make_symbol.ulp

Copyright (c) 2004 Ed Anuff <ed@anuff.com>. All Rights Reserved.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the 
Free Software Foundation, Inc., 
59 Temple Place, Suite 330, 
Boston, MA  02111-1307  USA

Usage:

This ULP generates a symbol and device from a text file containing a list of pin names.

For non-BGA parts, the text file should contain a list of pin names in the pin number order that they are listed on the device datasheet.  Each pin name should appear on a seperate line and there should ideally be no blank lines in the file.  Duplicate names are acceptable and the ULP will automatically detect these and generate the appropriate @ suffix to allow them to work correctly within Eage.  

The following example shows a pin list text file that contains 6 pins:

GND
D
CS#
CLK
Q
VCC

In the above example, pin 1 would be GND and pin 6 would be VCC.

For BGA parts, the text file should contain a list of pin and pad names.  Each pin and pad name should be on a seperate line, with the pin name and pad name seperated by a tab.  For example, a BGA pin list text file might contain the following pins:

A1 	A1
A3 	B1
A5 	C1
A7 	D1
GND 	E1
NC 	A2
B2 	B2
A4 	C2
B6 	D2
A8 	E2
VCC 	A3
A2 	B3
B4 	C3
A6 	D3
B8 	E3
OE# 	A4
B1 	B4
B3 	C4
B5 	D4
B7 	E4

In the above example, the first item on each line is the pin name and the second item is the BGA pad name.

After the ULP is run, it will generate a symbol script and a device script, with the suffixes _symbol.scr and _device.scr.  The symbol script should be run first and then the device script.  If the package or package pad prefix was not defined correctly, it might be necessary to hand edit the device script.