FOTA to external flash

RE: FOTA to external flash

Marshall — Wed, 09 Nov 2022 09:43:33 GMT

Yep, its all working sweet now.

Thanks for the support.

Marshall

RE: FOTA to external flash

Marshall — Wed, 09 Nov 2022 07:49:39 GMT

Thanks Simon,

Please don't close it yet, I'm seeing some weirdness on subsequent reboots. But I haven't had a chance to go through it yet.

Regards

Marshall

RE: FOTA to external flash

Simonr — Wed, 09 Nov 2022 07:29:36 GMT

Glad that it worked Marshall! I'm very sorry it took so long to get to the bottom of this though, let me know if you're in need of further assistance or if we can close this case.

Best regards,

Simon

RE: FOTA to external flash

Marshall — Tue, 08 Nov 2022 19:44:41 GMT

Thanks Simon

That solution works!

For anyone else browsing the same issue here is the link to the other post which tells you the exact changes to make in two lines.

View online

Regards

Marshall

RE: FOTA to external flash

Simonr — Tue, 08 Nov 2022 13:05:06 GMT

Hi Marshall

So, after some investigation and multiple discussions internally, there appears to be some big problems with external flash usage for the nRF91 and nRF53 series in NCS 2.1.x, and I'm very sorry I wasn't aware of this before now. It is indeed related to the case you linked to and we are working on a solution for the next release of NCS to fix this. For now, I think the fix will be to roll back to NCS 2.0.x to use external flash in applications. Unfortunately we don't have a project doing this already for the asset tracker v2 application.

Best regards,

Simon

UPDATE: I was just suggested a fix for using the external flash in your nRF91 application.

You need to set the CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y in your projects config file (described here).
You need to add this fix to your NCS directory: https://github.com/nrfconnect/sdk-nrf/pull/9169/files#diff-3618c46f4d0a530f32e99d83263fe217269f73f927f5c110f8aed6db3b8800dbR215

RE: FOTA to external flash

Marshall — Sun, 06 Nov 2022 08:52:49 GMT

Does this work at all, I've spent yet another weekend banging my head on the desk!

Can you please post a link to a WORKING and tested response to your point 2 above.

Also I found this... It seems to sum up the issues I'm having.

MCUBoot Update hooks - Rejects any mcuboot updates when used with immutable bootlader - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

Thanks

Marshall

RE: FOTA to external flash

Simonr — Fri, 04 Nov 2022 13:59:20 GMT

1. There shouldn't be necessary to do anything different compared to other applications to enable FOTA in the Asset Tracker v2 project.

2. To enable FOTA with external flash in you should set the external flash as the "chosen" target in the partition manager as explained in the external flash memory partitions documentation.

Best regards,

Simon

RE: FOTA to external flash

Marshall — Thu, 03 Nov 2022 19:22:17 GMT

Thanks Simon.

I was wanting to see any MCU Boot messages when it started to try and determine if my external flash was being detected by MCUBoot.

"We're also not sure where exactly this error occurs, as it only refers to your application trying to call a bad address after this firmware update it seems."

I'm not sure which issue this is referring to:

The original - "dfu_target_mcuboot: boot_request_upgrade for image-0 error -14"
The disabling of dfu by default in Asset Tracker V2

Perhaps it would be simpler if I rephrase the issue like this.

How do I enable FOTA in Asset Tracker V2?
How do I enable FOTA with External Flash in Asset Tracker V2?

Thanks and Regards

Marshall

RE: FOTA to external flash

Simonr — Thu, 03 Nov 2022 14:18:45 GMT

Sorry about the late reply, I needed to discuss this with some colleagues. First off, what exactly are you wanting to get the log of here exactly? The MCUBoot logging will only log the bootloader (what occurs when the MCU boots up before going into the application area), and not the entire DFU process. The logs of the actual DFU with the files moving from one place and onto your board is set in the DFU part of your application.

We're also not sure where exactly this error occurs, as it only refers to your application trying to call a bad address after this firmware update it seems.

Best regards,

Simon

RE: FOTA to external flash

Marshall — Tue, 01 Nov 2022 12:09:34 GMT

What is this in the asset_tracker_v2 application.

\boards\thingy91_nrf9160_ns.conf

# Disable MCUboot DFU -- incompatible with static partitions

CONFIG_SECURE_BOOT=n

CONFIG_BUILD_S1_VARIANT=n

I thought I got rid of static partitions. by comment out or rename the file

C:\ncs\v2.1.0\nrf\boards\arm\thingy91_nrf9160\thingy91_pm_static.yml

Don't I want to enable this so I can FOTA the new app into slot1 ?????

When I do enable it, it won't compile

CONFIG_SECURE_BOOT=y

CONFIG_BUILD_S1_VARIANT=y

