-
Notifications
You must be signed in to change notification settings - Fork 442
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 7 sometimes does not recognize the device as serial port #96
Comments
Thanks for the tip. I have a Win7-32 laptop. This gets a Serial Terminal and Program Upload. Opening the Arduino Serial Terminal does not reset the Pico. But my big problem is Win10-64 Desktop PC. After toggling power I see PicoArduino (COM23) in the Device Manager. Has Win10 installed the correct Driver ? David. |
I've just gone through this process, and that wasn't exactly what I saw, so here are some screenshots which might make it clearer to someone else. The serial port was shown as PicoArduino. Zadig (1) - Immediately after plugging in the Pi Pico, Zagig sees PicoArduino which shows as no driver, WinUSB Zadig (2) - PicoArduino (2E8A) needs to be set to USB Serial (CDC), using the arrow keys next to the driver type, then pressing Install Driver. Zadig (3) - PicoArduino (2E8A) after pressing Install Driver it looks like this: |
Windows 7 sometimes does not recognize the device as serial port, even after fresh reinstalling using BOOTSEL button. You still can upload sketch using BOOTSEL mode manually, but it requires disconnecting device each time. Simply, the issue disable easy upload and auto-restart feature.
There is "ArduinoPico" unrecognized device in the device manager list with ID:
USB\VID_2E8A&PID_000A&REV_0100
or similar. I am using Arduino IDE 1.8.13. Using different USB port didn't help. Restarting the IDE didn't help. On Windows 10 the same board works without any problems.I found solution to make it work also on Windows 7:
(from https://www.onetransistor.eu/2021/02/set-up-raspberry-pi-pico-for-microphyton.html , btw: I used "Install driver")
Tested on Windows 7 that had previously this issue. Maybe you can add it to README or somewhere?
The text was updated successfully, but these errors were encountered: