You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a WeAct CH592F, I just tried to config enable-debug and a subsequent config unprotect, but that left me with an inaccessible bootloader. So if this were a CH591 it would be a sure brick since they don't have the swio lines on a pin at all.
I have a linkE arriving so then I could test if the debug interface got activated hopefully, but this command should come with a warning?
The text was updated successfully, but these errors were encountered:
If I am understanding the code correctly, unprotect is hardcoded for the protection bytes in the CH32V20x/30x chips and is entirely inappropriate for the CHxxx chips. Those chips seem to instead need the reset_config command.
On a WeAct CH592F, I just tried to
config enable-debug
and a subsequentconfig unprotect
, but that left me with an inaccessible bootloader. So if this were a CH591 it would be a sure brick since they don't have the swio lines on a pin at all.I have a linkE arriving so then I could test if the debug interface got activated hopefully, but this command should come with a warning?
The text was updated successfully, but these errors were encountered: