Raspberry Pi Pico - C/C++ SDK Setup [macOS]

[@josephhillier5875]

Amazing tutorial mate, I look forward to seeing more of your tutorials. I'd love to see one on how you set up your terminal with the colours and suggestions!

[@deltocode]

Thanks a lot! Well, the shell is almost 100% vanilla fish shell (fishshell.com). I believe I only updated the prompt coloring (gist.github.com/eldelto/709af84dc77049f11e6192badcaa0e9c), completions come out of the box :)

[@edwardc1797]

This video was a big help. Thank you.

[@emanuelefavero]

Thanks a lot man! I was going insane with other tutorials and documentation

[@deltocode]

Glad it helped!

[@TheGothGaming]

You saved my life. Thank you!

[@deltocode]

That's amazing to hear! Glad it helped :)

[@serhiimamedov]

Could you also make a tutorial on how to setup debugging env?

[@deltocode]

Yeah, I can give it a look.

[@drivers99]

I’ll have to give this a shot. I wonder why the pdf of Getting Started with Raspberry Pi Pico has different dependencies (in section 9.1) but they don’t work for me (I was getting errors in vscode, and the compiler they said to choose wasn't listed) so I’ll try your way. I also ran into an error at one point following your tutorial because brew install gcc-arm-embedded had not actually succeeded (and I ignored it at first), because there was another binary already at /opt/homebrew/bin/arm-none-eabi-as (and all the other arm-... executables there). I saw it was symlinked to ../Cellar/arm-none-eabi-binutils/... so I did: brew uninstall arm-none-eabi-binutils and then I could do: brew install gcc-arm-embedded After that, make worked! Edit: Everything worked! We have blink.

[@deltocode]

Thanks for sharing the problems you ran into! I'm glad you got it to work :)

[@nguyenhuuanhtuan5360]

Very detailed explanation, thanks a lot.❤

[@serhiimamedov]

This is amazing tutorial. Thanks a lot!

[@deltocode]

Thanks for the kind words :)

[@AbrunheiroTrindade]

I'm starting to use the command line C compiler to develop software with R Pico. I use a Mac Silicon M1 and I followed all the steps in this video very carefully, after all it is very well prepared. I think I need to study more, however, I would like you to help me solve an error generated in the last step of the blink.c example (make command) (I use the basic Pico): .../build/_dps/picotool-src/errors/errors.cpp:1:10: Fatal Error 'cstdarg' file not found.

[@deltocode]

Hi, puh that's hard to say from a distance. Maybe you can give removing and reinstalling the cross-compilation toolchain a try. Some people reported that they had some different versions laying around from other projects that interfered. Also, removing the whole "build" directory again might resolve some transient errors. Hope that helps and good luck!

[@AbrunheiroTrindade]

@@deltocode, many thanks. I have re-installed everything carefully and resulted in the same error (~pico/blink/build/_deps/picotool-src/errors/errors.cpp:1:10: fatal error: 'cstdarg' file not found) and I was tragic, I commented the #include line and works fine. I do not know why this file was not found, since the file is on paths. Thanks for your attention. 1 | #include

[@deltocode]

@@AbrunheiroTrindade very weird... Happy to hear that you got it working though!

[@own1118]

hi thank you for this video, however at 9:51 when you use make i have an error :arm-none-eabi-gcc: fatal error: cannot read spec file 'nosys.specs': No such file or directory Do you know why? need help ^^

[@deltocode]

Hello, you can try running "arm-none-eabi-gcc --version" to see if the cross-compiler has been installed. If that works give deleting the whole build directory a try. I also encountered this issue once and that fixed it for me. Let me know if that solves the issue :)

[@Silasstokes]

I had this issue and it was because I had installed gcc from a brew tap while following instructions from another tutorial. In my case I just removed that package e.g `brew uninstall arm-none-eabi-gcc`, then I had to untap the cask `brew untap armmbed/formulae` and finally reinstall with the command from this tut: `brew install gcc-arm-embedded`, then I was able to run make without any issue.

[@deltocode]

@@Silasstokes thanks for sharing how you solved it!

[@spikiestvirus7433]

Thanks for the video! I just have one question I’m trying to view the debugger in my blink.c file but it is not showing any of my prinf(), got any ideas?

[@benarcher372]

Worked perfect!

[@whoisandrewnast]

Hello, I got to 3:26 where you entered git submodule update --init, but got this message: fatal: not a git repository (or any of the parent directories): .git. What should I do? Great video though, you're a lifesaver for making this! 🔥

[@deltocode]

