I've designed a custom board using the ESP32-solo-1. I'm using JTAG (JLink) to flash and debug it (currently from command line, intent to switch to Eclipse when everything is working).
I can flash it just fine with the following command:
Code: Select all
openocd -f interface/jlink.cfg -f target/esp32-solo-1.cfg -c "program_esp /Users/remco/eclipse-workspace/IDFTest/build/app-template.bin 0x10000 verify"
When I then start a debug session (from a second terminal) using
Code: Select all
xtensa-esp32-elf-gdb -x gdbinit ~/eclipse-workspace/IDFTest/build/app-template.elf
I've recompiled the app_template IDF example with FreeRTOS configured to use only a single core.
When I use a DevKitC V4 development board (with ESP32-WROOM-32D), the previous commands will indeed result in GDB stopping at the app_main() breakpoint. So it seems the JTAG setup and application are fine.
How can I verify why my custom board never hits the app_main() breakpoint?
Thanks in advance.
Kind regards,
Remco Poelstra