Skip to main content
Associate
August 1, 2024
Solved

NUCLEO-L552ZE-Q cant be programmed with STM32CUBEIDE

  • August 1, 2024
  • 2 replies
  • 2330 views

Hi,

I have recently purchased a NUCLEO-L552ZE-Q and I am trying to program it using the STM32CUBEIDE but it will not program. I get the following in the console:

 

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...
Shutting down...
Exit.

 

The microcontroller has to then be reset manually but it isn't programmed and the default led cycle program runs.

Am I doing something wrong? I have had another nucleo board working just fine, the F767 I believe.

 

Thanks

Best answer by Mahmoud Ben Romdhane

Hello @TelepathicWalrus ,

 

This issue has already been reported to the development team under the internal ticket: 186929.

 

Thanks.

Mahmoud

2 replies

Technical Moderator
August 1, 2024

Hello @TelepathicWalrus ,

 

First let me thank you for posting and welcome to the ST Community.

For more investigation, I suggest please that you provide the STM32CubeIDE version.

 

Thanks.

Mahmoud

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate
August 1, 2024

I have tried both 1.15.1 and 1.16 but both do the same, curiously i can program it with the stm32cubeprogrammer but obviously i am unable to do any debugging.

Technical Moderator
August 1, 2024

Hello @TelepathicWalrus ,

 

This issue has already been reported to the development team under the internal ticket: 186929.

 

Thanks.

Mahmoud

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate
August 2, 2024

I appear to have the exact same issue