-
Notifications
You must be signed in to change notification settings - Fork 10
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
GD32350G-START setup #9
Comments
GDLinkCLI is indeed Windows only. The default upload protocol for the GD32F350G-START is What exact |
I have been manually overriding the An example: When I use the default upload protocol on
|
Well that's not supposed to happen.
So.. openocd is crashing, or a library call it does. I've seen some problems regarding crashes in OpenOCD related to old libusb version, and coincidentally I've packaged OpenOCD with libusb-1.0.dll version 1.0.24. Can you go to If that doesn't get you further you can go to the Linux system, view the invoked command line with the project task Advanced->Verbose Upload, then use I'm also cross-checking this on my Windows + Linux system, since I do have exactly a GD32350G-START board here. |
I tried replacing the I only use the pio cli on the linux system, but on the windows system running the "verbose upload", e.g.,
gives the following:
and running it on linux gives
It seems i get an error 255 on the linux system. Great that you also have the board and can help debug the problem - I really appreciate the help! |
First try plugging the board in and it just works.
I'm powering the board with 2xUSB though, so the above USB port with the switch to the right position and the lower USB port for the actual GDLink are both connected. Can you verify on Windows using Zadig that the "CMSIS-DAP" device has HidUSB drivers loaded? |
On Linux I get the same
Error with the USB device forwarded, but I think that's just a very simple udev rules error / would work with sudo. Let me just add a line in the PlatformIO udev rules.. |
Ah, actually I didn't even have the PlatformIO udev rules installed, silly me. Following https://docs.platformio.org/en/latest/core/installation/udev-rules.html#platformio-udev-rules and logging out & back in again on my Ubuntu 22.04 system made my normal user be able to access to the CMSIS-DAP device and upload it, no problems.
So both Windows+Linux uploads are working for me, hm. |
I got the linux working by installing the udev rules! I verified that I have the exact same HidUSB drivers on the CMSIS-DAP device, but Windows is still giving the If you want to dig deeper into the issue, let me know if there is anything I can help with. If not, then thank you for your help! |
Non-working OpenOCD upload on Windows for some users is indeed absolutely critical. Can you please get GDB downloading https://github.com/brechtsanders/winlibs_mingw/releases/download/12.2.0-15.0.7-10.0.0-ucrt-r4/winlibs-x86_64-posix-seh-gcc-12.2.0-llvm-15.0.7-mingw-w64ucrt-10.0.0-r4.7z, extracting and adding the extracted to the PATH enviornment variable. Then check that in a new terminal (Windows+R ->
Adapt paths as needed. For me it says
|
Hi,
I don't know if this is the right place to ask, but any help will be appriciated.
I have a GD32350G-START development board that PlatformIO does not seem to recognize as a device. I can still compile the examples from this repo (which are great!) and flash them using the gdlinkcli upload protocol on my Windows machine. However, I need to flash the board using a linux machine and obviously can't call the
GD_Link_CLI.exe
, so I was wondering if there is any way to flash the board using without it?My current hardware setup is:
The text was updated successfully, but these errors were encountered: