You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When target is STM32F103, if MioLink is flashed with a debug firmware, at interface frequency higher than 1MHz, firmware verification (compare-sections) almost always fails (one or more sections - MIS-MATCHED).
This occurs when working over both SWD and JTAG.
Release firmware works fine, even at a frequency of 10MHz.
It seems to be somehow related to context switching, as after moving the GDB task to a core 1, the issue on SWD started occurring much less frequently.
Workaround: for debug firmware to work with STM32F103 (and probably with all STM32F1xx) use interface frequency 1MHz or lower (monitor frequency 1M).
The text was updated successfully, but these errors were encountered:
Misaka0x2730
changed the title
Verification failed on STM32F103 target on interface frequency >1MHz in the debug configuration
Verification failed on STM32F103 target on interface frequency >1MHz in the debug firmware
Oct 18, 2024
When target is STM32F103, if MioLink is flashed with a debug firmware, at interface frequency higher than 1MHz, firmware verification (compare-sections) almost always fails (one or more sections - MIS-MATCHED).
This occurs when working over both SWD and JTAG.
Release firmware works fine, even at a frequency of 10MHz.
It seems to be somehow related to context switching, as after moving the GDB task to a core 1, the issue on SWD started occurring much less frequently.
Workaround: for debug firmware to work with STM32F103 (and probably with all STM32F1xx) use interface frequency 1MHz or lower (
monitor frequency 1M
).The text was updated successfully, but these errors were encountered: