https://community.nxp.com/t5/S32K/An-error-occurred-while-debugging-with-J-LINK/m-p/2190133#M53732 <P>Hi&nbsp;<a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/256001">@baibi</a>,</P> <P>Which version for SEGGER SW are you using? As mentioned in this other community post (<A href="https://community.nxp.com/t5/S32K/S32K344-J-Link-GDB-Server-failed-Device-name-S32K344-not/m-p/1470053#M15832" target="_blank">Solved: S32K344 J-Link GDB Server failed: Device name 'S32K344' not recognised</A>), if version is too old the device may not have been added yet to the firmware.</P> <P>I can see from the&nbsp;<A href="https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html" target="_self">Release notes</A>&nbsp;that support for S32K348 was added in <SPAN>Version V8.46.</SPAN></P> <P><SPAN>Best regards,<BR />Julián</SPAN></P> Tue, 21 Oct 2025 17:24:37 GMT Julián_AragónM 2025-10-21T17:24:37Z https://community.nxp.com/t5/S32K/An-error-occurred-while-debugging-with-J-LINK/m-p/2189733#M53708 <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="baibi_0-1761031897310.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/361785i4E0374F7A94F38D5/image-size/medium?v=v2&amp;px=400" role="button" title="baibi_0-1761031897310.png" alt="baibi_0-1761031897310.png" /></span></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="baibi_1-1761032005942.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/361786i4A84BDCA6B7837BF/image-size/medium?v=v2&amp;px=400" role="button" title="baibi_1-1761032005942.png" alt="baibi_1-1761032005942.png" /></span></P><P><SPAN>An error occurred while debugging with J-Link, as shown in the figure. How should I resolve this error?</SPAN></P><P>&nbsp;</P> Tue, 21 Oct 2025 07:44:46 GMT https://community.nxp.com/t5/S32K/An-error-occurred-while-debugging-with-J-LINK/m-p/2189733#M53708 baibi 2025-10-21T07:44:46Z https://community.nxp.com/t5/S32K/An-error-occurred-while-debugging-with-J-LINK/m-p/2190133#M53732 <P>Hi&nbsp;<a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/256001">@baibi</a>,</P> <P>Which version for SEGGER SW are you using? As mentioned in this other community post (<A href="https://community.nxp.com/t5/S32K/S32K344-J-Link-GDB-Server-failed-Device-name-S32K344-not/m-p/1470053#M15832" target="_blank">Solved: S32K344 J-Link GDB Server failed: Device name 'S32K344' not recognised</A>), if version is too old the device may not have been added yet to the firmware.</P> <P>I can see from the&nbsp;<A href="https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html" target="_self">Release notes</A>&nbsp;that support for S32K348 was added in <SPAN>Version V8.46.</SPAN></P> <P><SPAN>Best regards,<BR />Julián</SPAN></P> Tue, 21 Oct 2025 17:24:37 GMT https://community.nxp.com/t5/S32K/An-error-occurred-while-debugging-with-J-LINK/m-p/2190133#M53732 Julián_AragónM 2025-10-21T17:24:37Z