• As I understand it Windows assigns each new device a new COM number.

    It wouldn't surprise me if between 1v91 and 2v04 the USB descriptors the Espruino WiFi reports changed, which may well have convinced Windows it was a different device. I believe this was required to allow you to have USB HID and VCP running in Windows at the same time without needing any driver hacks.

  • Thank you @Gordon for your immediate response.

    Just to add, I had updated a Pico from ~2v01 to ~2v03 back in May, before this mess and as always, the Com port assignment remained the same as it had always done.

    Next re-flash, I'll update this post. No other devices on hand and just not enuf time right now! ;-)


    'the USB descriptors the Espruino WiFi reports'
    'to have USB HID and VCP running'

    Would you educate us please on who/what organization controls the WiFi stuff then. My belief was that it was a small team in addition to your effort assisting in the releases? Or is the assumption the descriptor is changing from the Espruino release and because of the constant changing Windows development, just does the re-assignment? e.g. Which end, or both?

About

Avatar for Robin @Robin started