• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. Anyone ever import an ATE tester STDF fail log into Encounter...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 63
  • Views 12762
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Anyone ever import an ATE tester STDF fail log into Encounter Diagnostics?

SteveJ
SteveJ over 13 years ago

STDF, an industry standard format and yet Encounter only supports Chip Pad Pattern (CPP) and it's own format generated output. The convert_failures_to_cpp.pl script seems too generic to be of much use and the instructions leave much to be desired as it doesn't line-up with standard output from a tester.

Some of the documents on Cadence solutions seem to imply that Encounter Diagnostics in Volume mode will take in an SQL style database but once again user guide rather vague, more like you have to build that from CPP inputs for different die.

  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information