Rust Hardware Abstraction Layer (HAL) crate for the Vorago VA108xx family of MCUs
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Robin Müller 147c57defb
run cargo fmt
4 weeks ago
.cargo added utility files 7 months ago
.github try without use-cross in CI 6 months ago
automation EGit integration 6 months ago
examples some minor improvements 5 months ago
src run cargo fmt 4 weeks ago
test/DueSerialTest added Arduino Due test script 5 months ago
.gitignore ignoring Cargo.lock now 7 months ago small changelog update 5 months ago
Cargo.toml update changelog and manifest 5 months ago
LICENSE-APACHE added license files 7 months ago
NOTICE EGit integration 6 months ago update link 6 months ago
jlink.gdb added utility files 7 months ago
memory.x added utility files 7 months ago ci

HAL for the Vorago VA108xx MCU family

This repository contains the Hardware Abstraction Layer (HAL), which is an additional hardware abstraction on top of the peripheral access API.

It is the result of reading the datasheet for the device and encoding a type-safe layer over the raw PAC. This crate also implements traits specified by the embedded-hal project, making it compatible with various drivers in the embedded rust ecosystem.

In contrats to other HAL implementations, there is only one chip variant available here so there is no need to pass the chip variant as a feature.

Supported Boards

The first way to use this HAL will probably be with the REB1 development board. The BSP provided for this board also contains instructions how to flash the board.

Crate Version


Building an application requires the thumbv6m-none-eabi cross-compiler toolchain. If you have not installed it yet, you can do so with

rustup target add thumbv6m-none-eabi

After that, you can use cargo build to build the development version of the crate.

If you have not done this yet, it is recommended to read some of the excellent resources available to learn Rust:


Some examples, which are not specific to a particular board were provided as well. You can build the timer example with

cargo build --example timer-ticks

Setting up your own binary crate

If you have a custom board, you might be interested in setting up a new binary crate for your project. These steps aim to provide a complete list to get a binary crate working to flash your custom board.

The hello world of embedded development is usually to blinky a LED. This example is contained within the examples folder.

  1. Set up your Rust cross-compiler if you have not done so yet. See more in the build chapter

  2. Create a new binary crate with cargo init

  3. To ensure that cargo build cross-compiles, it is recommended to create a cargo/config.toml file. A sample .cargo/config.toml file is provided in this repository as well

  4. Copy the memory.x file into your project. This file contains information required by the linker.

  5. Copy the file to the src/ file in your binary crate

  6. You need to add some dependencies to your Cargo.toml file

     cortex-m = "<Compatible Version>"
     cortex-m-rt = "<Compatible Version>"
     panic-halt = "<Compatible Version>"
     embedded-hal = "<Compatible Version>"
     version = "<Most Recent Version>"
     features = ["rt"]
  7. Build the application with cargo build

  8. Flashing the board might work differently for different boards and there is usually more than one way. You can find example instructions for the REB1 development board here.