4 Commits (6bd55a16fe5a10b400b3cee1cc2f93bf66147fc6)

Author	SHA1	Message	Date
Russ Butler	47b78a2d17	Fix STM32 crashes on boot due to unset VTOR ... Remove HAL_Init and related code from SystemInit and move it to mbed_sdk_init. The function SystemInit is called early in the boot sequence before RAM is initialized or the VTOR is setup, so it should not be used to perform the HAL initialization. This fixes crashes due the vector table being used before it has been relocated.	2017-06-13 12:12:20 -05:00
Michel Jaouen	4a69072161	INIT:GCC add call to HAL_Init ... system_init, stops all on going timer. gcc _start , perform zero initialized. => HAL_Init must be done again also in GCC toolchain	2016-10-27 10:40:28 +02:00
Laurent MEUNIER	fe9d3174bf	INIT:GCC no rtos: Align pre-main initialization steps between TCs ... Various toolchains supported in MBED don't follow the same initialization steps. This can have impacts on platform behavior. For STM32, it is needed to call the HAL_Init() _after_ the RAM has been initialized (sdata from flash / zero initialized data) and _before_ the C++ objects are being created, especially if those objects require support of tickers for instance. In GCC, this is easily done because SystemInit is called after the ram initialisation, so HAL_Init does not need to called from mbed_sdk_init. this is covered by the changes in mbed_overrides.c files. This series should solve issue reported here: STM32 (At least F401) breaks if Tickers are activated in a global object #2115	2016-10-04 14:55:20 -05:00
Christopher Haster	0bad622a16	restructure - Moved targets out to top level ... hal/targets -> targets hal/targets.json -> targets/targets.json	2016-09-30 19:18:09 -05:00