Windows 11 + Pico2W = upload issues

[pike2k]

I've used pico1's fine with Win 10 (+Zadig) earlier but since I was forced to upgrade to Win 11 I am having serious issues.
For starters I have 2 devices, RP2350 Boot (Interface 0) + RP2350 Boot (Interface 1), which one is the one that I need to put the correct driver to? Does the other device interfere?

The Pico2W comes up in BOOTSEL mode on a Win10 computer without me having to press the BOOTSEL button. This does not happen on Win11. I figure it comes up in BOOTSEL mode because it doesn't (yet) have a valid image to boot from.

On the Win11 PC I've compiled code for 'Pico' in VS Code + Platform IO. I have 2x RP2350 Com Ports listed in devices. Uploading doesn't work. I am not sure if I need to make some special config for RP2350?

[pike2k]

I can now upload from Platform IO on Win11 to Pico2W. Here's how I did it.

I changed board from 'pico' to 'rpipico2' in platformio.ini and did a clean compile. I copied this firmware.uf2 to the Win10 pc and there I could copy the file onto the RP2350. I now moved the Pico2W to the Win11 PC and changed driver to 'WinUSB' for the (Interface1) device.

Now the upload part works. What apparently still doesn't work is BOOTSEL mode in Win11.

[pike2k]

It looks like we have identified the problem - I am missing the USBSTOR driver. I will focus my attention to resolving this issue.

[maxgerhardt]

The USBSTOR driver is an absolute Windows builtin. That cannot possibly be missing. Something else must guide it to wrongly install the usbser (usb serial) driver instead of the USB storage driver. The USBTreeView will be an indication of what the RP2350 actually says it is (bInterfaceClass).

[pike2k]

It seems like Zadig set a restorepoint before it did it's first change. I managed to rollback Zadig's changes. I now got a Virtual volume again when I use the BOOTSEL button. I will see tomorrow if I must reinstall WinUSB for the 'other device' in order for Picotool to work. Thanks for helping me understand the root issue.

[maxgerhardt]

Right, WinUSB drivers should only be loaded for Interface 1 of the RP2350 Boot device, then picotool upload should work. Leaving Interface 0 untouched.

[pike2k]

Funnily enough after I used the restorepoint, I was back on this config for the device presented when a valid image has been uploaded. The odd part is that it seems to work without issues with Platform IO and Picotool!

[pike2k]

I'm gonna take the chance and talk about the 'valid image' that is needed. I looked at the online docs under 'Using this core with PlatformIO' and it is not very clear what needs to be done with regards to the 'board' setting when you're are using a Pico2W. There's no list of available boards that I can find. Because of this, my first (wrong) instinct was that 'board = pico' was universal, and worked for every board. This caused me to start to play with Zadig :( I managed to get the onboard led working only when I guessed correctly that 'board = rpipico2w' was the correct board.

[earlephilhower]

From my lsusb output on a RP2350 in ROM UF2 upload mode. Interface 0 is a USB Mass Storage device, interface 1 is the PICOTOOL interface.

Bus 003 Device 058: ID 2e8a:000f Raspberry Pi RP2350 Boot
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x2e8a 
  idProduct          0x000f 
  bcdDevice            1.00
  iManufacturer           1 Raspberry Pi
  iProduct                2 RP2350 Boot
  iSerial                 3 8ECA1EE3401CF55E
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0037
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               50mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0021
  bNumDeviceCaps          1
  Platform Device Capability:
    bLength                28
    bDescriptorType        16
    bDevCapabilityType      5
    bReserved               0
    PlatformCapabilityUUID    {d8dd60df-4589-4cc7-9cd2-659d9e648a9f}
    CapabilityData[0]    0x00
    CapabilityData[1]    0x00
    CapabilityData[2]    0x03
    CapabilityData[3]    0x06
    CapabilityData[4]    0xa6
    CapabilityData[5]    0x00
    CapabilityData[6]    0x01
    CapabilityData[7]    0x00
Device Status:     0x0000
  (Bus Powered)

That said, none of those should be assigned to anything with Zadig. Only the serial ports (CDC ACM) after an app is running, no? There's nothing to mess with for the USBSTOR, that "just works" unless you hack it like show in the above image. Then your USB mass storage device will not show up, since WinUSB is eating it.

I suggest undoing any changed you've done w/Zadig and uploading blink using BOOTSEL and then trying the Zadig change again, and only on a USB CDC/ACM/Serial port.