• State Verified Answer
  • Locked Locked
  • Replies 16 replies
  • Subscribers 73 subscribers
  • Views 7261 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

    I compiled your project and was able to successfully flash it to nRF51822. I had to clean the project first.

    I was also able to reproduce the error you got. It happened when the "Makefile.common" and "gcc_nrf51_s110_bootloader_xxaa.ld" was not copied to the folder nrf51822\Source\templates\gcc. (These files are included in the GCC DFU project you found on GitHub)

    The .hex file should be called "bootloader_gcc_s110_bootloader_xxaa.hex" when the right linker script is chosen.

  • 0 in reply to Stian Røed Hafskjold

    Just to double check: I have the SoftDevice, My Application Project, and my DFU Application Project (bootloader - gcc - BLE). I first Erase-All, then flash the SoftDevice (88kB), then flash the .hex output of the DFU project (54kB), then My Application Project .hex code (112kB). Total memory usage is therefore 254kB. I don't think there is sufficient Flash memory to complete any OTA upgrade?

Reply
  • 0 in reply to Stian Røed Hafskjold

    Just to double check: I have the SoftDevice, My Application Project, and my DFU Application Project (bootloader - gcc - BLE). I first Erase-All, then flash the SoftDevice (88kB), then flash the .hex output of the DFU project (54kB), then My Application Project .hex code (112kB). Total memory usage is therefore 254kB. I don't think there is sufficient Flash memory to complete any OTA upgrade?

Children
No Data
Related
Terms of service