New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging is not working with firmware from Arduino IDE #12
Comments
Could you please attach the elf file, GDB remote log, and openocd log with increased log level ( |
Ok, thanks. I've tried reproducing this, looks like there are three issues:
|
The 2nd point (mon reset issue) has now been fixed, merge pending. |
Perhaps already solved in ESP-IDF, but I am using the Windows Sloeber-Arduino plugin. I solved this problem in Eclipse, by doing 2 things: 1: Setting the parameters in Eclipse->DebugAs->DebugConfiguration->GdbHardwareDebuging->Startup as follows: 2: Include file FreeRTOS-openocd.c the project... Using gdb also works; open a command shell and enter: |
#0 0x10c41485f in __asan_memcpy+0x1af (libclang_rt.asan_osx_dynamic.dylib:x86_64+0x4285f) #1 0x10ab3dcfd in buf_cpy binarybuffer.c:60 #2 0x10ab2774b in rtos_generic_stack_read rtos.c:664 #3 0x10aac3ed9 in freertos_get_thread_registers_from_stack FreeRTOS.c:1148 #4 0x10aab2ea2 in freertos_get_thread_reg_list FreeRTOS.c:1238 #5 0x10aab32b1 in freertos_get_thread_reg FreeRTOS.c:1269 #6 0x10aabe903 in freertos_get_tasks_details FreeRTOS.c:797 #7 0x10aab270f in freertos_update_threads FreeRTOS.c:1060 #8 0x10ab1d66e in rtos_thread_packet rtos.c:395 #9 0x10ab1bad2 in gdb_thread_packet rtos.c:191 #10 0x10aa4643d in gdb_input_inner gdb_server.c:3547 #11 0x10aa3d534 in gdb_input gdb_server.c:3743 #12 0x10aa8e565 in server_loop server.c:566 #13 0x1099f6e66 in openocd_thread openocd.c:380 #14 0x1099f685e in openocd_main openocd.c:419 #15 0x1099f52b1 in main main.c:40 #16 0x7fff6bf78cc8 in start+0x0 (libdyld.dylib:x86_64+0x1acc8)
Hi! I'm having a strange problem with debugging a simple example from Arduino IDE, whereas "Hello World" example from ESP-IDF can be debugged perfectly.
Hardware: FT2232H + esp32 dev board connected via JTAG.
When I'm trying to debug a simple "WiFiScan" sketch from Arduino in GDB I see either this GDB log with next openOCD log (looks like MCU stuck in ResetVector) or this one and this openOCD log with a strange thread number.
gdbinit it the same for both cases:
Am I missing something? Any advice and suggestions will be greatly appreciated!
The text was updated successfully, but these errors were encountered: