libopencm3
stm32-rs
libopencm3 | stm32-rs | |
---|---|---|
11 | 8 | |
2,944 | 1,180 | |
1.1% | 2.7% | |
5.7 | 8.7 | |
17 days ago | 5 days ago | |
C | Python | |
GNU General Public License v3.0 only | 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.
libopencm3
- Open source ARM Cortex-M microcontroller library
-
Setting up a good dev environment without recreating the world
Some of the vendor IDEs have the option to generate makefiles for a project. Depending on the processor, you could also opt out to a different system. A lot of the popular cortex-m stuff is supported by libopencm3.
- Is there a command line process for ST embedded devices?
-
Looking for someone interested in designing a HAL
You can also look at examples of HALs such as - libopencm3 (Though this is Cortex only) - RIOT OS (though this requires an RTOS)
- how come there aren't any open source drivers for MCUs?
- Is there a database of peripheral implementations for different STM32 MCU parts?
-
Portable driver libraries or HAL that supports Atmel SAM targets?
Yeah by the looks of it I am going to have to expand my project do creating a portable driver interface as well. Abstracting hardware interfaces to create portable code is fairly common in embedded development. For example, libopencm3 does this and has great support for STM32 parts but very limited support for SAM parts.
-
How can i implement USB interface for an embedded flight controller to enable serial prints, parameter changes AND reading data from an SD card?
TinyUSB or Libopencm3 are probably your best options (although check they support the SAME70).
-
Which uC has the most flexible, feature-packed SPI peripherals?
that is fair. SPI isn't very portable across Arm cpu vendors because all peripherals are vendor specific, i.e. the registers will differ a lot and APIs reflect that. Finding common ground is hard unless using specifically designed portable libraries like https://github.com/libopencm3/libopencm3
- Code organization and modularity
stm32-rs
-
STM32F4 Embedded Rust at the PAC: svd2rust
Developing code at the PAC, well, requires a PAC crate for the targeted controller. For the STM32 there exists a repo for all the supported PACs. These PACs are all generated using a command line tool called svd2rust. svd2rust grabs what is called an svd file and converts it into a PAC exposing API allowing access to peripheral registers. An SVD file is an Extensible Markup Language (XML) formatted file describing the hardware features of a device, listing all the peripherals and the registers associated with them. SVD files typically are released by microcontroller manufacturers.
-
Next Rust Compiler
In real world software, 99% of code is gluing preexisting lower-level functions together. In C/C++, the unsafe is implicit and needlessly covers everything. In Rust, the unsafe is only needed for the 1%.
You can safely implement a doubly-linked list in Rust, using unsafe, and that list can offer a safe interface so that the next higher level of code does not need to use unsafe. In fact, one doubly-linked list implementation that provides a safe interface is in the Rust standard library: https://doc.rust-lang.org/std/collections/struct.LinkedList.... . Most people do not rewrite std::list in C++ either.
Much of the Linux kernel really is the same: normal C code (maybe slightly more complicate than average userspace code, and definitely more carefully reviewed, but definitely not magic), that depends on extra carefully written lower level primitives that are _much_ more complicated internally than they appear from the outside (like the memory allocator, printk, RCU, etc.).
Rust is powerful enough to have libraries for register level access to micro-controllers (e.g. https://github.com/stm32-rs/stm32-rs), that encode moderately complex access rules safely in the type system (e.g. which specific set of bits is read-only or write-only, with which particular values (with nice human-readable names, even!), in which particular states of a state machine depending on other bits), all while allowing bypassing the restrictions with a simple unsafe keyword without even giving up on the nice API.
On the C/C++ side, I've used libopencm3, MBED, CMSIS, and everyone's favorite toy, Arduino. They're, in different ways, all much more mature and complete than anything Rust has today, but nothing comes even remotely close to Rust in terms of safety and long term potential.
-
NVIDIA Security Team: “What if we just stopped…
Packages: Where would I start with e.g. running Ada on a stm32? Resources are just a bit tough to find, and there's only a single stm32 package on Alire (which was inspired by cargo). But Rust has easy to find PACs and HALs for everything in the family, plus an official guide to setting up a project, including HIL debugging and unit testing on qemu, that takes about 15 minutes.
-
Cloning a Rare ISA Card to Use a Rare CD Drive
> (I threw out all my C/C++ books about 15 years ago - oops!).
The future is here for STM32: https://github.com/stm32-rs/stm32-rs
- Is there a database of peripheral implementations for different STM32 MCU parts?
-
Writing embedded firmware using Rust
Specifically these Rust register definitions are being auto-generated using SVD files published by the chip vendors (https://www.keil.com/pack/doc/CMSIS/SVD/html/index.html). For stm32 for example there are the auto-generated register definitions: https://github.com/stm32-rs/stm32-rs and then the HAL layers on top that try to build easy to use tools on top of the registers (e.g. an SPI or USART type with write and read functions). e.g. https://github.com/stm32-rs/stm32f4xx-hal for the stm32f4xx line
-
Any frameworks in Rust for developing on SiFive / ST / NXP boards?
For STM32, check out the Peripheral Access Crates by the stm32-rs ream. For higher-level access, I wrote This HAL library for STM32. Works on most newer variants, and includes examples for specific peripherals, and simple applications.
-
CMSIS libraries
Patches: https://github.com/stm32-rs/stm32-rs/tree/master/devices
What are some alternatives?
grblHAL - This repo has moved to a new home https://github.com/grblHAL
stm32-hal - This library provides access to STM32 peripherals in Rust.
libusb_stm32 - Lightweight USB device Stack for STM32 microcontrollers
stm32f4xx-hal - A Rust embedded-hal HAL for all MCUs in the STM32 F4 family
stm32-cube-cmake-vscode - STM32, VSCode and CMake detailed tutorial
probe-run - Run embedded programs just like native ones
rt-thread - RT-Thread is an open source IoT real-time operating system (RTOS).
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.
stm32disc_midisynth1 - midi-controlled synth example for STM32F407VG Discovery board
esp32 - Peripheral access crate for the ESP32
Nodate - A light-weight framework for STM32 and other architectures written in C++.
cortex-m - Low level access to Cortex-M processors