-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different SWD Programming Pins #9
Comments
Thank you for the info. I will add it to readme. How does your GD board looks like? |
I can add a photo of two more boards that use this pinout: Thing is, while they can be unlocked (throwing an error, but it works after) and erased, flashing fails - similar to "flashing fails" issue, maybe? |
@mamert thanks for the input. For you which board works and which one not? |
Both behave identically (fail). Though I have not had a single success with the sideboards, |
Hi! I have a similar situation, but it's important to me. SWD
First I clicked Option Bytes and selected disabled, got an error message "Failed to set option bytes! Please reset the target and try again", but the firmware has been erased, and the Erase Chip is running successfully. |
I have the same issue here with a YST board - no upload possible (and i checked the chip 5 times if it is a GD32F130 ...) - interestingly it shows as a :STM32F10xx Medium-density in ST-Link. Has anybody sorted this out yet? |
WDG_SW option should be set. |
Can you explain how you did the flashing via st-flash? |
@derFrickler, nevermind, I was wrong. |
Great! seems that did the trick. |
On my hoverboard sideboards the SWD programming pins differ from the ones specified in sideboard pinout. From top -> bottom mine go:
It took a while to figure out since I thought there was something wrong with my STLINK/V2 programmer, so it might help others with the same board to add a notice in the readme for that.
The text was updated successfully, but these errors were encountered: