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

Question about changing the bootloader start address.

Hi

I am using nRF52832 and SDK13 versions.

Can I change the bootloader start address from 0x78000 to 0x77000?

Currently, bootloaders are using 0x78000 to 0x7DFFF area.

This time, we are referring to sample ble_app_multirole_lesc to use Security Mode1 Level4.

The area used in FDS init is 0x7D000, but it overlaps with the bootloader and is not ready.

So I want to change the address of Bootload. Or can we change the FDS area?

I desperately need your help.

Thanks.

  • Hi,

    FDS will allocate its flash pages based on the bootloader start address as its end address. In other words, the FDS will not overlap with the bootloader even if you re-program the device with a larger bootloader.

    But please note that it's not possible to change the start address of the bootloader through DFU. You need to be able to re-program the chip through the debug interface to do this.

    Best regards,

    Vidar

  • Hi

    Vidar.

    Thank you for your answer.

    Since I added personal code to the bootloader provided by SDK and used it, it is used beyond the 0x7D000 area.

    Regarding FDS, (#define FDS_VIRTUAL_PAGES 3) and (#define FDS_VIRTUAL_PAGE_SIZE 1024) were set and used in Sdk_config.h. In page_init() in fds_init(), 0x7D000 and 0x7E000 areas should be checked and ALREADY_INSTALLED, but the bootloader filled the 0x7D000 area.

    Is there any way?

    Best regards,

    Chu

  • Hi Chu,

    Mr.Chu said:
    Regarding FDS, (#define FDS_VIRTUAL_PAGES 3) and (#define FDS_VIRTUAL_PAGE_SIZE 1024) were set and used in Sdk_config.h. In page_init() in fds_init(), 0x7D000 and 0x7E000 areas should be checked and ALREADY_INSTALLED, but the bootloader filled the 0x7D000 area
    Mr.Chu said:
    Is there any way?

    Sorry, I'm not sure I understand question? If the bootloader starts at 0x7D000, then the FDS pages will be moved to address 0x7A000, 0x7B000, and 0x7C000.

    Best regards,

    Vidar

Related