ESP_Angus wrote: ↑

Mon Sep 24, 2018 5:24 am

Some progress was made to remove this limit a while back, but unfortunately it hasn't been completed yet.

Hi, are there any news about this topic? Is there any way I could help removing this limitation?

Thank you for your reply. Then I assume there is no (clear) solution to this so source-level debugging needs to be sacrificed if SDMMC is used on the JTAG pins.

Does anyone know any solution to this issue?
Thank you very much.

According to the documentation , only two pin configurations are available for the SDMMC host peripheral. We want to replace an already working SD card interfaced via SPI by eMMC storage, but the 4-bit slot available on the ESP32 is connected to the same pins as the JTAG inteface. (GPIO 12, 13, 14 ...

Each one of your messages are different, unrelated questions: After update the USB driver, i got another ERROR Error: type 'esp32' is missing virt2phys Despite the error message, it even pops up on valid setups (where JTAG is able to program and debug) so I guess it can be safely ignored. C:\Users\v...

I did not remember esp-idf expects test components to be listed manually into a CMake list called TEST_COMPONENTS. That solved the problem and made everything on my previous posts not needed. I hope this is useful to other users.

I made some progress on this topic: the test_utils component can be found at $IDF_PATH/tools/unit-test-app/components and can be added to the build process by using: set(EXTRA_COMPONENT_DIRS ${EXTRA_COMPONENT_DIRS} $ENV{IDF_PATH}/tools/unit-test-app/components) However, the following step fails, app...

From what I read from the log you attached, libusb is failing to locate your device. Could you please ensure the device is recognized by Windows and its vendor ID and product ID match those from the log (0403 and 6010, respectively)?

We want to run some unit tests and we realized they are not being added into the ${test_components} CMake variable and thus not compiled. This is roughly the tree structure of our project: - project (also $PROJECT_PATH) - components - a - test CMakeLists.txt /* other source files */ CMakeLists.txt /...

Any ideas? :) FYI, dlts_static is a byte array that allows allocating the resources needed by DTLS statically by the caller (in other words, without heap allocation) and, at the same time, hiding the internals of the actual structure underneath. Therefore, this opaque structure is only valid as long...