esp32-rust-nostd-temperature-logg
rust-esp32-std-demo
| esp32-rust-nostd-temperature-logg | rust-esp32-std-demo | |
|---|---|---|
| 1 | 16 | |
| - | 776 | |
| - | - | |
| - | 6.8 | |
| - | 4 months ago | |
| Rust | ||
| - | 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.
esp32-rust-nostd-temperature-logg
-
Rust on Espressif chips – 15-07-2022
I think these esp32 + rust updates are really exciting!
I just noticed that the temperature logger project linked to in the post[0] is also using MQTT -- I've been waiting for a rust-based ESP32+wifi+MQTT solution!
[0]: https://github.com/bjoernQ/esp32-rust-nostd-temperature-logg...
rust-esp32-std-demo
-
ESP32 USB is frustrating, try JCUSB for S3 + USB + CDC + OpenOCD + Arduino IDE
This is my link: https://github.com/ivmarkov/rust-esp32-std-demo
- Rust on my ESP32 (using idf framework)
-
Embedded Rust on ESP32C3 Board, a Hands-on Quickstart Guide
A complete STD demo on ESP32C3
-
Low FPS on ESP32 LCD
I'm trying lots of Rust demos (including rust-esp32-std-demo, esp32-spooky-maze-game) for ESP32 on my M5GO kit with ili9342c controller and all of them struggle to give fullscreen (320x240) frame-rate > 5.
-
Considerations when benchmarking on mcu?
I used this demo as a guide, it uses esp-idf for rust, and allows you to use std
- Embedded Rust Development
-
Can you run rust on the new raspberry pi pico w?
rust-esp32-std-demo works quite well with WiFi, HTTPS and MQTTS. The only thing I could not make work (but I did not put much effort into it) was using async primitives. That part seems to be experimental, indeed.
-
Rust on Espressif chips – 15-07-2022
FWIW I've very recently gotten https://github.com/ivmarkov/rust-esp32-std-demo (which is a pretty comprehensive demo) running on a TinyPICO (w/ESP32) and am looking forward to building out my own projects next.
-
Is this normal bindgen/embuild behavior?
I'm using this template project to get started with the esp32, though I've started fresh in a new main function. Every time I build the project -even if I only add a blank line to main - it seems to re-compile bindgen and embuild, and regenerate the bindings for a variety of packages that have C components. I haven't made any changes to these though and the process takes a full 90 seconds. In addition nothing in the bindings that are getting generated shows up in intellisense in vscode. Any help appreciated.
-
Starting work using the esp32 in rust - problems and solutions. (devlog, i guess?)
This worked fairly well for me. I assume that's where the book takes you, bit I've missed if you said if you're trying to use std or no_std. https://github.com/ivmarkov/rust-esp32-std-demo
What are some alternatives?
embassy - Modern embedded framework, using Rust and async.
smol - A small and fast async runtime for Rust
esp32-rust-nostd-temperature-logger - MQTT temperature logger running on ESP32 in Rust (no-std / no RTOS)
esp-idf-sys - Bindings for ESP-IDF (Espressif's IoT Development Framework)
ili9341-rs - A WIP, no_std, generic driver for the ILI9341 (and ILI9340C) TFT LCD display
getrandom - A small cross-platform library to securely get random data (entropy)
espflash - Serial flasher utility for Espressif SoCs and modules based on esptool.py
polling - Portable interface to epoll, kqueue, event ports, and wepoll
esp-idf-template - A "Hello, world!" template of a Rust binary crate for the ESP-IDF framework.
socket2 - Advanced configuration options for sockets.
toml-rs - A TOML encoding/decoding library for Rust