A case for not choosing the latest components
By Dwight Bues, EE Times Guru
The 1980s were the halcyon days of circuit board design. In the days before Gate Arrays were inexpensively available with sufficient gate counts to completely implement the desired functionality, many manufacturers were producing ICs that implemented functional blocks that could be included in widely varied designs.
Since I was employed designing VME Bus circuit boards at that time, I recall having great flexibility in implementing my designs.Enter the engineer whom we called “Mr. VVI” behind his back.Incidentally, VVI stands for Vanished Vendor Item.A VVI is a device that, although you verified its availability with the vendor, they either never actually did produce or unexpectedly cancelled.
![]() |
E-mail This Article | ![]() |
![]() |
Printer-Friendly Page |
Related Articles
- Choosing the right A/D converter architecture and IP to meet the latest high speed wireless standards
- Key considerations and challenges when choosing LDOs
- An FPGA-to-ASIC case study for refining smart meter design
- SoC design: When is a network-on-chip (NoC) not enough?
- Radiation Tolerance is not just for Rocket Scientists: Mitigating Digital Logic Soft Errors in the Terrestrial Environment
New Articles
- Understanding MACsec and Its Integration
- Discover new Tessent UltraSight-V from Siemens EDA, and accelerate your RISC-V development.
- The Critical Factors of a High-performance Audio Codec - What Chip Designers Need to Know
- Density Management in Analog Layout Design: Addressing Issues and Ensuring Consistency
- Nexus: A Lightweight and Scalable Multi-Agent Framework for Complex Tasks Automation
Most Popular
- System Verilog Assertions Simplified
- Synthesis Methodology & Netlist Qualification
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
- UPF Constraint coding for SoC - A Case Study