Skip to main content
Associate
April 18, 2024
Solved

The debugging issue in STM32WL55CC still not fixed in current STM32CubeIDE release 1.14

  • April 18, 2024
  • 2 replies
  • 2098 views

Hi,

I am trying to debug both cores in STM32WL55CC chip. When trying debugging CM0+ i get error. I am using STM32CubeIDE ver 1.14.1 and also tried STM32CubeIDE ver 1.8 per a suggestion in older post, both don't work.

The followings are the configurations and error I am getting. 

asydhom_0-1713468137049.png

asydhom_1-1713468172915.png

M4 running under debug:

asydhom_2-1713468300783.png

and now starting M0 under debug:

 

asydhom_3-1713468337176.png

 

 

asydhom_4-1713468337178.png

M4 code is indeed running but debugger seems preoccupied with it and won’t share the resource for M0 debugging.

Thanks.

Ayman

 

 

 

Best answer by STTwo-32

Hello @asydhom 

I suggest that you take a look at the Application note AN5564. It highlights some of the points to bear in mind while debugging a device in the STM32WL Series. Knowing that I made a STM32 project using NUCLEO-WL55JC1, and I ran the debug session of the Cortex M4 and M0.

Best Regards.

STTwo-32

2 replies

STTwo-32
Technical Moderator
May 29, 2024

Hello @asydhom 

Sorry for my late replay. I've escalated your issue to the Concerned team for more investigation and correction if there is an error (under internal ticket number 182777).

Best Regards.

STTwo-32

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.
STTwo-32
STTwo-32Best answer
Technical Moderator
June 12, 2024

Hello @asydhom 

I suggest that you take a look at the Application note AN5564. It highlights some of the points to bear in mind while debugging a device in the STM32WL Series. Knowing that I made a STM32 project using NUCLEO-WL55JC1, and I ran the debug session of the Cortex M4 and M0.

Best Regards.

STTwo-32

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.