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

Поделиться
HTML-код
  • Опубликовано: 19 авг 2024

Комментарии • 35

  • @josephhillier5875
    @josephhillier5875 10 месяцев назад +2

    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
      @deltocode  10 месяцев назад

      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 :)

  • @chrisfaux3769
    @chrisfaux3769 3 месяца назад

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

    • @deltocode
      @deltocode  3 месяца назад +1

      Glad it helped!

  • @TheGothGaming
    @TheGothGaming Год назад +2

    You saved my life. Thank you!

    • @deltocode
      @deltocode  Год назад +1

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

  • @nguyenhuuanhtuan5360
    @nguyenhuuanhtuan5360 5 месяцев назад

    Very detailed explanation, thanks a lot.❤

  • @serhiimamedov
    @serhiimamedov 11 месяцев назад +1

    This is amazing tutorial. Thanks a lot!

    • @deltocode
      @deltocode  11 месяцев назад +1

      Thanks for the kind words :)

  • @benarcher372
    @benarcher372 5 месяцев назад

    Worked perfect!

  • @serhiimamedov
    @serhiimamedov 11 месяцев назад +2

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

    • @deltocode
      @deltocode  11 месяцев назад +1

      Yeah, I can give it a look.

  • @drivers99
    @drivers99 7 месяцев назад

    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
      @deltocode  7 месяцев назад

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

  • @kai-elec
    @kai-elec 7 месяцев назад

    Thank you so much.

    • @deltocode
      @deltocode  7 месяцев назад

      Glad it was helpful!

  • @spikiestvirus7433
    @spikiestvirus7433 3 месяца назад

    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?

  • @stephdumanoir1703
    @stephdumanoir1703 8 месяцев назад +2

    Does this work for Macs with the M1 chip?

    • @deltocode
      @deltocode  8 месяцев назад +1

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

  • @aviationodyssey1892
    @aviationodyssey1892 6 месяцев назад

    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
      @aviationodyssey1892 6 месяцев назад

      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
      @deltocode  6 месяцев назад

      @@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 :)

  • @own1118
    @own1118 10 месяцев назад +2

    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
      @deltocode  10 месяцев назад

      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
      @Silasstokes 10 месяцев назад +4

      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
      @deltocode  10 месяцев назад +1

      @@Silasstokes thanks for sharing how you solved it!

  • @user-lq7td7xq1l
    @user-lq7td7xq1l 10 месяцев назад

    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
      @deltocode  10 месяцев назад

      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.

  • @danielpicado5292
    @danielpicado5292 10 месяцев назад

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

    • @deltocode
      @deltocode  10 месяцев назад

      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!

  • @gurk_studios
    @gurk_studios 11 месяцев назад

    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
      @deltocode  11 месяцев назад

      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.

    • @gurk_studios
      @gurk_studios 10 месяцев назад +1

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

    • @deltocode
      @deltocode  10 месяцев назад

      @@gurk_studios glad you got it to work!

  • @dinofiori
    @dinofiori 13 дней назад

    got trouble after vim the script :/