<?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 dcp hash context alignment in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/dcp-hash-context-alignment/m-p/1164732#M10443</link>
    <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;I have a question related to the DCP driver from SDK2.8.2 (SDK_2.8.2_EVK-MIMXRT1060\devices\MIMXRT1062\drivers\fsl_dcp.c).&lt;/P&gt;&lt;P&gt;The function DCP_HASH_Update(...) calls dcp_hash_check_context(...), which (with DCP_USE_DCACHE=1) checks that the input hash context is 32-byte aligned.&lt;/P&gt;&lt;P&gt;I would like to ask: Why is this check performed?&lt;/P&gt;&lt;P&gt;As far as I understand the documentation (i.MX RT 1050 security reference manual, Rev. 1, 04/2018, section 7.4.6 DCP context buffer pointer), there isn't any requirement for the context alignment. It only states, that it should be word-aligned for optimal performance. There is no requirement for 32-byte alignment.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Michal&lt;/P&gt;</description>
    <pubDate>Thu, 08 Oct 2020 19:08:38 GMT</pubDate>
    <dc:creator>michalhojsik</dc:creator>
    <dc:date>2020-10-08T19:08:38Z</dc:date>
    <item>
      <title>dcp hash context alignment</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/dcp-hash-context-alignment/m-p/1164732#M10443</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;I have a question related to the DCP driver from SDK2.8.2 (SDK_2.8.2_EVK-MIMXRT1060\devices\MIMXRT1062\drivers\fsl_dcp.c).&lt;/P&gt;&lt;P&gt;The function DCP_HASH_Update(...) calls dcp_hash_check_context(...), which (with DCP_USE_DCACHE=1) checks that the input hash context is 32-byte aligned.&lt;/P&gt;&lt;P&gt;I would like to ask: Why is this check performed?&lt;/P&gt;&lt;P&gt;As far as I understand the documentation (i.MX RT 1050 security reference manual, Rev. 1, 04/2018, section 7.4.6 DCP context buffer pointer), there isn't any requirement for the context alignment. It only states, that it should be word-aligned for optimal performance. There is no requirement for 32-byte alignment.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Michal&lt;/P&gt;</description>
      <pubDate>Thu, 08 Oct 2020 19:08:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/dcp-hash-context-alignment/m-p/1164732#M10443</guid>
      <dc:creator>michalhojsik</dc:creator>
      <dc:date>2020-10-08T19:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: dcp hash context alignment</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/dcp-hash-context-alignment/m-p/1166319#M10515</link>
      <description>&lt;P&gt;Hello Michal,&lt;/P&gt;
&lt;P&gt;This is a DCACHE limitation. As you can see in the following application note, the buffer address should be L1 cache line size aligned (32 bytes in i.MXRT). Therefore, when using DCACHE 32-byte alignment is required.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/application-note/AN12042.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/application-note/AN12042.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Felipe&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 21:24:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/dcp-hash-context-alignment/m-p/1166319#M10515</guid>
      <dc:creator>FelipeGarcia</dc:creator>
      <dc:date>2020-10-12T21:24:16Z</dc:date>
    </item>
  </channel>
</rss>

