SCAN Validation – Mock Stages
hubs  dfx  val  scan
1. ip_connectivity_gen_checks:
This stage will create a module named “dfx_scan_ip_connectivity_checker”, containing
checkers for signals with “clst_ultiscan” in their name.
The check is done at every posedge of “dfx_ti.scan_ti.chassis_ip_connectivity_clock” and it
makes sure the sources are indeed connected to their destination, by simply comparing them.
Script: $WORKAREA/src/val/subsystems/dfx/script/scan_ip_connectivity_extraction.py
Inputs:
 ip2ip_file: $WORKAREA/output/hubs/defacto/trial/work/reports/ip2ip_final.rpt
Output:
 $WORKAREA/output/hubs/dfx/val/scan/scan_ip_connectivity_assertion.sv
Run cmd:
The Script will be called using SCAN val main Makefile as follows:
cd $WORKAREA/dfx/tessent/val/scan.
make -f Makefile run_ip_connectivity_list
Summary: the script will extract from ip2ip_final.rpt file all sources and destinations with
“clst_ultiscan” in their names, based on this list it will build scan_ip_connectivity_assertion.sv file
which contains following statements for each source and destination extracted: if (source ===
destination)  OK, else  Error. It also does some find-replace on the signal names. The
scan_ip_connectivity_assertion.sv file will be included in
$WORKAREA/src/val/subsystems/dfx/tb/dfx_scan_ip_connectivity_checker.sv
IT IS NOT A STATIC CHECK – IT RUNS DURING SIMULATION
2. scan_flop_extraction:
used for back annotation / isolation testing .
-
scan_io_extraction_chassis: