esp-hal
esp-backtrace
| esp-hal | esp-backtrace | |
|---|---|---|
| 3 | 1 | |
| 565 | 27 | |
| 3.7% | - | |
| 9.8 | 6.7 | |
| 7 days ago | about 1 month ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
esp-hal
-
Rust on Espressif chips – 29-09-2023
In the esp-hal, they appear to offer both sync and async I2C implementations, depending on what works best for an application. Since the async implementation is gated by a feature, it may not show up in the docs you linked.
Async implementation: https://github.com/esp-rs/esp-hal/blob/main/esp-hal-common/s...
You can also see the async feature mentioned here: https://docs.rs/crate/esp32s2-hal/latest/features
-
The Embedded Rust ESP Development Ecosystem
Going another level up the chain, we then have the hardware abstraction layer (HAL) crate. HAL crates are supposed to offer more portability and user-friendly API for a particular processor. For ESP devices the different hals are captured in the esp-hal repository. This occurs by implementing some common traits defined in what is referred to as the embedded-hal. Additionally, the device HAL attempts to incorporate mechanisms, or wrappers around lower-level functions, that are part of the Rust safety model.
-
How to write HALs and get into microcontroller programming
There is https://docs.rust-embedded.org/book/design-patterns/hal/index.html but I wonder what OP is missing in https://github.com/esp-rs/esp-hal
esp-backtrace
-
The Embedded Rust ESP Development Ecosystem
Among these several abstractions, we can program a microcontroller device at any level we like. Additionally, we can develop code with a mix of low-level and high-level abstractions. Obviously, to make code more portable it's better to stick to higher-level abstractions. Also in addition to the above, there exists other crates supporting other functions in no-std development. These include wifi services in the esp-wifi repository, heap allocators in the esp-alloc repository, logging features in the esp-println repository, exception handlers in the esp-backtrace repository, and finally embedded storage traits in the esp-storage repository.
What are some alternatives?
esp32-phantom - ESP32 Rust-based WiFi and BLE sandbox
esp-pacs - Peripheral Access Crates for Espressif SoCs and modules
linux-embedded-hal - Implementation of the `embedded-hal` traits for Linux devices
esp-alloc - A simple `no_std` heap allocator for RISC-V and Xtensa processors from Espressif
esp-idf-hal - embedded-hal implementation for Rust on ESP32 and ESP-IDF
esp-println - Provides print! and println! implementations various Espressif devices
esp-storage - implementation of embedded-storage traits to access unencrypted ESP32 flash
esp-wifi - A WiFi, Bluetooth and ESP-NOW driver for use with Espressif chips and bare-metal Rust