MCUBOOT with serial

RE: MCUBOOT with serial

Amanda Hsieh — Mon, 01 Jul 2024 18:27:58 GMT

A customer makes it work for them in this post.

RE: MCUBOOT with serial

trampas — Mon, 01 Jul 2024 17:00:18 GMT

Thanks for the help but it appears this does not work with nRF5340 and two cores:

Build mcuboot with CONFIG_SINGLE_APPLICATION_SLOT=y is failed

Also it does not look like VSCode intellisense works with MCUBoot. Looks like Nordic has lots of work to do...

RE: MCUBOOT with serial

Amanda Hsieh — Thu, 27 Jun 2024 13:17:48 GMT

Hi,

[quote user="trampas"]I am now trying to figure out how to configure the serial recovery mode. [/quote]

Please take a look at this course https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-1-dfu-over-uart/

For the UART serial recovery mode, I use the overlay-serial-UART.conf to include the relevant configs and add these configs to overlay-mcuboot_external_flash.conf and these lines to overlay-dfu_external_flash.overlay in my test project.

[quote user="trampas"]Additionally just to make things hard, the console UART is not the same UART we want to use for serial recovery.[/quote]

The uart-mcumgr setting is here. You can overwrite it with an overlay file.

-Amanda H.

RE: MCUBOOT with serial

trampas — Wed, 26 Jun 2024 20:59:35 GMT

I am using 2.6.1

The first issue was that the the overlay-mcuboot_external_flash.conf was not being used. I had to put a mcuboot.conf in the child_image directory and copy the configuration over to this file. I assume this might be a "feature" of the more recent zephyr/ncs....

The second issue is we were using the hci-ipc for the second core, which used all the flash and did not leave enough room for the b0n bootloader. I had to change configuration, remove logging, etc until I got size down where the b0n would fit.

The third issue was after all this the processor would not boot. This appeared to be because the external flash chip was configured wrong. As it turns out the overlay, in dfu/conf/overlay-dfu_esternal_flash.overlay, was being used and was setup wrong.

Now I have the application compiling and booting again. I am now trying to figure out how to configure the serial recovery mode. For this project we are not doing OTA but only serial firmware update. There seems to be little information on how from the application to boot into the serial recovery mode. Additionally just to make things hard, the console UART is not the same UART we want to use for serial recovery.

RE: MCUBOOT with serial

Amanda Hsieh — Wed, 26 Jun 2024 17:45:27 GMT

Hi,

[quote user=""]c:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
c:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `FLASH' overflowed by 2076 bytes[/quote]

See this answer.

[quote user=""]c:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj): in function `k_sleep':
D:/Projects/Remington/reach-handpiece-wksp/handpiece-fw/reach_hp/build/mcuboot/zephyr/include/generated/syscalls/kernel.h:135: undefined reference to `z_impl_k_sleep'
c:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: D:/Projects/Remington/reach-handpiece-wksp/handpiece-fw/reach_hp/build/mcuboot/zephyr/include/generated/syscalls/kernel.h:135: undefined reference to `z_impl_k_sleep'[/quote]

Sees missing this overlay-mcuboot_external_flash.conf

[quote user=""]c:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj):(.rodata.spi_nor_config_0+0x0): undefined reference to `__device_dts_ord_151'[/quote]

Seems missing this overlay-dfu_external_flash.overlay

I followed this course https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-1-dfu-over-uart/ to modify the v2.6.1 nrf5340_audio and here is my test project devzone.nordicsemi.com/.../nrf5340_5F00_audio_5F00_UART_5F00_recovery.7z for UART Serial recovery. It will get into UART recovery mode by holding BTN4 while resetting the Audio DK. Then LED1 will light on Blue to indicate the Audio DK gets into the recovery mode.

Regards,
Amanda H.