[adc_ctrl,dv] Fix path in call to DV_ASSERT_CTRL

The DV_ASSERT_CTRL macro expands into an $assertoff(...) call with the
hierarchy argument to choose where the assertions get turned off (or
on).

$assertoff() and $asserton() don't work with this style of path in all
cases. The LRM only requires them to work with local or absolute
paths: it doesn't allow up-references.

VCS *does* allow them (which is why the code was written like this),
but Xcelium doesn't. There are nice ways to do this cleanly, but they
are rather more effort than just shoving the absolute path of the dut
into the file here. Something to clean up when we come back to this
module, I think!

Signed-off-by: Rupert Swarbrick <[email protected]>

Author: rswarbrick

hw/ip/adc_ctrl/dv/sva/adc_ctrl_sva_if.sv

@@ -118,6 +118,6 @@ interface adc_ctrl_sva_if
   `DV_ASSERT_CTRL("PwrupTime_A_CTRL", PwrupTime_A)
   `DV_ASSERT_CTRL("WakeupTime_A_CTRL", WakeupTime_A)
   `DV_ASSERT_CTRL("EnterLowPower_A_CTRL", EnterLowPower_A)
-  `DV_ASSERT_CTRL("ADC_CTRL_FSM_A_CTRL", dut.u_adc_ctrl_core.u_adc_ctrl_fsm)
+  `DV_ASSERT_CTRL("ADC_CTRL_FSM_A_CTRL", tb.dut.u_adc_ctrl_core.u_adc_ctrl_fsm)
 
 endinterface : adc_ctrl_sva_if