<?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: LS1043a: invalid SECMON state at boot in QorIQ</title>
    <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1578219#M11258</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;Were you able to make any progress on this? I am seeing similar behavior on ls1046a where SECMON is in non-secure state at startup.&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jan 2023 00:52:52 GMT</pubDate>
    <dc:creator>abhkr24</dc:creator>
    <dc:date>2023-01-06T00:52:52Z</dc:date>
    <item>
      <title>LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763793#M6245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently working&amp;nbsp;with a LS1043a based platform (&lt;A href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fmicrosys.de%2Fproducts%2Fsystem-on-modules%2Fqoriqr-armr-architecture%2Fmiriactm-mpx-ls1043a%2F" rel="nofollow" target="_blank"&gt;miriac™ MPX-LS1043A&lt;/A&gt;&amp;nbsp;) with no possibility today to solder a JTAG connector.&amp;nbsp; I'm using QorIQ SDK2.0 to perform a SD boot with SPL binary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dumping SECMON HPSR register soon after ISBC boot in SPL, the reported SSM_STATE is "non-secure":&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;=&amp;gt; md.b 0x1e90014 4&lt;BR /&gt;01e90014: 80 00 0b 00&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;(NOTE: This is the log&amp;nbsp;of&amp;nbsp;a board with some fused programmed so showing OTPMK is non zero... But I have the exactly same behavior with the same platform without any fuse programmed. Then, before&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;permanently programming OTPMK fuses I payed attention to SFP_SVHESR indicating all "0"&amp;nbsp;&lt;/SPAN&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I was expecting SECMON to be in CHECK state before starting SPL&lt;/STRONG&gt;. Looking at SECMON's state machine the transition from CHECK to NON-SECURE may occur in case of External Boot or in case of Hardware Security Violation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is there any other reason for this transition to happen during BROM execution ?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logging all SECMON status registers, I cannot find trace of any "security violation".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is SD boot considered as an "External Boot" on LS1043a ?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure about all PBL and RCW stuff done for this platform so that I provide&amp;nbsp;below an abstract of u-boot config files in case something obvious can be found that may&amp;nbsp;explain this SECMON scenario:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;PBI commands embedded in my SPL image:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;#Configure Scratch register&lt;BR /&gt;09570600 00000000&lt;BR /&gt;09570604 10000000&lt;BR /&gt;#Alt base register&lt;BR /&gt;09570158 00001000&lt;BR /&gt;#Disable CCI barrier tranaction&lt;BR /&gt;09570178 0000e010&lt;BR /&gt;09180000 00000008&lt;BR /&gt;#USB PHY frequency sel&lt;BR /&gt;09570418 0000009c&lt;BR /&gt;0957041c 0000009c&lt;BR /&gt;09570420 0000009c&lt;BR /&gt;#flush PBI data&lt;BR /&gt;096100c0 000fffff&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;and&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;RCW values embedded in my SPL image:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;#PBL preamble and RCW header&lt;BR /&gt;aa55aa55 01ee0100&lt;BR /&gt;# RCW&lt;BR /&gt;0810000e 0a000000 00000000 00000000&lt;BR /&gt;33550002 00000002 60107000 c1002000&lt;BR /&gt;00000000 00000000 00000000 01036ffc&lt;BR /&gt;20004505 00001200 00000096 00000001&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any useful feedback,&lt;/P&gt;&lt;P&gt;Alexandre.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 May 2018 08:08:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763793#M6245</guid>
      <dc:creator>alexandreberder</dc:creator>
      <dc:date>2018-05-17T08:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763794#M6246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alexandre,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you sure the LS1043A on this board is the encrypted version, which includes the security features?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2018 19:34:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763794#M6246</guid>
      <dc:creator>jeffsteinheider</dc:creator>
      <dc:date>2018-05-18T19:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763795#M6247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/jeffsteinheider"&gt;jeffsteinheider&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;how would we check for the presence of such "security" features ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 07:25:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763795#M6247</guid>
      <dc:creator>vsiles</dc:creator>
      <dc:date>2018-05-22T07:25:12Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763796#M6248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are a couple of ways.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the part number is readable on the top of the SoC - LS1043AS&lt;STRONG&gt;E&lt;/STRONG&gt;.&amp;nbsp; The&amp;nbsp;&lt;STRONG&gt;E&amp;nbsp;&lt;/STRONG&gt;indicates that the device supports encryption and security, or if it is&amp;nbsp;&lt;STRONG&gt;N&lt;/STRONG&gt; then the device does not support security features.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also check this register in the device:&lt;/P&gt;&lt;P&gt;System Version Register (DCFG_CCSR_SVR)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will find documentation on this register in the reference manual.Section 12.3.10.&lt;/P&gt;&lt;P&gt;This is often printed out in either u-boot or linux during boot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Microsys should also be able to tell you the part number on your board.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 17:03:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763796#M6248</guid>
      <dc:creator>jeffsteinheider</dc:creator>
      <dc:date>2018-05-22T17:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763797#M6249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/jeffsteinheider"&gt;jeffsteinheider&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On our platform&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;DCFG_CCSR_SVR is with&amp;nbsp;0x8792_0610 thus indicating VAR_PER=0x06&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Such value&amp;nbsp;is not documented on latest available LS1043ARM, but according to Microsys support this indeed corresponds to LS1043a with encrypted version.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2018 05:55:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763797#M6249</guid>
      <dc:creator>alexandreberder</dc:creator>
      <dc:date>2018-05-23T05:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763798#M6250</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/jeffsteinheider"&gt;jeffsteinheider&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're now 100% sure LS1043A chip is the encrypted version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, to come back to original questions:&amp;nbsp;&lt;STRONG&gt;how can we investigate&amp;nbsp;this SECMON transition to "Non-Secure" state, so soon at startup&lt;/STRONG&gt; ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2018 09:39:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/763798#M6250</guid>
      <dc:creator>alexandreberder</dc:creator>
      <dc:date>2018-05-24T09:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1578219#M11258</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Were you able to make any progress on this? I am seeing similar behavior on ls1046a where SECMON is in non-secure state at startup.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 00:52:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1578219#M11258</guid>
      <dc:creator>abhkr24</dc:creator>
      <dc:date>2023-01-06T00:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1585654#M11280</link>
      <description>&lt;P&gt;Did you program the OTPMK, SRK, and DRV? All must be programmed for secure boot.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 17:46:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1585654#M11280</guid>
      <dc:creator>stadium_aquino</dc:creator>
      <dc:date>2023-01-19T17:46:18Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1585656#M11281</link>
      <description>&lt;P&gt;I programmed the SRK and the OTPMK. But not the DRV. Will try that later today.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 17:48:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1585656#M11281</guid>
      <dc:creator>abhkr24</dc:creator>
      <dc:date>2023-01-19T17:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a: invalid SECMON state at boot</title>
      <link>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1585775#M11283</link>
      <description>&lt;P&gt;Programmed the DRV fuse. But SECMON still not in check state. Same error continues.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 00:27:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/LS1043a-invalid-SECMON-state-at-boot/m-p/1585775#M11283</guid>
      <dc:creator>abhkr24</dc:creator>
      <dc:date>2023-01-20T00:27:08Z</dc:date>
    </item>
  </channel>
</rss>

