-
Notifications
You must be signed in to change notification settings - Fork 111
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
Windows (non mingw): "the system cannot find the path specified: picotool/build/rp2350_otp_contents.json
"
#145
Comments
I guess the easiest workaround is to just download the pre-compiled binary from https://github.com/raspberrypi/pico-sdk-tools @will-v-pi As there have now been several similar requests for Windows binaries, perhaps it's worth adding that link somewhere near the top of https://github.com/raspberrypi/picotool/blob/master/README.md ? |
I've made a PR to add a note about the pre-compiled binaries to the readme. But it should be possible to compile on Windows - I've just checked and had success running:
So this may be an issue with the vcpkg libusb - could you try downloading libusb instead as mentioned in the instructions in the readme? Also make sure you either have |
Hey guys, haven't gotten to the manual Is my understanding correct that Otherwise I could just connect a digital pin to the RUN pin right? |
You need to add the |
For context (and I'm not sure this is right) but I was hoping to avoid having to constantly unplug and plug my pico when trying to run/flash rust programs on my pico w. I don't know much about windows C compilation or any of this.
But it seems like, from reading the doc of
picotool reboot
that this would make it easier to reboot the pico into a flashable state.I am trying to build picotool. I am using the
vcpkg
LIBUSB and I should note I'm also compiling withSince I was getting a bunch of errors trying to just do the following (as the readme states):
I got quite far into the build (I think) but I ran into the following failure which I am having trouble debugging
This seems related to the newly released rp2350, which I'm not using. Does anyone have any advice on how to resolve this issue?
Thanks!
The text was updated successfully, but these errors were encountered: