svd2rust

Can the developer or any Rust users comment on using Sonatino with the Rust ESP32-S3 toolchain? Is there an SVD file defining the Sonatino's specialized peripherals so one can use rust2svd to create a Peripheral Access Crate (PAC) specific to the Sonatino? I'm interested in the other ergonomic Rust HAL representations as well. https://github.com/esp-rs/esp-pacs/tree/main/esp32s3 https://github.com/rust-embedded/svd2rust https://github.com/rust-embedded/awesome-embedded-rust?tab=r...

It may be true that manufacturers are ignoring Rust but that certainly does not stop or hinder me. Tools like svd2rust mean I only need to rely on the accuracy of their svd files (industry standard register maps) - see https://github.com/rust-embedded/svd2rust Additionally, I use vanilla VS Code and rust analyser so no need to use manufacturer supplied lock-in IDEs. There are many compiler targets to choose from for cross compilation and tools like probe-run to flash chips. One major issue is lack of manufacturer provided code examples written in Rust. For that I rely on the Rust community. A typical example being nrf-hal for Nordic Bluetooth chips.

SVD is this machinine readable description, and is available for most ARM micros, as it is needed for the peripheral register view in debuggers. svd2rust [1] is an project that generates a (very low level) Rust API for a specific micro from this file. Generally the file generated from this is known as the header files (as it is just C headers to access the registers directly) and the HAL is an abstraction layer on top, and is actually written manually by the microcontroller designer as it contains higher level functions (e.g. a function to calculate the clock settings to get a specific UART baudrate). The STDLib is often supplied by the compiler vendor instead, or is an open source project like picolibc [2] [1] https://github.com/rust-embedded/svd2rust [2] https://github.com/picolibc/picolibc

Out of curiosity, how is the embedded story (for both bare-metal and RTOS) in Rust nowadays? I took a look early last year, and I remember feeling that the ecosystem still wasn't as mature as I liked. There's svd2rust [0] and dslite2svd [1], which is basically "bindgen for hardware". Please do correct me if I'm wrong, but from what I understood [2], most SVD files leave out a lot of information so a lot of what svd2rust generates is unsafe. Seems like the only way around that is to patch the SVD files. Is this still the case? In addition, what about compiling with no stdlib? And how does that interop with existing Crates (ie. do new "embedded-specific" Crates need to be created?) Super excited to see Rust gain traction! I'll definitely take another shot in my free time and see how the ecosystem has matured. [0] https://github.com/japaric/

Also enjoying https://github.com/japaric/svd2rust - Generates simple uniform register mappings for various cortex-m and msp430 micros.