To be sure, the dmesg of Ubuntu 24.04 LTS running in the MacBook Air virtual machine(UTM 4.5.2) was collected.
2. start VSYS supply to Pico W
3. disconnect Type-C cable ([ 95.199566] at time)
4. attach Type-C cable (no response on dmesg)
The output of the dmesg matches the VBUS supply and USB device recognition on the Pico W side. Of course, since this is a virtual environment, it is governed by the behaviour of the physical hardware.
1. USB connection with no VSYS on Pico W ([ 80.413879] at time)[ 80.413879] usb 3-3: new full-speed USB device number 3 using xhci_hcd
[ 80.555221] usb 3-3: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00
[ 80.555236] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 80.555239] usb 3-3: Product: Pico
[ 80.555241] usb 3-3: Manufacturer: Raspberry Pi
[ 80.555242] usb 3-3: SerialNumber: E661640843564229
[ 80.562086] cdc_acm 3-3:1.0: ttyACM0: USB ACM device
[ 95.199566] usb 3-3: USB disconnect, device number 3
2. start VSYS supply to Pico W
3. disconnect Type-C cable ([ 95.199566] at time)
4. attach Type-C cable (no response on dmesg)
The output of the dmesg matches the VBUS supply and USB device recognition on the Pico W side. Of course, since this is a virtual environment, it is governed by the behaviour of the physical hardware.
Statistics: Posted by 0yama — Wed May 08, 2024 3:53 am