This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failure to loadfile binary to my PCB w/ nRF51822 using nRF51 DK Debug Out

I have built a PCB that uses the nRF51822 . I am failing to load the binary onto the chip via the nRF51 DK. I can:

connect to the nRF51822 on my mac using the JLinkExe.

execute the erase command in JLink I have a small binary called LED_TEST.hex that I attempt to load. No matter how many times I run loadfile, I get the message:

Downloading file [LED_TEST.hex]...Info: J-Link: Flash download: Restarting flash programming due to program error (possibly skipped erasure of half-way erased sector). Info: J-Link: Flash download: Skip optimizations disabled for second try. Error while programming flash: Programming failed.

I'm looking for ideas on how to best debug this. I have a file that I logged the SWD traffic into. I am new to SWD traffic, and there are A LOT of records...so i'm not sure where would be the best place to focus within the SWD traffic in order to tip me off why this is happening. Here is the log file: LBL_SWD_loadfile.txt

Parents
  • Thank you very much for your insight. I do believe I am connecting over SWD. Note the TCP/IP connection on the console output in Eclipse. Also, there are records to the debug port...which doesn't happen unless i connect. the protocol analyzer i am using is Saleae logic's..and i would agree with you...perhaps the parsing is incorrect. Connecting to J-Link... ... Target voltage: 3.30 V Listening on TCP/IP port 2331 Connecting to target...Connected to target Waiting for GDB connection...Connected to 127.0.0.1 Reading all registers Read 4 bytes @ address 0x00000000 (Data = 0x20000000) Target interface speed set to 1000 kHz Resetting target Halting target CPU... ...Target halted (PC = 0x0000048C)

Reply
  • Thank you very much for your insight. I do believe I am connecting over SWD. Note the TCP/IP connection on the console output in Eclipse. Also, there are records to the debug port...which doesn't happen unless i connect. the protocol analyzer i am using is Saleae logic's..and i would agree with you...perhaps the parsing is incorrect. Connecting to J-Link... ... Target voltage: 3.30 V Listening on TCP/IP port 2331 Connecting to target...Connected to target Waiting for GDB connection...Connected to 127.0.0.1 Reading all registers Read 4 bytes @ address 0x00000000 (Data = 0x20000000) Target interface speed set to 1000 kHz Resetting target Halting target CPU... ...Target halted (PC = 0x0000048C)

Children
No Data
Related