Skip to main content

Milestone 1

Milestone 1 Status​

This milestone was completed December 16, 2025.

In this milestone, an initial kickoff meeting with the RISE Security WG members was held. Introductions of all key stakeholders were made, and a lengthly technical discussion about the project was held. RISCstar created or updated GIT repositories in riscv-optee for all key software used in this project, and produced this documentation which desribes how we build the software, and instructions on how to use the software to test our changes to OpenSBI, along with a framework for progress notes on each milestone.

Milestone Description​

Milestone 1 is about baseline setup and project kickoff. The initial kickoff meeting between all project participants will be held held. RISCstar will set up and document the development environment. RISCstar will also set up GIT repositories for QEMU, OpenSBI, the Linux kernel (OpenSBI domain A) and a simple bare metal application (OpenSBI domain B).

Deliverables:​

  • Development environment setup
    • GNU cross toolchains
    • Device tree compiler
    • Python3
    • Doxygen, graphviz
  • GIT repository for OpenSBI.
  • GIT repository for Linux kernel with MPXY and RPMI support.
  • GIT repository for bare metal application.
  • GIT repository for QEMU with WorldGuard support.
  • Instructions and builds of the above source code to enable the trialing of code during later stages of development.
  • Ability to install and test OpenSBI and Linux on the target platforms and target domains.
  • Documentation on building the above software and setting it up for testing OpenSBI.

Git Maintenance Strategy​

RISCstar has an organization on GitHub: https://github.com/riscstar We maintain forks of existing public repositories–including the Linux kernel. Repositories kept here may include private GitHub forks of other upstream projects we’re working with as well. This space will primarily be used to host snapshots of code being developed.

Whenever we need to do development on an open source component, we maintain a git repository for that component. A “component” in this sense is anything that has an upstream git repository, such as Linux, OpenSBI, OP-TEE, and so on. We will have a branching strategy that makes it clear what a given branch represents, based on its name. Branches will be updated regularly, with topic branches derived from very recently published upstream code.

Public Git repositories for this project will be hosted by RISE, in the riscv-optee GitLab group. Branches published in the RISE repositories are intended to be “released”, in that they will be stable and are meant to be shared. They are expected to function correctly when used by others trying to reproduce our work. Topic and integration branches in these repositories will be named with a prefix “rp016”.