I'm really surprised the folks at Pi Towers didn't release a Pico 2 W at the same time as the main Pico. Personally I always just throw a W in everything even if it doesn't need wifi, just in case :)
Thanks. If its not too much trouble, could you perhaps investigate on the Power savings mode for the Pico 2, Deep sleep and all. Thanks. (I would probably guess that the C/C++ SDK / Arduino would be suitable for bench marking tests for power.)
The PICO and PICO2 are actually quite nice when it comes to the development and how well the SDK if the PICO is created. When developing for the ESP32 I always found that with Arduino you can do a lot of things well, as long as you stay with the ecosystem and just use one core. When you start to add a RTOS and want to use the 'Arduino' Libraries then I found out quickly that a lot of libraries where not well capable for multicore. They where often sprinkled with delay's here and there, and custom timing which make that horrible to integrate in an RTOS. ESP32 is a very nice device and easy to start with... PICO has a bit steeper learning curve when using the SDK but give you a lot of power when working in an RTOS. connecting multiple SPI modules in RTOS works then very very easy.
I'm really surprised the folks at Pi Towers didn't release a Pico 2 W at the same time as the main Pico. Personally I always just throw a W in everything even if it doesn't need wifi, just in case :)
Amazing work! Quick Work - Fantastic! thank you for showing what's already possible this early with the new Pico 2!
Thanks. If its not too much trouble, could you perhaps investigate on the Power savings mode for the Pico 2, Deep sleep and all. Thanks. (I would probably guess that the C/C++ SDK / Arduino would be suitable for bench marking tests for power.)
Nice one, Les! 🙂
Why not use a picoW and pico2, both using micropython
Well done !
Oh wow!
Pico 2 arduino ide support ??
ESP32 can do what pico 2 can do, why don't you just use the ESP32?
The PICO and PICO2 are actually quite nice when it comes to the development and how well the SDK if the PICO is created. When developing for the ESP32 I always found that with Arduino you can do a lot of things well, as long as you stay with the ecosystem and just use one core.
When you start to add a RTOS and want to use the 'Arduino' Libraries then I found out quickly that a lot of libraries where not well capable for multicore. They where often sprinkled with delay's here and there, and custom timing which make that horrible to integrate in an RTOS.
ESP32 is a very nice device and easy to start with... PICO has a bit steeper learning curve when using the SDK but give you a lot of power when working in an RTOS. connecting multiple SPI modules in RTOS works then very very easy.
why? just use ESP32, its cost same, is much better, have WIFI and BT...
💩💨😷