<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ATF - Black screen when Secure Boot enabled (SB_EN=1) fixed by setting NXP_ROM_RSVD to 0x8000 in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2196898#M16257</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The issue isn't related to the chip date(neither recent nor old) , there is a t&lt;SPAN&gt;here is a known issue for LS1046a/43a since LSDK21.08. the patch you applied is the correct one as workaround for the mentioned issue.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 31 Oct 2025 22:51:55 GMT</pubDate>
    <dc:creator>Oswalag</dc:creator>
    <dc:date>2025-10-31T22:51:55Z</dc:date>
    <item>
      <title>ATF - Black screen when Secure Boot enabled (SB_EN=1) fixed by setting NXP_ROM_RSVD to 0x8000</title>
      <link>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2188371#M16218</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've an issue with an ls1043a soc. When the secure boot is enabled (SB_EN=1 in rcw) with the fuse blown with the keys (but ITS=0), the console stay black...&lt;/P&gt;&lt;P&gt;When debugging with a Jtag device, it comes out that the i/esbc is stuck in a function that looks like a panic: "0x1d0: b 0x1d0". The Scratch status register seems not initialised (random or 0 value).&lt;/P&gt;&lt;P&gt;And after few days of debugging and tries, I finally fixed the issue by patching the file "plat/nxp/soc-ls1043a/soc.def", changing the value of "NXP_ROM_RSVD" to"0x8000" instead of "0x5900". Actually the same change as the one done to the ls1046a in the commit hash&amp;nbsp;41556d6b428d2ae4b265bb8a87125dfb3f5bd307 (on the qoriq-atf repo)...&lt;/P&gt;&lt;P&gt;So, my guess is that the ls1043a soc had his ROM code updated "recently" with one similar to the ls1046a and give an issue when booting with SB_EN=1 only (no problems if the secure boot is not enabled thought).... The soc we have was bought 3 weeks ago, so it's a recent one: LS1043AXE8QQB-SBRG2206-1N96N.&lt;/P&gt;&lt;P&gt;As I've also an ls1046a chip, if I revert that commit for the ls1046a def, the same behaviour as the ls1043a happens: Black screen and stuck at (almost) the same location with the same assembly code (panic).&lt;/P&gt;&lt;P&gt;So, could someone at NXP could just confirm me my guess is right and the issue is really fixed ?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2025 13:51:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2188371#M16218</guid>
      <dc:creator>daviddg</dc:creator>
      <dc:date>2025-10-17T13:51:45Z</dc:date>
    </item>
    <item>
      <title>Re: ATF - Black screen when Secure Boot enabled (SB_EN=1) fixed by setting NXP_ROM_RSVD to 0x8000</title>
      <link>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2189506#M16225</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I'm investigating your issue, I'll update here.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 02:27:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2189506#M16225</guid>
      <dc:creator>Oswalag</dc:creator>
      <dc:date>2025-10-21T02:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: ATF - Black screen when Secure Boot enabled (SB_EN=1) fixed by setting NXP_ROM_RSVD to 0x8000</title>
      <link>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2196898#M16257</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The issue isn't related to the chip date(neither recent nor old) , there is a t&lt;SPAN&gt;here is a known issue for LS1046a/43a since LSDK21.08. the patch you applied is the correct one as workaround for the mentioned issue.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2025 22:51:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2196898#M16257</guid>
      <dc:creator>Oswalag</dc:creator>
      <dc:date>2025-10-31T22:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: ATF - Black screen when Secure Boot enabled (SB_EN=1) fixed by setting NXP_ROM_RSVD to 0x8000</title>
      <link>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2197504#M16261</link>
      <description>Perfect then. Thanks for the investigation and confirmation &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;BR /&gt;&lt;BR /&gt;Is there an official patch somewhere ?</description>
      <pubDate>Mon, 03 Nov 2025 12:24:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/ATF-Black-screen-when-Secure-Boot-enabled-SB-EN-1-fixed-by/m-p/2197504#M16261</guid>
      <dc:creator>daviddg</dc:creator>
      <dc:date>2025-11-03T12:24:46Z</dc:date>
    </item>
  </channel>
</rss>

