You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2520: tools/board-runner: Improve documentation and OpenTitan support r=bradjc a=alistair23
### Pull Request Overview
Improvements to the OT board runner.
### Testing Strategy
Using board runner to run Tock2.0 tests on OT.
### TODO or Help Wanted
### Documentation Updated
- [X] Updated the relevant files in `/docs`, or no updates are required.
### Formatting
- [X] Ran `make prepush`.
Co-authored-by: Alistair Francis <[email protected]>
This is a Rust program that uses rexpect to test Tock on different boards. The goal of this is to automated the testing, currently it still requires manual steps though.
3
+
This is a Rust program that uses rexpect to test Tock on different boards.
4
+
The goal of this is to automated the testing, currently it still requires
5
+
manual steps though.
4
6
5
7
## Supported Boards
6
8
7
9
### OpenTitan
8
10
9
11
This can be used to perform Tock release testing on the OpenTitan board.
10
12
11
-
This assumes that the OpenTitan serial console is available on the machines first serial port (`/dev/ttyUSB0` for Unix systems). The tests can be run from the top level of the Tock direcotry with the following command
13
+
This assumes that the OpenTitan serial console is available on the machines
14
+
first serial port (`/dev/ttyUSB0` for Unix systems). The tests can be run from
15
+
the top level of the Tock direcotry with the following command
12
16
13
17
```shell
14
-
OPENTITAN_TREE=<opentitan_repo> LIBTOCK_C_TREE=<libtock_c_repo> TARGET=earlgrey-nexysvideo make board-release-test
18
+
OPENTITAN_TREE=<opentitan_repo> LIBTOCK_C_TREE=<libtock_c_repo> TARGET=earlgrey_nexysvideo make board-release-test
15
19
```
16
20
17
-
Where `opentitan_repo` and `libtock_c_repo` point to the top level directory of the corresponding repos. You will need to make sure that the OpenTitan spiflash command has been built in the OpenTitan repo and that the c apps have been built in the libtock-c repo.
21
+
Where `opentitan_repo` and `libtock_c_repo` point to the top level directory
22
+
of the corresponding repos. You will need to make sure that the OpenTitan
23
+
spiflash command has been built in the OpenTitan repo and that the c apps have
24
+
been built in the libtock-c repo.
18
25
19
26
### Redboard Artemis Nano
20
27
21
-
This can be used to perform Tock release testing on the Sparkfun Redboard Artemis Nano board.
28
+
This can be used to perform Tock release testing on the Sparkfun Redboard
29
+
Artemis Nano board.
22
30
23
-
This assumes that the ARtemis Nano serial console is available on the machines first serial port (`/dev/ttyUSB0` for Unix systems). The tests can be run from the top level of the Tock directory with the following command
31
+
This assumes that the ARtemis Nano serial console is available on the machines
32
+
first serial port (`/dev/ttyUSB0` for Unix systems). The tests can be run from
33
+
the top level of the Tock directory with the following command
24
34
25
35
```shell
26
36
LIBTOCK_C_TREE=<libtock_c_repo> TARGET=artemis_nano make board-release-test
27
37
```
28
38
29
-
Where `libtock_c_repo` points to the top level directory of the corresponding libtock-c repo.
39
+
Where `libtock_c_repo` points to the top level directory of the corresponding
0 commit comments