example_spp_acceptor_demo won't start under debug
Posted: Mon Jul 04, 2022 2:23 pm
Hi
I am using esp-idf-v4.4, platformio and VS Code. I am using an AZ Delivery ESP32DevKitCV2 and ESP-Prog debug board.
I have built example_spp_initiator and it runs successfully under the debugger and my Serial Bluetooth Terminal app can see it.
Using the same hardware, I can build the companion acceptor program and upload it to the ESP board.
However, when I try to run the program under the debugger, despite placing a breakpoint on the first line on main(), I am getting the following:
esp32.cpu1: Debug controller was reset.
esp32.cpu1: Core was reset.
esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
Temporary breakpoint 1 at 0x400d278c: file src/main.c, line 168.
PlatformIO: Initialization completed
PlatformIO: Resume the execution to `debug_init_break = tbreak app_main`
PlatformIO: More configuration options -> https://bit.ly/pio-debug
Note: automatically using hardware breakpoints for read-only addresses.
Info : esp32.cpu0: Target ha
lted, PC=0x40081D12, debug_reason=00000001
esp32.cpu0: Target halted, PC=0x40081D12, debug_reason=00000001
Info : Set GDB target to 'esp32.cpu0'
Set GDB target to 'esp32.cpu0'
Info : esp32.cpu1: Target halted, PC=0x4000C050, debug_reason=00000000
esp32.cpu1: Target halted, PC=0x4000C050, debug_reason=00000000
Program
received signal SIGTRAP, Trace/breakpoint trap.
0x40081d12 in panic_abort (details=0x3ffe339b "assert failed: s_prepare_reserved_regions C:\\.platformio\\packages\\framework-espidf\\components\\soc\\memory_layout_utils.c:94 (reserved[i + 1].start > reserved.start)") at C:\.platformio\packages\framework-espidf\components\esp_system\panic.c:404
404 *((int *) 0) = 0; // NOLINT(clang-analyzer-core.NullDereference) should be an invalid operation on targets
Where do I start looking?
Tim
I am using esp-idf-v4.4, platformio and VS Code. I am using an AZ Delivery ESP32DevKitCV2 and ESP-Prog debug board.
I have built example_spp_initiator and it runs successfully under the debugger and my Serial Bluetooth Terminal app can see it.
Using the same hardware, I can build the companion acceptor program and upload it to the ESP board.
However, when I try to run the program under the debugger, despite placing a breakpoint on the first line on main(), I am getting the following:
esp32.cpu1: Debug controller was reset.
esp32.cpu1: Core was reset.
esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
Temporary breakpoint 1 at 0x400d278c: file src/main.c, line 168.
PlatformIO: Initialization completed
PlatformIO: Resume the execution to `debug_init_break = tbreak app_main`
PlatformIO: More configuration options -> https://bit.ly/pio-debug
Note: automatically using hardware breakpoints for read-only addresses.
Info : esp32.cpu0: Target ha
lted, PC=0x40081D12, debug_reason=00000001
esp32.cpu0: Target halted, PC=0x40081D12, debug_reason=00000001
Info : Set GDB target to 'esp32.cpu0'
Set GDB target to 'esp32.cpu0'
Info : esp32.cpu1: Target halted, PC=0x4000C050, debug_reason=00000000
esp32.cpu1: Target halted, PC=0x4000C050, debug_reason=00000000
Program
received signal SIGTRAP, Trace/breakpoint trap.
0x40081d12 in panic_abort (details=0x3ffe339b "assert failed: s_prepare_reserved_regions C:\\.platformio\\packages\\framework-espidf\\components\\soc\\memory_layout_utils.c:94 (reserved[i + 1].start > reserved.start)") at C:\.platformio\packages\framework-espidf\components\esp_system\panic.c:404
404 *((int *) 0) = 0; // NOLINT(clang-analyzer-core.NullDereference) should be an invalid operation on targets
Where do I start looking?
Tim