swd configuration no device detected

[Transidico]

Good eavening,

Unfortunately, after programming the flash incorrectly, I can no longer find the target.
I tried deleting the .launch file; it sees that there is a card but can no longer find it.
I do not have an external debugger. How can I repair the target?

Thanks in advance.

[Transidico]

Let me explain what happened: I'm using the frdm-mcxc242 board with the integrated mcxpresso console. I wanted to try making a very simple program that would save a variable to the flash drive by inserting it from the console. It saved and read the variable to the flash drive 3 or 4 times, then at a certain point it showed me the screen shown before: SWD no device available.

I don't use external debuggers, but I need to recover the board. I tried pressing the reset button and restarting the PC, but it didn't work.

Was the board lost?

[Pablo_Ramos]

Hi @Transidico,

Can you help me test whether updating the firmware of the LPC55S69 resolves your issue?

You can follow the steps outlined in the following post:

How to update the debugger of the MCX - N & MCX - A - NXP Community

To set the EVK into DFU mode on the FRDM-MCXC242, you need to close jumper JP1.

Best Regards,
Pablo

[Transidico]

Good morning Pablo,

I tryed to do the programming the LPC55s69 but it didn't work. I also tryed to do the mass erase of the flash and also not work.

If i delate the file .launch i can see the device

but when I try to recharge, it does not recognise the device:

I really wouldn't know how to do that.

Thanks. Best regards

[Transidico]

Mass erase console: Executing flash operation 'Erase' (Erase flash) - Wed Sep 10 10:16:37 CEST 2025
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v24.9 (Sep 19 2024 19:34:05 - crt_emu_cm_redlink.exe build 802)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/Users/transidico/Desktop/workspace2/TB1585/Debug\MCXC242.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: MCXC_connect.scp =============
MCXC Connect Script
Connecting to Probe Index = 1
This probe = 1
This TAP = 0
This core = 0
DpID = 0BC11477
Assert NRESET
Reset pin state: 00
Power up Debug
MDM-AP APID: 0x001C0020
MDM-AP System Reset/Hold Reset/Debug Request
MDM-AP Control: 0x00000008
MDM-AP Status (Flash Ready) : 0x00000036
Part is secured
Mass Erase Required
============= END SCRIPT ===========================
Probe Firmware: MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.160 (NXP Semiconductors)
Serial Number: D3RQLYWOEAOJ0
VID:PID: 1FC9:0143
USB Path: 0001:000d:00
Using memory from core 0 after searching for a good core
redlink server client - failed to receive response (to op 62) from server after 2000ms - timed out (rc 138)
connection failed - EE(47): Debug Mailbox Request Failed... Retrying
redlink server client - failed to receive response (to op 12) from server after 2000ms - timed out (rc 138)
probe 1 TAP 0 failed to read TAP ID - Ee(FF). Redlink interface error 255.
Failed on connect: Ee(FF). Redlink interface error 255.
Connected&Reset. Was: NotConnected. DpID: 0BC11477. CpuID: 00000000. Info: <None>
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
Debug bus selected: MemAp 0
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
(100) Target Operation Failed
redlink server client - warning - 28 bytes of unexpected data from the server
error closing down debug session - Nn(05). Wire ACK Fault in DAP access
Unable to perform operation!
Command failed with exit code 1

[Pablo_Ramos · Accepted solution]

Hi @Transidico,

What could be happening is that the flash memory is secured. Could you help me check if the memory is protected?

You can do this using the MCUXpresso Secure Provisioning Tool.

Click the UART button (red). This will open the Connection with Target Processor window.
Test the UART connection by connecting the board through the MCU-Link USB (J13) and using Test connection button (green).
If the flash is secured as shown in the picture, you can try the following:

Open the Command Line Interface (blue) and run the command:
blhost -p COM37,57600 -- flash-erase-all-unsecure
Note: The COM port may vary depending on your setup.

Best Regards,
Pablo

[Transidico]

Good morning Pablo,
Thank you very much for your support. I managed to fix it, and now the card is working.
Could you tell me why this happened?

Thank you again.

[Transidico]

Ora capisco meglio il tuo punto. Dici che è l'lpc55s69, che gestisce la porta USB, a non funzionare correttamente. Ma perché?

Grazie ancora.

[Transidico]

I can't figure out what this new firmware has to do with anything. I think if I programmed the flash incorrectly, I think mass erasing the flash will probably fix the problem. If I programmed the flash with a variable from the console and the console abruptly shut down, I programmed the flash incorrectly. Can you tell me if mass erasing fixes this?

Thank you for reply.