2022-12-02 04:18 AM
I use STM32GO1291. when I was debugging I got an error (its picture attached in below ) also my LD3 is not blinking anymore. is microcontroller damaged or there is some other things wrong? why it isn't blinking anymore when I plug!
2022-12-02 05:24 AM
no blink -> damaged program or chip.
try:
debug configuration -> debuggger -> reset mode : hardware reset (+ connect under reset).
if no response,,,chip killer.
2022-12-02 05:46 AM
Hello @MFara.4,
Thank you for posting 😉!
LED3 is a user led on the NUCLEO-G031K8 that blinks when the default demonstration (firmware loaded by default in the MCU flash memory) is executed (UM2591 page 6).
Since you have managed to debug your application for the first time, you have erased the default demonstration from flash memory and have loaded your own application (in which you're not blinking the led). Which is fine and doesn't indicate that the microcontroller is damaged.
As for the debugging issues, could you specify whether you are using PA13 or PA14 in your application?
Thanks,
Aziz
2022-12-02 05:51 AM
Thanks for the reply!
sorry for simple question as I am beginner! how can I make it default again.
2022-12-02 06:04 AM
First you have to be able to load new firmware into the MCU. Can you connect under reset?
I suggest:
1- Downloading and installing STM32CubeProgrammer available under this link.
2- Trying to connect under reset
2022-12-02 06:27 AM
If you are able to connect, that means that the MCU isn't damaged and that your application is somehow preventing the debug access (by using PA13 or PA14 as GPIOs for example). You can then perform a full chip erase: and download a led blink application. An example is located under:
STM32Cube/Repository/STM32Cube_FW_G0/Projects/NUCLEO-G031K8/Examples/GPIO/GPIO_IOToggle
If you can't connect, most probably the chip is damaged.
I hope you find this helpful.