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
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.