Google Git
Sign in
opensecura / 3p / tock / libtock-rs / 80f2a1f56f364e58b9cf6e1d110587a42e8993eb
commit80f2a1f56f364e58b9cf6e1d110587a42e8993eb[log] [tgz]
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>Fri Feb 14 14:18:19 2020 +0000
committerGitHub <noreply@github.com>Fri Feb 14 14:18:19 2020 +0000
treeebbff68be88ceefafa0921a6153a483c3c0d4123
parente93f701f2a9c2be577d0e0f0b7c6ce2d84aa11d8 [diff]
parentebfd0b8fc14fcba22e4e1fadb12ffec5d42642e5 [diff]
Merge #137

137: Enable support for multiple boards and architectures r=Woyten a=Woyten

This PR is a starting point to support multiple boards and architectures. The design is as follows:

- Before the code is compiled a `build.rs` script selects an appropriate linker script. This selection is based on whether the environment variable `PLATFORM` is set or the file `platform` is present.
- When using `cargo run` on an embedded target architecture, the script `flash.sh` is executed instead of directly running the binary. `flash.sh` is a replacement for `run_example` and contains a new but incomplete dispatching section which determines the appropriate `tockloader_flags` for the currently selected platform.
- Aliases like `cargo rtv7em` are shorthand for `run --release --target=thumbv7em-none-eabi --example`

Co-authored-by: Woyten <woyten.tielesch@online.de>
tree: ebbff68be88ceefafa0921a6153a483c3c0d4123
  1. .cargo/
  2. .vscode/
  3. async-support/
  4. codegen/
  5. doc/
  6. examples/
  7. src/
  8. .gitignore
  9. .travis.yml
  10. bors.toml
  11. build.rs
  12. build_examples.sh
  13. Cargo.toml
  14. CHANGELOG.md
  15. CONTRIBUTING.md
  16. flash.sh
  17. layout_generic.ld
  18. layout_hail.ld
  19. layout_nrf52.ld
  20. layout_nrf52840.ld
  21. layout_opentitan.ld
  22. layout_riscv32.ld
  23. LICENSE-APACHE
  24. LICENSE-MIT
  25. README.md
  26. run_all_checks.sh
  27. rust-toolchain
  28. rustfmt.toml
README.md

Build Status

libtock-rs

Rust userland library for Tock (WIP)

Tested with tock Release 1.4.1.

The library works in principle on most boards, but there is currently the showstopper bug #28 that prevents the generation of relocatable code. This means that all applications must be installed at the flash address they are compiled with, which usually means that they must be compiled especially for your board and that there can only be one application written in rust at a time and it must be installed as the first application on the board, unless you want to play games with linker scripts. There are some *_layout.ld files provided that allow to run the examples on common boards. Due to MPU region alignment issues they may not work for applications that use a lot of RAM, in that case you may have to change the SRAM start address to fit your application.

Getting Started

This project is nascent and still under heavy development, but first steps:

  1. Ensure you have rustup installed.

  2. Clone the repository:

    git clone https://github.com/tock/libtock-rs
cd libtock-rs

  3. Install elf2tab:

    cargo install -f elf2tab --version 0.4.0

  4. Add dependencies for cross-compilation. Currently, only few platforms have been configured, e.g.:

    rustup target add thumbv7em-none-eabi # For an nRF52 DK board

    rustup target add riscv32imc-unknown-none-elf # For an OpenTitan board

  5. Use cargo r<arch> to compile and run an example app. The full command is platform dependent and looks as follows for the blink example:

    PLATFORM=nrf52 cargo rthumbv7em blink # For an nRF52 DK board

    PLATFORM=opentitan cargo rriscv32imc blink # For an OpenTitan board

    For an unknown platform, you may have to create your own memory layout definition. Place the layout definition file at layout_<platform>.ld and do not forget to enhance the tockloader_flags dispatching section in flash.sh. You are welcome to create a PR, s.t. the number of supported platforms grows.

Using libtock-rs

The easiest way to start using libtock-rs is adding an example to the examples folder. The boiler plate code you would write is

#![no_std]

use libtock::result::TockResult;

#[libtock::main]
async fn main() -> TockResult<()> {
  // Your code
}

If you want to use heap based allocation you will have to add

extern crate alloc;

to the preamble.

To run on the code on your board you can use

PLATFORM=<platform> cargo r<arch> <your_app>

This script does the following steps for you:

  • cross-compile your program
  • create a TAB (tock application bundle)
  • if you have a J-Link compatible board connected: flash this TAB to your board (using tockloader)

Instead of specifying an environment variable each time you can permanently configure your platform by writing its name into a file named platform, e.g.

echo nrf52 > platform

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

The contribution guidelines can be found here: contribution guidelines