MCUboot spi-nor external flash

[jju]

We have developed a custom board with an external SPI flash, which I have tested and it works. 

We want to use OTA over BLE, so we have added MCUboot to the project, which should use the external flash.

We are using SDK toolchain v2.6.1

In the prj.conf file I have enabled SPI external flash and MCU boot using:

CONFIG_FLASH=y

CONFIG_FLASH_MAP=y

CONFIG_SPI=y

CONFIG_SPI_NOR=y

CONFIG_BOOTLOADER_MCUBOOT=y

I have created a folder:

The files are added here.

When I try to build i fails with the error:

zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj):(.rodata.spi_nor_config_0+0x0): undefined reference to `__device_dts_ord_99'

Which I think refers to the spi-nor driver, but I'm stuck here, and cannot figure out why this happens. ?

4760.mcuboot.overlay

6835.mcuboot.conf

[Amanda Hsieh]

Hi, 

See my colleague's example in this case. 

Regards,
Amanda H.

[jju]

Hi, thank you.
Now it builds. :-)
But when powered on, it writes *** Booting nRF Connect SDK v3.5.99-ncs1-1 *** forever on the uart output.
I'm not sure why, but it does not seem to advertise 

[Amanda Hsieh]

You can take a look at this course https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-3-fota-over-bluetooth-low-energy/ 

[jju]

I got the peripheral lbs sample working, but I think I need some clarification, since I maybe don't exactly understand, how the mechanism is when using external flash.

In my App I initialize all the BT (as the peripheral lbs) and then call smp_bt_register();.

In the overlay files for the App and MCUboot I enable the CONFIG_SPI_NOR stuff.

But what is is the OTA mechanism exactly ?

1. The App connects to bluetooth, and transfers the data using the SMP protocol to the external flash.

2. The MCU reboots, and the MCUboot copies the content from the external flash to the internal flash (App section).

3. The MCUboot (starts) jumps to the App start vector in internal flash.

Is my understanding correct ?

(Note, when I debug using jtag, it looks like MCUboot is trying to boot from the external flash? )

[Amanda Hsieh]

Hi, 

The MCUboot secondary partition can then be placed in the external flash, increasing the available space for the application.

Please take a look at this DevAcademy course Lesson 8 – Bootloaders and DFU/FOTA for the OTA mechanism. 

-Amanda H.

[jju]

Thank you.
I almost got it working now... :-)
But when I updated the fw using the NRFconnect App, I cannot update again, it seems that it complaint about there is not enough room for the image.
But it should erase the external flash, not try to fit another image into that region. ?

I get the error:
I: Image index: 0, Swap type: perm
E: Image upload inspect failed: 9

[Amanda Hsieh]

Hi, 

Did you enable CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY in the prj.conf?

Could you provide the memory layout by executing "ninja partition_manager_report" under the build folder?

-Amanda H.

[jju]

Yes, I did put that line in the prj.conj for the main project, but not for the child_image project.

[Amanda Hsieh]

I suspect your external flash setting is not correct. You can check the memory layout by executing "ninja partition_manager_report" under the build folder or generate a Memory report  and provide the memory layout from the Partitions tab. 

You should see the mcuboot_secondary located on the external memory or at least the external memory.