2026-02-23 6:05 AM - last edited on 2026-02-23 6:41 AM by Andrew Neil
Dear STMicroelectronics Community,
I am experiencing a critical issue with my NUCLEO-144 STM32N657X0 EVAL BRD following an attempted ST-LINK firmware upgrade.
During the ST-LINK upgrade process (via STM32CubeProgrammer), the upgrade became stuck and did not complete successfully. After this, the board became non-operational.
Current behavior:
The board is no longer accessible via ST-LINK (SWD).
Flashing is not possible using STM32CubeProgrammer (ST-LINK connection fails).
The target MCU cannot be detected or programmed.
Powering the board via the on-board USB still works, but no flashing/debugging is possible.
The ST-LINK interface appears unresponsive / corrupted.
Actions already attempted:
Power cycling the board
Trying different USB cables and ports
Using STM32CubeProgrammer CLI and GUI
Attempting connection with different reset modes (UR / HWrst / HotPlug)
Verifying BOOT0/BOOT1 configurations
Using macOS (USB device intermittently detected)
It appears the ST-LINK firmware may be corrupted due to the interrupted upgrade process, and I am unable to recover the board using standard tools.
Could you please advise on:
Whether ST-LINK recovery is possible in this state
Any forced recovery or DFU procedure for ST-LINK V3
Whether this condition requires board replacement (RMA)
Board details:
Board: NUCLEO-N657X0-Q
ST-LINK version: ST-LINK V3 (on-board)
Host OS: macOS
STM32CubeProgrammer version: v2.21.0
Thank you for your support. I would appreciate guidance on how to recover the board, as it is currently unusable for development.
Kind regards,
Mahmoud Abdelgyd
2026-03-02 2:50 AM
Hello,
Please first try running directly STSW-LINK007 | Software - STMicroelectronics, and detail the displayed error if any. If no ST-Link device appears in the application, check if it appears at least in the device manager (if on Windows). May you please also precise if the board ever worked before the upgrade attempt or if it was the first action out of the box.
2026-03-02 12:07 PM
> Host OS: macOS
Please try the update on a Windows PC.