cancel
Showing results for 
Search instead for 
Did you mean: 

Why stm32cubeide(version:1.8.0) don't debug with stm32l4p5?

Eakyo.1
Associate III

Hi,

I am working with stm32l4p5,i use stm32cubeide(version:1.8.0). It fail to start during debugging because of hardfault.

Also it doesnt connect with st-link utility but it connects with stm32cubeproggramer. And after the procedure full chip erase with stm32cubeproggramer, debugging is completed.

Thank you for your help.

4 REPLIES 4
Imen.D
ST Employee

Hello @Eakyo.1​ ,

Have you upgraded the ST-link firmware?

Have you checked if this behavior has occurred with other boards?

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen
Eakyo.1
Associate III

Yes,i have upgraded the ST-link firmware but there was no solution.

Yes,i checked. This behavior has occurrred only stm32l4p5cet6.

Also while it erases full chip,i have fault of "The elf loader file is not accessible" at st-link utility.

Yes, in fact ST-link utility does not support the new MCU, and it's recommended to use STM32CubeProgrammer with this chip.

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen

So I can't just use stm32cubeide?

Do i have to do "full chip erase" before debugging(STM32CubeIde) at STM32CubeProgrammer?