<?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: MCUXpresso J-Link Debugging on eXIP iMXRT1062 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/MCUXpresso-J-Link-Debugging-on-eXIP-iMXRT1062/m-p/1417201#M187309</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/167009"&gt;@crisitanbalint&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; Normally, we debug the code before the BEE, after the application finished, then do the BEE again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; So, my understanding is, after BEE, the debug can't debug with JTAG directly, but you can try it on your own board.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; If you can't debug it with your encrypted board, and you still want to do the debug, you can run your code in the internal RAM with debug, after it is working, then you can burn it with flash BEE again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wish it helps you!&lt;/P&gt;
&lt;P&gt;If you still have questions about it, please kindly let me know.&lt;/P&gt;
&lt;P&gt;Best Regard,&lt;/P&gt;
&lt;P&gt;Kerry&lt;/P&gt;</description>
    <pubDate>Tue, 22 Feb 2022 05:42:09 GMT</pubDate>
    <dc:creator>kerryzhou</dc:creator>
    <dc:date>2022-02-22T05:42:09Z</dc:date>
    <item>
      <title>MCUXpresso J-Link Debugging on eXIP iMXRT1062</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MCUXpresso-J-Link-Debugging-on-eXIP-iMXRT1062/m-p/1415500#M187150</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Does Debug via MCUXpresso JTAG still work after an iMXRT1062 board has Encryption Enabled ( i.e. encrypted XIP enabled fuse bit, BEE key sel fuse bit and user key fused )? It will not have the HAB closed yet.&lt;/P&gt;&lt;P&gt;We want to enable enc XIP for testing and we wonder if those boards can be used further for development.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 18:07:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MCUXpresso-J-Link-Debugging-on-eXIP-iMXRT1062/m-p/1415500#M187150</guid>
      <dc:creator>crisitanbalint</dc:creator>
      <dc:date>2022-02-17T18:07:11Z</dc:date>
    </item>
    <item>
      <title>Re: MCUXpresso J-Link Debugging on eXIP iMXRT1062</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MCUXpresso-J-Link-Debugging-on-eXIP-iMXRT1062/m-p/1417201#M187309</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/167009"&gt;@crisitanbalint&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; Normally, we debug the code before the BEE, after the application finished, then do the BEE again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; So, my understanding is, after BEE, the debug can't debug with JTAG directly, but you can try it on your own board.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; If you can't debug it with your encrypted board, and you still want to do the debug, you can run your code in the internal RAM with debug, after it is working, then you can burn it with flash BEE again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wish it helps you!&lt;/P&gt;
&lt;P&gt;If you still have questions about it, please kindly let me know.&lt;/P&gt;
&lt;P&gt;Best Regard,&lt;/P&gt;
&lt;P&gt;Kerry&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 05:42:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MCUXpresso-J-Link-Debugging-on-eXIP-iMXRT1062/m-p/1417201#M187309</guid>
      <dc:creator>kerryzhou</dc:creator>
      <dc:date>2022-02-22T05:42:09Z</dc:date>
    </item>
  </channel>
</rss>

