Merging bootloader and application

RE: Merging bootloader and application

Vidar Berg — Fri, 01 Feb 2019 11:16:21 GMT

Your bootloader appears to have data in the mbr param page (memory layout), or have you allocated a different flash page for this (is allocated/reserved in flash_placement.xml)?

I just programmed the two hex files with the --sectorease to find out were the overlap was:

Note: bootloader settings occupy two flash pages if you use sdk 15.2.0. Otherwise you should use the --no-backup option when you generate the settings page with nrfutil.

Have a nice weekend:)

RE: Merging bootloader and application

Jesper de — Fri, 01 Feb 2019 09:13:33 GMT

we have checked the bootloader_settings_page, and it look like the post you have made.

Here are the files - could you please explain what you are looking for in them?

devzone.nordicsemi.com/.../1067.bootloader_5F00_setting.hex devzone.nordicsemi.com/.../dfu_5F00_fw.hex

have a nice weekend

Jesper de Fries

RE: Merging bootloader and application

Vidar Berg — Wed, 30 Jan 2019 12:57:07 GMT

Hello,

The settings page should not overlap with bootloader image. Have you made any changes to the default bootloader layout (i.e., Changing the address of the bootloader settings page)? Please verify that the "bootloader_settings_page" segment in flash_placement.xml looks like this:

  <MemorySegment name="bootloader_settings_page" start="0x0007F000" size="0x1000">
    <ProgramSection alignment="4" keep="Yes" load="No" name=".bootloader_settings_page" address_symbol="__start_bootloader_settings_page" end_symbol="__stop_bootloader_settings_page" start = "0x0007F000" size="0x1000" />
  </MemorySegment>

I can also try to find the "conflict" if you can upload bootloader_setting.hex and dfu_fw.hex

Best regards,

Vidar