Merge pull request #2295 from silabs-krdosvik/zalrsc-debug-addition-2

Debug vplan: zalrsc

cv32e40s/docs/VerifPlans/Simulation/debug-trace/CV32E40XS_debug.csv

@@ -174,7 +174,9 @@ The only supported match types are ""address match"" for {instr execution, load,
 Data matching is not supported (only addr matching), so ""mcontrol6.select"" is always 0.","Configure triggers for load/store/execute and combinations of them, configure tdata2, cause triggers to fire and check that debug mode is entered correctly.  All of these configurations must be crossed, also against match conditions.",Self Checking Test,Directed Self-Checking,Testcase,DTC: debug_test_trigger,?,"""tdata3"" and ""tcontrol"" should be removed.",?
 ,,,,,,Assertion Check,Other,Assertion Coverage,"A: a_dt_instr_trigger_hit_*, a_dt_load_trigger_hit_*, a_dt_store_trigger_hit_*. ",?,?,?
 User Manual v0.9.0.,,,trigger csrs,Some fields in the trigger csrs are hardwired.,Check that the tied fields are tied.,Assertion Check,Other,Assertion Coverage,"A: a_dt_tie_offs_tselect, a_dt_tie_offs_tdata1_mcontrol, a_dt_tie_offs_tdata1_etrigger, a_dt_tie_offs_tdata1_mcontrol6, a_dt_tie_offs_tdata1_disabled, a_dt_tie_offs_tdata2_etrigger. a_dt_tie_offs_tinfo.",,,
-,,,"""mcontrol6"" atomics","40X, ""mcontrol6"" trigger behavior has specific descriptions for ""A"" extension.","40X, TODO this section must be filled out when the time comes for planning atomics verification.",,,,,?,?,?
+,,,"""mcontrol6"" and ""mcontrol"" atomics","40X, ""mcontrol"" and ""mcontrol6"" trigger behavior has specific descriptions for ""A"" extension.","40X, TODO AMO.",Assertion Check,Other,Assertion Coverage,Not yet prioritized (TODO).,,,
+,,,,"LR.W have same trigger match rules as any other loads, no matter what the destination register is. ","Inspect that LR.W is treated like any other load instruction, no matter what the destination register is.",N/A,Other,inspection,This seems to be correct. And incorrect behaviour should therefore be triggered by the a_dt_load_trigger_hit_* assertions,,,
+,,,,"SC.W have same trigger match rules as any other store, no matter if it is successful or failing.","Inspect that SC.W is treated like any other store instruction, no matter if it is successful or failing.",N/A,Other,Assertion Coverage/inspection,This seems to be correct. And incorrect behaviour should therefore be triggered by the a_dt_store_trigger_hit_* assertions,?,?,?
 "40S User Manual
 
 Debug 1.0.0","Control and Status Registers

cv32e40s/docs/VerifPlans/Simulation/debug-trace/CV32E40XS_debug.json

@@ -468,13 +468,43 @@
         "Reference document": "",
         "Requirement Location": "",
         "Feature": "Trigger module",
-        "Sub Feature": "\"mcontrol6\" atomics",
-        "Feature Description": "40X, \"mcontrol6\" trigger behavior has specific descriptions for \"A\" extension.",
-        "Verification Goal": "40X, TODO this section must be filled out when the time comes for planning atomics verification.",
-        "Pass/Fail Criteria": "",
-        "Test Type": "",
-        "Coverage Method": "",
-        "Link to Coverage": "",
+        "Sub Feature": "\"mcontrol6\" and \"mcontrol\" atomics",
+        "Feature Description": "40X, \"mcontrol\" and \"mcontrol6\" trigger behavior has specific descriptions for \"A\" extension.",
+        "Verification Goal": "40X, TODO AMO.",
+        "Pass/Fail Criteria": "Assertion Check",
+        "Test Type": "Other",
+        "Coverage Method": "Assertion Coverage",
+        "Link to Coverage": "Not yet prioritized (TODO).",
+        "Review (Marton)": "",
+        "Review (Robin)": "",
+        "Review (Henrik)": ""
+    },
+    {
+        "Reference document": "",
+        "Requirement Location": "",
+        "Feature": "Trigger module",
+        "Sub Feature": "",
+        "Feature Description": "LR.W have same trigger match rules as any other loads, no matter what the destination register is. ",
+        "Verification Goal": "Inspect that LR.W is treated like any other load instruction, no matter what the destination register is.",
+        "Pass/Fail Criteria": "N/A",
+        "Test Type": "Other",
+        "Coverage Method": "inspection",
+        "Link to Coverage": "This seems to be correct. And incorrect behaviour should therefore be triggered by the a_dt_load_trigger_hit_* assertions",
+        "Review (Marton)": "",
+        "Review (Robin)": "",
+        "Review (Henrik)": ""
+    },
+    {
+        "Reference document": "",
+        "Requirement Location": "",
+        "Feature": "Trigger module",
+        "Sub Feature": "",
+        "Feature Description": "SC.W have same trigger match rules as any other store, no matter if it is successful or failing.",
+        "Verification Goal": "Inspect that SC.W is treated like any other store instruction, no matter if it is successful or failing.",
+        "Pass/Fail Criteria": "N/A",
+        "Test Type": "Other",
+        "Coverage Method": "Assertion Coverage/inspection",
+        "Link to Coverage": "This seems to be correct. And incorrect behaviour should therefore be triggered by the a_dt_store_trigger_hit_* assertions",
         "Review (Marton)": "?",
         "Review (Robin)": "?",
         "Review (Henrik)": "?"