<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123620/nrf5340---multi-qspi-flash-chip-models</link><description>I&amp;#39;m working on nRF5340 custom platform (NCS 2.6.1, Zephyr 3.5.99). I use MCUBoot immutable bootloader and external QSPI NOR Flash for slot-1 partition during DFU. 
 This is my working dts overlay configuration for flash model EN25QH64 
 
 On the board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Sep 2025 09:57:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123620/nrf5340---multi-qspi-flash-chip-models" /><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/548469?ContentTypeID=1</link><pubDate>Thu, 11 Sep 2025 09:57:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5bb7b7b6-5982-4105-ac20-f6257782464f</guid><dc:creator>Gabriele</dc:creator><description>&lt;p&gt;The problem can be solved by patching the flash driver (&lt;span&gt;nrf_qspi_nor.c) by testing different JEDEC IDs and then configuring the device for the correct one. The array of allowed JEDEC IDs can be managed as a new parameter in the dts configurator.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/545649?ContentTypeID=1</link><pubDate>Thu, 14 Aug 2025 10:56:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:746fe0e8-b3e0-47d1-8ff0-54db2b4d3844</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Sorry no.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/545645?ContentTypeID=1</link><pubDate>Thu, 14 Aug 2025 10:10:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28fbf97c-d570-4196-9fc8-1fdd6d109a04</guid><dc:creator>Gabriele</dc:creator><description>&lt;p data-start="205" data-end="347"&gt;I see. Would it be possible to address the problem by linking the flash model selection to the logic state of a GPIO input at boot time?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/545639?ContentTypeID=1</link><pubDate>Thu, 14 Aug 2025 09:24:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:86b6498a-fecd-4d55-88ee-1075a274a0a4</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;I am sorry to say, but&amp;nbsp;zephyr and devicetree is very static in this sense, so I am not aware of any way you can dynamically detect and choose which external flash you can use run-time.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/545605?ContentTypeID=1</link><pubDate>Thu, 14 Aug 2025 06:33:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3354c6b1-58c4-41ea-a403-64de4b7ab0db</guid><dc:creator>Gabriele</dc:creator><description>&lt;p&gt;Hi Kenneth, could you please elaborate a bit more on your answer ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/545578?ContentTypeID=1</link><pubDate>Wed, 13 Aug 2025 19:02:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79384684-e09b-48d7-bf9f-0221969fd8c1</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi again,&lt;/p&gt;
[quote user=""]At runtime, the firmware should be able to detect which flash is present (for example, by reading the JEDEC ID) and use the appropriate device.[/quote]
&lt;p&gt;After reading your case again and the above requirement, I am sorry to say but it&amp;#39;s not possible to do what you request.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf5340 - Multi QSPI Flash chip models.</title><link>https://devzone.nordicsemi.com/thread/545367?ContentTypeID=1</link><pubDate>Tue, 12 Aug 2025 11:57:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0baf08b4-11e3-4e82-a235-43863ebc9edc</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Key person is out of office this week, we will look into this next week.&lt;/p&gt;
&lt;p&gt;Sorry for the delay,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>