https://github.com/newam/ambientsensor-rs
A rust re-implementation of an old embedded C project.
https://github.com/newam/ambientsensor-rs
Last synced: 3 months ago
JSON representation
A rust re-implementation of an old embedded C project.
- Host: GitHub
- URL: https://github.com/newam/ambientsensor-rs
- Owner: newAM
- License: mit
- Created: 2021-01-04T04:17:42.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2024-06-10T00:27:06.000Z (11 months ago)
- Last Synced: 2025-01-11T04:42:28.013Z (4 months ago)
- Language: Rust
- Homepage:
- Size: 187 KB
- Stars: 20
- Watchers: 4
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ambientsensor-rs
This is a rust re-implementation of an embedded C project I did a while ago: [AmbientSensor].
Schematics, photos, ect. will be in that repository, this repository is just for the rust firmware.
## Status
This is still a work in progress.
1. The OPT3002 luminosity sensor is not implemented.
2. The panic handler needs to get hooked up to the EEPROM to store error logs then reset.
## Purpose
Co-workers kept hyping up this new rust language, and I wanted to see if the hype was warranted.
On paper rust seems amazing, but the only way to really evaluate a language is to use it. I specifically wanted to compare embedded rust to embedded C, and [AmbientSensor] was simply the last embedded project I completed in C.
Turns out, the hype was warranted.
There is not a lot of commentary I can offer about embedded rust that has not already been said. The concepts rust introduces (safety, ownership, lifetimes) make developing robust code simple. The language is new and still has a small (but rapidly growing) ecosystem for embedded development. From my experience a lot of embedded development is still C simply because nothing else offers a compelling reason to switch (except C++ depending on who you ask). The features rust brings to the table are incredibly compelling for embedded development, and I think rust has a bright future in this industry.
## Notable crates used
* [rtic](https://rtic.rs/0.5/book/en/) - RTOS
* [rtt_target](https://docs.rs/rtt-target/0.3.0/rtt_target/) - Probe based logging
* [cargo-embed](https://crates.io/crates/cargo-embed) - build and run your code with one command
* [embedded-hal](https://github.com/rust-embedded/embedded-hal) - abstractions for embedded hardware
## Crates Developed
* [bme280-multibus](https://github.com/newAM/bme280-multibus) - Bosch BME280 driver
* [eeprom25aa02e48](https://github.com/newAM/eeprom25aa02e48-rs) - EEPROM driver, my first rust crate
* [w5500-dhcp](https://github.com/newAM/w5500-rs) - W5500 DHCP client
* [w5500-hl](https://github.com/newAM/w5500-rs) - Higher level W5500 Ethernet chip driver
* [w5500-ll](https://github.com/newAM/w5500-rs) - Low level W5500 Ethernet chip driver
* [w5500-mqtt](https://github.com/newAM/w5500-rs) - W5500 MQTT client
## Building
You will need [rustup] and the `thumbv6m-none-eabi` target.
```bash
rustup target add thumbv6m-none-eabi
```
After you have that target available you can build, the default target is already set in `.cargo/config.toml`.
```bash
cargo build
```
[rustup]: https://rustup.rs/
[AmbientSensor]: https://github.com/newam/ambientsensor