You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For whatever reason, I have found it difficult to successfully open serial comms to the pico since the SDK update to 1.1. I end up having to unplug and replug the board up to about ten times before successfully establishing serial comms. Once established, they are rock solid for hours though, so that's good. The most common error reported by pyserial is FileNotFoundError.
I have gone back to 9f00974 and do not observe this problem.
The text was updated successfully, but these errors were encountered:
I think this might be raspberrypi/pico-sdk#257. At least commit has been made to the v1.1.1 patch branch that references that issue and I think that it solved this issue for me. At least I now see the pico show up under COM4. There is also an unknown device in device managed called "Reset" that has an invalid driver. Not sure if that's a bug or you have to install a driver to access the new USB reset behaviour (which I think is the route cause of all of this...maybe!)
I'll push some new firmware to master and for #10 shortly, compiled against the latest commit in the SDK patch branch anyway. Let me know if that resolves the issue for you!
For whatever reason, I have found it difficult to successfully open serial comms to the pico since the SDK update to 1.1. I end up having to unplug and replug the board up to about ten times before successfully establishing serial comms. Once established, they are rock solid for hours though, so that's good. The most common error reported by pyserial is
FileNotFoundError
.I have gone back to 9f00974 and do not observe this problem.
The text was updated successfully, but these errors were encountered: