mcuboot reads jedec id of external spi flash as 00 00 00 in nRF Connect SDK versions 2.3.0, 2.4.0 and 2.4.1

[mnor]

Good day,

I've got a secondary slot in external spi flash working in version 2.2.0 of the nRF Connect SDK.

However, when I upgrade to versions 2.3.0, 2.4.0 or 2.4.1 of the SDK and use the attached .conf file I get the following error from mcuboot.

E: Device id 00 00 00 does not match config 1f 45 08
I: fs=2, odr=0x4 lp_en=0x0 scale=9576
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
I: Starting bootloader
W: Failed reading sectors; BOOT_MAX_IMG_SECTORS=256 - too small?
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0x10000
I: Jumping to the first image slotrmiot:~$ [00:00:00.007,354] <inf> lis2dh: fs=2, odr=0x4 lp_en=0x0 scale=9576
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***

Am I missing a setting for mcuboot that would cause it to not properly read the jedec id of the spi flash? Please note, this is a spi flash, not a qspi flash.

Thanks,

Mike Norton

prj_v2.4.1.conf

[AHaug]

Hi,

This issue looks like the first issue reported at https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/config_and_build/bootloaders_and_dfu/bootloader_external_flash.html#troubleshooting

What I suspect is that you see the changes in how image management, among other things, has been included within configurations rather than being required as code in your project.

For instance as shown here in this repository written by a colleague of mine containing multiple minimal bootloader samples:

Note the difference in between main.c from v2.2.0 and v2.3.0 tags of the mcuboot_smp_ble sample (the complete changelog can be seen here).

Could you investigate the differences and see if applying the changes allows you to migrate your project from v2.2.0 to v2.3.0? For v2.4.0 there might be other changes that the repository I mention does not consider as the samples here are only tested for v2.2.0 and v2.3.0 of NCS

Kind regards,
Andreas

[mnor]

I am aware of the issue reported at https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/config_and_build/bootloaders_and_dfu/bootloader_external_flash.html#troubleshooting.

I have applied the changes but am still seeing the same initial error from mcuboot:

E: Device id 00 00 00 does not match config 1f 45 08

[AHaug]

Hi, 

Could you tell me more about your hardware and setup? Is it a regular nRF52800DK or is it a custom board? 

Could you supply me with the overlay files if any?

Kind regards,
Andreas