Error in final launch sequence - No device on target

alw · ‎2025-02-05

I have a NUCLEO-G491RE board connected to a PC running STM32CubeIDE v1.17.0. On first connection I was prompted to update the firmware on the board, which I did. On successful completion of the update I disconnected and reconnected the board, but the download failed with the attached message.

I have tried several USB cables and also with and without an intermediate USB hub to eliminate these possibilities.

What is the solution please?

alw · ‎2025-02-07

Problem solved, it was just jumper link settings.

JP5 (5V_SEL): 5V_STLK

JP6 (IDD): On

JP7 (BOOT0): Off

Suggestion, rather than the error messages that are provided, have ones that advise users to check thatthese links are correctly fitted.

View solution in original post

Mahmoud Ben Romdhane · ‎2025-02-06

Hello @alw ,

First let me thank you for posting.

For more investigation, I suggest please that you provide your STM32CubeIDE Project.

Thanks.

Mahmoud

alw · ‎2025-02-06

Hi Mahmoud,

Please see attached, a simple enough program that builds ok, just can't run it on the target NUCLEO-G491RE board after updating the firmware on it. Is there a way of manually reflashing the STLink firmware to the NUCLEO board please?

Kind regards,

Al

alw · ‎2025-02-06

Hi Mahmoud,

I hit the limit on private messages.

The only issue I have is that I can't run the application without launching debug, even with selecting Run As STM32C/C++ Application. How do I run without activating debug please?

STMicroelectronics ST-LINK GDB server. Version 7.9.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

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

-------------------------------------------------------------------

STM32CubeProgrammer v2.18.0

-------------------------------------------------------------------

Log output file: C:\Users\al_wa\AppData\Local\Temp\STM32CubeProgrammer_a02844.log

ST-LINK SN : 0039003C3133511237363734

ST-LINK FW : V3J15M7

Board : NUCLEO-G474RE

Voltage : 3.28V

SWD freq : 24000 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID : 0x469

Revision ID : Rev X

Device name : STM32G47x/G48x/G414

Flash size : 512 KBytes

Device type : MCU

Device CPU : Cortex-M4

BL Version : 0xD5

Debug in Low Power mode enabled

Opening and parsing file: ST-LINK_GDB_server_a02844.srec

Memory Programming ...

File : ST-LINK_GDB_server_a02844.srec

Size : 11.86 KB

Address : 0x08000000

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 5]

Download in Progress:

File download complete

Time elapsed during download operation: 00:00:00.326

Verifying ...

Download verified successfully

Target is not responding, retrying...

Shutting down...

Target is not responding, retrying...

alw · ‎2025-02-07

Hi Mahmoud,

I just got the same message about hitting the limit again on private messages

Following one of the other posts I deleted the existing .metadata folder in the workspace so that a new one would be created on launching STM32CubeIDE. I build a simple application based on my Nucleo board (just changing LPUART1 baud rate) and again try to Run As STM32 C/C++ Application. All I want to do download and run the application to the target hardware without invoking the debugger, I never had these problems with previous versions of STM32CubeIDE.

STMicroelectronics ST-LINK GDB server. Version 7.9.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

ST-LINK Failed to get target status

Error in initializing ST-LINK device.

Reason: Unknown. Please check power and cabling to target.

alw · ‎2025-02-07

alw · ‎2025-02-07

Jumper link is on 5V_STLK

alw · ‎2025-02-07

And despite the error message I can upgrade the ST-Link as before, so the cable etc. is ok.

Mahmoud Ben Romdhane · ‎2025-02-07

Hello @alw ,

Further to your comment, I was able to launch the debug session using the STM32CubeIDE Project that you have attached.

I suggest please that you provide the debug configuration.

Thanks.

Mahmoud

alw · ‎2025-02-07

Hi Mahmoud,

I've attached a screen capture of the debug configuration and also having cleared out my workspace, a zip file of that containing the one project, as deleting the previous .metadata folder changed the run sequence such that the GDB server doesn't start.