PROMlink Help File Version 6.1 ~0000 \bMAIN SCREEN\b Press \bAlt\b+\bhighlighted letter key\b or click the mouse on the menu title to select the desired menu. \bS\betup Select device, programming parameters \bD\bata Load master, transfer data, edit RAM \bP\brogram Program/test devices \bT\basks Load, edit, add or remove Tasks \bU\btilities Terminal emulation, device update \bO\bptions Programmer, serial port, display, etc. E\bx\bit Exit PROMlink-6, DOS shell \bH\belp Help for help, indexed help topics The System Status display contains the following items: \s1ATask\q The name of the currently-loaded Task. If no Task has been loaded or any parameters have been changed since the last Task was loaded, this line will be blank. \s1AData\q The source of the data currently in programmer RAM. \s1ASource\q May be the name of a disk file, "Master Device" or "Host Download". If PROMlink does not know where the data in RAM came from, this line will contain a "?". \s1ASumcheck\q The sumcheck of the data in programmer RAM. The sumcheck is normally the sumcheck of RAM from the beginning of RAM to the end of the data that will fit into the selected device. If the Set Size is greater than one, the sumcheck will be the sum of the sumchecks of each device in the set. If PROMlink-6 has not yet calculated the RAM sumcheck this field will contain a "?". \s1ADevice\q The name of the currently-selected device. The Data I/O family/pinout code for the device will be displayed if the "Display Family/Pinout Code with Device Name" option is enabled in the Set Preferences option of the Options menu. \s1AProcess\q The currently-selected "process", which is the combination of operations that will be performed on the device if the "Process Devices" option is selected. \s1ANotes\q Any miscellaneous information about PROMlink-6 status. The first line always shows whether all programming parameters are set to default values or not. The second line changes depending on what PROMlink-6 is doing. ~0010 NOINDEX \b< OK >\b Selecting < OK > accepts the currently displayed values and exits the dialog box. ~0011 NOINDEX \b< Cancel >\b Selecting < CANCEL > exits the dialog box without saving any changes made. ~0012 NOINDEX \b< Exit >\b Selecting < EXIT > exits the dialog box. ~0013 NOINDEX \b< Save >\b Selecting < Save > saves the contents of the dialog box to the associated file and exits the dialog box. ~0020 \bSETUP MENU\b The Setup menu contains programming/testing options. Options found in the Setup menu are: \bþ\b Select Device \bþ\b Select Process \bþ\b Select device programming parameters: General Parameters Memory Parameters Logic Parameters \bþ\b Session Data Logging \bþ\b Exit PROMlink-6 ~0021 \bSELECT DEVICE\b Use the Select Device option to specify the target device. You can enter the manufacturer and device name (standard DOS wildcards can be used), any Data I/O family and pinout code, or select the manufacturer and device name from lists. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ \s1ATyped in\q ³ \s1AResult\q ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ \bINTEL 27128\b ³ Selects device INTEL 27128 (if found) and ³ ³ ³ exits dialog ³ ³ ³ ³ ³ \bAMD\b ³ Lists all AMD devices ³ ³ ³ ³ ³ \bTI *16L8*\b ³ Lists all TI devices with "16L8" in name ³ ³ ³ ³ ³ ³ ³ ³ \b* *27?512*\b ³ Lists all devices with "27" followed by ³ ³ ³ any character and "512" in the name ³ ³ ³ ³ ³ \bM\b ³ Lists all manufacturers starting with "M" ³ ³ ³ ³ ³ \bF/P 9717\b ³ Select device using Data I/O ³ ³ ³ family and pinout code 9717 ³ ³ ³ ³ ³ \bEXTENDED_ALG\b ³ Lists extended (ALG.EXT) algorithms ³ ³ ³ (UniSite, 2900 and 3900 only) ³ ³ ³ ³ ³ \bKEEP_CURRENT\b ³ Lists Keep Current(TM) algorithms ³ ³ ³ (UniSite, 2900 and 3900 only) ³ ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ When you select < Manufacturer > from the Select Device dialog box, a list of manufacturers appears. When you select a manufacturer, a list of devices made by that manufacturer appears. When you select one of those devices, PROMlink selects the device and exits the dialog box. Family and pinout codes can have 4 or 6 digits. You can also develop a Custom Device File to select programmable devices by names you assign to them. For details, select Custom Device File from the General Help Index in the Help menu. ~0022 \bSELECT PROCESS\b Use the Select Process option to select the operations to be performed on the target device. The process options include: \bþ\b Blank check \bþ\b Illegal bit check \bþ\b Program \bþ\b Verify The Select Process dialog box contains a check box for each of these operations. An X in the check box indicates that the operation is selected. PROMlink automatically performs a verify operation whenever a program operation is performed. You cannot select the Program operation without selecting the Verify operation. ~0023 \bGENERAL PARAMETERS\b Use the General Parameters option to set various programming parameters. These options apply to memory, microprocessor, and programmable logic devices. General Parameters include: \bþ\b Number of verify passes \bþ\b Security option \bþ\b Continuity checking \bþ\b Electronic I.D. checking ~0024 \bMEMORY PARAMETERS\b Use the Memory Parameters option to set various programming parameters for memory and microprocessor devices. Memory Parameters include: \bþ\b Set size \bþ\b Word width \bþ\b Operation boundaries (begin RAM, block size, etc.) The Memory Parameters settings have no effect when the target device is a programmable logic device. ~0025 \bLOGIC PARAMETERS\b Use the Logic Parameters option to set various programming parameters for programmable logic devices. Logic Parameters include: \bþ\b Test mode (fuse and/or vector verification) \bþ\b Vector testing options The Logic Parameters settings have no effect when the target device is a memory or microprocessor device. ~0028 \bSESSION DATA LOGGING\b Use the Session Data Logging option to enable or disable the logging of the programming/testing session data (date, time, yield tally) to a disk file. For session data logging to occur, Session Data Logging must be enabled and a log file must be specified. For information on the format of the session data log file, select Log File Format from the General Help Index in the Help menu. ~0029 \bLOG FILE\b Use the Log File entry field to specify the disk file to write session data (date, time, yield tally) at the end of a programming/testing session. To access a file selection dialog box, use the \bTab\b or \bShift\b+\bTab\b keys to position the cursor in the entry field and press \bF2\b. You can select an existing log file or enter the name of a new log file. Log files must have a \b.log\b extension. You must enable Session Data Logging and specify a log file to use this feature. Select Log File Format from General Help for information on the session data log file format. ~0030 \bEXIT PROMlink\b Use the Exit PROMlink option to exit PROMlink-6 and return to DOS. ~0031 \bRESTORE DEFAULTS\b Use the Restore Defaults option to set all programming parameters to their default values. ~0040 \bDATA MENU\b The Data menu contains options for downloading data to, or modifying data in, programmer RAM. The Data menu options include: \bþ\b Load RAM from Master \bþ\b Load RAM from File \bþ\b Create File from RAM \bþ\b Load RAM from Host \bþ\b I/O Format \bþ\b View/Edit RAM \bþ\b Fill RAM ~0041 \bLOAD RAM FROM MASTER\b Use the Load RAM from Master option to load programmer RAM from a master device. When the master device is a logic device, all data in the device is loaded. When the master device is a memory device, the following Memory Parameters affect the loading of master device data: \bþ\b Begin RAM \bþ\b Begin Device \bþ\b Device Block ~0042 \bLOAD RAM FROM FILE\b Use the Load RAM from File option to load programmer RAM from a file. The Load RAM from File dialog box contains two entry fields. \bþ\b Data File \bþ\b I/O Format When the cursor is in either field, press \bF2\b (or use the mouse to click on the down arrow to the right of the field or to double-click anywhere in the field) for a list of choices. When the target device is a logic device, all data in the file is loaded. When the target device is a memory device, the following Memory Parameters affect the amount and location of file data loaded: \bþ\b I/O Offset \bþ\b I/O Block \bþ\b Begin RAM You can load file data to the UniSite, 2900 and 3900 programmers at high speed (115.2K baud) when the data is stored in the following formats. (10) Binary (95) Motorola 32-bit (16) Absolute Binary (83) Intel INTELLEC (82) Motorola EXORciser (88) Intel MCS-86 (87) Motorola EXORMAX (99) Intel Hex-32 High-speed transfer is automatically used when I/O Format in the Data menu is set to one of the above. ~0043 \bCREATE FILE FROM RAM\b Use the Create File from RAM option to copy programmer RAM to a file in the selected I/O format. The Create File from RAM dialog box contains two entry fields: \bþ\b Data File \bþ\b I/O Format When the cursor is in either field, press \bF2\b (or click the mouse on the down arrow to the right of the field or double-click anywhere in the field) for a submenu of choices. If the specified file already exists, you are asked if you want to overwrite the existing file. When the target device is a logic device, all programmer RAM data is copied to the file. When the target device is a memory device, the following Memory Parameters affect the amount and location of programmer RAM data copied to the file: \bþ\b I/O Offset \bþ\b I/O Block \bþ\b Begin RAM ~0044 \bLOAD RAM FROM HOST\b Use the Load RAM from Host option to transfer data from a host (remote computer) and load it to programmer RAM. To use the Load RAM from Host option, connect your host to a serial port (Host Port) on your PC. The Host Port baud rate does not have to match the baud rate of the Programmer Port. You may need to run a terminal emulation program on the Host Port to set up the host for sending data. You can select VT100 on Host Port from the Options menu to invoke the internal VT100 emulator on the Host Port or you can run an external program from DOS (your own terminal emulator). You can define a Task to automatically start the Host Terminal Emulator before beginning the host download. \s1ANote:\q For the host download feature to work, the host must respond to the XON/XOFF handshaking protocol. The host must suspend transmission upon receipt of the XOFF character (hex 13) and resume transmission upon receipt of the XON character (hex 11). When you select the Load RAM from Host option, you are prompted for an optional Host Command: a string of characters that will be sent to the host to start the transmission of data. For example, if you enter a Host Command of "cat filename.ext," the host sends the data after it receives that command. When the target device is a logic device, all host data is loaded to programmer RAM. When the target device is a memory device, the following Memory Parameters affect the amount and location of host data loaded to programmer RAM: \bþ\b I/O Offset \bþ\b I/O Block \bþ\b Begin RAM ~0045 \bI/O FORMAT\b Use the I/O Format option to set the translation format for transferring data to and from the programmer. With the UniSite/2900/3900 programmers, high-speed (115.2 Kbaud) transfer is automatically used when I/O Format is set to one of the following. (10) Binary (95) Motorola 32-bit (16) Absolute Binary (83) Intel INTELLEC (82) Motorola EXORciser (88) Intel MCS-86 (87) Motorola EXORMAX (99) Intel Hex-32 ~0046 \bVIEW/EDIT RAM\b Use the View/Edit RAM option to view and edit programmer RAM. The View/Edit RAM option works differently with each programmer. \s1BUniSite, 2900, 3900 and 29B with LogicPak\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For these programmers, PROMlink-6 uses its terminal emulator to run the programmer's internal menu system. This provides the fastest, most powerful editing capability. To use this feature with UniSite/2900/3900, set the User Menu Port parameter (accessible from the UniSite terminal interface) to "Remote". See "Establishing Communication" in the General Help Index for more information on configuring these programmers for use with PROMlink-6. \s1BSeries 1000, Model 212 (Memory Devices), Model 288 and\q \s1B29B with UniPak\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Since these programmers do not have an accessible internal editor, PROMlink-6 provides a simple screen-oriented byte editor. Use this editor to page through programmer RAM or jump to a specific RAM address. Programmer RAM can be changed by entering new data in either hexadecimal or ASCII-character formats. \s1BModel 212 (Logic Devices)\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The Model 212 has a built-in logic data editor, but it is not available in Computer Remote Control. When you select the View/Edit RAM option, a message box will appear asking you to select the "Terminal Control" option from the 212 front panel. When you have done this, select < OK > in the message box and the 212's Terminal Control menu will appear on the PC screen. After you have edited RAM using the Terminal Control menu commands, press \bAlt\b+\bF1\b" to exit. A message box will appear asking you to select "Computer Control" from the 212 front panel. When you have done this, select < OK > in the message box to return to normal PROMlink-6 control. ~0047 \bFILL RAM\b Use the Fill RAM option to fill an area of programmer RAM with a data byte. The Fill RAM option works differently with each programmer. \s1BUniSite, 2900, 3900 and Series 1000\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The Fill RAM dialog box has three hexadecimal entry fields: Begin Address Specifies the first location in RAM to be filled. Block Size Specifies how many bytes will be filled. Fill Data The value of the data byte to be written to RAM. Use the \bTab\b key to move between the fields, enter the desired values, then press \bEnter\b (or click on < OK > with the mouse) to begin the fill operation. \s1ANote:\q On the S1000, the block size filled will be in "words" as defined by the Word Size parameter. The Begin Address is in bytes. \s1B200 Series\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The Fill RAM dialog box has one hexadecimal entry field: \bþ\b Fill Data Fill Data is the value of the data byte to be written to RAM. Enter the desired value then press \bEnter\b (or click on < OK > with the mouse) to begin the fill operation. \s1B29B with UniPak or LogicPak\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Select Clear RAM to fill all of programmer RAM with zeros. ~0048 \bSPLIT RAM DATA\b Use the Split RAM Data option to split a block of 16-bit-wide word data into two 8-bit-wide blocks around the specified RAM midpoint. Then you can program the data into two 8-bit-wide devices. The Split RAM Data option places even-addressed bytes into consecutive addresses starting at address 0, and places odd-addressed bytes into consecutive addresses starting at the specified RAM midpoint. This splits the data into two adjacent blocks occupying the same original block of RAM. The RAM Midpoint must be a power of two between 2 and the midpoint of installed programmer RAM. ~0049 \bSHUFFLE RAM DATA\b Use the Shuffle RAM Data option to merge two adjacent blocks of 8-bit-wide data into one block of 16-bit-wide data occupying the same original block of RAM. The Shuffle RAM Data option places the data bytes below the specified RAM Midpoint in even-numbered addresses starting with address 0, and places data bytes from the RAM Midpoint and higher in odd-numbered addresses starting with address 1. The RAM Midpoint must be a power of two between 2 and the midpoint of installed programmer RAM. ~0050 \bFILL FUSE MAP\b Use the Fill Fuse Map option to fill the entire array of the selected logic device with a specified fuse state (0 or 1). "0" represents an unprogrammed state and "1" represents a programmed state. ~0060 \bPROGRAM MENU\b The Program menu contains options for performing device operations together or individually. These operations include illegal bit check, blank check, verify and functional test. Program menu options include: \bþ\b Process Devices \bþ\b Select Process \bþ\b Blank Check Only \bþ\b Illegal Bit Check Only \bþ\b Program/Verify Only \bþ\b Verify Only ~0061 \bPROCESS DEVICES\b Use the Process Devices option to run the programming operations defined in the Select Process option of the Program menu. ~0062 \bSELECT PROCESS\b Use the Select Process option to define the programming operations run by selecting Process Devices from the Program menu. ~0063 \bBLANK CHECK\b Use the Blank Check option to search the device(s) installed in the programmer socket(s) for programmed locations. A failure is indicated if any are found. Selecting the Blank Check Only option from the Program menu runs the operation. Enabling Blank Check in the Select Process dialog box adds the operation to those performed when Process Devices is selected from the Program menu. ~0064 \bILLEGAL BIT CHECK\b The illegal bit test compares data in a device against the programmer's RAM to determine if the device has already- programmed locations of incorrect polarity. For example, an illegal bit error will occur if data in RAM indicates that a specific bit should be in an unprogrammed state while the corresponding bit in the device is in a programmed state. A failure is indicated if any are found. Selecting the Illegal Bit Check Only option from the Program menu runs the operation. Enabling Illegal Bit Check in the Select Process dialog box adds the operation to those performed when Process Devices is selected from the Program menu. ~0065 \bPROGRAM/VERIFY\b Use the Program/Verify option to program the device(s) installed in the programmer socket(s) with the data in programmer RAM and then verify the programmed device data matches programmer RAM. A failure is indicated if any discrepancies are found. When the target device is a logic device, the entire fuse array is programmed. When the target device is a memory device, the following Memory Parameters affect the amount and location of data programmed: \bþ\b Begin RAM \bþ\b Begin Device \bþ\b Device Block Selecting the Program/Verify Only option from the Program menu runs the operation. Enabling Program (Verify is automatically enabled also) in the Select Process dialog box adds the operation to those performed when Process Devices is selected from the Program menu. ~0066 \bVERIFY\b Use the Verify option to ensure that the data in the device(s) installed in the programmer socket(s) matches programmer RAM. A failure is indicated if any discrepancies are found. When the target device is a logic device, the entire fuse array is verified. When the target device is a memory device, the following Memory Parameters affect the amount and location of data verified: \bþ\b Begin RAM \bþ\b Begin Device \bþ\b Device Block Selecting the Verify Only option from the Program menu runs the operation. Enabling Verify in the Select Process dialog box adds the operation to those performed when Process Devices is selected from the Program menu. ~0080 \bTASKS MENU\b The Tasks menu contains options for defining Tasks. A Task is a data record containing all the information necessary for programming and/or testing a particular device. You can store up to 2500 Tasks in a DOS file. Tasks menu options include: \bþ\b Load Task \bþ\b Edit Task \bþ\b Add Task \bþ\b Duplicate Task \bþ\b Remove Task \bþ\b Select Task File ~0081 \bLOAD TASK\b Use the Load Task option to load a previously created Task. The Load Task dialog box contains three items: \bþ\b Task file \bþ\b Task name \bþ\b Task list box Tasks in the task file are displayed in the list box. Select a different Task file by highlighting the Task File entry field and pressing \bF2\b (or by clicking the mouse on the down arrow to the right of the field or double-clicking anywhere in the field) to access a file selection dialog box. Select a Task by entering the name of the Task into the Task entry field or by highlighting the desired Task in the list box and pressing \bEnter\b (or by clicking the mouse on < OK > or double-clicking on the list box line). If you enter the name of a non-existent Task into the entry field, the list box will move to the position the Task WOULD BE if it existed. This feature can be used to find a Task when you do not remember the exact name. When you load a Task, \bþ\b The device type specified in the Task is selected in the programmer. \bþ\b Various programming/testing parameters are set as defined in the Task. \bþ\b The data file (if required) is sent to the programmer. \bþ\b PROMlink is configured to perform the set of operations specified in the Task PROMlink-6 then enters the Process Devices screen, ready to perform the set of operations specified in the Task. The top line of the system status window shows the name of the currently loaded Task. ~0083 \bEDIT TASK\b Use the Edit Task option to change previously created Tasks. The Edit Task dialog box contains three fields: \bþ\b Task file \bþ\b Task name \bþ\b Task list box Tasks in the Task file are displayed in the list box. Select a different Task file by highlighting the Task File entry field and pressing \bF2\b (or by clicking the mouse on the down arrow to the right of the field or by double-clicking anywhere in the field) to access a file selection dialog box. Select a Task by entering the name of the Task into the Task entry field or by highlighting the desired Task in the list box and pressing \bEnter\b (or by clicking the mouse on < OK > or double-clicking on the list box line). If you enter the name of a non-existent Task into the entry field, the list box will move to the position the Task WOULD BE if it existed. This feature can be used to find a Task when you do not remember the exact name. When a Task is selected, a dialog box appears with the following items, containing the current values for the Task. \bþ\b Description \bþ\b Device(s) \bþ\b Data Source \bþ\b Process(es) \bþ\b Programmer Type \bþ\b I/O Format \bþ\b < More... > (Select < More... > to select programming parameters. ) When you exit Edit Task by selecting the < Save > pushbutton, your new selections are written to the specified Task file. ~0084 \bADD TASK\b Use the Add Task option to create new Tasks. The Add Task dialog box contains three items: \bþ\b Task file \bþ\b Task name \bþ\b Task list box Tasks in the selected Task file are displayed in the list box. Select a different Task file by highlighting the Task File entry field and pressing \bF2\b (or by clicking the mouse on the down arrow to the right of the field or by double-clicking anywhere in the field) to access a file selection dialog box. To add a new Task to the Task file, 1. Enter the new Task name in the Task entry field and press \bEnter\b. A Task name may contain up to 25 characters. All printable characters are valid, including spaces. 2. The following items are displayed with their default values: \bþ\b Description \bþ\b Devices \bþ\b Data Source \bþ\b Process(es) \bþ\b Programmer Type \bþ\b I/O Format \bþ\b < More... > (Select < More... > to select programming parameters. ) 3. Change the values in the dialog box. When you exit Add Task by selecting the < Save > pushbutton, your new selections are written to the Task file. ~0085 \bDUPLICATE TASK\b Use the Duplicate Task option to duplicate a Task. Using Duplicate Task reduces the effort required to create a new Task. The Duplicate Task dialog box contains three items: \bþ\b Task file \bþ\b Task name \bþ\b Task list box Tasks in the Task file are displayed in the list box. Select a different Task file by highlighting the Task File entry field and pressing \bF2\b (or by clicking the mouse on the down arrow to the right of the field or by double-clicking anywhere in the field) to access a file selection dialog box. Select a Task by entering the name of the Task into the Task entry field or by highlighting the desired Task in the list box and pressing \bEnter\b (or by clicking the mouse on < OK > or double-clicking on the list box line). If you enter the name of a non-existent Task into the entry field, the list box will move to the position the Task WOULD BE if it existed. This feature can be used to find a Task when you do not remember the exact name. When a Task has been selected for duplication, you will be prompted for the new Task name. Enter the name for the duplicate Task and press \bEnter\b. The Edit Task dialog box will appear with the current values for the Task items: \bþ\b Description \bþ\b Device(s) \bþ\b Data Source \bþ\b Process(es) \bþ\b Programmer Type \bþ\b I/O Format \bþ\b < More... > (Select < More... > to select programming parameters. ) 3. Change the values in the dialog box. When you exit Duplicate Task by selecting the < Save > pushbutton, your new selections are written to the Task file. ~0086 \bREMOVE TASK\b Use the Remove Task option to remove a Task from a Task file. The Remove Task dialog box contains three items: \bþ\b Task file \bþ\b Task name \bþ\b Task list box Tasks in the Task file are displayed in the list box. Select a different Task file by highlighting the Task File entry field and pressing \bF2\b (or by clicking the mouse on the down arrow to the right of the field or by double-clicking anywhere in the field) to access a file selection dialog box. Select a Task by entering the name of the Task into the Task entry field or by highlighting the desired Task in the list box and pressing \bEnter\b (or by clicking the mouse on < OK > or double-clicking on the list box line). If you enter the name of a non-existent Task into the entry field, the list box will move to the position the Task WOULD BE if it existed. This feature can be used to find a Task when you do not remember the exact name. When a Task has been selected for removal, the program asks to confirm the removal. Select < OK > to remove the Task or < CANCEL > to cancel the operation. ~0088 \bIMPORT TASK\b Use the Import Task option to copy a Task from one database to another. The Import Task dialog box contains four input fields: \bþ\b Source database (the database to copy FROM) \bþ\b Task name \bþ\b Destination database (the database to copy TO) \bþ\b Task name Note that the Task name for the destination database can be different from the name in the source database. ~0100 \bUTILITIES MENU\b The Utilities menu contains PROMlink-6 utility functions. The menu includes: \bþ\b Programmer Interface (for some programmers) \bþ\b VT100 on Host Port \bþ\b VT100 on Programmer Port \bþ\b External Terminal Emulator (if one specified) \bþ\b Device List Update \bþ\b Task Device Check ~0101 \bPROGRAMMER INTERFACE\b Use the Programmer Interface option to enter the programmer's menu system and access programmer functions not available with PROMlink-6. The programmer's menu system is accessed with the internal terminal emulator. To return to PROMlink-6, press \bAlt\b+\bF1\b. ~0102 \bTERMINAL EMULATION\b Terminal emulation in PROMlink-6 can be done in two ways: \bþ\b Internal VT100 emulation on either the Host or Programmer ports \bþ\b Running an external DOS program Options for VT100 emulation on the Host and Programmer ports are always available in the Utilities menu. If a program is specified in the Set Terminal Emulation option of the Options menu, the External Terminal Emulator option will also be available in the Utilities menu. When an external terminal emulation program is used, the program must configure the serial port (for example, the baud rate) as needed. PROMlink's port settings will have no effect. ~0103 \bDEVICE LIST UPDATE\b Use the Device List Update option to update PROMlink-6 programmer device support files after a programmer update is installed. PROMlink-6 copies the device list from the programmer and saves it to the PC. When Device List Update is selected, a window appears showing the number of devices uploaded so far and the name of the manufacturer whose devices are currently coming in. This process may take a couple of minutes, depending on the number of devices supported by the programmer. ~0105 \bTASK FILE DEVICE CHECK\b Use the Task File Device Check option to verify that the device names stored in the selected Task file (use Select Task File in the Tasks menu) are supported in the current device support files. Occasionally, a programmer update includes a device name change (for example, an ACME 16L8A might become an ACME 16L8A/B). If a Task contains the name of a specific device whose name has been changed in the programmer's device support list, a "Device Not Found" message will occur when the Task is loaded. When the Task File Device Check utility is run, and an unrecognized device name is found in a Task, the Select Device window appears prompting you to select a replacement device. PROMlink then searches the rest of the Tasks in the Task file, replacing each occurence of the device. \s1ANote:\q Using wildcards (such as * *16L8*) when creating Tasks can reduce device support update conflicts. ~0120 \bOPTIONS MENU\b The Options menu contains options for PROMlink-6 system configuration. Except for Programmer Type, these options are set up at installation and infrequently changed. The Options menu includes: \bþ\b Programmer Type \bþ\b Programmer Port settings \bþ\b Host Port settings \bþ\b I/O Timeout \bþ\b Terminal Emulation \bþ\b Display Type \bþ\b Sumcheck Digits \bþ\b Set Preferences ~0121 \bPROGRAMMER TYPE\b Use the Programmer Type option to specify the Data I/O programmer controlled by PROMlink-6. The Programmer Type dialog box contains a list of supported programmers. When you select a programmer from the list, PROMlink-6 is reconfigured based on the features available on the selected programmer and loads the programmer device list and messages from disk. ~0125 \bPROGRAMMER PORT\b Use the Programmer Port option to set the parameters for the programmer port. The Programmer Port dialog box has a group of radio buttons for each parameter. The Programmer Port settings must match the settings of the programmer's serial port. For optimum performance, the ports should be set to the fastest baud rate supported by the programmer. Recommended Programmer Port settings are: Port : COM1 or COM2 Baud Rate : 9600 (19200 if supported on programmer) Parity : None Data Bits : 8 Stop Bits : 1 Following is a brief explanation of each parameter: \s1EPort\q Selects which PC serial port is being used to connect to the programmer. The "None" option is used to disable the port. Disabling the port may be desired if you do not intend to use the port and some other hardware (such as a serial mouse) in your system uses the port or the interrupt associated with the port. \s1EBaud Rate\q Selects the baud rate. Baud rate is the rate (bits per second) at which data bits are transmitted and received across the serial connection. For 8-bit data with one start and one stop bit and no parity bit, the rate at which characters are sent is equal to the baud rate divided by 10. For example, 9600 baud represents a character transmission rate of 960 characters per second. \s1EParity\q Selects the kind of parity. Parity is an error detection method in which the sending port adds an extra bit to each character to force the number of 1s in the character and parity bit combination to be even (even parity) or odd (odd parity). If the receiving port detects an incorrect parity in the received character, an error is flagged. Select None to disable parity checking. \s1EData Bits\q Selects the number of data bits. Data bits are the bits representing the actual data (character) being transmitted. \bAll\b binary data translation formats and the built-in RAM data editor in PROMlink-6 use 8 data bits. \s1EStop Bits\q Selects the number of stop bits. Stop bits are the bits used to signal the end of a serial data character. ~0126 \bHOST PORT\b Use the Host Port option to set the parameters for the host (remote computer) port. Each parameter in the Host Port dialog box contains a set of mutually-exclusive options. The Host Port settings must match the settings of the host's serial port. For optimum performance, set ports to the fastest baud rate supported by both host and programmer. Following is a brief explanation of each parameter: \s1EPort\q Selects which PC serial port is being used to connect to the programmer. \s1EBaud Rate\q Selects the baud rate. Baud rate is the rate (bits per second) at which data bits are transmitted and received across the serial connection. For 8-bit data with one start and one stop bit and no parity bit, the rate at which characters are sent is equal to the baud rate divided by 10. For example, 9600 baud represents a character transmission rate of 960 characters per second. \s1EParity\q Selects the kind of parity. Parity is an error detection method in which the sending port adds an extra bit to each character to force the number of 1s in the character and parity bit combination to be even (even parity) or odd (odd parity). If the receiving port detects an incorrect parity in the received character, an error is flagged. Select None to disable parity checking. \s1EData Bits\q Selects the data bits. Data bits are the number of bits in each serial data packet representing the actual data (character) being transmitted. \bAll\b binary data translation formats and the built-in RAM data editor in PROMlink-6 use 8 data bits. \s1EStop Bits\q Selects the stop bits. Stop bits are the number of bits used to signal the end of a serial data packet (character). ~0127 \bI/O TIMEOUT\b Use the I/O Timeout option to set the amount of time you want the programmer to wait for incoming data to arrive during a data input operation before flagging an error. I/O Timeout may be useful when downloading data from a host (remote computer) manually or from a host that takes a long time to respond to the data request. Setting the I/O Timeout to zero causes the programmer to wait indefinitely. On the Model 212, Model 288, 29B and UniPak, and 29B and LogicPak programmers, a non-zero I/O timeout enables the programmer's default timeout; it does not set the timeout period to the specified value. ~0128 NOINDEX \bTERMINAL EMULATION\b Use the Terminal Emulation option to select the external terminal emulator to be used to provide terminal emulation when \bþ\b External Terminal Emulator is selected from the Utilities menu OR \bþ\b Load Task is selected from the Tasks menu and the selected Task specifies running an external terminal emulator. If an external terminal emulator is not specified, PROMlink-6 uses an internal VT100 terminal emulator. When you select the Terminal Emulation option, the file selection dialog box appears. If a terminal emulation program is currently specified, it appears in the filename entry field. \s1ANote:\q If an external terminal emulator is specified, but you want to use the internal VT100 emulator only, delete the filename in the filename entry field and press \bEnter\b or click on < OK > with the mouse. When a menu option that specifies an external terminal emulator is selected, PROMlink-6 remains in PC memory while the PC runs the external terminal emulator. Because PROMlink-6 requires a major portion of the PC memory, the external terminal emulation program must be small in order to run successfully. PROMlink-6 will attempt to run any .EXE, .COM or .BAT file. The file specified in the filename entry field can be a program other than an external terminal emulator. ~0129 \bDISPLAY TYPE\b Use the Display Type option to select the type of display being used with the PC running PROMlink-6. There are four options: \bþ\b Color \bþ\b Color/CGA \bþ\b Monochrome \bþ\b Monochrome/CGA Use the color mode for standard EGA and VGA systems. Use the monochrome mode for systems with a monochrome monitor. Monochrome mode modifies the display for maximum readability on a black and white monitor. PROMlink-6 automatically selects monochrome when there is a monochrome card in the PC. You may need to select monochrome mode if a color video card is used with a monochrome monitor. Use the Color/CGA and Monochrome/CGA modes for systems with monitors that appear "snowy." Using a CGA mode gives a clear display with a slight decrease in display speed. ~0130 \bSUMCHECK DIGITS\b Use the Sumcheck Digits option to select the maximum number of digits PROMlink-6 will use to display programmer RAM sumchecks on the screen. The Sumcheck Digits dialog box contains one entry field. Enter the desired maximum number of sumcheck digits (4 to 8). If a programmer does not support the number of digits specified for a sumcheck, the maximum number of digits that the programmer can provide will be displayed. ~0131 \bSET PREFERENCES\b Use the Set Preferences option to select your program behavior preferences. There are four options: \bþ\b Pop-up Sumcheck Window After Transfer/Load Operation \bþ\b Beep After Completion of Device Operation \bþ\b Sound On \bþ\b Display Family/Pinout Code with Device Name \bþ\b Provide Help When Right Mouse Button Pressed ~0140 \bEXIT MENU\b The Exit menu contains options for exiting PROMlink-6. The Exit menu options are: \bþ\b DOS Shell \bþ\b Exit PROMlink-6 ~0141 \bDOS SHELL\b Use the DOS Shell option to temporarily suspend PROMlink-6 (PROMlink-6 remains in PC memory) and return to DOS to run \bsmall\b programs and standard standard DOS functions. To return to PROMlink-6, enter \bexit\b at the DOS prompt. ~0160 \bHELP MENU\b The Help menu contains options provides access to help on the help system menu operation and PROMlink-6 operation. The Help menu options are: \bþ\b Help for Help \bþ\b Keys Help \bþ\b Dialogs Help \bþ\b General Help Index \bþ\b Messages Help Index \bþ\b About PROMlink-6 ~0161 NOINDEX \bHELP FOR HELP\b Use the Help for Help option for a description of the PROMlink-6 help system and how to use it. ~0162 NOINDEX \bKEYS HELP\b Use the Keys Help option for help on the key functions in PROMlink-6. ~0163 NOINDEX \bDIALOGS HELP\b Use the Dialogs Help option for help on dialog boxes. ~0164 NOINDEX \bGENERAL HELP INDEX\b Select General Help Index for an alphabetical list of PROMlink-6 help topics. Selecting from the list accesses help on the selected topic. ~0165 NOINDEX \bMESSAGES HELP INDEX\b Select Messages Help Index for an alphabetical list of PROMlink-6 messages. Selecting from the list accesses help on the selected message. ~0166 NOINDEX \bABOUT PROMlink\b Select About PROMlink for information on PROMlink-6 version and copyright. ~0221 \bVERIFY PASSES\b \s1ETwo-pass Verify\q Specifies two verify passes: one at the maximum Vcc voltage; and one at the minimum Vcc voltage. \s1EOne-pass Verify\q Specifies one verify pass at the nominal Vcc voltage. ~0222 \bCUSTOM COMMANDS\b A Custom Command is a sequence of characters that PROMlink-6 sends to the programmer before any device or data transfer operations. The Custom Command must be a valid Computer Remote Control (CRC) command for the programmer. See the programmer manual for a list of valid CRC commands. You can define up to three custom commands. PROMlink-6 sends a carriage return (hex 13) after the Custom Command and expects a "<" character to be returned by the programmer. An example of using a Custom Command would be to set the low and high verify Vcc voltages on the 212 Logic programmer. The CRC command to do this (found in the Computer Remote Control section of the 212 manual) is "hhll18]", where hh and ll are the high-pass and low-pass voltages in tenths of a volt. To set the voltages to 5.8 and 4.2 volts, you would enter "584218]" (no quotes) in in one of the Custom Command entry fields. Each Custom Command may be followed by one or more flags that indicate at what time the command should be sent to the programmer. The flags are: P send command prior to device processing (program, verify, etc.) M send command prior to loading master device D send command prior to data download ("load RAM from file") U send command prior to data upload ("create file from RAM") If no flags are supplied, the command is send before any operation. The flag(s) should be placed on the Custom Command line following the command and at least one space. For example: 1 ^ D 2 3 Custom Command #1 would clear all of programmer RAM before performing a data download. RAM would not be cleared again before a programming operation. ~0223 \bSECURITY OPTION\b The Security Option value determines the programming of the security bit(s) in the device. The allowable range for and definition of the Security Option values differs between programmers. \s1BUniSite, 2900, 3900, 212 Logic and 29B LogicPak\q Option Security Fuse Value Programming Data = ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 0 Disabled 0 1 Disabled 1 2 Enabled 0 3 Enabled 1 \s1BSeries 1000, Model 212 with Family Codes D5, 54\q Value Function ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 0 Program data into PROM array 1 Program PROM array, verify, then program security bit 2 Program Security bit \s1BModel 212 with Family Code 5A\q Value Function ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 0 Array 1 Array, lock bit 1 and lock bit 2 2 Lock bit 1 and lock bit 2 3 Encryption table (32 bytes) 4 Lock bit 1 5 Array and encryption table 6 Array and lock bit 1 7 Array, encryption table and lock bit 1 \s1BModel 212 with Family Code 51\q Value Function ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 0 Array and user signature 1 Array, user signature and security bit 2 Security bit only ~0224 \bREJECT COUNT\b \s1EManufacturer-\q The programming algorithm supplies the \s1Especified\q manufacturer's specified number of programming pulses. \s1ESingle Pulse\q The programming algorithm supplies a single programming pulse or a military reject count. ~0225 \bELECTRONIC ID CHECKING\b Enable the Electronic ID Checking option to verify that the Electronic ID in the device is appropriate for the selected device type. If the appropriate ID is not found, the operation fails and a message is issued. ~0226 \bBULK ERASE OF EE DEVICES\b Enable the Bulk Erase of EE Devices option to cause electrically- erasable devices to be erased before being programmed with new data. ~0227 \bPROGRAM/VERIFY FROM MASTER\b Enable the Program/Verify from Master option to cause the master device to be used as the data source for program and verify operations. ~0228 \bENABLE SPECIAL DATA\b Turn on the Enable Special Data option to program special locations in the selected device. Enable Special Data is device-dependent. Refer to the Data I/O Reference Chart to determine if Enable Special Data applies to a device. ~0229 \bCONTINUITY CHECKING\b Enable the Continuity Checking option to verify all testable device pins are making contact in the socket. If contact is not verified on all testable pins, the operation fails and a message is issued. ~0231 \bSET SIZE\b The Set Size option indicates the number of "virtual devices" to be programmed with data from different blocks of programmer RAM. The value of the Set Size option does not refer to the number of physical devices used, but to the virtual devices with a data word width indicated by the Word Width option. If the Word Width value is greater than the word width of the selected device, then a virtual device is made up of more than one physical device. For example, if the data word width is 16, the set size is 2, and the devices used are 8-bit devices, then 4 devices would be programmed: two for each 16-bit set. ~0232 \bWORD WIDTH\b The Word Width parameter sets the number of bits in the "virtual device" being programmed. The term "virtual device" is used here because setting the word width larger than the word size of the selected device actually implies the use of more than one device. The Word Width parameter must be at least as large as the word width of the selected device and, if it is larger, it must be an integer multiple of the word width of the selected device. ~0233 \bI/O OFFSET\b \s1AFor Input Operations:\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The address where data is placed in programmer RAM is calculated by taking the incoming address, subtracting the I/O Offset and adding the Begin RAM address. An I/O Offset of \bFFFFFFFF\b causes the I/O offset to default to the first incoming address. \s1AFor Output Operations:\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The outgoing address is calculated by taking the address where the data is located, subtracting the Begin RAM address and adding the I/O Offset. An I/O Offset of \bFFFFFFFF\b causes the I/O Offset to default to zero. ~0234 \bI/O BLOCK\b The I/O Block parameter sets the number of bytes to be used in data transfer operations. The default value of \b000000\b causes the I/O block size to be set to the size of the selected device. ~0235 \bBEGIN RAM\b The Begin RAM parameter sets the first programmer RAM address from which or to which data is to be transferred during device- related operations such as load, program and verify. The default value of Begin RAM is \b000000\b. ~0236 \bBEGIN DEVICE\b The Begin Device parameter sets the first device address from which or to which data is to be transferred. The default value of Begin Device is \b000000\b. ~0237 \bDEVICE BLOCK\b The Device Block parameter sets the number of bytes to be used in device operations. The default value of \b000000\b causes the device block size to be set to the size of the selected device. ~0238 \bAUTOMATIC RAM FILL\b The Automatic RAM Fill parameter selects the data (if any) that programmer RAM will be filled with prior to initiation of an I/O transfer to the programmer. \s1ENone\q Memory is not changed. \s1EDefault\q Unused locations are initialized to the unprogrammed state for the device. \s1ESpecific\q Unused locations are filled with the specified two-digit hex number. ~0239 \bODD/EVEN BYTE SWAP\b Defines the order in which data is transferred to or from devices with a word width greater than eight bits. When Odd/Even Byte Swap is disabled (not checked), the low byte of RAM data corresponds to the low byte (DO-D7) of the device, and the high byte of RAM data corresponds to the high byte (D8-D15) of the device. When Odd/Even Byte Swap is enabled (checked), the low byte of RAM data corresponds to the high byte (D8-D15) of the device, and the high byte of RAM data corresponds to the low byte (D0-D7) of the device. ~0240 \bI/O BEGIN ADDRESS\b The Begin RAM parameter sets the first programmer RAM address from which or to which data is to be transferred during I/O operations such as Load RAM from File and Create File from RAM. The default value of I/O Begin is \b000000\b. ~0251 \bVERIFY OPTIONS\b The Verify Options parameter determines what verification procedures are performed during a verify operation. The options are: \bþ\b Fuse array verify and functional test \bþ\b Fuse array verify only \bþ\b Functional test only Functional Test usually means application of structured test vectors. The 29B with LogicPak may use Logic Fingerprint testing. ~0252 \bCOMPENSATED VECTORS\b The Compensated Vectors option provides special load compensation to the device output pins during structured vector testing. Enabling Compensated Vectors improves some vector testing problems, especially with high-speed devices. ~0253 \bHIGH-SPEED DRIVERS\b The High-speed Drivers option specifies a lower-impedance, faster pin driver to apply structured vector levels to device inputs. Enabling High-speed Drivers improves some vector testing problems, especially with high-speed devices. ~0254 \bSERIAL VECTOR TEST\b The Serial Vector Test option applies the structured test vector levels serially (pin-by-pin) instead of the normal parallel method. This option provides compatibility with programmers that apply vector levels serially. ~0255 \bDIP/LCC VECTOR TRANSLATION\b This options provides automatic translation of structured test vectors loaded from a DIP JEDEC data file to vectors appropriate for testing the PLCC version of the device. ~0300 \bSELECTING A FILE\b Select a file in one of several ways: \bþ\b Enter the filename in the filename entry field \bþ\b Select the path and filename from the list boxes \bþ\b A combination of the above The file selection dialog box contains \bþ\b A status line \bþ\b A filename entry field \bþ\b A current directory indicator line \bþ\b A file list box \bþ\b A dirs/drives list box To access a file in a different directory, press \bTab\b to get to the dirs/drives list box, highlight the drive you want, and press \bEnter\b; then highlight the directory you want and press \bEnter\b. Some file selection dialog boxes accept only files with a certain extension. Task files have a \b.tsk\b extension. Log files have a \b.log\b extension. The file list box contains all files matching the filename wildcard in the filename entry field. Change the filename wildcard by entering a new wildcard in the filename entry field and pressing \bEnter\b. To select a file from the file list box, press \bEnter\b when the desired file is highlighted, or double-click on the desired file with the mouse. You can specify a drive, path, or file that is not currently available on the PC by entering any valid DOS path name\filename combination in the filename entry field. If the drive or path is not available, the file list box will indicate that the drive and/or path is not available, but the file will be accepted. ~0330 \bHOST COMMAND\b When you select the Load RAM from Host option, you are prompted for an optional Host Command: a string of characters that will be sent to the host (remote computer) to start the transmission of data. The Host Command is sent to the host when Load RAM from Host is selected. PROMlink-6 adds a carriage return (hex 13) to the end of the Host Command. ~0354 \bSTARTING DEVICE OPERATIONS\b To start a device operation: \bþ\b Press \bSpace\b or \bEnter\b (with < Start > highlighted) \bþ\b Click the mouse on < Start > \bþ\b Press lever or close dial on programmer (gang and set programming) To end a processing session: \bþ\b Press \bEsc\b \bþ\b Highlight < Exit >, then press \bSpace\b or \bEnter\b \bþ\b Click the mouse on < Exit > ~0391 \bTASK DESCRIPTION\b A Task description may contain up to 40 characters. The Task description appears to the right of the Task name in the Task list box. It is only used for identification purposes and can be any text you want. ~0392 \bTASK DEVICE TYPE(S)\b Use the Device(s) entry fields to create a Task-specific device list. You can select up to five specific devices from the Select Device list box, or enter up to five device wildcards. To access the Select Device list box, press \bF2\b or click the mouse on the down arrow to the right of the field (or double-click anywhere in the field). If more than one specific device or at least one wildcard are specified, a list of devices to choose from is presented to the operator when the Task is loaded. The following are some examples of Device(s) list box entries: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ \s1AEntry\q ³ \s1AResult\q ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ \bINTEL 27128\b ³ Exact device INTEL 27128 ³ ³ ³ ³ ³ \bTI *16L8*\b ³ All TI devices with "16L8" in name ³ ³ ³ ³ ³ \b* *27?512*\b ³ All devices with "27" followed by any ³ ³ ³ character and "512" in the name ³ ³ ³ ³ ³ \bF/P 9717\b ³ Data I/O family and pinout code 9717 ³ ³ ³ ³ ³ \bEXTENDED_ALG\b ³ Causes display of Extended Algorithms ³ ³ ³ when Task is loaded ³ ³ ³ ³ ³ \bKEEP_CURRENT\b ³ Causes display of Keep Current(TM) ³ ³ ³ algorithms when Task is loaded ³ ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ~0393 \bTASK DATA SOURCE\b The Data Source for a Task can be any one of the following: \bþ\b None \bþ\b PC Disk File (Data File entry field appears) \bþ\b Master Device \bþ\b Host Download (Host Command entry field appears) \bþ\b Terminal/Host (Host Command entry field appears) \s1ENone\q No data source is specified and no data is transferred into programmer RAM when you load the Task. \s1EPC Disk File\q The data source for the Task is a PC disk file. Enter the path and filename of the PC disk file in the Data File entry field that appears when you select PC Disk File. When you load the Task the data is downloaded into programmer RAM. \s1EMaster Device\q The data source for the Task is a Master Device. When you load the Task, you are prompted to load a master device. \s1EHost Download\q The data source for the Task is a host (remote computer) download. When you load the Task, a host download is initiated. If necessary, enter a host command in the Host Command entry field that appears when you select Host Download. \s1ETerminal/Host\q The data source for the Task is a host (remote computer) download. When you load the Task, the terminal emulator selected in the Set Terminal Emulation option of the Options menu is initiated (the internal VT100 emulator on the Host port is used if no external emulator is specified). You can then communicate with the host computer and prepare it to send data. When you exit the terminal emulator, a host download is initiated. If necessary, enter a host command in the Host Command entry field that appears when you select Terminal/Host. ~0394 \bTASK DATA FILE\b Enter the path and filename of a PC disk file. When you load the Task, the data is transferred into programmer RAM. You can enter the path and filename, or press \bF2\b or click the mouse on the down arrow to the right of the field (or double- click anywhere in the field) to access a file selection dialog box. ~0395 \bTASK PROCESS(ES)\b The Process(es) check box field contains three columns of check boxes. Each column represents a process and has a check box for each of the following operations. \bþ\b Blank check \bþ\b Illegal bit \bþ\b Program \bþ\b Verify An X in the check box indicates that the operation is selected. One or more boxes checked in a single column defines a process. If more than one process is specified (an X in more than one column), you are prompted to choose one when you load the Task. Since PROMlink automatically perform a verify operation whenever a program operation is performed, you cannot select the Program operation without selecting the Verify operation. ~0396 \bTASK PROGRAMMER TYPE\b To select a programmer type for a Task, press \bF2\b or click the mouse on the down arrow to the right of the field (or double- click anywhere in the field) to access a programmer list box. Select "Default" or a specific programmer type from the list. When you select Default as the programmer type, the Task works with the current programmer selected in PROMlink-6 when the Task is loaded. If you load a Task that is assigned a specific programmer type, PROMlink-6 reconfigures to that programmer type when you load the Task. ~0398 NOINDEX \b< MORE... >\b Select < More... > to select programming parameters. ~0399 \bDATA SUMCHECK\b Entering a hexadecimal value in the Data Sumcheck input field causes PROMlink-6 to verify that the programmer RAM sumcheck (following the loading of a Task) matches the entered value. If the sumchecks do not match, an error is reported, and the Task is not successfully loaded. If the field is left blank, no checking will occur. ~0400 \bSELECTING A TASK DEVICE\b A Task-specific device list created from the Device(s) list box appears when you select Load Task from the Tasks menu. To select a device from the list use the following keys. \s1AKey:\q \s1AAction:\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \bUp Arrow\b moves highlight up one line \bDown Arrow\b moves highlight down one line \bPgUp\b moves highlight up one screen \bPgDn\b moves highlight down one screen \bHome\b moves highlight to first device in list box \bEnd\b moves highlight to last device in list box \bEnter\b selects highlighted device You can also use the mouse and the scroll bar at the bottom of the list box to position the cursor on a device name and highlight it by clicking the left mouse button. Double-click to select the device. ~0410 \BESTABLISHING COMMUNICATION\b If PROMlink-6 cannot contact the programmer, check that \bþ\b The programmer is in computer remote control mode. \bþ\b The RS-232 cable is connected properly. \bþ\b The PROMlink-6 port settings match the programmer's. \s1AEntering Computer Remote Control Mode\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For PROMlink-6 to communicate with the programmer, the programmer must be in Computer Remote Control (CRC) mode. The procedure for entering CRC mode depends on the type of programmer you are using. \s1BUniSite, 2900, 3900\q To operate the UniSite/2900/3900 with PROMlink-6, two parameters should be set in the programmer's terminal menus: \bþ\b User Menu Port should be set to "Remote" \bþ\b Power-up CRC Mode should be set to "Yes" The programmer's terminal menus may be accessed using PROMlink's internal VT100 emulator, found in the Utilities menu. Connect the RS-232 cable from the PC Programmer Port to the programmer's "Terminal" port. Select \bVT100 on Programmer Port\b from PROMlink's Utilities menu and power-up the programmer. The User Menu Port parameter is found under "More Commands/ Configure System/Edit/Communication". Set the parameter to "R". The Power-up CRC Mode parameter is found under "More Commands/ Configure System/Edit/Interface". Set the parameter to "Y". When the two parameters are set, save the configuration as the power up default from the "More Commands/Configure System/Save" screen. The RS-232 cable should then be moved to the programmer's "Remote" port. When the UniSite is powered-down and powered-up again, it should be ready to communicate with PROMlink. \s1BSeries 1000\q Select "Remote Control" from the programmer front panel. \s1B200 Series\q Select "RS232 Port-Computer Control" from the programmer front panel. \s1B29B with UniPak, 29B with LogicPak\q Select \bF1\b from the 29B front panel. \s1ARS-232 Cable\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The RS-232 cable supplied with PROMlink-6 works with any PC serial port and any supported Data I/O programmer. Make sure that the cable is connected to the correct port on the PC (the port selected in PROMlink's \bProgrammer Port\b option). For UniSite/2900/3900, make sure the cable is connected to the "Remote" port. For UniSite, make sure the the button next to the "Remote" port is in the correct position (the "Remote" light on UniSite's front panel should be lit). \s1APort Settings\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The PROMlink-6 Programmer Port settings must match the programmer's serial port settings. To change the Programmer Port settings, select \bProgrammer Port\b from the Options menu. ~0415 \bINDIVIDUAL SOCKET STATUS\b The Individual Socket Status window shows the status of each socket on a multi-socket (gang/set) programmer after a device operation is completed. When the number of physical devices in a set is greater than one, the window also shows the sumcheck of each socket without an error. The errors that can occur in each socket are \bþ\b Device Test (continuity or overcurrent) \bþ\b Electronic ID \bþ\b Non-blank \bþ\b Illegal Bit \bþ\b Program Fail \bþ\b Verify Fail ~0416 NOINDEX \bTASK LOADED\b Your Task has been successfully loaded. Proceed with programming. ~0500 MSG \bOPERATION CANCELLED\b An Operation Cancelled message appears when an operation is halted by the operator before completion. Halting an operation is done by one of the following actions: \bþ\b Pressing \bEsc\b \bþ\b Clicking the mouse on < Stop > or < Cancel > buttons ~0501 MSG \bUNRECOGNIZED COMMAND\b An Unrecognized Command message appears when the programmer does not recognize a command sent by PROMlink-6. Make sure you have the proper programmer type selected. If you are using Custom Commands, make sure the Custom Command is correctly entered and is appropriate for the programmer being used. ~0502 MSG \bUNKNOWN ERROR RESPONSE\b An Unknown Error Response message appears when PROMlink-6 receives an error code response it cannot recognize from the programmer. Make sure you have the proper programmer type selected. If the message persists, contact Data I/O. ~0506 MSG \bINVALID DATA\b An Invalid Data message appears when an I/O translator is unable to translate a data file. Try the operation again. If the problem persists, the data file is probably invalid. ~0507 MSG \bPROGRAMMER TIMEOUT\b A Programmer Timeout message appears when the programmer does not respond to a command from PROMlink-6 in an appropriate amount of time. Make sure the correct programmer type is selected and retry the operation. ~0510 MSG \bUNABLE TO RESTORE REMOTE CONTROL\b The Unable To Restore Remote Control message appears when cannot return the programmer to Computer Remote Control operation after using the built-in terminal emulator to access the programmer's internal menus. Either re-boot the programmer or use the VT100 on Programmer Port option to manually switch the computer back into Remote Mode. ~0511 MSG \bBAD FILE SPECIFICATION\b The Bad File Specification message appears when a drive:path\\file specification has a filename portion that does not meet the syntax requirements for a DOS filename. ~0512 MSG \bBAD PATH SPECIFICATION\b The Bad Path Specification message appears when a drive:path\\file specification has a path portion that does not meet the syntax requirements for a DOS path name. ~0513 MSG \bBAD DRIVE SPECIFICATION\b The Bad Drive Specification message appears when a drive:path\\file specification has a drive specifier that does not meet the syntax requirements for a DOS drive specifier. ~0514 MSG \bIMPROPER FILENAME EXTENSION\b The Improper Filename Extension message appears when a file specification is entered that has an incorrect extension for the type of file. PROMlink-6 will add the proper extension (if required) if a filename without an extension is entered but will generate a Improper Filename Extension message if the filename already has an extension of the wrong type. ~0515 MSG \bCUSTOM DEVICE FILE NOT FOUND\b The Custom Device File Not Found message appears when PROMlink-6 attempts to translate a custom device name and cannot find the custom device file for the selected programmer. The custom device file (.CUS extension) must be located in the same directory as the standard programmer device file (.DEV extension). For more information on custom devices, see the Custom Device File entry in the General Help Index. ~0516 MSG \bCUSTOM DEVICE NAME NOT FOUND\b The Custom Device Name Not Found message appears when PROMlink-6 cannot find the custom device name in the custom device file for the selected programmer. Make sure that you do a Device List Update after any changes to the custom device file. For more information on custom devices, see the Custom Device File entry in the General Help Index. ~0517 MSG \bBAD F/P CODE IN CUSTOM FILE\b The Bad Family/Pinout Code In Custom Device File message occurs when PROMlink-6 has translated a custom device name to a Data I/O family/pinout code, but the family/pinout code is of the incorrect format. Family/pinout codes should consist of four or six hexadecimal digits. Check the custom device file entry for the device. For more information on custom devices, see the Custom Device File entry in the General Help Index. ~0518 MSG \bTRANSLATED CUSTOM DEVICE NOT FOUND\b The Translated Custom Device Not Found message occurs when PROMlink-6 has translated a custom device, but the target device name is not found in the programmer's device list. Check the custom device file to make sure that the Data I/O device name supplied for the custom device is correct. Also make sure that the device is supported on the programmer. For more information on custom devices, see the Custom Device File entry in the General Help Index. ~0519 MSG \bDISPLAY LIMIT REACHED\b The Display Limit Reached message occurs when the expansion of wildcards in the Task device list results in a list of more than 400 devices, or when PROMlink runs out of memory when expanding the wildcard(s). The list box will contain as many matches as possible. To prevent this error, use a combination of specific devices and/or wildcards that results in a smaller list of devices. Note: the wildcard "* *" will always cause this error on a programmer that supports more than 400 devices. ~0520 MSG \bSUMCHECK MISMATCH\b The Sumcheck Mismatch message occurs when, as a result of loading a Task, the resultant programmer RAM sumcheck does not match the sumcheck value stored in the Task record. Attempt to load the Task again. If the message recurs, ensure that the sumcheck stored in the Task "Data Sumcheck" field is correct for the data source used. ~0551 MSG \bFILE NOT FOUND\b The File Not Found message appears when an attempt is made to access a file that does not exist. ~0552 MSG \bDEVICE I/O ERROR\b The Device I/O Error message appears when PROMlink-6 is using a disk drive and an unrecoverable input or output error occurs. Try the operation again. If the error persists, the disk drive or data file is defective. ~0553 MSG \bDISK FULL\b The Disk Full message appears during a disk write operation when the disk drive does not have enough free space to write the required information. Delete any unnecessary files to make room for the file or write the file to a different disk drive. ~0554 MSG \bBAD PATH/FILENAME\b The Bad Path/Filename message appears when an attempt is made to access a file with an invalid filename. ~0555 MSG \bTOO MANY FILES\b The Too Many Files message appears under the following conditions: \b1\b The number of open files exceeds the number of open files permitted by DOS. \b2\b The limit on the number of files in the root directory has been reached. For the first problem, increase the number of open files allowed by changing the \bFILES=\b entry in the \bconfig.sys\b file. For the second problem, reduce the number of files in the root directory or store the file in a subdirectory. ~0556 MSG \bDEVICE UNAVAILABLE\b The Device Unavailable message appears when an attempt is made to access an unavailable disk drive. Check the list of available drives in the Dirs/Drives list box in the file selection dialog box. ~0557 MSG \bPERMISSION DENIED\b The Permission Denied message appears when an attempt is made to write to a write-protected disk, or to access a locked file. ~0558 MSG \bDISK NOT READY\b The Disk Not Ready message appears when a floppy disk drive has been specified and there is no disk in the drive or when the floppy disk drive door is open. ~0559 MSG \bDISK MEDIA ERROR\b The Disk Media Error message appears when the disk drive hardware has detected a flaw on the disk. ~0560 MSG \bPATH/FILE ACCESS ERROR\b The Path/File Access Error message appears under the following conditions: \bþ\b DOS is unable to make a connection between the specified path and filename. \bþ\b An attempt is made to save a file that would replace an existing read-only file. ~0561 MSG \bPATH NOT FOUND\b The Path Not Found message appears during a file operation when DOS is unable to find the specified path. ~0562 MSG \bPC SERIAL PORT OVERRUN ERROR\b The PC Serial Port Overrun Error message appears when incoming data overflows the receive buffer. This can occur if you have device drivers or TSRs installed that reduce the PC's ability to respond to incoming characters on the serial port. If the message appears when you are performing a download from a host (remote computer), check that the host can properly respond to XON/XOFF handshaking. ~0563 MSG \bPC SERIAL PORT PARITY ERROR\b The PC Serial Port Parity Error message appears if the serial port detects a parity error in incoming data. Check that the parity settings for the PC, programmer and host (remote computer) are the same. ~0564 MSG \bPC SERIAL PORT FRAMING ERROR\b The PC Serial Port Framing Error message appears when the serial port detects a start bit, but the stop bit is positioned incorrectly. Check that the baud rates of the PC, programmer and host (remote computer) are the same and that you are using the correct serial cable. ~0565 MSG \bDOS SHELL FAILURE\b The DOS Shell Failure message appears either when PROMlink-6 is unable to exit to a DOS Shell or run an external DOS program. This is usually caused by not having enough memory in the PC or an incorrect filename. Refer to the message that DOS prints on the screen behind the PROMlink-6 message window for more information. ~0566 MSG \bDEVICE FILE NOT FOUND\b The Device File Not Found message appears when PROMlink-6 cannot locate the device file for the currently selected programmer. This message can appear when PROMlink-6 is first started, when a new programmer is selected in either the Options menu or in the Task editing window, or during a Task File Device Check. The message indicates that the device file does not exist in the current directory or the directory (if any) defined with the PLFILES environment variable. If you wish to run PROMlink-6 from a directory other than the one in which the PROMlink-6 files are located, you should place the following line in your AUTOEXEC.BAT file: set PLFILES=pathname "pathname" is the name of the directory in which the PROMlink-6 files are located. You should also add "pathname" to the PATH statement in AUTOEXEC.BAT. PROMlink will look for each of its support files first in the current directory. If the file is not found, PROMlink will look in the directory defined by PLFILES. The PROMlink-6 installation program will automatically make the necessary changes to your AUTOEXEC.BAT file if you allow it. ~0567 MSG \bDEVICE FILE NOT LOADED\b The Device File Not Loaded message appears when the Select Device option is selected and the device file for the current programmer has not been loaded. The device file is loaded when PROMlink-6 is first started or when a new programmer is selected in either the Options menu or in the Task editing window. The most likely reason for the device file not being loaded is that PROMlink could not find the device file in the current directory or the directory (if any) defined with the PLFILES environment variable. If you wish to run PROMlink-6 from a directory other than the one in which the PROMlink-6 files are located, you should place the following line in your AUTOEXEC.BAT file: set PLFILES=pathname "pathname" is the name of the directory in which the PROMlink-6 files are located. You should also add "pathname" to the PATH statement in AUTOEXEC.BAT. PROMlink will look for each of its support files first in the current directory. If the file is not found, PROMlink will look in the directory defined by PLFILES. The PROMlink-6 installation program will automatically make the necessary changes to your AUTOEXEC.BAT file if you allow it. ~0568 MSG \bDEVICE NOT SUPPORTED\b The Device Not Supported message appears when the currently- selected device cannot be programmed/tested with the selected programming equipment. Select a different device type or contact Data I/O for device support update information. ~0569 NOINDEX \bOPERATION NOT ALLOWED IN SIMULATION MODE\b The option you have selected is not supported in Simulation Mode. ~0570 NOINDEX \bRAM EDITOR TRANSFER ERROR\b The RAM Editor Transfer Sumcheck Error message occurs when the sumcheck of the data transferred to/from the programmer when using PROMlink's built-in RAM editor does not match the sumcheck transmitted at the end of the data block. The RAM Editor Timeout error occurs when the programmer does not send data when the editor routine requests it. A likely cause is a logic device selected. Retry the editing operation. If the error persists, contact Data I/O. ~0571 MSG \bNO DATA UPLOADED\b The No Data Uploaded message occurs when the programmer is unable to send the requested data during a Create File From RAM operation. The most likely cause is an incorrect I/O format for the device type selected. ~0572 NOINDEX \bHOST PORT CANNOT BE SAME AS PROGRAMMER PORT\b A Load RAM From Host operation has been attempted with the Host Port set to the same hardware serial port as the Programmer Port. See the Options/Programmer Port and Options/Host Port options to change the port assignments. ~0573 MSG \bDEVICE UPDATE NOT SUPPORTED\b The Device Update Not Supported message appears when the Device Update function is attempted and the programmer is unable to provide device information. The most likely cause is that the operating software in the programmer is of a version too early to support the device update feature. Contact Data I/O for update information. ~0574 NOINDEX \bDEVICE MISMATCHES MAY STILL EXIST\b The Device Mismatches May Still Exist message appears when, during a Task File Device Check operation, an error occurs or the user does not specify a replacement device for one or more devices that were not found. To ensure no mismatches, run the Task Device Device Check utility again and supply replacements for all devices. ~0575 MSG \bBAD DATA IN TASK RECORD\b The Bad Data in Task Record message appears when one or more fields in the loaded Task record have erroneous (out of range) values. This indicates a corrupted Task file. Delete and replace the Task that causes the error. If more problems occur with the Task or other Tasks in the file, replace the Task file. ~0576 MSG \bINVALID TASK FILE\b The Invalid Task File message occurs when PROMlink-6 determines that the specified Task file is not of the correct format. Choose another Task file. ~0577 MSG \bTASK LIMIT EXCEEDED\b The Task Limit Exceeded message appears when an attempt is made to add a Task to a Task file that contains 2500 Tasks (!). Remove one or more Tasks from the file or create another Task file. ~0578 MSG \bNO EXTENDED ALGORITHMS FOUND\b The No Extended Algorithms Found message appears when the "EXTENDED_ALGS" item is selected from the device manufacturer list and no extended algorithms are found on the programmer disk(s). Extended algorithms are found in a disk file called ALG.EXT. ~0579 MSG \bNO KEEP CURRENT ALGORITHMS FOUND\b The No Keep Current Algorithms Found message appears when the "KEEP_CURRENT" item is selected from the device manufacturer list and no Keep Current algorithms are found on the programmer disk(s). ~0580 NOINDEX \bFEATURE NOT SUPPORTED\b The system software in the programmer does not support the selected option. Contact Data I/O for programmer software update information. ~0581 NOINDEX \bDEVICE UPDATE INCOMPLETE\b The Device Update utility has been stopped before completion or an error has occurred during the device update. The device file for the selected programmer has been deleted and no device selection operations are possible until the Device Update utility is performed until completion. ~0582 NOINDEX \bERROR LOADING TASK IN BATCH MODE\b The loading of the specified Task in batch mode has not been successful. PROMlink-6 will now return to DOS. Use the normal operating mode of PROMlink-6 to make any changes to the Task. ~0583 MSG \bNO LOG FILE SPECIFIED\b To use PROMlink's session data logging feature you must, from the Setup/Session Data Logging menu: (1) Select the "Enabled" radio button (2) Provide the name of the file into which session data will be appended ~0584 MSG \bNO SOCKETS INSTALLED\b The No Sockets Installed message appears when device operations are attemped with no programming rails installed in the programmer. Install one or more programming rails and repeat the operation. ~0585 MSG \bERROR MESSAGE FILE NOT LOADED\b The Error Message File Not Loaded message appears when a programmer operation is attempted when the error messages for the programmer have not been loaded. The error message file is loaded when PROMlink-6 is first started or when a new programmer is selected in the Options\Programmer Type menu. The most likely reason for the error message file not being loaded is that PROMlink could not find the file in the current directory or the directory (if any) defined with the PLFILES environment variable. If you wish to run PROMlink-6 from a directory other than the one in which the PROMlink-6 files are located, you should place the following line in your AUTOEXEC.BAT file: set PLFILES=pathname "pathname" is the name of the directory in which the PROMlink-6 files are located. You should also add "pathname" to the PATH statement in AUTOEXEC.BAT. PROMlink will look for each of its support files first in the current directory. If the file is not found, PROMlink will look in the directory defined by PLFILES. The PROMlink-6 installation program will automatically make the necessary changes to your AUTOEXEC.BAT file if you allow it. ~0586 MSG \bNO DEVICE SELECTED\b PROMlink-6 required that a device be selected before any programmer operations are performed (even the RAM editor!). Select a device (from the Setup/Select Device menu or by loading a Task) and retry the operation. ~0587 MSG \bTASK DEVICE NOT FOUND\b The Task Device Not Found message occurs when PROMlink-6 is not able to find the specific device (or any matches to a device wildcard) specified in a Task when the Task is loaded. Check the Task to determine if the specified device(s) are correctly entered. If you have recently updated your programmer device file with the Device Update utility, you should run the Task File Device Check utility on the Task file containing the Task to determine if device names have changed. ~0588 MSG \bFILE/DIRECTORY DISPLAY LIMIT\b Due to PC memory limitations, PROMlink is able to display only a limited number of file and directory entries in the file selection dialog box. The limit depends on several factors such as how much memory PROMlink is using for other purposes and the place within PROMlink where the file selection dialog box is used. Upon reaching the limit for either files or directories, PROMlink will display as many entries as it can. You can always enter the desired filename in the entry field. ~0589 MSG \bERROR MESSAGE FILE NOT FOUND\b The Error Message File Not Found message appears when PROMlink-6 cannot locate the error message file PL.ERR. This message can appear when PROMlink-6 is first started or when a new programmer is selected in either the Options menu or in the Task editing window. The message indicates that the error message file does not exist in the current directory or the directory (if any) defined with the PLFILES environment variable. If you wish to run PROMlink-6 from a directory other than the one in which the PROMlink-6 files are located, you should place the following line in your AUTOEXEC.BAT file: set PLFILES=pathname "pathname" is the name of the directory in which the PROMlink-6 files are located. You should also add "pathname" to the PATH statement in AUTOEXEC.BAT. PROMlink will look for each of its support files first in the current directory. If the file is not found, PROMlink will look in the directory defined by PLFILES. The PROMlink-6 installation program will automatically make the necessary changes to your AUTOEXEC.BAT file if you allow it. ~0590 MSG \bERROR LOADING ERROR MESSAGES\b The Error Loading Error Messages message (!) appears when PROMlink cannot find the error messages for the selected programmer in the file PL.ERR. The PL.ERR file may be damaged. Reinstall the file from the PROMlink-6 distribution disk. ~0591 MSG \bERROR LOADING SETUP FILE\b The Error Loading Setup File message occurs when PROMlink-6 fails to load setup information from the file PL.SET. If this happens, PROMlink-6 sets all parameters to default values. This message is most likely to occur if PROMlink-6 cannot find the file PL.SET because it doesn't exist in the current directory or the directory (if any) defined with the PLFILES environment variable. To create a new PL.SET, just exit PROMlink-6. A new PL.SET is written by PROMlink-6 each time you exit the program. If you wish to run PROMlink-6 from a directory other than the one in which the PROMlink-6 files are located, you should place the following line in your AUTOEXEC.BAT file: set PLFILES=pathname "pathname" is the name of the directory in which the PROMlink-6 files are located. You should also add "pathname" to the PATH statement in AUTOEXEC.BAT. PROMlink will look for each of its support files first in the current directory. If the file is not found, PROMlink will look in the directory defined by PLFILES. The PROMlink-6 installation program will automatically make the necessary changes to your AUTOEXEC.BAT file if you allow it. ~0592 MSG \bBAD DATA IN SETUP FILE\b The Bad Data In Setup File message occurs when PROMlink detects that the values in one or more fields in the file PL.SET are invalid. To create a new PL.SET, just exit PROMlink-6. A new PL.SET is written by PROMlink-6 each time you exit the program. ~0593 MSG \bPORT NOT ENABLED\b The Port Not Enabled message appears when an operation is attempted that requires the use of the Programmer Port or Host Port, and that port has been disabled in the Options menu. See the Programmer Port or Host Port options in the Options menu to enable the port. ~0594 MSG \bPORT NOT INSTALLED\b The Port Not Installed message appears when an operation is attempted that requires the use of the PC serial port COM1 or COM2, and that port is not installed in the PC. Install the required hardware, or see the Programmer Port or Host Port options in the Options menu to change the port assignment to a COM port that is installed. ~0603 \bPOP-UP SUMCHECK\b Enable Pop-up Sumcheck Window After Transfer/Load Operation to display the RAM sumcheck after a data download from a disk file or host (remote computer). When Pop-up Sumcheck Window After Transfer/Load Operation is disabled, PROMlink-6 returns to the main screen after the download and the sumcheck is displayed in the System Status box on the main screen. ~0604 \bBEEP AFTER COMPLETION\b Enable the Beep After Completion of Device Operation option to generate an audible signal after the completion of a device operation. One beep signifies pass; three beep signifies errors have occurred. Beep After Completion will have no effect unless Sound On is also enabled. ~0605 \bSOUND ON\b Enable Sound On to permit PROMlink to beep upon completion of certain operations and when errors occur. ~0606 \bDISPLAY FAMILY/PINOUT\b Enable Display Family/Pinout Code with Device Name to display the Family/Pinout Code to the right of the device name in the System Status box on the main screen. ~0607 \bRIGHT MOUSE BUTTON HELP\b Enable the Provide Help When Right Mouse Button Pressed option to allow accessing context-sensitive help by pressing the right mouse button (as an alternative to clicking on the < F1=Help > button). When this option is enabled, you may exit the Help window by clicking on the right mouse button again. ~0700 \bRAM EDITOR\b Use the PROMlink-6 RAM editor to edit programmer RAM in blocks of 256 bytes. When you enter the editor, the first 256 bytes of RAM are displayed. The editor has two editing fields, hexadecimal and ASCII. Enter hexadecimal numbers in the hex field. Enter ASCII characters in the ASCII field. To change entry fields use \bTab\b or \bShift\b+\bTab\b. Use the pushbuttons at the bottom of the screen to \bþ\b Write current block and load next block \bþ\b Write current block and load previous block \bþ\b Jump to the block containing a specified address \bþ\b Restore the contents of the current block \bþ\b Exit the editor The byte address of the cursor is shown at the top of the editor screen. ~0800 \bLOG FILE FORMAT\b The log file created by PROMlink-6 is a line-oriented ASCII file. After each programming or testing session, a six-line record is appended to the file. An example of a PROMlink-6 log file record is shown below. An explanation of each line is shown below. Line Format ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1 - 2 324-5678-001 3 25/07/91 09:47 4 c:\\data\\p5678001.jed 5 AMD 16L8-7 6 357,2,0,1,0,3 \s1ALine 1: A Dash\q Example: \b-\b The first line of each record is a dash (-). This line visually separates each log file record. \s1ALine 2: Task Name\q Example: \b324-5678-001\b The second line of each record is the Task name that was loaded for the programming/testing session. In the example, the line contains a ten digit part number, which is a possible Task name. If no Task is loaded during the session, this line contains a question mark (?). \s1ALine 3: Date and Time\q Example: \b25/07/91 09:47\b The third line of each record is the date and time that the record was added to the log file. The day, month and year are two digits each, separated by forward slashes (/). After the date is a single space followed by the time in 24-hour format. Hours and minutes are and represented by two digits, separated by a colon (:). \s1ALine 4: Data Source\q Example: \bc:\\data\\p5678001.jed\b The fourth line of each record is the name of the data source used for the programming/testing session. If the data came from a PC disk file, the line will contain the name of the file. Other data sources can be: Master Device, Host Download or Host: "command," where "command" is the host (remote computer) command (in quotes) that was used to initiate the host download. If the data source used in the session is unknown, the line will contain a question mark (?). \s1ALine 5: Device Type\q Example: \bAMD 16L8-7\b The fifth line of each record is the name of the device used for the programming/testing session. The device name appears exactly as it does in PROMlink-6. If a Data I/O family and pinout code was used to select the device, the name will be F/P XXXX, where XXXX is the family and pinout code (may be six digits). \s1ALine 6: Device Category Counts\q Example: \b357,2,0,1,0,3\b The sixth line of each record contains six device category counts separated by commas. The counts, from left to right as shown in the example, are listed below with a description of their contents: Count Position Device Category Counted Example ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1 Parts correctly programmed/tested 357 2 Bad devices 2 3 Illegal bit/non-blank 0 4 Programming errors 1 5 Data verify errors 0 6 Functional verify errors 3 The second count, Bad devices, is a catch-all category for any device failures that do not fall in the other categories. Failures in this count include continuity check fail, security fuse blown, and overcurrent failures. ~0810 \bHIGH-SPEED DOWNLOAD\b You can send memory data to the UniSite and the 2900 and 3900 programmers at high speed (115.2k baud) when the data is stored in certain I/O formats. High-speed transfer is automatically used when I/O Format is set to one of the following. (10) Binary (95) Motorola 32-bit (16) Absolute Binary (83) Intel INTELLEC (82) Motorola EXORciser (88) Intel MCS-86 (87) Motorola EXORMAX (99) Intel Hex-32 ~0820 \bCUSTOM DEVICE FILE\b Use the Custom Device File feature to create a cross-reference between your own names for programmable devices and the names used by a particular Data I/O programmer. This feature is not supported with the 29B programmer with the microprocessor modules for the 288 Multiprogrammer. PROMlink-6 stores device information for each programmer in a separate disk file. The file has a name unique to the programmer and a .dev extension. To use the Custom Device File feature, you must create a file of the same name, in the same directory, but with a .cus extension. This file will contain the cross- referencing information. A different file is required for each programmer type used. \s1ACustom Device Filenames\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ UniSite or UniSite/SetSite: UNISITE.CUS 2900 Programming System: 2900.CUS 3900 Programming System: 3900.CUS Series 1000: S1000.CUS Series 1000LC: S1000LC.CUS 200 Series Model 212 with EPROM module: 212MEM.CUS Model 212 with Logic module: 212LOGIC.CUS Model 212 with Microprocessor module: 212MICRO.CUS Model 288 32-pin EPROM module: 288MOS32.CUS Model 288 40-pin EPROM module: 288MOS40.CUS \s1ACustom Device File Format\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ A typical custom device file line looks like this: YourName : OurName where "YourName" is your name for the device and "OurName" is the name of the device as it appears in the Select Device menu. You can also reference a Data I/O family and pinout code by using F/P XXXX where XXXX is the family and pinout code (may be six digits). If the first non-blank line in the file does not have a colon in it, the line contents are used as the "manufacturer" name for the custom devices. If no such line is included in the file, the devices will appear under the manufacturer CUSTOM. A custom device file for UniSite (UNISITE.CUS) with a manufacturer name of ACME might look like this: ACME DEVICEA : AMD 16L8-7 DEVICEB : INTEL 27128 The spaces on either side of the colon are not required. \s1AUsing the Custom Device File\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ To activate the above custom device file, select the Device List Update option from the Utilities menu. After running Device List Update, the first manufacturer in the Select Device list will be ACME, and the two devices, DEVICEA and DEVICEB, will be available. When you select ACME DEVICEA, the AMD 16L8-7 is selected. ~0821 \bEXTENDED ALGORITHMS\b The Extended Algorithms feature allows access to device algorithms stored in the file ALG.EXT on the programmer disk. ALG.EXT files are algorithm files issued by Data I/O to handle device approvals and special device algorithm updates. On a programmer that supports extended algorithms, the special manufacturer name EXTENDED_ALG appears in the Select Device list box. Selecting EXTENDED_ALG presents a list of all extended algorithms available (if any). On the UniSite, the ALG.SYS file can be located on either the system or algorithm disk. ~0822 \bKEEP CURRENT ALGORITHMS\b The Keep Current feature allows access to special premium algorithms stored in files with the extension .KC? (where ? is a revision number). On a programmer that supports the Keep Current service, the special manufacturer name KEEP_CURRENT appears in the Select Device list box. Selecting KEEP_CURRENT presents a list of all Keep Current devices available (if any). On the UniSite, the Keep Current files can be located on either the system or algorithm disk. ~0830 \bPRODUCTION MODE\b PROMlink-6 can be run in a restricted-access mode in which loading Tasks and processing devices are the only operations that can be performed. Production Mode can be entered by starting PROMlink-6 with a "P" or "p" argument on the DOS command line. For example, typing "PL P" will start PROMlink-6 in Production Mode. ~0831 \bBATCH MODE\b PROMlink-6 can be run in a "one-job only" mode in which PROMlink-6 starts up, a single Task is loaded, one or more devices are processed, and PROMlink-6 exits back to DOS. This mode is useful if you are iteratively developing data for a programmable device using other PC software tools and need to program a new device frequently. To use this mode, create the Task to be used in PROMlink-6's normal mode and exit PROMlink-6. To start PROMlink-6 in batch mode, add the Task file name (optional) and the name of the Task separated by a double colon on the DOS command line. The file::Task specifier must be enclosed in double quotes. PL "TASKFILE::TASKNAME" runs TASKNAME from file TASKFILE PL "TASKNAME" runs TASKNAME from last Task file used This command can be placed in a DOS batch file or in a script file for a "make" utility. Note that to use the Task file specifier you should not create Tasks with two consecutive colons in their names. ~0840 \bPLFILES DOS ENVIRONMENT VARIABLE\b If you wish to run PROMlink-6 from a directory other than the one in which the PROMlink-6 files are located, you should place the following line in your AUTOEXEC.BAT file: set PLFILES=pathname "pathname" is the name of the directory in which the PROMlink-6 files are located. You should also add "pathname" to the PATH statement in AUTOEXEC.BAT. PROMlink will look for each of its support files first in the current directory. If the file is not found, PROMlink will look in the directory defined by PLFILES. The PROMlink-6 installation program will automatically make the necessary changes to your AUTOEXEC.BAT file if you allow it. ~0850 \bCONGIFURATION FILE CONVERSION\b The PROMlink program prior to Version 6.00 used "configuration files" to store various PROMlink setups. PROMlink-6 no longer uses the same configuration files, but now has Task files, which provide an even more convenient method of storing job information. If you have been using PROMlink prior to Version 6.00, and have generated a number of configuration files, Data I/O has developed a conversion utility called CFN2TSK.EXE that will create a single Task file out of many old-PROMlink configuration files. After conversion, your old jobs will be available in the Task selection window in PROMlink-6. Selecting a Task in PROMlink-6 completely configures the programmer for performing the job (even loading a data file if necessary). After loading a Task, all you need to do is put devices in the programmer socket. To run CFN2TSK, just type CFN2TSK at the DOS prompt. CFN2TSK will prompt you for the information it needs. When you have completed the conversion and have verified that the new Tasks work, you may delete the old configuration files. ~0851 \bPC INTERRUPT CONGIFURATION\b The successful installation of PROMlink-6 may require some modification of your PC's hardware configuration due to conflicts in the use of PC hardware interrupts. PROMlink uses one serial port to communicate with the programmer. Another serial port may be used to connect to a remote host computer. Either port may be assigned to PC serial port COM1 or COM2, which use interrupts IRQ4 and IRQ3 respectively. For each serial port used, there MUST BE NO other hardware in the PC that can generate interrupts on the same IRQ line. If you are not going to use a host computer connection, it is recommended that PROMlink-6's Host Port be set to "None" (the default). If you are using a serial mouse, you should make sure that neither the Programmer Port nor the Host Port are using the same COM port as the mouse (this means you cannot use a serial mouse and a remote host connection at the same time). ~0852 \bSERIAL MOUSE USE\b If you are using a serial mouse (a mouse that connects to one of the PC's serial ports), you should make sure that the neither the Programmer Port nor the Host Port in PROMlink-6 are assigned to the same COM port that the mouse is using. Since PROMlink-6 requires a serial port for communication with the programmer, use of a serial mouse dictates that you have two serial ports installed in the PC. If you have two serial ports, the following procedure should result in successful operation: \bþ\b Set the Programmer Port in PROMlink-6 to whichever COM port is NOT being used by the serial mouse. \bþ\b Set the Host Port in PROMlink-6 to "None". Use of a serial mouse prevents the use of PROMlink-6's host download option. ~1002 MSG \bCONTINUITY TEST FAIL\b The Continuity Test Fail (or Device Not Enabled) message appears under the following conditions: \bþ\b The device socket is not in the locked position. \bþ\b The device is inserted backwards. \bþ\b The device is not correctly justified in the socket. \bþ\b The device pins are not making contact. Check the position of the device in the socket and try the operation again. If the problem persists, replace the device. ~1003 MSG \bNON-BLANK\b The Non-blank message appears when the programmer performs a blank check operation and detects that a location in the device is not blank (has been programmed). ~1004 MSG \bILLEGAL BIT\b The Illegal Bit message appears when the programmer performs an illegal bit check and detects that a location in the device is programmed to the non-blank state when the data in programmer RAM indicates that the location should not be programmed. If possible, erase the device; otherwise, use a new device. ~1005 MSG \bPROGRAM FAIL\b The Program Fail message appears during programming when the programmer is unable to program a location to the state indicated in programmer RAM. This message indicates a defective device. Replace the device. ~1006 MSG \bVERIFY FAIL\b The Verify Fail message appears during array verification when a device location is found that does not match the data in programmer RAM. \s1ETwo-pass Verify\q Specifies two verify passes: one at the maximum Vcc voltage; and one at the minimum Vcc voltage. \s1EOne-pass Verify\q Specifies one verify pass at the nominal Vcc voltage. ~1008 MSG \bFUNCTIONAL TEST FAIL\b The Functional Test Fail message appears when the programmer has detected an error during a functional test (structured test vectors) on a logic device. \s1ETwo-pass Verify\q Specifies two verify passes: one at the maximum Vcc voltage; and one at the minimum Vcc voltage. \s1EOne-pass Verify\q Specifies one verify pass at the nominal Vcc voltage. ~1010 MSG \bSECURITY FUSE PROGRAM FAIL\b The Security Fuse Program Fail message appears when the programmer is unable to program the device's security fuse. This message indicates a defective device. Replace the device. ~1011 MSG \bSECURITY FUSE VIOLATION\b The Security Fuse Violation message appears when an attempt is made to load, program or verify a device that has a programmed security fuse. ~1012 MSG \bDEVICE OVERCURRENT\b The Device Overcurrent message appears during a device operation when a device draws more current than the maximum-allowable current for the device. This message indicates a defective device. Replace the device. ~1013 MSG \bERASE FAIL\b The Erase Fail message appears when the programmer is unable to erase an electrically erasable (EE) device. This message indicates a defective device. Replace the device. ~1014 MSG \bELECTRONIC ID ERROR\b The Electronic ID Error message appears when the electronic ID read from the device does not match the expected ID. The Electronic ID message appears under the following conditions: \bþ\b The incorrect device type is installed in the socket. \bþ\b The incorrect device type is selected in PROMlink-6. \bþ\b The device is defective. Verify that the installed and selected device types are correct. If the error persists, replace the device. ~1015 MSG \bALGORITHM-SPECIFIC ERROR\b The Algorithm-Specific Error is a generic error generated by the device programming algorithm. PROMlink-6 is unable to determine the source of the problem. ~1016 MSG \bLOGIC FINGERPRINT TEST FAIL\b The Logic Fingerprint Test Fail message indicates one of the following: \bþ\b The device failed the Fingerprint test. \bþ\b The Logic Fingerprint test sum is incorrect. \bþ\b The device cannot be tested with Logic Fingerprint. See the \bLogicPak User Manual\b for limitations on Logic Fingerprint. ~1020 MSG \bDEVICE DISABLE ERROR\b The Device Disable Error message appears when the programmer detects that the device is unable to tristate all of its data pins. This message indicates a defective device. Replace the device. ~1021 MSG \bDEVICE ENABLE ERROR\b The Device Enable Error message appears when the programmer detects that one or more of the device's data pins are not driving when the device is enabled. This message indicates a defective device. Replace the device. ~1022 MSG \bDATA SHORT\b The Data Short message appears when the programmer detects that one or more of the device's data pins are shorted. This message indicates a defective device. Replace the device. ~1023 MSG \bADDRESS SHORT\b The Address Short message appears when the programmer detects that one or more of the device's address pins are shorted. This message indicates a defective device. Replace the device. ~1024 MSG \bDATA BUS FAIL\b The Data Bus Fail message appears when the programmer detects that the device's data bus is defective. This message can also result from poor contact between the device pins and the socket. Check that the device is properly installed in the socket. If the error persists, replace the device. ~1025 MSG \bINCORRECT MODULE/ADAPTER\b The Incorrect Module/Adapter message appears when an adapter, module, or programming rail required for programming the selected device is not installed. Install the correct programming hardware and try the operation again. ~1026 MSG \bINSUFFICIENT PIN DRIVERS\b The Insufficient Pin Drivers message appears when the programmer does not have a sufficient number of pin drivers installed to perform an operation on the selected device. Contact Data I/O for an upgrade to your programmer hardware. ~1027 MSG \bDEVICE SELECTION ERROR\b The Device Selection Error message appears when an attempt is made to select a device type that is not supported on the current programmer. If you have recently updated your programmer, and the programmer supports automatic device support uploading (the Device List Update option appears in the Utilities menu), run the Device List Update utility to ensure that the device file matches the programmer device support and try selecting the device again. If you are using a Data I/O family and pinout code to select the device, check that the family and pinout code is valid for the current programmer. ~1028 MSG \bEND OF RAM EXCEEDED\b The End of RAM Exceeded message appears when programmer RAM size is insufficient to perform the current operation using the specified begin RAM address, block size and/or set size. Check that the begin RAM address, block size and/or set size are set correctly. ~1029 MSG \bI/O TIMEOUT\b The I/O Timeout message appears when the specified time elapses before the programmer begins receiving data during a host (remote computer) download. Set the amount of time the programmer waits for data before issuing an I/O Timeout message by selecting the I/O Timeout option from the Options menu. ~1030 \bPROGRAMMER SERIAL PORT ERRORS\b There are three types of serial port errors: \bþ\b Framing Error \bþ\b Parity Error \bþ\b Overrun Error Combinations of the above errors can occur. \s1AFraming Error\q The Framing message appears when the serial port detects a start bit, but the stop bit is positioned incorrectly. Check that the baud rates of the PC and programmer are the same and that you are using the correct serial cable. \s1AParity Error\q The Parity message appears if the serial port detects a parity error in incoming data. Check that the parity settings for the PC, programmer and host (remote computer) are the same. \s1AOverrun Error\q The Overrun message appears when incoming data overflows the programmer's receive buffer. Check that the selected baud rate is compatible with the current programmer. Some programmers may have difficulty receiving data at speeds greater than 9600 baud. ~1031 MSG \bSUMCHECK ERROR\b The Sumcheck Error message appears when the sumcheck of the data received by the programmer during a host (remote computer) download does not match the sumcheck that is sent along with the data. In some I/O formats, transmission and/or fuse map sumchecks are part of the transmitted data records. The programmer compares those sumchecks with the sumchecks it calculates on the incoming data. A Sumcheck Error message is generated if the sumchecks do not match. If a Sumcheck Error message appears, try the operation again. If the error persists, the problem is most likely an invalid data file or, less likely, errors in transmission. The Sumcheck Error message can also appear when using format 16 in the Create File From RAM option. Retry the operation. ~1032 MSG \bI/O FORMAT ERROR\b The I/O Format Error message appears when the programmer is unable to translate incoming data due to an incompatibility with the selected I/O format. Check the source file for compatibility with the selected format. See your programmer User Manual for a list of supported I/O formats. ~1033 MSG \bILLEGAL I/O FORMAT\b The Illegal I/O Format message appears under the following conditions: \bþ\b The selected I/O format is not available on the current programmer. \bþ\b The selected I/O format is incompatible with the selected device. Select an I/O format that is supported on the current programmer and is appropriate for the selected device. See your programmer User Manual for a list of supported I/O formats. ~1034 MSG \bI/O VERIFY ERROR\b The I/O Verify Error message appears when the data received does not match the data in programmer RAM. ~1035 MSG \bI/O INITIALIZATION ERROR\b The I/O Initialization Error message appears when an attempt to initialize the programmer's serial port fails. Check the serial cable connections and try again. ~1036 MSG \bNON-JEDEC DATA IN RAM\b The Non-JEDEC Data in RAM message appears when a device operation is attempted on a logic device and programmer RAM contains inappropriate data. Load RAM with an appropriate JEDEC data file or master device. This message can also appear when you attempt to upload JEDEC format data from the programmer and a non-logic device is selected. ~1037 MSG \bINVALID COMMAND\b The Invalid Command message appears when the programmer receives a command from PROMlink-6 that it cannot interpret. Try the operation again. ~1038 MSG \bEND OF DEVICE EXCEEDED\b The End of Device Exceeded message appears when there is not enough memory in the selected device to hold the amount of data specified. The Begin Device address may be set too high, the Device Block size may be too large, or you may need to select a device with more memory. Although the operation may still be performed, only part of the data will be programmed into the device. ~1039 MSG \bI/O FORMAT EXCEEDED\b The I/O Format Exceeded message appears when an address field in the data to be output from the programmer exceeds the maximum value allowed in the address field of the selected I/O format. Select an I/O format that supports the desired address range or reduce the I/O Offset and/or I/O Block size to achieve addresses within the range of the selected I/O format. See your programmer User Manual for a list of supported I/O formats. ~1040 MSG \bPRELOAD NOT SUPPORTED\b The Preload Not Supported message appears when preload vectors are applied to a logic device that does not support preload. Remove the preload vectors or choose a device type that supports preload. ~1041 MSG \bCRC DEFAULT RESTORE FAIL\b The CRC Default Restore Fail message appears when an attempt to save or restore CRC default parameters to or from the programmer disk fails. ~1042 MSG \bPROGRAMMER FILE ERROR\b The Programmer File Error message appears when a disk file error occurs during a command that accesses the programmer's disk drive. If the operation requires a filename, make sure the filename is valid. If the operation requires writing to the disk, make sure the disk is not write-protected. ~1043 MSG \bBLOCK MOVE ERROR\b A Block Move error occurs when a block move within RAM exceeds the RAM boundaries. Check the begin address and block size and try the operation again. ~1044 MSG \bEND OF FILE EXCEEDED\b The End of File Exceeded message appears when the specified memory block size and begin address parameters are too large for the intended data file. Change the block size and begin address so they are small enough to accommodate the data file. ~1045 MSG \bALGORITHM DISK NOT FOUND\b The Algorithm Disk not Found message appears when an attempt is made to select a device without the Algorithm disk in the drive. Insert the Algorithm disk and attempt the operation again. ~1046 MSG \bINCOMPATIBLE DISKS\b The Incompatible System and Algorithm Disks message appears when the version number of the Algorithm disk does not match the version number of the System disk. Insert the correct version of the Algorithm disk and attempt the operation again. ~1047 MSG \bINVALID COMMAND FOR MODE\b The Invalid Command for Mode message appears when a gang or set operation is attempted on a device that does not support gang programming. Select a different device type. ~1048 MSG \bELECTRONIC ID NOT SUPPORTED\b The Electronic ID Not Supported message appears when an attempt is made to read the electronic ID of a device that does not contain an electronic ID. Disable the electronic ID option or change devices. ~1049 MSG \bUNABLE TO LOAD SYSTEM FILE\b The Unable to Load System File message appears when an attempt is made to exit or suspend Computer Remote Control mode without the system disk installed in the disk drive. Check that the system disk is in the drive when you exit CRC. ~1050 MSG \bSOFTWARE SECURITY VIOLATION\b The Software Security Violation message appears when an attempt is made to use a version of system software that has not been installed yet. Perform the Update from the programmer's terminal interface to install the new version of software. ~1052 MSG \bPARTIAL DEVICE OPERATION\b The Partial Device Operation Not Allowed message appears when block limits other than the defaults are used for a device that only supports the defaults. Set the block size equal to, or greater than, the device size (or to 000000, which defaults to the device size). ~1053 MSG \bODD BEGIN ADDRESS NOT ALLOWED\b The Odd Begin Address Not Allowed message appears when the Begin Device address is set to an odd number and you attempt a device operation on a 16-bit (or larger) device. Set the Begin Device address to an even number. ~1054 MSG \bRAM FILE BUFFER EXCEEDED\b The RAM File Buffer Exceeded message appears when you attempt to write data beyond the end of a previously allocated RAM File. ~1055 MSG \bRAM FILE NOT FOUND\b The RAM File Not Found message appears when you attempt to perform an operation with a RAM file and the programmer cannot find the RAM file. ~1056 MSG \bRAM FILE CREATE ERROR\b The RAM File Create Error message appears when an attempt to create a RAM file fails. Possible explanations for this are \bþ\b An illegal filename was used \bþ\b A RAM file with the same name already exists ~1057 MSG \bRAM FILE SPACE EXHAUSTED\b The RAM File Space Exhausted message appears when an attempt to create a RAM file fails. Possible explanations for this are \bþ\b There is not enough RAM space left \bþ\b There are not enough directory entries left ~1058 MSG \bPORT TRANSFER ERROR\b The Port Transfer Error message appears when an attempt is made to transfer data through a serial port that is not properly connected. Check that the serial port is properly connected. ~1059 MSG \bUNDEFINED CRC ERROR\b The Undefined CRC Error message appears when the programmer encounters an error that it cannot categorize. Document the circumstances which created the error and contact Data I/O. (See the Technical Assistance topic in the Help Index.) ~1060 MSG \bOPERATION ABORTED\b The Operation Aborted message appears when an operation is stopped midprocess. This message appears on \bþ\b UniSite/SetSite when the socket lever is moved to the OPEN (stop) position during a device operation. \bþ\b The Series 1000 when the socket dial is turned to the OPEN position during a device operation. ~1061 MSG \bNO FUNCTIONAL TEST DATA\b The No Functional Test Data message appears when the Verify Options parameter is set for Functional Test Only and no test vectors are loaded in programmer RAM (and, on programmers with Logic Fingerprint capability, the number of Logic Fingerprint test cycles is zero). Change the Verify Options parameter (in the Logic Parameters dialog box accessed in a Task menu by selecting the < More... > pushbutton) or resolve the undefined vectors or Logic Fingerprint cycle count. ~1062 MSG \bLOGIC OPTION\b The Logic Option message appears when a logic-related function is requested and a memory adapter is installed. Choose a different function or change the adapter. ~1063 MSG \bMEMORY OPTION\b The Memory Option message appears when a memory-related function is requested and a logic adapter is installed. Choose a different function or change the adapter. ~1064 MSG \bWORD WIDTH ERROR\b The Word Width Error message appears when the selected word width is not an integer multiple of the word width of the selected device. For example, a word width of 24 is invalid for a 16-bit device. Some valid word widths for a 16-bit device are 32, 48, and 64. Select a word width that is an integer multiple of the selected device word width. ~1065 MSG \bTWO MASTERS\b The Two Masters message appears when two master devices are detected, one in each rail. Remove one of the master devices. ~1066 MSG \bNO DEVICES PRESENT\b The No Devices Present message appears during a programming or verification operation when the programmer detects no devices in the sockets. Insert the device(s). ~1067 MSG \bINVALID SET\b The Invalid Set message appears during a load, program, or verify operation. During a load operation, the message appears when the number of devices present (or that passed device testing) is less than the number of devices in the set. During a program or verify operation, the message appears when the number of devices in the set exceeds the number of device sockets. The Invalid Set message may also appear if the selected device (such as a microprocessor) does not support set operations. ~1068 MSG \bSYNC ENABLED\b The Synchronous Programming Enabled message appears when synchronous programming is disabled and an attempt is made to verify a device that was programmed with synchronous programming enabled. Enable synchronous programming and try the operation again. ~1069 MSG \bSYNC DISABLED\b The Synchronous Programming Disabled message appears when synchronous programming is enabled and an attempt is made to verify a device that was programmed with synchronous programming disabled. Disable synchronous programming and try the operation again. ~1070 MSG \bDEVICE CHECK FAIL\b The Device Check Fail message appears under the following conditions: \bþ\b The device is incorrectly installed in the socket \bþ\b The incorrect device type is selected \bþ\b The security bit is programmed ~1071 MSG \bSOURCE/DESTINATION ERROR\b The Source/Destination Error message appears when an illegal source or destination key sequence is entered. ~1072 MSG \bILLEGAL RAM PAGE\b The Illegal RAM Page message appears when the attempted operation requires a 16K RAM page change that the present Pak software does not support. Either modify RAM or the block size so that the first and last bytes of the operation reside in the same 16K range, or contact Data I/O for a Pak software update. ~1073 MSG \bPROGRAMMING PAK RESET\b The Programming Pak Reset message appears when the programming electronics will not start an operation due to a reset condition. This message is usually caused by an overcurrent condition caused by an incorrectly-inserted or bad device in the socket. ~1074 MSG \bDATA LOCKED\b The Data Locked message appears when data is locked (prevented from being changed) by Select Function F3. Use the password to release the data lock. ~1075 MSG \bILLEGAL CENTERPOINT\b The Illegal Centerpoint message appears when an illegal centerpoint is specified for a RAM split or shuffle operation. The specified RAM Midpoint must be a power of two between address "2" and the midpoint of installed programmer RAM. ~1076 MSG \bODD RAM LIMIT\b The Odd RAM Limit message appears when an odd RAM address is set for a device operation with a word-wide device. Check the address and try the operation again. ~1077 MSG \bNO BLOCK SIZE\b The No Block Size message appears when no block size is set for a device operation with a word-wide device. Check the set block size and try the operation again. ~1078 MSG \bDEFECTIVE DEVICE\b The Defective Device message appears when the programmer determines that the device does not meet the manufacturer's specifications. Replace the device. ~1079 MSG \bBURIED REGISTER ERROR\b The Buried Register error occurs when proper sequencing is not followed in the applied structured test vectors. ~1080 MSG \bILLEGAL FUSE DATA\b The Illegal Fuse Data message appears when one or more fuse states in programmer RAM are illegal for the particular device selected. Correct fuse data in RAM to meet manufacturer's requirements. ~1081 MSG \bVCC ERROR\b The Vcc Error message appears when the programmer applies voltage to the device's Vcc pin and the voltage drops to an unacceptable level. This message indicates a defective device. Replace the device. ~1082 MSG \bVPP ERROR\b The Vpp Error message appears when the programming power supplies cannot be set to the proper levels. This message indicates a defective device. Replace the device. ~1083 MSG \bBEGIN RAM POINTER NON-ZERO\b The Begin RAM Pointer Non-zero message usually occurs when changing from one programming Pak to another. Refer to the programmer manual to reset the begin RAM pointer to zero. ~1084 MSG \bINVALID DEVICE OPERATION\b The Invalid Device-related Operation message appears when a program, verify, or other device operation is attempted with a design adapter installed. Choose a command appropriate for the installed adapter, or a programming/testing (P/T) adapter. ~1085 MSG \bNO FUSE VERIFY SET\b The No Fuse Verify Set message appears when an attempt is made to program a device with the verify option set to 2. Set the verify option to 0 or 1 and try the operation again. ~1086 MSG \bLOGIC FINGERPRINT NOT ALLOWED\b The Logic Fingerprint Not Allowed message appears when an attempt is made to perform a Logic Fingerprint test on a device that does not support Logic Fingerprint testing. Set the number of Logic Fingerprint cycles to zero. ~1087 MSG \bALGORITHM SET 1 NOT FOUND\b The Algorithm Set 1 Not Found message appears when an attempt is made to select a device whose algorithm is stored on an Algorithm disk that is not inserted in the programmer's disk drive. Insert the correct Algorithm Disk and retry the operation. ~1088 MSG \bALGORITHM SET 2 NOT FOUND\b The Algorithm Set 2 Not Found message appears when an attempt is made to select a device whose algorithm is stored on an Algorithm disk that is not inserted in the programmer's disk drive. Insert the correct Algorithm Disk and retry the operation. ~1089 MSG \bSYSTEM DISK NOT FOUND\b The System Disk Not Found message appears when an attempt is made to perform an operation that requires the system disk to be installed in the programmer, and the disk is not installed. Install the system disk in the drive and try the operation again. ~1090 MSG \bALGORITHM SET 3 NOT FOUND\b The Algorithm Set 3 Not Found message appears when an attempt is made to select a device whose algorithm is stored on an Algorithm disk that is not inserted in the programmer's disk drive. Insert the correct Algorithm Disk and retry the operation. ~1091 MSG \bINCOMPLETE FILE SET\b The Incomplete File Set message appears when, during device selection, all of the necessary files are not found on the mass storage module. Update the algorithms on the mass storage module (must be done from the Programmer Interface) and try the operation again. ~1100 MSG \bPROGRAMMER HARDWARE FAILURE\b For all Programmer Hardware Failure messages, note the exact text of the message and refer to your programmer User Manual for more information. ~1101 MSG \bHARDWARE SELF-TEST\b The Hardware Did Not Pass Self-test message appears when the programmer does not pass self-test upon powerup. Check the following: \bþ\b Modules and adapters are installed correctly. \bþ\b There are no devices in any of the sockets. Then \bþ\b Power down the programmer. \bþ\b Power up the programmer. If the error persists \bþ\b Check the self-test screen in the programmer's terminal menus. ~1102 MSG \bMASTER INSERTION ERROR\b The Master Insertion Error occurs when either the master device has been inserted incorrectly or is not present (if the operation requires a master). Correctly insert the master device. ~1500 \bHELP FOR HELP\b PROMlink-6 features extensive online documentation. You can access this online documentation in two ways: \bþ\b General Help Index \bþ\b Context-sensitive help \s1AGeneral Help Index\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ To access the General Help Index, select Help (\bAlt\b+\bH\b) from the main screen menu then select \bGeneral Help Index\b. The index lists help topics alphabetically. To access the online documentation on any topic, use the arrow keys to highlight the topic. Press Enter or click the mouse on the < OK > pushbutton at the bottom of the General Help Index dialog box. Mouse users can double-click on the help topic. \s1AContext-sensitive Help\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ To access context-sensitive help press \bF1\b, click the mouse on the < F1=Help > pushbutton in the lower right-hand corner of the screen, or just press the right mouse button. Context-sensitive help provides further information on the currently-highlighted item. Help information appears in a window titled PROMlink-6 Help. The current help topic appears at the top of the text in boldface. If there is more information than can be displayed on one page, a scroll bar appears on the right side of the window. To exit Help press \bEnter\b, \bEsc\b or \bSpace\b or click the mouse on the < OK > pushbutton. ~1510 \bKEYS HELP\b The following is a description of the keys most commonly used to run PROMlink-6. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ \s1AKey\q ³ \s1AFunctions\q ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ \bTab\b ³ Move the highlight in a dialog box. ³ ³ \bShift\b+\bTab\b ³ \bTab\b moves forward to the next selection, ³ ³ ³ and \bShift\b+\bTab\b moves backward to the ³ ³ ³ previous selection. ³ ³ ³ ³ ³ \bEnter\b ³ Accepts the current selections in a ³ ³ ³ dialog box and accepts the default action ³ ³ ³ button (highlighted brackets). In a ³ ³ ³ multiple-line text entry field, \bEnter\b ³ ³ ³ moves the cursor to the beginning of the ³ ³ ³ next line or to the next selection set. ³ ³ ³ ³ ³ \bEsc\b ³ Cancels a dialog box without saving ³ ³ ³ any changed values and cancels an ³ ³ ³ operation in process. ³ ³ ³ ³ ³ \bSpace\b ³ Toggles the state of a check box item. ³ ³ ³ ³ ³ \bF1\b ³ Accesses context-sensitive help. ³ ³ ³ ³ ³ \bF2\b ³ Accesses a drop-down list. ³ ³ ³ From the main screen, presents a list of ³ ³ ³ parameters set to non-default values. ³ ³ ³ ³ ³ Arrow keys ³ Move the highlight within a bulleted list ³ ³ ³ in a dialog box. In a scrolling window ³ ³ ³ the arrow keys move text up or down one ³ ³ ³ screen. ³ ³ ³ ³ ³ \bHome\b ³ Move the cursor to the beginning of the ³ ³ \bEnd\b ³ list, end of the list, up one screen or ³ ³ \bPgUp\b ³ down one screen, respectively ³ ³ \bPgDn\b ³ ³ ³ ³ ³ ³ \bAlt\b+\bletter\b ³ Selects a pull down menu from the main ³ ³ ³ screen menu. ³ ³ ³ ³ ³ \bCtrl\b+\bletter\b ³ Selects a menu option without having to ³ ³ ³ go to that menu. The available ³ ³ ³ combinations are ³ ³ ³ ³ ³ ³ Select Device \bCtrl\b+\bD\b ³ ³ ³ Load RAM from Master \bCtrl\b+\bL\b ³ ³ ³ Load RAM from File \bCtrl\b+\bF\b ³ ³ ³ Create File from RAM \bCtrl\b+\bC\b ³ ³ ³ Process Devices \bCtrl\b+\bP\b ³ ³ ³ Load Task \bCtrl\b+\bT\b ³ ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ~1520 \bDIALOG BOX\b A dialog box is the window that appears when you select a menu option that is followed by an ellipsis (...). A dialog box offers at least one entry field or group of choices. A dialog box may offer a sub-dialog box, for example the < More... > pushbutton offered in the Edit Task dialog box. The following is a brief description of the items found in a dialog box and how to use them: \s1APushbutton\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ An pushbutton is a string of text enclosed in angle brackets (<>). The most common examples are the < OK > and < Cancel > pushbuttons. To select an pushbutton using the keyboard, press \bTab\b or \bShift\b+\bTab\b until the pushbutton is highlighted then press \bSpace\b or \bEnter\b. To select an pushbutton with the mouse, use the mouse to position the cursor on the pushbutton and click the left mouse button. If the angle brackets on the pushbutton are highlighted all the time (even when the pushbutton isn't) and no other pushbutton is currently highlighted, the button, representing the "default action" of the dialog box, can be selected from anywhere in the dialog box (except a multi-line entry field) by pressing \bEnter\b. \s1ARadio Button\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ A radio button is represented by two parentheses with a space between them ( ) when unselected and two parentheses with a dot between them () when selected. Radio buttons are used when only one item out of a group can be selected. To select a radio button using the keyboard, press \bTab\b or \bShift\b+\bTab\b to reach the group of radio buttons. The currently-selected radio button will be highlighted. Use the arrow keys to move within the group of radio buttons. The arrow keys will move the highlight (and the dot) between the buttons in the group. To select a radio button with the mouse, use the mouse to position the cursor on the radio button (or the text next to the button) and click the left mouse button. \s1ACheck Box\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ A check box appears as a two square brackets with a space between them [ ] when "off" (not enabled). The check box appears as two square brackets with an X between them [X] when "on" (enabled). Check Boxes toggle On and Off with \bSpace\b. To toggle a check box with the mouse, use the mouse to position the cursor on the check box (or the text next to the check box) and click the left mouse button. \s1AList Box\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ List boxes are used to provide selection of an item from a large list of options. To select an item from a list box, press \bTab\b to enter the box, and use the arrow keys to move the highlight bar between the list options. If there are more options than can be displayed in the list box (indicated by the presence of a scroll bar), the \bPgUp\b and \bPgDn\b keys scroll the list one screen. \bHome\b and \bEnd\b move to the beginning and end of the list. Mouse users can highlight a list box item by clicking on the item. If a scroll bar is present, the mouse can be used to drag the scroll bar marker to move rapidly within the list. \s1AEntry Field\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ An entry field is a dialog box item that allows keyboard entry of text and numeric values. When an entry field is highlighted, a cursor appears in it. At this time you can type characters into the field. If you have just entered the field and begin typing, the existing contents of the field are automatically erased. \bHome\b moves the cursor to the beginning of the text. \bEnd\b moves the cursor to the end of the text. Use \bBackspace\b and \bDel\b to overtype and delete characters. \bIns\b toggles insert/overtype mode. \s1ADrop-Down List\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ A drop down list is a dialog box item that appears as a single selection field containing the current value of the item. At the far right end of the field is a single down arrow  indicating a list of values to pick from is available. To access the list, press \bF2\b. A dialog box containing a list box will appear. Upon selecting an item from the list, the dialog box will disappear and the new value will appear in the status line. Mouse users can access the drop-down list by clicking the mouse on the down arrow or by double-clicking anywhere on the status line. ~2001 \bCUSTOMER SUPPORT OFFICES\b \s1AUnited States\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, contact \bData I/O Customer Resource Center\b Telephone: 800 247-5700 Fax: 206 882-1043 For warranty service or Keep Current subscription service, contact your nearest Data I/O Service Center below: \bData I/O Corporate Office\b 10525 Willows Road N.E. P.O. Box 97046 Redmond, WA 98073-9746 Telephone: 206 881-6444 Fax: 206 882-1043 Telex: 152167 \bData I/O California\b 1701 Fox Drive San Jose, CA 95131 Telephone: 408 437-9600 Fax: 408 437-1218 \bData I/O Northeastern United States\b 20 Cotton Road Nashua, NH 03063 Telephone: 603 889-8511 800 858-5803 (NJ & NY only) Fax: 603 880-0697 \s1ACanada\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, contact: \bData I/O Customer Resource Center\b Telephone: 800 247-5700 Fax: 206 882-1043 For warranty service or Keep Current subscription service, contact: \bData I/O Canada\b 6725 Airport Road, Suite 302 Mississauga, Ontario, L4V 1V2 Telephone: 416 678-0761 Fax: 416 678-7306 \s1AUnited Kingdom\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, warranty service, or Keep Current subscription service, contact: \bData I/O Limited\b 660 Eskdale Road Winnersh, Wokingham Berkshire RG11 5TS Telephone: 0734 440011 Fax: 0734 448700 \s1AJapan\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, warranty service, or Keep Current subscription service, contact: \bData I/O Japan\b Sumitomoseimei Higashishinbashi Bldg. 8F 2-1-7, Higashi-Shinbashi Minato-Ku, Tokyo 105 Telephone: 03 3432-6991 Fax: 03 3432-6094 (Sales) 03 3432-6093 (Other) Telex: 2522685 DATAIO J \s1AGermany\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, warranty service, or Keep Current subscription service, contact: \bData I/O Electronic Systems Vertriebs GmbH\b Lochhammer Schlag 5a D-8032 Gr<132>felfing Telephone: 089 858580 Fax: 089 8585810 \s1AOther European Countries\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, warranty service, or Keep Current subscription service, contact the office below and ask for the number of your local Data I/O representative: \bData I/O Europe\b World Trade Center Strawinskylaan 537 1077 XX Amsterdam, The Netherlands Telephone: +31 (0)20 6622866 Fax: +31 (0)20 6624427 \s1AOther Countries Worldwide\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ For technical assistance, warranty service, or Keep Current subscription service, contact the office below and ask for the number of your local Data I/O representative: \bData I/O Intercontinental\b 10525 Willows Road N.E. P.O. Box 97046 Redmond, WA USA 98073-9746 Telephone: 206 881-6444 Fax: 206 882-1043 Telex: 4740166 ~2002 \bTECHNICAL ASSISTANCE\b \s1ACalling\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ To help us provide quick and accurate assistance, please be at your programmer or computer when you call, and have the following ready: \bþ\b Product version number \bþ\b Product serial number (if available) \bþ\b Detailed description of the problem you are experiencing \bþ\b Error messages (if any) \bþ\b Device manufacturer and part number (if device-related) \bþ\b Product manual For technical assistance, see the Customer Support Offices topic in the Help Index. \s1AElectronic Mail\q ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ You can also reach Data I/O via electronic mail (e-mail). To help us provide quick and accurate assistance, please include the information listed above. Also, include your name, phone number, and e-mail address in your message, and send it to one of the following addresses: techhelp@Data-IO.COM or {apple|decwrl|rutgers|gatech|uunet}!pilchuck!techhelp \s1ANote:\q Select one of the five addresses listed above in braces. For example, you might send e-mail to the following address: \buunet!pilchuck!techhelp\b See your system administrator if you need more information on which address to use. ~2003 \bWARRANTY INFORMATION\b Data I/O Corporation warrants this product against defects in materials and workmanship at the time of delivery and thereafter for a period of ninety (90) days. The foregoing warranty and the manufacturers' warranties, if any, are in lieu of all other warranties, expressed, implied or arising under law, including, but not limitied to, the implied warranties of merchantability and fitness for a particular purpose. Data I/O maintains customer service offices throughout the world, each staffed with factory-trained technicians to provide prompt, quality service. For warranty service, see the Customer Support Offices topic in the Help Index. ~2004 \bKEEP CURRENT SUBSCRIPTION SERVICE\b Data I/O offers a one-year subscription to keep your product and documentation up-to-date with the latest features and device support. This subscription also incorporates manufacturer-recommended changes to existing device support to maintain optimum yields, throughput, and long-term reliability. For more information, or to order a Keep Current subscription service, see the Customer Support Offices topic in the Help Index. ~2005 \bBULLETIN BOARD SERVICE\b From the Data I/O Bulletin Board System (BBS) you can obtain a wide range of information on Data I/O products, including current product descriptions, new revision information, technical support information, helpful application notes, and other miscellaneous information. In addition, the BBS has a large collection of useful DOS utilities you can download. The BBS message facility allows you to leave messages for the BBS system operator, Customer Support personnel, or other customers. Functions are available to provide device support information or to request support for a particular device. To learn more about the U.S. Data I/O BBS, call 1-206-882-3211. Multiple lines are available, all supporting 1200/2400/9600/19200 baud with U.S. Robotics Courier HST modems with V.42bis compatibility, set to 8 data bits, 1 stop bit and no parity. Call 1-206-861-6959 to contact the BBS connected to a U.S. Robotics Dual/HST modem supporting 1200/2400/9600/19200 baud with V.32bis/V.42bis compatibility. Online help files provide more information about the BBS and its capabilities. For your nearest Data I/O Bulletin Board System outside the U.S., see the Customer Support Offices topic in the Help Index. ~2006 \bEND USER REGISTRATION\b If the end user for this product or your address has changed since the Registration Card was mailed, please notify your nearest Customer Support office (see the Customer Support Offices topic in the Help Index). This ensures that you receive information about product enhancements. Be sure to include the product serial number, if available. ~2007 \bADDRESS CHANGE\b If the end user for this product or your address has changed since the Registration Card was mailed, please notify your nearest Customer Support office (see the Customer Support Offices topic in the Help Index). This ensures that you receive information about product enhancements. Be sure to include the product serial number, if available. ~2008 \bTYPOGRAPHIC CONVENTIONS\b Throughout the PROMlink-6 online documentation (Help) different typographic conventions represent different cases of input and output. \s1AKeyboard Keys\q Keyboard keys are shown in bold. For example, \bEnter\b \bTab\b \s1AKey Combinations\q Key combinations, such as \bCtrl\b+\bT\b are shown as two keys separated by a plus. For example, \bCtrl\b+\bL\b \bAlt\b+\bS\b \s1AOptional Input\q Optional parts of a command are shown in brackets. For example, \b[option1] [option2] . . . [optionN]\b Parts separated by a vertical bar (for example, OR|OR| . . . ) are mutually exclusive; that is, only one of the options listed can be specified. ~3005 NOINDEX \bUNISITE UNIVERSAL PROGRAMMING SYSTEM\b The UniSite Universal Programmer programs and tests all programmable intergrated circuits including FPGAs, PLDs, memories, and microcontrollers, in a single site. Universal pin drivers support every device pin so additional hardware adapters are not needed. The optional PinSite module expands device support to include surface-mount devices (SMDs) and pin-grid arrays (PGAs). Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3010 NOINDEX \bUNISITE SETSITE\b The UniSite SetSite module is an option to the UniSite. It provides set and gang programming support for up to eight 4 megabyte EPROMs and skinny or wide DIP EE/EPROMs to 40-pins. The SetSite closes and programs all eight sockets with one lever and also provides programming information for each socket. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3015 NOINDEX \b2900 PROGRAMMING SYSTEM\b The 2900 programs virtually all PLDs, memories and microcontrollers on the market. It features device support libraries that let you choose the level of support you need. These libraries include EPROMs, PROMs, E-micros and PLDs to 44 pins. The 2900 also features the new Matchbook carrier for PLCC and LCC devices that greatly improves the handling and programming of these surface mount devices. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3020 NOINDEX \b3900 PROGRAMMING SYSTEM\b The 3900 supports thousands of FPGAs, PLDs, memory devices, and microcontrollers up to 88 pins. For flexibility and affordability, this support is offered in device libraries so you pay only for the support you need when you need it. These libraries include memory, microcontrollers, PLDs and FPGAs up to 88-pins. The 3900 also features the Matchbook carrier for surface mount devices. Each Matchbook set accomodates an entire package family, replacing the traditional fragile, costly SMD sockets. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3030 NOINDEX \bSERIES 1000 PARALLEL PROGRAMMERS\b For programming memory and microcontroller devices in medium- to high-volume production environments, Series 1000 Parallel Programmers offer throughput as much as five times that of other parallel programmers. The programmer supports up to 30 devices at a time, utilizes fast test and verification routines, has four removable socket rails that support both DIP and PLCC packages and uses the latest programming algorithms. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3032 NOINDEX \bSERIES 1000LC\b Data I/O's Series 1000LC Parallel Programmer offers single rail low-cost gang programming support for small-to-medium-volume production environments. Based on the line of Series 1000 Parallel Programmers, this high-speed, high-reliability system supports up to 15 MOS/CMOS PROMs, EPROMs and EEPROMs up to one megabit in 24-, 28-, 32-, and 40-pin DIP and the equivalent PLCC packages. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3035 NOINDEX \b212 MEMORY SYSTEM\b The 212 Memory Programming System supports more than 400 24-, 28-, 32- and 40-pin MOS/CMOS EPROMs and EEPROMs up to four megabits. You can operate the 212 using the front panel keys, or remotely via a personal computer and the RS232C serial/ bidirectional parallel port. Optional modules support CMOS logic and microcontrollers. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3040 NOINDEX \b212 LOGIC SYSTEM\b The 212 Logic Programming System supports hundreds of 20- and 24-pin CMOS logic devices in DIP packages. The system comes complete with the 212 Multi Programmer; a logic programming module; and ABEL-PLD Design Software, an optimized version of industry-standard ABEL Design Software. Optional modules support EPROMs and microcontrollers. If you already own the 212 Memory Programming System, you can simply add the logic programming module and ABEL-PLD to get all the capability of the Logic Programming System. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3042 NOINDEX \b212 MICRO MODULE\b The 212 microcontroller programming module adds support for 874X and 875X microcontrollers to either the 212 Memory Programming System or the 212 Logic Programming System. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3045 NOINDEX \b288 32-PIN EPROM MODULE\b The 288A Multi Programmer is an eight-socket MOS device programmer with 512K Bytes standard RAM (expandable to 2 megabytes) and removable socket modules. The 32-pin EPROM Module supports 24-, 28-, and 32-pin MOS/CMOS EPROMs and EEPROMs up to four megabits in gang and set programming mode. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3050 NOINDEX \b288 40-PIN EPROM MODULE\b The 288A Multi Programmer is an eight-socket MOS device programmer with 512K Bytes standard RAM (expandable to 2 megabytes) and removable socket modules. The 40-pin EPROM Module for the 288 supports 40-pin MOS and CMOS megabit EPROMs/EEPROMS, up to eight at a time in gang and set programming mode. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3055 NOINDEX \b288 87XX MODULE\b The 288A Multi Programmer is an eight-socket MOS device programmer with 512K Bytes standard RAM (expandable to 2 megabytes) and removable socket modules. The 87XX module programs 874X and 875X single-chip microcontrollers up to eight at a time (including the security bit if desired). Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3060 NOINDEX \b288 28-6870X MODULE\b The 288A Multi Programmer is an eight-socket MOS device programmer with 512K Bytes standard RAM (expandable to 2 megabytes) and removable socket modules. The 286870X module programs Motorola's 28-pin 6870X family of microcontrollers, up to eight at a time. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3065 NOINDEX \b288 40-6870X MODULE\b The 288A Multi Programmer is an eight-socket MOS device programmer with 512K Bytes standard RAM (expandable to 2 megabytes) and removable socket modules. The 406870X module programs Motorola's 40-pin 6870X family of microcontrollers, up to eight at a time. Call 1-800-3-DATAIO (1-800-332-8246) today for more information. ~3070 NOINDEX \b29B UNIPAK\b The 29B with the UniPak installed supports EPROMs, PROMs and microcontrollers. The 29B/UniPak has been replaced by the new 2900 Programming System, 3900 Programming System or UniSite Universal Programming System depending on your programming needs. Call 1-800-3-DATAIO (1-800-332-8246) today for more information on trade-up opportunities. ~3075 NOINDEX \b29B LOGICPAK\b The 29B with the LogicPak installed supports PLDs. This system has been replaced by the new 2900 Programming System, 2900 Programming System or UniSite Universal Programming System depending on your programming needs. Call 1-800-3-DATAIO (1-800-332-8246) today for more information on trade-up opportunities.