#1290 STM32_NO_INIT problems

[Edoardo Lombardi]

When the STM32_NO_INIT mode is enabled in an application, the low-level HAL code imposes a specific clock

#if STM32_NO_INIT || defined(__DOXYGEN__)
#define STM32_SYSCLK                STM32_HSICLK

This is logically incorrect, as the NO_INIT mode is typically used when the application is launched by a bootstrap or bootloader that has already taken care of clock initialization. Therefore, it's essential that the application uses the same clock chosen by the bootloader (already configured and initialized).
It is the responsibility of the user writing the application to ensure that the correct clock value is set in the mcuconf.h file.