2025-08-21 2:12 AM
Hi,
I recently bought two NUCLEO-WL55JC1 boards and was testing the SubGHz_Phy_PingPong example to establish communication between them. Everything was working fine at first, but at some point (I’m not sure if I changed anything), one of the boards stopped being recognized by STM32CubeIDE when trying to debug.
The error message is:
"Target no device found. Error in initializing ST-LINK device. Reason: No device found on target."
When I connect the board to the PC via USB, it is detected, but a FAIL.TXT file appears with the message:
"The interface firmware FAILED to reset/halt the target MCU".
I know the firmware is still loaded because, when powered, this board still sends messages that are received by the other one (which works normally).
The jumpers on both boards are configured the same way, and I have tried debugging through both USB and SWD without success.
Is there a way to make STM32CubeIDE detect the board again? What could be the cause of this issue?
Thanks in advance for your support.
2025-08-25 9:55 AM
Hello @blnc__ ,
I think that the MCU cannot be accessed by the ST-Link, not connected by SWD wires to SWD interface.
So, check the correct MCU connection to ST-Link and ensure that the ST-LINK firmware is up to date.
Also, make sure that you are using a data cable (not a charging one).
With CubeProgrammer, try connecting "under reset" and erase the firmware.
Please see this article: How to solve connection errors when connecting and programming the STM32 target board
2025-08-26 11:34 PM
Hello, thank you for the reply.
In CubeProgrammer, it lets me update the firmware but when trying to connect under reset (at the same time pressing the reset button) the error "Unable to get core ID. No STM32 target found." appears.