I looked at a very similar thread that had this title for MacOS and I feel that my issues are the same however changing the hardware debugger only changes the error I get. I am using sdk5 and attempting to debug the blinky project.
I am able to compile and download working hex files onto the chip using a PCA10001 board. But when I run gdb using the DSF I get the following error
No symbol table is loaded. Use the "file" command.
Temporary breakpoint 2, 0x000001c2 in main ()
Everything is compiled correctly to my knowledge and I am pointing to the location of my .out file and I even looked into the makes and double checked gcc was running with -g3 debug option
When I changed to the "Standard GDB Hardware Debugging Launcher" instead of the "GDB (DSF) Hardware Debugging Launcher" I think I got a little closer but I still cannot get the NRF51822 to debug.
symbol-file "C:\Nordic Semiconductor\nRF51 SDK_v6.0.0.43681\Nordic\nrf51822\Board\pca10001\blinky_example\gcc\_build\blinky_gcc_xxaa.out" mon endian little mon flash device = NRF51822 mon reset 0 load "C:\Nordic Semiconductor\nRF51 SDK_v6.0.0.43681\Nordic\nrf51822\Board\pca10001\blinky_example\gcc\_build\blinky_gcc_xxaa.out" Loading section .text, size 0x8ec lma 0x0 Loading section .ARM.exidx, size 0x8 lma 0x8ec Loading section .data, size 0x444 lma 0x8f4 Start address 0x2f9, load size 3384 Transfer rate: 1652 KB/sec, 1128 bytes/write. tbreak main Temporary breakpoint 1 at 0x1c2 continue
Temporary breakpoint 1, 0x000001c2 in main () kill
If I navigated to the gcc/_build directory and ran arm-none-eabi-gdb, opened a the 2331 port to the remote target and tried stepping- It still got caught up at 0x1c2. I don't know what is so special about 0x1c2 but it does not run when I tell it to continue or step. So I am inclined to wonder if I am using the incorrect gdb tool.
I think I am just about bald now...
