-
Notifications
You must be signed in to change notification settings - Fork 168
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
Problem with unbricking CH32V003J4M6 using WCH-LinkE #484
Comments
See here the procedure/trick with minichlink -u (required a power off) |
I also have the same issue, even thou I used the suggested method. |
Hi there! Thank you for your reply. I tried the trick in the video but it didn't work. In theory, the programmer can control its power output and power off the MCU by itself and that's how the official tool works. However, rvprog, a python-based CH32Vxxx utility, works just fine. So I think it should be the problem of minichlink. |
What issue did you have with minichlink? (What what physical programmer are you using) I've tried to make it as robust as possible for unbricking. |
I used wchlink-e with firmware version v2.15 as my programmer and tried to unbrick a SOP-8 CH32V003J4M6. I tried
|
This is a little surprising. Is this in Windows? Or Linux? And, also, are you recompiling the .exe. It's been quite some time since a new .exe has been checked into the main repo. |
Also, you may want to iteratively work on this with some folks live? If you're interested ping me on discord, and I can give you an invite. My name on Discord is |
Hi there! I compiled and uploaded the template code(which uses the debug pin PD1) to the MCU and I found that I couldn't upload other code to the MCU any more. So I tried to unbrick it using command
minichlink -u
but it stuck atConnection starting
for a while and failed. The log is shown below.However, after reinstalling the WCH vendor driver and using "Clear All Code Flash-By Power Off" in the WCH-Link Utility, the MCU was unbricked successfully.
btw, the connection between MCU and WCH-LinkE programmer as well as the version of WCH-LinkE and WCH-Link Utility is shown below:
The text was updated successfully, but these errors were encountered: