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 | |
|---|---|---|---|---|
| Custom PCB STM32G071RB stuck on run program: 3% | 0 | 362 | March 6, 2023 | |
| Problem going from development board to custom board | 14 | 1570 | May 23, 2022 | |
| Please let me know what to do after chip erase. | 12 | 1300 | July 27, 2023 | |
| Mbed does not start | 2 | 620 | February 1, 2021 | |
| STM32F767 Chip Code Compatibility | 9 | 778 | October 30, 2020 |