v2025-07-07 or later
This manual helps you set up your own design repository that can use RVX.
This method creates a new design repository by copying an existing one.
Unlike a Git fork:
It copies only the latest commit, so it uses less space.
It has no connection to the original repository.
It remains usable even if the original repository is deleted.
All results produced using RVX are subject to the following conditions:
They must not be used beyond the predefined purpose and scope specified in advance for a particular class or research project.
They must not be distributed to third parties other than the designated users or organizations.
They are free for non-commercial research use, provided that the paper is cited. All other uses require prior approval and a technology transfer agreement.
Manuals are available online - riscvexpress.github.io
Any part starting with # should be replaced or modified according to your environment.
On Linux, use the bash shell for command-line operations.
On Windows, use the Windows Power Shell for command-line operations.
Create your git repository on a hosting service or a self-managed server.
Names with generic meanings are strictly prohibited, as RVX features are deliberately disabled for repositories with such names.
The following are examples of prohibited names.
rvx_etri, rvx_platform, rvx_alpha, rvx_beta, ...
This list may be updated at any time without prior notice.
Clone your repository onto your local machine.
Clone the original repository, such as a tutorial
one.
Proceed with steps 1 and 2 of
the RVX installation. (Manual, Tutorial).
cmd) cd #(cloned directory of original repo)
cmd) make fork TARGET=#(cloned directory of your repo)The fork process
does not copy the platforms from the original repository.
Please copy them manually if needed.
Before working with your repository,
make sure to run activate or sync.
When the original repository is updated,
you can update yours using the same fork process.
After forking, make sure to run activate or sync.
If an update causes an issue due to a change in the submodule
address,
you can restore the .git directory using the
following command.
cmd) cd #(cloned directory of your repo)
cmd) make repair_repo