Skip to main content
Senior
March 10, 2022
Solved

STM32WL55 dual core debug _ error 18 when debugging CM0+

  • March 10, 2022
  • 12 replies
  • 15330 views

Hello,

I have started to use stm32wl55 nucleo.

I try to debug a basic application.

I start by debugging CPU1 (CM4) than after booting CPU2 (CM0+) i run the debug for the second CPU.

But ST-LINK: Could not verify ST device!

error details :

Error in final launch sequence:

Failed to start GDB server

Failed to start GDB server

Error in initializing ST-LINK device.

Reason: (18) Could not verify ST device! Abort connection.

Any suggestion ?

Thank's.

Best answer by mattias norlander

Hi,

Yes, unfortunately a regression bug has been confirmed with respect to debugging of STM32WL Cortex-M0+ core in STM32CubeIDE 1.9.0 vs previous versions. 

  • Short-term: The few number of users affected are advised to use STM32CubeIDE 1.8.0 which contains a matching feature set with respect to STM32WL development.
  • Long-term: The final fix will be delivered in the next STM32CubeIDE version.

Sorry for the inconvenience!

Kind regards, Mattias

12 replies

malarabAuthor
Senior
March 11, 2022

1- CM40693W00000KcGqsQAF.png 2- CM0P

0693W00000KcGs5QAF.png0693W00000KcGsKQAV.png

malarabAuthor
Senior
March 11, 2022

here is my debug config :

CM0P :

0693W00000KcGyxQAF.pngCM4 :

0693W00000KcH0TQAV.png

LaurentL
ST Employee
March 11, 2022

Hello,

The debug configs look good.

Maybe add one to the port on CM0+ debug config.

But you should download CM0+ application code with the CM4 core.

To do that, go to the startup tab (of CM4 debug) and add the CM0+ elf download.

And In the CM0+ startup tab, select the elf and edit to remove the download (keep the load symbols).

Rgds,

Laurent

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.
malarabAuthor
Senior
March 12, 2022

Hi LaurentL,

i have already do that. but it is not working !

i have repeated the same staps in this video https://youtu.be/QBEfewpPTSk

when i run an application the code in CM0P is executed ...so it is work correctly but not in debug mode !

LaurentL
ST Employee
March 14, 2022

Hi,

Did you change the Option Bytes config ?

Because I can see the DDS option bit (in Security Configuration OB) that should be unchecked to be able to debug CM0+.

Can you check with STM32CubeProgrammer that this bit is unchecked please ?

And is the security enabled ?

Option bit ESE in Security Config OB ESE tab above PCROP.

When you say you are trying a simple application, is it dealing with RF on CM0+ ?

Or really simple as the default "Empty" project or "Cube" project created with STM32CubeIde new project ?

Maybe the CM0+ application is going to low power mode ?

Can you try the simple empty project ?

Rgds,

Laurent

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.
malarabAuthor
Senior
March 21, 2022

Hi Laurent,

The applications which i tryed are : a dual core empty project and a blinking led project.

Finally, the problem was resolved by using CubeIDE v1.8.

Louis AUDOLY
ST Employee
March 17, 2022

Hello all,

We also encounter an issue with the last version of STM32CubeIDE v1.9.0. Rolled back to v1.8.0 could also resolve your issue if LaurentL's solutions did not resolve it already !

Best regards

malarabAuthor
Senior
March 21, 2022

Hi Laudo,

Thank you, the problem was resolved by returning to v1.8

mattias norlander
ST Employee
March 31, 2022

Hi,

Yes, unfortunately a regression bug has been confirmed with respect to debugging of STM32WL Cortex-M0+ core in STM32CubeIDE 1.9.0 vs previous versions. 

  • Short-term: The few number of users affected are advised to use STM32CubeIDE 1.8.0 which contains a matching feature set with respect to STM32WL development.
  • Long-term: The final fix will be delivered in the next STM32CubeIDE version.

Sorry for the inconvenience!

Kind regards, Mattias

Richard Lowe
Senior II
September 6, 2023

We are many releases past 1.9.0. As of today, 1.13, so where is the fix for this issue?

RMeij.1
Associate
December 8, 2022

Hello,

I am experiencing the same issue. I have updated to 1.11.0 hoping this would solve the problem but the same happens. There is no 1.8.0 on my system, before 1.9.0 there is 1.7.0.

Any suggestions?

Gr.RFM

DDong.2
Associate
February 28, 2023

Hi

I have upgraded stm32cube to 1.11.2 now. I'm experiencing the same issue too.

Would you like to tell me when we will get this fix ?

Richard Lowe
Senior II
August 25, 2023

I have the same issue on the STM32H747I-Eval board. Does not validate the CM4 core. I'd also like to know when this is being resolved.

Screenshot from 2023-08-25 13-16-10.png

Visitor II
December 23, 2023

I am using STM32H745 and I am facing this issue and I have searched for any one who has a solution but I can't find any one.

I am using cube ide 1.14 and have the same issue

ANy one can help?