4 releases (breaking)
|0.5.0||Sep 2, 2023|
|0.4.0||Feb 18, 2023|
|0.3.0||Dec 11, 2022|
|0.2.0||Aug 26, 2022|
#1533 in Hardware support
77 downloads per month
pimoroni_badger2040 - Board Support for the Pimoroni Badger2040
You should include this crate if you are writing code that you want to run on a Pimoroni Badger2040 - a conference-style badge built around an e-paper display and an rp2040
This crate includes the rp2040-hal, but also configures each pin of the RP2040 chip according to how it is connected up on the Badger2040.
To use this crate, your
Cargo.toml file should contain:
pimoroni_badger2040 = "0.4.0"
In your program, you will need to call
pimoroni_badger2040::Board::take().unwrap() to create
Boards structure. This will set up all the GPIOs for any on-board
devices and configure common clocks. See the examples folder for more details.
To compile an example, clone the rp-hal-boards repository and run:
rp-hal-boards/boards/pimoroni_badger2040 $ cargo build --release --example <name>
You will get an ELF file called
./target/thumbv6m-none-eabi/release/examples/<name>, where the
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_badger2040 $ cargo run --release --example <name>
If you get an error about not being able to find
$ cargo install elf2uf2-rs
then try repeating the
cargo run command above.
Flashes the Badger2040's activity LED on and off.
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:
- Fork the Project by clicking the 'Fork' button at the top of the page.
- Create your Feature Branch (
git checkout -b feature/AmazingFeature)
- Make some changes to the code or documentation.
- Commit your Changes (
git commit -m 'Add some AmazingFeature')
- Push to the Feature Branch (
git push origin feature/AmazingFeature)
- Create a New Pull Request
- An admin will review the Pull Request and discuss any changes that may be required.
- Once everyone is happy, the Pull Request can be merged by an admin, and your work is part of our project!
Code of Conduct
The contents of this repository are dual-licensed under the MIT OR Apache
2.0 License. That means you can chose either the MIT licence or the
Apache-2.0 licence when you re-use this code. See
APACHE2.0 for more
information on each specific licence.
Any submissions to this project (e.g. as Pull Requests) must be made available under these terms.