-----------------------------------------------------------------
------------------------------------------------------------------  
  OrCAD Programmable Logic Design Tools Release IV-386 Version 1.03 
-----------------------------------------------------------------
------------------------------------------------------------------

Enclosed is your OrCAD Programmable Logic Design Tools Release IV-386
Version 1.02 product (PLD-386).  The product includes a set of two disks; 
three manuals: Programmable Logic Design Tools User's Guide, Programmable 
Logic Design Tools Reference Guide, and Mach Design Guide; and a letter. 
The disk(s) contain PLD-386 (the compiler), VECTORS (the test vector
generator and logic simulator), a logic fitter from AMD to use for 
designing logic for MACH devices, a parts library, a reference library, 
and sample source code and associated schematics.

This product is designed to run on 386 or 486-based IBM PC-compatible 
machines. It uses the Ergo DOS extender and supports memory above 640K
available on your computer.  OrCAD recommends that you run this product 
on a computer that has at least 2MB of RAM.

------------------------------------------------------------------ 
------------------------------------------------------------------ 
PLD-386 features  

1.  AMD's MACH devices are supported in PLD-386 by using AMD's device
fitter software.  The devices currently supported are the MACH110 and
MACH210.  For information about these devices, see the OrCAD MACH
Design Guide. 

2.  In the LIBRARY directory, PLD-386 uses a slightly different naming 
convention than PLD-PC. PLD-386 recognizes the device type by its first 
character followed by the number identifying the type.  This naming 
convention allows for devices with different architectures that are the 
same basic type, such as the 22V10.  The Lattice GAL22V10 has 64 signature 
fuses that are not found in standard PAL devices.  If the device type 
specified is PAL22V10, then the device table P22V10.DEV is opened. If the 
type specified is GAL22V10, then G22V10.DEV is opened.  If no characters 
precede the device type, P is the default.  If 22V10 is the device type, 
for example, PLD-386 selects the P22V10.DEV.  

3.  When PLD-386 runs, it looks for the configuration file PLD.BCF.  To find
it, PLD-386 first looks in the current design (working directory).  If it
doesn't find the file there, PLD builds a path by getting the environmental
variable stored as ORCADPROJ and adding "TEMPLATE\" to it, and then
looks for the configuration file there.  If the configuration file isn't 
there, then PLD-386 uses its built-in default settings.  The file 
SWITCHES.TXT contains a list of defaults.  

4.  Stack space is increased to 32K (up from the 12K of PLD-PC v4.02).  This
accommodates the larger data space PLD-386 is able to use.

5.  The .BIN files (binary table files) used in PLD-PC v4.02 and later are  
part of the PLD-386 compiler. In PLD-PC, .BIN files are used to configure  
special characteristics about certain parts that PLD-PC cannot handle 
directly.  

6.  Schematic symbols in PLD-386 are user-definable.  (In PLD-PC, schematic 
symbols are hard-coded into the compiler.)  PLD-386 symbol definitions are 
stored in the file, SYMBOLS.SRC, which is found in the library directory.  
New definitions can be added to the file or existing ones modified.  Before 
and after making any changes to the file, be sure to make a backup, 
otherwise you risk losing your changes if the file is overwritten (such as 
when you installed an updated version of PLD-386). For more information 
about how to build symbols, see the file SYMBOLS.SRC.  

