-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Windows not detecting device after reconnecting. #16
Comments
several others had this issue, thread was hyjacked by console not found complaints then marked as invalid. i would be personally willing to ship one of my boards to somebody in Aust for testing to find the fault |
I'm not sure this is a hardware issue on my end, I've spoken to balika and will be dumping the spi when I get the chance. I find it odd version 2 of firmware works with no issues and version 3 doesn't. I'm in aus but can't really do hardware testing atm |
i bought 20 between our 2 aussie official suppliers had had same issue in both batches- 6/20 failed. i also found it extremely odd V2.0 works but 3 doesnt. |
I just tried holding the chip in a few different places with no luck, I'm wondering if they could be fake chips like this post in one of the other threads. mine is hard to read I would be interested to see if the 6 you have are the same, or they are different. I definitely need to order another pico or two though for other projects |
further inspection, can confirm ALL the picos that failed are very faint marking on chips, ALL working picos have a very white logo. i still am confused about pressure on chip as all of my boards worked that way. |
i have this same issue, my pico was from a authorised seller and does not look fake, it will not reconnect to windows at all with version 3 once disconnected, i have to reflash to get it to be recognise. pressing the chip makes no difference. Using version 2 i can reconnect, i hear the usb connect sound and the com port is immediately recognised, |
Does yours have a very faint logo on it or a nice bright one? |
Nice bright logo. looks perfect. |
Huh, could you maybe try holding at points on the chip like what was suggested earlier? |
As I said in my first message, pressing the chip makes no difference. |
Ah derp I was tired ahaha Odd so yours has bright printing on the chip? Curious indeed |
II had the same problem and it occurred to me to press hard on the main IC to see if it was a cold solder and it work. I did a little reflow and it hasn't given me any problems. In case someone else tries it and know if that is the cause of the problem. |
Hey guys! im from brasil. Mi pico have a very faint logo, so its fake right? =( ive pressed on chip (discredited) and it worked. you have to press on silver chip near the RB logo |
Upon initially flashing picoflasher 3.0 to my Raspberry Pi Pico, it is detected by windows and J-runner correctly and I am able to use it as such.
The problem occurs once I've disconnected the pico and reconnect it to my computer.
When I plug it back in windows doesn't detect the device unless I enter it back into flashing mode to flash a different .uf2 file to it.
While I can work around this, by reflashing the firmware it is a pain to have to do it every time.
Important Information
Device: Raspberry Pi Pico
Firmware: PicoFlasher 3.0
Operating System: Windows 10 Pro (Ver 21H1 OS Build 19043.1826)
Software: J-Runner with Extras 3.1.5b & J-Runner Pro v3.2.0
Edit: Quickly testing with PicoFlasher 2.0 this issue does not happen
The text was updated successfully, but these errors were encountered: