COP87L88GD/RD Family
8-Bit CMOS OTP Microcontrollers with 16k or 32k
Memory and 8-Channel A/D with Prescaler
General Description
The COP87L88GD/RD OTP (One Time Programmable)
Family microcontrollers are highly integratet COP8
ture core devices with 16k or 32k memory and advanced
features including anA/DConverter. These multi-chip CMOS
devices are suited for applications requiring a full featured
controller with an 8-bit A/D converter, and as pre-production
devices for a masked ROM design. Pin and software compatible 16k ROM versions are available (COP888GD), as
well as a range of COP8 software and hardware development tools.
COP87L88GD/RD Family 8-Bit CMOS OTP Microcontrollers with 16k or 32k Memory and
8-Channel A/D with Prescaler
July 1999
Family features include an 8-bit memory mapped architecture, 10 MHz CKI (-XE=crystal oscillator) with 1µs instruc-
™
tion cycle, three multi-function 16-bit timer/counters,
Fea-
MICROWIRE/PLUS
converter with prescaler and both differential and single
ended modes, two power saving HALT/IDLE modes, MIWU,
idle timer, high current outputs, software selectable I/O options, WATCHDOG
operation, program code security, and 44 pin package.
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
(Source)100 mA
)7V
CC
Pin
CC
CC
+ 0.3V
Total Current out of GND Pin
(Sink)110 mA
Storage Temperature Range−65˚C to +140˚C
Note 1:
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 Voltage2.75.5V
Power Supply Ripple (Note 3)Peak-to-Peak0.1 V
CC
Supply Current (Note 4)
CKI=10 MHzV
CKI=4 MHzV
HALT Current (Note 5)V
=
CC
=
CC
=
CC
=
V
CC
=
5.5V, t
4.0V, t
1µs20mA
c
=
2.5 µs10mA
c
5.5V, CKI=0 MHz12µA
4.0V, CKI=0 MHz10µA
IDLE Current (Note 4)
CKI=10 MHzV
CKI=4 MHzV
=
CC
=
CC
5.5V, t
4.0V, t
=
1 µs1.2mA
c
=
2.5 µs1mA
c
Input Levels
RESET , CKI
Logic High0.8 V
Logic Low0.2 V
CC
CC
All Other Inputs (L0-L7, G0-G6, C0-C7, I0-I7)
Logic High0.7 V
Logic Low0.2 V
Hi-Z Input LeakageV
Input Pullup CurrentV
Note 2: t
Note 3: Maximum rate of voltage change must be
Note 4: Supply and IDLE currents are measured with CKI driven with a square wave Oscillator, CKO driven 180˚ out of phase with CKI, inputs connected to V
and outputs driven low but not connected to a load.
Note 5: The HALTmode will stop CKI from oscillating in the RC and the Crystal configurations by bringing CKI high. Measurement of I
neither sourcing nor sinking current; with L, C, G0, and G2–G5programmed as low outputs and not driving a load; all outputs programmed low and not driving a load;
all inputs tied to V
CKI during HALT in crystal clock mode.
Note 6: The user must guarantee that D2 pin does not source more than 10 mA during RESET. If D2 sources more than 10 mA during reset, the device will go into
programming mode.
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.
Instruction Cycle Time
c
CC
)
c
=
r
=
r
=
r
≤ 5.5V1.0DCµs
CC
≤ 5.5V3.0DCµs
CC
Max4060
10 MHz Ext Clock5ns
10 MHz Ext Clock5ns
4.5V ≤ VCC≤ 5.5V200ns
4.5V ≤ VCC≤ 5.5V60ns
=
L
Setup Time (t
; clock monitor and comparator disabled. Parameter refers to HALT mode entered via setting bit 7 of the G Port data register. Part will pull up
) (Note 9)20ns
UWS
) (Note 9)56ns
UWH
)220ns
UPD
<
0.5 V/ms.
<
14V.WARNING: Voltages in excess of 14V will cause damage to the pins. This warning excludes
=
2.2k, C
100 pF
L
≤ 5.5V1.0µs
CC
HALTis done with device
DD
>
VCCand the pins will have sink current to VCCwhen
%
c
c
c
c
CC
www.national.com5
A/D Converter Specifications
=
V
Resolution8Bits
Absolute Accuracy
Non-LinearityDeviation from the Best Straight Line
Differential Non-Linearity
Common Mode Input Range (Note 12)GNDV
DC Common Mode Error
Off Channel Leakage Current12µA
On Channel Leakage Current12µA
A/D Clock Frequency (Note 11)0.11.67MHz
Converison Time (Note 10)17A/D Clock Cycles
Internal Reference Resistance1µs
Tum-on Time (Note 13)
Note 10: Conversion Time includes 7 A/D clock cycles sample and hold time.
Note 11: See Prescaler description.
Note 12: For V
log input voltages below ground or above the V
diode to conduct — especially at elevated temperatures, and cause errors for analog inputs near full-scale. The spec allows 50 mV forward bias of either diode. This
means that as long as the analog V
V
Note 13: Time or internal reference reistance to turn on and settle after coming out of HALT or IDLE mode.
±
10%,(VSS–0.050V) ≤ Any Input ≤ (VCC+ 0.050V)
5V
CC
ParameterConditionsMinTypMaxUnits
±
2LSB
±
1LSB
±
1LSB
CC
±
1/2LSB
=
>
(−)
(+) the digital output code will be 0000 0000. Two on-chip diodes are tied to each analog input. The diodes will forward conduct for ana-
V
IN
IN
does not exceed the supply voltage by more than 50 mV, the output code will be correct. To achieve an absolute 0 VDCto 5
input voltage range will therefore require a minimum supply voltage of 4.950 VDCover temperature variations, initial tolerance and loading.
DC
IN
supply. Be careful, during testing at low VCClevels (4.5V), as high level analog inputs (5V) can cause this input
CC
V
FIGURE 3. MICROWIRE/PLUS Timing
www.national.com6
DS012526-4
Typical Performance Characteristics (−55˚C ≤ T
DS012526-22DS012526-23
A
=
+125˚C)
DS012526-24DS012526-25
DS012526-26
www.national.com7
Pin Descriptions
VCCand GND are the power supply pins. All VCCand GND
pins must be connected.
CKI is the clock input. This can come from an R/C generated
oscillator, or a crystal oscillator (in conjunction with CKO).
See Oscillator Description section.
RESET is the master reset input. See Reset Description section.
The device contains three bidirectional 8-bit I/O ports (C, G
and L), where each individual bit may be independently configured as an input (Schmitt Trigger inputs on ports Land 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 4
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:
CONFIGURATIONDATAPort Set-Up
RegisterRegister
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 Multi-Input Wake Up on all eight pins. L4 and
L5 are used for the timer input functions T2A and T2B. L6
and L7 are used for the timer input functions T3A and T3B.
Port L has the following alternate features:
L7MIWU or T3B
L6MIWU or T3A
L5MIWU or T2B
L4MIWU or T2A
L3MIWU
L2MIWU
L1MIWU
L0MIWU
Port G is an 8-bit port with 5 I/O pins (G0, G2–G5), an input
pin (G6), and a dedicated output pin (G7). Pins G0 and
G2–G6 all have Schmitt Triggers on their inputs. Pin G1
serves as the dedicated WDOUT WATCHDOGoutput, while
pin G7 is either input or output depending on the oscillator
mask option selected. With the crystal oscillator option selected, G7 serves as the dedicated output pin for the CKO
clock output. With the single-pin R/C oscillator mask option
selected, G7 serves as a general purpose input pin but is
also used to bring the device out of HALT mode with a low to
high transition on G7. There are two registers associated
with the G Port, a data register and a configuration register.
Therefore, each of the 5 I/O bits (G0, G2–G5) can be individually configured under software control.
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 clock option), the associated bits in the data and
(TRI-STATE Output)
configuration registers for G6 and G7 are used for special
purpose functions as outlined on the next page. Reading the
G6 and G7 data bits will return zeros.
DS012526-5
FIGURE 4. I/O Port Configurations
Note that the chip will be placed in the HALT mode by writing
a “1” to bit 7 of the Port G Data Register. Similarly the chip
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:
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)
G0 INTR (External Interrupt Input)
Port G has the following dedicated functions:
G7 CKO Oscillator dedicated output or general purpose
input
G1 WDOUT WATCHDOG and/or Clock Monitor dedi-
cated output
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 for these unterminated pins
will return unpredicatable values.
Port I is an 8-bit Hi-Z input port, andalso provides theanalog
inputs to the A/D converter. The 28-pin device does not have
a full complement of Port I pins. The unavailable pins are not
terminated (i.e. they are floating). A read operation from
these unterminated pins will return unpredictable values.
The user should ensure that the software takes this into account by either masking out these inputs, or else restricting
the accesses to bit operations only. If unterminated, Port I
pins will draw power only when addressed.
Port D is an 8-bit output port that ispreset high whenRESET
goes low. The user can tie two or more D port outputs (except D2) together in order to get a higher drive.
www.national.com8
Pin Descriptions (Continued)
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.8 V
keep the external loading on D2 to
to prevent the chip from entering special modes. Also
CC
<
1000 pF.
Functional Description
The architecture of the device is modified Harvard architecture. With the Harvard architecture, the control store 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 Harvard architecture, permits
transfer of data from ROM to RAM.
CPU REGISTERS
The CPU can do an 8-bit addition, subtraction, logical orshift
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.
SP is the 8-bit stack pointer, which points to the subroutine/
interrupt stack (in RAM). The SP is initialized to RAM address 06F with reset.
S is the 8-bit Data SegmentAddress Register used toextend
the lower half of the address range (00 to 7F) into 256 data
segments of 128 bytes each.
All the CPU registers are memory mapped with the exception of the Accumulator (A) and the Program Counter (PC).
PROGRAM MEMORY
The program memory consists of 16 or 32 kbytes of OTP
EPROM. 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 devices vector to
program memory location 0FF Hex.
The device can be configured to inhibit external reads of the
program memory. This is done by programming the Security
Byte.
SECURITY FEATURE
The program memory array has an associated Security Byte
that is located outside of the program address range. This
byte can be addressed only from programming mode by a
programmer tool.
Security is an optional feature and can only be assertedafter
the memory array has been programmed and verified. A secured part will read all 00(hex) by a programmer. The part
will fail Blank Check and will fail Verify operations. A Read
operation will fill the programmer’s memory with 00(hex).
The Security Byte itself is always readable with a value of
00(hex) if unsecure and FF(hex) if secure.
) cycle time.
c
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, SP pointers and S register.
The data memory consists of 256 bytes of RAM. Sixteen
bytes of RAM are mapped as “registers” at addresses 0F0 to
0FF 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,B and S are memory mapped into this space
at address locations 0FC to 0FF Hex respectively, with the
other registers 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
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.
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 5
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.
www.national.com9
Data Memory Segment RAM
Extension
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.
(Continued)
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 follow-
clock cycles. The Clock Monitor bit
C
ing 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,
–32 tCclock cycles following
C
at which time the G1 output will enter the TRI-STATE mode.
The external RC network shown in
Figure 6
should be used
to ensure that the RESET pin is held lowuntil the powersupply to the chip stabilizes.
*
Reads as all ones.
DS012526-6
FIGURE 5. RAM Organization
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
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 128 bytes of RAM
are memory mapped at address locations 0100 to 017F hex.
Reset
The RESET input when pulled low initializes the microcontroller. Initialization will occur whenever the RESET input is
pulled low. Upon initialization, the data and configuration
registers for ports L, G and C are cleared, resulting in these
Ports being initialized to the TRI-STATE mode. Pin G1 of the
G Port is an exception (as noted below) since pin G1 is dedicated as the WATCHDOGand/or Clock Monitor error output
pin. Port D is set high. The PC, PSW, ICNTRL, CNTRL,
T2CNTRL and T3CNTRL control registers are cleared. The
Comparator Select Register is cleared. The S register is initialized to zero. The Multi-Input Wakeupregisters WKEN and
WKEDG are cleared. Wakeup register WKPND is unknown.
The stack pointer, SP, is initialized to 6F hex.
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
RC>5 x Power Supply Rise Time
DS012526-7
FIGURE 6. Recommended Reset Circuit
Oscillator Circuits
The chip can be driven by a clock input on the CKI input pin
which can be between DC and 10 MHz. The CKO output
clock is on pin G7 (crystal configuration). The CKI input frequency is divided down by 10 to produce the instruction
cycle clock (1/t
Note: External clocks with frequencies above about 4 MHz require the user
to drive the CKO (G7) pin with a signal 180 degrees out of phase with
CKI.
Figure 7
CRYSTAL OSCILLATOR
CKI and CKO can be connected to make a closed loop crystal (or resonator) controlled oscillator.
Table 1
standard crystal values.
R/C OSCILLATOR
By selecting CKI as a single pin oscillator input, a single pin
R/C oscillator circuit can be connected to it. CKO is available
as a general purpose input, and/or HALT restart input.
Note: Use of the R/C oscillator option will result in higher electromagnetic
emissions.
Table 2
functions of the component (R and C) values.
).
c
shows the Crystal and R/C oscillator diagrams.
shows the component values required for various
shows the variation in the oscillator frequencies as
www.national.com10
Oscillator Circuits (Continued)
DS012526-8
DS012526-9
FIGURE 7. Crystal and R/C Oscillator Diagrams
=
TABLE 1. Crystal Oscillator Configuration, T
25˚C
A
R1R2C1C2CKI Freq Conditions
(kΩ)(MΩ) (pF)(pF)(MHz)
013030–3610V
013030–364V
01200 100–1500.455V
TABLE 2. RC Oscillator Configuration, T
=
5V
CC
=
5V
CC
=
5V
CC
=
25˚C
A
RCCKI FreqInstr. CycleConditions
(kΩ) (pF)(MHz)(µs)
3.3822.2 to 2.73.7 to 4.6V
5.61001.1 to 1.37.4 to 9.0V
6.81000.9 to 1.18.8 to 10.8V
Note 14: 3k ≤ R ≤ 200k
50 pF ≤ C ≤ 200 pF
=
5V
CC
=
5V
CC
=
5V
CC
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
IEDGExternal interrupt edge polarity select
signals SK and SO respectively
(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.
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
T3PNDA Timer T3 Interrupt Pending Flag (Autoreload
T3ENATimer T3 Interrupt Enable for Timer Underflow
T3PNDB Timer T3 Interrupt Pending Flag for T3B cap-
T3ENBTimer T3 Interrupt Enable for Timer Underflow
or T2B Input capture edge
modes 1 and 2, T3 Underflow Interrupt Pending Flag in timer mode 3
RA in mode 1, T3 Underflow in mode 2, T3A
capture edge in mode 3)
or T3A Input capture edge
ture edge
or T3B Input capture edge
Timers
The device contains a very versatile set of timers (T0, T1,
T2, T3). All timers and associated autoreload/capture registers power up containing random data.
TIMER T0 (IDLE TIMER)
The 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, which is a
16-bit timer. The Timer T0 runs continuously at the fixed rate
of the instruction cycle clock, t
write to the IDLE Timer T0, which is a count down timer.
The Timer T0 supports the following functions:
j
Exit out of the Idle Mode (See Idle Mode description)
j
WATCHDOG logic (See WATCHDOG description)
j
Start up delay out of the HALT mode
Figure 8
is a functional block diagram showing the structure
of the IDLE Timer and its associated interrupt logic.
. The user cannot read or
c
Bits 11 through 15 of the ITMR register can be selected for
triggering the IDLE Timer interrupt. Each time the selected
bit underflows (every 4k, 8k, 16k, 32k or 64k instruction
cycles), the IDLE Timer interrupt pending bit T0PND is set,
thus generating an interrupt (if enabled), and bit 6 of the Port
G data register is reset, thus causing an exit from the IDLE
mode if the device is in that mode.
In order for an interrupt to be generated, the IDLE Timer interrupt enable bit T0EN must be set, and the GIE (Global Interrupt Enable) bit must also be set. The T0PND flag and
T0EN bit are bits 5 and 4 of the ICNTRL register, respectively.The interrupt can be used for any purpose. Typically, it
is used to perform a task upon exit from the IDLE mode. For
more information on the IDLE mode, refer to the PowerSave
Modes section.
The Idle Timer period is selected by bits 0–2 of the ITMR
register Bits 3–7 of the ITMR Register are reserved and
should not be used as software flags.
TABLE 3. Idle Timer Window Length
ITSEL2ITSEL1ITSEL0Idle Timer Period
(Instruction Cycles)
0004,096
0018,192
01016,384
01132,768
1XX65,536
The ITMR is cleared on Reset and the Idle Timer period is reset to 4,096 instruction cycles.
ITMR Register (Address X’0xCF)
ReservedITSEL2ITSEL1 ITSEL0
Bit 7Bit 0
Any time the IDLE Timer period is changed there is the possibility of generating a spurious IDLE Timer interrupt by setting the T0PND bit. The user is advised to disable IDLE
Timer interrupts prior to changing the value of the ITSEL bits
of the ITMR Register and then clear the T0PND bit before attempting to synchronize operation to the IDLE Timer.
www.national.com12
Timers (Continued)
FIGURE 8. Functional Block Diagram for Idle Timer T0
TIMER T1, TIMER T2 AND TIMER T3
The device has a set of three powerful timer/counter blocks,
T1, T2 and T3. The associated features and functioning of a
timer block are described by referring to the timer block Tx.
Since the three timer blocks, T1, T2 and T3 are identical, all
comments are equally applicable to any of the three timer
blocks.
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 powerful
and flexible timer block allows the device to easily perform all
timer functions with minimal software overhead. 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.
Mode 1. Processor Independent PWM Mode
As the name suggests, this mode allows the device to generate a PWM signal with very minimal user intervention. The
user only has to define the parameters of the PWM signal
(ON time and OFF time). Once begun, the timer block will
continuously generate the PWM signal completely independent of the microcontroller. The user software services the
timer block only when the PWM parameters require updating.
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, RxAand 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.
The Tx Timer control bits, TxC3, TxC2 and TxC1 set up the
timer for PWM mode operation.
Figure 9
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.
.
c
DS012526-17
www.national.com13
Timers (Continued)
DS012526-10
FIGURE 9. Timer in PWM Mode
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 bythe input signal from theTxA 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.
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 10
Event Counter mode.
Note: The PWM output is not available in this mode since the TxApin is being
shows a block diagram of the timer in External
used as the counter input clock.
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 11
shows a block diagram of the timer in Input Cap-
ture mode.
DS012526-11
FIGURE 10. Timer in External Event Counter Mode
Mode 3. Input Capture Mode
The 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 timer Tx is constantly running at the fixed t
rate. The two registers, RxA and RxB, act as capture regis-
c
ters. 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,
www.national.com14
DS012526-12
FIGURE 11. Timer in Input Capture Mode
TIMER CONTROL FLAGS
The control bits and their functions are summarized below.
TxC3Timer mode control
TxC2Timer mode control
TxC1Timer mode control
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)
TxPNDA Timer Interrupt Pending Flag
TxENATimer Interrupt Enable Flag
1 = Timer Interrupt Enabled
0 = Timer Interrupt Disabled
TxPNDB Timer Interrupt Pending Flag
TxENBTimer Interrupt Enable Flag
1 = Timer Interrupt Enabled
0 = Timer Interrupt Disabled
Timers (Continued)
The timer mode control bits (TxC3, TxC2 and TxC1) are detailed below:
ModeTxC3TxC2TxC1Description
101PWM: TxA ToggleAutoreload RAAutoreload RBt
1
100PWM: No TxA
Toggle
000External Event
2
001External Event
Counter
Counter
010Captures:Pos. TxA EdgePos. TxB Edget
TxA Pos. Edgeor Timer
TxB Pos. EdgeUnderflow
110Captures:Pos. TxANeg. TxBt
TxA Pos. EdgeEdge or TimerEdge
3
011Captures:Neg. TxANeg. TxBt
TxB Neg. EdgeUnderflow
TxA Neg. EdgeEdge or TimerEdge
TxB Neg. EdgeUnderflow
111Captures:Neg. TxANeg. TxBt
TxA Neg. EdgeEdge or TimerEdge
TxB Neg. EdgeUnderflow
Power Save Modes
The 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 the WATCHDOG logic, the Clock Monitor 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.
HALT MODE
The device can be placed in the HALT mode by writing a “1”
to the HALT flag (G7 data bit). All microcontroller activities,
including the clock and timers, are stopped. The WATCHDOG logic is disabled during the HALT mode. However, the
clock monitor circuitry if enabled remains active and will
cause the WATCHDOGoutput pin (WDOUT) togo 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 device comes out of reset (resetting the Clock Monitor
control bit with the first write to the WDSVR register). In the
HALTmode, the power requirements of the device are minimal and the applied voltage (V
=
(V
2.0V) without altering the state of the machine.
r
The 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 the L port. 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
be used with an RC clock configuration. The third method of
exiting the HALT mode is by pulling the RESET pin low.
Since 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
) may be decreased to V
CC
r
Interrupt A
Source
Autoreload RAAutoreload RB
Timer
Underflow
Timer
Underflow
Interrupt B
Source
Timer
Counts On
C
t
C
Pos. TxB EdgePos. TxA
Edge
Pos. TxB EdgePos. TxA
Edge
C
C
C
C
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 10. 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 startup timeout from the
IDLE timer enables the clock signals to be routed to the rest
of the chip.
If an RC 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.
The device has two mask options associated with the HALT
mode. The first mask option enables the HALT mode feature,
while the second mask option disables the HALT mode. With
the HALT mode enable mask option, the device will enter
and exit the HALTmode as described above. With the HALT
disable mask option, the device cannot be placed in the
HALTmode (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.
c
www.national.com15
Power Save Modes (Continued)
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, the WATCHDOG
logic, the clock monitor and the IDLE Timer T0, are stopped.
The power supply requirements of the microcontroller in this
mode of operation are typically around 30%of normal power
requirement of the microcontroller.
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.
The microcontroller may also be awakened from the IDLE
mode after a selectable amount of time up to 65,536 instruction cycles, or 65.536 milliseconds with a 1 MHz instruction
clock frequency.
The IDLE timer period is selectable from one of five values,
4k, 8k, 16k, 32k or 64k instruction cycles. Selection of this
value is made through the ITMR register.
The user has the option of being interrupted with a transition
on the thirteenth 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.
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 Timer T0 interrupt disabled. In this case, the device will
resume normal operation with the instruction immediately
following the “Enter IDLE Mode” instruction.
The IDLE timer cannot be started or stopped under software
control, and it is not memory mapped, so itcannot be reador
written by the software. Its state upon Reset is unknown.
Therefore, if the device is put into the IDLE mode at an arbitrary time, it will stay in the IDLE mode for somewhere between 1 and the selected number of instruction cycles.
Upon reset the ITMR register is cleared and selects the
4,096 instruction cycle tap of the Idle Timer.
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.
For more information on the IDLE Timer and its associated
interrupt, see the description in the Timers Section.
Multi-Input Wakeup
The Multi-Input Wakeupfeature is ued 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 12
shows the Multi-Input Wakeup logic.
FIGURE 12. Multi-Input Wake Up Logic
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 Reg: WKEN. The Reg:
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.
www.national.com16
DS012526-13
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 Reg: 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
Multi-Input Wakeup (Continued)
selects the trigger condition to be a positive edge. Changing
an edge select entails several steps in order to avoid a
pseudo 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)
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 inherited pseudo
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
Multi-Input 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 HALTmode if any Wakeup bit is
both enabled and pending. Consequently, the user has the
responsibility of clearing the pending flags before attempting
to enter the HALT mode.
WKEN, WKPND and WKEDG are all read/write registers,
and are cleared at reset.
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 HALTor
IDLE modes either with or without the interrupt enabled. Ifhe
elects to disable the interrupt, then the device will restart execution from the instruction immediately following the instruction that placed the microcontroller in the HALTor 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.)
A/D Converter
The device contains an 8-channel, multiplexed input, successive approximation, Analog-to Digital converter. The device’s VCC and GND pins are used for voltage reference.
OPERATING MODES
The A/D converter supports ratiometric measurements. It
supports both Single Ended and Differential modes of operation.
Four specific analog channel selection modes are supported. These are as follows:
Allow any specific channel to be selected at one time. The
A/D converter performs the specific conversion requested
and stops.
Allow any specific channel to be scanned continuously. In
other words, the user specifies the channel and the A/D converter scans it continuously. At any arbitrary time the user
can immediately read the result of the last conversion. The
user must wait for only the first conversion to complete.
Allow any differential channel pair to be selected at onetime.
The A/D converter performs the specific differential conversion requested and stops.
Allow any differential channel pair to be scanned continuously.In other words, the user specifies the differentialchannel pair and the A/D converter scans it continuously. At any
arbitrary time the user can immediately read the result of the
last differential conversion. The user must wait for only the
first conversion to complete.
TheA/D converter is supported by two memory mapped registers, the result register and the mode control register.
When the device is reset, the mode control register (ENAD)
is cleared, the A/D is powered down and the A/D result register has unknown data.
A/D Control Register
The ENAD control register contains 3 bits for channel selection, 2 bits for prescaler selection, 2 bits for mode selection
and a Busy bit. An A/D conversion is initiated by setting the
ADBSY bit in the ENAD control register. The result of the
conversion is available to the user in the A/D result register,
ADRSLT, when ADBSY is cleared by the hardware on
completion of the conversion.
ENAD (Address 0xCB)
CHANNELMODEPRESCALERBUSY
SELECTSELECTSELECT
ADCH2 ADCH1 ADCH0 ADMOD1 ADMOD0 PSC1 PSC0 ADBSY
Bit 7Bit0
www.national.com17
A/D Converter (Continued)
CHANNEL SELECT
This 3-bit field selects one of eight channels to be the V
The mode selection determines the V
input.
IN−
Single Ended mode:
Bit 7Bit 6Bit 5Channel No.
0000
0011
0102
0113
1004
1015
1106
1117
Differential mode:
Bit 7Bit 6Bit 5Channel Pairs (+, −)
0000,1
0011,0
0102,3
0113,2
1004,5
1015,4
1106,7
1117,6
MODE SELECT
This 2-bit field is used to select themode of operation (single
conversion, continuous conversions, differential, single
ended) as shown in the following table.
Bit 4Bit 3Mode
00Single Ended mode, single
conversion
01Single Ended mode, continuous scan
of a single channel into the result
register
10Differential mode, single conversion
11Differential mode, continuous scan of
a channel pair into the result register
PRESCALER SELECT
This 2-bit field is used to select one of the four prescaler
clocks for the A/D converter. The following table shows the
various prescaler options.
A/D Converter Clock Prescale
Bit 2Bit 1Clock Select
00Divide by 2
01Divide by 4
10Divide by 6
11Divide by 12
BUSY BIT
The ADBSY bit of the ENAD register is used to control starting and stopping of the A/D conversion. When ADBSY is
cleared, the prescale logic is disabled and the A/D clock is
turned off. Setting the ADBSY bit starts the A/D clock and ini-
IN+
tiates a conversion based on the mode selectvalue currently
in the ENAD register. Normal completion of an A/D conversion clears the ADBSY bit and turns off the A/D converter.
.
TheADBSY bit remains a oneduring continuous conversion.
The user can stop continuous conversion by writing a zeroto
the ADBSY bit.
If the user wishes to restart a conversion which is already in
progress, this can be accomplished only by writing a zero to
the ADBSY bit to stop the current conversion and then by
writing a one to ADBSY to start a new conversion. This can
be done in two consecutive instructions.
ADC Operation
The A/D converter interface works as follows. Setting the
ADBSY bit in the A/D control register ENAD initiates an A/D
conversion. The conversion sequence starts at the beginning of the write to ENAD operation which sets ADBSY, thus
powering up the A/D. At the first falling edge of the converter
clock following the write operation, the sample signal turns
on for seven clock cycles. If the A/D is in single conversion
mode, the conversion complete signal from the A/D will generate a power down for the A/D converter and will clear the
ADBSY bit in the ENAD register at the next instruction cycle
boundary. If the A/D is in continuous mode, the conversion
complete signal will restart the conversion sequence by deselecting the A/D for one converter clock cycle before starting the next sample. The A/D 8-bit result is immediately
loaded into the A/D result register (ADRSLT) upon completion. Internal logic prevents transient data (resulting from the
A/D writing a new result over an old one) being read from
ADRSLT.
Inadvertent changes to the ENAD register during conversion
are prevented by the control logic of the A/D. Any attempt to
write any bit of the ENAD Register except ADBSY, while
ADBSY is a one, is ignored. ADBSY must be cleared either
by completion of an A/D conversion or by the user before the
prescaler, conversion mode or channel select values can be
changed.After stopping the current conversion, the user can
load different values for the prescaler, conversion mode or
channel select and start a new conversion in one instruction.
It is important for the user to realize that, when used in differential mode, only the positive input to the A/D converter is
sampled and held. The negative input is constantly connected and should be held stable for the duration of the conversion. Failure to maintain a stable negative input will result
in incorrect conversion.
PRESCALER
The A/D Converter (A/D) contains a prescaler option that allows four different clock selections. The A/D clock frequency
is equal to CKI divided by the prescaler value. Note that the
prescaler value must be chosen such that the A/D clock falls
within the specified range. The maximum A/D frequency is
1.67 MHz. This equates to a 600 ns A/D clock cycle.
www.national.com18
A/D Converter (Continued)
The A/D converter takes 17 A/D clock cycles to complete a
conversion. Thus the minimum A/D conversion time for the
device is 10.2 µs when a prescaler of 6 has been selected.
The 17 A/D clock cycles needed for conversion consist of 1
cycle at the beginning for reset, 7 cycles for sampling, 8
cycles for converting, and 1 cycle for loading the result into
theA/D result register (ADRSLT). ThisA/D result register isa
read-only register. The user cannot write into ADRSLT.
TheADBSY flag provides an A/D clock inhibit function, which
saves power by powering down theA/D when it is not in use.
Note: The A/D converter is also powered down when the device is in either
the HALT or IDLE modes. If the A/D is running when the device enters
the HALT or IDLE modes, the A/D powers down and then restarts the
conversion with a corrupted sampled voltage (and thus an invalid result) when the device comes out of the HALT or IDLE modes.
Analog Input and Source Resistance Considerations
Figure 13
The differential mode has a similar A/D pin model. The leads
to the analog inputs should be kept as short as possible.
Both noise and digital clock coupling to an A/D input can
shows the A/D pin model in single ended mode.
cause conversion errors. The clock lead should be kept
away from the analog input line to reduce coupling. The A/D
channel input pins do not have any internal output driver circuitry connected to them because this circuitry would load
the analog input signals due to output buffer leakage current.
Source impedances greater than 3 kΩ on the analog input
lines will adversely affect the internal RC charging time during input sampling. As shown in
Figure 13
, the analog switch
to the DAC array is closed only during the 7 A/D cycle
sample time. Large source impedances on the analog inputs
may result in the DAC array not being charged to the correct
voltage levels, causing scale errors.
If large source resistance is necessary, the recommended
solution is to slow down the A/D clock speed in proportion to
the source resistance. The A/D converter may be operated
at the maximum speed for R
than 3 kΩ, A/D clock speed needs to be reduced. For example, with R
at half the maximum speed. A/D converter clock speed may
=
6kΩ, the A/D converter may be operated
S
less than 3 kΩ. For RSgreater
S
be slowed down by either increasing the A/D prescaler
divide-by or decreasing the CKI clock frquency. The A/D
minimum clock speed is 100 kHz.
*
The analog switch is closed only during the sample time.
FIGURE 13. A/D Pin Model (Single Ended Mode)
Interrupts
INTRODUCTION
Each device supports eleven 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.
DS012526-18
The Software trap has the highest priority while the default
VIS has the lowest priority.
Each of the 11 maskable inputs has a fixed arbitration ranking and vector.
Figure 14
shows the Interrupt Block Diagram.
www.national.com19
Interrupts (Continued)
FIGURE 14. Interrupt Block Diagram
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 acknowl-
DS012526-14
edged 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 isautomatically 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.
www.national.com20
Interrupts (Continued)
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.
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.
Table4
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 example, 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
servicing of another interrupt. Rather than restoring the program context (A, B, X, etc.) and executing the RETI instruction, an interrupt service routine can be terminatedby 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 interrupts 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.
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.
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 remains unchanged. The new PC is therefore pointing to the
vector of the active interrupt with the highestarbitration 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 15
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.com24
Interrupts (Continued)
NON-MASKABLE INTERRUPT
Pending Flag
There is a pending flag bit associated withthe 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.
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 lastlocation 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 thattriggered
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.
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 HALTor
IDLE modes either with or without the interrupt enabled. Ifhe
elects to disable the interrupt, then the device will restart execution from the instruction immediately following the instruction that placed the microcontroller in the HALTor 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.)
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.com25
WATCHDOG
The device contains a WATCHDOG and clock monitor. The
WATCHDOG is designed to detect the user program getting
stuck in infinite loops resulting in loss of program control or
“runaway” programs. 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 5
shows the WDSVR register.
TABLE 5. WATCHDOG Service Register (WDSVR)
WindowKey DataClock
SelectMonitor
X X 01100Y
7 6 543210
The lower limit of the service window is fixed at 2048 instruction cycles. Bits 7 and 6 of the WDSVR register allow the
user to pick an upper limit of the service window.
Table 6
shows the four possible combinations of lower and
upper limits for the WATCHDOG service window. This flexibility in choosing the WATCHDOG service 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 6. 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
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 input
c
rate on CKI of greater or equal to 100 kHz.
WATCHDOG Operation
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 7
shows the sequence of
events that can occur.
The user must service the WATCHDOGat 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 user may service the
WATCHDOG as many times as wished in the time period between the lower and upper limits of the service window. The
first write to the WDSVR Register is also counted as a
WATCHDOG service.
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.The WDOUT pin is in the high impedancestate in theinactive state. Upon triggering the WATCHDOG, the logic will
pull the WDOUT (G1) pin low for an additional 16 t
cycles after the signal level on WDOUT pin goes below the
–32t
c
lower Schmitt trigger threshold. After this delay, the device
will stop forcing the WDOUT output low.
The WATCHDOG service window will restart when the WDOUT pin goes high. It is recommended that the user tie the
WDOUT pin back to V
WDOUT high.
through a resistor in order to pull
CC
AWATCHDOGservice while the WDOUTsignal 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 enter high impedance state.
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 enter the high impedance TRI-STATE mode following 16 t
The Clock Monitor generates a continual Clock Monitor error
–32 tcclock cycles.
c
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
WATCHDOG AND CLOCK MONITOR SUMMARY
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.
c
www.national.com26
WATCHDOG Operation (Continued)
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 mask 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 mask option selected, or with
•
the single-pin R/C oscillator mask option selected and the
CLKDLYbit 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 2048 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 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 thirteenth 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 2048 instruction
cycles following IDLE, but must be serviced within theselected window to avoid a WATCHDOG error.
Following RESET,the initial WATCHDOGservice (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 2048 instruction cycles without causing a WATCHDOG error.
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 zeros. The opcode for software interrupt is zero. If the program fetches instructions
from undefined ROM, this will force a softwareinterrupt, 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 location06F 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), 140 to 17F (Segment 1),
and all other segments (i.e., Segments 2 … etc.) is read as
all 1’s, which in turn will cause the program to return to address 7FFF Hex. This is an undefined ROM location and the
instruction fetched (all 0’s) from this location will 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).
MICROWIRE/PLUS
MICROWIRE/PLUS is a serial synchronous communications
interface. The MICROWIRE/PLUS capabilityenables the device to interface with any of National Semiconductor’s MICROWIRE peripherals (i.e. A/D converters, display drivers,
2
E
PROMs etc.) and with other microcontrollers which support the MICROWIRE 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).
diagram of the MICROWIRE/PLUS logic.
FIGURE 17. MICROWIRE/PLUS Block Diagram
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.
clock rates that may be selected.
Figure 17
Table8
details the different
shows a block
DS012526-15
www.national.com27
MICROWIRE/PLUS (Continued)
TABLE 7. WATCHDOG Service Actions
KeyWindowClockAction
DataDataMonitor
MatchMatchMatchValid Service: Restart Service Window
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.
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
low. Loading the SIO register while the SK clock is high will
result in undefined data in the SIO register. SK clock is normally low when not shifting.
Setting the BUSY flag when the input SK clock is high in the
MICROWIRE/PLUS 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 low.
MICROWIRE/PLUS Master Mode Operation
In the MICROWIRE/PLUS Master mode of operation the
shift clock (SK) is generated internally by the device.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.
bit settings required for Master mode of operation.
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
c
c
c
Figure 18
Table 9
shows how
summarizes the
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 9
summarizes the settings required to enter the
Slave mode of operation.
The user must set the BUSY flag immediately upon entering
the Slave mode. This will ensure that all data bits sent by the
Master will be shifted properly. After eight clock pulses the
BUSY flag will be cleared and the sequence may be repeated.
Alternate SK Phase Operation
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 is normally low. In the 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. The
SIO register is shifted on each 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.
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 9. MICROWIRE/PLUS Mode Settings
This table assumes that the control flag MSEL is set.
G4 (SO)G5 (SK)G4G5Operation
Config. BitConfig. BitFun.Fun.
11SOInt.MICROWIRE/PLUS
01TRI-Int. MICROWIRE/PLUS
10SOExt. MICROWIRE/PLUS
00TRI-Ext. MICROWIRE/PLUS
SKMaster
STATESKMaster
SKSlave
STATESKSlave
www.national.com28
MICROWIRE/PLUS (Continued)
FIGURE 18. MICROWIRE/PLUS Application
DS012526-16
www.national.com29
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 xxAFUnused RAM 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 (CMPSL)
xxB8 to xxBFReserved
xxC0Timer T2 Lower Byte
xxC1Timer T2 Upper Byte
xxC2Timer T2 Autoload Register T2RA
Lower Byte
xxC3Timer T2 Autoload Register T2RA
Upper Byte
xxC4Timer T2 Autoload Register T2RB
Lower Byte
xxC5Timer T2 Autoload Register T2RB
Upper Byte
xxC6Timer T2 Control Register
xxC7WATCHDOG Service Register
(Reg:WDSVR)
xxC8MIWU Edge Select Register
(Reg:WKEDG)
xxC9MIWU Enable Register (Reg:WKEN)
xxCAMIWU Pending Register (Reg:WKPND)
xxCBReserved
xxCCReserved
xxCD to xxCFReserved
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)
xxD8Port C Data Register
xxD9Port C Configuration Register
AddressContents
S/ADD REG
xxDAPort C Input Pins (Read Only)
xxDBReserved for Port C
xxDCPort D
xxDD to xxDFReserved
xxE0 to xxE5Reserved
xxE6Timer T1 Autoload Register T1RB
Upper Byte
xxEECNTRL Control Register
xxEFPSW Register
xxF0 to FBOn-Chip RAM, Mapped as Registers
xxFCX Register
xxFDSP Register
xxFEB Register
xxFFS Register
0100 to 017FOn-Chip RAM, 128 Bytes
Reading memory locations 0070H–007FH (Segment 0) will return all ones.
Reading unused memory locations 0080H–00AFH (Segment 0) will return
undefined data. Reading memory locations from other unused Segments
(i.e., Segment 2, Segment 3, … etc.) will return undefined data.
www.national.com30
Addressing Modes
There are ten addressing modes, six for operand addressing
and four for transfer of control.
OPERAND ADDRESSING MODES
Register Indirect
This is the “normal” addressing mode. The operand is the
data memory addressed by the B pointer or X pointer.
Register Indirect (with auto post increment or
decrement of pointer)
This addressing mode is used with the LD and X instructions. The operand is the data memory addressed by the B
pointer or X pointer. This is a register indirect mode that automatically post increments or decrements the B or X register after executing the instruction.
Direct
The instruction contains an 8-bit address field that directly
points to the data memory for the operand.
Immediate
The instruction contains an 8-bit immediate field as the operand.
Short Immediate
This addressing mode is used with the Load B Immediate instruction. The instruction contains a 4-bit immediate field as
the operand.
Indirect
This addressing mode is used with the LAID instruction. The
contents of the accumulator are used as a partial address
(lower 8 bits of PC) for accessing a data operand from the
program memory.
TRANSFER OF CONTROL ADDRESSING MODES
Relative
This mode is used for the JP instruction, with the instruction
field being added to the program counter to get the new program location. JP has a range from −31 to +32 to allow a
1-byte relative jump (JP + 1 is implemented by a NOP instruction). There are no “pages” when using JP, since all 15
bits of PC are used.
Absolute
This mode is used with the JMP and JSR instructions, with
the instruction field of 12 bits replacing the lower 12 bits of
the program counter (PC). This allows jumping to any location in the current 4k program memory segment.
Absolute Long
This mode is used with the JMPL and JSRL instructions, with
the instruction field of 15 bits replacing the entire 15 bits of
the program counter (PC). This allows jumping to any location up to 32k in the program memory space.
Indirect
This mode is used with the JID instruction. The contents of
the accumulator are used as a partial address (lower 8 bits of
PC) for accessing a location in the program memory. The
contents of this program memory location serve as a partial
address (lower 8 bits of PC) for the jump to the next instruction.
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.
Instruction Set
Register and Symbol Definition
Registers
A8-Bit Accumulator Register
B8-Bit Address Register
X8-Bit Address Register
S8-Bit Segment Register
SP8-Bit Stack Pointer Register
PC15-Bit Program Counter Register
PUUpper 7 Bits of PC
PLLower 8 Bits of PC
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
Symbols
Immediate Data
(Includes B, X and SP)
Loaded with
Exchanged with
www.national.com31
Instruction Set (Continued)
INSTRUCTION SET
ADDA,MemlADDA←A + Meml
ADCA,MemlADD with CarryA←A+Meml+C,C←Carry
HC←Half Carry
SUBCA,MemlSubtract with CarryA←A−MemI+C,C←Carry
HC←Half 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 ImmedMem←Imm
LDReg,ImmLoaD Register Memory Immed.Reg←Imm
XA,[B
XA,[X
LDA, [B
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
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)
#
#
,MemSet BIT1 to bit, Mem (bit=0 to 7 immediate)
#
,MemReset BIT0 to bit, Mem
#
,MemIF BITIf bit in A or Mem is true do next instruction
±
±
±
],ImmLoaD Memory [B] Immed.[B]←Imm, (B←B±1)
If B Not EqualDo next if lower 4 bits of B≠Imm
↔
Mem
↔
[X]
±
]EXchange A with Memory [B]A↔[B], (B←B±1)
±
]EXchange A with Memory [X]A↔[X], (X←X±1)
]LoaD A with Memory [B]A←[B], (B←B±1)
]LoaD A with Memory [X]A←[X], (X←X±1)
↔
A3…A0
≠
>
Meml
Meml
www.national.com32
Instruction Set (Continued)
INSTRUCTION SET (Continued)
JSRLAddr.Jump SubRoutine Long[SP]←PL, [SP−1]←PU,SP−2, PC←ii
JSRAddrJump 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
www.national.com33
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.
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:
www.national.com34
>
Memory location addressed by B or X or directly.
<
16)
>
15)
Upper Nibble
JP+17 INTR 0
JMP
x000–x0FF
x000–x0FF
IFBNE 0JSR
LD
B,#0F
A, #i
ANDSZ
0,[B]
IFBIT
JP+18 JP+2 1
JMP
x100–x1FF
x100–x1FF
IFBNE 1JSR
B,#0E
*LD
1,[B]
IFBIT
JP+19 JP+3 2
JP+20 JP+4 3
JMP
JMP
x200–x2FF
x200–x2FF
IFBNE 2JSR
IFBNE 3JSR
B,#0D
*LD
*LD
2,[B]
IFBIT
IFBIT
JP+21 JP+5 4
JMP
x300–x3FF
x300–x3FF
IFBNE 4JSR
B,#0C
CLRALD
3,[B]
IFBIT
x400–x4FF
x400–x4FF
B,#0B
4,[B]
JP+22 JP+6 5
JMP
IFBNE 5JSR
SWAPALD
IFBIT
JP+23 JP+7 6
JMP
x500–x5FF
x500–x5FF
IFBNE 6JSR
B,#0A
DCORALD
5,[B]
IFBIT
x600–x6FF
x600–x6FF
B,#09
6,[B]
JP+24 JP+8 7
JMP
x700–x7FF
x700–x7FF
IFBNE 7JSR
B,#08
PUSHALD
7,[B]
IFBIT
JP+25 JP+9 8
JMP
IFBNE 8JSR
LD
RBIT
x800–x8FF
x800–x8FF
B,#07
0,[B]
0,[B]
Lower Nibble
JP+26 JP+10 9
JMP
IFBNE 9JSR
LD
RBIT
x900–x9FF
x900–x9FF
B,#06
1,[B]
1,[B]
JP+27 JP+11 A
JMP
IFBNE 0AJSR
LD
RBIT
xA00–xAFF
xA00–xAFF
B,#05
2,[B]
2,[B]
JP+28 JP+12 B
JMP
IFBNE 0BJSR
LD
RBIT
xB00–xBFF
xB00–xBFF
B,#04
3,[B]
3,[B]
JP+29 JP+13 C
JMP
IFBNE 0CJSR
LD
RBIT
JP+30 JP+14 D
JMP
xC00–xCFF
xC00–xCFF
IFBNE 0DJSR
LD
B,#03
4,[B]
RBIT
4,[B]
xD00–xDFF
xD00–xDFF
B,#02
5,[B]
5,[B]
JP+31 JP+15 E
JMP
IFBNE 0EJSR
LD
RBIT
xE00–xEFF
xE00–xEFF
B,#01
6,[B]
6,[B]
JP+32 JP+16 F
JMP
IFBNE 0FJSR
LD
RBIT
xF00–xFFF
xF00–xFFF
B,#00
7,[B]
7,[B]
Opcode Table
ADC
RRCARCADC
F E D C BA9 876 5 432 10
JP−15 JP−31 LD 0F0, #i DRSZ
A,[B]
A,#i
0F0
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, #iDRSZ
A,[B]
**OR A,#iOR
0F7
JP−8JP−24 LD 0F7, #iDRSZ
NOPRLCA LD A,#iIFCSBIT
0F8
JP−7JP−23 LD 0F8, #iDRSZ
IFNCSBIT
A,#i
IFNE
IFEQ
Md,#i
A,[B]
IFNE
0F9
JP−6JP−22 LD 0F9, #iDRSZ
INCASBIT
LD
[B+],#i
LD
A,[B+]
LD
A,[X+]
0FA
JP−5JP−21 LD 0FA, #i DRSZ
DECA SBIT
LD
[B−],#i
LD
A,[B−]
LD
A,[X−]
0FB
JP−4JP−20 LD 0FB, #i DRSZ
JMPL X A,Md POPASBIT
LD
Md,#i
0FC
JP−3JP−19 LD 0FC, #i DRSZ
RETSK SBIT
A,Md
DIRJSRLLD
0FD
JP−2JP−18 LD 0FD, #i DRSZ
RETSBIT
LD
[B],#i
LD
A,[B]
LD
A,[X]
0FE
JP−1JP−17 LD 0FE, #i DRSZ
**LD B,#i RETISBIT
0FF
JP−0JP−16 LD 0FF, #i DRSZ
www.national.com35
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
Development Tools Support
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
solutions 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.
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-NSDEV: Very low cost Software Development
•
Package for Windows. An integrated development environment for COP8, including WCOP8 IDE, COP8NSASM, COP8-MLSIM.
™
COP8, Manuals, and other COP8
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.
COP8-MLSIM: Free Instruction Level Simulator tool for
•
Windows. For testing and debugging software instructions only (No I/O or interrupt support).
www.national.com36
Development Tools Support
(Continued)
COP8 Real-Time Emulation Tools
COP8-DM: MetaLink Debug Module. A moderately
•
priced real-time in-circuit emulation tool, with COP8 device programmer. Includes COP8-NSDEV, DriveWay
COP8 Demo, MetaLink Debugger, power supply, emulation cables and adapters.
IM-COP8: MetaLink iceMASTER®. A full featured, real-
•
time in-circuit emulator for COP8 devices. Includes MetaLink Windows Debugger, and power supply. Packagespecific probes and surface mount adaptors are ordered
separately.
TOOLS ORDERING NUMBERS FOR THE COP87L88GD FAMILY DEVICES
VendorToolsOrder NumberCostNotes
National COP8-NSEVALCOP8-NSEVALFreeWeb site download
COP8-NSASMCOP8-NSASMFreeIncluded 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-EPUNot available for this device
COP8-DMContact MetaLink
Development
Devices
IM-COP8Contact MetaLink
MetaLink COP8-EPUNot available for this device
COP8-DMDM4-COP8-888GD (10
DM Target
Adapters
IM-COP8IM-COP8-AD-464 (-220)
IM Probe CardPC-888GD40DW-AD-10M10 MHz 40 DIP probe card; 2.5V to 6.0V
ICUCOP8-EVALNot available for this device
KKDWCOP8-IDEWCOP8-IDEVLIncluded in EPU and DM
IAREWCOP8-xxSee summary aboveL - H Included all software and manuals
Byte
COP8CCOP8CMIncluded all software and manuals
Craft
AisysDriveWay COP8DriveWay COP8LIncluded all software and manuals
OTP ProgrammersContact vendorsL - H For approved programmer listings and vendor
Cost: Free; VL =
<
$100; L = $100 - $300; M = $300 - $1k; H = $1k - $3k; VH = $3k - $5k
COP87L84GD/RDVL16k or 32k OTP devices.
MHz), plus PS-10, plus
DM-COP8/xxx (ie. 28D)
MHW-CONV39LDM target converters for 28SO
(10 MHz maximum)
PC-888GD44PW-AD-10M10 MHz 44 PLCC probe card; 2.5V to 6.0V
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.
MIncluded p/s (PS-10), target cable of choice (DIP or
PLCC; i.e. DM-COP8/40D), 16/20/28/40 DIP/SO and
44 PLCC programming sockets. Add target adapter (if
needed)
HBase unit 10 MHz; -220 = 220V; add probe card
(required) and target adapter (if needed); included
software and manuals
information, go to our OTP support page at:
www.national.com/cop8
www.national.com37
Development Tools Support (Continued)
WHERE TO GET TOOLS
Tools are ordered directly from the following vendors. Please go to the vendor’s web site for current listings of distributors.
VendorHome OfficeElectronic SitesOther Main Offices
AisysU.S.A.: Santa Clara, CAwww.aisysinc.comDistributors
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.
COP87L88GD/RD Family 8-Bit CMOS OTP Microcontrollers with 16k or 32k Memory and
8-Channel A/D with Prescaler
Order Number COP87L88RDV-XE or COP87L88GDV-XE
Plastic Leaded Chip Carrier (V)
NS Package Number V44A
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.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.