Date    : March 24, 1999
To      : Vantis/AMD MACH customers
Subject : README file for VantisPRO ver 3.00c

Thank you for selecting Vantis' programmable logic products. We are
excited to present the widest range of high-speed high-density CPLDs
with JTAG and in-system programming capabilities. You can now choose
from a 32-macrocell MACH111SP to the 512-macrocell MACH5-512.

This readme file contains:

  1 . Description of new features and fixes in VantisPRO/MACHPRO
  2 . Supported parts list (last update: 25 February 1999)
      a. Erasing/reinitializing the MACH4-32/32
  3 . Instructions for downloading VantisPRO updates from the Web
  4 . VantisPRO update installation instructions
      a. for Win 3.1, Win95/Win98
      b. for Win NT 4.0 (also for parallel port driver)
      c. for DOS version
  5 . Documentation and miscellaneous (demo) files
  6 . Part Naming Convention
  7 . Chain File compatibility between DOS and Windows versions
  8 . Using VantisPRO with Parallel Port Software Keys
  9 . Explanation of the "-j X -w" options in the DOS version of VantisPRO
 10 . Programming MACH CPLDs on ATE systems

To program these parts through their IEEE 1149.1 (JTAG) Test Access Ports,
Vantis has developed VantisPRO for DOS, Win 3.1, Win95/Win98 and Win NT 4.0.
The VantisPRO software and user manual can be found in the ZIP archive
MPRO_DSK.ZIP which is on our website www.vantis.com.

Along with the VantisPRO software, you will also need a programming cable
to connect to your parallel port. The other end of this cable is a 10-pin
connector which you use to send signals to the MACH CPLDs on your board.
The connector signals are described in the documentation in the ZIP file.
A schematic of the programming cable is provided in the VantisPRO webpage
so you can construct your own cable with your preferred connector, or you
can call your Vantis distributor for information on how to obtain one.

==================================================================

(1) New Features/Fixes:

Ver 3.00c (24 March 1999)
 = Modified scope looping window (enabled from Project | Advanced Options)
   to respond more quickly to mouse clicks.
Ver 3.00b (27 February 1999)
 = I/O boundary scan cell initialization function fixed to restore concurrent
   programming capability.
Ver 3.00a (31 January 1999)
 = VantisPRO(tm)/MACHPRO(tm) now supports long filenames w/ spaces (for
   Win95/98/NT)
Ver 3.00  (18 December 1998)
 = Program name change to VantisPRO(tm)
Ver 2.00p (23 November 1998)
 = Added SVF and ATE support code for the MACH4-32/32.
Ver 2.00o (13 November 1998)
 = Modifications to allow VF-1 pattern verify on NT systems.
Ver 2.00n (09 October 1998)
 = Modifications for VF-1 to allow normal device operation while performing
   a verify. Modified SVF_reset() so user can remove STATE RESET statement
   from the SVF file for JTAG test software like Asset Intertech.
Ver 2.00m (19 September 1998)
 = Modified command line version of code so that NT users can generate SVF
   and other ATE files even if the MPROPORT.SYS driver is not installed.
   Fixed VerMatrix() to read and print out a VF-1 pattern correctly.
Ver 2.00l (11 September 1998)
 = Fixed VF-1 JTAG-ISP routine: a buffer was not being deallocated after use
   and a variable was not initialized if there was only 1 device (a VF-1) in
   the chain. MACHPRO was also tested successfully on a Win98 system.
Ver 2.00j (28 August 1998)
 = Added field in Project | Options window for user to specify path for
   MACHPRO temp files. This will enable users to store chain files on a
   read-only drive and store results in a local drive.
Ver 2.00h (04 July 1998)
 = SVF file will now use the SVF spec rev D RUNTEST delay format as the
   default:

      RUNTEST 50.0E-3 SEC;    <== wait 50 ms in RUN-TEST-IDLE state
                                  independent of TCK frequency

   The previous delay format (SVF spec rev C and earlier) was:

      RUNTEST 50000 TCK;      <== 50 ms if TCK = 1 MHz

   You can still generate the previous (SVF spec rev C and earlier) format.
   In the Windows versions, click on PROJECT | ADVANCED OPTIONS, and then
   select the "Use RUNTEST format from SVF rev C and earlier". In the DOS
   version of MACHPRO, add 128K (ie., 131072) to the "-z X" parameter.
