• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 90 subscribers
  • Views 720 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 286260
Options
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

nrf52840 dfu map

john.liu

sdk nRF5_SDK_17.0.2_d674dde

I used some flash to store data.

But before dfu,it was equal to  (FF FF FF FF FF FF FF FF|........) and after dfu,it was equal to (29 48 0C F0 FC FD 29 49|)H....)I)

It was changed after dfu.

I used flash adder:0x3e000

How to solve it? thanks very much.

Parents
  • +1

    Hi,

    During DFU, the nRF5 SDK bootloader will do a dual bank update if there is enough space for it, where it uses the available space between the end of the application and the beginning of the bootloader. However, the bootloader can be configured to lay off a configurable amount of pages, counting down from immediately below the bootloader. This is for instance where FDS pages are located, and also where you should locate any other flash page that you use for persistent storage (make sure they are below FDS pages again if that is used). Then, you need to adjust the NRF_DFU_APP_DATA_AREA_SIZE define in the bootloader's sdk_config.h so that it covers all the reserved flash pages. With this, the bootloader will never write to those pages.

    PS: See Memory layout figure to get a better overview of this.

Reply
  • +1

    Hi,

    During DFU, the nRF5 SDK bootloader will do a dual bank update if there is enough space for it, where it uses the available space between the end of the application and the beginning of the bootloader. However, the bootloader can be configured to lay off a configurable amount of pages, counting down from immediately below the bootloader. This is for instance where FDS pages are located, and also where you should locate any other flash page that you use for persistent storage (make sure they are below FDS pages again if that is used). Then, you need to adjust the NRF_DFU_APP_DATA_AREA_SIZE define in the bootloader's sdk_config.h so that it covers all the reserved flash pages. With this, the bootloader will never write to those pages.

    PS: See Memory layout figure to get a better overview of this.

Children
No Data
Related
Terms of service