<?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: Using DCP while running Encrypted XIP with BEE in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412711#M18305</link>
    <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/188106"&gt;@damonb&lt;/a&gt;I saw you were using the BEE capabilities &lt;A href="https://community.nxp.com/t5/i-MX-RT/RT1064-Signed-amp-Encrypted-bootloader-amp-application/m-p/1370002" target="_self"&gt;in your post here&lt;/A&gt;. Have you used DCP in your encrypted application code?&lt;/P&gt;</description>
    <pubDate>Sat, 12 Feb 2022 21:22:00 GMT</pubDate>
    <dc:creator>natebowen</dc:creator>
    <dc:date>2022-02-12T21:22:00Z</dc:date>
    <item>
      <title>Using DCP while running Encrypted XIP with BEE</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412709#M18304</link>
      <description>&lt;P&gt;I currently have a non-encrypted second-stage bootloader that sets up the BEE peripheral with a register-based AES key. This is based on the driver example in SDK 2.11.0. Once the bootloader has set up the BEE, I jump to my AES-CTR encrypted application code. This process works fine.&lt;BR /&gt;&lt;BR /&gt;However, when I attempt to use the DCP in the application code (also based on the driver example from SDK 2.11.0) to perform AES encryption or decryption with an SRAM-based key, my encrypted data is returned as [0x00, 0x00, ...].&lt;/P&gt;&lt;P&gt;If I don't enable the BEE in the bootloader and jump to a non-encrypted version of my application code, the DCP functions as expected.&lt;/P&gt;&lt;P&gt;Is there any reason why the DCP should behave differently if the BEE is running? I have a copy of the RT106XSRM Rev 0, and the DCP and BEE chapters make no mention of each other. Note that I'm not using SW_GP2, here.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Feb 2022 21:09:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412709#M18304</guid>
      <dc:creator>natebowen</dc:creator>
      <dc:date>2022-02-12T21:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: Using DCP while running Encrypted XIP with BEE</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412711#M18305</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/188106"&gt;@damonb&lt;/a&gt;I saw you were using the BEE capabilities &lt;A href="https://community.nxp.com/t5/i-MX-RT/RT1064-Signed-amp-Encrypted-bootloader-amp-application/m-p/1370002" target="_self"&gt;in your post here&lt;/A&gt;. Have you used DCP in your encrypted application code?&lt;/P&gt;</description>
      <pubDate>Sat, 12 Feb 2022 21:22:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412711#M18305</guid>
      <dc:creator>natebowen</dc:creator>
      <dc:date>2022-02-12T21:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: Using DCP while running Encrypted XIP with BEE</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412790#M18309</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;It seems a bit weird, the DCP should be independent with the BEE, so to be prudent, I was wondering if you can list the steps of testing, as I'd like to replicate the phenomenon you encountered.&lt;BR /&gt;Looking forward to your reply.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 02:41:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1412790#M18309</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2022-02-14T02:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: Using DCP while running Encrypted XIP with BEE</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1413037#M18321</link>
      <description>&lt;P&gt;I'm afraid I'm not using DCP in the application code&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 10:35:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-DCP-while-running-Encrypted-XIP-with-BEE/m-p/1413037#M18321</guid>
      <dc:creator>damonb</dc:creator>
      <dc:date>2022-02-14T10:35:37Z</dc:date>
    </item>
  </channel>
</rss>