Ver 2.00g (17 June 1998)
 = Added M4_192/96 support. Also fixed some user-interface errors and
   the erase/reinitialize command processor.
Ver 2.00f (31 May 1998)
 = Support for MACH4-032/32 and MACH4-096/48. The code had to be modified
   because the MACH4-032/32 programming and verification algorithm was
   different from earlier MACH parts.
Ver 2.00d (23 December 1997)
 = Support for MACH4-064 type parts. The code had to be modified because
   the MACH4-064 programming and verification algorithm was different from
   the earlier MACH parts.
Ver 2.00c (14 November 1997)
 = Modified HP-PCF file generation: removed tabs and comments in the PCF file
   to reduce the file size. Windows version now has PCF variable editing
   capability.
Ver 2.00b (30 October 1997)
 = Fixed SVF file generation for MACH1xxSP and MACH2xxSP parts.
 = Added feature to turn off JTAG reset operation so that some customers
   can program MACH parts in systems using JTAG scan bridges.
Ver 2.00a (24 September 1997)
 = Modified ATE vector generation option in PROJECT | OPTIONS window so
   that you can now choose between generating programming and verification
   vectors or just programming vectors. Also corrected the way HP-PCF tester
   vectors are counted.
Ver 2.00 (20 September 1997)
 = Added file partitioning capability to HP Pattern Capture Format (PCF)
   generation. When MACHPRO ver 2.00 is instructed to generate HP-PCF
   vectors to program MACH CPLDs, users can specify the maximum number of
   vectors to write per file. The additional vectors will be written to
   files with the names (xxxxxxxx.AMD). Previous versions of MACHPRO wrote
   all the vectors into a single file, and users had to use the automatic
   partition generator program (APG.BAS).
Ver 1.40h (08 August 1997)
 = Win NT 4.0 version completed. See Win NT installation section.
Ver 1.40h (10 July 1997)
 = Added I/O vector editing capabilities to Win 3.1 and Win95 versions.
   DOS users can use a text editor to create an I/O vector as described
   in the MACHPRO documentation (see MISC directory in MPRO_DSK.ZIP).
 = Modified "Read JEDEC" operation so that it displays the checksum on
   screen after reading the device contents. If the device has don't
   care bits, then this checksum computation will be done with the
   don't care bits set to 1.
 = Added a debugging feature in the Project | Advanced Options menu. When
   this option is selected, MACHPRO will put all the devices in a chain
   into BYPASS mode, and then generate a continuous square wave through
   the TDI line. Use this to check serial JTAG TDI-TDO chain integrity.
Ver 1.40g (05 May 1997)
 = Added alternate parallel port pin mapping option so that customers
   can use a different programming cable.
Ver 1.40f
 = Fixes warning message "Could not remove file xxxx" if a nonexistent
   JEDEC or output filename is specified (Win95)
 = Generates correct ATE tester vectors even if MACH5xx JEDEC maps do not
   have all the don't care bits correctly specified.
Ver 1.40e
 = Windows versions have FOR loop optimizations turned off so that timing
   (for programming and erasing) will be more accurate across different PCs.
Ver 1.40d
 = Fixed SaveAs function in WMPRO95.EXE. Previous versions would always
   append the ".WCH" option to the user-specified filename.
Ver 1.40c
 = Fixed SVF-generation errors in the Windows 3.1 and Win95 versions
   caused by not reinitializing some global variables.
Ver 1.40b
 = Generates correct ATE programming and pattern verification
   vectors for ATE systems.
 = Initializes IO pins to the user-selected state when performing
   a pattern verify operation.
 = Issues a warning instead of crashing when trying to program
   a non-existent security fuse in a device (e.g., security fuse
   2 in a MACH231SP).
Ver 1.40
 = Now generates the correct ATE code for programming
   and verifying the user-programmable USERCODE.

==================================================================

(2) Supported Parts List

