-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems after re-connecting usb #197
Comments
any updates on this matter - seems to be possibly related to #199 ? |
Thanks for reporting.
Maybe. To find out please reproduce the bug and then run following commands in your terminal: ls /dev/cu.*
lsof /dev/cu.<insert the port name of your board here> If this command returns any output your issue should be caused by the same problem as #199. |
If that's the case, this could potential solve the issue: On macOS arm64 replace the |
Hi, @paulober sorry for the delayed reply but I had to postpone working on the project a bit, and now getting back... Also - now (I mean before I've attempted replacing the folder) occasionally it stuck during project upload, once it even bricked the Pico and I had to put the fresh uf2 again... |
I have replaced the contents of a wrapper with the files you have provided some time ago and it seemed to help for a while - though it still wasn't perfect in terms of connection/disconnecting bug. But after getting back to the project I have to report that the problem persists, not sure if that's because an automatic update of a extension (v3.7.6) overwrote the wrapper lib to a worse version again ? Anyway the connection to the board is super finicky - a rather random sequence of disconnecting the usb, relaunching VSCode, connecting again etc. end even sometimes just launching Thonny in between gets problem sorted for a while. Let me know how can I help to investigate the issue further to get things working in a stable manner. |
oh and btw - I ran the command you have mentioned before (
Curious that there is this Ultimaker thing - that's probably because I had Cura launched, nevertheless quitting it didn't really help and got just "wrapper" entry when I've re-ran the cmd. |
Ok and now after problems with connecting to Pico and quitting VSCode the
So it seems the process is not properly killed / not releasing usb port properly ? BTW - Killing the process via terminal cmd What helped immediately though was changing the USB port in my usb hub - we'll see how long it's gonna last and if it "fixes" the probem every time - I'll let you know. Hope there are some leads that would help to solve the issue ! |
Hello - any chance for making a serial connection with pico more stable ? |
What are the steps to reproduce this issue?
What happens?
Despite the "Pico Connected" info in status bar trying to run any command does nothing, no error, just nothing happens
What were you expecting to happen?
All commands should work as expected after re-connecting usb and while "Pico Connected" status is displayed.
Any logs, error output, etc?
No explicit errors shown in OUTPUT, there is following info generated after opening VS Code, successfully connecting to pico, running code, then disconnecting usb and re-connecting:
Any other comments?
I'm on Mac Book Pro M3 Max; Sonoma 14.1.1
It seems there is some issue with ports being locked / not properly released since after doing:
ps -ef | grep /dev/cu.usbmodem21201
I get (even after closing VS Code):
Then after killing the process via
kill
command pointing to PID of the process above I'm usually able to run / upload / etc again.Another cue to something wrong with ports (being blocked ?) is that when I launch Thonny after MicroPico stops working I get the message there such as:
Even if VS Code is closed before launching Thonny
Which version of MicroPico are you using?
MicroPython v1.22.1 on 2024-01-05; Raspberry Pi Pico W with RP2040
Support info
Copy this from the
Help -> Info/About -> Copy
(Code -> About Visual Studio Code -> Copy
on macOS) option in Visual Studio Code:The text was updated successfully, but these errors were encountered: