Problems:
1. Do you spend 2 or more months
developing validation test code for you new IC or device?
2. Do you struggle with test code
debugging and miss production goals?
3. Do you end up with many revision of
the same IC with overblown budget and missed time to market?
4. Do you keep revisions go A through
F? End up with Rev F, "failure to go to market"?
1. Cut back those first 2 months of
test development down to 1-2days.
2. Spend first 2 months instead on
characterizing with increased automation and debugging capabilities.
3. Meet production goals and
timelines.
4. Stop cycle of revs. At a minimum,
find all your device bugs
with rev A and go to market with rev B.
5. Provide your team
and company with cutting-edge technological advantage over your
competitors.
1. Scan device registers, measure pin
outputs, cross-test multiple modules (Oscillator, Regulator, Bandgap,
etc.) all on the first day of device arrival.
2. Focus engineering resources towards
finding bugs within your prototype device, not within the test code.
3. Ready your characterization and validation
software even before device returns from fabrication.
4. Reuse previously developed test modules
for future prototype devices. No porting required when an IP is
reused for a new family of devices.
Solution is
here: Semiconductor industry's newest Integrated Circuit Test
Development Software.
Chipalizer: Chip analyzer uploads
"your product datasheet" and deploys "device specific" test software
with automatic detection of any
equipment stack on USB, GPIB and/or RS-232.