The following MACH parts are supported by this version (refer to
section 6 in this README file for the part naming convention):

  - MACH111SP    - MACH355    - MACH465      - M4_032/032  M4A_032/32
  - MACH131SP                 - MACH466      - M4_064/032
  - MACH211SP    - MACH445    - MACHLV466    - M4_096/048
  - MACH221SP    - MACH446                   - M4_128/064  M4A_128/064
  - MACH231SP    - MACHLV446                 - M4_192/096
                                             - M4_256/128  M4A_256/128

  - MACH5-128 /  68 IO (PQFP/TQFP), 104 IO, 120 IO
  - MACH5LV-128
      =   68 I/O in 100-pin PQFP and TQFP
      =   74 I/O in 100-pin TQFP
      =  104 I/O in 144-pin PQFP and TQFP
      =  120 I/O in 160 PQFP

  - MACH5-192 /  68 IO (PQFP/TQFP), 104 IO, 120 IO, 160 IO
  - MACH5-256 /  68 IO (PQFP/TQFP), 104 IO, 120 IO, 160 IO
  - MACH5LV-256
      =   68 I/O in 100-pin PQFP and TQFP
      =  104 I/O in 144-pin PQFP and TQFP
      =  120 I/O in 160 PQFP
      =  160 I/O in 208-pin PQFP

  - MACH5-320 / 120 IO , 160 IO , 184 IO, 192 IO (3.3v and 5.0v versions)
  - MACH5-384 / 120 IO , 160 IO , 184 IO         (3.3v and 5.0v versions)
  - MACH5-512 / 120 IO , 160 IO , 184 IO         (3.3v and 5.0v versions)

For VantisPRO Win 3.1 and Win95/Win98, click on the JTAG PART pull-down
menu to see a complete list of supported parts. For more information on
using the software, please refer to the VantisPRO documentation.

(2a) Erasing/reinitializing the MACH4-32/32

The MACH4-32/32 (3.3v and 5.0v versions) cannot be erased/reinitialized
using the 'E' command in VantisPRO, but you can accomplish the same thing
by programming ('P' operation) the device with the initialization JEDEC
maps called M4_32xx.J_0 (e.g., xx = P5 for the 5v 44-pin PLCC device).
See section 6 in this README file for the complete list of MACH4-32/32
part names. These JEDEC maps are included in the same directory as the
other data files (.JDF and .BSM). Programming a MACH4-32/32 device with
this JEDEC map will tristate the I/O pins.

Note that the M4A-032/32 is a new die which can be erased/reinitialized
using the regular 'E' command in VantisPRO.

==================================================================

(3) Download Instructions (for Updates):

If you have the VantisPRO program on CD, then go directly to the
VantisPRO installation instructions for the operating system
being used.

To get VantisPRO updates from the Vantis webpage, use your Internet
browser to download the files MPRO_DSK.ZIP and JTAGPART.ZIP to a new
directory in your hard drive. MPRO_DSK.ZIP contains the EXE files and
documentation in Word format. JTAGPART.ZIP contains the programming
algorithm files (*.JDF) and the Boundary Scan Description Language
(*.BSM) files used by VantisPRO to program the MACH CPLDs.

Use PKUNZIP (2.04g) with the following command line options when
unarchiving the ZIP file:

   C:\NEW_DIR> pkunzip -d mpro_dsk

This will recreate the directory structure of the VantisPRO master
program disk.

==================================================================

(4a) Installation Instructions for Windows 3.1 and Win95/Win98 versions
     (Updates only):

To install the Windows (3.1 or Win95/Win98) version of VantisPRO, go to
the WIN_MPRO directory and run the Windows SETUP program.

For example:

   You copied MPRO_DSK.ZIP into a directory on your hard drive
   called NEW_DIR and you have run the PKUNZIP program as described
   in section (3). Type the following and the setup program will
   guide you through the rest of the installation process.

      C:\> cd \NEW_DIR\win_mpro
      C:\NEW_DIR\WIN_MPRO> win setup

You will be prompted to select either the Win 3.1, Win95/Win98, or
Win NT 4.0 version, and also for a subdirectory name to install the
VantisPRO program in.

After the installation process has completed, copy the JTAGPART.ZIP file
to the directory where you just installed VantisPRO, and unzip all the files
into this directory.

==================================================================

(4b) Installation Instructions for Windows NT 4.0 version (Updates only):

Follow the instructions in the previous section (4a) to install VantisPRO
for Win NT 4.0. After installing the VantisPRO NT binary and device
datafiles, install the VantisPRO parallel port driver. VantisPRO will
use this kernel-mode driver to communicate with the parallel port on
your NT system.

- You must have administrator-level privileges to install the device driver
- Open a DOS box or command line window in NT and run the MDRVINST.EXE
  program to install the VantisPRO parallel port driver. MDRVINST.EXE and
  the driver file MPROPORT.SYS can be found in the subdirectory where you
  just installed VantisPRO for Windows NT (WMPRONT.EXE) using the SETUP
  program.

  Example: If VantisPRO for NT (WMPRONT.EXE) was installed into the
           directory c:\WMACHPRO, then MDRVINST.EXE and MPROPORT.SYS
           will also be in this directory.

  To install the driver, go to the directory where MDRVINST.EXE is located
  and run the program with the following command line options:

    C:\wmachpro> MDRVINST mproport c:\wmachpro\mproport.sys

  Make sure you specify the driver file path correctly.

- After installing the driver, reboot/restart your system.

The driver is configured to automatically start every time you boot
your system. If you run VantisPRO NT and you get the message:

   "MPROLPTx|LPTx or driver may not be installed"

then you can set the NT Service Control Manager to start the driver
automatically by:

1. Starting the Control Panel
2. Double-clicking on Devices
3. Scrolling down to MPROPORT; click once on MPROPORT to select it
4. Click on START-UP and select AUTOMATIC

Close the Control Panel and reboot. MPROPORT.SYS will now start every
time you reboot/restart your system.

If you are experiencing problems w/ the MPROPORT driver, check the 
following:

1. Go to the START button, select SETTINGS, and then Control Panel.
2. Click on DEVICES, and look for MPROPORT in the scroll list
   = if the driver was installed correctly, it should read
           MPROPORT   Started  Automatic
   = if you do not see this, then check the registry

To check the registry (please be very careful when doing this
because it may affect your NT system setup):

1. Open a DOS command window
2. Type REGEDT32
3. Go to the HKEY_LOCAL_MACHINE window and click on:
   = SYSTEM, then
   = CurrentControlSet, then
   = Service, then
   = click on MPROPORT
4. On the right side of the same window, you should see
   driver information that will look similar to this:

   DependOnGroup:REG_MULTI_SZ:Parallel Arbitrator
   DependOnService:REG_MULTI_SZ:Parport
   DisplayName:REG_SZ:mproport
   ErrorControl:REG_DWORD:0x1
   Group:REG_SZ:Extended base
   ImagePath:REG_EXPAND_SZ:\??\c:\wmachpro\mproport.sys
   Start:REG_DWORD:0x2
   Tag:REG_DWORD:0x6
   Type:REG_DWORD:0x1

Things to check:

1. The ImagePath string tells the NT OS where to get the driver.
   Please check that the MPROPORT.SYS driver file is actually in
   this directory.
2. If MPROPORT.SYS is not in this directory, then you can do
   two things:
      a. Copy MPROPORT.SYS to the directory path defined by
         the ImagePath, or
      b. Change the name in the ImagePath directory
         = to do this, double click on the ImagePath
           name, and an edit window will appear
         = specify the directory name and make sure to leave 
           the "\??\" at the beginning of the directory name

If you are changing the ImagePath name, I recommend first putting
the MPROPORT.SYS file in the NT driver directory. This is usually
in C:\winNT\system32\drivers. After you put MPROPORT.SYS into this
directory, change the ImagePath directory string to this directory,
and then reboot/restart your system.

==================================================================

(4c) Installation Instructions (DOS ver 5.0 and later):

To install the updates of MACHPRO for DOS, switch to the DOS_MPRO directory
(e.g., cd \NEW_DIR\DOS_MPRO) and type:

  C:\NEW_DIR\DOS_MPRO> pkunzip -n mpro_dos

Please read the READ.ME file in the DOS_MPRO subdirectory for more
information on completing the installation.

After the installation process has completed, copy the JTAGPART.ZIP file
to the directory where you just installed MACHPRO, and unzip all the files
into this directory.

==================================================================

(5) Documentation and Miscellaneous (demo) files

Documentation is in a ZIP file called DOCUMENT.ZIP in the MPRO_DSK.ZIP
archive which contains the following files in WinWord 2.0 format:

  - CABLESPE.DOC = MACHPRO programming cable spec. The information in
                   this file will enable you to build your own programming
                   cable.
  - WINMPRO.DOC  = VantisPRO documentation (for DOS and Windows 3.1 version)
                   in WinWord format.

If you have access to a MACH231 demo board, then two MACH231sp design
example files are in the directory DEMO_BRD.231.

If you have access to a MACH445 demo board, then MACH445 sample design
files can be found in the directory DEMO_BRD.445.

If you received a 44-pin PLCC programming board, then MACH211SP sample
design files can be found in the directory DEMO_211.

==================================================================

(6) Part Naming Convention

To maintain compatibility with 8.3 character DOS filenames, use the
following part names when you create a chain file (see VantisPRO
documentation for more details on creating the chain file).

For the MACH1xx to MACH4xx parts:

   Name on Device       Name to be used
      Package         VantisPRO chain file
--------------------------+------------------------
         MACH111sp        |      MACH111i
--------------------------+------------------------
         MACH131sp        |      MACH131i
--------------------------+------------------------
         MACH211sp        |      MACH211i
--------------------------+------------------------
         MACH221sp        |      MACH221i
--------------------------+------------------------
         MACH231sp        |      MACH231i
--------------------------+------------------------
         MACH355          |      MACH355
--------------------------+------------------------
         MACH445          |      MACH445
--------------------------+------------------------
         MACH446          |      MACH446
--------------------------+------------------------
         MACHLV446        |      MACHL446
--------------------------+------------------------
         MACH465          |      MACH465
--------------------------+------------------------
         MACH466          |      MACH466
--------------------------+------------------------
         MACHLV466        |      MACHL466
--------------------------+------------------------
 M4_32/32     44-pin PLCC |      M4_032P5
--------------------------+------------------------
 M4LV_32/32   44-pin PLCC |      M4_032PL
--------------------------+------------------------
 M4_32/32     44-pin TQFP |      M4_032T5
--------------------------+------------------------
 M4LV_32/32   44-pin TQFP |      M4_032TL
--------------------------+------------------------
 M4_32/32     48-pin TQFP |      M4_32T8
--------------------------+------------------------
 M4LV_32/32   48-pin TQFP |      M4_32T8L
--------------------------+------------------------
 M4_64/32     44-pin PLCC |      M4_064P5
--------------------------+------------------------
 M4LV_64/32   44-pin PLCC |      M4_064PL
--------------------------+------------------------
 M4_64/32     44-pin TQFP |      M4_064T5
--------------------------+------------------------
 M4LV_64/32   44-pin TQFP |      M4_064TL
--------------------------+------------------------
 M4_64/32     48-pin TQFP |      M4_64T8
--------------------------+------------------------
 M4LV_64/32   48-pin TQFP |      M4_64T8L
--------------------------+------------------------
 M4_96/48    100-pin TQFP |      M4_96T5
--------------------------+------------------------
 M4LV_96/48  100-pin TQFP |      M4_96TL
--------------------------+------------------------
 M4_192/96   144-pin TQFP |      M4_192T5
--------------------------+------------------------
 M4LV_192/96 144-pin TQFP |      M4_192Tl
--------------------------+------------------------
         M4_128/100 PQFP  |      M4_128A  (Note 1)
--------------------------+------------------------
         M4_128 LV        |      M4_128AL (Note 2)
--------------------------+------------------------
         M4_256/208 PQFP  |      M4_256B  (Note 3)
--------------------------+------------------------
         M4_256 LV        |      M4_256BL (Note 4)
--------------------------+------------------------
Notes:
  1. New name for MACH446
  2. New name for MACHLV446
  3. New name for MACH466
  4. New name for MACHLV466

For the MACH5xx parts, the following naming convention is used:

   MVPxxxzw

  where: xxx = number of macrocells (eg., 512 for 512 macrocell device)

            z = package code
                  a =  84-pin PLCC
                  b = 100-pin PQFP (for parts w/  68 I/Os)
                  c = 208-pin PQFP (for parts w/ 160 I/Os)
                  d = 100-pin TQFP (for parts w/  68 I/Os)
                  e = 144-pin PQFP (for parts w/ 104 I/Os)
                  f = 160-pin PQFP (for parts w/ 120 I/Os)
                  g = 240-pin PQFP (for parts w/ 184 I/Os)
                  h = 256-pin BGA  (for parts w/ 192 I/Os)
                  j = 352-pin BGA  (for parts w/ 256 I/Os)
                  k = 100-pin TQFP (for parts w/  74 I/Os)
                  n = 144-pin TQFP (for parts w/ 104 I/Os)

            w = product size
                  6 = for MACH5-128/192/256
                  7 = for MACH5-320/384/512
                  L = 3.3 v version

  Example: MVP512CL = MACH5-512 208-pin PQFP 3.3v version

Use this reference guide when adding parts to chain files for the DOS
version of VantisPRO. When using the Windows version of VantisPRO, you can
select the device names from a parts list in a pull-down menu.

==================================================================

