Skip to main content
Graduate
January 21, 2022
Question

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

  • January 21, 2022
  • 2 replies
  • 817 views

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.

    This topic has been closed for replies.

    2 replies

    Technical Moderator
    January 24, 2022

    Hello @Eakyo.1​ ,

    Have you upgraded the ST-link firmware?

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

    Imen

    Eakyo.1Author
    Graduate
    January 25, 2022

    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.

    Technical Moderator
    January 25, 2022

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

    Eakyo.1Author
    Graduate
    January 26, 2022

    So I can't just use stm32cubeide?

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