From dc763951513535d5dc54be6d5a24e2a093504b03 Mon Sep 17 00:00:00 2001 From: follower Date: Wed, 27 Oct 2021 18:52:03 +1300 Subject: [PATCH] Typo fix: "-unkwon-" -> "-unknown-" --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ea86870bc..c8ffb95e9 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ from source. It consists of the following projects: ## Dependencies -- Xous requires its own Rust target, `riscv32imac-unkwon-xous-elf`. If you run `cargo xtask` from the command line, you should be prompted to install the target automatically if it does not already exist. +- Xous requires its own Rust target, `riscv32imac-unknown-xous-elf`. If you run `cargo xtask` from the command line, you should be prompted to install the target automatically if it does not already exist. - If you plan on doing USB firmware updates, you'll need `progressbar2` (updates) and `pyusb` (updates). Note that `pyusb` has name space conflicts with similarly named packages, so if updates aren't working you may need to create a `venv` or uninstall conflicting packages. - If you are doing development on the digital signatures with the Python helper scripts, you will need: `pycryptodome` (signing - PEM read), `cryptography` (signing - x509 read), `pynacl` (signing - ed25519 signatures) (most users won't need this). @@ -89,4 +89,4 @@ cargo xtask hw-image precursors/soc.svd The resulting images are in your target directory (typically `target/riscv32imac-unknown-xous-elf/release/`) with the names `xous.img` (for the kernel) and `loader.bin` (for its bootloader). The corresponding gateware is in `precursors/soc_csr.bin`. These can be written to your -device by following the [update guide](https://github.com/betrusted-io/betrusted-wiki/wiki/Updating-Your-Device). \ No newline at end of file +device by following the [update guide](https://github.com/betrusted-io/betrusted-wiki/wiki/Updating-Your-Device).