Robin Mueller
006a3e022c
# This is the 1st commit message: init commit # This is the commit message #2: smaller fixes for config files # This is the commit message #3: update VA416xx flash script file # This is the commit message #4: completed UART HAL, added first example # This is the commit message #5: UART, WDT and CLKGEN # This is the commit message #6: smaller workspace file tweaks # This is the commit message #7: SPI peripheral implementation # This is the commit message #8: update VS Code files # This is the commit message #9: update JLink files # This is the commit message #10: update VS Code files # This is the commit message #11: timer, PWM and I2C module # This is the commit message #12: Add CI # This is the commit message #13: update docs # This is the commit message #14: updates for documentation # This is the commit message #15: update CI as well # This is the commit message #16: add docs for setting up binary crate # This is the commit message #17: add additional memory section
108 lines
3.7 KiB
Markdown
108 lines
3.7 KiB
Markdown
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`](https://egit.irs.uni-stuttgart.de/rust/va416xx-rs/src/branch/main/va416xx)
|
|
PAC crate containing basic low-level register definition
|
|
- The [`va416xx-hal`](https://egit.irs.uni-stuttgart.de/rust/va416xx-rs/src/branch/main/va416xx-hal)
|
|
HAL crate containing higher-level abstractions on top of the PAC register crate.
|
|
- The [`vorago-peb1`](https://egit.irs.uni-stuttgart.de/rust/va416xx-rs/src/branch/main/vorago-peb1)
|
|
BSP crate containing support for the PEB1 development board.
|
|
|
|
It also contains the following helper crates:
|
|
|
|
- The `examples` crates contains various example applications for the HAL and the PAC.
|
|
|
|
## Using the `.cargo/config.toml` file
|
|
|
|
Use the following command to have a starting `config.toml` file
|
|
|
|
```sh
|
|
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:
|
|
|
|
```sh
|
|
cp -rT vscode .vscode
|
|
```
|
|
|
|
You can then adapt the files in `.vscode` to your needs.
|
|
|
|
## Flashing, running and debugging the software
|
|
|
|
You can use CLI or VS Code for flashing, running and debugging. In any case, take
|
|
care of installing the pre-requisites first.
|
|
|
|
### Pre-Requisites
|
|
|
|
1. [SEGGER J-Link tools](https://www.segger.com/downloads/jlink/) installed
|
|
2. [gdb-multiarch](https://packages.debian.org/sid/gdb-multiarch) or similar
|
|
cross-architecture debugger installed. All commands here assume `gdb-multiarch`.
|
|
|
|
### Using CLI
|
|
|
|
You can build the blinky example application with the following command
|
|
|
|
```sh
|
|
cargo build --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)
|
|
|
|
```sh
|
|
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
|
|
|
|
```sh
|
|
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:
|
|
|
|
```toml
|
|
[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 --example blinky` to flash the blinky
|
|
example.
|
|
|
|
### Using VS Code
|
|
|
|
Assuming a working debug connection to your VA108xx board, you can debug using VS Code with
|
|
the [`Cortex-Debug` plugin](https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug).
|
|
|
|
Some sample configuration files for VS code were provided and can be used by running
|
|
`cp -rT vscode .vscode` like specified above. After that, you can use `Run and Debug`
|
|
to automatically rebuild and flash your application.
|
|
|
|
If you would like to use a custom GDB application, you can specify the gdb binary in the following
|
|
configuration variables in your `settings.json`:
|
|
|
|
- `"cortex-debug.gdbPath"`
|
|
- `"cortex-debug.gdbPath.linux"`
|
|
- `"cortex-debug.gdbPath.windows"`
|
|
- `"cortex-debug.gdbPath.osx"`
|
|
|
|
The provided VS Code configurations also provide an integrated RTT logger, which you can access
|
|
via the terminal at `RTT Ch:0 console`.
|