Updated STM32CubeIDE, can't find device on target

magene · ‎2024-02-24

I upgraded STM32CubeIDE to version 1.14.1 today and can no longer connect with my target. The process of updating CubeIDE also updated my STLink-V3PWR debugger to V3PWR V4.J3.B1.P4. Now, programs that downloaded and ran just fine yesterday won't download with the "Target no device found" error.

The STMCubeMonitor-Power (version 1.2.1) software can take control, power on the target, get the temperature, reset my target board and can run the ULP Bench Test and report a ULPMark Score. That leads me to believe STMCubeMonitor-Power can download and run a program and my target board is still working. I don't have any other target boards available to try right now.

STM32CubeProgrammer gives a "Error: No STM32 target found!"

I'd appreciate any suggestions about how to fix this issue before I try rolling back the firmware on the debugger.

Here's the error I get in the CubeIDE Console window

STMicroelectronics ST-LINK GDB server. Version 7.5.0

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61234

Status Refresh Delay : 15s

Verbose Mode : Disabled

SWD Debug : Enabled

InitWhile : Enabled

Target no device found

Error in initializing ST-LINK device.

Reason: No device found on target.

Here's the error that pops up the CubeIDE "Problem Occurred" window

Error in final launch sequence:

Failed to execute MI command:
target remote localhost:61234

Error message from debugger back end:
localhost:61234: Connection timed out.
Failed to execute MI command:
target remote localhost:61234

Error message from debugger back end:
localhost:61234: Connection timed out.
localhost:61234: Connection timed out.

Thanks

CMYL · ‎2024-02-27

Hello @magene

Great news to know that you are able to connect your board and erase its flash.

- For boot there are 2 parameters, boot0 pin (controlled by boot switch) + BOOT_ADD0 (by default user flash 0x800_0000) and BOOT_ADD1 (by default system flash 0x1FF0_0000).

- Connecting BOOT0 to gnd is the same thing as putting the boot switch into userflash position. If not working with putting the boot switch, may be the the switch is damaged!! ,

- Choosing the system flash as boot (boot switch or Boot pin to VDD), means you are executing the embedded bootloader. No need in your use case as the bootloader is used to reprogram the flash memory using one of the serial interfaces (usart, i2c ....)

- By default all the nWRPx must be checked, means that there is no sector in the flash that is write protected. Do you changes these nWRPx option bytes ? If not, does you application have some code changing the nWRPx flash option bytes ? if none among above did, means that there is an issue in the hardware !!!

- One more possibility to answer, why nWRPx is set, bootloader in the system flash is setting WRPx but I double checked it is not the case !!!

Best regards,

Younes

marimuthu02111982 · ‎2024-09-05

same problem here but i am using bluepill stm32f103c8t6