rust/va416xx-rs
6
0
Fork 0
Code Issues Pull Requests Projects Releases 5 Wiki Activity
b1f63b64ce
va416xx-rs/vorago-peb1
History
Robin Mueller 22cc40c095
Some checks are pending
Rust/va416xx-rs/pipeline/head Build started...
Details
prepare release for BSP
2024-10-01 10:43:06 +02:00
..
jlink Init Commit 2024-06-25 20:01:21 +02:00
src Init Commit 2024-06-25 20:01:21 +02:00
.gitignore Init Commit 2024-06-25 20:01:21 +02:00
Cargo.toml prepare release for BSP 2024-10-01 10:43:06 +02:00
CHANGELOG.md prepare release for BSP 2024-10-01 10:43:06 +02:00
jlink-gdb.sh Init Commit 2024-06-25 20:01:21 +02:00
LICENSE-APACHE Init Commit 2024-06-25 20:01:21 +02:00
memory.x Init Commit 2024-06-25 20:01:21 +02:00
NOTICE Init Commit 2024-06-25 20:01:21 +02:00
README.md Init Commit 2024-06-25 20:01:21 +02:00

README.md

Rust BSP for the Vorago 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.

Notes on board revisions

On RevA, issuing the monitor reset command in the GDB application is problematic and will prevent the flashed binary from working properly. On board revision B, this was not an issue. For that reason, two different *.gdb files were provided in the jlink folder for each board revision. If you are not using these files, make sure to correctly configure your flash tools depending on which tool or board your are using.