Professional Documents
Culture Documents
Nuvoton 1T 8051-Based Microcontroller
Nuvoton 1T 8051-Based Microcontroller
N76E003
Datasheet
TABLE OF CONTENTS
1. GENERAL DESCRIPTION ............................................................................................................................... 5
2. FEATURES ....................................................................................................................................................... 6
3. BLOCK DIAGRAM............................................................................................................................................ 9
4. PIN CONFIGURATION ................................................................................................................................... 10
5. MEMORY ORGANIZATION ........................................................................................................................... 17
5.1 Program Memory .................................................................................................................................... 17
5.2 Data Memory .......................................................................................................................................... 19
5.3 On-Chip XRAM ....................................................................................................................................... 21
5.4 Non-Volatile Data Storage ...................................................................................................................... 21
6. SPECIAL FUNCTION REGISTER (SFR) ....................................................................................................... 22
6.1 ALL SFR DESCRIPTION ........................................................................................................................ 27
7. I/O PORT STRUCTURE AND OPERATION .................................................................................................. 85
7.1 Quasi-Bidirectional Mode ........................................................................................................................ 85
7.2 Push-Pull Mode....................................................................................................................................... 86
7.3 Input-Only Mode ..................................................................................................................................... 87
7.4 Open-Drain Mode ................................................................................................................................... 87
7.5 Read-Modify-Write Instructions .............................................................................................................. 88
7.6 Control Registers of I/O Ports ................................................................................................................. 88
7.6.1 Input and Output Data Control ..................................................................................................... 89
7.6.2 Output Mode Control .................................................................................................................... 90
7.6.3 Input Type .................................................................................................................................... 92
7.6.4 Output Slew Rate Control ............................................................................................................ 94
8. TIMER/COUNTER 0 AND 1 ............................................................................................................................ 96
8.1 Mode 0 (13-Bit Timer) ............................................................................................................................. 99
8.2 Mode 1 (16-Bit Timer) ........................................................................................................................... 100
8.3 Mode 2 (8-Bit Auto-Reload Timer) ........................................................................................................ 100
8.4 Mode 3 (Two Separate 8-Bit Timers) ................................................................................................... 101
9. TIMER 2 AND INPUT CAPTURE ................................................................................................................. 103
9.1 Auto-Reload Mode ................................................................................................................................ 107
9.2 Compare Mode ..................................................................................................................................... 108
9.3 Input Capture Module ........................................................................................................................... 108
10. TIMER 3 ...................................................................................................................................................... 114
11. WATCHDOG TIMER (WDT) ....................................................................................................................... 116
11.1 Time-Out Reset Timer ........................................................................................................................ 118
11.2 General Purpose Timer ...................................................................................................................... 119
12. SELF WAKE-UP TIMER (WKT) ................................................................................................................. 121
13. SERIAL PORT (UART) ............................................................................................................................... 123
13.1 Mode 0 ................................................................................................................................................ 128
13.2 Mode 1 ................................................................................................................................................ 129
13.3 Mode 2 ................................................................................................................................................ 130
13.4 Mode 3 ................................................................................................................................................ 131
13.5 Baud Rate ........................................................................................................................................... 132
13.6 Framing Error Detection ..................................................................................................................... 135
13.7 Multiprocessor Communication .......................................................................................................... 135
13.8 Automatic Address Recognition.......................................................................................................... 136
14. SERIAL PERIPHERAL INTERFACE (SPI) ................................................................................................ 140
14.1 Functional Description ........................................................................................................................ 140
14.2 Operating Modes ................................................................................................................................ 146
1. GENERAL DESCRIPTION
The N76E003 is an embedded flash type, 8-bit high performance 1T 8051-based microcontroller. The
instruction set is fully compatible with the standard 80C51 and performance enhanced.
The N76E003 contains a up to 18K Bytes of main Flash called APROM, in which the contents of User
Code resides. The N76E003 Flash supports In-Application-Programming (IAP) function, which
enables on-chip firmware updates. IAP also makes it possible to configure any block of User Code
array to be used as non-volatile data storage, which is written by IAP and read by IAP or MOVC
instruction. There is an additional Flash called LDROM, in which the Boot Code normally resides for
carrying out In-System-Programming (ISP). The LDROM size is configurable with a maximum of 4K
Bytes. To facilitate programming and verification, the Flash allows to be programmed and read
electronically by parallel Writer or In-Circuit-Programming (ICP). Once the code is confirmed, user can
lock the code for security.
The N76E003 provides rich peripherals including 256 Bytes of SRAM, 768 Bytes of auxiliary RAM
(XRAM), Up to 18 general purpose I/O, two 16-bit Timers/Counters 0/1, one 16-bit Timer2 with three-
channel input capture module, one Watchdog Timer (WDT), one Self Wake-up Timer (WKT), one 16-
bit auto-reload Timer3 for general purpose or baud rate generator, two UARTs with frame error
2
detection and automatic address recognition, one SPI, one I C, five enhanced PWM output channels,
eight-channel shared pin interrupt for all I/O, and one 12-bit ADC. The peripherals are equipped with
18 sources with 4-level-priority interrupts capability.
The N76E003 is equipped with three clock sources and supports switching on-the-fly via software. The
three clock sources include external clock input, 10 kHz internal oscillator, and one 16 MHz internal
precise oscillator that is factory trimmed to ±1% at room temperature. The N76E003 provides
additional power monitoring detection such as power-on reset and 4-level brown-out detection, which
stabilizes the power-on/off sequence for a high reliability system design.
The N76E003 microcontroller operation consumes a very low power with two economic power modes
to reduce power consumption - Idle and Power-down mode, which are software selectable. Idle
mode turns off the CPU clock but allows continuing peripheral operation. Power-down mode stops the
whole system clock for minimum power consumption. The system clock of the N76E003 can also be
slowed down by software clock divider, which allows for a flexibility between execution performance
and power consumption.
With high performance CPU core and rich well-designed peripherals, the N76E003 benefits to meet a
general purpose, home appliances, or motor control system accomplishment.
2. FEATURES
CPU:
Operating:
Memory:
– Additional 768 Bytes on-chip auxiliary RAM (XRAM) accessed by MOVX instruction.
Clock sources:
– 16 MHz high-speed internal oscillator trimmed to ±1% when VDD 5.0V, ±2% in all conditions.
Peripherals:
– Up to 17 general purpose I/O pins and one input-only pin. All output pins have individual 2-level
slew rate control.
– One 16-bit Timer 2 with three-channel input capture module and 9 input pin can be selected.
– One 16-bit auto-reload Timer 3, which can be the baud rate clock source of UARTs.
– One programmable Watchdog Timer (WDT) clocked by dedicated 10 kHz internal source.
– One dedicated Self Wake-up Timer (WKT) for self-timed wake-up for power reduced modes.
– Two full-duplex UART ports with frame error detection and automatic address recognition. TXD
and RXD pins of UART0 exchangeable via software.
– One SPI port with master and slave modes, up to 8 Mbps when system clock is 16 MHz.
2
– One I C bus with master and slave modes, up to 400 kbps data rate.
– Three pairs, six channels of pulse width modulator (PWM) output, 10 output pins can be
selected., up to 16-bit resolution, with different modes and Fault Brake function for motor
control.
– Eight channels of pin interrupt, shared for all I/O ports, with variable configuration of edge/level
detection.
– One 12-bit ADC, up to 500 ksps converting rate, hardware triggered and conversion result
compare facilitating motor control.
Power management:
Power monitor:
– Brown-out detection (BOD) with low power mode available, 4-level selection, interrupt or reset
options.
Development Tools:
TM
– Nuvoton On-Chip-Debugger (OCD) with KEIL development environment.
3. BLOCK DIAGRAM
Figure 3.1 shows the N76E003 functional block diagram and gives the outline of the device. User can
find all the peripheral functions of the device in the diagram.
Timer 2 9
Max. 4K Bytes IC0~IC7
with
LDROM Flash (P1.5, P1[2:0], P0.0, P0.1, P0[5:3])
Input Capture
Timer 3
8 MOSI (P0.0)
P1[7:0] MISO (P0.1)
P1 SPI
SS (P1.5)
SPCLK (P1.0)
1 10 PWM0~PWM5
[1]
P20 P2 (P1.5, P1.4, P1.2, P1.1, P1.0, P0.0,
PWM P0.1, P0[3:5])
FB (P1.4)
[2]
1
P30 P3
External Interrupt INT0 (P3.0)
INT1 (P1.7)
8
Pin Interrupt Any Port
Watchdog Timer
8
AIN0~7 (P1.7, P3.0, P0[7:3], P0.1)
12-bit ADC
STADC (P1.3 or P0.4)
System Clock
Power
Managment
4. PIN CONFIGURATION
PWM2/IC6/T0/AIN4/P0.5 1 20 P0.4/AIN5/STADC/PWM3/IC3
TXD/AIN3/P0.6 2 19 P0.3/PWM5/IC5/AIN6
RXD/AIN2/P0.7 3 18 P0.2/ICPCK/OCDCK/RXD_1/[SCL]
RST/P2.0 4 17 P0.1/PWM4/IC4/MISO
INT0/OSCIN/AIN1/P3.0 5 16 P0.0/PWM3/IC3/MOSI/T1
N76E003AT20
INT1/AIN0/P1.7 6 15 P1.0/PWM2/IC2/SPCLK
GND 7 14 P1.1/PWM1/IC1/AIN7/CLO
[SDA]/TXD_1/ICPDA/OCDDA/P1.6 8 13 P1.2/PWM0/IC0
VDD 9 12 P1.3/SCL/[STADC]
PWM5/IC7/SS/P1.5 10 11 P1.4/SDA/FB/PWM1
1. [ ] alternate function remapping option (if the same alternate function is shown twice, it indicates an exclusive choice not a duplication of the
function).
PWM2/IC6/T0/AIN4/P0.5 1 20 P0.4/AIN5/STADC/PWM3/IC3
TXD/AIN3/P0.6 2 19 P0.3/PWM5/IC5/AIN6
RXD/AIN2/P0.7 3 18 P0.2/ICPCK/OCDCK/RXD_1/[SCL]
RST/P2.0 4 17 P0.1/PWM4/IC4/MISO
INT0/OSCIN/AIN1/P3.0 5 16 P0.0/PWM3/IC3/MOSI/T1
N76E003AS20
INT1/AIN0/P1.7 6 15 P1.0/PWM2/IC2/SPCLK
GND 7 14 P1.1/PWM1/IC1/AIN7/CLO
[SDA]/TXD_1/ICPDA/OCDDA/P1.6 8 13 P1.2/PWM0/IC0
VDD 9 12 P1.3/SCL/[STADC]
PWM5/IC7/SS/P1.5 10 11 P1.4/SDA/FB/PWM1
1. [ ] alternate function remapping option (if the same alternate function is shown twice, it indicates an exclusive choice not a duplication of the
function).
P0.2/ICPCK/OCDCK/RXD_1/[SCL]
P0.0/PWM3/IC3/MOSI/T1
P0.1/PWM4/IC4/MISO
P0.3/PWM5/IC5/AIN6
P1.3/SCL/[STADC]
15 14 13 12 11
AIN5/STADC/PWM3/IC3/P0.4 16 10 P1.4/SDA/FB/PWM1
INT0/OSCIN/AIN1/P3.0 17 9 P1.2/PWM0/IC0
RST/P2.0 18 N76E003AQ20 8 P1.1/PWM1/IC1/AIN7/CLO
TXD/AIN3/P0.6 19 7 P1.0/PWM2/IC2/SPCLK
PWM2/IC6/T0/AIN4/P0.5 20 6 P1.5/PWM5/IC7/SS
1 2 3 4 5
RXD/AIN2/P0.7
INT1/AIN0/P1.7
GND
VDD
[SDA]/TXD_1/ICPDA/OCDDA/P1.6
1. [ ] alternate function remapping option (if the same alternate function is shown twice, it indicates an exclusive choice not a
duplication of the function).
P0.2/ICPCK/OCDCK/RXD_1/[SCL]
P1.1/PWM1/IC1/AIN7/CLO
P0.0/PWM3/IC3/MOSI/T1
P1.0/PWM2/IC2/SPCLK
P0.1/PWM4/IC4/MISO
15 14 13 12 11
PWM5/IC5/AIN6/P0.3 16 10 P1.2/PWM0/IC0
AIN5/STADC/PWM3/IC3/P0.4 17 9 P1.3/SCL/[STADC]
PWM2/IC6/T0/AIN4/P0.5 18 N76E003BQ20 8 P1.4/SDA/FB/PWM1
TXD/AIN3/P0.6 19 7 P1.5/PWM5/IC7/SS
RXD/AIN2/P0.7 20 6 VDD
1 2 3 4 5
RST/P2.0
INT0/OSCIN/AIN1/P3.0
INT1/AIN0/P1.7
GND
[SDA]/TXD_1/ICPDA/OCDDA/P1.6
1. [ ] alternate function remapping option (if the same alternate function is shown twice, it indicates an exclusive choice not a
duplication of the function).
P0.2/ICPCK/OCDCK/RXD_1/[SCL]
P1.1/PWM1/IC1/AIN7/CLO
P0.0/PWM3/IC3/MOSI/T1
P1.0/PWM2/IC2/SPCLK
P0.1/PWM4/IC4/MISO
15 14 13 12 11
PWM5/IC5/AIN6/P0.3 16 10 P1.2/PWM0/IC0
AIN5/STADC/PWM3/IC3/P0.4 17 9 P1.3/SCL/[STADC]
PWM2/IC6/T0/AIN4/P0.5 18 N76E003CQ20 8 P1.4/SDA/FB/PWM1
TXD/AIN3/P0.6 19 7 P1.5/PWM5/IC7/SS
RXD/AIN2/P0.7 20 6 VDD
1 2 3 4 5
RST/P2.0
INT0/OSCIN/AIN1/P3.0
INT1/AIN0/P1.7
GND
[SDA]/TXD_1/ICPDA/OCDDA/P1.6
1. [ ] alternate function remapping option (if the same alternate function is shown twice, it indicates an exclusive choice not a
duplication of the function).
Pin Number
N76E003AT2 N76E003BQ2
Symbol Multi-Function Description[1]
0 N76E003AQ2 0
N76E003AS2 0 N76E003CQ2
0 0
Pin Number
N76E003AT2 N76E003BQ2
Symbol Multi-Function Description[1]
0 N76E003AQ2 0
N76E003AS2 0 N76E003CQ2
0 0
5. MEMORY ORGANIZATION
A standard 80C51 based microcontroller divides the memory into two different sections, Program
Memory and Data Memory. The Program Memory is used to store the instruction codes, whereas the
Data Memory is used to store data or variations during the program execution.
The Data Memory occupies a separate address space from Program Memory. In N76E003, there are
256 Bytes of internal scratch-pad RAM. For many applications those need more internal RAM, the
N76E003 provides another on-chip 768 Bytes of RAM, which is called XRAM, accessed by MOVX
instruction.
The whole embedded flash, functioning as Program Memory, is divided into three blocks: Application
ROM (APROM) normally for User Code, Loader ROM (LDROM) normally for Boot Code, and CONFIG
bytes for hardware initialization. Actually, APROM and LDROM function in the same way but have
different size. Each block is accumulated page by page and the page size is 128 Bytes. The flash
control unit supports Erase, Program, and Read modes. The external writer tools though specific I/O
pins, In-Application-Programming (IAP), or In-System-Programming (ISP) can both perform these
modes.
The Program Memory stores the program codes to execute as shown in Figure 5.1. After any reset,
the CPU begins execution from location 0000H.
To service the interrupts, the interrupt service locations (called interrupt vectors) should be located in
the Program Memory. Each interrupt is assigned with a fixed location in the Program Memory. The
interrupt causes the CPU to jump to that location with where it commences execution of the interrupt
service routine (ISR). External Interrupt 0, for example, is assigned to location 0003H. If External
Interrupt 0 is going to be used, its service routine should begin at location 0003H. If the interrupt is not
going to be used, its service location is available as general purpose Program Memory.
The interrupt service locations are spaced at an interval of eight Bytes: 0003H for External Interrupt 0,
000BH for Timer 0, 0013H for External Interrupt 1, 001BH for Timer 1, etc. If an interrupt service
routine is short enough (as is often the case in control applications), it can reside entirely within the 8-
Byte interval. However longer service routines should use a JMP instruction to skip over subsequent
interrupt locations if other interrupts are in use.
The N76E003 provides two internal Program Memory blocks APROM and LDROM. Although they
both behave the same as the standard 8051 Program Memory, they play different rules according to
their ROM size. The APROM on N76E003 can be up to 18K Bytes. User Code is normally put inside.
CPU fetches instructions here for execution. The MOVC instruction can also read this region.
The other individual Program Memory block is called LDROM. The normal function of LDROM is to
store the Boot Code for ISP. It can update APROM space and CONFIG bytes. The code in APROM
can also re-program LDROM. For ISP details and configuration bit setting related with APROM and
LDROM, see Section 21.4 “In-System-Programming (ISP)” on page 225. Note that APROM and
LDROM are hardware individual blocks, consequently if CPU re-boots from LDROM, CPU will
automatically re-vector Program Counter 0000H to the LDROM start address. Therefore, CPU
accounts the LDROM as an independent Program Memory and all interrupt vectors are independent
from APROM.
CONFIG1
7 6 5 4 3 2 1 0
- - - - - LDSIZE[2:0]
- - - - - R/W
Factory default value: 1111 1111b
37FFH/
3BFFH/
3FFFH/
43FFH/
47FFH[1]
APROM
0FFFH/
0BFFH/
07FFH/
03FFH/
0000H[1] LDROM
0000H 0000H
BS = 0 BS = 1
[1] The logic boundary addresses of APROM and LDROM are defined
by CONFIG1[2:0].
Figure 5.2 shows the internal Data Memory spaces available on N76E003. Internal Data Memory
occupies a separate address space from Program Memory. The internal Data Memory can be divided
into three blocks. They are the lower 128 Bytes of RAM, the upper 128 Bytes of RAM, and the 128
Bytes of SFR space. Internal Data Memory addresses are always 8-bit wide, which implies an address
space of only 256 Bytes. Direct addressing higher than 7FH will access the special function registers
(SFRs) space and indirect addressing higher than 7FH will access the upper 128 Bytes of RAM.
Although the SFR space and the upper 128 Bytes of RAM share the same logic address, 80H through
FFH, actually they are physically separate entities. Direct addressing to distinguish with the higher 128
Bytes of RAM can only access these SFRs. Sixteen addresses in SFR space are either byte-
addressable or bit-addressable. The bit-addressable SFRs are those whose addresses end in 0H or
8H.
The lower 128 Bytes of internal RAM are present in all 80C51 devices. The lowest 32 Bytes as
general purpose registers are grouped into 4 banks of 8 registers. Program instructions call these
registers as R0 to R7. Two bits RS0 and RS1 in the Program Status Word (PSW[3:4]) select which
Register Bank is used. It benefits more efficiency of code space, since register instructions are shorter
than instructions that use direct addressing. The next 16 Bytes above the general purpose registers
(byte-address 20H through 2FH) form a block of bit-addressable memory space (bit-address 00H
through 7FH). The 80C51 instruction set includes a wide selection of single-bit instructions, and the
128 bits in this area can be directly addressed by these instructions. The bit addresses in this area are
00H through 7FH.
Either direct or indirect addressing can access the lower 128 Bytes space. But the upper 128 Bytes
can only be accessed by indirect addressing.
Another application implemented with the whole block of internal 256 Bytes RAM is used for the stack.
This area is selected by the Stack Pointer (SP), which stores the address of the top of the stack.
Whenever a JMP, CALL or interrupt is invoked, the return address is placed on the stack. There is no
restriction as to where the stack can begin in the RAM. By default however, the Stack Pointer contains
07H at reset. User can then change this to any value desired. The SP will point to the last used value.
Therefore, the SP will be incremented and then address saved onto the stack. Conversely, while
popping from the stack the contents will be read first, and then the SP is decreased.
FFH 02FFH
Upper 128 Bytes
SFR
internal RAM
(direct addressing)
(indirect addressing)
80H
7FH Lower 128 Bytes
internal RAM 768 Bytes XRAM
(direct or indirect (MOVX addressing)
00H addressing)
0000H
FFH FFH
The N76E003 provides additional on-chip 768 bytes auxiliary RAM called XRAM to enlarge the RAM
space. It occupies the address space from 00H through 2FFH. The 768 bytes of XRAM are indirectly
accessed by move external instruction MOVX @DPTR or MOVX @Ri. (See the demo code below.)
Note that the stack pointer cannot be located in any part of XRAM.
By applying IAP, any page of APROM or LDROM can be used as non-volatile data storage. For IAP
details, please see Section 21. “In-Application-Programming (IAP)” on page 219.
The N76E003 uses Special Function Registers (SFRs) to control and monitor peripherals and their
modes. The SFRs reside in the register locations 80 to FFH and are accessed by direct addressing
only. SFRs those end their addresses as 0H or 8H are bit-addressable. It is very useful in cases where
user would like to modify a particular bit directly without changing other bits via bit-field instructions. All
other SFRs are byte-addressable only. The N76E003 contains all the SFRs presenting in the standard
8051. However some additional SFRs are built in. Therefore, some of unused bytes in the original
8051 have been given new functions. The SFRs are listed below.
To accommodate more than 128 SFRs in the 0x80 to 0Xff address space, SFR paging has been
implemented. By default, all SFR accesses target SFR page 0. During device initialization, some
SFRs located on SFR page 1 may need to be accessed. The register SFRS is used to switch SFR
addressing page. Note that this register has TA write protection. Most of SFRs are available on both
SFR page 0 and 1.
Unoccupied addresses in the SFR space marked in “-“ are reserved for future use. Accessing
these areas will have an indeterminate effect and should be avoided.
Bits marked in “-“ are reserved for future use. They must be kept in their own initial states.
Accessing these bits may cause an unpredictable effect.
Following list all SFR description. For each SFR define also list in function IP chapter.
P0 – Port 0 (Bit-addressable)
7 6 5 4 3 2 1 0
P0.7 P0.6 P0.5 P0.4 P0.3 P0.2 P0.1 P0.0
R/W R/W R/W R/W R/W R/W R/W R/W
Address: 80H Reset value: 1111 1111b
SP – Stack Pointer
7 6 5 4 3 2 1 0
SP[7:0]
R/W
Address: 81H Reset value: 0000 0111b
P1 – Port 1 (Bit-addressable)
7 6 5 4 3 2 1 0
P1.7 P1.6 P1.5 P1.4 P1.3 P1.2 P1.1 P1.0
R/W R/W R/W R/W R/W R/W R/W R/W
Address: 90H Reset value: 1111 1111b
P2 – Port 2 (Bit-addressable)
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 P2.0
R R R R R R R R
Address: A0H Reset value: 0000 000Xb
Note: If MCU run in OCD debug mode and OCDEN = 0, hard fault reset will be
disabled and only HardF flag be asserted.
[1] BODEN, BOV[1:0], and BORST are initialized by being directly loaded from CONFIG2 bit 7,
[6:4], and 2 after all resets.
[2] BOF reset value depends on different setting of CONFIG2 and V DD voltage level. Please check
Table 24-1.
P3 – Port 3 (Bit-addressable)
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 P3.0
R R R R R R R R/W
Address: B0H Reset value: 0000 0001b
0 0 Quasi-bidirectional
0 1 Push-pull
1 0 Input-only (high-impedance)
1 1 Open-drain
2
I2DAT – I C Data
7 6 5 4 3 2 1 0
I2DAT[7:0]
R/W
Address: BCH Reset value: 0000 0000b
2
I2STAT – I C Status
7 6 5 4 3 2 1 0
I2STAT[7:3] 0 0 0
R R R R
Address: BDH Reset value: 1111 1000b
2
I2CLK – I C Clock
7 6 5 4 3 2 1 0
I2CLK[7:0]
R/W
Address: BEH Reset value: 0000 1001b
2
I2TOC – I C Time-out Counter
7 6 5 4 3 2 1 0
- - - - - I2TOCEN DIV I2TOF
- - - - - R/W R/W R/W
Address: BFH Reset value: 0000 0000b
2
I2CON – I C Control (Bit-addressable)
7 6 5 4 3 2 1 0
- I2CEN STA STO SI AA - I2CPX
- R/W R/W R/W R/W R/W - R/W
Address: C0H Reset value: 0000 0000b
2
I2ADDR – I C Own Slave Address
7 6 5 4 3 2 1 0
I2ADDR[7:1] GC
R/W R/W
Address: C1H Reset value: 0000 0000b
TA – Timed Access
7 6 5 4 3 2 1 0
TA[7:0]
W
Address: C7H Reset value: 0000 0000b
Instruction CY OV AC Instruction CY OV AC
[1]
ADD X X X CLR C 0
ADDC X X X CPL C X
SUBB X X X ANL C, bit X
MUL 0 X ANL C, /bit X
DIV 0 X ORL C, bit X
DA A X ORL C, /bit X
RRC A X MOV C, bit X
RLC A X CJNE X
SETB C 1
[1] X indicates the modification depends on the result of the instruction.
B – B Register (Bit-addressable)
7 6 5 4 3 2 1 0
B.7 B.6 B.5 B.4 B.3 B.2 B.1 B.0
R/W R/W R/W R/W R/W R/W R/W R/W
Address: F0H Reset value: 0000 0000b
Notice: Strongly suggests that disable POR function after power-on reset at the initial part of
Customer code. Please reference 24.1 Power-On Reset (POR) for more detail information.
The N76E003 has a maximum of 26 bit-addressable general I/O pins grouped as 4 ports, P0 to P3.
Each port has its port control register (Px register). The writing and reading of a port control register
have different meanings. A write to port control register sets the port output latch logic value, whereas
a read gets the port pin logic state. All I/O pins except P2.0 can be configured individually as one of
four I/O modes by software. These four modes are quasi-bidirectional (standard 8051 port structure),
push-pull, input-only, and open-drain modes. Each port spends two special function registers PxM1
and PxM2 to select the I/O mode of port Px. The list below illustrates how to select the I/O mode of
Px.n. Note that the default configuration of is input-only (high-impedance) after any reset except the
OCDDA and OCDCK pin, this two pins keep quasi mode with pull high resister about 600 LIRC clock
before change to input mode after reset
0 0 Quasi-bidirectional
0 1 Push-pull
1 0 Input-only (high-impedance)
1 1 Open-drain
All I/O pins can be selected as TTL level inputs or Schmitt triggered inputs by selecting corresponding
bit in PxS register. Schmitt triggered input has better glitch suppression capability. All I/O pins also
have bit-controllable, slew rate select ability via software. The control registers are PxSR. By default,
the slew rate is slow. If user would like to increase the I/O output speed, setting the corresponding bit
in PxSR, the slew rate is selected in a faster level.
P2.0 is configured as an input-only pin when programming RPD (CONFIG0.2) as 0. Meanwhile, P2.0
is permanent in input-only mode and Schmitt triggered type. P2.0 also has an internal pull-up enabled
by P20UP (P2S.7). If RPD remains un-programmed, P2.0 pin functions as an external reset pin and
P2.0 is not available. A read of P2.0 bit is always 0. Meanwhile, the internal pull-up is always enabled.
The quasi-bidirectional mode, as the standard 8051 I/O structure, can rule as both input and output.
When the port outputs a logic high, it is weakly driven, allowing an external device to pull the pin low.
When the pin is pulled low, it is driven strongly and able to sink a large current. In the quasi-
bidirectional I/O structure, there are three pull-high transistors. Each of them serves different
purposes. One of these pull-highs, called the “very weak” pull-high, is turned on whenever the port
latch contains logic 1. he “very weak” pull-high sources a very small current that will pull the pin high
if it is left floating.
A second pull-high, called the “weak” pull-high, is turned on when the outside port pin itself is at logic 1
level. This pull-high provides the primary source current for a quasi-bidirectional pin that is outputting
1. If a pin which has logic 1 on it is pulled low by an external device, the “weak” pull-high turns off, and
only the “very weak” pull-high remains on. To pull the pin low under these conditions, the external
device has to sink enough current (larger than ITL) to overcome the “weak” pull-high and make the
voltage on the port pin below its input threshold (lower than VIL).
The third pull-high is the “strong” pull-high. This pull-high is used to speed up 0-to-1 transitions on a
quasi-bidirectional port pin when the port latch changes from logic 0 to logic 1. When this occurs, the
strong pull-high turns on for two-CPU-clock time to pull the port pin high quickly. Then it turns off and
“weak” and “very weak” pull-highs continue remaining the port pin high. The quasi-bidirectional port
structure is shown below.
VDD
2-CPU-clock P P P
Very
delay Strong Weak
Weak
Port Pin
N
Port Latch
Input
The push-pull mode has the same pull-low structure as the quasi-bidirectional mode, but provides a
continuous strong pull-high when the port latch is written by logic 1. The push-pull mode is generally
used as output pin when more source current is needed for an output driving.
VDD
P Strong
Port Pin
N
Port Latch
Input
Input-only mode provides true high-impedance input path. Although a quasi-bidirectional mode I/O can
also be an input pin, but it requires relative strong input source. Input-only mode also benefits to power
consumption reduction for logic 0 input always consumes current from VDD if in quasi-bidirectional
mode. User needs to take care that an input-only mode pin should be given with a determined voltage
level by external devices or resistors. A floating pin will induce leakage current especially in Power-
down mode.
The open-drain mode turns off all pull-high transistors and only drives the pull-low of the port pin when
the port latch is given by logic 0. If the port latch is logic 1, it behaves as if in input-only mode. To be
2
used as an output pin generally as I C lines, an open-drain pin should add an external pull-high,
typically a resistor tied to VDD. User needs to take care that an open-drain pin with its port latch as
logic 1 should be given with a determined voltage level by external devices or resistors. A floating pin
will induce leakage current especially in Power-down mode.
Port Pin
N
Port Latch
Input
nstructions that read a byte from F or internal A , modify it, and rewrite it back, are called “ ead-
Modify-Write” instructions. When the destination is an O port or a port bit, these instructions read the
internal output latch rather than the external pin state. This kind of instructions read the port SFR
value, modify it and write back to the port SFR. All “Read-Modify-Write” instructions are listed as
follows.
Instruction Description
ANL Logical AND. (ANL direct, A and ANL direct, #data)
ORL Logical OR. (ORL direct, A and ORL direct, #data)
XRL Logical exclusive OR. (XRL direct, A and XRL direct, #data)
JBC Jump if bit = 1 and clear it. (JBC bit, rel)
CPL Complement bit. (CPL bit)
INC Increment. (INC direct)
DEC Decrement. (DEC direct)
DJNZ Decrement and jump if not zero. (DJNZ direct, rel)
MOV bit, C Move carry to bit. (MOV bit, C)
CLR bit Clear bit. (CLR bit)
SETB bit Set bit. (SETB bit)
The last three seem not obviously “ ead-Modify-Write” instructions but actually they are. They read
the entire port latch value, modify the changed bit, and then write the new value back to the port latch.
The N76E003 has a lot of I/O control registers to provide flexibility in all kinds of applications. The
SFRs related with I/O ports can be categorized into four groups: input and output control, output mode
control, input type and sink current control, and output slew rate control. All of SFRs are listed as
follows.
These registers are I/O input and output data buffers. Reading gets the I/O input data. Writing forces
the data output. All of these registers are bit-addressable.
P0 – Port 0 (Bit-addressable)
7 6 5 4 3 2 1 0
P0.7 P0.6 P0.5 P0.4 P0.3 P0.2 P0.1 P0.0
R/W R/W R/W R/W R/W R/W R/W R/W
Address: 80H Reset value: 1111 1111b
P1 – Port 1 (Bit-addressable)
7 6 5 4 3 2 1 0
P1.7 P1.6 P1.5 P1.4 P1.3 P1.2 P1.1 P1.0
R/W R/W R/W R/W R/W R/W R/W R/W
Address: 90H Reset value: 1111 1111b
P2 – Port 2 (Bit-addressable)
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 P2.0
R R R R R R R R
Address: A0H Reset value: 0000 000Xb
P3 – Port 3 (Bit-addressable)
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 P3.0
R R R R R R R R/W
Address: B0H Reset value: 0000 0001b
These registers control output mode which is configurable among four modes: input-only, quasi-
bidirectional, push-pull, or open-drain. Each pin can be configured individually. There is also a pull-up
control for P2.0 in P2S.7.
0 0 Quasi-bidirectional
0 1 Push-pull
1 0 Input-only (high-impedance)
1 1 Open-drain
0 0 Quasi-bidirectional
0 1 Push-pull
1 0 Input-only (high-impedance)
1 1 Open-drain
Each I/O pin can be configured individually as TTL input or Schmitt triggered input. Note that all of PxS
registers are accessible by switching SFR page to page 1.
Slew rate for each I/O pin is configurable individually. By default, each pin is in normal slew rate mode.
User can set each control register bit to enable high-speed slew rate for the corresponding I/O pin.
Note that all PxSR registers are accessible by switching SFR page to page 1.
8. TIMER/COUNTER 0 AND 1
Timer/Counter 0 and 1 on N76E003 are two 16-bit Timers/Counters. Each of them has two 8-bit
registers those form the 16-bit counting register. For Timer/Counter 0 they are TH0, the upper 8-bit
register, and TL0, the lower 8-bit register. Similarly Timer/Counter 1 has two 8-bit registers, TH1 and
TL1. TCON and TMOD can configure modes of Timer/Counter 0 and 1.
The Timer or Counter function is selected by the ̅ bit in TMOD. Each Timer/Counter has its own
selection bit. TMOD.2 selects the function for Timer/Counter 0 and TMOD.6 selects the function for
Timer/Counter 1
When configured as a “Timer”, the timer counts the system clock cycles. The timer clock is 1/12 of the
system clock (FSYS) for standard 8051 capability or direct the system clock for enhancement, which is
selected by T0M (CKCON.3) bit for Timer 0 and T1M (CKCON.4) bit for Timer 1. In the “Counter”
mode, the countering register increases on the falling edge of the external input pin T0. If the sampled
value is high in one clock cycle and low in the next, a valid 1-to-0 transition is recognized on T0 or T1
pin.
The Timers 0 and 1 can be configured to automatically toggle a port output whenever a timer overflow
occurs. The same device pins that are used for the T0 and T1 count inputs are also used for the timer
toggle outputs. This function is enabled by control bits T0OE and T1OE in the P2S register, and apply
to Timer 0 and Timer 1 respectively. The port outputs will be logic 1 prior to the first timer overflow
when this mode is turned on. In order for this mode to function, the ̅ bit should be cleared selecting
Note that the TH0 (TH1) and TL0 (TL1) are accessed separately. It is strongly recommended that in
mode 0 or 1, user should stop Timer temporally by clearing TR0 (TR1) bit before reading from or
writing to TH0 (TH1) and TL0 (TL1). The free-running reading or writing may cause unpredictable
result.
In Mode 0, the Timer/Counter is a 13-bit counter. The 13-bit counter consists of TH0 (TH1) and the
five lower bits of TL0 (TL1). The upper three bits of TL0 (TL1) are ignored. The Timer/Counter is
enabled when TR0 (TR1) is set and either GATE is 0 or ̅̅̅̅̅̅̅ (̅̅̅̅̅̅̅) is 1. Gate setting as 1 allows the
Timer to calculate the pulse width on external input pin ̅̅̅̅̅̅̅ (̅̅̅̅̅̅̅). When the 13-bit value moves
from 1FFFH to 0000H, the Timer overflow flag TF0 (TF1) is set and an interrupt occurs if enabled.
T0M (CKCON.3)
(T1M (CKCON.4))
1/12
0
FSYS C/T
1
0
1
TL0 (TL1)
T0 (T1) pin
0 4 7
TF0
0 7 Timer Interrupt
TR0 (TR1) (TF1)
TH0 (TH1)
GATE T0 (T1) pin
T0OE (P2S.2)
INT0 (INT1) pin (T1OE(P2S.3))
Mode 1 is similar to Mode 0 except that the counting registers are fully used as a 16-bit counter. Roll-
over occurs when a count moves FFFFH to 0000H. The Timer overflow flag TF0 (TF1) of the relevant
Timer/Counter is set and an interrupt will occurs if enabled.
T0M (CKCON.3)
(T1M (CKCON.4))
1/12
0
FSYS C/T
1
0
1
TL0 (TL1)
T0 (T1) pin 0 7
TF0
0 7 Timer Interrupt
TR0 (TR1) (TF1)
TH0 (TH1)
GATE T0 (T1) pin
T0OE (P2S.2)
INT0 (INT1) pin (T1OE(P2S.3))
In Mode 2, the Timer/Counter is in auto-reload mode. In this mode, TL0 (TL1) acts as an 8-bit count
register whereas TH0 (TH1) holds the reload value. When the TL0 (TL1) register overflow, the TF0
(TF1) bit in TCON is set and TL0 (TL1) is reloaded with the contents of TH0 (TH1) and the counting
process continues from here. The reload operation leaves the contents of the TH0 (TH1) register
unchanged. This feature is best suitable for UART baud rate generator for it runs without continuous
software intervention. Note that only Timer1 can be the baud rate source for UART. Counting is
enabled by setting the TR0 (TR1) bit as 1 and proper setting of GATE and ̅̅̅̅̅̅̅ (̅̅̅̅̅̅̅) pins. The
functions of GATE and ̅̅̅̅̅̅̅ (̅̅̅̅̅̅̅) pins are just the same as Mode 0 and 1.
T0M (CKCON.3)
(T1M (CKCON.4))
1/12
0
FSYS C/T
1
0
1
TL0 (TL1)
T0 (T1) pin TF0
0 7 Timer Interrupt
(TF1)
T0 (T1) pin
T0OE (P2S.2)
TR0 (TR1) (T1OE(P2S.3))
0 7
GATE TH0 (TH1)
INT0 (INT1) pin
Mode 3 has different operating methods for Timer 0 and Timer 1. For Timer/Counter 1, Mode 3 simply
freezes the counter. Timer/Counter 0, however, configures TL0 and TH0 as two separate 8 bit count
registers in this mode. TL0 uses the Timer/Counter 0 control bits ̅, GATE, TR0, ̅̅̅̅̅̅̅, and TF0.
The TL0 also can be used as a 1-to-0 transition counter on pin T0 as determined by ̅ (TMOD.2).
TH0 is forced as a clock cycle counter and takes over the usage of TR1 and TF1 from Timer/Counter
1. Mode 3 is used in case that an extra 8 bit timer is needed. If Timer/Counter 0 is configured in Mode
3, Timer/Counter 1 can be turned on or off by switching it out of or into its own Mode 3. It can still be
used in Modes 0, 1 and 2 although its flexibility is restricted. It no longer has control over its overflow
flag TF1 and the enable bit TR1. However Timer 1 can still be used as a Timer/Counter and retains
the use of GATE, ̅̅̅̅̅̅̅ pin and T1M. It can be used as a baud rate generator for the serial port or
other application not requiring an interrupt.
T0M (CKCON.3)
1/12
0
FSYS C/T
1
0
1
TL0
T0 pin
0 7 TF0 Timer 0 Interrupt
T0 pin
T0OE (P2S.2)
TR0
GATE
T1 pin
T1OE(P2S.3)
Timer 2 is a 16-bit up counter cascaded with TH2, the upper 8 bits register, and TL2, the lower 8 bit
register. Equipped with RCMP2H and RCMP2L, Timer 2 can operate under compare mode and auto-
reload mode selected by ̅̅̅̅̅̅ (T2CON.0). An 3-channel input capture module makes Timer 2
detect and measure the width or period of input pulses. The results of 3 input captures are stores in
C0H and C0L, C1H and C1L, C2H and C2L individually. The clock source of Timer 2 is from the
system clock pre-scaled by a clock divider with 8 different scales for wide field application. The clock is
enabled when TR2 (T2CON.2) is 1, and disabled when TR2 is 0. The following registers are related to
Timer 2 function.
C0L C0H
CAPF0
CAPF1 CMPCR
CAPF2 Clear
Clear Timer 2 (T2MOD.2)
[1]
CAPCR Counter
(T2MOD.3)
Clear Timer 2
00
CAPF0
CAPF1
01
10
=
CAPF2 11 LDEN[1]
LDTS[1:0] (T2MOD.7)
(T2MOD[1:0])
RCMP2L RCMP2H
Timer 2 Module
[1] Once CAPCR and LDEN are both set, an input capture event only clears TH2 and TL2 without reloading RCMP2H and RCMP2L contents.
The Timer 2 is configured as auto-reload mode by clearing ̅̅̅̅̅̅ . In this mode RCMP2H and
RCMP2L registers store the reload value. The contents in RCMP2H and RCMP2L transfer into TH2
and TL2 once the auto-reload event occurs if setting LDEN bit. The event can be the Timer 2 overflow
or one of the triggering event on any of enabled input capture channel depending on the LDTS[1:0]
(T2MOD[1:0]) selection. Note that once CAPCR (T2MOD.3) is set, an input capture event only clears
TH2 and TL2 without reloading RCMP2H and RCMP2L contents.
C0L C0H
CAPF0
CAPF1
CAPF2
CAPCR[1]
(T2MOD.3)
Clear Timer 2
FSYS Pre-scalar
TL2 TH2 TF2 Timer 2 Interrupt
T2DIV[2:0] TR2
(T2MOD[6:4]) (T2CON.2)
00
CAPF0 01
CAPF1 10
CAPF2 11 LDEN[1]
LDTS[1:0] (T2MOD.7)
(T2MOD[1:0])
RCMP2L RCMP2H
Timer 2 Module
[1] Once CAPCR and LDEN are both set, an input capture event only clears TH2 and TL2 without reloading RCMP2H and RCMP2L contents.
Figure 9.2. Timer 2 Auto-Reload Mode and Input Capture Module Functional Block Diagram
Timer 2 can also be configured as the compare mode by setting ̅̅̅̅̅̅. In this mode RCMP2H and
RCMP2L registers serve as the compare value registers. As Timer 2 up counting, TH2 and TL2 match
RCMP2H and RCMP2L, TF2 (T2CON.7) will be set by hardware to indicate a compare match event.
Setting CMPCR (T2MOD.2) makes the hardware to clear Timer 2 counter as 0000H automatically
after a compare match has occurred.
C0L C0H
CMPCR
(T2MOD.2)
Clear Timer 2
FSYS Pre-scalar
TL2 TH2
T2DIV[2:0] TR2
(T2MOD[6:4]) (T2CON.2)
= TF2 Timer 2 Interrupt
RCMP2L RCMP2H
Timer 2 Module
Figure 9.3. Timer 2 Compare Mode and Input Capture Module Functional Block Diagram
The input capture module along with Timer 2 implements the input capture function. The input capture
module is configured through CAPCON0~2 registers. The input capture module supports 3-channel
inputs (CAP0, CAP1, and CAP2) that share 9 I/O pins (P1.5, P1[2:0], P0.0, P0.1 and P0[5:3]). The pin
mux select through CAPCON3 and CAPCON4. Each input channel consists its own noise filter, which
is enabled via setting ENF0~2 (CAPCON2[6:4]). It filters input glitches smaller than four system clock
cycles. Input capture channels has their own independent edge detector but share the unique Timer
2. Each trigger edge detector is selected individually by setting corresponding bits in CAPCON1. It
supports positive edge capture, negative edge capture, or any edge capture. Each input capture
channel has to set its own enabling bit CAPEN0~2 (CAPCON0[6:4]) before use.
While input capture channel is enabled and the selected edge trigger occurs, the content of the free
running Timer 2 counter, TH2 and TL2, will be captured, transferred, and stored into the capture
registers CnH and CnL. The edge triggering also causes CAPFn (CAPCON0.n) set by hardware. The
interrupt will also generate if the ECAP (EIE.2) and EA bit are both set. For three input capture flags
share the same interrupt vector, user should check CAPFn to confirm which channel comes the input
capture edge. These flags should be cleared by software.
The bit CAPCR (CAPCON2.3) benefits the implement of period calculation. Setting CAPCR makes the
hardware clear Timer 2 as 0000H automatically after the value of TH2 and TL2 have been captured
after an input capture edge event occurs. It eliminates the routine software overhead of writing 16-bit
counter or an arithmetic subtraction.
10. TIMER 3
Timer 3 is implemented simply as a 16-bit auto-reload, up-counting timer. The user can select the pre-
scale with T3PS[2:0] (T3CON[2:0]) and fill the reload value into RH3 and RL3 registers to determine
its overflow rate. User then can set TR3 (T3CON.3) to start counting. When the counter rolls over
FFFFH, TF3 (T3CON.4) is set as 1 and a reload is generated and causes the contents of the RH3 and
RL3 registers to be reloaded into the internal 16-bit counter. If ET3 (EIE1.1) is set as 1, Timer 3
interrupt service routine will be served. TF3 is auto-cleared by hardware after entering its interrupt
service routine.
Timer 3 can also be the baud rate clock source of both UARTs. For details, please see Section 13.5
“Baud Rate” on page 132.
Timer 3
FSYS Pre-scalar Overflow TF3
Internal 16-bit Counter Timer 3 Interrupt
(1/1~1/128) (T3CON.4)
TR3
(T3CON.3)
T3PS[2:0]
(T3CON[2:0]) 0 7 0 7
RL3 RH3
The N76E003 provides one Watchdog Timer (WDT). It can be configured as a time-out reset timer to
reset whole device. Once the device runs in an abnormal status or hangs up by outward interference,
a WDT reset recover the system. It provides a system monitor, which improves the reliability of the
system. Therefore, WDT is especially useful for system that is susceptible to noise, power glitches, or
electrostatic discharge. The WDT also can be configured as a general purpose timer, of which the
periodic interrupt serves as an event timer or a durational system supervisor in a monitoring system,
which is able to operate during Idle or Power-down mode. WDTEN[3:0] (CONFIG4[7:4]) initialize the
WDT to operate as a time-out reset timer or a general purpose timer.
CONFIG4
7 6 5 4 3 2 1 0
WDTEN[3:0] - - - -
R/W - - - -
Factory default value: 1111 1111b
The WDT is implemented with a set of divider that divides the low-speed internal oscillator clock
nominal 10 kHz. The divider output is selectable and determines the time-out interval. When the time-
out interval is fulfilled, it will wake the system up from Idle or Power-down mode and an interrupt event
will occur if WDT interrupt is enabled. If WDT is initialized as a time-out reset timer, a system reset will
occur after a period of delay if without any software action.
1
The Watchdog time-out interval is determined by the formula × 64 , where
FLIRC × clock dividerscalar
FLIRC is the frequency of internal 10 kHz oscillator. The following table shows an example of the
Watchdog time-out interval with different pre-scales.
Note: When register CKDIV value is not equal 00H, the system clock frequency will be divided, if
under this condition after MCU into power down mode, the WDT Reset will fail. So suggest use WKT to
wakeup N76E003 when into power down mode.
0 0 0 1/1 6.40 ms
0 0 1 1/4 25.60 ms
0 1 0 1/8 51.20 ms
0 1 1 1/16 102.40 ms
1 0 0 1/32 204.80 ms
1 0 1 1/64 409.60 ms
1 1 0 1/128 819.20 ms
1 1 1 1/256 1.638 s
When the CONFIG bits WDTEN[3:0] (CONFIG4[7:4]) is not FH, the WDT is initialized as a time-out
reset timer. If WDTEN[3:0] is not 5H, the WDT is allowed to continue running after the system enters
Idle or Power-down mode. Note that when WDT is initialized as a time-out reset timer, WDTR and
WIDPD has no function.
10 kHz 512-clock
FLIRC Pre-scalar WDT counter overflow
Internal Delay
WDTRF WDT Reset
(1/1~1/256) (6-bit)
Oscillator clear
clear
WDPS[2:0] WDCLR
WDTF WDT Interrupt
After the device is powered and it starts to execute software code, the WDT starts counting
simultaneously. The time-out interval is selected by the three bits WDPS[2:0] (WDCON[2:0]). When
the selected time-out occurs, the WDT will set the interrupt flag WDTF (WDCON.5). If the WDT
interrupt enable bit EWDT (EIE.4) and global interrupt enable EA are both set, the WDT interrupt
routine will be executed. Meanwhile, an additional 512 clocks of the low-speed internal oscillator
delays to expect a counter clearing by setting WDCLR to avoid the system reset by WDT if the device
operates normally. If no counter reset by writing 1 to WDCLR during this 512-clock period, a WDT
reset will happen. Setting WDCLR bit is used to clear the counter of the WDT. This bit is self-cleared
for user monitoring it. Once a reset due to WDT occurs, the WDT reset flag WDTRF (WDCON.3) will
be set. This bit keeps unchanged after any reset other than a power-on reset. User may clear WDTRF
via software. Note that all bits in WDCON require timed access writing.
NOTICE: WDT counter has been specially taken care. The hardware automatically clears WDT
counter and pre-scalar value after :
(1) Entering into or being woken-up from Idle or Power Down mode
(2) Any resets. It prevents unconscious system reset.
The main application of the WDT with time-out reset enabling is for the system monitor. This is
important in real-time control applications. In case of some power glitches or electro-magnetic
interference, CPU may begin to execute erroneous codes and operate in an unpredictable state. If this
is left unchecked the entire system may crash. Using the WDT during software development requires
user to select proper “Feeding Dog” time by clearing the WD counter. By inserting the instruction of
setting WDCLR, it allows the code to run without any WDT reset. However If any erroneous code
executes by any interference, the instructions to clear the WDT counter will not be executed at the
required instants. Thus the WDT reset will occur to reset the system state from an erroneously
executing condition and recover the system.
There is another application of the WDT, which is used as a simple, long period timer. When the
CONFIG bits WDTEN[3:0] (CONFIG4[7:4]) is FH, the WDT is initialized as a general purpose timer. In
this mode, WDTR and WIDPD are fully accessed via software.
10 kHz
FLIRC
Internal Pre-scalar WDT counter overflow
WDTF WDT Interrupt
Oscillator (1/1~1/256) (6-bit)
clear
IDL (PCON.0)
PD (PCON.1)
WDPS[2:0] WDCLR
WIDPD
WDTR
The WDT starts running by setting WDTR as 1 and halts by clearing WDTR as 0. The WDTF flag will
be set while the WDT completes the selected time interval. The software polls the WDTF flag to detect
a time-out. An interrupt will occur if the individual interrupt EWDT (EIE.4) and global interrupt enable
EA is set. WDT will continue counting. User should clear WDTF and wait for the next overflow by
polling WDTF flag or waiting for the interrupt occurrence.
In some application of low power consumption, the CPU usually stays in Idle mode when nothing
needs to be served to save power consumption. After a while the CPU will be woken up to check if
For Example:
ORG 0000H
LJMP START
ORG 0053H
LJMP WDT_ISR
ORG 0100H
;********************************************************************
;WDT interrupt service routine
;********************************************************************
WDT_ISR:
CLR EA
MOV TA,#0AAH
MOV TA,#55H
ANL WDCON,#11011111B ;clear WDT interrupt flag
SETB EA
RETI
;********************************************************************
;Start here
;********************************************************************
START:
MOV TA,#0AAH
MOV TA,#55H
ORL WDCON,#00010111B ;choose interval length and enable WDT running
during ;Power-down
SETB EWDT ;enable WDT interrupt
SETB EA
MOV TA,#0AAH
MOV TA,#55H
ORL WDCON,#10000000B ; WDT run
;********************************************************************
;Enter Power-down mode
;********************************************************************
LOOP:
ORL PCON,#02H
LJMP LOOP
The N76E003 has a dedicated Self Wake-up Timer (WKT), which serves for a periodic wake-up timer
in low power mode or for general purpose timer. WKT remains counting in Idle or Power-down mode.
When WKT is being used as a wake-up timer, a start of WKT can occur just prior to entering a power
management mode. WKT has one clock source, internal 10 kHz. Note that the system clock frequency
must be twice over WKT clock. If WKT starts counting, the selected clock source will remain active
once the device enters Idle or Power-down mode. Note that the selected clock source of WKT will not
automatically enabled along with WKT configuration. User should manually enable the selected clock
source and waiting for stability to ensure a proper operation.
The WKT is implemented simply as a 8-bit auto-reload, up-counting timer with pre-scale 1/1 to 1/2048
selected by WKPS[2:0] (WKCON[2:0]). User fills the reload value into RWK register to determine its
overflow rate. The WKTR (WKCON.3) can be set to start counting. When the counter rolls over FFH,
WKTF (WKCON.4) is set as 1 and a reload is generated and causes the contents of the RWK register
to be reloaded into the internal 8-bit counter. If EWKT (EIE1.2) is set as 1, WKT interrupt service
routine will be served.
WKTCK
(WKCON.5) WKPS[2:0]
WKTR (WKCON[2:0]) 0 7
(WKCON.3) RWK
The N76E003 includes two enhanced full duplex serial ports enhanced with automatic address
recognition and framing error detection. As control bits of these two serial ports are implemented the
same, the bit names (including interrupt enabling or priority setting bits) end with “ _ ” (e.g. O _1)
to indicate serial port 1 control bits for making a distinction between these two serial ports. Generally
speaking, in the following contents, there will not be any reference to serial port 1, but only to serial
port 0.
Each serial port supports one synchronous communication mode, Mode 0, and three modes of full
duplex UART (Universal Asynchronous Receiver and Transmitter), Mode 1, 2, and 3. This means it
can transmit and receive simultaneously. The serial port is also receiving-buffered, meaning it can
commence reception of a second byte before a previously received byte has been read from the
register. The receiving and transmitting registers are both accessed at SBUF. Writing to SBUF loads
the transmitting register, and reading SBUF accesses a physically separate receiving register. There
are four operation modes in serial port. In all four modes, transmission initiates by any instruction that
uses SBUF as a destination register. Note that before serial port function works, the port latch bits of
P0.7 and P0.6 (for RXD and TXD pins) or P0.2 and P1.6 (for RXD_1 and TXD_1 pins) have to be set
to 1. For application flexibility, TXD and RXD pins of serial port 0 can be exchanged by UART0PX
(AUXR1.2).
13.1 Mode 0
Mode 0 provides synchronous communication with external devices. Serial data enters and exits
through RXD pin. TXD outputs the shift clocks. 8-bit frame of data are transmitted or received. Mode 0
therefore provides half-duplex communication because the transmitting or receiving data is via the
same data line RXD. The baud rate is enhanced to be selected as F SYS/12 if SM2 (SCON.5) is 0 or as
FSYS/2 if SM2 is 1. Note that whenever transmitting or receiving, the serial clock is always generated
by the MCU. Thus any device on the serial port in Mode 0 should accept the MCU as the master.
Figure 13.1 shows the associated timing of the serial port in Mode 0.
As shown there is one bi-directional data line (RXD) and one shift clock line (TXD). The shift clocks
are used to shift data in or out of the serial port controller bit by bit for a serial communication. Data
bits enter or emit LSB first. The band rate is equal to the shift clock frequency.
Transmission is initiated by any instruction writes to SBUF. The control block will then shift out the
clocks and begin to transfer data until all 8 bits are complete. Then the transmitted flag TI (SCON.1)
will be set 1 to indicate one byte transmitting complete.
Reception is initiated by the condition REN (SCON.4) = 1 and RI (SCON.0) = 0. This condition tells the
serial port controller that there is data to be shifted in. This process will continue until 8 bits have been
received. Then the received flag RI will be set as 1. User can clear RI to triggering the next byte
reception.
13.2 Mode 1
Mode 1 supports asynchronous, full duplex serial communication. The asynchronous mode is
commonly used for communication with PCs, modems or other similar interfaces. In Mode 1, 10 bits
are transmitted through TXD or received through RXD including a start bit (logic 0), 8 data bits (LSB
first) and a stop bit (logic 1). The baud rate is determined by the Timer 1. SMOD (PCON.7) setting 1
makes the baud rate double. Figure 13.2 shows the associated timings of the serial port in Mode 1 for
transmitting and receiving.
Transmission is initiated by any writing instructions to SBUF. Transmission takes place on TXD pin.
First the start bit comes out, the 8-bit data follows to be shifted out and then ends with a stop bit. After
the stop bit appears, TI (SCON.1) will be set to indicate one byte transmission complete. All bits are
shifted out depending on the rate determined by the baud rate generator.
Once the baud rate generator is activated and REN (SCON.4) is 1, the reception can begin at any
time. Reception is initiated by a detected 1-to-0 transition at RXD. Data will be sampled and shifted in
at the selected baud rate. In the midst of the stop bit, certain conditions should be met to load SBUF
with the received data:
1. RI (SCON.0) = 0, and
2. Either SM2 (SCON.5) = 0, or the received stop bit = 1 while SM2 = 1 and the received data matches
“Given” or “Broadcast” address. (For enhancement function, see 13.7 “Multiprocessor
Communication” and 13.8 “Automatic Address Recognition”.)
If these conditions are met, then the SBUF will be loaded with the received data, the RB8 (SCON.2)
with stop bit, and RI will be set. If these conditions fail, there will be no data loaded and RI will remain
0. After above receiving progress, the serial control will look forward another 1-to-0 transition on RXD
pin to start next data reception.
13.3 Mode 2
Mode 2 supports asynchronous, full duplex serial communication. Different from Mode1, there are 11
bits to be transmitted or received. They are a start bit (logic 0), 8 data bits (LSB first), a programmable
th th
9 bit TB8 or RB8 bit and a stop bit (logic 1). The most common use of 9 bit is to put the parity bit in it
or to label address or data frame for multiprocessor communication. The baud rate is fixed as 1/32 or
1/64 the system clock frequency depending on SMOD (PCON.7) bit. Figure 13.3 shows the
associated timings of the serial port in Mode 2 for transmitting and receiving.
Transmission is initiated by any writing instructions to SBUF. Transmission takes place on TXD pin.
First the start bit comes out, the 8-bit data and bit TB8 (SCON.3) follows to be shifted out and then
ends with a stop bit. After the stop bit appears, TI will be set to indicate the transmission complete.
While REN is set, the reception is allowed at any time. A falling edge of a start bit on RXD will initiate
the reception progress. Data will be sampled and shifted in at the selected baud rate. In the midst of
the stop bit, certain conditions should be met to load SBUF with the received data:
1. RI (SCON.0) = 0, and
th
2. Either SM2 (SCON.5) = 0, or the received 9 bit = 1 while SM2 = 1 and the received data matches
“Given” or “Broadcast” address. (For enhancement function, see 13.7 “Multiprocessor
Communication” and 13.8 “Automatic Address Recognition”.)
If these conditions are met, the SBUF will be loaded with the received data, the RB8(SCON.2) with the
th
received 9 bit and RI will be set. If these conditions fail, there will be no data loaded and RI will
remain 0. After above receiving progress, the serial control will look forward another 1-to-0 transition
on RXD pin to start next data reception.
13.4 Mode 3
Mode 3 has the same operation as Mode 2, except its baud rate clock source uses Timer 1 overflows
as its baud rate clocks. See Figure 13.3 for timing diagram of Mode 3. It has no difference from Mode
2.
Jul. 20, 2018 Page 131 of 276 Rev. 1.06
N76E003 Datasheet
The baud rate source and speed for different modes of serial port is quite different from one another.
All cases are listed in Table 13-3. The user should calculate the baud rate according to their system
configuration.
In Mode 1 or 3, the baud rate clock source of UART0 can be selected from Timer 1 or Timer 3. User
can select the baud rate clock source by BRCK (T3CON.5). For UART1, its baud rate clock comes
only from Timer 3 as its unique clock source.
When using Timer 1 as the baud rate clock source, note that the Timer 1 interrupt should be disabled.
Timer 1 itself can be configured for either “ imer” or “ ounter” operation. It can be in any of its three
running modes. However, in the most typical applications, it is configured for “ imer” operation, in the
auto-reload mode (Mode 2). If using Timer 3 as the baud rate generator, its interrupt should also be
disabled.
Formula
UART Mode Baud Rate Clock Source Baud Rate
Number
2SMOD FSYS
1 or 3 Timer 3 (for UART0) [5]
4
32 Pre - scale 65536 - {RH3,RL3}
1 FSYS
[5]
16 Pre - scale 65536 - {RH3,RL3}
Timer 3 (for UART1) 5
Important: Since the limitation of baud rate generator, Suggest setting baud rate under 38400
when system timer base 16MHz HIRC value. Following show the baud rate value table show the
deviation upper 38400 baud rate.
But In most application the baud rate 115200 is a common setting value. So we provide a special
function to modify HIRC to 16.6MHz. then the deviation of baud rate will be reasonable. Following
table shows the error value when HIRC and timer base modified.
N76E003 provide two bytes SFR to user trim HIRC value, default after reset the value is trim to
16MHz, once modify this SFR, the HIRC value will change. Suggest decrease reset value 15(dec.)
will trim HIRC to 16.6MHz.
Following two Byte combine the 9 bit internal RC trim value. Each bit deviation is 0.25% of 16MHz
that means about 40KHz / bit.
void MODIFY_HIRC_166(void)
{
unsigned char hircmap0,hircmap1;
unsigned int trimvalue16bit;
/* Since only power on will reload RCTRIM0 and RCTRIM1 value, check power on
flag*/
if ((PCON&SET_BIT4)==SET_BIT4)
{
hircmap0 = RCTRIM0;
hircmap1 = RCTRIM1;
trimvalue16bit = ((hircmap0<<1)+(hircmap1&0x01));
trimvalue16bit = trimvalue16bit - 15;
hircmap1 = trimvalue16bit&0x01;
hircmap0 = trimvalue16bit>>1;
TA=0XAA;
TA=0X55;
RCTRIM0 = hircmap0;
TA=0XAA;
TA=0X55;
RCTRIM1 = hircmap1;
/* After modify HIRC value, clear power on flag */
PCON &= CLR_BIT4;
}
}
Framing error detection is provided for asynchronous modes. (Mode 1, 2, or 3.) The framing error
occurs when a valid stop bit is not detected due to the bus noise or contention. The UART can detect
a framing error and notify the software.
The framing error bit, FE, is located in SCON.7. This bit normally serves as SM0. While the framing
error accessing enable bit SMOD0 (PCON.6) is set 1, it serves as FE flag. Actually, SM0 and FE
locate in different registers.
The FE bit will be set 1 via hardware while a framing error occurs. FE can be checked in UART
interrupt service routine if necessary. Note that SMOD0 should be 1 while reading or writing to FE. If
FE is set, any following frames received without frame error will not clear the FE flag. The clearing has
to be done via software.
The N76E003 multiprocessor communication feature lets a master device send a multiple frame serial
message to a slave device in a multi-slave configuration. It does this without interrupting other slave
devices that may be on the same serial line. This feature can be used only in UART Mode 2 or 3. User
can enable this function by setting SM2 (SCON.5) as logic 1 so that when a byte of frame is received,
th th
the serial interrupt will be generated only if the 9 bit is 1. (For Mode 2, the 9 bit is the stop bit.) When
th
the SM2 bit is 1, serial data frames that are received with the 9 bit as 0 do not generate an interrupt.
th
In this case, the 9 bit simply separates the slave address from the serial data.
When the master device wants to transmit a block of data to one of several slaves on a serial line, it
first sends out an address byte to identify the target slave. Note that in this case, an address byte
th
differs from a data byte. In an address byte, the 9 bit is 1 and in a data byte, it is 0. The address byte
interrupts all slaves so that each slave can examine the received byte and see if it is addressed by its
own slave address. The addressed slave then clears its SM2 bit and prepares to receive incoming
data bytes. The SM2 bits of slaves that were not addressed remain set, and they continue operating
normally while ignoring the incoming data bytes.
th
– First byte: the address, identifying the target slave device, (9 bit = 1).
th
– Next bytes: data, (9 bit = 0).
th
4. When the target slave receives the first byte, all of the slaves are interrupted because the 9 data
bit is 1. The targeted slave compares the address byte to its own address and then clears its SM2 bit
to receiving incoming data. The other slaves continue operating normally.
5. After all data bytes have been received, set SM2 back to 1 to wait for next address.
SM2 has no effect in Mode 0, and in Mode 1 can be used to check the validity of the stop bit. For
Mode 1 reception, if SM2 is 1, the receiving interrupt will not be issue unless a valid stop bit is
received.
The automatic address recognition is a feature, which enhances the multiprocessor communication
feature by allowing the UART to recognize certain addresses in the serial bit stream by using
hardware to make the comparisons. This feature saves a great deal of software overhead by
eliminating the need for the software to examine every serial address, which passes by the serial port.
Only when the serial port recognizes its own address, the receiver sets RI bit to request an interrupt.
The automatic address recognition feature is enabled when the multiprocessor communication feature
is enabled, SM2 is set.
If desired, user may enable the automatic address recognition feature in Mode 1. In this configuration,
the stop bit takes the place of the ninth data bit. RI is set only when the received command frame
address matches the device’s address and is terminated by a valid stop bit.
Using the automatic address recognition feature allows a master to selectively communicate with one
or more slaves by invoking the “Given” slave address or addresses. All of the slaves may be contacted
by using the “Broadcast” address. wo F s are used to define the slave address, ADD , and the
slave address mask, SADEN. SADEN is used to define which bits in the SADDR are to be used and
which bits are “don’t care”. he ADE mask can be logically ANDed with the SADDR to create the
“Given” address, which the master will use for addressing each of the slaves. Use of the “Given”
address allows multiple slaves to be recognized while excluding others.
The following examples will help to show the versatility of this scheme.
Example 1, slave 0:
SADDR = 11000000b
SADEN = 11111101b
Given = 110000X0b
Example 2, slave 1:
SADDR = 11000000b
SADEN = 11111110b
Given = 1100000Xb
In the above example SADDR is the same and the SADEN data is used to differentiate between the
two slaves. Slave 0 requires 0 in bit 0 and it ignores bit 1. Slave 1 requires 0 in bit 1 and bit 0 is
ignored. A unique address for Slave 0 would be 1100 0010 since slave 1 requires 0 in bit 1. A unique
address for slave 1 would be 11000001b since 1 in bit 0 will exclude slave 0. Both slaves can be
selected at the same time by an address, which has bit 0 = 0 (for slave 0) and bit 1 = 0 (for slave 1).
hus, both could be addressed with b as their “Broadcast” address.
In a more complex system the following could be used to select slaves 1 and 2 while excluding slave
0:
Example 1, slave 0:
SADDR = 11000000b
SADEN = 11111001b
Given = 11000XX0b
Example 2, slave 1:
SADDR = 11100000b
SADEN = 11111010b
Given = 11100X0Xb
Example 3, slave 2:
SADDR = 11000000b
SADEN = 11111100b
Given = 110000XXb
In the above example the differentiation among the 3 slaves is in the lower 3 address bits. Slave 0
requires that bit 0 = 0 and it can be uniquely addressed by 11100110b. Slave 1 requires that bit 1 = 0
and it can be uniquely addressed by 11100101b. Slave 2 requires that bit 2 = 0 and its unique address
is 11100011b. To select Slaves 0 and 1 and exclude Slave 2 use address 11100100b, since it is
necessary to make bit 2 = 1 to exclude slave 2.
he “Broadcast” address for each slave is created by taking the logical O of ADD and ADE .
Zeros in this result are treated as “don’t-cares”, e.g.:
SADDR = 01010110b
SADEN = 11111100b
Broadcast = 1111111Xb
he use of don’t-care bits provides flexibility in defining the Broadcast address, however in most
applications, interpreting the “don’t-cares” as all ones, the broadcast address will be FFH.
On reset, ADD and ADE are initialized to H. his produces a “Given” address of all “don’t
cares” as well as a “Broadcast” address of all XXXXXXXXb (all “don’t care” bits). his ensures that the
serial port will reply to any address, and so that it is backwards compatible with the standard 80C51
microcontrollers that do not support automatic address recognition.
The N76E003 provides a Serial Peripheral Interface (SPI) block to support high-speed serial
communication. SPI is a full-duplex, high-speed, synchronous communication bus between
microcontrollers or other peripheral devices such as serial EEPROM, LCD driver, or D/A converter. It
provides either Master or Slave mode, high-speed rate up to FSYS/2, transfer complete and write
collision flag. For a multi-master system, SPI supports Master Mode Fault to protect a multi-master
conflict.
FSYS
S
Divider M MISO
/2, /4, /8, /16 MSB LSB
Write Data Buffer M MOSI
CLOCK
SPR1
SPR0
SS
DISMODF
SSOE
SPIEN
MSTR
MSTR
MODF
SPIF
LSBFE
SPIEN
MSTR
SSOE
CPHA
CPOL
SPR1
SPR0
Internal
SPI Interrupt Data Bus
Figure 14.1. SPI Block Diagram shows SPI block diagram. It provides an overview of SPI architecture
in this device. The main blocks of SPI are the SPI control register logic, SPI status logic, clock rate
control logic, and pin control logic. For a serial data transfer or receiving, The SPI block exists a write
data buffer, a shift out register and a read data buffer. It is double buffered in the receiving and
transmit directions. Transmit data can be written to the shifter until when the previous transfer is not
complete. Receiving logic consists of parallel read data buffer so the shift register is free to accept a
second data, as the first received data will be transferred to the read data buffer.
The four pins of SPI interface are Master-In/Slave-Out (MISO), Master-Out/Slave-In (MOSI), Shift
Clock (SPCLK), and Slave Select ( ̅̅̅̅). The MOSI pin is used to transfer a 8-bit data in series from the
Master to the Slave. Therefore, MOSI is an output pin for Master device and an input for Slave.
Respectively, the MISO is used to receive a serial data from the Slave to the Master.
The SPCLK pin is the clock output in Master mode, but is the clock input in Slave mode. The shift
clock is used to synchronize the data movement both in and out of the devices through their MOSI and
MISO pins. The shift clock is driven by the Master mode device for eight clock cycles. Eight clocks
exchange one byte data on the serial lines. For the shift clock is always produced out of the Master
device, the system should never exist more than one device in Master mode for avoiding device
conflict.
Each Slave peripheral is selected by one Slave Select pin ( ̅̅̅̅). The signal should stay low for any
Slave access. When ̅̅̅̅ is driven high, the Slave device will be inactivated. If the system is multi-
slave, there should be only one Slave device selected at the same time. In the Master mode MCU, the
̅̅̅̅ pin does not function and it can be configured as a general purpose I/O. However, ̅̅̅̅ can be used
as Master Mode Fault detection (see Section 14.5 “Mode Fault Detection” on page 150) via software
setting if multi-master environment exists. The N76E003 also provides auto-activating function to
toggle ̅̅̅̅ between each byte-transfer.
Master/Slave Master/Slave
MCU1 MCU2
MISO MISO
MOSI MOSI
SPCLK SPCLK
SS SS
0 0
I/O 1 1 I/O
PORT 2 2 PORT
3 3
SO
SCK
SO
SO
SCK
SCK
SS
SS
SS
SI
SI
SI
Figure 14.2 shows a typical interconnection of SPI devices. The bus generally connects devices
together through three signal wires, MOSI to MOSI, MISO to MISO, and SPCLK to SPCLK. The
Master devices select the individual Slave devices by using four pins of a parallel port to control the
four ̅̅̅̅ pins. MCU1 and MCU2 play either Master or Slave mode. The ̅̅̅̅ should be configured as
Master Mode Fault detection to avoid multi-master conflict.
MOSI MOSI
SPI clock
generator SS SS
*
Master MCU GND Slave MCU
* SS configuration follows DISMODF and SSOE bits.
Figure 14.3 shows the simplest SPI system interconnection, single-master and signal-slave. During a
transfer, the Master shifts data out to the Slave via MOSI line. While simultaneously, the Master shifts
data in from the Slave via MISO line. The two shift registers in the Master MCU and the Slave MCU
can be considered as one 16-bit circular shift register. Therefore, while a transfer data pushed from
Master into Slave, the data in Slave will also be pulled in Master device respectively. The transfer
effectively exchanges the data, which was in the SPI shift registers of the two MCUs.
By default, SPI data is transferred MSB first. If the LSBFE (SPCR.5) is set, SPI data shifts LSB first.
This bit does not affect the position of the MSB and LSB in the data register. Note that all the following
description and figures are under the condition of LSBFE logic 0. MSB is transmitted and received
first.
There are three SPI registers to support its operations, including SPI control register (SPCR), SPI
status register (SPSR), and SPI data register (SPDR). These registers provide control, status, data
storage functions, and clock rate selection. The following registers relate to SPI function.
SPR[1:0] are valid only under Master mode (MSTR = 1). If under Slave mode, the
clock will automatically synchronize with the external clock on SPICLK pin from
Master device up to FSYS/2 communication speed.
The SPI can operate in Master mode while MSTR (SPCR.4) is set as 1. Only one Master SPI device
can initiate transmissions. A transmission always begins by Master through writing to SPDR. The byte
written to SPDR begins shifting out on MOSI pin under the control of SPCLK. Simultaneously, another
byte shifts in from the Slave on the MISO pin. After 8-bit data transfer complete, SPIF (SPSR.7) will
automatically set via hardware to indicate one byte data transfer complete. At the same time, the data
received from the Slave is also transferred in SPDR. User can clear SPIF and read data out of SPDR.
When MSTR is 0, the SPI operates in Slave mode. The SPCLK pin becomes input and it will be
clocked by another Master SPI device. The ̅̅̅̅̅ pin also becomes input. The Master device cannot
exchange data with the Slave device until the ̅̅̅̅̅ pin of the Slave device is externally pulled low.
Before data transmissions occurs, the ̅̅̅̅̅ of the Slave device should be pulled and remain low until
the transmission is complete. If ̅̅̅̅̅ goes high, the SPI is forced into idle state. If the ̅̅̅̅̅ is forced to
high at the middle of transmission, the transmission will be aborted and the rest bits of the receiving
shifter buffer will be high and goes into idle state.
In Slave mode, data flows from the Master to the Slave on MOSI pin and flows from the Slave to the
Master on MISO pin. The data enters the shift register under the control of the SPCLK from the Master
device. After one byte is received in the shift register, it is immediately moved into the read data buffer
and the SPIF bit is set. A read of the SPDR is actually a read of the read data buffer. To prevent an
overrun and the loss of the byte that caused by the overrun, the Slave should read SPDR out and the
first SPIF should be cleared before a second transfer of data from the Master device comes in the
read data buffer.
To accommodate a wide variety of synchronous serial peripherals, the SPI has a clock polarity bit
CPOL (SPCR.3) and a clock phase bit CPHA (SPCR.2). Figure 14.4. SPI Clock Formats shows that
CPOL and CPHA compose four different clock formats. The CPOL bit denotes the SPCLK line level in
its idle state. The CPHA bit defines the edge on which the MOSI and MISO lines are sampled. The
CPOL and CPHA should be identical for the Master and Slave devices on the same system. To
Communicate in different data formats with one another will result undetermined result.
sample sample
CPOL = 1
sample sample
In SPI, a Master device always initiates the transfer. If SPI is selected as Master mode (MSTR = 1)
and enabled (SPIEN = 1), writing to the SPI data register (SPDR) by the Master device starts the SPI
clock and data transfer. After shifting one byte out and receiving one byte in, the SPI clock stops and
SPIF (SPSR.7) is set in both Master and Slave. If SPI interrupt enable bit ESPI (EIE.0) is set 1 and
global interrupt is enabled (EA = 1), the interrupt service routine (ISR) of SPI will be executed.
Concerning the Slave mode, the ̅̅̅̅̅ signal needs to be taken care. As shown in Figure 14.4. SPI
Clock Formats, when CPHA = 0, the first SPCLK edge is the sampling strobe of MSB (for an example
of LSBFE = 0, MSB first). Therefore, the Slave should shift its MSB data before the first SPCLK edge.
The falling edge of ̅̅̅̅̅ is used for preparing the MSB on MISO line. The ̅̅̅̅̅ pin therefore should
toggle high and then low between each successive serial byte. Furthermore, if the slave writes data to
the SPI data register (SPDR) while ̅̅̅̅̅ is low, a write collision error occurs.
When CPHA = 1, the sampling edge thus locates on the second edge of SPCLK clock. The Slave
uses the first SPCLK clock to shift MSB out rather than the ̅̅̅̅̅ falling edge. Therefore, the ̅̅̅̅̅ line can
remain low between successive transfers. This format may be preferred in systems having single fixed
Master and single fixed Slave. The ̅̅̅̅̅ line of the unique Slave device can be tied to GND as long as
only CPHA = 1 clock mode is used.
The SPI should be configured before it is enabled (SPIEN = 1), or a change of LSBFE, MSTR,
CPOL, CPHA and SPR[1:0] will abort a transmission in progress and force the SPI system into
idle state. Prior to any configuration bit changed, SPIEN must be disabled first.
SPCLK Cycles
SPCLK Cycles 1 2 3 4 5 6 7 8
SPCLK (CPOL=0)
SPCLK (CPOL=1)
Transfer Progress[1]
(internal signal)
Input to Slave SS
SS output of Master[2]
SPIF (Master)
SPIF (Slave)
SPCLK Cycles
SPCLK Cycles 1 2 3 4 5 6 7 8
SPCLK (CPOL=0)
SPCLK (CPOL=1)
Transfer Progress[1]
(internal signal)
Input to Slave SS
SS output of Master[2]
SPIF (Master)
SPIF (Slave)
The N76E003 SPI gives a flexible ̅̅̅̅̅ pin feature for different system requirements. When the SPI
operates as a Slave, ̅̅̅̅̅ pin always rules as Slave select input. When the Master mode is enabled, ̅̅̅̅̅
has three different functions according to DISMODF (SPSR.3) and SSOE (SPCR.7). By default,
DISMODF is 0. It means that the Mode Fault detection activates. ̅̅̅̅̅ is configured as a input pin to
check if the Mode Fault appears. On the contrary, if DISMODF is 1, Mode Fault is inactivated and the
SSOE bit takes over to control the function of the ̅̅̅̅̅ pin. While SSOE is 1, it means the Slave select
signal will generate automatically to select a Slave device. The ̅̅̅̅̅ as output pin of the Master usually
connects with the ̅̅̅̅̅ input pin of the Slave device. The ̅̅̅̅̅ output automatically goes low for each
transmission when selecting external Slave device and goes high during each idle state to de-select
the Slave device. While SSOE is 0 and DISMODF is 1, ̅̅̅̅̅ is no more used by the SPI and reverts to
be a general purpose I/O pin.
The Mode Fault detection is useful in a system where more than one SPI devices might become
Masters at the same time. It may induce data contention. When the SPI device is configured as a
Master and the ̅̅̅̅̅ input line is configured for Mode Fault input depending on Table 14-1. Slave Select
Pin Configurations, a Mode Fault error occurs once the ̅̅̅̅̅ is pulled low by others. It indicates that
some other SPI device is trying to address this Master as if it is a Slave. Instantly the MSTR and
SPIEN control bits in the SPCR are cleared via hardware to disable SPI, Mode Fault flag MODF
(SPSR.4) is set and an interrupt is generated if ESPI (EIE .0) and EA are enabled.
The SPI is signal buffered in the transfer direction and double buffered in the receiving and transmit
direction. New data for transmission cannot be written to the shift register until the previous transaction
is complete. Write collision occurs while SPDR be written more than once while a transfer was in
progress. SPDR is double buffered in the transmit direction. Any writing to SPDR cause data to be
written directly into the SPI shift register. Once a write collision error is generated, WCOL (SPSR.6)
will be set as 1 via hardware to indicate a write collision. In this case, the current transferring data
continues its transmission. However the new data that caused the collision will be lost. Although the
SPI logic can detect write collisions in both Master and Slave modes, a write collision is normally a
Slave error because a Slave has no indicator when a Master initiates a transfer. During the receiving
of Slave, a write to SPDR causes a write collision in Slave mode. WCOL flag needs to be cleared via
software.
For receiving data, the SPI is double buffered in the receiving direction. The received data is
transferred into a parallel read data buffer so the shifter is free to accept a second serial byte.
However, the received data should be read from SPDR before the next data has been completely
shifted in. As long as the first byte is read out of the read data buffer and SPIF is cleared before the
next byte is ready to be transferred, no overrun error condition occurs. Otherwise the overrun error
occurs. In this condition, the second byte data will not be successfully received into the read data
register and the previous data will remains. If overrun occur, SPIOVF (SPSR.5) will be set via
hardware. An SPIOVF setting will also require an interrupt if enabled. Figure 14.7. SPI Overrun
Waveform shows the relationship between the data receiving and the overrun error.
Three SPI status flags, SPIF, MODF, and SPIOVF, can generate an SPI event interrupt requests. All
of them locate in SPSR. SPIF will be set after completion of data transfer with external device or a
new data have been received and copied to SPDR. MODF becomes set to indicate a low level on ̅̅̅̅̅
causing the Mode Fault state. SPIOVF denotes a receiving overrun error. If SPI interrupt mask is
enabled via setting ESPI (EIE.6) and EA is 1, CPU will executes the SPI interrupt service routine once
any of these three flags is set. User needs to check flags to determine what event caused the
interrupt. These three flags are software cleared.
SPIF
SPIOVF
SPI Interrupt
SS Mode
MODF
Fault ESPI
MSTR Detection EA
(EIE.6)
DISMODF
2
15. INTER-INTEGRATED CIRCUIT (I C)
2
The Inter-Integrated Circuit (I C) bus serves as an serial interface between the microcontrollers and
2 2
the I C devices such as EEPROM, LCD module, temperature sensor, and so on. The I C bus used
two wires design (a serial data line SDA and a serial clock line SCL) to transfer information between
devices.
2
The I C bus uses bi-directional data transfer between masters and slaves. There is no central master
and the multi-master system is allowed by arbitration between simultaneously transmitting masters.
The serial clock synchronization allows devices with different bit rates to communicate via one serial
2
bus. The I C bus supports four transfer modes including master transmitter, master receiver, slave
2
receiver, and slave transmitter. The I C interface only supports 7-bit addressing mode. A special mode
2
General Call is also available. The I C can meet both standard (up to 100kbps) and fast (up to 400k
bps) speeds.
For a bi-directional transfer operation, the SDA and SCL pins should be open-drain pads. This
implements a wired-AND function, which is essential to the operation of the interface. A low level on a
2 2
I C bus line is generated when one or more I C devices output a “ ”. A high level is generated when
2
all I C devices output “ ”, allowing the pull-up resistors to pull the line high. In N76E003, user should
2
set output latches of SCL and SDA. As logic 1 before enabling the I C function by setting I2CEN
(I2CON.6).
VDD
RUP RUP
SDA
SCL
2
Figure 15.1. I C Bus Interconnection
2
The I C is considered free when both lines are high. Meanwhile, any device, which can operate as a
master can occupy the bus and generate one transfer after generating a START condition. The bus
now is considered busy before the transfer ends by sending a STOP condition. The master generates
Jul. 20, 2018 Page 153 of 276 Rev. 1.06
N76E003 Datasheet
all of the serial clock pulses and the START and STOP condition. However if there is no START
condition on the bus, all devices serve as not addressed slave. The hardware looks for its own slave
address or a General Call address. (The General Call address detection may be enabled or disabled
by GC (I2ADDR.0).) If the matched address is received, an interrupt is requested.
2
Every transaction on the I C bus is 9 bits long, consisting of 8 data bits (MSB first) and a single
acknowledge bit. The number of bytes per transfer (defined as the time between a valid START and
STOP condition) is unrestricted but each byte has to be followed by an acknowledge bit. The master
th
device generates 8 clock pulse to send the 8-bit data. After the 8 falling edge of the SCL line, the
device outputting data on the SDA changes that pin to an input and reads in an acknowledge value on
th th
the 9 clock pulse. After 9 clock pulse, the data receiving device can hold SCL line stretched low if
next receiving is not prepared ready. It forces the next byte transaction suspended. The data
transaction continues when the receiver releases the SCL line.
SDA
MSB LSB ACK
SCL
1 2 8 9
START STOP
condition condition
2
Figure 15.2. I C Bus Protocol
2
The protocol of the I C bus defines two states to begin and end a transfer, START (S) and STOP (P)
conditions. A START condition is defined as a high-to-low transition on the SDA line while SCL line is
high. The STOP condition is defined as a low-to-high transition on the SDA line while SCL line is high.
2
A START or a STOP condition is always generated by the master and I C bus is considered busy after
a START condition and free after a STOP condition. After issuing the STOP condition successful, the
original master device will release the control authority and turn back as a not addressed slave.
2
Consequently, the original addressed slave will become a not addressed slave. The I C bus is free
and listens to next START condition of next transfer.
A data transfer is always terminated by a STOP condition generated by the master. However, if a
master still wishes to communicate on the bus, it can generate a repeated START (Sr) condition and
address the pervious or another slave without first generating a STOP condition. Various combinations
of read/write formats are then possible within such a transfer.
SDA
SCL
Repeated
START STOP START STOP
START
Following the START condition is generated, one byte of special data should be transmitted by the
th
master. It includes a 7-bit long slave address (SLA) following by an 8 bit, which is a data direction bit
(R/W), to address the target slave device and determine the direction of data flow. If R/W bit is 0, it
indicates that the master will write information to a selected slave. Also, if R/W bit is 1, it indicates that
the master will read information from the addressed slave. An address packet consisting of a slave
address and a read I or a write (W) bit is called SLA+R or SLA+W, respectively. A transmission
basically consists of a START condition, a SLA+W/R, one or more data packets and a STOP
condition. After the specified slave is addressed by SLA+W/R, the second and following 8-bit data
bytes issue by the master or the slave devices according to the R/W bit configuration.
here is an exception called “General all” address, which can address all devices by giving the first
byte of data all 0. A General Call is used when a master wishes to transmit the same message to
several slaves in the system. When this address is used, other devices may respond with an
acknowledge or ignore it according to individual software configuration. If a device response the
General Call, it operates as like in the slave-receiver mode. Note that the address 0x00 is reserved for
2
General Call and cannot be used as a slave address, therefore, in theory, a 7-bit addressing I C bus
accepts 127 devices with their slave addresses 1 to 127.
SDA
SCL
1-7 8 9 1-7 8 9 1-7 8 9
2
Figure 15.4. Data Format of One I C Transfer
During the data transaction period, the data on the SDA line should be stable during the high period of
the clock, and the data line can only change when SCL is low.
15.1.3 Acknowledge
e th
Th 9 SCL pulse for any transferred byte is dedicated as an Acknowledge (ACK). It allows receiving
devices (which can be the master or slave) to respond back to the transmitter (which also can be the
master or slave) by pulling the SDA line low. The acknowledge-related clock pulse is generated by the
master. The transmitter should release control of SDA line during the acknowledge clock pulse. The
ACK is an active-low signal, pulling the SDA line low during the clock pulse high duty, indicates to the
transmitter that the device has received the transmitted data. Commonly, a receiver, which has been
addressed is requested to generate an ACK after each byte has been received. When a slave receiver
does not acknowledge (NACK) the slave address, the SDA line should be left high by the slave so that
the mater can generate a STOP or a repeated START condition.
If a slave-receiver does acknowledge the slave address, it switches itself to not addressed slave mode
and cannot receive any more data bytes. This slave leaves the SDA line high. The master should
generate a STOP or a repeated START condition.
If a master-receiver is involved in a transfer, because the master controls the number of bytes in the
transfer, it should signal the end of data to the slave-transmitter by not generating an acknowledge on
the last byte. The slave-transmitter then switches to not addressed mode and releases the SDA line to
allow the master to generate a STOP or a repeated START condition.
15.1.4 Arbitration
A master may start a transfer only if the bus is free. It is possible for two or more masters to generate
a START condition. In these situations, an arbitration scheme takes place on the SDA line, while SCL
is high. During arbitration, the first of the competing master devices to place‘a’’1’ (high) on SDA while
Jul. 20, 2018 Page 156 of 276 Rev. 1.06
N76E003 Datasheet
another master transmits‘a’’0’ (low) switches off its data output stage because the level on the bus
does not match its own level. The arbitration lost master switches to the not addressed slave
immediately to detect its own slave address in the same serial transfer whether it is being addressed
by the winning master. It also releases SDA line to high level for not affecting the data transfer
continued by the winning master. However, the arbitration lost master continues generating clock
pulses on SCL line until the end of the byte in which it loses the arbitration.
Arbitration is carried out by all masters continuously monitoring the SDA line after outputting data. If
the value read from the SDA line does not match the value that the master has to output, it has lost
the arbitration. Note that a master can only lose arbitration when it outputs a high SDA value while
another master outputs a low value. Arbitration will continue until only one master remains, and this
may take many bits. Its first stage is a comparison of address bits, and if both masters are trying to
address the same device, arbitration continues on to the comparison of data bits or acknowledge bit.
SDA line
SCL line
START
condition
2
15.2 Control Registers of I C
2
There are five control registers to interface the I C bus including I2CON, I2STAT, I2DAT, I2ADDR, and
I2CLK. These registers provide protocol control, status, data transmitting and receiving functions, and
clock rate configuration. For application flexibility, SDA and SCL pins can be exchanged by I2CPX
2
(I2CON.0). The following registers relate to I C function.
2
I2CON – I C Control (Bit-addressable)
7 6 5 4 3 2 1 0
- I2CEN STA STO SI AA - I2CPX
- R/W R/W R/W R/W R/W - R/W
Address: C0H Reset value: 0000 0000b
2
I2STAT – I C Status
7 6 5 4 3 2 1 0
I2STAT[7:3] 0 0 0
R R R R
Address: BDH Reset value: 1111 1000b
2
I2DAT – I C Data
7 6 5 4 3 2 1 0
I2DAT[7:0]
R/W
Address: BCH Reset value: 0000 0000b
2
I2ADDR – I C Own Slave Address
7 6 5 4 3 2 1 0
I2ADDR[7:1] GC
R/W R/W
Address: C1H Reset value: 0000 0000b
2
I2CLK – I C Clock
7 6 5 4 3 2 1 0
I2CLK[7:0]
R/W
Address: BEH Reset value: 0000 1001b
2
In I C protocol definition, there are four operating modes including master transmitter, master receiver,
slave receiver, and slave transmitter. There is also a special mode called General Call. Its operating is
similar to master transmitter mode.
In the master transmitter mode, several bytes of data are transmitted to a slave receiver. The master
should prepare by setting desired clock rate in I2CLK. The master transmitter mode may now be
entered by setting STA (I2CON.5) bit as 1. The hardware will test the bus and generate a START
condition as soon as the bus becomes free. After a START condition is successfully produced, the SI
flag (I2CON.3) will be set and the status code in I2STAT show 08H. The progress is continued by
loading DA with the target slave address and the data direction bit “write” ( A+W). he bit
should then be cleared to commence SLA+W transaction.
After the SLA+W byte has been transmitted and an acknowledge (ACK) has been returned by the
addressed slave device, the SI flag is set again and I2STAT is read as 18H. The appropriate action to
be taken follows user defined communication protocol by sending data continuously. After all data is
transmitted, the master can send a STOP condition by setting STO (I2CON.4) and then clearing SI to
terminate the transmission. A repeated START condition can also be generated without sending
STOP condition to immediately initial another transmission.
(STA,STO,SI,AA) = (1,0,0,X)
Normal
A START will be transmitted
Arbitration lost
08H
A START has been transmitted
MT
to corresponding
slave mode
28H 10H A STOP has been transmitted A STOP has been transmitted
Data byte has been transmitted A repeated START has
ACK has been received been transmitted
or
30H
Data byte has been transmitted
NACK has been received
38H
Arbitration lost in
SLA+W or Data byte
MR
to master receiver
In the master receiver mode, several bytes of data are received from a slave transmitter. The
transaction is initialized just as the master transmitter mode. Following the START condition, I2DAT
should be loaded with the target slave address and the data direction bit “read” ( A+ ). After the
SLA+R byte is transmitted and an acknowledge bit has been returned, the SI flag is set again and
I2STAT is read as 40H. SI flag then should be cleared to receive data from the slave transmitter. If AA
flag (I2CON.2) is set, the master receiver will acknowledge the slave transmitter. If AA is cleared, the
master receiver will not acknowledge the slave and release the slave transmitter as a not addressed
slave. After that, the master can generate a STOP condition or a repeated START condition to
terminate the transmission or initial another one.
08H
A START has been transmitted
MR
to corresponding
slave mode
58H 50H 10H A STOP has been transmitted A STOP has been transmitted
Data byte has been received Data byte has been received A repeated START has
NACK has been transmitted ACK has been transmitted been transmitted
I2DAT = Data Byte I2DAT = Data Byte
38H
Arbitration lost in NACK bit
MT
to master transmitter
In the slave receiver mode, several bytes of data are received form a master transmitter. Before a
transmission is commenced, I2ADDR should be loaded with the address to which the device will
respond when addressed by a master. I2CLK does not affect in slave mode. The AA bit should be set
Jul. 20, 2018 Page 163 of 276 Rev. 1.06
N76E003 Datasheet
2
to enable acknowledging its own slave address. After the initialization above, the I C idles until it is
addressed by its own address with the data direction bit “write” ( A+W). he slave receiver mode
may also be entered if arbitration is lost.
After the slave is addressed by SLA+W, it should clear its SI flag to receive the data from the master
transmitter. If the AA bit is 0 during a transaction, the slave will return a non-acknowledge after the
next received data byte. The slave will also become not addressed and isolate with the master. It
cannot receive any byte of data with I2DAT remaining the previous byte of data, which is just received.
(STA,STO,SI,AA) = (0,0,0,1)
If own SLA+W is received,
ACK will be transmitted
60H
Own SLA+W has been received
ACK has been transmitted
I2DAT = own SLA+W
OR
68H
Arbitration lost and own SLA+W
has been received
ACK has been transmitted
I2DAT = own SLA+W
In the slave transmitter mode, several bytes of data are transmitted to a master receiver. After
2
I2ADDR and I2CON values are given, the I C wait until it is addressed by its own address with the
data direction bit “read” ( A+ ). he slave transmitter mode may also be entered if arbitration is lost.
After the slave is addressed by SLA+R, it should clear its SI flag to transmit the data to the master
receiver. Normally the master receiver will return an acknowledge after every byte of data is
transmitted by the slave. f the acknowledge is not received, it will transmit all “ ” data if it continues
Jul. 20, 2018 Page 164 of 276 Rev. 1.06
N76E003 Datasheet
the transaction. It becomes a not addressed slave. If the AA flag is cleared during a transaction, the
slave transmits the last byte of data. he next transmitting data will be all “ ” and the slave becomes
not addressed.
(STA,STO,SI,AA) = (0,0,0,1)
If own SLA+R is received,
ACK will be transmitted
A8H
Own SLA+R has been received
ACK has been transmitted
I2DAT = own SLA+R
OR
B0H
Arbitration lost and own SLA+R
has been received
ACK has been transmitted
I2DAT = own SLA+R
*
B8H C0H C8H A0H
Data byte has been transmitted Data byte has been transmitted Last Data byte has been transmitted A STOP or repeated START
ACK has been received NACK has been received ACK has been received has been received
The General all is a special condition of slave receiver mode by been addressed with all “ ” data in
slave address with data direction bit. Both GC (I2ADDR.0) bit and AA bit should be set as 1 to enable
acknowledging General Calls. The slave addressed by a General Call has different status code in
I2STAT with normal slave receiver mode. The General Call may also be produced if arbitration is lost.
(STA,STO,SI,AA) = (0,0,0,1)
GC = 1
If General Call is received,
ACK will be transmitted
70H
General Call has been received
ACK has been transmitted
I2DAT = 00H
OR
78H
Arbitration lost and General Call
has been received
ACK has been transmitted
I2DAT = 00H
There are two I2STAT status codes that do not correspond to the 25 defined states, which are
mentioned in previous sections. These are F8H and 00H states.
The first status code F8H indicates that no relevant information is available during each transaction.
2
Meanwhile, the SI flag is 0 and no I C interrupt is required.
The other status code 00H means a bus error has occurred during a transaction. A bus error is caused
by a START or STOP condition appearing temporally at an illegal position such as the second through
eighth bits of an address or a data byte, and the acknowledge bit. When a bus error occurs, the SI flag
2
is set immediately. When a bus error is detected on the I C bus, the operating device immediately
switches to the not addressed salve mode, releases SDA and SCL lines, sets the SI flag, and loads
I2STAT as 00H. To recover from a bus error, the STO bit should be set and then SI should be cleared.
2
After that, STO is cleared by hardware and release the I C bus without issuing a real STOP condition
2
waveform on I C bus.
Jul. 20, 2018 Page 166 of 276 Rev. 1.06
N76E003 Datasheet
There is a special case if a START or a repeated START condition is not successfully generated for
2
I C bus is obstructed by a low level on SDA line e.g. a slave device out of bit synchronization, the
2
problem can be solved by transmitting additional clock pulses on the SCL line. The I C hardware
transmits additional clock pulses when the STA bit is set, but no START condition can be generated
because the SDA line is pulled low. When the SDA line is eventually released, a normal START
condition is transmitted, state 08H is entered, and the serial transaction continues. If a repeated
2
START condition is transmitted while SDA is obstructed low, the I C hardware also performs the same
action as above. In this case, state 08H is entered instead of 10H after a successful START condition
is transmitted. Note that the software is not involved in solving these bus problems.
2
The following table is show the status display in I2STAT register of I C number and description:
0x18 Master Transmit Address ACK 0Xb0 Slave Transmit Arbitration Lost
0x20 Master Transmit Address NACK 0Xb8 Slave Transmit Data ACK
0x28 Master Transmit Data ACK 0Xc0 Slave Transmit Data NACK
0x30 Master Transmit Data NACK 0Xc8 Slave Transmit Last Data ACK
0x40 Master Receive Address ACK 0x68 Slave Receive Arbitration Lost
0x48 Master Receive Address NACK 0x80 Slave Receive Data ACK
0x50 Master Receive Data ACK 0x88 Slave Receive Data NACK
Note:
When I2C is enabled and I2C status is entered bus error state, SI flag is set by hardware. Until the I2C
bus error is handled, SI flag will maintain its value at 1 and cannot be cleared by software. That is to
Jul. 20, 2018 Page 167 of 276 Rev. 1.06
N76E003 Datasheet
clear SI flag does not clear I2C bus error as well. When using SI flag to determine I2C status and flow,
use following steps to enhance the reliability of the system.
Solution:
– If the STOP condition is invalid, disable the I2C bus and then restart the communication.
For example:
while(SI != 0)
{
if (I2STAT == 0x00)
{
STO = 1; // Check bus status if bus error,first send stop
}
SI = 0;
if(SI!=0) // If SI still keep 1
{
I2CEN = 0; // please first disable I2C.
I2CEN = 1 ; // Then enable I2C for clear SI.
SI = 0;
I2CEN = 0; // At last disable I2C for next a new transfer
}
}
2
15.4 Typical Structure of I C Interrupt Service Routine
TM
The following software example in C language for KEIL C51 compiler shows the typical structure of
2
the I C interrupt service routine including the 26 state service routines and may be used as a base for
user applications. User can follow or modify it for their own application. If one or more of the five
modes are not used, the associated state service routines may be removed, but care should be taken
that a deleted routine can never be invoked.
STO = 1;
AA = 1;
break;
case 0x50: /*50H, DATA received, ACK
transmitted*/
DATA_RECEIVED1 = I2DAT; //store received DATA
if (To_RX_Last_Data1) //if last DATA will be received
AA = 0; //not ACK next received DATA
else //if continuing receiving DATA
AA = 1;
break;
case 0x58: /*58H, DATA received, NACK
transmitted*/
DATA_RECEIVED_LAST1 = I2DAT;
STO = 1;
AA = 1;
break;
//====================================
//Slave Receiver and General Call Mode
//====================================
case 0x60: /*60H, own SLA+W received, ACK
returned*/
AA = 1;
break;
case 0x68: /*68H, arbitration lost in SLA+W/R
own SLA+W received, ACK returned */
AA = 0; //not ACK next received DATA after
//arbitration lost
STA = 1; //retry to transmit START if bus free
break;
case 0x70: //*70H, General Call received, ACK
returned
AA = 1;
break;
case 0x78: /*78H, arbitration lost in SLA+W/R
General Call received, ACK
returned*/
AA = 0;
STA = 1;
break;
case 0x80: /*80H, previous own SLA+W, DATA
received,
ACK returned*/
DATA_RECEIVED2 = I2DAT;
if (To_RX_Last_Data2)
AA = 0;
else
AA = 1;
break;
case 0x88: /*88H, previous own SLA+W, DATA
received,
AA = 0;
else
AA = 1;
break;
case 0Xc0: /*C0H, previous own SLA+R, DATA
transmitted,
NACK received, not addressed SLAVE
mode
entered*/
AA = 1;
break;
case 0Xc8: /*C8H, previous own SLA+R, last DATA
trans-
mitted, ACK received, not addressed
SLAVE
AA = 1; mode entered*/
break;
}//end of switch (I2STAT)
2
15.5 I C Time-Out
2
There is a 14-bit time-out counter, which can be used to deal with the I C bus hang-up. If the time-out
counter is enabled, the counter starts up counting until it overflows. Meanwhile I2TOF will be set by
2
hardware and requests I C interrupt. When time-out counter is enabled, setting flag SI to high will
2
reset counter and restart counting up after SI is cleared. If the I C bus hangs up, it causes the SI flag
not set for a period. The 14-bit time-out counter will overflow and require the interrupt service.
FSYS 0
14-bit I2C Time-out Counter I2TOF
1/4 1
Clear Counter
DIV
I2CEN
I2TOCEN
SI
2
Figure 15.12. I C Time-Out Counter
2
I2TOC – I C Time-out Counter
7 6 5 4 3 2 1 0
- - - - - I2TOCEN DIV I2TOF
- - - - - R/W R/W R/W
Address: BFH Reset value: 0000 0000b
2
15.6 I C Interrupt
2 2
There are two I C flags, SI and I2TOF. Both of them can generate an I C event interrupt requests. If
2 2
I C interrupt mask is enabled via setting EI2C (EIE.0) and EA as 1, CPU will execute the I C interrupt
service routine once any of these two flags is set. User needs to check flags to determine what event
2
caused the interrupt. Both of I C flags are cleared by software.
The N76E003 provides pin interrupt input for each I/O pin to detect pin state if button or keypad set is
used. A maximum 8-channel pin interrupt detection can be assigned by I/O port sharing. The pin
interrupt is generated when any key is pressed on a keyboard or keypad, which produces an edge or
level triggering event. Pin interrupt may be used to wake the CPU up from Idle or Power-down mode.
Each channel of pin interrupt can be enabled and polarity controlled independently by PIPEN and
PINEN register. PICON selects which port that the pin interrupt is active. It also defines which type of
pin interrupt is us– d – level detect or edge detect. Each channel also has its own interrupt flag. There
are total eight pin interrupt flags located in PIF register. The respective flags for each pin interrupt
channel allow the interrupt service routine to poll on which channel on which the interrupt event
occurs. All flags in PIF register are set by hardware and should be cleared by software.
PIPS[1:0]
(PICON[1:0])
00
P0.0
01 0
P1.0
P2.0
10 PIF0
11 PIT0 1
P3.0 PINEN0
PIPEN0
Pin Interrupt Channel 0
00
P0.1
01 0
P1.1
Reserved
10 PIF1
11 PIT1 1
Reserved PINEN1
PIPEN1
Pin Interrupt Channel 1
Pin Interrupt
00
P0.7
01 0
P1.7
Reserved
10 PIF7
11 PIT67 1
Reserved PINEN7
PIPEN7
Pin Interrupt Channel 7
Pin interrupt is generally used to detect an edge transient from peripheral devices like keyboard or
keypad. During idle state, the system prefers to enter Power-down mode to minimize power
consumption and waits for event trigger. Pin interrupt can wake up the device from Power-down mode.
The PWM (Pulse Width Modulation) signal is a useful control solution in wide application field. It can
used on motor driving, fan control, backlight brightness tuning, LED light dimming, or simulating as a
simple digital to analog converter output through a low pass filter circuit.
The N76E003 PWM is especially designed for motor control by providing three pairs, maximum 16-bit
resolution of PWM output with programmable period and duty. The architecture makes user easy to
drive the one-phase or three-phase brushless DC motor (BLDC), or three-phase AC induction motor.
Each of six PWM can be configured as one of independent mode, complementary mode, or
synchronous mode. If the complementary mode is used, a programmable dead-time insertion is
available to protect MOS turn-on simultaneously. The PWM waveform can be edge-aligned or center-
aligned with variable interrupt points.
The PWM generator is clocked by the system clock or Timer 1 overflow divided by a PWM clock pre-
scalar selectable from 1/1~1/128. The PWM period is defined by effective 16-bit period registers,
{PWMPH, PWMPL}. The period is the same for all PWM channels for they share the same 16-bit
period counter. The duty of each PWM is determined independently by the value of duty registers
{PWM0H, PWM0L}, {PWM1H, PWM1L}, {PWM2H, PWM2L}, {PWM3H, PWM3L}, {PWM4H, PWM4L},
and {PWM5H, PWM5L}. With six duty registers, six PWM output can be generated independently with
different duty cycles. The interval and duty of PWM signal is generated by a 16-bit counter comparing
with the period and duty registers.
To facilitate the three-phase motor control, a group mode can be used by setting GP (PWMCON1.5),
which makes {PWM0H, PWM0L} and {PWM1H, PWM1L} duty register decide duties of the PWM
outputs. In a three-phase motor control application, two-group PWM outputs generally are given the
same duty cycle. When the group mode is enabled, {PWM2H, PWM2L}, {PWM3H, PWM3L},
{PWM4H, PWM4L} and {PWM5H, PWM5L} registers have no effect. This mean is {PWM2H, PWM2L}
and {PWM4H, PWM4L} both as same as {PWM0H, PWM0L}. Also {PWM3H, PWM3L} and {PWM5H,
PWM5L} are same as {PWM1H, PWM1L}.
Note that enabling PWM does not configure the I/O pins into their output mode automatically. User
should configure I/O output mode via software manually.
LOAD (PWMCON0.6)
PWMRUN
(PWMCON0.7) 16-bit clear counter
up/down CLRPWM
Interrupt INTSEL[1:0], INTTYP[1:0]
FSYS 0 FPWM counter (PWMCON0.4) select/type (PWMCON0[3:0])
Pre-scalar edge/center
Timer 1 overflow 1
PWMCKS PWMDIV0[2:0]
PWMTYP PG0
(CKCON.6) (PWMCON1[2:0])
(PWMCON1.4) = PWM0/P1.2
PWM0 buffer
(PWM0H,
PWM0L) PWM0 Register
PG1
= PWM1/P1.1/P1.4
PWM1 buffer
(PWM1H,
PWM1L) PWM1 Register
= 0 PG2 PWM2/P0.5/P1.0
1
PWM2 buffer
PWM and
Fault Brake
output
(PWM2H, control
PWM2L) PWM2 Register
= 0 PG3 PWM3/P0.0/P0.4
1
PWM3 buffer
(PWM3H,
PWM3L) PWM3 Register
= 0 PG4 PWM4/P0.1
1
PWM4 buffer
(PWM4H,
PWM4L) PWM4 Register
= 0 PG5 PWM5/P0.3/P1.5
1
PWM5 buffer
GP
(PWMCON1.5) Brake event
(PWM5H, (P1.4/FB)
PWM5L) PWM5 Register
The PWM counter generates six PWM signals called PG0, PG1, PG2, PG3, PG4, and PG5. These
signals will go through the PWM and Fault Brake output control circuit. It generates real PWM outputs
on I/O pins. The output control circuit determines the PWM mode, dead-time insertion, mask output,
Fault Brake control, and PWM polarity. The last stage is a multiplexer of PWM output or I/O function.
User should set the PIOn bit to make the corresponding pin function as PWM output. Meanwhile, the
general purpose I/O function can be used.
PMEN0 P1.2 0
PNP0
PG0_DT PWM0/P1.2
PG0 0 0 1
0
PMD0 1
FBD0 1
PIO01
PWM0/1 1
PWM0/1 P1.1
dead 0
mode
time PWM1/P1.1
PG1 1
PG1_DT
P1.4 0
0 0
PMD1 FBD1 0 PWM1/P1.4
1 1 1
1
PMEN1 PIO11
PNP1
PIO02
P0.5 0
PMEN2
PWM2/P0.5
PG2_DT 1
PNP2
PG2 0
P1.0
0 0
PMD2
PWM2/3
1
FBD2
0 PWM2/P1.0
1 1
PWM2/3
dead 1
mode PIO12
time
PG3 PG3_DT
PIO03
0
P0.0 0
PMD3 0
1
FBD3 0 PWM3/P0.0
1 1
PMEN3
1
P0.4 0
PNP3
PWM3/P0.4
1
PIO13
PMEN4 PIO04
PNP4
PG4_DT
P0.1
PG4 0 0 0
PMD4 FBD4
0 PWM4/P0.1
1 1 1
PWM4/5 1
PWM4/5 PIO05
dead
mode
time P0.3 0
PG5 PG5_DT PWM5/P0.3
0 0 1
PMD5 0
1
FBD5 1
P1.5 0
PMEN5 1 PWM5/P1.5
1
PNP5
PIO15
BRK
PWMMOD[1:0] FBINEN
(PWMCON1[7:6]) PDTEN, PDTCNT PMEN, PMD FBD (PWMCON1.3) PNP PIOCON1,PIOCON0
Brake event
(P1.4/FB)
Figure 17.2. PWM and Fault Brake Output Control Block Diagram
User should follow the initialization steps below to start generating the PWM signal output. In the first
step by setting CLRPWM (PWMCON0.4), it ensures the 16-bit up counter reset for the accuracy of the
first duration. After initialization and setting {PWMPH, PWMPL} and all {PWMnH, PWMnL} registers,
PWMRUN (PWMCON0.7) can be set as logic 1 to trigger the 16-bit counter running. PWM starts to
generate waveform on its output pins. The hardware for all period and duty control registers are
double buffered designed. Therefore, {PWMPH, PWMPL} and all {PWMnH, PWMnL} registers can be
written to at any time, but the period and duty cycle of PWM will not be updated immediately until the
LOAD (PWMCON0.6) is set and previous period is complete. This prevents glitches when updating
the PWM period or duty.
A loading of new period and duty by setting LOAD should be ensured complete by monitoring
it and waiting for a hardware automatic clearing LOAD bit. Any updating of PWM control
registers during LOAD bit as logic 1 will cause unpredictable output.
The PWM generator provides two PWM types: edge-aligned or center-aligned. PWM type is selected
by PWMTYP (PWMCON1.4).
In edge-aligned mode, the 16-bit counter uses single slop operation by counting up from 0000H to
{PWMPH, PWMPL} and then starting from 0000H. The PWM generator signal (PGn before PWM and
Fault Brake output control) is cleared on the compare match of 16-bit counter and the duty register
{PWMnH, PWMnL} and set at the 16-bit counter is 0000H. The result PWM output waveform is left-
edge aligned.
PWMP (2nd)
PWMP (1st)
12-bit counter
PWM01 (2nd)
PWM01 (1st)
PWM01 (2nd)
duty valid
PG01 output
The output frequency and duty cycle for edge-aligned PWM are given by following equations:
FPWM
PWM frequency = (FPWM is the PWM clock source frequency divided by
{PWMPH,PWMPL} 1
PWMDIV).
{PWMnH,PWMnL}
PWM high level duty = .
{PWMPH,PWMPL} 1
In center-aligned mode, the 16-bit counter use dual slop operation by counting up from 0000H to
{PWMPH, PWMPL} and then counting down from {PWMPH, PWMPL} to 0000H. The PGn signal is
cleared on the up-count compare match of 16-bit counter and the duty register {PWMnH, PWMnL} and
set on the down-count compare match. Center-aligned PWM may be used to generate non-
overlapping waveforms.
PWMP (2nd)
PWMP (1st)
12-bit counter
PWM01 (2nd)
PWM01 (1st)
PWM01 (2nd)
duty valid
PG01 output
The output frequency and duty cycle for center-aligned PWM are given by following equations:
FPWM
PWM frequency = (FPWM is the PWM clock source frequency divided by
2 × {PWMPH,PWMPL}
PWMDIV).
{PWMnH,PWMnL}
PWM high level duty = .
{PWMPH,PWMPL}
After PGn signals pass through the first stage of the PWM and Fault Brake output control circuit. The
PWM mode selection circuit generates different kind of PWM output modes with six-channel, three-
pair signal PG0~PG5 . It supports independent mode, complementary mode, and synchronous mode.
Independent mode is enabled when PWMMOD[1:0] (PWMCON1[7:6]) is [0:0]. It is the default mode of
PWM. PG0, PG1, PG2, PG3, PG4 and PG5 output PWM signals independently.
Complementary mode is enabled when PWMMOD[1:0] = [0:1]. In this mode, PG0/2/4 output PWM
signals the same as the independent mode. However, PG1/3/5 output the out-phase PWM signals of
PG0/2/4 correspondingly, and ignore PG1/3/5 Duty register {PWMnH, PWMnL} (n:1/3/5). This mode
makes PG0/PG1 a PWM complementary pair and so on PG2/PG3 and PG4/PG5.
n a real motor application, a complementary PW output always has a need of “dead-time” insertion
to prevent damage of the power switching device like GPIBs due to being active on simultaneously of
the upper and lower switches of the half bridge, even in a “μs” duration. For a power switch device
physically cannot switch on/off instantly. For the N76E003 PWM, each PWM pair share a 9-bit dead-
time down-counter PDTCNT used to produce the off time between two PWM signals in the same pair.
On implementation, a 0-to-1 signal edge delays after PDTCNT timer underflows. The timing diagram
illustrates the complementary mode with dead-time insertion of PG0/PG1 pair. Pairs of PG2/PG3 and
PG4/PG5 have the same dead-time circuit. Each pair has its own dead-time enabling bit in the field of
PDTEN[3:0].
Note that the PDTCNT and PDTEN registers are all TA write protection. The dead-time control are
also valid only when the PWM is configured in its complementary mode.
PG0
PG1
PG0_DT
PG1_DT
Synchronous mode is enabled when PWMMOD[1:0] = [1:0]. In this mode, PG0/2/4 output PWM
signals the same as the independent mode. PG1/3/5 output just the same in-phase PWM signals of
PG02/4 correspondingly.
Each PWM signal can be software masked by driving a specified level of PWM signal. The PWM
mask output function is quite useful when controlling Electrical Commutation Motor like a BLDC.
PMEN contains six bits, those determine which channel of PWM signal will be masked. PMD set the
individual mask level of each PWM channel. The default value of PMEN is 00H, which makes all
outputs of PWM channels follow signals from PWM generator. Note that the masked level is reversed
or not by PNP setting on PWM output pins.
The Fault Brake function is usually implemented in conjunction with an enhanced PWM circuit. It rules
as a fault detection input to protect the motor system from damage. Fault Brake pin input (FB) is valid
when FBINEN (PWMCON1.3) is set. When Fault Brake is asserted PWM signals will be individually
overwritten by FBD corresponding bits. PWMRUN (PWMCON0.7) will also be automatically cleared by
hardware to stop PWM generating. The PWM 16-bit counter will also be reset as 0000H. A indicating
flag FBF will be set by hardware to assert a Fault Brake interrupt if enabled. FBD data output remains
even after the FBF is cleared by software. User should resume the PWM output only by setting
PWMRUN again. Meanwhile the Fault Brake state will be released and PWM waveform outputs on
pins as usual. Fault Brake input has a polarity selection by FBINLS (FBD.6) bit. Note that the Fault
Brake signal feed in FB pin should be longer than eight-system-clock time for FB pin input has a
permanent 8/FSYS de-bouncing, which avoids fake Fault Brake event by input noise. The other path to
trigger a Fault Brake event is the ADC compare event. It asserts the Fault Brake behavior just the
same as FB pin input. See Sector 18.1.3 “ADC Conversion Result Comparator” on page 198.
0
FB (P1.4) De-bounce
1
FBINLS
FBINEN
Fault Brake event
ADC comparator FBF Fault Brake interrupt
ADC compare event
Each PWM output channel has its independent polarity control bit, PNP0~PNP5. The default is high
active level on all control fields implemented with positive logic. It means the power switch is ON when
PWM outputs high level and OFF when low level. User can easily configure all setting with positive
logic and then set PNP bit to make PWM actually outputs according to the negative logic.
The PWM module has a flag PWMF (PWMCON0.5) to indicate certain point of each complete PWM
period. The indicating PWM channel and point can be selected by INTSEL[2:0] and INTTYP[1:0]
(PWMINTC[2:0] and [5:4]). Note that the center point and the end point interrupts are only available
when PWM operates in its center-aligned type. PWMF is cleared by software.
The PWM interrupt related with PWM waveform is shown as figure below.
Fault Brake event requests another interrupt, Fault Brake interrupt. It has different interrupt vector from
PWM interrupt. When either Fault Brake pin input event or ADC compare event occurs, FBF (FBD.7)
will be set by hardware. It generates Fault Brake interrupt if enabled. The Fault Brake interrupt enable
bit is EFB (EIE.5). FBF Is cleared via software.
The N76E003 is embedded with a 12-bit SAR ADC. The ADC (analog-to-digital converter) allows
conversion of an analog input signal to a 12-bit binary representation of that signal. The N76E003 is
selected as 8-channel inputs in single end mode. The internal band-gap voltage also can be the
internal ADC input. The analog input, multiplexed into one sample and hold circuit, charges a sample
and hold capacitor. The output of the sample and hold capacitor is the input into the converter. The
converter then generates a digital result of this analog level via successive approximation and stores
the result in the result registers.
VDD
AIN0
VREF
0000
AIN1 0001
AIN2 0010
AIN3 0011 ADCF ADC interrupt
AIN4 0100 12-bit SAR
AIN5 0101
AIN6
ADC 12
0110
AIN7 0111
Internal band-gap 1000
A/D convertion start
ADCRH ADCRL
ADCEN
ADC result
ADCHS[3:0] comparator
ADCS
External Trigger
[00]
PWM0 00
[01]
PWM2 01
0 ADCDLY
P0.4 PWM4 10
11
[10] ADCEX
P1.3 1
STADC
[11]
STADCPX ETGSEL[1:0]
(ADCCON0[5:4])
ETGTYP[1:0]
(ADCCON1[3:2])
Before ADC operation, the ADC circuit should be enabled by setting ADCEN (ADCCON1.0). This
makes ADC circuit active. It consume extra power. Once ADC is not used, clearing ADCEN to turn off
ADC circuit saves power.
The ADC analog input pin should be specially considered. ADCHS[2:0] are channel selection bits that
control which channel is connected to the sample and hold circuit. User needs to configure selected
ADC input pins as input-only (high impedance) mode via respective bits in PxMn registers. This
configuration disconnects the digital output circuit of each selected ADC input pin. But the digital input
circuit still works. Digital input may cause the input buffer to induce leakage current. To disable the
digital input buffer, the respective bits in AINDIDS should be set. Configuration above makes selected
ADC analog input pins pure analog inputs to allow external feeding of the analog voltage signals. Also,
the ADC clock rate needs to be considered carefully. The ADC maximum clock frequency is listed in
Table 31-9. ADC Electrical Characteristics Clock above the maximum clock frequency degrades ADC
performance unpredictably.
An A/D conversion is initiated by setting the ADCS bit (ADCCON0.6). When the conversion is
complete, the hardware will clear ADCS automatically, set ADCF (ADCCON0.7) and generate an
interrupt if enabled. The new conversion result will also be stored in ADCRH (most significant 8 bits)
VAIN
4095×
and ADCRL (least significant 4 bits). The 12-bit ADC result value is
VREF .
By the way, digital circuitry inside and outside the device generates noise which might affect the
accuracy of ADC measurements. If conversion accuracy is critical, the noise level can be reduced by
applying the following techniques:
1. Keep analog signal paths as short as possible. Make sure to run analog signals tracks well away
from high-speed digital tracks.
3. If any AIN pins are used as digital outputs, it is essential that these do not switch while a conversion
is in progress.
Besides setting ADCS via software, the N76E003 is enhanced by supporting hardware triggering
method to start an A/D conversion. If ADCEX (ADCCON1.1) is set, edges or period points on selected
PWM channel or edges of STADC pin will automatically trigger an A/D conversion. (The hardware
trigger also sets ADCS by hardware.) For application flexibility, STADC pin can be exchanged by
STADCPX (ADCCON1.6).
[00]
PWM0 00
[01]
PWM2 01
ADCDLY External Trigger
PWM4 10
[10]
STADC 11
[11]
ETGSEL[1:0]
(ADCCON0[5:4])
ETGTYP[1:0]
(ADCCON1[3:2])
The N76E003 ADC has a digital comparator, which compares the A/D conversion result with a 12-bit
constant value given in ACMPH and ACMPL registers. The ADC comparator is enabled by setting
ADCMPEN (ADCCON2.5) and each compare will be done on every A/D conversion complete
moment. ADCMPO (ADCCON2.4) shows the compare result according to its output polarity setting bit
ADCMPOP (ADCCON2.6). The ADC comparing result can trigger a PWM Fault Brake output directly.
This function is enabled when ADFBEN (ADCCON2.7). When ADCMPO is set, it generates a ADC
compare event and asserts Fault Brake. Please also see Sector 18.1.5“Fault Brake” on page 129.
ADCMPO
ADCR[11:0] + 0 (ADCCON2.4)
ADC compare event
ADCMP[11:0] - 1 ADFBEN
(ADCCON2.7)
ADCMPOP
ADCMPEN (ADCCON2.6)
(ADCCON2.5)
At room temperature, all N76E003 band-gap voltage values will be calibrated within the range of
1.17V to 1.30V. If you want to get the actual band-gap value for N76E003, read the 2 bytes value after
the UID address and the actually valid bit is 12. The first byte is the upper 8 bits, and the lower 4 bits
of the second byte are the lower 4 bits of the 12 bit.
Formula as following
For example:
Read the 2 bytes value after the UID address, wherein the first byte value is 0x64, and the second
byte value is 0x0E, merged as 0x64E = 1614. The conversion result is as follows:
#define set_IAPEN
BIT_TMP=EA;EA=0;TA=0Xaa;TA=0x55;CHPCON|=SET_BIT0 ;EA=BIT_TMP
#define set_IAPGO
BIT_TMP=EA;EA=0;TA=0Xaa;TA=0x55;IAPTRG|=SET_BIT0 ;EA=BIT_TMP
#define clr_IAPEN
BIT_TMP=EA;EA=0;TA=0Xaa;TA=0x55;CHPCON&=~SET_BIT0;EA=BIT_TMP
void READ_BANDGAP()
{
UINT8 BandgapHigh,BandgapLow;
Set_IAPEN; // Enable IAPEN
IAPAL = 0x0C;
IAPAH = 0x00;
IAPCN = 0x04;
set_IAPGO; // Trig set IAPGO
Jul. 20, 2018 Page 199 of 276 Rev. 1.06
N76E003 Datasheet
BandgapHigh = IAPFD;
IAPAL = 0x0d;
IAPAH = 0x00;
IAPCN = 0x04;
set_IAPGO; // Trig set IAPGO
BandgapLow = IAPFD;
BandgapLow = BandgapLow&0x0F;
Clr_IAPEN; // Disable IAPEN
Bandgap_Value = (BandgapHigh<<4)+BandgapLow;
Bandgap_Voltage = 3072/(0x1000/Bandgap_Value);
}
N76E003 internal embedded band-gap voltage also can be the internal ADC input. This input is useful
to measure Vref value then means can know the VDD value from ADC convert result. For a more
accuracy result when band-gap as ADC input, always give up the first three times convert data in
register after ADC enable and suggest add 20ms delay for a better result.
Double Bandgap_Voltage,VDD_Voltage;
void ADC_Bypass (void) // The first three times convert should be
bypass
{
unsigned char ozc;
for (ozc=0;ozc<0x03;ozc++)
{
clr_ADCF;
set_ADCS;
while(ADCF == 0);
}
}
void main (void)
{
double bgvalue;
READ_BANDGAP();
Enable_ADC_BandGap;
ADC_Bypass();
clr_ADCF;
set_ADCS;
while(ADCF == 0);
Jul. 20, 2018 Page 200 of 276 Rev. 1.06
N76E003 Datasheet
The N76E003 has several features such as WDT and Brown-out detection that are crucial to proper
operation of the system. If leaving these control registers unprotected, errant code may write
undetermined value into them and results in incorrect operation and loss of control. To prevent this
risk, the N76E003 has a protection scheme, which limits the write access to critical SFRs. This
protection scheme is implemented using a timed access (TA). The following registers are related to
the TA process.
TA – Timed Access
7 6 5 4 3 2 1 0
TA[7:0]
W
Address: C7H Reset value: 0000 0000b
In timed access method, the bits, which are protected, have a timed write enable window. A write is
successful only if this window is active, otherwise the write will be discarded. When the software writes
AAH to TA, a counter is started. This counter waits for 3 clock cycles looking for a write of 55H to TA.
If the second write of 55H occurs within 3 clock cycles of the first write of AAH, then the timed access
window is opened. It remains open for 4 clock cycles during which user may write to the protected bits.
After 4 clock cycles, this window automatically closes. Once the window closes, the procedure should
be repeated to write another protected bits. Not that the TA protected SFRs are required timed access
for writing but reading is not protected. User may read TA protected SFR without giving AAH and 55H
to TA register. The suggestion code for opening the timed access window is shown below.
Any enabled interrupt should be disabled during this procedure to avoid delay between these three
writings. If there is no interrupt enabled, the CLR EA and SETB EA instructions can be left out.
Examples of timed assess are shown to illustrate correct or incorrect writing process.
Example 1,
MOV TA,#0AAH ;3 clock cycles
MOV TA,#55H ;3 clock cycles
ORL WDCON,#data ;4 clock cycles
Example 2,
MOV TA,#0AAH ;3 clock cycles
MOV TA,#55H ;3 clock cycles
NOP ;1 clock cycle
ANL BODCON0,#data ;4 clock cycles
Example 3,
MOV TA,#0AAH ;3 clock cycles
MOV TA,#55H ;3 clock cycles
MOV WDCON,#data1 ;3 clock cycles
ORL BODCON0,#data2 ;4 clock cycles
Example 4,
MOV TA,#0AAH ;3 clock cycles
NOP ;1 clock cycle
MOV TA,#55H ;3 clock cycles
ANL BODCON0,#data ;4 clock cycles
In the first example, the writing to the protected bits is done before the 3-clock-cycle window closes. In
example 2, however, the writing to BODCON0 does not complete during the window opening, there
will be no change of the value of BODCON0. In example 3, the WDCON is successful written but the
BODCON0 write is out of the 3-clock-cycle window. Therefore, the BODCON0 value will not change
either. In Example 4, the second write 55H to TA completes after 3 clock cycles of the first write TA of
AAH, and thus the timed access window is not opened at all, and the write to the protected byte
affects nothing.
The purpose of the interrupt is to make the software deal with unscheduled or asynchronous events.
The N76E003 has a four-priority-level interrupt structure with 18 interrupt sources. Each of the
interrupt sources has an individual priority setting bits, interrupt vector and enable bit. In addition, the
interrupts can be globally enabled or disabled. When an interrupt occurs, the CPU is expected to
service the interrupt. This service is specified as an Interrupt Service Routine (ISR). The ISR resides
at a predetermined address as shown in Table 20-1. Interrupt Vectors. When the interrupt occurs if
enabled, the CPU will vector to the respective location depending on interrupt source, execute the
code at this location, stay in an interrupt service state until the ISR is done. Once an ISR has begun, it
can be interrupted only by a higher priority interrupt. The ISR should be terminated by a return from
interrupt instruction RETI. This instruction will force the CPU return to the instruction that would have
been next when the interrupt occurred.
Each of individual interrupt sources can be enabled or disabled through the use of an associated
interrupt enable bit in the IE and EIE SFRs. There is also a global enable bit EA bit (IE.7), which can
be cleared to disable all the interrupts at once. It is set to enable all individually enabled interrupts.
Setting the EA bit to logic 0 disables all interrupt sources regardless of the individual interrupt-enable
settings. Note that interrupts which occur when the EA bit is set to logic 0 will be held in a pending
state, and will not be serviced until the EA bit is set back to logic 1. All interrupt flags that generate
interrupts can also be set via software. Thereby software initiated interrupts can be generated.
Note that every interrupts, if enabled, is generated by a setting as logic 1 of its interrupt flag no matter
by hardware or software. User should take care of each interrupt flag in its own interrupt service
routine (ISR). Most of interrupt flags should be cleared by writing it as logic 0 via software to avoid
recursive interrupt requests.
There are four priority levels for all interrupts. They are level highest, high, low, and lowest; and they
are represented by level 3, level 2, level 1, and level 0. The interrupt sources can be individually set to
one of four priority levels by setting their own priority bits. Table 20-2. Interrupt Priority Level Setting
lists four priority setting. Naturally, a low level priority interrupt can itself be interrupted by a high level
priority interrupt, but not by any same level interrupt or lower level. In addition, there exists a pre-
defined natural priority among the interrupts themselves. The natural priority comes into play when the
interrupt controller has to resolve simultaneous requests having the same priority level.
1. While a low priority interrupt handler is running, if a high priority interrupt arrives, the handler will be
interrupted and the high priority handler will run. When the high priority handler does “ E ”, the low
priority handler will resume. When this handler does “ E ”, control is passed back to the main
program.
2. If a high priority interrupt is running, it cannot be interrupted by any other source – even if it is a high
priority interrupt which is higher in natural priority.
3. A low-priority interrupt handler will be invoked only if no other interrupt is already executing. Again,
the low priority interrupt cannot preempt another low priority interrupt, even if the later one is higher in
natural priority.
4. If two interrupts occur at the same time, the interrupt with higher priority will execute first. If both
interrupts are of the same priority, the interrupt which is higher in natural priority will be executed first.
This is the only context in which the natural priority matters.
This natural priority is defined as shown on Table 20-3. Characteristics of Each Interrupt Source. It
also summarizes the interrupt sources, flag bits, vector addresses, enable bits, priority bits, natural
priority and the permission to wake up the CPU from Power-down mode. For details of waking CPU up
from Power-down mode, please see Section 22.1 “Power-Down Mode” on page 231.
The interrupt flags are sampled every system clock cycle. In the same cycle, the sampled interrupts
are polled and their priority is resolved. If certain conditions are met then the hardware will execute an
internally generated LCALL instruction, which will vector the process to the appropriate interrupt vector
address. The conditions for generating the LCALL are,
2. The current polling cycle is the last cycle of the instruction currently being executed.
3. The current instruction does not involve a write to any enabling or priority setting bits and is not a
RETI.
If any of these conditions are not met, then the LCALL will not be generated. The polling cycle is
repeated every system clock cycle. If an interrupt flag is active in one cycle but not responded to for
the above conditions are not met, if the flag is not still active when the blocking condition is removed,
the denied interrupt will not be serviced. This means that the interrupt flag, which was once active but
not serviced is not remembered. Every polling cycle is new.
The processor responds to a valid interrupt by executing an LCALL instruction to the appropriate
service routine. This action may or may not clear the flag, which caused the interrupt according to
different interrupt source. The hardware LCALL behaves exactly like the software LCALL instruction.
This instruction saves the Program Counter contents onto the Stack RAM but does not save the
Program Status Word (PSW). The PC is reloaded with the vector address of that interrupt, which
caused the LCALL. Execution continues from the vectored address until an RETI instruction is
executed. On execution of the RETI instruction, the processor pops the Stack and loads the PC with
the contents at the top of the stack. User should take care that the status of the stack. The processor
does not notice anything if the stack contents are modified and will proceed with execution from the
address put back into PC. Note that a simple RET instruction would perform exactly the same process
as a RETI instruction, but it would not inform the Interrupt controller that the interrupt service routine is
completed. RET would leave the controller still thinking that the service routine is underway, making
future interrupts impossible.
The response time for each interrupt source depends on several factors, such as the nature of the
interrupt and the instruction underway. Each interrupt flags are polled and priority decoded each
system clock cycle. If a request is active and all three previous conditions are met, then the hardware
generated LCALL is executed. This LCALL itself takes 4 clock cycles to be completed. Thus, there is a
minimum reaction time of 5 clock cycles between the interrupt flag being set and the interrupt service
routine being executed.
A longer response time should be anticipated if any of the three conditions are not met. If a higher or
equal priority is being serviced, then the interrupt latency time obviously depends on the nature of the
service routine currently being executed. If the polling cycle is not the last clock cycle of the instruction
being executed, then an additional delay is introduced. The maximum response time (if no other
interrupt is currently being serviced or the new interrupt is of greater priority) occurs if the device is
performing a RETI, and then executes a longest 6-clock-cycle instruction as the next instruction. From
the time an interrupt source is activated (not detected), the longest reaction time is 16 clock cycles.
This period includes 5 clock cycles to complete RETI, 6 clock cycles to complete the longest
instruction, 1 clock cycle to detect the interrupt, and 4 clock cycles to complete the hardware LCALL to
the interrupt vector location.
Thus in a single-interrupt system the interrupt response time will always be more than 5 clock cycles
and not more than 16 clock cycles.
The external interrupt ̅̅̅̅̅̅̅ and ̅̅̅̅̅̅̅ can be used as interrupt sources. They are selectable to be
either edge or level triggered depending on bits IT0 (TCON.0) and IT1 (TCON.2). The bits IE0
(TCON.1) and IE1 (TCON.3) are the flags those are checked to generate the interrupt. In the edge
triggered mode, the ̅̅̅̅̅̅̅ or ̅̅̅̅̅̅̅ inputs are sampled every system clock cycle. If the sample is high in
one cycle and low in the next, then a high to low transition is detected and the interrupts request flag
IE0 or IE1 will be set. Since the external interrupts are sampled every system clock, they have to be
held high or low for at least one system clock cycle. The IE0 and IE1 are automatically cleared when
the interrupt service routine is called. If the level triggered mode is selected, then the requesting
Jul. 20, 2018 Page 217 of 276 Rev. 1.06
N76E003 Datasheet
source has to hold the pin low till the interrupt is serviced. The IE0 and IE1 will not be cleared by the
hardware on entering the service routine. In the level triggered mode, IE0 and IE1 follows the inverse
value of ̅̅̅̅̅̅̅ and ̅̅̅̅̅̅̅ pins. If interrupt pins continue to be held low even after the service routine is
completed, the processor will acknowledge another interrupt request from the same source. Both ̅̅̅̅̅̅̅
and ̅̅̅̅̅̅̅ can wake up the device from the Power-down mode.
Unlike A ’s real-time operation, to update flash data often takes long time. Furthermore, it is a quite
complex timing procedure to erase, program, or read flash data. The N76E003 carried out the flash
operation with convenient mechanism to help user re-programming the flash content by In-Application-
Programming (IAP). IAP is an in-circuit electrical erasure and programming method through software.
After IAP enabling by setting IAPEN (CHPCON.0 with TA protected) and setting the enable bit in
IAPUEN that allows the target block to be updated, user can easily fill the 16-bit target address in
IAPAH and IAPAL, data in IAPFD, and command in IAPCN. Then the IAP is ready to begin by setting
a triggering bit IAPGO (IAPTRG.0). Note that IAPTRG is also TA protected. At this moment, the CPU
holds the Program Counter and the built-in IAP automation takes over to control the internal charge-
pump for high voltage and the detail signal timing. The erase and program time is internally controlled
disregard of the operating voltage and frequency. Nominally, a page-erase time is 5 ms and a byte-
program time is 23.5 μs. After IAP action completed, the Program Counter continues to run the
following instructions. The IAPGO bit will be automatically cleared. An IAP failure flag, IAPFF
(CHPCON.6), can be check whether the previous IAP operation was successful or not. Through this
progress, user can easily erase, program, and verify the Flash Memory by just taking care of pure
software.
CONFIG2
7 6 5 4 3 2 1 0
CBODEN - CBOV[1:0] BOIAP CBORST - -
R/W - R/W R/W R/W - -
Factory default value: 1111 1111b
The N76E003 provides a wide range of applications to perform IAP to APROM, LDROM, or CONFIG
bytes. The IAP action mode and the destination of the flash block are defined by IAP control register
IAPCN.
IAPCN IAPA[15:0]
IAP Mode IAPFD[7:0]
IAPB[1:0] FOEN FCEN FCTRL[3:0] {IAPAH, IAPAL}
IAPCN IAPA[15:0]
IAP Mode IAPFD[7:0]
IAPB[1:0] FOEN FCEN FCTRL[3:0] {IAPAH, IAPAL}
IAP facilitates the updating flash contents in a convenient way; however, user should follow some
restricted laws in order that the IAP operates correctly. Without noticing warnings will possible cause
undetermined results even serious damages of devices. Furthermore, this paragraph will also support
useful suggestions during IAP procedures.
(1) If no more IAP operation is needed, user should clear IAPEN (CHPCON.0). It will make the system
void to trigger IAP unaware. Furthermore, IAP requires the HIRC running. If the external clock source
is selected, disabling IAP will stop the HIRC for saving power consumption. Note that a write to IAPEN
is TA protected.
(2) When the LOCK bit (CONFIG0.1) is activated, IAP reading, writing, or erasing can still be valid.
During IAP progress, interrupts (if enabled) should be disabled temporally by clearing EA bit
for implement limitation.
Do not attempt to erase or program to a page that the code is currently executing. This will
cause unpredictable program behavior and may corrupt program data.
In general application, there is a need of data storage, which is non-volatile so that it remains its
content even after the power is off. Therefore, in general application user can read back or update the
data, which rules as parameters or constants for system control. The Flash Memory array of the
N76E003 supports IAP function and any byte in the Flash Memory array may be read using the MOVC
instruction and thus is suitable for use as non-volatile data storage. IAP provides erase and program
function that makes it easy for one or more bytes within a page to be erased and programmed in a
routine. IAP performs in the application under the control of the microcontroller’s firmware. Be aware
of Flash Memory writing endurance of 100,000 cycles. A demo is illustrated as follows.
Jul. 20, 2018 Page 223 of 276 Rev. 1.06
N76E003 Datasheet
;******************************************************************************
; This code illustrates how to use IAP to make APROM 201h as a byte of
; Data Flash when user code is executed in APROM.
;******************************************************************************
PAGE_ERASE_AP EQU 00100010b
BYTE_PROGRAM_AP EQU 00100001b
ORG 0000h
MOV TA,#0Aah
MOV TA,#55h
ANL IAPUEN,#11111110b ;APUEN = 0, disable APROM update
MOV TA,#0Aah
MOV TA,#55h
ANL CHPCON,#11111110b ;IAPEN = 0, disable IAP mode
MOV DPTR,#201h
CLR A
MOVC A,@A+DPTR ;Read content of address 201h
MOV P0,A
SJMP $
//******************************************************************************
// This code illustrates how to use IAP to make APROM 201h as a byte of
// Data Flash when user code is executed in APROM.
//******************************************************************************
#define PAGE_ERASE_AP 0x22
#define BYTE_PROGRAM_AP 0x21
/*Data Flash, as part of APROM, is read by MOVC. Data Flash can be defined as
128-element array in “code” area from absolute address 0x0200 */
Main (void)
{
TA = 0Xaa; //CHPCON is TA protected
TA = 0x55;
CHPCON |= 0x01; //IAPEN = 1, enable IAP mode
while(1);
}
The Flash Memory supports both hardware programming and In-Application-Programming (IAP). If the
product is just under development or the end product needs firmware updating in the hand of an end
user, the hardware programming mode will make repeated programming difficult and inconvenient. In-
System-Programming (ISP) makes it easy and possible. ISP performs Flash Memory updating without
removing the microcontroller from the system. It allows a device to be re-programmed under software
control. Furthermore, the capability to update the application firmware makes wide range of
applications possible.
User can develop a custom Boot Code that resides in LDROM. The maximum size of LDROM is 4K
Bytes. User developed Boot Code can be re-programmed by parallel writer or In-Circuit-Programming
(ICP) tool.
General speaking, an ISP is carried out by a communication between PC and MCU. PC transfers the
new User Code to MCU through serial port. Then Boot Code receives it and re-programs into User
Code through IAP commands. Nuvoton provides ISP firmware and PC application for N76E003. It
makes user quite easy perform ISP through UART port. Please visit Nuvoton 8-bit Microcontroller
website: Nuvoton 80C51 Microcontroller Technical Support. A simple ISP demo code is given below.
;******************************************************************************
; This code illustrates how to do APROM and CONFIG IAP from LDROM.
; APROM are re-programmed by the code to output P1 as 55h and P0 as aah.
; The CONFIG2 is also updated to disable BOD reset.
; User needs to configure CONFIG0 = 0x7F, CONFIG1 = 0Xfe, CONFIG2 = 0Xff.
;******************************************************************************
PAGE_ERASE_AP EQU 00100010b
BYTE_PROGRAM_AP EQU 00100001b
BYTE_READ_AP EQU 00000000b
ALL_ERASE_CONFIG EQU 11100010b
BYTE_PROGRAM_CONFIG EQU 11100001b
BYTE_READ_CONFIG EQU 11000000b
ORG 0000h
CALL Enable_AP_Update
CALL Erase_AP ;erase AP data
CALL Program_AP ;programming AP data
CALL Disable_AP_Update
CALL Program_AP_Verify ;verify Programmed AP data
CALL Disable_IAP
MOV TA,#0Aah ;TA protection
MOV TA,#55h ;
ANL CHPCON,#11111101b ;BS = 0, reset to APROM
MOV TA,#0Aah
Jul. 20, 2018 Page 226 of 276 Rev. 1.06
N76E003 Datasheet
MOV TA,#55h
ORL CHPCON,#80h ;software reset and reboot from APROM
SJMP $
;********************************************************************
; IAP Subroutine
;********************************************************************
Enable_IAP:
MOV TA,#0Aah ;CHPCON is TA protected
MOV TA,#55h
ORL CHPCON,#00000001b ;IAPEN = 1, enable IAP mode
RET
Disable_IAP:
MOV TA,#0Aah
MOV TA,#55h
ANL CHPCON,#11111110b ;IAPEN = 0, disable IAP mode
RET
Enable_AP_Update:
MOV TA,#0Aah ;IAPUEN is TA protected
MOV TA,#55h
ORL IAPUEN,#00000001b ;APUEN = 1, enable APROM update
RET
Disable_AP_Update:
MOV TA,#0Aah
MOV TA,#55h
ANL IAPUEN,#11111110b ;APUEN = 0, disable APROM update
RET
Enable_CONFIG_Update:
MOV TA,#0Aah
MOV TA,#55h
ORL IAPUEN,#00000100b ;CFUEN = 1, enable CONFIG update
RET
Disable_CONFIG_Update:
MOV TA,#0Aah
MOV TA,#55h
ANL IAPUEN,#11111011b ;CFUEN = 0, disable CONFIG update
RET
Trigger_IAP:
MOV TA,#0Aah ;IAPTRG is TA protected
MOV TA,#55h
ORL IAPTRG,#00000001b ;write ‘1’ to IAPGO to trigger IAP process
RET
;********************************************************************
; IAP APROM Function
;********************************************************************
Erase_AP:
MOV IAPCN,#PAGE_ERASE_AP
MOV IAPFD,#0FFh
MOV R0,#00h
Erase_AP_Loop:
MOV IAPAH,R0
MOV IAPAL,#00h
CALL Trigger_IAP
MOV IAPAL,#80h
Jul. 20, 2018 Page 227 of 276 Rev. 1.06
N76E003 Datasheet
CALL Trigger_IAP
INC R0
CJNE R0,#44h,Erase_AP_Loop
RET
Program_AP:
MOV IAPCN,#BYTE_PROGRAM_AP
MOV IAPAH,#00h
MOV IAPAL,#00h
MOV DPTR,#AP_code
Program_AP_Loop:
CLR A
MOVC A,@A+DPTR
MOV IAPFD,A
CALL Trigger_IAP
INC DPTR
INC IAPAL
MOV A,IAPAL
CJNE A,#14,Program_AP_Loop
RET
Program_AP_Verify:
MOV IAPCN,#BYTE_READ_AP
MOV IAPAH,#00h
MOV IAPAL,#00h
MOV DPTR,#AP_code
Program_AP_Verify_Loop:
CALL Trigger_IAP
CLR A
MOVC A,@A+DPTR
MOV B,A
MOV A,IAPFD
CJNE A,B,Program_AP_Verify_Error
INC DPTR
INC IAPAL
MOV A,IAPAL
CJNE A,#14,Program_AP_Verify_Loop
RET
Program_AP_Verify_Error:
CALL Disable_IAP
MOV P0,#00h
SJMP $
;********************************************************************
; IAP CONFIG Function
;********************************************************************
Erase_CONFIG:
MOV IAPCN,#ALL_ERASE_CONFIG
MOV IAPAH,#00h
MOV IAPAL,#00h
MOV IAPFD,#0FFh
CALL Trigger_IAP
RET
Read_CONFIG:
MOV IAPCN,#BYTE_READ_CONFIG
MOV IAPAH,#00h
MOV IAPAL,#02h
CALL Trigger_IAP
MOV R7,IAPFD
RET
Jul. 20, 2018 Page 228 of 276 Rev. 1.06
N76E003 Datasheet
Program_CONFIG:
MOV IAPCN,#BYTE_PROGRAM_CONFIG
MOV IAPAH,#00h
MOV IAPAL,#02h
MOV A,R7
ANL A,#11111011b
MOV IAPFD,A ;disable BOD reset
MOV R6,A ;temp data
CALL Trigger_IAP
RET
Program_CONFIG_Verify:
MOV IAPCN,#BYTE_READ_CONFIG
MOV IAPAH,#00h
MOV IAPAL,#02h
CALL Trigger_IAP
MOV B,R6
MOV A,IAPFD
CJNE A,B,Program_CONFIG_Verify_Error
RET
Program_CONFIG_Verify_Error:
CALL Disable_IAP
MOV P0,#00h
SJMP $
;********************************************************************
; APROM code
;********************************************************************
AP_code:
DB 75h,0B1h, 00h ;OPCODEs of “MOV P0M1,#0”
DB 75h,0B3h, 00h ;OPCODEs of “MOV P1M1,#0”
DB 75h, 90h, 55h ;OPCODEs of “MOV P1,#55h”
DB 75h,080h,0Aah ;OPCODEs of “MOV P0,#0Aah”
DB 80h,0Feh ;OPCODEs of “SJMP $”
END
The N76E003 has several features that help user to control the power consumption of the device. The
power reduced feature has two option modes: Idle mode and Power-down mode, to save the power
consumption. For a stable current consumption, the state and mode of each pin should be taken care
of. The minimum power consumption can be attained by giving the pin state just the same as the
external pulls for example output 1 if pull-high is used or output 0 if pull-low. If the I/O pin is floating,
user is recommended to leave it as quasi-bidirectional mode. If P2.0 is configured as a input-only pin,
it should have an external pull-up or pull-low, or enable its internal pull-up by setting P20UP (P2S.7).
Idle Mode
Idle mode suspends CPU processing by holding the Program Counter. No program code are fetched
and run in Idle mode. It forces the CPU state to be frozen. The Program Counter (PC), Stack Pointer
(SP), Program Status Word (PSW), Accumulator (ACC), and the other registers hold their contents
during Idle mode. The port pins hold the logical states they had at the time Idle was activated.
Generally, it saves considerable power of typical half of the full operating power.
Since the clock provided for peripheral function logic circuit like timer or serial port still remain in Idle
mode, the CPU can be released from the Idle mode with any of enabled interrupt sources. User can
put the device into Idle mode by writing 1 to the bit IDL (PCON.0). The instruction that sets the IDL bit
is the last instruction that will be executed before the device enters Idle mode.
Jul. 20, 2018 Page 230 of 276 Rev. 1.06
N76E003 Datasheet
The Idle mode can be terminated in two ways. First, as mentioned, any enabled interrupt will cause an
exit. It will automatically clear the IDL bit, terminate Idle mode, and the interrupt service routine (ISR)
will be executed. After using the RETI instruction to jump out of the ISR, execution of the program will
be the one following the instruction, which put the CPU into Idle mode. The second way to terminate
Idle mode is with any reset other than software reset. Remember that if Watchdog reset is used to exit
Idle mode, the WIDPD (WDCON.4) needs to be set 1 to let WDT keep running in Idle mode.
Power-down mode is the lowest power state that the N76E003 can enter. It remain the power
consumption as A ”Μa” level by stopping the system clock source. Both of PU and peripheral
functions like Timers or UART are frozen. Flash memory is put into its stop mode. All activity is
completely stopped and the power consumption is reduced to the lowest possible value. The device
can be put into Power-down mode by writing 1 to bit PD (PCON.1). The instruction that does this
action will be the last instruction to be executed before the device enters Power-down mode. In the
Power-down mode, RAM maintains its content. The port pins output the values held by their own state
before Power-down respectively.
There are several ways to exit the N76E003 from the Power-down mode. The first is with all resets
except software reset. Brown-out reset will also wake up CPU from Power-down mode. Be sure that
brown-out detection is enabled before the system enters Power-down. However, for least power
consumption, it is recommended to enable low power BOD in Power-down mode. Of course the
external pin reset and power-on reset will remove the Power-down status. After the external reset or
power-on reset. The CPU is initialized and start executing program code from the beginning.
The second way to wake the N76E003 up from the Power-down mode is by an enabled external
interrupt. The trigger on the external pin will asynchronously restart the system clock. After oscillator is
stable, the device executes the interrupt service routine (ISR) for the corresponding external interrupt.
After the ISR is completed, the program execution returns to the instruction after the one, which puts
the device into Power-down mode and continues. Interrupts that allows to wake up CPU from Power-
down mode includes external interrupt ̅̅̅̅̅̅̅ and ̅̅̅̅̅̅̅, pin interrupt, WDT interrupt, WKT interrupt, and
brown-out interrupt.
The N76E003 has a wide variety of clock sources and selection features that allow it to be used in a
wide range of applications while maximizing performance and minimizing power consumption. The
N76E003 provides three options of the system clock sources including internal oscillator, or external
clock from XIN pin via software. The N76E003 is embedded with two internal oscillators: one 10 kHz
low-speed and one 16 MHz high-speed, which is factory trimmed to ±2% under all conditions. A clock
divider CKDIV is also available on N76E003 for adjustment of the flexibility between power
consumption and operating performance.
FECLK Flash
XIN
Memory
10
There are a total of three system clock sources selectable in the N76E003 including high-speed
internal oscillator, low-speed internal oscillator and external clock input. Each of them can be the
system clock source in the N76E003. Different active system clock sources also affect multi-function
of P3.0/XIN.
There are two internal oscillators in the N76E003 – one 16 MHz high-speed internal oscillator (HIRC)
and one 10 kHz low-speed (LIRC). Both of them can be selected as the system clock. HIRC can be
enabled by setting HIRCEN (CKEN.5). LIRC is enabled after device is powered up. User can set
OSC[1:0] (CKSWT [2:1]) as [1,1] to select the HIRC as the system clock. By setting OSC[1:0] as [1,0],
LIRC will be selected as the system clock. Note that after the N76E003 is powered, HIRC and LIRC
will be both enabled and HIRC is default selected as the system clock source. While using internal
oscillators, XIN automatically switch as one general purpose I/O P3.0 to expend the number of general
purpose I/O. The I/O output mode of P3.0 can be selected by configuring P3M1 and P3M2 registers.
The N76E003 supports clock source switching on-the-fly by controlling CKSWT and CKEN registers
via software. It provides a wide flexibility in application. Note that these SFRs are writing TA protected
for precaution. With this clock source control, the clock source can be switched between the external
clock source and the internal oscillator, even between the high and low-speed internal oscillator.
However, during clock source switching, the device requires some amount of warm-up period for an
original disabled clock source. Therefore, use should follow steps below to ensure a complete clock
source switching. User can enable the target clock source by writing proper value into CKEN register,
wait for the clock source stable by polling its status bit in CKSWT register, and switch to the target
clock source by changing OSC[1:0] (CKSWT[2:1]). After these step, the clock source switching is
successful and then user can also disable the original clock source if power consumption is
concerned. Note that if not following the steps above, the hardware will take certain actions to deal
with such illegal operations as follows.
1. If user tries to disable the current clock source by changing CKEN value, the device will ignore this
action. The system clock will remain the original one and CKEN will remain the original value.
2. If user tries to switch the system clock source to a disabled one by changing OSC[1:0] value,
OSC[1:0] value will be updated right away. But the system clock will remain the original one and
CKSWTF flag will be set by hardware.
3. Once user switches the system clock source to an enabled but still instable one, the hardware will
wait for stabilization of the target clock source and then switch to it in the background. During this
waiting period, the device will continue executing the program with the original clock source and
CKSWTF will be set as 1. After the stable flag of the target clock source (see CKSWT[7:3]) is set and
the clock source switches successfully, CKSWTF will be cleared as 0 automatically by hardware.
The oscillator frequency (FOSC) can be divided down, by an integer, up to 1/510 by configuring a
dividing register, CKDIV, to provide the system clock (FSYS). This feature makes it possible to
temporarily run the MCU at a lower rate, reducing power consumption. By dividing the clock, the MCU
can retain the ability to respond to events other than those that can cause interrupts (i.e. events that
allow exiting the Idle mode) by executing its normal program at a lower rate. This can often result in
lower power consumption than in Idle mode. This can allow bypassing the oscillator start-up time in
cases where Power-down mode would otherwise be used. The value of CKDIV may be changed by
the program at any time without interrupting code execution.
The N76E003 provides a CLO pin (P1.1) that outputs the system clock. Its frequency is the same as
FSYS. The output enable bit is CLOEN (CKCON.1). CLO output stops when device is put in its Power-
down mode because the system clock is turned off. Note that when noise problem or power
consumption is important issue, user had better not enable CLO output.
To prevent incorrect execution during power up and power drop, The N76E003 provide two power
monitor functions, power-on detection and brown-out detection.
The power-on detection function is designed for detecting power up after power voltage reaches to a
level where system can work. After power-on detected, the POF (PCON.4) will be set 1 to indicate a
cold reset, a power-on reset complete. The POF flag can be cleared via software.
Notice:
N76E003 provides power-on detection to prevent incorrect execution during power up and power
drop. The power-on detection function is designed for detecting power up after power voltage reaches
to a level where system can work. The N76E003 POR-detect-voltage stables at one value which falls
between 1.3 V to 1.5 V. When N76E003 runs in power down mode, the core runs under a low power
consumption condition. Every time N76E003 wakes up from power-down mode, power consumption
condition changes to normal power consumption. It can cause the core voltage glitch to less than 1.5
V. The POR will be trigger, and MCU will reset.
Workaround:
POR is for use by VDD power-on. After power-on, the system uses LVR for power detection. Strongly
suggests that disable POR function every time after power-on reset at the initial part of Customer
code.
To disable POR:
At SFR address, FDH is the PORDIS register to control disable POR function through software.
Since PORDIS register is TA protected, please always follow list code step to disable POR.
Sfr PORDIS = 0XFD;
TA =0XAA;
TA= 0X55;
PORDIS = 0X5A;
TA=0XAA;
TA=0X55;
PORDIS = 0XA5;
The other power monitoring function brown-out detection (BOD) circuit is used for monitoring the VDD
level during execution. There are eight CONFIG selectable brown-out trigger levels available for wide
voltage applications. These eight nominal levels are 2.2V, 2.7V, 3.7V and 4.4V selected via setting
CBOV[1:0] (CONFIG2[5:4]). BOD level can also be changed by setting BOV[1:0] (BODCON0[6:4])
after power-on. When VDD drops to the selected brown-out trigger level (VBOD), the BOD logic will
either reset the MCU or request a brown-out interrupt. User may decide to being reset or generating a
brown-out interrupt according to different applications. VBOD also can be set by software after power-
on. Note that BOD output is not available until 2~3 LIRC clocks after software enabling.
The BOD will request the interrupt while VDD drops below VBOD while BORST (BODCON0.2) is 0. In
this case, BOF (BODCON0.3) will be set as 1. After user cleared this flag whereas VDD remains below
VBOD, BOF will not set again. BOF just acknowledge user a power drop occurs. The BOF will also be
set as 1 after VDD goes higher than VBOD to indicate a power resuming. The BOD circuit provides an
useful status indicator BOS (BODCON0.0), which is helpful to tell a brown-out event or power
resuming event occurrence. If the BORST bit is set as 1, this will enable brown-out reset function.
After a brown-out reset, BORF (BODCON0.1) will be set as 1 via hardware. It will not be altered by
reset other than power-on. This bit can be cleared by software. Note that all bits in BODCON0 is
writing protected by timed access (TA).
Jul. 20, 2018 Page 238 of 276 Rev. 1.06
N76E003 Datasheet
The N76E003 provides low power BOD mode for saving current consumption and remaining BOD
functionality with limited detection response. By setting LPBOD[1:0] (BODCON1[2:1]), the BOD circuit
can be periodically enabled to sense the power voltage nominally every 1.6 ms, 6.4 ms, or 25.6 ms. It
saves much power but also provides low-speed power voltage sensing. Note that the hysteresis
feature will disappear in low power BOD mode.
For a noise sensitive system, the N76E003 has a BOD filter which filters the power noise to avoid
BOD event triggering unconsciously. The BOD filter is enabled by default and can be disabled by
setting BODFLT (BODCON1.0) as 0 if user requires a rapid BOD response. The minimum brown-out
detect pulse width is listed in Table 24-2.
BODEN
CONFIG2
7 6 5 4 3 2 1 0
CBODEN - CBOV[1:0] BOIAP CBORST - -
R/W - R/W R/W R/W - -
Factory default value: 1111 1111b
CBODEN CBORST
VDD Level BOF
(CONFIG2.7) (CONFIG2.2)
1 1 > VBOD always 0
1 0 < VBOD 1
1 0 > VBOD 0
0 X X 0
0 Normal mode
Any clock source Typ. 1μs
(LPBOD[1:0] = [0,0])
Low power mode 1
Any clock source 16 (1/FLIRC)
(LPBOD[1:0] = [0,1])
Low power mode 2
Any clock source 64 (1/FLIRC)
(LPBOD[1:0] = [1,0])
Low power mode 3
Any clock source 256 (1/ FLIRC)
(LPBOD[1:0] = [1,1])
1 Normal operation: 32 (1/FSYS)
Normal mode HIRC/ECLK Idle mode: 32 (1/FSYS)
(LPBOD[1:0] = [0,0]) Power-down mode: 2 (1/FLIRC)
LIRC 2 (1/FLIRC)
Low power mode 1
Any clock source 18 (1/FLIRC)
(LPBOD[1:0] = [0,1])
Low power mode 2
Any clock source 66 (1/FLIRC)
(LPBOD[1:0] = [1,0])
Low power mode 3
Any clock source 258 (1/ FLIRC)
(LPBOD[1:0] = [1,1])
25. RESET
The N76E003 has several options to place device in reset condition. It also offers the software flags to
indicate the source, which causes a reset. In general, most SFRs go to their Reset value irrespective
of the reset condition, but there are several reset source indicating flags whose state depends on the
source of reset. User can read back these flags to determine the cause of reset using software. There
are six ways of putting the device into reset state. They are power-on reset, brown-out reset, external
reset, hard fault reset, WDT reset, and software reset.
The N76E003 incorporates an internal power-on reset. During a power-on process of rising power
supply voltage VDD, the power-on reset will hold the MCU in reset mode when VDD is lower than the
voltage reference threshold. This design makes CPU not access program flash while the V DD is not
adequate performing the flash reading. If an undetermined operating code is read from the program
flash and executed, this will put CPU and even the whole system in to an erroneous state. After a
while, VDD rises above the threshold where the system can work, the selected oscillator will start and
then program code will execute from 0000H. At the same time, a power-on flag POF (PCON.4) will be
set 1 to indicate a cold reset, a power-on reset complete. Note that the contents of internal RAM will
be undetermined after a power-on. It is recommended that user gives initial values for the RAM block.
The POF is recommended to be cleared to 0 via software to check if a cold reset or warm reset
performed after the next reset occurs. If a cold reset caused by power off and on, POF will be set 1
again. If the reset is a warm reset caused by other reset sources, POF will remain 0. User may take a
different course to check other reset flags and deal with the warm reset event.
The brown-out detection circuit is used for monitoring the VDD level during execution. When VDD drops
to the selected brown-out trigger level (VBOD), the brown-out detection logic will reset the MCU if
Jul. 20, 2018 Page 243 of 276 Rev. 1.06
N76E003 Datasheet
BORST (BODCON0.2) setting 1. After a brown-out reset, BORF (BODCON0.1) will be set as 1 via
hardware. BORF will not be altered by any reset other than a power-on reset or brown-out reset itself.
This bit can be set or cleared by software.
The external reset pin ̅̅̅̅̅̅ is an input with a Schmitt trigger. An external reset is accomplished by
holding the ̅̅̅̅̅̅ pin low for at least 24 system clock cycles to ensure detection of a valid hardware
reset signal. The reset circuitry then synchronously applies the internal reset signal. Thus, the reset is
a synchronous operation and requires the clock to be running to cause an external reset.
Once the device is in reset condition, it will remain as long as ̅̅̅̅̅̅ pin is low. After the ̅̅̅̅̅̅ high is
removed, the MCU will exit the reset state and begin code executing from address 0000H. If an
external reset applies while CPU is in Power-down mode, the way to trigger a hardware reset is
slightly different. Since the Power-down mode stops system clock, the reset signal will asynchronously
cause the system clock resuming. After the system clock is stable, MCU will enter the reset state.
There is a RSTPINF (AUXR1.6) flag, which indicates an external reset took place. After the external
reset, this bit will be set as 1 via hardware. RSTPINF will not change after any reset other than a
power-on reset or the external reset itself. This bit can be cleared via software.
If Program Counter (PC) is over flash size, Hard Fault reset will occur. After Hard Fault reset, HardF
(AUXR1.5) flag will be set via hardware. HardF will not change after any reset other than a power-on
reset or the Hard Fault reset itself. This bit can be cleared via software. If MCU run in OCD debug
mode and OCDEN = 0, hard fault reset will be disabled and only HardF flag be asserted.
Note: If MCU run in OCD debug mode and OCDEN = 0, hard fault reset will be
disabled and only HardF flag be asserted.
The WDT is a free running timer with programmable time-out intervals and a dedicated internal clock
source. User can clear the WDT at any time, causing it to restart the counter. When the selected time-
out occurs but no software response taking place for a while, the WDT will reset the system directly
and CPU will begin execution from 0000H.
Once a reset due to WDT occurs, the WDT reset flag WDTRF (WDCON.3) will be set. This bit keeps
unchanged after any reset other than a power-on reset or WDT reset itself. User can clear WDTRF via
software.
Note: When register CKDIV value is not equal 00H, the system clock frequency will be divided, if
under this condition after MCU into power down mode, the WDT Reset will fail. So suggest use WKT to
wakeup N76E003 when into power down mode.
The N76E003 provides a software reset, which allows the software to reset the whole system just
similar to an external reset, initializing the MCU as it reset state. The software reset is quite useful in
the end of an ISP progress. For example, if an ISP of Boot Code updating User Code finishes, a
software reset can be asserted to re-boot CPU to execute new User Code immediately. Writing 1 to
SWRST (CHPCON.7) will trigger a software reset. Note that this bit is writing TA protection. The
instruction that sets the SWRST bit is the last instruction that will be executed before the device reset.
See demo code below.
If a software reset occurs, SWRF (AUXR.7) will be automatically set by hardware. User can check it
as the reset source indicator. SWRF keeps unchanged after any reset other than a power-on reset or
software reset itself. SWRF can be cleared via software.
MOV TA,#55h
ORL CHPCON,#10000000b ;software reset
CONFIG0.7 CHPCON.1
CBS BS
Load
Power-on reset
Watchgod Timer reset Reset and boot from APROM
Brown-out reset BS = 0
RST pin reset BS = 1
Hard Fault reset Reset and boot from LDROM
Software reset
The N76E003 provides user a flexible boot selection for variant application. The SFR bit BS in
CHPCON.1 determines MCU booting from APROM or LDROM after any source of reset. If reset
occurs and BS is 0, MCU will reboot from address 0000H of APROM. Else, the CPU will reboot from
address 0000H of LDROM. Note that BS is loaded from the inverted value of CBS bit in CONFIG0.7
after all resets except software reset.
CONFIG0
7 6 5 4 3 2 1 0
CBS - OCDPWM OCDEN - RPD LOCK -
R/W - R/W R/W - R/W R/W -
Factory default value: 1111 1111b
After the MCU is released from reset state, the hardware will always check the BS bit instead of
the CBS bit to determine from which block that the device reboots.
The reset state besides power-on reset does not affect the on-chip RAM. The data in the RAM will be
preserved during the reset. After the power-on reset the RAM contents will be indeterminate.
After a reset, most of SFRs go to their initial values except bits, which are affected by different reset
events. See the notes of Table 6-2. SFR Definitions and Reset Values. The Program Counter is forced
to 0000H and held as long as the reset condition is applied. Note that the Stack Pointer is also reset to
07H and thus the stack contents may be effectively lost during the reset event even though the RAM
contents are not altered.
After a reset, all peripherals and interrupts are disabled. The I/O port latches resumes FFH and I/O
mode input-only. Note: OCDDA and OCDCK pin keep quasi mode with pull high resister about 600
LIRC clock before change to input mode after reset.
The original 8051 contains one DPTR (data pointer) only. With single DPTR, it is difficult to move data
form one address to another with wasting code size and low performance. The N76E003 provides two
data pointers. Thus, software can load both a source and a destination address when doing a block
move. Once loading, the software simply switches between DPTR and DPTR1 by the active data
pointer selection DPS (AUXR1.0) bit.
An example of 64 bytes block move with dual DPTRs is illustrated below. By giving source and
destination addresses in data pointers and activating cyclic makes block RAM data move more simple
and efficient than only one DPTR. The INC AUXR1 instruction is the shortest (2 bytes) instruction to
accomplish DPTR toggling rather than ORL or ANL. For AUXR1.1 contains a hard-wired 0, it allows
toggling of the DPS bit by incrementing AUXR1 without interfering with other bits in the register.
AUXR1 also contains a general purpose flag GF2 in its bit 3 that can be set or cleared by the user via
software.
Before shipping out, each N76E003 chip was factory pre-programmed with a 96-bit width serial number, which is
guaranteed to be unique. The serial number is called UID. The user can read the unique code only by IAP
command. Please see IAP Commands.
The N76E003 is embedded in an on-chip-debugger (OCD) providing developers with a low cost
method for debugging user code, which is available on each package. The OCD gives debug
capability of complete program flow control with eight hardware address breakpoints, single step, free
running, and non-intrusive commands for memory access. The OCD system does not occupy any
locations in the memory map and does not share any on-chip peripherals.
When the OCDEN (CONFIG0.4) is programmed as 0 and LOCK (CONFIG0.1) remains un-
programmed as 1, the OCD is activated. The OCD cannot operate if chip is locked. The OCD system
uses a two-wire serial interface, OCDDA and OCDCK, to establish communication between the target
device and the controlling debugger host. OCDDA is an input/output pin for debug data transfer and
OCDCK is an input pin for synchronization with OCDDA data. The P2.0/̅̅̅̅̅̅ pin is also necessary for
OCD mode entry and exit. The N76E003 supports OCD with Flash Memory control path by ICP writer
mode, which shares the same three pins of OCD interface.
The N76E003 uses OCDDA, OCDCK, and P2.0/̅̅̅̅̅̅ pins to interface with the OCD system. When
designing a system where OCD will be used, the following restrictions must be considered for correct
operation:
1. If P2.0/̅̅̅̅̅̅ is configured as external reset pin, it cannot be connected directly to V DD and any
external capacitors connected must be removed.
2. If P2.0/̅̅̅̅̅̅ is configured as input pin P2.0, any external input source must be isolated.
The N76E003 is a fully-featured microcontroller that multiplexes several functions on its limited I/O
pins. Some device functionality must be sacrificed to provide resources for OCD system. The OCD
has the following limitations:
1. The P2.0/̅̅̅̅̅̅ pin needs to be used for OCD mode selection. Therefore, neither P2.0 input nor an
external reset source can be emulated.
2. The OCDDA pin is physically located on the same pin P1.6. Therefore, neither its I/O function nor
shared multi-functions can be emulated.
3. The OCDCK pin is physically located on the same pin as P0.2. Therefore, neither its I/O function
nor shared multi-functions can be emulated.
4. When the system is in Idle or Power-down mode, it is invalid to perform any accesses because
parts of the device may not be clocked. A read access could return garbage or a write access might
not succeed.
5. HIRC cannot be turned off because OCD uses this clock to monitor its internal status. The
instruction that turns off HIRC affects nothing if executing under debug mode. When CPU enters its
Power-down mode under debug mode, HIRC keeps turning on.
The N76E003 OCD system has another limitation that non-intrusive commands cannot be executed at
any time while the user’s program is running. on-intrusive commands allow a user to read or write
MCU memory locations or access status and control registers with the debug controller. A reading or
writing memory or control register space is allowed only when MCU is under halt condition after a
matching of the hardware address breakpoint or a single step running.
CONFIG0
7 6 5 4 3 2 1 0
CBS - OCDPWM OCDEN - RPD LOCK -
R/W - R/W R/W - R/W R/W -
Factory default value: 1111 1111b
Note: If MCU run in OCD debug mode and OCDEN = 0, hard fault reset will
be disabled and only HardF flag be asserted.
The N76E003 has several hardware configuration bytes, called CONFIG, those are used to configure
the hardware options such as the security bits, system clock source, and so on. These hardware
options can be re-configured through the parallel Writer, In-Circuit-Programming (ICP), or In-
Application-Programming (IAP). Several functions, which are defined by certain CONFIG bits are also
available to be re-configured by SFR. Therefore, there is a need to load such CONFIG bits into
respective SFR bits. Such loading will occur after resets. These SFR bits can be continuously
controlled via user’s software.
CONFIG0
7 6 5 4 3 2 1 0
CBS - OCDPWM OCDEN - RPD LOCK -
R/W - R/W R/W - R/W R/W -
Factory default value: 1111 1111b
Note: If MCU run in OCD debug mode and OCDEN = 0, hard fault reset will
be disabled and only Hard F flag be asserted.
3 - Reserved
2 RPD Reset pin disable
1 = The reset function of P2.0/Nrst pin Enabled. P2.0/Nrst functions as the
external reset pin.
0 = The reset function of P2.0/Nrst pin Disabled. P2.0/Nrst functions as an
input-only pin P2.0.
CONFIG0 7 6 5 4 3 2 1 0
CBS - OCDPWM OCDEN - RPD LOCK -
CHPCON 7 6 5 4 3 2 1 0
SWRST IAPFF - - - - BS IAPEN
CONFIG1
7 6 5 4 3 2 1 0
- - - - - LDSIZE[2:0]
- - - - - R/W
Factory default value: 1111 1111b
CONFIG2
7 6 5 4 3 2 1 0
CBODEN - CBOV[1:0] BOIAP CBORST - -
R/W - R/W R/W R/W - -
Factory default value: 1111 1111b
CONFIG2 7 6 5 4 3 2 1 0
CBODEN - CBOV[1:0] BOIAP CBORST - -
BODCON0 7 6 5 4 3 2 1 0
BODEN - BOV[1:0] BOF BORST BORF BOS
CONFIG4
7 6 5 4 3 2 1 0
WDTEN[3:0] - - - -
R/W - - - -
Factory default value: 1111 1111b
The Flash Memory can be programmed by “ n-Circuit-Programming” ( P). If the product is just under
development or the end product needs firmware updating in the hand of an end customer, the
hardware programming mode will make repeated programming difficult and inconvenient. ICP method
makes it easy and possible without removing the microcontroller from the system. ICP mode also
allows customers to manufacture circuit boards with un-programmed devices. Programming can be
done after the assembly process allowing the device to be programmed with the most recent firmware
or a customized firmware.
There are three signal pins, ̅̅̅̅̅̅, ICPDA, and ICPCK, involved in ICP function. ̅̅̅̅̅̅ is used to enter
or exit ICP mode. ICPDA is the data input and output pin. ICPCK is the clock input pin, which
synchronizes the data shifted in to or out from MCU under programming. User should leave these
three pins plus VDD and GND pins on the circuit board to make ICP possible.
Nuvoton provides ICP tool for N76E003, which enables user to easily perform ICP through Nuvoton
ICP programmer. The ICP programmer developed by Nuvoton has been optimized according to the
electric characteristics of MCU. It also satisfies the stability and efficiency during production progress.
For more details, please visit Nuvoton 8-bit Microcontroller website: Nuvoton 80C51 Microcontroller
Technical Support.
The N76E003 executes all the instructions of the standard 80C51 family fully compatible with MCS-51.
However, the timing of each instruction is different for it uses high performance 1T 8051 core. The
architecture eliminates redundant bus states and implements parallel execution of fetching, decode,
and execution phases. The N76E003 uses one clock per machine-cycle. It leads to performance
improvement of rate 8.1 (in terms of MIPS) with respect to traditional 12T 80C51 device working at the
same clock frequency. However, the real speed improvement seen in any system will depend on the
instruction mix.
All instructions are coded within an 8-bit field called an OPCODE. This single byte should be fetched
from Program Memory. The OPCODE is decoded by the CPU. It determines what action the CPU will
take and whether more operation data is needed from memory. If no other data is needed, then only
one byte was required. Thus the instruction is called a one byte instruction. In some cases, more data
is needed, which is two or three byte instructions.
Table 30-1 lists all instructions for details. The note of the instruction set and addressing modes are
shown below.
tresses at or above those listed under “Absolute aximum atings” may cause permanent damage
to the device. It is a stress rating only and functional operation of the device at these or any other
conditions above those indicated in the operational sections of this specification is not implied.
Exposure to absolute maximum rating conditions may affect device reliability.
[1] Under steady state (non-transient) conditions, IOL must be externally limited as follows,
Maximum IOL per port pin: 15 mA
Maximum total IOL for all outputs: 100 mA
[2] Pins of all ports in quasi-bidirectional mode source a transition current when they are being externally driven
from 1 to 0. The transition current reaches its maximum value when V IN is approximately 2V.
[3] It is measured while U keeps in running “ J P $” loop continuously. All pins of ports are configured as
quasi-bidirectional mode.
90% 90%
10% 10%
TR TF
T = 1/FOUT
0.50%
Percentage (%)
0.00%
-0.50%
MAX
-1.00% MIN
-1.50%
-2.00%
-40 -30 -20 -10 0 10 20 25 35 45 55 65 75 85 95 105 115 125
Temperature (℃)
1 10
Important Notice
Nuvoton Products are neither intended nor warranted for usage in systems or equipment, any
malfunction or failure of which may cause loss of human life, bodily injury or severe property
damage. Such applications are deemed, “ nsecure Usage”.
Insecure usage includes, but is not limited to: equipment for surgical implementation, atomic
energy control instruments, airplane or spaceship instruments, the control or operation of
dynamic, brake or safety systems designed for vehicular use, traffic signal instruments, all
types of safety devices, and other applications intended to support or sustain life.
All nsecure Usage shall be made at customer’s risk, and in the event that third parties lay
claims to uvoton as a result of customer’s nsecure Usage, customer shall indemnify the
damages and liabilities thus incurred by Nuvoton.