RE: Unable to debug nRF9160 using VSCode

user113696 — Wed, 15 Jun 2022 05:25:54 GMT

I ran into this issue again but this time with the nrf9160dk. I notice this issue occurs every time the MCU hits a hardfault. For example, using Segger, I saw that my code hits a hardfault at C:\ncs\v1.9.1\zephyr\arch\arm\core\aarch32\cortex_m\fault_s.S

SECTION_SUBSEC_FUNC(TEXT,__fault,z_arm_exc_spurious)

mrs r0, MSP
mrs r1, PSP
push {r0, lr}

If I debugged the same code with the debugger in VSCode, the debugger will crash and hangs forever when this breakpoint is about to be hit.

RE: Unable to debug nRF9160 using VSCode

user101568 — Tue, 14 Jun 2022 18:59:21 GMT

I'm unable to debug at all. It's a custom board using the nRF9160. I'm building on toolchain 2.0.0. Below is my output. The end result I get an error "Failed to launch undefined GDB Server: Timeout." I see the SEGGER J-Link GDB Server but it says at the bottom "waiting for GDB connection... and then it times out.

Below is the full output...

Reading symbols from c:\ncs\toolchains\v2.0.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-objdump.exe --syms -C -h -w c:\720-0068-00_200\trunk\design_files\F9160\APP\build\zephyr\merged.hex
Reading symbols from c:/ncs\toolchains\v2.0.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-nm.exe --defined-only -S -l -C -p c:\720-0068-00_200\trunk\design_files\F9160\APP\build\zephyr\merged.hex
Launching GDB: "c:\\ncs\\toolchains\\v2.0.0\\opt\\zephyr-sdk\\arm-zephyr-eabi\\bin\\arm-zephyr-eabi-gdb-no-py.exe" -q --interpreter=mi2 "c:\\720-0068-00_200\\trunk\\design_files\\F9160\\APP\\build\\zephyr\\merged.hex"
Set "showDevDebugOutput": true in your "launch.json" to see verbose GDB transactions here. Helpful to debug issues or report problems
Launching gdb-server: "C:/Program Files (x86)/SEGGER/JLink/JLinkGDBServer.exe" -singlerun -nogui -if swd -port 50000 -swoport 50001 -telnetport 50002 -device nRF9160_xxAA -select usb=504403659 -rtos "C:\\Program Files (x86)\\SEGGER\\JLink\\GDBServer\\RTOSPlugin_Zephyr.dll"
Please check TERMINAL tab (gdb-server) for output from C:/Program Files (x86)/SEGGER/JLink/JLinkGDBServer.exe
Finished reading symbols from objdump: Time: 88 ms
Finished reading symbols from nm: Time: 87 ms
Reading symbols from c:\720-0068-00_200\trunk\design_files\F9160\APP\build\zephyr\merged.hex...
(No debugging symbols found in c:\720-0068-00_200\trunk\design_files\F9160\APP\build\zephyr\merged.hex)
GNU gdb (Zephyr SDK 0.14.1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <gnu.org/.../gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-host_w64-mingw32 --target=arm-zephyr-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<github.com/.../issues>.
Find the GDB manual and other documentation resources online at:
<www.gnu.org/.../>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Failed to launch undefined GDB Server: Timeout.

RE: Unable to debug nRF9160 using VSCode

user113696 — Thu, 09 Jun 2022 07:36:17 GMT

Yes. The table here represents the result of my experiment

Application	Board	Can Debug via Vscode?	Can Debug via Segger?
Custom Application	Custom Board	No, debugger hangs forever	Yes
AT_Client	Custom Board	Yes	Yes

RE: Unable to debug nRF9160 using VSCode

user108933 — Thu, 09 Jun 2022 07:21:07 GMT

Hello,

''I tried debugging one of sample, "nRF9160/AT Client", and the same custom board can be debugged fine. '' You meant that you had no problem for AT client. So, the problem is when you try to run the custom application?

I have been talking to VS code team regarding this issue. I will get back to you later.

Thanks.

Best Regards