All of those are Raspberry Pi Pico VID:PID and it wouldn't surprise me if the "Unknown USB Device" failure was as well. Windows remembers what it has seen and it's not possible to tell from that what is active and what isn't.
Device: Périphérique USB composite ============================== BOOTSEL mode
Vendor ID: USB\VID_2E8A
Device ID: PID_0003
Device: Dispositif de stockage de masse USB ======================= BOOTSELmode
Vendor ID: USB\VID_2E8A
Device ID: PID_0003
Device: Périphérique USB composite ============================== PlatformIO serial port
Vendor ID: USB\VID_2E8A
Device ID: PID_00C0
Device: Périphérique USB inconnu (échec de demande de descripteur de périphérique)
Vendor ID: USB\DEVICE_DESCRIPTOR_FAILURE
Device ID:
Device: Périphérique USB composite ============================== MicroPython serial port
Vendor ID: USB\VID_2E8A
Device ID: PID_0005
The USB\DEVICE_DESCRIPTOR_FAILURE appears even when the pico isn't plugged.
My guess is that failure might be what should be COM4.
My first test would be to upload MicroPython and see if that presents itself as a COM port, maybe check if Thonny or PuTTY can see it.
Then I would unplug the Pico, delete all 2E8A:xxxx entries in Device Manager, keep running the above reporting script until there are no 2E8A:xxxx in the list. At least delete the failure item; it will likely have a yellow triangle next to it in Device Manager.
Then reboot, plug the Pico back in and see what the reporting script shows on 2E8A:xxxx. Then check that Thonny or PuTTY can see it.
After that, with a fair wind, PlatformIO might just work with that COM port. The COM port number will likely change once it does.
Statistics: Posted by hippy — Sat Feb 10, 2024 12:39 pm