va108xx-rs/va108xx-hal
Robin Mueller ef1c854cac
Some checks are pending
Rust/va108xx-rs/pipeline/head Build started...
fix READMEs
2024-06-16 19:08:51 +02:00
..
.cargo New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
.github New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
automation New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
src Set of fixes 2024-06-16 18:56:45 +02:00
tests/DueSerialTest New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
.gitignore New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
Cargo.toml Set of fixes 2024-06-16 18:56:45 +02:00
CHANGELOG.md prepare releases for HAL, BSP, PAC 2024-06-16 19:03:46 +02:00
jlink.gdb New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
LICENSE-APACHE New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
memory.x New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
NOTICE New VA108xx Rust workspace structure + dependency updates 2024-06-16 16:16:45 +02:00
README.md fix READMEs 2024-06-16 19:08:51 +02:00

Crates.io docs.rs

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.

Building

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:

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 blinky.rs file to the src/main.rs file in your binary crate

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

     [dependencies]
     cortex-m = "<Compatible Version>"
     cortex-m-rt = "<Compatible Version>"
     panic-halt = "<Compatible Version>"
     embedded-hal = "<Compatible Version>"
    
     [dependencies.va108xx-hal]
     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 in primary README.