- This topic has 3 replies, 3 voices, and was last updated 2 weeks, 1 day ago by
.
-
Posts
-
Does anyone know the format of the install packages for the PI PICO SDK for visualgdb? Currently the latest supported version is 2.0.0 which is the better part of a year out of date. There are bugs in this version as delivered by the rpi foundation that have since been fixed. There appears to be no prebuilt SDK tools for anything other than 2.0.0.
Several of the bugs (like using all available ram) are project blocking, so I have to move to the next version.
Just selecting a GIT tag for the pico sdk version gets the right version, but it won’t build. Any help in figuring all this out would be appreciated. I’m about to throw up my hands and switch to vs code.
I also want upgrade to SDK 2.1.1
the build fails with a version-conflict with “picotool”.
I’ve build new picotool (with VS2019 prof.) but no success.
in directory c:\Users\xxxx\AppData\Local\VisualGDB\PicoTools\picotool\
is a file picotoolConfigVersion.cmake with the package-versionnumber (2.0.0.)Maybe you have to tweak it.
@VGDB-Supporter:
Is there an easy way to ge SDK 2.1.1 running?
Kind regards Thomas
Hi,
We have added support for the SDK 2.1.0 a while ago. The 2.1.1 version got added just now.
In general, if you would like to use a version that we have not fully tested yet, you can get one from Git, but you would need to manually figure out the dependencies that are not included in the repository. E.g. you can try getting the new picotool from the VS Code extension, or check if Raspberry Pi maintainers have published a pre-built version.
Long-term, it looks like the packages used by the RP2040 VS Code extension are usable now, so we will eventually switch VisualGDB to download them just like it downloads the Arduino packages, so you won’t need wait for us to repackage anything.
- You must be logged in to reply to this topic.