ATMEL AT89C5131-PLTIL 8-bit flash microcontroller with full speed usb device Datasheet

Features
• 80C52X2 Core (6 Clocks per Instruction)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
– Maximum Core Frequency 48 MHz in X1 Mode, 24MHz in X2 Mode
– Dual Data Pointer
– Full-duplex Enhanced UART (EUART)
– Three 16-bit Timer/Counters: T0, T1 and T2
– 256 Bytes of Scratchpad RAM
32-Kbyte On-chip Flash In-System Programming through USB or UART
4-Kbyte EEPROM for Boot (3-Kbyte) and Data (1-Kbyte)
On-chip Expanded RAM (ERAM): 1024 Bytes
USB 1.1 and 2.0 Full Speed Compliant Module with Interrupt on Transfer Completion
– Endpoint 0 for Control Transfers: 32-byte FIFO
– 6 Programmable Endpoints with In or Out Directions and with Bulk, Interrupt or
Isochronous Transfers
• Endpoint 1, 2, 3: 32-byte FIFO
• Endpoint 4, 5: 2 x 64-byte FIFO with Double Buffering (Ping-pong Mode)
• Endpoint 6: 2 x 512-byte FIFO with Double Buffering (Ping-pong Mode)
– Suspend/Resume Interrupts
– Power-on Reset and USB Bus Reset
– 48 MHz DPLL for Full-speed Bus Operation
– USB Bus Disconnection on Microcontroller Request
5 Channels Programmable Counter Array (PCA) with 16-bit Counter, High-speed
Output, Compare/Capture, PWM and Watchdog Timer Capabilities
Programmable Hardware Watchdog Timer (One-time Enabled with Reset-out): 50 ms to
6s at 4 MHz
Keyboard Interrupt Interface on Port P1 (8 Bits)
TWI (Two Wire Interface) 400Kbit/s
SPI Interface (Master/Slave Mode)
34 I/O Pins
4 Direct-drive LED Outputs with Programmable Current Sources: 2-6-10 mA Typical
4-level Priority Interrupt System (11 sources)
Idle and Power-down Modes
0 to 32 MHz On-chip Oscillator with Analog PLL for 48 MHz Synthesis
Low Power Voltage Range
– 3.0V to 3.6V
– 30 mA Max Operating Current (at 40 MHz)
– 100 µA Max Power-down Current
Industrial Temperature Range
Packages: PLCC52, VQFP64, MLF48, SO28
8-bit Flash
Microcontroller
with Full Speed
USB Device
AT89C5131
Rev. 4136B–USB–09/03
Description
AT89C5131 is a high-performance Flash version of the 80C51 single-chip 8-bit microcontrollers with full speed USB functions.
AT89C5131 features a full-speed USB module compatible with the USB specifications
Version 1.1 and 2.0. This module integrates the USB transceivers with a 3.3V voltage
regulator and the Serial Interface Engine (SIE) with Digital Phase Locked Loop and
48 MHz clock recovery. USB Event detection logic (Reset and Suspend/Resume) and
FIFO buffers supporting the mandatory control Endpoint (EP0) and up to 6 versatile
Endpoints (EP1/EP2/EP3/EP4/EP5/EP6) with minimum software overhead are also part
of the USB module.
AT89C5131 retains the features of the Atmel 80C52 with extended Flash capacity (32Kbyte), 256 bytes of internal RAM, a 4-level interrupt system, two 16-bit timer/counters
(T0/T1), a full duplex enhanced UART (EUART) and an on-chip oscillator.
In addition, AT89C5131 has an on-chip expanded RAM of 1024 bytes (ERAM), a dualdata pointer, a 16-bit up/down Timer (T2), a Programmable Counter Array (PCA), up to
4 programmable LED current sources, a programmable hardware watchdog and a
power-on reset.
AT89C5131 has two software-selectable modes of reduced activity for further reduction
in power consumption. In the idle mode the CPU is frozen while the timers, the serial
ports and the interrupt system are still operating. In the power-down mode the RAM is
saved, the peripheral clock is frozen, but the device has full wake-up capability through
USB events or external interrupts.
2
AT89C5131
4136B–USB–09/03
AT89C5131
XTAL1
XTAL2
EUART
+
BRG
ALE
RAM
256x8
EEPROM
ERAM
4Kx8
1Kx8
32Kx8 Flash
Timer2
SCK
(1) (1) (1) (1)
(1) (1)
PCA
MISO
MOSI
SDA
SCL
T2
T2EX
CEX
ECI
VDD
VSS
TxD
(1) (1)
(2) (2)
SS
RxD
Block Diagram
SPI
TWI
C51
CORE
PSEN
CPU
EA
Timer 0
Timer 1
(2)
Notes:
INT
Ctrl
Parallel I/O Ports & Ext. Bus
Key Watch USB
Board Dog
Regulator
VREF
AVDD
AVSS
D+
D-
KIN
P4
P3
P2
P1
P0
INT1
(2) (2)
T1
(2) (2)
INT0
Port 0 Port 1 Port 2 Port 3 Port 4
RST
WR
(2)
T0
RD
1. Alternate function of Port 1
2. Alternate function of Port 3
3. Alternate function of Port 4
3
4136B–USB–09/03
Pinout Description
Pinout
1 52 51 50 49 48 47
P4.1/SDA
8
46
NC
P2.3/A11
9
P0.1/AD1
P2.4/A12
10
45
44
P2.5/A13
11
43
XTAL2
42
XTAL1
12
13
P2.6/A14
14
P2.7/A15
VDD
P0.2/AD2
RST
P0.3/AD3
41
VSS
P0.4/AD4
15
40
39
16
38
P0.5/AD5
AVDD
17
37
P0.6/AD6
PLCC52
P3.7/RD/LED3
NC
18
36
P0.7/AD7
AVSS
19
35
P3.6/WR/LED2
P3.0/RxD
20
34
NC
P3.4/T0
P3.5/T1/LED1
P3.3/INT1/LED0
P3.2/INT0
PSEN
P3.1/TxD
ALE
EA
VREF
NC
D+
D-
21 22 23 24 25 26 27 28 29 30 31 32 33
PLLF
4
P1.1/T2EX/KIN1/SS
P2.0/A8
2
P1.0/T2/KIN0
P2.1/A9
3
P1.3/CEX0/KIN3
P2.2/A10
5 4
P1.2/ECI/KIN2
P1.6/CEX3/KIN6/SCK
P1.5/CEX2/KIN5/MISO
6
P1.4/CEX1/KIN4
P1.7/CEX4/KIN7/MOSI
7
P0.0/AD0
P4.0/SCL
Figure 1. AT89C5131 52-pin PLCC Pinout
AT89C5131
4136B–USB–09/03
AT89C5131
NC
P1.0/T2/KIN0
P1.2/ECI/KIN2
P1.1/T2EX/KIN1/SS
P1.3/CEX0/KIN3
P0.0/AD0
P1.4/CEX1/KIN4
P2.1/A9
P2.0/A8
P2.2/A10
P1.5/CEX2/KIN5/MISO
P1.6/CEX3/KIN6/SCK
NC
P4.1/SCA
P4.0/SCL
P1.7/CEX4/KIN7/MOSI
Figure 2. AT89C5131 64-pin VQFP Pinout
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49
NC
P2.3/A11
1
2
48
47
NC
P2.4/A12
3
46
P0.1/AD1
P2.5/A13
4
45
P0.2/AD2
XTAL2
XTAL1
5
6
44
43
RST
P0.3/AD3
VSS
P2.6/A14
7
42
P2.7/A15
VDD
AVDD
8
9
41
40
VQFP64
10
39
11
AVSS 12
NC 13
P3.0/RxD 14
NC 15
NC 16
38
NC
37
36
35
NC
NC
P0.4/AD4
P3.7/RD/LED3
P0.5/AD5
P0.6/AD6
P0.7/AD7
P3.6/WR/LED2
34 NC
33 NC
P3.5/T1/LED1
NC
P3.4/T0
P3.2/INT0
P3.3/INT1/LED0
P3.1/TxD
ALE
PSEN
EA
VREF
NC
D-
D+
PLLF
NC
NC
17 18 19 20 21 22 23 24 25 26 27 28 29 30 3132
5
4136B–USB–09/03
P1.2/ECI/KIN2
P1.1/T2EX/KIN1/SS
P1.4/CEX1/KIN4
P1.3/CEX0/KIN3
P2.0/A8
P0.0/AD0
P2.1/A9
P1.5/CEX2/KIN5/MISO
P2.2/A10
P1.7/CEX4/KIN7/MOSI
P1.6/CEX3/KIN6/SCK
P4.0/SCL
Figure 3. AT89C5131 48-pin MLF Pinout
48 47 46 45 44 43 42 41 40 39 38 37
P4.1/SDA
P2.3/A11
1
36
P1.0/T2/KIN0
2
35
P0.1/AD1
P2.4/A12
3
34
P0.2/AD2
P2.5/A13
4
33
XTAL2
5
6
32
RST
P0.3/AD3
XTAL1
31
VSS
P0.4/AD4
8
30
29
9
28
P0.5/AD5
27
P0.6/AD6
MLF 48
P2.6/A14
P2.7/A15
7
VDD
AVDD
10
AVSS
11
26
P0.7/AD7
P3.0/RxD 12
25
P3.6/WR/LED2
P3.7/RD/LED3
P3.4/T0
P3.5/T1/LED1
P3.2/INT0
P3.3/INT1/LED0
ALE
PSEN
P3.1/TxD
VREF
EA
D+
D-
PLLF
13 14 15 16 17 18 19 20 21 22 23 24
Figure 4. AT89C5131 28-pin SO Pinout
P1.5/CEX2/KIN5/MISO 1
28
P1.4/CEX1/KIN4
P1.6/CEX3/KIN6/SCK 2
P1.7/CEX4/KIN7/MOSI 3
27
26
P1.3/CEX0/KIN3
P4.0/SCL 4
25
P1.1/T2EX/KIN1/SS
24
23
RST
P4.1/SDA 5
XTAL2 6
XTAL1 7
VDD 8
AVSS 9
P3.0/RxD 10
11
PLLF
D- 12
D+
VREF
6
13
14
SO28
P1.2/ECI/KIN2
P1.0/T2/KIN0
22
VSS
21
20
P3.7/RD/LED3
P3.6/WR/LED2
19
18
P3.4/T0
P3.5/T1/LED1
17
P3.3/INT1/LED0
16
P3.2/INT0
15
P3.1/TxD
AT89C5131
4136B–USB–09/03
AT89C5131
Signals
All the AT89C5131 signals are detailed by functionality on Table 1 through Table 12.
Table 1. Keypad Interface Signal Description
Signal
Name
Type
KIN[7:0)
I
Description
Keypad Input Lines
Holding one of these pins high or low for 24 oscillator periods triggers a
keypad interrupt if enabled. Held line is reported in the KBCON register.
Alternate
Function
P1[7:0]
Table 2. Programmable Counter Array Signal Description
Signal
Name
Type
ECI
I
Description
External Clock Input
Capture External Input
CEX[4:0]
I/O
Compare External Output
Alternate
Function
P1.2
P1.3
P1.4
P1.5
P1.6
P1.7
Table 3. Serial I/O Signal Description
Signal
Name
Type
RxD
I
TxD
O
Description
Alternate
Function
Serial Input
The serial input is P3.0 after reset, but it can also be configured to P4.0 by
software.
Serial Output
The serial output is P3.1 after reset, but it can also be configured to P4.1 by
software.
P3.0
P3.1
Table 4. Timer 0, Timer 1 and Timer 2 Signal Description
Signal
Name
Type
Description
Alternate
Function
Timer 0 Gate Input
INT0 serves as external run control for timer 0, when selected by GATE0
bit in TCON register.
INT0
I
External Interrupt 0
INT0 input set IE0 in the TCON register. If bit IT0 in this register is set, bits
IE0 are set by a falling edge on INT0. If bit IT0 is cleared, bits IE0 is set by
a low level on INT0.
P3.2
Timer 1 Gate Input
INT1 serves as external run control for Timer 1, when selected by GATE1
bit in TCON register.
INT1
I
External Interrupt 1
INT1 input set IE1 in the TCON register. If bit IT1 in this register is set, bits
IE1 are set by a falling edge on INT1. If bit IT1 is cleared, bits IE1 is set by
a low level on INT1.
P3.3
7
4136B–USB–09/03
Table 4. Timer 0, Timer 1 and Timer 2 Signal Description (Continued)
Signal
Name
Type
T0
I
Timer Counter 0 External Clock Input
When Timer 0 operates as a counter, a falling edge on the T0 pin
increments the count.
P3.4
T1
I
Timer/Counter 1 External Clock Input
When Timer 1 operates as a counter, a falling edge on the T1 pin
increments the count.
P3.5
T2
T2EX
Alternate
Function
Description
I
Timer/Counter 2 External Clock Input
O
Timer/Counter 2 Clock Output
I
Timer/Counter 2 Reload/Capture/Direction Control Input
P1.0
P1.1
Table 5. LED Signal Description
Signal
Name
LED[3:0]
Type
O
Alternate
Function
Description
Direct Drive LED Output
These pins can be directly connected to the Cathode of standard LEDs
without external current limiting resistors. The typical current of each
output can be programmed by software to 2, 6 or 10 mA. Several outputs
can be connected together to get higher drive capabilities.
P3.3
P3.5
P3.6
P3.7
Table 6. TWI Signal Description
Signal
Name
Type
Alternate
Function
SCL
I/O
SCL: TWI Serial Clock
SCL output the serial clock to slave peripherals.
SCL input the serial clock from master.
P4.0
SDA
I/O
SDA: TWI Serial Data
SCL is the bidirectional TWI data line.
P4.1
Description
Table 7. SPI Signal Description
Signal
Name
Type
SS
I/O
Alternate
Function
Description
SS: SPI Slave Select
P1.1
MISO: SPI Master Input Slave Output line
MISO
I/O
SCK
I/O
MOSI
8
I/O
When SPI is in master mode, MISO receives data from the slave
peripheral. When SPI is in slave mode, MISO outputs data to the master
controller.
SCK: SPI Serial Clock
SCK outputs clock to the slave peripheral or receive clock from the master
P1.5
P1.6
MOSI: SPI Master Output Slave Input line
When SPI is in master mode, MOSI outputs data to the slave peripheral.
When SPI is in slave mode, MOSI receives data from the master controller
P1.7
AT89C5131
4136B–USB–09/03
AT89C5131
Table 8. Ports Signal Description
Signal
Name
P0[7:0]
P1[7:0]
P2[7:0]
Type
Description
I/O
Port 0
P0 is an 8-bit open-drain bidirectional I/O port. Port 0
pins that have 1s written to them float and can be used
as high impedance inputs. To avoid any parasitic current
consumption, Floating P0 inputs must be pulled to VDD or
VSS.
I/O
Port 1
P1 is an 8-bit bidirectional I/O port with internal pull-ups,
except for P1.6 and P1.7 that are true open drain
outputs.
I/O
Port 2
P2 is an 8-bit bidirectional I/O port with internal pull-ups.
Alternate Function
AD[7:0]
KIN[7:0]
T2
T2EX
ECI
CEX[4:0]
A[15:8]
LED[3:0]
RxD
TxD
P3[7:0]
I/O
Port 3
P3 is an 8-bit bidirectional I/O port with internal pull-ups.
P4[1:0]
I/O
Port 4
P4 is an 2-bit bidirectional I/O port.
INT0
INT1
T0
T1
WR
RD
SCL
SDA
Table 9. Clock Signal Description
Signal
Name
Type
XTAL1
I
Input to the on-chip inverting oscillator amplifier
To use the internal oscillator, a crystal/resonator circuit is connected to this
pin. If an external oscillator is used, its output is connected to this pin.
-
XTAL2
O
Output of the on-chip inverting oscillator amplifier
To use the internal oscillator, a crystal/resonator circuit is connected to this
pin. If an external oscillator is used, leave XTAL2 unconnected.
-
PLLF
I
PLL Low Pass Filter input
Receives the RC network of the PLL low pass filter.
-
Description
Alternate
Function
Table 10. USB Signal Description
Signal
Name
Type
D+
I/O
USB Data + signal
-
D-
I/O
USB Data - signal
-
VREF
O
USB Reference Voltage
Connect this pin to D+ using a 1.5 kΩ resistor to use the Detach function.
-
Description
Alternate
Function
9
4136B–USB–09/03
Table 11. System Signal Description
Signal
Name
Type
AD[7:0]
I/O
A[15:8]
I/O
RD
I/O
Alternate
Function
Description
Multiplexed Address/Data LSB for external access
P0[7:0]
Data LSB for Slave port access (used for 8-bit and 16-bit modes)
Address Bus MSB for external access
P2[7:0]
Data MSB for Slave port access (used for 16-bit mode only)
Read Signal
Read signal asserted during external data memory read operation.
P3.7
Control input for slave port read access cycles.
WR
I/O
Write Signal
Write signal asserted during external data memory write operation.
P3.6
Control input for slave write access cycles.
I
Reset Input
Holding this pin low for 64 oscillator periods while the oscillator is running
resets the device. The Port pins are driven to their reset conditions when a
voltage lower than VIL is applied, whether or not the oscillator is running.
This pin has an internal pull-up resistor which allows the device to be reset
by connecting a capacitor between this pin and VSS.
Asserting RST when the chip is in Idle mode or Power-down mode returns
the chip to normal operation.
This pin is set to 0 for at least 12 oscillator periods when an internal reset
occurs.
-
ALE
O
Address Latch Enable Output
The falling edge of ALE strobes the address into external latch. This signal
is active only when reading or writing external memory using MOVX
instructions.
-
PSEN
O
Program
Test mode entry signal. This pin must be set to VDD for normal operation.
-
RST
External Access Enable
EA
I
This pin must be held low to force the device to fetch code from external
program memory starting at address 0000h. It is latched during reset and
cannot be dynamically changed during operation.
-
Table 12. Power Signal Description
Signal
Name
Type
Description
AVSS
GND
Alternate Ground
AVSS is used to supply the on-chip PLL and the USB PAD.
-
AVDD
PWR
Alternate Supply Voltage
AVDD is used to supply the on-chip PLL and the USB PAD.
-
VSS
GND
Digital Ground
VSS is used to supply the buffer ring and the digital core.
-
VDD
10
PWR
Digital Supply Voltage
VDD is used to supply the buffer ring on all versions of the device.
It is also used to power the on-chip voltage regulator of the Standard
versions or the digital core of the Low Power versions.
Alternate
Function
-
AT89C5131
4136B–USB–09/03
AT89C5131
Table 12. Power Signal Description (Continued)
Signal
Name
Type
Description
Alternate
Function
USB pull-up Controlled Output
VREF is used to control the USB D+ 1.5 kΩ pull up.
VREF
O
The Vref output is in high impedance when the bit DETACH is set in the
USBCON register.
When the bit DETACH is reseted,
-
In low-power chips, the Vref output voltage is equal to the AVDD input.
In standard versions, the Vref output voltage is equal to the internal
regulator output.
11
4136B–USB–09/03
SFR Mapping
12
The Special Function Registers (SFRs) of the AT89C5131 fall into the following
categories:
•
C51 core registers: ACC, B, DPH, DPL, PSW, SP
•
I/O port registers: P0, P1, P2, P3, P4
•
Timer registers: T2CON, T2MOD, TCON, TH0, TH1, TH2, TMOD, TL0, TL1, TL2,
RCAP2L, RCAP2H
•
Serial I/O port registers: SADDR, SADEN, SBUF, SCON
•
PCA (Programmable Counter Array) registers: CCON, CMOD, CCAPMx, CL, CH,
CCAPxH, CCAPxL (x: 0 to 4)
•
Power and clock control registers: PCON
•
Hardware Watchdog Timer registers: WDTRST, WDTPRG
•
Interrupt system registers: IEN0, IPL0, IPH0, IEN1, IPL1, IPH1
•
Keyboard Interface registers: KBE, KBF, KBLS
•
LED register: LEDCON
•
Two Wire Interface (TWI) registers: SSCON, SSCS, SSDAT, SSADR
•
Serial Port Interface (SPI) registers: SPCON, SPSTA, SPDAT
•
USB registers: Uxxx (17 registers)
•
PLL registers: PLLCON, PLLDIV
•
BRG (Baud Rate Generator) registers: BRL, BDRCON
•
Flash register: FCON (FCON access is reserved for the Flash API and ISP
software)
•
EEPROM register: EECON
•
Others: AUXR, AUXR1, CKCON0, CKCON1
AT89C5131
4136B–USB–09/03
AT89C5131
The table below shows all SFRs with their address and their reset value.
Table 13. SFR Descriptions
Bit
Addressable
Non-Bit Addressable
0/8
1/9
F8h
UEPINT
0000 0000
CH
CCAP0H
CCAP1H
CCAP2H
CCAP3H
CCAP4H
0000 0000
XXXX XXXX
XXXX XXXX
XXXX XXXX
XXXX XXXX
XXXX XXXX
F0h
B
0000 0000
0000 0000
E8h
E0h
2/A
3/B
4/C
5/D
6/E
7/F
FFh
LEDCON
F7h
CL
CCAP0L
CCAP1L
CCAP2L
CCAP3L
CCAP4L
0000 0000
XXXX XXXX
XXXX XXXX
XXXX XXXX
XXXX XXXX
XXXX XXXX
UBYCTLX
0000 0000
UBYCTHX
0000 0000
ACC
0000 0000
EFh
E7h
CCON
CMOD
CCAPM0
CCAPM1
CCAPM2
CCAPM3
CCAPM4
00X0 0000
00XX X000
X000 0000
X000 0000
X000 0000
X000 0000
X000 0000
D0h
PSW
0000 0000
FCON (1)
XXXX 0000
EECON
0000 0000
UEPCONX
1000 0000
UEPRST
0000 0000
C8h
T2CON
0000 0000
T2MOD
XXXX XX00
RCAP2L
0000 0000
RCAP2H
0000 0000
TL2
0000 0000
TH2
0000 0000
UEPSTAX
0000 0000
UEPDATX
0000 0000
CFh
UEPIEN
0000 0000
SPCON
SPSTA
SPDAT
0001 0100
0000 0000
XXXX XXXX
USBADDR
0000 0000
UEPNUM
0000 0000
C7h
UFNUMH
0000 0000
USBCON
0000 0000
USBINT
0000 0000
USBIEN
0000 0000
D8h
C0h
B8h
B0h
A8h
A0h
98h
90h
88h
80h
Note:
P4
XXXX 1111
DFh
D7h
IPL0
SADEN
X000 000
0000 0000
UFNUML
0000 0000
P3
IEN1
XXXX X000
IPL1
IPH1
IPH0
XXXX X000
XXXX X000
X000 0000
1111 1111
BFh
IEN0
SADDR
CKCON1
0000 0000
0000 0000
0000 0000
P2
AUXR1
1111 1111
XXXX X0X0
PLLCON
XXXX XX00
PLLDIV
0000 0000
WDTRST
WDTPRG
XXXX XXXX
XXXX X000
SCON
SBUF
BRL
BDRCON
KBLS
KBE
KBF
0000 0000
XXXX XXXX
0000 0000
XXX0 0000
0000 0000
0000 0000
0000 0000
P1
SSCON
SSCS
SSDAT
SSADR
1111 1111
0000 0000
1111 1000
1111 1111
1111 1110
AUXR
XX0X 0000
TCON
TMOD
TL0
TL1
TH0
TH1
0000 0000
0000 0000
0000 0000
0000 0000
0000 0000
0000 0000
P0
1111 1111
SP
0000 0111
DPL
0000 0000
DPH
0000 0000
0/8
1/9
2/A
3/B
6/E
A7h
97h
CKCON0
0000 0000
PCON
5/D
AFh
9Fh
00X1 0000
4/C
B7h
8Fh
87h
7/F
1. FCON access is reserved for the Flash API and ISP software.
Reserved
13
4136B–USB–09/03
The Special Function Registers (SFRs) of the AT89C5131 fall into the following
categories:
Table 14. C51 Core SFRs
Mnemonic
Add
Name
ACC
E0h
Accumulator
B
F0h
B Register
PSW
D0h
Program Status
Word
SP
81h
DPL
82h
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Stack Pointer
LSB of SPX
Data Pointer
Low byte
LSB of DPTR
DPH
83h
Data Pointer
High byte
MSB of DPTR
Table 15. I/O Port SFRs
14
Mnemonic
Add
Name
P0
80h
Port 0
P1
90h
Port 1
P2
A0h
Port 2
P3
B0h
Port 3
P4
C0h
Port 4 (x2)
AT89C5131
4136B–USB–09/03
AT89C5131
Table 16. Timer SFR’s
Mnemonic
Add
Name
7
6
5
4
3
2
1
0
TH0
8Ch
Timer/Counter 0 High byte
TL0
8Ah
Timer/Counter 0 Low byte
TH1
8Dh
Timer/Counter 1 High byte
TL1
8Bh
Timer/Counter 1 Low byte
TH2
CDh
Timer/Counter 2 High byte
TL2
CCh
Timer/Counter 2 Low byte
TCON
88h
Timer/Counter 0 and 1
control
TF1
TR1
TF0
TR0
IE1
IT1
IE0
IT0
TMOD
89h
Timer/Counter 0 and 1
Modes
GATE1
C/T1#
M11
M01
GATE0
C/T0#
M10
M00
T2CON
C8h
Timer/Counter 2 control
TF2
EXF2
RCLK
TCLK
EXEN2
TR2
C/T2#
CP/RL2#
T2MOD
C9h
Timer/Counter 2 Mode
T2OE
DCEN
RCAP2H
CBh
Timer/Counter 2
Reload/Capture High byte
RCAP2L
CAh
Timer/Counter 2
Reload/Capture Low byte
WDTRST
A6h
WatchDog Timer Reset
WDTPRG
A7h
WatchDog Timer Program
S2
S1
S0
Table 17. Serial I/O Port SFR’s
Mnemonic
Add
Name
SCON
98h
Serial Control
SBUF
99h
Serial Data Buffer
SADEN
B9h
Slave Address Mask
SADDR
A9h
Slave Address
7
6
5
4
3
2
1
0
FE/SM0
SM1
SM2
REN
TB8
RB8
TI
RI
7
6
5
4
3
2
1
0
BRR
TBCK
RBCK
SPD
SRC
Table 18. Baud Rate Generator SFR’s
Mnemonic
Add
Name
BRL
9Ah
Baud Rate Reload
BDRCON
9Bh
Baud Rate Control
15
4136B–USB–09/03
Table 19. PCA SFR’s
Mnemonic
Add
Name
7
6
CCON
D8h
PCA Timer/Counter Control
CF
CR
CMOD
D9h
PCA Timer/Counter Mode
CIDL
WDTE
CL
E9h
PCA Timer/Counter Low byte
CH
F9h
PCA Timer/Counter High byte
CCAPM0
CCAPM1
CCAPM2
CCAPM3
CCAPM4
DAh
DBh
DCh
DDh
DEh
PCA Timer/Counter Mode 0
PCA Timer/Counter Mode 1
PCA Timer/Counter Mode 2
PCA Timer/Counter Mode 3
PCA Timer/Counter Mode 4
CCAP0H
CCAP1H
CCAP2H
CCAP3H
CCAP4H
FAh
FBh
FCh
FDh
FEh
PCA Compare Capture Module 0 H
PCA Compare Capture Module 1 H
PCA Compare Capture Module 2 H
PCA Compare Capture Module 3 H
PCA Compare Capture Module 4 H
CCAP0L
CCAP1L
CCAP2L
CCAP3L
CCAP4L
EAh
EBh
ECh
EDh
EEh
PCA Compare Capture Module 0 L
PCA Compare Capture Module 1 L
PCA Compare Capture Module 2 L
PCA Compare Capture Module 3 L
PCA Compare Capture Module 4 L
5
4
3
2
1
0
CCF4
CCF3
CCF2
CCF1
CCF0
CPS1
CPS0
ECF
ECOM0
ECOM1
ECOM2
ECOM3
ECOM4
CAPP0
CAPP1
CAPP2
CAPP3
CAPP4
CAPN0
CAPN1
CAPN2
CAPN3
CAPN4
MAT0
MAT1
MAT2
MAT3
MAT4
TOG0
TOG1
TOG2
TOG3
TOG4
PWM0
PWM1
PWM2
PWM3
PWM4
ECCF0
ECCF1
ECCF2
ECCF3
ECCF4
CCAP0H7
CCAP1H7
CCAP2H7
CCAP3H7
CCAP4H7
CCAP0H6
CCAP1H6
CCAP2H6
CCAP3H6
CCAP4H6
CCAP0H5
CCAP1H5
CCAP2H5
CCAP3H5
CCAP4H5
CCAP0H4
CCAP1H4
CCAP2H4
CCAP3H4
CCAP4H4
CCAP0H3
CCAP1H3
CCAP2H3
CCAP3H3
CCAP4H3
CCAP0H2
CCAP1H2
CCAP2H2
CCAP3H2
CCAP4H2
CCAP0H1
CCAP1H1
CCAP2H1
CCAP3H1
CCAP4H1
CCAP0H0
CCAP1H0
CCAP2H0
CCAP3H0
CCAP4H0
CCAP0L7
CCAP1L7
CCAP2L7
CCAP3L7
CCAP4L7
CCAP0L6
CCAP1L6
CCAP2L6
CCAP3L6
CCAP4L6
CCAP0L5
CCAP1L5
CCAP2L5
CCAP3L5
CCAP4L5
CCAP0L4
CCAP1L4
CCAP2L4
CCAP3L4
CCAP4L4
CCAP0L3
CCAP1L3
CCAP2L3
CCAP3L3
CCAP4L3
CCAP0L2
CCAP1L2
CCAP2L2
CCAP3L2
CCAP4L2
CCAP0L1
CCAP1L1
CCAP2L1
CCAP3L1
CCAP4L1
CCAP0L0
CCAP1L0
CCAP2L0
CCAP3L0
CCAP4L0
Table 20. Interrupt SFR’s
Mnemonic
Add
Name
7
6
5
4
3
2
1
0
IEN0
A8h
Interrupt Enable Control 0
EA
EC
ET2
ES
ET1
EX1
ET0
EX0
IEN1
B1h
Interrupt Enable Control 1
EUSB
IPL0
B8h
Interrupt Priority Control Low 0
PPCL
PT2L
PSL
PT1L
PX1L
PT0L
PX0L
IPH0
B7h
Interrupt Priority Control High 0
PPCH
PT2H
PSH
PT1H
PX1H
PT0H
PX0H
IPL1
B2h
Interrupt Priority Control Low 1
PUSBL
PSPIL
PKBL
IPH1
B3h
Interrupt Priority Control High 1
PUSBH
PSPIH
PKBH
ESPI
EKB
Table 21. PLL SFRs
Mnemonic
Add
Name
PLLCON
A3h
PLL Control
PLLDIV
A4h
PLL Divider
16
7
R3
6
R2
5
R1
4
R0
3
N3
2
1
0
EXT48
PLLEN
PLOCK
N2
N1
N0
AT89C5131
4136B–USB–09/03
AT89C5131
Table 22. Keyboard SFRs
Mnemonic
Add
Name
7
6
5
4
3
2
1
0
KBF
9Eh
Keyboard Flag
Register
KBF7
KBF6
KBF5
KBF4
KBF3
KBF2
KBF1
KBF0
KBE
9Dh
Keyboard Input Enable
Register
KBE7
KBE6
KBE5
KBE4
KBE3
KBE2
KBE1
KBE0
KBLS
9Ch
Keyboard Level
Selector Register
KBLS7
KBLS6
KBLS5
KBLS4
KBLS3
KBLS2
KBLS1
KBLS0
7
6
5
4
3
2
1
0
Table 23. TWI SFRs
Mnemonic
Add
Name
SSCON
93h
Synchronous Serial
Control
CR2
SSIE
STA
STO
SI
AA
CR1
CR0
SSCS
94h
Synchronous Serial
Control-Status
SC4
SC3
SC2
SC1
SC0
-
-
-
SSDAT
95h
Synchronous Serial
Data
SD7
SD6
SD5
SD4
SD3
SD2
SD1
SD0
SSADR
96h
Synchronous Serial
Address
A7
A6
A5
A4
A3
A2
A1
A0
7
6
5
4
3
2
1
0
Table 24. SPI SFRs
Mnemonic
Add
Name
SPCON
C3h
Serial Peripheral
Control
SPR2
SPEN
SSDIS
MSTR
CPOL
CPHA
SPR1
SPR0
SPSTA
C4h
Serial Peripheral
Status-Control
SPIF
WCOL
SSERR
MODF
-
-
-
-
SPDAT
C5h
Serial Peripheral Data
R7
R6
R5
R4
R3
R2
R1
R0
Table 25. USDB SFR’s
Mnemonic
Add
Name
7
6
5
4
3
2
1
0
USBCON
BCh
USB Global Control
USBE
SUSPCLK
SDRMWUP
DETACH
UPRSM
RMWUPE
CONFG
FADDEN
USBADDR
C6h
USB Address
FEN
UADD6
UADD5
UADD4
UADD3
UADD2
UADD1
UADD0
USBINT
BDh
USB Global Interrupt
-
-
WUPCPU
EORINT
SOFINT
-
-
SPINT
USBIEN
BEh
USB Global Interrupt
Enable
-
-
EWUPCPU
EEORINT
ESOFINT
-
-
ESPINT
UEPNUM
C7h
USB Endpoint Number
-
-
-
-
EPNUM3
EPNUM2
EPNUM1
EPNUM0
UEPCONX
D4h
USB Endpoint X Control
EPEN
-
-
-
DTGL
EPDIR
EPTYPE1
EPTYPE0
UEPSTAX
CEh
USB Endpoint X Status
DIR
RXOUTB1
STALLRQ
TXRDY
STLCRC
RXSETUP
RXOUTB0
TXCMP
UEPRST
D5h
USB Endpoint Reset
-
EP6RST
EP5RST
EP4RST
EP3RST
EP2RST
EP1RST
EP0RST
UEPINT
F8h
USB Endpoint Interrupt
-
EP6INT
EP5INT
EP4INT
EP3INT
EP2INT
EP1INT
EP0INT
UEPIEN
C2h
USB Endpoint Interrupt
Enable
-
EP6INTE
EP5INTE
EP4INTE
EP3INTE
EP2INTE
EP1INTE
EP0INTE
17
4136B–USB–09/03
Table 25. USDB SFR’s
Mnemonic
Add
UEPDATX
CFh
UBYCTLX
Name
7
6
5
4
3
2
1
0
USB Endpoint X FIFO Data
FDAT7
FDAT6
FDAT5
FDAT4
FDAT3
FDAT2
FDAT1
FDAT0
E2h
USB Byte Counter Low (EP
X)
BYCT7
BYCT6
BYCT5
BYCT4
BYCT3
BYCT2
BYCT1
BYCT0
UBYCTHX
E3h
USB Byte Counter High
(EP X)
-
-
-
-
-
BYCT10
BYCT9
BYCT8
UFNUML
BAh
USB Frame Number Low
FNUM7
FNUM6
FNUM5
FNUM4
FNUM3
FNUM2
FNUM1
FNUM0
UFNUMH
BBh
USB Frame Number High
-
-
CRCOK
CRCERR
-
FNUM10
FNUM9
FNUM8
Table 26. Other SFR’s
18
Mnemonic
Add
Name
7
6
5
4
3
2
1
0
PCON
87h
Power Control
SMOD1
SMOD0
-
POF
GF1
GF0
PD
IDL
AUXR
8Eh
Auxiliary Register 0
DPU
-
M0
-
XRS1
XRS2
EXTRAM
A0
AUXR1
A2h
Auxiliary Register 1
-
-
ENBOOT
-
GF3
-
-
DPS
CKCON0
8Fh
Clock Control 0
-
WDX2
PCAX2
SIX2
T2X2
T1X2
T0X2
X2
CKCON1
AFh
Clock Control 1
-
-
-
-
-
-
-
SPIX2
LEDCON
F1h
LED Control
FCON
D1h
Flash Control
EECON
D2h
EEPROM Contol
LED3
LED2
LED1
LED0
FPL3
FPL2
FPL1
FPL0
FPS
FMOD1
FMOD0
FBUSY
EEPL3
EEPL2
EEPL1
EEPL0
-
-
EEE
EEBUSY
AT89C5131
4136B–USB–09/03
AT89C5131
Clock Controller
Introduction
The AT89C5131 clock controller is based on an on-chip oscillator feeding an on-chip
Phase Lock Loop (PLL). All the internal clocks to the peripherals and CPU core are generated by this controller.
The AT89C5131 X1 and X2 pins are the input and the output of a single-stage on-chip
inverter (see Figure 5) that can be configured with off-chip components as a Pierce
oscillator (see Figure 6). Value of capacitors and crystal characteristics are detailed in
the section “DC Characteristics”.
The X1 pin can also be used as input for an external 48 MHz clock.
The clock controller outputs three different clocks as shown in Figure 5:
•
a clock for the CPU core
•
a clock for the peripherals which is used to generate the Timers, PCA, WD, and Port
sampling clocks
•
a clock for the USB controller
These clocks are enabled or disabled depending on the power reduction mode as
detailed in Section “Power Management”, page 146.
Figure 5. Oscillator Block Diagram
÷2
0
Peripheral
Clock
1
CPU Core
Clock
PLL
X1
X2
IDL
CKCON.0
PCON.0
0
1
USB
Clock
X2
Oscillator
EXT48
PD
PLLCON.2
PCON.1
Two clock sources are available for CPU:
•
Crystal oscillator on X1 and X2 pins: Up to 32 MHz
•
External 48 MHz clock on X1 pin
In order to optimize the power consumption, the oscillator inverter is inactive when the
PLL output is not selected for the USB device.
19
4136B–USB–09/03
Figure 6. Crystal Connection
X1
C1
Q
C2
VSS
X2
PLL
PLL Description
The AT89C5131 PLL is used to generate internal high frequency clock (the USB Clock)
synchronized with an external low-frequency (the Peripheral Clock). The PLL clock is
used to generate the USB interface clock. Figure 7 shows the internal structure of the
PLL.
The PFLD block is the Phase Frequency Comparator and Lock Detector. This block
makes the comparison between the reference clock coming from the N divider and the
reverse clock coming from the R divider and generates some pulses on the Up or Down
signal depending on the edge position of the reverse clock. The PLLEN bit in PLLCON
register is used to enable the clock generation. When the PLL is locked, the bit PLOCK
in PLLCON register (see Figure 7) is set.
The CHP block is the Charge Pump that generates the voltage reference for the VCO by
injecting or extracting charges from the external filter connected on PLLF pin (see
Fi gure 8) . Value of the filter components ar e detailed in the Section “ DC
Characteristics”.
The VCO block is the Voltage Controlled Oscillator controlled by the voltage VREF produced by the charge pump. It generates a square wave signal: the PLL clock.
Figure 7. PLL Block Diagram and Symbol
PFILT
PLLCON.1
PLLEN
N divider
OSC
CLOCK
N3:0
Up
PFLD
CHP
Vref
VCO
USB Clock
Down
PLOCK
PLLCON.0
R divider
R3:0
USB
CLOCK
OSCclk × ( R + 1 )
USBclk = ----------------------------------------------N+1
USB Clock Symbol
Figure 8. PLL Filter Connection
PFILT
R
C2
C1
VSS
VSS
The typical values are: R = 100 Ω, C1 = 10 nf, C2 = 2.2 nF.
20
AT89C5131
4136B–USB–09/03
AT89C5131
PLL Programming
The PLL is programmed using the flow shown in Figure 9. As soon as clock generation
is enabled user must wait until the lock indicator is set to ensure the clock output is
stable.
Figure 9. PLL Programming Flow
PLL
Programming
Configure Dividers
N3:0 = xxxxb
R3:0 = xxxxb
Enable PLL
PLLEN = 1
PLL Locked?
LOCK = 1?
Divider Values
To generate a 48 MHz clock using the PLL, the divider values have to be configured following the oscillator frequency. The typical divider values are shown in Table 27.
Table 27. Typical Divider Values
Oscillator Frequency
R+1
N+1
PLLDIV
3 MHz
16
1
F0h
6 MHz
8
1
70h
8 MHz
6
1
50h
12 MHz
4
1
30h
16 MHz
3
1
20h
18 MHz
8
3
72h
20 MHz
12
5
B4h
24 MHz
2
1
10h
32 MHz
3
2
21h
40 MHz
12
10
B9h
21
4136B–USB–09/03
Registers
Table 28. CKCON0 (S:8Fh)
Clock Control Register 0
7
6
5
4
3
2
1
0
-
WDX2
PCAX2
SIX2
T2X2
T1X2
T0X2
X2
Bit
Bit Number Mnemonic Description
7
6
5
4
3
2
1
0
-
Reserved
The value read from this bit is always 0. Do not set this bit.
WDX2
Watchdog Clock
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
PCAX2
Programmable Counter Array Clock
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
SIX2
Enhanced UART Clock (Mode 0 and 2)
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
T2X2
Timer2 Clock
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
T1X2
Timer1 Clock
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
T0X2
Timer0 Clock
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
X2
System Clock Control bit
Clear to select 12 clock periods per machine cycle (STD mode, FCPU = FPER =
FOSC/2).
Set to select 6 clock periods per machine cycle (X2 mode, FCPU = FPER = FOSC).
Reset Value = 0000 0000b
22
AT89C5131
4136B–USB–09/03
AT89C5131
Table 29. CKCON1 (S:AFh)
Clock Control Register 1
7
6
5
4
3
2
1
0
-
-
-
-
-
-
-
SPIX2
Bit
Bit Number Mnemonic Description
7-1
0
-
SPIX2
Reserved
The value read from this bit is always 0. Do not set this bit.
SPI Clock
This control bit is validated when the CPU clock X2 is set. When X2 is low,
this bit has no effect.
Clear to select 6 clock periods per peripheral clock cycle.
Set to select 12 clock periods per peripheral clock cycle.
Reset Value = 0000 0000b
Table 30. PLLCON (S:A3h)
PLL Control Register
7
6
5
4
3
2
1
0
-
-
-
-
-
EXT48
PLLEN
PLOCK
Bit
Bit Number Mnemonic Description
7-3
-
Reserved
The value read from this bit is always 0. Do not set this bit.
2
EXT48
External 48 MHz Enable Bit
Set this bit to bypass the PLL and disable the crystal oscillator.
Clear this bit to select the PLL output as USB clock and to enable the crystal
oscillator.
1
PLLEN
PLL Enable Bit
Set to enable the PLL.
Clear to disable the PLL.
0
PLOCK
PLL Lock Indicator
Set by hardware when PLL is locked.
Clear by hardware when PLL is unlocked.
Reset Value = 0000 0000b
Table 31. PLLDIV (S:A4h)
PLL Divider Register
7
6
5
4
3
2
1
0
R3
R2
R1
R0
N3
N2
N1
N0
Bit
Bit Number Mnemonic Description
7-4
R3:0
PLL R Divider Bits
3-0
N3:0
PLL N Divider Bits
Reset Value = 0000 0000
23
4136B–USB–09/03
Dual Data Pointer
Register
The additional data pointer can be used to speed up code execution and reduce code
size.
The dual DPTR structure is a way by which the chip will specify the address of an external data memory location. There are two 16-bit DPTR registers that address the external
memory, and a single bit called DPS = AUXR1.0 (see Table 32) that allows the program
code to switch between them (see Figure 10).
Figure 10. Use of Dual Pointer
External Data Memory
7
0
DPS
DPTR1
DPTR0
AUXR1(A2H)
DPH(83H) DPL(82H)
Table 32. AUXR1 Register
AUXR1- Auxiliary Register 1(0A2h)
7
6
5
4
3
2
1
0
-
-
ENBOOT
-
GF3
0
-
DPS
Bit
Bit
Number
Mnemonic
7
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
6
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
5
ENBOOT
Description
Enable Boot Flash
Cleared to disable boot ROM.
Set to map the boot ROM between F800h - 0FFFFh.
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
-
3
GF3
2
0
Always cleared.
1
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
0
DPS
This bit is a general-purpose user flag.
Data Pointer Selection
Cleared to select DPTR0.
Set to select DPTR1.
Reset Value = XXXX XX0X0b
Not bit addressable
a. Bit 2 stuck at 0; this allows to use INC AUXR1 to toggle DPS without changing GF3.
24
AT89C5131
4136B–USB–09/03
AT89C5131
ASSEMBLY LANGUAGE
; Block move using dual data pointers
; Modifies DPTR0, DPTR1, A and PSW
; note: DPS exits opposite of entry state
; unless an extra INC AUXR1 is added
;
00A2 AUXR1 EQU 0A2H
;
0000 909000MOV DPTR,#SOURCE ; address of SOURCE
0003 05A2 INC AUXR1 ; switch data pointers
0005 90A000 MOV DPTR,#DEST ; address of DEST
0008 LOOP:
0008 05A2 INC AUXR1 ; switch data pointers
000A E0 MOVX A,@DPTR ; get a byte from SOURCE
000B A3 INC DPTR ; increment SOURCE address
000C 05A2 INC AUXR1 ; switch data pointers
000E F0 MOVX @DPTR,A ; write the byte to DEST
000F A3 INC DPTR ; increment DEST address
0010 70F6JNZ LOOP ; check for 0 terminator
0012 05A2 INC AUXR1 ; (optional) restore DPS
INC is a short (2 bytes) and fast (12 clocks) way to manipulate the DPS bit in the AUXR1
SFR. However, note that the INC instruction does not directly force the DPS bit to a particular state, but simply toggles it. In simple routines, such as the block move example,
only the fact that DPS is toggled in the proper sequence matters, not its actual value. In
other words, the block move routine works the same whether DPS is ’0’ or ’1’ on entry.
Observe that without the last instruction (INC AUXR1), the routine will exit with DPS in
the opposite state.
25
4136B–USB–09/03
Program/Code
Memory
The AT89C5131 implement 32 Kbytes of on-chip program/code memory. Figure 11
shows the split of internal and external program/code memory spaces depending on the
product.
The Flash memory increases EPROM and ROM functionality by in-circuit electrical erasure and programming. Thanks to the internal charge pump, the high voltage needed for
programming or erasing Flash cells is generated on-chip using the standard VDD voltage. Thus, the Flash Memory can be programmed using only one voltage and allows Inapplication Software Programming commonly known as IAP. Hardware programming
mode is also available using specific programming tool.
Figure 11. Program/Code Memory Organization
FFFFh
32 Kbytes
External Code
8000h
7FFFh1
32 Kbytes
Flash
0000h
AT89C5131
Note:
If the program executes exclusively from on-chip code memory (not from external memory), beware of executing code from the upper byte of on-chip memory (7FFFh) and
thereby disrupting I/O Ports 0 and 2 due to external prefetch. Fetching code constant
from this location does not affect Ports 0 and 2.
External Code Memory
Access
Memory Interface
The external memory interface comprises the external bus (Port 0 and Port 2) as well as
the bus control signals (PSEN, and ALE).
Figure 12 shows the structure of the external address bus. P0 carries address A7:0
while P2 carries address A15:8. Data D7:0 is multiplexed with A7:0 on P0. Table 33
describes the external memory interface signals.
Figure 12. External Code Memory Interface Structure
Flash
EPROM
AT89C5131
A15:8
P2
A15:8
ALE
P0
AD7:0
Latch
A7:0
A7:0
D7:0
PSEN
26
OE
AT89C5131
4136B–USB–09/03
AT89C5131
Table 33. External Data Memory Interface Signals
External Bus Cycles
Signal
Name
Type
Alternate
Function
A15:8
O
Address Lines
Upper address lines for the external bus.
P2.7:0
AD7:0
I/O
Address/Data Lines
Multiplexed lower address lines and data for the external memory.
P0.7:0
ALE
O
Address Latch Enable
ALE signals indicates that valid address information are available on lines
AD7:0.
-
PSEN
O
Program Store Enable Output
This signal is active low during external code fetch or external code read
(MOVC instruction).
-
Description
This section describes the bus cycles the AT89C5131 executes to fetch code (see
Figure 13) in the external program/code memory.
External memory cycle takes 6 CPU clock periods. This is equivalent to 12 oscillator
clock periods in standard mode or 6 oscillator clock periods in X2 mode. For further
information on X2 mode (see the clock Section).
For simplicity, the accompanying figure depicts the bus cycle waveforms in idealized
form and do not provide precise timing information.
Figure 13. External Code Fetch Waveforms
CPU Clock
ALE
PSEN
P0 D7:0
P2 PCH
Flash Memory
Architecture
PCL
D7:0
PCH
PCL
D7:0
PCH
AT89C5131 features two on-chip Flash memories:
•
Flash memory FM0:
containing 32 Kbytes of program memory (user space) organized into 128-byte
pages,
•
Flash memory FM1:
3 Kbytes for bootloader and Application Programming Interfaces (API).
The FM0 supports both parallel programming and Serial In-System Programming (ISP)
whereas FM1 supports only parallel programming by programmers. The ISP mode is
detailed in the “In-System Programming” section.
All Read/Write access operations on Flash memory by user application are managed by
a set of API described in the “In-System Programming” section.
27
4136B–USB–09/03
Figure 14. Flash Memory Architecture
3 Kbytes
Flash Memory
Boot Space
Hardware Security (1 Byte)
Extra Row (128 Bytes)
Column Latches (128 Bytes)
FM1
7FFFh
32 Kbytes
FFFFh
F400h
FM1 mapped between FFFFh and
F400h when bit ENBOOT is set in
AUXR1 register
Flash Memory
User Space
FM0
0000h
FM0 Memory Architecture
The Flash memory is made up of 4 blocks (see Figure 14):
1. The memory array (user space) 32 Kbytes
2. The Extra Row
3. The Hardware security bits
4. The column latch registers
User Space
This space is composed of a 32 Kbytes Flash memory organized in 256 pages of 128
bytes. It contains the user’s application code.
Extra Row (XRow)
This row is a part of FM0 and has a size of 128 bytes. The extra row may contain information for bootloader usage.
Hardware Security Space
The hardware security space is a part of FM0 and has a size of 1 byte.
The 4 MSB can be read/written by software. The 4 LSB can only be read by software
and written by hardware in parallel mode.
Column Latches
The column latches, also part of FM0, have a size of full page (128 bytes).
The column latches are the entrance buffers of the three previous memory locations
(user array, XRow and Hardware security byte).
Overview of FM0
Operations
The CPU interfaces to the Flash memory through the FCON register and AUXR1
register.
These registers are used to:
•
Map the memory spaces in the adressable space
•
Launch the programming of the memory spaces
•
Get the status of the Flash memory (busy/not busy)
•
Select the Flash memory FM0/FM1.
Mapping of the Memory Space By default, the user space is accessed by MOVC instruction for read only. The column
latches space is made accessible by setting the FPS bit in FCON register. Writing is
possible from 0000h to 7FFFh, address bits 6 to 0 are used to select an address within a
page while bits 14 to 7 are used to select the programming address of the page.
Setting this bit takes precedence on the EXTRAM bit in AUXR register.
28
AT89C5131
4136B–USB–09/03
AT89C5131
The other memory spaces (user, extra row, hardware security) are made accessible in
the code segment by programming bits FMOD0 and FMOD1 in FCON register in accordance with Table 34. A MOVC instruction is then used for reading these spaces.
Table 34. FM0 Blocks Select Bits
Launching Programming
FMOD1
FMOD0
FM0 Adressable Space
0
0
User (0000h-FFFFh)
0
1
Extra Row(FF80h-FFFFh)
1
0
Hardware Security (0000h)
1
1
reserved
FPL3:0 bits in FCON register are used to secure the launch of programming. A specific
sequence must be written in these bits to unlock the write protection and to launch the
programming. This sequence is 5 followed by A. Table 35 summarizes the memory
spaces to program according to FMOD1:0 bits.
Table 35. Programming Spaces
Write to FCON
FPL3:0
FPS
FMOD1
FMOD0
Operation
5
X
0
0
No action
A
X
0
0
Write the column latches in user
space
5
X
0
1
No action
A
X
0
1
Write the column latches in extra row
space
5
X
1
0
No action
A
X
1
0
Write the fuse bits space
5
X
1
1
No action
A
X
1
1
No action
User
Extra Row
Security
Space
Reserved
The Flash memory enters a busy state as soon as programming is launched. In this
state, the memory is not available for fetching code. Thus to avoid any erratic execution
during programming, the CPU enters Idle mode. Exit is automatically performed at the
end of programming.
Note:
Status of the Flash Memory
Interrupts that may occur during programming time must be disabled to avoid any spurious exit of the idle mode.
The bit FBUSY in FCON register is used to indicate the status of programming.
FBUSY is set when programming is in progress.
Selecting FM0/FM1
The bit ENBOOT in AUXR1 register is used to choose between FM0 and FM1 mapped
up to F800h.
29
4136B–USB–09/03
Loading the Column Latches
Any number of data from 1 byte to 128 bytes can be loaded in the column latches. This
provides the capability to program the whole memory by byte, by page or by any number
of bytes in a page.
When programming is launched, an automatic erase of the locations loaded in the column latches is first performed, then programming is effectively done. Thus, no page or
block erase is needed and only the loaded data are programmed in the corresponding
page.
The following procedure is used to load the column latches and is summarized in
Figure 15:
•
Map the column latch space by setting FPS bit.
•
Load the DPTR with the address to load.
•
Load Accumulator register with the data to load.
•
Execute the MOVX @DPTR, A instruction.
•
If needed loop the three last instructions until the page is completely loaded.
Figure 15. Column Latches Loading Procedure
Column Latches
Loading
Column Latches Mapping
FPS = 1
Data Load
DPTR = Address
ACC = Data
Exec: MOVX @DPTR, A
Last Byte
to load?
Data memory Mapping
FPS = 0
Programming the Flash Spaces
User
The following procedure is used to program the User space and is summarized in
Figure 16:
• Load data in the column latches from address 0000h to 7FFFh(1).
• Disable the interrupts.
• Launch the programming by writing the data sequence 50h followed by A0h in
FCON register.
The end of the programming indicated by the FBUSY flag cleared.
• Enable the interrupts.
Note:
30
1. The last page address used when loading the column latch is the one used to select
the page programming address.
AT89C5131
4136B–USB–09/03
AT89C5131
Extra Row
The following procedure is used to program the Extra Row space and is summarized in
Figure 16:
•
Load data in the column latches from address FF80h to FFFFh.
•
Disable the interrupts.
•
Launch the programming by writing the data sequence 52h followed by A2h in
FCON register.
The end of the programming indicated by the FBUSY flag cleared.
•
Enable the interrupts.
Figure 16. Flash and Extra Row Programming Procedure
Flash Spaces
Programming
Column Latches Loading
see Figure 15
Disable IT
EA = 0
Launch Programming
FCON = 5xh
FCON = Axh
FBusy
Cleared?
Erase Mode
FCON = 00h
End Programming
Enable IT
EA = 1
31
4136B–USB–09/03
Hardware Security
The following procedure is used to program the Hardware Security space and is summarized in Figure 17:
•
Set FPS and map Hardware byte (FCON = 0x0C)
•
Disable the interrupts.
•
Load DPTR at address 0000h.
•
Load Accumulator register with the data to load.
•
Execute the MOVX @DPTR, A instruction.
•
Launch the programming by writing the data sequence 54h followed by A4h in
FCON register.
The end of the programming indicated by the FBusy flag cleared.
•
Enable the interrupts.
Figure 17. Hardware Programming Procedure
Flash Spaces
Programming
FCON = 0Ch
Data Load
DPTR = 00h
ACC = Data
Exec: MOVX @DPTR, A
Disable IT
EA = 0
Launch Programming
FCON = 54h
FCON = A4h
FBusy
Cleared?
Erase Mode
FCON = 00h
End Programming
Enable IT
EA = 1
32
AT89C5131
4136B–USB–09/03
AT89C5131
Reading the Flash Spaces
User
Extra Row
Hardware Security
The following procedure is used to read the User space and is summarized in Figure 18:
•
Map the User space by writing 00h in FCON register.
•
Read one byte in Accumulator by executing MOVC A, @A+DPTR with A = 0 &
DPTR = 0000h to FFFFh.
The following procedure is used to read the Extra Row space and is summarized in
Figure 18:
•
Map the Extra Row space by writing 02h in FCON register.
•
Read one byte in Accumulator by executing MOVC A, @A+DPTR with A = 0 &
DPTR = FF80h to FFFFh.
The following procedure is used to read the Hardware Security space and is summarized in Figure 18:
•
Map the Hardware Security space by writing 04h in FCON register.
•
Read the byte in Accumulator by executing MOVC A, @A+DPTR with A = 0 &
DPTR = 0000h.
Figure 18. Reading Procedure
Flash Spaces Reading
Flash Spaces Mapping
FCON = 00000xx0b
Data Read
DPTR = Address
ACC = 0
Exec: MOVC A, @A+DPTR
Erase Mode
FCON = 00h
33
4136B–USB–09/03
Registers
Table 36. FCON (S:D1h)
Flash Control Register
7
6
5
4
3
2
1
0
FPL3
FPL2
FPL1
FPL0
FPS
FMOD1
FMOD0
FBUSY
Bit
Bit Number Mnemonic Description
7-4
FPL3:0
3
FPS
2-1
FMOD1:0
0
FBUSY
Programming Launch Command Bits
Write 5Xh followed by AXh to launch the programming according to FMOD1:0.
(see Table 35.)
Flash Map Program Space
Set to map the column latch space in the data memory space.
Clear to re-map the data memory space.
Flash Mode
See Table 34 or Table 35.
Flash Busy
Set by hardware when programming is in progress.
Clear by hardware when programming is done.
Can not be cleared by software.
Reset Value = 0000 0000b
34
AT89C5131
4136B–USB–09/03
AT89C5131
Flash EEPROM Memory
General Description
The Flash memory increases EPROM functionality with in-circuit electrical erasure and
programming. It contains 32 Kbytes of program memory organized in 256 pages of 128
bytes, respectively. This memory is both parallel and serial In-System Programmable
(ISP). ISP allows devices to alter their own program memory in the actual end product
under software control. A default serial loader (bootloader) program allows ISP of the
Flash.
The programming does not require 12V external programming voltage. The necessary
high programming voltage is generated on-chip using the standard VCC pins of the
microcontroller.
Features
Flash Programming and
Erasure
•
Flash EEPROM internal program memory.
•
Boot vector allows user-provided Flash loader code to reside anywhere in the Flash
memory space. This configuration provides flexibility to the user.
•
Default loader in Boot EEPROM allows programming via the serial port without the
need of a user provided loader.
•
Up to 64K bytes external program memory if the internal program memory is
disabled (EA = 0).
•
Programming and erase voltage with standard 5V or 3.3V VCC supply.
•
Read/Program/Erase:
•
Byte-wise read (without wait state).
•
Byte or page erase and programming (10 ms).
•
Typical programming time (32 Kbytes) in 10 sec.
•
Parallel programming with 87C51 compatible hardware interface to programmer.
•
Programmable security for the code in the Flash.
•
100K write cycles
•
10 years data retention
The 32 Kbytes Flash is programmed by bytes or by pages of 128 bytes. It is not necessary to erase a byte or a page before programming. The programming of a byte or a
page includes a self erase before programming.
There are three methods of programming the Flash memory:
1. The on-chip ISP bootloader may be invoked which will use low level routines to
program the pages. The interface used for serial downloading of Flash is the
UART.
2. The Flash may be programmed or erased in the end-user application by calling
low-level routines through a common entry point in the Boot ROM.
3. The Flash may be programmed using the parallel method by using a conventional EPROM programmer. The parallel programming method used by these
devices is similar to that used by EPROM 87C51 but it is not identical and the
commercially available programmers need to have support for the AT89C5131.
The bootloader and the Application Programming Interface (API) routines are located in
the Boot ROM.
35
4136B–USB–09/03
Flash Registers and
Memory Map
Hardware Registers
The AT89C5131 Flash memory uses several registers:
•
Hardware registers can only be accessed through the parallel programming modes
which are handled by the parallel programmer.
•
Software registers are in a special page of the Flash memory which can be
accessed through the API or with the parallel programming modes. This page,
called “Extra Flash Memory”, is not in the internal Flash program memory
addressing space.
The only hardware registers of the AT89C5131 is called Hardware Security Byte (HSB).
Table 37. Hardware Security Byte (HSB)
7
6
5
4
3
2
1
0
X2
BLJB
OSCON1
OSCON0
-
LB2
LB1
LB0
Bit
Bit
Number
Mnemonic
7
X2
Description
X2 Mode
Cleared to force X2 mode (6 clocks per instruction)
Set to force X1 mode, Standard Mode (Default).
Bootloader Jump Bit
6
BLJB
Set this bit to start the user’s application on next reset at address 0000h.
Cleared this bit to start the bootloader at address F400h (default).
Oscillator Control Bits
These two bits are used to control the oscillator in order to reduce consummation.
5-4
Bootloader Jump Bit (BLJB)
Flash Memory Lock Bits
36
OSCON
OSCON1-0 1
1
0
0
3
-
2-0
LB2-0
OSCON0
1
0
1
0
Description
The oscillator is configured to run from 0 to 32 MHz
The oscillator is configured to run from 0 to 16 MHz
The oscillator is configured to run from 0 to 8 MHz
This configuration shouldn’t be set
Reserved
User Memory Lock Bits
See Table 38
One bit of the HSB, the BLJB bit, is used to force the boot address:
•
When this bit is set the boot address is 0000h.
•
When this bit is reset the boot address is F400h. By default, this bit is cleared and
the ISP is enabled.
The three lock bits provide different levels of protection for the on-chip code and data,
when programmed as shown in Table 38.
AT89C5131
4136B–USB–09/03
AT89C5131
Table 38. Program Lock bits
Program Lock Bits
Security level
LB0
LB1
LB2
1
U
U
U
No program lock features enabled.
Notes:
Protection Description
2
P
U
U
MOVC instruction executed from external
program memory is disabled from fetching code
bytes from any internal memory, EA is sampled
and latched on reset, and further parallel
programming of the Flash and of the EEPROM
(boot and Xdata) is disabled. ISP and software
programming with API are still allowed.
3
X
P
U
Same as 2, also verify through parallel
programming interface is disabled and serial
programming ISP is disabled.
4
X
X
P
Same as 3, also external execution is disabled.
1.
2.
3.
4.
U: unprogrammed or “one” level.
P: programmed or “zero” level.
X: don’t care
WARNING: Security level 2 and 3 should only be programmed after Flash and code
verification.
These security bits protect the code access through the parallel programming interface.
They are set by default to level 4. The code access through the ISP is still possible and
is controlled by the “software security bits” which are stored in the extra Flash memory
accessed by the ISP firmware.
To load a new application with the parallel programmer, a chip erase must be done first.
This will set the HSB in its inactive state and will erase the Flash memory. The part reference can always be read using Flash parallel programming modes.
Default Values
Software Registers
The default value of the HSB provides parts ready to be programmed with ISP:
•
BLJB: Cleared to force ISP operation.
•
X2: Set to force X1 mode (Standard Mode)
•
OSCON1-0: Set to start with 32 MHz oscillator configuration value.
•
LB2-0: Security level four to protect the code from a parallel access with maximum
security.
Several registers are used, in factory and by parallel programmers, to make copies of
hardware registers contents. These values are used by Atmel ISP (see Section “In-System Programming (ISP)”).
These registers are in the “Extra Flash Memory” part of the Flash memory. This block is
also called ”XAF” or eXtra Array Flash. They are accessed in the following ways:
•
Commands issued by the parallel memory programmer.
•
Commands issued by the ISP software.
•
Calls of API issued by the application software.
Several software registers are described in Table 39.
37
4136B–USB–09/03
Table 39. Software Registers
Mnemonic
Description
Default value
SBV
Software Boot Vector
FCh
–
HSB
Copy of the Hardware
Security Byte
1011 1000b
–
BSB
Boot Status Byte
0FFh
–
SSB
Software Security Byte
FFh
–
–
Copy of the Manufacturer
Code
58h
Atmel
–
Copy of the Device ID #1:
Family Code
D7h
C51 X2, Electrically
Erasable
–
Copy of the Device ID #2:
Memories
F7h
AT89C5131 32 Kbyte
–
Size and Type
FBh
AT89C5131 16 Kbyte
–
Copy of the Device ID #3:
Name
EFh
AT89C5131 32 Kbyte,
revision 0
–
Revision
FFh
AT89C5131 16 Kbyte,
revision 0
After programming the part by ISP, the BSB must be cleared (00h) in order to allow the
application to boot at 0000h.
The content of the Software Security Byte (SSB) is described in Table 40 and Table 41.
To assure code protection from a parallel access, the HSB must also be at the required
level.
Table 40. Software Security Byte (SSB)
38
7
6
5
4
3
2
1
0
-
-
-
-
-
-
LB1
LB0
Bit
Bit
Number
Mnemonic
7
-
Reserved
Do not clear this bit.
6
-
Reserved
Do not clear this bit.
5
-
Reserved
Do not clear this bit.
4
-
Reserved
Do not clear this bit.
3
-
Reserved
Do not clear this bit.
2
-
Reserved
Do not clear this bit.
1-0
LB1-0
Description
User Memory Lock Bits
See Table 41
AT89C5131
4136B–USB–09/03
AT89C5131
The two lock bits provide different levels of protection for the on-chip code and data,
when programmed as shown to Table 41.
Table 41. Program Lock Bits of the SSB
Program Lock Bits
Security
Level
LB0
LB1
1
U
U
No program lock features enabled.
2
P
U
ISP programming of the Flash is disabled.
3
X
P
Same as 2, also verify through ISP programming interface is disabled.
Notes:
Flash Memory Status
1.
2.
3.
4.
Protection Description
U: unprogrammed or "one" level.
P: programmed or “zero” level.
X: don’t care
WARNING: Security level 2 and 3 should only be programmed after Flash and code
verification.
AT89C5131 parts are delivered with the ISP boot in the Flash memory. After ISP or parallel programming, the possible contents of the Flash memory are summarized in Figure
19:
Figure 19. Flash Memory Possible Contents
7FFFh AT89C5131
Virgin
Application
Virgin
or
Application
Application
Dedicated
ISP
Virgin
or
Application
Virgin
or
Application
Dedicated
ISP
0000h
Default
Memory Organization
After ISP
After ISP
After parallel
programming
After parallel
programming
After parallel
programming
In the AT89C5131, the lowest 16K or 32K of the 64 Kbyte program memory address
space is filled by internal Flash.
When the EA is pin high, the processor fetches instructions from internal program Flash.
Bus expansion for accessing program memory from 16K or 32K upward is automatic
since external instruction fetches occur automatically when the program counter
exceeds 3FFFh (16K) or 7FFFh (32K). If the EA pin is tied low, all program memory
fetches are from external memory. If all storage is on chip, then byte location 3FFFh
(16K) or 7FFFh (32K) should be left vacant to prevent and undesired pre-fetch from
external program memory address 4000h (16K) or 8000h (32K).
39
4136B–USB–09/03
EEPROM Data Memory
Description
The 1-Kbyte on-chip EEPROM memory block is located at addresses 0000h to 03FFh of
the ERAM memory space and is selected by setting control bits in the EECON register.
A read in the EEPROM memory is done with a MOVX instruction.
A physical write in the EEPROM memory is done in two steps: write data in the column
latches and transfer of all data latches into an EEPROM memory row (programming).
The number of data written on the page may vary from 1 to 128 bytes (the page size).
When programming, only the data written in the column latch is programmed and a ninth
bit is used to obtain this feature. This provides the capability to program the whole memory by bytes, by page or by a number of bytes in a page. Indeed, each ninth bit is set
when the writing the corresponding byte in a row and all these ninth bits are reset after
the writing of the complete EEPROM row.
Write Data in the Column
Latches
Data is written by byte to the column latches as for an external RAM memory. Out of the
11 address bits of the data pointer, the 4 MSBs are used for page selection (row) and 7
are used for byte selection. Between two EEPROM programming sessions, all the
addresses in the column latches must stay on the same page, meaning that the 4 MSB
must not be changed.
The following procedure is used to write to the column latches:
Programming
Read Data
40
•
Set bit EEE of EECON register
•
Load DPTR with the address to write
•
Store A register with the data to be written
•
Execute a MOVX @DPTR, A
•
If needed, loop the three last instructions until the end of a 128 bytes page
The EEPROM programming consists on the following actions:
•
Writing one or more bytes of one page in the column latches. Normally, all bytes
must belong to the same page; if not, the first page address will be latched and the
others discarded.
•
Launching programming by writing the control sequence (54h followed by A4h) to
the EECON register.
•
EEBUSY flag in EECON is then set by hardware to indicate that programming is in
progress and that the EEPROM segment is not available for reading.
•
The end of programming is indicated by a hardware clear of the EEBUSY flag.
The following procedure is used to read the data stored in the EEPROM memory:
•
Set bit EEE of EECON register
•
Stretch the MOVX to accommodate the slow access time of the column latch (Set
bit M0 of AUXR register)
•
Load DPTR with the address to read
•
Execute a MOVX A, @DPTR
AT89C5131
4136B–USB–09/03
AT89C5131
Registers
Table 42. EECON (S:0D2h)
EECON Register
7
6
5
4
3
2
1
0
EEPL3
EEPL2
EEPL1
EEPL0
-
-
EEE
EEBUSY
Bit Number
Bit
Mnemonic
7-4
EEPL3-0
Programming Launch command bits
Write 5Xh followed by AXh to EEPL to launch the programming.
3
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
2
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
1
0
EEE
EEBUSY
Description
Enable EEPROM Space bit
Set to map the EEPROM space during MOVX instructions (Write in the column
latches)
Clear to map the ERAM space during MOVX.
Programming Busy flag
Set by hardware when programming is in progress.
Cleared by hardware when programming is done.
Cannot be set or cleared by software.
Reset Value = XXXX XX00b
Not bit addressable
41
4136B–USB–09/03
In-System
Programming (ISP)
With the implementation of the User Space (FM0) and the Boot Space (FM1) in Flash
technology the AT89C5131 allows the system engineer the development of applications
with a very high level of flexibility. This flexibility is based on the possibility to alter the
customer program at any stages of a product’s life:
•
Before mounting the chip on the PCB, FM0 flash can be programmed with the
application code. FM1 is always preprogrammed by Atmel with a bootloader (chip
can be ordered with USB bootloader).(1)
•
Once the chip is mounted on the PCB, it can be programmed by serial mode via the
USB bus.
Note:
1. The user can also program his own bootloader in FM1.
This ISP allows code modification over the total lifetime of the product.
Besides the default Bootloaders Atmel provide customers all the needed ApplicationProgramming-Interfaces (API) which are needed for the ISP. The API are located in the
Boot memory.
This allow the customer to have a full use of the 32-Kbyte user memory.
Flash Programming and
Erasure
There are three methods for programming the Flash memory:
•
The Atmel bootloader located in FM1 is activated by the application. Low level API
routines (located in FM1)will be used to program FM0. The interface used for serial
downloading to FM0 is the USB. API can be called also by user’s bootloader located
in FM0 at [SBV]00h.
•
A further method exist in activating the Atmel boot loader by hardware activation.
See the Section “Hardware Security Byte”.
•
The FM0 can be programmed also by the parallel mode using a programmer.
Figure 20. Flash Memory Mapping
FFFFh
F400h
3K Bytes IAP
Bootloader
FM1
7FFFh
Custom
Bootloader
FM1 Mapped between F400h and FFFFh
when API Called
[SBV]00h
32K Bytes
Flash Memory
FM0
0000h
42
AT89C5131
4136B–USB–09/03
AT89C5131
Boot Process
Software Boot Process
Example
Many algorithms can be used for the software boot process. Below are descriptions of
the different flags and Bytes.
Boot Loader Jump bit (BLJB):
- This bit indicates if on RESET the user wants to jump to this application at address
@0000h on FM0 or execute the boot loader at address @F400h on FM1.
- BLJB = 0 (i.e. bootloader FM1 executed after a reset) is the default Atmel factory programming.
-To read or modify this bit, the APIs are used.
Boot Vector Address (SBV):
- This byte contains the MSB of the user boot loader address in FM0.
- The default value of SBV is FFh (no user boot loader in FM0).
- To read or modify this byte, the APIs are used.
Extra Byte (EB) & Boot Status Byte (BSB):
- These Bytes are reserved for customer use.
- To read or modify these Bytes, the APIs are used.
Figure 21. Hardware Boot Process Algorithm
bit ENBOOT in AUXR1 Register
Is Initialized with BLJB Inverted.
RESET
Hardware
Example, if BLJB=0, ENBOOT
is set (=1) during reset, thus the
bootloader is executed after the
reset.
ENBOOT = 0
PC = 0000h
BLJB == 0
?
Software
ENBOOT = 1
PC = F400h
Application
in FM0
Bootloader
in FM1
43
4136B–USB–09/03
ApplicationProgramming-Interface
Several Application Program Interface (API) calls are available for use by an application
program to permit selective erasing and programming of Flash pages. All calls are made
by functions.
All these APIs are described in detail in the following document on the Atmel web site.
–
XROW Bytes
Datasheet Bootloader USB AT89C5131.
The EXTRA ROW (XROW) includes 128 bytes. Some of these bytes are used for specific purpose in conjonction with the bootloader.
Table 43. XROW Mapping
Description
Hardware Conditions
Default Value
Address
Copy of the Manufacturer Code
58h
30h
Copy of the Device ID#1: Family code
D7h
31h
Copy of the Device ID#2: Memories size and type
BBh
60h
Copy of the Device ID#3: Name and Revision
FFh
61h
It is possible to force the controller to execute the bootloader after a Reset with hardware conditions.
During the first programming, the user can define a configuration on Port1 that will be
recognized by the chip as the hardware conditions during a Reset. If this condition is
met, the chip will start executing the bootloader at the end of the Reset.
See a detailed description in the applicable Document.
–
44
Datasheet Bootloader USB AT89C5131.
AT89C5131
4136B–USB–09/03
AT89C5131
Hardware Security Byte
Table 44. Hardware Security Byte
7
6
5
4
3
2
1
0
X2B
BLJB
OSCON1
OSCON0
-
LB2
LB1
LB0
Bit Number
Bit
Mnemonic
7
X2B
6
BLJB
Description
X2 Bit
Set this bit to start in standard mode
Clear this bit to start in X2 mode.
Bootloader Jump Bit
Set this bit to start the user’s application on next reset at address 0000h.
Cleared this bit to start the bootloader at address F400h (default).
5-4
OSCON1-0
3
-
2-0
LB2:0
Oscillator Control Bits
These two bits are used to control the oscillator in order to reduce
consumption.
OSCON1 OSCON0 Description
1
1
oscillator is configured to run from 0 to 32 MHz
1
0
oscillator is configured to run from 0 to 16 MHz
0
1
oscillator is configured to run from 0 to 8 MHz
0
0
this configuration shouldn’t be set
Reserved
The value read from this bit is indeterminate.
Lock Bits
Default value after erasing chip: FFh
Notes:
1. Only the 4 MSB bits can be access by software.
2. The 4 LSB bits can only be access by parallel mode.
45
4136B–USB–09/03
On-chip Expanded
RAM (ERAM)
The AT89C5131 provides additional Bytes of random access memory (RAM) space for
increased data parameter handling and high level language usage.
AT89C5131 devices have expanded RAM in external data space; maximum size and
location are described in Table 45.
Table 45. Description of Expanded RAM
Address
Part Number
ERAM Size
Start
End
AT89C5131
1024
00h
3FFh
The AT89C5131 has on-chip data memory that is mapped into the following four separate segments.
1. The Lower 128 bytes of RAM (addresses 00h to 7Fh) are directly and indirectly
addressable.
2. The Upper 128 bytes of RAM (addresses 80h to FFh) are indirectly addressable
only.
3. The Special Function Registers, SFRs, (addresses 80h to FFh) are directly
addressable only.
4. The expanded RAM bytes are indirectly accessed by MOVX instructions, and
with the EXTRAM bit cleared in the AUXR register (see Table 45)
The lower 128 bytes can be accessed by either direct or indirect addressing. The Upper
128 bytes can be accessed by indirect addressing only. The Upper 128 bytes occupy
the same address space as the SFR. That means they have the same address, but are
physically separate from SFR space.
Figure 22. Internal and External Data Memory Address
0FFh or 3FFh
0FFh
Upper
128 bytes
Internal
RAM
indirect accesses
ERAM
0FFFFh
0FFh
80h
Special
Function
Register
direct accesses
External
Data
Memory
80h
7Fh
Lower
128 bytes
Internal
RAM
direct or indirect
accesses
00
46
00
00FFh up to 03FFh
0000
AT89C5131
4136B–USB–09/03
AT89C5131
When an instruction accesses an internal location above address 7Fh, the CPU knows
whether the access is to the upper 128 bytes of data RAM or to SFR space by the
addressing mode used in the instruction.
•
Instructions that use direct addressing access SFR space. For example: MOV
0A0H, # data, accesses the SFR at location 0A0h (which is P2).
•
Instructions that use indirect addressing access the Upper 128 bytes of data RAM.
For example: MOV atR0, # data where R0 contains 0A0h, accesses the data byte at
address 0A0h, rather than P2 (whose address is 0A0h).
•
The ERAM bytes can be accessed by indirect addressing, with EXTRAM bit cleared
and MOVX instructions. This part of memory which is physically located on-chip,
logically occupies the first bytes of external data memory. The bits XRS0 and XRS1
are used to hide a part of the available ERAM as explained in Table 45. This can be
useful if external peripherals are mapped at addresses already used by the internal
ERAM.
•
With EXTRAM = 0, the ERAM is indirectly addressed, using the MOVX instruction in
combination with any of the registers R0, R1 of the selected bank or DPTR. An
access to ERAM will not affect ports P0, P2, P3.6 (WR) and P3.7 (RD). For
example, with EXTRAM = 0, MOVX atR0, # data where R0 contains 0A0H,
accesses the ERAM at address 0A0H rather than external memory. An access to
external data memory locations higher than the accessible size of the ERAM will be
performed with the MOVX DPTR instructions in the same way as in the standard
80C51, with P0 and P2 as data/address busses, and P3.6 and P3.7 as write and
read timing signals. Accesses to ERAM above 0FFH can only be done by the use of
DPTR.
•
With EXTRAM = 1, MOVX @Ri and MOVX @DPTR will be similar to the standard
80C51. MOVX at Ri will provide an eight-bit address multiplexed with data on Port0
and any output port pins can be used to output higher order address bits. This is to
provide the external paging capability. MOVX @DPTR will generate a sixteen-bit
address. Port2 outputs the high-order eight address bits (the contents of DPH) while
Port0 multiplexes the low-order eight address bits (DPL) with data. MOVX at Ri and
MOVX @DPTR will generate either read or write signals on P3.6 (WR) and P3.7
(RD).
The stack pointer (SP) may be located anywhere in the 256 bytes RAM (lower and
upper RAM) internal data memory. The stack may not be located in the ERAM.
The M0 bit allows to stretch the ERAM timings; if M0 is set, the read and write pulses
are extended from 6 to 30 clock periods. This is useful to access external slow
peripherals.
47
4136B–USB–09/03
Table 46. AUXR Register
AUXR - Auxiliary Register (8Eh)
7
6
5
4
3
2
1
0
DPU
-
M0
-
XRS1
XRS0
EXTRAM
AO
Bit
Bit
Number
Mnemonic
7
DPU
6
-
Description
Disable Weak Pull Up
Cleared to enabled weak pull up on standard Ports.
Set to disable weak pull up on standard Ports.
Reserved
The value read from this bit is indeterminate. Do not set this bit
Pulse length
5
M0
Cleared to stretch MOVX control: the RD and the WR pulse length is 6 clock
periods (default).
Set to stretch MOVX control: the RD and the WR pulse length is 30 clock
periods.
4
-
3
XRS1
2
1
XRS0
EXTRAM
Reserved
The value read from this bit is indeterminate. Do not set this bit
ERAM Size
XRS1
0
XRS0
0
ERAM size
256 bytes
0
1
512 bytes
1
0
768 bytes
1
1
1024 bytes (default)
EXTRAM bit
Cleared to access internal ERAM using MOVX at Ri at DPTR.
Set to access external memory.
0
AO
ALE Output bit
Cleared, ALE is emitted at a constant rate of 1/6 the oscillator frequency (or
1/3 if X2 mode is used) (default).
Set, ALE is active only when a MOVX or MOVC instruction is used.
Reset Value = 0X0X 1100b
Not bit addressable
48
AT89C5131
4136B–USB–09/03
AT89C5131
Timer 2
The Timer 2 in the AT89C5131 is the standard C52 Timer 2. It is a 16-bit timer/counter:
the count is maintained by two cascaded eight-bit timer registers, TH2 and TL2. It is
controlled by T2CON (Table 47) and T2MOD (Table 48) registers. Timer 2 operation is
similar to Timer 0 and Timer 1. C/T2 selects FOSC/12 (timer operation) or external pin T2
(counter operation) as the timer clock input. Setting TR2 allows TL2 to be incremented
by the selected input.
Timer 2 has 3 operating modes: capture, auto reload and Baud Rate Generator. These
modes are selected by the combination of RCLK, TCLK and CP/RL2 (T2CON).
Refer to the Atmel 8-bit microcontroller hardware documentation for the description of
Capture and Baud Rate Generator Modes.
Timer 2 includes the following enhancements:
Auto-reload Mode
•
Auto-reload mode with up or down counter
•
Programmable Clock-output
The Auto-reload mode configures Timer 2 as a 16-bit timer or event counter with automatic reload. If DCEN bit in T2MOD is cleared, Timer 2 behaves as in 80C52 (refer to
the Atmel 8-bit microcontroller hardware description). If DCEN bit is set, Timer 2 acts as
an Up/down timer/counter as shown in Figure 23. In this mode the T2EX pin controls the
direction of count.
When T2EX is high, Timer 2 counts up. Timer overflow occurs at FFFFh which sets the
TF2 flag and generates an interrupt request. The overflow also causes the 16-bit value
in RCAP2H and RCAP2L registers to be loaded into the timer registers TH2 and TL2.
When T2EX is low, Timer 2 counts down. Timer underflow occurs when the count in the
timer registers TH2 and TL2 equals the value stored in RCAP2H and RCAP2L registers.
The underflow sets TF2 flag and reloads FFFFh into the timer registers.
The EXF2 bit toggles when Timer 2 overflows or underflows according to the direction of
the count. EXF2 does not generate any interrupt. This bit can be used to provide 17-bit
resolution.
49
4136B–USB–09/03
Figure 23. Auto-reload Mode Up/Down Counter (DCEN = 1)
FCLK PERIPH
:6
0
1
T2
C/T2
TR2
T2CON
T2CON
(DOWN COUNTING RELOAD VALUE) T2EX:
FFh
(8-bit)
FFh
(8-bit)
if DCEN = 1, 1 = UP
if DCEN = 1, 0 = DOWN
if DCEN = 0, up counting
TOGGLE T2CON
EXF2
TL2
(8-bit)
TH2
(8-bit)
TF2
Timer 2
INTERRUPT
T2CON
RCAP2L
(8-bit)
RCAP2H
(8-bit)
(UP COUNTING RELOAD VALUE)
Programmable Clock
Output
In the Clock-out mode, Timer 2 operates as a 50%-duty-cycle, programmable clock generator (See Figure 24). The input clock increments TL2 at frequency FCLK PERIPH/2. The
timer repeatedly counts to overflow from a loaded value. At overflow, the contents of
RCAP2H and RCAP2L registers are loaded into TH2 and TL2. In this mode, Timer 2
overflows do not generate interrupts. The following formula gives the Clock-out frequency as a function of the system oscillator frequency and the value in the RCAP2H
and RCAP2L registers
F CLKPERIPH
Clock – OutFrequency = ---------------------------------------------------------------------------------------4 × ( 65536 – RCAP2H ⁄ RCAP2L )
For a 16 MHz system clock, Timer 2 has a programmable frequency range of 61 Hz
(FCLK PERIPH/216) to 4 MHz (FCLK PERIPH/4). The generated clock signal is brought out to
T2 pin (P1.0).
Timer 2 is programmed for the Clock-out mode as follows:
50
•
Set T2OE bit in T2MOD register.
•
Clear C/T2 bit in T2CON register.
•
Determine the 16-bit reload value from the formula and enter it in RCAP2H/RCAP2L
registers.
•
Enter a 16-bit initial value in timer registers TH2/TL2. It can be the same as the
reload value or a different one depending on the application.
•
To start the timer, set TR2 run control bit in T2CON register.
AT89C5131
4136B–USB–09/03
AT89C5131
It is possible to use Timer 2 as a baud rate generator and a clock generator simultaneously. For this configuration, the baud rates and clock frequencies are not
independent since both functions use the values in the RCAP2H and RCAP2L registers.
Figure 24. Clock-out Mode C/T2 = 0
FCLK PERIPH
:6
TR2
T2CON
TL2
(8-bit)
TH2
(8-bit)
OVERFLOW
RCAP2L
(8-bit)
RCAP2H
(8-bit)
Toggle
T2
Q
D
T2OE
T2MOD
T2EX
EXF2
EXEN2
T2CON
Timer 2
INTERRUPT
T2CON
51
4136B–USB–09/03
Table 47. T2CON Register
T2CON - Timer 2 Control Register (C8h)
7
6
5
4
3
2
1
0
TF2
EXF2
RCLK
TCLK
EXEN2
TR2
C/T2#
CP/RL2#
Bit
Bit
Number
Mnemonic
7
TF2
Description
Timer 2 overflow Flag
Must be cleared by software.
Set by hardware on Timer 2 overflow, if RCLK = 0 and TCLK = 0.
6
EXF2
Timer 2 External Flag
Set when a capture or a reload is caused by a negative transition on T2EX pin if
EXEN2 = 1.
When set, causes the CPU to vector to Timer 2 interrupt routine when Timer 2
interrupt is enabled.
Must be cleared by software. EXF2 doesn’t cause an interrupt in Up/down
counter mode (DCEN = 1).
5
RCLK
Receive Clock bit
Cleared to use Timer 1 overflow as receive clock for serial port in mode 1 or 3.
Set to use Timer 2 overflow as receive clock for serial port in mode 1 or 3.
4
TCLK
Transmit Clock bit
Cleared to use Timer 1 overflow as transmit clock for serial port in mode 1 or 3.
Set to use Timer 2 overflow as transmit clock for serial port in mode 1 or 3.
3
EXEN2
2
TR2
1
0
Timer 2 External Enable bit
Cleared to ignore events on T2EX pin for Timer 2 operation.
Set to cause a capture or reload when a negative transition on T2EX pin is
detected, if Timer 2 is not used to clock the serial port.
Timer 2 Run control bit
Cleared to turn off Timer 2.
Set to turn on Timer 2.
C/T2#
Timer/Counter 2 select bit
Cleared for timer operation (input from internal clock system: FCLK PERIPH).
Set for counter operation (input from T2 input pin, falling edge trigger). Must be
0 for clock out mode.
CP/RL2#
Timer 2 Capture/Reload bit
If RCLK = 1 or TCLK = 1, CP/RL2# is ignored and timer is forced to Auto-reload
on Timer 2 overflow.
Cleared to Auto-reload on Timer 2 overflows or negative transitions on T2EX
pin if EXEN2 = 1.
Set to capture on negative transitions on T2EX pin if EXEN2 = 1.
Reset Value = 0000 0000b
Bit addressable
52
AT89C5131
4136B–USB–09/03
AT89C5131
Table 48. T2MOD Register
T2MOD - Timer 2 Mode Control Register (C9h)
7
6
5
4
3
2
1
0
-
-
-
-
-
-
T2OE
DCEN
Bit
Number
Bit
Mnemonic Description
7
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
6
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
5
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
3
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
2
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
1
T2OE
Timer 2 Output Enable bit
Cleared to program P1.0/T2 as clock input or I/O port.
Set to program P1.0/T2 as clock output.
0
DCEN
Down Counter Enable bit
Cleared to disable Timer 2 as up/down counter.
Set to enable Timer 2 as up/down counter.
Reset Value = XXXX XX00b
Not bit addressable
53
4136B–USB–09/03
Programmable
Counter Array (PCA)
The PCA provides more timing capabilities with less CPU intervention than the standard
timer/counters. Its advantages include reduced software overhead and improved accuracy. The PCA consists of a dedicated timer/counter which serves as the time base for
an array of five compare/capture modules. Its clock input can be programmed to count
any one of the following signals:
•
÷6
Peripheral clock frequency (FCLK PERIPH) ÷ 2
•
Timer 0 overflow
•
External input on ECI (P1.2)
•
Peripheral clock frequency (FCLK PERIPH)
Each compare/capture modules can be programmed in any one of the following modes:
•
rising and/or falling edge capture,
•
software timer
•
high-speed output, or
•
pulse width modulator
Module 4 can also be programmed as a watchdog timer (see Section "PCA Watchdog
Timer", page 64).
When the compare/capture modules are programmed in the capture mode, software
timer, or high speed output mode, an interrupt can be generated when the module executes its function. All five modules plus the PCA timer overflow share one interrupt
vector.
The PCA timer/counter and compare/capture modules share Port 1 for external I/O.
These pins are listed below. If the port pin is not used for the PCA, it can still be used for
standard I/O.
PCA Component
External I/O Pin
16-bit Counter
P1.2/ECI
16-bit Module 0
P1.3/CEX0
16-bit Module 1
P1.4/CEX1
16-bit Module 2
P1.5/CEX2
16-bit Module 3
P1.6/CEX3
16-bit Module 4
P1.7/CEX4
The PCA timer is a common time base for all five modules (see Figure 25). The timer
count source is determined from the CPS1 and CPS0 bits in the CMOD register
(Table 49) and can be programmed to run at:
54
•
1/6 the peripheral clock frequency (FCLK PERIPH).
•
1/2 the peripheral clock frequency (FCLK PERIPH).
•
The Timer 0 overflow
•
The input on the ECI pin (P1.2)
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 25. PCA Timer/Counter
To PCA
modules
FCLK PERIPH/6
overflow
FCLK PERIPH/2
CH
T0 OVF
It
CL
16 Bit Up/Down Counter
P1.2
CIDL
WDTE
CF
CR
CPS1
CPS0
ECF
CMOD
0xD9
CCF2
CCF1
CCF0
CCON
0xD8
Idle
CCF4 CCF3
Table 49. CMOD Register
CMOD - PCA Counter Mode Register (D9h)
7
6
5
4
3
2
1
0
CIDL
WDTE
-
-
-
CPS1
CPS0
ECF
Bit
Bit
Number
Mnemonic
7
CIDL
Description
Counter Idle Control
Cleared to program the PCA Counter to continue functioning during idle Mode.
Set to program PCA to be gated off during idle.
Watchdog Timer Enable
6
WDTE
Cleared to disable Watchdog Timer function on PCA Module 4.
Set to enable Watchdog Timer function on PCA Module 4.
5
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
3
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
2
CPS1
1
CPS0
0
ECF
PCA Count Pulse Select
CPS1
0
CPS0
0
Selected PCA input
Internal clock fCLK PERIPH/6
0
1
1
1
0
1
Internal clock fCLK PERIPH/2
Timer 0 Overflow
External clock at ECI/P1.2 pin (max rate = fCLK PERIPH/ 4)
PCA Enable Counter Overflow Interrupt
Cleared to disable CF bit in CCON to inhibit an interrupt.
Set to enable CF bit in CCON to generate an interrupt.
Reset Value = 00XX X000b
Not bit addressable
55
4136B–USB–09/03
The CMOD register includes three additional bits associated with the PCA (See
Figure 25 and Table 49).
•
The CIDL bit allows the PCA to stop during idle mode.
•
The WDTE bit enables or disables the watchdog function on module 4.
•
The ECF bit when set causes an interrupt and the PCA overflow flag CF (in the
CCON SFR) to be set when the PCA timer overflows.
The CCON register contains the run control bit for the PCA and the flags for the PCA
timer (CF) and each module (see Table 50).
•
Bit CR (CCON.6) must be set by software to run the PCA. The PCA is shut off by
clearing this bit.
•
Bit CF: The CF bit (CCON.7) is set when the PCA counter overflows and an
interrupt will be generated if the ECF bit in the CMOD register is set. The CF bit can
only be cleared by software.
•
Bits 0 through 4 are the flags for the modules (bit 0 for module 0, bit 1 for module 1,
etc.) and are set by hardware when either a match or a capture occurs. These flags
can only be cleared by software.
Table 50. CCON Register
CCON - PCA Counter Control Register (D8h)
7
6
5
4
3
2
1
0
CF
CR
–
CCF4
CCF3
CCF2
CCF1
CCF0
Bit
Bit
Number Mnemonic Description
PCA Counter Overflow flag
7
CF
6
CR
5
–
4
CCF4
3
CCF3
2
CCF2
1
CCF1
0
CCF0
Set by hardware when the counter rolls over. CF flags an interrupt if bit ECF in
CMOD is set. CF may be set by either hardware or software but can only be cleared
by software.
PCA Counter Run control bit
Must be cleared by software to turn the PCA counter off.
Set by software to turn the PCA counter on.
Reserved
The value read from this bit is indeterminate. Do not set this bit.
PCA Module 4 interrupt flag
Must be cleared by software.
Set by hardware when a match or capture occurs.
PCA Module 3 interrupt flag
Must be cleared by software.
Set by hardware when a match or capture occurs.
PCA Module 2 interrupt flag
Must be cleared by software.
Set by hardware when a match or capture occurs.
PCA Module 1 Interrupt Flag
Must be cleared by software.
Set by hardware when a match or capture occurs.
PCA Module 0 Interrupt Flag
Must be cleared by software.
Set by hardware when a match or capture occurs.
Reset Value = 000X 0000b
Not bit addressable
56
AT89C5131
4136B–USB–09/03
AT89C5131
The watchdog timer function is implemented in module 4 (See Figure 28).
The PCA interrupt system is shown in Figure 26.
Figure 26. PCA Interrupt System
CF
CR
CCF4 CCF3 CCF2 CCF1 CCF0
CCON
0xD8
PCA Timer/Counter
Module 0
Module 1
To Interrupt
priority decoder
Module 2
Module 3
Module 4
CMOD.0
ECF
ECCFn CCAPMn.0
IE.6
EC
IE.7
EA
PCA Modules: each one of the five compare/capture modules has six possible functions. It can perform:
•
16-bit capture, positive-edge triggered
•
16-bit capture, negative-edge triggered
•
16-bit capture, both positive and negative-edge triggered
•
16-bit Software Timer
•
16-bit High-speed Output
•
8-bit Pulse Width Modulator
In addition, module 4 can be used as a Watchdog Timer.
Each module in the PCA has a special function register associated with it. These registers are: CCAPM0 for module 0, CCAPM1 for module 1, etc. (see Table 51). The
registers contain the bits that control the mode that each module will operate in.
•
The ECCF bit (CCAPMn.0 where n = 0, 1, 2, 3, or 4 depending on the module)
enables the CCF flag in the CCON SFR to generate an interrupt when a match or
compare occurs in the associated module.
•
PWM (CCAPMn.1) enables the pulse width modulation mode.
•
The TOG bit (CCAPMn.2) when set causes the CEX output associated with the
module to toggle when there is a match between the PCA counter and the module's
capture/compare register.
•
The match bit MAT (CCAPMn.3) when set will cause the CCFn bit in the CCON
register to be set when there is a match between the PCA counter and the module's
capture/compare register.
•
The next two bits CAPN (CCAPMn.4) and CAPP (CCAPMn.5) determine the edge
that a capture input will be active on. The CAPN bit enables the negative edge, and
57
4136B–USB–09/03
the CAPP bit enables the positive edge. If both bits are set both edges will be
enabled and a capture will occur for either transition.
•
The last bit in the register ECOM (CCAPMn.6) when set enables the comparator
function.
Table 52 shows the CCAPMn settings for the various PCA functions.
Table 51. CCAPMn Registers (n = 0-4)
CCAPM0 - PCA Module 0 Compare/Capture Control Register (0DAh)
CCAPM1 - PCA Module 1 Compare/Capture Control Register (0DBh)
CCAPM2 - PCA Module 2 Compare/Capture Control Register (0DCh)
CCAPM3 - PCA Module 3 Compare/Capture Control Register (0DDh)
CCAPM4 - PCA Module 4 Compare/Capture Control Register (0DEh)
7
6
5
4
3
2
1
0
-
ECOMn
CAPPn
CAPNn
MATn
TOGn
PWMn
ECCFn
Bit
Bit
Number
Mnemonic
7
-
6
ECOMn
Description
Reserved
The value read from this bit is indeterminate. Do not set this bit.
Enable Comparator
Cleared to disable the comparator function.
Set to enable the comparator function.
Capture Positive
5
CAPPn
4
CAPNn
Cleared to disable positive edge capture.
Set to enable positive edge capture.
Capture Negative
Cleared to disable negative edge capture.
Set to enable negative edge capture.
Match
3
MATn
When MATn = 1, a match of the PCA counter with this module’s
compare/capture register causes the
CCFn bit in CCON to be set, flagging an interrupt.
Toggle
2
TOGn
1
PWMn
When TOGn = 1, a match of the PCA counter with this module’s
compare/capture register causes the CEXn pin to toggle.
Pulse Width Modulation Mode
Cleared to disable the CEXn pin to be used as a pulse width modulated output.
Set to enable the CEXn pin to be used as a pulse width modulated output.
Enable CCF Interrupt
0
CCF0
Cleared to disable compare/capture flag CCFn in the CCON register to
generate an interrupt.
Set to enable compare/capture flag CCFn in the CCON register to generate an
interrupt.
Reset Value = X000 0000b
Not bit addressable
58
AT89C5131
4136B–USB–09/03
AT89C5131
Table 52. PCA Module Modes (CCAPMn Registers)
ECOMn
CAPPn
CAPNn
MATn
TOGn
PWM
m
ECCF
n
Module Function
0
0
0
0
0
0
0
No Operation
X
1
0
0
0
0
X
16-bit capture by a positiveedge trigger on CEXn
X
0
1
0
0
0
X
16-bit capture by a negative
trigger on CEXn
X
1
1
0
0
0
X
16-bit capture by a transition on
CEXn
1
0
0
1
0
0
X
16-bit Software Timer/Compare
mode.
1
0
0
1
1
0
X
16-bit High Speed Output
1
0
0
0
0
1
0
8-bit PWM
1
0
0
1
X
0
X
Watchdog Timer (module 4
only)
There are two additional registers associated with each of the PCA modules. They are
CCAPnH and CCAPnL and these are the registers that store the 16-bit count when a
capture occurs or a compare should occur. When a module is used in the PWM mode
these registers are used to control the duty cycle of the output (see Table 53 and
Table 54)
59
4136B–USB–09/03
Table 53. CCAPnH Registers (n = 0-4)
CCAP0H - PCA Module 0 Compare/Capture Control Register High (0FAh)
CCAP1H - PCA Module 1 Compare/Capture Control Register High (0FBh)
CCAP2H - PCA Module 2 Compare/Capture Control Register High (0FCh)
CCAP3H - PCA Module 3 Compare/Capture Control Register High (0FDh)
CCAP4H - PCA Module 4 Compare/Capture Control Register High (0FEh)
7
6
5
4
3
2
1
0
-
-
-
-
-
-
-
-
Bit
Bit
Number
Mnemonic
7-0
-
Description
PCA Module n Compare/Capture Control
CCAPnH Value
Reset Value = 0000 0000b
Not bit addressable
Table 54. CCAPnL Registers (n = 0-4)
CCAP0L - PCA Module 0 Compare/Capture Control Register Low (0EAh)
CCAP1L - PCA Module 1 Compare/Capture Control Register Low (0EBh)
CCAP2L - PCA Module 2 Compare/Capture Control Register Low (0ECh)
CCAP3L - PCA Module 3 Compare/Capture Control Register Low (0EDh)
CCAP4L - PCA Module 4 Compare/Capture Control Register Low (0EEh)
7
6
5
4
3
2
1
0
-
-
-
-
-
-
-
-
Bit
Bit
Number
Mnemonic
7-0
-
Description
PCA Module n Compare/Capture Control
CCAPnL Value
Reset Value = 0000 0000b
Not bit addressable
Table 55. CH Register
CH - PCA Counter Register High (0F9h)
7
6
5
4
3
2
1
0
-
-
-
-
-
-
-
-
Bit
Bit
Number
Mnemonic
Description
7-0
-
PCA counter
CH Value
Reset Value = 0000 0000b
Not bit addressable
60
AT89C5131
4136B–USB–09/03
AT89C5131
Table 56. CL Register
CL - PCA Counter Register Low (0E9h)
7
6
5
4
3
2
1
0
-
-
-
-
-
-
-
-
Bit
Bit
Number
Mnemonic
7-0
-
Description
PCA Counter
CL Value
Reset Value = 0000 0000b
Not bit addressable
PCA Capture Mode
To use one of the PCA modules in the capture mode either one or both of the CCAPM
bits CAPN and CAPP for that module must be set. The external CEX input for the module (on port 1) is sampled for a transition. When a valid transition occurs the PCA
hardware loads the value of the PCA counter registers (CH and CL) into the module’s
capture registers (CCAPnL and CCAPnH). If the CCFn bit for the module in the CCON
SFR and the ECCFn bit in the CCAPMn SFR are set then an interrupt will be generated
(see Figure 27).
Figure 27. PCA Capture Mode
CF
CR
CCF4 CCF3 CCF2 CCF1 CCF0 CCON
0xD8
PCA IT
PCA Counter/Timer
Cex.n
CH
CL
CCAPnH
CCAPnL
Capture
ECOMn CAPPn CAPNn MATn TOGn PWMn ECCFn CCAPMn, n = 0 to 4
0xDA to 0xDE
16-bit Software
Timer/Compare Mode
The PCA modules can be used as software timers by setting both the ECOM and MAT
bits in the modules CCAPMn register. The PCA timer will be compared to the module’s
capture registers and when a match occurs an interrupt will occur if the CCFn (CCON
SFR) and the ECCFn (CCAPMn SFR) bits for the module are both set (see Figure 28).
61
4136B–USB–09/03
Figure 28. PCA Compare Mode and PCA Watchdog Timer
CCON
CF
Write to
CCAPnL
CR
CCF4 CCF3 CCF2 CCF1 CCF0
0xD8
Reset
PCA IT
Write to
CCAPnH
1
CCAPnH
0
CCAPnL
Enable
Match
16-bit Comparator
CH
RESET(1)
CL
PCA Counter/Timer
ECOMn CAPPn CAPNn MATn TOGn PWMn ECCFn
CIDL
Note:
WDTE
CPS1 CPS0
ECF
CCAPMn, n = 0 to 4
0xDA to 0xDE
CMOD
0xD9
1. Only for Module 4
Before enabling ECOM bit, CCAPnL and CCAPnH should be set with a non zero value,
otherwise an unwanted match could happen. Writing to CCAPnH will set the ECOM bit.
Once ECOM set, writing CCAPnL will clear ECOM so that an unwanted match doesn’t
occur while modifying the compare value. Writing to CCAPnH will set ECOM. For this
reason, user software should write CCAPnL first, and then CCAPnH. Of course, the
ECOM bit can still be controlled by accessing to CCAPMn register.
High Speed Output Mode In this mode, the CEX output (on port 1) associated with the PCA module will toggle
each time a match occurs between the PCA counter and the module's capture registers.
To activate this mode the TOG, MAT, and ECOM bits in the module's CCAPMn SFR
must be set (see Figure 29).
A prior write must be done to CCAPnL and CCAPnH before writing the ECOMn bit.
62
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 29. PCA High-speed Output Mode
CCON
CF
CR
CCF4 CCF3 CCF2 CCF1 CCF0
0xD8
Write to
CCAPnL Reset
PCA IT
Write to
CCAPnH
1
CCAPnH
0
CCAPnL
Enable
16-bit Comparator
CH
Match
CL
CEXn
PCA counter/timer
ECOMn CAPPn CAPNn MATn TOGn PWMn ECCFn
CCAPMn, n = 0 to 4
0xDA to 0xDE
Before enabling ECOM bit, CCAPnL and CCAPnH should be set with a non zero value,
otherwise an unwanted match could happen.
Once ECOM set, writing CCAPnL will clear ECOM so that an unwanted match doesn’t
occur while modifying the compare value. Writing to CCAPnH will set ECOM. For this
reason, user software should write CCAPnL first, and then CCAPnH. Of course, the
ECOM bit can still be controlled by accessing to CCAPMn register.
Pulse Width Modulator
Mode
All of the PCA modules can be used as PWM outputs. Figure 30 shows the PWM function. The frequency of the output depends on the source for the PCA timer. All of the
modules will have the same frequency of output because they all share the PCA timer.
The duty cycle of each module is independently variable using the module's capture
register CCAPLn. When the value of the PCA CL SFR is less than the value in the module's CCAPLn SFR the output will be low, when it is equal to or greater than the output
will be high. When CL overflows from FF to 00, CCAPLn is reloaded with the value in
CCAPHn. This allows updating the PWM without glitches. The PWM and ECOM bits in
the module's CCAPMn register must be set to enable the PWM mode.
63
4136B–USB–09/03
Figure 30. PCA PWM Mode
CCAPnH
Overflow
CCAPnL
“0”
Enable
8-bit Comparator
<
≥
CEXn
“1”
CL
PCA Counter/Timer
ECOMn CAPPn CAPNn MATn TOGn PWMn ECCFn
CCAPMn, n = 0 to 4
0xDA to 0xDE
PCA Watchdog Timer
An on-board watchdog timer is available with the PCA to improve the reliability of the
system without increasing chip count. Watchdog timers are useful for systems that are
susceptible to noise, power glitches, or electrostatic discharge. Module 4 is the only
PCA module that can be programmed as a watchdog. However, this module can still be
used for other modes if the watchdog is not needed. Figure 28 shows a diagram of how
the watchdog works. The user pre-loads a 16-bit value in the compare registers. Just
like the other compare modes, this 16-bit value is compared to the PCA timer value. If a
match is allowed to occur, an internal reset will be generated. This will not cause the
RST pin to be driven low.
In order to hold off the reset, the user has three options:
1. Periodically change the compare value so it will never match the PCA timer
2. Periodically change the PCA timer value so it will never match the compare values, or
3. Disable the watchdog by clearing the WDTE bit before a match occurs and then
re-enable it
The first two options are more reliable because the watchdog timer is never disabled as
in option #3. If the program counter ever goes astray, a match will eventually occur and
cause an internal reset. The second option is also not recommended if other PCA modules are being used. Remember, the PCA timer is the time base for all modules;
changing the time base for other modules would not be a good idea. Thus, in most applications the first solution is the best option.
This watchdog timer won’t generate a reset out on the reset pin.
64
AT89C5131
4136B–USB–09/03
AT89C5131
Serial I/O Port
The serial I/O port in the AT89C5131 is compatible with the serial I/O port in the 80C52.
It provides both synchronous and asynchronous communication modes. It operates as
an Universal Asynchronous Receiver and Transmitter (UART) in three full-duplex
modes (modes 1, 2 and 3). Asynchronous transmission and reception can occur simultaneously and at different baud rates.
Serial I/O port includes the following enhancements:
Framing Error Detection
•
Framing error detection
•
Automatic address recognition
Framing bit error detection is provided for the three asynchronous modes (modes 1, 2
and 3). To enable the framing bit error detection feature, set SMOD0 bit in PCON register (see Figure 31).
Figure 31. Framing Error Block Diagram
SM0/FE
SM1
SM2
REN
TB8
RB8
TI
RI
SCON (98h)
Set FE Bit if Stop Bit is 0 (framing error) (SMOD0 = 1
SM0 to UART Mode Control (SMOD0 = 0)
SMOD1 SMOD0
-
POF
GF1
GF0
PD
PCON (87h)
IDL
To UART Framing Error Control
When this feature is enabled, the receiver checks each incoming data frame for a valid
stop bit. An invalid stop bit may result from noise on the serial lines or from simultaneous
transmission by two CPUs. If a valid stop bit is not found, the Framing Error bit (FE) in
SCON register (See Table 57) bit is set.
Software may examine FE bit after each reception to check for data errors. Once set,
only software or a reset can clear FE bit. Subsequently received frames with valid stop
bits cannot clear FE bit. When FE feature is enabled, RI rises on stop bit instead of the
last data bit (See Figure 32 and Figure 33).
Figure 32. UART Timings in Mode 1
RXD
D0
Start
Bit
D1
D2
D3
D4
Data Byte
D5
D6
D7
Stop
Bit
RI
SMOD0 = X
FE
SMOD0 = 1
65
4136B–USB–09/03
Figure 33. UART Timings in Modes 2 and 3
RXD
D0
Start
Bit
D1
D2
D3
D4
Data Byte
D5
D6
D7
D8
Ninth Stop
Bit
Bit
RI
SMOD0 = 0
RI
SMOD0 = 1
FE
SMOD0 = 1
Automatic Address
Recognition
The automatic address recognition feature is enabled when the multiprocessor communication feature is enabled (SM2 bit in SCON register is set).
Implemented in hardware, automatic address recognition enhances the multiprocessor
communication feature by allowing the serial port to examine the address of each
incoming command frame. Only when the serial port recognizes its own address, the
receiver sets RI bit in SCON register to generate an interrupt. This ensures that the CPU
is not interrupted by command frames addressed to other devices.
If desired, you may enable the automatic address recognition feature in mode 1. In this
configuration, the stop bit takes the place of the ninth data bit. Bit RI is set only when the
received command frame address matches the device’s address and is terminated by a
valid stop bit.
To support automatic address recognition, a device is identified by a given address and
a broadcast address.
Note:
Given Address
The multiprocessor communication and automatic address recognition features cannot
be enabled in mode 0 (i.e., setting SM2 bit in SCON register in mode 0 has no effect).
Each device has an individual address that is specified in SADDR register; the SADEN
register is a mask byte that contains don’t care bits (defined by zeros) to form the
device’s given address. The don’t care bits provide the flexibility to address one or more
slaves at a time. The following example illustrates how a given address is formed.
To address a device by its individual address, the SADEN mask byte must be 1111
1111b.
For example:
SADDR0101 0110b
SADEN1111 1100b
Given0101 01XXb
The following is an example of how to use given addresses to address different slaves:
Slave A:SADDR1111 0001b
SADEN1111 1010b
Given1111 0X0Xb
Slave B:SADDR1111 0011b
SADEN1111 1001b
Given1111 0XX1b
Slave C:SADDR1111 0011b
SADEN1111 1101b
Given1111 00X1b
66
AT89C5131
4136B–USB–09/03
AT89C5131
The SADEN byte is selected so that each slave may be addressed separately.
For slave A, bit 0 (the LSB) is a don’t care bit; for slaves B and C, bit 0 is a 1. To communicate with slave A only, the master must send an address where bit 0 is clear (e.g.
1111 0000b).
For slave A, bit 1 is a 1; for slaves B and C, bit 1 is a don’t care bit. To communicate with
slaves B and C, but not slave A, the master must send an address with bits 0 and 1 both
set (e.g. 1111 0011b).
To communicate with slaves A, B and C, the master must send an address with bit 0 set,
bit 1 clear, and bit 2 clear (e.g. 1111 0001b).
Broadcast Address
A broadcast address is formed from the logical OR of the SADDR and SADEN registers
with zeros defined as don’t care bits, e.g.:
SADDR0101 0110b
SADEN1111 1100b
Broadcast = SADDR OR SADEN1111 111Xb
The use of don’t care bits provides flexibility in defining the broadcast address, in most
applications, a broadcast address is FFh. The following is an example of using broadcast addresses:
Slave A:SADDR1111 0001b
SADEN1111 1010b
Broadcast1111 1X11b,
Slave B:SADDR1111 0011b
SADEN1111 1001b
Broadcast1111 1X11B,
Slave C:SADDR = 1111 0010b
SADEN1111 1101b
Broadcast1111 1111b
For slaves A and B, bit 2 is a don’t care bit; for slave C, bit 2 is set. To communicate with
all of the slaves, the master must send an address FFh. To communicate with slaves A
and B, but not slave C, the master can send and address FBh.
Reset Addresses
On reset, the SADDR and SADEN registers are initialized to 00h, i.e. the given and
broadcast addresses are XXXX XXXXb (all don’t care bits). This ensures that the serial
port will reply to any address, and so, that it is backwards compatible with the 80C51
microcontrollers that do not support automatic address recognition.
SADEN - Slave Address Mask Register (B9h)
7
6
5
4
3
2
1
0
Reset Value = 0000 0000b
Not bit addressable
67
4136B–USB–09/03
SADDR - Slave Address Register (A9h)
7
6
5
4
3
2
1
0
Reset Value = 0000 0000b
Not bit addressable
Baud Rate Selection for
UART for Mode 1 and 3
The Baud Rate Generator for transmit and receive clocks can be selected separately via
the T2CON and BDRCON registers.
Figure 34. Baud Rate Selection
TIMER1
0
TIMER2
TIMER_BRG_RX
0
1
/ 16
Rx Clock
1
RCLK
RBCK
INT_BRG
TIMER1
0
TIMER2
TIMER_BRG_TX
0
1
/ 16
1
Tx Clock
TCLK
TBCK
INT_BRG
Baud Rate Selection Table for
UART
Internal Baud Rate Generator
(BRG)
68
TCLK
RCLK
TBCK
RBCK
Clock Source
Clock Source
(T2CON)
(T2CON)
(BDRCON)
(BDRCON)
UART Tx
UART Rx
0
0
0
0
Timer 1
Timer 1
1
0
0
0
Timer 2
Timer 1
0
1
0
0
Timer 1
Timer 2
1
1
0
0
Timer 2
Timer 2
X
0
1
0
INT_BRG
Timer 1
X
1
1
0
INT_BRG
Timer 2
0
X
0
1
Timer 1
INT_BRG
1
X
0
1
Timer 2
INT_BRG
X
X
1
1
INT_BRG
INT_BRG
When the internal Baud Rate Generator is used, the Baud Rates are determined by the
BRG overflow depending on the BRL reload value, the value of SPD bit (Speed Mode)
in BDRCON register and the value of the SMOD1 bit in PCON register.
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 35. Internal Baud Rate
CLK PERIPH
/6
0
auto reload counter
overflow
BRG
/2
0
1
SPD
INT_BRG
1
BRL
SMOD1
BRR
•
The baud rate for UART is token by formula:
Baud_Rate =
2SMOD1 x FCLK PERIPH
(1-SPD)
2x2x6
(BRL) = 256 -
x 16 x [256 - (BRL)]
2SMOD1 x FCLK PERIPH
2x2x6
(1-SPD)
x 16 x Baud_Rate
69
4136B–USB–09/03
Table 57. SCON Register – SCON Serial Control Register (98h)
7
6
5
4
3
2
1
0
FE/SM0
SM1
SM2
REN
TB8
RB8
TI
RI
Bit
Bit
Number
Mnemonic
FE
Description
Framing Error bit (SMOD0 = 1)
Clear to reset the error state, not cleared by a valid stop bit.
Set by hardware when an invalid stop bit is detected.
SMOD0 must be set to enable access to the FE bit
7
SM0
Serial port Mode bit 0
Refer to SM1 for serial port mode selection.
SMOD0 must be cleared to enable access to the SM0 bit
6
SM1
Serial port Mode bit 1
Description
SM0 SM1 Mode
0
0
0
Shift Register
0
1
1
8-bit UART
1
0
2
9-bit UART
Baud Rate
FCPU PERIPH/6
Variable
FCPU PERIPH/32 or/16
1
Variable
1
3
9-bit UART
5
SM2
Serial port Mode 2 bit/Multiprocessor Communication Enable bit
Clear to disable multiprocessor communication feature.
Set to enable multiprocessor communication feature in mode 2 and 3, and
eventually mode 1. This bit should be cleared in mode 0.
4
REN
Reception Enable bit
Clear to disable serial reception.
Set to enable serial reception.
3
TB8
Transmitter Bit 8/Ninth bit to Transmit in Modes 2 and 3
2
RB8
Clear to transmit a logic 0 in the 9th bit.
Set to transmit a logic 1 in the 9th bit.
Receiver Bit 8/Ninth bit received in modes 2 and 3
Cleared by hardware if 9th bit received is a logic 0.
Set by hardware if 9th bit received is a logic 1.
In mode 1, if SM2 = 0, RB8 is the received stop bit. In mode 0 RB8 is not used.
1
0
TI
Transmit Interrupt flag
Clear to acknowledge interrupt.
Set by hardware at the end of the 8th bit time in mode 0 or at the beginning of the
stop bit in the other modes.
RI
Receive Interrupt flag
Clear to acknowledge interrupt.
Set by hardware at the end of the 8th bit time in mode 0, see Figure 32. and
Figure 33. in the other modes.
Reset Value = 0000 0000b
Bit addressable
70
AT89C5131
4136B–USB–09/03
AT89C5131
Example of computed value when X2 = 1, SMOD1 = 1, SPD = 1
FOSCA = 16.384 MHz
Baud Rates
FOSCA = 24 MHz
BRL
Error (%)
BRL
Error (%)
115200
247
1.23
243
0.16
57600
238
1.23
230
0.16
38400
229
1.23
217
0.16
28800
220
1.23
204
0.16
19200
203
0.63
178
0.16
9600
149
0.31
100
0.16
4800
43
1.23
-
-
Example of computed value when X2 = 0, SMOD1 = 0, SPD = 0
FOSCA = 16.384 MHz
FOSCA = 24 MHz
Baud Rates
BRL
Error (%)
BRL
Error (%)
4800
247
1.23
243
0.16
2400
238
1.23
230
0.16
1200
220
1.23
202
3.55
600
185
0.16
152
0.16
The baud rate generator can be used for mode 1 or 3 (refer to Figure 34.), but also for
mode 0 for UART, thanks to the bit SRC located in BDRCON register (Table 60.)
UART Registers
SADEN - Slave Address Mask Register for UART (B9h)
7
6
5
4
3
2
1
0
–
–
–
–
–
–
–
–
Reset Value = 0000 0000b
SADDR - Slave Address Register for UART (A9h)
7
6
5
4
3
2
1
0
–
–
–
–
–
–
–
–
Reset Value = 0000 0000b
SBUF - Serial Buffer Register for UART (99h)
7
6
5
4
3
2
1
0
–
–
–
–
–
–
–
–
Reset Value = XXXX XXXXb
71
4136B–USB–09/03
BRL - Baud Rate Reload Register for the internal baud rate generator, UART (9Ah)
7
6
5
4
3
2
1
0
–
–
–
–
–
–
–
–
Reset Value = 0000 0000b
Table 58. T2CON Register
T2CON - Timer 2 Control Register (C8h)
7
6
5
4
3
2
1
0
TF2
EXF2
RCLK
TCLK
EXEN2
TR2
C/T2#
CP/RL2#
Bit
Bit
Number
Mnemonic
7
TF2
Description
Timer 2 overflow Flag
Must be cleared by software.
Set by hardware on Timer 2 overflow, if RCLK = 0 and TCLK = 0.
6
EXF2
Timer 2 External Flag
Set when a capture or a reload is caused by a negative transition on T2EX pin if
EXEN2 = 1.
When set, causes the CPU to vector to Timer 2 interrupt routine when Timer 2
interrupt is enabled.
Must be cleared by software. EXF2 doesn’t cause an interrupt in Up/down
counter mode (DCEN = 1)
5
RCLK
Receive Clock bit for UART
Cleared to use Timer 1 overflow as receive clock for serial port in mode 1 or 3.
Set to use Timer 2 overflow as receive clock for serial port in mode 1 or 3.
4
TCLK
Transmit Clock bit for UART
Cleared to use Timer 1 overflow as transmit clock for serial port in mode 1 or 3.
Set to use Timer 2 overflow as transmit clock for serial port in mode 1 or 3.
3
EXEN2
2
TR2
1
0
Timer 2 External Enable bit
Cleared to ignore events on T2EX pin for Timer 2 operation.
Set to cause a capture or reload when a negative transition on T2EX pin is
detected, if Timer 2 is not used to clock the serial port.
Timer 2 Run control bit
Cleared to turn off Timer 2.
Set to turn on Timer 2.
C/T2#
Timer/Counter 2 select bit
Cleared for timer operation (input from internal clock system: FCLK PERIPH).
Set for counter operation (input from T2 input pin, falling edge trigger). Must be 0
for clock out mode.
CP/RL2#
Timer 2 Capture/Reload bit
If RCLK = 1 or TCLK = 1, CP/RL2# is ignored and timer is forced to Auto-reload
on Timer 2 overflow.
Cleared to Auto-reload on Timer 2 overflows or negative transitions on T2EX pin
if EXEN2 = 1.
Set to capture on negative transitions on T2EX pin if EXEN2 = 1.
Reset Value = 0000 0000b
Bit addressable
72
AT89C5131
4136B–USB–09/03
AT89C5131
Table 59. PCON Register
PCON - Power Control Register (87h)
7
6
5
4
3
2
1
0
SMOD1
SMOD0
-
POF
GF1
GF0
PD
IDL
Bit
Bit
Number
Mnemonic
7
SMOD1
6
SMOD0
5
-
Description
Serial port Mode bit 1 for UART
Set to select double baud rate in mode 1, 2 or 3.
Serial port Mode bit 0 for UART
Cleared to select SM0 bit in SCON register.
Set to select FE bit in SCON register.
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
POF
Power-Off Flag
Cleared to recognize next reset type.
Set by hardware when VCC rises from 0 to its nominal voltage. Can also be set by
software.
3
GF1
General-purpose Flag
Cleared by user for general-purpose usage.
Set by user for general-purpose usage.
2
GF0
General-purpose Flag
Cleared by user for general-purpose usage.
Set by user for general-purpose usage.
1
PD
Power-down Mode Bit
Cleared by hardware when reset occurs.
Set to enter power-down mode.
0
IDL
Idle Mode Bit
Cleared by hardware when interrupt or reset occurs.
Set to enter idle mode.
Reset Value = 00X1 0000b
Not bit addressable
Power-off flag reset value will be 1 only after a power on (cold reset). A warm reset
doesn’t affect the value of this bit.
73
4136B–USB–09/03
Table 60. BDRCON Register
BDRCON - Baud Rate Control Register (9Bh)
7
6
5
4
3
2
1
0
-
-
-
BRR
TBCK
RBCK
SPD
SRC
Bit
Number
Bit
Mnemonic
7
-
Reserved
The value read from this bit is indeterminate. Do not set this bit
6
-
Reserved
The value read from this bit is indeterminate. Do not set this bit
5
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
BRR
Baud Rate Run Control bit
Cleared to stop the internal Baud Rate Generator.
Set to start the internal Baud Rate Generator.
3
TBCK
Transmission Baud rate Generator Selection bit for UART
Cleared to select Timer 1 or Timer 2 for the Baud Rate Generator.
Set to select internal Baud Rate Generator.
2
RBCK
Reception Baud Rate Generator Selection bit for UART
Cleared to select Timer 1 or Timer 2 for the Baud Rate Generator.
Set to select internal Baud Rate Generator.
1
SPD
Description
Baud Rate Speed Control bit for UART
Cleared to select the SLOW Baud Rate Generator.
Set to select the FAST Baud Rate Generator.
Baud Rate Source select bit in Mode 0 for UART
0
SRC
Cleared to select FOSC/12 as the Baud Rate Generator (FCLK PERIPH/6 in X2
mode).
Set to select the internal Baud Rate Generator for UARTs in mode 0.
Reset Value = XXX0 0000b
Not bit addressable
74
AT89C5131
4136B–USB–09/03
AT89C5131
Interrupt System
Overview
The AT89C5131 has a total of 15 interrupt vectors: two external interrupts (INT0 and
INT1), three timer interrupts (timers 0, 1 and 2), the serial port interrupt, SPI interrupt,
Keyboard interrupt, USB interrupt and the PCA global interrupt. These interrupts are
shown in Figure 36.
Figure 36. Interrupt Control System
High priority
interrupt
IPH, IPL
3
INT0
IE0
0
3
TF0
0
3
INT1
IE1
0
3
Interrupt
Polling
Sequence, Decreasing From
High-to-Low Priority
TF1
0
3
PCA IT
0
RI
TI
3
TF2
EXF2
3
0
0
3
KBD IT
0
3
0
3
SPI IT
0
3
USBINT
UEPINT
0
Individual Enable
Global Disable
Low Priority
Interrupt
75
4136B–USB–09/03
Each of the interrupt sources can be individually enabled or disabled by setting or clearing a bit in the Interrupt Enable register (Table 62). This register also contains a global
disable bit, which must be cleared to disable all interrupts at once.
Each interrupt source can also be individually programmed to one out of four priority levels by setting or clearing a bit in the Interrupt Priority register (Table 63.) and in the
Interrupt Priority High register (Table 64). Table 61. shows the bit values and priority levels associated with each combination.
Registers
The PCA interrupt vector is located at address 0033H, the SPI interrupt vector is located
at address 0043H and Keyboard interrupt vector is located at address 004BH. All other
vectors addresses are the same as standard C52 devices.
Table 61. Priority Level Bit Values
IPH.x
IPL.x
Interrupt Level Priority
0
0
0 (Lowest)
0
1
1
1
0
2
1
1
3 (Highest)
A low-priority interrupt can be interrupted by a high priority interrupt, but not by another
low-priority interrupt. A high-priority interrupt can’t be interrupted by any other interrupt
source.
If two interrupt requests of different priority levels are received simultaneously, the
request of higher priority level is serviced. If interrupt requests of the same priority level
are received simultaneously, an internal polling sequence determines which request is
serviced. Thus within each priority level there is a second priority structure determined
by the polling sequence.
76
AT89C5131
4136B–USB–09/03
AT89C5131
Table 62. IEN0 Register
IEN0 - Interrupt Enable Register (A8h)
7
6
5
4
3
2
1
0
EA
EC
ET2
ES
ET1
EX1
ET0
EX0
Bit
Bit
Number
Mnemonic
7
EA
6
EC
Description
Enable All interrupt bit
Cleared to disable all interrupts.
Set to enable all interrupts.
PCA interrupt enable bit
Cleared to disable.
Set to enable.
5
ET2
Timer 2 overflow interrupt Enable bit
Cleared to disable Timer 2 overflow interrupt.
Set to enable Timer 2 overflow interrupt.
4
ES
Serial port Enable bit
Cleared to disable serial port interrupt.
Set to enable serial port interrupt.
3
ET1
Timer 1 overflow interrupt Enable bit
Cleared to disable Timer 1 overflow interrupt.
Set to enable Timer 1 overflow interrupt.
2
EX1
External interrupt 1 Enable bit
Cleared to disable external interrupt 1.
Set to enable external interrupt 1.
1
ET0
Timer 0 overflow interrupt Enable bit
Cleared to disable timer 0 overflow interrupt.
Set to enable timer 0 overflow interrupt.
0
EX0
External interrupt 0 Enable bit
Cleared to disable external interrupt 0.
Set to enable external interrupt 0.
Reset Value = 0000 0000b
Bit addressable
77
4136B–USB–09/03
Table 63. IPL0 Register
IPL0 - Interrupt Priority Register (B8h)
7
6
5
4
3
2
1
0
-
PPCL
PT2L
PSL
PT1L
PX1L
PT0L
PX0L
Bit
Bit
Number
Mnemonic
7
-
6
PPCL
PCA interrupt Priority bit
Refer to PPCH for priority level.
5
PT2L
Timer 2 overflow interrupt Priority bit
Refer to PT2H for priority level.
4
PSL
Serial port Priority bit
Refer to PSH for priority level.
3
PT1L
Timer 1 overflow interrupt Priority bit
Refer to PT1H for priority level.
2
PX1L
External interrupt 1 Priority bit
Refer to PX1H for priority level.
1
PT0L
Timer 0 overflow interrupt Priority bit
Refer to PT0H for priority level.
0
PX0L
External interrupt 0 Priority bit
Refer to PX0H for priority level.
Description
Reserved
The value read from this bit is indeterminate. Do not set this bit.
Reset Value = X000 0000b
Bit addressable
78
AT89C5131
4136B–USB–09/03
AT89C5131
Table 64. IPH0 Register
IPH0 - Interrupt Priority High Register (B7h)
7
6
5
4
3
2
1
0
-
PPCH
PT2H
PSH
PT1H
PX1H
PT0H
PX0H
Bit
Bit
Number
Mnemonic
7
-
6
5
4
3
2
1
0
Description
Reserved
The value read from this bit is indeterminate. Do not set this bit.
PPCH
PCA interrupt Priority high bit.
PPCH PPCL Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
PT2H
Timer 2 overflow interrupt Priority High bit
PT2H PT2L Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
PSH
Serial port Priority High bit
PSL
Priority Level
PSH
0
0
Lowest
0
1
1
0
1
1
Highest
PT1H
Timer 1 overflow interrupt Priority High bit
PT1H PT1L Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
PX1H
External interrupt 1 Priority High bit
PX1H PX1L Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
PT0H
Timer 0 overflow interrupt Priority High bit
PT0H PT0L Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
PX0H
External interrupt 0 Priority High bit
PX0H PX0L Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
Reset Value = X000 0000b
Not bit addressable
79
4136B–USB–09/03
Table 65. IEN1 Register
IEN1 - Interrupt Enable Register (B1h)
7
6
5
4
3
2
1
0
-
EUSB
-
-
-
ESPI
-
EKB
Bit
Bit
Number
Mnemonic
7
-
6
EUSB
5
-
Reserved
4
-
Reserved
3
-
Reserved
2
ESPI
1
-
0
EKB
Description
Reserved
USB Interrupt Enable bit
SPI interrupt Enable bit
Cleared to disable SPI interrupt.
Set to enable SPI interrupt.
Reserved
Keyboard interrupt Enable bit
Cleared to disable keyboard interrupt.
Set to enable keyboard interrupt.
Reset Value = XXXX X000b
Bit addressable
80
AT89C5131
4136B–USB–09/03
AT89C5131
Table 66. IPL1 Register
IPL1 - Interrupt Priority Register (B2h)
7
6
5
4
3
2
-
PUSBL
-
-
-
PSPIL
1
Bit
Bit
Number
Mnemonic
7
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
6
PUSBL
USB Interrupt Priority bit
The value read from this bit is indeterminate. Do not set this bit.
5
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
3
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
2
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
1
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
0
PKBL
0
PKBDL
Description
Keyboard Interrupt Priority bit
Refer to KBDH for priority level.
Reset Value = XXXX X000b
Bit addressable
81
4136B–USB–09/03
Table 67. IPH1 Register
IPH1 - Interrupt Priority High Register (B3h)
7
6
5
4
3
2
1
0
-
-
-
-
-
PSPIH
-
PKBH
Bit
Bit
Number
Mnemonic
7
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
6
PUSBH
USB Interrupt Priority High bit
The value read from this bit is indeterminate. Do not set this bit.
5
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
4
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
3
-
Reserved
The value read from this bit is indeterminate. Do not set this bit.
2
PSPIH
1
-
0
PKBH
Description
SPI Interrupt Priority High bit
SPIH SPIL
Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
Reserved
The value read from this bit is indeterminate. Do not set this bit.
Keyboard Interrupt Priority High bit
KBDH KBDL Priority Level
0
0
Lowest
0
1
1
0
1
1
Highest
Reset Value = XXXX X000b
Not bit addressable
82
AT89C5131
4136B–USB–09/03
AT89C5131
Interrupt Sources and
Vector Addresses
Table 68. Vector Table
Interrupt
Request
Vector
Number
Polling
Priority
Interrupt
Source
0
0
Reset
1
1
INT0
IE0
0003h
2
2
Timer 0
TF0
000Bh
3
3
INT1
IE1
0013h
4
4
Timer 1
IF1
001Bh
5
6
UART
RI+TI
0023h
6
7
Timer 2
TF2+EXF2
002Bh
7
5
PCA
CF + CCFn (n = 0-4)
0033h
8
8
Keyboard
KBDIT
003Bh
9
9
10
10
11
11
0053h
12
12
005Bh
13
13
0063h
14
14
15
15
Address
0000h
0043h
SPI
USB
SPIIT
UEPINT + USBINT
004Bh
006Bh
0073
83
4136B–USB–09/03
Keyboard Interface
Introduction
The AT89C5131 implements a keyboard interface allowing the connection of a 8 x n
matrix keyboard. It is based on 8 inputs with programmable interrupt capability on both
high or low level. These inputs are available as an alternate function of P1 and allow to
exit from idle and power down modes.
Description
The keyboard interface communicates with the C51 core through 3 special function registers: KBLS, the Keyboard Level Selection register (Table 71), KBE, The Keyboard
interrupt Enable register (Table 70), and KBF, the Keyboard Flag register (Table 69).
Interrupt
The keyboard inputs are considered as 8 independent interrupt sources sharing the
same interrupt vector. An interrupt enable bit (KBD in IE1) allows global enable or disable of the keyboard interrupt (see Figure 37). As detailed in Figure 38 each keyboard
input has the capability to detect a programmable level according to KBLS.x bit value.
Level detection is then reported in interrupt flags KBF.x that can be masked by software
using KBE.x bits.
This structure allow keyboard arrangement from 1 by n to 8 by n matrix and allow usage
of P1 inputs for other purpose.
Figure 37. Keyboard Interface Block Diagram
P1.0
Input Circuitry
P1.1
Input Circuitry
P1.2
Input Circuitry
P1.3
Input Circuitry
P1.4
Input Circuitry
P1.5
Input Circuitry
P1.6
Input Circuitry
P1.7
Input Circuitry
KBDIT
Keyboard Interface
Interrupt Request
KBD
IE1.0
Figure 38. Keyboard Input Circuitry
Vcc
0
P1:x
KBF.x
1
Internal Pull-up
84
KBE.x
KBLS.x
AT89C5131
4136B–USB–09/03
AT89C5131
Power Reduction Mode
P1 inputs allow exit from idle and power down modes as detailed in section “Powerdown Mode”.
Registers
Table 69. KBF Register
KBF - Keyboard Flag Register (9Eh)
7
6
5
4
3
2
1
0
KBF7
KBF6
KBF5
KBF4
KBF3
KBF2
KBF1
KBF0
Bit
Number
7
6
5
4
3
2
1
0
Bit
Mnemonic Description
KBF7
Keyboard line 7 flag
Set by hardware when the Port line 7 detects a programmed level. It generates a
Keyboard interrupt request if the KBKBIE.7 bit in KBIE register is set.
Must be cleared by software.
KBF6
Keyboard line 6 flag
Set by hardware when the Port line 6 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.6 bit in KBIE register is set.
Must be cleared by software.
KBF5
Keyboard line 5 flag
Set by hardware when the Port line 5 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.5 bit in KBIE register is set.
Must be cleared by software.
KBF4
Keyboard line 4 flag
Set by hardware when the Port line 4 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.4 bit in KBIE register is set.
Must be cleared by software.
KBF3
Keyboard line 3 flag
Set by hardware when the Port line 3 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.3 bit in KBIE register is set.
Must be cleared by software.
KBF2
Keyboard line 2 flag
Set by hardware when the Port line 2 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.2 bit in KBIE register is set.
Must be cleared by software.
KBF1
Keyboard line 1 flag
Set by hardware when the Port line 1 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.1 bit in KBIE register is set.
Must be cleared by software.
KBF0
Keyboard line 0 flag
Set by hardware when the Port line 0 detects a programmed level. It generates a
Keyboard interrupt request if the KBIE.0 bit in KBIE register is set.
Must be cleared by software.
Reset Value = 0000 0000b
85
4136B–USB–09/03
Table 70. KBE Register
KBE - Keyboard Input Enable Register (9Dh)
7
6
5
4
3
2
1
0
KBE7
KBE6
KBE5
KBE4
KBE3
KBE2
KBE1
KBE0
Bit
Number
Bit
Mnemonic Description
7
KBE7
Keyboard line 7 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.7 bit in KBF register to generate an interrupt request.
6
KBE6
Keyboard line 6 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.6 bit in KBF register to generate an interrupt request.
5
KBE5
Keyboard line 5 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.5 bit in KBF register to generate an interrupt request.
4
KBE4
Keyboard line 4 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.4 bit in KBF register to generate an interrupt request.
3
KBE3
Keyboard line 3 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.3 bit in KBF register to generate an interrupt request.
2
KBE2
Keyboard line 2 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.2 bit in KBF register to generate an interrupt request.
1
KBE1
Keyboard line 1 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.1 bit in KBF register to generate an interrupt request.
0
KBE0
Keyboard line 0 Enable bit
Cleared to enable standard I/O pin.
Set to enable KBF.0 bit in KBF register to generate an interrupt request.
Reset Value = 0000 0000b
86
AT89C5131
4136B–USB–09/03
AT89C5131
Table 71. KBLS Register
KBLS-Keyboard Level Selector Register (9Ch)
7
6
5
4
3
2
1
0
KBLS7
KBLS6
KBLS5
KBLS4
KBLS3
KBLS2
KBLS1
KBLS0
Bit
Number
Bit
Mnemonic Description
7
KBLS7
Keyboard line 7 Level Selection bit
Cleared to enable a low level detection on Port line 7.
Set to enable a high level detection on Port line 7.
6
KBLS6
Keyboard line 6 Level Selection bit
Cleared to enable a low level detection on Port line 6.
Set to enable a high level detection on Port line 6.
5
KBLS5
Keyboard line 5 Level Selection bit
Cleared to enable a low level detection on Port line 5.
Set to enable a high level detection on Port line 5.
4
KBLS4
Keyboard line 4 Level Selection bit
Cleared to enable a low level detection on Port line 4.
Set to enable a high level detection on Port line 4.
3
KBLS3
Keyboard line 3 Level Selection bit
Cleared to enable a low level detection on Port line 3.
Set to enable a high level detection on Port line 3.
2
KBLS2
Keyboard line 2 Level Selection bit
Cleared to enable a low level detection on Port line 2.
Set to enable a high level detection on Port line 2.
1
KBLS1
Keyboard line 1 Level Selection bit
Cleared to enable a low level detection on Port line 1.
Set to enable a high level detection on Port line 1.
0
KBLS0
Keyboard line 0 Level Selection bit
Cleared to enable a low level detection on Port line 0.
Set to enable a high level detection on Port line 0.
Reset Value = 0000 0000b
87
4136B–USB–09/03
Programmable LED
AT89C5131 have up to 4 programmable LED current sources, configured by the register LEDCON.
Table 72. LEDCON Register
LEDCON (S:F1h)
LED Control Register
7
6
LED3
Bit
Number
7:6
5:4
3:2
1:0
5
4
LED2
Bit
Mnemonic
3
2
LED1
1
0
LED0
Description
LED3
Port/LED3 Configuration
0
0
Standard C51 Port
0
1
2 mA current source when P3.7 is O
1
0
4 mA current source when P3.7 is O
1
1
10 mA current source when P3.7 is O
LED2
Port/LED2 Configuration
0
0
Standard C51 Port
0
1
2 mA current source when P3.6 is O
1
0
4 mA current source when P3.6 is O
1
1
10 mA current source when P3.6 is O
LED1
Port/LED1 Configuration
0
0
Standard C51 Port
0
1
2 mA current source when P3.5 is O
1
0
4 mA current source when P3.5 is O
1
1
10 mA current source when P3.5 is O
LED0
Port/LED0 Configuration
0
0
Standard C51 Port
0
1
2 mA current source when P3.3 is O
1
0
4 mA current source when P3.3 is O
1
1
10 mA current source when P3.3 is O
Reset Value = 00h
88
AT89C5131
4136B–USB–09/03
AT89C5131
Serial Peripheral
Interface (SPI)
The Serial Peripheral Interface module (SPI) allows full-duplex, synchronous, serial
communication between the MCU and peripheral devices, including other MCUs.
Features
Features of the SPI module include the following:
Signal Description
•
Full-duplex, three-wire synchronous transfers
•
Master or Slave operation
•
Eight programmable Master clock rates
•
Serial clock with programmable polarity and phase
•
Master mode fault error flag with MCU interrupt capability
•
Write collision flag protection
Figure 39 shows a typical SPI bus configuration using one Master controller and many
Slave peripherals. The bus is made of three wires connecting all the devices:
Figure 39. SPI Master/Slaves Interconnection
Slave 1
MISO
MOSI
SCK
SS
MISO
MOSI
SCK
SS
VDD
Slave 4
Slave 3
MISO
MOSI
SCK
SS
0
1
2
3
MISO
MOSI
SCK
SS
MISO
MOSI
SCK
SS
PORT
Master
Slave 2
The Master device selects the individual Slave devices by using four pins of a parallel
port to control the four SS pins of the Slave devices.
Master Output Slave Input
(MOSI)
This 1-bit signal is directly connected between the Master Device and a Slave Device.
The MOSI line is used to transfer data in series from the Master to the Slave. Therefore,
it is an output signal from the Master, and an input signal to a Slave. A byte (8-bit word)
is transmitted most significant bit (MSB) first, least significant bit (LSB) last.
Master Input Slave Output
(MISO)
This 1-bit signal is directly connected between the Slave Device and a Master Device.
The MISO line is used to transfer data in series from the Slave to the Master. Therefore,
it is an output signal from the Slave, and an input signal to the Master. A byte (8-bit
word) is transmitted most significant bit (MSB) first, least significant bit (LSB) last.
SPI Serial Clock (SCK)
This signal is used to synchronize the data movement both in and out the devices
through their MOSI and MISO lines. It is driven by the Master for eight clock cycles
which allows to exchange one byte on the serial lines.
Slave Select (SS)
Each Slave peripheral is selected by one Slave Select pin (SS). This signal must stay
low for any message for a Slave. It is obvious that only one Master (SS high level) can
drive the network. The Master may select each Slave device by software through port
89
4136B–USB–09/03
pins (Figure 39). To prevent bus conflicts on the MISO line, only one slave should be
selected at a time by the Master for a transmission.
In a Master configuration, the SS line can be used in conjunction with the MODF flag in
the SPI Status register (SPSTA) to prevent multiple masters from driving MOSI and
SCK (see Section “Error Conditions”, page 94).
A high level on the SS pin puts the MISO line of a Slave SPI in a high-impedance state.
The SS pin could be used as a general-purpose if the following conditions are met:
•
The device is configured as a Master and the SSDIS control bit in SPCON is set.
This kind of configuration can be found when only one Master is driving the network
and there is no way that the SS pin could be pulled low. Therefore, the MODF flag in
the SPSTA will never be set(1).
•
The Device is configured as a Slave with CPHA and SSDIS control bits set(2) This
kind of configuration can happen when the system comprises one Master and one
Slave only. Therefore, the device should always be selected and there is no reason
that the Master uses the SS pin to select the communicating Slave device.
Notes:
Baud Rate
1. Clearing SSDIS control bit does not clear MODF.
2. Special care should be taken not to set SSDIS control bit when CPHA =’0’ because in
this mode, the SS is used to start the transmission.
In Master mode, the baud rate can be selected from a baud rate generator which is controlled by three bits in the SPCON register: SPR2, SPR1 and SPR0. The Master clock is
chosen from one of seven clock rates resulting from the division of the internal clock by
2, 4, 8, 16, 32, 64 or 128.
Table 73 gives the different clock rates selected by SPR2:SPR1:SPR0:
Table 73. SPI Master Baud Rate Selection
90
SPR2
SPR1
SPR0
Clock Rate
Baud Rate Divisor (BD)
0
0
0
Don’t Use
No BRG
0
0
1
FCLK PERIPH/4
4
0
1
0
FCLK PERIPH/8
8
0
1
1
FCLK PERIPH/16
16
1
0
0
FCLK PERIPH/32
32
1
0
1
FCLK PERIPH/64
64
1
1
0
FCLK PERIPH/128
128
1
1
1
Don’t Use
No BRG
AT89C5131
4136B–USB–09/03
AT89C5131
Functional Description
Figure 40 shows a detailed structure of the SPI module.
Figure 40. SPI Module Block Diagram
Internal Bus
SPDAT
Shift Register
FCLK PERIPH
Clock
Divider
/4
/8
/16
/32
/64
/128
7
6
5
4
3
2
1
0
Receive Data Register
Pin
Control
Logic
Clock
Logic
MOSI
MISO
M
S
Clock
Select
SCK
SS
SPR2 SPEN SSDIS MSTR CPOL CPHA SPR1 SPR0
SPCON
SPI
Control
SPI Interrupt Request
8-bit bus
1-bit signal
SPSTA
SPIF
Operating Modes
WCOL SSERR MODF
-
-
-
-
The Serial Peripheral Interface can be configured as one of the two modes: Master
mode or Slave mode. The configuration and initialization of the SPI module is made
through one register:
•
The Serial Peripheral CONtrol register (SPCON)
Once the SPI is configured, the data exchange is made using:
•
SPCON
•
The Serial Peripheral STAtus register (SPSTA)
•
The Serial Peripheral DATa register (SPDAT)
During an SPI transmission, data is simultaneously transmitted (shifted out serially) and
received (shifted in serially). A serial clock line (SCK) synchronizes shifting and sampling on the two serial data lines (MOSI and MISO). A Slave Select line (SS) allows
individual selection of a Slave SPI device; Slave devices that are not selected do not
interfere with SPI bus activities.
When the Master device transmits data to the Slave device via the MOSI line, the Slave
device responds by sending data to the Master device via the MISO line. This implies
full-duplex transmission with both data out and data in synchronized with the same clock
(Figure 41).
91
4136B–USB–09/03
Figure 41. Full-duplex Master/Slave Interconnection
8-bit Shift Register
SPI
Clock Generator
MISO
MISO
MOSI
MOSI
SCK
SS
Master MCU
8-bit Shift Register
SCK
VDD
SS
VSS
Slave MCU
Master Mode
The SPI operates in Master mode when the Master bit, MSTR (1), in the SPCON register
is set. Only one Master SPI device can initiate transmissions. Software begins the transmission from a Master SPI module by writing to the Serial Peripheral Data Register
(SPDAT). If the shift register is empty, the byte is immediately transferred to the shift
register. The byte begins shifting out on MOSI pin under the control of the serial clock,
SCK. Simultaneously, another byte shifts in from the Slave on the Master’s MISO pin.
The transmission ends when the Serial Peripheral transfer data flag, SPIF, in SPSTA
becomes set. At the same time that SPIF becomes set, the received byte from the Slave
is transferred to the receive data register in SPDAT. Software clears SPIF by reading
the Serial Peripheral Status register (SPSTA) with the SPIF bit set, and then reading the
SPDAT.
Slave Mode
The SPI operates in Slave mode when the Master bit, MSTR (2), in the SPCON register is
cleared. Before a data transmission occurs, the Slave Select pin, SS, of the Slave
device must be set to’0’. SS must remain low until the transmission is complete.
In a Slave SPI module, data enters the shift register under the control of the SCK from
the Master SPI module. After a byte enters the shift register, it is immediately transferred
to the receive data register in SPDAT, and the SPIF bit is set. To prevent an overflow
condition, Slave software must then read the SPDAT before another byte enters the
shift register (3). A Slave SPI must complete the write to the SPDAT (shift register) at
least one bus cycle before the Master SPI starts a transmission. If the write to the data
register is late, the SPI transmits the data already in the shift register from the previous
transmission.
Transmission Formats
Software can select any of four combinations of serial clock (SCK) phase and polarity
using two bits in the SPCON: the Clock POLarity (CPOL (4) ) and the Clock PHAse
(CPHA4). CPOL defines the default SCK line level in idle state. It has no significant
effect on the transmission format. CPHA defines the edges on which the input data are
sampled and the edges on which the output data are shifted (Figure 42 and Figure 43).
The clock phase and polarity should be identical for the Master SPI device and the communicating Slave device.
1.
The SPI module should be configured as a Master before it is enabled (SPEN set). Also
the Master SPI should be configured before the Slave SPI.
2.
3.
The SPI module should be configured as a Slave before it is enabled (SPEN set).
The maximum frequency of the SCK for an SPI configured as a Slave is the bus clock
speed.
Before writing to the CPOL and CPHA bits, the SPI should be disabled (SPEN =’0’).
4.
92
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 42. Data Transmission Format (CPHA = 0)
SCK cycle number
1
2
3
4
5
6
7
8
MSB
bit6
bit5
bit4
bit3
bit2
bit1
LSB
bit6
bit5
bit4
bit3
bit2
bit1
LSB
SPEN (internal)
SCK (CPOL = 0)
SCK (CPOL = 1)
MOSI (from Master)
MISO (from Slave)
MSB
SS (to Slave)
Capture point
Figure 43. Data Transmission Format (CPHA = 1)
1
2
3
4
5
6
7
8
MOSI (from Master)
MSB
bit6
bit5
bit4
bit3
bit2
bit1
LSB
MISO (from Slave)
MSB
bit6
bit5
bit4
bit3
bit2
bit1
SCK cycle number
SPEN (internal)
SCK (CPOL = 0)
SCK (CPOL = 1)
LSB
SS (to Slave)
Capture point
Figure 44. CPHA/SS Timing
MISO/MOSI
Byte 1
Byte 2
Byte 3
Master SS
Slave SS
(CPHA = 0)
Slave SS
(CPHA = 1)
As shown in Figure 43, the first SCK edge is the MSB capture strobe. Therefore the
Slave must begin driving its data before the first SCK edge, and a falling edge on the SS
pin is used to start the transmission. The SS pin must be toggled high and then low
between each byte transmitted (Figure 40).
Figure 44 shows an SPI transmission in which CPHA is’1’. In this case, the Master
begins driving its MOSI pin on the first SCK edge. Therefore the Slave uses the first
SCK edge as a start transmission signal. The SS pin can remain low between transmissions (Figure 39). This format may be preferable in systems having only one Master and
only one Slave driving the MISO data line.
93
4136B–USB–09/03
Error Conditions
The following flags in the SPSTA signal SPI error conditions:
Mode Fault (MODF)
Mode Fault error in Master mode SPI indicates that the level on the Slave Select (SS)
pin is inconsistent with the actual mode of the device. MODF is set to warn that there
may have a multi-master conflict for system control. In this case, the SPI system is
affected in the following ways:
•
An SPI receiver/error CPU interrupt request is generated,
•
The SPEN bit in SPCON is cleared. This disable the SPI,
•
The MSTR bit in SPCON is cleared
When SS DISable (SSDIS) bit in the SPCON register is cleared, the MODF flag is set
when the SS signal becomes “0”.
However, as stated before, for a system with one Master, if the SS pin of the Master
device is pulled low, there is no way that another Master attempt to drive the network. In
this case, to prevent the MODF flag from being set, software can set the SSDIS bit in the
SPCON register and therefore making the SS pin as a general-purpose I/O pin.
Clearing the MODF bit is accomplished by a read of SPSTA register with MODF bit set,
followed by a write to the SPCON register. SPEN Control bit may be restored to its original set state after the MODF bit has been cleared.
Write Collision (WCOL)
A Write Collision (WCOL) flag in the SPSTA is set when a write to the SPDAT register is
done during a transmit sequence.
WCOL does not cause an interruption, and the transfer continues uninterrupted.
Clearing the WCOL bit is done through a software sequence of an access to SPSTA
and an access to SPDAT.
Overrun Condition
An overrun condition occurs when the Master device tries to send several data bytes
and the Slave devise has not cleared the SPIF bit issuing from the previous data byte
transmitted. In this case, the receiver buffer contains the byte sent after the SPIF bit was
last cleared. A read of the SPDAT returns this byte. All others bytes are lost.
This condition is not detected by the SPI peripheral.
Interrupts
Two SPI status flags can generate a CPU interrupt requests:
Table 74. SPI Interrupts
Flag
Request
SPIF (SP Data Transfer)
SPI Transmitter Interrupt request
MODF (Mode Fault)
SPI Receiver/Error Interrupt Request (if SSDIS = “0”)
Serial Peripheral data transfer flag, SPIF: This bit is set by hardware when a transfer
has been completed. SPIF bit generates transmitter CPU interrupt requests.
Mode Fault flag, MODF: This bit becomes set to indicate that the level on the SS is
inconsistent with the mode of the SPI. MODF with SSDIS reset, generates receiver/error
CPU interrupt requests.
Figure 45 gives a logical view of the above statements.
94
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 45. SPI Interrupt Requests Generation
SPIF
SPI Transmitter
CPU Interrupt Request
SPI
CPU Interrupt Request
MODF
SPI Receiver/Error
CPU Interrupt Request
SSDIS
Registers
There are three registers in the module that provide control, status and data storage
functions. These registers are describes in the following paragraphs.
Serial Peripheral Control
Register (SPCON)
•
The Serial Peripheral Control Register does the following:
–
Selects one of the Master clock rates
–
Configure the SPI module as Master or Slave
–
Selects serial clock polarity and phase
–
Enables the SPI module
–
Frees the SS pin for a general-purpose
Table 75 describes this register and explains the use of each bit.
Table 75. SPCON Register
SPCON - Serial Peripheral Control Register (0C3H)
7
6
5
4
3
2
1
0
SPR2
SPEN
SSDIS
MSTR
CPOL
CPHA
SPR1
SPR0
Bit
Number
Bit Mnemonic Description
7
SPR2
6
SPEN
Serial Peripheral Rate 2
Bit with SPR1 and SPR0 define the clock rate.
Serial Peripheral Enable
Cleared to disable the SPI interface.
Set to enable the SPI interface.
SS Disable
5
SSDIS
5
MSTR
Cleared to enable SS in both Master and Slave modes.
Set to disable SS in both Master and Slave modes. In Slave mode, this bit has
no effect if CPHA = “0”.
Serial Peripheral Master
Cleared to configure the SPI as a Slave.
Set to configure the SPI as a Master.
Clock Polarity
4
CPOL
Cleared to have the SCK set to “0” in idle state.
Set to have the SCK set to “1” in idle low.
Clock Phase
3
CPHA
Cleared to have the data sampled when the SCK leaves the idle state (see
CPOL).
Set to have the data sampled when the SCK returns to idle state (see CPOL).
95
4136B–USB–09/03
Bit
Number
2
1
Bit Mnemonic Description
SPR1
SPR0
SPR2
SPR1
SPR0
Serial Peripheral Rate
0
0
0
Invalid
0
0
1
FCLK PERIPH/4
0
1
0
FCLK PERIPH/8
0
1
1
FCLK PERIPH/16
1
0
0
FCLK PERIPH/32
1
0
1
FCLK PERIPH/64
1
1
0
FCLK PERIPH/128
1
1
1
Invalid
Reset Value = 0001 0100b
Not bit addressable
Serial Peripheral Status Register
(SPSTA)
The Serial Peripheral Status Register contains flags to signal the following conditions:
•
Data transfer complete
•
Write collision
•
Inconsistent logic level on SS pin (mode fault error)
Table 76 describes the SPSTA register and explains the use of every bit in the register.
Table 76. SPSTA Register
SPSTA - Serial Peripheral Status and Control register (0C4H)
7
6
5
4
3
2
1
0
SPIF
WCOL
SSERR
MODF
-
-
-
-
Bit
Number
Bit
Mnemonic Description
Serial Peripheral data transfer flag
7
SPIF
Cleared by hardware to indicate data transfer is in progress or has been
approved by a clearing sequence.
Set by hardware to indicate that the data transfer has been completed.
Write Collision flag
6
WCOL
Cleared by hardware to indicate that no collision has occurred or has been
approved by a clearing sequence.
Set by hardware to indicate that a collision has been detected.
Synchronous Serial Slave Error flag
5
SSERR
Set by hardware when SS is deasserted before the end of a received data.
Cleared by disabling the SPI (clearing SPEN bit in SPCON).
Mode Fault
4
MODF
Cleared by hardware to indicate that the SS pin is at appropriate logic level, or
has been approved by a clearing sequence.
Set by hardware to indicate that the SS pin is at inappropriate logic level.
3
96
-
Reserved
The value read from this bit is indeterminate. Do not set this bit
AT89C5131
4136B–USB–09/03
AT89C5131
Bit
Number
Bit
Mnemonic Description
2
-
1
-
0
-
Reserved
The value read from this bit is indeterminate. Do not set this bit
Reserved
The value read from this bit is indeterminate. Do not set this bit.
Reserved
The value read from this bit is indeterminate. Do not set this bit.
Reset Value = 00X0 XXXXb
Not Bit addressable
Serial Peripheral Data Register
(SPDAT)
The Serial Peripheral Data Register (Table 77) is a read/write buffer for the receive data
register. A write to SPDAT places data directly into the shift register. No transmit buffer is
available in this model.
A Read of the SPDAT returns the value located in the receive buffer and not the content
of the shift register.
Table 77. SPDAT Register
SPDAT - Serial Peripheral Data Register (0C5H)
7
6
5
4
3
2
1
0
R7
R6
R5
R4
R3
R2
R1
R0
Reset Value = Indeterminate
R7:R0: Receive data bits
SPCON, SPSTA and SPDAT registers may be read and written at any time while there
is no on-going exchange. However, special care should be taken when writing to them
while a transmission is on-going:
•
Do not change SPR2, SPR1 and SPR0
•
Do not change CPHA and CPOL
•
Do not change MSTR
•
Clearing SPEN would immediately disable the peripheral
•
Writing to the SPDAT will cause an overflow
97
4136B–USB–09/03
Two Wire Interface (TWI)
Introduction
The Synchronous Serial Link Controller (SSLC) provides the selection of one synchronous serial interface among the two most popular ones:
•
Two Wire Interface (TWI).
•
Serial Peripheral Interface (SPI)
When an interface is selected, the other is no longer available, its usage is exclusive.
This section describes the TWI. In the rest of the section SSLC means TWI. The TWI
bus is a bi-directional two-wire serial communication standard. It is designed primarily
for simple but efficient integrated circuit (IC) control. The system is comprised of two
lines, SCL (Serial Clock) and SDA (Serial Data) that carry information between the ICs
connected to them. The serial data transfer is limited to 400 Kbit/s in standard mode.
Various communication configurations can be designed using this bus. Figure 46 shows
a typical TWI bus configuration. All the devices connected to the bus can be master and
slave.
Figure 46. TWI Bus Configuration
device1
device2
device3
...
deviceN
SCL
SDA
98
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 47. Block Diagram
8
SSADR
Comparator
Input
Filter
SDA
PI2.1
Output
Stage
Address Register
SSDAT
ACK
Shift Register
Arbitration and
Sink Logic
Input
Filter
SCL
PI2.0
Output
Stage
Serial clock
generator
Timing
and
Control
Logic
FCLK PERIPH/4
Internal Bus
8
Interrupt
Timer 1
overflow
SSCON
Control Register
7
Status
Bits
SSCS
Status
Decoder
Status Register
8
99
4136B–USB–09/03
Description
The CPU interfaces to the TWI logic via the following four 8-bit special function registers: the Synchronous Serial Control register (SSCON; Table 84 and Table 79), the
Synchronous Serial Data register (SSDAT; Table 85), the Synchronous Serial Control
and Status register (SSCS; Table 86) and the Synchronous Serial Address register
(SSADR see Table 87 and Table 78).
SSCON is used to enable SSLC, to program the bit rate (see Table 79), to enable slave
modes, to acknowledge or not a received data, to send a START or a STOP condition
on the TWI bus, and to acknowledge a serial interrupt. A hardware reset disables SSLC.
In write mode, SSCS is used to select the TWI interface and to select the bit rate source.
In read mode, SSCS contains a status code which reflects the status of the TWI logic
and the TWI bus. The three least significant bits are always zero. The five most significant bits contain the status code. There are 26 possible status codes. When SSCS
contains F8h, no relevant state information is available and no serial interrupt is
requested. A valid status code is available in SSCS one machine cycle after SI is set by
hardware and is still present one machine cycle after SI has been reset by software.
Table 80 to Table 83 give the status for the master modes and miscellaneous states.
SSDAT contains a byte of serial data to be transmitted or a byte which has just been
received. It is addressable while it is not in process of shifting a byte. This occurs when
TWI logic is in a defined state and the serial interrupt flag is set. Data in SSDAT remains
stable as long as SI is set. While data is being shifted out, data on the bus is simultaneously shifted in; SSDAT always contains the last byte present on the bus.
SSADR may be loaded with the 7-bit slave address (7 most significant bits) to which
SSLC will respond when programmed as a slave transmitter or receiver. The LSB is
used to enable general call address (00h) recognition.
Figure 48 shows how a data transfer is accomplished on the TWI bus.
Figure 48. Complete Data Transfer on TWI Bus
SDA
MSB
acknowledgement
signal from receiver
acknowledgement
signal from receiver
SCL
1
2
7
8
S
1
9
2
3-8
9
ACK
ACK
clock line held low
while interrupts are serviced
start
condition
P
stop
condition
The four operating modes are:
•
Master Transmitter
•
Master Receiver
•
Slave Transmitter
•
Slave Receiver
Data transfer in each mode of operation is shown in Figure 49 to Figure 52. These figures contain the following abbreviations:
S: START condition
R: Read bit (high level at SDA)
W: Write bit (low level at SDA)
100
AT89C5131
4136B–USB–09/03
AT89C5131
A: Acknowledge bit (low level at SDA)
A: Not acknowledge bit (high level at SDA)
Data: 8-bit data byte
P: STOP condition
In Figure 49 to Figure 52, circles are used to indicate when the serial interrupt flag is set.
The numbers in the circles show the status code held in SSCS. At these points, a service routine must be executed to continue or complete the serial transfer. These service
routines are not critical since the serial transfer is suspended until the serial interrupt
flag is cleared by software.
When the serial interrupt routine is entered, the status code in SSCS is used to branch
to the appropriate service routine. For each status code, the required software action
and details of the following serial transfer are given in Table 85 to Table 86.
Master Transmitter Mode
In the master transmitter mode, a number of data bytes are transmitted to a slave
receiver (Figure 49). Before the master transmitter mode can be entered, SSCON must
be initialised as follows:
CR2
SSIE
STA
STO
SI
AA
CR1
CR0
bit rate
1
0
0
0
X
bit rate
bit rate
CR0, CR1 and CR2 define the internal serial bit rate if external bit rate generator is not
used. SSIE must be set to enable SSLC. STA, STO and SI must be cleared.
The master transmitter mode may now be entered by setting the STA bit. The TWI logic
will now test the TWI bus and generate a START condition as soon as the bus becomes
free. When a START condition is transmitted, the serial interrupt flag (SI bit in SSCON)
is set, and the status code in SSCS will be 08h. This status must be used to vector to an
interrupt routine that loads SSDAT with the slave address and the data direction bit
(SLA+W).
When the slave address and the direction bit have been transmitted and an acknowledgement bit has been received, SI is set again and a number of status code in SSCS
are possible. There are 18h, 20h or 38h for the master mode and also 68h, 78h or B0h if
the slave mode was enabled (AA=logic 1). The appropriate action to be taken for each
of these status code is detailed in Table 84. This scheme is repeated until a STOP condition is transmitted.
SSIE, CR2, CR1 and CR0 are not affected by the serial transfer and are referred to
Table 84. After a repeated START condition (state 10h) SSLC may switch to the master
receiver mode by loading SSDAT with SLA+R.
Master Receiver Mode
In the master receiver mode, a number of data bytes are received from a slave transmitter (Figure 50). The transfer is initialized as in the master transmitter mode. When the
START condition has been transmitted, the interrupt routine must load SSDAT with the
7-bit slave address and the data direction bit (SLA+R). The serial interrupt flag SI must
then be cleared before the serial transfer can continue.
When the slave address and the direction bit have been transmitted and an acknowledgement bit has been received, the serial interrupt flag is set again and a number of
status code in SSCS are possible. There are 40h, 48h or 38h for the master mode and
also 68h, 78h or B0h if the slave mode was enabled (AA=logic 1). The appropriate
action to be taken for each of these status code is detailed in Table . This scheme is
repeated until a STOP condition is transmitted.
101
4136B–USB–09/03
SSIE, CR2, CR1 and CR0 are not affected by the serial transfer and are referred to
Table . After a repeated START condition (state 10h) SSLC may switch to the master
transmitter mode by loading SSDAT with SLA+W.
Slave Receiver Mode
In the slave receiver mode, a number of data bytes are received from a master transmitter (Figure 51). To initiate the slave receiver mode, SSADR and SSCON must be loaded
as follows:
Table 78. SSADR: Slave Receiver Mode Initialization
A6
A5
A4
A3
A2
A1
A0
GC
own slave address
The upper 7 bits are the address to which SSLC will respond when addressed by a master. If the LSB (GC) is set SSLC will respond to the general call address (00h); otherwise
it ignores the general call address.
Table 79. SSCON: Slave Receiver Mode Initialization
CR2
SSIE
STA
STO
SI
AA
CR1
CR0
bit rate
1
0
0
0
1
bit rate
bit rate
CR0, CR1 and CR2 have no effect in the slave mode (Table 82). SSIE must be set to
enable SSLC. The AA bit must be set to enable the own slave address or the general
call address acknowledgement. STA, STO and SI must be cleared.
When SSADR and SSCON have been initialised, SSLC waits until it is addressed by its
own slave address followed by the data direction bit which must be at logic 0 (W) for
SSLC to operate in the slave receiver mode. After its own slave address and the W bit
have been received, the serial interrupt flag is set and a valid status code can be read
from SSCS. This status code is used to vector to an interrupt service routine.The appropriate action to be taken for each of these status code is detailed in Table 84. The slave
receiver mode may also be entered if arbitration is lost while SSLC is in the master
mode (states 68h and 78h of Table 84).
If the AA bit is reset during a transfer, SSLC will return a not acknowledge (logic 1) to
SDA after the next received data byte. While AA is reset, SSLC does not respond to its
own slave address. However, the TWI bus is still monitored and address recognition
may be resume at any time by setting AA. This means that the AA bit may be used to
temporarily isolate SSLC from the TWI bus.
Slave Transmitter Mode
102
In the slave transmitter mode, a number of data bytes are transmitted to a master
receiver (Figure 52). Data transfer is initialized as in the slave receiver mode. When
SSADR and SSCON have been initialized, SSLC waits until it is addressed by its own
slave address followed by the data direction bit which must be at logic 1 (R) for SSLC to
operate in the slave transmitter mode. After its own slave address and the R bit have
been received, the serial interrupt flag is set and a valid status code can be read from
SSCS. This status code is used to vector to an interrupt service routine. The appropriate
action to be taken for each of these status code is detailed in Table 83. The slave transmitter mode may also be entered if arbitration is lost while SSLC is in the master mode
(state B0h of Table 83).
AT89C5131
4136B–USB–09/03
AT89C5131
If the AA bit is reset during a transfer, SSLC will transmit the last byte of the transfer and
enter state C0h or C8h. SSLC is switched to the not addressed slave mode and will
ignore the master receiver if it continues the transfer. Thus the master receiver receives
all 1’s as serial data. While AA is reset, SSLC does not respond to its own slave
address. However, the TWI bus is still monitored and address recognition may be
resume at any time by setting AA. This means that the AA bit may be used to temporarily isolate SSLC from the TWI bus.
Miscellaneous States
There are two SSCS codes that do not correspond to a define SSLC hardware state
(see Table 86). These codes are discuss hereafter.
Status F8h indicates that no relevant information is available because the serial interrupt
flag is not set yet. This occurs between other states and when SSLC is not involved in a
serial transfer.
Status 00h indicates that a bus error has occurred during an SSLC serial transfer. A bus
error is caused when a START or a STOP condition occurs at an illegal position in the
format frame. Examples of such illegal positions happen during the serial transfer of an
address byte, a data byte, or an acknowledge bit. When a bus error occurs, SI is set. To
recover from a bus error, the STO flag must be set and SI must be cleared. This causes
SSLC to enter the not addressed slave mode and to clear the STO flag (no other bits in
SSCON are affected). The SDA and SCL lines are released and no STOP condition is
transmitted.
Notes
SSLC interfaces to the external TWI bus via two port pins: SCL (serial clock line) and
SDA (serial data line). To avoid low level asserting on these lines when SSLC is
enabled, the output latches of SDA and SLC must be set to logic 1.
Bit Frequency (kHz)
CR2
CR1
CR0
FOSCA= 12 MHz
FOSCA = 16 MHz
FOSCA divided by
0
0
0
47
62.5
256
0
0
1
53.5
71.5
224
0
1
0
62.5
83
192
0
1
1
75
100
160
1
0
0
12.5
16.5
960
1
0
1
100
-
120
1
1
0
-
-
60
0.67 < . < 83
96 · (256 - reload
value Timer 1)
(reload value range:
0-254 in mode 2)
1
1
1
0.5 < . < 62.5
103
4136B–USB–09/03
Figure 49. Format and State in the Master Transmitter Mode
MT
Successfull
transmission
to a slave
receiver
S
SLA
08h
W
A
Data
A
P
28h
18h
Next transfer
started with a
repeated start
condition
S
SLA
W
10h
Not acknowledge
received after the
slave address
A
R
P
20h
MR
Not acknowledge
received after a data
byte
A
P
30h
Arbitration lost in slave
address or data byte
A or A
Other master
continues
38h
Arbitration lost and
addressed as slave
From slave to master
104
Other master
continues
38h
Other master
continues
A
68h
From master to slave
A or A
Data
n
78h
A
B0h
To corresponding
states in slave mode
Any number of data bytes and their associated
acknowledge bits
This number (contained in SSCS) corresponds
to a defined state of the TWI bus
AT89C5131
4136B–USB–09/03
AT89C5131
Table 80. Status for Master Receiver Mode
Application Software Response
Status
Code
(SSCS)
To SSCON
Status of the TWI Bus and
TWI Hardware
08h
A START condition has been
transmitted
10h
A repeated START condition
has been transmitted
38h
40h
48h
Arbitration lost in SLA+R or
NOT ACK bit
SLA+R has been
transmitted; ACK has been
received
SLA+R has been
transmitted; NOT ACK has
been received
50h
58h
Data byte has been
received; ACK has been
returned
Data byte has been
received; NOT ACK has
been returned
To/from SSDAT
STA
STO
SI
AA
Next Action Taken by TWI Software
Load SLA+R
X
0
0
X
SLA+W will be transmitted;
ACK will be transmitted
Load SLA+R or
X
0
0
X
SLA+W will be transmitted;
ACK will be transmitted
Load SLA+W
X
0
0
X
SLA+W will be transmitted
Logic will switched to master transmitter mode
No SSDAT action or
0
0
0
X
TWI bus will be released and not addressed
slave mode will be entered
No SSDAT action
1
0
0
X
A START condition will be transmitted when the
bus becomes free
No SSDAT action or
0
0
0
0
Data byte will be received and NOT ACK will be
returned
No SSDAT action
0
0
0
1
Data byte will be received and ACK will be
returned
No SSDAT action or
1
0
0
X
No SSDAT action or
0
1
0
X
STOP condition will be transmitted and STO flag
will be reset
No SSDAT action
1
1
0
X
STOP condition followed by a START condition
will be transmitted and STO flag will be reset
Read data byte or
0
0
0
0
Data byte will be received and NOT ACK will be
returned
read data byte
0
0
0
1
Data byte will be received and ACK will be
returned
Read data byte or
1
0
0
X
Read data byte or
0
1
0
X
STOP condition will be transmitted and STO flag
will be reset
Read data byte
1
1
0
X
STOP condition followed by a START condition
will be transmitted and STO flag will be reset
Repeated START will be transmitted
Repeated START will be transmitted
105
4136B–USB–09/03
Figure 50. Format and State in the Master Receiver Mode
MR
Successfull
transmission
to a slave
receiver
S
SLA
08h
R
Data
A
A
50h
40h
Data
A
P
58h
Next transfer
started with a
repeated start
condition
S
SLA
R
10h
Not acknowledge
received after the
slave address
A
W
P
MT
48h
Arbitration lost in slave
address or acknowledge bit
A or A
Other master
continues
38h
Arbitration lost and
addressed as slave
From slave to master
106
Other master
continues
38h
Other master
continues
A
68h
From master to slave
A
Data
n
78h
A
B0h
To corresponding
states in slave mode
Any number of data bytes and their associated
acknowledge bits
This number (contained in SSCS) corresponds
to a defined state of the TWI bus
AT89C5131
4136B–USB–09/03
AT89C5131
Table 81. Status for Master Receiver Mode
Application Software Response
To SSCON
Status Code
(SSCS)
Status of the TWI Bus
and TWI Hardware
To/from SSDAT
STA
STO
SI
AA
Own SLA+W has
been received; ACK
has been returned
No SSDAT action
or
No SSDAT action
X
0
0
0
60h
X
0
0
1
Arbitration lost in
SLA+R/W as master;
own SLA+W has been
received; ACK has
been returned
No SSDAT action
or
No SSDAT action
X
0
0
0
X
0
0
1
General call address
has been received;
ACK has been
returned
No SSDAT action
or
No SSDAT action
X
0
0
0
X
0
0
1
Arbitration lost in
SLA+R/W as master;
general call address
has been received;
ACK has been
returned
No SSDAT action
or
No SSDAT action
X
0
0
0
X
0
0
1
Previously addressed
with own SLA+W; data
has been received;
ACK has been
returned
No SSDAT action
or
No SSDAT action
X
0
0
0
X
0
0
1
Read data byte or
0
0
0
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA
Read data byte or
0
0
0
1
Switched to the not addressed slave mode; own SLA will
be recognised; GCA will be recognised if GC=logic 1
Read data byte or
1
0
0
0
68h
70h
78h
80h
88h
90h
98h
Previously addressed
with own SLA+W; data
has been received;
NOT ACK has been
returned
Previously addressed
with general call; data
has been received;
ACK has been
returned
Previously addressed
with general call; data
has been received;
NOT ACK has been
returned
Next Action Taken by TWI Software
Data byte will be received and NOT ACK will be returned
Data byte will be received and ACK will be returned
Data byte will be received and NOT ACK will be returned
Data byte will be received and ACK will be returned
Data byte will be received and NOT ACK will be returned
Data byte will be received and ACK will be returned
Data byte will be received and NOT ACK will be returned
Data byte will be received and ACK will be returned
Data byte will be received and NOT ACK will be returned
Data byte will be received and ACK will be returned
Switched to the not addressed slave mode; no
recognition of own SLA or GCA. A START condition will
be transmitted when the bus becomes free
Switched to the not addressed slave mode; own SLA will
be recognised; GCA will be recognised if GC=logic 1. A
START condition will be transmitted when the bus
becomes free
Read data byte
1
0
0
1
Read data byte or
X
0
0
0
Read data byte
X
0
0
1
Read data byte or
0
0
0
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA
Read data byte or
0
0
0
1
Switched to the not addressed slave mode; own SLA will
be recognised; GCA will be recognised if GC=logic 1
Read data byte or
Read data byte
1
1
0
0
0
0
0
1
Data byte will be received and NOT ACK will be returned
Data byte will be received and ACK will be returned
Switched to the not addressed slave mode; no
recognition of own SLA or GCA. A START condition will
be transmitted when the bus becomes free
Switched to the not addressed slave mode; own SLA will
be recognised; GCA will be recognised if GC=logic 1. A
START condition will be transmitted when the bus
becomes free
107
4136B–USB–09/03
Table 81. Status for Master Receiver Mode (Continued)
Application Software Response
To SSCON
Status Code
(SSCS)
Status of the TWI Bus
and TWI Hardware
To/from SSDAT
STA
STO
SI
AA
Next Action Taken by TWI Software
Switched to the not addressed slave mode; no
recognition of own SLA or GCA
No SSDAT action
A0h
108
A STOP condition or
repeated START
condition has been
received while still
addressed as slave
or
No SSDAT action
or
No SSDAT action
or
No SSDAT action
0
0
0
0
Switched to the not addressed slave mode; own SLA will
be recognised; GCA will be recognised if GC=logic 1
0
0
0
1
1
0
0
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA. A START condition will
be transmitted when the bus becomes free
1
0
0
1
Switched to the not addressed slave mode; own SLA will
be recognised; GCA will be recognised if GC=logic 1. A
START condition will be transmitted when the bus
becomes free
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 51. Format and State in the Slave Receiver Mode
Reception of the own
slave address and one or
more
data bytes. All are
or
acknowledged.
S
SLA
W
Data
A
60h
A
Data
80h
Last data byte received
is not acknowledged.
A
P or S
80h
A0h
A
P or S
88h
Arbitration lost as master
and addressed as slave
A
68h
Reception of the general call
address and one or more data
bytes.
General Call
Data
A
70h
Last data byte received is
not acknowledged.
A
90h
Data
A
P or S
90h
A0h
A
P or S
98h
A
Arbitration lost as master and
addressed as slave by general call
78h
From master to slave
From slave to master
Data
n
A
Any number of data bytes and their associated
acknowledge bits
This number (contained in SSCS) corresponds
to a defined state of the TWI bus
109
4136B–USB–09/03
Table 82. Status for Slave Transmitter Mode
Application Software Response
Status
code
(SSCS)
A8h
B0h
B8h
C0h
C8h
110
To SSCON
Status of the TWI bus
and TWI hardware
Own SLA+R has been
received; ACK has been
returned
Arbitration lost in
SLA+R/W as master; own
SLA+R has been
received; ACK has been
returned
Data byte in SSDAT has
been transmitted; NOT
ACK has been received
Data byte in SSDAT has
been transmitted; NOT
ACK has been received
Last data byte in SSDAT
has been transmitted
(AA=0); ACK has been
received
To/from
SSDAT
STA
STO
SI
AA
Load data
byte or
X
0
0
0
Last data byte will be transmitted and NOT ACK will
be received
X
0
0
1
Data byte will be transmitted and ACK will be received
X
0
0
0
Last data byte will be transmitted and NOT ACK will
be received
X
0
0
1
Data byte will be transmitted and ACK will be received
X
0
0
0
Last data byte will be transmitted and NOT ACK will
be received
X
0
0
1
Data byte will be transmitted and ACK will be received
No SSDAT
action or
0
0
0
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA
No SSDAT
action or
0
1
Switched to the not addressed slave mode; own SLA
will be recognised; GCA will be recognised if GC=logic
1
No SSDAT
action or
1
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA. A START condition
will be transmitted when the bus becomes free
No SSDAT
action
1
0
0
1
No SSDAT
action or
0
0
0
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA
No SSDAT
action or
0
1
Switched to the not addressed slave mode; own SLA
will be recognised; GCA will be recognised if GC=logic
1
No SSDAT
action or
1
0
Switched to the not addressed slave mode; no
recognition of own SLA or GCA. A START condition
will be transmitted when the bus becomes free
No SSDAT
action
1
Load data
byte
Load data
byte or
Load data
byte
Load data
byte or
Load data
byte
0
0
0
0
0
0
0
0
0
0
1
Next Action Taken by TWI Software
Switched to the not addressed slave mode; own SLA
will be recognised; GCA will be recognised if GC=logic
1. A START condition will be transmitted when the bus
becomes free
Switched to the not addressed slave mode; own SLA
will be recognised; GCA will be recognised if GC=logic
1. A START condition will be transmitted when the bus
becomes free
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 52. Format and State in the Slave Transmitter Mode
Reception of the
own slave address
and one or more
data bytes
S
SLA
A
R
Data
A8h
Arbitration lost as master
and addressed as slave
A
Data
P or S
A
C0h
B8h
A
B0h
Last data byte transmitted.
Switched to not addressed
slave (AA=0)
All 1’s P or S
A
C8h
From master to slave
From slave to master
Data
A
n
Any number of data bytes and their associated
acknowledge bits
This number (contained in SSCS) corresponds
to a defined state of the TWI bus
Table 83. Status for Miscellaneous States
Application Software Response
To SSCON
Status Code
(SSCS)
Status of the TWI bus
and TWI hardware
F8h
No relevant state
information available;
SI= 0
00h
Bus error due to an
illegal START or STOP
condition
To/From SSDAT
No SSDAT action
No SSDAT action
S
T
A
S
T
O
S A
I A
No SSCON
action
0
1
0
Next action taken by
TWI software
Wait or proceed current
transfer
Only the internal
hardware is affected, no
STOP condition is sent on
X
the bus. In all cases, the
bus is released and STO
is reset
111
4136B–USB–09/03
Registers
Table 84. SSCON Register
SSCON - Synchronous Serial Control Register (93h)
7
6
5
4
3
2
1
0
CR2
SSIE
STA
STO
SI
AA
CR1
CR0
Bit
Number
Bit
Mnemonic Description
7
CR2
Control Rate bit 2
See .
6
SSIE
Synchronous Serial Interface Enable bit
Clear to disable SSLC.
Set to enable SSLC.
5
STA
Start flag
Set to send a START condition on the bus.
4
ST0
Stop flag
Set to send a STOP condition on the bus.
3
SI
Synchronous Serial Interrupt flag
Set by hardware when a serial interrupt is requested.
Must be cleared by software to acknowledge interrupt.
2
AA
Assert Acknowledge flag
Clear in master and slave receiver modes, to force a not acknowledge (high level
on SDA).
Clear to disable SLA or GCA recognition.
Set to recognise SLA or GCA (if GC set) for entering slave receiver or transmitter
modes.
Set in master and slave receiver modes, to force an acknowledge (low level on
SDA).
This bit has no effect when in master transmitter mode.
1
CR1
Control Rate bit 1
See Table
0
CR0
Control Rate bit 0
See Table
Table 85. SSDAT (095h) - Synchronous Serial Data Register (read/write)
SD7
SD6
SD5
SD4
SD3
SD2
SD1
SD0
7
6
5
4
3
2
1
0
Bit
Number
112
Bit
Mnemonic Description
7
SD7
Address bit 7 or Data bit 7.
6
SD6
Address bit 6 or Data bit 6.
5
SD5
Address bit 5 or Data bit 5.
4
SD4
Address bit 4 or Data bit 4.
3
SD3
Address bit 3 or Data bit 3.
2
SD2
Address bit 2 or Data bit 2.
AT89C5131
4136B–USB–09/03
AT89C5131
Bit
Number
Bit
Mnemonic Description
1
SD1
Address bit 1 or Data bit 1.
0
SD0
Address bit 0 (R/W) or Data bit 0.
Table 86. SSCS (094h) Read - Synchronous Serial Control and Status Register
7
6
5
4
3
2
1
0
SC4
SC3
SC2
SC1
SC0
0
0
0
Bit
Number
Bit
Mnemonic Description
0
0
Always zero
1
0
Always zero
2
0
Always zero
3
SC0
4
SC1
5
SC2
Status Code bit 2
See Table 80 to Table 83
6
SC3
Status Code bit 3
See Table 80 to Table 83
7
SC4
Status Code bit 4
See Table 80 to Table 83
Status Code bit 0
See Table 80 to Table 83
Status Code bit 1
See Table 80 to Table 83
Table 87. SSADR (096h) - Synchronous Serial Address Register (read/write)
7
6
5
4
3
2
1
0
A7
A6
A5
A4
A3
A2
A1
A0
Bit
Number
Bit
Mnemonic Description
7
A7
Slave address bit 7.
6
A6
Slave address bit 6.
5
A5
Slave address bit 5.
4
A4
Slave address bit 4.
3
A3
Slave address bit 3.
2
A2
Slave address bit 2.
1
A1
Slave address bit 1.
0
GC
General call bit
Clear to disable the general call address recognition.
Set to enable the general call address recognition.
113
4136B–USB–09/03
USB Controller
Introduction
The AT89C5131 implements a USB device controller supporting full speed data transfer
in accordance with the USB 1.1 and 2.0 Specifications. In addition to the default control
endpoint 0, it provides 6 other endpoints, which can be configured in control, bulk, interrupt or isochronous modes:
•
Endpoint 0:32-byte FIFO, default control endpoint
•
Endpoint 1, 2, 3: 32-byte FIFO
•
Endpoint 4, 5: 2 x 64-byte Ping-pong FIFO
•
Endpoint 6: 2 x 512-byte Ping-pong FIFO
This allows the firmware to be developed conforming to most USB device classes, for
example:
•
USB Mass Storage Class Control/Bulk/Interrupt (CBI) Transport, Revision 1.0 December 14, 1998
•
USB Mass Storage Class Bulk-only Transport, Revision 1.0 - September 31, 1999
•
USB Human Interface Device Class, Version 1.1 - April 7, 1999
•
USB Device Firmware Upgrade Class, Revision 1.0 - May 13, 1999
USB Mass Storage Classes
USB Mass Storage Class CBI
Transport
Within the CBI framework, the control endpoint is used to transport command blocks as
well as to transport standard USB requests. One Bulk-out endpoint is used to transport
data from the host to the device. One Bulk-in endpoint is used to transport data from the
device to the host. And one interrupt endpoint may also be used to signal command
completion (protocol 0) but it is optional and may not be used (protocol 1).
The following configuration adheres to these requirements:
USB Mass Storage Class Bulkonly Transport
•
Endpoint 0: 8 bytes, Control In-Out
•
Endpoint 4: 64 bytes, Bulk-out
•
Endpoint 5: 64 bytes, Bulk-in
•
Endpoint 3: 8 bytes, Interrupt In
Within the Bulk-only framework, the Control endpoint is only used to transport classspecific and standard USB requests for device set-up and configuration. One Bulk-out
endpoint is used to transport commands and data from the host to the device. One Bulkin endpoint is used to transport status and data from the device to the host. No interrupt
endpoint is needed.
The following configuration adheres to these requirements:
114
•
Endpoint 0: 8 bytes, Control In-Out
•
Endpoint 4: 64 bytes, Bulk-out
•
Endpoint 5: 64 bytes, Bulk-in
•
Endpoint 3: not used
AT89C5131
4136B–USB–09/03
AT89C5131
USB Device Firmware
Upgrade (DFU)
The USB Device Firmware Update (DFU) protocol can be used to upgrade the on-chip
Flash memory of the AT89C5131. This allows the implementation of product enhancements and patches to devices that are already in the field. Two different configurations
and descriptor sets are used to support DFU functions. The Run-Time configuration coexists with the usual functions of the device, which may be USB Mass Storage for the
AT89C5131. It is used to initiate DFU from the normal operating mode. The DFU configuration is used to perform the firmware update after device re-configuration and USB
reset. It excludes any other function. Only the default control pipe (endpoint 0) is used to
support DFU services in both configurations.
The only possible value for the wMaxPacketSize in the DFU configuration is 32 bytes,
which is the size of the FIFO implemented for endpoint 0.
Description
The USB device controller provides the hardware that the AT89C5131 needs to interface a USB link to a data flow stored in a double port memory (DPRAM).
The USB controller requires a 48 MHz ±0.25% reference clock, which is the output of
the AT89C5131 PLL (see Section “PLL”, page 20) divided by a clock prescaler. This
clock is used to generate a 12 MHz Full-speed bit clock from the received USB differential data and to transmit data according to full speed USB device tolerance. Clock
recovery is done by a Digital Phase Locked Loop (DPLL) block, which is compliant with
the jitter specification of the USB bus.
The Serial Interface Engine (SIE) block performs NRZI encoding and decoding, bit stuffing, CRC generation and checking, and the serial-parallel data conversion.
The Universal Function Interface (UFI) realizes the interface between the data flow and
the Dual Port RAM.
Figure 53. USB Device Controller Block Diagram
48 MHz +/- 0.25%
DPLL 12 MHz
D+
D-
C51
Microcontroller
Interface
USB
D+/DBuffer
UFI
Up to 48 MHz
UC_sysclk
SIE
115
4136B–USB–09/03
Serial Interface Engine (SIE)
The SIE performs the following functions:
•
NRZI data encoding and decoding.
•
Bit stuffing and un-stuffing.
•
CRC generation and checking.
•
Handshakes.
•
TOKEN type identifying.
•
Address checking.
•
Clock generation (via DPLL).
Figure 54. SIE Block Diagram
End of Packet
Detection
SYNC Detection
Start of Packet
Detection
D-
Clock
Recovery
Clk48
(48 MHz)
116
PID Decoder
NRZI ‘NRZ
Bit Un-stuffing
Packet Bit Counter
D+
Address Decoder DataOut
8
Serial to
Parallel Conversion
SysClk
(12 MHz)
CRC5 and CRC16
Generation/Check
USB Pattern Generator
Parallel to Serial Converter
Bit Stuffing
NRZI Converter
CRC16 Generator
8
DataIn [7:0]
AT89C5131
4136B–USB–09/03
AT89C5131
Function Interface Unit (FIU)
The Function Interface Unit provides the interface between the AT89C5131 and the SIE.
It manages transactions at the packet level with minimal intervention from the device
firmware, which reads and writes the endpoint FIFOs.
Figure 55. UFI Block Diagram
FIU
DPLL
Asynchronous Information
CSREG 0 to 7
Transfer
Transfer
Control
Endpoint 6
Registers
FSM
Endpoint 5
Bank
Endpoint 4
Endpoint 3
Endpoint 2
Endpoint 1
Endpoint 0
DPR Control
USB Side
SIE
DPR Control
mP side
C51
Microcontroller
Interface
Up to 48 MHz
UC_sysclk
User DPRAM
Figure 56. Minimum Intervention from the USB Device Firmware
OUT Transactions:
HOST
UFI
C51
OUT DATA0 (n bytes)
OUT
ACK
DATA1
OUT
interrupt C51
NACK
DATA1
ACK
Endpoint FIFO read (n bytes)
IN Transactions:
HOST
UFI
C51
IN
IN
NACK
Endpoint FIFO write
IN
DATA1
ACK
DATA1
interrupt C51
Endpoint FIFO write
117
4136B–USB–09/03
Configuration
General Configuration
•
USB controller enable
Before any USB transaction, the 48 MHz required by the USB controller must be
correctly generated (See “Clock Controller” on page 19).
The USB controller will be then enabled by setting the EUSB bit in the USBCON
register.
•
Set address
After a Reset or a USB reset, the software has to set the FEN (Function Enable) bit
in the USBADDR register. This action will allow the USB controller to answer to the
requests sent at the address 0.
When a SET_ADDRESS request has been received, the USB controller must only
answer to the address defined by the request. The new address will be stored in the
USBADDR register. The FEN bit and the FADDEN bit in the USBCON register will
be set to allow the USB controller to answer only to requests sent at the new
address.
•
Set configuration
The CONFG bit in the USBCON register has to be set after a
SET_CONFIGURATION request with a non-zero value. Otherwise, this bit has to be
cleared.
Endpoint Configuration
•
Selection of an Endpoint
The endpoint register access is performed using the UEPNUM register. The
registers
–
UEPSTAX
–
UEPCONX
–
UEPDATX
–
UBYCTLX
–
UBYCTHX
These registers correspond to the endpoint whose number is stored in the UEPNUM register. To select an Endpoint, the firmware has to write the endpoint number
in the UEPNUM register.
Figure 57. Endpoint Selection
Endpoint 0
UEPSTA0
UEPCON0
UBYCTH0
Endpoint 6
UEPSTA6
0
SFR registers
UBYCTL0
UEPCON6
UBYCTH6
UEPDAT0
UEPDAT6
1
2
3
4
5
6
X
UEPSTAX
UEPCONX
UBYCTHX
UEPDATX
UBYCTLX
UBYCTL6
UEPNUM
118
AT89C5131
4136B–USB–09/03
AT89C5131
•
Endpoint enable
Before using an endpoint, this one will be enabled by setting the EPEN bit in the
UEPCONX register.
An endpoint which is not enabled won’t answer to any USB request. The Default
Control Endpoint (Endpoint 0) will always be enabled in order to answer to USB
standard requests.
•
Endpoint type configuration
All Standard Endpoints can be configured in Control, Bulk, Interrupt or Isochronous
mode. The Ping-pong Endpoints can be configured in Bulk, Interrupt or Isochronous
mode. The configuration of an endpoint is performed by setting the field EPTYPE
with the following values:
–
Control:EPTYPE = 00b
–
Isochronous:EPTYPE = 01b
–
Bulk:EPTYPE = 10b
–
Interrupt:EPTYPE = 11b
The Endpoint 0 is the Default Control Endpoint and will always be configured in
Control type.
•
Endpoint direction configuration
For Bulk, Interrupt and Isochronous endpoints, the direction is defined with the
EPDIR bit of the UEPCONX register with the following values:
–
IN:EPDIR = 1b
–
OUT:EPDIR = 0b
For Control endpoints, the EPDIR bit has no effect.
•
Summary of Endpoint Configuration:
Do not forget to select the correct endpoint number in the UEPNUM register before
accessing to endpoint specific registers.
Table 88. Summary of Endpoint Configuration
Endpoint Configuration
EPEN
EPDIR
EPTYPE
UEPCONX
Disabled
0b
Xb
XXb
0XXX XXXb
Control
1b
Xb
00b
80h
Bulk-in
1b
1b
10b
86h
Bulk-out
1b
0b
10b
82h
Interrupt-In
1b
1b
11b
87h
Interrupt-Out
1b
0b
11b
83h
Isochronous-In
1b
1b
01b
85h
Isochronous-Out
1b
0b
01b
81h
119
4136B–USB–09/03
•
Endpoint FIFO reset
Before using an endpoint, its FIFO will be reset. This action resets the FIFO pointer
to its original value, resets the byte counter of the endpoint (UBYCTLX and
UBYCTHX registers), and resets the data toggle bit (DTGL bit in UEPCONX).
The reset of an endpoint FIFO is performed by setting to 1 and resetting to 0 the
corresponding bit in the UEPRST register.
For example, in order to reset the Endpoint number 2 FIFO, write 0000 0100b then
0000 0000b in the UEPRST register.
Note that the endpoint reset doesn’t reset the bank number for ping-pong endpoints.
Read/Write Data FIFO
Read Data FIFO
The read access for each OUT endpoint is performed using the UEPDATX register.
After a new valid packet has been received on an Endpoint, the data are stored into the
FIFO and the byte counter of the endpoint is updated (UBYCTLX and UBYCTHX registers). The firmware has to store the endpoint byte counter before any access to the
endpoint FIFO. The byte counter is not updated when reading the FIFO.
To read data from an endpoint, select the correct endpoint number in UEPNUM and
read the UEPDATX register. This action automatically decreases the corresponding
address vector, and the next data is then available in the UEPDATX register.
Write Data FIFO
The write access for each IN endpoint is performed using the UEPDATX register.
To write a byte into an IN endpoint FIFO, select the correct endpoint number in UEPNUM and write into the UEPDATX register. The corresponding address vector is
automatically increased, and another write can be carried out.
Warning 1: The byte counter is not updated.
Warning 2: Do not write more bytes than supported by the corresponding endpoint.
FIFO Mapping
Figure 58. Endpoint FIFO Configuration
Endpoint 0
UEPSTA0
UEPCON0
UBYCTH0
Endpoint 6
UEPSTA6
0
SFR registers
UBYCTL0
UEPCON6
UBYCTH6
UEPDAT0
UEPDAT6
1
2
3
4
5
6
X
UEPSTAX
UEPCONX
UBYCTHX
UEPDATX
UBYCTLX
UBYCTL6
UEPNUM
120
AT89C5131
4136B–USB–09/03
AT89C5131
Bulk/Interrupt
Transactions
Bulk and Interrupt transactions are managed in the same way.
Bulk/Interrupt OUT
Transactions in Standard
Mode
Figure 59. Bulk/Interrupt OUT transactions in Standard Mode
HOST
OUT
C51
UFI
DATA0 (n bytes)
ACK
RXOUTB0
Endpoint FIFO read byte 1
OUT
DATA1
Endpoint FIFO read byte 2
NAK
OUT
Endpoint FIFO read byte n
DATA1
Clear RXOUTB0
NAK
OUT
DATA1
ACK
RXOUTB0
Endpoint FIFO read byte 1
An endpoint will be first enabled and configured before being able to receive Bulk or
Interrupt packets.
When a valid OUT packet is received on an endpoint, the RXOUTB0 bit is set by the
USB controller. This triggers an interrupt if enabled. The firmware has to select the corresponding endpoint, store the number of data bytes by reading the UBYCTLX and
UBYCTHX registers. If the received packet is a ZLP (Zero Length Packet), the
UBYCTLX and UBYCTHX register values are equal to 0 and no data has to be read.
When all the endpoint FIFO bytes have been read, the firmware will clear the RXOUTB0
bit to allow the USB controller to accept the next OUT packet on this endpoint. Until the
RXOUTB0 bit has been cleared by the firmware, the USB controller will answer a NAK
handshake for each OUT requests.
If the Host sends more bytes than supported by the endpoint FIFO, the overflow data
won’t be stored, but the USB controller will consider that the packet is valid if the CRC is
correct and the endpoint byte counter contains the number of bytes sent by the Host.
121
4136B–USB–09/03
Bulk/Interrupt OUT
Transactions in Ping-pong
Mode
Figure 60. Bulk/Interrupt OUT Transactions in Ping-pong Mode
HOST
OUT
UFI
C51
DATA0 (n Bytes)
ACK
RXOUTB0
Endpoint FIFO Bank 0 - Read Byte 1
OUT
Endpoint FIFO Bank 0 - Read Byte 2
DATA1 (m Bytes)
ACK
Endpoint FIFO Bank 0 - Read Byte n
Clear RXOUTB0
OUT
RXOUTB1
DATA0 (p Bytes)
Endpoint FIFO Bank 1 - Read Byte 1
ACK
Endpoint FIFO Bank 1 - Read Byte 2
Endpoint FIFO Bank 1 - Read Byte m
Clear RXOUTB1
RXOUTB0
Endpoint FIFO Bank 0 - Read Byte 1
Endpoint FIFO Bank 0 - Read Byte 2
Endpoint FIFO Bank 0 - Read Byte p
Clear RXOUTB0
An endpoint will be first enabled and configured before being able to receive Bulk or
Interrupt packets.
When a valid OUT packet is received on the endpoint bank 0, the RXOUTB0 bit is set by
the USB controller. This triggers an interrupt if enabled. The firmware has to select the
corresponding endpoint, store the number of data bytes by reading the UBYCTLX and
UBYCTHX registers. If the received packet is a ZLP (Zero Length Packet), the
UBYCTLX and UBYCTHX register values are equal to 0 and no data has to be read.
When all the endpoint FIFO bytes have been read, the firmware will clear the RXOUB0
bit to allow the USB controller to accept the next OUT packet on the endpoint bank 0.
This action switches the endpoint bank 0 and 1. Until the RXOUTB0 bit has been
cleared by the firmware, the USB controller will answer a NAK handshake for each OUT
requests on the bank 0 endpoint FIFO.
When a new valid OUT packet is received on the endpoint bank 1, the RXOUTB1 bit is
set by the USB controller. This triggers an interrupt if enabled. The firmware empties the
bank 1 endpoint FIFO before clearing the RXOUTB1 bit. Until the RXOUTB1 bit has
been cleared by the firmware, the USB controller will answer a NAK handshake for each
OUT requests on the bank 1 endpoint FIFO.
The RXOUTB0 and RXOUTB1 bits are alternatively set by the USB controller at each
new valid packet receipt.
The firmware has to clear one of these two bits after having read all the data FIFO to
allow a new valid packet to be stored in the corresponding bank.
A NAK handshake is sent by the USB controller only if the banks 0 and 1 has not been
released by the firmware.
If the Host sends more bytes than supported by the endpoint FIFO, the overflow data
won’t be stored, but the USB controller will consider that the packet is valid if the CRC is
correct.
122
AT89C5131
4136B–USB–09/03
AT89C5131
Bulk/Interrupt IN Transactions
in Standard Mode
Figure 61. Bulk/Interrupt IN Transactions in Standard Mode
UFI
HOST
C51
Endpoint FIFO Write Byte 1
IN
Endpoint FIFO Write Byte 2
NAK
Endpoint FIFO Write Byte n
Set TXRDY
IN
DATA0 (n Bytes)
ACK
TXCMPL
Clear TXCMPL
Endpoint FIFO Write Byte 1
An endpoint will be first enabled and configured before being able to send Bulk or Interrupt packets.
The firmware will fill the FIFO with the data to be sent and set the TXRDY bit in the UEPSTAX register to allow the USB controller to send the data stored in FIFO at the next IN
request concerning this endpoint. To send a Zero Length Packet, the firmware will set
the TXRDY bit without writing any data into the endpoint FIFO.
Until the TXRDY bit has been set by the firmware, the USB controller will answer a NAK
handshake for each IN requests.
To cancel the sending of this packet, the firmware has to reset the TXRDY bit. The
packet stored in the endpoint FIFO is then cleared and a new packet can be written and
sent.
When the IN packet has been sent and acknowledged by the Host, the TXCMPL bit in
the UEPSTAX register is set by the USB controller. This triggers a USB interrupt if
enabled. The firmware will clear the TXCMPL bit before filling the endpoint FIFO with
new data.
The firmware will never write more bytes than supported by the endpoint FIFO.
All USB retry mechanisms are automatically managed by the USB controller.
123
4136B–USB–09/03
Bulk/Interrupt IN Transactions
in Ping-pong Mode
Figure 62. Bulk/Interrupt IN Transactions in Ping-pong Mode
HOST
UFI
C51
Endpoint FIFO Bank 0 - Write Byte 1
IN
Endpoint FIFO Bank 0 - Write Byte 2
NACK
Endpoint FIFO Bank 0 - Write Byte n
Set TXRDY
IN
Endpoint FIFO Bank 1 - Write Byte 1
DATA0 (n Bytes)
Endpoint FIFO Bank 1 - Write Byte 2
ACK
Endpoint FIFO Bank 1 - Write Byte m
TXCMPL
Clear TXCMPL
Set TXRDY
IN
DATA1 (m Bytes)
Endpoint FIFO Bank 0 - Write Byte 1
Endpoint FIFO Bank 0 - Write Byte 2
ACK
Endpoint FIFO Bank 0 - Write Byte p
TXCMPL
Clear TXCMPL
Set TXRDY
IN
DATA0 (p Bytes)
Endpoint FIFO Bank 1 - Write Byte 1
ACK
An endpoint will be first enabled and configured before being able to send Bulk or Interrupt packets.
The firmware will fill the FIFO bank 0 with the data to be sent and set the TXRDY bit in
the UEPSTAX register to allow the USB controller to send the data stored in FIFO at the
next IN request concerning the endpoint. The FIFO banks are automatically switched,
and the firmware can immediately write into the endpoint FIFO bank 1.
When the IN packet concerning the bank 0 has been sent and acknowledged by the
Host, the TXCMPL bit is set by the USB controller. This triggers a USB interrupt if
enabled. The firmware will clear the TXCMPL bit before filling the endpoint FIFO bank 0
with new data. The FIFO banks are then automatically switched.
When the IN packet concerning the bank 1 has been sent and acknowledged by the
Host, the TXCMPL bit is set by the USB controller. This triggers a USB interrupt if
enabled. The firmware will clear the TXCMPL bit before filling the endpoint FIFO bank 1
with new data.
The bank switch is performed by the USB controller each time the TXRDY bit is set by
the firmware. Until the TXRDY bit has been set by the firmware for an endpoint bank,
the USB controller will answer a NAK handshake for each IN requests concerning this
bank.
Note that in the example above, the firmware clears the Transmit Complete bit (TXCMPL) before setting the Transmit Ready bit (TXRDY). This is done in order to avoid the
firmware to clear at the same time the TXCMPL bit for bank 0 and the bank 1.
The firmware will never write more bytes than supported by the endpoint FIFO.
124
AT89C5131
4136B–USB–09/03
AT89C5131
Control Transactions
Setup Stage
The DIR bit in the UEPSTAX register will be at 0.
Receiving Setup packets is the same as receiving Bulk Out packets, except that the
RXSETUP bit in the UEPSTAX register is set by the USB controller instead of the
RXOUTB0 bit to indicate that an Out packet with a Setup PID has been received on the
Control endpoint. When the RXSETUP bit has been set, all the other bits of the UEPSTAX register are cleared and an interrupt is triggered if enabled.
The firmware has to read the Setup request stored in the Control endpoint FIFO before
clearing the RXSETUP bit to free the endpoint FIFO for the next transaction.
Data Stage: Control Endpoint
Direction
The data stage management is similar to Bulk management.
A Control endpoint is managed by the USB controller as a full-duplex endpoint: IN and
OUT. All other endpoint types are managed as half-duplex endpoint: IN or OUT. The
firmware has to specify the control endpoint direction for the data stage using the DIR bit
in the UEPSTAX register.
The firmware has to use the DIR bit before data IN in order to meet the data-toggle
requirements:
•
If the data stage consists of INs,
the firmware has to set the DIR bit in the UEPSTAX register before writing into the
FIFO and sending the data by setting to 1 the TXRDY bit in the UEPSTAX register.
The IN transaction is complete when the TXCMPL has been set by the hardware.
The firmware will clear the TXCMPL bit before any other transaction.
•
If the data stage consists of OUTs,
the firmware has to leave the DIR bit at 0. The RXOUTB0 bit is set by hardware
when a new valid packet has been received on the endpoint. The firmware must
read the data stored into the FIFO and then clear the RXOUTB0 bit to reset the
FIFO and to allow the next transaction.
To send a STALL handshake, see “STALL Handshake” on page 128.
Status Stage
The DIR bit in the UEPSTAX register will be reset at 0 for IN and OUT status stage.
The status stage management is similar to Bulk management.
•
For a Control Write transaction or a No-Data Control transaction, the status stage
consists of a IN Zero Length Packet (see “Bulk/Interrupt IN Transactions in
Standard Mode” on page 123). To send a STALL handshake, see “STALL
Handshake” on page 128.
•
For a Control Read transaction, the status stage consists of a OUT Zero Length
Packet (see “Bulk/Interrupt OUT Transactions in Standard Mode” on page 121).
125
4136B–USB–09/03
Isochronous Transactions
Isochronous OUT
Transactions in Standard
Mode
An endpoint will be first enabled and configured before being able to receive Isochronous packets.
When a OUT packet is received on an endpoint, the RXOUTB0 bit is set by the USB
controller. This triggers an interrupt if enabled. The firmware has to select the corresponding endpoint, store the number of data bytes by reading the UBYCTLX and
UBYCTHX registers. If the received packet is a ZLP (Zero Length Packet), the
UBYCTLX and UBYCTHX register values are equal to 0 and no data has to be read.
The STLCRC bit in the UEPSTAX register is set by the USB controller if the packet
stored in FIFO has a corrupted CRC. This bit is updated after each new packet receipt.
When all the endpoint FIFO bytes have been read, the firmware will clear the RXOUTB0
bit to allow the USB controller to store the next OUT packet data into the endpoint FIFO.
Until the RXOUTB0 bit has been cleared by the firmware, the data sent by the Host at
each OUT transaction will be lost.
If the RXOUTB0 bit is cleared while the Host is sending data, the USB controller will
store only the remaining bytes into the FIFO.
If the Host sends more bytes than supported by the endpoint FIFO, the overflow data
won’t be stored, but the USB controller will consider that the packet is valid if the CRC is
correct.
Isochronous OUT
Transactions in Ping-pong
Mode
An endpoint will be first enabled and configured before being able to receive Isochronous packets.
When a OUT packet is received on the endpoint bank 0, the RXOUTB0 bit is set by the
USB controller. This triggers an interrupt if enabled. The firmware has to select the corresponding endpoint, store the number of data bytes by reading the UBYCTLX and
UBYCTHX registers. If the received packet is a ZLP (Zero Length Packet), the
UBYCTLX and UBYCTHX register values are equal to 0 and no data has to be read.
The STLCRC bit in the UEPSTAX register is set by the USB controller if the packet
stored in FIFO has a corrupted CRC. This bit is updated after each new packet receipt.
When all the endpoint FIFO bytes have been read, the firmware will clear the RXOUB0
bit to allow the USB controller to store the next OUT packet data into the endpoint FIFO
bank 0. This action switches the endpoint bank 0 and 1. Until the RXOUTB0 bit has
been cleared by the firmware, the data sent by the Host on the bank 0 endpoint FIFO
will be lost.
If the RXOUTB0 bit is cleared while the Host is sending data on the endpoint bank 0, the
USB controller will store only the remaining bytes into the FIFO.
When a new OUT packet is received on the endpoint bank 1, the RXOUTB1 bit is set by
the USB controller. This triggers an interrupt if enabled. The firmware empties the bank
1 endpoint FIFO before clearing the RXOUTB1 bit. Until the RXOUTB1 bit has been
cleared by the firmware, the data sent by the Host on the bank 1 endpoint FIFO will be
lost.
The RXOUTB0 and RXOUTB1 bits are alternatively set by the USB controller at each
new packet receipt.
The firmware has to clear one of these two bits after having read all the data FIFO to
allow a new packet to be stored in the corresponding bank.
126
AT89C5131
4136B–USB–09/03
AT89C5131
If the Host sends more bytes than supported by the endpoint FIFO, the overflow data
won’t be stored, but the USB controller will consider that the packet is valid if the CRC is
correct.
Isochronous IN Transactions
in Standard Mode
An endpoint will be first enabled and configured before being able to send Isochronous
packets.
The firmware will fill the FIFO with the data to be sent and set the TXRDY bit in the UEPSTAX register to allow the USB controller to send the data stored in FIFO at the next IN
request concerning this endpoint.
If the TXRDY bit is not set when the IN request occurs, nothing will be sent by the USB
controller.
When the IN packet has been sent, the TXCMPL bit in the UEPSTAX register is set by
the USB controller. This triggers a USB interrupt if enabled. The firmware will clear the
TXCMPL bit before filling the endpoint FIFO with new data.
The firmware will never write more bytes than supported by the endpoint FIFO
Isochronous IN Transactions
in Ping-pong Mode
An endpoint will be first enabled and configured before being able to send Isochronous
packets.
The firmware will fill the FIFO bank 0 with the data to be sent and set the TXRDY bit in
the UEPSTAX register to allow the USB controller to send the data stored in FIFO at the
next IN request concerning the endpoint. The FIFO banks are automatically switched,
and the firmware can immediately write into the endpoint FIFO bank 1.
If the TXRDY bit is not set when the IN request occurs, nothing will be sent by the USB
controller.
When the IN packet concerning the bank 0 has been sent, the TXCMPL bit is set by the
USB controller. This triggers a USB interrupt if enabled. The firmware will clear the TXCMPL bit before filling the endpoint FIFO bank 0 with new data. The FIFO banks are then
automatically switched.
When the IN packet concerning the bank 1 has been sent, the TXCMPL bit is set by the
USB controller. This triggers a USB interrupt if enabled. The firmware will clear the TXCMPL bit before filling the endpoint FIFO bank 1 with new data.
The bank switch is performed by the USB controller each time the TXRDY bit is set by
the firmware. Until the TXRDY bit has been set by the firmware for an endpoint bank,
the USB controller won’t send anything at each IN requests concerning this bank.
The firmware will never write more bytes than supported by the endpoint FIFO.
127
4136B–USB–09/03
Miscellaneous
USB Reset
The EORINT bit in the USBINT register is set by hardware when a End Of Reset has
been detected on the USB bus. This triggers a USB interrupt if enabled. The USB controller is still enabled, but all the USB registers are reset by hardware. The firmware will
clear the EORINT bit to allow the next USB reset detection.
STALL Handshake
This function is only available for Control, Bulk, and Interrupt endpoints.
The firmware has to set the STALLRQ bit in the UEPSTAX register to send a STALL
handshake at the next request of the Host on the endpoint selected with the UEPNUM
register. The RXSETUP, TXRDY, TXCMPL, RXOUTB0 and RXOUTB1 bits must be first
reset to 0. The bit STLCRC is set at 1 by the USB controller when a STALL has been
sent. This triggers an interrupt if enabled.
The firmware will clear the STALLRQ and STLCRC bits after each STALL sent.
The STALLRQ bit is cleared automatically by hardware when a valid SETUP PID is
received on a CONTROL type endpoint.
Important note: when a Clear Halt Feature occurs for an endpoint, the firmware will reset
this endpoint using the UEPRST register in order to reset the data toggle management.
Start of Frame Detection
The SOFINT bit in the USBINT register is set when the USB controller detects a Start of
Frame PID. This triggers an interrupt if enabled. The firmware will clear the SOFINT bit
to allow the next Start of Frame detection.
Frame Number
When receiving a Start of Frame, the frame number is automatically stored in the
UFNUML and UFNUMH registers. The CRCOK and CRCERR bits indicate if the CRC of
the last Start of Frame is valid (CRCOK set at 1) or corrupted (CRCERR set at 1). The
UFNUML and UFNUMH registers are automatically updated when receiving a new Start
of Frame.
Data Toggle Bit
The Data Toggle bit is set by hardware when a DATA0 packet is received and accepted
by the USB controller and cleared by hardware when a DATA1 packet is received and
accepted by the USB controller. This bit is reset when the firmware resets the endpoint
FIFO using the UEPRST register.
For Control endpoints, each SETUP transaction starts with a DATA0 and data toggling
is then used as for Bulk endpoints until the end of the Data stage (for a control write
transfer). The Status stage completes the data transfer with a DATA1 (for a control read
transfer).
For Isochronous endpoints, the device firmware will ignore the data-toggle.
128
AT89C5131
4136B–USB–09/03
AT89C5131
Suspend/Resume Management
Suspend
The Suspend state can be detected by the USB controller if all the clocks are enabled
and if the USB controller is enabled. The bit SPINT is set by hardware when an idle
state is detected for more than 3 ms. This triggers a USB interrupt if enabled.
In order to reduce current consumption, the firmware can put the USB PAD in idle mode,
stop the clocks and put the C51 in Idle or Power-down mode. The Resume detection is
still active.
The USB PAD is put in idle mode when the firmware clear the SPINT bit. In order to
avoid a new suspend detection 3ms later, the firmware has to disable the USB clock
input using the SUSPCLK bit in the USBCON Register. The USB PAD automatically
exits of idle mode when a wake-up event is detected.
The stop of the 48 MHz clock from the PLL should be done in the following order:
1. Disable of the 48 MHz clock input of the USB controller by setting to 1 the SUSPCLK bit in the USBCON register.
2. Disable the PLL by clearing the PLLEN bit in the PLLCON register.
Resume
When the USB controller is in Suspend state, the Resume detection is active even if all
the clocks are disabled and if the C51 is in Idle or Power-down mode. The WUPCPU bit
is set by hardware when a non-idle state occurs on the USB bus. This triggers an interrupt if enabled. This interrupt wakes up the CPU from its Idle or Power-down state and
the interrupt function is then executed. The firmware will first enable the 48 MHz generation and then reset to 0 the SUSPCLK bit in the USBCON register if needed.
The firmware has to clear the SPINT bit in the USBINT register before any other USB
operation in order to wake up the USB controller from its Suspend mode.
The USB controller is then re-activated.
Figure 63. Example of a Suspend/Resume Management
USB Controller Init
SPINT
Detection of a SUSPEND State
Clear SPINT
Set SUSPCLK
Disable PLL
microcontroller in Power-down
WUPCPU
Detection of a RESUME State
Enable PLL
Clear SUSPCLK
Clear WUPCPU Bit
129
4136B–USB–09/03
Upstream Resume
A USB device can be allowed by the Host to send an upstream resume for Remote
Wake Up purpose.
When the USB controller receives the SET_FEATURE request:
DEVICE_REMOTE_WAKEUP, the firmware will set to 1 the RMWUPE bit in the USBCON register to enable this functionality. RMWUPE value will be 0 in the other cases.
If the device is in SUSPEND mode, the USB controller can send an upstream resume by
clearing first the SPINT bit in the USBINT register and by setting then to 1 the SDRMWUP bit in the USBCON register. The USB controller sets to 1 the UPRSM bit in the
USBCON register. All clocks must be enabled first. The Remote Wake is sent only if the
USB bus was in Suspend state for at least 5 ms. When the upstream resume is completed, the UPRSM bit is reset to 0 by hardware. The firmware will then clear the
SDRMWUP bit.
Figure 64. Example of REMOTE WAKEUP Management
USB Controller Init
SET_FEATURE: DEVICE_REMOTE_WAKEUP
Set RMWUPE
SPINT
Detection of a SUSPEND State
Suspend Management
Need USB Resume
Enable Clocks
Clear SPINT
UPRSM = 1
Set SDMWUP
UPRSM
Upstream RESUME Sent
Clear SDRMWUP
130
AT89C5131
4136B–USB–09/03
AT89C5131
Detach Simulation
In order to be re-enumerated by the Host, the AT89C5131 has the possibility to simulate
a DETACH - ATTACH of the USB bus.
The VREF output voltage is between 3.0V and 3.6V. This output can be connected to the
D+ pull-up as shown in Figure 65. This output can be put in high-impedance when the
DETACH bit is set to 1 in the USBCON register. Maintaining this output in high impedance for more than 3 µs will simulate the disconnection of the device. When resetting
the DETACH bit, an attach is then simulated.
Figure 65. Example of VREF Connection
VREF
1.5 kΩ
1
2
DD+
3
4
AT89C5131
VCC
DD+
GND
USB-B Connector
Figure 66. Disconnect Timing
D+
VIHZ(min)
VIL
D-
VSS
> = 2,5 µs
Disconnect
Detected
Device
Disconnected
USB Interrupt System
Interrupt System Priorities
D+
D-
Figure 67. USB Interrupt Control System
00
01
10
11
USB
Controller
EUSB
EA
IE1.6
IE0.7
Interrupt Enable
IPH/L
Priority Enable
Lowest Priority Interrupts
131
4136B–USB–09/03
Table 89. Priority Levels
USB Interrupt Control System
132
IPHUSB
IPLUSB
USB Priority Level
0
0
0
0
1
1
1
0
2
1
1
3
Lowest
Highest
As shown in Figure 68, many events can produce a USB interrupt:
•
TXCMPL: Transmitted In Data (see Table 96 on page 139). This bit is set by
hardware when the Host accept a In packet.
•
RXOUTB0: Received Out Data Bank 0 (see Table 96 on page 139). This bit is set
by hardware when an Out packet is accepted by the endpoint and stored in bank 0.
•
RXOUTB1: Received Out Data Bank 1 (only for Ping-pong endpoints) (see Table 96
on page 139). This bit is set by hardware when an Out packet is accepted by the
endpoint and stored in bank 1.
•
RXSETUP: Received Setup (see Table 96 on page 139). This bit is set by hardware
when an SETUP packet is accepted by the endpoint.
•
STLCRC: STALLED (only for Control, Bulk and Interrupt endpoints) (see Table 96
on page 139). This bit is set by hardware when a STALL handshake has been sent
as requested by STALLRQ, and is reset by hardware when a SETUP packet is
received.
•
SOFINT: Start of Frame Interrupt (See “USBIEN Register USBIEN (S:BEh) USB
Global Interrupt Enable Register” on page 136). This bit is set by hardware when a
USB Start of Frame packet has been received.
•
WUPCPU: Wake-Up CPU Interrupt (See “USBIEN Register USBIEN (S:BEh) USB
Global Interrupt Enable Register” on page 136). This bit is set by hardware when a
USB resume is detected on the USB bus, after a SUSPEND state.
•
SPINT: Suspend Interrupt (See “USBIEN Register USBIEN (S:BEh) USB Global
Interrupt Enable Register” on page 136). This bit is set by hardware when a USB
suspend is detected on the USB bus.
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 68. USB Interrupt Control Block Diagram
Endpoint X (X = 0..6)
TXCMP
UEPSTAX.0
RXOUTB0
UEPSTAX.1
EPXINT
UEPINT.X
RXOUTB1
UEPSTAX.6
EPXIE
UEPIEN.X
RXSETUP
UEPSTAX.2
STLCRC
UEPSTAX.3
WUPCPU
USBINT.5
EWUPCPU
USBIEN.5
EUSB
IE1.6
EORINT
USBINT.4
EEORINT
USBIEN.4
SOFINT
USBINT.3
ESOFINT
USBIEN.3
SPINT
USBINT.0
ESPINT
USBIEN.0
133
4136B–USB–09/03
USB Registers
Table 90. USBCON Register
USBCON (S:BCh)
USB Global Control Register
7
6
5
4
3
2
1
0
USBE
SUSPCLK
SDRMWUP
DETACH
UPRSM
RMWUPE
CONFG
FADDEN
Bit Number
7
6
5
4
3
2
Bit Mnemonic
Description
USBE
USB Enable
Set this bit to enable the USB controller.
Clear this bit to disable and reset the USB controller, to disable the USB
transceiver an to disable the USB controller clock inputs.
SUSPCLK
Suspend USB Clock
Set this bit to disable the 48 MHz clock input (Resume Detection is still
active).
Clear this bit to enable the 48 MHz clock input.
SDRMWUP
Send Remote Wake Up
Set this bit to force an external interrupt on the USB controller for Remote
Wake UP purpose.
An upstream resume is send only if the bit RMWUPE is set, all USB clocks
are enabled AND the USB bus was in SUSPEND state for at least 5 ms.
See UPRSM below.
This bit is cleared by software.
DETACH
Detach Command
Set this bit to simulate a Detach on the USB line. The VREF pin is then in a
floating state.
Clear this bit to maintain VREF at 3.3V.
UPRSM
Upstream Resume (read only)
This bit is set by hardware when SDRMWUP has been set and if RMWUPE
is enabled.
This bit is cleared by hardware after the upstream resume has been sent.
RMWUPE
Remote Wake-Up Enable
Set this bit to enabled request an upstream resume signaling to the host.
Clear this bit otherwise.
Note: Do not set this bit if the host has not set the
DEVICE_REMOTE_WAKEUP feature for the device.
1
0
CONFG
Configured
This bit will be set by the device firmware after a SET_CONFIGURATION
request with a non-zero value has been correctly processed.
It will be cleared by the device firmware when a SET_CONFIGURATION
request with a zero value is received. It is cleared by hardware on hardware
reset or when an USB reset is detected on the bus (SE0 state for at least 32
Full Speed bit times: typically 2.7 µs).
FADDEN
Function Address Enable
This bit will be set by the device firmware after a successful status phase of
a SET_ADDRESS transaction.
It will not be cleared afterwards by the device firmware. It is cleared by
hardware on hardware reset or when an USB reset is received (see above).
When this bit is cleared, the default function address is used (0).
Reset Value = 00h
134
AT89C5131
4136B–USB–09/03
AT89C5131
Table 91. USBINT Register
USBINT (S:BDh)
USB Global Interrupt Register
7
6
5
4
3
2
1
0
-
-
WUPCPU
EORINT
SOFINT
-
-
SPINT
Bit
Bit Number Mnemonic Description
7-6
-
Reserved
The value read from these bits is always 0. Do not set these bits.
5
Wake Up CPU Interrupt
This bit is set by hardware when the USB controller is in SUSPEND state and is
re-activated by a non-idle signal FROM USB line (not by an upstream resume).
WUPCPU
This triggers a USB interrupt when EWUPCPU is set in Figure 92 on page 136.
When receiving this interrupt, user has to enable all USB clock inputs.
This bit will be cleared by software (USB clocks must be enabled before).
4
EORINT
End Of Reset Interrupt
This bit is set by hardware when a End Of Reset has been detected by the USB
controller. This triggers a USB interrupt when EEORINT is set in the Figure 92
(see Figure 92 on page 136).
This bit will be cleared by software.
3
SOFINT
Start of Frame Interrupt
This bit is set by hardware when an USB Start of Frame PID (SOF) has been
detected. This triggers a USB interrupt when ESOFINT is set in the Figure 92
(see Figure 92 on page 136).
This bit will be cleared by software.
2
-
Reserved
The value read from this bit is always 0. Do not set this bit.
1
-
Reserved
The value read from this bit is always 0. Do not set this bit.
0
SPINT
Suspend Interrupt
This bit is set by hardware when a USB Suspend (Idle bus for three frame
periods: a J state for 3 ms) is detected. This triggers a USB interrupt when
ESPINT is set in see Figure 92 on page 136.
This bit will be cleared by software BEFORE any other USB operation to reactivate the macro.
Reset Value = 00h
135
4136B–USB–09/03
Table 92. USBIEN Register
USBIEN (S:BEh)
USB Global Interrupt Enable Register
7
6
5
4
3
2
1
0
-
-
EWUPCPU
EEORINT
ESOFINT
-
-
ESPINT
Bit Number Bit Mnemonic Description
7-6
5
Reserved
The value read from these bits is always 0. Do not set these bits.
-
EWUPCPU
Enable Wake Up CPU Interrupt
Set this bit to enable Wake Up CPU Interrupt. (See “USBIEN Register
USBIEN (S:BEh) USB Global Interrupt Enable Register” on page 136)
Clear this bit to disable Wake Up CPU Interrupt.
4
EEOFINT
Enable End Of Reset Interrupt
Set this bit to enable End Of Reset Interrupt. (See “USBIEN Register USBIEN
(S:BEh) USB Global Interrupt Enable Register” on page 136). This bit is set
after reset.
Clear this bit to disable End Of Reset Interrupt.
3
ESOFINT
Enable SOF Interrupt
Set this bit to enable SOF Interrupt. (See “USBIEN Register USBIEN (S:BEh)
USB Global Interrupt Enable Register” on page 136).
Clear this bit to disable SOF Interrupt.
2
-
Reserved
The value read from this bit is always 0. Do not set this bit.
1
-
Reserved
The value read from this bit is always 0. Do not set this bit.
0
ESPINT
Enable Suspend Interrupt
Set this bit to enable Suspend Interrupts (see the “USBIEN Register USBIEN
(S:BEh) USB Global Interrupt Enable Register” on page 136).
Clear this bit to disable Suspend Interrupts.
Reset Value = 10h
Table 93. USBADDR Register
USBADDR (S:C6h)
USB Address Register
7
6
5
4
3
2
1
0
FEN
UADD6
UADD5
UADD4
UADD3
UADD2
UADD1
UADD0
Bit
Bit Number Mnemonic Description
7
6-0
FEN
Function Enable
Set this bit to enable the function. FADD is reset to 1.
Cleared this bit to disable the function.
USB Address
This field contains the default address (0) after power-up or USB bus reset.
UADD[6:0]
It will be written with the value set by a SET_ADDRESS request received by the
device firmware.
Reset Value = 80h
136
AT89C5131
4136B–USB–09/03
AT89C5131
Table 94. UEPNUM Register
UEPNUM (S:C7h)
USB Endpoint Number
7
6
5
4
3
2
1
0
-
-
-
-
EPNUM3
EPNUM2
EPNUM1
EPNUM0
Bit Number
Bit Mnemonic
7-4
-
3-0
EPNUM[3:0]
Description
Reserved
The value read from these bits is always 0. Do not set these bits.
Endpoint Number
Set this field with the number of the endpoint which will be accessed when
reading or writing to, UEPDATX Register UEPDATX (S:CFh) USB FIFO Data
Endpoint X (X = EPNUM set in UEPNUM Register UEPNUM (S:C7h) USB
Endpoint Number), UBYCTLX Register UBYCTLX (S:E2h) USB Byte Count
Low Register X (X = EPNUM set in UEPNUM Register UEPNUM (S:C7h)
USB Endpoint Number), UBYCTHX Register UBYCTHX (S:E3h) USB Byte
Count High Register X (X = EPNUM set in UEPNUM Register UEPNUM
(S:C7h) USB Endpoint Number) or UEPCONX Register UEPCONX (S:D4h)
USB Endpoint X Control Register. This value can be 0, 1, 2, 3, 4, 5 or 6.
Reset Value = 00h
137
4136B–USB–09/03
Table 95. UEPCONX Register
UEPCONX (S:D4h)
USB Endpoint X Control Register
7
6
5
4
3
2
1
0
EPEN
-
-
-
DTGL
EPDIR
EPTYPE1
EPTYPE0
Bit Number
Description
Endpoint Enable
Set this bit to enable the endpoint according to the device configuration.
Endpoint 0 will always be enabled after a hardware or USB bus reset and
participate in the device configuration.
Clear this bit to disable the endpoint according to the device configuration.
7
EPEN
6
-
Reserved
The value read from this bit is always 0. Do not set this bit.
5
-
Reserved
The value read from this bit is always 0. Do not set this bit.
4
-
Reserved
The value read from this bit is always 0. Do not set this bit.
3
2
1-0
Note:
Bit
Mnemonic
DTGL
Data Toggle (Read-only)
This bit is set by hardware when a valid DATA0 packet is received and
accepted.
This bit is cleared by hardware when a valid DATA1 packet is received and
accepted.
EPDIR
Endpoint Direction
Set this bit to configure IN direction for Bulk, Interrupt and Isochronous
endpoints.
Clear this bit to configure OUT direction for Bulk, Interrupt and Isochronous
endpoints.
This bit has no effect for Control endpoints.
Endpoint Type
Set this field according to the endpoint configuration (Endpoint 0 will always be
configured as control):
EPTYPE[1:0] 00Control endpoint
01Isochronous endpoint
10Bulk endpoint
11Interrupt endpoint
1. (X = EPNUM set in UEPNUM Register UEPNUM (S:C7h) USB Endpoint Number)
Reset Value = 80h when UEPNUM = 0
Reset Value = 00h otherwise
138
AT89C5131
4136B–USB–09/03
AT89C5131
Table 96. UEPSTAX (S:CEh) USB Endpoint X Status Register
7
6
5
4
3
2
1
0
DIR
RXOUTB1
STALLRQ
TXRDY
STL/CRC
RXSETUP
RXOUTB0
TXCMP
Bit Number
Bit
Mnemonic
Description
DIR
Control Endpoint Direction
This bit is used only if the endpoint is configured in the control type (seeSection “UEPCONX Register UEPCONX (S:D4h)
USB Endpoint X Control Register”).
This bit determines the Control data and status direction.
The device firmware will set this bit ONLY for the IN data stage, before any other USB operation. Otherwise, the device
firmware will clear this bit.
6
RXOUTB1
Received OUT Data Bank 1 for Endpoints 4, 5 and 6 (Ping-pong mode)
This bit is set by hardware after a new packet has been stored in the endpoint FIFO data bank 1 (only in Ping-pong mode).
Then, the endpoint interrupt is triggered if enabled (see“UEPINT Register UEPINT (S:F8h read-only) USB Endpoint
Interrupt Register” on page 143) and all the following OUT packets to the endpoint bank 1 are rejected (NAK’ed) until this
bit has been cleared, excepted for Isochronous Endpoints.
This bit will be cleared by the device firmware after reading the OUT data from the endpoint FIFO.
5
STALLRQ
Stall Handshake Request
Set this bit to request a STALL answer to the host for the next handshake.Clear this bit otherwise.
For CONTROL endpoints: cleared by hardware when a valid SETUP PID is received.
7
4
3
2
1
0
TXRDY
TX Packet Ready
Set this bit after a packet has been written into the endpoint FIFO for IN data transfers. Data will be written into the
endpoint FIFO only after this bit has been cleared. Set this bit without writing data to the endpoint FIFO to send a Zero
Length Packet.
This bit is cleared by hardware, as soon as the packet has been sent for Isochronous endpoints, or after the host has
acknowledged the packet for Control, Bulk and Interrupt endpoints. When this bit is cleared, the endpoint interrupt is
triggered if enabled (see“UEPINT Register UEPINT (S:F8h read-only) USB Endpoint Interrupt Register” on page 143).
STLCRC
Stall Sent/CRC error flag
- For Control, Bulk and Interrupt Endpoints:
This bit is set by hardware after a STALL handshake has been sent as requested by STALLRQ. Then, the endpoint
interrupt is triggered if enabled (see“UEPINT Register UEPINT (S:F8h read-only) USB Endpoint Interrupt Register” on
page 143)
It will be cleared by the device firmware.
- For Isochronous Endpoints (Read-Only):
This bit is set by hardware if the last received data is corrupted (CRC error on data).
This bit is updated by hardware when a new data is received.
RXSETUP
Received SETUP
This bit is set by hardware when a valid SETUP packet has been received from the host. Then, all the other bits of the
register are cleared by hardware and the endpoint interrupt is triggered if enabled (see“UEPINT Register UEPINT (S:F8h
read-only) USB Endpoint Interrupt Register” on page 143).
It will be cleared by the device firmware after reading the SETUP data from the endpoint FIFO.
RXOUTB0
Received OUT Data Bank 0 (see also RXOUTB1 bit for Ping-pong Endpoints)
This bit is set by hardware after a new packet has been stored in the endpoint FIFO data bank 0. Then, the endpoint
interrupt is triggered if enabled (see“UEPINT Register UEPINT (S:F8h read-only) USB Endpoint Interrupt Register” on
page 143) and all the following OUT packets to the endpoint bank 0 are rejected (NAK’ed) until this bit has been cleared,
excepted for Isochronous Endpoints. However, for control endpoints, an early SETUP transaction may overwrite the
content of the endpoint FIFO, even if its Data packet is received while this bit is set.
This bit will be cleared by the device firmware after reading the OUT data from the endpoint FIFO.
TXCMPL
Transmitted IN Data Complete
This bit is set by hardware after an IN packet has been transmitted for Isochronous endpoints and after it has been
accepted (ACK’ed) by the host for Control, Bulk and Interrupt endpoints. Then, the endpoint interrupt is triggered if
enabled (see“UEPINT Register UEPINT (S:F8h read-only) USB Endpoint Interrupt Register” on page 143).
This bit will be cleared by the device firmware before setting TXRDY.
Reset Value = 00h
139
4136B–USB–09/03
Table 97. UEPDATX Register
UEPDATX (S:CFh)
USB FIFO Data Endpoint X (X = EPNUM set in UEPNUM Register UEPNUM (S:C7h)
7
6
5
4
3
2
1
0
FDAT7
FDAT6
FDAT5
FDAT4
FDAT3
FDAT2
FDAT1
FDAT0
Bit
Bit Number Mnemonic Description
Endpoint X FIFO data
7-0
FDAT[7:0] Data byte to be written to FIFO or data byte to be read from the FIFO, for the
Endpoint X (see EPNUM).
USB Endpoint Number)
Reset Value = XXh
Table 98. UBYCTLX Register
UBYCTLX (S:E2h)
USB Byte Count Low Register X (X = EPNUM set in UEPNUM Register UEPNUM
7
6
5
4
3
2
1
0
BYCT7
BYCT6
BYCT5
BYCT4
BYCT3
BYCT2
BYCT1
BYCT0
Bit
Bit Number Mnemonic Description
7-0
Byte Count LSB
Least Significant Byte of the byte count of a received data packet. The most
significant part is provided by the UBYCTHX Register UBYCTHX (S:E3h) USB
BYCT[7:0]
Byte Count High Register X (X = EPNUM set in UEPNUM Register UEPNUM
(S:C7h) USB Endpoint Number) (see Figure 98 on page 140). This byte count is
equal to the number of data bytes received after the Data PID.
(S:C7h) USB Endpoint Number)
Reset Value = 00h
140
AT89C5131
4136B–USB–09/03
AT89C5131
Table 99. UBYCTHX Register
UBYCTHX (S:E3h)
USB Byte Count High Register X (X = EPNUM set in UEPNUM Register UEPNUM
7
6
5
4
3
2
1
0
-
-
-
-
-
-
BYCT9
BYCT8
Bit Number Bit Mnemonic Description
7-2
2-0
-
BYCT[10:8]
Reserved
The value read from these bits is always 0. Do not set these bits.
Byte Count MSB
Most Significant Byte of the byte count of a received data packet. The Least
significant part is provided by UBYCTLX Register UBYCTLX (S:E2h) USB
Byte Count Low Register X (X = EPNUM set in UEPNUM Register UEPNUM
(S:C7h) USB Endpoint Number) (see Figure 98 on page 140).
(S:C7h) USB Endpoint Number)
Reset Value = 00h
141
4136B–USB–09/03
Table 100. UEPRST Register
UEPRST (S:D5h)
USB Endpoint FIFO Reset Register
7
6
5
4
3
2
1
0
-
EP6RST
EP5RST
EP4RST
EP3RST
EP2RST
EP1RST
EP0RST
Bit
Bit Number Mnemonic Description
Reserved
The value read from this bit is always 0. Do not set this bit.
7
-
6
EP6RST
Endpoint 6 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
5
EP5RST
Endpoint 5 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
4
EP4RST
Endpoint 4 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
3
EP3RST
Endpoint 3 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
2
EP2RST
Endpoint 2 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
1
EP1RST
Endpoint 1 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
0
EP0RST
Endpoint 0 FIFO Reset
Set this bit and reset the endpoint FIFO prior to any other operation, upon
hardware reset or when an USB bus reset has been received.
Then, clear this bit to complete the reset operation and start using the FIFO.
Reset Value = 00h
142
AT89C5131
4136B–USB–09/03
AT89C5131
Table 101. UEPINT Register
UEPINT (S:F8h read-only)
USB Endpoint Interrupt Register
7
6
5
4
3
2
1
0
-
EP6INT
EP5INT
EP4INT
EP3INT
EP2INT
EP1INT
EP0INT
Bit
Bit Number Mnemonic Description
7
6
5
4
3
2
1
0
-
Reserved
The value read from this bit is always 0. Do not set this bit.
EP6INT
Endpoint 6 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
EP5INT
Endpoint 5 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
EP4INT
Endpoint 4 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
EP3INT
Endpoint 3 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
EP2INT
Endpoint 2 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
EP1INT
Endpoint 1 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
EP0INT
Endpoint 0 Interrupt
This bit is set by hardware when an interrupt is triggered by the (see Table 96 on
page 139) and this endpoint interrupt is enabled by the UEPIEN Register
UEPIEN (S:C2h) USB Endpoint Interrupt Enable Register (see Figure 102 on
page 144).
This bit is cleared by software.
Reset Value = 00h
143
4136B–USB–09/03
Table 102. UEPIEN Register
UEPIEN (S:C2h)
USB Endpoint Interrupt Enable Register
7
6
5
4
3
2
1
0
-
EP6INTE
EP5INTE
EP4INTE
EP3INTE
EP2INTE
EP1INTE
EP0INTE
Bit
Bit Number Mnemonic Description
Reserved
The value read from this bit is always 0. Do not set this bit.
7
-
6
EP6INTE
Endpoint 6 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
5
EP5INTE
Endpoint 5 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
4
EP4INTE
Endpoint 4 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
3
EP3INTE
Endpoint 3 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
2
EP2INTE
Endpoint 2 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
1
EP1INTE
Endpoint 1 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
0
EP0INTE
Endpoint 0 Interrupt Enable
Set this bit to enable the interrupts for this endpoint.
Clear this bit to disable the interrupts for this endpoint.
Reset Value = 00h
144
AT89C5131
4136B–USB–09/03
AT89C5131
Table 103. UFNUMH Register
UFNUMH (S:BBh, read-only)
USB Frame Number High Register
7
6
5
4
3
2
1
0
-
-
CRCOK
CRCERR
-
FNUM10
FNUM9
FNUM8
Bit
Number
Bit
Mnemonic
Description
CRCOK
Frame Number CRC OK
This bit is set by hardware when a new Frame Number in Start of Frame Packet
is received without CRC error.
This bit is updated after every Start of Frame packet receipt.
Important note: the Start of Frame interrupt is generated just after the PID receipt.
4
CRCERR
Frame Number CRC Error
This bit is set by hardware when a corrupted Frame Number in Start of Frame
packet is received.
This bit is updated after every Start of Frame packet receipt.
Important note: the Start of Frame interrupt is generated just after the PID receipt.
3
-
5
2-0
Reserved
The value read from this bit is always 0. Do not set this bit.
Frame Number
FNUM[10:8] are the upper 3 bits of the 11-bit Frame Number (see the “UFNUML
Register UFNUML (S:BAh, read-only) USB Frame Number Low Register” on
FNUM[10:8]
page 145). It is provided in the last received SOF packet (see SOFINT in the
“USBIEN Register USBIEN (S:BEh) USB Global Interrupt Enable Register” on
page 136). FNUM is updated if a corrupted SOF is received.
Reset Value = 00h
Table 104. UFNUML Register
UFNUML (S:BAh, read-only)
USB Frame Number Low Register
7
6
5
4
3
2
1
0
FNUM7
FNUM6
FNUM5
FNUM4
FNUM3
FNUM2
FNUM1
FNUM0
Bit
Bit Number Mnemonic Description
7-0
Frame Number
FNUM[7:0] are the lower 8 bits of the 11-bit Frame Number (See “UFNUMH
FNUM[7:0]
Register UFNUMH (S:BBh, read-only) USB Frame Number High Register” on
page 145).
Reset Value = 00h
145
4136B–USB–09/03
Power Management
Idle Mode
An instruction that sets PCON.0 indicates that it is the last instruction to be executed
before going into the Idle mode. In the Idle mode, the internal clock signal is gated off to
the CPU, but not to the interrupt, Timer, and Serial Port functions. The CPU status is
preserved in its entirety: the Stack Pointer, Program Counter, Program Status Word,
Accumulator and all other registers maintain their data during Idle. The port pins hold
the logical states they had at the time Idle was activated. ALE and PSEN hold at logic
high level.
There are two ways to terminate the Idle mode. Activation of any enabled interrupt will
cause PCON.0 to be cleared by hardware, terminating the Idle mode. The interrupt will
be serviced, and following RETI the next instruction to be executed will be the one following the instruction that put the device into idle.
The flag bits GF0 and GF1 can be used to give an indication if an interrupt occurred during normal operation or during an Idle. For example, an instruction that activates Idle
can also set one or both flag bits. When Idle is terminated by an interrupt, the interrupt
service routine can examine the flag bits.
The other way of terminating the Idle mode is with a hardware reset. Since the clock
oscillator is still running, the hardware reset needs to be held active for only two
machine cycles (24 oscillator periods) to complete the reset.
Power-down Mode
To save maximum power, a power-down mode can be invoked by software (refer to
Table 13, PCON register).
In power-down mode, the oscillator is stopped and the instruction that invoked powerdown mode is the last instruction executed. The internal RAM and SFRs retain their
value until the power-down mode is terminated. VCC can be lowered to save further
power. Either a hardware reset or an external interrupt can cause an exit from powerdown. To properly terminate power-down, the reset or external interrupt should not be
executed before VCC is restored to its normal operating level and must be held active
long enough for the oscillator to restart and stabilize.
Only:
•
external interrupt INT0,
•
external interrupt INT1,
•
Keyboard interrupt and
•
USB Interrupt
are useful to exit from power-down. For that, interrupt must be enabled and configured
as level or edge sensitive interrupt input. When Keyboard Interrupt occurs after a power
down mode, 1024 clocks are necessary to exit to power-down mode and enter in operating mode.
Holding the pin low restarts the oscillator but bringing the pin high completes the exit as
detailed in Figure 69. When both interrupts are enabled, the oscillator restarts as soon
as one of the two inputs is held low and power-down exit will be completed when the first
input is released. In this case, the higher priority interrupt service routine is executed.
Once the interrupt is serviced, the next instruction to be executed after RETI will be the
one following the instruction that put AT89C5131 into power-down mode.
146
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 69. Power-down Exit Waveform
INT0
INT1
XTALA
or
XTALB
Power-down Phase
Active Phase
Oscillator restart Phase
Active Phase
Exit from power-down by reset redefines all the SFRs, exit from power-down by external
interrupt does no affect the SFRs.
Exit from power-down by either reset or external interrupt does not affect the internal
RAM content.
Note:
If idle mode is activated with power-down mode (IDL and PD bits set), the exit sequence
is unchanged, when execution is vectored to interrupt, PD and IDL bits are cleared and
idle mode is not entered.
This table shows the state of ports during idle and power-down modes.
Table 105. State of Ports
Mode
Program
Memory
ALE
PSEN
PORT0
PORT1
PORT2
PORT3
PORTI2
Idle
Internal
1
1
Port
Data(1)
Port
Data
Port Data
Port Data
Port
Data
Idle
External
1
1
Floating
Port
Data
Address
Port Data
Port
Data
Power-down
Internal
0
0
Port
Data(1)
Port
Data
Port Data
Port Data
Port
Data
Power-down
External
0
0
Floating
Port
Data
Port Data
Port Data
Port
Data
Note:
1. Port 0 can force a 0 level. A “one” will leave port floating.
147
4136B–USB–09/03
Registers
Table 106. PCON Register
PCON (S:87h)
Power Control Register
7
6
5
4
3
2
1
0
SMOD1
SMOD0
-
POF
GF1
GF0
PD
IDL
Bit
Bit Number Mnemonic Description
7
SMOD1
Serial Port Mode bit 1
Set to select double baud rate in mode 1, 2 or 3.
6
SMOD0
Serial Port Mode bit 0
Set to select FE bit in SCON register.
Clear to select SM0 bit in SCON register
5
-
Reserved
The value read from this bit is always 0. Do not set this bit.
4
POF
Power-Off Flag
Set by hardware when VCC rises from 0 to its nominal voltage. Can also be set by
software.
Clear to recognize next reset type.
3
GF1
General-purpose Flag 1
Set by software for general-purpose usage.
Cleared by software for general-purpose usage.
2
GF0
General-purpose Flag 0
Set by software for general-purpose usage.
Cleared by software for general-purpose usage.
1
PD
Power-down mode bit
Set this bit to enter in power-down mode.
Cleared by hardware when reset occurs.
0
IDL
Idle mode bit
Set this bit to enter in Idle mode.
Cleared by hardware when interrupt or reset occurs.
Reset Value = 10h
148
AT89C5131
4136B–USB–09/03
AT89C5131
Hardware Watchdog
Timer
The WDT is intended as a recovery method in situations where the CPU may be subjected to software upset. The WDT consists of a 14-bit counter and the WatchDog Timer
ReSeT (WDTRST) SFR. The WDT is by default disabled from exiting reset. To enable
the WDT, user must write 01EH and 0E1H in sequence to the WDTRST, SFR location
0A6H. When WDT is enabled, it will increment every machine cycle while the oscillator
is running and there is no way to disable the WDT except through reset (either hardware
reset or WDT overflow reset). When WDT overflows, it will drive an output RESET LOW
pulse at the RST-pin.
Using the WDT
To enable the WDT, user must write 01EH and 0E1H in sequence to the WDTRST, SFR
location 0A6H. When WDT is enabled, the user needs to service it by writing to 01EH
and 0E1H to WDTRST to avoid WDT overflow. The 14-bit counter overflows when it
reaches 16383 (3FFFH) and this will reset the device. When WDT is enabled, it will
increment every machine cycle while the oscillator is running. This means the user must
reset the WDT at least every 16383 machine cycle. To reset the WDT the user must
write 01EH and 0E1H to WDTRST. WDTRST is a write only register. The WDT counter
cannot be read or written. When WDT overflows, it will generate an output RESET pulse
at the RST-pin. The RESET pulse duration is 96 x TCLK PERIPH, where TCLK PERIPH =
1/FCLK PERIPH. To make the best use of the WDT, it should be serviced in those sections
of code that will periodically be executed within the time required to prevent a WDT
reset.
To have a more powerful WDT, a 27 counter has been added to extend the Time-out
capability, ranking from 16 ms to 2s at FOSCA = 12 MHz. To manage this feature, refer to
WDTPRG register description, Table 108.
Table 107. WDTRST Register
WDTRST - Watchdog Reset Register (0A6h)
7
6
5
4
3
2
1
0
-
-
-
-
-
-
-
-
Reset Value = XXXX XXXXb
Write only, this SFR is used to reset/enable the WDT by writing 01EH then 0E1H in
sequence.
149
4136B–USB–09/03
Table 108. WDTPRG Register
WDTPRG - Watchdog Timer Out Register (0A7h)
7
6
5
4
3
2
1
0
-
-
-
-
-
S2
S1
S0
Bit
Bit
Number
Mnemonic
7
-
6
-
5
-
4
-
3
-
2
S2
WDT Time-out select bit 2
1
S1
WDT Time-out select bit 1
0
S0
WDT Time-out select bit 0
Description
Reserved
The value read from this bit is undetermined. Do not try to set this bit.
S2
0
0
0
0
1
1
1
1
S1
0
0
1
1
0
0
1
1
S0
0
1
0
1
0
1
0
1
Selected Time-out
(214 - 1) machine cycles, 16.3 ms at FOSCA = 12 MHz
(215 - 1) machine cycles, 32.7 ms at FOSCA = 12 MHz
(216 - 1) machine cycles, 65.5 ms at FOSCA = 12 MHz
(217 - 1) machine cycles, 131 ms at FOSCA = 12 MHz
(218 - 1) machine cycles, 262 ms at FOSCA = 12 MHz
(219 - 1) machine cycles, 542 ms at FOSCA = 12 MHz
(220 - 1) machine cycles, 1.05 s at FOSCA = 12 MHz
(221 - 1) machine cycles, 2.09 s at FOSCA = 12 MHz
Reset value = XXXX X000
WDT During Power-down In Power-down mode the oscillator stops, which means the WDT also stops. While in
Power-down mode the user does not need to service the WDT. There are 2 methods of
and Idle
exiting Power-down mode: by a hardware reset or via a level activated external interrupt
which is enabled prior to entering Power-down mode. When Power-down is exited with
hardware reset, servicing the WDT should occur as it normally should whenever the
AT89C5131 is reset. Exiting Power-down with an interrupt is significantly different. The
interrupt is held low long enough for the oscillator to stabilize. When the interrupt is
brought high, the interrupt is serviced. To prevent the WDT from resetting the device
while the interrupt pin is held low, the WDT is not started until the interrupt is pulled high.
It is suggested that the WDT be reset during the interrupt service routine.
To ensure that the WDT does not overflow within a few states of exiting of power-down,
it is better to reset the WDT just before entering power-down.
In the Idle mode, the oscillator continues to run. To prevent the WDT from resetting the
AT89C5131 while in Idle mode, the user should always set up a timer that will periodically exit Idle, service the WDT, and re-enter Idle mode.
150
AT89C5131
4136B–USB–09/03
AT89C5131
ONCE Mode (ON
Chip Emulation)
The ONCE mode facilitates testing and debugging of systems using AT89C5131 without
removing the circuit from the board. The ONCE mode is invoked by driving certain pins
of the AT89C5131; the following sequence must be exercised:
•
Pull ALE low while the device is in reset (RST high) and PSEN is high.
•
Hold ALE low as RST is deactivated.
While the AT89C5131 is in ONCE mode, an emulator or test CPU can be used to drive
the circuit Table 109 shows the status of the port pins during ONCE mode.
Normal operation is restored when normal reset is applied.
Table 109. External Pin Status during ONCE Mode
ALE
PSEN
Port 0
Port 1
Port 2
Port 3
Port I2
XTALA1/2
XTALB1/2
Weak
pull-up
Weak
pull-up
Float
Weak
pull-up
Weak
pull-up
Weak
pull-up
Float
Active
Active
151
4136B–USB–09/03
Reduced EMI Mode
The ALE signal is used to demultiplex address and data buses on port 0 when used with
external program or data memory. Nevertheless, during internal code execution, ALE
signal is still generated. In order to reduce EMI, ALE signal can be disabled by setting
AO bit.
The AO bit is located in AUXR register at bit location 0. As soon as AO is set, ALE is no
longer output but remains active during MOVX and MOVC instructions and external
fetches. During ALE disabling, ALE pin is weakly pulled high.
Table 110. AUXR Register
AUXR - Auxiliary Register (8Eh)
7
6
5
4
3
2
1
0
DPU
-
M0
-
XRS1
XRS0
EXTRAM
AO
Bit
Bit
Number
Mnemonic
7
DPU
6
-
Description
Disable Weak Pull Up
Cleared to enabled weak pull up on standard Ports
Set to disable weak pull up on standard Ports
Reserved
The value read from this bit is indeterminate. Do not set this bit.
Pulse length
5
M0
Cleared to stretch MOVX control: the RD and the WR pulse length is 6 clock
periods (default).
Set to stretch MOVX control: the RD and the WR pulse length is 30 clock periods.
Reserved
4
-
3
XRS1
ERAM Size
2
XRS0
XRS1
0
0
1
1
1
EXTRAM
The value read from this bit is indeterminate. Do not set this bit.
XRS0
0
1
0
1
ERAM size
256 bytes
512 bytes
768 bytes
1024 bytes (default)
EXTRAM bit
Cleared to access internal ERAM using MOVX at Ri at DPTR.
Set to access external memory.
0
AO
ALE Output bit
Cleared, ALE is emitted at a constant rate of 1/6 the oscillator frequency (or 1/3 if
X2 mode is used) (default).
Set, ALE is active only during a MOVX or MOVC instruction is used.
Reset Value = 0X0X 1100b
Not bit addressable
152
AT89C5131
4136B–USB–09/03
AT89C5131
Electrical Characteristics
Absolute Maximum Ratings
Note:
Ambient Temperature Under Bias:
I = industrial ........................................................-40°C to 85°C
Storage Temperature .................................... -65°C to + 150°C
Voltage on VCC from VSS ...................................-0.5V to + 3.6V
Voltage on Any Pin from VSS .....................-0.5V to VCC + 0.2V
Stresses at or above those listed under “Absolute
Maximum Ratings” may cause permanent damage to
the device. This 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.
DC Parameters for Low Voltage
TA = -40°C to +85°C; VSS = 0V; VCC = 3.3V ± 10%; F = 0 to 40 MHz
Symbol
Parameter
Min
VIL
Input Low Voltage
VIH
Input High Voltage except XTAL1, RST
VIH1
Input High Voltage, XTAL1, RST
VOL
Output Low Voltage, ports 1, 2, 3 and 4(6)
VOL1
VOH
VOH1
RRST
Output Low Voltage, port 0, ALE, PSEN
Typ(5)
Max
Unit
-0.5
0.2Vcc - 0.1
V
0.2 VCC + 0.9
VCC + 0.5
V
0.7 VCC
VCC + 0.5
V
0.3
V
IOL = 100 µA(4)
0.45
V
IOL = 0.8 mA(4)
1.0
V
IOL = 1.6mA(4)
0.3
V
IOL = 200 µA(4)
0.45
V
IOL = 1.6 mA(4)
1.0
V
IOL = 3.5 mA(4)
VCC - 0.3
V
VCC - 0.7
V
IOH = -30 µA
VCC - 1.5
V
VCC - 0.3
V
VCC - 0.7
V
VCC - 1.5
V
(6)
Output High Voltage, ports 1, 2, 3, 4 and 5
Output High Voltage, port 0, ALE, PSEN
RST Pullup Resistor
Test Conditions
50
100
200
kΩ
IOH = -10 µA
IOH = -60 µA
VCC = 3.3V ± 10%
IOH = -200 µA
IOH = -1.6 mA
IOH = -3.5 mA
VCC = 3.3V ± 10%
IIL
Logical 0 Input Current ports 1, 2, 3 and 4
-50
µA
Vin = 0.45V
ILI
Input Leakage Current
±10
µA
0.45V < Vin < VCC
ITL
Logical 1 to 0 Transition Current, ports 1, 2, 3
and 4
-650
µA
Vin = 2.0V
CIO
Capacitance of I/O Buffer
10
pF
Fc = 1 MHz
TA = 25°C
IPD
Power-down Current
100
µA
3.0V < VCC < 3.6V(3)
ICC
VPFDP
Power Supply Current
50
ICCOP = 0.7 Freq (MHz) + 3 mA
VCC = 3.3V (1)(2)
ICCIDLE = 0.6 Freq (MHz) + 2 mA
Power Fail High Level Threshold
3.0
V
153
4136B–USB–09/03
Symbol
VPFDM
Notes:
Parameter
Typ(5)
Min
Max
Unit
Power Fail Low Level Threshold
2.2
V
Power fail hysteresis VPFDP - VPFDM
0.15
V
Test Conditions
1. Operating ICC is measured with all output pins disconnected; XTAL1 driven with TCLCH, TCHCL = 5 ns (see Figure 73.), VIL =
VSS + 0.5V,
VIH = VCC - 0.5V; XTAL2 N.C.; EA = RST = Port 0 = VCC. ICC would be slightly higher if a crystal oscillator used (see Figure
70.).
2. Idle ICC is measured with all output pins disconnected; XTAL1 driven with TCLCH, TCHCL = 5 ns, VIL = VSS + 0.5V, VIH = VCC 0.5V; XTAL2 N.C; Port 0 = VCC; EA = RST = VSS (see Figure 71).
3. Power-down ICC is measured with all output pins disconnected; EA = VCC, PORT 0 = VCC; XTAL2 NC.; RST = VSS (see Figure 72.). In addition, the WDT must be inactive and the POF flag must be set.
4. Capacitance loading on Ports 0 and 2 may cause spurious noise pulses to be superimposed on the VOLS of ALE and Ports 1
and 3. The noise is due to external bus capacitance discharging into the Port 0 and Port 2 pins when these pins make 1 to 0
transitions during bus operation. In the worst cases (capacitive loading 100 pF), the noise pulse on the ALE line may exceed
0.45V with maxi VOL peak 0.6V. A Schmitt Trigger use is not necessary.
5. Typicals are based on a limited number of samples and are not guaranteed. The values listed are at room temperature.
6. Under steady state (non-transient) conditions, IOL must be externally limited as follows:
Maximum IOL per port pin: 10 mA
Maximum IOL per 8-bit port:
Port 0: 26 mA
Ports 1, 2 and 3: 15 mA
Maximum total IOL for all output pins: 71 mA
If IOL exceeds the test condition, VOL may exceed the related specification. Pins are not guaranteed to sink current greater
than the listed test conditions.
Figure 70. ICC Test Condition, Active Mode
VCC
ICC
VCC
VCC
P0
RST
(NC)
CLOCK
SIGNAL
EA
XTAL2
XTAL1
VSS
All other pins are disconnected.
154
AT89C5131
4136B–USB–09/03
AT89C5131
Figure 71. ICC Test Condition, Idle Mode
VCC
ICC
VCC
VCC
P0
VCC
RST
EA
XTAL2
XTAL1
(NC)
CLOCK
SIGNAL
VSS
All other pins are disconnected.
Figure 72. ICC Test Condition, Power-down Mode
VCC
ICC
VCC
VCC
P0
VCC
RST
(NC)
EA
XTAL2
XTAL1
VSS
All other pins are disconnected.
Figure 73. Clock Signal Waveform for ICC Tests in Active and Idle Modes
VCC-0.5V
0.45V
TCLCH
TCHCL
TCLCH = TCHCL = 5ns.
0.7VCC
0.2VCC-0.1
LED’s
Table 111. LED Outputs DC Parameters
Symbol
IOL
Note:
Parameter
Output Low Current, P3.6 and P3.7 LED modes
Min
Typ
Max
Unit
Test Conditions
1
2
4
mA
2 mA configuration
2
4
8
mA
4 mA configuration
5
10
20
mA
10 mA configuration
1. (TA = -20°C to +50°C, VCC - VOL = 2 V ± 20%)
155
4136B–USB–09/03
USB DC Parameters
1 - VBUS
2-D3-D+
4 - GND
R
3
2
USB “B”
Receptacle
VREF
Rpad
Rpad
4
D+
D-
1
R = 1.5 kΩ
Rpad = 27Ω
Symbol
VREF
156
Parameter
Min
USB Reference Voltage
3.0
VIH
Input High Voltage for D+ and D- (Driven)
2.0
VIHZ
Input High Voltage for D+ and D- (Floating)
2.7
VIL
Input Low Voltage for D+ and D-
VOH
Output High Voltage for D+ and D-
VOL
Output Low Voltage for D+ and D-
Typ
Max
Unit
3.6
V
V
3.6
V
0.8
V
2.8
3.6
V
0.0
0.3
V
AT89C5131
4136B–USB–09/03
AT89C5131
AC Parameters
Explanation of the AC
Symbols
Each timing symbol has 5 characters. The first character is always a “T” (stands for
time). The other characters, depending on their positions, stand for the name of a signal
or the logical status of that signal. The following is a list of all the characters and what
they stand for.
Example:TAVLL = Time for Address Valid to ALE Low.
TLLPL = Time for ALE Low to PSEN Low.
TA = -40°C to +85°C; VSS = 0V; VCC = 3.3V ±10%; F = 0 to 40 MHz.
TA = -40°C to +85°C; VSS = 0V; VCC = 3.3V ± 10%.
(Load Capacitance for port 0, ALE and PSEN = 60 pF; Load Capacitance for all other
outputs = 60 pF.)
Table 112, Table 115 and Table 118 give the description of each AC symbols.
Table 113, Table 117 and Table 119 give for each range the AC parameter.
Table 114, Table 117 and Table 120 give the frequency derating formula of the AC
parameter for each speed range description. To calculate each AC symbols. take the x
value and use this value in the formula.
Example: TLLIV and 20 MHz, Standard clock.
x = 30 ns
T = 50 ns
TCCIV = 4T - x = 170 ns
External Program Memory
Characteristics
Table 112. Symbol Description
Symbol
T
Parameter
Oscillator Clock Period
TLHLL
ALE Pulse Width
TAVLL
Address Valid to ALE
TLLAX
Address Hold after ALE
TLLIV
ALE to Valid Instruction In
TLLPL
ALE to PSEN
TPLPH
PSEN Pulse Width
TPLIV
PSEN to Valid Instruction In
TPXIX
Input Instruction Hold after PSEN
TPXIZ
Input Instruction Float after PSEN
TAVIV
Address to Valid Instruction In
TPLAZ
PSEN Low to Address Float
157
4136B–USB–09/03
Table 113. AC Parameters for a Fix Clock (F = 40 MHz)
Symbol
Min
Max
T
25
ns
TLHLL
40
ns
TAVLL
10
ns
TLLAX
10
ns
TLLIV
Units
70
ns
TLLPL
15
ns
TPLPH
55
ns
TPLIV
35
TPXIX
ns
0
ns
TPXIZ
18
ns
TAVIV
85
ns
TPLAZ
10
ns
Table 114. AC Parameters for a Variable Clock
158
Symbol
Type
Standard
Clock
X2 Clock
X Parameter
Units
TLHLL
Min
2T-x
T-x
10
ns
TAVLL
Min
T-x
0.5 T - x
15
ns
TLLAX
Min
T-x
0.5 T - x
15
ns
TLLIV
Max
4T-x
2T-x
30
ns
TLLPL
Min
T-x
0.5 T - x
10
ns
TPLPH
Min
3T-x
1.5 T - x
20
ns
TPLIV
Max
3T-x
1.5 T - x
40
ns
TPXIX
Min
x
x
0
ns
TPXIZ
Max
T-x
0.5 T - x
7
ns
TAVIV
Max
5T-x
2.5 T - x
40
ns
TPLAZ
Max
x
x
10
ns
AT89C5131
4136B–USB–09/03
AT89C5131
External Program Memory Read Cycle
12 TCLCL
TLHLL
TLLIV
ALE
TLLPL
TPLPH
PSEN
TLLAX
TAVLL
PORT 0
INSTR IN
TPLIV
TPLAZ
A0-A7
TPXAV
TPXIZ
TPXIX
INSTR IN
A0-A7
INSTR IN
TAVIV
PORT 2
ADDRESS
OR SFR-P2
External Data Memory
Characteristics
ADDRESS A8-A15
ADDRESS A8-A15
Table 115. Symbol Description
Symbol
Parameter
TRLRH
RD Pulse Width
TWLWH
WR Pulse Width
TRLDV
RD to Valid Data In
TRHDX
Data Hold After RD
TRHDZ
Data Float After RD
TLLDV
ALE to Valid Data In
TAVDV
Address to Valid Data In
TLLWL
ALE to WR or RD
TAVWL
Address to WR or RD
TQVWX
Data Valid to WR Transition
TQVWH
Data set-up to WR High
TWHQX
Data Hold After WR
TRLAZ
RD Low to Address Float
TWHLH
RD or WR High to ALE high
159
4136B–USB–09/03
Table 116. AC Parameters for a Variable Clock (F = 40 MHz)
Symbol
Min
TRLRH
130
ns
TWLWH
130
ns
TRLDV
TRHDX
100
0
Units
ns
ns
TRHDZ
30
ns
TLLDV
160
ns
TAVDV
165
ns
100
ns
TLLWL
50
TAVWL
75
ns
TQVWX
10
ns
TQVWH
160
ns
TWHQX
15
ns
TRLAZ
TWHLH
160
Max
10
0
ns
40
ns
AT89C5131
4136B–USB–09/03
AT89C5131
Table 117. AC Parameters for a Variable Clock
Symbol
Type
Standard
Clock
X2 Clock
X Parameter
Units
TRLRH
Min
6T-x
3T-x
20
ns
TWLWH
Min
6T-x
3T-x
20
ns
TRLDV
Max
5T-x
2.5 T - x
25
ns
TRHDX
Min
x
x
0
ns
TRHDZ
Max
2T-x
T-x
20
ns
TLLDV
Max
8T-x
4T -x
40
ns
TAVDV
Max
9T-x
4.5 T - x
60
ns
TLLWL
Min
3T-x
1.5 T - x
25
ns
TLLWL
Max
3T+x
1.5 T + x
25
ns
TAVWL
Min
4T-x
2T-x
25
ns
TQVWX
Min
T-x
0.5 T - x
15
ns
TQVWH
Min
7T-x
3.5 T - x
25
ns
TWHQX
Min
T-x
0.5 T - x
10
ns
TRLAZ
Max
x
x
0
ns
TWHLH
Min
T-x
0.5 T - x
15
ns
TWHLH
Max
T+x
0.5 T + x
15
ns
External Data Memory Write
Cycle
TWHLH
ALE
PSEN
TLLWL
TWLWH
WR
TLLAX
PORT 0
A0-A7
TQVWX
TQVWH
TWHQX
DATA OUT
TAVWL
PORT 2
ADDRESS
OR SFR-P2
ADDRESS A8-A15 OR SFR P2
161
4136B–USB–09/03
External Data Memory Read Cycle
TWHLH
TLLDV
ALE
PSEN
TLLWL
TRLRH
RD
TRHDZ
TAVDV
TLLAX
PORT 0
TRHDX
A0-A7
DATA IN
TRLAZ
TAVWL
PORT 2
ADDRESS
OR SFR-P2
Serial Port Timing - Shift
Register Mode
ADDRESS A8-A15 OR SFR P2
Table 118. Symbol Description (F = 40 MHz)
Symbol
Parameter
TXLXL
Serial port clock cycle time
TQVHX
Output data set-up to clock rising edge
TXHQX
Output data hold after clock rising edge
TXHDX
Input data hold after clock rising edge
TXHDV
Clock rising edge to input data valid
Table 119. AC Parameters for a Fix Clock (F = 40 MHz)
Symbol
Min
Max
TXLXL
300
ns
TQVHX
200
ns
TXHQX
30
ns
TXHDX
0
ns
TXHDV
Units
117
ns
Table 120. AC Parameters for a Variable Clock
162
Symbol
Type
Standard
Clock
X2 Clock
X Parameter
for -M Range
TXLXL
Min
12 T
6T
TQVHX
Min
10 T - x
5T-x
50
ns
TXHQX
Min
2T-x
T-x
20
ns
TXHDX
Min
x
x
0
ns
TXHDV
Max
10 T - x
5 T- x
133
ns
Units
ns
AT89C5131
4136B–USB–09/03
AT89C5131
Shift Register Timing Waveform
INSTRUCTION
0
1
2
3
4
5
6
7
8
ALE
TXLXL
CLOCK
TXHQX
TQVXH
OUTPUT DATA
WRITE to SBUF
INPUT DATA
0
1
2
3
4
5
6
TXHDX
TXHDV
VALID
VALID
SET TI
VALID
VALID
VALID
VALID
VALID
VALID
SET RI
CLEAR RI
External Clock Drive
Characteristics (XTAL1)
7
Table 121. AC Parameters
Symbol
Parameter
Min
Max
Units
TCLCL
Oscillator Period
25
ns
TCHCX
High Time
5
ns
TCLCX
Low Time
5
ns
TCLCH
Rise Time
5
ns
TCHCL
Fall Time
5
ns
60
%
TCHCX/TCLCX
Cyclic ratio in X2 mode
40
External Clock Drive
Waveforms
VCC-0.5V
0.45V
0.7VCC
0.2VCC-0.1
TCHCX
TCLCH
TCLCX
TCHCL
TCLCL
AC Testing Input/Output
Waveforms
VCC -0.5V
0.2 VCC + 0.9
INPUT/OUTPUT
0.2 VCC - 0.1
0.45V
AC inputs during testing are driven at VCC - 0.5 for a logic “1” and 0.45V for a logic “0”.
Timing measurement are made at VIH min for a logic “1” and VIL max for a logic “0”.
Float Waveforms
FLOAT
VOH - 0.1 V
VOL + 0.1 V
VLOAD
VLOAD + 0.1 V
VLOAD - 0.1 V
For timing purposes as port pin is no longer floating when a 100 mV change from load
voltage occurs and begins to float when a 100 mV change from the loaded VOH/VOL level
occurs. IOL/IOH ≥ ±20 mA.
163
4136B–USB–09/03
Clock Waveforms
Valid in normal clock mode. In X2 mode XTAL2 must be changed to XTAL2/2.
INTERNAL
CLOCK
STATE4
STATE5
STATE6
STATE1
STATE2
STATE3
STATE4
STATE5
P1
P1
P1
P1
P1
P1
P1
P1
P2
P2
P2
P2
P2
P2
P2
P2
XTAL2
ALE
THESE SIGNALS ARE NOT ACTIVATED DURING THE
EXECUTION OF A MOVX INSTRUCTION
EXTERNAL PROGRAM MEMORY FETCH
PSEN
P0
DATA
SAMPLED
PCL OUT
DATA
SAMPLED
FLOAT
P2 (EXT)
PCL OUT
FLOAT
DATA
SAMPLED
PCL OUT
FLOAT
INDICATES ADDRESS TRANSITIONS
READ CYCLE
RD
PCL OUT (IF PROGRAM
MEMORY IS EXTERNAL)
P0
DPL OR Rt OUT
DATA
SAMPLED
FLOAT
INDICATES DPH OR P2 SFR TO PCH TRANSITION
P2
WRITE CYCLE
WR
P0
PCL OUT (EVEN IF PROGRAM
MEMORY IS INTERNAL)
DPL OR Rt OUT
PCL OUT (IF PROGRAM
MEMORY IS EXTERNAL)
DATA OUT
INDICATES DPH OR P2 SFR TO PCH TRANSITION
P2
PORT OPERATION
OLD DATA NEW DATA
MOV PORT SRC
P0 PINS SAMPLED
P0 PINS SAMPLED
MOV DEST P0
MOV DEST PORT (P1. P2. P3)
(INCLUDES INTO. INT1. TO T1)
SERIAL PORT SHIFT CLOCK
P1, P2, P3 PINS SAMPLED
RXD SAMPLED
P1, P2, P3 PINS SAMPLED
RXD SAMPLED
TXD (MODE 0)
This diagram indicates when signals are clocked internally. The time it takes the signals to propagate to the pins, however,
ranges from 25 to 125 ns. This propagation delay is dependent on variables such as temperature and pin loading. Propagation also varies from output to output and component. Typically though (TA = 25°C fully loaded) RD and WR propagation
delays are approximately 50 ns. The other signals are typically 85 ns. Propagation delays are incorporated in the AC
specifications.
164
AT89C5131
4136B–USB–09/03
AT89C5131
Flash Memory
Table 122. Timing Symbol Definitions
Signals
Conditions
S (Hardware
Condition)
PSEN, EA
L
Low
R
RST
V
Valid
B
FBUSY Flag
X
No Longer Valid
Table 123. Memory AC Timing
VDD = 3.3V ± 10%, TA = -40 to +85°C
Symbol
Parameter
Min
Typ
Max
Unit
TSVRL
Input PSEN Valid to RST Edge
50
ns
TRLSX
Input PSEN Hold after RST Edge
50
ns
TBHBL
Flash Internal Busy (Programming) Time
10
ms
Figure 74. Flash Memory - ISP Waveforms
RST
TSVRL
TRLSX
PSEN1
Figure 75. Flash Memory - Internal Busy Waveforms
FBUSY bit
TBHBL
165
4136B–USB–09/03
USB AC Parameters
Rise Time
Fall Time
90%
VHmin
90%
VCRS
10%
10%
Differential
Data Lines
tR
VLmax
tF
Table 124. USB AC Parameters
Symbol
Parameter
Min
tR
Rise Time
tF
Fall Time
Max
Unit
4
20
ns
4
20
ns
11.9700
12.0300
Mb/s
Crossover Voltage
1.3
2.0
V
tDJ1
Source Jitter Total to Next
Transaction
-3.5
3.5
ns
tDJ2
Source Jitter Total for Paired
Transactions
-4
4
ns
tJR1
Receiver Jitter to Next
Transaction
-18.5
18.5
ns
tJR2
Receiver Jitter for Paired
Transactions
-9
9
ns
tFDRATE
VCRS
166
Full-speed Data Rate
Typ
Test Conditions
AT89C5131
4136B–USB–09/03
AT89C5131
Ordering Information
Table 125. Possible Order Entries
Note:
Part Number
Memory Size (Kbytes)
Supply Voltage
Temperature Range
Package
Packing
AT89C5131-RDTIL
32
3.0 to 3.6V
Industrial
VQFP64
Tray
AT89C5131-PLTIL
32
3.0 to 3.6V
Industrial
MLF48
Stick
AT89C5131-S3SIL
32
3.0 to 3.6V
Industrial
PLCC52
Stick
AT89C5131-TISIL
32
3.0 to 3.6V
Industrial
SO28
Stick
1. Optional Packing and Package options (please consult Atmel sales representative):
-Tape and Reel
-Dry Pack
-Known good dice
167
4136B–USB–09/03
Packaging Information
64-lead VQFP
168
AT89C5131
4136B–USB–09/03
AT89C5131
52-lead PLCC
48-lead MLF
169
4136B–USB–09/03
170
AT89C5131
4136B–USB–09/03
AT89C5131
28-lead SO
171
4136B–USB–09/03
Datasheet Change
Log
Changes from 4136A 03/03 to 4136B - 09/03
172
1. Added Two Wire Interface description.
2. AC/DC parameters modified.
AT89C5131
4136B–USB–09/03
Table of Contents
Features ................................................................................................. 1
Description ............................................................................................ 2
Block Diagram ....................................................................................... 3
Pinout Description ................................................................................ 4
Pinout.................................................................................................................... 4
Signals ...................................................................................................................7
SFR Mapping ....................................................................................... 12
Clock Controller .................................................................................. 19
Introduction ......................................................................................................... 19
Oscillator............................................................................................................. 19
PLL ..................................................................................................................... 20
Registers..............................................................................................................22
Dual Data Pointer Register ................................................................ 24
Program/Code Memory ...................................................................... 26
External Code Memory Access ..........................................................................
Flash Memory Architecture.................................................................................
Overview of FM0 Operations ..............................................................................
Registers.............................................................................................................
26
27
28
34
Flash EEPROM Memory ..................................................................... 35
General Description ............................................................................................ 35
Features.............................................................................................................. 35
Flash Programming and Erasure........................................................................ 35
Flash Registers and Memory Map.......................................................................36
Flash Memory Status.......................................................................................... 39
Memory Organization ......................................................................................... 39
EEPROM Data Memory ....................................................................... 40
Description.......................................................................................................... 40
Write Data in the Column Latches ...................................................................... 40
Programming ...................................................................................................... 40
Read Data........................................................................................................... 40
Registers..............................................................................................................41
In-System Programming (ISP) ........................................................... 42
Flash Programming and Erasure........................................................................ 42
Boot Process ...................................................................................................... 43
i
4136B–USB–09/03
Application-Programming-Interface ....................................................................
XROW Bytes.......................................................................................................
Hardware Conditions ..........................................................................................
Hardware Security Byte ......................................................................................
44
44
44
45
On-chip Expanded RAM (ERAM) ....................................................... 46
Timer 2 ................................................................................................. 49
Auto-reload Mode ............................................................................................... 49
Programmable Clock Output .............................................................................. 50
Programmable Counter Array (PCA) ................................................ 54
PCA Capture Mode.............................................................................................
16-bit Software Timer/Compare Mode................................................................
High Speed Output Mode ...................................................................................
Pulse Width Modulator Mode..............................................................................
PCA Watchdog Timer .........................................................................................
61
61
62
63
64
Serial I/O Port ...................................................................................... 65
Framing Error Detection .....................................................................................
Automatic Address Recognition..........................................................................
Baud Rate Selection for UART for Mode 1 and 3...............................................
UART Registers..................................................................................................
65
66
68
71
Interrupt System ................................................................................. 75
Overview............................................................................................................. 75
Registers............................................................................................................. 76
Interrupt Sources and Vector Addresses.............................................................83
Keyboard Interface ............................................................................. 84
Introduction ......................................................................................................... 84
Description.......................................................................................................... 84
Registers............................................................................................................. 85
Programmable LED ............................................................................ 88
Serial Peripheral Interface (SPI) ........................................................ 89
Features.............................................................................................................. 89
Signal Description............................................................................................... 89
Functional Description ........................................................................................ 91
Two Wire Interface (TWI) .................................................................... 98
Introduction ......................................................................................................... 98
Description........................................................................................................ 100
Notes ................................................................................................................ 103
Registers............................................................................................................112
ii
4136B–USB–09/03
USB Controller .................................................................................. 114
Introduction ....................................................................................................... 114
Description........................................................................................................ 115
Configuration .................................................................................................... 118
Read/Write Data FIFO ...................................................................................... 120
Bulk/Interrupt Transactions............................................................................... 121
Control Transactions......................................................................................... 125
Isochronous Transactions..................................................................................126
Miscellaneous ....................................................................................................128
Suspend/Resume Management ........................................................................129
Detach Simulation..............................................................................................131
USB Interrupt System ....................................................................................... 131
USB Registers ...................................................................................................134
Power Management .......................................................................... 146
Idle Mode .......................................................................................................... 146
Power-down Mode............................................................................................ 146
Registers........................................................................................................... 148
Hardware Watchdog Timer .............................................................. 149
Using the WDT ................................................................................................. 149
WDT During Power-down and Idle ................................................................... 150
ONCE Mode (ON Chip Emulation) ................................................... 151
Reduced EMI Mode ........................................................................... 152
Electrical Characteristics ................................................................. 153
Absolute Maximum Ratings ............................................................................. 153
DC Parameters for Low Voltage ....................................................................... 153
USB DC Parameters......................................................................................... 156
AC Parameters ................................................................................................. 157
USB AC Parameters..........................................................................................166
Ordering Information ........................................................................ 167
Packaging Information ..................................................................... 168
64-lead VQFP ...................................................................................................
52-lead PLCC ...................................................................................................
48-lead MLF......................................................................................................
28-lead SO........................................................................................................
168
169
170
170
Datasheet Change Log..................................................................... 172
Changes from 4136A -03/03 to 4136B - 09/03 ................................................. 172
Table of Contents .................................................................................. i
iii
4136B–USB–09/03
Atmel Corporation
2325 Orchard Parkway
San Jose, CA 95131, USA
Tel: 1(408) 441-0311
Fax: 1(408) 487-2600
Regional Headquarters
Europe
Atmel Sarl
Route des Arsenaux 41
Case Postale 80
CH-1705 Fribourg
Switzerland
Tel: (41) 26-426-5555
Fax: (41) 26-426-5500
Asia
Room 1219
Chinachem Golden Plaza
77 Mody Road Tsimshatsui
East Kowloon
Hong Kong
Tel: (852) 2721-9778
Fax: (852) 2722-1369
Japan
9F, Tonetsu Shinkawa Bldg.
1-24-8 Shinkawa
Chuo-ku, Tokyo 104-0033
Japan
Tel: (81) 3-3523-3551
Fax: (81) 3-3523-7581
Atmel Operations
Memory
2325 Orchard Parkway
San Jose, CA 95131, USA
Tel: 1(408) 441-0311
Fax: 1(408) 436-4314
RF/Automotive
Theresienstrasse 2
Postfach 3535
74025 Heilbronn, Germany
Tel: (49) 71-31-67-0
Fax: (49) 71-31-67-2340
Microcontrollers
2325 Orchard Parkway
San Jose, CA 95131, USA
Tel: 1(408) 441-0311
Fax: 1(408) 436-4314
La Chantrerie
BP 70602
44306 Nantes Cedex 3, France
Tel: (33) 2-40-18-18-18
Fax: (33) 2-40-18-19-60
ASIC/ASSP/Smart Cards
1150 East Cheyenne Mtn. Blvd.
Colorado Springs, CO 80906, USA
Tel: 1(719) 576-3300
Fax: 1(719) 540-1759
Biometrics/Imaging/Hi-Rel MPU/
High Speed Converters/RF Datacom
Avenue de Rochepleine
BP 123
38521 Saint-Egreve Cedex, France
Tel: (33) 4-76-58-30-00
Fax: (33) 4-76-58-34-80
Zone Industrielle
13106 Rousset Cedex, France
Tel: (33) 4-42-53-60-00
Fax: (33) 4-42-53-60-01
1150 East Cheyenne Mtn. Blvd.
Colorado Springs, CO 80906, USA
Tel: 1(719) 576-3300
Fax: 1(719) 540-1759
Scottish Enterprise Technology Park
Maxwell Building
East Kilbride G75 0QR, Scotland
Tel: (44) 1355-803-000
Fax: (44) 1355-242-743
Literature Requests
www.atmel.com/literature
Disclaimer: Atmel Corporation makes no warranty for the use of its products, other than those expressly contained in the Company’s standard
warranty which is detailed in Atmel’s Terms and Conditions located on the Company’s web site. The Company assumes no responsibility for any
errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without notice, and
does not make any commitment to update the information contained herein. No licenses to patents or other intellectual property of Atmel are
granted by the Company in connection with the sale of Atmel products, expressly or by implication. Atmel’s products are not authorized for use
as critical components in life support devices or systems.
© Atmel Corporation 2003. All rights reserved. Atmel ® and combinations thereof are the registered trademarks of Atmel
Corporation or its subsidiaries. Other terms and product names may be the trademarks of others.
Printed on recycled paper.
4136B–USB–09/03
Similar pages