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_DISCO_L053C8 | ||
| TARGET_NUCLEO_L011K4 | ||
| TARGET_NUCLEO_L031K6 | ||
| TARGET_NUCLEO_L053R8 | ||
| TARGET_NUCLEO_L073RZ | ||
| PeripheralPins.h | ||
| analogin_api.c | ||
| analogout_api.c | ||
| common_objects.h | ||
| device.h | ||
| gpio_api.c | ||
| gpio_irq_api.c | ||
| gpio_object.h | ||
| i2c_api.c | ||
| lp_ticker.c | ||
| mbed_overrides.c | ||
| pinmap.c | ||
| port_api.c | ||
| pwmout_api.c | ||
| rtc_api.c | ||
| rtc_api_hal.h | ||
| serial_api.c | ||
| sleep.c | ||
| spi_api.c | ||
| us_ticker.c | ||