<?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: Not able to flash using JLINk debugger</title>
    <link>https://community.nxp.com/t5/S32K/Not-able-to-flash-using-JLINk-debugger/m-p/2147081#M51619</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/245712"&gt;@bhagwanjagtap&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Segger specifies that if an authentication key is required to enable debug access but has not yet been specified, a dialog box will appear prompting you to enter the key. For more details, please refer to the section "Specifying the authentication code using the ID Code dialog" in the following link:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://kb.segger.com/NXP_S32K3xx#Debug_Authentication" target="_blank" rel="noopener nofollow noreferrer"&gt;SEGGER -&amp;nbsp;NXP S32K3xx&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you are not seeing this behavior, could you please share a screenshot of the error message you are encountering?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, do you have access to another debugger that you could try using to flash the MCU? This could help determine whether the issue is related to the debugger or hardware.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
    <pubDate>Tue, 05 Aug 2025 21:19:52 GMT</pubDate>
    <dc:creator>VaneB</dc:creator>
    <dc:date>2025-08-05T21:19:52Z</dc:date>
    <item>
      <title>Not able to flash using JLINk debugger</title>
      <link>https://community.nxp.com/t5/S32K/Not-able-to-flash-using-JLINk-debugger/m-p/2146745#M51606</link>
      <description>&lt;P&gt;I am able to connect to target and JLINK&amp;nbsp; read the target with "No HSM flashed, no device lock", but when i try to flash the hex it shows "Locked device detected S32K324, please enter password"&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2025 08:37:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Not-able-to-flash-using-JLINk-debugger/m-p/2146745#M51606</guid>
      <dc:creator>bhagwanjagtap</dc:creator>
      <dc:date>2025-08-05T08:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Not able to flash using JLINk debugger</title>
      <link>https://community.nxp.com/t5/S32K/Not-able-to-flash-using-JLINk-debugger/m-p/2147081#M51619</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/245712"&gt;@bhagwanjagtap&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Segger specifies that if an authentication key is required to enable debug access but has not yet been specified, a dialog box will appear prompting you to enter the key. For more details, please refer to the section "Specifying the authentication code using the ID Code dialog" in the following link:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://kb.segger.com/NXP_S32K3xx#Debug_Authentication" target="_blank" rel="noopener nofollow noreferrer"&gt;SEGGER -&amp;nbsp;NXP S32K3xx&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you are not seeing this behavior, could you please share a screenshot of the error message you are encountering?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, do you have access to another debugger that you could try using to flash the MCU? This could help determine whether the issue is related to the debugger or hardware.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2025 21:19:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Not-able-to-flash-using-JLINk-debugger/m-p/2147081#M51619</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2025-08-05T21:19:52Z</dc:date>
    </item>
  </channel>
</rss>