D C:\opito\zephyr\opito_base_oct22\build\b0\zephyr && C:\ncs\toolchains\v2.1.0\opt\bin\cmake.exe -E echo ""
c:/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim.c.obj): in function `k_sem_give':
C:\opito\zephyr\opito_base_oct22\build\b0\zephyr\include\generated\syscalls\kernel.h:1062: undefined reference to `z_impl_k_sem_give'
c:/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim.c.obj): in function `k_sem_take':
C:\opito\zephyr\opito_base_oct22\build\b0\zephyr\include\generated\syscalls\kernel.h:1045: undefined reference to `z_impl_k_sem_take'
c:/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: C:\opito\zephyr\opito_base_oct22\build\b0\zephyr\include\generated\syscalls\kernel.h:1045: undefined reference to `z_impl_k_sem_take'
c:/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim.c.obj): in function `k_sem_give':
C:\opito\zephyr\opito_base_oct22\build\b0\zephyr\include\generated\syscalls\kernel.h:1062: undefined reference to `z_impl_k_sem_give'
c:/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim.c.obj): in function `k_sem_take':
C:\opito\zephyr\opito_base_oct22\build\b0\zephyr\include\generated\syscalls\kernel.h:1045: undefined reference to `z_impl_k_sem_take'
collect2.exe: error: ld returned 1 exit status

It really shouldn't be this hard...

Thanks

Marshall

RE: FOTA to external flash

Marshall — Tue, 01 Nov 2022 10:53:15 GMT

Thanks, that didn't work though.

Is there somewhere that you set the serial port config for MCUBoot as well?

This is in mcuboot.conf

CONFIG_SERIAL=y
CONFIG_LOG=y
CONFIG_LOG_BACKEND_UART=y 
CONFIG_MCUBOOT_LOG_LEVEL_DBG=y
#CONFIG_LOG_MODE_MINIMAL=y # former CONFIG_MODE_MINIMAL
### Ensure Zephyr logging changes don't use more resources
#was 0
CONFIG_LOG_DEFAULT_LEVEL=4 
### Decrease footprint by ~4 KB in comparison to CBPRINTF_COMPLETE=y
CONFIG_CBPRINTF_NANO=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_THREAD_NAME=y
#CONFIG_DEBUG_OPTIMIZATIONS=y

The overlay above is also in the child image folder, and the pins are correct for the UART.

Thanks

Marshall

RE: FOTA to external flash

Simonr — Tue, 01 Nov 2022 10:05:01 GMT

Hi Marshall

If you want to enable logging in the MCUBoot you need to add CONFIG_LOG=y and the backend you want to use CONFIG_LOG_BACKEND_UART=y for example. In projects where MCUBoot is the child image you should do it in the mcuboot.conf file located under child images I believe. Like this for example:

Best regards,

Simon

RE: FOTA to external flash

Marshall — Mon, 31 Oct 2022 19:23:42 GMT

Hi Simon

I just read out the JEDEC ID from the Flash, it matches the overlay.

[00:00:00.501,708] <inf> opito: JEDEC SPI-NOR SPI flash testing
[00:00:00.501,708] <inf> opito: ==========================
[00:00:00.503,021] <inf> opito: Flash read ID succeeded! 9d 60 16
[00:00:00.503,051] <inf> opito: Test 1: Flash erase
[00:00:00.553,863] <inf> opito: Flash erase succeeded!
[00:00:00.553,863] <inf> opito: Test 2: Flash write
[00:00:00.553,894] <inf> opito: Attempting to write 4 bytes
[00:00:00.558,868] <inf> opito: Data read matches data written. Good!!

Regards

Marshall

RE: FOTA to external flash

Marshall — Mon, 31 Oct 2022 18:44:11 GMT

Thanks for the reply Simon,

I am using a CircuitDojo Feather board, this has different flash on it, and the pins for driving it are different.

64/128 Mbit Single Operation Voltage (mouser.com)

The Flash is working, with the current overlay I'm using above.

But there are some good clues in your response that'll I'll follow.

How do I turn on the logging in the bootloader in Asset Tracker V2? It would be useful while I'm trying to sort out whats going on.

Regards

Marshall

RE: FOTA to external flash

Simonr — Mon, 31 Oct 2022 14:21:05 GMT

This issue looks very much like the issue described in this case, and seems to be related to the device JEDEC ID that you have set for your external flash. As my colleague Håkon explains, this can be read out of the datasheet of your used external flash. For the external flash mounted on the nRF91 DK, this is C2 28 17. If you read all zeroes here, your device has issues connecting to your flash.

For the nRF9160-DK, you must switch in the pins for communicating with the flash, as explained in this post:

RE: Full modem update configuration

Note that this is for the board controller, i.e. nrf9160dk_nrf52840, so it is important that you set the switch into "NRF52" position before programming the above snippet.

Best regards,

Simon