Language Selection

English French German Italian Portuguese Spanish

Raspberry Pi Foundation Release Their Own Silicon, the Raspberry Pi Pico

Filed under
Hardware

It was about time for the Raspberry Pi Foundation to release their own silicon, so here it is guys! Meet Raspberry Pi Pico, the result of several years of hard work designed to offer Raspberry Pi owners and anyone else who like building their own hardware high performance for integer workloads, flexible I/O, and low cost.

Raspberry Pi Pico is built on the RP2040 microcontroller chip, which features a dual-core ARM Cortex-M0+ processor running at 133MHz, 264KB of on-chip RAM, support for up to 16MB of off-chip flash memory via a dedicated QSPI bus, DMA controller, as well as interpolator and integer divider peripherals.

Read more

Raspberry Pi Pico Announced As $4 Microcontroller

  • Raspberry Pi Pico Announced As $4 Microcontroller

    Following November's launch of the Raspberry Pi 400 keyboard computer there is another new product from the UK foundation and it's not a new Raspberry Pi SBC.

    Raspberry Pi Pico is the new product announced today and it amounts to being a $4 micro-controller. The Pico is built around the RP2040, a microcontroller chip designed by the Raspberry Pi engineers. The RP2040 features a dual-core Arm Cortex M0+ processor with 264KB of internal RAM and support for up to 16MB of off-chip flash memory.

Raspberry Pi goes MCU with open-spec Pico

  • Raspberry Pi goes MCU with open-spec Pico

    RPi Ltd. has launched a $4 “Raspberry Pi Pico” board based on an “RP2040” chip with dual Cortex-M0+. The Pico adds 2MB flash, micro-USB, and 26 GPIO. RP2040-based boards are also available from Adafruit, Arduino, Pimoroni, and SparkFun.

    The Raspberry Pi project was modeled in part on the Arduino open hardware project that continues to dominate the world of MCU hacking and computer education. Now, after invading PC territory on the high end with the Raspberry Pi 400 keyboard computer, Raspberry Pi Trading has advanced into Arduino territory — and beyond the reach of Linux — with a custom-built RP2040 MCU with dual Cortex-M0+ cores. The RP2040 that processor drives a $4, quasi-SBC board called the Raspberry Pi Pico. Third parties have also launched RP2040 based boardlets (see farther below).

Meet Pico: Raspberry Pi’s First Microcontroller Device

  • Meet Pico: Raspberry Pi’s First Microcontroller Device [Available for $4]

    Raspberry Pi is popularly known for its single board computers. Not just limited to its impressive technology, but it also makes DIY projects affordable.

    Now, with its first microcontroller-class product “Raspberry Pi Pico” for just $4, they have introduced yet another low-cost board that is potentially going to be super popular.

    Here, I’ll mention some key highlights about it and how you can get one for yourself.

Welcome Raspberry Pi to the world of microcontrollers

  • Welcome Raspberry Pi to the world of microcontrollers

    ‘Raspberry and chips,’ not something you’d like to eat but in the world of silicon it’s actually a great combination. Eben Upton recently shared with us Raspberry Pi’s exciting vision for a revolutionary product that they were working on: a microcontroller, the RP2040, based on Raspberry Pi silicon.

    The news was both disruptive and exciting at the same time. At Arduino, we love to put our hands on innovative technologies, micros, sensors and all the building blocks that allow us to fulfill our mission of making technology simple to use for everyone. The curiosity was growing and a few weeks later we were already tinkering with the initial development tools. The processor is a very intriguing beast — it’s a dual-core Cortex-M0+ microcontroller with fairly sophisticated architecture.

    Since we have been experimenting quite a bit with multi-core processors with our Pro product, the “Portenta,” we decided to build an Arduino board based on this new silicon.

  • Meet Raspberry Pi Pico, Raspberry Silicon From Raspberry Foundation [Specs]

    Raspberry Pi Pico is a micro-controller class board exclusively from Raspberry Foundation. It is it is built on brand new RP2040. According to the foundation, Raspberry Pi Pico will remain in production until at least January, 2028. You need to pay just $4 to get this beautiful device.

Raspberry Pi Pico released and available at $4 only

  • Raspberry Pi Pico released and available at $4 only

    Last year, the Raspberry Foundation also released a brand new version of the Raspberry PI PC (personal computer), and it is directly built into a small-sized keyboard. Now there is more good news for hackers and hardware developers. They just announced their first microcontroller-based product named Raspberry Pi Pico. This small device is priced at only US $4. Unbelievable price. Let us find out about Raspberry Pi Pico hardware specs and software support.

    Many hobbyists and industrial applications or IoT use a Raspberry Pi with a microcontroller. A microcontroller is different than a microprocessor, which only contains a CPU. Raspberry Pi Pico includes an integrated processor, a small amount of memory, and other stuff for your application.

$4 Raspberry Pi Pico board features RP2040 dual-core...

  • $4 Raspberry Pi Pico board features RP2040 dual-core Cortex-M0+ MCU

    The Raspberry Pi Foundation introduced the Linux capable Raspberry Pi board in 2012 to teach programming and computers. Since then, the company has introduced models with faster processors, more memory, faster interfaces, culminating with the launch of Raspberry Pi 4 in 2019. The board also comes with a 40-pin header to teach electronics, but relying on a Linux SBC to blink a LED, gather data from sensors, or controlling servos is a bit over the top. So the Raspberry Pi Foundation decided to create their own MCU board called Raspberry Pi Pico powered by RP2040 dual-core Cortex-M0+ microcontroller designed in-house by the foundation.