Hi, that somewhat sounds like you are not in the pico-sdk directory or something went wrong when cloning the pico-sdk project from Github. Maybe try to toss the whole pico-sdk folder into the bin clone it again from Github. Afterwards you should be able to download all git submodules. Cheers

[@stephdumanoir1703]

Does this work for Macs with the M1 chip?

[@deltocode]

Hi, yes this works both with Intel and Apple Silicone chips. Have fun programming!

[@JanvierKahwaraKaliza]

Hello! thanks for this amazing tutorial, however i got stuck on the cmake part, i'm getting this masage " CMake Error at pico_sdk_import.cmake:68 (message): Directory '/Users/janvierkaliza' does not appear to contain the Raspberry Pi Pico SDK Call Stack (most recent call first): CMakeLists.txt:3 (include)" is there a way to fix this, thanks

[@deltocode]

Thanks for the nice words :) It looks like your PICO_SDK_PATH environment variable doesn't point the the actual pico-sdk folder. It should look something like this (depending where the sdk is located on your system of course): export PICO_SDK_PATH=/Users/eldelto/pico/pico-sdk/ I hope this can resolve your issue.

[@aviationodyssey1892]

Hi thank you for your tutorial! I am a newbie. I get an error while "make". arm-none-eabi-gcc: fatal error: cannot read spec file 'nosys.specs': No such file or directory. Can you help me?

[@aviationodyssey1892]

make[2]: *** [pico-sdk/src/rp2_common/boot_stage2/bs2_default.elf] Error 1 make[1]: *** [pico-sdk/src/rp2_common/boot_stage2/CMakeFiles/bs2_default.dir/all] Error 2 make: *** [all] Error 2

[@deltocode]

@@aviationodyssey1892 Hello! There is another user that ran into a similar problem. Silasstokes then pointed out how to resolve the issue. I'll just quote them here: I had this issue and it was because I had installed gcc from a brew tap while following instructions from another tutorial. In my case I just removed that package e.g `brew uninstall arm-none-eabi-gcc`, then I had to untap the cask `brew untap armmbed/formulae` and finally reinstall with the command from this tut: `brew install gcc-arm-embedded`, then I was able to run make without any issue. If that solves it for you, give their comment a like :)

[@danielpicado5292]

Hey boss what is those two "||" looking things u typoed in when making the pico folder. What do I type for that?

[@deltocode]

Hello! Not 100% sure what you mean. Creating the directory is done by executing "mkdir pico". Otherwise this guide also exists as a written version, maybe that clears it up: www.eldelto.net/articles/raspberry-pi-pico-setup-for-macos Cheers!

[@kai-elec]

Thank you so much.

[@deltocode]

Glad it was helpful!

[@henryerstudios]

I had an error when i wrote the make command. I didn't get the same messages that you got. Can you help me? % make [ 1%] Building ASM object pico-sdk/src/rp2_common/boot_stage2/CMakeFiles/bs2_default.dir/compile_time_choice.S.obj [ 2%] Linking ASM executable bs2_default.elf arm-none-eabi-gcc: fatal error: cannot read spec file 'nosys.specs': No such file or directory compilation terminated. make[2]: *** [pico-sdk/src/rp2_common/boot_stage2/bs2_default.elf] Error 1 make[1]: *** [pico-sdk/src/rp2_common/boot_stage2/CMakeFiles/bs2_default.dir/all] Error 2 make: *** [all] Error 2

[@deltocode]

Can you run 'arm-none-eabi-gcc --version' in a terminal and verify that the arm-gcc cross-compiler is installed? Sometimes it also helps to remove the whole 'build' directory and regenerate it if it is just a transitive error. Feel free to reach out if the error persists.

[@henryerstudios]

@@deltocode I ended up reinstalling everything but it ended up working fine so thank you cool video

[@deltocode]

@@henryerstudios glad you got it to work!

[@atheros9271]

got trouble after vim the script :/

[@VEC7ORlt]

Nice tutorial, but programming like that just pisses me off - the amount of side knowledge this requires is so discouraging - dependencies, upon dependencies, include this, that and the other, make, clean, clone and if you forget or don't know something - god help you figuring it all out...

[@deltocode]

@@VEC7ORlt Yes I feel you. It's definitely not as direct as programming an 8-bit AVR with nothing but the data sheet in hand. Any recommendations for systems you like better?

[@VEC7ORlt]

@@deltocode wrote a big thought out comment and the fucking comment nanny ate it. tldr AVR is one of the best, we need simpler toolchains and syntactic sugar.