• State Verified Answer
  • Locked Locked
  • Replies 16 replies
  • Subscribers 67 subscribers
  • Views 6758 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104213
Options
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

Problems flashing the DFU on the Eval Kit

Locky

I am using the GCC DFU project provided by Nordic on GitHub (devzone.nordicsemi.com/.../)

I altered the main.c to trigger to DFU mode based on the contents of the GPREGRET register rather than Button 7. However when I try and Flash the .hex file (bootloader_gcc_xxaa.hex) of the project on nRFgo Studio I get the follow error. The hex file has data in SoftDevice region. Try programming using "Program SoftDevice", or erase all before programming.

Can I (,how can i) alter this project to not reside in the SoftDevice region or do I have to fully integrate it with the SoftDevice (7.0.0) .hex?

Thank you for your help.

P.S. I am using rRFgo Studio 1.17.1 to flash

nrf51_bootloader_gcc-master.zip

Parents
  • 0

    Also noted that when I build the Nordic DFU project from GitHub, the bootloader.bin file is 261,937kB in size. So quite my project it definately not linking to the linker file properly. However I do not have any option in Eclipse to set the linker file paths. Isn't this done via the Makefile, which is already correctly referenced as the project compiles?

Reply
  • 0

    Also noted that when I build the Nordic DFU project from GitHub, the bootloader.bin file is 261,937kB in size. So quite my project it definately not linking to the linker file properly. However I do not have any option in Eclipse to set the linker file paths. Isn't this done via the Makefile, which is already correctly referenced as the project compiles?

Children
No Data
Related