Lots More Coverage About Raspberry Pi Pico

  • The Raspberry Pi Pico is a tiny $4 microcontroller running off the company’s very own chip

    Those specs might go in one ear and out the other, but the best way to illustrate the potential for a new Raspberry Pi product is to see it used in something cool. The Raspberry Pi Foundation is partnering with companies like Arduino, Adafruit, and Pimoroni to integrate the new RP2040 chip into other boards and gadgets. There’s a whole list in the blog post announcing the Pico, but a few notable ones are Pimoroni’s PicoSystem game console, Adafruit’s Feather RP 2040 board, and the Arduino Nano RP2040 Connect.

  • Raspberry Pi Pico Review: ‘Pi Silicon’ Debuts on $4 Microcontroller

    Perhaps even more important than the Pico itself is Raspberry Pi Foundation’s first foray into making its own silicon. We wanted to learn more about the RP2040 so we asked James Adams, Chief Operating Officer at Raspberry Pi Trading to tell us how “Pi Silicon” was created.

    “We couldn’t see a way to offer something differentiated in the microcontroller space using existing third-party silicon, so we set out to build our own,” Adams said. “The RP2040 chip has been a long time in the making - we started initial work at the back end of 2016, we had some test silicon in our hands in September 2018 which we then reworked into the final device we use on the Raspberry Pi Pico board. The device has evolved substantially since those early days. We learned a lot from our first test silicon and I think, although it has taken a while, what we've ended up with is very exciting (in terms the architecture and performance per $) - it's a superb bit of engineering. The RP2040 chips are fabricated at TSMC on their 40nm process.”

    Adams outlined some of the advantages of the custom silicon.

  • Raspberry Pi Enters Microcontroller Game With $4 Pico

    The microcontroller in question, the RP2040, is also Raspberry Pi’s first foray into custom silicon, and it’s got a dual-core Cortex M0+ with luxurious amounts of SRAM and some very interesting custom I/O peripheral hardware that will likely mean that you never have to bit-bang again. But a bare microcontroller is no fun without a dev board, and the Raspberry Pi Pico adds 2 MB of flash, USB connectivity, and nice power management.

  • Raspberry Pi Pico, RP2040 and Adafruit family of boards

    The Raspberry Pi Pico, RP2040 and Adafruit family of boards are here! We’re doing our live broadcast at 2am EST and will be updating this page soon!

  • The Raspberry Pi Pico is a new $4 microcontroller

    tl;dr: The Raspberry Pi Pico is a new $4 microcontroller board with a custom new dual-core 133 MHz ARM Cortex-M0+ microprocessor, 2MB of built-in flash memory, 26 GPIO pins, an assortment of SPI, I2C, UART, ADC, PWM, and PIO channels.

    It also has a few other party tricks, like edge castellations that make it easier to solder the Pico to other boards.

    The Pico is powered by a new RP2040 chip—a brand new Raspberry-Pi-built ARM processor. And the best thing about this processor is the insanely-detailed Datasheet available on the Pico website that steps through every bit of the chip's architecture.

  • Raspberry Pi Pico, the first microcontroller released by Raspberry Pi Foundation, based on the new RP2040 MCU.

    Raspberry Pi Pico is the first product using Raspberry Pi’s own MCU, the RP2040. The chip features dual-core ARM Cortex-M0+ at up to 133MHz with a RAM of 256KB, 2MB flash memory, and 264K multi-bank high-performance SRAM. Designed to be a flexible, low-power, and cost-effective development platform, Raspberry Pi Pico offers on-chip PLL for variable core frequency and access to the 30 GPIO pins.

  • Raspberry Pi Pico microcontroller: specifications, features and RP2040

    The ultra-light, ultra-small Raspberry Pi Pico microcontroller board is ideal for embedding inside digital projects. Raspberry Pi Pico represents two major firsts for Raspberry Pi: it’s the first microcontroller development board from Raspberry Pi; it’s also the first device to use a silicon chip designed by Raspberry Pi’s in‑house Application-Specific Integrated Circuit (ASIC) team.

  • Programming Raspberry Pi Pico with Python and MicroPython

    MicroPython is an implementation of the Python programming language that is already popular among Raspberry Pi users. MicroPython is built specifically for microcontrollers like the RP2040 that powers Raspberry Pi Pico. MicroPython offers the same friendly syntax as Python. It allows for full control over Raspberry Pi Pico’s various features, including its Programmable Input/Output (PIO) functionality.

  • How to solder GPIO pin headers to Raspberry Pi Pico

    Solder the four corner pins first. Take your time, don’t rush, and remember that mistakes can always be fixed.

  • Hello Raspberry Pi Pico and RP2040!

    That's not nearly all, though, because Raspberry Pi has also enabled all of their contributors, including SparkFun, to create their own development boards that utilize the RP2040 processor. With that knowledge, we are happy to also announce today three new SparkFun Original boards with the RP2040 at their hearts.

  • Happy Pico/RP2040 Day!

    We've been low-key waiting for Eben and Raspberry Pi to do something with microcontrollers for years, and we're not disappointed in the RP2040 and the support around it. As soon as we got word, we went full-on to make the best of what we do, but for this new microcontroller. We also made a few new things that this new chip inspired us to do.

    From the 20 or so designs that made it out of the initial flurry of ideas to design stage, 10-12 are ready for launch day, and the rest will follow in the next couple of months as the dust settles and we find what you love to do with the RP2040 and Pico.

    By each category, here's what we've done in brief:

  • Introducing Raspberry Pi Pico

    Issue 39 of HackSpace magazine comes with a free Pico. You can get one at your local newsagents or online. You'll also get a free Pico if you subscribe to HackSpace from £10. If you're in the UK you can subscribe here. If you're elsewhere in the world, head here to subscribe. Alternatively, you can get one from your favourite electronics retailer for just $4 plus local taxes and shipping.

  • RP2040 in depth

    There’s quite a lot going on inside the black package of RP2040 – including two processor cores, peripherals for many protocols, and PIO – and these all need to access memory. The fully connected bus fabric gives fast and predictable performance, even when lots of things are happening at once.

  • Raspberry Pi Pico FAQ

    The Raspberry Pi Pico board design files are open-source, along with all the provided software, examples, and documentation. The internal design of the RP2040 microcontroller itself is not open-source.

NeoPixel dithering with Pico

Raspberry PI Pico: Foundation entering the micro-controllers

From ITPro

  • What is the Raspberry Pi Pico?

    It includes a dual-core ARM Cortex-M0+ processor, 264KB of on-chip RAM and support for up to 16MB off-chip Flash memory, direct memory access (DMA) controller, as well as a rich set of peripherals. The chip is also augmented with the Raspberry Pi Foundation’s unique programmable I/O (PIO) subsystem.

