NUCLEO-L552ZE-Q cant be programmed with STM32CUBEIDE

[TelepathicWalrus]

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

[Mahmoud Ben Romdhane]

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

[TelepathicWalrus]

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.

[Mahmoud Ben Romdhane · Accepted solution]

Hello @TelepathicWalrus ,

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

Thanks.

Mahmoud

[TelepathicWalrus]

Ah okay so there should be an update to STM32cubeide soon to fix it?

[Mahmoud Ben Romdhane]

Hello @TelepathicWalrus ,

I'll keep you up to date until this thread is fixed.

Thanks.

Mahmoud

[Andrew Neil]

This looks similar?

https://community.st.com/t5/stm32-mcus-boards-and-hardware/issue-deploying-and-debugging-on-custom-pcb/td-p/704754

[John24ssj]

I appear to have the exact same issue

[TelepathicWalrus]

Hi,

Has there been any update yet? I really need to be able to use the debugger, unless there is another method to debug. Also I didn't mark that as the solution. I assume someone from st did but my problem is still here so it's not really a solution.

Thanks

[risho-lizhao]

Hello,

Try to use OpenOCD as debug probe instead of the ST-link GDB server. You can find that in debug configurations - tab debugger.