9 years, 1 month ago.

The init code for peripherals is called at instantiation time and it will derive clock settings by checking the SystemCoreClock variable. That variable should always reflect the basic systemclock. When you use own code to change the clock of the processor by manipulating the clocksource or the PLL or some other means it will result in incorrect peripheral clocks and thus wrong baudrates for UART, SPI, I2C and possibly tickers etc. So be careful when touching the clock in your own main code. Best way to do this is by using the mbed-src instead of the mbed lib and modify the system init files for the clock. In case you want to use the lib and still change the clock in your own main you can correct the baudrates by explicitly calling the serial.baud() method again after changing the clock. That should result in a recalculation using the new SystemCoreClock value.

Note that by default the nucleos use the internal high speed RC clocksource. That clock is not as accurate as a crystal and this could explain some discrepancy with the exact baudrate. There are also some baudrates which can not be generated accurately (or even at all) at specific SystemCoreClock values. The difference should stay within the tolerance range of most UART receivers/transmitters.