“armToolchainPath”: “C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major\bin” The Debugger stopped in the same place and there are 3 of the same warnings: if(NOT ($\build\zephyr\zephyr.elf”, Changed prj.conf, did a west build and west flash. Read 2 bytes address 0×0000CF4E (Data = 0xFA36) Read 2 bytes address 0×0000CF4C (Data = 0xF002) Waiting for GDB connection…Connected to 127.0.0.1
#Segger embedded studio changing from executable to library .dll
JLinkARM.dll V6.86f (DLL compiled 18:00:13)Ĭommand line: -if swd -port 50000 -swoport 50001 -telnetport 50002 -device nrf9160_xxAAįirmware: J-Link OB-K22-NordicSemi compiled 17:33:01įeature(s): RDI, FlashBP, FlashDL, JFlash, GDB SEGGER J-Link GDB Server V6.86f Command Line Version
Not implemented stop reason (assuming exception): undefined Reading symbols from C:\ncs\zephyr\samples\basic\blinky/build/zephyr/zephyr.elf… UndefinedC:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major\bin\arm-none-eabi-gdb.exe: warning: Couldn’t determine a path for the index cache directory. Launching GDB: “C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major\bin\arm-none-eabi-gdb.exe” “-q” “–interpreter=mi2” Please check OUTPUT tab (Adapter Output) for output from JLinkGDBServerCL.exe Squiggles are disabled for this translation unit (C:\ncs\zephyr\samples\basic\blinky\src\main.c).C/C++(1696)Ĭannot open source file “nrfx.h” (dependency of “zephyr.h”)C/C++(1696) #include errors detected based on information provided by the configurationProvider setting. The debugger launched however it stopped with some problems: I decided to go back to the VCS debugger since the new Jlink path was added. Now when I run Jlinkgdbservercl.exe it finds it tells me the device is unspecified…. SEGGER J-Link Commander V6.86f (Compiled 18:01:48) When I first opened a command prompt and ran both jlink.exe and jlinkgdbservercl.exe they were not recognized so I added to path to those executable to the path variable in the environmental variables. I’m not sure what this is telling me to do?
Now the VSC Debug Console is giving me the following message: Please check OUTPUT tab (Adapter Output) for output from JLinkGDBServerCL.exe However, I’m still getting the “Failed to launch…” error. When I checked the VSC output (which I hadn’t done before) after launching the debugger again I got this message: For C source files, IntelliSenseMode was changed from “msvc-圆4” to “gcc-arm” based on compiler args and probing compilerPath: “C:\PROGRA 2\GNUTOO1\92019- 1\bin\AR19DD1.EXE”īased on this message I went into the the c. and changed “intelliSenseMode”: “msvc-圆4” to “intelliSenseMode”: “gcc-arm”. Actually, I think I had already installed the nRF Command Line Tool when I first set up my the nrf5340 and the j-link. I installed the nRF Command Line Tools and got the same issue.
0 kommentar(er)