Getting Started with Raspberry Pi Pico using MicroPython and C

  • Getting Started with Raspberry Pi Pico using MicroPython and C

    Raspberry Pi Pico board was just launched last Thursday, but thanks to Cytron I received a sample a few hours after the announcement, and I’ve now had time to play with the board using MicroPython and C programming language.

    I went to the official documentation to get started, but I had to look around to achieve what I wanted to do, namely blinking some LEDs, so I’ll document my experience with my own getting started guide for Raspberry Pi Pico using a computer running Ubuntu 20.04 operating system. The instructions will be similar for Windows and Mac OS.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Now you can make video calls on a PinePhone (but it’s very much a work in progress)

When the PinePhone began shipping to early adopters, it had all the hardware you’d expect from a smartphone, but it lacked the software needed to make some of that hardware work. If you were one of the first people to get your hands on a PinePhone, you had a Linux-friendly phone with a camera that couldn’t be used to take pictures or record video. But over time kernel and app developers got the phone’s front and rear cameras working, and now most Linux distributions for the PinePhone allow you to take pictures (of mediocre quality). One thing you couldn’t do until recently though? Video calls. But now it looks like that’s possible too… soft of. The process looks rather painful at the moment, but it should get better over time. Read more Also: Plasma Mobile tarball release: bugfixes and new releases

A warning about 5.12-rc1

  • A warning about 5.12-rc1
    Hey peeps - some of you may have already noticed that in my public git
    tree, the "v5.12-rc1" tag has magically been renamed to
    "v5.12-rc1-dontuse". It's still the same object, it still says
    "v5.12-rc1" internally, and it is still is signed by me, but the
    user-visible name of the tag has changed.
    
    
    
    
    The reason is fairly straightforward: this merge window, we had a very
    innocuous code cleanup and simplification that raised no red flags at
    all, but had a subtle and very nasty bug in it: swap files stopped
    working right.  And they stopped working in a particularly bad way:
    the offset of the start of the swap file was lost.
    
    
    
    
    Swapping still happened, but it happened to the wrong part of the
    filesystem, with the obvious catastrophic end results.
    
    
    
    
    Now, the good news is even if you do use swap (and hey, that's nowhere
    near as common as it used to be), most people don't use a swap *file*,
    but a separate swap *partition*. And the bug in question really only
    happens for when you have a regular filesystem, and put a file on it
    as a swap.
    
    
    
    
    And, as far as I know, all the normal distributions set things up with
    swap partitions, not files, because honestly, swapfiles tend to be
    slower and have various other complexity issues.
    
    
    
    
    The bad news is that the reason we support swapfiles in the first
    place is that they do end up having some flexibility advantages, and
    so some people do use them for that reason. If so, do not use rc1.
    Thus the renaming of the tag.
    
    
    
    
    Yes, this is very unfortunate, but it really wasn't a very obvious
    bug, and it didn't even show up in normal testing, exactly because
    swapfiles just aren't normal. So I'm not blaming the developers in
    question, and it also wasn't due to the odd timing of the merge
    window, it was just simply an unusually nasty bug that did get caught
    and is fixed in the current tree.
    
    
    
    
    But I want everybody to be aware of because _if_ it bites you, it
    bites you hard, and you can end up with a filesystem that is
    essentially overwritten by random swap data. This is what we in the
    industry call "double ungood".
    
    
    
    
    Now, there's a couple of additional reasons for me writing this note
    other than just "don't run 5.12-rc1 if you use a swapfile". Because
    it's more than just "ok, we all know the merge window is when all the
    new scary code gets merged, and rc1 can be a bit scary and not work
    for everybody". Yes, rc1 tends to be buggier than later rc's, we are
    all used to that, but honestly, most of the time the bugs are much
    smaller annoyances than this time.
    
    
    
    
    And in fact, most of our rc1 releases have been so solid over the
    years that people may have forgotten that "yeah, this is all the new
    code that can have nasty bugs in it".
    
    
    
    
    One additional reason for this note is that I want to not just warn
    people to not run this if you have a swapfile - even if you are
    personally not impacted (like I am, and probably most people are -
    swap partitions all around) - I want to make sure that nobody starts
    new topic branches using that 5.12-rc1 tag. I know a few developers
    tend to go "Ok, rc1 is out, I got all my development work into this
    merge window, I will now fast-forward to rc1 and use that as a base
    for the next release". Don't do it this time. It may work perfectly
    well for you because you have the common partition setup, but it can
    end up being a horrible base for anybody else that might end up
    bisecting into that area.
    
    
    
    
    And the *final* reason I want to just note this is a purely git
    process one: if you already pulled my git tree, you will have that
    "v5.12-rc1" tag, and the fact that it no longer exists in my public
    tree under that name changes nothing at all for you. Git is
    distributed, and me removing that tag and replacing it with another
    name doesn't magically remove it from other copies unless you have
    special mirroring code.
    
    
    
    
    So if you have a kernel git tree (and I'm here assuming "origin"
    points to my trees), and you do
    
    
    
    
         git fetch --tags origin
    
    
    
    
    you _will_ now see the new "v5.12-rc1-dontuse" tag. But git won't
    remove the old v5.12-rc1 tag, because while git will see that it is
    not upstream, git will just assume that that simply means that it's
    your own local tag. Tags, unlike branch names, are a global namespace
    in git.
    
    
    
    
    So you should additionally do a "git tag -d v5.12-rc1" to actually get
    rid of the original tag name.
    
    
    
    
    Of course, having the old tag doesn't really do anything bad, so this
    git process thing is entirely up to you. As long as you don't _use_
    v5.12-rc1 for anything, having the tag around won't really matter, and
    having both 'v5.12-rc1' _and_ 'v5.12-rc1-dontuse' doesn't hurt
    anything either, and seeing both is hopefully already sufficient
    warning of "let's not use that then".
    
    
    
    
    Sorry for this mess,
                 Linus
    
    
    
    
    
  • A warning about 5.12-rc1

    Linus Torvalds has sent out a note telling people not to install the recent 5.12-rc1 development kernel; this is especially true for anybody running with swap files. "But I want everybody to be aware of because _if_ it bites you, it bites you hard, and you can end up with a filesystem that is essentially overwritten by random swap data. This is what we in the industry call 'double ungood'." Additionally, he is asking maintainers to not start branches from 5.12-rc1 to avoid future situations where people land in the buggy code while bisecting problems.

  •  
  • Linux 5.12-rc2 Likely Coming Early Due To That Nasty File-System Corruption Bug

    Linus Torvalds has now warned developers over using Linux 5.12-rc1 as a basis for their future branches and is looking to release 5.12-rc2 ahead of schedule as a result of that problematic file-system corruption bug stemming from a swap file bug. 

