LTX Corp. (LTXX) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LTX Corp. (LTXX)

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Mike Botham who wrote (1341)	8/7/1998 12:58:00 PM
From: ATELifer	Read Replies (1) of 2126

Mike, You are absolutely right in your statements about what is presented to the DUT pins. However, the key is where you make the tradeoffs. Many times a system can produce the waveform required by the DUT for specific pins but fail to produce the waveforms for other pins on the DUT because of the frequency mode selected. Device busses operating at different frequencies can be a problem. Some IO controller devices can have this problem where frequency requirements dictate 133MHz on some pins and 100MHz or some other lower frequency on other pins. The mode boundaries are what kill you. In order to run some pins at 133MHz you must select the 250MHz mode for all pins and thus limit the format flexibility required on those pins running under 125MHz. This will not always be the case and as devices run faster the format flexibility requirements are reduced. Another area where mode boundaries can hurt you is the complexity of the patterns. This is an area where the enVision++ software is very powerful in that it shields the user from having to create different pattern formats to satisfy each of the frequency modes. This is managed transparently in enVision++. -AL

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next