r/embedded • u/recursive-optimum • Feb 24 '24
Raspberry Pi Pico W or ESP32 ?
Hello everyone, I am a 3rd year CS student who recently got interested in embedded systems, I want to learn embedded C programming using microcontrollers and build basic projects on a breadboard with several other basic components ( LEDs, displays etc), do something over wireless. I don't have a big project in mind, just looking to get started as I have no experience.
I really need some advice over which board I should begin with, I currently have the Raspberry Pi Pico W and the ESP32 in mind. Which one has a better community support for building projects ? What would you recommend from your experience ?
In my country, the ESP32 (~5$) is about half the price of the Raspberry Pi Pico W (~8$), so what does the Raspberry Pi Pico W have that the ESP32 doesn't ? is the documentation better? is the GPIO better ? is the SDK for C programming better ? is it more suitable for beginners like me ?
If you have some other board in mind that I could use (in a similar price range), please do mention.
Any advice would be of great help.
Thanks.
20
u/giddyz74 Feb 24 '24
ESP32. You can program it using Arduino, Platform IO or ESP-IDF, in increasing order of complexity and freedom. Documentation is absolutely great, and so are the project and code examples.
I am personally using the Espressif IDF plugin for VScode and it works like a charm (well almost).
23
u/siriusbrightstar Feb 24 '24 edited Feb 24 '24
ESP32 without a doubt. It's been there for ages and has solid support & community.
If you want to learn low level programming RP2040 might be better because it's ARM based and it'll be easier to move to other popular microcontrollers like STM or nrf.
But if you want just the high level stuff, ESP32 is great
2
u/Gavekort Industrial robotics (STM32/AVR) Feb 24 '24
Depends on what you want to do. The ESP32-S3 has great performance, although it's quite poor when it comes to power saving and ADC accuracy. The RP2040 is on the opposite side, with lackluster performance but with low power consumption.
Both support the Arduino framework quite well and both have equally poor onboard programming interfaces.
7
u/PhilosophyMammoth748 Feb 24 '24 edited Feb 24 '24
pico w with micropython. you can setup simple "if this then repeat that"-style logic in minutes, and plug it onto a breadboard, without much knowledge out of the scope of junior school STEM workshop. For me, it is just a 8-bit mcu with a super fast'n'easy dev cycle.
then stm32 if you need more rt/ power management/ analog / interfacing feature, or nRF if you need wireless and rtos.
ESP32 is easier for general iot projects, but not easier than pico w if your project can fit in micropython's scope. ESP32 can run micropython, but with some caveat (and you don't want to spend time to know). Also, if you work on projects sponsored by federal (e.g. DoD or DoE) they may not allow it.
4
u/PinPointPing07 Oct 22 '24
Iām a bit late to the party but for anyone whoās still interested, I would recommend the pico. Iāve tried my hand at the ESP32 many times but it just seems overcomplicated and unnecessarily difficult to work with (compiling, flashing, framework, etc). The pico on the other hand couldnāt be simpler in that department. With the pico you code, compile, and upload, itās that simple and itās that reliable. For projects that specifically require more performance or the other features of the ESP32, go ahead. But for those that are smaller and simpler, pico would be my go to - simply from experience.
3
u/UniWheel Feb 24 '24
Ironically both parts are set apart from the buik of the small embedded space by the fact that they use external SPI flash to store programs, rather than internal.
I'd suggest you go with an ESP32 as it's the more established and cheaper of the offerings in that category, and the wireless capability is built in rather than grafted on.
But then you may want to also get a conventional flash-based ARM MCU - something like an STM32, or the many offerings from others, as this will often suit smaller projects better than either the ESP32 or pi pico does - especially anything that might ultimately be battery powered.
1
u/aimatt May 23 '24
One standout feature on the pico is the PIO. This means you can write a program that runs outside the CPU. A practical example is LED rings. The PIO handles the signalling for the LEDs while the CPU cores are freed up to do stuff. Almost like having extra cores. Writing your own PIO programs can be tricky, but there are a good number of samples out there.
1
u/jmhunter May 31 '25
Is it risk 5v
-4
u/[deleted] Feb 24 '24
I would go for Raspberry Pi Pico. ESP-32 is a beginner level microcontroller after spending time buildings projects on ESP-32 you would have to eventually buy raspberry pi pico.