Getting Started with the Pico W C/C++ SDK

[@Lucas-pc2rt]

For this tut being a year old, it still works well! The only thing I did differently is that I had to call cyw43_arch_init() or turning on/off the led would throw an error. The blink example for the pico w was moved to the wifi folder inside of the pico_w folder in pico-examples, as well as the lwipopts.h if I am remembering correctly. Very clear and coherent video. Thanks!

[@WeirdDuck781]

needs more likes OR PIN as it makes this video still relevant and up to date. Thank you by the way ;)

[@stylesoftware]

Keep it up buddy. To the point, that's what we want.

[@ui4lh]

Man, Ive been fighting with this stuff for sooooo long and this videa was a God send.... Thanks Electromaker for making it and so detailed!!! Subscribed...

[@maciekrostocki7202]

few things for people that will watch it now: blink example is in pico_w/wifi/blink, for me the blinking doesn't work if there isnt if(cyw43_arch_init()){....}, i also think that it's is better to declare PICO_SDK_PATH in bashrc so you don't have to do that every time and you should declare it relative to home directory, not directory you are currently in. Error lines for includes will disappear if you configure cmake for your directory, also it is worth adding set(PICO_BOARD pico_w) in CMakeLists

[@rd-tk6js]

fantastic, thanks !

[@ww3ok]

Good introduction to the Pico-W sdk and how it differs from the vanilla sdk. Thanks.

[@Alamartec]

Many thanks mate, you made it easy to follow.

[@gordonmgx]

Thanks. Very interesting tutorial

[@jacksparrow2000]

Thanks a lot! These simple steps worked for both the pico W and the Tiny 2040!

[@sotw1610]

Thanks for the video! It is a good introduction to get started with the picow board.

[@usefulelectronics]

Amazing, I am looking for a good source to start programming my pico with the native SDK

[@robertbox5399]

So you need help from the Dons at Bletchley Park to flash an LED using C on the Pico. Unbelievably complicated.

[@Electromakerio]

Since making this video, they've simplified it hugely, at least for Windows users. There is a one-click installer now. Personally, I still use more or less this method (docker rather than full VM) as I like the separation and dedicated working environment.

[@ApusApus]

Thanks, might be able to actually start using the native SDK instead of Arduino. Did you ever get rid of the error squiggles on the includes or are you just ignoring them?

[@JHess]

hey friend, not sure why but this video is only available in 360p.

[@Electromakerio]

Thanks for the heads up! This actually happens every time a video gets uploaded to KZbin, the standard definition version goes live as soon as the upload finishes, and the HD version takes a while longer. It's 1080p now. I usually upload them and release them a while into the future to avoid this but wanted to get it out early today!

[@ddienst]

It compiled the examples but when I try to compile the flash print it crashes on some assembly file. Can you share your VMware machine?

[@burtonrodman]

type the code yourself -- agree 1000%

[@EdwinFairchild]

How do you debug and step through your code ?

[@Electromakerio]

That's something I hope to revisit at some point soon! This was meant to be a very bare bones "zero to developing" video and including debugging just made it way too long. But yes, Debug and step through will be a future topic, let me know if there's any other specific stuff like this and I'll add it to the list!

[@wm6h]

VMWare 17 not free. 15 day trial only

[@captainpumpkinhead1512]

You don't need to use a VM to program the Pico. You can do it on Windows just fine. And you're making this harder for beginners by navigating around in terminal instead of a folder explorer.

[@Electromakerio]

You are totally right. Windows is not a problem to set up for some folks, yet the official Pi guides are aimed at those using a Pi. Given the fact that Raspberry Pi boards weren't the easiest things to come by for a while, I thought the VM was a good solution. I'm just a hobbyist, though, and I get stuff wrong all the time. Windows used to be more hassle than this to get set up, maybe it's different now. As to the command line stuff, I didn't do it to be complicated, I don't know any other way to work with git and the Pico SDK build tools that is any simpler. Other than moving the uf2 file onto the Pico in the file explorer, I don't know of any GUI for git/build tools that's not more complicated to get working than the terminal commands in the video. All of these things said, if you know simpler ways to do this please do tell me, I'm going to make a follow up to this video at some point about the Pico and I'm always interested in learning more!

[@coenheerink4923]

@@Electromakerio Linux is fine, even for beginners. It is worth to learn because it makes things much easier in the long run.

[@user-kx5xy4pm1r]

cmake -DPICO_BOARD=blink.. CMake Warning: No source or binary directory provided. Both will be assumed to be the same as the current working directory, but note that this warning will become a fatal error in future CMake releases. CMake Error: The source directory "/home/rstk003/pico/pico-examples/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. --- Why Iam getting this I couldnot solve this

[@yaoluxttu]

"cmake -DPICO_BOARD=blink.." between "blink" and "..". there should be a whitespace.

[@OpTicThErmal]

Where was this tutorial 6 hours ago!? You ended up making all the same decisions/trade-offs I preferred (except I tried to prove to myself I could build on my mac w/o a VM), but you helped point me to the PICO_W SPECIFIC SECTION OF PICO-EXAMPLES 🤦‍♂. The only thing I could find online was "oh, working with the LED is so easy just type this line of MicroPython" ...but I'm trying to get better performance with the C SDK & for some reason the LED is fundamentally different in the W? No warnings or anything until I EVENTUALLY discovered the -DPICO_BOARD option of cmake THANKFULLY. I kept trying to flash the original blink.c for my hello world & I was scrambling in every direction. No idea why it was so different that they couldn't just redefine "PICO_DEFAULT_LED_PIN", but I trust there's a more fundamental difference in the hardware. EVEN IF I noticed the pico_w/ directory (which I wouldn't've), I never would've looked beyond wifi/ Thanks for saving my day! Also credit to this forum comment that led me here: dev.webonomic.nl/blinking-a-led-on-the-raspberry-pi-pico-w#comment-78519