| commit | 5a533c0d44792f20289ca24e5d4d24bca6762e77 | [log] [tgz] |
|---|---|---|
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | Fri Jun 19 19:05:30 2020 +0000 |
| committer | GitHub <noreply@github.com> | Fri Jun 19 19:05:30 2020 +0000 |
| tree | f88a9b80c7c109e29646381d7ebd7addacef1f9d | |
| parent | a768ba1666fbd02fb55678de12ec62f9a6d95aeb [diff] | |
| parent | 2c24021e9048f0e11b43e6b3495f4d8b8b8c96b8 [diff] |
Merge #201 201: Amend memory layout for nordic boards to match tock 1.5 release r=jrvanwhy a=torfmaster # Contents In this PR I amend the memory layout for the nrf52dk to match the kernel size of the tock 1.5 release. This breaks compatibility with previous releases and should be merged alongside with #195 . I also tested the nrf52840 board which is already working with the 1.5 kernel without any changes. # Testing I ran the test suites on both development boards. However, I did no thorough test of compatibility of `libtock-rs` with the new kernel release. Co-authored-by: torfmaster <briefe@kebes.de>
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 boards/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.
This project is nascent and still under heavy development, but first steps:
Ensure you have rustup installed.
Clone the repository:
git clone --recursive https://github.com/tock/libtock-rs cd libtock-rs
Install the dependencies:
make setup
Use make to build examples
make nrf52 # Builds all examples for the nrf52 platform
make opentitan # Builds all examples for the OpenTitan platform
make opentitan FEATURES=alloc # Builds all examples for the OpenTitan platform, with alloc feature enabled
make flash-hail EXAMPLE=blink # Flash the example 'blink' program to the hail platform
For an unknown platform, you may have to create your own memory layout definition. Place the layout definition file at boards/layout_<platform>.ld and do not forget to enhance the tockloader_flags dispatching section in tools/flash.sh. You are welcome to create a PR, s.t. the number of supported platforms grows.
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 and store your example in the examples-alloc folder.
To build the examples for your board you can use
make <platform> [FEATURES=alloc]
An example can be flashed to your board after the build process by running:
make flash-<platform> EXAMPLE=<example>
This script does the following steps for you:
libtock-rs is licensed under either of
at your option.
Submodules have their own licenses.
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