(7) Chain file compatibility between DOS and Windows versions:

A JTAG chain file created for the DOS version of VantisPRO can be read by
the Windows version by specifying the full chain filename in the FILE
OPEN command. You can also instruct the Windows version of VantisPRO to
create a chain file readable by the DOS version. To do this, save the
chain information to a file with a .CHN file extension.

==================================================================

(8) VantisPRO and Parallel Port Software Keys (for MACH3xx/4xx):

This version of VantisPRO with the new cable (parallel port connector housing
is green with the label "Rev 2.0") is designed to work with software keys
attached to the parallel port only if you do not use the TRST pin on the
MACH3xx/4xx.

If you use TRST, then you have to remove the parallel port software key
and add the "-j 0" option to the DOS VantisPRO command line. In the Windows
version, remove the software key from the parallel port and click on
PROJECT, then OPTIONS, and then click on the "Software key present" box
to deselect it.

==================================================================

(9) Explanation of the "-j X -w" options in the DOS version of VantisPRO

If a software key is attached to your parallel port, then the key must be
put into transparent mode (by pulsing the parallel port STROBE pin) to
allow transmission and reception of signals to and from the JTAG chain
through the programming cable and parallel port. To pulse the strobe line,
use the "-j X" command line option in the DOS version of VantisPRO.

This option will hold the parallel port STROBE pin LOW for X processor
cycles, HIGH for X processor cycles, and then bring STROBE LOW again for
X processor cycles. X can be an integer from 0 to 32767. If X = 0, then
STROBE pulsing is turned off. In the Windows version of VantisPRO, specify
the strobe pulse width by selecting "Any key attached to parallel port"
in the PROJECT | OPTIONS menu, and specifying a value in the PROJECT |
Advanced Options menu.

Note that the parallel port STROBE line is used by VantisPRO as the TRST(L)
line. This means that if you are connecting this line on the programming
cable to a JTAG device with a TRST(L) pin, then you have to remove any
software keys from your parallel port (so that the programming cable is
attached directly to the port), and turn off STROBE pulsing by using
the option "-j 0".

In certain board designs, the TDO of the last JTAG device in the chain must
be given more time to settle at the parallel port before VantisPRO samples it.
This may occur if the signal is not buffered (e.g., by a 74LS244) and the
trace from the TDO of the last device to the JTAG connector is long ( > 1
foot). The additional settling time for an unbuffered TDO may be needed
because the TDO signal also has to drive the 6 foot long programming cable
to get back to the parallel port.

To increase the amount of time for a signal to settle before sampling, use
the "-w" option with the "-j X" option. For example, if you add the option
string "-j 50 -w" to the VantisPRO command line, then VantisPRO will turn off
strobe pulsing and use the value 50 as the number of processor cycles to
hold TCK (not STROBE/TRST) LOW, then another 50 processor cycles HIGH, then
50 cycles LOW again before sampling. If you specify X = 0, then VantisPRO will
generate a LOW-HIGH-LOW waveform on TCK as fast as it can and samples TDO as
soon as TCK goes LOW. To control the TDO sampling point in the Windows
version of VantisPRO, deselect the option "Any key attached to parallel port"
in Project | Options and specify the sampling delay time in the PROJECT |
Advanced Options menu."

==================================================================

(10) Programming MACH CPLDs on ATE systems

Appnotes are available on www.vantis.com for users who want to program
MACH JTAG-ISP devices on ATE systems from GenRad, HP, and Teradyne.

For HP 3070 Users:

When generating HP-PCF vectors, MACHPRO ver 2.00+ now lets the user specify
the maximum number of vectors to write per file. For example: If it takes
400K vectors to program and verify a MACH part, and if the user specifies
a maximum of 150K vectors per file, then MACHPRO 2.00+ will write the first
150K vectors to the specified PCF output file, then the next 150K will go
into the file 00000001.AMD, followed by the last 100K into the file
00000002.AMD. The HP tester engineer then compiles each of these tester
programs separately, and then runs them in sequence (as specified by their
filenames).

Users of earlier versions of MACHPRO can continue to use the automatic
partition generator program (APG.BAS) on the Vantis website (www.vantis.com)
to automatically partition a single MACHPRO-generated HP-PCF file into more
manageable test programs. For more information on this process please
refer to the application note on our website entitled:

  "In-System Programming on an HP3070 through the MACH
   CPLD 1149.1 Test Access Port"

============== end of README =====================================

