<?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 Fail debugging frdm-mcxn947 in MCX Microcontrollers</title>
    <link>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1992905#M1966</link>
    <description>&lt;P&gt;I have this issue where I can't debug or program any code in a FRDM-MCXN947, many troubles I've seen but this one is the latest&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;MCUXpresso IDE RedlinkMulti Driver v11.10 (Jul  2 2024 19:33:51 - crt_emu_cm_redlink build 741)
Found chip XML file in C:/Users/RMA2GA/Documents/MCUXpressoIDE_11.10.0_3148/workspace/led_assembly_v2/Debug\LPC1343.xml
(  5) Remote configuration complete
Reconnected to existing LinkServer process.
Probe Firmware: MCU-LINK FRDM-MCXN947 (r0E7) CMSIS-DAP V3.148 (NXP Semiconductors)
Serial Number:  0Z3QFQAMVXDWP
VID:PID:  1FC9:0143
USB Path: 0001:0008:00
connection failed - Em(01). Cannot find MEM-AP selected by core index (check target power).. Retrying
Failed on connect: Em(01). Cannot find MEM-AP selected by core index (check target power)
Connected&amp;amp;Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000000. Info: &amp;lt;None&amp;gt;
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
No debug bus (MemAp) selected
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Nov 2024 14:25:20 GMT</pubDate>
    <dc:creator>marcos-ramos</dc:creator>
    <dc:date>2024-11-12T14:25:20Z</dc:date>
    <item>
      <title>Fail debugging frdm-mcxn947</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1992905#M1966</link>
      <description>&lt;P&gt;I have this issue where I can't debug or program any code in a FRDM-MCXN947, many troubles I've seen but this one is the latest&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;MCUXpresso IDE RedlinkMulti Driver v11.10 (Jul  2 2024 19:33:51 - crt_emu_cm_redlink build 741)
Found chip XML file in C:/Users/RMA2GA/Documents/MCUXpressoIDE_11.10.0_3148/workspace/led_assembly_v2/Debug\LPC1343.xml
(  5) Remote configuration complete
Reconnected to existing LinkServer process.
Probe Firmware: MCU-LINK FRDM-MCXN947 (r0E7) CMSIS-DAP V3.148 (NXP Semiconductors)
Serial Number:  0Z3QFQAMVXDWP
VID:PID:  1FC9:0143
USB Path: 0001:0008:00
connection failed - Em(01). Cannot find MEM-AP selected by core index (check target power).. Retrying
Failed on connect: Em(01). Cannot find MEM-AP selected by core index (check target power)
Connected&amp;amp;Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000000. Info: &amp;lt;None&amp;gt;
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
No debug bus (MemAp) selected
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 14:25:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1992905#M1966</guid>
      <dc:creator>marcos-ramos</dc:creator>
      <dc:date>2024-11-12T14:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: Fail debugging frdm-mcxn947</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1993065#M1967</link>
      <description>&lt;P&gt;Hello, my name is Pavel, and I will be supporting your case, I recommend do a mass erase, or in other way maybe could change the firmware of the debugger.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKERSERVER" target="_blank"&gt;LinkServer for Microcontrollers | NXP Semiconductors&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 19:05:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1993065#M1967</guid>
      <dc:creator>Pavel_Hernandez</dc:creator>
      <dc:date>2024-11-12T19:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Fail debugging frdm-mcxn947</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1993921#M1976</link>
      <description>&lt;P&gt;Can you give me the steps to perform a mass erase?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 18:43:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1993921#M1976</guid>
      <dc:creator>marcos-ramos</dc:creator>
      <dc:date>2024-11-13T18:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: Fail debugging frdm-mcxn947</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1994152#M1980</link>
      <description>&lt;P&gt;Hello, I recommend use the SPDK and on the environment use the BLHOST to do a mas erase.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://spsdk.readthedocs.io/en/latest/usage/installation.html" target="_blank"&gt;Installation Guide — SPSDK documentation&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/user-guide/MCUBLHOSTUG.pdf" target="_blank"&gt;MCUBLHOSTUG.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;On the link above BLHOST could use the command get property 1 to confirm the board has communication (on ISP mode) with the Host, then use flash-erase-all.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2024 02:34:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Fail-debugging-frdm-mcxn947/m-p/1994152#M1980</guid>
      <dc:creator>Pavel_Hernandez</dc:creator>
      <dc:date>2024-11-14T02:34:48Z</dc:date>
    </item>
  </channel>
</rss>

