NCS DFU Supported External Flash Devices

RE: NCS DFU Supported External Flash Devices

Bryan — Tue, 23 May 2023 13:55:36 GMT

The missing items were:

In child_image/mcuboot/boards/o1-agg-nrf52833.conf
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_SPI_NRFX_RAM_BUFFER_SIZE=32
CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y
CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y

In prj.conf
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_SPI_NRFX_RAM_BUFFER_SIZE=32
CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y

Explicitly setting the flash layout page size fixed it.

PS C:\Virtuix\nordic\myapps\hello_world_dfu_833DK_ext_flash\build> west build -t partition_manager_report
-- west build: running target partition_manager_report
[1/1] cmd.exe /C "cd /D C:\Virtuix\nordic\myapps\hello_world_.../myapps/hello_world_dfu_833DK_ext_flash/build/partitions.yml" external_flash (0x100000 - 1024kB):
+-------------------------------------------+
| 0x0: mcuboot_secondary (0x71000 - 452kB) |
| 0x71000: external_flash (0x8f000 - 572kB) |
+-------------------------------------------+

flash_primary (0x80000 - 512kB):
+-------------------------------------------------+
| 0x0: mcuboot (0xf000 - 60kB) |
+---0xf000: mcuboot_primary (0x71000 - 452kB)-----+
| 0xf000: mcuboot_pad (0x200 - 512B) |
+---0xf200: mcuboot_primary_app (0x70e00 - 451kB)-+
| 0xf200: app (0x70e00 - 451kB) |
+-------------------------------------------------+

sram_primary (0x20000 - 128kB):
+--------------------------------------------+
| 0x20000000: sram_primary (0x20000 - 128kB) |
+--------------------------------------------+

PS C:\Virtuix\nordic\myapps\hello_world_dfu_833DK_ext_flash\build>

Kenneth - Thanks for all the help! Nordic's next dev academy should be DFU!

I have attached the working project.

devzone.nordicsemi.com/.../8551.hello_5F00_world_5F00_dfu_5F00_833DK_5F00_ext_5F00_flash.zip

RE: NCS DFU Supported External Flash Devices

Bryan — Wed, 10 May 2023 13:32:35 GMT

I just read through Hakon's response to my private case. Now I see what you mean. I will test it and update everyone.

RE: NCS DFU Supported External Flash Devices

Bryan — Wed, 10 May 2023 13:04:35 GMT

Kenneth,

My private case is for our custom board that has two spi busses, so it is more complex. This one is just to get the basic external flash DFU working.

RE: NCS DFU Supported External Flash Devices

Kenneth — Wed, 10 May 2023 09:32:46 GMT

Hello,

I can see you are getting help in a private case. I suggest you continue there, but please share your findings for anyone experiencing the same that find this public case.

Kenneth

RE: NCS DFU Supported External Flash Devices

Bryan — Tue, 09 May 2023 19:58:51 GMT

Kenneth,

Once again I was switched off this and onto something else. I never got to test adding "chosen". Without "chosen" it is still using internal flash.

I have upgraded to the latest NCS 2.3.0. I am back to getting this output when it boots.

*** Booting Zephyr OS build v3.2.99-ncs2 ***
I: Starting bootloader
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0xf000
*** Booting Zephyr OS build v3.2.99-ncs2 ***
Hello World 1! nrf52833dk_nrf52833

Since it had been awhile, I reconfirmed that the https://github.com/nrfconnect/sdk-zephyr/tree/main/tests/drivers/flash test still works.

from the file ncs\v2.3.0\bootloader\mcuboot\boot\bootutil\src\swap_move.c

num_sectors_pri = boot_img_num_sectors(state, BOOT_PRIMARY_SLOT);
num_sectors_sec = boot_img_num_sectors(state, BOOT_SECONDARY_SLOT);
if ((num_sectors_pri != num_sectors_sec) &&
(num_sectors_pri != (num_sectors_sec + 1))) {
BOOT_LOG_WRN("Cannot upgrade: not a compatible amount of sectors");
return 0;
}

However, if I look at the partition manager report it shows primary and secondary are exactly the same size.

PS C:\Virtuix\nordic\myapps\hello_world_dfu_833DK_ext_flash\build> west build -t partition_manager_report
-- west build: running target partition_manager_report
[1/1] cmd.exe /C "cd /D C:\Virtuix\nordic\myapps\hello_w...ps/hello_world_dfu_833DK_ext_flash/build/partitions.yml"
external_flash (0x100000 - 1024kB):
+-------------------------------------------+
| 0x0: mcuboot_secondary (0x71000 - 452kB) |
| 0x71000: external_flash (0x8f000 - 572kB) |
+-------------------------------------------+

flash_primary (0x80000 - 512kB):
+-------------------------------------------------+
| 0x0: mcuboot (0xf000 - 60kB) |
+---0xf000: mcuboot_primary (0x71000 - 452kB)-----+
| 0xf000: mcuboot_pad (0x200 - 512B) |
+---0xf200: mcuboot_primary_app (0x70e00 - 451kB)-+
| 0xf200: app (0x70e00 - 451kB) |
+-------------------------------------------------+

sram_primary (0x20000 - 128kB):
+--------------------------------------------+
| 0x20000000: sram_primary (0x20000 - 128kB) |
+--------------------------------------------+

PS C:\Virtuix\nordic\myapps\hello_world_dfu_833DK_ext_flash\build>

What I am missing?

devzone.nordicsemi.com/.../8463.hello_5F00_world_5F00_dfu_5F00_833DK_5F00_ext_5F00_flash.zip

RE: NCS DFU Supported External Flash Devices

Kenneth — Thu, 23 Mar 2023 08:41:42 GMT

Hello,

You should use both alias and chosen, ref:

/ { 	
	aliases 
	{ spi-flash0 = &is25lp080d; }; 
	chosen 
	{ nordic,pm-ext-flash = &is25lp080d; }; 
};

Looks like nRF52840DK already have the spi-flash0 defined in the board file:
https://github.com/nrfconnect/sdk-zephyr/blob/main/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts#L129

Well spotted this was the problem!

Kenneth

RE: NCS DFU Supported External Flash Devices

Bryan — Tue, 21 Mar 2023 17:39:32 GMT

Kenneth,

I keep getting shifted onto other tasks. Sorry for the delay.

CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y was not the root cause.

I ported the https://github.com/nrfconnect/sdk-zephyr/tree/main/tests/drivers/flash project to the nRF52833DK with the external SPI NOR Flash wired to it and got it working.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Running TESTSUITE flash_driver
===================================================================
START - test_read_unaligned_address
PASS - test_read_unaligned_address in 0.047 seconds
===================================================================
TESTSUITE flash_driver succeeded

------ TESTSUITE SUMMARY START ------

SUITE PASS - 100.00% [flash_driver]: pass = 1, fail = 0, skip = 0, total = 1 duration = 0.047 seconds
- PASS - [flash_driver.test_read_unaligned_address] duration = 0.047 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
PROJECT EXECUTION SUCCESSFUL

I can confirm it is working by simply lifting the power pin to the SPI NOR Flash.

E: Device id ff ff ff does not match config 9d 60 14
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Running TESTSUITE flash_driver
===================================================================

Assertion failed at ../src/main.c:59: flash_driver_setup: device_is_ready(flash_dev) is false

START - test_read_unaligned_address
FAIL - test_read_unaligned_address in 0.001 seconds
===================================================================
TESTSUITE flash_driver failed.

------ TESTSUITE SUMMARY START ------

SUITE FAIL - 0.00% [flash_driver]: pass = 0, fail = 1, skip = 0, total = 1 duration = 0.001 seconds
- FAIL - [flash_driver.test_read_unaligned_address] duration = 0.001 seconds

------ TESTSUITE SUMMARY END ------

===========================

I now have the nRF52833DK with external SPI NOR flash working, too. The key was to use the exact same nrf52833dk_nrf52833.overlay file from the flash test above in /boards and /child_image/mcuboot/boards.

The only difference between what works and what caused issues is the first five lines in the overlay file.

from the flash test that works

/ {
aliases {
spi-flash0 = &is25lp080d;
};
};

what I was trying to use, which was based on the nRF52840DK external flash overlay file.
/ {
chosen {
nordic,pm-ext-flash = &is25lp080d;
};
};

Kenneth - Two final questions.

1. I am not understanding what it hated about nordic,pm-ext-flash = &is25lp080d; This is the exact syntax used in the hello_world_dfu_840DK_ext_flash project overlay files.

2. I used spi-flash0 in the flash test because it was the exact same syntax as /boards/nrf52840dk_mx25l51245g.overlay

I honestly didn't expect it to work in the DFU project. It seems that spi-flash0 is standard label in Zephyr to define a external spi flash device. It is used in a lot of zephyr/boards/*.dts files. Am I understanding this correctly?

I have attached all three of the projects for everyone's reference.

devzone.nordicsemi.com/.../hello_5F00_world_5F00_dfu_5F00_840DK_5F00_ext_5F00_flash.zip

devzone.nordicsemi.com/.../6153.flash.zip devzone.nordicsemi.com/.../hello_5F00_world_5F00_dfu_5F00_833DK_5F00_ext_5F00_flash.zip

RE: NCS DFU Supported External Flash Devices

Kenneth — Tue, 14 Mar 2023 10:27:45 GMT

Hello,

I found 4 other cases with similar error message, I am linking it here it in case it can be of help?
MCUBoot runtime error: "Cannot upgrade: not a compatible amount of sectors" with external flash on nrf9160
MCUBoot, Zephyr, and static partition manager
MCUBoot fails to load if using CMake Overlay Config
Device Firmware Update (DFU) with MCUBoot bootloader showing Failed reading sectors; BOOT_MAX_IMG_SECTORS=128 - too small?

Wild guess, can you try:
CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y

Kenneth

RE: NCS DFU Supported External Flash Devices

Bryan — Mon, 13 Mar 2023 19:35:22 GMT

Kenneth,

I took the flash app you provided and modified it for the nRF52833DK with the ISSI is25lp080d SPI NOR flash. After a lot of experimental changes it is now passing. This shows that the flash is connected properly and can be read/written. I attached flash.zip for reference for everyone.

https://github.com/nrfconnect/sdk-zephyr/tree/main/tests/drivers/flash

ncs\v2.2.0\zephyr\tests\drivers\flash

The key modifications were:

* delete testcase.yaml

* Modify the contents of the overlay file.

/ {

aliases {

spi-flash0 = &is25lp080d;

};

&pinctrl {

spi1_default: spi1_default {

group1 {

psels = <NRF_PSEL(SPIM_SCK, 0, 23)>,

<NRF_PSEL(SPIM_MOSI, 0, 21)>,

<NRF_PSEL(SPIM_MISO, 0, 22)>;

};

spi1_sleep: spi1_sleep {

group1 {

psels = <NRF_PSEL(SPIM_SCK, 0, 23)>,

<NRF_PSEL(SPIM_MOSI, 0, 21)>,

<NRF_PSEL(SPIM_MISO, 0, 22)>;

low-power-enable;

};

&spi1 {

compatible = "nordic,nrf-spim"; <<<<<<<<<<<<<<<<<< added

status = "okay";

cs-gpios = <&gpio0 20 GPIO_ACTIVE_LOW>;

pinctrl-0 = <&spi1_default>;

pinctrl-1 = <&spi1_sleep>;

pinctrl-names = "default", "sleep";

is25lp080d:is25lp080d@0 {

// developer.nordicsemi.com/.../jedec,spi-nor.html

compatible = "jedec,spi-nor";

reg = <0>;

spi-max-frequency = <0x50000000>;

// see is25lp080d datasheet Section 8.29 for jedec-id

jedec-id = [ 9D 60 14 ]; <<<<<<<<<<<<<<<<<< added

size = <8388608>; // 8 Mbits

};

Notes from getting it working.

1. Required added compatible = "nordic,nrf-spim";

2. The jedec-id is required. I modified it to an incorrect value and the test fails. Confirm it is correct.

3. The sfdp-bfp field (used on the nRF52840DK external flash example) is not required (at least for this part) and is grossly over complex to implement. If you get a single bit incorrect, it won't work.

------ TESTSUITE SUMMARY START ------

SUITE PASS - 100.00% [flash_driver]: pass = 1, fail = 0, skip = 0, total = 1 duration = 0.047 seconds
- PASS - [flash_driver.test_read_unaligned_address] duration = 0.047 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
PROJECT EXECUTION SUCCESSFUL

=================================================================

Now that I know the flash is hooked up correctly and can talk to it, I integrated they overlay file it into my nRF52833 DK -based "hello world dfu" project.

The only modification I did was to both (/boards and /child_image/mcuboot/boards) both nrf52833dk_nrf52833.overlay files to use the below for dfu

/ {

chosen {

nordic,pm-ext-flash = &is25lp080d;

};

Instead of the below used for the flash test

/ {

aliases {

spi-flash0 = &is25lp080d;

};

When I flash the board, I got this error.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
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: 0xf000
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello World 1! nrf52833dk_nrf52833

If I increase CONFIG_BOOT_MAX_IMG_SECTORS=512, one error goes away.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting bootloader
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0xf000
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello World 1! nrf52833dk_nrf52833

CONFIG_BOOT_MAX_IMG_SECTORS is a setting from the nrf52840 DK serial DFU external flash example that I based this project on.

https://github.com/simon-iversen/sdk-zephyr/tree/serial_dfu_ext_flash_hello_world/samples/hello_world

1. I can not find a reference to what CONFIG_BOOT_MAX_IMG_SECTORS does and how it interacts with other settings.

2. "not a compatible amount of sectors". What is a "compatible amount of sectors"? Please explain.

3. I thought the source of the issues is the fact that I don't have a pm_static.yaml like in the above serial dfu with external flash example I reference above. Contents of pm_static.yaml

external_flash:
address: 0xf4000
end_address: 0x800000
region: external_flash
size: 0x70c000

mcuboot_secondary:
address: 0x00000
device: MX25R64
end_address: 0xf4000
region: external_flash
size: 0xf4000

This matches the output of:

PS C:\Virtuix\nordic\myapps\hello_world\build> west build -t partition_manager_report
-- west build: running target partition_manager_report
[1/1] cmd.exe /C "cd /D C:\Virtuix\nordic\myapps\hello_world\b...put C:/Virtuix/nordic/myapps/hello_world/build/partitions.yml" external_flash (0x800000 - 8192kB):
+---------------------------------------------+
| 0x0: mcuboot_secondary (0xf4000 - 976kB) |
| 0xf4000: external_flash (0x70c000 - 7216kB) |
+---------------------------------------------+

flash_primary (0x100000 - 1024kB):
+-------------------------------------------------+
| 0x0: mcuboot (0xc000 - 48kB) |
+---0xc000: mcuboot_primary (0xf4000 - 976kB)-----+
| 0xc000: mcuboot_pad (0x200 - 512B) |
+---0xc200: mcuboot_primary_app (0xf3e00 - 975kB)-+
| 0xc200: app (0xf3e00 - 975kB) |
+-------------------------------------------------+

sram_primary (0x40000 - 256kB):
+--------------------------------------------+
| 0x20000000: sram_primary (0x40000 - 256kB) |
+--------------------------------------------+

I then attempted to create my own pm_static.yaml

external_flash:

address: 0x71000

end_address: 0x100000

region: external_flash

size: 0x8f000

mcuboot_secondary:

address: 0x00000

device: is25lp080d

end_address: 0x8f000

region: external_flash

size: 0x8f000

Again based off the output of

PS C:\Virtuix\nordic\myapps\hello_world_dfu\build_nrf52833dk_nrf52833> west build -t partition_manager_report
-- west build: running target partition_manager_report
[1/1] cmd.exe /C "cd /D C:\Virtuix\nordic\myapps\hello_world_...pps/hello_world_dfu/build_nrf52833dk_nrf52833/partitions.yml"
external_flash (0x100000 - 1024kB):
+-------------------------------------------+
| 0x0: mcuboot_secondary (0x71000 - 452kB) |
PS C:\Virtuix\nordic\myapps\hello_world_dfu\build_nrf52833dk_nrf52833> west build -t partition_manager_report
-- west build: running target partition_manager_report
[1/1] cmd.exe /C "cd /D C:\Virtuix\nordic\myapps\hello_world_...pps/hello_world_dfu/build_nrf52833dk_nrf52833/partitions.yml"
external_flash (0x100000 - 1024kB):
+-------------------------------------------+
| 0x0: mcuboot_secondary (0x71000 - 452kB) |
| 0x71000: external_flash (0x8f000 - 572kB) |
+-------------------------------------------+

flash_primary (0x80000 - 512kB):
+-------------------------------------------------+
| 0x0: mcuboot (0xf000 - 60kB) |
+---0xf000: mcuboot_primary (0x71000 - 452kB)-----+
| 0xf000: mcuboot_pad (0x200 - 512B) |
+---0xf200: mcuboot_primary_app (0x70e00 - 451kB)-+
| 0xf200: app (0x70e00 - 451kB) |
+-------------------------------------------------+

sram_primary (0x20000 - 128kB):
+--------------------------------------------+
| 0x20000000: sram_primary (0x20000 - 128kB) |
+--------------------------------------------+

I still get the same output.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting bootloader
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0xf000
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello World 1! nrf52833dk_nrf52833

There is something I am simply not understanding.

devzone.nordicsemi.com/.../hello_5F00_world_5F00_dfu_5F00_13_5F00_3_5F00_23.zip

devzone.nordicsemi.com/.../flash.zip

RE: NCS DFU Supported External Flash Devices

Kenneth — Fri, 10 Mar 2023 11:31:31 GMT

For testing can you first try to make the flash test driver to work?

https://github.com/nrfconnect/sdk-zephyr/tree/main/tests/drivers/flash

In your case that want to use spi you can find these two files relevant:
boards/nrf52840dk_flash_spi.conf
boards/nrf52840dk_mx25r_high_perf.overlay
(remove the mxicy,mx25r-power-mode = "high-performance"; in your case from the .overlay)

By modifying the .overlay file you should hopefully relatively quickly find configuration that works.

RE: NCS DFU Supported External Flash Devices

Bryan — Thu, 09 Mar 2023 22:34:54 GMT

I have wired up the SPI NOR flash and added the sfdp-bfp into both overlay files

* boards\nrf52833dk_nrf52833.overlay

* child_image\mcuboot\boards\nrf52833dk_nrf52833.overlay

However, I am still seeing issues around the conf settings in prj.conf and child_image\mcuboot\boards\nrf52833dk_nrf52833.conf

CONFIG_FLASH=y

CONFIG_SPI=y

CONFIG_SPI_NOR=y

warning: SPI_NOR (defined at drivers/flash/Kconfig.nor:4) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: DT_HAS_JEDEC_SPI_NOR_ENABLED (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up SPI_NOR in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

It still builds, but when it boots...

*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting bootloader
W: Failed reading sectors; BOOT_MAX_IMG_SECTORS=256 - too small?
W: Cannot upgrade: not a compatible amount of sectors
E: Unable to determine flash sector of the image trailer
E: Image in the primary slot is not valid!
E: Unable to find bootable image

RE: NCS DFU Supported External Flash Devices

Bryan — Thu, 09 Mar 2023 15:26:37 GMT

Kenneth,

You are a genius! I started digging when you focused me on MULTITHREADING and I found this reference online in a prj.conf file. This resolved the error.

# If you don't add this when setting CONFIG_SPI=y, you'll get a lot of undefined references
# from the nrfx spim driver E.G. "undefined reference to `z_impl_k_sleep'"
CONFIG_MULTITHREADING=y

RE: NCS DFU Supported External Flash Devices

Kenneth — Thu, 09 Mar 2023 14:51:15 GMT

I did not have time to look into this today, and I am out of office tomorrow. The undefined reference to `z_impl_k_sem_give' error seems to be related to MULTITHREADING is not enabled? Maybe try to delete your build folder and build again.

Kenneth

RE: NCS DFU Supported External Flash Devices

Bryan — Wed, 08 Mar 2023 23:21:09 GMT

I finally am getting back to this ticket. Here is what I have done.

1. The "hello world" DFU over BLE using internal flash is working on the nRF52833 DK.

2. I then ported the project to the nRF52840 DK to use it's external QSPI flash. This is also working.

3. Now I am trying to add an external SPI flash device on a breakout board to the nRF52833 DK to prove it will work. The SPI NOR flash I am using is the ISSI IS25LP080D.
www.issi.com/.../25LP-WP080D-040D-020D.pdf

From item #2 above I modified...

Both of these overlay files update the SPI bus (identical content in both files)

/boards/nrf52833dk_nrf52833.overlay
/child_image/mcuboot/boards/nrf52833dk_nrf52833.overlay

Both of the these conf files have these lines added to switch from QSPI to SPI

prj.conf
/child_image/mcuboot/boards/nrf52833dk_nrf52833.conf

# Additions for DFU external flash

CONFIG_FLASH=y

CONFIG_SPI=y

CONFIG_SPI_NOR=y

I am seeing two things that are odd. CONFIG_SPI_NOR in both .conf files has the red/orange squiggly lines under it. When I highlight it says:

CONFIG_SPI_NOR was assigned the value y, but got the value n. Missing dependencies:
DT_HAS_JEDEC_SPI_NOR_ENABLED

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html and searching for "CONFIG_SPI_NOR" shows does have DT_HAS_JEDEC_SPI_NOR_ENABLED as a dependency.

However in my build directory both of the .config files shows CONFIG_DT_HAS_JEDEC_SPI_NOR_ENABLED=y

build_nrf52833dk_nrf52833/mcuboot/zephyr/.config
build_nrf52833dk_nrf52833/zephyr/.config

I suspect this is the root cause of the build error I am getting, but the message doesn't give any real detail.
c:/users/bryan/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr/drivers/spi/libdrivers__spi.a(spi_nrfx_spi.c.obj): in function `k_sem_give':
C:\Virtuix\nordic\myapps\hello_world_dfu\build_nrf52833dk_nrf52833\mcuboot\zephyr\include\generated\syscalls\kernel.h:1071: undefined reference to `z_impl_k_sem_give'

I have attached my hello_world_dfu project for reference. The build output log is saved in the root directory (build_output.txt). I appreciate any help!

devzone.nordicsemi.com/.../hello_5F00_world_5F00_dfu.zip

RE: NCS DFU Supported External Flash Devices

Bryan — Wed, 01 Mar 2023 16:04:00 GMT

Thanks for the feedback. I think spinning a breakout board and testing with the nRF52833 DK is the best way to go, too.

RE: NCS DFU Supported External Flash Devices

Kenneth — Wed, 01 Mar 2023 15:51:51 GMT

I think getting a breakout board as suggested is a good option to debug/verify this works. The breakout board can be done with a different package type.

That said, I do believe you should be able to make this work. The spi_nor driver is pretty generic.

In terms of how to switch between internal flash, spi flash and qspi flash you can find the driver test for the flash module useful:
https://github.com/nrfconnect/sdk-zephyr/tree/main/tests/drivers/flash

In your case that want to use spi you can find these two files relevant:
boards/nrf52840dk_flash_spi.conf
boards/nrf52840dk_mx25r_high_perf.overlay

By modifying the .overlay file you should hopefully relatively quickly find configuration that works.

Edit, here are the properties that can be set:
https://github.com/nrfconnect/sdk-zephyr/blob/main/dts/bindings/mtd/jedec%2Cspi-nor.yaml
https://github.com/nrfconnect/sdk-zephyr/blob/main/dts/bindings/mtd/jedec%2Cspi-nor-common.yaml

"Properties supporting Zephyr spi-nor flash driver (over the Zephyr SPI API) control of serial flash memories using the standard M25P80-based command set."

Kenneth

RE: NCS DFU Supported External Flash Devices

nordicator_prim3 — Tue, 28 Feb 2023 18:16:15 GMT

Hi Bryan,

This is not an answer to your question but just a tip on what else to look for when trying to find a compatible external flash.

- Make sure if you're going to use QSPI that the quad enable bit is at one of the supported registers. The options are shown in "jedec,jesd216.yaml" dts binding file. The options are: "S2B1v1", "S1B6", "S2B7", "S2B1v4", "S2B1v5", "S2B1v6" where S1B6 would mean the quad enable bit is bit 6 of status register 2. The description in the dts binding file has more information on this.

- Make sure that the read and write commands the the flash driver uses are supported by the chip you're looking at. You'll have to dig through the flash driver or just make sure that the read and write commands on the new chip are the same ones used in the MX25r64.

Just thought I would chime in with those tips - it was very rough trying to find an external flash chip having had no experience with NOR chips before needing to look for one. That and understanding how the flash drivers from nordic/zephyr work and what their limitations were. I would be scared of spinning up a board without verifying it as you said. Is it an option to get a SOP8 breakout to put the chip on to hook up to a devkit?

https://www.digikey.com/en/products/detail/adafruit-industries-llc/1212/5022800?utm_adgroup=Adapter%2C%20Breakout%20Boards&utm_source=google&utm_medium=cpc&utm_campaign=Shopping_Product_Prototyping%2C%20Fabrication%20Products_NEW&utm_term=&utm_content=Adapter%2C%20Breakout%20Boards&gclid=Cj0KCQiA6fafBhC1ARIsAIJjL8mOXW9DWxr5odwyvOOLTX1pvAM80a7WfErRodEIx46s3zjYh15Hqq4aAsnqEALw_wcB

Based on what you said about your board being small I'm guessing you're using the USON form factor though, so that's gonna be hard to find a breakout board for (and to solder).

Good luck!