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
I have some STLink v2 clones that I wanted to program with Blackmagic Probe firmware. If I run stlink-tool on macOS with the precompiled .bin file from the BMP project, stlink-tool will show a progress on sending the firmware, and act as if everything went well, but the actual hardware seems to still be running the original firmware, as if nothing had happened. Any clue what might be going on here? I am a bit mystified.
Can you take apart your adapter to check what's inside? Around two years ago STM32F1 supply was getting scarce and STM32F1 started getting really popular. These clones may or may not be suitable replacements for the original parts.
I think stlink-tool triggers DFU exit as well? It only responds with valid data once at least. I don't think the offset is an issue, that should cause a failure to run afterwards (and BMP is designed to be used specifically with stlink-tool anyway). The adapters are quite a few years old, probably closer to five years old.
I have some STLink v2 clones that I wanted to program with Blackmagic Probe firmware. If I run stlink-tool on macOS with the precompiled .bin file from the BMP project, stlink-tool will show a progress on sending the firmware, and act as if everything went well, but the actual hardware seems to still be running the original firmware, as if nothing had happened. Any clue what might be going on here? I am a bit mystified.
@UweBonnes might have some idea?
The text was updated successfully, but these errors were encountered: