From 6a33f69ccbf2104e6c0a824e28763953501ebe97 Mon Sep 17 00:00:00 2001 From: Elliot Baptist <157390164+elliotb-lowrisc@users.noreply.github.com> Date: Wed, 18 Sep 2024 12:55:37 +0100 Subject: [PATCH] Update verification_stages.rst OT links --- doc/03_reference/verification_stages.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/03_reference/verification_stages.rst b/doc/03_reference/verification_stages.rst index a93fdb35fc..76d36a4cd1 100644 --- a/doc/03_reference/verification_stages.rst +++ b/doc/03_reference/verification_stages.rst @@ -3,9 +3,9 @@ Verification Stages =================== -Ibex is being verified as part of the `OpenTitan `_ project and follows the `verification stages used in OpenTitan `_. +Ibex is being verified as part of the `OpenTitan `_ project and follows the `verification stages used in OpenTitan `_. The current verification stage of the 'opentitan' configuration of Ibex is **V2S**. -The full definition of V2S can be found at the `OpenTitan V2 `_ and `OpenTitan V2S `_ checklists. +The full definition of V2S can be found at the `OpenTitan V2 `_ and `OpenTitan V2S `_ checklists. Other Ibex configurations do not have a formal verification stage at present. V1 Checklist @@ -136,7 +136,7 @@ V2S Checklist Ibex SEC_CM Test Mapping ------------------------ -The :ref:`security features Ibex implements ` are given specific security countermeasure names in OpenTitan (see 'Security Countermeasures' in the `Hardware Interfaces `_ documentation section). +The :ref:`security features Ibex implements ` are given specific security countermeasure names in OpenTitan (see 'Security Countermeasures' in the `Comportability Definition and Specification `_ documentation section). Each countermeasure has a test that exercises it. The mapping between countermeasures and tests is given below