<?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 IMX8ULP J-Link Support in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX8ULP-J-Link-Support/m-p/2121457#M238628</link>
    <description>&lt;P&gt;Good morning!&amp;nbsp; Looking for some more detail on the limitations of J-Link JTAG interface with the IMX8ULP M33 core.&lt;/P&gt;&lt;P&gt;Thus far, yes, we have been able to follow AN14120 and attach after programming with UUU.&amp;nbsp; However, we are unable to program directly with JTAG to the M33 (yes, using the M33_container generated from imx-mkimage).&amp;nbsp; It appears that writes to any secure memory areas (0x1ffc2000, for instance), fail, while non secure RAM areas can be written.&lt;/P&gt;&lt;P&gt;Thus:&lt;/P&gt;&lt;P&gt;a) is there a solution to allow full programming of the M33 through JTAG without UUU or bootline toggling?&lt;/P&gt;&lt;P&gt;b) alternatively, is there a J-flash script/driver to support direct JTAG programming of the attached NOR on FlexSpi0?&lt;/P&gt;&lt;P&gt;c) Our J-link seems to detect that security is enabled on the processor (MIMX8UDCVP08SC on a -EVK), and goes into 'secure mode'....then fails to program anyway.&amp;nbsp; We seen conflicting opinions on if J-link support secure debug for the IMX8ULP series.&amp;nbsp; Any definitive information out there?&lt;/P&gt;&lt;P&gt;d) And finally - the IMX part number reference indicates that the S (in MIMX8UDCVP08SC) stands for 'security fuse enabled' in the part.&amp;nbsp; There are quite a few fuses and options related to security - anyone have a more precise definition of what all the S implies?&amp;nbsp; For example, JTAG must not be fused by default into secure JTAG access only, otherwise we wouldn't be able to attach at all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any and all help-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Jun 2025 13:19:30 GMT</pubDate>
    <dc:creator>Batwings99</dc:creator>
    <dc:date>2025-06-23T13:19:30Z</dc:date>
    <item>
      <title>IMX8ULP J-Link Support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8ULP-J-Link-Support/m-p/2121457#M238628</link>
      <description>&lt;P&gt;Good morning!&amp;nbsp; Looking for some more detail on the limitations of J-Link JTAG interface with the IMX8ULP M33 core.&lt;/P&gt;&lt;P&gt;Thus far, yes, we have been able to follow AN14120 and attach after programming with UUU.&amp;nbsp; However, we are unable to program directly with JTAG to the M33 (yes, using the M33_container generated from imx-mkimage).&amp;nbsp; It appears that writes to any secure memory areas (0x1ffc2000, for instance), fail, while non secure RAM areas can be written.&lt;/P&gt;&lt;P&gt;Thus:&lt;/P&gt;&lt;P&gt;a) is there a solution to allow full programming of the M33 through JTAG without UUU or bootline toggling?&lt;/P&gt;&lt;P&gt;b) alternatively, is there a J-flash script/driver to support direct JTAG programming of the attached NOR on FlexSpi0?&lt;/P&gt;&lt;P&gt;c) Our J-link seems to detect that security is enabled on the processor (MIMX8UDCVP08SC on a -EVK), and goes into 'secure mode'....then fails to program anyway.&amp;nbsp; We seen conflicting opinions on if J-link support secure debug for the IMX8ULP series.&amp;nbsp; Any definitive information out there?&lt;/P&gt;&lt;P&gt;d) And finally - the IMX part number reference indicates that the S (in MIMX8UDCVP08SC) stands for 'security fuse enabled' in the part.&amp;nbsp; There are quite a few fuses and options related to security - anyone have a more precise definition of what all the S implies?&amp;nbsp; For example, JTAG must not be fused by default into secure JTAG access only, otherwise we wouldn't be able to attach at all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any and all help-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jun 2025 13:19:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8ULP-J-Link-Support/m-p/2121457#M238628</guid>
      <dc:creator>Batwings99</dc:creator>
      <dc:date>2025-06-23T13:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: IMX8ULP J-Link Support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8ULP-J-Link-Support/m-p/2122020#M238669</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/251935"&gt;@Batwings99&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Which version of BSP you are using? Is the A core running with ATF?&lt;/P&gt;
&lt;P&gt;It seems an issue related to TRDC protection. Please have a check the TRDC configuration at address:&lt;/P&gt;
&lt;PRE class="lia-code-sample  language-markup"&gt;&lt;CODE&gt;8 words from 0x28032020
4 words from 0x28032BA8&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Harvey&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jun 2025 08:41:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8ULP-J-Link-Support/m-p/2122020#M238669</guid>
      <dc:creator>Harvey021</dc:creator>
      <dc:date>2025-06-24T08:41:37Z</dc:date>
    </item>
  </channel>
</rss>

