<?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 Identification of ARM-based controllers via Debugger in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Identification-of-ARM-based-controllers-via-Debugger/m-p/1313062#M11439</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;this refers to ALL ARM based controllers (automotive, industrial, consumer, ...)&lt;/P&gt;
&lt;P&gt;There are 3rd parties doing debuggers for lots of different devices, often they are using SWD for the interface.&lt;/P&gt;
&lt;P&gt;The first thing the debugger need to do is to identify the device.&lt;/P&gt;
&lt;P&gt;Therefore customers are asking for a table which shows the relation of an ID read by SWD and the device. This table should contain all devices and also all revisions.&lt;/P&gt;
&lt;P&gt;Vector-Informatik has created some list by reading out IDs of known devices, but this list is by far not complete and it is not clear, which ID is important for which purpose. This list is attached&lt;/P&gt;</description>
    <pubDate>Mon, 26 Jul 2021 07:39:57 GMT</pubDate>
    <dc:creator>JosefFuchs</dc:creator>
    <dc:date>2021-07-26T07:39:57Z</dc:date>
    <item>
      <title>Identification of ARM-based controllers via Debugger</title>
      <link>https://community.nxp.com/t5/S32K/Identification-of-ARM-based-controllers-via-Debugger/m-p/1313062#M11439</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;this refers to ALL ARM based controllers (automotive, industrial, consumer, ...)&lt;/P&gt;
&lt;P&gt;There are 3rd parties doing debuggers for lots of different devices, often they are using SWD for the interface.&lt;/P&gt;
&lt;P&gt;The first thing the debugger need to do is to identify the device.&lt;/P&gt;
&lt;P&gt;Therefore customers are asking for a table which shows the relation of an ID read by SWD and the device. This table should contain all devices and also all revisions.&lt;/P&gt;
&lt;P&gt;Vector-Informatik has created some list by reading out IDs of known devices, but this list is by far not complete and it is not clear, which ID is important for which purpose. This list is attached&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jul 2021 07:39:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Identification-of-ARM-based-controllers-via-Debugger/m-p/1313062#M11439</guid>
      <dc:creator>JosefFuchs</dc:creator>
      <dc:date>2021-07-26T07:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: Identification of ARM-based controllers via Debugger</title>
      <link>https://community.nxp.com/t5/S32K/Identification-of-ARM-based-controllers-via-Debugger/m-p/1313281#M11442</link>
      <description>&lt;P&gt;Hi Josef,&lt;/P&gt;
&lt;P&gt;In this forum I can share with you the values for the S32K1xx families.&lt;/P&gt;
&lt;P&gt;S32K1xx IDR(SW_DP_IDR): &lt;BR /&gt;0x001C_0000&lt;/P&gt;
&lt;P&gt;TargetID/JTAG ID:&lt;BR /&gt;Chip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PIN value&lt;BR /&gt;S32K116 - 0b0100110100&lt;BR /&gt;S32K118 - 0b0100110000&lt;BR /&gt;S32K142 - 0b0100111000&lt;BR /&gt;S32K144 - 0b0100111101&lt;BR /&gt;S32K144W - 0b0101010100&lt;BR /&gt;S32K146 - 0b0101000100&lt;BR /&gt;S32K148 - 0b0101010000&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Garabo&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jul 2021 16:02:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Identification-of-ARM-based-controllers-via-Debugger/m-p/1313281#M11442</guid>
      <dc:creator>Luis_Garabo</dc:creator>
      <dc:date>2021-07-26T16:02:57Z</dc:date>
    </item>
  </channel>
</rss>

