Write firmware to bank 1 from application

[oferAtom]

Hello.

I would like to know if its possible to preform a firmware update from the application itself like so:

1. Getting the firmware via UART in chunks of 2k (from a GSM modem).

2. Writing each chunk to Bank1.

3. Reset to DFU mode that will check if the data in Bank1 is valid.

4. If so, copy it to Bank0 and start the application.

If its possible, I would like to know how to write directly to bank1 from my application and how to reset to that DFU mode.

We are currently using SDK15.

Thanks and all the best,

Ofer.

[Vidar Berg]

Hello,

Yes, it should be possible re-use our existing DFU and bootloader libraries for this. Please take a look at this thread : https://devzone.nordicsemi.com/f/nordic-q-a/46994/background-dfu-application-source-code and see if helps answer your questions. Requirements were mostly the same except this customer was planning to receive the image from a Wifi module.

Best regards,

Vidar

[oferAtom]

Hi Vidar,

Thank you for the reply.

I've read the thread you send and many others including this one. Please let me know if I got this correctly:

From my application:

1. Get Bank1 address by calling nrf_dfu_bank1_start_addr().

2. Write the file I download to to that address (The file is the output of the nrfutil).

3. Call nrf_dfu_validation_init_cmd_execute(<Bank1 address>, <file size>).

4. If the return value is NRF_DFU_RES_CODE_SUCCESS, reset.

In the bootloader: The nrf_bootloader_init will call nrf_bootloader_fw_activate and app_activate() the new firmware?

All the best,
Ofer.

[oferAtom]

Hi Vidar,

Can I simply put the files (or just the *.bin file) in Bank1 and reset?

Will the bootloader see that it has data in Bank1, validate it and copy it to Bank0?

All the best,
Ofer.

[Vidar Berg]

Hi Ofer,

Yes, you can store the *.bin directly to bank 1 as well, but you will also need to store the init data (*.dat) to the BL settings page before you reset. This gives the bootloader the information it needs to activate the new app (Size of image, version number, etc - see Init packet).

Best regards,

Vidar

[oferAtom]

Thank you Vidar, I will try it.

[oferAtom]

Hi Vidar,

I'm trying to write my .bin file to bank1 but I get an error.

Here is what I did:

Init: 

nrf_dfu_flash_init(true)
uint32_t bank1_addr_offset = nrf_dfu_bank1_start_addr();

Getting first 4096 bytes chunk:

nrf_dfu_flash_erase(bank1_addr_offset, 1, NULL);
nrf_dfu_flash_store(bank1_addr_offset, chunk, chunk_len, NULL);
bank1_addr_offset += chunk_len;

The nrf_dfu_flash_erase prints: nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x00026000, len=1 pages), queue usage: 0

And the error happens in nrf_dfu_flash_store: <error> app: SOFTDEVICE: INVALID MEMORY ACCESS

Can you please tell me what I'm doing wrong?

My main goal is that once all the chunks are written to bank1 is to update the settings with the .dat file and reboot.

Thank you,

Ofer.

[Vidar Berg]

Hi Ofer,

Your current application is starting at address 0x26000 in flash (ie bank 0 start address), so Bank 1 should have been placed higher up in flash.

Have you programmed the Bootloader settings page? The s_dfu_settings.bank_0.image_size field should contain the size of your app so nrf_dfu_bank1_start_addr() can correctly determine the bank 1 address.

[oferAtom]

Hi Vidar,

I'm note sure I understand what you mean. I didn't programmed the Bootloader setting page yet. I get bank1 address from: 

uint32_t nrf_dfu_bank1_start_addr(void)
{
    uint32_t bank0_addr = nrf_dfu_bank0_start_addr();
    return ALIGN_TO_PAGE(bank0_addr + s_dfu_settings.bank_0.image_size);
}

Doesn't this already pointing to the start location of bank1?

[oferAtom]

I've added:

 

  <MemorySegment name="bootloader_settings_page" start="0x000FF000" 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 = "0x000FF000" size="0x1000" />
  </MemorySegment>
  <MemorySegment name="mbr_params_page" start="0x000FE000" size="0x1000">
	<ProgramSection alignment="4" keep="Yes" load="No" name=".mbr_params_page" address_symbol="__start_mbr_params_page" end_symbol="__stop_mbr_params_page" start = "0x000FE000" size="0x1000" />
  </MemorySegment>
  <MemorySegment name="ot_flash_data" start="0xdc000" size="0x4000">
	<ProgramSection alignment="4" keep="Yes" load="Yes" name=".ot_flash_data" address_symbol="__start_ot_flash_data" end_symbol="__stop_ot_flash_data" start = "0xdc000" size="0x4000" />
  </MemorySegment>
  <MemorySegment name="uicr_bootloader_start_address" start="0x00000FF8" size="0x4">
	<ProgramSection alignment="4" keep="Yes" load="Yes" name=".uicr_bootloader_start_address" address_symbol="__start_uicr_bootloader_start_address" end_symbol="__stop_uicr_bootloader_start_address" start = "0x00000FF8" size="0x4" />
  </MemorySegment>
  <MemorySegment name="uicr_mbr_params_page" start="0x00000FFC" size="0x4">
	<ProgramSection alignment="4" keep="Yes" load="Yes" name=".uicr_mbr_params_page" address_symbol="__start_uicr_mbr_params_page" end_symbol="__stop_uicr_mbr_params_page" start = "0x00000FFC" size="0x4" />
  </MemorySegment>
</Root>

To flash_placement.xml and and bootloader_settings_page RX 0x000FF000 0x1000;uicr_mbr_params_page RX 0x00000FFC 0x4;mbr_params_page RX 0x000FE000 0x1000

to the Memory segments.

Now the bank1 address is 0x72000 but the error: <error> app: SOFTDEVICE: INVALID MEMORY ACCESS still appears.

[Vidar Berg]

Hi Ofer,

The Softdevice will trigger the INVALID MEMORY ACCESS assert if the application tries to access either memory or peripherals that are reserved to the Softdevice (System on Chip resource requirements). As this is occuring when you try to do flash, I assume the problem is that you try to use the NVMC directly and not through the SD flash API.  Please make sure you have selected the SoftDevice backend for fstorage.