|
When designing a modern package it is critical to know the net of each die pad.
Many of the routing rules are net based. Power and grounds are of course treated
much differently than IOs. Yet many IC designers persist in sending the packaging
designer the pad information without the proper net names. At right you can see a typical pad coordinate table provided by an IC desginer. In fact, sometimes the die pads don't even have numbers -- all that is provided is the center coordinates of the pad! |
1 -685 420 2 -685 300 3 -685 180 4 -685 60 5 -685 -60 6 -685 -180 7 -685 -300 8 -685 -420 9 -420 -685 10 -300 -685 11 -180 -685 . . . 28 60 685 29 -60 685 30 -180 685 31 -300 685 32 -420 685 |
|
Power & Ground Nets are Crucial! If nothing else, the IC designer should assign the power and ground nets. Give all nets that are to be connected to a common metal ring the same net name. For the rest of the IO pads, give each die pad a unique name. The package design software assumes that any pads that share a common net name will be connected together! |
vss 1 -685 420 io1 2 -685 300 io2 3 -685 180 io3 4 -685 60 vdd 5 -685 -60 io4 6 -685 -180 io5 7 -685 -300 vddint 8 -685 -420 io6 9 -420 -685 io7 10 -300 -685 vss 11 -180 -685 . . . io8 28 60 685 nc 29 -60 685 vdd 30 -180 685 io10 31 -300 685 io11 32 -420 685 |
|
Verification using Connectivity If a proper name is assigned to each die pad, upon completion of the package, the package designer can create a netlist derived from the actual connectivity that matches up each die pad with the ball it is attached to. This makes verifying that the package is correctly designed more accurate. Many companies have found to their chagrin, that a completed package connects to the wrong ball pads. The error was not caught during package design because the designer had to hand edit the netlist provided by the IC designer to add in the signal names. |
vss 1 - io1 2 A5 io2 3 B4 io3 4 C4 vdd 5 - io4 6 E5 io5 7 F4 vddint 8 - io6 9 G3 io7 10 G4 vss 11 - . . . io8 28 H3 nc 29 - vdd 30 - io10 31 J4 io11 32 J5 |
|
What's in a AIF File Describes the basic sections of the AIF file and their syntax. |
Creating an AIF file with Excel Describes how to create an AIF file using MS Excel. |
Creating an AIF from GDSII Describes the program, SmartDie, used to read, scan and convert a pad ring layer into AIF. |
||
|
Sample AIF Files Shows simple and complex AIF files and their associated layout. |
Common Errors Describes the most common errors made when creating an AIF File. |
Multi Die AIF A special version of AIF II designed to contain multiple die (MCM) |
||
|
Amkor Adopts AIF Format Amkor Technology, the world's largest contract assembler has adopted AIF as its preferred format for exchanging die data ... |
Read AIF into Cadence APD You can read an AIF file directly into Cadence APD with this SKILL program. All intelligence is transferred. |
Wire Attach Offset describes how to support a wire attach point offset in AIF without breaking a proper AIF reader ... |
||
|
Importance of Net Names! An explantion of the value of adding net names to your die pad list ... |
How to Extend AIF Writing your own AIF tools? How to add your own extensions so that you won't break other's AIF parsers. |
AIFVU AIF Viewer web page.. |
||
|
ARTWORK CONVERSION SOFTWARE, INC. Company Profile 417 Ingalls St., Santa Cruz, CA 95060 Tel (831) 426-6163 Fax 426-2824 email: info@artwork.com |