7.  Device tables in PLD-386 are user-definable.  PLD-386 compiles ASCII 
device description tables (.DEV files) as it reads them.  You can build your 
own ASCII tables (or modify OrCAD's) to extend PLD-386's support to
certain new devices.  See the file DEVICES.TXT for information on how to
design these files.  

8.  The synthesis algorithm PLD-386 uses for saving memory in all
operations (/m3) handles 16 different signals.  (PLD-PC handles only
14 signals.)  For equations that use more than 16 signals, the compiler
automatically switches to a different synthesis algorithm.  

9.  Internal to the 22V10 is a synchronous preset node that sets all the  
registers when its product term is activated.  (In PLD-PC this was
available only by assigning a pin 26 to the reset node then writing an
equation for the reset term.)  PLD-386 scans all the registered equations
looking for a common product term.  If one is found it is stripped from the
equation and moved to the synchronous preset product term.  This feature
is available with the P22V10.DEV device table.  The P22V10x.DEV device
table makes no reference to the functions that provide this feature.  

10.  In PLD-PC, the asynchronous reset node of the 22V10 was available by  
assigning a signal to an imaginary pin (pin 25).  This was done in the same  
way as the preset node as described above.  Although these controls are still  
available, the dff() and register schematic symbols in PLD-386 now  
program the asynchronous reset term.  The reset will need to be shared by
all the registers, so do not try to reset one register with an equation that
is different from another.  Again this is only available when you use the
P22V10.DEV file.  

11. PLD-386 includes new keywords that allow you to control how RA and
EP devices behave when a reset or preset is applied to a register that is
defined to use the opposite polarity.  By default, the RA and EP devices are
active low.  (In PLD-PC, if a register was defined to be active high and a
reset or preset were applied, VECTORS would show the wrong value.)  For
more information about the new keywords, see the file DEVICES.TXT.

12.  The flat file (or make file) feature is temporarily disabled.  Do not
use the /f1 or /f2 switches.  In ESP, make sure that the radio button
labeled "Source is a Single File" is selected for the "Compile Source,"
"Test Logic," and "Create PLA" buttons.  

13.  To specify exactly where feedback occurs in a macrocell, use
signal pairing.  For examples, see the sample files PAIRING.PLD and
PAIRINGS.PLD.  PAIRING shows an example using Boolean equations while
PAIRINGS uses a schematic.  When using a schematic to define logic, and
signal feedback is needed, attach a module port to the signal that is to
feedback.  See PAIRINGS.SCH for a simple example of how signal pairing is
used in schematic entry.  Be sure to configure PLDGATES.LIB to view the
schematic in DRAFT.  

14. PLD-386 includes these new device tables:

GAL22V10      Supports signature fuses, but does not support reset or 
              preset factoring, or pin reassignment.

GAL20RA10     Supports signature fuses.

P22V10C       PLCC version of the 22V10. Does not support reset or 
              preset factoring, or pin reassignment.

P20L10C       PLCC version of 20L10.

P20L8C        PLCC version of 20L8.

P20R8C        PLCC version of 20R8.

MACH110           
MACH210    

15. PLD-386's schematic symbol library includes a G169, a binary up/down
counter.

16. PLD-386 runs in text mode (rather than in graphics mode).  Messages
from the compiler can be found in the .LST file PLD-386 produces, rather than 
in the #ESP_OUT.TXT file (which is where error messages from programs that
run in graphics mode can be found).  You can open the .LST file with any 
text editor. 

------------------------------------------------------------------ 
------------------------------------------------------------------ 
To install PLD-386:  

You install PLD-386 using a program called INSTALL, which you received 
with the product software.  During the installation process, the program 
will ask you to answer some questions about how you want the product to 
be installed.  Follow these steps:  

1.  Enter INSTALL to run the INSTALL program.  The ORCAD TOOL SETS  
screen displays.  Move the highlight bar to OrCAD Programmable Logic
Device Tools.  

     NOTE: If your computer has another installation program called       
     INSTALL, change directories to the location of your OrCAD executable         
     files before running INSTALL.  

2.  Press the space bar to change OrCAD Programmable Logic Device Tools
to YES.  

3.  Press <Enter>.  INSTALL then asks a series of questions about drives 
and directories.  Move the highlight bar to the appropriate selections and 
press <Enter>.   

INSTALL then asks you to place the "PLD Disk 1" in the drive you
selected.  

4.  Place Disk 1 in the drive and press any key to continue the installation. 
A screen that lists installation options displays.  

5.  Move the highlight bar to "Standard Installation of PLD Release IV-386  
Product Version 1.03" and press <Enter>.  The prompt "Do you want ALL of
the ORCADESP.DAT files in your project sub-directories updated?"
displays. ORCADESP.DAT files are used to store configuration information. 
PLD-386 uses a newer version of ORCADESP.DAT than PLD-PC used, so the old 
files need to be updated. Your old configuration settings are transferred 
to the newer version, so you won't have to reset your configurations.

If all of your OrCAD directories are on the same disk drive AND your
environment variables point into the directory structure properly, then
answer YES. If not, answer NO. 

Note that if you answer YES and your directory structure is somehow different
from what INSTALL expects, nothing destructive happens: INSTALL simply 
reports that the FIXDAT operation was unsuccessful.   

6.  If you answered YES in step 5, when the installation is complete,  
INSTALL will tell you it is going to use FIXDAT to update local  
configurations.  To allow INSTALL to proceed, press any key. To cancel
the operation, press <Esc> instead.  

If you see a message saying that FIXDAT was unable to update your 
ORCADESP.DAT files, either your OrCAD directories are not all on the 
same disk drive or not all of the environment variables point into the
directory structure properly. When this is the case, you must run FIXDAT
as a separate program.  FIXDAT is described in he next section of this file.  

When INSTALL is done, it displays "Installation Complete."  

------------------------------------------------------------------ 
------------------------------------------------------------------ 
Using FIXDAT  

FIXDAT is a program that transfers configuration information from older  
versions of ESP to newer versions--eliminating the need to reconfigure
tool sets, local configurations, and the on/off status of Transfers after
updating the software.  

When you install your new product or update, you are asked--at the 
beginning of the installation process--if you want to automatically update
the ORCADESP.DAT files in your design directories.  If you answer "YES," 
INSTALL runs a program called FIXDAT.  INSTALL automatically handles
the details and updates your configuration information.

FIXDAT is designed to run properly when the OrCAD directory structure is
found on one disk drive and the environment variables are set to point
to the proper directories.  If you ask INSTALL to run FIXDAT, and FIXDAT 
cannot find the files it needs (either because more than one disk is used or
environment variables do not point to the proper directories), it reports 
an error. In these cases, you can run FIXDAT as a separate program from the 
system command prompt. If you do not run FIXDAT when you install your update,
the ORCADESP.DAT file is copied to a TEMPLATE directory on the disk drive 
you specified as the drive on which to install the OrCAD software.  
FIXDAT takes two arguments:  

o     The path and filename of the old ORCADESP.DAT file to update.  
      In this discussion, the file to update is called the oldDATfile.  

o     The path and filename of the new ORCADESP.DAT file.  In this 
      discussion, this is called the newDATfile.  

This is how FIXDAT works:  

1.  First, FIXDAT reads in newDATfile followed by oldDATfile.  

2.  Then FIXDAT compares the two files and finds buttons in newDATfile
that have the same name as buttons in oldDATfile.  If it finds a match, it
copies the local configuration setting from oldDATfile to newDATfile. 
When FIXDAT is through with the comparison, you have a new newDATfile
that has all of oldDATfile's local configuration settings.   

3.  FIXDAT then replaces oldDATfile with the updated newDATfile.  

Note that if the newDATfile has new buttons in it that don't exist in the
oldDATfile, the local configuration settings for the new buttons are set to
OrCAD's defaults.  

------------------------------------------------------------------ 
Syntax  

FIXDAT [oldDATfile newDATfile] [switches]  

      Updates oldDATfile so that it has all of the buttons found in        
      newDATfile.  The settings in oldDATfile remain unchanged.  

/A   Reads the ORCADPROJ environment variable to find the TEMPLATE        
     design directory.  The ORCADESP.DAT files in ALL of the design        
     directories are updated to the version of the ORCADESP.DAT file in        
     the TEMPLATE design.  oldDATfile and newDATfile are not specified        
     when the /A switch is used.  

/L   Reads the ORCADPROJ environment variable to find the TEMPLATE        
     design directory.  The ORCADESP.DAT file in the current directory        
     only is updated to the version of the ORCADESP.DAT file in the        
     TEMPLATE design directory.  oldDATfile and newDATfile are not        
     specified when the /L switch is used.  

/U   Does the transfer even if oldDATfile and newDATfile are already       
     the same version.  The /U switch can be used in conjunction with the
     /L switch or /A switch.  If so, oldDATfile and newDATfile are not
     specified.  

      NOTE: FIXDAT reports an error if either newDATfile or oldDATfile        
      does not exist.  

------------------------------------------------------------------ 
Examples  

The next sections describe how to use FIXDAT to:  

o     Update all your ORCADESP.DAT files  

o     Update TEMPLATE's data file and data files in selected designs  

o     Update one ORCADESP.DAT file  

------------------------------------------------------------------ 
Update all your ORCADESP.DAT files  

If your directory structure is standard and you want to update all your
data files, follow these steps:  

1.  Change to the TEMPLATE design and enter this command:  

      C:\ORCAD\TEMPLATE>fixdat orcadesp.dat orcadesp.386  

ORCADESP.DAT is the data file with all your current configuration
settings.  ORCADESP.386 is the data file with the latest updates to the
design environment, and is saved in the TEMPLATE directory only when
FIXDAT is not run during installation.  This command updates your data file 
to the new version without losing your configuration settings.  

2.  To update the data file in each design, enter this line from anywhere in
the directory structure:  

      C:\>fixdat /a  

3.  Delete ORCADESP.386 from your TEMPLATE design to prevent copying it
to new designs.  If you allow INSTALL to automatically update the
ORCADESP.DAT files, INSTALL automatically deletes ORCADESP.386 for
you.  

------------------------------------------------------------------ 
Update TEMPLATE's data file and data files in selected designs  

1.  Change to the TEMPLATE design and enter this line:  

      C:\ORCAD\TEMPLATE>fixdat orcadesp.dat orcadesp.386  

Again, ORCADESP.DAT is the data file with all your current configuration  
settings.  ORCADESP.386 is the data file with the latest updates to the
design environment, and is saved in the TEMPLATE directory only when
FIXDAT is not run during installation.  This command updates TEMPLATE's 
data file to the new version without losing your configuration settings.  

2.  Change to the design containing the ORCADESP.DAT file you want to  
update.  

3.  Enter this line at the prompt:  

      C:\ORCAD\YOURDESN>fixdat /L  

4.  Repeat steps 2 and 3 for each design you need to update.  

5.  Delete ORCADESP.386 from your TEMPLATE design to prevent copying it
to new designs.  

------------------------------------------------------------------ 
Update one ORCADESP.DAT file  

To update a data file in a specific design without updating any other data  
files, follow these steps:  

1.  Copy the new data file ORCADESP.386 to a floppy disk.  In this example, 
the floppy disk is in drive A.  

2.  Delete ORCADESP.386 from your TEMPLATE design.  

3.  Enter this line:  

      C:\>fixdat \orcad\yourdesn\orcadesp.dat a:\orcadesp.386  

FIXDAT updates ORCADESP.DAT in the YOURDESN design to match the
version of ORCADESP.386 in the A: drive.  

-----------------------------------------------------------------
-------------------------------------------------------------------
Miscellaneous technical notes about PLD

1. Miser bits with EPLDs

EPLD devices supporting miser bits should have the miser bits set to 1.
The default state of these bits is 0.  If the design fails to program these
bits, unpredictable results may appear.  Use the configuration statement
below to ensure that the miser bits are programmed:

   | Configuration: "Miser:1"

2. Enable pin on RA devices

VECTORS looks at the product term as if it were the only enabling term
on RA devices.  Since the RA devices use a product term ANDed with an
external pin (13 on a 20R10 and 11 on a 16RA8), the external pin MUST be
enabled to get usable test vectors.  If this pin is not specified in the
PLD design, then by default VECTORS will enable this pin.

3. Array feedback on the EP310

The EP310 supports not only pin and register feedback, but also an array
feedback.  PLD-386 supports this feature with the configuration
statement:

   | Configuration: "Array Feedback", Q0

If this feature is used, the test vectors generated by VECTORS may be
incorrect.  VECTORS does not take the array feedback into account.

4. About specific devices

If you are confused about how the "in", "out", and "io" keywords apply to
specific devices, consult the DEVICES.TXT file, read its introductory
comments, and keep it handy in a notebook for reference.

As new device tables are developed, they are posted on the OrCAD
electronic bulletin board, which operates 24 hours a day.  Other notes and
information about OrCAD/PLD and the rest of the product line are also
available there.  The file BBS.TXT in the directory \ORCADESP\PLD
contains the latest information on the bulletin board and how to access it.



If you have any questions regarding this product, contact OrCAD Technical
Support at (503) 690-9722 (Monday-Friday, 8 AM to 4 PM).  

Thanks for your support,  

OrCAD 

