Skip to content
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

Open
timtimmahh opened this issue Nov 20, 2020 · 12 comments
Open

Different SWD Programming Pins #9

timtimmahh opened this issue Nov 20, 2020 · 12 comments

Comments

@timtimmahh
Copy link

On my hoverboard sideboards the SWD programming pins differ from the ones specified in sideboard pinout. From top -> bottom mine go:

  • VDD 3.3V
  • PA14 / SWCLK
  • PA13 / SWDIO
  • GND

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.

@EFeru
Copy link
Owner

EFeru commented Nov 20, 2020

Thank you for the info. I will add it to readme. How does your GD board looks like?

@timtimmahh
Copy link
Author

It looks almost identical to the one in your image I guess it just has some minor pin changes on the SWD interface. I know the main board connector is the same, but I haven't checked the other pins yet.
GD board front
GD board back

@mamert
Copy link

mamert commented Mar 12, 2021

I can add a photo of two more boards that use this pinout:
sideboard

Thing is, while they can be unlocked (throwing an error, but it works after) and erased, flashing fails - similar to "flashing fails" issue, maybe?
The resolution for that issue seems to be "no longer care", but it might be good to know how to identify those that WON'T work...

image
image

@EFeru
Copy link
Owner

EFeru commented Mar 12, 2021

@mamert thanks for the input. For you which board works and which one not?

@mamert
Copy link

mamert commented Mar 12, 2021

Both behave identically (fail).

Though I have not had a single success with the sideboards,
I have built hoverboard-firmware-hack-FOC successfully in the same VSCode,
so the environment is OK

@perdmen
Copy link

perdmen commented Dec 26, 2021

Hi! I have a similar situation, but it's important to me.

SWD

  • VDD 3.3V
  • PA14 / SWCLK
  • PA13 / SWDIO
  • GND

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.
when I click Program & Verify and want to install the firmware I get an error: "Programming error @ 0x8000000!"

IMG_4421

IMG_4414

IMG_4422

@captFuture
Copy link

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?

@Candas1
Copy link
Collaborator

Candas1 commented Mar 21, 2022

WDG_SW option should be set.
Pinout can differ between sideboards, you need to check which pin is connected to vdd, swdio, swclk and gnd.

@redeemarr
Copy link

Just in case, I was able to flash it with st-flash

@derFrickler
Copy link

Can you explain how you did the flashing via st-flash?
cant' get mine flashend as well. Mins is the green boad with the purple connector shown above.

@redeemarr
Copy link

@derFrickler, nevermind, I was wrong.
st-flash flashes the chip with no errors, but it doesn't work.
Make sure you checked nRST_STOP, nRST_STDBY and WDG_SW checkboxes while flashing with ST-Link utility. This was the reason it didn't work in my case.
#25

@derFrickler
Copy link

Great! seems that did the trick.
Thanks a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants