One firmware compatible with 2 different external flash models.

RE: One firmware compatible with 2 different external flash models.

Anthony Yuan — Sun, 07 Apr 2024 02:48:13 GMT

Hi Hieu,

Got it and many thanks for the update.

RE: One firmware compatible with 2 different external flash models.

Hieu — Tue, 02 Apr 2024 23:05:05 GMT

Hi Anthony,

My apology, but my previous answer appears to be incorrect.

There is a Kconfig option that let the application to discover the parameters of the external flash device on runtime, and therefore doesn't require the jedec-id declared. It CONFIG_SPI_NOR_SFDP_RUNTIME.

I tested and it worked with the AT45 Flash Driver sample, modified for the nRF52840 DK.

I would like to test if DFU also work with this Kconfig too but couldn't get to it yet. I am not sure when I can return to that, so I opt to inform you earlier than later.

Sorry again for my lacking answer.

Regards,

Hieu

RE: One firmware compatible with 2 different external flash models.

Hieu — Thu, 22 Feb 2024 12:42:01 GMT

No problem. Happy to help 🙂

RE: One firmware compatible with 2 different external flash models.

Anthony Yuan — Thu, 22 Feb 2024 02:59:43 GMT

Understood, Many thanks Hieu.

RE: One firmware compatible with 2 different external flash models.

Hieu — Wed, 21 Feb 2024 17:04:50 GMT

**Update: this answer is incorrect. Please see my later answer, where I learned of a new Kconfig that helps..

Hi Anthony,

I have looked into it, and unless you are using the external flash for your own data, I cannot find a way to use only one firmware for it either.

If you use external flash for your own data, you might be able to declare both flash devices on the same DeviceTree. You will have to implement your own flash access and memory management, because if you use any built-in support, the OS will try to initialize the flash device, and runs into error. To detect which flash device should be used, you can either just ignore the device that fail to initialize, or setup the hardware to have a pin tied to ground or logic high to differentiate the two hardware models.

I don't imagine this approach is of interested if you are using QSPI flash though.

By the way, if you are using 2.4.0, please consider moving to 2.4.3, where a few bugs are fixed. The change log can be found in the Release Notes.

Regards,

Hieu