Games: Godot, Artifact, Loop Hero, and Urtuk: The Desolation

  • Godot Showcase - Primal Light developer interview

    Welcome to the fourth developer interview following the introduction of the Godot Showcase page! This week, we are interviewing the studio Fat Gem about their first game Primal Light.

  • Valve gives up on Artifact setting it free with Artifact Classic and Artifact Foundry | GamingOnLinux

    Valve's Dota themed card game Artifact has now well and truly failed, as they've now stopped the 2.0 redevelopment which is now named Artifact Foundry with the original as Artifact Classic and both now free to play. In a post titled "The Future of Artifact", Valve mentioned how the player count fell off dramatically and it was pretty much dead shortly after being released. Even though the big 2.0 revamp was far along in development, they've now formally and totally shelved it as they "haven't managed to get the active player numbers to a level that justifies further development at this time".

  • Loop Hero is out now and I'm going to need help to tear myself away from it | GamingOnLinux

    Loop Hero, probably the only titles I've pre-ordered in the last few years is officially out now and I really will need some help to pull myself away from running just one more loop. It's such a strange and beautifully intoxicating mix of genres. For each loop through you're placed into a world full of nothing but a path and it's up to you to build up the world each time. You do this through your deck of cards, while the hero automatically loops around the path and fights enemies along the way without your input. Even though you don't have direct control, there's quite a lot of strategy involved in it.

  • Dark low-fantasy tactical survival RPG 'Urtuk: The Desolation' is out now | GamingOnLinux

    Urtuk: The Desolation from David Kaleta presents you with a dark world in a low-fantasy settings where you guide a team of survivors through a ruined world. Note: key provided by the developer. Hitting nearly one thousand user reviews and a Very Positive rating on Steam overall, Urtuk: The Desolation seems to have managed to hit a sweet spot. Giving you tough turn-based combat, with a character progression system that sees you extracting skills and traits from fallen enemies. It's a bit of a gross world and the main character, Urtuk, is an escaped subject of experimentation with a severe mutation and worsening health. The idea is to eventually find a cure but getting there will be tough.

