Fixed, found that mbed does the clock initialize from within the target. Found in “mbed-os/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F407xE/system_clock.c” just changed to select external crystal and do no other clock setup in main.cpp. Clock setup is done from there when calling HAL_Init(). Going to test the UART tomorrow to see if the same frame error persists now that we are at 168MHz. Thanks for the feedback.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| "SetSysClock failed" on STM32L432 custom board | 8 | 1220 | March 29, 2021 | |
| Custom PCB STM32G071RB stuck on run program: 3% | 0 | 376 | March 6, 2023 | |
| Problem going from development board to custom board | 14 | 1681 | May 23, 2022 | |
| How to port Mbed on custom exact replica board? | 3 | 540 | August 14, 2020 | |
| SetSysClock fail on my own board similar to Nucleo- STM32L476 | 11 | 228 | August 14, 2024 |