9 releases (breaking)

0.8.0 Apr 7, 2024
0.7.0 Sep 2, 2023
0.6.0 Feb 18, 2023
0.5.0 Dec 11, 2022
0.1.0 Dec 24, 2021

#1764 in Hardware support

Download history 14/week @ 2024-02-16 65/week @ 2024-02-23 8/week @ 2024-03-01 2/week @ 2024-03-08 1/week @ 2024-03-15 13/week @ 2024-03-29 105/week @ 2024-04-05 9/week @ 2024-04-12

478 downloads per month


244 lines

pimoroni-pico-explorer - Board Support for the Pimoroni Pico Explorer

You should include this crate if you are writing code that you want to run on a Pimoroni Pico Explorer - a board featuring a small LCD screen, a breadboard and some breakout headers.

This crate includes the rp2040-hal, but also configures each pin of the RP2040 chip according to how it is connected up on the Pico Explorer.


To use this crate, your Cargo.toml file should contain:

pimoroni-pico-explorer = "0.8.0"

In your program, you will need to call pimoroni_pico_explorer::Pins::new to create a new Pins structure. This will set up all the GPIOs for any on-board devices. See the examples folder for more details.


General Instructions

To compile an example, clone the rp-hal-boards repository and run:

rp-hal-boards/boards/pimoroni-pico-explorer $ cargo build --release --example <name>

You will get an ELF file called ./target/thumbv6m-none-eabi/release/examples/<name>, where the target folder is located at the top of the rp-hal-boards repository checkout. Normally you would also need to specify --target=thumbv6m-none-eabi but when building examples from this git repository, that is set as the default.

If you want to convert the ELF file to a UF2 and automatically copy it to the USB drive exported by the RP2040 bootloader, simply boot your board into bootloader mode and run:

rp-hal-boards/boards/pimoroni-pico-explorer $ cargo run --release --example <name>

If you get an error about not being able to find elf2uf2-rs, try:

$ cargo install elf2uf2-rs, then repeating the `cargo run` command above.


Displays the current temperature on the Pico Explorer's on-board LCD screen.


Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

The steps are:

  1. Fork the Project by clicking the 'Fork' button at the top of the page.
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Make some changes to the code or documentation.
  4. Commit your Changes (git commit -m 'Add some AmazingFeature')
  5. Push to the Feature Branch (git push origin feature/AmazingFeature)
  6. Create a New Pull Request
  7. An admin will review the Pull Request and discuss any changes that may be required.
  8. Once everyone is happy, the Pull Request can be merged by an admin, and your work is part of our project!

Code of Conduct

Contribution to this crate is organized under the terms of the Rust Code of Conduct, and the maintainer of this crate, the rp-rs team, promises to intervene to uphold that code of conduct.


The contents of this repository are dual-licensed under the MIT OR Apache 2.0 License. That means you can choose either the MIT license or the Apache-2.0 license when you re-use this code. See MIT or APACHE2.0 for more information on each specific license.

Any submissions to this project (e.g. as Pull Requests) must be made available under these terms.


~208K SLoC