Bootloader using QSPI as source

RE: Bootloader using QSPI as source

Sigurd — Tue, 18 Jan 2022 15:02:59 GMT

We don't have anything for that. It will require some major changes in the bootloader. See this similar post: https://devzone.nordicsemi.com/f/nordic-q-a/75120/dfu-in-external-memory

RE: Bootloader using QSPI as source

Randy Lee — Mon, 17 Jan 2022 13:47:51 GMT

OK, I can maybe construct what I'm after here in some combination with the BLE version or something .... What I'm really after tho is using QSPI (or any other storage for that matter) to have an image that I'd replace the FLASH with after checking it for validity. So it'd act in the end like the DFU path, but grab it from some big internal memory rather than OTA...

Basically I want to put into my QSPI memory is some sort of image that I'll use as the input to the bootloader. I can treat it more or less like a serial port (in a very abstract sense)...

Unlike a serial port (or BLE for that matter), doing this means I can check the integrity of the image BEFORE I blow away my FLASH and not do it if it's not good.

RE: Bootloader using QSPI as source

Sigurd — Mon, 17 Jan 2022 08:36:32 GMT

Hi,

Take a look at this example: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/qspi_bootloader_example.html

RE: Bootloader using QSPI as source

Randy Lee — Fri, 14 Jan 2022 12:53:46 GMT

Sorry, my bad: RF5 SDK 15.3 on 52840

RE: Bootloader using QSPI as source

Sigurd — Fri, 14 Jan 2022 09:43:39 GMT

Hi,

Are you using nRF Connect SDK, or nRF5 SDK?

For nRF Connect SDK we have this: http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.8.0/nrf/ug_bootloader_external_flash.html