-
Notifications
You must be signed in to change notification settings - Fork 109
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
CLI len(response) < 2 - USB Disconnect? #57
Comments
This error occurs on OS X on both X64 and M1/ARM64 TLDR -> problem starts in zondax/hid but might be caused by: We note a compile warning on junod We think that error message comes from: Which is a response problem from UnwrapResponseAPDU() Adding a little more information to the error, we arrive at the following from time to time: This is due to an APDU of all zeros being read every so often: UnwrapResponseAPDU 0x101, [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0], 0x40 In some cases, disposing of this 0 packet will yield the proper packet (sequenceInt = 0) on the next read. In other cases, the first packet seems to be gone forever. Which may point to a problem in the upstream https://github.com/Zondax/hid READ() where the C.hid_read somehow returns 64 bytes read, but returns a zero filled buffer. Noted the core problem at zondax/hid: |
Related to: Zondax/ledger-go#23 |
Often on CLI TX signing with ledger I get the following error:
The ledger device may or may not display the TX information. (50/50 chance)
Is there a portion of this project we should look into to help improve?
Or is this related to needing to change the protocol used to establish a better connection with the USB device on ledger? (U2F vs HID which might take a significant amount of work?)
The text was updated successfully, but these errors were encountered: