mirror of
https://github.com/rust-embedded/awesome-embedded-rust.git
synced 2024-11-18 23:41:10 +00:00
Rahul Thakoor
GitHub
commit
8d44454e85
6 changed files with 198 additions and 65 deletions
1
.github/CODEOWNERS
vendored
Normal file
1
.github/CODEOWNERS
vendored
Normal file
|
|
@ -0,0 +1 @@
|
|||
* @rust-embedded/resources @RandomInsano @berkus @rahul-thakoor
|
||||
37
CODE_OF_CONDUCT.md
Normal file
37
CODE_OF_CONDUCT.md
Normal file
|
|
@ -0,0 +1,37 @@
|
|||
# The Rust Code of Conduct
|
||||
|
||||
## Conduct
|
||||
|
||||
**Contact**: [Resources team](https://github.com/rust-embedded/wg#the-resources-team)
|
||||
|
||||
* We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.
|
||||
* On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all.
|
||||
* Please be kind and courteous. There's no need to be mean or rude.
|
||||
* Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
|
||||
* Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.
|
||||
* We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the [Citizen Code of Conduct](http://citizencodeofconduct.org/); if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups.
|
||||
* Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Resources team][team] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back.
|
||||
* Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.
|
||||
|
||||
## Moderation
|
||||
|
||||
These are the policies for upholding our community's standards of conduct.
|
||||
|
||||
1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)
|
||||
2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.
|
||||
3. Moderators will first respond to such remarks with a warning.
|
||||
4. If the warning is unheeded, the user will be "kicked," i.e., kicked out of the communication channel to cool off.
|
||||
5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.
|
||||
6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology.
|
||||
7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed.
|
||||
8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.
|
||||
|
||||
In the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
|
||||
|
||||
And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better — remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
|
||||
|
||||
The enforcement policies listed above apply to all official embedded WG venues; including official IRC channels (#rust-embedded); GitHub repositories under rust-embedded; and all forums under rust-embedded.org (forum.rust-embedded.org).
|
||||
|
||||
*Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).*
|
||||
|
||||
[team]: https://github.com/rust-embedded/wg#the-resources-team
|
||||
|
|
@ -2,12 +2,9 @@
|
|||
|
||||
Please note that this project is released with a [Contributor Code of Conduct](Code-of-Conduct.md). By participating in this project you agree to abide by its terms.
|
||||
|
||||
# The pull request should have a useful title. Pull requests with `Update readme.md` as title will be closed right away because I'm so tired of nobody reading this document. Please carefully read everything in `Adding to this list`.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- [Adding to this list](#adding-to-this-list)
|
||||
- [Creating your own awesome list](#creating-your-own-awesome-list)
|
||||
- [Adding something to an awesome list](#adding-something-to-an-awesome-list)
|
||||
- [Updating your Pull Request](#updating-your-pull-request)
|
||||
|
||||
|
|
@ -34,11 +31,11 @@ If you have something awesome to contribute to an awesome list, this is how you
|
|||
|
||||
You'll need a [GitHub account](https://github.com/join)!
|
||||
|
||||
1. Access the awesome list's GitHub page. For example: https://github.com/berkus/awesome-embedded-rust
|
||||
1. Access the awesome list's GitHub page. For example: https://github.com/rust-embedded/awesome-embedded-rust
|
||||
2. Click on the `readme.md` file: 
|
||||
3. Now click on the edit icon. 
|
||||
4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). 
|
||||
5. Say why you're proposing the changes, and then click on "Propose file change". 
|
||||
5. Say why you're proposing the changes (see section [Adding to this list](#adding-to-this-list) for details), and then click on "Propose file change". 
|
||||
6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)!
|
||||
|
||||
## Updating your Pull Request
|
||||
|
|
|
|||
|
|
@ -2,17 +2,11 @@
|
|||
|
||||
## Our Pledge
|
||||
|
||||
In the interest of fostering an open and welcoming environment, we as
|
||||
contributors and maintainers pledge to making participation in our project and
|
||||
our community a harassment-free experience for everyone, regardless of age, body
|
||||
size, disability, ethnicity, gender identity and expression, level of experience,
|
||||
nationality, personal appearance, race, religion, or sexual identity and
|
||||
orientation.
|
||||
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to creating a positive environment
|
||||
include:
|
||||
Examples of behavior that contributes to creating a positive environment include:
|
||||
|
||||
* Using welcoming and inclusive language
|
||||
* Being respectful of differing viewpoints and experiences
|
||||
|
|
@ -22,53 +16,31 @@ include:
|
|||
|
||||
Examples of unacceptable behavior by participants include:
|
||||
|
||||
* The use of sexualized language or imagery and unwelcome sexual attention or
|
||||
advances
|
||||
* The use of sexualized language or imagery and unwelcome sexual attention or advances
|
||||
* Trolling, insulting/derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or electronic
|
||||
address, without explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
* Publishing others' private information, such as a physical or electronic address, without explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a professional setting
|
||||
|
||||
## Our Responsibilities
|
||||
|
||||
Project maintainers are responsible for clarifying the standards of acceptable
|
||||
behavior and are expected to take appropriate and fair corrective action in
|
||||
response to any instances of unacceptable behavior.
|
||||
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
|
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or
|
||||
reject comments, commits, code, wiki edits, issues, and other contributions
|
||||
that are not aligned to this Code of Conduct, or to ban temporarily or
|
||||
permanently any contributor for other behaviors that they deem inappropriate,
|
||||
threatening, offensive, or harmful.
|
||||
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies both within project spaces and in public spaces
|
||||
when an individual is representing the project or its community. Examples of
|
||||
representing a project or community include using an official project e-mail
|
||||
address, posting via an official social media account, or acting as an appointed
|
||||
representative at an online or offline event. Representation of a project may be
|
||||
further defined and clarified by project maintainers.
|
||||
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported by contacting the project team at berkus@gmail.com. All
|
||||
complaints will be reviewed and investigated and will result in a response that
|
||||
is deemed necessary and appropriate to the circumstances. The project team is
|
||||
obligated to maintain confidentiality with regard to the reporter of an incident.
|
||||
Further details of specific enforcement policies may be posted separately.
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Embedded WG. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
|
||||
|
||||
Project maintainers who do not follow or enforce the Code of Conduct in good
|
||||
faith may face temporary or permanent repercussions as determined by other
|
||||
members of the project's leadership.
|
||||
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
||||
available at [http://contributor-covenant.org/version/1/4][version]
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
|
||||
|
||||
[homepage]: http://contributor-covenant.org
|
||||
[version]: http://contributor-covenant.org/version/1/4/
|
||||
[version]: http://contributor-covenant.org/version/1/4/
|
||||
|
|
|
|||
163
README.md
163
README.md
|
|
@ -6,23 +6,28 @@ This is a curated list of resources related to embedded and low-level programmin
|
|||
|
||||
[<img src="https://rawgit.com/rust-embedded/awesome-embedded-rust/master/rust-embedded-logo-256x256.png" align="right" width="256">](http://www.rust-embedded.org)
|
||||
|
||||
This project is developed and maintained by the [Resources team][team].
|
||||
|
||||
## Table of contents
|
||||
|
||||
* [Community](#community)
|
||||
* [Books, blogs and training materials](#books-blogs-and-training-materials)
|
||||
* [Tools](#tools)
|
||||
* [Device crates](#device-crates)
|
||||
* [ARM](#arm)
|
||||
* [Nordic](#nordic)
|
||||
* [NXP](#nxp)
|
||||
* [STMicroelectronics](#stmicroelectronics)
|
||||
* [Texas Instruments](#texas-instruments)
|
||||
* [MSP430](#msp430)
|
||||
* [HAL implementation crates](#hal-implementation-crates)
|
||||
* [OS](#os)
|
||||
* [Nordic](#nordic-1)
|
||||
* [NXP](#nxp-1)
|
||||
* [STMicroelectronics](#stmicroelectronics-1)
|
||||
* [Texas Instruments](#texas-instruments)
|
||||
* [Texas Instruments](#texas-instruments-1)
|
||||
* [Espressif](#espressif)
|
||||
* [Architecture support crates](#architecture-support-crates)
|
||||
* [ARM](#arm)
|
||||
* [Board support crates](#board-support-crates)
|
||||
* [Nordic](#nordic-2)
|
||||
* [NXP](#nxp-2)
|
||||
|
|
@ -32,19 +37,23 @@ This is a curated list of resources related to embedded and low-level programmin
|
|||
* [no-std crates](#no-std-crates)
|
||||
* [Rust forks](#rust-forks)
|
||||
- [AVR](#avr)
|
||||
* [Firmware projects](#firmware-projects)
|
||||
* [License](#license)
|
||||
|
||||
## Community
|
||||
|
||||
In 2018 Mozilla asked for creation of an embedded workgroup to help drive adoption in the Rust ecosystem.
|
||||
In 2018 Rust community has created an embedded workgroup to help drive adoption in the Rust ecosystem.
|
||||
|
||||
- [Embedded WG](https://github.com/rust-lang-nursery/embedded-wg/), including newsletters with progress updates.
|
||||
|
||||
- You can usually find the members of the embedded WG on the `#rust-embedded` channel (server: `irc.mozilla.org`).
|
||||
|
||||
- [embedded.rs](https://t.me/embedded_rs) Telegram chat about Rust for microcontrollers in Russian language.
|
||||
|
||||
## Books, blogs and training materials
|
||||
|
||||
- [Discovery](https://japaric.github.io/discovery/) by @japaric — this book is an introductory course on microcontroller-based embedded systems that uses Rust as the teaching language.
|
||||
- [Discovery](https://rust-embedded.github.io/discovery) by @rust-embedded — this book is an introductory course on microcontroller-based embedded systems that uses Rust as the teaching language. Original author: @japaric
|
||||
- [Cortex-M Quickstart](https://docs.rs/cortex-m-quickstart/0.3.1/cortex_m_quickstart/) by @japaric – a template and introduction to embedded Rust, suitable for developers familiar to embedded development but new to embedded Rust.
|
||||
- [Exploring Rust on Teensy](https://branan.github.io/teensy/) by @branan — Beginner set of articles on getting into embedded dev in Rust.
|
||||
- [Pragmatic Bare Metal Rust](http://www.hashmismatch.net/pragmatic-bare-metal-rust/) A starter article about starting Rust development on STM32 microcontrollers (cubeMX + FFI).
|
||||
- [Using Rust in an Embedded Project: A Simple Example](https://spin.atomicobject.com/2016/07/08/rust-embedded-project-example/#.V3-os-6qlZw.hackernews) Article and some links on setting up Rust cross-compiling.
|
||||
|
|
@ -59,6 +68,7 @@ In 2018 Mozilla asked for creation of an embedded workgroup to help drive adopti
|
|||
- [cortex-m rtfm](https://github.com/japaric/cortex-m-rtfm) RTFM framework for ARM Cortex-M microcontrollers
|
||||
- [msp430 rtfm](https://github.com/japaric/msp430-rtfm) RTFM framework for MSP430 MCUs
|
||||
- [FreeRTOS.rs](https://github.com/hashmismatch/freertos.rs) Rust interface for the FreeRTOS API
|
||||
- [MicroRust](https://droogmic.github.io/microrust/) Introductory book for embedded development in Rust on the micro:bit.
|
||||
|
||||
## Tools
|
||||
|
||||
|
|
@ -67,31 +77,32 @@ In 2018 Mozilla asked for creation of an embedded workgroup to help drive adopti
|
|||
- [μtest](https://github.com/japaric/utest) unit testing for microcontrollers and other no-std systems.
|
||||
- [bindgen](https://crates.io/crates/bindgen) Automatically generates Rust FFI bindings to C and C++ libraries. - 
|
||||
- [cortex-m semihosting](https://github.com/japaric/cortex-m-semihosting) Semihosting for ARM Cortex-M processors
|
||||
- [bobbin-cli](https://github.com/bobbin-rs/bobbin-cli) A Rust command line tool to simplify embedded development and deployment.
|
||||
|
||||
## Device crates
|
||||
|
||||
Register definition for microcontroller families. Usually generated using [`svd2rust`]. - 
|
||||
|
||||
[`svd2rust`]: https://crates.io/crates/svd2rust
|
||||
[`svd2rust`]: https://crates.io/crates/svd2rust
|
||||
|
||||
*NOTE* You may be able to find even more device crates by searching for the
|
||||
[`svd2rust`][svd2rust-kw] keyword on crates.io!
|
||||
|
||||
[svd2rust-kw]: https://crates.io/keywords/svd2rust
|
||||
|
||||
### ARM
|
||||
### Microchip
|
||||
|
||||
- [`cortex-m`](https://github.com/japaric/cortex-m) Low level access to Cortex-M processors
|
||||
- [`atsamd21`](https://github.com/wez/atsamd21-rs) Peripheral access API for Microchip (formerly Atmel) SAMD21 microcontrollers. This git repo hosts both the device crate and the hal.
|
||||
|
||||
### Nordic
|
||||
|
||||
- [`nrf51`](https://crates.io/crates/nrf51) Peripheral access API for nRF51 microcontrollers (generated using svd2rust) - 
|
||||
- [`nrf51822` playground](https://github.com/japaric/nrf51822) A crate to play with the nrf51822 module
|
||||
|
||||
### NXP
|
||||
|
||||
- [`lpc82x`](https://crates.io/crates/lpc82x) - 
|
||||
- [`mkw41z`](https://crates.io/crates/mkw41z) - 
|
||||
- [`k64`](https://crates.io/crates/k64) - 
|
||||
|
||||
### STMicroelectronics
|
||||
|
||||
|
|
@ -100,9 +111,17 @@ Register definition for microcontroller families. Usually generated using [`svd2
|
|||
- [`stm32f100xx`](https://github.com/japaric/stm32f100xx) Peripheral access API for STM32F100XX microcontrollers (generated using svd2rust) - 
|
||||
- [`stm32f30x`](https://crates.io/crates/stm32f30x) Peripheral access API for STM32F30X microcontrollers (generated using svd2rust) - 
|
||||
- [`stm32f429`](https://crates.io/crates/stm32f429) Peripheral access API for STM32F429 microcontrollers (generated using svd2rust) - 
|
||||
- [`stm32f469xx`](https://crates.io/crates/stm32f469xx) Peripheral access API for STM32f469XX microcontrollers (generated using svd2rust) -
|
||||
- [`stm32l151`](https://crates.io/crates/stm32l151) - 
|
||||
* [`stm32-rs`](https://github.com/adamgreig/stm32-rs) Peripheral access API for most STM32 microcontrollers (generated using svd2rust): [stm32f0](https://crates.io/crates/stm32f0), [stm32f1](https://crates.io/crates/stm32f1), [stm32f2](https://crates.io/crates/stm32f2), [stm32f3](https://crates.io/crates/stm32f3), [stm32f4](https://crates.io/crates/stm32f4), [stm32f7](https://crates.io/crates/stm32f7), [stm32l0](https://crates.io/crates/stm32l0), [stm32l1](https://crates.io/crates/stm32l1), [stm32l4](https://crates.io/crates/stm32l4), [stm32h7](https://crates.io/crates/stm32h7)
|
||||
|
||||
### Texas Instruments
|
||||
|
||||
- [`tm4c123x`](https://crates.io/crates/tm4c123x) Peripheral access API for TM4C123x microcontrollers (generated using svd2rust)
|
||||
- [`tm4c129x`](https://crates.io/crates/tm4c129x) Peripheral access API for TM4C129x microcontrollers (generated using svd2rust)
|
||||
|
||||
### MSP430
|
||||
|
||||
- [`msp430g2553`](https://github.com/japaric/msp430g2553) Peripheral access API for MSP430G2553 microcontrollers (generated using svd2rust)
|
||||
- [rust on msp](https://github.com/japaric/rust_on_msp) Simple blinking LED example that runs on MSP430.
|
||||
- [msp430 quickstart](https://github.com/japaric/msp430-quickstart) some examples for msp430
|
||||
|
|
@ -111,7 +130,7 @@ Register definition for microcontroller families. Usually generated using [`svd2
|
|||
|
||||
Implementations of [`embedded-hal`] for microcontroller families and systems running some OS. - 
|
||||
|
||||
[`embedded-hal`]: https://crates.io/crates/embedded-hal
|
||||
[`embedded-hal`]: https://crates.io/crates/embedded-hal
|
||||
|
||||
*NOTE* You may be able to find even more HAL implementation crates by searching for the
|
||||
[`embedded-hal-impl`] and [`embedded-hal`][embedded-hal-kw] keywords on crates.io!
|
||||
|
|
@ -123,7 +142,7 @@ Implementations of [`embedded-hal`] for microcontroller families and systems run
|
|||
|
||||
- [`linux-embedded-hal`] for embedded Linux systems like the Raspberry Pi. - 
|
||||
|
||||
[`linux-embedded-hal`]: https://crates.io/crates/linux-embedded-hal
|
||||
[`linux-embedded-hal`]: https://crates.io/crates/linux-embedded-hal
|
||||
|
||||
### Nordic
|
||||
|
||||
|
|
@ -135,7 +154,7 @@ Also check the list of [NXP board support crates][nxp-bsc]!
|
|||
|
||||
[nxp-bsc]: #nxp-1
|
||||
|
||||
- [`lpc82x-hal`](https://github.com/braun-robotics/rust-lpc82x-hal)
|
||||
- [`lpc82x-hal`](https://crates.io/crates/lpc82x-hal) - [](https://crates.io/crates/lpc82x-hal)
|
||||
|
||||
- [`mkw41z-hal`](https://crates.io/crates/mkw41z-hal) - 
|
||||
|
||||
|
|
@ -161,15 +180,33 @@ Also check the list of [STMicroelectronics board support crates][stm-bsc]!
|
|||
|
||||
- [`stm32l151-hal`](https://crates.io/crates/stm32l151-hal) - 
|
||||
|
||||
- [`stm32l432xx-hal`](https://crates.io/crates/stm32l432xx-hal) - 
|
||||
- Has examples that can run on boards like the [Nucleo-L432KC] and similar boards
|
||||
|
||||
[Nucleo-L432KC]: https://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mcu-eval-tools/stm32-mcu-eval-tools/stm32-mcu-nucleo/nucleo-l432kc.html
|
||||
|
||||
### Texas Instruments
|
||||
|
||||
- [`tm4c123x-hal`](https://github.com/thejpster/tm4c123x-hal)
|
||||
|
||||
[Blue pill]: http://wiki.stm32duino.com/index.php?title=Blue_Pill
|
||||
|
||||
### Espressif
|
||||
|
||||
- [`esp8266-hal`](https://github.com/emosenkis/esp8266-hal)  (not supported by rustc, so must be built with [mrustc](https://github.com/thepowersgang/mrustc), typically via the [esp-rs](https://github.com/emosenkis/esp-rs) build script)
|
||||
|
||||
## Architecture support crates
|
||||
|
||||
Crates tailored for general CPU architectures.
|
||||
|
||||
### ARM
|
||||
|
||||
- [`cortex-m`](https://github.com/japaric/cortex-m) Low level access to Cortex-M processors - 
|
||||
- [`cortex-a`](https://github.com/andre-richter/cortex-a) Low level access to Cortex-A processors (early state) - 
|
||||
|
||||
## Board support crates
|
||||
|
||||
Crates tailored for specific development boards.
|
||||
Crates tailored for specific boards.
|
||||
|
||||
[STM32F3DISCOVERY]: http://www.st.com/en/evaluation-tools/stm32f3discovery.html
|
||||
|
||||
|
|
@ -192,6 +229,15 @@ Crates tailored for specific development boards.
|
|||
- [`f3`](https://crates.io/crates/f3) Board Support Crate for the [STM32F3DISCOVERY] - 
|
||||
- [`blue-pill`](https://github.com/japaric/blue-pill) Board Support Crate for [Blue Pill].
|
||||
|
||||
### Texas Instruments
|
||||
|
||||
- [`stellaris-launchpad`](https://crates.io/crates/stellaris-launchpad) - For the Texas Instruments Stellaris Launchpad and Tiva-C Launchpad 
|
||||
- [`monotron`](https://github.com/thejpster/monotron) - A 1980s home-computer style application for the Texas Instruments Stellaris Launchpad. PS/2 keyboard input, text output on a bit-bashed 800x600 VGA signal. Uses [menu], [vga-framebuffer] and [pc-keyboard].
|
||||
|
||||
### Special Purpose
|
||||
|
||||
- [`betafpv-f3`](https://github.com/JoshMcguigan/betafpv-f3) - For the BetaFPV F3 drone flight controller
|
||||
|
||||
## Driver crates
|
||||
|
||||
Platform agnostic crates to interface external components. These crates use the [`embedded-hal`]
|
||||
|
|
@ -212,6 +258,11 @@ have achieved the "released" status (published on crates.io + documentation / sh
|
|||
5. [MCP3425] - I2C - 16-bit ADC - [Intro blog post][5] - 
|
||||
6. [SGP30] - I2C - Gas sensor - [Intro blog post][6] - 
|
||||
7. [HTS221] - I2C - Humidity and temperature sensor - [Intro blog post][7] - 
|
||||
8. [SSD1306] - I2C/SPI - OLED display controller - [Intro blog post][8] - 
|
||||
9. [MMA7660FC] - I2C - 3-axis accelerometer - [Intro blog post][9]
|
||||
10. [shift-register-driver] - GPIO - Shift register - [Intro blog post][10] - 
|
||||
11. [TSL256X] - I2C - Light Intensity Sensor - [Intro blog post][11] - 
|
||||
12. [EEPROM24x] - I2C - 24x series serial EEPROM driver - [Intro blog post][12] - 
|
||||
|
||||
[L3GD20]: https://crates.io/crates/l3gd20
|
||||
[LSM303DLHC]: https://crates.io/crates/lsm303dlhc
|
||||
|
|
@ -231,6 +282,21 @@ have achieved the "released" status (published on crates.io + documentation / sh
|
|||
[HTS221]: https://crates.io/crates/hts221
|
||||
[7]: https://medium.com/@pdanielgallagher/hts221-humidity-and-temperature-sensor-88056ea9e5fa
|
||||
|
||||
[SSD1306]: https://crates.io/crates/ssd1306
|
||||
[8]: https://wapl.es/electronics/rust/2018/04/30/ssd1306-driver.html
|
||||
|
||||
[MMA7660FC]: https://crates.io/crates/mma7660fc
|
||||
[9]: https://rahul-thakoor.github.io/an-i2c-rust-driver-for-mma7660fc-based-3-axis-digital-accelerometer/
|
||||
|
||||
[shift-register-driver]: https://crates.io/crates/shift-register-driver
|
||||
[10]: https://www.joshmcguigan.com/blog/shift-register-driver/
|
||||
|
||||
[TSL256X]: https://crates.io/crates/tsl256x
|
||||
[11]: https://www.joshmcguigan.com/blog/tsl256x-light-intensity-sensor-driver/
|
||||
|
||||
[EEPROM24x]: https://crates.io/crates/eeprom24x
|
||||
[12]: https://blog.eldruin.com/24x-serial-eeprom-driver-in-rust/
|
||||
|
||||
*NOTE* You may be able to find even more driver crates by searching for the [`embedded-hal-driver`]
|
||||
keyword on crates.io!
|
||||
|
||||
|
|
@ -251,21 +317,35 @@ Work in progress drivers. Help the authors make these crates awesome!
|
|||
- [BH1750] - I2C - ambient light sensor (lux meter)
|
||||
- [SHT2x] - I2C - temperature / humidity sensors
|
||||
- [INA260] - I2C - power monitor - 
|
||||
- [SSD1306] - I2C - OLED display driver
|
||||
- [ILI9341] - SPI - TFT LCD display
|
||||
- [HD44780] - Parallel port - LCD controller
|
||||
- [HD44780-driver] - GPIO - LCD controller - 
|
||||
- [MCP9808] - I2C - Temperature sensor - 
|
||||
- [MMA7660FC] - I2C - 3-axis accelerometer
|
||||
- [AXP209] - I2C - Power management unit
|
||||
- [DS3234] - SPI - Real time clock
|
||||
- [PCD8544] - SPI - 48x84 pixels matrix LCD controller
|
||||
- [PCD8544_rich] - SPI - Rich driver for 48x84 pixels matrix LCD controller - 
|
||||
- [HC-SR04] - DIO - Ultrasound sensor
|
||||
- [AFE4400] - SPI - Pulse oximeter
|
||||
- [SX1278] - SPI - Long range (LoRa) transceiver
|
||||
- [RFM69] - SPI - ISM radio transceiver
|
||||
- [LS010B7DH01] - SPI - Memory LCD
|
||||
- [MAX31855] - SPI - Thermocouple digital converter
|
||||
- [MAX31865] - SPI - RTD to Digital converter - 
|
||||
- [SHT3x] - I2C - Temperature / humidity sensors
|
||||
- [SX1509] - I2C - IO Expander / Keypad driver
|
||||
- [NRF24L01] - SPI - 2.4 GHz wireless communication
|
||||
- [embedded-nrf24l01] - SPI+GPIO - 2.4 GHz radio
|
||||
- [stm32-eth] - MCU - Ethernet
|
||||
- [bme680] - I2C - Temperature / humidity / gas / pressure sensor - 
|
||||
- [w5500] - SPI - Ethernet Module with hardwired protocols : TCP, UDP, ICMP, IPv4, ARP, IGMP, PPPoE - 
|
||||
- [OneWire] - 1wire - OneWire protocol implementation with drivers for devices such as [DS18B20](https://datasheets.maximintegrated.com/en/ds/DS18B20.pdf) - 
|
||||
- [SSD1322] - SPI - Graphical OLED display controller - 
|
||||
- [GridEYE] - I2C - Rust driver for Grid-EYE / Panasonic AMG88(33)
|
||||
- [DS1307] - I2C - Real-time clock driver - 
|
||||
- [PCF857x] - I2C - I/O expanders: PCF8574, PCF8574A, PCF8575 
|
||||
- [eink-waveshare] - SPI - driver for E-Paper Modules from Waveshare
|
||||
- [BlueNRG] - SPI - driver for BlueNRG-MS Bluetooth module. 
|
||||
|
||||
[MFRC522]: https://github.com/japaric/mfrc522
|
||||
[MPU9250]: https://github.com/japaric/mpu9250
|
||||
|
|
@ -278,12 +358,12 @@ Work in progress drivers. Help the authors make these crates awesome!
|
|||
[BH1750]: https://github.com/wose/bh1750
|
||||
[SHT2x]: https://github.com/dbrgn/sht2x-rs
|
||||
[INA260]: https://crates.io/crates/ina260
|
||||
[SSD1306]: https://github.com/jamwaffles/ssd1306
|
||||
[ILI9341]: https://github.com/yuri91/ili9341-rs
|
||||
[HD44780]: http://github.com/kunerd/clerk
|
||||
[HD44780-driver]: https://crates.io/crates/hd44780-driver
|
||||
[MCP9808]: https://crates.io/crates/mcp9808
|
||||
[MMA7660FC]: https://github.com/rahul-thakoor/mma7660fc
|
||||
[PCD8544]: https://github.com/pcein/pcd8544
|
||||
[PCD8544_rich]: https://crates.io/crates/pcd8544
|
||||
[AXP209]: https://github.com/RandomInsano/axp209-rs
|
||||
[DS3234]: https://github.com/rust-lang-nursery/embedded-wg/issues/39#issuecomment-375262785
|
||||
[HC-SR04]: https://github.com/nordmoen/hc-sr04
|
||||
|
|
@ -292,30 +372,73 @@ Work in progress drivers. Help the authors make these crates awesome!
|
|||
[RFM69]: https://github.com/lolzballs/rfm69
|
||||
[LS010B7DH01]: https://github.com/byronwasti/ls010b7dh01
|
||||
[MAX31855]: https://github.com/mbacch/max31855
|
||||
[MAX31865]: https://crates.io/crates/max31865
|
||||
[SHT3x]: https://github.com/miek/sht3x-rs
|
||||
[SX1509]: https://github.com/wez/sx1509
|
||||
[NRF24L01]: https://github.com/maikelwever/nrf24l01
|
||||
[embedded-nrf24l01]: https://crates.io/crates/embedded-nrf24l01
|
||||
[stm32-eth]: https://github.com/astro/stm32-eth
|
||||
[bme680]: https://github.com/marcelbuesing/bme680
|
||||
[w5500]: https://crates.io/crates/w5500
|
||||
[OneWire]: https://crates.io/crates/onewire
|
||||
[SSD1322]: https://crates.io/crates/ssd1322
|
||||
[GridEYE]: https://github.com/uwearzt/grideye
|
||||
[DS1307]: https://crates.io/crates/ds1307
|
||||
[PCF857x]: https://crates.io/crates/pcf857x
|
||||
[eink-waveshare]: https://crates.io/crates/eink_waveshare_rs
|
||||
[BlueNRG]: https://crates.io/crates/bluenrg
|
||||
|
||||
## no-std crates
|
||||
|
||||
[`#![no_std]` crates][no-std-category] designed to run on resource constrained devices.
|
||||
|
||||
*whoops* this list is currently empty. Want to help us write it? Leave a comment on issue [#2].
|
||||
|
||||
- [bit_field](https://crates.io/crates/bit_field): manipulating bitfields and bitarrays - 
|
||||
- [heapless](https://crates.io/crates/heapless): provides `Vec`, `String`, `LinearMap`, `RingBuffer` backed by fixed-size buffers - 
|
||||
- [intrusive-collections](https://crates.io/crates/intrusive-collections): intrusive (non-allocating) singly/doubly linked lists and red-black trees - 
|
||||
- [managed](https://crates.io/crates/managed): provides `ManagedSlice`, `ManagedMap` backed by either their std counterparts or fixed-size buffers for `#![no_std]`. - 
|
||||
- [smoltcp](https://github.com/m-labs/smoltcp): a small TCP/IP stack that runs without `alloc`
|
||||
- [nalgebra](https://crates.io/crates/nalgebra): general-purpose and low-dimensional linear algebra library - 
|
||||
- [smoltcp](https://github.com/m-labs/smoltcp): a small TCP/IP stack that runs without `alloc`
|
||||
- [embedded-graphics](https://crates.io/crates/embedded-graphics): 2D drawing library for any size display - 
|
||||
- [scroll](https://crates.io/crates/scroll): extensible and endian-aware Read/Write traits for generic containers - 
|
||||
- [vga-framebuffer]: A VGA signal generator and font renderer for VGA-less microcontrollers. Used by [Monotron](https://github.com/thejpster/monotron) to generate 48 by 36 character display using 3 SPI peripherals and a timer.
|
||||
- [menu]: A basic command-line interface library. Has nested menus and basic help functionality.
|
||||
- [pc-keyboard]: A PS/2 keyboard protocol driver. Transport (bit-banging or SPI) agnostic, but can convert Set 2 Scancodes into Unicode.
|
||||
- [console-traits](https://github.com/thejpster/console-traits): Describes a basic text console. Used by [menu] and implemented by [vga-framebuffer].
|
||||
- [register-rs](https://github.com/rust-osdev/register-rs): Unified interface for MMIO and CPU registers. Provides type-safe bitfield manipulation. - 
|
||||
|
||||
[pc-keyboard]: https://github.com/thejpster/pc-keyboard
|
||||
[vga-framebuffer]: https://github.com/thejpster/vga-framebuffer-rs
|
||||
[menu]: https://github.com/thejpster/menu
|
||||
|
||||
### WIP
|
||||
|
||||
Work in progress crates. Help the authors make these crates awesome!
|
||||
|
||||
- [light-cli](https://github.com/rudihorn/light-cli): a lightweight heapless cli interface
|
||||
- [bluetooth-hci](https://crates.io/crates/bluetooth-hci): device-independent Bluetooth Host-Controller Interface implementation.
|
||||
|
||||
[no-std-category]: https://crates.io/categories/no-std
|
||||
[#2]: https://github.com/rust-embedded/awesome-embedded-rust/issues/2
|
||||
|
||||
## Rust forks
|
||||
|
||||
### AVR
|
||||
- [AVR Rust](https://github.com/avr-rust/rust) Fork of Rust with AVR support.
|
||||
|
||||
## Firmware projects
|
||||
- [anne-key](https://github.com/ah-/anne-key): Alternate keyboard firmware for the Obins ANNE Pro
|
||||
|
||||
## License
|
||||
|
||||
This list is licensed under
|
||||
|
||||
- CC0 1.0 Universal License ([LICENSE-CC0](LICENSE-CC0) or
|
||||
https://creativecommons.org/publicdomain/zero/1.0/legalcode)
|
||||
|
||||
## Code of Conduct
|
||||
|
||||
Contribution to this crate is organized under the terms of the [Rust Code of
|
||||
Conduct][CoC], the maintainer of this crate, the [HAL team][team], promises
|
||||
to intervene to uphold that code of conduct.
|
||||
|
||||
[CoC]: CODE_OF_CONDUCT.md
|
||||
[team]: https://github.com/rust-embedded/wg#the-resources-team
|
||||
|
|
|
|||
3
bors.toml
Normal file
3
bors.toml
Normal file
|
|
@ -0,0 +1,3 @@
|
|||
delete_merged_branches = true
|
||||
required_approvals = 1
|
||||
status = ["continuous-integration/travis-ci/push"]
|
||||
Loading…
Reference in a new issue