<?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>i.MX ProcessorsのトピックOCRAM not accessible on IMX8QM-MEK</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961493#M143412</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We received newer version of the IMX8QM-MEK boards and I was trying to access OCRAM to perform some memory tests. This&amp;nbsp;&lt;SPAN&gt;OCRAM&lt;/SPAN&gt; region (0x100000 - 0x13FFFF) doesn't seem to be accessible. I am booting the board using u-boot and loading an application on top of it. I see that this region of memory is not accessible by u-boot as well.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However this was accessible in the previous version of the board.&lt;/P&gt;&lt;P&gt;I tried using the SC APIs to&amp;nbsp;assign the memory region but wasn't successful (find memory API returns - not found error). What do i need to do to access this region? I presume the SCFW has changed and doesn't allow access?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U-Boot version loaded on the new board - U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 09 Jun 2019 16:06:45 GMT</pubDate>
    <dc:creator>nagabhushan_v</dc:creator>
    <dc:date>2019-06-09T16:06:45Z</dc:date>
    <item>
      <title>OCRAM not accessible on IMX8QM-MEK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961493#M143412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We received newer version of the IMX8QM-MEK boards and I was trying to access OCRAM to perform some memory tests. This&amp;nbsp;&lt;SPAN&gt;OCRAM&lt;/SPAN&gt; region (0x100000 - 0x13FFFF) doesn't seem to be accessible. I am booting the board using u-boot and loading an application on top of it. I see that this region of memory is not accessible by u-boot as well.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However this was accessible in the previous version of the board.&lt;/P&gt;&lt;P&gt;I tried using the SC APIs to&amp;nbsp;assign the memory region but wasn't successful (find memory API returns - not found error). What do i need to do to access this region? I presume the SCFW has changed and doesn't allow access?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U-Boot version loaded on the new board - U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Jun 2019 16:06:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961493#M143412</guid>
      <dc:creator>nagabhushan_v</dc:creator>
      <dc:date>2019-06-09T16:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: OCRAM not accessible on IMX8QM-MEK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961494#M143413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nagabhushan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can try to fully rebuild image using latest patches, "Linux 4.14.98_2.0.1-Patch"&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/support/developer-resources/evaluation-and-development-boards/i.mx-evaluation-and-development-boards/i.mx-software-and-development-tool:IMX-SW" title="https://www.nxp.com/support/developer-resources/evaluation-and-development-boards/i.mx-evaluation-and-development-boards/i.mx-software-and-development-tool:IMX-SW"&gt;i.MX Software | NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;note, recommended to use configuration derived from latest Register Programming Aid&lt;/P&gt;&lt;P&gt;and latest ddr test: mx8_ddr_stress_test_ER9.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2019 23:40:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961494#M143413</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-06-10T23:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: OCRAM not accessible on IMX8QM-MEK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961495#M143414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Igor. I tried building the fsl-core-image-base images for Patch&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;4.14.98_2.0.1-Patch as you suggested but I still wasn't able to access the OCRAM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Also I see that in A0 boards the SECO firmware (&lt;SPAN&gt;ahab-container.image) was not required but is now included in B0. Is this making the OCRAM secure?&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jun 2019 05:04:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961495#M143414</guid>
      <dc:creator>nagabhushan_v</dc:creator>
      <dc:date>2019-06-18T05:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: OCRAM not accessible on IMX8QM-MEK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961496#M143415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nagabhushan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I sent list of changes via mail, please note that&lt;/P&gt;&lt;P&gt;i.MX8QM is not publicly released yet and not fully supported.&lt;/P&gt;&lt;P&gt;May be suggested to proceed with help of extended support of&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/support/support/nxp-professional-services:PROFESSIONAL-SERVICE" title="https://www.nxp.com/support/support/nxp-professional-services:PROFESSIONAL-SERVICE"&gt;NXP Professional Services | NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jun 2019 09:35:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961496#M143415</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-06-18T09:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: OCRAM not accessible on IMX8QM-MEK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961497#M143416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you, Igor. The change log was helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jun 2019 14:14:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/OCRAM-not-accessible-on-IMX8QM-MEK/m-p/961497#M143416</guid>
      <dc:creator>nagabhushan_v</dc:creator>
      <dc:date>2019-06-18T14:14:08Z</dc:date>
    </item>
  </channel>
</rss>

