Update marchid, mvendorid, mimpid values in docs (#278)

* Update marchid, mvendorid, mimpid values in docs

* Update getting_started.rst

---------

Co-authored-by: Davide Schiavone <davide@openhwgroup.org>
This commit is contained in:
Mohammed Eladawy 2025-02-05 19:13:33 +02:00 committed by GitHub
parent 4b782ac0d7
commit b7e5534480
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -12,9 +12,8 @@ The RISC-V Privileged Architecture specifies several read-only CSRs that identif
These are ``mvendorid``, ``marchid`` and ``mimpid``. These are ``mvendorid``, ``marchid`` and ``mimpid``.
The fixed, read-only values for these CSRs are defined in :file:`rtl/cve2_pkg.sv`. The fixed, read-only values for these CSRs are defined in :file:`rtl/cve2_pkg.sv`.
Implementers should carefully consider appropriate values for these registers. Implementers should carefully consider appropriate values for these registers.
Ibex, as an open source implementation, has an assigned architecture ID (``marchid``) of 22. Ibex, as an open source implementation, has an assigned architecture ID (``marchid``) of 0x23 (equivalent to 0d35).
(Allocations are specified in `marchid.md of the riscv-isa-manual repository <https://github.com/riscv/riscv-isa-manual/blob/master/marchid.md>`_.) (Allocations are specified in `marchid.md of the riscv-isa-manual repository <https://github.com/riscv/riscv-isa-manual/blob/master/marchid.md>`_.)
If significant changes are made to the micro-architecture a different architecture ID should be used. If significant changes are made to the micro-architecture a different architecture ID should be used.
The vendor ID and implementation ID (``mvendorid`` and ``mimpid``) both read as 0 by default, meaning non-implemented. The vendor ID and implementation ID (``mvendorid`` and ``mimpid``). The vendor ID (mvendorid) is assigned the value 0x602 and the implementation ID (mimpid) is assigned the value 0x0.
Implementers may wish to use other values here.
Please see the RISC-V Privileged Architecture specification for more details on what these IDs represent and how they should be chosen. Please see the RISC-V Privileged Architecture specification for more details on what these IDs represent and how they should be chosen.