today's howtos

  • How to find duplicate files in Linux? Help is here with the fdupes command! - Webleit.info

    Fdupes is a command line tool that allows you to find all duplicate files through the console. The advantage over using graphical tools like fslint is of course the speed. At the end of the day, there is nothing faster and more convenient than the Linux console. Why should we look for duplicate files in Linux? No matter what operating system you use sooner or later, your computer will contain many files of different sizes, and if you’re not careful enough, repeating them can cost you disk space that you need. For example, you inadvertently downloaded the same ultra HD movie with 40 giga bytes twice.

  • How to Install Moodle with Nginx and Let's Encrypt SSL on Ubuntu 20.04

    Moodle is a free and open-source Learning Management System written in PHP. It provides a way for tutors and instructors to create courses for their students or learners. Moodle provides a robust and secure integrated system and comes with a custom dashboard that helps users to access current, past or future courses, as well as review pending work. It is used by many schools, universities, and organizations across the globe and provides a better learning experience. It provides a rich set of features including, wiki, grading, assignment submission, online quizzes, discussion boards, and more. In this tutorial, we will show you how to install Moodle with Nginx web server and Let's Encrypt SSL on Ubuntu 20.04.

  • Install WordPress Automatically on Ubuntu 20.04 using WordOps

    WordOps is a simple tool that provides the ability to deploy WordPress sites from the command line using an optimized LEMP stack. The LEMP software stack consists of a group of software that describes a Linux Operating System, an Nginx web server (pronounced engine-x), a MySQL database with the dynamic processing being handled by PHP. LEMP is an acronym for Linux, Engine-x (Nginx), MySQL and PHP. WordOps simplifies so much of the process of installing and configuring all the packages from the LEMP stack needed to deploy a site while taking care of creating virtual hosts in Nginx, installing WordPress, and even gets you a SSL certificate. It also installs some components that allow you to see statistics about the server’s workload. In this tutorial we’ll use WordOps to quickly and easily install WordPress on an Ubuntu 20.04 machine, and we’ll check out and explain some of the extra features that WordOps offers.

  • How to Find Out When a Webpage Was Published - Make Tech Easier

    When you’re doing research on a topic, it’s vital to ensure your sources are up to date. If you’re writing an academic paper, dates of publication are often required in the citations. The majority of the time, getting the date is easy: simply look on the site and find the published date to find how recent it was. Things get a little more complicated when there is no date listed on the webpage. When this happens, how do you know when a webpage was published?

  • How to install Wireshark 3.4.3 on a Chromebook

    Today we are looking at how to install Wireshark 3.4.3 on a Chromebook. Please follow the video/audio guide as a tutorial where we explain the process step by step and use the commands below.

  • Another Piece For The Home Network Puzzle – A Return To Cisco IOS! – Jon's FOSS Blog

    I’ve missed the good old days of configuring and setting up good quality switching hardware (like the big, huge Cisco switches and routers I used to experiment on with their IOS command line interface). I recently ordered this newer, smaller Cisco switch which can also provide power to a new “prosumer” WiFi AP (no power cables needed).

  • Making environment variables accessible in front-end containers - Red Hat Developer

    When building a container for a single-page application using any modern JavaScript framework (such as Angular, React, or Vue.js), you might find that the configuration settings are different depending on where the container will run. A typical case would be the base URL for your API, which will differ depending on whether you are testing the application or deploying it into production. Developers usually solve this problem using environment variables. Environment variables typically work on the backend because that is where code runs. But what if your application lives in the user’s browser? There are many ways around this limitation. In some cases, you might build a server whose endpoint holds the necessary parameters. Another workaround is to use PHP to inject the environment variables as globals in the JavaScript code. Both of these options work, but it would be ideal to inject the environment variables as part of the container build process. That way, you don’t have to change the codebase, and you can still deliver the application content using a static web server like NGINX. This article shows you how to inject environment variables directly into your codebase as you build your container.

  • The Strange Case of How We Escaped the Docker Default Container

    TL;DR During an internal container-based Red Team engagement, the Docker default container spontaneously and silently changed cgroups overnight, which allowed us to escalate privileges and gain...

  • How to copy and paste between host and VM