-
Notifications
You must be signed in to change notification settings - Fork 48
picotool incompatible with SDK #51
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
Comments
Update: |
@will-v-pi This script checks out the |
This is a known bug in the 2.1.0 and 2.1.1 SDK releases (raspberrypi/pico-sdk#2401) - as the error message states, the fix is to install picotool 2.1.1 separately, which is fixed by #43 |
Closing as duplicate of #43 |
This is useful. |
@lurch apologies if I appear a little naive :-/ My problem is that when building the sdk examples, it downloads and builds its own local copy (version 2.1.2-develop) UPDATE : aah you posted a link above, let me take a look |
@lurch option 1export picotool_DIR=/usr/local/bin option 2export picotool_INSTALL_DIR=/usr/local/bin option 3 (directly to cmake)cmake -Dpicotool_DIR=/usr/local/bin -DPICO_PLATFORM=rp2350 ${PICO_EXAMPLES_PATH} None of these options seem to stop the downloading of a newer version of picotool, very confused as to what I am doing wrong here, but in all cases I get
to test it is correct
I should also add, I have a built version of picotool(2.1.1) here All I need to know, is how to direct the build system to use this version of picotool, but it seems to ignore the variables from above ? |
Just to confirm, when you built & installed picotool, did you definitely follow the instructions (ie use You should have these additional files installed, which are the files the SDK actually searches for
Do not use any of your three options - the
|
@will-v-pi forgive me - I am not quite correct in what I am saying, picotool was actually downloaded and built by the pico-setup.sh script itself, but it looks like it does not do a "make install" it just copies the binary file itself, so the files you describe above would not exist.
in which case should my actual flow be as follows ?
|
Yep, that's the bug in |
OK, I went back the folder that pico-setup.sh downloaded and built picotool and issued |
Yes |
See #52 🙂 |
Hi All
Installing via this script works perfectly
But when trying to build the entire set of examples there is a failure at this point when building hello_serial_enc for a target of rp2350
the commands I submitted were
the error
Interestingly, there was a warning earlier in the process, which indicates that there is no available picotool 2.1.1
how can I fix this ?
The text was updated successfully, but these errors were encountered: