Z16F6411FI20AG [IXYS]
Microcontroller, 16-Bit, FLASH, 20MHz, CMOS, PQFP80, QFP-80;
| 型号： | Z16F6411FI20AG |
| 厂家： | 
IXYS CORPORATION |
| 描述： | Microcontroller, 16-Bit, FLASH, 20MHz, CMOS, PQFP80, QFP-80 时钟 微控制器 外围集成电路 |
| 文件： | 总392页 (文件大小：24370K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
High Performance Microcontrollers
ZNEO® Z16F Series
Product Specification
PS022010-0811
Copyright ©2011 Zilog®, Inc. All rights reserved.
www.zilog.com
ZNEO Z16F Series ZNEO
Product Specification
ii
DO NOT USE THIS PRODUCT IN LIFE SUPPORT SYSTEMS.
Warning:
LIFE SUPPORT POLICY
ZILOG’S PRODUCTS ARE NOT AUTHORIZED FOR USE AS CRITICAL COMPONENTS IN LIFE
SUPPORT DEVICES OR SYSTEMS WITHOUT THE EXPRESS PRIOR WRITTEN APPROVAL OF
THE PRESIDENT AND GENERAL COUNSEL OF ZILOG CORPORATION.
As used herein
Life support devices or systems are devices which (a) are intended for surgical implant into the body, or (b)
support or sustain life and whose failure to perform when properly used in accordance with instructions for
use provided in the labeling can be reasonably expected to result in a significant injury to the user. A criti-
cal component is any component in a life support device or system whose failure to perform can be reason-
ably expected to cause the failure of the life support device or system or to affect its safety or effectiveness.
Document Disclaimer
©2011 Zilog, Inc. All rights reserved. Information in this publication concerning the devices, applications,
or technology described is intended to suggest possible uses and may be superseded. ZILOG, INC. DOES
NOT ASSUME LIABILITY FOR OR PROVIDE A REPRESENTATION OF ACCURACY OF THE
INFORMATION, DEVICES, OR TECHNOLOGY DESCRIBED IN THIS DOCUMENT. ZILOG ALSO
DOES NOT ASSUME LIABILITY FOR INTELLECTUAL PROPERTY INFRINGEMENT RELATED
IN ANY MANNER TO USE OF INFORMATION, DEVICES, OR TECHNOLOGY DESCRIBED
HEREIN OR OTHERWISE. The information contained within this document has been verified according
to the general principles of electrical and mechanical engineering.
Z8, Z8 Encore!, ZNEO and Z16F are trademarks or registered trademarks of Zilog, Inc. All other product
or service names are the property of their respective owners.
PS022010-0811
P R E L I M I N A R Y
Disclaimer
ZNEO Z16F Series
Product Specification
iii
Revision History
Each instance in this document’s revision history reflects a change from its previous edi-
tion. For more details, refer to the corresponding page(s) or appropriate links furnished in
the table below.
Revision
Date Level
Page
No.
Section
Description
Aug
10
Multi-Channel PWM Timer
Per CR#13095, corrected PWMEN descrip-
125,
2011
tion in PWM Control 0 Register (PWMCTL0) 127–
table; corrected description in PWM Dead-
band Register (PWMDB) table and added
footnote; added same footnote to PWM Mini-
mum Pulse Width Filter (PWMMPF), PWM
Fault Mask Register (PWMFM), and PWM
Fault Control Register (PWMFCTL) tables.
129,
131
Jun
2011
09
08
Electrical Characteristics
Corrected V
parator Electrical Characteristics table
input offset value in Com-
346
COFF
Aug
N/A
Removed ISO information.
ii
2010
All
Updated logos.
All
Table 191
Changed the Minimum, Typical and Maxi-
345
mum values for V
(Externally supplied
REF
Voltage Reference only).
Jan
2009
07
06
Timer 0–2 Control 0 Register
Analog Functions
Table 62: added “Only Counter Mode should
be used with this feature” to Bit 4 description.
109
ADC Overview, updated fast conversion time 243
to 2.5µs.
Electrical Characteristics
Updated Table 185.
336
335
117
Internal Precision Oscillator
Removed reference to 32kHz.
Feb
Independent and Complemen- Corrected PWM Registers. Updated Edge-
2007
tary PWM Outputs
Aligned PWM Output figure.
Electrical Characteristics
Replaced 105°C with 125°C in Tables 185
through 192. Added Figures 73 through 75.
336
I2C Master/Slave Controller
Packaging
Changes to Software Control of I2C Transac- 209
tions section.
Updated Part Number Suffix Designations
section.
362
Enhanced Serial Peripheral
Interface
Throughput section modified.
181
PS022010-0811
P R E L I M I N A R Y
Revision History
ZNEO Z16F Series
Product Specification
iv
Jul
2006
05
04
External Interface, General-
Purpose Input/Output, DMA
Controller, Option Bits, On-Chip Option bits, on-chip debugger and Electrical
Debugger and Electrical Char- characteristics.
acteristics
Modifications done in the following chapters: 37, 66,
External Interface, GPIO, DMA Controller,
267,
292,
298,
336
Ordering Information
All
Ordering Information modified.
359
All
Jan
2006
Changed zneo to ZNEO in the entire docu-
ment.
All
Added TM symbol to ZNEO.
All
Signal and Pin Descriptions,
Modifications done to following chapters: Pin 7, 80,
Interrupt Controller and Analog description, Interrupt controller and Analog
242
359
Functions
functions.
Ordering Information
Ordering Information modified.
PS022010-0811
P R E L I M I N A R Y
Revision History
ZNEO® Z16F Series MCUs
Product Specification
v
Table of Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
ZNEO CPU Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
External Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Flash Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Random Access Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
ZNEO Peripheral Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
10-Bit Analog-to-Digital Converter with Programmable Gain Amplifier . . . . . . 4
Analog Comparator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Operational Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
General-Purpose Input/Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Universal Asynchronous Receiver/Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Infrared Encoder/Decoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Inter-Integrated Circuit Master/Slave Controller . . . . . . . . . . . . . . . . . . . . . . . . . 4
Enhanced Serial Peripheral Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
DMA Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Pulse Width Modulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Standard Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Interrupt Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Crystal Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Reset Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
On-Chip Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Signal and Pin Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Available Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Pin Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Pin Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Address Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Internal Nonvolatile Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Internal RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Input/Output Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
vi
Input/Output Memory Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
CPU Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
External Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Endianness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Bus Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Peripheral Address Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
External Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
External Interface Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chip Selects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Tools Compatibility Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
External WAIT Pin Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Wait State Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
ISA-Compatible Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
External Interface Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
External Interface Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chip Select Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
External Interface Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
External Interface Write Timing, Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . 47
External Interface Write Timing, ISA Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
External Interface Read Timing, Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . 50
External Interface Read Timing, ISA Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Reset and Stop Mode Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Reset Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
System Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Power-On Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Voltage Brown-Out Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Watchdog Timer Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
External Pin Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
External Reset Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
User Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Fault Detect Logic Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Stop Mode Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Stop Mode Recovery Using WDT Time-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Stop Mode Recovery Using a GPIO Port Pin Transition . . . . . . . . . . . . . . . . . . 61
Reset Status and Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
STOP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
HALT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Peripheral-Level Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
vii
Power Control Option Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
General-Purpose Input/Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
GPIO Port Availability by Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
GPIO Alternate Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
GPIO Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
GPIO Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Port A-K Input Data Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Port A-K Output Data Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Port A-K Data Direction Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Port A-K High Drive Enable Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Port A-K Alternate Function High and Low Registers . . . . . . . . . . . . . . . . . . . 74
Port A-K Output Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Port A-K Pull-Up Enable Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Port A-K Stop Mode Recovery Source Enable Registers . . . . . . . . . . . . . . . . . 77
Port A IRQ MUX1 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Port A IRQ MUX Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Port A IRQ Edge Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Port C IRQ MUX Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Interrupt Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Interrupt Vector Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Master Interrupt Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Interrupt Vectors and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
System Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Interrupt Assertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
System Exception Status Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Last IRQ Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Interrupt Request 0 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Interrupt Request 1 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Interrupt Request 2 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
IRQ0 Enable High and Low Bit Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
IRQ1 Enable High and Low Bit Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
IRQ2 Enable High and Low Bit Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Timer Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Reading Timer Count Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
viii
Timer Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Timer 0‒2 High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Timer X Reload High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . . 108
Timer 0–2 PWM High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . 109
Timer 0–2 Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Multi-Channel PWM Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
PWM Option Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
PWM Reload Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
PWM Prescaler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
PWM Period and Count Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
PWM Duty Cycle Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Independent and Complementary PWM Outputs . . . . . . . . . . . . . . . . . . . . . . 118
Manual Off-State Control of PWM Output Channels . . . . . . . . . . . . . . . . . . . 119
Deadband Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Minimum PWM Pulse Width Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Synchronization of PWM and ADC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Synchronized Current-Sense Sample and Hold . . . . . . . . . . . . . . . . . . . . . . . . 120
PWM Timer and Fault Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Fault Detection and Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
PWM Operation in CPU HALT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
PWM Operation in CPU STOP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Observing the State of PWM Output Channels . . . . . . . . . . . . . . . . . . . . . . . . 121
PWM Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
PWM High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
PWM Reload High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . . . . 123
PWM 0–2 Duty Cycle High and Low Byte Registers . . . . . . . . . . . . . . . . . . . 124
PWM Control 0 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
PWM Control 1 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
PWM Deadband Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
PWM Minimum Pulse Width Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
PWM Fault Mask Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
PWM Fault Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
PWM Fault Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
PWM Input Sample Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
PWM Output Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Current-Sense Sample and Hold Control Registers . . . . . . . . . . . . . . . . . . . . . 134
LIN-UART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
ix
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Data Format for Standard UART Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Transmitting Data using the Polled Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Transmitting Data Using Interrupt-Driven Method . . . . . . . . . . . . . . . . . . . . . 138
Receiving Data Using the Polled Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Receiving Data Using the Interrupt-Driven Method . . . . . . . . . . . . . . . . . . . . 140
Clear To Send Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
External Driver Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
LIN-UART Special Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
MULTIPROCESSOR (9-bit) Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
LIN Protocol Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
LIN-UART Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
LIN-UART DMA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
LIN-UART Baud Rate Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Noise Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
LIN-UART Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
LIN-UART Transmit Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
LIN-UART Receive Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
LIN-UART Status 0 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
LIN-UART Mode Select and Status Register . . . . . . . . . . . . . . . . . . . . . . . . . 158
LIN-UART Control 0 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
LIN-UART Control 1 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
LIN-UART Address Compare Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
LIN-UART Baud Rate High and Low Byte Registers . . . . . . . . . . . . . . . . . . . 166
Infrared Encoder/Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Transmitting IrDA Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Receiving IrDA Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Infrared Encoder/Decoder Control Register Definitions . . . . . . . . . . . . . . . . . . . . 175
Enhanced Serial Peripheral Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
ESPI Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Master-In/Slave-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Master-Out/Slave-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Serial Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Slave Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
ESPI Register Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
x
Comparison with Basic SPI Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
ESPI Clock Phase and Polarity Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
SPI Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Error Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
ESPI Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
DMA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
ESPI Baud Rate Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
ESPI Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
ESPI Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
ESPI Transmit Data Command Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
ESPI Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
ESPI Mode Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
ESPI Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
ESPI State Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
ESPI Baud Rate High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . . 201
I2C Master/Slave Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
I2C Master/Slave Controller Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Comparison with Master Mode only I2C Controller . . . . . . . . . . . . . . . . . . . . 205
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
SDA and SCL Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
I2C Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Start and Stop Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Software Control of I2C Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Master Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Slave Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
DMA Control of I2C Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
I2C Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
I2C Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
I2C Interrupt Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
I2C Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
I2C Baud Rate High and Low Byte Registers . . . . . . . . . . . . . . . . . . . . . . . . . 230
I2C State Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
I2C Mode Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
I2C Slave Address Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Watchdog Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
xi
Watchdog Timer Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Watchdog Timer Time-Out Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Watchdog Timer Reload Unlock Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Watchdog Timer Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Watchdog Timer Reload High and Low Byte Registers . . . . . . . . . . . . . . . . . 241
Analog Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
ADC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
ADC Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
ADC Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
ADC0 Timer 0 Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
ADC Convert on Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Reference Buffer, RBUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Internal Voltage Reference Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
ADC Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
ADC0 Control Register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
ADC0 Data High Byte Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
ADC0 Data Low Bits Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Sample Settling Time Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Sample Time Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
ADC Clock Prescale Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
ADC0 Max Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
ADC Timer 0 Capture Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Comparator and Operational Amplifier Overview . . . . . . . . . . . . . . . . . . . . . . . . . 251
Comparator Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Operational Amplifier Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Comparator Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Comparator and Operational Amplifier Control Register . . . . . . . . . . . . . . . . 253
Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Information Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Timing Using the Flash Frequency Register . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Flash Read Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Flash Write/Erase Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Page Erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Mass Erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Flash Controller Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
xii
Flash Controller Behavior using the On-Chip Debugger . . . . . . . . . . . . . . . . . 260
Flash Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Flash Command Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Flash Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Flash Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Flash Sector Protect Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Flash Page Select Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Flash Frequency Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
DMA Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
DMA Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
DMA Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
DMA Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
DMA Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
DMA Control Bit Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
DMA Watermark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
DMA Peripheral Interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Buffer Closure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
DMA Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Linked List Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
DMA Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
DMA Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
DMA Request Select Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
DMA Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
DMA Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
DMA X Transfer Length Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
DMA Destination Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
DMA Source Address Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
DMA List Address Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
External DMA Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
DMA Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Option Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Option Bit Address Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Program Memory Address 0001H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Program Memory Address 0002H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Program Memory Address 0003H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Information Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
IPO Trim Registers (Information Area Address 0021H and 0022H) . . . . . . . 296
ADC Reference Voltage Trim (Information Area Address 0023H) . . . . . . . . 297
On-Chip Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
xiii
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
On-Chip Debug Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Serial Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Baud Rate Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Auto-Baud Detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Line Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
9-Bit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Start Bit Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Initialization during Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Debug Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Error Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
DEBUG HALT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Reading and Writing Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Reading Memory CRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Instruction Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
On-Chip Debugger Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Cyclic Redundancy Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Memory Cyclic Redundancy Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
UART Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Serial Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
DBG Pin as a GPIO Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Receive Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Transmit Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Baud Rate Reload Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Line Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
OCD Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
OCD Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Hardware Breakpoint Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Trace Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Trace Address Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
On-Chip Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Crystal Oscillator Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
xiv
Oscillator Operation with an External RC Network . . . . . . . . . . . . . . . . . . . . . . . . 328
Oscillator Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
System Clock Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Clock Selection Following System Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Clock Failure Detection and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Oscillator Control Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Oscillator Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Oscillator Divide Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Internal Precision Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
On-Chip Peripheral AC and DC Electrical Characteristics . . . . . . . . . . . . . . . . . . 343
AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
General Purpose I/O Port Input Data Sample Timing . . . . . . . . . . . . . . . . . . . 349
On-Chip Debugger Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
SPI Master Mode Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
SPI Slave Mode Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
I2C Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
UART Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Part Number Suffix Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Precharacterization Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
PS022010-0811
P R E L I M I N A R Y
Table of Contents
ZNEO® Z16F Series MCUs
Product Specification
xv
List of Figures
Figure 1. Motor Control MCUs Z16F Series Block Diagram . . . . . . . . . . . . . . . . . . . . 2
Figure 2. Z16F2810 MCU, 64-Pin Low-Profile Quad Flat Package (LQFP) . . . . . . . . 8
Figure 3. Z16F2810 MCU, 68-Pin Plastic Leaded Chip Carrier (PLCC) . . . . . . . . . . . 9
Figure 4. ZNEO Z16F Series, 80-Pin Quad Flat Package (QFP) . . . . . . . . . . . . . . . . 10
Figure 5. ZNEO Z16F Series, 100-Pin Low-Profile Quad Flat Package (LQFP) . . . 11
Figure 6. Physical Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 7. Endianness of Words and Quads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 8. Alignment of Word and Quad Operations on 16-bit Memories . . . . . . . . . 22
Figure 9. Chip Select Boundary Addressing with 128 KB Internal Flash . . . . . . . . . 38
Figure 10. External Interface Wait State Operation Example (Write Operation) . . . . 41
Figure 11. External Interface Timing for a Write Operation, Normal Mode . . . . . . . . 48
Figure 12. External Interface Timing for a Write Operation, ISA Mode . . . . . . . . . . . 50
Figure 13. External Interface Timing for a Read Operation, Normal Mode . . . . . . . . . 52
Figure 14. External Interface Timing for a Read Operation, 2 Wait States and 1 Post
Read Wait State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 15. External Interface Timing for a Read Operation, ISA Mode . . . . . . . . . . . 55
Figure 16. Power-On Reset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 17. Voltage Brown-Out Reset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 18. GPIO Port Pin Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 19. Interrupt Controller Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 20. Timer Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 21. PWM Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 22. Edge-Aligned PWM Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 23. Center-Aligned PWM Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 24. LIN-UART Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 25. LIN-UART Asynchronous Data Format without Parity . . . . . . . . . . . . . . 137
Figure 26. LIN-UART Asynchronous Data Format with Parity . . . . . . . . . . . . . . . . . 137
Figure 27. LIN-UART Driver Enable Signal Timing (shown with 1 Stop Bit
and Parity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 28. LIN-UART Asynchronous MULTIPROCESSOR Mode Data Format . . 143
Figure 29. LIN-UART Receiver Interrupt Service Routine Flow . . . . . . . . . . . . . . . 149
Figure 30. Noise Filter System Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 31. Noise Filter Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
PS022010-0811
P R E L I M I N A R Y
List of Figures
ZNEO® Z16F Series MCUs
Product Specification
xvi
Figure 32. Infrared Data Communication System Block Diagram . . . . . . . . . . . . . . 172
Figure 33. Infrared Data Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 34. Infrared Data Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 35. ESPI Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 36. ESPI Timing when PHASE = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 37. ESPI Timing when PHASE = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 38. SPI Mode (SSMD = 000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 39. I2S Mode (SSMD = 010) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 40. ESPI Configured as an SPI Master in a Single Master, Single Slave
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 41. ESPI Configured as an SPI Master in a Single Master, Multiple Slave
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 42. ESPI Configured as an SPI Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 43. I2C Controller Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 44. Data Transfer Format, Master Write Transaction with 7-Bit Addressing . 211
Figure 45. Data Transfer Format, Master Write Transaction with 10-Bit Addressing 212
Figure 46. Data Transfer Format, Master Read Transaction with 7-Bit Addressing . 214
Figure 47. Data Transfer Format, Master Read Transaction with 10-Bit Addressing 215
Figure 48. Data Transfer Format, Slave Receive Transaction with 7-Bit Addressing 218
Figure 49. Data Transfer Format, Slave Receive Transaction with 10-Bit Addressing 220
Figure 50. Data Transfer Format, Slave Transmit Transaction with 7-Bit Addressing 221
Figure 51. Data Transfer Format, Slave Transmit Transaction with 10-Bit Addressing 222
Figure 52. Analog Functions Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Figure 53. ADC Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 54. ADC Convert Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 55. Flash Memory Arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 56. DMA Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 57. DMA Channel Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 58. Direct DMA Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 59. Linked List Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 60. External DMA Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Figure 61. External ISA DMA transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Figure 62. On-Chip Debugger Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Figure 63. Interfacing a Serial Pin with an RS-232 Interface, #1 of 2 . . . . . . . . . . . . 300
Figure 64. Interfacing a Serial Pin with an RS-232 Interface, #2 of 2 . . . . . . . . . . . . 300
Figure 65. OCD Serial Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
PS022010-0811
P R E L I M I N A R Y
List of Figures
ZNEO® Z16F Series MCUs
Product Specification
xvii
Figure 66. Output Driver when Drive High and Open Drain Enabled . . . . . . . . . . . . 303
Figure 67. 9-Bit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Figure 68. Start Bit Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Figure 69. Initialization During Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 70. Recommended 20MHz Crystal Oscillator Configuration . . . . . . . . . . . . . 327
Figure 71. Connecting the On-Chip Oscillator to an External RC Network . . . . . . . . 328
Figure 72. Typical RC Oscillator Frequency as a Function of the External
Capacitance with a 15kΩ Resistor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Figure 73. Typical IDD Versus System Clock Frequency . . . . . . . . . . . . . . . . . . . . . . 340
Figure 74. Typical HALT Mode Idd Versus System Clock Frequency . . . . . . . . . . . 341
Figure 75. STOP Mode Current Versus VDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Figure 76. Port Input Sample Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 77. SPI Master Mode Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Figure 78. SPI Slave Mode Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Figure 79. I2C Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 80. UART Timing with CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Figure 81. UART Timing without CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Figure 82. 64-Pin Low-Profile Quad Flat Package (LQFP) . . . . . . . . . . . . . . . . . . . . 355
Figure 83. 68-Pin Plastic Lead Chip Carrier (PLCC) Package . . . . . . . . . . . . . . . . . . 356
Figure 84. 80-Pin Quad-Flat Package (QFP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Figure 85. 100-Pin Low-Profile Quad-Flat Package (LQFP) . . . . . . . . . . . . . . . . . . . 358
PS022010-0811
P R E L I M I N A R Y
List of Figures
ZNEO® Z16F Series MCUs
Product Specification
xviii
List of Tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
ZNEO Z16F Series Package Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Pin Characteristics of the ZNEO CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Reserved Memory Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
ZNEO CPU Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Register File Address Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
External Interface Signals Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Example Usage of Chip Selects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
External Interface Control Register (EXTCT) . . . . . . . . . . . . . . . . . . . . . . . 42
Table 10. External Chip Select Control Registers High (EXTCSxH) . . . . . . . . . . . . . 43
Table 11. External Chip Select Control Registers Low for CS0 (EXTCS0L) . . . . . . . 44
Table 12. External Chip Select Control Registers Low for CS1 (EXTCS1L) . . . . . . . 45
Table 13. External Chip Select Control Registers Low for CS2 to CS5 (EXTCSxL) . 46
Table 14. External Interface Timing for a Write Operation, Normal Mode . . . . . . . . 47
Table 15. External Interface Timing for a Write Operation, ISA Mode . . . . . . . . . . . 49
Table 16. External Interface Timing for a Read Operation, Normal Mode . . . . . . . . . 51
Table 17. External Interface Timing for a Read Operation, ISA Mode . . . . . . . . . . . 54
Table 18. Reset and Stop Mode Recovery Characteristics and Latency . . . . . . . . . . . 56
Table 19. System Reset Sources and Resulting Reset Action . . . . . . . . . . . . . . . . . . . 57
Table 20. Stop Mode Recovery Sources and Resulting Action . . . . . . . . . . . . . . . . . . 61
Table 21. Reset Status and Control Register (RSTSCR) . . . . . . . . . . . . . . . . . . . . . . . 62
Table 22. Reset Status Register Values Following Reset . . . . . . . . . . . . . . . . . . . . . . 63
Table 23. GPIO Port Availability by Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Table 24. Port Alternate Function Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 25. Port A-K Input Data Registers (PxIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 26. Port A-K Output Data Registers (PxOUT) . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 27. Port A-K Data Direction Registers (PxDD) . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 28. Port A-K High Drive Enable Registers (PxHDE) . . . . . . . . . . . . . . . . . . . . 74
Table 29. Port A-K Alternate Function Low Registers (PxAFL) . . . . . . . . . . . . . . . . 75
Table 30. Alternate Function Enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 31. Port A-K Alternate Function High Registers (PxAFH) . . . . . . . . . . . . . . . . 75
Table 32. Port A-K Output Control Registers (PxOC) . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 33. Port A-K Pull-Up Enable Registers (PxPUE) . . . . . . . . . . . . . . . . . . . . . . . 76
PS022010-0811
P R E L I M I N A R Y
List of Tables
ZNEO® Z16F Series MCUs
Product Specification
xix
Table 34. Port A-K Stop Mode Recovery Source Enable Registers (PxSMRE) . . . . . 77
Table 35. Port A IRQ MUX1 Register (PAIMUX1) . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 36. Port A IRQ MUX Register (PAIMUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 37. Port A IRQ Edge Register (PAIEDGE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 38. Port C IRQ MUX Register (PCIMUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 39. Interrupt Vectors in Order of Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 40. Interrupt Vector Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 41. System Exception Register High (SYSEXCPH) . . . . . . . . . . . . . . . . . . . . . 84
Table 42. System Exception Register Low (SYSEXCPL) . . . . . . . . . . . . . . . . . . . . . 85
Table 43. Last IRQ Register (LASTIRQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 44. Interrupt Request 0 Register (IRQ0) and Interrupt Request 0 Set
Register (IRQ0SET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 45. Interrupt Request1 Register (IRQ1) and Interrupt Request1 Set
Register (IRQ1SET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 46. Interrupt Request 2 Register (IRQ2) and Interrupt Request 2 Set
Register (IRQ2SET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 47. IRQ0 Enable and Priority Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Table 48. IRQ0 Enable High Bit Register (IRQ0ENH) . . . . . . . . . . . . . . . . . . . . . . . 90
Table 49. IRQ0 Enable Low Bit Register (IRQ0ENL) . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 50. IRQ1 Enable and Priority Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 51. IRQ1 Enable High Bit Register (IRQ1ENH) . . . . . . . . . . . . . . . . . . . . . . . 92
Table 52. IRQ1 Enable Low Bit Register (IRQ1ENL) . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 53. IRQ2 Enable and Priority Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 54. IRQ2 Enable Low Bit Register (IRQ2ENL) . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 55. IRQ2 Enable High Bit Register (IRQ2ENH) . . . . . . . . . . . . . . . . . . . . . . . 93
Table 56. Timer 0‒2 High Byte Register (TxH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 57. Timer 0‒2 Low Byte Register (TXL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 58. Timer 0‒2 Reload High Byte Register (TxRH) . . . . . . . . . . . . . . . . . . . . . 108
Table 59. Timer 0‒2 Reload Low Byte Register (TxRL) . . . . . . . . . . . . . . . . . . . . . 108
Table 60. Timer 0–2 PWM High Byte Register (TxPWMH) . . . . . . . . . . . . . . . . . . 109
Table 61. Timer 0–2 PWM Low Byte Register (TxPWML) . . . . . . . . . . . . . . . . . . . 109
Table 62. Timer 0‒2 Control 0 Register (TxCTL0) . . . . . . . . . . . . . . . . . . . . . . . . . 110
Table 63. Timer 0‒2 Control 1 Register (TxCTL1) . . . . . . . . . . . . . . . . . . . . . . . . . 111
Table 64. PWM High Byte Register (PWMH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 65. PWM Low Byte Register (PWML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 66. PWM Reload High Byte Register (PWMRH) . . . . . . . . . . . . . . . . . . . . . . 123
PS022010-0811
P R E L I M I N A R Y
List of Tables
ZNEO® Z16F Series MCUs
Product Specification
xx
Table 67. PWM Reload Low Byte Register (PWMRL) . . . . . . . . . . . . . . . . . . . . . . 123
Table 68. PWM 0–2 H/L Duty Cycle High Byte Register (PWMHxDH, PWMLxDH) .124
Table 69. PWM Control 0 Register (PWMCTL0) . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Table 70. PWM 0–2 H/L Duty Cycle Low Byte Register (PWMHxDL, PWMLxDL) . .125
Table 71. PWM Control 1 Register (PWMCTL1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 72. PWM Deadband Register (PWMDB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 73. PWM Minimum Pulse Width Filter (PWMMPF) . . . . . . . . . . . . . . . . . . . 128
Table 74. PWM Fault Mask Register (PWMFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table 75. PWM Fault Status Register (PWMFSTAT) . . . . . . . . . . . . . . . . . . . . . . . 130
Table 76. PWM Fault Control Register (PWMFCTL) . . . . . . . . . . . . . . . . . . . . . . . 131
Table 77. PWM Input Sample Register (PWMIN) . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Table 78. PWM Output Control Register (PWMOUT) . . . . . . . . . . . . . . . . . . . . . . . 133
Table 79. Current-Sense Sample and Hold Control Register (CSSHR0 and CSSHR1) .134
Table 80. LIN-UART Transmit Data Register (UxTXD) . . . . . . . . . . . . . . . . . . . . . 154
Table 81. LIN-UART Receive Data Register (UxRXD) . . . . . . . . . . . . . . . . . . . . . . 154
Table 82. LIN-UART Status 0 Register, Standard UART Mode (UxSTAT0) . . . . . 155
Table 83. LIN-UART Status 0 Register, LIN Mode (UxSTAT0) . . . . . . . . . . . . . . . 156
Table 84. LIN-UART Mode Select and Status Register (UxMDSTAT) . . . . . . . . . . 158
Table 85. MULTIPROCESSOR Mode Status Field (MSEL = 000b) . . . . . . . . . . . . 159
Table 86. Digital Noise Filter Mode Status Field (MSEL = 001b) . . . . . . . . . . . . . . 159
Table 87. LIN Mode Status Field (MSEL = 010B) . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Table 88. Hardware Revision Mode Status Field (MSEL = 111b) . . . . . . . . . . . . . . 159
Table 89. LIN-UART Control 0 Register (UxCTL0) . . . . . . . . . . . . . . . . . . . . . . . . 160
Table 90. MultiProcessor Control Register (UxCTL1 with MSEL = 000b) . . . . . . . 162
Table 91. Noise Filter Control Register (UxCTL1 with MSEL = 001b) . . . . . . . . . . 164
Table 92. LIN Control Register (UxCTL1 with MSEL = 010b) . . . . . . . . . . . . . . . . 165
Table 93. LIN-UART Address Compare Register (UxADDR) . . . . . . . . . . . . . . . . . 166
Table 94. LIN-UART Baud Rate High Byte Register (UxBRH) . . . . . . . . . . . . . . . 166
Table 95. LIN-UART Baud Rate Low Byte Register (UxBRL) . . . . . . . . . . . . . . . . 167
Table 96. LIN-UART Baud Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Table 97. ESPI Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Table 98. ESPI Clock Phase (PHASE) and Clock Polarity (CLKPOL) Operation . . 181
Table 99. ESPI Tx DMA Descriptor Command Field . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 100. ESPI Tx DMA Descriptor Status Field . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Table 101. ESPI Rx DMA Descriptor Status Field . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Table 102. ESPI Data Register (ESPIDATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
PS022010-0811
P R E L I M I N A R Y
List of Tables
ZNEO® Z16F Series MCUs
Product Specification
xxi
Table 103. ESPI Transmit Data Command Register (ESPITDCR) . . . . . . . . . . . . . . . 194
Table 104. ESPI Control Register (ESPICTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Table 105. ESPI Mode Register (ESPIMODE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Table 106. ESPI Status Register (ESPISTAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 107. ESPI State Register (ESPISTATE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Table 108. ESPISTATE Values and Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Table 109. ESPI Baud Rate High Byte Register (ESPIBRH) . . . . . . . . . . . . . . . . . . . 202
Table 110. ESPI Baud Rate Low Byte Register (ESPIBRL) . . . . . . . . . . . . . . . . . . . . 202
Table 111. I2C Master/Slave Controller Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Table 112. I2C Data Register (I2CDATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Table 113. I2C Interrupt Status Register (I2CISTAT) . . . . . . . . . . . . . . . . . . . . . . . . . 228
Table 114. I2C Control Register (I2CCTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Table 115. I2C Baud Rate High Byte Register (I2CBRH) . . . . . . . . . . . . . . . . . . . . . 231
Table 116. I2C Baud Rate Low Byte Register (I2CBRL) . . . . . . . . . . . . . . . . . . . . . . 231
Table 117. I2C State Register (I2CSTATE), Description when DIAG = 0 . . . . . . . . . 232
Table 118. I2C State Register (I2CSTATE), Description when DIAG = 1 . . . . . . . . . 233
Table 119. I2CSTATE_H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Table 120. I2CSTATE_L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Table 121. I2C Mode Register (I2CMODE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Table 122. I2C Slave Address Register (I2CSLVAD) . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 123. Watchdog Timer Approximate Time-Out Delays . . . . . . . . . . . . . . . . . . . 239
Table 124. Watchdog Timer Reload High Byte Register (WDTH) . . . . . . . . . . . . . . 241
Table 125. Watchdog Timer Reload Low Byte Register (WDTL) . . . . . . . . . . . . . . . 241
Table 126. ADC0 Control Register 0 (ADC0CTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Table 127. ADC0 Data High Byte Register (ADC0D_H) . . . . . . . . . . . . . . . . . . . . . . 247
Table 128. ADC0 Data Low Bits Register (ADC0D_L) . . . . . . . . . . . . . . . . . . . . . . . 248
Table 129. Sample and Settling Time (ADCSST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Table 130. Sample Time (ADCST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Table 131. ADC Clock Prescale Register (ADCCP) . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Table 132. ADC0 MAX Register (ADC0MAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Table 133. ADC Timer 0 Capture Register, High Byte (ADCTCAP_H) . . . . . . . . . . 251
Table 134. ADC Timer 0 Capture Register, Low Byte (ADCTCAP_L) . . . . . . . . . . . 251
Table 135. Comparator and Op Amp Control Register (CMPOPC) . . . . . . . . . . . . . . 253
Table 136. Flash Memory Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Table 137. Flash Memory Sector Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Table 138. ZNEO Z16F Series Information Area Map . . . . . . . . . . . . . . . . . . . . . . . . 257
PS022010-0811
P R E L I M I N A R Y
List of Tables
ZNEO® Z16F Series MCUs
Product Specification
xxii
Table 139. Flash Command Register (FCMD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Table 140. Flash Status Register (FSTAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Table 141. Flash Control Register (FCTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Table 142. Flash Sector Protect Register (FSECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Table 143. Flash Page Select Register (FPAGE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Table 144. Flash Frequency Register (FFREQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Table 145. Linked List Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Table 146. DMA Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Table 147. DMA Bandwidth Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Table 148. DMA Select Register (DAMxREQSEL) . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Table 149. DMA Control Register A (DMAxCTL) . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Table 150. DMA X Transfer Length High Register (DMAxTXLNH) . . . . . . . . . . . . 286
Table 151. DMA X Transfer Length Low Register (DMAxTXLNL) . . . . . . . . . . . . . 287
Table 152. DMA X Destination Address Register Upper (DMAxDARU) . . . . . . . . . 287
Table 153. DMA X Destination Address Register High (DMAxDARH) . . . . . . . . . . 287
Table 154. DMA X Destination Address Register Low (DMAxDARL) . . . . . . . . . . 287
Table 155. DMA X Source Address Register Upper DMAxSARU . . . . . . . . . . . . . . 288
Table 156. DMA X Source Address Register High (DMAxSARH) . . . . . . . . . . . . . . 288
Table 157. DMA X Source Address Register Low (DMAxSARL) . . . . . . . . . . . . . . 288
Table 158. DMA X List Address Register Upper DMAxLARU . . . . . . . . . . . . . . . . 289
Table 159. DMA X List Address Register High (DMAxLARH) . . . . . . . . . . . . . . . . 289
Table 160. DMA X List Address Register Low (DMAxLARL) . . . . . . . . . . . . . . . . . 289
Table 161. Option Bits At Program Memory Address 0000H . . . . . . . . . . . . . . . . . . 293
Table 162. Options Bits at Program Memory Address 0001H . . . . . . . . . . . . . . . . . . 294
Table 163. Options Bits at Program Memory Address 0002H . . . . . . . . . . . . . . . . . . 295
Table 164. Options Bits at Program Memory Address 0003H . . . . . . . . . . . . . . . . . . 295
Table 165. IPO Trim 1 (IPOTRIM1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Table 166. IPO Trim 2 (IPOTRIM2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Table 167. ADC Reference Voltage Trim (ADCTRIM) . . . . . . . . . . . . . . . . . . . . . . . 297
Table 168. OCD Baud Rate Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Table 169. On-Chip Debugger Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Table 170. Receive Data Register (DBGRXD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Table 171. Transmit Data Register (DBGTXD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Table 172. Baud Rate Reload Register (DBGBR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Table 173. Line Control Register (DBGLCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Table 174. Status Register (DBGSTAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
PS022010-0811
P R E L I M I N A R Y
List of Tables
ZNEO® Z16F Series MCUs
Product Specification
xxiii
Table 175. Control Register (DBGCTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Table 176. OCD Control Register (OCDCTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Table 177. OCD Status Register (OCDSTAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Table 178. Hardware Breakpoint Register (HWBPn) . . . . . . . . . . . . . . . . . . . . . . . . . 323
Table 179. Trace Control Register (TRACECTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Table 180. Trace Address (TRACEADDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Table 181. Recommended Crystal Oscillator Specifications (20MHz Operation) . . . 327
Table 182. Oscillator Configuration and Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Table 183. Oscillator Control Register (OSCCTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Table 184. Oscillator Divide Register (OSCDIV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Table 185. Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Table 186. DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Table 187. POR and VBO Electrical Characteristics and Timing . . . . . . . . . . . . . . . . 343
Table 188. Reset and Stop Mode Recovery Pin Timing . . . . . . . . . . . . . . . . . . . . . . . 343
Table 189. Flash Memory Electrical Characteristics and Timing . . . . . . . . . . . . . . . . 344
Table 190. Watchdog Timer Electrical Characteristics and Timing . . . . . . . . . . . . . . 344
Table 191. ADC Electrical Characteristics and Timing . . . . . . . . . . . . . . . . . . . . . . . 345
Table 192. Comparator Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Table 193. Operational Amplifier Electrical Characteristics . . . . . . . . . . . . . . . . . . . . 346
Table 194. AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Table 195. GPIO Port Input Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Table 196. On-Chip Debugger Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Table 197. SPI Master Mode Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Table 198. SPI Slave Mode Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Table 199. I2C Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Table 200. UART Timing with CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Table 201. UART Timing without CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Table 202. ZNEO Part Selection Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Table 203. ZNEO Z16F Series Part Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
PS022010-0811
P R E L I M I N A R Y
List of Tables
ZNEO® Z16F Series MCUs
Product Specification
1
Introduction
Zilog’s ZNEO® Z16F family of products are optimized for demanding applications. The
®
ZNEO line of Zilog microcontroller products is based on the ZNEO CPU.
Features
ZNEO family of products include the following features:
•
•
•
•
20MHz ZNEO CPU
128KB internal Flash memory with 16-bit access and In-Circuit Programming (ICP)
4KB internal RAM with 16-bit access
External interface allows seamless connection to external data memory and peripheral
with:
–
–
–
–
–
Six chip selects with programmable wait states
24-bit address bus supports 16MB
Selectable 8-bit or 16-bit data bus widths
Programmable chip select signal polarity
ISA-compatible mode
•
•
•
•
12-channel, 10-bit Analog-to-Digital Converter (ADC)
Operational Amplifier
Analog Comparator
4-channel Direct Memory Access (DMA) controller supports internal or external DMA
requests
•
Two full-duplex 9-bit Universal Asynchronous Receiver/Transmitter (UARTs) with
support for Local Interconnect Network (LIN) and Infrared Data Association (IrDA)
•
•
•
•
Internal Precision Oscillator (IPO)
Inter-Integrated Circuit (I2C) master/slave controller
Enhanced Serial Peripheral Interface (ESPI)
12-bit Pulse Width Modulation (PWM) module with three complementary pairs or six
independent PWM outputs with deadband generation and fault trip input
•
•
Three standard 16-bit timers with Capture, Compare and PWM capability
Watchdog Timer (WDT) with internal RC oscillator
PS022010-0811
P R E L I M I N A R Y
Introduction
ZNEO® Z16F Series MCUs
Product Specification
2
•
•
•
•
•
•
•
76 General-Purpose Input/Output (GPIO) pins
24 interrupts with programmable priority
On-Chip Debugger (OCD)
Voltage Brown-Out (VBO) protection
Power-On Reset (POR)
2.7V to 3.6V operating voltage with 5 V-tolerant inputs
0°C to +70°C standard temperature and –40°C to +105°C extended temperature oper-
ating ranges
Block Diagram
Figure 1 displays the architecture of the ZNEO® Z16F Series MCU.
Oscillators
(XTAL, IPO)
On-Chip
Debugger
POR/VBO
and Reset
Controller
ZNEO
CPU
Interrupt
Controller
WDT with
RC Oscillator
System
Clock
Memory Buses
Timers
(3)
UARTs
(2)
2
Flash
Controller
RAM
Controller
I C
ESPI
Analog
DMA
PWM
IrDA
Flash
Memory
RAM
GPIO with External Interface (Address and Data Bus)
Figure 1. Motor Control MCUs Z16F Series Block Diagram
PS022010-0811
P R E L I M I N A R Y
Block Diagram
ZNEO® Z16F Series MCUs
Product Specification
3
ZNEO CPU Features
Zilog’s ZNEO® CPU meets the continuing demand for faster and more code-efficient
microcontrollers. The ZNEO CPU features are as follows:
•
16MB of program memory address space for object code and data with 8-bit or 16-bit
data paths
•
•
•
8-bit, 16-bit and 32-bit ALU operations
24-bit stack with overflow protection
Direct register-to-register architecture allows each memory address to function as an
accumulator to improve execution time and decrease the required program memory
•
•
New instructions improve execution efficiency for code developed using higher-level
programming languages including ‘C’
Pipelined instructions: Fetch, Decode and Execute
For more information about the ZNEO CPU, refer to the ZNEO CPU Core User Manual
(UM0188), available for download at www.zilog.com.
External Interface
The external interface allows seamless connection to external memory and peripherals. A
24-bit address bus and a selectable 8-bit or 16-bit data bus allows parallel access up to
16MB. The programmable nature of the external interface supports connection to various
bus styles. More GPIO pins are utilized by controlling address and control signals bitwise.
Flash Controller
The Motor Control MCUs products contain 128 KB of internal Flash memory. The Flash
controller programs and erases the Flash memory. ZNEO CPU accesses 16-bits at a time
of internal Flash memory to improve the processor throughput. A sector protection
scheme allows flexible protection of user code.
Random Access Memory
An internal RAM of 4 KB provides storage space for data, variables and stack operations.
Like Flash memory, ZNEO CPU accesses 16-bits at a time of internal RAM to improve
the processor performance.
ZNEO Peripheral Overview
The peripheral features of the ZNEO CPU are described in this section.
PS022010-0811
P R E L I M I N A R Y
ZNEO CPU Features
ZNEO® Z16F Series MCUs
Product Specification
4
10-Bit Analog-to-Digital Converter with Programmable Gain
Amplifier
The ADC converts an analog input signal to a 10-bit binary number. The ADC accepts
inputs from 12 different analog input sources.
Analog Comparator
It features an on-chip analog comparator with external input pins.
Operational Amplifier
It features a two-input, one-output operational amplifier.
General-Purpose Input/Output
The Motor Control MCUs features 76 GPIO pins. Each pin is individually programmable.
Universal Asynchronous Receiver/Transmitter
It contains two fully-featured UARTs with LIN protocol support. The UART communica-
tion is full-duplex and capable of handling asynchronous data transfers. The UARTs sup-
port 8-bit and 9-bit data modes, selectable parity and an efficient bus transceiver driver
enable signal for controlling a multi-transceiver bus, such as RS-485.
Infrared Encoder/Decoders
The ZNEO Z16F Series products contain two fully-functional, high-performance UART
to Infrared Encoder/Decoders (Endecs). Each infrared endec is integrated with an on-chip
UART to allow easy communication between the ZNEO Z16F Series device and IrDA
physical layer specification Version 1.3-compliant infrared transceivers. Infrared commu-
nication provides secure, reliable, low-cost and point-to-point communication between
PCs, PDAs, cell phones, printers and other infrared enabled devices.
Inter-Integrated Circuit Master/Slave Controller
The I2C controller makes Z16F2811 compatible with the I2C protocol. It consists of two
bidirectional bus lines, a serial data (SDA) line and a serial clock (SCL) line. The I2C
operates as a Master and/or Slave and supports multi-master bus arbitration.
Enhanced Serial Peripheral Interface
The ESPI allows the data exchange between ZNEO Z16F Series and other peripheral
devices such as electrically erasable programmable read-only memory (EEPROMs),
PS022010-0811
P R E L I M I N A R Y
10-Bit Analog-to-Digital Converter with
ZNEO® Z16F Series MCUs
Product Specification
5
ADCs and integrated service digital network (ISDN) devices. The SPI is a full-duplex,
synchronous, character-oriented channel which supports a four-wire interface.
DMA Controller
The Motor Control MCUs features a 4-channel DMA for efficient transfer of data between
peripherals and/or memories. The DMA Controller supports data transfers to and from
both internal and external devices.
Pulse Width Modulator
The Motor Control MCUs features a flexible PWM module with three complementary
pairs or six independent PWM outputs supporting deadband operation and fault protection
trip input. These features provide multiphase control capability for a variety of motor
types and ensure safe operation of the motor by providing immediate shutdown of the
PWM pins during Fault condition.
Standard Timers
Three 16-bit reloadable timers are used for timing/counting events and PWM signal gener-
ation. These timers provide a 16-bit programmable reload counter and operate in ONE-
SHOT, CONTINUOUS, GATED, CAPTURE, COMPARE, CAPTURE and COMPARE
and PWM modes. The PWM function provides two complementary output signals with
programmable dead-time insertion.
Interrupt Controller
The Motor Control MCUs products support three levels of programmable interrupt prior-
ity. The interrupt sources include internal peripherals, GPIO pins and system fault detec-
tion.
Crystal Oscillator
The on-chip crystal oscillator features programmable gain to support crystals and ceramic
resonators from 32 kHz to 20 MHz. The oscillator is also used with external RC networks
or clock drivers.
Reset Controller
The Motor Control MCUs is reset using the RESET pin, POR, WDT, Stop Mode Recov-
ery or VBO warning signal. The bidirectional RESET pin also provides a system RESET
output indicator.
PS022010-0811
P R E L I M I N A R Y
DMA Controller
ZNEO® Z16F Series MCUs
Product Specification
6
On-Chip Debugger
The ZNEO Z16F Series features an integrated OCD. The OCD provides a rich-set of
debugging capabilities, such as reading and writing memory, programming the Flash, set-
ting breakpoints and executing code. A single-pin interface provides communication to
the OCD.
PS022010-0811
P R E L I M I N A R Y
On-Chip Debugger
ZNEO® Z16F Series MCUs
Product Specification
7
Signal and Pin Descriptions
The ZNEO® Z16F Series products are available in various package styles and pin config-
urations. This chapter describes the signals and available pin configurations for each pack-
age style. For more information about the physical package specifications, see the
Packaging chapter on page 355.
Available Packages
Table 1 lists the package styles available for each device within the ZNEO Z16F Series
product line.
Table 1. ZNEO Z16F Series Package Options
64-pin
LQFP
68-pin
PLCC
80-Pin
QFP
100-pin
LQFP
Part Number
Z16F2811
Z16F2810*
Z16F6411
Z16F3211
X
X
X
X
X
X
X
X
X
Note: *The Z16F2810 MCU does not feature an external bus interface.
Pin Configurations
Figures 2 through 5 display the configurations of all of the packages available in the
ZNEO Z16F Series. For description of each signal, see Table 2 on page 12.
PS022010-0811
P R E L I M I N A R Y
Signal and Pin Descriptions
ZNEO® Z16F Series MCUs
Product Specification
8
40
48
PA0/T0IN/T0OUT 49
33
32 PA7/SDA
PD6/CTS1
PC3/SCK
PD7/PWML2
PD2/PWMH2
PC2/SS
RESET
VDD
VSS
PE5
PE4
PE6
PE3
25
PE7
VSS
56
VDD
PE2
PE1
PG3
VDD
PE0
PC7/T2OUT/PWML0
PC6/T2IN/T2OUT/PWMH0
DBG
VSS
PD1/PWML1
PD0/PWMH1
XOUT
PC1/T1OUT/COMPOUT
XIN 64
17 PC0/T1IN/T1OUT/CINN
16
1
8
Figure 2. Z16F2810 MCU, 64-Pin Low-Profile Quad Flat Package (LQFP)
PS022010-0811
P R E L I M I N A R Y
Pin Configurations
ZNEO® Z16F Series MCUs
Product Specification
9
9
1
61
60 PA7/SDA
PD6/CTS1
PA0/T0IN/T0OUT 10
PD2/PWMH2
PC2/SS
RESET
VDD
PC3/SCK
PD7/PWML2
VSS
PE5
PE6
PE7
PE4
PE3
VSS
52
18
VDD
PE2
PE1
PE0
PG3
VDD
PC7/T2OUT/PWML0
VSS
PC6/T2IN/T2OUT/PWMH0
DBG
VDD
PD1/PWML1
PD0/PWMH1
XOUT
PC1/T1OUT/COMPOUT
PC0/T1IN/T1OUT/CINN
XIN 26
27
44 VSS
43
35
Figure 3. Z16F2810 MCU, 68-Pin Plastic Leaded Chip Carrier (PLCC)
PS022010-0811
P R E L I M I N A R Y
Pin Configurations
ZNEO® Z16F Series MCUs
Product Specification
10
80
65
64
75
70
PA7/SDA/CS4
PA0/T0IN/T0OUT/DMA0REQ
PD2/PWMH2/ADR22
PC2/SS/CS4
PF6/ADR6
RESET
1
5
PD6/CTS1/ADR17
PC3/SCK/DMA2REQ
PD7/PWML2/ADR23
PG0/ADR8
VSS
PG1/ADR9
60
55
50
VDD
PF5/ADR5
PF4/ADR4
PF3/ADR3
PE4/DATA4
PE3/DATA3
VSS
PE2/DATA2
PE1/DATA1
PE0/DATA0
VSS
PG2/ADR10
PE5/DATA5
PE6/DATA6
PE7/DATA7
10
15
VDD
PG3/ADR11
PG4/ADR12
PG5/ADR13
PG6/ADR14
VDD
PG7/ADR15
PF2/ADR2
PF1/ADR1
PF0/ADR0
VDD
PC7/T2OUT/PWML0
PC6/T2IN/T2OUT/PWMH0
DBG
45
41
20
24
PD1/PWML1/ADR21
PD0/PWMH1/ADR20
XOUT
PC1/T1OUT/DMA1ACK/COMPOUT
PC0/T1IN/T1OUT/DMA1REQ/CINN
VSS
XIN
25
40
30
35
Figure 4. ZNEO Z16F Series, 80-Pin Quad Flat Package (QFP)
PS022010-0811
P R E L I M I N A R Y
Pin Configurations
ZNEO® Z16F Series MCUs
Product Specification
11
100
1
80
95
76
90
85
75
PA0 /T0IN/T0OUT/ DMA0REQ
PD2/PWMH2/ADR22
PC2/SS/CS4
PA6/SCL/CS3
PA7/SDA/CS4
PD6/CTS1/ADR17
PC3/SCK/DMA2REQ
PD7/PWML2/ADR23
PF6/ADR6
RESET
5
VDD
PF5/ADR5
PF4/ADR4
PF3/ADR3
PE4/DATA4
PE3/DATA3
VSS
PG0/ADR8
VSS
70
65
60
PG1/ADR9
PG2/ADR10
10
PE5/DATA5
PE6/DATA6
PE7/DATA7
PE2/DATA2
PE1/DATA1
PE0/DATA0
VSS
VDD
PG3/ADR11
PG4/ADR12
15
20
PG5/ADR13
PF2/ADR2
PF1/ADR1
PF0/ADR0
VDD
PG6/ADR14
VDD
PG7/ADR15
PC7/T2OUT/PWML0
PC6/T2IN/T2OUT/PWMH0
DBG
PD1/PWML1/ADR21
PD0/PWMH1/ADR20
XOUT
55
PC1/T1OUT/DMA1ACK/COMPOUT
PC0/T1IN/T1OUT/DMA1REQ/CINN
VSS
XIN
VSS
25
26
51
50
35
30
40
45
Figure 5. ZNEO Z16F Series, 100-Pin Low-Profile Quad Flat Package (LQFP)
PS022010-0811
P R E L I M I N A R Y
Pin Configurations
ZNEO® Z16F Series MCUs
Product Specification
12
Signal Descriptions
Table 2 describes the ZNEO signals. To determine the signals available for the specific
package styles, see the Pin Configurations section on page 7. Most of the signals described
in Table 2 are multiplexed with GPIO pins. These signals are available as alternate func-
tions on the GPIO pins. For more details about the GPIO alternate functions, see the Gen-
eral-Purpose Input/Output chapter on page 66.
Table 2. Signal Descriptions
Signal Mnemonic
I/O
Description
General-Purpose Input/Output Ports A–K
PA[7:0]
PB[7:0]
PC[7:0]
PD[7:0]
PE[7:0]
PF[7:0]
PG[7:0]
PH[3:0]
PJ[7:0]
PK[7:0]
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
Port A[7:0]: These pins are used for GPIO
Port B[7:0]: These pins are used for GPIO
Port C[7:0]: These pins are used for GPIO
Port D[7:0]: These pins are used for GPIO
Port E[7:0]: These pins are used for GPIO
Port F[7:0]: These pins are used for GPIO
Port G[7:0]: These pins are used for GPIO
Port H[3:0]: These pins are used for GPIO
Port J[7:0]: These pins are used for GPIO
Port K[7:0]: These pins are used for GPIO
External Interface
ADR[23:0]
O
Address bus: When the associated GPIO pins are configured for
alternate function and the external interface is enabled, these pins
function as output pin only. The address bus signals are driven to
0, when execution is out of internal program memory. The address
bus alternate functions are individually enabled and disabled.
DATA[15:0]
I/O
Data bus: When the associated GPIO pins are configured for alter-
nate function and the external interface is enabled, these pins
functions as input/output. The data bus alternate functions are indi-
vidually enabled and disabled. When write operation is not per-
formed through the external interface, these signals are tri-stated.
The data bus is enabled as either 8-bits (DATA[7:0] only) or 16-bits
(DATA[15:0]).
RD
O
Read output: This pin is the Read output signal from the external
interface. Assertion of the RD signal indicates that the ZNEO CPU
is performing a read operation from the external memory or periph-
eral.
PS022010-0811
P R E L I M I N A R Y
Signal Descriptions
ZNEO® Z16F Series MCUs
Product Specification
13
Table 2. Signal Descriptions (Continued)
I/O Description
Signal Mnemonic
WR
O
Write output: This pin is the Write output signal from the external
interface. Assertion of the WR signal indicates that the ZNEO CPU
is performing a write operation to the external memory or periph-
eral.
CS0/CS1/CS2
CS3/CS4/CS5
O
Chip select outputs: These pins are the chip select output signals
from the external interface. The CS output pins have programma-
ble polarity through the external interface control register.
BHEN/BLEN
WAIT
O
I
Byte high enable and byte low enable indicators.
Wait input: Asserting this input signal will pause the CPU to pro-
vide slower external peripherals more time to complete bus trans-
actions through the external interface.
Direct Memory Access Controller
DMA0REQ
DMA1REQ
DMA2REQ
I
DMA request inputs: Each of the DMA channels have an external
request input which allows external peripherals to request access
to the address and data buses for data transfer.
DMA0ACK
DMA1ACK
DMA2ACK
O
DMA request outputs: Each of the DMA channels have an
acknowledge indicator output to notify external peripherals that
their request for access to address and data buses has been
approved.
Inter-Integrated Circuit Controller
2
SCL
I/O
Serial clock: an input or an output clock for the I C. When the
GPIO pin is configured for alternate function to enable the SCL
function, this pin is open-drain.
SDA
I/O
Serial data: This open-drain pin transfers data between the I2C
and a slave. When the GPIO pin is configured for alternate func-
tion to enable the SDA function, this pin is open-drain.
Enhanced Serial Peripheral Interface Controller
I/O
Slave select: This signal is an output or an input. If ZNEO is the
SPI master, this pin is configured as the slave select output. If
ZNEO is the SPI slave, this pin is an input slave select.
SS
SCK
I/O
SPI serial clock: The SPI master supplies this pin. If the ZNEO
Z16F Series device is the SPI master, this pin is an output. If the
ZNEO Z16F Series device is the SPI slave, this pin is an input.
MOSI
MISO
I/O
I/O
Master-Out/Slave-In: This signal is the data output from the SPI
master device and the data input to the SPI slave device.
Master-In/Slave-Out: This pin is the data input to the SPI master
device and the data output from the SPI slave device.
PS022010-0811
P R E L I M I N A R Y
Signal Descriptions
ZNEO® Z16F Series MCUs
Product Specification
14
Table 2. Signal Descriptions (Continued)
I/O Description
Signal Mnemonic
UART Controllers
TXD0/TXD1
O
I
Transmit data: These signals transmit outputs from the UARTs.
RXD0/RXD1
Receive data: These signals receives inputs for the UARTs and
IrDAs.
CTS0/CTS1
DE0/DE1
I
Clear to Send: These signals are control inputs for the UARTs.
O
Driver Enable (DE): This signal allows automatic control of exter-
nal RS-485 drivers. This signal is approximately the inverse of the
Transmit Empty (TXE) bit in the UART Status 0 Register. The DE
signal is used to ensure an external RS-485 driver is enabled
when data is transmitted by the UART.
General-Purpose Timers
T0OUT/T0OUT
T1OUT/T1OUT
T2OUT/T2OUT
O
I
General-purpose timer outputs: These signals are output pins from
the timers.
T0IN/T0IN1/T0IN2
/T1IN/T2IN
General-purpose timer inputs: These signals are used as the cap-
ture, gating and counter inputs.
Pulse-Width Modulator for Motor Control
PWMH0/PWMH1/
PWMH2
O
O
I
PWM High output.
PWML0/PWML1/
PWML2
PWM Low output.
FAULT0/FAULTY
PWM Fault condition input: FAULT0 and FAULTY are active Low.
Analog
ANA[11:0]
VREF
I
I
Analog input: These signals are inputs to the ADC.
ADC reference voltage input or internal reference output:
The VREF pin must be capacitively coupled to analog ground, if
the internal voltage reference is selected as the ADC reference
voltage. A 10 mF capacitor is recommended.
CINP
I
I
Comparator positive input
Comparator negative input
Comparator output
CINN
COMPOUT
OPINP
OPINN
OPOUT
O
I
Operational amplifier positive input
Operational amplifier negative input
Operational amplifier output
I
O
PS022010-0811
P R E L I M I N A R Y
Signal Descriptions
ZNEO® Z16F Series MCUs
Product Specification
15
Table 2. Signal Descriptions (Continued)
I/O Description
Signal Mnemonic
Oscillators
X
I
External crystal input: the input pin to the crystal oscillator.
A crystal is connected between it and the X pin to form the
IN
OUT
oscillator. In addition, this pin is used with external RC networks or
external clock drivers to provide the system clock to the system.
X
O
External crystal output: This pin is the output of crystal oscillator. A
OUT
crystal is connected between it and the X pin to form the oscilla-
IN
tor. This pin must be left unconnected when not using a crystal.
On-Chip Debugger
DBG
I/O
Debug: This pin is the control and data input and output to and
from the OCD.
Caution: For operation of the OCD, all power pins (V and
DD
AVDD) must be supplied with power and all ground pins (V and
SS
AVSS) must be grounded. This pin is open-drain and must have an
external pull-up resistor to ensure proper operation.
Reset
RESET
I/O
RESET: Bidirectional RESET signals generates a Reset when
asserted (driven Low) and drives a Low output when the ZNEO is
in Reset.
Power Supply
V
I
I
I
I
Power supply
Analog power supply
Ground
DD
AV
DD
SS
V
SS
AV
Analog ground
PS022010-0811
P R E L I M I N A R Y
Signal Descriptions
ZNEO® Z16F Series MCUs
Product Specification
16
Pin Characteristics
Table 3 provides information about the characteristics of each pin available on the ZNEO
products. The data in Table 3 are sorted alphabetically by pin symbol mnemonic.
Table 3. Pin Characteristics of the ZNEO CPU
Internal
Tri–State Pull-up or
Schmitt
Trigger
Input
Symbol
Reset
Active
Open Drain
Output
Mnemonic Direction Direction Low/High Output
Pull-down
AV
AV
N/A
N/A
I/O
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Yes
Yes
No
No
N/A
N/A
Yes
DD
SS
N/A
No
No
DBG
I
I
Pull-up
Yes
Yes
PA[7:0]
I/O
Pull-up, pro-
grammable
Yes,
programmable
PB[7:0]
PC[7:0]
PD[7:0]
PE[7:0]
PF[7:0]
PG[7:0]
PH[3:0]
PJ[7:0]
PK[7:0]
RESET
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
I
I
I
I
I
I
I
I
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Pull-up,
programmable
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
Pull-up,
programmable
Yes,
programmable
I/O
I/O
N/A
N/A
I
I
Low
N/A
N/A
N/A
N/A
N/A
N/A
Yes
N/A
N/A
N/A
N/A
Pull-up
N/A
No
Yes
No
No
No
No
No
Yes
No
V
V
V
X
X
I
REF
DD
SS
N/A
N/A
I
N/A
N/A
N/A
No
No
No
IN
O
O
No
OUT
Note: X represents integers 0, 1,... to indicate multiple pins with symbol mnemonics which differ only by an integer.
PS022010-0811
P R E L I M I N A R Y
Pin Characteristics
ZNEO® Z16F Series MCUs
Product Specification
17
Address Space
The ZNEO CPU features a unique architecture with a single, unified 24-bit address space.
It supports up to four memory areas:
•
•
•
•
Internal nonvolatile memory (Flash, EEPROM, EPROM or ROM).
Internal RAM.
Internal I/O memory (internal peripherals).
External memory (and/or memory-mapped peripherals).
The 24-bit address space supports up to 16MB (16,777,216 bytes) of memory. The ZNEO
CPU accesses any two of the above memory areas in parallel. In addition, the ZNEO CPU
supports three different data widths:
•
•
•
Byte (8-bit)
Word (16-bit)
Quad (32-bit)
The ZNEO CPU accesses memories of different bus width:
•
•
8-bit wide memories
16-bit wide memories
Memory Map
The memory map of the ZNEO CPU displayed in Figure 6 shows the locations of internal
nonvolatile memory, internal RAM and internal I/O memory. External memory, however,
is placed at addresses which are not occupied by internal memory.
PS022010-0811
P R E L I M I N A R Y
Address Space
ZNEO® Z16F Series MCUs
Product Specification
18
FF_FFFFH - Top of I/O Memory
Internal I/O Memory
External Memory
Internal RAM
FF_E000H - Bottom of I/O Memory
FF_DFFFH
FF_C000H
FF_BFFFH - Top of Internal RAM
XX_XXXXH - Bottom of Internal RAM
(device specific)
External Memory
XX_XXXXH - Top of Internal nonvolatile Memory
(device specific)
Internal nonvolatile
Memory
00_0000H - Bottom of Internal nonvolatile Memory
Figure 6. Physical Memory Map
To determine the amount of internal RAM and internal nonvolatile memory available for
the specific device, see the Ordering Information section on page 359.
Internal Nonvolatile Memory
Internal nonvolatile memory contains executable program code, constants and data. For
each product within the ZNEO CPU family, a memory block beginning at address
00_0000His reserved for user option bits and system vectors (for example, RESET, Trap,
Interrupts and System Exceptions, etc.). Table 4 provides an example of reserved memory
map for a ZNEO CPU product with 24 interrupt vectors.
PS022010-0811
P R E L I M I N A R Y
Internal Nonvolatile Memory
ZNEO® Z16F Series MCUs
Product Specification
19
Table 4. Reserved Memory Map Example
Memory Address (Hex)
Description
Option bits
00_0000–00_0003
00_0004–00_0007
00_0008–00_000B
00_000C–00_000F
00_0010–00_006F
RESET vector
System exception vector
Privileged trap vector
Interrupt vectors
Internal RAM
Internal RAM is mainly employed for data and stacks. However, internal RAM also con-
tains program code for execution. Most ZNEO CPU devices contain some internal RAM.
The top (highest address) of internal RAM is always located at address FF_BFFFH. The
bottom (lowest address) of internal RAM is a function of the amount of internal RAM
available. To determine the amount of internal RAM available, see the Ordering Informa-
tion section on page 359.
Input/Output Memory
The ZNEO CPU supports 8 KB (8,192 bytes) of I/O memory space located at addresses
FF_E000Hthrough FF_FFFFH. The I/O memory addresses are reserved for control of the
ZNEO CPU, the on-chip peripherals and the I/O ports. Refer to the device-specific Prod-
uct Specification for descriptions of the peripheral and I/O control registers. Attempts to
read or execute from unavailable I/O memory addresses returns FFH. Attempts to write to
unavailable I/O memory addresses produce no effect.
Input/Output Memory Precautions
Some control registers within the I/O memory provide read-only or write-only access.
When accessing these read-only or write-only registers, ensure that the instructions do not
attempt to read from a write-only register or conversely write to a read-only register.
CPU Control Registers
Some registers are reserved within 8KB of I/O memory for ZNEO CPU control; these
ZNEO CPU Control registers are listed in Table 5. For information about the operation of
the ZNEO CPU Control registers, refer to the ZNEO CPU Core User Manual (UM0188),
available for download at www.zilog.com.
PS022010-0811
P R E L I M I N A R Y
Internal RAM
ZNEO® Z16F Series MCUs
Product Specification
20
Table 5. ZNEO CPU Control Registers
Address (Hex)
FF_E004-FF_E007
FF_E00C-FF_E00F
FF_E010
Register Description
Program counter overflow
Stack pointer overflow
Flags
Register Mnemonic
PCOV
SPOV
FLAGS
CPUCTL
FF_E012
CPU control
External Memory
Many ZNEO CPU products support external data and address buses for connecting to
additional external memories and/or memory-mapped peripherals. The external addresses
are used for storing program code, data, constants and stack, etc. Attempts to read from or
write to unavailable external addresses is undefined.
Endianness
The ZNEO CPU accesses data in big endian order, that is, the address of a multi-byte word
or quad points to the most significant byte. Figure 7 displays the Endianness of the ZNEO
CPU.
PS022010-0811
P R E L I M I N A R Y
External Memory
ZNEO® Z16F Series MCUs
Product Specification
21
LSB
00_0081H
00_0080H
Address
of Word
MSB
00_0083H
LSB
00_0082H
00_0081H
00_0080H
Address
of Quad
MSB
Figure 7. Endianness of Words and Quads
Bus Widths
The ZNEO CPU accesses 8-bit or 16-bit memories. The data buses of the internal nonvol-
atile memory and internal RAM are 16-bit wide. The internal peripherals are a mix of 8-bit
and 16-bit peripherals. The external memory bus is configured as an 8-bit or 16-bit mem-
ory bus.
If a Word or Quad operation occurs on a 16-bit wide memory, the number of memory
accesses depends on the alignment of the address. If the address is aligned on an even
boundary, a Word operation takes one memory access and a Quad operation takes two
memory accesses. If the address is on an odd boundary (unaligned), a Word operation
takes two memory accesses and a Quad operation takes three memory accesses. Figure 8
displays the alignment Word and Quad operations on 16-bit memories.
PS022010-0811
P R E L I M I N A R Y
Bus Widths
ZNEO® Z16F Series MCUs
Product Specification
22
000082H
000080H
000083H
LSB
000080H
LSB 000081H
MSB 000081H
MSB
Aligned Word Access
Unaligned Word Access
000084H
LSB
000085H
000083H
000082H
000080H MSB
LSB 000083H
000082H
000080H
000081H
MSB 000081H
Aligned Quad Access
Unaligned Quad Access
Figure 8. Alignment of Word and Quad Operations on 16-bit Memories
PS022010-0811
P R E L I M I N A R Y
Bus Widths
ZNEO® Z16F Series MCUs
Product Specification
23
Peripheral Address Map
Table 6 provides the address map for the peripheral space of the ZNEO® Z16F Series of
products. Not all devices and package styles in the ZNEO Z16F Series support all periph-
erals or all GPIO ports. Registers for unimplemented peripherals are considered as
reserved.
Table 6. Register File Address Map
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
ZNEO CPU Base Address = FF_E000
FF_E004-FF_E007
FF_E00C-FF_E00F
FF_E010
Program Counter Overflow
PCOV
SPOV
00FFFFFF
00000000
XX
Refer to
the ZNeo
CPU
User
Manual
Stack Pointer Overflow
Flags
FLAGS
CPUCTL
FF_E012
CPU Control
00
ZNEO Trace Address = FF_E014
FF_E013
Trace Control
Trace Address
TRACECTL
00
324
325
FF_E014-FF_E017
TRACEADDR
XXXXXXXX
Interrupt Controller Base Address = FF_E020
FF_E020
System Exception Status High
SYSEXCPH
SYSEXCPL
—
0000
0000
XX
84
84
—
FF_E021
System Exception Status Low
Reserved
FF_E022
FF_E023
Last IRQ Register
LASTIRQ
—
02
85
—
FF_E024-FF_E02F
FF_E030
Reserved
—
Interrupt Request 0
Interrupt Request 0 Set
IRQ0 Enable High Bit
IRQ0 Enable Low Bit
Interrupt Request 1
Interrupt Request 1Set
IRQ1 Enable High Bit
IRQ1 Enable Low Bit
Interrupt Request 2
Interrupt Request 2 Set
IRQ2 Enable High Bit
IRQ0
00
86
86
90
90
87
87
91
91
88
89
92
FF_E031
IRQ0SET
IRQ0ENH
IRQ0ENL
IRQ1
xx
FF_E032
00
FF_E033
00
FF_E034
00
FF_E035
IRQ1SET
IRQ1ENH
IRQ1ENL
IRQ2
XX
FF_E036
00
FF_E037
00
FF_E038
00
FF_E039
IRQ2SET
IRQ2ENH
xx
FF_E03A
00
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
24
Table 6. Register File Address Map (Continued)
Address (Hex)
FF_E03B
Register Description
IRQ2 Enable Low Bit
Reserved
Mnemonic
IRQ2ENL
—
Reset (Hex) Page No
00
XX
92
—
FF_E03C-FF_E03F
Watchdog Timer Base Address = FF_E040
FF_E040-FF_E041
FF_E042
Reserved
—
—
—
Watchdog Timer Reload
High Byte
WDTH
04
241
FF_E043
Watchdog Timer Reload
Low Byte
WDTL
—
00
241
—
FF_E044-FF_E04F
Reserved
—
Reset Base Address = FF_E050
FF_E050
Reset Status and Control Reg-
ister
RSTSCR
—
XX
XX
62
—
FF_E051-FF_E06F
Reserved
Flash Controller Base Address = FF_E060
FF_E060
Flash Command Register
FCMD
FSTAT
FCTL
XX
00
261
262
263
264
—
FF_E060
Flash Status Register
Flash Control Register
Flash Sector Protect Register
Reserved
FF_E061
00
FF_E062
FSECT
—
00
FF_E063
XX
FF_E064-FF_E065
FF_E066-FF_E067
Flash Page Select Register
Flash Frequency Register
FPAGE
FFREQ
0000
0000
265
266
External Interface Base Address = FF_E070
FF_E070
External Interface Control
Reserved
EXTCT
—
42
—
FF_E071
—
FF_E072
Chip Select 0 Control High
Chip Select 0 Control Low
Chip Select 1 Control High
Chip Select 1 Control Low
Chip Select 2 Control High
Chip Select 2 Control Low
Chip Select 3 Control High
Chip Select 3 Control Low
Chip Select 4 Control High
EXTCS0H
EXTCS0L
EXTCS1H
EXTCS1L
EXTCS2H
EXTCS2L
EXTCS3H
EXTCS3L
EXTCS4H
43
44
43
45
43
46
43
46
43
FF_E073
FF_E074
FF_E075
FF_E076
FF_E077
FF_E078
FF_E079
FF_E07A
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
25
Table 6. Register File Address Map (Continued)
Address (Hex)
FF_E07B
Register Description
Chip Select 4 Control Low
Chip Select 5 Control High
Chip Select 5 Control Low
Reserved
Mnemonic
EXTCS4L
EXTCS5H
EXTCS5L
—
Reset (Hex) Page No
46
43
46
FF_E07C
FF_E07D
FF_E07E-FF_E07F
—
—
On Chip Debugger = FF_E080
FF_E080
Debug Receive Data
DBGRXD
DBGTXD
DBGBR
XX
XX
315
315
316
316
318
319
FF_E081
Debug Transmit Data
Debug Baud Rate
Debug Line Control
Debug Status
FF_E082-FF_E083
FF_E084
XXXX
XX
DBGLCR
DBGSTAT
DBGCTL
FF_E085
XX
FF_E086
Debug Control
XX
Hardware Breakpoints = FF_E090
FF_E090-FF_E093
FF_E094-FF_E097
FF_E098-FF_E09B
FF_E09C-FF_E09F
Hardware Breakpoint 0
HWBP0
HWBP1
HWBP2
HWBP3
00000000
00000000
00000000
00000000
323
323
323
323
Hardware Breakpoint 1
Hardware Breakpoint 2
Hardware Breakpoint 3
Oscillator Control Base Address = FF_E0A0
FF_E0A0
FF_E0A1
Oscillator Control
Oscillator Divide
OSCCTL
OSCDIV
A0
00
333
334
GPIO Base Address = FF_E100
GPIO Port A Base Address = FF_E100
FF_E100
FF_E101
FF_E102
FF_E103
FF_E104
FF_E105
FF_E106
FF_E107
FF_E108
Port A Input Data
PAIN
PAOUT
PADD
XX
00
00
00
00
00
00
00
00
71
72
73
74
75
75
76
76
77
Port A Output Data
Port A Data Direction
Port A High Drive Enable
Port A Alternate Function High
Port A Alternate Function Low
Port A Output Control
Port A Pull-Up Enable
PAHDE
PAAFH
PAAFL
PAOC
PAPUE
PASMRE
Port A Stop Mode Recovery
Enable
FF_E109-FF_E10B
Port A Reserved
—
—
—
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
26
Table 6. Register File Address Map (Continued)
Address (Hex)
FF_E10C
Register Description
Port A IRQ MUX1
Port A Reserved
Port A IRQ MUX
Port A IRQ Edge
Mnemonic
PAIMUX1
—
Reset (Hex) Page No
00
—
77
—
78
78
FF_E10D
FF_E10E
PAIMUX
PAIEDGE
00
00
FF_E10F
GPIO Port B Base Address = FF_E110
FF_E110
FF_E111
FF_E112
FF_E113
FF_E114
FF_E115
FF_E116
FF_E117
FF_E118
Port B Input Data
PBIN
PBOUT
PBDD
XX
00
00
00
—
71
72
73
74
—
Port B Output Data
Port B Data Direction
Port B High Drive Enable
Reserved
PBHDE
—
Port B Alternate Function Low
Port B Output Control
Port B Pull-Up Enable
PBAFL
PBOC
PBPUE
PBSMRE
00
00
00
00
75
76
76
77
Port B Stop Mode Recovery
Enable
FF_E119-FF_E11F
Port B Reserved
—
—
—
GPIO Port C Base Address = FF_E120
FF_E120
FF_E121
FF_E122
FF_E123
FF_E124
FF_E125
FF_E126
FF_E127
FF_E128
Port C Input Data
PCIN
PCOUT
PCDD
XX
00
00
00
00
00
00
00
00
71
72
73
74
75
76
76
76
77
Port C Output Data
Port C Data Direction
Port C High Drive Enable
Port C Alternate Function High
Port C Alternate Function Low
Port C Output Control
Port C Pull-Up Enable
PCHDE
PCAFH
PCAFL
PCOC
PCPUE
PCSMRE
Port C Stop Mode Recovery
Enable
FF_E129-FF_E12D
FF_E12E
Port C Reserved
Port C IRQ MUX
Port C Reserved
—
PCIMUX
—
—
00
—
—
79
—
FF_E12F
GPIO Port D Base Address = FF_E130
FF_E130
Port D Input Data
PDIN
XX
00
71
72
FF_E131
Port D Output Data
PDOUT
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
27
Table 6. Register File Address Map (Continued)
Address (Hex)
FF_E132
FF_E133
FF_E134
FF_E135
FF_E136
FF_E137
FF_E138
Register Description
Mnemonic
PDDD
Reset (Hex) Page No
Port D Data Direction
00
00
00
00
00
00
00
73
74
75
76
76
76
77
Port D High Drive Enable
Port D Alternate Function High
Port D Alternate Function Low
Port D Output Control
PDHDE
PDAFH
PDAFL
PDOC
Port D Pull-Up Enable
PDPUE
PDSMRE
Port D Stop Mode Recovery
Enable
FF_E139-FF_E13F
Port D Reserved
—
—
—
GPIO Port E Base Address = FF_E140
FF_E140
FF_E141
FF_E142
FF_E143
FF_E144
FF_E145
FF_E146
FF_E147
FF_E148
Port E Input Data
Port E Output Data
Port E Data Direction
Port E High Drive Enable
Reserved
PEIN
PEOUT
PEDD
PEHDE
—
XX
00
00
00
—
71
72
73
74
—
—
76
76
77
Reserved
—
—
Port E Output Control
Port E Pull-Up Enable
PEOC
PEPUE
PESMRE
00
00
00
Port E Stop Mode Recovery
Enable
FF_E149-FF_E14F
Port E Reserved
—
—
—
GPIO Port F Base Address = FF_E150
FF_E150
FF_E151
FF_E152
FF_E153
FF_E154
FF_E155
FF_E156
FF_E157
FF_E158
Port F Input Data
PFIN
PFOUT
PFDD
XX
00
00
00
—
71
72
73
74
—
Port F Output Data
Port F Data Direction
Port F High Drive Enable
Reserved
PFHDE
—
Port F Alternate Function Low
Port F Output Control
Port F Pull-Up Enable
PFAFL
PFOC
PFPUE
PFSMRE
00
00
00
00
76
76
76
77
Port F Stop Mode Recovery
Enable
FF_E159-FF_E15F
Port F Reserved
—
—
—
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
28
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
GPIO Port G Base Address = FF_E160
FF_E160
FF_E161
FF_E162
FF_E163
FF_E164
FF_E165
FF_E166
FF_E167
FF_E168
Port G Input Data
PGIN
PGOUT
PGDD
PGHDE
—
XX
00
00
00
—
71
72
73
74
—
Port G Output Data
Port G Data Direction
Port G High Drive Enable
Reserved
Port G Alternate Function Low
Port G Output Control
Port G Pull-Up Enable
PGAFL
PGOC
PGPUE
PGSMRE
00
00
00
00
76
76
76
77
Port G Stop Mode Recovery
Enable
FF_E169-FF_E16F
Port G Reserved
—
—
—
GPIO Port H Base Address = FF_E170
FF_E170
FF_E171
FF_E172
FF_E173
FF_E174
FF_E175
FF_E176
FF_E177
FF_E178
Port H Input Data
PHIN
PHOUT
PHDD
XX
00
00
00
00
00
00
00
00
71
72
73
74
75
76
76
76
77
Port H Output Data
Port H Data Direction
Port H High Drive Enable
Port H Alternate Function High
Port H Alternate Function Low
Port H Output Control
Port H Pull-Up Enable
PHHDE
PHAFH
PHAFL
PHOC
PHPUE
PHSMRE
Port H Stop Mode Recovery
Enable
FF_E179-FF_E17F
Port H Reserved
—
—
—
GPIO Port J Base Address = FF_E180
FF_E180
Port J Input Data
Port J Output Data
Port J Data Direction
Port J High Drive Enable
Reserved
PJIN
PJOUT
PJDD
PJHDE
—
XX
00
00
00
—
71
72
73
74
—
—
76
76
FF_E181
FF_E182
FF_E183
FF_E184
FF_E185
Reserved
—
—
FF_E186
Port J Output Control
Port J Pull-Up Enable
PJOC
PJPUE
00
00
FF_E187
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
29
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
FF_E188
Port J Stop Mode Recovery
Enable
PJSMRE
00
77
FF_E189-FF_E18F
Port J Reserved
—
—
—
GPIO Port K Base Address = FF_E190
FF_E190
FF_E191
FF_E192
FF_E193
FF_E194
FF_E195
FF_E196
FF_E197
FF_E198
Port K Input Data
PKIN
PKOUT
PKDD
XX
00
00
00
—
71
72
73
74
—
Port K Output Data
Port K Data Direction
Port K High Drive Enable
Reserved
PKHDE
—
Port K Alternate Function Low
Port K Output Control
Port K Pull-Up Enable
PKAFL
PKOC
PKPUE
PKSMRE
00
00
00
00
76
76
76
77
Port K Stop Mode Recovery
Enable
FF_E199-FF_E19F
Port K Reserved
—
—
—
Serial Channels Base Address = FF_E200
LIN-UART 0 Base Address = FF_E200
FF_E200
LIN-UART0 Transmit Data
U0TXD
U0RXD
XX
154
154
155
160
164
162
LIN-UART0 Receive Data
LIN-UART0 Status 0
LIN-UART0 Control 0
LIN-UART0 Control 1
XX
FF_E201
FF_E202
FF_E203
FF_E204
U0STAT0
U0CTL0
0000011Xb
00
00
00
U0CTL1
LIN-UART0 Mode Select and
Status
U0MDSTAT
FF_E205
LIN-UART0 Address Compare
Register
U0ADDR
U0BRH
U0BRL
—
00
FF
FF
XX
166
166
167
—
FF_E206
LIN-UART0 Baud Rate High
Byte
FF_E207
LIN-UART0 Baud Rate Low
Byte
FF_E208-FF_E20F
Reserved
LIN-UART 1 Base Address = FF_E210
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
30
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
LIN-UART1 Transmit Data
LIN-UART1 Receive Data
LIN-UART1 Status 0
Mnemonic
U1TXD
Reset (Hex) Page No
FF_E210
XX
154
154
155
160
164
162
U1RXD
XX
FF_E211
FF_E212
FF_E213
FF_E214
U1STAT0
U1CTL0
0000011Xb
LIN-UART1 Control 0
LIN-UART1 Control 1
00
00
00
U1CTL1
LIN-UART1 Mode Select and
Status
U1MDSTAT
FF_E215
FF_E216
FF_E217
LIN-UART1 Address Compare
Register
U1ADDR
U1BRH
U1BRL
—
00
FF
FF
XX
166
166
167
—
LIN-UART1 Baud Rate High
Byte
LIN-UART1 Baud Rate Low
Byte
FF_E218-FF_E23F
Reserved
2
I C Base Address = FF_E240
2
FF_E240
I C Data
I2CDATA
I2CISTAT
I2CCTL
00
80
00
FF
FF
C0
00
00
XX
227
228
229
231
231
232
236
237
—
2
FF_E241
I C Interrupt Status
2
FF_E242
I C Control
2
FF_E243
I C Baud Rate High Byte
I2CBRH
I2CBRL
I2CSTATE
I2CMODE
I2CSLVAD
—
2
FF_E244
I C Baud Rate Low Byte
2
FF_E245
I C State
2
FF_E246
I C Mode
2
FF_E247
I C Slave Address
FF_E248-FF_E25F
Reserved
Enhanced Serial Peripheral Interface Base Address = FF_E260
FF_E260
ESPI Data
ESPIDATA
—
XX
XX
00
00
01
00
FF
FF
193
FF_E261
Reserved
FF_E262
ESPI Control
ESPICTL
ESPIMODE
ESPISTAT
ESPISTATE
ESPIBRH
ESPIBRL
194
197
198
200
202
202
FF_E263
ESPI Mode
FF_E264
ESPI Status
FF_E265
ESPI State
FF_E266
ESPI Baud Rate High Byte
ESPI Baud Rate Low Byte
FF_E267
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
31
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
Timers: Base Address = FFF_E300
Timer 0 (General-Purpose Timer) Base Address = FF_E300
FF_E300
FF_E301
FF_E302
FF_E303
FF_E304
FF_E305
FF_E306
FF_E307
Timer 0 High Byte
T0H
T0L
00
01
FF
FF
00
00
00
00
107
107
108
108
109
109
110
111
Timer 0 Low Byte
Timer 0 Reload High Byte
Timer 0 Reload Low Byte
Timer 0 PWM High Byte
Timer 0 PWM Low Byte
Timer 0 Control 0
T0RH
T0RL
T0PWMH
T0PWML
T0CTL0
T0CTL1
Timer 0 Control 1
Timer 1 (General-Purpose Timer) Base Address = FF_E310
FF_E310
FF_E311
FF_E312
FF_E313
FF_E314
FF_E315
FF_E316
FF_E317
Timer 1 High Byte
T1H
T1L
00
01
FF
FF
00
00
00
00
107
107
108
108
109
109
110
111
Timer 1 Low Byte
Timer 1 Reload High Byte
Timer 1 Reload Low Byte
Timer 1 PWM High Byte
Timer 1 PWM Low Byte
Timer 1 Control 0
T1RH
T1RL
T1PWMH
T1PWML
T1CTL0
T1CTL1
Timer 1 Control 1
Timer 2 (General-Purpose Timer) Base Address = FF_E320
FF_E320
FF_E321
FF_E322
FF_E323
FF_E324
FF_E325
FF_E326
FF_E327
Timer 2 High Byte
T2H
T2L
00
01
FF
FF
00
00
00
00
107
107
108
108
109
109
110
111
Timer 2 Low Byte
Timer 2 Reload High Byte
Timer 2 Reload Low Byte
Timer 2 PWM High Byte
Timer 2 PWM Low Byte
Timer 2 Control 0
T2RH
T2RL
T2PWMH
T2PWML
T2CTL0
T2CTL1
Timer 2 Control 1
Pulse Width Modulator (PWM) Base Address = FF_E380
FF_E380
PWM Control 0
PWM Control 1
PWM Deadband
PWMCTL0
PWMCTL1
PWMDB
00
00
00
125
126
127
FF_E381
FF_E382
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
32
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
FF_E383
PWM Minimum Pulse Width Fil-
ter
PWMMPF
00
128
FF_E384
FF_E385
FF_E386
FF_E387
FF_E388
FF_E389
FF_E38A
PWM Fault Mask
PWM Fault Status
PWM Input Sample Register
PWM Output Control
PWM Fault Control
Reserved
PWMFM
PWMFSTAT
PWMIN
00
00
00
00
00
—
129
130
132
133
131
—
PWMOUT
PWMFCTL
—
Current-Sense Sample and
Hold Control 0
CSSHR0
00
134
FF_E38B
Current-Sense Sample and
Hold Control 1
CSSHR1
00
134
FF_E38C-FF_E38B
FF_E38C
Reserved
—
—
XX
XX
FF
FF
00
—
PWM High Byte
PWMH
122
122
123
123
124
FF_E38D
PWM Low Byte
PWML
FF_E38E
PWM Reload High Byte
PWM Reload Low Byte
PWMRH
PWMRL
PWMH0DH
FF_E38F
FF_E390
PWM 0 High Side Duty Cycle
High Byte
FF_E391
PWM 0 High Side Duty Cycle
Low Byte
PWMH0DL
PWML0DH
PWML0DL
PWMH1DH
PWMH1DL
PWML1DH
PWML1DL
PWMH2DH
00
00
00
00
00
00
00
00
125
124
125
124
125
124
125
124
FF_E392
PWM 0 Low Side Duty Cycle
High Byte
FF_E393
PWM 0 Low Side Duty Cycle
Low Byte
FF_E394
PWM 1 High Side Duty Cycle
High Byte
FF_E395
PWM 1 High Side Duty Cycle
Low Byte
FF_E396
PWM 1 Low Side Duty Cycle
High Byte
FF_E397
PWM 1 Low Side Duty Cycle
Low Byte
FF_E398
PWM 2 High Side Duty Cycle
High Byte
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
33
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
FF_E399
PWM 2 High Side Duty Cycle
Low Byte
PWMH2DL
00
00
00
—
125
124
125
—
FF_E39A
PWM 2 Low Side Duty Cycle
High Byte
PWML2DH
PWML2DL
—
FF_E39B
PWM 2 Low Side Duty Cycle
Low Byte
FF_E39C-FF_E3BF
Reserved for PWM
DMA Block Base Address = FF_E400
DMA Request Selection Control
DMA0 Request Select
DMA0REQSEL
DMA1REQSEL
DMA2REQSEL
DMA3REQSEL
—
00
00
00
00
—
282
282
282
282
—
FF_E400
FF_E401
FF_E402
FF_E403
FF_E404-F
DMA1 Request Select
DMA2 Request Select
DMA3 Request Select
Reserved
DMA Channel 0 Base Address = FF_E410
FF_E410
FF_E411
FF_E412
FF_E413
FF_E414
FF_E415
DMA0 Control 0
DMA0CTL0
DMA0CTL1
DMA0TXLNH
DMA0TXLNL
—
00
00
00
00
—
285
285
286
287
—
DMA0 Control 1
DMA0 Transfer Length High
DMA0 Transfer Length Low
Reserved
DMA0 Destination Address
Upper
DMA0DARU
00
287
FF_E416
FF_E417
DMA0 Destination Address
High
DMA0DARH
DMA0DARL
00
00
287
287
DMA0 Destination Address
Low
FF_E418
Reserved
—
—
00
00
00
—
—
FF_E419
DMA0 Source Address Upper
DMA0 Source Address High
DMA0 Source Address Low
Reserved
DMA0SARU
DMA0SARH
DMA0SARL
—
288
288
288
—
FF_E41A
FF_E41B
FF_E41C
FF_E41D
DMA0 List Address Upper
DMA0 List Address High
DMA0LARU
DMA0LARH
00
00
289
289
FF_E41E
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
34
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
FF_E41F
DMA0 List Address Low
DMA0LARL
00
289
DMA Channel 1 Base Address = FF_E420
FF_E420
FF_E421
FF_E422
FF_E423
FF_E424
FF_E425
DMA1 Control 0
DMA1CTL0
DMA1CTL1
DMA1TXLNH
DMA1TXLNL
—
00
00
00
00
—
285
285
286
287
—
DMA1 Control 1
DMA1 Transfer Length High
DMA1 Transfer Length Low
Reserved
DMA1 Destination Address
Upper
DMA1DARU
00
287
FF_E426
FF_E427
DMA1 Destination Address
High
DMA1DARH
DMA1DARL
00
00
287
287
DMA1 Destination Address
Low
FF_E428
FF_E429
FF_E42A
FF_E42B
FF_E42C
FF_E42D
FF_E42E
FF_E42F
Reserved
—
—
00
00
00
—
—
DMA1 Source Address Upper
DMA1 Source Address High
DMA1 Source Address Low
Reserved
DMA1SARU
DMA1SARH
DMA1SARL
—
288
288
288
—
DMA1 List Address Upper
DMA1 List Address High
DMA1 List Address Low
DMA1LARU
DMA1LARH
DMA1LARL
00
00
00
289
289
289
DMA Channel 2 Base Address = FF_E430
FF_E430
FF_E431
FF_E432
FF_E433
FF_E434
FF_E435
DMA2 Control 0
DMA2CTL0
DMA2CTL1
DMA2TXLNH
DMA2TXLNL
—
00
00
00
00
—
285
285
286
287
—
DMA2 Control 1
DMA2 Transfer Length High
DMA2 Transfer Length Low
Reserved
DMA2 Destination Address
Upper
DMA2DARU
00
287
FF_E436
FF_E437
DMA2 Destination Address
High
DMA2DARH
DMA2DARL
—
00
00
—
287
287
—
DMA2 Destination Address
Low
FF_E438
Reserved
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
35
Table 6. Register File Address Map (Continued)
Address (Hex)
FF_E439
FF_E43A
FF_E43B
FF_E43C
FF_E43D
FF_E43E
FF_E43F
Register Description
DMA2 Source Address Upper
DMA2 Source Address High
DMA2 Source Address Low
Reserved
Mnemonic
DMA2SARU
DMA2SARH
DMA2SARL
Reset (Hex) Page No
00
00
00
288
288
288
DMA2 List Address Upper
DMA2 List Address High
DMA2 List Address Low
DMA2LARU
DMA2LARH
DMA2LARL
00
00
00
289
289
289
DMA Channel 3 Base Address = FF_E440
FF_E440
FF_E441
FF_E442
FF_E443
FF_E444
FF_E445
DMA3 Control 0
DMA3CTL0
DMA3CTL1
DMA3TXLNH
DMA3TXLNL
—
00
00
00
00
—
285
285
286
287
—
DMA3 Control 1
DMA3 Transfer Length High
DMA3 Transfer Length Low
Reserved
DMA3 Destination Address
Upper
DMA3DARU
00
287
FF_E446
FF_E447
DMA3 Destination Address
High
DMA3DARH
DMA3DARL
00
00
287
287
DMA3 Destination Address
Low
FF_E448
FF_E449
FF_E44A
FF_E44B
FF_E44C
FF_E44D
FF_E44E
FF_E44F
Reserved
—
—
00
00
00
—
—
DMA3 Source Address Upper
DMA3 Source Address High
DMA3 Source Address Low
Reserved
DMA3SARU
DMA3SARH
DMA3SARL
—
288
288
288
—
DMA3 List Address Upper
DMA3 List Address High
DMA3 List Address Low
DMA3LARU
DMA3LARH
DMA3LARL
00
00
00
289
289
289
Analog Block Base Address = FF_E500
ADC Base Address = FF_E500
FF_E500
ADC0 Control Register
ADC0CTL
—
00
—
246
—
FF_E501
Reserved
FF_E502
ADC0 Data High Byte Register
ADC0 Data Low Bits Register
ADC0D_H
ADC0D_L
XX
XX
247
248
FF_E503
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
36
Table 6. Register File Address Map (Continued)
Address (Hex)
Register Description
Mnemonic
Reset (Hex) Page No
FF_E504
ADC Sample and Settling Time
Register
ADCSST
0F
248
FF_E505
ADC Sample Hold Time
ADC Clock Prescale Register
ADC0 MAX Register
Reserved
ADCST
ADCCP
ADC0MAX
—
3F
00
00
—
249
249
250
—
FF_E506
FF_E507
FF_E508-FF_E50F
FF_E510
Comparator and Op-Amp Con-
trol
CMPOPC
00
253
FF_E511
FF_E512
Reserved
—
—
—
ADC Sample Timer Capture
High
ADCTCAPH
XX
251
FF_E513
ADC Sample Timer Capture
Low
ADCTCAPL
—
XX
251
—
Option Trim Registers Base Address = FF_FF00
®
FF_FF00-FF_FF24
Reserved for internal Zilog
use
—
FF_FF25
IPO Trim 1
IPO Trim 2
IPOTRIM1
IPOTRIM2
ADCTRIM
XX
XX
XX
296
296
297
FF_FF26
FF_FF27
ADC Reference Voltage Trim
Note: XX = Undefined.
PS022010-0811
P R E L I M I N A R Y
Peripheral Address Map
ZNEO® Z16F Series MCUs
Product Specification
37
External Interface
The external interface allows seamless connection to external memory and/or peripherals.
The configurable nature of the external interface supports connection with many different
bus styles and signal formats. Bit-wise control of the address, data and control signals
means no wasted GPIO pins. Other features of the external interface includes:
•
•
•
•
•
•
•
Hardware bus controller with programmable signal polarity for chip selects
Programmable wait state generator
Selectable address and data bus widths
Six external chip selects
ISA-compatible mode
External program execution and Stack operations
External WAIT pin for slow peripherals
External Interface Signals
Table 7 lists the external interface signals. The external interface consists of a 24-bit
address bus, an 8-bit/16-bit bidirectional data bus and control signals (Read, Write, Chip
Selects and Wait). It is not necessary to use all pins for proper operation of the external
interface. The external interface signals are enabled pin-by-pin using the GPIO alternate
functions. For more information about GPIO alternate functions, see the General-Purpose
Input/Output section on page 66.
Table 7. External Interface Signals Description
External Interface Signal
DATA[7:0]
DATA[15:8]
ADDR[7:0]
ADDR[15:8]
ADDR[23:16]
WR
Direction
Input/Output
Input/Output
Output
Output
Output
Output
RD
Output
CS0
Output
WAIT
Input
PS022010-0811
P R E L I M I N A R Y
External Interface
ZNEO® Z16F Series MCUs
Product Specification
38
Table 7. External Interface Signals Description (Continued)
External Interface Signal
Direction
Output
Output
Output
Output
Output
CS1
CS2
CS3
CS4
CS5
Chip Selects
The chip selects support connection of multiple memories and peripherals to the external
interface. Figure 9 displays the memory map of the chip selects. The chip select boundar-
ies are at fixed addresses. On-chip memory always have priority over external memory.
Chip select 0 has the lowest priority and chip select 5 has the highest priority.
16 MB
Memory
Addresses
FFFFFFH
CS3–CS5
CS2
Zoom in on CS3–CS5
Addresses
F00000H
EFFFFFH
FFDFFFH
CS5
CS4
CS3
CS1
FFD800H
FFD7FFH
FFD000H
FFCFFFH
800000H
7FFFFFH
CS0
FFC800H
020000H
01FFFFH
000000H
128 KB
Internal Flash
Figure 9. Chip Select Boundary Addressing with 128 KB Internal Flash
PS022010-0811
P R E L I M I N A R Y
Chip Selects
ZNEO® Z16F Series MCUs
Product Specification
39
Table 8. Example Usage of Chip Selects
Chip
Lower
Upper
Select
Memory/Peripheral
Address
Address
Typical Uses
64 KB Internal Flash
000000H
00FFFFH Program Code, Look-up Tables and
Interrupt Vectors.
CS0
CS1
8 MB External ROM
or Flash
010000H
7FFFFFH Program Code and Look-up Tables.
Lowest 64 KB of the 8 MB is inaccessi-
ble as the on-chip Flash has higher pri-
ority for addresses 000000Hthrough
00FFFFH.
128 KB External RAM
080000H
09FFFFH Stack and Data is placed anywhere in
CS1 address space except where
higher priority CS2 or CS3 overlaps.
0AFFFFH
F00000H
0EFFFFH Unused addresses as no external
memory placed in these locations.
CS2
CS3
External Ethernet MAC
External CAN controller.
F3FFFFH Ethernet MAC is an example of an
external communication peripheral that
is connected to the external interface.
FFC800H
F80000H
FFCFFFH CAN controller is another example of
an external communication peripheral
that is connected to the external inter-
face.
FFFFFFH Unused addresses as no external
memory or peripherals placed in these
locations.
Tools Compatibility Guidelines
The external interface offers the designer the flexibility to place external devices in almost
any range of the 24-bit address space. The primary hardware consideration is that more
chip selects are available in high memory and devices needing more than 15 wait states
must use one of chip selects CS[2–5]. After a design is completed, it is necessary to
develop software for it. The task of designing application software is much easier if the
hardware designer considers the following guidelines:
•
The microcontroller’s internal Flash memory must be enabled during software devel-
opment. This simplifies downloading of program code and allows the ZDS II default
program configuration to be used. If the internal Flash is disabled, the address space
beginning at 00_0000Hmust address external Flash or other memory containing the
necessary option bits, vectors and application startup code.
•
Any external nonvolatile memory must be located above the internal Flash in the ad-
dress space, but below any volatile (random access) memory. There is a gap or hole in
PS022010-0811
P R E L I M I N A R Y
Tools Compatibility Guidelines
ZNEO® Z16F Series MCUs
Product Specification
40
the address space between internal and external nonvolatile memory and between non-
volatile and volatile memory.
•
•
Any external volatile (random access) memory must be located at or above 80_0000H
in the 24-bit address space (in the CS1 range). This location is a requirement of the
ZDSII GUI. Volatile memory on CS0 is located in a lower address range if it is config-
ured by adding an edited linker RANGE command to the Additional Linker Commands
field of the ZDS II project settings.
External volatile memory falling below FF_8000Hmust be addressed as a contiguous
block. The ZDS II C-Compiler large model does not support holes in 32-bit addressed
volatile memory. There is a hole between this memory and volatile memory at or above
FF_8000H, however.
•
•
External volatile memory at or above FF_8000Hmust be addressed as a block contig-
uous with the microcontroller’s internal RAM. The ZDS II C-Compiler small model
does not support holes in 16-bit addressable volatile memory.
External volatile memory must not be located above internal RAM, which ends at
FF_BFFFH. This location is a requirement of the ZDS II GUI. Volatile memory is lo-
cated at FF_C000Hand extend up to FF_DFFFHif the space is not used for I/O, but the
range must be configured by adding an edited linker RANGE command to the Addi-
tional Linker Commands field of the project settings. The debugger memory window
always displays this range as part of the I/O Data space, however.
•
The ZDS II GUI assumes external I/O is located in the range FF_C000Hto FF_DFFFH.
Any external I/O that is located elsewhere is accessed using absolute addressing. The
debugger memory window displays all addresses below FF_C000Has part of the Mem-
ory space.
For details about how ZDSII development tools use memory, refer to the Zilog Developer
Studio II – ZNEO User Manual (UM0171).
External WAIT Pin Operation
Setup of the external WAIT pin is selected by the GPIO alternate function. When using the
external WAIT pin, at least one internal wait state must be added to allow sufficient
address valid to wait input setup time.
PS022010-0811
P R E L I M I N A R Y
External WAIT Pin Operation
ZNEO® Z16F Series MCUs
Product Specification
41
Operation
Wait State Generator
Programmable wait states are inserted to provide external devices with additional clock
cycles to complete their read and write operations. The number of wait states are con-
trolled by the CSxWAIT[3:0] field and the PRxWAIT[1:0] field as shown in the the Chip
Select Control Registers section on page 43. The wait states idle the ZNEO CPU for the
specified number of system clock cycles; a maximum of 31 wait states are inserted. An
example of wait state operation is illustrated in Figure 10. In this example, the external
interface has been configured to provide two wait states. See the detailed timing diagrams
in the External Interface Timing section on page 47.
2 Wait States
Enabled in Wait
State Generator
TCLK
TWAIT
TWAIT
X
IN
ADDR[23:0]
DATA[15:0]
(output)
CS
WR
Figure 10. External Interface Wait State Operation Example (Write Operation)
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
42
ISA-Compatible Mode
Configuring the external interface for ISA Mode adjusts the Read timing to follow the ISA
Mode commonly employed in PC and related applications. In ISA Mode, assertion of the
Read signal (RD) is delayed one-half system clock. Also, an extra wait state is added dur-
ing read operations.
External Interface Control Register Definitions
The following section describes the various control registers.
External Interface Control Register
The External Interface Control Register, shown in Table 9, enables the interface and sets
the internal memory size.
Table 9. External Interface Control Register (EXTCT)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BUSSEL
00
MEMSIZE
00
RESERVED
0000
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E070H
Bit
Description
[7:6]
Bus Select External Interface Enable
BUSSEL 00 = No External Bus.
01 = 8-bit External Bus Interface is enabled (Port E).
1X = 16-bit External Bus Interface is enabled (Port J and Port E).
[5:4]
Select Internal Memory Size
MEMSIZE 00 = 128 KB of internal memory.
01 = 64 KB of internal memory.
10 = 32 KB of internal memory.
11 = No Internal Memory.
[3:0]
Reserved
These bits are reserved and must be programmed to 0000.
PS022010-0811
P R E L I M I N A R Y
ISA-Compatible Mode
ZNEO® Z16F Series MCUs
Product Specification
43
Chip Select Control Registers
The Chip Select Control registers control the chip select outputs. Each chip select has a
High byte and Low byte.
Table 10. External Chip Select Control Registers High (EXTCSxH)
Bits
7
CSxEN
0
6
POLSEL
0
5
CSxISA
0
4
3
2
1
0
Field
RESET
R/W
W/B
0
RESERVED
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_(E072, E074, E076, E078, E07A, E07C)H
Bit
Description
[7]
CSEN
Chip Select Enable
0 = CSx is disabled.
1 = CSx is enabled.
[6]
Polarity Select
POLSEx 0 = CSx is active Low.
1 = CSx is active High.
[5]
Chip Select ISA Mode Enable
CSxISA 0 = ISA Mode disabled.
1 = ISA Mode enabled.
[4]
W/B
Word or Byte Mode Select per Chip Select for 16-Bit or 8-Bit Peripherals
0 = External interface uses Data[15:0] for this chip select.
1 = External interface uses Data[7:0] for this chip select.
[3:0]
Reserved
These bits are reserved and must be programmed to 0000.
PS022010-0811
P R E L I M I N A R Y
Chip Select Control Registers
ZNEO® Z16F Series MCUs
Product Specification
44
Table 11 lists the External Chip Select Control Registers Low for CS0 (EXTCS0L). This
register sets the number of wait states for chip select 0. Waits are only added if the chip
select is enabled. Chip Select 0 is enabled automatically in ROMLESS Mode.
Table 11. External Chip Select Control Registers Low for CS0 (EXTCS0L)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RESERVED
PR0WAIT
CS0WAIT
0
0
1
1
1
1
1
1
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_(E073)H
Bit
Description
Reserved
[7:6]
These bits are reserved and must be programmed to 00.
[5:4]
Post Read Wait Selection
PR0WAIT[2:0] 00 = 0 wait state.
01 = 1 wait state.
10 = 2 wait states.
11 = 3 wait states.
[3:0]
CS0WAIT
Chip Select 0 Wait Selection
0000 = 0 wait state.
0001 = 1 wait state.
0010 = 2 wait states.
0011 = 3 wait states.
0100 = 4 wait states.
0101 = 5 wait states.
0110 = 6 wait states.
0111 = 7 wait states.
1000 = 8 wait states.
1001 = 9 wait states.
1010 = 10 wait state.s
1011 = 11 wait states.
1100 = 12 wait states.
1101 = 13 wait states.
1110 = 14 wait states.
1111 = 15 wait states.
PS022010-0811
P R E L I M I N A R Y
Chip Select Control Registers
ZNEO® Z16F Series MCUs
Product Specification
45
Table 12 shows the External Chip Select Control Registers Low for CS1(EXTSC1L). This
register sets the number of wait states for Chip Select 1. Waits are only added if the chip
select is enabled.
Table 12. External Chip Select Control Registers Low for CS1 (EXTCS1L)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RESERVED
PR1WAIT
CS1WAIT
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_(E075)H
Bit
Description
Reserved
[7:6]
These bits are reserved and must be programmed to 00.
[5:4]
Post Read Wait Selection
PR1WAIT[2:0] 00 = 0 wait state.
01 = 1 wait state.
10 = 2 wait states.
11 = 3 wait states.
[3:0]
CS1WAIT
Chip Select 1 Wait Selection
0000 = 0 wait state.
0001 = 1 wait state.
0010 = 2 wait states.
0011 = 3 wait states.
0100 = 4 wait states.
0101 = 5 wait states.
0110 = 6 wait states.
0111 = 7 wait states.
1000 = 8 wait states.
1001 = 9 wait states.
1010 = 10 wait states.
1011 = 11 wait states.
1100 = 12 wait states.
1101 = 13 wait states.
1110 = 14 wait states.
1111 = 15 wait states.
PS022010-0811
P R E L I M I N A R Y
Chip Select Control Registers
ZNEO® Z16F Series MCUs
Product Specification
46
Table 13 lists the External Chip Select Control Registers Low for CS2 to CS5 (EXTC-
SxL). This register sets the number of wait states for chip selects 2 through 5. Waits are
only added if the chip select is enabled.
Table 13. External Chip Select Control Registers Low for CS2 to CS5 (EXTCSxL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RESERVED
PRxWAIT
CSxWAIT
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_(E077, E079, E07B, E07D)H
Bit
Description
Reserved
[7:6]
These bits are reserved and must be programmed to 00.
[5:4]
Post Read Wait Selection
PRxWAIT[2:0] 00 = 0 wait state.
01 = 1 wait state.
10 = 2 wait states.
11 = 3 wait states.
[3:0]
CSxWAIT
Chip Select x Wait Selection
0000 = 0 wait state.
0001 = 2 wait state.
0010 = 4 wait states.
0011 = 6 wait states.
0100 = 8 wait states.
0101 = 10 wait states.
0110 = 12 wait states.
0111 = 14 wait states.
1000 = 16 wait states.
1001 = 18 wait states.
1010 = 20 wait states.
1011 = 22 wait states.
1100 = 24 wait states.
1101 = 26 wait states.
1110 = 28 wait states.
1111 = 30 wait states.
PS022010-0811
P R E L I M I N A R Y
Chip Select Control Registers
ZNEO® Z16F Series MCUs
Product Specification
47
External Interface Timing
The following sections describe the ZNEO Z16F Series MCU’s external interface timing.
External Interface Write Timing, Normal Mode
Figure 11 and Table 14 provide timing information for the external interface performing a
write operation. In Figure 11, it is assumed that the wait state generator is configured to
provide 1 wait state during write operations. The external WAIT input pin is generating an
additional Wait period. It is assumed in Figure 11 that the chip select (CS) signal has been
configured for active Low operation. Though the internal system clock is not provided as
an external signal, it provides a useful reference for control signal events.
At the completion of a Write cycle, the deassertion of the WR signal is fed back from the
pin and used on chip to control the deassertion of the data, CS, address and byte enable
signals to assure proper timing of the data hold.
Note:
Table 14. External Interface Timing for a Write Operation, Normal Mode
Delay (ns)
Parameter
Abbreviation
Minimum
Maximum
T
T
T
T
T
T
T
T
T
T
T
T
T
T
SYS CLK Rise to Address Valid Delay
WR Rise to Address Output Hold Time
SYS CLK Rise to Data Valid Delay
WR Rise to Data Output Hold Time
SYS CLK Rise to CS Assertion Delay
WR Rise to CS Deassertion Hold Time
SYS CLK Rise to WR Assertion Delay
SYS CLK Rise to WR Deassertion Hold Time
10
1
3
3
3
2
10
10
3
4
5
6
1/2T
+10
7
CLK
3
1
1
8
WAIT Input Pin Assertion to X Rise Setup Time
9
IN
WAIT Input Pin Deassertion to X Rise Setup Time
10
11
12
13
14
IN
SYS CLK Rise to DMAACK Assertion Delay
10
10
SYS CLK Rise to DMAACK Deassertion Hold Time
SYS CLK Rise to BHEN or BLEN Assertion Delay
WR Rise to BHEN or BLEN Deassertion Hold Time
3
3
PS022010-0811
P R E L I M I N A R Y
External Interface Timing
ZNEO® Z16F Series MCUs
Product Specification
48
1 Wait State from Wait State Generator
and 1 Wait State from External WAIT pin
T
T
WAIT
T
CLK
WAIT
X
IN
T
T
2
1
ADDR[23:0]
DATA[15:0]
T
T
4
6
3
T
T
5
CS
T
T
8
7
WR
T
T
10
9
WAIT
(From pin)
T
T
T
12
11
13
DMAACK
T
14
BHEN/BLEN
Figure 11. External Interface Timing for a Write Operation, Normal Mode
PS022010-0811
P R E L I M I N A R Y
External Interface Write Timing, Normal
ZNEO® Z16F Series MCUs
Product Specification
49
External Interface Write Timing, ISA Mode
Figure 12 and Table 15 provide timing information for the external interface performing a
write operation. In Figure 12, it is assumed that the wait state generator has been config-
ured to provide 1 wait state during write operations. The external WAIT input pin is gener-
ating an additional Wait period. As with NORMAL mode, the WR signal is fed back from
the pin and used on chip to time the removal of the data signals to ensure proper timing of
the data hold.
Table 15. External Interface Timing for a Write Operation, ISA Mode
Delay (ns)
Parameter
Abbreviation
Minimum
Maximum
T
T
T
T
T
T
T
T
T
T
T
T
T
T
X
X
X
Rise to Address Valid Delay
Rise to Address Output Hold Time
Rise to Data Valid Delay
10
1
IN
IN
IN
3
3
3
2
10
10
10
3
WR Rise to Data Output Hold Time
4
X
X
X
X
Rise to CS Assertion Delay
5
IN
IN
IN
IN
Rise to CS Deassertion Hold Time
Fall to WR Assertion Delay
6
7
Fall to WR Deassertion Hold Time
3
1
1
8
WAIT Input Pin Assertion to X Rise Setup Time
9
IN
WAIT Input Pin Deassertion to X Rise Setup Time
10
11
12
13
14
IN
X
X
X
X
Rise to DMAACK Assertion Delay
10
10
IN
IN
IN
IN
Rise to DMAACK Deassertion Hold Time
Rise to BHEN or BLEN Assertion Delay
Rise to BHEN or BLEN Deassertion Hold Time
3
3
PS022010-0811
P R E L I M I N A R Y External Interface Write Timing, ISA Mode
ZNEO® Z16F Series MCUs
Product Specification
50
1 Wait State from Wait State Generator
and 1 Wait State from External WAIT pin
T
T
WAIT
T
CLK
WAIT
X
IN
T
T
2
1
ADDR[23:0]
DATA[15:0]
T
T
4
3
T
T
5
6
CS
T
T
8
7
WR
T
T
10
9
WAIT
(From pin)
T
T
12
11
DMAACK
T
T
14
13
BHEN/BLEN
Figure 12. External Interface Timing for a Write Operation, ISA Mode
External Interface Read Timing, Normal Mode
Figure 13 and Table 16 provide timing information for the external interface performing a
read operation in NORMAL Mode. In Figure 13, it is assumed the wait state generator has
been configured to provide 2 wait states during read operations. For proper data hold time
PS022010-0811
P R E L I M I N A R Y
External Interface Read Timing, Normal
ZNEO® Z16F Series MCUs
Product Specification
51
determination, be aware that the input data is captured on chip during the rising edge of
the system clock prior to the RD signal deassertion. The Read signal (RD) timing is shown
for both NORMAL and ISA modes.
Table 16. External Interface Timing for a Read Operation, Normal Mode
Delay (ns)
Parameter
Abbreviation
Minimum
Maximum
T
T
T
T
T
T
T
T
T
T
T
T
T
T
X
X
Rise to Address Valid Delay
10
1
IN
IN
Rise to Address Output Hold Time
3
0
3
2
Data Input Valid to X Rise Setup Time
3
3
IN
RD Rise to Data Input Hold Time
4
X
X
X
X
Rise to CS Assertion Delay
10
10
5
IN
IN
IN
IN
Rise to CS Deassertion Hold Time
Rise to RD Assertion Delay
6
7
Rise to RD Deassertion Hold Time
3
1
1
8
WAIT Input Pin Assertion to X Rise Setup Time
9
IN
WAIT Input Pin Deassertion to X Rise Setup Time
10
11
12
13
14
IN
X
X
X
X
Rise to DMAACK Assertion Delay
10
10
IN
IN
IN
IN
Rise to DMAACK Deassertion Hold Time
Rise to BHEN or BLEN Assertion Delay
Rise to BHEN or BLEN Deassertion Hold Time
3
3
PS022010-0811
P R E L I M I N A R Y
External Interface Read Timing, Normal
ZNEO® Z16F Series MCUs
Product Specification
52
1 Wait State from Wait State Generator
and 1 Wait State from External WAIT pin
T
T
WAIT
T
CLK
WAIT
X
IN
T
T
2
1
ADDR[23:0]
DATA[15:0]
T
T
4
3
T
T
5
6
CS
RD
T
7
T
8
T
T
10
9
WAIT
(From pin)
T
T
11
T
T
12
DMAACK
13
14
BHEN/BLEN
Figure 13. External Interface Timing for a Read Operation, Normal Mode
PS022010-0811
P R E L I M I N A R Y
External Interface Read Timing, Normal
ZNEO® Z16F Series MCUs
Product Specification
53
Figure 14 and Table 16 provide timing information for the External Interface performing a
read operation in NORMAL Mode with a post read wait state. The configuration is the
same as in Figure 13, with the exception of the post read wait state.
1 Wait State from Wait State Generator
and 1 Wait State from External WAIT pin
1 Post Read Wait State
T
T
T
PRWAIT
T
CLK
WAIT
WAIT
X
IN
T
2
T
1
ADDR[23:0]
DATA[15:0]
T
T
4
3
T
T
5
6
CS
RD
T
T
7
8
T
T
10
9
WAIT
(From pin)
Figure 14. External Interface Timing for a Read Operation, 2 Wait States and 1 Post Read Wait State
External Interface Read Timing, ISA Mode
Figure 15 and Table 17 provide timing information for the external interface performing a
read operation in ISA Mode. In Figure 15, it is assumed the wait state generator has been
configured to provide 2 wait states during read operations. In Figure 15, it is also assumed
that the chip select (CS) signals have been configured for active Low operation. The Read
signal (RD) timing is shown for both NORMAL and ISA modes.
PS022010-0811
P R E L I M I N A R Y External Interface Read Timing, ISA Mode
ZNEO® Z16F Series MCUs
Product Specification
54
Table 17. External Interface Timing for a Read Operation, ISA Mode
Delay (ns)
Parameter
Abbreviation
Minimum
Maximum
T
T
T
T
T
T
T
T
T
T
T
T
T
T
X
X
Rise to Address Valid Delay
10
1
IN
IN
Rise to Address Output Hold Time
3
3
3
2
Data Input Valid to X Rise Setup Time
3
3
IN
X
X
X
X
X
Rise to Data Input Hold Time
Rise to CS Assertion Delay
4
IN
IN
IN
IN
IN
10
10
5
Rise to CS Deassertion Hold Time
Fall to RD Assertion Delay
6
7
Fall to RD Deassertion Hold Time
3
1
1
8
WAIT Input Pin Assertion to X Rise Setup Time
9
IN
WAIT Input Pin Deassertion to X Rise Setup Time
10
11
12
13
14
IN
X
X
X
X
Rise to DMAACK Assertion Delay
10
10
IN
IN
IN
IN
Rise to DMAACK Deassertion Hold Time
Rise to BHEN or BLEN Assertion Delay
Rise to BHEN or BLEN Deassertion Hold Time
3
3
PS022010-0811
P R E L I M I N A R Y External Interface Read Timing, ISA Mode
ZNEO® Z16F Series MCUs
Product Specification
55
1 Wait State from Wait State Generator
and 1 Wait State from External WAIT pin
T
T
WAIT
T
CLK
WAIT
X
IN
T
T
2
1
ADDR[23:0]
DATA[15:0]
T
T
4
3
T
T
6
5
CS
RD
T
T
8
7
T
T
10
9
WAIT
(From pin)
T
T
11
12
DMAACK
T
T
13
14
BHEN/BLEN
Figure 15. External Interface Timing for a Read Operation, ISA Mode
PS022010-0811
P R E L I M I N A R Y External Interface Read Timing, ISA Mode
ZNEO® Z16F Series MCUs
Product Specification
56
Reset and Stop Mode Recovery
The reset controller within the ZNEO® Z16F Series controls RESET and Stop Mode
Recovery operation. In a typical operation, the following events causes a Reset to occur:
•
•
•
•
•
•
Power-On Reset
Voltage Brown-Out
WDT time-out (when configured through the WDT_RESoption bit to initiate a Reset)
External RESET pin assertion
OCD initiated Reset (OCDCTL[0]set to 1)
Fault detect logic
When ZNEO Z16F Series is in STOP Mode, a Stop Mode Recovery is initiated by either
of the following operations:
•
•
WDT time-out
GPIO port input pin transition on an enabled Stop Mode Recovery source
Reset Types
The ZNEO Z16F Series provides two different types of Reset operation (System Reset and
Stop Mode Recovery). The type of Reset is a function of both the current operating mode
of the ZNEO Z16F Series device and the source of the Reset. Table 18 lists the types of
Reset and their operating characteristics.
Table 18. Reset and Stop Mode Recovery Characteristics and Latency
Reset Characteristics and Latency
Peripheral Control
Reset Type
Registers
ZNEO CPU
Reset Latency (Delay)
System Reset Reset (as applicable)
Reset
A minimum of 66 internal precision oscillator
cycles.
Stop Mode
Recovery
Unaffected, except RST- Reset
SRC and OSCCTL regis-
ters
A minimum of 66 internal precision oscillator
cycles.
PS022010-0811
P R E L I M I N A R Y
Reset and Stop Mode Recovery
ZNEO® Z16F Series MCUs
Product Specification
57
System Reset
During a System Reset, the ZNEO Z16F Series device is held in Reset for 66 cycles of the
IPO. At the beginning of Reset, all GPIO pins are configured as inputs. All GPIO pro-
grammable pull-ups are disabled.
At the start of a System Reset, the motor control PWM outputs are forced to high-imped-
ance momentarily. When the option bits that control the off-state have been properly eval-
uated, the PWM outputs are forced to the programmed off-state.
During Reset, the ZNEO CPU and on-chip peripherals are nonactive; however, the IPO
and WDT oscillator continue to run. During the first 50 clock cycles, the internal option
bit registers are initialized, after which the system clock for the core and peripherals
begins operating. The ZNEO CPU and on-chip peripherals remain nonactive through the
next 16 cycles of the system clock, after which the internal reset signal is deasserted.
On Reset, control registers within the register file that have a defined reset value are
loaded with their reset values. Other control registers (including the Flags) and general-
purpose RAM are undefined following Reset. The ZNEO CPU fetches the Reset vector at
program memory address 0004Hand loads that value into the program counter. Program
execution begins at the Reset vector address.
Table 19 lists the System Reset sources as a function of the operating mode. The following
text provides more detailed information about the individual Reset sources. Note that a
POR/VBO event always has priority over all other possible reset sources to ensure that a
full System Reset occurs.
Table 19. System Reset Sources and Resulting Reset Action
Operating Mode
System Reset Source
Action
NORMAL or HALT modes
POR/VBO
System Reset
WDT time-out when configured for Reset System Reset
RESET pin assertion
Write RSTSCR[0]to 1
Fault detect logic reset
POR/VBO
System Reset
System Reset
System Reset
System Reset
System Reset
System Reset
STOP Mode
RESET pin assertion
Fault detect logic reset
Power-On Reset
Each device in the ZNEO Z16F Series contains an internal POR circuit. The POR circuit
monitors the supply voltage and holds the device in the Reset state until the supply voltage
reaches a safe operating level. After the supply voltage exceeds the POR voltage threshold
PS022010-0811
P R E L I M I N A R Y
System Reset
ZNEO® Z16F Series MCUs
Product Specification
58
(VPOR) and has stabilized, the POR counter is enabled and counts 50 cycles of the IPO. At
this point, the system clock is enabled and the POR counter counts a total of 16 system
clock pulses. The device is held in the Reset state until the second POR counter sequence
has timed out. After the ZNEO Z16F Series exits the POR state, the ZNEO CPU fetches
the Reset vector. Following POR, the PORstatus bit in the Reset Status and Control Regis-
ter is set to 1.
Figure 16 displays Power-On Reset operation. For the POR threshold voltage (VPOR), see
Table 75 on page 342.
V
= 3.3 V
CC
VPOR
VVBO
Program
Execution
V
= 0.0 V
CC
System Clock
Internal Precision
Oscillator
Oscillator
Start-up
Internal RESET
Signal
Option Bit
Counter Delay
System Clock
Counter Delay
Not to Scale
Figure 16. Power-On Reset Operation
Voltage Brown-Out Reset
The ZNEO Z16F Series provides Low Voltage Brown-Out (VBO) protection. The VBO
circuit senses the supply voltage when it drops to an unsafe level (below the VBO thresh-
old voltage) and forces the device into the Reset state. While the supply voltage remains
below the POR voltage threshold (VPOR), the VBO holds the device in the Reset state.
When the supply voltage exceeds the VPOR and is stabilized, the device progresses
through a full System Reset sequence, as described in the section <CrossRef> Power-On
PS022010-0811
P R E L I M I N A R Y
Voltage Brown-Out Reset
ZNEO® Z16F Series MCUs
Product Specification
59
Reset on page 57. Following Power-On Reset, the PORstatus bit in the reset source regis-
ter is set to 1. Figure 17 displays Voltage Brown-Out operation. For VBO and POR thresh-
old voltages (VVBO and VPOR), see Figure 75 on page 342.
The VBO circuit is either enabled or disabled during STOP Mode. Operation during STOP
Mode is controlled by the VBO_AOoption bit. For information about configuring VBO_AO,
see the Option Bits chapter on page 292.
V
= 3.3 V
V
= 3.3 V
VPOR
VVBO
CC
CC
Program
Execution
Voltage
Brown-Out
Program
Execution
System Clock
Internal Precision
Oscillator
Internal RESET
Signal
Option Bit
System Clock
Counter Delay Counter Delay
Figure 17. Voltage Brown-Out Reset Operation
Watchdog Timer Reset
If the device is in NORMAL or HALT Mode, the WDT initiates a System Reset at time-
out if the WDT_RESoption bit is set to 1. This setting is the default (unprogrammed) setting
of the WDT_RESoption bit. The WDTstatus bit in the Reset Status and Control Register is
set to signify that the reset was initiated by the WDT.
External Pin Reset
The input-only RESET pin has a schmitt-triggered input, an internal pull-up, an analog fil-
ter and a digital filter to reject noise. After the RESET pin is asserted for at least four sys-
PS022010-0811
P R E L I M I N A R Y
Watchdog Timer Reset
ZNEO® Z16F Series MCUs
Product Specification
60
tem clock cycles, the device progresses through the System Reset sequence. While the
RESET input pin is asserted Low, the ZNEO Z16F Series device continues to be held in
the Reset state. If the RESET pin is held Low beyond the System Reset time-out, the
device exits the Reset state 16 system clock cycles following RESET pin deassertion. If
the RESET pin is released before the System Reset time-out, the RESET pin is driven
Low by the chip until the completion of the time-out as described in the next section. In
STOP Mode, the digital filter is bypassed as the system clock is disabled.
Following a System Reset initiated by the external RESET pin, the EXTstatus bit in the
Reset Status and Control Register is set to 1.
External Reset Indicator
During System Reset, the RESET pin functions as an open drain (active Low) RESET
Mode indicator in addition to the input functionality. This Reset output feature allows a
ZNEO Z16F Series device to Reset other components to which it is connected, even if the
Reset is caused by internal sources such as POR, VBO or WDT events and as an indica-
tion of when the reset sequence completes.
After an internal reset event occurs, the internal circuitry begins driving the RESET pin
Low. The RESET pin is held Low by the internal circuitry until the appropriate delay
listed in Table 18 on page 56 has elapsed.
User Reset
A System Reset is initiated by setting RSTSCR[0]. If the Write was caused by the OCD,
the OCD is not Reset.
Fault Detect Logic Reset
Fault detect circuitry exists to detect illegal state changes which is caused by transient
power or electrostatic discharge events. When such a fault is detected, a system reset is
forced. Following the system reset, the FLTDbit in the Reset Status and Control Register is
set.
Stop Mode Recovery
STOP Mode is entered by execution of a STOPinstruction by the ZNEO CPU. For detailed
information about STOP Mode, see the Low-Power Modes chapter on page 64. During
Stop Mode Recovery, the device is held in Reset for 66 cycles of the internal precision
oscillator.
PS022010-0811
P R E L I M I N A R Y
External Reset Indicator
ZNEO® Z16F Series MCUs
Product Specification
61
Stop Mode Recovery only affects the contents of the the Reset Status and Control Register
(see page 62) and the Oscillator Control Register (see page 332). Stop Mode Recovery
does not affect any other values in the register file, including the stack pointer, register
pointer, flags, peripheral control registers and general-purpose RAM.
The ZNEO CPU fetches the Reset vector at program memory addresses 0004H-0007H
and loads that value into the program counter. Program execution begins at the Reset vec-
tor address. Following Stop Mode Recovery, the STOPbit in the Reset Status and Control
Register is set to 1. Table 20 lists the Stop Mode Recovery sources and resulting actions.
The following text provides more detailed information about each of the Stop Mode
Recovery sources.
Table 20. Stop Mode Recovery Sources and Resulting Action
Operating
Mode
Stop Mode Recovery Source
Action
STOP Mode
WDT time-out when configured for Reset
Stop Mode Recovery
WDT time-out when configured for System Stop Mode Recovery followed by WDT Sys-
Exception
tem Exception
Data transition on any GPIO Port pin
Stop Mode Recovery
enabled as a Stop Mode Recovery source
Stop Mode Recovery Using WDT Time-Out
If the WDT times out during STOP Mode, the device undergoes a Stop Mode Recovery
sequence. In the Reset Status and Control Register, the WDTand STOPbits are set to 1. If
the WDT is configured to generate a System Exception on time-out, the ZNEO CPU ser-
vices the WDT System Exception following the normal Stop Mode Recovery sequence.
Stop Mode Recovery Using a GPIO Port Pin Transition
Each of the GPIO port pins is configured as a Stop Mode Recovery input source. If any
GPIO pin enabled as a Stop Mode Recovery source, a change in the input pin value (from
High to Low or from Low to High) initiates Stop Mode Recovery. The GPIO Stop Mode
Recovery signals are filtered to reject pulses less than 10 ns (typical) in duration. In the
Reset Status and Control Register, the STOPbit is set to 1.
Short pulses on the port pin initiates Stop Mode Recovery without initiating an interrupt
(if enabled for that pin).
Caution:
PS022010-0811
P R E L I M I N A R Y Stop Mode Recovery Using WDT Time-Out
ZNEO® Z16F Series MCUs
Product Specification
62
Reset Status and Control Register
The Reset Status and Control Register (RSTSCR), shown in Table 21, records the cause of
the most recent RESET or Stop Mode Recovery. All status bits are updated on each
RESET or Stop Mode Recovery event. Table 22 indicates the possible states of the Reset
status bits following a RESET or Stop Mode Recovery event.
Table 21. Reset Status and Control Register (RSTSCR)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
POR
STOP
WDT
EXT
FLT
USR
Reserved USER_RST
See Table 22 for a description of these bits.
R
R
R
R
R
R
R
W
Addr
FF‒E050H
Bit
Description
[7]
POR
[6]
STOP
[5]
WDT
For a description of bits [7:2], see Table 22.
[4]
EXT
[3]
FLT
[2]
USR
[1]
Reserved
These bits are reserved and must be programmed to 0.
[0]
USER_RST
The USER_RST bit in this register allows software controlled RESET of the part pin. This
bit is a Write Only bit that causes a System Reset with the result identified by the USR bit
after being executed.
0 = No action.
1 = Causes System Reset.
PS022010-0811
P R E L I M I N A R Y
Reset Status and Control Register
ZNEO® Z16F Series MCUs
Product Specification
63
Table 22. Reset Status Register Values Following Reset
Reset or Stop Mode Recovery Event
Power-On Reset
POR STOP WDT EXT
FLT USR
1
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
1
0
0
1
0
0
1
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
1
Reset using RESET pin assertion
Reset using WDT time-out
Reset from Fault detect logic
Stop Mode Recovery using GPIO pin transition
Stop Mode Recovery using WDT time-out
Reset using software control; write 1 to bit 0 of this register
PS022010-0811
P R E L I M I N A R Y
Reset Status and Control Register
ZNEO® Z16F Series MCUs
Product Specification
64
Low-Power Modes
The ZNEO® Z16F Series products contain advanced integrated power-saving features.
Power management functions are divided into three categories to include CPU operating
modes, peripheral power control and programmable option bits. The highest level of
power reduction is provided through a combination of all functions.
STOP Mode
Execution of the ZNEO CPU’s STOPinstruction places the device into STOP Mode. In
STOP Mode, the operating characteristics are:
•
•
•
•
•
IPO is stopped; XIN and XOUT pins are driven to VSS.
System clock is stopped.
ZNEO CPU is stopped.
Program counter (PC) stops incrementing.
If enabled for operation during STOP Mode, the WDT and its internal RC oscillator
continue to operate.
•
•
If enabled for operation in STOP Mode through the associated option bit, the VBO
protection circuit continues to operate.
All other on-chip peripherals are nonactive.
To minimize current in STOP Mode, all GPIO pins that are configured as digital inputs
must be driven to one of the supply rails (VDD or VSS), the VBO protection must be dis-
abled and WDT must be disabled. The device is brought out of STOP Mode using Stop
Mode Recovery. For detailed information about Stop Mode Recovery, see the Reset and
Stop Mode Recovery section on page 56.
To prevent excess current consumption when using an external clock source in STOP
Mode, the external clock must be disabled.
Caution:
PS022010-0811
P R E L I M I N A R Y
Low-Power Modes
ZNEO® Z16F Series MCUs
Product Specification
65
HALT Mode
Execution of the ZNEO CPU’s HALT instruction places the device into HALT Mode. The
following list represents the operating characteristics of the ZNEO CPU in HALT Mode:
•
•
•
•
•
•
System clock is enabled and continues to operate
ZNEO CPU is stopped
PC stops incrementing
WDT’s internal RC oscillator continues to operate
If enabled, the WDT continues to operate
All other on-chip peripherals continue to operate
The ZNEO CPU is brought out of HALT Mode by any of the following operations:
•
•
•
•
•
•
Interrupt or System Exception
WDT time-out (System Exception or Reset)
Power-On Reset
VBO reset
External RESET pin assertion
Instantaneous HALT Mode recovery
To minimize current in HALT Mode, all GPIO pins which are configured as inputs must
be driven to one of the supply rails (VDD or VSS).
Peripheral-Level Power Control
On-chip peripherals in ZNEO Z16F Series parts automatically enter a low power mode
after Reset and whenever the peripheral is disabled. To minimize power consumption,
unused peripherals must be disabled. See the individual peripheral chapters for specific
register settings to enable or disable the peripheral.
Power Control Option Bits
User programmable option bits are available in some versions of the ZNEO Z16F Series
devices that enable very low power STOP Mode operation. These options include dis-
abling the VBO protection circuits and disabling the WDT oscillator. For detailed descrip-
tion of the user options that affect power management, see the Option Bits chapter on page
292.
PS022010-0811
P R E L I M I N A R Y
HALT Mode
ZNEO® Z16F Series MCUs
Product Specification
66
General-Purpose Input/Output
The ZNEO® Z16F Series products contain general-purpose input/output (GPIO) pins
arranged as Ports A–K. Each port contains control and data registers. The GPIO control
registers are used to determine data direction, open-drain, output drive current and alter-
nate pin functions. Each port pin is individually programmable.
GPIO Port Availability by Device
Table 23 lists the port pins available by device and package pin count.
Table 23. GPIO Port Availability by Device
Device
Pin-Count Port A Port B Port C Port D Port E Port F Port G Port H Port J Port K
Z16F2811 100-pin
80-pin
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[7:0]
[3]
[3:0]
[3:0]
[3:0]
[3:0]
[3:0]
[3:0]
[3:0]
[3:0]
[3:0]
[7:0]
—
[7:0]
—
Z16F6411 100-pin
80-pin
[7:0]
—
[7:0]
—
Z16F3211 100-pin
80-pin
[7:0]
—
[7:0]
Z16F2810 80-pin
68-pin
—
—
—
—
—
64-pin
[7]
[3]
—
Architecture
Figure 18 displays a simplified block diagram of a GPIO port pin. This diagram does not
display the ability to accommodate alternate functions and variable port current drive
strength.
PS022010-0811
P R E L I M I N A R Y
General-Purpose Input/Output
ZNEO® Z16F Series MCUs
Product Specification
67
V
DD
Pull-up Enable
Port Input
Schmitt Trigger
Data Register
Q
D
System
Clock
V
DD
Port Output Control
Port Output
Data Register
Data
Bus
D
Q
Port
Pin
System
Clock
Port Data Direction
Figure 18. GPIO Port Pin Block Diagram
GND
GPIO Alternate Functions
Many GPIO port pins are used for GPIO and to provide access to the on-chip peripheral
functions such as timers, serial communication devices and external data and address bus.
The Port A–K alternate function registers configure these pins for either GPIO or alternate
function operation. When a pin is configured for alternate function, control of the port pin
direction (I/O) is passed from the Port A–K data direction registers to the alternate func-
tion assigned to this pin. Table 24 on page 68 lists the alternate functions associated with
each port pin.
For detailed information about enabling the external interface data signals, see the Exter-
nal Interface chapter on page 37. When the external interface data signals are enabled for
an 8-bit port, the other GPIO functionality including alternate functions cannot be used.
PS022010-0811
P R E L I M I N A R Y
GPIO Alternate Functions
ZNEO® Z16F Series MCUs
Product Specification
68
Table 24. Port Alternate Function Mapping
Alternate
Alternate
Function 2
Alternate
Function 3
External
Interface
Port
Pin
Function 1
T0IN/T0OUT
T0OUT
DE0
Port A
PA0
PA1
PA2
PA3
PA4
PA5
PA6
PA7
DMA0REQ
DMA0ACK
FAULTY
FAULT0
CS1
T0INPB
CTS0
RXD0
TXD0
CS2
SCL
CS3
SDA
CS4
Port B
Port C
Port D
PB0/T0IN0 ANA0
PB1/T0IN1 ANA1
PB2/T0IN2 ANA2
PB3
PB4
PB5
PB6
PB7
PC0
PC1
PC2
PC3
PC4
PC5
PC6
PC7
PD0
PD1
PD2
PD3
PD4
PD5
PD6
PD7
ANA3/OPOUT
ANA4
ANA5
ANA6/OPINP/CINN
ANA7/OPINN
T1IN/T1OUT
T1OUT
SS
DMA1REQ
DMA1ACK
CS4
CINN
COMPOUT
SCK
DMA2REQ
DMA2ACK
CS5
MOSI
MISO
T2IN/T2OUT
T2OUT
PWMH1
PWML1
PWMH2
DE1
PWMH0
PWML0
ADDR[20]
ADDR[21]
ADDR[22]
ADDR[16]
ADDR[18]
ADDR[19]
ADDR[17]
ADDR[23]
RXD1
TXD1
CTS1
PWML2
PS022010-0811
P R E L I M I N A R Y
GPIO Alternate Functions
ZNEO® Z16F Series MCUs
Product Specification
69
Table 24. Port Alternate Function Mapping (Continued)
Alternate
Function 1
Alternate
Function 2
Alternate
Function 3
External
Interface
Port
Pin
Port E
PE0
PE1
PE2
PE3
PE4
PE5
PE6
PE7
PF0
PF1
PF2
PF3
PF4
PF5
PF6
PF7
PG0
PG1
PG2
PG3
PG4
PG5
PG6
PG7
PH0
PH1
PH2
PH3
DATA[0]
DATA[1]
DATA[2]
DATA[3]
DATA[4]
DATA[5]
DATA[6]
DATA[7]
Port F
Port G
Port H
ADDR[0]
ADDR[1]
ADDR[2]
ADDR[3]
ADDR[4]
ADDR[5]
ADDR[6]
ADDR[7]
ADDR[8]
ADDR[9]
ADDR[10]
ADDR[11]
ADDR[12]
ADDR[13]
ADDR[14]
ADDR[15]
ANA8
WR
ANA9
RD
ANA10
CS0
WAIT
ANA11/CPINP
PS022010-0811
P R E L I M I N A R Y
GPIO Alternate Functions
ZNEO® Z16F Series MCUs
Product Specification
70
Table 24. Port Alternate Function Mapping (Continued)
Alternate
Function 1
Alternate
Function 2
Alternate
Function 3
External
Interface
Port
Pin
Port J
PJ0
PJ1
PJ2
PJ3
PJ4
PJ5
PJ6
PJ7
PK0
PK1
PK2
PK3
PK4
PK5
PK6
PK7
DATA[8]
DATA[9]
DATA[10]
DATA[11]
DATA[12]
DATA[13]
DATA[14]
DATA[15]
Port K
BHEN
BLEN
CS0
CS1
CS2
CS3
CS4
CS5
GPIO Interrupts
Many of the GPIO port pins are used as interrupt sources. Some port pins are configured
to generate an interrupt request on either the rising edge or falling edge of the pin input
signal. Other port pin interrupts generate an interrupt when any edge occurs (both rising
and falling). For more information about interrupts using the GPIO pins, see the Interrupt
Controller chapter on page 80.
PS022010-0811
P R E L I M I N A R Y
GPIO Interrupts
ZNEO® Z16F Series MCUs
Product Specification
71
GPIO Control Register Definitions
Port A-K Input Data Registers
Reading from the Port A-K Input Data registers, shown in Table 25, returns the sampled
values from the corresponding port pins. The Port A-K Input Data registers are Read-only.
Table 25. Port A-K Input Data Registers (PxIN)
Bits
7
PIN7
X
6
PIN6
X
5
PIN5
X
4
PIN4
X
3
PIN3
X
2
PIN2
X
1
PIN1
X
0
PIN0
X
Field
RESET
R/W
R
R
R
R
R
R
R
R
Addr
FF_E100, FF_E110, FF_E120, FF_E130, FF_E140,
FF_E150, FF_E160, FF_E170, FF_E180, FF_E190
Bit
Description
[7:0]
Port Input Data
PIN[7:0] Sampled data from the corresponding port pin input.
0 = Input data is logical 0 (Low).
1 = Input data is logical 1 (High).
PS022010-0811
P R E L I M I N A R Y
GPIO Control Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
72
Port A-K Output Data Registers
The Port A-K Output Data registers, shown in Table 26, write output data to the pins.
Table 26. Port A-K Output Data Registers (PxOUT)
Bits
7
POUT7
0
6
POUT6
0
5
POUT5
0
4
POUT4
0
3
POUT3
0
2
POUT2
0
1
POUT1
0
0
POUT0
0
Field
RESET
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E101, FF_E111, FF_E121, FF_E131, FF_E141,
FF_E151, FF_E161, FF_E171, FF_E181, FF_E191
Bit
Description
[7:0]
Port Output Data
POUT[7:0] These bits contain the data to be driven out from the port pins. The values are only driven if
the corresponding pin is configured as an output and the pin is not configured for alternate
function operation.
0 = Drive a logical 0 (Low).
1= Drive a logical 1 (High). High value is not driven if the drain has been disabled by setting
the corresponding port output control register bit to 1.
PS022010-0811
P R E L I M I N A R Y
Port A-K Output Data Registers
ZNEO® Z16F Series MCUs
Product Specification
73
Port A-K Data Direction Registers
The Port A-K Data Direction registers, shown in Table 27, configure the specified port
pins as either inputs or outputs.
Table 27. Port A-K Data Direction Registers (PxDD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DD7
1
DD6
1
DD5
1
DD4
1
DD3
1
DD2
1
DD1
1
DD0
1
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E102, FF_E112, FF_E122, FF_E132, FF_E142, FF_E152,
FF_E162, FF_E172, FF_E182, FF_E192
Bit
Description
[7:0]
Data Direction
DD[7:0] These bits control the direction of the associated port pin. Port alternate function operation
overrides the data direction register setting.
0 = Output
Data in the Port A-K Output Data Register is driven onto the port pin.
1 = Input
The port pin is sampled and the value written into the Port A-K Input Data Register. The output
driver is high impedance.
PS022010-0811
P R E L I M I N A R Y
Port A-K Data Direction Registers
ZNEO® Z16F Series MCUs
Product Specification
74
Port A-K High Drive Enable Registers
Setting the bits in the Port A-K High Drive Enable registers, shown in Table 28, to 1, con-
figures the specified port pins for high current output drive operation. The Port A-K High
Drive Enable registers affect the pins directly and as a result, alternate functions are also
affected.
Table 28. Port A-K High Drive Enable Registers (PxHDE)
Bits
7
PHDE7
0
6
PHDE6
0
5
PHDE5
0
4
PHDE4
0
3
PHDE3
0
2
PHDE2
0
1
PHDE1
0
0
PHDE0
0
Field
RESET
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E103, FF_E113, FF_E123, FF_E133, FF_E143, FF_E153, FF_E163, FF_E173, FF_E183,
FF_E193
Bit
Description
[7:0]
Port High Drive Enabled
PHDE[7:0] 0 = The port pin is configured for standard output current drive.
1 = The port pin is configured for high output current drive.
Port A-K Alternate Function High and Low Registers
The Port A-K Alternate Function High and Low registers, shown in Table 29 and Table 30
on page 75, select the alternate functions for the selected pins. To determine the alternate
function associated with each port pin, see the GPIO Alternate Functions section on page
67. When changing alternate functions, it is recommended to use word data mode instruc-
tions to perform simultaneous Writes to the port Alternate Function High and Low regis-
ters.
Caution: Do not enable alternate function for GPIO port pins which do not have an associated al-
ternate function. Failure to follow this guideline will result in undefined operation.
PS022010-0811
P R E L I M I N A R Y
Port A-K High Drive Enable Registers
ZNEO® Z16F Series MCUs
Product Specification
75
Table 29. Port A-K Alternate Function High Registers (PxAFH)
Bits
7
AFH[7]
0
6
AFH[6]
0
5
AFH[5]
0
4
AFH[4]
0
3
AFH[3]
0
2
AFH[2]
0
1
AFH[1]
0
0
AFH[0]
0
Field
RESET
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E104, FF_E124, FF_E134, FF_E174
Table 30. Port A-K Alternate Function Low Registers (PxAFL)
Bits
7
AFL[7]
0
6
AFL[6]
0
5
AFL[5]
0
4
AFL[4]
0
3
AFL[3]
0
2
AFL[2]
0
1
AFL[1]
0
0
AFL[0]
0
Field
RESET
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E105, FF_E115, FF_E125, FF_E135, FF_E155, FF_E165, FF_E175, FF_E195
Table 31. Alternate Function Enabling
AFH[x]
AFL[x]
Priority
0
0
1
1
0
1
0
1
No Alternate Function Enabled
Alternate Function 1 Enabled
Alternate Function 2 Enabled
Alternate Function 3 Enabled
Note: x indicates the register bits from 0 through 7.
Port A-K Output Control Registers
Setting the bits in the Port A-K Output Control registers to 1, shown in Table 32, config-
ures the specified port pins for open-drain operation. These registers affect the pins
directly and as a result, alternate functions are also affected. Enabling the I2C controller
automatically configures the SCL and SDA pins as open-drain; independent of the setting
in the output control registers that have the SCL and SDA alternate functions.
PS022010-0811
P R E L I M I N A R Y
Port A-K Output Control Registers
ZNEO® Z16F Series MCUs
Product Specification
76
Table 32. Port A-K Output Control Registers (PxOC)
Bits
7
POC7
0
6
POC6
0
5
POC5
0
4
POC4
0
3
POC3
0
2
POC2
0
1
POC1
0
0
POC0
0
Field
RESET
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E106, FF_E116, FF_E126, FF_E136, FF_E146,
FF_E156, FF_E166, FF_E176, FF_E186, FF_E196
Bit
Description
[7:0]
Port Output Control
POC[7:0] These bits function independently of the alternate function bits and disable the drains
if set to 1.
0 = The drains are enabled for any output mode.
1 = The drain of the associated pin is disabled (open-drain mode).
Port A-K Pull-Up Enable Registers
Setting the bits in the Port A-K Pull-Up Enable registers to 1 enables a weak internal resis-
tive pull-up on the specified port pins. These registers affect the pins directly and as a
result, alternate functions are also affected. See Table 33.
Table 33. Port A-K Pull-Up Enable Registers (PxPUE)
Bits
7
PUE7
0
6
PUE6
0
5
PUE5
0
4
PUE4
0
3
PUE3
0
2
PUE2
0
1
PUE1
0
0
PUE0
0
Field
RESET
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E107, FF_E117, FF_E127, FF_E137, FF_E147, FF_E157,
FF_E167, FF_E177, FF_E187, FF_E197
Bit
Description
[7:0]
Port Pull-Up Enable
PUE[7:0] These bits function independently of the alternate function bit and enable the weak pull-up if
set to 1.
0 = The weak pull-up on the port pin is disabled.
1 = The weak pull-up on the port pin is enabled.
PS022010-0811
P R E L I M I N A R Y
Port A-K Pull-Up Enable Registers
ZNEO® Z16F Series MCUs
Product Specification
77
Port A-K Stop Mode Recovery Source Enable Registers
Setting the bits in the Port A-K Stop Mode Recovery Source Enable registers to 1, shown
in Table 34, configures the specified port pins as a Stop Mode Recovery source. During
STOP Mode, any logic transition on a port pin enabled as a Stop Mode Recovery source
initiates Stop Mode Recovery.
Table 34. Port A-K Stop Mode Recovery Source Enable Registers (PxSMRE)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PSMRE7 PSMRE6 PSMRE5 PSMRE4 PSMRE3 PSMRE2 PSMRE1 PSMRE0
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E108, FF_E118, FF_E128, FF_E138, FF_E148,
FF_E158, FF_E168, FF_E178, FF_E188, FF_E198
Bit
Description
[7:0]
Port Stop Mode Recovery Source Enabled
PSMRE[7:0] 0 = The port pin is not configured as a Stop Mode Recovery source. Transitions on this pin
during STOP Mode do not initiate Stop Mode Recovery.
1 = The port pin is configured as a Stop Mode Recovery source. Any logic transition on this
pin during STOP Mode initiates Stop Mode Recovery.
Port A IRQ MUX1 Register
The Port IRQ MUX1 Register, shown in Table 35, selects either Port A/D pins or the com-
parator/DBG channel as interrupt sources.
Table 35. Port A IRQ MUX1 Register (PAIMUX1)
Bits
7
CPIMUX
0
6
5
4
3
2
1
0
DBGIMUX
0
Field
RESET
R/W
Reserved
FF_E10C
0
0
0
0
0
0
R/W
R/W
R
R
R
R
R
R/W
Addr
Bit
Description
[7]
CPIMUX
Comparator Interrupt MUX
0 = Select Port A7/D7 based upon the Port A IRQ edge register as the interrupt source.
1 = Select the comparator as the interrupt source.
PS022010-0811
P R E L I M I N A R Y
Port A-K Stop Mode Recovery Source
ZNEO® Z16F Series MCUs
Product Specification
78
Bit
Description
[6:1]
Reserved
These bits are reserved and must be programmed to 000000.
[0]
Debug Interrupt MUX
DBGIMUX 0 = Select Port A0/D0 based on the Port A IRQ edge register as the interrupt source.
1 = Select the DBG as the interrupt source.
Port A IRQ MUX Register
The Port IRQ MUX Register, shown in Table 36, selects either Port A or Port D pins as
interrupt sources.
Table 36. Port A IRQ MUX Register (PAIMUX)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PAIMUX7 PAIMUX6 PAIMUX5 PAIMUX4 PAIMUX3 PAIMUX2 PAIMUX1 PAIMUX0
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E10E
Bit
Description
PAIMUX[7:0] Port A/D Interrupt Source
0 = Select Port Ax as interrupt source.
1 = Select Port Dx as interrupt source.
Port A IRQ Edge Register
The Port IRQ Edge Register, shown in Table 37, selects either positive or negative edge as
the port pin interrupt sources.
Table 37. Port A IRQ Edge Register (PAIEDGE)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PAIEDGE7 PAIEDGE6 PAIEDGE5 PAIEDGE4 PAIEDGE3 PAIEDGE2 PAIEDGE1 PAIEDGE0
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E10F
Bit
Description
Port A/D Interrupt Edge
[7:0]
PAIEDGE[7:0] 0 = Select Port A/D pin negedge as interrupt source.
1 = Select Port A/D pins posedge as interrupt source.
PS022010-0811
P R E L I M I N A R Y
Port A IRQ MUX Register
ZNEO® Z16F Series MCUs
Product Specification
79
Port C IRQ MUX Register
The Port C IRQ MUX Register, shown in Table 38, selects either Port C pins or the DMA
channels as interrupt sources.
Table 38. Port C IRQ MUX Register (PCIMUX)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
PCIMUX3 PCIMUX2 PCIMUX1 PCIMUX0
0
0
0
0
0
0
0
0
R
R
R
R
R/W
R/W
R/W
R/W
Addr
FF_E12E
Bit
Description
Reserved
[7:4]
These bits are reserved and must be programmed to 000000.
[3:0]
Port C Interrupt MUX
PCIMUX[3:0] 0 = Select DMA Chan[3:0] as interrupt source.
1 = Select port C pins as interrupt source.
PS022010-0811
P R E L I M I N A R Y
Port C IRQ MUX Register
ZNEO® Z16F Series MCUs
Product Specification
80
Interrupt Controller
The interrupt controller on the ZNEO® Z16F Series products prioritize interrupt requests
from on-chip peripherals and the GPIO port pins. The features of the interrupt controller
includes:
•
Flexible GPIO interrupts:
– Eight selectable rising and falling edge GPIO interrupts
– Four dual-edge interrupts
•
•
Three levels of individually programmable interrupt priority
Software Interrupt Requests (IRQ) assertion
The IRQs allow peripheral devices to suspend CPU operation in an orderly manner and
force the CPU to start an ISR. Usually this service routine is involved with exchange of
data, status information or control information between the CPU and the interrupting
peripheral. When the service routine is completed, the CPU returns to the operation from
which it was interrupted.
System exceptions are nonmaskable requests which allow critical system functions to sus-
pend CPU operation in an orderly manner and force the CPU to start a service routine.
Usually this service routine tries to determine how critical the exception is. When the ser-
vice routine is complete, the CPU returns to the operation from which it was interrupted.
The ZNEO Z16F Series supports both vectored and polled interrupt handling. For polled
interrupts, the interrupt control has no effect on operation. For more information about
interrupt servicing by the ZNEO CPU, refer to the ZNEO CPU Core User Manual
(UM0188), available for download at www.zilog.com.
Interrupt Vector Listing
Table 39 lists all of the interrupts available in order of priority.
PS022010-0811
P R E L I M I N A R Y
Interrupt Controller
ZNEO® Z16F Series MCUs
Product Specification
81
Table 39. Interrupt Vectors in Order of Priority
Program Memory
Priority Vector Address
Programmable
Priority?
Interrupt Source
Reset (not an interrupt)
System Exceptions
Reserved
Highest 0004H
0008H
No
No
000CH
0010H
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Timer 2
0014H
Timer 1
0018H
Timer 0
001CH
0020H
UART 0 receiver
UART 0 transmitter
2
0024H
I C
0028H
SPI
002CH
0030H
ADC0
Port A7 or Port D7, rising or falling input edge or
Comparator output rising and falling edge (source
selected in PortA IRQ MUX registers)
0034H
0038H
003CH
0040H
0044H
0048H
004CH
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Port A6 or Port D6, rising or falling input edge
Port A5 or Port D5, rising or falling input edge
Port A4 or Port D4, rising or falling input edge
Port A3 or Port D3, rising or falling input edge
Port A2 or Port D2, rising or falling input edge
Port A1 or Port D1, rising or falling input edge
Port A0 or Port D0, rising or falling input edge or
OCD Interrupt (source selected in PortA IRQ MUX
registers)
0050H
0054H
0058H
005CH
0060H
0064H
0068H
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
PWM Timer
UART 1 receiver
UART 1 transmitter
PWM Fault
Port C3, both input edges/DMA 3
Port C2, both input edges/DMA 2
Port C1, both input edges/DMA 1
Port C0, both input edges/DMA 0
Lowest
006CH
PS022010-0811
P R E L I M I N A R Y
Interrupt Vector Listing
ZNEO® Z16F Series MCUs
Product Specification
82
The most significant byte (MSB) of the four byte interrupt vector is not used. The vector is
stored in the three least significant byte (LSB) of the vector, as shown in Table 40.
Table 40. Interrupt Vector Placement
Vector Byte
Data
0
1
2
3
Reserved
IRQ Vector[23:16]
IRQ Vector[15:8]
IRQ Vector[7:0]
Architecture
Figure 19 displays a block diagram of the interrupt controller.
High
Port Interrupts
Priority
Vector
Priority
MUX
IRQ Request
Medium
Priority
Internal Interrupts
Low
Priority
Figure 19. Interrupt Controller Block Diagram
Operation
Master Interrupt Enable
The master interrupt enable bit in the flag register globally enables or disables interrupts.
This bit has been moved to the flag register (bit 0). Thus, anytime the register is loaded, it
PS022010-0811
P R E L I M I N A R Y
Architecture
ZNEO® Z16F Series MCUs
Product Specification
83
changes the state of the IRQE bit. For the IRETinstruction, the bit is set based on what has
been pushed on the stack.
Interrupts are globally enabled by any of the following actions:
•
•
Execution of an Enable Interrupt (EI) instruction
Writing 1 to the IRQEbit in the flag register
Interrupts are globally disabled by any of the following actions:
•
•
Execution of a Disable Interrupt (DI) instruction
ZNEO CPU acknowledgement of an interrupt service request from the interrupt con-
troller
•
•
•
•
Writing 0 to the IRQEbit in the flag register
Reset
Execution of a TRAPinstruction
All System Exceptions
Interrupt Vectors and Priority
The interrupt controller supports three levels of interrupt priority. Level 3 is the highest
priority, Level 2 is the second highest priority and Level 1 is the lowest priority. If all of
the interrupts are enabled with identical interrupt priority (for example, all interrupts
enabled as Level 2 interrupts), the interrupt priority is assigned from highest to lowest as
specified in Table 39 on page 81. Level 3 interrupts always have higher priority than Level
2 interrupts, which in turn, always have higher priority than Level 1 interrupts. Within
each interrupt priority levels (Level 1, Level 2 or Level 3), priority is assigned as specified
in Table 39. Reset and System Exceptions have the highest priority.
System Exceptions
System Exceptions are generated for stack overflow, illegal instructions, divide-by-zero
and divide overflow, etc. The System Exceptions are not affected by the IRQE and share a
single vector.
Each exception has a bit in the system exception status register. When a system exception
occurs it pushes the program counter and the flags on the stack, fetches the system excep-
tion vector from 000008H(similar to a IRQ) and the bit associated with that exception is
set in the status register. Additional exceptions from the same source are blocked until the
status bit of the particular exception is cleared by writing 1 to that status bit. Other types of
exceptions occur while servicing an exception. When this happens the processor again
PS022010-0811
P R E L I M I N A R Y
Interrupt Vectors and Priority
ZNEO® Z16F Series MCUs
Product Specification
84
vectors to the system exception vector and sets the associated exception status bit. The ser-
vice routine would then have to respond to the new exception.
When an illegal instruction occurs, the program counter and flags are pushed onto the
stack only once. If the associated exception bit is not Reset, the program counter and flags
cannot be pushed a second time.
Note:
Interrupt Assertion
Interrupt sources assert their interrupt requests for only a single system clock period (sin-
gle pulse). When the interrupt request is acknowledged by the ZNEO CPU, the corre-
sponding bit in the interrupt request register is cleared until the next interrupt occurs.
Writing 1 to the corresponding bit in the interrupt request register clears the interrupt
request.
Program code generates interrupts directly. Writing a 1 to the appropriate bit in the inter-
rupt request set register triggers an interrupt (assuming that interrupts are enabled). When
the interrupt request is acknowledged by the ZNEO CPU, the bit in the interrupt request
register is automatically cleared to 0.
System Exception Status Registers
When a System Exception occurs, the System Exception Status registers are read to deter-
mine which system exception occurred. These registers are read individually or read as a
16-bit quantity.
Table 41. System Exception Register High (SYSEXCPH)
Bits
7
6
5
DIV0
0
4
3
ILL
2
1
Reserved
0
0
Field
RESET
R/W
SPOVF
0
PCOVF
0
DIVOVF
0
0
0
0
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
Addr
FF_E020H
Bit
Description
[7]
Stack Pointer Overflow
SPOVF If this bit is 1, a stack pointer overflow exception occurred. Writing 1 to this bit clears it to 0.
[6] Program Counter Overflow
PCOVF If this bit is 1, a program counter overflow exception occurred. Writing 1 to this bit clears it to 0.
PS022010-0811
P R E L I M I N A R Y
Interrupt Assertion
ZNEO® Z16F Series MCUs
Product Specification
85
Bit
Description (Continued)
Divide by Zero
[5]
DIV0
If this bit is 1, a divide operation was executed where the denominator was zero. Writing 1 to
this bit clear it to 0.
[4]
Divide Over Flow
DIVOVF If this bit is 1, a divide overflow occurred. A divide overflow happens when the result is greater
than FFFFFFFFH. Writing 1 to this bit clears it to 0.
[3]
ILL
Illegal Instruction
If this bit is 1, an illegal instruction occurred. Writing 1 to this bit clears it to 0.
[2:0]
Reserved
These bits are reserved and must be programmed to 000.
Table 42. System Exception Register Low (SYSEXCPL)
Bits
7
6
5
Reserved
0
4
3
2
1
0
WDT
0
Field
RESET
R/W
WDTOSC PRIOSC
0
0
0
0
0
0
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
Addr
FF_E021H
Bit
Description
Reserved
[7:3]
These bits are reserved and must be programmed to 00000.
[2]
WDTOSC
WDT Oscillator Fail
If this bit is 1, a WDT oscillator fail exception occurred. Writing 1 to this bit clears it to 0.
[1]
PRIOSC
Primary Oscillator Fail
If this bit is 1, a primary oscillator fail exception occurred. Writing 1 to this bit clears it to 0.
[0]
WDT
Watchdog Timer Interrupt
If this bit is 1, a WDT exception occurred. Writing 1 to this bit clears it to 0.
Last IRQ Register
When an interrupt occurs, the 5th bit value of the interrupt vector is stored in the Last IRQ
Register, shown in Table 43. This register allows the software to determine which inter-
rupt source was last serviced. It is used by RTOS which have a single interrupt entry point.
To implement this the software must set all interrupt vectors to the entry point address.
The entry point service routine then reads this register to determine which source caused
the interrupt or exception and respond accordingly.
PS022010-0811
P R E L I M I N A R Y
Last IRQ Register
ZNEO® Z16F Series MCUs
Product Specification
86
Table 43. Last IRQ Register (LASTIRQ)
Bits
7
6
5
4
IRQADR
0
3
2
1
0
Field
RESET
R/W
Always 0
Always 00
0
0
0
0
1
0
0
R
R/W
R/W
R/W
R/W
R/W
R
R
Addr
FF_E023H
Interrupt Request 0 Register
The Interrupt Request 0 (IRQ0) Register, shown in Table 44, stores the interrupt requests
for both vectored and polled interrupts. When a request is presented to the interrupt con-
troller, the corresponding bit in the IRQ0 Register becomes 1. If interrupts are globally
enabled (vectored interrupts), the interrupt controller passes an interrupt request to the
ZNEO CPU. If interrupts are globally disabled (polled interrupts), the ZNEO CPU reads
the Interrupt Request 0 Register to determine if any interrupt requests are pending. Writing
1 to the bits in this register clears the interrupt. The bits of this register are set by writing 1
to the Interrupt Request 0 Set Regsiter (IRQ0SET) at address FF_E031H.
Table 44. Interrupt Request 0 Register (IRQ0) and Interrupt Request 0 Set Register (IRQ0SET)
Bits
7
T2I
6
T1I
5
T0I
4
3
2
I2CI
0
1
SPII
0
0
ADCI
0
Field
RESET
R/W
U0RXI
0
U0TXI
0
0
0
0
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
Addr
Field
RESET
R/W
FF_E030H
T2I
0
T1I
0
T0I
0
U0RXI
U0TXI
I2CI
0
SPII
0
ADCI
0
0
0
W
W
W
W
W
W
W
W
Addr
FF_E031H
Note: IRQ0SET at address FF_E031H is write only and used to set the interrupts identified.
Bit
Description
[7]
T2I
Timer 2 Interrupt Request
0 = No interrupt request is pending for timer 2.
1 = An interrupt request from timer 2 is awaiting service. Writing 1 to this bit resets it to 0.
[6]
T1I
Timer 1 Interrupt Request
0 = No interrupt request is pending for timer 1.
1 = An interrupt request from timer 1 is awaiting service. Writing 1 to this bit resets it to 0.
PS022010-0811
P R E L I M I N A R Y
Interrupt Request 0 Register
ZNEO® Z16F Series MCUs
Product Specification
87
Bit
Description (Continued)
[5]
T0I
Timer 0 Interrupt Request
0 = No interrupt request is pending for timer 0.
1 = An interrupt request from timer 0 is awaiting service. Writing 1 to this bit resets it to 0.
[4]
U0RXI
UART 0 Receiver Interrupt Request
0 = No interrupt request is pending for the UART 0 receiver.
1 = An interrupt request from the UART 0 receiver is awaiting service. Writing 1 to this bit
resets it to 0.
[3]
U0TXI
UART 0 Transmitter Interrupt Request
0 = No interrupt request is pending for the UART 0 transmitter.
1 = An interrupt request from the UART 0 transmitter is awaiting service. Writing 1 to this bit
resets it to 0.
[2]
I2CI
I2C Interrupt Request
0 = No interrupt request is pending for the I2C.
1 = An interrupt request from the I2C is awaiting service. Writing 1 to this bit resets it to 0.
[1]
SPII
SPI Interrupt Request
0 = No interrupt request is pending for the SPI.
1 = An interrupt request from the SPI is awaiting service. Writing 1 to this bit resets it to 0.
[0]
ADCI
ADC Interrupt Request
0 = No interrupt request is pending for ADC.
1 = An interrupt request from ADC is awaiting service. Writing 1 to this bit resets it to 0.
Interrupt Request 1 Register
The Interrupt Request 1 (IRQ1) Register, shown in Table 45, stores interrupt requests for
both vectored and polled interrupts. When a request is presented to the interrupt controller,
the corresponding bit in the IRQ1 Register becomes 1. If interrupts are globally enabled
(vectored interrupts), the interrupt controller passes an interrupt request to the ZNEO
CPU. If interrupts are globally disabled (polled interrupts), the ZNEO CPU reads the
Interrupt Request 1 Register to determine, if any interrupt requests are pending. Writing 1
to the bits in this register clears the interrupt. The bits of this register are set by writing 1 to
the Interrupt Request 1 Set Register (IRQ1SET) at address FF_E035H.
PS022010-0811
P R E L I M I N A R Y
Interrupt Request 1 Register
ZNEO® Z16F Series MCUs
Product Specification
88
Table 45. Interrupt Request1 Register (IRQ1) and Interrupt Request1 Set Register (IRQ1SET)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PAD7I
0
PAD6I
0
PAD5I
0
PAD4I
0
PAD3I
0
PAD2I
0
PAD1I
0
PAD0I
0
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
Addr
Field
RESET
R/W
FF_E034H
PAD7I
PAD6I
PAD5I
PAD4I
PAD3I
PAD2I
PAD1I
PAD0I
0
0
0
0
0
0
0
0
W
W
W
W
W
W
W
W
Addr
FF_E035H
Note: IRQ1SET at address FF_E035H is write only and used to set the interrupts identified.
Bit
Description
[7:0]
PADxI
Port A/D Pin x Interrupt Request
0 = No interrupt request is pending for GPIO port A/D pin x.
1 = An interrupt request from GPIO port A/D pin x is awaiting service. Writing 1 to these bits
resets it to 0.
Here, x indicates the specific GPIO port pin number (0 through 7). PAD7I and PAD0I have
interrupt sources other than Port A and Port D as selected by the Port A IRQ MUX registers.
PAD7I is configured to provide the comparator interrupt. PAD0I is configured to provide the
OCD interrupt.
Note: The above IRQ1 bits are set any time the selected port is toggled. The setting of these bits
are not affected by the associated interrupt enable bits.
Interrupt Request 2 Register
The Interrupt Request 2 (IRQ2) Register, shown in Table 46, stores interrupt requests for
both vectored and polled interrupts. When a request is presented to the interrupt controller,
the corresponding bit in the IRQ2 Register becomes 1. If interrupts are globally enabled
(vectored interrupts), the interrupt controller passes an interrupt request to the ZNEO
CPU. If interrupts are globally disabled (polled interrupts), the ZNEO CPU reads the
Interrupt Request 1 Register to determine, if any interrupt requests are pending. Writing 1
to the bits in this register clears the interrupt. The bits of this register are set by writing 1 to
the Interrupt Request 2 Set Register (IRQ2SET) at address FF_E039H.
PS022010-0811
P R E L I M I N A R Y
Interrupt Request 2 Register
ZNEO® Z16F Series MCUs
Product Specification
89
Table 46. Interrupt Request 2 Register (IRQ2) and Interrupt Request 2 Set Register (IRQ2SET)
Bits
7
6
5
4
3
2
1
0
Field
PWMTI
U1RXI
U1TXI
PWMFI
PC3I/
PC2I/
PC1I/
PC0I/
DMA3I
DMA2I
DMA1I
DMA0I
RESET
R/W
0
0
0
0
0
0
0
0
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
R/W1C
Addr
Field
FF_E038H
PWMTI
U1RXI
U1TXI
PWMFI
PC3I/
PC2I/
PC1I/
PC0I/
DMA3I
DMA2I
DMA1I
DMA0I
RESET
R/W
0
0
0
0
0
0
0
0
W
W
W
W
W
W
W
W
Addr
FF_E039H
Note: IRQ2SET at address FF_E039H is write only and used to set the interrupts identified.
Bit
Description
[7]
PWM Timer Interrupt Request
PWMTI 0 = No interrupt request is pending for the PWM timer.
1 = An interrupt request from the PWM timer is awaiting service. Writing 1 to this bit resets it to
0.
[6]
U1RXI
UART 1 Receiver Interrupt Request
0 = No interrupt request is pending for the UART 1 receiver.
1 = An interrupt request from the UART 1 receiver is awaiting service. Writing 1 to this bit
resets it to 0.
[5]
U1TXI
UART 1 Transmitter Interrupt Request
0 = No interrupt request is pending for the UART 1 transmitter.
1 = An interrupt request from the UART 1 transmitter is awaiting service. Writing 1 to this bit
resets it to 0.
[4]
PWM Fault Interrupt Request
PWMFI 0 = No interrupt request is pending for the PWM fault.
1 = An interrupt request from the PWM fault is awaiting service. Writing 1 to this bit resets it to
0.
[3:0]
PCxI/
DMAxI
Port C Pin x or DMA x Interrupt Request
0 = No interrupt request is pending for GPIO port C pin x or DMA x.
1 = An interrupt request from GPIO port C pin x or DMAx is awaiting service. Writing 1 to this
bit resets it to 0.
Where x indicates the specific GPIO port C pin or DMA number (0 through 3).
PS022010-0811
P R E L I M I N A R Y
Interrupt Request 2 Register
ZNEO® Z16F Series MCUs
Product Specification
90
IRQ0 Enable High and Low Bit Registers
The IRQ0 enable high and low bit registers, shown in Tables 48 and 49, form a priority
encoded enabling for interrupts in the Interrupt Request 0 Register. Priority is generated
by setting bits in each register. Table 47 describes the priority control for IRQ0.
Table 47. IRQ0 Enable and Priority Encoding
IRQ0ENH[x]
IRQ0ENL[x]
Priority
Disabled
Level 1
Level 2
Level 3
Description
Disabled
Low
0
0
1
1
0
1
0
1
Nominal
High
Note: x indicates the range of register bits 0 through 7.
Table 48. IRQ0 Enable High Bit Register (IRQ0ENH)
Bits
7
T2ENH
0
6
T1ENH
0
5
T0ENH
0
4
3
2
1
0
Field
RESET
R/W
U0RENH U0TENH I2CENH
SPIENH ADCENH
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E032H
Bit
Description
[7]
T2ENH
Timer 2 Interrupt Request Enable High Bit.
Timer 0 Interrupt Request Enable High Bit.
Timer 0 Interrupt Request Enable High Bit.
[6]
T1ENH
[5]
T0ENH
[4]
U0RENH
UART 0 Receive Interrupt Request Enable High Bit.
UART 0 Transmit Interrupt Request Enable High Bit.
I2C Interrupt Request Enable High Bit.
[3]
U0TENH
[2]
I2CENH
[1]
SPI Interrupt Request Enable High Bit.
SPIENH
[0]
ADC Interrupt Request Enable High Bit.
ADCENH
PS022010-0811
P R E L I M I N A R Y IRQ0 Enable High and Low Bit Registers
ZNEO® Z16F Series MCUs
Product Specification
91
Table 49. IRQ0 Enable Low Bit Register (IRQ0ENL)
Bits
7
T2ENL
0
6
T1ENL
0
5
T0ENL
0
4
3
2
I2CENL
0
1
0
Field
RESET
R/W
U0RENL U0TENL
SPIENL ADCENL
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E033H
Bit
Description
[7]
T2ENL
Timer 2 Interrupt Request Enable Low Bit.
Timer 1 Interrupt Request Enable Low Bit.
Timer 0 Interrupt Request Enable Low Bit.
[6]
T1ENL
[5]
T0ENL
[4]
U0RENL
UART 0 Receive Interrupt Request Enable Low Bit.
UART 0 Transmit Interrupt Request Enable Low Bit.
I2C Interrupt Request Enable Low Bit.
[3]
U0TENL
[2]
I2CENL
[1]
SPI Interrupt Request Enable Low Bit.
SPIENL
[0]
ADC Interrupt Request Enable Low Bit.
ADCENL
IRQ1 Enable High and Low Bit Registers
The IRQ1 Enable High and Low Bit registers, shown in Tables 51 and 52, form a priority
encoded enabling for interrupts in the Interrupt Request 1 Register. Priority is generated
by setting bits in each register. Table 50 describes the priority control for IRQ1.
Table 50. IRQ1 Enable and Priority Encoding
IRQ1ENH[x]
IRQ1ENL[x]
Priority
Disabled
Level 1
Level 2
Level 3
Description
Disabled
Low
0
0
1
1
0
1
0
1
Nominal
High
Note: x indicates the register bits from 0 through 7.
PS022010-0811
P R E L I M I N A R Y IRQ1 Enable High and Low Bit Registers
ZNEO® Z16F Series MCUs
Product Specification
92
Table 51. IRQ1 Enable High Bit Register (IRQ1ENH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PAD7ENH PAD6ENH PAD5ENH PAD4ENH PAD3ENH PAD2ENH PAD1ENH PAD0ENH
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E036H
Bit
Description
[7:0]
Port A/D Bit[x] Interrupt Request Enable High Bit.
PADxENH
Table 52. IRQ1 Enable Low Bit Register (IRQ1ENL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PAD7ENL PAD6ENL PAD5ENL PAD4ENL PAD3ENL PAD2ENL PAD1ENL PAD0ENL
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E037H
Bit
Description
[7:0]
Port A/D Bit[x] Interrupt Request Enable Low Bit.
PADxENL
IRQ2 Enable High and Low Bit Registers
The IRQ2 Enable High and Low Bit registers, shown in Tables 54 and 55, form a priority
encoded enabling for interrupts in the Interrupt Request 2 Register. Priority is generated
by setting bits in each register. Table 53 describes the priority control for IRQ2.
Table 53. IRQ2 Enable and Priority Encoding
IRQ2ENH[x]
IRQ2ENL[x]
Priority
Disabled
Level 1
Level 2
Level 3
Description
Disabled
Low
0
0
1
1
0
1
0
1
Nominal
High
Note: x indicates the register bits from 0 through 7.
PS022010-0811
P R E L I M I N A R Y IRQ2 Enable High and Low Bit Registers
ZNEO® Z16F Series MCUs
Product Specification
93
Table 54. IRQ2 Enable High Bit Register (IRQ2ENH)
Bits
7
6
5
4
3
2
1
0
PWMTENH U1RENH
U1TENH PWMFENH
C3ENH/
C2ENH/
C1ENH/
C0ENH/
Field
DMA3ENH DMA2ENH DMA1ENH DMA0ENH
RESET
R/W
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E03AH
Bit
Description
[7]
PWM Timer Interrupt Request Enable High Bit.
PWMTENH
[6]
U1RENH
UART 1 Receive Interrupt Request Enable High Bit.
UART 1 Transmit Interrupt Request Enable High Bit.
PWM Fault Interrupt Request Enable High Bit.
Port Cx or DMAx Interrupt Request Enable High Bit.
[5]
U1TENH
[4]
PWMFENH
[3:0]
CxENH/
DMAxENH
Table 55. IRQ2 Enable Low Bit Register (IRQ2ENL)
Bits
7
6
5
4
3
2
1
0
Field
PWMTENL U1RENL
U1TENL PWMFENL C3ENL/
C2ENL/
C1ENL/
C0ENL/
DMA3ENL DMA2ENL DMA1ENL DMA0ENL
RESET
R/W
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E03BH
Bit
Description
[7]
PWM Timer Interrupt Request Enable Low Bit.
PWMTENL
[6]
U1RENL
UART 1 Receive Interrupt Request Enable Low Bit.
UART 1 Transmit Interrupt Request Enable Low Bit.
[5]
U1TENL
PS022010-0811
P R E L I M I N A R Y IRQ2 Enable High and Low Bit Registers
ZNEO® Z16F Series MCUs
Product Specification
94
Bit
Description
[4]
PWM Fault Interrupt Request Enable Low Bit.
PWMFENL
[3:0]
Port Cx or DMAx Interrupt Request Enable Low Bit.
CxENL/
DMAxENL
PS022010-0811
P R E L I M I N A R Y IRQ2 Enable High and Low Bit Registers
ZNEO® Z16F Series MCUs
Product Specification
95
Timers
The ZNEO® Z16F Series contains three 16-bit reloadable timers used for timing, event
counting or generation of pulse width modulated (PWM) signals. These timers include the
following features:
• 16-bit reload counter
• Programmable prescaler with values ranging from 1 to 128
• PWM output generation (single or differential)
• Capture and compare capability
• External input pin for event counting, clock gating or capture signal
• Complementary timer output pins
• Timer interrupt
Architecture
Capture and compare capability measures the velocity from a tachometer wheel or reads
sensor outputs for rotor position for brushless DC motor commutation. Figure 20 displays
the architecture of the timer.
PS022010-0811
P R E L I M I N A R Y
Timers
ZNEO® Z16F Series MCUs
Product Specification
96
Timer Block
Timer
Control
Data
Bus
Block
Control
16-Bit
Reload Register
Interrupt,
PWM,
Timer
Interrupt
and
Timer Output
Control
TOUT
TOUT
System
Clock
16-Bit Counter
with Prescaler
Timer
Input
Gate
Input
16-Bit
PWM/Compare
Capture
Input
Figure 20. Timer Block Diagram
Operation
The general-purpose timer is a 16-bit up-counter. In normal operation, the timer is initial-
ized to 0001H. When the timer is enabled, it counts up to the value contained in the
Reload High and Low Byte registers, then resets to 0001H. The counter either halts or
continues depending on the mode.
Minimum time-out delay (1 system clock) is set by loading the value 0001Hinto the
Timer Reload High and Low byte registers and setting the prescale value to 1.
Maximum time-out delay (216 * 27 system clocks) is set by loading the value 0000Hinto
the Timer Reload High and Low byte registers and setting the prescale value to 128. When
the timer reaches FFFFH, the timer rolls over to 0000H.
If the reload register is set to a value less than the current counter value, the counter con-
tinues counting until it reaches FFFFHand then resets to 0000H. Then the timer continues
to count until it reaches the reload value and it resets to 0001H.
When T0IN0, T0IN1 and T0IN2 functions are enabled on the PB0, PB1 and PB2 pins,
each Timer 0 input will have the same effect as the single Timer 0 Input pin T0IN. For
example, if the Timer 0 is in Capture Mode, any transitions on any of the PB0, PB1 and
PB2 pins will cause a Capture.
Note:
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
97
Timer Operating Modes
The timers are configured to operate in the following modes:
ONE-SHOT Mode
In ONE-SHOT Mode, the timer counts up to the 16-bit reload value stored in the Timer
Reload High and Low byte registers. The timer input is the system clock. When the timer
reaches the reload value, it generates an interrupt and the count value in the Timer High
and Low byte registers is reset to 0001H. The timer is automatically disabled and stops
counting.
If the timer output alternate function is enabled, the timer output pin changes state for one
system clock cycle (from Low to High then back to Low if TPOL = 0) at timer Reload. If
the timer output is required to make a permanent state change on ONE-SHOT time-out,
first set the TPOL bit in the Timer Control 1 Register to the start value before beginning
ONE-SHOT Mode. Then, after starting the timer, set TPOLto the opposite value.
Observe the following steps to configure a timer for ONE-SHOT Mode and initiate the
count:
1. Write to the timer control registers to:
–
–
–
–
Disable the timer
Configure the timer for ONE-SHOT Mode
Set the prescale value
Set the initial output level (High or Low) using the TPOL bit for the timer output
alternate function
–
Set the INTERRUPT Mode
2. Write to the Timer High and Low Byte registers to set the starting count value.
3. Write to the Timer Reload High and Low Byte registers to set the reload value.
4. Enable the timer interrupt, if required and set the timer interrupt priority by writing to
the relevant interrupt registers.
5. When using the timer output function, configure the associated GPIO port pin for the
timer output alternate function.
6. Write to the Timer Control 1 Register to enable the timer and initiate counting.
The timer period is calculated by the following equation (start value = 1):
Reload Value – Start Value + 1 Prescale
One-Shot Mode Time-Out Period (s) = -----------------------------------------------------------------------------------------------------
System Clock Frequency (Hz)
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
98
TRIGGERED ONE-SHOT Mode
In TRIGGERED ONE-SHOT Mode, the timer operates as follows:
1. The timer is nonactive until a trigger is received. The timer trigger is taken from the
timer input pin. The TPOL bit in the Timer Control 1 Register selects whether the trig-
ger occurs on the rising edge or the falling edge of the timer input signal.
2. Following the trigger event, the timer counts system clocks up to the 16-bit reload
value stored in the Timer Reload High and Low Byte registers.
3. After reaching the reload value, the timer outputs a pulse on the timer output pin,
generates an interrupt and resets the count value in the Timer High and Low Byte
registers to 0001H. The duration of the output pulse is a single system clock. The
TPOL bit also sets the polarity of the output pulse.
4. The timer now idles until the next trigger event. Trigger events, which occur while the
timer is responding to a previous trigger is ignored.
Observe the following steps to configure timer 0 in TRIGGERED ONE-SHOT Mode and
initiate operation:
1. Write to the timer control registers to:
–
–
–
–
Disable the timer
Configure the timer for TRIGGERED ONE-SHOT Mode
Set the prescale value
Set the initial output level (High or Low) via the TPOL bit for the timer output
alternate function
–
Set the INTERRUPT Mode
2. Write to the Timer High and Low Byte registers to set the starting count value.
3. Write to the Timer Reload High and Low Byte registers to set the reload value.
4. Enable the timer interrupt, if required and set the timer interrupt priority by writing to
the relevant interrupt registers.
5. When using the timer output function, configure the associated GPIO port pin for the
timer output alternate function.
6. Write to the Timer Control 1 Register to enable the timer. Counting does not start until
the appropriate input transition occurs.
The timer period is calculated by the following equation (Start Value = 1):
Reload Value – Start Value + 1 Prescale
Triggered One-Shot Mode Time-Out Period (s) = ----------------------------------------------------------------------------------------------------------
System Clock Frequency (Hz)
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
99
CONTINUOUS Mode
In CONTINUOUS Mode, the timer counts up to the 16-bit reload value stored in the
Timer Reload High and Low Byte registers. After reaching the reload value, the timer gen-
erates an interrupt, the count value in the Timer High and Low Byte registers is reset to
0001Hand counting resumes. If the timer output alternate function is enabled, the timer
output pin changes state (from Low to High or High to Low) after timer Reload.
Observe the following steps to configure a timer for CONTINUOUS Mode and initiate
count:
1. Write to the timer control registers to:
–
–
–
–
Disable the timer
Configure the timer for CONTINUOUS Mode
Set the prescale value
Set the initial output level (High or Low) through TPOL for the timer output
alternate function
2. Write to the Timer High and Low Byte registers to set the starting count value (usually
0001H). This only affects the first pass in CONTINUOUS Mode. After the first timer
reload in CONTINUOUS Mode, counting always begins at the reset value of 0001H.
3. Write to the Timer Reload High and Low Byte registers to set the Reload period.
4. Enable the timer interrupt, if required and set the timer interrupt priority by writing to
the relevant interrupt registers.
5. When using the timer output function, configure the associated GPIO port pin for the
timer output alternate function.
6. Write to the Timer Control 1 Register to enable the timer and initiate counting.
The timer period is calculated by the following equation:
Reload Value Prescale
Continuous Mode Time-Out Period (s) = ------------------------------------------------------------------------
System Clock Frequency (Hz)
If an initial starting value other than 0001His loaded into the Timer High and Low Byte
registers, use the ONE-SHOT Mode equation to determine the first time-out period.
COUNTER and COMPARATOR COUNTER Modes
In COUNTER Mode, the timer counts input transitions from a GPIO port pin. The timer
input is taken from the associated GPIO port pin. The TPOL bit in the Timer Control 1
Register selects whether the count occurs on the rising edge or the falling edge of the timer
input signal. In COUNTER Mode, the prescaler is disabled.
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
100
The input frequency of the timer input signal must not exceed one-fourth the system
clock frequency.
Caution:
In COMPARATOR COUNTER Mode, the timer counts output transitions from an analog
comparator output. The timer takes its input from the output of the comparator. The TPOL
bit in the Timer Control 1 Register selects whether the count occurs on the rising edge or
the falling edge of the comparator output signal. The prescaler is disabled in the COM-
PARATOR COUNTER Mode.
The frequency of the comparator output signal must not exceed one-fourth the system
clock frequency.
Caution:
After reaching the reload value stored in the Timer Reload High and Low Byte registers,
the timer generates an interrupt. The count value in the Timer High and Low Byte registers
is reset to 0001Hand counting resumes.
If the timer output alternate function is enabled, the timer output pin changes state (from
Low to High or High to Low) at timer Reload.
Observe the following steps to configure a timer for COUNTER and COMPARATOR
COUNTER modes and initiate the count:
1. Write to the timer control registers to:
–
–
–
Disable the timer.
Configure the timer for COUNTER or COMPARATOR COUNTER Mode.
Select either the rising edge or falling edge of the timer input or comparator output
signal for the count. This also sets the initial logic level (High or Low) for the
timer output alternate function. However, enabling the timer output function is not
required.
2. Write to the Timer Reload High and Low Byte registers to set the starting count value.
This affects only the first pass in the COUNTER modes. After the first timer Reload,
counting always begins at the reset value of 0001H.
3. Write to the Timer Reload High and Low Byte registers to set the reload value.
4. Enable the timer interrupt, if appropriate and set the timer interrupt priority by writing
to the relevant interrupt registers.
5. Configure the associated GPIO port pin for the timer input alternate function
(COUNTER Mode).
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
101
6. When using the timer output function, configure the associated GPIO port pin for the
timer output alternate function.
7. Write to the Timer Control 1 Register to enable the timer.
PWM SINGLE and DUAL OUTPUT Modes
In PWM SINGLE OUTPUT Mode, the timer outputs a PWM output signal through a
GPIO Port pin. In PWM DUAL OUTPUT Mode, the timer outputs a PWM output signal
and also its complement through two GPIO port pins. The timer first counts up to the 16-
bit PWM match value stored in the timer PWM High and Low Byte registers. When the
timer count value matches the PWM value, the timer output toggles. The timer continues
counting until it reaches the reload value stored in the Timer Reload High and Low Byte
registers. When it reaches the reload value, the timer generates an interrupt. The count
value in the Timer High and Low Byte registers is reset to 0001Hand counting resumes.
The timer output signal begins with value = TPOLand then transits to TPOL, when the
timer value matches the PWM value. The timer output signal returns to TPOLafter the
timer reaches the reload value and is reset to 0001H.
In PWM DUAL OUTPUT Mode, the timer also generates a second PWM output signal,
timer output complement (TOUT). A programmable deadband is configured (PWMDfield)
to delay (0 to 128 system clock cycles) the Low to a High (inactive to active) output tran-
sitions on these two pins. This configuration ensures a time gap between the deassertion of
one PWM output to the assertion of its complement.
Observe the following steps to configure a timer for PWM SINGLE or DUAL OUTPUT
Mode and initiate the PWM operation:
1. Write to the timer control registers to:
–
–
–
–
Disable the timer
Configure the timer for the selected PWM Mode
Set the prescale value
Set the initial logic level (High or Low) and PWM High or Low transition for the
timer output alternate function with the TPOL bit
–
Set the deadband delay (DUAL OUTPUT Mode) with the PWMDfield
2. Write to the Timer High and Low Byte registers to set the starting count value
(typically 0001H). The starting count value only affects the first pass in PWM Mode.
After the first timer reset in PWM Mode, counting always begins at the reset value of
0001H.
3. Write to the PWM High and Low Byte registers to set the PWM value.
4. Write to the Timer Reload High and Low Byte registers to set the reload value (PWM
period). The reload value must be greater than the PWM value.
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
102
5. Enable the timer interrupt, if required and set the timer interrupt priority by writing to
the relevant interrupt registers.
6. Configure the associated GPIO port pin(s) for the timer output alternate function.
7. Write to the Timer Control 1 Register to enable the timer and initiate counting.
The PWM period is determined by the following equation:
Reload Value Prescale
PWM Period (s) = ------------------------------------------------------------------------
System Clock Frequency (Hz)
If an initial starting value other than 0001His loaded into the Timer High and Low Byte
registers, use the ONE-SHOT Mode equation to determine the first PWM time-out period.
If TPOLis set to 0, the ratio of the PWM output High time to the total period is determined
by:
Reload Value – PWM Value
--------------------------------------------------------------------
PWM Output High Time Ratio (%) =
100
Reload Value
If TPOLis set to 1, the ratio of the PWM output High time to the total period is determined
by:
PWM Value
Reload Value
--------------------------------
PWM Output High Time Ratio (%) =
100
CAPTURE Modes
There are three CAPTURE modes which provide slightly different methods for recording
the time or time interval between timer input events. These modes are CAPTURE Mode,
CAPTURE RESTART Mode and CAPTURE COMPARE Mode. In all of the three modes,
when the appropriate timer input transition (capture event) occurs, the timer counter value
is captured and stored in the PWM High and Low Byte registers. The TPOL bit in the
Timer Control 1 Register determines if the Capture occurs on a rising edge or a falling
edge of the timer input signal. The TICONFIG bit determines whether interrupts are gen-
erated on capture events, reload events or both. The INCAP bit in Timer Control 0 Regis-
ter clears to indicate an interrupt caused by a reload event and sets to indicate the timer
interrupt is caused by an input capture event.
If the timer output alternate function is enabled, the timer output pin changes state (from
Low to High or High to Low) at timer Reload. The initial value is determined by the
TPOL bit.
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
103
CAPTURE Mode
When the timer is enabled in CAPTURE Mode, it counts continuously and resets to
0000H from FFFFH. When the Capture event occurs, the timer counter value is captured
and stored in the PWM High and Low Byte registers, an interrupt is generated and the
timer continues counting. The timer continues counting up to the 16-bit reload value
stored in the Timer Reload High and Low Byte registers. On reaching the reload value, the
timer generates an interrupt and continues counting.
CAPTURE RESTART Mode
When the timer is enabled in CAPTURE RESTART Mode, it counts continuously until the
capture event occurs or the timer count reaches the 16-bit Compare value stored in the
Timer Reload High and Low Byte registers. If the Capture event occurs first, the timer
counter value is captured and stored in the PWM High and Low byte registers, an interrupt
is generated and the count value in the Timer High and Low Byte registers is Reset to
0001Hand counting resumes. If no Capture event occurs, on reaching the reload value, the
timer generates an interrupt, the count value in the Timer High and Low Byte registers is
Reset to 0001Hand counting resumes.
CAPTURE/COMPARE Mode
The CAPTURE/COMPARE Mode is identical to CAPTURE RESTART Mode except that
counting does not start until the first appropriate external timer reload high and low byte
input transition occurs. Every subsequent appropriate transition (after the first) of the
timer reload high and low byte input signal captures the current count value. When the
Capture event occurs, an interrupt is generated, the count value in the Timer Reload High
and Low byte High and Low Byte registers is reset to 0001Hand counting resumes. If no
Capture event occurs, on reaching the Compare value, the timer generates an interrupt, the
count value in the Timer High and Low Byte registers is Reset to 0001Hand counting
resumes.
Observe the following steps to configure a timer for one of the CAPTURE modes and ini-
tiate the count:
1. Write to the timer control registers to:
–
–
–
–
–
Disable the timer
Configure the timer for the selected CAPTURE Mode
Set the prescale value
Set the Capture edge (rising or falling) for the timer input
Configure the timer interrupt to be generated at the input capture event, the reload
event or both by setting TICONFIGfield
2. Write to the Timer Reload High and Low Byte registers to set the starting count value
(typically 0001H).
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
104
3. Write to the Timer Reload High and Low Byte registers to set the reload value.
4. Enable the timer interrupt, if appropriate and set the timer interrupt priority by writing
to the relevant interrupt registers.
5. Configure the associated GPIO port pin for the timer input alternate function.
6. Write to the Timer Control 1 Register to enable the timer. In CAPTURE and CAP-
TURE RESTART modes, the timer begins counting. In CAPTURE COMPARE Mode
the timer does not start counting until the first appropriate input transition occurs.
In CAPTURE modes, the elapsed time from timer start to Capture event is calculated
using the following equation (start value = 1):
Capture Value – Start Value + 1 Prescale
Capture Elapsed Time (s) = -----------------------------------------------------------------------------------------------------------
System Clock Frequency (Hz)
COMPARE Mode
In COMPARE Mode, the timer counts up to the 16-bit Compare value stored in the Timer
Reload High and Low Byte registers. After reaching the compare value, the timer gener-
ates an interrupt and counting continues (the timer value is not reset to 0001H). If the
timer output alternate function is enabled, the timer output pin changes state (from Low to
High or High to Low).
If the timer reaches FFFFH, the timer rolls over to 0000Hand continues counting.
Observe the following steps to configure timer for COMPARE Mode and initiate the
count:
1. Write to the timer control registers to:
–
–
–
–
Disable the timer
Configure the timer for COMPARE Mode
Set the prescale value
Set the initial logic level (High or Low) for the timer output alternate function, if
required
2. Write to the Timer High and Low Byte registers to set the starting count value.
3. Write to the Timer Reload High and Low Byte registers to set the Compare value.
4. Enable the timer interrupt, if appropriate and set the timer interrupt priority by writing
to the relevant interrupt registers.
5. When using the timer output function, configure the associated GPIO port pin for the
timer output alternate function.
6. Write to the Timer Control 1 Register to enable the timer and initiate counting.
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
105
The compare time is calculated by the following equation (Start Value = 1):
Compare Value – Start Value + 1 Prescale
Compare Mode Time (s) = --------------------------------------------------------------------------------------------------------------
System Clock Frequency (Hz)
GATED Mode
In GATED Mode, the timer counts only when the timer input signal is in its active state as
determined by the TPOL bit in the Timer Control 1 Register. When the timer input signal
is active, counting begins. A timer interrupt is generated when the timer input signal tran-
sits from active to inactive state or a timer reload occurs. To determine if a timer input sig-
nal deassertion generated the interrupt, read the associated GPIO input value and compare
to the value stored in the TPOL bit.
The timer counts up to the 16-bit reload value stored in the Timer Reload High and Low
Byte registers. On reaching the reload value, the timer generates an interrupt, the count
value in the Timer High and Low Byte registers is Reset to 0001Hand counting continues
as long as the timer input signal is active. If the timer output alternate function is enabled,
the timer output pin changes state (from Low to High or from High to Low) at timer
reload.
Observe the following steps to configure a timer for GATED Mode and initiate the count:
1. Write to the timer control registers to:
–
–
–
–
Disable the timer
Configure the timer for GATED Mode
Set the prescale value
Select the active state of the timer input through the TPOL bit
2. Write to the Timer High and Low Byte registers to set the initial count value. This
affects only the first pass in GATED Mode. After the first timer Reset in GATED
Mode, counting always begins at the reset value of 0001H.
3. Write to the Timer Reload High and Low Byte registers to set the reload value.
4. Enable the timer interrupt and set the timer interrupt priority by writing to the relevant
interrupt registers.
5. Configure the timer interrupt to be generated only at the input deassertion event, the
reload event or both by setting TICONFIGfield of the Timer Control 0 Register.
6. Configure the associated GPIO port pin for the timer input alternate function.
7. Write to the Timer Control 1 Register to enable the timer.
8. The timer counts when the timer input is equal to the TPOL bit.
PS022010-0811
P R E L I M I N A R Y
Timer Operating Modes
ZNEO® Z16F Series MCUs
Product Specification
106
Reading Timer Count Values
The current count value in the timer is read while counting (enabled). This has no effect on
timer operation. Normally, the count must be read with one 16-bit operation. However, 8-
bit reads are done with the following method. When the timer is enabled and the timer
high byte register is read, the contents of the timer low byte register are placed in a holding
register. A subsequent read from the timer low byte register returns the value in the hold-
ing register. This operation allows accurate reads of the full 16-bit timer count value when
enabled. When the timer is not enabled, a read from the timer low byte register returns the
actual value in the counter.
The Timers can be cascaded by using the Cascade bit in the Timer control registers. When
this bit is set for a Timer, the input source is redefined. When the Cascade bit is set for
Timer 0, the input for Timer 0 is the output of the Analog Comparator. When the Cascade
bit is set for Timer 1 and Timer 2, the output of Timer 0 and Timer 1 become the input for
Timer 1 and Timer 2, respectively. Any Timer Mode can be used. Timer 0 can be cascaded
to Timer 1 only by setting the Cascade bit for Timer 1. Timer 1 cascaded to Timer 2 only
by setting the Cascade bit for Timer 2. Or all three cascaded, Timer 0 to Timer 1 or Timer
2 for really long counts by setting the Cascade bit for Timer 1 and Timer 2.
Timer Control Register Definitions
Timer 0‒2 High and Low Byte Registers
The Timer 0‒2 High and Low Byte (TxH and TxL) registers, shown in Tables 56 and 57,
contain the current 16-bit timer count value. When the timer is enabled, a read from TxH
stores the value in TxL to a temporary holding register. A read from TxL always returns
this temporary register when the timer is enabled. When the timer is disabled, reads from
the TxL reads the register directly.
Writing to the Timer High and Low Byte registers while the timer is enabled is not recom-
mended. There are no temporary holding registers available for write operations, so simul-
taneous 16-bit writes are not possible. When either of the timer high or low byte registers
are written during counting, the 8-bit written value is placed in the counter (High or Low
Byte) at the next clock edge. The counter continues counting from the new value.
PS022010-0811
P R E L I M I N A R Y
Reading Timer Count Values
ZNEO® Z16F Series MCUs
Product Specification
107
Table 56. Timer 0‒2 High Byte Register (TxH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
TH
00H
R/W
Addr
FF‒E300H, FF‒E310H, FF‒E320H
Bit
Description
[7:0]
TH
Timer High and Low Byte
These two bytes, {TH[7:0], TL[7:0]}, contain the current 16-bit timer count value.
Table 57. Timer 0‒2 Low Byte Register (TXL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
TL
01H
R/W
Addr
FF‒E301H, FF‒E311H, FF‒E321H
Bit
Description
[7:0]
TL
Timer High and Low Byte
These two bytes, {TH[7:0], TL[7:0]}, contain the current 16-bit timer count value.
PS022010-0811
P R E L I M I N A R Y Timer 0‒2 High and Low Byte Registers
ZNEO® Z16F Series MCUs
Product Specification
108
Timer X Reload High and Low Byte Registers
The Timer 0‒2 Reload High and Low Byte (TxRH and TxRL) registers, shown in
Tables 58 and 59, store a 16-bit reload value, {TRH[7:0], TRL[7:0]}. Values written to the
Timer Reload High Byte Register are stored in a temporary holding register. When a write
to the Timer Reload Low Byte Register occurs, the temporary holding register value is
written to the Timer High Byte Register. This operation allows simultaneous updates of
the 16-bit timer reload value.
Table 58. Timer 0‒2 Reload High Byte Register (TxRH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
TRH
FFH
R/W
Addr
FF‒E302H, FF‒E312H, FF‒E322H
Bit
Description
[7:0]
TRH
Timer Reload High and Low
These two bytes form the 16-bit reload value, {TRH[7:0], TRL[7:0]}. This value sets the maxi-
mum count value which initiates a timer reload to 0001H.
Table 59. Timer 0‒2 Reload Low Byte Register (TxRL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
TRL
FF
R/W
Addr
FF‒E303H, FF‒E313H, FF‒E323H
Bit
Description
[7:0]
TRL
Timer Reload High and Low
These two bytes form the 16-bit reload value, {TRH[7:0], TRL[7:0]}. This value sets the maxi-
mum count value which initiates a timer reload to 0001H.
PS022010-0811
P R E L I M I N A R Y
Timer X Reload High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
109
Timer 0–2 PWM High and Low Byte Registers
The Timer 0‒2 PWM High and Low Byte (TxPWMH and TxPWML) registers, shown in
Tables 60 and 61, define PWM operations and store the timer counter values for the CAP-
TURE modes. These TxPWMH and TxPWML registers also store the 16-bit captured
timer value when operating in CAPTURE or CAPTURE/COMPARE modes.
Table 60. Timer 0–2 PWM High Byte Register (TxPWMH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PWMH
00H
R/W
Addr
FF‒E304H, FF‒E314H, FF‒E324H
Bit
Description
[7:0]
PWMH
Pulse-Width Modulator High and Low Bytes
These two bytes, {PWMH[7:0], PWML[7:0]}, form a 16-bit value which is compared to the cur-
rent 16-bit timer count. When a match occurs, the PWM output changes state. The PWM out-
put value is set by the TPOL bit in the Timer Control 1 Register (TxCTL1).
Table 61. Timer 0–2 PWM Low Byte Register (TxPWML)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PWML
00H
R/W
Addr
FF‒E305H, FF‒E315H, FF‒E315H
Bit
Description
[7:0]
PWML
Pulse-Width Modulator High and Low Bytes
These two bytes, {PWMH[7:0], PWML[7:0]}, form a 16-bit value which is compared to the cur-
rent 16-bit timer count. When a match occurs, the PWM output changes state. The PWM out-
put value is set by the TPOL bit in the Timer Control 1 Register (TxCTL1).
Timer 0–2 Control Registers
Timer 0–2 Control 0 Register
The Timer 0–2 Control 0 Register (TxCTL0), together with the Timer 0–2 Control 1
(TxCTL1) Register, determines timer configuration and operation.
PS022010-0811
P R E L I M I N A R Y
Timer 0–2 PWM High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
110
Table 62. Timer 0‒2 Control 0 Register (TxCTL0)
Bits
7
TMODE[3]
0
6
5
4
CASCADE
0
3
2
PWMD
000
1
0
Field
RESET
R/W
TICONFIG
00
INCAP
0
R/W
R/W
R/W
R/W
R
Addr
FF‒E306H, FF‒E316H, FF‒E326H
Bit
Description
[7]
Timer Mode High Bit
TMODE[3] This bit along with TMODE[2:0] field in T0CTL1 register determines the operating mode of
the timer. This bit is the most significant bit of the timer mode selection value. For more
details, see the Timer 0‒2 Control 1 Register (TxCTL1) section on page 111.
[6:5]
Timer Interrupt Configuration
TICONFIG This field configures timer interrupt definitions.
These bits affect all modes. The effect per mode is explained below:
ONE SHOT, CONTINUOUS, COUNTER, PWM, COMPARE, DUAL PWM, TRIGGERED
ONE-SHOT, COMPARATOR COUNTER:
0x Timer interrupt occurs on reload.
10 Timer interrupts are disabled.
11 Timer Interrupt occurs on reload.
GATED:
0x Timer interrupt occurs on reload.
10 Timer interrupt occurs on inactive gate edge.
11 Timer interrupt occurs on reload.
CAPTURE, CAPTURE/COMPARE, CAPTURE RESTART:
0x Timer interrupt occurs on reload and capture.
10 Timer interrupt occurs on capture only.
11 Timer interrupt occurs on reload only.
[4]
Timer Cascade
CASCADE This field allows the timers to be cascaded for larger counts. Only Counter Mode must be
used with this feature.
0 = The timer is not cascaded.
1 = Timer is cascaded. If timer 0 CASCADE bit is set, ANALOG COMPARATOR output is
used as input. If timer 1 CASCADE bit is set, the Timer 0 output is used as the input. If timer
2 CASCADE bit is set, the timer 1 output is used as input.
PS022010-0811
P R E L I M I N A R Y
Timer 0–2 Control Registers
ZNEO® Z16F Series MCUs
Product Specification
111
Bit
Description (Continued)
PWM Delay Value
[3:1]
PWMD
This field is a programmable delay to control the number of additional system clock cycles
following a PWM or Reload compare before the timer output or the timer output complement
is switched to the active state. This field ensures a time gap between deassertion of one
PWM output to the assertion of its complement.
No delay.
2 cycles delay.
4 cycles delay.
8 cycles delay.
16 cycles delay.
32 cycles delay.
64 cycles delay.
128 cycles delay.
[0]
INCAP
Input Capture Event
0 = Previous timer interrupt is not a result of a timer input capture event.
1 = Previous timer interrupt is a result of a timer input capture event.
Timer 0‒2 Control 1 Register
The Timer 0‒2 Control 1 (TxCTL1) Register enables/disables the timer, sets the prescaler
value and determines the timer operating mode.
Table 63. Timer 0‒2 Control 1 Register (TxCTL1)
Bits
7
6
TPOL
0
5
4
3
2
1
0
Field
RESET
R/W
TEN
0
PRES
000
TMODE
000
R/W
R/W
R/W
R/W
Addr
FF‒E307H, FF‒E317H, FF‒E327H
Bit
Description
[7]
TEN
0 = Timer is disabled.
1 = Timer is enabled.
Note: the TEN bit is cleared automatically when the timer stops.
PS022010-0811
P R E L I M I N A R Y
Timer 0–2 Control Registers
ZNEO® Z16F Series MCUs
Product Specification
112
Bit
Description (Continued)
[6]
TPOL
Timer Input/Output Polarity
This bit is a function of the current operating mode of the timer. It determines the polarity of
the input and/or output signal. When the timer is disabled, the timer output signal is set to
the value of this bit.
ONE-SHOT Mode
If the timer is enabled, the timer output signal pulses (changes state) for one system clock
cycle after timer Reload.
CONTINUOUS Mode
If the timer is enabled, the timer output signal is complemented after timer Reload.
COUNTER Mode
If the timer is enabled, the timer output signal is complemented after timer reload.
0 = Count occurs on the rising edge of the timer input signal.
1 = Count occurs on the falling edge of the timer input signal.
PWM SINGLE OUTPUT Mode
When enabled, the timer output is forced to TPOL after PWM count match and forced back
to TPOL after Reload.
CAPTURE Mode
If the timer is enabled, the timer output signal is complemented after timer Reload.
0 = Count is captured on the rising edge of the timer input signal.
1 = Count is captured on the falling edge of the timer input signal.
COMPARE Mode
The timer output signal is complemented after timer Reload.
GATED Mode
The timer output signal is complemented after timer Reload.
0 = Timer counts when the timer input signal is High and interrupts are generated on the fall-
ing edge of the timer input.
1 = Timer counts when the timer input signal is Low and interrupts are generated on the ris-
ing edge of the timer input.
CAPTURE/COMPARE Mode
If the timer is enabled, the timer output signal is complemented after timer Reload.
0 = Counting starts on the first rising edge of the timer Input signal.
The current count is captured on subsequent rising edges of the timer
input signal.
1 = Counting starts on the first falling edge of the timer input signal.
The current count is captured on subsequent falling edges of the timer
input signal.
PWM DUAL OUTPUT Mode
If enabled, the timer output is set=TPOL after PWM match and set = TPOL after Reload. If
enabled the timer output complement takes on the opposite value of the timer output. The
PWMD field in the T0CTL1 Register determines an optional added delay on the assertion
(Low to High) transition of both timer output and the timer output complement for deadband
generation.
PS022010-0811
P R E L I M I N A R Y
Timer 0–2 Control Registers
ZNEO® Z16F Series MCUs
Product Specification
113
Bit
Description (Continued)
[6]
TPOL
(cont’d)
CAPTURE RESTART Mode
If the timer is enabled, the timer output signal is complemented after timer Reload.
0 = Count is captured on the rising edge of the timer input signal.
1 = Count is captured on the falling edge of the timer input signal.
ANALOG COMPARATOR COUNTER Mode
If the timer is enabled, the timer output signal is complemented after timer Reload.
0 = Count is captured on the rising edge of the timer input signal.
1 = Count is captured on the falling edge of the timer input signal.
TRIGGERED ONE-SHOT Mode
If the timer is enabled, the timer output signal is complemented after timer Reload.
0 = The timer triggers on a Low to High transition on the input.
1 = The timer triggers on a High to Low transition on the input.
PRES
[5:3]
The timer input clock is divided by 2
, where PRES is set from 0 to 7. The prescaler is
PRES
reset each time the timer is disabled. This ensures proper clock division each time the timer
is restarted.
000 = Divide by 1
001 = Divide by 2
010 = Divide by 4
011 = Divide by 8
100 = Divide by 16
101 = Divide by 32
110 = Divide by 64
111 = Divide by 128
[2:0]
This field along with the TMODE[3]bit in T0CTL0 register determines the operating mode of
TMODE[2:0] the timer. TMODE[3:0] selects from the following modes:
0000 = ONE-SHOT Mode
0001 = CONTINUOUS Mode
0010 = COUNTER Mode
0011 = PWM SINGLE OUTPUT Mode
0100 = CAPTURE Mode
0101 = COMPARE Mode
0110 = GATED Mode
0111 = CAPTURE/COMPARE Mode
1000 = PWM DUAL OUTPUT Mode
1001 = CAPTURE RESTART Mode
1010 = COMPARATOR COUNTER Mode
1011 = TRIGGERED ONE-SHOT Mode
PS022010-0811
P R E L I M I N A R Y
Timer 0–2 Control Registers
ZNEO® Z16F Series MCUs
Product Specification
114
Multi-Channel PWM Timer
The ZNEO® Z16F Series includes a Multi-Channel PWM optimized for motor control
applications. The PWM includes the following features:
•
•
•
•
•
•
Six independent PWM outputs or three complementary PWM output pairs
Programmable deadband insertion for complementary output pairs
Edge-aligned or center-aligned PWM signal generation
PWM off-state is an option bit programmable
PWM outputs driven to off-state on System Reset
Asynchronous disabling of PWM outputs on system fault; outputs are forced to off-
state
•
•
•
•
•
•
•
Fault inputs generate pulse-by-pulse or hard shutdown
12-bit reload counter with 1, 2, 4 or 8 programmable clock prescaler
High current source and sink on all PWM outputs
PWM pairs used as general purpose inputs when outputs are disabled
ADC synchronized with PWM period
Synchronization for current-sense sample and hold
Narrow pulse suppression with programmable threshold
Architecture
The PWM unit consists of a master timer to generate the modulator time base and six inde-
pendent compare registers to set the PWM for each output. The six outputs are designed to
provide control signals for inverter drive circuits. The outputs are grouped into pairs con-
sisting of a high-side driver and a low-side driver output. The output pairs are programma-
ble to operate independently or as complementary signals.
In complementary output mode, a programmable dead-time is inserted to ensure nonover-
lapping signal transitions. The master count and compare values feed into modulator logic
which generates the proper transitions in the output states. Output polarity and fault/off-
state control logic allows programming of the default off-states which forces the outputs to
a safe state in the event a fault in the motor drive is detected. Figure 21 displays the archi-
tecture of the PWM modulator.
PS022010-0811
P R E L I M I N A R Y
Multi-Channel PWM Timer
ZNEO® Z16F Series MCUs
Product Specification
115
ISense S/H
IRQ
12-bit Counter with
Prescaler
Control Logic
ADC Trig
Fault inputs
PWM Deadband
PWMH0D
PWML0D
Data Bus
PWM
State
Logic
Fault
Polarity
Logic
PWMH0
PWML0
System Clock
PWMH1D
PWML1D
PWM
State
Logic
Fault
Polarity
Logic
PWMH1
PWML1
PWMH2D
PWML2D
PWM
State
Logic
Fault
Polarity
Logic
PWMH2
PWML2
Figure 21. PWM Block Diagram
Operation
PWM Option Bits
To protect the configuration of critical PWM parameters, settings to enable output chan-
nels and the default off-state are maintained as user option bits. These values are set when
the user program code is written to the part; the software cannot change these values. For
more, see the Option Bits chapter on page 292.
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
116
PWM Output Polarity and Off-State
The default off-state and polarity of the PWM outputs are controlled by the option bits
PWMHI and PWMLO. The PWMHI option controls the off-state and polarity for PWM
high-side outputs PWMH0, PWMH1 and PWMH2. The PWMLO option controls the off-
state and polarity for low-side outputs PWML0, PWML1 and PWML2.
The off-state is the value programmed in the option bit. For example, programming PWMHI
to 1 makes the off-state of PWMH0, PWMH1 and PWMH2 a High logic value and the
active state a Low logic value. Conversely, programming PWMHI to 0 causes the off-state
to be a Low logic value. PWMLO is programmed in a similar manner.
PWM Enable
The MCEN option bit enables output pairs PWM0, PWM1 and PWM2. If the Motor Con-
trol option is not enabled, the PWM outputs remain in a high-impedance state after reset
and is used as alternate functions like general purpose input. If the Motor Control option is
enabled, following a Power-On Reset (POR) the PWM pins enter a high impedance state.
As the internal reset proceeds, the PWM outputs are forced to the off-state as determined
by the PWMHI and PWMLO off-state option bits.
PWM Reload Event
To prevent erroneous PWM pulse-widths and periods, registers that control the timing of
the output are buffered. Buffering causes all of the PWM compare values to update. In
other words, the registers controlling the duty cycle and clock source prescaler only take
effect on a PWM reload event. A PWM reload event is configured to occur at the end of
each PWM period or only every 2, 4, or 8 PWM periods by setting the RELFREQ bits in
the PWM Control 1 Register (PWMCTL1). Software indicates that all new values are
ready by setting the READY bit in the PWM Control 0 Register (PWMCTL0) to 1. When
the READY bit is set to 1, the buffered values take effect at the next reload event.
PWM Prescaler
The prescaler decreases the PWM clock signal by factors of 1, 2, 4, or 8 with respect to the
system clock. The PRES[1:0] bit field in the PWM Control 1 Register (PWMCTL1) con-
trols prescaler operation. This 2-bit PRES field is buffered so that the prescale value only
changes on a PWM Reload event.
PWM Period and Count Resolution
The PWM counter operates in two modes to allow edge-aligned and center-aligned out-
puts. Figures 22 and 23 illustrate edge and center-aligned PWM outputs. The mode in
which the PWM operates determine the period of the PWM outputs (PERIOD). The pro-
grammed duty-cycle (PWMDC) and the programmed deadband time (PWMDB) deter-
PS022010-0811
P R E L I M I N A R Y
PWM Reload Event
ZNEO® Z16F Series MCUs
Product Specification
117
mine the active time of a PWM output. The following sections describe the PWM TIMER
modes and the registers controlling the duty-cycle and deadband time.
PWMxH
No Dead Band
PWMLx
PERIOD
PWMHx
Dead Band Insertion
PWMLx
PWMDB
PWMDB
PWMDC
Figure 22. Edge-Aligned PWM Output
PWMHx
No Dead Band
PWMLx
PERIOD
PWMHx
Dead Band Insertion
PWMLx
PWMDB
PWMDB
Figure 23. Center-Aligned PWM Output
PS022010-0811
P R E L I M I N A R Y
PWM Period and Count Resolution
ZNEO® Z16F Series MCUs
Product Specification
118
EDGE-ALIGNED Mode
In EDGE-ALIGNED PWM Mode, a 12-bit up counter creates the PWM period with a
minimum resolution equal to the PWM clock source period. The counter counts up to the
reload value, resets to 000Hand then resumes counting.
Prescaler Reload Value
------------------------------------------------------------
Edge-Aligned PWM Mode Period =
f
PWMclk
CENTER-ALIGNED Mode
In CENTER-ALIGNED PWM Mode, a 12-bit up/down counter creates the PWM period
with a minimum resolution equal to twice the PWM clock source period. The counter
counts up to the reload value and then counts down to 0.
2 Prescaler Reload Value
---------------------------------------------------------------------
Center-Aligned PWM Mode Period =
f
PWMclk
PWM Duty Cycle Registers
The PWM duty cycle registers (PWMH0D, PWML0D, PWMH1D, PWML1D,
PWMH2D, PWML2D) contain a 16-bit signed value where bit 15 is the sign bit. The duty
cycle value is compared to the current 12-bit unsigned PWM count value. If the PWM
duty cycle value is set less than or equal to 0, the PWM output is deasserted for full PWM
period. If the PWM duty cycle value is set to a value greater than the PWM reload value,
the PWM output is asserted for full PWM period.
Independent and Complementary PWM Outputs
The six PWM outputs are configured to operate independently or as three complementary
pairs. Operation as six independent PWM channels are enabled by setting the INDEN bit
in the PWM Control 1 Register (PWMCTL1). In INDEPENDENT Mode, each PWM out-
put uses its own PWM duty cycle value.
When PWM outputs are configured to operate as three complementary pairs, the PWM
duty cycle values PWMH0D, PWMH1D and PWMH2D control the modulator output. In
COMPLEMENTARY OUTPUT Mode deadband time is also inserted.
The POLx bits in the PWM Control 1 Register (PWMCTL1) select the relative polarity of
the high- and low-side signals. As illustrated in Figures 22 and 23, when the POLx bits are
cleared to 0, the PWM high-side output will start in the on-state and transits to the off-state
when the PWM timer count reaches the programmed duty cycle. The low-side PWM
value starts in the off-state and transits to the on-state as the PWM timer count reaches the
value in the associated duty cycle register. Alternately, setting the POLx causes the high-
side output to start in the off-state and the low-side output to start in the on-state.
PS022010-0811
P R E L I M I N A R Y
PWM Duty Cycle Registers
ZNEO® Z16F Series MCUs
Product Specification
119
Manual Off-State Control of PWM Output Channels
Each PWM output is controlled directly by the modulator logic or set to the off-state. To
manually set the PWM output to the off-state, set the OUTCTL bit and the associated
OUTx bits in the PWM Output Control Register (PWMOUT). Off-state control operates
individually by channel. For example, suppressing a single output of pair allows the com-
plementary channel to continue operating. Similarly, if the outputs are operating indepen-
dently disabling one output channel has no effect on the other PWM outputs.
Deadband Insertion
When the PWM outputs are configured to operate as complementary pairs, an 8-bit dead-
band value is defined in the PWM Deadband Register (PWMDB). Inserting deadband
time causes the modulator to separate the deassertion of one PWM signal from the asser-
tion of its complement. This separation is essential for many motor control applications to
prevent simultaneous turn-on of the high-side and low-side drive transistors. The dead-
band counter directly counts system clock cycles and is unaffected by PWM prescaler set-
tings. The width of this deadband is the number of system clock cycles specified in the
PWM Deadband Register (PWMDB).
The minimum deadband duration is zero system clocks; the maximum time is 255 system
clocks. Both PWM outputs of a complementary pair is deasserted during the deadband
period. Generation of deadband time does not alter the PWM period but the deadband time
is subtracted from the active time of the PWM outputs. Figure 22 on page 117 displays the
effect of deadband insertion on the PWM output.
Minimum PWM Pulse Width Filter
The PWM modulator is capable of producing pulses as narrow as a single system clock
cycle in width. The response time of external drive circuit is slower than the period of a
system clock. Therefore, a filter is implemented to enforce a minimum width pulse on the
PWM output pins. All output pulses, either High or Low, must be at least the minimum
number of PWM clock cycles in width, as specified in the PWM Minimum Pulse Width
Filter (PWMMPF) Register (for more details, see the PWM Prescaler section on page
116).
If the expected pulse width is less than the threshold, the associated PWM output does not
change state until the duty cycle value has changed sufficiently to allow pulse generation
of an acceptable width. The minimum pulse width filter also accounts for the duty cycle
variation caused by the deadband insertion. The PWM output pulse is filtered even if the
programmed duty cycle is greater than the threshold but the decrease in pulse width
because of deadband insertion causes the pulse to be too narrow. The pulse width filter
value is calculated as:
PS022010-0811
P R E L I M I N A R Y Manual Off-State Control of PWM Output
ZNEO® Z16F Series MCUs
Product Specification
120
roundupPWMMPF = T
T
PWMprescaler
minPulseOut
systemClock
where minPulseOut is the shortest allowed pulse width on the PWM outputs (in seconds).
Synchronization of PWM and ADC
The ADC on the ZNeo is synchronized with the PWM period. Enabling the PWM ADC
trigger causes the PWM to generate an ADC conversion signal at the end of each PWM
period. Additionally, in CENTER-ALIGNED Mode, the PWM generates a trigger at the
center of the period. Setting the ADCTRIG bit in the PWM Control 0 Register
(PWMCTL0) enables the ADC synchronization.
Synchronized Current-Sense Sample and Hold
The PWM controls the current-sense input sample and hold amplifier. The signal control-
ling the sample/hold is configured to always sample or automatically hold when any or all
of the PWM High or Low outputs are in the on state. The current-sense sample and hold is
controlled by the Current-Sense Sample and Hold Control Register (CSSHR0 and
CSSHR1).
PWM Timer and Fault Interrupts
The PWM generates interrupts to the ZNEO CPU during any of the following events:
•
PWM Reload, in which the interrupt is generated at the end of a PWM period when a
PWM register reload occurs
•
PWM Fault, in which a fault condition is indicated by asserting any FAULT pins or by
the assertion of the comparator
Fault Detection and Protection
The ZNEO contains hardware and software fault controls, which allow rapid deassertion
of all enabled PWM output signals. A logic Low on an external fault pin (FAULT0 or
FAULT1) or the assertion of the over current comparator forces the PWM outputs to the
predefined off-state.
Similar deassertion of the PWM outputs is accomplished in software by writing to the
PWMOFF bit in the PWM Control 0 Register. The PWM counter continues to operate
while the outputs are deasserted (inactive) due to one of these fault conditions.
The fault inputs are individually enabled through the PWM Fault Control Register. If a
fault condition is detected and the source is enabled, the fault interrupt is generated. The
PS022010-0811
P R E L I M I N A R Y
Synchronization of PWM and ADC
ZNEO® Z16F Series MCUs
Product Specification
121
PWM Fault Status Register (PWMFSTAT) is read to determine which fault source caused
the interrupt.
When a fault is detected and the PWM outputs are disabled, modulator control of the
PWM outputs are reenabled either by the software or by the fault input signal deasserting.
Selection of the reenable method is made using the PWM Fault Control Register (PWM-
FCTL). Configuration of the fault modes and reenable methods allow pulse-by-pulse lim-
iting and hard shutdown. When configured in AUTOMATIC RESTART Mode, the PWM
outputs are reengaged at beginning of the next PWM cycle (master timer value is equal to
0) if all fault signals are deasserted. In software controlled restart, all fault inputs must be
deasserted and the fault flags must be cleared.
The fault input pin is Schmitt-triggered. The input signal from the pin as well as the com-
parators pass though an analog filter to reject high-frequency noise.
The logic path from the fault sources to the PWM output is asynchronous ensuring that the
fault inputs forces the PWM outputs to their off-state even if the system clock is stopped.
PWM Operation in CPU HALT Mode
When the ZNEO CPU is operating in HALT Mode, the PWM continues to operate if it is
enabled. To minimize current in HALT Mode, the PWM must be disabled by clearing the
PWMEN bit to 0.
PWM Operation in CPU STOP Mode
When the ZNEO CPU is operating in STOP Mode, the PWM is disabled as the system
clock ceases to operate in STOP Mode. The PWM output remains in the same state as they
were prior to entering the STOP Mode. In normal operation, the PWM outputs must be
disabled by software prior to the CPU entering the STOP Mode. A fault condition detected
in STOP Mode forces the PWM outputs to the predefined off-state.
Observing the State of PWM Output Channels
The logic value of the PWM outputs is sampled by reading the PWMIN Register. If a
PWM channel pair is disabled (option bit is not set), the associated PWM outputs are
forced to high impedance and are used as general purpose inputs.
PWM Control Register Definitions
The following sections describe the various PWM control registers.
PS022010-0811
P R E L I M I N A R Y
PWM Operation in CPU HALT Mode
ZNEO® Z16F Series MCUs
Product Specification
122
PWM High and Low Byte Registers
The PWM High and Low Byte (PWMH and PWML) registers, shown in Table 64 and
Table 65) contain the current 12-bit PWM count value. Reads from PWMH stores the
value in PWML to a temporary holding register. A read from PWML always returns this
temporary register value. It is not recommended to write to the PWM High and Low Byte
registers when the PWM is enabled. There are no temporary holding registers for write
operations, so simultaneous 12-bit writes are not possible. When either the PWM High
and Low Byte registers are written during counting, the 8-bit written value is placed in the
counter (High or Low Byte) at the next clock edge. The counter continues counting from
the new value.
Table 64. PWM High Byte Register (PWMH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
0H
PWMH
0H
R/W
R/W
Addr
FF_E38CH
Bit
Description
Reserved
[7:4]
These bits are reserved and must be programmed to 0000.
[3:0]
PWMH
PWM High and Low Bytes
The upper byte of two bytes {PWMH[3:0], PWML[7:0]} that contain the current 12-bit PWM
count value.
Table 65. PWM Low Byte Register (PWML)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PWML
01H
R/W
Addr
FF_E38DH
Bit
Description
[7:0]
PWML
PWM High and Low Bytes
The lower byte of two bytes {PWMH[3:0], PWML[7:0]} that contain the current 12-bit PWM
count value.
PS022010-0811
P R E L I M I N A R Y
PWM High and Low Byte Registers
ZNEO® Z16F Series MCUs
Product Specification
123
PWM Reload High and Low Byte Registers
The PWM Reload High and Low Byte (PWMRH and PWMRL) registers, shown in
Tables 66 and 67, store a 12-bit reload value, {PWMRH[3:0], PWMRL[7:0]}. The PWM
reload value is held in buffer registers. The PWM reload value written to the buffer regis-
ters are not used by the PWM generator until the next PWM reload event occurs. Reads
from these registers always return the values from the buffer registers.
Prescaler Reload Value
------------------------------------------------------------
Edge-Aligned PWM Mode Period =
f
PWMclk
2 Prescaler Reload Value
---------------------------------------------------------------------
Center-Aligned PWM Mode Period =
f
PWMclk
Table 66. PWM Reload High Byte Register (PWMRH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
0H
PWMRH
FH
R/W
R/W
Addr
FF_E38EH
Bit
Description
Reserved
[7:4]
These bits are reserved and must be programmed to 0000.
[3:0]
PWM Reload Register High and Low
PWMRH These two bytes form the 12-bit reload value, {PWMRH[3:0], PWMRL[7:0]}. This value sets the
PWM period.
Table 67. PWM Reload Low Byte Register (PWMRL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PWMRL
FF
R/W
Addr
FF_E38FH
Bit
Description
[7:0]
PWM Reload Register High and Low
PWMRL These two bytes form the 12-bit reload value, {PWMRH[3:0], PWMRL[7:0]}. This value sets the
PWM period.
PS022010-0811
P R E L I M I N A R Y PWM Reload High and Low Byte Registers
ZNEO® Z16F Series MCUs
Product Specification
124
PWM 0–2 Duty Cycle High and Low Byte Registers
The PWM 0–2 H/L (High Side/Low Side) Duty Cycle High and Low Byte (PWMxDH
and PWMxDL) registers, shown in Tables 68 and 69, set the duty cycle of the PWM sig-
nal. This 14-bit signed value is compared to the PWM count value to determine the PWM
output. Reads from these registers always return the values from the temporary holding
registers. The PWM generator does not use the PWM duty cycle value until the next PWM
reload event occurs.
PWM Duty Cycle Value
PWM Reload Value
----------------------------------------------------------
PWM Duty Cycle = 100
Writing a negative value (DUTYH[7] = 1) forces the PWM to be OFF for the full PWM
period. Writing a positive value greater than the 12-bit PWM reload value forces the PWM
to be ON for the full PWM period.
Table 68. PWM 0–2 H/L Duty Cycle High Byte Register (PWMHxDH, PWMLxDH)
Bits
7
SIGN
X
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
XX
DUTYH
X_XXXX
R/W
R/W
R/W
Addr
FF_E390H, FF_E392H, FF_E394H, FF_E396H, FF_E398H, FF_E39AH
Bit
Description
[7]
SIGN
Duty Cycle Sign
0 = Duty cycle is a positive two’s complement number.
1 = Duty cycle is a negative two’s complement number. Output is forced to the off-state.
[6:5]
Reserved
These bits are reserved and must be programmed to 00.
[4:0]
DUTYH
PWM Duty Cycle High and Low Bytes
The upper byte of two bytes {DUTYH[7:0], DUTYL[7:0]} that form a 14-bit signed value; bits
5 and 6 of the High byte are always 0. The value is compared to the current 12-bit PWM
count.
PS022010-0811
P R E L I M I N A R Y PWM 0–2 Duty Cycle High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
125
Table 69. PWM 0–2 H/L Duty Cycle Low Byte Register (PWMHxDL, PWMLxDL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DUTYL
XXH
R/W
Addr
FF_E391H, FF_E393H, FF_E395H, FF_E397H, FF_E399H, FF_E39BH
Bit
Description
[7:0]
DUTYL
PWM Duty Cycle High and Low Bytes
The lower byte of two bytes {DUTYH[7:0], DUTYL[7:0]} that form a 14-bit signed value; bits
5 and 6 of the High byte are always 0. The value is compared to the current 12-bit PWM
count.
PWM Control 0 Register
The PWM Control 0 Register (PWMCTL0) controls PWM operation.
Table 70. PWM Control 0 Register (PWMCTL0)
Bits
7
6
5
ALIGN
0
4
3
2
1
0
PWMEN
0
Field
RESET
R/W
PWMOFF OUTCTL
Reserved ADCTRIG Reserved READY
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E380H
Bit
Description
[7]
PWMOFF
Place PWM Outputs in Off State
0 = Disable modulator control of PWM pins. Outputs are in predefined off state; not depen-
dent on the Reload event.
1 = Reenable modulator control of PWM pins at next PWM Reload event.
[6]
OUTCTL
PWM Output Control
0 = PWM outputs are controlled by the pulse-width modulator.
1 = PWM outputs selectively disabled (set to off-state) according to values in the OUTx bits
of the PWMOUT Register.
[5]
ALIGN
PWM Edge Alignment
0 = PWM outputs are edge aligned.
1 = PWM outputs are center aligned.
[4]
Reserved
This bit is reserved and must be programmed to 0.
PS022010-0811
P R E L I M I N A R Y
PWM Control 0 Register
ZNEO® Z16F Series MCUs
Product Specification
126
Bit
Description (Continued)
[3]
ADCTRIG
ADC Trigger Enable
0 = No ADC trigger pulses.
1 = ADC trigger enabled.
[2]
Reserved
This bit is reserved and must be programmed to 0.
[1]
READY
Values Ready for Next Reload Event
0 = PWM values (prescale, period and duty cycle) are not ready. Do not use values in hold-
ing registers at next PWM reload event.
1 = PWM values (prescale, period and duty cycle) are ready. Transfer all values from tempo-
rary holding registers to working registers at next PWM reload event.
[0]
PWMEN
PWM Enable
0 = PWM is disabled and enabled PWM output pins are forced to default off-state. PWM
master counter is stopped. Certain control registers may only be written in this state.
1 = PWM is enabled and PWM output pins are enabled as outputs.
PWM Control 1 Register
The PWM Control 1 (PWMCTL1) Register controls portions of PWM operation.
Table 71. PWM Control 1 Register (PWMCTL1)
Bits
7
6
5
INDEN
0
4
POL45
0
3
POL23
0
2
POL10
0
1
0
Field
RESET
R/W
RLFREQ[1:0]
PRES[1:0]
00
00
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E381H
Bit
Description
[7:6]
Reload Event Frequency
RLFREQ[1:0] This bit field is buffered. Changes to the reload event frequency takes effect at the end of
the current PWM period. Reads always return the bit values from the temporary holding
register.
00 = PWM reload event occurs at the end of every PWM period.
01 = PWM reload event occurs once every two PWM periods.
10 = PWM reload event occurs once every four PWM periods.
11 = PWM reload event occurs once every eight PWM periods.
[5]
INDEN
Independent PWM Mode Enable
0 = PWM outputs operate as three complementary pairs.
1 = PWM outputs operate as six independent channels.
PS022010-0811
P R E L I M I N A R Y
PWM Control 1 Register
ZNEO® Z16F Series MCUs
Product Specification
127
Bit
Description (Continued)
[4]
POL2
PWM2 Polarity
0 = Noninverted polarity for channel pair PWM2.
1 = Invert output polarity for channel pair PWM2.
[3]
POL1
PWM1 Polarity
0 = Noninverted polarity for channel pair PWM1.
1 = Invert output polarity for channel pair PWM1.
[2]
POL0
PWM0 Polarity
0 = Noninverted polarity for channel pair PWM0.
1 = Invert output polarity for channel pair PWM0.
[1:0]
PRES
PWM Prescaler
The prescaler divides down the PWM input clock (either the system clock or the PWMIN
external input). This field is buffered. Changes to this field take effect at the next PWM
reload event. Reads always return the values from the temporary holding register.
00 = Divide by 1.
01 = Divide by 2.
10 = Divide by 4.
11 = Divide by 8.
PWM Deadband Register
The PWM Deadband (PWMDB) Register, shown in Table 72, stores the 8-bit PWM dead-
band value. The deadband value determines the number of PWM input cycles to use for
the deadband time for complementary PWM output pairs. When counting PWM input
cycles, the PWM input signal is used directly (no prescaler). The minimum deadband
value is 1. Maximum deadband time is programmed by setting a value of 00h.
Table 72. PWM Deadband Register (PWMDB)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PWMDB[7:0]
01H
R/W
Addr
FF_E382H
Bit
Description
[7:0]
PWM Deadband
PWMDB[7:0] Sets the PWM deadband period for which both PWM outputs
of a complementary PWM output pair are deasserted.
Note: This register can only be written when PWMEN is cleared.
PS022010-0811
P R E L I M I N A R Y
PWM Deadband Register
ZNEO® Z16F Series MCUs
Product Specification
128
PWM Minimum Pulse Width Filter
The value in the PWMMPF Register, shown in Table 73, determines the minimum width
pulse, either High or Low, generated by the PWM module. The minimum pulse width
period is calculated as:
PWMDB + PWMMPF
------------------------------------------------------------------------------
=
T
minPulseOut
T
PwmPrescale
systemClock
Table 73. PWM Minimum Pulse Width Filter (PWMMPF)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
PWMMPF[7:0]
00H
R/W
Addr
FF_E383H
Bit
Description
[7:0]
Minimum Pulse Filter
PWMDB[7:0] Sets the minimum allowed output pulse width in PWM clock cycles.
Note: This register can only be written when PWMEN is cleared.
PWM Fault Mask Register
The PWM Fault Mask Register, shown in Table 74, enables individual fault sources.
When an input is asserted, PWM behavior is determined by the PWM Fault Control Reg-
ister (PWMFCTL). The Comparator 0–3 outputs generate PWM faults and the associated
fault system exception. The bits in this register can only be set; all other writes are
ignored.
PS022010-0811
P R E L I M I N A R Y
PWM Minimum Pulse Width Filter
ZNEO® Z16F Series MCUs
Product Specification
129
Table 74. PWM Fault Mask Register (PWMFM)
Bits
7
6
5
DBGMSK
0
4
3
2
1
0
Field
RESET
R/W
Reserved
Reserved
F1MASK C0MASK FMASK
00
R
000
R
0
0
0
R/W
R/W
R/W
R/W
Addr
FF_E384H
Bit
Description
Reserved
[7:6]
These bits are reserved and must be programmed to 00.
[5]
Debug Entry Fault Mask
DBGMSK
0 = Entering CPU DEBUG Mode generates a PWM Fault.
1 = Entering CPU DEBUG Mode does not generate a PWM Fault.
[4:3]
Reserved
These bits are reserved and must be programmed to 00.
[2]
F1MASK
Fault 1 Fault Mask
0 = Fault 1 generates a PWM Fault.
1 = Fault 1 does not generate a PWM Fault.
[1]
C0MASK
Comparator Fault Mask
0 = Comparator generates a PWM Fault.
1 = Comparator does not generate a PWM Fault.
[0]
F0MASK
Fault Pin Mask
0 = Fault 0 pin generates a PWM Fault.
1 = Fault 0 pin does not generate a PWM Fault.
Note: This register can only be written when PWMEN is cleared.
PS022010-0811
P R E L I M I N A R Y
PWM Fault Mask Register
ZNEO® Z16F Series MCUs
Product Specification
130
PWM Fault Status Register
The PWM Fault Status (PWMFSTAT) Register, shown in Table 75, provides the status of
fault inputs and timer reloads. The fault flags indicate the fault source, which is active. If a
fault source is masked, the flag in this register is not set when the source is asserted. The
reload flag is set when the timer compare values are updated. Clear flags by writing a 1 to
the flag bits. Fault flag bits are cleared only if the associated fault source has deasserted.
Table 75. PWM Fault Status Register (PWMFSTAT)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RLDFlag Reserved DBGFLAG
Reserved
F1FLAG C0FLAG
FFLAG
U
U
0
U
00
R
U
U
R/W1C*
R
R/W1C*
R/W1C*
R/W1C*
R/W1C*
Addr
FF_E385H
Bit
Description
Reload Flag
[7]
RLDFlag
This bit is set and latched when a PWM timer reload occurs. Writing a 1 to this bit clears the
flag.
[6]
Reserved
This bit is reserved and must be programmed to 0.
[5]
Debug Flag
DBGFLAG This bit is set and latched when DEBUG Mode is entered. Writing a 1 to this bit clears the
flag.
[4:3]
Reserved
Reserved
These bits are reserved and must be programmed to 00.
[2]
F1FLAG
Fault 1 Flag
This bit is set and latched when fault1 is asserted. Writing a 1 to this bit clears the flag.
[1]
C0FLAG
Comparator 0 Flag
This bit is set and latched when comparator is asserted. Writing a 1 to this bit clears the flag.
[0]
FFLAG
Fault Flag
This bit is set and latched when the fault0 input is asserted. Writing a 1 to this bit clears the
flag.
Note: *For this register, W1C means you must write a 1 to clear the flag.
PS022010-0811
P R E L I M I N A R Y
PWM Fault Status Register
ZNEO® Z16F Series MCUs
Product Specification
131
PWM Fault Control Register
The PWM Fault Control (PWMFCTL) Register, shown in Table 76, determines how the
PWM recovers from a fault condition. Settings in this register select either an automatic or
a software-controlled PWM restart.
Table 76. PWM Fault Control Register (PWMFCTL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved DBGRST CMP1INT CMP1RST CMPINT CMPRST Fault0INT Fault0RST
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E388H
Bit
Description
Reserved
[7]
This bit is reserved and must be programmed to 0.
[6]
Debug Restart
DBGRST
0 = Automatic recovery. PWM resumes control of outputs when all fault sources have deas-
stered and a new PWM period begins.
1 = Software controlled recovery. PWM resumes control of outputs only after all fault
sources have deasserted and all fault flags are cleared and a PWM reload occurs.
[5]
Comparator 1 Interrupt
CMP1INT
0 = Interrupt on comparator assertion disabled.
1 = Interrupt on comparator assertion enabled.
[4]
Comparator 1 Restart
CMP1RST 0 = Automatic recovery. PWM resumes control of outputs when all fault sources have deas-
stered.
Software Controlled Recovery
1 = PWM resumes control of outputs only after all fault sources have deasserted and all fault
flags are cleared and a PWM reload occurs.
[3
Comparator 0 Interrupt
CMP0INT
0 = Interrupt on comparator 0 assertion disabled.
1 = Interrupt on comparator 0 assertion enabled.
[2]
Comparator 0 Restart
CMP0RST 0 = Automatic recovery. PWM resumes control of outputs when all fault sources have deas-
stered.
Software Controlled Recovery
1 = PWM resumes control of outputs only after all fault sources have deasserted and all fault
flags are cleared and a PWM reload occurs.
Note: This register can only be written when PWMEN is cleared.
PS022010-0811
P R E L I M I N A R Y
PWM Fault Control Register
ZNEO® Z16F Series MCUs
Product Specification
132
Bit
Description (Continued)
[1]
Fault 0 Interrupt
Fault0INT
0 = Interrupt on fault 0 pin assertion disabled.
1 = Interrupt on Fault0 pin assertion enabled.
[0]
Fault 0 Restart
Fault0RST 0 = Automatic recovery. PWM resumes control of outputs when all fault sources have deas-
stered.
Software Controlled Recovery
1 = PWM resumes control of outputs only after all fault sources have deasserted and all fault
flags are cleared and a PWM reload occurs.
Note: This register can only be written when PWMEN is cleared.
PWM Input Sample Register
The PWM pin value is sampled by reading the PWM Input Sample Register, shown in
Table 77.
Table 77. PWM Input Sample Register (PWMIN)
Bits
7
6
FAULT
0
5
4
IN2H
0
3
2
IN1H
0
1
0
IN0H
0
Field
RESET
R/W
Reserved
IN2L
0
IN1L
0
IN0L
0
0
R
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E386H
Bit
Description
Reserved
[7]
This bit is reserved and must be programmed to 0.
[6]
FAULT
Sample Fault0 pin
0 = A Low-level signal was read on the fault pin.
1 = A High-level signal was read on the fault pin.
[5:0]
Sample PWM Pins
IN2L/IN2H/ 0 = A Low-level signal was read on the pins.
IN1L/IN1H/ 1 = A High-level signal was read on the pins.
IN0L/IN0H
PS022010-0811
P R E L I M I N A R Y
PWM Input Sample Register
ZNEO® Z16F Series MCUs
Product Specification
133
PWM Output Control Register
The PWM Output Control (PWMOUT) Register, shown in Table 78, enables modulator
control of the six PWM output signals. Output control is enabled by the OUTCTL bit in
the PWMCTL0 Register. The PWM continues to operate but has no effect on the disabled
PWM pins. If a fault condition is detected, all PWM outputs are forced to their selected off
states.
Table 78. PWM Output Control Register (PWMOUT)
Bits
7
6
5
OUT2L
0
4
OUT2H
0
3
OUT1L
0
2
OUT1H
0
1
OUT0L
0
0
OUT0H
0
Field
RESET
R/W
Reserved Reserved
0
0
R
R
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E387H
Bit
Description
Reserved
[7,6]
These bits are reserved and must be programmed to 00.
[5,3,1]
PWM 2L/1L/0L Output Configuration
0 = PWM 2L/1L/0L output signal is enabled and controlled by PWM.
1 = PWM 2L/1L/0L output signal is in low-side off-state.
OUT2L/
OUT1L/
OUT0L
[4,2,0]
PWM 2H/1H/0H Output Configuration
0 = PWM 2H/1H/0H output signal is enabled and controlled by PWM.
1 = PWM 2H/1H/0H output signal is in high-side off-state.
OUT2H/
OUT1H/
OUT0H
PS022010-0811
P R E L I M I N A R Y
PWM Output Control Register
ZNEO® Z16F Series MCUs
Product Specification
134
Current-Sense Sample and Hold Control Registers
The Current-Sense Sample/Hold Control Register, shown in Table 79, defines the behav-
ior of the dedicated current sense sample and hold inputs to the ADC from the operational
amplifier. These input hold the current input value whenever all high-side outputs or all
low-side outputs are in the on-state. The register bits control which PWM outputs must be
asserted to activate the internal hold signal. Disabling the HEN, LEN, NHEN and NLEN
bits allows software control of the input sample/hold by writing the SHPOL bit.
Table 79. Current-Sense Sample and Hold Control Register (CSSHR0 and CSSHR1)
Bits
7
SHPOL
0
6
5
NHEN
0
4
3
NLEN
0
2
1
0
Field
RESET
R/W
HEN
0
LEN
0
SHPWM2 SHPWM1 SHPWM0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E38AH and FF_E38BH
Bit
Description
[7]
SHPOL
Sample Hold Polarity
0 = Hold when terms are active.
1 = Hold when terms are not active.
[6]
HEN
High Side Active Enable
0 = Ignore Product of PWMH0, PWMH1, PWMH2 in sample/hold equation.
1 = Hold when PWMH0, PWMH1, PWMH2 are all active.
[5]
NHEN
High Side Inactive Enable
0 = Ignore product of PWMH0, PWMH1, PWMH2 in sample/hold equation.
1 = Hold when are all active.
[4]
LEN
Low Side Active Enable
0 = Ignore product of PWML0, PWML1, PWML2 in sample/hold equation.
1 = Hold when PWML0, PWML1, PWML2 are all active.
[3]
NLEN
Low Side Inactive Enable
0 = Ignore product of PWML0, PWML1, PWML2 in sample/hold equation.
1 = Hold when PWML0, PWML1, PWML2 are all active.
[2]
SHPWM2
PWM channel2 Sample/Hold Enable
0 = Channel 2 terms are not used in sample/hold equation.
1 = Channel 2 terms are used in sample/hold equation.
[1]
SHPWM1
PWM Channel1 Sample/Hold Equation
0 = Channel 1 terms are not used in sample/hold equation.
1 = Channel 1 terms are used in sample/hold equation.
[0]
SHPWM0
PWM Channel0 Sample/Hold Equation
0 = Channel 0 terms are not used in sample/hold equation.
1 = Channel 0 terms are used in sample/hold equation.
PS022010-0811
P R E L I M I N A R Y Current-Sense Sample and Hold Control
ZNEO® Z16F Series MCUs
Product Specification
135
LIN-UART
The Local Interconnect Network Universal Asynchronous Receiver/Transmitter (LIN-
UART) is a full-duplex communication channel capable of handling asynchronous data
transfers in standard UART applications as well as providing LIN protocol support.
Features of the LIN-UART include:
•
•
•
•
8-bit asynchronous data transfer
Selectable even and odd-parity generation and checking
Option of one or two stop bits
Selectable MULTIPROCESSOR (9-Bit) Mode with three configurable interrupt
schemes
•
•
•
Separate transmit and receive interrupts or DMA requests
Framing, parity, overrun and break detection
16-bit Baud Rate Generator (BRG), which functions as a general-purpose timer with
interrupt
•
•
Driver enable output for external bus transceivers
LIN protocol support for both MASTER and SLAVE modes:
–
–
–
Break generation and detection
Selectable slave autobaud
Check Tx versus Rx data when sending
•
Configurable digital noise filter on receive data line
Architecture
The LIN-UART consists of three primary functional blocks: transmitter, receiver and
BRG. The LIN-UART’s transmitter and receiver function independently but use the same
baud rate and data format. The basic UART operation is enhanced by the noise filter and
IrDA blocks. Figure 24 displays the LIN-UART architecture.
PS022010-0811
P R E L I M I N A R Y
LIN-UART
ZNEO® Z16F Series MCUs
Product Specification
136
Parity Checker
Receive Shifter
Rx IRQ
RxDmaReq
Receiver Control
with Address Compare
RxD
Receive Data
Register
Control Registers
System Bus
Transmit Data
Status Registers
Baud Rate
Generator
Register
Transmit Shift
Register
TxD
Transmitter Control
Tx IRQ
TxDmaReq
Parity Generator
CTS
DE
Figure 24. LIN-UART Block Diagram
Operation
Data Format for Standard UART Modes
The LIN-UART always transmits and receives data in an 8-bit data format, with the first
bit being the least-significant bit. An even- or odd-parity bit or multiprocessor address/
data bit is optionally added to the data stream. Each character begins with an active Low
start bit and ends with either 1 or 2 active High stop bits. Figures 25 and 26 display the
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
137
asynchronous data format employed by the LIN-UART, without parity and with parity,
respectively.
Data Field
Stop Bit(s)
Idle State
of Line
lsb
msb
Bit7
1
0
Start
Bit0
Bit1
Bit2
Bit3
Bit4
Bit5
Bit6
1
2
Figure 25. LIN-UART Asynchronous Data Format without Parity
Data Field
Stop Bit(s)
Idle State
of Line
lsb
msb
1
0
Start
Bit0
Bit1
Bit2
Bit3
Bit4
Bit5
Bit6
Bit7 Parity
1
2
Figure 26. LIN-UART Asynchronous Data Format with Parity
Transmitting Data using the Polled Method
Observe the following steps to transmit data using the polled operating method:
1. Write to the LIN-UART Baud Rate High and Low Byte registers to set the appropriate
baud rate.
2. Enable the LIN-UART pin functions by configuring the associated GPIO port pins for
alternate function operation.
3. If MULTIPROCESSOR Mode is required, write to the LIN-UART Control 1 Register
to enable MULTIPROCESSOR (9-Bit) Mode functions by setting the MULTIPRO-
CESSOR Mode select bit (MPEN) to enable MULTIPROCESSOR Mode.
4. Write to the LIN-UART Control 0 Register to:
a. Set the transmit enable bit (TEN) to enable the LIN-UART for data transmission.
PS022010-0811
P R E L I M I N A R Y Transmitting Data using the Polled Method
ZNEO® Z16F Series MCUs
Product Specification
138
b. If parity is required and MULTIPROCESSOR Mode is not enabled, set the parity
enable bit (PEN) and select either even- or odd parity (PSEL).
c. Set or clear the CTSEbit to enable or disable control from the remote receiver
using the CTS pin.
5. Check the TDREbit in the LIN-UART Status 0 Register to determine if the Transmit
Data Register is empty (indicated by a 1). If this register is empty, continue to Step 6.
If the Transmit Data Register is full (indicated by a 0), continue to monitor the TDRE
bit until the Transmit Data Register becomes available to receive new data.
6. If in MULTIPROCESSOR Mode, write the LIN-UART Control 1 Register to select
the outgoing address bit by setting the multiprocessor bit transmitter (MPBT) if sending
an address byte; clear it if sending a data byte.
7. Write the data byte to the LIN-UART Transmit Data Register. The transmitter auto-
matically transfers the data to the transmit shift register and transmits the data.
8. If MULTIPROCESSOR Mode is required and MULTIPROCESSOR Mode is
enabled, make any changes to the multiprocessor bit transmitter (MPBT) value.
9. To transmit additional bytes, return to Step 4.
Transmitting Data Using Interrupt-Driven Method
The LIN-UART transmitter interrupt indicates the availability of the Transmit Data Regis-
ter to accept new data for transmission. Observe the following steps to configure the LIN-
UART for interrupt-driven data transmission:
1. Write to the LIN-UART Baud Rate High and Low Byte registers to set the appropriate
baud rate.
2. Enable the LIN-UART pin functions by configuring the associated GPIO port pins for
alternate function operation.
3. Execute a DIinstruction to disable interrupts.
4. Write to the interrupt control registers to enable the LIN-UART transmitter interrupt
and set the appropriate priority.
5. If MULTIPROCESSOR Mode is required, write to the LIN-UART Control 1 Register
to enable MULTIPROCESSOR (9-Bit) Mode functions by setting the MULTIPRO-
CESSOR Mode select bit (MPEN) to enable MULTIPROCESSOR Mode.
6. Write to the LIN-UART Control 0 Register to:
a. Set the transmit enable bit (TEN) to enable the LIN-UART for data transmission
b. Enable parity, if MULTIPROCESSOR Mode is not enabled and select either even
or odd parity.
PS022010-0811
P R E L I M I N A R Y Transmitting Data Using Interrupt-Driven
ZNEO® Z16F Series MCUs
Product Specification
139
c. Set or clear the CTSE bit to enable or disable control from the remote receiver
through the CTS pin.
7. Execute an EIinstruction to enable interrupts.
The LIN-UART is now configured for interrupt-driven data transmission. As the LIN-
UART Transmit Data Register is empty, an interrupt is generated immediately. When the
LIN-UART transmit interrupt is detected and there is transmit data ready to send, the asso-
ciated interrupt service routine (ISR) performs the following operations:
1. If operating in MULTIPROCESSOR Mode, write the LIN-UART Control 1 Register
to select the outgoing address bit by setting the multiprocessor bit transmitter (MPBT)
if sending an address byte; clear it if sending a data byte.
2. Write the data byte to the LIN-UART Transmit Data Register. The transmitter auto-
matically transfers the data to the transmit shift register and transmits the data.
3. Execute the IRETinstruction to return from the interrupt service routine and waits for
the Transmit Data Register to again become empty.
If a transmit interrupt occurs and there is no transmit data ready to send, the interrupt ser-
vice routine executes the IRETinstruction. When the application contains data to transmit,
software sets the appropriate interrupt request bit in the interrupt controller to initiate a
new transmit interrupt. Another alternative would be for software to write the data to the
Transmit Data Register instead of invoking the ISR.
Receiving Data Using the Polled Method
Observe the following steps to configure the LIN-UART for polled data reception:
1. Write to the LIN-UART Baud Rate High and Low Byte registers to set the appropriate
baud rate.
2. Enable the LIN-UART pin functions by configuring the associated GPIO port pins for
alternate function operation.
3. Write to the LIN-UART Control 1 Register to enable MULTIPROCESSOR Mode
functions.
4. Write to the LIN-UART Control 0 Register to:
a. Set the receive enable bit (REN) to enable the LIN-UART for data reception.
b. Enable parity, if MULTIPROCESSOR Mode is not enabled and select either even
or odd parity.
5. Check the RDAbit in the LIN-UART Status 0 Register to determine if the Receive
Data Register contains a valid data byte (indicated by a 1). If RDA is set to 1 to indi-
PS022010-0811
P R E L I M I N A R Y Receiving Data Using the Polled Method
ZNEO® Z16F Series MCUs
Product Specification
140
cate available data, continue to Step 6. If the Receive Data Register is empty (indi-
cated by a 0), continue to monitor the RDAbit awaiting reception of the valid data.
6. Read data from the LIN-UART Receive Data Register. If operating in MULTIPRO-
CESSOR (9-Bit) Mode, further actions are required depending on the MULTIPRO-
CESSOR Mode bits MPMD[1:0].
7. Return to Step 5 to receive additional data.
Receiving Data Using the Interrupt-Driven Method
The LIN-UART receiver interrupt indicates the availability of new data (as well as error
conditions). Observe the following steps to configure the LIN-UART receiver for inter-
rupt-driven operation:
1. Write to the LIN-UART Baud Rate High and Low Byte registers to set the appropriate
baud rate.
2. Enable the LIN-UART pin functions by configuring the associated GPIO port pins for
alternate function operation.
3. Execute a DIinstruction to disable interrupts.
4. Write to the interrupt control registers to enable the LIN-UART receiver interrupt and
set the appropriate priority.
5. Clear the LIN-UART receiver interrupt in the applicable interrupt request register.
6. Write to the LIN-UART Control 1 Register to enable MULTIPROCESSOR (9-Bit)
Mode functions:
a. Set the MULTIPROCESSOR Mode select (MPEN) to enable MULTIPROCES-
SOR Mode.
b. Set the MULTIPROCESSOR Mode bits, MPMD[1:0],to select the appropriate
address matching scheme.
c. Configure the LIN-UART to interrupt on received data and errors or errors only
(interrupt on errors only is unlikely to be useful for ZNEO devices without a
DMA block).
7. Write the device address to the Address Compare Register (automatic multiprocessor
modes only).
8. Write to the LIN-UART Control 0 Register to:
a. Set the receive enable bit (REN) to enable the LIN-UART for data reception
b. Enable parity, if MULTIPROCESSOR Mode is not enabled and select either
even- or odd-parity.
9. Execute an EIinstruction to enable interrupts.
PS022010-0811
P R E L I M I N A R Y Receiving Data Using the Interrupt-Driven
ZNEO® Z16F Series MCUs
Product Specification
141
The LIN-UART is now configured for interrupt-driven data reception. When the LIN-
UART receiver interrupt is detected, the associated ISR performs the following opera-
tions:
1. Check the LIN-UART Status 0 Register to determine whether the source of the inter-
rupt is error, break, or received data.
2. If the interrupt was due to data available, read the data from the LIN-UART Receive
Data Register. If operating in MULTIPROCESSOR (9-Bit) Mode, further actions are
required depending on the MULTIPROCESSOR Mode bits MPMD[1:0].
3. Execute the IRETinstruction to return from the ISR and await more data.
Clear To Send Operation
The clear to send (CTS) pin, if enabled by the CTSEbit of the LIN-UART Control 0 Reg-
ister, performs flow control on the outgoing transmit data stream. The CTS input pin is
sampled one system clock before beginning any new character transmission. To delay
transmission of the next data character, an external receiver must deassert CTS at least one
system clock cycle before a new data transmission begins. For multiple character trans-
missions, this operation is typically performed during the Stop bit transmission. If CTS
deasserts in the middle of a character transmission, the current character is sent com-
pletely.
External Driver Enable
The LIN-UART provides a Driver Enable (DE) signal for off-chip bus transceivers. This
feature reduces the software overhead associated with using a GPIO pin to control the
transceiver when communicating on a multi-transceiver bus such as RS-485.
Driver Enable is a programmable polarity signal which envelopes the entire transmitted
data frame including parity and stop bits as illustrated in Figure 27. The DE signal asserts
when a byte is written to the LIN-UART Transmit Data Register. The DE signal asserts at
least one bit period and no greater than two bit periods before the Start bit is transmitted.
This allows a set-up time to enable the transceiver. The DE signal deasserts one system
clock period after the last Stopbit is transmitted. This one system clock delay allows both
time for data to clear the transceiver before disabling it, as well as the ability to determine
if another character follows the current character. In the event of back to back characters
(new data must be written to the Transmit Data Register before the previous character is
completely transmitted) the DE signal is not deasserted between characters. The DEPOL
bit in the LIN-UART Control Register 1 sets the polarity of the DE signal.
PS022010-0811
P R E L I M I N A R Y
Clear To Send Operation
ZNEO® Z16F Series MCUs
Product Specification
142
1
DE
0
Data Field
Stop Bit
Idle State
of Line
lsb
msb
Bit7 Parity
1
0
Start
Bit0
Bit1
Bit2
Bit3
Bit4
Bit5
Bit6
1
Figure 27. LIN-UART Driver Enable Signal Timing (shown with 1 Stop Bit and Parity)
The DE to Start bit setup time is calculated as follows:
1
2
-------------------------------------
-------------------------------------
DE to Start Bit Setup Time (s)
Baud Rate (Hz)
Baud Rate (Hz)
LIN-UART Special Modes
The LIN-UART features the following two special modes:
•
•
MULTIPROCESSOR Mode
LIN Mode
The LIN-UART has a common control register (Control 0), which has a unique register
address and several mode-specific control registers (multiprocessor control, noise filter
control and LIN control) which share a common register address (Control 1). When the
Control 1 address is read or written, the mode select (MSEL[2:0])field of the mode select
and status register determines which physical register is accessed. Similarly, there are
mode-specific status registers, one of which is returned when the Status 0 Register is read,
depending on the MSEL field.
MULTIPROCESSOR (9-bit) Mode
The LIN-UART features a MULTIPROCESSOR (9-Bit) Mode which uses an extra (9th)
bit for selective communication when a number of processors share a common UART bus.
In MULTIPROCESSOR Mode (also referred to as 9-Bit Mode), the multiprocessor bit
(MP) is transmitted immediately following the 8 bits of data and immediately preceding the
Stop bit(s), as illustrated in Figure 28.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Special Modes
ZNEO® Z16F Series MCUs
Product Specification
143
Data Field
Stop Bit(s)
Idle State
of Line
lsb
msb
Bit7
1
0
Start
Bit0
Bit1
Bit2
Bit3
Bit4
Bit5
Bit6
MP
1
2
Figure 28. LIN-UART Asynchronous MULTIPROCESSOR Mode Data Format
In MULTIPROCESSOR (9-Bit) Mode, the Parity (9th) bit location becomes the MULTI-
PROCESSOR control bit. The LIN-UART Control 1 and Status 1 registers provide MUL-
TIPROCESSOR (9-Bit) Mode control and status information. If an automatic address
matching scheme is enabled, the LIN-UART Address Compare Register holds the net-
work address of the device.
MULTIPROCESSOR (9-bit) Mode Receive Interrupts
When MULTIPROCESSOR Mode is enabled, the LIN-UART processes only frames
addressed to it. You can determine whether a frame of data is addressed to the LIN-UART
is made in hardware, software or a combination of the two, depending on the multiproces-
sor configuration bits. In general, the address compare feature reduces the load on the
CPU because it is not required to access the LIN-UART when it receives data directed to
other devices on the multi-node network. The following 3 MULTIPROCESSOR modes
are available in the hardware:
1. Interrupt on all address bytes.
2. Interrupt on matched address bytes and correctly framed data bytes.
3. Interrupt only on correctly framed data bytes.
These modes are selected with MPMD[1:0]in the LIN-UART Control 1 Register. For all
MULTIPROCESSOR modes, bit MPENof the LIN-UART Control 1 Register must be set
to 1.
The first scheme is enabled by writing 01bto MPMD[1:0]. In this mode, all incoming
address bytes cause an interrupt, while data bytes never cause an interrupt. The ISR checks
the address byte which triggered the interrupt. If it matches the LIN-UART address, the
software clears MPMD[0]. At this point, each new incoming byte interrupts the CPU. The
software determines the end of the frame and checks for it by reading the MPRXbit of the
LIN-UART Status 1 Register for each incoming byte. If MPRX=1, a new frame has begun.
If the address of this new frame is different from the LIN-UART’s address, then
PS022010-0811
P R E L I M I N A R Y
MULTIPROCESSOR (9-bit) Mode
ZNEO® Z16F Series MCUs
Product Specification
144
MPMD[0]must be set to 1 by software, causing the LIN-UART interrupts to go inactive
until the next address byte. If the new frame’s address matches the LIN-UART’s, then the
data in the new frame is processed.
The second scheme is enabled by setting MPMD[1:0]to 10band writing the LIN-UART’s
address into the LIN-UART Address Compare Register. This mode introduces more hard-
ware control, interrupting only on frames which match the address of LIN-UART. When
an incoming address byte does not match the address of LIN-UART, it is ignored. All suc-
cessive data bytes in this frame are also ignored. When a matching address byte occurs, an
interrupt is issued and further interrupts occur on each successive data byte. The first data
byte in the frame has NEWFRM=1in the LIN-UART Status 1 Register. When the next
address byte occurs, the hardware compares it to the address of LIN-UART. If there is a
match, the interrupt occurs and the NEWFRM bit is set for the first byte of the new frame.
If there is no match, the LIN-UART ignores all incoming bytes until the next address
match.
The third scheme is enabled by setting MPMD[1:0]to 11band by writing the address of
LIN-UART into the LIN-UART Address Compare Register. This mode is identical to the
second scheme, except that there are no interrupts on address bytes. The first data byte of
each frame remains accompanied by a NEWFRMassertion.
LIN Protocol Mode
The LIN protocol as supported by the LIN-UART module is defined in revision 2.0 of the
LIN specification package. The LIN protocol specification covers all aspects of transfer-
ring information between LIN master and slave devices using message frames including
error detection and recovery, SLEEP Mode and wake up from SLEEP Mode. The LIN-
UART hardware in LIN Mode provides character transfers to support the LIN protocol
including Break transmission and detection, WAKE-UP transmission and detection and
slave autobauding. Part of the error detection of the LIN protocol is for both master and
slave devices to monitor their receive data when transmitting. If the receive and transmit
data streams do not match, the LIN-UART asserts the PLE bit (physical layer error bit in
Status 0 Register). The message frame time-out aspect of the protocol is left to software,
requiring the use of an additional general purpose timer. The LIN Mode of the LIN-UART
does not provide any hardware support for computing/verifying the checksum field or to
verify the contents of the identifier field. These fields are treated as data and are not inter-
preted by the hardware.
The LIN bus contains a single master and one or more slaves. The LIN master is responsi-
ble for transmitting the message frame header which consists of the Break, Synch, and
Identifier fields. Either the master or one of the slaves transmits the associated response
section of the message, which consists of data characters followed by a checksum charac-
ter.
In LIN Mode, the interrupts defined for normal UART operation still apply with the fol-
lowing changes:
PS022010-0811
P R E L I M I N A R Y
LIN Protocol Mode
ZNEO® Z16F Series MCUs
Product Specification
145
•
•
Parity error (PE bit in Status 0 Register) is redefined as the Physical Layer Error (PLE)
bit. The PLE bit indicates that receive data does not match transmit data when the LIN-
UART is transmitting. This applies to both MASTER and SLAVE OPERATING
modes.
The break detect interrupt (BRKDbit in Status 0 Register) indicates when a Break is de-
tected by the slave (break condition for at least 11 bit times). Software uses this inter-
rupt to start a timer checking for message frame time-out. The duration of the break is
read in the RxBreakLength[3:0]field of the Mode Status register.
•
•
The break detect interrupt (BRKDbit in Status 0 Register) indicates when a wake-up
message has been received if the LIN-UART is in LINSLEEP state.
In LIN SLAVE Mode, if the BRG counter overflows while measuring the autobaud pe-
riod (Startbit to beginning of bit 7 of autobaud character) an overrun error is indicat-
ed (OEbit in the Status 0 Register). In this case, software sets the LinState field back to
10b, where the slave ignores the current message and waits for the next Break signal.
The baud reload high and low registers are not updated by hardware if this autobaud
error occurs. The OEbit is also set if a data overrun error occurs.
LIN System Clock Requirements
The LIN master provides the timing reference for the LIN network and is required to have
a clock source with a tolerance of ±0.5%. A slave with autobaud capability is required to
have a baud clock matching the master oscillator within ±14%. The slave nodes autobaud
to lock onto the master timing reference with an accuracy of ±2%. If a slave does not con-
tain autobaud capability, it must include a baud clock which deviates from the masters by
no more than ±1.5%. These accuracy requirements must include effects such as voltage
and temperature drift during operation.
Before sending or receiving messages, the baud reload High/Low registers must be initial-
ized. Unlike standard UART modes, the baud reload High/Low registers must be loaded
with the baud interval rather than 1/16 of the baud interval.
In order to autobaud with the required accuracy, the LIN slave system clock must be at
least 100 times the baud rate.
LIN Mode Initialization and Operation
A LIN protocol mode is selected by setting either the LIN master (LMST) or LIN slave
(LSLV) and optionally (for LIN slave) the autobaud enable (ABEN) bits in the LIN Control
Register. To access the LIN Control Register, the mode select (MSEL) field of the LIN-
UART Mode Select/Status Register must be 010b. The LIN-UART Control 0 Register
must be initialized with TEN = 1, REN = 1, all other bits = 0.
In addition to the LMST, LSLV and ABEN bits in the LIN Control Register, a Lin-
State[1:0] field exists that defines the current state of the LIN logic. This field is initially
PS022010-0811
P R E L I M I N A R Y
LIN Protocol Mode
ZNEO® Z16F Series MCUs
Product Specification
146
set by the software. In the LIN SLAVE Mode, the LinState field is updated by hardware as
the slave moves through the Wait for Break, AutoBaud and Active states.
The noise filter is also required to be enabled and configured when interfacing to a LIN
bus.
LIN MASTER Mode Operation
LIN MASTER Mode is selected by setting the bits LMST = 1, LSLV = 0, ABEN = 0, Lin-
State[1:0] = 11b. If the LIN bus protocol indicates the bus is required go into the LIN
Sleep state, the LinState[1:0] bits must be set = 00bby the software.
The Break is the first part of the message frame transmitted by the master, consisting of at
least 13 bit periods of logical zero on the LIN bus. During initialization of the LIN master,
the duration (in bit times) of the Break is written to the TxBreakLength field of the LIN
Control Register. The transmission of the Break is performed by setting the SBRKbit in the
Control 0 Register. The LIN-UART starts the Break after the SBRKbit is set and any char-
acter transmission currently underway has completed. The SBRKbit is deasserted by hard-
ware after the break is completed.
The Synch character is transmitted by writing a 55Hto the Transmit Data Register (TDRE
must be 1 before writing). The Synch character is not transmitted by the hardware until
after the Break is complete.
The Identifier character is transmitted by writing the appropriate value to the Transmit
Data Register (TDREmust be 1 before writing).
If the master is sending the response portion of the message, these data and checksum
characters are written to the Transmit Data Register when the TDRE bit asserts.
If the Transmit Data Register is written after TDRE asserts, but before TXE asserts, the
hardware inserts one or two Stop bits between each character as determined by the Stop bit
in the Control 0 Register. Additional idle time occurs between characters if TXE asserts
before the next character is written.
LIN Sleep Mode
While the LIN bus is in the Sleep state, the CPU is in either low power STOP Mode, in
HALT Mode, or in normal operational state. Any device on the LIN bus issues a Wake-up
message (transmits an 80Hcharacter) if it requires the master to initiate a LIN message
frame. Following the Wake-up message, the master wakes up and initiates a new message.
If the CPU is in STOP Mode, the LIN-UART is not active and the Wake-up message must
be detected by a GPIO edge detect Stop Mode Recovery. The duration of the Stop Mode
Recovery sequence may preclude making an accurate measurement of the Wake-up mes-
sage duration.
If the CPU is in HALT or OPERATIONAL Mode, the LIN-UART (if enabled) times the
duration of the Wake-up and provides an interrupt following the end of the break sequence
if the duration is 4 bit times. The total duration of the Wake-up message in bit times is
PS022010-0811
P R E L I M I N A R Y
LIN Protocol Mode
ZNEO® Z16F Series MCUs
Product Specification
147
obtained by reading the RxBreakLengthfield in the mode status register. After a Wake-
up message is detected, the LIN-UART is placed (by software) into either Lin Master or
Lin Slave Wait for Break states as appropriate. If the break duration exceeds fifteen bit
times, the RxBreakLengthfield contains the value FH.
Lin Sleep state is selected by software setting LinState[1:0]=00. The decision to
move from an active state to sleep state is based on the LIN messages as interpreted by the
software.
LIN Slave Operation
LIN SLAVE Mode is selected by setting the bits LMST= 0, LSLV= 1, ABEN= 1or 0and
LinState[1:0]=01b(Wait for Break state). The LIN slave detects the start of a new
message by the Break which appears to the slave as a break of at least 11 bit times in dura-
tion. The LIN-UART detects the Break and generates an interrupt to the CPU. The dura-
tion of the Break is observable in the RxBreakLengthfield of the mode status register. A
Break of less than 11 bit times in duration does not generate a break interrupt when the
LIN-UART is in “Wait for Break” state. If the Break duration exceeds 15 bit times, the
RxBreakLengthfield contains the value FH.
Following the Break the LIN-UART hardware automatically transits to the autobaud state,
where it autobauds by timing the duration of the first 8 bit times of the Synch character as
defined in the standard. At the end of the autobaud period, the duration measured by the
BRG counter (auto baud period divided by 8) is automatically transferred to the baud
reload high and low registers if the ABENbit of the LIN Control Register is set. If the BRG
counter overflows before reaching the start of bit 7 in the autobaud sequence the autobaud
overrun error interrupt occurs, the OE bit in the Status 0 Register is set and the baud reload
registers are not updated. To autobaud within 2% of the master’s baud rate, the slave sys-
tem clock must be minimum 100 times the baud rate. To avoid an autobaud overrun error,
the system clock must not be greater than 219 times the baud rate (16 bit counter following
3-bit prescaler when counting the 8 bit times of the autobaud sequence).
Following the Synch character, the LIN-UART hardware transits to the active state, where
the Identifier character is received and the characters of the response section of the mes-
sage are sent or received. The slave remains in the active state until a Break is received or
the software forces a state change. When it is in active State (autobaud has completed), a
Break of 10 or more bit times is recognized and a transition to the autobaud state is caused.
LIN-UART Interrupts
The LIN-UART features separate interrupts for the transmitter and receiver. In addition,
when the LIN-UART primary functionality is disabled, the BRG also functions as a basic
timer with interrupt capability.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Interrupts
ZNEO® Z16F Series MCUs
Product Specification
148
Transmitter Interrupts
The transmitter generates a single interrupt when the Transmit Data Register empty bit
(TDRE) is set to 1. This indicates that the transmitter is ready to accept new data for trans-
mission. The TDRE interrupt occurs when the transmitter is initially enabled and after the
transmit shift register has shifted the first bit of a character out. At this point, the Transmit
Data Register is written with the next character to send. This provides 7 bit periods of
latency to load the Transmit Data Register before the transmit shift register completes
shifting the current character. Writing to the LIN-UART Transmit Data Register clears the
TDRE bit to 0.
Receiver Interrupts
The receiver generates an interrupt when any of the following occurs:
•
A data byte is received and is available in the LIN-UART Receive Data Register. This
interrupt is disabled independent of the other receiver interrupt sources using the
RDAIRQbit (this feature is useful in devices, which support DMA). The received data
interrupt occurs after the receive character is placed in the Receive Data Register. To
avoid an overrun error, the software responds to this received data available condition
before the next character is completely received.
Note: In MULTIPROCESSOR Mode (MPEN= 1), the receive data interrupts are dependent on
the multiprocessor configuration and the most recent address byte.
•
•
•
•
A break is received.
A receive data overrun or LIN slave autobaud overrun error is detected.
A data framing error is detected.
A parity error is detected (physical layer error in LIN Mode).
LIN-UART Overrun Errors
When an overrun error condition occurs, the LIN-UART prevents overwriting of the valid
data currently in the Receive Data Register. The break detect and overrun status bits are
not displayed until the valid data is read.
When the valid data is read, the OE bit of the Status 0 Register is updated to indicate the
overrun condition (and Break Detect, if applicable). The RDA bit is set to 1 to indicate that
the Receive Data Register contains a data byte. However, because the overrun error
occurred, this byte may not contain valid data and must be ignored. The BRKD bit indi-
cates if the overrun is caused due to a break condition on the line. After reading the status
PS022010-0811
P R E L I M I N A R Y
LIN-UART Interrupts
ZNEO® Z16F Series MCUs
Product Specification
149
byte indicating an overrun error, the Receive Data Register must be read again to clear the
error bits in the LIN-UART Status 0 Register.
In LIN Mode, an overrun error is signaled for receive data overruns as described above
and in the LIN Slave, if the BRG counter overflows during the autobaud sequence (the
ATBbit will also be set in this case). There is no data associated with the autobaud over-
flow interrupt, however the Receive Data Register must be read to clear the OE bit. In this
case software must write 10bto the LinStatefield, forcing the LIN slave back to Wait
for Break state.
LIN-UART Data and Error Handling Procedure
Figure 29 displays the recommended procedure for use in LIN-UART receiver interrupt
service routines.
Receiver
Ready
Receiver
Interrupt
Read Status
No
Errors?
Yes
Read Data which
clears RDA bit and
resets error bits
Read Data
Discard Data
Figure 29. LIN-UART Receiver Interrupt Service Routine Flow
PS022010-0811
P R E L I M I N A R Y
LIN-UART Interrupts
ZNEO® Z16F Series MCUs
Product Specification
150
Baud Rate Generator Interrupts
If the BRGCTL bit of the Multiprocessor Control Register (LIN-UART Control 1 Register
with MSEL = 000b) register is set and the RENbit of the Control 0 Register is 0, the LIN-
UART receiver interrupt asserts when the LIN-UART baud rate generator reloads. This
action allows the BRG to function as an additional counter if the LIN-UART receiver
functionality is not employed. The transmitter is enabled in this mode.
LIN-UART DMA Interface
The DMA engine is configured to move UART transmit and/or receive data. This reduces
processor overhead, especially when moving blocks of data. The DMA interface on the
LIN-UART consists of the TxDmaReqand RxDmaReqoutputs and the TxDmaAckand
RxDmaAckinputs. Any of the DMA channels are configured to process the UART DMA
requests.
If transmit data is to be moved by the DMA, the transmit interrupt must be disabled in the
interrupt controller. If receive data is to be moved by the DMA, the RDAIRQ bit in the
LIN-UART Control 1 Register must be set. This disables receive data interrupts when still
enabling error interrupts. The receive interrupt must be enabled in the interrupt controller
to process error condition interrupts.
LIN-UART Baud Rate Generator
The LIN-UART baud rate generator creates a lower frequency baud rate clock for data
transmission. The input to the BRG is the system clock. The LIN-UART Baud Rate High
and Low Byte registers combine to create a 16-bit baud rate divisor value (BRG[15:0])
which sets the data transmission rate (baud rate) of the LIN-UART. The LIN-UART data
rate is calculated using the following equation for normal UART operation:
System Clock Frequency (Hz)
16 UART Baud Rate Divisor Value
------------------------------------------------------------------------------------------
UART Data Rate (bps) =
The LIN-UART data rate is calculated using the following equation for LIN Mode UART
operation:
System Clock Frequency (Hz)
UART Baud Rate Divisor Value
-----------------------------------------------------------------------------
UART Data Rate (bps) =
When the LIN-UART is disabled, the BRG functions as a basic 16-bit timer with interrupt
on time-out. Observe the following steps to configure BRG as a timer with interrupt on
time-out:
1. Disable the LIN-UART receiver by clearing the REN bit in the LIN-UART Control 0
Register to 0 (TEN bit is asserted, transmit activity may occur).
PS022010-0811
P R E L I M I N A R Y
LIN-UART DMA Interface
ZNEO® Z16F Series MCUs
Product Specification
151
2. Load the appropriate 16-bit count value into the LIN-UART Baud Rate High and Low
Byte registers.
3. Enable the BRG timer function and associated interrupt by setting the BRGCTL bit in
the LIN-UART Control 1 Register to 1. Enable the UART receive interrupt in the
interrupt controller.
When configured as a general purpose timer, the BRG interrupt interval is calculated using
the following equation:
UART BRG Interrupt Interval (s) = System Clock Period (s) BRG[15:0]
Noise Filter
A noise filter circuit is included to filter noise on a digital input signal, such as UART
receive data before the data is sampled by the block. This filter is a requirement for proto-
cols in a noisy environment.
The noise filter includes following features:
•
•
Synchronizes the receive input data to the system clock.
Noise filter enable (NFEN)input selects whether the noise filter is bypassed (NFEN =
0) or included (NFEN = 1) in the receive data path.
•
Noise filter control (NFCTL[2:0])input selects the width of the up/down saturating
counter digital filter. The available widths range is from 4 to11 bits.
•
•
The digital filter output has hysteresis.
Provides an active low saturated state output (FiltSatB), used to indicate presence of
noise.
Architecture
Figure 30 displays how the noise filter is integrated with the LIN-UART for use on a LIN
network.
PS022010-0811
P R E L I M I N A R Y
Noise Filter
ZNEO® Z16F Series MCUs
Product Specification
152
System
Clock
RxD
RxD
RxD
FiltSatB
Noise Filter
NFEN, NFCTL
LIN
Transceiver
LIN-UART
TxD
TxD
TxD
Figure 30. Noise Filter System Block Diagram
Operation
Figure 31 displays the operation of the noise filter with and without noise. The noise filter
in this example is a 2-bit up/down counter, which saturates at 00band 11b. A 2-bit coun-
ter is shown for convenience, the operation of wider counters is similar. The output of the
filter switches from 1 to 0 when the counter counts down from 01bto 00band switches
from 0 to 1 when the counter counts up from 10bto 11b. The noise filter delays the
received data by three system clock cycles.
The FiltSatBsignal is checked when the filtered RxD is sampled in the center of the bit
time. The presence of noise (FiltSatB= 1 at center of bit time) does not mean the sam-
pled data is incorrect, just that the filter is not in its saturated state of all 1’s or all 0’s. If
FiltSatB= 1when RxD is sampled during a receive character, the NEbit in the Mod-
eStatus[4:0]field is set. An indication of the level of noise in the network is obtained
by observing this bit.
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
153
Baud Period
16x Sample
Clock
Input
RxD (ideal)
Data Bit = 0
Data Bit = 1
Clean RxD
Example
Noise Filter
Up/Dn Cntr
3 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3
nominal filter delay
Noise Filter
Output RxD
Input
RxD (noisy)
Data Bit=0
Data Bit=1
Noise RxD
Example
Noise Filter
Up/Dn Cntr
3 3 2 1 0 0 0 0 0 0 1 2 1 0 0 0 0 0 1 0 1 2 3 3 3 3 2 3 3 3 3 3 3 3
Noise Filter
Output RxD
FiltSatB
Output
UART
Sample
Point
Figure 31. Noise Filter Operation
LIN-UART Control Register Definitions
The LIN-UART control registers support the LIN-UART, the associated Infrared encoder/
decoder and the noise filter. For detailed information about the infrared operation, see the
Infrared Encoder/Decoder chapter on page 172.
LIN-UART Transmit Data Register
Data bytes written to the LIN-UART Transmit Data Register, shown in Table 80, are
shifted out on the TXD pin. The Write-only LIN-UART Transmit Data Register shares a
Register File address with the Read-only LIN-UART Receive Data register.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
154
Table 80. LIN-UART Transmit Data Register (UxTXD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
TXD
X
W
Addr
FF‒E200H, FF‒E210H
Bit
Description
[7:0]
TXD
Transmit Data
LIN-UART transmitter data byte to be shifted out through the TXD pin.
LIN-UART Receive Data Register
Data bytes received through the RXD pin are stored in the LIN-UART Receive Data Reg-
ister, shown in Table 81. The Read-only LIN-UART Receive Data Register shares a regis-
ter file address with the Write-only LIN-UART Transmit Data Register.
Table 81. LIN-UART Receive Data Register (UxRXD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RXD
X
R
Addr
FF‒E200H, FF‒E210H
Bit
Description
[7:0]
RXD
Receive Data
LIN-UART receiver data byte from the RXD pin
PS022010-0811
P R E L I M I N A R Y
LIN-UART Receive Data Register
ZNEO® Z16F Series MCUs
Product Specification
155
LIN-UART Status 0 Register
The LIN-UART Status 0 Register identifies the current LIN-UART operating configura-
tion and status. Table 82 describes the Status 0 Register for standard UART Mode.
Table 83 describes the Status 0 Register for LIN Mode.
Table 82. LIN-UART Status 0 Register, Standard UART Mode (UxSTAT0)
Bits
7
RDA
0
6
PE
0
5
OE
0
4
FE
0
3
BRKD
0
2
TDRE
1
1
TXE
1
0
CTS
X
Field
RESET
R/W
R
R
R
R
R
R
R
R
Addr
FF‒E201H, FF‒E211H
Bit
Description
[7]
RDA
Receive Data Available
This bit indicates that the LIN-UART Receive Data Register has received data. Reading the
LIN-UART Receive Data Register clears this bit.
0 = The LIN-UART Receive Data Register is empty.
1 = There is a byte in the LIN-UART Receive Data Register.
[6]
PE
Parity Error
This bit indicates that a parity error has occurred. Reading the Receive Data Register clears
this bit.
0 = No parity error occurred.
1 = A parity error occurred.
[5]
OE
Overrun Error
This bit indicates that an overrun error has occurred. An overrun occurs when new data is
received and the Receive Data Register has not been read. Reading the Receive Data Regis-
ter clears this bit.
0 = No overrun error occurred.
1 = An overrun error occurred.
[4]
FE
Framing Error
This bit indicates that a framing error (no Stop bit following data reception) is detected. Read-
ing the Receive Data Register clears this bit.
0 = No framing error occurred.
1 = A framing error occurred.
[3]
BRKD
Break Detect
This bit indicates that a break has occurred. If the data bits, parity/multiprocessor bit and Stop
bit(s) are all zeros then this bit is set to 1. Reading the Receive Data Register clears this bit.
0 = No break occurred.
1 = A break occurred.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Status 0 Register
ZNEO® Z16F Series MCUs
Product Specification
156
Bit
Description
[2]
TDRE
Transmitter Data Register Empty
This bit indicates that the Transmit Data Register is empty and ready for additional data. Writ-
ing to the Transmit Data Register resets this bit.
0 = Do not write to the Transmit Data Register.
1 = The Transmit Data Register is ready to receive an additional byte to be transmitted.
[1]
TXE
Transmitter Empty
This bit indicates that the transmit shift register is empty and character transmission is finished.
0 = Data is currently transmitting.
1 = Transmission is complete.
[0]
CTS
CTS Signal
When this bit is read it returns the CTS signal level. If LBEN= 1, the CTS input signal is
replaced by the internal receive data Available signal to provide flow control in LOOPBACK
Mode. CTS only affects transmission if the CTSEbit = 1.
Table 83. LIN-UART Status 0 Register, LIN Mode (UxSTAT0)
Bits
7
RDA
0
6
PLE
0
5
OE
0
4
FE
0
3
BRKD
0
2
TDRE
1
1
TXE
1
0
ATB
0
Field
RESET
R/W
R
R
R
R
R
R
R
R
Addr
FF‒E201H, FF‒E211H
Bit
Description
[7]
RDA
Receive Data Available
This bit indicates that the Receive Data Register has received data. Reading the Receive Data
Register clears this bit.
0 = The Receive Data Register is empty.
1 = There is a byte in the Receive Data Register.
[6]
PLE
Physical Layer Error
This bit indicates that transmit and receive data do not match when a LIN slave or master is
transmitting. This type of instance can be caused by a fault in the physical layer or multiple
devices driving the bus simultaneously. Reading the Status 0 Register or the Receive Data
Register clears this bit.
0 = Transmit and receive data match.
1 = Transmit and receive data do not match.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Status 0 Register
ZNEO® Z16F Series MCUs
Product Specification
157
Bit
Description (Continued)
[5]
OE
Receive Data and Autobaud Overrun Error
This bit is set just as in normal UART operation if a receive data overrun error occurs.
This bit is also set during LIN slave autobaud if the BRG counter overflows before the end of
the autobaud sequence, indicating that the receive activity was not an autobaud character or
the master baud rate is too slow. The ATB status bit will also be set in this case. This bit is
cleared by reading the Receive Data Register.
0 = No autobaud or data overrun error occurred.
1 = An autobaud or data overrun error occurred.
[4]
FE
Framing Error
This bit indicates that a framing error (no Stop bit following data reception) is detected. Read-
ing the Receive Data Register clears this bit.
0 = No framing error occurred.
1 = A framing error occurred.
[3]
BRKD
Break Detect
This bit is set in LIN Mode if (a) in LinSleep state and a break of at least 4 bit times occurred
(Wake-up event) or (b) in Slave Wait Break state and a break of at least 11 bit times occurred
(Break event), or (c) in Slave Active state and a break of at least 10 bit times occurs. Reading
the Status 0 Register or the Receive Data Register clears this bit.
0 = No LIN break occurred.
1 = A LIN break occurred.
[2]
TDRE
Transmitter Data Register Empty
This bit indicates that the Transmit Data Register is empty and ready for additional data. Writ-
ing to the Transmit Data Register resets this bit.
0 = Do not write to the Transmit Data Register.
1 = The Transmit Data Register is ready to receive an additional byte to be transmitted.
[1]
TXE
Transmitter Empty
This bit indicates that the transmit shift register is empty and character transmission is finished.
0 = Data is currently transmitting.
1 = Transmission is complete.
[0]
ATB
LIN Slave AutoBaud Complete
This bit is set in LIN SLAVE Mode when an autobaud character is received. If the ABIEN bit is
set in the LIN Control Register then a receive interrupt is generated when this bit is set. Read-
ing the Status 0 Register clears this bit. This bit will be 0 in LIN MASTER Mode.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Status 0 Register
ZNEO® Z16F Series MCUs
Product Specification
158
LIN-UART Mode Select and Status Register
The LIN-UART Mode Select and Status Register contains mode select and status bits. The
four Mode Status options in Table 84 are further described in Tables 85 through 88.
Table 84. LIN-UART Mode Select and Status Register (UxMDSTAT)
Bits
7
6
MSEL
0
5
4
3
2
1
0
Field
RESET
R/W
Mode Status
0
0
0
0
0
0
0
R/W
R/W
R/W
R
R
R
R
R
Addr
FF‒E204H, FF‒E214H
Bit
Description
Mode Select
[7:5]
MSEL
This R/W field determines which control register is accessed when performing a Write or Read
to the UART Control 1 Register address. This field also determines which status is returned in
the mode status field when reading this register.
000 = Multiprocessor and normal UART control/status
001 = Noise Filter control/status
010 = LIN Protocol control/status
011–110: Reserved
111 = LIN-UART hardware revision (allows hardware revision to be read in the mode status
field)
[4:0]
Mode
Status
Mode Status
This read-only field returns status corresponding to the mode selected by MSELas follows:
000: MULTIPROCESSOR and NORMAL UART Mode status = {NE, 0,0,NEWFRM, MPRX}
001: Noise filter status = {NE, 0,0,0,0}
010: LIN Mode status = {NE, RxBreakLength[3:0]}
011–110: Reserved = {0, 0, 0, 0, 0}
111: LIN-UART hardware revision
PS022010-0811
P R E L I M I N A R Y
LIN-UART Mode Select and Status
ZNEO® Z16F Series MCUs
Product Specification
159
Table 85. MULTIPROCESSOR Mode Status Field (MSEL = 000b)
Noise Event
NE
This bit is asserted if digital noise is detected on the receive data line when the data is sam-
pled (center of bit time). If this bit is set, it does not mean that the receive data is corrupted
(in extreme cases), just that one or more of the noise filter data samples near the center of
the bit time did not match the average data value.
NEWFRM
MPRX
New Frame
Status bit denoting the start of a new frame. Reading the LIN-UART Receive Data Register
Resets this bit to 0.
0 = The current byte is not the first data byte of a new frame.
1 = The current byte is the first data byte of a new frame.
Multiprocessor Receive
Returns the value of the last multiprocessor bit received. Reading from the LIN-UART
Receive Data Register Resets this bit to 0.
Table 86. Digital Noise Filter Mode Status Field (MSEL = 001b)
NE
Noise Event
This bit is asserted if digital noise is detected on the receive data line while the data is sam-
pled (center of bit time). If this bit is set, it does not mean that the receive data is corrupted
(in extreme cases), just that one or more of the noise filter data samples near the center of
the bit time did not match the average data value.
Table 87. LIN Mode Status Field (MSEL = 010B)
NE
Noise Event
This bit is asserted if some noise level is detected on the receive data line when the data is
sampled (center of bit time). If this bit is set, it does not indicate that the receive data is cor-
rupt (in extreme cases), just that one or more of the 16x data samples near the center of the
bit time did not match the average data value.
RxBreak-
Length
LIN Mode Received Break Length
This field is read following a break (LIN WAKE-UP or BREAK) so software determines the
measured duration of the break. If the break exceeds 15 bit times the value saturates at
1111B.
Table 88. Hardware Revision Mode Status Field (MSEL = 111b)
LIN-UART This field indicates the hardware revision of the LIN-UART block.
Hardware
Revision
00_xxx LIN UART hardware rev
01_xxx Reserved
10_xxx Reserved
11_xxx Reserved
PS022010-0811
P R E L I M I N A R Y
LIN-UART Mode Select and Status
ZNEO® Z16F Series MCUs
Product Specification
160
LIN-UART Control 0 Register
The LIN-UART Control 0 Register, shown in Table 89, configures the basic properties of
the LIN-UART’s transmit and receive operations.
Table 89. LIN-UART Control 0 Register (UxCTL0)
Bits
7
6
5
CTSE
0
4
3
PSEL
0
2
SBRK
0
1
STOP
0
0
LBEN
0
Field
RESET
R/W
TEN
0
REN
0
PEN
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF‒E202H, FF‒E212H
Bit
Description
[7]
TEN
Transmit Enable
This bit enables or disables the transmitter. The enable is also controlled by the CTS signal
and the CTSEbit. If the CTS signal is Low and the CTSEbit is 1, the transmitter is enabled.
0 = Transmitter disabled.
1 = Transmitter enabled.
[6]
REN
Receive Enable
This bit enables or disables the receiver.
0 = Receiver disabled.
1 = Receiver enabled.
[5]
CTSE
CTS Enable
0 = The CTS signal has no effect on the transmitter.
1 = The LIN-UART recognizes the CTS signal as an enable control for the transmitter.
[4]
PEN
Parity Enable
This bit enables or disables parity. Even or odd is determined by the PSEL bit.
0 = Parity is disabled. This bit is overridden by the MPEN bit.
1 = The transmitter sends data with an additional parity bit and the receiver receives an addi-
tional parity bit.
[3]
PSEL
Parity Select
0 = Even parity is transmitted and expected on all received data.
1 = Odd parity is transmitted and expected on all received data.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control 0 Register
ZNEO® Z16F Series MCUs
Product Specification
161
Bit
Description (Continued)
Send Break
[2]
SBRK
This bit pauses or breaks data transmission. Sending a break interrupts any transmission in
progress, so ensure that the transmitter has finished sending data before setting this bit. In
standard UART Mode, the duration of the break is determined by how long software leaves this
bit asserted. Also the duration of any required Stopbits following the break must be timed by
software before writing a new byte to be transmitted to the Transmit Data Register. In LIN
Mode, the master sends a Break character by asserting SBRK. The duration of the break is
timed by hardware and the SBRK bit is deasserted by hardware when the Break is completed.
The duration of the Break is determined by the TxBreakLength field of the LIN Control Regis-
ter. One or two Stop bits are automatically provided by the hardware in LIN Mode as defined by
the Stop bit.
0 = No break is sent.
1 = The output of the transmitter is 0.
[1]
STOP
Stop Bit Select
0 = The transmitter sends one stop bit.
1 = The transmitter sends two stop bits.
[0]
LBEN
Loop Back Enable
0 = Normal operation.
1 = All transmitted data is looped back to the receiver within the IrDA module.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control 0 Register
ZNEO® Z16F Series MCUs
Product Specification
162
LIN-UART Control 1 Registers
Multiple LIN-UART control registers, shown in Tables 90 through 92, are accessible by a
single bus address. The register selected is determined by the mode select (MSEL) field.
These registers provide additional control over the LIN-UART operation.
Multiprocessor Control Register (LIN-UART Control 1 Register with
MSEL = 000b)
When MSEL= 000b, this register provides control for UART MULTIPROCESSOR Mode,
IRDA Mode, baud rate timer mode as well as other features which applies to multiple
modes.
Table 90. MultiProcessor Control Register (UxCTL1 with MSEL = 000b)
Bits
7
MPMD[1]
0
6
MPEN
0
5
MPMD[0]
0
4
MPBT
0
3
DEPOL
0
2
1
0
IREN
0
Field
RESET
R/W
BRGCTL RDAIRQ
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF‒E203H, FF‒E213H with MSEL= 000b
Bit
Description
[7,5]
MULTIPROCESSOR Mode
MPMD[1] If MULTIPROCESSOR (9-Bit) Mode is enabled,
00 = The LIN-UART generates an interrupt request on all received bytes (data and address).
01 = The LIN-UART generates an interrupt request only on received address bytes.
10 = The LIN-UART generates an interrupt request when a received address byte matches the
value stored in the Address Compare Register and on all successive data bytes until an
address mismatch occurs.
11 = The LIN-UART generates an interrupt request on all received data bytes for which the
most recent address byte matched the value in the Address Compare Register.
[6]
MPEN
MULTIPROCESSOR (9-bit) Enable
This bit is used to enable MULTIPROCESSOR (9-Bit) Mode.
0 = Disable MULTIPROCESSOR (9-Bit) Mode.
1 = Enable MULTIPROCESSOR (9-Bit) Mode.
[4]
MPBT
Multiprocessor Bit Transmit
This bit is applicable only when MULTIPROCESSOR (9-Bit) Mode is enabled.
0 = Send 0 in the multiprocessor bit location of the data stream (9th bit).
1 = Send 1 in the multiprocessor bit location of the data stream (9th bit).
[3]
Driver Enable Polarity
DEPOL 0 = DE signal is active High.
1 = DE signal is active Low.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control 1 Registers
ZNEO® Z16F Series MCUs
Product Specification
163
Bit
Description (Continued)
[2]
Baud Rate Generator Control
BRGCTL This bit causes different LIN-UART behaviors, depending on whether the LIN-UART receiver is
enabled (REN= 1in the LIN-UART Control 0 Register).
When the LIN-UART receiver is not enabled, this bit determines whether the baud rate genera-
tor issues interrupts.
0 = BRG is disabled. Reads from the Baud Rate High and Low Byte registers return the BRG
Reload Value.
1 = BRG is enabled and counting. The BRG generates a receive interrupt when it counts down
to 0. Reads from the Baud Rate High and Low Byte registers return the current BRG count
value.
When the LIN-UART receiver is enabled, this bit allows reads from the baud rate registers to
return the BRG count value instead of the Reload Value.
0 = Reads from the Baud Rate High and Low Byte registers return the BRG Reload Value.
1 = Reads from the Baud Rate High and Low Byte registers return the current BRG count
value. Unlike the timers, there is no mechanism to latch the High byte when the Low byte is
read.
[1]
Receive Data Interrupt Enable
RDAIRQ 0 = Received data and receiver errors generates an interrupt request to the interrupt controller.
1 = Received data does not generate an interrupt request to the interrupt controller. Only
receiver errors generate an interrupt request.
[0]
IREN
Infrared Encoder/Decoder Enable
0 = Infrared encoder/decoder is disabled. LIN-UART operates normally.
1 = Infrared encoder/decoder is enabled. The LIN-UART transmits and receives data through
the Infrared encoder/decoder.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control 1 Registers
ZNEO® Z16F Series MCUs
Product Specification
164
Noise Filter Control Register (LIN-UART Control 1 Register with MSEL
= 001b)
When MSEL= 001b, this register, shown in Table 91, provides control for the digital noise
filter.
Table 91. Noise Filter Control Register (UxCTL1 with MSEL = 001b)
Bits
7
NFEN
0
6
5
NFCTL
0
4
3
2
1
0
Field
RESET
R/W
Reserved
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R
R
R
R
Addr
FF‒E203H, FF‒E213H with MSEL= 001b
Bit
Description
[7]
NFEN
Noise Filter Enable
0 = Noise filter is disabled.
1 = Noise filter is enabled. Receive data is preprocessed by the noise filter.
[6:4]
NFCTL
Noise Filter Control
This field controls the delay and noise rejection characteristics of the noise filter. The wider the
counter the more delay that is introduced by the filter and the wider the noise event that is fil-
tered.
000 = 4-bit up/down counter
001 = 5-bit up/down counter
010 = 6-bit up/down counter
011 = 7-bit up/down counter
100 = 8-bit up/down counter
101 = 9-bit up/down counter
110 = 10-bit up/down counter
111 = 11-bit up/down counter
[3:0]
Reserved
These bits are reserved and must be programmed to 0000.
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control 1 Registers
ZNEO® Z16F Series MCUs
Product Specification
165
LIN Control Register (LIN-UART Control 1 Register with MSEL = 010b)
When MSEL= 010b, this register, shown in Table 92, provides control for the LIN Mode
of operation.
Table 92. LIN Control Register (UxCTL1 with MSEL = 010b)
Bits
7
LMST
0
6
LSLV
0
5
ABEN
0
4
ABIEN
0
3
2
1
0
Field
RESET
R/W
LINSTATE[1:0]
TxBreakLength
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF‒E203H, FF‒E213H with MSEL= 010b
Bit
Description
LIN Master Mode
[7]
LMST
0 = LIN Master Mode not selected.
1 = LIN Master Mode selected (if MPEN, PEN, LSLV= 0)
[6]
LSLV
LIN Slave Mode
0 = LIN Slave Mode not selected.
1 = LIN Slave Mode selected (if MPEN, PEN, LMST= 0)
[5]
ABEN
Autobaud Enable
0 = Autobaud not enabled.
1 = Autobaud enabled if in LIN SLAVE Mode.
[4]
ABIEN
Autobaud Interrupt Enable
0 = Interrupt following autobaud does not occur.
1 = Interrupt following autobaud enabled if in LIN SLAVE Mode. When the autobaud char-
acter is received, a receive interrupt is generated and the ATBbit is set in the Status 0
Register.
[3:2]
LIN State Machine
LINSTATE[1:0] The LinState is controlled by both hardware and software. Software force a state change
at any time if necessary. In normal operation, software moves the state in and out of
Sleep state. For a LIN Slave, software changes the state from Sleep to Wait for Break
after which hardware cycles through the Wait for Break, Autobaud and Active states.
Software changes the state from one of the active states to Sleep state if the LIN bus
goes into Sleep Mode. For a LIN Master, software changes state from Sleep to Active
where it remains until software sets it back to the Sleep state. After configuration software
does not alter the LinStatefield during operation.
00 = Sleep State (either LMST or LSLV is set)
01 = Wait for Break state (only valid for LSLV = 1)
10 = Autobaud state (only valid for LSLV = 1)
11 = Active state (either LMST or LSLV is set)
PS022010-0811
P R E L I M I N A R Y
LIN-UART Control 1 Registers
ZNEO® Z16F Series MCUs
Product Specification
166
Bit
Description (Continued)
TxBreakLength
[1:0]
TxBreakLength Used in LIN Mode by the master to control the duration of the transmitted Break.
00 = 13 bit times
01 = 14 bit times
10 = 15 bit times
11 = 16 bit times
LIN-UART Address Compare Register
The LIN-UART Address Compare Register, shown in Table 93, stores the multi-node net-
work address of the LIN-UART. When the MPMD[1]bit of LIN-UART Control Register 0
is set, all incoming address bytes are compared to the value stored in the Address Compare
Register. Receive interrupts and RDAassertions occur only in the event of a match.
Table 93. LIN-UART Address Compare Register (UxADDR)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
COMP_ADDR
00H
R/W
Addr
FF‒E205H, FF‒E215H
Bit
Description
[7:0]
Compare Address
COMP_ADDR This 8-bit value is compared to the incoming address bytes.
LIN-UART Baud Rate High and Low Byte Registers
The LIN-UART Baud Rate High and Low Byte registers, shown in Tables 94 and 95,
combine to create a 16-bit baud rate divisor value (BRG[15:0]) which sets the data trans-
mission rate (baud rate) of the LIN-UART.
Table 94. LIN-UART Baud Rate High Byte Register (UxBRH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BRH
1
R/W
Addr
FF‒E206H, FF‒E216H
PS022010-0811
P R E L I M I N A R Y
LIN-UART Address Compare Register
ZNEO® Z16F Series MCUs
Product Specification
167
Table 95. LIN-UART Baud Rate Low Byte Register (UxBRL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BRL
1
R/W
Addr
FF‒E207H, FF‒E217H
The LIN-UART data rate is calculated using the following equation for standard UART
modes. For LIN protocol, the baud rate registers must be programmed with the baud
period rather than 1/16 baud period.
The UART must be disabled when updating the baud rate registers because High and Low
registers must be written independently.
Note:
The LIN-UART data rate is calculated using the following equation for standard UART
operation:
System Clock Frequency (Hz)
16 UART Baud Rate Divisor Value
------------------------------------------------------------------------------------------
UART Baud Rate (bits/s) =
The LIN-UART data rate is calculated using the following equation for LIN Mode UART
operation:
System Clock Frequency (Hz)
UART Baud Rate Divisor Value
-----------------------------------------------------------------------------
UART Data Rate (bits/s) =
For a given LIN-UART data rate, the integer baud rate divisor value is calculated using the
following equation for standard UART operation:
System Clock Frequency (Hz)
16 UART Data Rate (bits/s)
------------------------------------------------------------------------
UART Baud Rate Divisor Value (BRG) = Round
For a given LIN-UART data rate, the integer baud rate divisor value is calculated using the
following equation for LIN Mode UART operation:
System Clock Frequency (Hz)
------------------------------------------------------------------------
UART Baud Rate Divisor Value (BRG) = Round
UART Data Rate (bits/s)
PS022010-0811
P R E L I M I N A R Y LIN-UART Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
168
The baud rate error relative to the appropriate baud rate is calculated using the following
equation:
Actual Data Rate – Desired Data Rate
------------------------------------------------------------------------------------------
UART Baud Rate Error (%) = 100
Desired Data Rate
For reliable communication, the LIN-UART baud rate error must never exceed 5 percent.
Table 96 provides information about baud rate errors for popular baud rates and com-
monly used crystal oscillator frequencies for normal UART Mode of operation.
When the LIN-UART is disabled, the baud rate generator functions as a basic 16-bit timer
with interrupt on time-out. To configure the baud rate generator as a timer with interrupt
on time-out, complete the following procedure:
1. Disable the LIN-UART receiver by clearing the REN bit in the LIN-UART Control 0
Register to 0 (TENbit is asserted, transmit activity may occur).
2. Load the appropriate 16-bit count value into the LIN-UART Baud Rate High and Low
Byte registers.
3. Enable the baud rate generator timer function and associated interrupt by setting the
BRGCTL bit in the LIN-UART Control 1 Register to 1. Enable the UART receive
interrupt in the interrupt controller.
When configured as a general purpose timer, the BRG interrupt interval is calculated using
the following equation:
UART BRG Interrupt Interval (s) = System Clock Period (s) BRG[15:0]
PS022010-0811
P R E L I M I N A R Y LIN-UART Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
169
Table 96. LIN-UART Baud Rates
20.0MHz System Clock 10.0MHz System Clock
Desired
Rate
(kHz)
BRG
Divisor
(Decimal)
Actual
Rate
(kHz)
Desired
Rate
(kHz)
BRG
Divisor
(Decimal)
Actual
Rate
(kHz)
Error
(%)
Error
(%)
1250.0
625.0
250.0
115.2
57.6
1
2
1250.0
625.0
250.0
113.64
56.82
37.88
19.23
9.62
0.00
0.00
1250.0
625.0
250.0
115.2
57.6
N/A
1
N/A
625.0
208.33
125.0
56.8
N/A
0.00
5
0.00
3
–16.67
8.51
11
–1.19
–1.36
–1.36
0.16
5
22
11
–1.36
1.73
38.4
33
38.4
16
39.1
19.2
65
19.2
33
18.9
0.16
9.60
130
260
521
1042
2083
4167
0.16
9.60
65
9.62
0.16
4.80
4.81
0.16
4.80
130
260
521
1042
2083
4.81
0.16
2.40
2.399
1.199
0.60
–0.03
–0.03
0.02
2.40
2.40
–0.03
–0.03
–0.03
0.2
1.20
1.20
1.20
0.60
0.60
0.60
0.30
0.299
–0.01
0.30
0.30
PS022010-0811
P R E L I M I N A R Y LIN-UART Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
170
Table 96. LIN-UART Baud Rates (Continued)
5.5296MHz System Clock 3.579545MHz System Clock
Desired
Rate
(kHz)
BRG
Divisor
(Decimal)
Actual
Rate
(kHz)
Desired
Rate
(kHz)
BRG
Divisor
(Decimal)
Actual
Rate
(kHz)
Error
(%)
Error
(%)
1250.0
625.0
250.0
115.2
57.6
N/A
N/A
1
N/A
N/A
N/A
N/A
1250.0
625.0
250.0
115.2
57.6
N/A
N/A
1
N/A
N/A
N/A
N/A
345.6
115.2
57.6
38.4
19.2
9.60
4.80
2.40
1.20
0.60
0.30
38.24
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
223.72
111.9
55.9
37.3
18.6
9.73
4.76
2.41
1.20
0.60
0.30
–10.51
–2.90
–2.90
–2.90
–2.90
1.32
3
2
6
4
38.4
9
38.4
6
19.2
18
19.2
12
23
47
93
186
373
746
9.60
36
9.60
4.80
72
4.80
–0.83
0.23
2.40
144
288
576
1152
2.40
1.20
1.20
0.23
0.60
0.60
–0.04
–0.04
0.30
0.30
PS022010-0811
P R E L I M I N A R Y LIN-UART Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
171
Table 96. LIN-UART Baud Rates (Continued)
1.8432MHz System Clock
Desired
Rate
(kHz)
BRG
Divisor
(Decimal)
Actual
Rate
(kHz)
Error
(%)
1250.0
625.0
250.0
115.2
57.6
N/A
N/A
N/A
1
N/A
N/A
N/A
N/A
N/A
N/A
115.2
57.6
38.4
19.2
9.60
4.80
2.40
1.20
0.60
0.30
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
2
38.4
3
19.2
6
9.60
12
24
48
96
192
384
4.80
2.40
1.20
0.60
0.30
PS022010-0811
P R E L I M I N A R Y LIN-UART Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
172
Infrared Encoder/Decoder
The ZNEO® Z16F Series products contain two fully-functional, high-performance UART-
to-infrared encoder/decoders (endecs). Each infrared endec is integrated with an on-chip
UART to allow easy communication between the ZNEO and IrDA physical layer specifi-
cation, version 1.3-compliant infrared transceivers. Infrared communication provides
secure, reliable, low-cost, point-to-point communication between PCs, PDAs, cell phones,
printers and other infrared-enabled devices.
Architecture
Figure 32 displays the architecture of the infrared endec.
System
Clock
®
Zilog
ZHX1810
RxD
RXD
TXD
RXD
Infrared
TxD
Encoder/Decoder
(Endec)
TXD
Infrared
Transceiver
UART
Baud Rate
Clock
Interrupt
I/O
Data
Signal Address
Figure 32. Infrared Data Communication System Block Diagram
Operation
When the infrared endec is enabled, the transmit data from the associated on-chip UART
is encoded as digital signals in accordance with the IrDA standard and output to the infra-
red transceiver via the TXD pin. Similarly, data received from the infrared transceiver is
passed to the infrared endec via the RXD pin, decoded by the infrared endec and then
PS022010-0811
P R E L I M I N A R Y
Infrared Encoder/Decoder
ZNEO® Z16F Series MCUs
Product Specification
173
passed to the UART. Communication is half-duplex, which means that simultaneous data
transmission and reception is not allowed.
The baud rate is set by the UART’s baud rate generator and supports IrDA standard baud
rates from 9600 baud to 115.2 Kbaud. Higher baud rates are possible, but do not meet
IrDA specifications. The UART must be enabled to use the infrared endec. The infrared
endec data rate is calculated using the following equation:
System Clock Frequency (Hz)
16 UART Baud Rate Divisor Value
------------------------------------------------------------------------------------------
Infrared Data Rate (bps) =
Transmitting IrDA Data
The data to be transmitted using the infrared transceiver is first sent to the UART. The
UART’s transmit signal (TXD) and baud rate clock are used by the IrDA to generate the
modulation signal (IR_TXD) that drives the infrared transceiver. Each UART/infrared
data bit is 16-clocks wide. If the data to be transmitted is 1, the IR_TXD signal remains
Low for the full 16-clock period. If the data to be transmitted is 0, a 3-clock high pulse is
output following a 7-clock low period. After the 3-clock high pulse, a 6-clock low pulse is
output to complete the full 16-clock data period. Figure 33 displays IrDA data transmis-
sion. When the infrared endec is enabled, the UART’s TXD signal is internal to the ZNEO
Z16F Series products while the IR_TXD signal is output through the TXD pin.
16-clock
period
Baud Rate
Clock
UART’s
TXD
Start Bit = 0
Data Bit 0 = 1
Data Bit 1 = 0
Data Bit 2 = 1
Data Bit 3 = 1
3-clock
pulse
IR_TXD
7-clock
delay
Figure 33. Infrared Data Transmission
PS022010-0811
P R E L I M I N A R Y
Transmitting IrDA Data
ZNEO® Z16F Series MCUs
Product Specification
174
Receiving IrDA Data
Data received from the infrared transceiver via the IR_RXD signal through the RXD pin
is decoded by the infrared endec and passed to the UART. The UART’s baud rate clock is
used by the infrared endec to generate the demodulated signal (RXD) that drives the
UART. Each UART/infrared data bit is 16-clocks wide. Figure 34 displays data reception.
When the infrared endec is enabled, the UART’s RXD signal is internal to the ZNEO
Z16F Series products when the IR_RXD signal is received through the RXD pin.
16-clock
period
Baud Rate
Clock
Start Bit = 0
Data Bit 0 = 1
Data Bit 1 = 0
Data Bit 2 = 1
Data Bit 3 = 1
IR_RXD
min. 1.6 s
pulse
UART’s
RXD
Start Bit = 0
Data Bit 0 = 1
Data Bit 1 = 0
Data Bit 2 = 1
Data Bit 3 = 1
8-clock
delay
16-clock
period
16-clock
period
16-clock
period
16-clock
period
Figure 34. Infrared Data Reception
The system clock frequency must be at least 1.0MHz to ensure proper reception of the
Caution:
1.6s minimum width pulses allowed by the IrDA standard.
Endec Receiver Synchronization
The IrDA receiver uses a local baud rate clock counter (0 to 15 clock periods) to generate
an input stream for the UART and to create a sampling window for detection of incoming
pulses. The generated UART input (UART RXD) is delayed by 8 baud rate clock periods
with respect to the incoming IrDA data stream. When a falling edge in the input data
stream is detected, the endec counter is reset. When the count reaches a value of 8, the
UART RXD value is updated to reflect the value of the decoded data.
When the count reaches 12 baud clock periods, the sampling window for the next incom-
ing pulse opens. The window remains open until the count again reaches 8 (or in other
PS022010-0811
P R E L I M I N A R Y
Receiving IrDA Data
ZNEO® Z16F Series MCUs
Product Specification
175
words, 24 baud clock periods since the previous pulse was detected). This open window
allows the endec a sampling of minus 4 baudrate clocks to plus 8 baudrate clocks around
the expected time of an incoming pulse. If an incoming pulse is detected inside this win-
dow, this process is repeated. If the incoming data is a logical 1 (no pulse), the endec
returns to the initial state and waits for the next falling edge. As each falling edge is
detected, the endec clock counter is reset, resynchronizing the endec to the incoming sig-
nal. This allows the endec to tolerate jitter and baud rate errors in the incoming data
stream. Resynchronizing the endec does not alter the operation of the UART, which ulti-
mately receives the data. The UART is only synchronized to the incoming data stream
when a Start bit is received.
Infrared Encoder/Decoder Control Register Definitions
All infrared endec configuration and status information is set by the UART control reg-
isters as defined in the beginning of the LIN-UART Control Register Definitions section
on page 153.
Caution:
To prevent spurious signals during IrDA data transmission, set the IRENbit in the UARTx
Control 1 Register to 1 to enable the infrared encoder/decoder before enabling the GPIO
port alternate function for the corresponding pin.
PS022010-0811
P R E L I M I N A R Y Infrared Encoder/Decoder Control Register
ZNEO® Z16F Series MCUs
Product Specification
176
Enhanced Serial Peripheral Interface
The Enhanced Serial Peripheral Interface (ESPI) supports SPI (Serial Peripheral Interface)
and Inter IC Sound (I2S) modes of operation.
The features of the ESPI include:
•
•
•
•
Full-duplex, synchronous, character-oriented communication
Four-wire interface (SS, SCK, MOSI, MISO)
Transmit and receive buffer registers to enable high throughput
Transfer rates up to maximum of one-fourth the system clock frequency in SLAVE
Mode
•
•
•
Error detection
Dedicated programmable baud rate generator (BRG)
Data transfer control through polling, interrupt, or DMA
Architecture
The ESPI is a full-duplex, synchronous, character-oriented channel that supporting a four-
wire interface (serial clock, transmit and receive data and Slave select). The ESPI block
consists of a shift register, transmit and receive data buffer registers, a baud rate (clock)
generator, control/status registers and a control state machine. Transmit and receive trans-
fers are in sync as there is a single shift register for both transmit and receive data. Fig-
ure 35 displays a block diagram of the ESPI.
PS022010-0811
P R E L I M I N A R Y
Enhanced Serial Peripheral Interface
ZNEO® Z16F Series MCUs
Product Specification
177
Peripheral Bus
Interrupt
DMA Requests
TX RX
ESPI BRH
Register
ESPI Control
Register
ESPI Status
Register
ESPI BRL
Register
ESPI State
Register
ESPI Mode
Register
ESPI State
Machine
Baud
Rate
Generator
Interrupt/
DMA Logic
count = 1
Transmit Data Register
SCK
Logic
0 Shift Register 7
data_out
Receive Data Register
SCK SCK
in
out
SS out SS in
MISO
out
MOSI
out
Pin Direction
Control
MISO MOSI
in
in
GPIO Logic and Port Pins
SS
MISO
MOSI
SCK
Figure 35. ESPI Block Diagram
PS022010-0811
P R E L I M I N A R Y
Architecture
ZNEO® Z16F Series MCUs
Product Specification
178
ESPI Signals
The four ESPI signals are:
•
•
•
•
Master-In/Slave-Out (MISO)
Master-Out/Slave-In (MOSI)
Serial clock (SCK)
Slave select (SS)
The following paragraphs describe these signals in both MASTER and SLAVE modes.
The appropriate GPIO pins must be configured using the GPIO alternate function regis-
ters.
Master-In/Slave-Out
The MISO pin is configured as an input in a master device and as an output in a slave
device. Data is transferred to most significant bit first. The MISO pin of a slave device is
placed in a high-impedance state if the slave is not selected. When the ESPI is not enabled,
this signal is in a high-impedance state. The direction of this pin is controlled by the MMEN
bit of the ESPI Control Register.
Master-Out/Slave-In
The MOSI pin is configured as an output in a master device and as an input in a slave
device. Data is transferred to most significant bit first. When the ESPI is not enabled, this
signal is in a high-impedance state. The direction of this pin is controlled by the MMENbit
of the ESPI Control Register.
Serial Clock
The SCK synchronizes data movement both in and out of the shift register via the MOSI
and MISO pins. In MASTER Mode (MMEN=1), the ESPI’s baud rate generator creates the
serial clock and drives it out via its SCK pin to the slave devices. In SLAVE Mode, the
SCK pin is an input. Slave devices ignore the SCK signal unless their SS pin is asserted.
The master and slave are each capable of exchanging a character of data during a sequence
of NUMBITS clock cycles; see the NUMBITS field in the ESPI Mode Register (ESPI-
MODE) on page 197. In both master and slave ESPI devices, data is shifted on one edge of
the SCK and is sampled on the opposite edge where data is stable. SCK phase and polarity
is determined by the Phaseand Clkpolbits in the ESPI Control Register (ESPICTL) on
page 194.
PS022010-0811
P R E L I M I N A R Y
ESPI Signals
ZNEO® Z16F Series MCUs
Product Specification
179
Slave Select
The SS signal is a bidirectional framing signal with several modes of operation to support
SPI and other synchronous serial interface protocols. The SLAVE SELECT Mode is
selected by the SSMD field of the ESPI Mode Register. The direction of the SS signal is
controlled by the SSIO bit of the ESPI Mode Register. The SS signal is an input on slave
devices and is an output on the active master device. Slave devices ignore transactions on
the bus unless their slave select input is asserted. In SPI MASTER Mode, additional GPIO
pins are required to provide Slave Selects if there is more than one slave device.
ESPI Register Overview
The ESPI Control/Status Registers are summarized in Table 97. These registers are
accessed by either Word (16-bit) or Byte operations.
Table 97. ESPI Registers
Word Address
XXXXX0
Even Address
Data
Odd Address
Transmit Data Command
Mode
XXXXX2
Control
XXXXX4
Status
State
XXXXX6
Baud Rate High Baud Rate Low
Comparison with Basic SPI Block
The ESPI module includes many enhancements when compared to the simpler SPI mod-
ule in other Z8 Encore!® parts. This section highlights the differences between the ESPI
module and the SPI module as follows:
•
•
Transmit and receive data buffer register added to support higher performance.
Multiple interrupt sources (transmit data, receive data, errors). SPI module only has
data transfer complete interrupt.
•
•
•
DMA Controller interface (separate transmit and receive interfaces).
Register addresses redefined to facilitate 16-bit transfers on the ZNEO® Z16F Series.
Transmit data command register – new register to facilitate DMA interface and im-
prove performance with 16-bit transfers. SSV and TEOF is set on same cycle on which
the data register is written.
•
Control register:
– IRQE changed to DIRQE. This allows data interrupts to be disabled when using
DMA but still allow error interrupts.
PS022010-0811
P R E L I M I N A R Y
Slave Select
ZNEO® Z16F Series MCUs
Product Specification
180
– STR bit on the SPI module replaced with ESPIEN1. SPIEN replaced with
ESPIEN0. This enhancement allows unidirectional transfers which minimizes
software or DMA overhead.
– BIRQ replaced with BRGCTL.
•
Mode register:
– Added SSMD field which adds support for loop back and I2S modes.
– Moved SSV bit to the transmit data command register as described above.
– Added slave select polarity (SSPO) to support active High and Low slave select on
SS pin.
•
•
Status register:
– IRQ split into TDRE and RDRF (separate transmit and receive interrupts).
– Replace overrun error with separate transmit under-run and receive overrun.
State register.
– Replaced SCKEN bit with SCKI.
– Replaced TCKEN with SDI.
Operation
During transfer, data is sent and received simultaneously by both master and slave
devices. Separate signals are required to transmit data, receive data and the serial clock.
When a transfer occurs, a multibit (typically 8-bit) character is shifted out one data pin and
a multi-bit character is simultaneously shifted in on a second data pin. An 8-bit shift regis-
ter in the master and an 8-bit shift register in the slave is connected as a circular buffer.
The ESPI shift register is buffered to support back-to-back character transfers in high per-
formance applications.
A transaction is initiated when the Transmit Data Register is written in the master device.
The value from the data register is transferred into the shift register and the transaction
begins. After the transmit data is loaded into the shift register, the Transmit Data register
Empty (TDRE) status bit asserts, indicating that Transmit Data Register is written with the
next value. At the end of each character transfer, the shift register value (receive data) is
loaded into the Receive Data Register. At that point the Receive Data register Full (RDRF)
status bit asserts. When software or DMA reads the receive data from the Receive Data
Register, the RDRF signal deasserts.
The master sources the SCK and SS signal during the transfer.
Internal data movement (either by software or DMA) to/from the ESPI block is controlled
by the Transmit Data Register empty (TDRE) and Receive Data Register full (RDRF) sig-
nals. These signals are read only bits in the ESPI Status Register. When either the TDRE
or RDRF bits assert, an interrupt is sent to the interrupt controller if the data interrupt
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
181
request enable (DIRQE) bit is set. The TDRE and RDRF signals also generate transmit
and receive DMA requests.
In many cases the software application is only moving information in one direction. In
such a case, either the TDRE or RDRF interrupts/DMA requests is disabled to minimize
software/DMA overhead. Unidirectional data transfer is supported by setting the
ESPIEN1, 0 bits in the control register to 10or 01. If the DMA engine is being used to
move the data, the transmit and receive data interrupts are disabled through the DIRQE bit
of the control register. In this case error interrupts still occurs and must be handled directly
by the software.
Throughput
In MASTER Mode, the maximum supported SCK rate is one-half the system clock fre-
quency. This rate is achieved by programming the value 0001Hinto the baud rate high/
low register pair. Though each character is transferred at this rate, it is unlikely that soft-
ware interrupt routines or DMA keeps up with this rate. In SPI Mode, the transfer will
automatically pause between characters until the current receive character is read and the
next transmit data value is written.
In SLAVE Mode, the transfer rate is controlled by the master. As long as the TDRE and
RDRF interrupt or DMA requests are serviced before the next character transfer completes
the slave will keep up with the master. In SLAVE Mode, the baud rate is restricted to a
maximum of one-fourth of the system clock frequency to allow for synchronization of the
SCK input to the internal system clock.
ESPI Clock Phase and Polarity Control
The ESPI supports four combinations of SCK phase and polarity using two bits in the
ESPI Control Register. The clock polarity bit, CLKPOL, selects an active High or active
Low clock and has no effect on the transfer format. The clock phase bit, PHASE, selects
one of two fundamentally different transfer formats. The data is output a half-cycle before
the receive clock edge which provides a half cycle of setup and hold time. Table 98 lists
the ESPI clock phase and polarity operation parameters.
Table 98. ESPI Clock Phase (PHASE) and Clock Polarity (CLKPOL) Operation
SCK
Transmit
Edge
SCK
Receive
Edge
SCK Idle
State
PHASE
CLKPOL
0
0
1
1
0
1
0
1
Falling
Rising
Rising
Falling
Rising
Falling
Falling
Rising
Low
High
Low
High
PS022010-0811
P R E L I M I N A R Y
Throughput
ZNEO® Z16F Series MCUs
Product Specification
182
Transfer Format with Phase Equals Zero
Figure 36 displays the timing diagram for an SPI type transfer in which PHASE= 0. For
SPI transfers the clock only toggles during the character transfer. The two SCK wave-
forms show polarity with CLKPOL= 0and with CLKPOL= 1. The diagram is interpreted
as either a Master or Slave timing diagram as the SCK MISO and MOSI pins are directly
connected between the master and the slave.
SCK
(CLKPOL = 0)
SCK
(CLKPOL = 1)
MOSI
Bit7
Bit7
Bit6
Bit6
Bit5
Bit5
Bit4
Bit4
Bit3
Bit3
Bit2
Bit2
Bit1
Bit1
Bit0
Bit0
MISO
Input Sample Time
SS
Figure 36. ESPI Timing when PHASE = 0
Transfer Format with Phase Equals One
Figure 37 displays the timing diagram for an SPI type transfer in which PHASE=1. For
SPI transfers the clock only toggles during the character transfer. Two waveforms are
depicted for SCK, one for CLKPOL= 0and another for CLKPOL= 1.
PS022010-0811
P R E L I M I N A R Y
ESPI Clock Phase and Polarity Control
ZNEO® Z16F Series MCUs
Product Specification
183
SCK
(CLKPOL = 0)
SCK
(CLKPOL = 1)
MOSI
Bit7
Bit7
Bit6
Bit6
Bit5
Bit5
Bit4
Bit4
Bit3
Bit3
Bit2
Bit2
Bit1
Bit1
Bit0
Bit0
MISO
Input Sample Time
SS
Figure 37. ESPI Timing when PHASE = 1
Modes of Operation
This section describes the different modes of data transfer supported by the ESPI block.
The mode is selected by the SLAVE SELECT Mode (SSMD) field of the mode register.
SPI Mode
This mode is selected by setting the SSMD field of the mode register to 000. In this mode,
software or DMA controls the assertion of the SS signal directly via the SSV bit of the SPI
transmit data command register. Either DMA or software is used to control an SPI Mode
transaction. Prior to or simultaneously with writing the first transmit data byte, software or
DMA sets the SSV bit. Software sets the SSV bit either by performing a byte write to the
transmit data command register prior to writing the first transmit character to the data reg-
ister or by performing a word write to the data register address which loads the first trans-
mit character and simultaneously sets the SSV bit.
The DMA sets the SSV bit via the command field of the descriptor. The SSV bit is written
on the DMA command bus prior to or in sync with the first data byte. SS will remain
asserted while one or more characters are transferred. There are two mechanisms for deas-
serting SS at the end of the transaction. One method is used by DMA and also by software,
is to set the TEOFbit of the transmit data command register when the last TDRE interrupt
PS022010-0811
P R E L I M I N A R Y
Modes of Operation
ZNEO® Z16F Series MCUs
Product Specification
184
or DMA request is being serviced (set TEOF before or simultaneously with writing the
last data byte). When the last bit of the last character is transmitted, the hardware will
automatically deassert the SSV and TEOF bits. The second method is for software to
directly clear the SSV bit after the transaction completes. If software clears the SSV bit
directly, it is not necessary for software to also set the TEOF bit on the last transmit byte.
After writing the last transmit byte, the end of the transaction is detected by waiting for the
last RDRF interrupt or monitoring the TFST bit in the ESPI Status register.
The transmit underrun and receive overrun errors do not occur in an SPI Mode master. If
the RDRF and TDRE requests have not been serviced before the current byte transfer
completes, SCLK is paused until the data register is read and written. The transmit under-
run and receive overrun errors will occur in a slave if the slave’s software/DMA does not
keep up with the master data rate. If a transmit underrun occurs in SLAVE Mode, the shift
register in the slave is loaded with all 1s.
In the SPI Mode, the SCK is active only for the data transfer with one SCK period per bit
transferred. If the SPI bus has multiple slaves, the slave select lines to all or one of the
slaves must be controlled independently by software using GPIO pins.
Figure 38 displays multiple character transfer in SPI Mode. Note that while character ’n’
is being transferred using the shift register, software/DMA responds to the receive request
for character n-1 and the transmit request for character n+1.
PS022010-0811
P R E L I M I N A R Y
Modes of Operation
ZNEO® Z16F Series MCUs
Product Specification
185
SCK (SSMD = 00,
PHASE = 0,
CLKPOL = 0,
SSPO = 0)
Bit0
Bit7
Bit6
Bit1
Bit0
Bit7
Bit 6
MOSI, MISO
Rx Data Register
Empty
Tx n+1
empty
Tx n+2
Tx/Rx n+1
Rx n-1
Rx n
Tx n
Tx Data Register
Shift Register
Tx/Rx n-1
Tx/Rx n
TDRE
RDRF
ESPI Interrupt
Figure 38. SPI Mode (SSMD = 000)
I2S (Inter-IC Sound) Mode
This mode is selected by setting the SSMD field of the mode register to 010. The Phase
and Clkpolbits of the control register must be set to 0. This mode is illustrated in Fig-
ure 39 with SS alternating between consecutive frames. A frame consists of a fixed num-
ber of data bytes as defined in the DMA buffer descriptor or by software. I2S (Inter-IC
Sound) mode is typically used to transfer left or right channel audio data.
The SSV indicates whether the corresponding bytes are left or right channel data. The
SSV value must be updated when servicing the TDRE interrupt/request for the first byte in
a left or write channel frame. This update is accomplished by performing a word write
when writing the first byte of the audio word, which updates both the ESPI data and trans-
mit data command words or by doing a byte write to update SSV followed by a byte write
to the data register. The SS signal leads the data by one SCK period.
If a DMA Channel is controlling data transfer, each sequence of left (or right) channel byte
is considered a frame with a buffer descriptor. The SSV bit is defined in the buffer descrip-
tor command field and is automatically written to the transmit data command register just
prior to or in synchronous with the first data byte of the frame being written. Note that the
PS022010-0811
P R E L I M I N A R Y
Modes of Operation
ZNEO® Z16F Series MCUs
Product Specification
186
number of bits per frame is a value other than an integral number of 8-bits by setting
NUMBITS to a value other than 0.
Example. To send 20 bits/frame, set NUMBITS = 5 and read/write 4 bytes per frame. The
transmit data must be left justified and the receive data must be right justified.
The transaction is terminated when the master has no more data to transmit. After the last
bit is transferred, SCLK stops and SS and SSV returns to their default states. If TEOF is
not set on the last byte, a transmit underrun error occurs at this point.
SCK (SSMD = 010,
PHASE = 0,
CLKPOL = 0)
SS
(SSPO = 0)
SSV=0
Bit7
SSV=1
Bit7
Bit0
Bit 7
MOSI, MISO
Bit0
frame n
(may be multiple
bytes)
frame n + 1
2
Figure 39. I S Mode (SSMD = 010)
SPI Protocol Configuration
This section describes in detail how to configure the ESPI block for the SPI protocol. In
the SPI protocol the master sources the SCK and asserts slave select signals to one or more
slaves. The slave select signals are typically active Low.
SPI Master Operation
The ESPI block is configured for MASTER Mode operation by setting the MMENbit = 1in
the ESPICTL Register. The SSMD field of the ESPI Mode register is set to 000 for SPI
protocol mode. The Phase, Clkpoland Worbits in the ESPICTL Register and the
NUMBITS field in the ESPI Mode Register must be consistent with the Slave SPI devices.
Typically for an SPI master SSIO=1and SSPO=0. The appropriate GPIO pins are con-
figured for the ESPI alternate function on the MOSI, MISO and SCK pins. The GPIO for
the ESPI SS pin is configured in alternate function mode as well though software uses any
GPIO pin(s) to drive one or more slave select lines. If the ESPI SS signal is not used to
PS022010-0811
P R E L I M I N A R Y
SPI Protocol Configuration
ZNEO® Z16F Series MCUs
Product Specification
187
drive a slave select the SSIO bit must still be set to 1 in a single master system. Figure 40
and Figure 41 displays the ESPI block configured as an SPI master.
ESPI Master
To Slave’s SS Pin
From Slave
SS
8-bit Shift Register
Bit 0 Bit 7
MISO
MOSI
SCK
To Slave
To Slave
Baud Rate
Generator
Figure 40. ESPI Configured as an SPI Master in a Single Master, Single Slave System
ESPI Master
To Slave #2’s SS Pin
To Slave #1’s SS Pin
GPIO
GPIO
8-bit Shift Register
Bit 0 Bit 7
From Slaves
To Slaves
MISO
MOSI
Baud Rate
Generator
SCK
To Slaves
Figure 41. ESPI Configured as an SPI Master in a Single Master, Multiple Slave System
PS022010-0811
P R E L I M I N A R Y
SPI Protocol Configuration
ZNEO® Z16F Series MCUs
Product Specification
188
Multi-Master SPI Operation
In a multi-master SPI system, all SCK pins are tied together, all MOSI pins are tied
together and all MISO pins are tied together. All SPI pins must be configured in open-
drain mode to prevent bus contention. At any time, only one SPI device is configured as
the master and all other devices on the bus are configured as slaves. The master asserts the
SS pin on the selected slave. Then, the active master drives the clock and transmit data on
the SCK and MOSI pins to the SCK and MOSI pins on the slave (including those slaves
which are not enabled). The enabled slave drives data out its MISO pin to the MISO mas-
ter pin.
When the ESPI is configured as a master in a multi-master SPI system, the SS pin must be
configured as an input. The SS input signal on a device configured as a master must
remain High. If the SS signal on the active master goes Low (indicating another master is
accessing this device as a slave), a collision error flag is set in the ESPI Status Register.
The slave select outputs on a master in a multi-master system must come from GPIO pins.
SPI Slave Operation
The ESPI block is configured for SLAVE Mode operation by setting the MMEN bit = 0 in
the ESPICTL Register and setting the SSIObit =0in the ESPIMODE Register. The
SSMD field of the ESPI Mode Register is set to 00 for SPI protocol mode. The Phase,
Clkpoland WORbits in the ESPICTL Register and the NUMBITS field in the ESPI-
MODE Register must be set to be consistent with the other SPI devices. Typically for an
SPI slave SSPO = 0.
If the slave has data to send to the master, the data must be written to the data register
before the transaction starts (first edge of SCK when SS is asserted). If the data register is
not written prior to the slave transaction, the MISO pin outputs all 1s.
Due to the delay resulting from synchronization of the SS and SCK input signals to the
internal system clock, the maximum SCK baud rate which is supported in SLAVE Mode is
the system clock frequency divided by 8. This rate is controlled by the SPI master.
Figure 42 displays the ESPI configuration in SPI SLAVE Mode.
PS022010-0811
P R E L I M I N A R Y
SPI Protocol Configuration
ZNEO® Z16F Series MCUs
Product Specification
189
SPI Slave
From Master
SS
8-bit Shift Register
MISO
MOSI
To Master
Bit 7
Bit 0
From Master
SCK
From Master
Figure 42. ESPI Configured as an SPI Slave
Error Detection
Error events detected by the ESPI block are described in this section. Error events gener-
ate an ESPI interrupt and set a bit in the ESPI Status Register. The error bits of the ESPI
Status register are read/write 1 to clear.
Transmit Underrun
A transmit underrun error occurs for a master with SSMD = 10 or 11 when a character
transfer completes and TDRE = 1. In these modes when a transmit underrun occurs the
transfer is aborted (SCK will halt and SSV will be deasserted). For a master in SPI Mode
(SSMD=00), a transmit underrun is not signaled because SCK will pause and wait for the
data register to be written.
In SLAVE Mode, a transmit underrun error occurs if TDRE = 1 at the start of a transfer.
When a transmit underrun occurs in SLAVE Mode, ESPI transmits a character of all 1s.
A transmit underrun sets the TUNDbit in the ESPI Status Register to 1. Writing 1 to TUND
clears this error flag.
Mode Fault (Multi-Master Collision)
A mode fault indicates when more than one master is trying to communicate at the same
time (a multi-master collision) in SPI Mode. The mode fault is detected when the enabled
master’s SS input pin is asserted. For this to happen the control and mode registers must
be configured with MMEN = 1, SSIO = 0 (SS is an input) and SS input = 0. A mode fault
sets the COLbit in the ESPI Status Register to 1. Writing a 1 to COLclears this error flag.
PS022010-0811
P R E L I M I N A R Y
Error Detection
ZNEO® Z16F Series MCUs
Product Specification
190
Receive Overrun
A receive overrun error occurs when a transfer completes and the RDRF bit is still set
from the previous transfer. A receive overrun sets the ROVR bit in the ESPI Status Regis-
ter to 1. Writing 1 to ROVR clears this error flag. The Receive Data Register is not over-
written and will contain the data from the transfer which initially set the RDRF bit.
Subsequent received data is lost until the RDRF bit is cleared.
Slave Mode Abort
In SLAVE Mode of operation if the SS pin deasserts before all bits in a character have
been transferred, the transaction is aborted. When this condition occurs the ABT bit is set
in the ESPI Status register. A slave abort error resets the slave control logic to the idle
state.
A slave abort error is also asserted in SLAVE Mode, if BRGCTL=1and a BRG time-out
occurs. When BRGCTL=1is in SLAVE Mode, it functions as a WDT monitoring the SCK
signal. The BRG counter is reloaded every time a transition on SCK occurs while SS is
asserted. The baud rate reload registers must be programmed with a value longer than the
expected time between SS assertion and the first SCK edge, between SCK transitions
while SS is asserted and between the last SCK edge and SS deassertion. A time-out indi-
cates the master is stalled or disabled. Writing 1 to ABT clears this error flag.
ESPI Interrupts
ESPI has a single interrupt output which is asserted when any of the TDRE, TUND, COL,
ABT, ROVR, or RDRFbits are set in the ESPI Status Register. The interrupt is a pulse (dura-
tion of one system clock) generated when any one of the source bits initially set. The
TDRE and RDRF interrupts are enabled/disabled through the Data Interrupt Request
Enable (DIRQE) bit of the ESPI Control Register.
A transmit interrupt is asserted by the TDREstatus bit when the ESPI block is enabled and
the DIRQEbit is set. The TDREbit in the status register is cleared automatically when the
Transmit Data Register is written or the ESPI block is disabled. When the Transmit Data
register value is loaded into the shift register to start a new transfer, the TDRE bit will be
set again causing a new transmit interrupt. If information is being received but not trans-
mitted the transmit interrupts are eliminated by selecting RECEIVE ONLY Mode
(ESPIEN1,0=01). A master operates in Receive Only mode; however, a write to the
ESPI (Transmit) Data Register is still required to initiate the transfer of a character.
A receive interrupt is generated by the RDRF status bit when the ESPI block is enabled;
the DIRQEbit is set and a character transfer completes. At the end of the character transfer,
the contents of the shift register is transferred into the Receive Data register, causing the
RDRFbit to assert. The RDRFbit is cleared when the Receive Data register is read. If infor-
mation is being transmitted but not received by the software application, the receive inter-
PS022010-0811
P R E L I M I N A R Y
ESPI Interrupts
ZNEO® Z16F Series MCUs
Product Specification
191
rupt is eliminated by selecting Transmit Only mode (ESPIEN1,0=10) in either
MASTER or SLAVE modes.
ESPI error interrupts occur if any of the TUND, COL, ABTand ROVRbits in the ESPI Status
register are set. These bits are cleared by writing a 1 to the corresponding bit.
If the ESPI is disabled (ESPIEN1,0=00), an ESPI interrupt is generated by a BRG time-
out. This timer function must be enabled by setting the BRGCTLbit in the ESPICTL Regis-
ter. This timer interrupt does not set any of the bits of the ESPI Status register.
DMA Interface
The assertion of the TDRE and RDRF signals generate transmit and receive DMA
requests (SPITxReq, SPIRxReq), allowing data movement to be handled by a DMA Con-
troller rather than directly by software. The DMA acknowledges these requests through
the SPITxAck and SPIRxAck signals). Inputs allow the SSVand TEOFbits of the Transmit
Data Command register to be controlled by the DMA. The SPITxReqEOF and
SPIRxReqEOF outputs to the DMA provides an indication that SS has deasserted (trans-
action complete).
If the software application is moving data in only one direction, the ESPIEN1,0bits are
set to 10 or 01, allowing a single DMA Channel to control the ESPI data transfer. For a
master, the valid options are transmit only or transmit-receive. For a slave, all options are
valid. When a slave is operating in RECEIVE ONLY Mode, it will transmit characters of
all 1s.
DMA Descriptors
For ESPI Transmit DMA descriptors, the 4-bit CMDSTATfield of the descriptor is in the
format shown in Table 99. The SSV bit in the Master’s transmit buffer descriptor CMD-
STATfield controls the ESPI SS output. The SSV bit in the descriptor is transferred to the
SSV bit in the ESPI Data Command register with the first byte of the buffer. If the EOF bit
is set in the DMA descriptor control word, the end of frame signal from the DMA (EOF-
Sync) will assert coincident with writing the last byte in the buffer to the ESPI Data regis-
ter, setting the TEOF bit of the ESPI Data Command register. After this last byte has been
transferred, the Master’s SS output will deassert and the SSV and TEOF bits in the Data
Command register will be cleared. The CMDSTATfield in ESPI Receive DMA Descriptors
has no function.
Table 99. ESPI Tx DMA Descriptor Command Field
Reserved
Reserved
Reserved
SSV
For ESPI DMA descriptors, the 4-bit frame status field of the descriptor has the format
shown in Tables 100 and 101.
PS022010-0811
P R E L I M I N A R Y
DMA Interface
ZNEO® Z16F Series MCUs
Product Specification
192
Table 100. ESPI Tx DMA Descriptor Status Field
COL TUND
0
0
Table 101. ESPI Rx DMA Descriptor Status Field
RSS ABT ROVR
0
In Table 101, RSS is the value of SS associated with the last byte written. This value is
useful in I2S Mode to distinquish left/right channel data. For a description of the COL,
TUND, ABT and ROVR bits listed in the above tables, see the ESPI Status Register
(ESPISTAT) on page 198.
ESPI Baud Rate Generator
In ESPI MASTER Mode, the BRG creates a lower frequency serial clock (SCK) for data
transmission synchronization between the Master and the external Slave. The input to the
BRG is the system clock. The ESPI Baud Rate High and Low Byte registers combine to
form a 16-bit reload value, BRG[15:0], for the ESPI BRG. The ESPI baud rate is calcu-
lated using the following equation:
System Clock Frequency (Hz)
------------------------------------------------------------------------
SPI Baud Rate (bps) =
2 BRG[15:0]
Minimum baud rate is obtained by setting BRG[15:0] to 0000H for a clock divisor value
of (2 x 65536 = 131072).
When the ESPI is disabled, the BRG functions as a basic 16-bit timer with interrupt on
time-out. Observe the following steps to configure the BRG as a timer with interrupt on
time-out:
1. Disable the ESPI by clearing the ESPIEN1,0 bits in the ESPI Control register.
2. Load the appropriate 16-bit count value into the ESPI Baud Rate High and Low Byte
registers.
3. Enable the BRG timer function and associated interrupt by setting the BRGCTL bit in
the ESPI Control register to 1.
When configured as a general purpose timer, the SPI BRG interrupt interval is calculated
using the following equation:
SPI BRG Interrupt Interval (s) = System Clock Period (s) BRG[15:0]
PS022010-0811
P R E L I M I N A R Y
ESPI Baud Rate Generator
ZNEO® Z16F Series MCUs
Product Specification
193
ESPI Control Register Definitions
ESPI Data Register
The ESPI Data Register, shown in Table 102, addresses both the outgoing Transmit Data
register and the incoming Receive Data register. Reads from the ESPI Data register return
the contents of the Receive Data register. The Receive Data register is updated with the
contents of the shift register at the end of each transfer. Writes to the ESPI Data register
load the Transmit Data register unless TDRE=0. Data is shifted out starting with bit 7. The
last bit received resides in bit position 0.
With the ESPI configured as a Master, writing a data byte to this register initiates the data
transmission. With the ESPI configured as a Slave, writing a data byte to this register
loads the shift register in preparation for the next data transfer with the external Master. In
either the Master or Slave modes, if TDRE = 0, writes to this register are ignored.
When the character length is less than 8 bits (as set by the NUMBITSfield in the ESPI
Mode register), the transmit character must be left justified in the ESPI Data register. A
received character of less than 8 bits is right justified (last bit received is in bit position 0).
For example, if the ESPI is configured for 4-bit characters, the transmit characters must be
written to ESPIDATA[7:4] and the received characters are read from ESPIDATA[3:0].
Table 102. ESPI Data Register (ESPIDATA)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DATA
X
X
X
X
X
X
X
X
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E260H
Bit
Description
Data
[7:0]
DATA
Transmit and/or receive data. Writes to the ESPIDATA Register load the shift register. Reads
from the ESPIDATA Register return the value of the Receive Data Register.
ESPI Transmit Data Command Register
The ESPI Transmit Data Command Register, shown in Table 103, provides control of the
SS pin when it is configured as an output (MASTER Mode). The TEOF and SSV bits are
controlled by the DMA interface as well as by a bus write to this register.
PS022010-0811
P R E L I M I N A R Y
ESPI Control Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
194
Table 103. ESPI Transmit Data Command Register (ESPITDCR)
Bits
7
6
5
4
3
2
1
TEOF
0
0
Field
RESET
R/W
Reserved
SSV
0
0
0
0
0
0
0
R
R
R
R
R
R
R/W
R/W
Addr
FF_E261H
Bit
Description
Reserved
[7:2]
These bits are reserved and are read-only.
[1]
TEOF
Transmit End of Frame
This bit is used in Master Mode to indicate that the data in the Transmit Data Register is the
last byte of the transfer or frame. When the last byte has been sent SS (and SSV) change state
and TEOF automatically clears.
0 = The data in the Transmit Data Register is not the last character in the message.
1 = The data in the Transmit Data Register is the last character in the message.
[0]
SSV
Slave Select Value
When SSIO = 1, writes to this register controls the value output on the SS pin. See the SSMD
field of the ESPI Mode Register section on page 197 for more details.
ESPI Control Register
The ESPI Control Register, shown in Table 104, configures the ESPI for transmit and
receive operations.
Table 104. ESPI Control Register (ESPICTL)
Bits
7
DIRQE
0
6
5
4
PHASE
0
3
CLKPOL
0
2
WOR
0
1
MMEN
0
0
ESPIEN0
0
Field
RESET
R/W
ESPIEN1 BRGCTL
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E262H
PS022010-0811
P R E L I M I N A R Y
ESPI Control Register
ZNEO® Z16F Series MCUs
Product Specification
195
Bit
Description
[7]
DIRQE
Data Interrupt Request Enable
This bit is used to disable or enable data (TDRE and RDRF) interrupts. Disabling the data
interrupts is required when controlling data transfer by DMA or polling. Error interrupts are
not disabled. To block all ESPI interrupt sources, clear the ESPI interrupt enable bit in the
Interrupt Controller.
0 = TDRE and RDRF assertions do not cause an interrupt. Use this setting if controlling data
transfer through DMA or by software polling of TDRE and RDRF. The TUND, COL, ABT
and ROVRbits cause an interrupt.
1 = TDRE and RDRF assertions will cause an interrupt. TUND, COL, ABT and ROVR will
also cause interrupts. Use this setting if controlling data transfer through interrupt han-
dlers.
[6,0]
ESPIEN1,
ESPIEN0
ESPI Enable and Direction Control
00 = ESPI block is disabled. BRG is used as a general purpose timer by setting BRGCTL =
1.
01 = RECEIVE ONLY Mode. Use this setting if the software application is receiving data but
not sending. The TDRE asserts; however, the transmit interrupt and DMA requests do
not assert. In SLAVE Mode, the transmitted data will be all 1s. In MASTER Mode soft-
ware must still write to the Transmit Data register to initiate the transfer.
10 = TRANSMIT ONLY Mode. Use this setting in MASTER or SLAVE Mode when the soft-
ware application is sending data but not receiving. RDRF will assert, but receive inter-
rupt and DMA requests do not occur.
11 = TRANSMIT/RECEIVE Mode. Use this setting if the software application is both sending
and receiving information. Both TDRE and RDRF will be active.
[5]
BRGCTL
Baud Rate Generator Control
The function of this bit depends upon ESPIEN1,0. When ESPIEN1,0 = 00, this bit allows
enabling the BRG to provide periodic interrupts.
If the ESPI is disabled (ESPIEN1,ESPIEN0=00):
0 = The BRG timer function is disabled. Reading the Baud Rate High and Low registers
returns the BRG reload value.
1 = The BRG timer function and time-out interrupt are enabled. Reading the Baud Rate High
and Low registers returns the BRG Counter value.
If the ESPI is enabled:
0 = Reading the Baud Rate High and Low registers returns the BRG reload value. If MMEN=
1, the BRG is enabled to generate SCK. If MMEN=0, the BRG is disabled.
1 = Reading the Baud Rate High and Low registers returns the BRG Counter value. If MMEN
=1, the BRG is enabled to generate SCK. If MMEN=0, the BRG is enabled to provide a
Slave SCK time-out. See the Slave Mode Abort section on page 190 for further details.
[4]
PHASE
Phase Select
Sets the phase relationship of the data to the clock. For more information about operation of
the PHASEbit, see the ESPI Clock Phase and Polarity Control section on page 181.
[3]
CLKPOL
Clock Polarity
0 = SCK idles Low (0).
1 = SCK idles High (1).
PS022010-0811
P R E L I M I N A R Y
ESPI Control Register
ZNEO® Z16F Series MCUs
Product Specification
196
Bit
Description (Continued)
[2]
WOR
Wire-OR (Open-Drain) Mode Enabled
0 = ESPI signal pins not configured for open-drain.
1 = All four ESPI signal pins (SCK, SS, MISO, MOSI) configured for open-drain function.
This setting is used for Multi-Master and/or Multi-Slave configurations.
[1]
MMEN
ESPI Master Mode Enable
This bit controls the data I/O pin selection and SCK direction.
0 = Data-out on MISO, data-in on MOSI (used in SPI Slave Mode), SCK is an input.
1 = Data-out on MOSI, data-in on MISO (used in SPI Master Mode), SCK is an output.
If reading the counter one byte at a time while the BRG is counting keep in mind that the
values will not be in sync. It is recommended to read the counter using word (2-byte)
reads.
Caution:
PS022010-0811
P R E L I M I N A R Y
ESPI Control Register
ZNEO® Z16F Series MCUs
Product Specification
197
ESPI Mode Register
The ESPI Mode Register, shown in Table 105, configures the character bit width and
mode of the ESPI I/O pins.
Table 105. ESPI Mode Register (ESPIMODE)
Bits
7
6
5
4
3
NUMBITS[2:0]
000
2
1
SSIO
0
0
SSPO
0
Field
RESET
R/W
SSMD
000
R/W
R/W
R/W
R/W
Addr
FF_E263H
Bit
Description
SLAVE SELECT Mode
[7:5]
SSMD
This field selects the behavior of SS as a framing signal. For a detailed description of
these modes, see the Slave Select section on page 179.
000 = SPI Mode
When SSIO = 1, the SS pin is driven directly from the SSV bit in the Transmit Data Com-
mand register. The Master software or DMA must set SSV (or a GPIO output if the SS pin
is not connected to the appropriate Slave) to the asserted state prior to or on the same
clock cycle with which the Transmit Data Register is written with the initial byte.
At the end of a frame (after the last RDRF event), SSV is deasserted by software. Alter-
natively, SSV is automatically deasserted by hardware if the TEOF bit in the Transmit
Data Command register is set when the last transmit byte is loaded. In SPI Mode, SCK is
active only for data transfer (one clock cycle per bit transferred).
001 = LOOPBACK Mode
When ESPI is configured as Master (MMEN = 1) the outputs are deasserted and data is
looped from shift register out to shift register in. When ESPI is configured as a Slave
(MMEN = 0) and SS in asserts, MISO (Slave output) is tied to MOSI (Slave input) to pro-
vide an a remote loop back (echo) function.
2
010 = I S Mode
In this mode, the value from SSV will be output by the Master on the SS pin one SCK
period before the data and will remain in that state until the start of the next frame. Typi-
cally this mode is used to send back-to-back frames with SS alternating on each frame. A
frame boundary is indicated in the Master when SSV changes. A frame boundary is
detected in the Slave by SS changing state. The SS framing signal will lead the frame by
one SCK period. In this mode SCK will run continuously, starting with the initial SS asser-
tion. Frames will run back-to-back as long as software/DMA continue to provide data. The
2
I S protocol (Inter IC Sound) is used to carry left and right channel audio data with the SS
signal indicating which channel is being sent. In Slave Mode, the change in state of SS
(Low to High or High to Low) will trigger the start of a transaction on the next SCK cycle.
PS022010-0811
P R E L I M I N A R Y
ESPI Mode Register
ZNEO® Z16F Series MCUs
Product Specification
198
Bit
Description (Continued)
[4:2]
Number of Data Bits Per Character to Transfer
NUMBITS[2:0] This field contains the number of bits to shift for each character transfer. For information
about valid bit positions when the character length is less than 8-bits, see the ESPI Data
Register section on page 193.
000 = 8 bits
001 = 1 bit
010 = 2 bits
011 = 3 bits
100 = 4 bits
101 = 5 bits
110 = 6 bits
111 = 7 bits
[1]
SSIO
Slave Select I/O
This bit controls the direction of the SS pin. In single Master Mode, SSIO is set to 1
unless a separate GPIO pin is being used to provide the SS output function. In the SPI
Slave or Multi-Master configuration SSIO is set to 0.
0 = SS pin configured as an input (SPI Slave and Multi-Master modes)
1 = SS pin configured as an output (SPI single Master Mode)
[0]
SSPO
Slave Select Polarity
This bit controls the polarity of the SS pin.
0 = SS is active Low. (SSV = 1 corresponds to SS = 0)
1 = SS is active High. (SSV = 1 corresponds to SS = 1)
ESPI Status Register
The ESPI Status Register, shown in Table 106, indicates the current state of the ESPI. All
bits revert to their Reset state, if the ESPI is disabled.
Table 106. ESPI Status Register (ESPISTAT)
Bits
7
TDRE
0
6
5
4
ABT
0
3
ROVR
0
2
RDRF
0
1
TFST
0
0
SLAS
1
Field
RESET
R/W
TUND
0
COL
0
R
R/W*
R/W*
R/W*
R/W*
R
R
R
Addr
FF_E264H
R/W* = Read access. Write a 1 to clear the bit to 0.
Bit
Description
[7]
TDRE
Transmit Data Register Empty
0 = Transmit Data Register is full or ESPI is disabled.
1 = Transmit Data Register is empty. A write to the ESPI (Transmit) Data register clears this bit.
PS022010-0811
P R E L I M I N A R Y
ESPI Status Register
ZNEO® Z16F Series MCUs
Product Specification
199
Bit
Description (Continued)
[6]
TUND
Transmit Underrun
0 = A Transmit Underrun error has not occurred.
1 = A Transmit Underrun error has occurred.
[5]
COL
Collision
0 = A Multi-Master collision (mode fault) has not occurred.
1 = A Multi-Master collision (mode fault) has been detected.
[4]
ABT
Slave Mode Transaction Abort
This bit is set if the ESPI is configured in Slave Mode, a transaction is occurring and SS deas-
serts before all bits of a character have been transferred as defined by the NUMBITS field of
the ESPIMODE Register. This bit is also be set in Slave Mode by an SCK monitor time-out
(MMEN = 0, BRGCTL = 1).
0 = A Slave Mode transaction abort has not occurred.
1 = A Slave Mode transaction abort has been detected.
[3]
ROVR
Receive Overrun
0 = A Receive Overrun error has not occurred.
1 = A Receive Overrun error has occurred.
[2]
RDRF
Receive Data Register Full
0 = Receive Data register is empty.
1 = Receive Data register is full. A read from the ESPI (Receive) Data register clears this bit.
[1]
TFST
Transfer Status
0 = No data transfer is currently in progress.
1 = Data transfer is currently in progress.
[0]
SLAS
Slave Select
Reading this bit returns the current value of the SS exclusive-OR’d with the SSPO bit.
0 = SS pin is Low, if SSPO = 0, SS pin is High if SSPO = 1 (SS is asserted).
1 = SS pin is High, if SSPO = 0, SS pin is Low if SSPO = 1 (SS is deasserted).
PS022010-0811
P R E L I M I N A R Y
ESPI Status Register
ZNEO® Z16F Series MCUs
Product Specification
200
ESPI State Register
The ESPI State Register, shown in Table 107, provides observability of the ESPI clock,
data and internal state. Table 108 describes the ESPI State Machine values.
Table 107. ESPI State Register (ESPISTATE)
Bits
7
SCKI
0
6
SDI
0
5
4
3
2
1
0
Field
RESET
R/W
ESPISTATE
0
R
R
R
Addr
FF_E265H
Bit
Description
[7]
SCKI
Serial Clock Input
This bit reflects the state of the serial clock pin.
0 = The SCK input pin is Low
1 = The SCK input pin is High
[6]
SDI
Serial Data Input
This bit reflects the state of the serial data input (MOSI or MISO depending on the MMENbit).
0 = The serial data input pin is Low.
1 = The serial data input pin is High.
[5:0]
ESPI State Machine
ESPISTATE Indicates the current state of the internal ESPI State Machine. This information is intended
for manufacturing test. The state values may change in future hardware revisions and are
not intended to be used by a software driver. Table 108 defines the valid states.
Table 108. ESPISTATE Values and Description
ESPISTATE Value Description
00_0000
00_0001
00_0010
00_0011
01_0000
11_0001
11_0010
10_1110
10_1111
10_1100
Idle
Slave Wait For SCK
I2S Slave Mode start delay
I2S Slave Mode start delay
SPI Master Mode start delay
I2S Master Mode start delay
I2S Master Mode start delay
Bit 7 Receive
Bit 7 Transmit
Bit 6 Receive
PS022010-0811
P R E L I M I N A R Y
ESPI State Register
ZNEO® Z16F Series MCUs
Product Specification
201
Table 108. ESPISTATE Values and Description (Continued)
ESPISTATE Value Description
10_1101
10_1010
10_1011
10_1000
10_1001
10_0110
10_0111
10_0100
10_0101
10_0010
10_0011
10_0000
10_0001
Bit 6 Transmit
Bit 5 Receive
Bit 5 Transmit
Bit 4 Receive
Bit 4 Transmit
Bit 3 Receive
Bit 3 Transmit
Bit 2 Receive
Bit 2 Transmit
Bit 1 Receive
Bit 1 Transmit
Bit 0 Receive
Bit 0 Transmit
ESPI Baud Rate High and Low Byte Registers
The ESPI Baud Rate High and Low Byte registers, shown in Tables 109 and 110, combine
to form a 16-bit reload value, BRG[15:0], for the ESPI Baud Rate Generator. The ESPI
baud rate is calculated using the following equation:
System Clock Frequency (Hz)
------------------------------------------------------------------------
SPI Baud Rate (bps) =
2 BRG[15:0]
Minimum baud rate is obtained by setting BRG[15:0] to 0000Hfor a clock divisor value
of (2 x 65536 = 131072)
When the ESPI function is disabled, the BRG functions as a basic 16-bit timer with inter-
rupt on time-out.
Observe the following procedure to configure the BRG as a general purpose timer with
interrupt on time-out:
1. Disable the ESPI by setting ESPIEN[1:0]=00in the SPI Control register.
2. Load the appropriate 16-bit count value into the ESPI Baud Rate High and Low Byte
registers.
3. Enable the BRG timer function and associated interrupt by setting the BRGCTLbit in
the ESPI Control register to 1.
PS022010-0811
P R E L I M I N A R Y
ESPI Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
202
When configured as a general purpose timer, the SPI BRG interrupt interval is calculated
using the following equation:
SPI BRG Interrupt Interval (s) = System Clock Period (s) BRG[15:0]
Table 109. ESPI Baud Rate High Byte Register (ESPIBRH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BRH
1
1
1
1
1
1
1
1
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E266H
Bit
Description
[7:0]
BRH
ESPI Baud Rate High Byte
Most significant byte, BRG[15:8], of the ESPI Baud Rate Generator’s reload value.
Table 110. ESPI Baud Rate Low Byte Register (ESPIBRL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BRL
1
1
1
1
1
1
1
1
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/w
Addr
FF_E267H
Bit
Description
[7:0]
BRL
ESPI Baud Rate Low Byte
Least significant byte, BRG[7:0], of the ESPI Baud Rate Generator’s reload value.
PS022010-0811
P R E L I M I N A R Y
ESPI Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
203
2
I C Master/Slave Controller
The I2C Master/Slave Controller makes the ZNEO® Z16F Series bus compatible with the
I2C protocol. The I2C bus consists of the serial data signal (SDA) and a serial clock (SCL)
signal bidirectional lines.
Features of the I2C Controller include:
•
•
•
•
•
•
•
Operates in MASTER/SLAVE or SLAVE ONLY modes
Supports arbitration in a Multi-Master environment (MASTER/SLAVE Mode)
Supports data rates up to 400 kbps
7-bit or 10-bit Slave address recognition (interrupt only on address match)
Optional general call address recognition
Optional digital filter on receive SDA and SCL lines
Optional interactive receive mode allows software interpretation of each received
address and/or data byte before acknowledging
•
•
Unrestricted number of data bytes per transfer
Baud Rate Generator (BRG) is used as a general purpose timer with interrupt if the I2C
controller is disabled
Architecture
Figure 43 displays the architecture of the I2C Controller.
PS022010-0811
P R E L I M I N A R Y
I2C Master/Slave Controller
ZNEO® Z16F Series MCUs
Product Specification
204
SDA
SCL
Shift
SHIFT
Load
I2CDATA
Baud Rate Generator
I2CBRH
I2CBRL
Tx/Rx State Machine
I2CISTAT
I2CSTATE
I2CCTL
I2CMODE
I2CSLVAD
2
I C Interrupt
Tx and Rx DMA Requests
Register Bus
2
Figure 43. I C Controller Block Diagram
PS022010-0811
P R E L I M I N A R Y
Architecture
ZNEO® Z16F Series MCUs
Product Specification
205
I2C Master/Slave Controller Registers
Table 111 summarizes the I2C Master/Slave Controller software-accessible registers.
2
Table 111. I C Master/Slave Controller Registers
Name
Abbreviation Description
2
I C Data
I2CDATA
I2CISTAT
I2CCTL
Transmit/Receive Data Register.
2
I C Interrupt Status
Interrupt Status Register.
2
I C Control
Control Register–basic control functions.
High byte of baud rate generator initialization value.
Low byte of baud rate generator initialization value.
State Register.
2
I C Baud Rate High
I2CBRH
I2CBRL
2
I C Baud Rate Low
2
I C State
I2CSTATE
I2CMODE
2
I C Mode
Selects MASTER or SLAVE modes, 7-bit or 10-Bit Address.
Configure address recognition, Defines Slave Address bits [9:8].
2
I C Slave Address
I2CSLVAD
Defines Slave Address bits [7:0]
Comparison with Master Mode only I2C Controller
Porting code written for the Master-only I2C Controller found on other Z8 Encore!® parts
to the I2C Master/Slave Controller is straightforward. The I2CDATA, I2CCTL, I2CBRH
and I2CBRL Register definitions are not changed.
The differences between the Master-only I2C Controller and I2C Master/Slave Controller
designs are:
•
•
•
The Status Register (I2CSTATE) from the Master-only I2C Controller is split into the
Interrupt Status (I2CISTAT) Register and the State (I2CSTATE) Register because there
are more interrupt sources. The ACK, 10B, TAS(now called AS) and DSS(now called
DS) bits formerly in the status register are moved to the state register.
The I2CSTATE Register is called as I2CDST (Diagnostic State) Register in the MAS-
TER ONLY Mode version. The I2CDST Register provided diagnostic information.
The I2CSTATE Register contains status and state information that are useful to soft-
ware in operational mode.
The I2CMODE Register is called as I2CDIAG (Diagnostic Control) Register in the
MASTER ONLY Mode version. The I2CMODE Register provides control for SLAVE
modes of operation as well as the most significant two bits of the 10-bit Slave address.
•
•
The I2CSLVAD Register is added for programming the Slave address.
The ACKV bit in the I2CSTATE Register enables the Master to verify the acknowledge
from the Slave before sending the next byte.
2
PS022010-0811
P R E L I M I N A R Y
I C Master/Slave Controller Registers
ZNEO® Z16F Series MCUs
Product Specification
206
•
Support for multi-master environments. If arbitration is lost when operating as a Mas-
ter, the ARBLST bit in the I2CISTAT Register is set and the mode automatically
switches to Slave Mode.
Operation
The I2C Master/Slave Controller operates in either SLAVE ONLY Mode or MASTER/
SLAVE Mode with Master arbitration. In MASTER/SLAVE Mode, it is used as the only
Master on the bus or as one of several Masters on the bus with arbitration. In a multi-Mas-
ter environment, the controller switches from MASTER to SLAVE Mode on losing arbi-
tration.
Though slave operation is fully supported in MASTER/SLAVE Mode, if a device is
intended to operate only as a slave, the SLAVE ONLY Mode is selected. In SLAVE ONLY
Mode, the device does not initiate a transaction even if software inadvertently sets the
START bit.
SDA and SCL Signals
I2C sends all addresses, data and acknowledge signals over the SDA line, the most-signif-
icant bit first. SCL is the clock for the I2C bus. When the SDA and SCL pin alternate func-
tions are selected for their respective GPIO ports, the pins are automatically configured for
open-drain operation.
The Master is responsible for driving the SCL clock signal. During the Low period of the
clock, a Slave holds the SCL signal Low to suspend the transaction if it is not ready to pro-
ceed. The Master releases the clock at the end of the Low period and notices that the clock
remains Low instead of returning to a High level. When the Slave releases the clock, the
I2C Master continues the transaction. All data is transferred in bytes and there is no limit
to the amount of data transferred in one operation. When transmitting address, data or
acknowledge, the SDA signal changes in the middle of the Low period of SCL. When
receiving address, data, or acknowledge, the SDA signal is sampled in the middle of the
High period of SCL.
A low-pass digital filter is applied to the SDA and SCL receive signals by setting the filter
enable (FILTEN) bit in the I2C Control Register. When the filter is enabled, any glitch,
which is less than a system clock period in width is rejected. This filter must be enabled
when running in I2C Fast Mode (400 kbps) and is also used at lower data rates.
I2C Interrupts
The I2C Controller contains multiple interrupt sources that are combined into one interrupt
request signal to the interrupt controller. If the I2C Controller is enabled, the source of the
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
207
interrupt is determined by bits, which are set in the I2CISTAT Register. If the I2C Control-
ler is disabled, the BRG Controller is used to generate general-purpose timer interrupts.
Each interrupt source other than the baud rate generator interrupt has an associated bit in
the I2CISTAT Register, which clears automatically when software reads the register or
performs some other task such as reading or writing the data register.
Transmit Interrupts
Transmit interrupts (TDREbit = 1 in I2CISTAT) occur under the following conditions:
•
•
The Transmit Data Register is empty and the TXIbit = 1 in the I2C Control Register
The I2C Controller is enabled, with any one of the following operations:
–
–
The first bit of a 10-bit address is shifted out
The first bit of the final byte of an address is shifted out and the RDbit is deas-
serted
–
The first bit of a data byte is shifted out
Writing to the I2C Data Register always clears the TRDEbit to 0.
Receive Interrupts
Receive interrupts (RDRFbit = 1in I2CISTAT) occur when a byte of data has been
received by the I2C Controller. The RDRFbit is cleared by reading from the I2C Data Reg-
ister. If the RDRF interrupt is not serviced prior to the completion of the next receive byte,
the I2C Controller holds SCL Low during the last data bit of the next byte until RDRFis
cleared to prevent receive overruns. A receive interrupt does not occur when a Slave
receives an address byte or for data bytes following a Slave address that did not match. An
exception is if the interactive receive mode (IRM) bit is set in the I2CMODE Register in
which case receive interrupts occur for all receive address and data bytes in Slave Mode.
Slave Address Match Interrupts
Slave address match interrupts (SAMbit = 1in I2CISTAT) occur when the I2C Controller
is in Slave Mode and an address is received which matches the unique Slave address. The
General Call Address (0000_0000) and STARTBYTE (0000_0001) are recognized if the
GCE bit = 1 in the I2CMODE Register. Software verifies the RDbit in the I2CISTAT Reg-
ister to determine if the transaction is a read or write transaction. The General Call
Address and STARTBYTE addresses are also distinguished by the RDbit. The general call
address (GCA) bit of the I2CISTAT Register indicates whether the address match occurred
on the unique Slave address or the General Call/STARTBYTE address. The SAMbit clears
automatically when the I2CISTAT Register is read.
If configured using the MODE[1:0]field of the I2C Mode Register for 7-bit slave address-
ing, the most significant 7 bits of the first byte of the transaction are compared against the
SLA[6:0]bits of the Slave Address Register. If configured for 10-bit slave addressing,
PS022010-0811
P R E L I M I N A R Y
I2C Interrupts
ZNEO® Z16F Series MCUs
Product Specification
208
the first byte of the transaction is compared against {11110,SLA[9:8],R/W} and the sec-
ond byte is compared against SLA[7:0].
Arbitration Lost Interrupts
Arbitration Lost interrupts (ARBLSTbit = 1 in I2CISTAT) occur when the I2C Controller is
in Master Mode and loses arbitration (outputs a 1 on SDA and receives a 0 on SDA). The
I2C Controller switches to SLAVE Mode when this occurs. This bit clears automatically
when the I2CISTAT Register is read.
Stop/Restart Interrupts
A Stop/Restart event interrupt (SPRSbit = 1 in I2CISTAT) occurs when the I2C Controller
is in SLAVE Mode and a Stop or Restart condition is received, indicating the end of the
transaction. The RSTRbit in the I2C State Register indicates whether the bit was set due to
a Stop or Restart condition. When a Restart occurs, a new transaction by the same Master
is expected to follow. This bit is cleared automatically when the I2CISTAT Register is
read. The Stop/Restart interrupt only occurs on a selected (address match) slave.
Not Acknowledge interrupts
Not Acknowledge interrupts (NCKIbit = 1 in I2CISTAT) occur in Master Mode when a
Not Acknowledge is received or sent by the I2C Controller and the START or STOP bit is
not set in the I2C Control Register. In MASTER Mode the Not Acknowledge interrupt
clears by setting the START or STOP bit. When this interrupt occurs in Master Mode, the
I2C Controller waits until it is cleared before performing any action. In SLAVE Mode, the
Not Acknowledge interrupt occurs when a Not Acknowledge is received in response to the
data sent. The NCKIbit clears in Slave Mode when software reads the I2CISTAT Register.
General Purpose Timer Interrupt from Baud Rate Generator
If the I2C Controller is disabled (IENbit in the I2CCTL Register = 0) and the BIRQbit in
the I2CCTL Register = 1, an interrupt is generated when the BRG counts down to 1. The
BRG reloads and continues counting, providing a periodic interrupt. None of the bits in
the I2CISTAT Register are set, allowing the BRG in the I2C Controller to be used as a gen-
eral purpose timer when the I2C Controller is disabled.
Start and Stop Conditions
The Master generates the Start and Stop conditions to start or end a transaction. To start a
transaction, the I2C Controller generates a Start condition by pulling the SDA signal Low
while SCL is High. To complete a transaction, the I2C Controller generates a STOP condi-
tion by creating a Low-to-High transition of the SDA signal while the SCL signal is High.
The START and STOP events occur when the START and STOP bits in the I2C Control
Register are written by software to begin or end a transaction. Any byte transfer currently
under way finishes, including the acknowledge phase before the START or STOP condi-
tion occurs.
PS022010-0811
P R E L I M I N A R Y
Start and Stop Conditions
ZNEO® Z16F Series MCUs
Product Specification
209
Software Control of I2C Transactions
The I2C Controller is configured using the I2C Control and I2C Mode registers. The
MODE[1:0]field of the I2C Mode Register allows configuring the I2C Controller for Mas-
ter/Slave or SLAVE ONLY Mode and configures the slave for 7-bit or 10-Bit Address
recognition. The baud rate High and Low Byte Registers must be programmed for the I2C
baud rate in Slave Mode as well as in MASTER Mode. In Slave Mode, the baud rate value
programmed must match the master’s baud rate within ±25% for proper operation.
MASTER/SLAVE Mode is used for:
•
•
•
MASTER ONLY operation in a single master, one or more slave I2C system
MASTER/SLAVE in a multi-master, multi-slave I2C system
SLAVE ONLY operation in an I2C system
In SLAVE ONLY Mode, the STARTbit of the I2C Control Register is ignored (software
cannot initiate a master transaction by accident). This restricts the operation to SLAVE
ONLY Mode and prevents accidental operation in MASTER Mode.
Software controls I2C transactions by enabling the I2C Controller interrupt in the interrupt
controller or by polling the I2C Status Register.
To use interrupts, the I2C interrupt must be enabled in the Interrupt Controller and fol-
lowed by executing an EIinstruction. The TXI bit in the I2C Control Register must be set
to enable transmit interrupts. An I2C interrupt service routine then verifies the I2C Status
Register to determine the cause of the interrupt.
To control transactions by polling, the interrupt bits (TDRE, RDRF, SAM, ARBLST,
SPRS and NCKI) in the I2C Status Register must be polled. The TDREbit asserts regard-
less of the state of the TXI bit.
Master Transactions
The following sections describe the Master read and write transactions to both 7- and 10-
bit slaves.
Master Arbitration
If a Master loses arbitration during the address byte, it releases the SDA line, switches to
SLAVE Mode and monitors the address to determine if it is selected as a Slave. If a Master
loses arbitration during a transmit data byte, it releases the SDA line and waits for the next
STOP or START condition.
The Master detects a loss of arbitration when a 1 is transmitted but a 0 is received from the
bus in the same bit time. This loss occurs if more than one Master is simultaneously
accessing the bus. Loss of arbitration occurs during the address phase (two or more Mas-
PS022010-0811
P R E L I M I N A R Y
Software Control of I2C Transactions
ZNEO® Z16F Series MCUs
Product Specification
210
ters accessing different Slaves) or during the data phase when the Masters are attempting
to write different data to the same Slave.
When a Master loses arbitration, software is informed by means of the Arbitration Lost
interrupt. Software repeats the same transaction again at a later time.
A special case occurs when a slave transaction starts just before software attempts to start
a new master transaction by setting the STARTbit. In this case the state machine enters the
slave states before the START bit is set and the I2C Controller does not arbitrate. If a slave
address match occurs and the I2C Controller receives or transmits data, the STARTbit is
cleared and an Arbitration Lost interrupt is asserted. Software minimizes the chance of
this occurring by checking the BUSY bit in the I2CSTATE Register before initiating a
master transaction. If a slave address match does not occur, the Arbitration Lost interrupt
does not occur and the STARTbit is not cleared. The I2C Controller initiates the master
transaction after the I2C bus is no longer busy.
Master Address Only Transactions
It is sometimes appropriate to perform an address-only transaction to determine if a partic-
ular Slave device is able to respond. This transaction is performed by monitoring the
ACKV bit in the I2CSTATE Register after the address has been written to the I2CDATA
Register and the START bit has been set. After ACKV is set, the ACK bit in the
I2CSTATE Register determines if the Slave is able to communicate. The STOP bit must be
set in the I2CCTL Register to terminate the transaction without transferring data. For a 10-
bit slave address, if the first address byte is acknowledged, the second address byte must
also be sent to determine if the appropriate slave is responding.
Another approach is to set both the STOP and START bits (for sending a 7-bit address).
After both bits are cleared (7-bit address has been sent and transaction is complete), the
ACKbit is read to determine if the slave is acknowledged. For a 10-bit slave, set the STOP
bit after the second TDRE interrupt (second address byte is being sent).
Master Transaction Diagrams
In the following transaction diagrams, shaded regions indicate data transferred from the
Master to the Slave and unshaded regions indicate data transferred from the Slave to the
Master. The transaction field labels are defined as follows:
S: Start
W: Write
A: Acknowledge
A: Not Acknowledge
P: Stop
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
211
Master Write Transaction with a 7-Bit Address
Figure 44 displays the data transfer format from a Master to a 7-bit addressed Slave.
S
Slave Address W=0
A
Data
A
Data
A
Data
A/A
P/S
Figure 44. Data Transfer Format, Master Write Transaction with 7-Bit Addressing
Observe the following procedure for a Master transmit operation to a 7-bit addressed
Slave:
1. Software initializes the MODE field in the I2C Mode Register for MASTER/SLAVE
Mode with either 7-bit or 10-bit slave address. The MODE field selects the address
width for this node when addressed as a Slave, not for the remote Slave. Software
asserts the IENbit in the I2C Control Register.
2. Software asserts the TXI bit of the I2C Control Register to enable Transmit interrupts.
3. The I2C interrupt asserts, because the I2C Data Register is empty
4. Software responds to the TDREbit by writing a 7-bit Slave address plus write bit (=0)
to the I2C Data Register.
5. Software sets the STARTbit of the I2C Control Register.
6. The I2C Controller sends the Start condition to the I2C Slave.
7. The I2C Controller loads the I2C Shift Register with the contents of the I2C Data Reg-
ister.
8. When one bit of address is shifted out by the SDA signal, the Transmit interrupt
asserts.
9. Software responds by writing the transmit data into the I2C Data Register.
10. The I2C Controller shifts the rest of the address and write bit out the SDA signal.
11. The I2C Slave sends an acknowledge (by pulling the SDA signal Low) during the next
High period of SCL. The I2C Controller sets the ACKbit in the I2C State Register.
If the slave does not acknowledge the address byte, the I2C Controller sets the NCKI
bit in the I2C Interrupt Status Register, sets the ACKV bit and clears the ACK bit in
the I2C State Register. Software responds to the Not Acknowledge interrupt by setting
the STOP bit and clearing the TXI bit. The I2C Controller flushes the Transmit Data
Register, sends the STOP condition on the bus and clears the STOP and NCKI bits.
The transaction is complete (ignore the following steps).
12. The I2C Controller loads the contents of the I2C Shift Register with the contents of the
I2C Data Register.
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
212
13. The I2C Controller shifts the data out of through the SDA signal. When the first bit is
sent, the Transmit interrupt asserts.
14. If more bytes remain to be sent, return to step 9.
15. When there is no more data to be sent, software responds by setting the STOP bit of
the I2C Control Register (or START bit to initiate a new transaction).
16. If no additional transaction is queued by the Master, software clears the TXIbit of the
I2C Control Register.
17. The I2C Controller completes transmission of the data on the SDA signal.
18. The I2C Controller sends the STOP condition to the I2C bus.
If the Slave terminates the transaction early by responding with a Not Acknowledge dur-
ing the transfer, the I2C Controller asserts the NCKIinterrupt and halts. Software must ter-
minate the transaction by setting either the STOP bit (end transaction) or the START bit
(end this transaction, start a new one). In this case, it is not necessary for software to set
the FLUSH bit of the I2CCTL Register to flush the data that was previously written but
not transmitted. The I2C Controller hardware automatically flushes transmit data in this
Not Acknowledge case.
Note:
Master Write Transaction with a 10-Bit Address
Figure 45 displays the data transfer format from a Master to a 10-bit addressed Slave.
Slave Address
1st Byte
Slave Address
2nd Byte
S
W=0
A
A
Data
A
Data
A/A
F/S
Figure 45. Data Transfer Format, Master Write Transaction with 10-Bit Addressing
The first seven bits transmitted in the first byte are 11110XX. The two bits XXare the two
most-significant bits of the 10-bit address. The lowest bit of the first byte transferred is the
read/write control bit (=0). The transmit operation is carried out in the same manner as 7-
Bit Address.
Observe the following procedure for a Master transmit operation to a 10-bit addressed
Slave:
1. Software initializes the MODE field in the I2C Mode Register for MASTER/SLAVE
Mode with 7- or 10-Bit Address (I2C bus protocol allows mixing Slave address types).
The MODE field selects the address width for this node when addressed as a Slave,
not for the remote Slave. Software asserts the IENbit in the I2C Control Register.
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
213
2. Software asserts the TXI bit of the I2C Control Register to enable Transmit interrupts.
3. The I2C interrupt asserts because the I2C Data Register is empty.
4. Software responds to the TDREinterrupt by writing the first Slave address byte
(11110xx0). The least-significant bit must be 0 for the write operation.
5. Software asserts the STARTbit of the I2C Control Register.
6. The I2C Controller sends the START condition to the I2C Slave.
7. The I2C Controller loads the I2C Shift Register with the contents of the I2C Data Reg-
ister.
8. When one bit of address is shifted out by the SDA signal, the Transmit interrupt
asserts.
9. Software responds by writing the second byte of address into the contents of the I2C
Data Register.
10. The I2C Controller shifts the rest of the first byte of address and write bit out the SDA
signal.
11. The I2C Slave sends an acknowledge by pulling the SDA signal Low during the next
High period of SCL. The I2C Controller sets the ACK bit in the I2C Status Register.
If the slave does not acknowledge the first address byte, the I2C Controller sets the
NCKIbit in the I2C Status Register, sets the ACKVbit and clears the ACKbit in the I2C
State Register. Software responds to the Not Acknowledge interrupt by setting the
STOP bit and clearing the TXIbit. The I2C Controller flushes the second address byte
from the data register, sends the STOP condition on the bus and clears the STOPand
NCKIbits. The transaction is complete; ignore the following steps.
12. The I2C Controller loads the I2C Shift Register with the contents of the I2C Data Reg-
ister (2nd address byte).
13. The I2C Controller shifts the second address byte out the SDA signal. When the first
bit is sent, the Transmit interrupt asserts.
14. Software responds by writing the data to be written out to the I2C Control Register.
15. The I2C Controller shifts out the rest of the second byte of Slave address (or ensuing
data bytes if looping) by the SDA signal.
16. The I2C Slave sends an acknowledge by pulling the SDA signal Low during the next
High period of SCL. The I2C Controller sets the ACKbit in the I2C Status Register.
If the slave does not acknowledge, return to the second paragraph of Step 11.
17. The I2C Controller shifts the data out by the SDA signal. After the first bit is sent, the
Transmit interrupt asserts.
18. If more bytes remain to be sent, return to step 14.
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
214
19. Software responds by asserting the STOP bit of the I2C Control Register.
20. The I2C Controller completes transmission of the data on the SDA signal.
21. The I2C Controller sends the STOP condition to the I2C bus.
Note: If the Slave responds with a Not Acknowledge during the transfer, the I2C Controller
asserts the NCKI bit, sets the ACKVbit and clears the ACKbit in the I2C State Register and
halts. Software terminates the transaction by setting either the STOP bit (end transaction)
or the START bit (end this transaction, start a new one). The Transmit Data Register is
flushed automatically.
Master Read Transaction with a 7-Bit Address
Figure 46 displays the data transfer format for a read operation to a 7-bit addressed Slave.
Slave
Address
S
R=1
A
Data
A
Data
A
P/S
Figure 46. Data Transfer Format, Master Read Transaction with 7-Bit Addressing
The procedure for a Master read operation to a 7-bit addressed Slave is as follows:
1. Software initializes the MODE field in the I2C Mode Register for MASTER/SLAVE
Mode with 7- or 10-Bit Address (I2C bus protocol allows mixing Slave address types).
The MODE field selects the address width for this node when addressed as a Slave,
not for the remote Slave. Software asserts the IENbit in the I2C Control Register.
2. Software writes the I2C Data Register with a 7-bit Slave address plus the read bit (=1).
3. Software asserts the START bit of the I2C Control Register.
4. For a single byte transfer, software asserts the NAKbit of the I2C Control Register so
that after the first byte of data has been read by the I2C Controller, a Not Acknowledge
instruction is sent to the I2C Slave.
5. The I2C Controller sends the START condition.
6. The I2C Controller sends the address and read bit out the SDA signal.
7. The I2C Slave acknowledges the address by pulling the SDA signal Low during the
next High period of SCL.
If the slave does not acknowledge the address byte, the I2C Controller sets the NCKI
bit in the I2C Status Register, sets the ACKVbit and clears the ACKbit in the I2C State
Register. Software responds to the Not Acknowledge interrupt by setting the STOP bit
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
215
and clearing the TXI bit. The I2C Controller flushes the Transmit Data Register, sends
the STOP condition on the bus and clears the STOP and NCKI bits. The transaction is
complete (ignore the following steps).
8. The I2C Controller shifts in the first byte of data from the I2C Slave on the SDA sig-
nal.
9. The I2C Controller asserts the Receive interrupt.
10. Software responds by reading the I2C Data Register. If the next data byte is to be the
last, software must set the NAKbit of the I2C Control Register.
11. The I2C Controller sends a Not Acknowledge to the I2C Slave if it has received the
last byte; otherwise it sends an Acknowledge.
12. If there are more bytes to transfer, the I2C Controller returns to step 7.
13. A NAK interrupt (NCKIbit in I2CISTAT) is generated by the I2C Controller.
14. Software responds by setting the STOP bit of the I2C Control Register.
15. A STOP condition is sent to the I2C Slave.
Master Read Transaction with a 10-Bit Address
Figure 47 displays the read transaction format for a 10-bit addressed Slave.
Slave Address
1st Byte
Slave Address
2nd Byte
Slave Address
1st Byte
S
W=0 A
A S
R=1
A
Data
A
Data A P
Figure 47. Data Transfer Format, Master Read Transaction with 10-Bit Addressing
The first seven bits transmitted in the first byte are 11110XX. The two bits XXare the two
most-significant bits of the 10-bit address. The lowest bit of the first byte transferred is the
write control bit.
The data transfer procedure for a read operation to a 10-bit addressed Slave is as follows:
1. Software initializes the MODE field in the I2C Mode Register for MASTER/SLAVE
Mode with 7-bit or 10-Bit Address (I2C bus protocol allows mixing Slave address
types). The MODE field selects the address width for this node when addressed as a
Slave, not for the remote Slave. Software asserts the IENbit in the I2C Control Regis-
ter.
2. Software writes 11110B followed by the two most significant address bits and a 0
(write) to the I2C Data Register.
3. Software asserts the STARTbit of the I2C Control Register.
4. The I2C Controller sends the Start condition.
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
216
5. The I2C Controller loads the I2C Shift Register with the contents of the I2C Data Reg-
ister.
6. When the first bit is shifted out, a Transmit interrupt asserts.
7. Software responds by writing the least significant eight bits of address to the I2C Data
Register.
8. The I2C Controller completes shifting of the first address byte.
9. The I2C Slave sends an acknowledge by pulling the SDA signal Low during the next
High period of SCL.
If the slave does not acknowledge the address byte, the I2C Controller sets the NCKI
bit in the I2C Status Register, sets the ACKVbit and clears the ACKbit in the I2C State
Register. Software responds to the Not Acknowledge interrupt by setting the STOP bit
and clearing the TXI bit. The I2C Controller flushes the Transmit Data Register, sends
the STOP condition on the bus and clears the STOPand NCKIbits. The transaction is
complete (ignore the following steps).
10. The I2C Controller loads the I2C Shift Register with the contents of the I2C Data Reg-
ister (lower byte of 10 bit address).
11. The I2C Controller shifts out the next eight bits of address. After the first bit shifts, the
I2C Controller generates a Transmit interrupt.
12. Software responds by setting the STARTbit of the I2C Control Register to generate a
repeated Start.
13. Software responds by writing 11110Bfollowed by the 2-bit Slave address and a 1
(read) to the I2C Data Register.
14. If you want to read only one byte, software responds by setting the NAKbit of the I2C
Control Register.
15. After the I2C Controller shifts out the address bits mentioned in step 9 (second address
transfer), the I2C Slave sends an acknowledge by pulling the SDA signal Low during
the next High period of SCL.
If the slave does not acknowledge the address byte, the I2C Controller sets the NCKI
bit in the I2C Status Register, sets the ACKV bit and clears the ACKbit in the I2C State
Register. Software responds to the Not Acknowledge interrupt by setting the STOP bit
and clearing the TXI bit. The I2C Controller flushes the Transmit Data Register, sends
the STOP condition on the bus and clears the STOP and NCKI bits. The transaction is
complete (ignore the following steps).
16. The I2C Controller sends the repeated START condition.
17. The I2C Controller loads the I2C Shift Register with the contents of the I2C Data Reg-
ister (third address transfer).
PS022010-0811
P R E L I M I N A R Y
Master Transactions
ZNEO® Z16F Series MCUs
Product Specification
217
18. The I2C Controller sends 11110Bfollowed by the two most significant bits of the
Slave read address and a 1 (read).
19. The I2C Slave sends an acknowledge by pulling the SDA signal Low during the next
High period of SCL.
20. The I2C Controller shifts in a byte of data from the Slave.
21. The I2C Controller asserts the Receive interrupt.
22. Software responds by reading the I2C Data Register. If the next data byte is to be the
last, software must set the NAKbit of the I2C Control Register.
23. The I2C Controller sends an Acknowledge or Not Acknowledge to the I2C Slave
based on the NAKbit.
24. If there are more bytes to transfer, the I2C Controller returns to step 18.
25. The I2C Controller generates a NAK interrupt (NCKI bit in I2CISTAT).
26. Software responds by setting the STOP bit of the I2C Control Register.
27. A STOP condition is sent to the I2C Slave.
Slave Transactions
The following sections describe Read and Write transactions to the I2C Controller config-
ured for 7-bit and 10-bit SLAVE modes.
Slave Address Recognition
The following Slave address recognition options are supported:
Slave 7-Bit Address Recognition Mode. If IRM= 0 during the address phase and the
controller is configured for MASTER/SLAVE or SLAVE 7-BIT ADDRESS Mode, the
hardware detects a match to the 7-bit Slave address defined in the I2CSLVAD Register and
generates the Slave Address Match interrupt (SAMbit = 1 in I2CISTAT Register). The I2C
Controller automatically responds during the acknowledge phase with the value in the NAK
bit of the I2CCTL Register.
Slave 10-Bit Address Recognition Mode. If IRM= 0 during the address phase and the
controller is configured for Master/Slave or SLAVE 10-BIT ADDRESS Mode, the hard-
ware detects a match to the 10-bit Slave address defined in the I2CMODE and I2CSLVAD
registers and generates the Slave Address Match interrupt (SAMbit = 1 in I2CISTAT Reg-
ister). The I2C Controller automatically responds during the acknowledge phase with the
value in the NAKbit of the I2CCTL Register.
General Call and STARTBYTE Address Recognition Mode. If GCE= 1 and IRM= 0
during the address phase and the controller is configured for Master/Slave or Slave in
either 7- or 10-BIT ADDRESS Mode, the hardware detects a match to the General Call
Address or START byte and generates the Slave Address Match interrupt. A General Call
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
218
Address is a 7-bit address of all 0’s with the R/W bit = 0. A START byte is a 7-bit address
of all 0’s with the R/W bit = 1. The SAMand GCAbits are set in the I2CISTAT Register. The
RDbit in the I2CISTAT Register distinguishes a General Call Address from a START byte
(= 0 for General Call Address). For a General Call Address, the I2C Controller automati-
cally responds during the address acknowledge phase with the value in the NAKbit of the
I2CCTL Register. If software processes the data bytes associated with the GCAbit, the IRM
bit is optionally set following the SAM interrupt to allow software to examine each
received data byte before deciding to set or clear the NAKbit. A START byte will not be
acknowledged (requirement the I2C specification).
Software Address Recognition Mode. To disable the hardware address recognition, the
IRMbit must be set = 1 prior to the reception of the address byte(s). When IRM= 1 each
received byte generates a receive interrupt (RDRF= 1 in the I2CISTAT Register). Software
must examine each byte and determine whether to set or clear the NAKbit. The Slave holds
SCL Low during the acknowledge phase until software responds by writing to the
I2CCTL Register. The value written to the NAKbit is used by the controller to drive the
I2C Bus, then releasing the SCL. The SAM and GCAbits are not set when IRM= 1 during
the address phase, but the RDbit is updated based on the first address byte.
Slave Transaction Diagrams
In the following transaction diagrams, shaded regions indicate data transferred from the
Master to the Slave and unshaded regions indicate data transferred from the Slave to the
Master. The transaction field labels are defined as follows:
S: Start
W: Write
A: Acknowledge
A: Not Acknowledge
P: Stop
Slave Receive Transaction with 7-Bit Address
The data transfer format for writing data from Master to Slave in 7-bit address Mode is
shown in Figure 47. The following procedure describes the I2C Master/Slave Controller
operating as a Slave in 7-bit address Mode, receiving data from the bus Master.
Slave
Address
S
W=0
A
Data
A
Data
A
Data
A/A
P/S
Figure 48. Data Transfer Format, Slave Receive Transaction with 7-Bit Addressing
1. Software configures the controller for operation as a Slave in 7-Bit Address Mode as
follows.
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
219
a. Initialize the MODE field in the I2C Mode Register for either SLAVE ONLY
Mode or MASTER/SLAVE Mode with 7-Bit Addressing.
b. Optionally set the GCEbit.
c. Initialize the SLA[6:0] bits in the I2C Slave Address Register.
d. Set IEN= 1 in the I2C Control Register. Set NAK= 0 in the I2C Control Register.
e. Program the Baud Rate High and Low Byte registers for the I2C baud rate.
2. The bus Master initiates a transfer, sending the address byte. The Slave Mode I2C
Controller recognizes its own address and detects the R/W bit = 0 (write from Master
to Slave). The I2C Controller acknowledges, indicating it is available to accept the
transaction.The SAMbit in the I2CISTAT Register is set = 1, causing an interrupt. The
RDbit in the I2CISTAT Register is set = 0, indicating a write to the Slave. The I2C
Controller holds the SCL signal Low, waiting for software to load the first data byte.
3. Software responds to the interrupt by reading the I2CISTAT Register (which clears the
SAMbit). After verifying that the SAMbit = 1, software checks the RDbit. When RD=
0, no immediate action is required until the first byte of data is received. If software is
only able to accept a single byte it sets the NAKbit in the I2CCTL Register at this time.
4. The Master detects the acknowledge and sends the byte of data.
5. The I2C controller receives the data byte and responds with Acknowledge or Not
Acknowledge depending on the state of the NAKbit in the I2CCTL Register. The I2C
controller generates the receive data interrupt by setting the RDRFbit in the I2CISTAT
Register.
6. Software responds by reading the I2CISTAT Register, finding the RDRFbit=1 and
reading the I2CDATA Register clearing the RDRFbit. If software accepts only one
more data byte, it sets the NAKbit in the I2CCTL Register.
7. The Master and Slave loop on steps 4–6 until the Master detects a Not Acknowledge
instruction or runs out of data to send.
8. The Master sends the STOP or RESTART signal on the bus. Either of these signals
cause the I2C Controller to assert the Stop interrupt (STOP bit = 1 in the I2CISTAT
Register). When the Slave receive data from the Master, software takes no action in
response to the Stop interrupt other than reading the I2CISTAT Register, clearing the
STOP bit in the I2CISTAT Register.
Slave Receive Transaction with 10-Bit Address
The data transfer format for writing data from Master to Slave with 10-Bit Addressing is
shown in Figure 48. The following procedure describes the I2C Master/Slave Controller
operating as a Slave in 10-Bit Addressing Mode, receiving data from the bus Master.
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
220
Slave Address
1st Byte
Slave Address
2nd Byte
S
W=0
A
A
Data
A
Data
A/A
P/S
Figure 49. Data Transfer Format, Slave Receive Transaction with 10-Bit Addressing
1. Software configures the controller for operation as a Slave in 10-Bit Addressing Mode
as follows.
a. Initialize the MODE field in the I2CMODE Register for either SLAVE ONLY
Mode or MASTER/SLAVE Mode with 10-Bit Addressing.
b. Optionally set the GCEbit.
c. Initialize the SLA[7:0] bits in the I2CSLVAD Register and the SLA[9:8] bits in the
I2CMODE Register.
d. Set IEN= 1 in the I2CCTL Register. Set NAK= 0 in the I2C Control Register.
e. Program the Baud Rate High and Low Byte registers for the I2C baud rate.
2. The Master initiates a transfer by sending the first address byte. The I2C Controller
recognizes the start of a 10-bit address with a match to SLA[9:8] and detects the R/W
bit = 0 (write from Master to Slave). The I2C Controller acknowledges, indicating that
it is available to accept the transaction.
3. The Master sends the second address byte. The Slave Mode I2C Controller detects an
address match between the second address byte and SLA[7:0]. The SAMbit in the
I2CISTAT Register is set = 1, causing an interrupt. The RDbit is set = 0, indicating a
write to the Slave. The I2C Controller Acknowledges, indicating it is available to
accept the data.
4. Software responds to the interrupt by reading the I2CISTAT Register, which clears the
SAMbit. When RD= 0, no immediate action is taken by software until the first byte of
data is received. If software is only able to accept a single byte it sets the NAKbit in the
I2CCTL Register.
5. The Master detects the Acknowledge and sends the first byte of data.
6. The I2C controller receives the first byte and responds with Acknowledge or Not
Acknowledge, depending on the state of the NAKbit in the I2CCTL Register. The I2C
controller generates the receive data interrupt by setting the RDRFbit in the I2CISTAT
Register.
7. Software responds by reading the I2CISTAT Register, finding the RDRFbit = 1 and
then reading the I2CDATA Register, which clears the RDRFbit. If software accepts
only one more data byte, it sets the NAKbit in the I2CCTL Register.
8. The Master and Slave loops on steps 5–7 until the Master detects a Not Acknowledge
instruction or runs out of data to send.
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
221
9. The Master sends the STOP or RESTART signal on the bus. Either of these signals
cause the I2C Controller to assert the Stop interrupt (STOP bit = 1 in the I2CISTAT
Register). When the Slave receive data from the Master, software takes no action in
response to the Stop interrupt other than reading the I2CISTAT Register, clearing the
STOP bit.
Slave Transmit Transaction with 7-Bit Address
The data transfer format for a Master reading data from a Slave in 7-bit address Mode is
shown in Figure 49. The following procedure describes the I2C Master/Slave Controller
operating as a Slave in 7-Bit Addressing Mode, transmitting data to the bus Master.
Slave
Address
S
R=1
A
Data
A
Data
A
P/S
Figure 50. Data Transfer Format, Slave Transmit Transaction with 7-Bit Addressing
1. Software configures the controller for operation as a Slave in 7-Bit Addressing Mode
as follows.
a. Initialize the MODE field in the I2C Mode Register for either SLAVE ONLY
Mode or MASTER/SLAVE Mode with 7-Bit Addressing.
b. Optionally set the GCEbit.
c. Initialize the SLA[6:0] bits in the I2C Slave Address Register.
d. Set IEN= 1 in the I2C Control Register. Set NAK= 0 in the I2C Control Register.
e. Program the Baud Rate High and Low Byte registers for the I2C baud rate.
2. The Master initiates a transfer, sending the address byte. The SLAVE Mode I2C Con-
troller finds an address match and detects the R/W bit = 1 (read by Master from
Slave). The I2C Controller acknowledges, indicating that it is ready to accept the
transaction.The SAMbit in the I2CISTAT Register is set = 1, causing an interrupt. The
RDbit is set = 1, indicating a read from the Slave.
3. Software responds to the interrupt by reading the I2CISTAT Register, clearing the SAM
bit. When RD= 1, software responds by loading the first data byte into the I2CDATA
Register. Software sets the TXIbit in the I2CCTL Register to enable transmit inter-
rupts. When the Master initiates the data transfer, the I2C Controller holds SCL Low
until software has written the first data byte to the I2CDATA Register.
4. SCL is released and the first data byte is shifted out.
5. When the first bit of the first data byte is transferred, the I2C controller sets the TDRE
bit, which asserts the transmit data interrupt.
6. Software responds to the transmit data interrupt (TDRE= 1) by loading the next data
byte into the I2CDATA Register, which clears TDRE.
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
222
7. When the Master receives the data byte, the Master transmits an Acknowledge
instruction (or Not Acknowledge instruction for the last data byte).
8. The bus cycles through steps 5–7 until the last byte has been transferred. If software
has not yet loaded the next data byte when the Master brings SCL Low to transfer the
most significant data bit, the Slave I2C Controller holds SCL Low until the data regis-
ter is written. When the Slave receives a Not Acknowledge instruction, the I2C Con-
troller sets the NCKIbit in the I2CISTAT Register and generates the Not Acknowledge
interrupt.
9. Software responds to the Not Acknowledge interrupt by clearing the TXIbit in the
I2CCTL Register and by asserting the FLUSHbit of the I2CCTL Register to empty the
data register.
10. When the Master completes the last acknowledge cycle, it asserts the STOP or
RESTART condition on the bus.
11. The Slave I2C Controller asserts the STOP/RESTART interrupt (set SPRSbit in
I2CISTAT Register).
12. Software responds to the STOP/RESTART interrupt by reading the I2CISTAT Regis-
ter which clears the SPRSbit.
Slave Transmit (Master Read) Transaction with 10-Bit Address
Figure 51 displays the data transfer format for a Master reading data from a Slave with 10-
Bit Addressing.
Slave Address
1st Byte
Slave Address
2nd Byte
Slave Address
1st Byte
S
W=0 A
A S
R=1
A
Data
A
Data A P
Figure 51. Data Transfer Format, Slave Transmit Transaction with 10-Bit Addressing
The following procedure describes the I2C Master/Slave Controller operating as a Slave in
10-Bit Addressing Mode, transmitting data to the bus Master:
1. Software configures the controller for operation as a Slave in 10-Bit Addressing
Mode.
–
Initialize the MODE field in the I2C Mode Register for either SLAVE ONLY
Mode or MASTER/SLAVE Mode with 10-Bit Addressing.
–
–
Optionally set the GCEbit.
Initialize the SLA[7:0] bits in the I2CSLVAD Register and SLA[9:8] in the
I2CMODE Register.
–
–
Set IEN= 1, NAK= 0 in the I2C Control Register.
Program the Baud Rate High and Low Byte registers for the I2C baud rate.
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
223
2. The Master initiates a transfer, sending the first address byte. The Slave Mode I2C
Controller recognizes the start of a 10-bit address with a match to SLA[9:8] and detects
the R/W bit = 0 (write from Master to Slave). The I2C Controller acknowledges, indi-
cating that it is available to accept the transaction.
3. The Master sends the second address byte. The Slave Mode I2C Controller compares
the second address byte with the value in SLA[7:0]. If there is a match, the SAMbit in
the I2CISTAT Register is set = 1, causing a Slave Address Match interrupt. The RDbit
is set = 0, indicating a write to the Slave. If a match occurs, the I2C Controller
acknowledges on the I2C bus, indicating that it is available to accept the data.
4. Software responds to the Slave Address Match interrupt by reading the I2CISTAT
Register which clears the SAMbit. When the RDbit = 0, no further action is required.
5. The Master notifies the Acknowledge and sends a Restart instruction, followed by the
2
first address byte with the R/W = 1. The Slave Mode I C Controller recognizes the
Restart followed by the first address byte with a match to SLA[9:8] and detects the R/W
2
= 1 (Master reads from Slave). The Slave I C Controller sets the SAMbit in the
I2CISTAT Register, which causes the Slave Address Match interrupt. The RDbit is set =
2
1. The Slave Mode I C Controller acknowledges on the bus.
6. Software responds to the interrupt by reading the I2CISTAT Register, clearing the SAM
bit. Software loads the initial data byte into the I2CDATA Register and sets the TXIbit
in the I2CCTL Register.
7. The Master starts the data transfer by asserting SCL Low. After the I2C Controller has
data available to transmit the SCL is released and the Master proceeds to shift the first
data byte.
8. When the first bit of the first data byte is transferred, the I2C controller sets the TDRE
bit, which asserts the transmit data interrupt.
9. Software responds to the transmit data interrupt by loading the next data byte into the
I2CDATA Register.
10. The I2C Master shifts in the remainder of the data byte. The Master transmits the
Acknowledge (or Not Acknowledge for the last data byte).
11. The bus cycles through steps 7–10 until the last byte has been transferred. If software
has not yet loaded the next data byte when the Master brings SCL Low to transfer the
most significant data bit, the Slave I2C Controller holds SCL Low until the data regis-
ter is written. When the Slave receives a Not Acknowledge, the I2C Controller sets the
NCKIbit in the I2CISTAT Register and generates the NAK interrupt.
12. Software responds to the NAK interrupt by clearing the TXIbit in the I2CCTL Regis-
ter and by asserting the FLUSHbit of the I2CCTL Register.
13. When the Master has completed the acknowledge cycle of the last transfer it asserts
the STOP or RESTART condition on the bus.
PS022010-0811
P R E L I M I N A R Y
Slave Transactions
ZNEO® Z16F Series MCUs
Product Specification
224
14. The Slave I2C Controller asserts the STOP/RESTART interrupt (set SPRS bit in
I2CISTAT Register).
15. Software responds to the Stop interrupt by reading the I2CISTAT Register, clearing
the SPRSbit.
DMA Control of I2C Transactions
The DMA engine is configured to support transmit and receive DMA requests from the
I2C Controller. The I2C data interrupt requests must be disabled by setting the DMAIFbit
in the I2C Mode Register and clearing the TXI bit in the I2C Control Register. This allows
error condition interrupts to be handled by software while data movement is handled by
the DMA engine.
The DMA interface on the I2C Controller is intended to support data transfer but not
MASTER Mode address byte transfer. The START, STOP and NAK bits must be con-
trolled by software.
A summary of the sequence of I2C data transfer using the DMA follows.
Master Write Transaction with Data DMA
1. Configure the selected DMA Channel for I2C transmit. The IEOB bit must be set in
the DMACTL Register for the last buffer to be transferred.
2. The I2C interrupt must be enabled in the interrupt controller to alert software of any
I2C error conditions. A Not Acknowledge interrupt occurs on the last byte transferred.
3. The I2C Master/Slave must be configured as defined in the sections above describing
Master Mode transactions. The TXIbit in the I2CCTL Register must be cleared.
4. Initiate the I2C transaction as described in the Master Address Only Transactions sec-
tion on page 210, using the ACKVand ACKbits in the I2CSTATE Register to determine
if the slave acknowledges.
5. Set the DMAIF bit in the I2CMODE Register.
6. The DMA transfers the data, which is to be transmitted to the slave.
7. When the DMA interrupt occurs, poll the I2CSTAT Register until the TDRE bit = 1 to
ensure that the I2C Master/Slave hardware has commenced transmitting the most
recent byte written by the DMA.
8. Set the STOP bit in the I2CCTL Register. The STOP bit is polled by software to deter-
mine when the transaction is actually completed.
9. Clear the DMAIF bit in the I2CMODE Register.
The following section describes the I2C Master/Slave Controller operating as a Slave in
10-Bit Addressing Mode, transmitting data to the bus master.
PS022010-0811
P R E L I M I N A R Y
DMA Control of I2C Transactions
ZNEO® Z16F Series MCUs
Product Specification
225
Note: If the slave sends a Not Acknowledge prior to the last byte, a Not Acknowledge interrupt
occurs. Software must respond to this interrupt by clearing the DMAIF bit and setting the
STOP bit to end the transaction.
Master Read Transaction with Data DMA
In master read transactions, the Master is responsible for the Acknowledge for each data
byte transferred. The Master software must set the NAK bit after the next to the last data
byte has been received or while the last byte is being received. The DMA supports this by
setting the DMA watermark to 0x01, which results in a DMA interrupt when the next to
the last byte has been received. A DMA interrupt also occurs when the last byte is
received. Otherwise, the sequence is similar to that described above for the Master write
transaction.
1. Configure the selected DMA Channel for I2C receive. The IEOBbit must be set in the
DMACTL Register for the last buffer to be transferred. Typically one buffer is defined
with a transfer length of N where N bytes are expected to be read from the slave. The
watermark is set to 1 by writing a 0x01 to DMAxLAR[23:16].
2. The I2C interrupt must be enabled in the interrupt controller to alert software of any
I2C error conditions. A Not Acknowledge interrupt occurs on the last byte transferred.
3. The I2C Master/Slave must be configured as defined in the sections above describing
MASTER Mode transactions. The TXIbit in the I2CCTL Register must be cleared.
4. Initiate the I2C transaction as described in the Master Address Only Transactions sec-
tion on page 210, using the ACKVand ACKbits in the I2CSTATE Register to determine
if the slave acknowledges. Do not set the STOP bit unless ACKV=1 and ACK=0 (slave
did not acknowledge).
5. Set the DMAIFbit in the I2CMODE Register.
6. The DMA transfers the data to memory as it is received from the slave.
7. When the first DMA interrupt occurs indicating the (N-1)st byte has been received,
the NAKbit must be set in the I2CCTL Register.
8. When the second DMA interrupt occurs, it indicates that the Nth byte has been
received. Set the STOP bit in the I2CCTL Register. The STOP bit is polled by soft-
ware to determine when the transaction is actually completed.
9. Clear the DMAIFbit in the I2CMODE Register.
Slave Write Transaction with Data DMA
In a transaction where the I2C Master/Slave operates as a slave, receiving data written by a
master, the software must set the NAKbit after the N-1st byte has been received or during
PS022010-0811
P R E L I M I N A R Y
DMA Control of I2C Transactions
ZNEO® Z16F Series MCUs
Product Specification
226
the reception of the last byte. As in the Master Read transaction described above, the
watermark DMA interrupt is used to notify software when the N-1st byte has been
received.
1. Configure the selected DMA Channel for I2C receive. The IEOBbit must be set in the
DMACTL Register for the last buffer to be transferred. Typically one buffer will be
defined with a transfer length of N where N bytes are expected to be received from the
master. The watermark is set to 1 by writing a 0x01 to DMAxLAR[23:16].
2. The I2C interrupt must be enabled in the interrupt controller to alert software of any
I2C error conditions.
3. The I2C Master/Slave must be configured as defined in the sections above describing
Slave Mode transactions. The TXIbit in the I2CCTL Register must be cleared.
4. When the SAM interrupt occurs, set the DMAIFbit in the I2CMODE Register.
5. The DMA transfers the data to memory as it is received from the master.
6. When the first DMA interrupt occurs indicating that the (N-1)st byte is received, the
NAKbit must be set in the I2CCTL Register.
7. When the second DMA interrupt occurs, it indicates that the Nth byte is received. A
Stop I2C interrupt occurs (SPRSbit set in the I2CSTAT Register) when the master
issues the STOP (or RESTART) condition.
8. Clear the DMAIFbit in the I2CMODE Register.
Slave Read Transaction with Data DMA
In this transaction the I2C Master/Slave operates as a slave, sending data to the master.
1. Configure the selected DMA Channel for I2C transmit. The IEOBbit must be set in
the DMACTL Register for the last buffer to be transferred. Typically a single buffer
with a transfer length of N is defined.
2. The I2C interrupt must be enabled in the interrupt controller to alert software of any
I2C error conditions. A Not Acknowledge interrupt occurs on the last byte transferred.
3. The I2C Master/Slave must be configured as defined in the sections above describing
Slave Mode transactions. The TXIbit in the I2CCTL Register must be cleared.
4. When the SAM interrupt occurs, set the DMAIFbit in the I2CMODE Register.
5. The DMA transfers the data to be transmitted to the master.
6. When the DMA interrupt occurs, the last byte is being transferred to the master. The
master must send a Not Acknowledge for this last byte, setting the NCKIbit in the
I2CSTAT Register and generating the I2C interrupt. A Stop or Restart interrupt (SPRS
bit set in I2CSTAT Register) follows.
7. Clear the DMAIFbit in the I2CMODE Register.
PS022010-0811
P R E L I M I N A R Y
DMA Control of I2C Transactions
ZNEO® Z16F Series MCUs
Product Specification
227
Note: If the master sends a Not Acknowledge prior to the last byte, software responds to the Not
Acknowledge interrupt by clearing the DMAIFbit.
2
I C Control Register Definitions
The following section describes the I2C control registers.
I2C Data Register
The I2C Data Register, shown in Table 112, holds the data that is to be loaded into the
Shift Register to transmit onto the I2C bus. This register also holds data that is loaded from
the Shift Register after it is received from the I2C bus. The I2C Shift Register is not acces-
sible in the Register File address space, but is used only to buffer incoming and outgoing
data.
Writes by software to the I2CDATA Register are blocked if a slave write transaction is
underway (I2C Controller in Slave Mode, data being received).
2
Table 112. I C Data Register (I2CDATA)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DATA
0
R/W
Addr
FF‒E240H
I2C Interrupt Status Register
The Read-only I2C Interrupt Status Register, shown in Table 113, indicates the cause of
any current I2C interrupt and provides the status of the I2C Controller. When an interrupt
occurs, one or more of the TDRE, RDRF, SAM, ARBLST, SPRSor NCKIbits is set. The GCA
and RDbits do not generate an interrupt but rather provide status associated with the SAM
bit interrupt.
PS022010-0811
P R E L I M I N A R Y
I2C Control Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
228
2
Table 113. I C Interrupt Status Register (I2CISTAT)
Bits
7
TDRE
1
6
RDRF
0
5
SAM
0
4
GCA
0
3
RD
0
2
1
SPRS
0
0
NCKI
0
Field
RESET
R/W
ARBLST
0
R
R
R
R
R
R
R
R
Addr
FF‒E241H
Bit
Description
[7]
TDRE
Transmit Data Register Empty
2
2
When the I C Controller is enabled, this bit is 1 if the I C Data Register is empty. When set, the
2
2
I C Controller generates an interrupt, except when the I C Controller is shifting in data during
the reception of a byte or when shifting an address and the RD bit is set. This bit clears by writ-
ing to the I2CDATA Register.
[6]
RDRF
Receive Data Register Full
This bit is set = 1 when the I C Controller is enabled and the I C Controller has received a byte
of data. When asserted, this bit causes the I C Controller to generate an interrupt. This bit
2
2
2
clears by reading the I2CDATA Register.
[5]
SAM
Slave Address Match
This bit is set = 1 if the I C Controller is enabled in Slave Mode and an address is received
2
which matches the unique Slave address or General Call Address (if enabled by the GCEbit in
2
the I C Mode Register). In 10-Bit Addressing Mode, this bit is not set until a match is achieved
on both address bytes. When this bit is set, the RDand GCAbits are also valid. This bit clears
by reading the I2CISTAT Register.
[4]
GCA
General Call Address
This bit is set in Slave Mode when the General Call Address or START byte is recognized (in
either 7- or 10-bit Slave Mode). The GCEbit in the I C Mode Register must be set to enable
2
recognition of the General Call Address and START byte. This bit clears when IEN= 0 and is
updated following the first address byte of each Slave Mode transaction. A General Call
Address is distinguished from a START byte by the value of the RD bit (RD = 0 for General Call
Address, 1 for START byte).
[3]
RD
Read
This bit indicates the direction of transfer of the data. It is set when the Master is reading data
from the Slave. This bit matches the least-significant bit of the address byte after the START
condition occurs (for both Master and Slave modes). This bit clears when IEN = 0 and is
updated following the first address byte of each transaction.
[2]
Arbitration Lost
2
ARBLST This bit is set when the I C Controller is enabled in Master Mode and loses arbitration (outputs
a 1 on SDA and receives a 0 on SDA). The ARBLSTbit clears when the I2CISTAT Register is
read.
PS022010-0811
P R E L I M I N A R Y
I2C Interrupt Status Register
ZNEO® Z16F Series MCUs
Product Specification
229
Bit
Description (Continued)
[1]
SPRS
Stop/Restart Condition Interrupt
2
This bit is set when the I C Controller is enabled in Slave Mode and detects a STOP or
RESTART condition during a transaction directed to this slave. This bit clears when the
I2CISTAT Register is read. Read the RSTR bit of the I2CSTATE Register to determine whether
the interrupt was caused by a STOP or RESTART condition.
[0]
NCKI
NAK Interrupt
In Master Mode, this bit is set when a Not Acknowledge condition is received or sent and nei-
ther the START nor the STOP bit is active. In Master Mode, this bit is cleared only by setting
the START or STOP bits.
In Slave Mode, this bit is set when a Not Acknowledge condition is received (Master reading
data from Slave), indicating the Master is finished reading. A STOP or RESTART condition fol-
lows. In Slave Mode this bit clears when the I2CISTAT Register is read.
I2C Control Register
The I2C Control Register, shown in Table 114, enables and configures the I2C operation.
2
Table 114. I C Control Register (I2CCTL)
Bits
7
IEN
0
6
START
0
5
4
BIRQ
0
3
TXI
0
2
NAK
0
1
FLUSH
0
0
FILTEN
0
Field
RESET
R/W
STOP
0
R/W
R/W1
R/W1
R/W
R/W
R/W1
R/W
R/W
Addr
FF‒E242H
Note: R/W1 = The bit is set (write 1) but not cleared.
Bit
Description
2
[7]
I C Enable
2
IEN
This bit enables the I C Controller.
[6]
START
Send Start Condition
2
When set, this bit causes the I C Controller (when configured as the Master) to send the Start
condition. After it is asserted, this bit is cleared by the I C Controller after it sends the Start con-
2
dition or by deasserting the IENbit. If this bit is 1, it cannot be cleared by writing to the bit. After
this bit is set, the START condition is sent if there is data in the I2CDATA or I2CSHIFT Register.
2
If there is no data in one of these registers, the I C Controller waits until data is loaded. If this
2
bit is set while the I C Controller is shifting out data, it generates a RESTART condition after
the byte shifts and the acknowledge phase completes. If the STOP bit is also set, it also waits
until the STOP condition is sent before the START condition.
If START is set while a Slave Mode transaction is underway to this device, the START bit is
cleared and ARBLSTbit in the Interrupt Status Register will be set.
2
PS022010-0811
P R E L I M I N A R Y
I C Control Register
ZNEO® Z16F Series MCUs
Product Specification
230
Bit
Description (Continued)
Send Stop Condition
[5]
2
STOP
When set, this bit causes the I C Controller (when configured as the Master) to send the STOP
2
condition after the byte in the I C Shift Register has completed transmission or after a byte has
2
been received in a receive operation. When set, this bit is reset by the I C Controller after a
STOP condition has been sent or by deasserting the IEN bit. If this bit is 1, it cannot be cleared
to 0 by writing to the register.
If STOP is set while a Slave Mode transaction is underway, the STOP bit will be cleared by
hardware.
[4]
BIRQ
Baud Rate Generator Interrupt Request
2
2
This bit is ignored when the I C Controller is enabled. If this bit is set = 1 when the I C Control-
ler is disabled (IEN= 0) the baud rate generator is used as an additional timer causing an
interrupt to occur every time the baud rate generator counts down to 1. The baud rate genera-
tor runs continuously in this Mode, generating periodic interrupts.
[3]
TXI
Enable TDRE Interrupts
This bit enables interrupts when the I C Data Register is empty.
2
[2]
NAK
Send NAK
Setting this bit sends a Not Acknowledge condition after the next byte of data has been
received. It is automatically deasserted after the Not Acknowledge is sent or the IENbit is
cleared. If this bit is 1, it cannot be cleared to 0 by writing to the register.
[1]
FLUSH
Flush Data
2
Setting this bit clears the I C Data Register and sets the TDREbit to 1. This bit allows flushing
2
of the I C Data Register when an NAK condition is received after the next data byte has been
2
written to the I C Data Register. Reading this bit always returns 0.
2
[0]
I C Signal Filter Enable
FILTEN Setting this bit enables low-pass digital filters on the SDA and SCL input signals. This function
2
provides the spike suppression filter required in I C Fast Mode. These filters reject any input
pulse with periods less than a full system clock cycle. The filters introduce a 3-system clock
cycle latency on the inputs.
I2C Baud Rate High and Low Byte Registers
The I2C Baud Rate High and Low Byte registers, shown in Tables 115 and 116, combine
to form a 16-bit reload value, BRG[15:0], for the I2C Baud Rate Generator. The baud rate
High and Low Byte Registers must be programmed for the I2C baud rate in Slave Mode as
well as in MASTER Mode. In Slave Mode, the baud rate value programmed must match
the master's baud rate within ±25% for proper operation.
The I2C baud rate is calculated using the following equation.
System Clock Frequency (Hz)
------------------------------------------------------------------------
I2C Baud Rate (bps) =
4 BRG[15:0]
PS022010-0811
P R E L I M I N A R Y
I2C Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
231
Note: If BRG= 0000H, use 10000Hin the equation.
2
Table 115. I C Baud Rate High Byte Register (I2CBRH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BRH
FFH
R/W
Addr
FF‒E243H
Bit
Description
2
[7:0]
I C Baud Rate High Byte
2
BRH
Most significant byte, BRG[15:8], of the I C Baud Rate Generator’s reload value.
If the DIAGbit in the I2C Mode Register is set to 1, a read of the I2CBRH Register returns
Note:
the current value of the I2C Baud Rate Counter[15:8].
2
Table 116. I C Baud Rate Low Byte Register (I2CBRL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
BRL
FFH
R/W
Addr
FF‒E244H
Bit
Description
2
[7:0]
I C Baud Rate Low Byte
2
BRL
Least significant byte, BRG[7:0], of the I C Baud Rate Generator’s reload value.
Note: If the DIAGbit in the I2C Mode Register is set to 1, a read of the I2CBRL Register returns
the current value of the I2C Baud Rate Counter[7:0].
PS022010-0811
P R E L I M I N A R Y
I2C Baud Rate High and Low Byte
ZNEO® Z16F Series MCUs
Product Specification
232
I2C State Register
The read-only I2C State Register provides information about the state of the I2C bus and
the I2C Bus Controller.
When the DIAGbit of the I2C Mode Register is cleared, this register provides information
about the internal state of the I2C Controller and I2C Bus as shown in Table 117. When the
DIAGbit of the I2C Mode Register is set, this register returns the value of the I2C Control-
ler state machine, as shown in Table 118. Tables 119 and 120 describe the state encoding
of the I2C State registers.
2
Table 117. I C State Register (I2CSTATE), Description when DIAG = 0
Bits
7
ACKV
0
6
ACK
0
5
AS
0
4
DS
0
3
10B
0
2
RSTR
0
1
0
BUSY
X
Field
RESET
R/W
SCLOUT
X
R
R
R
R
R
R
R
R
Addr
FF‒E245H
Bit
Description
ACK Valid
[7]
ACKV
This bit is set if sending data (Master or Slave) and the ACKbit in this register is valid for the
byte just transmitted. This bit is monitored if it is appropriate for software to verify the ACKvalue
before writing the next byte to be sent. To operate in this Mode, the data register must not be
written when TDREasserts; instead, software waits for ACKVto assert. This bit clears when
transmission of the next byte begins or the transaction is ended by a STOP or RESTART con-
dition.
[6]
ACK
Acknowledge
This bit indicates the status of the Acknowledge for the last byte transmitted or received. This
bit is set for an Acknowledge and cleared for a Not Acknowledge condition.
[5]
AS
Address State
2
This bit is active High while the address is being transferred on the I C bus.
[4]
DS
Data State
2
This bit is active High while the data is being transferred on the I C bus.
[3]
10B
10B
This bit indicates whether a 10 or 7-bit address is being transmitted when operating as a Mas-
ter. After the STARTbit is set, if the five most-significant bits of the address are 11110B, this bit
is set. When set, it is reset after the address has been sent.
[2]
RSTR
Restart
This bit is updated each time a STOP or RESTART interrupt occurs (SPRSbit set in I2CISTAT
Register).
0 = Stop condition
1 = Restart condition
PS022010-0811
P R E L I M I N A R Y
I2C State Register
ZNEO® Z16F Series MCUs
Product Specification
233
Bit
Description (Continued)
Serial Clock Output
[1]
SCLOUT Current value of Serial Clock being output onto the bus. The actual values of the SCL and SDA
2
signals on the I C bus is observed via the GPIO Input Register.
2
[0]
I C Bus Busy
2
BUSY
0 = No activity on the I C Bus.
2
1 = A transaction is underway on the I C bus.
2
Table 118. I C State Register (I2CSTATE), Description when DIAG = 1
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
I2CSTATE_H
I2CSTATE_L
0
0
0
0
0
0
0
0
R
R
R
R
R
R
R
R
Addr
FF‒E245H
Bit
Description
2
[7:4]
I C State High
2
I2CSTATE_H This field defines the current state of the I C Controller. It is the most significant nibble of
the internal state machine. Table 119 defines the states for this field.
2
[3:0]
I C State Low
2
I2CSTATE_L Least significant nibble of the I C state machine. This field defines the substates for the
states defined by I2CSTATE_H. Table 120 defines the values for this field.
Table 119. I2CSTATE_H
State Encoding
0000
State Name
Idle
State Description
2
2
I C bus is idle or I C Controller is disabled.
2
0001
Slave Start
Slave Bystander
Slave Wait
I C Controller has received a start condition.
0010
Address did not match–ignore remainder of transaction.
0011
Waiting for STOP or RESTART condition after sending a
Not Acknowledge instruction.
0100
0101
Master Stop2
Master completing STOP condition (SCL = 1, SDA = 1).
Master Start/Restart
Master Mode sending START condition (SCL = 1, SDA =
0).
0110
Master Stop1
Master initiating STOP condition (SCL = 1, SDA = 0).
PS022010-0811
P R E L I M I N A R Y
I2C State Register
ZNEO® Z16F Series MCUs
Product Specification
234
Table 119. I2CSTATE_H (Continued)
State Description
State Encoding
State Name
0111
Master Wait
Master received a Not Acknowledge instruction, waiting
for software to assert STOP or START control bits.
1000
1001
1010
Slave Transmit Data
Slave Receive Data
Slave Receive Addr1
Nine substates, one for each data bit and one for the
acknowledge.
Nine substates, one for each data bit and one for the
acknowledge.
Slave Receiving first address byte (7 and 10 bit address-
ing)
Nine substates, one for each address bit and one for the
acknowledge.
1011
Slave Receive Addr2
Slave Receiving second address byte (10 bit address-
ing)
Nine substates, one for each address bit and one for the
acknowledge.
1100
1101
1110
Master Transmit Data
Master Receive Data
Master Transmit Addr1
Nine substates, one for each data bit and one for the
acknowledge.
Nine substates, one for each data bit and one for the
acknowledge.
Master sending first address byte (7- and 10-Bit
Addressing)
Nine substates, one for each address bit and one for the
acknowledge.
1111
Master Transmit Addr2
Master sending second address byte (10-Bit Address-
ing)
Nine substates, one for each address bit and one for the
acknowledge.
Table 120. I2CSTATE_L
State
Sub-State
I2CSTATE_H I2CSTATE_L Sub-State Name
State Description
0000–0100
0110–0111
0000
0000
—
—
There are no substates for these I2CSTATE_H
values.
There are no substates for these I2CSTATE_H
values.
PS022010-0811
P R E L I M I N A R Y
I2C State Register
ZNEO® Z16F Series MCUs
Product Specification
235
Table 120. I2CSTATE_L (Continued)
State
Sub-State
I2CSTATE_H I2CSTATE_L Sub-State Name
State Description
0101
0000
0001
Master Start
Initiating a new transaction.
Master Restart
Master is ending one transaction and starting a
new one without letting the bus go nonactive.
1000–1111
0111
0110
0101
0100
0011
0010
0001
0000
1000
send/receive bit 7
send/receive bit 6
send/receive bit 5
send/receive bit 4
send/receive bit 3
send/receive bit 2
send/receive bit 1
send/receive bit 0
Sending/Receiving most significant bit.
Sending/Receiving least significant bit
send/receive Acknowl- Sending/Receiving Acknowledge
edge
PS022010-0811
P R E L I M I N A R Y
I2C State Register
ZNEO® Z16F Series MCUs
Product Specification
236
I2C Mode Register
The I2C Mode Register, shown in Table 121, provides control over MASTER versus
SLAVE operating mode, Slave address and diagnostic modes.
2
Table 121. I C Mode Register (I2CMODE)
Bits
7
DMAIF
0
6
5
4
3
2
1
0
DIAG
0
Field
RESET
R/W
MODE[1:0]
IRM
0
GCE
0
SLA[9:8]
0
0
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF‒E246H
Bit
Description
[7]
DMAIF
DMA Interface Mode
0 = Used when software polling or interrupts are used to move data.
1 = Used when the DMA is used to move data. The TDREand RDRFbits in the status regis-
2
ter are not affected but the I C Interrupt is not asserted when TDREor RDRFare set. The
2
I C interrupt reflects only the error conditions. The assertion of TDREcauses a transmit
DMA request. The assertion of RDRF causes a receive DMA request.
2
[6:5]
I C Controller Operational Mode Select
MODE[1:0] 00 = Master/Slave capable (supports multi-Master arbitration) with 7-bit Slave address
01 = Master/Slave capable (supports multi-Master arbitration) with 10-bit Slave address
10 = Slave Only capable with 7-bit address
11 = Slave Only capable with 10-bit address
[4]
IRM
Interactive Receive Mode
Valid in Slave Mode when software must interpret each received byte before acknowledg-
ing. This bit is useful for processing the data bytes following a General Call Address or if
software wants to disable hardware address recognition.
0 = Acknowledge occurs automatically and is determined by the value of the NAKbit of the
I2CCTL Register.
1 = A receive interrupt is generated for each byte received (address or data). The SCL is
held Low during the acknowledge cycle until software writes to the I2CCTL Register.
The value written to the NAKbit of the I2CCTL Register is output on SDA. This value
allows software to Acknowledge or Not Acknowledge after interpreting the associated
address/data byte.
[3]
GCE
General Call Address Enable
Enables reception of messages beginning with the General Call Address or START byte.
0 = Do not accept a message with the General Call Address or START byte.
1 = Do accept a message with the General Call Address or START byte. When an address
2
match occurs, the GCA and RD bits in the I C Status Register indicates whether the
address matched the General Call Address/START byte or not. Following the General
Call Address byte, software sets the IRMbit that allows software to examine the follow-
ing data byte(s) before acknowledging.
2
PS022010-0811
P R E L I M I N A R Y
I C Mode Register
ZNEO® Z16F Series MCUs
Product Specification
237
Bit
Description (Continued)
[2:1]
SLA[9:8]
Slave Address Bits 9 and 8
Initialize with the appropriate Slave address value when using 10-bit Slave addressing.
These bits are ignored when using 7-bit Slave addressing.
[0]
DIAG
Diagnostic Mode
Selects read back value of the Baud Rate Reload and State registers.
0 = Reading the Baud Rate registers returns the Baud Rate register values. Reading the
2
State Register returns I C Controller state information.
1 = Reading the Baud Rate registers returns the current value of the baud rate counter.
Reading the State Register returns additional state information.
I2C Slave Address Register
The I2C Slave Address Register, shown in Table 122, provides control over the lower
order address bits used in 7-bit and 10-bit Slave address recognition.
2
Table 122. I C Slave Address Register (I2CSLVAD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
SLA[7:0]
00H
R/W
Addr
FF‒E247H
Bit
Description
[7:0]
Slave Address Bits 7–0
SLA[7:0] Initialize with the appropriate Slave address value. When using 7 bit Slave addressing,
SLA[9:7] are ignored.
PS022010-0811
P R E L I M I N A R Y
I2C Slave Address Register
ZNEO® Z16F Series MCUs
Product Specification
238
Watchdog Timer
The Watchdog Timer (WDT) helps protect against corrupt or unreliable software, power
faults and other system-level problems which places the ZNEO® Z16F Series device into
unsuitable operating states.
The WDT includes the following features:
•
•
•
On-chip RC oscillator
A selectable time-out response: short reset or system exception
16-bit programmable time-out value
Operation
The WDT is a retriggerable one-shot timer that resets or interrupts the ZNEO Z16F Series
device, when the WDT reaches its terminal count. The WDT uses its own dedicated on-
chip RC oscillator as its clock source. The WDT has only two modes of operation—on
and off. After enabled, it always counts and must be refreshed to prevent a time-out. An
enable is performed by executing the WDTinstruction or by setting the WDT_AOoption bit.
The WDT_AObit enables the WDT to operate all of the time, even if a WDTinstruction has
not been executed.
To minimize power consumption, the RC oscillator is disabled. The RC oscillator is dis-
abled by clearing the WDTEN bit in the Oscillator Control Register. If the RC oscillator is
disabled, the WDT will not operate.
The WDT is a 16-bit reloadable downcounter that uses two 8-bit registers in the ZNEO
CPU register space to set the reload value. The nominal WDT time-out period is illus-
trated by the following equation:
WDT Reload Value
-----------------------------------------------
WDT Time-out Period (ms) =
10
In the equation above, the WDT reload value is the decimal value of the 16-bit value
yielded by {WDTH[7:0], WDTL[7:0]} and the typical Watchdog Timer RC oscillator fre-
quency is 10kHz. Table 123 provides approximate time-out delays for the minimum,
default and maximum WDT reload values.
PS022010-0811
P R E L I M I N A R Y
Watchdog Timer
ZNEO® Z16F Series MCUs
Product Specification
239
Table 123. Watchdog Timer Approximate Time-Out Delays
WDT Reload WDT Reload
Approximate Time-Out Delay
Value
Value
(with 10 kHz typical WDT oscillator frequency)
(Hex)
0400
FFFF
(Decimal)
1024
Typical
Description
102.4 ms
6.55 s
Reset value time-out delay
Maximum time-out delay
65,536
Watchdog Timer Refresh
When enabled first, the WDT is loaded with the value in the Watchdog Timer Reload reg-
isters. The WDT then counts down to 0000Hunless a WDTinstruction is executed by the
ZNEO CPU. Execution of the WDTinstruction causes the downcounter to be reloaded with
the WDT reload value stored in the Watchdog Timer Reload registers. Counting resumes
following the reload operation.
When the ZNEO Z16F Series device is operating in DEBUG Mode (through the OCD),
the WDT is continuously refreshed to prevent spurious WDT time-outs.
Watchdog Timer Time-Out Response
The WDT times out when the counter reaches 0000H. A time-out of the WDT generates
either a system exception or a short reset. The WDT_RESoption bit determines the time-out
response of the WDT. For information about programming of the WDT_RESoption bit, see
the Option Bits chapter on page 292.
WDT System Exception in Normal Operation
If configured to generate a system exception when a time-out occurs, the WDT issues an
exception request to the interrupt controller. The ZNEO CPU responds to the request by
fetching the System Exception vector and executing code from the vector address. After
time-out and system exception generation, the WDT is reloaded automatically and contin-
ues counting.
WDT System Exception in STOP Mode
If configured to generate a system exception when a time-out occurs and the ZNEO Z16F
Series device is in STOP Mode, the WDT automatically initiates a Stop Mode Recovery
and generates a system exception request. Both the WDT status bit and the STOP bit in the
Reset Status and Control Register are set to 1 following WDT time-out in STOP Mode.
For detailed information, see the Reset and Stop Mode Recovery chapter on page 56.
PS022010-0811
P R E L I M I N A R Y
Watchdog Timer Refresh
ZNEO® Z16F Series MCUs
Product Specification
240
Following completion of the Stop Mode Recovery, the ZNEO CPU responds to the system
exception request by fetching the System Exception vector and executing code from the
vector address.
WDT Reset in Normal Operation
If configured to generate a Reset when a time-out occurs, the WDT forces the device into
the Reset state. The WDTstatus bit in the Reset Status and Control Register is set to 1. For
more information about Reset and the WDT status bit, see the Reset and Stop Mode
Recovery chapter on page 56. Following a Reset sequence, the WDT Counter is initialized
with its reset value.
WDT Reset in STOP Mode
If enabled in STOP Mode and configured to generate a Reset when a time-out occurs and
the device is in STOP Mode, the WDT initiates a Stop Mode Recovery. Both the WDT
status bit and the STOP bit in the Reset Status and Control Register register are set to 1
following WDT time-out in STOP Mode. For detailed information, see the Reset and Stop
Mode Recovery chapter on page 56.
Watchdog Timer Reload Unlock Sequence
Writing the unlock sequence to the Watchdog Timer Reload High (WDTH) register
address unlocks the two Watchdog Timer Reload registers (WDTH and WDTL) to allow
changes to the time-out period. These write operations to the WDTH Register address pro-
duce no effect on the bits in the WDTH Register. The locking mechanism prevents spuri-
ous writes to the reload registers.
The following sequence is required to unlock the Watchdog Timer Reload registers
(WDTH and WDTL) for write access:
1. Write 55Hto the Watchdog Timer Reload High register (WDTH).
2. Write AAHto the Watchdog Timer reload high register (WDTH).
3. Write the appropriate value to the Watchdog Timer reload high register (WDTH).
4. Write the appropriate value to the Watchdog Timer reload low register (WDTL).
All steps of the WDT reload unlock sequence must be written in the order presented
above. The values in the Watchdog Timer Reload registers are loaded into the counter
every time a WDTinstruction is executed.
PS022010-0811
P R E L I M I N A R Y Watchdog Timer Reload Unlock Sequence
ZNEO® Z16F Series MCUs
Product Specification
241
Watchdog Timer Register Definitions
Watchdog Timer Reload High and Low Byte Registers
The Watchdog Timer Reload High and Low Byte (WDTH, WDTL) registers, shown in
Table 124 through Table 125) form the 16-bit reload value that is loaded into the WDT
when a WDTinstruction executes. The 16-bit reload value is {WDTH[7:0], WDTL[7:0]}.
Writing to these registers following the unlock sequence sets the appropriate reload value.
Reading from these registers returns the current WDT count value.
The 16-bit WDT Reload Value must not be set to a value less than 0004H.
Caution:
Table 124. Watchdog Timer Reload High Byte Register (WDTH)
Bits
7
6
5
4
3
2
1
0
Field
WDTH
RESET
R/W
0
0
0
0
0
1
0
0
R/W*
R/W*
R/W*
R/W*
R/W*
R/W*
R/W*
R/W*
Addr
FF_E042H
Note: R/W* = Read returns the current WDT count value. Write sets the appropriate Reload Value.
Bit
Description
[7:0]
WDTH
WDT Reload High Byte
Most significant byte (MSB), Bits[15:8], of the 16-bit WDT reload value.
Table 125. Watchdog Timer Reload Low Byte Register (WDTL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
WDTL
0
0
0
0
0
0
0
0
R/W*
R/W*
R/W*
R/W*
R/W*
R/W*
R/W*
R/W*
Addr
FF_E043H
Note: R/W* = Read returns the current WDT count value. Write sets the appropriate Reload Value.
Bit
Description
[7:0]
WDTL
WDT Reload Low Byte
Least significant byte (LSB), Bits[7:0], of the 16-bit WDT reload value.
PS022010-0811
P R E L I M I N A R Y
Watchdog Timer Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
242
Analog Functions
The ZNEO® Z16F Series devices include a 12-channel Analog-to-Digital Converter
(ADC), an operational amplifier and a comparator.
The features of the analog functions include:
•
ADC with 12 analog input sources multiplexed with General-Purpose Input/Output
(GPIO) ports
•
•
Operational amplifier with output internally connect to the ADC
Comparator with separate inputs or shared with the operational amplifier
Figure 51 displays the block diagram for analog functions.
COMPOUT
+
CINP
Comp
-
START0
ADCEN0
ADCLK
SAMPLE/HOLD0
CINN
+
Op-Amp
-
OPINN
Analog Input
Multiplexer
Analog-to-Digital
Converter0
10
ANA0
ANA1
ANA2
ANA3
ANA4
ANA5
ANA6
ANA7
ANA8
ANA9
Data
Output0
S&H
Amp
Analog Input
BUSY0
Reference Input
Internal Voltage
Reference Generator
VREF
RBUF
ANA10
ANA11
ANAIN0[3:0]
REFEN
SAMPLE/HOLD1
Figure 52. Analog Functions Block Diagram
PS022010-0811
P R E L I M I N A R Y
Analog Functions
ZNEO® Z16F Series MCUs
Product Specification
243
ADC Overview
The ZNEO Z16F Series devices include a 12-channel ADC. The ADC converts an analog
input signal to a 10-bit binary number. The features of the successive approximation ADC
include:
•
•
•
•
•
•
•
•
12 analog input sources multiplexed with GPIO ports
Fast conversion time (2.5s)
Programmable timing controls
Interrupt on conversion complete
Internal voltage reference generator
Internal reference voltage available externally
Ability to supply external reference voltage
Ability to perform simultaneous or independent conversions
Architecture
The architecture as illustrated in Figure 52 consists of a 12-input multiplexer, sample-and-
hold amplifier and 10-bit successive approximation ADC. The ADC digitizes the signal
on selected channel and stores the digitized data in the ADC data registers. In environment
with high electrical noise, an external RC filter must be added at the input pins to reduce
high frequency noise.
Operation
The ADC converts the analog input, ANAx, to a 10-bit digital representation. The equa-
tion for calculating the digital value is:
ADC Output = 1024*(ANAx/VREF)
Assuming zero gain and offset errors, any voltage outside the ADC input limits of AVSS
and VREF returns all 0s or 1s, respectively.
A new conversion is initiated by either software write to the ADC Control register’s
STARTbit or by PWM trigger. For detailed information about the PWM trigger, see the
Synchronization of PWM and ADC section on page 120. Initiating a new conversion stops
any conversion currently in progress and begins a new conversion. To avoid disrupting a
PS022010-0811
P R E L I M I N A R Y
ADC Overview
ZNEO® Z16F Series MCUs
Product Specification
244
conversion already in progress, the STARTbit is read to indicate ADC operation status
(busy or available).
ADC Timing
Each ADC measurement consists of three phases:
1. Input sampling (programmable, minimum of 1.0µs).
2. Sample-and-hold amplifier settling (programmable, minimum of 0.5µs).
3. Conversion is 12 ADCLK cycles.
Figure 53 displays the timing of an ADC conversion.
conversion period
START bit
set by user
cleared by BUSY
1.0 µs min
sample period
Programable
settling period
SAMPLE/HOLD
Internal signal
BUSY
Internal signal
12 clock
convert period
Figure 53. ADC Timing Diagram
Figure 54 displays the timing of convert period showing the 10 bit progression of the out-
put.
PS022010-0811
P R E L I M I N A R Y
ADC Timing
ZNEO® Z16F Series MCUs
Product Specification
245
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17
ADC Clock
BUSY
12 clocks
convert period
Figure 54. ADC Convert Timing
ADC Interrupts
The ADC generates an interrupt request when a conversion has been completed. An inter-
rupt request pending when the ADC is disabled is not automatically cleared.
ADC0 Timer 0 Capture
The Timer 0 count is captured for every ADC0 conversion. The information is used to
determine the zero crossing of back EMF in motor control applications. The capture of the
Timer 0 count occurs when the programmed sample time is complete for every conversion
and stored in the ADC timer capture register (ADCTCAP).
ADC Convert on Read
The ADC is set up to automatically convert the next channel input after reading the results
of the current conversion. The conversions continue up to the channel listed in the
ADC0MAX Register and then start over at the initial channel. The initial channel to con-
vert is written to the control register, ADC0CTL, prior to starting the convert on Read pro-
cess. Once started, the conversions continue to loop from the initial channel to Max
channel until the convert on Read bit, CVTRD0, is cleared or the data is not read from the
data registers.
PS022010-0811
P R E L I M I N A R Y
ADC Interrupts
ZNEO® Z16F Series MCUs
Product Specification
246
Reference Buffer, RBUF
The reference buffer, RBUF, supplies the reference voltage for the ADC. When enabled,
the internal voltage reference generator supplies the ADC and the voltage is available on
the VREF pin. When RBUF is disabled, the reference voltage must be supplied externally
through the VREF pin. RBUF is controlled by the REFENbit in the ADC0 Control Register.
Internal Voltage Reference Generator
The internal voltage reference generator provides the voltage to RBUF. The internal refer-
ence voltage is 2 V.
ADC Control Register Definitions
The following sections describe the control registers for the ADC.
ADC0 Control Register 0
The ADC0 Control Register initiates the A/D conversion and provides ADC0 status infor-
mation.
Table 126. ADC0 Control Register 0 (ADC0CTL)
Bits
7
6
5
REFEN
0
4
ADC0EN
0
3
2
1
0
Field
RESET
R/W
START0 CVTRD0
ANAIN0[3:0]
0
0
0
0
0
0
R/W1
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF‒E500H
Bit
Description
[7]
ADC0 Start/Busy
START0 0 = Writing to 0 has no effect. Reading a 0 indicates the ADC0 is available to begin a conver-
sion.
1 = Writing to 1 starts a conversion on ADC0. Reading a 1 indicates a conversion is currently in
progress.
[6]
Convert On Read
CVTRD0 0 = The ADC0 operates normally.
1 = If this bit is set to 1, whenever the ADC0D Register is read it increments the ANAIN field by
one and start a new conversion. The ANAIN field increments until it reaches the value set
in the ADC0MAX Register. After doing the conversion on the channel specified by the
ADC0MAX Register, the next read resets the ANAIN field to 0. This function is used with
the DMA to perform continuous conversions.
PS022010-0811
P R E L I M I N A R Y
Reference Buffer, RBUF
ZNEO® Z16F Series MCUs
Product Specification
247
Bit
Description (Continued)
Reference Enable
[5]
REFEN 0 = Internal reference voltage is disabled allowing an external reference voltage to be used by
the ADC0.
1 = Internal reference voltage for the ADC0 is enabled. The internal reference voltage is mea-
sured on the VREF pin.
[4]
ADC0 Enable
ADC0EN 0 = ADC0 is disabled for low power operation.
1 = ADC0 is enabled for normal use.
[3:0]
Analog Input Select
ANAIN0 0000 = ANA0 input is selected for analog-to-digital conversion.
0001 = ANA1 input is selected for analog-to-digital conversion.
0010 = ANA2 input is selected for analog-to-digital conversion.
0011 = ANA3 input is selected for analog-to-digital conversion.
0100 = ANA4 input is selected for analog-to-digital conversion.
0101 = ANA5 input is selected for analog-to-digital conversion.
0110 = ANA6 input is selected for analog-to-digital conversion.
0111 = ANA7 input is selected for analog-to-digital conversion.
1000 = ANA8 input is selected for analog-to-digital conversion.
1001 = ANA9 input is selected for analog-to-digital conversion.
1010 = ANA10 input is selected for analog-to-digital conversion.
1011 = ANA11 input is selected for analog-to-digital conversion.
1100 = This bit is reserved and must be programmed to 0.
1111 = This bit is reserved and must be programmed to 0.
ADC0 Data High Byte Register
The ADC0 Data High Byte Register contains the upper eight bits of the ADC0 output.
Access to the ADC0 Data High Byte Register is read-only.
Table 127. ADC0 Data High Byte Register (ADC0D_H)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
ADC0D_H
X
R
Addr
FF‒E502H
Bit
Description
[7:0]
ADC0 High Byte
ADC0D_H 00H–FFH = The last conversion output is held in the data registers until the next ADC con-
version is completed.
PS022010-0811
P R E L I M I N A R Y
ADC0 Data High Byte Register
ZNEO® Z16F Series MCUs
Product Specification
248
ADC0 Data Low Bits Register
The ADC0 Data Low Bits Register contains the lower bits of the ADC0 output. Access to
the ADC0 Data Low Bits Register is Read-Only.
Table 128. ADC0 Data Low Bits Register (ADC0D_L)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
ADC0D_L
Reserved
X
R
X
R
Addr
FF‒E503H
Bit
Description
ADC0 Low Bits
[7:6]
ADC0D_L
00–11b = These bits are the 2 least significant bits of the 10-bit ADC0 output. These bits are
undefined after a Reset.
[5:0]
Reserved
These bits are reserved and must be programmed to 0.
Sample Settling Time Register
The Sample Settling Time Register is used to program the length of time from the SAM-
PLE/HOLD signal to the START signal, when the conversion begins. The number of
clock cycles required for settling varies from system to system depending on the system
clock period used. This register must be programmed to contain the number of clocks
required to meet a 0.5s minimum settling time.
Table 129. Sample and Settling Time (ADCSST)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
SST
1
0
0
0
1
1
1
1
R
R/W
Addr
FF‒E504H
Bit
Description
Reserved
[7:5]
These bits are reserved and must be programmed to 0.
[4:0]
SST
Sample Settling Time
00H–1FH = Sample settling time in number of system clock periods to meet 0.5s minimum.
PS022010-0811
P R E L I M I N A R Y
ADC0 Data Low Bits Register
ZNEO® Z16F Series MCUs
Product Specification
249
Sample Time Register
The Sample Time Register is used to program the length of active time for the sample after
a conversion has begun by setting the STARTbit in the ADC Control Register or initiated
by the PWM. The number of system clock cycles required for sample time varies from
system to system depending on the clock period used. This register must be programmed
to contain the number of system clocks required to meet a 1s minimum sample time.
Table 130. Sample Time (ADCST)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
ST
0
1
1
1
1
1
1
R
R/W
Addr
FF‒E505H
Bit
Description
Reserved
[7:6]
These bits are reserved and must be programmed to 00.
[5:0]
SHT
Sample Hold Time
00H–3FH = Sample Hold time in number of system clock periods to meet 1s minimum.
ADC Clock Prescale Register
The ADC Clock Prescale Register is used to provide a divided system clock to the ADC.
When this register is programmed with 0H, the system clock is used for the ADC Clock.
Table 131. ADC Clock Prescale Register (ADCCP)
Bits
7
6
5
4
3
DIV16
0
2
DIV8
0
1
DIV4
0
0
DIV2
0
Field
RESET
R/W
Reserved
0
R
R/W
Addr
FF‒E506H
Bit
Description
Reserved
[7:4]
These bits are reserved and must be programmed to 0000.
[3]
DIV16
DIV16
0 = Clock is not divided.
1 = System Clock is divided by 16 for ADC Clock.
PS022010-0811
P R E L I M I N A R Y
Sample Time Register
ZNEO® Z16F Series MCUs
Product Specification
250
Bit
Description (Continued)
[2]
DIV8
DIV8
0 = Clock is not divided.
1 = System Clock is divided by 8 for ADC Clock.
[1]
DIV4
DIV4
0 = Clock is not divided.
1 = System Clock is divided by 4 for ADC Clock.
[0]
DIV2
DIV2
0 = Clock is not divided.
1 = System Clock is divided by 2 for ADC Clock.
ADC0 Max Register
The ADC0 Max Register determines the highest channel that the Convert on Read incre-
ments to.
Table 132. ADC0 MAX Register (ADC0MAX)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
0
LASTCHAN0
0H
R/W
FF‒E507H
Addr
Bit
Description
Reserved
[7:4]
These bits are reserved and must be programmed to 0000.
[3:0]
Last Channel 0
LASTCHAN0 0 = These bits determine the last channel number to increment to when the Convert On
Read is set.
PS022010-0811
P R E L I M I N A R Y
ADC0 Max Register
ZNEO® Z16F Series MCUs
Product Specification
251
ADC Timer 0 Capture Register
The ADC Timer 0 Capture Register contains the sixteen bits of the ADC Timer 0 count.
The access to the ADC Timer 0 Capture Register is read-only. It reads 8 bits at a time or as
a 16-bit word.
Table 133. ADC Timer 0 Capture Register, High Byte (ADCTCAP_H)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
ADCTCAPH
X
R
Addr
FF‒E512H
Bit
Description
[7:0]
ADC Timer 0 Count High Byte
ADCTCAPH 00H–FFH = The Timer 0 count is held in the data registers until the next ADC conversion is
started.
Table 134. ADC Timer 0 Capture Register, Low Byte (ADCTCAP_L)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
ADCTCAPL
X
R
Addr
FF‒E513H
Bit
Description
[7:0]
ADC Timer 0 Count Low Byte
ADCTCAPL 00H–FFH = The Timer 0 count is held in the data registers until the next ADC conversion is
started.
Comparator and Operational Amplifier Overview
ZNeo devices feature a general-purpose comparator and an operational amplifier. The
comparator is a moderate speed (200ns propagation delay) device which is designed for a
maximum input offset of 5mV. The comparator is used to compare two analog input sig-
nals. General-purpose input pins (CINP and CINN) provides the comparator inputs. The
output is available as an interrupt source.
PS022010-0811
P R E L I M I N A R Y
ADC Timer 0 Capture Register
ZNEO® Z16F Series MCUs
Product Specification
252
The operational amplifier is a two-input, one-output operational amplifier with a typical
open loop gain of 10,000 (80dB). The general-purpose input pin (OPINP) provides the
noninverting amplifier input, while general-purpose input pin (OPINN) provides the
inverting amplifier input. The output is available at the output pin (OPOUT).
The key operating characteristics of the operational amplifier are:
•
•
•
•
•
•
Frequency compensated for unity gain stability
Input common-mode-range from GND (0.0V) to VDD – 1V
Input offset voltage less than 15mV
Output voltage swing from GND + 0.1V to VDD – 0.1V
Input bias current less than 1A
Operating the operational amplifier open loop (no feedback) effectively provides
another on-chip comparator
Comparator Operation
The comparator output reflects the relationship between the noninverting input and the
inverting (reference) input. If the voltage on the noninverting input is higher than the volt-
age on the inverting input, the comparator output is at a high state. If the voltage on the
noninverting input is lower than the voltage on the inverting input, the comparator output
is at a low state.
To operate, the comparator must be enabled by setting the CMPENbit in the comparator
and op-amp register to 1. In addition the CINP and CINN comparator input alternate func-
tions must be enabled on their respective GPIO pins. For more information, see the GPIO
Alternate Functions section on page 67.
The comparator does not automatically power-down. To reduce operating current when
not in use, the comparator is disabled by clearing the CMPENbit to 0.
Operational Amplifier Operation
To operate, the operational amplifier must be enabled by setting the OPENbit in the com-
parator and op-amp register to 1. In addition, the OPINP, OPINN and OPOUT alternate
functions must be enabled on their respective general-purpose I/O pins. For more informa-
tion, see GPIO Alternate Functions.
The logical value of the operational amplifier output (OPOUT) is read from the Port 3 data
input register if both the operational amplifier and input pin Schmitt trigger are enabled.
For more information, see GPIO Alternate Functions. The operational amplifier generates
an interrupt via the GPIO Port B3 input interrupt, if enabled.
PS022010-0811
P R E L I M I N A R Y
Comparator Operation
ZNEO® Z16F Series MCUs
Product Specification
253
The output of the operational amplifier is also connected to an analog input (ANA3) of the
ADC multiplexer.
The operational amplifier does not automatically power-down. To reduce operating cur-
rent when not in use, the operational amplifier is disabled by clearing the OPEN bit in the
comparator and op-amp register to 0.
When the operational amplifier is disabled, the output is high impedance.
Interrupts
The comparator generates an interrupt on any change in the logic output value (from 0 to 1
and from 1 to 0). For information about enabling and prioritization of the comparator
interrupt, see the Interrupt Controller chapter on page 80.
Comparator Control Register Definitions
The following sections describe the comparator control registers.
Comparator and Operational Amplifier Control Register
The Comparator and Operational Amplifier Control Register (CMPOPC), shown in
Table 135, enables the comparator and operational amplifier and provides access to the
comparator output.
Table 135. Comparator and Op Amp Control Register (CMPOPC)
Bits
7
OPEN
0
6
5
4
3
2
CMPIV
0
1
0
Field
RESET
R/W
Reserved
CPISEL CMPIRQ
CMPOUT CMPEN
00
R
0
0
X
R
0
R/W
R/W
R/W
R/W
R/W
Addr
FF_E510H
Bit
Description
[7]
OPEN
Operational Amplifier Disable
0 = Operational amplifier is disabled.
1 = Operational amplifier is enabled.
[6:5]
Reserved
These bits are reserved and must be programmed to 00.
PS022010-0811
P R E L I M I N A R Y
Interrupts
ZNEO® Z16F Series MCUs
Product Specification
254
Bit
Description (Continued)
Comparator Input Select
[4]
CPISEL 0 = PortB6 provides the comparator - input.
1 = PortC0 provides the comparator - input.
[3]
Comparator Interrupt Edge Select
CMPIRQ 0 = Interrupt Request on Comparator Rising Edge.
1 = Interrupt Request on Comparator Falling Edge.
[2]
CMPIV
PWM Fault Comparator Polarity
0 = PWM Fault is active when cp+ > cp-
1 = PWM Fault is active when cp- > cp+
[1]
Comparator Output Value
CMPOUT 0 = Comparator output is logical 0.
1 = Comparator output is logical 1.
[0]
Comparator Enable
CMPEN 0 = Comparator is disabled.
1 = Comparator is enabled.
PS022010-0811
P R E L I M I N A R Y
Comparator and Operational Amplifier
ZNEO® Z16F Series MCUs
Product Specification
255
Flash Memory
The products in the ZNEO® Z16F Series feature up to 128 KB of nonvolatile Flash
memory with read/write/erase capability. The Flash memory is programmed and erased in-
circuit by either user code or through the OCD.
The Flash memory array is arranged in 2 KB pages. The 2 KB page is the minimum Flash
block size that is erased. The Flash memory is also divided into eight sectors, which is pro-
tected from programming and erase operations on a per sector basis.
Table 136 describes the Flash memory configuration for each device in the ZNEO Z16F
Series. Table 137 lists the sector address ranges. Figure 55 displays the Flash memory
arrangement.
Table 136. Flash Memory Configurations
Pages
Internal
Flash Size
Number of
Pages
Program Memory
Addresses
Number of
Sector Size Sectors
per
Sector
Part Number
Z16F2811
Z16F2810
Z16F6411
Z16F3211
128 KB
128 KB
64 KB
64
64
32
16
000000H–01FFFFH
000000H–01FFFFH
0000H–FFFFH
16 KB
16 KB
8 KB
8
8
8
8
8
8
4
2
32 KB
0000H–7FFFH
4 KB
Table 137. Flash Memory Sector Addresses
Flash Sector Address Ranges
Sector
Number
Z16F2811/Z16F2810
000000H–003FFFH
Z16F6411
Z16F3211
0
1
2
3
4
5
6
7
000000H–001FFFH
002000H–003FFFH
004000H–005FFFH
006000H–007FFFH
008000H–009FFFH
00A000H–00BFFFH
00C000H–00DFFFH
00E000H–00FFFFH
000000H–000FFFH
001000H–001FFFH
002000H–002FFFH
003000H–003FFFH
004000H–004FFFH
005000H–005FFFH
006000H–006FFFH
007000H–007FFFH
004000H–007FFFH
008000H–00BFFFH
00C000H–00FFFFH
010000H–013FFFH
014000H–017FFFH
018000H–01BFFFH
01C000H–01FFFFH
PS022010-0811
P R E L I M I N A R Y
Flash Memory
ZNEO® Z16F Series MCUs
Product Specification
256
128 KB Flash
Program Memory
Addresses
01FFFFH
01F800H
01F7FFH
01F000H
01EFFFH
01E800H
64 Pages
2 KB per Page
0017FFH
001000H
000FFFH
000800H
0007FFH
000000H
Figure 55. Flash Memory Arrangement
Information Area
Table 138 describes the ZNEO Z16F Series Information Area. This 128-byte Information
Area is accessed by setting bit 7 of the Flash Control register to 1. When access is enabled,
the Information Area is mapped into program memory and overlays the 128 bytes at
addresses 000000Hto 00007FH. When the Information Area access is enabled, instruc-
tions access data from the Information Area. The CPU instruction fetches always come
from Main Memory regardless of the Information Area access bit. Access to the Informa-
tion Area is read-only.
PS022010-0811
P R E L I M I N A R Y
Information Area
ZNEO® Z16F Series MCUs
Product Specification
257
Table 138. ZNEO Z16F Series Information Area Map
Program Memory Address (Hex)
000000H–00003FH
Function
Reserved.
000040H–000053H
Part Number: 20-character ASCII alphanumeric code,
left-justified and padded with zeros.
000054H–00007FH
Reserved.
Operation
The Flash Controller provides the proper signals and timing for the Word programming,
Page Erase and Mass erase functions within Flash memory. The Flash Controller contains
a protection mechanism, using the Flash Command Register (FCMD), to prevent acciden-
tal programming or erasure. The following subsections provide details about the various
operations (Lock, Unlock, Sector Protect, Byte Programming, Page Erase and Mass
Erase).
Timing Using the Flash Frequency Register
Before performing a program or erase operation on the Flash memory, you must first
configure the Flash Frequency Register. The Flash Frequency Register allows program-
ming and erasure of the Flash with system clock frequencies ranging from 32 kHz through
20 MHz (the valid range is limited to the device operating frequencies).
The 16-bit Flash Frequency Register must be written with the system clock frequency in
kHz before a program or erase operation is initiated. This value is calculated using the fol-
lowing equation:
System Clock Frequency (Hz)
------------------------------------------------------------------------
FFREQ[15:0] =
1000
Flash programming and erasure is not supported for system clock frequencies below
32kHz, above 20MHz, or outside of the device operating frequency range. The Flash
Frequency Register must be loaded with the correct value to ensure proper Flash pro-
gramming and erase operations.
Caution:
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
258
Flash Read Protection
The user code within the Flash memory is protected from external access. Programming
the Flash Read Protect option bit prevents reading of user code by the OCD or by using the
FLASH CONTROLLER BYPASS Mode. For more information, see the Option Bits
chapter on page 292 and the On-Chip Debugger chapter on page 298.
Flash Write/Erase Protection
The ZNEO Z16F Series provides several levels of protection against accidental program
and erasure of the Flash memory contents. This protection is provided by the Flash Con-
troller unlock mechanism, the Flash Sector Protect register and the Flash Write Protect
option bit.
Flash Controller Unlock Mechanism
At Reset, the Flash Controller locks to prevent accidental program or erasure of the Flash
memory. To program or erase the Flash memory, the Flash controller must be unlocked.
After unlocking the Flash Controller, the Flash is programmed or erased. Any value writ-
ten by user code to the Flash Command Register or Flash Page Select Register out of
sequence locks the Flash Controller.
Observe the following steps to unlock the Flash Controller from user code:
1. Write the page to be programmed or erased to the Flash Page Select Register.
2. Write the first unlock command 73Hto the Flash Command Register.
3. Write the second unlock command 8CHto the Flash Command Register.
Flash Sector Protection
The Flash Sector Protect register is configured to prevent sectors from being programmed
or erased. After a sector is protected, it cannot be unprotected by user code. The Flash Sec-
tor Protect register is cleared after reset and any previously written protection values will
be lost. User code must write this register in their initialization routine if they want to
enable sector protection.
When user code writes the Flash Sector Protect register, bits are set to 1 only. Thus, sectors
are protected, but not unprotected, using register write operations.
Flash Write Protection Option Bit
The Flash Write Protect option bit is enabled to block all program and erase operations
from user code. For more detail, see the Option Bits chapter on page 292.
PS022010-0811
P R E L I M I N A R Y
Flash Read Protection
ZNEO® Z16F Series MCUs
Product Specification
259
Programming
When the Flash Controller is unlocked, word writes to Program memory from user code
programs a word into the Flash if the address is located in the unlocked page. An erased
Flash word contains all ones (FFFFH). The programming operation is used to change bits
from 1 to 0. To change a Flash bit (or multiple bits) from 0 to 1 requires a Page Erase or
Mass Erase operation.
The Flash must be programmed one word (16-bits) at a time. If a byte (8-bit) write to
Flash memory occurs, the Flash controller waits until the other byte within the word is
written before beginning the programming operation.
While the Flash Controller programs the Flash memory, Flash reads are held in wait. If the
CPU is fetching instruction from Flash, the CPU idles until the programming operation is
complete. Interrupts that occur when a programming operation is in progress are serviced
after the programming operation is complete. To exit PROGRAMMING Mode and lock
the Flash Controller, write 00Hto the Flash Command Register.
User code cannot program Flash Memory on a page that lies in a protected sector. When
user code writes memory locations, only addresses located in the unlocked page are pro-
grammed. Memory writes outside of the unlocked page are ignored.
Each memory location must not be programmed more than twice before an erase occurs.
Caution:
Observe the following steps to program the Flash from user code:
1. Write the page of memory to be programmed to the Flash Page Select Register.
2. Write the first unlock command 73Hto the Flash Command Register.
3. Write the second unlock command 8CH to the Flash Command Register.
4. Write a word to Program memory.
5. Repeat step 4 to program additional memory locations on the same page.
6. Write 00Hto the Flash Command Register to lock the Flash Controller.
Page Erase
The Flash memory is erased one page (2 KB) at a time. Page Erasing the Flash memory
sets all words in that page to the value FFFFH. The Flash Page Select Register identifies
the page to be erased. While the Flash Controller executes the Page Erase operation, Flash
reads are held in wait. Interrupts that occur when the Page Erase operation is in progress
will be serviced after the Page Erase operation is complete. When the Page Erase opera-
PS022010-0811
P R E L I M I N A R Y
Programming
ZNEO® Z16F Series MCUs
Product Specification
260
tion is complete, the Flash Controller returns to its locked state. Only pages located in
unprotected sectors are erased.
The four steps to performing a Page Erase operation are:
1. Write the page to be erased to the Flash Page Select Register.
2. Write the first unlock command 73Hto the Flash Command Register.
3. Write the second unlock command 8CHto the Flash Command Register.
4. Write the Page Erase command 95Hto the Flash Command Register.
Mass Erase
The Flash memory cannot be Mass Erased by user code.
Flash Controller Bypass
The Flash Controller is bypassed and the control signals for the Flash memory brought out
to the GPIO pins. Bypassing the Flash Controller allows faster Programming algorithms
by controlling the Flash programming signals directly.
Flash Controller Bypass is recommended for large volume gang programming
applications, which do not require in-circuit programming of the Flash memory.
Flash Controller Behavior using the On-Chip Debugger
The following changes in behavior of the Flash Controller occur when the Flash
Controller is accessed using the On-Chip Debugger:
• The Flash Controller does not have to be unlocked for program and erase operations.
• The Flash Write Protect option bit is ignored.
• The Flash Sector Protect register is ignored for programming and erase operations.
• Programming operations are not limited to the page selected in the Flash Page Select
Register.
• Bits in the Flash Sector Protect register is written to 1 or 0.
• The Flash Page Select Register is written when the Flash Controller is unlocked.
• The Mass Erase command is enabled.
PS022010-0811
P R E L I M I N A R Y
Mass Erase
ZNEO® Z16F Series MCUs
Product Specification
261
Flash Control Register Definitions
Flash Command Register
The Flash Command Register, shown in Table 139, unlocks the Flash Controller for pro-
gramming and erase operations. The Write-only Flash Command Register shares its
address with the Read-only Flash Status Register.
Table 139. Flash Command Register (FCMD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
FCMD
XXH
W
Addr
FF_E060H
Bit
Description
[7:0]
FCMD
Flash Command
73H = First unlock command.
8CH = Second unlock command.
95H = Page erase command.
63H = Mass erase command.
Note: *All other commands, or any commands out of sequence, lock the Flash Controller.
PS022010-0811
P R E L I M I N A R Y
Flash Control Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
262
Flash Status Register
The Flash Status Register, shown in Table 140, indicates the current state of the Flash
Controller. This register is read at any time. The Read-only Flash Status Register shares its
address with the Write-only Flash Command Register.
Table 140. Flash Status Register (FSTAT)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
UNLOCK Reserved
FSTAT
00H
R
0
0
R
R
Addr
FF_E060H
Bit
Description
Unlocked
[7]
UNLOCK This status bit is set when the Flash Controller is unlocked.
0 = Flash Controller locked.
1 = Flash Controller unlocked.
[6]
Reserved
This bit is reserved and must be programmed to 0.
[5:0]
FSTAT
Flash Controller Status
00_0000 = Flash Controller idle.
00_1xxx = Program operation in progress.
01_0xxx = Page erase operation in progress.
10_0xxx = Mass erase operation in progress.
PS022010-0811
P R E L I M I N A R Y
Flash Status Register
ZNEO® Z16F Series MCUs
Product Specification
263
Flash Control Register
The Flash Control Register, shown in Table 141, selects how the Flash memory is
accessed.
Table 141. Flash Control Register (FCTL)
Bits
7
6
5
4
3
Reserved
00H
2
1
0
Field
RESET
R/W
INFO
0
R/W
R
Addr
FF_E061H
Bit
Description
[7]
INFO
Information Area Access
This bit selects access to the information area.
0 = Information Area is not selected.
1 = Information Area is selected. The Information area is mapped into the Program memory
address space at addresses 000000Hthrough 00007FH.
[6:0]
Reserved
These bits are reserved and must be programmed to 0000000.
PS022010-0811
P R E L I M I N A R Y
Flash Control Register
ZNEO® Z16F Series MCUs
Product Specification
264
Flash Sector Protect Register
The Flash Sector Protect Register, shown in Table 142, protects Flash memory sectors
from being programmed or erased from user code. User code can only write bits in this
register to 1 (bits cannot be cleared to 0 by user code).
Table 142. Flash Sector Protect Register (FSECT)
Bits
7
SECT7
0
6
SECT6
0
5
SECT5
0
4
SECT4
0
3
SECT3
0
2
SECT2
0
1
SECT1
0
0
SECT0
0
Field
RESET
R/W
R/W1
R/W1
R/W1
R/W1
R/W1
R/W1
R/W1
R/W1
Addr
FF_E062H
Note: R/W1 = Register is accessible for read operations. Register is written to 1 only (via user code).
Bit
Description
[7:0]
SECTn
Sector Protect
0 = Sector n is programmed or erased from user code.
1 = Sector n is protected and cannot be programmed or erased from user code.
Note: User code write bits from 0 to 1 only.
PS022010-0811
P R E L I M I N A R Y
Flash Sector Protect Register
ZNEO® Z16F Series MCUs
Product Specification
265
Flash Page Select Register
The Flash Page Select (FPAGE) Register, shown in Table 143, selects one of the 64 avail-
able Flash memory pages to be erased or programmed. Each Flash Page contains 2048
words of Flash memory. During a Page Erase operation, all Flash memory locations within
the page will be erased to FFFFH.
Table 143. Flash Page Select Register (FPAGE)
Bits
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Reserved
0H
0
Field
RESET
R/W
Reserved
PAGE
00H
R
00H
R/W
R
Addr
FF_E064–FF_E065H
Bit
Description
Reserved
[15:9]
These bits are reserved and must be programmed to 00000000.
[8:3]
PAGE
Page Select
This 6-bit field selects the Flash memory page for Programming and Page Erase operations.
Program Memory Address[16:11] = FPAGE[8:3] = PAGE[5:0].
[2:0]
Reserved
These bits are reserved and must be programmed to 000.
Flash Frequency Register
The Flash Frequency Register, shown in Table 144, sets the time for Flash program and
erase operations. The 16-bit Flash Frequency Register must be written with the system
clock frequency in kiloHertz. The Flash Frequency value is calculated using the following
equation:
System Clock Frequency
-----------------------------------------------------------
FFREQ[15:0] =
1000
Flash programming and erasure is not supported for system clock frequencies below
32kHz, above 20MHz, or outside of the valid operating frequency range for the device.
The Flash Frequency Register must be loaded with the correct value to ensure proper pro-
gram and erase times.
Caution:
PS022010-0811
P R E L I M I N A R Y
Flash Page Select Register
ZNEO® Z16F Series MCUs
Product Specification
266
Table 144. Flash Frequency Register (FFREQ)
12 11 10
Bits
15
14
13
9
8
7
6
5
4
3
2
1
0
Field
RESET
R/W
FFREQ
0000H
R/W
Addr
FF_E066-FFE067H
Bit
Description
Flash Frequency
[15:0]
FFREQ This value is used to time Flash program and erase operations.
PS022010-0811
P R E L I M I N A R Y
Flash Frequency Register
ZNEO® Z16F Series MCUs
Product Specification
267
DMA Controller
The ZNEO Z16F Series’ four DMA channels are used to transfer data from memory to
memory, memory to peripherals, peripherals to memory, or peripherals to peripherals.
DMA Features
The features of the DMA Controller include:
•
•
Four independent DMA channels.
Memory <=> memory, memory <=> peripheral, peripheral <=> memory, peripheral
<=> peripheral transfers
•
•
•
•
•
DIRECT or LINKED LIST modes of operation
Byte, word, or quad operation
DMA and CPU bandwidth sharing control
Up to 64 K transfers (64 KByte, 64 KWord or 64 KQuad)
External DMA request and DMA acknowledge signals
DMA Block Diagram
Figure 56 shows the blocks that comprise the DMA Controller.
PS022010-0811
P R E L I M I N A R Y
DMA Controller
ZNEO® Z16F Series MCUs
Product Specification
268
Request0
Request EOF0
Channel 0
Acknowledge0
Interrupt0
Channel
MUX
Request1
Request EOF1
Channel 1
Acknowledge1
Interrupt1
(Internal Only)
Channel 2
Request2
Request EOF2
DMA
Bus
Controller
Acknowledge2
Interrupt2
Request3
Request EOF3
Channel 3
Acknowledge3
Interrupt3
CMDVLD
EOFSYNC
RDSTAT
CMDBUS
STATBUS
Memory Bus
Figure 56. DMA Block Diagram
PS022010-0811
P R E L I M I N A R Y
DMA Block Diagram
ZNEO® Z16F Series MCUs
Product Specification
269
DMA Description
The DMA is used to off load the processor from doing repetitive tasks. DMA transfers
data from one memory address to another memory address. Because all peripherals are
mapped in memory, the DMA transfers data to or from peripherals.
The DMA transfers data from the source address to the destination address. This requires a
read and/or write cycle that is generated by the DMA Controller. Each DMA transfer
requires a minimum of two system clock cycles to execute.
The DMA operates in DIRECT or LINKED LIST modes. DIRECT Mode and LINKED
LIST Mode are almost the same. In DIRECT Mode, the software loads the DMA Channel
registers directly. In LINKED LIST Mode, the DMA loads its registers from memory.
DMA Register Description
Each DMA channel consists of a 16-bit control register, a 16-bit transfer length register, a
24-bit destination address register, a 24-bit source address register and a 24-bit list address
register; see Figure 57.
DMA Control (DMACTL)
Transfer Length (TXLN)
Destination Address (DAR)
Source Address (SAR)
List Address (LAR)
Figure 57. DMA Channel Registers
Buffers
A buffer is an allocation of contiguous memory bytes. Buffers are allocated by software to
be used by the DMA. The DMA transfers data to or from buffers. A typical application
would be to send data to serial channels such as I2C, UART and SPI. The data to be sent is
placed in a buffer by software.
PS022010-0811
P R E L I M I N A R Y
DMA Description
ZNEO® Z16F Series MCUs
Product Specification
270
Frames
A frame is a single buffer or a collection of buffers. Frame boundaries spans multiple buf-
fers.
Source Address Register
The source address register (SAR) points to the data to be transferred. Each time a transfer
occurs the SAR is selected to stay fixed or increment/decrement by the size of the transfer
(example 1, 2, 4). If we were sending data to a serial channel, the SAR points to the data to
be transferred and the SAR would be set to increment or decrement depending on the
order of data in the buffer (ascending or desending).
Destination Address Register
The destination address register (DAR) points to the location to store the data transferred
from the address pointed to by the SAR. Each time a transfer occurs the DAR is selected
to stay fixed or increment/decrement by the size of the transfer (for example, 1, 2 and 4).
When sending data to a serial channel, the DAR points to the data register of the serial
channel and is set to a fixed address. Each transfer is then sent to the serial channel data
register because the DAR would not change.
Transfer Length
The Transfer Length Register (TXLN) is used to specify how many transfers must occur
to transfer this buffer. If we were sending bytes to a serial channel, the value of the number
of bytes in the buffer pointed to by the SAR would be placed in this register. Each time a
transfer takes place this register is decremented by one. When the transfer length decre-
ments to 0, the buffer is complete and the DMA either stops or loads new control informa-
tion and addresses. For additional detail, see the Linked List Mode section on page 277.
List Address Register
The list address register (LAR) is only used for LINKED LIST Mode. The LAR points to
a list of descriptors (described in the Linked List Descriptor, Table 145). This descriptor
list contains setup information for each buffer that the DMA will transfer. Linked-list
DMAs reduce the amount of overhead on the CPU to service the DMA.
Descriptor
A descriptor is a 16-byte field in the memory space that must be aligned on 16-byte
boundaries (i.e., the lower 4 bits of the address are 0). Table 145 provides the descriptor
format.
PS022010-0811
P R E L I M I N A R Y
DMA Register Description
ZNEO® Z16F Series MCUs
Product Specification
271
Table 145. Linked List Descriptor
Address
LAR
Even
CONTROL
TXLN
LAR + 02H
LAR + 04H
LAR + 08H
LAR + 0CH
DAR High
SAR High
LAR High
DMA Control Bit Definitions
The following paragraphs explain the control bits of each DMA Channel.
DMAxEN
This bit if set by the CPU enables the DMA Channel for direct operation. Direct operation
uses the addresses and transfer length, which has been directly written to the DMA Chan-
nel by software.
If this bit is set by a descriptor read then LINKED LIST Mode is enabled. Linked list oper-
ation starts when an address is written to the DMAxLAR. This write causes the DMA to
read in the descriptor control value and addresses and place them in the DMA Channel.
LOOP
If the DMA is in LINKED LIST Mode and this bit is set to 1, it prevents the DMA from
updating the descriptor when the buffer is closed. This bit is set to allow lists to loop on
themselves without software intervention.
TXSIZE
The TXSIZE bits set the width of the transfer, as follows:
00 8-bit bytes are transferred on each DMA transfer. The destination and source
addresses increment or decrement by 1 for each transfer if the DSTCTL and/or
SRCCTL is selected for increment or decrement. The transfer length is decremented
by 1 to allow 64Kbytes to be transferred.
01 A 16-bit word is transferred on each DMA transfer. The destination and source
addresses increment or decrement by 2 if the DSTCTL and/or SRCCTL is selected
for increment or decrement. In WORD Mode, the transfer length is still decre-
mented by 1 to allow 64Kwords to be transferred.
10 A 32-bit quad is transferred on each DMA transfer. The destination and source
addresses increment or decrement by 4 if the DSTCTL and/or SRCCTL is selected
for increment or decrement. In QUAD Mode, the transfer length is still decremented
by 1 to allow 64Kquads to be transferred.
PS022010-0811
P R E L I M I N A R Y
DMA Control Bit Definitions
ZNEO® Z16F Series MCUs
Product Specification
272
DSTCTL and SRCCTL Fields
The DSTCTL and SRCCTL fields control the increment or decrement of the source and
destination addresses. The address is set to increment, decrement or not change on each
DMA transfer.
00 = Fixed
01 = Increment
10 = Decrement
11 = Reserved
Interrupt on End Of Buffer (IEOB)
The Interrupt On End Of Buffer bit forces the DMA Channel to generate an interrupt when
the buffer is closed. If the DMA is operating in DIRECT Mode and the TXLN decrements
to the watermark value (see the DMA Watermark section on page 273) and this bit is set,
then an interrupt is also generated.
Transfer List (TXFR)
If the DMA is operating in LINKED LIST MODE and this bit is set, the DMA uses the
next LAR address in the descriptor for the next descriptor address instead of incrementing
the current DMAxLAR address by 16. As a result, the looping of true linked lists with buf-
fers is allowed following the descriptor or transfers to other loops.
End of Frame (EOF)
If this bit is set, the EOF signal is sent to the peripheral on the last transfer in the buffer
(i.e., TXLN == 1). This action signals the peripheral to close the frame (only used for on-
chip peripherals). This bit is also set if a peripheral requests an end of frame before the
buffer transfer is completed.
Halt After This Buffer (HALT)
If this bit is set, then the DMA stops after this buffer is closed. The DMAxLAR points to
the next descriptor, but the descriptor will not be fetched.
Command Status (CMDSTAT)
These four bits are exported to the requesting device on the CMDBUS on the first transfer
of a new buffer. These bits are set by a software write or from the DMA reading the
descriptor. At the end of a buffer, these four bits will convey the status from the peripheral
if the EOF bit is set. See the appropriate Zilog product specification(s) for the definitions
of these commands and statuses.
PS022010-0811
P R E L I M I N A R Y
DMA Control Bit Definitions
ZNEO® Z16F Series MCUs
Product Specification
273
DMA Watermark
When operating in DIRECT Mode, the DMAxLAR[23:16] byte is used as a watermark
interrupt. If these bits are set to any value other than 0, they are compared to the low byte
of the decremented transfer length during a transfer. If the IEOBbit is set and the upper
byte of DMAxTXLN[15:8] is zero and DMAxTXLN[7:0] == DMAxLAR[23:16] then an
interrupt is generated. This function allows the DMA Channel to generate an interrupt
prior to the buffer becoming empty.
DMA Peripheral Interface signals
The DMA uses two input signals, four output signals and two 4-bit buses to communicate
with the peripherals. The input signals are Request (REQ) and Request EOF. The output
signals are Acknowledge (ACK), Command Valid (CMDVLD), End of Frame (EOF-
SYNC) and Read Status (RDSTAT). The two 4-bit buses are Command Bus (CMDBUS)
and Stat Bus (STATBUS).
A DMA transfer is initiated with the Request (REQ). When the DMA is servicing a
Request from a peripheral it will assert its acknowledge signal (ACK) to let the peripheral
know that a transfer is in progress. When the first byte of the transfer is written the CMD-
VLD is asserted and the command bits are placed on the CMDBUS. The peripheral must
latch the command from the bus when it sees this combination of signals.
If the EOFbit is set on the current buffer, then when the TXLN decrements to 0, the EOF-
SYNC signal is asserted on the last data transfer to the peripheral. As a result, the periph-
eral is informed that it has received the last byte in the frame.
After receiving the EOFSYNC signal, the peripheral must assert the Request EOF signal
to the DMA to let the DMA know that the descriptor is closed. This could be immediately
or at some later time if the data transferred still must be processed. For peripherals, which
do not support a Request EOF, the EOFSYNC is tied to Request EOF to terminate the
transfer.
After the Request EOF is asserted the DMA closes the descriptor. The DMA asserts the
ACK and RDSTAT signal, if the descriptor EOF bit is set. The peripheral, if it has status,
places it on the STATBUS. This status is then placed in the descriptor and DMA status bits
when it is closed.
If a peripheral must close a descriptor because of an error or the end of a packet is reached
then it asserts it is Request EOF. If the transfer length is not zero, then the DMA will set
the EOF bit, close the descriptor and generate an interrupt.
PS022010-0811
P R E L I M I N A R Y
DMA Watermark
ZNEO® Z16F Series MCUs
Product Specification
274
Buffer Closure
A DMA buffer closure is requested in two ways. The first is when the transfer length
reaches zero. The second is when the DMA receives a request end of frame from the
peripheral. When either of these cases occur, the DMA begins closure of the buffer.
Loop Mode Closure
If the LOOP bit is set then the current buffer descriptor is not modified. The DMAxLAR
increments or a new LAR value is fetched from the descriptor.
EOF Closure
The DMAxENbit is reset to 0. If the EOFbit is set, the CMDSTAT field is set with the status
data from the peripheral. If the channel is in LINKED LIST Mode then the DMAxCTL
word is written back to the CONTROL word of the descriptor. The DMAxLAR incre-
ments or is loaded with new LAR data from the descriptor if the TXFRbit is set.
Normal Closure
The DMAxENbit is reset to 0. If the channel is in LINKED LIST Mode then the DMAx-
CTL word is written back to the CONTROL word of the descriptor. The DMAxLAR
increments or is loaded with new LAR data from the descriptor if the TXFRbit is set.
DMA Modes
Each DMA channel operates in two modes, direct and linked list. Both modes use the
DMA Channel registers. The only difference is in how they are loaded. In DIRECT Mode,
the DMA Channel registers are directly loaded by software and when the transfer is com-
plete, the DMA stops. In LINKED LIST Mode, the DMA will load its own registers from
a descriptor list which is pointed to by the DMAxLAR Register. It then loads the next
descriptor in the list and continues executing.
The descriptor Control/Status field and address bytes maintain the same format as the con-
trol and address registers in the DMA.
Direct Mode
DIRECT Mode only uses the registers in the DMA for operation. The software writes
these registers directly to set up and enable the DMA. DIRECT Mode is entered by
directly setting the DMAxEN bit in the DMAxCTL0 Register.
Figure 58 displays the DMA registers and how they point to the buffers allocated in mem-
ory.
PS022010-0811
P R E L I M I N A R Y
Buffer Closure
ZNEO® Z16F Series MCUs
Product Specification
275
Memory Map
Destination
Buffer
DMA Channel Registers
DMA Control (DMACTL0,1)
Transfer Length (TXLN)
Destination Address (DAR)
Source Address (SAR)
List Address (LAR)
Source
Buffer
Figure 58. Direct DMA Diagram
PS022010-0811
P R E L I M I N A R Y
DMA Modes
ZNEO® Z16F Series MCUs
Product Specification
276
Direct DMA Setup and Operation
Observe the following steps to set up the DMA in DIRECT Mode:
1. Write the DAMxREQSEL to select the request source.
2. Write the DMAxDAR Register with the destination address.
3. Write the DMAxSAR Register with the source address.
4. Write the DMAxTXLN with the transfer length.
5. Write DMAxLARU with watermark if required, otherwise write to 0.
6. Write DMAxCTL. Note that the control register and the address are written directly
with word and quad operations.
–
–
–
–
–
–
–
–
–
–
DMAxEN, set to 1.
LOOP, reset to 0; not used in this mode.
TXSIZE, set to the transfer size, byte, word or quad.
DSTCTL, set to fixed, increment, or decrement.
SRCCTL, set to fixed, increment, or decrement.
IEOB, set to 1 to generate an interrupt at the end of buffer or watermark.
TXFR, reset to 0; not used in this mode.
EOF, set this bit to 1 if it is an EOF buffer.
HALT, reset to 0; not used in this mode.
CMDSTAT, set these bits with the command for the peripheral.
7. The DMA is now set up and begins operating when it receives a request.
After the DMA is set up and a request is received, the DMA performs the following oper-
ation:
1. Generates a request to the CPU.
2. Transfers data for each request until the transfer length reaches zero or the DMA
receives a Request EOF signal.
3. When the DMA receives the Request EOF signal, or the transfer length reaches 0, it
resets the DMAxENbit, then performs the following operation, based upon the EOFand
IEOBbits:
a. If EOFis set, then the DMA reads the status from the peripheral and places it in the
CMDSTAT field of the DMAxCTL Register.
b. If the IEOBbit is set, or if the buffer ended with a Request EOF, the DMA Chan-
nel generates a request to the CPU.
PS022010-0811
P R E L I M I N A R Y
DMA Modes
ZNEO® Z16F Series MCUs
Product Specification
277
c. If EOFis not set and IEOBis set, then the DMA Channel generates a request to the
CPU.
Linked List Mode
LINKED LIST Mode requires the software to allocate buffers and set up a list of descrip-
tors for each buffer. After allocation is complete, the software writes to the DMAxLAR
Register with the address of the first descriptor. After the DMAxLAR is written, the DMA
reads the first descriptor into the DMA control and address registers, with the exception of
the LAR data. It next executes the transfers as specified by the descriptor data in the
DMA. When these transfers are complete, the DMA reads in the next descriptor in the list
and continues executing transfers. Figure 59 displays two descriptors and two sets of des-
tination and source buffers; it also displays how the descriptors are loaded into the DMA
and executed.
PS022010-0811
P R E L I M I N A R Y
Linked List Mode
ZNEO® Z16F Series MCUs
Product Specification
278
Memory
Destination Pointers
Destination Buffer 0
Destination Buffer 1
Source Pointers
Source Buffer 0
Source Buffer 1
Control/Status
TXLN
DAR
SAR
1rst Descriptor
2nd Descriptor
LAR
Control/Status
TXLN
DAR
SAR
LAR
TXFR Bit Set
Figure 59. Linked List Diagram
PS022010-0811
P R E L I M I N A R Y
Linked List Mode
ZNEO® Z16F Series MCUs
Product Specification
279
Linked List Setup and Operation
The software initially must create the descriptor lists and allocate the buffers for each list.
In addition, software must perform the following operations.
1. Write the DAMxREQSEL to select the appropriate request source.
2. Set the CONTROL field in the descriptor (not the DMA) for the appropriate opera-
tion:
a. DMAxEN: set to 1.
b. LOOP: set to 1 to not have the descriptor modified.
c. TXSIZE: set the appropriate size for byte, word or quad.
d. DSTCTL: set to increment, decrement, or fixed.
e. SRCCTL: set to increment, decrement, or fixed.
f. IEOB: set to 1 if an interrupt must be generated when this descriptor is closed.
g. TXFR: set this bit if the LAR is used to point to the next descriptor.
h. EOF: if an end-of-frame buffer, then set this bit.
i. HALT: if the DMA must stop at the end of this buffer, then set this bit to 1.
j. CMDSTAT: set this field with a command for the selected peripheral.
3. Write the destination address to the destination field.
4. Write the source address to the source field.
5. Write the transfer length for this buffer.
6. If this descriptor has its TXFRbit set then the LAR address to point to the next descrip-
tor.
7. If there are additional descriptors in the list then set them up using the same procedure
listed above.
After the descriptor has been set up, the software must write the DMAxLAR in the appro-
priate DMA with the address of the descriptor. The DMA performs the following opera-
tions:
1. Generate a request to the CPU.
2. Place the DMAxLAR address on the bus and fetch the CONTROL word from the
descriptor. This word is then placed in the DMAxCTL Register of the DMA Channel.
3. Fetch the Destination address from the descriptor and place it in the DMAxDAR Reg-
ister in the DMA Channel.
4. Fetch the Source address from the descriptor and place it in the DMAxSAR Register
in the DMA Channel.
PS022010-0811
P R E L I M I N A R Y
Linked List Mode
ZNEO® Z16F Series MCUs
Product Specification
280
5. Fetch the TXLN length from the descriptor and place it in the DMAxTXLN Register
in the DMA Channel.
6. After the reads have been completed, the DMA starts looking for requests and transfer
data until the transfer length reaches zero or the DMA receives a Request EOF signal.
7. When the DMA receives the Request EOF signal, it performs the following operations
based upon the LOOPand EOFbit:
–
00: The DMA writes the descriptor Control/Status word with the DMAxENbit reset
to 0.
–
01: The DMA requests status from the peripheral. It then writes the descriptor
Control/Status word with the DMAxENbit reset to 0 and the status returned from
the peripheral. The DMA then writes the TXLN length to the descriptor.
–
10, 11: The DMA does not modify the descriptor.
8. If the HALTbit is set the DMA closes the current buffer but does not fetch the next
descriptor.
9. After a new DMAxLAR address has been updated, the DMA returns to Step 2 and
fetches the control/status byte.
DMA Priority
The DMA priority is based upon the last channel serviced. After a channel is serviced it
becomes the lowest priority channel. Table 146 lists the DMA priority; each DMA has
equal priority under this scheme.
PS022010-0811
P R E L I M I N A R Y
DMA Priority
ZNEO® Z16F Series MCUs
Product Specification
281
Table 146. DMA Priority
Last Channel
Serviced
DMA Priority
DMA0
DMA1 (Highest)
DMA2
DMA3
DMA0 (Lowest)
DMA1
DMA2
DMA3
DMA2 (Highest)
DMA3
DMA0
DMA1 (Lowest)
DMA3 (Highest)
DMA0
DMA1
DMA2 (Lowest)
DMA 0 (Highest)
DMA 1
DMA 2
DMA 3 (Lowest)
DMA Bandwidth Selection
In the CPUCTL Register, the DMABW Mode bits set the maximum bus bandwidth the
DMA is allowed. There are four modes (For more details, refer to the ZNEO CPU Core
User Manual (UM0188), available for download at www.zilog.com.
Table 147 lists the DMA bandwidth selection.
Table 147. DMA Bandwidth Selection
Bits
00
Description
DMA uses 100% of the bandwidth.
01
DMA is allowed one transfer for each CPU operation.
DMA is allowed one transfer for every two CPU operations.
DMA is allowed one transfer for every three CPU operations.
10
11
DMA Interrupts
Each DMA has its own interrupt vector. Interrupts occur on the following conditions:
•
Whenever a buffer is completed which has its IEOB set
PS022010-0811
P R E L I M I N A R Y
DMA Interrupts
ZNEO® Z16F Series MCUs
Product Specification
282
•
•
When the upper eight bits of the transfer length equal zero and the lower eight bits of
the transfer length is equal to the DMAxLAR[23:16] and the DMA is in DIRECT Mode
If a buffer has been terminated by a Request EOF
For additional information about interrupts, see the Interrupt Controller chapter on page
80.
DMA Request Select Register
The DMA Request Select Register, shown in Table 148, governs the state of the DMA
Channel.
Table 148. DMA Select Register (DAMxREQSEL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
CHANSTATE
REQSEL
0
0
0
0
0
0
0
0
R
R
R
R
R/W
R/W
R/W
R/W
Addr
FFE400H, FFE401H, FFE402H, FFE403H
Bit
Description
[7:4]
Channel State
CHANSTATE 0000 = DMA Off
0001 = DIRECT Mode, Waiting for End of Frame signal
0010 = LINKED LIST Mode, Waiting for End of Frame signal
0011 = Reserved
0100 = DIRECT Mode, First byte transfer, send command
0101 = LINKED LIST Mode, First byte transfer, send command
0110 = DIRECT Mode, Transfer of buffer in progress
0111 = LINKED LIST Mode, Transfer of buffer in progress
1000 = DIRECT Mode, Close Descriptor
1001 = LINKED LIST Mode, New List
1010 = LINKED LIST Mode, Close Descriptor
1011-1111 = Reserved
PS022010-0811
P R E L I M I N A R Y
DMA Request Select Register
ZNEO® Z16F Series MCUs
Product Specification
283
Bit
Description (Continued)
[3:0]
DMA Request Selection by Channel
REQSEL
DMA0
DMA 0 Request Select
0000 = Continuous (i.e., Memory to Memory)
0001 = Timer 0
0010 = Timer 1
0011 = Timer 2
0100 = UART0 RXD
0101 = UART0 TXD
0110 = UART1 RXD
0111 = UART1 TXD
1000 = I2C RX
1001 = I2C TX
1010 = SPI RX
1011 = SPI TX
1100 = ADC0
1101 = Reserved
1110 = Reserved
1111 = DMA0REQ Pin
DMA1
DMA 1 Request Select
0000 = Continuous (i.e., Memory to Memory)
0001 = Timer 0
0010 = Timer 1
0011 = Timer 2
0100 = UART0 RXD
0101 = UART0 TXD
0110 = UART1 RXD
0111 = UART1 TXD
1000 = I2C RX
1001 = I2C TX
1010 = SPI RX
1011 = SPI TX
1100 = ADC0
1101 = Reserved
1110 = Reserved
1111 = DMA1REQ Pin
PS022010-0811
P R E L I M I N A R Y
DMA Request Select Register
ZNEO® Z16F Series MCUs
Product Specification
284
Bit
Description (Continued)
DMA2
DMA 2 Request Select
0000 = Continuous (i.e., Memory to Memory)
0001 = Timer 0
0010 = Timer 1
0011 = Timer 2
0100 = UART0 RXD
0101 = UART0 TXD
0110 = UART1 RXD
0111 = UART1 TXD
1000 = I2C RX
1001 = I2C TX
1010 = SPI RX
1011 = SPI TX
1100 = ADC0
1101 = Reserved
1110 = Reserved
1111 = DMA2REQ Pin
DMA3
DMA 3 Request Select
0000 = Continuous (i.e., Memory to Memory)
0001 = Timer 0
0010 = Timer 1
0011 = Timer 2
0100 = UART0 RXD
0101 = UART0 TXD
0110 = UART1 RXD
0111 = UART1 TXD
1000 = I2C RX
1001 = I2C TX
1010 = SPI RX
1011 = SPI TX
1100 = ADC0
1101 = Reserved
1110 = Reserved
1111 = Reserved
PS022010-0811
P R E L I M I N A R Y
DMA Request Select Register
ZNEO® Z16F Series MCUs
Product Specification
285
DMA Control Registers
The following section describes the DMA control registers.
DMA Control Register
The DMA Control Register, shown in Table 149, enables and control the DMA transfer.
Table 149. DMA Control Register A (DMAxCTL)
Bits
15
DMAxEN
0
14
LOOP
0
13
12
11
10
9
8
Field
RESET
R/W
TXSIZE
DSTCTL
SRCCTL
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE410H, FFE420H, FFE430H, FFE440H
Bits
7
IEOB
0
6
TXFR
0
5
4
HALT
0
3
2
1
0
Field
RESET
R/W
EOF
0
CMDSTAT
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE411H, FFE421H, FFE431H, FFE441H
Bit
Description
[15]
DMAxEN
DMA X Enable
If this bit is written directly, then NORMAL Mode is executed. If this bit is read in from a
descriptor, then LINKED LIST Mode is executed.
0 = DMA is disabled.
1 = DMA is enabled.
[14]
LOOP
LOOP Mode
0 = Descriptor is modified when the buffer is closed.
1 = Descriptor is not modified when buffer is closed.
[13:12]
TXSIZE
Transfer Size
00 = Byte.
01 = Word.
10 = Quad.
11 = Reserved.
[11:10]
DSTCTL
Destination Control Register
00 = Destination address does not change.
01 = Destination address increments.
10 = Destination address decrements.
11 = Reserved.
PS022010-0811
P R E L I M I N A R Y
DMA Control Registers
ZNEO® Z16F Series MCUs
Product Specification
286
Bit
Description (Continued)
[9:8]
SRCCTL
Source Control Register
00 = Source address does not change.
01 = Source address increments.
10 = Source address decrements.
11 = Reserved.
[7]
IEOB
Interrupt On End Of Buffer
0 = Do not generate an interrupt when the DMA completes this buffer.
1 = Generate interrupt at the end of this buffer.
[6]
TXFR
Transfer To New List Address
This bit is used only in LINKED LIST Mode.
0 = Increment DMAxLAR by 16 at the end of this buffer.
1 = Load the DMAxLAR with the new List Address value from the descriptor.
[5]
EOF
End Of Frame
0 = Not a End Of Frame buffer.
1 = This buffer is the end of the current frame.
[4]
HALT
Halt After This Buffer
This bit is used only in LINKED LIST Mode.
0 = Next descriptor is loaded.
1 = The DMA will halt at the end of this buffer.
[3:0]
Command Status Field
CMDSTAT On the first transfer of a buffer, this field is placed on the CMDBUS and the CMDVALID is
asserted. If the EOFbit is set, the DMA requests a status from the peripheral and places it in
this field. In LINKED LIST Mode, this field is written back to the descriptor. The DMA does
not use this field; it simply passes it on. The definitions of these bits are specified in each
peripheral.
DMA X Transfer Length Register
The DMA X Transfer Length High and Low registers, shown in Tables 150 and 151, form
a 16-bit transfer length. Each of these registers is decremented each time a DMA transfer
occurs.
Table 150. DMA X Transfer Length High Register (DMAxTXLNH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxTXLNH
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE412H, FFE422H, FFE432H, FFE442H
PS022010-0811
P R E L I M I N A R Y
DMA X Transfer Length Register
ZNEO® Z16F Series MCUs
Product Specification
287
Table 151. DMA X Transfer Length Low Register (DMAxTXLNL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxTXLNL
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE413H, FFE423H, FFE433H, FFE443H
DMA Destination Address
The DMA X Destination Address Register Upper, High and Low registers form the desti-
nation address. This address points to the location in which the data from the transfer will
be stored.
Table 152. DMA X Destination Address Register Upper (DMAxDARU)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxDARU
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE415H, FFE425H,FFE435H,FFE445
Table 153. DMA X Destination Address Register High (DMAxDARH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxDARH
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE416H, FFE426H, FFE436H, FFE446H
Table 154. DMA X Destination Address Register Low (DMAxDARL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxDARL
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE417H, FFE427H, FFE437H, FFE447H
PS022010-0811
P R E L I M I N A R Y
DMA Destination Address
ZNEO® Z16F Series MCUs
Product Specification
288
DMA Source Address Registers
The DMA X Source Address Register Upper, High and Low registers form a 24-bit source
address. This address is used to point to the source data for the transfer.
Table 155. DMA X Source Address Register Upper DMAxSARU
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxSARU
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE419H, FFE429H, FFE439H, FFE449H
Table 156. DMA X Source Address Register High (DMAxSARH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxSARH
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE41AH, FFE42AH, FFE43AH, FFE44AH
Table 157. DMA X Source Address Register Low (DMAxSARL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxSARL
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE41BH, FFE42BH, FFE43BH, FFE44BH
PS022010-0811
P R E L I M I N A R Y
DMA Source Address Registers
ZNEO® Z16F Series MCUs
Product Specification
289
DMA List Address Register
The DMA List Address Register is written when the list mode for the DMA is used. This
register contains the address of the current list the DMA is operating on. Writing the
DMAxLARL Register (shown in Table 160) enables the DMA for list operation.
Table 158. DMA X List Address Register Upper DMAxLARU
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxLARU
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE41DH, FFE42DH, FFE43DH, FFE44DH
In DIRECT Mode, this register is used to set a watermark interrupt. This interrupt occurs
when the DMATXLN[15:8] equals 0 and DMAxTXLN[7:0] equals DMAxLARU. Note
when using the watermark the DMAxLARL must not be written.
Table 159. DMA X List Address Register High (DMAxLARH)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxLARH
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE41EH, FFE42EH, FFE43EH, FFE44EH
Table 160. DMA X List Address Register Low (DMAxLARL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DMAxLARL
0
0
0
0
0
0
0
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFE41FH, FFE42FH, FFE43FH, FFE44FH
Writing to the DMAxLARL Register causes the DMA to enter LINKED LIST Mode.
PS022010-0811
P R E L I M I N A R Y
DMA List Address Register
ZNEO® Z16F Series MCUs
Product Specification
290
External DMA Signals
Two external pins are associated with each DMA Channel capable of external transfers
(Channel 3 does not have external DMA capability). They are active Low DMAxREQ and
DMAxACK signals. DMAxACK signals are outputs and DMAxREQ are inputs.
DMAxREQ must be asserted for a minimum of one system clock period to generate one
DMA transfer. DMAxREQ is left asserted for multiple transactions and deasserted after
DMAxACK asserts for the last appropriate transfer.
DMA Timing
External DMA Transfer
Figure 60 shows the read and write timing of external DMA transfers.
Normal Read Cycle
Normal Write Cycle
ADDR[23:0]
DATA[15:0]
CS
RD
WR
WAIT
(From pin)
DMAACK
BHEN/BLEN
Figure 60. External DMA Transfer
PS022010-0811
P R E L I M I N A R Y
External DMA Signals
ZNEO® Z16F Series MCUs
Product Specification
291
External ISA DMA Transfer
Figure 61 shows the read and write timing of external ISA DMA transfers.
ISA Read Cycle
ISA Write Cycle
ADDR[23:0]
DATA[15:0]
CS
RD
WR
WAIT
(From pin)
DMAACK
BHEN/BLEN
Figure 61. External ISA DMA transfer
PS022010-0811
P R E L I M I N A R Y
DMA Timing
ZNEO® Z16F Series MCUs
Product Specification
292
Option Bits
Option bits allow user configuration of certain aspects of the ZNEO® Z16F Series opera-
tion. The feature configuration data is stored in the Program memory and read during
Reset. The features available for control using the option bits are:
•
•
•
•
WDT time-out response selection–interrupt or Reset
WDT enabled at Reset
The ability to prevent unwanted read access to user code in Program memory
The ability to prevent accidental programming and erasure of the user code in Program
memory
•
•
•
Voltage Brown-Out (VBO) configuration—always enabled or disabled during STOP
Mode to reduce STOP Mode power consumption
Oscillator mode selection for high, medium and low power crystal oscillators, or exter-
nal RC oscillator
PWM pin setup for motor control application
Operation
Each time the option bits are programmed or erased, the device must be Reset for the
change to take place. During any reset operation (System Reset, Short Reset, or Stop
Mode Recovery), the option bits are automatically read from the Program memory and
written to Option Configuration registers. The Option Configuration registers control
operation of the device. Option Bit Control Register are loaded before the device exits
Reset and the ZNEO CPU begins code execution. The Option Configuration registers are
not part of the Register file and are not accessible for read or write access.
Option Bit Address Space
The first four bytes of Program Memory at addresses 0000H through 0003H, shown in
Tables 161 and 162, respectively, are reserved for the user option bits. These bytes are
used to configure user specific options. You can change the option bits to meet application
requirements.
Program Memory Address 0000H
Option bits in this space are altered to change the chip configuration at reset.
PS022010-0811
P R E L I M I N A R Y
Option Bits
ZNEO® Z16F Series MCUs
Product Specification
293
Table 161. Option Bits At Program Memory Address 0000H
Bits
7
6
5
4
3
2
1
0
RP
U
Field
RESET
R/W
OSC_SEL[1:0]
WDT_RES WDT_AO VBO_AO DBGUART
FWP
U
U
U
U
U
U
U
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
Program Memory 0000H
Note: U = Unchanged by Reset. R/W = Read/Write.
Bit
Description
[7:6]
Oscillator Mode Selection
OSC_SEL[1:0] 00 = On-chip oscillator configured for use with external RC networks (<4MHz).
01 = Minimum power for use with very low frequency crystals (32kHz to 1.0MHz).
10 = Medium power for use with medium frequency crystals or ceramic resonators
(0.5MHz to 10.0MHz).
11 = Maximum power for use with high frequency crystals (8.0MHz to 20.0MHz). This
setting is the default for unprogrammed (erased) Flash.
[5]
WDT_RES
WDT Reset
0 = WDT time-out generates an interrupt request. Interrupts must be globally enabled for
the ZNEO CPU to acknowledge the interrupt request.
1 = WDT time-out causes a Short Reset. This setting is the default for unprogrammed
(erased) Flash.
[4]
WDT_AO
WDT Always On
0 = WDT is automatically enabled after reset. The WDT oscillator is disabled by clearing
the WDTEN bit in the OSCCTL Register.
1 = WDT is enabled upon execution of the WDTinstruction. The WDT oscillator is disabled
by clearing the WDTEN bit in the OSCCTL Register.
[3]
VBO_AO
Voltage Brown-Out Protection Always On
0 = Voltage Brown-Out protection is disabled in STOP Mode to reduce total power con-
sumption.
1 = Voltage Brown-Out protection is always enabled, including during STOP Mode. This
setting is the default for unprogrammed (erased) Flash.
[2]
DBGUART
Debug UART Enable
0 = The Debug UART option is enabled.
1 = The Debug UART option is disabled.
PS022010-0811
P R E L I M I N A R Y
Option Bit Address Space
ZNEO® Z16F Series MCUs
Product Specification
294
Bit
Description (Continued)
Flash Write Protect
[1]
FWP
0 = Programming, Page Erase and Mass Erase through user code is disabled. Flash
operations are allowed through the On-Chip Debugger.
1 = Programming, Page Erase and Mass Erase are enabled for all of Flash Program
Memory.
[0]
RP
Read Protect
0 = User program code is inaccessible. Limited control features are available through the
OCD.
1 = User program code is accessible. All OCD commands are enabled. This setting is the
default for unprogrammed (erased) Flash.
Program Memory Address 0001H
Option bits in this space are altered to change the chip configuration at reset.
Table 162. Options Bits at Program Memory Address 0001H
Bits
7
6
5
Reserved
U
4
3
2
MCEN
U
1
PWMHI
U
0
PWMLO
U
Field
RESET
R/W
U
U
U
U
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
Program Memory 0001H
Note: U = Unchanged by Reset. R/W = Read/Write.
Bit
Description
Reserved
[7:3]
These Option Bits are reserved for future use and must always be 1. This setting is the default
for unprogrammed (erased) Flash.
[2]
MCEN
Motor Control Enable
0 = Motor control pins are enabled on reset.
1 = Normal Pin operation.
[1]
High Side Off Initial Value
PWMHI 0 = The high side off value is equal to 0.
1 = The high side off value is equal to 1.
[0]
Low Side Off Initial Value
PWMLO 0 = The low side off value is equal to 0.
1 = The low side off value is equal to 1.
PS022010-0811
P R E L I M I N A R Y
Program Memory Address 0001H
ZNEO® Z16F Series MCUs
Product Specification
295
Program Memory Address 0002H
Option Bits in this space are altered to change the chip configuration at reset.
Table 163. Options Bits at Program Memory Address 0002H
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
Reserved
U
U
U
U
U
U
U
U
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
Program Memory 0002H
Note: U = Unchanged by Reset. R/W = Read/Write.
Bit
Description
Reserved
[7:0]
These option bits are reserved for future use and must always be 1. This setting is the default
for unprogrammed (erased) Flash.
Program Memory Address 0003H
Option bits in this space are altered to change the chip configuration at reset.
Table 164. Options Bits at Program Memory Address 0003H
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
ROMLESS 16 LPOPT
Reserved
U
U
U
U
U
U
U
U
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
Program Memory 0003H
Note: U = Unchanged by Reset. R/W = Read/Write.
Bit
Description
[7]
ROMLESS 16 Select
ROMLESS 16 0 = If the device is ROMLESS, the data bus is 8 bits wide and is on Port E[7:0].
1 = If the device is ROMLESS, the data bus is 16 bits wide and is on {Port J[7:0], Port
E[7:0]}
PS022010-0811
P R E L I M I N A R Y
Program Memory Address 0002H
ZNEO® Z16F Series MCUs
Product Specification
296
Bit
Description (Continued)
Low Power Option
[6]
LPOPT
0 = The part will come up in low power mode. The Clock is divided by 8 and Flash
memory will only be accessed the last half of the last cycle of the divide. This reduces
Flash power consumption.
1 = The part will come up normally.
[5:0]
Reserved
These option bits are reserved for future use and must always be 1. This setting is the
default for unprogrammed (erased) Flash.
Information Area
Data in the information area of memory cannot be altered directly. If you wish to alter the
factory settings, it must be done by writing to the Register Address identified. The part
defaults to the factory settings after reset and the registers must be rewritten to have the
user settings in effect. Read the information area address to determine the factory settings.
IPO Trim Registers (Information Area Address 0021H and 0022H)
Tables 165 and 166 define the IPO Trim settings, which are altered after reset by accessing
the IPOTRIM1 and IPOTRIM2 registers.
Table 165. IPO Trim 1 (IPOTRIM1)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
IPO TEMP TRIM
IPO TRIM
L
L
L
L
L
L
L
L
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFFF_FF25H
Note: L = Loaded at Reset. R/W = Read/Write. This register is loaded from Information area on Reset.
Table 166. IPO Trim 2 (IPOTRIM2)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
IPO TRIM
L
L
L
L
L
L
L
L
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFFF_FF26
Note: L = Loaded at Reset. R/W = Read/Write. This register is loaded from Information area on Reset.
PS022010-0811
P R E L I M I N A R Y
Information Area
ZNEO® Z16F Series MCUs
Product Specification
297
ADC Reference Voltage Trim (Information Area Address 0023H)
Table 167 defines the ADC Reference Voltage Trim settings, which are altered after reset
by accessing the ADCTRIM Register.
Table 167. ADC Reference Voltage Trim (ADCTRIM)
Bits
7
6
Reserved
L
5
4
3
2
1
0
Field
RESET
R/W
ADCREF[4:0]
L
L
L
L
L
L
L
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FFFF_FF27
Note: L = Loaded at Reset. R/W = Read/Write. This register is loaded from Information area on Reset.
Bit
Description
[7:5]
Reserved
These bits are reserved and must be programmed to 1.
[4:0]
ADC Reference Trim
ADCREF[4:0] These bits are used to trim the ADC reference voltage generator. If the part is not going to
be trimmed, the value of this register must be F0H.
PS022010-0811
P R E L I M I N A R Y ADC Reference Voltage Trim (Information
ZNEO® Z16F Series MCUs
Product Specification
298
On-Chip Debugger
The ZNEO® Z16F Series products have an integrated On-Chip Debugger (OCD) that pro-
vides the following features:
•
•
•
•
•
•
•
•
Reading and writing memory
Reading and writing CPU registers
Execution of CPU instructions
In-circuit programming and erasing of the Flash
Unlimited number of software breakpoints
Four hardware breakpoints
Instruction execution trace
Single-pin serial communication interface
Architecture
The OCD consists of two main blocks: the transmitter/receiver unit and the debug control
logic. Figure 62 displays the architecture of the OCD.
PS022010-0811
P R E L I M I N A R Y
On-Chip Debugger
ZNEO® Z16F Series MCUs
Product Specification
299
BAUD RATE
DETECTOR &
GENERATOR
TRANSMIT
& RECEIVE
CONTROLLER
RX DATA
TX DATA
SHIFTER
DBG
PIN
DEBUG
CONTROLLER
CPU
Figure 62. On-Chip Debugger Block Diagram
Operation
For effective operation of the device, all power pins (VDD and AVDD) must be supplied
with power and all ground pins (VSS and AVSS) must be properly grounded. The DBG
pin must be connected to VDD through an external pull-up resistor to ensure proper op-
eration.
Caution:
On-Chip Debug Enable
The DBG pin is mainly used for debugging. The OCD is always enabled by default fol-
lowing reset. Disable the OCD after startup and use the DBG pin as a UART or a GPIO
pin if the DBGUARToption bit has been cleared.
To use the DBG pin as a UART or GPIO pin, the OCD must be disabled. The OCD is dis-
abled by clearing the OCDEN bit in the Debug Control Register (DBGCTL). The OCD
cannot be disabled if the OCDLOCK bit in the DBGCTL Register is set.
PS022010-0811
P R E L I M I N A R Y
Operation
ZNEO® Z16F Series MCUs
Product Specification
300
Serial Interface
The DBG pin is used for serial communication. This one-pin interface is a bidirectional
half-duplex open-drain interface that transmits and receives data. Transmit and receive
operations cannot occur simultaneously. The serial data is sent and received using the
asynchronous protocol defined in RS-232. The serial pin is connected to the serial port of
the PC using minimal external hardware. Two different methods for connecting the serial
pin to an RS-232 interface are depicted in Figures 63 and 64.
The serial pin is open-drain and must be connected to VDD through an external pull-up
resistor to ensure proper operation.
V
DD
RS-232
Transceiver
10 k
Diode
RS232 TX
RS232 RX
DBG pin
Figure 63. Interfacing a Serial Pin with an RS-232 Interface, #1 of 2
V
DD
RS-232
Transceiver
Open-Drain
Buffer
10 k
RS232 TX
RS232 RX
DBG pin
Figure 64. Interfacing a Serial Pin with an RS-232 Interface, #2 of 2
Serial Data Format
The data format of the serial interface uses the asynchronous protocol defined in RS-232.
Each character is transmitted as one start bit, eight to nine data bits (least-significant bit
first) and one stop bit; see Figure 65.
PS022010-0811
P R E L I M I N A R Y
Serial Interface
ZNEO® Z16F Series MCUs
Product Specification
301
ST
D0 D1 D2 D3 D4 D5 D6
D7 SP
ST = Start Bit
SP = Stop Bit
D0–D7 = Data Bits
Figure 65. OCD Serial Data Format
Each bit time is of same length. The bit period is set by the baud rate generator.
When the transmitter sends a character, it first sends a Low start bit. The transmitter then
waits one bit time. After the start bit is sent, the transmitter sends the next data bit. The
transmitter sends each data bit in turn, waiting one full bit time before sending the next
data bit. After the last data bit is sent, the transmitter sends a high stop bit for one bit time.
The receiver looks for the falling edge of the start bit. After the receiver sees the start bit is
Low, it waits one half bit time and samples the middle of the start bit. If the middle of the
start bit is High, the receiver considers this as a false start bit. The receiver ignores a false
start bit and searches for another falling edge. If the middle of the start bit is Low, the
receiver considers the start bit valid. The receiver will wait a full bit time from the middle
of the start bit to sample the next data bit. The next data bit is sampled in the middle of the
bit period. The receiver repeats this operation for each data bit, waiting one full bit time to
between sampling each data bit.
After the receiver has sampled the last data bit, it waits one full bit time and sample the
middle of the stop bit. If the stop bit is Low, the receiver detects a framing error.
If the stop bit is High, the data was correctly framed between a start and stop bit. After the
receiver samples the middle of the stop bit, it begins searching for another start bit. To cor-
rect for any bit skew due to error between the transmit and receive baud rate clocks, the
receiver does not wait for the full stop bit to be received before searching for the next start
bit.
Baud Rate Generator
The baud rate generator (BRG) is used to generate a bit clock for transmit and receive
operations. The BRG reload register is automatically configured by the auto-baud detec-
tor, or it is written by software.
The value in the BRG reload register is calculated as:
SYSTEM CLOCK
BAUD RELOAD VALUE =
x 8
BAUD RATE
PS022010-0811
P R E L I M I N A R Y
Baud Rate Generator
ZNEO® Z16F Series MCUs
Product Specification
302
This reload value is the number of system clocks used to transmit and receive eight data
bits.
The BRG has a 16-bit reload counter and is clocked by the system clock. When the OCD
is enabled, this register is limited to 12 bits. The minimum baud rate is calculated using the
following equation:
SYSTEM CLOCK
BAUD RELOAD VALUE =
x 8
BAUD RATE
The minimum baud rate when the OCD is enabled is the system clock frequency divided
by 512. The minimum baud rate is the system clock frequency divided by 8192 when the
OCD is disabled.
For asynchronous operation, the maximum baud rate is roughly the system clock fre-
quency divided by eight (eight clocks per bit). With slow baud rates and clean signals, you
will be able to achieve asynchronous baud rates up to 4 clocks per bit. If data is synchro-
nized with the system clock, the maximum baud rate is the system clock frequency (one
bit per clock). The maximum baud rates are limited by the rise and fall times due to the
cable impedance. Table 168 lists minimum and maximum baud rates for sample crystal
frequencies.
Table 168. OCD Baud Rate Limits
System Clock
Frequency
Maximum
Baud Rate
Minimum Baud Rate
(OCDEN=0)
Minimum Baud Rate
(OCDEN=1)
20.0MHz
1.0MHz
2.5M baud*
125K baud
4096 baud
2442 baud
123 baud
4.0 baud
39,062 baud
1953 baud
64 baud
32.768kHz
Note: *The maximum baud rate is limited by the rise and fall times due to the cable impedance.
Auto-Baud Detector
To operate using various clock frequencies over a range of baud rates, the serial interface
has an auto-baud detector. The auto-baud detector is used to automatically set up the baud
rate generator.
The auto-baud detector is set up to measure one of two different auto-baud characters, 80H
(default) or 0DH. The default auto-baud character 80His compatible with previous Z8
Encore!® debug interfaces. When the OCD is disabled and the DBG pin is being used as a
UART, you can switch to an auto-baud character of 0DH. The 0DHcharacter is the ASCII
carriage return character and is sent using a terminal interface.
When using the auto-baud character 80H, the auto-baud detector measures the period from
the falling edge at the beginning of the start bit to the rising edge at the beginning of data
PS022010-0811
P R E L I M I N A R Y
Auto-Baud Detector
ZNEO® Z16F Series MCUs
Product Specification
303
bit 7. For the auto-baud character 0DH, the auto-baud detector measures the period from
the rising edge at the end of the start bit to the rising edge at the beginning of the stop bit.
This measured value is automatically written to the BRG reload register after the auto-
baud character is received. Once configured, the BRG will generate a bit clock based on
this measured character time.
Line Control
When operating at high speeds, it is appropriate to speed up the rise and fall times of the
single wire bus. Three control bits are used to control the bus rise and fall times, the high
drive strength enable bit, the drive high enable bit and the output enable control bit.
The high drive strength enable bit puts the pin into HIGH DRIVE Mode. For information
about high drive strength, see the Electrical Characteristics chapter on page 336.
If the output enable control bit is set, the line is driven High and Low during transmission.
If the drive high control bit is set, it drives the line high for short periods when transmit-
ting a logic one. This rapidly charges the inherent capacitance of the single wire bus.
If both the output enable and drive high control bits are set, the line is driven high for one
clock cycle when transmitting a one. If the output enable bit is clear and the drive high bit
is set, the line is driven high until the input is detected High or the center of the bit time
occurs, whichever is first.
Logic 0
Logic 1
System Clock
Bus Voltage
Drive High
Output
Driver
High Impedance
{
Drive Low
Figure 66. Output Driver when Drive High and Open Drain Enabled
9-Bit Mode
The serial interface is configured to transmit and receive a ninth data bit. This ninth bit is
used to transmit or receive a software generated parity bit. It is used as an address/data bit
in a multi-node system such as RS-485.
PS022010-0811
P R E L I M I N A R Y
Line Control
ZNEO® Z16F Series MCUs
Product Specification
304
ST
D0 D1 D2 D3 D4 D5 D6 D7 NB SP
ST = Start Bit
SP = Stop Bit
NB = Ninth Bit
D0–D7 = Data Bits
Figure 67. 9-Bit Mode
Start Bit Flow Control
If flow control is required, start bit flow control is used. Start bit flow control requires the
receiving device send the start bit. The transmitter waits for the start bit, then transmit its
data following the start bit.
Receiving
ST
Device
Transmitting
Device
D0 D1 D2 D3 D4 D5 D6 D7 SP
Single Wire
Bus
ST
D0 D1 D2 D3 D4 D5 D6 D7 SP
ST = Start Bit
SP = Stop Bit
D0-D7 = Data Bits
Figure 68. Start Bit Flow Control
If the standard serial port of a PC is used, transmit flow control is enabled on the ZNEO
Z16F Series device. The PC sends the start bit when receiving data by transmitting the
character FFH. Because the FFHcharacter is also received from a nonresponsive device,
space parity (parity bit always zero) must be enabled and used as an acknowledge bit.
Initialization
The OCD ignores any data received until it receives the read revision command 00H. After
the read revision command is received, the remaining debug commands are issued. The
packet CRC is not sent for the first read revision command issued during initialization.
PS022010-0811
P R E L I M I N A R Y
Start Bit Flow Control
ZNEO® Z16F Series MCUs
Product Specification
305
Initialization during Reset
The OCD is initialized during reset by asserting the reset pin, sending the auto-baud char-
acter, and then issuing the read revision command. When the OCD is initialized during
reset, the DBGHALTbit in the OCDCTL Register is automatically set.
Reset Pin
Internal
System Reset
Debug Reset
Debug Pin
80H
00H IDH IDL
Reset Time-Out
Reset Pin Remains Asserted
Figure 69. Initialization During Reset
Debug Lock
The interface has a locking mechanism to prevent user code from disabling the OCD and
using the DBG pin as a UART or GPIO pin. The DBGLOCKbit in the DBGCTL Register
prevents you from disabling the OCD and modifying any register that would inhibit com-
munication with the OCD. The default state of the DBGLOCKbit is set accordingly to the
DBGUARToption bit.
In order to use the DBG pin as a UART or GPIO pin, you must program the DBGUART
option bit to 0 so the OCDLOCKcontrol bit is cleared after reset. After the control register is
unlocked, software then clears the OCDENcontrol bit to use the DBG pin as a UART or
GPIO pin.
If the DBGUARToption bit is cleared and the OCDLOCKcontrol bit is not set, the OCDis still
locked before code has the chance to disable the OCD by initializing the Debugger during
reset and writing the OCDLOCKcontrol bit to 1.
Error Reset
The serial interface has an Auto-Reset mechanism that resets the serial interface when a
Transmit Collision or Receive Framing Error is detected. When a Transmit Collision or
Receive Framing Error is detected when OCDENis set, the OCD aborts any command cur-
PS022010-0811
P R E L I M I N A R Y
Initialization during Reset
ZNEO® Z16F Series MCUs
Product Specification
306
rently in progress, transmits a Serial Break condition for 4096 system clocks and sets the
ABSRCHbit in the DBGCTL Register. This break is sent to ensure the host also detects the
error.
A clock change invalidates the baud reload value. Communication cannot continue until a
new autobaud reload value is set. As a result, the device automatically sends a serial break
to reset the communication link whenever a clock change occurs.
DEBUG HALT Mode
During debugging, it is appropriate to stop the CPU from executing instructions by plac-
ing the device in DEBUG HALT Mode. The operating characteristics of the ZNEO Z16F
Series devices in DEBUG HALT Mode are:
•
•
•
The ZNEO CPU fetch unit stops, idling the ZNEO CPU
All enabled on-chip peripherals operate unless in STOP Mode
Constantly refreshes the WDT, if enabled
Entering DEBUG HALT Mode
The device enters DEBUG HALT Mode by any of the following operations:
•
•
•
Write the DBGHALT bit in the DBGCTL Register to 1 using the OCD interface
ZNEO CPU execution of BRKinstruction (when enabled)
Hardware breakpoint match.
Exiting DEBUG HALT Mode
The device exits DEBUG HALT Mode by any of the following operations:
•
•
•
•
Clearing the DBGHALTbit in the DBGCTL Register to 0
Power-On Reset
Voltage Brown-Out reset
Asserting the RESET pin Low to initiate a Reset
Reading and Writing Memory
Most debugging functions are accomplished by reading and writing control registers. The
OCD hardware has the capability of reading and writing memory when the CPU is run-
ning.
When a read or write request from the OCD hardware occurs, the OCD steals the bus for
the number of cycles required to complete the read or write operation. This bus stealing
PS022010-0811
P R E L I M I N A R Y
DEBUG HALT Mode
ZNEO® Z16F Series MCUs
Product Specification
307
occurs on a per byte basis, not a per command basis. Because the debugger operates seri-
ally, it takes several clock cycles to transmit or receive a character.
If the debugger receives a command to read or write a block of memory, it will not steal
the bus for the entire read or write command. The debugger will only steal the bus for a
short period of time for each data byte. A debug write cycle will occur after a byte has
been received during a write operation. A debug read cycle will occur when the transmit-
ter is empty during a read operation.
Data read from or written to the OCD occurs one byte at a time. Therefore, memory read
and write operations occur one byte at a time. Operations that occur on multi-byte words
does not occur concurrently.
Reading Memory CRC
Because the ZNEO device has such a large memory space and the debug interface is serial,
reading massive amounts of data during debugging is time consuming. The OCD hard-
ware has the capability of calculating a cyclic redundancy check (CRC) on memory to
allow memory caching mechanisms to be used by the host debugging software. This CRC
verifies that the contents of a memory cache has not changed.
When the read CRC command is issued, the OCD hardware steals the CPU bus during the
entire read operation. The length of time it takes to generate the CRC is equal to the
amount of time it takes to read the memory used in the CRC calculation.
The OCD hardware also features the capability of returning separate CRCs for each 4K
block of memory. Software determines these portions of memory, which are modified
when the cache for a large block of memory is invalidated.
Breakpoints
Software Breakpoints
Breakpoints are generated when the CPU executes the BRKinstruction and breakpoints are
enabled. If breakpoints are not enabled, the BRKinstruction will vector to the system
exception vector and set the illegal instruction status bit.
If a Breakpoint is generated, the OCD is configured to automatically enter DEBUG HALT
Mode or to just loop on the instruction. If the OCD is configured to loop on the instruc-
tion, the CPU is still able to service DMA and interrupt requests in the background. Soft-
ware polls the DBGBRKbit of the DBGCTL Register to determine if the OCD has reached
a Breakpoint.
Hardware Breakpoint
There are four hardware breakpoints on the ZNEO Device. When enabled, a breakpoint is
generated when the program counter matches the value in the breakpoint register, or when
PS022010-0811
P R E L I M I N A R Y
Reading Memory CRC
ZNEO® Z16F Series MCUs
Product Specification
308
a memory access occurs at the address in the breakpoint register. A data watchpoint
watches a range of addresses by selecting how many lower address bits are ignored.
Instruction Trace
Trace Overview
The ZNEO has the ability to trace the instruction flow. If enabled, it uses existing Memory
to store the Program Counter data each time a change in execution flow occurs. This
requires you to allocate memory space to hold the trace information.
Trace Events
A trace event occurs anytime a CALL, RET, Interrupt, IRET, TRAP, JP, DJNZ, or Excep-
tion occurs. Trace takes four cycles each time a trace event occurs (five cycles for IRQ,
TRAP and Exceptions).
Trace Buffer
The Trace Buffer is controlled by two registers: Trace Control (TRACECTL) and Trace
Address (TRACEADDR) register. The TRACECTL register is used to enable the trace
and select the size of the Trace Buffer. TRACEADDR selects the starting address for the
trace. The trace address is modulo-n based upon the size of the TRACESEL field in the
TRACECTL Register. The modulo-n is zero aligned, which means that the trace buffer
always wraps to 0 for the selected size. For example, if the TRACEADDR is set to
FFFFB050H and the TRACECTL is set to 81H, the Buffer is located from FFFFB000H to
FFFFB0FFH with the first trace event to be written to FFFFB050H. When the address
reaches FFFFB0FFH it will roll over to FFFFB000H.
Trace buffer sizes are 128, 256, 512, 1024, 2048, 4096, 8192 and 16384 bytes. Each trace
event requires eight bytes giving a minimum of 16 events to a maximum of 2048 events.
Only the Program Counter values are stored. Other information has to be inferred from the
source code by the trace debugger.
Trace Operation
On each trace event the current program counter is placed in memory pointed to by the
TRACEADDR. TRACEADDR increments by 4 and the next state of the program counter
is written to the TRACEADDR. TRACEADDR increments by 4 again. TRACEADDR
always points to the next data to be written. The lower two bits of the TRACEADDR are
always zero.
Extracting Trace Information
The trace information is extracted by reading the data from the selected trace memory
area. The data is then interpreted by the Trace Debugger software.
PS022010-0811
P R E L I M I N A R Y
Instruction Trace
ZNEO® Z16F Series MCUs
Product Specification
309
On-Chip Debugger Commands
The hardware OCD supports several commands for controlling the device. In the
following list of commands, data sent from the host to the OCD is identified by:
DBG <-- Data
Data sent from the OCD back to the host is identified by:
DBG --> Data
Multiple bytes transmitted are represented with double arrows, either <<or >>.
Read Revision. The Read Revision command returns the revision identifier.
DBG <-- 0000_0000
DBG --> RevID[15:8]
DBG --> RevID[7:0]
DBG --> CRC[0:7]
Read Status Register. The Read Status Register command returns the contents of the
OCDSTAT Register.
DBG <-- 0000_0001
DBG --> status[7:0]
DBG --> CRC[0:7]
Read Control Register. The Read Control register command returns the contents of the
OCDCTL Register.
DBG <-- 0000_0010
DBG --> OCDCTL[7:0]
DBG --> CRC[0:7]
Write Control Register. The Write Control register command writes data to the OCDCTL
Register.
DBG <-- 0000_0011
DBG <-- OCDCTL[7:0]
DBG --> CRC[0:7]
Read Registers. The Read registers command returns the contents of CPU registers R15
through R0.
DBG <-- 0000_0100
DBG ->> regdata[31:24]
DBG ->> regdata[23:16]
DBG ->> regdata[15:8]
DBG ->> regdata[7:0]
DBG --> CRC[0:7]
Write Registers. The Write registers command writes data to CPU registers R15 through R0.
DBG <-- 0000_0101
DBG <<- regdata[31:24]
PS022010-0811
P R E L I M I N A R Y
On-Chip Debugger Commands
ZNEO® Z16F Series MCUs
Product Specification
310
DBG <<- regdata[23:16]
DBG <<- regdata[15:8]
DBG <<- regdata[7:0]
DBG --> CRC[0:7]
Read PC. The Read Program Counter command returns the contents of the program counter.
DBG <-- 0000_0110
DBG --> 00h
DBG --> PC[23:16]
DBG --> PC[15:8]
DBG --> PC[7:0]
DBG --> CRC[0:7]
Write PC. The Write Program Counter command writes data to the program counter.
DBG <-- 0000_0111
DBG <-- 00h
DBG <-- PC[23:16]
DBG <-- PC[15:8]
DBG <-- PC[7:0]
DBG --> CRC[0:7]
Read Flags. The Read Flags command returns the contents of the CPU flags.
DBG <-- 0000_1000
DBG --> 00h
DBG --> flags[7:0]
DBG --> CRC[0:7]
Write Instruction. The Write Instruction command writes one word of Op Code to the
CPU.
DBG <-- 0000_1001
DBG <-- opcode[15:8]
DBG <-- opcode[7:0]
DBG --> CRC[0:7]
Read Register. The Read Register command returns the contents of a single CPU register.
DBG <-- {0100,regno[3:0]}
DBG --> regdata[31:24]
DBG --> regdata[23:16]
DBG --> regdata[15:8]
DBG --> regdata[7:0]
DBG --> CRC[0:7]
Write Register. The Write Register command writes data to a single CPU register.
DBG <-- {0101,regno[3:0]}
DBG <-- regdata[31:24]
DBG <-- regdata[23:16]
DBG <-- regdata[15:8]
DBG <-- regdata[7:0]
DBG --> CRC[0:7]
PS022010-0811
P R E L I M I N A R Y
On-Chip Debugger Commands
ZNEO® Z16F Series MCUs
Product Specification
311
Read Memory. The Read memory command reads data from memory. The memory
address is sign extended.
DBG <-- {1000,Size[3:0]}
DBG <-- addr[15:8]
DBG <-- addr[7:0]
DBG ->> 1 to 16 bytes of data
DBG --> CRC[0:7]
Write Memory. The Write memory command writes data to memory. The memory
address is sign extended.
DBG <-- {1001,size[3:0}
DBG <-- addr[15:8]
DBG <-- addr[7:0]
DBG <<- 1 to 16 bytes of data
DBG --> CRC[0:7]
Read Memory. The Read memory command reads data from memory.
DBG <-- {1010,size[3:0}
DBG <-- size[11:4]
DBG <-- 00h
DBG <-- addr[23:16]
DBG <-- addr[15:8]
DBG <-- addr[7:0]
DBG ->> 1 to 4096 bytes of data
DBG --> CRC[0:7]
Write Memory. The Write memory command writes data to memory.
DBG <-- {1011,size[3:0}
DBG <-- size[11:4]
DBG <-- 00h
DBG <-- addr[23:16]
DBG <-- addr[15:8]
DBG <-- addr[7:0]
DBG <<- 1 to 4096 bytes of data
DBG --> CRC[0:7]
Read Memory CRC. The Read memory CRC command computes and return the CRC of
a block of memory.
DBG <-- {1110,BlockCount[3:0]}
DBG <-- BlockCount[11:4]
DBG <-- 00h
DBG <-- addr[23:16]
DBG <-- {addr[15:12],xxxx}
DBG --> MemoryCRC[0:7]
DBG --> MemoryCRC[8:15]
DBG --> CRC[0:7]
MemoryCRCis computed on memory in increments of 4K blocks. The BlockCountfield
determines how many blocks of memory to compute the MemoryCRCon.
PS022010-0811
P R E L I M I N A R Y
On-Chip Debugger Commands
ZNEO® Z16F Series MCUs
Product Specification
312
Read Each Memory CRC. The Read memory CRC command computes and return the
CRC of a block each 4K memory block.
DBG <-- {1111,BlockCount[3:0]}
DBG <-- BlockCount[11:4]
DBG <-- 00h
DBG <-- addr[23:16]
DBG <-- {addr[15:12],xxxx}
DBG ->> MemoryCRC[0:7]
DBG ->> MemoryCRC[8:15]
DBG --> CRC[0:7]
The MemoryCRCis computed on memory in increments of 4K blocks. The CRC is
returned for each 4K block and is reset at the start of each block. The BlockCountfield
determines how many blocks of memory to compute the MemoryCRCon.
The On-Chip Debugger commands are summarized in Table 169.
Table 169. On-Chip Debugger Commands
Disabled by Read Protect
Debug Command
Command Byte
0000–0000
0000–0001
0000–0010
0000–0011
Option Bit
Read Revision
—
—
—
Read OCD Status Register
Read OCD Control Register
Write OCD Control Register
Cannot single step (bit0 has no
effect).
Read Registers (CPU registers R15-R0) 0000–0100
Yes.
Yes.
Yes.
Yes.
Yes.
Yes.
Yes.
Yes.
Write Registers (CPU registers R15-R0)
Read Program Counter
0000–0101
0000–0110
Write Program Counter
0000–0111
Read Flags
0000–1000
Write Instruction
0000–1001
Read Register (single CPU register)
Write Register (single CPU register)
0100–(regno[3:0])
0100–(regno[3:0])
0100–(regno[3:0])
Read Memory (short -address is sign
extended)
Read only unprotected memory loca-
tions.
Note: Unlisted command byte values are reserved.
PS022010-0811
P R E L I M I N A R Y
On-Chip Debugger Commands
ZNEO® Z16F Series MCUs
Product Specification
313
Table 169. On-Chip Debugger Commands (Continued)
Disabled by Read Protect
Option Bit
Debug Command
Command Byte
Write Memory (short -address is sign
extended)
0100–(regno[3:0])
Write only unprotected memory loca-
tions.
Read Memory (long)
1010–size[3:0]
1011–size[3:0]
Read only unprotected memory loca-
tions.
Write Memory (long)
Write only unprotected memory loca-
tions.
Read Memory CRC
1110–BlockCount[3:0]
1111–BlockCount[3:0]
—
—
Read Each Memory CRC
Note: Unlisted command byte values are reserved.
Cyclic Redundancy Check
To ensure transmitted and received data is free of errors, the OCD transmits an 8-bit cyclic
redundancy check (CRC) at the end of each command. The CRC is enabled after the OCD
is initialized, it is not sent with the first read revision command. This CRC is disabled by
clearing the CRCEN bit of the DBGCTL Register.
The CRC is reset at the beginning of each command and is computed on the data received
from and sent to the host. The CRC is calculated using the ATM-8 HEC polynomial
8
2
1
0
x +x +x +x . The CRC is preset to all ones. Data is shifted through the polynomial LSB
first. The resulting CRC is reversed and inverted. The check value is CFh.
Memory Cyclic Redundancy Check
The read memory CRC command computes the CRC on memory in 4K blocks, up to 4K
blocks at a time (16M of data). The Memory CRC is computed using the 16-bit CCITT
16 12
5
0
polynomial x +x +x +x . The CRC is preset to all ones. Data is shifted through the
polynomial LSB first. The resulting CRC is reversed and inverted. The check value is
F0B8h.
UART Mode
When the OCD is disabled, the DBG pin is used as a single pin half-duplex UART. When
the serial interface is in UART Mode, data received on the single wire bus is written to the
Receive Data register. Data written to the Transmit Data register is transmitted on the sin-
gle wire bus. In UART Mode, the auto-baud hardware is used to configure the BRG, or the
baud rate registers are written to set a specific baud rate.
PS022010-0811
P R E L I M I N A R Y
Cyclic Redundancy Check
ZNEO® Z16F Series MCUs
Product Specification
314
The UARTEN control bit must be set to 1 to use the serial interface as a UART. Clearing
the UARTEN control bit to 0 will prevent data received on the DBG pin from being writ-
ten to the Receive Data register. Clearing the UARTEN control bit to 0 also prevents data
written to the Transmit Data register from being transmitted on the single pin interface.
If the UART is disabled, data is still written to the Receive Data register and read from the
Transmit Data register. These actions still generates UART interrupts. The UARTEN con-
trol bit only prevents data from being transmitted to or received from the DBG pin.
Serial Errors
The serial interface detects the following error conditions:
•
•
•
•
Receive framing error (received Stop bit is Low)
Transmit collision (OCD releases the bus high to send a logic 1 and detects it is Low)
Receive overrun (received data before previously received data read)
Receive break detect (10 or more bits Low)
Transmission of data is prevented if the transmit collision, receive framing error, receive
break detect, receive overrun, or Receive Data Register full status bits are set.
Interrupts
The Debug UART generates interrupts during the following conditions:
•
•
•
•
Receive Data register is Full (includes Rx Framing Error and Rx Overrun Error)
Transmit Data register is empty
Auto-Baud Detector loads the BRG (auto-baud character received)
Receive Break detected
DBG Pin as a GPIO Pin
The DBG pin is used as a GPIO pin. The serial interface cannot be used for debugging
when the DBG pin is configured as a GPIO pin. To set up the DBG pin as a GPIO pin,
software must clear the DBGUARToption bit and OCDENcontrol bit.
Software uses the pin as an input by clearing the output enable control bit. The PIN status
bit in Line Control Register (DBGLCR) reflects the state of the DBG pin.
The DBG pin is configured as an output pin by setting the output enable control bit. The
logic state of the IDLE bit in Line Control Register is driven onto the DBG pin.
PS022010-0811
P R E L I M I N A R Y
Serial Errors
ZNEO® Z16F Series MCUs
Product Specification
315
Control Register Definitions
Receive Data Register
The Receive Data Register (DBGRXD), shown in Table 170, holds data received by the
serial UART.
Table 170. Receive Data Register (DBGRXD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RXDATA
XX
R/W
Addr
FF_E080
Bit
Description
[7:0]
Receive Data
RXDATA In UART Mode, data received on the serial interface is transferred from the shift register into
this register. This register is written to simulate data received if the DBG pin is being used by
the OCD.
Transmit Data Register
The Transmit Data Register (DBGTXD), shown in Table 171, holds data to be transmitted
by the serial UART.
Table 171. Transmit Data Register (DBGTXD)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
TXDATA
XX
R/W
Addr
FF_E081
Bit
Description
[7:0]
Transmit Data
TXDATA In UART Mode, data written to this register is transmitted on the serial interface. This register is
read to simulate data transmitted if the DBG pin is being used by the OCD.
PS022010-0811
P R E L I M I N A R Y
Control Register Definitions
ZNEO® Z16F Series MCUs
Product Specification
316
Baud Rate Reload Register
The Baud Rate Reload Register (DBGBR), shown in Table 172, is used to configure the
baud rate of the serial communication stream. This register is automatically set by the
Auto-Baud Detector. This register cannot be written by the CPU when OCDLOCKis set.
Table 172. Baud Rate Reload Register (DBGBR)
Bits
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Field
RESET
R/W
RELOAD
0000H
R/W
Addr
FF_E082-FF_E083
Bit
Description
Baud Rate Reload Value
[7:0]
RELOAD This value is the baud rate reload value used to generate a bit clock. It is calculated as:
SYSTEM CLOCK
RELOAD =
x 8
BAUD RATE
Line Control Register
The Line Control Register (DBGLCR), shown in Table 173, controls the state of the
UART. This register cannot be written by the CPU when OCDLOCKis set.
Table 173. Line Control Register (DBGLCR)
Bits
7
OE
0
6
5
4
TXFC
0
3
NBEN
0
2
NB
0
1
0
PIN
X
Field
RESET
R/W
TDH
0
HDS
0
OUT
1
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R
Addr
FF_E084
Bit
Description
[7]
OE
Output Enable
This bit controls the output driver. If the UART is enabled, this bit controls the output driver dur-
ing transmission only.
0 = Pin is open-drain during UART transmit. Pin behaves as an input if UART is disabled.
1 = Pin is driven during transmission if UART is enabled. Pin is an output if UART is disabled.
PS022010-0811
P R E L I M I N A R Y
Baud Rate Reload Register
ZNEO® Z16F Series MCUs
Product Specification
317
Bit
Description (Continued)
Transmit Drive High
[6]
TDH
This control bit causes the interface to drive the line high when a logic 1 is being transmitted. If
OE is zero, the line stops being driven when the input is high or at the center of the bit, which-
ever is first. If OE is one, the line is driven high for one clock cycle. This bit is ignored if Debug
Mode is zero and the UART is disabled.
0 = Transmit Drive High disabled.
1 = Transmit Drive High enabled.
[5]
HDS
High Drive Strength
This control bit enabled high drive strength for the output driver.
0 = Low Drive Strength
1 = High Drive Strength
[4]
TXFC
Transmitter Start Bit Flow Control
This control bit enables start bit flow control on the transmitter. The transmitter waits until a
remote device sends a start bit before transmitting its data.
0 = Transmitter start bit flow control disabled.
1 = Transmitter start bit flow control enabled.
[3]
NBEN
9-Bit Mode Enable
This control bit enables transmission and reception of a ninth data bit.
0 = Nine bit mode disabled.
1 = Nine bit mode enabled.
[2]
NB
Value Of Ninth Bit
This bit is the value of the ninth data bit. When written, this reflects the ninth data bit that will be
transmitted if nine bit mode is enabled. When read, this bit reflects the value of the ninth bit of
the last nine bit character received.
0 = Ninth bit is zero.
1 = Ninth bit is one.
[1]
OUT
Output State
This control bit sets the state of the output transceiver. If the UART is enabled, this bit must be
set to 1 to idle high. Clearing this bit to 0 when the UART is enabled will transmit a break con-
dition. If the UART is disabled, this logic value will be driven onto the pin if OE is set. This bit is
ignored in Debug Mode.
0 = Transmit Break if UART enabled. Drive Low if UART disabled and output enabled.
1 = Idle High if UART enabled. Drive high if UART disabled and output enabled.
[0]
PIN
Debug Pin
This bit reflects the state of the DBG pin.
0 = DBG pin is Low.
1 = DBG pin is High.
PS022010-0811
P R E L I M I N A R Y
Line Control Register
ZNEO® Z16F Series MCUs
Product Specification
318
Status Register
The Status Register (DBGSTAT), shown in Table 174, contains status information about
the state of the UART.
Table 174. Status Register (DBGSTAT)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
RDRF
0
RXOV
0
RXFE
0
RXBRK
0
TDRE
1
TXCOL
0
RXBUSY TXBUSY
0
0
R/W1C
R/W1C
R/W1C
R/W1C
R/W1S
R/W1C
R
R
Addr
FF_E085
Bit
Description
[7]
RDRF
Receive Data Register Full
This bit reflects the status of the Receive Data register. When data is written to the Receive
Data register, or data is transferred from the shift register to the Receive Data register, this bit
is set to 1. When the Receive Data register is read, this bit is cleared to 0. This bit is also
cleared to 0 by writing a one to this bit.
0 = Receive Data register is empty.
1 = Receive Data register is full.
[6]
RXOV
Receive Overrun
This bit is set when a Receive Overrun occurs. A Receive Overrun occurs when there is data in
the Receive Data register and another byte is written to this register.
0 = Receive Overrun has not occurred
1 = Receive Overrun has occurred.
[5]
RXFE
Receive Framing Error
This bit is set when a Receive Framing error has been detected. This bit is cleared by
writing a one to this bit.
0 = No Framing Error detected.
1 = Receive Framing Error detected.
[4]
Receive Break Detect
RXBRK This bit is set when a Break condition has been detected. This occurs when 10 or more bits
received are Low. This bit is cleared by writing a one to this bit.
0 = No Break detected.
1 = Break detected.
[3]
TDRE
Transmit Data Register Empty
This bit reflects the status of the Transmit Data register. When the Transmit Data register is
written, this bit is cleared to 0. When data from the Transmit Data Register is read or trans-
ferred to the transmit shift register, this bit is set to 1. This bit is written to 1 to abort the trans-
mission of data being held in the Transmit Data Register.
0 = Transmit Data register is full.
1 = Transmit Data register is empty.
PS022010-0811
P R E L I M I N A R Y
Status Register
ZNEO® Z16F Series MCUs
Product Specification
319
Bit
Description (Continued)
Transmit Collision
[2]
TXCOL This bit is set when a Transmit Collision occurs. This bit is cleared by writing a one to this bit.
0 = No collision has been detected.
1 = Transmit Collision has been detected.
[1]
Receiver Busy
RXBUSY This bit is set when the receiver is receiving the data. Multi-master systems uses this bit to
ensure the line is idle before sending the data.
0 = Receiver is idle.
1 = Receiver is receiving data.
[0]
Transmitter Busy
TXBUSY This bit is set when the transmitter is sending the data. This bit is used to determine when to
turn off a transceiver for RS-485 applications.
0 = Transmitter is idle.
1 = Transmitter is sending the data.
Control Register
The Control Register (DBGCTL), shown in Table 175, sets the mode of the serial inter-
face.
Table 175. Control Register (DBGCTL)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
OCDLOCK OCDEN
Reserved
CRCEN UARTEN ABCHAR ABSRCH
1
1
00
R
1
0
0
1
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E086
Bit
Description
[7]
On-Chip Debug Lock
OCDLOCK This bit locks the Debug Control register so it cannot be written by the CPU. This bit is auto-
matically set if the DBGUARToption bit is in its default erased state (one).
0 = Debug Control register unlocked.
1 = Debug Control register locked.
[6]
OCDEN
On-Chip Debug Enable
This bit is set when the OCD is enabled. When this bit is set, received data is interpreted as
debug command. To use the DBG pin as a UART or GPIO pin, this bit must be cleared to 0
by software. This bit cannot be written by the CPU if OCDLOCKis set.
0 = OCD is disabled.
1 = OCD is enabled.
PS022010-0811
P R E L I M I N A R Y
Control Register
ZNEO® Z16F Series MCUs
Product Specification
320
Bit
Description (Continued)
[5:4]
Reserved
These bits are reserved and must be programmed to 00.
[3]
CRCEN
CRC Enable
If this bit is set, a CRC is appended to the end of each debug command. Clearing this bit will
disable transmission of the CRC.
0 = CRC disabled
1 = CRC enabled
[2]
UARTEN
UART Enable
This bit is used to enable or disable the UART. This bit is ignored when OCDENis set.
0 = UART Disabled.
1 = UART Enabled.
[1]
ABCHAR
Auto-Baud Character
This bit selects the character used during auto-baud detection. This bit cannot be written by
the CPU if OCDENis set.
0 = Auto-baud character to be measured is 80H.
1 = Auto-baud character to be measured is 0DH.
[0]
ABSRCH
Auto-Baud Search Mode
This bit enables auto-baud search mode. When this bit is set, the next character received is
measured to set the Baud Rate Reload register. This bit clears itself to 0 after the reload reg-
ister has been written. This bit is automatically set when OCDENis set if a serial communica-
tion error occurs. This bit cannot be written by the CPU if the OCDENbit is set.
0 = Auto-baud search disabled.
1 = Auto-baud search enabled.
PS022010-0811
P R E L I M I N A R Y
Control Register
ZNEO® Z16F Series MCUs
Product Specification
321
OCD Control Register
The OCD Control Register (OCDCTL), shown in Table 176, controls the state of the CPU.
This register puts the CPU in DEBUG HALT Mode, enables breakpoints, or single-steps
an instruction.
Table 176. OCD Control Register (OCDCTL)
Bits
7
6
5
4
3
2
Reserved
000
1
0
STEP
0
Field
RESET
R/W
DBGHALT BRKHALT BRKEN DBGSTOP
0
0
0
0
R/W
R/W
R/W
R/W
R
R/W
Bit
Description
Debug Halt
[7]
DBGHALT Setting this bit to 1 causes the device to enter DEBUG HALT Mode. When in DEBUG HALT
Mode, the CPU stops fetching instructions. Clearing this bit causes the CPU to start running
again. This bit is automatically set to 1 when a breakpoint occurs if the BRKHALT bit is set.
0 = The device is running.
1 = The device is in DEBUG HALT Mode.
[6]
Breakpoint Halt
BRKHALT This bit determines what action the OCD takes when a Breakpoint occurs. If this bit is set to
1, then the DBGHALT bit is automatically set to 1 when a breakpoint occurs. If BRKHALT is
zero, then the CPU will loop on the breakpoint.
0 = CPU loops on current instruction when breakpoint occurs.
1 = A Breakpoint sets DBGHALT to 1.
[5]
BRKEN
Enable Breakpoints
This bit controls the behavior of the BRKinstruction and the hardware breakpoint. By default,
these generate an illegal instruction system trap. If this bit is set to 1, these events generate
a Breakpoint instead of a system trap. The resulting action depends upon the BRKHALT bit.
0 = BRKinstruction and hardware breakpoint generates system trap.
1 = BRKinstruction and hardware breakpoint generates a breakpoint.
[4]
Debug Stop Mode
DBGSTOP This bit controls the system clock behavior in STOP Mode. When set to 1, the system clock
will continue to operate in STOP Mode.
0 = Stop Mode debug disabled. system clock stops in STOP Mode.
1 = Stop Mode debug enabled. system clock runs in STOP Mode.
[3:1]
Reserved
These bits are reserved and must be programmed to 000.
[0]
STEP
Single-Step An Instruction
This bit is used to single step an instruction when in DEBUG HALT Mode. This bit is auto-
matically cleared after an instruction is executed.
0 = Idle
1 = Single Step an Instruction.
PS022010-0811
P R E L I M I N A R Y
OCD Control Register
ZNEO® Z16F Series MCUs
Product Specification
322
OCD Status Register
The OCD Status Register (OCDSTAT), shown in Table 177, reports status information
about the current state of the system.
Table 177. OCD Status Register (OCDSTAT)
Bits
7
6
5
HALT
0
4
STOP
0
3
RPEN
0
2
1
TDRF
0
0
RDRE
1
Field
RESET
R/W
DBGHALT DBGBRK
Reserved
0
0
0
R
R
R
R
R
R
R
R
Bit
Description
[7]
DEBUG HALT Mode
DBGHALT This status bit indicates if the CPU is stopped and in DEBUG HALT Mode.
0 = Device is running.
1 = CPU is in DEBUG HALT Mode.
[6]
DBGBRK
Debug Break
This bit indicates if the CPU has reached a BRKinstruction. This bit is set when a BRK
instruction is executed. It is cleared when the DBGHALT control bit is written to 0.
[5]
HALT
HALT Mode
0 = The device is not in HALT Mode.
1 = The device is in HALT Mode.
[4]
STOP
STOP Mode
0 = The device is not in Stop Mode.
1 = The device is in Stop Mode.
[3]
RPEN
Read Protect Enabled
0 = Memory Read Protect is disabled.
1 = Memory Read Protect is enabled.
[2]
Reserved
This bit is reserved and must be programmed to 0.
[1]
TDRF
Transmit Data Register Full
This bit is set when the Transmit Data Register is full.
0 = Transmit Data register is empty
1 = Transmit Data register is full
[0]
RDRE
Receive Data Register Empty
This bit indicates when the Receive Data Register is empty.
0 = Receive Data register is full.
1 = Receive Data register is empty.
PS022010-0811
P R E L I M I N A R Y
OCD Status Register
ZNEO® Z16F Series MCUs
Product Specification
323
Hardware Breakpoint Registers
The Hardware Breakpoint Register (HWBPn), shown in Table 178, is used to set hardware
breakpoints.
Table 178. Hardware Breakpoint Register (HWBPn)
Bits
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Field
RESET
R/W
PC ST RD WR
MASK
ADDR[23:16]
00H
0
0
0
0
0000
R/W
R/W R/W R/W R/W
R/W
Addr
FF_E090-FF_E091,FF_E094-FF_E095,FF_E098-FF_E099,FF_E09C-FF_E09D
14 13 12 11 10
15
9
8
7
6
5
4
3
2
1
0
Bits
Field
RESET
R/W
ADDR[15:0]
0000H
R/W
Addr
FF_E092-FF_E093,FF_E096-FF_E097,FF_E09A-FF_E09B,FF_E09E-FF_E09F
Bit
Description
[31]
PC
Break on Program Counter Match
This bit will enable the hardware breakpoint.
0 = Break on program counter match disabled.
1 = Break on program counter match enabled.
[30]
ST
Status
This bit is set when a hardware breakpoint occurs.
0 = No breakpoint occurred because this bit was last written to 0.
1 = Breakpoint has occurred or this bit written to 1.
[29]
RD
Break On Data Read
This bit will enable the hardware watchpoint for data reads.
0 = Hardware watchpoint on read disabled.
1 = Hardware Watchpoint on read enabled.
[28]
RW
Break On Data Write
This bit will enable the hardware watchpoint for data writes.
0 = Hardware watchpoint on data write disabled.
1 = Hardware watchpoint on data write enabled.
[27:24]
MASK
Watchpoint Address Mask
The MASK field specifies the number of bits in ADDR to ignore when comparing against
addresses for read and write watchpoints. The mask is set to ignore 0 to 15 of the lower
address bits. This allows the watchpoint to monitor a memory block up to 32K in size.
PS022010-0811
P R E L I M I N A R Y
Hardware Breakpoint Registers
ZNEO® Z16F Series MCUs
Product Specification
324
Bit
Description (Continued)
Breakpoint Address
[23:16]
ADDR[23:16] The address to match when generating a breakpoint.
[15:0]
ADDR[15:0]
Trace Control Register
The Trace Control Register (TRACECTL), shown in Table 179, is used to enable the
Trace operation. It also selects the size of the trace buffer.
Table 179. Trace Control Register (TRACECTL)
Bits
7
TRACEEN
0
6
5
4
3
2
1
TRACESEL
000
0
Field
RESET
R/W
Reserved
0
0
0
0
R/W
R
R
R
R
R/W
Addr
FF_E013
Bit
Description
[7]
Trace Enable
TRACEEN 0 = Trace is disabled.
1 = Traces is enabled
[6:3]
Reserved
This bit is reserved and must be programmed to 0000.
[2:0]
Trace Size Select
TRACESEL 000 – 128 Bytes (16 Events)
001 – 256 Bytes (32 Events)
010 – 512 Bytes (64 Events)
011 – 1024 Bytes (128 Events)
100 – 2048 Bytes (256 Events)
101 – 4096 Bytes (512 Events)
110 – 8192 Bytes (1024 Events)
111 – 16384 Bytes (2048 Events)
PS022010-0811
P R E L I M I N A R Y
Trace Control Register
ZNEO® Z16F Series MCUs
Product Specification
325
Trace Address Register
The Trace Address Register (TRACEADDR), shown in Table 180, points to the next data
trace location.
Table 180. Trace Address (TRACEADDR)
Bits
31
15
30
14
29
13
28
27
26
25
24
23
22
21
20
19
18
17
16
Field
RESET
R/W
Reserved
TRACEADDR[23:16]
00H
R
XXH
R/W
Addr
FF_E014
Bits
12
11
10
9
8
7
6
5
4
3
2
1
0
Field
RESET
R/W
TRACEADDR[15:2]
XXXXH
00
00
R
R/W
Addr
FF_E016
Bit
Description
Reserved
[31:24]
This bit is reserved and must be programmed to 00000000.
[23:16]
TRACEADDR[23:16]
Trace Address
These bits form a 24-bit address used by the trace logic to store the next PC
value to memory.
[15:2]
TRACEADDR[15:2]
[1:0]
These read-only bits are unused.
00
PS022010-0811
P R E L I M I N A R Y
Trace Address Register
ZNEO® Z16F Series MCUs
Product Specification
326
On-Chip Oscillator
The products in the ZNEO® Z16F Series feature an on-chip oscillator for use with external
crystals with frequencies from 32 kHz to 20 MHz. In addition, the oscillator supports
external RC networks with oscillation frequencies up to 4 MHz or ceramic resonators with
oscillation frequencies up to 20 MHz. This oscillator generates the primary system clock
for the internal ZNEO CPU and the majority of the on-chip peripherals. Alternatively, the
XIN input pin also accept a CMOS-level clock input signal (32 kHz to 20 MHz). If an
external clock generator is used, the XOUT pin must be left unconnected.
When configured for use with crystal oscillators or external clock drivers, the frequency of
the signal on the XIN input pin determines the frequency of the system clock (that is, no
internal clock divider). In RC operation, the system clock is driven by a clock divider
(divide by 2) to ensure 50% duty cycle.
Operating Modes
The ZNEO Z16F Series products support four different oscillator modes:
• On-chip oscillator configured for use with external RC networks (<4MHz).
• Minimum power for use with very low frequency crystals (32kHz to 1.0MHz).
• Medium power for use with medium frequency crystals or ceramic resonators (0.5MHz
to 10.0MHz)
• Maximum power for use with high frequency crystals or ceramic resonators (8.0MHz
to 20.0MHz)
The oscillator mode is selected through user-programmable option bits. For more informa-
tion, see the Option Bits chapter on page 292.
Crystal Oscillator Operation
Figure 70 displays a recommended configuration for connection with an external
fundamental mode, parallel-resonant crystal operating at 20MHz. Recommended 20MHz
crystal specifications are provided in Table 181. Resistor R1 is optional and limits total
power dissipation by the crystal. The printed circuit board layout must add no more than 4
pF of stray capacitance to either the XIN or XOUT pins. If oscillation does not occur, it
reduce the values of capacitors C1 and C2 to decrease loading.
PS022010-0811
P R E L I M I N A R Y
On-Chip Oscillator
ZNEO® Z16F Series MCUs
Product Specification
327
On-Chip Oscillator
X
XOUT
IN
R1 = 220
Crystal
C1 = 22 pF
C2 = 22 pF
Figure 70. Recommended 20MHz Crystal Oscillator Configuration
Table 181. Recommended Crystal Oscillator Specifications (20MHz Operation)
Parameter
Frequency
Resonance
Mode
Value
Units
Comments
20
MHz
Parallel
Fundamental
Series Resistance (R )
25
20
7
pF
Maximum
Maximum
Maximum
Maximum
S
Load Capacitance (C )
L
Shunt Capacitance (C )
pF
0
Drive Level
1
mW
PS022010-0811
P R E L I M I N A R Y
Crystal Oscillator Operation
ZNEO® Z16F Series MCUs
Product Specification
328
Oscillator Operation with an External RC Network
Figure 71 displays a recommended configuration for connection with an external
resistor-capacitor (RC) network.
V
DD
R
C
X
IN
Figure 71. Connecting the On-Chip Oscillator to an External RC Network
An external resistance value of 15 k is recommended for oscillator operation with an
external RC network. The minimum resistance value to ensure operation is 10 kThe
typical oscillator frequency is estimated from the values of the resistor (R in k) and
capacitor (C in pF) elements using the following equation:
6
110
--------------------------------
Oscillator Frequency (kHz) =
1.5 R C
Figure 3 displays the typical (3.3 V and 25°C) oscillator frequency as a function of the
capacitor (C in pF) employed in the RC network assuming a 15k external resistor. For
very small values of C, the parasitic capacitance of the oscillator XIN pin and the printed
circuit board must be included in the estimation of the oscillator frequency.
PS022010-0811
P R E L I M I N A R Y Oscillator Operation with an External RC
ZNEO® Z16F Series MCUs
Product Specification
329
1000
900
800
700
600
500
400
300
200
100
0
0
100
200
300
400
500
600
700
800
900
1000
C (pF)
Figure 72. Typical RC Oscillator Frequency as a Function
of the External Capacitance with a 15 kΩ Resistor
PS022010-0811
P R E L I M I N A R Y Oscillator Operation with an External RC
ZNEO® Z16F Series MCUs
Product Specification
330
Oscillator Control
The ZNEO® Z16F Series uses three possible user-selectable clocking schemes:
•
•
•
Trimmable internal precision oscillator
On-chip oscillator using off-chip crystal/resonator or external clock driver
On-chip low-precision Watchdog Timer oscillator
In addition, ZNEO Z16F Series contain clock failure detection and recovery circuitry,
allowing continued operation despite a failure of the primary oscillator.
The on-chip system clock frequency is reduced through a clock divider allowing reduced
dynamic power dissipation. The FLASH is powered down during portions of the clock
period when running slower than 10 MHz.
Operation
This section explains the logic used to select the system clock, divide down the system
clock and handle oscillator failures. A description of the specific operation of each oscilla-
tor is outlined elsewhere in this document. See the Watchdog Timer chapter on page 238,
the Internal Precision Oscillator chapter on page 335 and the On-Chip Oscillator chapter
on page 326.
System Clock Selection
The oscillator control block selects from the available clocks. Table 182 details each clock
source and its usage.
PS022010-0811
P R E L I M I N A R Y
Oscillator Control
ZNEO® Z16F Series MCUs
Product Specification
331
Table 182. Oscillator Configuration and Selection
Clock Source
Internal Precision • 5.5 MHz
Oscillator • High precision possible when
Characteristics
Required Setup
• The reset default.
trimmed
• No external components
required
External Crystal/ • 0 to 20 MHz
• Configure Option Bits for correct external oscilla-
Resonator/
External Clock
Drive
• Very high accuracy (dependent tor mode
on crystal/resonator or external • Unlock and write Oscillator Control Register
source)
(OSCCTL) to enable external oscillator
• Requires external components • Wait for required stabilization time
• Unlock and write Oscillator Control Register
(OSCCTL) to select external oscillator
Internal Watch-
dog Timer Oscil- • Low accuracy
lator • No external components
• 10 kHz nominal
• Unlock and write Oscillator Control Register
(OSCCTL) to enable and select Internal WDT
oscillator
required
• Low power consumption
Unintentional access to the Oscillator Control Register (OSCCTL) stops the chip by
switching to a nonfunctioning oscillator. Accidental alteration of the OSCCTL Register is
prevented by a locking/unlocking scheme. To write the register, unlock it by making two
writes to the OSCCTL Register with the values E7Hfollowed by 18H. A third write to the
OSCCTL Register then changes the value of the register and returns the register to a
locked state. Any other sequence of oscillator control register writes has no effect. The
values written to unlock the register must be ordered correctly, but is not required to be
consecutive. It is possible to access other registers within the locking/unlocking operation.
Clock Selection Following System Reset
The internal precision oscillator is selected following a System Reset. Startup code after
the System Reset changes the system clock source by unlocking and configuring the OSC-
CTL Register. If the LPOPTbit in Program Memory Address 0003His zero, FLASH LOW
POWER Mode is enabled during reset. When FLASH LOW POWER Mode is enabled
during reset, the FLPENbit in the Oscillator Control Register (OSCCTL) will be set and
the DIVfield of the OSCDIV Register will be set to 08H.
PS022010-0811
P R E L I M I N A R Y Clock Selection Following System Reset
ZNEO® Z16F Series MCUs
Product Specification
332
Clock Failure Detection and Recovery
Primary Oscillator Failure
The ZNEO Z16F Series generates a System Exception when a failure of the primary
oscillator occurs if the POFENbit is set in the OSCCTL Register. To maintain system
function in this situation, the clock failure recovery circuitry automatically forces the
Watchdog Timer oscillator to drive the system clock. Although this oscillator runs at a
much lower frequency than the original system clock, the CPU continues to operate,
allowing execution of a clock failure vector and software routines that either remedy the
oscillator failure or issue a failure alert. This automatic switch-over is not available if the
WDT is the primary oscillator.
The primary oscillator failure detection circuitry asserts if the system clock frequency
drops below 1kHz ±50%. For operating frequencies below 2kHz, do not enable the clock
failure circuitry (POFENmust be deserted in the OSCCTL Register).
Watchdog Timer Failure
In the event of a Watchdog Timer oscillator failure, a System Exception is used if the
WDFENbit of the OSCCTL Register is set. This event does not trigger an attendant clock
switch-over, but alerts the CPU of the failure. After a WDT failure, it is no longer possible
to detect a primary oscillator failure.
The Watchdog Timer oscillator failure detection circuit counts system clocks while
looking for a WDT clock. The logic counts 8000 system clock cycles before determining
that a failure occurred. The system clock rate determines the speed at which the WDT
failure is detected. A very slow system clock results in very slow detection times.
If the WDT is the primary oscillator or if the Watchdog Timer oscillator is disabled,
deassert the WDFENbit of the OSCCTL Register.
Oscillator Control Register Definitions
Oscillator Control Register
The Oscillator Control Register (OSCCTL), shown in Table 183, enables or disables the
various oscillator circuits, enables/disables the failure detection/recovery circuitry,
actively powers down the flash and selects the primary oscillator, which becomes the
system clock.
The Oscillator Control Register must be unlocked before writing. Writing the two-step
sequence E7Hfollowed by 18Hto the Oscillator Control Register address unlocks it. The
register locks after completion of a register write to the OSCCTL.
PS022010-0811
P R E L I M I N A R Y
Clock Failure Detection and Recovery
ZNEO® Z16F Series MCUs
Product Specification
333
Table 183. Oscillator Control Register (OSCCTL)
Bits
7
INTEN
1
6
XTLEN
0
5
WDTEN
1
4
POFEN
0
3
WDFEN
0
2
FLPEN
0*
1
0
Field
RESET
R/W
SCKSEL
00
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Addr
FF_E0A0H
Note: *The reset value is 1 if the option bit LPOPT is 0.
Bit
Description
[7]
INTEN
Internal Precision Oscillator Enable
0 = Internal precision oscillator is disabled.
1 = Internal precision oscillator is enabled.
[6]
XTLEN
Crystal Oscillator Enable
0 = Crystal oscillator is disabled.
1 = Crystal oscillator is enabled.
[5]
WDT Oscillator Enable
WDTEN 0 = WDT oscillator is disabled.
1 = WDT oscillator is enabled.
[4]
Primary Oscillator Failure Detection Enable
POFEN 0 = Failure detection and recovery of primary oscillator is disabled. This bit is cleared automat-
ically if a primary oscillator failure is detected.
1 = Failure detection and recovery of primary oscillator is enabled.
[3]
WDT Oscillator Failure Detection Enable
WDFEN 0 = Failure detection of WDT oscillator is disabled.This bit is cleared automatically if a WDT
oscillator failure is detected.
1 = Failure detection of WDT oscillator is enabled.
[2]
FLPEN
Flash Low Power Mode Enable
0 = Flash Low Power Mode is disabled.
1 = Flash Low Power Mode is enabled. The Flash will be powered down during idle periods of
the clock and powered up during Flash reads. This bit must only be set if the frequency of
the primary oscillator source is 8 MHz or lower. The reset value of this bit is controlled by
the LPOPToption bit during reset.
[1:0]
System Clock Oscillator Select
SCKSEL 00 = Internal precision oscillator functions as system clock at 5.6 MHz.
01 = Crystal oscillator or external clock driver functions as system clock.
10 = Reserved.
11 = Watchdog Timer oscillator functions as system clock.
PS022010-0811
P R E L I M I N A R Y
Oscillator Control Register
ZNEO® Z16F Series MCUs
Product Specification
334
Oscillator Divide Register
The Oscillator Divide Register (OSCDIV), shown in Table 184, provides the value to
divide the system clock by. The Oscillator Divide Register must be unlocked before writ-
ing. Writing the two-step sequence E7Hfollowed by 18Hto the Oscillator Control Register
address unlocks it. The register locks after completion of a register write to the OSCDIV.
Table 184. Oscillator Divide Register (OSCDIV)
Bits
7
6
5
4
3
2
1
0
Field
RESET
R/W
DIV
00H*
R/W
Addr
FF_E0A1H
Note: *The reset value is 08H if the option bit LPOPT is 0.
Bit
Value (H) Description
[7:0]
DIV
00H–FFH Oscillator Divide
00H–divider is disabled; all other entries are the divide value for scaling the sys-
tem clock.
PS022010-0811
P R E L I M I N A R Y
Oscillator Divide Register
ZNEO® Z16F Series MCUs
Product Specification
335
Internal Precision Oscillator
The Internal Precision Oscillator (IPO) is designed for use without external components.
Nominal untrimmed accuracy is approximately ±30%. You can manually trim the
oscillator to achieve a ±4% frequency accuracy over the operating temperature and supply
voltage range of the device.
The IPO features include:
•
•
•
•
•
On-chip RC oscillator which does not require external components
Nominal ±30% accuracy without trim or manually trim the oscillator to achieve a ± 4%
Typical output frequency of 5.5296MHz
Trimming possible through Flash option bits with user override
Eliminates crystals or ceramic resonators in applications where high timing accuracy is
not required
Operation
The internal oscillator is an RC relaxation oscillator and has its sensitivity to power supply
variation minimized. By using ratio tracking thresholds, the effect of power supply voltage
is cancelled out. The dominant source of oscillator error is the absolute variance of chip
level fabricated components, such as capacitors. An 8-bit trimming register, incorporated
into the design, allows compensation of absolute variation of oscillator frequency. After it
is calibrated, the oscillator frequency is relatively stable and does not require subsequent
calibration.
By default, the oscillator is configured through the Flash Option bits. However, the user
code overrides these trim values as described in the Option Bits chapter on page 292.
PS022010-0811
P R E L I M I N A R Y
Internal Precision Oscillator
ZNEO® Z16F Series MCUs
Product Specification
336
Electrical Characteristics
All data in this chapter is prequalification and precharacterization and is subject to change.
Absolute Maximum Ratings
Stress greater than those listed in Table 185 may cause permanent damage to the device.
These ratings are stress ratings only. Operation of the device at any condition outside those
indicated in the operational sections of these specifications is not implied. Exposure to
absolute maximum rating conditions for extended periods affects device reliability. For
improved reliability, unused inputs must be tied to one of the supply voltages (VDD or
VSS).
Table 185. Absolute Maximum Ratings
Parameter
Minimum Maximum
Units
C
Notes
Ambient temperature under bias
Storage temperature
–40
–65
–0.3
–0.3
–5
+125
+150
+5.5
+3.6
+5
C
Voltage on any pin with respect to V
V
1
2
SS
Voltage on V pin with respect to V
V
DD
SS
Maximum current on input and/or inactive output pin
Maximum output current from active output pin
µA
mA
–25
+25
100-Pin LQFP Maximum Ratings at –40°C to 70°C
Total power dissipation
1325
368
mW
mA
Maximum current into V or out of V
DD
SS
100-Pin LQFP Maximum Ratings at 70°C to 125°C
Total power dissipation
482
134
mW
mA
Maximum current into V or out of V
DD
SS
80-Pin QFP Maximum Ratings at –40°C to 70°C
Total power dissipation
550
150
mW
mA
Maximum current into V or out of V
DD
SS
80-Pin QFP Maximum Ratings at 70°C to 125°C
Total power dissipation
Notes:
200
mW
1. This voltage applies to 5 V tolerant pins which are Port A, C, D, E, F and G pins (except pins PC0 and PC1).
2. This voltage applies to VDD, AVDD, pins supporting analog input (Ports B and H), Pins PC0 and PC1, RESET,
DBG and XIN pins which are non 5 V tolerant pins.
PS022010-0811
P R E L I M I N A R Y
Electrical Characteristics
ZNEO® Z16F Series MCUs
Product Specification
337
Table 185. Absolute Maximum Ratings (Continued)
Parameter
Maximum current into V or out of V
Minimum Maximum
Units
Notes
56
mA
DD
SS
68-Pin PLCC Maximum Ratings at –40°C to 70°C
Total power dissipation
1.0
W
Maximum current into V or out of V
275
mA
DD
SS
68-Pin PLCC Maximum Ratings at
7
0°C to 125°C
Total power dissipation
500
140
W
Maximum current into V or out of V
mA
DD
SS
64-Pin LQFP Maximum Ratings at –40°C to 70°C
Total power dissipation
1.0
W
Maximum current into V or out of V
275
mA
DD
SS
64-Pin LQFP Maximum Ratings at
7
0°C to 125°C
Total power dissipation
540
150
W
Maximum current into V or out of V
mA
DD
SS
Notes:
1. This voltage applies to 5 V tolerant pins which are Port A, C, D, E, F and G pins (except pins PC0 and PC1).
2. This voltage applies to VDD, AVDD, pins supporting analog input (Ports B and H), Pins PC0 and PC1, RESET,
DBG and XIN pins which are non 5 V tolerant pins.
PS022010-0811
P R E L I M I N A R Y
Absolute Maximum Ratings
ZNEO® Z16F Series MCUs
Product Specification
338
DC Characteristics
Table 186 lists the DC characteristics of the ZNEO® Z16F Series products. All voltages
are referenced to VSS, the primary system ground. Any parameter value in the typical col-
umn is from characterization at 3.3V and 0°C. These values are provided for design guid-
ance only and are not tested in production.
Table 186. DC Characteristics
T = –40°C to 125°C
A
Symbol Parameter
Min
Typ
Max
Units Conditions
V
V
Supply Voltage
2.7
—
3.6
V
DD
IL1
Low Level Input Voltage
–0.3
0.3*V
V
For all input pins except
RESET, DBG, X
DD
IN
V
V
Low Level Input Voltage
–0.3
—
—
0.2*V
5.5
V
V
For RESET, DBG and X
IN
IL2
DD
High Level Input Volt-
age
0.7*V
Port A, C, D, E, F and G
IH1
DD
1
pins except pins PC0 and
PC1
V
V
V
V
V
High Level Input Volt-
age
0.7*V
0.8*V
—
—
—
—
—
—
V
V
+0.3
+0.3
V
V
V
V
V
Port B, H and pins PC0 and
PC1
IH2
DD
DD
DD
High Level Input Volt-
age
RESET, DBG and X pins
IN
IH3
DD
Low Level Output Volt-
age Standard Drive
0.4
I
= 2 mA; V = 3.0V
OL1
OH1
OL2
OL DD
High Output Drive disabled
High Level Output Volt-
age Standard Drive
2.4
—
I
OH
= –2 mA; V = 3.0V
DD
High Output Drive disabled
Low Level Output Volt-
age High Drive
—
0.6
I
OL
= 20 mA; V = 3.3 V
DD
High Output Drive enabled
T = –40°C to +70°C
A
V
V
V
I
High Level Output Volt-
age High Drive
2.4
—
—
—
—
v
—
0.6
—
V
V
I
= –20 mA; V = 3.3 V
OH2
OL3
OH3
OH DD
High Output Drive enabled;
T = –40°C to +70°C
A
Low Level Output Volt-
age High Drive
I
= 15 mA; V = 3.3 V
OL DD
High Output Drive enabled;
TA = +70°C to +125°C
High Level Output Volt-
age High Drive
2.4
–5
V
I
= 15 mA; V = 3.3 V
OH DD
High Output Drive enabled;
TA = +70°C to +125°C
Input Leakage Current
+5
µA
V
V
= 3.6 V;
DD
IL
1
= V or V
IN
DD
SS
Note:
1. This condition excludes all pins that have on-chip pull-ups enabled, when driven Low.
PS022010-0811
P R E L I M I N A R Y
DC Characteristics
ZNEO® Z16F Series MCUs
Product Specification
339
Table 186. DC Characteristics (Continued)
T = –40°C to 125°C
A
Symbol Parameter
Min
Typ
Max
Units Conditions
I
Tri-State Leakage Cur-
rent
–5
—
+5
µA
V
= 3.6 V
TL
DD
2
C
GPIO Port Pad Capaci-
tance
—
8.0
—
pF
PAD
2
C
C
X
X
Pad Capacitance
—
—
30
8.0
—
—
pF
pF
µA
µA
XIN
IN
2
Pad Capacitance
9.5
XOUT
OUT
I
I
Weak Pull-up Current
100
600
350
V
V
= 2.7 V to 3.6 V
= 3.0 V; 25°C
PU
DD
DD
Supply Current in STOP
Mode with VBO enabled
CCS1
I
Supply Current in STOP
Mode with VBO dis-
abled
2
1
µA
µA
V
V
= 3.0 V; 25°C
= 3.0 V; 25°C
CCS2
DD
DD
I
Supply Current in STOP
Mode with VBO dis-
abled and WDT dis-
abled
CCS3
CCA
CCH
I
I
Active I
at 20MHz
—
—
18
4
35
6
mA Typ: V =3.0 V/30°C
DD
DD
Max: V =3.6 V/125°C
Peripherals enabled, no
loads
DD
I
in HALT Mode at
mA Typ: V =3.0 V/30°C
DD
DD
20MHz
Max: V =3.6 V/125°C
DD
Peripherals off, no loads
Note:
1. This condition excludes all pins that have on-chip pull-ups enabled, when driven Low.
PS022010-0811
P R E L I M I N A R Y
DC Characteristics
ZNEO® Z16F Series MCUs
Product Specification
340
Figure 73 displays the typical current consumption while operating at 3.3 V at 30 ºC ver-
sus the system clock frequency.
Active Idd vs CLK Freq at 30 ºC
35
30
25
20
15
10
5
0
0
5
10
15
20
25
CLK Freq (MHz)
Vdd=2.6V
Vdd=3.0V
Vdd=3.3V
Vdd=3.7V
Figure 73. Typical I
Versus System Clock Frequency
DD
PS022010-0811
P R E L I M I N A R Y
DC Characteristics
ZNEO® Z16F Series MCUs
Product Specification
341
Figure 74 displays typical current consumption while operating at 3.3V at 30ºC in HALT
Mode versus the system clock frequency.
Halt Idd vs CLK Freq at 30 ºC
6
5
4
3
2
1
0
0
5
10
15
20
25
CLK Freq (MHz)
Vdd=2.6V
Vdd=3.0V
Vdd=3.3V
Vdd=3.7V
Figure 74. Typical HALT Mode I
Versus System Clock Frequency
DD
PS022010-0811
P R E L I M I N A R Y
DC Characteristics
ZNEO® Z16F Series MCUs
Product Specification
342
Figure 75 displays the STOP Mode current consumption versus VDD at ambient tempera-
ture with VBO and WDT disabled (ICCS2).
Figure 75. STOP Mode Current Versus V
DD
PS022010-0811
P R E L I M I N A R Y
DC Characteristics
ZNEO® Z16F Series MCUs
Product Specification
343
On-Chip Peripheral AC and DC Electrical Characteristics
Table 187 lists the POR and VBO electrical characteristics and timing. Table 188 lists the
Reset and Stop Mode Recovery pin timing.
Table 187. POR and VBO Electrical Characteristics and Timing
T = –40°C to 125°C
A
1
Symbol Parameter
Min
Typ
Max
Units Conditions
V
Power-On Reset voltage
threshold
2.20
2.45
2.70
V
V
= V
POR
DD
POR
V
Voltage Brown-Out reset
voltage threshold
2.15
2.40
50
2.65
V
V
= V
VBO
DD
VBO
V
–V
100
—
mV
V
POR
VBO
Starting V voltage to
—
—
V
SS
DD
ensure valid POR
T
Power-On Reset analog
delay
50
—
—
ms
µs
V
> V
; T
Digital
ANA
DD
POR POR
Reset delay follows T
ANA
T
Power-On Reset digital
delay
—
12
10
—
66 IPO cycles
POR
T
T
Voltage Brown-Out pulse
rejection period
—
—
ms
ms
V
Reset
< V
to generate a
VBO
DD
VBO
Time for V to transition
0.10
100
RAMP
DD
from V to V
to
SS
POR
ensure valid Reset
I
Supply current
500
µA
V
= 3.3 V.
DD
CC
Note:
1. Data in the typical column is from characterization at 3.3 V and 0°C. These values are provided for design guid-
ance only and are not tested in production.
Table 188. Reset and Stop Mode Recovery Pin Timing
T = –40°C to 125°C
A
Symbol Parameter
Min
Typ
Max
Units Conditions
Not in STOP Mode.
= System Clock period.
T
RESET pin assertion to
4
—
—
T
CLK
RESET
initiate a System Reset
T
CLK
T
Stop Mode Recovery
pin Pulse Rejection
Period
10
20
40
ns
RESET, DBG and GPIO pins
configured as SMR sources.
SMR
PS022010-0811
P R E L I M I N A R Y On-Chip Peripheral AC and DC Electrical
ZNEO® Z16F Series MCUs
Product Specification
344
Table 189 lists the Flash Memory electrical characteristics and timing. Table 190 lists the
WDT electrical characteristics and timing.
Table 189. Flash Memory Electrical Characteristics and Timing
V
= 2.7 to 3.6V
DD
T = –40°C to 125°C
A
Parameter
Min
Typ
—
Max
Units Notes
Flash Byte Read Time
Flash Byte Program Time
Flash Page Erase Time
Flash Mass Erase Time
50
20
—
40
—
—
2
ns
s
—
10
—
ms
ms
200
—
—
Writes to Single Address
Before Next Erase
—
Flash Row Program Time
—
—
8
ms
Cumulative program time for
single row cannot exceed limit
1
before next erase
Data Retention
Endurance
Note:
100
—
—
—
—
years 25°C
10,000
cycles Program/erase cycles
1. This parameter is only an issue when bypassing the Flash Controller.
Table 190. Watchdog Timer Electrical Characteristics and Timing
T = –40°C to 125°C
A
Symbol Parameter
WDT Oscillator Frequency
Min
Typ
Max
20
Units Conditions
F
5
10
kHz
WDT
PS022010-0811
P R E L I M I N A R Y On-Chip Peripheral AC and DC Electrical
ZNEO® Z16F Series MCUs
Product Specification
345
Table 191 lists the Analog-to-Digital Converter (ADC) electrical characteristics and tim-
ing.
Table 191. ADC Electrical Characteristics and Timing
T = –40°C to 125°C
A
Symbol Parameter
Min
Typ
Max
Units Conditions
bits External V
Resolution
10
13
—
—
= 2.0 V
REF
Throughput Conversion
CLKs ADC clock cycles
MHz
ADCCLK Frequency
20
2
1
2
2
2
2
DNL
INL
Differential Nonlinearity
–0.99
–3
LSB Typical system config
LSB Typical system config
mV Typical system config
LSB Typical system config
V
1
Integral Nonlinearity
3
1
Offset Error
–30
–4.5
1.9
30
4.5
2.1
1
Gain Error
On-Chip Voltage
2
2
3
Reference
VREF
Externally supplied Volt-
age Reference
1.9
0
2.1
VREF
500
V
V
Analog Input Voltage
Range
Analog Input Current
nA
Reference Input Current
Analog Input Capacitance
Operating Supply Voltage
Operating Current, AVDD
2.0
mA Worst case code
15
pF
V
AVDD
Notes:
2.7
3.6
9
mA Active conversion @
20 MHz
Power Down Current
<1
µA
1. These parameters are guaranteed by design and not tested on every part.
2. Typical system configuration is defined as, 20MHz clock with ADC clock divide by 4, 1 µs sample hold time,
0.5µs sample settling time.
3. On-chip voltage reference cannot be used if AVDD is below 3.0V.
PS022010-0811
P R E L I M I N A R Y On-Chip Peripheral AC and DC Electrical
ZNEO® Z16F Series MCUs
Product Specification
346
Table 192 provides electrical characteristics and timing information for the on-chip com-
parator.
Table 192. Comparator Electrical Characteristics
T = –40°C to 125°C
A
Symbol
Parameter
Min
Typ
Max
Units Conditions
V
Input offset
—
5
mV
V
V
= 3.3 V;
DD
COFF
= V ÷ 2
IN
DD
T
Propagation delay
Input bias current
—
200
40
ns
V
V
mode = 1 V
COMM
CPROP
= 100 mV
DIFF
I
1
µA
V
B
CMVR
Common-mode voltage
range
–0.3
V
–1
DD
I
Supply current
µA
V
= 3.6 V
DD
CC
T
Wake up time from off
state
5
µs CINP = 0.9 V
CINN= 1.0 V
wup
Table 193 provides electrical characteristics and timing information for the on-chip opera-
tional amplifier.
Table 193. Operational Amplifier Electrical Characteristics
T = –40°C to 125°C
A
Symbol Parameter
Min
Typ
Max
15
Units Conditions
V
Input offset
5
mV
V
V
=3.3V;
OS
DD
CM
= V ÷ 2
DD
TC
Input offset Average Drift
Input bias current
1
µV/C
µA
µA
V
VOS
I
I
TBD
TBD
B
Input offset current
OS
CMVR
Common-Mode Voltage
Range
–0.3
V
– 1
DD
V
V
Output Low
Output High
0.1
V
V
I
I
= 100 µA
OL
SINK
V
– 1
= 100 µA
SOURCE
OH
DD
CMRR
Common-Mode Rejection
Ratio
70
dB 0 < V
< 1.4V;
CM
T = 25ºC
A
PS022010-0811
P R E L I M I N A R Y On-Chip Peripheral AC and DC Electrical
ZNEO® Z16F Series MCUs
Product Specification
347
Table 193. Operational Amplifier Electrical Characteristics (Continued)
T = –40°C to 125°C
A
Symbol Parameter
PSRR Power Supply Rejection
Min
Typ
Max
Units Conditions
80
dB
V
= 2.7 V – 3.6 V;
DD
Ratio
T = 25 ºC
A
A
Voltage Gain
Slew Rate while rising
80
12
dB
VOL
SR+
V/µs
R
C
A
= 33 K;
= 50 pF;
= 1,
LOAD
LOAD
VCL
V
= 0.7 V to 1.7 V
IN
SR-
Slew Rate while falling
16
50
V/µs
R
C
A
= 33 K;
= 50 pF;
= 1,
= 1.7 V to 0.7 V
LOAD
LOAD
VCL
V
IN
GBW
FM
Gain-Bandwidth Product
Phase Margin
5
MHz
degree
mA
I
Supply Current
1
V = 3.6 V;
DD
S
V
= V ÷ 2
OUT
DD
T
Wake up time from off
state
20
µs
WUP
PS022010-0811
P R E L I M I N A R Y On-Chip Peripheral AC and DC Electrical
ZNEO® Z16F Series MCUs
Product Specification
348
AC Characteristics
The section provides information about the AC characteristics and timing. All AC timing
information assumes a standard load of 50 pF on all outputs. Table 194 lists the ZNEO
Z16F Series AC characteristics and timing.
Table 194. AC Characteristics
T = –40°C to 125°C
A
Symbol Parameter
Min
—
Max
20.0
20.0
Units Conditions
F
System Clock Frequency
MHz Read-only from Flash memory
sysclk
0.032768
MHz Program or erasure of the
Flash memory
F
Crystal Oscillator
Frequency
1.0
20.0
MHz System clock frequencies
below the crystal oscillator mini-
mum require an external clock
driver
XTAL
T
T
T
T
T
System Clock Period
50
20
20
—
—
—
30
30
3
ns
ns
ns
ns
ns
T
T
T
T
T
= 1/F
sysclk
XIN
CLK
CLK
CLK
CLK
CLK
System Clock High Time
System Clock Low Time
System Clock Rise Time
System Clock Fall Time
= 50 ns
= 50 ns
= 50 ns
= 50 ns
XINH
XINL
XINR
XINF
3
PS022010-0811
P R E L I M I N A R Y
AC Characteristics
ZNEO® Z16F Series MCUs
Product Specification
349
General Purpose I/O Port Input Data Sample Timing
Figure 76 displays timing of the GPIO port input sampling. The input value on a GPIO
port pin is sampled on the rising edge of the system clock. The port value is then available
to the ZNEO CPU on the second rising clock edge following the change of the port value.
Table 195 lists the GPIO port input timing.
TCLK
System
Clock
Port Value
Changes to 0
Port Pin
Input Value
Port Input Data
0 Value May Be Read
Register Latch
From Port Input
Data Register
Figure 76. Port Input Sample Timing
Table 195. GPIO Port Input Timing
Delay (ns)
Parameter Description
Min
Max
T
GPIO Port Pin Pulse Width to ensure Stop Mode Recovery (for
GPIO Port Pins enabled as SMR sources)
1µs
SMR
On-Chip Debugger Timing
Table 196 provides timing information for the DBG pin. The DBG pin timing specifica-
tions assume a 4µs maximum rise and fall time.
Table 196. On-Chip Debugger Timing
Delay (ns)
Parameter Description
DBG Debug frequency.
Min
Max
—
System Clock/4
PS022010-0811
P R E L I M I N A R Y
General Purpose I/O Port Input Data
ZNEO® Z16F Series MCUs
Product Specification
350
SPI Master Mode Timing
Figure 77 and Table 197 provides timing information for SPI Master Mode pins. Timing is
shown with SCK rising edge used to source MOSI output data, SCK falling edge used to
sample MISO input data. Timing on the SS output pin(s) is controlled by software.
SCK
T1
MOSI
(Output)
Output Data
T2
T3
MISO
Input Data
(Input)
Figure 77. SPI Master Mode Timing
Table 197. SPI Master Mode Timing
Delay (ns)
Parameter
SPI Master
Description
Min
Max
T
T
T
SCK Rise to MOSI output Valid Delay
–5
20
0
+5
1
2
3
MISO input to SCK (receive edge) Setup Time
MISO input to SCK (receive edge) Hold Time
SPI Slave Mode Timing
Figure 78 and Table 198 provide timing information for the SPI Slave Mode pins. Timing
is shown with SCK rising edge used to source MISO output data, SCK falling edge used to
sample MOSI input data.
PS022010-0811
P R E L I M I N A R Y
SPI Master Mode Timing
ZNEO® Z16F Series MCUs
Product Specification
351
SCK
T1
MISO
(Output)
Output Data
T2
T3
MOSI
Input Data
(Input)
T4
SS
(Input)
Figure 78. SPI Slave Mode Timing
Table 198. SPI Slave Mode Timing
Delay (ns)
Parameter Description
SPI Slave
Min
Max
T
SCK (transmit edge) to MISO output Valid Delay
2 * X period
IN
3 * X period
IN
1
+ 20 ns
T
T
T
MOSI input to SCK (receive edge) Setup Time
MOSI input to SCK (receive edge) Hold Time
SS input assertion to SCK setup
0
2
3
4
3 * X period
IN
1 * X period
IN
PS022010-0811
P R E L I M I N A R Y
SPI Slave Mode Timing
ZNEO® Z16F Series MCUs
Product Specification
352
I2C Timing
Figure 79 and Table 199 provide timing information for I2C pins.
SCL
(Output)
T1
SDA
(Output)
Output Data
T3
T2
Input Data
SDA
(Input)
2
Figure 79. I C Timing
2
Table 199. I C Timing
Delay (ns)
Min Max
Parameter Description
2
I C
T
T
T
SCL Fall to SDA output delay
SCL period/4
1
2
3
SDA Input to SCL rising edge Setup Time
SDA Input to SCL falling edge Hold Time
0
0
UART Timing
Figure 80 and Table 200 provide timing information for the UART pins in situations in
which the Clear To Send input pin (CTS) is used for flow control. In this example, it is
assumed that the Driver Enable polarity has been configured to be Active Low and is rep-
resented here by DE. The CTS to DE assertion delay (T1) assumes the UART Transmit
Data register has been loaded with data prior to CTS assertion.
PS022010-0811
P R E L I M I N A R Y
I2C Timing
ZNEO® Z16F Series MCUs
Product Specification
353
CTS
(Input)
T1
DE
(Output)
T2
T3
TXD
(Output)
Stop
Start Bit 0 Bit 1
Bit 7 Parity
End of
Stop Bit(s)
Figure 80. UART Timing with CTS
Table 200. UART Timing with CTS
Delay (ns)
Parameter Description
Min
Max
T
T
T
CTS Fall to DE Assertion Delay
2 * X period
IN
2 * X period
IN
+ 1 Bit period
1
2
3
DE Assertion to TXD Falling Edge (Start) Delay
End of Stop Bit(s) to DE Deassertion Delay
1 Bit period
1 Bit period
+ 1 * X period
IN
1 * X period
IN
2 * X period
IN
Figure 81 and Table 201 provide timing information for UART pins for the case where
the Clear To Send input signal (CTS) is not used for flow control. In this example, it is
assumed that the Driver Enable polarity has been configured to be Active Low and is
represented here by DE. DE asserts after the UART Transmit Data register has been
written. DE remains asserted for multiple characters as long as the Transmit Data register
is written with the next character before the current character has completed.
PS022010-0811
P R E L I M I N A R Y
UART Timing
ZNEO® Z16F Series MCUs
Product Specification
354
DE
(Output)
T1
T2
TXD
(Output)
Stop
Start Bit 0 Bit 1
Bit 7 Parity
End of
Stop Bit(s)
Figure 81. UART Timing without CTS
Table 201. UART Timing without CTS
Delay (ns)
Parameter Description
Min
Max
T
DE Assertion to TXD Falling Edge (Start) Delay
1 Bit period
1 Bit period
1
+ 1 * X period
IN
T
End of Stop Bit(s) to DE Deassertion Delay
1 * X period
IN
2 * X period
IN
2
PS022010-0811
P R E L I M I N A R Y
UART Timing
ZNEO® Z16F Series MCUs
Product Specification
355
Packaging
Figure 82 displays the 64-pin low-profile quad flat package (LQFP) available for the
ZNEO® Z16F Series devices.
A
HD
D
A2
A1
E
HE
DETAIL A
LE
c
e
b
L
0-7°
Figure 82. 64-Pin Low-Profile Quad Flat Package (LQFP)
PS022010-0811
P R E L I M I N A R Y
Packaging
ZNEO® Z16F Series MCUs
Product Specification
356
Figure 83 displays the 68-pin plastic lead chip carrier (PLCC) package available for the
ZNEO Z16F Series devices.
Figure 83. 68-Pin Plastic Lead Chip Carrier (PLCC) Package
PS022010-0811
P R E L I M I N A R Y
Packaging
ZNEO® Z16F Series MCUs
Product Specification
357
Figure 84 displays the 80-pin quad flat package (QFP) available for the ZNEO Z16F
Series devices.
Figure 84. 80-Pin Quad-Flat Package (QFP)
PS022010-0811
P R E L I M I N A R Y
Packaging
ZNEO® Z16F Series MCUs
Product Specification
358
Figure 85 displays the 100-pin low-profile quad-flat package (LQFP) available for the
ZNEO Z16F Series devices.
Figure 85. 100-Pin Low-Profile Quad-Flat Package (LQFP)
PS022010-0811
P R E L I M I N A R Y
Packaging
ZNEO® Z16F Series MCUs
Product Specification
359
Ordering Information
Table 202 identifies the basic features and package styles available for each device within
the ZNEO product line.
Table 202. ZNEO Part Selection Guide
Part Number
Z16F2811
128
128
128
128
64
4
4
4
4
4
4
2
2
Yes
Yes
No
76
60
60
46
76
60
76
60
1
1
1
1
1
1
1
1
3
3
3
3
3
3
3
3
12
12
12
12
12
12
12
12
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
X
X
X
Z16F2810
Z16F6411
Z16F3211
No
X
Yes
Yes
Yes
Yes
X
X
64
X
X
32
32
®
You can order the ZNEO Z16F Series from Zilog by providing the part numbers listed in
Table 203. For more information regarding ordering, contact your local Zilog sales office.
Our website (www.zilog.com) lists all regional offices and provides additional informa-
tion about ZNEO Z16F Series product.
PS022010-0811
P R E L I M I N A R Y
Ordering Information
ZNEO® Z16F Series MCUs
Product Specification
360
Table 203. ZNEO Z16F Series Part Numbering
Part Number
ZNEO Z16F Series
Standard Temperature: 0°C to +70°C
Z16F2811AL20SG 128
Z16F2811FI20SG 128
Z16F2810FI20SG 128
Z16F2810AG20SG 128
Z16F2810VH20SG 128
Z16F6411AL20SG 64
Z16F6411FI20SG 64
Z16F3211AL20SG 32
Z16F3211FI20SG 32
4
4
4
4
4
4
4
2
2
Yes 76
Yes 60
1
1
1
1
1
1
1
1
1
3
3
3
3
3
3
3
3
3
12
12
12
12
12
12
12
12
12
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
100-pin LQFP
80-pin QFP
80-pin QFP
64-pin LQFP
68-pin PLCC
100-pin LQFP
80-pin QFP
100-pin LQFP
80-pin QFP
No
No
No
60
46
46
Yes 76
Yes 60
Yes 76
Yes 60
Extended Temperature: –40°C to +105°C
Z16F2811AL20EG 128
Z16F2811FI20EG 128
Z16F2810FI20EG 128
Z16F2810AG20EG 128
Z16F2810VH20EG 128
Z16F6411AL20EG 64
Z16F6411FI20EG 64
Z16F3211AL20EG 32
Z16F3211FI20EG 32
4
4
4
4
4
4
4
2
2
Yes 76
Yes 60
1
1
1
1
1
1
1
1
1
3
3
3
3
3
3
3
3
3
12
12
12
12
12
12
12
12
12
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
100-pin LQFP
80-pin QFP
80-pin QFP
64-pin LQFP
68-pin PLCC
100-pin LQFP
80-pin QFP
100-pin LQFP
80-pin QFP
No
No
No
60
46
46
Yes 76
Yes 60
Yes 76
Yes 60
PS022010-0811
P R E L I M I N A R Y
Ordering Information
ZNEO® Z16F Series MCUs
Product Specification
361
Table 203. ZNEO Z16F Series Part Numbering
Part Number
Automotive Temperature: –40°C to +125°C
Z16F2811AL20AG 128
Z16F2811FI20AG 128
Z16F2810FI20AG 128
Z16F2810AG20AG 128
Z16F2810VH20AG 128
Z16F6411AL20AG 64
Z16F6411FI20AG 64
Z16F3211AL20AG 32
Z16F3211FI20AG 32
4
4
4
4
4
4
4
2
2
Yes 76
Yes 60
1
1
1
1
1
1
1
1
1
3
3
3
3
3
3
3
3
3
12
12
12
12
12
12
12
12
12
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
100-pin LQFP
80-pin QFP
80-pin QFP
64-pin LQFP
68-pin PLCC
100-pin LQFP
80-pin QFP
100-pin LQFP
80-pin QFP
No
No
No
60
46
46
Yes 76
Yes 60
Yes 76
Yes 60
ZNEO Z16F Series Development Tools
Z16F2800100ZCOG
®
ZNEO Z16F Series Development Kit
USB Smart Cable Accessory Kit
ZUSBSC00100ZACG
ZUSBOPTSC01ZACG
Opto-Isolated USB Smart Cable Accessory Kit
Ethernet Smart Cable Accessory Kit
ZENETSC0100ZACG
PS022010-0811
P R E L I M I N A R Y
Ordering Information
ZNEO® Z16F Series MCUs
Product Specification
362
Part Number Suffix Designations
Z16 F 28 11 AL 20
S
G
Environmental Flow
G = Lead Free
Temperature Range
S = Standard, 0°C to +70°C
E = Extended, –40°C to +105°C
A = Automotive, –40°C to +125°C
Speed
20 = 20 MHz
Package
AG = LQFP-64
AL = LQFP-100
FI = QFP-80
VH = PLCC-68
Device Type
10 = Without External Interface
11 = With External Interface
Memory Size
28 = 128 KB Flash
64 = 64 KB Flash
32 = 32 KB Flash
Memory Type
F = Flash
®
Zilog 16-bit ZNEO Microcontroller Family
Note: Packages are not available for all memory sizes. See the Ordering Information section on
page 359 for available packages.
Precharacterization Product
®
The product represented by this document is newly introduced and Zilog has not com-
pleted the full characterization of the product. The document states what Zilog knows
about this product at this time, but additional features or nonconformance with some
aspects of the document might be found, either by Zilog or its customers in the course of
further application and characterization work. In addition, Zilog cautions that delivery
might be uncertain at times, due to start-up yield issues. For more information, please visit
www.zilog.com.
PS022010-0811
P R E L I M I N A R Y
Part Number Suffix Designations
ZNEO® Z16F Series MCUs
Product Specification
363
Index
operation 252
control register
Numerics
10-bit ADC 4
external interface 42, 285
control register definition, UART 153
control register, I2C 229
control registers
64-lead low-profile quad flat package 355
68-lead plastic lead chip carrier package 356
80-lead quad flat package 357, 358
CPU 19
CPU
A
absolute maximum ratings 336
control registers 19
CPU and peripheral overview 3
current measurement
architecture 243
AC characteristics 348
ADC
block diagram 242
electrical characteristics and timing 345
overview 243
operation 243
Customer Support 369
ADC Channel Register 1 (ADCCTL) 246
ADC Data High Byte Register (ADCDH) 247, 251
ADC Data Low Bit Register (ADCDL) 248, 249,
250, 251
D
data
width 17
analog block/PWM signal synchronization 245
analog block/PWM signal zynchronization 245
analog signals 14
analog-to-digital converter
overview 243
data register, I2C 227
DC characteristics 338
debugger, on-chip 298
device, port availability 66
DMA
architecture
controller 4
voltage measurements 243
E
B
electrical characteristics 336
baud rate generator, UART 150
block diagram 2
bus
width 17
bus width
ADC 345
flash memory and timing 344
GPIO input data sample timing 349
watchdog timer 344
electrical noise 243
external interface 37
control register 42, 285
ISA-compatible mode 42
operation 41
non-volatile memory (internal) 21
RAM (internal) 21
C
characteristics, electrical 336
clock phase (SPI) 181
comparator
signals 37, 290
external memory 17
external pin reset 59
definition 251
non-inverting/inverting input 252
PS022010-0811
P R E L I M I N A R Y
Index
ZNEO® Z16F Series MCUs
Product Specification
364
F
flash
I
I/O memory 17
precautions 19
I2C 4
controller 4
option bit address space 292
program memory address 0000H 292
program memory address 0001H 294, 295
flash memory 255
10-bit address read transaction 215
10-bit address transaction 212
10-bit addressed slave data transfer format 212,
220
arrangement 256
code protection 258
configurations 255
control register definitions 261
controller bypass 260
7-bit address transaction 209, 217
7-bit address, reading a transaction 214
7-bit addressed slave data transfer format 211,
218
electrical characteristics and timing 344
flash status register 262
mass erase 260
7-bit receive data transfer format 215, 221, 222
baud high and low byte registers 230, 232, 236,
237
operation 257
operation timing 257
page erase 259
C status register 228, 232
control register definitions 227
controller 203, 242
page select register 265
FPS register 265
controller signals 13
interrupts 206
FSTAT register 262
operation 206
SDA and SCL signals 206
stop and start conditions 208
I2CBRH register 231, 233, 236, 237
I2CBRL register 231
G
general-purpose I/O 66
generator, wait state 41
GPIO 4, 66
I2CCTL register 229
alternate functions 67
architecture 66
input data sample timing 349
interrupts 70
I2CDATA register 227
I2CSTAT register 228, 232
infrared encoder/decoder (IrDA) 172
interface, external 37
port A–H alternate function subregisters 74
port A–H data direction subregisters 73
port A–H input data registers 71
port A–H output control subregisters 74, 76
port A–H output data registers 72
port A–H stop mode recovery subregisters 77,
78, 79
interrupt controller 4, 80
architecture 80
interrupt assertion types 84
interrupt vectors and priority 83
operation 82
register definitions 84
interrupt request 0 register 86
interrupt request 1 register 87
interrupt request 2 register 88
interrupt vector listing 80
interrupts
port availability by device 66
port input timing 349
H
HALT mode 65
SPI 190
UART 147
introduction 1
PS022010-0811
P R E L I M I N A R Y
Index
ZNEO® Z16F Series MCUs
Product Specification
365
IrDA
architecture 151, 172
N
noise, electrical 243
block diagram 152, 172
control register definitions 175
operation 152, 172
non-volatile memory 17, 18
bus width 21
receiving data 174
transmitting data 173
O
OCD
IRQ0 enable high and low bit registers 90
IRQ1 enable high and low bit registers 91
IRQ2 enable high and low bit registers 92
ISA-compatible mode 42
architecture 298
baud rate limits 302
block diagram 299
commands 309
timing 349
L
on-chip debugger 4
on-chip debugger (OCD) 298
on-chip debugger signals 15
on-chip oscillator 326
operation 245
low power modes 64
LQFP
64 lead 355
M
current measurement 243
voltage measurement timing diagram 244, 245
operational amplifier
operation 252
master interrupt enable 82
master-in, slave-out and-in 178
memory
bus widths 17
overview 251
external 17
I/O 17
Operational Description 95, 114, 135, 330, 335
option bits 18
internal 17, 18, 19
map 17
oscillator signals 15
non-volatile 17, 18
parallel access 17
RAM 17, 19
P
packaging
LQFP
random access 17, 19
memory access
quad 21
64 lead 355
PLCC
68 lead 356
word 21
QFP 357, 358
memory map 17
MISO 178
parallel access
memory 17
mode
peripheral AC and DC electrical characteristics 343
memory
ISA-compatible 42
MOSI 178
internal 17
motor control measurements
ADC Control register definitions 246
interrupts 245, 246
overview 243
PHASE=0 timing (SPI) 182
PHASE=1 timing (SPI) 183
pin characteristics 16
PLCC
multiprocessor mode, UART 142
68-lead 356
port availability, device 66
PS022010-0811
P R E L I M I N A R Y
Index
ZNEO® Z16F Series MCUs
Product Specification
366
port input timing (GPIO) 349
power supply signals 15
SPI status (SPISTAT) 198
status, SPI 198
power-on and voltage brown-out 343
precautions, I/O memory 19
UARTx baud rate high byte (UxBRH) 166
UARTx baud rate low byte (UxBRL) 167
UARTx Control 0 (UxCTL0) 160, 166
UARTx control 1 (UxCTL1) 162, 164, 165
UARTx receive data (UxRXD) 154
UARTx status 0 (UxSTAT0) 155, 156
UARTx status 1 (UxSTAT1) 158
UARTx transmit data (UxTXD) 154
watchdog timer control (WDTCTL) 333, 334
watchdog timer reload high byte (WDTH) 241
watchdog timer reload low byte (WDTL) 241
register file address map 23
Q
QFP 357, 358
quad mode
memory access 21
R
RAM 17, 19
bus width 21
random-access memory 17, 19
receive
registers
7-bit data transfer format (I2C) 215, 221, 222
IrDA data 174
ADC channel 1 246
ADC data high byte 247, 251
ADC data low bit 248, 249, 250, 251
reset
receiving UART data-interrupt-driven method 140
receiving UART data-polled method 139
register 197
and STOP mode characteristics 56
and STOP mode recovery 56
controller 4
baud low and high byte (I2C) 230, 232, 236,
237
baud rate high and low byte (SPI) 201
control (SPI) 194
S
control, I2C 229
SCK 178
data, SPI 193
SDA and SCL (IrDA) signals 206
serial clock 178
external interface control 42, 285
flash page select (FPS) 265
flash status (FSTAT) 262
GPIO port A–H alternate function subregisters
75
serial peripheral interface (SPI) 176
signal descriptions 12
SIO 4
slave data transfer formats (I2C) 212, 220
slave select 179
GPIO port A–H data direction subregisters 73
I2C baud rate high (I2CBRH) 231, 233, 236,
237
SPI
architecture 176
I2C control (I2CCTL) 229
I2C data (I2CDATA) 227
I2C status 228, 232
baud rate generator 192
baud rate high and low byte register 201
clock phase 181
configured as slave 189
control register 194
control register definitions 193
data register 193
error detection 189
interrupts 190
mode fault error 189
I2C status (I2CSTAT) 228, 232
I2C baud rate low (I2CBRL) 231
mode, SPI 197
SPI baud rate high byte (SPIBRH) 202
SPI baud rate low byte (SPIBRL) 202
SPI control (SPICTL) 194
SPI data (SPIDATA) 193, 194
PS022010-0811
P R E L I M I N A R Y
Index
ZNEO® Z16F Series MCUs
Product Specification
367
mode register 197
multi-master operation 186
operation 178
reload high and low byte registers 108, 123
timer control register definitions 106, 121
triggered one-shot mode 98
overrun error 189, 190
signals 178
single master, multiple slave system 187
single master,single slave system 187
status register 198
timers 0–3
control registers 109, 111
high and low byte registers 106, 109, 122, 124
timing diagram, voltage measurement 244
transmit
timing, PHASE = 0 182
timing, PHASE=1 183
SPI controller signals 13
SPI mode (SPIMODE) 197
SPIBRH register 202
SPIBRL register 202
SPICTL register 194
SPIDATA register 193, 194
SPIMODE register 197
SPISTAT register 198
SS, SPI signal 178
IrDA data 173
transmitting UART data-polled method 137
U
UART 4
architecture 135
asynchronous data format without/with parity
137
baud rate generator 150
baud rates table 169
control register definitions 153
controller signals 14
STOP mode 64
STOP mode recovery
sources 60
data format 136
interrupts 147
using a GPIO port pin transition 61
using watchdog timer time-out 61
system 18
multiprocessor mode 142
receiving data using interrupt-driven method
140
system and core resets 57
system vectors 18
receiving data using the polled method 139
transmitting data using the polled method 137
x baud rate high and low registers 166
x control 0 and control 1 registers 160, 162
x status 0 and status 1 registers 155, 158
UxBRH register 166
T
tiing diagram, voltage measurement 245
timer signals 14
timers 4, 95
UxBRL register 167
architecture 95, 114
block diagram 96, 115
capture mode 102, 103
capture/compare mode 103
compare mode 104
continuous mode 99
counter mode 99
UxCTL0 register 160, 166
UxCTL1 register 162, 164, 165
UxRXD register 154
UxSTAT0 register 155, 156
UxSTAT1 register 158
UxTXD register 154
V
gated mode 105
one-shot mode 97
vectors 18
operating mode 97
PWM mode 101
reading the timer count values 106
interrupts 18
system exceptions 18
voltage brownout reset (VBR) 58
PS022010-0811
P R E L I M I N A R Y
Index
ZNEO® Z16F Series MCUs
Product Specification
368
voltage measurement timing diagram 244, 245
watchdog timer
approximate time-out delay 239
W
electrical characteristics and timing 344
interrupt in normal operation 239
WDTCTL register 333, 334
WDTH register 241
WDTL register 241
word mode
wait state generator 41
watch-dog timer
approximate time-out delays 335
control register 332, 334
interrupt in STOP mode 239
operation 335
memory access 21
refresh 239
Z
ZNEO
block diagram 2
introduction 1
ZNEO CPU features 3
reload unlock sequence 240
reload upper, high and low registers 241
reset 59
reset in normal operation 240
reset in STOP mode 240
time-out response 239
PS022010-0811
P R E L I M I N A R Y
Index
ZNEO Z16F Series
Product Specification
369
Customer Support
To share comments, get your technical questions answered, or report issues you may be
experiencing with our products, please visit Zilog’s Technical Support page at
http://support.zilog.com.
To learn more about this product, find additional documentation, or to discover other fac-
ets about Zilog product offerings, please visit the Zilog Knowledge Base or consider par-
ticipating in the Zilog Forum.
This publication is subject to replacement by a later edition. To determine whether a later
edition exists, please visit the Zilog website at http://www.zilog.com.
PS022010-0811
P R E L I M I N A R Y
Customer Support
相关型号：
Z16F6411FI20SG
ZNEO® Z16F Series Flash Microcontroller A 16-bit Single-Cycle CISC MCU Solution
ZILOG
Z16FMC28AG20EG
IC 16-BIT, FLASH, 20 MHz, MICROCONTROLLER, PQFP64, LEAD FREE, LQFP-64, Microcontroller
ZILOG
Z16FMC28AG20SG
IC 16-BIT, FLASH, 20 MHz, MICROCONTROLLER, PQFP64, LEAD FREE, LQFP-64, Microcontroller
ZILOG
Z16FMC32AG20EG
IC 16-BIT, FLASH, 20 MHz, MICROCONTROLLER, PQFP64, LEAD FREE, LQFP-64, Microcontroller
ZILOG
Z16FMC32AG20SG
IC 16-BIT, FLASH, 20 MHz, MICROCONTROLLER, PQFP64, LEAD FREE, LQFP-64, Microcontroller
ZILOG
Z16FMC64AG20SG
IC 16-BIT, FLASH, 20 MHz, MICROCONTROLLER, PQFP64, LEAD FREE, LQFP-64, Microcontroller
ZILOG
©2020 ICPDF网 联系我们和版权申明