<?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>S32KのトピックRe: S32K3 Debug Authentication</title>
    <link>https://community.nxp.com/t5/S32K/S32K3-Debug-Authentication/m-p/1895335#M36976</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/219702"&gt;@Mateusz_K&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition to the information provided in the S32K3 Reference Manual and HSE_B Reference Manual on debug protection, PEMicro has posted the instructions on their website for S32K3xx Secure Debug with MULTILINK.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.pemicro.com/blog/index.cfm?post_id=216#ordering" target="_blank" rel="noopener"&gt;Using PEmicro Tools to Enable S32K3xx Secure Debug Support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Also, the HSE Demo App is provided with some of the scripts for Lauterbach TRACE32 used for debug authorization. As well as the application to enable the application debugging authorization feature.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;B.R.&lt;/P&gt;&lt;P&gt;VaneB&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2024 18:05:12 GMT</pubDate>
    <dc:creator>VaneB</dc:creator>
    <dc:date>2024-06-27T18:05:12Z</dc:date>
    <item>
      <title>S32K3 Debug Authentication</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-Debug-Authentication/m-p/1895193#M36971</link>
      <description>&lt;P&gt;Where I can get more information about dynamic debugger authentication method (challenger &amp;amp; response), more than there is written in the Reference Manual, anyway? I want to know how response from the debugger should be generated? Are there any documents considering this matter?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 13:29:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-Debug-Authentication/m-p/1895193#M36971</guid>
      <dc:creator>Mateusz_K</dc:creator>
      <dc:date>2024-06-27T13:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3 Debug Authentication</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-Debug-Authentication/m-p/1895335#M36976</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/219702"&gt;@Mateusz_K&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition to the information provided in the S32K3 Reference Manual and HSE_B Reference Manual on debug protection, PEMicro has posted the instructions on their website for S32K3xx Secure Debug with MULTILINK.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.pemicro.com/blog/index.cfm?post_id=216#ordering" target="_blank" rel="noopener"&gt;Using PEmicro Tools to Enable S32K3xx Secure Debug Support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Also, the HSE Demo App is provided with some of the scripts for Lauterbach TRACE32 used for debug authorization. As well as the application to enable the application debugging authorization feature.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;B.R.&lt;/P&gt;&lt;P&gt;VaneB&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 18:05:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-Debug-Authentication/m-p/1895335#M36976</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2024-06-27T18:05:12Z</dc:date>
    </item>
  </channel>
</rss>

