-
Notifications
You must be signed in to change notification settings - Fork 24
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
Tried with CH568L , unsuccess. But solution found :) will place PR in near weeks. #20
Comments
Small update:
In short minimal change which is needed is checksum calculation update. I checked with my CH568 chip based board and it works after code modification. |
Cool. I have my local version with debugging support, but it prints way too much stuff, and don't get time to clear it up. Welcome, PR! |
I suspect you might need the new key for newer bootloader versions that @pablomarx found in pablomarx@280d7ef and that I've included in my pr #22 i'm kinda curious whether it's bootloader version or "chip sub id" version that determines this, but I'd kinda lean towards bootloader version, rather than chip sub id |
@karlp It depend on "chip sub id" (we can call it other name) and it gotten from disassembled (and converted to C) original WCHISP software. Here is key generation function :
|
First of all , nice work !
But, would like to see more output.
Like:
Erasing ...
Flashing ...
Verifying ..
I added :
and got response when tried to flash:
But board do not startup / do not work.
When uploading with WCHISPTool 3.0 result in working board.
Will continue next week, will try to capture USB traffic for both applications.
The text was updated successfully, but these errors were encountered: