xous-core/kernel
Sean Cross 4e17946960 kernel: riscv: ensure stack is 16-byte aligned
Make sure processes are set up such that the stack is aligned to a
16-byte boundary.

Signed-off-by: Sean Cross <sean@xobs.io>
2021-07-07 14:34:05 +08:00
..
.cargo wip 2021-06-16 16:53:40 +08:00
.vscode
bin clean up some boot process holdovers 2021-04-30 23:28:31 +08:00
src kernel: riscv: ensure stack is 16-byte aligned 2021-07-07 14:34:05 +08:00
assemble.ps1
assemble.sh suspend/resume now works to hardware 2021-04-30 19:29:36 +08:00
build.rs kernel: don't use debug_here in CI 2021-06-21 20:05:24 +08:00
Cargo.lock kernel: use gdbstub dev/0.6 2021-06-27 19:23:53 +08:00
Cargo.toml kernel: use gdbstub dev/0.6 2021-06-27 19:23:53 +08:00
link.x
README.md adding license info to README 2021-01-25 14:57:39 +01:00

Xous Kernel

This contains the core kernel for Xous. It requires a stage 1 loader in order to start up, as it assumes the system is already running in Supervisor mode.

Building

To build the kernel, you will need a riscv32 target for Rust. Possible targets include riscv32i-unknown-none-elf, riscv32imac-unknown-none-elf, or riscv32imac-unknown-xous-elf.

  1. Decide what target you want. For simple, embedded systems this could be riscv32i-unknown-none-elf, and for more complex systems with compressed instructions you could use riscv32imac-unknown-none-elf.
  2. Get Rust. Go to https://rustup.rs/ and follow its instructions.
  3. Install the proper toolchain: rustup target add ${target_arch}
  4. Build the kernel: cargo build --release --target ${target_arch}

Using

To use the kernel, you must package it up into an arguments binary with xous-tools.

Testing

TBD

Contribution Guidelines

Contributor Covenant

Please see CONTRIBUTING for details on how to make a contribution.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide its terms.

License

Copyright © 2020

This project is licensed under the Apache License 2.0 LICENSE. For accurate information, please check individual files.