mirror of https://github.com/ARMmbed/mbed-os.git
fe9d3174bf
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 |
||
|---|---|---|
| .. | ||
| TARGET_STM32F0 | ||
| TARGET_STM32F1 | ||
| TARGET_STM32F2 | ||
| TARGET_STM32F3 | ||
| TARGET_STM32F4 | ||
| TARGET_STM32F7 | ||
| TARGET_STM32L0 | ||
| TARGET_STM32L1 | ||
| TARGET_STM32L4 | ||