IP Verification : IP TripTik needed on system-on-chip highway
IP TripTik needed on system-on-chip highway
By David Lammers, EE Times
May 28, 2002 (9:57 a.m. EST)
URL: http://www.eetimes.com/story/OEG20020524S0092
By this fall, hundreds of system-on-chip design teams around the world will be targeting 90-nanometer process technologies. Though schedules vary, the leading foundries and integrated device manufacturers expect to make system-chips on 90-nm design rules by next spring. With transistor counts of 100 million or more translating into gate counts of 20 million plus, these SoC devices will-with few exceptions-include intellectual property brought in from a company's own IP repository or purchased from a commercial IP vendor. Dabs of memory placed here and there, digital signal processors and microcontrollers, USB and other interface circuitry . . . the list is long. To broaden their IP offerings and develop a new revenue stream, companies such as IBM, Motorola, Philips, STMicroelectronics and many others are forming partnerships with two ideas in mind. One thrust is to create process platforms that include a core digital transistor tha t will be as close to the same as possible among the various partners. The other prong is to create both hard and soft IP that can be easily swapped among the partners and sold to other vendors. Consider Motorola, which recently announced that it will co-develop process technology with two European partners, STMicroelectronics and Philips, at a 300-mm development fab at Crolles, France. These companies have been "aligning" their processes with Taiwan Semiconductor Manufacturing Co. At the 90-nm node and beyond, the trio will be able to provide one another with IP from within their own repositories and from commercial IP vendors qualified on TSMC's processes, said Craig Lage, a director at Motorola's semiconductor process R&D center (Austin, Texas). IBM is taking a similar track. The company wants to develop IP libraries that can be sold to companies that would have the option of fabbing their SoC designs at a foundry. Will it work? Or will these designs get bogged down in leg al tangles, in which the secret sauce within an IP block is patented-protected from deep disclosure to a design team at one of the partners or commercial IP providers? Will the design team have the same understanding as the team that originated the IP of what "functional verification" means? Contributors to the week's In Focus section consider the steps SoC design teams can take to ensure that verified IP blocks will work properly in the context of a full chip.
Related Articles
- Case study of a complex video system-on-chip
- A Multiprocessor System-on-chip Architecture with Enhanced Compiler Support and Efficient Interconnect
- Developing a Reusable IP Platform within a System-on-Chip Design Framework targeted towards an Academic R&D Environment
- DPCI: An Efficient Scalable System-on-chip Communication Architecture
- An Overview of Secret Key and Identity Management for System-on-Chip Architects
New Articles
- Quantum Readiness Considerations for Suppliers and Manufacturers
- A Rad Hard ASIC Design Approach: Triple Modular Redundancy (TMR)
- Early Interactive Short Isolation for Faster SoC Verification
- The Ideal Crypto Coprocessor with Root of Trust to Support Customer Complete Full Chip Evaluation: PUFcc gained SESIP and PSA Certified™ Level 3 RoT Component Certification
- Advanced Packaging and Chiplets Can Be for Everyone
Most Popular
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- UPF Constraint coding for SoC - A Case Study
- Dynamic Memory Allocation and Fragmentation in C and C++
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
E-mail This Article | Printer-Friendly Page |