MC9S12ZVHY/MC9S12ZVHL Families Reference Manual HCS12

Document technical information

Format pdf
Size 3.2 MB
First found Jun 9, 2017

Document content analysis

Language
English
Type
not defined
Concepts
no text concepts found

Persons

Organizations

Places

Transcript

MC9S12ZVHY/MC9S12ZVHL
Families
Reference Manual
HCS12
Microcontrollers
MC9S12ZVHYRMV1
Rev. 1.02
3/2014
freescale.com
To provide the most up-to-date information, the revision of our documents on the World Wide Web will be
the most current. Your printed copy may be an earlier revision. To verify you have the latest information
available, refer to:
freescale.com
A full list of family members and options is included in the appendices.
The following revision history table summarizes changes contained in this document.
This document contains information for all constituent modules, with the exception of the S12Z CPU. For
S12ZCPU information please refer to the CPU S12Z Reference Manual.
Revision History
Date
Revision
Level
Sep, 2013
1.00
First release for external web site
- Add ZVHY 32K
- Update OSC etc. electrical spec
Nov, 2013
1.01
- Updated Appendix A electrical spec
- Updated SCI/ADC/SPI/BDC/FTMRZ sections (see section rev. history)
1.02
- Added ZVHL part and corresponding LINPHY information.
- Updated STOP mode BDC dependency text.
- Changed VLVRXA minimum from 2.97V to 2.95V
- Added frequency spec. for WSTAT to operating conditions table
- Removed incorrect device overview reference to over-temperature protection
- Corrected vector mapping of ADC CONIF_OIE interrupt
- Updated CPMU section (see section rev. history)
Mar, 2014
Description
Freescale Semiconductor reserves the right to make changes without further notice to any products herein. Freescale Semiconductor makes no warranty,
representation or guarantee regarding the suitability of its products for any particular purpose, nor does Freescale Semiconductor assume any liability arising out of
the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. “Typical”
parameters that may be provided in Freescale Semiconductor data sheets and/or specifications can and do vary in different applications and actual performance may
vary over time. All operating parameters, including “Typicals”, must be validated for each customer application by customer’s technical experts. Freescale
Semiconductor does not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not designed, intended, or
authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other
application in which the failure of the Freescale Semiconductor product could create a situation where personal injury or death may occur. Should Buyer purchase or
use Freescale Semiconductor products for any such unintended or unauthorized application, Buyer shall indemnify and hold Freescale Semiconductor and its officers,
employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly
or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Freescale Semiconductor was
negligent regarding the design or manufacture of the part.
Chapter 1
Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.1
1.2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.2.1 MC9S12ZVHY/MC9S12ZVHL Families Member Comparison . . . . . . . . . . . . . . . . . . 24
1.3 Maskset 0N39G and 1N39G device compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.4 Chip-Level Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.5 Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.5.1 S12Z Central Processor Unit (CPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.5.2 Embedded Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.5.3 Clocks, Reset & Power Management Unit (CPMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.5.4 Main External Oscillator (XOSCLCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.5.5 32K External Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.5.6 System Integrity Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.5.7 Real Time Clock (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.5.8 Timer (TIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.5.9 Pulse Width Modulation Module (PWM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.5.10 Simple Sound Generator (SSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.5.11 Liquid Crystal Display driver (LCD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.5.12 LIN physical layer transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.5.13 Stepper Motor Controller (MC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.5.14 Stepper Stall Detect (SSD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.5.15 Multi-Scalable Controller Area Network (MSCAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.5.16 Inter-IC Bus Module (IIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.5.17 Serial Communication Interface Module (SCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.5.18 Serial Peripheral Interface Module (SPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.5.19 Analog-to-Digital Converter Module (ADC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.5.20 Supply Voltage Sensor (BATS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.5.21 On-Chip Voltage Regulator system (VREG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.6 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.6.1 Device Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.6.2 Part ID registers Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.7 Signal Description and Device Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.7.1 Pin Assignment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.7.2 Detailed Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.7.3 VSENSE - Voltage Sensor Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.7.4 BCTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.7.5 Power Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.8 Package and Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1.9 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.9.1 Chip Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.9.2 Debugging Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1.9.3 Low Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1.10 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.10.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
3
1.11
1.12
1.13
1.14
1.15
1.16
1.17
1.18
1.19
1.20
1.21
1.10.2 Securing the Microcontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.10.3 Operation of the Secured Microcontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1.10.4 Unsecuring the Microcontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1.10.5 Reprogramming the Security Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
1.10.6 Complete Memory Erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Resets and Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
1.11.1 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
1.11.2 Interrupt Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1.11.3 Effects of Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
COP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ADC0 Internal Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
The ADC0 VRH/VRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
The ADC0 Conversion Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
ADC Result Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
BDC Clock Source Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
FTMRZ Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
RTC Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
LCD Clock Source Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
32K OSC enable control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Chapter 2
Port Integration Module (S12ZVHYPIMV1)
2.1
2.2
2.3
2.4
2.5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
2.3.1 Register Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.4.2 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.4.3 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2.4.4 Pin interrupts and Wakeup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Initialization and Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.5.1 Port Data and Data Direction Register writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.5.2 SCI0,1 Baud Rate Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.5.3 RTC on chip calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.5.4 RTC off chip calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Chapter 3
Memory Mapping Control (S12ZMMCV1)
3.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
4
Freescale Semiconductor
3.2
3.3
3.4
3.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.1.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.1.4 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.1.5 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.3.1 Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
3.4.1 Global Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
3.4.2 Illegal Accesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
3.4.3 Uncorrectable ECC Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Chapter 4
Interrupt (S12ZINTV0)
4.1
4.2
4.3
4.4
4.5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
4.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.4.1 S12Z Exception Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4.4.2 Interrupt Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4.4.3 Priority Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4.4.4 Reset Exception Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4.4.5 Exception Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4.4.6 Interrupt Vector Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.5.1 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.5.2 Interrupt Nesting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.5.3 Wake Up from Stop or Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Chapter 5
Background Debug Controller (S12ZBDCV2)
5.1
5.2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
5
5.3
5.4
5.5
Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.4.1 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.4.2 Enabling BDC And Entering Active BDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.4.3 Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.4.4 BDC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.4.5 BDC Access Of Internal Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.4.6 BDC Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.4.7 Serial Interface Hardware Handshake (ACK Pulse) Protocol . . . . . . . . . . . . . . . . . . . . 173
5.4.8 Hardware Handshake Abort Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.4.9 Hardware Handshake Disabled (ACK Pulse Disabled) . . . . . . . . . . . . . . . . . . . . . . . . . 176
5.4.10 Single Stepping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5.4.11 Serial Communication Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5.5.1 Clock Frequency Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Chapter 6
S12Z Debug (S12ZDBGV2) Module
6.1
6.2
6.3
6.4
6.5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.4 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6.1.5 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.2.1 External Event Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.2.2 Profiling Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Memory Map and Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.4.1 DBG Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.4.2 Comparator Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.4.3 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
6.4.4 State Sequence Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
6.4.5 Trace Buffer Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
6.4.6 Code Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
6.4.7 Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
6.5.1 Avoiding Unintended Breakpoint Re-triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
6.5.2 Debugging Through Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
6.5.3 Breakpoints from other S12Z sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
6.5.4 Code Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
6
Freescale Semiconductor
Chapter 7
S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.1
7.2
7.3
7.4
7.5
7.6
7.7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
7.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
7.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
7.1.3 S12CPMU_UHV_V5 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.2.1 RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.2.2 EXTAL and XTAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.2.3 VSUP — Regulator Power Input Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.2.4 VDDA, VSSA — Regulator Reference Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.2.5 VDDX, VSSX — Pad Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.2.6 BCTL — Base Control Pin for external PNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.2.7 VSS — Core Logic Ground Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.2.8 VDD — Internal Regulator Output Supply (Core Logic) . . . . . . . . . . . . . . . . . . . . . . . 239
7.2.9 VDDF — Internal Regulator Output Supply (NVM Logic) . . . . . . . . . . . . . . . . . . . . . 239
7.2.10 API_EXTCLK — API external clock output pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.2.11 TEMPSENSE — Internal Temperature Sensor Output Voltage . . . . . . . . . . . . . . . . . . 239
Memory Map and Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
7.4.1 Phase Locked Loop with Internal Filter (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
7.4.2 Startup from Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
7.4.3 Stop Mode using PLLCLK as source of the Bus Clock . . . . . . . . . . . . . . . . . . . . . . . . 282
7.4.4 Full Stop Mode using Oscillator Clock as source of the Bus Clock . . . . . . . . . . . . . . . 283
7.4.5 External Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
7.4.6 System Clock Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
7.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
7.5.2 Description of Reset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
7.5.3 Oscillator Clock Monitor Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
7.5.4 PLL Clock Monitor Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
7.5.5 Computer Operating Properly Watchdog (COP) Reset . . . . . . . . . . . . . . . . . . . . . . . . . 288
7.5.6 Power-On Reset (POR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
7.5.7 Low-Voltage Reset (LVR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
7.6.1 Description of Interrupt Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
7.7.1 General Initialization Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
7.7.2 Application information for COP and API usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
7.7.3 Application Information for PLL and Oscillator Startup . . . . . . . . . . . . . . . . . . . . . . . . 292
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
7
Chapter 8
Timer Module (TIM16B8CV3) Block Description
8.1
8.2
8.3
8.4
8.5
8.6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
8.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
8.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8.1.3 Block Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
8.2.1 IOC7 — Input Capture and Output Compare Channel 7 . . . . . . . . . . . . . . . . . . . . . . . . 299
8.2.2 IOC6 - IOC0 — Input Capture and Output Compare Channel 6-0 . . . . . . . . . . . . . . . . 299
Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
8.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
8.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
8.4.1 Prescaler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
8.4.2 Input Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
8.4.3 Output Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
8.4.4 Pulse Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
8.4.5 Event Counter Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
8.4.6 Gated Time Accumulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
8.6.1 Channel [7:0] Interrupt (C[7:0]F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
8.6.2 Pulse Accumulator Input Interrupt (PAOVI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
8.6.3 Pulse Accumulator Overflow Interrupt (PAOVF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
8.6.4 Timer Overflow Interrupt (TOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Chapter 9
Pulse-Width Modulator (S12PWM8B8CV2)
9.1
9.2
9.3
9.4
9.5
9.6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
9.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
9.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
9.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
9.2.1 PWM7 - PWM0 — PWM Channel 7 - 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
9.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
9.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
9.4.1 PWM Clock Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
9.4.2 PWM Channel Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
8
Freescale Semiconductor
Chapter 10
Analog-to-Digital Converter (ADC12B_LBA_V1)
10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
10.2 Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
10.2.1 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
10.2.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
10.3 Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
10.3.1 Detailed Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
10.4 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
10.4.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
10.4.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
10.5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
10.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
10.5.2 Analog Sub-Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
10.5.3 Digital Sub-Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
10.6 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
10.7 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
10.7.1 ADC Conversion Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
10.7.2 ADC Sequence Abort Done Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
10.7.3 ADC Error and Conversion Flow Control Issue Interrupt . . . . . . . . . . . . . . . . . . . . . . . 411
10.8 Use Cases and Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
10.8.1 List Usage — CSL single buffer mode and RVL single buffer mode . . . . . . . . . . . . . . 412
10.8.2 List Usage — CSL single buffer mode and RVL double buffer mode . . . . . . . . . . . . . 412
10.8.3 List Usage — CSL double buffer mode and RVL double buffer mode . . . . . . . . . . . . . 413
10.8.4 List Usage — CSL double buffer mode and RVL single buffer mode . . . . . . . . . . . . . 413
10.8.5 List Usage — CSL double buffer mode and RVL double buffer mode . . . . . . . . . . . . . 414
10.8.6 RVL swapping in RVL double buffer mode and related registers ADCIMDRI and
ADCEOLRI 414
10.8.7 Conversion flow control application information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
10.8.8 Continuous Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
10.8.9 Triggered Conversion — Single CSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
10.8.10Fully Timing Controlled Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Chapter 11
Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
11.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
11.1.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
11.1.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
11.1.4 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
11.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
11.2.1 RXCAN — CAN Receiver Input Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
11.2.2 TXCAN — CAN Transmitter Output Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
9
11.2.3 CAN System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
11.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
11.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
11.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
11.3.3 Programmer’s Model of Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
11.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
11.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
11.4.2 Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
11.4.3 Identifier Acceptance Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
11.4.4 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
11.4.5 Low-Power Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
11.4.6 Reset Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
11.4.7 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
11.5 Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
11.5.1 MSCAN initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
11.5.2 Bus-Off Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Chapter 12
Serial Communication Interface (S12SCIV6)
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
12.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
12.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
12.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.2.1 TXD — Transmit Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.2.2 RXD — Receive Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.3.1 Module Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
12.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
12.4.1 Infrared Interface Submodule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
12.4.2 LIN Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
12.4.3 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
12.4.4 Baud Rate Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
12.4.5 Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
12.4.6 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
12.4.7 Single-Wire Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
12.4.8 Loop Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
12.5 Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
12.5.1 Reset Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
12.5.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
12.5.3 Interrupt Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
12.5.4 Recovery from Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
12.5.5 Recovery from Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
10
Freescale Semiconductor
Chapter 13
Serial Peripheral Interface (S12SPIV5)
13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
13.1.1 Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
13.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
13.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
13.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
13.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
13.2.1 MOSI — Master Out/Slave In Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
13.2.2 MISO — Master In/Slave Out Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
13.2.3 SS — Slave Select Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
13.2.4 SCK — Serial Clock Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
13.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
13.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
13.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
13.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
13.4.1 Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
13.4.2 Slave Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
13.4.3 Transmission Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
13.4.4 SPI Baud Rate Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
13.4.5 Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
13.4.6 Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
13.4.7 Low Power Mode Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Chapter 14
Inter-Integrated Circuit (IICV3) Block Description
14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
14.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
14.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
14.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
14.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
14.2.1 IIC_SCL — Serial Clock Line Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
14.2.2 IIC_SDA — Serial Data Line Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
14.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
14.3.1 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
14.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
14.4.1 I-Bus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
14.4.2 Operation in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
14.4.3 Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
14.4.4 Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
14.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
14.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
14.7 Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
14.7.1 IIC Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
11
Chapter 15
Liquid Crystal Display (LCD40F4BV3) Block Description
15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
15.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
15.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
15.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
15.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
15.2.1 BP[3:0] — Analog Backplane Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
15.2.2 FP[39:0] — Analog Frontplane Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
15.2.3 VLCD — LCD Supply Voltage Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
15.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
15.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
15.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
15.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
15.4.1 LCD Driver Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
15.4.2 Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
15.4.3 Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
15.4.4 LCD Waveform Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
15.4.5 LCD Clock Inputs & Reset Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
15.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
15.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Chapter 16
Motor Controller (MC10B8CV1)
16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
16.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
16.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
16.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
16.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
16.2.1 M0C0M/M0C0P/M0C1M/M0C1P — PWM Output Pins for Motor 0 . . . . . . . . . . . . 596
16.2.2 M1C0M/M1C0P/M1C1M/M1C1P — PWM Output Pins for Motor 1 . . . . . . . . . . . . 596
16.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
16.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
16.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
16.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
16.4.1 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
16.4.2 PWM Duty Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
16.4.3 Motor Controller Counter Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
16.4.4 Output Switching Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
16.4.5 Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
16.4.6 Operation in Stop and Pseudo-Stop Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
16.5 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
16.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
16.6.1 Timer Counter Overflow Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
12
Freescale Semiconductor
16.7 Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
16.7.1 Code Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Chapter 17
Stepper Stall Detector (SSDV2) Block Description
17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
17.1.1 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
17.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
17.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
17.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
17.2.1 COSM/COSP — Cosine Coil Pins for Motor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
17.2.2 SINM/SINP — Sine Coil Pins for Motor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
17.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
17.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
17.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
17.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
17.4.1 Return to Zero Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
17.4.2 Full Step States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
17.4.3 Operation in Low Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
17.4.4 Stall Detection Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Chapter 18
Real-Time Counter With Calendar (RTCV2)
18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
18.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
18.2.1 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
18.2.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
18.3 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
18.3.1 OSCCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
18.3.2 OSCCLK_32K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
18.3.3 IRCCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
18.3.4 RTCCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
18.3.5 CALCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
18.4 Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
18.4.1 RTC Control Register 1(RTCCTL1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
18.4.2 RTC Control Register 2 (RTCCTL2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
18.4.3 RTC Control Register 3 (RTCCTL3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
18.4.4 RTC Control Register 4 (RTCCTL4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
18.4.5 RTC Status Register 1 (RTCS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
18.4.6 RTC Compensation Configure Register (RTCCCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
18.4.7 RTC Counter Register (RTCCNT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
18.4.8 RTC Modulo Register (RTCMOD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
18.4.9 RTC Second Register (RTCSECR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
18.4.10RTC Minute Register (RTCMINR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
13
18.4.11RTC Hour Register (RTCHRR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
18.5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
18.5.1 RTC clock and reset behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
18.5.2 Calendar Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
18.5.3 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
18.5.4 RTC Clock Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
18.5.5 Calendar Register and Bit Write Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
18.5.6 Load buffer register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
18.6 Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
18.6.1 RTC Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
18.6.2 RTC compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Chapter 19
Simple Sound Generator (SSGV1)
19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
19.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
19.1.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
19.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
19.2.1 SGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
19.2.2 SGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
19.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
19.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
19.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
19.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
19.4.1 SSG Amplitude Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
19.4.2 SSG Tone Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
19.4.3 SSG Attack and Decay function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
19.4.4 SSG Start and Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
19.4.5 Register Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
19.4.6 SSG Output Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
19.5 Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Chapter 20
ECC Generation module (SRAM_ECCV1)
20.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
20.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
20.2 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
20.2.1 Register Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
20.2.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
20.3 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
20.3.1 Aligned 2 and 4 Byte Memory write access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
20.3.2 Other Memory write access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
20.3.3 Memory read access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
20.3.4 Memory initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
14
Freescale Semiconductor
20.3.5 Interrupt handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
20.3.6 ECC Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
20.3.7 ECC Debug Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Chapter 21
64 KB Flash Module (S12ZFTMRZ64K2KV2)
21.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
21.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
21.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
21.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
21.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
21.3 Memory Map and Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
21.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
21.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
21.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
21.4.1 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
21.4.2 IFR Version ID Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
21.4.3 Flash Block Read Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
21.4.4 Internal NVM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
21.4.5 Flash Command Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
21.4.6 Allowed Simultaneous P-Flash and EEPROM Operations . . . . . . . . . . . . . . . . . . . . . . 723
21.4.7 Flash Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
21.4.8 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
21.4.9 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
21.4.10Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
21.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
21.5.1 Unsecuring the MCU using Backdoor Key Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
21.5.2 Unsecuring the MCU in Special Single Chip Mode using BDM . . . . . . . . . . . . . . . . . 742
21.5.3 .Mode and Security Effects on Flash Command Availability . . . . . . . . . . . . . . . . . . . . 742
21.6 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Chapter 22
Supply Voltage Sensor - (BATSV2)
22.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
22.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
22.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
22.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
22.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
22.2.1 VSENSE — Supply (Battery) Voltage Sense Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
22.2.2 VSUP — Voltage Supply Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
22.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
22.3.1 Register Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
22.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
22.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
15
22.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
22.4.2 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Chapter 23
LIN Physical Layer (S12LINPHYV2)
23.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
23.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
23.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
23.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
23.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
23.2.1 LIN — LIN Bus Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
23.2.2 LGND — LIN Ground Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
23.2.3 VLINSUP — Positive Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
23.2.4 LPTxD — LIN Transmit Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
23.2.5 LPRxD — LIN Receive Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
23.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
23.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
23.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
23.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
23.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
23.4.2 Slew Rate and LIN Mode Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
23.4.3 Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
23.4.4 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
23.5 Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
23.5.1 Module Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
23.5.2 Interrupt handling in Interrupt Service Routine (ISR) . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Appendix A
MCU Electrical Specifications
A.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
A.1.1 Parameter Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
A.1.2 Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
A.1.3 Current Injection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
A.1.4 Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
A.1.5 ESD Protection and Latch-up Immunity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
A.1.6 Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
A.1.7 Power Dissipation and Thermal Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
A.1.8 I/O Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
A.1.9 Supply Currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
A.1.10 ADC Conversion Result Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
Appendix B
ADC Electricals
B.1 ADC Operating Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
16
Freescale Semiconductor
B.1.1 Factors Influencing Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
B.1.2 ADC Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
Appendix C
PLL Electrical Specifications
C.1 Reset, Oscillator and PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
C.1.1 Phase Locked Loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Appendix D
IRC Electrical Specifications
Appendix E
LCD Electrical Specifications
E.1
LCD Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
Appendix F
MSCAN Electrical Specifications
F.1
MSCAN Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Appendix G
NVM Electrical Parameters
G.1 NVM Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
G.2 NVM Reliability Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Appendix H
BATS Electrical Specifications
H.1 Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
H.2 Static Electrical Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
H.3 Dynamic Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Appendix I
VREG Electrical Specifications
Appendix J
Electrical Characteristics for the Oscillator (OSCLCPcr)
J.1
OSCLCP Electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Appendix K
OSC32K Electrical Specifications
K.1 DC Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
K.2 Frequency Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
17
Appendix L
SPI Electrical Specifications
L.1
L.2
Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Slave Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Appendix M
LINPHY Electrical Specifications
M.1 Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
M.2 Static Electrical Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
M.3 Dynamic Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Appendix N
Ordering Information
Appendix O
Package Information
O.1 144 LQFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
O.2 100 LQFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
Appendix P
Detailed Register Address Map
P.1
Detailed Register Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
18
Freescale Semiconductor
Chapter 1
Device Overview MC9S12ZVHY/MC9S12ZVHL Families. . . . . 23
Chapter 2
Port Integration Module (S12ZVHYPIMV1) . . . . . . . . . . . . . . . . 71
Chapter 3
Memory Mapping Control (S12ZMMCV1) . . . . . . . . . . . . . . . . 115
Chapter 4
Interrupt (S12ZINTV0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Chapter 5
Background Debug Controller (S12ZBDCV2) . . . . . . . . . . . . 141
Chapter 6
S12Z Debug (S12ZDBGV2) Module. . . . . . . . . . . . . . . . . . . . . 179
Chapter 7
S12 Clock, Reset and Power Management Unit . . . . . . . . . . 229
Chapter 8
Timer Module (TIM16B8CV3) Block Description . . . . . . . . . . 295
Chapter 9
Pulse-Width Modulator (S12PWM8B8CV2) . . . . . . . . . . . . . . 323
Chapter 10
Analog-to-Digital Converter (ADC12B_LBA_V1) . . . . . . . . . 353
Chapter 11
Freescale’s Scalable Controller Area Network . . . . . . . . . . . 421
Chapter 12
Serial Communication Interface (S12SCIV6) . . . . . . . . . . . . . 475
Chapter 13
Serial Peripheral Interface (S12SPIV5) . . . . . . . . . . . . . . . . . . 515
Chapter 14
Inter-Integrated Circuit (IICV3) Block Description. . . . . . . . . 541
Chapter 15
Liquid Crystal Display (LCD40F4BV3) Block Description . . 569
Chapter 16
Motor Controller (MC10B8CV1). . . . . . . . . . . . . . . . . . . . . . . . 593
Chapter 17
Stepper Stall Detector (SSDV2) Block Description . . . . . . . . 621
Chapter 18
Real-Time Counter With Calendar (RTCV2) . . . . . . . . . . . . . . 639
Chapter 19
SimpleSound Generator (SSGV1) . . . . . . . . . . . . . . . . . . . . . . 657
Chapter 20
ECC Generation module (SRAM_ECCV1) . . . . . . . . . . . . . . . 677
Chapter 21
64 KB Flash Module (S12ZFTMRZ64K2KV2) . . . . . . . . . . . . . 689
Chapter 22
Supply Voltage Sensor - (BATSV2). . . . . . . . . . . . . . . . . . . . . 743
Chapter 23
LIN Physical Layer (S12LINPHYV2) . . . . . . . . . . . . . . . . . . . . 755
Appendix A MCU Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 777
Appendix B ADC Electricals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
Appendix C PLL Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 797
Appendix D IRC Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Appendix E LCD Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 801
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
19
Appendix F MSCAN Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . 803
Appendix G NVM Electrical Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Appendix H BATS Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . 809
Appendix I
VREG Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . 813
Appendix J
Electrical Characteristics for the Oscillator (OSCLCPcr) . . . 815
Appendix K OSC32K Electrical Specifications. . . . . . . . . . . . . . . . . . . . . . 817
Appendix L SPI Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Appendix M LINPHY Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . 825
Appendix N Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Appendix O Package Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Appendix P Detailed Register Address Map. . . . . . . . . . . . . . . . . . . . . . . . 839
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
20
Freescale Semiconductor
PAGE INTENTIONALLY LEFT BLANK
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
21
PAGE INTENTIONALLY LEFT BLANK
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
22
Freescale Semiconductor
Chapter 1
Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-1. Revision History
Version
Number
Revision
Date
0.02
April 2012
• Add the BDCFCLK source to bus clock
• Add RTC clock source
0.04
July 2012
• Fix typos
0.05
Sep 2012
•
•
•
•
0.06
Nov 2012
• Update for 1N39G
0.07
July 2013
• Add 32K device
0.08
Jan 2014
• Add ZVHL part
1.1
Description of Changes
Update ADC conversion reference IFR location
Correct 100LQFP pinout signals typos
Fix base on review feedback
Add FTMRZ related connection
Introduction
The MC9S12ZVHY/MC9S12ZVHL Families are optimized automotive 16-bit microcontroller product
families, focused on low-cost, high-performance and application component count reduction. They
integrate many components of the MagniV mixed signal microcontroller S12ZVH-family, including a 5V
regulator system to supply the microcontroller and other components. The MC9S12ZVHY is targeted at
automotive and motorcycle instrument cluster applications requiring stepper motor gauges and segment
LCD displays. The MC9S12ZVHL is targeted at automotive and motorcycle instrument cluster
applications requiring stepper motor gauges, segment LCD displays and LIN communications.
The devices features a 4x40 liquid crystal display (LCD) controller/driver and a pulse width modulated
motor controller (MC) consisting of up to 16 high current outputs. The devices are capable of stepper
motor stall detection (SSD) via hardware or software, please contact Freescale sales office for detailed
information on software SSD.
The MC9S12ZVHY/MC9S12ZVHL Families deliver an optimized solution with the integration of several
key system components into a single device, optimizing system architecture and achieving significant PCB
space savings. These families deliver all the advantages and efficiencies of a 16-bit MCU while retaining
the low cost, power consumption, EMC, and code-size efficiency advantages currently enjoyed by users
of Freescale’s existing S12(X) MCU families. The MC9S12ZVHY/MC9S12ZVHL Families also feature
the revolutionary S12Z CPU with code size and execution efficiencies even higher than our class leading
S12X CPU. They also provides a linear memory map for all members of the family, eliminating the
inconvenience and performance impact of page swapping. In addition to the I/O ports available in each
module, further I/O ports are available with interrupt capability allowing wake-up from stop or wait modes.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
23
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.2
Features
This section describes the key features of the MC9S12ZVHY/MC9S12ZVHL Families.
1.2.1
MC9S12ZVHY/MC9S12ZVHL Families Member Comparison
Table 1-2 provides a summary of feature set differences within the MC9S12ZVHY/MC9S12ZVHL
Families. LINPHY function is only available on MC9S12ZVHL family.
Table 1-2. Derivative Comparison
Feature
MC9S12ZVHY64/ZVHL64
Package
100 pins (LQFP)
CPU
144 pins (LQFP)
MC9S12ZVHY32/ZVHL32
100 pins (LQFP)
144 pins (LQFP)
HCS12Z
HCS12Z
Flash memory (ECC)
64 KB
32 KB
EEPROM (ECC)
2 KB
2KB
RAM (ECC)
4 KB
2 KB
2
2
Stepper Motor Drive (with HW
SSD)
Segment LCD
4 x 32
Simple Sound Generator (SSG)
4 x 40
4 x 32
4 x 40
Yes
Yes
2
2
Only avaiable on ZVHL
Only available on ZVHL
SPI
1
1
IIC
1
1
CAN (digital communication
module)
1
1
SCI
LIN Physical Layer
Timer
Two 8ch x 16-bit
(not all IOC
avaiable on pins)
Two 8ch x 16-bit
Two 8ch x 16-bit
(not all IOC
avaiable on pins)
Two 8ch x 16-bit
PWM
8 ch (8-bit) / 4ch (16-bit)
8 ch (8-bit) / 4ch (16-bit)
RTC
Yes
Yes
10-bit resolution
10-bit resolution
ADC Resolution
ADC Inputs
Frequency modulated PLL
4 pins + internal
signals
8 pins + internal
signals
4 pins + internal
signals
Yes
8 pins + internal
signals
Yes
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
24
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Feature
MC9S12ZVHY64/ZVHL64
MC9S12ZVHY32/ZVHL32
Yes
Yes
1 (with independent clock source)
1 (with independent clock source)
Internal 1 MHz RC oscillator
Autonomous window
watchdog
Key Wakeup I/Os
General purpose I/Os (5 V)(1)
19
24
19
24
up to 73 for ZVHY
up to 78 for ZVHL
up to 100
up to 73 for ZVHY
up to 78 for ZVHL
up to 100
Direct Battery Voltage sense
pin
Yes
Yes
Vsup sense
Yes
Yes
1 General sensor
1 General sensor
VSUP Supply voltage
5.5 V – 18 V (normal operation)
up to 40V (protected operation)
5.5 V – 18 V (normal operation)
up to 40V (protected operation)
VDDX Output current
Determined by power dissipation of
external ballast
Determined by power dissipation of
external ballast
32 MHz
32 MHz
Chip temperature sensor
Maximum Bus Frequency
1. Maximum I/O count based on multiplexing with peripherals.
1.3
Maskset 0N39G and 1N39G device compare
0N39G and 1N39G device module versions differ as shown in Table 1-3.
NOTE User should take care when switching from 0N39G to 1N39G device
Table 1-3. Device Difference for 0N39G and 1N39G
1.4
0N39G
1N39G
SCI
V5
V6
BDC
V1
V2
MCU
no ADC reference voltage to IFR
ADC reference voltage to IFR
Chip-Level Features
On-chip modules available within the family include the following features:
• S12Z CPU core
• Up to 64 KB on-chip flash with ECC
• 2 KB EEPROM with ECC
• Up to 4 KB on-chip SRAM with ECC
• Phase locked loop (IPLL) frequency multiplier with internal filter
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
25
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
1.5
1 MHz internal RC oscillator with +/-1.3% accuracy over rated temperature range
4-20 MHz amplitude controlled pierce oscillator
32 KHz oscillator for RTC and LCD
Internal COP (watchdog) module
LCD driver for segment LCD with 40 frontplanes x 4 backplanes
Stepper Motor Controller (MC) with drivers for up to 2 motors
Up to 2 Stepper Stall Detector (SSD) modules (one for each motor)
Real Time Clock (RTC) support the Hour/Minute/Second function and frequency compensation
One Analog-to-Digital Converters (ADC) with 10-bit resolution and up to 8 channels available on
external pins
Two Timer module (TIM) supporting input/output channels that provide a range of 16-bit input
capture & output compare (8 channels)
One Pulse Width Modulation (PWM) modules with up to 8 x 8-bit channels
Simple Sound Generation (SSG) for monotonic tone generation
One Inter-Integrated Circuit (IIC) module
One Serial Peripheral Interface (SPI) module
Two Serial Communication Interface (SCI) module supporting LIN 1.3, 2.0, 2.1 and SAE J2602
communications on ZVHY. One serial communication interface (SCI) module with interface to
internal LIN phyiscal layer transceiver (with RX connected to a timer channel for frequency
calibration purposes, if desired) on ZVHL.
One MSCAN (up to 1 Mbp/s, CAN 2.0 A, B compliant) module
On-chip Voltage Regulator (VREG) for regulation of input supply and all internal voltages
Autonomous Periodic Interrupt (API) (combination with cyclic, watchdog)
Supply voltage sense with low battery warning.
Chip temperature sensor
Module Features
The following sections provide more details of the integrated modules.
1.5.1
S12Z Central Processor Unit (CPU)
The S12Z CPU is a revolutionary high-speed core, with code size and execution efficiencies over the S12X
CPU. The S12Z CPU also provides a linear memory map eliminating the inconvenience & performance
impact of page swapping.
• Harvard Architecture - parallel data and code access
• 3 stage pipeline
• 32-Bit wide instruction and databus
• 32-Bit ALU
• 24-bit addressing, i.e. 16 MB linear address space
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
26
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
•
•
•
•
•
Instructions and Addressing modes optimized for C-Programming & Compiler
Optimized address path so it is capable to run at maximum bus cycle without Flash wait states
— MAC unit 32bit += 32bit*32bit
— Hardware divider
— Single cycle multi-bit shifts (Barrel shifter)
Special instructions for fixed point match
Unimplemented opcode traps
Unprogrammed byte value (0xFF) defaults to SWI instruction
1.5.1.1
•
Background Debug Controller (BDC) with single-wire interface
— Non-intrusive memory access commands
— Supports in-circuit programming of on-chip nonvolatile memory
1.5.1.2
•
•
•
•
Background Debug Controller (BDC)
Debugger (DBG)
Enhanced DBG module including:
— Four comparators (A, B, C and D) each configurable to monitor PC addresses or addresses of
data accesses
— A and C compare full address bus and full 32-bit data bus with data bus mask register
— B and D compare full address bus only
— Three modes: simple address/data match, inside address range, or outside address range
— Tag-type or force-type hardware breakpoint requests
State sequencer control
64 x 64-bit circular trace buffer to capture change-of-flow addresses or address and data of every
access
— Begin, End and Mid alignment of tracing to trigger
Profiling mode
1.5.2
1.5.2.1
Embedded Memory
Flash
On-chip flash memory:
• Up to 64 KB of program flash memory
— 32 data bits plus 7 syndrome ECC (error correction code) bits allow single bit fault correction
and double fault detection
— Erase sector size 512 bytes
— Automated program and erase algorithm
— User margin level setting for reads
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
27
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
— Protection scheme to prevent accidental program or erase
1.5.2.2
•
Up to 2 KB EEPROM
— 16 data bits plus 6 syndrome ECC (error correction code) bits allow single bit error correction
and double fault detection
— Erase sector size 4 bytes
— Automated program and erase algorithm
— User margin level setting for reads
1.5.2.3
•
Clocks, Reset & Power Management Unit (CPMU)
Real Time Interrupt (RTI)
Clock Monitor, supervising the correct function of the oscillator (CM)
System reset generation
Autonomous periodic interrupt (API) (combination with cyclic, watchdog)
Low Power Operation
— RUN mode is the main full performance operating mode with the entire device clocked.
— WAIT mode when the internal CPU clock is switched off, so the CPU does not execute
instructions.
— Pseudo STOP - system clocks are stopped but the RTI, COP, API, RTC and LCD modules can
be enabled with clock source from the osc.
— STOP - the oscillator is stopped in this mode, all clocks are switched off and all counters and
dividers remain frozen. The 32K oscillator can be enabled, RTC and LCD can be still function
if enabled. The API and COP can still function if their clock source are from API
clock(ACLK).
1.5.3.1
•
SRAM
Up to 4 KB of general-purpose RAM with ECC
— Single bit error correction and double bit error detection
1.5.3
•
•
•
•
•
EEPROM
Internal Phase-Locked Loop (IPLL)
Phase-locked-loop clock frequency multiplier
— No external components required
— Reference divider and multiplier allow large variety of clock rates
— Automatic bandwidth control mode for low-jitter operation
— Automatic frequency lock detector
— Configurable option to spread spectrum for reduced EMC radiation (frequency modulation)
— Reference clock sources:
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
28
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
– Internal 1 MHz RC oscillator (IRC)
– External 4-20 MHz crystal oscillator/resonator
1.5.3.2
•
1.5.4
•
1.5.5
•
1.5.6
•
•
•
•
•
•
•
•
•
Internal RC Oscillator (IRC)
Trimmable internal reference clock.
— Frequency: 1 MHz; Trimmed accuracy over -40°C to 150°C junction temperature range: ±1.3%
Main External Oscillator (XOSCLCP)
Loop control Pierce oscillator using 4 MHz to 20 MHz crystal
— Current gain control on amplitude output
— Signal with low harmonic distortion
— Low power
— Good noise immunity
— Eliminates need for external current limiting resistor
— Transconductance sized for optimum start-up margin for typical crystals
— Oscillator pins shared with GPIO functionality
32K External Oscillator
Low speed oscillator using 32 kHz to 40 kHz crystal
— Low power
— Good noise immunity
— Oscillator pins shared with GPIO functionality
System Integrity Support
Power-On Reset (POR)
Illegal address detection
Low-voltage detection and low voltage reset generation
Clock monitor
High temperature Interrupt
Computer Operating Properly (COP) watchdog
— Configurable as window COP for enhanced failure detection
— Can be initialized out of reset using option bits located in flash memory
Unimplemented opcode traps
Unprogrammed byte value (0xFF) defaults to SWI instruction
ECC support on embedded NVM and SRAM
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
29
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.5.7
•
•
•
•
Real Time Clock (RTC)
Basic Clock functions with separate counters for Hour, Minutes and Seconds.
Hardware Compensation to reduce the effects of frequency variation on the 1 Hz clock (to the
counters) caused by temperature changes of crystal characteristics. Correction factor calculated by
firmware. (Programmable correction factor).
16-bit CPU register programming interface with protection against run-away code.
Option to output the buffered 32.768 kHz clock or the compensated 1 Hz clock for calibration.
1.5.8
•
•
•
Timer (TIM)
Up to two timer modules for input capture or output compare
— 8 x 16-bit channels per module
16-bit free-running counter with 8-bit precision prescaler
16-bit pulse accumulator
1.5.9
•
•
•
•
Pulse Width Modulation Module (PWM)
8 channels x 8-bit (4 channels x 16-bit)
Programmable period and duty cycle per channel
Center-aligned or edge-aligned outputs
Programmable clock select logic with a wide range of frequencies
1.5.10
•
•
•
•
•
•
•
•
Programmable amplitude level with maximum 11 bit resolution from zero amplitude to max
amplitude
Sound STOP function to stop sound generation immediately
Registers double-buffered synchronously reload at edge of tone to avoid distortion of output tone.
Interrupt generated when SSG configure registers reload occurs
Input clock prescaler with 11 bit resolution
Module disable for power saving when SSG is not in use
Separate or mixed frequency and amplitude outputs for flexibility in external hardware variation.
Decay/attack function which can decrease/increase sound amplitude automatically without cpu
interaction. The function includs linear, gong and exponential decay/attack profiles
1.5.11
•
•
•
Simple Sound Generator (SSG)
Liquid Crystal Display driver (LCD)
Up to 40 frontplanes and 4 backplanes or general-purpose input or output
5 modes of operation allow for different display sizes to meet application requirements
Unused frontplane and backplane pins can be used as general-purpose I/O
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
30
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.5.12
•
•
•
•
•
•
•
•
•
•
Compliant with LIN physical layer 2.2
Compliant with the SAE J2602-2 LIN standard for 1N39G
Standby mode with glitch-filtered wake-up
Slew rate selection optimized for the baud rates:
— 10 kBit/s
— 20 kBit/s
— Fast Mode (up to 250 kBit/s)
Selectable pull-up of 34 k or 330 k (in Shutdown Mode, 330 k only)
Current limitation on LIN Bus pin rising edges
Over-current protection with transmitter shutdown
LIN TxD-dominant timeout feature monitoring the LPTxD signal for 1N39G
Automatic transmitter shutdown in case of an over-current or TxD-dominant timeout.
Fulfills the OEM “Hardware Requirements for LIN (CAN and FlexRay) Interfaces in Automotive
Applications” v1.3 for 1N39G
1.5.13
•
•
•
•
•
•
Stepper Stall Detect (SSD)
Up to two SSD
Programmable Full Step State
Programmable Integration polarity
Blanking (recirculation) state
16-bit Integration Accumulator register
16-Bit Modulus Down Counter with interrupt
1.5.15
•
•
•
Stepper Motor Controller (MC)
PWM motor controller (MC) with up to 16 high current outputs
Each PWM channel switchable between two drivers in an H-bridge configuration
Left, right and center aligned outputs
Support for sine and cosine drive
Dithering
Output slew rate control
1.5.14
•
•
•
•
•
•
LIN physical layer transceiver
Multi-Scalable Controller Area Network (MSCAN)
Implementation of the CAN protocol — Version 2.0A/B
Five receive buffers with FIFO storage scheme
Three transmit buffers with internal prioritization using a “local priority” concept
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
31
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
•
•
Flexible maskable identifier filter supports two full-size (32-bit) extended identifier filters, or four
16-bit filters, or either 8-bit filters
Programmable wake-up functionality with integrated low-pass filter
1.5.16
•
•
•
•
•
•
•
•
•
•
•
•
•
Compatible with I2C bus standard
Multi-master operation
Software programmable for one of 256 different serial clock frequencies
Software selectable acknowledge bit
Interrupt driven byte-by-byte data transfer
Arbitration lost interrupt with automatic mode switching from master to slave
Calling address identification interrupt
Start and stop signal generation/detection
Repeated start signal generation
Acknowledge bit generation/detection
Bus busy detection
General Call Address detection
Compliant to ten-bit address
1.5.17
•
•
•
•
•
•
•
Serial Communication Interface Module (SCI)
Full-duplex or single-wire operation
Standard mark/space non-return-to-zero (NRZ) format
16-bit baud rate selection
Programmable character length
Programmable polarity for transmitter and receiver
Active edge receive wakeup
Break detection/generation supporting LIN communications
1.5.18
•
•
•
•
•
•
Inter-IC Bus Module (IIC)
Serial Peripheral Interface Module (SPI)
Configurable 8- or 16-bit data size
Full-duplex or single-wire bidirectional
Double-buffered transmit and receive
Master or slave mode
MSB-first or LSB-first shifting
Serial clock phase and polarity options
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
32
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.5.19
•
•
•
•
One ADC
— 10-bit resolution
— Up to 8 external channels & 8 internal channels
— Left or right aligned result data
— Continuous conversion mode
ADC directly writes results to RAM, preventing stall of further conversions
Internal signals monitored with the ADC module
— Vrh, Vrl, Vrl+Vrh/2, Vsup or Vsense monitor, Vbg, TempSense.
External pins can also be used as digital I/O
1.5.20
•
•
•
Supply Voltage Sensor (BATS)
VSENSE & VSUP pin low or a high voltage interrupt
VSENSE & VSUP pin can be routed via an internal divider to the internal ADC channel
Generation of low or high voltage interrupts
1.5.21
•
Analog-to-Digital Converter Module (ADC)
On-Chip Voltage Regulator system (VREG)
Voltage regulator
— Linear voltage regulator directly supplied by VSUP (protected VBAT)
— Low-voltage detect with low-voltage interrupt VSUP
— Power-On Reset (POR)
— Low-Voltage Reset (LVR)
— External ballast device support to reduce internal power dissipation
— Capable of supplying both the MCU internally plus external components
— Over-temperature interrupt
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
33
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.6
Block Diagram
Figure 1-1. MC9S12ZVHY/MC9S12ZVHL Families Block Diagram1
MOSI0
SCK0
SS0
BATS
Voltage Supply Monitor
Synchronous Serial IF
IIC0
SDA0
SCL0
S12ZCPU
Interrupt Module
PE[1:0]
BDC
Background
Debug Controller
EXTAL
Low Power Pierce
XTAL Oscillator
Clock Monitor
COP Watchdog
Real Time Interrupt
Auto. Periodic Int.
PLL with Frequency
Modulation option
PTE[3:2]
RESET
TEST
PE[3:2]
Reset Generation
and Test Entry
CAN0
msCAN 2.0B
PTT(KWT) PTAD(KWAD)
PP[7:0]
PC[7:0]
PH[7:0]
PG[7:0]
PF[7:0]
PD[7:0]
PB[3:0]
PA[7:0]
RXD1
TXD1
SGA0
SGT0
RXCAN0
TXCAN0
RTC
32.768K OSC
PTU
XIRQ/IRQ function
Motor Driver0
SSD 0
Motor Driver1
SSD 1
TIM0
IOC0_[7:0]
VLCD
LINPHY
LIN
LGND
SCI1
Asynchronous Serial IF
SSG0
PS[7:0]
32K_XTAL
PTJ
PJ[3:0]
PWM[7:0]
Internal 1 MHz
Oscillator
32K_EXTAL
PS7
PS6
PU[7:0]
PWM0
40 X 4 LCD display
PTE[1:0]
BKGD
DBG
Debug Module
4 Comparators
64 Byte Trace Buffer
PTS(KWS)
RXD0
SCI0
Asynchronous Serial IF TXD0
MISO0
SPI0
PT[7:0]
PTP
IOC1_[7:0]
PTC
TIM1
Voltage Regulator
(Nominal 12 V)
PTH
VSENSE
ECLK
PTG
VSS3
VSS2
VSS1
VDDA
VDDX1
VSUP
BCTL
PAD[7:0]
PTF
AN0_[7:0]
Up to 2 KB EEPROM with ECC
PTD
10-bit 8-channel
Analog-Digital Converter
PTB
Up to 4 KB RAM with ECC
VDDA/VRH
VSSA/VRL
ADC0
PTA
Up to 64 KB Flash with ECC
LIN
LGND
5V IO Supply
VDDX3,2,1/VSSX3,2,1
VDDM1/VSSM1
VDDA/VSSA
1. LINPHY is only avaiable on ZVHL part
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
34
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.6.1
Device Memory Map
Table 1-4 shows the device register memory map.
Table 1-4. Module Register Address Ranges
Address
Module
Size
(Bytes)
0x0000-0x0003
ID Registers
4
0x0004-0x000F
Reserved
12
0x0010-0x001F
INT
16
0x0020-0x006F
Reserved
80
0x0070-0x00FF
MMC
144
0x0100-0x017F
DBG
128
0x0180-0x01FF
Reserved
128
0x0200-0x037F
PIM
384
0x0380-0x039F
FTMRZ
32
0x03A0-0x03BF
Reserved
32
0x03C0-0x03CF
RAM ECC
16
0x03D0-0x03FF
Reserved
48
0x0400-0x042F
TIM1
48
0x0430-0x047F
Reserved
80
0x0480-0x04AF
PWM
48
0x04B0-0x05BF
Reserved
272
0x05C0-0x05EF
TIM0
48
0x05F0-0x05FF
Reserved
16
0x0600-0x063F
ADC0
64
0x0640-0x06BF
Reserved
128
0x06C0-0x06DF
CPMU
32
0x06E0-0x06EF
Reserved
16
0x06F0-0x06F7
BATS
8
0x06F8-0x06FF
Reserved
8
0x0700-0x0707
SCI0
8
0x0708-0x070F
Reserved
8
0x0710-0x0717
SCI1
8
0x0718-0x077F
Reserved
104
0x0780-0x0787
SPI0
8
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
35
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-4. Module Register Address Ranges
Address
Module
Size
(Bytes)
0x0788-0x07BF
Reserved
56
0x07C0-0x07C7
IIC0
8
0x07C8-0x07FF
Reserved
56
0x0800-0x083F
CAN0
64
0x0840-0x097F
Reserved
320
0x0980-0x0987
LINPHY
8
0x0988-0x09FF
Reserved
120
0x0A00-0x0A1F
LCD
32
0x0A20-0x0A3F
Reserved
32
0x0A40-0x0A7F
MC
64
0x0A80-0x0A87
SSD0
8
0x0A88-0x0A8F
Reserved
8
0x0A90-0x0A97
SSD1
8
0x0A98-0x0ADF
Reserved
72
0x0AE0-0x0AEF
RTC
16
0x0AF0-0x0AFF
Reserved
16
0x0B00-0x0B17
SSG0
24
0x0B18-0x0FFF
Reserved
1256
NOTE
Reserved register space shown in the table is not allocated to any module.
This register space is reserved for future use. Writing to these locations has
no effect. Read access to these locations returns zero.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
36
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Register Space
4 KB
RAM
0x00_0000
0x00_1000
max. 1 MB - 4 KB
EEPROM
0x10_0000
max. 1 MB - 48 KB
Reserved
0x1F_4000
Reserved (read only)
0x1F_8000
NVM IFR
0x1F_C000
512 Byte
5 KB
256 Byte
0x20_0000
Unimplemented
6 MB
0x80_0000
Program NVM
max. 8 MB
Unimplemented
address range
Low address aligned
High address aligned
0xFF_FFFF
Figure 1-2. MC9S12ZVHY/MC9S12ZVHL Families Global Memory Map.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
37
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.6.2
Part ID registers Assignments
The Part ID registers is located in four 8-bit registers at addresses 0x0000-0x0003. The read-only value is
a unique ID for each revision of the chip. Table 1-5 shows the assigned Part ID register value.
Table 1-5. Assigned IDs Numbers
1.7
Device
Mask Set number
Part ID
MC9S12ZVHY64
0N39G
32’h03160000
MC9S12ZVHY32
0N39G
32’h03160000
MC9S12ZVHY64
1N39G
32’h03161000
MC9S12ZVHY32
1N39G
32’h03161000
MC9S12ZVHL64
1N39G
32’h03161001
MC9S12ZVHL32
1N39G
32’h03161001
Signal Description and Device Pinouts
This section describes signals that connect off-chip. It includes a pinout diagram, a table of signal
properties, and detailed discussion of signals. It is built from the signal description sections of the
individual IP blocks on the device.
1.7.1
Pin Assignment Overview
Table 1-6 provides a summary of which ports are available for 100-pin and 144-pin package option.
Table 1-6. Port Availability by Package Option
MC9S12ZVHY/
MC9S12ZVHL
MC9S12ZVHY
MC9S12ZVHL
Port
144 LQFP
100 LQFP
100 LQFP
Port AD
PAD[7:0]
PAD[3:0]
PAD[3:0]
Port A
PA[7:0]
PA[7:2]
PA[7:2]
Port B
PB[3:0]
PB[3:0]
PB[3:0]
Port C
PC[7:0]
PC[5:4]
PC[5:2]
Port D
PD[7:0]
PD[7:3]
PD[7:3]
Port E
PE[3:0]
PE[3:0]
PE[3:0]
Port F
PF[7:0]
PF[7:0]
PF[7:0]
Port G
PG[7:0]
PG[7:0]
PG[7:0]
Port H
PH[7:0]
PH[4:0]
PH[4:0]
Port P
PP[7:0]
PP[1,3,5,7]
PP[0,1,3,5,7]
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
38
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-6. Port Availability by Package Option
MC9S12ZVHY/
MC9S12ZVHL
MC9S12ZVHY
MC9S12ZVHL
Port
144 LQFP
100 LQFP
100 LQFP
Port S
PS[7:0]
PS[7:0]
PS[7:0]
Port T
PT[7:0]
PT[7:6], PT[4:0]
PT[7:6], PT[4:0]
Port U
PU[7:0]
PU[7:0]
PU[7:0]
Port J
PJ[3:0]
—
PJ[1:0]
sum of ports
100
73
78
NOTE
To avoid current drawn from floating inputs, all non-bonded pins should be
configured as output or configured as input with a pull up or pull down
device enabled
1.7.2
1.7.2.1
Detailed Signal Descriptions
RESET — External Reset Signal
The RESET signal is an active low bidirectional control signal. It acts as an input to initialize the MCU to
a known start-up state, and an output when an internal MCU function causes a reset. The RESET pin has
an internal pull-up device.
1.7.2.2
TEST — Test Pin
This input only pin is reserved for factory test. This pin has an internal pull-down device.
NOTE
The TEST pin must be tied to ground in all applications.
1.7.2.3
MODC — Mode C Signal
The MODC signal is used as a MCU operating mode select during reset. The state of this signal is latched
to the MODC bit at the rising edge of RESET. The signal has an internal pull-up device.
1.7.2.4
PAD[7:0] / KWAD[7:0] — Port AD, Input Pins of ADC
PAD[7:0] are general-purpose input or output signals. The signals can be configured on per signal basis as
interrupt inputs with wake-up capability (KWAD[7:0]). These signals can have a pull-up or pull-down
device selected and enabled on per signal basis. Out of reset the pull devices are disabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
39
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.5
PA[7:0] — Port A I/O Signals
PA[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
1.7.2.6
PB[3:0] — Port B I/O Signals
PB[3:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
1.7.2.7
PC[7:0] — Port C I/O Signals
PC[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull devices are disabled.
1.7.2.8
PD[7:0] — Port D I/O Signals
PD[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
1.7.2.9
PE[3:0] — Port E I/O Signals
PE[3:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
1.7.2.10
PF[7:0] — Port F I/O Signals
PF[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
1.7.2.11
PJ[3:0] — Port J I/O Signals
PJ[3:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are disabled.
1.7.2.12
PG[7:0] — Port G I/O Signals
PG[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
1.7.2.13
PH[7:0] — Port H I/O Signals
PH[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull-down devices are enabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
40
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.14
PP[7:0] — Port P I/O Signals
PP[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. Out of reset the pull devices are disabled.
1.7.2.15
PS[7:0] / KWS[7:0] — Port S I/O signals
PS[7:0] are general-purpose input or output signals. The signals can be configured on per signal basis as
interrupt inputs with wake-up capability (KWS[7:0]). These signals can have a pull-up or pull-down device
selected and enabled on per signal basis. The signals can be configured on per signals basis as open drain
output. Out of reset the pull-up devices are enabled.
1.7.2.16
PT[7:0] / KWT[7:0] — Port T I/O signals
PT[7:0] are general-purpose input or output signals. The signals can be configured on per signal basis as
interrupt inputs with wake-up capability (KWT[7:0]). These signals can have a pull-up or pull-down
device selected and enabled on per signal basis. Out of reset the pull devices are disabled.
1.7.2.17
PU[7:0] — Port U I/O Signals
PU[7:0] are general-purpose input or output signals. They can have a pull-up or pull-down device selected
and enabled on per signal basis. They can have a slew rate enabled per signal basis also. Out of reset the
pull devices are disabled.
1.7.2.18
AN0_[7:0] — ADC0 Input Signals
AN0_[7:0] are the analog inputs of the Analog-to-Digital Converters.
1.7.2.19
VRH, VRL — ADC0 Reference Signals
VRH and VRL are the reference voltage input pins for the analog-to-digital converter.
1.7.2.20
SPI0 Signals
1.7.2.20.1
SS0 Signal
This signal is associated with the slave select SS functionality of the serial peripheral interface SPI0.
1.7.2.20.2
SCK0 Signal
This signal is associated with the serial clock SCK functionality of the serial peripheral interface SPI0.
1.7.2.20.3
MISO0 Signal
This signal is associated with the MISO functionality of the serial peripheral interface SPI0. This signal
acts as master input during master mode or as slave output during slave mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
41
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.20.4
MOSI0 Signal
This signal is associated with the MOSI functionality of the serial peripheral interface SPI0. This signal
acts as master output during master mode or as slave input during slave mode
1.7.2.21
1.7.2.21.1
SCI[1:0] Signals
RXD[1:0] Signals
These signals are associated with the receive functionality of the serial communication interfaces
(SCI[1:0]).
1.7.2.21.2
TXD[1:0] Signals
These signals are associated with the transmit functionality of the serial communication interfaces
(SCI[1:0]).
1.7.2.22
1.7.2.22.1
CAN0 Signals
RXCAN0 Signal
This signal is associated with the receive functionality of the scalable controller area network controller
(MSCAN0).
1.7.2.22.2
TXCAN0 Signal
This signal is associated with the transmit functionality of the scalable controller area network controller
(MSCAN0).
1.7.2.23
Timer IOC0_[7:0] & IOC1_[7:0] Signals
The signals IOC0_[7:0] are associated with the input capture or output compare functionality of the timer
(TIM0) module.
The signals IOC1_[7:0] are associated with the input capture or output compare functionality of the timer
(TIM1) module.
1.7.2.24
PWM[7:0] Signals
The signals PWM[7:0] are associated with the PWM module digital channel outputs.
1.7.2.25
1.7.2.25.1
LCD Signals
FP[39:0] Signals
These signals are associated with the segment LCD frontplane driver output.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
42
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.25.2
BP[3:0] Signals
These signals are associate the segment LCD backplane driver output.
1.7.2.26
1.7.2.26.1
RTC Signals
RTC_CAL Signal
The signal can be the RTC output clock CALCLK for external clock calibration or external 1HZ standard
clock input for on chip clock calibration.
1.7.2.27
1.7.2.27.1
SSG0 Signals
SGT0 Signals
The signal is from SSG0 output, it contain tone or tone mixed with amplitude digital output.
1.7.2.27.2
SGA0 Signals
The signal is from SSG0 output, it contain the amplitude digital output.
1.7.2.28
1.7.2.28.1
IIC0 Signals
SDA0 Signal
This signal is associated with the serial data pin of IIC0.
1.7.2.28.2
SCL0 Signal
This signal is associated with the serial clock pin of IIC0.
1.7.2.29
1.7.2.29.1
MC Signals
M0C0M, M0C0P, M0C1M and M0C1P Signals
These signal are associated with the high current PWM out pin for the motor driver.
1.7.2.29.2
M1C0M, M1C0P, M1C1M and M1C1P Signals
These signal are associated with the high current PWM out pin for the motor driver.
1.7.2.30
1.7.2.30.1
SSD[1:0] Signals
M0COSM, M0COSP, M0SINM and M0SINP Signals
These signal are used to measure the back EMF to calibrate the pointer reset position which are associated
with SSD[0].
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
43
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.30.2
M1COSM, M1COSP, M1SINM and M1SINP Signals
These signal are used to measure the back EMF to calibrate the pointer reset position which are associated
with SSD[1].
1.7.2.31
Interrupt Signals — IRQ and XIRQ
IRQ is a maskable level or falling edge sensitive input. XIRQ is a non-maskable level-sensitive interrupt.
1.7.2.32
1.7.2.32.1
Oscillator and Clock Signals
4-20MHz main Oscillator Pins — EXTAL and XTAL
EXTAL and XTAL are the crystal driver. On reset, the OSC is not enabled, all the device clocks are derived
from the internal reference clock. EXTAL is the oscillator input. XTAL is the oscillator output.
1.7.2.32.2
32.768kHz Oscillator Pins — 32K_EXTAL and 32K_XTAL
32K_EXTAL and 32K_XTAL are the 32.768KHZ crystal driver. On reset the OSC is not enabled.
32K_EXTAL is the oscillator input. 32K_XTAL is the oscillator output. Figure 1-3 is the 32K OSC
connection diagram. Refer to the Appendix Table K-1., “OSC32K DC Electrical Specifications for the Cx,
Cy and RF requirement. Both RTC and LCD clock source can from the 32K OSC. The OSC enable control
is from the RTC. If the RTCCTL2[CLKSRC] is set, then it will enable the 32K OSC. After enable the OSC,
it needs to wait enough time before enable the RTC and LCD. Refer to Appendix Table K-2., “OSC32K
Frequency Specifications for the startup time requirement.
32K OSC
32K_EXTAL
Rs
32K_XTAL
Cx
Cy
RF
Crystal or Resonator
Figure 1-3. 32K OSC Crystal/Resonator Connection
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
44
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.32.3
API_EXTCLK
This signal is associated with the output of the API.
1.7.2.32.4
ECLK
This signal is associated with the output of the divided bus clock (ECLK).
NOTE
This feature is only intended for debug purposes at room temperature.
It must not be used for clocking external devices in an application.
1.7.2.33
1.7.2.33.1
BDC and Debug Signals
BKGD — Background Debug signal
The BKGD signal is used as a pseudo-open-drain signal for the background debug communication. The
BKGD signal has an internal pull-up device.
1.7.2.33.2
PDO — Profiling Data Output
This is the profiling data output signal used when the DBG module profiling feature is enabled. This signal
is output only and provides a serial, encoded data stream that can be used by external development tools
to reconstruct the internal CPUcode flow.
1.7.2.33.3
PDOCLK — Profiling Data Output Clock
This is the PDO clock signal used when the DBG module profiling feature is enabled. This signal is output
only. During code profiling this is the clock signal that can be used by external development tools to sample
the PDO signal.
1.7.2.33.4
DBGEEV — External Event Input
This signal is the DBG external event input. It is input only. Within the DBG module, it allows an external
event to force a state sequencer transition, or trace buffer entry, or to gate trace buffer entries. A falling
edge at the external event signal constitutes an event. Rising edges have no effect. The maximum frequency
of events is half the internal core bus frequency.
1.7.2.34
1.7.2.34.1
LIN Physical Layer 0 Signals
LIN
This pad is connected to the single-wire LIN data bus.
1.7.2.34.2
LPTXD0
This is the LIN physical layer transmitter input signal.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
45
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.2.34.3
LPRXD0
This is the LIN physical layer receiver output signal.
1.7.2.34.4
LPDC0
This is the LIN LPDR1 register bit, visible at the designated pin for debug purposes.
1.7.3
VSENSE - Voltage Sensor Input
This pin can be connected to the supply (Battery) line for voltage measurements. The voltage present at
this input is scaled down by an internal voltage divider, and can be routed to the internal ADC via an analog
multiplexer. The pin itself is protected against reverse battery connections. To protect the pin from external
fast transients an external resistor is needed.
1.7.4
BCTL
BCTL provides the base current of an external bipolar of the VDDM, VDDA and VDDX supplies.
1.7.5
Power Supply Pins
The power and ground pins are described below. Because fast signal transitions place high, short-duration
current demands on the power supply, use bypass capacitors with high-frequency characteristics and place
them as close to the MCU as possible.
NOTE
All ground pins must be connected together in the application.
1.7.5.1
VDDX1, VDDX2, VDDX3, VSSX1, VSSX2, VSSX3 — Digital I/O Power and
Ground Pins
VDDX1 is a dedicated voltage regulator output for the digital I/O drivers. It must be connected externally
to the VDDX2 and VDDX3 pin, which supplies the VDDX domain pads. The VSSX1, VSSX2 and
VSSX3 pins are the ground pin for the digital I/O drivers. The VDDX1 and VDDX2 are internal connected
by metal, VDDX3 is not connect to VDDX1 or VDDX2 internally.
Bypass requirements on VDDX1/VSSX1, VDDX2/VSSX2 and VDDX3/VSSX3 depend on how heavily
the MCU pins are loaded.
1.7.5.2
VDDA, VSSA — External Power Supply Pins for ADC and VREG
These are the power supply and ground pins for the analog-to-digital converter and the voltage regulator.
1.7.5.3
VDDM1, VSSM1 — External Power Supply Pins for Motor PAD
These are the power supply and ground pins for the motor driver pads. It should be supply by external
power transistor.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
46
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.7.5.4
VLCD- Power Supply Reference Pin for LCD driver
VLCD is the voltage reference pin for the LCD driver. Adjusting the voltage on this pin will chan1ge the
display contrast.
1.7.5.5
VSS1, VSS2 — Core Ground Pin
The VDD voltage supply of nominally 1.8V is generated by the internal voltage regulator. The return
current path is through the VSS1 and VSS2 pin.
1.7.5.6
VSUP — Voltage Supply Pin for Voltage Regulator
VSUP is the 12V supply voltage pin for the on chip voltage regulator. This is the voltage supply input from
which the voltage regulator generates the on chip voltage supplies. It must be protected externally against
a reverse battery connection.
1.8
Package and Pinouts
The MC9S12ZVHY/MC9S12ZVHL Families will be offered in 100 pin and 144 pin LQFP packages.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
47
144
143
142
141
140
139
138
137
136
135
134
133
132
131
130
129
128
127
126
125
124
123
122
121
120
119
118
117
116
115
114
113
112
111
110
109
PG3 / FP27
PG4 / FP28
PG5 / FP29
PG6 / FP30
PG7 / FP31
PH0 / FP32
PH1 / FP33
PH2 / FP34
PH3 / FP35
PH4 / FP36
PH5 / FP37
PH6 / FP38
PH7 / FP39
VSSX3
VDDX3
PB0 / BP0
PB1 / BP1
PB2 / BP2
PB3 / BP3
PP4 / PWM04
PP2 / PWM02
PP0 / PWM00
NC
VSS2
PE3 / 32K_XTAL
PE2 / 32K_EXTAL
VSSA / VRL
VDDA / VRH
PAD7 / AN7 / KWAD7
PAD6 / AN6 / KWAD6
PAD5 / AN5 / KWAD5
PAD4 / AN4 / KWAD4
PAD3 / AN3 / KWAD3
PAD2 / AN2 / KWAD2
PAD1 / AN1 / KWAD1
PAD0 / AN0 / KWAD0
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
144 LQFP
Top view
108
107
106
105
104
103
102
101
100
99
98
97
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
80
79
78
77
76
75
74
73
BKGD / MODC
PC7 / TXD1
PC6 / RXD1
PC5 / SGA0 / IOC0_7
PC4 / SGT0 / IOC0_6
PT4 / PDO / IOC1_4 / KWT4
PT3 / PDOCLK / IOC1_3 / KWT3
PT2 / DBGEEV / IOC1_2 / KWT2
PT1 / RTC_CAL / IOC1_1 / KWT1
PT0 / API_EXTCLK / IOC1_0 / KWT0
VSSX2
VDDX2
PS7 / TXD0 / IRQ / KWS7
PS6 / RXD0 / XIRQ / KWS6
PS5 / (TXCAN0) / SDA0 / KWS5
PS4 / (RXCAN0) / SCL0 / KWS4
PS3 / SS0 / KWS3
PS2 / SCK0 / KWS2
PS1 / MOSI0 / KWS1
PS0 / MISO0 / KWS0
NC
BCTL
VSENSE
NC
NC
NC
PJ3
NC
PJ2
VSS1
PJ1
NC
PJ0
NC
NC
VSUP
FP17 / PF1
FP16 / PF0
FP15 / PD7
FP14 / PD6
FP13 / PD5
FP12 / PD4
FP11 / PD3
FP10 / PD2
FP9 / PD1
FP8 / PD0
FP7 / (PWM06) / PA7
FP6 / (PWM04) / PA6
FP5 / (PWM02) / PA5
FP4 / (PWM00) / PA4
FP3 / (SDA0) / PA3
FP2 / (SCL0) / PA2
FP1 / PA1
FP0 / PA0
TEST
PWM01 / PP1
PWM03 / PP3
(RXD1) / PWM05 / PP5
(TXD1) / PWM07 / PP7
NC
NC
RXCAN0 / PC0
TXCAN0 / PC1
IOC0_4 / LPRXD0 / PC2
IOC0_5 / LPTXD0 / PC3
RESET
EXTAL / PE0
XTAL / PE1
VSSX1
VDDX1
PWM06 / PP6
KWT5 / IOC1_5 / PT5
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
FP26 / PG2
FP25 / PG1
FP24 / PG0
VLCD
FP23 / PF7
KWT7 / IOC1_7 / PT7
NC
NC
M0COSM / M0C0M / IOC0_0 / PU0
M0COSP / M0C0P / PU1
M0SINM / M0C1M / IOC0_1 / PU2
M0SINP / M0C1P / / PU3
VDDM1
VSSM1
M1COSM / M1C0M / IOC0_2 / PU4
M1COSP / M1C0P / PU5
M1SINM / M1C1M / IOC0_3 / PU6
M1SINP / M1C1P / PU7
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
LGND
LIN
KWT6 / IOC1_6 / ECLK / PT6
FP22 / PF6
FP21 / PF5
FP20 / PF4
FP19 / PF3
FP18 / PF2
Figure 1-4. MC9S12ZVHY/MC9S12ZVHL Families 144-pin LQFP pin out
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
48
Freescale Semiconductor
100
99
98
97
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
80
79
78
77
76
PG4 / FP28
PG5 / FP29
PG6 / FP30
PG7 / FP31
PH0 / FP32
PH1 / FP33
PH2 / FP34
PH3 / FP35
PH4 / FP36
VSSX3
VDDX3
PB0 / BP0
PB1 / BP1
PB2 / BP2
PB3 / BP3
NC
VSS2
PE3 / 32K_XTAL
PE2 / 32K_EXTAL
VSSA / VRL
VDDA / VRH
PAD3 / AN3 / KWAD3
PAD2 / AN2 / KWAD2
PAD1 / AN1 / KWAD1
PAD0 / AN0 / KWAD0
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
100 LQFP
Top view
75
74
73
72
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
56
55
54
53
52
51
BKGD / MODC
PC5 / SGA0 / IOC0_7
PC4 / SGT0 / IOC0_6
PT4 / PDO / IOC1_4 / KWT4
PT3 / PDOCLK / IOC1_3 / KWT3
PT2 / DBGEEV / IOC1_2 / KWT2
PT1 / RTC_CAL / IOC1_1 / KWT1
PT0 / API_EXTCLK / IOC1_0 / KWT0
VSSX2
VDDX2
PS7 / TXD0 / IRQ / KWS7
PS6 / RXD0 / XIRQ / KWS6
PS5 / (TXCAN0) / SDA0 / KWS5
PS4 / (RXCAN0) / SCL0 / KWS4
PS3 / SS0 / KWS3
PS2 / SCK0 / KWS2
PS1 / MOSI0 / KWS1
PS0 / MISO0 / KWS0
NC
BCTL
VSENSE
VSS1
NC
NC
VSUP
FP17 / PF1
FP16 / PF0
FP15 / PD7
FP14 / PD6
FP13 / PD5
FP12 / PD4
FP11 / PD3
FP7 / (PWM06) / PA7
FP6 / (PWM04) / PA6
FP5 / (PWM02) / PA5
FP4 / (PWM00) / PA4
FP3 / (SDA0) / PA3
FP2 / (SCL0) / PA2
TEST
PWM01 / PP1
PWM03 / PP3
(RXD1) / PWM05 / PP5
(TXD1) / PWM07 / PP7
NC
NC
RESET
EXTAL / PE0
XTAL / PE1
VSSX1
VDDX1
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
FP27 / PG3
FP26 / PG2
FP25 / PG1
FP24 / PG0
VLCD
FP23 / PF7
KWT7 / IOC1_7 / PT7
M0COSM / M0C0M / IOC0_0 / PU0
M0COSP / M0C0P / PU1
M0SINM / M0C1M / IOC0_1 / PU2
M0SINP / M0C1P / PU3
VDDM1
VSSM1
M1COSM / M1C0M / IOC0_2 / PU4
M1COSP / M1C0P / PU5
M1SINM / M1C1M / IOC0_3 / PU6
M1SINP / M1C1P / PU7
VSS3
NC*
KWT6 / IOC1_6 / ECLK / PT6
FP22 / PF6
FP21 / PF5
FP20 / PF4
FP19 / PF3
FP18 / PF2
Figure 1-5. MC9S12ZVHY 100-pin LQFP pin out
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
49
100
99
98
97
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
80
79
78
77
76
PG4 / FP28
PG5 / FP29
PG6 / FP30
PG7 / FP31
PH0 / FP32
PH1 / FP33
PH2 / FP34
PH3 / FP35
PH4 / FP36
VSSX3
VDDX3
PB0 / BP0
PB1 / BP1
PB2 / BP2
PB3 / BP3
PP0 / PWM00
VSS2
PE3 / 32K_XTAL
PE2 / 32K_EXTAL
VSSA / VRL
VDDA / VRH
PAD3 / AN3 / KWAD3
PAD2 / AN2 / KWAD2
PAD1 / AN1 / KWAD1
PAD0 / AN0 / KWAD0
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
75
74
73
72
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
56
55
54
53
52
51
100 LQFP
Top view
BKGD / MODC
PC5 / SGA0 / IOC0_7
PC4 / SGT0 / IOC0_6
PT4 / PDO / IOC1_4 / KWT4
PT3 / PDOCLK / IOC1_3 / KWT3
PT2 / DBGEEV / IOC1_2 / KWT2
PT1 / RTC_CAL / IOC1_1 / KWT1
PT0 / API_EXTCLK / IOC1_0 / KWT0
VSSX2
VDDX2
PS7 / TXD0 / LPDC0 / IRQ / KWS7
PS6 / RXD0 / XIRQ / KWS6
PS5 / (TXCAN0) / SDA0 / KWS5
PS4 / (RXCAN0) / SCL0 / KWS4
PS3 / SS0 / KWS3
PS2 / SCK0 / KWS2
PS1 / MOSI0 / KWS1
PS0 / MISO0 / KWS0
NC
BCTL
VSENSE
VSS1
PJ1
PJ0
VSUP
FP17 / PF1
FP16 / PF0
FP15 / PD7
FP14 / PD6
FP13 / PD5
FP12 / PD4
FP11 / PD3
FP7 / (PWM06) / PA7
FP6 / (PWM04) / PA6
FP5 / (PWM02) / PA5
FP4 / (PWM00) / PA4
FP3 / (SDA0) / PA3
FP2 / (SCL0) / PA2
TEST
PWM01 / PP1
PWM03 / PP3
(RXD1) / PWM05 / PP5
(TXD1) / PWM07 / PP7
IOC0_4 / LPRXD0 / PC2
IOC0_5 / LPTXD0 / PC3
RESET
EXTAL / PE0
XTAL / PE1
VSSX1
VDDX1
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
FP27 / PG3
FP26 / PG2
FP25 / PG1
FP24 / PG0
VLCD
FP23 / PF7
KWT7 / IOC1_7 / PT7
M0COSM / M0C0M / IOC0_0 / PU0
M0COSP / M0C0P / PU1
M0SINM / M0C1M / IOC0_1 / PU2
M0SINP / M0C1P / PU3
VDDM1
VSSM1
M1COSM / M1C0M / IOC0_2 / PU4
M1COSP / M1C0P / PU5
M1SINM / M1C1M / IOC0_3 / PU6
M1SINP / M1C1P / PU7
LGND
LIN
KWT6 / IOC1_6 / ECLK / PT6
FP22 / PF6
FP21 / PF5
FP20 / PF4
FP19 / PF3
FP18 / PF2
Figure 1-6. MC9S12ZVHL 100-pin LQFP pin out
Table 1-7. Pin Summary
LQFP
Option
Function
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
1
2
PG2
FP26
—
—
—
—
Power
Supply
VDDX
Internal Pull
Resistor
CTRL
Reset
State
PERG/
PPSG
Pull
Down
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
50
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
2
3
PG1
FP25
—
—
—
—
3
4
PG0
FP24
—
—
—
4
5
VLCD
—
—
—
5
6
PF7
FP23
—
6
7
PT7
IOC1_7
7
—
—
8
—
9
Power
Supply
Internal Pull
Resistor
CTRL
Reset
State
VDDX
PERG/
PPSG
Pull
Down
—
VDDX
PERG/
PPSG
Pull
Down
—
—
VDDX
—
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
KWT7
—
—
—
VDDX
PERT/
PPST
Disabled
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
8
PU0
IOC0_0
M0C0M
M0COSM
—
—
VDDM
PERU/
PPSU
Disabled
10
9
PU1
—
M0C0P
M0COSP
—
—
VDDM
PERU/
PPSU
Disabled
11
10
PU2
IOC0_1
M0C1M
M0SINM
—
—
VDDM
PERU/
PPSU
Disabled
12
11
PU3
—
M0C1P
M0SINP
—
—
VDDM
PERU/
PPSU
Disabled
13
12
VDDM1
—
—
—
—
—
—
—
—
14
13
VSSM1
—
—
—
—
—
VDDM
—
—
15
14
PU4
IOC0_2
M1C0M
M1COSM
—
—
VDDM
PERU/
PPSU
Disabled
16
15
PU5
—
M1C0P
M1COSP
—
—
VDDM
PERU/
PPSU
Disabled
17
16
PU6
IOC0_3
M1C1M
M1SINM
—
—
VDDM
PERU/
PPSU
Disabled
18
17
PU7
—
M1C1P
M1SINP
—
—
VDDM
PERU/
PPSU
Disabled
19
—
—
—
—
—
—
—
—
—
—
20
—
—
—
—
—
—
—
—
—
—
21
—
—
—
—
—
—
—
—
—
—
22
—
—
—
—
—
—
—
—
—
—
23
—
—
—
—
—
—
—
—
—
—
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
51
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
24
—
—
—
—
—
—
—
25
—
—
—
—
—
—
26
—
—
—
—
—
27
—
—
—
—
28
—
—
—
29
18
LGDN
30
19
31
Power
Supply
Internal Pull
Resistor
CTRL
Reset
State
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
LIN(1)
—
—
—
—
—
—
—
—
20
PT6
ECLK
IOC1_6
KWT6
—
—
VDDX
PERT/
PPST
Disabled
32
21
PF6
FP22
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
33
22
PF5
FP21
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
34
23
PF4
FP20
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
35
24
PF3
FP19
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
36
25
PF2
FP18
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
37
26
PF1
FP17
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
38
27
PF0
FP16
—
—
—
—
VDDX
PERF/
PPSF
Pull
Down
39
28
PD7
FP15
—
—
—
—
VDDX
PERD/
PPSD
Pull
Down
40
29
PD6
FP14
—
—
—
—
VDDX
PERD/
PPSD
Pull
Down
41
30
PD5
FP13
—
—
—
—
VDDX
PERD/
PPSD
Pull
Down
42
31
PD4
FP12
—
—
—
—
VDDX
PERD/
PPSD
Pull
Down
43
32
PD3
FP11
—
—
—
—
VDDX
PERD/
PPSD
Pull
Down
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
52
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
44
—
PD2
FP10
—
—
—
—
45
—
PD1
FP9
—
—
—
46
—
PD0
FP8
—
—
47
33
PA7
(PWM6)
FP7
48
34
PA6
(PWM4)
49
35
PA5
50
36
51
Power
Supply
Internal Pull
Resistor
CTRL
Reset
State
VDDX
PERD/
PPSD
Pull
Down
—
VDDX
PERD/
PPSD
Pull
Down
—
—
VDDX
PERD/
PPSD
Pull
Down
—
—
—
VDDX
PERA/
PPSA
Pull
Down
FP6
—
—
—
VDDX
PERA/
PPSA
Pull
Down
(PWM2)
FP5
—
—
—
VDDX
PERA/
PPSA
Pull
Down
PA4
(PWM0)
FP4
—
—
—
VDDX
PERA/
PPSA
Pull
Down
37
PA3
(SDA0)
FP3
—
—
—
VDDX
PERA/
PPSA
Pull
Down
52
38
PA2
(SCL0)
FP2
—
—
—
VDDX
PERA/
PPSA
Pull
Down
53
—
PA1
FP1
—
—
—
—
VDDX
PERA/
PPSA
Pull
Down
54
—
PA0
FP0
—
—
—
—
VDDX
PERA/
PPSA
Pull
Down
55
39
TEST
—
—
—
—
—
VDDX
—
—
56
40
PP1
PWM1
—
—
—
—
VDDX
PERP/
PPSP
Disabled
57
41
PP3
PWM3
—
—
—
—
VDDX
PERP/
PPSP
Disabled
58
42
PP5
PWM5
(RXD1)
—
—
—
VDDX
PERP/
PPSP
Disabled
59
43
PP7
PWM7
(TXD1)
—
—
—
VDDX
PERP/
PPSP
Disabled
60
—
—
—
—
—
—
—
—
—
—
61
—
—
—
—
—
—
—
—
—
—
62
—
PC0
RXCAN0
—
—
—
—
VDDX
PERC/
PPSC
Disabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
53
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
Power
Supply
Internal Pull
Resistor
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
63
—
PC1
TXCAN0
—
—
—
—
VDDX
PERC/
PPSC
Disabled
64
44(2)
PC2
LPRXD0
IOC0_4
—
—
—
VDDX
PERC/
PPSC
Disabled
65
45(2)
PC3
LPTXD0
IOC0_5
—
—
—
VDDX
PERC/
PPSC
Disabled
66
46
RESET
—
—
—
—
—
VDDX
TEST pin
Pull Up
67
47
PE0
EXTAL
—
—
—
—
VDDX
PERE/
PPSE
Pull
Down
68
48
PE1
XTAL
—
—
—
—
VDDX
PERE/
PPSE
Pull
Down
69
49
VSSX1
—
—
—
—
—
—
—
—
70
50
VDDX1
—
—
—
—
—
VDDX
—
—
71
—
PP6
PWM6
—
—
—
—
VDDX
PERP/
PPSP
Disabled
72
—
PT5
IOC1_5
KWT5
—
—
—
VDDX
PERT/
PPST
Disabled
73
51
VSUP
—
—
—
—
—
VSUP
—
—
74
—
—
—
—
—
—
—
—
—
—
75
—
—
—
—
—
—
—
—
—
—
76
52(2)
PJ0
—
—
—
—
—
VDDX
PERJ/
PPSJ
Disabled
77
—
—
—
—
—
—
—
—
—
—
78
53(2)
PJ1
—
—
—
—
—
VDDX
PERJ/
PPSJ
Disabled
79
54
VSS1
—
—
—
—
—
—
—
—
80
—
PJ2
—
—
—
—
—
VDDX
PERJ/
PPSJ
Disabled
81
—
—
—
—
—
—
—
—
—
—
82
—
PJ3
—
—
—
—
—
VDDX
PERJ/
PPSJ
Disabled
83
—
—
—
—
—
—
—
—
—
—
84
—
—
—
—
—
—
—
—
—
—
CTRL
Reset
State
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
54
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
85
—
—
—
—
—
—
—
86
55
VSENS
E
—
—
—
—
87
56
BCTL
—
—
—
88
57
—
—
—
89
58
PS0
MISO0
90
59
PS1
91
60
92
Power
Supply
Internal Pull
Resistor
CTRL
Reset
State
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
KWS0
—
—
—
VDDX
PERS/
PPSS
Pull Up
MOSI0
KWS1
—
—
—
VDDX
PERS/
PPSS
Pull Up
PS2
SCK0
KWS2
—
—
—
VDDX
PERS/
PPSS
Pull Up
61
PS3
SS0
KWS3
—
—
—
VDDX
PERS/
PPSS
Pull Up
93
62
PS4
(RXCAN
0)
SCL0
KWS4
—
—
VDDX
PERS/
PPSS
Pull Up
94
63
PS5
(TXCAN
0)
SDA0
KWS5
—
—
VDDX
PERS/
PPSS
Pull Up
95
64
PS6
RXD0
XIRQ
KWS6
—
—
VDDX
PERS/
PPSS
Pull Up
96
65
PS7
TXD0
LPDC0
IRQ
KWS7
—
VDDX
PERS/
PPSS
Pull Up
(3)
97
66
VDDX2
—
—
—
—
—
VDDX
—
—
98
67
VSSX2
—
—
—
—
—
—
—
—
99
68
PT0
API_EXT
CLK
IOC1_0
KWT0
—
—
VDDX
PERT/
PPST
Disabled
100
69
PT1
RTC_CA
L
IOC1_1
KWT1
—
—
VDDX
PERT/
PPST
Disabled
101
70
PT2
DBGEEV
IOC1_2
KWT2
—
—
VDDX
PERT/
PPST
Disabled
102
71
PT3
PDOCLK
IOC1_3
KWT3
—
—
VDDX
PERT/
PPST
Disabled
103
72
PT4
PDO
IOC1_2
KWT2
—
—
VDDX
PERT/
PPST
Disabled
104
73
PC4
SGT0
IOC0_6
—
—
—
VDDX
PERC/
PPSC
Disabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
55
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
Power
Supply
Internal Pull
Resistor
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
105
74
PC5
SGA0
IOC0_7
—
—
—
VDDX
PERC/
PPSC
Disabled
106
—
PC6
RXD1
—
—
—
—
VDDX
PERC/
PPSC
Disabled
107
—
PC7
TXD1
—
—
—
—
VDDX
PERC/
PPSC
Disabled
108
75
BKGD
MODC
—
—
—
—
VDDX
109
76
PAD0
AN0_0
KWAD0
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
110
77
PAD1
AN0_1
KWAD1
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
111
78
PAD2
AN0_2
KWAD2
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
112
79
PAD3
AN0_3
KWAD3
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
113
—
PAD4
AN0_4
KWAD4
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
114
—
PAD5
AN0_5
KWAD5
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
115
—
PAD6
AN0_6
KWAD6
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
116
—
PAD7
AN0_7
KWAD7
—
—
—
VDDA
PER1AD/
PPS1AD
Disabled
117
80
VDDA/V
RH
—
—
—
—
—
VDDA
—
—
118
81
VSSA/V
RL
—
—
—
—
—
—
—
—
119
82
PE2
32K_EX
TAL
—
—
—
—
VDDX
PERE/
PPSE
Pull
Down
120
83
PE3
32K_XTA
L
—
—
—
—
VDDX
PERE/
PPSE
Pull
Down
121
84
VSS2
—
—
—
—
—
—
—
—
122
—
—
—
—
—
—
—
VDD
—
—
123
85(2)
PP0
PWM0
—
—
—
—
VDDX
PERP/
PPSP
Disabled
CTRL
Reset
State
Pull Up
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
56
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
Power
Supply
Internal Pull
Resistor
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
124
—
PP2
PWM2
—
—
—
—
VDDX
PERP/
PPSP
Disabled
125
—
PP4
PWM4
—
—
—
—
VDDX
PERP/
PPSP
Disabled
126
86
PB3
BP3
—
—
—
—
VDDX
PERB/
PPSB
Pull
Down
127
87
PB2
BP2
—
—
—
—
VDDX
PERB/
PPSB
Pull
Down
128
88
PB1
BP1
—
—
—
—
VDDX
PERB/
PPSB
Pull
Down
129
89
PB0
BP0
—
—
—
—
VDDX
PERB/
PPSB
Pull
Down
130
90
VDDX3
—
—
—
—
—
VDDX
—
—
131
91
VSSX3
—
—
—
—
—
—
—
—
132
—
PH7
FP39
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
133
—
PH6
FP38
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
134
—
PH5
FP37
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
135
92
PH4
FP36
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
136
93
PH3
FP35
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
137
94
PH2
FP34
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
138
95
PH1
FP33
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
139
96
PH0
FP32
—
—
—
—
VDDX
PERH/
PPSH
Pull
Down
140
97
PG7
FP31
—
—
—
—
VDDX
PERG/
PPSG
Pull
Down
141
98
PG6
FP30
—
—
—
—
VDDX
PERG/
PPSG
Pull
Down
142
99
PG5
FP29
—
—
—
—
VDDX
PERG/
PPSG
Pull
Down
CTRL
Reset
State
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
57
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-7. Pin Summary
LQFP
Option
Function
144
100
Pin
1st
Func.
2nd
Func.
3rd
Func.
4th
Func.
5th
Func.
143
100
PG4
FP28
—
—
—
—
144
1
PG3
FP27
—
—
—
—
Power
Supply
Internal Pull
Resistor
CTRL
Reset
State
VDDX
PERG/
PPSG
Pull
Down
VDDX
PERG/
PPSG
Pull
Down
1. NC on ZVHY, don’t connect to VDD/VSS
2. Pin not avaiable on ZVHY
3. Function not avaiable on ZVHY
1.9
Modes of Operation
The MCU can operate in different modes. These are described in 1.9.1 Chip Configuration Modes.
The MCU can operate in different power modes to facilitate power saving when full system performance
is not required. These are described in 1.9.3 Low Power Modes.
Some modules feature a software programmable option to freeze the module status whilst the background
debug module is active to facilitate debugging. This is referred to as freeze mode at module level.
1.9.1
Chip Configuration Modes
The different modes and the security state of the MCU affect the debug features (enabled or disabled).
The operating mode out of reset is determined by the state of the MODC signal during reset (Table 1-8).
The MODC bit in the MODE register shows the current operating mode and provides limited mode
switching during operation. The state of the MODC signal is latched into this bit on the rising edge of
RESET
Table 1-8. Chip Modes
Chip Modes
1.9.1.1
MODC
Normal single chip
1
Special single chip
0
Normal Single-Chip Mode
This mode is intended for normal device operation. The opcode from the on-chip memory is being
executed after reset (requires the reset vector to be programmed correctly). The processor program is
executed from internal memory.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
58
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.9.1.2
Special Single-Chip Mode
This mode is used for debugging operation, boot-strapping, or security related operations. The background
debug mode BDM is active on leaving reset in this mode.
1.9.2
Debugging Modes
The background debug mode (BDM) can be activated by the BDC module or directly when resetting into
Special Single-Chip mode. Detailed information can be found in the BDC module section.
Writing to internal memory locations using the debugger, whilst code is running or at a breakpoint, can
change the flow of application code.
The MC9S12ZVHY/MC9S12ZVHL Families supports BDC communication throughout the device Stop
mode. During Stop
mode, writes to control registers can alter the operation and lead to unexpected results. It is thus
recommended not to reconfigure the peripherals during STOP using the debugger.
1.9.3
Low Power Modes
The device has two dynamic-power modes (run and wait) and two static low-power modes stop and pseudo
stop). For a detailed description refer to Chapter 7, “S12 Clock, Reset and Power Management Unit
(S12CPMU_UHV_V5).
• Dynamic power mode: Run
— Run mode is the main full performance operating mode with the entire device clocked. The user
can configure the device operating speed through selection of the clock source and the phase
locked loop (PLL) frequency. To save power, unused peripherals must not be enabled.
• Dynamic power mode: Wait
— This mode is entered when the CPU executes the WAI instruction. In this mode the CPU does
not execute instructions. The internal CPU clock is switched off. All peripherals can be active
in system wait mode. For further power consumption reduction, the peripherals can
individually turn off their local clocks. Asserting RESET, XIRQ, IRQ, or any other interrupt
that is not masked ends system wait mode.
• Static power mode Pseudo-stop:
— In this mode the system clocks are stopped but the oscillator is still running and the real time
interrupt (RTI), watchdog (COP), RTC, LCD and Autonomous Periodic Interrupt (API) may
be enabled. Other peripherals are turned off. This mode consumes more current than system
STOP mode but, as the oscillator continues to run, the full speed wake up time from this mode
is significantly shorter.
• Static power mode: Stop
— The oscillator is stopped in this mode. By default, clocks are switched off and the counters and
dividers remain frozen. The Autonomous Periodic Interrupt (API), Key Wake-Up, RTC, CAN
and the CAN physical layer transceiver modules may be enabled to wake the device.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
59
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
— If the BDC is enabled, in Stop mode, the VREG remains in full performance mode and the
CPMU continues operation as in run mode..With BDC enabled and BDCCIS bit set, then all
clocks remain active during Stop mode to allow BDC access to internal peripherals. If the BDC
is enabled and BDCCIS is clear, then the BDCSI clock remains active, but bus and core clocks
are disabled. With the BDC enabled during Stop, the VREG full performance mode and clock
activity lead to higher current consumption than with BDC disabled
— If the BDC is enabled in Stop mode, then the voltage monitoring remains enabled.
1.10
Security
The MCU security mechanism prevents unauthorized access to the flash memory. It must be emphasized
that part of the security must lie with the application code. An extreme example would be application code
that dumps the contents of the internal memory. This would defeat the purpose of security. Also, if an
application has the capability of downloading code through a serial port and then executing that code (e.g.
an application containing bootloader code), then this capability could potentially be used to read the
EEPROM and Flash memory contents even when the microcontroller is in the secure state. In this example,
the security of the application could be enhanced by requiring a response authentication before any code
can be downloaded.
Device security details are also described in the flash block description (Section 21.5, “Security”).
1.10.1
Features
The security features of the S12Z chip family are:
• Prevent external access of the non-volatile memories (Flash, EEPROM) content
• Restrict execution of NVM commands
1.10.2
Securing the Microcontroller
The chip can be secured by programming the security bits located in the options/security byte in the Flash
memory array. These non-volatile bits keep the device secured through reset and power-down.
This byte can be erased and programmed like any other Flash location. Two bits of this byte are used for
security (SEC[1:0]). The contents of this byte are copied into the Flash security register (FSEC) during a
reset sequence.
The meaning of the security bits SEC[1:0] is shown in Table 1-9. For security reasons, the state of device
security is controlled by two bits. To put the device in unsecured mode, these bits must be programmed to
SEC[1:0] = ‘10’. All other combinations put the device in a secured mode. The recommended value to put
the device in secured state is the inverse of the unsecured state, i.e. SEC[1:0] = ‘01’.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
60
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-9. Security Bits
SEC[1:0]
Security State
00
1 (secured)
01
1 (secured)
10
0 (unsecured)
11
1 (secured)
NOTE
Please refer to the Section 21.5, “Security” for more security byte details.
1.10.3
Operation of the Secured Microcontroller
By securing the device, unauthorized access to the EEPROM and Flash memory contents is prevented.
Secured operation has the following effects on the microcontroller:
1.10.3.1
•
•
Background Debug Controller (BDC) operation is completely disabled.
Execution of Flash and EEPROM commands is restricted (described in flash block description).
1.10.3.2
•
•
Normal Single Chip Mode (NS)
Special Single Chip Mode (SS)
Background Debug Controller (BDC) commands are restricted
Execution of Flash and EEPROM commands is restricted (described in flash block description).
In special single chip mode the device is in active BDM after reset. In special single chip mode on a secure
device, only the BDC mass erase and BDC control and status register commands are possible. BDC access
to memory mapped resources is disabled. The BDC can only be used to erase the EEPROM and Flash
memory without giving access to their contents.
1.10.4
Unsecuring the Microcontroller
Unsecuring the microcontroller can be done using three different methods:
1. Backdoor key access
2. Reprogramming the security bits
3. Complete memory erase
1.10.4.1
Unsecuring the MCU Using the Backdoor Key Access
In normal single chip mode, security can be temporarily disabled using the backdoor key access method.
This method requires that:
• The backdoor key has been programmed to a valid value.
• The KEYEN[1:0] bits within the Flash options/security byte select ‘enabled’.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
61
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
•
The application program programmed into the microcontroller has the capability to write to the
backdoor key locations.
The backdoor key values themselves would not normally be stored within the application data, which
means the application program would have to be designed to receive the backdoor key values from an
external source (e.g. through a serial port).
The backdoor key access method allows debugging of a secured microcontroller without having to erase
the Flash. This is particularly useful for failure analysis.
NOTE
No word backdoor key word is allowed to have the value 0x0000 or 0xFFFF.
1.10.5
Reprogramming the Security Bits
In normal single chip mode, security can also be disabled by erasing and reprogramming the security bits
within Flash options/security byte to the unsecured value. Because the erase operation will erase the entire
sector from (0xFF_FE00–0xFF_FFFF), the backdoor key and the interrupt vectors will also be erased; this
method is not recommended for normal single chip mode. The application software can only erase and
program the Flash options/security byte if the Flash sector containing the Flash options/security byte is not
protected (see Flash protection). Thus Flash protection is a useful means of preventing this method. The
microcontroller will enter the unsecured state after the next reset following the programming of the
security bits to the unsecured value.
This method requires that:
• The application software previously programmed into the microcontroller has been designed to
have the capability to erase and program the Flash options/security byte.
• The Flash sector containing the Flash options/security byte is not protected.
1.10.6
Complete Memory Erase
The microcontroller can be unsecured by erasing the entire EEPROM and Flash memory contents. If
ERASE_FLASH is successfully completed, then the Flash unsecures the device and programs the security
byte automatically.
1.11
1.11.1
Resets and Interrupts
Resets
Table 1-10. lists all reset sources and the vector locations. Resets are explained in detail in the Chapter 7,
“S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
62
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-10. Reset Sources and Vector Locations
1.11.2
Vector Address
Reset Source
CCR
Mask
Local Enable
0xFFFFFC
Power-On Reset (POR)
None
None
Low Voltage Reset (LVR)
None
None
External pin RESET
None
None
Clock monitor reset
None
CPMUOSC(OSCE)
COP watchdog reset
None
CR[2:0] in CPMUCOP register
Interrupt Vectors
Table 1-11 lists all interrupt sources and vectors in the default order of priority. The interrupt module
description provides an Interrupt Vector Base register (IVBR) to relocate the vectors.
Table 1-11. Interrupt Vector Locations (Sheet 1 of 4)
CCR
Mask
Local Enable
Unimplemented page1 op-code trap
(SPARE)
None
None
-
-
Vector base + 0x1F4
Unimplemented page2 op-code trap
(TRAP)
None
None
-
-
Vector base + 0x1F0
Software interrupt instruction (SWI)
None
None
-
-
Vector base + 0x1EC
System call interrupt instruction
(SYS)
None
None
-
-
Vector base + 0x1E8
Machine exception
None
None
-
-
Vector Address(1)
Interrupt Source
Vector base + 0x1F8
Vector base + 0x1E4
Reserved
Vector base + 0x1E0
Reserved
Wake up
Wake up
from STOP from WAIT
Vector base + 0x1DC
Spurious interrupt
—
None
-
-
Vector base + 0x1D8
XIRQ interrupt request
X bit
None
Yes
Yes
Vector base + 0x1D4
IRQ interrupt request
I bit
IRQCR(IRQEN)
Yes
Yes
Vector base + 0x1D0
RTI time-out interrupt
I bit
CPMUINT (RTIE)
See CPMU
section
Yes
Vector base + 0x1CC
TIM0 timer channel 0
I bit
TIM0TIE (C0I)
No
Yes
Vector base + 0x1C8
TIM0 timer channel 1
I bit
TIM0TIE (C1I)
No
Yes
Vector base + 0x1C4
TIM0 timer channel 2
I bit
TIM0TIE (C2I)
No
Yes
Vector base + 0x1C0
TIM0 timer channel 3
I bit
TIM0TIE (C3I)
No
Yes
Vector base + 0x1BC
TIM0 timer channel 4
I bit
TIM0TIE (C4I)
No
Yes
Vector base + 0x1B8
TIM0 timer channel 5
I bit
TIM0TIE (C5I)
No
Yes
Vector base + 0x1B4
TIM0 timer channel 6
I bit
TIM0TIE (C6I)
No
Yes
Vector base + 0x1B0
TIM0 timer channel 7
I bit
TIM0TIE (C7I)
No
Yes
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
63
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-11. Interrupt Vector Locations (Sheet 2 of 4)
Vector Address(1)
Interrupt Source
CCR
Mask
Local Enable
Vector base + 0x1AC
TIM0 timer overflow
I bit
TIM0TSCR2(TOI)
No
Yes
Vector base + 0x1A8
TIM0 Pulse accumulator A overflow
I bit
TIM0PACTL(PAOVI)
No
Yes
Vector base + 0x1A4
TIM0 Pulse accumulator input edge
I bit
TIM0PACTL(PAI)
No
Yes
Vector base + 0x1A0
SPI0
I bit
SPI0CR1 (SPIE, SPTIE)
No
Yes
Vector base + 0x19C
SCI0
I bit
SCI0CR2
Yes
Yes
Vector base + 0x198
SCI1
I bit
SCI1CR2
Yes
Yes
Vector base + 0x194
Reserved
Vector base + 0x190
Reserved
Wake up
Wake up
from STOP from WAIT
Vector base + 0x18C
ADC0 Error
I bit
ADC0EIE(IA_EIE,CMD_EIE,
EOL_EIE,TRIG_EIE,RSTAR_
EIE,LDOK_EIE)
ADC0IE(CONIF_OIE)
No
Yes
Vector base + 0x188
ADC0 conversion sequence abort
I bit
ADC0IE(SEQAR_IE)
No
Yes
Vector base + 0x184
ADC0 conversion complete
I bit
ADC0CONIE[15:0]
No
Yes
Vector base + 0x180
Oscillator status interrupt
I bit
CPMUINT (OSCIE)
No
Yes
Vector base + 0x17C
PLL lock interrupt
I bit
CPMUINT (LOCKIE)
No
Yes
No
Yes
Vector base + 0x178
to
Vector base + 0x174
Vector base + 0x170
Reserved
RAM error
I bit
Vector base + 0x16C
to
Vector base + 0x168
ECCIE (SBEEIE)
Reserved
Vector base + 0x164
FLASH error
I bit
FERCNFG (SFDIE)
No
Yes
Vector base + 0x160
FLASH command
I bit
FCNFG (CCIE)
No
Yes
Vector base + 0x15C
CAN0 wake-up
I bit
CAN0RIER (WUPIE)
Yes
Yes
Vector base + 0x158
CAN0 errors
I bit
CAN0RIER (CSCIE, OVRIE)
No
Yes
Vector base + 0x154
CAN0 receive
I bit
CAN0RIER (RXFIE)
No
Yes
Vector base + 0x150
CAN0 transmit
I bit
CAN0RIER (TXEIE[2:0])
No
Yes
Vector base + 0x14C
to
Vector base + 0x148
Vector base + 0x144
Reserved
LINPHY0 over-current interrupt
Vector base + 0x140 BATS supply voltage monitor interrupt
Vector base + 0x13C
to
Vector base + 0x130
I bit
LP0IE (LP0ERR)
Yes
Yes
I bit
BATIE (BVHIE,BVLIE)
No
Yes
Reserved
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
64
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-11. Interrupt Vector Locations (Sheet 3 of 4)
Vector Address(1)
Interrupt Source
CCR
Mask
Local Enable
Vector base + 0x12C
Port T interrupt
I bit
PIET(PIET[7:0])
Wake up
Wake up
from STOP from WAIT
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Reserved
Vector base + 0x128
Vector base + 0x124
Port S interrupt
I bit
Vector base + 0x120
to
Vector base + 0x108
PIES(PIES[7:0])
Reserved
Vector base + 0x104
Low-voltage interrupt (LVI)
I bit
Vector base + 0x100
Autonomous periodical interrupt
(API)
I bit
Vector base + 0xFC
High temperature interrupt
I bit
Vector base + 0xF8
CPMUCTRL (LVIE)
CPMUAPICTRL (APIE)
CPMUHTCTL(HTIE)
Reserved
Vector base + 0xF4
Port AD interrupt
I bit
Vector base + 0xF0
to
Vector base + 0xB8
PIEADL(PIEADL[7:0])
Reserved
Vector base + 0xB4
IIC
I bit
Vector base + 0xB0
IIC0IBCR(IBIE)
Reserved
Vector base + 0xAC
TIM1 timer channel 0
I bit
TIM1TIE (C0I)
No
Yes
Vector base + 0xA8
TIM1 timer channel 1
I bit
TIM1TIE (C1I)
No
Yes
Vector base + 0xA4
TIM1 timer channel 2
I bit
TIM1TIE (C2I)
No
Yes
Vector base + 0xA0
TIM1 timer channel 3
I bit
TIM1TIE (C3I)
No
Yes
Vector base + 0x9C
TIM1 timer channel 4
I bit
TIM1TIE (C4I)
No
Yes
Vector base + 0x98
TIM1 timer channel 5
I bit
TIM1TIE (C5I)
No
Yes
Vector base + 0x94
TIM1 timer channel 6
I bit
TIM1TIE (C6I)
No
Yes
Vector base + 0x90
TIM1 timer channel 7
I bit
TIM1TIE (C7I)
No
Yes
Vector base + 0x8C
TIM1 timer overflow
I bit
TIM1TSCR2(TOI)
No
Yes
Vector base + 0x88
TIM1 Pulse accumulator A overflow
I bit
TIM1PACTL(PAOVI)
No
Yes
Vector base + 0x84
TIM1 Pulse accumulator input edge
I bit
TIM1PACTL(PAI)
No
Yes
Vector base + 0x80
to
Vector base + 0x7C
Reserved
Vector base + 0x78
Motor Control Timer Overflow
I bit
MCCTL1(MCOCIE)
No
Yes
Vector base + 0x74
SSD0
I bit
MDC0CTL(MCZIE,AOVIE)
No
Yes
Vector base + 0x70
SSD1
I bit
MDC1CTL(MCZIE,AOVIE)
No
Yes
Vector base + 0x6C
to
Vector base + 0x68
Reserved
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
65
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-11. Interrupt Vector Locations (Sheet 4 of 4)
Vector Address(1)
Interrupt Source
CCR
Mask
Vector base + 0x64
RTC
I bit
RTCCTL4(HRIE,MINIE,SECI
E,COMPIE,TB0IE)
Yes
Yes
Vector base + 0x60
SSG0 Ready For Next Data(RNDI)
I bit
SSG0IE(RNDIE)
No
Yes
Vector base + 0x5C
to
Vector base + 0x10
1. 15 bits vector address based
1.11.3
Local Enable
Wake up
Wake up
from STOP from WAIT
Reserved
Effects of Reset
When a reset occurs, MCU registers and control bits are initialized. For RTC block, some registers are
power on reset only. Refer to the respective block sections for register reset states.
On each reset, the Flash module executes a reset sequence to load Flash configuration registers
1.11.3.1
Flash Configuration Reset Sequence Phase
On each reset, the Flash module will hold CPU activity while loading Flash module registers from the
Flash memory. If double faults are detected in the reset phase, Flash module protection and security may
be active on leaving reset. This is explained in more detail in the Section 21.6, “Initialization” of flash
block.
1.11.3.2
Reset While Flash Command Active
If a reset occurs while any Flash command is in progress, that command will be immediately aborted. The
state of the word being programmed or the sector/block being erased is not guaranteed.
1.11.3.3
I/O Pins
Refer to Chapter 2, “Port Integration Module (S12ZVHYPIMV1) for reset configurations of all peripheral
module ports.
1.11.3.4
RAM
The system RAM arrays, including their ECC syndromes, are initialized following a power on reset, but
not out of warm reset. All other RAM arrays are not initialized out of any type of reset.
With the exception of resets resulting from low voltage conditions, the RAM content is unaltered by a reset
occurrence.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
66
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.12
COP Configuration
The COP time-out rate bits CR[2:0] and the WCOP bit in the CPMUCOP register are loaded from the
Flash configuration field byte at global address 0xFF_FE0E during the reset sequence. See Table 1-12 and
Table 1-13 for coding
Table 1-12. Initial COP Rate Configuration
NV[2:0] in
FOPT Register
CR[2:0] in
COPCTL Register
000
111
001
110
010
101
011
100
100
011
101
010
110
001
111
000
Table 1-13. Initial WCOP Configuration
1.13
NV[3] in
FOPT Register
WCOP in
COPCTL Register
1
0
0
1
ADC0 Internal Channels
Table 1-14 lists the internal sources which are connected to these special conversion channels.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
67
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
Table 1-14. ADC0 Channel Assignment
ADC0CMD_1 CH_SEL[5:0]
1.14
[5]
[4]
[3]
[2]
[1]
[0]
Analog Input
Channel
Usage
0
0
1
0
0
0
Internal_0
ADC temperature sensor
0
0
1
0
0
1
Internal_1
Bandgap Voltage VBG or
Vreg temperature sensor
VHT
0
0
1
0
1
0
Internal_2
RESERVED
0
0
1
0
1
1
Internal_3
RESERVED
0
0
1
1
0
0
Internal_4
VSENSE or VSUP
selectable in BATS
module
0
0
1
1
0
1
Internal_5
RESERVED
0
0
1
1
1
0
Internal_6
RESERVED
0
0
1
1
1
1
Internal_7
RESERVED
The ADC0 VRH/VRL
The ADC0 offers two possible sources for both reference voltages VRH[1:0] and VRL[1:0]. On the
MC9S12ZVHY/MC9S12ZVHL Families only VRH[1], VRL[1] sources are connected at device level(to
VDDA, VSSA respectively), the VRH[0], VRL[0] sources are not connected. Thus the application must
set both VRH_SEL and VRL_SEL in the ADC0CCMD_1 to 1.
1.15
The ADC0 Conversion Resolution
The MC9S12ZVHY/MC9S12ZVHL Families only support 10 and 8 bit converstion resolution, although
ADC block guide still has 12 bit related descrition.
1.16
ADC Result Reference
MCUs of the MC9S12ZVHY/MC9S12ZVHL Families are able to measure the internal reference voltage
VBG(see Table 1-14). VBG is a constant voltage with a narrow distribution over temperature and external
voltage supply (see Table A-16).
A 10-bit left justified1 ADC conversion result of VBG is provided at address 0x1F_C040/0x1F_C041 in
the NVM’s IFR for reference.The measurement conditions of the reference conversion are listed in
Section A.1.10, “ADC Conversion Result Reference””. By measuring the voltage VBG (see Table 1-14)
1. The format of the stored VBG reference value is still subject to change.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
68
Freescale Semiconductor
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
and comparing the result to the reference value in the IFR, it is possible to determine the ADC’s reference
voltage VRH in the application environment:
StoredReference
V RH = ------------------------------------------------------- • 5V
ConvertedReference
The exact absolute value of an analog conversion can be determined as follows:
StoredReference • 5V
Result = ConvertedADInput • -----------------------------------------------------------------nConvertedReference • 2
With:
ConvertedADInput:
ConvertedReference:
StoredReference:
n:
1.17
Result of the analog to digital conversion of the desired pin
Result of channel “Internal_1” conversion
Value in IFR location 0x1F_C040/0x1F_C041
ADC resolution (10 bit)
BDC Clock Source Connectivity
The BDC clock, BDCCLK, is mapped to the IRCCLK generated in CPMU module. The BDC clock,
BDCFCLK, is mapped to the bus clock.
1.18
FTMRZ Connectivity
The soc_erase_all_req input to the flash module is driven directly by a BDC erase flash request resulting
from the BDC ERASE_FLASH command.
The FTMRZ FCLKDIV register is forced to 0x05 by the BDC ERASE_FLASH command. This
configures the clock frequency correctly for the initial bus frequency on leaving reset. The bus frequency
must not be changed before launching the ERASE_FLASH command.
1.19
RTC Clock Source
The RTC has three clock source, the 32K OSC, main OSC or IRC, refer to Section 18.4.2, “RTC Control
Register 2 (RTCCTL2)” for more information. When select main OSC, user need to config the registers in
CPMU block, refer to CPMU block guide for more detailed information. And main OSC will be stop if
silicon enter full stop mode. And if select the 1 MHz internal IRC clock, then the clock will be off when
enter full stop or pseudo stop mode, the RTC function will be stop.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
69
Chapter 1 Device Overview MC9S12ZVHY/MC9S12ZVHL Families
1.20
LCD Clock Source Connectivity
The LCD’s clock is connected to the RTC’s RTCCLK output. User need to set the RTCCTL2[RTCPS] in
Section 18.4.2, “RTC Control Register 2 (RTCCTL2)” to get the expect RTCCLK frequency if it uses the
main OSC as clock source.
1.21
32K OSC enable control
The 32K OSC enable is controlled by the RTCCTL2[CLKSRC] in Section 18.4.2, “RTC Control Register
2 (RTCCTL2)”. Setting the bits to 2’b01 enable the 32K OSC, it also selects the 32K OSC as the source
for LCD and RTC clock. RTCCTL2 is write one time only in NSC mode, once enable the 32K OSC, it will
be not able to switch off.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
70
Freescale Semiconductor
Chapter 2
Port Integration Module (S12ZVHYPIMV1)
Revision History
Rev. No.
(Item No.)
Date (Submitted
By)
V0.01
Mar 2012
• Initial Version
V0.02
Mar 2012
• fix typos
V0.04
Oct 2012
• fix typos, add XIRQ function explain
V0.05
Jan 2014
• add the ZVHL LINPHY related function
2.1
2.1.1
Sections
Affected
Substantial Change(s)
Introduction
Overview
The MC9S12ZVHY/MC9S12ZVHL Families port integration module establishes the interface between
the peripheral modules and the I/O pins for all ports. It controls the electrical pin properties as well as the
signal prioritization and multiplexing on shared pins.
This document covers:
• 8-pin port A associated with the LCD FP[7:0] and rerouting of PWM0, PWM2, PWM4, PWM6
channels and rerouting of IIC
• 4-pin port B associated with the LCD BP[3:0]
• 8-pin port C associated with TIM0_IOC[7:4], MSCAN0, SCI1, SSG0 and LINPHY0’s
LPTXD0&LPRXD0
• 8-pin port D associated with LCD FP[15:8]
• 4-pin port E associated with the external 4-16MHZ oscillator and 32.768KHZ oscillator
• 8-pin port F associated with LCD FP[23:16]
• 8-pin port G associated with LCD FP[31:24]
• 8-pin port H associated with LCD FP[39:32]
• 4-pin Port J
• 8-pin port P associated with 8 PWM channels; associated with the rerouting SCI1 function also.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
71
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
•
•
•
•
8-pin port S associated with SCI0, IIC0, SPI0 modules and rerouting of MSCAN0. PS7 and PS6
also associated with IRQ, XIRQ interrupt inputs; associated with the key wakeup functions.
LINPHY0’s LPDC0 is routing to this PS7 also.
8-pin port T with the key wakeup function and 8 TIM1 channels, also associated with
— API_EXTCLK
— DBG external signals PDO, PDOCLK and DBGEEV
— ECLK output
8-pin port AD associated with 8 ADC0 channels; associated with the key wakeup function also
8-pin port U associated with SSD0, SSD1, 2 Motor controls and 4 TIM0 channels
Most I/O pins can be configured by register bits to select data direction and to enable and select pullup or
pulldown devices.
NOTE
This document assumes the availability of all features (144-pin package
option). Some functions are not available on lower pin count package
options. Refer to the pin-out summary in the SOC Guide.
2.1.2
Features
The PIM includes these distinctive registers:
• Data registers and data direction registers for ports A, B, C, D, E, F, G, H, T, S, P, AD, U and J
when used as general-purpose I/O
• Control registers to enable pull devices and select pullups/pulldowns on ports A, B, C, D, E, F, G,
H, T, S, P, AD, U and J
• Single control register bit to enable pullups on BKGD pin
• Control register to enable open-drain (wired-or) mode on port S and port A (only PA3, PA2)
• Control register to enable digital input buffers on port AD
• Control register to enable the slew rate control on Port U.
• Interrupt flag register for pin interrupts on port S, T and AD
• Control register to configure IRQ pin operation
• Control register to enable ECLK output
• Control register to enable the RTC_CAL input or output
• Routing registers to support signal relocation on external pins and control internal routings:
— IIC0 to alternative pins
— SCI1 to alternative pins
— MSCAN0 to alternative pins
— PWM0, PWM2, PWM4, PWM6 to alternative pins
— rerouting the RTC_CAL to TIM1 channel
— rerouting the RXD0 and RXD1 to TIM1 channel for the baud rate detection
— Various SCI0-LINPHY0 routing options supporting standalone use and conformance testing
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
72
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
A standard port pin has the following minimum features:
• Input/output selection
• 5V output drive
• 5V digital and analog input
• Input with selectable pullup or pulldown device
Optional features supported on dedicated pins:
•
Open drain for wired-or connections
•
Interrupt input with glitch filtering
•
Slew rate control on motor pads
2.2
External Signal Description
This section lists and describes the signals that do connect off-chip.
Table 2-1 shows all pins with the pins and functions that are controlled by the PIM. Routing options are
denoted in parenthesis.
NOTE
If there is more than one function associated with a pin, the output priority
is indicated by the position in the table from top (highest priority) to bottom
(lowest priority).
Table 2-1. Pin Functions and Priorities
Port
Pin Name
Pin Function
& Priority(1)
I/O
-
BKGD
MODC(2)
I
BKGD
Description
MODC input during RESET
Routing Register
Pin
Function
after Reset
BKGD
I/O S12ZBDC communication
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
73
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
A
PA7
FP7
O
LCD FP7 signal
O
PWM channel 6
(PWM6)
PTA[7]
PA6
FP6
O
LCD FP6 signal
(PWM4)
O
PWM channel 4
O
LCD FP5 signal
(PWM2)
O
PWM channel 2
PA3
FP4
O
LCD FP4 signal
O
PWM channel 0
PA2
PA1
FP3
I/O General-purpose
PB3
PTA[2]
I/O General-purpose
BP3
PTB[3]
PB2
BP2
PTB[2]
PB1
BP1
PTB[1]
PB0
BP0
PTB[0]
PWM2RR
PWM6RR
O
IIC0RR
LCD FP2 signal
I/O SCL of IIC0 signal
PTA[0]
B
O
(SCL0)
FP0
PWM4RR
LCD FP3 signal
I/O SDA of IIC0 signal
PTA[1]
PA0
O
PTA[3]
FP1
PWM6RR
I/O General-purpose
(SDA0)
FP2
GPIO
I/O General-purpose
(PWM0)
PTA[4]
Pin
Function
after Reset
I/O General-purpose
FP5
PTA[5]
PA4
Routing Register
I/O General-purpose
PTA[6]
PA5
Description
IIC0RR
LCD FP1 signal
I/O General-purpose
O
LCD FP0 signal
I/O General-purpose
O
LCD BP3 signals
GPIO
I/O General-purpose
O
LCD BP2 signal
I/O General-purpose
O
LCD BP1 signal
I/O General-purpose
O
LCD BP0 signal
I/O General-purpose
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
74
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
C
PC7
TXD1
O
PTC[7]
I/O General-purpose
PC6
RXD1
PC5
PC4
PC3
PC2
I
IOC0_7
O
TIM0 channel 7
SGA of SSG0
SGA0
O
PTC[5]
I/O General-purpose
IOC0_6
O
TIM0 channel 6
SGT0
O
SGT of SSG0
PTC[4]
I/O General-purpose
IOC0_5
O
TIM0 channel 5
LPTXD0
I
TXD of LINPHY0
PTC[3]
I/O General-purpose
IOC0_4
O
TIM0 channel 4
LPRXD0
O
RXD of LINPHY0
TXCAN0
PC0
RXCAN0
PTC[1]
FP15
PTD[7]
PD6
FP14
PTD[6]
PD5
FP13
PTD[5]
PD4
FP12
PTD[4]
PD3
FP11
PTD[3]
PD2
FP10
PTD[2]
PD1
FP9
PTD[1]
PD0
FP8
PTD[0]
GPIO
S0L00RR2-0
S0L00RR2-0
I/O General-purpose
PC1
PD7
Pin
Function
after Reset
RXD of SCI1
I/O General-purpose
PTC[0]
Routing Register
TXD of SCI1
PTC[6]
PTC[2]
D
Description
O
TX of MSCAN0
C0RR
I/O General-purpose
I
RX of MSCAN0
C0RR
I/O General-purpose
O
LCD FP15 signal
GPIO
I/O General-purpose
O
LCD FP14 signal
I/O General-purpose
O
LCD FP13 signal
I/O General-purpose
O
LCD FP12 signal
I/O General-purpose
O
LCD FP11 signal
I/O General-purpose
O
LCD FP10 signal
I/O General-purpose
O
LCD FP9 signal
I/O General-purpose
O
LCD FP8 signal
I/O General-purpose
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
75
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
PE3
32K_XTAL
-
PE2
32K_EXTAL
PTE[3]
E
PTE[2]
PE1
XTAL
PTE[1]
PE0
EXTAL
PTE[0]
F
PF7
FP23
PTF[7]
PF6
FP22
PTF[6]
PF5
FP21
PTF[5]
PF4
FP20
PTF[4]
PF3
FP19
PTF[3]
PF2
FP18
PTF[2]
PF1
FP17
PTF[1]
PF0
FP16
PTF[0]
Description
Routing Register
Pin
Function
after Reset
32K OSC signal
I/O General-purpose
-
32K OSC signal
I/O General-purpose
-
CPMU OSC signal
GPIO
I/O General-purpose
-
CPMU OSC signal
I/O General-purpose
O
LCD FP23 signal
GPIO
I/O General-purpose
O
LCD FP22 signal
I/O General-purpose
O
LCD FP21 signal
I/O General-purpose
O
LCD FP20 signal
I/O General-purpose
O
LCD FP19 signal
I/O General-purpose
O
LCD FP18 signal
I/O General-purpose
O
LCD FP17 signal
I/O General-purpose
O
LCD FP16 signal
I/O General-purpose
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
76
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
G
PG7
FP31
O
PTG[7]
PG6
FP30
PTG[6]
PG5
FP29
PTG[5]
PG4
FP28
PTG[4]
PG3
FP27
PTG[3]
PG2
FP26
PTG[2]
PG1
FP25
PTG[1]
PG0
FP24
PTG[0]
H
PH7
FP39
PTH[7]
PH6
FP38
PTH[6]
PH5
FP37
PTH[5]
PH4
FP36
PTH[4]
PH3
FP35
PTH[3]
PH2
FP34
PTH[2]
PH1
FP33
PTH[1]
PH0
J
FP32
Description
LCD FP31 signal
Routing Register
Pin
Function
after Reset
GPIO
I/O General-purpose
O
LCD FP30 signal
I/O General-purpose
O
LCD FP29 signal
I/O General-purpose
O
LCD FP28 signal
I/O General-purpose
O
LCD FP27 signal
I/O General-purpose
O
LCD FP26 signal
I/O General-purpose
O
LCD FP25 signal
I/O General-purpose
O
LCD FP24 signal
I/O General-purpose
O
LCD FP39 signal
GPIO
I/O General-purpose
O
LCD FP38 signal
I/O General-purpose
O
LCD FP37 signal
I/O General-purpose
O
LCD FP36 signal
I/O General-purpose
O
LCD FP35 signal
I/O General-purpose
O
LCD FP34 signal
I/O General-purpose
O
LCD FP33 signal
I/O General-purpose
O
LCD FP32 signal
PTH[0]
I/O General-purpose
PJ3
PTJ[3]
I/O General-purpose
PJ2
PTJ[2]
I/O General-purpose
PJ1
PTJ[1]
I/O General-purpose
PJ0
PTJ[0]
I/O General-purpose
GPIO
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
77
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
P
PP7
(TXD1)
O
TXD of SCI1
PWM7
O
PWM channel 7
PP[7]
I/O General-purpose
PWM6
O
PP[6]
I/O General-purpose
PP6
PP5
Description
Pin
Function
after Reset
SCI1RR
GPIO
PWM channel 6
(RXD1)
O
RXD of SCI1
PWM5
O
PWM channel 5
PP[5]
I/O General-purpose
PP4
PWM4
O
PP[4]
I/O General-purpose
PP3
PWM3
O
PP[3]
I/O General-purpose
PP2
PWM2
O
PP[2]
I/O General-purpose
PP1
PWM1
O
PP[1]
I/O General-purpose
PWM0
O
PP[0]
I/O General-purpose
PP0
Routing Register
SCI1RR
PWM channel 4
PWM channel 3
PWM channel 2
PWM channel 1
PWM channel 0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
78
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
S
PS7
IRQ
O
LPDC0
TXD0
PTS[7]/KWS[7]
PS6
PTS[4]/KWS[4]
SS0
SCK0
S0L0RR2-0
I/O General-purpose; with interrupt and wakeup
SDA of IIC0
I/O TX of MSCAN0
C0RR
I/O General-purpose; with interrupt and wakeup
SCL of IIC0
I/O RX of MSCAN0
C0RR
I/O General-purpose; with interrupt and wakeup
I/O General-purpose; with interrupt and wakeup
I/O SPI0 serial clock
PTS[2]/KWS[2]
MOSI0
I/O General-purpose; with interrupt and wakeup
I/O SPI0 master out/slave in
PTS[1]/KWS[1]
PS0
XIRQ interrupt input(3)
I/O SPI0 slave select
PTS[3]/KWS[3]
PS1
I/O General-purpose; with interrupt and wakeup
O
(RXCAN)
PS2
S0L0RR2-0
O
SCL0
PS3
I/O TXD of SCI0
I/O RXD of SCI0
(TXCAN0)
PS4
S0L0RR2-0
RXD0
PTS[5]/KWS[5]
Pin
Function
after Reset
GPIO
I/O LINPHY0 TXD direct control by register bit
LP0DR[LP0DR1]
O
SDA0
Routing Register
IRQ interrupt input
XIRQ
PTS[6]/KWS[6]
PS5
Description
MISO0
I/O General-purpose; with interrupt and wakeup
I/O SPI0 master in/slave out
PTS[0]/KWS[0]
I/O General-purpose; with interrupt and wakeup
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
79
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
T
PT7
IOC1_7
O
PTT[7]/KWT[7]
PT6
IOC1_6
IOC1_5
IOC1_4
IOC1_3
I/O General-purpose; with interrupt and wakeup
DBG profiling data output
I/O General-purpose; with interrupt and wakeup
I/O TIM1 channel 3
PDOCLK
PTT[3]/KWT[3]
IOC1_2
O
DBG profiling clock
I/O General-purpose; with interrupt and wakeup
I/O TIM1 channel 2
DBGEEV
PTT[2]/KWT[2]
PT0
I/O General-purpose; with interrupt and wakeup
O
PTT[4]/KWT[4]
PT1
Free running clock output
I/O TIM1 channel 4
PDO
PT2
GPIO
I/O TIM1 channel 5
PTT[5]/KWT[5]
PT3
TIM1 channel 7
Pin
Function
after Reset
I/O General-purpose; with interrupt and wakeup
O
PTT[6]/KWT[6]
PT4
Routing Register
I/O TIM1 channel 6
ECLK
PT5
Description
IOC1_1
I
DBG external event input
I/O General-purpose; with interrupt and wakeup
I/O TIM1 channel 1
RTC_CAL
I/O RTC CALCLK output or external 1HZ input
PTT[1]/KWT[1]
I/O General-purpose; with interrupt and wakeup
(IOC1_0)
I/O TIM1 channel 0
API_EXTCLK
O
PTT[0]/KWT[0]
I/O General-purpose; with interrupt and wakeup
T1IC0RR1-0
API clock output
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
80
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
I/O
PAD7
AN0_7
I
PTADL[7]/
KWADL[7]
PAD6
AN0_6
PAD5
AN0_5
PAD4
AD
AN0_4
PAD3
AN0_3
PAD2
AN0_2
PAD1
AN0_1
PAD0
AN0_0
ADC0 analog input 3
GPIO
ADC0 analog input 2
ADC0 analog input 1
I/O General-purpose; with interrupt and wakeup
I
PTADL[0]/
KWADL[0]
ADC0 analog input 4
I/O General-purpose; with interrupt and wakeup
I
PTADL[1]/
KWADL[1]
ADC0 analog input 5
I/O General-purpose; with interrupt and wakeup
I
PTADL[2]/
KWADL[2]
ADC0 analog input 6
I/O General-purpose; with interrupt and wakeup
I
PTADL[3]/
KWADL[3]
ADC0 analog input 7
I/O General-purpose; with interrupt and wakeup
I
PTADL[4]/
KWADL[4]
Pin
Function
after Reset
I/O General-purpose; with interrupt and wakeup
I
PTADL[5]/
KWADL[5]
Routing Register
I/O General-purpose; with interrupt and wakeup
I
PTADL[6]/
KWADL[6]
Description
ADC0 analog input 0
I/O General-purpose; with interrupt and wakeup
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
81
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Port
Pin Name
Pin Function
& Priority(1)
U
PU[7]
M1SINP
PU[6]
PU[5]
PU[4]
PU[3]
PU[2]
PU[1]
PU[0]
I/O
Description
I/O SSD1 Sine+ Node
M1C1P
O
PTU[7]
I/O General purpose
M1SINM
I/O SSD1 Sine- Node
M1C1M
O
I/O TIM0 channel 3
I/O General purpose
I/O SSD1 Cosine+ Node
M1C0P
O
PTU[5]
I/O General purpose
Motor control output for motor 1
I/O SSD1 Cosine- Node
M1C0M
O
IOC0_2
I/O TIM0 channel2
Motor control output for motor 1
PTU[4]
I/O General purpose
M0SINP
I/O SSD0 Sine+ Node
M0C1P
O
PTU[3]
I/O General purpose
M0SINM
I/O SSD0 Sine- Node
M0C1M
O
IOC0_1
I/O TIM0 channel 1
PTU[2]
I/O General purpose
M0COSP
Motor control output for motor 0
Motor control output for motor 0
I/O SSD0 Cosine+ Node
M0C0P
O
PTU[1]
I/O General purpose
M0COSM
GPIO
Motor control output for motor 1
PTU[6]
M1COSM
Pin
Function
after Reset
Motor control output for motor 1
IOC0_3
M1COSP
Routing Register
Motor control output for motor 0
I/O SSD0 Cosine- Node
M0C0M
O
IOC0_0
I/O TIM0 channel 0
Motor control output for motor 0
PTU[0]
I/O General purpose
1. Signals in parenthesis denote alternative module routing pins
2. Function active when RESET asserted.
3. The interrupt is enabled by clearing the X mask bit in the CPU CCR. The pin is forced to input upon first clearing of the X bit
and is held in this state until reset. A stop or wait recovery with the X bit set (refer to S12ZCPU reference manual) is not
available.
2.3
Memory Map and Register Definition
This section provides a detailed description of all port integration module registers.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
82
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.1
Register Map
Global
Address
Register
Name
0x0200
MODRR0
0x0201
MODRR1
0x0202
MODRR2
0x0203
MODRR3
0x0204–
0x0207
Reserved
0x0208
ECLKCTL
0x0209
IRQCR
0x020A
PIMMISC
0x020B–
0x020D
Reserved
0x020E
0x020F
Reserved
R
Reserved
0x0220
PTA
0x0221
PTB
0x0222
PTIA
5
4
0
0
0
0
R
0
0
0
0
0
0
SCI1RR
IIC0RR
0
0
0
0
0
0
0
0
0
0
0
W
R
W
R
3
C0RR
R
2
1
Bit 0
0
0
0
PWM6RR PWM4RR PWM2RR PWM0RR
0
0
T1IC0RR1 T1IC0RR0
S0L0RR2
S0L0RR1
S0L0RR0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
W
R
W
R
W
R
NECLK
IRQE
IRQEN
0
0
0
0
0
0
0
CALCLKE
N
0
0
0
0
0
0
0
0
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
0
0
0
0
0
0
0
0
PTA7
PTA6
PTA5
PTA4
PTA3
PTA2
PTA1
PTA0
0
0
0
0
PTB3
PTB2
PTB1
PTB0
PTIA7
PTIA6
PTIA5
PTIA4
PTIA3
PTIA2
PTIA1
PTIA0
W
R
W
R
R
W
0x0210–
0x021F
6
W
W
Reserved
Bit 7
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
83
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x0223
PTIB
0x0224
DDRA
0x0225
DDRB
0x0226
PERA
0x0227
PERB
0x0228
PPSA
0x0229
PPSB
0x022A–
0x023D
Reserved
0x023E
WOMA
0x023F
Reserved
0x0240
PTC
0x0241
PTD
0x0242
PTIC
0x0243
PTID
0x0244
DDRC
0x0245
DDRD
R
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
PTIB3
PTIB2
PTIB1
PTIB0
DDRA7
DDRA6
DDRA5
DDRA4
DDRA3
DDRA2
DDRA1
DDRA0
0
0
0
0
DDRB3
DDRB2
DDRB1
DDRB0
PERA7
PERA6
PERA5
PERA4
PERA3
PERA2
PERA1
PERA0
0
0
0
0
PERB3
PERB2
PERB1
PERB0
PPSA7
PPSA6
PPSA5
PPSA4
PPSA3
PPSA2
PPSA1
PPSA0
0
0
0
0
PPSB3
PPSB2
PPSB1
PPSB0
0
0
0
0
0
0
0
0
0
0
0
0
WOMA3
WOMA2
0
0
0
0
0
0
0
0
0
0
PTC7
PTC6
PTC5
PTC4
PTC3
PTC2
PTC1
PTC0
PTD7
PTD6
PTD5
PTD4
PTD3
PTD2
PTD1
PTD0
PTIC7
PTIC6
PTIC5
PTIC4
PTIC3
PTIC2
PTIC1
PTIC0
PTID7
PTID6
PTID5
PTID4
PTID3
PTID2
PTID1
PTID0
DDRC7
DDRC6
DDRC5
DDRC4
DDRC3
DDRC2
DDRC1
DDRC0
DDRD7
DDRD6
DDRD5
DDRD4
DDRD3
DDRD2
DDRD1
DDRD0
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
84
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x0246
PERC
0x0247
PERD
0x0248
PPSC
0x0249
PPSD
0x024A–
0x025F
Reserved
0x0260
PTE
0x0261
PTF
0x0262
PTIE
0x0263
PTIF
0x0264
DDRE
0x0265
DDRF
0x0266
PERE
0x0267
PERF
0x0268
PPSE
0x0269
PPSF
0x026A–
0x027F
Reserved
R
W
R
W
R
W
R
W
R
Bit 7
6
5
4
3
2
1
Bit 0
PERC7
PERC6
PERC5
PERC4
PERC3
PERC2
PERC1
PERC0
PERD7
PERD6
PERD5
PERD4
PERD3
PERD2
PERD1
PERD0
PPSC7
PPSC6
PPSC5
PPSC4
PPSC3
PPSC2
PPSC1
PPSC0
PPSD7
PPSD6
PPSD5
PPSD4
PPSD3
PPSD2
PPSD1
PPSD0
0
0
0
0
0
0
0
0
0
0
0
0
PTE3
PTE2
PTE1
PTE0
PTF7
PTF6
PTF5
PTF4
PTF3
PTF2
PTF1
PTF0
0
0
0
0
PTIE3
PTIE2
PTIE1
PTIE0
PTIF7
PTIF6
PTIF5
PTIF4
PTIF3
PTIF2
PTIF1
PTIF0
0
0
0
0
DDRE3
DDRE2
DDRE1
DDRE0
DDRF7
DDRF6
DDRF5
DDRF4
DDRF3
DDRF2
DDRF1
DDRF0
0
0
0
0
PERE3
PERE2
PERE1
PERE0
PERF7
PERF6
PERF5
PERF4
PERF3
PERF2
PERF1
PERF0
0
0
0
0
PPSE3
PPSE2
PPSE1
PPSE0
PPSF7
PPSF6
PPSF5
PPSF4
PPSF3
PPSF2
PPSF1
PPSF0
0
0
0
0
0
0
0
0
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
85
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x0280
Reserved
0x0281
PTADL
0x0282
Reserved
0x0283
PTIADL
0x0284
Reserved
0x0285
DDRADL
0x0286
Reserved
0x0287
PERADL
0x0288
Reserved
0x0289
PPSADL
0x028A–
0x028B
Reserved
0x028C
Reserved
0x028D
PIEADL
0x028E
Reserved
0x028F
PIFADL
0x0290–
0x0298
Reserved
R
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
PTADL7
PTADL6
PTADL5
PTADL4
PTADL3
PTADL2
PTADL1
PTADL0
0
0
0
0
0
0
0
0
PTIADL6
PTIADL5
PTIADL4
PTIADL3
PTIADL2
PTIADL1
PTIADL0
0
0
0
0
0
0
0
W
R
W
R
W
R PTIADL7
W
R
0
W
R
W
R
DDRADL7 DDRADL6 DDRADL5 DDRADL4 DDRADL3 DDRADL2 DDRADL1 DDRADL0
0
0
0
0
0
0
0
0
W
R
W
R
PERADL7 PERADL6 PERADL5 PERADL4 PERADL3 PERADL2 PERADL1 PERADL0
0
0
0
0
0
0
0
0
W
R
W
R
PPSADL7 PPSADL6 PPSADL5 PPSADL4 PPSADL3 PPSADL2 PPSADL1 PPSADL0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
PIEADL7
PIEADL6
PIEADL5
PIEADL4
PIEADL3
PIEADL2
PIEADL1
PIEADL0
0
0
0
0
0
0
0
0
PIFADL7
PIFADL6
PIFADL5
PIFADL4
PIFADL3
PIFADL2
PIFADL1
PIFADL0
0
0
0
0
0
0
0
0
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
86
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x0299
DIENADL
0x029A–
0x02BF
Reserved
0x02C0
PTT
Bit 7
R
W
R
0x02C2
PTIT
DDRT
R
PERT
R
R
R
W
0x02C4
PPST
R
W
0x02C5
Reserved
0x02C6
PIET
0x02C7
PIFT
0x02C8–
0x02CF
Reserved
0x02D0
PTS
0x02D1
PTIS
0x02D2
DDRS
0x02D3
PERS
0x02D4
PPSS
4
3
2
1
Bit 0
DIENADL7 DIENADL6 DIENADL5 DIENADL4 DIENADL3 DIENADL2 DIENADL1 DIENADL0
0
0
0
0
0
0
0
0
PTT7
PTT6
PTT5
PTT4
PTT3
PTT2
PTT1
PTT0
PTIT7
PTIT6
PTIT5
PTIT4
PTIT3
PTIT2
PTIT1
PTIT0
DDRT7
DDRT6
DDRT5
DDRT4
DDRT3
DDRT2
DDRT1
DDRT0
PERT7
PERT6
PERT5
PERT4
PERT3
PERT2
PERT1
PERT0
PPST7
PPST6
PPST5
PPST4
PPST3
PPST2
PPST1
PPST0
0
0
0
0
0
0
0
0
PIET7
PIET6
PIET5
PIET4
PIET3
PIET2
PIET1
PIET0
PIFT7
PIFT6
PIFT5
PIFT4
PIFT3
PIFT2
PIFT1
PIFT0
0
0
0
0
0
0
0
0
PTS7
PTS6
PTS5
PTS4
PTS3
PTS2
PTS1
PTS0
PTIS7
PTIS6
PTIS5
PTIS4
PTIS3
PTIS2
PTIS1
PTIS0
DDRS7
DDRS6
DDRS5
DDRS4
DDRS3
DDRS2
DDRS1
DDRS0
PERS7
PERS6
PERS5
PERS4
PERS3
PERS2
PERS1
PERS0
PPSS7
PPSS6
PPSS5
PPSS4
PPSS3
PPSS2
PPSS1
PPSS0
W
W
0x02C3
5
W
W
0x02C1
6
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
87
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x02D5
Reserved
0x02D6
PIES
0x02D7
PIFS
0x02D8–
0x02DE
Reserved
0x02DF
WOMS
0x02E0–
0x02EF
Reserved
0x02F0
PTP
0x02F1
PTIP
0x02F2
DDRP
0x02F3
PERP
0x02F4
PPSP
0x02F5–
0x02FF
Reserved
0x0300
PTH
0x0301
PTIH
0x0302
DDRH
0x0303
PERH
R
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
PIES7
PIES6
PIES5
PIES4
PIES3
PIES2
PIES1
PIES0
PIFS7
PIFS6
PIFS5
PIFS4
PIFS3
PIFS2
PIFS1
PIFS0
0
0
0
0
0
0
0
0
WOMS7
WOMS6
WOMS5
WOMS4
WOMS3
WOMS2
WOMS1
WOMS0
0
0
0
0
0
0
0
0
PTP7
PTP6
PTP5
PTP4
PTP3
PTP2
PTP1
PTP0
PTIP7
PTIP6
PTIP5
PTIP4
PTIP3
PTIP2
PTIP1
PTIP0
DDRP7
DDRP6
DDRP5
DDRP4
DDRP3
DDRP2
DDRP1
DDRP0
PERP7
PERP6
PERP5
PERP4
PERP3
PERP2
PERP1
PERP0
PPSP7
PPSP6
PPSP5
PPSP4
PPSP3
PPSP2
PPSP1
PPSP0
0
0
0
0
0
0
0
0
PTH7
PTH6
PTH5
PTH4
PTH3
PTH2
PTH1
PTH0
PTIH7
PTIH6
PTIH5
PTIH4
PTIH3
PTIH2
PTIH1
PTIH0
DDRH7
DDRH6
DDRH5
DDRH4
DDRH3
DDRH2
DDRH1
DDRH0
PERH7
PERH6
PERH5
PERH4
PERH3
PERH2
PERH1
PERH0
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
88
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x0304
PPSH
0x0305–
0x030F
Reserved
0x0310
PTJ
0x0311
PTIJ
0x0312
DDRJ
0x0313
PERJ
0x0314
PPSJ
0x0315–
0x031F
Reserved
0x0320
PTG
0x0321
PTIG
0x0322
DDRG
0x0323
PERG
0x0324
PPSG
0x0325–
0x032F
Reserved
0x0350
PTU
0x0351
PTIU
R
W
R
Bit 7
6
5
4
3
2
1
Bit 0
PPSH7
PPSH6
PPSH5
PPSH4
PPSH3
PPSH2
PPSH1
PPSH0
0
0
0
0
0
0
0
0
0
0
0
0
PTJ3
PTJ2
PTJ1
PTJ0
0
0
0
0
PTIJ3
PTIJ2
PTIJ1
PTIJ0
0
0
0
0
DDRJ3
DDRJ2
DDRJ1
DDRJ0
0
0
0
0
PERJ3
PERJ2
PERJ1
PERJ0
0
0
0
0
PPSJ3
PPSJ2
PPSJ1
PPSJ0
0
0
0
0
0
0
0
0
PTG7
PTG6
PTG5
PTG4
PTG3
PTG2
PTG1
PTG0
PTIG7
PTIG6
PTIG5
PTIG4
PTIG3
PTIG2
PTIG1
PTIG0
DDRG7
DDRG6
DDRG5
DDRG4
DDRG3
DDRG2
DDRG1
DDRG0
PERG7
PERG6
PERG5
PERG4
PERG3
PERG2
PERG1
PERG0
PPSG7
PPSG6
PPSG5
PPSG4
PPSG3
PPSG2
PPSG1
PPSG0
0
0
0
0
0
0
0
0
PTU7
PTU6
PTU5
PTU4
PTU3
PTU2
PTU1
PTU0
PTIU7
PTIU6
PTIU5
PTIU4
PTIU3
PTIU2
PTIU1
PTIU0
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
89
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Global
Address
Register
Name
0x0352
DDRU
0x0353
PERU
0x0354
PPSU
0x0355–
0x035D
Reserved
0x035E
SRRU
0x035F
Reserved
0x0360–
0x037F
Reserved
2.3.2
R
W
R
W
R
W
R
Bit 7
6
5
4
3
2
1
Bit 0
DDRU7
DDRU6
DDRU5
DDRU4
DDRU3
DDRU2
DDRU1
DDRU0
PERU7
PERU6
PERU5
PERU4
PERU3
PERU2
PERU1
PERU0
PPSU7
PPSU6
PPSU5
PPSU4
PPSU3
PPSU2
PPSU1
PPSU0
0
0
0
0
0
0
0
0
SRRU7
SRRU6
SRRU5
SRRU4
SRRU3
SRRU2
SRRU1
SRRU0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
R
W
R
W
R
W
Register Descriptions
This section describes the details of all configuration registers.
• If not stated differently, writing to reserved bits has no effect and read returns zero.
• All register read accesses are synchronous to internal clocks.
• All registers can be written at any time, however a specific configuration might not become active.
E.g. a pullup device does not become active while the port is used as a push-pull output.
• General-purpose data output availability depends on prioritization; input data registers always
reflect the pin status independent of the use.
• Pull-device availability, pull-device polarity, wired-or mode, key-wake up functionality are
independent of the prioritization unless noted differently.
• The description of registers PTx, PTIx, DDRx, DIENx, PERx, PPSx, SRRx, WOMx, PIEx and
PIFx generically assumes a fully implemented 8-bit register. For availability of individual bits refer
to Section 2.3.1, “Register Map“”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
90
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.1
Module Routing Register 0 (MODRR0)
Access: User read/write(1)
Address 0x0200
R
7
6
5
4
0
0
0
0
3
2
1
0
0
0
0
0
0
0
C0RR
W
Reset
—
—
—
—
CAN0
0
0
0
0
0
Figure 2-1. Module Routing Register 0 (MODRR0)
1. Read: Anytime
Write: Once in normal, anytime in special mode
.
Table 2-2. Module Routing Register0 Field Descriptions
Field
3
C0RR
Description
Module Routing Register — CAN0 routing
1 TXCAN0 on PS5 and RXCAN0 on PS4
0 TXCAN0 on PC1 and RXCAN0 on PC0
2.3.2.2
Module Routing Register 1 (MODRR1)
Access: User read/write(1)
Address 0x0201
R
7
6
5
4
0
0
0
0
3
2
1
0
PWM6RR
PWM4RR
PWM2RR
PWM0RR
W
Reset
—
—
—
—
PWM6
PWM4
PWM2
PWM0
0
0
0
0
0
0
0
0
Figure 2-2. Module Routing Register 1 (MODRR1)
1. Read: Anytime
Write: Once in normal, anytime in special mode
Table 2-3. MODRR1 Routing Register Field Descriptions
Field
Description
3
Module Routing Register — PWM6 routing
PWM6RR
1 PWM6 to PA7
0 PWM6 to PP6
2
Module Routing Register — PWM4 routing
PWM4RR
1 PWM4 to PA6
0 PWM4 to PP4
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
91
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Table 2-3. MODRR1 Routing Register Field Descriptions
Field
Description
1
Module Routing Register — PWM2 routing
PWM2RR
1 PWM2 to PA5
0 PWM2 to PP2
0
Module Routing Register — PWM0 routing
PWM0RR
1 PWM0 to PA4
0 PWM0 to PP0
2.3.2.3
Module Routing Register 2 (MODRR2)
Access: User read/write(1)
Address 0x0202
R
7
6
0
0
5
4
SCI1RR
IIC0RR
SCI1
IIC0
0
0
3
2
0
0
1
0
T1IC0RR1
T1IC0RR0
W
Reset
0
0
TIM1 IC0
0
0
0
0
Figure 2-3. Module Routing Register 2 (MODRR2)
1. Read: Anytime
Write: Once in normal, anytime in special mode
Table 2-4. MODRR2 Routing Register Field Descriptions
Field
5
SCI1RR
Description
Module Routing Register — SCI1 routing
1 TXD1 on PP7; RXD1 on PP5
0 TXD1 on PC7; RXD1 on PC6
4
IIC0RR
Module Routing Register — IIC0 routing
1 SCL0 on PA2; SDA0 on PA3
0 SCL0 on PS4; SDA0 on PS5
1-0
Module Routing Register — TIM1 IC0 routing
T1IC0RR1-0
11 TIM1 input capture channel 0 is connected to RXD1
10 TIM1 input capture channel 0 is connected to RXD0
01 TIM1 input capture channel 0 is connected to RTC’s CALCLK
00 TIM1 input capture channel 0 is connected to PT0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
92
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.4
Module Routing Register 3 (MODRR3)1
Access: User read/write(1)
Address 0x0200
R
7
6
5
4
3
0
0
0
0
0
2
1
0
S0L0RR2-0
W
Reset
—
—
—
—
—
SCI0-LINPHY0 (see Figure 2-5)
0
0
0
0
0
0
0
0
Figure 2-4. Module Routing Register 3 (MODRR3)
1. Read: Anytime
Write: Once in normal, anytime in special mode
Field
Description
2-0
Module Routing Register — SCI0-LINPHY0 routing
S0L0RR2-0
Selection of SCI0-LINPHY0 interface routing options to support probing and conformance testing. Refer to
Figure 2-5 for an illustration and Table 2-5 for preferred settings. SCI0 must be enabled for TXD0 routing to take
effect on pins. LINPHY0 must be enabled for LPRXD0 and LPDC0 routings to take effect on pins.
1. This register is only avaiable on ZVHL
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
93
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
S0L0RR0
S0L0RR1
S0L0RR2
0
1
PS7 / TXD0 / LPDC0
PC3 / LPTXD0
1
TXD0
0
0
LPTXD0
1
LPDR1
LINPHY0
SCI0
0
RXD0
LIN
LPRXD0
1
0
1
PC2 / LPRXD0
PS6 / RXD0
Figure 2-5. SCI0-to-LINPHY0 Routing Options Illustration
Table 2-5. Preferred Interface Configurations
S0L0RR[2:0]
000
Signal Routing
TXD0 -> LPTXD0
LPRXD0 -> RXD0
Description
Default setting:
SCI0 connects to LINPHY0, interface internal only
001
LPDR1 -> LPTXD0
LPRXD -> RXD0
Direct control setting:
LP0DR[LPDR1] register bit controls LPTXD0, interface internal
only
100
TXD0 -> LPTXD0, PS7
LPRXD0 -> RXD0, PC2
Probe setting:
SCI0 connects to LINPHY0, interface accessible on 2 external pins
110
TXD0 -> PS7
PC3 -> LPTXD0
PS6 -> RXD0
LPRXD0 -> PC2
Conformance test setting:
Interface opened and all 4 signals routed externally
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
94
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
NOTE
For standalone usage of SCI0 on external pins set
[S0L0RR2:S0L0RR0]=0b110 and disable the LINPHY0 (LPCR[LPE]=0).
This releases PC3 and PC2 to other associated functions and maintains
TXD0 and RXD0 signals on PS7 and PS6, respectively, if no other function
with higher priority takes precedence.
2.3.2.5
ECLK Control Register (ECLKCTL)
Access: User read/write(1)
Address 0x0208
7
R
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
NECLK
W
Reset:
1
Figure 2-6. ECLK Control Register (ECLKCTL)
1. Read: Anytime
Write: Anytime
Table 2-6. ECLKCTL Register Field Descriptions
Field
7
NECLK
Description
No ECLK — Disable ECLK output
This bit controls the availability of a free-running clock on the ECLK pin. This clock has a fixed rate equivalent to the
internal bus clock.
1 ECLK disabled
0 ECLK enabled
2.3.2.6
IRQ Control Register (IRQCR)
Access: User read/write(1)
Address 0x0209
7
6
IRQE
IRQEN
0
0
R
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
Figure 2-7. IRQ Control Register (IRQCR)
1. Read: Anytime
Write:
IRQE: Once in normal mode, anytime in special mode
IRQEN: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
95
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Table 2-7. IRQCR Register Field Descriptions
Field
7
IRQE
Description
IRQ select edge sensitive only —
1 IRQ pin configured to respond only to falling edges. Falling edges on the IRQ pin are detected anytime when
IRQE=1 and will be cleared only upon a reset or the servicing of the IRQ interrupt.
0 IRQ configured for low level recognition
6
IRQEN
IRQ enable —
1 IRQ pin is connected to interrupt logic
0 IRQ pin is disconnected from interrupt logic
2.3.2.7
PIM Miscellaneous Register (PIMMISC)
Access: User read/write(1)
Address 0x020A
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
CALCLKEN
W
Reset
0
0
0
0
0
0
0
0
Figure 2-8. PIM Miscellaneous Register (PIMMISC)
1. Read: Anytime
Write:Anytime
Table 2-8. PIM Miscellaneous Register Field Descriptions
Field
Description
RTC_CAL output Enable — Activate the RTC CALCLK output on PT1
0
CALCLKE
N
1 CALCLK output on PT1 enabled
0 CALCLK output on PT1 disabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
96
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.8
Reserved Register
Access: User read/write(1)
Address 0x020E
R
7
6
5
4
3
2
1
0
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
x
x
x
x
x
x
x
x
W
Reset
Figure 2-9. Reserved Register
1. Read: Anytime
Write: Only in special mode
These reserved registers are designed for factory test purposes only and are
not intended for general user access. Writing to these registers when in
special modes can alter the modules functionality
Access: User read/write(1)
Address 0x020F
7
R
Reserved
6
5
4
3
2
1
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
x
x
x
x
x
x
0
Reserved
W
Reset
x
x
Figure 2-10. Reserved Register
1. Read: Anytime
Write: Only in special mode
These reserved registers are designed for factory test purposes only and are
not intended for general user access. Writing to these registers when in
special modes can alter the modules functionality
2.3.2.9
Port C Polarity Select Register
Access: User read/write(1)
Address 0x0248 PPSC
7
6
5
4
3
2
1
0
PPSx7
PPSx6
PPSx5
PPSx4
PPSx3
PPSx2
PPSx1
PPSx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-11. Port C Polarity Select Register
1. Read: Anytime
Write: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
97
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Table 2-9. Port C Polarity Select Register Field Descriptions
Field
7-1
PPSC
Description
Pull C Polarity Select — Configure pull device on input pin
This bits select a pullup or a pulldown device if enabled on the associated port input pin.
1 pulldown device selected
0 pullup device selected
0
PPSC
Port C Pull Polarity Select — Configure pull device on input pin
This bit selects a pullup or a pulldown device if enabled on the associated port input pin.
If MSCAN0 is active and routing to this pin, a pullup device can be activated on the RXCAN0 input; attempting to
select a pulldown disables the pull-device.
1 pulldown device selected
0 pullup device selected
2.3.2.10
Port S Polarity Select Register
Access: User read/write(1)
Address 0x02D4 PPSS
7
6
5
4
3
2
1
0
PPSx7
PPSx6
PPSx5
PPSx4
PPSx3
PPSx2
PPSx1
PPSx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-12. Port S Polarity Select Register
1. Read: Anytime
Write: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
98
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Table 2-10. Port S Polarity Select Register Field Descriptions
Field
7-5
PPSS
Description
Pull S Polarity Select — Configure pull device and pin interrupt edge polarity on input pin
This bits select a pullup or a pulldown device if enabled on the associated port input pin.
1 pulldown device selected; rising edge selected
0 pullup device selected; falling edge selected
4
PPSS
Port S Pull Polarity Select — Configure pull device and pin interrupt edge polarity on input pin
This bit selects a pullup or a pulldown device if enabled on the associated port input pin.
If MSCAN0 is active and routing to this pin, a pullup device can be activated on the RXCAN0 input; attempting to
select a pulldown disables the pull-device.
1 pulldown device selected; rising edge selected
0 pullup device selected; falling edge selected
3-0
PPSS
Port S Pull Polarity Select — Configure pull device and pin interrupt edge polarity on input pin
This bit selects a pullup or a pulldown device if enabled on the associated port input pin.
This bit also selects the polarity of the active interrupt edge.
1 pulldown device selected; rising edge selected
0 pullup device selected; falling edge selected
2.3.2.11
Port Data Register
Access: User read/write(1)
Address 0x0220 PTA
0x0221 PTB
0x0240 PTC
0x0241 PTD
0x0260 PTE
0x0261 PTF
0x0281 PTADL
0x02C0 PTT
0x02D0 PTS
0x02F0 PTP
0x0300 PTH
0x0310 PTJ
0x0320 PTG
0x0350 PTU
7
6
5
4
3
2
1
0
PTx7
PTx6
PTx5
PTx4
PTx3
PTx2
PTx1
PTx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-13. Port Data Register
1. Read: Anytime. The data source is depending on the data direction value.
Write: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
99
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Table 2-11. Port Data Register Field Descriptions
Field
7-0
PTx
Description
Port — General purpose input/output data
This register holds the value driven out to the pin if the pin is used as a general purpose output.
When not used with the alternative function (refer to Table 2-1), these pins can be used as general purpose I/O.
If the associated data direction bits of these pins are set to 1, a read returns the value of the port register, otherwise
the buffered pin input state is read.
2.3.2.12
Port Input Register
Access: User read only(1)
Address 0x0222 PTIA
0x0223 PTIB
0x0242 PTIC
0x0243 PTID
0x0262 PTIE
0x0263 PTIF
0x0283 PTIADL
0x02C1 PTIT
0x02D1 PTIS
0x02F1 PTIP
0x0301 PTIH
0x0311 PTIJ
0x0321 PTIG
0x0351 PTIU
R
7
6
5
4
3
2
1
0
PTIx7
PTIx6
PTIx5
PTIx4
PTIx3
PTIx2
PTIx1
PTIx0
0
0
0
0
0
0
0
0
W
Reset
Figure 2-14. Port Input Register
1. Read: Anytime
Write:Never
Table 2-12. Port Input Register Field Descriptions
Field
7-0
PTIx
Description
Port Input — Data input
A read always returns the buffered input state of the associated pin. It can be used to detect overload or short circuit
conditions on output pins.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
100
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.13
Data Direction Register
Access: User read/write(1)
Address 0x0224 DDRA
0x0225 DDRB
0x0244 DDRC
0x0245 DDRD
0x0264 DDRE
0x0265 DDRF
0x0285 DDRADL
0x02C2 DDRT
0x02D2 DDRS
0x02F2 DDRP
0x0302 DDRH
0x0312 DDRJ
0x0322 DDRG
0x0352 DDRU
7
6
5
4
3
2
1
0
DDRx7
DDRx6
DDRx5
DDRx4
DDRx3
DDRx2
DDRx1
DDRx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-15. Data Direction Register
1. Read: Anytime
Write: Anytime
Table 2-13. Data Direction Register Field Descriptions
Field
7-0
DDRx
Description
Data Direction — Select general-purpose data direction
This bit determines whether the pin is a general-purpose input or output.
1 Associated pin is configured as output
0 Associated pin is configured as input
NOTE
Due to internal synchronization circuits, it can take up to two bus clock
cycles until the correct value is read on port data and port input registers,
when changing the data direction register.
The general-purpose data direction configuration can be overruled by an enabled peripheral function
shared on the same pin (Table 2-22). If more then one peripheral function is available and enabled at the
same time, the highest ranked module according the predefined priority scheme in Table 2-1 will take
precedence on the pin.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
101
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.14
Digital Input Enable Register
Access: User read/write(1)
Address 0x0299 DIENADL
7
6
5
4
3
2
1
0
DIENx7
DIENx6
DIENx5
DIENx4
DIENx3
DIENx2
DIENx1
DIENx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-16. Digital Input Enable Register
1. Read: Anytime
Write: Anytime
Table 2-14. Digital Input Enable Register Field Descriptions
Field
7-0
DIENx
Description
Digital Input Enable — Input buffer control
This bit controls the digital input function. If set to 1 the input buffers are enabled and the pin can be used with the
digital function. If the pin is used with an analog function this bit shall be cleared to avoid shoot-through current.
1 Associated pin is configured as digital input
0 Associated pin digital input is disabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
102
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.15
Pull Device Enable Register
Access: User read/write(1)
Address 0x0226 PERA
0x0227 PERB
0x0246 PERC
0x0247 PERD
0x0266 PERE
0x0267 PERF
0x0287 PERADL
0x02C3 PERT
0x02D3 PERS
0x02F3 PERP
0x0303 PERH
0x0313 PERJ
0x0323 PERG
0x0353 PERU
7
6
5
4
3
2
1
0
PERx7
PERx6
PERx5
PERx4
PERx3
PERx2
PERx1
PERx0
Ports B, E:
0
0
0
0
1
1
1
1
Ports C, P T,
ADL, J, U:
0
0
0
0
0
0
0
0
Others:
1
1
1
1
1
1
1
1
R
W
Reset
Figure 2-17. Pull Device Enable Register
1. Read: Anytime
Write: Anytime
Table 2-15. Pull Device Register Field Descriptions
Field
7-0
PERx
Description
Pull Enable — Activate pull device on input pin
This bit controls whether a pull device on the associated port input or open-drain output pin is active. If a pin is used
as push-pull output this bit has no effect. The polarity is selected by the related polarity select register bit. On opendrain output pins only a pullup device can be enabled.
1 Pull device enabled
0 Pull device disabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
103
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.16
Polarity Select Register
Access: User read/write(1)
Address 0x0228 PPSA
0x0229 PPSB
0x0248 PPSC
0x0249 PPSD
0x0268 PPSE
0x0269 PPSF
0x0289 PPSADL
0x02C4 PPST
0x02D4 PPSS
0x02F4 PPSP
0x0304 PPSH
0x0314 PPSJ
0x0324 PPSG
0x0354 PPSU
7
6
5
4
3
2
1
0
PPSx7
PPSx6
PPSx5
PPSx4
PPSx3
PPSx2
PPSx1
PPSx0
Ports B, E:
0
0
0
0
1
1
1
1
Ports A, D,
F, G, H:
1
1
1
1
1
1
1
1
Others:
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-18. Polarity Select Register
1. Read: Anytime
Write: Anytime
Table 2-16. Polarity Select Register Field Descriptions
Field
7-0
PPSx
Description
Pull Polarity Select — Configure pull device and pin interrupt edge polarity on input pin
This bit selects a pullup or a pulldown device if enabled on the associated port input pin.
If a port has interrupt functionality this bit also selects the polarity of the active edge.
If MSCAN0 is active a pullup device can be activated on the RXCAN0 input; attempting to select a pulldown disables
the pull-device.
1 Pulldown device selected; rising edge selected
0 Pullup device selected; falling edge selected
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
104
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.17
Wired-Or Mode Register
Access: User read/write(1)
Address 0x023E WOMA
0x02DF WOMS
7
6
5
4
3
2
1
0
WOMx7
WOMx6
WOMx5
WOMx4
WOMx3
WOMx2
WOMx1
WOMx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-19. Wired-Or Mode Register
1. Read: Anytime
Write: Anytime
Table 2-17. Wired-Or Mode Register Field Descriptions
Field
7-0
WOMx
Description
Wired-Or Mode — Enable open-drain output
This bit configures the output pin as wired-or. If enabled the output is driven active low only (open-drain) while the
active high drive is turned off. This allows a multipoint connection of several serial modules. These bits have no
influence on pins used as inputs. Enable the IIC0, it will force the corresponding pins to be open drain output.
1 Output buffers operate as open-drain outputs
0 Output buffers operate as push-pull outputs
2.3.2.18
Port Interrupt Enable Register
Read: Anytime
Access: User read/write(1)
Address 0x02C6 PIET
0x02D6 PIES
0x028D PIEADL
7
6
5
4
3
2
1
0
PIEx7
PIEx6
PIEx5
PIEx4
PIEx3
PIEx2
PIEx1
PIEx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-20. Port Interrupt Enable Register
1. Read: Anytime
Write: Anytime
Table 2-18. Port Interrupt Enable Register Field Descriptions
Field
7-0
PIEx
Description
Port Interrupt Enable — Activate pin interrupt
This bit enables or disables the edge sensitive pin interrupt on the associated pin. An interrupt can be generated if
the pin is operating in input or output mode when in use with the general-purpose or related peripheral function.
1 Interrupt is enabled
0 Interrupt is disabled (interrupt flag masked)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
105
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.3.2.19
Port Interrupt Flag Register
Access: User read/write(1)
Address 0x02C7 PIFT
0x02D7 PIFS
0x028F PIFADL
7
6
5
4
3
2
1
0
PIFx7
PIFx6
PIFx5
PIFx4
PIFx3
PIFx2
PIFx1
PIFx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-21. Port Interrupt Flag Register
1. Read: Anytime
Write: Anytime
Table 2-19. Port Interrupt Flag Register Field Descriptions
Field
7-0
PIFx
Description
Port Interrupt Flag — Signal pin event
The flag asserts after a valid active edge was detected on the related pin (see Section 2.4.4, “Pin interrupts and
Wakeup“”). This can be a rising or a falling edge based on the state of the polarity select register.
Writing a logic “1” to the corresponding bit field clears the flag.
1 Active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set)
0 No active edge occurred
2.3.2.20
Port Slew Rate Register
Access: User read/write(1)
Address 0x035E SRRU
7
6
5
4
3
2
1
0
SRRx7
SRRx6
SRRx5
SRRx4
SRRx3
SRRx2
SRRx1
SRRx0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 2-22. Port Slew Rate Register
1. Read: Anytime
Write: Anytime
Table 2-20. Port Interrupt Flag Register Field Descriptions
Field
7-0
SRRx
Description
Port Slew Rate— Slew Rate control(1)
1 Enable the slew rate control and disable the digital input buffer
0 Disable the slew rate control and enable the digital input buffer
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
106
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
1. When change SRRx from non-zero value to zero value or vice versa, It will need to wait about 300 nanoseconds delay
before the slew rate control to be real function as setting. When enter STOP, to save the power, the slew rate control will
be force to off state. After wakeup from STOP, it will also need to wait about 300 nanoseconds before slew rate control
to be function as setting. To enable the TIM0 ICx functions which shared with motor pads, the corresponding SRRx bit
should be set to zero.
2.3.2.21
PIM Reserved Register
Access: User read(1)
Address (any reserved)
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
Figure 2-23. PIM Reserved Register
1. Read: Always reads 0x00
Write: Unimplemented
2.4
Functional Description
2.4.1
General
Each pin except BKGD can act as general-purpose I/O. In addition each pin can act as an output or input
of a peripheral module.
2.4.2
Registers
Table 2-21 lists the configuration registers which are available on each port. These registers except the pin
input registers can be written at any time, however a specific configuration might not become active.
For example selecting a pullup device: This device does not become active while the port is used as a pushpull output.
Table 2-21. Register availability per port(1)
Port
Data
Input
Data
Direction
Pull
Enable
Polarity
Select
WiredOr Mode
Slew
Rate
Enable
Interrupt
Enable
Interrupt
Flag
A
yes
yes
yes
yes
yes
yes(2)
-
-
-
B
yes
yes
yes
yes
yes
-
-
-
-
C
yes
yes
yes
yes
yes
-
-
-
-
D
yes
yes
yes
yes
yes
-
-
-
-
E
yes
yes
yes
yes
yes
-
-
-
-
F
yes
yes
yes
yes
yes
-
-
-
-
J
yes
yes
yes
yes
yes
-
-
-
-
G
yes
yes
yes
yes
yes
-
-
-
-
H
yes
yes
yes
yes
yes
-
-
-
-
P
yes
yes
yes
yes
yes
-
-
-
-
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
107
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Table 2-21. Register availability per port(1)
Port
Data
Input
Data
Direction
Pull
Enable
Polarity
Select
WiredOr Mode
Slew
Rate
Enable
Interrupt
Enable
Interrupt
Flag
S
yes
yes
yes
yes
yes
yes
-
yes
yes
T
yes
yes
yes
yes
yes
-
-
yes
yes
AD
yes
yes
yes
yes
yes
-
-
yes
yes
-
yes
-
-
U
yes
yes
yes
yes
yes
1. Each cell represents one register with individual configuration bits
2. Only PA3/PA2
Table 2-22 shows the effect of enabled peripheral features on I/O state and enabled pull devices.
Table 2-22. Effect of Enabled Features
Enabled
Feature
Related Pin(s)
Effect on
I/O state
Effect on enabled
pull device
CPMU OSC
EXTAL, XTAL
CPMU takes control
Forced off
32K OSC
32K_EXTAL,
32K_XTAL
OSC takes control if CLKSRC Forced off
in Section 18.4.2, “RTC Control
Register 2 (RTCCTL2)“ is set
LCD
FP[39:0], BP[3:0]
LCD takes control
Forced off
TIMx
OCx
Forced output
Forced off
ICx
None (DDR maintains control)
None (PER/PPS maintain control)
SPIx
MISO, MOSI, SCK, SS Controlled input/output
Forced off if output
SCIx
TXD
Forced output
Forced off
RXD
Forced input
None (PER/PPS maintain control)
TXCAN
Forced output
Forced off
RXCAN
Forced input
Pulldown forced off
IICx
SCL, SDA
Controlled input/output
Forced off if output
S12ZDBG
PDO, PDOCLK
Forced output
Forced off
SSGx
SGA, SGT
Forced output
Forced off
PWM channel
PWMx
Forced output
Forced off
MC
MxCxM, MxCxP
Forced output
Forced off
SSDx
MxCOSM, MxCOSP,
MxSINM, MxSINP
Controlled input/output
Forced off if output
API
API_EXTCLK
Forced output
Forced off
ADCx
ANx
None (DDR maintains
control(1))
None (PER/PPS maintain control)
LINPHYx
LPTXD0
Forced input
None (PER/PPS maintain control)
LPRXD0
Forced output
Forced off
CANx
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
108
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
1. To use the digital input function the related bit in Digital Input Enable Register (DIENADx) must be set to logic level
“1”. To use the digital input function the related bit in Slew Rate Register (SRRx) must be set to logic level “0”.
2.4.2.1
Data register (PTx)
This register holds the value driven out to the pin if the pin is used as a general-purpose I/O.
Writing to this register has only an effect on the pin if the pin is used as general-purpose output. When
reading this address, the synchronized state of the pin is returned if the associated data direction register
bits are configured as input.
If the data direction register bits are configured as output, the contents of the data register is returned. This
is independent of any other configuration (Figure 2-24).
2.4.2.2
Input register (PTIx)
This register is read-only and always returns the synchronized state of the pin (Figure 2-24).
2.4.2.3
Data direction register (DDRx)
This register defines whether the pin is used as an general-purpose input or an output.
If a peripheral module controls the pin the contents of the data direction register is ignored (Figure 2-24).
Independent of the pin usage with a peripheral module this register determines the source of data when
reading the associated data register address (Section 2.4.2.1, “Data register (PTx)“”).
NOTE
Due to internal synchronization circuits, it can take up to 2 bus clock cycles
until the correct value is read on port data or port input registers, when
changing the data direction register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
109
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
PTI
0
1
PT
0
PIN
1
DDR
0
1
data out
Module
output enable
module enable
Figure 2-24. Illustration of I/O pin functionality
2.4.2.4
Pull device enable register (PERx)
This register turns on a pullup or pulldown device on the related pins determined by the associated polarity
select register (Section 2.4.2.5, “Polarity select register (PPSx)“”).
The pull device becomes active only if the pin is used as an input or as a wired-or output. Some peripheral
module only allow certain configurations of pull devices to become active. Refer to the respective bit
descriptions.
2.4.2.5
Polarity select register (PPSx)
This register selects either a pullup or pulldown device if enabled.
It becomes only active if the pin is used as an input. A pullup device can be activated if the pin is used as
a wired-or output.
On pins with interrupt functionality this register selects the active edge polarity of the input signal.
2.4.2.6
Wired-or mode register (WOMx)
If the pin is used as an output this register turns off the active-high drive. This allows wired-or type
connections of outputs.
2.4.2.7
Interrupt enable register (PIEx)
If the pin is used as an interrupt input this register serves as a mask to the interrupt flag to enable/disable
the interrupt.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
110
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.4.2.8
Interrupt flag register (PIFx)
If the pin is used as an interrupt input this register holds the interrupt flag after a valid pin event.
2.4.2.9
Digital input enable register (DIENADx)
This register controls the digital input buffer. If DIENADx is set to logic level “1”, then it will enable the
digital input buffer.
2.4.2.10
Slew rate register (SRRx)
This register selects the slew rate function on the motor pad. It also controls the digital input buffer. If
SRRx is set to logic level “1”, then it will disable the digital input buffer.
2.4.2.11
Module routing register (MODRRx)
Routing registers allow software re-configuration of specific peripheral inputs and outputs:
• MODRR0 supports CAN0 rerouting
• MODRR1 supports PWM channel rerouting
• MODRR2 supports TIM1IC0, IIC0 and SCI1 rerouting
• MODRR3 supports LINPHY0 and SCI0 rerouting
2.4.3
Interrupts
This section describes the interrupts generated by the PIM and their individual sources. Vector addresses
and interrupt priorities are defined at MCU level.
Table 2-23. PIM Interrupt Sources
Module Interrupt Sources
2.4.3.1
Local Enable
XIRQ
None
IRQ
IRQCR[IRQEN]
Port S pin interrupt
PIES[PIES7-PIES0]
Port T pin interrupt
PIET[PIET7-PIET0]
Port AD pin interrupt
PIEADL[PIEADL7-PIEADL0]
XIRQ, IRQ Interrupts
The XIRQ pin allows requesting non-maskable interrupts after reset initialization. During reset, the X bit
in the condition code register is set and any interrupts are masked until software enables them.
The IRQ pin allows requesting asynchronous interrupts. The interrupt input is disabled out of reset. To
enable the interrupt the IRQCR[IRQEN] bit must be set and the I bit cleared in the condition code register.
The interrupt can be configured for level-sensitive or falling-edge-sensitive triggering. If IRQCR[IRQEN]
is cleared while an interrupt is pending, the request will deassert.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
111
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
Both interrupts are capable to wake-up the device from stop mode. Means for glitch filtering are not
provided on these pins.
2.4.4
Pin interrupts and Wakeup
Ports S, T and AD offer pin interrupt and key-wakeup capability. The related interrupt enable (PIE) as well
as the sensitivity to rising or falling edges (PPS) can be individually configured on per-pin basis. All
bits/pins in a port share the same interrupt vector. Interrupts can be used with the pins configured as inputs
or outputs.
An interrupt is generated when a bit in the port interrupt flag (PIF) and its corresponding port interrupt
enable (PIE) are both set. The pin interrupt feature is also capable to wake up the CPU when it is in stop
or wait mode(key-wakeup).
A digital filter on each pin prevents short pulses from generating an interrupt. A valid edge on an input is
detected if 4 consecutive samples of a passive level are followed by 4 consecutive samples of an active
level. Else the sampling logic is restarted.
In run and wait mode the filters are continuously clocked by the bus clock. Pulses with a duration of
tPULSE < nP_MASK/fbus are assuredly filtered out while pulses with a duration of tPULSE > nP_PASS/fbus
guarantee a pin interrupt.
In stop mode the filter clock is generated by an RC-oscillator. The minimum pulse length varies over
process conditions, temperature and voltage(Figure 2-25). Pulses with a duration of tPULSE < tP_MASK are
assuredly filtered out while pulses with a duration of tPULSE > tP_PASS guarantee a wakeup event.
Please refer to the appendix table “Pin Interrupt Characteristics” for pulse length limits.
To maximize current saving the RC oscillator is active only if the following condition is true on any
individual pin:
Sample count <= 4 (at active or passive level) and interrupt flag not set (PIF[x]=0).
Glitch, filtered out, no interrupt flag set
Valid pulse, interrupt flag set
uncertain
tP_MASK
tP_PASS
Figure 2-25. Interrupt Glitch Filter (here: active low level selected)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
112
Freescale Semiconductor
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
2.5
2.5.1
Initialization and Application Information
Port Data and Data Direction Register writes
It is not recommended to write PORTx/PTx and DDRx in a word access. When changing the register pins
from inputs to outputs, the data may have extra transitions during the write access. Initialize the port data
register before enabling the outputs.
2.5.2
SCI0,1 Baud Rate Detection
The baud rate for SCI0 and SCI1 is achieved by using a timer channel to measure the data rate on the RXD
pin.
1. Establish the link:
— For SCI0: Set [T1IC0RR1:T1IC0RR0]=0b10 to disconnect IOC0 from TIM1 input capture
channel 0 and reroute the timer input from the RXD0 of SCI0.
— For SCI1: Set [T1IC0RR1:T1IC0RR0]=0b11 to disconnect IOC0 from TIM1 input capture
channel 0 and reroute the timer input from the RXD1 of SCI1.
2. Determine pulse width of incoming data: Configure TIM1 IC0 to measure time between incoming
signal edges.
2.5.3
RTC on chip calibration
The on chip RTC calibration used the TIM1 IC0 and IC1 channel.
1. Establish the link:
— Set the RTC configuration to generate the expect CALCLK frequency
— Set [T1IC0RR1:T1IC0RR0]=0b10 to disconnect IOC0 from TIM1 input capture channel 0 and
reroute the RTC CALCLK to IC0.
— Input a standard clock on RTC_CAL pin
2. Determine pulse width of incoming data: Configure TIM1 IC0 and IC1 to measure time between
incoming signal edges. Need to pay attention to timer overflow also.
3. Compare the data between IC0 and IC1 to get the RTC clock frequency value. Suppose the
RTC_CAL measure value is B, and CALCLK measure value is A. Then the CALCLK frequency
will be between fRTC_CAL * (B-2) / (A+2) and fRTC_CAL * (B+2) / (A-2). Depend on the
calibration, user need to select the RTC_CAL, CALCLK and TIM1 frequency.
2.5.4
RTC off chip calibration
The off chip RTC calibration, user need to set the CALCLKEN bit in the PIMMIC register to enable the
CALCLK out on RTC_CAL pin. Base on the external requirement, user can set the RTCMOD and CALS
bit in RTCCTL3 registers to get the expected CALCLK output on RTC_CAL pin.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
113
Chapter 2 Port Integration Module (S12ZVHYPIMV1)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
114
Freescale Semiconductor
Chapter 3
Memory Mapping Control (S12ZMMCV1)
Table 3-1. Revision History
Revision
Number
Revision Date
V01.00
6 Mar 2012
Added footnotes to Table 3-8
V01.01
5 Apr 2012
Fixed wording
V01.02
16 May 2012
Fixed wording
V01.03
27 Jul 2012
Corrected Table 3-8
V01.04
27 Jul 2012
Added feature tags
V01.05
6 Aug 2012
Fixed wording
V01.06
12 Feb 2013
V01.07
3 May 2013
3.1
Sections
Affected
Figure 3-8
3.3.2.2/3-120
Description of Changes
• Changed “KByte:to “KB”
• Corrected the description of the MMCECH/L register
•
• Fixed typos
• Removed PTU references
Introduction
The S12ZMMC module controls the access to all internal memories and peripherals for the S12ZCPU, and
the S12ZBDC module. It also provides dirct memory access for the ADC module. The S12ZMMC
determines the address mapping of the on-chip resources, regulates access priorities and enforces memory
protection. Figure 3-1 shows a block diagram of the S12ZMMC module.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
115
Chapter 3 Memory Mapping Control (S12ZMMCV1)
3.1.1
Glossary
Table 3-2. Glossary Of Terms
Term
Definition
MCU
Microcontroller Unit
CPU
S12Z Central Processing Unit
BDC
S12Z Background Debug Controller
ADC
Analog-to-Digital Converter
unmapped
address range
Address space that is not assigned to a memory
reserved address
Address space that is reserved for future use cases
range
illegal access
Memory access, that is not supported or prohibited by the S12ZMMC, e.g. a data store to NVM
access violation
Either an illegal access or an uncorrectable ECC error
byte
8-bit data
word
16-bit data
3.1.2
Overview
The S12ZMMC provides access to on-chip memories and peripherals for the S12ZCPU, the S12ZBDC,
and the ADC. It arbitrates memory accesses and determines all of the MCU memory maps. Furthermore,
the S12ZMMC is responsible for selecting the MCUs functional mode.
3.1.3
•
•
•
Features
S12ZMMC mode operation control
Memory mapping for S12ZCPU, S12ZBDC, and ADC
— Maps peripherals and memories into a 16 MByte address space for the S12ZCPU, the
S12ZBDC, and the ADC
— Handles simultaneous accesses to different on-chip resources (NVM, RAM, and peripherals)
Access violation detection and logging
— Triggers S12ZCPU machine exceptions upon detection of illegal memory accesses and
uncorrectable ECC errors
— Logs the state of the S12ZCPU and the cause of the access error
3.1.4
3.1.4.1
Modes of Operation
Chip configuration modes
The S12ZMMC determines the chip configuration mode of the device. It captures the state of the MODC
pin at reset and provides the ability to switch from special-single chip mode to normal single chip-mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
116
Freescale Semiconductor
Chapter 3 Memory Mapping Control (S12ZMMCV1)
3.1.4.2
Power modes
The S12ZMMC module is only active in run and wait mode.There is no bus activity in stop mode.
3.1.5
Block Diagram
e
Run Mode Controller
S12ZCPU
S12ZBDC
ADC
Memory Protection
Register
Block
Crossbar Switch
Program
Flash
EEPROM
RAM
Peripherals
Figure 3-1. S12ZMMC Block Diagram
3.2
External Signal Description
The S12ZMMC uses two external pins to determine the devices operating mode: RESET and MODC
(Table 3-3)
See device overview for the mapping of these signals to device pins.
Table 3-3. External System Pins Associated With S12ZMMC
Pin Name
3.3
3.3.1
Description
RESET
External reset signal. The RESET signal is active low.
MODC
This input is captured in bit MODC of the MODE register when the external RESET pin deasserts.
Memory Map and Register Definition
Memory Map
A summary of the registers associated with the MMC block is shown in Figure 3-2. Detailed descriptions
of the registers and bits are given in the subsections that follow.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
117
Chapter 3 Memory Mapping Control (S12ZMMCV1)
Address
Name
0x0070
MODE
Bit 7
R
W
0x00710x007F
Reserved
0x0080
MMCECH
R
MODC
0
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
R
ITR[3:0]
TGT[3:0]
ACC[3:0]
ERR[3:0]
W
0x0081
MMCECL
R
W
0x0082
MMCCCRH
R
CPUU
0
0
0
0
0
0
0
0
CPUX
0
CPUI
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
0x0083
MMCCCRL
R
W
0x0084
Reserved
R
W
0x0085
MMCPCH
R
CPUPC[23:16]
W
0x0086
MMCPCM
R
CPUPC[15:8]
W
0x0087
MMCPCL
R
CPUPC[7:0]
W
0x00880x00FF
Reserved
R
0
0
0
0
W
= Unimplemented or Reserved
Figure 3-2. S12ZMMC Register Summary
3.3.2
Register Descriptions
This section consists of the S12ZMMC control and status register descriptions in address order.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
118
Freescale Semiconductor
Chapter 3 Memory Mapping Control (S12ZMMCV1)
3.3.2.1
Mode Register (MODE)
Address: 0x0070
7
R
W
Reset
MODC
MODC1
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1. External signal (see Table 3-3).
= Unimplemented or Reserved
Figure 3-3. Mode Register (MODE)
Read: Anytime.
Write: Only if a transition is allowed (see Figure 3-4).
The MODE register determines the operating mode of the MCU.
CAUTION
Table 3-4. MODE Field Descriptions
Field
Description
7
MODC
Mode Select Bit — This bit determines the current operating mode of the MCU. Its reset value is captured from
the MODC pin at the rising edge of the RESET pin. Figure 3-4 illustrates the only valid mode transition from
special single-chip mode to normal single chip mode.
Reset with
MODC pin = 1
Reset with
MODC pin = 0
Normal
Single-Chip
Mode (NS)
Special
Single-Chip
Mode (SS)
write access to
MODE:
1 → MODC bit
Figure 3-4. Mode Transition Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
119
Chapter 3 Memory Mapping Control (S12ZMMCV1)
3.3.2.2
Error Code Register (MMCECH, MMCECL)
Address: 0x0080 (MMCECH)
7
6
R
4
3
2
ITR[3:0]
W
Reset
5
0
1
0
TGT[3:0]
0
0
0
0
0
0
0
6
5
4
3
2
1
0
0
0
Address: 0x0081 (MMCECL)
7
R
ACC[3:0]
W
Reset
0
0
ERR[3:0]
0
0
0
0
Figure 3-5. Error Code Register (MMCEC)
Read: Anytime
Write: Write of 0xFFFF to MMCECH:MMCECL resets both registers to 0x0000
Table 3-5. MMCECH and MMCECL Field Descriptions
Field
Description
7-4 (MMCECH)
ITR[3:0]
Initiator Field — The ITR[3:0] bits capture the initiator which caused the access violation. The initiator is
captured in form of a 4 bit value which is assigned as follows:
0:
none (no error condition detected)
1:
S12ZCPU
2:
reserved
3:
ADC
4-15: reserved
3-0 (MMCECH)
TGT[3:0]
Target Field — The TGT[3:0] bits capture the target of the faulty access. The target is captured in form of a
4 bit value which is assigned as follows:
0:
none
1:
register space
2:
RAM
3:
EEPROM
4:
program flash
5:
IFR
6-15: reserved
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
120
Freescale Semiconductor
Chapter 3 Memory Mapping Control (S12ZMMCV1)
Field
Description
7-4 (MMCECL)
ACC[3:0]
Access Type Field — The ACC[3:0] bits capture the type of memory access, which caused the access
violation. The access type is captured in form of a 4 bit value which is assigned as follows:
0:
none (no error condition detected)
1:
opcode fetch
2:
vector fetch
3:
data load
4:
data store
5-15: reserved
3-0 (MMCECL)
ERR[3:0]
Error Type Field — The EC[3:0] bits capture the type of the access violation. The type is captured in form of
a 4 bit value which is assigned as follows:
0:
none (no error condition detected)
1:
access to an illegal address
2:
uncorrectable ECC error
3-15: reserved
The MMCEC register captures debug information about access violations. It is set to a non-zero value if a
S12ZCPU access violation or an uncorrectable ECC error has occurred. At the same time this register is
set to a non-zero value, access information is captured in the MMCPCn and MMCCCRn registers. The
MMCECn, the MMCPCn and the MMCCCRn registers are not updated if the MMCECn registers contain
a non-zero value. The MMCECn registers are cleared by writing the value 0xFFFF.
3.3.2.3
Captured S12ZCPU Condition Code Register (MMCCCRH, MMCCCRL)
Address: 0x0082 (MMCCCRH)
R
7
6
5
4
3
2
1
0
CPUU
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
Address: 0x0083 (MMCCCRL)
R
7
6
5
4
3
2
1
0
0
CPUX
0
CPUI
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
Figure 3-6. Captured S12ZCPU Condition Code Register (MMCCCRH, MMCCCRL)
Read: Anytime
Write: Never
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
121
Chapter 3 Memory Mapping Control (S12ZMMCV1)
Table 3-6. MMCCCRH and MMCCCRL Field Descriptions
Field
Description
7 (MMCCCRH)
CPUU
S12ZCPU User State Flag — This bit shows the state of the user/supervisor mode bit in the S12ZCPU’s CCR
at the time the access violation has occurred. The S12ZCPU user state flag is read-only; it will be automatically
updated when the next error condition is flagged through the MMCEC register. This bit is undefined if the error
code registers (MMCECn) are cleared.
6 (MMCCCRL)
CPUX
S12ZCPU X-Interrupt Mask— This bit shows the state of the X-interrupt mask in the S12ZCPU’s CCR at the
time the access violation has occurred. The S12ZCPU X-interrupt mask is read-only; it will be automatically
updated when the next error condition is flagged through the MMCEC register. This bit is undefined if the error
code registers (MMCECn) are cleared.
4 (MMCCCRL)
CPUI
S12ZCPU I-Interrupt Mask— This bit shows the state of the I-interrupt mask in the CPU’s CCR at the time the
access violation has occurred. The S12ZCPU I-interrupt mask is read-only; it will be automatically updated
when the next error condition is flagged through the MMCEC register. This bit is undefined if the error code
registers (MMCECn) are cleared.
3.3.2.4
Captured S12ZCPU Program Counter (MMCPCH, MMCPCM, MMCPCL)
Address: 0x0085 (MMCPCH)
7
6
5
R
4
3
2
1
0
CPUPC[23:16]
W
Reset
0
0
0
0
0
0
0
0
6
5
4
3
2
1
0
0
0
0
0
3
2
1
0
0
0
0
0
Address: 0x0086 (MMCPCM)
7
R
CPUPC[15:8]
W
Reset
0
0
0
0
6
5
4
Address: 0x0087 (MMCPCL)
7
R
CPUPC[7:0]
W
Reset
0
0
0
0
Figure 3-7. Captured S12ZCPU Program Counter (MMCPCH, MMCPCM, MMCPCL)
Read: Anytime
Write: Never
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
122
Freescale Semiconductor
Chapter 3 Memory Mapping Control (S12ZMMCV1)
Table 3-7. MMCPCH, MMCPCM, and MMCPCL Field Descriptions
Field
Description
7–0 (MMCPCH)
7–0 (MMCPCM)
7–0 (MMCPCL)
CPUPC[23:0]
S12ZCPU Program Counter Value— The CPUPC[23:0] stores the CPU’s program counter value at the time
the access violation occurred. CPUPC[23:0] always points to the instruction which triggered the violation. These
bits are undefined if the error code registers (MMCECn) are cleared.
3.4
Functional Description
This section provides a complete functional description of the S12ZMMC module.
3.4.1
Global Memory Map
The S12ZMMC maps all on-chip resources into an 16MB address space, the global memory map. The
exact resource mapping is shown in Figure 3-8. The global address space is used by the S12ZCPU, ADC,
and the S12ZBDC module.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
123
Chapter 3 Memory Mapping Control (S12ZMMCV1)
Register Space
0x00_0000
0x00_1000
4 KB
RAM
max. 1 MByte - 4 KB
0x10_0000
EEPROM
max. 1 MByte - 48 KB
Reserved
512 Byte
0x1F_4000
Reserved (read only)
6 KBKB
0x1F_8000
NVM IFR
256 Byte
0x1F_C000
0x20_0000
Unmapped
6 MByte
0x80_0000
Program NVM
max. 8 MByte
Unmapped
address range
Low address aligned
High address aligned
0xFF_FFFF
Figure 3-8. Global Memory Map
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
124
Freescale Semiconductor
Chapter 3 Memory Mapping Control (S12ZMMCV1)
3.4.2
Illegal Accesses
The S12ZMMC module monitors all memory traffic for illegal accesses. See Table 3-8 for a complete list
of all illegal accesses.
Table 3-8. Illegal memory accesses
Register
space
RAM
EEPROM
Reserved
Space
Reserved
Read-only
Space
NVM IFR
Program NVM
Unmapped
Space
S12ZCPU
S12ZBDC
ADC
Read access
ok
ok
illegal access
Write access
ok
ok
illegal access
Code execution
illegal access
Read access
ok
ok
ok
Write access
ok
ok
ok
Code execution
ok
Read access
ok(1)
ok1
ok1
Write access
illegal access
illegal access
illegal access
Code execution
ok1
Read access
ok
ok
illegal access
Write access
only permitted in SS mode
ok
illegal access
Code execution
illegal access
Read access
ok
ok
illegal access
Write access
illegal access
illegal access
illegal access
Code execution
illegal access
Read access
ok1
ok1
illegal access
Write access
illegal access
illegal access
illegal access
Code execution
illegal access
Read access
ok1
ok1
ok1
Write access
illegal access
illegal access
illegal access
Code execution
ok1
Read access
illegal access
illegal access
illegal access
Write access
illegal access
illegal access
illegal access
Code execution
illegal access
1. Unsupported NVM accesses during NVM command execution (“collisions”), are treated as illegal accesses.
Illegal accesses are reported in several ways:
• All illegal accesses performed by the S12ZCPU trigger machine exceptions.
• All illegal accesses performed through the S12ZBDC interface, are captured in the ILLACC bit of
the BDCCSRL register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
125
Chapter 3 Memory Mapping Control (S12ZMMCV1)
•
All illegal accesses performed by the ADC module trigger error interrupts. See ADC section for
details.
NOTE
Illegal accesses caused by S12ZCPU opcode prefetches will also trigger
machine exceptions, even if those opcodes might not be executed in the
program flow. To avoid these machine exceptions, S12ZCPU instructions
must not be executed from the last (high addresses) 8 bytes of RAM,
EEPROM, and Flash.
3.4.3
Uncorrectable ECC Faults
RAM and flash use error correction codes (ECC) to detect and correct memory corruption. Each
uncorrectable memory corruption, which is detected during a S12ZCPU or ADC access triggers a machine
exception. Uncorrectable memory corruptions which are detected during a S12ZBDC access, are captured
in the RAMWF or the RDINV bit of the BDCCSRL register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
126
Freescale Semiconductor
Chapter 4
Interrupt (S12ZINTV0)
Table 4-1. Revision History
Version
Number
Revision
Date
Effective
Date
V00.01
17 Apr 2009
all
Initial version based on S12XINT V2.06
V00.02
14 Jul 2009
all
Reduce RESET vectors from three to one.
V00.03
05 Oct 2009
all
Removed dedicated ECC machine exception vector and marked vector-table
entry “reserved for future use”.
Added a second illegal op-code vector (to distinguish between SPARE and
TRAP).
V00.04
04 Jun 2010
all
Fixed remaining descriptions of RESET vectors.
Split non-maskable hardware interrupts into XGATE software error and
machine exception requests.
Replaced mentions of CCR (old name from S12X) with CCW (new name).
V00.05
12 Jan 2011
all
Corrected wrong IRQ vector address in some descriptions.
V00.06
22 Mar 2011
all
Added vectors for RAM ECC and NVM ECC machine exceptions. And moved
position to 1E0..1E8.
Moved XGATE error interrupt to vector 1DC.
Remaining vectors accordingly.
Removed illegal address reset as a potential reset source.
V00.07
15 Apr 2011
all
Removed illegal address reset as a potential reset source from Exception
vector table as well. Added the other possible reset sources to the table.
Changed register addresses according to S12Z platform definition.
V00.08
02 May 2011
all
Reduced machine exception vectors to one.
Removed XGATE error interrupt.
Moved Spurious interrupt vector to 1DC.
Moved vector base address to 010 to make room for NVM non-volatile
registers.
V00.09
12 Aug 2011
all
Added: Machine exceptions can cause wake-up from STOP or WAIT
V00.10
21 Feb 2012
all
Corrected reset value for INT_CFADDR register
V00.11
02 Jul 2012
all
Removed references and functions related to XGATE
V00.12
22 May 2013
all
added footnote about availability of “Wake-up from STOP or WAIT by XIRQ
with X bit set” feature
4.1
Description of Changes
Introduction
The INT module decodes the priority of all system exception requests and provides the applicable vector
for processing the exception to the CPU. The INT module supports:
• I-bit and X-bit maskable interrupt requests
• One non-maskable unimplemented page1 op-code trap
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
127
Chapter 4 Interrupt (S12ZINTV0)
•
•
•
•
•
•
One non-maskable unimplemented page2 op-code trap
One non-maskable software interrupt (SWI)
One non-maskable system call interrupt (SYS)
One non-maskable machine exception vector request
One spurious interrupt vector request
One system reset vector request
Each of the I-bit maskable interrupt requests can be assigned to one of seven priority levels supporting a
flexible priority scheme. The priority scheme can be used to implement nested interrupt capability where
interrupts from a lower level are automatically blocked if a higher level interrupt is being processed.
4.1.1
Glossary
The following terms and abbreviations are used in the document.
Table 4-2. Terminology
Term
CCW
Condition Code Register (in the S12Z CPU)
DMA
Direct Memory Access
INT
Interrupt
IPL
Interrupt Processing Level
ISR
Interrupt Service Routine
MCU
Micro-Controller Unit
IRQ
refers to the interrupt request associated with the IRQ pin
XIRQ
4.1.2
•
•
•
•
•
•
•
•
•
Meaning
refers to the interrupt request associated with the XIRQ pin
Features
Interrupt vector base register (IVBR)
One system reset vector (at address 0xFFFFFC).
One non-maskable unimplemented page1 op-code trap (SPARE) vector (at address vector base1 +
0x0001F8).
One non-maskable unimplemented page2 op-code trap (TRAP) vector (at address vector base1 +
0x0001F4).
One non-maskable software interrupt request (SWI) vector (at address vector base1 + 0x0001F0).
One non-maskable system call interrupt request (SYS) vector (at address vector base1 +
0x00001EC).
One non-maskable machine exception vector request (at address vector base1 + 0x0001E8).
One spurious interrupt vector (at address vector base1 + 0x0001DC).
One X-bit maskable interrupt vector request associated with XIRQ (at address vector base1 +
0x0001D8).
1. The vector base is a 24-bit address which is accumulated from the contents of the interrupt vector base register (IVBR, used
as the upper 15 bits of the address) and 0x000 (used as the lower 9 bits of the address).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
128
Freescale Semiconductor
Chapter 4 Interrupt (S12ZINTV0)
•
•
•
•
•
4.1.3
•
•
•
4.1.4
One I-bit maskable interrupt vector request associated with IRQ (at address vector base1 +
0x0001D4).
up to 113 additional I-bit maskable interrupt vector requests (at addresses vector base1 + 0x000010
.. vector base + 0x0001D0).
Each I-bit maskable interrupt request has a configurable priority level.
I-bit maskable interrupts can be nested, depending on their priority levels.
Wakes up the system from stop or wait mode when an appropriate interrupt request occurs or
whenever XIRQ is asserted, even if X interrupt is masked.
Modes of Operation
Run mode
This is the basic mode of operation.
Wait mode
In wait mode, the INT module is capable of waking up the CPU if an eligible CPU exception
occurs. Please refer to Section 4.5.3, “Wake Up from Stop or Wait Mode” for details.
Stop Mode
In stop mode, the INT module is capable of waking up the CPU if an eligible CPU exception
occurs. Please refer to Section 4.5.3, “Wake Up from Stop or Wait Mode” for details.
Block Diagram
Figure 4-1 shows a block diagram of the INT module.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
129
Chapter 4 Interrupt (S12ZINTV0)
Peripheral
Interrupt Requests
Wake Up
CPU
Interrupt
Requests
One Set Per Channel
(Up to 117 Channels)
PRIOLVL2
PRIOLVL1
PRIOLVL0
New
IPL
Priority
Level
Filter
PRIOLVLn
Priority Level
= configuration bits from the associated
channel configuration register
IVBR
= Interrupt Vector Base
IPL
= Interrupt Processing Level
IVBR
Highest Pending
IPL
To CPU
Non I Bit Maskable
Channels
Priority
Decoder
Vector
Address
Current
IPL
Figure 4-1. INT Block Diagram
4.2
External Signal Description
The INT module has no external signals.
4.3
Memory Map and Register Definition
This section provides a detailed description of all registers accessible in the INT module.
4.3.1
Module Memory Map
Table 4-3 gives an overview over all INT module registers.
Table 4-3. INT Memory Map
Address
Use
Access
0x000010–0x000011
Interrupt Vector Base Register (IVBR)
R/W
0x000012–0x000016
RESERVED
—
0x000017
Interrupt Request Configuration Address Register
(INT_CFADDR)
R/W
0x000018
Interrupt Request Configuration Data Register 0
(INT_CFDATA0)
R/W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
130
Freescale Semiconductor
Chapter 4 Interrupt (S12ZINTV0)
Table 4-3. INT Memory Map
4.3.2
0x000019
Interrupt Request Configuration Data Register 1
(INT_CFDATA1)
R/W
0x00001A
Interrupt Request Configuration Data Register 2
(INT_CFDATA2
R/W
0x00001B
Interrupt Request Configuration Data Register 3
(INT_CFDATA3)
R/W
0x00001C
Interrupt Request Configuration Data Register 4
(INT_CFDATA4)
R/W
0x00001D
Interrupt Request Configuration Data Register 5
(INT_CFDATA5)
R/W
0x00001E
Interrupt Request Configuration Data Register 6
(INT_CFDATA6)
R/W
0x00001F
Interrupt Request Configuration Data Register 7
(INT_CFDATA7)
R/W
Register Descriptions
This section describes in address order all the INT module registers and their individual bits.
Address
Register
Name
0x000010
IVBR
Bit 7
6
5
R
R
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
0x000019 INT_CFDATA1 R
W
0x00001A INT_CFDATA2 R
W
0x00001B INT_CFDATA3 R
W
0x00001C INT_CFDATA4 R
1
Bit 0
0
INT_CFADDR[6:3]
W
0x000018 INT_CFDATA0 R
2
IVB_ADDR[7:1]
W
0x000017 INT_CFADDR R
3
IVB_ADDR[15:8]
W
0x000011
4
W
0
0
PRIOLVL[2:0]
PRIOLVL[2:0]
PRIOLVL[2:0]
PRIOLVL[2:0]
PRIOLVL[2:0]
= Unimplemented or Reserved
Figure 4-2. INT Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
131
Chapter 4 Interrupt (S12ZINTV0)
Register
Name
Address
0x00001D INT_CFDATA5 R
Bit 7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
1
PRIOLVL[2:0]
W
0x00001E INT_CFDATA6 R
PRIOLVL[2:0]
W
0x00001F INT_CFDATA7 R
Bit 0
PRIOLVL[2:0]
W
= Unimplemented or Reserved
Figure 4-2. INT Register Summary
4.3.2.1
Interrupt Vector Base Register (IVBR)
Address: 0x000010
15
14
13
12
11
10
R
8
7
6
5
4
3
2
1
0
0
IVB_ADDR[15:1]
W
Reset
9
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
Figure 4-3. Interrupt Vector Base Register (IVBR)
Read: Anytime
Write: Anytime
Table 4-4. IVBR Field Descriptions
Field
Description
15–1
IVB_ADDR
[15:1]
Interrupt Vector Base Address Bits — These bits represent the upper 15 bits of all vector addresses. Out
of reset these bits are set to 0xFFFE (i.e., vectors are located at 0xFFFE00–0xFFFFFF).
Note: A system reset will initialize the interrupt vector base register with “0xFFFE” before it is used to
determine the reset vector address. Therefore, changing the IVBR has no effect on the location of the
reset vector (0xFFFFFC–0xFFFFFF).
4.3.2.2
Interrupt Request Configuration Address Register (INT_CFADDR)
Address: 0x000017
7
R
6
0
0
4
3
INT_CFADDR[6:3]
W
Reset
5
0
0
0
1
2
1
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 4-4. Interrupt Configuration Address Register (INT_CFADDR)
Read: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
132
Freescale Semiconductor
Chapter 4 Interrupt (S12ZINTV0)
Write: Anytime
Table 4-5. INT_CFADDR Field Descriptions
Field
Description
6–3
Interrupt Request Configuration Data Register Select Bits — These bits determine which of the 128
INT_CFADDR[6:3] configuration data registers are accessible in the 8 register window at INT_CFDATA0–7.
The hexadecimal value written to this register corresponds to the upper 4 bits of the vector number
(multiply with 4 to get the vector address offset).
If, for example, the value 0x70 is written to this register, the configuration data register block for the 8
interrupt vector requests starting with vector at address (vector base + (0x70*4 = 0x0001C0)) is selected
and can be accessed as INT_CFDATA0–7.
4.3.2.3
Interrupt Request Configuration Data Registers (INT_CFDATA0–7)
The eight register window visible at addresses INT_CFDATA0–7 contains the configuration data for the
block of eight interrupt requests (out of 128) selected by the interrupt configuration address register
(INT_CFADDR) in ascending order. INT_CFDATA0 represents the interrupt configuration data register
of the vector with the lowest address in this block, while INT_CFDATA7 represents the interrupt
configuration data register of the vector with the highest address, respectively.
Address: 0x000018
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-5. Interrupt Request Configuration Data Register 0 (INT_CFDATA0)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Address: 0x000019
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-6. Interrupt Request Configuration Data Register 1 (INT_CFDATA1)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Address: 0x00001A
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-7. Interrupt Request Configuration Data Register 2 (INT_CFDATA2)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
133
Chapter 4 Interrupt (S12ZINTV0)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Address: 0x00001B
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-8. Interrupt Request Configuration Data Register 3 (INT_CFDATA3)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Address: 0x00001C
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-9. Interrupt Request Configuration Data Register 4 (INT_CFDATA4)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Address: 0x00001D
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-10. Interrupt Request Configuration Data Register 5 (INT_CFDATA5)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Address: 0x00001E
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-11. Interrupt Request Configuration Data Register 6 (INT_CFDATA6)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
134
Freescale Semiconductor
Chapter 4 Interrupt (S12ZINTV0)
Address: 0x00001F
R
7
6
5
4
3
0
0
0
0
0
0
0
0
0
0
2
0
PRIOLVL[2:0]
W
Reset
1
0
0
1(1)
= Unimplemented or Reserved
Figure 4-12. Interrupt Request Configuration Data Register 7 (INT_CFDATA7)
1. Please refer to the notes following the PRIOLVL[2:0] description below.
Read: Anytime
Write: Anytime
Table 4-6. INT_CFDATA0–7 Field Descriptions
Field
Description
2–0
Interrupt Request Priority Level Bits — The PRIOLVL[2:0] bits configure the interrupt request priority level of
PRIOLVL[2:0] the associated interrupt request. Out of reset all interrupt requests are enabled at the lowest active level (“1”).
Please also refer to Table 4-7 for available interrupt request priority levels.
Note: Write accesses to configuration data registers of unused interrupt channels are ignored and read
accesses return all 0s. For information about what interrupt channels are used in a specific MCU, please
refer to the Device Reference Manual for that MCU.
Note: When non I-bit maskable request vectors are selected, writes to the corresponding INT_CFDATA
registers are ignored and read accesses return all 0s. The corresponding vectors do not have
configuration data registers associated with them.
Note: Write accesses to the configuration register for the spurious interrupt vector request
(vector base + 0x0001DC) are ignored and read accesses return 0x07 (request is handled by the CPU,
PRIOLVL = 7).
Table 4-7. Interrupt Priority Levels
Priority
low
high
4.4
PRIOLVL2
PRIOLVL1
PRIOLVL0
Meaning
0
0
0
Interrupt request is disabled
0
0
1
Priority level 1
0
1
0
Priority level 2
0
1
1
Priority level 3
1
0
0
Priority level 4
1
0
1
Priority level 5
1
1
0
Priority level 6
1
1
1
Priority level 7
Functional Description
The INT module processes all exception requests to be serviced by the CPU module. These exceptions
include interrupt vector requests and reset vector requests. Each of these exception types and their overall
priority level is discussed in the subsections below.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
135
Chapter 4 Interrupt (S12ZINTV0)
4.4.1
S12Z Exception Requests
The CPU handles both reset requests and interrupt requests. The INT module contains registers to
configure the priority level of each I-bit maskable interrupt request which can be used to implement an
interrupt priority scheme. This also includes the possibility to nest interrupt requests. A priority decoder
is used to evaluate the relative priority of pending interrupt requests.
4.4.2
Interrupt Prioritization
After system reset all I-bit maskable interrupt requests are configured to be enabled, are set up to be
handled by the CPU and have a pre-configured priority level of 1. Exceptions to this rule are the nonmaskable interrupt requests and the spurious interrupt vector request at (vector base + 0x0001DC) which
cannot be disabled, are always handled by the CPU and have a fixed priority levels. A priority level of 0
effectively disables the associated I-bit maskable interrupt request.
If more than one interrupt request is configured to the same interrupt priority level the interrupt request
with the higher vector address wins the prioritization.
The following conditions must be met for an I-bit maskable interrupt request to be processed.
1. The local interrupt enabled bit in the peripheral module must be set.
2. The setup in the configuration register associated with the interrupt request channel must meet the
following conditions:
a) The priority level must be set to non zero.
b) The priority level must be greater than the current interrupt processing level in the condition
code register (CCW) of the CPU (PRIOLVL[2:0] > IPL[2:0]).
3. The I-bit in the condition code register (CCW) of the CPU must be cleared.
4. There is no access violation interrupt request pending.
5. There is no SYS, SWI, SPARE, TRAP, Machine Exception or XIRQ request pending.
NOTE
All non I-bit maskable interrupt requests always have higher priority than Ibit maskable interrupt requests. If an I-bit maskable interrupt request is
interrupted by a non I-bit maskable interrupt request, the currently active
interrupt processing level (IPL) remains unaffected. It is possible to nest
non I-bit maskable interrupt requests, e.g., by nesting SWI, SYS or TRAP
calls.
4.4.2.1
Interrupt Priority Stack
The current interrupt processing level (IPL) is stored in the condition code register (CCW) of the CPU.
This way the current IPL is automatically pushed to the stack by the standard interrupt stacking procedure.
The new IPL is copied to the CCW from the priority level of the highest priority active interrupt request
channel which is configured to be handled by the CPU. The copying takes place when the interrupt vector
is fetched. The previous IPL is automatically restored from the stack by executing the RTI instruction.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
136
Freescale Semiconductor
Chapter 4 Interrupt (S12ZINTV0)
4.4.3
Priority Decoder
The INT module contains a priority decoder to determine the relative priority for all interrupt requests
pending for the CPU.
A CPU interrupt vector is not supplied until the CPU requests it. Therefore, it is possible that a higher
priority interrupt request could override the original exception which caused the CPU to request the vector.
In this case, the CPU will receive the highest priority vector and the system will process this exception first
instead of the original request.
If the interrupt source is unknown (for example, in the case where an interrupt request becomes inactive
after the interrupt has been recognized, but prior to the vector request), the vector address supplied to the
CPU defaults to that of the spurious interrupt vector.
NOTE
Care must be taken to ensure that all exception requests remain active until
the system begins execution of the applicable service routine; otherwise, the
exception request may not get processed at all or the result may be a
spurious interrupt request (vector at address (vector base + 0x0001DC)).
4.4.4
Reset Exception Requests
The INT module supports one system reset exception request. The different reset types are mapped to this
vector (for details please refer to the Clock and Power Management Unit module (CPMU)):
1. Pin reset
2. Power-on reset
3. Low-voltage reset
4. Clock monitor reset request
5. COP watchdog reset request
4.4.5
Exception Priority
The priority (from highest to lowest) and address of all exception vectors issued by the INT module upon
request by the CPU are shown in Table 4-8. Generally, all non-maskable interrupts have higher priorities
than maskable interrupts. Please note that between the four software interrupts (Unimplemented op-code
trap page1/page2 requests, SWI request, SYS request) there is no real priority defined since they cannot
occur simultaneously (the S12Z CPU executes one instruction at a time).
Table 4-8. Exception Vector Map and Priority
Vector Address(1)
0xFFFFFC
Source
Pin reset, power-on reset, low-voltage reset, clock monitor reset, COP watchdog reset
(Vector base + 0x0001F8)
Unimplemented page1 op-code trap (SPARE) vector request
(Vector base + 0x0001F4)
Unimplemented page2 op-code trap (TRAP) vector request
(Vector base + 0x0001F0)
Software interrupt instruction (SWI) vector request
(Vector base + 0x0001EC)
System call interrupt instruction (SYS) vector request
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
137
Chapter 4 Interrupt (S12ZINTV0)
Table 4-8. Exception Vector Map and Priority
Vector Address(1)
Source
(Vector base + 0x0001E8)
Machine exception vector request
(Vector base + 0x0001E4)
Reserved
(Vector base + 0x0001E0)
Reserved
(Vector base + 0x0001DC)
Spurious interrupt
(Vector base + 0x0001D8)
XIRQ interrupt request
(Vector base + 0x0001D4)
IRQ interrupt request
(Vector base + 0x000010
Device specific I-bit maskable interrupt sources (priority determined by the associated
..
configuration registers, in descending order)
Vector base + 0x0001D0)
1. 24 bits vector address based
4.4.6
Interrupt Vector Table Layout
The interrupt vector table contains 128 entries, each 32 bits (4 bytes) wide. Each entry contains a 24-bit
address (3 bytes) which is stored in the 3 low-significant bytes of the entry. The content of the most
significant byte of a vector-table entry is ignored. Figure 4-13 illustrates the vector table entry format.
Bits
[31:24]
[23:0]
(unused)
ISR Address
Figure 4-13. Interrupt Vector Table Entry
4.5
4.5.1
Initialization/Application Information
Initialization
After system reset, software should:
• Initialize the interrupt vector base register if the interrupt vector table is not located at the default
location (0xFFFE00–0xFFFFFB).
• Initialize the interrupt processing level configuration data registers (INT_CFADDR,
INT_CFDATA0–7) for all interrupt vector requests with the desired priority levels. It might be a
good idea to disable unused interrupt requests.
• Enable I-bit maskable interrupts by clearing the I-bit in the CCW.
• Enable the X-bit maskable interrupt by clearing the X-bit in the CCW (if required).
4.5.2
Interrupt Nesting
The interrupt request priority level scheme makes it possible to implement priority based interrupt request
nesting for the I-bit maskable interrupt requests.
• I-bit maskable interrupt requests can be interrupted by an interrupt request with a higher priority,
so that there can be up to seven nested I-bit maskable interrupt requests at a time (refer to Figure 414 for an example using up to three nested interrupt requests).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
138
Freescale Semiconductor
Chapter 4 Interrupt (S12ZINTV0)
I-bit maskable interrupt requests cannot be interrupted by other I-bit maskable interrupt requests per
default. In order to make an interrupt service routine (ISR) interruptible, the ISR must explicitly clear the
I-bit in the CCW (CLI). After clearing the I-bit, I-bit maskable interrupt requests with higher priority can
interrupt the current ISR.
An ISR of an interruptible I-bit maskable interrupt request could basically look like this:
• Service interrupt, e.g., clear interrupt flags, copy data, etc.
• Clear I-bit in the CCW by executing the CPU instruction CLI (thus allowing interrupt requests with
higher priority)
• Process data
• Return from interrupt by executing the instruction RTI
0
Stacked IPL
IPL in CCW
0
0
4
0
0
0
4
7
4
3
1
0
7
6
RTI
L7
5
4
RTI
Processing Levels
3
L3 (Pending)
2
L4
RTI
1
L1 (Pending)
0
RTI
Reset
Figure 4-14. Interrupt Processing Example
4.5.3
4.5.3.1
Wake Up from Stop or Wait Mode
CPU Wake Up from Stop or Wait Mode
Every I-bit maskable interrupt request which is configured to be handled by the CPU is capable of waking
the MCU from stop or wait mode. Additionally machine exceptions can wake-up the MCU from stop or
wait mode.
To determine whether an I-bit maskable interrupts is qualified to wake up the CPU or not, the same settings
as in normal run mode are applied during stop or wait mode:
• If the I-bit in the CCW is set, all I-bit maskable interrupts are masked from waking up the MCU.
• An I-bit maskable interrupt is ignored if it is configured to a priority level below or equal to the
current IPL in CCW.
The X-bit maskable interrupt request can wake up the MCU from stop or wait mode at anytime, even if
the X-bit in CCW is set1. If the X-bit maskable interrupt request is used to wake-up the MCU with the XS12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
139
Chapter 4 Interrupt (S12ZINTV0)
bit in the CCW set, the associated ISR is not called. The CPU then resumes program execution with the
instruction following the WAI or STOP instruction. This feature works following the same rules like any
interrupt request, i.e. care must be taken that the X-bit maskable interrupt request used for wake-up
remains active at least until the system begins execution of the instruction following the WAI or STOP
instruction; otherwise, wake-up may not occur.
1. The capability of the XIRQ pin to wake-up the MCU with the X bit set may not be available if, for example, the XIRQ pin is
shared with other peripheral modules on the device. Please refer to the Port Integration Module (PIM) section of the MCU
reference manual for details.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
140
Freescale Semiconductor
Chapter 5
Background Debug Controller (S12ZBDCV2)
Table 5-1. Revision History
Revision
Number
Revision Date
Sections
Affected
V2.04
03.Dec.2012
Section 5.1.3.3
Included BACKGROUND/ Stop mode dependency
V2.05
22.Jan.2013
Section 5.3.2.2
Improved NORESP description and added STEP1/ Wait mode dependency
V2.06
22.Mar.2013
Section 5.3.2.2
Improved NORESP description of STEP1/ Wait mode dependency
Description of Changes
V2.07
11.Apr.2013
V2.08
31.May.2013
Section 5.4.4.4
Section 5.4.7.1
Removed misleading WAIT and BACKGROUND interdepency description
Added subsection dedicated to Long-ACK
V2.09
29.Aug.2013
Section 5.4.4.12
Noted that READ_DBGTB is only available for devices featuring a trace buffer.
V2.10
21.Oct.2013
Section 5.1.3.3.2 Improved description of NORESP dependence on WAIT and BACKROUND
5.1
Section 5.1.3.3.1 Improved STOP and BACKGROUND interdepency description
Introduction
The background debug controller (BDC) is a single-wire, background debug system implemented in onchip hardware for minimal CPU intervention. The device BKGD pin interfaces directly to the BDC.
The S12ZBDC maintains the standard S12 serial interface protocol but introduces an enhanced handshake
protocol and enhanced BDC command set to support the linear instruction set family of S12Z devices and
offer easier, more flexible internal resource access over the BDC serial interface.
5.1.1
Glossary
Table 5-2. Glossary Of Terms
Term
Definition
DBG
On chip Debug Module
BDM
Active Background Debug Mode
CPU
S12Z CPU
SSC
Special Single Chip Mode (device operating mode
NSC
Normal Single Chip Mode (device operating mode)
BDCSI
Background Debug Controller Serial Interface. This refers to the single pin BKGD serial interface.
EWAIT
Optional S12 feature which allows external devices to delay external accesses until deassertion of EWAIT
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
141
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.1.2
Features
The BDC includes these distinctive features:
• Single-wire communication with host development system
• SYNC command to determine communication rate
• Genuine non-intrusive handshake protocol
• Enhanced handshake protocol for error detection and stop mode recognition
• Active out of reset in special single chip mode
• Most commands not requiring active BDM, for minimal CPU intervention
• Full global memory map access without paging
• Simple flash mass erase capability
5.1.3
Modes of Operation
S12 devices feature power modes (run, wait, and stop) and operating modes (normal single chip, special
single chip). Furthermore, the operation of the BDC is dependent on the device security status.
5.1.3.1
BDC Modes
The BDC features module specific modes, namely disabled, enabled and active. These modes are
dependent on the device security and operating mode. In active BDM the CPU ceases execution, to allow
BDC system access to all internal resources including CPU internal registers.
5.1.3.2
Security and Operating mode Dependency
In device run mode the BDC dependency is as follows
• Normal modes, unsecure device
General BDC operation available. The BDC is disabled out of reset.
• Normal modes, secure device
BDC disabled. No BDC access possible.
• Special single chip mode, unsecure
BDM active out of reset. All BDC commands are available.
• Special single chip mode, secure
BDM active out of reset. Restricted command set available.
When operating in secure mode, BDC operation is restricted to allow checking and clearing security by
mass erasing the on-chip flash memory. Secure operation prevents BDC access to on-chip memory other
than mass erase. The BDC command set is restricted to those commands classified as Always-available.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
142
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.1.3.3
5.1.3.3.1
Low-Power Modes
Stop Mode
The execution of the CPU STOP instruction leads to stop mode only when all bus masters (CPU, or others,
depending on the device) have finished processing. The operation during stop mode depends on the
ENBDC and BDCCIS bit settings as summarized in Table 5-3
Table 5-3. BDC STOP Operation Dependencies
ENBDC
BDCCIS
Description Of Operation
0
0
BDC has no effect on STOP mode.
0
1
BDC has no effect on STOP mode.
1
0
Only BDCSI clock continues
1
1
All clocks continue
A disabled BDC has no influence on stop mode operation. In this case the BDCSI clock is disabled in stop
mode thus it is not possible to enable the BDC from within stop mode.
STOP Mode With BDC Enabled And BDCCIS Clear
If the BDC is enabled and BDCCIS is clear, then the BDC prevents the BDCCLK clock (Figure 5-5) from
being disabled in stop mode. This allows BDC communication to continue throughout stop mode in order
to access the BDCCSR register. All other device level clock signals are disabled on entering stop mode.
NOTE
This is intended for application debugging, not for fast flash programming.
Thus the CLKSW bit must be clear to map the BDCSI to BDCCLK.
With the BDC enabled, an internal acknowledge delays stop mode entry and exit by 2 BDCSI clock + 2
bus clock cycles. If no other module delays stop mode entry and exit, then these additional clock cycles
represent a difference between the debug and not debug cases. Furthermore if a BDC internal access is
being executed when the device is entering stop mode, then the stop mode entry is delayed until the internal
access is complete (typically for 1 bus clock cycle).
Accesses to the internal memory map are not possible when the internal device clocks are disabled. Thus
attempted accesses to memory mapped resources are suppressed and the NORESP flag is set. Resources
can be accessed again by the next command received following exit from Stop mode.
A BACKGROUND command issued whilst in stop mode remains pending internally until the device
leaves stop mode. This means that subsequent active BDM commands, issued whilst BACKGROUND is
pending, set the ILLCMD flag because the device is not yet in active BDM.
If ACK handshaking is enabled, then the first ACK, following a stop mode entry is long to indicate a stop
exception. The BDC indicates a stop mode occurrence by setting the BDCCSR bit STOP. If the host
attempts further communication before the ACK pulse generation then the OVRUN bit is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
143
Chapter 5 Background Debug Controller (S12ZBDCV2)
STOP Mode With BDC Enabled And BDCCIS Set
If the BDC is enabled and BDCCIS is set, then the BDC prevents core clocks being disabled in stop mode.
This allows BDC communication, for access of internal memory mapped resources, but not CPU registers,
to continue throughout stop mode.
A BACKGROUND command issued whilst in stop mode remains pending internally until the device
leaves stop mode. This means that subsequent active BDM commands, issued whilst BACKGROUND is
pending, set the ILLCMD flag because the device is not yet in active BDM.
If ACK handshaking is enabled, then the first ACK, following a stop mode entry is long to indicate a stop
exception. The BDC indicates a stop mode occurrence by setting the BDCCSR bit STOP. If the host
attempts further communication before the ACK pulse generation then the OVRUN bit is set.
5.1.3.3.2
Wait Mode
The device enters wait mode when the CPU starts to execute the WAI instruction. The second part of the
WAI instruction (return from wait mode) can only be performed when an interrupt occurs. Thus on
entering wait mode the CPU is in the middle of the WAI instruction and cannot permit access to CPU
internal resources, nor allow entry to active BDM. Thus only commands classified as Non-Intrusive or
Always-Available are possible in wait mode.
On entering wait mode, the WAIT flag in BDCCSR is set. If the ACK handshake protocol is enabled then
the first ACK generated after WAIT has been set is a long-ACK pulse. Thus the host can recognize a wait
mode occurrence. The WAIT flag remains set and cannot be cleared whilst the device remains in wait
mode. After the device leaves wait mode the WAIT flag can be cleared by writing a “1” to it.
A BACKGROUND command issued whilst in wait mode sets the NORESP bit and the BDM active
request remains pending internally until the CPU leaves wait mode due to an interrupt. The device then
enters BDM with the PC pointing to the address of the first instruction of the ISR.
With ACK disabled, further Non-Intrusive or Always-Available commands are possible, in this pending
state, but attempted Active-Background commands set NORESP and ILLCMD because the BDC is not in
active BDM state.
With ACK enabled, if the host attempts further communication before the ACK pulse generation then the
OVRUN bit is set.
Similarly the STEP1 command issued from a WAI instruction cannot be completed by the CPU until the
CPU leaves wait mode due to an interrupt. The first STEP1 into wait mode sets the BDCCSR WAIT bit.
If the part is still in Wait mode and a further STEP1 is carried out then the NORESP and ILLCMD bits are
set because the device is no longer in active BDM for the duration of WAI execution.
5.1.4
Block Diagram
A block diagram of the BDC is shown in Figure 5-1.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
144
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
HOST
SYSTEM
BKGD
SERIAL INTERFACE CONTROL
AND SHIFT REGISTER
CLOCK DOMAIN
CONTROL
INSTRUCTION
DECODE AND
FSM
BDCSI
CORE CLOCK
ADDRESS
BUS INTERFACE
AND
CONTROL LOGIC
BDCCSR REGISTER
AND DATAPATH
CONTROL
DATA
BUS CONTROL
CPU CONTROL
ERASE FLASH
FLASH ERASED
FLASH SECURE
Figure 5-1. BDC Block Diagram
5.2
External Signal Description
A single-wire interface pin (BKGD) is used to communicate with the BDC system. During reset, this pin
is a device mode select input. After reset, this pin becomes the dedicated serial interface pin for the BDC.
BKGD is a pseudo-open-drain pin with an on-chip pull-up. Unlike typical open-drain pins, the external
RC time constant on this pin due to external capacitance, plays almost no role in signal rise time. The
custom protocol provides for brief, actively driven speed-up pulses to force rapid rise times on this pin
without risking harmful drive level conflicts. Refer to Section 5.4.6” for more details.
5.3
5.3.1
Memory Map and Register Definition
Module Memory Map
Table 5-4 shows the BDC memory map.
Table 5-4. BDC Memory Map
Global Address
Module
Size
(Bytes)
Not Applicable
BDC registers
2
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
145
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.3.2
Register Descriptions
The BDC registers are shown in Figure 5-2. Registers are accessed only by host-driven communications
to the BDC hardware using READ_BDCCSR and WRITE_BDCCSR commands. They are not accessible
in the device memory map.
Global
Address
Register
Name
Bit 7
Not
Applicable
BDCCSRH R
Not
Applicable
BDCCSRL R
W
W
ENBDC
WAIT
6
BDMACT
STOP
5
4
0
BDCCIS
RAMWF
OVRUN
= Unimplemented, Reserved
3
2
STEAL
CLKSW
NORESP
RDINV
0
1
Bit 0
UNSEC
ERASE
ILLACC
ILLCMD
= Always read zero
Figure 5-2. BDC Register Summary
5.3.2.1
BDC Control Status Register High (BDCCSRH)
Register Address: This register is not in the device memory map. It is accessible using BDC inherent addressing commands
7
R
W
ENBDC
6
BDMACT
5
BDCCIS
4
0
3
2
STEAL
CLKSW
1
0
UNSEC
ERASE
Reset
Secure AND SSC-Mode
1
1
0
0
0
0
0
0
Unsecure AND SSC-Mode
1
1
0
0
0
0
1
0
Secure AND NSC-Mode
0
0
0
0
0
0
0
0
Unsecure AND NSC-Mode
0
0
0
0
0
0
1
0
= Unimplemented, Reserved
0
= Always read zero
Figure 5-3. BDC Control Status Register High (BDCCSRH)
Read: All modes through BDC operation only.
Write: All modes through BDC operation only, when not secured, but subject to the following:
— Bits 7,3 and 2 can only be written by WRITE_BDCCSR commands.
— Bit 5 can only be written by WRITE_BDCCSR commands when the device is not in stop mode.
— Bits 6, 1 and 0 cannot be written. They can only be updated by internal hardware.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
146
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-5. BDCCSRH Field Descriptions
Field
Description
7
ENBDC
Enable BDC — This bit controls whether the BDC is enabled or disabled. When enabled, active BDM can be
entered and non-intrusive commands can be carried out. When disabled, active BDM is not possible and the
valid command set is restricted. Further information is provided in Table 5-7.
0 BDC disabled
1 BDC enabled
Note: ENBDC is set out of reset in special single chip mode.
6
BDMACT
BDM Active Status — This bit becomes set upon entering active BDM. BDMACT is cleared as part of the active
BDM exit sequence.
0 BDM not active
1 BDM active
Note: BDMACT is set out of reset in special single chip mode.
5
BDCCIS
BDC Continue In Stop — If ENBDC is set then BDCCIS selects the type of BDC operation in stop mode (as
shown in Table 5-3). If ENBDC is clear, then the BDC has no effect on stop mode and no BDC communication
is possible.If ACK pulse handshaking is enabled, then the first ACK pulse following stop mode entry is a long
ACK. This bit cannot be written when the device is in stop mode.
0 Only the BDCSI clock continues in stop mode
1 All clocks continue in stop mode
3
STEAL
Steal enabled with ACK— This bit forces immediate internal accesses with the ACK handshaking protocol
enabled. If ACK handshaking is disabled then BDC accesses steal the next bus cycle.
0 If ACK is enabled then BDC accesses await a free cycle, with a timeout of 512 cycles
1 If ACK is enabled then BDC accesses are carried out in the next bus cycle
2
CLKSW
Clock Switch — The CLKSW bit controls the BDCSI clock source. This bit is initialized to “0” by each reset and
can be written to “1”. Once it has been set, it can only be cleared by a reset. When setting CLKSW a minimum
delay of 150 cycles at the initial clock speed must elapse before the next command can be sent. This guarantees
that the start of the next BDC command uses the new clock for timing subsequent BDC communications.
0 BDCCLK used as BDCSI clock source
1 Device fast clock used as BDCSI clock source
Note: Refer to the device specification to determine which clock connects to the BDCCLK and fast clock inputs.
1
UNSEC
Unsecure — If the device is unsecure, the UNSEC bit is set automatically.
0 Device is secure.
1 Device is unsecure.
Note: When UNSEC is set, the device is unsecure and the state of the secure bits in the on-chip Flash EEPROM
can be changed.
0
ERASE
Erase Flash — This bit can only be set by the dedicated ERASE_FLASH command. ERASE is unaffected by
write accesses to BDCCSR. ERASE is cleared either when the mass erase sequence is completed,
independent of the actual status of the flash array or by a soft reset.
Reading this bit indicates the status of the requested mass erase sequence.
0 No flash mass erase sequence pending completion
1 Flash mass erase sequence pending completion.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
147
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.3.2.2
BDC Control Status Register Low (BDCCSRL)
Register Address: This register is not in the device memory map. It is accessible using BDC inherent addressing commands
R
W
Reset
7
6
5
4
3
2
1
0
WAIT
STOP
RAMWF
OVRUN
NORESP
RDINV
ILLACC
ILLCMD
0
0
0
0
0
0
0
0
Figure 5-4. BDC Control Status Register Low (BDCCSRL)
Read: BDC access only.
Write: Bits [7:5], [3:0] BDC access only, restricted to flag clearing by writing a “1” to the bit position.
Write: Bit 4 never. It can only be cleared by a SYNC pulse.
If ACK handshaking is enabled then BDC commands with ACK causing a BDCCSRL[3:1] flag setting
condition also generate a long ACK pulse. Subsequent commands that are executed correctly generate a
normal ACK pulse. Subsequent commands that are not correctly executed generate a long ACK pulse. The
first ACK pulse after WAIT or STOP have been set also generates a long ACK. Subsequent ACK pulses
are normal, whilst STOP and WAIT remain set.
Long ACK pulses are not immediately generated if an overrun condition is caused by the host driving the
BKGD pin low whilst a target ACK is pending, because this would conflict with an attempted host
transmission following the BKGD edge. When a whole byte has been received following the offending
BKGD edge, the OVRUN bit is still set, forcing subsequent ACK pulses to be long.
Unimplemented BDC opcodes causing the ILLCMD bit to be set do not generate a long ACK because this
could conflict with further transmission from the host. If the ILLCMD is set for another reason, then a long
ACK is generated for the current command if it is a BDC command with ACK.
Table 5-6. BDCCSRL Field Descriptions
Field
Description
7
WAIT
WAIT Indicator Flag — Indicates that the device entered wait mode. Writing a “1” to this bit whilst in wait mode
has no effect. Writing a “1” after exiting wait mode, clears the bit.
0 Device did not enter wait mode
1 Device entered wait mode.
6
STOP
STOP Indicator Flag — Indicates that the CPU requested stop mode following a STOP instruction. Writing a
“1” to this bit whilst not in stop mode clears the bit. Writing a “1” to this bit whilst in stop mode has no effect.
This bit can only be set when the BDC is enabled.
0 Device did not enter stop mode
1 Device entered stop mode.
5
RAMWF
RAM Write Fault — Indicates an ECC double fault during a BDC write access to RAM.
Writing a “1” to this bit, clears the bit.
0 No RAM write double fault detected.
1 RAM write double fault detected.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
148
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-6. BDCCSRL Field Descriptions (continued)
Field
Description
4
OVRUN
Overrun Flag — Indicates unexpected host activity before command completion.
This occurs if a new command is received before the current command completion.
With ACK enabled this also occurs if the host drives the BKGD pin low whilst a target ACK pulse is pending
To protect internal resources from misinterpreted BDC accesses following an overrun, internal accesses are
suppressed until a SYNC clears this bit.
A SYNC clears the bit.
0 No overrun detected.
1 Overrun detected when issuing a BDC command.
3
NORESP
No Response Flag — Indicates that the BDC internal action or data access did not complete. This occurs in
the following scenarios:
a) If no free cycle for an access is found within 512 core clock cycles. This could typically happen if a code loop
without free cycles is executing with ACK enabled and STEAL clear.
b) With ACK disabled or STEAL set, when an internal access is not complete before the host starts
data/BDCCSRL retrieval or an internal write access is not complete before the host starts the next BDC
command.
c) Attempted internal memory or SYNC_PC accesses during STOP mode set NORESP if BDCCIS is clear.
In the above cases, on setting NORESP, the BDC aborts the access if permitted. (For devices supporting
EWAIT, BDC external accesses with EWAIT assertions, prevent a command from being aborted until EWAIT
is deasserted).
d) If a BACKGROUND command is issued whilst the device is in wait mode the NORESP bit is set but the
command is not aborted. The active BDM request is completed when the device leaves wait mode.
Furthermore subsequent CPU register access commands during wait mode set the NORESP bit, should it
have been cleared.
e) If a command is issued whilst awaiting return from Wait mode. This can happen when using STEP1 to step
over a CPU WAI instruction, if the CPU has not returned from Wait mode before the next BDC command is
received.
f) If STEP1 is issued with the BDC enabled as the device enters Wait mode regardless of the BDMACT state.
When NORESP is set a value of 0xEE is returned for each data byte associated with the current access.
Writing a “1” to this bit, clears the bit.
0 Internal action or data access completed.
1 Internal action or data access did not complete.
2
RDINV
Read Data Invalid Flag — Indicates invalid read data due to an ECC error during a BDC initiated read access.
The access returns the actual data read from the location.
Writing a “1” to this bit, clears the bit.
0 No invalid read data detected.
1 Invalid data returned during a BDC read access.
1
ILLACC
Illegal Access Flag — Indicates an attempted illegal access. This is set in the following cases:
When the attempted access addresses unimplemented memory
When the access attempts to write to the flash array
When a CPU register access is attempted with an invalid CRN (Section 5.4.5.1).
Illegal accesses return a value of 0xEE for each data byte
Writing a “1” to this bit, clears the bit.
0 No illegal access detected.
1 Illegal BDC access detected.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
149
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-6. BDCCSRL Field Descriptions (continued)
Field
Description
0
ILLCMD
Illegal Command Flag — Indicates an illegal BDC command. This bit is set in the following cases:
When an unimplemented BDC command opcode is received.
When a DUMP_MEM{_WS}, FILL_MEM{_WS} or READ_SAME{_WS} is attempted in an illegal sequence.
When an active BDM command is received whilst BDM is not active
When a non Always-available command is received whilst the BDC is disabled or a flash mass erase is ongoing.
When a non Always-available command is received whilst the device is secure
Read commands return a value of 0xEE for each data byte
Writing a “1” to this bit, clears the bit.
0 No illegal command detected.
1 Illegal BDC command detected.
5.4
5.4.1
Functional Description
Security
If the device resets with the system secured, the device clears the BDCCSR UNSEC bit. In the secure state
BDC access is restricted to the BDCCSR register. A mass erase can be requested using the
ERASE_FLASH command. If the mass erase is completed successfully, the device programs the security
bits to the unsecure state and sets the BDC UNSEC bit. If the mass erase is unsuccessful, the device
remains secure and the UNSEC bit is not set.
For more information regarding security, please refer to device specific security information.
5.4.2
Enabling BDC And Entering Active BDM
BDM can be activated only after being enabled. BDC is enabled by setting the ENBDC bit in the BDCCSR
register, via the single-wire interface, using the command WRITE_BDCCSR.
After being enabled, BDM is activated by one of the following1:
• The BDC BACKGROUND command
• A CPU BGND instruction
• The DBG Breakpoint mechanism
Alternatively BDM can be activated directly from reset when resetting into Special Single Chip Mode.
The BDC is ready for receiving the first command 10 core clock cycles after the deassertion of the internal
reset signal. This is delayed relative to the external pin reset as specified in the device reset documentation.
On S12Z devices an NVM initialization phase follows reset. During this phase the BDC commands
classified as always available are carried out immediately, whereas other BDC commands are subject to
delayed response due to the NVM initialization phase.
NOTE
After resetting into SSC mode, the initial PC address must be supplied by
the host using the WRITE_Rn command before issuing the GO command.
1. BDM active immediately out of special single-chip reset.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
150
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
When BDM is activated, the CPU finishes executing the current instruction. Thereafter only BDC
commands can affect CPU register contents until the BDC GO command returns from active BDM to user
code or a device reset occurs. When BDM is activated by a breakpoint, the type of breakpoint used
determines if BDM becomes active before or after execution of the next instruction.
NOTE
Attempting to activate BDM using a BGND instruction whilst the BDC is
disabled, the CPU requires clock cycles for the attempted BGND execution.
However BACKGROUND commands issued whilst the BDC is disabled
are ignored by the BDC and the CPU execution is not delayed.
5.4.3
Clock Source
The BDC clock source can be mapped to a constant frequency clock source or a PLL based fast clock. The
clock source for the BDC is selected by the CLKSW bit as shown in Figure 5-5. The BDC internal clock
is named BDCSI clock. If BDCSI clock is mapped to the BDCCLK by CLKSW then the serial interface
communication is not affected by bus/core clock frequency changes. If the BDC is mapped to BDCFCLK
then the clock is connected to a PLL derived source at device level (typically bus clock), thus can be subject
to frequency changes in application. Debugging through frequency changes requires SYNC pulses to resynchronize. The sources of BDCCLK and BDCFCLK are specified at device level.
BDC accesses of internal device resources always use the device core clock. Thus if the ACK handshake
protocol is not enabled, the clock frequency relationship must be taken into account by the host.
When changing the clock source via the CLKSW bit a minimum delay of 150 cycles at the initial clock
speed must elapse before a SYNC can be sent. This guarantees that the start of the next BDC command
uses the new clock for timing subsequent BDC communications.
BDCCLK
BDCFCLK
0
BDCSI Clock
BDC serial interface
and FSM
1
CLKSW
Core clock
BDC device resource
interface
Figure 5-5. Clock Switch
5.4.4
BDC Commands
BDC commands can be classified into three types as shown in Table 5-7.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
151
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-7. BDC Command Types
Command Type
Secure
Status
BDC
Status
Always-available
Secure or
Unsecure
Enabled or
Disabled
Non-intrusive
Active background
Unsecure
Unsecure
Enabled
Active
CPU Status
Command Set
—
•
•
•
•
Read/write access to BDCCSR
Mass erase flash memory using ERASE_FLASH
SYNC
ACK enable/disable
Code
execution
allowed
•
•
•
•
•
•
•
•
Read/write access to BDCCSR
Memory access
Memory access with status
Mass erase flash memory using ERASE_FLASH
Debug register access
BACKGROUND
SYNC
ACK enable/disable
Code
execution
halted
•
•
•
•
•
•
•
•
•
•
Read/write access to BDCCSR
Memory access
Memory access with status
Mass erase flash memory using ERASE_FLASH
Debug register access
Read or write CPU registers
Single-step the application
Exit active BDM to return to the application program (GO)
SYNC
ACK enable/disable
Non-intrusive commands are used to read and write target system memory locations and to enter active
BDM. Target system memory includes all memory and registers within the global memory map, including
external memory.
Active background commands are used to read and write all memory locations and CPU resources.
Furthermore they allow single stepping through application code and to exit from active BDM.
Non-intrusive commands can only be executed when the BDC is enabled and the device unsecure. Active
background commands can only be executed when the system is not secure and is in active BDM.
Non-intrusive commands do not require the system to be in active BDM for execution, although, they can
still be executed in this mode. When executing a non-intrusive command with the ACK pulse handshake
protocol disabled, the BDC steals the next bus cycle for the access. If an operation requires multiple cycles,
then multiple cycles can be stolen. Thus if stolen cycles are not free cycles, the application code execution
is delayed. The delay is negligible because the BDC serial transfer rate dictates that such accesses occur
infrequently.
For data read commands, the external host must wait at least 16 BDCSI clock cycles after sending the
address before attempting to obtain the read data. This is to be certain that valid data is available in the
BDC shift register, ready to be shifted out. For write commands, the external host must wait 16 bdcsi
cycles after sending the data to be written before attempting to send a new command. This is to avoid
disturbing the BDC shift register before the write has been completed. The external host must wait at least
for 16 bdcsi cycles after a control command before starting any new serial command.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
152
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
If the ACK pulse handshake protocol is enabled and STEAL is cleared, then the BDC waits for the first
free bus cycle to make a non-intrusive access. If no free bus cycle occurs within 512 core clock cycles then
the BDC aborts the access, sets the NORESP bit and uses a long ACK pulse to indicate an error condition
to the host.
Table 5-8 summarizes the BDC command set. The subsequent sections describe each command in detail
and illustrate the command structure in a series of packets, each consisting of eight bit times starting with
a falling edge. The bar across the top of the blocks indicates that the BKGD line idles in the high state. The
time for an 8-bit command is 8 × 16 target BDCSI clock cycles.
The nomenclature below is used to describe the structure of the BDC commands. Commands begin with
an 8-bit hexadecimal command code in the host-to-target direction (most significant bit first)
/
d
dack
ad24
rd8
rd16
rd24
rd32
rd64
rd.sz
wd8
wd16
wd32
wd.sz
ss
sz
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
crn
WS
=
=
separates parts of the command
delay 16 target BDCSI clock cycles (DLY)
delay (16 cycles) no ACK; or delay (=> 32 cycles) then ACK.(DACK)
24-bit memory address in the host-to-target direction
8 bits of read data in the target-to-host direction
16 bits of read data in the target-to-host direction
24 bits of read data in the target-to-host direction
32 bits of read data in the target-to-host direction
64 bits of read data in the target-to-host direction
read data, size defined by sz, in the target-to-host direction
8 bits of write data in the host-to-target direction
16 bits of write data in the host-to-target direction
32 bits of write data in the host-to-target direction
write data, size defined by sz, in the host-to-target direction
the contents of BDCCSRL in the target-to-host direction
memory operand size (00 = byte, 01 = word, 10 = long)
(sz = 11 is reserved and currently defaults to long)
core register number, 32-bit data width
command suffix signaling the operation is with status
Table 5-8. BDC Command Summary
Command
Mnemonic
Command
Classification
ACK
Command
Structure
Description
SYNC
Always
Available
N/A
N/A(1)
Request a timed reference pulse to
determine the target BDC communication
speed
ACK_DISABLE
Always
Available
No
0x03/d
Disable the communication handshake.
This command does not issue an ACK
pulse.
ACK_ENABLE
Always
Available
Yes
0x02/dack
Enable the communication handshake.
Issues an ACK pulse after the command is
executed.
BACKGROUND
Non-Intrusive
Yes
0x04/dack
Halt the CPU if ENBDC is set. Otherwise,
ignore as illegal command.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
153
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-8. BDC Command Summary (continued)
Command
Mnemonic
Command
Classification
ACK
Command
Structure
DUMP_MEM.sz
Non-Intrusive
Yes
(0x32+4 x sz)/dack/rd.sz
Dump (read) memory based on operand
size (sz). Used with READ_MEM to dump
large blocks of memory. An initial
READ_MEM is executed to set up the
starting address of the block and to retrieve
the first result. Subsequent DUMP_MEM
commands retrieve sequential operands.
DUMP_MEM.sz_WS
Non-Intrusive
No
(0x33+4 x sz)/d/ss/rd.sz
Dump (read) memory based on operand
size (sz) and report status. Used with
READ_MEM{_WS} to dump large blocks of
memory. An initial READ_MEM{_WS} is
executed to set up the starting address of
the block and to retrieve the first result.
Subsequent DUMP_MEM{_WS}
commands retrieve sequential operands.
FILL_MEM.sz
Non-Intrusive
Yes
(0x12+4 x sz)/wd.sz/dack
Fill (write) memory based on operand size
(sz). Used with WRITE_MEM to fill large
blocks of memory. An initial WRITE_MEM
is executed to set up the starting address
of the block and to write the first operand.
Subsequent FILL_MEM commands write
sequential operands.
FILL_MEM.sz_WS
Non-Intrusive
No
(0x13+4 x sz)/wd.sz/d/ss
Fill (write) memory based on operand size
(sz) and report status. Used with
WRITE_MEM{_WS} to fill large blocks of
memory. An initial WRITE_MEM{_WS} is
executed to set up the starting address of
the block and to write the first operand.
Subsequent FILL_MEM{_WS} commands
write sequential operands.
GO
Active
Background
Yes
0x08/dack
Resume CPU user code execution
GO_UNTIL(2)
Active
Background
Yes
0x0C/dack
Go to user program. ACK is driven upon
returning to active background mode.
Non-Intrusive
Yes
0x00/dack
No operation
Active
Background
Yes
(0x60+CRN)/dack/rd32
READ_MEM.sz
Non-Intrusive
Yes
(0x30+4 x sz)/ad24/dack/rd.sz Read the appropriately-sized (sz) memory
value from the location specified by the 24bit address
READ_MEM.sz_WS
Non-Intrusive
No
(0x31+4 x sz)/ad24/d/ss/rd.sz Read the appropriately-sized (sz) memory
value from the location specified by the 24bit address and report status
READ_DBGTB
Non-Intrusive
Yes
NOP
READ_Rn
(0x07)/dack/rd32/dack/rd32
Description
Read the requested CPU register
Read 64-bits of DBG trace buffer
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
154
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-8. BDC Command Summary (continued)
Command
Mnemonic
Command
Classification
ACK
Command
Structure
READ_SAME.sz
Non-Intrusive
Yes
(0x50+4 x sz)/dack/rd.sz
Read from location. An initial READ_MEM
defines the address, subsequent
READ_SAME reads return content of
same address
READ_SAME.sz_WS
Non-Intrusive
No
(0x51+4 x sz)/d/ss/rd.sz
Read from location. An initial READ_MEM
defines the address, subsequent
READ_SAME reads return content of
same address
Always
Available
No
0x2D/rd16
SYNC_PC
Non-Intrusive
Yes
0x01/dack/rd24
WRITE_MEM.sz
Non-Intrusive
Yes
(0x10+4 x
sz)/ad24/wd.sz/dack
WRITE_MEM.sz_WS
Non-Intrusive
No
Active
Background
Yes
(0x40+CRN)/wd32/dack
WRITE_BDCCSR
Always
Available
No
0x0D/wd16
ERASE_FLASH
Always
Available
No
0x95/d
READ_BDCCSR
WRITE_Rn
Description
Read the BDCCSR register
Read current PC
Write the appropriately-sized (sz) memory
value to the location specified by the 24-bit
address
(0x11+4 x sz)/ad24/wd.sz/d/ss Write the appropriately-sized (sz) memory
value to the location specified by the 24-bit
address and report status
Write the requested CPU register
Write the BDCCSR register
Mass erase internal flash
STEP1 (TRACE1)
Active
Yes
0x09/dack
Execute one CPU command.
Background
1. The SYNC command is a special operation which does not have a command code.
2. The GO_UNTIL command is identical to the GO command if ACK is not enabled.
5.4.4.1
SYNC
The SYNC command is unlike other BDC commands because the host does not necessarily know the
correct speed to use for serial communications until after it has analyzed the response to the SYNC
command.
To issue a SYNC command, the host:
1. Ensures that the BKGD pin is high for at least 4 cycles of the slowest possible BDCSI clock without
reset asserted.
2. Drives the BKGD pin low for at least 128 cycles of the slowest possible BDCSI clock.
3. Drives BKGD high for a brief speed-up pulse to get a fast rise time. (This speedup pulse is typically
one cycle of the host clock which is as fast as the maximum target BDCSI clock).
4. Removes all drive to the BKGD pin so it reverts to high impedance.
5. Listens to the BKGD pin for the sync response pulse.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
155
Chapter 5 Background Debug Controller (S12ZBDCV2)
Upon detecting the sync request from the host (which is a much longer low time than would ever occur
during normal BDC communications), the target:
1. Discards any incomplete command
2. Waits for BKGD to return to a logic high.
3. Delays 16 cycles to allow the host to stop driving the high speed-up pulse.
4. Drives BKGD low for 128 BDCSI clock cycles.
5. Drives a 1-cycle high speed-up pulse to force a fast rise time on BKGD.
6. Removes all drive to the BKGD pin so it reverts to high impedance.
7. Clears the OVRRUN flag (if set).
The host measures the low time of this 128-cycle SYNC response pulse and determines the correct speed
for subsequent BDC communications. Typically, the host can determine the correct communication speed
within a few percent of the actual target speed and the serial protocol can easily tolerate this speed error.
If the SYNC request is detected by the target, any partially executed command is discarded. This is referred
to as a soft-reset, equivalent to a timeout in the serial communication. After the SYNC response, the target
interprets the next negative edge (issued by the host) as the start of a new BDC command or the start of
new SYNC request.
A SYNC command can also be used to abort a pending ACK pulse. This is explained in Section 5.4.8.
5.4.4.2
ACK_DISABLE
Disable host/target handshake protocol
Always Available
0x03
host →
target
D
L
Y
Disables the serial communication handshake protocol. The subsequent commands, issued after the
ACK_DISABLE command, do not execute the hardware handshake protocol. This command is not
followed by an ACK pulse.
5.4.4.3
ACK_ENABLE
Enable host/target handshake protocol
Always Available
0x02
host →
target
D
A
C
K
Enables the hardware handshake protocol in the serial communication. The hardware handshake is
implemented by an acknowledge (ACK) pulse issued by the target MCU in response to a host command.
The ACK_ENABLE command is interpreted and executed in the BDC logic without the need to interface
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
156
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
with the CPU. An ACK pulse is issued by the target device after this command is executed. This command
can be used by the host to evaluate if the target supports the hardware handshake protocol. If the target
supports the hardware handshake protocol, subsequent commands are enabled to execute the hardware
handshake protocol, otherwise this command is ignored by the target. Table 5-8 indicates which
commands support the ACK hardware handshake protocol.
For additional information about the hardware handshake protocol, refer to Section 5.4.7,” and
Section 5.4.8.”
5.4.4.4
BACKGROUND
Enter active background mode (if enabled)
Non-intrusive
0x04
host →
target
D
A
C
K
Provided ENBDC is set, the BACKGROUND command causes the target MCU to enter active BDM as
soon as the current CPU instruction finishes. If ENBDC is cleared, the BACKGROUND command is
ignored.
A delay of 16 BDCSI clock cycles is required after the BACKGROUND command to allow the target
MCU to finish its current CPU instruction and enter active background mode before a new BDC command
can be accepted.
The host debugger must set ENBDC before attempting to send the BACKGROUND command the first
time. Normally the host sets ENBDC once at the beginning of a debug session or after a target system reset.
During debugging, the host uses GO commands to move from active BDM to application program
execution and uses the BACKGROUND command or DBG breakpoints to return to active BDM.
A BACKGROUND command issued during stop or wait modes cannot immediately force active BDM
because the WAI instruction does not end until an interrupt occurs. For the detailed mode dependency
description refer to Section 5.1.3.3.
The host can recognize this pending BDM request condition because both NORESP and WAIT are set, but
BDMACT is clear. Whilst in wait mode, with the pending BDM request, non-intrusive BDC commands
are allowed.
5.4.4.5
DUMP_MEM.sz, DUMP_MEM.sz_WS
DUMP_MEM.sz
Read memory specified by debug address register, then
increment address
0x32
Non-intrusive
Data[7-0]
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
157
Chapter 5 Background Debug Controller (S12ZBDCV2)
DUMP_MEM.sz
host →
target
D
A
C
K
0x36
host →
target
D
A
C
K
0x3A
host →
target
D
A
C
K
target →
host
Data[15-8]
Data[7-0]
target →
host
target →
host
Data[31-24]
Data[23-16]
Data[15-8]
Data[7-0]
target →
host
target →
host
target →
host
target →
host
DUMP_MEM.sz_WS
Read memory specified by debug address register with status,
then increment address
0x33
host →
target
BDCCSRL
D
L
Y
0x37
host →
target
D
L
Y
0x3B
host →
target
D
L
Y
target →
host
Non-intrusive
Data[7-0]
target →
host
BDCCSRL
Data[15-8]
Data[7-0]
target →
host
target →
host
BDCCSRL
Data[31-24]
Data23-16]
Data[15-8]
target →
host
target →
host
target →
host
target →
host
target →
host
Data[7-0]
target →
host
DUMP_MEM{_WS} is used with the READ_MEM{_WS} command to access large blocks of memory.
An initial READ_MEM{_WS} is executed to set-up the starting address of the block and to retrieve the
first result. The DUMP_MEM{_WS} command retrieves subsequent operands. The initial address is
incremented by the operand size (1, 2, or 4) and saved in a temporary register. Subsequent
DUMP_MEM{_WS} commands use this address, perform the memory read, increment it by the current
operand size, and store the updated address in the temporary register. If the with-status option is specified,
the BDCCSRL status byte is returned before the read data. This status byte reflects the state after the
memory read was performed. If enabled, an ACK pulse is driven before the data bytes are transmitted. The
effect of the access size and alignment on the next address to be accessed is explained in more detail in
Section 5.4.5.2”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
158
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
NOTE
DUMP_MEM{_WS} is a valid command only when preceded by SYNC,
NOP, READ_MEM{_WS}, or another DUMP_MEM{_WS} command.
Otherwise, an illegal command response is returned, setting the ILLCMD
bit. NOP can be used for inter-command padding without corrupting the
address pointer.
The size field (sz) is examined each time a DUMP_MEM{_WS} command is processed, allowing the
operand size to be dynamically altered. The examples show the DUMP_MEM.B{_WS},
DUMP_MEM.W{_WS} and DUMP_MEM.L{_WS} commands.
5.4.4.6
FILL_MEM.sz, FILL_MEM.sz_WS
FILL_MEM.sz
Write memory specified by debug address register, then
increment address
Non-intrusive
0x12
Data[7-0]
host →
target
host →
target
0x16
Data[15-8]
Data[7-0]
host →
target
host →
target
host →
target
0x1A
Data[31-24]
Data[23-16]
Data[15-8]
Data[7-0]
host →
target
host →
target
host →
target
host →
target
host →
target
D
A
C
K
D
A
C
K
D
A
C
K
FILL_MEM.sz_WS
Write memory specified by debug address register with
status, then increment address
0x13
Data[7-0]
host →
target
host →
target
0x17
Data[15-8]
Data[7-0]
host →
target
host →
target
host →
target
Non-intrusive
BDCCSRL
D
L
Y
target →
host
BDCCSRL
D
L
Y
target →
host
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
159
Chapter 5 Background Debug Controller (S12ZBDCV2)
FILL_MEM.sz_WS
0x1B
Data[31-24]
Data[23-16]
Data[15-8]
Data[7-0]
host →
target
host →
target
host →
target
host →
target
host →
target
BDCCSRL
D
L
Y
target →
host
FILL_MEM{_WS} is used with the WRITE_MEM{_WS} command to access large blocks of memory.
An initial WRITE_MEM{_WS} is executed to set up the starting address of the block and write the first
datum. If an initial WRITE_MEM{_WS} is not executed before the first FILL_MEM{_WS}, an illegal
command response is returned. The FILL_MEM{_WS} command stores subsequent operands. The initial
address is incremented by the operand size (1, 2, or 4) and saved in a temporary register. Subsequent
FILL_MEM{_WS} commands use this address, perform the memory write, increment it by the current
operand size, and store the updated address in the temporary register. If the with-status option is specified,
the BDCCSRL status byte is returned after the write data. This status byte reflects the state after the
memory write was performed. If enabled an ACK pulse is generated after the internal write access has been
completed or aborted. The effect of the access size and alignment on the next address to be accessed is
explained in more detail in Section 5.4.5.2”
NOTE
FILL_MEM{_WS} is a valid command only when preceded by SYNC,
NOP, WRITE_MEM{_WS}, or another FILL_MEM{_WS} command.
Otherwise, an illegal command response is returned, setting the ILLCMD
bit. NOP can be used for inter command padding without corrupting the
address pointer.
The size field (sz) is examined each time a FILL_MEM{_WS} command is processed, allowing the
operand size to be dynamically altered. The examples show the FILL_MEM.B{_WS},
FILL_MEM.W{_WS} and FILL_MEM.L{_WS} commands.
5.4.4.7
GO
Go
Non-intrusive
0x08
host →
target
D
A
C
K
This command is used to exit active BDM and begin (or resume) execution of CPU application code. The
CPU pipeline is flushed and refilled before normal instruction execution resumes. Prefetching begins at the
current address in the PC. If any register (such as the PC) is altered by a BDC command whilst in BDM,
the updated value is used when prefetching resumes. If enabled, an ACK is driven on exiting active BDM.
If a GO command is issued whilst the BDM is inactive, an illegal command response is returned and the
ILLCMD bit is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
160
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.4.4.8
GO_UNTIL
Go Until
Active Background
0x0C
D
A
C
K
host →
target
This command is used to exit active BDM and begin (or resume) execution of application code. The CPU
pipeline is flushed and refilled before normal instruction execution resumes. Prefetching begins at the
current address in the PC. If any register (such as the PC) is altered by a BDC command whilst in BDM,
the updated value is used when prefetching resumes.
After resuming application code execution, if ACK is enabled, the BDC awaits a return to active BDM
before driving an ACK pulse. timeouts do not apply when awaiting a GO_UNTIL command ACK.
If a GO_UNTIL is not acknowledged then a SYNC command must be issued to end the pending
GO_UNTIL.
If a GO_UNTIL command is issued whilst BDM is inactive, an illegal command response is returned and
the ILLCMD bit is set.
If ACK handshaking is disabled, the GO_UNTIL command is identical to the GO command.
5.4.4.9
NOP
No operation
Active Background
0x00
D
A
C
K
host →
target
NOP performs no operation and may be used as a null command where required.
5.4.4.10
READ_Rn
Read CPU register
Active Background
0x60+CRN
host →
target
Data [31-24] Data [23-16]
D
A
C
K
target →
host
target →
host
Data [15-8]
Data [7-0]
target →
host
target →
host
This command reads the selected CPU registers and returns the 32-bit result. Accesses to CPU registers
are always 32-bits wide, regardless of implemented register width. Bytes that are not implemented return
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
161
Chapter 5 Background Debug Controller (S12ZBDCV2)
zero. The register is addressed through the CPU register number (CRN). See Section 5.4.5.1 for the CRN
address decoding. If enabled, an ACK pulse is driven before the data bytes are transmitted.
If the device is not in active BDM, this command is illegal, the ILLCMD bit is set and no access is
performed.
5.4.4.11
READ_MEM.sz, READ_MEM.sz_WS
READ_MEM.sz
Read memory at the specified address
0x30
Address[23-0]
host →
target
host →
target
0x34
Address[23-0]
host →
target
host →
target
Non-intrusive
Data[7-0]
D
A
C
K
target →
host
Data[15-8]
Data[7-0]
target →
host
target →
host
Data[31-24]
Data[23-16]
Data[15-8]
Data[7-0]
target →
host
target →
host
target →
host
target →
host
D
A
C
K
0x38
Address[23-0]
host →
target
host →
target
D
A
C
K
READ_MEM.sz_WS
Read memory at the specified address with status
0x31
Address[23-0]
host →
target
host →
target
0x35
Address[23-0]
host →
target
host →
target
0x39
Address[23-0]
host →
target
host →
target
BDCCSRL
D
L
Y
D
L
Y
D
L
Y
target →
host
Non-intrusive
Data[7-0]
target →
host
BDCCSRL
Data [15-8]
Data [7-0]
target →
host
target →
host
BDCCSRL
Data[31-24]
Data[23-16]
Data [15-8]
target →
host
target →
host
target →
host
target →
host
target →
host
Data [7-0]
target →
host
Read data at the specified memory address. The address is transmitted as three 8-bit packets (msb to lsb)
immediately after the command.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
162
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
The hardware forces low-order address bits to zero longword accesses to ensure these accesses are on 0modulo-size alignments. Byte alignment details are described in Section 5.4.5.2”. If the with-status option
is specified, the BDCCSR status byte is returned before the read data. This status byte reflects the state
after the memory read was performed. If enabled, an ACK pulse is driven before the data bytes are
transmitted.
The examples show the READ_MEM.B{_WS}, READ_MEM.W{_WS} and READ_MEM.L{_WS}
commands.
5.4.4.12
READ_DBGTB
Read DBG trace buffer
TB Line [31- TB Line [23- TB Line [15- TB Line [724]
16]
8]
0]
0x07
host →
target
Non-intrusive
D
A
C
K
target →
host
target →
host
target →
host
target →
host
TB Line [63- TB Line [55- TB Line [47- TB Line [3956]
48]
40]
32]
D
A
C
K
target →
host
target →
host
target →
host
target →
host
This command is only available on devices, where the DBG module includes a trace buffer. Attempted use
of this command on devices without a traace buffer return 0x00.
Read 64 bits from the DBG trace buffer. Refer to the DBG module description for more detailed
information. If enabled an ACK pulse is generated before each 32-bit longword is ready to be read by the
host. After issuing the first ACK a timeout is still possible whilst accessing the second 32-bit longword,
since this requires separate internal accesses. The first 32-bit longword corresponds to trace buffer line
bits[31:0]; the second to trace buffer line bits[63:32]. If ACK handshaking is disabled, the host must wait
16 clock cycles (DLY) after completing the first 32-bit read before starting the second 32-bit read.
5.4.4.13
READ_SAME.sz, READ_SAME.sz_WS
READ_SAME
Read same location specified by previous READ_MEM{_WS}
0x54
host →
target
D
A
C
K
Data[15-8]
Data[7-0]
target →
host
target →
host
Non-intrusive
READ_SAME_WS
Read same location specified by previous READ_MEM{_WS}
Non-intrusive
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
163
Chapter 5 Background Debug Controller (S12ZBDCV2)
READ_SAME_WS
0x55
host →
target
D
L
Y
BDCCSRL
Data [15-8]
target →
host
target →
host
Data [7-0]
target →
host
Read from location defined by the previous READ_MEM. The previous READ_MEM command defines
the address, subsequent READ_SAME commands return contents of same address. The example shows
the sequence for reading a 16-bit word size. Byte alignment details are described in Section 5.4.5.2”. If
enabled, an ACK pulse is driven before the data bytes are transmitted.
NOTE
READ_SAME{_WS} is a valid command only when preceded by SYNC,
NOP, READ_MEM{_WS}, or another READ_SAME{_WS} command.
Otherwise, an illegal command response is returned, setting the ILLCMD
bit. NOP can be used for inter-command padding without corrupting the
address pointer.
5.4.4.14
READ_BDCCSR
Read BDCCSR Status Register
0x2D
host →
target
D
L
Y
Always Available
BDCCSR
[15:8]
BDCCSR
[7-0]
target
→ host
target
→ host
Read the BDCCSR status register. This command can be executed in any mode.
5.4.4.15
SYNC_PC
Sample current PC
0x01
host →
target
D
A
C
K
Non-intrusive
PC
data[23–16]
PC
data[15–8]
PC
data[7–0]
target →
host
target →
host
target →
host
This command returns the 24-bit CPU PC value to the host. Unsuccessful SYNC_PC accesses return 0xEE
for each byte. If enabled, an ACK pulse is driven before the data bytes are transmitted. The value of 0xEE
is returned if a timeout occurs, whereby NORESP is set. This can occur if the CPU is executing the WAI
instruction, or the STOP instruction with BDCCIS clear, or if a CPU access is delayed by EWAIT. If the
CPU is executing the STOP instruction and BDCCIS is set, then SYNC_PC returns the PC address of the
instruction following STOP in the code listing.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
164
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
This command can be used to dynamically access the PC for performance monitoring as the execution of
this command is considerably less intrusive to the real-time operation of an application than a
BACKGROUND/read-PC/GO command sequence. Whilst the BDC is not in active BDM, SYNC_PC
returns the PC address of the instruction currently being executed by the CPU. In active BDM, SYNC_PC
returns the address of the next instruction to be executed on returning from active BDM. Thus following a
write to the PC in active BDM, a SYNC_PC returns that written value.
5.4.4.16
WRITE_MEM.sz, WRITE_MEM.sz_WS
WRITE_MEM.sz
Write memory at the specified address
Non-intrusive
0x10
Address[23-0]
Data[7–0]
host →
target
host → target
host →
target
0x14
Address[23-0]
Data[15–8]
Data[7–0]
host →
target
host → target
host →
target
host →
target
0x18
Address[23-0]
host →
target
host → target
D
A
C
K
D
A
C
K
Data[31–24] Data[23–16]
host →
target
Data[15–8]
Data[7–0]
host →
target
host →
target
host →
target
D
A
C
K
WRITE_MEM.sz_WS
Write memory at the specified address with status
Non-intrusive
0x11
Address[23-0]
Data[7–0]
host →
target
host →
target
host →
target
0x15
Address[23-0]
Data[15–8]
Data[7–0]
host →
target
host →
target
host →
target
host →
target
0x19
Address[23-0]
host →
target
host →
target
BDCCSRL
D
L
Y
target →
host
Data[31–24] Data[23–16]
host →
target
host →
target
BDCCSRL
D
L
Y
target →
host
Data[15–8]
Data[7–0]
host →
target
host →
target
BDCCSRL
D
L
Y
target →
host
Write data to the specified memory address. The address is transmitted as three 8-bit packets (msb to lsb)
immediately after the command.
If the with-status option is specified, the status byte contained in BDCCSRL is returned after the write data.
This status byte reflects the state after the memory write was performed. The examples show the
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
165
Chapter 5 Background Debug Controller (S12ZBDCV2)
WRITE_MEM.B{_WS}, WRITE_MEM.W{_WS}, and WRITE_MEM.L{_WS} commands. If enabled
an ACK pulse is generated after the internal write access has been completed or aborted.
The hardware forces low-order address bits to zero longword accesses to ensure these accesses are on 0modulo-size alignments. Byte alignment details are described in Section 5.4.5.2”.
5.4.4.17
WRITE_Rn
Write general-purpose CPU register
0x40+CRN
Active Background
Data [31–24] Data [23–16] Data [15–8]
host →
target
host →
target
host →
target
host →
target
Data [7–0]
host →
target
D
A
C
K
If the device is in active BDM, this command writes the 32-bit operand to the selected CPU generalpurpose register. See Section 5.4.5.1 for the CRN details. Accesses to CPU registers are always 32-bits
wide, regardless of implemented register width. If enabled an ACK pulse is generated after the internal
write access has been completed or aborted.
If the device is not in active BDM, this command is rejected as an illegal operation, the ILLCMD bit is set
and no operation is performed.
5.4.4.18
WRITE_BDCCSR
Write BDCCSR
Always Available
0x0D
host →
target
BDCCSR
Data [15-8]
BDCCSR
Data [7-0]
host →
target
host →
target
D
L
Y
16-bit write to the BDCCSR register. No ACK pulse is generated. Writing to this register can be used to
configure control bits or clear flag bits. Refer to the register bit descriptions.
5.4.4.19
ERASE_FLASH
Erase FLASH
Always Available
0x95
host →
target
D
L
Y
Mass erase the internal flash. This command can always be issued. On receiving this command twice in
succession, the BDC sets the ERASE bit in BDCCSR and requests a flash mass erase. Any other BDC
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
166
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
command following a single ERASE_FLASH initializes the sequence, such that thereafter the
ERASE_FLASH must be applied twice in succession to request a mass erase. If 512 BDCSI clock cycles
elapse between the consecutive ERASE_FLASH commands then a timeout occurs, which forces a soft
reset and initializes the sequence. The ERASE bit is cleared when the mass erase sequence has been
completed. No ACK is driven.
During the mass erase operation, which takes many clock cycles, the command status is indicated by the
ERASE bit in BDCCSR. Whilst a mass erase operation is ongoing, Always-available commands can be
issued. This allows the status of the erase operation to be polled by reading BDCCSR to determine when
the operation is finished.
The status of the flash array can be verified by subsequently reading the flash error flags to determine if the
erase completed successfully.
ERASE_FLASH can be aborted by a SYNC pulse forcing a soft reset.
NOTE: Device Bus Frequency Considerations
The ERASE_FLASH command requires the default device bus clock
frequency after reset. Thus the bus clock frequency must not be changed
following reset before issuing an ERASE_FLASH command.
5.4.4.20
STEP1
Step1
Active Background
0x09
host →
target
D
A
C
K
This command is used to step through application code. In active BDM this command executes the next
CPU instruction in application code. If enabled an ACK is driven.
If a STEP1 command is issued and the CPU is not halted, the command is ignored.
Using STEP1 to step through a CPU WAI instruction is explained in Section 5.1.3.3.2.
5.4.5
BDC Access Of Internal Resources
Unsuccessful read accesses of internal resources return a value of 0xEE for each data byte. This enables a
debugger to recognize a potential error, even if neither the ACK handshaking protocol nor a status
command is currently being executed. The value of 0xEE is returned in the following cases.
• Illegal address access, whereby ILLACC is set
• Invalid READ_SAME or DUMP_MEM sequence
• Invalid READ_Rn command (BDM inactive or CRN incorrect)
• Internal resource read with timeout, whereby NORESP is set
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
167
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.4.5.1
BDC Access Of CPU Registers
The CRN field of the READ_Rn and WRITE_Rn commands contains a pointer to the CPU registers. The
mapping of CRN to CPU registers is shown in Table 5-9. Accesses to CPU registers are always 32-bits
wide, regardless of implemented register width. This means that the BDC data transmission for these
commands is 32-bits long. The valid bits of the transfer are listed in the Valid Data Bits column. The other
bits of the transmission are redundant.
Attempted accesses of CPU registers using a CRN of 0xD,0xE or 0xF is invalid, returning the value 0xEE
for each byte and setting the ILLACC bit.
Table 5-9. CPU Register Number (CRN) Mapping
CPU Register
Valid Data Bits
Command
Opcode
Command
Opcode
D0
[7:0]
WRITE_D0
0x40
READ_D0
0x60
5.4.5.2
D1
[7:0]
WRITE_D1
0x41
READ_D1
0x61
D2
[15:0]
WRITE_D2
0x42
READ_D2
0x62
D3
[15:0]
WRITE_D3
0x43
READ_D3
0x63
D4
[15:0]
WRITE_D4
0x44
READ_D4
0x64
D5
[15:0]
WRITE_D5
0x45
READ_D5
0x65
D6
[31:0]
WRITE_D6
0x46
READ_D6
0x66
D7
[31:0]
WRITE_D7
0x47
READ_D7
0x67
X
[23:0]
WRITE_X
0x48
READ_X
0x68
Y
[23:0]
WRITE_Y
0x49
READ_Y
0x69
SP
[23:0]
WRITE_SP
0x4A
READ_SP
0x6A
PC
[23:0]
WRITE_PC
0x4B
READ_PC
0x6B
CCR
[15:0]
WRITE_CCR
0x4C
READ_CCR
0x6C
BDC Access Of Device Memory Mapped Resources
The device memory map is accessed using READ_MEM, DUMP_MEM, WRITE_MEM, FILL_MEM
and READ_SAME, which support different access sizes, as explained in the command descriptions.
When an unimplemented command occurs during a DUMP_MEM, FILL_MEM or READ_SAME
sequence, then that sequence is ended.
Illegal read accesses return a value of 0xEE for each byte. After an illegal access FILL_MEM and
READ_SAME commands are not valid, and it is necessary to restart the internal access sequence with
READ_MEM or WRITE_MEM. An illegal access does not break a DUMP_MEM sequence. After read
accesses that cause the RDINV bit to be set, DUMP_MEM and READ_SAME commands are valid, it is
not necessary to restart the access sequence with a READ_MEM.
The hardware forces low-order address bits to zero for longword accesses to ensure these accesses are
realigned to 0-modulo-size alignments.
Word accesses map to 2-bytes from within a 4-byte field as shown in Table 5-10. Thus if address bits [1:0]
are both logic “1” the access is realigned so that it does not straddle the 4-byte boundary but accesses data
from within the addressed 4-byte field.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
168
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
Table 5-10. Field Location to Byte Access Mapping
Address[1:0]
Access Size
00
01
10
11
00
32-bit
Data[31:24]
Data[23:16]
Data [15:8]
Data [7:0]
01
32-bit
Data[31:24]
Data[23:16]
Data [15:8]
Data [7:0]
Realigned
10
32-bit
Data[31:24]
Data[23:16]
Data [15:8]
Data [7:0]
Realigned
11
32-bit
Data[31:24]
Data[23:16]
Data [15:8]
Data [7:0]
Realigned
00
16-bit
Data [15:8]
Data [7:0]
01
16-bit
10
16-bit
Data [15:8]
Data [7:0]
11
16-bit
Data [15:8]
Data [7:0]
00
8-bit
01
8-bit
10
8-bit
11
8-bit
Data [15:8]
Note
Data [7:0]
Realigned
Data [7:0]
Data [7:0]
Data [7:0]
Data [7:0]
Denotes byte that is not transmitted
5.4.5.2.1
FILL_MEM and DUMP_MEM Increments and Alignment
FILL_MEM and DUMP_MEM increment the previously accessed address by the previous access size to
calculate the address of the current access. On misaligned longword accesses, the address bits [1:0] are
forced to zero, therefore the following FILL_MEM or DUMP_MEM increment to the first address in the
next 4-byte field. This is shown in Table 5-11, the address of the first DUMP_MEM.32 following
READ_MEM.32 being calculated from 0x004000+4.
When misaligned word accesses are realigned, then the original address (not the realigned address) is
incremented for the following FILL_MEM, DUMP_MEM command.
Misaligned word accesses can cause the same locations to be read twice as shown in rows 6 and 7. The
hardware ensures alignment at an attempted misaligned word access across a 4-byte boundary, as shown
in row 7. The following word access in row 8 continues from the realigned address of row 7.
d
Table 5-11. Consecutive Accesses With Variable Size
Row
Command
Address
Address[1:0]
00
01
10
11
1
READ_MEM.32
0x004003
11
Accessed
Accessed
Accessed
Accessed
2
DUMP_MEM.32
0x004004
00
Accessed
Accessed
Accessed
Accessed
3
DUMP_MEM.16
0x004008
00
Accessed
Accessed
4
DUMP_MEM.16
0x00400A
10
Accessed
Accessed
5
DUMP_MEM.08
0x00400C
00
6
DUMP_MEM.16
0x00400D
01
7
DUMP_MEM.16
0x00400E
10
8
DUMP_MEM.16
0x004010
01
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
169
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.4.5.2.2
READ_SAME Effects Of Variable Access Size
READ_SAME uses the unadjusted address given in the previous READ_MEM command as a base
address for subsequent READ_SAME commands. When the READ_MEM and READ_SAME size
parameters differ then READ_SAME uses the original base address buts aligns 32-bit and 16-bit accesses,
where those accesses would otherwise cross the aligned 4-byte boundary. Table 5-12 shows some
examples of this.
d
Table 5-12. Consecutive READ_SAME Accesses With Variable Size
Row
5.4.6
Command
Base Address
00
01
10
11
1
READ_MEM.32
0x004003
Accessed
Accessed
Accessed
Accessed
2
READ_SAME.32
—
Accessed
Accessed
Accessed
Accessed
3
READ_SAME.16
—
Accessed
Accessed
4
READ_SAME.08
—
5
READ_MEM.08
0x004000
Accessed
6
READ_SAME.08
—
Accessed
7
READ_SAME.16
—
Accessed
Accessed
8
READ_SAME.32
—
Accessed
Accessed
Accessed
Accessed
Accessed
9
READ_MEM.08
0x004002
Accessed
10
READ_SAME.08
—
Accessed
11
READ_SAME.16
—
Accessed
Accessed
12
READ_SAME.32
—
Accessed
Accessed
13
READ_MEM.08
0x004003
Accessed
14
READ_SAME.08
—
Accessed
15
READ_SAME.16
—
16
READ_SAME.32
—
17
READ_MEM.16
18
READ_SAME.08
19
20
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
0x004001
Accessed
Accessed
—
Accessed
READ_SAME.16
—
Accessed
Accessed
READ_SAME.32
—
Accessed
Accessed
21
READ_MEM.16
0x004003
22
READ_SAME.08
—
23
READ_SAME.16
—
24
READ_SAME.32
—
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
Accessed
BDC Serial Interface
The BDC communicates with external devices serially via the BKGD pin. During reset, this pin is a mode
select input which selects between normal and special modes of operation. After reset, this pin becomes
the dedicated serial interface pin for the BDC.
The BDC serial interface uses an internal clock source, selected by the CLKSW bit in the BDCCSR
register. This clock is referred to as the target clock in the following explanation.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
170
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
The BDC serial interface uses a clocking scheme in which the external host generates a falling edge on the
BKGD pin to indicate the start of each bit time. This falling edge is sent for every bit whether data is
transmitted or received. Data is transferred most significant bit (MSB) first at 16 target clock cycles per
bit. The interface times out if during a command 512 clock cycles occur between falling edges from the
host. The timeout forces the current command to be discarded.
The BKGD pin is a pseudo open-drain pin and has a weak on-chip active pull-up that is enabled at all
times. It is assumed that there is an external pull-up and that drivers connected to BKGD do not typically
drive the high level. Since R-C rise time could be unacceptably long, the target system and host provide
brief drive-high (speedup) pulses to drive BKGD to a logic 1. The source of this speedup pulse is the host
for transmit cases and the target for receive cases.
The timing for host-to-target is shown in Figure 5-6 and that of target-to-host in Figure 5-7 and
Figure 5-8. All cases begin when the host drives the BKGD pin low to generate a falling edge. Since the
host and target operate from separate clocks, it can take the target up to one full clock cycle to recognize
this edge; this synchronization uncertainty is illustrated in Figure 5-6. The target measures delays from this
perceived start of the bit time while the host measures delays from the point it actually drove BKGD low
to start the bit up to one target clock cycle earlier. Synchronization between the host and target is
established in this manner at the start of every bit time.
Figure 5-6 shows an external host transmitting a logic 1 and transmitting a logic 0 to the BKGD pin of a
target system. The host is asynchronous to the target, so there is up to a one clock-cycle delay from the
host-generated falling edge to where the target recognizes this edge as the beginning of the bit time. Ten
target clock cycles later, the target senses the bit level on the BKGD pin. Internal glitch detect logic
requires the pin be driven high no later than eight target clock cycles after the falling edge for a logic 1
transmission.
Since the host drives the high speedup pulses in these two cases, the rising edges look like digitally driven
signals.
BDCSI clock
(TARGET MCU)
HOST
TRANSMIT 1
HOST
TRANSMIT 0
10 CYCLES
SYNCHRONIZATION
UNCERTAINTY
EARLIEST START
OF NEXT BIT
TARGET SENSES BIT LEVEL
PERCEIVED START
OF BIT TIME
Figure 5-6. BDC Host-to-Target Serial Bit Timing
Figure 5-7 shows the host receiving a logic 1 from the target system. The host holds the BKGD pin low
long enough for the target to recognize it (at least two target clock cycles). The host must release the low
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
171
Chapter 5 Background Debug Controller (S12ZBDCV2)
drive at the latest after 6 clock cycles, before the target drives a brief high speedup pulse seven target clock
cycles after the perceived start of the bit time. The host should sample the bit level about 10 target clock
cycles after it started the bit time.
BDCSI clock
(TARGET MCU)
HOST DRIVE
TO BKGD PIN
TARGET MCU
SPEEDUP PULSE
HIGH-IMPEDANCE
HIGH-IMPEDANCE
HIGH-IMPEDANCE
PERCEIVED START
OF BIT TIME
R-C RISE
BKGD PIN
10 CYCLES
10 CYCLES
EARLIEST START
OF NEXT BIT
HOST SAMPLES BKGD PIN
Figure 5-7. BDC Target-to-Host Serial Bit Timing (Logic 1)
Figure 5-8 shows the host receiving a logic 0 from the target. The host initiates the bit time but the target
finishes it. Since the target wants the host to receive a logic 0, it drives the BKGD pin low for 13 target
clock cycles then briefly drives it high to speed up the rising edge. The host samples the bit level about 10
target clock cycles after starting the bit time.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
172
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
BDCSI clock
(TARGET MCU)
HOST DRIVE
TO BKGD PIN
HIGH-IMPEDANCE
SPEEDUP
PULSE
TARGET MCU
DRIVE AND
SPEED-UP PULSE
PERCEIVED START
OF BIT TIME
BKGD PIN
10 CYCLES
EARLIEST START
OF NEXT BIT
10 CYCLES
HOST SAMPLES BKGD PIN
Figure 5-8. BDC Target-to-Host Serial Bit Timing (Logic 0)
5.4.7
Serial Interface Hardware Handshake (ACK Pulse) Protocol
BDC commands are processed internally at the device core clock rate. Since the BDCSI clock can be
asynchronous relative to the bus frequency, a handshake protocol is provided so the host can determine
when an issued command has been executed. This section describes the hardware handshake protocol.
The hardware handshake protocol signals to the host controller when a BDC command has been executed
by the target. This protocol is implemented by a low pulse (16 BDCSI clock cycles) followed by a brief
speedup pulse on the BKGD pin, generated by the target MCU when a command, issued by the host, has
been successfully executed (see Figure 5-9). This pulse is referred to as the ACK pulse. After the ACK
pulse has finished, the host can start the bit retrieval if the last issued command was a read command, or
start a new command if the last command was a write command or a control command.
BDCSI clock
(TARGET MCU)
HIGH-IMPEDANCE
16 CYCLES
TARGET
TRANSMITS
ACK PULSE
HIGH-IMPEDANCE
32 CYCLES
SPEED UP PULSE
MINIMUM DELAY
FROM THE BDC COMMAND
BKGD PIN
EARLIEST
START OF
NEXT BIT
16th CYCLE OF THE
LAST COMMAND BIT
Figure 5-9. Target Acknowledge Pulse (ACK)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
173
Chapter 5 Background Debug Controller (S12ZBDCV2)
The handshake protocol is enabled by the ACK_ENABLE command. The BDC sends an ACK pulse when
the ACK_ENABLE command has been completed. This feature can be used by the host to evaluate if the
target supports the hardware handshake protocol. If an ACK pulse is issued in response to this command,
the host knows that the target supports the hardware handshake protocol.
Unlike the normal bit transfer, where the host initiates the transmission by issuing a negative edge on the
BKGD pin, the serial interface ACK handshake pulse is initiated by the target MCU by issuing a negative
edge on the BKGD pin. Figure 5-9 specifies the timing when the BKGD pin is being driven. The host must
follow this timing constraint in order to avoid the risk of an electrical conflict at the BKGD pin.
When the handshake protocol is enabled, the STEAL bit in BDCCSR selects if bus cycle stealing is used
to gain immediate access. If STEAL is cleared, the BDC is configured for low priority bus access using
free cycles, without stealing cycles. This guarantees that BDC accesses remain truly non-intrusive to not
affect the system timing during debugging. If STEAL is set, the BDC gains immediate access, if necessary
stealing an internal bus cycle.
NOTE
If bus steals are disabled then a loop with no free cycles cannot allow access.
In this case the host must recognize repeated NORESP messages and then
issue a BACKGROUND command to stop the target and access the data.
Figure 5-10 shows the ACK handshake protocol without steal in a command level timing diagram. The
READ_MEM.B command is used as an example. First, the 8-bit command code is sent by the host,
followed by the address of the memory location to be read. The target BDC decodes the command. Then
an internal access is requested by the BDC. When a free bus cycle occurs the READ_MEM.B operation
is carried out. If no free cycle occurs within 512 core clock cycles then the access is aborted, the NORESP
flag is set and the target generates a Long-ACK pulse.
Having retrieved the data, the BDC issues an ACK pulse to the host controller, indicating that the addressed
byte is ready to be retrieved. After detecting the ACK pulse, the host initiates the data read part of the
command.
TARGET
BKGD PIN
READ_MEM.B
ADDRESS[23–0]
HOST
HOST
BYTE IS
RETRIEVED
TARGET
NEW BDC COMMAND
HOST
TARGET
BDC ISSUES THE
ACK PULSE (NOT TO SCALE)
BDC DECODES
THE COMMAND
MCU EXECUTES THE
READ_MEM.B
COMMAND
Figure 5-10. Handshake Protocol at Command Level
Alternatively, setting the STEAL bit configures the handshake protocol to make an immediate internal
access, independent of free bus cycles.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
174
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
The ACK handshake protocol does not support nested ACK pulses. If a BDC command is not
acknowledged by an ACK pulse, the host needs to abort the pending command first in order to be able to
issue a new BDC command. The host can decide to abort any possible pending ACK pulse in order to be
sure a new command can be issued. Therefore, the protocol provides a mechanism in which a command,
and its corresponding ACK, can be aborted.
Commands With-Status do not generate an ACK, thus if ACK is enabled and a With-Status command is
issued, the host must use the 512 cycle timeout to calculate when the data is ready for retrieval.
5.4.7.1
Long-ACK Hardware Handshake Protocol
If a command results in an error condition, whereby a BDCCSRL flag is set, then the target generates a
“Long-ACK” low pulse of 64 BDCSI clock cycles, followed by a brief speed pulse. This indicates to the
host that an error has occurred. The host can subsequently read BDCCSR to determine the type of error.
Whether normal ACK or Long-ACK, the ACK pulse is not issued earlier than 32 BDCSI clock cycles after
the BDC command was issued. The end of the BDC command is assumed to be the 16th BDCSI clock
cycle of the last bit. The 32 cycle minimum delay differs from the 16 cycle delay time with ACK disabled.
If a BDC access request does not gain access within 512 core clock cycles, the request is aborted, the
NORESP flag is set and a Long-ACK pulse is transmitted to indicate an error case.
Following a STOP or WAI instruction, if the BDC is enabled, the first ACK, following stop or wait mode
entry is a long ACK to indicate an exception.
5.4.8
Hardware Handshake Abort Procedure
The abort procedure is based on the SYNC command. To abort a command that has not responded with an
ACK pulse, the host controller generates a sync request (by driving BKGD low for at least 128 BDCSI
clock cycles and then driving it high for one BDCSI clock cycle as a speedup pulse). By detecting this long
low pulse in the BKGD pin, the target executes the SYNC protocol, see Section 5.4.4.1”, and assumes that
the pending command and therefore the related ACK pulse are being aborted. After the SYNC protocol
has been completed the host is free to issue new BDC commands.
The host can issue a SYNC close to the 128 clock cycles length, providing a small overhead on the pulse
length to assure the sync pulse is not misinterpreted by the target. See Section 5.4.4.1”.
Figure 5-11 shows a SYNC command being issued after a READ_MEM, which aborts the READ_MEM
command. Note that, after the command is aborted a new command is issued by the host.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
175
Chapter 5 Background Debug Controller (S12ZBDCV2)
READ_MEM.B CMD
IS ABORTED BY THE SYNC REQUEST
(NOT TO SCALE)
BKGD PIN
READ_MEM.B
HOST
ADDRESS[23-0]
SYNC RESPONSE
FROM THE TARGET
(NOT TO SCALE)
READ_BDCCSR
TARGET
HOST
TARGET
NEW BDC COMMAND
HOST
TARGET
NEW BDC COMMAND
BDC DECODES
AND TRYS TO EXECUTE
Figure 5-11. ACK Abort Procedure at the Command Level (Not To Scale)
Figure 5-12 shows a conflict between the ACK pulse and the SYNC request pulse. The target is executing
a pending BDC command at the exact moment the host is being connected to the BKGD pin. In this case,
an ACK pulse is issued simultaneously to the SYNC command. Thus there is an electrical conflict between
the ACK speedup pulse and the SYNC pulse. As this is not a probable situation, the protocol does not
prevent this conflict from happening.
AT LEAST 128 CYCLES
BDCSI clock
(TARGET MCU)
ACK PULSE
TARGET MCU
DRIVES TO
BKGD PIN
HIGH-IMPEDANCE
ELECTRICAL CONFLICT
HOST
DRIVES SYNC
TO BKGD PIN
SPEEDUP PULSE
HOST AND TARGET
DRIVE TO BKGD PIN
HOST SYNC REQUEST PULSE
BKGD PIN
16 CYCLES
Figure 5-12. ACK Pulse and SYNC Request Conflict
5.4.9
Hardware Handshake Disabled (ACK Pulse Disabled)
The default state of the BDC after reset is hardware handshake protocol disabled. It can also be disabled
by the ACK_DISABLE BDC command. This provides backwards compatibility with the existing host
devices which are not able to execute the hardware handshake protocol. For host devices that support the
hardware handshake protocol, true non-intrusive debugging and error flagging is offered.
If the ACK pulse protocol is disabled, the host needs to use the worst case delay time at the appropriate
places in the protocol.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
176
Freescale Semiconductor
Chapter 5 Background Debug Controller (S12ZBDCV2)
If the handshake protocol is disabled, the access is always independent of free cycles, whereby BDC has
higher priority than CPU. Since at least 2 bytes (command byte + data byte) are transferred over BKGD
the maximum intrusiveness is only once every few hundred cycles.
After decoding an internal access command, the BDC then awaits the next internal core clock cycle. The
relationship between BDCSI clock and core clock must be considered. If the host retrieves the data
immediately, then the BDCSI clock frequency must not be more than 4 times the core clock frequency, in
order to guarantee that the BDC gains bus access within 16 the BDCSI cycle DLY period following an
access command. If the BDCSI clock frequency is more than 4 times the core clock frequency, then the
host must use a suitable delay time before retrieving data (see 5.5.1/5-178). Furthermore, for stretched read
accesses to external resources via a device expanded bus (if implemented) the potential extra stretch cycles
must be taken into consideration before attempting to obtain read data.
If the access does not succeed before the host starts data retrieval then the NORESP flag is set but the
access is not aborted. The NORESP state can be used by the host to recognize an unexpected access
conflict due to stretched expanded bus accesses. Although the NORESP bit is set when an access does not
succeed before the start of data retrieval, the access may succeed in following bus cycles if the internal
access has already been initiated.
5.4.10
Single Stepping
When a STEP1 command is issued to the BDC in active BDM, the CPU executes a single instruction in
the user code and returns to active BDM. The STEP1 command can be issued repeatedly to step through
the user code one instruction at a time.
If an interrupt is pending when a STEP1 command is issued, the interrupt stacking operation occurs but
no user instruction is executed. In this case the stacking counts as one instruction. The device re-enters
active BDM with the program counter pointing to the first instruction in the interrupt service routine.
When stepping through the user code, the execution of the user code is done step by step but peripherals
are free running. Some peripheral modules include a freeze feature, whereby their clocks are halted when
the device enters active BDM. Timer modules typically include the freeze feature. Serial interface modules
typically do not include the freeze feature. Hence possible timing relations between CPU code execution
and occurrence of events of peripherals no longer exist.
If the handshake protocol is enabled and BDCCIS is set then stepping over the STOP instruction causes
the Long-ACK pulse to be generated and the BDCCSR STOP flag to be set. When stop mode is exited due
to an interrupt the device enters active BDM and the PC points to the start of the corresponding interrupt
service routine. Stepping can be continued.
Stepping over a WAI instruction, the STEP1 command cannot be finished because active BDM cannot be
entered after CPU starts to execute the WAI instruction.
Stepping over the WAI instruction causes the BDCCSR WAIT and NORESP flags to be set and, if the
handshake protocol is enabled, then the Long-ACK pulse is generated. Then the device enters wait mode,
clears the BDMACT bit and awaits an interrupt to leave wait mode. In this time non-intrusive BDC
commands are possible, although the STEP1 has actually not finished. When an interrupt occurs the device
leaves wait mode, enters active BDM and the PC points to the start of the corresponding interrupt service
routine. A further ACK related to stepping over the WAI is not generated.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
177
Chapter 5 Background Debug Controller (S12ZBDCV2)
5.4.11
Serial Communication Timeout
The host initiates a host-to-target serial transmission by generating a falling edge on the BKGD pin. If
BKGD is kept low for more than 128 target clock cycles, the target understands that a SYNC command
was issued. In this case, the target waits for a rising edge on BKGD in order to answer the SYNC request
pulse. When the BDC detects the rising edge a soft reset is generated, whereby the current BDC command
is discarded. If the rising edge is not detected, the target keeps waiting forever without any timeout limit.
If a falling edge is not detected by the target within 512 clock cycles since the last falling edge, a timeout
occurs and the current command is discarded without affecting memory or the operating mode of the
MCU. This is referred to as a soft-reset. This timeout also applies if 512 cycles elapse between 2
consecutive ERASE_FLASH commands. The soft reset is disabled whilst the internal flash mass erase
operation is pending completion.
timeouts are also possible if a BDC command is partially issued, or data partially retrieved. Thus if a time
greater than 512 BDCSI clock cycles is observed between two consecutive negative edges, a soft-reset
occurs causing the partially received command or data retrieved to be discarded. The next negative edge
at the BKGD pin, after a soft-reset has occurred, is considered by the target as the start of a new BDC
command, or the start of a SYNC request pulse.
5.5
5.5.1
Application Information
Clock Frequency Considerations
Read commands without status and without ACK must consider the frequency relationship between
BDCSI and the internal core clock. If the core clock is slow, then the internal access may not have been
carried out within the standard 16 BDCSI cycle delay period (DLY). The host must then extend the DLY
period or clock frequencies accordingly. Taking internal clock domain synchronizers into account, the
minimum number of BDCSI periods required for the DLY is expressed by:
#DLY > 3(f(BDCSI clock) / f(core clock)) + 4
and the minimum core clock frequency with respect to BDCSI clock frequency is expressed by
Minimum f(core clock) = (3/(#DLY cycles -4))f(BDCSI clock)
For the standard 16 period DLY this yields f(core clock)>= (1/4)f(BDCSI clock)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
178
Freescale Semiconductor
Chapter 6
S12Z Debug (S12ZDBGV2) Module
Table 6-1. Revision History Table
Revision
Number
Revision
Date
2.04
19.APR.2012
2.05
23.MAY.2012
General
2.06
10.SEP.2012
Section 6.4.5.3
2.07
18.OCT.2012
General
2.08
16.NOV.2012
Section 6.5.1
2.09
19.DEC.2012
General
2.10
28.JUN.2013
General
Section 6.3.2.21
Section 6.3.2.1
Section 6.3.2.5
2.11
15.JUL.2013
Section 6.3.2
6.1
Sections
Affected
Description Of Changes
Section 6.4.5.2.1 Documented DBGTB read dependency on PROFILE bit
Formatting changes to support DBGV3 from single source
Added NOTE about PC trace buffer entries for Comp D timestamps
Formatting corrections
Modified step over breakpoint information
Formatting corrections
Emphasized need to set TSOURCE for tracing or profiling
Corrected DBGCDM write access dependency
Corrrected ARM versus PTACT dependency
Modified DBGTBH read access dependencies
Added explicit names to state control register bit fields
Introduction
The DBG module provides on-chip breakpoints and trace buffer with flexible triggering capability to allow
non-intrusive debug of application software. The DBG module is optimized for the S12Z architecture and
allows debugging of CPU module operations.
Typically the DBG module is used in conjunction with the BDC module, whereby the user configures the
DBG module for a debugging session over the BDC interface. Once configured the DBG module is armed
and the device leaves active BDM returning control to the user program, which is then monitored by the
DBG module. Alternatively the DBG module can be configured over a serial interface using SWI routines.
6.1.1
Glossary
Table 6-2. Glossary Of Terms
Term
Definition
COF
Change Of Flow.
Change in the program flow due to a conditional branch, indexed jump or interrupt
PC
Program Counter
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
179
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-2. Glossary Of Terms
Term
Definition
BDM
Background Debug Mode.
In this mode CPU application code execution is halted.
Execution of BDC “active BDM” commands is possible.
BDC
WORD
Data Line
CPU
Trigger
Background Debug Controller
6.1.2
16-bit data entity
64-bit data entity
S12Z CPU module
A trace buffer input that triggers tracing start, end or mid point
Overview
The comparators monitor the bus activity of the CPU. A single comparator match or a series of matches
can trigger bus tracing and/or generate breakpoints. A state sequencer determines if the correct series of
matches occurs. Similarly an external event can trigger bus tracing and/or generate breakpoints.
The trace buffer is visible through a 2-byte window in the register address map and can be read out using
standard 16-bit word reads.
6.1.3
•
•
•
•
•
Features
Four comparators (A, B, C, and D)
— Comparators A and C compare the full address bus and full 32-bit data bus
— Comparators A and C feature a data bus mask register
— Comparators B and D compare the full address bus only
— Each comparator can be configured to monitor PC addresses or addresses of data accesses
— Each comparator can select either read or write access cycles
— Comparator matches can force state sequencer state transitions
Three comparator modes
— Simple address/data comparator match mode
— Inside address range mode, Addmin ≤ Address ≤ Addmax
— Outside address range match mode, Address < Addmin or Address > Addmax
State sequencer control
— State transitions forced by comparator matches
— State transitions forced by software write to TRIG
— State transitions forced by an external event
The following types of breakpoints
— CPU breakpoint entering active BDM on breakpoint (BDM)
— CPU breakpoint executing SWI on breakpoint (SWI)
Trace control
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
180
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
•
•
— Tracing session triggered by state sequencer
— Begin, End, and Mid alignment of tracing to trigger
Four trace modes
— Normal: change of flow (COF) PC information is stored (see Section 6.4.5.2.1) for change of
flow definition.
— Loop1: same as Normal but inhibits consecutive duplicate source address entries
— Detail: address and data for all read/write access cycles are stored
— Pure PC: All program counter addresses are stored.
2 Pin (data and clock) profiling interface
— Output of code flow information
6.1.4
Modes of Operation
The DBG module can be used in all MCU functional modes.
The DBG module can issue breakpoint requests to force the device to enter active BDM or an SWI ISR.
The BDC BACKGROUND command is also handled by the DBG to force the device to enter active BDM.
When the device enters active BDM through a BACKGROUND command with the DBG module armed,
the DBG remains armed.
6.1.5
Block Diagram
B
EXTERNAL EVENT
TRIG
COMPARATOR A
COMPARATOR B
COMPARATOR C
COMPARATOR D
MATCH0
COMPARATOR
MATCH CONTROL
CPU BUS
BUS INTERFACE
REGISTERS
MATCH1
STATE SEQUENCER
AND
EVENT CONTROL
BREAKPOINT
REQUESTS
MATCH2
MATCH3
TRACE
CONTROL
TRIGGER
TRACE BUFFER
PROFILE
OUTPUT
READ TRACE DATA (DBG READ DATA BUS)
Figure 6-1. Debug Module Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
181
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.2
6.2.1
External Signal Description
External Event Input
The DBG module features an external event input signal, DBGEEV. The mapping of this signal to a device
pin is specified in the device specific documentation. This function can be enabled and configured by the
EEVE field in the DBGC1 control register. This signal is input only and allows an external event to force
a state sequencer transition, or trace buffer entry, or to gate trace buffer entries. With the external event
function enabled, a falling edge at the external event pin constitutes an event. Rising edges have no effect.
If configured for gating trace buffer entries, then a low level at the pin allows entries, but a high level
suppresses entries. The maximum frequency of events is half the internal core bus frequency. The function
is explained in the EEVE field description.
NOTE
Due to input pin synchronization circuitry, the DBG module sees external
events 2 bus cycles after they occur at the pin. Thus an external event
occurring less than 2 bus cycles before arming the DBG module is perceived
to occur whilst the DBG is armed.
When the device is in stop mode the synchronizer clocks are disabled and
the external events are ignored.
6.2.2
Profiling Output
The DBG module features a profiling data output signal PDO. The mapping of this signal to a device pin
is specified in the device specific documentation. The device pin is enabled for profiling by setting the
PDOE bit. The profiling function can be enabled by the PROFILE bit in the DBGTCRL control register.
This signal is output only and provides a serial, encoded data stream that can be used by external
development tools to reconstruct the internal CPU code flow, as specified in Section 6.4.6. During code
profiling the device PDOCLK output is used as a clock signal.
6.3
6.3.1
Memory Map and Registers
Module Memory Map
A summary of the registers associated with the DBG module is shown in Figure 6-2. Detailed descriptions
of the registers and bits are given in the subsections that follow.
Address
Name
Bit 7
0x0100
DBGC1
R
W
0x0101
DBGC2
R
W
ARM
0
6
0
TRIG
0
5
4
3
2
reserved
BDMBP
BRKCPU
reserved
0
0
CDCM
1
Bit 0
EEVE
ABCM
Figure 6-2. Quick Reference to DBG Registers
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
182
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Address
0x0102
Name
Bit 7
R
DBGTCRH
reserved
W
6
5
TSOURCE
4
3
TRANGE
2
1
TRCMOD
0x0103
DBGTCRL
R
W
0
0
0
0
0x0104
DBGTB
R
W
Bit 15
Bit 14
Bit 13
0x0105
DBGTB
R
W
Bit 7
Bit 6
Bit 5
0x0106
DBGCNT
R
W
0
0x0107
DBGSCR1
R
W
C3SC1
C3SC0
C2SC1
C2SC0
0x0108
DBGSCR2
R
W
C3SC1
C3SC0
C2SC1
0x0109
DBGSCR3
R
W
C3SC1
C3SC0
0x010A
DBGEFR
0x010B
DBGSR
R
W
0x010C0x010F
Reserved
0x0110
Bit 0
TALIGN
DSTAMP
PDOE
PROFILE
STAMP
Bit 12
Bit 11
Bit 10
Bit 9
Bit 8
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
C1SC1
C1SC0
C0SC1
C0SC0
C2SC0
C1SC1
C1SC0
C0SC1
C0SC0
C2SC1
C2SC0
C1SC1
C1SC0
C0SC1
C0SC0
TRIGF
0
EEVF
ME3
ME2
ME1
ME0
TBF
0
0
PTACT
0
SSF2
SSF1
SSF0
R
W
0
0
0
0
0
0
0
0
DBGACTL
R
W
0
NDB
INST
RW
RWE
reserved
COMPE
0x01110x0114
Reserved
R
W
0
0
0
0
0
0
0
0x0115
DBGAAH
R
W
DBGAA[23:16]
0x0116
DBGAAM
R
W
DBGAA[15:8]
0x0117
DBGAAL
R
W
DBGAA[7:0]
0x0118
DBGAD0
R
W
Bit 31
30
29
28
27
26
25
Bit 24
0x0119
DBGAD1
R
W
Bit 23
22
21
20
19
18
17
Bit 16
0x011A
DBGAD2
R
W
Bit 15
14
13
12
11
10
9
Bit 8
CNT
R PTBOVF
W
0
0
Figure 6-2. Quick Reference to DBG Registers
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
183
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Address
Name
Bit 7
6
5
4
3
2
1
Bit 0
Bit 7
6
5
4
3
2
1
Bit 0
0x011B
DBGAD3
R
W
0x011C
DBGADM0
R
W
Bit 31
30
29
28
27
26
25
Bit 24
0x011D
DBGADM1
R
W
Bit 23
22
21
20
19
18
17
Bit 16
0x011E
DBGADM2
R
W
Bit 15
14
13
12
11
10
9
Bit 8
0x011F
DBGADM3
R
W
Bit 7
6
5
4
3
2
1
Bit 0
0x0120
DBGBCTL
R
W
0
0
RW
RWE
reserved
COMPE
0x01210x0124
Reserved
R
W
0
0
0
0
0
0
0x0125
DBGBAH
R
W
DBGBA[23:16]
0x0126
DBGBAM
R
W
DBGBA[15:8]
0x0127
DBGBAL
R
W
DBGBA[7:0]
0x01280x012F
Reserved
R
W
0
0
0
0
0
0x0130
DBGCCTL
R
W
0
RW
RWE
reserved
COMPE
0x01310x0134
Reserved
R
W
0
0
0
0
0
0x0135
DBGCAH
R
W
DBGCA[23:16]
0x0136
DBGCAM
R
W
DBGCA[15:8]
0x0137
DBGCAL
R
W
DBGCA[7:0]
0x0138
DBGCD0
R
W
Bit 31
30
29
28
27
26
25
Bit 24
0x0139
DBGCD1
R
W
Bit 23
22
21
20
19
18
17
Bit 16
0x013A
DBGCD2
R
W
Bit 15
14
13
12
11
10
9
Bit 8
INST
0
0
0
NDB
INST
0
0
0
0
0
0
0
Figure 6-2. Quick Reference to DBG Registers
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
184
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Address
Name
Bit 7
6
5
4
3
2
1
Bit 0
Bit 7
6
5
4
3
2
1
Bit 0
0x013B
DBGCD3
R
W
0x013C
DBGCDM0
R
W
Bit 31
30
29
28
27
26
25
Bit 24
0x013D
DBGCDM1
R
W
Bit 23
22
21
20
19
18
17
Bit 16
0x013E
DBGCDM2
R
W
Bit 15
14
13
12
11
10
9
Bit 8
0x013F
DBGCDM3
R
W
Bit 7
6
5
4
3
2
1
Bit 0
0x0140
DBGDCTL
R
W
0
0
RW
RWE
reserved
COMPE
0x01410x0144
Reserved
R
W
0
0
0
0
0
0
0x0145
DBGDAH
R
W
DBGDA[23:16]
0x0146
DBGDAM
R
W
DBGDA[15:8]
0x0147
DBGDAL
R
W
DBGDA[7:0]
0x01480x017F
Reserved
R
W
0
0
0
0
0
INST
0
0
0
0
0
0
Figure 6-2. Quick Reference to DBG Registers
6.3.2
Register Descriptions
This section consists of the DBG register descriptions in address order. When ARM is set in DBGC1, the
only bits in the DBG module registers that can be written are ARM, and TRIG
6.3.2.1
Debug Control Register 1 (DBGC1)
Address: 0x0100
7
0x0100
Reset
ARM
0
6
0
TRIG
0
5
4
3
2
reserved
BDMBP
BRKCPU
reserved
0
0
0
0
1
0
EEVE
0
0
Figure 6-3. Debug Control Register (DBGC1)
Read: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
185
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Write: Bit 7 Anytime with the exception that it cannot be set if PTACT is set. An ongoing profiling session
must be finished before DBG can be armed again.
Bit 6 can be written anytime but always reads back as 0.
Bits 5:0 anytime DBG is not armed and PTACT is clear.
NOTE
On a write access to DBGC1 and simultaneous hardware disarm from an
internal event, the hardware disarm has highest priority, clearing the ARM
bit and generating a breakpoint, if enabled.
NOTE
When disarming the DBG by clearing ARM with software, the contents of
bits[5:0] are not affected by the write, since up until the write operation,
ARM = 1 preventing these bits from being written. These bits must be
cleared using a second write if required.
Table 6-3. DBGC1 Field Descriptions
Field
Description
7
ARM
Arm Bit — The ARM bit controls whether the DBG module is armed. This bit can be set and cleared by register
writes and is automatically cleared when the state sequencer returns to State0 on completing a debugging
session. On setting this bit the state sequencer enters State1.
0 Debugger disarmed. No breakpoint is generated when clearing this bit by software register writes.
1 Debugger armed
6
TRIG
Immediate Trigger Request Bit — This bit when written to 1 requests an immediate transition to final state
independent of comparator status. This bit always reads back a 0. Writing a 0 to this bit has no effect.
0 No effect.
1 Force state sequencer immediately to final state.
4
BDMBP
Background Debug Mode Enable — This bit determines if a CPU breakpoint causes the system to enter
Background Debug Mode (BDM) or initiate a Software Interrupt (SWI). If this bit is set but the BDC is not enabled,
then no breakpoints are generated.
0 Breakpoint to Software Interrupt if BDM inactive. Otherwise no breakpoint.
1 Breakpoint to BDM, if BDC enabled. Otherwise no breakpoint.
3
BRKCPU
CPU Breakpoint Enable — The BRKCPU bit controls whether the debugger requests a breakpoint to CPU upon
transitions to State0. If tracing is enabled, the breakpoint is generated on completion of the tracing session. If
tracing is not enabled, the breakpoint is generated immediately. Please refer to Section 6.4.7 for further details.
0 Breakpoints disabled
1 Breakpoints enabled
1–0
EEVE
External Event Enable — The EEVE bits configure the external event function. Table 6-4 explains the bit
encoding.
Table 6-4. EEVE Bit Encoding
EEVE
Description
00
External event function disabled
01
External event forces a trace buffer entry if tracing is enabled
10
External event is mapped to the state sequencer, replacing comparator channel 3
11
External event pin gates trace buffer entries
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
186
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.3.2.2
Debug Control Register2 (DBGC2)
Address: 0x0101
R
7
6
5
4
0
0
0
0
0
0
0
3
0
1
CDCM
W
Reset
2
0
0
ABCM
0
0
0
= Unimplemented or Reserved
Figure 6-4. Debug Control Register2 (DBGC2)
Read: Anytime.
Write: Anytime the module is disarmed and PTACT is clear.
This register configures the comparators for range matching.
Table 6-5. DBGC2 Field Descriptions
Field
Description
3–2
CDCM[1:0]
C and D Comparator Match Control — These bits determine the C and D comparator match mapping as
described in Table 6-6.
1–0
ABCM[1:0]
A and B Comparator Match Control — These bits determine the A and B comparator match mapping as
described in Table 6-7.
Table 6-6. CDCM Encoding
CDCM
Description
00
Match2 mapped to comparator C match....... Match3 mapped to comparator D match.
01
Match2 mapped to comparator C/D inside range....... Match3 disabled.
10
Match2 mapped to comparator C/D outside range....... Match3 disabled.
11
Reserved(1)
1. Currently defaults to Match2 mapped to inside range: Match3 disabled.
Table 6-7. ABCM Encoding
ABCM
Description
00
Match0 mapped to comparator A match....... Match1 mapped to comparator B match.
01
Match0 mapped to comparator A/B inside range....... Match1 disabled.
10
Match0 mapped to comparator A/B outside range....... Match1 disabled.
11
Reserved(1)
1. Currently defaults to Match0 mapped to inside range: Match1 disabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
187
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.3.2.3
Debug Trace Control Register High (DBGTCRH)
Address: 0x0102
R
W
Reset
7
6
5
reserved
TSOURCE
0
0
4
3
TRANGE
0
2
1
TRCMOD
0
0
0
TALIGN
0
0
0
Figure 6-5. Debug Trace Control Register (DBGTCRH)
Read: Anytime.
Write: Anytime the module is disarmed and PTACT is clear.
WARNING
DBGTCR[7] is reserved. Setting this bit maps the tracing to an unimplemented bus, thus
preventing proper operation.
This register configures the trace buffer for tracing and profiling.
Table 6-8. DBGTCRH Field Descriptions
Field
6
TSOURCE
Description
Trace Control Bits — The TSOURCE enables the tracing session.
0 No CPU tracing/profiling selected
1 CPU tracing/profiling selected
5–4
TRANGE
Trace Range Bits — The TRANGE bits allow filtering of trace information from a selected address range when
tracing from the CPU in Detail mode. These bits have no effect in other tracing modes. To use a comparator for
range filtering, the corresponding COMPE bit must remain cleared. If the COMPE bit is set then the comparator
is used to generate events and the TRANGE bits have no effect. See Table 6-9 for range boundary definition.
3–2
TRCMOD
Trace Mode Bits — See Section 6.4.5.2 for detailed Trace Mode descriptions. In Normal Mode, change of flow
information is stored. In Loop1 Mode, change of flow information is stored but redundant entries into trace
memory are inhibited. In Detail Mode, address and data for all memory and register accesses is stored. See
Table 6-10.
1–0
TALIGN
Trigger Align Bits — These bits control whether the trigger is aligned to the beginning, end or the middle of a
tracing or profiling session. See Table 6-11.
Table 6-9. TRANGE Trace Range Encoding
TRANGE
Tracing Range
00
Trace from all addresses (No filter)
01
Trace only in address range from $00000 to Comparator D
10
Trace only in address range from Comparator C to $FFFFFF
11
Trace only in range from Comparator C to Comparator D
Table 6-10. TRCMOD Trace Mode Bit Encoding
TRCMOD
Description
00
Normal
01
Loop1
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
188
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-10. TRCMOD Trace Mode Bit Encoding
TRCMOD
Description
10
Detail
11
Pure PC
Table 6-11. TALIGN Trace Alignment Encoding
TALIGN
Description
00
Trigger ends data trace
01
Trigger starts data trace
10
32 lines of data trace follow trigger
11(1)
1. Tracing/Profiling disabled.
6.3.2.4
Reserved
Debug Trace Control Register Low (DBGTCRL)
Address: 0x0103
R
7
6
5
4
0
0
0
0
0
0
0
0
W
Reset
3
2
1
0
DSTAMP
PDOE
PROFILE
STAMP
0
0
0
0
= Unimplemented or Reserved
Figure 6-6. Debug Trace Control Register Low (DBGTCRL)
Read: Anytime.
Write: Anytime the module is disarmed and PTACT is clear.
This register configures the profiling and timestamp features
Table 6-12. DBGTCRL Field Descriptions
Field
3
DSTAMP
2
PDOE
1
PROFILE
Description
Comparator D Timestamp Enable — This bit, when set, enables Comparator D matches to generate
timestamps in Detail, Normal and Loop1 trace modes.
0 Comparator D match does not generate timestamp
1 Comparator D match generates timestamp if timestamp function is enabled
Profile Data Out Enable — This bit, when set, configures the device profiling pins for profiling.
0 Device pins not configured for profiling
1 Device pins configured for profiling
Profile Enable — This bit, when set, enables the profile function, whereby a subsequent arming of the DBG
activates profiling.
When PROFILE is set, the TRCMOD bits are ignored.
0 Profile function disabled
1 Profile function enabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
189
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-12. DBGTCRL Field Descriptions (continued)
Field
Description
0
STAMP
Timestamp Enable — This bit, when set, enables the timestamp function. The timestamp function adds a
timestamp to each trace buffer entry in Detail, Normal and Loop1 trace modes.
0 Timestamp function disabled
1 Timestamp function enabled
6.3.2.5
Debug Trace Buffer Register (DBGTB)
Address: 0x0104, 0x0105
15
R
W
14
13
12
11
10
9
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9
8
7
6
5
4
3
2
1
0
Bit 8
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
POR
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Other
Resets
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Figure 6-7. Debug Trace Buffer Register (DBGTB)
Read: Only when unlocked AND not armed and the TSOURCE bit is set, otherwise an error code (0xEE)
is returned. Only aligned word read operations are supported. Misaligned word reads or byte reads return
the error code 0xEE for each byte. The PROFILE bit must be clear to read profiling data,
Write: Aligned word writes when the DBG is disarmed and both PTACT and PROFILE are clear unlock
the trace buffer for reading but do not affect trace buffer contents.
Table 6-13. DBGTB Field Descriptions
Field
Description
15–0
Bit[15:0]
Trace Buffer Data Bits — The Trace Buffer Register is a window through which the lines of the trace buffer may
be read 16 bits at a time. Each valid read of DBGTB increments an internal trace buffer pointer which points to
the next address to be read. When the ARM bit is written to 1 the trace buffer is locked to prevent reading. The
trace buffer can only be unlocked for reading by writing to DBGTB with an aligned word write when the module
is disarmed. The DBGTB register can be read only as an aligned word. Byte reads or misaligned access of these
registers returns 0xEE and does not increment the trace buffer pointer. Similarly word reads while the debugger
is armed or trace buffer is locked return 0xEEEE. The POR state is undefined Other resets do not affect the trace
buffer contents.
6.3.2.6
Debug Count Register (DBGCNT)
Address: 0x0106
7
R
6
5
4
0
3
2
1
0
—
0
—
0
—
0
CNT
W
Reset
POR
0
0
—
0
—
0
—
0
—
0
= Unimplemented or Reserved
Figure 6-8. Debug Count Register (DBGCNT)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
190
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Read: Anytime.
Write: Never.
Table 6-14. DBGCNT Field Descriptions
Field
Description
6–0
CNT[6:0]
Count Value — The CNT bits [6:0] indicate the number of valid data lines stored in the trace buffer. Table 6-15
shows the correlation between the CNT bits and the number of valid data lines in the trace buffer. When the CNT
rolls over to zero, the TBF bit in DBGSR is set. Thereafter incrementing of CNT continues if configured for endalignment or mid-alignment.
The DBGCNT register is cleared when ARM in DBGC1 is written to a one. The DBGCNT register is cleared by
power-on-reset initialization but is not cleared by other system resets. If a reset occurs during a debug session,
the DBGCNT register still indicates after the reset, the number of valid trace buffer entries stored before the reset
occurred. The DBGCNT register is not decremented when reading from the trace buffer.
Table 6-15. CNT Decoding Table
6.3.2.7
TBF (DBGSR)
CNT[6:0]
Description
0
0000000
No data valid
0
0000001
32 bits of one line valid
0
0000010
0000100
0000110
..
1111100
1 line valid
2 lines valid
3 lines valid
..
62 lines valid
0
1111110
63 lines valid
1
0000000
64 lines valid; if using Begin trigger alignment,
ARM bit is cleared and the tracing session ends.
1
0000010
..
1111110
64 lines valid,
oldest data has been overwritten by most recent data
Debug State Control Register 1 (DBGSCR1)
Address: 0x0107
R
W
Reset
7
6
5
4
3
2
1
0
C3SC1
C3SC0
C2SC1
C2SC0
C1SC1
C1SC0
C0SC1
C0SC0
0
0
0
0
0
0
0
0
Figure 6-9. Debug State Control Register 1 (DBGSCR1)
Read: Anytime.
Write: If DBG is not armed and PTACT is clear.
The state control register 1 selects the targeted next state whilst in State1. The matches refer to the outputs
of the comparator match control logic as depicted in Figure 6-1 and described in Section 6.3.2.12”.
Comparators must be enabled by setting the comparator enable bit in the associated DBGXCTL control
register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
191
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-16. DBGSCR1 Field Descriptions
Field
Description
1–0
C0SC[1:0]
Channel 0 State Control.
These bits select the targeted next state whilst in State1 following a match0.
3–2
C1SC[1:0]
Channel 1 State Control.
These bits select the targeted next state whilst in State1 following a match1.
5–4
C2SC[1:0]
Channel 2 State Control.
These bits select the targeted next state whilst in State1 following a match2.
7–6
C3SC[1:0]
Channel 3 State Control.
If EEVE !=10, these bits select the targeted next state whilst in State1 following a match3.
If EEVE = 10, these bits select the targeted next state whilst in State1 following an external event.
Table 6-17. State1 Match State Sequencer Transitions
CxSC[1:0]
Function
00
Match has no effect
01
Match forces sequencer to State2
10
Match forces sequencer to State3
11
Match forces sequencer to Final State
In the case of simultaneous matches, the match on the higher channel number (3...0) has priority.
6.3.2.8
Debug State Control Register 2 (DBGSCR2)
Address: 0x0108
R
W
Reset
7
6
5
4
3
2
1
0
C3SC1
C3SC0
C2SC1
C2SC0
C1SC1
C1SC0
C0SC1
C0SC0
0
0
0
0
0
0
0
0
Figure 6-10. Debug State Control Register 2 (DBGSCR2)
Read: Anytime.
Write: If DBG is not armed and PTACT is clear.
The state control register 2 selects the targeted next state whilst in State2. The matches refer to the outputs
of the comparator match control logic as depicted in Figure 6-1 and described in Section 6.3.2.12”.
Comparators must be enabled by setting the comparator enable bit in the associated DBGXCTL control
register.
Table 6-18. DBGSCR2 Field Descriptions
Field
Description
1–0
C0SC[1:0]
Channel 0 State Control.
These bits select the targeted next state whilst in State2 following a match0.
3–2
C1SC[1:0]
Channel 1 State Control.
These bits select the targeted next state whilst in State2 following a match1.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
192
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-18. DBGSCR2 Field Descriptions (continued)
Field
Description
5–4
C2SC[1:0]
Channel 2 State Control.
These bits select the targeted next state whilst in State2 following a match2.
7–6
C3SC[1:0]
Channel 3 State Control.
If EEVE !=10, these bits select the targeted next state whilst in State2 following a match3.
If EEVE =10, these bits select the targeted next state whilst in State2 following an external event.
Table 6-19. State2 Match State Sequencer Transitions
CxSC[1:0]
Function
00
Match has no effect
01
Match forces sequencer to State1
10
Match forces sequencer to State3
11
Match forces sequencer to Final State
In the case of simultaneous matches, the match on the higher channel number (3...0) has priority.
6.3.2.9
Debug State Control Register 3 (DBGSCR3)
Address: 0x0109
R
W
Reset
7
6
5
4
3
2
1
0
C3SC1
C3SC0
C2SC1
C2SC0
C1SC1
C1SC0
C0SC1
C0SC0
0
0
0
0
0
0
0
0
Figure 6-11. Debug State Control Register 3 (DBGSCR3)
Read: Anytime.
Write: If DBG is not armed and PTACT is clear.
The state control register three selects the targeted next state whilst in State3. The matches refer to the
outputs of the comparator match control logic as depicted in Figure 6-1 and described in Section 6.3.2.12”.
Comparators must be enabled by setting the comparator enable bit in the associated DBGxCTL control
register.
Table 6-20. DBGSCR3 Field Descriptions
Field
Description
1–0
C0SC[1:0]
Channel 0 State Control.
These bits select the targeted next state whilst in State3 following a match0.
3–2
C1SC[1:0]
Channel 1 State Control.
These bits select the targeted next state whilst in State3 following a match1.
5–4
C2SC[1:0]
Channel 2 State Control.
These bits select the targeted next state whilst in State3 following a match2.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
193
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-20. DBGSCR3 Field Descriptions (continued)
Field
7–6
C3SC[1:0]
Description
Channel 3 State Control.
If EEVE !=10, these bits select the targeted next state whilst in State3 following a match3.
If EEVE =10, these bits select the targeted next state whilst in State3 following an external event.
Table 6-21. State3 Match State Sequencer Transitions
CxSC[1:0]
Function
00
Match has no effect
01
Match forces sequencer to State1
10
Match forces sequencer to State2
11
Match forces sequencer to Final State
In the case of simultaneous matches, the match on the higher channel number (3....0) has priority.
6.3.2.10
Debug Event Flag Register (DBGEFR)
Address: 0x010A
R
7
6
5
4
3
2
1
0
PTBOVF
TRIGF
0
EEVF
ME3
ME2
ME1
ME0
0
0
0
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 6-12. Debug Event Flag Register (DBGEFR)
Read: Anytime.
Write: Never
DBGEFR contains flag bits each mapped to events whilst armed. Should an event occur, then the
corresponding flag is set. With the exception of TRIGF, the bits can only be set when the ARM bit is set.
The TRIGF bit is set if a TRIG event occurs when ARM is already set, or if the TRIG event occurs
simultaneous to setting the ARM bit.All other flags can only be cleared by arming the DBG module. Thus
the contents are retained after a debug session for evaluation purposes.
A set flag does not inhibit the setting of other flags.
Table 6-22. DBGEFR Field Descriptions
Field
7
PTBOVF
6
TRIGF
Description
Profiling Trace Buffer Overflow Flag — Indicates the occurrence of a trace buffer overflow event during a
profiling session.
0 No trace buffer overflow event
1 Trace buffer overflow event
TRIG Flag — Indicates the occurrence of a TRIG event during the debug session.
0 No TRIG event
1 TRIG event
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
194
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-22. DBGEFR Field Descriptions
Field
4
EEVF
3–0
ME[3:0]
6.3.2.11
Description
External Event Flag — Indicates the occurrence of an external event during the debug session.
0 No external event
1 External event
Match Event[3:0]— Indicates a comparator match event on the corresponding comparator channel.
Debug Status Register (DBGSR)
Address: 0x010B
R
7
6
5
4
3
2
1
0
TBF
0
0
PTACT
0
SSF2
SSF1
SSF0
—
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
POR
= Unimplemented or Reserved
Figure 6-13. Debug Status Register (DBGSR)
Read: Anytime.
Write: Never.
Table 6-23. DBGSR Field Descriptions
Field
Description
7
TBF
Trace Buffer Full — The TBF bit indicates that the trace buffer has been filled with data since it was last armed.
If this bit is set, then all trace buffer lines contain valid data, regardless of the value of DBGCNT bits CNT[6:0].
The TBF bit is cleared when ARM in DBGC1 is written to a one. The TBF is cleared by the power on reset
initialization. Other system generated resets have no affect on this bit
4
PTACT
Profiling Transmission Active — The PTACT bit, when set, indicates that the profiling transmission is still
active. When clear, PTACT then profiling transmission is not active. The PTACT bit is set when profiling begins
with the first PTS format entry to the trace buffer. The PTACT bit is cleared when the profiling transmission ends.
2–0
SSF[2:0]
State Sequencer Flag Bits — The SSF bits indicate the current State Sequencer state. During a debug session
on each transition to a new state these bits are updated. If the debug session is ended by software clearing the
ARM bit, then these bits retain their value to reflect the last state of the state sequencer before disarming. If a
debug session is ended by an internal event, then the state sequencer returns to State0 and these bits are
cleared to indicate that State0 was entered during the session. On arming the module the state sequencer enters
State1 and these bits are forced to SSF[2:0] = 001. See Table 6-24.
Table 6-24. SSF[2:0] — State Sequence Flag Bit Encoding
SSF[2:0]
Current State
000
State0 (disarmed)
001
State1
010
State2
011
State3
100
Final State
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
195
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-24. SSF[2:0] — State Sequence Flag Bit Encoding
6.3.2.12
SSF[2:0]
Current State
101,110,111
Reserved
Debug Comparator A Control Register (DBGACTL)
Address: 0x0110
7
R
0
W
Reset
0
6
5
NDB
INST
0
0
4
0
0
3
2
1
0
RW
RWE
reserved
COMPE
0
0
0
0
= Unimplemented or Reserved
Figure 6-14. Debug Comparator A Control Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-25. DBGACTL Field Descriptions
Field
Description
6
NDB
Not Data Bus — The NDB bit controls whether the match occurs when the data bus matches the comparator
register value or when the data bus differs from the register value. This bit is ignored if the INST bit in the
same register is set.
0 Match on data bus equivalence to comparator register contents
1 Match on data bus difference to comparator register contents
5
INST
Instruction Select — This bit configures the comparator to compare PC or data access addresses.
0 Comparator compares addresses of data accesses
1 Comparator compares PC address
3
RW
2
RWE
0
COMPE
Read/Write Comparator Value Bit — The RW bit controls whether read or write is used in compare for the
associated comparator. The RW bit is ignored if RWE is clear or INST is set.
0 Write cycle is matched
1 Read cycle is matched
Read/Write Enable Bit — The RWE bit controls whether read or write comparison is enabled for the
associated comparator. This bit is ignored when INST is set.
0 Read/Write is not used in comparison
1 Read/Write is used in comparison
Enable Bit — Determines if comparator is enabled
0 The comparator is not enabled
1 The comparator is enabled
Table 6-26 shows the effect for RWE and RW on the comparison conditions. These bits are ignored if INST
is set, because matches based on opcodes reaching the execution stage are data independent.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
196
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-26. Read or Write Comparison Logic Table
6.3.2.13
RWE Bit
RW Bit
RW Signal
Comment
0
x
0
RW not used in comparison
0
x
1
RW not used in comparison
1
0
0
Write match
1
0
1
No match
1
1
0
No match
1
1
1
Read match
Debug Comparator A Address Register (DBGAAH, DBGAAM, DBGAAL)
Address: 0x0115, DBGAAH
23
22
21
R
19
18
17
16
DBGAA[23:16]
W
Reset
20
0
0
0
0
0
0
0
0
14
13
12
11
10
9
8
Address: 0x0116, DBGAAM
15
R
DBGAA[15:8]
W
Reset
0
0
0
0
0
0
0
0
6
5
4
3
2
1
0
0
0
0
0
Address: 0x0117, DBGAAL
7
R
DBGAA[7:0]
W
Reset
0
0
0
0
Figure 6-15. Debug Comparator A Address Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-27. DBGAAH, DBGAAM, DBGAAL Field Descriptions
Field
Description
23–16
DBGAA
[23:16]
Comparator Address Bits [23:16]— These comparator address bits control whether the comparator compares
the address bus bits [23:16] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
15–0
DBGAA
[15:0]
Comparator Address Bits [15:0]— These comparator address bits control whether the comparator compares
the address bus bits [15:0] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
197
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.3.2.14
Debug Comparator A Data Register (DBGAD)
Address: 0x0118, 0x0119, 0x011A, 0x011B
31
R
W
W
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Bit 31 Bit 30 Bit 29 Bit 28 Bit 27 Bit 26 Bit 25 Bit 24 Bit 23 Bit 22 Bit 21 Bit 20 Bit 19 Bit 18 Bit 17 Bit 16
Reset
R
30
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Bit 8
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
0
0
0
0
0
0
0
0
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9
Reset
0
0
0
0
0
0
0
Figure 6-16. Debug Comparator A Data Register (DBGAD)
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
This register can be accessed with a byte resolution, whereby DBGAD0, DBGAD1, DBGAD2, DBGAD3
map to DBGAD[31:0] respectively.
Table 6-28. DBGAD Field Descriptions
Field
Description
31–16
Bits[31:16]
(DBGAD0,
DBGAD1)
Comparator Data Bits — These bits control whether the comparator compares the data bus bits to a logic one
or logic zero. The comparator data bits are only used in comparison if the corresponding data mask bit is logic 1.
0 Compare corresponding data bit to a logic zero
1 Compare corresponding data bit to a logic one
15–0
Bits[15:0]
(DBGAD2,
DBGAD3)
Comparator Data Bits — These bits control whether the comparator compares the data bus bits to a logic one
or logic zero. The comparator data bits are only used in comparison if the corresponding data mask bit is logic 1.
0 Compare corresponding data bit to a logic zero
1 Compare corresponding data bit to a logic one
6.3.2.15
Debug Comparator A Data Mask Register (DBGADM)
Address: 0x011C, 0x011D, 0x011E, 0x011F
31
R
W
Reset
R
W
Reset
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Bit 31 Bit 30 Bit 29 Bit 28 Bit 27 Bit 26 Bit 25 Bit 24 Bit 23 Bit 22 Bit 21 Bit 20 Bit 19 Bit 18 Bit 17 Bit 16
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Bit 8
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
0
0
0
0
0
0
0
0
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9
0
0
0
0
0
0
0
Figure 6-17. Debug Comparator A Data Mask Register (DBGADM)
Read: Anytime.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
198
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Write: If DBG not armed and PTACT is clear.
This register can be accessed with a byte resolution, whereby DBGADM0, DBGADM1, DBGADM2,
DBGADM3 map to DBGADM[31:0] respectively.
Table 6-29. DBGADM Field Descriptions
Field
Description
31–16
Bits[31:16]
(DBGADM0,
DBGADM1)
Comparator Data Mask Bits — These bits control whether the comparator compares the data bus bits to the
corresponding comparator data compare bits.
0 Do not compare corresponding data bit
1 Compare corresponding data bit
15-0
Bits[15:0]
(DBGADM2,
DBGADM3)
Comparator Data Mask Bits — These bits control whether the comparator compares the data bus bits to the
corresponding comparator data compare bits.
0 Do not compare corresponding data bit
1 Compare corresponding data bit
6.3.2.16
Debug Comparator B Control Register (DBGBCTL)
Address: 0x0120
R
7
6
0
0
0
0
W
Reset
5
INST
0
4
0
0
3
2
1
0
RW
RWE
reserved
COMPE
0
0
0
0
= Unimplemented or Reserved
Figure 6-18. Debug Comparator B Control Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-30. DBGBCTL Field Descriptions
Field(1)
5
INST
3
RW
2
RWE
Description
Instruction Select — This bit configures the comparator to compare PC or data access addresses.
0 Comparator compares addresses of data accesses
1 Comparator compares PC address
Read/Write Comparator Value Bit — The RW bit controls whether read or write is used in compare for the
associated comparator. The RW bit is ignored if RWE is clear or INST is set.
0 Write cycle is matched
1 Read cycle is matched
Read/Write Enable Bit — The RWE bit controls whether read or write comparison is enabled for the
associated comparator. This bit is ignored when INST is set.
0 Read/Write is not used in comparison
1 Read/Write is used in comparison
0
COMPE
Enable Bit — Determines if comparator is enabled
0 The comparator is not enabled
1 The comparator is enabled
1. If the ABCM field selects range mode comparisons, then DBGACTL bits configure the comparison, DBGBCTL is ignored.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
199
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-31 shows the effect for RWE and RW on the comparison conditions. These bits are ignored if INST
is set, as matches based on instructions reaching the execution stage are data independent.
Table 6-31. Read or Write Comparison Logic Table
6.3.2.17
RWE Bit
RW Bit
RW Signal
Comment
0
x
0
RW not used in comparison
0
x
1
RW not used in comparison
1
0
0
Write match
1
0
1
No match
1
1
0
No match
1
1
1
Read match
Debug Comparator B Address Register (DBGBAH, DBGBAM, DBGBAL)
Address: 0x0125, DBGBAH
23
22
21
R
19
18
17
16
DBGBA[23:16]
W
Reset
20
0
0
0
0
0
0
0
0
14
13
12
11
10
9
8
Address: 0x0126, DBGBAM
15
R
DBGBA[15:8]
W
Reset
0
0
0
0
0
0
0
0
6
5
4
3
2
1
0
0
0
0
0
Address: 0x0127, DBGBAL
7
R
DBGBA[7:0]
W
Reset
0
0
0
0
Figure 6-19. Debug Comparator B Address Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-32. DBGBAH, DBGBAM, DBGBAL Field Descriptions
Field
Description
23–16
DBGBA
[23:16]
Comparator Address Bits [23:16]— These comparator address bits control whether the comparator compares
the address bus bits [23:16] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
15–0
DBGBA
[15:0]
Comparator Address Bits[15:0]— These comparator address bits control whether the comparator compares
the address bus bits [15:0] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
200
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.3.2.18
Debug Comparator C Control Register (DBGCCTL)
Address: 0x0130
7
R
0
W
Reset
6
5
NDB
INST
0
0
0
4
0
0
3
2
1
0
RW
RWE
reserved
COMPE
0
0
0
0
= Unimplemented or Reserved
Figure 6-20. Debug Comparator C Control Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-33. DBGCCTL Field Descriptions
Field
Description
6
NDB
Not Data Bus — The NDB bit controls whether the match occurs when the data bus matches the comparator
register value or when the data bus differs from the register value. This bit is ignored if the INST bit in the
same register is set.
0 Match on data bus equivalence to comparator register contents
1 Match on data bus difference to comparator register contents
5
INST
Instruction Select — This bit configures the comparator to compare PC or data access addresses.
0 Comparator compares addresses of data accesses
1 Comparator compares PC address
3
RW
2
RWE
0
COMPE
Read/Write Comparator Value Bit — The RW bit controls whether read or write is used in compare for the
associated comparator. The RW bit is ignored if RWE is clear or INST is set.
0 Write cycle is matched
1 Read cycle is matched
Read/Write Enable Bit — The RWE bit controls whether read or write comparison is enabled for the
associated comparator. This bit is not used if INST is set.
0 Read/Write is not used in comparison
1 Read/Write is used in comparison
Enable Bit — Determines if comparator is enabled
0 The comparator is not enabled
1 The comparator is enabled
Table 6-34 shows the effect for RWE and RW on the comparison conditions. These bits are ignored if INST
is set, because matches based on opcodes reaching the execution stage are data independent.
Table 6-34. Read or Write Comparison Logic Table
RWE Bit
RW Bit
RW Signal
Comment
0
x
0
RW not used in comparison
0
x
1
RW not used in comparison
1
0
0
Write match
1
0
1
No match
1
1
0
No match
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
201
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-34. Read or Write Comparison Logic Table
6.3.2.19
RWE Bit
RW Bit
RW Signal
Comment
1
1
1
Read match
Debug Comparator C Address Register (DBGCAH, DBGCAM, DBGCAL)
Address: 0x0135, DBGCAH
23
22
21
R
19
18
17
16
DBGCA[23:16]
W
Reset
20
0
0
0
0
0
0
0
0
14
13
12
11
10
9
8
Address: 0x0136, DBGCAM
15
R
DBGCA[15:8]
W
Reset
0
0
0
0
0
0
0
0
6
5
4
3
2
1
0
0
0
0
0
Address: 0x0137, DBGCAL
7
R
DBGCA[7:0]
W
Reset
0
0
0
0
Figure 6-21. Debug Comparator C Address Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-35. DBGCAH, DBGCAM, DBGCAL Field Descriptions
Field
Description
23–16
DBGCA
[23:16]
Comparator Address Bits [23:16]— These comparator address bits control whether the comparator compares
the address bus bits [23:16] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
15–0
DBGCA
[15:0]
Comparator Address Bits[15:0]— These comparator address bits control whether the comparator compares
the address bus bits [15:0] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
202
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.3.2.20
Debug Comparator C Data Register (DBGCD)
Address: 0x0138, 0x0139, 0x013A, 0x013B
31
R
W
W
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Bit 31 Bit 30 Bit 29 Bit 28 Bit 27 Bit 26 Bit 25 Bit 24 Bit 23 Bit 22 Bit 21 Bit 20 Bit 19 Bit 18 Bit 17 Bit 16
Reset
R
30
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Bit 8
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
0
0
0
0
0
0
0
0
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9
Reset
0
0
0
0
0
0
0
Figure 6-22. Debug Comparator C Data Register (DBGCD)
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
This register can be accessed with a byte resolution, whereby DBGCD0, DBGCD1, DBGCD2, DBGCD3
map to DBGCD[31:0] respectively.
XGATE data accesses have a maximum width of 16-bits and are mapped to DBGCD[15:0].
Table 6-36. DBGCD Field Descriptions
Field
Description
31–16
Bits[31:16]
(DBGCD0,
DBGCD1)
Comparator Data Bits — These bits control whether the comparator compares the data bus bits to a logic one
or logic zero. The comparator data bits are only used in comparison if the corresponding data mask bit is logic 1.
0 Compare corresponding data bit to a logic zero
1 Compare corresponding data bit to a logic one
15–0
Bits[15:0]
(DBGCD2,
DBGCD3)
Comparator Data Bits — These bits control whether the comparator compares the data bus bits to a logic one
or logic zero. The comparator data bits are only used in comparison if the corresponding data mask bit is logic 1.
0 Compare corresponding data bit to a logic zero
1 Compare corresponding data bit to a logic one
6.3.2.21
Debug Comparator C Data Mask Register (DBGCDM)
Address: 0x013C, 0x013D, 0x013E, 0x013F
31
R
W
Reset
R
W
Reset
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Bit 31 Bit 30 Bit 29 Bit 28 Bit 27 Bit 26 Bit 25 Bit 24 Bit 23 Bit 22 Bit 21 Bit 20 Bit 19 Bit 18 Bit 17 Bit 16
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Bit 8
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
0
0
0
0
0
0
0
0
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9
0
0
0
0
0
0
0
Figure 6-23. Debug Comparator C Data Mask Register (DBGCDM)
Read: Anytime.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
203
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Write: If DBG not armed and PTACT is clear.
This register can be accessed with a byte resolution, whereby DBGCDM0, DBGCDM1, DBGCDM2,
DBGCDM3 map to DBGCDM[31:0] respectively.
XGATE data accesses have a maximum width of 16-bits and are mapped to DBGCDM[15:0].
Table 6-37. DBGCDM Field Descriptions
Field
Description
31–16
Bits[31:16]
(DBGCDM0,
DBGCDM1)
Comparator Data Mask Bits — These bits control whether the comparator compares the data bus bits to the
corresponding comparator data compare bits.
0 Do not compare corresponding data bit
1 Compare corresponding data bit
15–0
Bits[15:0]
(DBGCDM2,
DBGCDM3)
Comparator Data Mask Bits — These bits control whether the comparator compares the data bus bits to the
corresponding comparator data compare bits.
0 Do not compare corresponding data bit
1 Compare corresponding data bit
6.3.2.22
Debug Comparator D Control Register (DBGDCTL)
Address: 0x0140
R
7
6
0
0
0
0
W
Reset
5
INST
0
4
0
0
3
2
1
0
RW
RWE
reserved
COMPE
0
0
0
0
= Unimplemented or Reserved
Figure 6-24. Debug Comparator D Control Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-38. DBGDCTL Field Descriptions
Field(1)
5
INST
3
RW
2
RWE
0
COMPE
Description
Instruction Select — This bit configures the comparator to compare PC or data access addresses.
0 Comparator compares addresses of data accesses
1 Comparator compares PC address
Read/Write Comparator Value Bit — The RW bit controls whether read or write is used in compare for the
associated comparator. The RW bit is ignored if RWE is clear or INST is set.
0 Write cycle is matched
1 Read cycle is matched
Read/Write Enable Bit — The RWE bit controls whether read or write comparison is enabled for the
associated comparator. This bit is ignored if INST is set.
0 Read/Write is not used in comparison
1 Read/Write is used in comparison
Enable Bit — Determines if comparator is enabled
0 The comparator is not enabled
1 The comparator is enabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
204
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
1. If the CDCM field selects range mode comparisons, then DBGCCTL bits configure the comparison, DBGDCTL is ignored.
Table 6-39 shows the effect for RWE and RW on the comparison conditions. These bits are ignored if INST
is set, because matches based on opcodes reaching the execution stage are data independent.
Table 6-39. Read or Write Comparison Logic Table
6.3.2.23
RWE Bit
RW Bit
RW Signal
Comment
0
x
0
RW not used in comparison
0
x
1
RW not used in comparison
1
0
0
Write match
1
0
1
No match
1
1
0
No match
1
1
1
Read match
Debug Comparator D Address Register (DBGDAH, DBGDAM, DBGDAL)
Address: 0x0145, DBGDAH
23
22
21
R
19
18
17
16
DBGDA[23:16]
W
Reset
20
0
0
0
0
0
0
0
0
14
13
12
11
10
9
8
Address: 0x0146, DBGDAM
15
R
DBGDA[15:8]
W
Reset
0
0
0
0
0
0
0
0
6
5
4
3
2
1
0
0
0
0
0
Address: 0x0147, DBGDAL
7
R
DBGDA[7:0]
W
Reset
0
0
0
0
Figure 6-25. Debug Comparator D Address Register
Read: Anytime.
Write: If DBG not armed and PTACT is clear.
Table 6-40. DBGDAH, DBGDAM, DBGDAL Field Descriptions
Field
Description
23–16
DBGDA
[23:16]
Comparator Address Bits [23:16]— These comparator address bits control whether the comparator compares
the address bus bits [23:16] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
205
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-40. DBGDAH, DBGDAM, DBGDAL Field Descriptions
Field
Description
15–0
DBGDA
[15:0]
Comparator Address Bits[15:0]— These comparator address bits control whether the comparator compares
the address bus bits [15:0] to a logic one or logic zero.
0 Compare corresponding address bit to a logic zero
1 Compare corresponding address bit to a logic one
6.4
Functional Description
This section provides a complete functional description of the DBG module.
6.4.1
DBG Operation
The DBG module operation is enabled by setting ARM in DBGC1. When armed it supports storing of data
in the trace buffer and can be used to generate breakpoints to the CPU. The DBG module is made up of
comparators, control logic, the trace buffer, and the state sequencer, Figure 6-1.
The comparators monitor the bus activity of the CPU. Comparators can be configured to monitor opcode
addresses (effectively the PC address) or data accesses. Comparators can be configured during data
accesses to mask out individual data bus bits and to use R/W access qualification in the comparison.
Comparators can be configured to monitor a range of addresses.
When configured for data access comparisons, the match is generated if the address (and optionally data)
of a data access matches the comparator value.
Configured for monitoring opcode addresses, the match is generated when the associated opcode reaches
the execution stage of the instruction queue, but before execution of that opcode.
When a match with a comparator register value occurs, the associated control logic can force the state
sequencer to another state (see Figure 6-26).
The state sequencer can transition freely between the states 1, 2 and 3. On transition to Final State bus
tracing can be triggered. On completion of tracing the state sequencer enters State0. If tracing is disabled
or End aligned tracing is enabled then the state sequencer transitions immediately from Final State to
State0. The transition to State0 generates breakpoints if breakpoints are enabled.
Independent of the comparators, state sequencer transitions can be forced by the external event input or by
writing to the TRIG bit in the DBGC1 control register.
The trace buffer is visible through a 2-byte window in the register address map and can be read out using
standard 16-bit word reads.
6.4.2
Comparator Modes
The DBG contains four comparators, A, B, C, and D. Each comparator compares the address stored in
DBGXAH, DBGXAM, and DBGXAL with the PC (opcode addresses) or selected address bus (data
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
206
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
accesses). Furthermore, comparators A and C can compare the data buses to values stored in DBGXD3-0
and allow data bit masking.
The comparators can monitor the buses for an exact address or an address range. The comparator
configuration is controlled by the control register contents and the range control by the DBGC2 contents.
The comparator control register also allows the type of data access to be included in the comparison
through the use of the RWE and RW bits. The RWE bit controls whether the access type is compared for
the associated comparator and the RW bit selects either a read or write access for a valid match.
The INST bit in each comparator control register is used to determine the matching condition. By setting
INST, the comparator matches opcode addresses, whereby the databus, data mask, RW and RWE bits are
ignored. The comparator register must be loaded with the exact opcode address.
The comparator can be configured to match memory access addresses by clearing the INST bit.
Each comparator match can force a transition to another state sequencer state (see Section 6.4.3”).
Once a successful comparator match has occurred, the condition that caused the original match is not
verified again on subsequent matches. Thus if a particular data value is matched at a given address, this
address may not contain that data value when a subsequent match occurs.
Comparators C and D can also be used to select an address range to trace from, when tracing CPU accesses
in Detail mode. This is determined by the TRANGE bits in the DBGTCRH register. The TRANGE
encoding is shown in Table 6-9. If the TRANGE bits select a range definition using comparator D and the
COMPE bit is clear, then comparator D is configured for trace range definition. By setting the COMPE bit
the comparator is configured for address bus comparisons, the TRANGE bits are ignored and the tracing
range function is disabled. Similarly if the TRANGE bits select a range definition using comparator C and
the COMPE bit is clear, then comparator C is configured for trace range definition.
Match[0, 1, 2, 3] map directly to Comparators [A, B, C, D] respectively, except in range modes (see
Section 6.3.2.2”). Comparator priority rules are described in the event priority section (Section 6.4.3.5”).
6.4.2.1
Exact Address Comparator Match
With range comparisons disabled, the match condition is an exact equivalence of address bus with the
value stored in the comparator address registers. Qualification of the type of access (R/W) is also possible.
Code may contain various access forms of the same address, for example a 16-bit access of ADDR[n] or
byte access of ADDR[n+1] both access n+1. The comparators ensure that any access of the address defined
by the comparator address register generates a match, as shown in the example of Table 6-41. Thus if the
comparator address register contains ADDR[n+1] any access of ADDR[n+1] matches. This means that a
16-bit access of ADDR[n] or 32-bit access of ADDR[n-1] also match because they also access
ADDR[n+1]. The right hand columns show the contents of DBGxA that would match for each access.
Table 6-41. Comparator Address Bus Matches
Access
Address
ADDR[n]
ADDR[n+1]
ADDR[n+2]
ADDR[n+3]
32-bit
ADDR[n]
Match
Match
Match
Match
16-bit
ADDR[n]
Match
Match
No Match
No Match
16-bit
ADDR[n+1]
No Match
Match
Match
No Match
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
207
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-41. Comparator Address Bus Matches
Access
Address
ADDR[n]
ADDR[n+1]
ADDR[n+2]
ADDR[n+3]
8-bit
ADDR[n]
Match
No Match
No Match
No Match
If the comparator INST bit is set, the comparator address register contents are compared with the PC, the
data register contents and access type bits are ignored. The comparator address register must be loaded
with the address of the first opcode byte.
6.4.2.2
Address and Data Comparator Match
Comparators A and C feature data comparators, for data access comparisons. The comparators do not
evaluate if accessed data is valid. Accesses across aligned 32-bit boundaries are split internally into
consecutive accesses. The data comparator mapping to accessed addresses for the CPU is shown in
Table 6-42, whereby the Address column refers to the lowest 2 bits of the lowest accessed address. This
corresponds to the most significant data byte.
Table 6-42. Comparator Data Byte Alignment
Address[1:0]
Data Comparator
00
DBGxD0
01
DBGxD1
10
DBGxD2
11
DBGxD3
The fixed mapping of data comparator bytes to addresses within a 32-bit data field ensures data matches
independent of access size. To compare a single data byte within the 32-bit field, the other bytes within
that field must be masked using the corresponding data mask registers. This ensures that any access of that
byte (32-bit,16-bit or 8-bit) with matching data causes a match. If no bytes are masked then the data
comparator always compares all 32-bits and can only generate a match on a 32-bit access with correct 32bit data value. In this case, 8-bit or 16-bit accesses within the 32-bit field cannot generate a match even if
the contents of the addressed bytes match because all 32-bits must match. In Table 6-43 the Access
Address column refers to the address bits[1:0] of the lowest accessed address (most significant data byte).
Table 6-43. Data Register Use Dependency On CPU Access Type
Memory Address[2:0]
Case
Access
Address
Access
Size
000
001
010
011
1
00
32-bit
DBGxD0
DBGxD1
DBGxD2
DBGxD3
2
01
32-bit
DBGxD1
DBGxD2
DBGxD3
3
10
32-bit
4
11
32-bit
5
00
16-bit
6
01
16-bit
7
10
16-bit
8
11
16-bit
DBGxD2
DBGxD0
100
101
110
DBGxD0
DBGxD3
DBGxD0
DBGxD1
DBGxD3
DBGxD0
DBGxD1
DBGxD2
DBGxD1
DBGxD1
DBGxD2
DBGxD2
DBGxD3
DBGxD3
DBGxD0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
208
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Memory Address[2:0]
Case
Access
Address
Access
Size
000
9
00
8-bit
DBGxD0
10
01
8-bit
11
10
8-bit
12
11
8-bit
13
00
8-bit
001
010
011
100
101
110
DBGxD1
DBGxD2
DBGxD3
DBGxD0
Denotes byte that is not accessed.
For a match of a 32-bit access with data compare, the address comparator must be loaded with the address
of the lowest accessed byte. For Case1 Table 6-43 this corresponds to 000, for Case2 it corresponds to 001.
To compare all 32-bits, it is required that no bits are masked.
6.4.2.3
Data Bus Comparison NDB Dependency
The NDB control bit allows data bus comparators to be configured to either match on equivalence or on
difference. This allows monitoring of a difference in the contents of an address location from an expected
value.
When matching on an equivalence (NDB=0), each individual data bus bit position can be masked out by
clearing the corresponding mask bit, so that it is ignored in the comparison. A match occurs when all data
bus bits with corresponding mask bits set are equivalent. If all mask register bits are clear, then a match is
based on the address bus only, the data bus is ignored.
When matching on a difference, mask bits can be cleared to ignore bit positions. A match occurs when any
data bus bit with corresponding mask bit set is different. Clearing all mask bits, causes all bits to be ignored
and prevents a match because no difference can be detected. In this case address bus equivalence does not
cause a match. Bytes that are not accessed are ignored. Thus when monitoring a multi byte field for a
difference, partial accesses of the field only return a match if a difference is detected in the accessed bytes.
Table 6-44. NDB and MASK bit dependency
6.4.2.4
NDB
DBGADM
Comment
0
0
Do not compare data bus bit.
0
1
Compare data bus bit. Match on equivalence.
1
0
Do not compare data bus bit.
1
1
Compare data bus bit. Match on difference.
Range Comparisons
Range comparisons are accurate to byte boundaries. Thus for data access comparisons a match occurs if
at least one byte of the access is in the range (inside range) or outside the range (outside range). For opcode
comparisons only the address of the first opcode byte is compared with the range.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
209
Chapter 6 S12Z Debug (S12ZDBGV2) Module
When using the AB comparator pair for a range comparison, the data bus can be used for qualification by
using the comparator A data and data mask registers. Similarly when using the CD comparator pair for a
range comparison, the data bus can be used for qualification by using the comparator C data and data mask
registers. The DBGACTL/DBGCCTL RW and RWE bits can be used to qualify the range comparison on
either a read or a write access. The corresponding DBGBCTL/DBGDCTL bits are ignored. The
DBGACTL/DBGCCTL COMPE/INST bits are used for range comparisons. The DBGBCTL/DBGDCTL
COMPE/INST bits are ignored in range modes.
6.4.2.4.1
Inside Range (CompAC_Addr ≤ address ≤ CompBD_Addr)
In the Inside Range comparator mode, either comparator pair A and B or comparator pair C and D can be
configured for range comparisons by the control register (DBGC2). The match condition requires a
simultaneous valid match for both comparators. A match condition on only one comparator is not valid.
6.4.2.4.2
Outside Range (address < CompAC_Addr or address > CompBD_Addr)
In the Outside Range comparator mode, either comparator pair A and B or comparator pair C and D can
be configured for range comparisons. A single match condition on either of the comparators is recognized
as valid. Outside range mode in combination with opcode address matches can be used to detect if opcodes
are from an unexpected range.
NOTE
When configured for data access matches, an outside range match would
typically occur at any interrupt vector fetch or register access. This can be
avoided by setting the upper or lower range limit to $FFFFFF or $000000
respectively. Interrupt vector fetches do not cause opcode address matches.
6.4.3
Events
Events are used as qualifiers for a state sequencer change of state. The state control register for the current
state determines the next state for each event. An event can immediately initiate a transition to the next
state sequencer state whereby the corresponding flag in DBGSR is set.
6.4.3.1
6.4.3.1.1
Comparator Match Events
Opcode Address Comparator Match
The comparator is loaded with the address of the selected instruction and the comparator control register
INST bit is set. When the opcode reaches the execution stage of the instruction queue a match occurs just
before the instruction executes, allowing a breakpoint immediately before the instruction boundary. The
comparator address register must contain the address of the first opcode byte for the match to occur.
Opcode address matches are data independent thus the RWE and RW bits are ignored. CPU compares are
disabled when BDM becomes active.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
210
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.4.3.1.2
Data Access Comparator Match
Data access matches are generated when an access occurs at the address contained in the comparator
address register. The match can be qualified by the access data and by the access type (read/write). The
breakpoint occurs a maximum of 2 instructions after the access in the CPU flow. Note, if a COF occurs
between access and breakpoint, the opcode address of the breakpoint can be elsewhere in the memory map.
Opcode fetches are not classed as data accesses. Thus data access matches are not possible on opcode
fetches.
6.4.3.2
External Event
The DBGEEV input signal can force a state sequencer transition, independent of internal comparator
matches. The DBGEEV is an input signal mapped directly to a device pin and configured by the EEVE
field in DBGC1. The external events can change the state sequencer state, or force a trace buffer entry, or
gate trace buffer entries.
If configured to change the state sequencer state, then the external match is mapped to DBGSCRx bits
C3SC[1:0]. In this configuration, internal comparator channel3 is de-coupled from the state sequencer but
can still be used for timestamps. The DBGEFR bit EEVF is set when an external event occurs.
6.4.3.3
Setting The TRIG Bit
Independent of comparator matches it is possible to initiate a tracing session and/or breakpoint by writing
the TRIG bit in DBGC1 to a logic “1”. This forces the state sequencer into the Final State. If configured
for End aligned tracing or for no tracing, the transition to Final State is followed immediately by a
transition to State0. If configured for Begin- or Mid Aligned tracing, the state sequencer remains in Final
State until tracing is complete, then it transitions to State0.
Breakpoints, if enabled, are issued on the transition to State0.
6.4.3.4
Profiling Trace Buffer Overflow Event
During code profiling a trace buffer overflow forces the state sequencer into the disarmed State0 and, if
breakpoints are enabled, issues a breakpoint request to the CPU.
6.4.3.5
Event Priorities
If simultaneous events occur, the priority is resolved according to Table 6-45. Lower priority events are
suppressed. It is thus possible to miss a lower priority event if it occurs simultaneously with an event of a
higher priority. The event priorities dictate that in the case of simultaneous matches, the match on the
higher comparator channel number (3,2,1,0) has priority.
If a write access to DBGC1 with the ARM bit position set occurs simultaneously to a hardware disarm
from an internal event, then the ARM bit is cleared due to the hardware disarm.
Table 6-45. Event Priorities
Priority
Source
Action
Highest
TB Overflow
Immediate force to state 0, generate breakpoint and terminate tracing
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
211
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-45. Event Priorities
TRIG
Force immediately to final state
DBGEEV
Force to next state as defined by state control registers (EEVE=2’b10)
Match3
Force to next state as defined by state control registers
Match2
Force to next state as defined by state control registers
Match1
Force to next state as defined by state control registers
Match0
Force to next state as defined by state control registers
Lowest
6.4.4
State Sequence Control
State 0
(Disarmed)
ARM = 1
State1
Final State
State2
State3
Figure 6-26. State Sequencer Diagram
The state sequencer allows a defined sequence of events to provide a breakpoint and/or a trigger point for
tracing of data in the trace buffer. When the DBG module is armed by setting the ARM bit in the DBGC1
register, the state sequencer enters State1. Further transitions between the states are controlled by the state
control registers and depend upon event occurrences (see Section 6.4.3). From Final State the only
permitted transition is back to the disarmed State0. Transition between the states 1 to 3 is not restricted.
Each transition updates the SSF[2:0] flags in DBGSR accordingly to indicate the current state. If
breakpoints are enabled, then an event based transition to State0 generates the breakpoint request. A
transition to State0 resulting from writing “0” to the ARM bit does not generate a breakpoint request.
6.4.4.1
Final State
On entering Final State a trigger may be issued to the trace buffer according to the trigger position control
as defined by the TALIGN field (see Section 6.3.2.3”).
If tracing is enabled and either Begin or Mid aligned triggering is selected, the state sequencer remains in
Final State until completion of the trace. On completion of the trace the state sequencer returns to State0
and the debug module is disarmed; if breakpoints are enabled, a breakpoint request is generated.
If tracing is disabled or End aligned triggering is selected, then when the Final State is reached the state
sequencer returns to State0 immediately and the debug module is disarmed. If breakpoints are enabled, a
breakpoint request is generated on transitions to State0.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
212
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.4.5
Trace Buffer Operation
The trace buffer is a 64 lines deep by 64-bits wide RAM array. If the TSOURCE bit is set the DBG module
can store trace information in the RAM array in a circular buffer format. Data is stored in mode dependent
formats, as described in the following sections. After each trace buffer entry, the counter register DBGCNT
is incremented. Trace buffer rollover is possible when configured for End- or Mid-Aligned tracing, such
that older entries are replaced by newer entries. Tracing of CPU activity is disabled when the BDC is
active.
The RAM array can be accessed through the register DBGTB using 16-bit wide word accesses. After each
read, the internal RAM pointer is incremented so that the next read will receive fresh information. Reading
the trace buffer whilst the DBG is armed returns invalid data and the trace buffer pointer is not
incremented.
In Detail mode the address range for CPU access tracing can be limited to a range specified by the
TRANGE bits in DBGTCRH. This function uses comparators C and D to define an address range inside
which accesses should be traced. Thus traced accesses can be restricted, for example, to particular register
or RAM range accesses.
The external event pin can be configured to force trace buffer entries in Normal or Loop1 trace modes. All
tracing modes support trace buffer gating. In Pure PC and Detail modes external events do not force trace
buffer entries.
If the external event pin is configured to gate trace buffer entries then any trace mode is valid.
6.4.5.1
Trace Trigger Alignment
Using the TALIGN bits (see Section 6.3.2.3”) it is possible to align the trigger with the end, the middle, or
the beginning of a tracing session.
If End or Mid-Alignment is selected, tracing begins when the ARM bit in DBGC1 is set and State1 is
entered. The transition to Final State if End-Alignment is selected, ends the tracing session. The transition
to Final State if Mid-Alignment is selected signals that another 32 lines are traced before ending the tracing
session. Tracing with Begin-Alignment starts at the trigger and ends when the trace buffer is full.
Table 6-46. Tracing Alignment
TALIGN
Tracing Begin
Tracing End
00
On arming
At trigger
01
At trigger
When trace buffer is full
10
On arming
When 32 trace buffer lines have
been filled after trigger
11
6.4.5.1.1
Reserved
Storing with Begin-Alignment
Storing with Begin-Alignment, data is not stored in the trace buffer until the Final State is entered. Once
the trigger condition is met the DBG module remains armed until 64 lines are stored in the trace buffer.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
213
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Using Begin-Alignment together with opcode address comparisons, if the instruction is about to be
executed then the trace is started. If the trigger is at the address of a COF instruction, whilst tracing COF
addresses, then that COF address is stored to the trace buffer. If breakpoints are enabled, the breakpoint is
generated upon entry into State0 on completion of the tracing session; thus the breakpoint does not occur
at the instruction boundary.
6.4.5.1.2
Storing with Mid-Alignment
Storing with Mid-Alignment, data is stored in the trace buffer as soon as the DBG module is armed. When
the trigger condition is met, another 32 lines are traced before ending the tracing session, irrespective of
the number of lines stored before the trigger occurred, then the DBG module is disarmed and no more data
is stored. Using Mid-Alignment with opcode address triggers, if the instruction is about to be executed then
the trace is continued for another 32 lines. If breakpoints are enabled, the breakpoint is generated upon
entry into State0 on completion of the tracing session; thus the breakpoint does not occur at the instruction
boundary. When configured for Compressed Pure-PC tracing, the MAT info bit is set to indicate the last
PC entry before a trigger event.
6.4.5.1.3
Storing with End-Alignment
Storing with End-Alignment, data is stored in the trace buffer until the Final State is entered. Following
this trigger, the DBG module immediately transitions to State0. If the trigger is at the address of a COF
instruction the trigger event is not stored in the trace buffer.
6.4.5.2
Trace Modes
The DBG module can operate in four trace modes. The mode is selected using the TRCMOD bits in the
DBGTCRH register. Normal, Loop1 and Detail modes can be configured to store a timestamp with each
entry, by setting the STAMP bit. The modes are described in the following subsections.
In addition to the listed trace modes it is also possible to use code profiling to fill the trace buffer with a
highly compressed COF format. This can be subsequently read out in the same fashion as the listed trace
modes (see Section 6.4.6).
6.4.5.2.1
Normal Mode
In Normal Mode, change of flow (COF) program counter (PC) addresses are stored.
CPU COF addresses are defined as follows:
• Source address of taken conditional branches (bit-conditional, and loop primitives)
• Destination address of indexed JMP and JSR instruction.s
• Destination address of RTI and RTS instructions.
• Vector address of interrupts
BRA, BSR, BGND as well as non-indexed JMP and JSR instructions are not classified as change of flow
and are not stored in the trace buffer.
COF addresses stored include the full address bus of CPU and an information byte, which contains bits to
indicate whether the stored address was a source, destination or vector address.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
214
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
NOTE
When a CPU indexed jump instruction is executed, the destination address
is stored to the trace buffer on instruction completion, indicating the COF
has taken place. If an interrupt occurs simultaneously then the next
instruction carried out is actually from the interrupt service routine. The
instruction at the destination address of the original program flow gets
executed after the interrupt service routine.
In the following example an IRQ interrupt occurs during execution of the
indexed JMP at address MARK1. The NOP at the destination (SUB_1) is
not executed until after the IRQ service routine but the destination address
is entered into the trace buffer to indicate that the indexed JMP COF has
taken place.
MARK1:
MARK2:
LD
JMP
NOP
SUB_1:
NOP
ADDR1:
NOP
DBNE
IRQ_ISR: LD
ST
RTI
X,#SUB_1
(0,X)
; IRQ interrupt occurs during execution of this
;
; JMP Destination address TRACE BUFFER ENTRY 1
; RTI Destination address TRACE BUFFER ENTRY 3
;
; Source address TRACE BUFFER ENTRY 4
D0,PART5
D1,#$F0
D1,VAR_C1
; IRQ Vector $FFF2 = TRACE BUFFER ENTRY 2
;
The execution flow taking into account the IRQ is as follows
LD
MARK1:
JMP
IRQ_ISR: LD
ST
RTI
SUB_1:
NOP
NOP
ADDR1:
DBNE
X,#SUB_1
(0,X)
D1,#$F0
D1,VAR_C1
;
;
;
;
;
D0,PART5
The Normal Mode trace buffer format is shown in the following tables. Whilst tracing in Normal or Loop1
modes each array line contains 2 data entries, thus in this case the DBGCNT[0] is incremented after each
separate entry. Information byte bits indicate if an entry is a source, destination or vector address.
The external event input can force trace buffer entries independent of COF occurrences, in which case the
EEVI bit is set and the PC value of the last instruction is stored to the trace buffer. If the external event
coincides with a COF buffer entry a single entry is made with the EEVI bit set.
Normal mode profiling with timestamp is possible when tracing from a single source by setting the
STAMP bit in DBGTCRL. This results in a different format (see Table 6-48).
Table 6-47. Normal and Loop1 Mode Trace Buffer Format without Timestamp
Mode
8-Byte Wide Trace Buffer Line
7
6
5
4
3
2
1
0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
215
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-47. Normal and Loop1 Mode Trace Buffer Format without Timestamp
CPU
CINF1
CPCH1
CPCM1
CPCL1
CINF0
CPCH0
CPCM0
CPCL0
CINF3
CPCH3
CPCM3
CPCL3
CINF2
CPCH2
CPCM2
CPCL2
Table 6-48. Normal and Loop1 Mode Trace Buffer Format with Timestamp
Mode
CPU
8-Byte Wide Trace Buffer Line
7
6
5
4
3
2
1
0
Timestamp
Timestamp
Reserved
Reserved
CINF0
CPCH0
CPCM0
CPCL0
Timestamp
Timestamp
Reserved
Reserved
CINF1
CPCH1
CPCM1
CPCL1
CINF contains information relating to the CPU.
CPU Information Byte CINF For Normal And Loop1 Modes
Bit 7
Bit 6
CET
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
0
CTI
EEVI
0
TOVF
Figure 6-27. CPU Information Byte CINF
Table 6-49. CINF Bit Descriptions
Field
Description
7–6
CET
CPU Entry Type Field — Indicates the type of stored address of the trace buffer entry as described in Table 6-50
3
CTI
Comparator Timestamp Indicator — This bit indicates if the trace buffer entry corresponds to a comparator
timestamp.
0 Trace buffer entry initiated by trace mode specification conditions or timestamp counter overflow
1 Trace buffer entry initiated by comparator D match
2
EEVI
External Event Indicator — This bit indicates if the trace buffer entry corresponds to an external event.
0 Trace buffer entry not initiated by an external event
1 Trace buffer entry initiated by an external event
0
TOVF
Timestamp Overflow Indicator — Indicates if the trace buffer entry corresponds to a timestamp overflow
0 Trace buffer entry not initiated by a timestamp overflow
1 Trace buffer entry initiated by a timestamp overflow
Table 6-50. CET Encoding
CET
Entry Type Description
00
Non COF opcode address (entry forced by an external event)
01
Vector destination address
10
Source address of COF opcode
11
Destination address of COF opcode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
216
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.4.5.2.2
Loop1 Mode
Loop1 Mode, similarly to Normal Mode also stores only COF address information to the trace buffer, it
however allows the filtering out of redundant information.
The intent of Loop1 Mode is to prevent the trace buffer from being filled entirely with duplicate
information from a looping construct such as delays using the DBNE instruction. The DBG monitors trace
buffer entries and prevents consecutive duplicate address entries resulting from repeated branches.
Loop1 Mode only inhibits consecutive duplicate source address entries that would typically be stored in
most tight looping constructs. It does not inhibit repeated entries of destination addresses or vector
addresses, since repeated entries of these could indicate a bug in application code that the DBG module is
designed to help find.
The trace buffer format for Loop1 Mode is the same as that of Normal Mode.
6.4.5.2.3
Detail Mode
When tracing CPU activity in Detail Mode, address and data of data and vector accesses are traced. The
information byte indicates the size of access and the type of access (read or write).
ADRH, ADRM, ADRL denote address high, middle and low byte respectively. The numerical suffix
indicates which tracing step. DBGCNT increments by 2 for each line completed.
If timestamps are enabled then each CPU entry can span 2 trace buffer lines, whereby the second line
includes the timestamp. If a valid PC occurs in the same cycle as the timestamp, it is also stored to the trace
buffer and the PC bit is set. The second line featuring the timestamp is only stored if no further data access
occurs in the following cycle. This is shown in Table 6-52, where data accesses 2 and 3 occur in
consecutive cycles, suppressing the entry2 timestamp. If 2 lines are used for an entry, then DBGCNT
increments by 4. A timestamp line is indicated by bit1 in the TSINF byte. The timestamp counter is only
reset each time a timestamp line entry is made. It is not reset when the data and address trace buffer line
entry is made.
Table 6-51. Detail Mode Trace Buffer Format without Timestamp
Mode
CPU
Detail
8-Byte Wide Trace Buffer Line
7
6
5
4
3
2
1
0
CDATA31
CDATA21
CDATA11
CDATA01
CINF1
CADRH1
CADRM1
CADRL1
CDATA32
CDATA22
CDATA12
CDATA02
CINF2
CADRH2
CADRM2
CADRL2
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
217
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Table 6-52. Detail Mode Trace Buffer Format with Timestamp
8-Byte Wide Trace Buffer Line
Mode
CPU
Detail
7
6
5
4
3
2
1
0
CDATA31
CDATA21
CDATA11
CDATA01
CINF1
CADRH1
CADRM1
CADRL1
Timestamp
Timestamp
Reserved
Reserved
TSINF1
CPCH1
CPCM1
CPCL1
CDATA32
CDATA22
CDATA12
CDATA02
CINF2
CADRH2
CADRM2
CADRL2
CDATA33
CDATA23
CDATA13
CDATA03
CINF3
CADRH3
CADRM3
CADRL3
Timestamp
Timestamp
Reserved
Reserved
TSINF3
CPCH3
CPCM3
CPCL3
Detail Mode data entries store the bytes aligned to the address of the MSB accessed (Byte1 Table 6-53).
Thus accesses split across 32-bit boundaries are wrapped around.
Table 6-53. Detail Mode Data Byte Alignment
Access
Address
Access
Size
CDATA31
CDATA21
CDATA11
CDATA01
00
32-bit
Byte1
Byte2
Byte3
Byte4
01
32-bit
Byte4
Byte1
Byte2
Byte3
10
32-bit
Byte3
Byte4
Byte1
Byte2
11
32-bit
Byte2
Byte3
Byte4
Byte1
00
24-bit
Byte1
Byte2
Byte3
01
24-bit
10
24-bit
Byte3
Byte1
11
24-bit
Byte2
Byte3
00
16-bit
Byte1
Byte2
01
16-bit
10
16-bit
11
16-bit
Byte2
00
8-bit
Byte1
01
8-bit
10
8-bit
11
8-bit
Byte2
Byte3
Byte1
Byte2
Byte1
Byte1
Byte2
Byte1
Byte2
Byte1
Byte1
Byte1
Byte1
Denotes byte that is not accessed.
Information Bytes
BYTE
Bit 7
CINF
TSINF
Bit 6
CSZ
0
0
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
CRW
0
0
0
0
0
0
0
CTI
PC
1
TOVF
Figure 6-28. Information Bytes CINF and XINF
When tracing in Detail Mode, CINF provides information about the type of CPU access being made.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
218
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
TSINF provides information about a timestamp. Bit1 indicates if the byte is a TSINF byte.
Table 6-54. CINF Field Descriptions
Field
Description
7–6
CSZ
Access Type Indicator — This field indicates the CPU access size.
00 8-bit Access
0116-bit Access
10 24-bit Access
11 32-bit Access
5
CRW
Read/Write Indicator — Indicates if the corresponding stored address corresponds to a read or write access.
0 Write Access
1 Read Access
Table 6-55. TSINF Field Descriptions
Field
Description
3
CTI
Comparator Timestamp Indicator — This bit indicates if the trace buffer entry corresponds to a comparator
timestamp.
0 Trace buffer entry initiated by trace mode specification conditions or timestamp counter overflow
1 Trace buffer entry initiated by comparator D match
2
PC
Program Counter Valid Indicator — Indicates if the PC entry is valid on the timestamp line.
0 Trace buffer entry does not include PC value
1 Trace buffer entry includes PC value
0
TOVF
6.4.5.2.4
Timestamp Overflow Indicator — Indicates if the trace buffer entry corresponds to a timestamp overflow
0 Trace buffer entry not initiated by a timestamp overflow
1 Trace buffer entry initiated by a timestamp overflow
Pure PC Mode
In Pure PC Mode, the PC addresses of all opcodes loaded into the execution stage, including illegal
opcodes, are stored.
Tracing from a single source, compression is implemented to increase the effective trace depth. A
compressed entry consists of the lowest PC byte only. A full entry consists of all PC bytes. If the PC
remains in the same 256 byte range, then a compressed entry is made, otherwise a full entry is made. The
full entry is always the last entry of a record.
Each trace buffer line consists of 7 payload bytes, PLB0-6, containing full or compressed CPU PC
addresses and 1 information byte to indicate the type of entry (compressed or base address) for each
payload byte.
Each trace buffer line is filled from right to left. The final entry on each line is always a base address, used
as a reference for the previous entries on the same line. Whilst tracing, a base address is typically stored
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
219
Chapter 6 S12Z Debug (S12ZDBGV2) Module
in bytes[6:4], the other payload bytes may be compressed or complete addresses as indicated by the info
byte bits.
Table 6-56. Pure PC Mode Trace Buffer Format Single Source
Mode
CPU
8-Byte Wide Trace Buffer Line
7
6
5
4
3
2
1
0
CXINF
BASE
BASE
BASE
PLB3
PLB2
PLB1
PLB0
If the info bit for byte3 indicates a full CPU PC address, whereby bytes[5:3] are used, then the info bit
mapped to byte[4] is redundant and the byte[6] is unused because a line overflow has occurred. Similarly
a base address stored in bytes[4:2] causes line overflow, so bytes[6:5] are unused.
CXINF[6:4] indicate how many bytes in a line contain valid data, since tracing may terminate before a
complete line has been filled.
CXINF Information Byte Source Tracing
7
CXINF
MAT
6
5
PLEC
4
3
2
1
0
NB3
NB2
NB1
NB0
Figure 6-29. Pure PC Mode CXINF
Table 6-57. CXINF Field Descriptions
Field
Description
MAT
Mid Aligned Trigger— This bit indicates a mid aligned trigger position. When a mid aligned trigger occurs, the
next trace buffer entry is a base address and the counter is incremented to a new line, independent of the number
of bytes used on the current line. The MAT bit is set on the current line, to indicate the position of the trigger.
When configured for begin or end aligned trigger, this bit has no meaning.
NOTE: In the case when ARM and TRIG are simultaneously set together in the same cycle that a new PC value
is registered, then this PC is stored to the same trace buffer line and MAT set.
0 Line filled without mid aligned trigger occurrence
1 Line last entry is the last PC entry before a mid aligned trigger
PLEC[2:0]
NBx
Payload Entry Count— This field indicates the number of valid bytes in the trace buffer line
Binary encoding is used to indicate up to 7 valid bytes.
Payload Compression Indicator— This field indicates if the corresponding payload byte is the lowest byte of a
base PC entry
0 Corresponding payload byte is a not the lowest byte of a base PC entry
1 Corresponding payload byte is the lowest byte of a base PC entry
Pure PC mode tracing does not support timestamps or external event entries.
6.4.5.3
Timestamp
When set, the STAMP bit in DBGTCRL configures the DBG to add a timestamp to trace buffer entries in
Normal, Loop1 and Detail trace buffer modes. The timestamp is generated from a 16-bit counter and is
stored to the trace buffer line each time a trace buffer entry is made.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
220
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
The number of core clock cycles since the last entry equals the timestamp + 1. The core clock runs at twice
the frequency of the bus clock. The timestamp of the first trace buffer entry is 0x0000. With timestamps
enabled trace buffer entries are initiated in the following ways:
• according to the trace mode specification, for example COF PC addresses in Normal mode
• on a timestamp counter overflow
If the timestamp counter reaches 0xFFFF then a trace buffer entry is made, with timestamp=
0xFFFF and the timestamp overflow bit TOVF is set.
• on a match of comparator D
If STAMP and DSTAMP are set then comparator D is used for forcing trace buffer entries with
timestamps. The state control register settings determine if comparator D is also used to trigger the
state sequencer. Thus if the state control register configuration does not use comparator D, then it
is used solely for the timestamp function. If comparator D initiates a timestamp then the CTI bit is
set in the INFO byte. This can be used in Normal/Loop1 mode to indicate when a particular data
access occurs relative to the PC flow. For example when the timing of an access may be unclear
due to the use of indexes.
NOTE
If comparator D is configured to match a PC address then associated
timestamps trigger a trace buffer entry during execution of the previous
instruction. Thus the PC stored to the trace buffer is that of the previous
instruction.The comparator must contain the PC address of the instruction’s
first opcode byte
Timestamps are disabled in Pure PC mode.
6.4.5.4
Reading Data from Trace Buffer
The data stored in the trace buffer can be read using either the background debug controller (BDC) module
or the CPU provided the DBG module is not armed and is configured for tracing by TSOURCE. When the
ARM bit is set the trace buffer is locked to prevent reading. The trace buffer can only be unlocked for
reading by an aligned word write to DBGTB when the module is disarmed. The trace buffer can only be
read through the DBGTB register using aligned word reads. Reading the trace buffer while the DBG
module is armed, or trace buffer locked returns 0xEE and no shifting of the RAM pointer occurs. Any byte
or misaligned reads return 0xEE and do not cause the trace buffer pointer to increment to the next trace
buffer address.
Reading the trace buffer is prevented by internal hardware whilst profiling is active because the RAM
pointer is used to indicate the next row to be transmitted. Thus attempted reads of DBGTB do not return
valid data when the PROFILE bit is set. To initialize the pointer and read profiling data, the PROFILE bit
must be cleared and remain cleared.
The trace buffer data is read out first-in first-out. By reading CNT in DBGCNT the number of valid 64-bit
lines can be determined. DBGCNT does not decrement as data is read.
Whilst reading, an internal pointer is used to determine the next line to be read. After a tracing session, the
pointer points to the oldest data entry, thus if no overflow has occurred, the pointer points to line0. The
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
221
Chapter 6 S12Z Debug (S12ZDBGV2) Module
pointer is initialized by each aligned write to DBGTB to point to the oldest data again. This enables an
interrupted trace buffer read sequence to be easily restarted from the oldest data entry. After reading all
trace buffer lines, the next read wraps around and returns the contents of line0.
The least significant word of each 64-bit wide array line is read out first. All bytes, including those
containing invalid information are read out.
6.4.5.5
Trace Buffer Reset State
The trace buffer contents are not initialized by a system reset. Thus should a system reset occur, the trace
session information from immediately before the reset occurred can be read out. The DBGCNT bits are
not cleared by a system reset. Thus should a reset occur, the number of valid lines in the trace buffer is
indicated by DBGCNT. The internal pointer is cleared by a system reset. It can be initialized by an aligned
word write to DBGTB following a reset during debugging, so that it points to the oldest valid data again.
Debugging occurrences of system resets is best handled using mid or end trigger alignment since the reset
may occur before the trace trigger, which in the begin trigger alignment case means no information would
be stored in the trace buffer.
6.4.6
6.4.6.1
Code Profiling
Code Profiling Overview
Code profiling supplies encoded COF information on the PDO pin and the reference clock on the
PDOCLK pin. If the TSOURCE bit is set then code profiling is enabled by setting the PROFILE bit. The
associated device pin is configured for code profiling by setting the PDOE bit. Once enabled, code
profiling is activated by arming the DBG. During profiling, if PDOE is set, the PDO operates as an output
pin at a half the internal bus frequency, driving both high and low.
Independent of PDOE status, profiling data is stored to the trace buffer and can be read out in the usual
manner when the debug session ends and the PROFILE bit has been cleared.
The external debugger uses both edges of the clock output to strobe the data on PDO. The first PDOCLK
edge is used to sample the first data bit on PDO.
Figure 6-30. Profiling Output Interface
CLOCK
PDOCLK
DATA
TBUF
PDO
DEV TOOL
DBG
MCU
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
222
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Figure 6-31 shows the profiling clock, PDOCLK, whose edges are offset from the bus clock, to ease setup
and hold time requirements relative to PDO, which is synchronous to the bus clock.
Figure 6-31. PDO Profiling Clock Control
STROBE
BUS CLOCK
PDO
CLOCK ENABLE
PDOCLK
The trace buffer is used as a temporary storage medium to store COF information before it is transmitted.
COF information can be transmitted whilst new information is written to the trace buffer. The trace buffer
data is transmitted at PDO least significant bit first. After the first trace buffer entry is made, transmission
begins in the first clock period in which no further data is written to the trace buffer.
If a trace buffer line transmission completes before the next trace buffer line is ready, then the clock output
is held at a constant level until the line is ready for transfer.
6.4.6.2
Profiling Configuration, Alignment and Mode Dependencies
The PROFILE bit must be set and the DBG armed to enable profiling. Furthermore the PDOE bit must be
set to configure the PDO and PDOCLK pins for profiling.
If TALIGN is configured for End-Aligned tracing then profiling begins as soon as the module is armed.
If TALIGN is configured for Begin-aligned tracing, then profiling begins when the state sequencer enters
Final State and continues until a software disarm or trace buffer overflow occurs; thus profiling does not
terminate after 64 line entries have been made.
Mid-Align tracing is not supported whilst profiling; if the TALIGN bits are configured for Mid-Align
tracing when PROFILE is set, then the alignment defaults to end alignment.
Profiling entries continue until either a trace buffer overflow occurs or the DBG is disarmed by a state
machine transition to State0. The profiling output transmission continues, even after disarming, until all
trace buffer entries have been transmitted. The PTACT bit indicates if a profiling transmission is still
active. The PTBOVF indicates if a trace buffer overflow has occurred.
The profiling timestamp feature is used only for the PTVB and PTW formats, thus differing from
timestamps offered in other modes.
Profiling does not support trace buffer gating. The external pin gating feature is ignored during profiling.
When the DBG module is disarmed but profiling transmission is ongoing, register write accesses are
suppressed.
When the DBG module is disarmed but profiling transmission is still ongoing, reading from the DBGTB
returns the code 0xEE.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
223
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.4.6.3
Code Profiling Internal Data Storage Format
When profiling starts, the first trace buffer entry is made to provide the start address. This uses a 4 byte
format (PTS), including the INFO byte and a 3-byte PC start address. In order to avoid trace buffer
overflow a fully compressed format is used for direct (conditional branch) COF information.
Table 6-58. Profiling Trace buffer line format
Format
8-Byte Wide Trace Buffer Line
7
6
5
4
3
1
PC Start Address
PTS
PTIB
2
Indirect
Indirect
PTHF
0
INFO
Indirect
Direct
Direct
Direct
Direct
INFO
0
Direct
Direct
Direct
Direct
INFO
PTVB
Timestamp
Timestamp
Vector
Direct
Direct
Direct
Direct
INFO
PTW
Timestamp
Timestamp
0
Direct
Direct
Direct
Direct
INFO
The INFO byte indicates the line format used. Up to 4 bytes of each line are dedicated to branch COFs.
Further bytes are used for storing indirect COF information (indexed jumps and interrupt vectors). Indexed
jumps force a full line entry with the PTIB format and require 3-bytes for the full 24-bit destination
address. Interrupts force a full line entry with the PTVB format, whereby vectors are stored as a single byte
and a 16-bit timestamp value is stored simultaneously to indicate the number of bus cycles relative to the
previous COF. At each trace buffer entry the 16-bit timestamp counter is cleared. The device vectors use
address[8:0] whereby address[1:0] are constant zero for vectors. Thus the value stored to the PTVB vector
byte is equivalent to (Vector Address[8:1]).
After the PTS entry, the pointer increments and the DBG begins to fill the next line with direct COF
information. This continues until the direct COF field is full or an indirect COF occurs, then the INFO byte
and, if needed, indirect COF information are entered on that line and the pointer increments to the next line.
If a timestamp overflow occurs, indicating a 65536 bus clock cycles without COF, then an entry is made
with the TSOVF bit set, INFO[6] (Table 6-59) and profiling continues.
If a trace buffer overflow occurs, a final entry is made with the TBOVF bit set, profiling is terminated and
the DBG is disarmed. Trace buffer overflow occurs when the trace buffer contains 64 lines pending
transmission.
Whenever the DBG is disarmed during profiling, a final entry is made with the TERM bit set to indicate
the final entry.
When a final entry is made then by default the PTW line format is used, except if a COF occurs in the same
cycle in which case the corresponding PTIB/PTVB/PTHF format is used. Since the development tool
receives the INFO byte first, it can determine in advance the format of data it is about to receive. The
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
224
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
transmission of the INFO byte starts when a line is complete. Whole bytes are always transmitted. The
grey shaded bytes of Table 6-58 are not transmitted.
Figure 6-32. INFO byte encoding
7
6
5
4
0
TSOVF
TBOVF
TERM
3
2
1
0
Line Format
Table 6-59. Profiling Format Encoding
6.4.6.4
INFO[3:0]
Line Format
Source
Description
0000
PTS
CPU
Initial CPU entry
0001
PTIB
CPU
Indexed jump with up to 31 direct COFs
0010
PTHF
CPU
31 direct COFs without indirect COF
0011
PTVB
CPU
Vector with up to 31 direct COFs
0111
PTW
CPU
Error (Error codes in INFO[7:4])
Others
Reserved
CPU
Reserved
INFO[7:4]
Bit Name
INFO[7]
Reserved
CPU
INFO[6]
TSOVF
CPU
Timestamp Overflow
INFO[5]
TBOVF
CPU
Trace Buffer Overflow
INFO[4]
TERM
CPU
Profiling terminated by disarming
Vector[7:0]
Vector[7:0]
CPU
Device Interrupt Vector Address [8:1]
Description
Reserved
Direct COF Compression
Each branch COF is stored to the trace buffer as a single bit (0=branch not taken, 1=branch taken) until an
indirect COF (indexed jump, return, or interrupt) occurs. The branch COF entries are stored in the byte
fields labelled “Direct” in Table 6-58. These entries start at byte1[0] and continue through to byte4[7], or
until an indirect COF occurs, whichever occurs sooner. The entries use a format whereby the left most
asserted bit is always the stop bit, which indicates that the bit to its right is the first direct COF and byte1[0]
is the last COF that occurred before the indirect COF. This is shown in Table 6-60, whereby the Bytes 4 to
1 of the trace buffer are shown for 3 different cases. The stop bit field for each line is shaded.
In line0, the left most asserted bit is Byte4[7]. This indicates that all remaining 31 bits in the 4-byte field
contain valid direct COF information, whereby each 1 represents branch taken and each 0 represents
branch not taken. The stop bit of line1 indicates that all 30 bits to it’s right are valid, after the 30th direct
COF entry, an indirect COF occurred, that is stored in bytes 7 to 5. In this case the bit to the left of the stop
bit is redundant. Line2 indicates that an indirect COF occurred after 8 direct COF entries. The indirect
COF address is stored in bytes 7 to 5. All bits to the left of the stop bit are redundant.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
225
Chapter 6 S12Z Debug (S12ZDBGV2) Module
Line
Byte4
Byte3
Byte2
Byte1
Line0
1
0
0
1
0
0
1
0
0
1
0
1
1
0
0
1
0
0
1
0
0
0
0
1
1
0
0
0
0
1
1
0
Line1
0
1
1
0
0
1
0
1
1
0
0
1
0
0
1
0
1
1
0
0
1
0
0
1
0
1
1
0
0
1
0
0
Line2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
1
0
0
0
1
Table 6-60. Profiling Direct COF Format
6.4.7
Breakpoints
Breakpoints can be generated by state sequencer transitions to State0. Transitions to State0 are forced by
the following events
• Through comparator matches via Final State.
• Through software writing to the TRIG bit in the DBGC1 register via Final State.
• Through the external event input (DBGEEV) via Final State.
• Through a profiling trace buffer overflow event.
Breakpoints are not generated by software writes to DBGC1 that clear the ARM bit.
6.4.7.1
Breakpoints From Comparator Matches or External Events
Breakpoints can be generated when the state sequencer transitions to State0 following a comparator match
or an external event.
If a tracing session is selected by TSOURCE, the transition to State0 occurs when the tracing session has
completed, thus if Begin or Mid aligned triggering is selected, the breakpoint is requested only on
completion of the subsequent trace. If End aligned tracing or no tracing session is selected, the transition
to State0 and associated breakpoints are immediate.
6.4.7.2
Breakpoints Generated Via The TRIG Bit
When TRIG is written to “1”, the Final State is entered. If a tracing session is selected by TSOURCE,
State0 is entered and breakpoints are requested only when the tracing session has completed, thus if Begin
or Mid aligned triggering is selected, the breakpoint is requested only on completion of the subsequent
trace. If no tracing session is selected, the state sequencer enters State0 immediately and breakpoints are
requested. TRIG breakpoints are possible even if the DBG module is disarmed.
6.4.7.3
DBG Breakpoint Priorities
If a TRIG occurs after Begin or Mid aligned tracing has already been triggered by a comparator instigated
transition to Final State, then TRIG no longer has an effect. When the associated tracing session is
complete, the breakpoint occurs. Similarly if a TRIG is followed by a subsequent comparator match, it has
no effect, since tracing has already started.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
226
Freescale Semiconductor
Chapter 6 S12Z Debug (S12ZDBGV2) Module
6.4.7.3.1
DBG Breakpoint Priorities And BDC Interfacing
Breakpoint operation is dependent on the state of the S12ZBDC module. BDM cannot be entered from a
breakpoint unless the BDC is enabled (ENBDC bit is set in the BDC). If BDM is already active,
breakpoints are disabled. In addition, while executing a BDC STEP1 command, breakpoints are disabled.
When the DBG breakpoints are mapped to BDM (BDMBP set), then if a breakpoint request, either from
a BDC BACKGROUND command or a DBG event, coincides with an SWI instruction in application code,
(i.e. the DBG requests a breakpoint at the next instruction boundary and the next instruction is an SWI)
then the CPU gives priority to the BDM request over the SWI request.
On returning from BDM, the SWI from user code gets executed. Breakpoint generation control is
summarized in Table 6-61.
Table 6-61. Breakpoint Mapping Summary
6.5
6.5.1
BRKCPU
BDMBP Bit
(DBGC1[4])
BDC
Enabled
BDM
Active
Breakpoint
Mapping
0
X
X
X
No Breakpoint
1
0
X
0
Breakpoint to SWI
1
0
1
1
No Breakpoint
1
1
0
X
No Breakpoint
1
1
1
0
Breakpoint to BDM
1
1
1
1
No Breakpoint
Application Information
Avoiding Unintended Breakpoint Re-triggering
Returning from an instruction address breakpoint using an RTI or BDC GO command without PC
modification, returns to the instruction that generated the breakpoint. If an active breakpoint or trigger still
exists at that address, this can re-trigger, disarming the DBG. If configured for BDM breakpoints, the user
must apply the BDC STEP1 command to increment the PC past the current instruction.
If configured for SWI breakpoints, the DBG can be re configured in the SWI routine. If a comparator match
occurs at an SWI vector address then a code SWI and DBG breakpoint SWI could occur simultaneously.
In this case the SWI routine is executed twice before returning.
6.5.2
Debugging Through Reset
To debug through reset, the debugger can recognize a reset occurrence and pull the device BKGD pin low.
This forces the device to leave reset in special single chip (SSC) mode, because the BKGD pin is used as
the MODC signal in the reset phase. When the device leaves reset in SSC mode, CPU execution is halted
and the device is in active BDM. Thus the debugger can configure the DBG for tracing and breakpoints
before returning to application code execution. In this way it is possible to analyze the sequence of events
emerging from reset. The recommended handling of the internal reset scenario is as follows:
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
227
Chapter 6 S12Z Debug (S12ZDBGV2) Module
•
•
•
•
•
•
6.5.3
When a reset occurs the debugger pulls BKGD low until the reset ends, forcing SSC mode entry.
Then the debugger reads the reset flags to determine the cause of reset.
If required, the debugger can read the trace buffer to see what happened just before reset. Since the
trace buffer and DBGCNT register are not affected by resets other than POR.
The debugger configures and arms the DBG to start tracing on returning to application code.
The debugger then sets the PC according to the reset flags.
Then the debugger returns to user code with GO or STEP1.
Breakpoints from other S12Z sources
The DBG is neither affected by CPU BGND instructions, nor by BDC BACKGROUND commands.
6.5.4
Code Profiling
The code profiling data output pin PDO is mapped to a device pin that can also be used as GPIO in an
application. If profiling is required and all pins are required in the application, it is recommended to use
the device pin for a simple output function in the application, without feedback to the chip. In this way the
application can still be profiled, since the pin has no effect on code flow.
The PDO provides a simple bit stream that must be strobed at both edges of the profiling clock when
profiling. The external development tool activates profiling by setting the DBG ARM bit, with PROFILE
and PDOE already set. Thereafter the first bit of the profiling bit stream is valid at the first rising edge of
the profiling clock. No start bit is provided. The external development tool must detect this first rising edge
after arming the DBG. To detect the end of profiling, the DBG ARM bit can be monitored using the BDC.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
228
Freescale Semiconductor
Chapter 7
S12 Clock, Reset and Power Management Unit
(S12CPMU_UHV_V5)
Revision History
Rev. No.
(Item No)
V05.07
V05.08
V05.09
V05.10
V05.11
V05.12
7.1
Date
(Submitted By)
Sections Affected
Substantial Change(s)
25 Feb. 2013
• Format and font corrections
• added “_V5” to block name
3 April 2013
• Format and font corrections
27 June 2013
13 Aug.2013
21 Aug.2013
20 Feb.2014
• PMRF register Bit: corrected description
• some wording improvements
• Signal description: added that availability of BCTL pin is defined
in device specification
• some wording improvements and details
• changed frequency upper limit of external Pierce Oscillator
(XOSCLCP) from 16MHz to 20MHz
• fPLLRST changed to fVCORST
• correct bit numbering for CSAD Bit
• corrected typo in heading of CPMUOSC2 Field Description
• corrected description of CSAD bit
• Refined description of STOP mode entry. Added reference to
device specification because BDC running in Stop mode does
not lead to CPMU going in Stop Mode.
Introduction
This specification describes the function of the Clock, Reset and Power Management Unit
(S12CPMU_UHV_V5).
• The Pierce oscillator (XOSCLCP) provides a robust, low-noise and low-power external clock
source. It is designed for optimal start-up margin with typical crystal oscillators.
• The Voltage regulator (VREGAUTO) operates from the range 6V to 18V. It provides all the
required chip internal voltages and voltage monitors.
• The Phase Locked Loop (PLL) provides a highly accurate frequency multiplier with internal filter.
• The Internal Reference Clock (IRC1M) provides a 1MHz internal clock.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
229
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.1.1
Features
The Pierce Oscillator (XOSCLCP) contains circuitry to dynamically control current gain in the output
amplitude. This ensures a signal with low harmonic distortion, low power and good noise immunity.
• Supports crystals or resonators from 4MHz to 20MHz.
• High noise immunity due to input hysteresis and spike filtering.
• Low RF emissions with peak-to-peak swing limited dynamically
• Transconductance (gm) sized for optimum start-up margin for typical crystals
• Dynamic gain control eliminates the need for external current limiting resistor
• Integrated resistor eliminates the need for external bias resistor
• Low power consumption: Operates from internal 1.8V (nominal) supply, Amplitude control limits
power
• Optional oscillator clock monitor reset
• Optional full swing mode for higher immunity against noise injection on the cost of higher power
consumption and increased emission
The Voltage Regulator (VREGAUTO) has the following features:
• Input voltage range from 6 to 18V (nominal operating range)
• Low-voltage detect (LVD) with low-voltage interrupt (LVI)
• Power-on reset (POR)
• Low-voltage reset (LVR)
• On Chip Temperature Sensor and Bandgap Voltage measurement via internal ADC channel.
• Voltage Regulator providing Full Performance Mode (FPM) and Reduced Performance Mode
(RPM)
• External ballast device support to reduce internal power dissipation
• Capable of supplying both the MCU internally plus external components
• Over-temperature interrupt
The Phase Locked Loop (PLL) has the following features:
• Highly accurate and phase locked frequency multiplier
• Configurable internal filter for best stability and lock time
• Frequency modulation for defined jitter and reduced emission
• Automatic frequency lock detector
• Interrupt request on entry or exit from locked condition
• PLL clock monitor reset
• Reference clock either external (crystal) or internal square wave (1MHz IRC1M) based.
• PLL stability is sufficient for LIN communication in slave mode, even if using IRC1M as reference
clock
The Internal Reference Clock (IRC1M) has the following features:
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
230
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
•
•
Frequency trimming
(A factory trim value for 1MHz is loaded from Flash Memory into the CPMUIRCTRIMH and
CPMUIRCTRIML registers after reset, which can be overwritten by application if required)
Temperature Coefficient (TC) trimming.
(A factory trim value is loaded from Flash Memory into the IRCTRIM register to turn off TC
trimming after reset. Application can trim the TC if required by overwriting the IRCTRIM
register).
Other features of the S12CPMU_UHV_V5 include
• Oscillator clock monitor to detect loss of crystal
• Autonomous periodical interrupt (API)
• Bus Clock Generator
— Clock switch to select either PLLCLK or external crystal/resonator based Bus Clock
— PLLCLK divider to adjust system speed
• System Reset generation from the following possible sources:
— Power-on reset (POR)
— Low-voltage reset (LVR)
— COP system watchdog, COP reset on time-out, windowed COP
— Loss of oscillation (Oscillator clock monitor fail)
— Loss of PLL clock (PLL clock monitor fail)
— External pin RESET
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
231
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.1.2
Modes of Operation
This subsection lists and briefly describes all operating modes supported by the S12CPMU_UHV_V5.
7.1.2.1
Run Mode
The voltage regulator is in Full Performance Mode (FPM).
NOTE
The voltage regulator is active, providing the nominal supply voltages with
full current sourcing capability (see also Appendix for VREG electrical
parameters). The features ACLK clock source, Low Voltage Interrupt (LVI),
Low Voltage Reset (LVR) and Power-On Reset (POR) are available.
The Phase Locked Loop (PLL) is on.
The Internal Reference Clock (IRC1M) is on.
The API is available.
•
•
•
PLL Engaged Internal (PEI)
— This is the default mode after System Reset and Power-On Reset.
— The Bus Clock is based on the PLLCLK.
— After reset the PLL is configured for 50MHz VCOCLK operation.
Post divider is 0x03, so PLLCLK is VCOCLK divided by 4, that is 12.5MHz and Bus Clock is
6.25MHz.
The PLL can be re-configured for other bus frequencies.
— The reference clock for the PLL (REFCLK) is based on internal reference clock IRC1M.
PLL Engaged External (PEE)
— The Bus Clock is based on the PLLCLK.
— This mode can be entered from default mode PEI by performing the following steps:
– Configure the PLL for desired bus frequency.
– Program the reference divider (REFDIV[3:0] bits) to divide down oscillator frequency if
necessary.
– Enable the external oscillator (OSCE bit).
– Wait for oscillator to start up (UPOSC=1) and PLL to lock (LOCK=1).
PLL Bypassed External (PBE)
— The Bus Clock is based on the Oscillator Clock (OSCCLK).
— The PLLCLK is always on to qualify the external oscillator clock. Therefore it is necessary to
make sure a valid PLL configuration is used for the selected oscillator frequency.
— This mode can be entered from default mode PEI by performing the following steps:
– Make sure the PLL configuration is valid for the selected oscillator frequency.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
232
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
– Enable the external oscillator (OSCE bit).
– Wait for oscillator to start up (UPOSC=1).
– Select the Oscillator Clock (OSCCLK) as source of the Bus Clock (PLLSEL=0).
— The PLLCLK is on and used to qualify the external oscillator clock.
7.1.2.2
Wait Mode
For S12CPMU_UHV_V5 Wait Mode is the same as Run Mode.
7.1.2.3
Stop Mode
Stop mode can be entered by executing the CPU STOP instruction. See device level specification for more
details.
The voltage regulator is in Reduced Performance Mode (RPM).
NOTE
The voltage regulator output voltage may degrade to a lower value than in
Full Performance Mode (FPM), additionally the current sourcing capability
is substantially reduced (see also Appendix for VREG electrical
parameters). Only clock source ACLK is available and the Power On Reset
(POR) circuitry is functional. The Low Voltage Interrupt (LVI) and Low
Voltage Reset (LVR) are disabled.
The API is available.
The Phase Locked Loop (PLL) is off.
The Internal Reference Clock (IRC1M) is off.
Core Clock and Bus Clock are stopped.
Depending on the setting of the PSTP and the OSCE bit, Stop Mode can be differentiated between Full
Stop Mode (PSTP = 0 or OSCE=0) and Pseudo Stop Mode (PSTP = 1 and OSCE=1). In addition, the
behavior of the COP in each mode will change based on the clocking method selected by
COPOSCSEL[1:0].
• Full Stop Mode (PSTP = 0 or OSCE=0)
External oscillator (XOSCLCP) is disabled.
— If COPOSCSEL1=0:
The COP and RTI counters halt during Full Stop Mode.
After wake-up from Full Stop Mode the Core Clock and Bus Clock are running on PLLCLK
(PLLSEL=1). COP and RTI are running on IRCCLK (COPOSCSEL0=0, RTIOSCSEL=0).
— If COPOSCSEL1=1:
The clock for the COP is derived from ACLK (trimmable internal RC-Oscillator clock). During
Full Stop Mode the ACLK for the COP can be stopped (COP static) or running (COP active)
depending on the setting of bit CSAD. When bit CSAD is set the ACLK clock source for the
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
233
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
•
COP is stopped during Full Stop Mode and COP continues to operate after exit from Full Stop
Mode. For this COP configuration (ACLK clock source, CSAD set) a latency time (please refer
to CSAD bit description for details) occurs when entering or exiting (Full, Pseudo) Stop Mode.
When bit CSAD is clear the ACLK clock source is on for the COP during Full Stop Mode and
COP is operating.
During Full Stop Mode the RTI counter halts.
After wake-up from Full Stop Mode the Core Clock and Bus Clock are running on PLLCLK
(PLLSEL=1). The COP runs on ACLK and RTI is running on IRCCLK (COPOSCSEL0=0,
RTIOSCSEL=0).
Pseudo Stop Mode (PSTP = 1 and OSCE=1)
External oscillator (XOSCLCP) continues to run.
— If COPOSCSEL1=0:
If the respective enable bits are set (PCE=1 and PRE=1) the COP and RTI will continue to run
with a clock derived from the oscillator clock.
The clock configuration bits PLLSEL, COPOSCSEL0, RTIOSCSEL are unchanged.
— If COPOSCSEL1=1:
If the respective enable bit for the RTI is set (PRE=1) the RTI will continue to run with a clock
derived from the oscillator clock.
The clock for the COP is derived from ACLK (trimmable internal RC-Oscillator clock). During
Pseudo Stop Mode the ACLK for the COP can be stopped (COP static) or running (COP active)
depending on the setting of bit CSAD. When bit CSAD is set the ACLK for the COP is stopped
during Pseudo Stop Mode and COP continues to operate after exit from Pseudo Stop Mode.
For this COP configuration (ACLK clock source, CSAD set) a latency time (please refer to
CSAD bit description for details) occurs when entering or exiting (Pseudo, Full) Stop Mode.
When bit CSAD is clear the ACLK clock source is on for the COP during Pseudo Stop Mode
and COP is operating.
The clock configuration bits PLLSEL, COPOSCSEL0, RTIOSCSEL are unchanged.
NOTE
When starting up the external oscillator (either by programming OSCE bit
to 1 or on exit from Full Stop Mode with OSCE bit already 1) the software
must wait for a minimum time equivalent to the startup-time of the external
oscillator tUPOSC before entering Pseudo Stop Mode.
7.1.2.4
Freeze Mode (BDM active)
For S12CPMU_UHV_V5 Freeze Mode is the same as Run Mode except for RTI and COP which can be
frozen in Active BDM Mode with the RSBCK bit in the CPMUCOP register. After exiting BDM Mode
RTI and COP will resume its operations starting from this frozen status.
Additionally the COP can be forced to the maximum time-out period in Active BDM Mode. For details
please see also the RSBCK and CR[2:0] bit description field of Table 7-13 in Section 7.3.2.10,
“S12CPMU_UHV_V5 COP Control Register (CPMUCOP)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
234
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
235
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.1.3
S12CPMU_UHV_V5 Block Diagram
VSUP
vsup
monitor
ADC
VDDA
Low Voltage Detect VDDA
Low Voltage Detect
VSSA
VDDX
Voltage
VDDX, VDD, VDDF
Regulator
LVRF
6V to 18V
Power-On Detect
(VREGAUTO)
PORF
VSSX
VSS
LVIE Low Voltage Interrupt
LVDS
S12CPMU_UHV
COP time-out
COPRF
PMRF
BCTL
OMRF
osc monitor fail
Power-On Reset
System Reset
Reset
Generator
PLL monitor fail
RESET
OSCCLK
OSCCLK
Monitor
EXTAL
Loop
Controlled
REFDIV[3:0]
IRCTRIM[9:0]
Pierce
XTAL Oscillator
Internal
(XOSCLCP)
Reference
Reference
4MHz-20MHz
Divider
Clock
(IRC1M)
PSTP
OSCMOD
IRCCLK
OSCCLK
UPOSC UPOSC=0 sets PLLSEL bit
REFCLK
FBCLK
Phase
locked
Loop with
internal
Filter (PLL)
Post
Divider
1,2,.32
divide
by 4
Oscillator status Interrupt
OSCIE
PLLSEL
POSTDIV[4:0]
OSCE
Lock
detect
IRCCLK
ECLK2X
(Core Clock)
PLLCLK
HTDS
High
Temperature
Sense
VCOFRQ[1:0]
LOCK
LOCKIE
Divide by
2*(SYNDIV+1)
ACLK
CSAD
SYNDIV[5:0]
divide
by 2
IRCCLK
COPOSCSEL1
Bus Clock
divide
by 2
Watchdog
UPOSC=0 clears
CPMUCOP
API Interrupt
APIE
RTI Interrupt
RTIE
RTICLK
PCE
Autonomous API_EXTCLK
Periodic
Interrupt (API)
APICLK
COP time-out
to Reset
Generator IRCCLK
OSCCLK
COPOSCSEL0
PLL lock interrupt
ACLK
RC
Osc.
COPCLK COP
HT Interrupt
HTIE
VCOCLK
REFFRQ[1:0]
UPOSC
ECLK
divide
by 2 (Bus Clock)
OSCCLK
RTIOSCSEL
Real Time
Interrupt (RTI)
PRE
CPMURTI
Figure 7-1. Block diagram of S12CPMU_UHV_V5
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
236
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Figure 7-2 shows a block diagram of the XOSCLCP.
OSCMOD
Clock monitor fail
Monitor
Peak
Detector
+
_
Gain Control
OSCCLK
VDD=1.8V
VSS
Rf
Quartz Crystals
EXTAL
or
Ceramic Resonators
XTAL
C1
C2
VSS
VSS
Figure 7-2. XOSCLCP Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
237
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.2
Signal Description
This section lists and describes the signals that connect off chip as well as internal supply nodes and special
signals.
7.2.1
RESET
Pin RESET is an active-low bidirectional pin. As an input it initializes the MCU asynchronously to a
known start-up state. As an open-drain output it indicates that an MCU-internal reset has been triggered.
7.2.2
EXTAL and XTAL
These pins provide the interface for a crystal to control the internal clock generator circuitry. EXTAL is
the input to the crystal oscillator amplifier. XTAL is the output of the crystal oscillator amplifier. If
XOSCLCP is enabled, the MCU internal OSCCLK_LCP is derived from the EXTAL input frequency. If
OSCE=0, the EXTAL pin is pulled down by an internal resistor of approximately 200 kΩ and the XTAL
pin is pulled down by an internal resistor of approximately 700 kΩ.
NOTE
Freescale recommends an evaluation of the application board and chosen
resonator or crystal by the resonator or crystal supplier.
The loop controlled circuit (XOSCLCP) is not suited for overtone
resonators and crystals.
7.2.3
VSUP — Regulator Power Input Pin
Pin VSUP is the power input of VREGAUTO. All currents sourced into the regulator loads flow through
this pin.
A suitable reverse battery protection network can be used to connect VSUP to the car battery supply
network.
7.2.4
VDDA, VSSA — Regulator Reference Supply Pins
Pins VDDA and VSSA,are used to supply the analog parts of the regulator. Internal precision reference
circuits are supplied from these signals.
An off-chip decoupling capacitor (220 nF(X7R ceramic)) between VDDA and VSSA is required and can
improve the quality of this supply.
VDDA has to be connected externally to VDDX.
7.2.5
VDDX, VSSX — Pad Supply Pins
VDDX is the supply domain for the digital Pads.
An off-chip decoupling capacitor (10µF plus 220 nF(X7R ceramic)) between VDDX and VSSX is
required.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
238
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
This supply domain is monitored by the Low Voltage Reset circuit.
VDDX has to be connected externally to VDDA.
7.2.6
BCTL — Base Control Pin for external PNP
BCTL is the ballast connection for the on chip voltage regulator. It provides the base current of an external
BJT (PNP) of the VDDX and VDDA supplies. An additional 5.6KΩ resistor between emitter and base of
the BJT is required. See the device specification if this pin is available on this device.
7.2.7
VSS — Core Logic Ground Pin
VSS is the core logic supply return pin. It must be grounded.
7.2.8
VDD — Internal Regulator Output Supply (Core Logic)
Node VDD is a device internal supply output of the voltage regulator that provides the power supply for
the internal core logic.
This supply domain is monitored by the Low Voltage Reset circuit and The Power On Reset circuit.
7.2.9
VDDF — Internal Regulator Output Supply (NVM Logic)
Node VDDF is a device internal supply output of the voltage regulator that provides the power supply for
the NVM logic.
This supply domain is monitored by the Low Voltage Reset circuit.
7.2.10
API_EXTCLK — API external clock output pin
This pin provides the signal selected via APIES and is enabled with APIEA bit. See the device
specification if this clock output is available on this device and to which pin it might be connected.
7.2.11
TEMPSENSE — Internal Temperature Sensor Output Voltage
Depending on the VSEL setting either the voltage level generated by the temperature sensor or the VREG
bandgap voltage is driven to a special channel input of the ADC Converter. See device level specification
for connectivity of ADC special channels.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
239
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3
Memory Map and Registers
This section provides a detailed description of all registers accessible in the S12CPMU_UHV_V5.
7.3.1
Module Memory Map
The S12CPMU_UHV_V5 registers are shown in Figure 7-3.
Address
Offset
Register
Name
Bit 7
6
5
4
3
2
1
Bit 0
0x0000
R
CPMU
RESERVED00 W
0
0
0
0
0
0
0
0
0x0001
R
CPMU
RESERVED01 W
0
0
0
0
0
0
0
0
0x0002
R
CPMU
RESERVED02 W
0
0
0
0
0
0
0
0
R
0
PORF
LVRF
OMRF
PMRF
0x0003
CPMURFLG
0x0004
CPMU
SYNR
0x0005
CPMU
REFDIV
0x0006
CPMU
POSTDIV
0x0007
CPMUIFLG
0x0008
CPMUINT
0x0009
CPMUCLKS
0x000A
CPMUPLL
0x000B
CPMURTI
0x000C
CPMUCOP
0x000D
RESERVED
CPMUTEST0
0x000E
RESERVED
CPMUTEST1
W
R
W
R
W
R
0
VCOFRQ[1:0]
REFFRQ[1:0]
0
SYNDIV[5:0]
0
0
0
0
0
0
0
0
PLLSEL
PSTP
CSAD
COP
OSCSEL1
0
0
FM1
FM0
RTDEC
RTR6
RTR5
WCOP
RSBCK
0
0
0
0
0
REFDIV[3:0]
POSTDIV[4:0]
W
R
W
R
W
R
W
R
RTIF
RTIE
W
R
W
R
W
R
0
COPRF
LOCK
0
0
0
PRE
PCE
RTI
OSCSEL
COP
OSCSEL0
0
0
0
0
RTR4
RTR3
RTR2
RTR1
RTR0
0
0
CR2
CR1
CR0
0
0
0
0
0
0
0
0
0
0
0
0
LOCKIF
LOCKIE
WRTMASK
OSCIF
OSCIE
UPOSC
0
W
R
W
= Unimplemented or Reserved
Figure 7-3. CPMU Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
240
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Address
Offset
Register
Name
0x000F
CPMU
ARMCOP
0x0010
CPMU
HTCTL
0x0011
CPMU
LVCTL
0x0012
CPMU
APICTL
0x0013 CPMUACLKTR
0x0014
CPMUAPIRH
0x0015
CPMUAPIRL
0x0016
RESERVED
CPMUTEST3
0x0017
CPMUHTTR
0x0018
CPMU
IRCTRIMH
0x0019
CPMU
IRCTRIML
0x001A
CPMUOSC
0x001B
CPMUPROT
0x001C
RESERVED
CPMUTEST2
0x001D
CPMU
VREGCTL
0x001E
CPMUOSC2
0x001F
Bit 7
6
5
4
3
2
1
Bit 0
R
0
0
0
0
0
0
0
0
W
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
R
0
0
HTIE
HTIF
0
0
0
LVIE
LVIF
0
0
APIE
APIF
ACLKTR5
ACLKTR4
ACLKTR3
0
0
APIR15
APIR14
APIR13
APIR12
APIR11
APIR10
APIR9
APIR8
APIR7
APIR6
APIR5
APIR4
APIR3
APIR2
APIR1
APIR0
0
0
0
0
0
0
0
0
0
0
0
HTTR3
HTTR2
HTTR1
HTTR0
W
R
VSEL
0
HTE
HTDS
0
0
LVDS
APIES
APIEA
APIFE
W
R
W
R
W
R
W
R
W
R
APICLK
ACLKTR2 ACLKTR1 ACLKTR0
W
R
W
HTOE
R
W
R
W
R
IRCTRIM[9:8]
IRCTRIM[7:0]
W
R
0
TCTRIM[4:0]
OSCE
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Reserved
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
R
W
R
W
R
W
R
CPMU
RESERVED1F W
0
PROT
0
EXTXON
INTXON
OMRE
OSCMOD
0
0
= Unimplemented or Reserved
Figure 7-3. CPMU Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
241
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2
Register Descriptions
This section describes all the S12CPMU_UHV_V5 registers and their individual bits.
Address order is as listed in Figure 7-3
7.3.2.1
S12CPMU_UHV_V5 Reset Flags Register (CPMURFLG)
This register provides S12CPMU_UHV_V5 reset flags.
Module Base + 0x0003
7
R
6
5
PORF
LVRF
Note 1
Note 2
0
4
3
0
2
1
0
OMRF
PMRF
Note 4
Note 5
0
COPRF
W
Reset
0
0
Note 3
0
1. PORF is set to 1 when a power on reset occurs. Unaffected by System Reset.
2. LVRF is set to 1 when a low voltage reset occurs. Unaffected by System Reset. Set by power on reset.
3. COPRF is set to 1 when COP reset occurs. Unaffected by System Reset. Cleared by power on reset.
4. OMRF is set to 1 when an oscillator clock monitor reset occurs. Unaffected by System Reset. Cleared by power on reset.
5. PMRF is set to 1 when a PLL clock monitor reset occurs. Unaffected by System Reset. Cleared by power on reset.
= Unimplemented or Reserved
Figure 7-4. S12CPMU_UHV_V5 Flags Register (CPMURFLG)
Read: Anytime
Write: Refer to each bit for individual write conditions
Table 7-1. CPMURFLG Field Descriptions
Field
Description
6
PORF
Power on Reset Flag — PORF is set to 1 when a power on reset occurs. This flag can only be cleared by writing
a 1. Writing a 0 has no effect.
0 Power on reset has not occurred.
1 Power on reset has occurred.
5
LVRF
Low Voltage Reset Flag — LVRF is set to 1 when a low voltage reset occurs on the VDD, VDDF or VDDX
domain. This flag can only be cleared by writing a 1. Writing a 0 has no effect.
0 Low voltage reset has not occurred.
1 Low voltage reset has occurred.
3
COPRF
COP Reset Flag — COPRF is set to 1 when a COP (Computer Operating Properly) reset occurs. Refer to 7.5.5,
“Computer Operating Properly Watchdog (COP) Reset and 7.3.2.10, “S12CPMU_UHV_V5 COP Control
Register (CPMUCOP) for details.This flag can only be cleared by writing a 1. Writing a 0 has no effect.
0 COP reset has not occurred.
1 COP reset has occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
242
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-1. CPMURFLG Field Descriptions (continued)
Field
Description
1
OMRF
Oscillator Clock Monitor Reset Flag — OMRF is set to 1 when a loss of oscillator (crystal) clock occurs. Refer
to7.5.3, “Oscillator Clock Monitor Reset for details.This flag can only be cleared by writing a 1. Writing a 0 has
no effect.
0 Loss of oscillator clock reset has not occurred.
1 Loss of oscillator clock reset has occurred.
0
PMRF
PLL Clock Monitor Reset Flag — PMRF is set to 1 when a loss of PLL clock occurs. This flag can only be
cleared by writing a 1. Writing a 0 has no effect.
0 Loss of PLL clock reset has not occurred.
1 Loss of PLL clock reset has occurred.
7.3.2.2
S12CPMU_UHV_V5 Synthesizer Register (CPMUSYNR)
The CPMUSYNR register controls the multiplication factor of the PLL and selects the VCO frequency
range.
Module Base + 0x0004
7
6
5
4
3
2
1
0
0
0
0
R
VCOFRQ[1:0]
SYNDIV[5:0]
W
Reset
0
1
0
1
1
Figure 7-5. S12CPMU_UHV_V5 Synthesizer Register (CPMUSYNR)
Read: Anytime
Write: If PROT=0 (CPMUPROT register) and PLLSEL=1 (CPMUCLKS register), then write anytime.
Else write has no effect.
NOTE
Writing to this register clears the LOCK and UPOSC status bits.
If PLL has locked (LOCK=1)
f VCO = 2 × f REF × ( SYNDIV + 1 )
NOTE
fVCO must be within the specified VCO frequency lock range. Bus
frequency fbus must not exceed the specified maximum.
The VCOFRQ[1:0] bits are used to configure the VCO gain for optimal stability and lock time. For correct
PLL operation the VCOFRQ[1:0] bits have to be selected according to the actual target VCOCLK
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
243
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
frequency as shown in Table 7-2. Setting the VCOFRQ[1:0] bits incorrectly can result in a non functional
PLL (no locking and/or insufficient stability).
Table 7-2. VCO Clock Frequency Selection
7.3.2.3
VCOCLK Frequency Ranges
VCOFRQ[1:0]
32MHz <= fVCO <= 48MHz
00
48MHz < fVCO <= 64MHz
01
Reserved
10
Reserved
11
S12CPMU_UHV_V5 Reference Divider Register (CPMUREFDIV)
The CPMUREFDIV register provides a finer granularity for the PLL multiplier steps when using the
external oscillator as reference.
Module Base + 0x0005
7
6
R
5
4
0
0
3
2
REFFRQ[1:0]
1
0
1
1
REFDIV[3:0]
W
Reset
0
0
0
0
1
1
Figure 7-6. S12CPMU_UHV_V5 Reference Divider Register (CPMUREFDIV)
Read: Anytime
Write: If PROT=0 (CPMUPROT register) and PLLSEL=1 (CPMUCLKS register), then write anytime.
Else write has no effect.
NOTE
Write to this register clears the LOCK and UPOSC status bits.
If XOSCLCP is enabled (OSCE=1)
f OSC
f REF = -----------------------------------( REFDIV + 1 )
If XOSCLCP is disabled (OSCE=0)
f REF = f IRC1M
The REFFRQ[1:0] bits are used to configure the internal PLL filter for optimal stability and lock time. For
correct PLL operation the REFFRQ[1:0] bits have to be selected according to the actual REFCLK
frequency as shown in Table 7-3.
If IRC1M is selected as REFCLK (OSCE=0) the PLL filter is fixed configured for the 1MHz <= fREF <=
2MHz range. The bits can still be written but will have no effect on the PLL filter configuration.
For OSCE=1, setting the REFFRQ[1:0] bits incorrectly can result in a non functional PLL (no locking
and/or insufficient stability).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
244
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-3. Reference Clock Frequency Selection if OSC_LCP is enabled
REFCLK Frequency Ranges
(OSCE=1)
REFFRQ[1:0]
1MHz <= fREF <= 2MHz
00
2MHz < fREF <= 6MHz
01
6MHz < fREF <= 12MHz
10
fREF >12MHz
11
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
245
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.4
S12CPMU_UHV_V5 Post Divider Register (CPMUPOSTDIV)
The POSTDIV register controls the frequency ratio between the VCOCLK and the PLLCLK.
Module Base + 0x0006
R
7
6
5
0
0
0
4
3
2
1
0
1
1
POSTDIV[4:0]
W
Reset
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 7-7. S12CPMU_UHV_V5 Post Divider Register (CPMUPOSTDIV)
Read: Anytime
Write: If PLLSEL=1 write anytime, else write has no effect
If PLL is locked (LOCK=1)
f VCO
f PLL = ----------------------------------------( POSTDIV + 1 )
If PLL is not locked (LOCK=0)
f VCO
f PLL = --------------4
If PLL is selected (PLLSEL=1)
f PLL
f bus = ------------2
When changing the POSTDIV[4:0] value or PLL transitions to locked stated (lock=1), it takes up to 32
Bus Clock cycles until fPLL is at the desired target frequency. This is because the post divider gradually
changes (increases or decreases) fPLL in order to avoid sudden load changes for the on-chip voltage
regulator.
7.3.2.5
S12CPMU_UHV_V5 Interrupt Flags Register (CPMUIFLG)
This register provides S12CPMU_UHV_V5 status bits and interrupt flags.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
246
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Module Base + 0x0007
7
R
6
5
0
0
RTIF
4
3
2
LOCK
0
LOCKIF
1
0
UPOSC
OSCIF
W
Reset
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 7-8. S12CPMU_UHV_V5 Flags Register (CPMUIFLG)
Read: Anytime
Write: Refer to each bit for individual write conditions
Table 7-4. CPMUIFLG Field Descriptions
Field
Description
7
RTIF
Real Time Interrupt Flag — RTIF is set to 1 at the end of the RTI period. This flag can only be cleared by writing
a 1. Writing a 0 has no effect. If enabled (RTIE=1), RTIF causes an interrupt request.
0 RTI time-out has not yet occurred.
1 RTI time-out has occurred.
4
LOCKIF
PLL Lock Interrupt Flag — LOCKIF is set to 1 when LOCK status bit changes. This flag can only be cleared by
writing a 1. Writing a 0 has no effect. If enabled (LOCKIE=1), LOCKIF causes an interrupt request.
0 No change in LOCK bit.
1 LOCK bit has changed.
3
LOCK
Lock Status Bit — LOCK reflects the current state of PLL lock condition. Writes have no effect. While PLL is
unlocked (LOCK=0) fPLL is fVCO / 4 to protect the system from high core clock frequencies during the PLL
stabilization time tlock.
0 VCOCLK is not within the desired tolerance of the target frequency.
fPLL = fVCO/4.
1 VCOCLK is within the desired tolerance of the target frequency.
fPLL = fVCO/(POSTDIV+1).
1
OSCIF
Oscillator Interrupt Flag — OSCIF is set to 1 when UPOSC status bit changes. This flag can only be cleared
by writing a 1. Writing a 0 has no effect. If enabled (OSCIE=1), OSCIF causes an interrupt request.
0 No change in UPOSC bit.
1 UPOSC bit has changed.
0
UPOSC
Oscillator Status Bit — UPOSC reflects the status of the oscillator. Writes have no effect. Entering Full Stop
Mode UPOSC is cleared.
0 The oscillator is off or oscillation is not qualified by the PLL.
1 The oscillator is qualified by the PLL.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
247
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.6
S12CPMU_UHV_V5 Interrupt Enable Register (CPMUINT)
This register enables S12CPMU_UHV_V5 interrupt requests.
Module Base + 0x0008
7
R
6
5
0
0
RTIE
4
3
2
0
0
LOCKIE
1
0
0
OSCIE
W
Reset
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 7-9. S12CPMU_UHV_V5 Interrupt Enable Register (CPMUINT)
Read: Anytime
Write: Anytime
Table 7-5. CPMUINT Field Descriptions
Field
7
RTIE
Description
Real Time Interrupt Enable Bit
0 Interrupt requests from RTI are disabled.
1 Interrupt will be requested whenever RTIF is set.
4
LOCKIE
PLL Lock Interrupt Enable Bit
0 PLL LOCK interrupt requests are disabled.
1 Interrupt will be requested whenever LOCKIF is set.
1
OSCIE
Oscillator Corrupt Interrupt Enable Bit
0 Oscillator Corrupt interrupt requests are disabled.
1 Interrupt will be requested whenever OSCIF is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
248
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.7
S12CPMU_UHV_V5 Clock Select Register (CPMUCLKS)
This register controls S12CPMU_UHV_V5 clock selection.
Module Base + 0x0009
7
6
5
4
3
2
1
0
PLLSEL
PSTP
CSAD
COP
OSCSEL1
PRE
PCE
RTI
OSCSEL
COP
OSCSEL0
1
0
0
0
0
0
0
0
R
W
Reset
= Unimplemented or Reserved
Figure 7-10. S12CPMU_UHV_V5 Clock Select Register (CPMUCLKS)
Read: Anytime
Write:
•
•
•
•
•
•
Only possible if PROT=0 (CPMUPROT register) in all MCU Modes (Normal and Special Mode).
All bits in Special Mode (if PROT=0).
PLLSEL, PSTP, PRE, PCE, RTIOSCSEL: In Normal Mode (if PROT=0).
CSAD: In Normal Mode (if PROT=0) until CPMUCOP write once has taken place.
COPOSCSEL0: In Normal Mode (if PROT=0) until CPMUCOP write once has taken place.
If COPOSCSEL0 was cleared by UPOSC=0 (entering Full Stop Mode with COPOSCSEL0=1 or
insufficient OSCCLK quality), then COPOSCSEL0 can be set once again.
COPOSCSEL1: In Normal Mode (if PROT=0) until CPMUCOP write once has taken place.
COPOSCSEL1 will not be cleared by UPOSC=0 (entering Full Stop Mode with COPOSCSEL1=1
or insufficient OSCCLK quality if OSCCLK is used as clock source for other clock domains: for
instance core clock etc.).
NOTE
After writing CPMUCLKS register, it is strongly recommended to read
back CPMUCLKS register to make sure that write of PLLSEL,
RTIOSCSEL and COPOSCSEL was successful. This is because under
certain circumstances writes have no effect or bits are automatically
changed (see CPMUCLKS register and bit descriptions).
NOTE
When using the oscillator clock as system clock (write PLLSEL = 0) it is
highly recommended to enable the oscillator clock monitor reset feature
(write OMRE = 1 in CPMUOSC2 register). If the oscillator monitor reset
feature is disabled (OMRE = 0) and the oscillator clock is used as system
clock, the system will stall in case of loss of oscillation.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
249
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-6. CPMUCLKS Descriptions
Field
7
PLLSEL
Description
PLL Select Bit
This bit selects the PLLCLK as source of the System Clocks (Core Clock and Bus Clock).
PLLSEL can only be set to 0, if UPOSC=1.
UPOSC= 0 sets the PLLSEL bit.
Entering Full Stop Mode sets the PLLSEL bit.
0 System clocks are derived from OSCCLK if oscillator is up (UPOSC=1, fbus = fosc / 2).
1 System clocks are derived from PLLCLK, fbus = fPLL / 2.
6
PSTP
Pseudo Stop Bit
This bit controls the functionality of the oscillator during Stop Mode.
0 Oscillator is disabled in Stop Mode (Full Stop Mode).
1 Oscillator continues to run in Stop Mode (Pseudo Stop Mode), option to run RTI and COP.
Note: Pseudo Stop Mode allows for faster STOP recovery and reduces the mechanical stress and aging of the
resonator in case of frequent STOP conditions at the expense of a slightly increased power consumption.
Note: When starting up the external oscillator (either by programming OSCE bit to 1 or on exit from Full Stop
Mode with OSCE bit already 1) the software must wait for a minimum time equivalent to the startup-time
of the external oscillator tUPOSC before entering Pseudo Stop Mode.
5
CSAD
COP in Stop Mode ACLK Disable — If this bit is set the ACLK for the COP in Stop Mode is disabled. Hence
the COP is static while in Stop Mode and continues to operate after exit from Stop Mode.
For CSAD = 1 and COP is running on ACLK (COPOSCSEL1 = 1) the following applies:
Due to clock domain crossing synchronization there is a latency time of 2 ACLK cycles to enter Stop Mode.
After exit from STOP mode (when interrupt service routine is entered) the software has to wait for 2 ACLK
cycles before it is allowed to enter Stop mode again (STOP instruction). It is absolutely forbidden to enter
Stop Mode before this time of 2 ACLK cycles has elapsed.
0 COP running in Stop Mode (ACLK for COP enabled in Stop Mode).
1 COP stopped in Stop Mode (ACLK for COP disabled in Stop Mode)
4
COP
OSCSEL1
COP Clock Select 1 — COPOSCSEL0 and COPOSCSEL1 combined determine the clock source to the COP
(see also Table 7-7).
If COPOSCSEL1 = 1, COPOSCSEL0 has no effect regarding clock select and changing the COPOSCSEL0 bit
does not re-start the COP time-out period.
COPOSCSEL1 selects the clock source to the COP to be either ACLK (derived from trimmable internal RCOscillator) or clock selected via COPOSCSEL0 (IRCCLK or OSCCLK).
Changing the COPOSCSEL1 bit re-starts the COP time-out period.
COPOSCSEL1 can be set independent from value of UPOSC.
UPOSC= 0 does not clear the COPOSCSEL1 bit.
0 COP clock source defined by COPOSCSEL0
1 COP clock source is ACLK derived from a trimmable internal RC-Oscillator
3
PRE
RTI Enable During Pseudo Stop Bit — PRE enables the RTI during Pseudo Stop Mode.
0 RTI stops running during Pseudo Stop Mode.
1 RTI continues running during Pseudo Stop Mode if RTIOSCSEL=1.
Note: If PRE=0 or RTIOSCSEL=0 then the RTI will go static while Stop Mode is active. The RTI counter will not
be reset.
2
PCE
COP Enable During Pseudo Stop Bit — PCE enables the COP during Pseudo Stop Mode.
0 COP stops running during Pseudo Stop Mode
1 COP continues running during Pseudo Stop Mode if COPOSCSEL=1
Note: If PCE=0 or COPOSCSEL=0 then the COP will go static while Stop Mode is active. The COP counter will
not be reset.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
250
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-6. CPMUCLKS Descriptions (continued)
Field
Description
1
RTI Clock Select— RTIOSCSEL selects the clock source to the RTI. Either IRCCLK or OSCCLK. Changing the
RTIOSCSEL RTIOSCSEL bit re-starts the RTI time-out period.
RTIOSCSEL can only be set to 1, if UPOSC=1.
UPOSC= 0 clears the RTIOSCSEL bit.
0 RTI clock source is IRCCLK.
1 RTI clock source is OSCCLK.
0
COP
OSCSEL0
COP Clock Select 0 — COPOSCSEL0 and COPOSCSEL1 combined determine the clock source to the COP
(see also Table 7-7)
If COPOSCSEL1 = 1, COPOSCSEL0 has no effect regarding clock select and changing the COPOSCSEL0 bit
does not re-start the COP time-out period.
When COPOSCSEL1=0,COPOSCSEL0 selects the clock source to the COP to be either IRCCLK or OSCCLK.
Changing the COPOSCSEL0 bit re-starts the COP time-out period.
COPOSCSEL0 can only be set to 1, if UPOSC=1.
UPOSC= 0 clears the COPOSCSEL0 bit.
0 COP clock source is IRCCLK.
1 COP clock source is OSCCLK
Table 7-7. COPOSCSEL1, COPOSCSEL0 clock source select description
COPOSCSEL1
COPOSCSEL0
COP clock source
0
0
IRCCLK
0
1
OSCCLK
1
x
ACLK
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
251
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.8
S12CPMU_UHV_V5 PLL Control Register (CPMUPLL)
This register controls the PLL functionality.
Module Base + 0x000A
R
7
6
0
0
5
4
FM1
FM0
0
0
3
2
1
0
0
0
0
0
0
0
0
0
W
Reset
0
0
Figure 7-11. S12CPMU_UHV_V5 PLL Control Register (CPMUPLL)
Read: Anytime
Write: Anytime if PROT=0 (CPMUPROT register) and PLLSEL=1 (CPMUCLKS register). Else write has
no effect.
NOTE
Write to this register clears the LOCK and UPOSC status bits.
NOTE
Care should be taken to ensure that the bus frequency does not exceed the
specified maximum when frequency modulation is enabled.
Table 7-8. CPMUPLL Field Descriptions
Field
Description
5, 4
FM1, FM0
PLL Frequency Modulation Enable Bits — FM1 and FM0 enable frequency modulation on the VCOCLK. This
is to reduce noise emission. The modulation frequency is fref divided by 16. See Table 7-9 for coding.
Table 7-9. FM Amplitude selection
FM1
FM0
FM Amplitude /
fVCO Variation
0
0
FM off
0
1
±1%
1
0
±2%
1
1
±4%
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
252
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.9
S12CPMU_UHV_V5 RTI Control Register (CPMURTI)
This register selects the time-out period for the Real Time Interrupt.
The clock source for the RTI is either IRCCLK or OSCCLK depending on the setting of the RTIOSCSEL
bit. In Stop Mode with PSTP=1 (Pseudo Stop Mode) and RTIOSCSEL=1 the RTI continues to run, else
the RTI counter halts in Stop Mode.
Module Base + 0x000B
7
6
5
4
3
2
1
0
RTDEC
RTR6
RTR5
RTR4
RTR3
RTR2
RTR1
RTR0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 7-12. S12CPMU_UHV_V5 RTI Control Register (CPMURTI)
Read: Anytime
Write: Anytime
NOTE
A write to this register starts the RTI time-out period. A change of the
RTIOSCSEL bit (writing a different value or loosing UPOSC status) restarts the RTI time-out period.
Table 7-10. CPMURTI Field Descriptions
Field
Description
7
RTDEC
Decimal or Binary Divider Select Bit — RTDEC selects decimal or binary based prescaler values.
0 Binary based divider value. See Table 7-11
1 Decimal based divider value. See Table 7-12
6–4
RTR[6:4]
Real Time Interrupt Prescale Rate Select Bits — These bits select the prescale rate for the RTI.See Table 711 and Table 7-12.
3–0
RTR[3:0]
Real Time Interrupt Modulus Counter Select Bits — These bits select the modulus counter target value to
provide additional granularity.Table 7-11 and Table 7-12 show all possible divide values selectable by the
CPMURTI register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
253
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-11. RTI Frequency Divide Rates for RTDEC = 0
RTR[6:4] =
RTR[3:0]
000
(OFF)
001
(210)
010
(211)
011
(212)
100
(213)
101
(214)
110
(215)
111
(216)
0000 (÷1)
OFF(1)
210
211
212
213
214
215
216
0001 (÷2)
OFF
2x210
2x211
2x212
2x213
2x214
2x215
2x216
0010 (÷3)
OFF
3x210
3x211
3x212
3x213
3x214
3x215
3x216
0011 (÷4)
OFF
4x210
4x211
4x212
4x213
4x214
4x215
4x216
0100 (÷5)
OFF
5x210
5x211
5x212
5x213
5x214
5x215
5x216
0101 (÷6)
OFF
6x210
6x211
6x212
6x213
6x214
6x215
6x216
0110 (÷7)
OFF
7x210
7x211
7x212
7x213
7x214
7x215
7x216
0111 (÷8)
OFF
8x210
8x211
8x212
8x213
8x214
8x215
8x216
1000 (÷9)
OFF
9x210
9x211
9x212
9x213
9x214
9x215
9x216
1001 (÷10)
OFF
10x210
10x211
10x212
10x213
10x214
10x215
10x216
1010 (÷11)
OFF
11x210
11x211
11x212
11x213
11x214
11x215
11x216
1011 (÷12)
OFF
12x210
12x211
12x212
12x213
12x214
12x215
12x216
1100 (÷13)
OFF
13x210
13x211
13x212
13x213
13x214
13x215
13x216
1101 (÷14)
OFF
14x210
14x211
14x212
14x213
14x214
14x215
14x216
1110 (÷15)
OFF
15x210
15x211
15x212
15x213
15x214
15x215
15x216
1111 (÷16)
OFF
16x210
16x211
16x212
16x213
16x214
16x215
16x216
1. Denotes the default value out of reset.This value should be used to disable the RTI to ensure future backwards compatibility.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
254
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-12. RTI Frequency Divide Rates for RTDEC=1
RTR[6:4] =
RTR[3:0]
000
(1x103)
001
(2x103)
010
(5x103)
011
(10x103)
100
(20x103)
101
(50x103)
110
(100x103)
111
(200x103)
0000 (÷1)
1x103
2x103
5x103
10x103
20x103
50x103
100x103
200x103
0001 (÷2)
2x103
4x103
10x103
20x103
40x103
100x103
200x103
400x103
0010 (÷3)
3x103
6x103
15x103
30x103
60x103
150x103
300x103
600x103
0011 (÷4)
4x103
8x103
20x103
40x103
80x103
200x103
400x103
800x103
0100 (÷5)
5x103
10x103
25x103
50x103
100x103
250x103
500x103
1x106
0101 (÷6)
6x103
12x103
30x103
60x103
120x103
300x103
600x103
1.2x106
0110 (÷7)
7x103
14x103
35x103
70x103
140x103
350x103
700x103
1.4x106
0111 (÷8)
8x103
16x103
40x103
80x103
160x103
400x103
800x103
1.6x106
1000 (÷9)
9x103
18x103
45x103
90x103
180x103
450x103
900x103
1.8x106
1001 (÷10)
10 x103
20x103
50x103
100x103
200x103
500x103
1x106
2x106
1010 (÷11)
11 x103
22x103
55x103
110x103
220x103
550x103
1.1x106
2.2x106
1011 (÷12)
12x103
24x103
60x103
120x103
240x103
600x103
1.2x106
2.4x106
1100 (÷13)
13x103
26x103
65x103
130x103
260x103
650x103
1.3x106
2.6x106
1101 (÷14)
14x103
28x103
70x103
140x103
280x103
700x103
1.4x106
2.8x106
1110 (÷15)
15x103
30x103
75x103
150x103
300x103
750x103
1.5x106
3x106
1111 (÷16)
16x103
32x103
80x103
160x103
320x103
800x103
1.6x106
3.2x106
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
255
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.10
S12CPMU_UHV_V5 COP Control Register (CPMUCOP)
This register controls the COP (Computer Operating Properly) watchdog.
The clock source for the COP is either ACLK, IRCCLK or OSCCLK depending on the setting of the
COPOSCSEL0 and COPOSCSEL1 bit (see also Table 7-7).
In Stop Mode with PSTP=1 (Pseudo Stop Mode), COPOSCSEL0=1 and COPOSCEL1=0 and PCE=1 the
COP continues to run, else the COP counter halts in Stop Mode with COPOSCSEL1 =0.
In Full Stop Mode and Pseudo Stop Mode with COPOSCSEL1=1 the COP continues to run.
Module Base + 0x000C
7
6
WCOP
RSBCK
R
W
Reset
5
4
3
0
0
0
2
1
0
CR2
CR1
CR0
F
F
F
WRTMASK
F
0
0
0
0
After de-assert of System Reset the values are automatically loaded from the Flash memory. See Device specification for
details.
= Unimplemented or Reserved
Figure 7-13. S12CPMU_UHV_V5 COP Control Register (CPMUCOP)
Read: Anytime
Write:
1. RSBCK: Anytime in Special Mode; write to “1” but not to “0” in Normal Mode
2. WCOP, CR2, CR1, CR0:
— Anytime in Special Mode, when WRTMASK is 0, otherwise it has no effect
— Write once in Normal Mode, when WRTMASK is 0, otherwise it has no effect.
– Writing CR[2:0] to “000” has no effect, but counts for the “write once” condition.
– Writing WCOP to “0” has no effect, but counts for the “write once” condition.
When a non-zero value is loaded from Flash to CR[2:0] the COP time-out period is started.
A change of the COPOSCSEL0 or COPOSCSEL1 bit (writing a different value) or loosing UPOSC status
while COPOSCSEL1 is clear and COPOSCSEL0 is set, re-starts the COP time-out period.
In Normal Mode the COP time-out period is restarted if either of these conditions is true:
1. Writing a non-zero value to CR[2:0] (anytime in special mode, once in normal mode) with
WRTMASK = 0.
2. Writing WCOP bit (anytime in Special Mode, once in Normal Mode) with WRTMASK = 0.
3. Changing RSBCK bit from “0” to “1”.
In Special Mode, any write access to CPMUCOP register restarts the COP time-out period.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
256
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-13. CPMUCOP Field Descriptions
Field
Description
7
WCOP
Window COP Mode Bit — When set, a write to the CPMUARMCOP register must occur in the last 25% of the
selected period. A write during the first 75% of the selected period generates a COP reset. As long as all writes
occur during this window, $55 can be written as often as desired. Once $AA is written after the $55, the time-out
logic restarts and the user must wait until the next window before writing to CPMUARMCOP. Table 7-14 shows
the duration of this window for the seven available COP rates.
0 Normal COP operation
1 Window COP operation
6
RSBCK
COP and RTI Stop in Active BDM Mode Bit
0 Allows the COP and RTI to keep running in Active BDM mode.
1 Stops the COP and RTI counters whenever the part is in Active BDM mode.
5
Write Mask for WCOP and CR[2:0] Bit — This write-only bit serves as a mask for the WCOP and CR[2:0] bits
WRTMASK while writing the CPMUCOP register. It is intended for BDM writing the RSBCK without changing the content of
WCOP and CR[2:0].
0 Write of WCOP and CR[2:0] has an effect with this write of CPMUCOP
1 Write of WCOP and CR[2:0] has no effect with this write of CPMUCOP.
(Does not count for “write once”.)
2–0
CR[2:0]
COP Watchdog Timer Rate Select — These bits select the COP time-out rate (see Table 7-14 and Table 7-15).
Writing a nonzero value to CR[2:0] enables the COP counter and starts the time-out period. A COP counter timeout causes a System Reset. This can be avoided by periodically (before time-out) initializing the COP counter
via the CPMUARMCOP register.
While all of the following four conditions are true the CR[2:0], WCOP bits are ignored and the COP operates at
highest time-out period (2 24 cycles) in normal COP mode (Window COP mode disabled):
1) COP is enabled (CR[2:0] is not 000)
2) BDM mode active
3) RSBCK = 0
4) Operation in Special Mode
Table 7-14. COP Watchdog Rates if COPOSCSEL1=0.
(default out of reset)
CR2
CR1
CR0
COPCLK
Cycles to time-out
(COPCLK is either IRCCLK or
OSCCLK depending on the
COPOSCSEL0 bit)
0
0
0
COP disabled
0
0
1
2 14
0
1
0
2 16
0
1
1
2 18
1
0
0
2 20
1
0
1
2 22
1
1
0
2 23
1
1
1
2 24
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
257
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-15. COP Watchdog Rates if COPOSCSEL1=1.
CR2
CR1
CR0
COPCLK
Cycles to time-out
(COPCLK is ACLK divided by 2)
0
0
0
COP disabled
0
0
1
27
0
1
0
29
0
1
1
2 11
1
0
0
2 13
1
0
1
2 15
1
1
0
2 16
1
1
1
2 17
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
258
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.11
Reserved Register CPMUTEST0
NOTE
This reserved register is designed for factory test purposes only, and is not
intended for general user access. Writing to this register when in Special
Mode can alter the S12CPMU_UHV_V5’s functionality.
Module Base + 0x000D
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 7-14. Reserved Register (CPMUTEST0)
Read: Anytime
Write: Only in Special Mode
7.3.2.12
Reserved Register CPMUTEST1
NOTE
This reserved register is designed for factory test purposes only, and is not
intended for general user access. Writing to this register when in Special
Mode can alter the S12CPMU_UHV_V5’s functionality.
Module Base + 0x000E
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 7-15. Reserved Register (CPMUTEST1)
Read: Anytime
Write: Only in Special Mode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
259
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.13
S12CPMU_UHV_V5 COP Timer Arm/Reset Register (CPMUARMCOP)
This register is used to restart the COP time-out period.
Module Base + 0x000F
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
W ARMCOP-Bit ARMCOP-Bit ARMCOP-Bit ARMCOP-Bit ARMCOP-Bit ARMCOP-Bit ARMCOP-Bit ARMCOP-Bit
7
6
5
4
3
2
1
0
Reset
0
0
0
0
0
0
0
0
Figure 7-16. S12CPMU_UHV_V5 CPMUARMCOP Register
Read: Always reads $00
Write: Anytime
When the COP is disabled (CR[2:0] = “000”) writing to this register has no effect.
When the COP is enabled by setting CR[2:0] nonzero, the following applies:
Writing any value other than $55 or $AA causes a COP reset. To restart the COP time-out period
write $55 followed by a write of $AA. These writes do not need to occur back-to-back, but the
sequence ($55, $AA) must be completed prior to COP end of time-out period to avoid a COP reset.
Sequences of $55 writes are allowed. When the WCOP bit is set, $55 and $AA writes must be done
in the last 25% of the selected time-out period; writing any value in the first 75% of the selected
period will cause a COP reset.
7.3.2.14
High Temperature Control Register (CPMUHTCTL)
The CPMUHTCTL register configures the temperature sense features.
Module Base + 0x0010
R
7
6
0
0
W
Reset
0
0
5
VSEL
0
4
0
0
3
HTE
0
2
HTDS
0
1
0
HTIE
HTIF
0
0
= Unimplemented or Reserved
Figure 7-17. High Temperature Control Register (CPMUHTCTL)
Read: Anytime
Write: VSEL, HTE, HTIE and HTIF are write anytime, HTDS is read only
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
260
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-16. CPMUHTCTL Field Descriptions
Field
Description
5
VSEL
Voltage Access Select Bit — If set, the bandgap reference voltage VBG can be accessed internally (i.e.
multiplexed to an internal Analog to Digital Converter channel). If not set, the die temperature proportional
voltage VHT of the temperature sensor can be accessed internally. See device level specification for connectivity.
For any of these access the HTE bit must be set.
0 An internal temperature proportional voltage VHT can be accessed internally.
1 Bandgap reference voltage VBG can be accessed internally.
3
HTE
High Temperature Sensor/Bandgap Voltage Enable Bit — This bit enables the high temperature sensor and
bandgap voltage amplifier.
0 The temperature sensor and bandgap voltage amplifier is disabled.
1 The temperature sensor and bandgap voltage amplifier is enabled.
2
HTDS
High Temperature Detect Status Bit — This read-only status bit reflects the temperature status. Writes have
no effect.
0 Junction Temperature is below level THTID or RPM.
1 Junction Temperature is above level THTIA and FPM.
1
HTIE
High Temperature Interrupt Enable Bit
0 Interrupt request is disabled.
1 Interrupt will be requested whenever HTIF is set.
0
HTIF
High Temperature Interrupt Flag — HTIF is set to 1 when HTDS status bit changes. This flag can only be
cleared by writing a 1.
Writing a 0 has no effect. If enabled (HTIE=1), HTIF causes an interrupt request.
0 No change in HTDS bit.
1 HTDS bit has changed.
Figure 7-18. Voltage Access Select
VBG
Ref
VSEL
TEMPSENSE
ADC
Channel
C
HTD
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
261
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.15
Low Voltage Control Register (CPMULVCTL)
The CPMULVCTL register allows the configuration of the low-voltage detect features.
Module Base + 0x0011
R
7
6
5
4
3
2
0
0
0
0
0
LVDS
0
0
0
0
0
U
W
Reset
1
0
LVIE
LVIF
0
U
The Reset state of LVDS and LVIF depends on the external supplied VDDA level
= Unimplemented or Reserved
Figure 7-19. Low Voltage Control Register (CPMULVCTL)
Read: Anytime
Write: LVIE and LVIF are write anytime, LVDS is read only
Table 7-17. CPMULVCTL Field Descriptions
Field
Description
2
LVDS
Low-Voltage Detect Status Bit — This read-only status bit reflects the voltage level on VDDA. Writes have no
effect.
0 Input voltage VDDA is above level VLVID or RPM.
1 Input voltage VDDA is below level VLVIA and FPM.
1
LVIE
Low-Voltage Interrupt Enable Bit
0 Interrupt request is disabled.
1 Interrupt will be requested whenever LVIF is set.
0
LVIF
Low-Voltage Interrupt Flag — LVIF is set to 1 when LVDS status bit changes. This flag can only be cleared by
writing a 1. Writing a 0 has no effect. If enabled (LVIE = 1), LVIF causes an interrupt request.
0 No change in LVDS bit.
1 LVDS bit has changed.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
262
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.16
Autonomous Periodical Interrupt Control Register (CPMUAPICTL)
The CPMUAPICTL register allows the configuration of the autonomous periodical interrupt features.
Module Base + 0x0012
7
R
W
Reset
APICLK
0
6
5
0
0
0
0
4
3
2
1
0
APIES
APIEA
APIFE
APIE
APIF
0
0
0
0
0
= Unimplemented or Reserved
Figure 7-20. Autonomous Periodical Interrupt Control Register (CPMUAPICTL)
Read: Anytime
Write: Anytime
Table 7-18. CPMUAPICTL Field Descriptions
Field
7
APICLK
Description
Autonomous Periodical Interrupt Clock Select Bit — Selects the clock source for the API. Writable only if
APIFE = 0. APICLK cannot be changed if APIFE is set by the same write operation.
0 Autonomous Clock (ACLK) used as source.
1 Bus Clock used as source.
4
APIES
Autonomous Periodical Interrupt External Select Bit — Selects the waveform at the external pin
API_EXTCLK as shown in Figure 7-21. See device level specification for connectivity of API_EXTCLK pin.
0 If APIEA and APIFE are set, at the external pin API_EXTCLK periodic high pulses are visible at the end of
every selected period with the size of half of the minimum period (APIR=0x0000 in Table 7-22).
1 If APIEA and APIFE are set, at the external pin API_EXTCLK a clock is visible with 2 times the selected API
Period.
3
APIEA
Autonomous Periodical Interrupt External Access Enable Bit — If set, the waveform selected by bit APIES
can be accessed externally. See device level specification for connectivity.
0 Waveform selected by APIES can not be accessed externally.
1 Waveform selected by APIES can be accessed externally, if APIFE is set.
2
APIFE
Autonomous Periodical Interrupt Feature Enable Bit — Enables the API feature and starts the API timer
when set.
0 Autonomous periodical interrupt is disabled.
1 Autonomous periodical interrupt is enabled and timer starts running.
1
APIE
Autonomous Periodical Interrupt Enable Bit
0 API interrupt request is disabled.
1 API interrupt will be requested whenever APIF is set.
0
APIF
Autonomous Periodical Interrupt Flag — APIF is set to 1 when the in the API configured time has elapsed.
This flag can only be cleared by writing a 1.Writing a 0 has no effect. If enabled (APIE = 1), APIF causes an
interrupt request.
0 API time-out has not yet occurred.
1 API time-out has occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
263
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Figure 7-21. Waveform selected on API_EXTCLK pin (APIEA=1, APIFE=1)
API min. period / 2
APIES=0
API period
APIES=1
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
264
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.17
Autonomous Clock Trimming Register (CPMUACLKTR)
The CPMUACLKTR register configures the trimming of the Autonomous Clock (ACLK - trimmable
internal RC-Oscillator) which can be selected as clock source for some CPMU features.
Module Base + 0x0013
7
R
W
Reset
6
5
4
3
2
ACLKTR5
ACLKTR4
ACLKTR3
ACLKTR2
ACLKTR1
ACLKTR0
F
F
F
F
F
F
1
0
0
0
0
0
After de-assert of System Reset a value is automatically loaded from the Flash memory.
Figure 7-22. Autonomous Clock Trimming Register (CPMUACLKTR)
Read: Anytime
Write: Anytime
Table 7-19. CPMUACLKTR Field Descriptions
Field
Description
7–2
Autonomous Clock Period Trimming Bits — See Table 7-20 for trimming effects. The ACLKTR[5:0] value
ACLKTR[5:0] represents a signed number influencing the ACLK period time.
Table 7-20. Trimming Effect of ACLKTR[5:0]
Bit
Trimming Effect
ACLKTR[5]
Increases period
ACLKTR[4]
Decreases period less than ACLKTR[5] increased it
ACLKTR[3]
Decreases period less than ACLKTR[4]
ACLKTR[2]
Decreases period less than ACLKTR[3]
ACLKTR[1]
Decreases period less than ACLKTR[2]
ACLKTR[0]
Decreases period less than ACLKTR[1]
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
265
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.18
Autonomous Periodical Interrupt Rate High and Low Register
(CPMUAPIRH / CPMUAPIRL)
The CPMUAPIRH and CPMUAPIRL registers allow the configuration of the autonomous periodical
interrupt rate.
Module Base + 0x0014
R
W
Reset
7
6
5
4
3
2
1
0
APIR15
APIR14
APIR13
APIR12
APIR11
APIR10
APIR9
APIR8
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 7-23. Autonomous Periodical Interrupt Rate High Register (CPMUAPIRH)
Module Base + 0x0015
R
W
Reset
7
6
5
4
3
2
1
0
APIR7
APIR6
APIR5
APIR4
APIR3
APIR2
APIR1
APIR0
0
0
0
0
0
0
0
0
Figure 7-24. Autonomous Periodical Interrupt Rate Low Register (CPMUAPIRL)
Read: Anytime
Write: Anytime if APIFE=0, Else writes have no effect.
Table 7-21. CPMUAPIRH / CPMUAPIRL Field Descriptions
Field
Description
15-0
APIR[15:0]
Autonomous Periodical Interrupt Rate Bits — These bits define the time-out period of the API. See Table 722 for details of the effect of the autonomous periodical interrupt rate bits.
The period can be calculated as follows depending on logical value of the APICLK bit:
APICLK=0: Period = 2*(APIR[15:0] + 1) * (ACLK Clock Period * 2)
APICLK=1: Period = 2*(APIR[15:0] + 1) * Bus Clock Period
NOTE
For APICLK bit clear the first time-out period of the API will show a latency
time between two to three fACLK cycles due to synchronous clock gate
release when the API feature gets enabled (APIFE bit set).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
266
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-22. Selectable Autonomous Periodical Interrupt Periods
APICLK
APIR[15:0]
Selected Period
0
0000
0.2 ms(1)
0
0001
0.4 ms1
0
0002
0.6 ms1
0
0003
0.8 ms1
0
0004
1.0 ms1
0
0005
1.2 ms1
0
.....
.....
0
FFFD
13106.8 ms1
0
FFFE
13107.0 ms1
0
FFFF
13107.2 ms1
1
0000
2 * Bus Clock period
1
0001
4 * Bus Clock period
1
0002
6 * Bus Clock period
1
0003
8 * Bus Clock period
1
0004
10 * Bus Clock period
1
0005
12 * Bus Clock period
1
.....
.....
1
FFFD
131068 * Bus Clock period
1
FFFE
131070 * Bus Clock period
1
FFFF
1. When fACLK is trimmed to 20KHz.
131072 * Bus Clock period
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
267
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.19
Reserved Register CPMUTEST3
NOTE
This reserved register is designed for factory test purposes only, and is not
intended for general user access. Writing to this register when in Special
Mode can alter the S12CPMU_UHV_V5’s functionality.
Module Base + 0x0016
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 7-25. Reserved Register (CPMUTEST3)
Read: Anytime
Write: Only in Special Mode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
268
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.20
High Temperature Trimming Register (CPMUHTTR)
The CPMUHTTR register configures the trimming of the S12CPMU_UHV_V5 temperature sense.
Module Base + 0x0017
7
R
W
Reset
HTOE
0
6
5
4
0
0
0
0
0
0
3
2
1
0
HTTR3
HTTR2
HTTR1
HTTR0
F
F
F
F
After de-assert of System Reset a trim value is automatically loaded from the Flash memory. See Device specification for
details.
= Unimplemented or Reserved
Figure 7-26. High Temperature Trimming Register (CPMUHTTR)
Read: Anytime
Write: Anytime
Table 7-24. CPMUHTTR Field Descriptions
Field
7
HTOE
3–0
HTTR[3:0]
Description
High Temperature Offset Enable Bit — If set the temperature sense offset is enabled.
0 The temperature sense offset is disabled. HTTR[3:0] bits don’t care.
1 The temperature sense offset is enabled. HTTR[3:0] select the temperature offset.
High Temperature Trimming Bits — See Table 7-25 for trimming effects.
Table 7-25. Trimming Effect of HTTR
Bit
Trimming Effect
HTTR[3]
Increases VHT twice of HTTR[2]
HTTR[2]
Increases VHT twice of HTTR[1]
HTTR[1]
Increases VHT twice of HTTR[0]
HTTR[0]
Increases VHT (to compensate Temperature Offset)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
269
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.21
S12CPMU_UHV_V5 IRC1M Trim Registers (CPMUIRCTRIMH /
CPMUIRCTRIML)
Module Base + 0x0018
15
14
13
12
11
R
10
9
8
0
TCTRIM[4:0]
IRCTRIM[9:8]
W
Reset
F
F
F
F
F
0
F
F
After de-assert of System Reset a factory programmed trim value is automatically loaded from the Flash memory to
provide trimmed Internal Reference Frequency fIRC1M_TRIM.
Figure 7-27. S12CPMU_UHV_V5 IRC1M Trim High Register (CPMUIRCTRIMH)
Module Base + 0x0019
7
6
5
4
3
2
1
0
F
F
F
R
IRCTRIM[7:0]
W
Reset
F
F
F
F
F
After de-assert of System Reset a factory programmed trim value is automatically loaded from the Flash memory to
provide trimmed Internal Reference Frequency fIRC1M_TRIM.
Figure 7-28. S12CPMU_UHV_V5 IRC1M Trim Low Register (CPMUIRCTRIML)
Read: Anytime
Write: Anytime if PROT=0 (CPMUPROT register). Else write has no effect
NOTE
Writes to these registers while PLLSEL=1 clears the LOCK and UPOSC
status bits.
Table 7-26. CPMUIRCTRIMH/L Field Descriptions
Field
Description
15-11
IRC1M temperature coefficient Trim Bits
TCTRIM[4:0] Trim bits for the Temperature Coefficient (TC) of the IRC1M frequency.
Table 7-27 shows the influence of the bits TCTRIM[4:0] on the relationship between frequency and temperature.
Figure 7-30 shows an approximate TC variation, relative to the nominal TC of the IRC1M (i.e. for
TCTRIM[4:0]=0x00000 or 0x10000).
9-0
IRC1M Frequency Trim Bits — Trim bits for Internal Reference Clock
IRCTRIM[9:0] After System Reset the factory programmed trim value is automatically loaded into these registers, resulting in a
Internal Reference Frequency fIRC1M_TRIM.See device electrical characteristics for value of fIRC1M_TRIM.
The frequency trimming consists of two different trimming methods:
A rough trimming controlled by bits IRCTRIM[9:6] can be done with frequency leaps of about 6% in average.
A fine trimming controlled by bits IRCTRIM[5:0] can be done with frequency leaps of about 0.3% (this trimming
determines the precision of the frequency setting of 0.15%, i.e. 0.3% is the distance between two trimming
values).
Figure 7-29 shows the relationship between the trim bits and the resulting IRC1M frequency.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
270
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
IRC1M frequency (IRCCLK)
IRCTRIM[9:6]
{
1.5MHz
IRCTRIM[5:0]
......
1MHz
600KHz
IRCTRIM[9:0]
$000
$3FF
Figure 7-29. IRC1M Frequency Trimming Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
271
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
frequency
11
0] =
11
0x1
0x11111
...
0x10101
0x10100
0x10011
0x10010
0x10001
[4:
IM
TR
TC
TC increases
TCTRIM[4:0] = 0x10000 or 0x00000 (nominal TC)
TCT
RIM
- 40C
[4:0
]=0
x01
111
0x00001
0x00010
0x00011
0x00100
0x00101
...
0x01111
TC decreases
150C
temperature
Figure 7-30. Influence of TCTRIM[4:0] on the Temperature Coefficient
NOTE
The frequency is not necessarily linear with the temperature (in most cases
it will not be). The above diagram is meant only to give the direction
(positive or negative) of the variation of the TC, relative to the nominal TC.
Setting TCTRIM[4:0] at 0x00000 or 0x10000 does not mean that the
temperature coefficient will be zero. These two combinations basically
switch off the TC compensation module, which results in the nominal TC of
the IRC1M.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
272
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-27. TC trimming of the frequency of the IRC1M at ambient temperature
TCTRIM[4:0]
IRC1M Indicative
relative TC variation
IRC1M indicative frequency drift for relative
TC variation
00000
0 (nominal TC of the IRC)
0%
00001
-0.27%
-0.5%
00010
-0.54%
-0.9%
00011
-0.81%
-1.3%
00100
-1.08%
-1.7%
00101
-1.35%
-2.0%
00110
-1.63%
-2.2%
00111
-1.9%
-2.5%
01000
-2.20%
-3.0%
01001
-2.47%
-3.4%
01010
-2.77%
-3.9%
01011
-3.04
-4.3%
01100
-3.33%
-4.7%
01101
-3.6%
-5.1%
01110
-3.91%
-5.6%
01111
-4.18%
-5.9%
10000
0 (nominal TC of the IRC)
0%
10001
+0.27%
+0.5%
10010
+0.54%
+0.9%
10011
+0.81%
+1.3%
10100
+1.07%
+1.7%
10101
+1.34%
+2.0%
10110
+1.59%
+2.2%
10111
+1.86%
+2.5%
11000
+2.11%
+3.0%
11001
+2.38%
+3.4%
11010
+2.62%
+3.9%
11011
+2.89%
+4.3%
11100
+3.12%
+4.7%
11101
+3.39%
+5.1%
11110
+3.62%
+5.6%
11111
+3.89%
+5.9%
NOTE
Since the IRC1M frequency is not a linear function of the temperature, but
more like a parabola, the above relative variation is only an indication and
should be considered with care.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
273
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Be aware that the output frequency varies with the TC trimming. A
frequency trimming correction is therefore necessary. The values provided
in Table 7-27 are typical values at ambient temperature which can vary from
device to device.
7.3.2.22
S12CPMU_UHV_V5 Oscillator Register (CPMUOSC)
This registers configures the external oscillator (XOSCLCP).
Module Base + 0x001A
7
6
R
5
0
OSCE
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
Reserved
W
Reset
0
0
0
= Unimplemented or Reserved
Figure 7-31. S12CPMU_UHV_V5 Oscillator Register (CPMUOSC)
Read: Anytime
Write: Anytime if PROT=0 (CPMUPROT register) and PLLSEL=1 (CPMUCLKS register). Else write has
no effect.
NOTE.
Write to this register clears the LOCK and UPOSC status bits.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
274
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-28. CPMUOSC Field Descriptions
Field
Description
7
OSCE
Oscillator Enable Bit — This bit enables the external oscillator (XOSCLCP). The UPOSC status bit in the
CPMIUFLG register indicates when the oscillation is stable and when OSCCLK can be selected as source of the
Bus Clock or source of the COP or RTI.If the oscillator clock monitor reset is enabled (OMRE = 1 in
CPMUOSC2 register), then a loss of oscillation will lead to an oscillator clock monitor reset.
0 External oscillator is disabled.
REFCLK for PLL is IRCCLK.
1 External oscillator is enabled.
Oscillator clock monitor is enabled.
External oscillator is qualified by PLLCLK.
REFCLK for PLL is the external oscillator clock divided by REFDIV.
If OSCE bit has been set (write “1”) the EXTAL and XTAL pins are exclusively reserved for the oscillator
and they can not be used anymore as general purpose I/O until the next system reset.
Note: When starting up the external oscillator (either by programming OSCE bit to 1 or on exit from Full Stop
Mode with OSCE bit already 1) the software must wait for a minimum time equivalent to the startup-time
of the external oscillator tUPOSC before entering Pseudo Stop Mode.
5
Reserved
Do not alter this bit from its reset value. It is for Manufacturer use only and can change the Oscillator behavior.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
275
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.23
S12CPMU_UHV_V5 Protection Register (CPMUPROT)
This register protects the clock configuration registers from accidental overwrite:
CPMUSYNR, CPMUREFDIV, CPMUCLKS, CPMUPLL, CPMUIRCTRIMH/L, CPMUOSC and
CPMUOSC2
Module Base + 0x001B
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
PROT
W
Reset
0
0
0
0
0
0
0
0
Figure 7-32. S12CPMU_UHV_V5 Protection Register (CPMUPROT)
Read: Anytime
Write: Anytime
Field
Description
PROT
Clock Configuration Registers Protection Bit — This bit protects the clock configuration registers from
accidental overwrite (see list of protected registers above): Writing 0x26 to the CPMUPROT register clears the
PROT bit, other write accesses set the PROT bit.
0 Protection of clock configuration registers is disabled.
1 Protection of clock configuration registers is enabled. (see list of protected registers above).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
276
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.24
Reserved Register CPMUTEST2
NOTE
This reserved register is designed for factory test purposes only, and is not
intended for general user access. Writing to this register when in Special
Mode can alter the S12CPMU_UHV_V5’s functionality.
Module Base + 0x001C
7
R
W
Reset
6
0
0
0
0
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 7-33. Reserved Register CPMUTEST2
Read: Anytime
Write: Only in Special Mode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
277
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.3.2.25
Voltage Regulator Control Register (CPMUVREGCTL)
The CPMUVREGCTL allows to enable or disable certain parts of the voltage regulator.This register must
be configured after system startup.
Module Base + 0x001D
R
7
6
5
4
3
2
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
1
0
EXTXON
INTXON
1
1
= Unimplemented or Reserved
Figure 7-34. Voltage Regulator Control Register (CPMUVREGCTL)
Read: Anytime
Write: Once in normal modes, anytime in special modes
Table 7-29. Effects of writing the EXTXON and INTXON bits
value of
EXTXON
to be written
value of
INTXON
to be written
Write Access
0
0
blocked, no effect
0
1
legal access
1
0
legal access
1
1
blocked, no effect
Table 7-30. CPMUVREGCTL Field Descriptions
Field
Description
1
EXTXON
External voltage regulator Enable Bit for VDDX domain — Should be set to 1 if external BJT is present on
the PCB, cleared otherwise.
0 VDDX control loop does not use external BJT
1 VDDX control loop uses external BJT
0
INTXON
Internal voltage regulator Enable Bit for VDDX domain— Should be set to 1 if no external BJT is present on
the PCB, cleared otherwise.
0 VDDX control loop does not use internal power transistor
1 VDDX control loop uses internal power transistor
7.3.2.26
S12CPMU_UHV_V5 Oscillator Register 2 (CPMUOSC2)
This registers configures the external oscillator (XOSCLCP).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
278
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Module Base + 0x001E
R
7
6
5
4
3
2
0
0
0
0
0
0
1
0
OMRE
OSCMOD
0
0
W
Reset
0
0
0
0
0
0
Figure 7-35. S12CPMU_UHV_V5 Oscillator Register 2 (CPMUOSC2)
Read: Anytime
Write: Anytime if PROT=0 (CPMUPROT register) and PLLSEL=1 (CPMUCLKS register). Else write has
no effect.
Table 7-31. CPMUOSC2 Field Descriptions
Field
Description
1
OMRE
This bit enables the oscillator clock monitor reset. If OSCE bit in CPMUOSC register is 1, then the OMRE bit can
not be changed (writes will have no effect).
0 Oscillator clock monitor reset is disabled
1 Oscillator clock monitor reset is enabled
0
OSCMOD
This bit selects the mode of the external oscillator (XOSCLCP)
If OSCE bit in CPMUOSC register is 1, then the OSCMOD bit can not be changed (writes will have no effect).
0 External oscillator configured for loop controlled mode (reduced amplitude on EXTAL and XTAL))
1 External oscillator configured for full swing mode (full swing amplitude on EXTAL and XTAL)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
279
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.4
7.4.1
Functional Description
Phase Locked Loop with Internal Filter (PLL)
The PLL is used to generate a high speed PLLCLK based on a low frequency REFCLK.
The REFCLK is by default the IRCCLK which is trimmed to fIRC1M_TRIM=1MHz.
If using the oscillator (OSCE=1) REFCLK will be based on OSCCLK. For increased flexibility, OSCCLK
can be divided in a range of 1 to 16 to generate the reference frequency REFCLK using the REFDIV[3:0]
bits. Based on the SYNDIV[5:0] bits the PLL generates the VCOCLK by multiplying the reference clock
by a 2, 4, 6,... 126, 128. Based on the POSTDIV[4:0] bits the VCOCLK can be divided in a range of 1,2,
3, 4, 5, 6,... to 32 to generate the PLLCLK.
If oscillator is enabled (OSCE=1)
f OSC
f REF = -----------------------------------( REFDIV + 1 )
If oscillator is disabled (OSCE=0)
f REF = f IRC1M
f VCO = 2 × f REF × ( SYNDIV + 1 )
If PLL is locked (LOCK=1)
f VCO
f PLL = ----------------------------------------( POSTDIV + 1 )
If PLL is not locked (LOCK=0)
f VCO
f PLL = --------------4
If PLL is selected (PLLSEL=1)
f PLL
f bus = ------------2
.
NOTE
Although it is possible to set the dividers to command a very high clock
frequency, do not exceed the specified bus frequency limit for the MCU.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
280
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Several examples of PLL divider settings are shown in Table 7-32. The following rules help to achieve
optimum stability and shortest lock time:
• Use lowest possible fVCO / fREF ratio (SYNDIV value).
• Use highest possible REFCLK frequency fREF.
Table 7-32. Examples of PLL Divider Settings
fosc
REFDIV[3:0]
fREF
REFFRQ[1:0] SYNDIV[5:0]
fVCO
VCOFRQ[1:0] POSTDIV[4:0]
fPLL
fbus
off
$00
1MHz
00
$18
50MHz
01
$03
12.5MHz
6.25MHz
off
$00
1MHz
00
$18
50MHz
01
$00
50MHz
25MHz
4MHz
$00
4MHz
01
$05
48MHz
00
$00
48MHz
24MHz
The phase detector inside the PLL compares the feedback clock (FBCLK = VCOCLK/(SYNDIV+1)) with
the reference clock (REFCLK = (IRC1M or OSCCLK)/(REFDIV+1)). Correction pulses are generated
based on the phase difference between the two signals. The loop filter alters the DC voltage on the internal
filter capacitor, based on the width and direction of the correction pulse which leads to a higher or lower
VCO frequency.
The user must select the range of the REFCLK frequency (REFFRQ[1:0] bits) and the range of the
VCOCLK frequency (VCOFRQ[1:0] bits) to ensure that the correct PLL loop bandwidth is set.
The lock detector compares the frequencies of the FBCLK and the REFCLK. Therefore the speed of the
lock detector is directly proportional to the reference clock frequency. The circuit determines the lock
condition based on this comparison. So e.g. a failure in the reference clock will cause the PLL not to lock.
If PLL LOCK interrupt requests are enabled, the software can wait for an interrupt request and for instance
check the LOCK bit. If interrupt requests are disabled, software can poll the LOCK bit continuously
(during PLL start-up) or at periodic intervals. In either case, only when the LOCK bit is set, the VCOCLK
will have stabilized to the programmed frequency.
• The LOCK bit is a read-only indicator of the locked state of the PLL.
• The LOCK bit is set when the VCO frequency is within the tolerance, ∆Lock, and is cleared when
the VCO frequency is out of the tolerance, ∆unl.
• Interrupt requests can occur if enabled (LOCKIE = 1) when the lock condition changes, toggling
the LOCK bit.
In case of loss of reference clock (e.g. IRCCLK) the PLL will not lock or if already locked, then it will
unlock. The frequency of the VCOCLK will be very low and will depend on the value of the
VCOFRQ[1:0] bits.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
281
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.4.2
Startup from Reset
An example for startup of the clock system from Reset is given in Figure 7-36.
Figure 7-36. Startup of clock system after Reset
System
Reset
768 cycles
PLLCLK
fPLL increasing
fVCORST
fPLL=25 MHz
fPLL=12.5MHz
)(
tlock
LOCK
SYNDIV
$18 (default target fVCO=50MHz)
POSTDIV
$03 (default target fPLL=fVCO/4 = 12.5MHz)
CPU
reset state
7.4.3
$01
vector fetch, program execution
example change
of POSTDIV
Stop Mode using PLLCLK as source of the Bus Clock
An example of what happens going into Stop Mode and exiting Stop Mode after an interrupt is shown in
Figure 7-37. Disable PLL Lock interrupt (LOCKIE=0) before going into Stop Mode.
Figure 7-37. Stop Mode using PLLCLK as source of the Bus Clock
wake up
CPU
execution
interrupt
STOP instruction
continue execution
tSTP_REC
PLLCLK
LOCK
tlock
Depending on the COP configuration there might be an additional significant latency time until COP is
active again after exit from Stop Mode due to clock domain crossing synchronization. This latency time
occurs if COP clock source is ACLK and the CSAD bit is set (please refer to CSAD bit description for
details).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
282
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.4.4
Full Stop Mode using Oscillator Clock as source of the Bus Clock
An example of what happens going into Full Stop Mode and exiting Full Stop Mode after an interrupt is
shown in Figure 7-38.
Disable PLL Lock interrupt (LOCKIE=0) and oscillator status change interrupt (OSCIE=0) before going
into Full Stop Mode.
Figure 7-38. Full Stop Mode using Oscillator Clock as source of the Bus Clock
wake up
CPU
execution
Core
Clock
PLLCLK
interrupt
STOP instruction
continue execution
tSTP_REC
tlock
OSCCLK
UPOSC
select OSCCLK as Core/Bus Clock by writing PLLSEL to “0”
PLLSEL
automatically set when going into Full Stop Mode
Depending on the COP configuration there might be an additional significant latency time until COP is
active again after exit from Stop Mode due to clock domain crossing synchronization. This latency time
occurs if COP clock source is ACLK and the CSAD bit is set (please refer to CSAD bit description for
details).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
283
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.4.5
7.4.5.1
External Oscillator
Enabling the External Oscillator
An example of how to use the oscillator as source of the Bus Clock is shown in Figure 7-39.
Figure 7-39. Enabling the external oscillator
enable external oscillator by writing OSCE bit to one.
OSCE
crystal/resonator starts oscillating
EXTAL
UPOSC flag is set upon successful start of oscillation
UPOSC
OSCCLK
select OSCCLK as Core/Bus Clock by writing PLLSEL to zero
PLLSEL
Core
Clock
based on PLL Clock
based on OSCCLK
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
284
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.4.6
7.4.6.1
System Clock Configurations
PLL Engaged Internal Mode (PEI)
This mode is the default mode after System Reset or Power-On Reset.
The Bus Clock is based on the PLLCLK, the reference clock for the PLL is internally generated (IRC1M).
The PLL is configured to 50 MHz VCOCLK with POSTDIV set to 0x03. If locked (LOCK=1) this results
in a PLLCLK of 12.5 MHz and a Bus Clock of 6.25 MHz. The PLL can be re-configured to other bus
frequencies.
The clock sources for COP and RTI can be based on the internal reference clock generator (IRC1M) or the
RC-Oscillator (ACLK).
7.4.6.2
PLL Engaged External Mode (PEE)
In this mode, the Bus Clock is based on the PLLCLK as well (like PEI). The reference clock for the PLL
is based on the external oscillator.
The clock sources for COP and RTI can be based on the internal reference clock generator or on the
external oscillator clock or the RC-Oscillator (ACLK).
This mode can be entered from default mode PEI by performing the following steps:
1. Configure the PLL for desired bus frequency.
2. Enable the external Oscillator (OSCE bit).
3. Wait for oscillator to start-up and the PLL being locked (LOCK = 1) and (UPOSC =1).
4. Clear all flags in the CPMUIFLG register to be able to detect any future status bit change.
5. Optionally status interrupts can be enabled (CPMUINT register).
Loosing PLL lock status (LOCK=0) means loosing the oscillator status information as well (UPOSC=0).
The impact of loosing the oscillator status (UPOSC=0) in PEE mode is as follows:
• The PLLCLK is derived from the VCO clock (with its actual frequency) divided by four until the
PLL locks again.
Application software needs to be prepared to deal with the impact of loosing the oscillator status at any
time.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
285
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.4.6.3
PLL Bypassed External Mode (PBE)
In this mode, the Bus Clock is based on the external oscillator clock. The reference clock for the PLL is
based on the external oscillator.
The clock sources for COP and RTI can be based on the internal reference clock generator or on the
external oscillator clock or the RC-Oscillator (ACLK).
This mode can be entered from default mode PEI by performing the following steps:
1. Make sure the PLL configuration is valid.
2. Enable the external Oscillator (OSCE bit)
3. Wait for the oscillator to start-up and the PLL being locked (LOCK = 1) and (UPOSC =1)
4. Clear all flags in the CPMUIFLG register to be able to detect any status bit change.
5. Optionally status interrupts can be enabled (CPMUINT register).
6. Select the Oscillator clock as source of the Bus clock (PLLSEL=0)
Loosing PLL lock status (LOCK=0) means loosing the oscillator status information as well (UPOSC=0).
The impact of loosing the oscillator status (UPOSC=0) in PBE mode is as follows:
• PLLSEL is set automatically and the Bus clock is switched back to the PLL clock.
• The PLLCLK is derived from the VCO clock (with its actual frequency) divided by four until the
PLL locks again.
Application software needs to be prepared to deal with the impact of loosing the oscillator status at any
time.
7.5
7.5.1
Resets
General
All reset sources are listed in Table 7-33. There is only one reset vector for all these reset sources. Refer
to MCU specification for reset vector address.
Table 7-33. Reset Summary
Reset Source
Local Enable
Power-On Reset (POR)
None
Low Voltage Reset (LVR)
None
External pin RESET
None
PLL Clock Monitor Reset
None
Oscillator Clock Monitor Reset
OSCE Bit in CPMUOSC register and
OMRE Bit in CPMUOSC2 register
COP Reset
CR[2:0] in CPMUCOP register
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
286
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.5.2
Description of Reset Operation
Upon detection of any reset of Table 7-33, an internal circuit drives the RESET pin low for 512 PLLCLK
cycles. After 512 PLLCLK cycles the RESET pin is released. The internal reset of the MCU remains
asserted while the reset generator completes the 768 PLLCLK cycles long reset sequence.In case the
RESET pin is externally driven low for more than these 768 PLLCLK cycles (External Reset), the internal
reset remains asserted longer.
NOTE
While System Reset is asserted the PLLCLK runs with the frequency
fVCORST.
Figure 7-40. RESET Timing
RESET
S12_CPMU drives
RESET pin low
fVCORST
fVCORST
)
)
PLLCLK
S12_CPMU releases
RESET pin
(
512 cycles
)
(
(
256 cycles
possibly
RESET
driven low
externally
7.5.3
Oscillator Clock Monitor Reset
If the external oscillator is enabled (OSCE=1)and the oscillator clock monitor reset is enabled (OMRE=1),
then in case of loss of oscillation or the oscillator frequency drops below the failure assert frequency fCMFA
(see device electrical characteristics for values), the S12CPMU_UHV_V5 generates an Oscillator Clock
Monitor Reset. In Full Stop Mode the external oscillator and the oscillator clock monitor are disabled.
7.5.4
PLL Clock Monitor Reset
In case of loss of PLL clock oscillation or the PLL clock frequency is below the failure assert frequency
fPMFA (see device electrical characteristics for values), the S12CPMU_UHV_V5 generates a PLL Clock
Monitor Reset. In Full Stop Mode the PLL and the PLL clock monitor are disabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
287
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.5.5
Computer Operating Properly Watchdog (COP) Reset
The COP (free running watchdog timer) enables the user to check that a program is running and
sequencing properly. When the COP is being used, software is responsible for keeping the COP from
timing out. If the COP times out it is an indication that the software is no longer being executed in the
intended sequence; thus COP reset is generated.
The clock source for the COP is either ACLK, IRCCLK or OSCCLK depending on the setting of the
COPOSCSEL0 and COPOSCSEL1 bit.
Depending on the COP configuration there might be a significant latency time until COP is active again
after exit from Stop Mode due to clock domain crossing synchronization. This latency time occurs if COP
clock source is ACLK and the CSAD bit is set (please refer to CSAD bit description for details)
Table 7-34 gives an overview of the COP condition (run, static) in Stop Mode depending on legal
configuration and status bit settings:
Table 7-34. COP condition (run, static) in Stop Mode
COPOSCSEL1 CSAD PSTP
PCE
COPOSCSEL0
OSCE
UPOSC
COP counter behavior in Stop Mode
(clock source)
1
0
x
x
x
x
x
Run (ACLK)
1
1
x
x
x
x
x
Static (ACLK)
0
x
1
1
1
1
1
Run (OSCCLK)
0
x
1
1
0
0
x
Static (IRCCLK)
0
x
1
1
0
1
x
Static (IRCCLK)
0
x
1
0
0
x
x
Static (IRCCLK)
0
x
1
0
1
1
1
Static (OSCCLK)
0
x
0
1
1
1
1
Static (OSCCLK)
0
x
0
1
0
1
x
Static (IRCCLK)
0
x
0
1
0
0
0
Static (IRCCLK)
0
x
0
0
1
1
1
Satic (OSCCLK)
0
x
0
0
0
1
1
Static (IRCCLK)
0
x
0
0
0
1
0
Static (IRCCLK)
0
x
0
0
0
0
0
Static (IRCCLK)
Three control bits in the CPMUCOP register allow selection of seven COP time-out periods.
When COP is enabled, the program must write $55 and $AA (in this order) to the CPMUARMCOP
register during the selected time-out period. Once this is done, the COP time-out period is restarted. If the
program fails to do this and the COP times out, a COP reset is generated. Also, if any value other than $55
or $AA is written, a COP reset is generated.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
288
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Windowed COP operation is enabled by setting WCOP in the CPMUCOP register. In this mode, writes to
the CPMUARMCOP register to clear the COP timer must occur in the last 25% of the selected time-out
period. A premature write will immediately reset the part.
In MCU Normal Mode the COP time-out period (CR[2:0]) and COP window (WCOP) setting can be
automatically pre-loaded at reset release from NVM memory (if values are defined in the NVM by the
application). By default the COP is off and no window COP feature is enabled after reset release via NVM
memory. The COP control register CPMUCOP can be written once in an application in MCU Normal
Mode to update the COP time-out period (CR[2:0]) and COP window (WCOP) setting loaded from NVM
memory at reset release. Any value for the new COP time-out period and COP window setting is allowed
except COP off value if the COP was enabled during pre-load via NVM memory.
The COP clock source select bits can not be pre-loaded via NVM memory at reset release. The IRC clock
is the default COP clock source out of reset.
The COP clock source select bits (COPOSCSEL0/1) and ACLK clock control bit in Stop Mode (CSAD)
can be modified until the CPMUCOP register write once has taken place. Therefore these control bits
should be modified before the final COP time-out period and window COP setting is written.
The CPMUCOP register access to modify the COP time-out period and window COP setting in MCU
Normal Mode after reset release must be done with the WRTMASK bit cleared otherwise the update is
ignored and this access does not count as the write once.
7.5.6
Power-On Reset (POR)
The on-chip POR circuitry detects when the internal supply VDD drops below an appropriate voltage
level. The POR is deasserted, if the internal supply VDD exceeds an appropriate voltage level (voltage
levels not specified, because the internal supply can not be monitored externally).The POR circuitry is
always active. It acts as LVR in Stop Mode.
7.5.7
Low-Voltage Reset (LVR)
The on-chip LVR circuitry detects when one of the supply voltages VDD, VDDX and VDDF drops below
an appropriate voltage level. If LVR is deasserted the MCU is fully operational at the specified maximum
speed. The LVR assert and deassert levels for the supply voltage VDDX are VLVRXA and VLVRXD and are
specified in the device Reference Manual.The LVR circuitry is active in Run- and Wait Mode.
7.6
Interrupts
The interrupt vectors requested by the S12CPMU_UHV_V5 are listed in Table 7-35. Refer to MCU
specification for related vector addresses and priorities.
Table 7-35. S12CPMU_UHV_V5 Interrupt Vectors
Interrupt Source
CCR
Mask
Local Enable
RTI time-out interrupt
I bit
CPMUINT (RTIE)
PLL lock interrupt
I bit
CPMUINT (LOCKIE)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
289
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
Table 7-35. S12CPMU_UHV_V5 Interrupt Vectors
CCR
Mask
Local Enable
Oscillator status
interrupt
I bit
CPMUINT (OSCIE)
Low voltage interrupt
I bit
CPMULVCTL (LVIE)
High temperature
interrupt
I bit
CPMUHTCTL (HTIE)
Autonomous
Periodical Interrupt
I bit
CPMUAPICTL (APIE)
Interrupt Source
7.6.1
7.6.1.1
Description of Interrupt Operation
Real Time Interrupt (RTI)
The clock source for the RTI is either IRCCLK or OSCCLK depending on the setting of the RTIOSCSEL
bit. In Stop Mode with PSTP=1 (Pseudo Stop Mode), RTIOSCSEL=1 and PRE=1 the RTI continues to
run, else the RTI counter halts in Stop Mode.
The RTI can be used to generate hardware interrupts at a fixed periodic rate. If enabled (by setting
RTIE=1), this interrupt will occur at the rate selected by the CPMURTI register. At the end of the RTI timeout period the RTIF flag is set to one and a new RTI time-out period starts immediately.
A write to the CPMURTI register restarts the RTI time-out period.
7.6.1.2
PLL Lock Interrupt
The S12CPMU_UHV_V5 generates a PLL Lock interrupt when the lock condition (LOCK status bit) of
the PLL changes, either from a locked state to an unlocked state or vice versa. Lock interrupts are locally
disabled by setting the LOCKIE bit to zero. The PLL Lock interrupt flag (LOCKIF) is set to1 when the
lock condition has changed, and is cleared to 0 by writing a 1 to the LOCKIF bit.
7.6.1.3
Oscillator Status Interrupt
When the OSCE bit is 0, then UPOSC stays 0. When OSCE=1 the UPOSC bit is set after the LOCK bit is
set.
Upon detection of a status change (UPOSC) the OSCIF flag is set. Going into Full Stop Mode or disabling
the oscillator can also cause a status change of UPOSC.
Any change in PLL configuration or any other event which causes the PLL lock status to be cleared leads
to a loss of the oscillator status information as well (UPOSC=0).
Oscillator status change interrupts are locally enabled with the OSCIE bit.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
290
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
NOTE
Loosing the oscillator status (UPOSC=0) affects the clock configuration of
the system1. This needs to be dealt with in application software.
7.6.1.4
Low-Voltage Interrupt (LVI)
In FPM the input voltage VDDA is monitored. Whenever VDDA drops below level VLVIA, the status bit
LVDS is set to 1. When VDDA rises above level VLVID the status bit LVDS is cleared to 0. An interrupt,
indicated by flag LVIF = 1, is triggered by any change of the status bit LVDS if interrupt enable bit LVIE
= 1.
7.6.1.5
HTI - High Temperature Interrupt
In FPM the junction temperature TJ is monitored. Whenever TJ exceeds level THTIA the status bit HTDS
is set to 1. Vice versa, HTDS is reset to 0 when TJ get below level THTID. An interrupt, indicated by flag
HTIF = 1, is triggered by any change of the status bit HTDS, if interrupt enable bit HTIE = 1.
7.6.1.6
Autonomous Periodical Interrupt (API)
The API sub-block can generate periodical interrupts independent of the clock source of the MCU. To
enable the timer, the bit APIFE needs to be set.
The API timer is either clocked by the Autonomous Clock (ACLK - trimmable internal RC oscillator) or
the Bus Clock. Timer operation will freeze when MCU clock source is selected and Bus Clock is turned
off. The clock source can be selected with bit APICLK. APICLK can only be written when APIFE is not
set.
The APIR[15:0] bits determine the interrupt period. APIR[15:0] can only be written when APIFE is
cleared. As soon as APIFE is set, the timer starts running for the period selected by APIR[15:0] bits. When
the configured time has elapsed, the flag APIF is set. An interrupt, indicated by flag APIF = 1, is triggered
if interrupt enable bit APIE = 1. The timer is re-started automatically again after it has set APIF.
The procedure to change APICLK or APIR[15:0] is first to clear APIFE, then write to APICLK or
APIR[15:0], and afterwards set APIFE.
The API Trimming bits ACLKTR[5:0] must be set so the minimum period equals 0.2 ms if stable
frequency is desired.
See Table 7-20 for the trimming effect of ACLKTR[5:0].
NOTE
The first period after enabling the counter by APIFE might be reduced by
API start up delay tsdel.
It is possible to generate with the API a waveform at the external pin API_EXTCLK by setting APIFE and
enabling the external access with setting APIEA.
1. For details please refer to “7.4.6 System Clock Configurations”
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
291
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
7.7
7.7.1
Initialization/Application Information
General Initialization Information
Usually applications run in MCU Normal Mode.
It is recommended to write the CPMUCOP register in any case from the application program initialization
routine after reset no matter if the COP is used in the application or not, even if a configuration is loaded
via the flash memory after reset. By doing a “controlled” write access in MCU Normal Mode (with the
right value for the application) the write once for the COP configuration bits (WCOP,CR[2:0]) takes place
which protects these bits from further accidental change. In case of a program sequencing issue (code
runaway) the COP configuration can not be accidentally modified anymore.
7.7.2
Application information for COP and API usage
In many applications the COP is used to check that the program is running and sequencing properly. Often
the COP is kept running during Stop Mode and periodic wake-up events are needed to service the COP on
time and maybe to check the system status.
For such an application it is recommended to use the ACLK as clock source for both COP and API. This
guarantees lowest possible IDD current during Stop Mode. Additionally it eases software implementation
using the same clock source for both, COP and API.
The Interrupt Service Routine (ISR) of the Autonomous Periodic Interrupt API should contain the write
instruction to the CPMUARMCOP register. The value (byte) written is derived from the “main routine”
(alternating sequence of $55 and $AA) of the application software.
Using this method, then in the case of a runtime or program sequencing issue the application “main
routine” is not executed properly anymore and the alternating values are not provided properly. Hence the
COP is written at the correct time (due to independent API interrupt request) but the wrong value is written
(alternating sequence of $55 and $AA is no longer maintained) which causes a COP reset.
If the COP is stopped during any Stop Mode it is recommended to service the COP shortly before Stop
Mode is entered.
7.7.3
Application Information for PLL and Oscillator Startup
The following C-code example shows a recommended way of setting up the system clock system using
the PLL and Oscillator:
/* Procedure proposed by to setup PLL and Oscillator */
/* example for OSC = 4 MHz and Bus Clock = 25MHz, That is VCOCLK = 50MHz */
/* Initialize */
/* PLL Clock = 50 MHz, divide by one */
CPMUPOSTDIV = 0x00;
/* Generally: Whenever changing PLL reference clock (REFCLK) frequency to a higher value */
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
292
Freescale Semiconductor
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
/* it is recommended to write CPMUSYNR = 0x00 in order to stay within specified */
/* maximum frequency of the MCU */
CPMUSYNR = 0x00;
/* configure PLL reference clock (REFCLK) for usage with Oscillator */
/* OSC=4MHz divide by 4 (3+1) = 1MHz, REFCLK range 1MHz to 2 MHz (REFFRQ[1:0] = 00) */
CPMUREFDV = 0x03;
/* enable external Oscillator, switch PLL reference clock (REFCLK) to OSC */
CPMUOSC = 0x80;
/* multiply REFCLK = 1MHz by 2*(24+1)*1MHz = 50MHz */
/* VCO range 48 to 80 MHz (VCOFRQ[1:0] = 01) */
CPMUSYNR = 0x58;
/* clear all flags, especially LOCKIF and OSCIF */
CPMUIFLG = 0xFF;
/* put your code to loop and wait for the LOCKIF and OSCIF or */
/* poll CPMUIFLG register until both UPOSC and LOCK status are “1” */
/* that is CPMIFLG == 0x1B */
/*...............continue to your main code execution here...............*/
/* in case later in your code you want to disable the Oscillator and use the */
/* 1MHz IRCCLK as PLL reference clock */
/* Generally: Whenever changing PLL reference clock (REFCLK) frequency to a higher value */
/* it is recommended to write CPMUSYNR = 0x00 in order to stay within specified */
/* maximum frequency of the MCU */
CPMUSYNR = 0x00;
/* disable OSC and switch PLL reference clock to IRC */
CPMUOSC = 0x00;
/* multiply REFCLK = 1MHz by 2*(24+1)*1MHz = 50MHz */
/* VCO range 48 to 80 MHz (VCOFRQ[1:0] = 01) */
CPMUSYNR = 0x58;
/* clear all flags, especially LOCKIF and OSCIF */
CPMUIFLG = 0xFF;
/* put your code to loop and wait for the LOCKIF or */
/* poll CPMUIFLG register until both LOCK status is “1” */
/* that is CPMIFLG == 0x18 */
/*...............continue to your main code execution here...............*/
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
293
Chapter 7 S12 Clock, Reset and Power Management Unit (S12CPMU_UHV_V5)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
294
Freescale Semiconductor
Chapter 8
Timer Module (TIM16B8CV3) Block Description
Table 8-1.
V03.00
Jan. 28, 2009
V03.01
Aug. 26, 2009
Initial version
8.1.2/8-296
8.3.2.15/8-312
8.3.2.2/8-302,
8.3.2.3/8-302,
8.3.2.4/8-303,
8.4.3/8-318
V03.02
Apri,12,2010
V03.03
Jan,14,2013
8.3.2.8/8-306
8.3.2.11/8-309
8.4.3/8-318
- Correct typo: TSCR ->TSCR1;
- Correct typo: ECTxxx->TIMxxx
- Correct reference: Figure 8-25 -> Figure 8-30
- Add description, “a counter overflow when TTOV[7] is set”, to be the
condition of channel 7 override event.
- Phrase the description of OC7M to make it more explicit
-Add Table 8-10
-update TCRE bit description
-add Figure 8-31
-single source generate different channel guide
8.1
Introduction
The basic scalable timer consists of a 16-bit, software-programmable counter driven by a flexible
programmable prescaler.
This timer can be used for many purposes, including input waveform measurements while simultaneously
generating an output waveform. Pulse widths can vary from microseconds to many seconds.
This timer could contain up to 8 input capture/output compare channels with one pulse accumulator
available only on channel 7. The input capture function is used to detect a selected transition edge and
record the time. The output compare function is used for generating output signals or for timer software
delays. The 16-bit pulse accumulator is used to operate as a simple event counter or a gated time
accumulator. The pulse accumulator shares timer channel 7 when the channel is available and when in
event mode.
A full access for the counter registers or the input capture/output compare registers should take place in
one clock cycle. Accessing high byte and low byte separately for all of these registers may not yield the
same result as accessing them in one word.
8.1.1
Features
The TIM16B8CV3 includes these distinctive features:
• Up to 8 channels available. (refer to device specification for exact number)
• All channels have same input capture/output compare functionality.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
295
Chapter 8 Timer Module (TIM16B8CV3) Block Description
•
•
•
Clock prescaling.
16-bit counter.
16-bit pulse accumulator on channel 7 .
8.1.2
Modes of Operation
Stop:
Timer is off because clocks are stopped.
Freeze:
Timer counter keeps on running, unless TSFRZ in TSCR1 is set to 1.
Wait:
Counters keeps on running, unless TSWAI in TSCR1 is set to 1.
Normal:
Timer counter keep on running, unless TEN in TSCR1 is cleared to 0.
8.1.3
Block Diagrams
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
296
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Bus clock
Prescaler
16-bit Counter
Channel 0
Input capture
Output compare
Channel 1
Input capture
Output compare
Channel 2
Input capture
Output compare
Timer overflow
interrupt
Timer channel 0
interrupt
Channel 3
Input capture
Output compare
Registers
Channel 4
Input capture
Output compare
Channel 5
Input capture
Output compare
Timer channel 7
interrupt
PA overflow
interrupt
PA input
interrupt
Channel 6
Input capture
Output compare
16-bit
Pulse accumulator
Channel 7
Input capture
Output compare
IOC0
IOC1
IOC2
IOC3
IOC4
IOC5
IOC6
IOC7
Maximum possible channels, scalable from 0 to 7.
Pulse Accumulator is available only if channel 7 exists.
Figure 8-1. TIM16B8CV3 Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
297
Chapter 8 Timer Module (TIM16B8CV3) Block Description
TIMCLK (Timer clock)
CLK1
CLK0
Intermodule Bus
Clock select
(PAMOD)
Edge detector
IOC7
PACLK
PACLK / 256
PACLK / 65536
Prescaled clock
(PCLK)
4:1 MUX
Interrupt
PACNT
MUX
Divide by 64
M clock
Figure 8-2. 16-Bit Pulse Accumulator Block Diagram
16-bit Main Timer
IOCn
Edge detector
Set CnF Interrupt
TCn Input Capture Reg.
Figure 8-3. Interrupt Flag Setting
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
298
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
PULSE
ACCUMULATOR
PAD
CHANNEL 7 OUTPUT COMPARE
OCPD
TEN
TIOS7
Figure 8-4. Channel 7 Output Compare/Pulse Accumulator Logic
8.2
External Signal Description
The TIM16B8CV3 module has a selected number of external pins. Refer to device specification for exact
number.
8.2.1
IOC7 — Input Capture and Output Compare Channel 7
This pin serves as input capture or output compare for channel 7 . This can also be configured as pulse
accumulator input.
8.2.2
IOC6 - IOC0 — Input Capture and Output Compare Channel 6-0
Those pins serve as input capture or output compare for TIM16B8CV3 channel .
NOTE
For the description of interrupts see Section 8.6, “Interrupts”.
8.3
Memory Map and Register Definition
This section provides a detailed description of all memory and registers.
8.3.1
Module Memory Map
The memory map for the TIM16B8CV3 module is given below in Figure 8-5. The address listed for each
register is the address offset. The total address for each register is the sum of the base address for the
TIM16B8CV3 module and the address offset for each register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
299
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.3.2
Register Descriptions
This section consists of register descriptions in address order. Each description includes a standard register
diagram with an associated figure number. Details of register bit and field function follow the register
diagrams, in bit order.
Only bits related to implemented channels are valid.
Register
Name
0x0000
TIOS
0x0001
CFORC
0x0002
OC7M
0x0003
OC7D
0x0004
TCNTH
0x0005
TCNTL
0x0006
TSCR1
0x0007
TTOV
0x0008
TCTL1
0x0009
TCTL2
0x000A
TCTL3
0x000B
TCTL4
0x000C
TIE
0x000D
TSCR2
0x000E
TFLG1
0x000F
TFLG2
0x0010–0x001F
TCxH–TCxL(1)
0x0020
PACTL
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
Bit 7
6
5
4
3
2
1
Bit 0
IOS7
IOS6
IOS5
IOS4
IOS3
IOS2
IOS1
IOS0
0
FOC7
0
FOC6
0
FOC5
0
FOC4
0
FOC3
0
FOC2
0
FOC1
0
FOC0
OC7M7
OC7M6
OC7M5
OC7M4
OC7M3
OC7M2
OC7M1
OC7M0
OC7D7
OC7D6
OC7D5
OC7D4
OC7D3
OC7D2
OC7D1
OC7D0
TCNT15
TCNT14
TCNT13
TCNT12
TCNT11
TCNT10
TCNT9
TCNT8
TCNT7
TCNT6
TCNT5
TCNT4
TCNT3
TCNT2
TCNT1
TCNT0
TEN
TSWAI
TSFRZ
TFFCA
PRNT
0
0
0
TOV7
TOV6
TOV5
TOV4
TOV3
TOV2
TOV1
TOV0
OM7
OL7
OM6
OL6
OM5
OL5
OM4
OL4
OM3
OL3
OM2
OL2
OM1
OL1
OM0
OL0
EDG7B
EDG7A
EDG6B
EDG6A
EDG5B
EDG5A
EDG4B
EDG4A
EDG3B
EDG3A
EDG2B
EDG2A
EDG1B
EDG1A
EDG0B
EDG0A
C7I
C6I
C5I
C4I
C3I
C2I
C1I
C0I
0
0
0
TCRE
PR2
PR1
PR0
C6F
C5F
C4F
C3F
C2F
C1F
C0F
0
0
0
0
0
0
0
Bit 15
Bit 14
Bit 13
Bit 12
Bit 11
Bit 10
Bit 9
Bit 8
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
PAEN
PAMOD
PEDGE
CLK1
CLK0
PAOVI
PAI
TOI
C7F
TOF
0
Figure 8-5. TIM16B8CV3 Register Summary (Sheet 1 of 2)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
300
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Register
Name
Bit 7
0x0021
PAFLG
0x0022
PACNTH
0x0023
PACNTL
0x0024–0x002B
Reserved
0x002C
OCPD
0x002D
Reserved
0x002E
PTPSR
R
0
W
R
PACNT15
W
R
PACNT7
W
R
W
R
OCPD7
W
R
R
W
R
W
0x002F
Reserved
PTPS7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
PAOVF
PAIF
PACNT14
PACNT13
PACNT12
PACNT11
PACNT10
PACNT9
PACNT8
PACNT6
PACNT5
PACNT4
PACNT3
PACNT2
PACNT1
PACNT0
OCPD6
OCPD5
OCPD4
OCPD3
OCPD2
OCPD1
OCPD0
PTPS6
PTPS5
PTPS4
PTPS3
PTPS2
PTPS1
PTPS0
Figure 8-5. TIM16B8CV3 Register Summary (Sheet 2 of 2)
1. The register is available only if corresponding channel exists.
8.3.2.1
Timer Input Capture/Output Compare Select (TIOS)
Module Base + 0x0000
7
6
5
4
3
2
1
0
IOS7
IOS6
IOS5
IOS4
IOS3
IOS2
IOS1
IOS0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-6. Timer Input Capture/Output Compare Select (TIOS)
Read: Anytime
Write: Anytime
Table 8-2. TIOS Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero.
Field
7:0
IOS[7:0]
Description
Input Capture or Output Compare Channel Configuration
0 The corresponding implemented channel acts as an input capture.
1 The corresponding implemented channel acts as an output compare.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
301
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.3.2.2
Timer Compare Force Register (CFORC)
Module Base + 0x0001
7
6
5
4
3
2
1
0
R
0
0
0
0
0
0
0
0
W
FOC7
FOC6
FOC5
FOC4
FOC3
FOC2
FOC1
FOC0
0
0
0
0
0
0
0
0
Reset
Figure 8-7. Timer Compare Force Register (CFORC)
Read: Anytime but will always return 0x0000 (1 state is transient)
Write: Anytime
Table 8-3. CFORC Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero.
Field
Description
7:0
FOC[7:0]
Note: Force Output Compare Action for Channel 7:0 — A write to this register with the corresponding data
bit(s) set causes the action which is programmed for output compare “x” to occur immediately. The action
taken is the same as if a successful comparison had just taken place with the TCx register except the
interrupt flag does not get set. A channel 7 event, which can be a counter overflow when TTOV[7] is set or
a successful output compare on channel 7, overrides any channel 6:0 compares. If forced output compare
on any channel occurs at the same time as the successful output compare then forced output compare
action will take precedence and interrupt flag won’t get set.
8.3.2.3
Output Compare 7 Mask Register (OC7M)
Module Base + 0x0002
7
6
5
4
3
2
1
0
OC7M7
OC7M6
OC7M5
OC7M4
OC7M3
OC7M2
OC7M1
OC7M0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-8. Output Compare 7 Mask Register (OC7M)
Read: Anytime
Write: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
302
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Table 8-4. OC7M Field Descriptions
Field
Description
7:0
OC7M[7:0]
Output Compare 7 Mask — A channel 7 event, which can be a counter overflow when TTOV[7] is set or a
successful output compare on channel 7, overrides any channel 6:0 compares. For each OC7M bit that is set,
the output compare action reflects the corresponding OC7D bit.
0 The corresponding OC7Dx bit in the output compare 7 data register will not be transferred to the timer port on
a channel 7 event, even if the corresponding pin is setup for output compare.
1 The corresponding OC7Dx bit in the output compare 7 data register will be transferred to the timer port on a
channel 7 event.
Note: The corresponding channel must also be setup for output compare (IOSx = 1 and OCPDx = 0) for data to
be transferred from the output compare 7 data register to the timer port.
8.3.2.4
1
Output Compare 7 Data Register (OC7D)
.
Module Base + 0x0003
7
6
5
4
3
2
1
0
OC7D7
OC7D6
OC7D5
OC7D4
OC7D3
OC7D2
OC7D1
OC7D0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-9. Output Compare 7 Data Register (OC7D)
Read: Anytime
Write: Anytime
Table 8-5. OC7D Field Descriptions
Field
Description
7:0
OC7D[7:0]
Output Compare 7 Data — A channel 7 event, which can be a counter overflow when TTOV[7] is set or a
successful output compare on channel 7, can cause bits in the output compare 7 data register to transfer to the
timer port data register depending on the output compare 7 mask register.
8.3.2.5
Timer Count Register (TCNT)
Module Base + 0x0004
15
14
13
12
11
10
9
9
TCNT15
TCNT14
TCNT13
TCNT12
TCNT11
TCNT10
TCNT9
TCNT8
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-10. Timer Count Register High (TCNTH)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
303
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Module Base + 0x0005
7
6
5
4
3
2
1
0
TCNT7
TCNT6
TCNT5
TCNT4
TCNT3
TCNT2
TCNT1
TCNT0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-11. Timer Count Register Low (TCNTL)
The 16-bit main timer is an up counter.
A full access for the counter register should take place in one clock cycle. A separate read/write for high
byte and low byte will give a different result than accessing them as a word.
Read: Anytime
Write: Has no meaning or effect in the normal mode; only writable in special modes .
The period of the first count after a write to the TCNT registers may be a different size because the write
is not synchronized with the prescaler clock.
8.3.2.6
Timer System Control Register 1 (TSCR1)
Module Base + 0x0006
7
6
5
4
3
TEN
TSWAI
TSFRZ
TFFCA
PRNT
0
0
0
0
0
R
2
1
0
0
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 8-12. Timer System Control Register 1 (TSCR1)
Read: Anytime
Write: Anytime
Table 8-6. TSCR1 Field Descriptions
Field
7
TEN
6
TSWAI
Description
Timer Enable
0 Disables the main timer, including the counter. Can be used for reducing power consumption.
1 Allows the timer to function normally.
If for any reason the timer is not active, there is no ÷64 clock for the pulse accumulator because the ÷64 is
generated by the timer prescaler.
Timer Module Stops While in Wait
0 Allows the timer module to continue running during wait.
1 Disables the timer module when the MCU is in the wait mode. Timer interrupts cannot be used to get the MCU
out of wait.
TSWAI also affects pulse accumulator.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
304
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Table 8-6. TSCR1 Field Descriptions (continued)
Field
Description
5
TSFRZ
Timer Stops While in Freeze Mode
0 Allows the timer counter to continue running while in freeze mode.
1 Disables the timer counter whenever the MCU is in freeze mode. This is useful for emulation.
TSFRZ does not stop the pulse accumulator.
4
TFFCA
Timer Fast Flag Clear All
0 Allows the timer flag clearing to function normally.
1 For TFLG1(0x000E), a read from an input capture or a write to the output compare channel (0x0010–0x001F)
causes the corresponding channel flag, CnF, to be cleared. For TFLG2 (0x000F), any access to the TCNT
register (0x0004, 0x0005) clears the TOF flag. Any access to the PACNT registers (0x0022, 0x0023) clears
the PAOVF and PAIF flags in the PAFLG register (0x0021) if channel 7 exists. This has the advantage of
eliminating software overhead in a separate clear sequence. Extra care is required to avoid accidental flag
clearing due to unintended accesses.
3
PRNT
Precision Timer
0 Enables legacy timer. PR0, PR1, and PR2 bits of the TSCR2 register are used for timer counter prescaler
selection.
1 Enables precision timer. All bits of the PTPSR register are used for Precision Timer Prescaler Selection, and
all bits.
This bit is writable only once out of reset.
8.3.2.7
Timer Toggle On Overflow Register 1 (TTOV)
Module Base + 0x0007
7
6
5
4
3
2
1
0
TOV7
TOV6
TOV5
TOV4
TOV3
TOV2
TOV1
TOV0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-13. Timer Toggle On Overflow Register 1 (TTOV)
Read: Anytime
Write: Anytime
Table 8-7. TTOV Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero.
Field
Description
7:0
TOV[7:0]
Toggle On Overflow Bits — TOVx toggles output compare pin on overflow. This feature only takes effect when
in output compare mode. When set, it takes precedence over forced output compare but not channel 7 override
events.
0 Toggle output compare pin on overflow feature disabled.
1 Toggle output compare pin on overflow feature enabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
305
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.3.2.8
Timer Control Register 1/Timer Control Register 2 (TCTL1/TCTL2)
Module Base + 0x0008
7
6
5
4
3
2
1
0
OM7
OL7
OM6
OL6
OM5
OL5
OM4
OL4
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-14. Timer Control Register 1 (TCTL1)
Module Base + 0x0009
7
6
5
4
3
2
1
0
OM3
OL3
OM2
OL2
OM1
OL1
OM0
OL0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-15. Timer Control Register 2 (TCTL2)
Read: Anytime
Write: Anytime
Table 8-8. TCTL1/TCTL2 Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero
Field
Description
7:0
OMx
Output Mode — These eight pairs of control bits are encoded to specify the output action to be taken as a result
of a successful OCx compare. When either OMx or OLx is 1, the pin associated with OCx becomes an output
tied to OCx.
Note: To enable output action by OMx bits on timer port, the corresponding bit in OC7M should be cleared. For
an output line to be driven by an OCx the OCPDx must be cleared.
7:0
OLx
Output Level — These eightpairs of control bits are encoded to specify the output action to be taken as a result
of a successful OCx compare. When either OMx or OLx is 1, the pin associated with OCx becomes an output
tied to OCx.
Note: To enable output action by OLx bits on timer port, the corresponding bit in OC7M should be cleared. For
an output line to be driven by an OCx the OCPDx must be cleared.
Table 8-9. Compare Result Output Action
OMx
OLx
Action
0
0
No output compare
action on the timer output signal
0
1
Toggle OCx output line
1
0
Clear OCx output line to zero
1
1
Set OCx output line to one
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
306
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Note: To enable output action using the OM7 and OL7 bits on the timer port,the corresponding bit OC7M7
in the OC7M register must also be cleared. The settings for these bits can be seen inTable 8-10.
Table 8-10. The OC7 and OCx event priority
OC7M7=0
OC7M7=1
OC7Mx=1
TC7=TCx
OC7Mx=0
TC7>TCx
TC7=TCx
OC7Mx=1
TC7>TCx
TC7=TCx
IOCx=OMx/OLx
IOC7=OM7/OL7
IOCx=OC7Dx IOCx=OC7Dx
IOC7=OM7/O +OMx/OLx
L7
IOC7=OM7/O
L7
OC7Mx=0
TC7>TCx
IOCx=OC7Dx IOCx=OC7Dx
IOC7=OC7D7 +OMx/OLx
IOC7=OC7D7
TC7=TCx
TC7>TCx
IOCx=OMx/OLx
IOC7=OC7D7
Note: in Table 8-10, the IOS7 and IOSx should be set to 1
IOSx is the register TIOS bit x,
OC7Mx is the register OC7M bit x,
TCx is timer Input Capture/Output Compare register,
IOCx is channel x,
OMx/OLx is the register TCTL1/TCTL2,
OC7Dx is the register OC7D bit x.
IOCx = OC7Dx+ OMx/OLx, means that both OC7 event and OCx event will change channel x value.
8.3.2.9
Timer Control Register 3/Timer Control Register 4 (TCTL3 and TCTL4)
Module Base + 0x000A
7
6
5
4
3
2
1
0
EDG7B
EDG7A
EDG6B
EDG6A
EDG5B
EDG5A
EDG4B
EDG4A
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-16. Timer Control Register 3 (TCTL3)
Module Base + 0x000B
7
6
5
4
3
2
1
0
EDG3B
EDG3A
EDG2B
EDG2A
EDG1B
EDG1A
EDG0B
EDG0A
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-17. Timer Control Register 4 (TCTL4)
Read: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
307
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Write: Anytime.
Table 8-11. TCTL3/TCTL4 Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero.
Field
7:0
EDGnB
EDGnA
Description
Input Capture Edge Control — These eight pairs of control bits configure the input capture edge detector
circuits.
Table 8-12. Edge Detector Circuit Configuration
8.3.2.10
EDGnB
EDGnA
Configuration
0
0
Capture disabled
0
1
Capture on rising edges only
1
0
Capture on falling edges only
1
1
Capture on any edge (rising or falling)
Timer Interrupt Enable Register (TIE)
Module Base + 0x000C
7
6
5
4
3
2
1
0
C7I
C6I
C5I
C4I
C3I
C2I
C1I
C0I
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-18. Timer Interrupt Enable Register (TIE)
Read: Anytime
Write: Anytime.
Table 8-13. TIE Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero
Field
Description
7:0
C7I:C0I
Input Capture/Output Compare “x” Interrupt Enable — The bits in TIE correspond bit-for-bit with the bits in
the TFLG1 status register. If cleared, the corresponding flag is disabled from causing a hardware interrupt. If set,
the corresponding flag is enabled to cause a interrupt.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
308
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.3.2.11
Timer System Control Register 2 (TSCR2)
Module Base + 0x000D
7
R
6
5
4
0
0
0
TOI
3
2
1
0
TCRE
PR2
PR1
PR0
0
0
0
0
W
Reset
0
0
0
0
= Unimplemented or Reserved
Figure 8-19. Timer System Control Register 2 (TSCR2)
Read: Anytime
Write: Anytime.
Table 8-14. TSCR2 Field Descriptions
Field
7
TOI
Description
Timer Overflow Interrupt Enable
0 Interrupt inhibited.
1 Hardware interrupt requested when TOF flag set.
3
TCRE
Timer Counter Reset Enable — This bit allows the timer counter to be reset by a successful output compare 7
event. This mode of operation is similar to an up-counting modulus counter.
0 Counter reset inhibited and counter free runs.
1 Counter reset by a successful output compare 7.
Note: If TC7 = 0x0000 and TCRE = 1, TCNT will stay at 0x0000 continuously. If TC7 = 0xFFFF and TCRE = 1,
TOF will never be set when TCNT is reset from 0xFFFF to 0x0000.
Note: TCRE=1 and TC7!=0, the TCNT cycle period will be TC7 x "prescaler counter width" + "1 Bus Clock", for
a more detail explanation please refer to Section 8.4.3, “Output Compare
Note: This bit and feature is available only when channel 7 exists. If channel 7 doesn’t exist, this bit is reserved.
Writing to reserved bit has no effect. Read from reserved bit return a zero.
2:0
PR[2:0]
Timer Prescaler Select — These three bits select the frequency of the timer prescaler clock derived from the
Bus Clock as shown in Table 8-15.
Table 8-15. Timer Clock Selection
PR2
PR1
PR0
Timer Clock
0
0
0
Bus Clock / 1
0
0
1
Bus Clock / 2
0
1
0
Bus Clock / 4
0
1
1
Bus Clock / 8
1
0
0
Bus Clock / 16
1
0
1
Bus Clock / 32
1
1
0
Bus Clock / 64
1
1
1
Bus Clock / 128
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
309
Chapter 8 Timer Module (TIM16B8CV3) Block Description
NOTE
The newly selected prescale factor will not take effect until the next
synchronized edge where all prescale counter stages equal zero.
8.3.2.12
Main Timer Interrupt Flag 1 (TFLG1)
Module Base + 0x000E
7
6
5
4
3
2
1
0
C7F
C6F
C5F
C4F
C3F
C2F
C1F
C0F
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-20. Main Timer Interrupt Flag 1 (TFLG1)
Read: Anytime
Write: Used in the clearing mechanism (set bits cause corresponding bits to be cleared). Writing a zero
will not affect current status of the bit.
Table 8-16. TRLG1 Field Descriptions
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero.
Field
Description
7:0
C[7:0]F
Input Capture/Output Compare Channel “x” Flag — These flags are set when an input capture or output
compare event occurs. Clearing requires writing a one to the corresponding flag bit while TEN or PAEN is set to
one.
Note: When TFFCA bit in TSCR register is set, a read from an input capture or a write into an output compare
channel (0x0010–0x001F) will cause the corresponding channel flag CxF to be cleared.
8.3.2.13
Main Timer Interrupt Flag 2 (TFLG2)
Module Base + 0x000F
7
R
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
TOF
W
Reset
0
Unimplemented or Reserved
Figure 8-21. Main Timer Interrupt Flag 2 (TFLG2)
TFLG2 indicates when interrupt conditions have occurred. To clear a bit in the flag register, write the bit
to one while TEN bit of TSCR1 or PAEN bit of PACTL is set to one.
Read: Anytime
Write: Used in clearing mechanism (set bits cause corresponding bits to be cleared).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
310
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Any access to TCNT will clear TFLG2 register if the TFFCA bit in TSCR register is set.
Table 8-17. TRLG2 Field Descriptions
Field
Description
7
TOF
Timer Overflow Flag — Set when 16-bit free-running timer overflows from 0xFFFF to 0x0000. Clearing this bit
requires writing a one to bit 7 of TFLG2 register while the TEN bit of TSCR1 or PAEN bit of PACTL is set to one
(See also TCRE control bit explanation) .
8.3.2.14
Timer Input Capture/Output Compare Registers High and Low 0–
7(TCxH and TCxL)
0x0018=TC4H
0x001A=TC5H
0x001C=TC6H
0x001E=TC7H
Module Base + 0x0010 = TC0H
0x0012 = TC1H
0x0014=TC2H
0x0016=TC3H
15
14
13
12
11
10
9
0
Bit 15
Bit 14
Bit 13
Bit 12
Bit 11
Bit 10
Bit 9
Bit 8
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-22. Timer Input Capture/Output Compare Register x High (TCxH)
0x0019 =TC4L
0x001B=TC5L
0x001D=TC6L
0x001F=TC7L
Module Base + 0x0011 = TC0L
0x0013 = TC1L
0x0015 =TC2L
0x0017=TC3L
7
6
5
4
3
2
1
0
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-23. Timer Input Capture/Output Compare Register x Low (TCxL)
1
This register is available only when the corresponding channel exists and is reserved if that channel does not exist. Writes to
a reserved register have no functional effect. Reads from a reserved register return zeroes.
Depending on the TIOS bit for the corresponding channel, these registers are used to latch the value of the
free-running counter when a defined transition is sensed by the corresponding input capture edge detector
or to trigger an output action for output compare.
Read: Anytime
Write: Anytime for output compare function.Writes to these registers have no meaning or effect during
input capture. All timer input capture/output compare registers are reset to 0x0000.
NOTE
Read/Write access in byte mode for high byte should take place before low
byte otherwise it will give a different result.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
311
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.3.2.15
16-Bit Pulse Accumulator Control Register (PACTL)
Module Base + 0x0020
7
R
6
5
4
3
2
1
0
PAEN
PAMOD
PEDGE
CLK1
CLK0
PAOVI
PAI
0
0
0
0
0
0
0
0
W
Reset
0
Unimplemented or Reserved
Figure 8-24. 16-Bit Pulse Accumulator Control Register (PACTL)
Read: Any time
Write: Any time
When PAEN is set, the Pulse Accumulator counter is enabled. The Pulse Accumulator counter shares the
input pin with IOC7.
Table 8-18. PACTL Field Descriptions
Field
6
PAEN
Description
Pulse Accumulator System Enable — PAEN is independent from TEN. With timer disabled, the pulse
accumulator can function unless pulse accumulator is disabled.
0 16-Bit Pulse Accumulator system disabled.
1 Pulse Accumulator system enabled.
5
PAMOD
Pulse Accumulator Mode — This bit is active only when the Pulse Accumulator is enabled (PAEN = 1). See
Table 8-19.
0 Event counter mode.
1 Gated time accumulation mode.
4
PEDGE
Pulse Accumulator Edge Control — This bit is active only when the Pulse Accumulator is enabled (PAEN = 1).
For PAMOD bit = 0 (event counter mode). See Table 8-19.
0 Falling edges on IOC7 pin cause the count to be increased.
1 Rising edges on IOC7 pin cause the count to be increased.
For PAMOD bit = 1 (gated time accumulation mode).
0 IOC7 input pin high enables M (Bus clock) divided by 64 clock to Pulse Accumulator and the trailing falling
edge on IOC7 sets the PAIF flag.
1 IOC7 input pin low enables M (Bus clock) divided by 64 clock to Pulse Accumulator and the trailing rising edge
on IOC7 sets the PAIF flag.
3:2
CLK[1:0]
Clock Select Bits — Refer to Table 8-20.
1
PAOVI
0
PAI
Pulse Accumulator Overflow Interrupt Enable
0 Interrupt inhibited.
1 Interrupt requested if PAOVF is set.
Pulse Accumulator Input Interrupt Enable
0 Interrupt inhibited.
1 Interrupt requested if PAIF is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
312
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Table 8-19. Pin Action
PAMOD
PEDGE
Pin Action
0
0
Falling edge
0
1
Rising edge
1
0
Div. by 64 clock enabled with pin high level
1
1
Div. by 64 clock enabled with pin low level
NOTE
If the timer is not active (TEN = 0 in TSCR), there is no divide-by-64
because the ÷64 clock is generated by the timer prescaler.
Table 8-20. Timer Clock Selection
CLK1
CLK0
Timer Clock
0
0
Use timer prescaler clock as timer counter clock
0
1
Use PACLK as input to timer counter clock
1
0
Use PACLK/256 as timer counter clock frequency
1
1
Use PACLK/65536 as timer counter clock frequency
For the description of PACLK please refer Figure 8-30.
If the pulse accumulator is disabled (PAEN = 0), the prescaler clock from the timer is always used as an
input clock to the timer counter. The change from one selected clock to the other happens immediately
after these bits are written.
8.3.2.16
1
Pulse Accumulator Flag Register (PAFLG)
.
Module Base + 0x0021
R
7
6
5
4
3
2
0
0
0
0
0
0
1
0
PAOVF
PAIF
0
0
W
Reset
0
0
0
0
0
0
Unimplemented or Reserved
Figure 8-25. Pulse Accumulator Flag Register (PAFLG)
Read: Anytime
Write: Anytime
When the TFFCA bit in the TSCR register is set, any access to the PACNT register will clear all the flags
in the PAFLG register. Timer module or Pulse Accumulator must stay enabled (TEN=1 or PAEN=1) while
clearing these bits.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
313
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Table 8-21. PAFLG Field Descriptions
Field
Description
1
PAOVF
Pulse Accumulator Overflow Flag — Set when the 16-bit pulse accumulator overflows from 0xFFFF to 0x0000.
Clearing this bit requires writing a one to this bit in the PAFLG register while TEN bit of TSCR1 or PAEN bit of
PACTL register is set to one.
0
PAIF
Pulse Accumulator Input edge Flag — Set when the selected edge is detected at the IOC7 input pin.In event
mode the event edge triggers PAIF and in gated time accumulation mode the trailing edge of the gate signal at
the IOC7 input pin triggers PAIF.
Clearing this bit requires writing a one to this bit in the PAFLG register while TEN bit of TSCR1 or PAEN bit of
PACTL register is set to one. Any access to the PACNT register will clear all the flags in this register when TFFCA
bit in register TSCR(0x0006) is set.
8.3.2.17
Pulse Accumulators Count Registers (PACNT)
Module Base + 0x0022
15
14
13
12
11
10
9
0
PACNT15
PACNT14
PACNT13
PACNT12
PACNT11
PACNT10
PACNT9
PACNT8
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-26. Pulse Accumulator Count Register High (PACNTH)
1
.
Module Base + 0x0023
7
6
5
4
3
2
1
0
PACNT7
PACNT6
PACNT5
PACNT4
PACNT3
PACNT2
PACNT1
PACNT0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-27. Pulse Accumulator Count Register Low (PACNTL)
Read: Anytime
Write: Anytime
These registers contain the number of active input edges on its input pin since the last reset.
When PACNT overflows from 0xFFFF to 0x0000, the Interrupt flag PAOVF in PAFLG (0x0021) is set.
Full count register access should take place in one clock cycle. A separate read/write for high byte and low
byte will give a different result than accessing them as a word.
NOTE
Reading the pulse accumulator counter registers immediately after an active
edge on the pulse accumulator input pin may miss the last count because the
input has to be synchronized with the Bus clock first.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
314
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.3.2.18
Output Compare Pin Disconnect Register(OCPD)
Module Base + 0x002C
7
6
5
4
3
2
1
0
OCPD7
OCPD6
OCPD5
OCPD4
OCPD3
OCPD2
OCPD1
OCPD0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-28. Output Compare Pin Disconnect Register (OCPD)
Read: Anytime
Write: Anytime
All bits reset to zero.
Table 8-22. OCPD Field Description
Note: Writing to unavailable bits has no effect. Reading from unavailable bits return a zero.
Field
Description
7:0
OCPD[7:0]
Output Compare Pin Disconnect Bits
0 Enables the timer channel port. Output Compare action will occur on the channel pin. These bits do not affect
the input capture or pulse accumulator functions.
1 Disables the timer channel port. Output Compare action will not occur on the channel pin, but the output
compare flag still become set.
8.3.2.19
Precision Timer Prescaler Select Register (PTPSR)
Module Base + 0x002E
7
6
5
4
3
2
1
0
PTPS7
PTPS6
PTPS5
PTPS4
PTPS3
PTPS2
PTPS1
PTPS0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 8-29. Precision Timer Prescaler Select Register (PTPSR)
Read: Anytime
Write: Anytime
All bits reset to zero.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
315
Chapter 8 Timer Module (TIM16B8CV3) Block Description
...
Table 8-23. PTPSR Field Descriptions
Field
Description
7:0
PTPS[7:0]
Precision Timer Prescaler Select Bits — These eight bits specify the division rate of the main Timer prescaler.
These are effective only when the PRNT bit of TSCR1 is set to 1. Table 8-24 shows some selection examples in
this case.
The newly selected prescale factor will not take effect until the next synchronized edge where all prescale counter
stages equal zero.
The Prescaler can be calculated as follows depending on logical value of the PTPS[7:0] and PRNT bit:
PRNT = 1 : Prescaler = PTPS[7:0] + 1
Table 8-24. Precision Timer Prescaler Selection Examples when PRNT = 1
PTPS7
PTPS6
PTPS5
PTPS4
PTPS3
PTPS2
PTPS1
PTPS0
Prescale
Factor
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
1
2
0
0
0
0
0
0
1
0
3
0
0
0
0
0
0
1
1
4
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
8.4
-
-
-
-
-
-
-
-
-
0
0
0
1
0
0
1
1
20
0
0
0
1
0
1
0
0
21
0
0
0
1
0
1
0
1
22
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1
1
1
1
1
1
0
0
253
1
1
1
1
1
1
0
1
254
1
1
1
1
1
1
1
0
255
1
1
1
1
1
1
1
1
256
Functional Description
This section provides a complete functional description of the timer TIM16B8CV3 block. Please refer to
the detailed timer block diagram in Figure 8-30 as necessary.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
316
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
PTPSR[7:0]
PRE-PRESCALER
MUX
PRNT
tim source Clock
CLK[1:0]
PACLK
PACLK/256
PACLK/65536
PR[2:1:0]
channel 7 output
compare
1
MUX
0
PRESCALER
TCRE
CxI
TCNT(hi):TCNT(lo)
CxF
CLEAR COUNTER
16-BIT COUNTER
TOF
INTERRUPT
LOGIC
TOI
TE
TOF
CHANNEL 0
16-BIT COMPARATOR
C0F
C0F
OM:OL0
TC0
EDG0A
TOV0
EDGE
DETECT
EDG0B
CH. 0 CAPTURE
IOC0 PIN
LOGIC CH. 0COMPARE
IOC0 PIN
IOC0
CHANNEL 1
16-BIT COMPARATOR
C1F
C1F
OM:OL1
TC1
EDG1A
EDGE
DETECT
EDG1B
CH. 1 CAPTURE
IOC1 PIN
LOGIC CH. 1 COMPARE
TOV1
IOC1 PIN
IOC1
CHANNEL2
CHANNEL7
16-BIT COMPARATOR
C7F
C7F
TC7
OM:OL7
EDG7A
EDG7B
PAOVF
TOV7
EDGE
DETECT
IOC7
PACNT(hi):PACNT(lo)
PACLK/65536
PEDGE
MUX
16-BIT COUNTER
CH.7 CAPTURE
IOC7 PIN PA INPUT
LOGIC CH. 7 COMPARE IOC7 PIN
PAEN
EDGE
DETECT
PACLK
PACLK/256
TEN
INTERRUPT
REQUEST
PAMOD
INTERRUPT
LOGIC
PAIF
PEDGE
DIVIDE-BY-64
PAOVI
PAI
PAOVF
PAIF
tim source
clock
PAOVF
PAOVI
Maximum possible channels, scalable from 0 to 7.
Pulse Accumulator is available only if channel 7 exists.
Figure 8-30. Detailed Timer Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
317
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.4.1
Prescaler
The prescaler divides the Bus clock by 1, 2, 4, 8, 16, 32, 64 or 128. The prescaler select bits, PR[2:0], select
the prescaler divisor. PR[2:0] are in timer system control register 2 (TSCR2).
The prescaler divides the Bus clock by a prescalar value. Prescaler select bits PR[2:0] of in timer system
control register 2 (TSCR2) are set to define a prescalar value that generates a divide by 1, 2, 4, 8, 16, 32,
64 and 128 when the PRNT bit in TSCR1 is disabled.
By enabling the PRNT bit of the TSCR1 register, the performance of the timer can be enhanced. In this
case, it is possible to set additional prescaler settings for the main timer counter in the present timer by
using PTPSR[7:0] bits of PTPSR register generating divide by 1, 2, 3, 4,....20, 21, 22, 23,......255, or 256.
8.4.2
Input Capture
Clearing the I/O (input/output) select bit, IOSx, configures channel x as an input capture channel. The
input capture function captures the time at which an external event occurs. When an active edge occurs on
the pin of an input capture channel, the timer transfers the value in the timer counter into the timer channel
registers, TCx.
The minimum pulse width for the input capture input is greater than two Bus clocks.
An input capture on channel x sets the CxF flag. The CxI bit enables the CxF flag to generate interrupt
requests. Timer module or Pulse Accumulator must stay enabled (TEN bit of TSCR1 or PAEN bit of
PACTL register must be set to one) while clearing CxF (writing one to CxF).
8.4.3
Output Compare
Setting the I/O select bit, IOSx, configures channel x when available as an output compare channel. The
output compare function can generate a periodic pulse with a programmable polarity, duration, and
frequency. When the timer counter reaches the value in the channel registers of an output compare channel,
the timer can set, clear, or toggle the channel pin if the corresponding OCPDx bit is set to zero. An output
compare on channel x sets the CxF flag. The CxI bit enables the CxF flag to generate interrupt requests.
Timer module or Pulse Accumulator must stay enabled (TEN bit of TSCR1 or PAEN bit of PACTL register
must be set to one) while clearing CxF (writing one to CxF).
The output mode and level bits, OMx and OLx, select set, clear, toggle on output compare. Clearing both
OMx and OLx results in no output compare action on the output compare channel pin.
Setting a force output compare bit, FOCx, causes an output compare on channel x. A forced output
compare does not set the channel flag.
A channel 7 event, which can be a counter overflow when TTOV[7] is set or a successful output compare
on channel 7, overrides output compares on all other output compare channels. The output compare 7 mask
register masks the bits in the output compare 7 data register. The timer counter reset enable bit, TCRE,
enables channel 7 output compares to reset the timer counter. A channel 7 output compare can reset the
timer counter even if the IOC7 pin is being used as the pulse accumulator input.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
318
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Writing to the timer port bit of an output compare pin does not affect the pin state. The value written is
stored in an internal latch. When the pin becomes available for general-purpose output, the last value
written to the bit appears at the pin.
When TCRE is set and TC7 is not equal to 0, then TCNT will cycle from 0 to TC7. When TCNT reaches
TC7 value, it will last only one Bus cycle then reset to 0.
Note: in Figure 8-31,if PR[2:0] is equal to 0, one prescaler counter equal to one Bus clock
Figure 8-31. The TCNT cycle diagram under TCRE=1 condition
prescaler
counter
TC7
0
1 Bus
clock
1
TC7-1
TC7
0
TC7 event
TC7 event
8.4.3.1
-----
OC Channel Initialization
The internal register whose output drives OCx can be programmed before the timer drives OCx. The
desired state can be programmed to this internal register by writing a one to CFORCx bit with TIOSx,
OCPDx and TEN bits set to one.
Set OCx: Write a 1 to FOCx while TEN=1, IOSx=1, OMx=1, OLx=1 and OCPDx=1
Clear OCx: Write a 1 to FOCx while TEN=1, IOSx=1, OMx=1, OLx=0 and OCPDx=1
Setting OCPDx to zero allows the internal register to drive the programmed state to OCx. This allows a
glitch free switch over of port from general purpose I/O to timer output once the OCPDx bit is set to zero.
8.4.4
Pulse Accumulator
The pulse accumulator (PACNT) is a 16-bit counter that can operate in two modes:
Event counter mode — Counting edges of selected polarity on the pulse accumulator input pin, PAI.
Gated time accumulation mode — Counting pulses from a divide-by-64 clock. The PAMOD bit selects the
mode of operation.
The minimum pulse width for the PAI input is greater than two Bus clocks.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
319
Chapter 8 Timer Module (TIM16B8CV3) Block Description
8.4.5
Event Counter Mode
Clearing the PAMOD bit configures the PACNT for event counter operation. An active edge on the IOC7
pin increments the pulse accumulator counter. The PEDGE bit selects falling edges or rising edges to
increment the count.
NOTE
The PACNT input and timer channel 7 use the same pin IOC7. To use the
IOC7, disconnect it from the output logic by clearing the channel 7 output
mode and output level bits, OM7 and OL7. Also clear the channel 7 output
compare 7 mask bit, OC7M7.
The Pulse Accumulator counter register reflect the number of active input edges on the PACNT input pin
since the last reset.
The PAOVF bit is set when the accumulator rolls over from 0xFFFF to 0x0000. The pulse accumulator
overflow interrupt enable bit, PAOVI, enables the PAOVF flag to generate interrupt requests.
NOTE
The pulse accumulator counter can operate in event counter mode even
when the timer enable bit, TEN, is clear.
8.4.6
Gated Time Accumulation Mode
Setting the PAMOD bit configures the pulse accumulator for gated time accumulation operation. An active
level on the PACNT input pin enables a divided-by-64 clock to drive the pulse accumulator. The PEDGE
bit selects low levels or high levels to enable the divided-by-64 clock.
The trailing edge of the active level at the IOC7 pin sets the PAIF. The PAI bit enables the PAIF flag to
generate interrupt requests.
The pulse accumulator counter register reflect the number of pulses from the divided-by-64 clock since the
last reset.
NOTE
The timer prescaler generates the divided-by-64 clock. If the timer is not
active, there is no divided-by-64 clock.
8.5
Resets
The reset state of each individual bit is listed within Section 8.3, “Memory Map and Register Definition”
which details the registers and their bit fields
8.6
Interrupts
This section describes interrupts originated by the TIM16B8CV3 block. Table 8-25 lists the interrupts
generated by the TIM16B8CV3 to communicate with the MCU.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
320
Freescale Semiconductor
Chapter 8 Timer Module (TIM16B8CV3) Block Description
Table 8-25. TIM16B8CV3 Interrupts
Interrupt
Offset
Vector
Priority
Source
Description
C[7:0]F
—
—
—
Timer Channel 7–0
Active high timer channel interrupts 7–0
PAOVI
—
—
—
Pulse Accumulator
Input
Active high pulse accumulator input interrupt
PAOVF
—
—
—
Pulse Accumulator
Overflow
Pulse accumulator overflow interrupt
TOF
—
—
—
Timer Overflow
Timer Overflow interrupt
The TIM16B8CV3 could use up to 11 interrupt vectors. The interrupt vector offsets and interrupt numbers
are chip dependent.
8.6.1
Channel [7:0] Interrupt (C[7:0]F)
This active high outputs will be asserted by the module to request a timer channel 7 – 0 interrupt. The TIM
block only generates the interrupt and does not service it. Only bits related to implemented channels are
valid.
8.6.2
Pulse Accumulator Input Interrupt (PAOVI)
This active high output will be asserted by the module to request a timer pulse accumulator input interrupt.
The TIM block only generates the interrupt and does not service it.
8.6.3
Pulse Accumulator Overflow Interrupt (PAOVF)
This active high output will be asserted by the module to request a timer pulse accumulator overflow
interrupt. The TIM block only generates the interrupt and does not service it.
8.6.4
Timer Overflow Interrupt (TOF)
This active high output will be asserted by the module to request a timer overflow interrupt. The TIM block
only generates the interrupt and does not service it.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
321
Chapter 8 Timer Module (TIM16B8CV3) Block Description
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
322
Freescale Semiconductor
Chapter 9
Pulse-Width Modulator (S12PWM8B8CV2)
Table 9-1. Revision History
Revision
Number
Revision Date
Sections
Affected
v02.00
Feb. 20, 2009
All
9.1
Description of Changes
Initial revision of scalable PWM. Started from pwm_8b8c (v01.08).
Introduction
The Version 2 of S12 PWM module is a channel scalable and optimized implementation of S12
PWM8B8C Version 1. The channel is scalable in pairs from PWM0 to PWM7 and the available channel
number is 2, 4, 6 and 8. The shutdown feature has been removed and the flexibility to select one of four
clock sources per channel has improved. If the corresponding channels exist and shutdown feature is not
used, the Version 2 is fully software compatible to Version 1.
9.1.1
Features
The scalable PWM block includes these distinctive features:
• Up to eight independent PWM channels, scalable in pairs (PWM0 to PWM7)
• Available channel number could be 2, 4, 6, 8 (refer to device specification for exact number)
• Programmable period and duty cycle for each channel
• Dedicated counter for each PWM channel
• Programmable PWM enable/disable for each channel
• Software selection of PWM duty pulse polarity for each channel
• Period and duty cycle are double buffered. Change takes effect when the end of the effective period
is reached (PWM counter reaches zero) or when the channel is disabled.
• Programmable center or left aligned outputs on individual channels
• Up to eight 8-bit channel or four 16-bit channel PWM resolution
• Four clock sources (A, B, SA, and SB) provide for a wide range of frequencies
• Programmable clock select logic
9.1.2
Modes of Operation
There is a software programmable option for low power consumption in wait mode that disables the input
clock to the prescaler.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
323
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
In freeze mode there is a software programmable option to disable the input clock to the prescaler. This is
useful for emulation.
Wait:
The prescaler keeps on running, unless PSWAI in PWMCTL is set to 1.
Freeze:
The prescaler keeps on running, unless PFRZ in PWMCTL is set to 1.
9.1.3
Block Diagram
Figure 9-1 shows the block diagram for the 8-bit up to 8-channel scalable PWM block.
PWM8B8C
PWM Channels
Channel 7
Period and Duty
Counter
Channel 6
Bus Clock
Clock Select
PWM Clock
Period and Duty
PWM6
Counter
Channel 5
Period and Duty
PWM7
PWM5
Counter
Control
Channel 4
Period and Duty
PWM4
Counter
Channel 3
Period and Duty
Enable
PWM3
Counter
Channel 2
Polarity
Period and Duty
Alignment
PWM2
Counter
Channel 1
Period and Duty
PWM1
Counter
Channel 0
Period and Duty
Counter
PWM0
Maximum possible channels, scalable in pairs from PWM0 to PWM7.
Figure 9-1. Scalable PWM Block Diagram
9.2
External Signal Description
The scalable PWM module has a selected number of external pins. Refer to device specification for exact
number.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
324
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
9.2.1
PWM7 - PWM0 — PWM Channel 7 - 0
Those pins serve as waveform output of PWM channel 7 - 0.
9.3
Memory Map and Register Definition
9.3.1
Module Memory Map
This section describes the content of the registers in the scalable PWM module. The base address of the
scalable PWM module is determined at the MCU level when the MCU is defined. The register decode map
is fixed and begins at the first address of the module address offset. The figure below shows the registers
associated with the scalable PWM and their relative offset from the base address. The register detail
description follows the order they appear in the register map.
Reserved bits within a register will always read as 0 and the write will be unimplemented. Unimplemented
functions are indicated by shading the bit.
NOTE
Register Address = Base Address + Address Offset, where the Base Address
is defined at the MCU level and the Address Offset is defined at the module
level.
9.3.2
Register Descriptions
This section describes in detail all the registers and register bits in the scalable PWM module.
Register
Name
0x0000
PWME(1)
R
W
0x0001
PWMPOL1
W
0x0002
PWMCLK1
W
R
R
0x0003
R
PWMPRCLK W
0x0004
R
PWMCAE1 W
0x0005
PWMCTL1
R
W
Bit 7
6
5
4
3
2
1
Bit 0
PWME7
PWME6
PWME5
PWME4
PWME3
PWME2
PWME1
PWME0
PPOL7
PPOL6
PPOL5
PPOL4
PPOL3
PPOL2
PPOL1
PPOL0
PCLK7
PCLKL6
PCLK5
PCLK4
PCLK3
PCLK2
PCLK1
PCLK0
PCKB2
PCKB1
PCKB0
PCKA2
PCKA1
PCKA0
CAE7
CAE6
CAE5
CAE4
CAE3
CAE2
CAE1
CAE0
CON67
CON45
CON23
CON01
PSWAI
PFRZ
0
0
0
0
= Unimplemented or Reserved
Figure 9-2. The scalable PWM Register Summary (Sheet 1 of 4)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
325
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Register
Name
Bit 7
6
5
4
3
2
1
Bit 0
PCLKAB6
PCLKAB5
PCLKAB4
PCLKAB3
PCLKAB2
PCLKAB1
PCLKAB0
0
0
0
0
0
0
0
0
0x0008
R
PWMSCLA W
Bit 7
6
5
4
3
2
1
Bit 0
0x0009
R
PWMSCLB W
Bit 7
6
5
4
3
2
1
Bit 0
0x000A
R
RESERVED W
0
0
0
0
0
0
0
0
0x000B
R
RESERVED W
0
0
0
0
0
0
0
0
0x000C
R
PWMCNT0 W
(2)
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x000D
PWMCNT12 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x000E
PWMCNT22 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x000F
PWMCNT32 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x0010
PWMCNT42 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x0011
PWMCNT52 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x0012
PWMCNT62 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
R
0x0013
PWMCNT72 W
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
0x0006
R
PWMCLKAB W PCLKAB7
1
0x0007
R
RESERVED W
= Unimplemented or Reserved
Figure 9-2. The scalable PWM Register Summary (Sheet 2 of 4)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
326
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Register
Name
Bit 7
6
5
4
3
2
1
Bit 0
0x0014
R
PWMPER02 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0015
R
PWMPER12 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0016
R
PWMPER22 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0017
R
PWMPER32 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0018
R
PWMPER42 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0019
R
PWMPER52 W
Bit 7
6
5
4
3
2
1
Bit 0
0x001A
R
PWMPER62 W
Bit 7
6
5
4
3
2
1
Bit 0
0x001B
R
PWMPER72 W
Bit 7
6
5
4
3
2
1
Bit 0
0x001C
R
PWMDTY02 W
Bit 7
6
5
4
3
2
1
Bit 0
0x001D
R
PWMDTY12 W
Bit 7
6
5
4
3
2
1
Bit 0
0x001E
R
PWMDTY22 W
Bit 7
6
5
4
3
2
1
Bit 0
0x001F
R
PWMDTY32 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0010
R
PWMDTY42 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0021
R
PWMDTY52 W
Bit 7
6
5
4
3
2
1
Bit 0
0x0022
R
PWMDTY62 W
Bit 7
6
5
4
3
2
1
Bit 0
= Unimplemented or Reserved
Figure 9-2. The scalable PWM Register Summary (Sheet 3 of 4)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
327
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Register
Name
Bit 7
6
5
4
3
2
1
Bit 0
Bit 7
6
5
4
3
2
1
Bit 0
0x0024
R
RESERVED W
0
0
0
0
0
0
0
0
0x0025
R
RESERVED W
0
0
0
0
0
0
0
0
0x0026
R
RESERVED W
0
0
0
0
0
0
0
0
0x0027
R
RESERVED W
0
0
0
0
0
0
0
0
0x0023
R
PWMDTY72 W
= Unimplemented or Reserved
Figure 9-2. The scalable PWM Register Summary (Sheet 4 of 4)
1. The related bit is available only if corresponding channel exists.
2. The register is available only if corresponding channel exists.
9.3.2.1
PWM Enable Register (PWME)
Each PWM channel has an enable bit (PWMEx) to start its waveform output. When any of the PWMEx
bits are set (PWMEx = 1), the associated PWM output is enabled immediately. However, the actual PWM
waveform is not available on the associated PWM output until its clock source begins its next cycle due to
the synchronization of PWMEx and the clock source.
NOTE
The first PWM cycle after enabling the channel can be irregular.
An exception to this is when channels are concatenated. Once concatenated mode is enabled (CONxx bits
set in PWMCTL register), enabling/disabling the corresponding 16-bit PWM channel is controlled by the
low order PWMEx bit. In this case, the high order bytes PWMEx bits have no effect and their
corresponding PWM output lines are disabled.
While in run mode, if all existing PWM channels are disabled (PWMEx–0 = 0), the prescaler counter shuts
off for power savings.
Module Base + 0x0000
R
W
Reset
7
6
5
4
3
2
1
0
PWME7
PWME6
PWME5
PWME4
PWME3
PWME2
PWME1
PWME0
0
0
0
0
0
0
0
0
Figure 9-3. PWM Enable Register (PWME)
Read: Anytime
Write: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
328
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Table 9-2. PWME Field Descriptions
Note: Bits related to available channels have functional significance. Writing to unavailable bits has no effect. Read from
unavailable bits return a zero
Field
Description
7
PWME7
Pulse Width Channel 7 Enable
0 Pulse width channel 7 is disabled.
1 Pulse width channel 7 is enabled. The pulse modulated signal becomes available at PWM output bit 7 when
its clock source begins its next cycle.
6
PWME6
Pulse Width Channel 6 Enable
0 Pulse width channel 6 is disabled.
1 Pulse width channel 6 is enabled. The pulse modulated signal becomes available at PWM output bit 6 when
its clock source begins its next cycle. If CON67=1, then bit has no effect and PWM output line 6 is disabled.
5
PWME5
Pulse Width Channel 5 Enable
0 Pulse width channel 5 is disabled.
1 Pulse width channel 5 is enabled. The pulse modulated signal becomes available at PWM output bit 5 when
its clock source begins its next cycle.
4
PWME4
Pulse Width Channel 4 Enable
0 Pulse width channel 4 is disabled.
1 Pulse width channel 4 is enabled. The pulse modulated signal becomes available at PWM, output bit 4 when
its clock source begins its next cycle. If CON45 = 1, then bit has no effect and PWM output line 4 is disabled.
3
PWME3
Pulse Width Channel 3 Enable
0 Pulse width channel 3 is disabled.
1 Pulse width channel 3 is enabled. The pulse modulated signal becomes available at PWM, output bit 3 when
its clock source begins its next cycle.
2
PWME2
Pulse Width Channel 2 Enable
0 Pulse width channel 2 is disabled.
1 Pulse width channel 2 is enabled. The pulse modulated signal becomes available at PWM, output bit 2 when
its clock source begins its next cycle. If CON23 = 1, then bit has no effect and PWM output line 2 is disabled.
1
PWME1
Pulse Width Channel 1 Enable
0 Pulse width channel 1 is disabled.
1 Pulse width channel 1 is enabled. The pulse modulated signal becomes available at PWM, output bit 1 when
its clock source begins its next cycle.
0
PWME0
Pulse Width Channel 0 Enable
0 Pulse width channel 0 is disabled.
1 Pulse width channel 0 is enabled. The pulse modulated signal becomes available at PWM, output bit 0 when
its clock source begins its next cycle. If CON01 = 1, then bit has no effect and PWM output line 0 is disabled.
9.3.2.2
PWM Polarity Register (PWMPOL)
The starting polarity of each PWM channel waveform is determined by the associated PPOLx bit in the
PWMPOL register. If the polarity bit is one, the PWM channel output is high at the beginning of the cycle
and then goes low when the duty count is reached. Conversely, if the polarity bit is zero, the output starts
low and then goes high when the duty count is reached.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
329
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Module Base + 0x0001
R
W
Reset
7
6
5
4
3
2
1
0
PPOL7
PPOL6
PPOL5
PPOL4
PPOL3
PPOL2
PPOL1
PPOL0
0
0
0
0
0
0
0
0
Figure 9-4. PWM Polarity Register (PWMPOL)
Read: Anytime
Write: Anytime
NOTE
PPOLx register bits can be written anytime. If the polarity is changed while
a PWM signal is being generated, a truncated or stretched pulse can occur
during the transition
Table 9-3. PWMPOL Field Descriptions
Note: Bits related to available channels have functional significance. Writing to unavailable bits has no effect. Read from
unavailable bits return a zero
Field
7–0
PPOL[7:0]
9.3.2.3
Description
Pulse Width Channel 7–0 Polarity Bits
0 PWM channel 7–0 outputs are low at the beginning of the period, then go high when the duty count is
reached.
1 PWM channel 7–0 outputs are high at the beginning of the period, then go low when the duty count is
reached.
PWM Clock Select Register (PWMCLK)
Each PWM channel has a choice of four clocks to use as the clock source for that channel as described
below.
Module Base + 0x0002
R
W
Reset
7
6
5
4
3
2
1
0
PCLK7
PCLKL6
PCLK5
PCLK4
PCLK3
PCLK2
PCLK1
PCLK0
0
0
0
0
0
0
0
0
Figure 9-5. PWM Clock Select Register (PWMCLK)
Read: Anytime
Write: Anytime
NOTE
Register bits PCLK0 to PCLK7 can be written anytime. If a clock select is
changed while a PWM signal is being generated, a truncated or stretched
pulse can occur during the transition.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
330
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Table 9-4. PWMCLK Field Descriptions
Note: Bits related to available channels have functional significance. Writing to unavailable bits has no effect. Read from
unavailable bits return a zero
Field
7-0
PCLK[7:0]
Description
Pulse Width Channel 7-0 Clock Select
0 Clock A or B is the clock source for PWM channel 7-0, as shown in Table 9-5 and Table 9-6.
1 Clock SA or SB is the clock source for PWM channel 7-0, as shown in Table 9-5 and Table 9-6.
The clock source of each PWM channel is determined by PCLKx bits in PWMCLK and PCLKABx bits
in PWMCLKAB (see Section 9.3.2.7, “PWM Clock A/B Select Register (PWMCLKAB)). For Channel
0, 1, 4, 5, the selection is shown in Table 9-5; For Channel 2, 3, 6, 7, the selection is shown in Table 9-6.
Table 9-5. PWM Channel 0, 1, 4, 5 Clock Source Selection
PCLKAB[0,1,4,5]
PCLK[0,1,4,5]
Clock Source Selection
0
0
1
1
0
1
0
1
Clock A
Clock SA
Clock B
Clock SB
Table 9-6. PWM Channel 2, 3, 6, 7 Clock Source Selection
9.3.2.4
PCLKAB[2,3,6,7]
PCLK[2,3,6,7]
Clock Source Selection
0
0
1
1
0
1
0
1
Clock B
Clock SB
Clock A
Clock SA
PWM Prescale Clock Select Register (PWMPRCLK)
This register selects the prescale clock source for clocks A and B independently.
Module Base + 0x0003
7
R
6
0
W
Reset
0
5
4
PCKB2
PCKB1
PCKB0
0
0
0
3
0
0
2
1
0
PCKA2
PCKA1
PCKA0
0
0
0
= Unimplemented or Reserved
Figure 9-6. PWM Prescale Clock Select Register (PWMPRCLK)
Read: Anytime
Write: Anytime
NOTE
PCKB2–0 and PCKA2–0 register bits can be written anytime. If the clock
pre-scale is changed while a PWM signal is being generated, a truncated or
stretched pulse can occur during the transition.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
331
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Table 9-7. PWMPRCLK Field Descriptions
Field
Description
6–4
PCKB[2:0]
Prescaler Select for Clock B — Clock B is one of two clock sources which can be used for all channels. These
three bits determine the rate of clock B, as shown in Table 9-8.
2–0
PCKA[2:0]
Prescaler Select for Clock A — Clock A is one of two clock sources which can be used for all channels. These
three bits determine the rate of clock A, as shown in Table 9-8.
s
Table 9-8. Clock A or Clock B Prescaler Selects
9.3.2.5
PCKA/B2
PCKA/B1
PCKA/B0
Value of Clock A/B
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
Bus clock
Bus clock / 2
Bus clock / 4
Bus clock / 8
Bus clock / 16
Bus clock / 32
Bus clock / 64
Bus clock / 128
PWM Center Align Enable Register (PWMCAE)
The PWMCAE register contains eight control bits for the selection of center aligned outputs or left aligned
outputs for each PWM channel. If the CAEx bit is set to a one, the corresponding PWM output will be
center aligned. If the CAEx bit is cleared, the corresponding PWM output will be left aligned. See
Section 9.4.2.5, “Left Aligned Outputs” and Section 9.4.2.6, “Center Aligned Outputs” for a more detailed
description of the PWM output modes.
Module Base + 0x0004
R
W
Reset
7
6
5
4
3
2
1
0
CAE7
CAE6
CAE5
CAE4
CAE3
CAE2
CAE1
CAE0
0
0
0
0
0
0
0
0
Figure 9-7. PWM Center Align Enable Register (PWMCAE)
Read: Anytime
Write: Anytime
NOTE
Write these bits only when the corresponding channel is disabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
332
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Table 9-9. PWMCAE Field Descriptions
Note: Bits related to available channels have functional significance. Writing to unavailable bits has no effect. Read from
unavailable bits return a zero
Field
7–0
CAE[7:0]
9.3.2.6
Description
Center Aligned Output Modes on Channels 7–0
0 Channels 7–0 operate in left aligned output mode.
1 Channels 7–0 operate in center aligned output mode.
PWM Control Register (PWMCTL)
The PWMCTL register provides for various control of the PWM module.
Module Base + 0x0005
7
R
W
Reset
6
CON67
0
5
4
3
2
CON45
CON23
CON01
PSWAI
PFRZ
0
0
0
0
0
1
0
0
0
0
0
= Unimplemented or Reserved
Figure 9-8. PWM Control Register (PWMCTL)
Read: Anytime
Write: Anytime
There are up to four control bits for concatenation, each of which is used to concatenate a pair of PWM
channels into one 16-bit channel. If the corresponding channels do not exist on a particular derivative, then
writes to these bits have no effect and reads will return zeroes. When channels 6 and 7are concatenated,
channel 6 registers become the high order bytes of the double byte channel. When channels 4 and 5 are
concatenated, channel 4 registers become the high order bytes of the double byte channel. When channels
2 and 3 are concatenated, channel 2 registers become the high order bytes of the double byte channel.
When channels 0 and 1 are concatenated, channel 0 registers become the high order bytes of the double
byte channel.
See Section 9.4.2.7, “PWM 16-Bit Functions” for a more detailed description of the concatenation PWM
Function.
NOTE
Change these bits only when both corresponding channels are disabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
333
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Table 9-10. PWMCTL Field Descriptions
Note: Bits related to available channels have functional significance. Writing to unavailable bits has no effect. Read from
unavailable bits return a zero
Field
Description
7
CON67
Concatenate Channels 6 and 7
0 Channels 6 and 7 are separate 8-bit PWMs.
1 Channels 6 and 7 are concatenated to create one 16-bit PWM channel. Channel 6 becomes the high order
byte and channel 7 becomes the low order byte. Channel 7 output pin is used as the output for this 16-bit
PWM (bit 7 of port PWMP). Channel 7 clock select control-bit determines the clock source, channel 7 polarity
bit determines the polarity, channel 7 enable bit enables the output and channel 7 center aligned enable bit
determines the output mode.
6
CON45
Concatenate Channels 4 and 5
0 Channels 4 and 5 are separate 8-bit PWMs.
1 Channels 4 and 5 are concatenated to create one 16-bit PWM channel. Channel 4 becomes the high order
byte and channel 5 becomes the low order byte. Channel 5 output pin is used as the output for this 16-bit
PWM (bit 5 of port PWMP). Channel 5 clock select control-bit determines the clock source, channel 5 polarity
bit determines the polarity, channel 5 enable bit enables the output and channel 5 center aligned enable bit
determines the output mode.
5
CON23
Concatenate Channels 2 and 3
0 Channels 2 and 3 are separate 8-bit PWMs.
1 Channels 2 and 3 are concatenated to create one 16-bit PWM channel. Channel 2 becomes the high order
byte and channel 3 becomes the low order byte. Channel 3 output pin is used as the output for this 16-bit
PWM (bit 3 of port PWMP). Channel 3 clock select control-bit determines the clock source, channel 3 polarity
bit determines the polarity, channel 3 enable bit enables the output and channel 3 center aligned enable bit
determines the output mode.
4
CON01
Concatenate Channels 0 and 1
0 Channels 0 and 1 are separate 8-bit PWMs.
1 Channels 0 and 1 are concatenated to create one 16-bit PWM channel. Channel 0 becomes the high order
byte and channel 1 becomes the low order byte. Channel 1 output pin is used as the output for this 16-bit
PWM (bit 1 of port PWMP). Channel 1 clock select control-bit determines the clock source, channel 1 polarity
bit determines the polarity, channel 1 enable bit enables the output and channel 1 center aligned enable bit
determines the output mode.
3
PSWAI
PWM Stops in Wait Mode — Enabling this bit allows for lower power consumption in wait mode by disabling
the input clock to the prescaler.
0 Allow the clock to the prescaler to continue while in wait mode.
1 Stop the input clock to the prescaler whenever the MCU is in wait mode.
2
PFRZ
PWM Counters Stop in Freeze Mode — In freeze mode, there is an option to disable the input clock to the
prescaler by setting the PFRZ bit in the PWMCTL register. If this bit is set, whenever the MCU is in freeze mode,
the input clock to the prescaler is disabled. This feature is useful during emulation as it allows the PWM function
to be suspended. In this way, the counters of the PWM can be stopped while in freeze mode so that once normal
program flow is continued, the counters are re-enabled to simulate real-time operations. Since the registers can
still be accessed in this mode, to re-enable the prescaler clock, either disable the PFRZ bit or exit freeze mode.
0 Allow PWM to continue while in freeze mode.
1 Disable PWM input clock to the prescaler whenever the part is in freeze mode. This is useful for emulation.
9.3.2.7
PWM Clock A/B Select Register (PWMCLKAB)
Each PWM channel has a choice of four clocks to use as the clock source for that channel as described
below.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
334
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Module Base + 0x00006
R
W
7
6
5
4
3
2
1
0
PCLKAB7
PCLKAB6
PCLKAB5
PCLKAB4
PCLKAB3
PCLKAB2
PCLKAB1
PCLKAB0
0
0
0
0
0
0
0
0
Reset
Figure 9-9. PWM Clock Select Register (PWMCLK)
Read: Anytime
Write: Anytime
NOTE
Register bits PCLKAB0 to PCLKAB7 can be written anytime. If a clock
select is changed while a PWM signal is being generated, a truncated or
stretched pulse can occur during the transition.
Table 9-11. PWMCLK Field Descriptions
Note: Bits related to available channels have functional significance. Writing to unavailable bits has no effect. Read from
unavailable bits return a zero
Field
Description
7
PCLKAB7
Pulse Width Channel 7 Clock A/B Select
0 Clock B or SB is the clock source for PWM channel 7, as shown in Table 9-6.
1 Clock A or SA is the clock source for PWM channel 7, as shown in Table 9-6.
6
PCLKAB6
Pulse Width Channel 6 Clock A/B Select
0 Clock B or SB is the clock source for PWM channel 6, as shown in Table 9-6.
1 Clock A or SA is the clock source for PWM channel 6, as shown in Table 9-6.
5
PCLKAB5
Pulse Width Channel 5 Clock A/B Select
0 Clock A or SA is the clock source for PWM channel 5, as shown in Table 9-5.
1 Clock B or SB is the clock source for PWM channel 5, as shown in Table 9-5.
4
PCLKAB4
Pulse Width Channel 4 Clock A/B Select
0 Clock A or SA is the clock source for PWM channel 4, as shown in Table 9-5.
1 Clock B or SB is the clock source for PWM channel 4, as shown in Table 9-5.
3
PCLKAB3
Pulse Width Channel 3 Clock A/B Select
0 Clock B or SB is the clock source for PWM channel 3, as shown in Table 9-6.
1 Clock A or SA is the clock source for PWM channel 3, as shown in Table 9-6.
2
PCLKAB2
Pulse Width Channel 2 Clock A/B Select
0 Clock B or SB is the clock source for PWM channel 2, as shown in Table 9-6.
1 Clock A or SA is the clock source for PWM channel 2, as shown in Table 9-6.
1
PCLKAB1
Pulse Width Channel 1 Clock A/B Select
0 Clock A or SA is the clock source for PWM channel 1, as shown in Table 9-5.
1 Clock B or SB is the clock source for PWM channel 1, as shown in Table 9-5.
0
PCLKAB0
Pulse Width Channel 0 Clock A/B Select
0 Clock A or SA is the clock source for PWM channel 0, as shown in Table 9-5.
1 Clock B or SB is the clock source for PWM channel 0, as shown in Table 9-5.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
335
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
The clock source of each PWM channel is determined by PCLKx bits in PWMCLK (see Section 9.3.2.3,
“PWM Clock Select Register (PWMCLK)) and PCLKABx bits in PWMCLKAB as shown in Table 9-5
and Table 9-6.
9.3.2.8
PWM Scale A Register (PWMSCLA)
PWMSCLA is the programmable scale value used in scaling clock A to generate clock SA. Clock SA is
generated by taking clock A, dividing it by the value in the PWMSCLA register and dividing that by two.
Clock SA = Clock A / (2 * PWMSCLA)
NOTE
When PWMSCLA = $00, PWMSCLA value is considered a full scale value
of 256. Clock A is thus divided by 512.
Any value written to this register will cause the scale counter to load the new scale value (PWMSCLA).
Module Base + 0x0008
R
W
Reset
7
6
5
4
3
2
1
0
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
Figure 9-10. PWM Scale A Register (PWMSCLA)
Read: Anytime
Write: Anytime (causes the scale counter to load the PWMSCLA value)
9.3.2.9
PWM Scale B Register (PWMSCLB)
PWMSCLB is the programmable scale value used in scaling clock B to generate clock SB. Clock SB is
generated by taking clock B, dividing it by the value in the PWMSCLB register and dividing that by two.
Clock SB = Clock B / (2 * PWMSCLB)
NOTE
When PWMSCLB = $00, PWMSCLB value is considered a full scale value
of 256. Clock B is thus divided by 512.
Any value written to this register will cause the scale counter to load the new scale value (PWMSCLB).
Module Base + 0x0009
R
W
Reset
7
6
5
4
3
2
1
0
Bit 7
6
5
4
3
2
1
Bit 0
0
0
0
0
0
0
0
0
Figure 9-11. PWM Scale B Register (PWMSCLB)
Read: Anytime
Write: Anytime (causes the scale counter to load the PWMSCLB value).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
336
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
9.3.2.10
PWM Channel Counter Registers (PWMCNTx)
Each channel has a dedicated 8-bit up/down counter which runs at the rate of the selected clock source.
The counter can be read at any time without affecting the count or the operation of the PWM channel. In
left aligned output mode, the counter counts from 0 to the value in the period register - 1. In center aligned
output mode, the counter counts from 0 up to the value in the period register and then back down to 0.
Any value written to the counter causes the counter to reset to $00, the counter direction to be set to up,
the immediate load of both duty and period registers with values from the buffers, and the output to change
according to the polarity bit. The counter is also cleared at the end of the effective period (see
Section 9.4.2.5, “Left Aligned Outputs” and Section 9.4.2.6, “Center Aligned Outputs” for more details).
When the channel is disabled (PWMEx = 0), the PWMCNTx register does not count. When a channel
becomes enabled (PWMEx = 1), the associated PWM counter starts at the count in the PWMCNTx
register. For more detailed information on the operation of the counters, see Section 9.4.2.4, “PWM Timer
Counters”.
In concatenated mode, writes to the 16-bit counter by using a 16-bit access or writes to either the low or
high order byte of the counter will reset the 16-bit counter. Reads of the 16-bit counter must be made by
16-bit access to maintain data coherency.
NOTE
Writing to the counter while the channel is enabled can cause an irregular
PWM cycle to occur.
Module Base + 0x000C = PWMCNT0, 0x000D = PWMCNT1, 0x000E = PWMCNT2, 0x000F = PWMCNT3
Module Base + 0x0010 = PWMCNT4, 0x0011 = PWMCNT5, 0x0012 = PWMCNT6, 0x0013 = PWMCNT7
7
6
5
4
3
2
1
0
R
Bit 7
6
5
4
3
2
1
Bit 0
W
0
0
0
0
0
0
0
0
Reset
0
0
0
0
0
0
0
0
Figure 9-12. PWM Channel Counter Registers (PWMCNTx)
1
This register is available only when the corresponding channel exists and is reserved if that channel does not exist. Writes to
a reserved register have no functional effect. Reads from a reserved register return zeroes.
Read: Anytime
Write: Anytime (any value written causes PWM counter to be reset to $00).
9.3.2.11
PWM Channel Period Registers (PWMPERx)
There is a dedicated period register for each channel. The value in this register determines the period of
the associated PWM channel.
The period registers for each channel are double buffered so that if they change while the channel is
enabled, the change will NOT take effect until one of the following occurs:
• The effective period ends
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
337
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
•
•
The counter is written (counter resets to $00)
The channel is disabled
In this way, the output of the PWM will always be either the old waveform or the new waveform, not some
variation in between. If the channel is not enabled, then writes to the period register will go directly to the
latches as well as the buffer.
NOTE
Reads of this register return the most recent value written. Reads do not
necessarily return the value of the currently active period due to the double
buffering scheme.
See Section 9.4.2.3, “PWM Period and Duty” for more information.
To calculate the output period, take the selected clock source period for the channel of interest (A, B, SA,
or SB) and multiply it by the value in the period register for that channel:
• Left aligned output (CAEx = 0)
PWMx Period = Channel Clock Period * PWMPERx
• Center Aligned Output (CAEx = 1)
PWMx Period = Channel Clock Period * (2 * PWMPERx)
For boundary case programming values, please refer to Section 9.4.2.8, “PWM Boundary Cases”.
Module Base + 0x0014 = PWMPER0, 0x0015 = PWMPER1, 0x0016 = PWMPER2, 0x0017 = PWMPER3
Module Base + 0x0018 = PWMPER4, 0x0019 = PWMPER5, 0x001A = PWMPER6, 0x001B = PWMPER7
R
W
Reset
7
6
5
4
3
2
1
0
Bit 7
6
5
4
3
2
1
Bit 0
1
1
1
1
1
1
1
1
Figure 9-13. PWM Channel Period Registers (PWMPERx)
1
This register is available only when the corresponding channel exists and is reserved if that channel does not exist. Writes to
a reserved register have no functional effect. Reads from a reserved register return zeroes.
Read: Anytime
Write: Anytime
9.3.2.12
PWM Channel Duty Registers (PWMDTYx)
There is a dedicated duty register for each channel. The value in this register determines the duty of the
associated PWM channel. The duty value is compared to the counter and if it is equal to the counter value
a match occurs and the output changes state.
The duty registers for each channel are double buffered so that if they change while the channel is enabled,
the change will NOT take effect until one of the following occurs:
• The effective period ends
• The counter is written (counter resets to $00)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
338
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
•
The channel is disabled
In this way, the output of the PWM will always be either the old duty waveform or the new duty waveform,
not some variation in between. If the channel is not enabled, then writes to the duty register will go directly
to the latches as well as the buffer.
NOTE
Reads of this register return the most recent value written. Reads do not
necessarily return the value of the currently active duty due to the double
buffering scheme.
See Section 9.4.2.3, “PWM Period and Duty” for more information.
NOTE
Depending on the polarity bit, the duty registers will contain the count of
either the high time or the low time. If the polarity bit is one, the output starts
high and then goes low when the duty count is reached, so the duty registers
contain a count of the high time. If the polarity bit is zero, the output starts
low and then goes high when the duty count is reached, so the duty registers
contain a count of the low time.
To calculate the output duty cycle (high time as a% of period) for a particular channel:
• Polarity = 0 (PPOL x =0)
Duty Cycle = [(PWMPERx-PWMDTYx)/PWMPERx] * 100%
• Polarity = 1 (PPOLx = 1)
Duty Cycle = [PWMDTYx / PWMPERx] * 100%
For boundary case programming values, please refer to Section 9.4.2.8, “PWM Boundary Cases”.
Module Base + 0x001C = PWMDTY0, 0x001D = PWMDTY1, 0x001E = PWMDTY2, 0x001F = PWMDTY3
Module Base + 0x0020 = PWMDTY4, 0x0021 = PWMDTY5, 0x0022 = PWMDTY6, 0x0023 = PWMDTY7
R
W
Reset
7
6
5
4
3
2
1
0
Bit 7
6
5
4
3
2
1
Bit 0
1
1
1
1
1
1
1
1
Figure 9-14. PWM Channel Duty Registers (PWMDTYx)
1
This register is available only when the corresponding channel exists and is reserved if that channel does not exist. Writes to
a reserved register have no functional effect. Reads from a reserved register return zeroes.
Read: Anytime
Write: Anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
339
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
9.4
9.4.1
Functional Description
PWM Clock Select
There are four available clocks: clock A, clock B, clock SA (scaled A), and clock SB (scaled B). These
four clocks are based on the bus clock.
Clock A and B can be software selected to be 1, 1/2, 1/4, 1/8,..., 1/64, 1/128 times the bus clock. Clock SA
uses clock A as an input and divides it further with a reloadable counter. Similarly, clock SB uses clock B
as an input and divides it further with a reloadable counter. The rates available for clock SA are software
selectable to be clock A divided by 2, 4, 6, 8,..., or 512 in increments of divide by 2. Similar rates are
available for clock SB. Each PWM channel has the capability of selecting one of four clocks, clock A,
Clock B, clock SA or clock SB.
The block diagram in Figure 9-15 shows the four different clocks and how the scaled clocks are created.
9.4.1.1
Prescale
The input clock to the PWM prescaler is the bus clock. It can be disabled whenever the part is in freeze
mode by setting the PFRZ bit in the PWMCTL register. If this bit is set, whenever the MCU is in freeze
mode (freeze mode signal active) the input clock to the prescaler is disabled. This is useful for emulation
in order to freeze the PWM. The input clock can also be disabled when all available PWM channels are
disabled (PWMEx-0 = 0). This is useful for reducing power by disabling the prescale counter.
Clock A and clock B are scaled values of the input clock. The value is software selectable for both clock
A and clock B and has options of 1, 1/2, 1/4, 1/8, 1/16, 1/32, 1/64, or 1/128 times the bus clock. The value
selected for clock A is determined by the PCKA2, PCKA1, PCKA0 bits in the PWMPRCLK register. The
value selected for clock B is determined by the PCKB2, PCKB1, PCKB0 bits also in the PWMPRCLK
register.
9.4.1.2
Clock Scale
The scaled A clock uses clock A as an input and divides it further with a user programmable value and
then divides this by 2. The scaled B clock uses clock B as an input and divides it further with a user
programmable value and then divides this by 2. The rates available for clock SA are software selectable to
be clock A divided by 2, 4, 6, 8,..., or 512 in increments of divide by 2. Similar rates are available for clock
SB.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
340
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Clock A
PCKA2
PCKA1
PCKA0
Clock A/2, A/4, A/6,....A/512
M
U
X
Clock to
PWM Ch 0
PCLK0 PCLKAB0
Count = 1
8-Bit Down
Counter
M
U
X
Load
PWMSCLA
DIV 2
Clock SA
PCLK1 PCLKAB1
M
U
X
M
Clock to
PWM Ch 1
Clock to
PWM Ch 2
U
PCLK2 PCLKAB2
M
U
X
2 4 8 16 32 64 128
Divide by
Prescaler Taps:
X
PCLK3 PCLKAB3
Clock B
Clock B/2, B/4, B/6,....B/512
M
U
M
U
X
Clock to
PWM Ch 4
PCLK4 PCLKAB4
Count = 1
8-Bit Down
Counter
X
M
U
X
Load
PWMSCLB
DIV 2
Clock SB
PCKB2
PCKB1
PCKB0
Clock to
PWM Ch 5
PCLK5 PCLKAB5
M
U
X
Clock to
PWM Ch 6
PCLK6 PCLKAB6
PWME7-0
Bus Clock
PFRZ
Freeze Mode Signal
Clock to
PWM Ch 3
M
U
X
Clock to
PWM Ch 7
PCLK7 PCLKAB7
Prescale
Scale
Clock Select
Maximum possible channels, scalable in pairs from PWM0 to PWM7.
Figure 9-15. PWM Clock Select Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
341
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Clock A is used as an input to an 8-bit down counter. This down counter loads a user programmable scale
value from the scale register (PWMSCLA). When the down counter reaches one, a pulse is output and the
8-bit counter is re-loaded. The output signal from this circuit is further divided by two. This gives a greater
range with only a slight reduction in granularity. Clock SA equals clock A divided by two times the value
in the PWMSCLA register.
NOTE
Clock SA = Clock A / (2 * PWMSCLA)
When PWMSCLA = $00, PWMSCLA value is considered a full scale value
of 256. Clock A is thus divided by 512.
Similarly, clock B is used as an input to an 8-bit down counter followed by a divide by two producing clock
SB. Thus, clock SB equals clock B divided by two times the value in the PWMSCLB register.
NOTE
Clock SB = Clock B / (2 * PWMSCLB)
When PWMSCLB = $00, PWMSCLB value is considered a full scale value
of 256. Clock B is thus divided by 512.
As an example, consider the case in which the user writes $FF into the PWMSCLA register. Clock A for
this case will be E (bus clock) divided by 4. A pulse will occur at a rate of once every 255x4 E cycles.
Passing this through the divide by two circuit produces a clock signal at an E divided by 2040 rate.
Similarly, a value of $01 in the PWMSCLA register when clock A is E divided by 4 will produce a clock
at an E divided by 8 rate.
Writing to PWMSCLA or PWMSCLB causes the associated 8-bit down counter to be re-loaded.
Otherwise, when changing rates the counter would have to count down to $01 before counting at the proper
rate. Forcing the associated counter to re-load the scale register value every time PWMSCLA or
PWMSCLB is written prevents this.
NOTE
Writing to the scale registers while channels are operating can cause
irregularities in the PWM outputs.
9.4.1.3
Clock Select
Each PWM channel has the capability of selecting one of four clocks, clock A, clock SA, clock B or clock
SB. The clock selection is done with the PCLKx control bits in the PWMCLK register and PCLKABx
control bits in PWMCLKAB register. For backward compatibility consideration, the reset value of
PWMCLK and PWMCLKAB configures following default clock selection.
For channels 0, 1, 4, and 5 the clock choices are clock A.
For channels 2, 3, 6, and 7 the clock choices are clock B.
NOTE
Changing clock control bits while channels are operating can cause
irregularities in the PWM outputs.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
342
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
9.4.2
PWM Channel Timers
The main part of the PWM module are the actual timers. Each of the timer channels has a counter, a period
register and a duty register (each are 8-bit). The waveform output period is controlled by a match between
the period register and the value in the counter. The duty is controlled by a match between the duty register
and the counter value and causes the state of the output to change during the period. The starting polarity
of the output is also selectable on a per channel basis. Shown below in Figure 9-16 is the block diagram
for the PWM timer.
Clock Source
From Port PWMP
Data Register
8-Bit Counter
Gate
PWMCNTx
(Clock Edge
Sync)
Up/Down
Reset
8-bit Compare =
T
M
U
X
Q
PWMDTYx
Q
R
M
U
X
To Pin
Driver
8-bit Compare =
PWMPERx
PPOLx
Q
T
CAEx
Q
R
PWMEx
Figure 9-16. PWM Timer Channel Block Diagram
9.4.2.1
PWM Enable
Each PWM channel has an enable bit (PWMEx) to start its waveform output. When any of the PWMEx
bits are set (PWMEx = 1), the associated PWM output signal is enabled immediately. However, the actual
PWM waveform is not available on the associated PWM output until its clock source begins its next cycle
due to the synchronization of PWMEx and the clock source. An exception to this is when channels are
concatenated. Refer to Section 9.4.2.7, “PWM 16-Bit Functions” for more detail.
NOTE
The first PWM cycle after enabling the channel can be irregular.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
343
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
On the front end of the PWM timer, the clock is enabled to the PWM circuit by the PWMEx bit being high.
There is an edge-synchronizing circuit to guarantee that the clock will only be enabled or disabled at an
edge. When the channel is disabled (PWMEx = 0), the counter for the channel does not count.
9.4.2.2
PWM Polarity
Each channel has a polarity bit to allow starting a waveform cycle with a high or low signal. This is shown
on the block diagram Figure 9-16 as a mux select of either the Q output or the Q output of the PWM output
flip flop. When one of the bits in the PWMPOL register is set, the associated PWM channel output is high
at the beginning of the waveform, then goes low when the duty count is reached. Conversely, if the polarity
bit is zero, the output starts low and then goes high when the duty count is reached.
9.4.2.3
PWM Period and Duty
Dedicated period and duty registers exist for each channel and are double buffered so that if they change
while the channel is enabled, the change will NOT take effect until one of the following occurs:
• The effective period ends
• The counter is written (counter resets to $00)
• The channel is disabled
In this way, the output of the PWM will always be either the old waveform or the new waveform, not some
variation in between. If the channel is not enabled, then writes to the period and duty registers will go
directly to the latches as well as the buffer.
A change in duty or period can be forced into effect “immediately” by writing the new value to the duty
and/or period registers and then writing to the counter. This forces the counter to reset and the new duty
and/or period values to be latched. In addition, since the counter is readable, it is possible to know where
the count is with respect to the duty value and software can be used to make adjustments
NOTE
When forcing a new period or duty into effect immediately, an irregular
PWM cycle can occur.
Depending on the polarity bit, the duty registers will contain the count of
either the high time or the low time.
9.4.2.4
PWM Timer Counters
Each channel has a dedicated 8-bit up/down counter which runs at the rate of the selected clock source (see
Section 9.4.1, “PWM Clock Select” for the available clock sources and rates). The counter compares to
two registers, a duty register and a period register as shown in Figure 9-16. When the PWM counter
matches the duty register, the output flip-flop changes state, causing the PWM waveform to also change
state. A match between the PWM counter and the period register behaves differently depending on what
output mode is selected as shown in Figure 9-16 and described in Section 9.4.2.5, “Left Aligned Outputs”
and Section 9.4.2.6, “Center Aligned Outputs”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
344
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Each channel counter can be read at anytime without affecting the count or the operation of the PWM
channel.
Any value written to the counter causes the counter to reset to $00, the counter direction to be set to up,
the immediate load of both duty and period registers with values from the buffers, and the output to change
according to the polarity bit. When the channel is disabled (PWMEx = 0), the counter stops. When a
channel becomes enabled (PWMEx = 1), the associated PWM counter continues from the count in the
PWMCNTx register. This allows the waveform to continue where it left off when the channel is reenabled. When the channel is disabled, writing “0” to the period register will cause the counter to reset on
the next selected clock.
NOTE
If the user wants to start a new “clean” PWM waveform without any
“history” from the old waveform, the user must write to channel counter
(PWMCNTx) prior to enabling the PWM channel (PWMEx = 1).
Generally, writes to the counter are done prior to enabling a channel in order to start from a known state.
However, writing a counter can also be done while the PWM channel is enabled (counting). The effect is
similar to writing the counter when the channel is disabled, except that the new period is started
immediately with the output set according to the polarity bit.
NOTE
Writing to the counter while the channel is enabled can cause an irregular
PWM cycle to occur.
The counter is cleared at the end of the effective period (see Section 9.4.2.5, “Left Aligned Outputs” and
Section 9.4.2.6, “Center Aligned Outputs” for more details).
Table 9-12. PWM Timer Counter Conditions
Counter Clears ($00)
Counter Counts
Counter Stops
When PWMCNTx register written to
any value
When PWM channel is enabled
(PWMEx = 1). Counts from last value in
PWMCNTx.
When PWM channel is disabled
(PWMEx = 0)
Effective period ends
9.4.2.5
Left Aligned Outputs
The PWM timer provides the choice of two types of outputs, left aligned or center aligned. They are
selected with the CAEx bits in the PWMCAE register. If the CAEx bit is cleared (CAEx = 0), the
corresponding PWM output will be left aligned.
In left aligned output mode, the 8-bit counter is configured as an up counter only. It compares to two
registers, a duty register and a period register as shown in the block diagram in Figure 9-16. When the
PWM counter matches the duty register the output flip-flop changes state causing the PWM waveform to
also change state. A match between the PWM counter and the period register resets the counter and the
output flip-flop, as shown in Figure 9-16, as well as performing a load from the double buffer period and
duty register to the associated registers, as described in Section 9.4.2.3, “PWM Period and Duty”. The
counter counts from 0 to the value in the period register – 1.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
345
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
NOTE
Changing the PWM output mode from left aligned to center aligned output
(or vice versa) while channels are operating can cause irregularities in the
PWM output. It is recommended to program the output mode before
enabling the PWM channel.
PPOLx = 0
PPOLx = 1
PWMDTYx
Period = PWMPERx
Figure 9-17. PWM Left Aligned Output Waveform
To calculate the output frequency in left aligned output mode for a particular channel, take the selected
clock source frequency for the channel (A, B, SA, or SB) and divide it by the value in the period register
for that channel.
• PWMx Frequency = Clock (A, B, SA, or SB) / PWMPERx
• PWMx Duty Cycle (high time as a% of period):
— Polarity = 0 (PPOLx = 0)
Duty Cycle = [(PWMPERx-PWMDTYx)/PWMPERx] * 100%
— Polarity = 1 (PPOLx = 1)
Duty Cycle = [PWMDTYx / PWMPERx] * 100%
As an example of a left aligned output, consider the following case:
Clock Source = E, where E = 10 MHz (100 ns period)
PPOLx = 0
PWMPERx = 4
PWMDTYx = 1
PWMx Frequency = 10 MHz/4 = 2.5 MHz
PWMx Period = 400 ns
PWMx Duty Cycle = 3/4 *100% = 75%
The output waveform generated is shown in Figure 9-18.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
346
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
E = 100 ns
Duty Cycle = 75%
Period = 400 ns
Figure 9-18. PWM Left Aligned Output Example Waveform
9.4.2.6
Center Aligned Outputs
For center aligned output mode selection, set the CAEx bit (CAEx = 1) in the PWMCAE register and the
corresponding PWM output will be center aligned.
The 8-bit counter operates as an up/down counter in this mode and is set to up whenever the counter is
equal to $00. The counter compares to two registers, a duty register and a period register as shown in the
block diagram in Figure 9-16. When the PWM counter matches the duty register, the output flip-flop
changes state, causing the PWM waveform to also change state. A match between the PWM counter and
the period register changes the counter direction from an up-count to a down-count. When the PWM
counter decrements and matches the duty register again, the output flip-flop changes state causing the
PWM output to also change state. When the PWM counter decrements and reaches zero, the counter
direction changes from a down-count back to an up-count and a load from the double buffer period and
duty registers to the associated registers is performed, as described in Section 9.4.2.3, “PWM Period and
Duty”. The counter counts from 0 up to the value in the period register and then back down to 0. Thus the
effective period is PWMPERx*2.
NOTE
Changing the PWM output mode from left aligned to center aligned output
(or vice versa) while channels are operating can cause irregularities in the
PWM output. It is recommended to program the output mode before
enabling the PWM channel.
PPOLx = 0
PPOLx = 1
PWMDTYx
PWMDTYx
PWMPERx
PWMPERx
Period = PWMPERx*2
Figure 9-19. PWM Center Aligned Output Waveform
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
347
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
To calculate the output frequency in center aligned output mode for a particular channel, take the selected
clock source frequency for the channel (A, B, SA, or SB) and divide it by twice the value in the period
register for that channel.
• PWMx Frequency = Clock (A, B, SA, or SB) / (2*PWMPERx)
• PWMx Duty Cycle (high time as a% of period):
— Polarity = 0 (PPOLx = 0)
Duty Cycle = [(PWMPERx-PWMDTYx)/PWMPERx] * 100%
— Polarity = 1 (PPOLx = 1)
Duty Cycle = [PWMDTYx / PWMPERx] * 100%
As an example of a center aligned output, consider the following case:
Clock Source = E, where E = 10 MHz (100 ns period)
PPOLx = 0
PWMPERx = 4
PWMDTYx = 1
PWMx Frequency = 10 MHz/8 = 1.25 MHz
PWMx Period = 800 ns
PWMx Duty Cycle = 3/4 *100% = 75%
Shown in Figure 9-20 is the output waveform generated.
E = 100 ns
E = 100 ns
DUTY CYCLE = 75%
PERIOD = 800 ns
Figure 9-20. PWM Center Aligned Output Example Waveform
9.4.2.7
PWM 16-Bit Functions
The scalable PWM timer also has the option of generating up to 8-channels of 8-bits or 4-channels of 16bits for greater PWM resolution. This 16-bit channel option is achieved through the concatenation of two
8-bit channels.
The PWMCTL register contains four control bits, each of which is used to concatenate a pair of PWM
channels into one 16-bit channel. Channels 6 and 7 are concatenated with the CON67 bit, channels 4 and
5 are concatenated with the CON45 bit, channels 2 and 3 are concatenated with the CON23 bit, and
channels 0 and 1 are concatenated with the CON01 bit.
NOTE
Change these bits only when both corresponding channels are disabled.
When channels 6 and 7 are concatenated, channel 6 registers become the high order bytes of the double
byte channel, as shown in Figure 9-21. Similarly, when channels 4 and 5 are concatenated, channel 4
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
348
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
registers become the high order bytes of the double byte channel. When channels 2 and 3 are concatenated,
channel 2 registers become the high order bytes of the double byte channel. When channels 0 and 1 are
concatenated, channel 0 registers become the high order bytes of the double byte channel.
When using the 16-bit concatenated mode, the clock source is determined by the low order 8-bit channel
clock select control bits. That is channel 7 when channels 6 and 7 are concatenated, channel 5 when
channels 4 and 5 are concatenated, channel 3 when channels 2 and 3 are concatenated, and channel 1 when
channels 0 and 1 are concatenated. The resulting PWM is output to the pins of the corresponding low order
8-bit channel as also shown in Figure 9-21. The polarity of the resulting PWM output is controlled by the
PPOLx bit of the corresponding low order 8-bit channel as well.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
349
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
Clock Source 7
High
Low
PWMCNT6
PWMCNT7
Period/Duty Compare
PWM7
Clock Source 5
High
Low
PWMCNT4
PWMCNT5
Period/Duty Compare
PWM5
Clock Source 3
High
Low
PWMCNT2
PWMCNT3
Period/Duty Compare
PWM3
Clock Source 1
High
Low
PWMCNT0
PWMCNT1
Period/Duty Compare
PWM1
Maximum possible 16-bit channels
Figure 9-21. PWM 16-Bit Mode
Once concatenated mode is enabled (CONxx bits set in PWMCTL register), enabling/disabling the
corresponding 16-bit PWM channel is controlled by the low order PWMEx bit. In this case, the high order
bytes PWMEx bits have no effect and their corresponding PWM output is disabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
350
Freescale Semiconductor
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
In concatenated mode, writes to the 16-bit counter by using a 16-bit access or writes to either the low or
high order byte of the counter will reset the 16-bit counter. Reads of the 16-bit counter must be made by
16-bit access to maintain data coherency.
Either left aligned or center aligned output mode can be used in concatenated mode and is controlled by
the low order CAEx bit. The high order CAEx bit has no effect.
Table 9-13 is used to summarize which channels are used to set the various control bits when in 16-bit
mode.
Table 9-13. 16-bit Concatenation Mode Summary
Note: Bits related to available channels have functional significance.
9.4.2.8
CONxx
PWMEx
PPOLx
PCLKx
CAEx
PWMx
Output
CON67
PWME7
PPOL7
PCLK7
CAE7
PWM7
CON45
PWME5
PPOL5
PCLK5
CAE5
PWM5
CON23
PWME3
PPOL3
PCLK3
CAE3
PWM3
CON01
PWME1
PPOL1
PCLK1
CAE1
PWM1
PWM Boundary Cases
Table 9-14 summarizes the boundary conditions for the PWM regardless of the output mode (left aligned
or center aligned) and 8-bit (normal) or 16-bit (concatenation).
Table 9-14. PWM Boundary Cases
9.5
PWMDTYx
PWMPERx
PPOLx
PWMx Output
$00
(indicates no duty)
>$00
1
Always low
$00
(indicates no duty)
>$00
0
Always high
XX
$00(1)
(indicates no period)
1
Always high
XX
$001
(indicates no period)
0
Always low
>= PWMPERx
XX
1
Always high
>= PWMPERx
XX
1. Counter = $00 and does not count.
0
Always low
Resets
The reset state of each individual bit is listed within the Section 9.3.2, “Register Descriptions” which
details the registers and their bit-fields. All special functions or modes which are initialized during or just
following reset are described within this section.
• The 8-bit up/down counter is configured as an up counter out of reset.
• All the channels are disabled and all the counters do not count.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
351
Chapter 9 Pulse-Width Modulator (S12PWM8B8CV2)
•
•
9.6
For channels 0, 1, 4, and 5 the clock choices are clock A.
For channels 2, 3, 6, and 7 the clock choices are clock B.
Interrupts
The PWM module has no interrupt.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
352
Freescale Semiconductor
Chapter 10
Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-1. Revision History
Revision
Number
Revision
Date
V1.35
06. Nov 2012
10.4.2.9/10-376
Modified bit description of flag LDOK_EIF for better understanding.
V1.36
08 Nov 2012
10.4.2.13/10-381
Updated description of bits RIDX_IMD for better understanding.
V1.37
19. Apr 2013
-
Sections Affected
Description of Changes
Updates from review of reference manual to fix typos etc.
V1.38
30. Apr 2013
10.4.2.13/10-381
Provided more detailed information regarding captured information in
bits RIDX_IMD[5:0] for different scenarios of Sequence Abort Event
execution.
V1.39
02. Jul 2013
10.4.2.6/10-370
Update of: Timing considerations for Restart Mode
V1.40
02. Oct 2013
entire document
Updated formatting and wording correction for entire document (for
technical publications).
10.1
Introduction
The ADC12B_LBA is an n-channel multiplexed input successive approximation analog-to-digital
converter. Refer to device electrical specifications for ADC parameters and accuracy.
The List Based Architecture (LBA) provides flexible conversion sequence definition as well as flexible
oversampling. The order of channels to be converted can be freely defined. Also, multiple instantiations of
the module can be triggered simultaneously (matching sampling point across multiple module
instantiations).
There are four register bits which control the conversion flow (please refer to the description of register
ADCFLWCTL).
The four conversion flow control bits of register ADCFLWCTL can be modified in two different ways:
• Via data bus accesses
• Via internal interface Signals (Trigger, Restart, LoadOK, and Seq_Abort; see also Figure 10-2).
Each Interface Signal is associated with one conversion flow control bit.
For information regarding internal interface connectivity related to the conversion flow control please refer
to the device overview of the reference manual.
The ADCFLWCTL register can be controlled via internal interface only or via data bus only or by both
depending on the register access configuration bits ACC_CFG[1:0].
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
353
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
The four bits of register ADCFLWCTL reflect the captured request and status of the four internal interface
Signals (LoadOK, Trigger, Restart, and Seq_abort; see also Figure 10-2) if access configuration is set
accordingly and indicate event progress (when an event is processed and when it is finished).
Conversion flow error situations are captured by corresponding interrupt flags in the ADCEIF register.
There are two conversion flow control modes (Restart Mode, Trigger Mode). Each mode causes a certain
behavior of the conversion flow control bits which can be selected according to the application needs.
Please refer to Section 10.4.2.1, “ADC Control Register 0 (ADCCTL_0) and Section 10.5.3.2.4, “The two
conversion flow control Mode Configurations for more information regarding conversion flow control.
Because internal components of the ADC are turned on/off with bit ADC_EN, the ADC requires a
recovery time period (tREC) after ADC is enabled until the first conversion can be launched via a trigger.
When bit ADC_EN gets cleared (transition from 1’b1 to 1’b0) any ongoing conversion sequence will be
aborted and pending results, or the result of current conversion, gets discarded (not stored). The ADC
cannot be re-enabled before any pending action or action in process is finished respectively aborted, which
could take up to a maximum latency time of tDISABLE (see device reference manual for more details).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
354
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Key Features
Programmer’s Model with List Based Architecture for conversion command and result value
organization
Selectable resolution of 8-bit, 10-bit, or 12-bit
Channel select control for n external analog input channels
Provides up to eight device internal channels (please see the device reference manual for
connectivity information and Figure 10-2)
Programmable sample time
A sample buffer amplifier for channel sampling (improved performance in view to influence of
channel input path resistance versus conversion accuracy)
Left/right justified result data
Individual selectable VRH_0/1 and VRL_0/1 inputs on a conversion command basis (please see
Figure 10-2)
Special conversions for selected VRH_0/1, VRL_0/1, (VRL_0/1 + VRH_0/1) / 2
15 conversion interrupts with flexible interrupt organization per conversion result
One dedicated interrupt for “End Of List” type commands
Command Sequence List (CSL) with a maximum number of 64 command entries
Provides conversion sequence abort
Restart from top of active Command Sequence List (CSL)
The Command Sequence List and Result Value List are implemented in double buffered manner
(two lists in parallel for each function)
Conversion Command (CSL) loading possible from System RAM or NVM
Single conversion flow control register with software selectable access path
Two conversion flow control modes optimized to different application use cases
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
355
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.2.1
10.2.1.1
Modes of Operation
Conversion Modes
This architecture provides single, multiple, or continuous conversion on a single channel or on multiple
channels based on the Command Sequence List.
10.2.1.2
•
MCU Operating Modes
MCU Stop Mode
Before issuing an MCU Stop Mode request the ADC should be idle (no conversion or conversion
sequence or Command Sequence List ongoing).
If a conversion, conversion sequence, or CSL is in progress when an MCU Stop Mode request is
issued, a Sequence Abort Event occurs automatically and any ongoing conversion finish. After the
Sequence Abort Event finishes, if the STR_SEQA bit is set (STR_SEQA=1), then the conversion
result is stored and the corresponding flags are set. If the STR_SEQA bit is cleared
(STR_SEQA=0), then the conversion result is not stored and the corresponding flags are not set.
The microcontroller then enters MCU Stop Mode without SEQAD_IF being set.
Alternatively, the Sequence Abort Event can be issued by software before an MCU Stop Mode
request. As soon as flag SEQAD_IF is set the MCU Stop Mode request can be is issued.
With the occurrence of the MCU Stop Mode Request until exit from Stop Mode all flow control
signals (RSTA, SEQA, LDOK, TRIG) are cleared.
After exiting MCU Stop Mode, the following happens in the order given with expected event(s)
depending on the conversion flow control mode:
— In ADC conversion flow control mode “Trigger Mode” a Restart Event is expected to
simultaneously set bits TRIG and RSTA, causing the ADC to execute the Restart Event
(CMD_IDX and RVL_IDX cleared) followed by the Trigger Event. The Restart Event can be
generated automatically after exit from MCU Stop Mode if bit AUT_RSTA is set.
— In ADC conversion flow control mode “Restart Mode”, a Restart Event is expected to set bit
RSTA only (ADC already aborted at MCU Stop Mode entry hence bit SEQA must not be set
simultaneously) causing the ADC to execute the Restart Event (CDM_IDX and RVL_IDX
cleared). The Restart Event can be generated automatically after exit from MCU Stop Mode if
bit AUT_RSTA is set.
— The RVL buffer select (RVL_SEL) is not changed if a CSL is in process at MCU Stop Mode
request. Hence the same buffer will be used after exit from Stop Mode that was used when the
Stop Mode request occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
356
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
•
MCU Wait Mode
Depending on the ADC Wait Mode configuration bit SWAI, the ADC either continues conversion
in MCU Wait Mode or freezes conversion at the next conversion boundary before MCU Wait Mode
is entered.
ADC behavior for configuration SWAI =1’b0:
The ADC continues conversion during Wait Mode according to the conversion flow control
sequence. It is assumed that the conversion flow control sequence is continued (conversion flow
control bits TRIG, RSTA, SEQA, and LDOK are serviced accordingly).
ADC behavior for configuration SWAI = 1’b1:
At MCU Wait Mode request the ADC should be idle (no conversion or conversion sequence or
Command Sequence List ongoing).
If a conversion, conversion sequence, or CSL is in progress when an MCU Wait Mode request is
issued, a Sequence Abort Event occurs automatically and any ongoing conversion finish. After the
Sequence Abort Event finishes, if the STR_SEQA bit is set (STR_SEQA=1), then the conversion
result is stored and the corresponding flags are set. If the STR_SEQA bit is cleared
(STR_SEQA=0), then the conversion result is not stored and the corresponding flags are not set.
Alternatively the Sequence Abort Event can be issued by software before MCU Wait Mode request.
As soon as flag SEQAD_IF is set, the MCU Wait Mode request can be issued.
With the occurrence of the MCU Wait Mode request until exit from Wait Mode all flow control
signals (RSTA, SEQA, LDOK, TRIG) are cleared.
After exiting MCU Wait Mode, the following happens in the order given with expected event(s)
depending on the conversion flow control mode:
— In ADC conversion flow control mode “Trigger Mode”, a Restart Event is expected to occur.
This simultaneously sets bit TRIG and RSTA causing the ADC to execute the Restart Event
(CMD_IDX and RVL_IDX cleared) followed by the Trigger Event. The Restart Event can be
generated automatically after exit from MCU Wait Mode if bit AUT_RSTA is set.
— In ADC conversion flow control mode “Restart Mode”, a Restart Event is expected to set bit
RSTA only (ADC already aborted at MCU Wait Mode entry hence bit SEQA must not be set
simultaneously) causing the ADC to execute the Restart Event (CDM_IDX and RVL_IDX
cleared). The Restart Event can be generated automatically after exit from MCU Wait Mode if
bit AUT_RSTA is set.
— The RVL buffer select (RVL_SEL) is not changed if a CSL is in process at MCU Wait Mode
request. Hence the same RVL buffer will be used after exit from Wait Mode that was used when
Wait Mode request occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
357
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
NOTE
In principle, the MCU could stay in Wait Mode for a shorter period of time
than the ADC needs to abort an ongoing conversion (range of µs). Therefore
in case a Sequence Abort Event is issued automatically due to MCU Wait
Mode request a following Restart Event after exit from MCU Wait Mode
can not be executed before ADC has finished this Sequence Abort Event.
The Restart Event is detected but it is pending.
This applies in case MCU Wait Mode is exited before ADC has finished the
Sequence Abort Event and a Restart Event is issued immediately after exit
from MCU Wait Mode. Bit READY can be used by software to detect when
the Restart Event can be issued without latency time in processing the event
(see also Figure 10-1).
Wait Mode request (SWAI=1’b1),
Automatic Sequence Abort
Event Wake-up
Event
AN3 AN1 AN4 IN5 AN6 AN1
Sequence_0
Wait Mode
entry
Abort
Active
Restart
Event
Trigger
AN3 AN1 AN4 AN5 AN2 AN0
Sequence_n
CSL_0
Begin from top of current CSL
Sequence_1
EOS
READY=1’b1
Earliest point of time to issue
Restart Event without latency
Idle
Active
t
Figure 10-1. Conversion Flow Control Diagram - Wait Mode (SWAI=1’b1, AUT_RSTA=1’b0)
•
MCU Freeze Mode
Depending on the ADC Freeze Mode configuration bit FRZ_MOD, the ADC either continues
conversion in Freeze Mode or freezes conversion at next conversion boundary before the MCU
Freeze Mode is entered. After exit from MCU Freeze Mode with previously frozen conversion
sequence the ADC continues the conversion with the next conversion command and all ADC
interrupt flags are unchanged during MCU Freeze Mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
358
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.2.2
Block Diagram
System Clock
Clock
Prescaler
ADC Clock
Error/
FlowCtrl Issue
Int.
Error
handler
(EN)
Data Bus
LoadOK
Sequence Abort Int.
Trigger
Control Unit
Restart
Conversion Int.
(Conversion Flow, Timing, Interrupt)
Seq_abort
see reference
manual for
connectivity
information
regarding ADC
internal interface
Internal_7
Internal_6
Internal_5
Internal_4
Internal_3
Internal_2
DMA access
ADC
Temperature
Sense
Comm_0
Comm_1
..........
Idle/
..........
Active
...........
.......... Command
........... Sequence AlternativeList
...........
Command
(RAM/
...........
Sequence
NVM)
...........
List
...........
(RAM/
Comm 63
NVM)
int.
Channel
MUX
VREG_sense
DMA access
VRH_1
VRH_0
Result_0
Result_1
..........
active
.......... Conversion
........... Result List
..........
(RAM)
...........
...........
Alternative
...........
Result
...........
List
...........
(RAM)
Result 63
Successive
Approximation
Register (SAR)
and C-DAC
VRL_1
VRL_0
VDDA
VSSA
Final
+
Buffer
-
ANx
.....
AN2
AN1
ext.
Channel
MUX
AN0
+
-
Buffer
AMP
Comparator
Sample & Hold
PIM
ADC12B_LBA
Figure 10-2. ADC12B_LBA Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
359
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.3
Signal Description
This section lists all inputs to the ADC12B_LBA block.
10.3.1
10.3.1.1
Detailed Signal Descriptions
ANx (x = n,..., 2, 1, 0)
This pin serves as the analog input Channel x. The maximum input channel number is n. Please refer to
the device reference manual for the maximum number of input channels.
10.3.1.2
VRH_0, VRH_1, VRL_0, VRL_1
VRH_0/1 are the high reference voltages, VRL0/1 are the low reference voltages for a ADC conversion
selectable on a conversion command basis. Please refer to the device reference manual for availability and
connectivity of these pins.
10.3.1.3
VDDA, VSSA
These pins are the power supplies for the analog circuitry of the ADC12B_LBA block.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
360
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4
Memory Map and Register Definition
This section provides a detailed description of all registers accessible in the ADC12B_LBA.
10.4.1
Module Memory Map
Figure 10-3 gives an overview of all ADC12B_LBA registers.
NOTE
Register Address = Base Address + Address Offset, where the Base Address
is defined at the MCU level and the Address Offset is defined at the module
level.
Address
Name
0x0000
ADCCTL_0
0x0001
ADCCTL_1
0x0002
ADCSTS
0x0003
ADCTIM
0x0004
ADCFMT
0x0005
ADCFLWCTL
0x0006
ADCEIE
0x0007
ADCIE
0x0008
ADCEiF
0x0009
ADCIF
0x000A ADCCONIE_0
0x000B ADCCONIE_1
0x000C ADCCONIF_0
0x000D ADCCONIF_1
0x000E
ADCIMDRI_0
0x000F
ADCIMDRI_1
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
R
W
Bit 7
6
5
4
ADC_EN
ADC_SR
FRZ_MOD
SWAI
SMOD_ACC
AUT_RSTA
CSL_BMOD RVL_BMOD
CSL_SEL
RVL_SEL
DBECC_ERR Reserved
0
3
2
ACC_CFG[1:0]
1
Bit 0
STR_SEQA
MOD_CFG
0
0
0
0
READY
0
0
0
PRS[6:0]
0
0
0
SEQA
TRIG
RSTA
LDOK
IA_EIE
CMD_EIE
EOL_EIE
DJM
SEQAD_IE CONIF_OIE
IA_EIF
CMD_EIF
SEQAD_IF CONIF_OIF
Reserved
EOL_EIF
Reserved
0
0
Reserved TRIG_EIE
0
0
0
RSTAR_EIE
LDOK_EIE
0
0
RSTAR_EIF
LDOK_EIF
0
0
0
Reserved TRIG_EIF
0
SRES[2:0]
0
0
0
0
0
0
CON_IE[15:8]
CON_IE[7:1]
EOL_IE
CON_IF[15:8]
CON_IF[7:1]
CSL_IMD
RVL_IMD
0
0
0
0
EOL_IF
0
0
0
0
RIDX_IMD[5:0]
= Unimplemented or Reserved
Figure 10-3. ADC12B_LBA Register Summary (Sheet 1 of 3)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
361
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Address
Name
0x0010
ADCEOLRI
0x0011
Reserved
0x0012
Reserved
0x0013
Reserved
0x0014
ADCCMD_0
0x0015
ADCCMD_1
0x0016
ADCCMD_2
0x0017
ADCCMD_3
0x0018
Reserved
0x0019
Reserved
0x001A
Reserved
0x001B
Reserved
0x001C
ADCCIDX
0x001D
ADCCBP_0
0x001E
ADCCBP_1
0x001F
ADCCBP_2
0x0020
ADCRIDX
0x0021
ADCRBP_0
0x0022
ADCRBP_1
0x0023
ADCRBP_2
0x0024
ADCCROFF0
0x0025
ADCCROFF1
0x0026
Reserved
Bit 7
6
R CSL_EOL RVL_EOL
W
R
0
0
W
R
0
0
W
R Reserved
W
R
CMD_SEL
W
R
VRH_SEL VRL_SEL
W
R
W
R
Reserved Reserved
W
R
W
R
W
R
W
R
W
R
0
0
W
R
W
R
W
R
W
R
0
0
W
R
0
0
W
R
W
R
W
R
0
W
R
0
W
R
0
0
W
5
0
4
0
3
0
2
0
1
0
Bit 0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Reserved
0
0
INTFLG_SEL[3:0]
CH_SEL[5:0]
0
SMP[4:0]
0
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
CMD_IDX[5:0]
CMD_PTR[23:16]
CMD_PTR[15:8]
0
CMD_PTR[7:2]
0
RES_IDX[5:0]
0
0
RES_PTR[19:16]
RES_PTR[15:8]
0
RES_PTR[7:2]
0
CMDRES_OFF0[6:0]
CMDRES_OFF1[6:0]
0
0
Reserved
= Unimplemented or Reserved
Figure 10-3. ADC12B_LBA Register Summary (Sheet 2 of 3)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
362
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Address
Name
0x0027
Reserved
0x0028
Reserved
0x0029
Reserved
0x002A0x003F
Reserved
Bit 7
R
W
R
W
R Reserved
W
R
0
W
6
5
4
3
2
1
Bit 0
0
0
0
0
Reserved
Reserved
0
0
Reserved
0
0
0
0
= Unimplemented or Reserved
Figure 10-3. ADC12B_LBA Register Summary (Sheet 3 of 3)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
363
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2
Register Descriptions
This section describes in address order all the ADC12B_LBA registers and their individual bits.
10.4.2.1
ADC Control Register 0 (ADCCTL_0)
Module Base + 0x0000
R
W
Reset
15
14
13
12
ADC_EN
ADC_SR
FRZ_MOD
SWAI
0
0
0
0
11
10
ACC_CFG[1:0]
0
9
8
STR_SEQA
MOD_CFG
0
0
0
= Unimplemented or Reserved
Figure 10-4. ADC Control Register 0 (ADCCTL_0)
Read: Anytime
Write:
• Bits ADC_EN, ADC_SR, FRZ_MOD and SWAI writable anytime
• Bits MOD_CFG, STR_SEQA and ACC_CFG[1:0] writable if bit ADC_EN clear or bit
SMOD_ACC set
Table 10-2. ADCCTL_0 Field Descriptions
Field
Description
15
ADC_EN
ADC Enable Bit — This bit enables the ADC (e.g. sample buffer amplifier etc.) and controls accessibility of ADC
register bits. When this bit gets cleared any ongoing conversion sequence will be aborted and pending results
or the result of current conversion gets discarded (not stored). The ADC cannot be re-enabled before any
pending action or action in process is finished or aborted, which could take up to a maximum latency time of
tDISABLE (see device reference manual for more details).
Because internal components of the ADC are turned on/off with this bit, the ADC requires a recovery time period
(tREC) after ADC is enabled until the first conversion can be launched via a trigger.
0 ADC disabled.
1 ADC enabled.
14
ADC_SR
ADC Soft-Reset — This bit causes an ADC Soft-Reset if set after a severe error occurred (see list of severe
errors in Section 10.4.2.9, “ADC Error Interrupt Flag Register (ADCEIF) that causes the ADC to cease
operation). It clears all overrun flags and error flags and forces the ADC state machine to its idle state. It also
clears the Command Index Register, the Result Index Register, and the CSL_SEL and RVL_SEL bits (to be
ready for a new control sequence to load new command and start execution again from top of selected CSL).
A severe error occurs if an error flag is set which cause the ADC to cease operation.
In order to make the ADC operational again an ADC Soft-Reset must be issued.
Once this bit is set it can not be cleared by writing any value. It is cleared only by ADC hardware after the SoftReset has been executed.
0 No ADC Soft-Reset issued.
1 Issue ADC Soft-Reset.
13
FRZ_MOD
12
SWAI
Freeze Mode Configuration — This bit influences conversion flow during Freeze Mode.
0 ADC continues conversion in Freeze Mode.
1 ADC freezes the conversion at next conversion boundary at Freeze Mode entry.
Wait Mode Configuration — This bit influences conversion flow during Wait Mode.
0 ADC continues conversion in Wait Mode.
1 ADC halts the conversion at next conversion boundary at Wait Mode entry.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
364
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-2. ADCCTL_0 Field Descriptions (continued)
Field
Description
11-10
ADCFLWCTL Register Access Configuration — These bits define if the register ADCFLWCTL is controlled
ACC_CFG[1:0] via internal interface only or data bus only or both. See Table 10-3. for more details.
9
Control Of Conversion Result Storage and RSTAR_EIF flag setting at Sequence Abort or Restart Event
STR_SEQA — This bit controls conversion result storage and RSTAR_EIF flag setting when a Sequence Abort Event or
Restart Event occurs as follows:
If STR_SEQA = 1’b0 and if a:
• Sequence Abort Event or Restart Event is issued during a conversion the data of this conversion is not stored
and the respective conversion complete flag is not set
• Restart Event only is issued before the last conversion of a CSL is finished and no Sequence Abort Event is
in process (SEQA clear) causes the RSTA_EIF error flag to be asserted and bit SEQA gets set by hardware
If STR_SEQA = 1’b1 and if a:
• Sequence Abort Event or Restart Event is issued during a conversion the data of this conversion is stored and
the respective conversion complete flag is set and Intermediate Result Information Register is updated.
• Restart Event only occurs during the last conversion of a CSL and no Sequence Abort Event is in process
(SEQA clear) does not set the RSTA_EIF error flag
• Restart Event only is issued before the CSL is finished and no Sequence Abort Event is in process (SEQA
clear) causes the RSTA_EIF error flag to be asserted and bit SEQA gets set by hardware
8
MOD_CFG
(Conversion Flow Control) Mode Configuration — This bit defines the conversion flow control after a Restart
Event and after execution of the “End Of List” command type:
- Restart Mode
- Trigger Mode
(For more details please see also section Section 10.5.3.2, “Introduction of the Programmer’s Model and
following.)
0 “Restart Mode” selected.
1 “Trigger Mode” selected.
Table 10-3. ADCFLWCTL Register Access Configurations
ACC_CFG[1]
ACC_CFG[0]
0
0
ADCFLWCTL Access Mode
None of the access paths is enabled
(default / reset configuration)
0
1
Single Access Mode - Internal Interface
(ADCFLWCTL access via internal interface only)
1
0
Single Access Mode - Data Bus
(ADCFLWCTL access via data bus only)
1
1
Dual Access Mode
(ADCFLWCTL register access via internal interface and data bus)
NOTE
Each conversion flow control bit (SEQA, RSTA, TRIG, LDOK) must be
controlled by software or internal interface according to the requirements
described in Section 10.5.3.2.4, “The two conversion flow control Mode
Configurations and overview summary in Table 10-10.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
365
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.2
ADC Control Register 1 (ADCCTL_1)
Module Base + 0x0001
7
R
W
6
5
CSL_BMOD RVL_BMOD SMOD_ACC
Reset
0
0
4
AUT_RSTA
0
0
3
2
1
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-5. ADC Control Register 1 (ADCCTL_1)
Read: Anytime
Write:
• Bit CSL_BMOD and RVL_BMOD writable if bit ADC_EN clear or bit SMOD_ACC set
• Bit SMOD_ACC only writable in MCU Special Mode
• Bit AUT_RSTA writable anytime
Table 10-4. ADCCTL_1 Field Descriptions
Field
Description
7
CSL Buffer Mode Select Bit — This bit defines the CSL buffer mode. This bit is only writable if ADC_EN is clear.
CSL_BMOD 0 CSL single buffer mode.
1 CSL double buffer mode.
6
RVL Buffer Mode Select Bit — This bit defines the RVL buffer mode.
RVL_BMOD 0 RVL single buffer mode
1 RVL double buffer mode
5
Special Mode Access Control Bit — This bit controls register access rights in MCU Special Mode. This bit is
SMOD_ACC automatically cleared when leaving MCU Special Mode.
Note: When this bit is set also the ADCCMD register is writeable via the data bus to allow modification of the
current command for debugging purpose. But this is only possible if the current command is not already
processed (conversion not started).
Please see access details given for each register.
Care must be taken when modifying ADC registers while bit SMOD_ACC is set to not corrupt a possible ongoing
conversion.
0 Normal user access - Register write restrictions exist as specified for each bit.
1 Special access - Register write restrictions are lifted.
4
AUT_RSTA
Automatic Restart Event after exit from MCU Stop and Wait Mode (SWAI set) — This bit controls if a Restart
Event is automatically generated after exit from MCU Stop Mode or Wait Mode with bit SWAI set. It can be
configured for ADC conversion flow control mode “Trigger Mode” and “Restart Mode” (anytime during application
runtime).
0 No automatic Restart Event after exit from MCU Stop Mode.
1 Automatic Restart Event occurs after exit from MCU Stop Mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
366
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.3
ADC Status Register (ADCSTS)
It is important to note that if flag DBECC_ERR is set the ADC ceases operation. In order to make the ADC
operational again an ADC Soft-Reset must be issued. An ADC Soft-Reset clears bits CSL_SEL and
RVL_SEL.
Module Base + 0x0002
R
W
Reset
7
6
CSL_SEL
RVL_SEL
0
0
5
4
3
2
1
0
DBECC_ERR
Reserved
READY
0
0
0
0
0
1
0
0
0
= Unimplemented or Reserved
Figure 10-6. ADC Status Register (ADCSTS)
Read: Anytime
Write:
• Bits CSL_SEL and RVL_SEL anytime if bit ADC_EN is clear or bit SMOD_ACC is set
• Bits DBECC_ERR and READY not writable
Table 10-5. ADCSTS Field Descriptions
Field
Description
7
CSL_SEL
Command Sequence List Select bit — This bit controls and indicates which ADC Command List is active. This
bit can only be written if ADC_EN bit is clear. This bit toggles in CSL double buffer mode when no conversion or
conversion sequence is ongoing and bit LDOK is set and bit RSTA is set. In CSL single buffer mode this bit is
forced to 1’b0 by bit CSL_BMOD.
0 ADC Command List 0 is active.
1 ADC Command List 1 is active.
6
RVL_SEL
Result Value List Select Bit — This bit controls and indicates which ADC Result List is active. This bit can only
be written if bit ADC_EN is clear. After storage of the initial Result Value List this bit toggles in RVL double buffer
mode whenever the conversion result of the first conversion of the current CSL is stored or a CSL got aborted.
In RVL single buffer mode this bit is forced to 1’b0 by bit RVL_BMOD.
Please see also Section 10.2.1.2, “MCU Operating Modes for information regarding Result List usage in case of
Stop or Wait Mode.
0 ADC Result List 0 is active.
1 ADC Result List 1 is active.
5
DBECC_ERR
3
READY
Double Bit ECC Error Flag — This flag indicates that a double bit ECC error occurred during conversion
command load or result storage and ADC ceases operation.
In order to make the ADC operational again an ADC Soft-Reset must be issued.
This bit is cleared if bit ADC_EN is clear.
0 No double bit ECC error occurred.
1 A double bit ECC error occurred.
Ready For Restart Event Flag — This flag indicates that ADC is in its idle state and ready for a Restart Event.
It can be used to verify after exit from Wait Mode if a Restart Event can be issued and processed immediately
without any latency time due to an ongoing Sequence Abort Event after exit from MCU Wait Mode (see also the
Note in Section 10.2.1.2, “MCU Operating Modes).
0 ADC not in idle state.
1 ADC is in idle state.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
367
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.4
ADC Timing Register (ADCTIM)
Module Base + 0x0003
7
R
6
5
4
0
0
2
1
0
1
0
1
PRS[6:0]
W
Reset
3
0
0
0
0
= Unimplemented or Reserved
Figure 10-7. ADC Timing Register (ADCTIM))
Read: Anytime
Write: These bits are writable if bit ADC_EN is clear or bit SMOD_ACC is set
Table 10-6. ADCTIM Field Descriptions
Field
Description
6-0
PRS[6:0]
ADC Clock Prescaler — These 7bits are the binary prescaler value PRS. The ADC conversion clock frequency
is calculated as follows:
f BUS
f A TD CLK = -----------------------------------2x ( PRS + 1 )
Refer to Device Specification for allowed frequency range of fATDCLK.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
368
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.5
ADC Format Register (ADCFMT)
Module Base + 0x0004
7
R
W
Reset
DJM
0
6
5
4
3
0
0
0
0
0
0
0
0
2
1
0
SRES[2:0]
0
0
0
= Unimplemented or Reserved
Figure 10-8. ADC Format Register (ADCFMT)
Read: Anytime
Write: Bits DJM and SRES[2:0] are writable if bit ADC_EN clear or bit SMOD_ACC set
Table 10-7. ADCFMT Field Descriptions
Field
7
DJM
2-0
SRES[2:0]
Description
Result Register Data Justification — Conversion result data format is always unsigned. This bit controls
justification of conversion result data in the conversion result list.
0 Left justified data in the conversion result list.
1 Right justified data in the conversion result list.
ADC Resolution Select — These bits select the resolution of conversion results. See Table 10-8 for coding.
Table 10-8. Selectable Conversion Resolution
SRES[2]
SRES[1]
SRES[0]
ADC Resolution
0
0
0
8-bit data
0
0
1
Reserved
0
1
0
10-bit data
0
1
1
Reserved
1
0
0
12-bit data
1
x
x
(1)
Reserved
1.
1.
1. Reserved settings cause a severe error at ADC conversion start whereby
the CMD_EIF flag is set and ADC ceases operation
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
369
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.6
ADC Conversion Flow Control Register (ADCFLWCTL)
Bit set and bit clear instructions should not be used to access this register.
When the ADC is enabled the bits of ADCFLWCTL register can be modified after a latency time of three
Bus Clock cycles.
All bits are cleared if bit ADC_EN is clear or via ADC soft-reset.
Module Base + 0x0005
7
R
W
Reset
6
5
4
SEQA
TRIG
RSTA
LDOK
0
0
0
0
3
2
1
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-9. ADC Conversion Flow Control Register (ADCFLWCTL)
Read: Anytime
Write:
• Bits SEQA, TRIG, RSTA, LDOK can only be set if bit ADC_EN is set.
• Writing 1’b0 to any of these bits does not have an effect
Timing considerations (Trigger Event - channel sample start) depending on ADC mode configuration:
• Restart Mode
When the Restart Event has been processed (initial command of current CSL is loaded) it takes two
Bus Clock cycles plus two ADC conversion clock cycles (pump phase) from the Trigger Event (bit
TRIG set) until the select channel starts to sample.
During a conversion sequence (back to back conversions) it takes five Bus Clock cycles plus two
ADC conversion clock cycles (pump phase) from current conversion period end until the newly
selected channel is sampled in the following conversion period.
• Trigger Mode
When a Restart Event occurs a Trigger Event is issued simultaneously. The time required to process
the Restart Event is mainly defined by the internal read data bus availability and therefore can vary.
In this mode the Trigger Event is processed immediately after the Restart Event is finished and both
conversion flow control bits are cleared simultaneously. From de-assert of bit TRIG until sampling
begins five Bus Clock cycles are required. Hence from occurrence of a Restart Event until channel
sampling it takes five Bus Clock cycles plus an uncertainty of a few Bus Clock cycles.
For more details regarding the sample phase please refer to Section 10.5.2.2, “Sample and Hold Machine
with Sample Buffer Amplifier.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
370
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-9. ADCFLWCTL Field Descriptions
Field
Description
7
SEQA
Conversion Sequence Abort Event — This bit indicates that a conversion sequence abort event is in progress.
When this bit is set the ongoing conversion sequence and current CSL will be aborted at the next conversion
boundary. This bit gets cleared when the ongoing conversion sequence is aborted and ADC is idle.
This bit can only be set if bit ADC_EN is set.
This bit is cleared if bit ADC_EN is clear.
Data Bus Control:
This bit can be controlled via the data bus if access control is configured accordingly via ACC_CFG[1:0].
Writing a value of 1’b0 does not clear the flag.
Writing a one to this bit does not clear it but causes an overrun if the bit has already been set. See
Section 10.5.3.2.6, “Conversion flow control in case of conversion sequence control bit overrun scenarios for
more details.
Internal Interface Control:
This bit can be controlled via the internal interface Signal “Seq_Abort” if access control is configured accordingly
via ACC_CFG[1:0]. After being set an additional request via the internal interface Signal “Seq_Abort” causes an
overrun. See also conversion flow control in case of overrun situations.
General:
In both conversion flow control modes (Restart Mode and Trigger Mode) when bit RSTA gets set automatically
bit SEQA gets set when the ADC has not reached one of the following scenarios:
- A Sequence Abort request is about to be executed or has been executed.
- “End Of List” command type has been executed or is about to be executed
In case bit SEQA is set automatically the Restart error flag RSTA_EIF is set to indicate an unexpected Restart
Request.
0 No conversion sequence abort request.
1 Conversion sequence abort request.
6
TRIG
Conversion Sequence Trigger Bit — This bit starts a conversion sequence if set and no conversion or
conversion sequence is ongoing. This bit is cleared when the first conversion of a sequence starts to sample.
This bit can only be set if bit ADC_EN is set.
This bit is cleared if bit ADC_EN is clear.
Data Bus Control:
This bit can be controlled via the data bus if access control is configured accordingly via ACC_CFG[1:0].
Writing a value of 1’b0 does not clear the flag.
After being set this bit can not be cleared by writing a value of 1’b1 instead the error flag TRIG_EIF is set. See
also Section 10.5.3.2.6, “Conversion flow control in case of conversion sequence control bit overrun scenarios
for more details.
Internal Interface Control:
This bit can be controlled via the internal interface Signal “Trigger” if access control is configured accordingly via
ACC_CFG[1:0]. After being set an additional request via internal interface Signal “Trigger“ causes the flag
TRIG_EIF to be set.
0 No conversion sequence trigger.
1 Trigger to start conversion sequence.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
371
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-9. ADCFLWCTL Field Descriptions (continued)
Field
Description
5
RSTA
Restart Event (Restart from Top of Command Sequence List) — This bit indicates that a Restart Event is
executed. The ADC loads the conversion command from top of the active Sequence Command List when no
conversion or conversion sequence is ongoing. This bit is cleared when the first conversion command of the
sequence from top of active Sequence Command List has been loaded into the ADCCMD register.
This bit can only be set if bit ADC_EN is set.
This bit is cleared if bit ADC_EN is clear.
Data Bus Control:
This bit can be controlled via the data bus if access control is configured accordingly via ACC_CFG[1:0].
Writing a value of 1’b0 does not clear the flag.
Writing a one to this bit does not clear it but causes an overrun if the bit has already been set. See also
Section 10.5.3.2.6, “Conversion flow control in case of conversion sequence control bit overrun scenarios for
more details.
Internal Interface Control:
This bit can be controlled via the internal interface Signal “Restart” if access control is configured accordingly via
ACC_CFG[1:0]. After being set an additional request via internal interface Signal “Restart“ causes an overrun.
See conversion flow control in case of overrun situations for more details.
General:
In conversion flow control mode “Trigger Mode” when bit RSTA gets set bit TRIG is set simultaneously if one of
the following has been executed:
- “End Of List” command type has been executed or is about to be executed
- Sequence Abort Event
0 Continue with commands from active Sequence Command List.
1 Restart from top of active Sequence Command List.
4
LDOK
Load OK for alternative Command Sequence List — This bit indicates if the preparation of the alternative
Sequence Command List is done and Command Sequence List must be swapped with the Restart Event. This
bit is cleared when bit RSTA is set (Restart Event executed) and the Command Sequence List got swapped.
This bit can only be set if bit ADC_EN is set.
This bit is cleared if bit ADC_EN is clear.
This bit is forced to zero if bit CSL_BMOD is clear.
Data Bus Control:
This bit can be controlled via the data bus if access control is configured accordingly via ACC_CFG[1:0].
Writing a value of 1’b0 does not clear the flag.
To set bit LDOK the bits LDOK and RSTA must be written simultaneously.
After being set this bit can not be cleared by writing a value of 1’b1. See also Section 10.5.3.2.6, “Conversion
flow control in case of conversion sequence control bit overrun scenarios for more details.
Internal Interface Control:
This bit can be controlled via the internal interface Signal “LoadOK” and “Restart” if access control is configured
accordingly via ACC_CFG[1:0]. With the assertion of Interface Signal “Restart” the interface Signal “LoadOK” is
evaluated and bit LDOK set accordingly (bit LDOK set if Interface Signal “LoadOK” asserted when Interface
Signal “Restart” asserts).
General:
Only in “Restart Mode” if a Restart Event occurs without bit LDOK being set the error flag LDOK_EIF is set except
when the respective Restart Request occurred after or simultaneously with a Sequence Abort Request.
The LDOK_EIF error flag is also not set in “Restart Mode” if the first Restart Event occurs after:
- ADC got enabled
- Exit from Stop Mode
- ADC Soft-Reset
0 Load of alternative list done.
1 Load alternative list.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
372
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-10. Summary of Conversion Flow Control Bit Scenarios
RSTA
TRIG
SEQA
LDOK
Conversion Flow
Conversion Flow Control
Control Mode
Scenario
0
0
0
0
Both Modes
Valid
0
0
0
1
Both Modes
Can Not Occur
0
0
1
0
Both Modes
5.
Valid
0
0
1
1
Both Modes
Can Not Occur
0
1
0
0
Both Modes
2.
Valid
0
1
0
1
Both Modes
Can Not Occur
0
1
1
0
Both Modes
Can Not Occur
0
1
1
1
Both Modes
Can Not Occur
1
0
0
0
Both Modes
4.
Valid
1
0
0
1
Both Modes
1. 4.
Valid
1
0
1
0
Both Modes
3. 4. 5.
Valid
1
0
1
1
Both Modes
1
1
0
0
1
1
0
1
1
1
1
1
1. 3. 4. 5.
“Restart Mode”
Error flag TRIG_EIF set
“Trigger Mode”
2. 4. 6.
Valid
“Restart Mode”
Error flag TRIG_EIF set
1
“Trigger Mode”
1
Valid
Valid
1. 2. 4. 6.
“Restart Mode”
Error flag TRIG_EIF set
“Trigger Mode”
2. 3. 4. 5. 6.
Valid
“Restart Mode”
Error flag TRIG_EIF set
“Trigger Mode”
(1) (2) (3) (4) (5) (6)
Valid
0
1
1. Swap CSL buffer
2. Start conversion sequence
3. Prevent RSTA_EIF and LDOK_EIF
4. Load conversion command from top of CSL
5. Abort any ongoing conversion, conversion sequence and CSL
6. Bit TRIG set automatically in Trigger Mode
For a detailed description of all conversion flow control bit scenarios please see also Section 10.5.3.2.4,
“The two conversion flow control Mode Configurations, Section 10.5.3.2.5, “The four ADC conversion
flow control bits and Section 10.5.3.2.6, “Conversion flow control in case of conversion sequence control
bit overrun scenarios
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
373
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.7
ADC Error Interrupt Enable Register (ADCEIE)
Module Base + 0x0006
7
R
W
Reset
6
5
4
3
2
1
IA_EIE
CMD_EIE
EOL_EIE
Reserved
TRIG_EIE
RSTAR_EIE
LDOK_EIE
0
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-10. ADC Error Interrupt Enable Register (ADCEIE)
Read: Anytime
Write: Anytime
Table 10-11. ADCEIE Field Descriptions
Field
7
IA_EIE
Description
Illegal Access Error Interrupt Enable Bit — This bit enables the illegal access error interrupt.
0 Illegal access error interrupt disabled.
1 Illegal access error interrupt enabled.
6
CMD_EIE
Command Value Error Interrupt Enable Bit — This bit enables the command value error interrupt.
0 Command value interrupt disabled.
1 Command value interrupt enabled.
5
EOL_EIE
”End Of List” Error Interrupt Enable Bit — This bit enables the “End Of List” error interrupt.
0 “End Of List” error interrupt disabled.
1 “End Of List” error interrupt enabled.
3
TRIG_EIE
Conversion Sequence Trigger Error Interrupt Enable Bit — This bit enables the conversion sequence trigger
error interrupt.
0 Conversion sequence trigger error interrupt disabled.
1 Conversion sequence trigger error interrupt enabled.
2
Restart Request Error Interrupt Enable Bit— This bit enables the restart request error interrupt.
RSTAR_EIE 0 Restart Request error interrupt disabled.
1 Restart Request error interrupt enabled.
1
LDOK_EIE
Load OK Error Interrupt Enable Bit — This bit enables the Load OK error interrupt.
0 Load OK error interrupt disabled.
1 Load OK error interrupt enabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
374
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.8
ADC Interrupt Enable Register (ADCIE)
Module Base + 0x0007
7
R
W
6
5
SEQAD_IE
CONIF_OIE
Reserved
0
0
0
Reset
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-11. ADC Interrupt Enable Register (ADCIE)
Read: Anytime
Write: Anytime
Table 10-12. ADCIE Field Descriptions
Field
Description
7
SEQAD_IE
Conversion Sequence Abort Done Interrupt Enable Bit — This bit enables the conversion sequence abort
event done interrupt.
0 Conversion sequence abort event done interrupt disabled.
1 Conversion sequence abort event done interrupt enabled.
6
CONIF_OIE
ADCCONIF Register Flags Overrun Interrupt Enable — This bit enables the flag which indicates if an overrun
situation occurred for one of the CON_IF[15:1] flags or for the EOL_IF flag.
0 No ADCCONIF Register Flag overrun occurred.
1 ADCCONIF Register Flag overrun occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
375
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.9
ADC Error Interrupt Flag Register (ADCEIF)
If one of the following error flags is set the ADC ceases operation:
• IA_EIF
• CMD_EIF
• EOL_EIF
• TRIG_EIF
In order to make the ADC operational again an ADC Soft-Reset must be issued which clears above listed
error interrupt flags.
The error interrupt flags RSTAR_EIF and LDOK_EIF do not cause the ADC to cease operation. If set the
ADC continues operation. Each of the two bits can be cleared by writing a value of 1’b1. Both bits are also
cleared if an ADC Soft-Reset is issued.
All bits are cleared if bit ADC_EN is clear. Writing any flag with value 1’b0 does not clear a flag. Writing
any flag with value 1’b1 does not set the flag.
Module Base + 0x0008
R
W
Reset
7
6
5
4
3
2
1
IA_EIF
CMD_EIF
EOL_EIF
Reserved
TRIG_EIF
RSTAR_EIF
LDOK_EIF
0
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-12. ADC Error Interrupt Flag Register (ADCEIF)
Read: Anytime
Write:
• Bits RSTAR_EIF and LDOK_EIF are writable anytime
• Bits IA_EIF, CMD_EIF, EOL_EIF and TRIG_EIF are not writable
Table 10-13. ADCEIF Field Descriptions
Field
7
IA_EIF
Description
Illegal Access Error Interrupt Flag — This flag indicates that storing the conversion result caused an illegal
access error or conversion command loading from outside system RAM or NVM area occurred.
The ADC ceases operation if this error flag is set (issue of type severe).
0 No illegal access error occurred.
1 An illegal access error occurred.
6
CMD_EIF
Command Value Error Interrupt Flag — This flag indicates that an invalid command is loaded (Any command
that contains reserved bit settings) or illegal format setting selected (reserved SRES[2:0] bit settings).
The ADC ceases operation if this error flag is set (issue of type severe).
0 Valid conversion command loaded.
1 Invalid conversion command loaded.
5
EOL_EIF
“End Of List” Error Interrupt Flag — This flag indicates a missing “End Of List” command type in current
executed CSL.
The ADC ceases operation if this error flag is set (issue of type severe).
0 No “End Of List” error.
1 “End Of List” command type missing in current executed CSL.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
376
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-13. ADCEIF Field Descriptions (continued)
Field
Description
3
TRIG_EIF
Trigger Error Interrupt Flag — This flag indicates that a trigger error occurred.
This flag is set in “Restart” Mode when a conversion sequence got aborted and no Restart Event occurred before
the Trigger Event or if the Trigger Event occurred before the Restart Event was finished (conversion command
has been loaded).
This flag is set in “Trigger” Mode when a Trigger Event occurs before the Restart Event is issued to start
conversion of the initial Command Sequence List. In “Trigger” Mode only a Restart Event is required to start
conversion of the initial Command Sequence List.
This flag is set when a Trigger Event occurs before a conversion sequence got finished.
This flag is also set if a Trigger occurs while a Trigger Event is just processed - first conversion command of a
sequence is beginning to sample (see also Section 10.5.3.2.6, “Conversion flow control in case of conversion
sequence control bit overrun scenarios).
This flag is also set if the Trigger Event occurs automatically generated by hardware in “Trigger Mode” due to a
Restart Event and simultaneously a Trigger Event is generated via data bus or internal interface.
The ADC ceases operation if this error flag is set (issue of type severe).
0 No trigger error occurred.
1 A trigger error occurred.
2
Restart Request Error Interrupt Flag — This flag indicates a flow control issue. It is set when a Restart Request
RSTAR_EIF occurs after a Trigger Event and before one of the following conditions was reached:
- The “End Of List” command type has been executed
- Depending on bit STR_SEQA if the “End Of List” command type is about to be executed
- The current CSL has been aborted or is about to be aborted due to a Sequence Abort Request.
The ADC continues operation if this error flag is set.
This flag is not set for Restart Request overrun scenarios (see also Section 10.5.3.2.6, “Conversion flow control
in case of conversion sequence control bit overrun scenarios).
0 No Restart request error situation occurred.
1 Restart request error situation occurred.
1
LDOK_EIF
Load OK Error Interrupt Flag — This flag can only be set in “Restart Mode”. It indicates that a Restart Request
occurred without LDOK. This flag is not set if a Sequence Abort Event is already in process (bit SEQA set) when
the Restart Request occurs or a Sequence Abort Request occurs simultaneously with the Restart Request.
The LDOK_EIF error flag is also not set in “Restart Mode” if the first Restart Event occurs after:
- ADC got enabled
- Exit from Stop Mode
- ADC Soft-Reset
- ADC used in CSL single buffer mode
The ADC continues operation if this error flag is set.
0 No Load OK error situation occurred.
1 Load OK error situation occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
377
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.10 ADC Interrupt Flag Register (ADCIF)
After being set any of these bits can be cleared by writing a value of 1’b1 or via ADC soft-reset (bit
ADC_SR). All bits are cleared if bit ADC_EN is clear. Writing any flag with value 1’b0 does not clear the
flag. Writing any flag with value 1’b1 does not set the flag.
Module Base + 0x0009
R
W
7
6
5
SEQAD_IF
CONIF_OIF
Reserved
0
0
0
Reset
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-13. ADC Interrupt Flag Register (ADCIF)
Read: Anytime
Write: Anytime
Table 10-14. ADCIF Field Descriptions
Field
Description
7
SEQAD_IF
Conversion Sequence Abort Done Interrupt Flag — This flag is set when the Sequence Abort Event has been
executed except the Sequence Abort Event occurred by hardware in order to be able to enter MCU Stop Mode
or Wait Mode with bit SWAI set.This flag is also not set if the Sequence Abort request occurs during execution
of the last conversion command of a CSL and bit STR_SEQA being set.
0 No conversion sequence abort request occurred.
1 A conversion sequence abort request occurred.
6
CONIF_OIF
ADCCONIF Register Flags Overrun Interrupt Flag — This flag indicates if an overrun situation occurred for
one of the CON_IF[15:1] flags or for the EOL_IF flag. In RVL single buffer mode (RVL_BMOD clear) an overrun
of the EOL_IF flag is not indicated (For more information please see Note below).
0 No ADCCONIF Register Flag overrun occurred.
1 ADCCONIF Register Flag overrun occurred.
NOTE
In RVL double buffer mode a conversion interrupt flag (CON_IF[15:1]) or
End Of List interrupt flag (EOL_IF) overrun is detected if one of these bits
is set when it should be set again due to conversion command execution.
In RVL single buffer mode a conversion interrupt flag (CON_IF[15:1])
overrun is detected only. The overrun is detected if any of the conversion
interrupt flags (CON_IF[15:1]) is set while the first conversion result of a
CSL is stored (result of first conversion from top of CSL is stored).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
378
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.11 ADC Conversion Interrupt Enable Register (ADCCONIE)
Module Base + 0x000A
15
14
13
12
11
10
R
8
7
6
5
4
3
2
1
CON_IE[15:1]
W
Reset
9
0
0
0
0
0
0
0
0
0
0
EOL_IE
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-14. ADC Conversion Interrupt Enable Register (ADCCONIE)
Read: Anytime
Write: Anytime
Table 10-15. ADCCONIE Field Descriptions
Field
15-1
CON_IE[15:1]
0
EOL_IE
Description
Conversion Interrupt Enable Bits — These bits enable the individual interrupts which can be triggered via
interrupt flags CON_IF[15:1].
0 ADC conversion interrupt disabled.
1 ADC conversion interrupt enabled.
End Of List Interrupt Enable Bit — This bit enables the end of conversion sequence list interrupt.
0 End of list interrupt disabled.
1 End of list interrupt enabled.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
379
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.12 ADC Conversion Interrupt Flag Register (ADCCONIF)
After being set any of these bits can be cleared by writing a value of 1’b1. All bits are cleared if bit
ADC_EN is clear or via ADC soft-reset (bit ADC_SR set). Writing any flag with value 1’b0 does not clear
the flag. Writing any flag with value 1’b1 does not set the flag.
Module Base + 0x000C
15
14
13
12
11
10
R
8
7
6
5
4
3
2
1
CON_IF[15:1]
W
Reset
9
0
0
0
0
0
0
0
0
0
0
EOL_IF
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-15. ADC Conversion Interrupt Flag Register (ADCCONIF)
Read: Anytime
Write: Anytime
Table 10-16. ADCCONIF Field Descriptions
Field
Description
15-1
CON_IF[15:1]
Conversion Interrupt Flags — These bits could be set by the binary coded interrupt select bits
INTFLG_SEL[3:0] when the corresponding conversion command has been processed and related data has been
stored to RAM.
See also notes below.
0
EOL_IF
End Of List Interrupt Flag — This bit is set by the binary coded conversion command type select bits
CMD_SEL[1:0] for “end of list” type of commands and after such a command has been processed and the related
data has been stored RAM.
See also second note below
NOTE
These bits can be used to indicate if a certain packet of conversion results is
available. Clearing a flag indicates that conversion results have been
retrieved by software and the flag can be used again (see also Section 10.8.6,
“RVL swapping in RVL double buffer mode and related registers
ADCIMDRI and ADCEOLRI.
NOTE
Overrun situation of a flag CON_IF[15:1] and EOL_IF are indicated by flag
CONIF_OIF.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
380
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.13 ADC Intermediate Result Information Register (ADCIMDRI)
This register is cleared when bit ADC_SR is set or bit ADC_EN is clear.
Module Base + 0x000E
15
14
R CSL_IMD RVL_IMD
13
12
11
10
9
8
7
6
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
5
4
3
2
1
0
0
0
RIDX_IMD[5:0]
W
Reset
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-16. ADC Intermediate Result Information Register (ADCIMDRI)
Read: Anytime
Write: Never
Table 10-17. ADCIMDRI Field Descriptions
Field
Description
15
CSL_IMD
Active CSL At Intermediate Event — This bit indicates the active (used) CSL at the occurrence of a conversion
interrupt flag (CON_IF[15:1]) (occurrence of an intermediate result buffer fill event) or when a Sequence Abort
Event gets executed.
0 CSL_0 active (used) when a conversion interrupt flag (CON_IF[15:1]) got set.
1 CSL_1 active (used) when a conversion interrupt flag (CON_IF[15:1]) got set.
14
RVL_IMD
Active RVL At Intermediate Event — This bit indicates the active (used) RVL buffer at the occurrence of a
conversion interrupt flag (CON_IF[15:1]) (occurrence of an intermediate result buffer fill event) or when a
Sequence Abort Event gets executed.
0 RVL_0 active (used) when a conversion interrupt flag (CON_IF[15:1]) got set.
1 RVL_1 active (used) when a conversion interrupt flag (CON_IF[15:1]) got set.
5-0
RES_IDX Value At Intermediate Event — These bits indicate the result index (RES_IDX) value at the
RIDX_IMD[5:0] occurrence of a conversion interrupt flag (CON_IF[15:1]) (occurrence of an intermediate result buffer fill event)
or occurrence of EOL_IF flag or when a Sequence Abort Event gets executed to abort an ongoing conversion
(the result index RES_IDX is captured at the occurrence of a result data store).
When a Sequence Abort Event has been processed flag SEQAD_IF is set and the RES_IDX value of the last
stored result is provided. Hence in case an ongoing conversion is aborted the RES_IDX value captured in
RIDX_IMD bits depends on bit STORE_SEQA:
- STORE_SEQA =1: The result index of the aborted conversion is provided
- STORE_SEQA =0: The result index of the last stored result at abort execution time is provided
In case a CSL is aborted while no conversion is ongoing (ADC waiting for a Trigger Event) the last captured result
index is provided.
In case a Sequence Abort Event was initiated by hardware due to MCU entering Stop Mode or Wait Mode with
bit SWAI set, the result index of the last stored result is captured by bits RIDX_IMD but flag SEQAD_IF is not set.
NOTE
The register ADCIMDRI is updated and simultaneously a conversion
interrupt flag CON_IF[15:1] occurs when the corresponding conversion
command (conversion command with INTFLG_SEL[3:0] set) has been
processed and related data has been stored to RAM.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
381
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.14 ADC End Of List Result Information Register (ADCEOLRI)
This register is cleared when bit ADC_SR is set or bit ADC_EN is clear.
Module Base + 0x0010
R
7
6
5
4
3
2
1
0
CSL_EOL
RVL_EOL
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 10-17. ADC End Of List Result Information Register (ADCEOLRI)
Read: Anytime
Write: Never
Table 10-18. ADCEOLRI Field Descriptions
Field
Description
7
CSL_EOL
Active CSL When “End Of List” Command Type Executed — This bit indicates the active (used) CSL when
a “End Of List” command type has been executed and related data has been stored to RAM.
0 CSL_0 active when “End Of List” command type executed.
1 CSL_1 active when “End Of List” command type executed.
6
RVL_EOL
Active RVL When “End Of List” Command Type Executed — This bit indicates the active (used) RVL when
a “End Of List” command type has been executed and related data has been stored to RAM.
0 RVL_0 active when “End Of List” command type executed.
1 RVL_1 active when “End Of List” command type executed.
NOTE
The conversion interrupt EOL_IF occurs and simultaneously the register
ADCEOLRI is updated when the “End Of List” conversion command type
has been processed and related data has been stored to RAM.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
382
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.15 ADC Command Register 0 (ADCCMD_0)
Module Base + 0x0014
31
R
CMD_SEL
W
Reset
30
0
0
29
28
0
0
0
0
27
26
25
24
INTFLG_SEL[3:0]
0
0
0
0
= Unimplemented or Reserved
Figure 10-18. ADC Command Register 0 (ADCCMD_0)
Read: Anytime
Write: Only writable if bit SMOD_ACC is set
(see also Section 10.4.2.2, “ADC Control Register 1 (ADCCTL_1) bit SMOD_ACC description for more
details)
Table 10-19. ADCCMD_0 Field Descriptions
Field
Description
31-30
Conversion Command Select Bits — These bits define the type of current conversion described in Table 10CMD_SEL[1:0]
20.
27-24
Conversion Interrupt Flag Select Bits — These bits define which interrupt flag is set in the ADCIFH/L register
INTFLG_SEL[3:0] at the end of current conversion.The interrupt flags ADCIF[15:1] are selected via binary coded bits
INTFLG_SEL[3:0]. See also Table 10-21
NOTE
If bit SMOD_ACC is set modifying this register must be done carefully only when no conversion and conversion sequence is ongoing.
Table 10-20. Conversion Command Type Select
CMD_SEL[1]
CMD_SEL[0]
Conversion Command Type Description
0
0
Normal Conversion
0
1
1
0
End Of Sequence
(Wait for Trigger to execute next sequence or for a Restart)
End Of List
(Automatic wrap to top of CSL
and Continue Conversion)
End Of List
1
1
(Wrap to top of CSL and:
- In “Restart Mode” wait for Restart Event followed by a Trigger
- In “Trigger Mode” wait for Trigger or Restart Event)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
383
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-21. Conversion Interrupt Flag Select
CON_IF[15:1]
INTFLG_SEL[3]
INTFLG_SEL[2]
INTFLG_SEL[1]
INTFLG_SEL[0]
Comment
0x0000
0
0
0
0
No flag set
0x0001
0
0
0
1
0x0002
0
0
1
0
0x0004
0
0
1
1
0x0008
0
1
0
0
0x0010
0
1
0
1
Only one flag can
....
...
...
...
...
(one hot coding)
0x0800
1
1
0
0
0x1000
1
1
0
1
0x2000
1
1
1
0
0x4000
1
1
1
1
be set
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
384
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.16 ADC Command Register 1 (ADCCMD_1)
A command which contains reserved bit settings causes the error flag CMD_EIF being set and ADC cease
operation.
Module Base + 0x0015
R
W
23
22
VRH_SEL
VRL_SEL
Reset
0
21
20
19
18
17
16
0
0
CH_SEL[5:0]
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-19. ADC Command Register 1 (ADCCMD_1)
Read: Anytime
Write: Only writable if bit SMOD_ACC is set
(see also Section 10.4.2.2, “ADC Control Register 1 (ADCCTL_1) bit SMOD_ACC description for more
details)
Table 10-22. ADCCMD_1 Field Descriptions
Field
Description
23
VRH_SEL
Reference High Voltage Select Bit — This bit selects the high voltage reference for current conversion.
0 VRH_0 input selected as high voltage reference.
1 VRH_1 input selected as high voltage reference.
22
VRL_SEL
Reference Low Voltage Select Bit — This bit selects the voltage reference for current conversion.
0 VRL_0 input selected as low voltage reference.
1 VRL_1 input selected as low voltage reference.
21-16
ADC Input Channel Select Bits — These bits select the input channel for the current conversion. See Table 10CH_SEL[5:0] 23 for channel coding information.
NOTE
If bit SMOD_ACC is set modifying this register must be done carefully only when no conversion and conversion sequence is ongoing.
Table 10-23. Analog Input Channel Select
CH_SEL[5]
CH_SEL[4]
CH_SEL[3]
CH_SEL[2]
CH_SEL[1]
CH_SEL[0]
Analog Input Channel
0
0
0
0
0
0
VRL_0/1
0
0
0
0
0
1
VRH_0/1
0
0
0
0
1
0
(VRH_0/1 + VRL_0/1) / 2
0
0
0
0
1
1
Reserved
0
0
0
1
0
0
Reserved
0
0
0
1
0
1
Reserved
0
0
0
1
1
0
Reserved
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
385
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-23. Analog Input Channel Select
CH_SEL[5]
CH_SEL[4]
CH_SEL[3]
CH_SEL[2]
CH_SEL[1]
CH_SEL[0]
Analog Input Channel
0
0
0
1
1
1
Reserved
0
0
1
0
0
0
Internal_0
(ADC temperature sense)
0
0
1
0
0
1
Internal_1
(Vreg_3v3 sense)
0
0
1
0
1
0
Internal_2
0
0
1
0
1
1
Internal_3
0
0
1
1
0
0
Internal_4
0
0
1
1
0
1
Internal_5
0
0
1
1
1
0
Internal_6
0
0
1
1
1
1
Internal_7
0
1
0
0
0
0
AN0
0
1
0
0
0
1
AN1
0
1
0
0
1
0
AN2
0
1
0
0
1
1
AN3
0
1
0
1
0
0
AN4
0
1
x
x
x
x
ANx
1
x
x
x
x
x
Reserved
NOTE
ANx in Table 10-23 is the maximum number of implemented analog input
channels on the device. Please refer to the device overview of the reference
manual for details regarding number of analog input channels.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
386
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.17 ADC Command Register 2 (ADCCMD_2)
A command which contains reserved bit settings causes the error flag CMD_EIF being set and ADC cease
operation.
Module Base + 0x0016
15
14
13
R
11
SMP[4:0]
W
Reset
12
0
0
0
0
0
10
9
0
0
0
0
8
Reserved
0
= Unimplemented or Reserved
Figure 10-20. ADC Command Register 2 (ADCCMD_2)
Read: Anytime
Write: Only writable if bit SMOD_ACC is set
(see also Section 10.4.2.2, “ADC Control Register 1 (ADCCTL_1) bit SMOD_ACC description for more
details)
Table 10-24. ADCCMD_2 Field Descriptions
Field
Description
15-11
SMP[4:0]
Sample Time Select Bits — These four bits select the length of the sample time in units of ADC conversion
clock cycles. Note that the ADC conversion clock period is itself a function of the prescaler value (bits PRS[6:0]).
Table 10-25 lists the available sample time lengths.
NOTE
If bit SMOD_ACC is set modifying this register must be done carefully only when no conversion and conversion sequence is ongoing.
Table 10-25. Sample Time Select
SMP[4]
SMP[3]
SMP[2]
SMP[1]
SMP[0]
Sample Time
in Number of
ADC Clock Cycles
0
0
0
0
0
4
0
0
0
0
1
5
0
0
0
1
0
6
0
0
0
1
1
7
0
0
1
0
0
8
0
0
1
0
1
9
0
0
1
1
0
10
0
0
1
1
1
11
0
1
0
0
0
12
0
1
0
0
1
13
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
387
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Table 10-25. Sample Time Select
SMP[4]
SMP[3]
SMP[2]
SMP[1]
SMP[0]
Sample Time
in Number of
ADC Clock Cycles
0
1
0
1
0
14
0
1
0
1
1
15
0
1
1
0
0
16
0
1
1
0
1
17
0
1
1
1
0
18
0
1
1
1
1
19
1
0
0
0
0
20
1
0
0
0
1
21
1
0
0
1
0
22
1
0
0
1
1
23
1
0
1
0
0
24
1
0
1
0
1
Reserved
1
0
1
1
0
Reserved
1
0
1
1
1
Reserved
1
1
x
x
x
Reserved
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
388
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.18 ADC Command Register 3 (ADCCMD_3)
Module Base + 0x0017
R
W
Reset
7
6
5
Reserved
Reserved
0
0
4
3
2
1
0
0
0
0
Reserved
0
0
0
= Unimplemented or Reserved
Figure 10-21. ADC Command Register 3 (ADCCMD_3)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
389
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.19 ADC Command Index Register (ADCCIDX)
It is important to note that these bits do not represent absolute addresses instead it is a sample index (object
size 32bit).
Module Base + 0x001C
R
7
6
0
0
5
4
3
2
1
0
0
0
CMD_IDX[5:0]
W
Reset
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-22. ADC Command Index Register (ADCCIDX)
Read: Anytime
Write: NA
Table 10-26. ADCCIDX Field Descriptions
Field
Description
5-0
CMD_IDX
[5:0]
ADC Command Index Bits — These bits represent the command index value for the conversion commands
relative to the two CSL start addresses in the memory map. These bits do not represent absolute addresses
instead it is a sample index (object size 32bit). See also Section 10.5.3.2.2, “Introduction of the two Command
Sequence Lists (CSLs) for more details.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
390
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.20 ADC Command Base Pointer Register (ADCCBP)
Module Base + 0x001D
23
22
21
20
19
18
17
16
R
CMD_PTR[23:16]
W
Reset
0
0
0
0
0
0
0
0
14
13
12
11
10
9
8
0
0
Module Base + 0x001E
15
R
CMD_PTR[15:8]
W
Reset
0
0
0
0
0
0
6
5
4
3
2
Module Base + 0x001F
7
R
CMD_PTR[7:2]
W
Reset
0
0
0
0
0
0
1
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-23. ADC Command Base Pointer Registers (ADCCBP_0, ADCCBP_1, ADCCBP_2))
Read: Anytime
Write: Bits CMD_PTR[23:2] writable if bit ADC_EN clear or bit SMOD_ACC set
Table 10-27. ADCCBP Field Descriptions
Field
Description
23-2
ADC Command Base Pointer Address — These bits define the base address of the two CSL areas inside the
CMD_PTR [23:2] system RAM or NVM of the memory map. They are used to calculate the final address from which the conversion
commands will be loaded depending on which list is active. For more details see Section 10.5.3.2.2, “Introduction
of the two Command Sequence Lists (CSLs).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
391
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.21 ADC Result Index Register (ADCRIDX)
It is important to note that these bits do not represent absolute addresses instead it is a sample index (object
size 16bit).
Module Base + 0x0020
R
7
6
0
0
5
4
3
2
1
0
0
0
RES_IDX[5:0]
W
Reset
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-24. ADC Result Index Register (ADCRIDX)
Read: Anytime
Write: NA
Table 10-28. ADCRIDX Field Descriptions
Field
Description
5-0
RES_IDX[5:0]
ADC Result Index Bits — These read only bits represent the index value for the conversion results relative to
the two RVL start addresses in the memory map. These bits do not represent absolute addresses instead it is a
sample index (object size 16bit). See also Section 10.5.3.2.3, “Introduction of the two Result Value Lists (RVLs)
for more details.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
392
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.22 ADC Result Base Pointer Register (ADCRBP)
Module Base + 0x0021
R
23
22
21
20
0
0
0
0
19
18
17
16
RES_PTR[19:16]
W
Reset
0
0
0
0
0
0
0
0
14
13
12
11
10
9
8
0
0
Module Base + 0x0022
15
R
RES_PTR[15:8]
W
Reset
0
0
0
0
0
0
6
5
4
3
2
Module Base + 0x0023
7
R
RES_PTR[7:2]
W
Reset
0
0
0
0
0
0
1
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-25. ADC Result Base Pointer Registers (ADCRBP_0, ADCRBP_1, ADCRBP_2))
Read: Anytime
Write: Bits RES_PTR[19:2] writeable if bit ADC_EN clear or bit SMOD_ACC set
Table 10-29. ADCRBP Field Descriptions
Field
Description
19-2
ADC Result Base Pointer Address — These bits define the base address of the list areas inside the system
RES_PTR[19:2] RAM of the memory map to which conversion results will be stored to at the end of a conversion. These bits can
only be written if bit ADC_EN is clear. See also Section 10.5.3.2.3, “Introduction of the two Result Value Lists
(RVLs).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
393
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.23 ADC Command and Result Offset Register 0 (ADCCROFF0)
Module Base + 0x0024
7
R
6
5
4
0
3
2
1
0
0
0
0
CMDRES_OFF0[6:0]
W
Reset
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-26. ADC Command and Result Offset Register 0 (ADCCROFF0)
Read: Anytime
Write: NA
Table 10-30. ADCCROFF0 Field Descriptions
Field
Description
6-0
ADC Command and Result Offset Value — These read only bits represent the conversion command and result
CMDRES_OFF0 offset value relative to the conversion command base pointer address and result base pointer address in the
[6:0]
memory map to refer to CSL_0 and RVL_0. It is used to calculate the address inside the system RAM to which
the result at the end of the current conversion is stored to and the area (RAM or NVM) from which the conversion
commands are loaded from. This is a zero offset (null offset) which can not be modified. These bits do not
represent absolute addresses instead it is a sample offset (object size 16bit for RVL, object size 32bit for CSL).
See also Section 10.5.3.2.2, “Introduction of the two Command Sequence Lists (CSLs) and Section 10.5.3.2.3,
“Introduction of the two Result Value Lists (RVLs) for more details.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
394
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.4.2.24 ADC Command and Result Offset Register 1 (ADCCROFF1)
It is important to note that these bits do not represent absolute addresses instead it is an sample offset
(object size 16bit for RVL, object size 32bit for CSL).
Module Base + 0x0025
7
R
6
5
4
0
2
1
0
0
0
0
CMDRES_OFF1[6:0]
W
Reset
3
0
0
0
0
0
= Unimplemented or Reserved
Figure 10-27. ADC Command and Result Offset Register 1 (ADCCROFF1)
Read: Anytime
Write: These bits are writable if bit ADC_EN clear or bit SMOD_ACC set
Table 10-31. ADCCROFF1 Field Descriptions
Field
Description
6-0
ADC Result Address Offset Value — These bits represent the conversion command and result offset value
CMDRES_OFF1 relative to the conversion command base pointer address and result base pointer address in the memory map
[6:0]
to refer to CSL_1 and RVL_1. It is used to calculate the address inside the system RAM to which the result at
the end of the current conversion is stored to and the area (RAM or NVM) from which the conversion commands
are loaded from. These bits do not represent absolute addresses instead it is an sample offset (object size 16bit
for RVL, object size 32bit for CSL).,These bits can only be modified if bit ADC_EN is clear. See also
Section 10.5.3.2.2, “Introduction of the two Command Sequence Lists (CSLs) and Section 10.5.3.2.3,
“Introduction of the two Result Value Lists (RVLs) for more details.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
395
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5
Functional Description
10.5.1
Overview
The ADC12B_LBA consists of an analog sub-block and a digital sub-block. It is a successive
approximation analog-to-digital converter including a sample-and-hold mechanism and an internal charge
scaled C-DAC (switched capacitor scaled digital-to-analog converter) with a comparator to realize the
successive approximation algorithm.
10.5.2
Analog Sub-Block
The analog sub-block contains all analog circuits (sample and hold, C-DAC, analog Comparator, and so
on) required to perform a single conversion. Separate power supplies VDDA and VSSA allow noise from
the MCU circuitry to be isolated from the analog sub-block for improved accuracy.
10.5.2.1
Analog Input Multiplexer
The analog input multiplexers connect one of the external or internal analog input channels to the sample
and hold storage node.
10.5.2.2
Sample and Hold Machine with Sample Buffer Amplifier
The Sample and Hold Machine controls the storage and charge of the storage node (sample capacitor) to
the voltage level of the analog signal at the selected ADC input channel. This architecture employs the
advantage of reduced crosstalk between channels.
The sample buffer amplifier is used to raise the effective input impedance of the A/D machine, so that
external components (higher bandwidth or higher impedance connected as specified) are less significant
to accuracy degradation.
During the sample phase, the analog input connects first via a sample buffer amplifier with the storage node
always for two ADC clock cycles (“Buffer” sample time). For the remaining sample time (“Final” sample
time) the storage node is directly connected to the analog input source. Please see also Figure 10-28 for
illustration and the Appendix of the device reference manual for more details.
The input analog signals are unipolar and must be within the potential range of VSSA to VDDA.
During the hold process, the analog input is disconnected from the storage node.
1
2
3
Total Sample Time
(N = SMP[4:0])
"Buffer"
Sample Time
(2 cycles)
4
5
6
7
8
9
10
11
12
13
14
SAR Sequence
(Resolution Dependent Length: SRES[2:0])
"Final"
Sample Time
(N - 2 cycles)
Sample CAP hold phase
ADC_CLK
Figure 10-28. Sampling and Conversion Timing Example (8-bit Resolution, 4 Cycle Sampling)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
396
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Please note that there is always a pump phase of two ADC_CLK cycles before the sample phase begins,
hence glitches during the pump phase could impact the conversion accuracy for short sample times.
10.5.3
Digital Sub-Block
The digital sub-block contains a list-based programmer’s model and the control logic for the analog subblock circuits.
10.5.3.1
Analog-to-Digital (A/D) Machine
The A/D machine performs the analog-to-digital conversion. The resolution is program selectable to be
either 8- or 10- or 12 bits. The A/D machine uses a successive approximation architecture. It functions by
comparing the sampled and stored analog voltage with a series of binary coded discrete voltages.
By following a binary search algorithm, the A/D machine identifies the discrete voltage that is nearest to
the sampled and stored voltage.
Only analog input signals within the potential range of VRL_0/1 to VRH_0/1 (A/D reference potentials)
will result in a non-railed digital output code.
10.5.3.2
Introduction of the Programmer’s Model
The ADC_LBA provides a programmer’s model that uses a system memory list-based architecture for
definition of the conversion command sequence and conversion result handling.
The Command Sequence List (CSL) and Result Value List (RVL) are implemented in double buffered
manner and the buffer mode is user selectable for each list (bits CSL_BMOD, RVL_BMOD). The 32-bit
wide conversion command is double buffered and the currently active command is visible in the ADC
register map at ADCCMD register space.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
397
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5.3.2.1
Introduction of The Command Sequence List (CSL) Format
A Command Sequence List (CSL) contains up to 64 conversion commands. A user selectable number of
successive conversion commands in the CSL can be grouped as a command sequence. This sequence of
conversion commands is successively executed by the ADC at the occurrence of a Trigger Event. The
commands of a sequence are successively executed until an “End Of Sequence” or “End Of List”
command type identifier in a command is detected (command type is coded via bits CMD_SEL[1:0]). The
number of successive conversion commands that belong to a command sequence and the number of
command sequences inside the CSL can be freely defined by the user and is limited by the 64 conversion
commands a CSL can contain. A CSL must contain at least one conversion command and one “end of list”
command type identifier. The minimum number of command sequences inside a CSL is zero and the
maximum number of command sequences is 63. A command sequence is defined with bits
CMD_SEL[1:0] in the register ADCCMD_M by defining the end of a conversion sequence. The
Figure 10-29 and Figure 10-30 provides examples of a CSL.
CSL_0/1
Waiting for trigger
to proceed
Waiting for trigger
to proceed
Command_1
normal conversion
Command_2
normal conversion
Command_3
normal conversion
Command_4
normal conversion
Command_5
normal conversion
Command_6
normal conversion
Command_7
Command_8
Command_9
Waiting for trigger
to proceed
Wait for RSTA or
LDOK+RSTA
Command Coding Information
Command_10
Command_11
End Of Sequence
normal conversion
normal conversion
End Of Sequence
normal conversion
Command_12
normal conversion
Command_13
End Of List
}
}
}
done by bits
Sequence_1
Sequence_2
Sequence_3
CMD_SEL[1:0]
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
1
0
0
0
0
1
1
Figure 10-29. Example CSL with sequences and an “End Of List” command type identifier
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
398
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Initial trigger
only
CSL_0
Command coding information
Command_1
normal conversion
Command_2
normal conversion
Command_3
normal conversion
Command_4
normal conversion
Command_5
normal conversion
Command_6
normal conversion
Command_7
normal conversion
Command_8
normal conversion
Command_9
normal conversion
Command_10
normal conversion
Command_11
normal conversion
Command_12
normal conversion
Command_13
done by bits
}
End Of List, wrap to top, continue
continuous
conversion
CMD_SEL[1:0]
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
Figure 10-30. Example CSL for continues conversion
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
399
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5.3.2.2
Introduction of the two Command Sequence Lists (CSLs)
The two Command Sequence Lists (CSLs) can be referred to via the Command Base Pointer Register plus
the Command and Result Offset Registers plus the Command Index Register (ADCCBP,
ADCCROFF_0/1, ADCCIDX).
The final address for conversion command loading is calculated by the sum of these registers (e.g.:
ADCCBP+ADCCROFF_0+ADCCIDX or ADCCBP+ADCCROFF_1+ADCCIDX).
Bit CSL_BMOD selects if the CSL is used in double buffer or single buffer mode. In double buffer mode,
the CSL can be swapped by flow control bits LDOK and RSTA. For detailed information about when and
how the CSL is swapped, please refer to Section 10.5.3.2.5, “The four ADC conversion flow control bits
- description of Restart Event + CSL Swap, Section 10.8.7.1, “Initial Start of a Command Sequence List
and Section 10.8.7.3, “Restart CSL execution with new/other CSL (alternative CSL becomes active CSL)
— CSL swapping
Which list is actively used for ADC command loading is indicated by bit CSL_SEL. The register to define
the CSL start addresses (ADCCBP) can be set to any even location of the system RAM or NVM area. It
is the user’s responsibility to make sure that the different ADC lists do not overlap or exceed the system
RAM or the NVM area, respectively. The error flag IA_EIF will be set for accesses to ranges outside
system RAM area and cause an error interrupt if enabled.
Scenario with: CSL_SEL = 1’b0
0x00_0000
Scenario with: CSL_SEL = 1’b1
Memory Map
Register Space
RAM or NVM start address
0x00_0000
CSL_0 (active)
ADCCBP+(ADCCROFF_0+
ADCCIDX(max))
ADCCBP+(ADCCROFF_1)
ADCCBP+(ADCCROFF_1+
ADCCIDX(max))
RAM or NVM end address
Register Space
RAM / NVM start address
RAM or NVM Space
ADCCBP+(ADCCROFF_0)
Memory Map
RAM or NVM Space
ADCCBP+(ADCCROFF_0)
CSL_0 (alternative)
ADCCBP+(ADCCROFF_0+
ADCCIDX(max))
CSL_1 (alternative)
ADCCBP+(ADCCROFF_1)
ADCCMDP+(ADCCROFF_1+
ADCCIDX(max))
CSL_1 (active)
RAM or NVM end address
Note: Address register names in () are not absolute addresses instead they are a sample offset or sample index
Figure 10-31. Command Sequence List Schema in Double Buffer Mode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
400
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
CSL_SEL = 1’b0 (forced by CSL_BMOD)
0x00_0000
Memory Map
Register Space
RAM or NVM start address
RAM or NVM Space
ADCCBP+(ADCCROFF_0)
CSL_0 (active)
ADCCBP+(ADCCROFF_0+
ADCCIDX(max))
RAM or NVM end address
Note: Address register names in () are not absolute addresses instead they are a sample offset or sample index
Figure 10-32. Command Sequence List Schema in Single Buffer Mode
While the ADC is enabled, one CSL is active (indicated by bit CSL_SEL) and the corresponding list
should not be modified anymore. At the same time the alternative CSL can be modified to prepare the ADC
for new conversion sequences in CSL double buffered mode. When the ADC is enabled, the command
address registers (ADCCBP, ADCCROFF_0/2, ADCCIDX) are read only and register ADCCIDX is under
control of the ADC.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
401
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5.3.2.3
Introduction of the two Result Value Lists (RVLs)
The same list-based architecture as described above for the CSL has been implemented for the Result
Value List (RVL) with corresponding address registers (ADCRBP, ADCCROFF_0/1, ADCRIDX).
The final address for conversion result storage is calculated by the sum of these registers (e.g.:
ADCRBP+ADCCROFF_0+ADCRIDX or ADCRBP+ADCCROFF_1+ADCRIDX).
The RVL_BMOD bit selects if the RVL is used in double buffer or single buffer mode. In double buffer
mode the RVL is swapped:
• Each time an “End Of List” command type got executed followed by the first conversion from top
of the next CSL and related (first) result is about to be stored
• A CSL got aborted (bit SEQA=1’b1) and ADC enters idle state (becomes ready for new flow
control events)
Using the RVL in double buffer mode the RVL is not swapped after exit from Stop Mode or Wait Mode
with bit SWAI set. Hence the RVL used before entry of Stop or Wait Mode with bit SWAI set is overwritten
after exit from the MCU Operating Mode (see also Section 10.2.1.2, “MCU Operating Modes).
Which list is actively used for the ADC conversion result storage is indicated by bit RVL_SEL. The
register to define the RVL start addresses (ADCRBP) can be set to any even location of the system RAM
area. It is the user’s responsibility to make sure that the different ADC lists do not overlap or exceed the
system RAM area. The error flag IA_EIF will be set for accesses to ranges outside system RAM area and
cause an error interrupt if enabled.
Scenario with: RVL_SEL = 1’b0
0x00_0000
Scenario with: RVL_SEL = 1’b1
Memory Map
Register Space
RAM start address
0x00_0000
RVL_0 (active)
ADCRBP+(ADCCROFF_0+
ADCRIDX(max))
ADCRBP+(ADCCROFF_1)
ADCRBP+(ADCCROFF_1+
ADCRIDX(max))
RAM end address
Register Space
RAM start address
RAM Space
ADCRBP+(ADCCROFF_0)
Memory Map
RAM Space
ADCRBP+(ADCCROFF_0)
RVL_0 (alternative)
ADCRBP+(ADCCROFF_0+
ADCRIDX(max))
RVL_1 (alternative)
ADCRBP+(ADCCROFF_1)
ADCRBP+(ADCCROFF_1+
ADCRIDX(max))
RVL_1 (active)
RAM end address
Note: Address register names in () are not absolute addresses instead they are a sample offset or sample index
Figure 10-33. Result Value List Schema in Double Buffer Mode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
402
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
RVL_SEL = 1’b0 (forced by bit RVL_BMOD)
Memory Map
0x00_0000
Register Space
RAM start address
RAM Space
ADCRBP+(ADCCROFF_0)
RVL_0 (active)
ADCRBP+(ADCCROFF_0+
ADCRIDX(max))
RAM end address
Note: Address register names in () are not absolute addresses instead they are a sample offset or sample index
Figure 10-34. Result Value List Schema in Single Buffer Mode
While ADC is enabled, one Result Value List is active (indicated by bit RVL_SEL). The conversion Result
Value List can be read anytime. When the ADC is enabled the conversion result address registers
(ADCRBP, ADCCROFF_0/1, ADCRIDX) are read only and register ADCRIDX is under control of the
ADC.
A conversion result is always stored as 16bit entity in unsigned data representation. Left and right
justification inside the entity is selected via the DJM control bit. Unused bits inside an entity are stored
zero.
Table 10-32. Conversion Result Justification Overview
Conversion Resolution
Left Justified Result
Right Justified Result
(SRES[1:0])
(DJM = 1’b0)
(DJM = 1’b1)
8 bit
{Result[7:0],8’b00000000}
{8’b00000000,Result[7:0]}
10 bit
{Result[9:0],6’b000000}
{6’b000000,Result[9:0]}
12 bit
{Result[11:0],4’b0000}
{4’b0000,Result[11:0]}
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
403
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5.3.2.4
The two conversion flow control Mode Configurations
The ADC provides two modes (“Trigger Mode” and “Restart Mode”) which are different in the conversion
control flow. The “Restart Mode” provides precise timing control about the sample start point but is more
complex from the flow control perspective, while the “Trigger Mode” is more simple from flow control
point of view but is less controllable regarding conversion sample start.
Following are the key differences:
In “Trigger Mode” configuration, when conversion flow control bit RSTA gets set the bit TRIG gets set
automatically. Hence in “Trigger Mode” the applications should not set the bit TRIG and bit RSTA
simultaneously (via data bus or internal interface), because it is a flow control failure and the ADC will
cease operation.
In “Trigger Mode” configuration, after the execution of the initial Restart Event the current CSL can be
executed and controlled via Trigger Events only. Hence, if the “End Of List” command is reached a restart
of conversion flow from top of current CSL does not require to set bit RSTA because returning to the top
of current CSL is done automatically. Therefore the current CSL can be executed again after the “End Of
List” command type is executed by a Trigger Event only.
In “Restart Mode” configuration, the execution of a CSL is controlled via Trigger Events and Restart
Events. After execution of the “End Of List” command the conversion flow must be continued by a Restart
Event followed by a Trigger Event and the Trigger Event must not occur before the Restart Event has
finished.
For more details and examples regarding flow control and application use cases please see following
section and Section 10.8.7, “Conversion flow control application information.
10.5.3.2.5
The four ADC conversion flow control bits
There are four bits to control conversion flow (execution of a CSL and CSL exchange in double buffer
mode). Each bit is controllable via the data bus and internal interface depending on the setting of
ACC_CFG[1:0] bits (see also Figure 10-2). In the following the conversion control event to control the
conversion flow is given with the related internal interface signal and corresponding register bit name
together with information regarding:
— Function of the conversion control event
— How to request the event
— When is the event finished
— Mandatory requirements to executed the event
A summary of all event combinations is provided by Table 10-10.
•
Trigger Event
Internal Interface Signal: Trigger
Corresponding Bit Name: TRIG
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
404
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
– Function:
Start the first conversion of a conversion sequence which is defined in the active Command
Sequence List
– Requested by:
- Positive edge of internal interface signal Trigger
- Write Access via data bus to set control bit TRIG
– When finished:
This bit is cleared by the ADC when the first conversion of the sequence is beginning to
sample
– Mandatory Requirements:
- In all ADC conversion flow control modes bit TRIG is only set (Trigger Event executed)
if the Trigger Event occurs while no conversion or conversion sequence is ongoing (ADC
idle)
- In ADC conversion flow control mode “Restart Mode” with a Restart Event in progress it
is not allowed that a Trigger Event occurs before the background command load phase has
finished (Restart Event has been executed) else the error flag TRIG_EIF is set
- In ADC conversion flow control mode “Trigger Mode” a Restart Event causes bit TRIG
being set automatically. Bit TRIG is set when no conversion or conversion sequence is
ongoing (ADC idle) and the RVL done condition is reached by one of the following:
* A “End Of List” command type has been executed
* A Sequence Abort Event is in progress or has been executed
The ADC executes the Restart Event followed by the Trigger Event.
- In ADC conversion flow control mode “Trigger Mode” a Restart Event and a simultaneous
Trigger Event via internal interface or data bus causes the TRIG_EIF bit being set and ADC
cease operation.
•
Restart Event (with current active CSL)
Internal Interface Signal: Restart
Corresponding Bit Name: RSTA
– Function:
- Go to top of active CSL (clear index register for CSL)
- Load one background command register and wait for Trigger (CSL offset register is not
switched independent of bit CSL_BMOD)
- Set error flag RSTA_EIF when a Restart Request occurs before one of the following
conditions was reached:
* The "End Of List" command type has been executed
* Depending on bit STR_SEQA if the "End Of List" command type is about to be executed
* The current CSL has been aborted or is about to be aborted due to a Sequence Abort
Request.
– Requested by:
- Positive edge of internal interface signal Restart
- Write Access via data bus to set control bit RSTA
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
405
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
– When finished:
This bit is cleared when the first conversion command of the sequence from top of active
Sequence Command List is loaded
– Mandatory Requirement:
- In all ADC conversion flow control modes a Restart Event causes bit RSTA to be set. Bit
SEQA is set simultaneously by ADC hardware if:
* ADC not idle (a conversion or conversion sequence is ongoing and current CSL not
finished) and no Sequence Abort Event in progress (bit SEQA not already set or set
simultaneously via internal interface or data bus)
* ADC idle but RVL done condition not reached
The RVL done condition is reached by one of the following:
* A “End Of List” command type has been executed
* A Sequence Abort Event is in progress or has been executed (bit SEQA already set or set
simultaneously via internal interface or data bus)
The ADC executes the Sequence Abort Event followed by the Restart Event for the
conditions described before or only a Restart Event.
- In ADC conversion flow control mode “Trigger Mode” a Restart Event causes bit TRIG
being set automatically. Bit TRIG is set when no conversion or conversion sequence is
ongoing (ADC idle) and the RVL done condition is reached by one of the following:
* A “End Of List” command type has been executed
* A Sequence Abort Event is in progress or has been executed
The ADC executes the Restart Event followed by the Trigger Event.
- In ADC conversion flow control mode “Trigger Mode” a Restart Event and a simultaneous
Trigger Event via internal interface or data bus causes the TRIG_EIF bit being set and ADC
cease operation.
•
Restart Event + CSL Exchange (Swap)
Internal Interface Signals: Restart + LoadOK
Corresponding Bit Names: RSTA + LDOK
– Function:
Go to top of active CSL (clear index register for CSL) and switch to other offset register for
address calculation if configured for double buffer mode (exchange the CSL list)
Requested by:
- Internal interface with the assertion of Interface Signal Restart the interface Signal
LoadOK is evaluated and bit LDOK is set accordingly (bit LDOK set if Interface Signal
LoadOK asserted when Interface Signal Restart asserts).
- Write Access via data bus to set control bit RSTA simultaneously with bit LDOK.
– When finished:
Bit LDOK can only be cleared if it was set as described before and both bits (LDOK, RSTA)
are cleared when the first conversion command from top of active Sequence Command List
is loaded
– Mandatory Requirement:
No ongoing conversion or conversion sequence
Details if using the internal interface:
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
406
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
If signal Restart is asserted before signal LoadOK is set the conversion starts from top of
currently active CSL at the next Trigger Event (no exchange of CSL list).
If signal Restart is asserted after or simultaneously with signal LoadOK the conversion starts
from top of the other CSL at the next Trigger Event (CSL is switched) if CSL is configured
for double buffer mode.
•
Sequence Abort Event
Internal Interface Signal: Seq_Abort
Corresponding Bit Name: SEQA
– Function:
Abort any possible ongoing conversion at next conversion boundary and abort current
conversion sequence and active CSL
– Requested by:
- Positive edge of internal interface signal Seq_Abort
- Write Access via data bus to set control bit SEQA
– When finished:
This bit gets cleared when an ongoing conversion is finished and the result is stored and/or
an ongoing conversion sequence is aborted and current active CSL is aborted (ADC idle,
RVL done)
– Mandatory Requirement:
- In all ADC conversion flow control modes bit SEQA can only be set if:
* ADC not idle (a conversion or conversion sequence is ongoing)
* ADC idle but RVL done condition not reached
The RVL done condition is not reached if:
* An “End Of List” command type has not been executed
* A Sequence Abort Event has not been executed (bit SEQA not already set)
- In all ADC conversion flow control modes a Sequence Abort Event can be issued at any
time
- In ADC conversion flow control mode “Restart Mode” after a conversion sequence abort
request has been executed it is mandatory to set bit RSTA. If a Trigger Event occurs before
a Restart Event is executed (bit RSTA set and cleared by hardware), bit TRIG is set, error
flag TRIG_EIF is set, and the ADC can only be continued by a Soft-Reset. After the Restart
Event the ADC accepts new Trigger Events (bit TRIG set) and begins conversion from top
of the currently active CSL.
- In ADC conversion flow control mode “Restart Mode” after a Sequence Abort Event has
been executed, a Restart Event causes only the RSTA bit being set. The ADC executes a
Restart Event only.
– In both conversion flow control modes (“Restart Mode” and “Trigger Mode”) when
conversion flow control bit RSTA gets set automatically bit SEQA gets set when the ADC
has not reached one of the following scenarios:
* An “End Of List” command type has been executed or is about to be executed
* A Sequence Abort request is about to be executed or has been executed.
In case bit SEQA is set automatically the Restart error flag RSTA_EIF is set to indicate an
unexpected Restart Request.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
407
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5.3.2.6
Conversion flow control in case of conversion sequence control bit overrun
scenarios
Restart Request Overrun:
If a legal Restart Request is detected and no Restart Event is in progress, the RSTA bit is set due to the
request. The set RSTA bit indicates that a Restart Request was detected and the Restart Event is in process.
In case further Restart Requests occur while the RSTA bit is set, this is defined a overrun situation. This
scenario is likely to occur when bit STR_SEQA is set or when a Restart Event causes a Sequence Abort
Event. The request overrun is captured in a background register that always stores the last detected overrun
request. Hence if the overrun situation occurs more than once while a Restart Event is in progress, only the
latest overrun request is pending. When the RSTA bit is cleared, the latest overrun request is processed and
RSTA is set again one cycle later.
LoadOK Overrun:
Simultaneously at any Restart Request overrun situation the LoadOK input is evaluated and the status is
captured in a background register which is alternated anytime a Restart Request Overrun occurs while
Load OK Request is asserted. The Load OK background register is cleared as soon as the pending Restart
Request gets processed.
Trigger Overrun:
If a Trigger occurs whilst bit TRIG is already set, this is defined as a Trigger overrun situation and causes
the ADC to cease conversion at the next conversion boundary and to set bit TRIG_EIF. A overrun is also
detected if the Trigger Event occurs automatically generated by hardware in “Trigger Mode” due to a
Restart Event and simultaneously a Trigger Event is generated via data bus or internal interface. In this
case the ADC ceases operation before conversion begins to sample. In “Trigger Mode” a Restart Request
Overrun does not cause a Trigger Overrun (bit TRIG_EIF not set).
Sequence Abort Request Overrun:
If a Sequence Abort Request occurs whilst bit SEQA is already set, this is defined as a Sequence Abort
Request Overrun situation and the overrun request is ignored.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
408
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.5.3.3
ADC List Usage and Conversion/Conversion Sequence Flow
Description
It is the user’s responsibility to make sure that the different lists do not overlap or exceed the system RAM
area respectively the CSL does not exceed the NVM area if located in the NVM. The error flag IA_EIF
will be set for accesses done outside the system RAM area and will cause an error interrupt if enabled for
lists that are located in the system RAM.
Generic flow for ADC register load at conversion sequence start/restart:
• It is mandatory that the ADC is idle (no ongoing conversion or conversion sequence).
• It is mandatory to have at least one CSL with valid entries. See also Section 10.8.7.2, “Restart CSL
execution with currently active CSL or Section 10.8.7.3, “Restart CSL execution with new/other
CSL (alternative CSL becomes active CSL) — CSL swapping for more details on possible
scenarios.
• A Restart Event occurs, which causes the index registers to be cleared (register ADCCIDX and
ADCRIDX are cleared) and to point to the top of the corresponding lists (top of active RVL and
CSL).
• Load conversion command to background conversion command register 1.
• The control bit(s) RSTA (and LDOK if set) are cleared.
• Wait for Trigger Event to start conversion.
Generic flow for ADC register load during conversion:
• The index registers ADCCIDX is incremented.
• The inactive background command register is loaded with a new conversion command.
Generic flow for ADC result storage at end of conversion:
• Index register ADCRIDX is incremented and the conversion result is stored in system RAM. As
soon as the result is successfully stored, any conversion interrupt flags are set accordingly.
• At the conversion boundary the other background command register becomes active and visible in
the ADC register map.
• If the last executed conversion command was of type “End Of Sequence”, the ADC waits for the
Trigger Event.
• If the last executed conversion command was of type “End Of List” and the ADC is configured in
“Restart Mode”, the ADC sets all related flags and stays idle awaiting a Restart Event to continue.
• If the last executed conversion command was of type “End Of List” and the ADC is configured in
“Trigger Mode”, the ADC sets all related flags and automatically returns to top of current CSL and
is awaiting a Trigger Event to continue.
• If the last executed conversion command was of type “Normal Conversion” the ADC continues
command execution in the order of the current CSL (continues conversion).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
409
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.6
Resets
At reset the ADC12B_LBA is disabled and in a power down state. The reset state of each individual bit is
listed within Section 10.4.2, “Register Descriptions” which details the registers and their bit-fields.
10.7
Interrupts
The ADC supports three types of interrupts:
• Conversion Interrupt
• Sequence Abort Interrupt
• Error and Conversion Flow Control Issue Interrupt
Each of the interrupt types is associated with individual interrupt enable bits and interrupt flags.
10.7.1
ADC Conversion Interrupt
The ADC provides one conversion interrupt associated to 16 interrupt enable bits with dedicated interrupt
flags. The 16 interrupt flags consist of:
• 15 conversion interrupt flags which can be associated to any conversion completion.
• One additional interrupt flag which is fixed to the “End Of List” conversion command type within
the active CSL.
The association of the conversion number with the interrupt flag number is done in the conversion
command.
10.7.2
ADC Sequence Abort Done Interrupt
The ADC provides one sequence abort done interrupt associated with the sequence abort request for
conversion flow control. Hence, there is only one dedicated interrupt flag and interrupt enable bit for
conversion sequence abort and it occurs when the sequence abort is done.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
410
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.7.3
ADC Error and Conversion Flow Control Issue Interrupt
The ADC provides one error interrupt for four error classes related to conversion interrupt overflow,
command validness, DMA access status and Conversion Flow Control issues, and CSL failure. The
following error interrupt flags belong to the group of severe issues which cause an error interrupt if enabled
and cease ADC operation:
• IA_EIF
• CMD_EIF
• EOL_EIF
• TRIG_EIF
In order to make the ADC operational again, an ADC Soft-Reset must be issued which clears the above
listed error interrupt flags.
NOTE
It is important to note that if flag DBECC_ERR is set, the ADC ceases
operation as well, but does not cause an ADC error interrupt. Instead, a
machine exception is issued. In order to make the ADC operational again an
ADC Soft-Reset must be issued.
Remaining error interrupt flags cause an error interrupt if enabled, but ADC continues operation. The
related interrupt flags are:
• RSTAR_EIF
• LDOK_EIF
• CONIF_OIF
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
411
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.8
10.8.1
Use Cases and Application Information
List Usage — CSL single buffer mode and RVL single buffer mode
In this use case both list types are configured for single buffer mode (CSL_BMOD=1’b0 and
RVL_BMOD=1’b0, CSL_SEL and RVL_SEL are forced to 1’b0). The index register for the CSL and RVL
are cleared to start from the top of the list with next conversion command and result storage in the
following cases:
• The conversion flow reaches the command containing the “End-of-List” command type identifier
• A Restart Request occurs at a sequence boundary
• After an aborted conversion or conversion sequence
CSL_0
RVL_0
CSL_1
(unused)
RVL_1
(unused)
Figure 10-35. CSL Single Buffer Mode — RVL Single Buffer Mode Diagram
10.8.2
List Usage — CSL single buffer mode and RVL double buffer mode
In this use case the CSL is configured for single buffer mode (CSL_BMOD=1’b0) and the RVL is
configured for double buffer mode (RVL_BMOD=1’b1). In this buffer configuration only the result list
RVL is switched when the first conversion result of a CSL is stored after a CSL was successfully finished
or a CSL got aborted.
CSL_0
RVL_0
CSL_1
(unused)
RVL_1
Figure 10-36. CSL Single Buffer Mode — RVL Single Buffer Mode Diagram
The last entirely filled RVL (an RVL where the corresponding CSL has been executed including the “End
Of List “ command type) is shown by register ADCEOLRI.
The CSL is used in single buffer mode and bit CSL_SEL is forced to 1’b0.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
412
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.8.3
List Usage — CSL double buffer mode and RVL double buffer mode
In this use case both list types are configured for double buffer mode (CSL_BMOD=1’b1 and
RVL_BMOD=1’b1) and whenever a Command Sequence List (CSL) is finished or aborted the command
Sequence List is swapped by the simultaneous assertion of bits LDOK and RSTA.
CSL_0
RVL_0
CSL_1
RVL_1
Figure 10-37. CSL Double Buffer Mode — RVL Double Buffer Mode Diagram
This use case can be used if the channel order or CSL length varies very frequently in an application.
10.8.4
List Usage — CSL double buffer mode and RVL single buffer mode
In this use case the CSL is configured for double buffer mode (CSL_BMOD=1’b1) and the RVL is
configured for single buffer mode (RVL_BMOD=1’b0).
The two command lists can be different sizes and the allocated result list memory area in the RAM must
be able to hold as many entries as the larger of the two command lists. Each time when the end of a
Command Sequence List is reached, if bits LDOK and RSTA are set, the commands list is swapped.
CSL_0
RVL_0
CSL_1
RVL_1
(unused)
Figure 10-38. CSL Double Buffer Mode — RVL Single Buffer Mode Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
413
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.8.5
List Usage — CSL double buffer mode and RVL double buffer mode
In this use case both list types are configured for double buffer mode (CSL_BMOD=1’b1) and
RVL_BMOD=1’b1).
This setup is the same as Section 10.8.3, “List Usage — CSL double buffer mode and RVL double buffer
mode but at the end of a CSL the CSL is not always swapped (bit LDOK not always set with bit RSTA).
The Result Value List is swapped whenever a CSL is finished or a CSL got aborted.
CSL_0
RVL_0
CSL_1
RVL_1
Figure 10-39. CSL Double Buffer Mode — RVL Double Buffer Mode Diagram
10.8.6
RVL swapping in RVL double buffer mode and related registers
ADCIMDRI and ADCEOLRI
When using the RVL in double buffer mode, the registers ADCIMDRI and ADCEOLRI can be used by
the application software to identify which RVL holds relevant and latest data and which CSL is related to
this data. These registers are updated at the setting of one of the CON_IF[15:1] or the EOL_IF interrupt
flags. As described in the register description Section 10.4.2.13, “ADC Intermediate Result Information
Register (ADCIMDRI) and Section 10.4.2.14, “ADC End Of List Result Information Register
(ADCEOLRI), the register ADCIMDRI, for instance, is always updated at the occurrence of a
CON_IF[15:1] interrupt flag amongst other cases. Also each time the last conversion command of a CSL
is finished and the corresponding result is stored, the related EOL_IF flag is set and register ADCEOLRI
is updated. Hence application software can pick up conversion results, or groups of results, or an entire
result list driven fully by interrupts. A use case example diagram is shown in Figure 10-40.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
414
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
CSL Buffer
Wake-up
Event with
AUT_RSTA= 1’b1
Stop Mode request
while conversion
ongoing and before EOL
Initial
Restart
Event
CSL_0
CSL_1
INT_1
EOL
CSL_0
INT_2 EOL
Stop Mode
entry
tdelay
INT_1
return to execute
from top of CSL
RVL swap
due to EOL
followed by
first result of
next CSL to store
RVL_0
RVL Buffer
CSL_0
RVL_0
RVL_1
bits not valid
until first EOL
RVL values before Stop Mode
entry are overwritten
bits are valid
RVL_EOL
1’b0
1’b1
CSL_EOL
1’b0
1’b1
EOL_IF
1’b1
set by
hardware
bits not valid
until first INT
no RVL
swap
1’b1
cleared by
software
before next EOL
should be cleared by software
before Stop Mode entry
bits are valid
RVL_IMD
1’b0
1’b1
1’b0
CSL_IMD
1’b0
1’b1
1’b0
RIDX_IMD[5:0]
CON_IF[15:1]
0x00
0x05
0x0000 0x0001
0x0A
0x0000
0x08
0x0B
0x0010
0x05
0x0001
Flag should be cleared by
software before it is set again
t
Comments:
EOL:
”End Of List” command type processed
INT_x: One of the CON_IF interrupt flags occurs
tdelay:
Delay can vary depending on the DMA performance, and ADC configuration (conversion
flow using the Trigger to proceed through the CSL)
Figure 10-40. RVL Swapping — Use Case Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
415
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.8.7
Conversion flow control application information
The ADC12B_LBA provides various conversion control scenarios to the user accomplished by the
following features.
The ADC conversion flow control can be realized via the data bus only, the internal interface only, or by
both access methods. The method used is software configurable via bits ACC_CFG[1:0].
The conversion flow is controlled via the four conversion flow control bits: SEQA, TRIG, RSTA, and
LDOK.
Two different conversion flow control modes can be configured: Trigger Mode or Restart Mode
Single or double buffer configuration of CSL and RVL.
10.8.7.1
Initial Start of a Command Sequence List
At the initial start of a Command Sequence List after device reset all entries for at least one of the two CSL
must have been completed and data must be valid. Depending on if the CSL_0 or the CSL_1 should be
executed at the initial start of a Command Sequence List the following conversion control sequence must
be applied:
If CSL_0 should be executed at the initial conversion start after device reset:
A Restart Event and a Trigger Event must occur (depending to the selected conversion flow control mode
the events must occur one after the other or simultaneously) which causes the ADC to start conversion with
commands loaded from CSL_0.
If CSL_1 should be executed at the initial conversion start after device reset:
Bit LDOK must be set simultaneously with the Restart Event followed by a Trigger Event (depending on
the selected conversion flow control mode the Trigger events must occur simultaneously or after the
Restart Event is finished). As soon as the Trigger Event gets executed the ADC starts conversion with
commands loaded from CSL_1.
As soon as a new valid Restart Event occurs the flow for ADC register load at conversion sequence start
as described in Section 10.5.3.3, “ADC List Usage and Conversion/Conversion Sequence Flow
Description applies.
10.8.7.2
Restart CSL execution with currently active CSL
To restart a Command Sequence List execution it is mandatory that the ADC is idle (no conversion or
conversion sequence is ongoing).
If necessary, a possible ongoing conversion sequence can be aborted by the Sequence Abort Event (setting
bit SEQA). As soon as bit SEQA is cleared by the ADC, the current conversion sequence has been aborted
and the ADC is idle (no conversion sequence or conversion ongoing).
After a conversion sequence abort is executed it is mandatory to request a Restart Event (bit RSTA set).
After the Restart Event is finished (bit RSTA is cleared), the ADC accepts a new Trigger Event (bit TRIG
can be set) and begins conversion from the top of the currently active CSL. In conversion flow control
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
416
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
mode “Trigger Mode” only a Restart Event is necessary if ADC is idle to restart Conversion Sequence List
execution (the Trigger Event occurs automatically).
It is possible to set bit RSTA and SEQA simultaneously, causing a Sequence Abort Event followed by a
Restart Event. In this case the error flags behave differently depending on the selected conversion flow
control mode:
• Setting both flow control bits simultaneously in conversion flow control mode “Restart Mode”
prevents the error flags RSTA_EIF and LDOK_EIF from occurring.
• Setting both flow control bits simultaneously in conversion flow control mode “Trigger Mode”
prevents the error flag RSTA_EIF from occurring.
If only a Restart Event occurs while ADC is not idle and bit SEQA is not set already (Sequence Abort
Event in progress) a Sequence Abort Event is issued automatically and bit RSTAR_EIF is set.
Please see also the detailed conversion flow control bit mandatory requirements and execution information
for bit RSTA and SEQA described in Section 10.5.3.2.5, “The four ADC conversion flow control bits.
10.8.7.3
Restart CSL execution with new/other CSL (alternative CSL becomes
active CSL) — CSL swapping
After all alternative conversion command list entries are finished the bit LDOK can be set simultaneously
with the next Restart Event to swap command buffers.
To start conversion command list execution it is mandatory that the ADC is idle (no conversion or
conversion sequence is ongoing).
If necessary, a possible ongoing conversion sequence can be aborted by the Sequence Abort Event (setting
bit SEQA). As soon as bit SEQA is cleared by the ADC, the current conversion sequence has been aborted
and the ADC is idle (no conversion sequence or conversion ongoing).
After a conversion sequence abort is executed it is mandatory to request a Restart Event (bit RSTA set) and
simultaneously set bit LDOK to swap the CSL buffer. After the Restart Event is finished (bit RSTA and
LDOK are cleared), the ADC accepts a new Trigger Event (bit TRIG can be set) and begins conversion
from the top of the newly selected CSL buffer. In conversion flow control mode “Trigger Mode” only a
Restart Event (simultaneously with bit LDOK being set) is necessary to restart conversion command list
execution with the newly selected CSL buffer (the Trigger Event occurs automatically).
It is possible to set bits RSTA, LDOK and SEQA simultaneously, causing a Sequence Abort Event
followed by a Restart Event. In this case the error flags behave differently depending on the selected
conversion flow control mode:
• Setting these three flow control bits simultaneously in “Restart Mode” prevents the error flags
RSTA_EIF and LDOK_EIF from occurring.
• Setting these three flow control bits simultaneously in “Trigger Mode” prevents the error flag
RSTA_EIF from occurring.
If only a Restart Event occurs while ADC is not idle and bit SEQA is not set already (Sequence Abort
Event in progress) a Sequence Abort Event is issued automatically and bit RSTAR_EIF is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
417
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
Please see also the detailed conversion flow control bit mandatory requirements and execution information
for bit RSTA and SEQA described in Section 10.5.3.2.5, “The four ADC conversion flow control bits.
10.8.8
Continuous Conversion
Applications that only need to continuously convert a list of channels, without the need for timing control
or the ability to perform different sequences of conversions (grouped number of different channels to
convert) can make use of the following simple setup:
• “Trigger Mode” configuration
• Single buffer CSL
• Depending on data transfer rate either use single or double buffer RVL configuration
• Define a list of conversion commands which only contains the “End Of List” command with
automatic wrap to top of CSL
After finishing the configuration and enabling the ADC an initial Restart Event is sufficient to launch the
continuous conversion until next device reset or low power mode.
In case a Low Power Mode is used:
If bit AUT_RSTA is set before Low Power Mode is entered the conversion continues automatically as soon
as a low power mode (Stop Mode or Wait Mode with bit SWAI set) is exited.
Initial
Restart
Event
Wake-up
Stop Mode request,
Automatic Sequence Abort Event with
AUT_RSTA
Event
AN3 AN1 AN4 IN5 AN3 AN1 AN4 IN5 AN3 AN1
EOL
EOL
AN3 AN1 AN4
Stop Mode
entry
Abort
CSL_0
Active
Idle
Idle
Active
t
Figure 10-41. Conversion Flow Control Diagram — Continuous Conversion (with Stop Mode)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
418
Freescale Semiconductor
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.8.9
Triggered Conversion — Single CSL
Applications that require the conversion of one or more groups of different channels in a periodic and
timed manner can make use of a configuration in “Trigger Mode” with a single CSL containing a list of
sequences. This means the CSL consists of several sequences each separated by an “End of Sequence”
command. The last command of the CSL uses the “End Of List” command with wrap to top of CSL and
waiting for a Trigger (CMD_SEL[1:0] =2’b11). Hence after the initial Restart Event each sequence can be
launched via a Trigger Event and repetition of the CSL can be launched via a Trigger after execution of
the “End Of List” command.
Initial
Restart
Event
Trigger
AN3 AN1 AN4 IN5
Trigger
Trigger
AN2 AN0 AN4 IN3
AN6 AN1 IN1
Sequence_1
Sequence_2
Sequence_0
EOS
EOS
Repetition of CSL_0
AN3 AN1 AN4
Sequence_0
EOL
Active
CSL_0
t
Figure 10-42. Conversion Flow Control Diagram — Triggered Conversion (CSL Repetition)
initial
Restart
Event
Trigger
Stop Mode request,
Automatic Sequence Abort
Event
Trigger
AN3 AN1 AN4 IN5 AN21AN0 AN4 IN3
Sequence_1
Sequence_0
EOS
Wake-up
Event with
AUT_RSTA
Trigger
AN3 AN1 AN4 AN5 AN2 AN0
AN6 AN1
Sequence_2
EOS
Begin from top of current CSL
Sequence_1
Sequence_0
Stop Mode
entry
EOS
Abort
Active
CSL_0
Idle
Idle
Active
t
Figure 10-43. Conversion Flow Control Diagram — Triggered Conversion (with Stop Mode)
In case a Low Power Mode is used:
If bit AUT_RSTA is set before Low Power Mode is entered, the conversion continues automatically as
soon as a low power mode (Stop Mode or Wait Mode with bit SWAI set) is exited.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
419
Chapter 10 Analog-to-Digital Converter (ADC12B_LBA_V1)
10.8.10 Fully Timing Controlled Conversion
As described previously, in “Trigger Mode” a Restart Event automatically causes a trigger. To have full
and precise timing control of the beginning of any conversion/sequence the “Restart Mode” is available.
In “Restart Mode” a Restart Event does not cause a Trigger automatically; instead, the Trigger must be
issued separately and with correct timing, which means the Trigger is not allowed before the Restart Event
(conversion command loading) is finished (bit RSTA=1’b0 again). The time required from Trigger until
sampling phase starts is given (refer to Section 10.4.2.6, “ADC Conversion Flow Control Register
(ADCFLWCTL), Timing considerations) and hence timing is fully controllable by the application.
Additionally, if a Trigger occurs before a Restart Event is finished, this causes the TRIG_EIF flag being
set. This allows detection of false flow control sequences.
any
Restart
Event Trigger
Trigger
Stop Mode request,
Automatic Sequence Abort
Event
Trigger
AN3 AN1 AN4 IN5 AN21AN0 AN4 IN3
Sequence_1
Sequence_0
EOS
conversion command
load phase
CSL_0
Wake-up
Event with
AUT_RSTA
AN6 AN1
Sequence_2
EOS
Begin from top of current CSL
Trigger
AN3 AN1 AN4 AN5 AN2 AN0
Sequence_1
Sequence_0
Stop Mode
entry
EOS
Abort
Active
Idle
Idle
Active
t
Figure 10-44. Conversion Flow Control Diagram — Fully Timing Controlled Conversion (with Stop Mode)
Unlike the Stop Mode entry shown in Figure 10-43 and Figure 10-44 it is recommended to issue the Stop
Mode at sequence boundaries (when ADC is idle and no conversion/conversion sequence is ongoing).
Any of the Conversion flow control application use cases described above (Continuous, Triggered, or Fully
Timing Controlled Conversion) can be used with CSL single buffer mode or with CSL double buffer mode.
If using CSL double buffer mode, CSL swapping is performed by issuing a Restart Event with bit LDOK
set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
420
Freescale Semiconductor
Chapter 11
Freescale’s Scalable Controller Area Network
(S12MSCANV3)
Revision History
Revision
Number
Revision Date
Sections
Affected
V03.14
12 Nov 2012
Table 11-10
V03.15
12 Jan 2013
Table 11-2
Table 11-25
Figure 11-37
11.1/11-421
11.3.2.15/11442
V03.16
08 Aug 2013
11.1
Description of Changes
• Corrected RxWRN and TxWRN threshold values
•
•
•
•
•
Updated TIME bit description
Added register names to buffer map
Updated TSRH and TSRL read conditions
Updated introduction
Updated CANTXERR and CANRXERR register notes
• Corrected typos
Introduction
Freescale’s scalable controller area network (S12MSCANV3) definition is based on the MSCAN12
definition, which is the specific implementation of the MSCAN concept targeted for the S12, S12X and
S12Z microcontroller families.
The module is a communication controller implementing the CAN 2.0A/B protocol as defined in the
Bosch specification dated September 1991. For users to fully understand the MSCAN specification, it is
recommended that the Bosch specification be read first to familiarize the reader with the terms and
concepts contained within this document.
Though not exclusively intended for automotive applications, CAN protocol is designed to meet the
specific requirements of a vehicle serial data bus: real-time processing, reliable operation in the EMI
environment of a vehicle, cost-effectiveness, and required bandwidth.
MSCAN uses an advanced buffer arrangement resulting in predictable real-time behavior and simplified
application software.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
421
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.1.1
Glossary
Table 11-1. Terminology
ACK
Acknowledge of CAN message
CAN
Controller Area Network
CRC
Cyclic Redundancy Code
EOF
End of Frame
FIFO
First-In-First-Out Memory
IFS
Inter-Frame Sequence
SOF
Start of Frame
CPU bus
CPU related read/write data bus
CAN bus
CAN protocol related serial bus
oscillator clock
11.1.2
Direct clock from external oscillator
bus clock
CPU bus related clock
CAN clock
CAN protocol related clock
Block Diagram
MSCAN
Oscillator Clock
Bus Clock
CANCLK
MUX
Presc.
Tq Clk
Receive/
Transmit
Engine
RXCAN
TXCAN
Transmit Interrupt Req.
Receive Interrupt Req.
Errors Interrupt Req.
Message
Filtering
and
Buffering
Control
and
Status
Wake-Up Interrupt Req.
Configuration
Registers
Wake-Up
Low Pass Filter
Figure 11-1. MSCAN Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
422
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.1.3
Features
The basic features of the MSCAN are as follows:
• Implementation of the CAN protocol — Version 2.0A/B
— Standard and extended data frames
— Zero to eight bytes data length
— Programmable bit rate up to 1 Mbps1
— Support for remote frames
• Five receive buffers with FIFO storage scheme
• Three transmit buffers with internal prioritization using a “local priority” concept
• Flexible maskable identifier filter supports two full-size (32-bit) extended identifier filters, or four
16-bit filters, or eight 8-bit filters
• Programmable wake-up functionality with integrated low-pass filter
• Programmable loopback mode supports self-test operation
• Programmable listen-only mode for monitoring of CAN bus
• Programmable bus-off recovery functionality
• Separate signalling and interrupt capabilities for all CAN receiver and transmitter error states
(warning, error passive, bus-off)
• Programmable MSCAN clock source either bus clock or oscillator clock
• Internal timer for time-stamping of received and transmitted messages
• Three low-power modes: sleep, power down, and MSCAN enable
• Global initialization of configuration registers
11.1.4
Modes of Operation
For a description of the specific MSCAN modes and the module operation related to the system operating
modes refer to Section 11.4.4, “Modes of Operation”.
1. Depending on the actual bit timing and the clock jitter of the PLL.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
423
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.2
External Signal Description
The MSCAN uses two external pins.
NOTE
On MCUs with an integrated CAN physical interface (transceiver) the
MSCAN interface is connected internally to the transceiver interface. In
these cases the external availability of signals TXCAN and RXCAN is
optional.
11.2.1
RXCAN — CAN Receiver Input Pin
RXCAN is the MSCAN receiver input pin.
11.2.2
TXCAN — CAN Transmitter Output Pin
TXCAN is the MSCAN transmitter output pin. The TXCAN output pin represents the logic level on the
CAN bus:
0 = Dominant state
1 = Recessive state
11.2.3
CAN System
A typical CAN system with MSCAN is shown in Figure 11-2. Each CAN station is connected physically
to the CAN bus lines through a transceiver device. The transceiver is capable of driving the large current
needed for the CAN bus and has current protection against defective CAN or defective stations.
CAN node 2
CAN node 1
CAN node n
MCU
CAN Controller
(MSCAN)
TXCAN
RXCAN
Transceiver
CANH
CANL
CAN Bus
Figure 11-2. CAN System
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
424
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3
Memory Map and Register Definition
This section provides a detailed description of all registers accessible in the MSCAN.
11.3.1
Module Memory Map
Figure 11-3 gives an overview on all registers and their individual bits in the MSCAN memory map. The
register address results from the addition of base address and address offset. The base address is
determined at the MCU level and can be found in the MCU memory map description. The address offset
is defined at the module level.
The MSCAN occupies 64 bytes in the memory space. The base address of the MSCAN module is
determined at the MCU level when the MCU is defined. The register decode map is fixed and begins at the
first address of the module address offset.
The detailed register descriptions follow in the order they appear in the register map.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
425
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Register
Name
Bit 7
0x0000
CANCTL0
R
0x0001
CANCTL1
R
W
W
0x0002
CANBTR0
R
0x0003
CANBTR1
R
0x0004
CANRFLG
R
0x0005
CANRIER
R
0x0006
CANTFLG
R
0x0007
CANTIER
0x0008
CANTARQ
W
W
W
W
R
R
CSWAI
SYNCH
3
2
1
Bit 0
TIME
WUPE
SLPRQ
INITRQ
SLPAK
INITAK
CANE
CLKSRC
LOOPB
LISTEN
BORM
WUPM
SJW1
SJW0
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0
SAMP
TSEG22
TSEG21
TSEG20
TSEG13
TSEG12
TSEG11
TSEG10
WUPIF
CSCIF
RSTAT1
RSTAT0
TSTAT1
TSTAT0
OVRIF
RXF
WUPIE
CSCIE
RSTATE1
RSTATE0
TSTATE1
TSTATE0
OVRIE
RXFIE
0
0
0
0
0
TXE2
TXE1
TXE0
0
0
0
0
0
TXEIE2
TXEIE1
TXEIE0
0
0
0
0
0
ABTRQ2
ABTRQ1
ABTRQ0
0
0
0
0
0
ABTAK2
ABTAK1
ABTAK0
0
0
0
0
0
TX2
TX1
TX0
0
0
IDAM1
IDAM0
0
IDHIT2
IDHIT1
IDHIT0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
0x000A
CANTBSEL
W
0x000D
CANMISC
RXACT
4
W
W
0x000C
Reserved
RXFRM
5
W
0x0009
CANTAAK
0x000B
CANIDAC
6
R
R
R
W
R
W
R
W
BOHOLD
= Unimplemented or Reserved
Figure 11-3. MSCAN Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
426
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Register
Name
0x000E
CANRXERR
R
0x000F
CANTXERR
R
0x0010–0x0013
CANIDAR0–3
R
0x0014–0x0017
CANIDMRx
R
0x0018–0x001B
CANIDAR4–7
R
0x001C–0x001F
CANIDMR4–7
R
0x0020–0x002F
CANRXFG
R
0x0030–0x003F
CANTXFG
R
Bit 7
6
5
4
3
2
1
Bit 0
RXERR7
RXERR6
RXERR5
RXERR4
RXERR3
RXERR2
RXERR1
RXERR0
TXERR7
TXERR6
TXERR5
TXERR4
TXERR3
TXERR2
TXERR1
TXERR0
AC7
AC6
AC5
AC4
AC3
AC2
AC1
AC0
AM7
AM6
AM5
AM4
AM3
AM2
AM1
AM0
AC7
AC6
AC5
AC4
AC3
AC2
AC1
AC0
AM7
AM6
AM5
AM4
AM3
AM2
AM1
AM0
W
W
W
W
W
W
W
W
See Section 11.3.3, “Programmer’s Model of Message Storage”
See Section 11.3.3, “Programmer’s Model of Message Storage”
= Unimplemented or Reserved
Figure 11-3. MSCAN Register Summary (continued)
11.3.2
Register Descriptions
This section describes in detail all the registers and register bits in the MSCAN module. Each description
includes a standard register diagram with an associated figure number. Details of register bit and field
function follow the register diagrams, in bit order. All bits of all registers in this module are completely
synchronous to internal clocks during a register read.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
427
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3.2.1
MSCAN Control Register 0 (CANCTL0)
The CANCTL0 register provides various control bits of the MSCAN module as described below.
Access: User read/write(1)
Module Base + 0x0000
7
R
6
5
RXACT
RXFRM
4
3
2
1
0
TIME
WUPE
SLPRQ
INITRQ
0
0
0
1
SYNCH
CSWAI
W
Reset:
0
0
0
0
= Unimplemented
Figure 11-4. MSCAN Control Register 0 (CANCTL0)
1. Read: Anytime
Write: Anytime when out of initialization mode; exceptions are read-only RXACT and SYNCH, RXFRM (which is set by the
module only), and INITRQ (which is also writable in initialization mode)
NOTE
The CANCTL0 register, except WUPE, INITRQ, and SLPRQ, is held in the
reset state when the initialization mode is active (INITRQ = 1 and
INITAK = 1). This register is writable again as soon as the initialization
mode is exited (INITRQ = 0 and INITAK = 0).
Table 11-2. CANCTL0 Register Field Descriptions
Field
Description
7
RXFRM
Received Frame Flag — This bit is read and clear only. It is set when a receiver has received a valid message
correctly, independently of the filter configuration. After it is set, it remains set until cleared by software or reset.
Clearing is done by writing a 1. Writing a 0 is ignored. This bit is not valid in loopback mode.
0 No valid message was received since last clearing this flag
1 A valid message was received since last clearing of this flag
6
RXACT
Receiver Active Status — This read-only flag indicates the MSCAN is receiving a message(1). The flag is
controlled by the receiver front end. This bit is not valid in loopback mode.
0 MSCAN is transmitting or idle
1 MSCAN is receiving a message (including when arbitration is lost)
5
CSWAI(2)
CAN Stops in Wait Mode — Enabling this bit allows for lower power consumption in wait mode by disabling all
the clocks at the CPU bus interface to the MSCAN module.
0 The module is not affected during wait mode
1 The module ceases to be clocked during wait mode
4
SYNCH
Synchronized Status — This read-only flag indicates whether the MSCAN is synchronized to the CAN bus and
able to participate in the communication process. It is set and cleared by the MSCAN.
0 MSCAN is not synchronized to the CAN bus
1 MSCAN is synchronized to the CAN bus
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
428
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-2. CANCTL0 Register Field Descriptions (continued)
Field
Description
3
TIME
Timer Enable — This bit activates an internal 16-bit wide free running timer which is clocked by the bit clock rate.
If the timer is enabled, a 16-bit time stamp will be assigned to each transmitted/received message within the
active TX/RX buffer. Right after the EOF of a valid message on the CAN bus, the time stamp is written to the
highest bytes (0x000E, 0x000F) in the appropriate buffer (see Section 11.3.3, “Programmer’s Model of Message
Storage”). In loopback mode no receive timestamp is generated. The internal timer is reset (all bits set to 0) when
disabled. This bit is held low in initialization mode.
0 Disable internal MSCAN timer
1 Enable internal MSCAN timer
2
WUPE(3)
Wake-Up Enable — This configuration bit allows the MSCAN to restart from sleep mode or from power down
mode (entered from sleep) when traffic on CAN is detected (see Section 11.4.5.5, “MSCAN Sleep Mode”). This
bit must be configured before sleep mode entry for the selected function to take effect.
0 Wake-up disabled — The MSCAN ignores traffic on CAN
1 Wake-up enabled — The MSCAN is able to restart
1
SLPRQ(4)
Sleep Mode Request — This bit requests the MSCAN to enter sleep mode, which is an internal power saving
mode (see Section 11.4.5.5, “MSCAN Sleep Mode”). The sleep mode request is serviced when the CAN bus is
idle, i.e., the module is not receiving a message and all transmit buffers are empty. The module indicates entry
to sleep mode by setting SLPAK = 1 (see Section 11.3.2.2, “MSCAN Control Register 1 (CANCTL1)”). SLPRQ
cannot be set while the WUPIF flag is set (see Section 11.3.2.5, “MSCAN Receiver Flag Register (CANRFLG)”).
Sleep mode will be active until SLPRQ is cleared by the CPU or, depending on the setting of WUPE, the MSCAN
detects activity on the CAN bus and clears SLPRQ itself.
0 Running — The MSCAN functions normally
1 Sleep mode request — The MSCAN enters sleep mode when CAN bus idle
0
Initialization Mode Request — When this bit is set by the CPU, the MSCAN skips to initialization mode (see
INITRQ(5),(6) Section 11.4.4.5, “MSCAN Initialization Mode”). Any ongoing transmission or reception is aborted and
synchronization to the CAN bus is lost. The module indicates entry to initialization mode by setting INITAK = 1
(Section 11.3.2.2, “MSCAN Control Register 1 (CANCTL1)”).
The following registers enter their hard reset state and restore their default values: CANCTL0(7), CANRFLG(8),
CANRIER(9), CANTFLG, CANTIER, CANTARQ, CANTAAK, and CANTBSEL.
The registers CANCTL1, CANBTR0, CANBTR1, CANIDAC, CANIDAR0-7, and CANIDMR0-7 can only be
written by the CPU when the MSCAN is in initialization mode (INITRQ = 1 and INITAK = 1). The values of the
error counters are not affected by initialization mode.
When this bit is cleared by the CPU, the MSCAN restarts and then tries to synchronize to the CAN bus. If the
MSCAN is not in bus-off state, it synchronizes after 11 consecutive recessive bits on the CAN bus; if the MSCAN
is in bus-off state, it continues to wait for 128 occurrences of 11 consecutive recessive bits.
Writing to other bits in CANCTL0, CANRFLG, CANRIER, CANTFLG, or CANTIER must be done only after
initialization mode is exited, which is INITRQ = 0 and INITAK = 0.
0 Normal operation
1 MSCAN in initialization mode
1. See the Bosch CAN 2.0A/B specification for a detailed definition of transmitter and receiver states.
2. In order to protect from accidentally violating the CAN protocol, TXCAN is immediately forced to a recessive state when the
CPU enters wait (CSWAI = 1) or stop mode (see Section 11.4.5.2, “Operation in Wait Mode” and Section 11.4.5.3, “Operation
in Stop Mode”).
3. The CPU has to make sure that the WUPE register and the WUPIE wake-up interrupt enable register (see Section 11.3.2.6,
“MSCAN Receiver Interrupt Enable Register (CANRIER)) is enabled, if the recovery mechanism from stop or wait is required.
4. The CPU cannot clear SLPRQ before the MSCAN has entered sleep mode (SLPRQ = 1 and SLPAK = 1).
5. The CPU cannot clear INITRQ before the MSCAN has entered initialization mode (INITRQ = 1 and INITAK = 1).
6. In order to protect from accidentally violating the CAN protocol, TXCAN is immediately forced to a recessive state when the
initialization mode is requested by the CPU. Thus, the recommended procedure is to bring the MSCAN into sleep mode
(SLPRQ = 1 and SLPAK = 1) before requesting initialization mode.
7. Not including WUPE, INITRQ, and SLPRQ.
8. TSTAT1 and TSTAT0 are not affected by initialization mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
429
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
9. RSTAT1 and RSTAT0 are not affected by initialization mode.
11.3.2.2
MSCAN Control Register 1 (CANCTL1)
The CANCTL1 register provides various control bits and handshake status information of the MSCAN
module as described below.
Access: User read/write(1)
Module Base + 0x0001
7
6
5
4
3
2
CANE
CLKSRC
LOOPB
LISTEN
BORM
WUPM
0
0
0
1
0
0
R
1
0
SLPAK
INITAK
0
1
W
Reset:
= Unimplemented
Figure 11-5. MSCAN Control Register 1 (CANCTL1)
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1), except CANE which is write once in normal and anytime in
special system operation modes when the MSCAN is in initialization mode (INITRQ = 1 and INITAK = 1)
Table 11-3. CANCTL1 Register Field Descriptions
Field
7
CANE
Description
MSCAN Enable
0 MSCAN module is disabled
1 MSCAN module is enabled
6
CLKSRC
MSCAN Clock Source — This bit defines the clock source for the MSCAN module (only for systems with a clock
generation module; Section 11.4.3.2, “Clock System,” and Section Figure 11-43., “MSCAN Clocking Scheme,”).
0 MSCAN clock source is the oscillator clock
1 MSCAN clock source is the bus clock
5
LOOPB
Loopback Self Test Mode — When this bit is set, the MSCAN performs an internal loopback which can be used
for self test operation. The bit stream output of the transmitter is fed back to the receiver internally. The RXCAN
input is ignored and the TXCAN output goes to the recessive state (logic 1). The MSCAN behaves as it does
normally when transmitting and treats its own transmitted message as a message received from a remote node.
In this state, the MSCAN ignores the bit sent during the ACK slot in the CAN frame acknowledge field to ensure
proper reception of its own message. Both transmit and receive interrupts are generated.
0 Loopback self test disabled
1 Loopback self test enabled
4
LISTEN
Listen Only Mode — This bit configures the MSCAN as a CAN bus monitor. When LISTEN is set, all valid CAN
messages with matching ID are received, but no acknowledgement or error frames are sent out (see
Section 11.4.4.4, “Listen-Only Mode”). In addition, the error counters are frozen. Listen only mode supports
applications which require “hot plugging” or throughput analysis. The MSCAN is unable to transmit any
messages when listen only mode is active.
0 Normal operation
1 Listen only mode activated
3
BORM
Bus-Off Recovery Mode — This bit configures the bus-off state recovery mode of the MSCAN. Refer to
Section 11.5.2, “Bus-Off Recovery,” for details.
0 Automatic bus-off recovery (see Bosch CAN 2.0A/B protocol specification)
1 Bus-off recovery upon user request
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
430
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-3. CANCTL1 Register Field Descriptions (continued)
Field
Description
2
WUPM
Wake-Up Mode — If WUPE in CANCTL0 is enabled, this bit defines whether the integrated low-pass filter is
applied to protect the MSCAN from spurious wake-up (see Section 11.4.5.5, “MSCAN Sleep Mode”).
0 MSCAN wakes up on any dominant level on the CAN bus
1 MSCAN wakes up only in case of a dominant pulse on the CAN bus that has a length of Twup
1
SLPAK
Sleep Mode Acknowledge — This flag indicates whether the MSCAN module has entered sleep mode (see
Section 11.4.5.5, “MSCAN Sleep Mode”). It is used as a handshake flag for the SLPRQ sleep mode request.
Sleep mode is active when SLPRQ = 1 and SLPAK = 1. Depending on the setting of WUPE, the MSCAN will
clear the flag if it detects activity on the CAN bus while in sleep mode.
0 Running — The MSCAN operates normally
1 Sleep mode active — The MSCAN has entered sleep mode
0
INITAK
Initialization Mode Acknowledge — This flag indicates whether the MSCAN module is in initialization mode
(see Section 11.4.4.5, “MSCAN Initialization Mode”). It is used as a handshake flag for the INITRQ initialization
mode request. Initialization mode is active when INITRQ = 1 and INITAK = 1. The registers CANCTL1,
CANBTR0, CANBTR1, CANIDAC, CANIDAR0–CANIDAR7, and CANIDMR0–CANIDMR7 can be written only by
the CPU when the MSCAN is in initialization mode.
0 Running — The MSCAN operates normally
1 Initialization mode active — The MSCAN has entered initialization mode
11.3.2.3
MSCAN Bus Timing Register 0 (CANBTR0)
The CANBTR0 register configures various CAN bus timing parameters of the MSCAN module.
Access: User read/write(1)
Module Base + 0x0002
7
6
5
4
3
2
1
0
SJW1
SJW0
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0
0
0
0
0
0
0
0
0
R
W
Reset:
Figure 11-6. MSCAN Bus Timing Register 0 (CANBTR0)
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1)
Table 11-4. CANBTR0 Register Field Descriptions
Field
Description
7-6
SJW[1:0]
Synchronization Jump Width — The synchronization jump width defines the maximum number of time quanta
(Tq) clock cycles a bit can be shortened or lengthened to achieve resynchronization to data transitions on the
CAN bus (see Table 11-5).
5-0
BRP[5:0]
Baud Rate Prescaler — These bits determine the time quanta (Tq) clock which is used to build up the bit timing
(see Table 11-6).
Table 11-5. Synchronization Jump Width
SJW1
SJW0
Synchronization Jump Width
0
0
1 Tq clock cycle
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
431
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-5. Synchronization Jump Width (continued)
SJW1
SJW0
Synchronization Jump Width
0
1
2 Tq clock cycles
1
0
3 Tq clock cycles
1
1
4 Tq clock cycles
Table 11-6. Baud Rate Prescaler
11.3.2.4
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0
Prescaler value (P)
0
0
0
0
0
0
1
0
0
0
0
0
1
2
0
0
0
0
1
0
3
0
0
0
0
1
1
4
:
:
:
:
:
:
:
1
1
1
1
1
1
64
MSCAN Bus Timing Register 1 (CANBTR1)
The CANBTR1 register configures various CAN bus timing parameters of the MSCAN module.
Access: User read/write(1)
Module Base + 0x0003
7
6
5
4
3
2
1
0
SAMP
TSEG22
TSEG21
TSEG20
TSEG13
TSEG12
TSEG11
TSEG10
0
0
0
0
0
0
0
0
R
W
Reset:
Figure 11-7. MSCAN Bus Timing Register 1 (CANBTR1)
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1)
Table 11-7. CANBTR1 Register Field Descriptions
Field
Description
7
SAMP
Sampling — This bit determines the number of CAN bus samples taken per bit time.
0 One sample per bit.
1 Three samples per bit(1).
If SAMP = 0, the resulting bit value is equal to the value of the single bit positioned at the sample point. If
SAMP = 1, the resulting bit value is determined by using majority rule on the three total samples. For higher bit
rates, it is recommended that only one sample is taken per bit time (SAMP = 0).
6-4
Time Segment 2 — Time segments within the bit time fix the number of clock cycles per bit time and the location
TSEG2[2:0] of the sample point (see Figure 11-44). Time segment 2 (TSEG2) values are programmable as shown in
Table 11-8.
3-0
Time Segment 1 — Time segments within the bit time fix the number of clock cycles per bit time and the location
TSEG1[3:0] of the sample point (see Figure 11-44). Time segment 1 (TSEG1) values are programmable as shown in
Table 11-9.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
432
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
1. In this case, PHASE_SEG1 must be at least 2 time quanta (Tq).
Table 11-8. Time Segment 2 Values
TSEG22
TSEG21
TSEG20
Time Segment 2
0
0
0
1 Tq clock cycle(1)
0
0
1
2 Tq clock cycles
:
:
:
:
1
1
0
7 Tq clock cycles
1
1
1
8 Tq clock cycles
1. This setting is not valid. Please refer to Table 11-36 for valid settings.
Table 11-9. Time Segment 1 Values
TSEG13
TSEG12
TSEG11
TSEG10
Time segment 1
0
0
0
0
1 Tq clock cycle(1)
0
0
0
1
2 Tq clock cycles1
0
0
1
0
3 Tq clock cycles1
0
0
1
1
4 Tq clock cycles
:
:
:
:
:
1
1
1
0
15 Tq clock cycles
1
1
1
1
16 Tq clock cycles
1. This setting is not valid. Please refer to Table 11-36 for valid settings.
The bit time is determined by the oscillator frequency, the baud rate prescaler, and the number of time
quanta (Tq) clock cycles per bit (as shown in Table 11-8 and Table 11-9).
Eqn. 11-1
( Prescaler value )
Bit Time = ------------------------------------------------------ • ( 1 + TimeSegment1 + TimeSegment2 )
f CANCLK
11.3.2.5
MSCAN Receiver Flag Register (CANRFLG)
A flag can be cleared only by software (writing a 1 to the corresponding bit position) when the condition
which caused the setting is no longer valid. Every flag has an associated interrupt enable bit in the
CANRIER register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
433
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Access: User read/write(1)
Module Base + 0x0004
7
6
WUPIF
CSCIF
0
0
R
5
4
3
2
RSTAT1
RSTAT0
TSTAT1
TSTAT0
1
0
OVRIF
RXF
0
0
W
Reset:
0
0
0
0
= Unimplemented
Figure 11-8. MSCAN Receiver Flag Register (CANRFLG)
1. Read: Anytime
Write: Anytime when not in initialization mode, except RSTAT[1:0] and TSTAT[1:0] flags which are read-only; write of 1 clears
flag; write of 0 is ignored
NOTE
The CANRFLG register is held in the reset state1 when the initialization
mode is active (INITRQ = 1 and INITAK = 1). This register is writable again
as soon as the initialization mode is exited (INITRQ = 0 and INITAK = 0).
Table 11-10. CANRFLG Register Field Descriptions
Field
Description
7
WUPIF
Wake-Up Interrupt Flag — If the MSCAN detects CAN bus activity while in sleep mode (see Section 11.4.5.5,
“MSCAN Sleep Mode,”) and WUPE = 1 in CANTCTL0 (see Section 11.3.2.1, “MSCAN Control Register 0
(CANCTL0)”), the module will set WUPIF. If not masked, a wake-up interrupt is pending while this flag is set.
0 No wake-up activity observed while in sleep mode
1 MSCAN detected activity on the CAN bus and requested wake-up
6
CSCIF
CAN Status Change Interrupt Flag — This flag is set when the MSCAN changes its current CAN bus status
due to the actual value of the transmit error counter (TEC) and the receive error counter (REC). An additional 4bit (RSTAT[1:0], TSTAT[1:0]) status register, which is split into separate sections for TEC/REC, informs the
system on the actual CAN bus status (see Section 11.3.2.6, “MSCAN Receiver Interrupt Enable Register
(CANRIER)”). If not masked, an error interrupt is pending while this flag is set. CSCIF provides a blocking
interrupt. That guarantees that the receiver/transmitter status bits (RSTAT/TSTAT) are only updated when no
CAN status change interrupt is pending. If the TECs/RECs change their current value after the CSCIF is
asserted, which would cause an additional state change in the RSTAT/TSTAT bits, these bits keep their status
until the current CSCIF interrupt is cleared again.
0 No change in CAN bus status occurred since last interrupt
1 MSCAN changed current CAN bus status
5-4
RSTAT[1:0]
Receiver Status Bits — The values of the error counters control the actual CAN bus status of the MSCAN. As
soon as the status change interrupt flag (CSCIF) is set, these bits indicate the appropriate receiver related CAN
bus status of the MSCAN. The coding for the bits RSTAT1, RSTAT0 is:
00 RxOK:
0 ≤ receive error counter < 96
01 RxWRN: 96 ≤ receive error counter < 128
10 RxERR: 128 ≤ receive error counter
11 Bus-off(1): 256 ≤ transmit error counter
1. The RSTAT[1:0], TSTAT[1:0] bits are not affected by initialization mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
434
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-10. CANRFLG Register Field Descriptions (continued)
Field
Description
3-2
TSTAT[1:0]
Transmitter Status Bits — The values of the error counters control the actual CAN bus status of the MSCAN.
As soon as the status change interrupt flag (CSCIF) is set, these bits indicate the appropriate transmitter related
CAN bus status of the MSCAN. The coding for the bits TSTAT1, TSTAT0 is:
00 TxOK:
0 ≤ transmit error counter < 96
01 TxWRN: 96 ≤ transmit error counter < 128
10 TxERR: 128 ≤ transmit error counter < 256
11 Bus-Off: 256 ≤ transmit error counter
1
OVRIF
Overrun Interrupt Flag — This flag is set when a data overrun condition occurs. If not masked, an error interrupt
is pending while this flag is set.
0
No data overrun condition
1
A data overrun detected
0
RXF(2)
Receive Buffer Full Flag — RXF is set by the MSCAN when a new message is shifted in the receiver FIFO.
This flag indicates whether the shifted buffer is loaded with a correctly received message (matching identifier,
matching cyclic redundancy code (CRC) and no other errors detected). After the CPU has read that message
from the RxFG buffer in the receiver FIFO, the RXF flag must be cleared to release the buffer. A set RXF flag
prohibits the shifting of the next FIFO entry into the foreground buffer (RxFG). If not masked, a receive interrupt
is pending while this flag is set.
0
No new message available within the RxFG
1
The receiver FIFO is not empty. A new message is available in the RxFG
1. Redundant Information for the most critical CAN bus status which is “bus-off”. This only occurs if the Tx error counter exceeds
a number of 255 errors. Bus-off affects the receiver state. As soon as the transmitter leaves its bus-off state the receiver state
skips to RxOK too. Refer also to TSTAT[1:0] coding in this register.
2. To ensure data integrity, do not read the receive buffer registers while the RXF flag is cleared. For MCUs with dual CPUs,
reading the receive buffer registers while the RXF flag is cleared may result in a CPU fault condition.
11.3.2.6
MSCAN Receiver Interrupt Enable Register (CANRIER)
This register contains the interrupt enable bits for the interrupt flags described in the CANRFLG register.
Access: User read/write(1)
Module Base + 0x0005
7
6
5
4
3
2
1
0
WUPIE
CSCIE
RSTATE1
RSTATE0
TSTATE1
TSTATE0
OVRIE
RXFIE
0
0
0
0
0
0
0
0
R
W
Reset:
Figure 11-9. MSCAN Receiver Interrupt Enable Register (CANRIER)
1. Read: Anytime
Write: Anytime when not in initialization mode
NOTE
The CANRIER register is held in the reset state when the initialization mode
is active (INITRQ=1 and INITAK=1). This register is writable when not in
initialization mode (INITRQ=0 and INITAK=0).
The RSTATE[1:0], TSTATE[1:0] bits are not affected by initialization
mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
435
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-11. CANRIER Register Field Descriptions
Field
7
WUPIE(1)
6
CSCIE
Description
Wake-Up Interrupt Enable
0 No interrupt request is generated from this event.
1 A wake-up event causes a Wake-Up interrupt request.
CAN Status Change Interrupt Enable
0 No interrupt request is generated from this event.
1 A CAN Status Change event causes an error interrupt request.
5-4
Receiver Status Change Enable — These RSTAT enable bits control the sensitivity level in which receiver state
RSTATE[1:0] changes are causing CSCIF interrupts. Independent of the chosen sensitivity level the RSTAT flags continue to
indicate the actual receiver state and are only updated if no CSCIF interrupt is pending.
00 Do not generate any CSCIF interrupt caused by receiver state changes.
01 Generate CSCIF interrupt only if the receiver enters or leaves “bus-off” state. Discard other receiver state
changes for generating CSCIF interrupt.
10 Generate CSCIF interrupt only if the receiver enters or leaves “RxErr” or “bus-off”(2) state. Discard other
receiver state changes for generating CSCIF interrupt.
11 Generate CSCIF interrupt on all state changes.
3-2
Transmitter Status Change Enable — These TSTAT enable bits control the sensitivity level in which transmitter
TSTATE[1:0] state changes are causing CSCIF interrupts. Independent of the chosen sensitivity level, the TSTAT flags
continue to indicate the actual transmitter state and are only updated if no CSCIF interrupt is pending.
00 Do not generate any CSCIF interrupt caused by transmitter state changes.
01 Generate CSCIF interrupt only if the transmitter enters or leaves “bus-off” state. Discard other transmitter
state changes for generating CSCIF interrupt.
10 Generate CSCIF interrupt only if the transmitter enters or leaves “TxErr” or “bus-off” state. Discard other
transmitter state changes for generating CSCIF interrupt.
11 Generate CSCIF interrupt on all state changes.
1
OVRIE
Overrun Interrupt Enable
0 No interrupt request is generated from this event.
1 An overrun event causes an error interrupt request.
0
RXFIE
Receiver Full Interrupt Enable
0 No interrupt request is generated from this event.
1 A receive buffer full (successful message reception) event causes a receiver interrupt request.
1. WUPIE and WUPE (see Section 11.3.2.1, “MSCAN Control Register 0 (CANCTL0)”) must both be enabled if the recovery
mechanism from stop or wait is required.
2. Bus-off state is only defined for transmitters by the CAN standard (see Bosch CAN 2.0A/B protocol specification). Because
the only possible state change for the transmitter from bus-off to TxOK also forces the receiver to skip its current state to RxOK,
the coding of the RXSTAT[1:0] flags define an additional bus-off state for the receiver (see Section 11.3.2.5, “MSCAN Receiver
Flag Register (CANRFLG)”).
11.3.2.7
MSCAN Transmitter Flag Register (CANTFLG)
The transmit buffer empty flags each have an associated interrupt enable bit in the CANTIER register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
436
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Access: User read/write(1)
Module Base + 0x0006
R
7
6
5
4
3
0
0
0
0
0
2
1
0
TXE2
TXE1
TXE0
1
1
1
W
Reset:
0
0
0
0
0
= Unimplemented
Figure 11-10. MSCAN Transmitter Flag Register (CANTFLG)
1. Read: Anytime
Write: Anytime when not in initialization mode; write of 1 clears flag, write of 0 is ignored
NOTE
The CANTFLG register is held in the reset state when the initialization
mode is active (INITRQ = 1 and INITAK = 1). This register is writable when
not in initialization mode (INITRQ = 0 and INITAK = 0).
Table 11-12. CANTFLG Register Field Descriptions
Field
Description
2-0
TXE[2:0]
Transmitter Buffer Empty — This flag indicates that the associated transmit message buffer is empty, and thus
not scheduled for transmission. The CPU must clear the flag after a message is set up in the transmit buffer and
is due for transmission. The MSCAN sets the flag after the message is sent successfully. The flag is also set by
the MSCAN when the transmission request is successfully aborted due to a pending abort request (see
Section 11.3.2.9, “MSCAN Transmitter Message Abort Request Register (CANTARQ)”). If not masked, a
transmit interrupt is pending while this flag is set.
Clearing a TXEx flag also clears the corresponding ABTAKx (see Section 11.3.2.10, “MSCAN Transmitter
Message Abort Acknowledge Register (CANTAAK)”). When a TXEx flag is set, the corresponding ABTRQx bit
is cleared (see Section 11.3.2.9, “MSCAN Transmitter Message Abort Request Register (CANTARQ)”).
When listen-mode is active (see Section 11.3.2.2, “MSCAN Control Register 1 (CANCTL1)”) the TXEx flags
cannot be cleared and no transmission is started.
Read and write accesses to the transmit buffer will be blocked, if the corresponding TXEx bit is cleared
(TXEx = 0) and the buffer is scheduled for transmission.
0 The associated message buffer is full (loaded with a message due for transmission)
1 The associated message buffer is empty (not scheduled)
11.3.2.8
MSCAN Transmitter Interrupt Enable Register (CANTIER)
This register contains the interrupt enable bits for the transmit buffer empty interrupt flags.
Access: User read/write(1)
Module Base + 0x0007
R
7
6
5
4
3
0
0
0
0
0
2
1
0
TXEIE2
TXEIE1
TXEIE0
0
0
0
W
Reset:
0
0
0
0
0
= Unimplemented
Figure 11-11. MSCAN Transmitter Interrupt Enable Register (CANTIER)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
437
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
1. Read: Anytime
Write: Anytime when not in initialization mode
NOTE
The CANTIER register is held in the reset state when the initialization mode
is active (INITRQ = 1 and INITAK = 1). This register is writable when not
in initialization mode (INITRQ = 0 and INITAK = 0).
Table 11-13. CANTIER Register Field Descriptions
Field
Description
2-0
TXEIE[2:0]
11.3.2.9
Transmitter Empty Interrupt Enable
0 No interrupt request is generated from this event.
1 A transmitter empty (transmit buffer available for transmission) event causes a transmitter empty interrupt
request.
MSCAN Transmitter Message Abort Request Register (CANTARQ)
The CANTARQ register allows abort request of queued messages as described below.
Access: User read/write(1)
Module Base + 0x0008
R
7
6
5
4
3
0
0
0
0
0
2
1
0
ABTRQ2
ABTRQ1
ABTRQ0
0
0
0
W
Reset:
0
0
0
0
0
= Unimplemented
Figure 11-12. MSCAN Transmitter Message Abort Request Register (CANTARQ)
1. Read: Anytime
Write: Anytime when not in initialization mode
NOTE
The CANTARQ register is held in the reset state when the initialization
mode is active (INITRQ = 1 and INITAK = 1). This register is writable when
not in initialization mode (INITRQ = 0 and INITAK = 0).
Table 11-14. CANTARQ Register Field Descriptions
Field
Description
2-0
Abort Request — The CPU sets the ABTRQx bit to request that a scheduled message buffer (TXEx = 0) be
ABTRQ[2:0] aborted. The MSCAN grants the request if the message has not already started transmission, or if the
transmission is not successful (lost arbitration or error). When a message is aborted, the associated TXE (see
Section 11.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and abort acknowledge flags (ABTAK, see
Section 11.3.2.10, “MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK)”) are set and a
transmit interrupt occurs if enabled. The CPU cannot reset ABTRQx. ABTRQx is reset whenever the associated
TXE flag is set.
0 No abort request
1 Abort request pending
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
438
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3.2.10 MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK)
The CANTAAK register indicates the successful abort of a queued message, if requested by the
appropriate bits in the CANTARQ register.
Access: User read/write(1)
Module Base + 0x0009
R
7
6
5
4
3
2
1
0
0
0
0
0
0
ABTAK2
ABTAK1
ABTAK0
0
0
0
0
0
0
0
0
W
Reset:
= Unimplemented
Figure 11-13. MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK)
1. Read: Anytime
Write: Unimplemented
NOTE
The CANTAAK register is held in the reset state when the initialization
mode is active (INITRQ = 1 and INITAK = 1).
Table 11-15. CANTAAK Register Field Descriptions
Field
Description
2-0
Abort Acknowledge — This flag acknowledges that a message was aborted due to a pending abort request
ABTAK[2:0] from the CPU. After a particular message buffer is flagged empty, this flag can be used by the application
software to identify whether the message was aborted successfully or was sent anyway. The ABTAKx flag is
cleared whenever the corresponding TXE flag is cleared.
0 The message was not aborted.
1 The message was aborted.
11.3.2.11 MSCAN Transmit Buffer Selection Register (CANTBSEL)
The CANTBSEL register allows the selection of the actual transmit message buffer, which then will be
accessible in the CANTXFG register space.
Access: User read/write(1)
Module Base + 0x000A
R
7
6
5
4
3
0
0
0
0
0
2
1
0
TX2
TX1
TX0
0
0
0
W
Reset:
0
0
0
0
0
= Unimplemented
Figure 11-14. MSCAN Transmit Buffer Selection Register (CANTBSEL)
1. Read: Find the lowest ordered bit set to 1, all other bits will be read as 0
Write: Anytime when not in initialization mode
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
439
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
NOTE
The CANTBSEL register is held in the reset state when the initialization
mode is active (INITRQ = 1 and INITAK=1). This register is writable when
not in initialization mode (INITRQ = 0 and INITAK = 0).
Table 11-16. CANTBSEL Register Field Descriptions
Field
Description
2-0
TX[2:0]
Transmit Buffer Select — The lowest numbered bit places the respective transmit buffer in the CANTXFG
register space (e.g., TX1 = 1 and TX0 = 1 selects transmit buffer TX0; TX1 = 1 and TX0 = 0 selects transmit
buffer TX1). Read and write accesses to the selected transmit buffer will be blocked, if the corresponding TXEx
bit is cleared and the buffer is scheduled for transmission (see Section 11.3.2.7, “MSCAN Transmitter Flag
Register (CANTFLG)”).
0 The associated message buffer is deselected
1 The associated message buffer is selected, if lowest numbered bit
The following gives a short programming example of the usage of the CANTBSEL register:
To get the next available transmit buffer, application software must read the CANTFLG register and write
this value back into the CANTBSEL register. In this example Tx buffers TX1 and TX2 are available. The
value read from CANTFLG is therefore 0b0000_0110. When writing this value back to CANTBSEL, the
Tx buffer TX1 is selected in the CANTXFG because the lowest numbered bit set to 1 is at bit position 1.
Reading back this value out of CANTBSEL results in 0b0000_0010, because only the lowest numbered
bit position set to 1 is presented. This mechanism eases the application software’s selection of the next
available Tx buffer.
• LDAA CANTFLG; value read is 0b0000_0110
• STAA CANTBSEL; value written is 0b0000_0110
• LDAA CANTBSEL; value read is 0b0000_0010
If all transmit message buffers are deselected, no accesses are allowed to the CANTXFG registers.
11.3.2.12 MSCAN Identifier Acceptance Control Register (CANIDAC)
The CANIDAC register is used for identifier acceptance control as described below.
Access: User read/write(1)
Module Base + 0x000B
R
7
6
0
0
5
4
IDAM1
IDAM0
0
0
3
2
1
0
0
IDHIT2
IDHIT1
IDHIT0
0
0
0
0
W
Reset:
0
0
= Unimplemented
Figure 11-15. MSCAN Identifier Acceptance Control Register (CANIDAC)
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1), except bits IDHITx, which are read-only
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
440
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-17. CANIDAC Register Field Descriptions
Field
Description
5-4
IDAM[1:0]
Identifier Acceptance Mode — The CPU sets these flags to define the identifier acceptance filter organization
(see Section 11.4.3, “Identifier Acceptance Filter”). Table 11-18 summarizes the different settings. In filter closed
mode, no message is accepted such that the foreground buffer is never reloaded.
2-0
IDHIT[2:0]
Identifier Acceptance Hit Indicator — The MSCAN sets these flags to indicate an identifier acceptance hit (see
Section 11.4.3, “Identifier Acceptance Filter”). Table 11-19 summarizes the different settings.
Table 11-18. Identifier Acceptance Mode Settings
IDAM1
IDAM0
Identifier Acceptance Mode
0
0
Two 32-bit acceptance filters
0
1
Four 16-bit acceptance filters
1
0
Eight 8-bit acceptance filters
1
1
Filter closed
Table 11-19. Identifier Acceptance Hit Indication
IDHIT2
IDHIT1
IDHIT0
Identifier Acceptance Hit
0
0
0
Filter 0 hit
0
0
1
Filter 1 hit
0
1
0
Filter 2 hit
0
1
1
Filter 3 hit
1
0
0
Filter 4 hit
1
0
1
Filter 5 hit
1
1
0
Filter 6 hit
1
1
1
Filter 7 hit
The IDHITx indicators are always related to the message in the foreground buffer (RxFG). When a
message gets shifted into the foreground buffer of the receiver FIFO the indicators are updated as well.
11.3.2.13 MSCAN Reserved Register
This register is reserved for factory testing of the MSCAN module and is not available in normal system
operating modes.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
441
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Access: User read/write(1)
Module Base + 0x000C
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
W
Reset:
= Unimplemented
Figure 11-16. MSCAN Reserved Register
1. Read: Always reads zero in normal system operation modes
Write: Unimplemented in normal system operation modes
NOTE
Writing to this register when in special system operating modes can alter the
MSCAN functionality.
11.3.2.14 MSCAN Miscellaneous Register (CANMISC)
This register provides additional features.
Access: User read/write(1)
Module Base + 0x000D
R
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
BOHOLD
W
Reset:
0
0
0
0
0
0
0
0
= Unimplemented
Figure 11-17. MSCAN Miscellaneous Register (CANMISC)
1. Read: Anytime
Write: Anytime; write of ‘1’ clears flag; write of ‘0’ ignored
Table 11-20. CANMISC Register Field Descriptions
Field
Description
0
BOHOLD
Bus-off State Hold Until User Request — If BORM is set in MSCAN Control Register 1 (CANCTL1), this bit
indicates whether the module has entered the bus-off state. Clearing this bit requests the recovery from bus-off.
Refer to Section 11.5.2, “Bus-Off Recovery,” for details.
0 Module is not bus-off or recovery has been requested by user in bus-off state
1 Module is bus-off and holds this state until user request
11.3.2.15 MSCAN Receive Error Counter (CANRXERR)
This register reflects the status of the MSCAN receive error counter.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
442
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Access: User read/write(1)
Module Base + 0x000E
R
7
6
5
4
3
2
1
0
RXERR7
RXERR6
RXERR5
RXERR4
RXERR3
RXERR2
RXERR1
RXERR0
0
0
0
0
0
0
0
0
W
Reset:
= Unimplemented
Figure 11-18. MSCAN Receive Error Counter (CANRXERR)
1. Read: Only when in sleep mode (SLPRQ = 1 and SLPAK = 1) or initialization mode (INITRQ = 1 and INITAK = 1)
Write: Unimplemented
NOTE
Reading this register when in any other mode other than sleep or
initialization mode may return an incorrect value. For MCUs with dual
CPUs, this may result in a CPU fault condition.
11.3.2.16 MSCAN Transmit Error Counter (CANTXERR)
This register reflects the status of the MSCAN transmit error counter.
Access: User read/write(1)
Module Base + 0x000F
R
7
6
5
4
3
2
1
0
TXERR7
TXERR6
TXERR5
TXERR4
TXERR3
TXERR2
TXERR1
TXERR0
0
0
0
0
0
0
0
0
W
Reset:
= Unimplemented
Figure 11-19. MSCAN Transmit Error Counter (CANTXERR)
1. Read: Only when in sleep mode (SLPRQ = 1 and SLPAK = 1) or initialization mode (INITRQ = 1 and INITAK = 1)
Write: Unimplemented
NOTE
Reading this register when in any other mode other than sleep or
initialization mode, may return an incorrect value. For MCUs with dual
CPUs, this may result in a CPU fault condition.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
443
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3.2.17 MSCAN Identifier Acceptance Registers (CANIDAR0-7)
On reception, each message is written into the background receive buffer. The CPU is only signalled to
read the message if it passes the criteria in the identifier acceptance and identifier mask registers
(accepted); otherwise, the message is overwritten by the next message (dropped).
The acceptance registers of the MSCAN are applied on the IDR0–IDR3 registers (see Section 11.3.3.1,
“Identifier Registers (IDR0–IDR3)”) of incoming messages in a bit by bit manner (see Section 11.4.3,
“Identifier Acceptance Filter”).
For extended identifiers, all four acceptance and mask registers are applied. For standard identifiers, only
the first two (CANIDAR0/1, CANIDMR0/1) are applied.
Access: User read/write(1)
Module Base + 0x0010 to Module Base + 0x0013
7
6
5
4
3
2
1
0
AC7
AC6
AC5
AC4
AC3
AC2
AC1
AC0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 11-20. MSCAN Identifier Acceptance Registers (First Bank) — CANIDAR0–CANIDAR3
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1)
Table 11-21. CANIDAR0–CANIDAR3 Register Field Descriptions
Field
Description
7-0
AC[7:0]
Acceptance Code Bits — AC[7:0] comprise a user-defined sequence of bits with which the corresponding bits
of the related identifier register (IDRn) of the receive message buffer are compared. The result of this comparison
is then masked with the corresponding identifier mask register.
Access: User read/write(1)
Module Base + 0x0018 to Module Base + 0x001B
7
6
5
4
3
2
1
0
AC7
AC6
AC5
AC4
AC3
AC2
AC1
AC0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 11-21. MSCAN Identifier Acceptance Registers (Second Bank) — CANIDAR4–CANIDAR7
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
444
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-22. CANIDAR4–CANIDAR7 Register Field Descriptions
Field
Description
7-0
AC[7:0]
Acceptance Code Bits — AC[7:0] comprise a user-defined sequence of bits with which the corresponding bits
of the related identifier register (IDRn) of the receive message buffer are compared. The result of this comparison
is then masked with the corresponding identifier mask register.
11.3.2.18 MSCAN Identifier Mask Registers (CANIDMR0–CANIDMR7)
The identifier mask register specifies which of the corresponding bits in the identifier acceptance register
are relevant for acceptance filtering. To receive standard identifiers in 32 bit filter mode, it is required to
program the last three bits (AM[2:0]) in the mask registers CANIDMR1 and CANIDMR5 to “don’t care.”
To receive standard identifiers in 16 bit filter mode, it is required to program the last three bits (AM[2:0])
in the mask registers CANIDMR1, CANIDMR3, CANIDMR5, and CANIDMR7 to “don’t care.”
Access: User read/write(1)
Module Base + 0x0014 to Module Base + 0x0017
7
6
5
4
3
2
1
0
AM7
AM6
AM5
AM4
AM3
AM2
AM1
AM0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 11-22. MSCAN Identifier Mask Registers (First Bank) — CANIDMR0–CANIDMR3
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1)
Table 11-23. CANIDMR0–CANIDMR3 Register Field Descriptions
Field
Description
7-0
AM[7:0]
Acceptance Mask Bits — If a particular bit in this register is cleared, this indicates that the corresponding bit in
the identifier acceptance register must be the same as its identifier bit before a match is detected. The message
is accepted if all such bits match. If a bit is set, it indicates that the state of the corresponding bit in the identifier
acceptance register does not affect whether or not the message is accepted.
0 Match corresponding acceptance code register and identifier bits
1 Ignore corresponding acceptance code register bit
Access: User read/write(1)
Module Base + 0x001C to Module Base + 0x001F
7
6
5
4
3
2
1
0
AM7
AM6
AM5
AM4
AM3
AM2
AM1
AM0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 11-23. MSCAN Identifier Mask Registers (Second Bank) — CANIDMR4–CANIDMR7
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
445
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
1. Read: Anytime
Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1)
Table 11-24. CANIDMR4–CANIDMR7 Register Field Descriptions
Field
Description
7-0
AM[7:0]
Acceptance Mask Bits — If a particular bit in this register is cleared, this indicates that the corresponding bit in
the identifier acceptance register must be the same as its identifier bit before a match is detected. The message
is accepted if all such bits match. If a bit is set, it indicates that the state of the corresponding bit in the identifier
acceptance register does not affect whether or not the message is accepted.
0 Match corresponding acceptance code register and identifier bits
1 Ignore corresponding acceptance code register bit
11.3.3
Programmer’s Model of Message Storage
The following section details the organization of the receive and transmit message buffers and the
associated control registers.
To simplify the programmer interface, the receive and transmit message buffers have the same outline.
Each message buffer allocates 16 bytes in the memory map containing a 13 byte data structure.
An additional transmit buffer priority register (TBPR) is defined for the transmit buffers. Within the last
two bytes of this memory map, the MSCAN stores a special 16-bit time stamp, which is sampled from an
internal timer after successful transmission or reception of a message. This feature is only available for
transmit and receiver buffers, if the TIME bit is set (see Section 11.3.2.1, “MSCAN Control Register 0
(CANCTL0)”).
The time stamp register is written by the MSCAN. The CPU can only read these registers.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
446
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-25. Message Buffer Organization
Offset
Address
Register
Access
0x00X0
IDR0 — Identifier Register 0
R/W
0x00X1
IDR1 — Identifier Register 1
R/W
0x00X2
IDR2 — Identifier Register 2
R/W
0x00X3
IDR3 — Identifier Register 3
R/W
0x00X4
DSR0 — Data Segment Register 0
R/W
0x00X5
DSR1 — Data Segment Register 1
R/W
0x00X6
DSR2 — Data Segment Register 2
R/W
0x00X7
DSR3 — Data Segment Register 3
R/W
0x00X8
DSR4 — Data Segment Register 4
R/W
0x00X9
DSR5 — Data Segment Register 5
R/W
0x00XA
DSR6 — Data Segment Register 6
R/W
0x00XB
DSR7 — Data Segment Register 7
R/W
0x00XC
DLR — Data Length Register
R/W
(1)
0x00XD
TBPR — Transmit Buffer Priority Register
0x00XE
TSRH — Time Stamp Register (High Byte)
0x00XF
TSRL — Time Stamp Register (Low Byte)
1. Not applicable for receive buffers
R/W
R
R
Figure 11-24 shows the common 13-byte data structure of receive and transmit buffers for extended
identifiers. The mapping of standard identifiers into the IDR registers is shown in Figure 11-25.
All bits of the receive and transmit buffers are ‘x’ out of reset because of RAM-based implementation1.
All reserved or unused bits of the receive and transmit buffers always read ‘x’.
1. Exception: The transmit buffer priority registers are 0 out of reset.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
447
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Figure 11-24. Receive/Transmit Message Buffer — Extended Identifier Mapping
Register
Name
0x00X0
IDR0
0x00X1
IDR1
0x00X2
IDR2
0x00X3
IDR3
0x00X4
DSR0
0x00X5
DSR1
0x00X6
DSR2
0x00X7
DSR3
0x00X8
DSR4
0x00X9
DSR5
0x00XA
DSR6
0x00XB
DSR7
0x00XC
DLR
Bit 7
6
5
4
3
2
1
Bit0
ID28
ID27
ID26
ID25
ID24
ID23
ID22
ID21
ID20
ID19
ID18
SRR (=1)
IDE (=1)
ID17
ID16
ID15
ID14
ID13
ID12
ID11
ID10
ID9
ID8
ID7
ID6
ID5
ID4
ID3
ID2
ID1
ID0
RTR
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
DLC3
DLC2
DLC1
DLC0
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
R
W
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
448
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Figure 11-24. Receive/Transmit Message Buffer — Extended Identifier Mapping (continued)
Register
Name
Bit 7
6
5
4
3
2
1
Bit0
= Unused, always read ‘x’
Read:
• For transmit buffers, anytime when TXEx flag is set (see Section 11.3.2.7, “MSCAN Transmitter
Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see
Section 11.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”).
• For receive buffers, only when RXF flag is set (see Section 11.3.2.5, “MSCAN Receiver Flag
Register (CANRFLG)”).
Write:
•
•
For transmit buffers, anytime when TXEx flag is set (see Section 11.3.2.7, “MSCAN Transmitter
Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see
Section 11.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”).
Unimplemented for receive buffers.
Reset: Undefined because of RAM-based implementation
Figure 11-25. Receive/Transmit Message Buffer — Standard Identifier Mapping
Register
Name
IDR0
0x00X0
IDR1
0x00X1
IDR2
0x00X2
IDR3
0x00X3
Bit 7
6
5
4
3
2
1
Bit 0
ID10
ID9
ID8
ID7
ID6
ID5
ID4
ID3
ID2
ID1
ID0
RTR
IDE (=0)
R
W
R
W
R
W
R
W
= Unused, always read ‘x’
11.3.3.1
Identifier Registers (IDR0–IDR3)
The identifier registers for an extended format identifier consist of a total of 32 bits: ID[28:0], SRR, IDE,
and RTR. The identifier registers for a standard format identifier consist of a total of 13 bits: ID[10:0],
RTR, and IDE.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
449
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3.3.1.1
IDR0–IDR3 for Extended Identifier Mapping
Module Base + 0x00X0
7
6
5
4
3
2
1
0
ID28
ID27
ID26
ID25
ID24
ID23
ID22
ID21
x
x
x
x
x
x
x
x
R
W
Reset:
Figure 11-26. Identifier Register 0 (IDR0) — Extended Identifier Mapping
Table 11-26. IDR0 Register Field Descriptions — Extended
Field
Description
7-0
ID[28:21]
Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number.
Module Base + 0x00X1
7
6
5
4
3
2
1
0
ID20
ID19
ID18
SRR (=1)
IDE (=1)
ID17
ID16
ID15
x
x
x
x
x
x
x
x
R
W
Reset:
Figure 11-27. Identifier Register 1 (IDR1) — Extended Identifier Mapping
Table 11-27. IDR1 Register Field Descriptions — Extended
Field
Description
7-5
ID[20:18]
Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number.
4
SRR
Substitute Remote Request — This fixed recessive bit is used only in extended format. It must be set to 1 by
the user for transmission buffers and is stored as received on the CAN bus for receive buffers.
3
IDE
ID Extended — This flag indicates whether the extended or standard identifier format is applied in this buffer. In
the case of a receive buffer, the flag is set as received and indicates to the CPU how to process the buffer
identifier registers. In the case of a transmit buffer, the flag indicates to the MSCAN what type of identifier to send.
0 Standard format (11 bit)
1 Extended format (29 bit)
2-0
ID[17:15]
Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
450
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Module Base + 0x00X2
7
6
5
4
3
2
1
0
ID14
ID13
ID12
ID11
ID10
ID9
ID8
ID7
x
x
x
x
x
x
x
x
R
W
Reset:
Figure 11-28. Identifier Register 2 (IDR2) — Extended Identifier Mapping
Table 11-28. IDR2 Register Field Descriptions — Extended
Field
Description
7-0
ID[14:7]
Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number.
Module Base + 0x00X3
7
6
5
4
3
2
1
0
ID6
ID5
ID4
ID3
ID2
ID1
ID0
RTR
x
x
x
x
x
x
x
x
R
W
Reset:
Figure 11-29. Identifier Register 3 (IDR3) — Extended Identifier Mapping
Table 11-29. IDR3 Register Field Descriptions — Extended
Field
Description
7-1
ID[6:0]
Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number.
0
RTR
Remote Transmission Request — This flag reflects the status of the remote transmission request bit in the
CAN frame. In the case of a receive buffer, it indicates the status of the received frame and supports the
transmission of an answering frame in software. In the case of a transmit buffer, this flag defines the setting of
the RTR bit to be sent.
0 Data frame
1 Remote frame
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
451
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3.3.1.2
IDR0–IDR3 for Standard Identifier Mapping
Module Base + 0x00X0
7
6
5
4
3
2
1
0
ID10
ID9
ID8
ID7
ID6
ID5
ID4
ID3
x
x
x
x
x
x
x
x
R
W
Reset:
Figure 11-30. Identifier Register 0 — Standard Mapping
Table 11-30. IDR0 Register Field Descriptions — Standard
Field
Description
7-0
ID[10:3]
Standard Format Identifier — The identifiers consist of 11 bits (ID[10:0]) for the standard format. ID10 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number. See also ID bits in Table 11-31.
Module Base + 0x00X1
7
6
5
4
3
ID2
ID1
ID0
RTR
IDE (=0)
x
x
x
x
x
2
1
0
x
x
x
R
W
Reset:
= Unused; always read ‘x’
Figure 11-31. Identifier Register 1 — Standard Mapping
Table 11-31. IDR1 Register Field Descriptions
Field
Description
7-5
ID[2:0]
Standard Format Identifier — The identifiers consist of 11 bits (ID[10:0]) for the standard format. ID10 is the
most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an
identifier is defined to be highest for the smallest binary number. See also ID bits in Table 11-30.
4
RTR
Remote Transmission Request — This flag reflects the status of the Remote Transmission Request bit in the
CAN frame. In the case of a receive buffer, it indicates the status of the received frame and supports the
transmission of an answering frame in software. In the case of a transmit buffer, this flag defines the setting of
the RTR bit to be sent.
0 Data frame
1 Remote frame
3
IDE
ID Extended — This flag indicates whether the extended or standard identifier format is applied in this buffer. In
the case of a receive buffer, the flag is set as received and indicates to the CPU how to process the buffer
identifier registers. In the case of a transmit buffer, the flag indicates to the MSCAN what type of identifier to send.
0 Standard format (11 bit)
1 Extended format (29 bit)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
452
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Module Base + 0x00X2
7
6
5
4
3
2
1
0
x
x
x
x
x
x
x
x
R
W
Reset:
= Unused; always read ‘x’
Figure 11-32. Identifier Register 2 — Standard Mapping
Module Base + 0x00X3
7
6
5
4
3
2
1
0
x
x
x
x
x
x
x
x
R
W
Reset:
= Unused; always read ‘x’
Figure 11-33. Identifier Register 3 — Standard Mapping
11.3.3.2
Data Segment Registers (DSR0-7)
The eight data segment registers, each with bits DB[7:0], contain the data to be transmitted or received.
The number of bytes to be transmitted or received is determined by the data length code in the
corresponding DLR register.
Module Base + 0x00X4 to Module Base + 0x00XB
7
6
5
4
3
2
1
0
DB7
DB6
DB5
DB4
DB3
DB2
DB1
DB0
x
x
x
x
x
x
x
x
R
W
Reset:
Figure 11-34. Data Segment Registers (DSR0–DSR7) — Extended Identifier Mapping
Table 11-32. DSR0–DSR7 Register Field Descriptions
Field
7-0
DB[7:0]
Description
Data bits 7-0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
453
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.3.3.3
Data Length Register (DLR)
This register keeps the data length field of the CAN frame.
Module Base + 0x00XC
7
6
5
4
3
2
1
0
DLC3
DLC2
DLC1
DLC0
x
x
x
x
R
W
Reset:
x
x
x
x
= Unused; always read “x”
Figure 11-35. Data Length Register (DLR) — Extended Identifier Mapping
Table 11-33. DLR Register Field Descriptions
Field
Description
3-0
DLC[3:0]
Data Length Code Bits — The data length code contains the number of bytes (data byte count) of the respective
message. During the transmission of a remote frame, the data length code is transmitted as programmed while
the number of transmitted data bytes is always 0. The data byte count ranges from 0 to 8 for a data frame.
Table 11-34 shows the effect of setting the DLC bits.
Table 11-34. Data Length Codes
Data Length Code
11.3.3.4
DLC3
DLC2
DLC1
DLC0
Data Byte
Count
0
0
0
0
0
0
0
0
1
1
0
0
1
0
2
0
0
1
1
3
0
1
0
0
4
0
1
0
1
5
0
1
1
0
6
0
1
1
1
7
1
0
0
0
8
Transmit Buffer Priority Register (TBPR)
This register defines the local priority of the associated message buffer. The local priority is used for the
internal prioritization process of the MSCAN and is defined to be highest for the smallest binary number.
The MSCAN implements the following internal prioritization mechanisms:
• All transmission buffers with a cleared TXEx flag participate in the prioritization immediately
before the SOF (start of frame) is sent.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
454
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
•
The transmission buffer with the lowest local priority field wins the prioritization.
In cases of more than one buffer having the same lowest priority, the message buffer with the lower index
number wins.
Access: User read/write(1)
Module Base + 0x00XD
7
6
5
4
3
2
1
0
PRIO7
PRIO6
PRIO5
PRIO4
PRIO3
PRIO2
PRIO1
PRIO0
0
0
0
0
0
0
0
0
R
W
Reset:
Figure 11-36. Transmit Buffer Priority Register (TBPR)
1. Read: Anytime when TXEx flag is set (see Section 11.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the
corresponding transmit buffer is selected in CANTBSEL (see Section 11.3.2.11, “MSCAN Transmit Buffer Selection Register
(CANTBSEL)”)
Write: Anytime when TXEx flag is set (see Section 11.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the
corresponding transmit buffer is selected in CANTBSEL (see Section 11.3.2.11, “MSCAN Transmit Buffer Selection Register
(CANTBSEL)”)
11.3.3.5
Time Stamp Register (TSRH–TSRL)
If the TIME bit is enabled, the MSCAN will write a time stamp to the respective registers in the active
transmit or receive buffer right after the EOF of a valid message on the CAN bus (see Section 11.3.2.1,
“MSCAN Control Register 0 (CANCTL0)”). In case of a transmission, the CPU can only read the time
stamp after the respective transmit buffer has been flagged empty.
The timer value, which is used for stamping, is taken from a free running internal CAN bit clock. A timer
overrun is not indicated by the MSCAN. The timer is reset (all bits set to 0) during initialization mode. The
CPU can only read the time stamp registers.
Access: User read/write(1)
Module Base + 0x00XE
R
7
6
5
4
3
2
1
0
TSR15
TSR14
TSR13
TSR12
TSR11
TSR10
TSR9
TSR8
x
x
x
x
x
x
x
x
W
Reset:
Figure 11-37. Time Stamp Register — High Byte (TSRH)
1. Read: For transmit buffers: Anytime when TXEx flag is set (see Section 11.3.2.7, “MSCAN Transmitter Flag Register
(CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 11.3.2.11, “MSCAN Transmit
Buffer Selection Register (CANTBSEL)”). For receive buffers: Anytime when RXF is set.
Write: Unimplemented
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
455
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Access: User read/write(1)
Module Base + 0x00XF
R
7
6
5
4
3
2
1
0
TSR7
TSR6
TSR5
TSR4
TSR3
TSR2
TSR1
TSR0
x
x
x
x
x
x
x
x
W
Reset:
Figure 11-38. Time Stamp Register — Low Byte (TSRL)
1. Read: or transmit buffers: Anytime when TXEx flag is set (see Section 11.3.2.7, “MSCAN Transmitter Flag Register
(CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 11.3.2.11, “MSCAN Transmit
Buffer Selection Register (CANTBSEL)”). For receive buffers: Anytime when RXF is set.
Write: Unimplemented
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
456
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.4
11.4.1
Functional Description
General
This section provides a complete functional description of the MSCAN.
11.4.2
Message Storage
CAN Receive / Transmit Engine
Memory Mapped I/O
Rx1
Rx2
Rx3
Rx4
RXF
Receiver
TxBG
Tx0
TxFG
Tx1
MSCAN
TxBG
Tx2
Transmitter
CPU bus
RxFG
MSCAN
RxBG
Rx0
TXE0
PRIO
TXE1
CPU bus
PRIO
TXE2
PRIO
Figure 11-39. User Model for Message Buffer Organization
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
457
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
The MSCAN facilitates a sophisticated message storage system which addresses the requirements of a
broad range of network applications.
11.4.2.1
Message Transmit Background
Modern application layer software is built upon two fundamental assumptions:
• Any CAN node is able to send out a stream of scheduled messages without releasing the CAN bus
between the two messages. Such nodes arbitrate for the CAN bus immediately after sending the
previous message and only release the CAN bus in case of lost arbitration.
• The internal message queue within any CAN node is organized such that the highest priority
message is sent out first, if more than one message is ready to be sent.
The behavior described in the bullets above cannot be achieved with a single transmit buffer. That buffer
must be reloaded immediately after the previous message is sent. This loading process lasts a finite amount
of time and must be completed within the inter-frame sequence (IFS) to be able to send an uninterrupted
stream of messages. Even if this is feasible for limited CAN bus speeds, it requires that the CPU reacts
with short latencies to the transmit interrupt.
A double buffer scheme de-couples the reloading of the transmit buffer from the actual message sending
and, therefore, reduces the reactiveness requirements of the CPU. Problems can arise if the sending of a
message is finished while the CPU re-loads the second buffer. No buffer would then be ready for
transmission, and the CAN bus would be released.
At least three transmit buffers are required to meet the first of the above requirements under all
circumstances. The MSCAN has three transmit buffers.
The second requirement calls for some sort of internal prioritization which the MSCAN implements with
the “local priority” concept described in Section 11.4.2.2, “Transmit Structures.”
11.4.2.2
Transmit Structures
The MSCAN triple transmit buffer scheme optimizes real-time performance by allowing multiple
messages to be set up in advance. The three buffers are arranged as shown in Figure 11-39.
All three buffers have a 13-byte data structure similar to the outline of the receive buffers (see
Section 11.3.3, “Programmer’s Model of Message Storage”). An additional Transmit Buffer Priority
Register (TBPR) contains an 8-bit local priority field (PRIO) (see Section 11.3.3.4, “Transmit Buffer
Priority Register (TBPR)”). The remaining two bytes are used for time stamping of a message, if required
(see Section 11.3.3.5, “Time Stamp Register (TSRH–TSRL)”).
To transmit a message, the CPU must identify an available transmit buffer, which is indicated by a set
transmitter buffer empty (TXEx) flag (see Section 11.3.2.7, “MSCAN Transmitter Flag Register
(CANTFLG)”). If a transmit buffer is available, the CPU must set a pointer to this buffer by writing to the
CANTBSEL register (see Section 11.3.2.11, “MSCAN Transmit Buffer Selection Register
(CANTBSEL)”). This makes the respective buffer accessible within the CANTXFG address space (see
Section 11.3.3, “Programmer’s Model of Message Storage”). The algorithmic feature associated with the
CANTBSEL register simplifies the transmit buffer selection. In addition, this scheme makes the handler
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
458
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
software simpler because only one address area is applicable for the transmit process, and the required
address space is minimized.
The CPU then stores the identifier, the control bits, and the data content into one of the transmit buffers.
Finally, the buffer is flagged as ready for transmission by clearing the associated TXE flag.
The MSCAN then schedules the message for transmission and signals the successful transmission of the
buffer by setting the associated TXE flag. A transmit interrupt (see Section 11.4.7.2, “Transmit Interrupt”)
is generated1 when TXEx is set and can be used to drive the application software to re-load the buffer.
If more than one buffer is scheduled for transmission when the CAN bus becomes available for arbitration,
the MSCAN uses the local priority setting of the three buffers to determine the prioritization. For this
purpose, every transmit buffer has an 8-bit local priority field (PRIO). The application software programs
this field when the message is set up. The local priority reflects the priority of this particular message
relative to the set of messages being transmitted from this node. The lowest binary value of the PRIO field
is defined to be the highest priority. The internal scheduling process takes place whenever the MSCAN
arbitrates for the CAN bus. This is also the case after the occurrence of a transmission error.
When a high priority message is scheduled by the application software, it may become necessary to abort
a lower priority message in one of the three transmit buffers. Because messages that are already in
transmission cannot be aborted, the user must request the abort by setting the corresponding abort request
bit (ABTRQ) (see Section 11.3.2.9, “MSCAN Transmitter Message Abort Request Register
(CANTARQ)”.) The MSCAN then grants the request, if possible, by:
1. Setting the corresponding abort acknowledge flag (ABTAK) in the CANTAAK register.
2. Setting the associated TXE flag to release the buffer.
3. Generating a transmit interrupt. The transmit interrupt handler software can determine from the
setting of the ABTAK flag whether the message was aborted (ABTAK = 1) or sent (ABTAK = 0).
11.4.2.3
Receive Structures
The received messages are stored in a five stage input FIFO. The five message buffers are alternately
mapped into a single memory area (see Figure 11-39). The background receive buffer (RxBG) is
exclusively associated with the MSCAN, but the foreground receive buffer (RxFG) is addressable by the
CPU (see Figure 11-39). This scheme simplifies the handler software because only one address area is
applicable for the receive process.
All receive buffers have a size of 15 bytes to store the CAN control bits, the identifier (standard or
extended), the data contents, and a time stamp, if enabled (see Section 11.3.3, “Programmer’s Model of
Message Storage”).
The receiver full flag (RXF) (see Section 11.3.2.5, “MSCAN Receiver Flag Register (CANRFLG)”)
signals the status of the foreground receive buffer. When the buffer contains a correctly received message
with a matching identifier, this flag is set.
On reception, each message is checked to see whether it passes the filter (see Section 11.4.3, “Identifier
Acceptance Filter”) and simultaneously is written into the active RxBG. After successful reception of a
valid message, the MSCAN shifts the content of RxBG into the receiver FIFO, sets the RXF flag, and
1. The transmit interrupt occurs only if not masked. A polling scheme can be applied on TXEx also.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
459
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
generates a receive interrupt1 (see Section 11.4.7.3, “Receive Interrupt”) to the CPU. The user’s receive
handler must read the received message from the RxFG and then reset the RXF flag to acknowledge the
interrupt and to release the foreground buffer. A new message, which can follow immediately after the IFS
field of the CAN frame, is received into the next available RxBG. If the MSCAN receives an invalid
message in its RxBG (wrong identifier, transmission errors, etc.) the actual contents of the buffer will be
over-written by the next message. The buffer will then not be shifted into the FIFO.
When the MSCAN module is transmitting, the MSCAN receives its own transmitted messages into the
background receive buffer, RxBG, but does not shift it into the receiver FIFO, generate a receive interrupt,
or acknowledge its own messages on the CAN bus. The exception to this rule is in loopback mode (see
Section 11.3.2.2, “MSCAN Control Register 1 (CANCTL1)”) where the MSCAN treats its own messages
exactly like all other incoming messages. The MSCAN receives its own transmitted messages in the event
that it loses arbitration. If arbitration is lost, the MSCAN must be prepared to become a receiver.
An overrun condition occurs when all receive message buffers in the FIFO are filled with correctly
received messages with accepted identifiers and another message is correctly received from the CAN bus
with an accepted identifier. The latter message is discarded and an error interrupt with overrun indication
is generated if enabled (see Section 11.4.7.5, “Error Interrupt”). The MSCAN remains able to transmit
messages while the receiver FIFO is being filled, but all incoming messages are discarded. As soon as a
receive buffer in the FIFO is available again, new valid messages will be accepted.
11.4.3
Identifier Acceptance Filter
The MSCAN identifier acceptance registers (see Section 11.3.2.12, “MSCAN Identifier Acceptance
Control Register (CANIDAC)”) define the acceptable patterns of the standard or extended identifier
(ID[10:0] or ID[28:0]). Any of these bits can be marked ‘don’t care’ in the MSCAN identifier mask
registers (see Section 11.3.2.18, “MSCAN Identifier Mask Registers (CANIDMR0–CANIDMR7)”).
A filter hit is indicated to the application software by a set receive buffer full flag (RXF = 1) and three bits
in the CANIDAC register (see Section 11.3.2.12, “MSCAN Identifier Acceptance Control Register
(CANIDAC)”). These identifier hit flags (IDHIT[2:0]) clearly identify the filter section that caused the
acceptance. They simplify the application software’s task to identify the cause of the receiver interrupt. If
more than one hit occurs (two or more filters match), the lower hit has priority.
A very flexible programmable generic identifier acceptance filter has been introduced to reduce the CPU
interrupt loading. The filter is programmable to operate in four different modes:
• Two identifier acceptance filters, each to be applied to:
— The full 29 bits of the extended identifier and to the following bits of the CAN 2.0B frame:
– Remote transmission request (RTR)
– Identifier extension (IDE)
– Substitute remote request (SRR)
— The 11 bits of the standard identifier plus the RTR and IDE bits of the CAN 2.0A/B messages.
This mode implements two filters for a full length CAN 2.0B compliant extended identifier.
Although this mode can be used for standard identifiers, it is recommended to use the four or
eight identifier acceptance filters.
1. The receive interrupt occurs only if not masked. A polling scheme can be applied on RXF also.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
460
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
•
•
•
Figure 11-40 shows how the first 32-bit filter bank (CANIDAR0–CANIDAR3,
CANIDMR0–CANIDMR3) produces a filter 0 hit. Similarly, the second filter bank
(CANIDAR4–CANIDAR7, CANIDMR4–CANIDMR7) produces a filter 1 hit.
Four identifier acceptance filters, each to be applied to:
— The 14 most significant bits of the extended identifier plus the SRR and IDE bits of CAN 2.0B
messages.
— The 11 bits of the standard identifier, the RTR and IDE bits of CAN 2.0A/B messages.
Figure 11-41 shows how the first 32-bit filter bank (CANIDAR0–CANIDAR3,
CANIDMR0–CANIDMR3) produces filter 0 and 1 hits. Similarly, the second filter bank
(CANIDAR4–CANIDAR7, CANIDMR4–CANIDMR7) produces filter 2 and 3 hits.
Eight identifier acceptance filters, each to be applied to the first 8 bits of the identifier. This mode
implements eight independent filters for the first 8 bits of a CAN 2.0A/B compliant standard
identifier or a CAN 2.0B compliant extended identifier.
Figure 11-42 shows how the first 32-bit filter bank (CANIDAR0–CANIDAR3,
CANIDMR0–CANIDMR3) produces filter 0 to 3 hits. Similarly, the second filter bank
(CANIDAR4–CANIDAR7, CANIDMR4–CANIDMR7) produces filter 4 to 7 hits.
Closed filter. No CAN message is copied into the foreground buffer RxFG, and the RXF flag is
never set.
CAN 2.0B
Extended Identifier ID28
IDR0
ID21
ID20
IDR1
CAN 2.0A/B
Standard Identifier ID10
IDR0
ID3
ID2
IDR1
ID15
IDE
ID14
IDR2
ID7
ID6
IDR3
RTR
ID10
IDR2
ID3
ID10
IDR3
ID3
AM7
CANIDMR0
AM0
AM7
CANIDMR1
AM0
AM7
CANIDMR2
AM0
AM7
CANIDMR3
AM0
AC7
CANIDAR0
AC0
AC7
CANIDAR1
AC0
AC7
CANIDAR2
AC0
AC7
CANIDAR3
AC0
ID Accepted (Filter 0 Hit)
Figure 11-40. 32-bit Maskable Identifier Acceptance Filter
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
461
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
CAN 2.0B
Extended Identifier
ID28
IDR0
ID21
ID20
IDR1
CAN 2.0A/B
Standard Identifier
ID10
IDR0
ID3
ID2
IDR1
AM7
CANIDMR0
AM0
AM7
CANIDMR1
AM0
AC7
CANIDAR0
AC0
AC7
CANIDAR1
AC0
ID15
IDE
ID14
IDR2
ID7
ID6
IDR3
RTR
ID10
IDR2
ID3
ID10
IDR3
ID3
ID Accepted (Filter 0 Hit)
AM7
CANIDMR2
AM0
AM7
CANIDMR3
AM0
AC7
CANIDAR2
AC0
AC7
CANIDAR3
AC0
ID Accepted (Filter 1 Hit)
Figure 11-41. 16-bit Maskable Identifier Acceptance Filters
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
462
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
CAN 2.0B
Extended Identifier ID28
IDR0
ID21
ID20
IDR1
CAN 2.0A/B
Standard Identifier ID10
IDR0
ID3
ID2
IDR1
AM7
CIDMR0
AM0
AC7
CIDAR0
AC0
ID15
IDE
ID14
IDR2
ID7
ID6
IDR3
RTR
ID10
IDR2
ID3
ID10
IDR3
ID3
ID Accepted (Filter 0 Hit)
AM7
CIDMR1
AM0
AC7
CIDAR1
AC0
ID Accepted (Filter 1 Hit)
AM7
CIDMR2
AM0
AC7
CIDAR2
AC0
ID Accepted (Filter 2 Hit)
AM7
CIDMR3
AM0
AC7
CIDAR3
AC0
ID Accepted (Filter 3 Hit)
Figure 11-42. 8-bit Maskable Identifier Acceptance Filters
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
463
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.4.3.1
Protocol Violation Protection
The MSCAN protects the user from accidentally violating the CAN protocol through programming errors.
The protection logic implements the following features:
• The receive and transmit error counters cannot be written or otherwise manipulated.
• All registers which control the configuration of the MSCAN cannot be modified while the MSCAN
is on-line. The MSCAN has to be in Initialization Mode. The corresponding INITRQ/INITAK
handshake bits in the CANCTL0/CANCTL1 registers (see Section 11.3.2.1, “MSCAN Control
Register 0 (CANCTL0)”) serve as a lock to protect the following registers:
— MSCAN control 1 register (CANCTL1)
— MSCAN bus timing registers 0 and 1 (CANBTR0, CANBTR1)
— MSCAN identifier acceptance control register (CANIDAC)
— MSCAN identifier acceptance registers (CANIDAR0–CANIDAR7)
— MSCAN identifier mask registers (CANIDMR0–CANIDMR7)
• The TXCAN is immediately forced to a recessive state when the MSCAN goes into the power
down mode or initialization mode (see Section 11.4.5.6, “MSCAN Power Down Mode,” and
Section 11.4.4.5, “MSCAN Initialization Mode”).
• The MSCAN enable bit (CANE) is writable only once in normal system operation modes, which
provides further protection against inadvertently disabling the MSCAN.
11.4.3.2
Clock System
Figure 11-43 shows the structure of the MSCAN clock generation circuitry.
MSCAN
Bus Clock
CANCLK
CLKSRC
Prescaler
(1 .. 64)
Time quanta clock (Tq)
CLKSRC
Oscillator Clock
Figure 11-43. MSCAN Clocking Scheme
The clock source bit (CLKSRC) in the CANCTL1 register (11.3.2.2/11-430) defines whether the internal
CANCLK is connected to the output of a crystal oscillator (oscillator clock) or to the bus clock.
The clock source has to be chosen such that the tight oscillator tolerance requirements (up to 0.4%) of the
CAN protocol are met. Additionally, for high CAN bus rates (1 Mbps), a 45% to 55% duty cycle of the
clock is required.
If the bus clock is generated from a PLL, it is recommended to select the oscillator clock rather than the
bus clock due to jitter considerations, especially at the faster CAN bus rates.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
464
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
For microcontrollers without a clock and reset generator (CRG), CANCLK is driven from the crystal
oscillator (oscillator clock).
A programmable prescaler generates the time quanta (Tq) clock from CANCLK. A time quantum is the
atomic unit of time handled by the MSCAN.
Eqn. 11-2
f CANCLK
=
----------------------------------------------------Tq ( Prescaler value -)
A bit time is subdivided into three segments as described in the Bosch CAN 2.0A/B specification. (see
Figure 11-44):
• SYNC_SEG: This segment has a fixed length of one time quantum. Signal edges are expected to
happen within this section.
• Time Segment 1: This segment includes the PROP_SEG and the PHASE_SEG1 of the CAN
standard. It can be programmed by setting the parameter TSEG1 to consist of 4 to 16 time quanta.
• Time Segment 2: This segment represents the PHASE_SEG2 of the CAN standard. It can be
programmed by setting the TSEG2 parameter to be 2 to 8 time quanta long.
Eqn. 11-3
f Tq
Bit Rate = --------------------------------------------------------------------------------( number of Time Quanta )
NRZ Signal
SYNC_SEG
Time Segment 1
(PROP_SEG + PHASE_SEG1)
Time Segment 2
(PHASE_SEG2)
1
4 ... 16
2 ... 8
8 ... 25 Time Quanta
= 1 Bit Time
Transmit Point
Sample Point
(single or triple sampling)
Figure 11-44. Segments within the Bit Time
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
465
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-35. Time Segment Syntax
Syntax
Description
System expects transitions to occur on the CAN bus during this
period.
SYNC_SEG
Transmit Point
A node in transmit mode transfers a new value to the CAN bus at
this point.
Sample Point
A node in receive mode samples the CAN bus at this point. If the
three samples per bit option is selected, then this point marks the
position of the third sample.
The synchronization jump width (see the Bosch CAN 2.0A/B specification for details) can be programmed
in a range of 1 to 4 time quanta by setting the SJW parameter.
The SYNC_SEG, TSEG1, TSEG2, and SJW parameters are set by programming the MSCAN bus timing
registers (CANBTR0, CANBTR1) (see Section 11.3.2.3, “MSCAN Bus Timing Register 0 (CANBTR0)”
and Section 11.3.2.4, “MSCAN Bus Timing Register 1 (CANBTR1)”).
Table 11-36 gives an overview of the Bosch CAN 2.0A/B specification compliant segment settings and the
related parameter values.
NOTE
It is the user’s responsibility to ensure the bit time settings are in compliance
with the CAN standard.
Table 11-36. Bosch CAN 2.0A/B Compliant Bit Time Segment Settings
Synchronization
Jump Width
Time Segment 1
TSEG1
Time Segment 2
TSEG2
5 .. 10
4 .. 9
2
1
1 .. 2
0 .. 1
4 .. 11
3 .. 10
3
2
1 .. 3
0 .. 2
5 .. 12
4 .. 11
4
3
1 .. 4
0 .. 3
6 .. 13
5 .. 12
5
4
1 .. 4
0 .. 3
7 .. 14
6 .. 13
6
5
1 .. 4
0 .. 3
8 .. 15
7 .. 14
7
6
1 .. 4
0 .. 3
9 .. 16
8 .. 15
8
7
1 .. 4
0 .. 3
11.4.4
11.4.4.1
SJW
Modes of Operation
Normal System Operating Modes
The MSCAN module behaves as described within this specification in all normal system operating modes.
Write restrictions exist for some registers.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
466
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.4.4.2
Special System Operating Modes
The MSCAN module behaves as described within this specification in all special system operating modes.
Write restrictions which exist on specific registers in normal modes are lifted for test purposes in special
modes.
11.4.4.3
Emulation Modes
In all emulation modes, the MSCAN module behaves just like in normal system operating modes as
described within this specification.
11.4.4.4
Listen-Only Mode
In an optional CAN bus monitoring mode (listen-only), the CAN node is able to receive valid data frames
and valid remote frames, but it sends only “recessive” bits on the CAN bus. In addition, it cannot start a
transmission.
If the MAC sub-layer is required to send a “dominant” bit (ACK bit, overload flag, or active error flag), the
bit is rerouted internally so that the MAC sub-layer monitors this “dominant” bit, although the CAN bus
may remain in recessive state externally.
11.4.4.5
MSCAN Initialization Mode
The MSCAN enters initialization mode when it is enabled (CANE=1).
When entering initialization mode during operation, any on-going transmission or reception is
immediately aborted and synchronization to the CAN bus is lost, potentially causing CAN protocol
violations. To protect the CAN bus system from fatal consequences of violations, the MSCAN
immediately drives TXCAN into a recessive state.
NOTE
The user is responsible for ensuring that the MSCAN is not active when
initialization mode is entered. The recommended procedure is to bring the
MSCAN into sleep mode (SLPRQ = 1 and SLPAK = 1) before setting the
INITRQ bit in the CANCTL0 register. Otherwise, the abort of an on-going
message can cause an error condition and can impact other CAN bus
devices.
In initialization mode, the MSCAN is stopped. However, interface registers remain accessible. This mode
is used to reset the CANCTL0, CANRFLG, CANRIER, CANTFLG, CANTIER, CANTARQ,
CANTAAK, and CANTBSEL registers to their default values. In addition, the MSCAN enables the
configuration of the CANBTR0, CANBTR1 bit timing registers; CANIDAC; and the CANIDAR,
CANIDMR message filters. See Section 11.3.2.1, “MSCAN Control Register 0 (CANCTL0),” for a
detailed description of the initialization mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
467
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Bus Clock Domain
CAN Clock Domain
INITRQ
SYNC
sync.
INITRQ
sync.
SYNC
INITAK
CPU
Init Request
INITAK
Flag
INITAK
INIT
Flag
Figure 11-45. Initialization Request/Acknowledge Cycle
Due to independent clock domains within the MSCAN, INITRQ must be synchronized to all domains by
using a special handshake mechanism. This handshake causes additional synchronization delay (see
Figure 11-45).
If there is no message transfer ongoing on the CAN bus, the minimum delay will be two additional bus
clocks and three additional CAN clocks. When all parts of the MSCAN are in initialization mode, the
INITAK flag is set. The application software must use INITAK as a handshake indication for the request
(INITRQ) to go into initialization mode.
NOTE
The CPU cannot clear INITRQ before initialization mode (INITRQ = 1 and
INITAK = 1) is active.
11.4.5
Low-Power Options
If the MSCAN is disabled (CANE = 0), the MSCAN clocks are stopped for power saving.
If the MSCAN is enabled (CANE = 1), the MSCAN has two additional modes with reduced power
consumption, compared to normal mode: sleep and power down mode. In sleep mode, power consumption
is reduced by stopping all clocks except those to access the registers from the CPU side. In power down
mode, all clocks are stopped and no power is consumed.
Table 11-37 summarizes the combinations of MSCAN and CPU modes. A particular combination of
modes is entered by the given settings on the CSWAI and SLPRQ/SLPAK bits.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
468
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
Table 11-37. CPU vs. MSCAN Operating Modes
MSCAN Mode
Reduced Power Consumption
CPU Mode
Normal
Sleep
RUN
CSWAI = X(1)
SLPRQ = 0
SLPAK = 0
CSWAI = X
SLPRQ = 1
SLPAK = 1
WAIT
CSWAI = 0
SLPRQ = 0
SLPAK = 0
CSWAI = 0
SLPRQ = 1
SLPAK = 1
STOP
Power Down
Disabled
(CANE=0)
CSWAI = X
SLPRQ = X
SLPAK = X
CSWAI = 1
SLPRQ = X
SLPAK = X
CSWAI = X
SLPRQ = X
SLPAK = X
CSWAI = X
SLPRQ = X
SLPAK = X
CSWAI = X
SLPRQ = X
SLPAK = X
1. ‘X’ means don’t care.
11.4.5.1
Operation in Run Mode
As shown in Table 11-37, only MSCAN sleep mode is available as low power option when the CPU is in
run mode.
11.4.5.2
Operation in Wait Mode
The WAI instruction puts the MCU in a low power consumption stand-by mode. If the CSWAI bit is set,
additional power can be saved in power down mode because the CPU clocks are stopped. After leaving
this power down mode, the MSCAN restarts and enters normal mode again.
While the CPU is in wait mode, the MSCAN can be operated in normal mode and generate interrupts
(registers can be accessed via background debug mode).
11.4.5.3
Operation in Stop Mode
The STOP instruction puts the MCU in a low power consumption stand-by mode. In stop mode, the
MSCAN is set in power down mode regardless of the value of the SLPRQ/SLPAK and CSWAI bits
(Table 11-37).
11.4.5.4
MSCAN Normal Mode
This is a non-power-saving mode. Enabling the MSCAN puts the module from disabled mode into normal
mode. In this mode the module can either be in initialization mode or out of initialization mode. See
Section 11.4.4.5, “MSCAN Initialization Mode”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
469
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.4.5.5
MSCAN Sleep Mode
The CPU can request the MSCAN to enter this low power mode by asserting the SLPRQ bit in the
CANCTL0 register. The time when the MSCAN enters sleep mode depends on a fixed synchronization
delay and its current activity:
• If there are one or more message buffers scheduled for transmission (TXEx = 0), the MSCAN will
continue to transmit until all transmit message buffers are empty (TXEx = 1, transmitted
successfully or aborted) and then goes into sleep mode.
• If the MSCAN is receiving, it continues to receive and goes into sleep mode as soon as the CAN
bus next becomes idle.
• If the MSCAN is neither transmitting nor receiving, it immediately goes into sleep mode.
Bus Clock Domain
CAN Clock Domain
SLPRQ
SYNC
sync.
SLPRQ
sync.
SYNC
SLPAK
CPU
Sleep Request
SLPAK
Flag
SLPAK
SLPRQ
Flag
MSCAN
in Sleep Mode
Figure 11-46. Sleep Request / Acknowledge Cycle
NOTE
The application software must avoid setting up a transmission (by clearing
one or more TXEx flag(s)) and immediately request sleep mode (by setting
SLPRQ). Whether the MSCAN starts transmitting or goes into sleep mode
directly depends on the exact sequence of operations.
If sleep mode is active, the SLPRQ and SLPAK bits are set (Figure 11-46). The application software must
use SLPAK as a handshake indication for the request (SLPRQ) to go into sleep mode.
When in sleep mode (SLPRQ = 1 and SLPAK = 1), the MSCAN stops its internal clocks. However, clocks
that allow register accesses from the CPU side continue to run.
If the MSCAN is in bus-off state, it stops counting the 128 occurrences of 11 consecutive recessive bits
due to the stopped clocks. TXCAN remains in a recessive state. If RXF = 1, the message can be read and
RXF can be cleared. Shifting a new message into the foreground buffer of the receiver FIFO (RxFG) does
not take place while in sleep mode.
It is possible to access the transmit buffers and to clear the associated TXE flags. No message abort takes
place while in sleep mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
470
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
If the WUPE bit in CANCTL0 is not asserted, the MSCAN will mask any activity it detects on CAN.
RXCAN is therefore held internally in a recessive state. This locks the MSCAN in sleep mode. WUPE
must be set before entering sleep mode to take effect.
The MSCAN is able to leave sleep mode (wake up) only when:
• CAN bus activity occurs and WUPE = 1
or
• the CPU clears the SLPRQ bit
NOTE
The CPU cannot clear the SLPRQ bit before sleep mode (SLPRQ = 1 and
SLPAK = 1) is active.
After wake-up, the MSCAN waits for 11 consecutive recessive bits to synchronize to the CAN bus. As a
consequence, if the MSCAN is woken-up by a CAN frame, this frame is not received.
The receive message buffers (RxFG and RxBG) contain messages if they were received before sleep mode
was entered. All pending actions will be executed upon wake-up; copying of RxBG into RxFG, message
aborts and message transmissions. If the MSCAN remains in bus-off state after sleep mode was exited, it
continues counting the 128 occurrences of 11 consecutive recessive bits.
11.4.5.6
MSCAN Power Down Mode
The MSCAN is in power down mode (Table 11-37) when
• CPU is in stop mode
or
• CPU is in wait mode and the CSWAI bit is set
When entering the power down mode, the MSCAN immediately stops all ongoing transmissions and
receptions, potentially causing CAN protocol violations. To protect the CAN bus system from fatal
consequences of violations to the above rule, the MSCAN immediately drives TXCAN into a recessive
state.
NOTE
The user is responsible for ensuring that the MSCAN is not active when
power down mode is entered. The recommended procedure is to bring the
MSCAN into Sleep mode before the STOP or WAI instruction (if CSWAI
is set) is executed. Otherwise, the abort of an ongoing message can cause an
error condition and impact other CAN bus devices.
In power down mode, all clocks are stopped and no registers can be accessed. If the MSCAN was not in
sleep mode before power down mode became active, the module performs an internal recovery cycle after
powering up. This causes some fixed delay before the module enters normal mode again.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
471
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.4.5.7
Disabled Mode
The MSCAN is in disabled mode out of reset (CANE=0). All module clocks are stopped for power saving,
however the register map can still be accessed as specified.
11.4.5.8
Programmable Wake-Up Function
The MSCAN can be programmed to wake up from sleep or power down mode as soon as CAN bus activity
is detected (see control bit WUPE in MSCAN Control Register 0 (CANCTL0). The sensitivity to existing
CAN bus action can be modified by applying a low-pass filter function to the RXCAN input line (see
control bit WUPM in Section 11.3.2.2, “MSCAN Control Register 1 (CANCTL1)”).
This feature can be used to protect the MSCAN from wake-up due to short glitches on the CAN bus lines.
Such glitches can result from—for example—electromagnetic interference within noisy environments.
11.4.6
Reset Initialization
The reset state of each individual bit is listed in Section 11.3.2, “Register Descriptions,” which details all
the registers and their bit-fields.
11.4.7
Interrupts
This section describes all interrupts originated by the MSCAN. It documents the enable bits and generated
flags. Each interrupt is listed and described separately.
11.4.7.1
Description of Interrupt Operation
The MSCAN supports four interrupt vectors (see Table 11-38), any of which can be individually masked
(for details see Section 11.3.2.6, “MSCAN Receiver Interrupt Enable Register (CANRIER)” to
Section 11.3.2.8, “MSCAN Transmitter Interrupt Enable Register (CANTIER)”).
Refer to the device overview section to determine the dedicated interrupt vector addresses.
Table 11-38. Interrupt Vectors
Interrupt Source
Wake-Up Interrupt (WUPIF)
11.4.7.2
CCR Mask
I bit
Local Enable
CANRIER (WUPIE)
Error Interrupts Interrupt (CSCIF, OVRIF)
I bit
CANRIER (CSCIE, OVRIE)
Receive Interrupt (RXF)
I bit
CANRIER (RXFIE)
Transmit Interrupts (TXE[2:0])
I bit
CANTIER (TXEIE[2:0])
Transmit Interrupt
At least one of the three transmit buffers is empty (not scheduled) and can be loaded to schedule a message
for transmission. The TXEx flag of the empty message buffer is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
472
Freescale Semiconductor
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.4.7.3
Receive Interrupt
A message is successfully received and shifted into the foreground buffer (RxFG) of the receiver FIFO.
This interrupt is generated immediately after receiving the EOF symbol. The RXF flag is set. If there are
multiple messages in the receiver FIFO, the RXF flag is set as soon as the next message is shifted to the
foreground buffer.
11.4.7.4
Wake-Up Interrupt
A wake-up interrupt is generated if activity on the CAN bus occurs during MSCAN sleep or power-down
mode.
NOTE
This interrupt can only occur if the MSCAN was in sleep mode (SLPRQ = 1
and SLPAK = 1) before entering power down mode, the wake-up option is
enabled (WUPE = 1), and the wake-up interrupt is enabled (WUPIE = 1).
11.4.7.5
Error Interrupt
An error interrupt is generated if an overrun of the receiver FIFO, error, warning, or bus-off condition
occurs. MSCAN Receiver Flag Register (CANRFLG) indicates one of the following conditions:
• Overrun — An overrun condition of the receiver FIFO as described in Section 11.4.2.3, “Receive
Structures,” occurred.
• CAN Status Change — The actual value of the transmit and receive error counters control the
CAN bus state of the MSCAN. As soon as the error counters skip into a critical range (Tx/Rxwarning, Tx/Rx-error, bus-off) the MSCAN flags an error condition. The status change, which
caused the error condition, is indicated by the TSTAT and RSTAT flags (see Section 11.3.2.5,
“MSCAN Receiver Flag Register (CANRFLG)” and Section 11.3.2.6, “MSCAN Receiver
Interrupt Enable Register (CANRIER)”).
11.4.7.6
Interrupt Acknowledge
Interrupts are directly associated with one or more status flags in either the MSCAN Receiver Flag Register
(CANRFLG) or the MSCAN Transmitter Flag Register (CANTFLG). Interrupts are pending as long as
one of the corresponding flags is set. The flags in CANRFLG and CANTFLG must be reset within the
interrupt handler to handshake the interrupt. The flags are reset by writing a 1 to the corresponding bit
position. A flag cannot be cleared if the respective condition prevails.
NOTE
It must be guaranteed that the CPU clears only the bit causing the current
interrupt. For this reason, bit manipulation instructions (BSET) must not be
used to clear interrupt flags. These instructions may cause accidental
clearing of interrupt flags which are set after entering the current interrupt
service routine.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
473
Chapter 11 Freescale’s Scalable Controller Area Network (S12MSCANV3)
11.5
11.5.1
Initialization/Application Information
MSCAN initialization
The procedure to initially start up the MSCAN module out of reset is as follows:
1. Assert CANE
2. Write to the configuration registers in initialization mode
3. Clear INITRQ to leave initialization mode
If the configuration of registers which are only writable in initialization mode shall be changed:
1. Bring the module into sleep mode by setting SLPRQ and awaiting SLPAK to assert after the CAN
bus becomes idle.
2. Enter initialization mode: assert INITRQ and await INITAK
3. Write to the configuration registers in initialization mode
4. Clear INITRQ to leave initialization mode and continue
11.5.2
Bus-Off Recovery
The bus-off recovery is user configurable. The bus-off state can either be left automatically or on user
request.
For reasons of backwards compatibility, the MSCAN defaults to automatic recovery after reset. In this
case, the MSCAN will become error active again after counting 128 occurrences of 11 consecutive
recessive bits on the CAN bus (see the Bosch CAN 2.0 A/B specification for details).
If the MSCAN is configured for user request (BORM set in MSCAN Control Register 1 (CANCTL1)), the
recovery from bus-off starts after both independent events have become true:
• 128 occurrences of 11 consecutive recessive bits on the CAN bus have been monitored
• BOHOLD in MSCAN Miscellaneous Register (CANMISC) has been cleared by the user
These two events may occur in any order.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
474
Freescale Semiconductor
Chapter 12
Serial Communication Interface (S12SCIV6)
Table 12-1. Revision History
Version Revision Effective
Number
Date
Date
05.03 12/25/2008
05.04
08/05/2009
05.05
06/03/2010
06.01
05/29/2012
06.02
10/17/2012
06.03
06.04
10/25/2012
12/19/2012
06.05
02/22/2013
06.06
03/11/2013
06.07
09/03/2013
06.08
10/14/2013
12.1
Author
Description of Changes
remove redundancy comments in Figure1-2
fix typo, SCIBDL reset value be 0x04, not 0x00
fix typo, Table 12-3,SCICR1 Even parity should be PT=0
fix typo, on page 12-498,should be BKDIF,not BLDIF
update register map, change BD,move IREN to SCIACR2
fix typo on page 12-480 and on page 12-480;fix typo of
version V6
update fast data tolerance calculation and add notes.
fix typo Table 12-2, SBR[15:4],not SBR[15:0]
fix typo Table 12-6,12.4.1/12-493
fix typo Figure 12-1./12-477 Figure 12-4./12-480
update Table 12-2./12-480 12.4.4/12-495 12.4.6.3/12-502
fix typo of BDL reset value,Figure 12-4
fix typo of Table 12-2,Table 12-16,reword 12.4.4/12-495
update Figure 12-14./12-492 Figure 12-16./12-496
Figure 12-20./12-501
update 12.4.4/12-495,more detail for two baud
add note for Table 12-16./12-495
update Figure 12-2./12-479,Figure 12-12./12-490
update Figure 12-4./12-480 12.3.2.9/12-490
Introduction
This block guide provides an overview of the serial communication interface (SCI) module.
The SCI allows asynchronous serial communications with peripheral devices and other CPUs.
12.1.1
Glossary
IR: InfraRed
IrDA: Infrared Design Associate
IRQ: Interrupt Request
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
475
Chapter 12 Serial Communication Interface (S12SCIV6)
LIN: Local Interconnect Network
LSB: Least Significant Bit
MSB: Most Significant Bit
NRZ: Non-Return-to-Zero
RZI: Return-to-Zero-Inverted
RXD: Receive Pin
SCI : Serial Communication Interface
TXD: Transmit Pin
12.1.2
Features
The SCI includes these distinctive features:
• Full-duplex or single-wire operation
• Standard mark/space non-return-to-zero (NRZ) format
• Selectable IrDA 1.4 return-to-zero-inverted (RZI) format with programmable pulse widths
• 16-bit baud rate selection
• Programmable 8-bit or 9-bit data format
• Separately enabled transmitter and receiver
• Programmable polarity for transmitter and receiver
• Programmable transmitter output parity
• Two receiver wakeup methods:
— Idle line wakeup
— Address mark wakeup
• Interrupt-driven operation with eight flags:
— Transmitter empty
— Transmission complete
— Receiver full
— Idle receiver input
— Receiver overrun
— Noise error
— Framing error
— Parity error
— Receive wakeup on active edge
— Transmit collision detect supporting LIN
— Break Detect supporting LIN
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
476
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
•
•
•
Receiver framing error detection
Hardware parity checking
1/16 bit-time noise detection
12.1.3
Modes of Operation
The SCI functions the same in normal, special, and emulation modes. It has two low power modes, wait
and stop modes.
• Run mode
• Wait mode
• Stop mode
12.1.4
Block Diagram
Figure 12-1 is a high level block diagram of the SCI module, showing the interaction of various function
blocks.
SCI Data Register
RXD Data In
Bus Clock
Infrared
Decoder
Receive Shift Register
Receive
Receive & Wakeup
Control
Baud Rate
IDLE
Receive
RDRF/OR
Interrupt
Generation BRKD
Generator
RXEDG
BERR
Data Format Control
Transmit
Baud Rate
Generator
1/16
Transmit Control
Transmit Shift Register
SCI
Interrupt
Request
Transmit
TDRE
Interrupt
Generation TC
Infrared
Encoder
Data Out TXD
SCI Data Register
Figure 12-1. SCI Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
477
Chapter 12 Serial Communication Interface (S12SCIV6)
12.2
External Signal Description
The SCI module has a total of two external pins.
12.2.1
TXD — Transmit Pin
The TXD pin transmits SCI (standard or infrared) data. It will idle high in either mode and is high
impedance anytime the transmitter is disabled.
12.2.2
RXD — Receive Pin
The RXD pin receives SCI (standard or infrared) data. An idle line is detected as a line high. This input is
ignored when the receiver is disabled and should be terminated to a known voltage.
12.3
Memory Map and Register Definition
This section provides a detailed description of all the SCI registers.
12.3.1
Module Memory Map and Register Definition
The memory map for the SCI module is given below in Figure 12-2. The address listed for each register is
the address offset. The total address for each register is the sum of the base address for the SCI module and
the address offset for each register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
478
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2
Register Descriptions
This section consists of register descriptions in address order. Each description includes a standard register
diagram with an associated figure number. Writes to a reserved register locations do not have any effect
and reads of these locations return a zero. Details of register bit and field function follow the register
diagrams, in bit order.
Register
Name
0x0000
SCIBDH1
W
0x0001
SCIBDL1
W
0x0002
SCICR11
R
R
R
W
0x0000
SCIASR12
W
0x0001
SCIACR12
W
0x0002
SCIACR22
0x0003
SCICR2
0x0004
SCISR1
0x0005
SCISR2
0x0006
SCIDRH
0x0007
SCIDRL
R
R
R
W
R
W
R
Bit 7
6
5
4
3
2
1
Bit 0
SBR15
SBR14
SBR13
SBR12
SBR11
SBR10
SBR9
SBR8
SBR7
SBR6
SBR5
SBR4
SBR3
SBR2
SBR1
SBR0
LOOPS
SCISWAI
RSRC
M
WAKE
ILT
PE
PT
0
0
0
0
BERRV
BERRIF
BKDIF
0
0
0
0
BERRIE
BKDIE
IREN
TNP1
TNP0
0
0
BERRM1
BERRM0
BKDFE
TIE
TCIE
RIE
ILIE
TE
RE
RWU
SBK
TDRE
TC
RDRF
IDLE
OR
NF
FE
PF
0
0
TXPOL
RXPOL
BRK13
TXDIR
0
0
0
Reserved
Reserved
Reserved
RXEDGIF
RXEDGIE
0
W
R
W
R
AMAP
R8
W
T8
RAF
R
R7
R6
R5
R4
R3
R2
R1
R0
W
T7
T6
T5
T4
T3
T2
T1
T0
1.These registers are accessible if the AMAP bit in the SCISR2 register is set to zero.
2,These registers are accessible if the AMAP bit in the SCISR2 register is set to one.
= Unimplemented or Reserved
Figure 12-2. SCI Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
479
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.1
SCI Baud Rate Registers (SCIBDH, SCIBDL)
Module Base + 0x0000
R
W
Reset
7
6
5
4
3
2
1
0
SBR15
SBR14
SBR13
SBR12
SBR11
SBR10
SBR9
SBR8
0
0
0
0
0
0
0
0
Figure 12-3. SCI Baud Rate Register (SCIBDH)
Module Base + 0x0001
R
W
Reset
7
6
5
4
3
2
1
0
SBR7
SBR6
SBR5
SBR4
SBR3
SBR2
SBR1
SBR0
0
1
0
0
0
0
0
0
Figure 12-4. SCI Baud Rate Register (SCIBDL)
Read: Anytime, if AMAP = 0.
Write: Anytime, if AMAP = 0.
NOTE
Those two registers are only visible in the memory map if AMAP = 0 (reset
condition).
The SCI baud rate register is used by to determine the baud rate of the SCI, and to control the infrared
modulation/demodulation submodule.
Table 12-2. SCIBDH and SCIBDL Field Descriptions
Field
Description
SBR[15:0]
SCI Baud Rate Bits — The baud rate for the SCI is determined by the bits in this register. The baud rate is
calculated two different ways depending on the state of the IREN bit.
The formulas for calculating the baud rate are:
When IREN = 0 then,
SCI baud rate = SCI bus clock / (SBR[15:0])
When IREN = 1 then,
SCI baud rate = SCI bus clock / (2 x SBR[15:1])
Note: The baud rate generator is disabled after reset and not started until the TE bit or the RE bit is set for the
first time. The baud rate generator is disabled when (SBR[15:4] = 0 and IREN = 0) or (SBR[15:5] = 0 and
IREN = 1).
Note: . User should write SCIBD by word access. The updated SCIBD may take effect until next RT clock start,
write SCIBDH or SCIBDL separately may cause baud generator load wrong data at that time,if second
write later then RT clock.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
480
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.2
SCI Control Register 1 (SCICR1)
Module Base + 0x0002
R
W
Reset
7
6
5
4
3
2
1
0
LOOPS
SCISWAI
RSRC
M
WAKE
ILT
PE
PT
0
0
0
0
0
0
0
0
Figure 12-5. SCI Control Register 1 (SCICR1)
Read: Anytime, if AMAP = 0.
Write: Anytime, if AMAP = 0.
NOTE
This register is only visible in the memory map if AMAP = 0 (reset
condition).
Table 12-3. SCICR1 Field Descriptions
Field
Description
7
LOOPS
Loop Select Bit — LOOPS enables loop operation. In loop operation, the RXD pin is disconnected from the SCI
and the transmitter output is internally connected to the receiver input. Both the transmitter and the receiver must
be enabled to use the loop function.
0 Normal operation enabled
1 Loop operation enabled
The receiver input is determined by the RSRC bit.
6
SCISWAI
5
RSRC
4
M
SCI Stop in Wait Mode Bit — SCISWAI disables the SCI in wait mode.
0 SCI enabled in wait mode
1 SCI disabled in wait mode
Receiver Source Bit — When LOOPS = 1, the RSRC bit determines the source for the receiver shift register
input. See Table 12-4.
0 Receiver input internally connected to transmitter output
1 Receiver input connected externally to transmitter
Data Format Mode Bit — MODE determines whether data characters are eight or nine bits long.
0 One start bit, eight data bits, one stop bit
1 One start bit, nine data bits, one stop bit
3
WAKE
Wakeup Condition Bit — WAKE determines which condition wakes up the SCI: a logic 1 (address mark) in the
most significant bit position of a received data character or an idle condition on the RXD pin.
0 Idle line wakeup
1 Address mark wakeup
2
ILT
Idle Line Type Bit — ILT determines when the receiver starts counting logic 1s as idle character bits. The
counting begins either after the start bit or after the stop bit. If the count begins after the start bit, then a string of
logic 1s preceding the stop bit may cause false recognition of an idle character. Beginning the count after the
stop bit avoids false idle character recognition, but requires properly synchronized transmissions.
0 Idle character bit count begins after start bit
1 Idle character bit count begins after stop bit
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
481
Chapter 12 Serial Communication Interface (S12SCIV6)
Table 12-3. SCICR1 Field Descriptions (continued)
Field
Description
1
PE
Parity Enable Bit — PE enables the parity function. When enabled, the parity function inserts a parity bit in the
most significant bit position.
0 Parity function disabled
1 Parity function enabled
0
PT
Parity Type Bit — PT determines whether the SCI generates and checks for even parity or odd parity. With even
parity, an even number of 1s clears the parity bit and an odd number of 1s sets the parity bit. With odd parity, an
odd number of 1s clears the parity bit and an even number of 1s sets the parity bit.
0 Even parity
1 Odd parity
Table 12-4. Loop Functions
LOOPS
RSRC
Function
0
x
Normal operation
1
0
Loop mode with transmitter output internally connected to receiver input
1
1
Single-wire mode with TXD pin connected to receiver input
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
482
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.3
SCI Alternative Status Register 1 (SCIASR1)
Module Base + 0x0000
7
R
W
Reset
RXEDGIF
0
6
5
4
3
2
0
0
0
0
BERRV
0
0
0
0
0
1
0
BERRIF
BKDIF
0
0
= Unimplemented or Reserved
Figure 12-6. SCI Alternative Status Register 1 (SCIASR1)
Read: Anytime, if AMAP = 1
Write: Anytime, if AMAP = 1
Table 12-5. SCIASR1 Field Descriptions
Field
7
RXEDGIF
Description
Receive Input Active Edge Interrupt Flag — RXEDGIF is asserted, if an active edge (falling if RXPOL = 0,
rising if RXPOL = 1) on the RXD input occurs. RXEDGIF bit is cleared by writing a “1” to it.
0 No active receive on the receive input has occurred
1 An active edge on the receive input has occurred
2
BERRV
Bit Error Value — BERRV reflects the state of the RXD input when the bit error detect circuitry is enabled and
a mismatch to the expected value happened. The value is only meaningful, if BERRIF = 1.
0 A low input was sampled, when a high was expected
1 A high input reassembled, when a low was expected
1
BERRIF
Bit Error Interrupt Flag — BERRIF is asserted, when the bit error detect circuitry is enabled and if the value
sampled at the RXD input does not match the transmitted value. If the BERRIE interrupt enable bit is set an
interrupt will be generated. The BERRIF bit is cleared by writing a “1” to it.
0 No mismatch detected
1 A mismatch has occurred
0
BKDIF
Break Detect Interrupt Flag — BKDIF is asserted, if the break detect circuitry is enabled and a break signal is
received. If the BKDIE interrupt enable bit is set an interrupt will be generated. The BKDIF bit is cleared by writing
a “1” to it.
0 No break signal was received
1 A break signal was received
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
483
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.4
SCI Alternative Control Register 1 (SCIACR1)
Module Base + 0x0001
7
R
W
Reset
RXEDGIE
0
6
5
4
3
2
0
0
0
0
0
0
0
0
0
0
1
0
BERRIE
BKDIE
0
0
= Unimplemented or Reserved
Figure 12-7. SCI Alternative Control Register 1 (SCIACR1)
Read: Anytime, if AMAP = 1
Write: Anytime, if AMAP = 1
Table 12-6. SCIACR1 Field Descriptions
Field
Description
7
RXEDGIE
Receive Input Active Edge Interrupt Enable — RXEDGIE enables the receive input active edge interrupt flag,
RXEDGIF, to generate interrupt requests.
0 RXEDGIF interrupt requests disabled
1 RXEDGIF interrupt requests enabled
1
BERRIE
0
BKDIE
Bit Error Interrupt Enable — BERRIE enables the bit error interrupt flag, BERRIF, to generate interrupt
requests.
0 BERRIF interrupt requests disabled
1 BERRIF interrupt requests enabled
Break Detect Interrupt Enable — BKDIE enables the break detect interrupt flag, BKDIF, to generate interrupt
requests.
0 BKDIF interrupt requests disabled
1 BKDIF interrupt requests enabled
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
484
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.5
SCI Alternative Control Register 2 (SCIACR2)
Module Base + 0x0002
R
W
Reset
7
6
5
IREN
TNP1
TNP0
0
0
0
4
3
0
0
0
0
2
1
0
BERRM1
BERRM0
BKDFE
0
0
0
= Unimplemented or Reserved
Figure 12-8. SCI Alternative Control Register 2 (SCIACR2)
Read: Anytime, if AMAP = 1
Write: Anytime, if AMAP = 1
Table 12-7. SCIACR2 Field Descriptions
Field
7
IREN
6:5
TNP[1:0]
Description
Infrared Enable Bit — This bit enables/disables the infrared modulation/demodulation submodule.
0 IR disabled
1 IR enabled
Transmitter Narrow Pulse Bits — These bits enable whether the SCI transmits a 1/16, 3/16, 1/32 or 1/4 narrow
pulse. See Table 12-8.
2:1
Bit Error Mode — Those two bits determines the functionality of the bit error detect feature. See Table 12-9.
BERRM[1:0]
0
BKDFE
Break Detect Feature Enable — BKDFE enables the break detect circuitry.
0 Break detect circuit disabled
1 Break detect circuit enabled
Table 12-8. IRSCI Transmit Pulse Width
TNP[1:0]
Narrow Pulse Width
11
1/4
10
1/32
01
1/16
00
3/16
Table 12-9. Bit Error Mode Coding
BERRM1
BERRM0
Function
0
0
Bit error detect circuit is disabled
0
1
Receive input sampling occurs during the 9th time tick of a transmitted bit
(refer to Figure 12-19)
1
0
Receive input sampling occurs during the 13th time tick of a transmitted bit
(refer to Figure 12-19)
1
1
Reserved
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
485
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.6
SCI Control Register 2 (SCICR2)
Module Base + 0x0003
R
W
Reset
7
6
5
4
3
2
1
0
TIE
TCIE
RIE
ILIE
TE
RE
RWU
SBK
0
0
0
0
0
0
0
0
Figure 12-9. SCI Control Register 2 (SCICR2)
Read: Anytime
Write: Anytime
Table 12-10. SCICR2 Field Descriptions
Field
7
TIE
Description
Transmitter Interrupt Enable Bit — TIE enables the transmit data register empty flag, TDRE, to generate
interrupt requests.
0 TDRE interrupt requests disabled
1 TDRE interrupt requests enabled
6
TCIE
Transmission Complete Interrupt Enable Bit — TCIE enables the transmission complete flag, TC, to generate
interrupt requests.
0 TC interrupt requests disabled
1 TC interrupt requests enabled
5
RIE
Receiver Full Interrupt Enable Bit — RIE enables the receive data register full flag, RDRF, or the overrun flag,
OR, to generate interrupt requests.
0 RDRF and OR interrupt requests disabled
1 RDRF and OR interrupt requests enabled
4
ILIE
Idle Line Interrupt Enable Bit — ILIE enables the idle line flag, IDLE, to generate interrupt requests.
0 IDLE interrupt requests disabled
1 IDLE interrupt requests enabled
3
TE
Transmitter Enable Bit — TE enables the SCI transmitter and configures the TXD pin as being controlled by
the SCI. The TE bit can be used to queue an idle preamble.
0 Transmitter disabled
1 Transmitter enabled
2
RE
Receiver Enable Bit — RE enables the SCI receiver.
0 Receiver disabled
1 Receiver enabled
1
RWU
Receiver Wakeup Bit — Standby state
0 Normal operation.
1 RWU enables the wakeup function and inhibits further receiver interrupt requests. Normally, hardware wakes
the receiver by automatically clearing RWU.
0
SBK
Send Break Bit — Toggling SBK sends one break character (10 or 11 logic 0s, respectively 13 or 14 logics 0s
if BRK13 is set). Toggling implies clearing the SBK bit before the break character has finished transmitting. As
long as SBK is set, the transmitter continues to send complete break characters (10 or 11 bits, respectively 13
or 14 bits).
0 No break characters
1 Transmit break characters
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
486
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.7
SCI Status Register 1 (SCISR1)
The SCISR1 and SCISR2 registers provides inputs to the MCU for generation of SCI interrupts. Also,
these registers can be polled by the MCU to check the status of these bits. The flag-clearing procedures
require that the status register be read followed by a read or write to the SCI data register.It is permissible
to execute other instructions between the two steps as long as it does not compromise the handling of I/O,
but the order of operations is important for flag clearing.
Module Base + 0x0004
R
7
6
5
4
3
2
1
0
TDRE
TC
RDRF
IDLE
OR
NF
FE
PF
1
0
0
0
0
0
0
W
Reset
1
= Unimplemented or Reserved
Figure 12-10. SCI Status Register 1 (SCISR1)
Read: Anytime
Write: Has no meaning or effect
Table 12-11. SCISR1 Field Descriptions
Field
Description
7
TDRE
Transmit Data Register Empty Flag — TDRE is set when the transmit shift register receives a byte from the
SCI data register. When TDRE is 1, the transmit data register (SCIDRH/L) is empty and can receive a new value
to transmit.Clear TDRE by reading SCI status register 1 (SCISR1), with TDRE set and then writing to SCI data
register low (SCIDRL).
0 No byte transferred to transmit shift register
1 Byte transferred to transmit shift register; transmit data register empty
6
TC
Transmit Complete Flag — TC is set low when there is a transmission in progress or when a preamble or break
character is loaded. TC is set high when the TDRE flag is set and no data, preamble, or break character is being
transmitted.When TC is set, the TXD pin becomes idle (logic 1). Clear TC by reading SCI status register 1
(SCISR1) with TC set and then writing to SCI data register low (SCIDRL). TC is cleared automatically when data,
preamble, or break is queued and ready to be sent. TC is cleared in the event of a simultaneous set and clear of
the TC flag (transmission not complete).
0 Transmission in progress
1 No transmission in progress
5
RDRF
Receive Data Register Full Flag — RDRF is set when the data in the receive shift register transfers to the SCI
data register. Clear RDRF by reading SCI status register 1 (SCISR1) with RDRF set and then reading SCI data
register low (SCIDRL).
0 Data not available in SCI data register
1 Received data available in SCI data register
4
IDLE
Idle Line Flag — IDLE is set when 10 consecutive logic 1s (if M = 0) or 11 consecutive logic 1s (if M =1) appear
on the receiver input. Once the IDLE flag is cleared, a valid frame must again set the RDRF flag before an idle
condition can set the IDLE flag.Clear IDLE by reading SCI status register 1 (SCISR1) with IDLE set and then
reading SCI data register low (SCIDRL).
0 Receiver input is either active now or has never become active since the IDLE flag was last cleared
1 Receiver input has become idle
Note: When the receiver wakeup bit (RWU) is set, an idle line condition does not set the IDLE flag.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
487
Chapter 12 Serial Communication Interface (S12SCIV6)
Table 12-11. SCISR1 Field Descriptions (continued)
Field
Description
3
OR
Overrun Flag — OR is set when software fails to read the SCI data register before the receive shift register
receives the next frame. The OR bit is set immediately after the stop bit has been completely received for the
second frame. The data in the shift register is lost, but the data already in the SCI data registers is not affected.
Clear OR by reading SCI status register 1 (SCISR1) with OR set and then reading SCI data register low
(SCIDRL).
0 No overrun
1 Overrun
Note: OR flag may read back as set when RDRF flag is clear. This may happen if the following sequence of
events occurs:
1. After the first frame is received, read status register SCISR1 (returns RDRF set and OR flag clear);
2. Receive second frame without reading the first frame in the data register (the second frame is not
received and OR flag is set);
3. Read data register SCIDRL (returns first frame and clears RDRF flag in the status register);
4. Read status register SCISR1 (returns RDRF clear and OR set).
Event 3 may be at exactly the same time as event 2 or any time after. When this happens, a dummy
SCIDRL read following event 4 will be required to clear the OR flag if further frames are to be received.
2
NF
Noise Flag — NF is set when the SCI detects noise on the receiver input. NF bit is set during the same cycle as
the RDRF flag but does not get set in the case of an overrun. Clear NF by reading SCI status register 1(SCISR1),
and then reading SCI data register low (SCIDRL).
0 No noise
1 Noise
1
FE
Framing Error Flag — FE is set when a logic 0 is accepted as the stop bit. FE bit is set during the same cycle
as the RDRF flag but does not get set in the case of an overrun. FE inhibits further data reception until it is
cleared. Clear FE by reading SCI status register 1 (SCISR1) with FE set and then reading the SCI data register
low (SCIDRL).
0 No framing error
1 Framing error
0
PF
Parity Error Flag — PF is set when the parity enable bit (PE) is set and the parity of the received data does not
match the parity type bit (PT). PF bit is set during the same cycle as the RDRF flag but does not get set in the
case of an overrun. Clear PF by reading SCI status register 1 (SCISR1), and then reading SCI data register low
(SCIDRL).
0 No parity error
1 Parity error
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
488
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.8
SCI Status Register 2 (SCISR2)
Module Base + 0x0005
7
R
W
Reset
AMAP
0
6
5
0
0
0
0
4
3
2
1
TXPOL
RXPOL
BRK13
TXDIR
0
0
0
0
0
RAF
0
= Unimplemented or Reserved
Figure 12-11. SCI Status Register 2 (SCISR2)
Read: Anytime
Write: Anytime
Table 12-12. SCISR2 Field Descriptions
Field
Description
7
AMAP
Alternative Map — This bit controls which registers sharing the same address space are accessible. In the reset
condition the SCI behaves as previous versions. Setting AMAP=1 allows the access to another set of control and
status registers and hides the baud rate and SCI control Register 1.
0 The registers labelled SCIBDH (0x0000),SCIBDL (0x0001), SCICR1 (0x0002) are accessible
1 The registers labelled SCIASR1 (0x0000),SCIACR1 (0x0001), SCIACR2 (0x00002) are accessible
4
TXPOL
Transmit Polarity — This bit control the polarity of the transmitted data. In NRZ format, a one is represented by
a mark and a zero is represented by a space for normal polarity, and the opposite for inverted polarity. In IrDA
format, a zero is represented by short high pulse in the middle of a bit time remaining idle low for a one for normal
polarity, and a zero is represented by short low pulse in the middle of a bit time remaining idle high for a one for
inverted polarity.
0 Normal polarity
1 Inverted polarity
3
RXPOL
Receive Polarity — This bit control the polarity of the received data. In NRZ format, a one is represented by a
mark and a zero is represented by a space for normal polarity, and the opposite for inverted polarity. In IrDA
format, a zero is represented by short high pulse in the middle of a bit time remaining idle low for a one for normal
polarity, and a zero is represented by short low pulse in the middle of a bit time remaining idle high for a one for
inverted polarity.
0 Normal polarity
1 Inverted polarity
2
BRK13
Break Transmit Character Length — This bit determines whether the transmit break character is 10 or 11 bit
respectively 13 or 14 bits long. The detection of a framing error is not affected by this bit.
0 Break character is 10 or 11 bit long
1 Break character is 13 or 14 bit long
1
TXDIR
Transmitter Pin Data Direction in Single-Wire Mode — This bit determines whether the TXD pin is going to
be used as an input or output, in the single-wire mode of operation. This bit is only relevant in the single-wire
mode of operation.
0 TXD pin to be used as an input in single-wire mode
1 TXD pin to be used as an output in single-wire mode
0
RAF
Receiver Active Flag — RAF is set when the receiver detects a logic 0 during the RT1 time period of the start
bit search. RAF is cleared when the receiver detects an idle character.
0 No reception in progress
1 Reception in progress
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
489
Chapter 12 Serial Communication Interface (S12SCIV6)
12.3.2.9
SCI Data Registers (SCIDRH, SCIDRL)
Module Base + 0x0006
7
R
6
R8
W
Reset
0
T8
0
5
4
3
0
0
0
0
0
0
2
1
0
Reserved
Reserved
Reserved
0
0
0
= Unimplemented or Reserved
Figure 12-12. SCI Data Registers (SCIDRH)
Module Base + 0x0007
7
6
5
4
3
2
1
0
R
R7
R6
R5
R4
R3
R2
R1
R0
W
T7
T6
T5
T4
T3
T2
T1
T0
0
0
0
0
0
0
0
0
Reset
Figure 12-13. SCI Data Registers (SCIDRL)
Read: Anytime; reading accesses SCI receive data register
Write: Anytime; writing accesses SCI transmit data register; writing to R8 has no effect
NOTE
The reserved bit SCIDRH[2:0] are designed for factory test purposes only,
and are not intended for general user access. Writing to these bit is possible
when in special mode and can alter the modules functionality.
Table 12-13. SCIDRH and SCIDRL Field Descriptions
Field
Description
SCIDRH
7
R8
Received Bit 8 — R8 is the ninth data bit received when the SCI is configured for 9-bit data format (M = 1).
SCIDRH
6
T8
Transmit Bit 8 — T8 is the ninth data bit transmitted when the SCI is configured for 9-bit data format (M = 1).
SCIDRL
7:0
R[7:0]
T[7:0]
R7:R0 — Received bits seven through zero for 9-bit or 8-bit data formats
T7:T0 — Transmit bits seven through zero for 9-bit or 8-bit formats
NOTE
If the value of T8 is the same as in the previous transmission, T8 does not
have to be rewritten.The same value is transmitted until T8 is rewritten
In 8-bit data format, only SCI data register low (SCIDRL) needs to be
accessed.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
490
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
When transmitting in 9-bit data format and using 8-bit write instructions,
write first to SCI data register high (SCIDRH), then SCIDRL.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
491
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4
Functional Description
This section provides a complete functional description of the SCI block, detailing the operation of the
design from the end user perspective in a number of subsections.
Figure 12-14 shows the structure of the SCI module. The SCI allows full duplex, asynchronous, serial
communication between the CPU and remote devices, including other CPUs. The SCI transmitter and
receiver operate independently, although they use the same baud rate generator. The CPU monitors the
status of the SCI, writes the data to be transmitted, and processes received data.
R8
IREN
SCI Data
Register
NF
FE
Ir_RXD
Bus
Clock
Receive
Shift Register
SCRXD
Receive
and Wakeup
Control
PF
RAF
RE
IDLE
RWU
RDRF
LOOPS
OR
RSRC
M
Receive
Baud Rate
Generator
IDLE
ILIE
RDRF/OR
Infrared
Receive
Decoder
R16XCLK
RXD
RIE
TIE
WAKE
Data Format
Control
ILT
PE
SBR15:SBR0
TDRE
TDRE
TC
SCI
Interrupt
Request
PT
TC
TCIE
TE
Transmit
Baud Rate
Generator
÷16
Transmit
Control
LOOPS
SBK
RSRC
T8
Transmit
Shift Register
RXEDGIE
Active Edge
Detect
RXEDGIF
BKDIF
RXD
SCI Data
Register
Break Detect
BKDFE
SCTXD
BKDIE
LIN Transmit BERRIF
Collision
Detect
BERRIE
R16XCLK
Infrared
Transmit
Encoder
BERRM[1:0]
Ir_TXD
TXD
R32XCLK
TNP[1:0]
IREN
Figure 12-14. Detailed SCI Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
492
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.1
Infrared Interface Submodule
This module provides the capability of transmitting narrow pulses to an IR LED and receiving narrow
pulses and transforming them to serial bits, which are sent to the SCI. The IrDA physical layer
specification defines a half-duplex infrared communication link for exchange data. The full standard
includes data rates up to 16 Mbits/s. This design covers only data rates between 2.4 Kbits/s and 115.2
Kbits/s.
The infrared submodule consists of two major blocks: the transmit encoder and the receive decoder. The
SCI transmits serial bits of data which are encoded by the infrared submodule to transmit a narrow pulse
for every zero bit. No pulse is transmitted for every one bit. When receiving data, the IR pulses should be
detected using an IR photo diode and transformed to CMOS levels by the IR receive decoder (external
from the MCU). The narrow pulses are then stretched by the infrared submodule to get back to a serial bit
stream to be received by the SCI.The polarity of transmitted pulses and expected receive pulses can be
inverted so that a direct connection can be made to external IrDA transceiver modules that use active low
pulses.
The infrared submodule receives its clock sources from the SCI. One of these two clocks are selected in
the infrared submodule in order to generate either 3/16, 1/16, 1/32 or 1/4 narrow pulses during
transmission. The infrared block receives two clock sources from the SCI, R16XCLK and R32XCLK,
which are configured to generate the narrow pulse width during transmission. The R16XCLK and
R32XCLK are internal clocks with frequencies 16 and 32 times the baud rate respectively. Both
R16XCLK and R32XCLK clocks are used for transmitting data. The receive decoder uses only the
R16XCLK clock.
12.4.1.1
Infrared Transmit Encoder
The infrared transmit encoder converts serial bits of data from transmit shift register to the TXD pin. A
narrow pulse is transmitted for a zero bit and no pulse for a one bit. The narrow pulse is sent in the middle
of the bit with a duration of 1/32, 1/16, 3/16 or 1/4 of a bit time. A narrow high pulse is transmitted for a
zero bit when TXPOL is cleared, while a narrow low pulse is transmitted for a zero bit when TXPOL is set.
12.4.1.2
Infrared Receive Decoder
The infrared receive block converts data from the RXD pin to the receive shift register. A narrow pulse is
expected for each zero received and no pulse is expected for each one received. A narrow high pulse is
expected for a zero bit when RXPOL is cleared, while a narrow low pulse is expected for a zero bit when
RXPOL is set. This receive decoder meets the edge jitter requirement as defined by the IrDA serial infrared
physical layer specification.
12.4.2
LIN Support
This module provides some basic support for the LIN protocol. At first this is a break detect circuitry
making it easier for the LIN software to distinguish a break character from an incoming data stream. As a
further addition is supports a collision detection at the bit level as well as cancelling pending transmissions.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
493
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.3
Data Format
The SCI uses the standard NRZ mark/space data format. When Infrared is enabled, the SCI uses RZI data
format where zeroes are represented by light pulses and ones remain low. See Figure 12-15 below.
8-Bit Data Format
(Bit M in SCICR1 Clear)
Start
Bit
Bit 0
Bit 1
Bit 2
Bit 3
Bit 4
Bit 5
Possible
Parity
Bit
Bit 6
STOP
Bit
Bit 7
Next
Start
Bit
Standard
SCI Data
Infrared
SCI Data
9-Bit Data Format
(Bit M in SCICR1 Set)
Start
Bit
Bit 0
Bit 1
Bit 2
Bit 3
Bit 4
Bit 5
POSSIBLE
PARITY
Bit
Bit 6
Bit 7
Bit 8
STOP
Bit
NEXT
START
Bit
Standard
SCI Data
Infrared
SCI Data
Figure 12-15. SCI Data Formats
Each data character is contained in a frame that includes a start bit, eight or nine data bits, and a stop bit.
Clearing the M bit in SCI control register 1 configures the SCI for 8-bit data characters. A frame with eight
data bits has a total of 10 bits. Setting the M bit configures the SCI for nine-bit data characters. A frame
with nine data bits has a total of 11 bits.
Table 12-14. Example of 8-Bit Data Formats
Start
Bit
Data
Bits
Address
Bits
Parity
Bits
Stop
Bit
1
8
0
0
1
1
7
0
1
1
(1)
0
1
1
7
1
1. The address bit identifies the frame as an address
character. See Section 12.4.6.6, “Receiver Wakeup”.
When the SCI is configured for 9-bit data characters, the ninth data bit is the T8 bit in SCI data register
high (SCIDRH). It remains unchanged after transmission and can be used repeatedly without rewriting it.
A frame with nine data bits has a total of 11 bits.
Table 12-15. Example of 9-Bit Data Formats
Start
Bit
Data
Bits
Address
Bits
Parity
Bits
Stop
Bit
1
9
0
0
1
1
8
0
1
1
8
(1)
0
1
1
1
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
494
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
1. The address bit identifies the frame as an address
character. See Section 12.4.6.6, “Receiver Wakeup”.
12.4.4
Baud Rate Generation
A 16-bit modulus counter in the two baud rate generator derives the baud rate for both the receiver and the
transmitter. The value from 0 to 65535 written to the SBR15:SBR0 bits determines the baud rate. The value
from 0 to 4095 written to the SBR15:SBR4 bits determines the baud rate clock with SBR3:SBR0 for fine
adjust. The SBR bits are in the SCI baud rate registers (SCIBDH and SCIBDL) for both transmit and
receive baud generator. The baud rate clock is synchronized with the bus clock and drives the receiver. The
baud rate clock divided by 16 drives the transmitter. The receiver has an acquisition rate of 16 samples per
bit time.
Baud rate generation is subject to one source of error:
• Integer division of the bus clock may not give the exact target frequency.
Table 12-16 lists some examples of achieving target baud rates with a bus clock frequency of 25 MHz.
When IREN = 0 then,
SCI baud rate = SCI bus clock / (SCIBR[15:0])
Table 12-16. Baud Rates (Example: Bus Clock = 25 MHz)
Bits
SBR[15:0]
Receiver(1)
Clock (Hz)
Transmitter(2)
Clock (Hz)
Target
Baud Rate
Error
(%)
109
3669724.8
229,357.8
230,400
.452
217
1843318.0
115,207.4
115,200
.006
651
614439.3
38,402.5
38,400
.006
1302
307219.7
19,201.2
19,200
.006
2604
153,609.8
9600.6
9,600
.006
5208
76,804.9
4800.3
4,800
.006
10417
38,398.8
2399.9
2,400
.003
20833
19,200.3
1200.02
1,200
.00
41667
9599.9
600.0
600
.00
65535
6103.6
1. 16x faster then baud rate
2. divide 1/16 form transmit baud generator
381.5
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
495
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.5
Transmitter
Internal Bus
Transmit baud
generator
SBR15:SBR4
÷ 16
SCI Data Registers
Stop
SBR3:SBR0
11-Bit Transmit Register
H
8
7
6
5
4
3
2
1
0
TXPOL
SCTXD
L
MSB
M
Start
Bus
Clock
LOOP
CONTROL
TIE
Break (All 0s)
TDRE IRQ
Parity
Generation
Preamble (All 1s)
PT
Shift Enable
PE
Load from SCIDR
T8
To Receiver
LOOPS
RSRC
TDRE
Transmitter Control
TC IRQ
TC
TCIE
TE
BERRIF
BER IRQ
TCIE
SBK
BERRM[1:0]
Transmit
Collision Detect
SCTXD
SCRXD
(From Receiver)
Figure 12-16. Transmitter Block Diagram
12.4.5.1
Transmitter Character Length
The SCI transmitter can accommodate either 8-bit or 9-bit data characters. The state of the M bit in SCI
control register 1 (SCICR1) determines the length of data characters. When transmitting 9-bit data, bit T8
in SCI data register high (SCIDRH) is the ninth bit (bit 8).
12.4.5.2
Character Transmission
To transmit data, the MCU writes the data bits to the SCI data registers (SCIDRH/SCIDRL), which in turn
are transferred to the transmitter shift register. The transmit shift register then shifts a frame out through
the TXD pin, after it has prefaced them with a start bit and appended them with a stop bit. The SCI data
registers (SCIDRH and SCIDRL) are the write-only buffers between the internal data bus and the transmit
shift register.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
496
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
The SCI also sets a flag, the transmit data register empty flag (TDRE), every time it transfers data from the
buffer (SCIDRH/L) to the transmitter shift register.The transmit driver routine may respond to this flag by
writing another byte to the Transmitter buffer (SCIDRH/SCIDRL), while the shift register is still shifting
out the first byte.
To initiate an SCI transmission:
1. Configure the SCI:
a) Select a baud rate. Write this value to the SCI baud registers (SCIBDH/L) to begin the baud
rate generator. Remember that the baud rate generator is disabled when the baud rate is zero.
Writing to the SCIBDH has no effect without also writing to SCIBDL.
b) Write to SCICR1 to configure word length, parity, and other configuration bits
(LOOPS,RSRC,M,WAKE,ILT,PE,PT).
c) Enable the transmitter, interrupts, receive, and wake up as required, by writing to the SCICR2
register bits (TIE,TCIE,RIE,ILIE,TE,RE,RWU,SBK). A preamble or idle character will now
be shifted out of the transmitter shift register.
2. Transmit Procedure for each byte:
a) Poll the TDRE flag by reading the SCISR1 or responding to the TDRE interrupt. Keep in mind
that the TDRE bit resets to one.
b) If the TDRE flag is set, write the data to be transmitted to SCIDRH/L, where the ninth bit is
written to the T8 bit in SCIDRH if the SCI is in 9-bit data format. A new transmission will not
result until the TDRE flag has been cleared.
3. Repeat step 2 for each subsequent transmission.
NOTE
The TDRE flag is set when the shift register is loaded with the next data to
be transmitted from SCIDRH/L, which happens, generally speaking, a little
over half-way through the stop bit of the previous frame. Specifically, this
transfer occurs 9/16ths of a bit time AFTER the start of the stop bit of the
previous frame.
Writing the TE bit from 0 to a 1 automatically loads the transmit shift register with a preamble of 10 logic
1s (if M = 0) or 11 logic 1s (if M = 1). After the preamble shifts out, control logic transfers the data from
the SCI data register into the transmit shift register. A logic 0 start bit automatically goes into the least
significant bit position of the transmit shift register. A logic 1 stop bit goes into the most significant bit
position.
Hardware supports odd or even parity. When parity is enabled, the most significant bit (MSB) of the data
character is the parity bit.
The transmit data register empty flag, TDRE, in SCI status register 1 (SCISR1) becomes set when the SCI
data register transfers a byte to the transmit shift register. The TDRE flag indicates that the SCI data
register can accept new data from the internal data bus. If the transmit interrupt enable bit, TIE, in SCI
control register 2 (SCICR2) is also set, the TDRE flag generates a transmitter interrupt request.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
497
Chapter 12 Serial Communication Interface (S12SCIV6)
When the transmit shift register is not transmitting a frame, the TXD pin goes to the idle condition, logic
1. If at any time software clears the TE bit in SCI control register 2 (SCICR2), the transmitter enable signal
goes low and the transmit signal goes idle.
If software clears TE while a transmission is in progress (TC = 0), the frame in the transmit shift register
continues to shift out. To avoid accidentally cutting off the last frame in a message, always wait for TDRE
to go high after the last frame before clearing TE.
To separate messages with preambles with minimum idle line time, use this sequence between messages:
1. Write the last byte of the first message to SCIDRH/L.
2. Wait for the TDRE flag to go high, indicating the transfer of the last frame to the transmit shift
register.
3. Queue a preamble by clearing and then setting the TE bit.
4. Write the first byte of the second message to SCIDRH/L.
12.4.5.3
Break Characters
Writing a logic 1 to the send break bit, SBK, in SCI control register 2 (SCICR2) loads the transmit shift
register with a break character. A break character contains all logic 0s and has no start, stop, or parity bit.
Break character length depends on the M bit in SCI control register 1 (SCICR1). As long as SBK is at logic
1, transmitter logic continuously loads break characters into the transmit shift register. After software
clears the SBK bit, the shift register finishes transmitting the last break character and then transmits at least
one logic 1. The automatic logic 1 at the end of a break character guarantees the recognition of the start bit
of the next frame.
The SCI recognizes a break character when there are 10 or 11(M = 0 or M = 1) consecutive zero received.
Depending if the break detect feature is enabled or not receiving a break character has these effects on SCI
registers.
If the break detect feature is disabled (BKDFE = 0):
• Sets the framing error flag, FE
• Sets the receive data register full flag, RDRF
• Clears the SCI data registers (SCIDRH/L)
• May set the overrun flag, OR, noise flag, NF, parity error flag, PE, or the receiver active flag, RAF
(see 3.4.4 and 3.4.5 SCI Status Register 1 and 2)
If the break detect feature is enabled (BKDFE = 1) there are two scenarios1
The break is detected right from a start bit or is detected during a byte reception.
• Sets the break detect interrupt flag, BKDIF
• Does not change the data register full flag, RDRF or overrun flag OR
• Does not change the framing error flag FE, parity error flag PE.
• Does not clear the SCI data registers (SCIDRH/L)
• May set noise flag NF, or receiver active flag RAF.
1. A Break character in this context are either 10 or 11 consecutive zero received bits
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
498
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
Figure 12-17 shows two cases of break detect. In trace RXD_1 the break symbol starts with the start bit,
while in RXD_2 the break starts in the middle of a transmission. If BRKDFE = 1, in RXD_1 case there
will be no byte transferred to the receive buffer and the RDRF flag will not be modified. Also no framing
error or parity error will be flagged from this transfer. In RXD_2 case, however the break signal starts later
during the transmission. At the expected stop bit position the byte received so far will be transferred to the
receive buffer, the receive data register full flag will be set, a framing error and if enabled and appropriate
a parity error will be set. Once the break is detected the BRKDIF flag will be set.
Start Bit Position
Stop Bit Position
BRKDIF = 1
RXD_1
Zero Bit Counter
1
2
3
4
5
6
7
8
9
10 . . .
BRKDIF = 1
FE = 1
RXD_2
Zero Bit Counter
1
2
3
4
5
6
7
8
9
10
...
Figure 12-17. Break Detection if BRKDFE = 1 (M = 0)
12.4.5.4
Idle Characters
An idle character (or preamble) contains all logic 1s and has no start, stop, or parity bit. Idle character
length depends on the M bit in SCI control register 1 (SCICR1). The preamble is a synchronizing idle
character that begins the first transmission initiated after writing the TE bit from 0 to 1.
If the TE bit is cleared during a transmission, the TXD pin becomes idle after completion of the
transmission in progress. Clearing and then setting the TE bit during a transmission queues an idle
character to be sent after the frame currently being transmitted.
NOTE
When queueing an idle character, return the TE bit to logic 1 before the stop
bit of the current frame shifts out through the TXD pin. Setting TE after the
stop bit appears on TXD causes data previously written to the SCI data
register to be lost. Toggle the TE bit for a queued idle character while the
TDRE flag is set and immediately before writing the next byte to the SCI
data register.
If the TE bit is clear and the transmission is complete, the SCI is not the
master of the TXD pin
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
499
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.5.5
LIN Transmit Collision Detection
This module allows to check for collisions on the LIN bus.
LIN Physical Interface
Synchronizer Stage
Receive Shift
Register
Compare
RXD Pin
Bit Error
LIN Bus
Bus Clock
Sample
Point
Transmit Shift
Register
TXD Pin
Figure 12-18. Collision Detect Principle
If the bit error circuit is enabled (BERRM[1:0] = 0:1 or = 1:0]), the error detect circuit will compare the
transmitted and the received data stream at a point in time and flag any mismatch. The timing checks run
when transmitter is active (not idle). As soon as a mismatch between the transmitted data and the received
data is detected the following happens:
• The next bit transmitted will have a high level (TXPOL = 0) or low level (TXPOL = 1)
• The transmission is aborted and the byte in transmit buffer is discarded.
• the transmit data register empty and the transmission complete flag will be set
• The bit error interrupt flag, BERRIF, will be set.
• No further transmissions will take place until the BERRIF is cleared.
4
5
6
7
8
BERRM[1:0] = 0:1
9
10
11
12
13
14
15
0
Sampling End
3
Sampling Begin
Input Receive
Shift Register
2
Sampling End
Output Transmit
Shift Register
1
Sampling Begin
0
BERRM[1:0] = 1:1
Compare Sample Points
Figure 12-19. Timing Diagram Bit Error Detection
If the bit error detect feature is disabled, the bit error interrupt flag is cleared.
NOTE
The RXPOL and TXPOL bit should be set the same when transmission
collision detect feature is enabled, otherwise the bit error interrupt flag may
be set incorrectly.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
500
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.6
Receiver
Internal Bus
RXPOL
Data
Recovery
Loop
Control
H
11-Bit Receive Shift Register
8
7
6
5
4
3
2
1
0
L
All 1s
SCRXD
From TXD Pin
or Transmitter
Stop
Receive Baud
Generator
MSB
Bus
Clock
SCI Data Register
SBR3:SBR0
Start
SBR15:SBR4
RE
RAF
LOOPS
RSRC
FE
M
WAKE
ILT
PE
PT
RWU
NF
Wakeup
Logic
PE
R8
Parity
Checking
Idle IRQ
IDLE
ILIE
BRKDFE
OR
Break
Detect Logic
RIE
BRKDIF
BRKDIE
Active Edge
Detect Logic
RDRF/OR
IRQ
RDRF
Break IRQ
RXEDGIF
RXEDGIE
RX Active Edge IRQ
Figure 12-20. SCI Receiver Block Diagram
12.4.6.1
Receiver Character Length
The SCI receiver can accommodate either 8-bit or 9-bit data characters. The state of the M bit in SCI
control register 1 (SCICR1) determines the length of data characters. When receiving 9-bit data, bit R8 in
SCI data register high (SCIDRH) is the ninth bit (bit 8).
12.4.6.2
Character Reception
During an SCI reception, the receive shift register shifts a frame in from the RXD pin. The SCI data register
is the read-only buffer between the internal data bus and the receive shift register.
After a complete frame shifts into the receive shift register, the data portion of the frame transfers to the
SCI data register. The receive data register full flag, RDRF, in SCI status register 1 (SCISR1) becomes set,
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
501
Chapter 12 Serial Communication Interface (S12SCIV6)
indicating that the received byte can be read. If the receive interrupt enable bit, RIE, in SCI control
register 2 (SCICR2) is also set, the RDRF flag generates an RDRF interrupt request.
12.4.6.3
Data Sampling
The RT clock rate. The RT clock is an internal signal with a frequency 16 times the baud rate. To adjust
for baud rate mismatch, the RT clock (see Figure 12-21) is re-synchronized immediatelly at bus clock
edge:
• After every start bit
• After the receiver detects a data bit change from logic 1 to logic 0 (after the majority of data bit
samples at RT8, RT9, and RT10 returns a valid logic 1 and the majority of the next RT8, RT9, and
RT10 samples returns a valid logic 0)
To locate the start bit, data recovery logic does an asynchronous search for a logic 0 preceded by three logic
1s.When the falling edge of a possible start bit occurs, the RT clock begins to count to 16.
LSB
Start Bit
RXD
Samples
1
1
1
1
1
1
1
1
0
0
Start Bit
Qualification
0
0
Start Bit
Verification
0
0
0
Data
Sampling
RT4
RT3
RT2
RT1
RT16
RT15
RT14
RT13
RT12
RT11
RT10
RT9
RT8
RT7
RT6
RT5
RT4
RT3
RT2
RT1
RT1
RT1
RT1
RT1
RT1
RT1
RT1
RT CLock Count
RT1
RT Clock
Reset RT Clock
Figure 12-21. Receiver Data Sampling
To verify the start bit and to detect noise, data recovery logic takes samples at RT3, RT5, and RT7.
Figure 12-17 summarizes the results of the start bit verification samples.
Table 12-17. Start Bit Verification
RT3, RT5, and RT7 Samples
Start Bit Verification
Noise Flag
000
Yes
0
001
Yes
1
010
Yes
1
011
No
0
100
Yes
1
101
No
0
110
No
0
111
No
0
If start bit verification is not successful, the RT clock is reset and a new search for a start bit begins.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
502
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
To determine the value of a data bit and to detect noise, recovery logic takes samples at RT8, RT9, and
RT10. Table 12-18 summarizes the results of the data bit samples.
Table 12-18. Data Bit Recovery
RT8, RT9, and RT10 Samples
Data Bit Determination
Noise Flag
000
0
0
001
0
1
010
0
1
011
1
1
100
0
1
101
1
1
110
1
1
111
1
0
NOTE
The RT8, RT9, and RT10 samples do not affect start bit verification. If any
or all of the RT8, RT9, and RT10 start bit samples are logic 1s following a
successful start bit verification, the noise flag (NF) is set and the receiver
assumes that the bit is a start bit (logic 0).
To verify a stop bit and to detect noise, recovery logic takes samples at RT8, RT9, and RT10. Table 12-19
summarizes the results of the stop bit samples.
Table 12-19. Stop Bit Recovery
RT8, RT9, and RT10 Samples
Framing Error Flag
Noise Flag
000
1
0
001
1
1
010
1
1
011
0
1
100
1
1
101
0
1
110
0
1
111
0
0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
503
Chapter 12 Serial Communication Interface (S12SCIV6)
In Figure 12-22 the verification samples RT3 and RT5 determine that the first low detected was noise and
not the beginning of a start bit. The RT clock is reset and the start bit search begins again. The noise flag
is not set because the noise occurred before the start bit was found.
LSB
Start Bit
0
0
0
0
0
0
RT10
1
RT9
RT1
1
RT8
RT1
1
RT7
0
RT1
1
RT1
1
RT5
1
RT1
Samples
RT1
RXD
0
RT3
RT2
RT1
RT16
RT15
RT14
RT13
RT12
RT11
RT6
RT5
RT4
RT3
RT2
RT4
RT3
RT Clock Count
RT2
RT Clock
Reset RT Clock
Figure 12-22. Start Bit Search Example 1
In Figure 12-23, verification sample at RT3 is high. The RT3 sample sets the noise flag. Although the
perceived bit time is misaligned, the data samples RT8, RT9, and RT10 are within the bit time and data
recovery is successful.
Perceived Start Bit
Actual Start Bit
LSB
1
0
RT1
RT1
RT1
RT1
1
0
0
0
0
0
RT10
1
RT9
1
RT8
1
RT7
1
RT1
Samples
RT1
RXD
RT7
RT6
RT5
RT4
RT3
RT2
RT1
RT16
RT15
RT14
RT13
RT12
RT11
RT6
RT5
RT4
RT3
RT Clock Count
RT2
RT Clock
Reset RT Clock
Figure 12-23. Start Bit Search Example 2
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
504
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
In Figure 12-24, a large burst of noise is perceived as the beginning of a start bit, although the test sample
at RT5 is high. The RT5 sample sets the noise flag. Although this is a worst-case misalignment of perceived
bit time, the data samples RT8, RT9, and RT10 are within the bit time and data recovery is successful.
Perceived Start Bit
LSB
Actual Start Bit
RT1
RT1
0
1
0
0
0
0
RT10
0
RT9
1
RT8
1
RT7
1
RT1
Samples
RT1
RXD
RT9
RT8
RT7
RT6
RT5
RT4
RT3
RT2
RT1
RT16
RT15
RT14
RT13
RT12
RT11
RT6
RT5
RT4
RT3
RT Clock Count
RT2
RT Clock
Reset RT Clock
Figure 12-24. Start Bit Search Example 3
Figure 12-25 shows the effect of noise early in the start bit time. Although this noise does not affect proper
synchronization with the start bit time, it does set the noise flag.
Perceived and Actual Start Bit
LSB
RT1
RT1
RT1
RT1
1
1
1
1
0
RT1
1
RT1
1
RT1
1
RT1
1
RT1
1
RT1
RXD
Samples
1
0
RT3
RT2
RT1
RT16
RT15
RT14
RT13
RT12
RT11
RT9
RT10
RT8
RT7
RT6
RT5
RT4
RT3
RT Clock Count
RT2
RT Clock
Reset RT Clock
Figure 12-25. Start Bit Search Example 4
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
505
Chapter 12 Serial Communication Interface (S12SCIV6)
Figure 12-26 shows a burst of noise near the beginning of the start bit that resets the RT clock. The sample
after the reset is low but is not preceded by three high samples that would qualify as a falling edge.
Depending on the timing of the start bit search and on the data, the frame may be missed entirely or it may
set the framing error flag.
Start Bit
0
RT1
RT1
RT1
RT1
RT1
RT1
RT1
RT1
RT1
0
1
1
0
0
0
0
0
0
0
0
RT1
1
RT1
1
RT1
1
RT1
1
RT1
1
RT1
1
RT1
1
RT1
1
RT7
1
RT1
Samples
LSB
No Start Bit Found
RXD
RT1
RT1
RT1
RT1
RT6
RT5
RT4
RT3
RT Clock Count
RT2
RT Clock
Reset RT Clock
Figure 12-26. Start Bit Search Example 5
In Figure 12-27, a noise burst makes the majority of data samples RT8, RT9, and RT10 high. This sets the
noise flag but does not reset the RT clock. In start bits only, the RT8, RT9, and RT10 data samples are
ignored.
Start Bit
LSB
1
1
1
1
1
0
RT1
RT1
RT1
RT1
RT1
RT1
RT1
RT1
0
0
0
1
0
1
RT10
1
RT9
1
RT8
1
RT7
1
RT1
Samples
RT1
RXD
RT3
RT2
RT1
RT16
RT15
RT14
RT13
RT12
RT11
RT6
RT5
RT4
RT3
RT Clock Count
RT2
RT Clock
Reset RT Clock
Figure 12-27. Start Bit Search Example 6
12.4.6.4
Framing Errors
If the data recovery logic does not detect a logic 1 where the stop bit should be in an incoming frame, it
sets the framing error flag, FE, in SCI status register 1 (SCISR1). A break character also sets the FE flag
because a break character has no stop bit. The FE flag is set at the same time that the RDRF flag is set.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
506
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.6.5
Baud Rate Tolerance
A transmitting device may be operating at a baud rate below or above the receiver baud rate. Accumulated
bit time misalignment can cause one of the three stop bit data samples (RT8, RT9, and RT10) to fall outside
the actual stop bit. A noise error will occur if the RT8, RT9, and RT10 samples are not all the same logical
values. A framing error will occur if the receiver clock is misaligned in such a way that the majority of the
RT8, RT9, and RT10 stop bit samples are a logic zero.
As the receiver samples an incoming frame, it re-synchronizes the RT clock on any valid falling edge
within the frame. Re synchronization within frames will correct a misalignment between transmitter bit
times and receiver bit times.
12.4.6.5.1
Slow Data Tolerance
Figure 12-28 shows how much a slow received frame can be misaligned without causing a noise error or
a framing error. The slow stop bit begins at RT8 instead of RT1 but arrives in time for the stop bit data
samples at RT8, RT9, and RT10.
MSB
Stop
RT16
RT15
RT14
RT13
RT12
RT11
RT10
RT9
RT8
RT7
RT6
RT5
RT4
RT3
RT2
RT1
Receiver
RT Clock
Data
Samples
Figure 12-28. Slow Data
Let’s take RTr as receiver RT clock and RTt as transmitter RT clock.
For an 8-bit data character, it takes the receiver 9 bit times x 16 RTr cycles +7 RTr cycles = 151 RTr cycles
to start data sampling of the stop bit.
With the misaligned character shown in Figure 12-28, the receiver counts 151 RTr cycles at the point when
the count of the transmitting device is 9 bit times x 16 RTt cycles = 144 RTt cycles.
The maximum percent difference between the receiver count and the transmitter count of a slow 8-bit data
character with no errors is:
((151 – 144) / 151) x 100 = 4.63%
For a 9-bit data character, it takes the receiver 10 bit times x 16 RTr cycles + 7 RTr cycles = 167 RTr cycles
to start data sampling of the stop bit.
With the misaligned character shown in Figure 12-28, the receiver counts 167 RTr cycles at the point when
the count of the transmitting device is 10 bit times x 16 RTt cycles = 160 RTt cycles.
The maximum percent difference between the receiver count and the transmitter count of a slow 9-bit
character with no errors is:
((167 – 160) / 167) X 100 = 4.19%
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
507
Chapter 12 Serial Communication Interface (S12SCIV6)
12.4.6.5.2
Fast Data Tolerance
Figure 12-29 shows how much a fast received frame can be misaligned. The fast stop bit ends at RT10
instead of RT16 but is still sampled at RT8, RT9, and RT10.
Stop
Idle or Next Frame
RT16
RT15
RT14
RT13
RT12
RT11
RT10
RT9
RT8
RT7
RT6
RT5
RT4
RT3
RT2
RT1
Receiver
RT Clock
Data
Samples
Figure 12-29. Fast Data
For an 8-bit data character, it takes the receiver 9 bit times x 16 RTr cycles + 9 RTr cycles = 153 RTr cycles
to finish data sampling of the stop bit.
With the misaligned character shown in Figure 12-29, the receiver counts 153 RTr cycles at the point when
the count of the transmitting device is 10 bit times x 16 RTt cycles = 160 RTt cycles.
The maximum percent difference between the receiver count and the transmitter count of a fast 8-bit
character with no errors is:
((160 – 153) / 160) x 100 = 4.375%
For a 9-bit data character, it takes the receiver 10 bit times x 16 RTr cycles + 9 RTr cycles = 169 RTr cycles
to finish data sampling of the stop bit.
With the misaligned character shown in Figure 12-29, the receiver counts 169 RTr cycles at the point when
the count of the transmitting device is 11 bit times x 16 RTt cycles = 176 RTt cycles.
The maximum percent difference between the receiver count and the transmitter count of a fast 9-bit
character with no errors is:
((176 – 169) /176) x 100 = 3.98%
NOTE
Due to asynchronous sample and internal logic, there is maximal 2 bus
cycles between startbit edge and 1st RT clock, and cause to additional
tolerance loss at worst case. The loss should be 2/SBR/10*100%, it is
small.For example, for highspeed baud=230400 with 25MHz bus, SBR
should be 109, and the tolerance loss is 2/109/10*100=0.18%, and fast data
tolerance is 4.375%-0.18%=4.195%.
12.4.6.6
Receiver Wakeup
To enable the SCI to ignore transmissions intended only for other receivers in multiple-receiver systems,
the receiver can be put into a standby state. Setting the receiver wakeup bit, RWU, in SCI control register 2
(SCICR2) puts the receiver into standby state during which receiver interrupts are disabled.The SCI will
still load the receive data into the SCIDRH/L registers, but it will not set the RDRF flag.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
508
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
The transmitting device can address messages to selected receivers by including addressing information in
the initial frame or frames of each message.
The WAKE bit in SCI control register 1 (SCICR1) determines how the SCI is brought out of the standby
state to process an incoming message. The WAKE bit enables either idle line wakeup or address mark
wakeup.
12.4.6.6.1
Idle Input line Wakeup (WAKE = 0)
In this wakeup method, an idle condition on the RXD pin clears the RWU bit and wakes up the SCI. The
initial frame or frames of every message contain addressing information. All receivers evaluate the
addressing information, and receivers for which the message is addressed process the frames that follow.
Any receiver for which a message is not addressed can set its RWU bit and return to the standby state. The
RWU bit remains set and the receiver remains on standby until another idle character appears on the RXD
pin.
Idle line wakeup requires that messages be separated by at least one idle character and that no message
contains idle characters.
The idle character that wakes a receiver does not set the receiver idle bit, IDLE, or the receive data register
full flag, RDRF.
The idle line type bit, ILT, determines whether the receiver begins counting logic 1s as idle character bits
after the start bit or after the stop bit. ILT is in SCI control register 1 (SCICR1).
12.4.6.6.2
Address Mark Wakeup (WAKE = 1)
In this wakeup method, a logic 1 in the most significant bit (MSB) position of a frame clears the RWU bit
and wakes up the SCI. The logic 1 in the MSB position marks a frame as an address frame that contains
addressing information. All receivers evaluate the addressing information, and the receivers for which the
message is addressed process the frames that follow.Any receiver for which a message is not addressed can
set its RWU bit and return to the standby state. The RWU bit remains set and the receiver remains on
standby until another address frame appears on the RXD pin.
The logic 1 MSB of an address frame clears the receiver’s RWU bit before the stop bit is received and sets
the RDRF flag.
Address mark wakeup allows messages to contain idle characters but requires that the MSB be reserved
for use in address frames.
NOTE
With the WAKE bit clear, setting the RWU bit after the RXD pin has been
idle can cause the receiver to wake up immediately.
12.4.7
Single-Wire Operation
Normally, the SCI uses two pins for transmitting and receiving. In single-wire operation, the RXD pin is
disconnected from the SCI. The SCI uses the TXD pin for both receiving and transmitting.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
509
Chapter 12 Serial Communication Interface (S12SCIV6)
Transmitter
Receiver
TXD
RXD
Figure 12-30. Single-Wire Operation (LOOPS = 1, RSRC = 1)
Enable single-wire operation by setting the LOOPS bit and the receiver source bit, RSRC, in SCI control
register 1 (SCICR1). Setting the LOOPS bit disables the path from the RXD pin to the receiver. Setting
the RSRC bit connects the TXD pin to the receiver. Both the transmitter and receiver must be enabled
(TE = 1 and RE = 1).The TXDIR bit (SCISR2[1]) determines whether the TXD pin is going to be used as
an input (TXDIR = 0) or an output (TXDIR = 1) in this mode of operation.
NOTE
In single-wire operation data from the TXD pin is inverted if RXPOL is set.
12.4.8
Loop Operation
In loop operation the transmitter output goes to the receiver input. The RXD pin is disconnected from the
SCI.
Transmitter
TXD
Receiver
RXD
Figure 12-31. Loop Operation (LOOPS = 1, RSRC = 0)
Enable loop operation by setting the LOOPS bit and clearing the RSRC bit in SCI control register 1
(SCICR1). Setting the LOOPS bit disables the path from the RXD pin to the receiver. Clearing the RSRC
bit connects the transmitter output to the receiver input. Both the transmitter and receiver must be enabled
(TE = 1 and RE = 1).
NOTE
In loop operation data from the transmitter is not recognized by the receiver
if RXPOL and TXPOL are not the same.
12.5
12.5.1
Initialization/Application Information
Reset Initialization
See Section 12.3.2, “Register Descriptions”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
510
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.5.2
12.5.2.1
Modes of Operation
Run Mode
Normal mode of operation.
To initialize a SCI transmission, see Section 12.4.5.2, “Character Transmission”.
12.5.2.2
Wait Mode
SCI operation in wait mode depends on the state of the SCISWAI bit in the SCI control register 1
(SCICR1).
• If SCISWAI is clear, the SCI operates normally when the CPU is in wait mode.
• If SCISWAI is set, SCI clock generation ceases and the SCI module enters a power-conservation
state when the CPU is in wait mode. Setting SCISWAI does not affect the state of the receiver
enable bit, RE, or the transmitter enable bit, TE.
If SCISWAI is set, any transmission or reception in progress stops at wait mode entry. The
transmission or reception resumes when either an internal or external interrupt brings the CPU out
of wait mode. Exiting wait mode by reset aborts any transmission or reception in progress and
resets the SCI.
12.5.2.3
Stop Mode
The SCI is inactive during stop mode for reduced power consumption. The STOP instruction does not
affect the SCI register states, but the SCI bus clock will be disabled. The SCI operation resumes from
where it left off after an external interrupt brings the CPU out of stop mode. Exiting stop mode by reset
aborts any transmission or reception in progress and resets the SCI.
The receive input active edge detect circuit is still active in stop mode. An active edge on the receive input
can be used to bring the CPU out of stop mode.
12.5.3
Interrupt Operation
This section describes the interrupt originated by the SCI block.The MCU must service the interrupt
requests. Table 12-20 lists the eight interrupt sources of the SCI.
Table 12-20. SCI Interrupt Sources
Interrupt
Source
Local Enable
TDRE
SCISR1[7]
TIE
TC
SCISR1[6]
TCIE
RDRF
SCISR1[5]
RIE
OR
SCISR1[3]
IDLE
SCISR1[4]
Description
Active high level. Indicates that a byte was transferred from SCIDRH/L to the
transmit shift register.
Active high level. Indicates that a transmit is complete.
Active high level. The RDRF interrupt indicates that received data is available
in the SCI data register.
Active high level. This interrupt indicates that an overrun condition has occurred.
ILIE
Active high level. Indicates that receiver input has become idle.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
511
Chapter 12 Serial Communication Interface (S12SCIV6)
Table 12-20. SCI Interrupt Sources
RXEDGIF SCIASR1[7]
RXEDGIE
Active high level. Indicates that an active edge (falling for RXPOL = 0, rising for
RXPOL = 1) was detected.
BERRIF
SCIASR1[1]
BERRIE
Active high level. Indicates that a mismatch between transmitted and received data
in a single wire application has happened.
BKDIF
SCIASR1[0]
BRKDIE
Active high level. Indicates that a break character has been received.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
512
Freescale Semiconductor
Chapter 12 Serial Communication Interface (S12SCIV6)
12.5.3.1
Description of Interrupt Operation
The SCI only originates interrupt requests. The following is a description of how the SCI makes a request
and how the MCU should acknowledge that request. The interrupt vector offset and interrupt number are
chip dependent. The SCI only has a single interrupt line (SCI Interrupt Signal, active high operation) and
all the following interrupts, when generated, are ORed together and issued through that port.
12.5.3.1.1
TDRE Description
The TDRE interrupt is set high by the SCI when the transmit shift register receives a byte from the SCI
data register. A TDRE interrupt indicates that the transmit data register (SCIDRH/L) is empty and that a
new byte can be written to the SCIDRH/L for transmission.Clear TDRE by reading SCI status register 1
with TDRE set and then writing to SCI data register low (SCIDRL).
12.5.3.1.2
TC Description
The TC interrupt is set by the SCI when a transmission has been completed. Transmission is completed
when all bits including the stop bit (if transmitted) have been shifted out and no data is queued to be
transmitted. No stop bit is transmitted when sending a break character and the TC flag is set (providing
there is no more data queued for transmission) when the break character has been shifted out. A TC
interrupt indicates that there is no transmission in progress. TC is set high when the TDRE flag is set and
no data, preamble, or break character is being transmitted. When TC is set, the TXD pin becomes idle
(logic 1). Clear TC by reading SCI status register 1 (SCISR1) with TC set and then writing to SCI data
register low (SCIDRL).TC is cleared automatically when data, preamble, or break is queued and ready to
be sent.
12.5.3.1.3
RDRF Description
The RDRF interrupt is set when the data in the receive shift register transfers to the SCI data register. A
RDRF interrupt indicates that the received data has been transferred to the SCI data register and that the
byte can now be read by the MCU. The RDRF interrupt is cleared by reading the SCI status register one
(SCISR1) and then reading SCI data register low (SCIDRL).
12.5.3.1.4
OR Description
The OR interrupt is set when software fails to read the SCI data register before the receive shift register
receives the next frame. The newly acquired data in the shift register will be lost in this case, but the data
already in the SCI data registers is not affected. The OR interrupt is cleared by reading the SCI status
register one (SCISR1) and then reading SCI data register low (SCIDRL).
12.5.3.1.5
IDLE Description
The IDLE interrupt is set when 10 consecutive logic 1s (if M = 0) or 11 consecutive logic 1s (if M = 1)
appear on the receiver input. Once the IDLE is cleared, a valid frame must again set the RDRF flag before
an idle condition can set the IDLE flag. Clear IDLE by reading SCI status register 1 (SCISR1) with IDLE
set and then reading SCI data register low (SCIDRL).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
513
Chapter 12 Serial Communication Interface (S12SCIV6)
12.5.3.1.6
RXEDGIF Description
The RXEDGIF interrupt is set when an active edge (falling if RXPOL = 0, rising if RXPOL = 1) on the
RXD pin is detected. Clear RXEDGIF by writing a “1” to the SCIASR1 SCI alternative status register 1.
12.5.3.1.7
BERRIF Description
The BERRIF interrupt is set when a mismatch between the transmitted and the received data in a single
wire application like LIN was detected. Clear BERRIF by writing a “1” to the SCIASR1 SCI alternative
status register 1. This flag is also cleared if the bit error detect feature is disabled.
12.5.3.1.8
BKDIF Description
The BKDIF interrupt is set when a break signal was received. Clear BKDIF by writing a “1” to the
SCIASR1 SCI alternative status register 1. This flag is also cleared if break detect feature is disabled.
12.5.4
Recovery from Wait Mode
The SCI interrupt request can be used to bring the CPU out of wait mode.
12.5.5
Recovery from Stop Mode
An active edge on the receive input can be used to bring the CPU out of stop mode.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
514
Freescale Semiconductor
Chapter 13
Serial Peripheral Interface (S12SPIV5)
Table 13-1. Revision History
Revision
Number
Revision Date
Sections
Affected
V05.00
24 Mar 2005
13.3.2/13-519
13.1
Description of Changes
- Added 16-bit transfer width feature.
Introduction
The SPI module allows a duplex, synchronous, serial communication between the MCU and peripheral
devices. Software can poll the SPI status flags or the SPI operation can be interrupt driven.
13.1.1
Glossary of Terms
SPI
SS
SCK
MOSI
MISO
MOMI
SISO
13.1.2
Serial Peripheral Interface
Slave Select
Serial Clock
Master Output, Slave Input
Master Input, Slave Output
Master Output, Master Input
Slave Input, Slave Output
Features
The SPI includes these distinctive features:
• Master mode and slave mode
• Selectable 8 or 16-bit transfer width
• Bidirectional mode
• Slave select output
• Mode fault error flag with CPU interrupt capability
• Double-buffered data register
• Serial clock with programmable polarity and phase
• Control of SPI operation during wait mode
13.1.3
Modes of Operation
The SPI functions in three modes: run, wait, and stop.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
515
Chapter 13 Serial Peripheral Interface (S12SPIV5)
•
•
•
Run mode
This is the basic mode of operation.
Wait mode
SPI operation in wait mode is a configurable low power mode, controlled by the SPISWAI bit
located in the SPICR2 register. In wait mode, if the SPISWAI bit is clear, the SPI operates like in
run mode. If the SPISWAI bit is set, the SPI goes into a power conservative state, with the SPI clock
generation turned off. If the SPI is configured as a master, any transmission in progress stops, but
is resumed after CPU goes into run mode. If the SPI is configured as a slave, reception and
transmission of data continues, so that the slave stays synchronized to the master.
Stop mode
The SPI is inactive in stop mode for reduced power consumption. If the SPI is configured as a
master, any transmission in progress stops, but is resumed after CPU goes into run mode. If the SPI
is configured as a slave, reception and transmission of data continues, so that the slave stays
synchronized to the master.
For a detailed description of operating modes, please refer to Section 13.4.7, “Low Power Mode Options”.
13.1.4
Block Diagram
Figure 13-1 gives an overview on the SPI architecture. The main parts of the SPI are status, control and
data registers, shifter logic, baud rate generator, master/slave control logic, and port control logic.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
516
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
SPI
2
SPI Control Register 1
BIDIROE
2
SPI Control Register 2
SPC0
SPI Status Register
SPIF MODF SPTEF
Interrupt Control
SPI
Interrupt
Request
Baud Rate Generator
Slave
Control
CPOL
CPHA
Phase + SCK In
Slave Baud Rate Polarity
Control
Master Baud Rate
Phase + SCK Out
Polarity
Control
Master
Control
Counter
Bus Clock
Prescaler Clock Select
SPPR
3
SPR
MOSI
MISO
Port
Control
Logic
SCK
SS
Baud Rate
Shift
Clock
Sample
Clock
3
Shifter
SPI Baud Rate Register
Data In
LSBFE=1
LSBFE=0
LSBFE=1
MSB
SPI Data Register
LSBFE=0
LSBFE=0 LSB
LSBFE=1
Data Out
Figure 13-1. SPI Block Diagram
13.2
External Signal Description
This section lists the name and description of all ports including inputs and outputs that do, or may, connect
off chip. The SPI module has a total of four external pins.
13.2.1
MOSI — Master Out/Slave In Pin
This pin is used to transmit data out of the SPI module when it is configured as a master and receive data
when it is configured as slave.
13.2.2
MISO — Master In/Slave Out Pin
This pin is used to transmit data out of the SPI module when it is configured as a slave and receive data
when it is configured as master.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
517
Chapter 13 Serial Peripheral Interface (S12SPIV5)
13.2.3
SS — Slave Select Pin
This pin is used to output the select signal from the SPI module to another peripheral with which a data
transfer is to take place when it is configured as a master and it is used as an input to receive the slave select
signal when the SPI is configured as slave.
13.2.4
SCK — Serial Clock Pin
In master mode, this is the synchronous output clock. In slave mode, this is the synchronous input clock.
13.3
Memory Map and Register Definition
This section provides a detailed description of address space and registers used by the SPI.
13.3.1
Module Memory Map
The memory map for the SPI is given in Figure 13-2. The address listed for each register is the sum of a
base address and an address offset. The base address is defined at the SoC level and the address offset is
defined at the module level. Reads from the reserved bits return zeros and writes to the reserved bits have
no effect.
Register
Name
Bit 7
6
5
4
3
2
1
Bit 0
SPIE
SPE
SPTIE
MSTR
CPOL
CPHA
SSOE
LSBFE
MODFEN
BIDIROE
SPISWAI
SPC0
SPR2
SPR1
SPR0
0x0000
SPICR1
R
W
0x0001
SPICR2
R
W
0
0x0002
SPIBR
R
W
0
0x0003
SPISR
R
W
0x0004
SPIDRH
XFRW
0
0
0
SPPR2
SPPR1
SPPR0
SPIF
0
SPTEF
MODF
0
0
0
0
R
W
R15
T15
R14
T14
R13
T13
R12
T12
R11
T11
R10
T10
R9
T9
R8
T8
0x0005
SPIDRL
R
W
R7
T7
R6
T6
R5
T5
R4
T4
R3
T3
R2
T2
R1
T1
R0
T0
0x0006
Reserved
R
W
0x0007
Reserved
R
W
= Unimplemented or Reserved
Figure 13-2. SPI Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
518
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
13.3.2
Register Descriptions
This section consists of register descriptions in address order. Each description includes a standard register
diagram with an associated figure number. Details of register bit and field function follow the register
diagrams, in bit order.
13.3.2.1
SPI Control Register 1 (SPICR1)
Module Base +0x0000
R
W
Reset
7
6
5
4
3
2
1
0
SPIE
SPE
SPTIE
MSTR
CPOL
CPHA
SSOE
LSBFE
0
0
0
0
0
1
0
0
Figure 13-3. SPI Control Register 1 (SPICR1)
Read: Anytime
Write: Anytime
Table 13-2. SPICR1 Field Descriptions
Field
Description
7
SPIE
SPI Interrupt Enable Bit — This bit enables SPI interrupt requests, if SPIF or MODF status flag is set.
0 SPI interrupts disabled.
1 SPI interrupts enabled.
6
SPE
SPI System Enable Bit — This bit enables the SPI system and dedicates the SPI port pins to SPI system
functions. If SPE is cleared, SPI is disabled and forced into idle state, status bits in SPISR register are reset.
0 SPI disabled (lower power consumption).
1 SPI enabled, port pins are dedicated to SPI functions.
5
SPTIE
SPI Transmit Interrupt Enable — This bit enables SPI interrupt requests, if SPTEF flag is set.
0 SPTEF interrupt disabled.
1 SPTEF interrupt enabled.
4
MSTR
SPI Master/Slave Mode Select Bit — This bit selects whether the SPI operates in master or slave mode.
Switching the SPI from master to slave or vice versa forces the SPI system into idle state.
0 SPI is in slave mode.
1 SPI is in master mode.
3
CPOL
SPI Clock Polarity Bit — This bit selects an inverted or non-inverted SPI clock. To transmit data between SPI
modules, the SPI modules must have identical CPOL values. In master mode, a change of this bit will abort a
transmission in progress and force the SPI system into idle state.
0 Active-high clocks selected. In idle state SCK is low.
1 Active-low clocks selected. In idle state SCK is high.
2
CPHA
SPI Clock Phase Bit — This bit is used to select the SPI clock format. In master mode, a change of this bit will
abort a transmission in progress and force the SPI system into idle state.
0 Sampling of data occurs at odd edges (1,3,5,...) of the SCK clock.
1 Sampling of data occurs at even edges (2,4,6,...) of the SCK clock.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
519
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Table 13-2. SPICR1 Field Descriptions (continued)
Field
Description
1
SSOE
Slave Select Output Enable — The SS output feature is enabled only in master mode, if MODFEN is set, by
asserting the SSOE as shown in Table 13-3. In master mode, a change of this bit will abort a transmission in
progress and force the SPI system into idle state.
0
LSBFE
LSB-First Enable — This bit does not affect the position of the MSB and LSB in the data register. Reads and
writes of the data register always have the MSB in the highest bit position. In master mode, a change of this bit
will abort a transmission in progress and force the SPI system into idle state.
0 Data is transferred most significant bit first.
1 Data is transferred least significant bit first.
Table 13-3. SS Input / Output Selection
13.3.2.2
MODFEN
SSOE
Master Mode
Slave Mode
0
0
SS not used by SPI
SS input
0
1
SS not used by SPI
SS input
1
0
SS input with MODF feature
SS input
1
1
SS is slave select output
SS input
SPI Control Register 2 (SPICR2)
Module Base +0x0001
7
R
0
W
Reset
0
6
5
XFRW
0
0
0
4
3
MODFEN
BIDIROE
0
0
2
0
0
1
0
SPISWAI
SPC0
0
0
= Unimplemented or Reserved
Figure 13-4. SPI Control Register 2 (SPICR2)
Read: Anytime
Write: Anytime; writes to the reserved bits have no effect
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
520
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Table 13-4. SPICR2 Field Descriptions
Field
Description
6
XFRW
Transfer Width — This bit is used for selecting the data transfer width. If 8-bit transfer width is selected, SPIDRL
becomes the dedicated data register and SPIDRH is unused. If 16-bit transfer width is selected, SPIDRH and
SPIDRL form a 16-bit data register. Please refer to Section 13.3.2.4, “SPI Status Register (SPISR) for
information about transmit/receive data handling and the interrupt flag clearing mechanism. In master mode, a
change of this bit will abort a transmission in progress and force the SPI system into idle state.
0 8-bit Transfer Width (n = 8)(1)
1 16-bit Transfer Width (n = 16)1
4
MODFEN
Mode Fault Enable Bit — This bit allows the MODF failure to be detected. If the SPI is in master mode and
MODFEN is cleared, then the SS port pin is not used by the SPI. In slave mode, the SS is available only as an
input regardless of the value of MODFEN. For an overview on the impact of the MODFEN bit on the SS port pin
configuration, refer to Table 13-3. In master mode, a change of this bit will abort a transmission in progress and
force the SPI system into idle state.
0 SS port pin is not used by the SPI.
1 SS port pin with MODF feature.
3
BIDIROE
Output Enable in the Bidirectional Mode of Operation — This bit controls the MOSI and MISO output buffer
of the SPI, when in bidirectional mode of operation (SPC0 is set). In master mode, this bit controls the output
buffer of the MOSI port, in slave mode it controls the output buffer of the MISO port. In master mode, with SPC0
set, a change of this bit will abort a transmission in progress and force the SPI into idle state.
0 Output buffer disabled.
1 Output buffer enabled.
1
SPISWAI
SPI Stop in Wait Mode Bit — This bit is used for power conservation while in wait mode.
0 SPI clock operates normally in wait mode.
1 Stop SPI clock generation when in wait mode.
0
Serial Pin Control Bit 0 — This bit enables bidirectional pin configurations as shown in Table 13-5. In master
SPC0
mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state.
1. n is used later in this document as a placeholder for the selected transfer width.
Table 13-5. Bidirectional Pin Configurations
Pin Mode
SPC0
BIDIROE
MISO
MOSI
Master Mode of Operation
Normal
0
X
Master In
Master Out
Bidirectional
1
0
MISO not used by SPI
Master In
1
Master I/O
Slave Mode of Operation
Normal
0
X
Slave Out
Slave In
Bidirectional
1
0
Slave In
MOSI not used by SPI
1
Slave I/O
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
521
Chapter 13 Serial Peripheral Interface (S12SPIV5)
13.3.2.3
SPI Baud Rate Register (SPIBR)
Module Base +0x0002
7
R
0
W
Reset
0
6
5
4
3
SPPR2
SPPR1
SPPR0
0
0
0
0
0
2
1
0
SPR2
SPR1
SPR0
0
0
0
= Unimplemented or Reserved
Figure 13-5. SPI Baud Rate Register (SPIBR)
Read: Anytime
Write: Anytime; writes to the reserved bits have no effect
Table 13-6. SPIBR Field Descriptions
Field
Description
6–4
SPPR[2:0]
SPI Baud Rate Preselection Bits — These bits specify the SPI baud rates as shown in Table 13-7. In master
mode, a change of these bits will abort a transmission in progress and force the SPI system into idle state.
2–0
SPR[2:0]
SPI Baud Rate Selection Bits — These bits specify the SPI baud rates as shown in Table 13-7. In master mode,
a change of these bits will abort a transmission in progress and force the SPI system into idle state.
The baud rate divisor equation is as follows:
BaudRateDivisor = (SPPR + 1) • 2(SPR + 1)
Eqn. 13-1
The baud rate can be calculated with the following equation:
Baud Rate = BusClock / BaudRateDivisor
Eqn. 13-2
NOTE
For maximum allowed baud rates, please refer to the SPI Electrical
Specification in the Electricals chapter of this data sheet.
Table 13-7. Example SPI Baud Rate Selection (25 MHz Bus Clock) (Sheet 1 of 3)
SPPR2
SPPR1
SPPR0
SPR2
SPR1
SPR0
Baud Rate
Divisor
Baud Rate
0
0
0
0
0
0
2
12.5 Mbit/s
0
0
0
0
0
1
4
6.25 Mbit/s
0
0
0
0
1
0
8
3.125 Mbit/s
0
0
0
0
1
1
16
1.5625 Mbit/s
0
0
0
1
0
0
32
781.25 kbit/s
0
0
0
1
0
1
64
390.63 kbit/s
0
0
0
1
1
0
128
195.31 kbit/s
0
0
0
1
1
1
256
97.66 kbit/s
0
0
1
0
0
0
4
6.25 Mbit/s
0
0
1
0
0
1
8
3.125 Mbit/s
0
0
1
0
1
0
16
1.5625 Mbit/s
0
0
1
0
1
1
32
781.25 kbit/s
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
522
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Table 13-7. Example SPI Baud Rate Selection (25 MHz Bus Clock) (Sheet 2 of 3)
Baud Rate
Divisor
Baud Rate
0
64
390.63 kbit/s
1
128
195.31 kbit/s
1
0
256
97.66 kbit/s
1
1
512
48.83 kbit/s
0
0
0
6
4.16667 Mbit/s
0
0
1
12
2.08333 Mbit/s
0
0
1
0
24
1.04167 Mbit/s
0
0
1
1
48
520.83 kbit/s
1
0
1
0
0
96
260.42 kbit/s
1
0
1
0
1
192
130.21 kbit/s
0
1
0
1
1
0
384
65.10 kbit/s
0
1
0
1
1
1
768
32.55 kbit/s
0
1
1
0
0
0
8
3.125 Mbit/s
0
1
1
0
0
1
16
1.5625 Mbit/s
0
1
1
0
1
0
32
781.25 kbit/s
0
1
1
0
1
1
64
390.63 kbit/s
0
1
1
1
0
0
128
195.31 kbit/s
0
1
1
1
0
1
256
97.66 kbit/s
0
1
1
1
1
0
512
48.83 kbit/s
0
1
1
1
1
1
1024
24.41 kbit/s
1
0
0
0
0
0
10
2.5 Mbit/s
1
0
0
0
0
1
20
1.25 Mbit/s
1
0
0
0
1
0
40
625 kbit/s
1
0
0
0
1
1
80
312.5 kbit/s
1
0
0
1
0
0
160
156.25 kbit/s
1
0
0
1
0
1
320
78.13 kbit/s
1
0
0
1
1
0
640
39.06 kbit/s
1
0
0
1
1
1
1280
19.53 kbit/s
1
0
1
0
0
0
12
2.08333 Mbit/s
1
0
1
0
0
1
24
1.04167 Mbit/s
1
0
1
0
1
0
48
520.83 kbit/s
1
0
1
0
1
1
96
260.42 kbit/s
1
0
1
1
0
0
192
130.21 kbit/s
1
0
1
1
0
1
384
65.10 kbit/s
1
0
1
1
1
0
768
32.55 kbit/s
1
0
1
1
1
1
1536
16.28 kbit/s
1
1
0
0
0
0
14
1.78571 Mbit/s
1
1
0
0
0
1
28
892.86 kbit/s
1
1
0
0
1
0
56
446.43 kbit/s
1
1
0
0
1
1
112
223.21 kbit/s
1
1
0
1
0
0
224
111.61 kbit/s
1
1
0
1
0
1
448
55.80 kbit/s
SPPR2
SPPR1
SPPR0
SPR2
SPR1
SPR0
0
0
1
1
0
0
0
1
1
0
0
0
1
1
0
0
1
1
0
1
0
0
1
0
0
1
0
1
0
0
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
523
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Table 13-7. Example SPI Baud Rate Selection (25 MHz Bus Clock) (Sheet 3 of 3)
Baud Rate
Divisor
Baud Rate
0
896
27.90 kbit/s
1
1792
13.95 kbit/s
0
0
16
1.5625 Mbit/s
0
1
32
781.25 kbit/s
0
1
0
64
390.63 kbit/s
0
1
1
128
195.31 kbit/s
1
1
0
0
256
97.66 kbit/s
1
1
0
1
512
48.83 kbit/s
1
1
1
1
0
1024
24.41 kbit/s
1
1
1
1
1
2048
12.21 kbit/s
SPPR2
SPPR1
SPPR0
SPR2
SPR1
SPR0
1
1
0
1
1
1
1
0
1
1
1
1
1
0
1
1
1
0
1
1
1
1
1
1
1
1
1
1
1
1
13.3.2.4
SPI Status Register (SPISR)
Module Base +0x0003
R
7
6
5
4
3
2
1
0
SPIF
0
SPTEF
MODF
0
0
0
0
0
0
1
0
0
0
0
0
W
Reset
= Unimplemented or Reserved
Figure 13-6. SPI Status Register (SPISR)
Read: Anytime
Write: Has no effect
Table 13-8. SPISR Field Descriptions
Field
Description
7
SPIF
SPIF Interrupt Flag — This bit is set after received data has been transferred into the SPI data register. For
information about clearing SPIF Flag, please refer to Table 13-9.
0 Transfer not yet complete.
1 New data copied to SPIDR.
5
SPTEF
SPI Transmit Empty Interrupt Flag — If set, this bit indicates that the transmit data register is empty. For
information about clearing this bit and placing data into the transmit data register, please refer to Table 13-10.
0 SPI data register not empty.
1 SPI data register empty.
4
MODF
Mode Fault Flag — This bit is set if the SS input becomes low while the SPI is configured as a master and mode
fault detection is enabled, MODFEN bit of SPICR2 register is set. Refer to MODFEN bit description in
Section 13.3.2.2, “SPI Control Register 2 (SPICR2)”. The flag is cleared automatically by a read of the SPI status
register (with MODF set) followed by a write to the SPI control register 1.
0 Mode fault has not occurred.
1 Mode fault has occurred.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
524
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Table 13-9. SPIF Interrupt Flag Clearing Sequence
XFRW Bit
SPIF Interrupt Flag Clearing Sequence
0
Read SPISR with SPIF == 1
1
Read SPISR with SPIF == 1
then
Read SPIDRL
Byte Read SPIDRL (1)
or
then Byte Read SPIDRH (2)
Byte Read SPIDRL
or
Word Read (SPIDRH:SPIDRL)
1. Data in SPIDRH is lost in this case.
2. SPIDRH can be read repeatedly without any effect on SPIF. SPIF Flag is cleared only by the read
of SPIDRL after reading SPISR with SPIF == 1.
Table 13-10. SPTEF Interrupt Flag Clearing Sequence
XFRW Bit
SPTEF Interrupt Flag Clearing Sequence
0
Read SPISR with SPTEF == 1 then
1
Read SPISR with SPTEF == 1
Write to SPIDRL (1)
Byte Write to SPIDRL 1(2)
or
then Byte Write to SPIDRH 1(3) Byte Write to SPIDRL 1
or
Word Write to (SPIDRH:SPIDRL) 1
1. Any write to SPIDRH or SPIDRL with SPTEF == 0 is effectively ignored.
2. Data in SPIDRH is undefined in this case.
3. SPIDRH can be written repeatedly without any effect on SPTEF. SPTEF Flag is cleared only by
writing to SPIDRL after reading SPISR with SPTEF == 1.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
525
Chapter 13 Serial Peripheral Interface (S12SPIV5)
13.3.2.5
SPI Data Register (SPIDR = SPIDRH:SPIDRL)
Module Base +0x0004
7
6
5
4
3
2
1
0
R
R15
R14
R13
R12
R11
R10
R9
R8
W
T15
T14
T13
T12
T11
T10
T9
T8
0
0
0
0
0
0
0
0
Reset
Figure 13-7. SPI Data Register High (SPIDRH)
Module Base +0x0005
7
6
5
4
3
2
1
0
R
R7
R6
R5
R4
R3
R2
R1
R0
W
T7
T6
T5
T4
T3
T2
T1
T0
0
0
0
0
0
0
0
0
Reset
Figure 13-8. SPI Data Register Low (SPIDRL)
Read: Anytime; read data only valid when SPIF is set
Write: Anytime
The SPI data register is both the input and output register for SPI data. A write to this register
allows data to be queued and transmitted. For an SPI configured as a master, queued data is
transmitted immediately after the previous transmission has completed. The SPI transmitter empty
flag SPTEF in the SPISR register indicates when the SPI data register is ready to accept new data.
Received data in the SPIDR is valid when SPIF is set.
If SPIF is cleared and data has been received, the received data is transferred from the receive shift
register to the SPIDR and SPIF is set.
If SPIF is set and not serviced, and a second data value has been received, the second received data
is kept as valid data in the receive shift register until the start of another transmission. The data in
the SPIDR does not change.
If SPIF is set and valid data is in the receive shift register, and SPIF is serviced before the start of
a third transmission, the data in the receive shift register is transferred into the SPIDR and SPIF
remains set (see Figure 13-9).
If SPIF is set and valid data is in the receive shift register, and SPIF is serviced after the start of a
third transmission, the data in the receive shift register has become invalid and is not transferred
into the SPIDR (see Figure 13-10).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
526
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Data A Received
Data B Received
Data C Received
SPIF Serviced
Receive Shift Register
Data B
Data A
Data C
SPIF
SPI Data Register
Data B
Data A
= Unspecified
Data C
= Reception in progress
Figure 13-9. Reception with SPIF serviced in Time
Data A Received
Data B Received
Data C Received
Data B Lost
SPIF Serviced
Receive Shift Register
Data B
Data A
Data C
SPIF
SPI Data Register
Data A
= Unspecified
Data C
= Reception in progress
Figure 13-10. Reception with SPIF serviced too late
13.4
Functional Description
The SPI module allows a duplex, synchronous, serial communication between the MCU and peripheral
devices. Software can poll the SPI status flags or SPI operation can be interrupt driven.
The SPI system is enabled by setting the SPI enable (SPE) bit in SPI control register 1. While SPE is set,
the four associated SPI port pins are dedicated to the SPI function as:
• Slave select (SS)
• Serial clock (SCK)
• Master out/slave in (MOSI)
• Master in/slave out (MISO)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
527
Chapter 13 Serial Peripheral Interface (S12SPIV5)
The main element of the SPI system is the SPI data register. The n-bit1 data register in the master and the
n-bit1 data register in the slave are linked by the MOSI and MISO pins to form a distributed 2n-bit1
register. When a data transfer operation is performed, this 2n-bit1 register is serially shifted n1 bit positions
by the S-clock from the master, so data is exchanged between the master and the slave. Data written to the
master SPI data register becomes the output data for the slave, and data read from the master SPI data
register after a transfer operation is the input data from the slave.
A read of SPISR with SPTEF = 1 followed by a write to SPIDR puts data into the transmit data register.
When a transfer is complete and SPIF is cleared, received data is moved into the receive data register. This
data register acts as the SPI receive data register for reads and as the SPI transmit data register for writes.
A common SPI data register address is shared for reading data from the read data buffer and for writing
data to the transmit data register.
The clock phase control bit (CPHA) and a clock polarity control bit (CPOL) in the SPI control register 1
(SPICR1) select one of four possible clock formats to be used by the SPI system. The CPOL bit simply
selects a non-inverted or inverted clock. The CPHA bit is used to accommodate two fundamentally
different protocols by sampling data on odd numbered SCK edges or on even numbered SCK edges (see
Section 13.4.3, “Transmission Formats”).
The SPI can be configured to operate as a master or as a slave. When the MSTR bit in SPI control register1
is set, master mode is selected, when the MSTR bit is clear, slave mode is selected.
NOTE
A change of CPOL or MSTR bit while there is a received byte pending in
the receive shift register will destroy the received byte and must be avoided.
13.4.1
Master Mode
The SPI operates in master mode when the MSTR bit is set. Only a master SPI module can initiate
transmissions. A transmission begins by writing to the master SPI data register. If the shift register is
empty, data immediately transfers to the shift register. Data begins shifting out on the MOSI pin under the
control of the serial clock.
• Serial clock
The SPR2, SPR1, and SPR0 baud rate selection bits, in conjunction with the SPPR2, SPPR1, and
SPPR0 baud rate preselection bits in the SPI baud rate register, control the baud rate generator and
determine the speed of the transmission. The SCK pin is the SPI clock output. Through the SCK
pin, the baud rate generator of the master controls the shift register of the slave peripheral.
• MOSI, MISO pin
In master mode, the function of the serial data output pin (MOSI) and the serial data input pin
(MISO) is determined by the SPC0 and BIDIROE control bits.
• SS pin
If MODFEN and SSOE are set, the SS pin is configured as slave select output. The SS output
becomes low during each transmission and is high when the SPI is in idle state.
If MODFEN is set and SSOE is cleared, the SS pin is configured as input for detecting mode fault
error. If the SS input becomes low this indicates a mode fault error where another master tries to
1. n depends on the selected transfer width, please refer to Section 13.3.2.2, “SPI Control Register 2 (SPICR2)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
528
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
drive the MOSI and SCK lines. In this case, the SPI immediately switches to slave mode, by
clearing the MSTR bit and also disables the slave output buffer MISO (or SISO in bidirectional
mode). So the result is that all outputs are disabled and SCK, MOSI, and MISO are inputs. If a
transmission is in progress when the mode fault occurs, the transmission is aborted and the SPI is
forced into idle state.
This mode fault error also sets the mode fault (MODF) flag in the SPI status register (SPISR). If
the SPI interrupt enable bit (SPIE) is set when the MODF flag becomes set, then an SPI interrupt
sequence is also requested.
When a write to the SPI data register in the master occurs, there is a half SCK-cycle delay. After
the delay, SCK is started within the master. The rest of the transfer operation differs slightly,
depending on the clock format specified by the SPI clock phase bit, CPHA, in SPI control register 1
(see Section 13.4.3, “Transmission Formats”).
NOTE
A change of the bits CPOL, CPHA, SSOE, LSBFE, XFRW, MODFEN,
SPC0, or BIDIROE with SPC0 set, SPPR2-SPPR0 and SPR2-SPR0 in
master mode will abort a transmission in progress and force the SPI into idle
state. The remote slave cannot detect this, therefore the master must ensure
that the remote slave is returned to idle state.
13.4.2
Slave Mode
The SPI operates in slave mode when the MSTR bit in SPI control register 1 is clear.
• Serial clock
In slave mode, SCK is the SPI clock input from the master.
• MISO, MOSI pin
In slave mode, the function of the serial data output pin (MISO) and serial data input pin (MOSI)
is determined by the SPC0 bit and BIDIROE bit in SPI control register 2.
• SS pin
The SS pin is the slave select input. Before a data transmission occurs, the SS pin of the slave SPI
must be low. SS must remain low until the transmission is complete. If SS goes high, the SPI is
forced into idle state.
The SS input also controls the serial data output pin, if SS is high (not selected), the serial data
output pin is high impedance, and, if SS is low, the first bit in the SPI data register is driven out of
the serial data output pin. Also, if the slave is not selected (SS is high), then the SCK input is
ignored and no internal shifting of the SPI shift register occurs.
Although the SPI is capable of duplex operation, some SPI peripherals are capable of only
receiving SPI data in a slave mode. For these simpler devices, there is no serial data out pin.
NOTE
When peripherals with duplex capability are used, take care not to
simultaneously enable two receivers whose serial outputs drive the same
system slave’s serial data output line.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
529
Chapter 13 Serial Peripheral Interface (S12SPIV5)
As long as no more than one slave device drives the system slave’s serial data output line, it is possible for
several slaves to receive the same transmission from a master, although the master would not receive return
information from all of the receiving slaves.
If the CPHA bit in SPI control register 1 is clear, odd numbered edges on the SCK input cause the data at
the serial data input pin to be latched. Even numbered edges cause the value previously latched from the
serial data input pin to shift into the LSB or MSB of the SPI shift register, depending on the LSBFE bit.
If the CPHA bit is set, even numbered edges on the SCK input cause the data at the serial data input pin to
be latched. Odd numbered edges cause the value previously latched from the serial data input pin to shift
into the LSB or MSB of the SPI shift register, depending on the LSBFE bit.
When CPHA is set, the first edge is used to get the first data bit onto the serial data output pin. When CPHA
is clear and the SS input is low (slave selected), the first bit of the SPI data is driven out of the serial data
output pin. After the nth1 shift, the transfer is considered complete and the received data is transferred into
the SPI data register. To indicate transfer is complete, the SPIF flag in the SPI status register is set.
NOTE
A change of the bits CPOL, CPHA, SSOE, LSBFE, MODFEN, SPC0, or
BIDIROE with SPC0 set in slave mode will corrupt a transmission in
progress and must be avoided.
13.4.3
Transmission Formats
During an SPI transmission, data is transmitted (shifted out serially) and received (shifted in serially)
simultaneously. The serial clock (SCK) synchronizes shifting and sampling of the information on the two
serial data lines. A slave select line allows selection of an individual slave SPI device; slave devices that
are not selected do not interfere with SPI bus activities. Optionally, on a master SPI device, the slave select
line can be used to indicate multiple-master bus contention.
MASTER SPI
SHIFT REGISTER
BAUD RATE
GENERATOR
SLAVE SPI
MISO
MISO
MOSI
MOSI
SCK
SCK
SS
VDD
SHIFT REGISTER
SS
Figure 13-11. Master/Slave Transfer Block Diagram
13.4.3.1
Clock Phase and Polarity Controls
Using two bits in the SPI control register 1, software selects one of four combinations of serial clock phase
and polarity.
1. n depends on the selected transfer width, please refer to Section 13.3.2.2, “SPI Control Register 2 (SPICR2)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
530
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
The CPOL clock polarity control bit specifies an active high or low clock and has no significant effect on
the transmission format.
The CPHA clock phase control bit selects one of two fundamentally different transmission formats.
Clock phase and polarity should be identical for the master SPI device and the communicating slave
device. In some cases, the phase and polarity are changed between transmissions to allow a master device
to communicate with peripheral slaves having different requirements.
13.4.3.2
CPHA = 0 Transfer Format
The first edge on the SCK line is used to clock the first data bit of the slave into the master and the first
data bit of the master into the slave. In some peripherals, the first bit of the slave’s data is available at the
slave’s data out pin as soon as the slave is selected. In this format, the first SCK edge is issued a half cycle
after SS has become low.
A half SCK cycle later, the second edge appears on the SCK line. When this second edge occurs, the value
previously latched from the serial data input pin is shifted into the LSB or MSB of the shift register,
depending on LSBFE bit.
After this second edge, the next bit of the SPI master data is transmitted out of the serial data output pin of
the master to the serial input pin on the slave. This process continues for a total of 16 edges on the SCK
line, with data being latched on odd numbered edges and shifted on even numbered edges.
Data reception is double buffered. Data is shifted serially into the SPI shift register during the transfer and
is transferred to the parallel SPI data register after the last bit is shifted in.
After 2n1 (last) SCK edges:
• Data that was previously in the master SPI data register should now be in the slave data register and
the data that was in the slave data register should be in the master.
• The SPIF flag in the SPI status register is set, indicating that the transfer is complete.
Figure 13-12 is a timing diagram of an SPI transfer where CPHA = 0. SCK waveforms are shown for
CPOL = 0 and CPOL = 1. The diagram may be interpreted as a master or slave timing diagram because
the SCK, MISO, and MOSI pins are connected directly between the master and the slave. The MISO signal
is the output from the slave and the MOSI signal is the output from the master. The SS pin of the master
must be either high or reconfigured as a general-purpose output not affecting the SPI.
1. n depends on the selected transfer width, please refer to Section 13.3.2.2, “SPI Control Register 2 (SPICR2)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
531
Chapter 13 Serial Peripheral Interface (S12SPIV5)
End of Idle State
Begin
1
SCK Edge Number
2
3
4
5
6
7
8
Begin of Idle State
End
Transfer
9
10
11
12
13 14
15
16
Bit 1
Bit 6
LSB Minimum 1/2 SCK
for tT, tl, tL
MSB
SCK (CPOL = 0)
SCK (CPOL = 1)
If next transfer begins here
SAMPLE I
MOSI/MISO
CHANGE O
MOSI pin
CHANGE O
MISO pin
SEL SS (O)
Master only
SEL SS (I)
tT
tL
MSB first (LSBFE = 0): MSB
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
LSB first (LSBFE = 1): LSB
Bit 1
Bit 2
Bit 3
Bit 4
Bit 5
tL = Minimum leading time before the first SCK edge
tT = Minimum trailing time after the last SCK edge
tI = Minimum idling time between transfers (minimum SS high time)
tL, tT, and tI are guaranteed for the master mode and required for the slave mode.
tI
tL
Figure 13-12. SPI Clock Format 0 (CPHA = 0), with 8-bit Transfer Width selected (XFRW = 0)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
532
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
End of Idle State
SCK Edge Number
Begin
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Begin of Idle State
End
Transfer
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
SCK (CPOL = 0)
SCK (CPOL = 1)
If next transfer begins here
SAMPLE I
MOSI/MISO
CHANGE O
MOSI pin
CHANGE O
MISO pin
SEL SS (O)
Master only
SEL SS (I)
MSB first (LSBFE = 0)
LSB first (LSBFE = 1)
tL
tT tI tL
MSB Bit 14Bit 13Bit 12Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 LSB
Minimum 1/2 SCK
LSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 Bit 9 Bit 10Bit 11Bit 12Bit 13Bit 14 MSB
for tT, tl, tL
tL = Minimum leading time before the first SCK edge
tT = Minimum trailing time after the last SCK edge
tI = Minimum idling time between transfers (minimum SS high time)
tL, tT, and tI are guaranteed for the master mode and required for the slave mode.
Figure 13-13. SPI Clock Format 0 (CPHA = 0), with 16-Bit Transfer Width selected (XFRW = 1)
In slave mode, if the SS line is not deasserted between the successive transmissions then the content of the
SPI data register is not transmitted; instead the last received data is transmitted. If the SS line is deasserted
for at least minimum idle time (half SCK cycle) between successive transmissions, then the content of the
SPI data register is transmitted.
In master mode, with slave select output enabled the SS line is always deasserted and reasserted between
successive transfers for at least minimum idle time.
13.4.3.3
CPHA = 1 Transfer Format
Some peripherals require the first SCK edge before the first data bit becomes available at the data out pin,
the second edge clocks data into the system. In this format, the first SCK edge is issued by setting the
CPHA bit at the beginning of the n1-cycle transfer operation.
The first edge of SCK occurs immediately after the half SCK clock cycle synchronization delay. This first
edge commands the slave to transfer its first data bit to the serial data input pin of the master.
A half SCK cycle later, the second edge appears on the SCK pin. This is the latching edge for both the
master and slave.
1. n depends on the selected transfer width, please refer to Section 13.3.2.2, “SPI Control Register 2 (SPICR2)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
533
Chapter 13 Serial Peripheral Interface (S12SPIV5)
When the third edge occurs, the value previously latched from the serial data input pin is shifted into the
LSB or MSB of the SPI shift register, depending on LSBFE bit. After this edge, the next bit of the master
data is coupled out of the serial data output pin of the master to the serial input pin on the slave.
This process continues for a total of n1 edges on the SCK line with data being latched on even numbered
edges and shifting taking place on odd numbered edges.
Data reception is double buffered, data is serially shifted into the SPI shift register during the transfer and
is transferred to the parallel SPI data register after the last bit is shifted in.
After 2n1 SCK edges:
• Data that was previously in the SPI data register of the master is now in the data register of the
slave, and data that was in the data register of the slave is in the master.
• The SPIF flag bit in SPISR is set indicating that the transfer is complete.
Figure 13-14 shows two clocking variations for CPHA = 1. The diagram may be interpreted as a master or
slave timing diagram because the SCK, MISO, and MOSI pins are connected directly between the master
and the slave. The MISO signal is the output from the slave, and the MOSI signal is the output from the
master. The SS line is the slave select input to the slave. The SS pin of the master must be either high or
reconfigured as a general-purpose output not affecting the SPI.
End of Idle State
Begin
SCK Edge Number
1
2
3
4
End
Transfer
5
6
7
8
9
10
11
12
13 14
Begin of Idle State
15
16
SCK (CPOL = 0)
SCK (CPOL = 1)
If next transfer begins here
SAMPLE I
MOSI/MISO
CHANGE O
MOSI pin
CHANGE O
MISO pin
SEL SS (O)
Master only
SEL SS (I)
tT
tL
tI
tL
MSB first (LSBFE = 0):
LSB first (LSBFE = 1):
MSB
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
LSB Minimum 1/2 SCK
for tT, tl, tL
LSB
Bit 1
Bit 2
Bit 3
Bit 4
Bit 5
Bit 6
MSB
tL = Minimum leading time before the first SCK edge, not required for back-to-back transfers
tT = Minimum trailing time after the last SCK edge
tI = Minimum idling time between transfers (minimum SS high time), not required for back-to-back transfers
Figure 13-14. SPI Clock Format 1 (CPHA = 1), with 8-Bit Transfer Width selected (XFRW = 0)
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
534
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
End of Idle State
SCK Edge Number
Begin
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Begin of Idle State
End
Transfer
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
SCK (CPOL = 0)
SCK (CPOL = 1)
If next transfer begins here
SAMPLE I
MOSI/MISO
CHANGE O
MOSI pin
CHANGE O
MISO pin
SEL SS (O)
Master only
SEL SS (I)
tT tI tL
Minimum 1/2 SCK
for tT, tl, tL
tL
MSB first (LSBFE = 0)
LSB first (LSBFE = 1)
MSB Bit 14Bit 13Bit 12Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 LSB
LSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 Bit 9 Bit 10Bit 11Bit 12Bit 13Bit 14 MSB
tL = Minimum leading time before the first SCK edge, not required for back-to-back transfers
tT = Minimum trailing time after the last SCK edge
tI = Minimum idling time between transfers (minimum SS high time), not required for back-to-back transfers
Figure 13-15. SPI Clock Format 1 (CPHA = 1), with 16-Bit Transfer Width selected (XFRW = 1)
The SS line can remain active low between successive transfers (can be tied low at all times). This format
is sometimes preferred in systems having a single fixed master and a single slave that drive the MISO data
line.
• Back-to-back transfers in master mode
In master mode, if a transmission has completed and new data is available in the SPI data register,
this data is sent out immediately without a trailing and minimum idle time.
The SPI interrupt request flag (SPIF) is common to both the master and slave modes. SPIF gets set one
half SCK cycle after the last SCK edge.
13.4.4
SPI Baud Rate Generation
Baud rate generation consists of a series of divider stages. Six bits in the SPI baud rate register (SPPR2,
SPPR1, SPPR0, SPR2, SPR1, and SPR0) determine the divisor to the SPI module clock which results in
the SPI baud rate.
The SPI clock rate is determined by the product of the value in the baud rate preselection bits
(SPPR2–SPPR0) and the value in the baud rate selection bits (SPR2–SPR0). The module clock divisor
equation is shown in Equation 13-3.
BaudRateDivisor = (SPPR + 1) • 2(SPR + 1)
Eqn. 13-3
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
535
Chapter 13 Serial Peripheral Interface (S12SPIV5)
When all bits are clear (the default condition), the SPI module clock is divided by 2. When the selection
bits (SPR2–SPR0) are 001 and the preselection bits (SPPR2–SPPR0) are 000, the module clock divisor
becomes 4. When the selection bits are 010, the module clock divisor becomes 8, etc.
When the preselection bits are 001, the divisor determined by the selection bits is multiplied by 2. When
the preselection bits are 010, the divisor is multiplied by 3, etc. See Table 13-7 for baud rate calculations
for all bit conditions, based on a 25 MHz bus clock. The two sets of selects allows the clock to be divided
by a non-power of two to achieve other baud rates such as divide by 6, divide by 10, etc.
The baud rate generator is activated only when the SPI is in master mode and a serial transfer is taking
place. In the other cases, the divider is disabled to decrease IDD current.
NOTE
For maximum allowed baud rates, please refer to the SPI Electrical
Specification in the Electricals chapter of this data sheet.
13.4.5
13.4.5.1
Special Features
SS Output
The SS output feature automatically drives the SS pin low during transmission to select external devices
and drives it high during idle to deselect external devices. When SS output is selected, the SS output pin
is connected to the SS input pin of the external device.
The SS output is available only in master mode during normal SPI operation by asserting SSOE and
MODFEN bit as shown in Table 13-3.
The mode fault feature is disabled while SS output is enabled.
NOTE
Care must be taken when using the SS output feature in a multimaster
system because the mode fault feature is not available for detecting system
errors between masters.
13.4.5.2
Bidirectional Mode (MOMI or SISO)
The bidirectional mode is selected when the SPC0 bit is set in SPI control register 2 (see Table 13-11). In
this mode, the SPI uses only one serial data pin for the interface with external device(s). The MSTR bit
decides which pin to use. The MOSI pin becomes the serial data I/O (MOMI) pin for the master mode, and
the MISO pin becomes serial data I/O (SISO) pin for the slave mode. The MISO pin in master mode and
MOSI pin in slave mode are not used by the SPI.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
536
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
Table 13-11. Normal Mode and Bidirectional Mode
When SPE = 1
Master Mode MSTR = 1
Serial Out
Normal Mode
SPC0 = 0
MOSI
MOSI
Serial In
SPI
SPI
Serial In
MISO
Serial Out
Bidirectional Mode
SPC0 = 1
Slave Mode MSTR = 0
MOMI
Serial Out
MISO
Serial In
BIDIROE
SPI
Serial In
BIDIROE
SPI
Serial Out
SISO
The direction of each serial I/O pin depends on the BIDIROE bit. If the pin is configured as an output,
serial data from the shift register is driven out on the pin. The same pin is also the serial input to the shift
register.
• The SCK is output for the master mode and input for the slave mode.
• The SS is the input or output for the master mode, and it is always the input for the slave mode.
• The bidirectional mode does not affect SCK and SS functions.
NOTE
In bidirectional master mode, with mode fault enabled, both data pins MISO
and MOSI can be occupied by the SPI, though MOSI is normally used for
transmissions in bidirectional mode and MISO is not used by the SPI. If a
mode fault occurs, the SPI is automatically switched to slave mode. In this
case MISO becomes occupied by the SPI and MOSI is not used. This must
be considered, if the MISO pin is used for another purpose.
13.4.6
Error Conditions
The SPI has one error condition:
• Mode fault error
13.4.6.1
Mode Fault Error
If the SS input becomes low while the SPI is configured as a master, it indicates a system error where more
than one master may be trying to drive the MOSI and SCK lines simultaneously. This condition is not
permitted in normal operation, the MODF bit in the SPI status register is set automatically, provided the
MODFEN bit is set.
In the special case where the SPI is in master mode and MODFEN bit is cleared, the SS pin is not used by
the SPI. In this special case, the mode fault error function is inhibited and MODF remains cleared. In case
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
537
Chapter 13 Serial Peripheral Interface (S12SPIV5)
the SPI system is configured as a slave, the SS pin is a dedicated input pin. Mode fault error doesn’t occur
in slave mode.
If a mode fault error occurs, the SPI is switched to slave mode, with the exception that the slave output
buffer is disabled. So SCK, MISO, and MOSI pins are forced to be high impedance inputs to avoid any
possibility of conflict with another output driver. A transmission in progress is aborted and the SPI is
forced into idle state.
If the mode fault error occurs in the bidirectional mode for a SPI system configured in master mode, output
enable of the MOMI (MOSI in bidirectional mode) is cleared if it was set. No mode fault error occurs in
the bidirectional mode for SPI system configured in slave mode.
The mode fault flag is cleared automatically by a read of the SPI status register (with MODF set) followed
by a write to SPI control register 1. If the mode fault flag is cleared, the SPI becomes a normal master or
slave again.
NOTE
If a mode fault error occurs and a received data byte is pending in the receive
shift register, this data byte will be lost.
13.4.7
13.4.7.1
Low Power Mode Options
SPI in Run Mode
In run mode with the SPI system enable (SPE) bit in the SPI control register clear, the SPI system is in a
low-power, disabled state. SPI registers remain accessible, but clocks to the core of this module are
disabled.
13.4.7.2
SPI in Wait Mode
SPI operation in wait mode depends upon the state of the SPISWAI bit in SPI control register 2.
• If SPISWAI is clear, the SPI operates normally when the CPU is in wait mode
• If SPISWAI is set, SPI clock generation ceases and the SPI module enters a power conservation
state when the CPU is in wait mode.
–
If SPISWAI is set and the SPI is configured for master, any transmission and reception in
progress stops at wait mode entry. The transmission and reception resumes when the SPI exits
wait mode.
–
If SPISWAI is set and the SPI is configured as a slave, any transmission and reception in
progress continues if the SCK continues to be driven from the master. This keeps the slave
synchronized to the master and the SCK.
If the master transmits several bytes while the slave is in wait mode, the slave will continue to
send out bytes consistent with the operation mode at the start of wait mode (i.e., if the slave is
currently sending its SPIDR to the master, it will continue to send the same byte. Else if the
slave is currently sending the last received byte from the master, it will continue to send each
previous master byte).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
538
Freescale Semiconductor
Chapter 13 Serial Peripheral Interface (S12SPIV5)
NOTE
Care must be taken when expecting data from a master while the slave is in
wait or stop mode. Even though the shift register will continue to operate,
the rest of the SPI is shut down (i.e., a SPIF interrupt will not be generated
until exiting stop or wait mode). Also, the byte from the shift register will
not be copied into the SPIDR register until after the slave SPI has exited wait
or stop mode. In slave mode, a received byte pending in the receive shift
register will be lost when entering wait or stop mode. An SPIF flag and
SPIDR copy is generated only if wait mode is entered or exited during a
tranmission. If the slave enters wait mode in idle mode and exits wait mode
in idle mode, neither a SPIF nor a SPIDR copy will occur.
13.4.7.3
SPI in Stop Mode
Stop mode is dependent on the system. The SPI enters stop mode when the module clock is disabled (held
high or low). If the SPI is in master mode and exchanging data when the CPU enters stop mode, the
transmission is frozen until the CPU exits stop mode. After stop, data to and from the external SPI is
exchanged correctly. In slave mode, the SPI will stay synchronized with the master.
The stop mode is not dependent on the SPISWAI bit.
13.4.7.4
Reset
The reset values of registers and signals are described in Section 13.3, “Memory Map and Register
Definition”, which details the registers and their bit fields.
• If a data transmission occurs in slave mode after reset without a write to SPIDR, it will transmit
garbage, or the data last received from the master before the reset.
• Reading from the SPIDR after reset will always read zeros.
13.4.7.5
Interrupts
The SPI only originates interrupt requests when SPI is enabled (SPE bit in SPICR1 set). The following is
a description of how the SPI makes a request and how the MCU should acknowledge that request. The
interrupt vector offset and interrupt priority are chip dependent.
The interrupt flags MODF, SPIF, and SPTEF are logically ORed to generate an interrupt request.
13.4.7.5.1
MODF
MODF occurs when the master detects an error on the SS pin. The master SPI must be configured for the
MODF feature (see Table 13-3). After MODF is set, the current transfer is aborted and the following bit is
changed:
• MSTR = 0, The master bit in SPICR1 resets.
The MODF interrupt is reflected in the status register MODF flag. Clearing the flag will also clear the
interrupt. This interrupt will stay active while the MODF flag is set. MODF has an automatic clearing
process which is described in Section 13.3.2.4, “SPI Status Register (SPISR)”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
539
Chapter 13 Serial Peripheral Interface (S12SPIV5)
13.4.7.5.2
SPIF
SPIF occurs when new data has been received and copied to the SPI data register. After SPIF is set, it does
not clear until it is serviced. SPIF has an automatic clearing process, which is described in
Section 13.3.2.4, “SPI Status Register (SPISR)”.
13.4.7.5.3
SPTEF
SPTEF occurs when the SPI data register is ready to accept new data. After SPTEF is set, it does not clear
until it is serviced. SPTEF has an automatic clearing process, which is described in Section 13.3.2.4, “SPI
Status Register (SPISR)”.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
540
Freescale Semiconductor
Chapter 14
Inter-Integrated Circuit (IICV3) Block Description
Table 14-1. Revision History
Revision
Number
Revision Date
V01.03
28 Jul 2006
V01.04
17 Nov 2006
14.3.1.2/14-545 - Revise Table1-5
V01.05
14 Aug 2007
14.3.1.1/14-545 - Backward compatible for IBAD bit name
14.1
Sections
Affected
Description of Changes
14.7.1.7/14-565 - Update flow-chart of interrupt routine for 10-bit address
Introduction
The inter-IC bus (IIC) is a two-wire, bidirectional serial bus that provides a simple, efficient method of data
exchange between devices. Being a two-wire device, the IIC bus minimizes the need for large numbers of
connections between devices, and eliminates the need for an address decoder.
This bus is suitable for applications requiring occasional communications over a short distance between a
number of devices. It also provides flexibility, allowing additional devices to be connected to the bus for
further expansion and system development.
The interface is designed to operate up to 100 kbps with maximum bus loading and timing. The device is
capable of operating at higher baud rates, up to a maximum of clock/20, with reduced bus loading. The
maximum communication length and the number of devices that can be connected are limited by a
maximum bus capacitance of 400 pF.
14.1.1
Features
The IIC module has the following key features:
• Compatible with I2C bus standard
• Multi-master operation
• Software programmable for one of 256 different serial clock frequencies
• Software selectable acknowledge bit
• Interrupt driven byte-by-byte data transfer
• Arbitration lost interrupt with automatic mode switching from master to slave
• Calling address identification interrupt
• Start and stop signal generation/detection
• Repeated start signal generation
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
541
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
•
•
•
•
Acknowledge bit generation/detection
Bus busy detection
General Call Address detection
Compliant to ten-bit address
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
542
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
14.1.2
Modes of Operation
The IIC functions the same in normal, special, and emulation modes. It has two low power modes: wait
and stop modes.
14.1.3
Block Diagram
The block diagram of the IIC module is shown in Figure 14-1.
IIC
Registers
Start
Stop
Arbitration
Control
Clock
Control
In/Out
Data
Shift
Register
Interrupt
bus_clock
SCL
SDA
Address
Compare
Figure 14-1. IIC Block Diagram
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
543
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
14.2
External Signal Description
The IICV3 module has two external pins.
14.2.1
IIC_SCL — Serial Clock Line Pin
This is the bidirectional serial clock line (SCL) of the module, compatible to the IIC bus specification.
14.2.2
IIC_SDA — Serial Data Line Pin
This is the bidirectional serial data line (SDA) of the module, compatible to the IIC bus specification.
14.3
Memory Map and Register Definition
This section provides a detailed description of all memory and registers for the IIC module.
14.3.1
Register Descriptions
This section consists of register descriptions in address order. Each description includes a standard register
diagram with an associated figure number. Details of register bit and field function follow the register
diagrams, in bit order.
Register
Name
0x0000
IBAD
0x0001
IBFD
0x0002
IBCR
0x0003
IBSR
R
W
R
W
R
W
R
Bit 7
6
5
4
3
2
1
ADR7
ADR6
ADR5
ADR4
ADR3
ADR2
ADR1
IBC7
IBC6
IBC5
IBC4
IBC3
IBC2
IBC1
IBEN
IBIE
MS/SL
Tx/Rx
TXAK
0
0
TCF
IAAS
IBB
D7
D6
D5
GCEN
ADTYPE
0
W
0x0004
IBDR
R
W
0x0005
IBCR2
W
R
RSTA
Bit 0
0
IBC0
IBSWAI
0
SRW
D4
D3
D2
D1
D0
0
0
ADR10
ADR9
ADR8
IBAL
IBIF
RXAK
= Unimplemented or Reserved
Figure 14-2. IIC Register Summary
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
544
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
14.3.1.1
IIC Address Register (IBAD)
Module Base +0x0000
7
6
5
4
3
2
1
ADR7
ADR6
ADR5
ADR4
ADR3
ADR2
ADR1
0
0
0
0
0
0
0
R
0
0
W
Reset
0
= Unimplemented or Reserved
Figure 14-3. IIC Bus Address Register (IBAD)
Read and write anytime
This register contains the address the IIC bus will respond to when addressed as a slave; note that it is not
the address sent on the bus during the address transfer.
Table 14-2. IBAD Field Descriptions
Field
Description
7:1
ADR[7:1]
Slave Address — Bit 1 to bit 7 contain the specific slave address to be used by the IIC bus module.The default
mode of IIC bus is slave mode for an address match on the bus.
0
Reserved
Reserved — Bit 0 of the IBAD is reserved for future compatibility. This bit will always read 0.
14.3.1.2
IIC Frequency Divider Register (IBFD)
Module Base + 0x0001
7
6
5
4
3
2
1
0
IBC7
IBC6
IBC5
IBC4
IBC3
IBC2
IBC1
IBC0
0
0
0
0
0
0
0
0
R
W
Reset
= Unimplemented or Reserved
Figure 14-4. IIC Bus Frequency Divider Register (IBFD)
Read and write anytime
Table 14-3. IBFD Field Descriptions
Field
Description
7:0
IBC[7:0]
I Bus Clock Rate 7:0 — This field is used to prescale the clock for bit rate selection. The bit clock generator is
implemented as a prescale divider — IBC7:6, prescaled shift register — IBC5:3 select the prescaler divider and
IBC2-0 select the shift register tap point. The IBC bits are decoded to give the tap and prescale values as shown
in Table 14-4.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
545
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-4. I-Bus Tap and Prescale Values
IBC2-0
(bin)
SCL Tap
(clocks)
SDA Tap
(clocks)
000
5
1
001
6
1
010
7
2
011
8
2
100
9
3
101
10
3
110
12
4
111
15
4
Table 14-5. Prescale Divider Encoding
IBC5-3
(bin)
scl2start
(clocks)
scl2stop
(clocks)
scl2tap
(clocks)
tap2tap
(clocks)
000
2
7
4
1
001
2
7
4
2
010
2
9
6
4
011
6
9
6
8
100
14
17
14
16
101
30
33
30
32
110
62
65
62
64
111
126
129
126
128
Table 14-6. Multiplier Factor
IBC7-6
MUL
00
01
01
02
10
04
11
RESERVED
The number of clocks from the falling edge of SCL to the first tap (Tap[1]) is defined by the values shown
in the scl2tap column of Table 14-4, all subsequent tap points are separated by 2IBC5-3 as shown in the
tap2tap column in Table 14-5. The SCL Tap is used to generated the SCL period and the SDA Tap is used
to determine the delay from the falling edge of SCL to SDA changing, the SDA hold time.
IBC7–6 defines the multiplier factor MUL. The values of MUL are shown in the Table 14-6.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
546
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
SCL Divider
SCL
SDA Hold
SDA
SDA
SCL Hold(stop)
SCL Hold(start)
SCL
START condition
STOP condition
Figure 14-5. SCL Divider and SDA Hold
The equation used to generate the divider values from the IBFD bits is:
SCL Divider = MUL x {2 x (scl2tap + [(SCL_Tap -1) x tap2tap] + 2)}
The SDA hold delay is equal to the CPU clock period multiplied by the SDA Hold value shown in
Table 14-7. The equation used to generate the SDA Hold value from the IBFD bits is:
SDA Hold = MUL x {scl2tap + [(SDA_Tap - 1) x tap2tap] + 3}
The equation for SCL Hold values to generate the start and stop conditions from the IBFD bits is:
SCL Hold(start) = MUL x [scl2start + (SCL_Tap - 1) x tap2tap]
SCL Hold(stop) = MUL x [scl2stop + (SCL_Tap - 1) x tap2tap]
Table 14-7. IIC Divider and Hold Values (Sheet 1 of 6)
IBC[7:0]
(hex)
SCL Divider
(clocks)
SDA Hold
(clocks)
SCL Hold
(start)
SCL Hold
(stop)
MUL=1
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
547
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-7. IIC Divider and Hold Values (Sheet 2 of 6)
IBC[7:0]
(hex)
SCL Divider
(clocks)
SDA Hold
(clocks)
SCL Hold
(start)
SCL Hold
(stop)
00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
28
29
2A
2B
2C
20/22
22/24
24/26
26/28
28/30
30/32
34/36
40/42
28/32
32/36
36/40
40/44
44/48
48/52
56/60
68/72
48
56
64
72
80
88
104
128
80
96
112
128
144
160
192
240
160
192
224
256
288
320
384
480
320
384
448
512
576
7
7
8
8
9
9
10
10
7
7
9
9
11
11
13
13
9
9
13
13
17
17
21
21
9
9
17
17
25
25
33
33
17
17
33
33
49
49
65
65
33
33
65
65
97
6
7
8
9
10
11
13
16
10
12
14
16
18
20
24
30
18
22
26
30
34
38
46
58
38
46
54
62
70
78
94
118
78
94
110
126
142
158
190
238
158
190
222
254
286
11
12
13
14
15
16
18
21
15
17
19
21
23
25
29
35
25
29
33
37
41
45
53
65
41
49
57
65
73
81
97
121
81
97
113
129
145
161
193
241
161
193
225
257
289
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
548
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-7. IIC Divider and Hold Values (Sheet 3 of 6)
IBC[7:0]
(hex)
SCL Divider
(clocks)
SDA Hold
(clocks)
SCL Hold
(start)
SCL Hold
(stop)
2D
2E
2F
30
31
32
33
34
35
36
37
38
39
3A
3B
3C
3D
3E
3F
640
768
960
640
768
896
1024
1152
1280
1536
1920
1280
1536
1792
2048
2304
2560
3072
3840
97
129
129
65
65
129
129
193
193
257
257
129
129
257
257
385
385
513
513
318
382
478
318
382
446
510
574
638
766
958
638
766
894
1022
1150
1278
1534
1918
321
385
481
321
385
449
513
577
641
769
961
641
769
897
1025
1153
1281
1537
1921
40
41
42
43
44
45
46
47
48
49
4A
4B
4C
4D
4E
4F
50
51
52
53
54
55
56
57
58
40
44
48
52
56
60
68
80
56
64
72
80
88
96
112
136
96
112
128
144
160
176
208
256
160
14
14
16
16
18
18
20
20
14
14
18
18
22
22
26
26
18
18
26
26
34
34
42
42
18
12
14
16
18
20
22
26
32
20
24
28
32
36
40
48
60
36
44
52
60
68
76
92
116
76
22
24
26
28
30
32
36
42
30
34
38
42
46
50
58
70
50
58
66
74
82
90
106
130
82
MUL=2
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
549
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-7. IIC Divider and Hold Values (Sheet 4 of 6)
IBC[7:0]
(hex)
SCL Divider
(clocks)
SDA Hold
(clocks)
SCL Hold
(start)
SCL Hold
(stop)
59
5A
5B
5C
5D
5E
5F
60
61
62
63
64
65
66
67
68
69
6A
6B
6C
6D
6E
6F
70
71
72
73
74
75
76
77
78
79
7A
7B
7C
7D
7E
7F
192
224
256
288
320
384
480
320
384
448
512
576
640
768
960
640
768
896
1024
1152
1280
1536
1920
1280
1536
1792
2048
2304
2560
3072
3840
2560
3072
3584
4096
4608
5120
6144
7680
18
34
34
50
50
66
66
34
34
66
66
98
98
130
130
66
66
130
130
194
194
258
258
130
130
258
258
386
386
514
514
258
258
514
514
770
770
1026
1026
92
108
124
140
156
188
236
156
188
220
252
284
316
380
476
316
380
444
508
572
636
764
956
636
764
892
1020
1148
1276
1532
1916
1276
1532
1788
2044
2300
2556
3068
3836
98
114
130
146
162
194
242
162
194
226
258
290
322
386
482
322
386
450
514
578
642
770
962
642
770
898
1026
1154
1282
1538
1922
1282
1538
1794
2050
2306
2562
3074
3842
80
81
82
83
84
72
80
88
96
104
28
28
32
32
36
24
28
32
36
40
44
48
52
56
60
MUL=4
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
550
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-7. IIC Divider and Hold Values (Sheet 5 of 6)
IBC[7:0]
(hex)
SCL Divider
(clocks)
SDA Hold
(clocks)
SCL Hold
(start)
SCL Hold
(stop)
85
86
87
88
89
8A
8B
8C
8D
8E
8F
90
91
92
93
94
95
96
97
98
99
9A
9B
9C
9D
9E
9F
A0
A1
A2
A3
A4
A5
A6
A7
A8
A9
AA
AB
AC
AD
AE
AF
B0
B1
112
128
152
112
128
144
160
176
192
224
272
192
224
256
288
320
352
416
512
320
384
448
512
576
640
768
960
640
768
896
1024
1152
1280
1536
1920
1280
1536
1792
2048
2304
2560
3072
3840
2560
3072
36
40
40
28
28
36
36
44
44
52
52
36
36
52
52
68
68
84
84
36
36
68
68
100
100
132
132
68
68
132
132
196
196
260
260
132
132
260
260
388
388
516
516
260
260
44
52
64
40
48
56
64
72
80
96
120
72
88
104
120
136
152
184
232
152
184
216
248
280
312
376
472
312
376
440
504
568
632
760
952
632
760
888
1016
1144
1272
1528
1912
1272
1528
64
72
84
60
68
76
84
92
100
116
140
100
116
132
148
164
180
212
260
164
196
228
260
292
324
388
484
324
388
452
516
580
644
772
964
644
772
900
1028
1156
1284
1540
1924
1284
1540
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
551
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-7. IIC Divider and Hold Values (Sheet 6 of 6)
IBC[7:0]
(hex)
SCL Divider
(clocks)
SDA Hold
(clocks)
SCL Hold
(start)
SCL Hold
(stop)
B2
B3
B4
B5
B6
B7
B8
B9
BA
BB
BC
BD
BE
BF
3584
4096
4608
5120
6144
7680
5120
6144
7168
8192
9216
10240
12288
15360
516
516
772
772
1028
1028
516
516
1028
1028
1540
1540
2052
2052
1784
2040
2296
2552
3064
3832
2552
3064
3576
4088
4600
5112
6136
7672
1796
2052
2308
2564
3076
3844
2564
3076
3588
4100
4612
5124
6148
7684
Note:Since the bus frequency is speeding up,the SCL Divider could be expanded by it.Therefore,in the
table,when IBC[7:0] is from $00 to $0F,the SCL Divider is revised by the format value1/value2.Value1 is
the divider under the low frequency.Value2 is the divider under the high frequency.How to select the
divider depends on the bus frequency.When IBC[7:0] is from $10 to $BF,the divider is not changed.
14.3.1.3
IIC Control Register (IBCR)
Module Base + 0x0002
7
6
5
4
3
IBEN
IBIE
MS/SL
Tx/Rx
TXAK
R
1
0
0
0
IBSWAI
RSTA
W
Reset
2
0
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 14-6. IIC Bus Control Register (IBCR)
Read and write anytime
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
552
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-8. IBCR Field Descriptions
Field
Description
7
IBEN
I-Bus Enable — This bit controls the software reset of the entire IIC bus module.
0 The module is reset and disabled. This is the power-on reset situation. When low the interface is held in reset
but registers can be accessed
1 The IIC bus module is enabled.This bit must be set before any other IBCR bits have any effect
If the IIC bus module is enabled in the middle of a byte transfer the interface behaves as follows: slave mode
ignores the current transfer on the bus and starts operating whenever a subsequent start condition is detected.
Master mode will not be aware that the bus is busy, hence if a start cycle is initiated then the current bus cycle
may become corrupt. This would ultimately result in either the current bus master or the IIC bus module losing
arbitration, after which bus operation would return to normal.
6
IBIE
I-Bus Interrupt Enable
0 Interrupts from the IIC bus module are disabled. Note that this does not clear any currently pending interrupt
condition
1 Interrupts from the IIC bus module are enabled. An IIC bus interrupt occurs provided the IBIF bit in the status
register is also set.
5
MS/SL
Master/Slave Mode Select Bit — Upon reset, this bit is cleared. When this bit is changed from 0 to 1, a START
signal is generated on the bus, and the master mode is selected. When this bit is changed from 1 to 0, a STOP
signal is generated and the operation mode changes from master to slave.A STOP signal should only be
generated if the IBIF flag is set. MS/SL is cleared without generating a STOP signal when the master loses
arbitration.
0 Slave Mode
1 Master Mode
4
Tx/Rx
Transmit/Receive Mode Select Bit — This bit selects the direction of master and slave transfers. When
addressed as a slave this bit should be set by software according to the SRW bit in the status register. In master
mode this bit should be set according to the type of transfer required. Therefore, for address cycles, this bit will
always be high.
0 Receive
1 Transmit
3
TXAK
Transmit Acknowledge Enable — This bit specifies the value driven onto SDA during data acknowledge cycles
for both master and slave receivers. The IIC module will always acknowledge address matches, provided it is
enabled, regardless of the value of TXAK. Note that values written to this bit are only used when the IIC bus is a
receiver, not a transmitter.
0 An acknowledge signal will be sent out to the bus at the 9th clock bit after receiving one byte data
1 No acknowledge signal response is sent (i.e., acknowledge bit = 1)
2
RSTA
Repeat Start — Writing a 1 to this bit will generate a repeated START condition on the bus, provided it is the
current bus master. This bit will always be read as a low. Attempting a repeated start at the wrong time, if the bus
is owned by another master, will result in loss of arbitration.
1 Generate repeat start cycle
1
Reserved — Bit 1 of the IBCR is reserved for future compatibility. This bit will always read 0.
RESERVED
0
IBSWAI
I Bus Interface Stop in Wait Mode
0 IIC bus module clock operates normally
1 Halt IIC bus module clock generation in wait mode
Wait mode is entered via execution of a CPU WAI instruction. In the event that the IBSWAI bit is set, all
clocks internal to the IIC will be stopped and any transmission currently in progress will halt.If the CPU
were woken up by a source other than the IIC module, then clocks would restart and the IIC would resume
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
553
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
from where was during the previous transmission. It is not possible for the IIC to wake up the CPU when
its internal clocks are stopped.
If it were the case that the IBSWAI bit was cleared when the WAI instruction was executed, the IIC internal
clocks and interface would remain alive, continuing the operation which was currently underway. It is also
possible to configure the IIC such that it will wake up the CPU via an interrupt at the conclusion of the
current operation. See the discussion on the IBIF and IBIE bits in the IBSR and IBCR, respectively.
14.3.1.4
IIC Status Register (IBSR)
Module Base + 0x0003
R
7
6
5
TCF
IAAS
IBB
4
3
2
0
SRW
IBAL
1
0
RXAK
IBIF
W
Reset
1
0
0
0
0
0
0
0
= Unimplemented or Reserved
Figure 14-7. IIC Bus Status Register (IBSR)
This status register is read-only with exception of bit 1 (IBIF) and bit 4 (IBAL), which are software
clearable.
Table 14-9. IBSR Field Descriptions
Field
Description
7
TCF
Data Transferring Bit — While one byte of data is being transferred, this bit is cleared. It is set by the falling
edge of the 9th clock of a byte transfer. Note that this bit is only valid during or immediately following a transfer
to the IIC module or from the IIC module.
0 Transfer in progress
1 Transfer complete
6
IAAS
Addressed as a Slave Bit — When its own specific address (I-bus address register) is matched with the calling
address or it receives the general call address with GCEN== 1,this bit is set.The CPU is interrupted provided the
IBIE is set.Then the CPU needs to check the SRW bit and set its Tx/Rx mode accordingly.Writing to the I-bus
control register clears this bit.
0 Not addressed
1 Addressed as a slave
5
IBB
Bus Busy Bit
0 This bit indicates the status of the bus. When a START signal is detected, the IBB is set. If a STOP signal is
detected, IBB is cleared and the bus enters idle state.
1 Bus is busy
4
IBAL
Arbitration Lost — The arbitration lost bit (IBAL) is set by hardware when the arbitration procedure is lost.
Arbitration is lost in the following circumstances:
1. SDA sampled low when the master drives a high during an address or data transmit cycle.
2. SDA sampled low when the master drives a high during the acknowledge bit of a data receive cycle.
3. A start cycle is attempted when the bus is busy.
4. A repeated start cycle is requested in slave mode.
5. A stop condition is detected when the master did not request it.
This bit must be cleared by software, by writing a one to it. A write of 0 has no effect on this bit.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
554
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
Table 14-9. IBSR Field Descriptions (continued)
Field
Description
3
Reserved — Bit 3 of IBSR is reserved for future use. A read operation on this bit will return 0.
RESERVED
2
SRW
Slave Read/Write — When IAAS is set this bit indicates the value of the R/W command bit of the calling address
sent from the master
This bit is only valid when the I-bus is in slave mode, a complete address transfer has occurred with an address
match and no other transfers have been initiated.
Checking this bit, the CPU can select slave transmit/receive mode according to the command of the master.
0 Slave receive, master writing to slave
1 Slave transmit, master reading from slave
1
IBIF
I-Bus Interrupt — The IBIF bit is set when one of the following conditions occurs:
— Arbitration lost (IBAL bit set)
— Data transfer complete (TCF bit set)
— Addressed as slave (IAAS bit set)
It will cause a processor interrupt request if the IBIE bit is set. This bit must be cleared by software, writing a one
to it. A write of 0 has no effect on this bit.
0
RXAK
Received Acknowledge — The value of SDA during the acknowledge bit of a bus cycle. If the received
acknowledge bit (RXAK) is low, it indicates an acknowledge signal has been received after the completion of 8
bits data transmission on the bus. If RXAK is high, it means no acknowledge signal is detected at the 9th clock.
0 Acknowledge received
1 No acknowledge received
14.3.1.5
IIC Data I/O Register (IBDR)
Module Base + 0x0004
7
6
5
4
3
2
1
0
D7
D6
D5
D4
D3
D2
D1
D0
0
0
0
0
0
0
0
0
R
W
Reset
Figure 14-8. IIC Bus Data I/O Register (IBDR)
In master transmit mode, when data is written to the IBDR a data transfer is initiated. The most significant
bit is sent first. In master receive mode, reading this register initiates next byte data receiving. In slave
mode, the same functions are available after an address match has occurred.Note that the Tx/Rx bit in the
IBCR must correctly reflect the desired direction of transfer in master and slave modes for the transmission
to begin. For instance, if the IIC is configured for master transmit but a master receive is desired, then
reading the IBDR will not initiate the receive.
Reading the IBDR will return the last byte received while the IIC is configured in either master receive or
slave receive modes. The IBDR does not reflect every byte that is transmitted on the IIC bus, nor can
software verify that a byte has been written to the IBDR correctly by reading it back.
In master transmit mode, the first byte of data written to IBDR following assertion of MS/SL is used for
the address transfer and should com.prise of the calling address (in position D7:D1) concatenated with the
required R/W bit (in position D0).
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
555
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
14.3.1.6
IIC Control Register 2(IBCR2)
Module Base + 0x0005
7
6
GCEN
ADTYPE
0
0
R
5
4
3
0
0
0
2
1
0
ADR10
ADR9
ADR8
0
0
0
W
Reset
0
0
0
Figure 14-9. IIC Bus Control Register 2(IBCR2)
This register contains the variables used in general call and in ten-bit address.
Read and write anytime
Table 14-10. IBCR2 Field Descriptions
Field
Description
General Call Enable.
0 General call is disabled. The module dont receive any general call data and address.
1 enable general call. It indicates that the module can receive address and any data.
7
GCEN
6
ADTYPE
Address Type— This bit selects the address length. The variable must be configured correctly before IIC enters
slave mode.
0 7-bit address
1 10-bit address
5,4,3
Reserved — Bit 5,4 and 3 of the IBCR2 are reserved for future compatibility. These bits will always read 0.
RESERVED
2:0
ADR[10:8]
14.4
Slave Address [10:8] —These 3 bits represent the MSB of the 10-bit address when address type is asserted
(ADTYPE = 1).
Functional Description
This section provides a complete functional description of the IICV3.
14.4.1
I-Bus Protocol
The IIC bus system uses a serial data line (SDA) and a serial clock line (SCL) for data transfer. All devices
connected to it must have open drain or open collector outputs. Logic AND function is exercised on both
lines with external pull-up resistors. The value of these resistors is system dependent.
Normally, a standard communication is composed of four parts: START signal, slave address transmission,
data transfer and STOP signal. They are described briefly in the following sections and illustrated in
Figure 14-10.
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
556
Freescale Semiconductor
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
MSB
CL
1
DA
LSB
2
3
4
5
6
7
8
MSB
9
ADR7 ADR6 ADR5 ADR4ADR3 ADR2 ADR1R/W
Calling Address
Start
Signal
Read/
Write
MSB
CL
1
DA
XXX
3
4
5
6
7
8
Calling Address
Read/
Write
3
4
5
6
7
8
D7
D6
D5
D4
D3
D2
D1
D0
Data Byte
1
XX
Ack
Bit
9
No
Ack
Bit
MSB
9
ADR7 ADR6 ADR5 ADR4 ADR3 ADR2 ADR1R/W
Start
Signal
2
Ack
Bit
LSB
2
LSB
1
LSB
2
3
4
5
6
7
8
9
ADR7 ADR6 ADR5 ADR4 ADR3 ADR2 ADR1R/W
Repeated
Start
Signal
New Calling Address
Read/
Write
No
Ack
Bit
Figure 14-10. IIC-Bus Transmission Signals
14.4.1.1
START Signal
When the bus is free, i.e. no master device is engaging the bus (both SCL and SDA lines are at logical
high), a master may initiate communication by sending a START signal.As shown in Figure 14-10, a
START signal is defined as a high-to-low transition of SDA while SCL is high. This signal denotes the
beginning of a new data transfer (each data transfer may contain several bytes of data) and brings all slaves
out of their idle states.
SDA
SCL
START Condition
STOP Condition
Figure 14-11. Start and Stop Conditions
S12ZVHY/S12ZVHL Family Reference Manual Rev. 1.02
Freescale Semiconductor
557
Chapter 14 Inter-Integrated Circuit (IICV3) Block Description
14.4.1.2
Slave Address Transmission
The first byte of data transfer immediately after the START signal is the slave address transmitted by the
master. This is a seven-bit calling address followed by a R/W bit. The R/W bit tells the slave the desired
direction of data transfer.
1 = Read transfer, the slave transmits data to the master.
0 = Write transfer, the master transmits data to the slave.
If the calling address is 10-bit, another byte is followed by the first byte.Only the slave with a calling
address that matches the one transmitted by the master will respond by sending back an acknowledge bit.
This is done by pulling the SDA low at the 9th clock (see Figure 14-10).
No two slaves in the system may have the same address. If the IIC bus is master, it must not transmit an
address that is equal to its own slave address. The IIC bus cannot be master and slave at the same
time.However, if arbitration is lost during an address cycle the IIC bus will revert to slave mode and operate
correctly even if it is being addressed by another master.
14.4.1.3
Data Transfer
As soon as successful slave addressing is achieved, the data transfer can proceed byte-by-byte in a
direction specified by the R/W bit sent by the calling master
All transfers that come after an address cycle are referred to as data transfers, even if they carry sub-address
information for t