From ec3143f01471840134064e8b20c20a8e53a33fe5 Mon Sep 17 00:00:00 2001
From: David Harris <David_Harris@hmc.edu>
Date: Fri, 29 Nov 2024 12:03:14 -0800
Subject: [PATCH] Updated warning in ramxdetector

---
 testbench/common/ramxdetector.sv | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/testbench/common/ramxdetector.sv b/testbench/common/ramxdetector.sv
index c600cff8c..fac34fb43 100644
--- a/testbench/common/ramxdetector.sv
+++ b/testbench/common/ramxdetector.sv
@@ -39,7 +39,7 @@ module ramxdetector #(parameter XLEN, LLEN) (
     /* verilator lint_off WIDTHXZEXPAND */
     if (MemReadM & ~LSULoadAccessFaultM & (ReadDataM === 'bx)) begin
       /* verilator lint_on WIDTHXZEXPAND */
-      $display("WARNING: Attempting to read from unitialized RAM.  Processor may go haywire if it uses x value. But this is normal in WALLY-mmu tests.");
+      $display("WARNING: Attempting to read from unitialized RAM.  Processor may go haywire if it uses x value. But this is normal in WALLY-mmu and ExceptionInstr tests.");
       $display("  PCM = %x InstrM = %x (%s), IEUAdrM = %x", PCM, InstrM, InstrMName, IEUAdrM);
       //$stop;
     end