<?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: JTAG Access in S32K</title>
    <link>https://community.nxp.com/t5/S32K/JTAG-Access/m-p/2336103#M57407</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254751"&gt;@addisonaudette1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There seems to be some confusion. In the thread you referenced, the discussion is about the S32K3 T-Box, which indeed does not include an on‑board debugger.&lt;/P&gt;
&lt;P&gt;However, the S32K3X4EVB‑T172 does include an on‑board debugger, and it also provides an embedded JTAG connector (J12). You can use either of these interfaces to flash and debug the MCU.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
    <pubDate>Thu, 19 Mar 2026 17:13:14 GMT</pubDate>
    <dc:creator>VaneB</dc:creator>
    <dc:date>2026-03-19T17:13:14Z</dc:date>
    <item>
      <title>JTAG Access</title>
      <link>https://community.nxp.com/t5/S32K/JTAG-Access/m-p/2336054#M57403</link>
      <description>&lt;P&gt;I am figuring out how to disable and enable JTAG access on the&amp;nbsp;s32k3x4evb-t172 board and am reading conflicting information.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this forum post (&lt;A href="https://community.nxp.com/t5/S32K/S32-can-t-find-Hardware-S32K344-for-Debug/td-p/1613856#:~:text=The%20S32K344%20MCU%20can%20only%20be%20reprogrammed,*%20There%20is%20no%20onboard%20debugging%20connection" target="_blank"&gt;Solved: S32 can't find Hardware (S32K344) for Debug - NXP Community&lt;/A&gt;) - the solution says&amp;nbsp;There is no on-board programmer/debugger and the S32K344 MCU can be reprogrammed via the J40 JTAG/SWD connector only.&lt;/P&gt;&lt;P&gt;However in the&amp;nbsp;&lt;FONT size="3"&gt;MCU Automotive Board Quick Starts it says you can either connect a micro usb cable to the J4- connector to debug via the on-board s32K3 debugger or just one of the available JTAG connectors to debug via the external S32k3 debugger.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Could someone elaborate which is correct and what the options are for hardware configuration JTAG access?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 15:55:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/JTAG-Access/m-p/2336054#M57403</guid>
      <dc:creator>addisonaudette1</dc:creator>
      <dc:date>2026-03-19T15:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: JTAG Access</title>
      <link>https://community.nxp.com/t5/S32K/JTAG-Access/m-p/2336103#M57407</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254751"&gt;@addisonaudette1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There seems to be some confusion. In the thread you referenced, the discussion is about the S32K3 T-Box, which indeed does not include an on‑board debugger.&lt;/P&gt;
&lt;P&gt;However, the S32K3X4EVB‑T172 does include an on‑board debugger, and it also provides an embedded JTAG connector (J12). You can use either of these interfaces to flash and debug the MCU.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 17:13:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/JTAG-Access/m-p/2336103#M57407</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2026-03-19T17:13:14Z</dc:date>
    </item>
  </channel>
</rss>

