<?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 how to debug csec function use jlink gdbsever in S32K</title>
    <link>https://community.nxp.com/t5/S32K/how-to-debug-csec-function-use-jlink-gdbsever/m-p/2162612#M52348</link>
    <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&amp;nbsp; we enable csec function and write key in CSEC_KEY_1，then debug the app use jlink gdbsever，so mcu is locked.&lt;/P&gt;&lt;P&gt;&amp;nbsp; how to debug csec function use jlink gdbsever ,must be erase all csec key?&lt;/P&gt;</description>
    <pubDate>Wed, 03 Sep 2025 06:33:15 GMT</pubDate>
    <dc:creator>top</dc:creator>
    <dc:date>2025-09-03T06:33:15Z</dc:date>
    <item>
      <title>how to debug csec function use jlink gdbsever</title>
      <link>https://community.nxp.com/t5/S32K/how-to-debug-csec-function-use-jlink-gdbsever/m-p/2162612#M52348</link>
      <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&amp;nbsp; we enable csec function and write key in CSEC_KEY_1，then debug the app use jlink gdbsever，so mcu is locked.&lt;/P&gt;&lt;P&gt;&amp;nbsp; how to debug csec function use jlink gdbsever ,must be erase all csec key?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Sep 2025 06:33:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/how-to-debug-csec-function-use-jlink-gdbsever/m-p/2162612#M52348</guid>
      <dc:creator>top</dc:creator>
      <dc:date>2025-09-03T06:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: how to debug csec function use jlink gdbsever</title>
      <link>https://community.nxp.com/t5/S32K/how-to-debug-csec-function-use-jlink-gdbsever/m-p/2162842#M52370</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/253564"&gt;@top&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just answered similar question here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K/S32K142%E4%BD%BF%E7%94%A8CSEc%E5%8A%9F%E8%83%BD%E8%8A%AF%E7%89%87%E8%A2%AB%E9%94%81%E6%AD%BB/m-p/2162840/highlight/true#M52369" target="_blank"&gt;https://community.nxp.com/t5/S32K/S32K142%E4%BD%BF%E7%94%A8CSEc%E5%8A%9F%E8%83%BD%E8%8A%AF%E7%89%87%E8%A2%AB%E9%94%81%E6%AD%BB/m-p/2162840/highlight/true#M52369&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Yes, it's necessary to erase the keys (disable CSEc) by CMD_DBG_CHAL and CMD_DBG_AUTH commands with knowledge of MASTER_ECU_KEY. Or use different debug probe (like Pemicro)&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 03 Sep 2025 10:56:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/how-to-debug-csec-function-use-jlink-gdbsever/m-p/2162842#M52370</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-09-03T10:56:16Z</dc:date>
    </item>
  </channel>
</rss>

