-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
Fails to flash using a GD-Link, a CMSIS-DAP debugger #189
Comments
The GD32VF103 is a RISC-V based chip, not an ARM chip, so we need to use JTAG for the connection. |
Is this still an issue or could you fix this by using JTag as a protocol @luojia65 :) |
This is not implemented yet, we don't support raw JTAG for RISC-V using CMSIS-DAP. |
Oh I am sorry, I completely forgot that JTag is not supported on CMSIS-DAP yet. |
Is this issue solved? What I want to say here is, ... |
Thew problem here is that JTag is not implemented for CMSIS-DAP. If you want to put in the effort, please feel free to do that, I would gladly accept a PR. But it's so rarely used I don't see fit to put my time into it :) |
Thanks for your reply. If no one is working on it, then I'll happily do it. I can't estimate how long it will take though. I'll get back here when I get something ready to show you. |
Hi! Not much progress. I was playing around with GD32V bootloader. As for probe-rs, I could proceed to the point ram_download example completes successfully. If Disasm-san or anyone is to get this done, I won't be pissed at all. No worry there. |
To support GD32V flashing we need three things:
|
@Tiwalun I tried running cli with |
189: Bump git-version from 0.3.4 to 0.3.5 r=Tiwalun a=dependabot[bot] Bumps [git-version](https://github.com/fusion-engineering/rust-git-version) from 0.3.4 to 0.3.5. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fusion-engineering/rust-git-version/commit/e46c2f3f7d6954f421bf829abc4fe3ecfd565135"><code>e46c2f3</code></a> Bump version to 0.3.5.</li> <li><a href="https://github.com/fusion-engineering/rust-git-version/commit/3dbe2ad73e18f0472d1e6d8dacda2425b310a5de"><code>3dbe2ad</code></a> Include COPYING file in macro crate.</li> <li><a href="https://github.com/fusion-engineering/rust-git-version/commit/f40e32dbb0cb8cfde94e1570eac9f7f739de0655"><code>f40e32d</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/fusion-engineering/rust-git-version/issues/13">#13</a> from kingsimmy/patch-1</li> <li><a href="https://github.com/fusion-engineering/rust-git-version/commit/2c2c3a43ff7e4098be7a2670362cd0ed79d6e21b"><code>2c2c3a4</code></a> Update lib.rs</li> <li>See full diff in <a href="https://github.com/fusion-engineering/rust-git-version/compare/v0.3.4...v0.3.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=git-version&package-manager=cargo&previous-version=0.3.4&new-version=0.3.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting ``@dependabot` rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - ``@dependabot` rebase` will rebase this PR - ``@dependabot` recreate` will recreate this PR, overwriting any edits that have been made to it - ``@dependabot` merge` will merge this PR after your CI passes on it - ``@dependabot` squash and merge` will squash and merge this PR after your CI passes on it - ``@dependabot` cancel merge` will cancel a previously requested merge and block automerging - ``@dependabot` reopen` will reopen this PR if it is closed - ``@dependabot` close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - ``@dependabot` ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - ``@dependabot` ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - ``@dependabot` ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
GD32Vxxx-START boards unfortunately seem to be impossible to source :( |
Describe the bug
I tried to flash with a GD-Link debugger (CMSIS-DAP) connected, but error occurred.
To Reproduce
Steps to reproduce the behavior:
cargo flash --example vf103c-start-blinky
Expected behavior
The program should be flashed and the LED light blinks.
Stacktrace
No stacktrace available
Desktop (please complete the following information):
Additional context
RUST_LOG=debug
report:Full
RUST_LOG=trace
report:https://paste.ubuntu.com/p/V5ygXJSqTz/
The text was updated successfully, but these errors were encountered: