Upload port required #2
Comments
|
have you found a solution? |
|
I'm running on Ubuntu and if I insert the board in upload mode, it presents itself as a USB drive so I added: which is the standard path to mounted drives in Ubuntu |
|
ah ok i just tried it in a linux vm and yeah that worked
|
|
Hi @MNS26 ! Does a COM port show up in Device Manager when you connect your board board? |
|
yes it does show up |
|
@MNS26 Could you please check VID:PID of the COM10 port? |
|
the VID is 2e8a and the PID is 00c0 |
|
@MNS26 That's strange, the VID:PID combination in the board manifest is the same. Could you please run the |
|
@valeros here is the output |
|
i dont see any obvious errors 🤔 |
|
Forgot to mention, please delete the custom upload port as well. |
|
@valeros removed the manual port |
|
@MNS26 According to your screenshot above, the COM10 port is the right one, but it fails for some reason. Could you please also try to upload a simple blink example using Arduino IDE? How the upload workflow implemented there? Would be great if you could copy paste here the logs from Arduino IDE. Please keep in mind that you might need to enable the verbose log in the Settings: |
|
@valeros i used the stand-alone version of arduino (dont plan on installing it) |
|
Does it work if you manually specify COM10 as the upload port, e.g.: |
|
@valeros just ran it with and now it worked |
|
also knowing that the pico has 2 cores is there a way to use the 2nd one? and if so how? and when i tried to upload something again via vscode it froze |
|
@valeros maybe a little off topic for this issue but when i was using the unofficial (WizIO) platform but now with the exact same code it just turns of for a split second roughly every second EDIT: mistyped the max value in the map() function |
|
nvm i just rewrote the exact same code and now it works -_- . . . why just why |
|
I got it to work on windows using the upload port setting Method 1 - Holding Bootsel while plugging in and using drive as upload port Method 2 - Using COM port without using Bootsel button Both work with no problem. Great work! |
|
@danielkucera i think you can close this issue by now seeing that its basically solved |
|
But it does NOT work for me without upload_port (on Ubuntu). |
|
nvm then |
|
I wasn't able to use @savejeff 's method (it would just timeout with Maybe for people who already used the Arduino IDE with the Pico have this driver pre-installed? On Windows 10 btw. Edit: I also experienced the same behavior for my Sparkfun RP2040 ThingPlus, using Zadig allowed the first upload to go through, and from there on I could delete |
FYI : I have installed the Pico Core in Arduino IDE before I installed it on PlatformIO. That might be the reason I have no problems with Driver etc. |
|
I had problems uploading on Ubuntu. It turned out that picotool was having protection problems writing to the usb disk. I solved that by adding the line: SUBSYSTEMS=="usb", ATTRS{idVendor}=="2e8a", MODE:="0666" to /etc/udev/rules.d/99-platformio-udev.rules So my platformio.ini for Ubuntu is: [env:pico] Hope this is useful. |
|
Debian system here. Also having the mysterious failures. Using @mpmarks addition to my udev rules helped, even though I'd installed the latest udev rules from https://docs.platformio.org/en/latest/faq.html#platformio-udev-rules and even though I could upload successfully by manually copying to /media/USERNAME/RPI-RP2. Ie, it wasn't obvious this was a permissions error, but it was. Now I have no upload-specific information in my An arduino sketch is already running on my pico, so the autoreset works. But it's still not perfect: the first time I run But I can tell that the forced reset works and my sketch has stopped running. Re-running So this seems like the remaining issue is just a race condition: it's resetting correctly but not waiting quite long enough to let the upload succeed. The second time I run the upload commands it is already reset into BOOTSEL mode and (now that the Is there any way to tweak the wait time between reset and upload? |
After adding the above mentioned udev rule (and a reboot), my build uploads are now working without issue after seeing the timeout My platform.io, for reference. I was able to just use the serial port for upload, and this removes need for mounting too. And an upload run: Running on Arch Linux/5.13.13 as an unprivileged user in |
|
Pico-noob here, pio 5.2.3b4, macos 12.0.1. FWIW, the only way I got things to work smoothly was as follows:
The
It's not a great out-of-the-box first-time experience, but at least it works. Here's the |
|
I'm no
Hopefully, anyone encountering the |
|
I tried the above Go fix, but it did not work for me. This was my first time using Go. Hope this helps someone with Pico upload in the future. |
|
On my environment, I need to run the copy command for uploading firmware after showing If Should the picotool upload uf2 file to the media? My environment |
No it does so via libusb. I have a patch to get |
|
Thank you for the information but I cannot upload with the following settings. |
|
Oops, can you do a |
|
Thank you for updating but it still failed for both case for /devtty/ACM0 available and /media/${USER}/RPI-RP2 available. |
|
Hmm auto-detection of that can still be.. imrpoved then. Setting |
|
Thank you for the advise but |
|
Try updating the platform per above again and retry, sorry. |
|
The log become succeeded but it does not upload firmware. |
|
Sorry, please try updating again and retry. If it still not works, issue to https://github.com/maxgerhardt/platform-raspberrypi/issues |
Since I'm having the same issue, I added a reply in the existing issue: EDIT: |
|
If someone is still having this issue on win 11 this is what finally worked for me: toonrobotics blog post TLDR: you need to update the driver with zadig, as mentioned by @maxgerhardt above, but you have to install winusb (so not libusb_win32) for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I don't specify upload port, I get an error message:
If it's really the case, it would be good to mention this in the example or docs.
The text was updated successfully, but these errors were encountered: