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
It would be really nice if we got an error when the CH341 is unable to communicate with the EEPROM instead of just reading 0xFF and having to guess if we're reading an empty EEPROM.
aystarik added this feature in his fork and that feature works, but unfortunately aystarik changed a ton of other stuff and after playing around with their fork it's obvious to me that it's buggy and unreliable.
If someone wants to have a look at how aystarik did it then the relevant commit is here
The text was updated successfully, but these errors were encountered:
It would be really nice if we got an error when the CH341 is unable to communicate with the EEPROM instead of just reading 0xFF and having to guess if we're reading an empty EEPROM.
aystarik added this feature in his fork and that feature works, but unfortunately aystarik changed a ton of other stuff and after playing around with their fork it's obvious to me that it's buggy and unreliable.
If someone wants to have a look at how aystarik did it then the relevant commit is here
The text was updated successfully, but these errors were encountered: