
                      iFX780/iFX740 Open Fitter Kit
                               
                               Version 3.1
                               
            Support for Intel's iFX780/iFX740 FLEXlogic FPGAs

                               DOS Version


                             October 21, 1993
            


               --------------------------------------------
               1-800-628-8686 (Applications Hotline Number)
                     (916) 356-3600 (Bulletin Board)

                              Intel Corp.
                       Programmable Logic Devices
                         1900 Prairie City Road
                           Folsom, CA  95630
                                FM3-42




This release of the iFX780/iFX740 Open Fitter Kit adds support for the
iFX740 FPGA. This device is the same architecture as the iFX780 FPGA, but
contains 40 macrocells instead of the 80 macrocells in the iFX780. The iFX740
is available in both a 44 pin PLCC and 68 pin PLCC package.

The  iFX780/iFX740 Open Fitter Kit provides support within a variety of Third
Party environments for Intel's entire line of programmable logic.  With the
iFX780/iFX740 fitter, you will be able to write source files in the language
you are familiar with, and then compile JEDECs for any Intel programmable
logic device.  It even includes support for advanced architectural features
available on the iFX780/iFX740 which may not be describable using the
vendor's standard language.

All of this is accomplished through a seamless interface which is
transparent to the user.  The user can write standard  source files
in the vendor's native language and compile them into Intel devices
without ever leaving the environment of choice.




*** Installation ***

To install this version of the iFX780/iFX740 Open Fitter, insert the
diskette into drive A and type:

        a:\install <CR>

Then follow the on-screen instructions.  This installation routine copies 
the disk contents into the specified directory on your hard disk, 
uncompacts the files, and sets the required system variables.

If PLDshell Plus (TM) Design software has been installed previously, do not 
let the installation program modify your autoexec.bat file.  For example, 
select "N" when the installation program prompts the user:

        " May I create/modify the autoexec.bat file (Y/N) ? "

However, when the installation is complete, add the directory in which the
Open fitter was installed (usually c:\pldasm) to the PATH in your
autoexec.bat.  

If PLDshell Plus (TM) Design software has not been installed, you should 
let the install program make changes to your autoexec.bat.  All PATH 
modifications will be made automatically.



**************************************************************************
**************************************************************************

	The following section contains a list of problem that have been
fixed fixed in recent releases.


Problems fixed in iFX780 Open Fitter Kit V3.0.2:

A. Incorrect programming of preset and clear
   -----------------------------------------

   If a macrocell has both preset and clear equations, it is possible that the
   preset  and clear equations will be programmed incorrectly.  This only 
   happens if this macrocell is the first one in a CFB which has preset or
   clear.  If any of the prior macrocells has a preset or clear, the macrocell
   will be programmed correctly.  The problem will net be found by the user
   until the device is programmed and tested.


B. Incorrect programming of feedback path
   --------------------------------------

   The JEDEC for a design is incorrect when a macrocell uses the combinatorial
   feedback path from another macrocell  which has a low asserted output.  For
   example:

      PIN IN
      PIN OUT
      PIN OUT1   CMBFBK

      /OUT1 = IN
      OUT = OUT1

    The assertion of OUT will not be the same as OUT1 as the user desires.


C.  Synchronous clock getting changed to asynchronous clock
    -------------------------------------------------------

    When a clock equation is specified as synchronous, but the fitter promotes
    it to being asynchronous, the JEDEC file will be incorrect.  The fitter
    will try to assign the clock to a synchronous clock pin, even when the
    equation is driven by another pin or a p-term.


D.  Problem generating report file
    ------------------------------

    There are instances where the iFX780 fitter will abort during the 
    generation of the report file. The user will get a message about the 
    process aborting and the report file will be empty.  This is caused
    by some of the signal names being generated by the compiler.


E.  Incorrect conversion of Comparator term
    ---------------------------------------

    It is possible that the comparator for an equation could be logically
    incorrect after minimization.  If the output of the equation is inverted
    during demorganization or minimization, the comparator input is not 
    correctly changed to be logically equivalent.


Problems fixed in iFX780 Open Fitter Kit V3.0.1:

A.  Buried SRAMs
    ------------

    Buried SRAMS are not programmed into the JEDEC correctly.  The fitter
    states that the SRAM has been fitted and assembled correctly, but when 
    the actual device is tested, it acts like the SRAM does not exist.
    Also if the report file for the design is viewed, the SRAM definition
    section for this SRAM will have asterisks as pin assignments.  


B.  SRAM Names
    ----------

    SRAM names are no longer supported.  An SRAM must be specified as follows:

    PIN dout[0:9] RAM

    or 

    NODE dout[0:9] RAM

    rather than

    PIN dout[0:9] RAM sramout

    If the last form is used, the parser will generate the following message:

    ERROR E4330-PDSTODDB:  Misplaced statement(s) on line X at SRAMOUT.

    To fix the error, the word 'sramout' must be deleted.  Throughout the rest
    of the design, this RAM will be specified by using the name 'dout'.


C.  Registered Use of the SRAM
    --------------------------

    If you have specified that the SRAM use either Registered output or
    Registered feedback, the fitter will give a message stating that this is 
    not supported yet. 

    The use of Registered output and Feedback are supported. The message
    should read that simulation of this is not supported yet.


D.  SRAM Definition
    ---------------

    Define SRAM's with a single Pin statement such as 

        Pin dout[0:9]  ram  ; THIS WORKS

     currently defining a ram with multiple pin names does not work.

        pin dout[0]  ram    ; THIS DOES NOT WORK
        pin dout[1]  ram    ; THIS DOES NOT WORK


E. Outputs without equations
   -------------------------

   If you specify a pin in the pin list and do not specify an equation for
   that signal, the pin will be turned into an input pin.  There is no way to
   keep the pin as an output pin other than assigned an equation to the pin.


F. Fitter aborts when generating report file
   -----------------------------------------

   There are times when the fitter will abort when a report file is being
   generated.  This happens when there are long local signal names inside 
   modules with long names.  These signal names are too long for the report
   generator to handle.


G. VCC and GND cannot be used in compare equations
   -----------------------------------------------

   When VCC is used as an input to a compare equation, the fitter will
   abort. If GND is used as an input to a compare equation, the fitter will
   not program the JEDEC correctly for the GND input.


H. No error generated for illegal pin numbers
   ------------------------------------------

   If an illegal pin number is specified for a signal (i.e. IO9 rather than 
   IO09), the parser will not generate an error stating that this is an illegal
   pin number.  The fitter will then reassign the pin and it looks to the 
   user like the pin assignment was totally ignored.


I. OE inversion confusion
   ----------------------

   The fitter treats a single term OE and its inversion as the same, even
   though they have to take up two OE positions in the CFB.  The fitter will
   then tie both OEs to the same OE equation.  This causes the outputs to
   be enabled with the same OE assertion, rather than the opposites as 
   the user desires.


J. Incorrect feedback programming
   ------------------------------

   If you specify a output with pin feedback, the output will get programmed
   as internal feedback.


K. Incorrect programming for 14 p-terms
   ------------------------------------

   If all 14 p-terms are used in macrocell 0 of a CFB, the last 2 pterms will
   be programmed incorrectly.

-----------------------------------------------------------------------------

iFX780/iFX740 Open Fitter Kit and Memory Managers

   The iFX780/iFX740 Open Fitter Kit software takes advantage of the
   latest compiler and memory manager technology.  The generated code is
   targeted for the Intel 386 microprocessor family and makes use of its
   advanced instruction set.  Because of this, and the fact that the
   applications make exhaustive use of the memory manager, they are
   somewhat sensitive to hardware and software conflicts.

   While it would be impossible to test the software on every possible
   machine configuration, we have tested it on those that are most
   common.  Any problems encountered can usually be tracked down to a
   conflict of some sort.

-- Memory Managers

   Most of the executables in the package require Extended Memory and
   some sort of Memory Manager.  We have included a utility called
   MEMCHK.EXE; it can be used to quickly determine how much memory will
   be available to the software.  As a general rule, you should have
   about 2000K (2 megabytes) available, but more may be needed for
   larger designs.

         |  Note that a '2 Meg' machine will have only one     |
         |  megabyte of extended memory as the first megabyte  |
         |  is used for DOS and Upper Memory.  If you are      |
         |  working on designs that are in need of more memory |
         |  than your machine has, see the section below on    |
         |  Microsoft Windows 3.x                              |

   The memory manager included with Microsoft's MS-DOS 5.0, EMM386,
   provides adequate support if properly configured.  It also has
   the capability to provided Expanded Memory (EMS) emulation, but any
   memory used for EMS will not be usable by the iFX780/iFX740 Open
   Fitter Kit software which uses Extended Memory.  Please refer to
   your DOS manual for details on configuring EMM386.

   If you run programs that _must_ have Expanded Memory (EMS), you 
   may want to consider Quarterdeck's QEMM-386 v6.x.  In addition to
   providing excellent memory management, it provides for Expanded
   and Extended memory support within the same memory pool.
   
         |  There have been some problems on some machines     |
         |  with QEMM-386 and our software when the Stealth    |
         |  mode was being used.  Disable this feature if you  |
         |  are having any problems with the iFX780/iFX740     |
         |  Open Fitter Kit.                                        |

-- Microsoft Windows 3.x
   
   We, in general, do not recommend running the iFX780/iFX740 Open
   Fitter Kit software under Windows 3.x.
   
   If you are working on designs that are demanding more memory than
   available, try running the software from Windows in a DOS box.
   Windows provides virtual memory support to DOS applications, so it
   is possible to have much more extended memory available to programs
   than your machine physically has.  This feature has been tested on
   machines running DOS 5.0, QEMM-386, and Windows 3.1 (Enhanced Mode),
   but will likely work with other setups.

---------------------------------------------------------------------------


 A technical support Hotline is available every weekday from 8am to 5pm
 Pacific Daylight Time.  Please call the Hotline for further
 information on uPLD's or help with this software.  The Hotline is
 available only to U.S.  and Canadian users.  Outside the U.S.  and
 Canada, please contact your local Intel authorized sales office.

 A 24 hour modem-accessed bulletin board is available at (916)
 985-2308.  The purpose of the bulletin board is to provide up-to-date
 information pertinent to Intel uPLDs and development tools.




*FLEXlogic, PLDshell Plus and PLDasm are a trademarks of Intel, Corp.


**************************************************************************
**************************************************************************



 If you would like additional information on Intel's PLDs and Tools, order the 
 Programmable Logic Handbook (Lit. #296083). 
 
                    US and Canada   1-800-548-4725 

 For PLD customer support issues, US and Canada, call the Applications Hotline 
 between 8am and 5pm Pacific Daylight Time.

                       1-800-628-8686
 
 Outside the US, please call one of the following numbers for the Programmable 
 Logic Handbook (Lit. #296083) and customer support issues:
 
          EUROPE:  Contact your local Intel Distributor.
               Belgium                 Italy
               Finland                 Russia
               France                  Spain
               Germany                 Sweden
               Holland                 Switzerland
               Ireland                 United Kingdom
               Israel
     
          ASIA PACIFIC:
              Australia  -   61-2975-3300
              China, PRC -   861-500-4850
              Hong Kong  -   852-844-4555
              India      -   91-812-215065
              Korea      -   822-784-8186
              Singapore  -   652-507-811
              Taiwan     -   886-35-78
              Taiwan     -   886-35-78
        
          JAPAN:  81-29847-8522

 A 24 hour modem-accessed bulletin board is available at (916) 985-2308.  The 
 purpose of the bulletin board is to provide up-to-date information pertinent 
 to Intel uPLDs and development tools.

 PLDshell Plus is a software shell program that provides an easy to use
 environment for programmable logic device design and the PLDasm compiler/
 simulator to support our entire family of uPLD devices in a PALASM(R)2 
 compatible language syntax.  The following devices are supported:

         22V10              PLD610             PLD910
         85C220             85C508             5C060
         85C224             5AC312             5C090
         85C22V10           5AC324             5C180
         85C060             5C031              FX780
         85C090             5C032              FX740


 Additionally, PLDshell Plus supports a wide range of conversions from
 common 20 and 24 pin PAL (R) and GAL (R) devices. Refer to PLDshell's
 on-help for a listing of which device conversions are supported. 
 PLDshell Plus can provide either JEDEC conversion or direct compilation
 of PDS source into an Intel device.


 The main features of PLDshell Plus are:

    1) A supervisory, menu-driven "shell" for other PLD design tools.

    2) PALASM(R)2 compatible design language via the PLDasm compiler.

    3) Logic minimization via an ESPRESSO II-mv minimizer.

    4) Full unassigned pin and device fitting of the entire Intel uPLD
       family of devices. 

    5) Device conversion from common PAL(R)/GAL(R) devices into 
       Intel uPLD devices.

    6) Device independent design and simulation capability.

    7) Enhanced logic simulation via superset keywords.

    8) Graphical viewing/editing of simulation waveforms on
       VGA/EGA and Hercules monitors.

    9) Translation of ADF/SMF files into PDS format for iPLS II
       users.

   10) A design Merge capability, including modular and hierarchical
       design capabilities.

   11) A design Estimator that compares basic design requirements to
       a device database to narrow the choices of target devices.

   12) A utility program, MEMCHK.EXE, which when executed reports the
       total amount of memory available for PLDshell Plus' use.  When 
       memory problems are or have been experienced this program should 
       be run to help in diagnosing the problem.


