FDS and bootloader

RE: FDS and bootloader

deren — Fri, 18 Sep 2020 00:43:00 GMT

This issue is still in SDK17

RE: FDS and bootloader

sudo — Tue, 11 Feb 2020 19:05:41 GMT

+1 from me too. This is still an issue in SDK v16.0.0. It is an easy fix, but it would be great if it were updated in the SDK so that we don't have to make manual changes as others have mentioned.

RE: FDS and bootloader

Xenoamor — Wed, 04 Dec 2019 15:30:50 GMT

I'm going to plus one this as well. Seems like a very low risk/effort change
For now I'll have to edit the SDK itself

RE: FDS and bootloader

Bojan Potocnik — Fri, 07 Jun 2019 11:57:46 GMT

This is still an issue in the SDK v15.3.0. When one want to change the DFU name from the application using `nrf_dfu_settings_adv_name_copy` and `nrf_dfu_settings_adv_name_write`, the files nrf_dfu_settings_svci.c, nrf_dfu_settings.c and nrf_dfu_flash.c are required to be compiled.

Error: L6200E: Symbol m_fs multiply defined (by nrf_dfu_flash.o and fds.o) occurs because:

nRF5_SDK_15\components\libraries\fds\fds.c

NRF_FSTORAGE_DEF(nrf_fstorage_t m_fs) =
{
    // The flash area boundaries are set in fds_init().
    .evt_handler = fs_event_handler,
};

nRF5_SDK_15\components\libraries\bootloader\dfu\nrf_dfu_flash.c

NRF_FSTORAGE_DEF(nrf_fstorage_t m_fs) =
{
    .evt_handler = dfu_fstorage_evt_handler,
    .start_addr  = MBR_SIZE,
    .end_addr    = BOOTLOADER_SETTINGS_ADDRESS + BOOTLOADER_SETTINGS_PAGE_SIZE
};

Could this please be renamed (as Kristin suggested) in the next SDK revision? I would not like to edit the SDK code locally, for multiple reasons.

RE: FDS and bootloader

Fabien Comte — Mon, 23 Apr 2018 14:17:13 GMT

Ok i will try that. Thank you.

RE: FDS and bootloader

FormerMember — Mon, 23 Apr 2018 08:06:08 GMT

From the build output, both instances of the FDS are named "m_fs". Changing the name of one of the instances should solve the problem, for example "m_bootloader_fs".