COP8FG Family
8-Bit CMOS ROM Based and OTP Microcontrollers with
8k to 32k Memory, Two Comparators and USART
General Description
Note: COP8FG devices are 15 MHz versions of the
COP8SG devices.
The COP8FGx5 Family ROM based microcontrollers are
highly integrated COP8
32k memory and advanced features including Analog comparators, and zero external components. These single-chip
CMOS devices are suited for more complex applications requiring a full featured controller with larger memory,lowEMI,
two comparators, and a full-duplex USART. COP8FGx7 devices are 100%form-fit-function compatible 8k or 32k OTP
(One Time Programmable) versions for use in production or
development.
™
Feature core devices with 8k to
July 1999
Erasable windowed versions are available for use with a
range of COP8 software and hardware development tools.
Family features include an 8-bit memory mapped architecture, 15 MHz CKI with 0.67 µs instruction cycle, 14 interrupts, three multi-function 16-bit timer/counters with PWM,
full duplex USART, MICROWIRE/PLUS
parators, two power saving HALT/IDLE modes, MIWU, idle
timer, on-chip R/C oscillator, high current outputs, user selectable options (WATCHDOG
power-on-reset), 4.5V to 5.5V operation, program code security, and 28/40/44 pin packages.
Devices included in this datasheet are:
™
, two analog com-
™
, 4 clock/oscillator modes,
COP8FG Family, 8-Bit CMOS ROM Based and OTP Microcontrollers with 8k to 32k Memory, Two
Comparators and USART
DeviceMemory (bytes)
COP8FGE58k ROM25624/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
COP8FGG516k ROM51224/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
COP8FGH520k ROM51224/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
COP8FGK524k ROM51224/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
COP8FGR532k ROM51224/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
COP8FGE78k OTP EPROM25624/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
COP8FGR732k OTP EPROM51224/36/4028 DIP/SOIC, 40 DIP, 44 PLCC/QFP-40 to +85˚C
n Low cost 8-bit microcontroller
n Quiet Design (low radiated emissions)
n Multi-Input Wakeup pins with optional interrupts (8 pins)
n Mask selectable clock options
n Internal Power-On-Reset—user selectable
n WATCHDOG and Clock Monitor Logic—user selectable
n Eight high current outputs
n 256 or 512 bytes on-board RAM
n 8k to 32k ROM or OTP EPROM with security feature
CPU Features
n Versatile easy to use instruction set
n 0.67 µs instruction cycle time
n Fourteen multi-source vectored interrupts servicing
— External interrupt / Timers T0 — T3
— MICROWIRE/PLUS Serial Interface
— Multi-Input Wake Up
COP8™, MICROWIRE/PLUS™, and WATCHDOG™are trademarks of National SemiconductorCorporation.
®
TRI-STATE
is a registered trademark of National Semiconductor Corporation.
®
iceMASTER
is a registered trademark of MetaLink Corporation.
n Idle Timer (T0)
n MICROWIRE/PLUS Serial Interface (SPI Compatible)
n Full Duplex USART
n Two Analog Comparators
I/O Features
n Software selectable I/O options (TRI-STATE
Output,Push-Pull Output, Weak Pull-Up Input, and High
Impedance Input)
n Schmitt trigger inputs on ports G and L
n Eight high current outputs
n Packages: 28 SO with 24 I/O pins, 40 DIP with 36 I/O
pins, 44 PLCC and PQFP with 40 I/O pins
®
Block Diagram
Fully Static CMOS Design
n Low current drain (typically<4 µA)
n Two power saving modes: HALT and IDLE
Temperature Range
n −40˚C to +85˚C
Development Support
n Windowed packages for DIP and PLCC
n Real time emulation and full program debug offered by
MetaLink Development System
FIGURE 1. COP8FGx Block Diagram
www.national.com2
DS101116-44
1.0 Device Description
1.1 ARCHITECTURE
The COP8 family is based on a modified Harvard architecture, which allows data tables to be accessed directly from
program memory. This is very important with modern
microcontroller-based applications, since program memory
is usually ROM or EPROM, while data memory is usually
RAM. Consequently data tables need to be contained in
non-volatile memory,so they are not lost when the microcontroller is powered down. In a modified Harvard architecture,
instruction fetch and memory data transfers can be overlapped with a two stage pipeline, which allows the next instruction to be fetched from program memory while the current instruction is being executed using data memory. This is
not possible with a Von Neumann single-address bus architecture.
The COP8 family supports a software stack scheme that allows the user to incorporate many subroutine calls. This capability is important when using High Level Languages. With
a hardware stack, the user is limited to a small fixed number
of stack levels.
1.2 INSTRUCTION SET
In today’s 8-bit microcontroller application arena cost/
performance, flexibility and time to market are several of the
key issues that system designers face in attempting to build
well-engineered products that compete in the marketplace.
Many of these issues can be addressed through the manner
in which a microcontroller’s instruction set handles processing tasks. And that’s why COP8 family offers a unique and
code-efficient instruction set— one that provides the flexibility,functionality, reduced costs and faster time to market that
today’s microcontroller based products require.
Code efficiency is important because it enables designers to
pack more on-chip functionality into less program memory
space. Selecting a microcontroller with less program
memory size translates into lower system costs, and the
added security of knowing that more code can be packed
into the available program memory space.
1.2.1 Key Instruction Set Features
The COP8 family incorporates a unique combination of instruction set features, which provide designers with optimum
code efficiency and program memory utilization.
Single Byte/Single Cycle Code Execution
The efficiency is due to the fact that the majority of instructions are of the single byte variety, resulting in minimum program space. Because compact code does not occupy a substantial amount of program memory space, designers can
integrate additional features and functionality into the microcontroller program memory space. Also, the majority instructions executed by the device are single cycle, resulting in
minimum program execution time. In fact, 77%of the instructions are single byte single cycle, providing greater code and
I/O efficiency, and faster code execution.
1.2.2 Many Single-Byte, Multifunction Instructions
The COP8 instruction set utilizes many single-byte, multifunction instructions. This enables a single instruction to accomplish multiple functions, such as DRSZ, DCOR, JID, LD
(Load) and X (Exchange) instructions with post-incrementing
and post-decrementing, to name just a few examples. In
many cases, the instruction set can simultaneously execute
as many as three functions with the same single-byte instruction.
JID: (Jump Indirect); Single byte instruction; decodes external events and jumps to corresponding service routines
(analogous to “DO CASE” statements in higher level languages).
LAID: (Load Accumulator-Indirect); Single byte look up table
instruction provides efficient data path from the program
memory to the CPU. This instruction can be used for table
lookup and to read the entire program memory for checksum
calculations.
RETSK: (Return Skip); Single byte instruction allows return
from subroutine and skips next instruction. Decision to
branch can be made in the subroutine itself, saving code.
AUTOINC/DEC: (Auto-Increment/Auto-Decrement); These
instructions use the two memory pointers B and X to efficiently process a block of data (analogous to “FOR NEXT” in
higher level languages).
1.2.3 Bit-Level Control
Bit-level control over many of the microcontroller’s I/O ports
provides a flexible means to ease layout concerns and save
board space. All members of the COP8 family provide the
ability to set, reset and test any individual bit in the data
memory address space, including memory-mapped I/O ports
and associated registers.
1.2.4 Register Set
Three memory-mapped pointers handle register indirect addressing and software stack pointer functions. The memory
data pointers allow the option of post-incrementing or postdecrementing with the data movement instructions (LOAD/
EXCHANGE). And 15 memory-maped registers allow designers to optimize the precise implementation of certain
specific instructions.
1.3 EMI REDUCTION
The COP8FGx5 family of devices incorporates circuitry that
guards against electromagnetic interference— an increasing
problem in today’s microcontroller board designs. National’s
patented EMI reduction technology offers low EMI clock circuitry,gradual turn-on output drivers (GTOs) and internal I
smoothing filters, to help circumvent many of the EMI issues
influencing embedded control designs. National has
achieved 15 dB–20 dB reduction in EMI transmissions when
designs have incorporated its patented EMI reducing circuitry.
1.4 PACKAGING/PIN EFFICIENCY
Real estate and board configuration considerations demand
maximum space and pin efficiency,particularly given today’s
high integration and small product form factors. Microcontroller users try to avoid using large packages to get the I/O
needed. Large packages take valuable board space and increases device cost, two trade-offs that microcontroller designs can ill afford.
The COP8 family offersa wide range of packages and do not
waste pins: up to 90.9%(or 40 pins in the 44-pin package)
are devoted to useful I/O.
CC
www.national.com3
Connection Diagrams
Note 1: X=E for 8k, G for 16k,
H for 20k, K for 24k, R for 32k
Y=5 for ROM, 7 for OTP
Top View
Order Number COP8FGXY28M8
See NS Package Number M28B
Order Number COP8FGXY28N8
See NS Package Number N28A
Order Number COP8FGR728Q3
See NS Package Number D28JQ
DS101116-4
DS101116-5
Top View
Order Number COP8FGXY40N8
See NS Package Number N40A
Order Number COP8FGR540Q3
See NS Package Number D40KQ
DS101116-6
Top View
Order Number COP8FGXY44V8
See NS Package Number V44A
Order Number COP8FGR744J3
L0I/OMIWU11171711
L1I/OMIWU or CKX12181812
L2I/OMIWU or TDX13191913
L3I/OMIWU or RDX14202014
L4I/OMIWU or T2A15212519
L5I/OMIWU or T2B16222620
L6I/OMIWU or T3A17232721
L7I/OMIWU or T3B18242822
G0I/OINT25353933
G1I/OWDOUT*26364034
G2I/OT1B27374135
G3I/OT1A28384236
G4I/OSO13341
G5I/OSK24442
G6ISI35543
G7ICKO46644
D0O19252923
D1O20263024
D2O21273125
D3O22283226
D4O293327
D5O303428
D6O313529
D7O323630
F0I/O7993
F1I/OCOMP1IN−810104
F2I/OCOMP1IN+911115
F3I/OCOMP1OUT1012126
F4I/OCOMP2IN−13137
F5I/OCOMP2IN+14148
F6I/OCOMP2OUT15159
F7I/O161610
C0I/O394337
C1I/O404438
C2I/O1139
C3I/O2240
C4I/O2115
C5I/O2216
C6I/O2317
C7I/O2418
V
CC
GND23333731
CKII5771
RESET
* G1 operation as WDOUT is controlled by ECON bit 2.
I24343832
68 8 2
www.national.com5
2.1 Ordering Information
DS101116-8
FIGURE 3. Part Numbering Scheme
www.national.com6
3.0 Electrical Characteristics
Absolute Maximum Ratings
If Military/Aerospace specified devices are required,
please contact the National Semiconductor Sales Office/
Distributors for availability and specifications.
Supply Voltage (V
Voltage at Any Pin−0.3V to V
Total Current into V
Pin (Source)100 mA
)7V
CC
CC
(Note 2)
CC
+0.3V
Total Current out of GND
Pin (Sink)110 mA
Storage Temperature
Range−65˚C to +140˚C
ESD Protection Level2kV (Human Body Model)
Note 2:
Absolute maximum ratings indicate limits beyond which damage to
the device may occur. DC and AC electrical specifications are not ensured
when operating the device at absolute maximum ratings.
DC Electrical Characteristics
−40˚C ≤ TA≤ +85˚C unless otherwise specified.
ParameterConditionsMinTypMaxUnits
Operating Voltage4.55.5V
Power Supply Rise Time1050 x 10
V
Start Voltage to Guarantee POR00.25V
CC
Power Supply Ripple (Note 4)Peak-to-Peak0.1 V
Supply Current (Note 5)
CKI = 15 MHzV
CKI = 10 MHzV
CKI = 4 MHzV
HALT Current (Note 6)V
= 5.5V, tC= 0.67 µs9.0mA
CC
= 5.5V, tC= 1 µs6.0mA
CC
= 4.5V, tC= 2.5 µs2.1mA
CC
= 5.5V, CKI=0MHz
CC
<
410 µA
IDLE Current (Note 5)
CKI = 15 MHzV
CKI = 10 MHzV
CKI = 4 MHzV
Input Levels (V
IH,VIL
)
= 5.5V, tC= 0.67 µs2.25mA
CC
= 5.5V, tC= 1 µs1.5mA
CC
= 4.5V, tC= 2.5 µs0.8mA
CC
RESET
Logic High0.8 V
cc
Logic Low0.2 V
CKI, All Other Inputs
Logic High0.7 V
cc
Logic Low0.2 V
Internal Bias Resistor for the
0.512MΩ
Crystal/Resonator Oscillator
CKI Resistance to V
Oscillator is selected
Hi-Z Input LeakageV
Input Pullup CurrentV
G and L Port Input HysteresisV
Note 3: tC= Instruction cycle time.
Note 4: Maximum rate of voltage change must be
Note 5: Supply and IDLE currents are measured with CKI driven with a square wave Oscillator, External Oscillator, inputs connected to V
but not connected to a load.
Note 6: The HALT mode will stop CKI from oscillating in the R/C and the Crystal configurations. In the R/C configuration, CKI is forced high internally. In the crystal
or external configuration, CKI is TRI-STATE. Measurement of I
grammed as low outputs and not driving a load; all outputs programmed low and not driving a load; all inputs tied to V
to HALT mode entered via setting bit 7 of the G Port data register.
Note 7: Pins G6 and RESET are designed with a high voltage input network. These pins allow input voltages
biased at voltages>VCC(the pins do not have source current when biased at a voltage below VCC). The effective resistance to VCCis 750Ω (typical). These two
pins will not latch up. The voltage at the pins must be limited to
ESD transients.
Note 8: The output propagation delay is referenced to the end of the instruction cycle where the output change occurs.
Note 9: Parameter characterized but not tested.
Note 10: Rise times faster than the minimum specification may trigger an internal power-on-reset.
Note 11: MICROWIRE Setup and Hold Times and Propagation Delays are referenced to the appropriate edge of the MICROWIRE clock. See and the MICROWIRE
operation description.
)
C
≤ 5.5V0.67µs
CC
≤ 5.5V2µs
CC
CC
≤ 5.5V
±
35
%
%
= 2.2k, CL= 100 pF
L
≤ 5.5V1.0µs
CC
20ns
56ns
UWH
UWS
) (Note
) (Note
220ns
C
C
C
C
<
0.5 V/ms.
HALT is done with device neither sourcing nor sinking current; with L. F, C, G0, and G2–G5 pro-
DD
<
14V.WARNING: Voltages in excess of 14V will cause damage to the pins. This warning excludes
; clock monitor disabled. Parameter refers
CC
>
VCCand the pins will have sink current to VCCwhen
and outputs driven low
CC
www.national.com8
Comparators AC and DC Characteristics
VCC= 5V, −40˚C ≤ TA≤ +85˚C.
ParameterConditionsMinTypMaxUnits
Input Offset Voltage (Note 12)0.4V ≤ V
≤ VCC− 1.5V
IN
±
5
Input Common Mode Voltage Range0.4V
Voltage Gain100dB
Low Level Output CurrentV
High Level Output CurrentV
= 0.4V−1.6mA
OL
OH=VCC
− 0.4V1.6mA
DC Supply Current per Comparator
(When Enabled)
Response Time (Note 13)200 mV step input
100 mV Overdrive,
100 pF Load
Note 12: The comparator inputs are high impedance port inputs and, as such, input current is limited to port input leakage current.
Note 13: Response time is measured from a step input to a valid logic level at the comparator output. software response time is dependent of instruction execution.
DS101116-9
FIGURE 4. MICROWIRE/PLUS Timing
±
15mV
− 1.5V
CC
150µA
200ns
www.national.com9
Typical Performance Characteristics T
DS101116-49DS101116-50
=
25˚C (unless otherwise specified)
A
DS101116-51DS101116-52
www.national.com10
4.0 Pin Descriptions
The COP8FGx I/O structure enables designers to reconfigure the microcontroller’s I/O functions with a single instruction. Each individual I/O pin can be independently configured
as output pin low, output high, input with high impedance or
input with weak pull-up device. A typical example is the use
of I/O pins as the keyboard matrix input lines. The input lines
can be programmed with internal weak pull-ups so that the
input lines read logic high when the keys are all open. With
a key closure, the corresponding input line will read a logic
zero since the weak pull-up can easily be overdriven. When
the key is released, the internal weak pull-up will pull the input line back to logic high. This eliminates the need for external pull-up resistors. The high current options are available
for driving LEDs, motors and speakers. This flexibility helps
to ensure a cleaner design, with less external components
and lower costs. Below is the general description of all available pins.
V
and GND are the power supply pins. All VCCand GND
CC
pins must be connected.
CKI is the clock input. This can come from the Internal R/C
oscillator, external, or a crystal oscillator (in conjunction with
CKO). See Oscillator Description section.
RESET is the master reset input. See Reset description section.
Each device contains four bidirectional 8-bit I/O ports (C, G,
L and F), where each individual bit may be independently
configured as an input (Schmitt trigger inputs on ports L and
G), output or TRI-STATE under program control. Three data
memory address locations are allocated for each of these
I/O ports. Each I/O port has two associated 8-bit memory
mapped registers, the CONFIGURATION register and the
output DATAregister. A memory mapped address is also reserved for the input pins of each I/O port. (See the memory
map for the various addresses associated with the I/O ports.)
Figure 5
shows the I/O port configurations. The DATA and
CONFIGURATION registers allow for each port bit to be individually configured under software control as shown below:
CONFIGURATION
Register
00Hi-Z Input
01Input with Weak Pull-Up
10Push-Pull Zero Output
11Push-Pull One Output
Port L is an 8-bit I/O port. All L-pins have Schmitt triggers on
the inputs.
Port L supports the Multi-Input Wake Up feature on all eight
pins. Port L has the following alternate pin functions:
L7 Multi-input Wakeup or T3B (Timer T3B Input)
L6 Multi-input Wakeup or T3A (Timer T3A Input)
L5 Multi-input Wakeup or T2B (Timer T2B Input)
L4 Multi-input Wakeup or T2A (Timer T2A Input)
L3 Multi-input Wakeup and/or RDX (USART Receive)
L2 Multi-input Wakeup or TDX (USART Transmit)
L1 Multi-input Wakeup and/or CKX (USART Clock)
L0 Multi-input Wakeup
Port G is an 8-bit port. Pin G0, G2–G5 are bi-directional I/O
ports. Pin G6 is always a general purpose Hi-Z input. All pins
have Schmitt Triggers on their inputs.Pin G1 serves as the
dedicated WATCHDOG output with weak pullup if
DATA
Register
Port Set-Up
(TRI-STATE Output)
WATCHDOG feature is selected by the Mask Option register.The pin is a general purpose I/O if WATCHDOGfeature is not selected. If WATCHDOG feature is selected, bit
1 of the Port G configuration and data register does not have
any effect on Pin G1 setup. Pin G7 is either input or output
depending on the oscillator option selected. With the crystal
oscillator option selected, G7 serves as the dedicated output
pin for the CKO clock output. With the internal R/C or the external oscillator option selected, G7 serves as a general purpose Hi-Z input pin and is also used to bring the device out
of HALT mode with a low to high transition on G7.
Since G6 is an input only pin and G7 is the dedicated CKO
clock output pin (crystal clock option) or general purpose input (R/C or external clock option), the associated bits in the
data and configuration registers for G6 and G7 are used for
special purpose functions as outlined below. Reading the G6
and G7 data bits will return zeroes.
Each device will be placed in the HALT mode by writing a “1”
to bit 7 of the Port G Data Register. Similarly the device will
be placed in the IDLE mode by writing a “1” to bit 6 of the
Port G Data Register.
Writing a “1” to bit 6 of the Port G Configuration Register enables the MICROWIRE/PLUS to operate with the alternate
phase of the SK clock. The G7 configuration bit, if set high,
enables the clock start up delay after HALT when the R/C
clock configuration is used.
Config. Reg.Data Reg.
G7CLKDLYHALT
G6Alternate SKIDLE
Port G has the following alternate features:
G7 CKO Oscillator dedicated output or general purpose in-
put
G6 SI (MICROWIRE Serial Data Input)
G5 SK (MICROWIRE Serial Clock)
G4 SO (MICROWIRE Serial Data Output)
G3 T1A (Timer T1 I/O)
G2 T1B (Timer T1 Capture Input)
G1 WDOUT WATCHDOGand/or CLock Monitor if WATCH-
DOG enabled, otherwise it is a general purpose I/O
G0 INTR (External Interrupt Input)
Port C is an 8-bit I/O port. The 40-pin device does not have
a full complement of Port C pins. The unavailable pins are
not terminated. A read operation on these unterminated pins
will return unpredictable values. The 28 pin device do not offer Port C. On this device, the associated Port C Data and
Configuration registers should not be used.
Port F is an 8-bit I/O port. The 28--pin device does not have
a full complement of Port F pins. The unavailable pins are
not terminated. A read operation on these unterminated pins
will return unpredictable values.
Port F1–F3 are used for Comparator 1. Port F4–F6 are used
for Comparator 2.
The Port F has the following alternate features:
F6 COMP2OUT (Comparator 2 Output)
F5 COMP2+IN (Comparator 2 Positive Input)
F4 COMP2-IN (Comparator 2 Negative Input)
F3 COMP1OUT (Comparator 1 Output)
F2 COMP1+IN (Comparator 1 Positive Input)
F1 COMP1-IN (Comparator 1 Negative Input)
Note: For compatibility with existing software written for COP888xG devices
and with existing Mask ROM devices, a read of the Port I input pins
www.national.com11
4.0 Pin Descriptions (Continued)
(address xxD7) will return the same data as reading the Port F input
pins (address xx96). It is recommended new applications which will go
to production with the COP8FGx use the Port F addresses. Note that
compatible ROM devices contains the input only Port I instead of the
bi-directional Port F.
Port D is an 8-bit output port that is preset high when RESET
goes low. The user can tie two or more D port outputs (except D2) together in order to get a higher drive.
Note: Care must be exercised with the D2 pin operation. At RESET, the ex-
ternal loads on this pin must ensure that the output voltages stay
above 0.7 V
keep the external loading on D2 to less than 1000 pF.
FIGURE 6. I/O Port Configurations— Output Mode
FIGURE 7. I/O Port Configurations— Input Mode
to prevent the chip from entering special modes. Also
CC
FIGURE 5. I/O Port Configurations
DS101116-10
DS101116-12
DS101116-11
5.0 Functional Description
The architecture of the devices are a modified Harvard architecture. With the Harvard architecture, the program memory
ROM is separated from the data store memory (RAM). Both
ROM and RAM have their own separate addressing space
with separate address buses. The architecture, though
based on the Harvard architecture, permits transfer of data
from ROM to RAM.
5.1 CPU REGISTERS
The CPU can do an 8-bit addition, subtraction, logical or shift
operation in one instruction (t
There are six CPU registers:
A is the 8-bit Accumulator Register
PC is the 15-bit Program Counter Register
PU is the upper 7 bits of the program counter (PC)
PL is the lower 8 bits of the program counter (PC)
B is an 8-bit RAM address pointer, which can be optionally
post auto incremented or decremented.
X is an 8-bit alternate RAM address pointer, which can be
optionally post auto incremented or decremented.
S is the 8-bit Segment Address Register used to extend the
lower half of the address range (00 to 7F) into 256 data segments of 128 bytes each.
SP is the 8-bit stack pointer, which points to the subroutine/
interrupt stack (in RAM). With reset the SP is initialized to
RAM address 02F Hex (devices with 64 bytes of RAM), or
initialized to RAM address 06F Hex (devices with 128 bytes
of RAM).
All the CPU registers are memory mapped with the exception of the Accumulator (A) and the Program Counter (PC).
5.2 PROGRAM MEMORY
The program memory consists of varies sizes of ROM.
These bytes may hold program instructions or constant data
(data tables for the LAID instruction, jump vectors for the JID
instruction, and interrupt vectors for the VIS instruction). The
program memory is addressed by the 15-bit program
counter (PC). All interrupts in the device vector to program
memory location 0FF Hex. The contents of the program
memory read 00 Hex in the erased state. Program execution
starts at location 0 after RESET.
5.3 DATA MEMORY
The data memory address space includes the on-chip RAM
and data registers, the I/O registers (Configuration, Data and
Pin), the control registers, the MICROWIRE/PLUS SIO shift
register, and the various registers, and counters associated
with the timers (with the exception of the IDLE timer). Data
memory is addressed directly by the instruction or indirectly
by the B, X and SP pointers.
The data memory consists of 256 or 512 bytes of RAM. Sixteen bytes of RAM are mapped as “registers” at addresses
0F0 to 0FE Hex. These registers can be loaded immediately,
and also decremented and tested with the DRSZ (decrement
register and skip if zero) instruction. The memory pointer
registers X, SP and B are memory mapped into this space at
address locations 0FC to 0FE Hex respectively, with the
other registers (except 0FF) being available for general usage.
The instruction set permits any bit in memory to be set, reset
or tested. All I/O and registers (except A and PC) are
) cycle time.
C
www.national.com12
5.0 Functional Description (Continued)
memory mapped; therefore, I/O bits and register bits can be
directly and individually set, reset and tested. The accumulator (A) bits can also be directly and individually tested.
Note: RAM contents are undefined upon power-up.
5.4 DATA MEMORY SEGMENT RAM EXTENSION
Data memory address 0FF is used as a memory mapped location for the Data Segment Address Register (S).
The data store memory is either addressed directly by a
single byte address within the instruction, or indirectly relative to the reference of the B, X, or SP pointers (each contains a single-byte address). This single-byte address allows
an addressing range of 256 locations from 00 to FF hex. The
upper bit of this single-byte address divides the data store
memory into two separate sections as outlined previously.
With the exception of the RAM register memory from address locations 00F0 to 00FF, all RAM memory is memory
mapped with the upper bit of the single-byte address being
equal to zero. This allows the upper bit of the single-byte address to determine whether or not the base address range
(from 0000 to 00FF) is extended. If this upper bit equals one
(representing address range 0080 to 00FF), then address
extension does not take place. Alternatively, if this upper bit
equals zero, then the data segment extension register S is
used to extend the base address range (from 0000 to 007F)
from XX00 to XX7F, where XX represents the 8 bits from the
S register. Thus the 128-byte data segment extensions are
located from addresses 0100 to 017F for data segment 1,
0200 to 027F for data segment 2, etc., up to FF00 to FF7F
for data segment 255. The base address range from 0000 to
007F represents data segment 0.
Figure 8
illustrates how the S register data memory extension is used in extending the lower half of the base address
range (00 to 7F hex) into 256 data segments of 128 bytes
each, with a total addressing range of 32 kbytes from XX00
to XX7F. This organization allows a total of 256 data segments of 128 bytes each with an additional upper base segment of 128 bytes. Furthermore, all addressing modes are
available for all data segments. The S register must be
changed under program control to move from one data segment (128 bytes) to another. However, the upper base segment (containing the 16 memory registers, I/O registers,
control registers, etc.) is always available regardless of the
contents of the S register, since the upper base segment
(address range 0080 to 00FF) is independent of data segment extension.
FIGURE 8. RAM Organization
The instructions that utilize the stack pointer (SP) always reference the stack as part of the base segment (Segment 0),
regardless of the contents of the S register. The S register is
not changed by these instructions. Consequently, the stack
(used with subroutine linkage and interrupts) is always located in the base segment. The stack pointer will be initialized to point at data memory location 006F as a result of reset.
The 128 bytes of RAM contained in the base segment are
split between the lower and upper base segments. The first
112bytes of RAM are resident from address 0000 to 006F in
the lower base segment, while the remaining 16 bytes of
DS101116-45
RAM represent the 16 data memory registers located at addresses 00F0 to 00FF of the upper base segment. No RAM
is located at the upper sixteen addresses (0070 to 007F) of
the lower base segment.
Additional RAM beyond these initial 128 bytes, however, will
always be memory mapped in groups of 128 bytes (or less)
at the data segment address extensions (XX00 to XX7F) of
the lower base segment. The additional 384 bytes of RAM in
this device are memory mapped at address locations 0100
to 017F, 0200 to 027F and 0300 to 037F hex.
www.national.com13
5.0 Functional Description (Continued)
Memory address ranges 0200 to 027F and 0300 to 037F are
unavailable on the COP8FGx5 and, if read, will return underfined data.
5.5 ECON (CONFIGURATION) REGISTER
For compatibility with COP8FGx7 devices, mask options are
defined by an ECON Configuration Register which is programmed at the same time as the program code. Therefore,
the register is programmed at the same time as the program
memory.
The format of the ECON register is as follows:
Bit 7 Bit 6Bit 5Bit 4 Bit 3Bit 2Bit 1Bit 0
XPOR SECURITY CKI 2 CKI 1 WATCHF-PortHALT
DOG
Bit 7= xThis is for factory test. The polarity is “Don’t
Care.”
Bit 6= 1Power-on reset enabled.
= 0Power-on reset disabled.
Bit 5= 1Security enabled.
Bits 4,3=0,0 External CKI option selected. G7 is avail-
able as a HALT restart and/or general purpose input. CKI is clock input.
= 0, 1 R/C oscillator option selected. G7 is avail-
able as a HALT restart and/or general purpose input. CKI clock input. Internal R/C
components are supplied for maximum R/C
frequency.
= 1, 0 Crystal oscillator with on-chip crystal bias
resistor disabled. G7 (CKO) is the clock
generator output to crystal/resonator.
= 1, 1 Crystal oscillator with on-chip crystal bias
resistor enabled. G7 (CKO) is the clock
generator output to crystal/resonator.
Bit 2= 1WATCHDOG feature disabled. G1 is a gen-
eral purpose I/O.
= 0WATCHDOG feature enabled. G1 pin is
WATCHDOG output with weak pullup.
Bit 1= 1Force port I compatibility. Disable port F
outputs and pull-ups. This is intended for
compatibility with existing code and Mask
ROMMed devices only. This bit should be
programmed to 0 for all other applications.
= 0Enable full port F capability.
Bit 0= 1HALT mode disabled.
= 0HALT mode enabled.
5.6 USER STORAGE SPACE IN EPROM
The ECON register is outside of the normal address range of
the ROM and can not be accessed by the executing software.
The COP8 assembler defines a special ROM section type,
CONF, into which the ECON may be coded. Both ECON and
User Data are programmed automatically by programmers
that are certified by National.
The following examples illustrate the declaration of ECON
and the User information.
Syntax:
[label:] .sectecon, conf
.dbvalue ;1 byte,
;configures options
.db<user information>
.endsect; up to 8 bytes
Example: The following sets a value in the ECON register
and User Identification for a COP8FGR728M7. The ECON
bit values shown select options: Power-on enabled, Security
disabled, Crystal oscillator with on-chip bias disabled,
WATCHDOG enabled and HALT mode enabled.
.sect econ, conf
.db0x55;por, xtal, wd, halt
.db'my v1.00' ;user data declaration
.endsect
5.7 RESET
The devices are initialized when the RESET pin is pulled low
or the On-chip Power-On Reset is enabled.
DS101116-13
FIGURE 9. Reset Logic
The following occurs upon initialization:
Port L: TRI-STATE (High Impedance Input)
Port C: TRI-STATE (High Impedance Input)
Port G: TRI-STATE (High Impedance Input)
Port F: TRI-STATE (High Impedance Input)
Port D: HIGH
PC: CLEARED to 0000
PSW, CNTRL and ICNTRL registers: CLEARED
SIOR:
UNAFFECTED after RESET with power already applied
RANDOM after RESET at power-on
T2CNTRL: CLEARED
T3CNTRL: CLEARED
Accumulator, Timer 1, Timer 2 and Timer 3:
RANDOM after RESET with crystal clock option
(power already applied)
UNAFFECTED after RESET with R/C clock option
(power already applied)
RANDOM after RESET at power-on
WKEN, WKEDG: CLEARED
WKPND: RANDOM
SP (Stack Pointer):
Initialized to RAM address 06F Hex
B and X Pointers:
UNAFFECTED after RESET with power already applied
RANDOM after RESET at power-on
S Register: CLEARED
www.national.com14
5.0 Functional Description (Continued)
RAM:
UNAFFECTED after RESET with power already applied
RANDOM after RESET at power-on
USART:
PSR, ENU, ENUR, ENUI: Cleared except the TBMT bit
which is set to one.
COMPARATORS:
CMPSL; CLEARED
WATCHDOG (if enabled):
The device comes out of reset with both the WATCHDOG logic and the Clock Monitor detector armed, with the
WATCHDOG service window bits set and the Clock Monitor
bit set. The WATCHDOG and Clock Monitor circuits are inhibited during reset. The WATCHDOG service window bits
being initialized high default to the maximum WATCHDOG
service window of 64k t
being initialized high will cause a Clock Monitor error following reset if the clock has not reached the minimum specified
frequency at the termination of reset. A Clock Monitor error
will cause an active low error output on pin G1. This error
output will continue until 16 t
the clock frequency reaching the minimum specified value,
at which time the G1 output will go high.
5.7.1 External Reset
The RESET input when pulled low initializes the device. The
RESET pin must be held low for a minimum of one instruction cycle to guarantee a valid reset. During Power-Up initialization, the user must ensure that the RESET pin is held low
until the device is within the specified VCCvoltage. An R/C
circuit on the RESET pin with a delay 5 times (5x) greater
than the power supply rise time or 15 µs whichever is
greater,is recommended. Reset should also be wide enough
to ensure crystal start-up upon Power-Up.
RESET may also be used to cause an exit from the HALT
mode.
A recommended reset circuit for this device is shown in
ure 10
.
clock cycles. The Clock Monitor bit
C
–32 tCclock cycles following
C
Fig-
Under no circumstances should the RESET pin be allowed
to float. If the on-chip Power-On Reset feature is being used,
RESET pin should be connected directly to V
of the power-on reset detector will always preset the Idle
timer to 0FFF(4096 t
generated.
). At this time, the internal reset will be
C
. The output
CC
If the Power-On Reset feature is enabled, the internal reset
will not be turned off until the Idle timer underflows.The internal reset will perform the same functions as external reset.
The user is responsible for ensuring that V
mum level for the operating frequency within the 4096 t
ter the underflow, the logic is designed such that no additional internal resets occur as long as V
2.0V.
is at the mini-
CC
remains above
CC
C
. Af-
The contents of data registers and RAM are unknown following the on-chip reset.
RC>5x power supply rise time or 15 µs, whichever is greater.
DS101116-14
FIGURE 10. Reset Circuit Using External Reset
5.7.2 On-Chip Power-On Reset
The on-chip reset circuit is selected by a bit in the ECON register. When enabled, the device generates an internal reset
rises to a voltage level above 2.0V. The on-chip reset
as V
CC
circuitry is able to detect both fast and slow rise times on V
(VCCrise time between 10 ns and 50 ms).To guarantee an
on-chip power-on-reset, V
the start voltage specified in the DC characteristics.Also, if
V
be lowered to the start voltage before powering back up
CC
to the operating range. If this is not possible, it is recom-
must start at a voltage less than
CC
CC
mended that external reset be used.
DS101116-15
FIGURE 11. Reset Timing (Power-On Reset Enabled)
with V
Tied to RESET
CC
DS101116-16
FIGURE 12. Reset Circuit Using Power-On Reset
www.national.com15
5.0 Functional Description (Continued)
5.8 OSCILLATOR CIRCUITS
There are four clock oscillator options available: Crystal Oscillator with or without on-chip bias resistor, R/C Oscillator
with on-chip resistor and capacitor, and External Oscillator.
The oscillator feature is selected by programming the ECON
register, which is summarized in
TABLE 1. Oscillator Option
ECON4 ECON3Oscillator Option
00External Oscillator
10Crystal Oscillator without Bias Resistor
01R/C Oscillator
11Crystal Oscillator with Bias Resistor
5.8.1 Crystal Oscillator
The crystal Oscillator mode can be selected by programming
ECON Bit 4 to 1. CKI is the clock input while G7/CKO is the
clock generator output to the crystal. An on-chip bias resistor
connected between CKI and CKO can be enabled by programming ECON Bit 3 to 1 with the crystal oscillator option
selection. The value of the resistor is in the range of 0.5M to
2M (typically 1.0M).
Table2
quired for various standard crystal values. Resistor R2 is
only used when the on-chip bias resistor is disabled.
13
shows the crystal oscillator connection diagram.
TABLE 2. Crystal Oscillator Configuration,
T
= 25˚C, VCC=5V
A
R1 (kΩ)R2(MΩ)C1 (pF)C2 (pF)
01181815
01202010
0125254
5.61100100–1560.455
Table 1
.
shows the component values re-
Figure
CKI Freq.
(MHz)
5.8.2 External Oscillator
The External Oscillator mode can be selected by programming ECON Bit 3 to 0 and ECON Bit 4 to 0. CKI can be
driven by an external clock signal provided it meets the
specified duty cycle, rise and fall times, and input levels. G7/
CKO is available as a general purpose input G7 and/or Halt
control.
Figure 14
shows the external oscillator connection
diagram.
5.8.3 R/C Oscillator
The R/C Oscillator mode can be selected by programming
ECON Bit 3 to 1 and ECON Bit 4 to 0. In R/C oscillation
mode, CKI is left floating, while G7/CKO is available as a
general purpose input G7 and/or HALTcontrol. The R/C controlled oscillator has on-chip resistor and capacitor for maximum R/C oscillator frequency operation. The maximum frequency is 5 MHz
±
35%for VCCbetween 4.5V to 5.5V and
temperature range of −40˚C to +85˚C. For max frequency
operation, the CKI pin should be left floating. For lower frequencies, an external capacitor should be connected between CKI and either V
cillator to external noise can be improved by connecting one
half the external capacitance to V
PC board trace length on the CKI pin should be kept as short
as possible.
Table 3
function of external capacitance on the CKI pin.
or GND. Immunity of the R/C os-
CC
and one half to GND.
CC
shows the oscillator frequency as a
Figure 15
shows the R/C oscillator configuration.
TABLE 3. R/C Oscillator Configuration,
−40˚C to +85˚C, V
OSC Freq. Variation of
External
Capacitor (pF)*
R/C OSC Freq
CC
(MHz)
= 4.5V to 5.5V,
±
%
35
Instr. Cycle
(µs)
052.0
942.5
5225.0
125110
610032 kHz312.5
* Assumes 3-5 pF board capacitance.
With On-Chip Bias Resistor
DS101116-17
FIGURE 13. Crystal Oscillator
www.national.com16
Without On-Chip Bias Resistor
DS101116-18
5.0 Functional Description (Continued)
FIGURE 14. External Oscillator
DS101116-19
For operation at lower than maximum R/C oscillator frequency.
DS101116-20
For operation at maximum R/C oscillator frequency.
DS101116-21
FIGURE 15. R/C Oscillator
www.national.com17
5.0 Functional Description (Continued)
5.9 CONTROL REGISTERS
CNTRL Register (Address X'00EE)
T1C3 T1C2 T1C1 T1C0 MSEL IEDGSL1SL0
Bit 7Bit 0
The Timer1 (T1) and MICROWIRE/PLUS control register
contains the following bits:
T1C3Timer T1 mode control bit
T1C2Timer T1 mode control bit
T1C1Timer T1 mode control bit
T1C0Timer T1 Start/Stop control in timer
modes 1 and 2, T1 Underflow Interrupt
Pending Flag in timer mode 3
MSELSelects G5 and G4 as MICROWIRE/PLUS
signals SK and SO respectively
IEDGExternal interrupt edge polarity select
(0 = Rising edge, 1 = Falling edge)
SL1 & SL0 Select the MICROWIRE/PLUS clock divide
by (00 = 2, 01 = 4, 1x = 8)
PSW Register (Address X'00EF)
HC C T1PNDA T1ENA EXPND BUSY EXEN GIE
Bit 7Bit 0
The PSW register contains the following select bits:
HCHalf Carry Flag
CCarry Flag
T1PNDA Timer T1 Interrupt Pending Flag (Autoreload
RA in mode 1, T1 Underflow in Mode 2, T1A
capture edge in mode 3)
T1ENATimer T1 Interrupt Enable for Timer Underflow
The Half-Carry flag is also affected by all the instructions that
affect the Carry flag. The SC (Set Carry) and R/C (Reset
Carry) instructions will respectively set or clear both the carry
flags. In addition to the SC and R/C instructions, ADC,
SUBC, RRC and RLC instructions affect the Carry and Half
Carry flags.
ICNTRL Register (Address X'00E8)
Reserved LPEN T0PND T0EN µWPND µWEN T1PNDB T1ENB
Bit 7Bit0
The ICNTRL register contains the following bits:
Reserved This bit is reserved and must be zero
LPENL Port Interrupt Enable (Multi-Input Wakeup/
The T3CNTRL control register contains the following bits:
T3C3Timer T3 mode control bit
T3C2Timer T3 mode control bit
T3C1Timer T3 mode control bit
T3C0Timer T3 Start/Stop control in timer
modes 1 and 2, T3 Underflow Interrupt Pending Flag in timer mode 3
T3PNDA Timer T3 Interrupt Pending Flag (Autoreload
RA in mode 1, T3 Underflow in mode 2, T3A
capture edge in mode 3)
T3ENATimer T3 Interrupt Enable for Timer Underflow
or T3A Input capture edge
T3PNDB Timer T3 Interrupt Pending Flag for T3B cap-
ture edge
T3ENBTimer T3 Interrupt Enable for Timer Underflow
or T3B Input capture edge
6.0 Timers
Each device contains a very versatile set of timers (T0, T1,
T2 and T3). Timer T1, T2 and T3 and associated autoreload/
capture registers power up containing random data.
6.1 TIMER T0 (IDLE TIMER)
Each device supports applications that require maintaining
real time and low power with the IDLE mode. This IDLE
mode support is furnished by the IDLE timer T0. The Timer
T0 runs continuously at the fixed rate of the instruction cycle
clock, t
. The user cannot read or write to the IDLE TimerT0,
C
which is a count down timer.
The Timer T0 supports the following functions:
Exit out of the Idle Mode (See Idle Mode description)
•
WATCHDOG logic (See WATCHDOG description)
•
Start up delay out of the HALT mode
•
www.national.com18
6.0 Timers (Continued)
Timing the width of the internal power-on-reset
•
The IDLE Timer T0 can generate an interrupt when the
twelfth bit toggles. This toggle is latched into the T0PND
pending flag, and will occur every 2.731 ms at the maximum
clock frequency (t
interrupt from the twelfth bit of Timer T0 to be enabled or disabled. Setting T0EN will enable the interrupt, while resetting
it will disable the interrupt.
6.2 TIMER T1, TIMER T2 and TIMER T3
Each device have a set of three powerful timer/counter
blocks, T1, T2 and T3. Since T1, T2, and T3 are identical, all
comments are equally applicable to any of the three timer
blocks which will be referred to as Tx.
Each timer block consists of a 16-bit timer, Tx, and two supporting 16-bit autoreload/capture registers, RxA and RxB.
Each timer block has two pins associated with it, TxA and
TxB. The pin TxA supports I/O required by the timer block,
while the pin TxB is an input to the timer block. The timer
block has three operating modes: Processor Independent
PWM mode, External Event Counter mode, and Input Capture mode.
The control bits TxC3, TxC2, and TxC1 allow selection of the
different modes of operation.
6.2.1 Mode 1. Processor Independent PWM Mode
One of the timer’s operating modes is the Processor Independent PWM mode. In this mode, the timer generates a
“Processor Independent” PWM signal because once the
timer is setup, no more action is required from the CPU
which translates to less software overhead and greater
throughput. The user software services the timer block only
when the PWM parameters require updating. This capability
is provided by the fact that the timer has two separate 16-bit
reload registers. One of the reload registers contains the
“ON” timer while the other holds the “OFF” time. By contrast,
a microcontroller that has only a single reload register requires an additional software to update the reload value (alternate between the on-time/off-time).
The timer can generate the PWM output with the width and
duty cycle controlled by the values stored in the reload registers. The reload registers control the countdown values
= 0.67 µs).A control flag T0EN allows the
C
and the reload values are automatically written into the timer
when it counts down through 0, generating interrupt on each
reload. Under software control and with minimal overhead,
the PMW outputs are useful in controlling motors, triacs, the
intensity of displays, and in providing inputs for data acquisition and sine wave generators.
In this mode, the timer Tx counts down at a fixed rate of t
Upon every underflow the timer is alternately reloaded with
the contents of supporting registers, RxA and RxB. The very
first underflow of the timer causes the timer to reload from
the register RxA. Subsequent underflows cause the timer to
be reloaded from the registers alternately beginning with the
register RxB.
Figure 16
shows a block diagram of the timer in PWM mode.
The underflows can be programmed to toggle the TxA output
pin. The underflows can also be programmed to generate interrupts.
Underflows from the timer are alternately latched into two
pending flags, TxPNDA and TxPNDB. The user must reset
these pending flags under software control. Two control enable flags, TxENA and TxENB, allow the interrupts from the
timer underflow to be enabled or disabled. Setting the timer
enable flag TxENA will cause an interrupt when a timer underflow causes the RxAregister to be reloaded into the timer.
Setting the timer enable flag TxENB will cause an interrupt
when a timer underflow causes the RxB register to be reloaded into the timer. Resetting the timer enable flags will
disable the associated interrupts.
Either or both of the timer underflow interrupts may be enabled. This gives the user the flexibility of interrupting once
per PWM period on either the rising or falling edge of the
PWM output. Alternatively, the user may choose to interrupt
on both edges of the PWM output.
6.2.2 Mode 2. External Event Counter Mode
This mode is quite similar to the processor independent
PWM mode described above. The main difference is that the
timer,Tx, is clocked by the input signal from the TxA pin. The
Tx timer control bits, TxC3,TxC2 and TxC1 allow the timer to
be clocked either on a positive or negative edge from the
TxA pin. Underflows from the timer are latched into the TxPNDA pending flag. Setting the TxENA control flag will cause
an interrupt when the timer underflows.
.
C
FIGURE 16. Timer in PWM Mode
DS101116-46
www.national.com19
6.0 Timers (Continued)
In this mode the input pin TxB can be used as an independent positive edge sensitive interrupt input if the TxENB control flag is set. The occurrence of a positive edge on the TxB
input pin is latched into the TxPNDB flag.
Figure 17
Event Counter mode.
Note: The PWM output is not available in this mode since the TxA pin is being
6.2.3 Mode 3. Input Capture Mode
Each device can precisely measure external frequencies or
time external events by placing the timer block, Tx, in the input capture mode. In this mode, the reload registers serve as
independent capture registers, capturing the contents of the
timer when an external event occurs (transition on the timer
input pin). The capture registers can be read while maintaining count, a feature that lets the user measure elapsed time
and time between events. By saving the timer value when
shows a block diagram of the timer in External
used as the counter input clock.
DS101116-47
FIGURE 17. Timer in External Event Counter Mode
the external event occurs, the time of the external event is
recorded. Most microcontrollers have a latency time because they cannot determine the timer value when the external event occurs. The capture register eliminates the latency
time, thereby allowing the applications program to retrieve
the timer value stored in the capture register.
In this mode, the timer Tx is constantly running at the fixed t
rate. The two registers, RxA and RxB, act as capture registers. Each register acts in conjunction with a pin. The register
RxAacts in conjunction with the TxA pin and the register RxB
acts in conjunction with the TxB pin.
The timer value gets copied over into the register when a
trigger event occurs on its corresponding pin. Control bits,
TxC3, TxC2 and TxC1, allow the trigger events to be specified either as a positive or a negative edge. The trigger condition for each input pin can be specified independently.
The trigger conditions can also be programmed to generate
interrupts. The occurrence of the specified trigger condition
on the TxA and TxB pins will be respectively latched into the
pending flags, TxPNDA and TxPNDB. The control flag TxENA allows the interrupt on TxA to be either enabled or disabled. Setting the TxENAflag enables interrupts to be generated when the selected trigger condition occurs on the TxA
pin. Similarly, the flag TxENB controls the interrupts from the
TxB pin.
Underflows from the timer can also be programmed to generate interrupts. Underflows are latched into the timer TxC0
pending flag (the TxC0 control bit serves as the timer underflow interrupt pending flag in the Input Capture mode). Consequently, the TxC0 control bit should be reset when entering the Input Capture mode. The timer underflow interrupt is
enabled with the TxENA control flag. When a TxA interrupt
occurs in the Input Capture mode, the user must check both
the TxPNDA and TxC0 pending flags in order to determine
whether a TxA input capture or a timer underflow (or both)
caused the interrupt.
Figure 18
shows a block diagram of the timer T1 in Input
Capture mode. Timer T2 and T3 are identical to T1.
C
FIGURE 18. Timer in Input Capture Mode
www.national.com20
DS101116-48
6.0 Timers (Continued)
6.3 TIMER CONTROL FLAGS
TxPNDA Timer Interrupt Pending Flag
TxENATimer Interrupt Enable Flag
The control bits and their functions are summarized below.
TxC3Timer mode control
TxC2Timer mode control
TxC1Timer mode control
TxPNDB Timer Interrupt Pending Flag
TxENBTimer Interrupt Enable Flag
TxC0Timer Start/Stop control in Modes 1 and 2 (Pro-
cessor Independent PWM and External Event
Counter), where 1 = Start, 0 = Stop
Timer Underflow Interrupt Pending Flag in
Mode 3 (Input Capture)
The timer mode control bits (TxC3, TxC2 and TxC1) are detailed below:
TxA Neg. EdgeEdge or TimerEdge
TxB Neg. EdgeUnderflow
111Captures:Neg. TxANeg. TxBt
TxA Neg. EdgeEdge or TimerEdge
TxB Neg. EdgeUnderflow
Interrupt A
Source
Interrupt B
Source
Autoreload RAAutoreload RB
Timer
Pos. TxB EdgePos. TxA
Underflow
Timer
Pos. TxB EdgePos. TxA
Underflow
Timer
Counts On
C
t
C
Edge
Edge
C
C
C
C
www.national.com21
7.0 Power Saving Features
Today, the proliferation of battery-operated based applications has placed new demands on designers to drive power
consumption down. Battery-operated systems are not the
only type of applications demanding low power. The power
budget constraints are also imposed on those consumer/
industrial applications where well regulated and expensive
power supply costs cannot be tolerated. Such applications
rely on low cost and low power supply voltage derived directly from the “mains” by using voltage rectifier and passive
components. Low power is demanded even in automotive
applications, due to increased vehicle electronics content.
This is required to ease the burden from the car battery.Low
power 8-bit microcontrollers supply the smarts to control
battery-operated, consumer/industrial, and automotive applications.
Each device offers system designers a variety of low-power
consumption features that enable them to meet the demanding requirements of today’s increasing range of low-power
applications. These features include low voltage operation,
low current drain, and power saving features such as HALT,
IDLE, and Multi-Input wakeup (MIWU).
Each device offers the user two power save modes of operation: HALT and IDLE. In the HALT mode, all microcontroller
activities are stopped. In the IDLE mode, the on-board oscillator circuitry and timer T0 are active but all other microcontroller activities are stopped. In either mode, all on-board
RAM, registers, I/O states, and timers (with the exception of
T0) are unaltered.
Clock Monitor, if enabled, can be active in both modes.
7.1 HALT MODE
Each device can be placed in the HALTmode by writing a “1”
to the HALT flag (G7 data bit). All microcontroller activities,
including the clock and timers, are stopped. The WATCHDOG logic on the devices are disabled during the HALT
mode. However, the clock monitor circuitry, if enabled, remains active and will cause the WATCHDOG output pin
(WDOUT) to go low. If the HALT mode is used and the user
does not want to activate the WDOUT pin, the Clock Monitor
should be disabled after the devices come out of reset (resetting the Clock Monitor control bit with the first write to the
WDSVR register). In the HALT mode, the power requirements of the devices are minimal and the applied voltage
(V
) may be decreased to Vr(Vr= 2.0V) without altering the
CC
state of the machine.
Each device supports three different ways of exiting the
HALT mode. The first method of exiting the HALT mode is
with the Multi-Input Wakeup feature on Port L. The second
method is with a low to high transition on the CKO (G7) pin.
This method precludes the use of the crystal clock configuration (since CKO becomes a dedicated output), and so may
only be used with an R/C clock configuration. The third
method of exiting the HALT mode is by pulling the RESET
pin low.
On wakeup from G7 or Port L, the devices resume execution
from the HALT point. On wakeup from RESET execution will
resume from location PC=0 and all RESET conditions apply.
If a crystal or ceramic resonator may be selected as the oscillator, the Wakeup signal is not allowed to start the chip
running immediately since crystal oscillators and ceramic
resonators have a delayed start up time to reach full amplitude and frequency stability. The IDLE timer is used to generate a fixed delay to ensure that the oscillator has indeed
stabilized before allowing instruction execution. In this case,
upon detecting a valid Wakeup signal, only the oscillator circuitry is enabled. The IDLE timer is loaded with a value of
256 and is clocked with the t
clock is derived by dividing the oscillator clock down by a fac-
instruction cycle clock. The t
C
tor of 9. The Schmitt trigger following the CKI inverter on the
chip ensures that the IDLE timer is clocked only when the oscillator has a sufficiently large amplitude to meet the Schmitt
trigger specifications. This Schmitt trigger is not part of the
oscillator closed loop. The start-up time-out from the IDLE
timer enables the clock signals to be routed to the rest of the
chip.
If an R/C clock option is being used, the fixed delay is introduced optionally. A control bit, CLKDLY, mapped as configuration bit G7, controls whether the delay is to be introduced
or not. The delay is included if CLKDLY is set, and excluded
if CLKDLY is reset. The CLKDLY bit is cleared on reset.
Each device has two options associated with the HALT
mode. The first option enables the HALTmode feature, while
the second option disables the HALTmode selected through
bit 0 of the ECON register. With the HALT mode enable option, the device will enter and exit the HALT mode as described above. With the HALTdisable option, the device cannot be placed in the HALT mode (writing a “1” to the HALT
flag will have no effect, the HALT flag will remain “0”).
The WATCHDOG detector circuit is inhibited during the
HALTmode. However, the clock monitor circuit if enabled remains active during HALT mode in order to ensure a clock
monitor error if the device inadvertently enters the HALT
mode as a result of a runaway program or power glitch.
If the device is placed in the HALT mode, with the R/C oscillator selected, the clock input pin (CKI) is forced to a logic
high internally. With the crystal or external oscillator the CKI
pin is TRI-STATE.
It is recommended that the user not halt the device by merely
stopping the clock in external oscillator mode. If this method
is used, there is a possibility of greater than specified HALT
current.
If the user wishes to stop an external clock, it is recommended that the CPU be halted by setting the Halt flag first
and the clock be stopped only after the CPU has halted.
C
www.national.com22
7.0 Power Saving Features (Continued)
FIGURE 19. Wakeup from HALT
7.2 IDLE MODE
The device is placed in the IDLE mode by writing a “1” to the
IDLE flag (G6 data bit). In this mode, all activities, except the
associated on-board oscillator circuitry and the IDLE Timer
T0, are stopped.
As with the HALT mode, the device can be returned to normal operation with a reset, or with a Multi-Input Wakeup from
the L Port. Alternately, the microcontroller resumes normal
operation from the IDLE mode when the twelfth bit (representing 4.096 ms at internal clock frequency of 10 MHz, t
1 µs) of the IDLE Timer toggles.
This toggle condition of the twelfth bit of the IDLE TimerT0 is
latched into the T0PND pending flag.
The user has the option of being interrupted with a transition
on the twelfth bit of the IDLE Timer T0. The interrupt can be
enabled or disabled via the T0EN control bit. Setting the
T0EN flag enables the interrupt and vice versa.
C
DS101116-25
The user can enter the IDLE mode with the Timer T0 interrupt enabled. In this case, when the T0PND bit gets set, the
device will first execute the Timer T0 interrupt service routine
and then return to the instruction following the “Enter Idle
Mode” instruction.
Alternatively, the user can enter the IDLE mode with the
IDLE TimerT0 interrupt disabled. In this case, the device will
resume normal operation with the instruction immediately
following the “Enter IDLE Mode” instruction.
Note: It is necessary to program two NOP instructions following both the set
=
HALT mode and set IDLE mode instructions. These NOP instructions
are necessary to allow clock resynchronization following the HALT or
IDLE modes.
FIGURE 20. Wakeup from IDLE
DS101116-26
www.national.com23
7.0 Power Saving Features (Continued)
7.3 MULTI-INPUT WAKEUP
The Multi-Input Wakeup feature is used to return (wakeup)
the device from either the HALT or IDLE modes. Alternately
Multi-Input Wakeup/Interrupt feature may also be used to
generate up to 8 edge selectable external interrupts.
Figure 21
The Multi-Input Wakeup feature utilizes the L Port. The user
selects which particular L port bit (or combination of L Port
bits) will cause the device to exit the HALT or IDLE modes.
The selection is done through the register WKEN. The register WKEN is an 8-bit read/write register, which contains a
control bit for every L port bit. Setting a particular WKEN bit
enables a Wakeup from the associated L port pin.
The user can select whether the trigger condition on the selected L Port pin is going to be either a positive edge (low to
high transition) or a negative edge (high to low transition).
This selection is made via the register WKEDG, which is an
8-bit control register with a bit assigned to each L Port pin.
Setting the control bit will select the trigger condition to be a
negative edge on that particular L Port pin. Resetting the bit
selects the trigger condition to be a positive edge. Changing
an edge select entails several steps in order to avoid a
Wakeup condition as a result of the edge change. First, the
associated WKEN bit should be reset, followed by the edge
select change in WKEDG. Next, the associated WKPND bit
should be cleared, followed by the associated WKEN bit being re-enabled.
An example may serve to clarify this procedure. Suppose we
wish to change the edge select from positive (low going high)
shows the Multi-Input Wakeup logic.
to negative (high going low) for L Port bit 5, where bit 5 has
previously been enabled for an input interrupt. The program
would be as follows:
If the L port bits have been used as outputs and then
changed to inputs with Multi-Input Wakeup/Interrupt,a safety
procedure should also be followed to avoid wakeup conditions. After the selected L port bits have been changed from
output to input but before the associated WKEN bits are enabled, the associated edge select bits in WKEDG should be
set or reset for the desired edge selects, followed by the associated WKPND bits being cleared.
This same procedure should be used following reset, since
the L port inputs are left floating as a result of reset.
The occurrence of the selected trigger condition for MultiInput Wakeup is latched into a pending register called WKPND. The respective bits of the WKPND register will be set
on the occurrence of the selected trigger edge on the corresponding Port L pin. The user has the responsibility of clearing these pending flags. Since WKPND is a pending register
for the occurrence of selected wakeup conditions, the device
will not enter the HALT mode if any Wakeup bit is both enabled and pending. Consequently, the user must clear the
pending flags before attempting to enter the HALT mode.
WKEN and WKEDG are all read/write registers, and are
cleared at reset. WKPND register contains random value after reset.
FIGURE 21. Multi-Input Wake Up Logic
www.national.com24
DS101116-27
8.0 USART
Each device contains a full-duplex software programmable
USART. The USART (
register, a receive shift register and seven addressable registers, as follows: a transmit buffer register (TBUF), a receiver buffer register (RBUF), a USART control and status
register (ENU), a USART receive control and status register
(ENUR), a USART interrupt and clock source register
(ENUI), a prescaler select register (PSR) and baud (BAUD)
register.The ENU register contains flags for transmit and receive functions; this register also determines the length of
the data frame (7, 8 or 9 bits), the value of the ninth bit in
transmission, and parity selection bits. The ENUR register
flags framing, data overrun and parity errors while the USART is receiving.
Figure 22
) consists of a transmit shift
Other functions of the ENUR register include saving the
ninth bit received in the data frame, enabling or disabling the
USART’s attention mode of operation and providing additional receiver/transmitter status information via RCVG and
XMTG bits. The determination of an internal or external clock
source is done by the ENUI register, as well as selecting the
number of stop bits and enabling or disabling transmit and
receive interrupts. A control flag in this register can also select the USART mode of operation: asynchronous or
synchronous.
FIGURE 22. USART Block Diagram
DS101116-39
www.national.com25
8.0 USART (Continued)
8.1 USART CONTROL AND STATUS REGISTERS
The operation of the USART is programmed through three
registers: ENU, ENUR and ENUI.
8.2 DESCRIPTION OF USART REGISTER BITS
ENU-USART Control and Status Register (Address at 0BA)
PEN PSEL1 XBIT9/ CHL1 CHL0ERR RBFL TBMT
PSEL0
Bit 7Bit 0
PEN: This bit enables/disables Parity (7- and 8-bit modes
only). Read/Write, cleared on reset.
the USART is operating with nine data bits per frame. For
seven or eight data bits per frame, this bit in conjunction with
PSEL1 selects parity. Read/Write, cleared on reset.
CHL1, CHL0: These bits select the character frame format.
Parity is not included and is generated/verified by hardware.
Read/Write, cleared on reset.
format is used.
ERR: This bit is a global USART error flag which gets set if
any or a combination of the errors (DOE, FE, PE) occur.
Read only; it cannot be written by software, cleared on reset.
RBFL: This bit is set when the USART has received a complete character and has copied it into the RBUF register. It is
automatically reset when software reads the character from
RBUF. Read only; it cannot be written by software, cleared
on reset.
TBMT: This bit is set when the USART transfers a byte of
data from the TBUF register into the TSFT register for transmission. It is automatically reset when software writes into
the TBUF register. Read only, bit is set to “one” on reset; it
cannot be written by software.
ENUR-USART Receive Control and Status Register
(Address at 0BB)
DOE FE PE Reserved RBIT9 ATTN XMTG RCVG
(Note 14)
Bit 7Bit 0
Note 14: Bit is reserved for future use. User must set to zero.
DOE: Flags a Data Overrun Error. Read only, cleared on
read, cleared on reset.
DOE = 0Indicates no Data Overrun Error has been de-
tected since the last time the ENUR register
was read.
DOE = 1Indicates the occurrence of a Data Overrun Er-
ror.
FE: Flags a Framing Error. Read only, cleared on read,
cleared on reset.
FE = 0Indicates no Framing Error has been detected
since the last time the ENUR register was read.
FE = 1Indicates the occurrence of a Framing Error.
PE: Flags a Parity Error. Read only, cleared on read, cleared
on reset.
PE = 0Indicates no Parity Error has been detected since
the last time the ENUR register was read.
PE = 1Indicates the occurrence of a Parity Error.
SPARE:Reserved for future use. Read/Write, cleared on re-
set.
RBIT9: Contains the ninth data bit received when the US-
ART is operating with nine data bits per frame. Read only,
cleared on reset.
ATTN: ATTENTION Mode is enabled while this bit is set.
This bit is cleared automatically on receiving a character with
data bit nine set. Read/Write, cleared on reset.
XMTG: This bit is set to indicate that the USART is transmitting. It gets reset at the end of the last frame (end of last Stop
bit). Read only, cleared on reset.
RCVG: This bit is set high whenever a framing error occurs
and goes low when RDX goes high. Read only, cleared on
reset.
ENUI-USART Interrupt and Clock Source Register
(Address at 0BC)
STP2 STP78 ETDX SSEL XRCLK XTCLKERIETI
Bit 7Bit 0
STP2: This bit programs the number of Stop bits to be transmitted. Read/Write, cleared on reset.
STP2 = 0One Stop bit transmitted.
STP2 = 1Two Stop bits transmitted.
STP78: This bit is set to program the last Stop bit to be 7/8th
of a bit in length. Read/Write, cleared on reset.
ETDX: TDX (USART Transmit Pin) is the alternate function
assigned to Port L pin L2; it is selected by setting ETDX bit.
To simulate line break generation, software should reset
ETDX bit and output logic zero to TDX pin through Port L
data and configuration registers. Read/Write, cleared on reset.
SSEL: USART mode select. Read/Write, cleared on reset.
SSEL = 0Asynchronous Mode.
SSEL = 1Synchronous Mode.
XRCLK: This bit selects the clock source for the receiver
section. Read/Write, cleared on reset.
XRCLK = 0The clock source is selected through the
PSR and BAUD registers.
XRCLK = 1Signal on CKX (L1) pin is used as the clock.
XTCLK: This bit selects the clock source for the transmitter
section. Read/Write, cleared on reset.
XTCLK = 0The clock source is selected through the
PSR and BAUD registers.
XTCLK = 1Signal on CKX (L1) pin is used as the clock.
ERI: This bit enables/disables interrupt from the receiver
section. Read/Write, cleared on reset.
ERI = 0Interrupt from the receiver is disabled.
ERI = 1Interrupt from the receiver is enabled.
www.national.com26
8.0 USART (Continued)
ETI: This bit enables/disables interrupt from the transmitter
section. Read/Write, cleared on reset.
ETI = 0Interrupt from the transmitter is disabled.
ETI = 1Interrupt from the transmitter is enabled.
8.3 Associated I/O Pins
Data is transmitted on the TDX pin and received on the RDX
pin. TDX is the alternate function assigned to Port L pin L2;
it is selected by setting ETDX (in the ENUI register) to one.
RDX is an inherent function of Port L pin L3, requiring no
setup.
The baud rate clock for the USART can be generated onchip, or can be taken from an external source. Port L pin L1
(CKX) is the external clock I/O pin. The CKX pin can be either an input or an output, as determined by Port L Configuration and Data registers (Bit 1). As an input, it accepts a
clock signal which may be selected to drive the transmitter
and/or receiver. As an output, it presents the internal Baud
Rate Generator output.
8.4 USART Operation
The USART has two modes of operation: asynchronous
mode and synchronous mode.
8.4.1 ASYNCHRONOUS MODE
This mode is selected by resetting the SSEL (in the ENUI
register) bit to zero. The input frequency to the USART is 16
times the baud rate.
The TSFT and TBUF registers double-buffer data for transmission. While TSFT is shifting out the current character on
the TDX pin, the TBUF register may be loaded by software
with the next byte to be transmitted. When TSFT finishes
transmitting the current character the contents of TBUF are
transferred to the TSFT register and the Transmit Buffer
Empty Flag (TBMT in the ENU register) is set. The TBMT
flag is automatically reset by the USART when software
loads a new character into the TBUF register. There is also
the XMTG bit which is set to indicate that the USART is
transmitting. This bit gets reset at the end of the last frame
(end of last Stop bit). TBUF is a read/write register.
The RSFT and RBUF registers double-buffer data being received. The USART receiver continually monitors the signal
on the RDX pin for a low level to detect the beginning of a
Start bit. Upon sensing this low level, it waits for half a bit
time and samples again. If the RDX pin is still low, the receiver considers this to be a valid Start bit, and the remaining
bits in the character frame are each sampled a single time, at
the mid-bit position. Serial data input on the RDX pin is
shifted into the RSFT register. Upon receiving the complete
character, the contents of the RSFT register are copied into
the RBUF register and the Received Buffer Full Flag (RBFL)
is set. RBFL is automatically reset when software reads the
character from the RBUF register. RBUF is a read only register. There is also the RCVG bit which is set high when a
framing error occurs and goes low once RDX goes high.
TBMT, XMTG, RBFL and RCVG are read only bits.
8.4.2 SYNCHRONOUS MODE
In this mode data is transferred synchronously with the
clock. Data is transmitted on the rising edge and received on
the falling edge of the synchronous clock.
This mode is selected by setting SSEL bit in the ENUI register. The input frequency to the USART is the same as the
baud rate.
When an external clock input is selected at the CKX pin, data
transmit and receive are performed synchronously with this
clock through TDX/RDX pins.
If data transmit and receive are selected with the CKX pin as
clock output, the device generates the synchronous clock
output at the CKX pin. The internal baud rate generator is
used to produce the synchronous clock. Data transmit and
receive are performed synchronously with this clock.
8.5 FRAMING FORMATS
The USART supports several serial framing formats (
23
). The format is selected using control bits in the ENU,
ENUR and ENUI registers.
The first format (1, 1a, 1b, 1c) for data transmission (CHL0 =
1, CHL1 = 0) consists of Start bit, seven Data bits (excluding
parity) and 7/8, one or two Stop bits. In applications using
parity, the parity bit is generated and verified by hardware.
The second format (CHL0 = 0, CHL1 = 0) consists of one
Start bit, eight Data bits (excluding parity) and 7/8, one or
two Stop bits. Parity bit is generated and verified by hardware.
The third format for transmission (CHL0 = 0, CHL1 = 1) consists of one Start bit, nine Data bits and 7/8, one or two Stop
bits. This format also supports the USART “ATTENTION”
feature. When operating in this format, all eight bits of TBUF
and RBUF are used for data. The ninth data bit is transmitted
and received using two bits in the ENU and ENUR registers,
called XBIT9 and RBIT9. RBIT9 is a read only bit. Parity is
not generated or verified in this mode.
For any of the above framing formats, the last Stop bit can
be programmed to be 7/8th of a bit in length. If two Stop bits
are selected and the 7/8th bit is set (selected), the second
Stop bit will be 7/8th of a bit in length.
The parity is enabled/disabled by PEN bit located in the ENU
register. Parity is selected for 7- and 8-bit modes only. If parity is enabled (PEN = 1), the parity selection is then performed by PSEL0 and PSEL1 bits located in the ENU register.
Note that the XBIT9/PSEL0 bit located in the ENU register
serves two mutually exclusive functions. This bit programs
the ninth bit for transmission when the USART is operating
with nine data bits per frame. There is no parity selection in
this framing format. For other framing formats XBIT9 is not
needed and the bit is PSEL0 used in conjunction with PSEL1
to select parity.
The frame formats for the receiver differ from the transmitter
in the number of Stop bits required. The receiver only requires one Stop bit in a frame, regardless of the setting of the
Stop bit selection bits in the control register. Note that an implicit assumption is made for full duplex USART operation
that the framing formats are the same for the transmitter and
receiver.
Figure
www.national.com27
8.0 USART (Continued)
FIGURE 23. Framing Formats
8.6 USART INTERRUPTS
The USART is capable of generating interrupts. Interrupts
are generated on Receive Buffer Full and Transmit Buffer
Empty. Both interrupts have individual interrupt vectors. Two
bytes of program memory space are reserved for each interrupt vector. The two vectors are located at addresses 0xEC
to 0xEF Hex in the program memory space. The interrupts
can be individually enabled or disabled using Enable Transmit Interrupt (ETI) and Enable Receive Interrupt (ERI) bits in
the ENUI register.
The interrupt from the Transmitter is set pending, and remains pending, as long as both the TBMT and ETI bits are
set. To remove this interrupt, software must either clear the
ETI bit or write to the TBUF register (thus clearing the TBMT
bit).
The interrupt from the receiver is set pending, and remains
pending, as long as both the RBFL and ERI bits are set. To
remove this interrupt, software must either clear the ERI bit
or read from the RBUF register (thus clearing the RBFL bit).
8.7 Baud Clock Generation
The clock inputs to the transmitter and receiver sections of
the USART can be individually selected to come either from
an external source at the CKX pin (port L, pin L1) or from a
source selected in the PSR and BAUD registers. Internally,
www.national.com28
DS101116-40
the basic baud clock is created from the oscillator frequency
through a two-stage divider chain consisting of a 1–16 (increments of 0.5) prescaler and an 11-bit binary counter. (
ure 24
). The divide factors are specified through two read/
write registers shown in
Rate Divisor spills over into the Prescaler Select Register
(PSR). PSR is cleared upon reset.
As shown in
NO CLOCK. This condition is the USART power down mode
where the USART clock is turned off for power saving purpose. The user must also turn the USART clock off when a
different baud rate is chosen.
The correspondences between the 5-bit Prescaler Select
and Prescaler factors are shown in
ways to calculate the two divisor factors, but one particularly
effective method would be to achieve a 1.8432 MHz frequency coming out of the first stage. The 1.8432 MHz prescaler output is then used to drive the software programmable
baud rate counter to create a 16x clock for the following baud
rates: 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 3600,
4800, 7200, 9600, 19200 and 38400 (
rates may be created by using appropriate divisors. The 16x
clock is then divided by 16 to provide the rate for the serial
shift registers of the transmitter and receiver.
As an example, considering Asynchronous Mode and a CKI
clock of 4.608 MHz, the prescaler factor selected is:
4.608/1.8432 = 2.5
The 2.5 entry is available in
caler output is then used with proper Baud Rate Divisor
(
Table 4
) to obtain different baud rates. For a baud rate of
19200 e.g., the entry in
N−1=5(N−1isthevalue from
N=6(NistheBaud Rate Divisor)
Baud Rate = 1.8432 MHz/(16 x 6) = 19200
The divide by 16 is performed because in the asynchronous
mode, the input frequency to the USART is 16 times the
baud rate. The equation to calculate baud rates is given below.
The actual Baud Rate may be found from:
Where:
BR is the Baud Rate
Fc is the CKI frequency
N is the Baud Rate Divisor (
P is the Prescaler Divide Factor selected by the value in the
Prescaler Select Register (
Note: In the Synchronous Mode, the divisor 16 is replaced by two.
Example:
Asynchronous Mode:
Crystal Frequency=5MHz
Desired baud rate = 9600
Using the above equationNxPcanbecalculated first.
NxP=(5x10
Now 32.552 is divided by each Prescaler Factor (
obtain a value closest to an integer. This factor happens to
be 6.5 (P = 6.5).
N = 32.552/6.5 = 5.008 (N = 5)
The programmed value (from
Using the above values calculated for N and P:
BR=(5x10
%
error = (9615.385 − 9600)/9600 x 100 = 0.16
8.8 Effect of HALT/IDLE
The USART logic is reinitialized when either the HALT or
IDLE modes are entered. This reinitialization sets the TBMT
flag and resets all read only bits in the USART control and
status registers. Read/Write bits remain unchanged. The
Transmit Buffer (TBUF) is not affected, but the Transmit Shift
register (TSFT) bits are set to one. The receiver registers
RBUF and RSFT are not affected.
The device will exit from the HALT/IDLE modes when the
Start bit of a character is detected at the RDX (L3) pin. This
feature is obtained by using the Multi-Input Wakeup scheme
provided on the device.
Before entering the HALT or IDLE modes the user program
must select the Wakeup source to be on the RDX pin. This
selection is done by setting bit 3 of WKEN (Wakeup Enable)
register.The Wakeup trigger condition is then selected to be
high to low transition. This is done via the WKEDG register
(Bit 3 is one.)
If the device is halted and crystal oscillator is used, the
Wakeup signal will not start the chip running immediately be-
Table 5
. The 1.8432 MHz pres-
Table 4
is 5.
Table 4
BR = Fc/(16xNxP)
Table 4
).
Table 5
)
6
)/(16 x 9600) = 32.552
Table 4
) should be 4 (N − 1).
6
)/(16x5x6.5) = 9615.384
)
Table5
%
)to
cause of the finite start up time requirement of the crystal oscillator.The idle timer (T0) generates a fixed (256 t
ensure that the oscillator has indeed stabilized before allow-
) delay to
c
ing the device to execute code. The user has to consider this
delay when data transfer is expected immediately after exiting the HALT mode.
8.9 Diagnostic
Bits CHARL0 and CHARL1 in the ENU register provide a
loopback feature for diagnostic testing of the USART. When
these bits are set to one, the following occur: The receiver input pin (RDX) is internally connected to the transmitter output pin (TDX); the output of the Transmitter Shift Register is
“looped back” into the Receive Shift Register input. In this
mode, data that is transmitted is immediately received. This
feature allows the processor to verify the transmit and receive data paths of the USART.
Note that the framing format for this mode is the nine bit format; one Start bit, nine data bits, and 7/8, one or two Stop
bits. Parity is not generated or verified in this mode.
8.10 Attention Mode
The USART Receiver section supports an alternate mode of
operation, referred to as ATTENTION Mode. This mode of
operation is selected by the ATTN bit in the ENUR register.
The data format for transmission must also be selected as
having nine Data bits and either 7/8, one or two Stop bits.
The ATTENTION mode of operation is intended for use in
networking the device with other processors. Typically in
such environments the messages consists of device addresses, indicating which of several destinations should receive them, and the actual data. This Mode supports a
scheme in which addresses are flagged by having the ninth
bit of the data field set to a 1. If the ninth bit is reset to a zero
the byte is a Data byte.
While in ATTENTION mode, the USART monitors the communication flow, but ignores all characters until an address
character is received. Upon receiving an address character,
the USART signals that the character is ready by setting the
RBFL flag, which in turn interrupts the processor if USART
Receiver interrupts are enabled.The ATTNbit is also cleared
automatically at this point, so that data characters as well as
address characters are recognized. Software examines the
contents of the RBUF and responds by deciding either to accept the subsequent data stream (by leaving the ATTNbit reset) or to wait until the next address character is seen (by
setting the ATTN bit again).
Operation of the USART Transmitteris not affected by selection of this Mode. The value of the ninth bit to be transmitted
is programmed by setting XBIT9 appropriately. The value of
the ninth bit received is obtained by reading RBIT9. Since
this bit is located in ENUR register where the error flags reside, a bit operation on it will reset the error flags.
www.national.com30
9.0 Comparators
The device contains two differential comparators, each with
a pair of inputs (positive and negative) and an output. Ports
F1–F3 and F4–F6 are used for the comparators. The following is the Port F assignment:
A Comparator Select Register (CMPSL) is used to enable
the comparators, read the outputs of the comparators internally, and enable the outputs of the comparators to the pins.
Two control bits (enable and output enable) and one result
bit are associated with each comparator. The comparator result bits (CMP1RD and CMP2RD) are read only bits which
will read as zero if the associated comparator is not enabled.
The Comparator Select Register is cleared with reset, resulting in the comparators being disabled. The comparators
should also be disabled before entering either the HALT or
IDLE modes in order to save power.The configuration of the
CMPSL register is as follows:
The CMPSL register contains the following bits:
Reserved These bits are reserved and must be zero
CMP20E Selects pin I6 as comparator 2 output provided
that CMP2EN is set to enable the comparator
CMP2RD Comparator 2 result (this is a read only bit, which
will read as 0 if the comparator is not enabled)
CMP2EN Enable comparator 2
CMP10E Selects pin I3 as comparator 1 output provided
that CMPIEN is set to enable the comparator
CMP1RD Comparator 1 result (this is a read only bit, which
will read as 0 if the comparator is not enabled)
CMP1EN Enable comparator 1
Note that the two unused bits of CMPSL may be used as
software flags.
Note: For compatibility with existing code and with existing Mask ROMMed
devices the bits of the CMPSL register will take precedence over the
associated Port F configuration and data output bits.
10.0 Interrupts
10.1 INTRODUCTION
Each device supports thirteen vectored interrupts. Interrupt
sources include Timer 0, Timer 1, Timer 2, Timer 3, Port L
Wakeup, Software Trap, MICROWIRE/PLUS, and External
Input.
All interrupts force a branch to location 00FF Hex in program
memory. The VIS instruction may be used to vector to the
appropriate service routine from location 00FF Hex.
The Software trap has the highest priority while the default
VIS has the lowest priority.
Each of the 13 maskable inputs has a fixed arbitration ranking and vector.
Figure 26
shows the Interrupt Block Diagram.
FIGURE 26. Interrupt Block Diagram
DS101116-28
www.national.com31
10.0 Interrupts (Continued)
10.2 MASKABLE INTERRUPTS
All interrupts other than the Software Trap are maskable.
Each maskable interrupt has an associated enable bit and
pending flag bit. The pending bit is set to 1 when the interrupt
condition occurs. The state of the interrupt enable bit, combined with the GIE bit determines whether an active pending
flag actually triggers an interrupt. All of the maskable interrupt pending and enable bits are contained in mapped control registers, and thus can be controlled by the software.
Amaskable interrupt condition triggers an interrupt under the
following conditions:
1. The enable bit associated with that interrupt is set.
2. The GIE bit is set.
3. The device is not processing a non-maskable interrupt.
(If a non-maskable interrupt is being serviced, a
maskable interrupt must wait until that service routine is
completed.)
An interrupt is triggered only when all of these conditions are
met at the beginning of an instruction. If different maskable
interrupts meet these conditions simultaneously, the highest
priority interrupt will be serviced first, and the other pending
interrupts must wait.
Upon Reset, all pending bits, individual enable bits, and the
GIE bit are reset to zero. Thus, a maskable interrupt condition cannot trigger an interrupt until the program enables it by
setting both the GIE bit and the individual enable bit. When
enabling an interrupt, the user should consider whether or
not a previously activated (set) pending bit should be acknowledged. If, at the time an interrupt is enabled, any previous occurrences of the interrupt should be ignored, the associated pending bit must be reset to zero prior to enabling
the interrupt. Otherwise, the interrupt may be simply enabled; if the pending bit is already set, it will immediately trigger an interrupt. A maskable interrupt is active if its associated enable and pending bits are set.
An interrupt is an asychronous event which may occur before, during, or after an instruction cycle. Any interrupt which
occurs during the execution of an instruction is not acknowledged until the start of the next normally executed instruction
is to be skipped, the skip is performed before the pending interrupt is acknowledged.
At the start of interrupt acknowledgment, the following actions occur:
1. The GIE bit is automatically reset to zero, preventing any
subsequent maskable interrupt from interrupting the current service routine. This feature prevents one maskable
interrupt from interrupting another one being serviced.
2. The address of the instruction about to be executed is
pushed onto the stack.
3. The program counter (PC) is loaded with 00FF Hex,
causing a jump to that program memory location.
The device requires seven instruction cycles to perform the
actions listed above.
If the user wishes to allow nested interrupts, the interrupts
service routine may set the GIE bit to 1 by writing to the PSW
register,and thus allow other maskable interrupts to interrupt
the current service routine. If nested interrupts are allowed,
caution must be exercised. The user must write the program
in such a way as to prevent stack overflow, loss of saved
context information, and other unwanted conditions.
The interrupt service routine stored at location 00FF Hex
should use the VIS instruction to determine the cause of the
interrupt, and jump to the interrupt handling routine corresponding to the highest priority enabled and active interrupt.
Alternately, the user may choose to poll all interrupt pending
and enable bits to determine the source(s) of the interrupt. If
more than one interrupt is active, the user’s program must
decide which interrupt to service.
Within a specific interrupt service routine, the associated
pending bit should be cleared. This is typically done as early
as possible in the service routine in order to avoid missing
the next occurrence of the same type of interrupt event.
Thus, if the same event occurs a second time, even while the
first occurrence is still being serviced, the second occurrence will be serviced immediately upon return from the current interrupt routine.
An interrupt service routine typically ends with an RETI instruction. This instruction sets the GIE bit back to 1, pops the
address stored on the stack, and restores that address to the
program counter. Program execution then proceeds with the
next instruction that would have been executed had there
been no interrupt. If there are any valid interrupts pending,
the highest-priority interrupt is serviced immediately upon return from the previous interrupt.
10.3 VIS INSTRUCTION
The general interrupt service routine, which starts at address
00FF Hex, must be capable of handling all types of interrupts. The VIS instruction, together with an interrupt vector
table, directs the device to the specific interrupt handling routine based on the cause of the interrupt.
VIS is a single-byte instruction, typically used at the very beginning of the general interrupt service routine at address
00FF Hex, or shortly after that point, just after the code used
for context switching. The VIS instruction determines which
enabled and pending interrupt has the highest priority, and
causes an indirect jump to the address corresponding to that
interrupt source. The jump addresses (vectors) for all possible interrupts sources are stored in a vector table.
The vector table may be as long as 32 bytes (maximum of 16
vectors) and resides at the top of the 256-byte block containing the VIS instruction. However, if the VIS instruction is at
the very top of a 256-byte block (such as at 00FF Hex), the
vector table resides at the top of the next 256-byte block.
Thus, if the VIS instruction is located somewhere between
00FF and 01DF Hex (the usual case), the vector table is located between addresses 01E0 and 01FF Hex. If the VIS instruction is located between 01FF and 02DF Hex, then the
vector table is located between addresses 02E0 and 02FF
Hex, and so on.
Each vector is 15 bits long and points to the beginning of a
specific interrupt service routine somewhere in the 32 kbyte
memory space. Each vector occupies two bytes of the vector
table, with the higher-order byte at the lower address. The
vectors are arranged in order of interrupt priority. The vector
of the maskable interrupt with the lowest rank is located to
0yE0 (higher-order byte) and 0yE1 (lower-order byte). The
next priority interrupt is located at 0yE2 and 0yE3, and so
forth in increasing rank. The Software Trap has the highest
rank and its vector is always located at 0yFE and 0yFF. The
number of interrupts which can become active defines the
size of the table.
Table6
shows the types of interrupts, the interrupt arbitration
ranking, and the locations of the corresponding vectors in
the vector table.
The vector table should be filled by the user with the memory
locations of the specific interrupt service routines. For ex-
www.national.com32
10.0 Interrupts (Continued)
ample, if the Software Trap routine is located at 0310 Hex,
then the vector location 0yFE and -0yFF should contain the
data 03 and 10 Hex, respectively. When a Software Trap interrupt occurs and the VIS instruction is executed, the program jumps to the address specified in the vector table.
The interrupt sources in the vector table are listed in order of
rank, from highest to lowest priority. If two or more enabled
and pending interrupts are detected at the same time, the
one with the highest priority is serviced first. Upon return
from the interrupt service routine, the next highest-level
pending interrupt is serviced.
If the VIS instruction is executed, but no interrupts are enabled and pending, the lowest-priority interrupt vector is
used, and a jump is made to the corresponding address in
the vector table. This is an unusual occurrence, and may be
the result of an error. It can legitimately result from a change
in the enable bits or pending flags prior to the execution of
the VIS instruction, such as executing a single cycle instruction which clears an enable flag at the same time that the
pending flag is set. It can also result, however, from inadvertent execution of the VIS command outside of the context of
an interrupt.
The default VIS interrupt vector can be useful for applications in which time critical interrupts can occur during the
gram context (A, B, X, etc.) and executing the RETI instruction, an interrupt service routine can be terminated by returning to the VIS instruction. In this case, interrupts will be
serviced in turn until no further interrupts are pending and
the default VIS routine is started. After testing the GIE bit to
ensure that execution is not erroneous, the routine should
restore the program context and execute the RETI to return
to the interrupted program.
This technique can save up to fifty instruction cycles (t
more, (50µs at 10 MHz oscillator) of latency for pending in-
), or
c
terrupts with a penalty of fewer than ten instruction cycles if
no further interrupts are pending.
To ensure reliable operation, the user should always use the
VIS instruction to determine the source of an interrupt. Although it is possible to poll the pending bits to detect the
source of an interrupt, this practice is not recommended. The
use of polling allows the standard arbitration ranking to be altered, but the reliability of the interrupt system is compromised. The polling routine must individually test the enable
and pending bits of each maskable interrupt. If a Software
Trap interrupt should occur, it will be serviced last, even
though it should have the highest priority.Under certain conditions, a Software Trap could be triggered but not serviced,
resulting in an inadvertent “locking out” of all maskable interrupts by the Software Trap pending flag. Problems such as
this can be avoided by using VIS instruction.
servicing of another interrupt. Rather than restoring the pro-
Note 15: y is a variable which represents the VIS block. VIS and the vector table must be located in the same 256-byte block except if VIS is located at the last address of a block. In this case, the table must be in the next block.
www.national.com33
10.0 Interrupts (Continued)
10.3.1 VIS Execution
When the VIS instruction is executed it activates the arbitration logic. The arbitration logic generates an even number
between E0 and FE (E0, E2, E4, E6 etc...) depending on
which active interrupt has the highest arbitration ranking at
the time of the 1st cycle of VIS is executed. For example, if
the software trap interrupt is active, FE is generated. If the
external interrupt is active and the software trap interrupt is
not, then FAis generated and so forth. If the only active interrupt is software trap, than E0 is generated. This number replaces the lower byte of the PC. The upper byte of the PC re-
mains unchanged. The new PC is therefore pointing to the
vector of the active interrupt with the highest arbitration ranking. This vector is read from program memory and placed
into the PC which is now pointed to the 1st instruction of the
service routine of the active interrupt with the highest arbitration ranking.
Figure 27
instruction.
tion.
The non-maskable interrupt pending flag is cleared by the
RPND (Reset Non-Maskable Pending Bit) instruction (under
certain conditions) and upon RESET.
illustrates the different steps performed by the VIS
.
.
.
.=0FF; The interrupt causes a
VIS; branch to address 0FF
; The VIS causes a branch to
;interrupt vector table
.
.
.
.=01FA; Vector table (within 256 byte
.ADDRW SERVICE; of VIS inst.) containing the ext
; interrupt service routine
.
.
RETI
.
.
; Reset ext interrupt pend. bit
.
.
.
JPINT_EXIT; Return, set the GIE bit
www.national.com36
10.0 Interrupts (Continued)
10.4 NON-MASKABLE INTERRUPT
10.4.1 Pending Flag
There is a pending flag bit associated with the non-maskable
interrupt, called STPND. This pending flag is not memorymapped and cannot be accessed directly by the software.
The pending flag is reset to zero when a device Reset occurs. When the non-maskable interrupt occurs, the associated pending bit is set to 1. The interrupt service routine
should contain an RPND instruction to reset the pending flag
to zero. The RPND instruction always resets the STPND
flag.
10.4.2 Software Trap
The Software Trap is a special kind of non-maskable interrupt which occurs when the INTR instruction (used to acknowledge interrupts) is fetched from program memory and
placed in the instruction register. This can happen in a variety of ways, usually because of an error condition. Some examples of causes are listed below.
If the program counter incorrectly points to a memory location beyond the available program memory space, the nonexistent or unused memory location returns zeroes which is
interpreted as the INTR instruction.
If the stack is popped beyond the allowed limit (address 06F
Hex), a 7FFF will be loaded into the PC, if this last location in
program memory is unprogrammed or unavailable, a Software Trap will be triggered.
A Software Trap can be triggered by a temporary hardware
condition such as a brownout or power supply glitch.
The Software Trap has the highest priority of all interrupts.
When a Software Trapoccurs, the STPND bit is set. The GIE
bit is not affected and the pending bit (not accessible by the
user) is used to inhibit other interrupts and to direct the program to the ST service routine with the VIS instruction. Nothing can interrupt a Software Trap service routine except for
another Software Trap. The STPND can be reset only by the
RPND instruction or a chip Reset.
The Software Trap indicates an unusual or unknown error
condition. Generally, returning to normal execution at the
point where the Software Trap occurred cannot be done reliably. Therefore, the Software Trap service routine should
reinitialize the stack pointer and perform a recovery procedure that restarts the software at some known point, similar
to a device Reset, but not necessarily performing all the
same functions as a device Reset. The routine must also execute the RPND instruction to reset the STPND flag. Otherwise, all other interrupts will be locked out. Tothe extent possible, the interrupt routine should record or indicate the
context of the device so that the cause of the Software Trap
can be determined.
If the user wishes to return to normal execution from the
point at which the Software Trap was triggered, the user
must first execute RPND, followed by RETSK rather than
RETI or RET. This is because the return address stored on
the stack is the address of the INTR instruction that triggered
the interrupt. The program must skip that instruction in order
to proceed with the next one. Otherwise, an infinite loop of
Software Traps and returns will occur.
Programming a return to normal execution requires careful
consideration. If the Software Trap routine is interrupted by
another Software Trap, the RPND instruction in the service
routine for the second Software Trap will reset the STPND
flag; upon return to the first Software Trap routine, the
STPND flag will have the wrong state. This will allow
maskable interrupts to be acknowledged during the servicing
of the first Software Trap. Toavoid problems such as this, the
user program should contain the Software Trap routine to
perform a recovery procedure rather than a return to normal
execution.
Under normal conditions, the STPND flag is reset by a
RPND instruction in the Software Trap service routine. If a
programming error or hardware condition (brownout, power
supply glitch, etc.) sets the STPND flag without providing a
way for it to be cleared, all other interrupts will be locked out.
To alleviate this condition, the user can use extra RPND instructions in the main program and in the WATCHDOG service routine (if present). There is no harm in executing extra
RPND instructions in these parts of the program.
10.5 PORT L INTERRUPTS
Port L provides the user with an additional eight fully selectable, edge sensitive interrupts which are all vectored into the
same service subroutine.
The interrupt from Port L shares logic with the wake up circuitry.The register WKEN allows interrupts from Port L to be
individually enabled or disabled. The register WKEDG specifies the trigger condition to be either a positive or a negative
edge. Finally, the register WKPND latches in the pending
trigger conditions.
The GIE (Global Interrupt Enable) bit enables the interrupt
function.
A control flag, LPEN, functions as a global interrupt enable
for Port L interrupts. Setting the LPEN flag will enable interrupts and vice versa. A separate global pending flag is not
needed since the register WKPND is adequate.
Since Port L is also used for waking the device out of the
HALTor IDLE modes, the user can elect to exit the HALT or
IDLE modes either with or without the interrupt enabled. If he
elects to disable the interrupt, then the device will restart execution from the instruction immediately following the instruction that placed the microcontroller in the HALT or IDLE
modes. In the other case, the device will first execute the interrupt service routine and then revert to normal operation.
(See HALT MODE for clock option wakeup information.)
10.6 INTERRUPT SUMMARY
The device uses the following types of interrupts, listed below in order of priority:
1. The Software Trap non-maskable interrupt, triggered by
the INTR (00 opcode) instruction. The Software Trap is
acknowledged immediately. This interrupt service routine can be interrupted only by another Software Trap.
The Software Trap should end with two RPND instructions followed by a restart procedure.
2. Maskable interrupts, triggered by an on-chip peripheral
block or an external device connected to the device. Under ordinary conditions, a maskable interrupt will not interrupt any other interrupt routine in progress. A
maskable interrupt routine in progress can be interrupted by the non-maskable interrupt request. A
maskable interrupt routine should end with an RETI instruction or, prior to restoring context, should return to
execute the VIS instruction. This is particularly useful
when exiting long interrupt service routiness if the time
between interrupts is short. In this case the RETI instruction would only be executed when the default VIS routine is reached.
www.national.com37
11.0 WATCHDOG/Clock Monitor
Each device contains a user selectable WATCHDOG and
clock monitor. The following section is applicable only if
WATCHDOG feature has been selected in the ECON register.The WATCHDOGis designed to detect the user program
getting stuck in infinite loops resulting in loss of program control or “runaway” programs.
The WATCHDOG logic contains two separate service windows. While the user programmable upper window selects
the WATCHDOG service time, the lower window provides
protection against an infinite program loop that contains the
WATCHDOG service instruction.
The Clock Monitor is used to detect the absence of a clock or
a very slow clock below a specified rate on the CKI pin.
The WATCHDOG consists of two independent logic blocks:
WD UPPER and WD LOWER. WD UPPER establishes the
upper limit on the service window and WD LOWER defines
the lower limit of the service window.
Servicing the WATCHDOG consists of writing a specific
value to a WATCHDOG Service Register named WDSVR
which is memory mapped in the RAM. This value is composed of three fields, consisting of a 2-bit Window Select, a
5-bit Key Data field, and the 1-bit Clock Monitor Select field.
Table 7
shows the WDSVR register.
TABLE 7. WATCHDOG Service Register (WDSVR)
Window
Select
Key Data
XX01100Y
76543210
The lower limit of the service window is fixed at 256 instruction cycles. Bits 7 and 6 of the WDSVR register allow the
user to pick an upper limit of the service window.
Table 8
shows the four possible combinations of lower and
upper limits for the WATCHDOG service window. This flexibility in choosing the WATCHDOGservice window prevents
any undue burden on the user software.
Bits 5, 4, 3, 2 and 1 of the WDSVR register represent the
5-bit Key Data field. The key data is fixed at 01100. Bit 0 of
the WDSVR Register is the Clock Monitor Select bit.
TABLE 8. WATCHDOG Service Window Select
WDSVR WDSVRClockService Window
Bit 7Bit 6Monitor(Lower-Upper Limits)
00x2048–8k t
01x2048–16k t
10x2048–32k t
11x2048–64k t
xx0Clock Monitor Disabled
xx1Clock Monitor Enabled
11.1 CLOCK MONITOR
The Clock Monitor aboard the device can be selected or deselected under program control. The Clock Monitor is guaranteed not to reject the clock if the instruction cycle clock (1/
t
) is greater or equal to 10 kHz. This equates to a clock
C
input rate on CKI of greater or equal to 100 kHz.
Cycles
C
C
C
C
Clock
Monitor
Cycles
Cycles
Cycles
11.2 WATCHDOG/CLOCK MONITOR OPERATION
The WATCHDOG is enabled by bit 2 of the ECON register.
When this ECON bit is 0, the WATCHDOG is enabled and
pin G1 becomes the WATCHDOGoutput with a weak pullup.
The WATCHDOG and Clock Monitor are disabled during reset. The device comes out of reset with the WATCHDOG
armed, the WATCHDOG Window Select bits (bits 6, 7 of the
WDSVR Register) set, and the Clock Monitor bit (bit 0 of the
WDSVR Register) enabled. Thus, a Clock Monitor error will
occur after coming out of reset, if the instruction cycle clock
frequency has not reached a minimum specified value, including the case where the oscillator fails to start.
The WDSVR register can be written to only once after reset
and the key data (bits 5 through 1 of the WDSVR Register)
must match to be a valid write. This write to the WDSVR register involves two irrevocable choices: (i) the selection of the
WATCHDOG service window (ii) enabling or disabling of the
Clock Monitor. Hence, the first write to WDSVR Register involves selecting or deselecting the Clock Monitor, select the
WATCHDOG service window and match the WATCHDOG
key data. Subsequent writes to the WDSVR register will
compare the value being written by the user to the WATCHDOG service window value and the key data (bits 7 through
1) in the WDSVR Register.
Table 9
shows the sequence of
events that can occur.
The user must service the WATCHDOG at least once before
the upper limit of the service window expires. The WATCHDOG may not be serviced more than once in every lower
limit of the service window.
The WATCHDOG has an output pin associated with it. This
is the WDOUT pin, on pin 1 of the port G. WDOUT is active
low and must be externally connected to the RESET pin or to
some other external logic which handles WATCHDOG event.
The WDOUT pin has a weak pullup in the inactive state. This
pull-up is sufficient to serve as the connection to V
tems which use the internal Power On Reset. Upon trigger-
CC
for sys-
ing the WATCHDOG, the logic will pull the WDOUT (G1) pin
low for an additional 16 t
on WDOUT pin goes below the lower Schmitt trigger thresh-
–32tCcycles after the signal level
C
old. After this delay, the device will stop forcing the WDOUT
output low. The WATCHDOG service window will restart
when the WDOUT pin goes high.
AWATCHDOGservice while the WDOUT signal is active will
be ignored. The state of the WDOUT pin is not guaranteed
on reset, but if it powers up low then the WATCHDOG will
time out and WDOUT will go high.
The Clock Monitor forces the G1 pin low upon detecting a
clock frequency error. The Clock Monitor error will continue
until the clock frequency has reached the minimum specified
value, after which the G1 output will go high following 16
t
–32 tCclock cycles. The Clock Monitor generates a con-
C
tinual Clock Monitor error if the oscillator fails to start, or fails
to reach the minimum specified frequency. The specification
for the Clock Monitor is as follows:
>
1/t
10 kHz— No clock rejection.
C
<
10 Hz— Guaranteed clock rejection.
1/t
C
www.national.com38
11.0 WATCHDOG/Clock Monitor (Continued)
TABLE 9. WATCHDOG Service Actions
KeyWindowClockAction
DataDataMonitor
MatchMatchMatchValid Service: Restart Service Window
The following salient points regarding the WATCHDOG and
CLOCK MONITOR should be noted:
Both the WATCHDOG and CLOCK MONITOR detector
•
circuits are inhibited during RESET.
Following RESET, the WATCHDOG and CLOCK MONI-
•
TOR are both enabled, with the WATCHDOG having the
maximum service window selected.
The WATCHDOG service window and CLOCK MONI-
•
TOR enable/disable option can only be changed once,
during the initial WATCHDOG service following RESET.
The initial WATCHDOG service must match the key data
•
value in the WATCHDOG Service register WDSVR in order to avoid a WATCHDOG error.
Subsequent WATCHDOG services must match all three
•
data fields in WDSVR in order to avoid WATCHDOG errors.
The correct key data value cannot be read from the
•
WATCHDOG Service register WDSVR. Any attempt to
read this key data value of 01100 from WDSVR will read
as key data value of all 0’s.
The WATCHDOG detector circuit is inhibited during both
•
the HALT and IDLE modes.
The CLOCK MONITOR detector circuit is active during
•
both the HALT and IDLE modes. Consequently, the device inadvertently entering the HALT mode will be detected as a CLOCK MONITOR error (provided that the
CLOCK MONITOR enable option has been selected by
the program).
With the single-pin R/C oscillator option selected and the
•
CLKDLY bit reset, the WATCHDOG service window will
resume following HALT mode from where it left off before
entering the HALT mode.
With the crystal oscillator option selected, or with the
•
single-pin R/C oscillator option selected and the CLKDLY
bit set, the WATCHDOG service window will be set to its
selected value from WDSVR following HALT. Consequently, the WATCHDOG should not be serviced for at
least 256 instruction cycles following HALT, but must be
serviced within the selected window to avoid a WATCHDOG error.
The IDLE timer T0 is not initialized with external RESET.
•
The user can sync in to the IDLE counter cycle with an
•
IDLE counter (T0) interrupt or by monitoring the T0PND
flag. The T0PND flag is set whenever the twelfth bit of the
IDLE counter toggles (every 4096 instruction cycles). The
user is responsible for resetting the T0PND flag.
A hardware WATCHDOG service occurs just as the de-
•
vice exits the IDLE mode. Consequently, the WATCHDOG should not be serviced for at least 256 instruction
cycles following IDLE, but must be serviced within the selected window to avoid a WATCHDOG error.
Following RESET,the initial WATCHDOG service (where
•
the service window and the CLOCK MONITOR enable/
disable must be selected) may be programmed anywhere within the maximum service window (65,536 instruction cycles) initialized by RESET.Note that this initial
WATCHDOG service may be programmed within the initial 256 instruction cycles without causing a WATCHDOG
error.
11.4 DETECTION OF ILLEGAL CONDITIONS
The device can detect various illegal conditions resulting
from coding errors, transient noise, power supply voltage
drops, runaway programs, etc.
Reading of undefined ROM gets zeroes. The opcode for
software interrupt is 00. If the program fetches instructions
from undefined ROM, this will force a software interrupt, thus
signaling that an illegal condition has occurred.
The subroutine stack grows down for each call (jump to subroutine), interrupt, or PUSH, and grows up for each return or
POP. The stack pointer is initialized to RAM location 06F Hex
during reset. Consequently, if there are more returns than
calls, the stack pointer will point to addresses 070 and 071
Hex (which are undefined RAM). Undefined RAM from addresses 070 to 07F (Segment 0), and all other segments
(i.e., Segments 4 … etc.) is read as all 1’s, which in turn will
cause the program to return to address 7FFF Hex. It is recommended that the user either leave this location unprogrammed or place an INTR instruction (all 0’s) in this location
to generate a software interrupt signaling an illegal condition.
Thus, the chip can detect the following illegal conditions:
1. Executing from undefined ROM.
2. Over “POP”ing the stack by having more returns than
calls.
When the software interrupt occurs, the user can re-initialize
the stack pointer and do a recovery procedure before restarting (this recovery program is probably similar to that following reset, but might not contain the same program initialization procedures). The recovery program should reset the
software interrupt pending bit using the RPND instruction.
www.national.com39
12.0 MICROWIRE/PLUS
MICROWIRE/PLUS is a serial SPI compatible synchronous
communications interface. The MICROWIRE/PLUS capability enables the device to interface with MICROWIRE/PLUS
or SPI peripherals (i.e. A/D converters, display drivers, EEPROMs etc.) and with other microcontrollers which support
the MICROWIRE/PLUS or SPI interface. It consists of an
8-bit serial shift register (SIO) with serial data input (SI), serial data output (SO) and serial shift clock (SK).
shows a block diagram of the MICROWIRE/PLUS logic.
The shift clock can be selected from either an internal source
or an external source. Operating the MICROWIRE/PLUS arrangement with the internal clock source is called the Master
mode of operation. Similarly, operating the MICROWIRE/
PLUS arrangement with an external shift clock is called the
Slave mode of operation.
The CNTRL register is used to configure and control the
MICROWIRE/PLUS mode. To use the MICROWIRE/PLUS,
the MSEL bit in the CNTRL register is set to one. In the master mode, the SK clock rate is selected by the two bits, SL0
and SL1, in the CNTRL register.
Table10
clock rates that may be selected.
TABLE 10. MICROWIRE/PLUS
Master Mode Clock Select
SL1SL0SK Period
002xt
014xt
1x8xt
Where tCis the instruction cycle clock
Figure 29
details the different
C
C
C
12.1 MICROWIRE/PLUS OPERATION
Setting the BUSY bit in the PSW register causes the
MICROWIRE/PLUS to start shifting the data. It gets reset
when eight data bits have been shifted. The user may reset
the BUSY bit by software to allow less than 8 bits to shift. If
enabled, an interrupt is generated when eight data bits have
been shifted. The device may enter the MICROWIRE/PLUS
mode either as a Master or as a Slave.
Figure 29
shows how
two microcontroller devices and several peripherals may be
interconnected using the MICROWIRE/PLUS arrangements.
WARNING
The SIO register should only be loaded when the SK clock is
in the idle phase. Loading the SIO register while the SK clock
is in the active phase, will result in undefined data in the SIO
register.
Setting the BUSY flag when the input SK clock is in the active phase while in the MICROWIRE/PLUS is in the slave
mode may cause the current SK clock for the SIO shift register to be narrow. For safety, the BUSY flag should only be
set when the input SK clock is in the idle phase.
12.1.1 MICROWIRE/PLUS Master Mode Operation
In the MICROWIRE/PLUS Master mode of operation the
shift clock (SK) is generated internally. The MICROWIRE
Master always initiates all data exchanges. The MSEL bit in
the CNTRL register must be set to enable the SO and SK
functions onto the G Port. The SO and SK pins must also be
selected as outputs by setting appropriate bits in the Port G
configuration register. In the slave mode, the shift clock
stops after 8 clock pulses.
Table 11
summarizes the bit set-
tings required for Master mode of operation.
FIGURE 29. MICROWIRE/PLUS Application
www.national.com40
DS101116-32
12.0 MICROWIRE/PLUS (Continued)
12.1.2 MICROWIRE/PLUS Slave Mode Operation
In the MICROWIRE/PLUS Slave mode of operation the SK
clock is generated by an external source. Setting the MSEL
bit in the CNTRL register enables the SO and SK functions
onto the G Port. The SK pin must be selected as an input
and the SO pin is selected as an output pin by setting and resetting the appropriate bits in the Port G configuration register.
Table 11
Slave mode of operation.
summarizes the settings required to enter the
The user must set the BUSY flag immediately upon entering
the Slave mode. This ensures that all data bits sent by the
Master is shifted properly.After eight clock pulses the BUSY
flag is clear, the shift clock is stopped, and the sequence
may be repeated.
12.1.3 Alternate SK Phase Operation and SK Idle
Polarity
The device allows either the normal SK clock or an alternate
phase SK clock to shift data in and out of the SIO register. In
both the modes the SK idle polarity can be either high or low.
The polarity is selected by bit 5 of Port G data register. In the
TABLE 11. MICROWIRE/PLUS Mode Settings
This table assumes that the control flag MSEL is set.
G4 (SO)G5 (SK)G4G5Operation
Config. Bit Config. BitFun. Fun.
11SOInt. MICROWIRE/PLUS
SK Master
01TRI-Int. MICROWIRE/PLUS
STATE SK Master
10SOExt. MICROWIRE/PLUS
SK Slave
00TRI-Ext. MICROWIRE/PLUS
STATE SK Slave
normal mode data is shifted in on the rising edge of the SK
clock and the data is shifted out on the falling edge of the SK
clock. In the alternate SK phase operation, data is shifted in
on the falling edge of the SK clock and shifted out on the rising edge of the SK clock. Bit 6 of Port G configuration register selects the SK edge.
A control flag, SKSEL, allows either the normal SK clock or
the alternate SK clock to be selected. Resetting SKSEL
causes the MICROWIRE/PLUS logic to be clocked from the
normal SK signal. Setting the SKSEL flag selects the alternate SK clock. The SKSEL is mapped into the G6 configuration bit. The SKSEL flag will power up in the reset condition,
selecting the normal SK signal.
TABLE 12. MICROWIRE/PLUS Shift Clock Polarity and Sample/Shift Phase
FIGURE 30. MICROWIRE/PLUS SPI Mode Interface Timing, Normal SK Mode, SK Idle Phase being Low
DS101116-34
FIGURE 31. MICROWIRE/PLUS SPI Mode Interface Timing, Alternate SK Mode, SK Idle Phase being Low
www.national.com41
12.0 MICROWIRE/PLUS (Continued)
DS101116-35
FIGURE 32. MICROWIRE/PLUS SPI Mode Interface Timing, Alternate SK Mode, SK Idle Phase being High
DS101116-31
FIGURE 33. MICROWIRE/PLUS SPI Mode Interface Timing, Normal SK Mode, SK Idle Phase being High
www.national.com42
13.0 Memory Map
All RAM, ports and registers (except A and PC) are mapped into data memory address space.
AddressContents
S/ADD REG
0000 to 006FOn-Chip RAM bytes (112 bytes)
0070 to 007FUnused RAM Address Space (Reads As
All Ones)
xx80 to xx93Unused RAM Address Space (Reads
Undefined Data)
xx94Port F data register, PORTFD
xx95Port F configuration register, PORTFC
xx96Port F input pins (read only), PORTFP
xx97 to xxAFUnused address space (Reads
Undefined Data)
xxB0Timer T3 Lower Byte
xxB1Timer T3 Upper Byte
xxB2Timer T3 Autoload Register T3RA Lower
Byte
xxB3Timer T3 Autoload Register T3RA Upper
Byte
xxB4Timer T3 Autoload Register T3RB Lower
Byte
xxB5Timer T3 Autoload Register T3RB Upper
Byte
xxB6Timer T3 Control Register
xxB7Comparator Select Register
(Reg:CMPSL)
xxB8UART Transmit Buffer (Reg:TBUF)
xxB9UART Receive Buffer (Reg:RBUF)
xxBAUART Control and Status Register
(Reg:ENU)
xxBBUART Receive Control and Status
Register (Reg:ENUR)
xxBCUART Interrupt and Clock Source
Byte
xxC6Timer T2 Control Register
xxC7WATCHDOG Service Register
(Reg:WDSVR)
xxC8MIWU Edge Select Register
(Reg:WKEDG)
AddressContents
S/ADD REG
xxC9MIWU Enable Register (Reg:WKEN)
xxCAMIWU Pending Register (Reg:WKPND)
xxCB to xxCF Reserved
xxD0Port L Data Register
xxD1Port L Configuration Register
xxD2Port L Input Pins (Read Only)
xxD3Reserved for Port L
xxD4Port G Data Register
xxD5Port G Configuration Register
xxD6Port G Input Pins (Read Only)
xxD7Port I Input Pins (Read Only) (Actually
reads Port F input pins)
xxD8Port C Data Register
xxD9Port C Configuration Register
xxDAPort C Input Pins (Read Only)
xxDBReserved for Port C
xxDCPort D
xxDD to xxDF Reserved for Port D
xxE0 to xxE5Reserved for EE Control Registers
xxE6Timer T1 Autoload Register T1RB Lower
Byte
xxEECNTRL Control Register
xxEFPSW Register
xxF0 to FBOn-Chip RAM Mapped as Registers
xxFCX Register
xxFDSP Register
xxFEB Register
xxFFS Register
0100–017FOn-Chip 128 RAM Bytes
0200–027FOn-Chip 128 RAM Bytes (Reads as
undefined data on COP8FGE)
0300–037FOn-Chip 128 RAM Bytes (Reads as
undefined data on COP8FGE)
Note: Reading memory locations 0070H–007FH (Segment 0) will return all
ones. Reading unused memory locations 0080H–0093H (Segment 0)
will return undefined data. Reading memory locations from other Segments (i.e., Segment 4, Segment 5, … etc.) will return undefined data.
www.national.com43
14.0 Instruction Set
14.1 INTRODUCTION
This section defines the instruction set of the COPSAx7
Family members. It contains information about the instruction set features, addressing modes and types.
14.2 INSTRUCTION FEATURES
The strength of the instruction set is based on the following
features:
Mostly single-byte opcode instructions minimize program
•
size.
One instruction cycle for the majority of single-byte in-
•
structions to minimize program execution time.
Many single-byte, multiple function instructions such as
•
DRSZ.
Three memory mapped pointers: two for register indirect
•
addressing, and one for the software stack.
Sixteen memory mapped registers that allow an opti-
•
mized implementation of certain instructions.
Ability to set, reset, and test any individual bit in data
•
memory address space, including the memory-mapped
I/O ports and registers.
Register-Indirect LOAD and EXCHANGE instructions
•
with optional automatic post-incrementing or decrementing of the register pointer. This allows for greater efficiency (both in cycle time and program code) in loading,
walking across and processing fields in data memory.
Unique instructions to optimize program size and
•
throughput efficiency. Some of these instructions are
DRSZ, IFBNE, DCOR, RETSK, VIS and RRC.
14.3 ADDRESSING MODES
The instruction set offers a variety of methods for specifying
memory addresses. Each method is called an addressing
mode. These modes are classified into two categories: operand addressing modes and transfer-of-control addressing
modes. Operand addressing modes are the various methods of specifying an address for accessing (reading or writing) data. Transfer-of-control addressing modes are used in
conjunction with jump instructions to control the execution
sequence of the software program.
14.3.1 Operand Addressing Modes
The operand of an instruction specifies what memory location is to be affected by that instruction. Several different operand addressing modes are available, allowing memory locations to be specified in a variety of ways. An instruction
can specify an address directly by supplying the specific address, or indirectly by specifying a register pointer. The contents of the register (or in some cases, two registers) point to
the desired memory location. In the immediate mode, the
data byte to be used is contained in the instruction itself.
Each addressing mode has its own advantages and disadvantages with respect to flexibility,execution speed, and program compactness. Not all modes are available with all instructions. The Load (LD) instruction offers the largest
number of addressing modes.
The available addressing modes are:
Direct
•
Register B or X Indirect
•
Register B or X Indirect with Post-Incrementing/
•
Decrementing
Immediate
•
Immediate Short
•
Indirect from Program Memory
•
The addressing modes are described below. Each description includes an example of an assembly language instruction using the described addressing mode.
Direct. The memory address is specified directly as a byte in
the instruction. In assembly language, the direct address is
written as a numerical value (or a label that has been defined
elsewhere in the program as a numerical value).
Example: Load Accumulator Memory Direct
LD A,05
Reg/DataContentsContents
MemoryBeforeAfter
AccumulatorXX HexA6 Hex
Memory LocationA6 HexA6 Hex
0005 Hex
Register B or X Indirect. The memory address is specified
by the contents of the B Register or X register (pointer register). In assembly language, the notation [B] or [X] specifies
which register serves as the pointer.
Example: Exchange Memory with Accumulator, B Indirect
X A,[B]
Reg/DataContentsContents
MemoryBeforeAfter
Accumulator01 Hex87 Hex
Memory Location87 Hex01 Hex
0005 Hex
B Pointer05 Hex05 Hex
Register B or X Indirect with Post-Incrementing/
Decrementing. The relevant memory address is specified
by the contents of the B Register or X register (pointer register). The pointer register is automatically incremented or
decremented after execution, allowing easy manipulation of
memory blocks with software loops. In assembly language,
the notation [B+], [B−], [X+], or [X−] specifies which register
serves as the pointer, and whether the pointer is to be incremented or decremented.
Example: Exchange Memory with Accumulator, B Indirect
Intermediate. The data for the operation follows the instruction opcode in program memory. In assembly language, the
number sign character (
with Post-Increment
X A,[B+]
Reg/DataContentsContents
MemoryBeforeAfter
Accumulator03 Hex62 Hex
Memory Location62 Hex03 Hex
0005 Hex
B Pointer05 Hex06 Hex
#
) indicates an immediate operand.
www.national.com44
14.0 Instruction Set (Continued)
Example: Load Accumulator Immediate
#
LD A,
05
Reg/DataContentsContents
MemoryBeforeAfter
AccumulatorXX Hex05 Hex
Immediate Short. This is a special case of an immediate instruction. In the “Load B immediate” instruction, the 4-bit immediate value in the instruction is loaded into the lower
nibble of the B register. The upper nibble of the B register is
reset to 0000 binary.
Example: Load B Register Immediate Short
#
LD B,
7
Reg/DataContentsContents
MemoryBeforeAfter
B Pointer12 Hex07 Hex
Indirect from Program Memory. This is a special case of
an indirect instruction that allows access to data tables
stored in program memory. In the “Load Accumulator Indirect” (LAID) instruction, the upper and lower bytes of the Program Counter (PCU and PCL) are used temporarily as a
pointer to program memory. For purposes of accessing program memory, the contents of the Accumulator and PCL are
exchanged. The data pointed to by the Program Counter is
loaded into the Accumulator,and simultaneously, the original
contents of PCL are restored so that the program can resume normal execution.
Example: Load Accumulator Indirect
LAID
Reg/DataContentsContents
MemoryBeforeAfter
PCU04 Hex04 Hex
PCL35 Hex36 Hex
Accumulator1F Hex25 Hex
Memory Location25 Hex25 Hex
041F Hex
14.3.2 Tranfer-of-Control Addressing Modes
Program instructions are usually executed in sequential order. However, Jump instructions can be used to change the
normal execution sequence. Several transfer-of-control addressing modes are available to specify jump addresses.
A change in program flow requires a non-incremental
change in the Program Counter contents. The Program
Counter consists of two bytes, designated the upper byte
(PCU) and lower byte (PCL). The most significant bit of PCU
is not used, leaving 15 bits to address the program memory.
Different addressing modes are used to specify the new address for the Program Counter. The choice of addressing
mode depends primarily on the distance of the jump. Farther
jumps sometimes require more instruction bytes in order to
completely specify the new Program Counter contents.
The available transfer-of-control addressing modes are:
Jump Relative
•
Jump Absolute
•
Jump Absolute Long
•
Jump Indirect
•
The transfer-of-control addressing modes are described below. Each description includes an example of a Jump instruction using a particular addressing mode, and the effect
on the Program Counter bytes of executing that instruction.
Jump Relative. In this 1-byte instruction, six bits of the instruction opcode specify the distance of the jump from the
current program memory location. The distance of the jump
can range from −31 to +32. AJP+1 instruction is not allowed.
The programmer should use a NOP instead.
Example: Jump Relative
JP 0A
RegContentsContents
BeforeAfter
PCU02 Hex02 Hex
PCL05 Hex0F Hex
Jump Absolute. In this 2-byte instruction, 12 bits of the instruction opcode specify the new contents of the Program
Counter. The upper three bits of the Program Counter remain unchanged, restricting the new Program Counter address to the same 4 kbyte address space as the current instruction.
(This restriction is relevant only in devices using more than
one 4 kbyte program memory space.)
Example: Jump Absolute
JMP 0125
RegContentsContents
BeforeAfter
PCU0C Hex01 Hex
PCL77 Hex25 Hex
Jump Absolute Long. In this 3-byte instruction, 15 bits of
the instruction opcode specify the new contents of the Program Counter.
Example: Jump Absolute Long
JMP 03625
Reg/ContentsContents
MemoryBeforeAfter
PCU42 Hex36 Hex
PCL36 Hex25 Hex
www.national.com45
14.0 Instruction Set (Continued)
Jump Indirect. In this 1-byte instruction, the lower byte of
the jump address is obtained from a table stored in program
memory, with the Accumulator serving as the low order byte
of a pointer into program memory. For purposes of accessing program memory, the contents of the Accumulator are
written to PCL (temporarily). The data pointed to by the Program Counter (PCH/PCL) is loaded into PCL, while PCH remains unchanged.
Example: Jump Indirect
JID
Reg/ContentsContents
MemoryBeforeAfter
PCU01 Hex01 Hex
PCLC4 Hex32 Hex
Accumulator26 Hex26 Hex
Memory
Location32 Hex32 Hex
0126 Hex
The VIS instruction is a special case of the Indirect Transfer
of Control addressing mode, where the double-byte vector
associated with the interrupt is transferred from adjacent addresses in program memory into the Program Counter in order to jump to the associated interrupt service routine.
14.4 INSTRUCTION TYPES
The instruction set contains a wide variety of instructions.
The available instructions are listed below, organized into related groups.
Some instructions test a condition and skip the next instruction if the condition is not true. Skipped instructions are executed as no-operation (NOP) instructions.
14.4.1 Arithmetic Instructions
The arithmetic instructions perform binary arithmetic such as
addition and subtraction, with or without the Carry bit.
Add (ADD)
Add with Carry (ADC)
Subtract (SUB)
Subtract with Carry (SUBC)
Increment (INC)
Decrement (DEC)
Decimal Correct (DCOR)
Clear Accumulator (CLR)
Set Carry (SC)
Reset Carry (RC)
14.4.2 Transfer-of-Control Instructions
The transfer-of-control instructions change the usual sequential program flow by altering the contents of the Program Counter. The Jump to Subroutine instructions save the
Program Counter contents on the stack before jumping; the
Return instructions pop the top of the stack back into the
Program Counter.
Jump Relative (JP)
Jump Absolute (JMP)
Jump Absolute Long (JMPL)
Jump Indirect (JID)
Jump to Subroutine (JSR)
www.national.com46
Jump to Subroutine Long (JSRL)
Return from Subroutine (RET)
Return from Subroutine and Skip (RETSK)
Return from Interrupt (RETI)
Software Trap Interrupt (INTR)
Vector Interrupt Select (VIS)
14.4.3 Load and Exchange Instructions
The load and exchange instructions write byte values in registers or memory. The addressing mode determines the
source of the data.
The logical instructions perform the operations AND, OR,
and XOR (Exclusive OR). Other logical operations can be
performed by combining these basic operations. For example, complementing is accomplished by exclusiveORing
the Accumulator with FF Hex.
Logical AND (AND)
Logical OR (OR)
Exclusive OR (XOR)
14.4.5 Accumulator Bit Manipulation Instructions
The Accumulator bit manipulation instructions allow the user
to shift the Accumulator bits and to swap its two nibbles.
Rotate Right Through Carry (RRC)
Rotate Left Through Carry (RLC)
Swap Nibbles of Accumulator (SWAP)
14.4.6 Stack Control Instructions
Push Data onto Stack (PUSH)
Pop Data off of Stack (POP)
14.4.7 Memory Bit Manipulation Instructions
The memory bit manipulation instructions allow the user to
set and reset individual bits in memory.
Set Bit (SBIT)
Reset Bit (RBIT)
Reset Pending Bit (RPND)
14.4.8 Conditional Instructions
The conditional instruction test a condition. If the condition is
true, the next instruction is executed in the normal manner; if
the condition is false, the next instruction is skipped.
If Equal (IFEQ)
If Not Equal (IFNE)
If Greater Than (IFGT)
If Carry (IFC)
If Not Carry (IFNC)
If Bit (IFBIT)
If B Pointer Not Equal (IFBNE)
And Skip if Zero (ANDSZ)
Decrement Register and Skip if Zero (DRSZ)
14.0 Instruction Set (Continued)
14.4.9 No-Operation Instruction
The no-operation instruction does nothing, except to occupy
space in the program memory and time in execution.
No-Operation (NOP)
Note: The VIS is a special case of the Indirect Transfer of Control addressing
mode, where the double byte vector associated with the interrupt is
transferred from adjacent addresses in the program memory into the
program counter (PC) in order to jump to the associated interrupt service routine.
14.5 REGISTER AND SYMBOL DEFINITION
The following abbreviations represent the nomenclature
used in the instruction description and the COP8
cross-assembler.
Registers
A8-Bit Accumulator Register
B8-Bit Address Register
X8-Bit Address Register
SP8-Bit Stack Pointer Register
PC15-Bit Program Counter Register
PUUpper 7 Bits of PC
PLLower 8 Bits of PC
14.6 INSTRUCTION SET SUMMARY
ADDA,MemlADDA←A + Meml
ADCA,MemlADD with CarryA←A+Meml+C,C←Carry,
SUBCA,MemlSubtract with CarryA←A−MemI+C,C←Carry,
ANDA,MemlLogical ANDA←A and Meml
ANDSZA,ImmLogical AND Immed., Skip if ZeroSkip next if (A and Imm)=0
ORA,MemlLogical ORA←A or Meml
XORA,MemlLogical EXclusive ORA←A xor Meml
IFEQMD,ImmIF EQualCompare MD and Imm, Do next if MD=Imm
IFEQA,MemlIF EQualCompare A and Meml, Do next if A=Meml
IFNEA,MemlIF Not EqualCompare A and Meml, Do next if A
IFGTA,MemlIF Greater ThanCompare A and Meml, Do next if A
IFBNE
DRSZRegDecrement Reg., Skip if ZeroReg←Reg − 1, Skip if Reg=0
SBIT
RBIT
IFBIT
RPNDReset PeNDing FlagReset Software Interrupt Pending Flag
XA,MemEXchange A with MemoryA
XA,[X]EXchange A with Memory [X]A
LDA,MemlLoaD A with MemoryA←Meml
LDA,[X]LoaD A with Memory [X]A←[X]
LDB,ImmLoaD B with Immed.B←Imm
LDMem,ImmLoaD Memory Immed.Mem←Imm
LDReg,ImmLoaD Register Memory Immed.Reg←Imm
XA,[B
XA,[X
#
#
,MemSet BIT1 to bit, Mem (bit=0 to 7 immediate)
#
,MemReset BIT0 to bit, Mem
#
,MemIF BITIf bit#, A or Mem is true do next instruction
If B Not EqualDo next if lower 4 bits of B≠Imm
±
]EXchange A with Memory [B]A↔[B], (B←B±1)
±
]EXchange A with Memory [X]A↔[X], (X←X±1)
C1 Bit of PSW Register for Carry
HC1 Bit of PSW Register for Half Carry
GIE1 Bit of PSW Register for Global Interrupt
[B]Memory Indirectly Addressed by B Register
[X]Memory Indirectly Addressed by X Register
MDDirect Addressed Memory
MemDirect Addressed Memory or [B]
MemlDirect Addressed Memory or [B] or
Imm8-Bit Immediate Data
RegRegister Memory: Addresses F0 to FF
BitBit Number (0 to 7)
←
↔
Enable
Immediate Data
(Includes B, X and SP)
Loaded with
Exchanged with
HC←Half Carry
HC←Half Carry
↔
Mem
↔
[X]
Registers
Symbols
≠
>
Meml
Meml
www.national.com47
14.0 Instruction Set (Continued)
LDA, [B±]LoaD A with Memory [B]A←[B], (B←B±1)
LDA, [X
LD[B
CLRACLeaR AA←0
INCAINCrement AA←A+1
DECADECrement AA←A−1
LAIDLoad A InDirect from ROMA←ROM (PU,A)
DCORADecimal CORrect AA←BCD correction of A (follows ADC, SUBC)
RRCARotate A Right thru CC→A7→…→A0→C
RLCARotate A Left thru CC←A7←…←A0←C, HC←A0
SWAPASWAP nibbles of AA7…A4
SCSet CC←1, HC←1
RCReset CC←0, HC←0
IFCIF CIF C is true, do next instruction
IFNCIF Not CIf C is not true, do next instruction
POPAPOP the stack into ASP←SP+1,A←[SP]
PUSHAPUSH A onto the stack[SP]←A, SP←SP−1
VISVector to Interrupt Service RoutinePU←[VU], PL←[VL]
JMPLAddr.Jump absolute LongPC←ii (ii=15 bits, 0 to 32k)
JMPAddr.Jump absolutePC9…0←i(i=12 bits)
JPDisp.Jump relative shortPC←PC+r(ris−31to+32, except 1)
JSRLAddr.Jump SubRoutine Long[SP]←PL, [SP−1]←PU,SP−2, PC←ii
JSRAddr.Jump SubRoutine[SP]←PL, [SP−1]←PU,SP−2, PC9…0←i
JIDJump InDirectPL←ROM (PU,A)
RETRETurn from subroutineSP + 2, PL←[SP], PU←[SP−1]
RETSKRETurn and SKipSP + 2, PL←[SP],PU←[SP−1],
RETIRETurn from InterruptSP + 2, PL←[SP],PU←[SP−1],GIE←1
INTRGenerate an Interrupt[SP]←PL, [SP−1]←PU, SP−2, PC←0FF
NOPNo OPerationPC←PC+1
±
]LoaD A with Memory [X]A←[X], (X←X±1)
±
],ImmLoaD Memory [B] Immed.[B]←Imm, (B←B±1)
↔
A3…A0
skip next instruction
www.national.com48
14.0 Instruction Set (Continued)
14.7 INSTRUCTION EXECUTION TIME
Most instructions are single byte (with immediate addressing
mode instructions taking two bytes).
Most single byte instructions take one cycle time to execute.
Skipped instructions require x number of cycles to be
skipped, where x equals the number of bytes in the skipped
instruction opcode.
See the BYTES and CYCLES per INSTRUCTION table for
details.
Bytes and Cycles per Instruction
The following table shows the number of bytes and cycles for
each instruction in the format of byte/cycle.
X A, (Note 16)1/11/32/31/21/3
LD A, (Note 16)1/11/32/32/21/21/3
LD B, Imm1/1(If B
LD B, Imm2/2(If B
LD Mem, Imm2/23/32/2
LD Reg, Imm2/3
IFEQ MD, Imm3/3
=
Note 16:
>
Memory location addressed by B or X or directly.
RegisterDirect Immed.Register Indirect
IndirectAuto Incr. & Decr.
[B][X][B+, B−][X+, X−]
<
16)
>
15)
www.national.com49
14.0 Instruction Set (Continued)
JP+17 INTR 0
JP+18 JP+2 1
JP+19 JP+3 2
JP+20 JP+4 3
JP+21 JP+5 4
JMP
JMP
JMP
JMP
JMP
x000–x0FF
x100–x1FF
x200–x2FF
x300–x3FF
x400–x4FF
x000–x0FF
x100–x1FF
x200–x2FF
x300–x3FF
x400–x4FF
IFBNE 0JSR
IFBNE 1JSR
IFBNE 2JSR
IFBNE 3JSR
IFBNE 4JSR
LD
B,#0F
A, #i
ANDSZ
B,#0E
*LD
B,#0D
*LD
B,#0C
*LD
B,#0B
CLRALD
JP+22 JP+6 5
JMP
IFBNE 5JSR
SWAPALD
JP+23 JP+7 6
JMP
x500–x5FF
x500–x5FF
IFBNE 6JSR
B,#0A
DCORALD
x600–x6FF
x600–x6FF
B,#09
JP+24 JP+8 7
JMP
IFBNE 7JSR
PUSHALD
x700–x7FF
x700–x7FF
B,#08
JP+25 JP+9 8
JMP
IFBNE 8JSR
LD
RBIT
x800–x8FF
x800–x8FF
B,#07
0,[B]
Lower Nibble
JP+26 JP+10 9
JMP
IFBNE 9JSR
LD
RBIT
x900–x9FF
x900–x9FF
B,#06
1,[B]
JP+27 JP+11 A
JMP
IFBNE 0AJSR
LD
RBIT
xA00–xAFF
xA00–xAFF
B,#05
2,[B]
JP+28 JP+12 B
JMP
IFBNE 0BJSR
LD
RBIT
xB00–xBFF
xB00–xBFF
B,#04
3,[B]
JP+29 JP+13 C
JMP
IFBNE 0CJSR
LD
RBIT
xC00–xCFF
xC00–xCFF
B,#03
4,[B]
JP+30 JP+14 D
JMP
IFBNE 0DJSR
LD
RBIT
JP+31 JP+15 E
JMP
xD00–xDFF
xD00–xDFF
IFBNE 0EJSR
LD
B,#02
5,[B]
RBIT
xE00–xEFF
xE00–xEFF
B,#01
6,[B]
JP+32 JP+16 F
JMP
IFBNE 0FJSR
LD
RBIT
xF00–xFFF
xF00–xFFF
B,#00
7,[B]
0,[B]
IFBIT
1,[B]
IFBIT
2,[B]
IFBIT
IFBIT
3,[B]
IFBIT
4,[B]
IFBIT
5,[B]
IFBIT
6,[B]
IFBIT
Upper Nibble
ADC
A,[B]
A,#i
RRCARCADC
0F0
F E D C BA9 876 5 432 10
14.8 OPCODE TABLE
www.national.com50
JP−15 JP−31 LD 0F0, #i DRSZ
A,[B]
SUBC
A, #i
*SCSUBC
0F1
JP−14 JP−30 LD 0F1, #i DRSZ
A,[B]
IFEQ
A,#i
IFEQ
X
A,[B+]
X
A,[X+]
0F2
JP−13 JP−29 LD 0F2, #i DRSZ
A,[B]
IFGT
A,#i
IFGT
X
A,[B−]
X
A,[X−]
0F3
JP−12 JP−28 LD 0F3, #i DRSZ
ADD
A,[B]
A,#i
VISLAIDADD
0F4
JP−11 JP−27 LD 0F4, #i DRSZ
AND
A,[B]
A,#i
RPNDJIDAND
0F5
JP−10 JP−26 LD 0F5, #i DRSZ
XOR
A,[B]
A,#i
XOR
A,[B]
X A,[X]X
0F6
JP−9JP−25 LD 0F6, #i DRSZ
**OR A,#iOR
JP−8JP−24 LD 0F7, #i DRSZ
7,[B]
A,[B]
0F7
0,[B]
NOP RLCA LD A,#iIFCSBIT
0F8
JP−7JP−23 LD 0F8, #i DRSZ
1,[B]
IFNCSBIT
A,#i
IFNE
IFEQ
Md,#i
A,[B]
IFNE
0F9
JP−6JP−22 LD 0F9, #i DRSZ
2,[B]
INCASBIT
LD
[B+],#i
LD
A,[B+]
LD
A,[X+]
0FA
JP−5JP−21 LD 0FA, #i DRSZ
3,[B]
DECA SBIT
LD
[B−],#i
LD
A,[B−]
LD
A,[X−]
0FB
JP−4JP−20 LD 0FB, #i DRSZ
4,[B]
JMPL X A,Md POPA SBIT
LD
Md,#i
0FC
JP−3JP−19 LD 0FC, #i DRSZ
5,[B]
RETSK SBIT
A,Md
DIRJSRLLD
0FD
JP−2JP−18 LD 0FD, #i DRSZ
6,[B]
RETSBIT
LD
[B],#i
LD
A,[B]
LD
A,[X]
0FE
JP−1JP−17 LD 0FE, #i DRSZ
7,[B]
**LD B,#i RETISBIT
0FF
JP−0JP−16 LD 0FF, #i DRSZ
i is the immediate data
Where,
Md is a directly addressed memory location
* is an unused opcode
The opcode 60 Hex is also the opcode for IFBIT #i,A
15.0 Mask Options
See Section 5.5 ECON (CONFIGURATION) REGISTER.
16.0 Development Support
16.1 OVERVIEW
National is engaged with an international community of independent 3rd party vendors who provide hardware and software development tool support. Through National’s interaction and guidance, these tools cooperate to form a choice of
tools that fits each developer’s needs.
This section provides a summary of the tool and development kits currently available. Up-to-date information, selection guides, free tools, demos, updates, and purchase information can be obtained at our web site at:
www.national.com/cop8.
16.2 SUMMARY OF TOOLS
COP8 Evaluation Tools
COP8–NSEVAL: Free Software Evaluation package for
•
Windows. A fully integrated evaluation environment for
COP8, including versions of WCOP8 IDE (Integrated Development Environment), COP8-NSASM, COP8-MLSIM,
COP8C, DriveWay
information.
COP8–MLSIM: Free Instruction Level Simulator tool for
•
Windows. For testing and debugging software instructions only (No I/O or interrupt support).
COP8–EPU: Very Low cost COP8 Evaluation & Pro-
•
gramming Unit. Windows based evaluation and
hardware-simulation tool, with COP8 device programmer
and erasable samples. Includes COP8-NSDEV, Driveway COP8 Demo, MetaLink Debugger, I/O cables and
power supply.
COP8–EVAL-ICUxx: Very Low cost evaluation and de-
•
sign test board for COP8ACC and COP8SGx Families,
from ICU. Real-time environment with add-on A/D, D/A,
and EEPROM. Includes software routines and reference
designs.
Manuals,Applications Notes, Literature: Available free
Unit. Windows based development and hardwaresimulation tool for COPSx/xG families, with COP8 device
programmer and samples. Includes COP8-NSDEV,
Driveway COP8 Demo, MetaLink Debugger, cables and
power supply.
COP8-DM: Moderate cost Debug Module from MetaLink.
•
A Windows based, real-time in-circuit emulation tool with
COP8 device programmer. Includes COP8-NSDEV,
DriveWay COP8 Demo, MetaLink Debugger, power supply, emulation cables and adapters.
COP8 Development Languages and Environments
COP8-NSASM: Free COP8 Assembler v5 for Win32.
•
Macro assembler, linker, and librarian for COP8 software
development. Supports all COP8 devices. (DOS/Win16
v4.10.2 available with limited support). (Compatible with
WCOP8 IDE, COP8C, and DriveWay COP8).
™
COP8, Manuals, and other COP8
COP8-NSDEV: Very low cost Software Development
•
Package for Windows. An integrated development environment for COP8, including WCOP8 IDE, COP8NSASM, COP8-MLSIM.
COP8C: Moderately priced C Cross-Compiler and Code
•
Development System from Byte Craft (no code limit). Includes BCLIDE (Byte Craft Limited Integrated Development Environment) for Win32, editor, optimizing C CrossCompiler, macro cross assembler, BC-Linker, and
MetaLink tools support. (DOS/SUN versions available;
Compiler is installable under WCOP8 IDE; Compatible
with DriveWay COP8).
EWCOP8-KS: Very Low cost ANSI C-Compiler and Em-
•
bedded Workbench from IAR (Kickstart version:
COP8Sx/Fx only with 2k code limit; No FP). A fully integrated Win32 IDE, ANSI C-Compiler, macro assembler,
editor, linker, Liberian, C-Spy simulator/debugger, PLUS
MetaLink EPU/DM emulator support.
EWCOP8-AS: Moderately priced COP8 Assembler and
•
Embedded Workbench from IAR (no code limit). A fully integrated Win32 IDE, macro assembler, editor, linker, librarian, and C-Spy high-level simulator/debugger with
I/O and interrupts support. (Upgradeable with optional
C-Compiler and/or MetaLink Debugger/Emulator support).
EWCOP8-BL: Moderately priced ANSI C-Compiler and
•
Embedded Workbench from IAR (Baseline version: All
COP8 devices; 4k code limit; no FP). A fully integrated
Win32 IDE, ANSI C-Compiler, macro assembler, editor,
linker,librarian, and C-Spy high-level simulator/debugger.
(Upgradeable; CWCOP8-M MetaLink tools interface support optional).
EWCOP8: Full featured ANSI C-Compiler and Embed-
•
ded Workbench for Windows from IAR (no code limit). A
fully integrated Win32 IDE, ANSI C-Compiler, macro assembler, editor, linker, librarian, and C-Spy high-level
simulator/debugger. (CWCOP8-M MetaLink tools interface support optional).
EWCOP8-M: Full featured ANSI C-Compiler and Embed-
•
ded Workbench for Windows from IAR (no code limit). A
fully integrated Win32 IDE, ANSI C-Compiler, macro assembler, editor, linker, librarian, C-Spy high-level
simulator/debugger, PLUS MetaLink debugger/hardware
interface (CWCOP8-M).
COP8 Productivity Enhancement Tools
WCOP8 IDE: Very Low cost IDE (Integrated Develop-
•
ment Environment) from KKD. Supports COP8C, COP8NSASM, COP8-MLSIM, DriveWay COP8, and MetaLink
debugger under a common Windows Project Management environment. Code development, debug, and emulation tools can be launched from the project window
framework.
DriveWay-COP8: Low cost COP8 Peripherals Code
•
Generation tool from Aisys Corporation. Automatically
generates tested and documented C or Assembly source
code modules containing I/O drivers and interrupt handlers for each on-chip peripheral. Application specific
code can be inserted for customization using the integrated editor. (Compatible with COP8-NSASM, COP8C,
and WCOP8 IDE.)
COP8-UTILS: Free set of COP8 assembly code ex-
•
amples, device drivers, and utilities to speed up code development.
www.national.com51
16.0 Development Support (Continued)
COP8-MLSIM: Free Instruction Level Simulator tool for
•
Windows. For testing and debugging software instructions only (No I/O or interrupt support).
COP8 Real-Time Emulation Tools
COP8-DM: MetaLink Debug Module. A moderately
•
priced real-time in-circuit emulation tool, with COP8 device programmer. Includes MetaLink Debugger, power
supply, emulation cables and adapters.
IM-COP8: MetaLink iceMASTER®. A full featured, real-
•
time in-circuit emulator for COP8 devices. Includes
COP8-NSDEV, Driveway COP8 Demo, MetaLink Windows Debugger, and power supply. Package-specific
probes and surface mount adaptors are ordered separately.
Note: The following order numbers apply to the COP8 devices in this datasheet only.
VendorToolsOrder NumberCostNotes
National COP8-NSEVALCOP8-NSEVALFreeWeb site download
COP8-NSASMCOP8-NSASMFree Included in EPU and DM. Web site download
COP8-MLSIMCOP8-MLSIMFreeIncluded in EPU and DM. Web site download
COP8-NSDEVCOP8-NSDEVVLIncluded in EPU and DM. Order CD from website
COP8-EPUCOP8SG-EPU (-1 or -2)VL-1 = 110V, -2 = 220V; Included p/s, 40 pin DIP target
DM-COP8/20D-SOVL20 pin DIP to SO converter
DM-COP8/20D-16DVL20 pin DIP to 16 pin DIP converter
DM-COP8/20DVL20 pin DIP target cable
DM-COP8/28D-28CSPL28 pin DIP to 28 pin CSP converter
DM-COP8/44P-44QL44 pin PLCC to 44 QFP converter
COP8FGx7VL8k or 32k Eraseable or OTP devices
COP8SA-PGMALFor programming 16/20/28 SOIC and 44 PLCC on the
COP8-PGMA-44QFPLFor programming 44 QFP on any programmer
COP8-PGMA-28CSPLFor programming 28 CSP on any programmer
COP8-PGMA-28SOVLFor programming 16/20/28 SOIC on any programmer
COP8 Device Programmer Support
MetaLink’s EPU and Debug Module include development
•
device programming capability for COP8 devices.
Third-party programmers and automatic handling equip-
•
ment cover needs from engineering prototype and pilot
production, to full production environments.
Factory programming available for high-volume require-
•
ments.
16.3 TOOLS ORDERING NUMBERS FOR THE
COP8FGx FAMILY DEVICES
The COP8FGx devices are faster speed versions of the
COP8SGx devices, and the existing SGx tools can be used
without updating or modification (just use the SGx menus).
The COP8SG-DM and IM-COP8/400 ICE can be used for
emulation with the limitation of 10 MHz emulation speed
maximum. For full speed COP8FGx emulation, use the 15
MHz COP8FG-DM.
NationalU.S.A.: Santa Clara, CAwww.national.com/cop8Europe: +49 (0) 180 530 8585
1-800-272-9959support
fax: 1-800-737-7018europe.support
The following companies have approved COP8 programmers in a variety of configurations. Contact your local office
or distributor. You can link to their web sites and get the latest listing of approved programmers from National’s COP8
OTP Support page at: www.national.com/cop8.
Complete product information and technical support is available from National’s customer response centers, and from
our on-line COP8 customer support sites.
COP8FG Family, 8-Bit CMOS ROM Based and OTP Microcontrollers with 8k to 32k Memory, Two
Comparators and USART
LIFE SUPPORT POLICY
NATIONAL’S PRODUCTS ARE NOT AUTHORIZED FOR USE AS CRITICAL COMPONENTS IN LIFE SUPPORT
DEVICES OR SYSTEMS WITHOUT THE EXPRESS WRITTEN APPROVAL OF THE PRESIDENT AND GENERAL
COUNSEL OF NATIONAL SEMICONDUCTOR CORPORATION. As used herein:
1. Life support devices or systems are devices or
systems which, (a) are intended for surgical implant
into the body, or (b) support or sustain life, and
whose failure to perform when properly used in
accordance with instructions for use provided in the
2. A critical component is any component of a life
support device or system whose failure to perform
can be reasonably expected to cause the failure of
the life support device or system, or to affect its
safety or effectiveness.
labeling, can be reasonably expected to result in a
significant injury to the user.
National does not assume any responsibility for use of any circuitry described, no circuit patent licenses are implied and National reserves the right at any time without notice to change said circuitry and specifications.