stm32f0-discovery-basic-template icon indicating copy to clipboard operation
stm32f0-discovery-basic-template copied to clipboard

Possibly wrong Reset_Handler in startup .s file ?

Open MrSpock opened this issue 13 years ago • 6 comments

Hello,

Please correct me if I'm wrong but what would happend after pushing reset BTN on STM32F0DISCOVERY board ? I 'm assuming that program should be restarted and resume operation from start. Insted of it after pressing RESET sample led blinking program stops working. In order to resume normal work I have to turn off/on power.

Here is gdb output when pushing reset button on board:

Program received signal SIGINT, Interrupt.

Reset_Handler () at Device/startup_stm32f0xx.s:71

Src window: │70 Reset_Handler:

│71 ldr r0, =_estack
│72 mov sp, r0 /* set stack pointer */

Is this normal behavior ?

MrSpock avatar Jun 21 '12 20:06 MrSpock

Sorry for formating - I wasn't expecting this after submiting my issue :/

MrSpock avatar Jun 21 '12 20:06 MrSpock

You may be right. I experience a similar problem. After I program the chip (using OpenOCD) it runs just fine until I press the reset button. This causes it to freeze. But power cycling the board fixes the issue and then the reset button works as expected.

Unfortunately I don't know what is the root cause or how to fix it. Any thoughts?

szczys avatar Jun 24 '12 21:06 szczys

Thanks for confirmation that you have similar symptoms. I have working similar template for STM32F1xx (gcc and make based build), so I will try compare those two in next few days so maybe solution will emerge.

MrSpock avatar Jun 25 '12 16:06 MrSpock

@MrSpock i have the same problem on STM32F0d (first reset after programming using OpenOCD makes board freeze, power off-on fixes it) and would like to know if you found a solution.

temoto avatar Jan 27 '13 22:01 temoto

Hallo. Have the same problem. MCU STM32F051C8. I try to use ST-Link on STM32VLDISCOVERY and STM32F4DISCOVERY boards. Help me please, Is any solutions?

a-golosnyak avatar Dec 31 '14 11:12 a-golosnyak

Hallo, colleagues. 2 days later I found the cause of the problem. BOOT0 was not pull down.

a-golosnyak avatar Jan 02 '15 14:01 a-golosnyak