Rust support for the VA416xx family of MCUs
Go to file
2024-06-12 11:45:30 +02:00
.cargo update def-config.toml 2024-06-11 21:14:49 +02:00
jlink nothing but issues 2024-06-11 23:26:32 +02:00
scripts nothing but issues 2024-06-11 23:26:32 +02:00
va416xx GPIO example works 2024-06-12 11:29:12 +02:00
va416xx-hal GPIO example works 2024-06-12 11:29:12 +02:00
vorago-peb1 GPIO example works 2024-06-12 11:29:12 +02:00
vscode README 2024-06-12 11:45:30 +02:00
.gitignore gpio init 2024-06-12 10:12:11 +02:00
.gitmodules add all submodules as regular code 2024-06-11 13:48:42 +02:00
Cargo.toml fast blinky 2024-06-11 20:24:24 +02:00
jlink-gdb.sh finally its working with JLinkGDBServer 2021-12-09 21:00:22 +01:00
LICENSE-APACHE init commit 2021-12-07 00:31:51 +01:00
memory.x stll some issues 2021-12-07 11:56:18 +01:00
NOTICE init commit 2021-12-07 00:31:51 +01:00
README.md README 2024-06-12 11:45:30 +02:00

Vorago VA416xx Rust Support

This crate collection provided support to write Rust applications for the VA416XX family of devices.

List of crates

This workspace contains the following crates:

  • The va416xx PAC crate containing basic low-level register definition
  • The va416xx-hal HAL crate containing higher-level abstractions on top of the PAC register crate.
  • The vorago-peb1 BSP crate containing support for the PEB1 development board.

Using the .cargo/config.toml file

Use the following command to have a starting config.toml file

cp .cargo/def-config.toml .cargo/config.toml

You then can adapt the config.toml to your needs. For example, you can configure runners to conveniently flash with cargo run.

Using the sample VS Code files

Use the following command to have a starting configuration for VS Code:

cp vscode .vscode -r

You can then adapt the files in .vscode to your needs.

Flashing, running and debugging with the command line

Prerequisites

  1. SEGGER J-Link tools installed
  2. gdb-multiarch or similar cross-architecture debugger installed. All commands here assume gdb-multiarch.

Flashing and debugging the blinky application

You can build the blinky example application with the following command

cargo build -p va416xx-hal --example blinky

Start the GDB server first. The server needs to be started with a certain configuration and with a JLink script to disable ROM protection. For example, on Debian based system the following command can be used to do this (this command is also run when running the jlink-gdb.sh script)

JLinkGDBServer -select USB -device Cortex-M4 -endian little -if SWD -speed 2000 \
  -LocalhostOnly -vd -jlinkscriptfile ./jlink/JLinkSettings.JLinkScript

After this, you can flash and debug the application with the following command

gdb-mutliarch -q -x jlink/jlink.gdb target/thumbv7em-none-eabihf/debug/examples/blinky

Please note that you can automate all steps except starting the GDB server by using a cargo runner configuration, for example with the following lines in your .cargo/config.toml file:

[target.'cfg(all(target_arch = "arm", target_os = "none"))']
runner = "gdb-multiarch -q -x jlink/jlink.gdb"

After that, you can simply use cargo run -p va416xx-hal --example blinky to flash the blinky example.

Flashing, running and debugging with VS Code

TODO