-
Notifications
You must be signed in to change notification settings - Fork 22
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
Handshake Failed (sp_blocking_read returning 0) #47
Comments
Because on you are specifying chip |
Sorry, forgot to add it to the issue, i have tried using bl70x, same issue with both |
Did you tried another pc / cable? Are you sure you have correct COM port? (you don't need to specify com port on BL70X) |
I will try a new pc later. I have tried all of the above sadly |
I am having the same issue, here is the log:
I got the same error with 5 different USB cables on both my PC & laptop. Tried both USB C to C, and C to A cables. I also tried manually setting the COM of my device to COM10 but got the same error. Could it be that something changed on newer batches of the pinecil 2? |
@kajgies what is the output when --port is not specified? |
I am sure that COM3 is the pinecil. |
@kajgies please, can you open device manager, find the COM3, and find VID & PID? |
It says: |
This is very interesting, it is correct VID & PID. Did you tried to launch it as Admin? |
I tried both cmd & powershell. Tried it as admin too, same result |
@kajgies This is really interesting that even when device is connected and visible, it can't auto-detect or use the port... Maybe antivirus or something? I really never seen this happening. |
Just Windows antivirus. |
I tried linux and here it worked instantly. So for me the problem is resolved. Weird that it didn't work on Windows tho. I tried all the USB ports on a PC & a laptop, very strange. |
Anyone got it solved? I am on Windows 11, unable to flash pinecil v2 :( |
Bump, still a present issue, two machines, two cables, both win 10. |
Pinecil V2
Running v2.20.14DAF70
Windows 10 10.0.19045
The text was updated successfully, but these errors were encountered: