<?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: Why does PBI stop after 0x300 bytes? in QorIQ</title>
    <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913529#M8076</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your solution works, thanks a lot!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I don't understand, why it works now. Can you give an explanation, please?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Jun 2019 12:25:15 GMT</pubDate>
    <dc:creator>tmoos</dc:creator>
    <dc:date>2019-06-13T12:25:15Z</dc:date>
    <item>
      <title>Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913527#M8074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to secure-boot from SD card, on a QorIQ T1023. I created a PBI which should do the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Configure CPC as SRAM (256 KiB) and map it to 0xbff0_0000&lt;/LI&gt;&lt;LI&gt;Configure ACS to be at 0xbef4_0000 (i.e. SRAM is part of ACS)&lt;/LI&gt;&lt;LI&gt;Set SCRATCHRW1 to 0xbff3_fffc (which is located within SRAM)&lt;/LI&gt;&lt;LI&gt;Setup SPI (this is legacy - I simply didn't touch it)&lt;/LI&gt;&lt;LI&gt;Copy CSF from SD card into SRAM (starting at ACS+0xfd_7000)&lt;/LI&gt;&lt;LI&gt;Copy U-Boot SPL from SD card into SRAM (starting at ACS+0xfd_8000)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I can monitor the SD card lines with an logic analyzer. What I see is:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The PBI is read from SD card, but only the first 70 bytes or so (i.e. the RCW is read)&lt;/LI&gt;&lt;LI&gt;1,22 ms pause (maybe RCW is being applied?)&lt;/LI&gt;&lt;LI&gt;The PBI is read again from SD card, starting with RCW, but only the first 0x300 bytes.&lt;/LI&gt;&lt;LI&gt;The SoC stops. Nothing more happens.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I wonder that reading the PBI stops, even before the ISBC is started. I attach my binary to this post. It consists of the PBI and the main U-Boot (which comes after the PBI). I copied this binary to my SD card, at offset 0x1000.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you explain what happens?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards, Tanjeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2019 10:49:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913527#M8074</guid>
      <dc:creator>tmoos</dc:creator>
      <dc:date>2019-06-12T10:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913528#M8075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You wrote:&lt;/P&gt;&lt;P&gt;&amp;gt; Configure CPC as SRAM (256 KiB) and map it to 0xbff0_0000&lt;/P&gt;&lt;P&gt;Please use address 0xBFFC0000.&lt;/P&gt;&lt;P&gt;&amp;gt; Configure ACS to be at 0xbef4_0000 (i.e. SRAM is part of ACS)&lt;/P&gt;&lt;P&gt;Please use address 0xBF000000.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2019 03:02:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913528#M8075</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2019-06-13T03:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913529#M8076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your solution works, thanks a lot!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I don't understand, why it works now. Can you give an explanation, please?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2019 12:25:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913529#M8076</guid>
      <dc:creator>tmoos</dc:creator>
      <dc:date>2019-06-13T12:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913530#M8077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;256k is 0x40000.&lt;/P&gt;&lt;P&gt;Base address 0xBFFC0000 gives memory window up to 0xBFFFFFFF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addresses in the PBI instructions are provided as 3-byte (6 hexadecimal digits) offsets, so ACS base address for the above SRAM area has to be 0xBF000000.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2019 15:24:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913530#M8077</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2019-06-13T15:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913531#M8078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; 256k is 0x40000.&lt;/P&gt;&lt;P&gt;&amp;gt; Base address 0xBFFC0000 gives memory window up to 0xBFFFFFFF.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;And base address 0xBFF00000 gives memory window up to 0xBFF40000. I still don't understand why that window doesn't work. Is there a limitation where the SRAM can be mapped? If yes, where is the limitation documented?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jun 2019 08:14:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913531#M8078</guid>
      <dc:creator>tmoos</dc:creator>
      <dc:date>2019-06-14T08:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913532#M8079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please check the U-Boot configuration parameters.&lt;/P&gt;&lt;P&gt;I believe that in default case it must be allocated starting from 0xBFFC0000.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jun 2019 08:30:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913532#M8079</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2019-06-14T08:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: Why does PBI stop after 0x300 bytes?</title>
      <link>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913533#M8080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found the reason for my problem: The ACS address must be 16 MiB aligned. My ACS address was 0xbef4_0000, which is not properly aligned. The PBL ignores the 24 lower bits, thus using 0xbe00_0000.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is documented in the "QorIQ T1024 Reference Manual", Rev.0 (07/2015), section "4.5.5 Alternate configuration base address register low (LCC_ALTCBARL)".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jun 2019 12:20:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/QorIQ/Why-does-PBI-stop-after-0x300-bytes/m-p/913533#M8080</guid>
      <dc:creator>tmoos</dc:creator>
      <dc:date>2019-06-14T12:20:27Z</dc:date>
    </item>
  </channel>
</rss>

