home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.ibm.pc.hardware
- Path: sparky!uunet!wupost!sdd.hp.com!hp-cv!hp-pcd!hpcvca!hpcvccl.cv.hp.com!scott
- From: scott@hpcvccl.cv.hp.com (Scott Linn)
- Subject: Re: What's the deal? My chip says "SX-25"; Norton says "SX-33"
- Message-ID: <1992Dec31.011847.26106@hpcvca.cv.hp.com>
- Sender: nobody@hpcvca.cv.hp.com
- Nntp-Posting-Host: hpcvccl.cv.hp.com
- Organization: Hewlett-Packard Company, Corvallis, Oregon USA
- References: <1ht90eINNei0@hpscit.sc.hp.com>
- Date: Thu, 31 Dec 1992 01:18:47 GMT
- Lines: 27
-
- matthias@nsr.hp.com (Matthias Kamm) writes:
- : : The usual route is exactly as Danny had stated: test every part at 33MHz.
- : : If it fails, test it at 25. If it fails, keep going down until you are
- : : out of speed.
- :
- : This is very possibly wrong. If this were the case, then the cost of test for
- : the 16Mhz chip would be three times that of the 33Mhz chip (assuming 33,25,16
- : speed grades for their microprocessors). Every chip test insertion
- : cost bucks, and the 25Mhz chip with two test insertions would cost Intel MORE
- : than the 33Mhz chip! One thing we used to do (when I worked at a semi. co.)
-
- You didn't read the rest of my response, did you?
-
- You put the part in a socket. The program runs non-speed critical tests
- first. If the part fails, the package autohandler kicks it out to the fail
- bin. If it passes, the test program then runs a 33MHz test. If that passes,
- the autohandler bins it out to the 33MHz bin/tube. If it fails, the test
- then turns the clock down to 25MHz. Run the (smaller vector set). If it
- passes, bin to 25MHz. Etc.
-
- Note that there is only one (1) insertion, everything is autohandled via
- machine, and the test time is NOT 3x, but something quite a bit less. A
- person simply loads parts in the top of the autohandler, and removes packages
- pre-binned out the bottom.
-
- Scott Linn
- scott@hpcvccl.cv.hp.com
-