<?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 About tzasc on imx6q sabre sd borad:  How to trigger the synchronous external data abort in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/About-tzasc-on-imx6q-sabre-sd-borad-How-to-trigger-the/m-p/1180383#M164696</link>
    <description>&lt;P&gt;The current experimental development board is IMx6Qsabresd, the environment is &lt;A href="https://source.codeaurora.org/external/imx/uboot-imx?h=imx_v2018.03_4.14.98_2.0.0_ga" target="_blank" rel="noopener"&gt;IMx Uboot 4.14&lt;/A&gt; + &lt;A href="https://source.codeaurora.org/external/imx/linux-imx?h=imx_4.14.98_2.0.0_ga" target="_self"&gt;IMX Linux 4.14&lt;/A&gt; + &lt;A href="https://source.codeaurora.org/external/imx/imx-optee-os?h=imx_4.14.98_2.0.0_ga" target="_blank" rel="noopener"&gt;IMx optee OS&lt;/A&gt;, 4M region is set as the normal world read-only, the secure world can read and write&lt;BR /&gt;Expectations:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Synchronous External Data ABORT is triggered into Monitor mode when the normal world writes to this region&lt;BR /&gt;I have done :&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;The cache has been set to write through, the SCR.EA bit has been set to 1, IOMUX GPR9, and CCM GPR3&amp;nbsp; has been set&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; In the normal world, I write the value to this region, then read it, the value is incorrect. It means that the tzasc is worked&lt;BR /&gt;Does anyone know how to trigger this exception?&lt;/P&gt;</description>
    <pubDate>Tue, 10 Nov 2020 01:53:47 GMT</pubDate>
    <dc:creator>xushouyin17</dc:creator>
    <dc:date>2020-11-10T01:53:47Z</dc:date>
    <item>
      <title>About tzasc on imx6q sabre sd borad:  How to trigger the synchronous external data abort</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/About-tzasc-on-imx6q-sabre-sd-borad-How-to-trigger-the/m-p/1180383#M164696</link>
      <description>&lt;P&gt;The current experimental development board is IMx6Qsabresd, the environment is &lt;A href="https://source.codeaurora.org/external/imx/uboot-imx?h=imx_v2018.03_4.14.98_2.0.0_ga" target="_blank" rel="noopener"&gt;IMx Uboot 4.14&lt;/A&gt; + &lt;A href="https://source.codeaurora.org/external/imx/linux-imx?h=imx_4.14.98_2.0.0_ga" target="_self"&gt;IMX Linux 4.14&lt;/A&gt; + &lt;A href="https://source.codeaurora.org/external/imx/imx-optee-os?h=imx_4.14.98_2.0.0_ga" target="_blank" rel="noopener"&gt;IMx optee OS&lt;/A&gt;, 4M region is set as the normal world read-only, the secure world can read and write&lt;BR /&gt;Expectations:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Synchronous External Data ABORT is triggered into Monitor mode when the normal world writes to this region&lt;BR /&gt;I have done :&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;The cache has been set to write through, the SCR.EA bit has been set to 1, IOMUX GPR9, and CCM GPR3&amp;nbsp; has been set&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; In the normal world, I write the value to this region, then read it, the value is incorrect. It means that the tzasc is worked&lt;BR /&gt;Does anyone know how to trigger this exception?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2020 01:53:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/About-tzasc-on-imx6q-sabre-sd-borad-How-to-trigger-the/m-p/1180383#M164696</guid>
      <dc:creator>xushouyin17</dc:creator>
      <dc:date>2020-11-10T01:53:47Z</dc:date>
    </item>
    <item>
      <title>Re: About tzasc on imx6q sabre sd borad:  How to trigger the synchronous external data abort</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/About-tzasc-on-imx6q-sabre-sd-borad-How-to-trigger-the/m-p/1185486#M165138</link>
      <description>&lt;P&gt;Hi shouyin xu,&lt;/P&gt;
&lt;P&gt;I quote the ARM Cortex-A9 TRM: "External aborts can be configured to trap to Monitor mode by setting the EA bit in the SCR".&lt;/P&gt;
&lt;P&gt;I think the External abort registers that are mainly involved are SCR and DFSR/IFSR so it is already active.&lt;/P&gt;
&lt;P&gt;The DFSR register gives you additional details on the abort to know the Fault Type and the cause (Read/Write).&lt;/P&gt;
&lt;P&gt;Check that status register when you try to write to that memory region.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Luis.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 21:19:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/About-tzasc-on-imx6q-sabre-sd-borad-How-to-trigger-the/m-p/1185486#M165138</guid>
      <dc:creator>nxf63969</dc:creator>
      <dc:date>2020-11-18T21:19:17Z</dc:date>
    </item>
  </channel>
</rss>

