|
 AA
automates pre-layout testability analysis. AA tools are typically
used after schematic capture and before CAD layout for assemblies
that have a mix of scan and non-scan devices. AA generates two reports
to help design and test engineers make the most effective use of
physical and virtual access to the assembly-under-test.
The Virtual Interconnect Test report identifies all the pure scan
nets and scan control nets (TDI/TDO interconnects) that can be fully
tested by VIT and TAPIT
techniques, and where physical test points can be safely eliminated.
The Virtual Component Test report identifies the nets where adding
physical access would permit VCCT
testing of non-scan devices. For in-circuit test, these nets can
be accessed by a bed-of-nails probe. For the edge-connector test,
nets can be routed to an edge connector or to a test connector for
access by ATE.
For the VIT report, AA sorts networks into four
categories:
- Pure scan nets
- Scan control nets
- Partial scan nets
- Non-scan nets
Physical test-pad access can be safely eliminated from pure scan
and scan control networks.
Boundary-Scan Virtual Interconnect
Test Report
|
| Pure boundary scan nets that
do not require test pads:
Net named ADBIO0 with device leads U_17_5 and U_16_144.
Net named ADBIO1 with device leads U_17_6 and U_16_146.
Net named ADBIO10 with device leads U_17_16 and U_16_7.
Net named ADBIO11 with device leads U_17_17 and U_16_9.
Net named ADBIO12 with device leads U_17_20 and U_16_11.
Net named ADBIO13 with device leads U_17_21 and U_16_13.
Net named ADBIO14 with device leads U_17_22 and U_16_15.
Net named ADBIO15 with device leads U_17_23 and U_16_17.
Net named ADBIO16 with device leads U_17_24 and U_16_145.
-
-
-
Boundary scan control nets that do not require test pads:
Net named TDX2 with device leads U_1_33 and U_16_56.
Net named TDX5 with device leads U_9_11 and U_11_14.
Net named TDX3 with device leads U_1_34 and U_10_14.
Net named TDX4 with device leads U_9_14 and U_10_11.
Net named TDX6 with device leads U_11_11 and U_12_14.
Net named TDX7 with device leads U_17_3 and U_12_11.
Net named TDX1 with device leads U_16_52 and U_14_11.
Nets with partial boundary scan access that require test
pads:
Net named PIPECLK with device leads U_17_63, U_4_64, U_16_51,
U_7_11, and U_13_11.
Net named A0 with device leads U_1_140 and U_8_6.
Net named A1 with device leads U_1_72, U_6_8, U_5_8, U_2_10,
and U_3_10.
Net named A10 with device leads U_1_61, U_6_22, U_5_22,
U_2_24, and U_3_24.
Net named A11 with device leads U_1_58, U_6_19, U_5_19,
U_2_21, and U_3_21.
Net named A12 with device leads U_1_57, U_2_23, and U_3_23.
Net named A13 with device leads U_1_56, U_2_2, and U_3_2.
Net named A2 with device leads U_1_71, U_6_7, U_5_7, U_2_9,
and U_3_9.
Net named A23 with device leads U_1_43, R_2_2, and R_1_1.
Net named A3 with device leads U_1_70, U_6_6, U_5_6, U_2_8,
and U_3_8.
-
-
-
Nets without boundary scan that require test pads:
Net named PIPEB0 with device leads U_4_1 and U_13_2.
Net named ND5D with device leads U_4_73 and R_14_1.
Net named ND5E with device leads U_4_72 and R_13_1.
Net named ND5F with device leads U_4_66 and R_12_1.
Net named PIPEC2 with device leads U_4_78 and U_7_7.
Net named PIPEC1 with device leads U_4_77 and U_7_4.
Net named PIPEC0 with device leads U_4_76 and U_7_3.
Net named ND6U with device leads U_4_77 and U_7_4.
Net named ND6V with device leads U_6_20, U_5_20, and R_15_1.
-
-
-
|
 |
