Add RP2040 Pico support. Similar project configuration to AVR. Pico is gaining in popularity for embedded applications and currently there is no installation for a project, or any on line help for the configuration.
I do use CB to develop for Pico in Linux and its really nice.
I can't say anything about wizards and how CD could support it, but I can tell how I work with the pico.
I think the major difference to AVR's is that the Pico SKD is designed for cmake and cmake alone. I tried some time to extract the core for stand-alone use (works with STM) but failed. The working solution now is to setup CB with "GCC for ARM" and use cmake by calling in in the build options
The scripts are static. The compile script only has a "pico"/"pcio2" board dependency. The clean is too trivial to show.
mkir -p build
cd build
cmake -DPIC_BOARD=pico # for pico2040
make -j 12 # number of cores
cd ..
Uploading I do with a script file calling the 'openocd' tool as I use the pico debug probe. This also allows debugging, again by the 'openocd' tool starting a gdb server that standard CB can use.
The key item, I think, is the CMakeLists.txt file used with the Pico SDK. All build related settings are made in that file. I include it as non-compile file into the project so its easy to edit. There is no adaptation for CB required.
I need to edit that file manually to
add source/header file names
add libraries files
add PICO SDK libraries to use
The former two is info available in the CB project and could possible be automated.
Hope it helps
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do use CB to develop for Pico in Linux and its really nice.
I can't say anything about wizards and how CD could support it, but I can tell how I work with the pico.
I think the major difference to AVR's is that the Pico SKD is designed for cmake and cmake alone. I tried some time to extract the core for stand-alone use (works with STM) but failed. The working solution now is to setup CB with "GCC for ARM" and use cmake by calling in in the build options
The scripts are static. The compile script only has a "pico"/"pcio2" board dependency. The clean is too trivial to show.
Uploading I do with a script file calling the 'openocd' tool as I use the pico debug probe. This also allows debugging, again by the 'openocd' tool starting a gdb server that standard CB can use.
The key item, I think, is the CMakeLists.txt file used with the Pico SDK. All build related settings are made in that file. I include it as non-compile file into the project so its easy to edit. There is no adaptation for CB required.
I need to edit that file manually to
The former two is info available in the CB project and could possible be automated.
Hope it helps