STM32F10x_Startup does not call SystemInit

Follow

Franz Trierweiler

• February 29, 2012 10:28

Hi,

Rowley start-up code for STm32F103 does not call SystemInit, whereas ST "official" startup files (provided with STM standard lib v 3.5) call SystemInit before branching to main. In this case, when entering the main, the core clock is already configured:

 

; Reset handler
Reset_Handler PROC
EXPORT Reset_Handler [WEAK]
IMPORT SystemInit
IMPORT __main
LDR R0, =SystemInit
BLX R0
LDR R0, =__main
BX R0
ENDP

This means that when generating a STM32F103 project from scratch with Crossworks (which generates its own startup files), you cannot simply use STM32 samples and its standard peripheral lib v3.5 (by adding it to your project tree). Roawley startup files must be replaced with ST ones, unless you call SystemInit from the main (in fact I did not try the first option since I guess there might be troubles with the label naming...)

Thus here are my questions:

1/ Do you plan to support STM32F103 lib 3.5 (as Rowley packages)  with the right ST startup files ?

2/ Why does not ST include Crosswork start-up files in its CMSIS/CM3/DeviceSupport/ST/STM32F10x/startup ?

 

Regards,

Franz

0

• 

  Michael Johnson

  • February 29, 2012 12:05

  The STM32 CPU support package does call SystemInit and uses the ST CMSIS header files.

  I guess you are using the obsolete STM32F10x CPU support package?

  0

  Comment actions Permalink

Please sign in to leave a comment.