fs_data usage in DFU bootloader and ble_app_hrs_*_with_dfu

RE: fs_data usage in DFU bootloader and ble_app_hrs_*_with_dfu

Hung Bui — Mon, 22 Aug 2016 13:07:33 GMT

@Lucas&Eliot: I actually don't know. Not sure the naming is very important ? It's unused anyway.

RE: fs_data usage in DFU bootloader and ble_app_hrs_*_with_dfu

Eliot Stock — Fri, 19 Aug 2016 19:20:55 GMT

I'd also really like to know that.

RE: fs_data usage in DFU bootloader and ble_app_hrs_*_with_dfu

Lucas Magasweran — Thu, 24 Mar 2016 21:05:42 GMT

Thanks @hunbui, great explanation. Can you also clarify why the section is named .fs_data_out as opposed to .fs_data in the sample bootloader linker script?

RE: fs_data usage in DFU bootloader and ble_app_hrs_*_with_dfu

Hung Bui — Wed, 23 Mar 2016 13:14:30 GMT

Hi Lucas,

fs_data is the use of the Section variable library in the fstorage. fstorage in ble_app_hrs handles the storing of bond information in the application.

fs_data hold the configuration value for fstorage module, it is placed in RAM. It's the RW data that will be stored in flash but copied to RAM when the chip bootup.

The bootloader doesn't use fstorage so you will see the section is not initialized and remain at 0x00. The bootloader uses pstorage_raw instead, to handle the flash management.

You don't have to worry about the fs_data when doing DFU, it's not related.