<?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>How to Modify the JEDEC ID</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118293/how-to-modify-the-jedec-id</link><description>In version 2.9.0, I modified the JEDEC ID. 
 The system is supposed to send a &amp;quot;Deep power- down enter(0xB9)&amp;quot; command after reading the JEDEC ID. 
 However, after the system reads the JEDEC ID, there is no response at all. 
 I have already modified the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 24 Jan 2025 14:23:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118293/how-to-modify-the-jedec-id" /><item><title>RE: How to Modify the JEDEC ID</title><link>https://devzone.nordicsemi.com/thread/519993?ContentTypeID=1</link><pubDate>Fri, 24 Jan 2025 14:23:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6fc1fbdb-6fe4-4acb-82f1-c84a75874843</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Thank you for the update! It may be useful for other encountering similar issues!&lt;/p&gt;
&lt;p&gt;Have a nice weekend!&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to Modify the JEDEC ID</title><link>https://devzone.nordicsemi.com/thread/519906?ContentTypeID=1</link><pubDate>Fri, 24 Jan 2025 02:26:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e00e240-d99c-47cb-9f61-1296c0170b48</guid><dc:creator>SunHuang</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for your reply. I&amp;rsquo;ve found the cause. Although I didn&amp;rsquo;t enable QSPI, I still had to forcibly disable it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to Modify the JEDEC ID</title><link>https://devzone.nordicsemi.com/thread/519890?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2025 23:23:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ece8cc9b-7a1e-458b-9d35-ab72da56c67c</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;What does the log from the nRF say?&lt;/p&gt;
&lt;p&gt;Would it be possible to zip and upload the application that is working in v2.6.1, and the one that is not working in v2.9.0?&lt;/p&gt;
&lt;p&gt;For debugging purposes, does it work if you try to build without sysbuild in v2.9.0? You set this when you create your build configuration, by ticking off &amp;quot;no sysbuild&amp;quot; at the very bottom. Alternatively, if you are building from the command line, you can add the argument --no-sysbuild.&lt;/p&gt;
&lt;p&gt;If this works, it suggests that there is some configuration setup that has changed, that needs some tweaking.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>