The NAT7210™ integrated circuit (“equipment”) is warranted against defects in material
and workmanship under normal use and service for a period of one (1) year from the date
of shipment from the National Instruments factory. During this period of one year,
National Instruments shall at its sole option either repair, replace, or credit the Buyer for
defective equipment if: (i) Buyer returns the equipment to National Instruments, FOB the
National Instruments factory in Austin, Texas; (ii) Buyer notifies National Instruments
promptly upon discovery of any defect in writing, including a detailed description of the
defect; and (iii) upon examination of the returned equipment, National Instruments is
satisfied that the circuit is defective and that the cause of such defect is not alteration or
repair by someone other than National Instruments, neglect, accident, misuse, improper
installation, or use contrary to any instructions issued by National Instruments.
A Return Material Authorization (RMA) number must be obtained from the factory and
clearly marked on the outside of the package before any equipment will be accepted for
warranty work. Prior to issuance of an RMA by National Instruments, Buyer shall allow
National Instruments the opportunity to inspect the equipment on-site at Buyer’s facility.
This warranty expires one year from date of original shipment regardless of any warranty
performance during that warranty period. The warranty provided herein is Buyer’s sole
and exclusive remedy for nonconformity of the equipment or for breach of any warranty.
THE ABOVE IS IN LIEU OF ALL OTHER WARRANTIES EXPRESSED OR
IMPLIED. NATIONAL INSTRUMENTS SPECIFICALLY DISCLAIMS THE
IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A
PARTICULAR PURPOSE. BUYER’S RIGHT TO RECOVER DAMAGES CAUSED
BY FAULT OR NEGLIGENCE ON THE PART OF NATIONAL INSTRUMENTS
SHALL BE LIMITED TO THE AMOUNT THERETOFORE PAID BY THE BUYER.
NATIONAL INSTRUMENTS WILL NOT BE LIABLE FOR DAMAGES RESULTING
FROM LOSS OF DATA, PROFITS, USE OF PRODUCTS, OR INCIDENTAL OR
CONSEQUENTIAL DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY
THEREOF. This limitation of the liability of National Instruments will apply regardless
of the form of action, whether in contract or tort, including negligence. National
Instruments recommends against the use of its products as critical components in any life
support devices or systems whose failure to perform can reasonably be expected to cause
significant injury to a human. Buyer assumes all risk for such application and agrees to
indemnify National Instruments for all damages which may be incurred due to use of the
National Instruments standard devices in medical or life support applications. Any action
against National Instruments must be brought within one year after the cause of action
accrues.
National Instruments believes that the information in this manual is accurate. The
document has been carefully reviewed for technical accuracy. In the event that technical
or typographical errors exist, National Instruments reserves the right to make changes to
subsequent editions of this document without prior notice to holders of this edition. The
reader should consult National Instruments if errors are suspected. In no event shall
National Instruments be liable for any damages arising out of or related to this document
or the information contained in it.
Copyright
Under the copyright laws, this publication may not be reproduced or transmitted in any
form, electronic or mechanical, including photocopying, recording, storing in an
information retrieval system, or translating, in whole or in part, without the prior written
consent of National Instruments Corporation.
Trademarks
NAT7210™ is a trademark of National Instruments Corporation.
Product and company names listed are trademarks or trade names of their respective
companies.
WARNING REGARDING MEDICAL AND CLINICAL
USE OF NATIONAL INSTRUMENTS PRODUCTS
National Instruments products are not designed with components and testing intended to
ensure a level of reliability suitable for use in treatment and diagnosis of humans.
Applications of National Instruments products involving medical or clinical treatment can
create a potential for accidental injury caused by product failure, or by errors on the part
of the user or application designer. Any use or application of National Instruments
products for or involving medical or clinical treatment must be performed by properly
trained and qualified medical personnel, and all traditional medical safeguards,
equipment, and procedures that are appropriate in the particular situation to prevent
serious injury or death should always continue to be used when National Instruments
products are being used. National Instruments products are NOT intended to be a
substitute for any form of established process, procedure, or equipment used to monitor
or safeguard human health and safety in medical or clinical treatment.
Contents
About This Manual ............................................................................................. xiii
Organization of This Manual ......................................................................... xiii
Conventions Used in This Manual................................................................. xiv
Related Documentation ................................................................................. xiv
Customer Communication ............................................................................. xv
This manual describes the programmable features of the NAT7210 and contains
information that is suitable for programmers and engineers who wish to write software
for the NAT7210.
This manual assumes that you are already familiar with general IEEE 488 concepts.
Organization of This Manual
This manual is organized as follows:
•Chapter 1, Introduction and General Description, explains the features and
capabilities of the NAT7210.
•Chapter 2, NAT7210 Architecture, discusses the internal hardware architecture of the
NAT7210.
•Chapter 3, 7210-Mode Interface Registers, contains NAT7210 address maps and
detailed descriptions of the NAT7210 interface registers in 7210 mode.
•Chapter 4, 9914-Mode Interface Registers, contains NAT7210 address maps and
detailed descriptions of the NAT7210 interface registers in 9914 mode.
•Chapter 5, Software Considerations, explains important NAT7210 programming
considerations, including chip initialization, Talkers and Listeners, message
reception, and holdoffs.
•Chapter 6, Controller Software Considerations, explains important system and GPIB
Controller considerations.
•Chapter 7, Hardware Considerations, explains important NAT7210 hardwareinterfacing considerations, including a description of the pins.
•Appendix A, Common Questions, lists common questions and answers.
•Appendix B, Introduction to the GPIB, discusses the history of the GPIB, GPIB
hardware configurations, and serial polling.
•Appendix C, Standard Commands for Programmable Instruments (SCPI), discusses
the SCPI document, the required SCPI commands, and SCPI programming.
•Appendix D, Multiline Interface Command Messages, lists the multiline interface
messages and describes the mnemonics and messages that correspond to the interface
functions.
•Appendix E, Mnemonics Key, defines the mnemonics (abbreviations) that this
manual uses for functions, remote messages, local messages, states, bits, registers,
integrated circuits, and system functions.
•Appendix F, Customer Communication, contains forms you can use to request help
from National Instruments or to comment on our products and manuals.
•The Glossary contains an alphabetical list and a description of the terms, including
abbreviations, acronyms, metric prefixes, mnemonics, and symbols, that this manual
uses.
•The Index contains an alphabetical list of the key terms and topics that this
manual uses, and it includes the page number where you can locate each term
and topic.
Conventions Used in This Manual
This manual uses the following conventions.
italicItalic text denotes emphasis, a cross reference, or an
introduction to a key concept.
bold italicBold italic text denotes a note, caution, or warning.
monospaceText in this font denotes programming examples.
IEEE 488 and IEEE 488 and IEEE 488.2 refer to the ANSI/IEEE
IEEE 488.2Standard 488.1-1987 and ANSI/IEEE Standard 488.2-1992,
respectively, which define the GPIB.
The Glossary lists abbreviations, acronyms, metric prefixes, mnemonics, symbols, and
terms.
Related Documentation
The following documents contain information that you may find helpful as you read this
manual.
•40-Pin IEEE 488.2 Controller Chip: Drop-In Replacement for NEC µPD7210
NAT7210APD
•ANSI/IEEE Standard 488.1-1987, IEEE Standard Digital Interface for
Programmable Instrumentation
•ANSI/IEEE Standard 488.2-1992, IEEE Standard Codes, Formats,
Protocols, and Common Commands
You may obtain the two ANSI/IEEE documents through the Institute of Electrical and
Electronics Engineers, 345 East 47th Street, New York, New York 10017.
You may obtain more information about Standard Commands for Programmable
Instruments from the SCPI Consortium, 8380 Hercules Drive, Suite P3, La Mesa,
CA 91942.
Customer Communication
National Instruments wants to receive your comments on our products and manuals. We
are interested in the applications you develop with our products, and we want to help if
you have problems with them. To make it easy for you to contact us, this manual
contains comment and configuration forms for you to complete. These forms are in
Appendix F, Customer Communication, at the end of this manual.
This chapter explains the features and capabilities of the NAT7210.
The NAT7210 is an IEEE 488.2 Controller chip designed to perform all the
interface functions defined in the ANSI/IEEE Standard 488.1-1987 and the
additional requirements and recommendations of the ANSI/IEEE Standard
488.2-1987. The NAT7210 manages the IEEE 488 interface functions with a set
of control and status registers that increase the throughput of driver software and
simplify hardware and software design. The NAT7210 performs complete
IEEE 488 Talker, Listener, and Controller functions and is software compatible
with the NEC µPD7210 and TI TMS9914A chips.
The NAT7210 can be characterized as a bus translator: it converts messages and
signals from the CPU into appropriate GPIB messages and signals. In GPIB
terminology, the NAT7210 implements GPIB board and device functions to
communicate with the central processor and memory. For the computer, the
NAT7210 is an interface to the outside world.
IEEE 488 Capabilities
The National Instruments NAT7210 has the features necessary to provide a
high-performance IEEE 488 interface. Table 1-1 lists the capabilities of the NAT7210
in terms of the IEEE 488 standard codes.
The NAT7210 has complete Source and Acceptor Handshake capability. It can operate
as a basic Talker or an extended Talker and can respond to a Serial Poll. If you place it in
talk-only mode, it is unaddressed to talk when it receives its listen address. The
NAT7210 GPIB interface can also operate as a basic Listener or an extended Listener.
If you place it in listen-only mode, it is unaddressed to listen when it receives its talk
address. The NAT7210 can request service from a Controller.
Device Clear and Trigger capability is included in the interface; the interpretation is
software dependent.
Other GPIB features include the following:
•Messages not sent when there are no Listeners
•Automatic detection of EOS and/or NL messages
•Automatic bus synchronization detection
•Programmable data transfer rates (T1 delays as short as 350 ns)
•Programmable GPIB transceiver support
•Automatic processing of IEEE 488 commands and read-undefined commands
•Ability to use six addressing modes:
–Automatic single or dual primary addressing detection
–Automatic single primary with single secondary address detection
–Single or dual primary with multiple secondary addressing
–Multiple primary addressing
CPU Interface Capabilities
•Software compatible with NEC µPD7210 and TI TMS9914A Controller chips
Figure 1-1 shows a block diagram of a typical application that uses the NAT7210
to implement an IEEE 488.2 interface.
CPU Bus
Control
Address
Decode
GPIB
XCVR
GPIB
Data
Interrupt
NAT7210
GPIB
XCVR
Figure 1-1. NAT7210 Implementation Block Diagram
In all applications, the NAT7210 must be connected to the GPIB via IEEE 488 compliant
transceivers such as the 75160 and 75162, which are available from National
Semiconductor and other vendors. The NAT7210 has control signals that let it easily
interface to several different types of transceivers.
This chapter discusses the internal hardware architecture of the NAT7210.
The NAT7210 includes the following major components:
•Read/Write Control converts the CPU interface signals to read and write signals for
each internal NAT7210 register.
•Internal NAT7210 Registers configure and control the operation of the NAT7210.
They transfer data between the NAT7210 and the GPIB, report status information,
and set the operating modes. Chapter 3, 7210-Mode Interface Registers, and
Chapter 4, 9914-Mode Interface Registers, describe each register in detail.
•Interface Functions implement the interface functions described in the IEEE 488.1
standard. Some internal registers control the interface functions, and you can use
other internal registers to monitor the status of interface functions. The interface
functions drive and receive the GPIB control signals and generate the signals to
control the GPIB transceivers.
•Message Decoders receive the GPIB data lines and decode the GPIB commands that
affect the operation of the interface functions.
The NAT7210 has two basic modes of operation: 7210 mode and 9914 mode.
In 7210 mode, the NAT7210 is software compatible with the µPD7210 IEEE 488
Controller. The NAT7210 has many registers and features that are not present in the
µPD7210. In 9914 mode, the NAT7210 is software compatible with the TMS9914A
IEEE 488 Controller. The NAT7210 has many registers and features that are not present
in the TMS9914A.
Note:Throughout this manual, 7210 mode refers to the NEC µPD7210 software
compatibility mode, and 9914 mode refers to the TI TMS9914A software
compatibility mode.
Changing the NAT7210 Mode
Figure 2-2 illustrates how you change the mode of the NAT7210.
sw9914 Auxiliary
Command
7210 Mode
sw7210 Auxiliary
Command
9914 Mode
Hardware Reset
Figure 2-2. Changing the NAT7210 Mode
Notice that the NAT7210 is in 7210 mode after a hardware reset. To change from 7210
mode to 9914 mode, write the sw9914 auxiliary command to the (7210 mode) Auxiliary
Mode Register (AUXMR). To change from 9914 mode to 7210 mode, write the sw7210
auxiliary command to the (9914 mode) Auxiliary Command Register (AUXCR).
This chapter contains NAT7210 address maps and detailed descriptions of the NAT7210
interface registers in 7210 mode. For 9914-mode register descriptions, see Chapter 4,
9914-Mode Interface Registers.
7210 Register Map
Table 3-1 is the register bit map for the NAT7210 in 7210 mode.
Notice that bold-ruled cells distinguish seven registers that are accessible only when the
Page-In state is true. Refer to The Page-In State section that immediately follows the
register map for more information.
At some offsets, Table 3-1 shows two readable or two writable registers. The shaded
registers in Table 3-1 are accessible only when the Page-In state is true. For each shaded
register, the corresponding unshaded register is accessible only when the Page-In state is
false.
How to Page-In
The NAT7210 enters the Page-In state when the host interface writes the Page-In
auxiliary command to the Auxiliary Mode Register (AUXMR). The NAT7210 registers
appear at their Page-In state offset for the first register access after the Page-In command.
The NAT7210 leaves the Page-In state at the end of the first register access after the
Page-In command.
Hidden Registers
In addition to the registers shown in Table 3-1, the NAT7210 contains hidden registers.
All hidden registers are write-only registers. Two or more hidden registers can appear at
the same offset. When you write an 8-bit pattern to these offsets, some of the bits
determine which hidden register will be written. The other bits represent the value
written to the register.
Address Register Map
The NAT7210 has two address registers: ADR1 and ADR0. Table 3-1 shows the offsets
for the readable portion of ADR1 and ADR0. The writable portion of ADR0 and ADR1
appears at the offset of the Address Register (ADR) shown in Table 3-1. Table 3-2
shows the bit map for the two writable address registers.
Some 7210-mode registers and 9914-mode registers share identical names. The
9914-mode registers are described in Chapter 4, 9914-Mode Interface Registers. If you
are using the NAT7210 in 7210 mode, be sure to read the proper description for the
7210-mode registers.
All registers are listed in alphabetical order. The registers are alphabetized according to
their mnemonics.
The host interface can put the NAT7210 into one of six GPIB addressing modes by
writing to the Address Mode Register (ADMR). The values of ADMR (7–6; 3–0) are
undefined after a hardware reset. Before the host interface can clear pon, it must write a
valid pattern to the ADMR.
Table 3-4. Valid ADMR Patterns
Hex Value
of
ADMR*
30No Addressing
The Controller cannot address the NAT7210 to become a Talker or
Listener in no-addressing mode.
31Normal Dual Addressing
The NAT7210 can implement one or two logical devices by using
normal dual addressing.
See the GPIB Addressing section in Chapter 5, Software Considerations.
32
33Extended Dual Addressing
Extended Single Addressing
Extended single addressing mode implements the Extended Listener and
Extended Talker functions, as defined in the IEEE 488 standard, without
intervention from the host interface.
See the GPIB Addressing section in Chapter 5, Software Considerations.
Extended dual addressing mode implements the Extended Listener and
Extended Talker functions, as defined in the IEEE 488 standard. This
mode requires intervention from the host interface.
GPIB Addressing Mode
See the GPIB Addressing section in Chapter 5, Software Considerations.
The NAT7210 becomes a GPIB Listener and enters the Listener Active
State (LACS). Do not use lon if a GPIB Controller is present in the
GPIB system.
The host interface should write a hex 30 (No Addressing) to the ADMR
immediately after writing lon to the ADMR. To force the NAT7210 to
exit LACS, issue the unlisten (lul) auxiliary command.
B0Talk Only (ton)
The NAT7210 becomes a GPIB Talker. Do not use ton if a GPIB
Controller is present in the GPIB system.
The host interface should write a hex 30 (No Addressing) to the ADMR
immediately after writing ton to the ADMR. To force the NAT7210 to
exit TACS, issue the local untalk (lut) auxiliary command.
* The hex values in Table 3-4 assume that TRM1 = 1 and TRM0 = 1.
Writing to the Address Register (ADR) loads the internal registers ADR0 and ADR1.
You must load both ADR0 and ADR1 for all addressing modes. See the GPIBAddressing section in Chapter 5, Software Considerations.
BitMnemonicDescription
7wARSAddress Register Select bit
If ARS = 1, writing to the ADR loads the seven low-order
bits of ADR into internal register ADR1. If ARS = 0,
writing to the ADR loads the seven low-order bits into
ADR0.
6wDTDisable Talker bit
DT = 1 disables recognition of the GPIB talk address
formed from AD[5–1]. ADR0 and ADR1 have
independent DT bits.
5wDLDisable Listener bit
DL = 1 disables recognition of the GPIB listen address
formed from AD[5–1]. ADR0 and ADR1 have
independent DL bits.
4–0wAD[5–1]NAT7210 GPIB Address bits 5 through 1
These bits specify the GPIB address of the NAT7210.
The corresponding GPIB talk address is formed by adding
hex 40 to AD[5–1], while the corresponding GPIB listen
address is formed by adding hex 20 to AD[5–1]. The
value written to AD[5–1] should not be 11111 (binary),
because the corresponding talk and listen addresses would
conflict with the GPIB Untalk (UNT) and GPIB Unlisten
(UNL) commands.
Address Register 0 (ADR0) reflects the internal GPIB address status of the NAT7210. In
extended single addressing mode, ADR0 indicates the address and enable bits for the
primary GPIB address of the NAT7210. In the dual primary addressing modes, ADR0
indicates the NAT7210 major primary GPIB address. See the GPIB Addressing section
in Chapter 5, Software Considerations.
BitMnemonicDescription
7rXReads back a 1 or 0.
6rDT0Disable Talker 0 bit
If DT0 = 1, the primary (or major) Talker function is not
enabled, and ADR0 is not compared with GPIB Talker
addresses.
If DT0 = 0, the NAT7210 responds to a GPIB talk address
matching bits AD[5–0 through 1–0].
5rDL0Disable Listener 0 bit
If DL0 = 1, the primary (or major) Listener function is not
enabled, and ADR0 is not compared with GPIB Listener
addresses.
If DL0 = 0, the NAT7210 responds to a GPIB listen
address matching bits AD[5–0 through 1–0].
4–0rAD[5–0 – 1–0] NAT7210 GPIB Address bits 5–0 through 1–0
These are the lower 5 bits of the NAT7210 GPIB primary
(or major) address. The primary talk address is formed by
adding hex 40 to AD[5–0 through 1–0], while the primary
listen address is formed by adding hex 20.
Address Register 1 (ADR1) indicates the status of the GPIB address and enable bits for
the secondary address of the NAT7210 if extended single addressing is used. ADR1
indicates the minor primary address of the NAT7210 if dual primary addressing is used.
See the GPIB Addressing section in Chapter 5, Software Considerations.
BitMnemonicDescription
7rEOIEnd-or-Identify bit
EOI indicates the value of the GPIB EOI line that is
latched when a data byte is received by the NAT7210
GPIB Acceptor Handshake (AH) function. If EOI = 1, the
EOI line was asserted with the received byte. EOI is
cleared by issuing the Chip Reset auxiliary command.
EOI is updated after each byte is received.
6rDT1Disable Talker 1 bit
If DT1 = 1, the secondary (or minor) Talker function is
not enabled—that is, the GPIB secondary address (or
minor primary talk address) is not compared with this
register.
5rDL1Disable Listener 1 bit
If DL1 = 1, the secondary (or minor) Listener function is
not enabled—that is, the GPIB secondary address (or
minor primary listen address) is not compared with this
register.
4–0rAD[5–1 – 1–1]NAT7210 GPIB Address bits 5–1 through 1–1
These bits indicate the NAT7210 secondary or minor
address. Form the secondary address by adding hex 60 to
bits AD[5–1 through 1–1]. Form the minor talk address
by adding hex 40 to AD[5–1 through 1–1]. Form the
listen address by adding a hex 20.
The Address Status Register (ADSR) contains information that you can use to monitor
the NAT7210 GPIB address status.
BitMnemonicDescription
7rCICController-In-Charge bit
CIC = ~(CIDS + CADS)
CIC indicates that the NAT7210 GPIB Controller
function is either in an active state with ATN* asserted or
a standby state with ATN* unasserted. The Controller
function is in an idle state (CIDS or CADS) if CIC = 0.
6rATN*Attention* bit
ATN* is a status bit that indicates the current level of the
GPIB ATN* signal. If ATN* = 0, the GPIB ATN* signal
is asserted.
5rSPMSSerial Poll Mode State bit
If SPMS = 1, the NAT7210 GPIB Talker (T) or Talker
Extended (TE) function is enabled to participate in a serial
poll.
LPAS indicates that the NAT7210 has received its
primary listen address. See the Address Mode Register(ADMR) section in this chapter.
LPAS is cleared by
(PCG & ~MLA & ACDS) + pon
3rTPASTalker Primary Addressed State bit
TPAS indicates that the NAT7210 has received its
primary GPIB talk address. See the Address ModeRegister(ADMR) section in this chapter.
TPAS is cleared by
(PCG & ~MTA & ACDS) + pon
2rLAListener Active bit
LA = 1 when the NAT7210 has been addressed or
programmed as a GPIB Listener—that is, the NAT7210 is
in the Listener Active State (LACS) or the Listener
Addressed State (LADS). The NAT7210 is addressed to
listen when it receives its listen address from the CIC.
The NAT7210 can also be programmed to listen by using
the Listen-Only (lon) bit in the ADMR.
If the NAT7210 is addressed to talk, it is automatically
unaddressed to listen.
LA is also cleared by
(UNL & ACDS) + IFC + pon + (lun & CACS)
+ lul
1rTATalker Active bit
TA = 1 when the NAT7210 has been addressed or
programmed as the GPIB Talker—that is, the NAT7210 is
in the Talker Active State (TACS), the Talker Addressed
State (TADS), or the Serial Poll Active State (SPAS).
The NAT7210 can be addressed to talk when it receives
its talk address from the CIC. It can also be programmed
to talk by using the Talk-Only (ton) bit in the ADMR.
If the NAT7210 is addressed to listen, it is automatically
unaddressed to talk.
TA is also cleared by
(OTA & ACDS) + IFC + pon + lut
0rMJMNMajor-Minor bit
MJMN indicates whether the information in the other
ADSR bits applies to the NAT7210 major or minor Talker
and Listener functions. MJMN = 1 when the NAT7210
receives its GPIB minor talk address or minor listen
address. MJMN clears when the NAT7210 receives its
major talk or major listen address. The pon message also
clears MJMN.
Note: Only one Talker or Listener can be active at a
time. The MJMN bit indicates which, if either,
of the NAT7210 Talker and Listener functions is
addressed or active.
MJMN is always 0 unless the normal or extended dual
primary addressing mode is enabled. See the Address
The Immediate Execute Power-On auxiliary command sets the local
pon message true, then clears it. If the local pon message is already
asserted, the pon auxiliary command simply clears the local pon
message. The following figure illustrates the behavior of the local
pon message:
Description
start of pon aux.
local pon
command pulse
message
true
end of pon aux.
command pulse
HW reset +
chip_reset aux. command
When the local pon message is true, the NAT7210 holds all GPIB
interface functions in their idle states.
Clear Parallel Poll Flag (~ist)
Set Parallel Poll Flag (ist)
These commands set and clear the Parallel Poll Flag. The value of
the Parallel Poll Flag is used as the local message ist when
AUXRB[4]w = 0. The value of SRQS is used as ist when ISS = 1.
A hardware reset or the Chip Reset auxiliary command clears ist.
The Chip Reset auxiliary command resets the NAT7210 to the
following conditions:
•The local pon message is set and the interface functions are
•The SPMR bits are cleared.
•The TRM[1–0] bits are cleared.
•The EOI bit is cleared.
•The AUXRA, AUXRB, AUXRE, AUXRF, AUXRG, and
•The Parallel Poll Flag is cleared.
•The BCR is cleared.
The interface functions remain in their idle states until they are
released by an Immediate Execute pon command. While the
interface functions are in their idle states, the host interface can
program the NAT7210 writable bits to their desired states.
Description
placed in their idle states.
AUXRI registers are cleared.
03Finish Handshake (rhdf)
The Finish Handshake command finishes a GPIB handshake that was
stopped because of a Holdoff On RFD condition.
See The GPIB rdy Message and RFD Holdoffs section in Chapter 5,
Software Considerations.
The Trigger command generates a high pulse on the T/R 3 pin when
TRM1 = 0. The DET bit is not set by issuing the Trigger command.
05
0D
06Send EOI (seoi)
07Nonvalid Secondary Command Or Address (nonvalid)
Clear Or Pulse Return To Local (rtl)
Set Return To Local (rtl)
The two Return To Local commands implement the rtl message as
defined by the IEEE 488 standard. If the host interface writes 05 hex,
the rtl message is generated in the form of a pulse. If rtl is already
set, the rtl command clears it. If the host interface writes 0D hex, the
rtl command is set and remains set until either the 05 hex rtl
command is issued or a Chip Reset auxiliary command is issued.
The seoi command causes the GPIB End-or-Identify (EOI) line to go
true with the next data byte transmitted. The EOI line is cleared upon
completion of the handshake for that byte. When NTNL = 0, the
NAT7210 recognizes the seoi command only if TACS = 1—that is,
the NAT7210 is in the Talker Active State.
Description
The nonvalid command releases a DAC (Data Accepted) holdoff.
If APT = 1, the NAT7210 operates as if an Other Secondary Address
(OSA) message had been received.
08*Request Control Command (rqc)
If the NAT7210 is in the Idle Controller State, the rqc command
forces the NAT7210 to become the Active Controller when it detects
that the ATN signal is unasserted.
0A*Release Control Command (rlc)
The rlc command forces the NAT7210 to become an Idle Controller
and to unassert ATN.
The lut command issues the local unt message, forcing the Talker
function to enter TIDS.
0C*Unlisten (lul)
The lul command issues the local unl message, forcing the Listener
function to enter LIDS.
0E*New Byte Available False (nbaf)
nbaf forces the local message, nba, to become false. This action
prohibits the NAT7210 from sending the last byte written to the
Command/Data Our Register (CDOR). See the Using nbaf section
in Chapter 5, Software Considerations.
0FValid Secondary Command Or Address (valid)
The valid command releases a DAC holdoff. If APT = 1, the
NAT7210 operates as if a My Secondary Address (MSA) message
had been received.
10Go To Standby (gts)
Description
The gts command pulses the local gts message. If the NAT7210 is
the Active Controller, gts causes the NAT7210 to become the
Standby Controller and to unassert the GPIB ATN signal. See the
Three Basic Controller States section in Chapter 6, Controller
Software Considerations.
11Take Control Asynchronously (tca)
The tca command pulses the local tca message. If the NAT7210 is
the Standby Controller, tca causes the NAT7210 to become the
Active Controller and to assert the GPIB ATN signal. See the
Standby State to Active State section in Chapter 6, Controller
Software Considerations.
The tcs command sets the local tcs message. If the NAT7210 is the
Standby Controller and an Active Listener, the tcs message causes the
NAT7210 to become the Active Controller when the NAT7210
performs an RFD holdoff—that is, the AH function enters ANRS.
The local tcs message clears when the NAT7210 becomes the Active
Controller by this method or if the NAT7210 becomes an Idle
Controller. See the Standby State to Active State section in Chapter 6,
Controller Software Considerations.
13Listen (ltn)
The ltn command pulses the local ltn message. If the NAT7210 is the
Active Controller, the local ltn message causes the NAT7210 to
become an Addressed Listener. The ltn command can also take the
NAT7210 out of the continuous data-receiving mode (see ltn & cont
command).
14Disable System Control (~rsc)
The ~rsc command, a hardware reset, or the Chip Reset auxiliary
command clears the local rsc message. See the SystemController
Considerations section in Chapter 6, Controller Software
Considerations.
Description
15*Switch To 9914A Mode (sw9914)
This command places the NAT7210 in 9914 compatibility mode.
16Clear IFC (~sic & rsc)
The ~sic & rsc command clears the local sic message and sets the
local rsc messages. This action causes the NAT7210 to become the
System Controller and to unassert the GPIB IFC signal. See the
System Controller Considerations section in Chapter 6, Controller
Software Considerations.
The ~sre & rsc command clears the local sre message and sets the
local rsc messages. This action causes the NAT7210 to become the
System Controller and to unassert the GPIB REN signal. See the
System Controller Considerations section in Chapter 6, Controller
Software Considerations.
18*
19*
1ATake Control Synchronously On END (tcse)
Request rsv True (reqt)
Request rsv False (reqf)
The reqt and reqf commands are inputs to the IEEE 488.2 Service
Request Synchronization Circuitry. These commands set and clear
the local rsv message.
If STBO IE = 1, the reqt and reqf commands are issued immediately.
If STBO IE = 0, the reqt and reqf commands are not issued
immediately: they are issued on the write of the SPMR that follows
the issuing of the reqt or reqf auxiliary command.
The tcse command causes the local tcs message to set when the
NAT7210 accepts a byte satisfying the END condition (see the END
RX bit ISR1[4]). If the NAT7210 is the Standby Controller and an
Active Listener, the tcs message causes the NAT7210 to become the
Active Controller when the NAT7210 performs an RFD holdoff—
that is, when the AH function enters ANRS. The local tcs message
(and the END detection circuitry) clears when the NAT7210 becomes
the Active Controller by this method or if the NAT7210 becomes an
Idle Controller.
The ltn & cont command pulses the local ltn message. If the
NAT7210 is the Active Controller, the local ltn message causes the
NAT7210 to become an Addressed Listener.
The ltn & cont command also places the NAT7210 in continuous
mode regardless of the settings of the AUXRA[1–0] bits (see TheGPIB rdy Message and RFD Holdoffs section in Chapter 5). If
the NAT7210 enters continuous mode because of the ltn & cont
command, it remains in continuous mode until the NAT7210
becomes unaddressed to Listen—that is, the L or LE function enters
LIDS—or until the control program issues the ltn command.
1CLocal Unlisten (lun)
The lun command pulses the local lun message. If the NAT7210 is
the Active Controller, the local lun message causes the NAT7210 to
become an Unaddressed Listener—that is, the L or LE function enters
LIDS.
1DExecute Parallel Poll (rpp1)
The rpp1 command sets the local rpp message. If the NAT7210 is
the Active Controller, the rpp message causes the NAT7210 to send
the IDY message to all GPIB devices in the system and to conduct
a parallel poll. (See the Conducting Parallel Polls section in
Chapter 6.) The rpp message clears when the NAT7210 completes
a parallel poll or becomes an Idle Controller.
Description
1ESet IFC (sic & rsc)
The sic & rsc command sets the local sic and rsc messages. The local
message pon or the ~rsc auxiliary command also clears sic. This
action causes the NAT7210 to become the System Controller and to
assert the GPIB IFC signal. See the System Controller
Considerations section in Chapter 6, Controller Software
Considerations.
The sre & rsc command sets the local sre and rsc messages. The
local message pon or the ~rsc auxiliary command also clears sre.
This action causes the NAT7210 to become the System Controller
and to assert the GPIB REN signal. See the System Controller
Considerations section in Chapter 6, Controller Software
Considerations.
50*Page-In Additional Registers (page-in)
The Page-In command causes the NAT7210 to enter the Page-In
state. The Page-In state makes several registers accessible. See ThePage-In State section located at the beginning of this chapter.
51*Holdoff Handshake Immediately (hldi)
This command forces the Acceptor Handshake function to
immediately perform an RFD holdoff. Issuing this command forces a
transition into ANRS, where the handshake is held off until a finish
handshake auxiliary command is issued.
54*Clear DET
This command clears the DET bit (ISR1[5]r). Use this command to
clear the DET bit when SISB = 1.
Description
55*Clear END
This command clears the END bit (ISR1[4]r). Use this command to
clear the END bit when SISB = 1.
56*Clear DEC
This command clears the DEC bit (ISR1[3]r). Use this command to
clear the DEC bit when SISB = 1.
57*Clear ERR
This command clears the ERR bit (ISR1[2]r). Use this command to
clear the ERR bit when SISB = 1.
AUXRA controls the End-of-String (EOS) and END messages and specifies the RFD
holdoff mode. The Chip Reset auxiliary command or a hardware reset clears AUXRA.
You write to AUXRA at the same offset as the AUXMR.
BitMnemonicDescription
4wBINBinary bit
The BIN bit selects the length of the EOS message. If
BIN = 1, the End-of-String Register (EOSR) is treated as
an 8-bit byte. When BIN = 0, the EOSR is treated as a
7-bit register (for ASCII characters), and only a 7-bit
comparison is done with the data on the GPIB.
3wXEOSTransmit END With EOS bit
XEOS permits or prohibits automatic transmission of the
GPIB END message at the same time as the EOS message
when the NAT7210 is in TACS. If XEOS = 1 and the
byte in the CDOR matches the contents of the EOSR, the
EOI line is sent true along with the data.
2wREOSEND On EOS Received bit
The REOS bit permits or prohibits setting the END bit
(ISR1[4]r) when the NAT7210 receives the EOS message
as a Listener. If REOS = 1 and the byte in the DIR
matches the byte in the EOSR, the END RX bit
(ISR1[4]r) is set and the acceptor function treats the EOS
character just as if it were received with EOI asserted.
HLDE and HLDA together determine the GPIB
data-receiving mode.
HLDEHLDAData-Receiving Mode
00Normal Handshake Mode
01RFD Holdoff on All Data Mode
10RFD Holdoff on END Mode
11Continuous Mode
For more information, see The GPIB rdy Message and
RFD Holdoffs section in Chapter 5, Software
Considerations.
Issuing the ltn & cont auxiliary command can also place
the NAT7210 in the continuous data-receiving mode.
The NAT7210 enters continuous mode regardless of
the value of HLDE and HLDA. In this situation, the
NAT7210 remains in continuous mode until you issue
the ltn auxiliary command or the NAT7210 becomes
unaddressed to listen (by entering the LIDS).
AUXRB affects several interface functions. The Chip Reset auxiliary command or a
hardware reset clears AUXRB. You write to AUXRB at the same offset as the AUXMR.
BitMnemonicDescription
4wISSIndividual Status Select bit
ISS determines the value of the NAT7210 ist message.
When ISS = 1, ist takes on the value of the NAT7210
Service Request State (SRQS). (The NAT7210 asserts
the GPIB SRQ message when it is in SRQS.) If ISS = 0,
ist takes on the value of the NAT7210 Parallel Poll Flag.
You set and clear the Parallel Poll Flag by using the Set
Parallel Poll Flag and Clear Parallel Poll Flag auxiliary
commands. See the Parallel Polling section in
Appendix B, Introduction to the GPIB.
3wINVInvert bit
INV determines the polarity of the INT pin.
INV BitINT Pin Polarity
0Active High
1Active Low
2wTRIThree-State Timing bit
TRI determines the NAT7210 GPIB Source Handshake
Timing (T1). Clearing TRI sets the low-speed timing
(T1 ≥ 2 µs). Setting TRI enables the NAT7210 to use a
shorter T1 delay. See the T1 Delay Generation section in
Chapter 5, Software Considerations.
AUXRE determines when the NAT7210 performs a DAC holdoff. The Chip Reset
auxiliary command or a hardware reset clears AUXRE.
Each bit of AUXRE enables DAC holdoffs on a GPIB command or group of commands.
When a GPIB Controller sends the specified command to the NAT7210, the CPT bit sets
and the NAT7210 performs a DAC holdoff. See the DAC Holdoffs section in Chapter 5,
AUXRF determines how the NAT7210 uses a DAC holdoff. The Chip Reset auxiliary
command or a hardware reset clears AUXRF.
Each bit of AUXRF enables DAC holdoffs on a GPIB command or group of commands.
When a GPIB Controller sends the specified command to the NAT7210, the CPT bit sets
and the NAT7210 performs a DAC holdoff. See the DAC Holdoffs section in Chapter 5,
Software Considerations.
BitMnemonicDescription
3wDHATADAC Holdoff On All Talker Addresses Command bit
2wDHALADAC Holdoff On All Listener Addresses Command bit
1wDHUNTLDAC Holdoff On The UNT Or UNL Command bit
0wDHALLDAC Holdoff On All UCG, ACG, And SCG Commands
Set NTNL to prevent the NAT7210 from sourcing data
(talking) when there is no external Listener, to modify the
setting of the ERR bit, to modify the way the nba local
message is cleared, and to change the EOI generation
function. If the NAT7210 is used in an IEEE 488.2
device, you should set NTNL.
If NTNL = 0, the following actions occur:
•The NAT7210 handshake function enters STRS after
the T1 delay has elapsed and NRFD is unasserted.
•The ERR bit is set on TACS & SDYS & DAC &
RFD or SIDS & (write CDOR) or the transition from
SDYS to SIDS.
•The local nba message is cleared upon entering SIDS
or STRS.
•The Send EOI auxiliary command is ignored or
forgotten upon exiting TACS.
If NTNL = 1, the following actions occur:
•The NAT7210 handshake function does not make the
transition from SDYS to STRS unless an external
Listener exists—that is, a device on the GPIB is
asserting NDAC.
•The ERR bit is set when the T1 delay has elapsed and
TACS & SDYS & EXTDAC & RFD (where
EXTDAC refers to some device on the GPIB
asserting NDAC).
•The local nba message is cleared upon entering STRS
and ~SPAS.
•The Send EOI auxiliary command is cleared upon
entering SDYS or STRS.
2wRPP2Request Parallel Poll 2 bit
If RPP2 = 1, the local rpp message is true. Clearing RPP2
clears rpp. If the NAT7210 is the Active Controller,
setting rpp causes the NAT7210 to conduct a parallel poll.
See the Conducting Parallel Polls section in Chapter 6,
ControllerSoftware Considerations.
1wDISTCTDisable Automatic Take Control bit
If DISTCT = 1, the NAT7210 considers the GPIB TCT
message undefined. If the GPIB Controller tries to pass
control to the NAT7210, the NAT7210 will not become a
Controller. You usually set DISTCT if the NAT7210 is a
talk-only or listen-only device.
If DISTCT = 0, the NAT7210 recognizes TCT. Another
Controller may pass control to the NAT7210 without
software intervention.
0wCHESClear Holdoff On End Select bit
CHES determines how long the NAT7210 remembers that
it detected an END condition.
If CHES = 0, the NAT7210 remembers the detection of
the END condition until the host interface issues the
Release Handshake Holdoff auxiliary command.
If CHES = 1, the NAT7210 remembers the detection of
the END condition until the Release Handshake Holdoff
auxiliary command is issued or the DIR is read when the
NAT7210 is in the normal handshake holdoff mode—that
is, HLDE and HLDA = 0.
USTD sets the value of the T1 delay (used by the Source
Handshake function for data setup) to 350 ns for the
second and subsequent data bytes sent after ATN
unasserts. If USTD = 0, the TRI bit (AUXRB[2]w)
determines the value of T1. See the T1 Delay Generation
section in Chapter 5, Software Considerations.
2wPP2Parallel Poll bit 2
If PP2 = 0, the NAT7210 responds to parallel polls in the
same manner as the µPD7210—that is, it supports Parallel
Poll functions PP1 and PP2 simultaneously. However, a
contradiction arises because PP1 requires the interface to
be configured by remote GPIB commands, and PP2
requires the interface to be configured locally and ignore
remote GPIB commands.
When PP2 = 1, the chip ignores remote GPIB
commands—that is, PPC and PPU are treated as
undefined commands, allowing a true implementation of
PP2. In addition, setting PP2 and U (PPR[4]w) lets the
NAT7210 support PP0 (no Parallel Poll response). See
the Parallel Polling section in Appendix B.
0wSISBStatic Interrupt Status Bits bit
If SISB = 0, reading ISR0, ISR1, or ISR2 clears the bits of
the register that is read (ISR0, ISR1, or ISR2).
7rATNGPIB Attention Status bit
7wATNGPIB Attention Control bit
6rDAVGPIB Data Valid Status bit
6wDAVGPIB Data Valid Control bit
5rNDACGPIB Not Data Accepted Status bit
5wNDACGPIB Not Data Accepted Control bit
4rNRFDGPIB Not Ready For Data Status bit
4wNRFDGPIB Not Ready For Data Control bit
3rEOIGPIB End-or-Identify Status bit
3wEOIGPIB End-or-Identify Control bit
2rSRQGPIB Service Request Status bit
2wSRQGPIB Service Request Control bit
1rIFCGPIB Interface Clear Status bit
1wIFCGPIB Interface Clear Control bit
0rRENGPIB Remote Enable Status bit
0wRENGPIB Remote Enable Control bit
Reads of the Bus Status Register (BSR) return the status of the GPIB control lines at the
time of the read. Write ones to bits in the Bus Control Register (BCR) to assert the
corresponding GPIB control lines.
Because the NAT7210 is either transmitting or receiving a GPIB control line at any
particular time and is not performing both actions simultaneously, setting a bit in the
BCR may not automatically assert the corresponding line on the GPIB. If the NAT7210
is transmitting a GPIB line when the corresponding bit in the BCR is set, the NAT7210
asserts the GPIB line. If the NAT7210 is receiving a GPIB line when the corresponding
bit in the BCR is set, the GPIB line is not asserted. However, in both these cases, the
GPIB signal internal to the NAT7210 is logically ORed with the value of the BCR bit.
Figure 3-1 illustrates the GPIB input/output hardware configuration.
Transmit Enable
GPIB Line Out
BCR Bit
PIN
NDAC
NRFD
SRQ
GPIB Line In
eliminates
glitches in
REN & IFC
Figure 3-1. GPIB I/O Hardware Configuration
In Figure 3-1, Transmit Enable represents the internal signal that is true when the chip is
driving a particular GPIB control line. GPIB Line Out represents the internal signal that
is true when an interface function within the chip is attempting to assert a GPIB control
signal. BCR Bit corresponds to the bit in the BCR. GPIB LineIn represents the internal
GPIB lines that are inputs to the GPIB interface functions and the BSR. The internal
signals SRQ, NDAC, and NRFD are monitored by the interface functions even when they
are not driven onto the pin. For this reason, the internal value of these signals is ORed
with the external value.
Because the BSR samples the GPIB control lines from the GPIB transceiver—not the
actual GPIB bus—the direction of each line determines the validity of each bit.
Generally, when a signal is an input, the BSR reflects its true bus status, while an output
signal reflects only the NAT7210 value of that particular line. Under normal GPIB
operation, this restriction on the validity of the BSR should not be too limiting, because
the lines that are typically monitored are valid when they are monitored. For example,
the SRQ line is valid in the BSR when the NAT7210 is CIC, which is also when the SRQ
line will be monitored.
The CDOR moves data from the CPU to the GPIB when
the interface is the GPIB Talker or Controller. Writing to
the CDOR sets the local message, nba. When nba is true,
the Source Handshake (SH) function can transfer the data
or command in the CDOR to other GPIB devices.
Writing to the CDOR also
•Clears the Data Out (DO) bit.
•Clears the DRQ signal (unless DMAO = 0).
The host interface can write to the CDOR at offset 0 or by
performing a DMA write operation.
The CDOR and the DIR use separate latches. A read of
the DIR does not change data in the CDOR. The CDOR
is a transparent latch; thus, the GPIB data bus (DIO(8–1))
reflects changes on the CPU data bus during write cycles
to the CDOR.
The host interface can examine the GPIB DIO lines by reading the Command Pass
Through Register (CPTR). The CPTR has no storage; the host interface should read the
CPTR only during a DAC holdoff. See the DAC Holdoffs section in Chapter 5, Software
The Data In Register (DIR) holds data that the NAT7210
receives when the NAT7210 is a Listener. The NAT7210
latches GPIB data into the DIR when LACS & ACDS is
true.
Latching data into the DIR causes the DI bit (ISR1[0]) to
set, unless the NAT7210 is in continuous mode (see
AUXMR[1:0]). Usually, latching data into the DIR
causes an RFD holdoff (see The GPIB rdy Message and
RFD Holdoffs section in Chapter 5, Software
Considerations).
The host interface can read the DIR at offset 0 or by
asserting the DACK* and RD* pins. Reading the DIR
also
•Clears DI (ISR1[0]).
•Clears the DRQ signal if DMAI (IMR2[4]) is set.
•Clears an RFD holdoff (depending on several other
conditions).
The DIR and the CDOR use separate latches. When the
host interface writes to the CDOR, data in the DIR is not
changed.
EOSR holds the byte that the NAT7210 uses to detect the end of a GPIB data block
transfer. The NAT7210 compares data it receives to a 7- or 8-bit byte (ASCII or
binary—depending on the BIN bit) in the EOSR in order to detect the end of a block of
data.
If the NAT7210 is a Listener and REOS = 1, the END bit is set in ISR1 whenever the
received data byte matches the EOSR. If the NAT7210 is a Talker and XEOS = 1, the
END message (GPIB EOI* line asserted low) is sent along with a data byte whenever the
data byte matches the EOSR.
ICR determines the internal clock frequency of the NAT7210. You write to the ICR at
the same offset as the AUXMR.
Note:The ICR resets to 00101000 (8 MHz).
BitMnemonicDescription
3–0F(3–0)Clock Frequency
These bits, in addition to MICR (ICR2[0]), determine the
length of certain delays that are required by the
IEEE 488 standard. You should set these bits according
to the frequency of the signal driving the CLK pin. For
proper operation, set F(3–0) and MICR as follows:
Interrupt Status Register 0 (ISR0) contains Interrupt Status bits and Internal Status bits.
Interrupt Mask Register 0 (IMR0) contains Interrupt Enable bits and Internal Control bits.
If an Interrupt Enable is true when the corresponding status condition or event occurs, the
NAT7210 can generate a hardware interrupt request. See the Generating HardwareInterrupts section in Chapter 5, Software Considerations.
Bits in ISR0 are set and cleared regardless of the status of bits in IMR0. If an interrupt
condition occurs at the same time the host interface is reading ISR0, the NAT7210 does
not set the corresponding Interrupt Status bit until the read is finished. A hardware reset
clears all bits in IMR0 except GLINT, which is set.
BitMnemonicDescription
7rnbaNew Byte Available local message bit
nba reflects the status of the local New Byte Available
message.
nba is set on writes to the CDOR. nba is cleared by
pon + nbaf + (NTNL & SIDS) + STRS
7wGLINTGlobal Interrupt Enable bit
GLINT enables the NAT7210 to assert the INT pin. If
GLINT = 0, the INT pin does not assert. See the
Generating Hardware Interrupts section in Chapter 5,
Software Considerations.
6rSTBOStatus Byte Out bit
6wSTBO IEStatus Byte Out Interrupt Enable bit
STBO IE determines how the NAT7210 requests service
and responds to serial polls. See the Serial Polling
section in Appendix B, Introduction to the GPIB.
If STBO IE = 0, the rsv bit in SPMR can be used to
request service. When the GPIB Controller serial polls
the NAT7210, the NAT7210 transmits the current value
of SPMR.
If STBO IE = 1, the rsv bit in the SPMR has no effect on
the Service Request (SR1) function and rsv must be
generated through the reqt auxiliary command. STBO
sets when the GPIB Controller serial polls the NAT7210.
In response to STBO, the host interface writes a byte to
SPMR, then the NAT7210 transmits this byte as the Serial
Poll response.
STBO is set by
STBO IE & SPAS
STBO is cleared by
pon + (write SPMR) + ~SPAS
5rNLNew Line Receive bit
NL is set when the NAT7210 accepts the ASCII new line
character from the GPIB data bus.
If NLEN = 1, the NAT7210 treats the 7-bit ASCII new
line character (0A hex) as an EOS character. The
Acceptor Handshake function responds to the acceptance
of a new line character in the same manner as if EOI were
sent.
4rEOSEnd-of-String bit
The EOS bit indicates that the END bit in ISR1 was set by
the acceptance of the End-of-String character.
EOS is set by
LACS & EOS & REOS & ACDS
EOS is cleared by
pon + (LACS & ~EOS & ACDS) + ~REOS
3rIFCIIFC Interrupt bit
3wIFCI IEIFC Interrupt Enable bit
IFCI is set on the assertion of the GPIB IFC* line.
IFCI is cleared by
pon + (read ISR0) & ~SISB + clearIFCI
2rATNIATN Interrupt bit
2wATNI IEATN Interrupt Enable bit
ATNI is set on the assertion of the ATN* line.
ATNI is cleared by
0rSYNCGPIB Synchronization bit
0wSYNC IEGPIB Synchronization Interrupt Enable bit
SYNC reflects the status of GPIB handshake lines after a
transfer. SYNC is set at the completion of a transfer when
the GPIB handshake is complete. An interrupt is
generated when SYNC IE and SYNC are set.
Interrupt Status Register 1 (ISR1) contains eight Interrupt Status bits. Interrupt Mask
Register 1 (IMR1) contains eight Interrupt Enable bits that directly correspond to the
Interrupt Status bits in ISR1. As a result, ISR1 and IMR1 service eight possible interrupt
conditions; each condition has an associated Interrupt Status bit and an Interrupt Enable
bit. If an Interrupt Enable bit is true when the corresponding status condition or event
occurs, the NAT7210 can generate a hardware interrupt request. See the GeneratingHardware Interrupts section in Chapter 5, Software Considerations.
Bits in ISR1 are set and cleared regardless of the status of the Interrupt bits in IMR1.
If an interrupt condition occurs at the same time the host interface is reading ISR1, the
NAT7210 does not set the corresponding Interrupt Status bit until the read is finished.
A hardware reset clears all bits in IMR1.
BitMnemonicDescription
7rCPTCommand Pass Through bit
7wCPT IECommand Pass Through Interrupt Enable bit
The CPT bit can flag the occurrence of two types of GPIB
commands: undefined commands and user-specified
commands.
When CPT ENAB = 1, the CPT bit flags the occurrence
of undefined commands and all following secondary
commands. The CPT bit flags undefined Address
Command Group (ACG) commands only when the
NAT7210 is an addressed Talker or Listener. The host
interface can read the CPTR to determine the command
the NAT7210 received.
The CPT bit also flags the occurrence of commands that
you specify when you set the AUXRE[3–0] or
AUXRF[3–0] bits.
When the CPT bit flags a command, the NAT7210
remains in a DAC Holdoff state until the host interface
writes the valid or invalid auxiliary command to the
AUXMR.
When APT sets, the NAT7210 enters the DAC Holdoff
state. When the host interface writes the valid or invalid
auxiliary command to the AUXMR, the NAT7210 exits
the DAC Holdoff state.
5rDETDevice Execute Trigger bit
5wDET IEDevice Execute Trigger Interrupt Enable bit
DET indicates that the NAT7210 received the GPIB
Group Execute Trigger (GET) command while the
NAT7210 was a GPIB Listener.
DET is set by
DTAS = GET & LADS & ACDS
DET is cleared by
pon + (read ISR1) & ~SISB + clearDET
4rEND RXEnd Received bit
4wEND IEEnd Received Interrupt Enable bit
END RX sets when the NAT7210, as a Listener, receives
a data byte satisfying the END condition. A data byte
satisfies the END condition if one of the following
conditions is true:
•REOS = 1 and the data byte matches the contents of
the EOSR.
•NLEN = 1 and the data byte matches the ASCII new
line character (hex 0A).
•The GPIB EOI signal is asserted when the byte is
received.
3rDECDevice Clear bit
3wDEC IEDevice Clear Interrupt Enable bit
DEC indicates that either the NAT7210 received the
GPIB Device Clear (DCL) command or that the
NAT7210 was a GPIB Listener and received the GPIB
Selected Device Clear (SDC) command.
DEC is set by
DCAS = (SDC & LADS + DCL) & ACDS
DEC is cleared by
pon + (read ISR1) & ~SISB + clearDEC
2rERRError bit
2wERR IE Error Interrupt Enable bit
The definition of ERR depends on NTNL. When
NTNL = 0, ERR indicates that the contents of the CDOR
have been lost. ERR sets when the NAT7210 sends data
over the GPIB while no Listener exists on the GPIB.
ERR also sets when a byte is written to the CDOR during
SIDS or when a transition from SDYS to SIDS occurs.
When NTNL = 1, ERR indicates that the source
handshake has attempted to send data or commands across
the bus but has found no Listeners (that is, NDAC and
NRFD were unasserted). Data is not lost. The SH
function does not source the data or command until a
Listener appears (that is, NDAC asserts).
1rDOData Out bit
1wDO IEData Out Interrupt Enable bit
DO indicates that the NAT7210, as GPIB Talker, is ready
to accept another data byte into the CDOR. This data byte
will be transmitted to the GPIB. DO clears when a byte is
written to the CDOR or when the NAT7210 ceases to be
the Active Talker.
DO is set by
TACS & SGNS & ~nba
DO is cleared by
~TACS + ~SGNS + nba + (read ISR1) & ~SISB
0rDIData In bit
0wDI IEData In Interrupt Enable Bit
DI indicates that the NAT7210, as a GPIB Listener, has
accepted a data byte from the GPIB Talker.
Interrupt Status Register 2 (ISR2) contains Interrupt Status bits and Internal Status bits.
Interrupt Mask Register 2 (IMR2) contains Interrupt Enable bits and Internal Control bits.
If an Interrupt Enable is true when the corresponding status condition or event occurs, the
NAT7210 can generate a hardware interrupt request. See the Generating HardwareInterrupts section in Chapter 5, Software Considerations.
Bits in ISR2 are set and cleared regardless of the status of the bits in IMR2. If an
interrupt condition occurs at the same time the host interface is reading ISR2, the
NAT7210 does not set the corresponding Interrupt Status bit until the read is finished.
A hardware reset clears all bits in IMR2.
BitMnemonicDescription
7rINTInterrupt bit
This bit is the logical OR of the Enabled Interrupt Status
bits in ISR0, ISR1, and ISR2.
6r SRQI Service Request bit
6w SRQI IE Service Request Interrupt Enable bit
SRQI indicates that the NAT7210, as CIC, received a
GPIB Service Request (SRQ) message. SRQI is normally
edge sensitive; however, consider the following sequence
of events:
1. SRQ asserts, which asserts SRQI.
2. The control program clears SRQI, but SRQ remains
asserted.
3. The NAT7210 serial polls a device.
4. The device sends the RQS message to the NAT7210
in response to the serial poll.
5. SRQ remains asserted because another device (not
the one being serial polled) is asserting SRQ.
In the situation outlined above, SRQI sets at the end of the
serial poll, even if SRQ never unasserts. In addition, if
the control program issues the clear SRQI auxiliary
command while SRQ is asserted, the NAT7210 clears
SRQI for one clock pulse and then sets SRQI again.
LOK and REM indicate the status of the GPIB
Remote/Local (RL1) function of the NAT7210.
LOKREMRL1 State
00LOCS
01REMS
10LWLS
11RWLS
See the Remote/Local State Considerations section in
Chapter 5, Software Considerations.
5wDMAODMA Output Enable bit
If DMAO = 1, the DRQ pin asserts when the NAT7210,
as a GPIB Talker, is ready to accept another data byte into
the CDOR.
4wDMAIDMA Input Enable bit
If DMAI = 1, the DRQ pin asserts to indicate that the
NAT7210, as a GPIB Listener, has accepted a data byte
from the GPIB Talker.
3rCOCommand Out bit
3wCO IECommand Out Interrupt Enable bit
CO = 1 indicates that the CDOR is empty and that another
command can be written to it for transmission over the
GPIB without overwriting a previous command.
You use the Parallel Poll Register (PPR) to locally configure the manner in which the
NAT7210 responds to a parallel poll. You write to the PPR at the same offset as the
AUXMR. See the Parallel Polling section in Appendix B, Introduction to the GPIB.
When you use remote Parallel Poll Configuration (IEEE 488 capability code PP1), do not
write to the PPR: writing to the PPR after it is remotely configured corrupts the
configuration. The NAT7210 implements remote configuration fully and automatically
without software assistance. However, you must still set or clear the individual status
(ist) message (by using Set/Clear Parallel Poll Flag auxiliary commands) according to
pre-established system protocol convention.
When you use the local Parallel Poll Configuration (capability code PP2), write to the
PPR in advance of a poll. If PP2 (AUXRI[2]w) = 0, the contents written to the PPR are
overwritten if the Controller sends a Parallel Poll command (such as PPE or PPD while in
PACS or PPU) that causes the remote configuration to override the local configuration.
If PP2 = 1, the reception of parallel poll commands does not affect the contents of the
PPR and the local configuration determines the response during parallel polls.
BitMnemonicDescription
4wUUnconfigure bit
The U bit determines whether the NAT7210 is locally
configured to participate in parallel polls. If U = 1, the
NAT7210 does not participate in parallel polls unless it is
remotely configured to do so. If the host interface sets U,
it should clear S and P[3–1] simultaneously.
If U = 0, the NAT7210 participates in parallel polls and
responds in the manner defined by PPR[3] through
PPR[0] and by ist. S and P[3–1] are the same as the bits
of the same name in the PPE message, and the I/O write
operation to the PPR is the same as the receipt of the PPE
message from the GPIB Controller.
P[3–1] indicate which of the eight DIO lines is asserted
during a parallel poll. The following table shows the
signal on which the NAT7210 responds to parallel polls.
P[3–1]Signals on which NAT7210
Responds to Parallel Polls
000
001
010
011
100
101
110
111
For examples of PPR configuration, see Chapter 6, ControllerSoftware Considerations.
The Source/Acceptor Status Register (SASR) contains status bits that you can use to
determine the state of the Source and Acceptor functions.
BitMnemonicDescription
7rnbaNew Byte Available local message
6rAEHSAcceptor End Holdoff State bit
5rANHS1Acceptor Not Ready Holdoff bit
4rANHS2Acceptor Not Ready Holdoff Immediately bit
3rADHSAcceptor Data Holdoff State bit
2rACRDYAcceptor Ready State bit
Use this bit to determine the state of the Acceptor
Handshake. By monitoring the LA and ATN bits in the
ADSR, the DAV bit in the BSR, and the ADHS and
ACRDY bits, you can determine the state of the Acceptor
Handshake function as described below:
Use these bits to determine the state of the Source
Handshake interface function. By monitoring the TA,
Serial Poll Mode State (SPMS), ATN bits in the ADSR,
and the SH1A and SH1B bits, you can determine the state
of the Source Handshake function as described below:
5–0r,S[6–1]Serial Poll Status bits 6 through 1
5–0w
These bits send device- or system-dependent status
information over the GPIB when the Controller serial
polls the NAT7210.
When STBO IE = 0, the NAT7210 transmits a byte of
status information, SPMR[7–0], to the CIC if the CIC
serial polls the NAT7210. The SPMR bits S[8, 6–1] are
double buffered. If the host interface writes to the SPMR
during a serial poll when SPAS is active, the NAT7210
saves the value. The NAT7210 updates the SPMR when
the NAT7210 exits SPAS.
When STBO IE = 1 and the Controller serial polls the
NAT7210, the STBO interrupt condition sets. The host
interface should write the STB and the RQS bit to the
SPMR in response to an STBO interrupt.
Issuing the Chip Reset auxiliary command clears these
bits.
PEND sets when rsv = 1. PEND clears when the
NAT7210 is in the Negative Poll Response State (NPRS)
and the local Request Service (rsv) message is false. By
reading the PEND status bit, you can confirm that a
request was accepted and that the Status Byte (STB) was
transmitted (PEND = 0).
6wrsv/RQSRequest Service/ RQS bit
When STBO IE = 0, bit 6 is the rsv bit. The rsv bit
generates the GPIB local rsv message. When rsv = 1 and
the GPIB Controller is not serial polling the NAT7210,
the NAT7210 enters the Service Request State (SRQS)
and asserts the GPIB SRQ signal. When the Controller
reads the STB during the poll, the NAT7210 clears rsv.
The rsv bit is also cleared by a hardware reset or by
writing 0 to it. Issuing the Chip Reset auxiliary command
also clears rsv.
When STBO IE = 1, bit 6 is the RQS bit. When the
Controller serial polls the NAT7210, the STBO interrupt
condition sets. The host interface should write the STB
and the RQS bit to the SPMR in response to an STBO
interrupt. The NAT7210 transfers the STB and RQS to
the Controller during that particular serial poll. A
hardware reset clears RQS. Issuing the Chip Reset
auxiliary command also clears RQS.
The Version Status Register (VSR) contains a value that is unique to each NAT7210
revision. You can use the VSR to distinguish a NAT7210 from a µPD7210. Future
versions of the NAT7210 may read 10XX.
BitMnemonicDescription
7–4rV[3 –0]The version number of the NAT7210APD is 1000.
This chapter contains NAT7210 address maps and detailed descriptions of the NAT7210
interface registers in 9914 mode. For 7210-mode register descriptions, see Chapter 3,
7210-Mode Interface Registers.
9914 Register Map
Table 4-1 is the register bit map for the NAT7210 in 9914 mode.
Notice that bold-ruled cells distinguish six registers that are accessible only when the
Page-In state is true. Refer to The Page-In Condition section that immediately follows
the register map for more information.
Four writable registers can appear at the same offset as the Address Status Register
(ADSR) (offset 4). After a hardware or software reset, no writable register appears at the
ADSR offset: the NAT7210 ignores writes to that offset.
One Page-In auxiliary command exists for each of the four registers. The host interface
can make one of the four registers accessible by issuing the appropriate Page-In
command to the Auxiliary Command Register (AUXCR). The paged-in register remains
accessible at the ADSR offset until the host interface pages-in another register or issues
the Clear Page-In Register auxiliary command.
When any one of the four writable registers is accessible at the ADSR offset, Interrupt
Status Register 2 (ISR2) is accessible at the same offset as ADR, and the Serial Poll
Status Register (SPSR) is accessible at the same offset as the Serial Poll Mode Register
(SPMR).
Hidden Registers
In addition to the registers shown in Table 4-1, the NAT7210 contains hidden registers.
All hidden registers are write-only registers. Two or more hidden registers can appear at
the same offset. When you write an 8-bit pattern to these offsets, some of the bits
determine which hidden register will be written. The other bits represent the value
written to the register.
Accessory Read Register Map
Several hidden registers appear at the ACCR offset. Table 4-2 shows these hidden
registers.
Table 4-2. Hidden Registers at the ACCR Offset
RegisterBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
ICR 0010 F3 F2 F1 F0
ACCA100BINXEOSREOS00
ACCB101ISSINVLWCSPEOIATCT
Some 7210-mode registers and 9914-mode registers share identical names. The
7210-mode registers are described in Chapter 3, 7210-Mode Interface Registers. If you
are using the NAT7210 in 9914 mode, be sure to read the proper description for the
9914-mode registers.
All registers are listed in alphabetical order. The registers are alphabetized according to
their mnemonics.
Accessory Register A (ACCRA) controls the EOS and END messages. A hardware reset
or the ch_rst auxiliary command clears ACCRA.
BitMnemonicDescription
4wBINBinary bit
The BIN bit selects the length of the EOS message. If
BIN = 1, the EOSR is treated as an 8-bit byte. When
BIN = 0, the EOSR is treated as a 7-bit register (for
ASCII characters), and only a 7-bit comparison is done
with the data on the GPIB.
3wXEOSTransmit END With EOS bit
The XEOS bit permits or prohibits automatic transmission
of the GPIB END message at the same time as the EOS
message when the NAT7210 is in Talker Active State
(TACS). If XEOS = 1 and the byte in the CDOR matches
the contents of the EOSR, the EOI line is sent true along
with the data.
2wREOSEND On EOS Received bit
The REOS bit permits or prohibits setting the END bit
(ISR0[3]r) when the NAT7210 receives the EOS message
as a Listener. If REOS = 1 and the byte in the DIR
matches the byte in the EOSR, the END bit (ISR1[4]r) is
set and the acceptor function treats the EOS character just
as if it were received with EOI asserted.
ISS determines the value of the NAT7210 ist message.
When ISS = 1, ist takes on the value of the NAT7210
SRQS. (The NAT7210 is asserting the GPIB SRQ
message when it is in SRQS.) If ISS = 0, ist takes on the
value of the NAT7210 Parallel Poll Flag. You set and
clear the Parallel Poll Flag by using the Set Parallel Poll
Flag and Clear Parallel Poll Flag auxiliary commands.
3wINVInvert bit
INV determines the polarity of the INT pin.
INV BitINT Pin Polarity
0Active High
1Active Low
See the Generating Hardware Interrupts section in
Chapter 5, Software Considerations.
2wLWCListen When Controller bit
LWC enables the NAT7210 to accept command bytes that
the NAT7210 sources when it is CIC. If LWC = 0, the
NAT7210 does not accept command bytes sent by the
NAT7210.
SPEOI determines whether the NAT7210 sends EOI
when a Controller serial polls the NAT7210.
SPEOIEOI During Serial Polls
0Sent False
1Sent True
0wATCTAutomatic Take Control bit
If ATCT = 1, the NAT7210 can—without software
intervention—take control when another CIC passes
control to the NAT7210. Use the CIC bit (ISR2[0] to
determine when the NAT7210 receives control. See the
GPIB Controller Considerations section in Chapter 6,
Controller Software Considerations.
Accessory Register E (ACCRE) determines how the NAT7210 uses a Data Accepted
(DAC) holdoff. A hardware reset or the ch_rst auxiliary command clears ACCRE.
Each bit of ACCRE enables DAC holdoffs on a GPIB command or group of
commands. When a GPIB Controller sends the specified command to the NAT7210,
the Unrecognized Command (UNC) bit sets and the NAT7210 performs a DAC holdoff.
See the DAC Holdoffs section in Chapter 5, Software Considerations.
Accessory Register F (ACCRF) determines how the NAT7210 uses a DAC holdoff.
A hardware reset or the ch_rst auxiliary command clears ACCRF.
Each bit of ACCRF enables DAC holdoffs on a GPIB command or group of commands.
When a GPIB Controller sends the specified command to the NAT7210, the UNC bit sets
and the NAT7210 performs a DAC holdoff. See the DAC Holdoffs section in Chapter 5,
Software Considerations.
BitMnemonicDescription
3wDHATADAC Holdoff On All Talker Addresses bit
2wDHALADAC Holdoff On All Listener Addresses bit
1wDHUNTLDAC Holdoff On The UNT Or UNL Command bit
0wDHALLDAC Holdoff On All UCG, ACG, And SCG Commands
If USTD = 1, the T1 delay can be as short as 350 ns. See
the T1 Delay Generation section in Chapter 5, SoftwareConsiderations.
2wPP1Parallel Poll bit 1
The PP1 bit permits or prohibits the NAT7210’s ability
to automatically respond to remote parallel poll
configuration. If PP1 = 1, the NAT7210 can be
configured remotely for parallel polls without software
intervention.
The Acceptor Handshake does not perform a DAC
holdoff or set the UNC bit when it receives a Parallel Poll
Command (PPC or PPU).
If PP1 = 0, parallel polls must be configured through the
PPR, and Parallel Poll commands must be monitored by
UNC.
0wDMAEDMA Enable bit
DMAE lets you use DMAO (IMR0[7]) and DMAI
(IMR0[6]) to enable the DRQ signal.
If DMAE = 0, DRQ always asserts when the NAT7210
receives a data byte as a Listener or when the NAT7210 is
a Talker and the CDOR is empty.
ADR is used to load the primary GPIB address of the interface.
BitMnemonicDescription
7wedpaEnable Dual Primary Addressing Mode bit
Setting edpa enables the dual primary addressing mode of
the NAT7210. If edpa = 1, the NAT7210 ignores the least
significant bit (A1) of its GPIB address. The NAT7210
then has two consecutive primary addresses. The ulpa bit
in the Address Status Register indicates which address is
active.
6wdalDisable Listener bit
Setting dal returns the NAT7210 Listener function to
LIDS and forces the NAT7210 Listener function to
remain in LIDS even if the chip receives its GPIB listen
address or a lon auxiliary command.
5wdatDisable Talker bit
Setting dat returns the NAT7210 Talker function to TIDS
and forces the Talker function to remain in TIDS even if
the chip receives its GPIB talk address or a ton auxiliary
command.
4–0wA[5–1]NAT7210 GPIB Address bits 5 through 1
A[5–1] specify the primary GPIB address of the
NAT7210. The corresponding GPIB talk address is
formed by adding hex 40 to A[5–1], while the
corresponding GPIB listen address is formed by adding
hex 20. A[5–1] should not be 11111 (binary) to prevent
the corresponding talk and listen addresses from
conflicting with the GPIB UNT and GPIB UNL
commands.
TPAS indicates that the NAT7210 has accepted its
primary talk address.
TPAS is cleared by
(PCG & ~MTA & ACDS) + pon
2rLAListener Active bit
LA = 1 when the NAT7210 has been addressed or
programmed as a GPIB Listener—that is, the NAT7210 is
in LACS or LADS. The NAT7210 is addressed to listen
when it receives its listen address from the CIC. You can
also program the NAT7210 to listen by using the
Listen-Only auxiliary command.
If the NAT7210 is addressed to listen, it is automatically
unaddressed to talk.
LA is cleared by
pon + IFC + (UNL & ACDS)
1rTATalker Active bit
TA = 1 when the NAT7210 has been addressed or
programmed as the GPIB Talker—that is, the NAT7210 is
in TACS, TADS, or SPAS. The NAT7210 can be
addressed to talk when it receives its talk address from the
CIC. You can also program the NAT7210 to talk by
using the Talk-Only auxiliary command.
If the NAT7210 is addressed to talk, it is automatically
unaddressed to listen.