Slide 1 EBTW 2005, Tallinn, Estonia
- On the Greater Acceptance of Functional Test
- f PCB Assemblies.
Billy Fenton & Chris Hammond
On the Greater Acceptance of Functional Test of PCB Assemblies. - - PowerPoint PPT Presentation
On the Greater Acceptance of Functional Test of PCB Assemblies. Billy Fenton & Chris Hammond EBTW 2005, Tallinn, Estonia Slide 1
Slide 1 EBTW 2005, Tallinn, Estonia
Billy Fenton & Chris Hammond
Slide 2 EBTW 2005, Tallinn, Estonia
Slide 3 EBTW 2005, Tallinn, Estonia
Area-Array Packaging (e.g. BGA) Increasing Board Operating Speeds Board Strain? Lead-free solder? Hidden Vias
Complexity Cost
Slide 4 EBTW 2005, Tallinn, Estonia
MDA ICT Boundary Scan Functional Test
Slide 5 EBTW 2005, Tallinn, Estonia
A component test, not a system test. Test Programming using the netlist and ATPG. Diagnostics to component or node level. Automatic Coverage Report(?)
Test Access IC Test
Slide 6 EBTW 2005, Tallinn, Estonia
Test programming from netlist and BSDL. Diagnostics to pin level. Automatic coverage report.
Digital Only – limits coverage. DFT required – can limit coverage. Will security prevent it being a panacea?
Slide 7 EBTW 2005, Tallinn, Estonia
Test Programming is slow and difficult. Extensive UUT knowledge needed. This is exacerbated by increasing complexity. Diagnostics are poor. No coverage report.
Test access is not an issue. Test coverage is high. DFT is low.
Slide 8 EBTW 2005, Tallinn, Estonia
report. But, on newer boards, FT can go where ICT/MDA/BST cannot go, but it lacks the advantages that made these methods attractive. So, what we need is a FT, that provides ATPG, diagnostics, and coverage
FT as a supplement or replacement to traditional electrical type tests???
ICT/MDA/BST FT Electrical Test Functional Test
Slide 9 EBTW 2005, Tallinn, Estonia
Uses CPU Emulation. Standard Architecture Boards.
ATPG using a known-good board. Using the BOM to:
Slide 10 EBTW 2005, Tallinn, Estonia
chipset drivers.
for known devices.
correct chipsets drivers
assembles a test program.
be manually added.
Chipset Library
Slide 11 EBTW 2005, Tallinn, Estonia
variables.
Slide 12 EBTW 2005, Tallinn, Estonia
PXA 255 ASP SDRAM Flash Audio Codec USB Controller
Slide 13 EBTW 2005, Tallinn, Estonia
Don’t!! Technician Skill
‘Shotgun’
Historical Information
Guided Fault Isolation Probabalistic Methods
Slide 14 EBTW 2005, Tallinn, Estonia
Slide 15 EBTW 2005, Tallinn, Estonia
Use netlist to extract BOM. Associate components with tests, and include failure probability, and identify which tests are the primary test(s) for each component.
If a test fails each associated component is scored appropriately. After overall test completion each component is given a final score. Method TBD. A list of components is presented, the one with the highest score is the most likely defect. Real-time data could be used to adjust probabilities.
Primary Test? Probability BOM Filter
Slide 16 EBTW 2005, Tallinn, Estonia
Slide 17 EBTW 2005, Tallinn, Estonia
Fault universe represents all possible faults. Coverage is the % of coverable faults. How does this relate to different test methods. For FT how do you define the fault universe??? How do you know what faults are covered by a particular functional test? Must tests be weighted? Etc. It’s all largely subjective.
Is a % style report meaningless? But, it can be what the customer wants? Is a yes/no report more meaningful, possibly with a high/medium/low coverage metric? Can this be extracted from the BOM/Test Matrix?
Slide 18 EBTW 2005, Tallinn, Estonia
Slide 19 EBTW 2005, Tallinn, Estonia
Slide 20 EBTW 2005, Tallinn, Estonia
Slide 21 EBTW 2005, Tallinn, Estonia
Automatic block diagram generation Determining component complexity automatically
Slide 22 EBTW 2005, Tallinn, Estonia
ATPG. Diagnostics to component level. Automatic generation of a test coverage report.