This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

I am looking for some guidance as to the memory regions to reserve for the Bootloader hex if I pull it in via Segger Embedded Studio. I have the memory allocations for the Application down pat and there is no problem linking in the SoftDevice. However how do I specify where the Bootloader goes (at the top of the memory allocation) using the section placement macros in Linker Options?

[UPDATE 10 JUNE - Brought up from the dead as it would be good if an answer could be found to this]

Thanks a lot - RJH

Parents
  • Note: A common misconception is that you need to flash the bootloader using nrfjprog. This is only the case when using Keil with nRF51. The Keil Flash algorithms can't properly write the UICR on nRF51 and this is why the problem occurs.

    If you are developing on nRF52, or you aren't using Keil, you can use your IDE to program the Bootloader no problem! (to be clear: You can program the bootloader from the Keil IDE when using nRF52 device).

Reply
  • Note: A common misconception is that you need to flash the bootloader using nrfjprog. This is only the case when using Keil with nRF51. The Keil Flash algorithms can't properly write the UICR on nRF51 and this is why the problem occurs.

    If you are developing on nRF52, or you aren't using Keil, you can use your IDE to program the Bootloader no problem! (to be clear: You can program the bootloader from the Keil IDE when using nRF52 device).

Children
No Data
Related