<?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のトピックNo more debug connection after Port-Cfg.</title>
    <link>https://community.nxp.com/t5/S32K/No-more-debug-connection-after-Port-Cfg/m-p/1650021#M22904</link>
    <description>&lt;P&gt;By trying out a binary I set up for S32K358 (On S32K3x8CVB-Q289) and another one for S32K344 (on the S32K3XXEVB-Q172) I got to the same problem:&lt;/P&gt;&lt;P&gt;Durring startup phase I suddenly lost debug-connection, and havent been able to get the connection back since then. The error appeared after the Port_Init() (Port-Module of the AUTOSAR-Stack):&lt;/P&gt;&lt;P&gt;After writing with the support-team of the debugger (iSystem), it seems like that the Port-Module reconfigured the JTAG-Pins of the controller, so that the jtag functionallity is no longer present.&lt;/P&gt;&lt;P&gt;Now the question is, am I able to get the debugger connetion back somehow on the the chips? Is there a way to reset the port-config without a debug-connection?&lt;/P&gt;&lt;P&gt;I wrote about this with one of the NXP-Engeneers, who recommended to open a question here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 May 2023 06:54:14 GMT</pubDate>
    <dc:creator>BenjaminKubitschek</dc:creator>
    <dc:date>2023-05-15T06:54:14Z</dc:date>
    <item>
      <title>No more debug connection after Port-Cfg.</title>
      <link>https://community.nxp.com/t5/S32K/No-more-debug-connection-after-Port-Cfg/m-p/1650021#M22904</link>
      <description>&lt;P&gt;By trying out a binary I set up for S32K358 (On S32K3x8CVB-Q289) and another one for S32K344 (on the S32K3XXEVB-Q172) I got to the same problem:&lt;/P&gt;&lt;P&gt;Durring startup phase I suddenly lost debug-connection, and havent been able to get the connection back since then. The error appeared after the Port_Init() (Port-Module of the AUTOSAR-Stack):&lt;/P&gt;&lt;P&gt;After writing with the support-team of the debugger (iSystem), it seems like that the Port-Module reconfigured the JTAG-Pins of the controller, so that the jtag functionallity is no longer present.&lt;/P&gt;&lt;P&gt;Now the question is, am I able to get the debugger connetion back somehow on the the chips? Is there a way to reset the port-config without a debug-connection?&lt;/P&gt;&lt;P&gt;I wrote about this with one of the NXP-Engeneers, who recommended to open a question here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2023 06:54:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/No-more-debug-connection-after-Port-Cfg/m-p/1650021#M22904</guid>
      <dc:creator>BenjaminKubitschek</dc:creator>
      <dc:date>2023-05-15T06:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: No more debug connection after Port-Cfg.</title>
      <link>https://community.nxp.com/t5/S32K/No-more-debug-connection-after-Port-Cfg/m-p/1650308#M22922</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/217272"&gt;@BenjaminKubitschek&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I assume the reset_b pin is reconfigured to another function too, otherwise the debugger should be able to reset the MCU and establish connection.&lt;/P&gt;
&lt;P&gt;The JTAG/SWD/Reset_b pins are set to their default JTAG/SWD/Reset_b functions after each system reset.&lt;/P&gt;
&lt;P&gt;The debugger can use it until it is reconfigured by the application SW.&lt;/P&gt;
&lt;P&gt;So, you should be able to connect the debugger within this short time window.&lt;/P&gt;
&lt;P&gt;If the reset_b pin is also reconfigured, you can power-cycle the MCU to reset it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Something similar was discussed here (S32K144):&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K/S32K144-EVB-got-corrupted-after-Running-a-SDK-based-project/m-p/1648726#M22823" target="_blank"&gt;https://community.nxp.com/t5/S32K/S32K144-EVB-got-corrupted-after-Running-a-SDK-based-project/m-p/1648726#M22823&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;As mentioned in the thread, PE Micro have an utility for this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With Lauterbach, we can use a script like this&lt;/P&gt;
&lt;LI-CODE lang="c"&gt;system.CPU S32K344
wait state.power()
system.attach&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Somewhat related thread is below (S32K312).&lt;/P&gt;
&lt;P&gt;The MCU was erased using J-link commander:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32-SDK/failed-to-power-up-dap-after-program-s32k312-with-pll0-equal/td-p/1609010" target="_blank"&gt;https://community.nxp.com/t5/S32-SDK/failed-to-power-up-dap-after-program-s32k312-with-pll0-equal/td-p/1609010&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately, I'm not aware of any solution using iSystem.&lt;/P&gt;
&lt;P&gt;I believe iSystem support should be able to help you with this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2023 12:14:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/No-more-debug-connection-after-Port-Cfg/m-p/1650308#M22922</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-05-15T12:14:04Z</dc:date>
    </item>
  </channel>
</rss>

