XC912DG128AMPV [MOTOROLA]
Microcontroller, 16-Bit, FLASH, 8MHz, CMOS, PQFP112, TQFP-112;
| 型号： | XC912DG128AMPV |
| 厂家： | 
MOTOROLA |
| 描述： | Microcontroller, 16-Bit, FLASH, 8MHz, CMOS, PQFP112, TQFP-112 时钟 微控制器 外围集成电路 |
| 文件： | 总404页 (文件大小：2089K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
MC68HC912DT128A/ D
MC68HC912DT128A
MC68HC912DG128A
Te c hnic a l Da ta
Re v 2.0
June 12, 2001
Re vision History
Re vision History
This section lists the revision history of the document since the first
release. Data for previous internal drafts is unavailable.
Cha ng e s from Re v 1.0 to Re v 2.0
Section
Page (in Rev 2.0)
Description of change
28, 29
31
Figures 4 and 5, pin 97 changed to TEST and note added.
Text added about connection of power supplies.
Note about non-standard oscillator circuit expanded.
33
Pinout and Signal
Descriptions
DC bias capacitor added to Figure 8 and notes added to cover DC
bias.
33
Text added in Table 6 and Port CAN pin descriptions about
non-connection of TxCAN pins when MSCAN modules are not
used.
39, 45
Registers
EEPROM
53, 58
102
CD bit name corrected in ATD0CTL5 and ATD1CTL5.
New section added ‘EEPROM Selective Write More Zeros’
Major rewrite of Limp-Home and Fast STOP Recovery modes.
System Clock Frequency Formulae updated for clarification.
Figure 18 modified for clarification.
141 to 158
159
Clock Functions
160
163
Figure 21 modified for clarification.
Enhanced Capture
Timer
192
Figure 28 modified for clarification.
321
Shading removed from CC bit in Table 54.
CD bit name corrected.
Analog-To-Digital
Converter
320, 321
MC68HC912DT128A Rev 2.0
MOTOROLA
Revision History
3
Re vision History
Section
Page (in Rev 2.0)
Description of change
Preliminary notes removed.
351, 352
EEPROM Programming Maximum Time to ‘AUTO’ Bit Set and
EEPROM Erasing Maximum Time to ‘AUTO’ Bit Set added to
Table 73.
359
Electrical
Characteristics
367
359
Several values in Table 78 updated.
Changed note after Table 73 and Table 74 to read ‘Based on the
average life time operating temperature of 70°C.’
New section added ‘2d. EEPROM Selective Write More Zeros’.
New section added ‘6. Port ADx’.
New section added ‘7. ATD’.
Appendix A:
MC68HC912DT128A
375
378
Appendix B: CGM
Practical Aspects
New section added ‘DC Bias’.
Cha ng e s from first ve rsion (inte rna l re le a se , no re vision num b e r) to Re v 1.0
Section
Page (in Rev 1.0)
Description of change
Ordering Information updated.
General Description
21
Addition of Caution regarding attempts to erase or program
protected locations.
EEPROM
MSI
109
236
Clarification of SP0DR register state on reset.
MC68HC912DT128A Rev 2.0
4
Revision History
MOTOROLA
List of Se c tions
List of Se c tions
Re vision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
List of Se c tions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Ta b le of Conte nts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Ge ne ra l De sc rip tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Ce ntra l Proc e ssing Unit . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Pinout a nd Sig na l De sc rip tions . . . . . . . . . . . . . . . . . . . . 27
Re g iste rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Op e ra ting Mod e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Re sourc e Ma p p ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Bus Control a nd Inp ut/ Outp ut . . . . . . . . . . . . . . . . . . . . 83
Fla sh EEPROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
EEPROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Re se ts a nd Inte rrup ts . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
I/ O Ports With Ke y Wa ke -Up . . . . . . . . . . . . . . . . . . . . . 127
Cloc k Func tions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
© Motorola, Inc., 2000
MOTOROLA
MC68HC912DT128A Rev 2.0
List of Sections
5
List of Se c tions
Pulse -Wid th Mod ula tor . . . . . . . . . . . . . . . . . . . . . . . . . 171
Enha nc e d Ca p ture Tim e r . . . . . . . . . . . . . . . . . . . . . . . 187
Multip le Se ria l Inte rfa c e . . . . . . . . . . . . . . . . . . . . . . . . 223
Inte r-IC Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
MSCAN Controlle r . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Ana log -To-Dig ita l Conve rte r (ATD) . . . . . . . . . . . . . . . 311
De ve lop m e nt Sup p ort. . . . . . . . . . . . . . . . . . . . . . . . . . 327
Ele c tric a l Cha ra c te ristic s . . . . . . . . . . . . . . . . . . . . . . . 351
Ap p e nd ix A: MC68HC912DT128A . . . . . . . . . . . . . . . . 373
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts . . . . . . . . . . . . . 377
Glossa ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Lite ra ture Up d a te s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
MC68HC912DT128A Rev 2.0
6
List of Sections
MOTOROLA
Ta b le of Conte nts
Ta b le of Conte nts
Revision History
Changes from Rev 1.0 to Rev 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Changes from first version to Rev 1.0 . . . . . . . . . . . . . . . . . . . . . . . . .4
List of Sections
Table of Contents
General Description
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
MC68HC912DT128A Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . .17
MC68HC912DG128A Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . .18
Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Central Processing
Unit
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Programming Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Addressing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Indexed Addressing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Opcodes and Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Pinout and Signal
Descriptions
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
MC68HC912DT128A Pin Assignments in 112-pin QFP . . . . . . . . . . .27
Power Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Port Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Registers
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Register Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
MC68HC912DT128A Rev 2.0
MOTOROLA
Table of Contents
7
Ta b le of Conte nts
Operating Modes
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Background Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Resource Mapping
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Internal Resource Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Flash EEPROM mapping through internal Memory Expansion . . . . .72
Miscellaneous System Control Register . . . . . . . . . . . . . . . . . . . . . . .77
Mapping test registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Memory Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Bus Control and
Input/Output
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Detecting Access Type from External Signals . . . . . . . . . . . . . . . . . .83
Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Flash EEPROM
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Flash EEPROM Control Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Flash EEPROM Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Flash EEPROM Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Programming the Flash EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Erasing the Flash EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Stop or Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
EEPROM
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
EEPROM Selective Write More Zeros . . . . . . . . . . . . . . . . . . . . . . .102
EEPROM Programmer’s Model . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
EEPROM Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Program/Erase Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Shadow Word Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Programming EEDIVH and EEDIVL Registers . . . . . . . . . . . . . . . . .112
MC68HC912DT128A Rev 2.0
8
Table of Contents
MOTOROLA
Table of Contents
Resets and
Interrupts
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Exception Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Maskable interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Latching of Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Interrupt Control and Priority Registers . . . . . . . . . . . . . . . . . . . . . . 119
Interrupt test registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Effects of Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Register Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
I/O Ports With Key
Wake-Up
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Key Wake-up and port Registers . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Key Wake-Up Input Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Clock Functions
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Clock Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Phase-Locked Loop (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Acquisition and Tracking Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Limp-Home and Fast STOP Recovery modes . . . . . . . . . . . . . . . . 141
System Clock Frequency Formulae . . . . . . . . . . . . . . . . . . . . . . . . 159
Clock Divider Chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Computer Operating Properly (COP) . . . . . . . . . . . . . . . . . . . . . . . 163
Real-Time Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Clock Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Clock Function Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Pulse-Width
Modulator
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
PWM Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
PWM Boundary Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
MC68HC912DT128A Rev 2.0
MOTOROLA
Table of Contents
9
Ta b le of Conte nts
Enhanced Capture
Timer
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Enhanced Capture Timer Modes of Operation . . . . . . . . . . . . . . . . .194
Timer Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
Timer and Modulus Counter Operation in Different Modes . . . . . . .221
Multiple Serial
Interface
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
Serial Communication Interface (SCI) . . . . . . . . . . . . . . . . . . . . . . .224
Serial Peripheral Interface (SPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . .235
Port S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
Inter-IC Bus
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
IIC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
IIC System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
IIC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
IIC Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
IIC Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263
MSCAN Controller
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269
External Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271
Identifier Acceptance Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279
Protocol Violation Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
Low Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Timer Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285
Clock System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Programmer’s Model of Message Storage . . . . . . . . . . . . . . . . . . . .289
Programmer’s Model of Control Registers . . . . . . . . . . . . . . . . . . . .294
MC68HC912DT128A Rev 2.0
10
Table of Contents
MOTOROLA
Table of Contents
Analog-To-Digital
Converter (ATD)
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
ATD Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
ATD Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Development
Support
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Instruction Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Background Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Instruction Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Electrical
Characteristics
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Tables of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Appendix A:
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
MC68HC912DT128
A
Significant changes from the MC68HC912DG128 (non-A suffix device)
373
Appendix B: CGM
Practical Aspects
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
A Few Hints For The CGM Crystal Oscillator Application . . . . . . . . 377
Practical Aspects For The PLL Usage . . . . . . . . . . . . . . . . . . . . . . 380
Printed Circuit Board Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Glossary
Literature Updates
Literature Distribution Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Customer Focus Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Microcontroller Division’s Web Site . . . . . . . . . . . . . . . . . . . . . . . . . 402
MC68HC912DT128A Rev 2.0
MOTOROLA
Table of Contents
11
Ta b le of Conte nts
MC68HC912DT128A Rev 2.0
12
Table of Contents
MOTOROLA
Ge ne ra l De sc rip tion
Ge ne ra l De sc rip tion
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
MC68HC912DT128A Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 17
Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Introd uc tion
The MC68HC912DT128A microcontroller unit (MCU) is a 16-bit device
composed of standard on-chip peripherals including a 16-bit central
processing unit (CPU12), 128K bytes of flash EEPROM, 8K bytes of
RAM, 2K bytes of EEPROM, two asynchronous serial communications
interfaces (SCI), a serial peripheral interface (SPI), an inter-IC interface
(I2C), an enhanced capture timer (ECT), two 8-channel, 10-bit
analog-to-digital converters (ADC), a four-channel pulse-width
modulator (PWM), and three CAN 2.0 A, B software compatible modules
(MSCAN12). System resource mapping, clock generation, interrupt
control and bus interfacing are managed by the lite integration module
(LIM). The MC68HC912DT128A has full 16-bit data paths throughout,
however, the external bus can operate in an 8-bit narrow mode so single
8-bit wide memory can be interfaced for lower cost systems. The
inclusion of a PLL circuit allows power consumption and performance to
be adjusted to suit operational requirements. In addition to the I/O ports
available in each module, 16 I/O ports are available with Key-Wake-Up
capability from STOP or WAIT mode.
The MC68HC912DG128A device is similar to the MC68HC912DT128A,
but it has only two MSCAN12 modules. The entire databook applies also
to the MC68HC912DG128A, except where differences are noted.
1-gen
MC68HC912DT128A Rev 2.0
MOTOROLA
General Description
13
Ge ne ra l De sc rip tion
Fe a ture s
•
16-bit CPU12
– Upward compatible with M68HC11 instruction set
– Interrupt stacking and programmer’s model identical to
M68HC11
– 20-bit ALU
– Instruction queue
– Enhanced indexed addressing
Multiplexed bus
•
•
– Single chip or expanded
– 16 address/16 data wide or 16 address/8 data narrow modes
Memory
– 128K byte flash EEPROM, made of four 32K byte modules
with 8K bytes protected BOOT section in each module
– 2K byte EEPROM
– 8K byte RAM with Vstby, made of two 4K byte modules.
Two Analog-to-digital converters
•
•
– 2 times 8-channels, 10-bit resolution
Three 1M bit per second, CAN 2.0 A, B software compatible
modules on the MC68HC912DT128A (two on the
MC68HC912DG128A)
– Two receive and three transmit buffers per CAN
– Flexible identifier filter programmable as 2 x 32 bit, 4 x 16 bit or
8 x 8 bit
– Four separate interrupt channels for Rx, Tx, error and wake-up
per CAN
– Low-pass filter wake-up function
– Loop-back for self test operation
2--gen
MC68HC912DT128A Rev 2.0
14
General Description
MOTOROLA
General Description
Features
– Programmable link to a timer input capture channel, for
time-stamping and network synchronization.
•
Enhanced capture timer (ECT)
– 16-bit main counter with 7-bit prescaler
– 8 programmable input capture or output compare channels; 4
of the 8 input captures with buffer
– Input capture filters and buffers, three successive captures on
four channels, or two captures on four channels with a
capture/compare selectable on the remaining four
– Four 8-bit or two 16-bit pulse accumulators
– 16-bit modulus down-counter with 4-bit prescaler
– Four user-selectable delay counters for signal filtering
4 PWM channels with programmable period and duty cycle
– 8-bit 4-channel or 16-bit 2-channel
•
– Separate control for each pulse width and duty cycle
– Center- or left-aligned outputs
– Programmable clock select logic with a wide range of
frequencies
•
•
Serial interfaces
– Two asynchronous serial communications interfaces (SCI)
– Inter IC bus interface (I2C)
– Synchronous serial peripheral interface (SPI)
LIM (lite integration module)
– WCR (windowed COP watchdog, real time interrupt, clock
monitor)
– ROC (reset and clocks)
– MEBI (multiplexed external bus interface)
– MMI (memory map and interface)
– INT (interrupt control)
3-gen
MC68HC912DT128A Rev 2.0
MOTOROLA
General Description
15
Ge ne ra l De sc rip tion
– BKP (breakpoints)
– BDM (background debug mode)
Two 8-bit ports with key wake-up interrupt
Clock generation
•
•
– Phase-locked loop clock frequency multiplier
– Limp home mode in absence of external clock
– Slow mode divider
– Low power 0.5 to 16 MHz crystal oscillator reference clock
112-Pin TQFP package
•
•
– Up to 67 general-purpose I/O lines on the
MC68HC912DT128A (up to 69 on the MC68HC912DG128A),
plus up to 18 input-only lines
– 5.0V operation at 8 MHz
Development support
– Single-wire background debug™ mode (BDM)
– On-chip hardware breakpoints
4-gen
MC68HC912DT128A Rev 2.0
16
General Description
MOTOROLA
General Description
MC68HC912DT128A Block Diagram
MC68HC912DT128A Bloc k Dia g ra m
VRH0
VRL0
VDDA
VSSA
VRH0
VRL0
VRH1
VRL1
VDDA
VSSA
VRH1
VRL1
VDDA
VSSA
ATD0
ATD1
128K byte flash EEPROM
VSTBY
8K byte RAM
AN00
AN01
AN02
AN03
AN04
AN05
AN06
AN07
PAD00
AN10
AN11
AN12
AN13
AN14
AN15
AN16
AN17
PAD10
PAD11
PAD12
PAD13
PAD14
PAD15
PAD16
PAD17
PAD01
PAD02
PAD03
PAD04
PAD05
PAD06
PAD07
2K byte EEPROM
CPU12
Periodic interrupt
Single-wire
IOC0
PT0
PT1
PT2
PT3
PT4
PT5
PT6
PT7
COP watchdog
background
debug module
BKGD
IOC1
IOC2
IOC3
IOC4
IOC5
IOC6
IOC7
Clock monitor
Breakpoints
Enhanced
capture
timer
XFC
VDDPLL
VSSPLL
Clock
Generation
module
PLL
RxD0
TxD0
RxD1
TxD1
PS0
PS1
PS2
PS3
SCI0
SCI1
EXTAL
XTAL
RESET
SDI/MISO
SDO/MOSI
SCK
PS4
PS5
PS6
PS7
SPI
SS
PE0
PE1
PE2
PE3
PE4
PE5
XIRQ
IRQ
R/W
LSTRB
ECLK
MODA
MODB
DBE/CAL
Lite
integration
module
(LIM)
PW0
PW1
PW2
PW3
PP0
PP1
PP2
PP3
PWM
PE6
PE7
PIX0
PK0
PK1
PK2
PK3
PK7
PPAGE
PIX1
PIX2
I/O
ECS
SCL
SDA
PIB7
PIB6
IIC
Multiplexed Address/Data Bus
TxCAN2
RxCAN2
TxCAN1
RxCAN1
TxCAN0
RxCAN0
CAN2
CAN1
CAN0
DDRA
DDRB
PORT A
PORT B
KWH7
KWH6
KWH5
KWH4
KWH3
KWH2
KWH1
KWH0
PH7
PH6
PH5
PH4
PH3
PH2
PH1
PH0
VDD ×2
VSS ×2
Power for internal circuitry
Wide
bus
KWU
KWJ7
KWJ6
KWJ5
KWJ4
KWJ3
KWJ2
KWJ1
KWJ0
PJ7
PJ6
PJ5
PJ4
PJ3
PJ2
PJ1
PJ0
VDDX ×2
VSSX ×2
Narrow bus
Power for I/O drivers
Figure 1 MC68HC912DT128A Block Diagram
5-gen
MC68HC912DT128A Rev 2.0
17
MOTOROLA
General Description
Ge ne ra l De sc rip tion
MC68HC912DG128A Bloc k Dia g ra m
VRH0
VRL0
VDDA
VSSA
VRH0
VRL0
VRH1
VRL1
VDDA
VSSA
VRH1
VRL1
VDDA
VSSA
ATD0
ATD1
128K byte flash EEPROM
VSTBY
8K byte RAM
AN00
AN01
AN02
AN03
AN04
AN05
AN06
AN07
PAD00
AN10
AN11
AN12
AN13
AN14
AN15
AN16
AN17
PAD10
PAD11
PAD12
PAD13
PAD14
PAD15
PAD16
PAD17
PAD01
PAD02
PAD03
PAD04
PAD05
PAD06
PAD07
2K byte EEPROM
CPU12
Periodic interrupt
Single-wire
background
debug module
IOC0
PT0
PT1
PT2
PT3
PT4
PT5
PT6
PT7
COP watchdog
Clock monitor
Breakpoints
BKGD
IOC1
IOC2
IOC3
IOC4
IOC5
IOC6
IOC7
Enhanced
capture
timer
XFC
VDDPLL
VSSPLL
Clock
Generation
module
PLL
RxD0
TxD0
RxD1
TxD1
PS0
PS1
PS2
PS3
SCI0
SCI1
EXTAL
XTAL
RESET
SDI/MISO
SDO/MOSI
SCK
PS4
PS5
PS6
PS7
SPI
SS
PE0
PE1
PE2
PE3
PE4
PE5
XIRQ
IRQ
R/W
LSTRB
ECLK
MODA
MODB
DBE/CAL
Lite
integration
module
(LIM)
PW0
PW1
PW2
PW3
PP0
PP1
PP2
PP3
PWM
PE6
PE7
PIX0
PK0
PK1
PK2
PK3
PK7
PPAGE
PIX1
PIX2
I/O
ECS
SCL
SDA
PIB7
PIB6
PIB5
PIB4
IIC
Multiplexed Address/Data Bus
I/O
TxCAN0
RxCAN0
CAN0
CAN1
DDRA
DDRB
TxCAN1
RxCAN1
PORT A
PORT B
KWH7
KWH6
KWH5
KWH4
KWH3
KWH2
KWH1
KWH0
PH7
PH6
PH5
PH4
PH3
PH2
PH1
PH0
VDD ×2
VSS ×2
Power for internal circuitry
Wide
bus
KWU
KWJ7
KWJ6
KWJ5
KWJ4
KWJ3
KWJ2
KWJ1
KWJ0
PJ7
PJ6
PJ5
PJ4
PJ3
PJ2
PJ1
PJ0
VDDX ×2
VSSX ×2
Narrow bus
Power for I/O drivers
Figure 2 MC68HC912DG128A Block Diagram
6-gen
MC68HC912DT128A Rev 2.0
18
General Description
MOTOROLA
General Description
Ordering Information
Ord e ring Inform a tion
Table 1 Device Ordering Information
Temperature
Package
Range
Voltage
Frequency
Order Number
Designator
–40 to +85°C
C
V
112-Pin TQFP
–40 to +105°C
–40 to +125°C
5V
8 MHz
Consult factory
M
Table 2 Development Tools Ordering Information
Description
Details
Order Number
Evaluation board kit
EVB and user's manual only
M68EVB912DG128
Low voltage serial debug interface cable can be
ordered separately
Serial Debug Interface
M68SDIL12
Complete evaluation
board kit
EVB, MCUez debug software, SDIL low voltage serial
debug interface cable
M68KIT912DG128
Adapter
112 pin TQFP adapter is also available.
M68ADP912DG128PV
7-gen
MC68HC912DT128A Rev 2.0
19
MOTOROLA
General Description
Ge ne ra l De sc rip tion
8-gen
MC68HC912DT128A Rev 2.0
20
General Description
MOTOROLA
Ce ntra l Proc e ssing Unit
Ce ntra l Proc e ssing Unit
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Programming Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Addressing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Indexed Addressing Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Opcodes and Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Introd uc tion
The CPU12 is a high-speed, 16-bit processing unit. It has full 16-bit data
paths and wider internal registers (up to 20 bits) for high-speed extended
math instructions. The instruction set is a proper superset of the
M68HC11instruction set. The CPU12 allows instructions with odd byte
counts, including many single-byte instructions. This provides efficient
use of ROM space. An instruction queue buffers program information so
the CPU always has immediate access to at least three bytes of machine
code at the start of every instruction. The CPU12 also offers an
extensive set of indexed addressing capabilities.
1-cpu12
MC68HC912DT128A Rev 2.0
MOTOROLA
Central Processing Unit
21
Ce ntra l Proc e ssing Unit
Prog ra m m ing Mod e l
CPU12 registers are an integral part of the CPU and are not addressed
as if they were memory locations.
A
B
7
0 7
0
0
8-BIT ACCUMULATORS A & B
OR
16-BIT DOUBLE ACCUMULATOR D
15
D
15
15
15
15
IX
IY
0
0
0
0
INDEX REGISTER X
INDEX REGISTER Y
STACK POINTER
SP
PC
PROGRAM COUNTER
CONDITION CODE REGISTER
S X H I N Z V C
Figure 3 Programming Model
Accumulators A and B are general-purpose 8-bit accumulators used to
hold operands and results of arithmetic calculations or data
manipulations. Some instructions treat the combination of these two
8-bit accumulators as a 16-bit double accumulator (accumulator D).
Index registers X and Y are used for indexed addressing mode. In the
indexed addressing mode, the contents of a 16-bit index register are
added to 5-bit, 9-bit, or 16-bit constants or the content of an accumulator
to form the effective address of the operand to be used in the instruction.
2--cpu12
MC68HC912DT128A Rev 2.0
22
Central Processing Unit
MOTOROLA
Central Processing Unit
Data Types
Stack pointer (SP) points to the last stack location used. The CPU12
supports an automatic program stack that is used to save system
context during subroutine calls and interrupts, and can also be used for
temporary storage of data. The stack pointer can also be used in all
indexed addressing modes.
Program counter is a 16-bit register that holds the address of the next
instruction to be executed. The program counter can be used in all
indexed addressing modes except autoincrement/decrement.
Condition Code Register (CCR) contains five status indicators, two
interrupt masking bits, and a STOP disable bit. The five flags are half
carry (H), negative (N), zero (Z), overflow (V), and carry/borrow (C). The
half-carry flag is used only for BCD arithmetic operations. The N, Z, V,
and C status bits allow for branching based on the results of a previous
operation.
Da ta Typ e s
The CPU12 supports the following data types:
•
•
•
•
Bit data
8-bit and 16-bit signed and unsigned integers
16-bit unsigned fractions
16-bit addresses
A byte is eight bits wide and can be accessed at any byte location. A
word is composed of two consecutive bytes with the most significant
byte at the lower value address. There are no special requirements for
alignment of instructions or operands.
3-cpu12
MC68HC912DT128A Rev 2.0
MOTOROLA
Central Processing Unit
23
Ce ntra l Proc e ssing Unit
Ad d re ssing Mod e s
Addressing modes determine how the CPU accesses memory locations
to be operated upon. The CPU12 includes all of the addressing modes
of the M68HC11 CPU as well as several new forms of indexed
addressing. Table 3 is a summary of the available addressing modes.
Table 3 M68HC12 Addressing Mode Summary
Addressing Mode
Source Format
Abbreviation
Description
INST
Inherent
(no externally supplied
operands)
INH
Operands (if any) are in CPU registers
INST #opr8i
or
INST #opr16i
Operand is included in instruction stream
8- or 16-bit size implied by context
Immediate
IMM
Operand is the lower 8-bits of an address in the
Direct
INST opr8a
DIR
range $0000 – $00FF
Extended
INST opr16a
EXT
Operand is a 16-bit address
INST rel8
or
INST rel16
An 8-bit or 16-bit relative offset from the current
pc is supplied in the instruction
Relative
REL
Indexed
(5-bit offset)
INST oprx5,xysp
INST oprx3,–xys
INST oprx3,+xys
IDX
IDX
IDX
5-bit signed constant offset from x, y, sp, or pc
Auto pre-decrement x, y, or sp by 1 ~ 8
Auto pre-increment x, y, or sp by 1 ~ 8
Indexed
(auto pre-decrement)
Indexed
(auto pre-increment)
Indexed
(auto post-
decrement)
INST oprx3,xys–
INST oprx3,xys+
IDX
IDX
Auto post-decrement x, y, or sp by 1 ~ 8
Auto post-increment x, y, or sp by 1 ~ 8
Indexed
(auto
post-increment)
Indexed
(accumulator offset)
Indexed with 8-bit (A or B) or 16-bit (D)
accumulator offset from x, y, sp, or pc
INST abd,xysp
INST oprx9,xysp
INST oprx16,xysp
IDX
IDX1
IDX2
Indexed
(9-bit offset)
9-bit signed constant offset from x, y, sp, or pc
(lower 8-bits of offset in one extension byte)
Indexed
(16-bit offset)
16-bit constant offset from x, y, sp, or pc
(16-bit offset in two extension bytes)
Pointer to operand is found at...
16-bit constant offset from x, y, sp, or pc
(16-bit offset in two extension bytes)
Indexed-Indirect
(16-bit offset)
INST [oprx16,xysp]
INST [D,xysp]
[IDX2]
Indexed-Indirect
(D accumulator
offset)
Pointer to operand is found at...
x, y, sp, or pc plus the value in D
[D,IDX]
4-cpu12
MC68HC912DT128A Rev 2.0
24
Central Processing Unit
MOTOROLA
Central Processing Unit
Indexed Addressing Modes
Ind e xe d Ad d re ssing Mod e s
The CPU12 indexed modes reduce execution time and eliminate code
size penalties for using the Y index register. CPU12 indexed addressing
uses a postbyte plus zero, one, or two extension bytes after the
instruction opcode. The postbyte and extensions do the following tasks:
•
•
•
•
Specify which index register is used.
Determine whether a value in an accumulator is used as an offset.
Enable automatic pre- or post-increment or decrement
Specify use of 5-bit, 9-bit, or 16-bit signed offsets.
Table 4 Summary of Indexed Operations
Postbyte
Code (xb)
Source Code
Syntax
Comments
,r
n,r
–n,r
5-bit constant offset n = –16 to +15
rr can specify X, Y, SP, or PC
rr0nnnnn
Constant offset (9- or 16-bit signed)
z-0 = 9-bit with sign in LSB of postbyte(s)
1 = 16-bit
if z = s = 1, 16-bit offset indexed-indirect (see below)
rr can specify X, Y, SP, or PC
n,r
–n,r
111rr0zs
16-bit offset indexed-indirect
rr can specify X, Y, SP, or PC
111rr011
rr1pnnnn
[n,r]
Auto pre-decrement/increment or Auto post-decrement/increment;
p = pre-(0) or post-(1), n = –8 to –1, +1 to +8
rr can specify X, Y, or SP (PC not a valid choice)
n,–r n,+r
n,r– n,r+
Accumulator offset (unsigned 8-bit or 16-bit)
aa-00 = A
01 = B
10 = D (16-bit)
11 = see accumulator D offset indexed-indirect
rr can specify X, Y, SP, or PC
A,r
B,r
D,r
111rr1aa
111rr111
Accumulator D offset indexed-indirect
rr can specify X, Y, SP, or PC
[D,r]
5-cpu12
MC68HC912DT128A Rev 2.0
25
MOTOROLA
Central Processing Unit
Ce ntra l Proc e ssing Unit
Op c od e s a nd Op e ra nd s
The CPU12 uses 8-bit opcodes. Each opcode identifies a particular
instruction and associated addressing mode to the CPU. Several
opcodes are required to provide each instruction with a range of
addressing capabilities.
Only 256 opcodes would be available if the range of values were
restricted to the number that can be represented by 8-bit binary
numbers. To expand the number of opcodes, a second page is added to
the opcode map. Opcodes on the second page are preceded by an
additional byte with the value $18.
To provide additional addressing flexibility, opcodes can also be
followed by a postbyte or extension bytes. Postbytes implement certain
forms of indexed addressing, transfers, exchanges, and loop primitives.
Extension bytes contain additional program information such as
addresses, offsets, and immediate data.
6-cpu12
MC68HC912DT128A Rev 2.0
26
Central Processing Unit
MOTOROLA
Pinout a nd Sig na l De sc rip tions
Pinout a nd Sig na l De sc rip tions
Conte nts
MC68HC912DT128A Pin Assignments in 112-pin QFP . . . . . . . . . . . 27
Power Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Port Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
MC68HC912DT128A Pin Assig nm e nts in 112-p in QFP
The MC68HC912DT128A is available in a 112-pin thin quad flat pack
(TQFP). Most pins perform two or more functions, as described in the
Signal Descriptions. Figure 4 shows pin assignments. In expanded
narrow modes the lower byte data is multiplexed with higher byte data
through pins 57-64.
1-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
27
Pinout a nd Sig na l De sc rip tions
1
2
3
4
5
6
7
8
84
83
82
81
80
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
PW2/PP2
PW1/PP1
PW0/PP0
IOC0/PT0
IOC1/PT1
IOC2/PT2
IOC3/PT3
KWJ7/PJ7
KWJ6/PJ6
KWJ5/PJ5
KWJ4/PJ4
PAD17/AN17
PAD07/AN07
PAD16/AN16
PAD06/AN06
PAD15/AN15
PAD05/AN05
PAD14/AN14
PAD04/AN04
PAD13/AN13
PAD03/AN03
PAD12/AN12
PAD02/AN02
PAD11/AN11
PAD01/AN01
PAD10/AN10
PAD00/AN00
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
V
DD
PK3
MC68HC912DT128A
V
SS
112TQFP
IOC4/PT4
IOC5/PT5
IOC6/PT6
IOC7/PT7
KWJ3/PJ3
KWJ2/PJ2
KWJ1/PJ1
KWJ0/PJ0
V
RL0
V
RH0
V
SS
V
DD
PA7/ADDR15/DATA15/DATA7
PA6/ADDR14/DATA14/DATA6
PA5/ADDR13/DATA13/DATA5
PA4/ADDR12/DATA12/DATA4
PA3/ADDR11/DATA11/DATA3
PA2/ADDR10/DATA10/DATA2
PA1/ADDR9/DATA9/DATA1
PA0/ADDR8/DATA8/DATA0
SMODN/TAGHI/BKGD
ADDR0/DATA0/PB0
ADDR1/DATA1/PB1
ADDR2/DATA2/PB2
ADDR3/DATA3/PB3
ADDR4/DATA4/PB4
Note: TEST = On early production devices this pin is used for factory test purposes. It is recommended that this pin
is not connected within the application, but it may be connected to VSS or 5.5V max without issue.
On later production devices this pin is not bonded out.
Figure 4 Pin Assignments in 112-pin QFP for MC68HC912DT128A
2-pins
MC68HC912DT128A Rev 2.0
28
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
MC68HC912DT128A Pin Assignments in 112-pin QFP
1
2
3
4
5
6
7
8
84
83
82
81
80
79
78
77
76
75
74
73
PW2/PP2
PW1/PP1
PW0/PP0
IOC0/PT0
IOC1/PT1
IOC2/PT2
IOC3/PT3
KWJ7/PJ7
KWJ6/PJ6
KWJ5/PJ5
KWJ4/PJ4
PAD17/AN17
PAD07/AN07
PAD16/AN16
PAD06/AN06
PAD15/AN15
PAD05/AN05
PAD14/AN14
PAD04/AN04
PAD13/AN13
PAD03/AN03
PAD12/AN12
PAD02/AN02
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
V
DD
72
PK3
PAD11/AN11
MC68HC912DG128A
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
V
PAD01/AN01
PAD10/AN10
PAD00/AN00
SS
112TQFP
IOC4/PT4
IOC5/PT5
IOC6/PT6
IOC7/PT7
KWJ3/PJ3
KWJ2/PJ2
KWJ1/PJ1
KWJ0/PJ0
V
RL0
V
RH0
V
SS
V
DD
PA7/ADDR15/DATA15/DATA7
PA6/ADDR14/DATA14/DATA6
PA5/ADDR13/DATA13/DATA5
PA4/ADDR12/DATA12/DATA4
PA3/ADDR11/DATA11/DATA3
PA2/ADDR10/DATA10/DATA2
PA1/ADDR9/DATA9/DATA1
PA0/ADDR8/DATA8/DATA0
SMODN/TAGHI/BKGD
ADDR0/DATA0/PB0
ADDR1/DATA1/PB1
ADDR2/DATA2/PB2
ADDR3/DATA3/PB3
ADDR4/DATA4/PB4
Note: TEST = On early production devices this pin is used for factory test purposes. It is recommended that this pin
is not connected within the application, but it may be connected to VSS or 5.5V max without issue.
On later production devices this pin is not bonded out.
Figure 5 Pin Assignments in 112-pin QFP for MC68HC912DG128A
3-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
29
Pinout a nd Sig na l De sc rip tions
4X
0.20 T L-M N
4X 28 TIPS
85
0.20 T L-M N
4X
P
J1
J1
PIN 1
IDENT
112
C
1
84
L
VIEW Y
X
108X
G
X=L, M OR N
VIEW Y
V
B
L
M
AA
J
B1
V1
28
57
BASE
METAL
F
D
29
56
M
0.13
T L-M N
N
SECTION J1-J1
A1
S1
ROTATED 90 COUNTERCLOCKWISE
°
NOTES:
A
1. DIMENSIONING AND TOLERANCING PER
ASME Y14.5M, 1994.
2. DIMENSIONS IN MILLIMETERS.
3. DATUMS L, M AND N TO BE DETERMINED AT
SEATING PLANE, DATUM T.
S
4. DIMENSIONS S AND V TO BE DETERMINED AT
SEATING PLANE, DATUM T.
5. DIMENSIONS A AND B DO NOT INCLUDE
MOLD PROTRUSION. ALLOWABLE
PROTRUSION IS 0.25 PER SIDE. DIMENSIONS
A AND B INCLUDE MOLD MISMATCH.
6. DIMENSION D DOES NOT INCLUDE DAMBAR
PROTRUSION. ALLOWABLE DAMBAR
PROTRUSION SHALL NOT CAUSE THE D
DIMENSION TO EXCEED 0.46.
C2
VIEW AB
θ2
θ3
C
0.050
112X
0.10
T
SEATING
PLANE
MILLIMETERS
T
DIM MIN
MAX
20.000 BSC
10.000 BSC
A
A1
B
B1
C
20.000 BSC
10.000 BSC
---
1.600
0.150
1.450
0.370
0.750
0.330
θ
C1 0.050
C2 1.350
D
E
F
0.270
0.450
0.270
R R2
G
J
0.650 BSC
0.090
0.170
K
P
0.500 REF
0.325 BSC
0.25
R R1
R1 0.100
R2 0.100
0.200
0.200
GAGE PLANE
S
S1
V
V1
Y
22.000 BSC
11.000 BSC
22.000 BSC
11.000 BSC
0.250 REF
1.000 REF
(K)
E
C1
θ1
Z
(Y)
(Z)
AA 0.090
0.160
8 °
0 °
3 °
11 °
11 °
θ
θ1
θ2
θ 3
7 °
VIEW AB
13 °
13 °
Figure 3 112-pin QFP Mechanical Dimensions (case no. 987)
4-pins
MC68HC912DT128A Rev 2.0
30
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Power Supply Pins
Powe r Sup p ly Pins
MC68HC912DT128A power and ground pins are described below and
summarized in Table 5.
All power supply pins must be connected to appropriate supplies.
On no account must any pins be left floating.
Inte rna l Powe r
(VDD) a nd Ground
(VSS)
Power is supplied to the MCU through VDD and VSS. 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.
Exte rna l Powe r
(VDDX) a nd
External power and ground for I/O drivers. 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. Bypass requirements
depend on how heavily the MCU pins are loaded.
Ground (VSSX
)
VDDA, VSSA
Provides operating voltage and ground for the analog-to-digital
converter. This allows the supply voltage to the A/D to be bypassed
independently.
Ana log to Dig ita l
Re fe re nc e
Volta g e s (VRH, VRL)
VRH0, VRL0: reference voltage high and low for ATD converter 0.
VRH1, VRL1: reference voltage high and low for ATD converter 1.
If the ATD modules are not used, leaving VRH connected to VDD will not
result in an increase of power consumption.
VDDPLL, VSSPLL
Provides operating voltage and ground for the Phase-Locked Loop. This
allows the supply voltage to the PLL to be bypassed independently.
5-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
31
Pinout a nd Sig na l De sc rip tions
NOTE: The VSSPLL pin should always be grounded even if the PLL is not used.
The VDDPLL pin should not be left floating. It is recommended to
connect the VDDPLL pin to ground if the PLL is not used.
XFC
PLL loop filter. Please see Appendix B: CGM Practical Aspects for
information on how to calculate PLL loop filter elements. Any current
leakage on this pin must be avoided.
XFC
R0
Ca
MCU
C0
VDDPLL
VDDPLL
Figure 7 PLL Loop FIlter Connections
VSTBY
Stand-by voltage supply to static RAM. Used to maintain the contents of
RAM with minimal power when the rest of the chip is powered down.
Table 5 MC68HC912DT128A Power and Ground Connection Summary
Pin Number
Mnemonic
VDD
Description
112-pin QFP
12, 65
14, 66
42, 107
40, 106
85
Internal power and ground.
VSS
VDDX
VSSX
VDDA
VSSA
VRH1
VRL1
VRH0
VRL0
External power and ground, supply to pin drivers.
Operating voltage and ground for the analog-to-digital converter, allows the
supply voltage to the A/D to be bypassed independently.
88
86
Reference voltages for the analog-to-digital converter 1
Reference voltages for the analog-to-digital converter 0.
87
67
68
6-pins
MC68HC912DT128A Rev 2.0
32
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Signal Descriptions
Table 5 MC68HC912DT128A Power and Ground Connection Summary
Pin Number
Mnemonic
Description
112-pin QFP
VDDPLL
VSSPLL
43
45
Provides operating voltage and ground for the Phase-Locked Loop. This allows
the supply voltage to the PLL to be bypassed independently.
Stand-by voltage supply to maintain the contents of RAM with minimal power
when the rest of the chip is powered down.
VSTBY
41
Sig na l De sc rip tions
Crysta l Drive r a nd
Exte rna l Cloc k
Inp ut (XTAL, EXTAL)
These pins provide the interface for either a crystal or a CMOS
compatible clock to control the internal clock generator circuitry. Out of
reset the frequency applied to EXTAL is twice the desired E–clock rate.
All the device clocks are derived from the EXTAL input frequency.
Please see Appendix B: CGM Practical Aspects for detailed information
on oscillator design.
NOTE: THE CRYSTAL CIRCUIT FOR COLPITTS OSCILLATOR IS CHANGED
FROM THE STANDARD PIERCE OSCILLATOR.
NOTE: The internal return path for the oscillator is the VSSPLL pin. Therefore it
is recommended to connect the common node of the resonator and the
capacitor directly to the VSSPLL pin.
2 x E crystal or ceramic resonator
EXTAL
MCU
C
C
XTAL
C
*
DC
*
Due to the nature of the translated ground Colpitts oscillator a
DC voltage bias is applied to the crystal.
Please contact the crystal manufacturer for specific DC bias
conditions and recommended capacitance value (if applicable).
Figure 8 Common Crystal Connections
7-pins
MC68HC912DT128A Rev 2.0
33
MOTOROLA
Pinout and Signal Descriptions
Pinout a nd Sig na l De sc rip tions
2 x E
EXTAL
CMOS-COMPATIBLE
EXTERNAL OSCILLATOR
MCU
XTAL
NC
Figure 9 External Oscillator Connections
XTAL is the crystal output.The XTAL pin must be left without terminal
when an external CMOS compatible clock input is connected to the
EXTAL pin. The XTAL output is normally intended to drive only a crystal.
The XTAL output can be buffered with a high-impedance buffer to drive
the EXTAL input of another device.
In all cases take extra care in the circuit board layout around the
oscillator pins. Load capacitances in the oscillator circuits include all
stray layout capacitances. Refer to Figure 8 and Figure 9 for diagrams
of oscillator circuits.
E-Cloc k Outp ut
(ECLK)
ECLK is the output connection for the internal bus clock. It is used to
demultiplex the address and data in expanded modes and is used as a
timing reference. ECLK frequency is equal to 1/2 the crystal frequency
out of reset. The E-clock output is turned off in single chip user mode to
reduce the effects of RFI. It can be turned on if necessary. In special
single-chip mode, the E-clock is turned ON at reset and can be turned
OFF. In special peripheral mode the E-clock is an input to the MCU. All
clocks, including the E clock, are halted when the MCU is in STOP
mode. It is possible to configure the MCU to interface to slow external
memory. ECLK can be stretched for such accesses.
Re se t (RESET)
An active low bidirectional control signal, RESET, acts as an input to
initialize the MCU to a known start-up state. It also acts as an open-drain
output to indicate that an internal failure has been detected in either the
clock monitor or COP watchdog circuit. The MCU goes into reset
asynchronously and comes out of reset synchronously. This allows the
8-pins
MC68HC912DT128A Rev 2.0
34
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Signal Descriptions
part to reach a proper reset state even if the clocks have failed, while
allowing synchronized operation when starting out of reset.
It is important to use an external low-voltage reset circuit (such as
MC34064 or MC34164) to prevent corruption of RAM or EEPROM due
to power transitions.
The reset sequence is initiated by any of the following events:
•
•
•
Power-on-reset (POR)
COP watchdog enabled and watchdog timer times out
Clock monitor enabled and Clock monitor detects slow or stopped
clock
•
User applies a low level to the reset pin
External circuitry connected to the reset pin should not include a large
capacitance that would interfere with the ability of this signal to rise to a
valid logic one within nine bus cycles after the low drive is released.
Upon detection of any reset, an internal circuit drives the reset pin low
and a clocked reset sequence controls when the MCU can begin normal
processing. In the case of POR or a clock monitor error, a 4096 cycle
oscillator startup delay is imposed before the reset recovery sequence
starts (reset is driven low throughout this 4096 cycle delay). The internal
reset recovery sequence then drives reset low for 16 to 17 cycles and
releases the drive to allow reset to rise. Nine cycles later this circuit
samples the reset pin to see if it has risen to a logic one level. If reset is
low at this point, the reset is assumed to be coming from an external
request and the internally latched states of the COP timeout and clock
monitor failure are cleared so the normal reset vector ($FFFE:FFFF) is
taken when reset is finally released. If reset is high after this nine cycle
delay, the reset source is tentatively assumed to be either a COP failure
or a clock monitor fail. If the internally latched state of the clock monitor
fail circuit is true, processing begins by fetching the clock monitor vector
($FFFC:FFFD). If no clock monitor failure is indicated, and the latched
state of the COP timeout is true, processing begins by fetching the COP
vector ($FFFA:FFFB). If neither clock monitor fail nor COP timeout are
pending, processing begins by fetching the normal reset vector
($FFFE:FFFF).
9-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
35
Pinout a nd Sig na l De sc rip tions
Ma ska b le
Inte rrup t Re q ue st
(IRQ)
The IRQ input provides a means of applying asynchronous interrupt
requests to the MCU. Either falling edge-sensitive triggering or
level-sensitive triggering is program selectable (INTCR register). IRQ is
always enabled and configured to level-sensitive triggering at reset. It
can be disabled by clearing IRQEN bit (INTCR register). When the MCU
is reset the IRQ function is masked in the condition code register. This
pin is always an input and can always be read. There is an active pull-up
on this pin while in reset and immediately out of reset. The pullup can be
turned off by clearing PUPE in the PUCR register.
Nonm a ska b le
Inte rrup t (XIRQ)
The XIRQ input provides a means of requesting a nonmaskable interrupt
after reset initialization. During reset, the X bit in the condition code
register (CCR) is set and any interrupt is masked until MCU software
enables it. Because the XIRQ input is level sensitive, it can be connected
to a multiple-source wired-OR network. This pin is always an input and
can always be read. There is an active pull-up on this pin while in reset
and immediately out of reset. The pullup can be turned off by clearing
PUPE in the PUCR register. XIRQ is often used as a power loss detect
interrupt.
Whenever XIRQ or IRQ are used with multiple interrupt sources (IRQ
must be configured for level-sensitive operation if there is more than one
source of IRQ interrupt), each source must drive the interrupt input with
an open-drain type of driver to avoid contention between outputs. There
must also be an interlock mechanism at each interrupt source so that the
source holds the interrupt line low until the MCU recognizes and
acknowledges the interrupt request. If the interrupt line is held low, the
MCU will recognize another interrupt as soon as the interrupt mask bit in
the MCU is cleared (normally upon return from an interrupt).
Mod e Se le c t
(SMODN, MODA,
a nd MODB)
The state of these pins during reset determine the MCU operating mode.
After reset, MODA and MODB can be configured as instruction queue
tracking signals IPIPE0 and IPIPE1 in expanded modes. MODA and
MODB have active pulldowns during reset.
The SMODN pin has an active pullup when configured as an input. The
pin can be used as BKGD or TAGHI after reset.
10-pins
MC68HC912DT128A Rev 2.0
36
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Signal Descriptions
Sing le -Wire
Ba c kg round Mod e
Pin (BKGD)
The BKGD pin receives and transmits serial background debugging
commands. A special self-timing protocol is used. The BKGD pin has an
active pullup when configured as an input; BKGD has no pullup control.
Refer to Development Support.
Exte rna l Add re ss
a nd Da ta Buse s
(ADDR[15:0] a nd
DATA[15:0])
External bus pins share functions with general-purpose I/O ports A and
B. In single-chip operating modes, the pins can be used for I/O; in
expanded modes, the pins are used for the external buses.
In expanded wide mode, ports A and B are used for multiplexed 16-bit
data and address buses. PA[7:0] correspond to
ADDR[15:8]/DATA[15:8]; PB[7:0] correspond to ADDR[7:0]/DATA[7:0].
In expanded narrow mode, ports A and B are used for the16-bit address
bus, and an 8-bit data bus is multiplexed with the most significant half of
the address bus on port A. In this mode, 16-bit data is handled as two
back-to-back bus cycles, one for the high byte followed by one for the
low byte. PA[7:0] correspond to ADDR[15:8] and to DATA[15:8] or
DATA[7:0], depending on the bus cycle. The state of the address pins
should be latched at the rising edge of E. To allow for maximum address
setup time at external devices, a transparent latch should be used.
Re a d / Write (R/ W)
In all modes this pin can be used as a general-purpose I/O and is an
input with an active pull-up out of reset. If the read/write function is
required it should be enabled by setting the RDWE bit in the PEAR
register. External writes will not be possible until enabled.
Low-Byte Strob e
(LSTRB)
In all modes this pin can be used as a general-purpose I/O and is an
input with an active pull-up out of reset. If the strobe function is required,
it should be enabled by setting the LSTRE bit in the PEAR register. This
signal is used in write operations. Therefore external low byte writes will
not be possible until this function is enabled. This pin is also used as
TAGLO in Special Expanded modes and is multiplexed with the LSTRB
function.
11-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
37
Pinout a nd Sig na l De sc rip tions
Instruc tion Que ue
Tra c king Sig na ls
(IPIPE1 a nd IPIPE0)
IPIPE1 (PE6) and IPIPE0 (PE5) signals are used to track the state of the
internal instruction queue. Data movement and execution state
information is time-multiplexed on the two signals. Refer to
Development Support.
Da ta Bus Ena b le
(DBE)
The DBE pin (PE7) is an active low signal that will be asserted low during
E-clock high time. DBE provides separation between output of a
multiplexed address and the input of data. When an external address is
stretched, DBE is asserted during what would be the last quarter cycle
of the last E-clock cycle of stretch. In expanded modes this pin is used
to enable the drive control of external buses during external reads. Use
of the DBE is controlled by the NDBE bit in the PEAR register. DBE is
enabled out of reset in expanded modes.
Inve rte d E c loc k
(ECLK)
The ECLK pin (PE7) can be used to latch the address for
de-multiplexing. It has the same behavior as the ECLK, except is
inverted. In expanded modes this pin is used to enable the drive control
of external buses during external reads. Use of the ECLK is controlled
by the NDBE and DBENE bits in the PEAR register.
Ca lib ra tion
re fe re nc e (CAL)
The CAL pin (PE7) is the output of the Slow Mode programmable clock
divider, SLWCLK, and is used as a calibration reference. The SLWCLK
frequency is equal to the crystal frequency out of reset and always has
a 50% duty. If the DBE function is enabled it will override the enabled
CAL output. The CAL pin output is disabled by clearing CALE bit in the
PEAR register.
Cloc k g e ne ra tion
m od ule
te st(CGMTST)
The CGMTST pin (PE6) is the output of the clocks tested when CGMTE
bit is set in PEAR register. The PIPOE bit must be cleared for the clocks
to be tested
12-pins
MC68HC912DT128A Rev 2.0
38
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Signal Descriptions
Table 6 MC68HC912DT128A Signal Description Summary
Pin
Shared
port
Number
Pin Name
Description
112-pin
47
EXTAL
XTAL
-
-
Crystal driver and external clock input pins. On reset all the device clocks
are derived from the EXTAL input frequency. XTAL is the crystal output.
48
An active low bidirectional control signal, RESET acts as an input to
initialize the MCU to a known start-up state, and an output when COP or
clock monitor causes a reset.
RESET
-
46
ADDR[7:0]
DATA[7:0]
PB[7:0]
PA[7:0]
31–24
64–57
External bus pins share function with general-purpose I/O ports A and B.
In single chip modes, the pins can be used for I/O. In expanded modes, the
pins are used for the external buses.
ADDR[15:8]
DATA[15:8]
Data bus control and, in expanded mode, enables the drive control of
external buses during external reads.
DBE
PE7
PE7
36
36
ECLK
Inverted E clock used to latch the address.
CAL is the output of the Slow Mode programmable clock divider, SLWCLK,
and is used as a calibration reference for functions such as time of day. It is
overridden when DBE function is enabled. It always has a 50% duty.
CAL
PE7
PE6
36
37
CGMTST
Clock generation module test output.
State of mode select pins during reset determine the initial operating mode
of the MCU. After reset, MODB and MODA can be configured as
instruction queue tracking signals IPIPE1 and IPIPE0 or as
general-purpose I/O pins.
MODB/IPIPE1,
MODA/IPIPE0
PE6, PE5
PE4
PE3
PE2
PE1
PE0
-
37, 38
39
E Clock is the output connection for the external bus clock. ECLK is used
as a timing reference and for address demultiplexing.
ECLK
LSTRB/TAGLO
R/W
Low byte strobe (0 = low byte valid), in all modes this pin can be used as
I/O. The low strobe function is the exclusive-NOR of A0 and the internal
SZ8 signal. (The SZ8 internal signal indicates the size 16/8 access.) Pin
function TAGLO used in instruction tagging. See Development Support.
53
Indicates direction of data on expansion bus. Shares function with
general-purpose I/O. Read/write in expanded modes.
54
Maskable interrupt request input provides a means of applying
asynchronous interrupt requests to the MCU. Either falling edge-sensitive
triggering or level-sensitive triggering is program selectable (INTCR
register).
IRQ
55
Provides a means of requesting asynchronous nonmaskable interrupt
requests after reset initialization
XIRQ
56
During reset, this pin determines special or normal operating mode. After
reset, single-wire background interface pin is dedicated to the background
debug function. Pin function TAGHI used in instruction tagging. See
Development Support.
SMODN/BKGD/
TAGHI
23
13-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
39
Pinout a nd Sig na l De sc rip tions
Table 6 MC68HC912DT128A Signal Description Summary
Pin
Shared
port
Number
Pin Name
Description
112-pin
IX[2:0]
ECS
PK[2:0]
PK7
109-111 Page Index register emulation outputs.
108 Emulation Chip select.
PW[3:0]
PP[3:0]
112, 1–3 Pulse Width Modulator channel outputs.
Slave select output for SPI master mode, input for slave mode or master
mode.
SS
PS7
96
SCK
SDO/MOSI
SDI/MISO
TxD1
PS6
PS5
PS4
PS3
PS2
PS1
PS0
95
94
93
92
91
90
89
Serial clock for SPI system.
Master out/slave in pin for serial peripheral interface
Master in/slave out pin for serial peripheral interface
SCI1 transmit pin
RxD1
SCI1 receive pin
TxD0
SCI0 transmit pin
RxD0
SCI0 receive pin
18–15, Pins used for input capture and output compare in the timer and pulse
IOC[7:0]
PT[7:0]
7–4
accumulator subsystem.
84/82/80
AN1[7:0]
PAD1[7:0] /78/76/7 Analog inputs for the analog-to-digital conversion module 1
4/72/70
83/81/79
AN0[7:0]
PAD0[7:0] /77/75/7 Analog inputs for the analog-to-digital conversion module 0
3/71/69
MSCAN2 transmit pin (MC68HC912DT128A only). Leave unconnected if
MSCAN2 is not used.
TxCAN2(1)
-
100
RxCAN2(1)
TxCAN1
-
-
-
101
102
103
MSCAN2 receive pin (MC68HC912DT128A only).
MSCAN1 transmit pin. Leave unconnected if MSCAN1 is not used.
MSCAN1 receive pin.
RxCAN1
MSCAN0 transmit pin. If the MSCAN is not used, Leave unconnected if
MSCAN0 is not used.
TxCAN0
-
104
RxCAN0
SCL
-
105
98
MSCAN0 receive pin.
PIB7
PIB6
I2C bus serial clock line pin
I2C bus serial data line pin
SDA
99
8–11, Key wake-up and general purpose I/O; can cause an interrupt when an
19–22 input transitions from high to low or from low to high (KWPJ).
KWJ[7:0]
KWH[7:0]
PJ[7:0]
PH[7:0]
32–35, Key wake-up and general purpose I/O; can cause an interrupt when an
49–52 input transitions from high to low or from low to high (KWPH).
1
MC68HC912DT128A only
14-pins
MC68HC912DT128A Rev 2.0
40
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Port Signals
Port Sig na ls
The MC68HC912DT128A incorporates eleven ports which are used to
control and access the various device subsystems. When not used for
these purposes, port pins may be used for general-purpose I/O. In
addition to the pins described below, each port consists of a data register
which can be read and written at any time, and, with the exception of port
AD0, port AD1, PE[1:0], RxCAN and TxCAN, a data direction register
which controls the direction of each pin. After reset all general purpose
I/O pins are configured as input.
Port A
Port A pins are used for address and data in expanded modes. When
this port is not used for external access such as in single-chip mode,
these pins can be used as general purpose I/O. The port data register is
not in the address map during expanded and peripheral mode operation.
When it is in the map, port A can be read or written at anytime.
Register DDRA determines whether each port A pin is an input or output.
DDRA is not in the address map during expanded and peripheral mode
operation. Setting a bit in DDRA makes the corresponding bit in port A
an output; clearing a bit in DDRA makes the corresponding bit in port A
an input. The default reset state of DDRA is all zeroes.
When the PUPA bit in the PUCR register is set, all port A input pins are
pulled-up internally by an active pull-up device. PUCR is not in the
address map in peripheral mode.
Setting the RDPA bit in register RDRIV causes all port A outputs to have
reduced drive level. RDRIV can be written once after reset. RDRIV is not
in the address map in peripheral mode. Refer to Bus Control and
Input/Output.
Port B
Port B pins are used for address and data in expanded modes. When
this port is not used for external access such as in single-chip mode,
these pins can be used as general purpose I/O. The port data register is
not in the address map during expanded and peripheral mode operation.
When it is in the map, port B can be read or written at anytime.
15-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
41
Pinout a nd Sig na l De sc rip tions
Register DDRB determines whether each port B pin is an input or output.
DDRB is not in the address map during expanded and peripheral mode
operation. Setting a bit in DDRB makes the corresponding bit in port B
an output; clearing a bit in DDRB makes the corresponding bit in port B
an input. The default reset state of DDRB is all zeroes.
When the PUPB bit in the PUCR register is set, all port B input pins are
pulled-up internally by an active pull-up device. PUCR is not in the
address map in peripheral mode.
Setting the RDPB bit in register RDRIV causes all port B outputs to have
reduced drive level. RDRIV can be written once after reset. RDRIV is not
in the address map in peripheral mode. Refer to Bus Control and
Input/Output.
Port E
Port E pins operate differently from port A and B pins. Port E pins are
used for bus control signals and interrupt service request signals. When
a pin is not used for one of these specific functions, it can be used as
general-purpose I/O. However, two of the pins (PE[1:0]) can only be
used for input, and the states of these pins can be read in the port data
register even when they are used for IRQ and XIRQ.
The PEAR register determines pin function, and register DDRE
determines whether each pin is an input or output when it is used for
general-purpose I/O. PEAR settings override DDRE settings. Because
PE[1:0] are input-only pins, only DDRE[7:2] have effect. Setting a bit in
the DDRE register makes the corresponding bit in port E an output;
clearing a bit in the DDRE register makes the corresponding bit in port E
an input. The default reset state of DDRE is all zeroes.
When the PUPE bit in the PUCR register is set, PE[7,3,2,1,0] are pulled
up. PE[7,3,2,0] are active pull-up devices. PUPCR is not in the address
map in peripheral mode.
Neither port E nor DDRE is in the map in peripheral mode or in the
internal map in expanded modes with EME set.
Setting the RDPE bit in register RDRIV causes all port E outputs to have
reduced drive level. RDRIV can be written once after reset. RDRIV is not
16-pins
MC68HC912DT128A Rev 2.0
42
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Port Signals
in the address map in peripheral mode. Refer to Bus Control and
Input/Output.
Port H
Port H pins are used for key wake-ups that can be used with the pins
configured as inputs or outputs. The key wake-ups are triggered with
either a rising or falling edge signal (KWPH). An interrupt is generated if
the corresponding bit is enabled (KWIEH). If any of the interrupts is not
enabled, the corresponding pin can be used as a general purpose I/O
pin. Refer to I/O Ports With Key Wake-Up.
Register DDRH determines whether each port H pin is an input or output.
Setting a bit in DDRH makes the corresponding bit in port H an output;
clearing a bit in DDRH makes the corresponding bit in port H an input.
The default reset state of DDRH is all zeroes.
Register KWPH not only determines what type of edge the key wake ups
are triggered, but it also determines what type of resistive load is used
for port H input pins when PUPH bit is set in the PUCR register. Setting
a bit in KWPH makes the corresponding key wake up input pin trigger at
rising edges and loads a pull down in the corresponding port H input pin.
Clearing a bit in KWPH makes the corresponding key wake up input pin
trigger at falling edges and loads a pull up in the corresponding port H
input pin. The default state of KWPH is all zeroes.
Setting the RDPH bit in register RDRIV causes all port H outputs to have
reduced drive level. RDRIV can be written once after reset. RDRIV is not
in the address map in peripheral mode. Refer to Bus Control and
Input/Output.
Port J
Port J pins are used for key wake-ups that can be used with the pins
configured as inputs or outputs. The key wake-ups are triggered with
either a rising or falling edge signal (KWPJ). An interrupt is generated if
the corresponding bit is enabled (KWIEJ). If any of the interrupts is not
enabled, the corresponding pin can be used as a general purpose I/O
pin. Refer to I/O Ports With Key Wake-Up.
Register DDRJ determines whether each port J pin is an input or output.
Setting a bit in DDRJ makes the corresponding bit in port J an output;
17-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
43
Pinout a nd Sig na l De sc rip tions
clearing a bit in DDRJ makes the corresponding bit in port J an input. The
default reset state of DDRJ is all zeroes.
Register KWPJ not only determines what type of edge the key wake ups
are triggered, but it also determines what type of resistive load is used
for port J input pins when PUPJ bit is set in the PUCR register. Setting a
bit in KWPJ makes the corresponding key wake up input pin trigger at
rising edges and loads a pull down in the corresponding port J input pin.
Clearing a bit in KWPJ makes the corresponding key wake up input pin
trigger at falling edges and loads a pull up in the corresponding port J
input pin. The default state of KWPJ is all zeroes.
Setting the RDPJ bit in register RDRIV causes all port J outputs to have
reduced drive level. RDRIV can be written once after reset. RDRIV is not
in the address map in peripheral mode. Refer to Bus Control and
Input/Output.
Port K
Port K pins are used for page index emulation in expanded or peripheral
modes. When page index emulation is not enabled, EMK is not set in
MODE register, or the part is in single chip mode, these pins can be used
for general purpose I/O. Port K bit 3 is used as a general purpose I/O pin
only. The port data register is not in the address map during expanded
and peripheral mode operation with EMK set. When it is in the map, port
K can be read or written at anytime.
Register DDRK determines whether each port K pin is an input or output.
DDRK is not in the address map during expanded and peripheral mode
operation with EMK set. Setting a bit in DDRK makes the corresponding
bit in port K an output; clearing a bit in DDRK makes the corresponding
bit in port K an input. The default reset state of DDRK is all zeroes.
When the PUPK bit in the PUCR register is set, all port K input pins are
pulled-up internally by an active pull-up device. PUCR is not in the
address map in peripheral mode.
Setting the RDPK bit in register RDRIV causes all port K outputs to have
reduced drive level. RDRIV can be written once after reset. RDRIV is not
in the address map in peripheral mode. Refer to Bus Control and
Input/Output.
18-pins
MC68HC912DT128A Rev 2.0
44
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Port Signals
Port CAN2
(MC68HC912DT12
8A only)
The MSCAN2 uses two external pins, one input (RxCAN2) and one
output (TxCAN2). The TxCAN2 output pin represents the logic level on
the CAN: ‘0’ is for a dominant state, and ‘1’ is for a recessive state.
RxCAN2 is on bit 0 of Port CAN2, TxCAN2 is on bit 1. If the MSCAN2 is
not used, TxCAN2 should be left unconnected.
Port CAN1
Port CAN0
Port IB
The MSCAN1 uses two external pins, one input (RxCAN1) and one
output (TxCAN1). The TxCAN1 output pin represents the logic level on
the CAN: ‘0’ is for a dominant state, and ‘1’ is for a recessive state.
RxCAN1 is on bit 0 of Port CAN1, TxCAN1 is on bit 1. If the MSCAN1 is
not used, TxCAN1 should be left unconnected.
The MSCAN0 uses two external pins, one input (RxCAN0) and one
output (TxCAN0). The TxCAN0 output pin represents the logic level on
the CAN: ‘0’ is for a dominant state, and ‘1’ is for a recessive state.
RxCAN0 is on bit 0 of Port CAN0, TxCAN0 is on bit 1. If the MSCAN0 is
not used, TxCAN0 should be left unconnected.
Bidirectional pins to IIC bus interface subsystem. The IIC bus interface
uses a Serial Data line (SDA) and Serial Clock line (SCL) for data
transfer. The pins are connected to a positive voltage supply via a pull
up resistor. The pull ups can be enabled internally or connected
externally. The output stages have open drain outputs in order to
perform the wired-AND function. When the IIC is disabled the pins can
be used as general purpose I/O pins. SCL is on bit 7 of Port IB and SDA
is on bit 6. On the MC68HC912DG128A, the remaining two pins of Port
IB (PIB5 and PIB4) are controlled by registers in the IIC address space.
Register DDRIB determines pin direction of port IB when used for
general-purpose I/O. When DDRIB bits are set, the corresponding pin is
configured for output. On reset the DDRIB bits are cleared and the
corresponding pin is configured for input.
When the PUPIB bit in the IBPURD register is set, all input pins are
pulled up internally by an active pull-up device. Pullups are disabled after
reset, except for input ports 0 through 5, which are always on regardless
of PUPIB bit.
19-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
45
Pinout a nd Sig na l De sc rip tions
Setting the RDPIB bit in the IBPURD register configures all port IB
outputs to have reduced drive levels. Levels are at normal drive
capability after reset. The IBPURD register can be read or written
anytime after reset. Refer to section Inter-IC Bus.
Port AD1
Port AD0
Port P
This port is an analog input interface to the analog-to-digital subsystem
and used for general-purpose input. When analog-to-digital functions
are not enabled, the port has eight general-purpose input pins,
PAD1[7:0]. The ADPU bit in the ATD1CTL2 register enables the A/D
function.
Port AD1 pins are inputs; no data direction register is associated with this
port. The port has no resistive input loads and no reduced drive controls.
Refer to Analog-To-Digital Converter (ATD).
This port is an analog input interface to the analog-to-digital subsystem
and used for general-purpose input. When analog-to-digital functions
are not enabled, the port has eight general-purpose input pins,
PAD0[7:0]. The ADPU bit in the ATD0CTL2 register enables the A/D
function.
Port AD0 pins are inputs; no data direction register is associated with this
port. The port has no resistive input loads and no reduced drive controls.
Refer to Analog-To-Digital Converter (ATD).
The four pulse-width modulation channel outputs share general-purpose
port P pins. The PWM function is enabled with the PWEN register.
Enabling PWM pins takes precedence over the general-purpose port.
When pulse-width modulation is not in use, the port pins may be used for
general-purpose I/O.
Register DDRP determines pin direction of port P when used for
general-purpose I/O. When DDRP bits are set, the corresponding pin is
configured for output. On reset the DDRP bits are cleared and the
corresponding pin is configured for input.
20-pins
MC68HC912DT128A Rev 2.0
46
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Port Signals
When the PUPP bit in the PWCTL register is set, all input pins are pulled
up internally by an active pull-up device. Pullups are disabled after reset.
Setting the RDPP bit in the PWCTL register configures all port P outputs
to have reduced drive levels. Levels are at normal drive capability after
reset. The PWCTL register can be read or written anytime after reset.
Refer to Pulse-Width Modulator.
Port S
Port S is the 8-bit interface to the standard serial interface consisting of
the two serial communications interfaces (SCI1 and SCI0) and the serial
peripheral interface (SPI) subsystems. Port S pins are available for
general-purpose I/O when standard serial functions are not enabled.
Port S pins serve several functions depending on the various internal
control registers. If WOMS bit in the SC0CR1register is set, the
P-channel drivers of the output buffers are disabled (wire-or mode) for
pins 0 through 3. If SWOM bit in the SP0CR1 register is set, the
P-channel drivers of the output buffers are disabled (wire-or mode) for
pins 4 through 7. The open drain control affects both the serial and the
general-purpose outputs. If the RDPS bit in the SP0CR2 register is set,
Port S pin drive capabilities are reduced. If PUPS bit in the SP0CR2
register is set, a pull-up device is activated for each port S pin
programmed as a general purpose input. If the pin is programmed as a
general-purpose output, the pull-up is disconnected from the pin
regardless of the state of PUPS bit. See Multiple Serial Interface.
Port T
This port provides eight general-purpose I/O pins when not enabled for
input capture and output compare in the timer and pulse accumulator
subsystem. The TEN bit in the TSCR register enables the timer function.
The pulse accumulator subsystem is enabled with the PAEN bit in the
PACTL register.
Register DDRT determines pin direction of port T when used for
general-purpose I/O. When DDRT bits are set, the corresponding pin is
configured for output. On reset the DDRT bits are cleared and the
corresponding pin is configured for input.
21-pins
MC68HC912DT128A Rev 2.0
MOTOROLA
Pinout and Signal Descriptions
47
Pinout a nd Sig na l De sc rip tions
When the PUPT bit in the TMSK2 register is set, all input pins are pulled
up internally by an active pull-up device. Pullups are disabled after reset.
Setting the RDPT bit in the TMSK2 register configures all port T outputs
to have reduced drive levels. Levels are at normal drive capability after
reset. The TMSK2 register can be read or written anytime after reset.
Refer to Enhanced Capture Timer.
Table 7 MC68HC912DT128A Port Description Summary
Pin
Data Direction
Register (Address)
Numbers
Port Name
Description
112-pin
Port A
PA[7:0]
In/Out
DDRA ($0002)
Port A and port B pins are used for address and data in
expanded modes. The port data registers are not in the
address map during expanded and peripheral mode operation.
When in the map, port A and port B can be read or written any
time.
64-57
Port B
PB[7:0]
In/Out
DDRB ($0003)
31–24
DDRA and DDRB are not in the address map in expanded or
peripheral modes.
84/82/80/
78/76/74/
72/70
Port AD1
PAD1[7:0]
In
In
Analog-to-digital converter 1 and general-purpose I/O.
Analog-to-digital converter 0 and general-purpose I/O.
83/81/79/
77/75/73/
71/69
Port AD0
PAD0[7:0]
Port CAN2
PCAN2[1] Out
PCAN2[0] In
PCAN2[1:0] are used with the MSCAN2 module and cannot be
used as general purpose I/O (MC68HC912DT128A only).
PCAN2[1:0] 100–101
(1)
Port CAN1
102–103
PCAN1[1] Out
PCAN1[0] In
PCAN1[1:0] are used with the MSCAN1 module and cannot be
used as general purpose I/O.
PCAN1[1:0]
Port CAN0
104–105
PCAN0[1] Out
PCAN0[0] In
PCAN0[1:0] are used with the MSCAN0 module and cannot be
used as general purpose I/O.
PCAN0[1:0]
Port IB
98–99
In/Out
DDRIB ($00E7)
General purpose I/O. PIB[7:6] are used with the I-Bus module
when enabled.
PIB[7:6]
Port IB
100–101
PIB[5:4](2)
In/Out
DDRIB ($00E7)
General purpose I/O (MC68HC912DG128A only).
PE[1:0] In
PE[7:2] In/Out
DDRE ($0009)
Port E
PE[7:0]
36–39,
53–56
Mode selection, bus control signals and interrupt service
request signals; or general-purpose I/O.
Port K
PK[7,3:0]
13,
108-111
In/Out
DDRK ($00FD)
Page index emulation signals in expanded or peripheral mode
or general-purpose I/O.
22-pins
MC68HC912DT128A Rev 2.0
48
Pinout and Signal Descriptions
MOTOROLA
Pinout and Signal Descriptions
Port Signals
Table 7 MC68HC912DT128A Port Description Summary
Pin
Data Direction
Register (Address)
Numbers
Port Name
Description
112-pin
Port P
PP[3:0]
112,
1–3
In/Out
DDRP ($0057)
General-purpose I/O. PP[3:0] are used with the pulse-width
modulator when enabled.
Port S
PS[7:0]
In/Out
DDRS ($00D7)
Serial communications interfaces 1 and 0 and serial peripheral
interface subsystems; or general-purpose I/O.
96–89
Port T
PT[7:0]
18–15,
7–4
In/Out
DDRT ($00AF)
General-purpose I/O when not enabled for input capture and
output compare in the timer and pulse accumulator subsystem.
1
2
MC68HC912DT128A only
MC68HC912DG128A only
Port Pull-Up
Pull-Down a nd
Re d uc e d Drive
MCU ports can be configured for internal pull-up. To reduce power
consumption and RFI, the pin output drivers can be configured to
operate at a reduced drive level. Reduced drive causes a slight increase
in transition time depending on loading and should be used only for ports
which have a light loading. Table 1 summarizes the port pull-up default
status and controls.
Table 1 Port Pull-Up, Pull-Down and Reduced Drive Summary
Enable Bit
Reduced Drive Control Bit
Port
Name
Resistive
Input Loads
Register
(Address)
Reset
State
Register
(Address)
Reset
State
Bit Name
Bit Name
Port A
Port B
Pull-up
PUCR ($000C)
PUCR ($000C)
PUPA
PUPB
Disabled RDRIV ($000D)
Disabled RDRIV ($000D)
RDPA
RDPB
Full drive
Full drive
Pull-up
Port E:
PE7, PE[3:2]
PE[1:0]
Pull-up
Pull-up
None
PUCR ($000C)
PUCR ($000C)
PUPE
PUPE
Enabled RDRIV ($000D)
Enabled
RDPE
—
Full drive
PE[6:4]
—
RDRIV ($000D)
RDPE
Full drive
Full drive
Pull-up or
Pull-down
Port H
Port J
PUCR ($000C)
PUCR ($000C)
PUPH
PUPJ
Disabled RDRIV ($000D)
Disabled RDRIV ($000D)
RDPH
RDPJ
Pull-up or
Pull-down
Full drive
Port K
Port P
Pull-up
Pull-up
PUCR ($000C)
PWCTL ($0054)
PUPK
PUPP
Disabled RDRIV ($000D)
Disabled PWCTL ($0054)
RDPK
RDPP
Full drive
Full drive
SP0CR2
Enabled
Port S
Port T
Pull-up
Pull-up
SP0CR2 ($00D1)
TMSK2 ($008D)
PUPS
TPU
RDPS
TDRB
Full drive
Full drive
($00D1)
Disabled TMSK2 ($008D)
23-pins
MC68HC912DT128A Rev 2.0
49
MOTOROLA
Pinout and Signal Descriptions
Pinout a nd Sig na l De sc rip tions
Table 1 Port Pull-Up, Pull-Down and Reduced Drive Summary
Enable Bit Reduced Drive Control Bit
Register Reset
Port
Name
Resistive
Input Loads
Register
(Address)
Reset
State
Bit Name
Bit Name
(Address)
State
Port IB[7:6]
Pull-up
IBPURD ($00E5)
PUPIB Disabled IBPURD ($00E5) RDPIB
PUPIB Disabled IBPURD ($00E5) RDPIB
Full drive
Port
Pull-up
IBPURD ($00E5)
Full drive
IB[5:4](1)
Port AD0
Port AD1
None
None
—
—
—
—
Port
None
—
—
CAN2[1](2)
Port
Pull-up
Always enabled
—
CAN2[0](2)
Port CAN1[1]
Port CAN1[0]
Port CAN0[1]
Port CAN0[0]
None
Pull-up
None
—
—
—
—
—
Always enabled
—
Pull-up
Always enabled
1
2
MC68HC912DG128A only
MC68HC912DT128A only
24-pins
MC68HC912DT128A Rev 2.0
50
Pinout and Signal Descriptions
MOTOROLA
Re g iste rs
Re g iste rs
Conte nts
Register Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Re g iste r Bloc k
The register block can be mapped to any 2K byte boundary within the
standard 64K byte address space by manipulating bits REG[15:11] in
the INITRG register. INITRG establishes the upper five bits of the
register block’s 16-bit address. The register block occupies the first 1K
byte of the 2K byte block. Default addressing (after reset) is indicated in
the table below. For additional information refer to Operating Modes.
Table 8 MC68HC912DT128A Register Map (Sheet 1 of 11)
Address
$0000
$0001
$0002
$0003
Bit 7
PA7
6
5
4
3
2
1
Bit 0
PA0
Name
PA6
PA5
PA4
PA3
PA2
PA1
PORTA(1)
PORTB(1)
DDRA(1)
DDRB(1)
PB7
PB6
PB5
PB4
PB3
PB2
PB1
PB0
DDA7
DDB7
DDA6
DDB6
DDA5
DDB5
DDA4
DDB4
DDA3
DDB3
DDA2
DDB2
DDA1
DDB1
DDA0
DDB0
$0004-$
0007
0
0
0
0
0
0
0
0
Reserved(3)
$0008
$0009
$000A
$000B
$000C
$000D
$000E
$000F
$0010
$0011
PE7
DDE7
NDBE
SMODN
PUPK
RDPK
0
PE6
DDE6
CGMTE
MODB
PUPJ
RDPJ
0
PE5
DDE5
PIPOE
MODA
PUPH
RDPH
0
PE4
DDE4
NECLK
ESTR
PUPE
RDPE
0
PE3
PE2
PE1
0
PE0
0
PORTE(2)
DDRE(2)
PEAR(3)
MODE(3)
PUCR(3)
RDRIV(3)
Reserved(3)
Reserved(3)
INITRM
DDE3
DDE2
LSTRE
RDWE
CALE
EMK
PUPB
RDPB
0
DBENE
EME
PUPA
RDPA
0
IVIS
EBSWAI
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
RAM15
REG15
RAM14
REG14
RAM13
REG13
0
0
0
REG12
REG11
0
MMSWAI
INITRG
1-reg
MC68HC912DT128A Rev 2.0
51
MOTOROLA
Registers
Re g iste rs
Table 8 MC68HC912DT128A Register Map (Sheet 2 of 11)
Address
Bit 7
EE15
6
5
4
3
0
2
0
1
0
Bit 0
Name
INITEE
MISC
$0012
EE14
EE13
EE12
EEON
$0013 ROMTST NDRF
RFSTR1 RFSTR0 EXSTR1 EXSTR0 ROMHM ROMON
$0014
$0015
$0016
$0017
$0018
$0019
$001A
$001B
$001C
$001D
$001E
$001F
$0020
$0021
$0022
$0023
$0024
$0025
$0026
$0027
$0028
$0029
$002A
$002B
$002C
RTIE
RTIF
CME
Bit 7
ITE6
ITD6
ITC6
ITB6
ITA6
0
RSWAI
0
RSBCK Reserved RTBYP
RTR2
0
RTR1
0
RTR0
0
RTICTL
RTIFLG
COPCTL
COPRST
ITST0
0
0
0
DISR
3
FCME FCMCOP WCOP
CR2
2
CR1
1
CR0
Bit 0
ITF4
ITE4
ITD4
ITC4
ITB4
0
6
ITE8
ITD8
ITC8
ITB8
ITA8
0
5
ITEA
ITDA
ITCA
ITBA
ITAA
0
4
ITEC
ITDC
ITCC
ITBC
ITAC
0
ITEE
ITDE
ITCE
ITBE
ITAE
0
ITF0
ITE0
ITD0
ITC0
ITB0
0
ITF2
ITE2
ITD2
ITC2
ITB2
0
ITST1
ITST2
ITST3
ITST4
Reserved
INTCR
IRQE
1
IRQEN
PSEL6
BKEN0
BKDBE
14
DLY
PSEL5
BKPM
BKMBH
13
0
0
0
0
0
PSEL4
0
PSEL3
PSEL2
PSEL1
0
0
HPRIO
BRKCT0
BRKCT1
BRKAH
BRKAL
BRKDH
BRKDL
Reserved
Reserved
PORTJ
PORTH
DDRJ
BKEN1
0
BK1ALE BK0ALE
0
BKMBL BK1RWE BK1RW BK0RWE BK0RW
Bit 15
Bit 7
Bit 15
Bit 7
0
12
4
11
3
10
2
9
1
Bit 8
Bit 0
Bit 8
Bit 0
0
6
5
14
13
12
11
10
9
6
5
4
3
2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
PJ7
PJ6
PH6
DDJ6
DDH6
PJ5
PH5
DDJ5
DDH5
PJ4
PH4
DDJ4
DDH4
PJ3
PH3
DDJ3
DDH3
PJ2
PH2
DDJ2
DDH2
PJ1
PH1
DDJ1
DDH1
PJ0
PH0
DDJ0
DDH0
PH7
DDJ7
DDH7
DDRH
KWIEJ7 KWIEJ6 KWIEJ5 KWIEJ4 KWIEJ3 KWIEJ2 KWIEJ1 KWIEJ0
$002D KWIEH7 KWIEH6 KWIEH5 KWIEH4 KWIEH3 KWIEH2 KWIEH1 KWIEH0
$002E KWIFJ7 KWIFJ6 KWIFJ5 KWIFJ4 KWIFJ3 KWIFJ2 KWIFJ1 KWIFJ0
$002F KWIFH7 KWIFH6 KWIFH5 KWIFH4 KWIFH3 KWIFH2 KWIFH1 KWIFH0
KWIEJ
KWIEH
KWIFJ
KWIFH
KWPJ
$0030
$0031
$0032
$0033
KWPJ7
KWPJ6
KWPJ5
KWPJ4
KWPJ3
KWPJ2
KWPJ1
KWPJ0
KWPH7 KWPH6 KWPH5 KWPH4 KWPH3 KWPH2 KWPH1 KWPH0
KWPH
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Reserved
Reserved
$0034–
$0037
Unimplemented(4)
Reserved
$0038
$0039
0
0
0
0
SYN5
0
SYN4
0
SYN3
0
SYN2
SYN1
SYN0
SYNR
REFDV2 REFDV1 REFDV0
REFDV
$003A TSTOUT7 TSTOUT6 TSTOUT5 TSTOUT4 TSTOUT3 TSTOUT2 TSTOUT1 TSTOUT0 CGTFLG
$003B
LOCKIF
LOCK
0
0
0
0
0
LHIF
LHIE
LHOME
NOLHM
PLLFLG
PLLCR
$003C LOCKIE
PLLON
AUTO
ACQ
PSTP
2--reg
MC68HC912DT128A Rev 2.0
52
Registers
MOTOROLA
Registers
Register Block
Table 8 MC68HC912DT128A Register Map (Sheet 3 of 11)
Address
$003D
$003E
$003F
$0040
$0041
$0042
$0043
$0044
$0045
$0046
$0047
$0048
$0049
$004A
$004B
$004C
$004D
$004E
$004F
$0050
$0051
$0052
$0053
$0054
$0055
$0056
$0057
Bit 7
0
6
5
4
3
2
1
Bit 0
0
Name
CLKSEL
SLOW
BCSP
BCSS
0
0
MCS
0
0
0
SLDV5
SLDV4
SLDV3
TST3
PCKA0
PPOL3
SLDV2
TST2
SLDV1
TST1
PCKB1
PPOL1
SLDV0
TST0
PCKB0
PPOL0
OPNLE
CON23
PCLK3
0
TRK
TSTCLKE
TST4
CGTCTL
PWCLK
CON01
PCKA2
PCKA1
PCKB2
PPOL2
PCLK2
PCLK1
PCLK0
PWPOL
0
0
0
PWEN3 PWEN2 PWEN1 PWEN0
PWEN
0
Bit 6
5
4
3
2
1
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
PSBCK
0
PWPRES
PWSCAL0
PWSCNT0
PWSCAL1
PWSCNT1
PWCNT0
PWCNT1
PWCNT2
PWCNT3
PWPER0
PWPER1
PWPER2
PWPER3
PWDTY0
PWDTY1
PWDTY2
PWDTY3
PWCTL
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
0
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
6
5
4
3
2
1
1
6
6
5
4
4
3
3
2
2
5
5
1
6
4
3
2
1
0
0
PSWAI
0
CENTR
0
RDPP
0
PUPP
0
DISCR
PP7
DDP7
DISCP
PP6
DDP6
DISCAL
PP5
DDP5
PWTST
PP4
DDP4
PP3
DDP3
PP2
DDP2
PP1
DDP1
PP0
DDP0
PORTP
DDRP
$0058-$
005F
0
0
0
0
0
0
0
0
Reserved
$0060
$0061
$0062
$0063
$0064
$0065
$0066
$0067
$0068
$0069
Reserved
Reserved
ATD0CTL0
ATD0CTL1
ATD0CTL2
ATD0CTL3
ATD0CTL4
ATD0CTL5
ATD0STAT0
ATD0STAT1
ADPU
0
AFFC
0
ASWAI
0
DJM
0
DSGN Reserved ASCIE
ASCIF
FRZ0
PRS0
CA
S1C
PRS3
CD
FIFO
PRS2
CC
FRZ1
PRS1
CB
RES10
0
SMP1
S8C
0
SMP0
SCAN
0
PRS4
MULT
0
SCF
CCF7
SAR9
SAR1
0
CC2
CC1
CC0
CCF6
SAR8
SAR0
CCF5
SAR7
RST
CCF4
SAR6
TSTOUT
CCF3
SAR5
TST3
CCF2
SAR4
TST2
CCF1
SAR3
TST1
CCF0
SAR2 ATD0TESTH
TST0
ATD0TESTL
$006A–$
006E
0
0
0
0
0
0
0
0
Reserved
3-reg
MC68HC912DT128A Rev 2.0
53
MOTOROLA
Registers
Re g iste rs
Table 8 MC68HC912DT128A Register Map (Sheet 4 of 11)
Address
Bit 7
6
PAD06
14
5
4
3
2
1
Bit 0
PAD00
Bit 8
0
Name
PORTAD0
ADR00H
ADR00L
ADR01H
ADR01L
ADR02H
ADR02L
ADR03H
ADR03L
ADR04H
ADR04L
ADR05H
ADR05L
ADR06H
ADR06L
ADR07H
ADR07L
TIOS
$006F
$0070
$0071
$0072
$0073
$0074
$0075
$0076
$0077
$0078
$0079
$007A
$007B
$007C
$007D
$007E
$007F
$0080
$0081
$0082
$0083
$0084
$0085
$0086
$0087
$0088
$0089
$008A
$008B
$008C
$008D
$008E
$008F
$0090
$0091
$0092
$0093
$0094
$0095
$0096
$0097
PAD07
Bit 15
Bit 7
PAD05
PAD04
PAD03
PAD02
PAD01
13
12
11
10
9
Bit 6
14
0
0
0
0
0
Bit 15
Bit 7
13
12
11
10
9
Bit 8
0
Bit 6
14
0
0
0
0
0
Bit 15
Bit 7
13
12
11
10
9
Bit 8
0
Bit 6
14
0
0
0
0
0
Bit 15
Bit 7
13
12
11
10
9
Bit 8
0
Bit 6
14
0
0
0
0
0
Bit 15
Bit 7
13
12
11
10
9
Bit 8
0
Bit 6
14
0
13
0
12
0
0
0
Bit 15
Bit 7
11
10
9
Bit 8
0
Bit 6
14
0
0
0
11
0
10
0
Bit 15
Bit 7
13
12
9
Bit 8
0
Bit 6
14
0
0
0
0
0
Bit 15
Bit 7
13
12
11
10
9
0
Bit 8
0
Bit 6
IOS6
FOC6
OC7M6
OC7D6
14
0
0
0
0
IOS7
FOC7
OC7M7
OC7D7
Bit 15
Bit 7
IOS5
FOC5
OC7M5
OC7D5
13
IOS4
FOC4
OC7M4
OC7D4
12
IOS3
FOC3
OC7M3
OC7D3
11
IOS2
FOC2
OC7M2
OC7D2
10
IOS1
FOC1
OC7M1
OC7D1
9
IOS0
FOC0
OC7M0
OC7D0
Bit 8
Bit 0
CFORC
OC7M
OC7D
TCNT
6
5
4
3
2
1
TCNT
TEN
TSWAI
TSBCK
TFFCA
Reserved
TSCR
Reserved
TQCR
OM7
OM3
EDG7B
EDG3B
C7I
OL7
OM6
OM2
EDG6B
EDG2B
C5I
PUPT
C5F
0
OL6
OL2
EDG6A
EDG2A
C4I
RDPT
C4F
0
OM5
OM1
EDG5B
EDG1B
C3I
TCRE
C3F
0
OL5
OL1
EDG5A
EDG1A
C2I
PR2
C2F
0
OM4
OL4
OL0
TCTL1
TCTL2
TCTL3
TCTL4
TMSK1
TMSK2
TFLG1
TFLG2
TC0
OL3
OM0
EDG7A
EDG4B
EDG4A
EDG0A
C0I
EDG3A
EDG0B
C6I
0
C1I
PR1
C1F
0
TOI
PR0
C0F
C7F
C6F
0
TOF
0
Bit 15
Bit 7
14
6
13
12
11
10
9
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
5
4
3
2
1
TC0
Bit 15
Bit 7
14
6
13
12
11
10
9
TC1
5
4
3
2
1
TC1
Bit 15
Bit 7
14
6
13
12
11
10
9
TC2
5
4
3
2
1
TC2
Bit 15
Bit 7
14
6
13
12
11
10
9
TC3
5
4
3
2
1
TC3
4-reg
MC68HC912DT128A Rev 2.0
54
Registers
MOTOROLA
Registers
Register Block
Table 8 MC68HC912DT128A Register Map (Sheet 5 of 11)
Address
$0098
$0099
$009A
$009B
$009C
$009D
$009E
$009F
$00A0
$00A1
$00A2
$00A3
$00A4
$00A5
$00A6
$00A7
$00A8
$00A9
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
0
6
14
6
5
13
5
4
12
4
3
2
1
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
PAI
Name
TC4
11
10
9
3
2
1
TC4
14
6
13
5
12
4
11
10
9
TC5
3
2
1
TC5
14
6
13
5
12
4
11
10
9
TC6
3
2
1
TC6
14
6
13
5
12
4
11
10
9
TC7
3
2
1
TC7
PAEN
0
PAMOD PEDGE
CLK1
CLK0
PAOVI
PACTL
PAFLG
PACN3
PACN2
PACN1
PACN0
MCCTL
MCFLG
ICPAR
DLYCT
ICOVW
ICSYS
Reserved
TIMTST
PORTT
DDRT
PBCTL
PBFLG
PA3H
0
0
5
5
5
5
0
0
0
PAOVF
PAIF
Bit 0
Bit 0
Bit 0
Bit 0
Bit 7
Bit 7
Bit 7
Bit 7
MCZI
MCZF
0
6
4
3
2
1
1
1
1
6
4
3
3
2
2
6
4
6
4
3
2
MODMC RDMCL
ICLAT
FLMC
POLF3
PA3EN
0
MCEN
POLF2
PA2EN
0
MCPR1 MCPR0
0
0
0
0
0
0
0
0
0
POLF1
PA1EN
DLY1
POLF0
PA0EN
DLY0
0
$00AA NOVW7 NOVW6 NOVW5 NOVW4 NOVW3 NOVW2 NOVW1 NOVW0
$00AB
$00AC
$00AD
$00AE
$00AF
$00B0
$00B1
$00B2
$00B3
$00B4
$00B5
$00B6
$00B7
$00B8
$00B9
$00BA
$00BB
$00BC
$00BD
$00BE
$00BF
$00C0
SH37
0
SH26
SH15
SH04
TFMOD PACMX
BUFEN
LATQ
0
0
0
0
0
0
0
0
0
0
PT5
DDT5
0
0
0
0
TCBYP
0
PT7
DDT7
0
PT6
PT4
PT3
PT2
PT1
PT0
DDT0
0
DDT6
DDT4
DDT3
DDT2
DDT1
PBEN
0
0
0
PBOVI
0
0
6
0
0
0
0
PBOVF
0
Bit 7
Bit 7
Bit 7
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
BTST
5
4
3
2
1
Bit 0
Bit 0
Bit 0
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
Bit 8
Bit 0
SBR8
6
5
4
3
2
1
PA2H
6
5
4
3
2
1
PA1H
6
5
4
3
2
1
PA0H
14
6
13
5
12
11
10
9
MCCNTH
MCCNTL
TC0H
4
3
2
1
14
6
13
5
12
11
10
9
4
3
2
1
TC0H
14
6
13
5
12
11
10
9
TC1H
4
3
2
1
TC1H
14
6
13
5
12
11
10
9
TC2H
4
12
3
11
2
10
1
9
TC2H
14
6
13
5
TC3H
4
3
2
1
TC3H
BSPL
BRLD
SBR12
SBR11
SBR10
SBR9
SC0BDH
5-reg
MC68HC912DT128A Rev 2.0
55
MOTOROLA
Registers
Re g iste rs
Table 8 MC68HC912DT128A Register Map (Sheet 6 of 11)
Address
Bit 7
6
SBR6
WOMS
TCIE
TC
5
SBR5
RSRC
RIE
RDRF
0
4
SBR4
M
3
SBR3
WAKE
TE
2
SBR2
ILT
1
SBR1
PE
Bit 0
SBR0
PT
Name
SC0BDL
SC0CR1
SC0CR2
SC0SR1
SC0SR2
SC0DRH
SC0DRL
SC1BDH
SC1BDL
SC1CR1
SC1CR2
SC1SR1
SC1SR2
SC1DRH
SC1DRL
SP0CR1
SP0CR2
SP0BR
$00C1
$00C2
$00C3
$00C4
$00C5
$00C6
$00C7
$00C8
$00C9
$00CA
$00CB
$00CC
$00CD
$00CE
$00CF
$00D0
$00D1
$00D2
$00D3
$00D4
$00D5
$00D6
$00D7
SBR7
LOOPS
TIE
ILIE
IDLE
0
RE
RWU
FE
SBK
PF
TDRE
0
OR
NF
0
0
0
0
RAF
0
R8
T8
0
0
0
0
0
R7/T7
BTST
SBR7
LOOPS
TIE
R6/T6
BSPL
SBR6
WOMS
TCIE
TC
R5/T5
BRLD
SBR5
RSRC
RIE
RDRF
0
R4/T4
SBR12
SBR4
M
R3/T3
SBR11
SBR3
WAKE
TE
R2/T2
SBR10
SBR2
ILT
R1/T1
SBR9
SBR1
PE
R0/T0
SBR8
SBR0
PT
ILIE
IDLE
0
RE
RWU
FE
SBK
PF
TDRE
0
OR
NF
0
0
0
0
RAF
0
R8
T8
0
0
0
0
0
R7/T7
SPIE
0
R6/T6
SPE
0
R5/T5
SWOM
0
R4/T4
MSTR
0
R3/T3
CPOL
PUPS
0
R2/T2
CPHA
RDPS
SPR2
0
R1/T1
SSOE
SSWAI
SPR1
0
R0/T0
LSBF
SPC0
SPR0
0
0
0
0
0
SPIF
0
WCOL
0
0
MODF
0
0
SP0SR
0
0
0
0
0
Reserved
SP0DR
Bit 7
PS7
DDS7
6
5
4
3
2
1
Bit 0
PS0
DDS0
PS6
DDS6
PS5
DDS5
PS4
DDS4
PS3
DDS3
PS2
DDS2
PS1
DDS1
PORTS
DDRS
$00D8–$
00DF
0
0
0
0
0
0
0
0
Reserved
$00E0
$00E1
$00E2
$00E3
$00E4
$00E5
$00E6
$00E7
ADR7
0
ADR6
0
ADR5
IBC5
MS/SL
IBB
ADR4
IBC4
Tx/Rx
IBAL
D4
ADR3
IBC3
TXAK
0
ADR2
IBC2
RSTA
SRW
D2
ADR1
IBC1
0
0
IBAD
IBFD
IBC0
IBSWAI
RXAK
D0
IBEN
TCF
D7
IBIE
IAAS
D6
IBCR
IBIF
D1
IBSR
D5
D3
IBDR
0
0
0
RDPIB
PIB4
0
0
0
PUPIB
PIB0
IBPURD
PORTIB
DDRIB
PIB7
PIB6
PIB5
PIB3
PIB2
PIB1
DDRIB7 DDRIB6 DDRIB5 DDRIB4 DDRIB3 DDRIB2 DDRIB1 DDRIB0
Unimplemented(4)
$00E8–
$00EB
Reserved
Reserved
$00EC–$
00ED
0
0
0
0
0
0
0
0
0
0
0
0
0
0
$00EE
EEDIV9 EEDIV8
EEDIVH
EEDIVL
EEMCR
$00EF
EEDIV7 EEDIV6 EEDIV5 EEDIV4 EEDIV3 EEDIV2 EEDIV1 EEDIV0
PROTLCK
$00F0 NOBDML NOSHW
Reserved
1
EESWAI
EERC
$00F1 SHPROT
1
BPROT5 BPROT4 BPROT3 BPROT2 BPROT1 BPROT0 EEPROT
6-reg
MC68HC912DT128A Rev 2.0
56
Registers
MOTOROLA
Registers
Register Block
Table 8 MC68HC912DT128A Register Map (Sheet 7 of 11)
Address
$00F2
$00F3
$00F4
$00F5
$00F6
$00F7
$00F8
$00F9
$00FA
$00FB
$00FC
$00FD
$00FE
$00FF
$0100
$0101
$0102
$0103
$0104
$0105
$0106
$0107
$0108
Bit 7
0
6
5
4
3
2
ETMSD
ERASE
0
1
Bit 0
ETMSE
EEPGM
LOCK
BOOTP
TMSE
PGM
Name
EETST
EREVTN
0
0
0
ETMR
EELAT
0
BULKP
0
0
AUTO
BYTE
ROW
EEPROG
FEELCK
FEEMCR
FEETST
FEECTL
MTST0
0
0
0
0
0
0
0
0
0
0
0
0
0
STRE
0
REVTUN
0
0
TMSD
0
TMR
ERAS
MT01
MT09
MT11
MT19
PK1
DDK1
0
0
FEESWAI HVEN
MT07
MT0F
MT17
MT1F
PK7
DDK7
0
MT06
MT05
MT0D
MT15
MT1D
0
MT04
MT03
MT0B
MT13
MT1B
PK3
DDK3
0
MT02
MT0A
MT12
MT1A
PK2
DDK2
0
MT00
MT08
MT10
MT18
PK0
MT0E
MT0C
MTST1
MT16
MT14
MTST2
MT1E
MT1C
MTST3
0
0
0
0
0
PORTK(5)
DDRK(5)
Reserved
PPAGE
0
0
DDK0
0
0
0
0
0
0
0
PIX2
PIX1
PIX0
0
0
0
CSWAI
0
SYNCH TLNKEN SLPAK
SLPRQ SFTRES
C0MCR0
0
0
0
LOOPB
BRP2
WUPM CLKSRC C0MCR1
SJW1
SAMP
SJW0
BRP5
BRP4
BRP3
BRP1
BRP0
C0BTR0
C0BTR1
C0RFLG
C0RIER
C0TFLG
C0TCR
TSEG22 TSEG21 TSEG20 TSEG13 TSEG12 TSEG11 TSEG10
WUPIF RWRNIF TWRNIF RERRIF TERRIF BOFFIF
WUPIE RWRNIE TWRNIE RERRIE TERRIE BOFFIE
OVRIF
OVRIE
TXE1
RXF
RXFIE
TXE0
0
0
0
ABTAK2 ABTAK1 ABTAK0
ABTRQ2 ABTRQ1 ABTRQ0
0
0
0
TXE2
TXEIE2
IDHIT2
TXEIE1
IDHIT1
TXEIE0
IDHIT0
0
IDAM1
IDAM0
C0IDAC
$0109–
$010D
Unimplemented(4)
Reserved
$010E RXERR7 RXERR6 RXERR5 RXERR4 RXERR3 RXERR2 RXERR1 RXERR0 C0RXERR
$010F TXERR7 TXERR6 TXERR5 TXERR4 TXERR3 TXERR2 TXERR1 TXERR0 C0TXERR
$0110
$0111
$0112
$0113
$0114
$0115
$0116
$0117
$0118
$0119
$011A
$011B
$011C
$011D
AC7
AC7
AC7
AC7
AM7
AM7
AM7
AM7
AC7
AC7
AC7
AC7
AM7
AM7
AC6
AC6
AC6
AC6
AM6
AM6
AM6
AM6
AC6
AC6
AC6
AC6
AM6
AM6
AC5
AC5
AC5
AC5
AM5
AM5
AM5
AM5
AC5
AC5
AC5
AC5
AM5
AM5
AC4
AC4
AC4
AC4
AM4
AM4
AM4
AM4
AC4
AC4
AC4
AC4
AM4
AM4
AC3
AC3
AC3
AC3
AM3
AM3
AM3
AM3
AC3
AC3
AC3
AC3
AM3
AM3
AC2
AC2
AC2
AC2
AM2
AM2
AM2
AM2
AC2
AC2
AC2
AC2
AM2
AM2
AC1
AC1
AC1
AC1
AM1
AM1
AM1
AM1
AC1
AC1
AC1
AC1
AM1
AM1
AC0
AC0
AC0
AC0
AM0
AM0
AM0
AM0
AC0
AC0
AC0
AC0
AM0
AM0
C0IDAR0
C0IDAR1
C0IDAR2
C0IDAR3
C0IDMR0
C0IDMR1
C0IDMR2
C0IDMR3
C0IDAR4
C0IDAR5
C0IDAR6
C0IDAR7
C0IDMR4
C0IDMR5
7-reg
MC68HC912DT128A Rev 2.0
57
MOTOROLA
Registers
Re g iste rs
Table 8 MC68HC912DT128A Register Map (Sheet 8 of 11)
Address
$011E
$011F
Bit 7
AM7
AM7
6
5
4
3
2
1
Bit 0
AM0
AM0
Name
AM6
AM6
AM5
AM5
AM4
AM4
AM3
AM3
AM2
AM2
AM1
AM1
C0IDMR6
C0IDMR7
$0120–
$013C
Unimplemented(4)
Reserved
$013D
0
0
0
0
0
0
PUPCAN RDPCAN PCTLCAN0
$013E
PCAN7
PCAN6
PCAN5
PCAN4
PCAN3
PCAN2
TxCAN
0
RxCAN PORTCAN0
$013F DDCAN7 DDCAN6 DDCAN5 DDCAN4 DDCAN3 DDCAN2
0
DDRCAN0
$0140–
FOREGROUND RECEIVE BUFFER 0
$014F
RxFG0
$0150–
TRANSMIT BUFFER 00
$015F
Tx00
Tx01
$0160–
TRANSMIT BUFFER 01
$016F
$0170–
TRANSMIT BUFFER 02
$017F
Tx02
$0180–
$01DF
Unimplemented(4)
Reserved
$01E0
$01E1
$01E2
$01E3
$01E4
$01E5
$01E6
$01E7
$01E8
$01E9
Reserved
Reserved
ATD1CTL0
ATD1CTL1
ATD1CTL2
ATD1CTL3
ATD1CTL4
ATD1CTL5
ATD1STAT0
ATD1STAT1
ADPU
0
AFFC
0
ASWAI
0
DJM
0
DSGN Reserved ASCIE
ASCIF
FRZ0
PRS0
CA
S1C
PRS3
CD
FIFO
PRS2
CC
FRZ1
PRS1
CB
RES10
0
SMP1
S8C
0
SMP0
SCAN
0
PRS4
MULT
0
SCF
CCF7
SAR9
SAR1
0
CC2
CC1
CC0
CCF6
SAR8
SAR0
CCF5
SAR7
RST
CCF4
SAR6
TSTOUT
CCF3
SAR5
TST3
CCF2
SAR4
TST2
CCF1
SAR3
TST1
CCF0
SAR2 ATD1TESTH
TST0
ATD1TESTL
$01EA–$
01EE
0
0
0
0
0
0
0
0
Reserved
$01EF
$01F0
$01F1
$01F2
$01F3
$01F4
$01F5
$01F6
$01F7
$01F8
$01F9
$01FA
$01FB
PAD17
Bit 15
Bit 7
PAD16
14
PAD15
PAD14
PAD13
PAD12
PAD11
PAD10
Bit 8
0
PORTAD1
ADR10H
ADR10L
ADR11H
ADR11L
ADR12H
ADR12L
ADR13H
ADR13L
ADR14H
ADR14L
ADR15H
ADR15L
13
0
12
0
11
0
10
0
9
0
9
0
9
0
9
0
9
0
9
0
Bit 6
14
Bit 15
Bit 7
13
0
12
0
11
0
10
0
Bit 8
0
Bit 6
14
Bit 15
Bit 7
13
0
12
0
11
0
10
0
Bit 8
0
Bit 6
14
Bit 15
Bit 7
13
0
12
0
11
0
10
0
Bit 8
0
Bit 6
14
Bit 15
Bit 7
13
0
12
0
11
0
10
0
Bit 8
0
Bit 6
14
Bit 15
Bit 7
13
0
12
0
11
0
10
0
Bit 8
0
Bit 6
8-reg
MC68HC912DT128A Rev 2.0
58
Registers
MOTOROLA
Registers
Register Block
Table 8 MC68HC912DT128A Register Map (Sheet 9 of 11)
Address
$01FC
Bit 7
Bit 15
Bit 7
Bit 15
Bit 7
0
6
14
5
4
12
0
3
11
0
2
10
0
1
9
0
9
0
Bit 0
Bit 8
0
Name
13
ADR16H
ADR16L
ADR17H
ADR17L
C2MCR0
$01FD
Bit 6
14
0
13
$01FE
12
0
11
0
10
0
Bit 8
0
$01FF
Bit 6
0
0
(6)$0200
(6)$0201
(6)$0202
(6)$0203
CSWAI
0
SYNCH TLNKEN SLPAK
SLPRQ SFTRES
0
0
0
0
LOOPB
BRP2
WUPM CLKSRC C2MCR1
SJW1
SAMP
SJW0
BRP5
BRP4
BRP3
BRP1
BRP0
C2BTR0
C2BTR1
C2RFLG
C2RIER
C2TFLG
C2TCR
TSEG22 TSEG21 TSEG20 TSEG13 TSEG12 TSEG11 TSEG10
(6)$0204 WUPIF RWRNIF TWRNIF RERRIF TERRIF BOFFIF
(6)$0205 WUPIE RWRNIE TWRNIE RERRIE TERRIE BOFFIE
(6)$0206
(6)$0207
(6)$0208
OVRIF
OVRIE
TXE1
RXF
RXFIE
TXE0
0
0
0
ABTAK2 ABTAK1 ABTAK0
ABTRQ2 ABTRQ1 ABTRQ0
0
0
0
TXE2
TXEIE2
IDHIT2
TXEIE1
IDHIT1
TXEIE0
IDHIT0
0
IDAM1
IDAM0
C2IDAC
$0209–
$020D
Unimplemented(4)
Reserved
(6)$020E RXERR7 RXERR6 RXERR5 RXERR4 RXERR3 RXERR2 RXERR1 RXERR0 C2RXERR
(6)$020F TXERR7 TXERR6 TXERR5 TXERR4 TXERR3 TXERR2 TXERR1 TXERR0 C2TXERR
(6)$0210
(6)$0211
(6)$0212
(6)$0213
(6)$0214
(6)$0215
(6)$0216
(6)$0217
(6)$0218
(6)$0219
(6)$021A
(6)$021B
(6)$021C
(6)$021D
(6)$021E
(6)$021F
AC7
AC7
AC7
AC7
AM7
AM7
AM7
AM7
AC7
AC7
AC7
AC7
AM7
AM7
AM7
AM7
AC6
AC6
AC6
AC6
AM6
AM6
AM6
AM6
AC6
AC6
AC6
AC6
AM6
AM6
AM6
AM6
AC5
AC5
AC5
AC5
AM5
AM5
AM5
AM5
AC5
AC5
AC5
AC5
AM5
AM5
AM5
AM5
AC4
AC4
AC4
AC4
AM4
AM4
AM4
AM4
AC4
AC4
AC4
AC4
AM4
AM4
AM4
AM4
AC3
AC3
AC3
AC3
AM3
AM3
AM3
AM3
AC3
AC3
AC3
AC3
AM3
AM3
AM3
AM3
AC2
AC2
AC2
AC2
AM2
AM2
AM2
AM2
AC2
AC2
AC2
AC2
AM2
AM2
AM2
AM2
AC1
AC1
AC1
AC1
AM1
AM1
AM1
AM1
AC1
AC1
AC1
AC1
AM1
AM1
AM1
AM1
AC0
AC0
AC0
AC0
AM0
AM0
AM0
AM0
AC0
AC0
AC0
AC0
AM0
AM0
AM0
AM0
C2IDAR0
C2IDAR1
C2IDAR2
C2IDAR3
C2IDMR0
C2IDMR1
C2IDMR2
C2IDMR3
C2IDAR4
C2IDAR5
C2IDAR6
C2IDAR7
C2IDMR4
C2IDMR5
C2IDMR6
C2IDMR7
$0220–
$023C
(6)$023D
(6)$023E PCAN7
Unimplemented(4)
Reserved
0
0
0
0
0
0
PUPCAN RDPCAN PCTLCAN2
PCAN6
PCAN5
PCAN4
PCAN3
PCAN2
TxCAN
0
RxCAN PORTCAN2
(6)$023F DDCAN7 DDCAN6 DDCAN5 DDCAN4 DDCAN3 DDCAN2
0
DDRCAN2
(6)$0240
– $024F
(6)$0250
FOREGROUND RECEIVE BUFFER 2
RxFG2
TRANSMIT BUFFER 20
– $025F
Tx20
9-reg
MC68HC912DT128A Rev 2.0
59
MOTOROLA
Registers
Re g iste rs
Table 8 MC68HC912DT128A Register Map (Sheet 10 of 11)
Address
Bit 7
6
5
4
3
2
1
Bit 0
Name
Tx21
(6)$0260
TRANSMIT BUFFER 21
TRANSMIT BUFFER 22
Unimplemented(4)
– $026F
(6)$0270
– $027F
Tx22
$0280-
$02FF
Reserved
C1MCR0
$0300
$0301
0
0
0
0
CSWAI
0
SYNCH TLNKEN SLPAK
SLPRQ SFTRES
0
0
LOOPB
BRP2
WUPM CLKSRC C1MCR1
$0302
$0303
$0304
$0305
$0306
$0307
$0308
SJW1
SAMP
SJW0
BRP5
BRP4
BRP3
BRP1
BRP0
C1BTR0
C1BTR1
C1RFLG
C1RIER
C1TFLG
C1TCR
TSEG22 TSEG21 TSEG20 TSEG13 TSEG12 TSEG11 TSEG10
WUPIF RWRNIF TWRNIF RERRIF TERRIF BOFFIF
WUPIE RWRNIE TWRNIE RERRIE TERRIE BOFFIE
OVRIF
OVRIE
TXE1
RXF
RXFIE
TXE0
0
0
0
ABTAK2 ABTAK1 ABTAK0
ABTRQ2 ABTRQ1 ABTRQ0
0
0
0
TXE2
TXEIE2
IDHIT2
TXEIE1
IDHIT1
TXEIE0
IDHIT0
0
IDAM1
IDAM0
C1IDAC
$0309–
$030D
Unimplemented(4)
Reserved
$030E RXERR7 RXERR6 RXERR5 RXERR4 RXERR3 RXERR2 RXERR1 RXERR0 C1RXERR
$030F TXERR7 TXERR6 TXERR5 TXERR4 TXERR3 TXERR2 TXERR1 TXERR0 C1TXERR
$0310
$0311
$0312
$0313
$0314
$0315
$0316
$0317
$0318
$0319
$031A
$031B
$031C
$031D
$031E
$031F
AC7
AC7
AC7
AC7
AM7
AM7
AM7
AM7
AC7
AC7
AC7
AC7
AM7
AM7
AM7
AM7
AC6
AC6
AC6
AC6
AM6
AM6
AM6
AM6
AC6
AC6
AC6
AC6
AM6
AM6
AM6
AM6
AC5
AC5
AC5
AC5
AM5
AM5
AM5
AM5
AC5
AC5
AC5
AC5
AM5
AM5
AM5
AM5
AC4
AC4
AC4
AC4
AM4
AM4
AM4
AM4
AC4
AC4
AC4
AC4
AM4
AM4
AM4
AM4
AC3
AC3
AC3
AC3
AM3
AM3
AM3
AM3
AC3
AC3
AC3
AC3
AM3
AM3
AM3
AM3
AC2
AC2
AC2
AC2
AM2
AM2
AM2
AM2
AC2
AC2
AC2
AC2
AM2
AM2
AM2
AM2
AC1
AC1
AC1
AC1
AM1
AM1
AM1
AM1
AC1
AC1
AC1
AC1
AM1
AM1
AM1
AM1
AC0
AC0
AC0
AC0
AM0
AM0
AM0
AM0
AC0
AC0
AC0
AC0
AM0
AM0
AM0
AM0
C1IDAR0
C1IDAR1
C1IDAR2
C1IDAR3
C1IDMR0
C1IDMR1
C1IDMR2
C1IDMR3
C1IDAR4
C1IDAR5
C1IDAR6
C1IDAR7
C1IDMR4
C1IDMR5
C1IDMR6
C1IDMR7
$0320–
$033C
Unimplemented(4)
Reserved
$033D
$033E
0
0
0
0
0
0
PUPCAN RDPCAN PCTLCAN1
PCAN7
PCAN6
PCAN5
PCAN4
PCAN3
PCAN2
TxCAN
0
RxCAN PORTCAN1
$033F DDCAN7 DDCAN6 DDCAN5 DDCAN4 DDCAN3 DDCAN2
0
DDRCAN1
$0340–
FOREGROUND RECEIVE BUFFER 1
$034F
RxFG1
10-reg
MC68HC912DT128A Rev 2.0
60
Registers
MOTOROLA
Registers
Register Block
Table 8 MC68HC912DT128A Register Map (Sheet 11 of 11)
Address
Bit 7
6
5
4
3
2
1
Bit 0
Name
Tx10
$0350–
$035F
TRANSMIT BUFFER 10
TRANSMIT BUFFER 11
TRANSMIT BUFFER 12
Unimplemented(4)
$0360–
$036F
Tx11
Tx12
$0370–
$037F
$0380-$
03FF
Reserved
= Reserved or unimplemented bits.
1. Port A, port B and data direction registers DDRA, DDRB are not in map in expanded and peripheral modes.
2. Port E and DDRE not in the map in peripheral and expanded modes with EME set.
3. Registers also not in map in peripheral mode.
4. Data read at these locations is undefined.
5. Port K and DDRK not in the map in peripheral and expanded modes with EMK set.
6. MC68HC912DT128A only. Locations are unimplemented on the MC68HC912DG128A.
11-reg
MC68HC912DT128A Rev 2.0
61
MOTOROLA
Registers
Re g iste rs
12-reg
MC68HC912DT128A Rev 2.0
62
Registers
MOTOROLA
Op e ra ting Mod e s
Op e ra ting Mod e s
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Operating Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Background Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Introd uc tion
Eight possible operating modes determine the operating configuration of
the MC68HC912DT128A. Each mode has an associated default
memory map and external bus configuration.
Op e ra ting Mod e s
The operating mode out of reset is determined by the states of the
BKGD, MODB, and MODA pins during reset.
The SMODN, MODB, and MODA bits in the MODE register show current
operating mode and provide limited mode switching during operation.
The states of the BKGD, MODB, and MODA pins are latched into these
bits on the rising edge of the reset signal.
Table 9 Mode Selection
BKGD MODB
MODA
Mode
Port A
G.P. I/O
Port B
G.P. I/O
ADDR
1
1
1
1
0
0
0
0
1
1
0
0
0
1
0
1
0
1
Normal Single Chip
Normal Expanded Narrow
Reserved (Forced to Peripheral)
Normal Expanded Wide
Special Single Chip
ADDR/DATA
—
—
ADDR/DATA
G.P. I/O
ADDR/DATA
G.P. I/O
ADDR
Special Expanded Narrow
ADDR/DATA
1-modes
MC68HC912DT128A Rev 2.0
63
MOTOROLA
Operating Modes
Op e ra ting Mod e s
Table 9 Mode Selection
BKGD MODB
MODA
Mode
Port A
Port B
0
0
1
1
0
1
Special Peripheral
Special Expanded Wide
ADDR/DATA
ADDR/DATA
ADDR/DATA
ADDR/DATA
There are two basic types of operating modes:
Normal modes — some registers and bits are protected
against accidental changes.
Special modes — allow greater access to protected control
registers and bits for special purposes such as testing and
emulation.
A system development and debug feature, background debug mode
(BDM), is available in all modes. In special single-chip mode, BDM is
active immediately after reset.
Norm a l Op e ra ting
Mod e s
These modes provide three operating configurations. Background
debug is available in all three modes, but must first be enabled for some
operations by means of a BDM background command, then activated.
Normal Single-Chip Mode — There are no external address and
data buses in this mode. The MCU operates as a stand-alone
device and all program and data resources are on-chip. External
port pins normally associated with address and data buses can be
used for general-purpose I/O.
Normal Expanded Wide Mode — This is a normal mode of
operation in which the expanded bus is present with a 16-bit data
bus. Ports A and B are used for the 16-bit multiplexed
address/data bus.
Normal Expanded Narrow Mode — This is a normal mode of
operation in which the expanded bus is present with an 8-bit data
bus. Ports A and B are used for the16-bit address bus. Port A is
used as the data bus, multiplexed with addresses. In this mode,
16-bit data is presented one byte at a time, the high byte followed
by the low byte. The address is automatically incremented on the
second cycle.
2--modes
MC68HC912DT128A Rev 2.0
64
Operating Modes
MOTOROLA
Operating Modes
Operating Modes
Sp e c ia l Op e ra ting
Mod e s
There are three special operating modes that correspond to normal
operating modes. These operating modes are commonly used in factory
testing and system development. In addition, there is a special
peripheral mode, in which an external master, such as an I.C. tester, can
control the on-chip peripherals.
Special Single-Chip Mode — This mode can be used to force the
MCU to active BDM mode to allow system debug through the
BKGD pin. There are no external address and data buses in this
mode. The MCU operates as a stand-alone device and all
program and data space are on-chip. External port pins can be
used for general-purpose I/O.
Special Expanded Wide Mode — This mode can be used for
emulation of normal expanded wide mode and emulation of
normal single-chip mode. Ports A and B are used for the 16-bit
multiplexed address/data bus.
Special Expanded Narrow Mode — This mode can be used for
emulation of normal expanded narrow mode. Ports A and B are
used for the16-bit address bus. Port A is used as the data bus,
multiplexed with addresses. In this mode, 16-bit data is presented
one byte at a time, the high byte followed by the low byte. The
address is automatically incremented on the second cycle.
Special Peripheral Mode — The CPU is not active in this mode.
An external master can control on-chip peripherals for testing
purposes. It is not possible to change to or from this mode without
going through reset. Background debugging should not be used
while the MCU is in special peripheral mode as internal bus
conflicts between BDM and the external master can cause
improper operation of both functions.
MODE — Mode Register
$000B
Bit 7
6
5
4
3
IVIS
1
2
1
EMK
1
Bit 0
EME
1
SMODN
MODB
MODA
ESTR
EBSWAI
RESET:
RESET:
RESET:
0
0
0
0
0
1
0
1
0
1
1
1
0
0
0
Special Single Chip
Special Exp Nar
Peripheral
1
1
1
1
1
1
3-modes
MC68HC912DT128A Rev 2.0
65
MOTOROLA
Operating Modes
Op e ra ting Mod e s
MODE — Mode Register
$000B
RESET:
RESET:
RESET:
RESET:
0
1
1
1
1
0
0
1
1
0
1
1
1
1
1
1
1
0
0
0
0
0
0
0
1
0
0
0
1
0
0
0
Special Exp Wide
Normal Single Chip
Normal Exp Nar
Normal Exp Wide
The MODE register controls the MCU operating mode and various
configuration options. This register is not in the map in peripheral mode
SMODN, MODB, MODA — Mode Select Special, B and A
These bits show the current operating mode and reflect the status of
the BKGD, MODB and MODA input pins at the rising edge of reset.
Read anytime.
SMODN may only be written if SMODN = 0 (in special modes) but the
first write is ignored.
MODB, MODA may be written once if SMODN = 1; anytime if SMODN
= 0 but the first write is ignored and in special peripheral and reserved
modes cannot be selected.
ESTR — E Clock Stretch Enable
Determines if the E Clock behaves as a simple free-running clock or
as a bus control signal that is active only for external bus cycles.
ESTR is always one in expanded modes since it is required for
address and data de-multiplexing and must follow stretched cycles.
0 = E never stretches (always free running).
1 = E stretches high during external access cycles and low during
non-visible internal accesses (IVIS = 0).
Normal modes: write once; Special modes: write anytime, read
anytime.
IVIS — Internal Visibility
This bit determines whether internal ADDR, DATA, R/W and LSTRB
signals can be seen on the external bus during accesses to internal
locations. In Special Narrow Mode if this bit is set and an internal
access occurs the data will appear wide on Ports A and B. This serves
4-modes
MC68HC912DT128A Rev 2.0
66
Operating Modes
MOTOROLA
Operating Modes
Operating Modes
the same function as the EMD bit of the non-multiplexed versions of
the HC12 and allows for emulation. Visibility is not available when the
part is operating in a single-chip mode.
0 = No visibility of internal bus operations on external bus.
1 = Internal bus operations are visible on external bus.
Normal modes: write once; Special modes: write anytime EXCEPT
the first time. Read anytime.
EBSWAI — Multiplexed External Bus Interface Module Stops in Wait
Mode
This bit controls access to the multiplexed external bus interface
module during wait mode. The module will delay before shutting down
in wait mode to allow for final bus activity to complete.
0 = MEBI continues functioning during wait mode.
1 = MEBI is shut down during wait mode.
Normal modes: write anytime; special modes: write never. Read
anytime.
EMK — Emulate Port K
In single-chip mode PORTK and DDRK are always in the map
regardless of the state of this bit.
0 = Port K and DDRK registers are in the memory map. Memory
expansion emulation is disabled and all pins are general
purpose I/O.
1 = In expanded or peripheral mode, PORTK and DDRK are
removed from the internal memory map. Removing the
registers from the map allows the user to emulate the function
of these registers externally.
Normal modes: write once; special modes: write anytime EXCEPT
the first time. Read anytime.
EME — Emulate Port E
In single-chip mode PORTE and DDRE are always in the map
regardless of the state of this bit.
0 = PORTE and DDRE are in the memory map.
5-modes
MC68HC912DT128A Rev 2.0
MOTOROLA
Operating Modes
67
Op e ra ting Mod e s
1 = If in an expanded mode, PORTE and DDRE are removed from
the internal memory map. Removing the registers from the
map allows the user to emulate the function of these registers
externally.
Normal modes: write once; special modes: write anytime EXCEPT
the first time. Read anytime.
Ba c kg round De b ug Mod e
Background debug mode (BDM) is an auxiliary operating mode that is
used for system development. BDM is implemented in on-chip hardware
and provides a full set of debug operations. Some BDM commands can
be executed while the CPU is operating normally. Other BDM
commands are firmware based, and require the BDM firmware to be
enabled and active for execution.
In special single-chip mode, BDM is enabled and active immediately out
of reset. BDM is available in all other operating modes, but must be
enabled before it can be activated. BDM should not be used in special
peripheral mode because of potential bus conflicts.
Once enabled, background mode can be made active by a serial
command sent via the BKGD pin or execution of a CPU12 BGND
instruction. While background mode is active, the CPU can interpret
special debugging commands, and read and write CPU registers,
peripheral registers, and locations in memory.
While BDM is active, the CPU executes code located in a small on-chip
ROM mapped to addresses $FF20 to $FFFF, and BDM control registers
are accessible at addresses $FF00 to $FF06. The BDM ROM replaces
the regular system vectors while BDM is active. While BDM is active, the
user memory from $FF00 to $FFFF is not in the map except through
serial BDM commands.
6-modes
MC68HC912DT128A Rev 2.0
68
Operating Modes
MOTOROLA
Re sourc e Ma p p ing
Re sourc e Ma p p ing
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Internal Resource Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Flash EEPROM mapping through internal Memory Expansion . . . . . 72
Miscellaneous System Control Register . . . . . . . . . . . . . . . . . . . . . . . 77
Mapping test registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Memory Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Introd uc tion
After reset, most system resources can be mapped to other addresses
by writing to the appropriate control registers.
Inte rna l Re sourc e Ma p p ing
The internal register block, RAM, and EEPROM have default locations
within the 64K byte standard address space but may be reassigned to
other locations during program execution by setting bits in mapping
registers INITRG, INITRM, and INITEE. During normal operating modes
these registers can be written once. It is advisable to explicitly establish
these resource locations during the initialization phase of program
execution, even if default values are chosen, in order to protect the
registers from inadvertent modification later.
Writes to the mapping registers go into effect between the cycle that
follows the write and the cycle after that. To assure that there are no
unintended operations, a write to one of these registers should be
followed with a NOP instruction.
1-mapping
MC68HC912DT128A Rev 2.0
MOTOROLA
Resource Mapping
69
Re sourc e Ma p p ing
If conflicts occur when mapping resources, the register block will take
precedence over the other resources; RAM or EEPROM addresses
occupied by the register block will not be available for storage. When
active, BDM ROM takes precedence over other resources, although a
conflict between BDM ROM and register space is not possible. The
following table shows resource mapping precedence.
Table 10 Mapping Precedence
Precedence
Resource
BDM ROM (if active)
Register Space
RAM
1
2
3
4
5
6
EEPROM
On-Chip Flash EEPROM
External Memory
In expanded modes, all address space not used by internal resources is
by default external memory.
The MC68HC912DT128A contains 128K bytes of Flash EEPROM
nonvolatile memory which can be used to store program code or static
data. This physical memory is composed of four 32k byte array modules,
00FEE32K, 01FEE32K, 10FEE32K and 11FEE32K. The 32K byte array
11FEE32K has a fixed location from $4000 to $7FFF and $C000 to
$FFFF. The three 32K byte arrays 00FEE32K, 01FEE32K and
10FEE32K are accessible through a 16K byte program page window
mapped from $8000 to $BFFF. The fixed 32K byte array 11FEE32K can
also be accessed through the program page window.
Re g iste r Bloc k
Ma p p ing
After reset the 1K byte register block resides at location $0000 but can
be reassigned to any 2K byte boundary within the standard 64K byte
address space. Mapping of internal registers is controlled by five bits in
the INITRG register. The register block occupies the first 1K byte of the
2K byte block.
2--mapping
MC68HC912DT128A Rev 2.0
70
Resource Mapping
MOTOROLA
Resource Mapping
Internal Resource Mapping
INITRG — Initialization of Internal Register Position Register
$0011
Bit 7
REG15
0
6
REG14
0
5
REG13
0
4
REG12
0
3
REG11
0
2
0
0
1
0
0
Bit 0
MMSWAI
0
RESET:
REG[15:11] — Internal register map position
These bits specify the upper five bits of the 16-bit registers address.
Normal modes: write once; special modes: write anytime. Read
anytime.
MMSWAI — Memory Mapping Interface Stop in Wait Control
This bit controls access to the memory mapping interface when in
Wait mode.
Normal modes: write anytime; special modes: write never. Read
anytime.
0 = Memory mapping interface continues to function during Wait
mode.
1 = Memory mapping interface access is shut down during Wait
mode.
RAM Ma p p ing
The MC68HC912DT128A has 8K bytes of fully static RAM that is used
for storing instructions, variables, and temporary data during program
execution. Since the RAM is actually implemented with two 4K RAM
arrays, any misaligned word access between last address of first 4K
RAM and first address of second 4K RAM will take two cycles instead of
one. After reset, RAM addressing begins at location $2000 but can be
assigned to any 8K byte boundary within the standard 64K byte address
space. Mapping of internal RAM is controlled by three bits in the INITRM
register.
INITRM — Initialization of Internal RAM Position Register
$0010
Bit 7
RAM15
0
6
RAM14
0
5
RAM13
1
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
0
0
RESET:
3-mapping
MC68HC912DT128A Rev 2.0
71
MOTOROLA
Resource Mapping
Re sourc e Ma p p ing
RAM[15:13] — Internal RAM map position
These bits specify the upper three bits of the 16-bit RAM address.
Normal modes: write once; special modes: write anytime. Read
anytime.
EEPROM Ma p p ing
The MC68HC912DT128A has 2K bytes of EEPROM which is activated
by the EEON bit in the INITEE register. Mapping of internal EEPROM is
controlled by four bits in the INITEE register. After reset EEPROM
address space begins at location $0800 but can be mapped to any 4K
byte boundary within the standard 64K byte address space. The
EEPROM block occupies the last 2K bytes of the 4K byte block.
INITEE— Initialization of Internal EEPROM Position Register
$0012
Bit 7
EE15
0
6
EE14
0
5
EE13
0
4
EE12
0
3
0
0
2
0
0
1
0
0
Bit 0
EEON
1
RESET:
EE[15:12] — Internal EEPROM map position
These bits specify the upper four bits of the 16-bit EEPROM address.
Normal modes: write once; special modes: write anytime. Read
anytime.
EEON — internal EEPROM On (Enabled)
Read or write anytime.
0 = Removes the EEPROM from the map.
1 = Places the on-chip EEPROM in the memory map at the
address selected by EE[15:12].
Fla sh EEPROM m a p p ing throug h inte rna l Me m ory Exp a nsion
The Page Index register or PPAGE provides memory management for
the MC68HC912DT128A. PPAGE consists of three bits to indicate
which physical location is active within the windows of the
MC68HC912DT128A. The MC68HC912DT128A has a user’s program
4-mapping
MC68HC912DT128A Rev 2.0
72
Resource Mapping
MOTOROLA
Resource Mapping
Flash EEPROM mapping through internal Memory Expansion
space window, a register space window for Flash module registers, and
a test program space window.
The user’s program page window consists of 16K Flash EEPROM bytes.
One of eight pages is viewed through this window for a total of 128K
accessible Flash EEPROM bytes.
The register space window consists of a 4-byte register block. One of
four pages is viewed through this window for each of the 32K flash
module register blocks of MC68HC912DT128A.
The test mode program page window consists of 32K Flash EEPROM
bytes. One of the four 32K byte arrays is viewed through this window for
a total 128K accessible Flash EEPROM bytes. This window is only
available in special mode for test purposes and replaces the user’s
program page window.
MC68HC912DT128A has a five pin port, port K, for emulation and for
general purpose I/O. Three pins are used to emulate the three page
indices (PPAGE bits) and one pin is used as an emulation chip select.
When these four pins are not used for emulation they serve as general
purpose I/O pins. The fifth port K pin is used as a general purpose I/O
pin.
Prog ra m spa c e
e xp a nsion
There are 128K bytes of Flash EEPROM for MC68HC912DT128A. With
a 64K byte address space, the PPAGE register is needed to perform on
chip memory expansion. A program space window of 16K byte pages is
located from $8000 to $BFFF. Three page indices are used to point to
one of eight different 16K byte pages.
Table 11 Program space Page Index
Page Index 2 Page Index 1 Page Index 0
(PPAGE bit 2) (PPAGE bit 1) (PPAGE bit 0)
16K Program space Page
Flash array
0
0
0
0
1
1
0
0
1
1
0
0
0
1
0
1
0
1
16K byte Page 0
16K byte Page 1
16K byte Page 2
16K byte Page 3
16K byte Page 4
16K byte Page 5
00FEE32K
00FEE32K
01FEE32K
01FEE32K
10FEE32K
10FEE32K
5-mapping
MC68HC912DT128A Rev 2.0
73
MOTOROLA
Resource Mapping
Re sourc e Ma p p ing
Table 11 Program space Page Index
Page Index 2 Page Index 1 Page Index 0
(PPAGE bit 2) (PPAGE bit 1) (PPAGE bit 0)
16K Program space Page
Flash array
1
1
1
1
0
1
16K byte Page 6*
16K byte Page 7*
11FEE32K
11FEE32K
* The 16K byte flash in program space page 6 can also be accessed at
a fixed location from $4000 to $7FFF. The 16K byte flash in program
space page 7 can also be accessed at a fixed location from $C000 to
$FFFF.
Fla sh re g iste r
sp a c e e xp a nsion
There are four 32K Flash arrays for MC68HC912DT128A and each
requires a 4-byte register block. A register space window is used to
access one of the four 4-byte blocks and the PPAGE register to map
each one into the window. The register space window is located from
$00F4 to $00F7 after reset. Only two page indices are used to point to
one of the four pages of the register space.
Table 12 Flash Register space Page Index
Page Index 2
(PPAGE bit
2)
Page Index 1 Page Index 0
(PPAGE bit 1) (PPAGE bit 0)
Flash register space Page
Flash array
0
0
1
1
0
1
0
1
X
X
X
X
$00F4-$00F7 Page 0
$00F4-$00F7 Page 1
$00F4-$00F7 Page 2
$00F4-$00F7 Page 3
00FEE32K
01FEE32K
10FEE32K
11FEE32K
Te st m od e
Prog ra m spa c e
e xp a nsion
In special mode and for test purposes only, the 128K bytes of Flash
EEPROM for MC68HC912DT128A can be accessed through a test
program space window of 32K bytes. This window replaces the user’s
program space window to be able to access an entire array. In special
mode and with ROMTST bit set in MISC register, a program space is
located from $8000 to $FFFF. Only two page indices are used to point
to one of the four 32K byte arrays. These indices can be viewed as
expanded addresses X16 and X15.
6-mapping
MC68HC912DT128A Rev 2.0
74
Resource Mapping
MOTOROLA
Resource Mapping
Flash EEPROM mapping through internal Memory Expansion
Table 13 Test mode program space Page Index
Page Index 2 Page Index 1 Page Index 0
(PPAGE bit 2) (PPAGE bit 1) (PPAGE bit 0)
Flash register space Page
Flash array
0
0
1
1
0
1
0
1
X
X
X
X
32K byte array Page 0
32K byte array Page 1
32K byte array Page 2
32K byte array Page 3
00FEE32K
01FEE32K
10FEE32K
11FEE32K
Pa g e Ind e x
re g iste r
d e sc rip tions
PORTK — Port K Data Register
$00FC
Bit 7
PK7
ECS
-
6
0
0
0
5
0
0
0
4
0
0
0
3
2
PK2
PIX2
-
1
PK1
PIX1
-
Bit 0
PK0
PIX0
-
PORT
Emulation
RESET:
PK3
-
-
Read and write anytime
Writes do not change pin state when pin configured for page index
emulation output.
This port is associated with page index emulation pins. When the port is
not enabled to emulate page index, the port pins are used as
general-purpose I/O. Port K bit 3 is used as a general purpose I/O pin
only. This register is not in the map in peripheral or expanded modes
while the EMK control bit in MODE register is set.
When inputs, these pins can be selected to be high impedance or pulled
up.
ECS — Emulation Chip Select of selected program space
When this signal is active low it indicates that the program space is
accessed. This also applies to test mode program space. An access
is made if address is at the program space window and either the
Flash or external memory is accessed. The ECS timing is E clock high
7-mapping
MC68HC912DT128A Rev 2.0
MOTOROLA
Resource Mapping
75
Re sourc e Ma p p ing
and can be stretched when accessing external memory depending on
the EXTR0 and EXTR1 bits in the MISC register. The ECS signal is
only active when the EMK bit is set.
PIX[2:0] — The content of the PPAGE register emulated externally.
This content indicates which Flash module register space is in the
memory map and which 16K byte Flash memory is in the program
space. In special mode and with ROMTST bit set, the content of the
Page Index register indicates which 32K byte Flash array is in the test
program space.
I
DDRK — Port K Data Direction Register
$00FD
Bit 7
DDK7
0
6
0
0
5
0
0
4
0
0
3
DDK3
0
2
DDK2
0
1
DDK1
0
Bit 0
DDK0
0
RESET:
Read and write: anytime.
This register determines the primary direction for each port K pin
configured as general-purpose I/O.
0 = Associated pin is a high-impedance input.
1 = Associated pin is an output.
This register is not in the map in peripheral or expanded modes while the
EMK control bit is set.
PPAGE — (Program) Page Index Register
$00FF
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
PIX2
0
1
PIX1
0
Bit 0
PIX0
0
0
0
RESET:
Read and write: anytime.
This register determines the active page viewed through
MC68HC912DT128A windows.
8-mapping
MC68HC912DT128A Rev 2.0
76
Resource Mapping
MOTOROLA
Resource Mapping
Miscellaneous System Control Register
CALL and RTC instructions have a special single wire mechanism to
read and write this register without using an address bus.
Misc e lla ne ous Syste m Control Re g iste r
Additional mapping and external resource controls are available. To use
external resources the part must be operated in one of the expanded
modes.
MISC — Miscellaneous Mapping Control Register
$0013
Mode
Bit 7
ROMTST
0
6
NDRF
0
5
RFSTR1
0
4
RFSTR0
0
3
EXSTR1
1
2
EXSTR0
1
1
ROMHM
0
Bit 0
ROMON
0
RESET:
RESET:
Exp mode
peripheral or
SC mode
0
0
0
0
1
1
0
1
Normal modes: write once; Special modes: write anytime. Read
anytime.
ROMTST — FLASH EEPROM Test mode
In normal modes, this bit is forced to zero.
0 = 16K window for Flash memory is located from $8000-$BFFF
1 = 32K window for Flash memory is located from $8000-$FFFF
NDRF — Narrow Data Bus for Register-Following Map Space
This bit enables a narrow bus feature for the 1K byte
Register-Following Map. This is useful for accessing 8-bit peripherals
and allows 8-bit and 16-bit external memory devices to be mixed in a
system. In Expanded Narrow (eight bit) modes, Single Chip Modes,
and Peripheral mode, this bit has no effect.
0 = Makes Register-Following MAP space act as a full 16 bit data
bus.
1 = Makes the Register-Following MAP space act the same as an
8 bit only external data bus (data only goes through port A
externally).
9-mapping
MC68HC912DT128A Rev 2.0
MOTOROLA
Resource Mapping
77
Re sourc e Ma p p ing
The Register-Following space is mapped from $0400 to $07FF after
reset, which is next to the register map. If the registers are moved this
space follows.
RFSTR1, RFSTR0 — Register Following Stretch
This two bit field determines the amount of clock stretch on accesses
to the 1K byte Register Following Map. It is valid regardless of the
state of the NDRF bit. In Single Chip and Peripheral Modes this bit
has no meaning or effect.
Table 14 RFSTR Stretch Bit Definition
Number of E Clocks
RFSTR1
RFSTR0
Stretched
0
0
1
1
0
1
0
1
0
1
2
3
EXSTR1, EXSTR0 — External Access Stretch
This two bit field determines the amount of clock stretch on accesses
to an external address space. In Single Chip and Peripheral Modes
this bit has no meaning or effect.
Table 15 EXSTR Stretch Bit Definition
Number of E Clocks
EXSTR1
EXSTR0
Stretched
0
0
1
1
0
1
0
1
0
1
2
3
ROMHM — Flash EEPROM only in second Half of Map
This bit has no meaning if ROMON bit is clear.
0 = The 16K byte of fixed Flash EEPROM in location $4000-$7FFF
can be accessed.
10-mapping
MC68HC912DT128A Rev 2.0
78
Resource Mapping
MOTOROLA
Resource Mapping
Mapping test registers
1 = Disables direct access to 16K byte Flash EEPROM from
$4000-$7FFF in the memory map. The physical location of
this16K byte Flash can still be accessed through the Program
Page window.
In special mode and with ROMTST bit set, this bit will allow overlap of
the four 32K Flash arrays and overlap the four 4-byte Flash register
space in the same map space to be able to program all arrays at the
same time.
0 = The four 32K Flash arrays are accessed with four pages for
each.
1 = The four 32K Flash arrays coincide in the same space and are
selected at the same time for programming.
CAUTION: Bit must be cleared before reading any of the arrays or registers.
ROMON — Enable Flash EEPROM
These bits are used to enable the Flash EEPROM arrays.
0 = Disables Flash EEPROM in the memory map.
1 = Enables Flash EEPROM in the memory map.
Ma p p ing te st re g iste rs
These registers are used in for testing the mapping logic. They can only
be read and after each read they get cleared. A write to each register will
have no effect.
MTST0 — Mapping Test Register 0
$00F8
$00F9
Bit 7
MT07
0
6
MT06
0
5
MT05
0
4
MT04
0
3
MT03
0
2
MT02
0
1
MT01
0
Bit 0
MT00
0
RESET:
MTST1 — Mapping Test Register 1
Bit 7
MT0F
0
6
MT0E
0
5
MT0D
0
4
MT0C
0
3
MT0B
0
2
MT0A
0
1
MT09
0
Bit 0
MT08
0
RESET:
11-mapping
MC68HC912DT128A Rev 2.0
79
MOTOROLA
Resource Mapping
Re sourc e Ma p p ing
MTST2 — Mapping Test Register 2
$00FA
$00FB
Bit 7
MT17
0
6
MT16
0
5
MT15
0
4
MT14
0
3
MT13
0
2
MT12
0
1
MT11
0
Bit 0
MT10
0
RESET:
MTST3 — Mapping Test Register 3
Bit 7
MT1F
0
6
MT1E
0
5
MT1D
0
4
MT1C
0
3
MT1B
0
2
MT1A
0
1
MT19
0
Bit 0
MT18
0
RESET:
Me m ory Ma p s
The following diagrams illustrate the memory map for each mode of
operation immediately after reset.
12-mapping
MC68HC912DT128A Rev 2.0
80
Resource Mapping
MOTOROLA
Resource Mapping
Memory Maps
$0000
$03FF
REGISTERS
(MAPPABLE TO ANY 2K SPACE)
$0000
$0400
$0800
$0FFF
2K bytes EEPROM
(MAPPABLE TO ANY 4K SPACE)
$0800
$1000
$2000
$2000
$3FFF
8K bytes RAM
(MAPPABLE TO ANY 8K SPACE)
$4000
$4000
16K Fixed Flash EEPROM
$8000
$8000
$C000
16K Page Window
Eight 16K Flash EEPROM pages
EXT
$A000 - $BFFF Protected BOOT
at odd programing pages
$BFFF
$C000
16K Fixed Flash EEPROM
$E000 - $FFFF Protected BOOT
$FFFF
$FF00
$FFFF
BDM
(if active)
$FF00
$FFFF
VECTORS
VECTORS
VECTORS
NORMAL
EXPANDED
SPECIAL
SINGLE CHIP
SINGLE CHIP
Figure 10 MC68HC912DT128A Memory Map after reset
The following diagram illustrates the memory paging scheme.
13-mapping
MC68HC912DT128A Rev 2.0
81
MOTOROLA
Resource Mapping
Re sourc e Ma p p ing
$0000
$0400
$0800
$1000
$2000
$4000
6
16K Flash
(Unpaged)
One 16K Page accessible at a time (selected by PPAGE value = 0 to 7)
00 Flash 32K
01 Flash 32K
10 Flash 32K
11 Flash 32K *
$8000
0
1
2
3
4
5
6
7
16K Flash
(Paged)
(8K Boot)
(8K Boot)
(8K Boot)
(8K Boot)
$C000
7
* This 32K Flash
accessible as
pages 6 & 7 and
as unpaged
$4000 - $7FFF &
$C000 - $FFFF
16K Flash
$E000
(Unpaged)
(8K Boot)
$FF00
VECTORS
$FFFF
NORMAL
SINGLE CHIP
Figure 11 MC68HC912DT128A Memory Paging
14-mapping
MC68HC912DT128A Rev 2.0
82
Resource Mapping
MOTOROLA
Bus Control a nd Inp ut/ Outp ut
Bus Control a nd Inp ut/ Outp ut
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Detecting Access Type from External Signals . . . . . . . . . . . . . . . . . . 83
Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Introd uc tion
Internally the MC68HC912DT128A has full 16-bit data paths, but
depending upon the operating mode and control registers, the external
multiplexed bus may be 8 or 16 bits. There are cases where 8-bit and
16-bit accesses can appear on adjacent cycles using the LSTRB signal
to indicate 8- or 16-bit data.
It is possible to have a mix of 8 and 16 bit peripherals attached to the
external multiplexed bus, using the NDRF bit in the MISC register while
in expanded wide modes.
De te c ting Ac c e ss Typ e from Exte rna l Sig na ls
The external signals LSTRB, R/W, and A0 can be used to determine the
type of bus access that is taking place. Accesses to the internal RAM
module are the only type of access that produce LSTRB = A0 = 1,
because the internal RAM is specifically designed to allow misaligned
16-bit accesses in a single cycle. In these cases the data for the address
that was accessed is on the low half of the data bus and the data for
address + 1 is on the high half of the data bus.
1-bus
MC68HC912DT128A Rev 2.0
MOTOROLA
Bus Control and Input/Output
83
Bus Control a nd Inp ut/ Outp ut
Table 16 Access Type vs. Bus Control Pins
LSTRB
A0
0
R/W
Type of Access
1
0
1
0
0
1
1
0
0
1
8-bit read of an even address
8-bit read of an odd address
8-bit write of an even address
8-bit write of an odd address
16-bit read of an even address
1
0
1
0
16-bit read of an odd address
(low/high data swapped)
1
0
1
1
0
1
1
0
0
16-bit write to an even address
16-bit write to an odd address
(low/high data swapped)
Re g iste rs
Not all registers are visible in the MC68HC912DT128A memory map
under certain conditions. In special peripheral mode the first 16 registers
associated with bus expansion are removed from the memory map.
In expanded modes, some or all of port A, port B, and port E are used
for expansion buses and control signals. In order to allow emulation of
the single-chip functions of these ports, some of these registers must be
rebuilt in an external port replacement unit. In any expanded mode, port
A, and port B, are used for address and data lines so registers for these
ports, as well as the data direction registers for these ports, are removed
from the on-chip memory map and become external accesses.
In any expanded mode, port E pins may be needed for bus control (e.g.,
ECLK, R/W). To regain the single-chip functions of port E, the emulate
port E (EME) control bit in the MODE register may be set. In this special
case of expanded mode and EME set, PORTE and DDRE registers are
removed from the on-chip memory map and become external accesses
so port E may be rebuilt externally.
2--bus
MC68HC912DT128A Rev 2.0
84
Bus Control and Input/Output
MOTOROLA
Bus Control and Input/Output
Registers
PORTA — Port A Register
$0000
Bit 7
6
5
4
3
2
1
Bit 0
PA0
—
Single Chip
RESET:
PA7
PA6
—
PA5
—
PA4
—
PA3
—
PA2
—
PA1
—
—
Expanded
& Periph:
ADDR15/ ADDR14/ ADDR13/ ADDR12/ ADDR11/ ADDR10/
DATA15 DATA14 DATA13 DATA12 DATA11 DATA10
ADDR15/ ADDR14/ ADDR13/ ADDR12/ ADDR11/ ADDR10/
ADDR9/
DATA9
ADDR8/
DATA8
Expanded
narrow
ADDR9/
DATA9/
DATA1
ADDR8/
DATA8/
DATA0
DATA15/
DATA7
DATA14/
DATA6
DATA13/
DATA5
DATA12/
DATA4
DATA11/
DATA3
DATA10/
DATA2
Bits PA[7:0] are associated respectively with addresses ADDR[15:8],
DATA[15:8] and DATA[7:0], in narrow mode. When this port is not
used for external addresses such as in single-chip mode, these pins
can be used as general-purpose I/O. DDRA determines the primary
direction of each pin. This register is not in the on-chip map in
expanded and peripheral modes. Read and write anytime.
DDRA — Port A Data Direction Register
$0002
Bit 7
DDA7
0
6
DDA6
0
5
DDA5
0
4
DDA4
0
3
DDA3
0
2
DDA2
0
1
DDA1
0
Bit 0
DDA0
0
RESET:
This register determines the primary direction for each port A pin
when functioning as a general-purpose I/O port. DDRA is not in the
on-chip map in expanded and peripheral modes. Read and write
anytime.
0 = Associated pin is a high-impedance input
1 = Associated pin is an output
PORTB — Port B Register
$0001
Bit 7
6
5
4
3
2
1
Bit 0
PB0
—
Single Chip
RESET:
PB7
PB6
—
PB5
—
PB4
—
PB3
—
PB2
—
PB1
—
—
Expanded
& Periph:
ADDR7/
DATA7
ADDR6/
DATA6
ADDR5/
DATA5
ADDR4/
DATA4
ADDR3/
DATA3
ADDR2/
DATA2
ADDR1/
DATA1
ADDR0/
DATA0
Expanded
narrow
ADDR7
ADDR6
ADDR5
ADDR4
ADDR3
ADDR2
ADDR1
ADDR0
3-bus
MC68HC912DT128A Rev 2.0
85
MOTOROLA
Bus Control and Input/Output
Bus Control a nd Inp ut/ Outp ut
Bits PB[7:0] are associated with addresses ADDR[7:0] and DATA[7:0]
(except in narrow mode) respectively. When this port is not used for
external addresses such as in single-chip mode, these pins can be
used as general-purpose I/O. DDRB determines the primary direction
of each pin. This register is not in the on-chip map in expanded and
peripheral modes. Read and write anytime.
DDRB — Port B Data Direction Register
$0003
Bit 7
DDB7
0
6
DDB6
0
5
DDB5
0
4
DDB4
0
3
DDB3
0
2
DDB2
0
1
DDB1
0
Bit 0
DDB0
0
RESET:
This register determines the primary direction for each port B pin
when functioning as a general-purpose I/O port. DDRB is not in the
on-chip map in expanded and peripheral modes. Read and write
anytime.
0 = Associated pin is a high-impedance input
1 = Associated pin is an output
PORTE — Port E Register
$0008
BIT 7
PE7
6
5
4
3
2
1
BIT 0
PE0
—
PE6
—
PE5
—
PE4
—
PE3
—
PE2
—
PE1
—
RESET:
—
DBE or
ECLK or
CAL
MODB or
IPIPE1 or
CGMTST
Alt. Pin
Function
MODA or
IPIPE0
LSTRB or
TAGLO
ECLK
R/W
IRQ
XIRQ
This register is associated with external bus control signals and
interrupt inputs, including data bus enable (DBE), mode select
(MODB/IPIPE1, MODA/IPIPE0), E clock, size (LSTRB), read/write
(R/W), IRQ, and XIRQ. When the associated pin is not used for one
of these specific functions, the pin can be used as general-purpose
I/O. The port E assignment register (PEAR) selects the function of
each pin. DDRE determines the primary direction of each port E pin
when configured to be general-purpose I/O.
Some of these pins have software selectable pull-ups (DBE, LSTRB,
R/W, IRQ and XIRQ). A single control bit enables the pull-ups for all
these pins which are configured as inputs.
4-bus
MC68HC912DT128A Rev 2.0
86
Bus Control and Input/Output
MOTOROLA
Bus Control and Input/Output
Registers
This register is not in the map in peripheral mode or expanded modes
when the EME bit is set.
Read and write anytime.
DDRE — Port E Data Direction Register
$0009
Bit 7
DDE7
0
6
DDE6
0
5
DDE5
0
4
DDE4
0
3
DDE3
0
2
DDE2
0
1
0
0
Bit 0
0
0
RESET:
This register determines the primary direction for each port E pin
configured as general-purpose I/O.
0 = Associated pin is a high-impedance input
1 = Associated pin is an output
PE[1:0] are associated with XIRQ and IRQ and cannot be configured
as outputs. These pins can be read regardless of whether the
alternate interrupt functions are enabled.
This register is not in the map in peripheral mode and expanded
modes while the EME control bit is set.
Read and write anytime.
PEAR — Port E Assignment Register
$000A
BIT 7
6
5
4
3
2
1
BIT 0
NDBE
CGMTE
PIPOE
NECLK
LSTRE
RDWE
CALE
DBENE
Normal Ex-
panded
RESET:
0
0
0
0
0
0
0
0
Special Ex-
panded
RESET:
RESET:
RESET:
0
1
1
0
1
0
1
0
0
0
1
1
1
0
0
1
0
0
0
0
0
0
0
0
Peripheral
Normal sin-
gle chip
Special sin-
gle chip
RESET:
0
0
1
0
1
1
0
0
Port E serves as general purpose I/O lines or as system and bus
control signals. The PEAR register is used to choose between the
general-purpose I/O functions and the alternate bus control functions.
When an alternate control function is selected, the associated DDRE
bits are overridden.
5-bus
MC68HC912DT128A Rev 2.0
MOTOROLA
Bus Control and Input/Output
87
Bus Control a nd Inp ut/ Outp ut
The reset condition of this register depends on the mode of operation
because bus control signals are needed immediately after reset in
some modes.
In normal single-chip mode, no external bus control signals are
needed so all of port E is configured for general-purpose I/O.
In normal expanded modes, the reset vector is located in external
memory. The DBE and E clock are required for de-multiplexing
address and data but LSTRB and R/W are only needed by the system
when there are external writable resources. Therefore in normal
expanded modes, the DBE and the E clock are configured for their
alternate bus control functions and the other bits of port E are
configured for general-purpose I/O. If the normal expanded system
needs any other bus control signals, PEAR would need to be written
before any access that needed the additional signals.
In special expanded modes, DBE, IPIPE1, IPIPE0, E, LSTRB, and
R/W are configured as bus-control signals.
In special single chip modes, DBE, IPIPE1, IPIPE0, E, LSTRB, R/W,
and CALE are configured as bus-control signals.
In peripheral mode, the PEAR register is not accessible for reads or
writes. However, the CGMTE control bit is reset to one to configure
PE6 as a test output for the CGM module.
NDBE — No Data Bus Enable
Normal: write once; Special: write anytime EXCEPT the first. Read
anytime.
0 = PE7 is used for DBE, external control of data enable on
memories, or inverted E clock.
1 = PE7 is CAL function if CALE bit is set in PEAR register or
general-purpose I/O otherwise.
The NDBE bit has no effect in Single Chip or Peripheral Modes and
PE7 is defaulted to the CAL function if CALE bit is set in PEAR
register or to an I/O otherwise.
CGMTE — Clock Generator Module Testing Enable
Normal: write never; Special: write anytime EXCEPT the first time.
Read anytime.
0 = PE6 is general-purpose I/O or pipe output.
6-bus
MC68HC912DT128A Rev 2.0
88
Bus Control and Input/Output
MOTOROLA
Bus Control and Input/Output
Registers
1 = PE6 is a test signal output from the CGM module (no effect in
single chip or normal expanded modes). PIPOE = 1 overrides
this function and forces PE6 to be a pipe status output signal.
PIPOE — Pipe Status Signal Output Enable
Normal: write once; Special: write anytime EXCEPT the first time.
Read anytime.
0 = PE[6:5] are general-purpose I/O (if CGMTE = 1, PE6 is a test
output signal from the CGM module).
1 = PE[6:5] are outputs and indicate the state of the instruction
queue (only effective in expanded modes).
NECLK — No External E Clock
Normal single chip: write once; special single chip: write anytime; all
other modes: write never.
Read anytime. In peripheral mode, E is an input and in all other
modes, E is an output.
0 = PE4 is the external E-clock pin subject to the following
limitation: In single-chip modes, to get an E clock output signal,
it is necessary to have ESTR = 0 in addition to NECLK = 0. A
16-bit write to PEAR and MODE registers can configure all
three bits in one operation.
1 = PE4 is a general-purpose I/O pin.
LSTRE — Low Strobe (LSTRB) Enable
Normal: write once; Special: write anytime EXCEPT the first time.
Read anytime. This bit has no effect in single-chip modes or normal
expanded narrow mode.
0 = PE3 is a general-purpose I/O pin.
1 = PE3 is configured as the LSTRB bus-control output, provided
the MCU is not in single chip or normal expanded narrow
modes.
LSTRB is used during external writes. After reset in normal expanded
mode, LSTRB is disabled. If needed, it should be enabled before
external writes. External reads do not normally need LSTRB because
all 16 data bits can be driven even if the MCU only needs 8 bits of
data.
7-bus
MC68HC912DT128A Rev 2.0
MOTOROLA
Bus Control and Input/Output
89
Bus Control a nd Inp ut/ Outp ut
TAGLO is a shared function of the PE3/LSTRB pin. In special
expanded modes with LSTRE set and the BDM tagging on, a zero at
the falling edge of E tags the instruction word low byte being read into
the instruction queue.
RDWE — Read/Write Enable
Normal: write once; Special: write anytime EXCEPT the first time.
Read anytime. This bit has no effect in single-chip modes.
0 = PE2 is a general-purpose I/O pin.
1 = PE2 is configured as the R/W pin. In single chip modes, RDWE
has no effect and PE2 is a general-purpose I/O pin.
R/W is used for external writes. After reset in normal expanded mode,
it is disabled. If needed it should be enabled before any external
writes.
CALE — Calibration Reference Enable
Read and write anytime.
0 = Calibration reference is disabled and PE7 is general purpose
I/O in single chip or peripheral modes or if NDBE bit is set.
1 = Calibration reference is enabled on PE7 in single chip and
peripheral modes or if NDBE bit is set.
DBENE — DBE or Inverted E Clock on PE7
Normal modes: write once. Special modes: write anytime EXCEPT
the first time. Read anytime.
DBENE controls which signal is output on PE7 when NDBE control bit
is cleared. The inverted E clock output can be used to latch the
address for de-multiplexing. It has the same behavior as the E clock,
except it is inverted. Please note that in the case of idle expansion
bus, the ‘not E clock’ signal could stay high for many cycles.
The DBENE bit has no effect in Single Chip or Peripheral Modes and
PE7 is defaulted to the CAL function if CALE bit is set in PEAR
register or to an I/O otherwise.
0 = PE7 pin used for DBE external control of data enable on
memories in expanded modes when NDBE = 0
1 = PE7 pin used for inverted E clock output in expanded modes
when NDBE = 0
8-bus
MC68HC912DT128A Rev 2.0
90
Bus Control and Input/Output
MOTOROLA
Bus Control and Input/Output
Registers
PUCR — Pull-Up Control Register
$000C
Bit 7
PUPK
0
6
PUPJ
0
5
PUPH
0
4
PUPE
1
3
0
0
2
0
0
1
PUPB
0
Bit 0
PUPA
0
RESET:
These bits select pull-up resistors for any pin in the corresponding
port that is currently configured as an input. This register is not in the
map in peripheral mode.
Read and write anytime.
PUPK — Pull-Up Port K Enable
0 = Port K pull-ups are disabled.
1 = Enable pull-up devices for all port K input pins.
PUPJ — Pull-Up or Pull-Down Port J Enable
0 = Port J resistive loads (pull-ups or pull-downs) are disabled.
1 = Enable resistive load devices (pull-ups or pull-downs) for all
port J input pins.
PUPH — Pull-Up or Pull-Down Port H Enable
0 = Port H resistive loads (pull-ups or pull-downs) are disabled.
1 = Enable resistive load devices (pull-ups or pull-downs) for all
port H input pins.
PUPE — Pull-Up Port E Enable
0 = Port E pull-ups on PE7, PE3, PE2, PE1 and PE0 are disabled.
1 = Enable pull-up devices for port E input pins PE7, PE3, PE2,
PE1 and PE0.
When this bit is set port E input pins 7, 3, 2, 1 & 0 have an active
pull-up device.
PUPB — Pull-Up Port B Enable
0 = Port B pull-ups are disabled.
1 = Enable pull-up devices for all port B input pins.
PUPA — Pull-Up Port A Enable
0 = Port A pull-ups are disabled.
1 = Enable pull-up devices for all port A input pins.
9-bus
MC68HC912DT128A Rev 2.0
MOTOROLA
Bus Control and Input/Output
91
Bus Control a nd Inp ut/ Outp ut
RDRIV — Reduced Drive of I/O Lines
$000D
Bit 7
RDPK
0
6
RDPJ
0
5
RDPH
0
4
RDPE
0
3
0
0
2
0
0
1
RDPB
0
Bit 0
RDPA
0
RESET:
These bits select reduced drive for the associated port pins. This
gives reduced power consumption and reduced RFI with a slight
increase in transition time (depending on loading). The reduced drive
function is independent of which function is being used on a particular
port.
This register is not in the map in peripheral mode.
Normal: write once; Special: write anytime EXCEPT the first time.
Read anytime.
RDPK — Reduced Drive of Port K
0 = All port K output pins have full drive enabled.
1 = All port K output pins have reduced drive capability.
RDPJ — Reduced Drive of Port J
0 = All port J output pins have full drive enabled.
1 = All port J output pins have reduced drive capability.
RDPH — Reduced Drive of Port H
0 = All port H output pins have full drive enabled.
1 = All port H output pins have reduced drive capability.
RDPE — Reduced Drive of Port E
0 = All port E output pins have full drive enabled.
1 = All port E output pins have reduced drive capability.
RDPB — Reduced Drive of Port B
0 = All port B output pins have full drive enabled.
1 = All port B output pins have reduced drive capability.
RDPA — Reduced Drive of Port A
0 = All port A output pins have full drive enabled.
1 = All port A output pins have reduced drive capability.
10-bus
MC68HC912DT128A Rev 2.0
92
Bus Control and Input/Output
MOTOROLA
Fla sh EEPROM
Fla sh EEPROM
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Flash EEPROM Control Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Flash EEPROM Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Flash EEPROM Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Programming the Flash EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Erasing the Flash EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Stop or Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Introd uc tion
The four Flash EEPROM array modules 00FEE32K, 01FEE32K,
10FEE32K and 11FEE32K for the MC68HC912DT128A serve as
electrically erasable and programmable, non-volatile ROM emulation
memory. The modules can be used for program code that must either
execute at high speed or is frequently executed, such as operating
system kernels and standard subroutines, or they can be used for static
data which is read frequently. The Flash EEPROM module is ideal for
program storage for single-chip applications allowing for field
reprogramming.
Ove rvie w
Each 32K Flash EEPROM array is arranged in a 16-bit configuration and
may be read as either bytes, aligned words or misaligned words. Access
1-flash
MC68HC912DT128A Rev 2.0
MOTOROLA
Flash EEPROM
93
Fla sh EEPROM
time is one bus cycle for byte and aligned word access and two bus
cycles for misaligned word operations.
Programming is by aligned word. The Flash EEPROM module supports
bulk erase only.
Each Flash EEPROM module has hardware interlocks which protect
stored data from accidental corruption. An erase- and
program-protected 8-Kbyte block for boot routines is located at the top
of each 32-Kbyte array. Since boot programs must be available at all
times, the only useful boot block is at $E000–$FFFF location. All paged
boot blocks can be used as protected program space if desired.
Fla sh EEPROM Control Bloc k
A 4-byte register block for each module controls the Flash EEPROM
operation. Configuration information is specified and programmed
independently from the contents of the Flash EEPROM array. At reset,
the 4-byte register section starts at address $00F4 and points to the
00FEE32K register block.
Fla sh EEPROM Arra ys
After reset, a fixed 32K Flash EEPROM array, 11FEE32K, is located
from addresses $4000 to $7FFF and from $C000 to $FFFF. The other
three 32K Flash EEPROM arrays 00FEE32K, 01FEE32K and
10FEE32K, are mapped through a 16K byte program page window
located from addresses $8000 to $BFFF. The page window has eight
16K byte pages. The last two pages also map the physical location of the
fixed 32K Flash EEPROM array 11FEE32K. In expanded modes, the
Flash EEPROM arrays are turned off. See Operating Modes.
2--flash
MC68HC912DT128A Rev 2.0
94
Flash EEPROM
MOTOROLA
Flash EEPROM
Flash EEPROM Registers
Fla sh EEPROM Re g iste rs
Each 32K byte Flash EEPROM module has a set of registers. The
register space $00F4-$00F7 is in a register space window of four pages.
Each register page of four bytes maps the register space for each Flash
module and each page is selected by the PPAGE register. See
Resource Mapping
FEELCK — Flash EEPROM Lock Control Register
$00F4
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
LOCK
0
0
0
RESET:
In normal modes the LOCK bit can only be written once after reset.
LOCK — Lock Register Bit
0 = Enable write to FEEMCR register
1 = Disable write to FEEMCR register
FEEMCR — Flash EEPROM Module Configuration Register
$00F5
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
BOOTP
1
0
0
RESET:
This register controls the operation of the Flash EEPROM array.
BOOTP cannot be changed when the LOCK control bit in the
FEELCK register is set or if ENPE in the FEECTL register is set.
BOOTP — Boot Protect
The boot blocks are located at $E000–$FFFF and $A000–$BFFF for
odd program pages for each Flash EEPROM module. Since boot
programs must be available at all times, the only useful boot block is
at $E000–$FFFF location. All paged boot blocks can be used as
protected program space if desired.
0 = Enable erase and program of 8K byte boot block
1 = Disable erase and program of 8K byte boot block
3-flash
MC68HC912DT128A Rev 2.0
MOTOROLA
Flash EEPROM
95
Fla sh EEPROM
FEECTL — Flash EEPROM Control Register
$00F7
Bit 7
6
0
0
5
0
0
4
FEESWAI
0
3
HVEN
0
2
0
0
1
ERAS
0
Bit 0
PGM
0
0
0
RESET:
This register controls the programming and erasure of the Flash
EEPROM.
FEESWAI — Flash EEPROM Stop in Wait Control
0 = Do not halt Flash EEPROM clock when the part is in wait
mode.
1 = Halt Flash EEPROM clock when the part is in wait mode.
HVEN — High-Voltage Enable
This bit enables the charge pump to supply high voltages for program
and erase operations in the array. HVEN can only be set if either PGM
or ERAS are set and the proper sequence for program or erase is
followed.
0 = Disables high voltage to array and charge pump off
1 = Enables high voltage to array and charge pump on
ERAS — Erase Control
This bit configures the memory for erase operation. ERAS is
interlocked with the PGM bit such that both bits cannot be equal to 1
or set to1 at the same time.
0 = Erase operation is not selected.
1 = Erase operation selected.
PGM — Program Control
This bit configures the memory for program operation. PGM is
interlocked with the ERAS bit such that both bits cannot be equal to 1
or set to1 at the same time.
0 = Program operation is not selected.
1 = Program operation selected.
4-flash
MC68HC912DT128A Rev 2.0
96
Flash EEPROM
MOTOROLA
Flash EEPROM
Operation
Op e ra tion
The Flash EEPROM can contain program and data. On reset, it can
operate as a bootstrap memory to provide the CPU with internal
initialization information during the reset sequence.
Bootstra p
Op e ra tion
After reset, the CPU controlling the system will begin booting up by
fetching the first program address from address $FFFE.
Sing le -Chip Mod e
Norm a l Ope ra tion
The Flash EEPROM allows a byte or aligned word read in one bus cycle.
Misaligned word read require an additional bus cycle. The Flash
EEPROM array responds to read operations only. Write operations are
ignored.
Prog ra m / Era se
Op e ra tion
An unprogrammed Flash EEPROM bit has a logic state of one. A bit
must be programmed to change its state from one to zero. Erasing a bit
returns it to a logic one. The Flash EEPROM has a minimum
program/erase life of 100 cycles. Programming or erasing the Flash
EEPROM is accomplished by a series of control register writes.
Programming is restricted to aligned word at a time as determined by
internal signal SZ8 and ADDR[0]. The Flash EEPROM must first be
completely erased prior to programming final data values.
Programming and erasing of Flash locations cannot be performed by
code being executed from the FLASH memory. While these operations
must be performed in the order shown, other unrelated operations may
occur between the steps. Do not exceed tFPGM maximum (40µs).
Prog ra m m ing the Fla sh EEPROM
Programming the Flash EEPROM is done on a row basis. A row consists
of 64 consecutive bytes starting from addresses $XX00, $XX40, $XX80
5-flash
MC68HC912DT128A Rev 2.0
MOTOROLA
Flash EEPROM
97
Fla sh EEPROM
and $XXC0. Use this step-by-step procedure to program a row of Flash
memory.
1. Set the PGM bit. This configures the memory for program
operation and enables the latching of address and data for
programming.
2. Write to any Flash address with any data within the row address
range desired.
3. Wait for a time, tNVS (min. 10µs).
4. Set the HVEN bit.
5. Wait for a time, tPGS (min. 5µs).
6. Write to the Flash address with data to the word desired to be
programmed. If BOOTP is asserted, an attempt to program an
address in the boot block will be ignored.
7. Wait for a time, tFPGM (min. 30µs).
8. Repeat step 6 and 7 until all the words within the row are
programmed.
9. Clear the PGM bit.
10. Wait for a time, tNVH (min. 5µs).
11. Clear the HVEN bit.
12. After time, tRCV (min 1µs), the memory can be accessed in read
mode again.
This program sequence is repeated throughout the memory until all data
is programmed. For minimum overall programming time and least
program disturb effect, the sequence should be part of an intelligent
operation which iterates per row.
Era sing the Fla sh EEPROM
The following sequence demonstrates the recommended procedure for
erasing any of the Flash EEPROM array.
1. Set the ERAS bit.
2. Write to any valid address in the Flash array. The data written and
the address written are not important. The boot block will be
6-flash
MC68HC912DT128A Rev 2.0
98
Flash EEPROM
MOTOROLA
Flash EEPROM
Stop or Wait Mode
erased only if the control bit BOOTP is negated.
3. Wait for a time, tNVS
.
4. Set the HVEN bit.
5. Wait for a time, tERAS
.
6. Clear the ERAS bit.
7. Wait for a time, tNVHL
.
8. Clear the HVEN bit.
9. After time, tRCV, the memory can be accessed in read mode again.
Stop or Wa it Mod e
When stop or wait commands are executed, the MCU puts the Flash
EEPROM in stop or wait mode. In these modes the Flash module will
cease erasure or programming immediately.
CAUTION: It is advised not to enter stop or wait modes when program or erase
operation of the Flash array is in progress.
7-flash
MC68HC912DT128A Rev 2.0
MOTOROLA
Flash EEPROM
99
Fla sh EEPROM
8-flash
MC68HC912DT128A Rev 2.0
100
Flash EEPROM
MOTOROLA
EEPROM
EEPROM
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
EEPROM Selective Write More Zeros . . . . . . . . . . . . . . . . . . . . . . . 102
EEPROM Programmer’s Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
EEPROM Control Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Program/Erase Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Shadow Word Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Programming EEDIVH and EEDIVL Registers . . . . . . . . . . . . . . . . . 112
Introd uc tion
The MC68HC912DT128A EEPROM nonvolatile memory is arranged in
a 16-bit configuration. The EEPROM array may be read as either bytes,
aligned words or misaligned words. Access times are one bus cycle for
byte and aligned word access and two bus cycles for misaligned word
operations.
Programming is by byte or aligned word. Attempts to program or erase
misaligned words will fail. Only the lower byte will be latched and
programmed or erased. Programming and erasing of the user EEPROM
can be done in normal modes.
Each EEPROM byte or aligned word must be erased before
programming. The EEPROM module supports byte, aligned word, row
(32 bytes) or bulk erase, all using the internal charge pump. The erased
state is $FF. The EEPROM module has hardware interlocks which
protect stored data from corruption by accidentally enabling the
program/erase voltage. Programming voltage is derived from the
internal VDD supply with an internal charge pump.
1-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
101
EEPROM
EEPROM Se le c tive Write More Ze ros
The EEPROM can be programmed such that one or multiple bits are
programmed (written to a logic “0”) at a time. However, the user should
may never program one bit more than once before erasing the entire
byte. In other words, the user is not allowed to over write a logic “0” with
another “0’.
For some applications it may be advantageous to track more than 10k
events with a single byte of EEPROM by programming one bit at a time.
For that purpose, a special selective bit programming technique is
available. An example is shown here.
Original state of byte = binary 1111:1111 (erased)
First event is recorded by programming bit position 0
Program write = binary 1111:1110;
Result = binary 1111:1110
Second event is recorded by programming bit position 1
Program write = binary 1111:1101;
Result = binary 1111:1100
Third event is recorded by programming bit position 2
Program write = binary 1111:1011;
Result = binary 1111:1000
Fourth event is recorded by programming bit position 3
Program write = binary 1111:0111;
Result = binary 1111:0000
Events five through eight are recorded in a similar fashion.
Note that none of the bit locations are actually programmed more than
once although the byte was programmed eight times.
When this technique is utilized, a program / erase cycle is defined as
multiple writes (up to eight) to a unique location followed by a single
erase sequence.
2--eeprom
MC68HC912DT128A Rev 2.0
102
EEPROM
MOTOROLA
EEPROM
EEPROM Programmer’s Model
EEPROM Prog ra m m e r’s Mod e l
The EEPROM module consists of two separately addressable sections.
The first is an eight-byte memory mapped control register block used for
control, testing and configuration of the EEPROM array. The second
section is the EEPROM array itself.
At reset, the eight-byte register section starts at address $00EC and the
EEPROM array is located from addresses $0800 to $0FFF. Registers
$00EC-$00ED are reserved.
Read/write access to the memory array section can be enabled or
disabled by the EEON control bit in the INITEE register ($0012). This
feature allows the access of memory mapped resources that have lower
priority than the EEPROM memory array. EEPROM control registers can
be accessed regardless of the state of EEON. Any EEPROM erase or
program operation already in progress will not be affected by the change
of EEON state. For information on re-mapping the register block and
EEPROM address space, refer to Operating Modes.
CAUTION: It is strongly recommended to discontinue program/erase operations
during WAIT (when EESWAI=1) or STOP modes since all
program/erase activities will be terminated abruptly and considered
unsuccessful.
For lowest power consumption during WAIT mode, it is advised to turn
off EEPGM.
The EEPROM module contains an extra word called SHADOW word
which is loaded at reset into the EEMCR, EEDIVH and EEDIVL
registers. To program the SHADOW word, when in special modes
(SMODN=0), the NOSHW bit in EEMCR register must be cleared.
Normal programming routines are used to program the SHADOW word
which becomes accessible at address $0FC0-$0FC1 when NOSHW is
cleared. At the next reset the SHADOW word data is loaded into the
EEMCR, EEDIVH and EEDIVL registers. The SHADOW word can be
protected from being programmed or erased by setting the SHPROT bit
of EEPROT register.
3-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
103
EEPROM
A steady internal self-time clock is required to provide accurate counts
to meet EEPROM program/erase requirements. This clock is generated
via by a programmable 10-bit prescaler register. Automatic
program/erase termination is also provided.
In ordinary situations, with crystal operating properly, the steady internal
self-time clock is derived from the input clock source (EXTALi). The
divider value is as in EEDIVH:EEDIVL. In limp-home mode, where the
oscillator has malfunctioned or is unavailable, the self-time clock is
derived from the PLL at fVCOMIN (nominally 1 MHz), with a predefined
divider value of $0023. Program/erase operation is not guaranteed in
limp-home mode. The clock switching function is only applicable for
permanent loss of crystal condition, so the program/erase will also not
be guaranteed when the loss of crystal condition is intermittent.
It is strongly recommended that the clock monitor is enabled to ensure
that the program/erase operation will be shutdown in the event of loss of
crystal with a clock monitor reset, or switch to a limp-home mode clock.
This will prevent unnecessary stress on the emulated EEPROM during
oscillator failure.
4-eeprom
MC68HC912DT128A Rev 2.0
104
EEPROM
MOTOROLA
EEPROM
EEPROM Control Registers
EEPROM Control Re g iste rs
EEDIVH — EEPROM Modulus Divider
$00EE
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
Bit 0
0
0
EEDIV9
EEDIV8
(1)
(1)
RESET:
—
—
1. Loaded from SHADOW word.
EEDIVL — EEPROM Modulus Divider
$00EF
Bit 7
6
5
4
3
2
1
Bit 0
EEDIV7
EEDIV6
EEDIV5
EEDIV4
EEDIV3
EEDIV2
EEDIV1
EEDIV0
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
RESET:
—
—
—
—
—
—
—
—
1. Loaded from SHADOW word.
EEDIV[9:0] — Prescaler divider
Loaded from SHADOW word at reset.
Read anytime. Write once in normal modes (SMODN =1) if EELAT =
0 and anytime in special modes (SMODN =0) if EELAT = 0.
The prescaler divider is required to produce a self-time clock with a
fixed frequency around 28.6 Khz for the range of oscillator
frequencies. The divider is set so that the oscillator frequency can be
divided by a divide factor that can produce a 35 µs ± 2µs timebase.
CAUTION: An incorrect or uninitialized value on EEDIV can result in overstress of
EEPROM array during program/erase operation. It is also strongly
recommend not to program EEPROM with oscillator frequencies less
than 250 Khz.
The EEDIV value is determined by the following formula:
–6
EEDIV = INT[EXTALi (hz) x 35×10 + 0.5]
5-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
105
EEPROM
NOTE: INT[A] denotes the round down integer value of A. Program/erase cycles
will not be activated when EEDIV = 0.
Table 17 EEDIV Selection
Osc Freq.
16 Mhz
8 Mhz
Osc Period
62.5ns
125ns
250ns
500ns
1µs
Divide Factor
EEDIV
$0230
$0118
$008C
$0046
$0023
$0012
$0009
560
280
140
70
4 Mhz
2 Mhz
1 Mhz
35
500 Khz
250 Khz
2µs
18
4µs
9
EEMCR — EEPROM Module Configuration
$00F0
Bit 7
6
5
4
3
1
1
2
1
Bit 0
DMY
0
RESERVED(1)
NOBDML
NOSHW
EESWAI PROTLCK
(2)
(2)
(2)
(2)
RESET:
—
—
—
—
1
0
1. Bits 4 and 5 have test functions and should not be programmed.
2. Loaded from SHADOW word.
Bits[7:4] are loaded at reset from the EEPROM SHADOW word.
NOTE: The bits 5 and 4 are reserved for test purposes. These locations in
SHADOW word should not be programmed otherwise some locations of
regular EEPROM array will not be more visible.
NOBDML — Background Debug Mode Lockout Disable
0 = The BDM lockout is enabled.
1 = The BDM lockout is disabled.
Loaded from SHADOW word at reset.
Read anytime. Write anytime in special modes (SMODN=0).
NOSHW — SHADOW Word Disable
0 = The SHADOW word is enabled and accessible at address
$0FC0-$0FC1.
1 = Regular EEPROM array at address $0FC0-$0FC1.
Loaded from SHADOW word at reset.
Read anytime. Write anytime in special modes (SMODN=0).
6-eeprom
MC68HC912DT128A Rev 2.0
106
EEPROM
MOTOROLA
EEPROM
EEPROM Control Registers
When NOSHW cleared, the regular EEPROM array bytes at address
$0FC0 and $0FC1 are not visible. The SHADOW word is accessed
instead for both read and program/erase operations. Bits[7:4] from
the high byte of the SHADOW word, $0FC0, are loaded to
EEMCR[7:4]. Bits[1:0] from the high byte of the SHADOW word,
$0FC0,are loaded to EEDIVH[1:0]. Bits[7:0] from the low byte of the
SHADOW word, $0FC1,are loaded to EEDIVL[7:0]. BULK
program/erase only applies if SHADOW word is enabled.
NOTE: Bit 6 from high byte of SHADOW word should not be programmed in
order to have the full EEPROM array visible.
EESWAI — EEPROM Stops in Wait Mode
0 = The module is not affected during WAIT mode
1 = The module ceases to be clocked during WAIT mode
Read and write anytime.
NOTE: The EESWAI bit should be cleared if the WAIT mode vectors are
mapped in the EEPROM array.
PROTLCK — Block Protect Write Lock
0 = Block protect bits and bulk erase protection bit can be written
1 = Block protect bits are locked
Read anytime. Write once in normal modes (SMODN = 1), set and
clear any time in special modes (SMODN = 0).
DMY— Dummy bit
Read and write anytime.
7-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
107
EEPROM
EEPROT — EEPROM Block Protect
$00F1
Bit 7
SHPROT
1
6
1
1
5
BPROT5
1
4
BPROT4
1
3
BPROT3
1
2
BPROT2
1
1
BPROT1
1
Bit 0
BPROT0
1
RESET:
Prevents accidental writes to EEPROM. Read anytime. Write anytime if
EEPGM = 0 and PROTLCK = 0.
SHPROT — SHADOW Word Protection
0 = The SHADOW word can be programmed and erased.
1 = The SHADOW word is protected from being programmed and
erased.
BPROT[5:0] — EEPROM Block Protection
0 = Associated EEPROM block can be programmed and erased.
1 = Associated EEPROM block is protected from being
programmed and erased.
Table 18 2K byte EEPROM Block Protection
Bit Name
BPROT5
BPROT4
BPROT3
BPROT2
BPROT1
BPROT0
Block Protected
$0800 to $0BFF
$0C00 to $0DFF
$0E00 to $0EFF
$0F00 to $0F7F
$0F80 to $0FBF
$0FC0 to $0FFF
Block Size
1024 Bytes
512 Bytes
256 Bytes
128 Bytes
64 Bytes
64 Bytes
EETST — EEPROM Test
$00F2
Bit 7
6
5
0
0
4
0
0
3
2
ETMSD
0
1
ETMR
0
Bit 0
ETMSE
0
0
0
EREVTN
0
0
0
RESET:
In normal mode, writes to EETST control bits have no effect and
always read zero. The EEPROM module cannot be placed in test
mode inadvertently during normal operation
8-eeprom
MC68HC912DT128A Rev 2.0
108
EEPROM
MOTOROLA
EEPROM
EEPROM Control Registers
.
EEPROG — EEPROM Control
$00F3
Bit 7
BULKP
1
6
0
0
5
AUTO
0
4
BYTE
0
3
ROW
0
2
ERASE
0
1
Bit 0
EELAT
0
EEPGM
0
RESET:
BULKP — Bulk Erase Protection
0 = EEPROM can be bulk erased.
1 = EEPROM is protected from being bulk or row erased.
Read anytime. Write anytime if EEPGM = 0 and PROTLCK = 0.
AUTO — Automatic shutdown of program/erase operation.
EEPGM is cleared automatically after the program/erase cycles are
finished when AUTO is set.
0 = Automatic clear of EEPGM is disabled.
1 = Automatic clear of EEPGM is enabled.
Read anytime. Write anytime if EEPGM = 0.
BYTE — Byte and Aligned Word Erase
0 = Bulk or row erase is enabled.
1 = One byte or one aligned word erase only.
Read anytime. Write anytime if EEPGM = 0.
ROW — Row or Bulk Erase (when BYTE = 0)
0 = Erase entire EEPROM array.
1 = Erase only one 32-byte row.
Read anytime. Write anytime if EEPGM = 0.
BYTE and ROW have no effect when ERASE = 0
Table 19 Erase Selection
BYTE
ROW
Block size
0
0
1
1
0
1
0
1
Bulk erase entire EEPROM array
Row erase 32 bytes
Byte or aligned word erase
Byte or aligned word erase
If BYTE = 1 only the location specified by the address written to the
programming latches will be erased. The operation will be a byte or
an aligned word erase depending on the size of written data.
9-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
109
EEPROM
ERASE — Erase Control
0 = EEPROM configuration for programming.
1 = EEPROM configuration for erasure.
Read anytime. Write anytime if EEPGM = 0.
Configures the EEPROM for erasure or programming.
Unless BULKP is set, erasure is by byte, aligned word, row or bulk.
EELAT — EEPROM Latch Control
0 = EEPROM set up for normal reads.
1 = EEPROM address and data bus latches set up for
programming or erasing.
Read anytime.
Write anytime except when EEPGM = 1 or EEDIV = 0.
BYTE, ROW, ERASE and EELAT bits can be written simultaneously
or in any sequence.
EEPGM — Program and Erase Enable
0 = Disables program/erase voltage to EEPROM.
1 = Applies program/erase voltage to EEPROM.
The EEPGM bit can be set only after EELAT has been set. When
EELAT and EEPGM are set simultaneously, EEPGM remains clear
but EELAT is set.
The BULKP, AUTO, BYTE, ROW, ERASE and EELAT bits cannot be
changed when EEPGM is set. To complete a program or erase cycle
when AUTO bit is clear, two successive writes to clear EEPGM and
EELAT bits are required before reading the programmed data. When
AUTO bit is set, EEPGM is automatically cleared after the program or
erase cycle is over. A write to an EEPROM location has no effect
when EEPGM is set. Latched address and data cannot be modified
during program or erase.
10-eeprom
MC68HC912DT128A Rev 2.0
110
EEPROM
MOTOROLA
EEPROM
Program/Erase Operation
Prog ra m / Era se Op e ra tion
A program or erase operation should follow the sequence below if AUTO
bit is clear:
1. Write BYTE, ROW and ERASE to desired value, write EELAT = 1
2. Write a byte or an aligned word to an EEPROM address
3. Write EEPGM = 1
4. Wait for programming, tPROG or erase, tERASE delay time
5. Write EEPGM = 0
6. Write EELAT = 0
If the AUTO bit is set, steps 4 and 5 can be replaced by a step to poll the
EEPGM bit until it is cleared.
CAUTION: The state machine will not start if an attempt is made to program or erase
a protected location and therefore the EEPGM bit will never clear on that
EEPROM operation. Check for protected status or use a software
timeout to avoid a continuous loop whilst polling the EEPGM bit. If using
a timeout, ensure steps 5 and 6 are still executed.
It is possible to program/erase more bytes or words without intermediate
EEPROM reads, by jumping from step 5 to step 2.
Sha d ow Word Ma p p ing
The shadow word is mapped to location $_FC0 and $_FC1 when the
NOSHW bit in EEMCR register is zero. The value in the shadow word is
loaded to the EEMCR, EEDIVH and EEDIVL after reset. Table 20 shows
the mapping of each bit from shadow word to the registers.
11-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
111
EEPROM
Table 20 Shadow word mapping
Shadow word location
Register / Bit
EEMCR / NOBDML
EEMCR / NOSHW
EEMCR / bit 5(1)
EEMCR / bit 4(1)
not mapped(2))
$_FC0 bit 7
$_FC0, bit 6
$_FC0, bit 5
$_FC0, bit 4
$_FC0, bit 3:2
$_FC0, bit 1:0
$_FC1, bit 7:0
EEDIVH / bit 1:0
EEMCR / bit 7:0
1. Reserved for testing. Must be set to one in user application.
2. Reserved. Must be set to one in user application for future compatibility.
Prog ra m m ing EEDIVH a nd EEDIVL Re g iste rs
The EEDIVH and EEDIVL registers must be correctly set according to
the oscillator frequency before any EEPROM location can be
programmed or erased.
Norm a l m od e
The EEDIVH and EEDIVL registers are write once in normal mode.
Upon system reset, the application program is required to write the
correct divider value to EEDIVH and EEDIVL registers based on the
oscillator frequency. After the first write, the value in the EEDIVH and
EEDIVL registers is locked from being overwritten until the next reset.
The EEPROM is then ready for standard program/erase routines.
CAUTION: Runaway code can possibly corrupt the EEDIVH and EEDIVL registers
if they are not initialized (write once registers).
12-eeprom
MC68HC912DT128A Rev 2.0
112
EEPROM
MOTOROLA
EEPROM
Programming EEDIVH and EEDIVL Registers
Sp e c ia l m od e
If an existing application code with EEPROM program/erase routines is
fixed and the system is already operating at a known oscillator
frequency, it is recommended to initialize the shadow word with the
corresponding EEDIVH and EEDIVL values in special mode. The
shadow word initializes EEDIVH and EEDIVL registers upon system
reset to ensure software compatibility with existing code. Initializing the
EEDIVH and EEDIVL registers in special modes (SMODN=0) is
accomplished by the following steps.
1. Write correct divider value to EEDIVH and EEDIVL registers
based on the oscillator frequency as per Table 17.
2. Remove the SHADOW word protection by clearing SHPROT bit in
EEPROT register.
3. Clear NOSHW bit in EEMCR register to make the SHADOW word
visible at $0FC0-$0FC1.
4. Write NOSHW bit in EEMCR register to make the SHADOW word
visible at $0FC0-$0FC1.
5. Program bits 1 and 0 of the high byte of the SHADOW word and
bits 7 to 0 of the low byte of the SHADOW word like a regular
EEPROM location at address $0FC0 and $0FC1. Do not program
other bits of the high byte of the SHADOW word (location $0FC0);
otherwise some regular EEPROM array locations will not be
visible. At the next reset, the SHADOW values are loaded into the
EEDIVH and EEDIVL registers. They do not require further
initialization as long as the oscillator frequency of the target
application is not changed.
6. Protect the SHADOW word by setting SHPROT bit in EEPROT
register.
13-eeprom
MC68HC912DT128A Rev 2.0
MOTOROLA
EEPROM
113
EEPROM
14-eeprom
MC68HC912DT128A Rev 2.0
114
EEPROM
MOTOROLA
Re se ts a nd Inte rrup ts
Re se ts a nd Inte rrup ts
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Exception Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Maskable interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Latching of Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Interrupt Control and Priority Registers. . . . . . . . . . . . . . . . . . . . . . . 119
Interrupt test registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Resets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Effects of Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Register Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Introd uc tion
CPU12 exceptions include resets and interrupts. Each exception has an
associated 16-bit vector, which points to the memory location where the
routine that handles the exception is located. Vectors are stored in the
upper 128 bytes of the standard 64K byte address map.
The six highest vector addresses are used for resets and non-maskable
interrupt sources. The remainder of the vectors are used for maskable
interrupts, and all must be initialized to point to the address of the
appropriate service routine.
1-reset
MC68HC912DT128A Rev 2.0
MOTOROLA
Resets and Interrupts
115
Re se ts a nd Inte rrup ts
Exc e p tion Priority
A hardware priority hierarchy determines which reset or interrupt is
serviced first when simultaneous requests are made. Six sources are not
maskable. The remaining sources are maskable, and any one of them
can be given priority over other maskable interrupts.
The priorities of the non-maskable sources are:
1. POR or RESET pin
2. Clock monitor reset
3. COP watchdog reset
4. Unimplemented instruction trap
5. Software interrupt instruction (SWI)
6. XIRQ signal (if X bit in CCR = 0)
Ma ska b le inte rrup ts
Maskable interrupt sources include on-chip peripheral systems and
external interrupt service requests. Interrupts from these sources are
recognized when the global interrupt mask bit (I) in the CCR is cleared. The
default state of the I bit out of reset is one, but it can be written at any time.
Interrupt sources are prioritized by default but any one maskable interrupt
source may be assigned the highest priority by means of the HPRIO
register. The relative priorities of the other sources remain the same.
An interrupt that is assigned highest priority is still subject to global
masking by the I bit in the CCR, or by any associated local bits. Interrupt
vectors are not affected by priority assignment. HPRIO can only be
written while the I bit is set (interrupts inhibited). Table 21 lists interrupt
sources and vectors in default order of priority. Before masking an
interrupt by clearing the corresponding local enable bit, it is required to
set the I-bit to avoid an SWI.
2--reset
MC68HC912DT128A Rev 2.0
116
Resets and Interrupts
MOTOROLA
Resets and Interrupts
Latching of Interrupts
La tc hing of Inte rrup ts
XIRQ is always level triggered and IRQ can be selected as a level
triggered interrupt. These level triggered interrupt pins should only be
released during the appropriate interrupt service routine. Generally the
interrupt service routine will handshake with the interrupting logic to
release the pin. In this way, the MCU will never start the interrupt service
sequence only to determine that there is no longer an interrupt source.
In event that this does occur the trap vector will be taken.
If IRQ is selected as an edge triggered interrupt, the hold time of the level
after the active edge is independent of when the interrupt is serviced. As
long as the minimum hold time is met, the interrupt will be latched inside
the MCU. In this case the IRQ edge interrupt latch is cleared
automatically when the interrupt is serviced.
All of the remaining interrupts are latched by the MCU with a flag bit.
These interrupt flags should be cleared during an interrupt service
routine or when interrupts are masked by the I bit. By doing this, the
MCU will never get an unknown interrupt source and take the trap
vector.
3-reset
MC68HC912DT128A Rev 2.0
MOTOROLA
Resets and Interrupts
117
Re se ts a nd Inte rrup ts
Table 21 Interrupt Vector Map
CCR
HPRIO Value to
Elevate
Vector Address
Interrupt Source
Local Enable
Mask
None
None
None
None
None
X bit
I bit
$FFFE, $FFFF
$FFFC, $FFFD
$FFFA, $FFFB
$FFF8, $FFF9
$FFF6, $FFF7
$FFF4, $FFF5
$FFF2, $FFF3
$FFF0, $FFF1
$FFEE, $FFEF
$FFEC, $FFED
$FFEA, $FFEB
$FFE8, $FFE9
$FFE6, $FFE7
$FFE4, $FFE5
$FFE2, $FFE3
$FFE0, $FFE1
$FFDE, $FFDF
$FFDC, $FFDD
$FFDA, $FFDB
$FFD8, $FFD9
Reset
None
COPCTL (CME, FCME)
COP rate selected
None
–
Clock monitor fail reset
COP failure reset
Unimplemented instruction trap
SWI
–
–
–
None
–
XIRQ
None
–
IRQ
INTCR (IRQEN)
RTICTL (RTIE)
TMSK1 (C0I)
TMSK1 (C1I)
TMSK1 (C2I)
TMSK1 (C3I)
TMSK1 (C4I)
TMSK1 (C5I)
TMSK1 (C6I)
TMSK1 (C7I)
TMSK2 (TOI)
PACTL (PAOVI)
PACTL (PAI)
SP0CR1 (SPIE)
$F2
$F0
$EE
$EC
$EA
$E8
$E6
$E4
$E2
$E0
$DE
$DC
$DA
$D8
Real time interrupt
Timer channel 0
Timer channel 1
Timer channel 2
Timer channel 3
Timer channel 4
Timer channel 5
Timer channel 6
Timer channel 7
Timer overflow
I bit
I bit
I bit
I bit
I bit
I bit
I bit
I bit
I bit
I bit
Pulse accumulator overflow
Pulse accumulator input edge
SPI serial transfer complete
I bit
I bit
I bit
SC0CR2
(TIE, TCIE, RIE, ILIE)
$FFD6, $FFD7
$FFD4, $FFD5
SCI 0
SCI 1
I bit
I bit
$D6
$D4
SC1CR2
(TIE, TCIE, RIE, ILIE)
$FFD2, $FFD3
$FFD0, $FFD1
ATD0 or ATD1
I bit
I bit
ATDxCTL2 (ASCIE)
C0RIER (WUPIE)
$D2
$D0
MSCAN 0 wake-up
KWIEJ[7:0] and
KWIEH[7:0]
$FFCE, $FFCF
Key wake-up J or H
I bit
$CE
$FFCC, $FFCD
$FFCA, $FFCB
Modulus down counter underflow
Pulse Accumulator B Overflow
I bit
I bit
MCCTL (MCZI)
PBCTL (PBOVI)
$CC
$CA
C0RIER (RWRNIE,
TWRNIE,
RERRIE, TERRIE,
BOFFIE, OVRIE)
$FFC8, $FFC9
MSCAN 0 errors
I bit
$C8
$FFC6, $FFC7
$FFC4, $FFC5
$FFC2, $FFC3
$FFC0, $FFC1
$FFBE, $FFBF
MSCAN 0 receive
MSCAN 0 transmit
CGM lock and limp home
IIC Bus
I bit
I bit
I bit
I bit
I bit
C0RIER (RXFIE)
C0TCR (TXEIE[2:0])
PLLCR (LOCKIE, LHIE)
IBCR (IBIE)
$C6
$C4
$C2
$C0
$BE
MSCAN 1 wake-up
C1RIER (WUPIE)
4-reset
MC68HC912DT128A Rev 2.0
118
Resets and Interrupts
MOTOROLA
Resets and Interrupts
Interrupt Control and Priority Registers
Table 21 Interrupt Vector Map
CCR
Mask
HPRIO Value to
Vector Address
Interrupt Source
Local Enable
Elevate
C1RIER (RWRNIE,
TWRNIE,
RERRIE, TERRIE,
$FFBC, $FFBD
MSCAN 1 errors
I bit
$BC
BOFFIE, OVRIE)
$FFBA, $FFBB
$FFB8, $FFB9
MSCAN 1 receive
MSCAN 1 transmit
I bit
I bit
I bit
C1RIER (RXFIE)
C1TCR (TXEIE[2:0])
C2RIER (WUPIE)
$BA
$B8
$B6
$FFB6, $FFB7(1) MSCAN 2 wake-up
C2RIER (RWRNIE,
TWRNIE,
RERRIE, TERRIE,
BOFFIE, OVRIE)
$FFB4, $FFB5(1) MSCAN 2 errors
I bit
$B4
$FFB2, $FFB3(1) MSCAN 2 receive
$FFB0, $FFB1(1) MSCAN 2 transmit
I bit
I bit
I bit
C2RIER (RXFIE)
$B2
$B0
C2TCR (TXEIE[2:0])
$FF80–$FFAF
Reserved
$80–$AE
1. MC68HC912DT128A only
Inte rrup t Control a nd Priority Re g iste rs
INTCR — Interrupt Control Register
$001E
Bit 7
IRQE
0
6
IRQEN
1
5
DLY
1
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
0
0
RESET:
IRQE — IRQ Select Edge Sensitive Only
0 = IRQ configured for low-level recognition.
1 = IRQ configured to respond only to falling edges (on pin PE1/
IRQ).
IRQE can be read anytime and written once in normal modes. In
special modes, IRQE can be read anytime and written anytime,
except the first write is ignored.
IRQEN — External IRQ Enable
The IRQ pin has an internal pull-up.
0 = External IRQ pin is disconnected from interrupt logic.
1 = External IRQ pin is connected to interrupt logic.
IRQEN can be read and written anytime in all modes.
5-reset
MC68HC912DT128A Rev 2.0
MOTOROLA
Resets and Interrupts
119
Re se ts a nd Inte rrup ts
DLY — Enable Oscillator Start-up Delay on Exit from STOP
The delay time of about 4096 cycles is based on the XCLK rate
chosen.
0 = No stabilization delay imposed on exit from STOP mode. A
stable external oscillator must be supplied.
1 = Stabilization delay is imposed before processing resumes after
STOP.
DLY can be read anytime and written once in normal modes. In
special modes, DLY can be read and written anytime.
HPRIO — Highest Priority I Interrupt
$001F
Bit 7
6
PSEL6
1
5
PSEL5
1
4
PSEL4
1
3
PSEL3
0
2
PSEL2
0
1
PSEL1
1
Bit 0
1
1
0
0
RESET:
Write only if I mask in CCR = 1 (interrupts inhibited). Read anytime.
To give a maskable interrupt source highest priority, write the low byte
of the vector address to the HPRIO register. For example, writing $F0 to
HPRIO would assign highest maskable interrupt priority to the real-time
interrupt timer ($FFF0). If an un-implemented vector address or a
non-I-masked vector address (value higher than $F2) is written, then
IRQ will be the default highest priority interrupt.
Inte rrup t te st re g iste rs
These registers are used in special modes for testing the interrupt logic
and priority without needing to know which modules and what functions
are used to generate the interrupts.Each bit is used to force a specific
interrupt vector by writing it to 1.Bits are named with B6 through F4 to
indicate vectors $FFB6 through $FFF4. These bits are also used in
special modes to view that an interrupt caused by a module has reached
the interrupt module.
6-reset
MC68HC912DT128A Rev 2.0
120
Resets and Interrupts
MOTOROLA
Resets and Interrupts
Resets
These registers can only be read in special modes (read in normal mode
will return $00). Reading these registers at the same time as the interrupt
is changing will cause an indeterminate value to be read. These
registers can only be written in special mode.
ITST0 — Interrupt Test Register 0
$0018
$0019
$001A
$001B
Bit 7
ITE6
0
6
ITE8
0
5
ITEA
0
4
ITEC
0
3
ITEE
0
2
ITF0
0
1
ITF2
0
Bit 0
ITF4
0
RESET:
ITST1 — Interrupt Test Register 1
Bit 7
ITD6
0
6
ITD8
0
5
ITDA
0
4
ITDC
0
3
ITDE
0
2
ITE0
0
1
ITE2
0
Bit 0
ITE4
0
RESET:
ITST2 — Interrupt Test Register 2
Bit 7
ITC6
0
6
ITC8
0
5
ITCA
0
4
ITCC
0
3
ITCE
0
2
ITD0
0
1
ITD2
0
Bit 0
ITD4
0
RESET:
ITST3 — Interrupt Test Register 3
Bit 7
ITB6
0
6
ITB8
0
5
ITBA
0
4
ITBC
0
3
ITBE
0
2
ITC0
0
1
ITC2
0
Bit 0
ITC4
0
RESET:
Re se ts
There are four possible sources of reset. Power-on reset (POR), and
external reset on the RESET pin share the normal reset vector. The
computer operating properly (COP) reset and the clock monitor reset
each has a vector. Entry into reset is asynchronous and does not require
a clock but the MCU cannot sequence out of reset without a system
clock.
Powe r-On Re se t
A positive transition on VDD causes a power-on reset (POR). An external
voltage level detector, or other external reset circuits, are the usual
source of reset in a system. The POR circuit only initializes internal
7-reset
MC68HC912DT128A Rev 2.0
MOTOROLA
Resets and Interrupts
121
Re se ts a nd Inte rrup ts
circuitry during cold starts and cannot be used to force a reset as system
voltage drops.
It is important to use an external low voltage reset circuit (for example:
MC34064 or MC33464) to prevent power transitions or corruption of
RAM or EEPROM.
Exte rna l Re se t
The CPU distinguishes between internal and external reset conditions
by sensing whether the reset pin rises to a logic one in less than nine
E-clock cycles after an internal device releases reset. When a reset
condition is sensed, an internal circuit drives the RESET pin low and a
clocked reset sequence controls when the MCU can begin normal
processing. In the case of a clock monitor error, a 4096 cycle oscillator
start-up delay is imposed before the reset recovery sequence starts
(reset is driven low throughout this 4096 cycle delay). The internal reset
recovery sequence then drives reset low for 16 to 17 cycles and releases
the drive to allow reset to rise. Nine E-clock cycles later the reset pin is
sampled. If the pin is still held low, the CPU assumes that an external
reset has occurred. If the pin is high, it indicates that the reset was
initiated internally by either the COP system or the clock monitor.
To prevent a COP reset from being detected during an external reset,
hold the reset pin low for at least 32 cycles. To prevent a clock monitor
reset from being detected during an external reset, hold the reset pin low
for at least 4096 + 32 cycles. An external RC power-up delay circuit on
the reset pin is not recommended — circuit charge time can cause the
MCU to misinterpret the type of reset that has occurred.
COP Re se t
The MCU includes a computer operating properly (COP) system to help
protect against software failures. When COP is enabled, software must
write $55 and $AA (in this order) to the COPRST register in order to keep
a watchdog timer from timing out. Other instructions may be executed
between these writes. A write of any value other than $55 or $AA or
software failing to execute the sequence properly causes a COP reset
to occur. In addition, windowed COP operation can be selected. In this
mode, a write to the COPRST register must occur in the last 25% of the
selected period. A premature write will also reset the part.
8-reset
MC68HC912DT128A Rev 2.0
122
Resets and Interrupts
MOTOROLA
Resets and Interrupts
Effects of Reset
Cloc k Monitor
Re se t
If clock frequency falls below a predetermined limit when the clock
monitor is enabled, a reset occurs.
Effe c ts of Re se t
When a reset occurs, MCU registers and control bits are changed to
known start-up states, as follows.
Op e ra ting Mod e
a nd Me m ory Ma p
Operating mode and default memory mapping are determined by the
states of the BKGD, MODA, and MODB pins during reset. The SMODN,
MODA, and MODB bits in the MODE register reflect the status of the
mode-select inputs at the rising edge of reset. Operating mode and
default maps can subsequently be changed according to strictly defined
rules.
Cloc k a nd
Wa tc hd og Control
Log ic
The COP watchdog system is enabled, with the CR[2:0] bits set for the
longest duration time-out. The clock monitor is disabled. The RTIF flag
is cleared and automatic hardware interrupts are masked. The rate
control bits are cleared, and must be initialized before the RTI system is
used. The DLY control bit is set to specify an oscillator start-up delay
upon recovery from STOP mode.
Inte rrup ts
PSEL is initialized in the HPRIO register with the value $F2, causing the
external IRQ pin to have the highest I-bit interrupt priority. The IRQ pin
is configured for level-sensitive operation (for wired-OR systems).
However, the interrupt mask bits in the CPU12 CCR are set to mask X-
and I-related interrupt requests.
Pa ra lle l I/ O
If the MCU comes out of reset in a single-chip mode, all ports are
configured as general-purpose high-impedance inputs.
If the MCU comes out of reset in an expanded mode, port A and port B
are used for the address/data bus, and port E pins are normally used to
control the external bus (operation of port E pins can be affected by the
9-reset
MC68HC912DT128A Rev 2.0
MOTOROLA
Resets and Interrupts
123
Re se ts a nd Inte rrup ts
PEAR register). Out of reset, port J, port H, port K, port IB, port P, port
S, port T, port AD0 and port AD1 are all configured as general-purpose
inputs.
Ce ntra lProc e ssing
Unit
After reset, the CPU fetches a vector from the appropriate address, then
begins executing instructions. The stack pointer and other CPU registers
are indeterminate immediately after reset. The CCR X and I interrupt
mask bits are set to mask any interrupt requests. The S bit is also set to
inhibit the STOP instruction.
Me m ory
After reset, the internal register block is located from $0000 to $03FF,
RAM is at $2000 to $3FFF, and EEPROM is located at $0800 to $0FFF.
In single chip mode one 32-Kbyte FLASH EEPROM module is located
from $4000 to $7FFF and $C000 to $FFFF, and the other three 32-Kbyte
FLASH EEPROM modules are accessible through the program page
window located from $8000 to $BFFF. The first 32-Kbyte FLASH
EEPROM is also accessible through the program page window.
Othe r Re sourc e s
The enhanced capture timer (ECT), pulse width modulation timer
(PWM), serial communications interfaces (SCI0 and SCI1), serial
peripheral interface (SPI), inter-IC bus (IIC), Motorola Scalable CANs
(MSCAN0 and MSCAN1) and analog-to-digital converters (ATD0 and
ATD1) are off after reset.
Re g iste r Sta c king
Once enabled, an interrupt request can be recognized at any time after
the I bit in the CCR is cleared. When an interrupt service request is
recognized, the CPU responds at the completion of the instruction being
executed. Interrupt latency varies according to the number of cycles
required to complete the instruction. Some of the longer instructions can
be interrupted and will resume normally after servicing the interrupt.
10-reset
MC68HC912DT128A Rev 2.0
124
Resets and Interrupts
MOTOROLA
Resets and Interrupts
Register Stacking
When the CPU begins to service an interrupt, the instruction queue is
cleared, the return address is calculated, and then it and the contents of
the CPU registers are stacked as shown in Table 22.
Table 22 Stacking Order on Entry to Interrupts
Memory Location
SP – 2
CPU Registers
RTNH : RTNL
YH : YL
SP – 4
SP – 6
XH : XL
SP – 8
B : A
SP – 9
CCR
After the CCR is stacked, the I bit (and the X bit, if an XIRQ interrupt
service request is pending) is set to prevent other interrupts from
disrupting the interrupt service routine. The interrupt vector for the
highest priority source that was pending at the beginning of the interrupt
sequence is fetched, and execution continues at the referenced location.
At the end of the interrupt service routine, an RTI instruction restores the
content of all registers from information on the stack, and normal
program execution resumes.
If another interrupt is pending at the end of an interrupt service routine,
the register unstacking and restacking is bypassed and the vector of the
interrupt is fetched.
11-reset
MC68HC912DT128A Rev 2.0
MOTOROLA
Resets and Interrupts
125
Re se ts a nd Inte rrup ts
12-reset
MC68HC912DT128A Rev 2.0
126
Resets and Interrupts
MOTOROLA
I/ O Ports With Ke y Wa ke -Up
I/ O Ports With Ke y Wa ke -Up
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Key Wake-up and port Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Key Wake-Up Input Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Introd uc tion
The offers 16 additional I/O ports with key wake-up capability.
The key wake-up feature of the MC68HC912DT128A issues an interrupt
that will wake up the CPU when it is in the STOP or WAIT mode. Two
ports are associated with the key wake-up function: port H and port J.
Port H and port J wake-ups are triggered with a either a rising or falling
signal edge. For each pin which has an interrupt enabled, there is a path
to the interrupt request signal which has no clocked devices when the
part is in stop mode. This allows an active edge to bring the part out of
stop.
Digital filtering is included to prevent pulses shorter than a specified
value from waking the part from STOP.
An interrupt is generated when a bit in the KWIFH or KWIFJ register and
its corresponding KWIEH or KWIEJ bit are both set. All 16 bits/pins
share the same interrupt vector. Key wake-ups can be used with the pins
configured as inputs or outputs.
Default register addresses, as established after reset, are indicated in
the following descriptions. For information on re-mapping the register
block, refer to Operating Modes.
1-kwu
MC68HC912DT128A Rev 2.0
MOTOROLA
I/O Ports With Key Wake-Up
127
I/ O Ports With Ke y Wa ke -Up
Ke y Wa ke -up a nd p ort Re g iste rs
PORTJ — Port J Register
$0028
$0029
$002A
Bit 7
PJ7
KWJ7
-
6
PJ6
KWJ6
-
5
PJ5
KWJ5
-
4
PJ4
KWJ4
-
3
PJ3
KWJ3
-
2
PJ2
KWJ2
-
1
PJ1
KWJ1
-
Bit 0
PJ0
KWJ0
-
PORT
KWU
RESET:
Read and write anytime.
PORTH — Port H Register
Bit 7
PH7
6
5
PH5
KWH5
-
4
PH4
KWH4
-
3
PH3
KWH3
-
2
PH2
KWH2
-
1
PH1
KWH1
-
Bit 0
PH0
KWH0
-
PH6
KWU
KWH7
-
KWH6
-
RESET:
Read and write anytime.
DDRJ — Port J Data Direction Register
Bit 7
DDJ7
0
6
DDJ6
0
5
DDJ5
0
4
DDJ4
0
3
DDJ3
0
2
DDJ2
0
1
DDJ1
0
Bit 0
DDJ0
0
RESET:
Data direction register J is associated with port J and designates each
pin as an input or output.
Read and write anytime
DDRJ[7:0] — Data Direction Port J
0 = Associated pin is an input
1 = Associated pin is an output
2--kwu
MC68HC912DT128A Rev 2.0
128
I/O Ports With Key Wake-Up
MOTOROLA
I/O Ports With Key Wake-Up
Key Wake-up and port Registers
DDRH — Port H Data Direction Register
$002B
Bit 7
DDH7
0
6
DDH6
0
5
DDH5
0
4
DDH4
0
3
DDH3
0
2
DDH2
0
1
DDH1
0
Bit 0
DDH0
0
RESET:
Data direction register H is associated with port H and designates each
pin as an input or output. Read and write anytime.
DDRH[7:0] — Data Direction Port H
0 = Associated pin is an input
1 = Associated pin is an output
KWIEJ — Key Wake-up Port J Interrupt Enable Register
$002C
Bit 7
KWIEJ7
0
6
KWIEJ6
0
5
KWIEJ5
0
4
KWIEJ4
0
3
KWIEJ3
0
2
KWIEJ2
0
1
KWIEJ1
0
Bit 0
KWIEJ0
0
RESET:
Read and write anytime.
KWIEJ[7:0] — Key Wake-up Port J Interrupt Enables
0 = Interrupt for the associated bit is disabled
1 = Interrupt for the associated bit is enabled
KWIEH — Key Wake-up Port H Interrupt Enable Register
$002D
Bit 7
KWIEH7
0
6
KWIEH6
0
5
KWIEH5
0
4
KWIEH4
0
3
KWIEH3
0
2
KWIEH2
0
1
KWIEH1
0
Bit 0
KWIEH0
0
RESET:
Read and write anytime.
KWIEH[7:0] — Key Wake-up Port H Interrupt Enables
0 = Interrupt for the associated bit is disabled
1 = Interrupt for the associated bit is enabled
3-kwu
MC68HC912DT128A Rev 2.0
129
MOTOROLA
I/O Ports With Key Wake-Up
I/ O Ports With Ke y Wa ke -Up
KWIFJ — Key Wake-up Port J Flag Register
$002E
Bit 7
KWIFJ7
0
6
KWIFJ6
0
5
KWIFJ5
0
4
KWIFJ4
0
3
KWIFJ3
0
2
KWIFJ2
0
1
KWIFJ1
0
Bit 0
KWIFJ0
0
RESET:
Read and write anytime.
Each flag is set by an active edge on its associated input pin. This could
be a rising or falling edge based on the state of the KWPJ register. To
clear the flag, write one to the corresponding bit in KWIFJ.
Initialize this register after initializing KWPJ so that illegal flags can be
cleared.
KWIFJ[7:0] — Key Wake-up Port J Flags
0 = Active edge on the associated bit has not occurred
1 = Active edge on the associated bit has occurred (an interrupt will
occur if the associated enable bit is set).
KWIFH — Key Wake-up Port H Flag Register
$002F
Bit 7
KWIFH7
0
6
KWIFH6
0
5
KWIFH5
0
4
KWIFH4
0
3
KWIFH3
0
2
KWIFH2
0
1
KWIFH1
0
Bit 0
KWIFH0
0
RESET:
Read and write anytime.
Each flag is set by an active edge on its associated input pin. This could
be a rising or falling edge based on the state of the KWPH register. To
clear the flag, write one to the corresponding bit in KWIFH.
Initialize this register after initializing KWPH so that illegal flags can be
cleared.
KWIFH[7:0] — Key Wake-up Port H Flags
0 = Active edge on the associated bit has not occurred
1 = Active edge on the associated bit has occurred (an interrupt will
occur if the associated enable bit is set)
4-kwu
MC68HC912DT128A Rev 2.0
130
I/O Ports With Key Wake-Up
MOTOROLA
I/O Ports With Key Wake-Up
Key Wake-up and port Registers
KWPJ — Key Wake-up Port J Polarity Register
$0030
Bit 7
KWPJ7
0
6
KWPJ6
0
5
KWPJ5
0
4
KWPJ4
0
3
KWPJ3
0
2
KWPJ2
0
1
KWPJ1
0
Bit 0
KWPJ0
0
RESET:
Read and write anytime. It is best to clear the flags after initializing this
register because changing the polarity of a bit can cause the associated
flag to become set.
KWPJ[7:0] — Key Wake-up Port J Polarity Selects
0 = Falling edge on the associated port J pin sets the associated
flag bit in the KWIFJ register and a resistive pull-up device is
connected to associated port J input pin.
1 = Rising edge on the associated port J pin sets the associated
flag bit in the KWIFJ register and a resistive pull-down device
is connected to associated port J input pin.
KWPH — Key Wake-up Port H Polarity Register
$0031
Bit 7
KWPH7
0
6
KWPH6
0
5
KWPH5
0
4
KWPH4
0
3
KWPH3
0
2
KWPH2
0
1
KWPH1
0
Bit 0
KWPH0
0
RESET:
Read and write anytime. It is best to clear the flags after initializing this
register because changing the polarity of a bit can cause the associated
flag to become set.
KWPH[7:0] — Key Wake-up Port H Polarity Selects
0 = Falling edge on the associated port H pin sets the associated
flag bit in the KWIFH register and a resistive pull-up device is
connected to associated port H input pin.
1 = Rising edge on the associated port H pin sets the associated
flag bit in the KWIFH register and a resistive pull-down device
is connected to associated port H input pin.
5-kwu
MC68HC912DT128A Rev 2.0
MOTOROLA
I/O Ports With Key Wake-Up
131
I/ O Ports With Ke y Wa ke -Up
Ke y Wa ke -Up Inp ut Filte r
The KWU input signals are filtered by a digital filter which is active only
during STOP mode.
The purpose of the filter is to prevent single pulses shorter than a
specified value from waking the part from STOP.
The filter is composed of an internal oscillator and a majority voting logic.
The filter oscillator starts the oscillation by detecting a triggering edge on
an input if the corresponding interrupt enable bit is set.
The majority voting logic takes three samples of an asserted input pin at
each filter oscillator period and if two samples are taken at the triggering
level, the filter recognizes a valid triggering level and sets the
corresponding interrupt flag. In this way the majority voting logic rejects
the short non-triggering state between two incoming triggering pulses.
As the filter is shared with all KWU inputs, the filter considers any pulse
coming from any input pin for which the corresponding interrupt enable
bit is set.
The timing specification is given for a single pulse. The time interval
between the triggering edges of two following pulses should be greater
than the tKWSP in order to be considered as a single pulse by the filter.
If this time interval is shorter than tKWSP, the majority voting logic may
treat the two consecutive pulses as a single valid pulse.
The filter is shared by all the KWU pins. Hence any valid triggering level
on any KWU pin is seen by the filter. The timing specification applies to
the input of the filter.
6-kwu
MC68HC912DT128A Rev 2.0
132
I/O Ports With Key Wake-Up
MOTOROLA
I/O Ports With Key Wake-Up
Key Wake-Up Input Filter
Glitch, filtered out, no STOP wake-up
Valid STOP Wake-Up pulse
tKWSTP min.
tKWSTP max.
Minimum time interval between pulses to be recognized as single pulses
tKWSP
Figure 12 STOP Key Wake-up Filter
7-kwu
MC68HC912DT128A Rev 2.0
133
MOTOROLA
I/O Ports With Key Wake-Up
I/ O Ports With Ke y Wa ke -Up
8-kwu
MC68HC912DT128A Rev 2.0
134
I/O Ports With Key Wake-Up
MOTOROLA
Cloc k Func tions
Cloc k Func tions
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Clock Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Phase-Locked Loop (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Acquisition and Tracking Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Limp-Home and Fast STOP Recovery modes . . . . . . . . . . . . . . . . . 141
System Clock Frequency Formulae . . . . . . . . . . . . . . . . . . . . . . . . . 159
Clock Divider Chains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Computer Operating Properly (COP) . . . . . . . . . . . . . . . . . . . . . . . . 163
Real-Time Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Clock Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Clock Function Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Introd uc tion
Clock generation circuitry generates the internal and external E-clock
signals as well as internal clock signals used by the CPU and on-chip
peripherals. A clock monitor circuit, a computer operating properly
(COP) watchdog circuit, and a periodic interrupt circuit are also
incorporated into the MC68HC912DT128A.
1-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
135
Cloc k Func tions
Cloc k Sourc e s
A compatible external clock signal can be applied to the EXTAL pin or
the MCU can generate a clock signal using an on-chip oscillator circuit
and an external crystal or ceramic resonator. The MCU uses several
types of internal clock signals derived from the primary clock signal:
TxCLK clocks are used by the CPU.
ECLK and PCLK are used by the bus interfaces, SPI, PWM, ATD0 and
ATD1.
MCLK is either PCLK or XCLK, and drives on-chip modules such as
SCI0, SCI1 and ECT.
XCLK drives on-chip modules such as RTI, COP and restart-from-stop
delay time.
SLWCLK is used as a calibration output signal.
The MSCAN module is clocked by EXTALi or SYSCLK, under control of
an MSCAN bit.
The clock monitor is clocked by EXTALi.
The BDM system is clocked by BCLK or ECLK, under control of a BDM
bit.
A slow mode clock divider is included to deliver a lower clock frequency
for the SCI baud rate generators, the ECT timer module, and the RTI and
COP clocks. The slow clock bus frequencies divide the crystal frequency
in a programmable range of 4 to 252, with steps of 4. This is very useful
for low power operation.
See the Clock Divider Chains section for further details. Figure 13 shows
some of the timing relationships.
2--clock
MC68HC912DT128A Rev 2.0
136
Clock Functions
MOTOROLA
Clock Functions
Phase-Locked Loop (PLL)
T1CLK
T2CLK
T3CLK
T4CLK
INT ECLK
PCLK
XCLK
CANCLK
Figure 13 Internal Clock Relationships
Pha se -Loc ke d Loop (PLL)
The phase-locked loop (PLL) of the 68HC912D60A is designed for
robust operation in an Automotive environment. The proposed PLL
crystal or ceramic resonator reference of 0.5 to 8MHz is selected for the
wide availability of components with good stability in the desired
temperature range. Please refer to Figure 18 in section Clock Divider
Chains for an overview of system clocks.
An oscillator design with reduced power consumption allows for slow
wait operation with a typical power supply current lower than a
milli-ampere. The PLL circuitry can be bypassed when the VDDPLL
supply is at VSS level. In this case the oscillator output transistor has a
stronger transconductance, for a crystal at twice the bus frequency.
Refer to Figure 7 in Pinout and Signal Descriptions.
3-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
137
Cloc k Func tions
EXTAL
LOCK
LOCK
DETECTOR
REFDV <2:0>
REDUCED
CONSUMPTION
OSCILLATOR
REFERENCE
PROGRAMMABLE
DIVIDER
REFCLK
DIVCLK
UP
PDET
PHASE
DETECTOR
XTAL
CPUMP
VCO
DOWN
EXTALi
VDDPLL
SLOW MODE
PROGRAMMABLE
CLOCK DIVIDER
LOOP
PROGRAMMABLE
DIVIDER
SLWCLK
LOOP
FILTER
XFC
PAD
÷2
× 2
SLDV <5:0>
SYN <5:0>
EXTALi
PLLCLK
XCLK
Figure 14 PLL Functional Diagram
The PLL may be used to run the MCU from a different time base than the
incoming crystal value. It creates an integer multiple of a reference
frequency. For increased flexibility, the crystal clock can be divided by
values in a range of 1 – 8 (in unit steps) to generate the reference
frequency. The PLL can multiply this reference clock in a range of 1 to
64. Although it is possible to set the divider to command a very high clock
frequency, do not exceed the specified bus frequency limit for the MCU.
If the PLL is selected, it will continue to run when in WAIT mode resulting
in more power consumption than normal. To take full advantage of the
reduced power consumption of WAIT mode, turn off the PLL before
going into WAIT. Please note that in this case the PLL stabilization time
applies.
The PLL operation is suspended in STOP mode. After STOP exit
followed by the stabilization time, it resumes operation at the same
frequency, provided the AUTO bit is set.
A passive external loop filter must be placed on the control line (XFC
pad). The filter is a second-order, low-pass filter to eliminate the VCO
input ripple. Values of components in the diagram are dependent upon
the desired VCO operation. See XFC description.
4-clock
MC68HC912DT128A Rev 2.0
138
Clock Functions
MOTOROLA
Clock Functions
Acquisition and Tracking Modes
Ac q uisition a nd Tra c king Mod e s
The lock detector compares the frequencies of the VCO feedback clock,
DIVCLK, and the final reference clock, REFCLK. Therefore, the speed
of the lock detector is directly proportional to the final reference
frequency. The circuit determines the mode of the PLL and the lock
condition based on this comparison.
The PLL filter is manually or automatically configurable into one of two
operating modes:
•
Acquisition mode — In acquisition mode, the filter can make large
frequency corrections to the VCO. This mode is used at PLL
start-up or when the PLL has suffered a severe noise hit and the
VCO frequency is far off the desired frequency. This mode can
also be desired in harsh environments when the leakage levels on
the filter pin (XFC) can overcome the tracking currents of the PLL
charge pump. When in acquisition mode, the ACQ bit in the PLL
control register is clear.
•
Tracking mode — In tracking mode, the filter makes only small
corrections to the frequency of the VCO. The PLL enters tracking
mode when the VCO frequency is nearly correct. The PLL is
automatically in tracking mode when not in acquisition mode or
when the ACQ bit is set.
The PLL can change the bandwidth or operational mode of the loop filter
manually or automatically. With an identical filtering time constant, the
PLL bandwidth is larger in acquisition mode than in tracking by a ratio of
about 3.
In automatic bandwidth control mode (AUTO = 1), the lock detector
automatically switches between acquisition and tracking modes.
Automatic bandwidth control mode also is used to determine when the
VCO clock, PLLCLK, is safe to use as the source for the base clock,
SYSCLK. If PLL LOCK interrupt requests are enabled, the software can
wait for an interrupt request and then check the LOCK bit. If CPU
interrupts are disabled, software can poll the LOCK bit continuously
(during PLL start-up, usually) or at periodic intervals. In either case,
when the LOCK bit is set, the PLLCLK clock is safe to use as the source
5-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
139
Cloc k Func tions
for the base clock. See Clock Divider Chains. If the VCO is selected as
the source for the base clock and the LOCK bit is clear, the PLL has
suffered a severe noise hit and the software must take appropriate
action, depending on the application.
The following conditions apply when the PLL is in automatic bandwidth
control mode:
•
•
The ACQ bit is a read-only indicator of the mode of the filter.
The ACQ bit is set when the VCO frequency is within a certain
tolerance, ∆trk, and is cleared when the VCO frequency is out of a
certain tolerance, ∆unt. See 19 Electrical Characteristics.
•
•
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 a certain
tolerance, ∆Lock, and is cleared when the VCO frequency is out of
a certain tolerance, ∆unl. See 19 Electrical Characteristics.
•
CPU interrupts can occur if enabled (LOCKIE = 1) when the lock
condition changes, toggling the LOCK bit.
The PLL also can operate in manual mode (AUTO = 0). All LOCK
features described above are active in this mode, only the bandwidth
control is disabled. Manual mode is used mainly for systems operating
under harsh conditions (e.g.uncoated PCBs in automotive
environments). When this is the case, the PLL is likely to remain in
acquisition mode. The following conditions apply when in manual mode:
•
ACQ is a writable control bit that controls the mode of the filter.
Before turning on the PLL in manual mode, the ACQ bit must be
clear.
•
In case tracking is desired (ACQ = 1), the software must wait a
given time, tacq, after turning on the PLL by setting PLLON in the
PLL control register. This is to avoid switching to tracking mode
too early while the XFC voltage level is still too far away from its
quiescent value corresponding to the target frequency. This
operation would be very detrimental to the stabilization time.
6-clock
MC68HC912DT128A Rev 2.0
140
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
Lim p -Hom e a nd Fa st STOP Re c ove ry m od e s
If the crystal frequency is not available due to a crystal failure or a long
crystal start-up time, the MCU system clock can be supplied by the VCO
at its minimum operating frequency, f VCOMIN. This mode of operation is
called Limp-Home Mode and is only available when the VDDPLL supply
voltage is at VDD level (i.e. power supply for the PLL module is present).
Upon power-up, the ability of the system to start in Limp-Home Mode is
restricted to normal MCU modes only.
The Clock Monitor circuit (see section Clock Monitor) can detect the loss
of EXTALi, the external clock input signal, regardless of whether this
signal is used as the source for MCU clocks or as the PLL reference
clock. The clock monitor control bits, CME and FCME, are used to
enable or disable external clock detection.
A missing external clock may occur in the three following instances:
•
•
•
During normal clock operation.
At Power-On Reset.
In the STOP exit sequence
Cloc k Loss d uring
Norm a l Ope ra tion
The ‘no limp-home mode’ bit, NOLHM, determines how the MCU
responds to an external clock loss in this case.
With limp home mode disabled (NOLHM bit set) and the clock monitor
enabled (CME or FCME bits set), on a loss of clock the MCU is reset via
the clock monitor reset vector. This is the same behavior as standard
M68HC12 circuits without PLL or operation with VDDPLL at VSS level.
With limp home mode enabled (NOLHM bit cleared) and the clock
monitor enabled (CME or FCME bits set), on a loss of clock, the PLL
VCO clock at its minimum frequency, f VCOMIN, is provided as the system
clock, allowing the MCU to continue operating.
The MCU is said to be operating in “limp-home” mode with the forced
VCO clock as the system clock. PLLON and BCSP (‘bus clock select
PLL’) signals are forced high and the MCS (‘module clock select’) signal
7-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
141
Cloc k Func tions
is forced low. The LHOME flag in the PLLFLG register is set to indicate
that the MCU is running in limp-home mode. A change of this flag sets
the limp-home interrupt flag, LHIF, and if enabled by the LHIE bit, the
limp-home mode interrupt is requested. The Clock Monitor is enabled
irrespective of CME and FCME bit settings. Module clocks to the RTI &
COP (XCLK), BDM (BCLK) and ECT & SCI (MCLK) are forced to be
PCLK (at f VCOMIN) and ECLK is also equal to f VCOMIN. MSCAN clock
select is unaffected.
EXTALi
A
B
Clock Monitor Fail
0 --> 4096
0 --> 4096
13-stage counter
(Clocked by XCLK)
Limp-Home
BCSP
Restore BCSP
PLLCLK (Limp-Home)
SYSCLK
Restore PLLCLK or EXTALi
Figure 15 Clock Loss during Normal Operation
The clock monitor is polled each time the 13-stage free running counter
reaches a count of 4096 XCLK cycles i.e. mid-count, hence the clock
status gets checked once every 8192 XCLK cycles. When the presence
of an external clock is detected, the MCU exits limp-home mode,
clearing the LHOME flag and setting the limp-home interrupt flag. Upon
leaving limp-home mode, BCSP and MCS signals are restored to their
values before the clock loss. All clocks return to their normal settings and
Clock Monitor control is returned to the CME & FCME bits. If AUTO and
BCSP bits were set before the clock loss (selecting the PLL to provide a
system clock) the SYSCLK ramps-up and the PLL locks at the previously
selected frequency. To prevent PLL operation when the external clock
8-clock
MC68HC912DT128A Rev 2.0
142
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
frequency comes back, software should clear the BCSP bit while running
in limp-home mode.
The two shaded regions A and B in Figure 15 present a of code run
away due to incorrect clocks on SYSCLK if the MCU is clocked by
EXTALi and the PLL is not used.
In region A, there is a delay between the loss of clock and its detection
by the clock monitor. When the EXTALi clock signal is disturbed, the
clock generation circuitry may receive an out of spec signal and drive the
CPU with irregular clocks. This may lead to code runaway.
In region B, as the 13-stage counter is free running, the count of 4096
may be reached when the amplitude of the EXTALi clock has not
stabilized. In this case, an improper EXTALi is sent to the clock
generation circuitry when limp-home mode is exited. This may also
cause code runaway.
If the MCU is clocked by the PLL, the risk of code runaway is very
low, but it can still occur under certain conditions due to irregular
clocks from the clock source appearing on the SYSCLK.
CAUTION: The COP watch dog should always be enabled in order to reset the MCU
in case of a code runaway situation.
NOTE: It is always advisable to take additional precautions within the
application software to trap such situations.
9-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
143
Cloc k Func tions
No Cloc k a t
Powe r-On Re se t
The voltage level on VDDPLL determines how the MCU responds to an
external clock loss in this case.
With the VDDPLL supply voltage at VDD level, any reset sets the Clock
Monitor Enable bit (CME) and the PLLON bit and clears the NOLHM bit.
Therefore, if the MCU is powered up without an external clock,
limp-home mode is entered provided the MCU is in a normal mode of
operation.
VDD
Power-On Detector
EXTALi
(Slow EXTALi)
Clock Monitor Fail
Limp-Home
0 --> 4096
0 --> 4096
13-stage counter
(Clocked by XCLK)
BCSP
Reset: BCSP = 0
Internal reset
SYSCLK
PLLCLK (L.H.)
EXTALi
SYSCLK
PLLCLK (Software check of Limp-Home Flag)
EXTALi
(Slow EXTALi)
Figure 16 No Clock at Power-On Reset
10-clock
MC68HC912DT128A Rev 2.0
144
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
During this power up sequence, after the POR pulse falling edge, the
VCO supplies the limp-home clock frequency to the 13-stage counter, as
the BCSP output is forced high and MCS is forced low. XCLK, BCLK and
MCLK are forced to be PCLK, which is supplied by the VCO at fVCOMIN
.
The initial period taken for the 13-stage counter to reach 4096 defines
the internal reset period.
If the clock monitor indicates the presence of an external clock during the
internal reset period, limp-home mode is de-asserted and the 13-stage
counter is then driven by EXTALi clock. After the 13-stage counter
reaches a count of 4096 XCLK cycles, the internal reset is released, the
13-stage counter is reset and the MCU exits reset normally using
EXTALi clock.
However, if the crystal start-up time is longer than the initial count of
4096 XCLK cycles, or in the absence of an external clock, the MCU will
leave the reset state in limp-home mode. The LHOME flag is set and
LHIF limp-home interrupt request is set, to indicate it is not operating at
the desired frequency. Then after yet another 4096 XCLK cycles
followed regularly by 8192 XCLK cycles (corresponding to the 13-stage
counter timing out), a check of the clock monitor status is performed.
When the presence of an external clock is detected limp-home mode is
exited generating a limp-home interrupt if enabled.
CAUTION: The clock monitor circuit can be misled by the EXTALi clock into
reporting a good signal before it has fully stabilised. Under these
conditions improper EXTALi clock cycles can occur on SYSCLK. This
may lead to a code runaway. To ensure that this situation does not
occur, the external Reset period should be longer than the oscillator
stabilisation time - this is an application dependent parameter.
With the VDDPLL supply voltage at VSS level, the PLL module and
hence limp-home mode are disabled, the device will remain effectively
in a static state whilst there is no activity on EXTALi. The internal reset
period and MCU operation will execute only on EXTALi clock.
NOTE: The external clock signal must stabilise within the initial 4096 reset
counter cycles.
11-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
145
Cloc k Func tions
STOP Exit a nd Fa st
STOP Re c ove ry
Stop mode is entered when a STOP instruction is executed. Recovery
from STOP depends primarily on the state of the three status bits
NOLHM, CME & DLY.
The DLY bit controls the duration of the waiting period between the
actual exit for some key blocks (e.g. clock monitor, clock generators) and
the effective exit from stop for all the rest of the MCU. DLY=1 enables
the 13-stage counter to generate a 4096 count delay. DLY=0 selects no
delay. As the XCLK is derived from the slow mode divider, the value in
the SLOW register modifies the actual delay time.
NOTE: DLY=0 is only recommended when there is a good signal available
at the EXTAL pin (e.g. an external square wave source).
STOP mode is exited with an external reset, an external interrupt from
IRQ or XIRQ, a Key Wake-Up interrupt from port J or port H, or an
MSCAN Wake-Up interrupt.
EXTALi
Clock Monitor Fail
Limp-Home
0 --> 4096
13-stage counter
(Clocked by XCLK)
BCSP
Restore BCSP
STOP (DLY = 1)
STOP (DLY = 0)
SYSCLK
PLLCLK (L.H.) Restore PLLCLK or EXTALi
Figure 17 STOP Exit and Fast STOP Recovery
12-clock
MC68HC912DT128A Rev 2.0
146
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
STOP e xit without
Lim p Hom e m od e ,
c loc k m onitor
d isa b le d
(NOLHM=1, CME=0, DLY=X)
If Limp home mode is disabled (VDDPLL=VSS or NOLHM bit set) and the
CME (or FCME) bit is cleared, the MCU goes into STOP mode when a
STOP instruction is executed.
If EXTALi clock is present then exit from STOP will occur normally using
this clock. Under this condition, DLY should always be set to allow the
crystal to stabilise and minimise the risk of code runaway. With DLY=1
execution resumes after a delay of 4096 XCLK cycles.
NOTE: The external clock signal should stabilise within the 4096 reset counter
cycles. Use of DLY=0 is not recommended due to this requirement.
Exe c uting the
(NOLHM=1, CME=1, DLY=X)
STOP instruc tion
without Lim p
Hom e m od e ,
c loc k m onitor
e na b le d
If the NOLHM bit and the CME (or FCME) bits are set, a clock monitor
failure is detected when a STOP instruction is executed and the MCU
resets via the clock monitor reset vector.
STOP e xit in Lim p
Hom e m od e with
De la y
(NOLHM=0, CME=X, DLY=1)
If the NOLHM bit is cleared, then the CME (or FCME) bit is masked when
a STOP instruction is executed to prevent a clock monitor failure. When
coming out of STOP mode, the MCU goes into limp-home mode where
CME and FCME signals are asserted.
When using a crystal oscillator, a normal STOP exit sequence requires
the DLY bit to be set to allow for the crystal stabilization period.
With the 13-stage counter clocked by the VCO (at fVCOMIN), following a
delay of 4096 XCLK cycles at the limp-home frequency, if the clock
monitor indicates the presence of an external clock, the limp-home mode
is de-asserted and the MCU exits STOP normally using EXTALi clock.
Where the crystal start-up time is longer than the initial count of 4096
XCLK cycles, or in the absence of an external clock, the MCU recovers
from STOP following the 4096 count in limp-home mode with both the
LHOME flag set and the LHIF limp-home interrupt request set to indicate
13-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
147
Cloc k Func tions
it is not operating at the desired frequency. Each time the 13-stage
counter reaches a count of 4096 XCLK cycles, a check of the clock
monitor status is performed.
When the presence of an external clock is detected, limp-home mode is
exited and the LHOME flag is cleared. This sets the limp-home interrupt
flag and if enabled by the LHIE bit, the limp-home mode interrupt is
requested.
CAUTION: The clock monitor circuit can be misled by EXTALi clock into reporting a
good signal before it has fully stabilised. Under these conditions,
improper EXTALi clock cycles can occur on SYSCLK. This may lead to
a code runaway.
STOP exit in Limp
(NOLHM=0, CME=X, DLY=0)
Home mode
without Delay
(Fast Stop
Fast STOP recovery refers to any exit from STOP using DLY=0.
If the NOLHM bit is cleared, then the CME (or FCME) bit is masked when
a STOP instruction is executed to prevent a clock monitor failure. When
coming out of STOP mode, the MCU goes into limp-home mode where
CME and FCME signals are asserted.
Recovery)
When using a crystal oscillator, it is possible to exit STOP with the DLY
bit cleared. In this case, STOP is de-asserted without delay and the MCU
will execute software in limp-home mode, giving the crystal oscillator
time to stablise.
CAUTION: This mode is not recommended since the risk of the clock monitor
detecting incorrect clocks is high.
14-clock
MC68HC912DT128A Rev 2.0
148
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
Each time the 13-stage counter reaches a count of 4096 XCLK cycles
(every 8192 cycles), a check of the clock monitor status is performed. If
the clock monitor indicates the presence of an external clock limp-home
mode is de-asserted, the LHOME flag is cleared and the limp-home
interrupt flag is set. Upon leaving limp-home mode, BCSP and MCS are
restored to their values before the loss of clock, and all clocks return to
their previous frequencies. If AUTO and BCSP were set before the clock
loss, the SYSCLK ramps-up and the PLL locks at the previously selected
frequency.
To prevent PLL operation when the external clock frequency comes
back, the software should clear the BCSP bit while running in limp-home
mode.
When using an external clock, i.e. a square wave source, it is possible
to exit STOP with the DLY bit cleared. In this case the LHOME flag is
never set and STOP is de-asserted without delay.
Pse ud o-STOP
Pseudo-STOP is a low power mode similar to STOP where the external
oscillator is allowed to run (at reduced amplitude) whilst the rest of the
part is in STOP. This increases the current consumption over STOP
mode by the amount of current in the oscillator, but reduces wear and
mechanical stress on the crystal.
If the PSTP bit in the PLLCR register is set, the MCU goes into
Pseudo-STOP mode when a STOP instruction is executed.
Pseudo-STOP mode is exited the same as STOP with an external reset,
an external interrupt from IRQ or XIRQ, a Key Wake-Up interrupt from
port J or port H, or an MSCAN Wake-Up interrupt.
The effect of the DLY bit is the same as noted above in STOP Exit and
Fast STOP Recovery.
15-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
149
Cloc k Func tions
Pse ud o-STOP e xit
in Lim p Hom e
m od e with De la y
(NOLHM=0, CME=X, DLY=1)
When coming out of Pseudo-STOP mode with the NOLHM bit cleared
and the DLY bit set, the MCU goes into limp-home mode (regardless of
the state of the CME or FCME bits).
The VCO supplies the limp-home clock frequency to the 13-stage
counter (XCLK). The BCSP output is forced high and MCS is forced low.
After the 13-stage counter reaches a count of 4096 XCLK cycles, a
check of the clock monitor is performed and as the crystal oscillator was
kept running due to the Pseudo-stop mode, the MCU exits STOP
normally, using the EXTALi clock. In the case where a crystal failure
occurred during pseudo-stop, then the MCU exits STOP using the limp
home clock (fVCOMIN) with both the LHOME flag set and the LHIF
limp-home interrupt request set to indicate it is not operating at the
desired frequency. Each time the 13-stage counter reaches a count of
4096 XCLK cycles, a check of the clock monitor is performed. If the clock
monitor indicates the presence of an external clock, limp-home mode is
de-asserted, the LHOME flag is cleared and the LHIF limp-home
interrupt request is set to indicate a return to normal operation using
EXTALi clock.
Pseudo-STOP exit
in Limp Home
mode without
Delay (Fast Stop
Recovery)
(NOLHM=0, CME=X, DLY=0)
If Pseudo-STOP is exited with the NOLHM bit set to 0 and the DLY bit is
cleared then the exit from Pseudo-STOP is accomplished without delay
as in Fast STOP recovery.
CAUTION: Where Pseudo-STOP recovers using the Limp Home Clock the VCO -
which has been held in STOP - must be restarted in order to supply the
limp home frequency. This restart, which occurs at a high frequency and
ramps toward the limp home frequency, is almost immediately supplied
to the CPU before it may have reached the steady state frequency. It is
possible that the initial clock frequency may be high enough to cause the
CPU to function incorrectly with a resultant risk of code runaway.
16-clock
MC68HC912DT128A Rev 2.0
150
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
Pse ud o-STOP e xit
without Lim p
Hom e m od e ,
c loc k m onitor
e na b le d
(NOLHM=1, CME=1, DLY=X)
If the NOLHM bit is set and the CME (or FCME) bits are set, a clock
monitor failure is detected when a STOP instruction is executed and the
MCU resets via the clock monitor reset vector.
Pse ud o-STOP e xit
without Lim p
Hom e m od e ,
c loc k m onitor
d isa b le d
(NOLHM=1, CME=0, DLY=1)
If NOLHM is set to 1 and the CME and FCME bits are cleared, the limp
home clock is not used. In this mode, crystal activity is the only method
by which the device may recover from Pseudo-STOP. The device will
start execution with the EXTALi clock following 4096 XCLK cycles.
(NOLHM=1, CME=0, DLY=0)
If NOLHM is set to 1 and the CME and FCME bits are cleared, the limp
home clock is not used. In this mode, crystal activity is the only method
by which the device may recover from Pseudo-STOP. The device will
start execution with the EXTALi clock following 16 XCLK cycles.
CAUTION: Due to switching of the clock this configuration is not recommended.
Sum m a ry of STOP
a nd p se ud o-STOP
Mod e Exit
Table 23 and Table 24 summarise the exit conditions from STOP and
pseudo-STOP modes using Interrupt, Key-interrupt and XIRQ.
A short RESET pulse should not be used to exit stop or pseudo-STOP
mode because Limp Home mode is automatically entered after RESET
(when VDDPLL=VDD). The RESET wakeup pulse must be longer than the
oscillator startup time (as in power on reset) in order to remove the risk
of code runaway.
Cond itions
17-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
151
Cloc k Func tions
. .
Table 23 Summary of STOP Mode Exit Conditions
Mode
Conditions
Summary
STOP exit without Limp Home
mode,
NOLHM=1
CME=0
Oscillator must be stable within 4096 XCLK cycles. XCLK
can be modified by SLOW divider register.
clock monitor disabled
DLY=X
Use of DLY=0 only recommended with external clock.
Executing the STOP instruction
without Limp Home mode, clock
monitor enabled
NOLHM=1
CME=1
DLY=X
When a STOP instruction is executed the MCU resets via
the clock monitor reset vector.
Oscillator must be stable within 4096
NOLHM=0
CME=X
DLY=1
STOP exit in Limp Home mode
with Delay
fVCOMIN cycles or there is a possibility of code runaway as
the clock monitor circuit can be misled by EXTALi clock into
reporting a good signal before it has fully stabilised
STOP exit in Limp Home mode
without Delay (Fast Stop
Recovery)
NOLHM=0
CME=X
DLY=0
This mode is only recommended for use with an external
clock source.
Table 24 Summary of Pseudo STOP Mode Exit Conditions
Mode
Conditions
Summary
CPU exits stop in limp home mode and oscillator running. If
the oscillator fails during pseudo-STOP and then recovers
there is a possibility of code runaway as the clock monitor
circuit can be misled by EXTALi clock into reporting a good
signal before it has fully stabilised
NOLHM=0
CME=X
DLY=1
Pseudo-STOP exit in Limp Home
mode with Delay
Pseudo-STOP exit
in Limp Home mode without
Delay (Fast Stop Recovery)
NOLHM=0
CME=X
DLY=0
This mode is not recommended as it is possible that the
initial VCO clock frequency may be high enough to cause
code runaway.
Pseudo-STOP exit without Limp
Home mode, clock monitor
enabled
NOLHM=1
CME=1
DLY=X
When a STOP instruction is executed the MCU resets via
the clock monitor reset vector.
Pseudo-STOP exit without Limp
Home mode, clock monitor
disabled, with Delay
NOLHM=1
CME=0
DLY=1
Oscillator starts operation following 4096 XCLK cycles
(actual controlled by SLOW mode divider).
Pseudo-STOP exit without Limp
Home mode, clock monitor
disabled, without Delay
NOLHM=1
CME=0
DLY=0
This mode is only recommended for use with an external
clock source.
18-clock
MC68HC912DT128A Rev 2.0
152
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
PLL Re g iste r De sc rip tions
SYNR — Synthesizer Register
$0038
Bit 7
6
0
0
5
SYN5
0
4
SYN4
0
3
SYN3
0
2
SYN2
0
1
SYN1
0
Bit 0
SYN0
0
0
0
RESET:
Read anytime, write anytime, except when BCSP = 1 (PLL selected as
bus clock).
If the PLL is on, the count in the loop divider (SYNR) register effectively
multiplies up the bus frequency from the PLL reference frequency by
SYNR + 1. Internally, SYSCLK runs at twice the bus frequency. Caution
should be used not to exceed the maximum rated operating frequency
for the CPU.
REFDV — Reference Divider Register
$0039
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
REFDV2
0
1
REFDV1
0
Bit 0
REFDV0
0
0
0
RESET:
Read anytime, write anytime, except when BCSP = 1.
The reference divider bits provides a finer granularity for the PLL
multiplier steps. The reference frequency is divided by REFDV + 1.
CGTFLG — Clock Generator Test Register
$003A
Bit 7
6
5
4
3
2
1
Bit 0
TSTOUT7 TSTOUT6 TSTOUT5 TSTOUT4 TSTOUT3 TSTOUT2 TSTOUT1 TSTOUT0
RESET:
0
0
0
0
0
0
0
0
Always reads zero, except in test modes.
19-clock
MC68HC912DT128A Rev 2.0
153
MOTOROLA
Clock Functions
Cloc k Func tions
PLLFLG — PLL Flags
$003B
Bit 7
6
LOCK
0
5
0
0
4
0
0
3
0
0
2
0
0
1
LHIF
0
Bit 0
LHOME
0
LOCKIF
RESET:
0
Read anytime, refer to each bit for write conditions.
LOCKIF — PLL Lock Interrupt Flag
0 = No change in LOCK bit.
1 = LOCK condition has changed, either from a locked state to an
unlocked state or vice versa.
To clear the flag, write one to this bit in PLLFLG. Cleared in limp-home
mode.
LOCK — Locked Phase Lock Loop Circuit
Regardless of the bandwidth control mode (automatic or manual):
0 = PLL VCO is not within the desired tolerance of the target
frequency.
1 = After the phase lock loop circuit is turned on, indicates the PLL
VCO is within the desired tolerance of the target frequency.
Write has no effect on LOCK bit. This bit is cleared in limp-home mode as
the lock detector cannot operate without the reference frequency.
LHIF — Limp-Home Interrupt Flag
0 = No change in LHOME bit.
1 = LHOME condition has changed, either entered or exited
limp-home mode.
To clear the flag, write one to this bit in PLLFLG.
LHOME — Limp-Home Mode Status
0 = MCU is operating normally, with EXTALi clock available for
generating clocks or as PLL reference.
1 = Loss of reference clock. CGM delivers PLL VCO limp-home
frequency to the MCU.
For Limp-Home mode, see Limp-Home and Fast STOP Recovery
modes.
20-clock
MC68HC912DT128A Rev 2.0
154
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
PLLCR — PLL Control Register
$003C
Bit 7
LOCKIE
0
6
5
AUTO
1
4
ACQ
0
3
0
0
2
PSTP
0
1
LHIE
0
Bit 0
PLLON
NOLHM
(1)
(2)
RESET:
—
—
1. Set when VDDPLL power supply is high. Forced to 0 when VDDPLL is low.
2. Cleared when VDDPLL power supply is high. Forced to 1 when VDDPLL is low.
Read and write anytime. Exceptions are listed below for each bit.
LOCKIE — PLL LOCK Interrupt Enable
0 = PLL LOCK interrupt is disabled
1 = PLL LOCK interrupt is enabled
Forced to 0 when VDDPLL=0.
PLLON — Phase Lock Loop On
0 = Turns the PLL off.
1 = Turns on the phase lock loop circuit. If AUTO is set, the PLL will
lock automatically.
Cannot be cleared when BCSP = 1 (PLL selected as bus clock). Forced
to 0 when VDDPLL is at VSS level. In limp-home mode, the output of
PLLON is forced to 1, but the PLLON bit reads the latched value.
AUTO — Automatic Bandwidth Control
0 = Automatic Mode Control is disabled and the PLL is under
software control, using ACQ bit.
1 = Automatic Mode Control is enabled. ACQ bit is read only.
Automatic bandwidth control selects either the high bandwidth
(acquisition) mode or the low bandwidth (tracking) mode depending
on how close to the desired frequency the VCO is running. See
Electrical Characteristics.
21-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
155
Cloc k Func tions
ACQ — Not in Acquisition
If AUTO = 1 (ACQ is Read Only)
0 = PLL VCO is not within the desired tolerance of the target
frequency. The loop filter is in high bandwidth, acquisition
mode.
1 = After the phase lock loop circuit is turned on, indicates the PLL
VCO is within the desired tolerance of the target frequency.
The loop filter is in low bandwidth, tracking mode.
If AUTO = 0
0 = High bandwidth PLL loop selected
1 = Low bandwidth PLL loop selected
PSTP — Pseudo-STOP Enable
0 = Pseudo-STOP oscillator mode is disabled
1 = Pseudo-STOP oscillator mode is enabled
In Pseudo-STOP mode, the oscillator is still running while the MCU is
maintained in STOP mode. This allows for a faster STOP recovery
and reduces the mechanical stress and aging of the resonator in case
frequent STOP conditions at the expense of a slightly increased
power consumption.
LHIE — Limp-Home Interrupt Enable
0 = Limp-Home interrupt is disabled
1 = Limp-Home interrupt is enabled
Forced to 0 when VDDPLL is at VSS level.
NOLHM —No Limp-Home Mode
0 = Loss of reference clock forces the MCU in limp-home mode.
1 = Loss of reference clock causes standard Clock Monitor reset.
Read anytime; Normal modes: write once; Special modes: write
anytime. Forced to 1 when VDDPLL is at VSS level.
22-clock
MC68HC912DT128A Rev 2.0
156
Clock Functions
MOTOROLA
Clock Functions
Limp-Home and Fast STOP Recovery modes
CLKSEL — Clock Generator Clock select Register
$003D
Bit 7
6
BCSP
0
5
BCSS
0
4
0
0
3
0
0
2
MCS
0
1
0
0
Bit 0
0
0
0
0
RESET:
Read and write anytime. Exceptions are listed below for each bit.
BCSP and BCSS bits determine the clock used by the main system
including the CPU and buses.
BCSP — Bus Clock Select PLL
0 = SYSCLK is derived from the crystal clock or from SLWCLK.
1 = SYSCLK source is the PLL.
Cannot be set when PLLON = 0. In limp-home mode, the output of
BCSP is forced to 1, but the BCSP bit reads the latched value.
BCSS — Bus Clock Select Slow
0 = SYSCLK is derived from the crystal clock EXTALi.
1 = SYSCLK source is the Slow clock SLWCLK.
This bit has no effect when BCSP is set.
MCS — Module Clock Select
0 = M clock is the same as PCLK.
1 = M clock is derived from Slow clock SLWCLK.
This bit determines the clock used by the ECT module and the baud
rate generators of the SCIs. In limp-home mode, the output of MCS is
forced to 0, but the MCS bit reads the latched value.
23-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
157
Cloc k Func tions
SLOW — Slow mode Divider Register
$003E
Bit 7
6
0
0
5
SLDV5
0
4
SLDV4
0
3
SLDV3
0
2
SLDV2
0
1
SLDV1
0
Bit 0
SLDV0
0
0
0
RESET:
Read and write anytime.
A write to this register changes the SLWCLK frequency with minimum
delay (less than one SLWCLK cycle), thus allowing immediate
tune-up of the performance versus power consumption for the
modules using this clock. The frequency divide ratio is
2 times (SLOW), hence the divide range is 2 to 126 (not on first pass
products). When SLOW = 0, the divider is bypassed. The generation
of E, P and M clocks further divides SLWCLK by 2. Hence, the final
ratio of Bus to EXTALi Frequency is programmable to 2, 4, 8, 12, 16,
20, ..., 252, by steps of 4. SLWCLK is a 50% duty cycle signal.
24-clock
MC68HC912DT128A Rev 2.0
158
Clock Functions
MOTOROLA
Clock Functions
System Clock Frequency Formulae
Syste m Cloc k Fre q ue nc y Form ula e
See Figure 18:
SLWCLK = EXTALi / ( 2 x SLOW )
SLWCLK = EXTALi
SLOW = 1,2,..63
SLOW = 0
PLLCLK = 2 x EXTALi x (SYNR + 1) / (REFDV + 1)
ECLK = SYSCLK / 2
XCLK = SLWCLK / 2
PCLK = SYSCLK / 2
BCLK1 = EXTALi / 2
Boolean equations:
SYSCLK = (BCSP & PLLCLK) | (BCSP & BCSS & EXTALi) | (BCSP &
BCSS & SLWCLK)
MCLK = (PCLK & MCS) | (XCLK & MCS)
MSCAN system = (EXTALi & CLKSRC) | (SYSCLK & CLKSRC)
BDM system = (BCLK & CLKSW) | (ECLK & CLKSW)
NOTE: During limp-home mode PCLK, ECLK, BCLK, MCLK and XCLK are
supplied by VCO (PLLCLK).
1. If SYSCLK is slower than EXTALi (BCSS=1, BCSP=0, SLOW>0), BCLK becomes ECLK.
MC68HC912DT128A Rev 2.0
25-clock
MOTOROLA
Clock Functions
159
Cloc k Func tions
Cloc k Divid e r Cha ins
Figure 18, Figure 19, Figure 20, and Figure 21 summarize the clock
divider chains for the various peripherals on the 68HC912D60A.
BCSP BCSS
1:x
TCLKs
T CLOCK
GENERATOR
SYSCLK
PHASE
LOCK
LOOP
PLLCLK
TO CPU
÷2
ECLK
PCLK
E AND P
CLOCK
GENERATOR
TO
BUSES,
SPI,
EXTALi
EXTAL
XTAL
BCSP BCSS
0:0
PWM,
ATD0, ATD1
REDUCED
CONSUMPTION
OSCILLATOR
EXTALi
CLKSRC = 0
CLKSRC = 1
BCSP BCSS
0:1
EXTALi
TO
MSCAN
MCS = 0
TO
SCI0, SCI1,
ECT
MCLK
MCS = 1
SLOW MODE
CLOCK
DIVIDER
SLWCLK
÷ 2
SYNC
XCLK
TO
RTI, COP
TO CAL
CLKSW = 0
CLKSW = 1
÷ 2
SYNC
TO BDM
TO CLOCK
MONITOR
Figure 18 Clock Generation Chain
26-clock
MC68HC912DT128A Rev 2.0
160
Clock Functions
MOTOROLA
Clock Functions
Clock Divider Chains
Bus clock select bits BCSP and BCSS in the clock select register
(CLKSEL) determine which clock drives SYSCLK for the main system
including the CPU and buses. BCSS has no effect if BCSP is set. During
the transition, the clock select output will be held low and all CPU activity
will cease until the transition is complete.
The Module Clock Select bit MCS determines the clock used by the ECT
module and the baud rate generators of the SCIs. In limp-home mode,
the output of MCS is forced to 0, but the MCS bit reads the latched value.
It allows normal operation of the serial and timer subsystems at a fixed
reference frequency while allowing the CPU to operate at a higher,
variable frequency.
XCLK
÷ 2048
÷4
0:0:0
0:0:0
REGISTER: COPCTL
BITS: CR2, CR1, CR0
REGISTER: RTICTL
BITS: RTR2, RTR1, RTR0
REGISTER: RTICTL
BIT:RTBYP
0:0:1
0:1:0
0:0:1
0:1:0
÷ 2
÷ 4
÷ 4
÷ 4
÷ 4
÷ 2
÷ 2
SC0BD
MODULUS DIVIDER:
÷ 1, 2, 3, 4, 5, 6,...,8190, 8191
SCI0
÷ 2
0:1:1
1:0:0
1:0:1
1:1:0
1:1:1
0:1:1
1:0:0
1:0:1
1:1:0
1:1:1
MCLK
RECEIVE
BAUD RATE (16x)
÷ 2
÷ 2
÷ 2
÷ 2
÷ 16
SCI0
TRANSMIT
BAUD RATE (1x)
SC1BD
MODULUS DIVIDER:
÷ 1, 2, 3, 4, 5, 6,...,8190, 8191
SCI1
RECEIVE
BAUD RATE (16x)
÷ 16
SCI1
TRANSMIT
BAUD RATE (1x)
TO RTI
TO COP
Figure 19 Clock Chain for SCI0, SCI1, RTI, COP
27-clock
MC68HC912DT128A Rev 2.0
161
MOTOROLA
Clock Functions
Cloc k Func tions
MCLK
TEN
REGISTER: TMSK2
BITS: PR2, PR1, PR0
0:0:0
REGISTER: MCCTL
BITS: MCPR1, MCPR0
0:0
MCEN
MODULUS
DOWN
COUNTER
0:0:1
0:1:0
0:1:1
0:1
1:0
1:1
÷ 2
÷ 2
÷ 2
÷ 2
÷ 2
÷ 2
÷ 2
÷ 4
÷ 2
÷ 2
REGISTER: PACTL
BITS: PAEN, CLK1, CLK0
0:x:x
1:0:0
1:0:1
1:1:0
Prescaled MCLK
1:0:0
1:0:1
1:1:0
1:1:1
PULSE ACC
LOW BYTE
PACLK/256
1:1:1
PACLK/65536
(PAOV)
TO TIMER
MAIN
COUNTER
(TCNT)
PULSE ACC
HIGH BYTE
PACLK
GATE
LOGIC
PAMOD
PORT T7
PAEN
Figure 20 Clock Chain for ECT
28-clock
MC68HC912DT128A Rev 2.0
162
Clock Functions
MOTOROLA
Clock Functions
Computer Operating Properly (COP)
PCLK
5-BIT MODULUS
COUNTER (PR0-PR4)
TO ATD0
and ATD1
÷ 2
÷ 2
REGISTER: SP0BR
BITS: SPR2, SPR1, SPR0
0:0:0
SPI
BIT RATE
÷ 2
÷ 2
÷ 2
0:0:1
0:1:0
MSCAN
CLOCK
EXTALi
CLKSRC
SYSCLK
ECLK
0:1:1
1:0:0
1:0:1
1:1:0
1:1:1
÷ 2
÷ 2
÷ 2
÷ 2
CLKSW
BDM BIT CLOCK:
BCLK
Receive: Detect falling edge,
count 12 E clocks, Sample input
BKGD IN
SYNCHRONIZER
Transmit 1: Detect falling edge,
count 6 E clocks while output is
high impedance, Drive out 1 E
cycle pulse high, high imped-
ance output again
BKGD DIRECTION
BKGD OUT
BKGD
PIN
LOGIC
Transmit 0: Detect falling edge,
Drive out low, count 9 E clocks,
Drive out 1 E cycle pulse high,
high impedance output
Figure 21 Clock Chain for MSCAN, SPI, ATD0, ATD1 and BDM
Com p ute r Op e ra ting Prop e rly (COP)
The COP or watchdog timer is an added check that a program is running
and sequencing properly. When the COP is being used, software is
responsible for keeping a free running watchdog timer from timing out. If
the watchdog timer times out it is an indication that the software is no
longer being executed in the intended sequence; thus a system reset is
initiated. Three control bits allow selection of seven COP time-out
periods. When COP is enabled, sometime during the selected period the
program must write $55 and $AA (in this order) to the COPRST register.
If the program fails to do this the part will reset. If any value other than
$55 or $AA is written, the part is reset.
29-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
163
Cloc k Func tions
In addition, windowed COP operation can be selected. In this mode,
writes to the COPRST register must occur in the last 25% of the selected
period. A premature write will also reset the part.
Re a l-Tim e Inte rrup t
There is a real time (periodic) interrupt available to the user. This
interrupt will occur at one of seven selected rates. An interrupt flag and
an interrupt enable bit are associated with this function. There are three
bits for the rate select.
Cloc k Monitor
The clock monitor circuit is based on an internal resistor-capacitor (RC)
time delay. If no EXTALi clock edges are detected within this RC time
delay, the clock monitor can optionally generate a system reset. The
clock monitor function is enabled/disabled by the CME control bit in the
COPCTL register. This time-out is based on an RC delay so that the
clock monitor can operate without any EXTALi clock.
Clock monitor time-outs are shown in Table 25. The corresponding
EXTALi clock period with an ideal 50% duty cycle is twice this time-out
value.
Table 25 Clock Monitor Time-Outs
Supply
Range
5 V +/– 10%
2–20 µS
30-clock
MC68HC912DT128A Rev 2.0
164
Clock Functions
MOTOROLA
Clock Functions
Clock Function Registers
Cloc k Func tion Re g iste rs
All register addresses shown reflect the reset state. Registers may be
mapped to any 2K byte space.
RTICTL — Real-Time Interrupt Control Register
$0014
Bit 7
RTIE
0
6
RSWAI
0
5
RSBCK
0
4
Reserved
0
3
RTBYP
0
2
RTR2
0
1
RTR1
0
Bit 0
RTR0
0
RESET:
RTIE — Real Time Interrupt Enable
Read and write anytime.
0 = Interrupt requests from RTI are disabled.
1 = Interrupt will be requested whenever RTIF is set.
RSWAI — RTI and COP Stop While in Wait
Write once in normal modes, anytime in special modes. Read
anytime.
0 = Allows the RTI and COP to continue running in wait.
1 = Disables both the RTI and COP whenever the part goes into
Wait.
RSBCK — RTI and COP Stop While in Background Debug Mode
Write once in normal modes, anytime in special modes. Read
anytime.
0 = Allows the RTI and COP to continue running while in
background mode.
1 = Disables both the RTI and COP when the part is in background
mode. This is useful for emulation.
RTBYP — Real Time Interrupt Divider Chain Bypass
Write not allowed in normal modes, anytime in special modes. Read
anytime.
0 = Divider chain functions normally.
1 = Divider chain is bypassed, allows faster testing (the divider
chain is normally XCLK divided by 213, when bypassed
becomes XCLK divided by 4).
31-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
165
Cloc k Func tions
RTR2, RTR1, RTR0 — Real-Time Interrupt Rate Select
Read and write anytime.
Rate select for real-time interrupt. The clock used for this module is
the XCLK.
Table 26 Real Time Interrupt Rates
Time-Out Period Time-Out Period Time-Out Period Time-Out Period
RTR2 RTR1 RTR0 Divide X By:
X = 125 KHz
X = 500 KHz
X = 2.0 MHz
X = 8.0 MHz
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
OFF
213
214
215
216
217
218
219
OFF
OFF
OFF
OFF
65.536 ms
131.72 ms
263.44 ms
526.88 ms
1.05 s
16.384 ms
32.768 ms
65.536 ms
131.72 ms
263.44 ms
526.88 ms
1.05 s
4.096 ms
8.196 ms
16.384 ms
32.768 ms
65.536 ms
131.72 ms
263.44 ms
1.024 ms
2.048 ms
4.096 ms
8.196 ms
16.384 ms
32.768 ms
65.536 ms
2.11 s
4.22 s
RTIFLG — Real Time Interrupt Flag Register
$0015
Bit 7
RTIF
0
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
0
0
RESET:
RTIF — Real Time Interrupt Flag
This bit is cleared automatically by a write to this register with this bit
set.
0 = Time-out has not yet occurred.
1 = Set when the time-out period is met.
32-clock
MC68HC912DT128A Rev 2.0
166
Clock Functions
MOTOROLA
Clock Functions
Clock Function Registers
COPCTL — COP Control Register
$0016
Bit 7
CME
0/1
6
5
4
3
DISR
0
2
CR2
1
1
CR1
1
Bit 0
CR0
FCME
FCMCOP
WCOP
RESET:
RESET:
0
0
0
0
0
0
1
1
Normal
Special
0/1
1
1
1
CME — Clock Monitor Enable
Read and write anytime.
If FCME is set, this bit has no meaning nor effect.
0 = Clock monitor is disabled. Slow clocks and stop instruction may
be used.
1 = Slow or stopped clocks (including the stop instruction) will
cause a clock reset sequence or limp-home mode. See
Limp-Home and Fast STOP Recovery modes.
On reset
CME is 1 if VDDPLL is high
CME is 0 if VDDPLL is low.
NOTE: The VDDPLL-dependent reset operation is not implemented on first
pass products.
In this case the state of CME on reset is 0.
FCME — Force Clock Monitor Enable
Write once in normal modes, anytime in special modes. Read
anytime.
In normal modes, when this bit is set, the clock monitor function
cannot be disabled until a reset occurs.
0 = Clock monitor follows the state of the CME bit.
1 = Slow or stopped clocks will cause a clock reset sequence or
limp-home mode.
See Limp-Home and Fast STOP Recovery modes.
33-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
167
Cloc k Func tions
FCMCOP — Force Clock Monitor Reset or COP Watchdog Reset
Writes are not allowed in normal modes, anytime in special modes.
Read anytime.
If DISR is set, this bit has no effect.
0 = Normal operation.
1 = A clock monitor failure reset or a COP failure reset is forced
depending on the state of CME and if COP is enabled.
CME
COP enabled
Forced reset
none
0
0
1
1
0
1
0
1
COP failure
Clock monitor failure
Both(1)
1. Highest priority interrupt vector is serviced.
WCOP — Window COP mode
Write once in normal modes, anytime in special modes. Read
anytime.
0 = Normal COP operation
1 = Window COP operation
When set, a write to the COPRST register must occur in the last 25%
of the selected period. A premature write will also reset the part. As
long as all writes occur during this window, $55 can be written as often
as desired. Once $AA is written the time-out logic restarts and the
user must wait until the next window before writing to COPRST.
Please note, there is a fixed time uncertainty about the exact COP
counter state when reset, as the initial prescale clock divider in the
RTI section is not cleared when the COP counter is cleared. This
means the effective window is reduced by this uncertainty. Table 27
below shows the exact duration of this window for the seven available
COP rates.
34-clock
MC68HC912DT128A Rev 2.0
168
Clock Functions
MOTOROLA
Clock Functions
Clock Function Registers
Table 27 COP Watchdog Rates
Window COP enabled:
Divide
XCLK
by
8.0 MHz XCLK
CR2 CR1 CR0
Window start
Effective
Window (2)
Time-out
Window end
(1)
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
OFF
2 13
2 15
2 17
2 19
2 21
2 22
2 23
OFF
OFF
OFF
OFF
1.024 ms -0/+0.256 ms
4.096 ms -0/+0.256 ms
16.384 ms -0/+0.256 ms
65.536 ms -0/+1.024 ms
262.144 ms -0/+1.024 ms
524.288 ms -0/+1.024 ms
1.048576 ms -0/+1.024 ms
0.768 ms
0.768 ms
0 % (3)
18.8 %
23.4 %
23.4 %
24.6 %
24.8 %
24.9 %
3.072 ms
3.840 ms
12.288 ms
49.152 ms
196.608 ms
393.216 ms
786.432 ms
16.128 ms
64.512 ms
261.120 ms
523.264 ms
1.047552 ms
1. Time for writing $55 following previous COP restart of time-out logic due to writing $AA.
2. Please refer to WCOP bit description above.
3. Window COP cannot be used at this rate.
DISR — Disable Resets from COP Watchdog and Clock Monitor
Writes are not allowed in normal modes, anytime in special modes.
Read anytime.
0 = Normal operation.
1 = Regardless of other control bit states, COP and clock monitor
will not generate a system reset.
CR2, CR1, CR0 — COP Watchdog Timer Rate select bits
These bits select the COP time-out rate. The clock used for this
module is the XCLK.
Write once in normal modes, anytime in special modes. Read
anytime.
35-clock
MC68HC912DT128A Rev 2.0
MOTOROLA
Clock Functions
169
Cloc k Func tions
COPRST — Arm/Reset COP Timer Register
$0017
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
Always reads $00.
Writing $55 to this address is the first step of the COP watchdog
sequence.
Writing $AA to this address is the second step of the COP watchdog
sequence. Other instructions may be executed between these writes
but both must be completed in the correct order prior to time-out to
avoid a watchdog reset. Writing anything other than $55 or $AA
causes a COP reset to occur.
36-clock
MC68HC912DT128A Rev 2.0
170
Clock Functions
MOTOROLA
Pulse -Wid th Mod ula tor
Pulse -Wid th Mod ula tor
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
PWM Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
PWM Boundary Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Introd uc tion
The pulse-width modulator (PWM) subsystem provides four
independent 8-bit PWM waveforms or two 16-bit PWM waveforms or a
combination of one 16-bit and two 8-bit PWM waveforms. Each
waveform channel has a programmable period and a programmable
duty-cycle as well as a dedicated counter. A flexible clock select scheme
allows four different clock sources to be used with the counters. Each of
the modulators can create independent, continuous waveforms with
software-selectable duty rates from 0 percent to 100 percent. The PWM
outputs can be programmed as left-aligned outputs or center-aligned
outputs.
The period and duty registers are double buffered so that if they change
while the channel is enabled, the change will not take effect until the
counter rolls over or the channel is disabled. If the channel is not
enabled, then writes to the period and/or duty register will go directly to
the latches as well as the buffer, thus ensuring that the PWM output will
always be either the old waveform or the new waveform, not some
variation in between.
A change in duty or period can be forced into immediate effect by writing
the new value to the duty and/or period registers and then writing to the
counter. This causes the counter to reset and the new duty and/or period
values to be latched. In addition, since the counter is readable it is
1-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
171
Pulse -Wid th Mod ula tor
possible to know where the count is with respect to the duty value and
software can be used to make adjustments by turning the enable bit off
and on.
The four PWM channel outputs share general-purpose port P pins.
Enabling PWM pins takes precedence over the general-purpose port.
When PWM are not in use, the port pins may be used for discrete input/
output.
CLOCK SOURCE
(ECLK or Scaled ECLK)
CENTR = 0
FROM PORT P
DATA REGISTER
UP/DOWN
GATE
PWCNTx
(CLOCK EDGE SYNC)
RESET
8-BIT COMPARE =
S
PWDTYx
Q
Q
MUX
MUX
TO PIN
DRIVER
R
8-BIT COMPARE =
PWPERx
PPOLx
PWENx
SYNC
PPOL = 0
PPOL = 1
PWDTY
PWPER
Figure 22 Block Diagram of PWM Left-Aligned Output Channel
2--pwm
MC68HC912DT128A Rev 2.0
172
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
Introduction
CLOCK SOURCE
(ECLK or Scaled ECLK)
CENTR = 1
RESET
FROM PORT P
DATA REGISTER
PWCNTx
GATE
(CLOCK EDGE SYNC)
(DUTY CYCLE)
8-BIT COMPARE =
T
PWDTYx
Q
Q
MUX
MUX
(PERIOD)
8-BIT COMPARE =
PWPERx
TO PIN
DRIVER
PPOLx
PWENx
SYNC
PPOL = 1
PPOL = 0
(PWPER − PWDTY) × 2
PWDTY
PWDTY
PWPER × 2
Figure 23 Block Diagram of PWM Center-Aligned Output Channel
3-pwm
MC68HC912DT128A Rev 2.0
173
MOTOROLA
Pulse-Width Modulator
Pulse -Wid th Mod ula tor
PSBCK
PSBCK IS BIT 0 OF PWCTL REGISTER.
INTERNAL SIGNAL LIMBDM IS ONE IF THE MCU IS IN BACKGROUND DEBUG MODE.
LIMBDM
CLOCK A
CLOCK TO PWM
CHANNEL 0
ECLK
0:0:0
0:0:0
= 0
8-BIT DOWN COUNTER
÷ 2
÷ 2
÷ 2
÷ 2
÷ 2
÷ 2
÷ 2
0:0:1
0:1:0
0:0:1
0:1:0
0:1:1
1:0:0
1:0:1
1:1:0
1:1:1
PWSCNT0
PCLK0
CLOCK TO PWM
CHANNEL 1
8-BIT SCALE REGISTER
PWSCAL0
0:1:1
1:0:0
1:0:1
1:1:0
1:1:1
÷ 2
PCLK1
PCLK2
CLOCK B
CLOCK TO PWM
CHANNEL 2
= 0
8-BIT DOWN COUNTER
PWSCNT1
CLOCK TO PWM
CHANNEL 3
BITS:
BITS:
REGISTER:
PWPRES
8-BIT SCALE REGISTER
PWSCAL1
PCKA2,
PCKA1,
PCKA0
PCKB2,
PCKB1,
PCKB0
÷ 2
PCLK3
*CLOCK S0 = (CLOCK A)/2, (CLOCK A)/4, (CLOCK A)/6,... (CLOCK A)/512
**CLOCK S1 = (CLOCK B)/2, (CLOCK B)/4, (CLOCK B)/6,... (CLOCK B)/512
Figure 24 PWM Clock Sources
4-pwm
MC68HC912DT128A Rev 2.0
174
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
PWM Register Descriptions
PWM Re g iste r De sc rip tions
PWCLK — PWM Clocks and Concatenate
$0040
Bit 7
CON23
0
6
CON01
0
5
PCKA2
0
4
PCKA1
0
3
PCKA0
0
2
PCKB2
0
1
Bit 0
PCKB1
0
PCKB0
0
RESET:
Read and write anytime.
CON23 — Concatenate PWM Channels 2 and 3
When concatenated, channel 2 becomes the high-order byte and
channel 3 becomes the low-order byte. Channel 2 output pin is used
as the output for this 16-bit PWM (bit 2 of port P). Channel 3
clock-select control bits determines the clock source. Channel 3
output pin becomes a general purpose I/O.
0 = Channels 2 and 3 are separate 8-bit PWMs.
1 = Channels 2 and 3 are concatenated to create one 16-bit PWM
channel.
CON01 — Concatenate PWM Channels 0 and 1
When concatenated, channel 0 becomes the high-order byte and
channel 1 becomes the low-order byte. Channel 0 output pin is used
as the output for this 16-bit PWM (bit 0 of port P). Channel 1
clock-select control bits determine the clock source. Channel 1 output
pin becomes a general purpose I/O.
0 = Channels 0 and 1 are separate 8-bit PWMs.
1 = Channels 0 and 1 are concatenated to create one 16-bit PWM
channel.
PCKA2 – PCKA0 — Prescaler for Clock A
Clock A is one of two clock sources which may be used for channels
0 and 1. These three bits determine the rate of clock A, as shown in
Table 28.
PCKB2 – PCKB0 — Prescaler for Clock B
Clock B is one of two clock sources which may be used for channels
2 and 3. These three bits determine the rate of clock B, as shown in
Table 28.
5-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
175
Pulse -Wid th Mod ula tor
Table 28 Clock A and Clock B Prescaler
PCKA2
PCKA1
PCKA0
Value of
Clock A (B)
(PCKB2) (PCKB1) (PCKB0)
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
P
P ÷ 2
P ÷ 4
P ÷ 8
P ÷ 16
P ÷ 32
P ÷ 64
P ÷ 128
PWPOL — PWM Clock Select and Polarity
$0041
Bit 7
PCLK3
0
6
PCLK2
0
5
PCLK1
0
4
3
2
PPOL2
0
1
PPOL1
0
Bit 0
PCLK0
0
PPOL3
0
PPOL0
0
RESET:
Read and write anytime.
PCLK3 — PWM Channel 3 Clock Select
0 = Clock B is the clock source for channel 3.
1 = Clock S1 is the clock source for channel 3.
PCLK2 — PWM Channel 2 Clock Select
0 = Clock B is the clock source for channel 2.
1 = Clock S1 is the clock source for channel 2.
PCLK1 — PWM Channel 1 Clock Select
0 = Clock A is the clock source for channel 1.
1 = Clock S0 is the clock source for channel 1.
PCLK0 — PWM Channel 0 Clock Select
0 = Clock A is the clock source for channel 0.
1 = Clock S0 is the clock source for channel 0.
If a clock select is changed while a PWM signal is being generated, a
truncated or stretched pulse may occur during the transition.
6-pwm
MC68HC912DT128A Rev 2.0
176
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
PWM Register Descriptions
The following four bits apply in left-aligned mode only:
PPOL3 — PWM Channel 3 Polarity
0 = Channel 3 output is low at the beginning of the period; high
when the duty count is reached.
1 = Channel 3 output is high at the beginning of the period; low
when the duty count is reached.
PPOL2 — PWM Channel 2 Polarity
0 = Channel 2 output is low at the beginning of the period; high
when the duty count is reached.
1 = Channel 2 output is high at the beginning of the period; low
when the duty count is reached.
PPOL1 — PWM Channel 1 Polarity
0 = Channel 1 output is low at the beginning of the period; high
when the duty count is reached.
1 = Channel 1 output is high at the beginning of the period; low
when the duty count is reached.
PPOL0 — PWM Channel 0 Polarity
0 = Channel 0 output is low at the beginning of the period; high
when the duty count is reached.
1 = Channel 0 output is high at the beginning of the period; low
when the duty count is reached.
Depending on the polarity bit, the duty registers may contain the count
of either the high time or the low time. If the polarity bit is zero and left
alignment is selected, the duty registers contain a count of the low
time. If the polarity bit is one, the duty registers contain a count of the
high time.
7-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
177
Pulse -Wid th Mod ula tor
PWEN — PWM Enable
$0042
Bit 7
6
0
0
5
0
0
4
0
0
3
PWEN3
0
2
PWEN2
0
1
PWEN1
0
Bit 0
PWEN0
0
0
0
RESET:
Setting any of the PWENx bits causes the associated port P line to
become an output regardless of the state of the associated data
direction register (DDRP) bit. This does not change the state of the data
direction bit. When PWENx returns to zero, the data direction bit controls
I/O direction. On the front end of the PWM channel, the scaler clock is
enabled to the PWM circuit by the PWENx enable bit being high. When
all four PWM channels are disabled, the prescaler counter shuts off to
save power. There is an edge-synchronizing gate circuit to guarantee
that the clock will only be enabled or disabled at an edge.
Read and write anytime.
PWEN3 — PWM Channel 3 Enable
The pulse modulated signal will be available at port P, bit 3 when its
clock source begins its next cycle.
0 = Channel 3 is disabled.
1 = Channel 3 is enabled.
PWEN2 — PWM Channel 2 Enable
The pulse modulated signal will be available at port P, bit 2 when its
clock source begins its next cycle.
0 = Channel 2 is disabled.
1 = Channel 2 is enabled.
PWEN1 — PWM Channel 1 Enable
The pulse modulated signal will be available at port P, bit 1 when its
clock source begins its next cycle.
0 = Channel 1 is disabled.
1 = Channel 1 is enabled.
PWEN0 — PWM Channel 0 Enable
The pulse modulated signal will be available at port P, bit 0 when its
clock source begins its next cycle.
0 = Channel 0 is disabled.
1 = Channel 0 is enabled.
8-pwm
MC68HC912DT128A Rev 2.0
178
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
PWM Register Descriptions
PWPRES — PWM Prescale Counter
$0043
Bit 7
6
Bit 6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
0
0
RESET:
PWPRES is a free-running 7-bit counter. Read anytime. Write only in
special mode (SMOD = 1).
PWSCAL0 — PWM Scale Register 0
$0044
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
Read and write anytime. A write will cause the scaler counter PWSCNT0
to load the PWSCAL0 value unless in special mode with DISCAL = 1 in
the PWTST register.
PWM channels 0 and 1 can select clock S0 (scaled) as its input clock by
setting the control bit PCLK0 and PCLK1 respectively. Clock S0 is
generated by dividing clock A by the value in the PWSCAL0 register + 1
and dividing again by two. When PWSCAL0 = $FF, clock A is divided by
256 then divided by two to generate clock S0.
PWSCNT0 — PWM Scale Counter 0 Value
$0045
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
PWSCNT0 is a down-counter that, upon reaching $00, loads the value
of PWSCAL0. Read any time.
9-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
179
Pulse -Wid th Mod ula tor
PWSCAL1 — PWM Scale Register 1
$0046
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
Read and write anytime. A write will cause the scaler counter PWSCNT1
to load the PWSCAL1 value unless in special mode with DISCAL = 1 in
the PWTST register.
PWM channels 2 and 3 can select clock S1 (scaled) as its input clock by
setting the control bit PCLK2 and PCLK3 respectively. Clock S1 is
generated by dividing clock B by the value in the PWSCAL1 register + 1
and dividing again by two. When PWSCAL1 = $FF, clock B is divided by
256 then divided by two to generate clock S1.
PWSCNT1 — PWM Scale Counter 1 Value
$0047
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
PWSCNT1 is a down-counter that, upon reaching $00, loads the value
of PWSCAL1. Read any time.
PWCNTx — PWM Channel Counters
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
0
6
6
6
6
6
0
5
5
5
5
5
0
4
4
4
4
4
0
3
3
3
3
3
0
2
2
2
2
2
0
1
1
1
1
1
0
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
0
PWCNT0
PWCNT1
PWCNT2
PWCNT3
RESET:
$0048
$0049
$004A
$004B
Read and write anytime. A write will cause the PWM counter to reset to
$00.
In special mode, if DISCR = 1, a write does not reset the PWM counter.
10-pwm
MC68HC912DT128A Rev 2.0
180
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
PWM Register Descriptions
The PWM counters are not reset when PWM channels are disabled. The
counters must be reset prior to a new enable.
Each counter may be read any time without affecting the count or the
operation of the corresponding PWM channel. Writes to a counter cause
the counter to be reset to $00 and force an immediate load of both duty
and period registers with new values. To avoid a truncated PWM period,
write to a counter while the counter is disabled. In left-aligned output
mode, resetting the counter and starting the waveform output is
controlled by a match between the period register and the value in the
counter. In center-aligned output mode the counters operate as up/down
counters, where a match in period changes the counter direction. The
duty register changes the state of the output during the period to
determine the duty.
When a channel is enabled, the associated PWM counter starts at the
count in the PWCNTx register using the clock selected for that channel.
In special mode, when DISCP = 1 and configured for left-aligned output,
a match of period does not reset the associated PWM counter.
PWPERx — PWM Channel Period Registers
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
1
6
6
6
6
6
1
5
5
5
5
5
1
4
4
4
4
4
1
3
3
3
3
3
1
2
2
2
2
2
1
1
1
1
1
1
1
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
1
PWPER0
PWPER1
PWPER2
PWPER3
RESET:
$004C
$004D
$004E
$004F
Read and write anytime.
The value in the period register determines the period of the associated
PWM channel. If written while the channel is enabled, the new value will
not take effect until the existing period terminates, forcing the counter to
reset. The new period is then latched and is used until a new period
value is written. Reading this register returns the most recent value
written. To start a new period immediately, write the new period value
11-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
181
Pulse -Wid th Mod ula tor
and then write the counter forcing a new period to start with the new
period value.
Period = Channel-Clock-Period × (PWPER + 1)
Period = Channel-Clock-Period × (2 × PWPER)
(CENTR = 0)
(CENTR = 1)
PWDTYx — PWM Channel Duty Registers
Bit 7
Bit 7
Bit 7
Bit 7
Bit 7
1
6
6
6
6
6
1
5
5
5
5
5
1
4
4
4
4
4
1
3
3
3
3
3
1
2
2
2
2
2
1
1
1
1
1
1
1
Bit 0
Bit 0
Bit 0
Bit 0
Bit 0
1
PWDTY0
PWDTY1
PWDTY2
PWDTY3
RESET:
$0050
$0051
$0052
$0053
Read and write anytime.
The value in each duty register determines the duty of the associated
PWM channel. When the duty value is equal to the counter value, the
output changes state. If the register is written while the channel is
enabled, the new value is held in a buffer until the counter rolls over
or the channel is disabled. Reading this register returns the most
recent value written.
If the duty register is greater than or equal to the value in the period
register, there will be no duty change in state. If the duty register is set
to $FF the output will always be in the state which would normally be
the state opposite the PPOLx value.
Left-Aligned-Output Mode (CENTR = 0):
Duty cycle = [(PWDTYx+1)/(PWPERx+1)] × 100%
(PPOLx = 1)
Duty cycle = [(PWPERx−PWDTYx)/(PWPERx+1)] × 100% (PPOLx = 0)
Center-Aligned-Output Mode (CENTR = 1):
Duty cycle = [(PWPERx−PWDTYx)/PWPERx] × 100%
Duty cycle = [PWDTYx/PWPERx] × 100%
(PPOLx = 0)
(PPOLx = 1)
12-pwm
MC68HC912DT128A Rev 2.0
182
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
PWM Register Descriptions
PWCTL — PWM Control Register
$0054
Bit 7
6
0
0
5
0
0
4
PSWAI
0
3
CENTR
0
2
RDPP
0
1
Bit 0
0
0
PUPP
0
PSBCK
0
RESET:
Read and write anytime.
PSWAI — PWM Halts while in Wait Mode
0 = Allows PWM main clock generator to continue while in wait
mode.
1 = Halt PWM main clock generator when the part is in wait mode.
CENTR — Center-Aligned Output Mode
To avoid irregularities in the PWM output mode, write the CENTR bit
only when PWM channels are disabled.
0 = PWM channels operate in left-aligned output mode
1 = PWM channels operate in center-aligned output mode
RDPP — Reduced Drive of Port P
0 = All port P output pins have normal drive capability.
1 = All port P output pins have reduced drive capability.
PUPP — Pull-Up Port P Enable
0 = All port P pins have an active pull-up device disabled.
1 = All port P pins have an active pull-up device enabled.
PSBCK — PWM Stops while in Background Mode
0 = Allows PWM to continue while in background mode.
1 = Disable PWM input clock when the part is in background mode.
13-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
183
Pulse -Wid th Mod ula tor
PWTST — PWM Special Mode Register (“Test”)
$0055
Bit 7
DISCR
0
6
DISCP
0
5
DISCAL
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
0
0
RESET:
Read anytime but write only in special mode (SMODN = 0). These bits
are available only in special mode and are reset in normal mode.
DISCR — Disable Reset of Channel Counter on Write to Channel
Counter
0 = Normal operation. Write to PWM channel counter will reset
channel counter.
1 = Write to PWM channel counter does not reset channel counter.
DISCP — Disable Compare Count Period
0 = Normal operation
1 = In left-aligned output mode, match of period does not reset the
associated PWM counter register.
DISCAL — Disable Load of Scale-Counters on Write to the Associated
Scale-Registers
0 = Normal operation
1 = Write to PWSCAL0 and PWSCAL1 does not load scale
counters
14-pwm
MC68HC912DT128A Rev 2.0
184
Pulse-Width Modulator
MOTOROLA
Pulse-Width Modulator
PWM Register Descriptions
PORTP — Port P Data Register
$0056
Bit 7
PP7
–
6
PP6
–
5
PP5
–
4
PP4
–
3
PP3
PWM3
–
2
PP2
PWM2
–
1
Bit 0
PP1
PWM1
–
PP0
PWM0
–
PWM
RESET:
–
–
–
–
PORTP can be read anytime.
PWM functions share port P pins 3 to 0 and take precedence over the
general-purpose port when enabled.
When configured as input, a read will return the pin level. For port bits 7
to 4 it will read zero because there are no available external pins.
When configured as output, a read will return the latched output data.
For port bits 7 to 4 it will read the last value written. A write will drive
associated pins only if configured for output and the corresponding PWM
channel is not enabled.
After reset, all pins are general-purpose, high-impedance inputs.
DDRP — Port P Data Direction Register
$0057
Bit 7
DDP7
0
6
DDP6
0
5
DDP5
0
4
DDP4
0
3
DDP3
0
2
DDP2
0
1
DDP1
0
Bit 0
DDP0
0
RESET:
DDRP determines pin direction of port P when used for general-purpose
I/O.
DDRP[7:4] — This bits served as memory locations since there are no
corresponding port pins.
DDRP[3:0] — Data Direction Port P pin 0-3
0 = I/O pin configured as high impedance input
1 = I/O pin configured for output.
15-pwm
MC68HC912DT128A Rev 2.0
MOTOROLA
Pulse-Width Modulator
185
Pulse -Wid th Mod ula tor
PWM Bound a ry Ca se s
The boundary conditions for the PWM channel duty registers and the
PWM channel period registers cause these results:
Table 29 PWM Left-Aligned Boundary Conditions
PWDTYx
PWPERx
>$00
>$00
–
PPOLx
Output
Low
$FF
1
0
1
0
1
0
$FF
High
High
Low
≥PWPERx
≥PWPERx
–
–
–
$00
High
Low
$00
Table 30 PWM Center-Aligned Boundary Conditions
PWDTYx
PWPERx
>$00
>$00
–
PPOLx
Output
Low
$00
1
0
1
0
1
0
$00
High
High
Low
≥PWPERx
≥PWPERx
–
–
–
$00
High
Low
$00
16-pwm
MC68HC912DT128A Rev 2.0
186
Pulse-Width Modulator
MOTOROLA
Enha nc e d Ca p ture Tim e r
Enha nc e d Ca p ture Tim e r
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Enhanced Capture Timer Modes of Operation . . . . . . . . . . . . . . . . . 194
Timer Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Timer and Modulus Counter Operation in Different Modes. . . . . . . . 221
Introd uc tion
The HC12 Enhanced Capture Timer module has the features of the
HC12 Standard Timer module enhanced by additional features in order
to enlarge the field of applications, in particular for automotive ABS
applications.
The additional features permit the operation of this timer module in a
mode similar to the Input Control Timer implemented on
MC68HC11NB4.
These additional features are:
•
•
16-Bit Buffer Register for four Input Capture (IC) channels.
Four 8-Bit Pulse Accumulators with 8-bit buffer registers
associated with the four buffered IC channels. Configurable also
as two 16-Bit Pulse Accumulators.
•
•
16-Bit Modulus Down-Counter with 4-bit Prescaler.
Four user selectable Delay Counters for input noise immunity
increase.
•
Main Timer Prescaler extended to 7-bit.
1-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
187
Enha nc e d Ca p ture Tim e r
This design specification describes the standard timer as well as the
additional features.
The basic timer consists of a 16-bit, software-programmable counter
driven by a 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.
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.
2--ect
MC68HC912DT128A Rev 2.0
188
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Introduction
÷ 1, 2, ..., 128
16-bit Free-running
16-bit load register
Prescaler
M clock
PT0
main timer
÷ 1, 4, 8, 16
16-bit modulus
down counter
M clock
Prescaler
RESET
0
Comparator
Pin logic
Pin logic
Pin logic
Pin logic
Pin logic
TC0 capture/compare register
Delay counter
Delay counter
Delay counter
Delay counter
PAC0
EDG0
EDG1
EDG2
EDG3
TC0H hold register
PA0H hold register
RESET
0
Comparator
PT1
PT2
PT3
TC1 capture/compare register
PAC1
TC1H hold register
PA1H hold register
RESET
0
Comparator
TC2 capture/compare register
PAC2
TC2H hold register
PA2H hold register
RESET
0
Comparator
TC3 capture/compare register
PAC3
TC3H hold register
PA3H hold register
Comparator
PT4
PT5
EDG4
EDG0
TC4 capture/compare register
MUX
MUX
ICLAT, LATQ, BUFEN
(force latch)
Comparator
Pin logic
Pin logic
Pin logic
EDG5
EDG1
TC5 capture/compare register
Write $0000
to modulus counter
LATQ
(MDC latch enable)
Comparator
PT6
PT7
EDG6
EDG2
TC6 capture/compare register
MUX
MUX
Comparator
EDG7
EDG3
TC7 capture/compare register
Figure 25 Timer Block Diagram in Latch Mode
3-ect
MC68HC912DT128A Rev 2.0
189
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
÷1, 2, ..., 128
16-bit Free-running
16-bit load register
Prescaler
M clock
PT0
main timer
÷ 1, 4, 8, 16
16-bit modulus
down counter
Prescaler
M clock
RESET
0
Comparator
Pin logic
TC0 capture/compare register
PAC0
Delay counter
Delay counter
Delay counter
Delay counter
EDG0
EDG1
EDG2
EDG3
TC0H hold register
PA0H hold register
RESET
0
Comparator
PT1
PT2
PT3
Pin logic
Pin logic
Pin logic
TC1 capture/compare register
PAC1
TC1H hold register
PA1H hold register
RESET
0
Comparator
TC2 capture/compare register
PAC2
TC2H hold register
PA2H hold register
RESET
0
Comparator
TC3 capture/compare register
PAC3
TC3H hold register
PA3H hold register
Comparator
LATQ, BUFEN
PT4
PT5
Pin logic
Pin logic
EDG4
EDG0
TC4 capture/compare register
(queue mode)
MUX
MUX
Read TC3H
hold register
Comparator
EDG5
EDG1
TC5 capture/compare register
Read TC2H
hold register
Comparator
PT6
PT7
Pin logic
Pin logic
EDG6
EDG2
TC6 capture/compare register
MUX
MUX
Read TC1H
hold register
Comparator
Read TC0H
hold register
EDG7
EDG3
TC7 capture/compare register
Figure 26 Timer Block Diagram in Queue Mode
4-ect
MC68HC912DT128A Rev 2.0
190
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Introduction
Load holding register and reset pulse accumulator
0
0
0
0
EDG0
8-bit PAC0 (PACN0)
PT0
PT1
PT2
PT3
Edge detector
Edge detector
Edge detector
Edge detector
Delay counter
PA0H holding register
8-bit PAC1 (PACN1)
Interrupt
EDG1
Delay counter
PA1H holding register
8-bit PAC2 (PACN2)
EDG2
Delay counter
PA2H holding register
8-bit PAC3 (PACN3)
Interrupt
EDG3
Delay counter
PA3H holding register
Figure 27 8-Bit Pulse Accumulators Block Diagram
5-ect
MC68HC912DT128A Rev 2.0
191
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
To TCNT Counter
CLK1
CLK0
4:1 MUX
Clock select
Prescaled MCLK
(TMSK2 bits PR2-PR0)
(PAMOD)
Edge detector
PT7
Interrupt
MUX
8-bit PAC3 (PACN3)
8-bit PAC2 (PACN2)
PACA
Divide by 64
M clock
Interrupt
8-bit PAC1 (PACN1)
8-bit PAC0 (PACN0)
Delay counter
Edge detector
PACB
PT0
Figure 28 16-Bit Pulse Accumulators Block Diagram
6-ect
MC68HC912DT128A Rev 2.0
192
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Introduction
Pulse accumulator A
PAD
OC7
(OM7=1 or OL7=1) or (OC7M7 = 1)
Figure 29 Block Diagram for Port7 with Output compare / Pulse Accumulator A
16-bit Main Timer
Delay counter
PTn
Edge detector
Set CnF Interrupt
TCn Input Capture Reg.
TCnH I.C. Holding Reg.
BUFEN • LATQ • TFMOD
Figure 30 C3F-C0F Interrupt Flag Setting
7-ect
MC68HC912DT128A Rev 2.0
193
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
Enha nc e d Ca p ture Tim e r Mod e s of Op e ra tion
The Enhanced Capture Timer has 8 Input Capture, Output Compare (IC/
OC) channels same as on the HC12 standard timer (timer channels TC0
to TC7). When channels are selected as input capture by selecting the
IOSx bit in TIOS register, they are called Input Capture (IC) channels.
Four IC channels are the same as on the standard timer with one
capture register which memorizes the timer value captured by an action
on the associated input pin.
Four other IC channels, in addition to the capture register, have also one
buffer called holding register. This permits to memorize two different
timer values without generation of any interrupt.
Four 8-bit pulse accumulators are associated with the four buffered IC
channels. Each pulse accumulator has a holding register to memorize
their value by an action on its external input. Each pair of pulse
accumulators can be used as a 16-bit pulse accumulator.
The 16-bit modulus down-counter can control the transfer of the IC
registers contents and the pulse accumulators to the respective holding
registers for a given period, every time the count reaches zero.
The modulus down-counter can also be used as a stand-alone time base
with periodic interrupt capability.
IC Cha nne ls
The IC channels are composed of four standard IC registers and four
buffered IC channels.
An IC register is empty when it has been read or latched into the
holding register.
A holding register is empty when it has been read.
No n-Buffe re d IC
Cha nne ls
The main timer value is memorized in the IC register by a valid input pin
transition. If the corresponding NOVWx bit of the ICOVW register is
cleared, with a new occurrence of a capture, the contents of IC register
are overwritten by the new value.
8-ect
MC68HC912DT128A Rev 2.0
194
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Enhanced Capture Timer Modes of Operation
If the corresponding NOVWx bit of the ICOVW register is set, the
capture register cannot be written unless it is empty.
This will prevent the captured value to be overwritten until it is read.
Buffe re d IC
Cha nne ls
There are two modes of operations for the buffered IC channels.
•
IC Latch Mode:
When enabled (LATQ=1), the main timer value is memorized in the IC
register by a valid input pin transition.
The value of the buffered IC register is latched to its holding register by
the Modulus counter for a given period when the count reaches zero, by
a write $0000 to the modulus counter or by a write to ICLAT in the
MCCTL register.
If the corresponding NOVWx bit of the ICOVW register is cleared, with a
new occurrence of a capture, the contents of IC register are overwritten
by the new value. In case of latching, the contents of its holding register
are overwritten.
If the corresponding NOVWx bit of the ICOVW register is set, the capture
register or its holding register cannot be written by an event unless they
are empty (see IC Channels). This will prevent the captured value to be
overwritten until it is read or latched in the holding register.
•
IC queue mode:
When enabled (LATQ=0), the main timer value is memorized in the IC
register by a valid input pin transition.
If the corresponding NOVWx bit of the ICOVW register is cleared, with a
new occurrence of a capture, the value of the IC register will be transferred
to its holding register and the IC register memorizes the new timer value.
If the corresponding NOVWx bit of the ICOVW register is set, the capture
register or its holding register cannot be written by an event unless they
are empty (see IC Channels).
In queue mode, reads of holding register will latch the corresponding
pulse accumulator value to its holding register.
9-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
195
Enha nc e d Ca p ture Tim e r
Pulse
There are four 8-bit pulse accumulators with four 8-bit holding registers
Ac c um ula tors
associated with the four IC buffered channels. A pulse accumulator
counts the number of active edges at the input of its channel.
The user can prevent 8-bit pulse accumulators counting further than $FF
by PACMX control bit in ICSYS ($AB). In this case a value of $FF means
that 255 counts or more have occurred.
Each pair of pulse accumulators can be used as a 16-bit pulse
accumulator.
There are two modes of operation for the pulse accumulators.
Pulse
Ac c um ula to r
la tc h m o d e
The value of the pulse accumulator is transferred to its holding register
when the modulus down-counter reaches zero, a write $0000 to the
modulus counter or when the force latch control bit ICLAT is written.
At the same time the pulse accumulator is cleared.
Pulse
Ac c um ula to r
q ue ue m o d e
When queue mode is enabled, reads of an input capture holding register
will transfer the contents of the associated pulse accumulator to its
holding register.
At the same time the pulse accumulator is cleared.
Mod ulus
Down-Counte r
The modulus down-counter can be used as a time base to generate a
periodic interrupt. It can also be used to latch the values of the IC
registers and the pulse accumulators to their holding registers.
The action of latching can be programmed to be periodic or only once.
10-ect
MC68HC912DT128A Rev 2.0
196
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
Tim e r Re g iste r De sc rip tions
Input/output pins default to general-purpose I/O lines until an internal
function which uses that pin is specifically enabled. The timer overrides
the state of the DDR to force the I/O state of each associated port line
when an output compare using a port line is enabled. In these cases the
data direction bits will have no affect on these lines.
When a pin is assigned to output an on-chip peripheral function, writing
to this PORTT bit does not affect the pin but the data is stored in an
internal latch such that if the pin becomes available for general-purpose
output the driven level will be the last value written to the PORTT bit.
TIOS — Timer Input Capture/Output Compare Select
$0080
Bit 7
IOS7
0
6
IOS6
0
5
IOS5
0
4
IOS4
0
3
IOS3
0
2
IOS2
0
1
IOS1
0
Bit 0
IOS0
0
RESET:
Read or write anytime.
IOS[7:0] — Input Capture or Output Compare Channel Configuration
0 = The corresponding channel acts as an input capture
1 = The corresponding channel acts as an output compare.
CFORC — Timer Compare Force Register
$0081
Bit 7
FOC7
0
6
FOC6
0
5
FOC5
0
4
FOC4
0
3
FOC3
0
2
FOC2
0
1
FOC1
0
Bit 0
FOC0
0
RESET:
Read anytime but will always return $00 (1 state is transient). Write
anytime.
11-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
197
Enha nc e d Ca p ture Tim e r
FOC[7:0] — 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 “n” to occur
immediately. The action taken is the same as if a successful
comparison had just taken place with the TCn register except the
interrupt flag does not get set.
OC7M — Output Compare 7 Mask Register
$0082
Bit 7
OC7M7
0
6
OC7M6
0
5
OC7M5
0
4
OC7M4
0
3
OC7M3
0
2
OC7M2
0
1
OC7M1
0
Bit 0
OC7M0
0
RESET:
Read or write anytime.
The bits of OC7M correspond bit-for-bit with the bits of timer port
(PORTT). Setting the OC7Mn will set the corresponding port to be an
output port regardless of the state of the DDRTn bit when the
corresponding TIOSn bit is set to be an output compare. This does not
change the state of the DDRT bits. At successful OC7, for eachbit that
is set in OC7M, the corresponding data bit in OC7D is stored to the
corresponding bit of the timer port.
NOTE: OC7M has priority over output action on timer port enabled by OMn and
OLn bits in TCTL1 and TCTL2. If an OC7M bit is set, it prevents the
action of corresponding OM and OL bits on the selected timer port.
OC7D — Output Compare 7 Data Register
$0083
Bit 7
OC7D7
0
6
OC7D6
0
5
OC7D5
0
4
OC7D4
0
3
OC7D3
0
2
OC7D2
0
1
OC7D1
0
Bit 0
OC7D0
0
RESET:
Read or write anytime.
The bits of OC7D correspond bit-for-bit with the bits of timer port
(PORTT). When a successful OC7 compare occurs, for each bit that is
set in OC7M, the corresponding data bit in OC7D is stored to the
corresponding bit of the timer port.
12-ect
MC68HC912DT128A Rev 2.0
198
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
When the OC7Mn bit is set, a successful OC7 action will override a
successful OC[6:0] compare action during the same cycle; therefore, the
OCn action taken will depend on the corresponding OC7D bit.
TCNT — Timer Count Register
$0084–$0085
Bit 7
Bit 15
Bit 7
0
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
0
Bit 0
Bit 8
Bit 0
0
RESET:
0
0
0
0
0
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 (SMODN = 0).
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.
TSCR — Timer System Control Register
$0086
Bit 7
TEN
0
6
TSWAI
0
5
TSBCK
0
4
TFFCA
0
3
0
2
0
1
0
Bit 0
0
RESET:
Read or write anytime.
TEN — 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 since the E÷64 is generated by the timer prescaler.
13-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
199
Enha nc e d Ca p ture Tim e r
TSWAI — 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 accumulators and modulus down counters.
TSBCK — Timer and Modulus Counter Stop While in Background Mode
0 = Allows the timer and modulus counter to continue running while
in background mode.
1 = Disables the timer and modulus counter whenever the MCU is
in background mode. This is useful for emulation.
TBSCK does not stop the pulse accumulator.
TFFCA — Timer Fast Flag Clear All
0 = Allows the timer flag clearing to function normally.
1 = For TFLG1($8E), a read from an input capture or a write to the
output compare channel ($90–$9F) causes the corresponding
channel flag, CnF, to be cleared. For TFLG2 ($8F), any access
to the TCNT register ($84, $85) clears the TOF flag. Any
access to the PACN3 and PACN2 registers ($A2, $A3) clears
the PAOVF and PAIF flags in the PAFLG register ($A1). Any
access to the PACN1 and PACN0 registers ($A4, $A5) clears
the PBOVF flag in the PBFLG register ($B1). Any access to the
MCCNT register ($B6, $B7) clears the MCZF flag in the
MCFLG register ($A7). 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.
14-ect
MC68HC912DT128A Rev 2.0
200
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
TQCR — Reserved
$0087
Bit 7
6
0
5
0
4
0
3
0
2
0
1
0
Bit 0
RESET:
0
0
TCTL1 — Timer Control Register 1
$0088
Bit 7
OM7
0
6
OL7
0
5
OM6
0
4
OL6
0
3
OM5
0
2
OL5
0
1
Bit 0
OM4
0
OL4
0
RESET:
TCTL2 — Timer Control Register 2
$0089
Bit 7
OM3
0
6
OL3
0
5
OM2
0
4
OL2
0
3
OM1
0
2
OL1
0
1
OM0
0
Bit 0
OL0
0
RESET:
Read or write anytime.
OMn — Output Mode
OLn — Output Level
These eight pairs of control bits are encoded to specify the output
action to be taken as a result of a successful OCn compare. When
either OMn or OLn is one, the pin associated with OCn becomes an
output tied to OCn regardless of the state of the associated DDRT bit.
NOTE: To enable output action by OMn and OLn bits on timer port, the
corresponding bit in OC7M should be cleared.
Table 31 Compare Result Output Action
OMn
OLn
Action
0
0
1
1
0
1
0
1
Timer disconnected from output pin logic
Toggle OCn output line
Clear OCn output line to zero
Set OCn output line to one
To operate the 16-bit pulse accumulators A and B (PACA and PACB)
independently of input capture or output compare 7 and 0 respectively
the user must set the corresponding bits IOSn = 1, OMn = 0 and OLn
= 0. OC7M7 or OC7M0 in the OC7M register must also be cleared.
15-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
201
Enha nc e d Ca p ture Tim e r
TCTL3 — Timer Control Register 3
$008A
$008B
Bit 7
EDG7B
0
6
EDG7A
0
5
EDG6B
0
4
EDG6A
0
3
EDG5B
0
2
EDG5A
0
1
EDG4B
0
Bit 0
EDG4A
0
RESET:
TCTL4 — Timer Control Register 4
Bit 7
EDG3B
0
6
EDG3A
0
5
EDG2B
0
4
EDG2A
0
3
EDG1B
0
2
EDG1A
0
1
EDG0B
0
Bit 0
EDG0A
0
RESET:
Read or write anytime.
EDGnB, EDGnA — Input Capture Edge Control
These eight pairs of control bits configure the input capture edge
detector circuits.
Table 2 Edge Detector Circuit Configuration
EDGnB
EDGnA
Configuration
Capture disabled
0
0
1
1
0
1
0
1
Capture on rising edges only
Capture on falling edges only
Capture on any edge (rising or falling)
TMSK1 — Timer Interrupt Mask 1
$008C
Bit 7
C7I
0
6
C6I
0
5
C5I
0
4
3
2
C2I
0
1
C1I
0
Bit 0
C0I
0
C4I
0
C3I
0
RESET:
Read or write anytime.
The bits in TMSK1 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 hardware interrupt.
Read or write anytime.
C7I–C0I — Input Capture/Output Compare “x” Interrupt Enable.
16-ect
MC68HC912DT128A Rev 2.0
202
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
TMSK2 — Timer Interrupt Mask 2
$008D
Bit 7
TOI
0
6
0
0
5
PUPT
0
4
RDPT
0
3
TCRE
0
2
PR2
0
1
Bit 0
PR0
0
PR1
0
RESET:
Read or write anytime.
TOI — Timer Overflow Interrupt Enable
0 = Interrupt inhibited
1 = Hardware interrupt requested when TOF flag set
PUPT — Timer Port Pull-Up Resistor Enable
This enable bit controls pull-up resistors on the timer port pins when
the pins are configured as inputs.
0 = Disable pull-up resistor function
1 = Enable pull-up resistor function
RDPT — Timer Port Drive Reduction
This bit reduces the effective output driver size which can reduce
power supply current and generated noise depending upon pin
loading.
0 = Normal output drive capability
1 = Enable output drive reduction function
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
If TC7 = $0000 and TCRE = 1, TCNT will stay at $0000 continuously.
If TC7 = $FFFF and TCRE = 1, TOF will never be set when TCNT is
reset from $FFFF to $0000.
PR2, PR1, PR0 — Timer Prescaler Select
These three bits specify the number of ÷2 stages that are to be
inserted between the module clock and the main timer counter.
17-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
203
Enha nc e d Ca p ture Tim e r
Table 32 Prescaler Selection
PR2
0
PR1
0
PR0
0
Prescale Factor
1
2
0
0
1
0
1
0
4
0
1
1
8
1
0
0
16
32
64
128
1
0
1
1
1
0
1
1
1
The newly selected prescale factor will not take effect until the next
synchronized edge where all prescale counter stages equal zero.
TFLG1 — Main Timer Interrupt Flag 1
$008E
Bit 7
C7F
0
6
C6F
0
5
C5F
0
4
C4F
0
3
C3F
0
2
C2F
0
1
C1F
0
Bit 0
C0F
0
RESET:
TFLG1 indicates when interrupt conditions have occurred. To clear a bit
in the flag register, write a one to the bit.
Use of the TFMOD bit in the ICSYS register ($AB) in conjunction with the
use of the ICOVW register ($AA) allows a timer interrupt to be generated
after capturing two values in the capture and holding registers instead of
generating an interrupt for every capture.
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.
When TFFCA bit in TSCR register is set, a read from an input capture or
a write into an output compare channel ($90–$9F) will cause the
corresponding channel flag CnF to be cleared.
C7F–C0F — Input Capture/Output Compare Channel “n” Flag.
18-ect
MC68HC912DT128A Rev 2.0
204
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
TFLG2 — Main Timer Interrupt Flag 2
$008F
Bit 7
TOF
0
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
Bit 0
0
0
0
0
RESET:
TFLG2 indicates when interrupt conditions have occurred. To clear a bit
in the flag register, set the bit to one.
Read anytime. Write used in clearing mechanism (set bits cause
corresponding bits to be cleared).
Any access to TCNT will clear TFLG2 register if the TFFCA bit in TSCR
register is set.
TOF — Timer Overflow Flag
Set when 16-bit free-running timer overflows from $FFFF to $0000.
This bit is cleared automatically by a write to the TFLG2 register with
bit 7 set. (See also TCRE control bit explanation.)
TC0 — Timer Input Capture/Output Compare Register 0
$0090–$0091
$0092–$0093
$0094–$0095
$0096–$0097
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC1 — Timer Input Capture/Output Compare Register 1
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC2 — Timer Input Capture/Output Compare Register 2
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC3 — Timer Input Capture/Output Compare Register 3
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
19-ect
MC68HC912DT128A Rev 2.0
205
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
TC4 — Timer Input Capture/Output Compare Register 4
$0098–$0099
$009A–$009B
$009C–$009D
$009E–$009F
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC5 — Timer Input Capture/Output Compare Register 5
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC6 — Timer Input Capture/Output Compare Register 6
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC7 — Timer Input Capture/Output Compare Register 7
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
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 $0000.
PACTL — 16-Bit Pulse Accumulator A Control Register
$00A0
BIT 7
6
PAEN
0
5
PAMOD
0
4
PEDGE
0
3
CLK1
0
2
CLK0
0
1
PAOVI
0
BIT 0
PAI
0
0
0
RESET:
16-Bit Pulse Accumulator A (PACA) is formed by cascading the 8-bit
pulse accumulators PAC3 and PAC2.
When PAEN is set, the PACA is enabled. The PACA shares the input pin
with IC7.
Read: any time
Write: any time
20-ect
MC68HC912DT128A Rev 2.0
206
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
PAEN — Pulse Accumulator A System Enable
0 = 16-Bit Pulse Accumulator A system disabled. 8-bit PAC3 and
PAC2 can be enabled when their related enable bits in ICPACR
($A8) are set.
Pulse Accumulator Input Edge Flag (PAIF) function is disabled.
1 = Pulse Accumulator A system enabled. The two 8-bit pulse
accumulators PAC3 and PAC2 are cascaded to form the PACA
16-bit pulse accumulator. When PACA in enabled, the PACN3
and PACN2 registers contents are respectively the high and low
byte of the PACA.
PA3EN and PA2EN control bits in ICPACR ($A8) have no effect.
Pulse Accumulator Input Edge Flag (PAIF) function is enabled.
PAEN is independent from TEN. With timer disabled, the pulse
accumulator can still function unless pulse accumulator is disabled.
PAMOD — Pulse Accumulator Mode
0 = event counter mode
1 = gated time accumulation mode
PEDGE — Pulse Accumulator Edge Control
For PAMOD bit = 0 (event counter mode).
0 = falling edges on PT7 pin cause the count to be incremented
1 = rising edges on PT7 pin cause the count to be incremented
For PAMOD bit = 1 (gated time accumulation mode).
0 = PT7 input pin high enables M divided by 64 clock to Pulse
Accumulator and the trailing falling edge on PT7 sets the PAIF
flag.
1 = PT7 input pin low enables M divided by 64 clock to Pulse
Accumulator and the trailing rising edge on PT7 sets the PAIF
flag.
PAMOD PEDGE
Pin Action
0
0
1
1
0
1
0
1
Falling edge
Rising edge
Div. by 64 clock enabled with pin high level
Div. by 64 clock enabled with pin low level
If the timer is not active (TEN = 0 in TSCR), there is no divide-by-64
since the E÷64 clock is generated by the timer prescaler.
21-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
207
Enha nc e d Ca p ture Tim e r
CLK1, CLK0 — Clock Select Bits
CLK1
CLK0
Clock Source
0
0
1
0
1
0
Use timer prescaler clock as timer counter clock
Use PACLK as input to timer counter clock
Use PACLK/256 as timer counter clock frequency
Use PACLK/65536 as timer counter clock
frequency
1
1
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.
PAOVI — Pulse Accumulator A Overflow Interrupt enable
0 = interrupt inhibited
1 = interrupt requested if PAOVF is set
PAI — Pulse Accumulator Input Interrupt enable
0 = interrupt inhibited
1 = interrupt requested if PAIF is set
PAFLG — Pulse Accumulator A Flag Register
$00A1
BIT 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
PAOVF
0
BIT 0
PAIF
0
0
0
RESET:
Read or 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.
PAOVF — Pulse Accumulator A Overflow Flag
Set when the 16-bit pulse accumulator A overflows from $FFFF to
$0000,or when 8-bit pulse accumulator 3 (PAC3) overflows from $FF
to $00.
This bit is cleared automatically by a write to the PAFLG register with
bit 1 set.
22-ect
MC68HC912DT128A Rev 2.0
208
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
PAIF — Pulse Accumulator Input edge Flag
Set when the selected edge is detected at the PT7 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 PT7 input pin triggers
PAIF.
This bit is cleared by a write to the PAFLG register with bit 0 set.
Any access to the PACN3, PACN2 registers will clear all the flags in
this register when TFFCA bit in register TSCR($86) is set.
PACN3, PACN2 — Pulse Accumulators Count Registers
$00A2, $00A3
BIT 7
BIt 7
Bit 7
0
6
6
6
0
5
5
5
0
4
4
4
0
3
3
3
0
2
2
2
0
1
1
1
0
BIT 0
Bit 0
Bit 0
0
$00A2
$00A3
PACN3 (hi)
PACN2 (lo)
RESET:
Read or write any time.
The two 8-bit pulse accumulators PAC3 and PAC2 are cascaded to form
the PACA 16-bit pulse accumulator. When PACA in enabled (PAEN=1
in PACTL, $A0) the PACN3 and PACN2 registers contents are
respectively the high and low byte of the PACA.
When PACN3 overflows from $FF to $00, the Interrupt flag PAOVF in
PAFLG ($A1) 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.
PACN1, PACN0 — Pulse Accumulators Count Registers
$00A4, $00A5
BIT 7
BIt 7
Bit 7
0
6
6
6
0
5
5
5
0
4
4
4
0
3
3
3
0
2
2
2
0
1
1
1
0
BIT 0
Bit 0
Bit 0
0
$00A4
$00A5
PACN1 (hi)
PACN0 (lo)
RESET:
Read or write any time.
23-ect
MC68HC912DT128A Rev 2.0
209
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
The two 8-bit pulse accumulators PAC1 and PAC0 are cascaded to form
the PACB 16-bit pulse accumulator. When PACB in enabled, (PBEN=1
in PBCTL, $B0) the PACN1 and PACN0 registers contents are
respectively the high and low byte of the PACB.
When PACN1 overflows from $FF to $00, the Interrupt flag PBOVF in
PBFLG ($B1) 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.
MCCTL — 16-Bit Modulus Down-Counter Control Register
$00A6
BIT 7
MCZI
0
6
MODMC
0
5
RDMCL
0
4
ICLAT
0
3
FLMC
0
2
MCEN
0
1
MCPR1
0
BIT 0
MCPR0
0
RESET:
Read or write any time.
MCZI — Modulus Counter Underflow Interrupt Enable
0 = Modulus counter interrupt is disabled.
1 = Modulus counter interrupt is enabled.
MODMC — Modulus Mode Enable
0 = The counter counts once from the value written to it and will
stop at $0000.
1 = Modulus mode is enabled. When the counter reaches $0000,
the counter is loaded with the latest value written to the
modulus count register.
NOTE: For proper operation, the MCEN bit should be cleared before modifying
the MODMC bit in order to reset the modulus counter to $FF.
RDMCL — Read Modulus Down-Counter Load
0 = Reads of the modulus count register will return the present
value of the count register.
1 = Reads of the modulus count register will return the contents of
the load register.
24-ect
MC68HC912DT128A Rev 2.0
210
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
ICLAT — Input Capture Force Latch Action
When input capture latch mode is enabled (LATQ and BUFEN bit in
ICSYS ($AB) are set), a write one to this bit immediately forces the
contents of the input capture registers TC0 to TC3 and their
corresponding 8-bit pulse accumulators to be latched into the
associated holding registers. The pulse accumulators will be
automatically cleared when the latch action occurs.
Writing zero to this bit has no effect. Read of this bit will return always
zero.
FLMC — Force Load Register into the Modulus Counter Count Register
This bit is active only when the modulus down-counter is enabled
(MCEN=1).
A write one into this bit loads the load register into the modulus
counter count register. This also resets the modulus counter
prescaler. Write zero to this bit has no effect.
When MODMC=0, counter starts counting and stops at $0000.
Read of this bit will return always zero.
MCEN — Modulus Down-Counter Enable
0 = Modulus counter disabled.
1 = Modulus counter is enabled.
When MCEN=0, the counter is preset to $FFFF. This will prevent an
early interrupt flag when the modulus down-counter is enabled.
MCPR1, MCPR0 — Modulus Counter Prescaler select
These two bits specify the division rate of the modulus counter
prescaler.
The newly selected prescaler division rate will not be effective until a
load of the load register into the modulus counter count register
occurs.
MCPR1
MCPR0
Prescaler division rate
0
0
1
1
0
1
0
1
1
4
8
16
25-ect
MC68HC912DT128A Rev 2.0
211
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
MCFLG — 16-Bit Modulus Down-Counter FLAG Register
$00A7
BIT 7
MCZF
0
6
0
0
5
0
0
4
0
0
3
POLF3
0
2
POLF2
0
1
POLF1
0
BIT 0
POLF0
0
RESET:
Read: any time
Write: Only for clearing bit 7
MCZF — Modulus Counter Underflow Interrupt Flag
The flag is set when the modulus down-counter reaches $0000.
A write one to this bit clears the flag. Write zero has no effect.
Any access to the MCCNT register will clear the MCZF flag in this
register when TFFCA bit in register TSCR($86) is set.
POLF3 – POLF0 — First Input Capture Polarity Status
This are read only bits. Write to these bits has no effect.
Each status bit gives the polarity of the first edge which has caused
an input capture to occur after capture latch has been read.
Each POLFx corresponds to a timer PORTx input.
0 = The first input capture has been caused by a falling edge.
1 = The first input capture has been caused by a rising edge.
ICPAR — Input Control Pulse Accumulators Register
$00A8
BIT 7
6
0
0
5
0
0
4
0
0
3
PA3EN
0
2
PA2EN
0
1
PA1EN
0
BIT 0
PA0EN
0
0
0
RESET:
The 8-bit pulse accumulators PAC3 and PAC2 can be enabled only if
PAEN in PATCL ($A0) is cleared. If PAEN is set, PA3EN and PA2EN
have no effect.
The 8-bit pulse accumulators PAC1 and PAC0 can be enabled only if
PBEN in PBTCL ($B0) is cleared. If PBEN is set, PA1EN and PA0EN
have no effect.
Read or write any time.
26-ect
MC68HC912DT128A Rev 2.0
212
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
PAxEN — 8-Bit Pulse Accumulator ‘x’ Enable
0 = 8-Bit Pulse Accumulator is disabled.
1 = 8-Bit Pulse Accumulator is enabled.
DLYCT — Delay Counter Control Register
$00A9
BIT 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
BIT 0
DLY0
0
0
0
DLY1
0
RESET:
Read or write any time.
If enabled, after detection of a valid edge on input capture pin, the delay
counter counts the pre-selected number of M clock (module clock)
cycles, then it will generate a pulse on its output. The pulse is generated
only if the level of input signal, after the preset delay, is the opposite of
the level before the transition.This will avoid reaction to narrow input
pulses.
After counting, the counter will be cleared automatically.
Delay between two active edges of the input signal period should be
longer than the selected counter delay.
DLYx — Delay Counter Select
DLY1
DLY0
Delay
0
0
1
1
0
1
0
1
Disabled (bypassed)
256M clock cycles
512M clock cycles
1024 M clock cycles
ICOVW — Input Control Overwrite Register
$00AA
BIT 7
NOVW7
0
6
NOVW6
0
5
NOVW5
0
4
3
2
NOVW2
0
1
NOVW1
0
BIT 0
NOVW0
0
NOVW4
0
NOVW3
0
RESET:
Read or write any time.
27-ect
MC68HC912DT128A Rev 2.0
213
MOTOROLA
Enhanced Capture Timer
Enha nc e d Ca p ture Tim e r
An IC register is empty when it has been read or latched into the holding
register.
A holding register is empty when it has been read.
NOVWx — No Input Capture Overwrite
0 = The contents of the related capture register or holding register
can be overwritten when a new input capture or latch occurs.
1 = The related capture register or holding register cannot be
written by an event unless they are empty (see IC Channels).
This will prevent the captured value to be overwritten until it is
read or latched in the holding register.
ICSYS — Input Control System Control Register
$00AB
BIT 7
SH37
0
6
SH26
0
5
SH15
0
4
SH04
0
3
TFMOD
0
2
PACMX
0
1
BUFEN
0
BIT 0
LATQ
0
RESET:
Read: any time
Write: May be written once (SMODN=1). Writes are always permitted
when SMODN=0.
SHxy — Share Input action of Input Capture Channels x and y
0 = Normal operation
1 = The channel input ‘x’ causes the same action on the channel
‘y’. The port pin ‘x’ and the corresponding edge detector is
used to be active on the channel ‘y’.
TFMOD — Timer Flag-setting Mode
Use of the TFMOD bit in the ICSYS register ($AB) in conjunction with
the use of the ICOVW register ($AA) allows a timer interrupt to be
generated after capturing two values in the capture and holding
registers instead of generating an interrupt for every capture.
By setting TFMOD in queue mode, when NOVW bit is set and the
corresponding capture and holding registers are emptied, an input
capture event will first update the related input capture register with
28-ect
MC68HC912DT128A Rev 2.0
214
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
the main timer contents. At the next event the TCn data is transferred
to the TCnH register, The TCn is updated and the CnF interrupt flag
is set. See Figure 30.
In all other input capture cases the interrupt flag is set by a valid
external event on PTn.
0 = The timer flags C3F–C0F in TFLG1 ($8E) are set when a valid
input capture transition on the corresponding port pin occurs.
1 = If in queue mode (BUFEN=1 and LATQ=0), the timer flags
C3F–C0F in TFLG1 ($8E) are set only when a latch on the
corresponding holding register occurs.
If the queue mode is not engaged, the timer flags C3F–C0F
are set the same way as for TFMOD=0.
PACMX — 8-Bit Pulse Accumulators Maximum Count
0 = Normal operation. When the 8-bit pulse accumulator has
reached the value $FF, with the next active edge, it will be
incremented to $00.
1 = When the 8-bit pulse accumulator has reached the value $FF,
it will not be incremented further. The value $FF indicates a
count of 255 or more.
BUFEN — IC Buffer Enable
0 = Input Capture and pulse accumulator holding registers are
disabled.
1 = Input Capture and pulse accumulator holding registers are
enabled. The latching mode is defined by LATQ control bit.
Write one into ICLAT bit in MCCTL ($A6), when LATQ is set
will produce latching of input capture and pulse accumulators
registers into their holding registers.
LATQ — Input Control Latch or Queue Mode Enable
The BUFEN control bit should be set in order to enable the IC and
pulse accumulators holding registers. Otherwise LATQ latching
modes are disabled.
Write one into ICLAT bit in MCCTL ($A6), when LATQ and BUFEN
are set will produce latching of input capture and pulse accumulators
registers into their holding registers.
29-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
215
Enha nc e d Ca p ture Tim e r
0 = Queue Mode of Input Capture is enabled.
The main timer value is memorized in the IC register by a valid
input pin transition.
With a new occurrence of a capture, the value of the IC register
will be transferred to its holding register and the IC register
memorizes the new timer value.
1 = Latch Mode is enabled. Latching function occurs when
modulus down-counter reaches zero or a zero is written into
the count register MCCNT (see Buffered IC Channels).
With a latching event the contents of IC registers and 8-bit
pulse accumulators are transferred to their holding registers.
8-bit pulse accumulators are cleared.
TIMTST — Timer Test Register
$00AD
BIT 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
TCBYP
0
BIT 0
0
0
0
0
RESET:
Read: any time
Write: only in special mode (SMOD = 1).
TCBYP — Main Timer Divider Chain Bypass
0 = Normal operation
1 = For testing only. The 16-bit free-running timer counter is divided
into two 8-bit halves and the prescaler is bypassed. The clock
drives both halves directly.
When the high byte of timer counter TCNT ($84) overflows
from $FF to $00, the TOF flag in TFLG2 ($8F) will be set.
PORTT — Timer Port Data Register
$00AE
BIT 7
PT7
I/OC7
-
6
PT6
I/OC6
-
5
PT5
I/OC5
-
4
PT4
I/OC4
-
3
PT3
I/OC3
-
2
PT2
I/OC2
-
1
PT1
I/OC1
-
BIT 0
PT0
I/OC0
-
PORT
TIMER
RESET:
Read: any time (inputs return pin level; outputs return data register
contents)
30-ect
MC68HC912DT128A Rev 2.0
216
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
Write: data stored in an internal latch (drives pins only if configured for
output)
Since the Output Compare 7 shares the pin with Pulse Accumulator
input, the only way for Pulse accumulator to receive an independent
input from Output Compare 7 is setting both OM7 & OL7 to be zero, and
also OC7M7 in OC7M register to be zero.
OC7 is still able to reset the counter if enabled while PT7 is used as input
to Pulse Accumulator.
PORTT can be read anytime. When configured as an input, a read will
return the pin level. When configured as an output, a read will return the
latched output data.
NOTE: Writes do not change pin state when the pin is configured for timer
output. The minimum pulse width for pulse accumulator input should
always be greater than the width of two module clocks due to input
synchronizer circuitry. The minimum pulse width for the input capture
should always be greater than the width of two module clocks due to
input synchronizer circuitry.
DDRT — Data Direction Register for Timer Port
$00AF
BIT 7
DDT7
0
6
DDT6
0
5
DDT5
0
4
DDT4
0
3
DDT3
0
2
DDT2
0
1
DDT1
0
BIT 0
DDT0
0
RESET:
Read or write any time.
0 = Configures the corresponding I/O pin for input only
1 = Configures the corresponding I/O pin for output.
The timer forces the I/O state to be an output for each timer port line
associated with an enabled output compare. In these cases the data
direction bits will not be changed, but have no effect on the direction
of these pins. The DDRT will revert to controlling the I/O direction of
a pin when the associated timer output compare is disabled. Input
captures do not override the DDRT settings.
31-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
217
Enha nc e d Ca p ture Tim e r
PBCTL — 16-Bit Pulse Accumulator B Control Register
$00B0
BIT 7
6
PBEN
0
5
0
0
4
0
0
3
0
0
2
0
0
1
PBOVI
0
BIT 0
0
0
0
0
RESET:
Read or write any time.
16-Bit Pulse Accumulator B (PACB) is formed by cascading the 8-bit
pulse accumulators PAC1 and PAC0.
When PBEN is set, the PACB is enabled. The PACB shares the input pin
with IC0.
PBEN — Pulse Accumulator B System Enable
0 = 16-bit Pulse Accumulator system disabled. 8-bit PAC1 and
PAC0 can be enabled when their related enable bits in
ICPACR ($A8) are set.
1 = Pulse Accumulator B system enabled. The two 8-bit pulse
accumulators PAC1 and PAC0 are cascaded to form the
PACB 16-bit pulse accumulator. When PACB in enabled, the
PACN1 and PACN0 registers contents are respectively the
high and low byte of the PACB.
PA1EN and PA0EN control bits in ICPACR ($A8) have no
effect.
PBEN is independent from TEN. With timer disabled, the pulse
accumulator can still function unless pulse accumulator is disabled.
PBOVI — Pulse Accumulator B Overflow Interrupt enable
0 = interrupt inhibited
1 = interrupt requested if PBOVF is set
PBFLG — Pulse Accumulator B Flag Register
$00B1
BIT 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
PBOVF
0
BIT 0
0
0
0
0
RESET:
Read or write any time.
32-ect
MC68HC912DT128A Rev 2.0
218
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer Register Descriptions
PBOVF — Pulse Accumulator B Overflow Flag
This bit is set when the 16-bit pulse accumulator B overflows from
$FFFF to $0000, or when 8-bit pulse accumulator 1 (PAC1) overflows
from $FF to $00.
This bit is cleared by a write to the PBFLG register with bit 1 set.
Any access to the PACN1 and PACN0 registers will clear the PBOVF
flag in this register when TFFCA bit in register TSCR($86) is set.
PA3H–PA0H — 8-Bit Pulse Accumulators Holding Registers
$00B2–$00B5
BIT 0
BIT 7
BIt 7
Bit 7
BIt 7
Bit 7
0
6
6
6
6
6
0
5
5
5
5
5
0
4
4
4
4
4
0
3
3
3
3
3
0
2
2
2
2
2
0
1
1
1
1
1
0
$00B2
$00B3
$00B4
$00B5
RESET:
Bit 0
Bit 0
Bit 0
Bit 0
0
PA3H
PA2H
PA1H
PA0H
Read: any time
Write: has no effect.
These registers are used to latch the value of the corresponding pulse
accumulator when the related bits in register ICPAR ($A8) are enabled
(see Pulse Accumulators).
MCCNT — Modulus Down-Counter Count Register
$00B6, $00B7
BIT 7
BIt 15
Bit 7
1
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
1
BIT 0
Bit 8
Bit 0
1
$00B6
$00B7
MCCNTH
MCCNTL
RESET:
1
1
1
1
1
Read or write any time.
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 different result
than accessing them as a word.
If the RDMCL bit in MCCTL register is cleared, reads of the MCCNT
register will return the present value of the count register. If the RDMCL
33-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
219
Enha nc e d Ca p ture Tim e r
bit is set, reads of the MCCNT will return the contents of the load
register.
If a $0000 is written into MCCNT and modulus counter while LATQ and
BUFEN in ICSYS ($AB) register are set, the input capture and pulse
accumulator registers will be latched.
With a $0000 write to the MCCNT, the modulus counter will stay at zero
and does not set the MCZF flag in MCFLG register.
If modulus mode is enabled (MODMC=1), a write to this address will
update the load register with the value written to it. The count register will
not be updated with the new value until the next counter underflow.
The FLMC bit in MCCTL ($A6) can be used to immediately update the
count register with the new value if an immediate load is desired.
If modulus mode is not enabled (MODMC=0), a write to this address will
clear the prescaler and will immediately update the counter register with
the value written to it and down-counts once to $0000.
TC0H — Timer Input Capture Holding Register 0
$00B8–$00B9
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC1H — Timer Input Capture Holding Register 1
$00BA–$00BB
Bit 0
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 8
Bit 0
TC2H — Timer Input Capture Holding Register 2
$00BC–$00BD
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
TC3H — Timer Input Capture Holding Register 3
$00BE–$00BF
Bit 7
Bit 15
Bit 7
6
14
6
5
13
5
4
12
4
3
11
3
2
10
2
1
9
1
Bit 0
Bit 8
Bit 0
34-ect
MC68HC912DT128A Rev 2.0
220
Enhanced Capture Timer
MOTOROLA
Enhanced Capture Timer
Timer and Modulus Counter Operation in Different Modes
Read: any time
Write: has no effect.
These registers are used to latch the value of the input capture registers
TC0 – TC3. The corresponding IOSx bits in TIOS ($80) should be
cleared (see IC Channels).
Tim e r a nd Mod ulus Counte r Op e ra tion in Diffe re nt Mod e s
STOP:
Timer and modulus counter are off since clocks are
stopped.
BGDM:
WAIT:
Timer and modulus counter keep on running, unless
TSBCK (REG$86, bit5) is set to one.
Counters keep on running, unless TSWAI in TSCR ($86)
is set to one.
NORMAL: Timer and modulus counter keep on running, unless TEN
in TSCR($86) respectively MCEN in MCCTL ($A6) are
cleared.
TEN=0:
All 16-bit timer operations are stopped, can only access
the registers.
MCEN=0:
PAEN=1:
PAEN=0:
Modulus counter is stopped.
16-bit Pulse Accumulator A is active.
8-Bit Pulse Accumulators 3 and 2 can be enabled. (see
ICPAR)
PBEN=1:
PBEN=0:
16-bit Pulse Accumulator B is active.
8-Bit Pulse Accumulators 1 and 0 can be enabled. (see
ICPAR)
35-ect
MC68HC912DT128A Rev 2.0
MOTOROLA
Enhanced Capture Timer
221
Enha nc e d Ca p ture Tim e r
36-ect
MC68HC912DT128A Rev 2.0
222
Enhanced Capture Timer
MOTOROLA
Multip le Se ria l Inte rfa c e
Multip le Se ria l Inte rfa c e
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Serial Communication Interface (SCI). . . . . . . . . . . . . . . . . . . . . . . . 224
Serial Peripheral Interface (SPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Port S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Introd uc tion
The multiple serial interface (MSI) module consists of three independent
serial I/O sub-systems: two serial communication interfaces (SCI0 and
SCI1) and the serial peripheral interface (SPI). Each serial pin shares
function with the general-purpose port pins of port S. The SCI
subsystems are NRZ type systems that are compatible with standard
RS-232 systems. These SCI systems have a new single wire operation
mode which allows the unused pin to be available as general-purpose I/
O. The SPI subsystem, which is compatible with the M68HC11 SPI,
includes new features such as SS output and bidirectional mode.
1-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
223
Multip le Se ria l Inte rfa c e
Bloc k d ia g ra m
RxD0
TxD0
PS0
PS1
MSI
SCI0
SCI1
RxD1
TxD1
PS2
PS3
MISO/SISO
MOSI/MOMI
SCK
PS4
PS5
PS6
PS7
SPI
CS/SS
HC12A4 MSI BLOCK
Figure 31 Multiple Serial Interface Block Diagram
Se ria l Com m unic a tion Inte rfa c e (SCI)
Two serial communication interfaces are available on the
MC68HC912DT128A. These are NRZ format (one start, eight or nine
data, and one stop bit) asynchronous communication systems with
independent internal baud rate generation circuitry and SCI transmitters
and receivers. They can be configured for eight or nine data bits (one of
which may be designated as a parity bit, odd or even). If enabled, parity
is generated in hardware for transmitted and received data. Receiver
parity errors are flagged in hardware. The baud rate generator is based
on a modulus counter, allowing flexibility in choosing baud rates. There
is a receiver wake-up feature, an idle line detect feature, a loop-back
mode, and various error detection features. Two port pins for each SCI
provide the external interface for the transmitted data (TXD) and the
received data (RXD).
For a faster wake-up out of WAIT mode by a received SCI message,
both SCI have the capability of sending a receiver interrupt, if enabled,
when RAF (receiver active flag) is set. For compatibility with other
2--msi
MC68HC912DT128A Rev 2.0
224
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Communication Interface (SCI)
M68HC12 products, this feature is active only in WAIT mode and is
disabled when VDDPLL supply is at VSS level.
MCLK
BAUD RATE
CLOCK
SCI TRANSMITTER
MSB
LSB
DIVIDER
10-11 Bit SHIFT REG
PARITY
GENERATOR
Rx Baud Rate
Tx Baud Rate
TxD BUFFER/SCxDRL
SCxBD/SELECT
TxD
SCxCR1/SCI CTL 1
TxMTR CONTROL
SCxCR2/SCI CTL 2
DATA BUS
SCxSR1/INT STATUS
INT REQUEST LOGIC
RxD
SCI RECEIVER
TO
INTERNAL
LOGIC
PARITY
DETECT
DATA RECOVERY
MSB
LSB
10-11 BIT SHIFT REG
TxD BUFFER/SCxDRL
SCxCR1/SCI CTL 1
WAKE-UP LOGIC
SCxSR1/INT STATUS
SCxCR2/SCI CTL 2
INT REQUEST LOGIC
HC12A4 SCI BLOCK
Figure 32 Serial Communications Interface Block Diagram
Da ta Form a t
The serial data format requires the following conditions:
•
An idle-line in the high state before transmission or reception of a
message.
3-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
225
Multip le Se ria l Inte rfa c e
•
A start bit (logic zero), transmitted or received, that indicates the
start of each character.
•
•
Data that is transmitted or received least significant bit (LSB) first.
A stop bit (logic one), used to indicate the end of a frame. (A frame
consists of a start bit, a character of eight or nine data bits and a
stop bit.)
•
•
A BREAK is defined as the transmission or reception of a logic
zero for one frame or more.
This SCI supports hardware parity for transmit and receive.
SCI Ba ud Ra te
Ge ne ra tion
The basis of the SCI baud rate generator is a 13-bit modulus counter.
This counter gives the generator the flexibility necessary to achieve a
reasonable level of independence from the CPU operating frequency
and still be able to produce standard baud rates with a minimal amount
of error. The clock source for the generator comes from the M Clock.
Table 33 Baud Rate Generation
Desired
SCI Baud Rate
BR Divisor for
M = 4.0 MHz
BR Divisor for
M = 8.0 MHz
110
300
2273
833
417
208
104
52
4545
2273
833
417
208
104
52
600
1200
2400
4800
9600
14400
19200
38400
26
17
35
13
26
—
13
SCI Re g iste r
De sc rip tions
Control and data registers for the SCI subsystem are described below.
The memory address indicated for each register is the default address
that is in use after reset. Both SCI have identical control registers
mapped in two blocks of eight bytes.
4-msi
MC68HC912DT128A Rev 2.0
226
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Communication Interface (SCI)
SC0BDH/SC1BDH — SCI Baud Rate Control Register
$00C0/$00C8
Bit 7
BTST
0
6
BSPL
0
5
BRLD
0
4
SBR12
0
3
SBR11
0
2
SBR10
0
1
SBR9
0
Bit 0
SBR8
0
High
RESET:
SC0BDL/SC1BDL — SCI Baud Rate Control Register
$00C1/$00C9
Bit 7
SBR7
0
6
SBR6
0
5
SBR5
0
4
SBR4
0
3
SBR3
0
2
SBR2
1
1
SBR1
0
Bit 0
SBR0
0
Low
RESET:
SCxBDH and SCxBDL are considered together as a 16-bit baud rate
control register.
Read any time. Write SBR[12:0] anytime. Low order byte must be written
for change to take effect. Write SBR[15:13] only in special modes. The
value in SBR[12:0] determines the baud rate of the SCI. The desired
baud rate is determined by the following formula:
MCLK
SCI Baud Rate = --------------------
16 × BR
which is equivalent to:
MCLK
BR = -----------------------------------------------
16 × SCI Baud Rate
BR is the value written to bits SBR[12:0] to establish baud rate.
NOTE: The baud rate generator is disabled until TE or RE bit in SCxCR2
register is set for the first time after reset, and/or the baud rate generator
is disabled when SBR[12:0] = 0.
BTST — Reserved for test function
BSPL — Reserved for test function
BRLD — Reserved for test function
5-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
227
Multip le Se ria l Inte rfa c e
SC0CR1/SC1CR1 — SCI Control Register 1
$00C2/$00CA
Bit 7
LOOPS
0
6
WOMS
0
5
RSRC
0
4
M
0
3
WAKE
0
2
ILT
0
1
PE
0
Bit 0
PT
0
RESET:
Read or write anytime.
LOOPS — SCI LOOP Mode/Single Wire Mode Enable
0 = SCI transmit and receive sections operate normally.
1 = SCI receive section is disconnected from the RXD pin and the
RXD pin is available as general purpose I/O. The receiver input
is determined by the RSRC bit. The transmitter output is
controlled by the associated DDRS bit. Both the transmitter
and the receiver must be enabled to use the LOOP or the
single wire mode.
If the DDRS bit associated with the TXD pin is set during the LOOPS
= 1, the TXD pin outputs the SCI waveform. If the DDRS bit
associated with the TXD pin is clear during the LOOPS = 1, the TXD
pin becomes high (IDLE line state) for RSRC = 0 and high impedance
for RSRC = 1. Refer to Table 34.
WOMS — Wired-Or Mode for Serial Pins
This bit controls the two pins (TXD and RXD) associated with the SCIx
section.
0 = Pins operate in a normal mode with both high and low drive
capability. To affect the RXD bit, that bit would have to be
configured as an output (via DDRS0/2) which is the single wire
case when using the SCI. WOMS bit still affects
general-purpose output on TXD and RXD pins when SCIx is
not using these pins.
1 = Each pin operates in an open drain fashion if that pin is
declared as an output.
6-msi
MC68HC912DT128A Rev 2.0
228
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Communication Interface (SCI)
RSRC — Receiver Source
When LOOPS = 1, the RSRC bit determines the internal feedback
path for the receiver.
0 = Receiver input is connected to the transmitter internally (not
TXD pin)
1 = Receiver input is connected to the TXD pin
Table 34 Loop Mode Functions
LOOPS RSRC DDRS1(3) WOMS
Function of Port S Bit 1/3
0
1
1
1
x
0
0
0
x
0
1
1
x
0/1
1
Normal Operations
LOOP mode without TXD output(TXD = High Impedance)
LOOP mode with TXD output (CMOS)
1
LOOP mode with TXD output (open-drain)
Single wire mode without TXD output
(the pin is used as receiver input only, TXD = High Impedance)
1
1
0
x
Single wire mode with TXD output
(the output is also fed back to receiver input, CMOS)
1
1
1
1
1
1
0
1
Single wire mode for the receiving and transmitting(open-drain)
M — Mode (select character format)
0 = One start, eight data, one stop bit
1 = One start, eight data, ninth data, one stop bit
WAKE — Wake-up by Address Mark/Idle
0 = Wake up by IDLE line recognition
1 = Wake up by address mark (last data bit set)
ILT — Idle Line Type
Determines which of two types of idle line detection will be used by
the SCI receiver.
0 = Short idle line mode is enabled.
1 = Long idle line mode is detected.
In the short mode, the SCI circuitry begins counting ones in the search
for the idle line condition immediately after the start bit. This means
that the stop bit and any bits that were ones before the stop bit could
be counted in that string of ones, resulting in earlier recognition of an
idle line.
7-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
229
Multip le Se ria l Inte rfa c e
In the long mode, the SCI circuitry does not begin counting ones in the
search for the idle line condition until a stop bit is received. Therefore,
the last byte’s stop bit and preceding “1” bits do not affect how quickly
an idle line condition can be detected.
PE — Parity Enable
0 = Parity is disabled.
1 = Parity is enabled.
PT — Parity Type
If parity is enabled, this bit determines even or odd parity for both the
receiver and the transmitter.
0 = Even parity is selected. An even number of ones in the data
character causes the parity bit to be zero and an odd number
of ones causes the parity bit to be one.
1 = Odd parity is selected. An odd number of ones in the data
character causes the parity bit to be zero and an even number
of ones causes the parity bit to be one.
SC0CR2/SC1CR2 — SCI Control Register 2
$00C3/$00CB
Bit 7
TIE
0
6
TCIE
0
5
RIE
0
4
ILIE
0
3
TE
0
2
RE
0
1
RWU
0
Bit 0
SBK
0
RESET:
Read or write anytime.
TIE — Transmit Interrupt Enable
0 = TDRE interrupts disabled
1 = SCI interrupt will be requested whenever the TDRE status flag
is set.
TCIE — Transmit Complete Interrupt Enable
0 = TC interrupts disabled
1 = SCI interrupt will be requested whenever the TC status flag is
set.
8-msi
MC68HC912DT128A Rev 2.0
230
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Communication Interface (SCI)
RIE — Receiver Interrupt Enable
0 = RDRF and OR interrupts disabled, RAF interrupt in WAIT mode
disabled
1 = SCI interrupt will be requested whenever the RDRF or OR
status flag is set, or when RAF is set while in WAIT mode with
VDDPLL high.
ILIE — Idle Line Interrupt Enable
0 = IDLE interrupts disabled
1 = SCI interrupt will be requested whenever the IDLE status flag
is set.
TE — Transmitter Enable
0 = Transmitter disabled
1 = SCI transmit logic is enabled and the TXD pin (Port S bit 1/bit
3) is dedicated to the transmitter. The TE bit can be used to
queue an idle preamble.
RE — Receiver Enable
0 = Receiver disabled
1 = Enables the SCI receive circuitry.
RWU — Receiver Wake-Up Control
0 = Normal SCI Receiver
1 = Enables the wake-up function and inhibits further receiver
interrupts. Normally hardware wakes the receiver by
automatically clearing this bit.
SBK — Send Break
0 = Break generator off
1 = Generate a break code (at least 10 or 11 contiguous zeros).
As long as SBK remains set the transmitter will send zeros. When
SBK is changed to zero, the current frame of all zeros is finished
before the TxD line goes to the idle state. If SBK is toggled on and off,
the transmitter will send only 10 (or 11) zeros and then revert to mark
idle or sending data.
9-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
231
Multip le Se ria l Inte rfa c e
SC0SR1/SC1SR1 — SCI Status Register 1
$00C4/$00CC
Bit 7
TDRE
1
6
TC
1
5
RDRF
0
4
IDLE
0
3
OR
0
2
NF
0
1
FE
0
Bit 0
PF
0
RESET:
The bits in these registers are set by various conditions in the SCI
hardware and are automatically cleared by special acknowledge
sequences. The receive related flag bits in SCxSR1 (RDRF, IDLE,
OR, NF, FE, and PF) are all cleared by a read of the SCxSR1 register
followed by a read of the transmit/receive data register low byte.
However, only those bits which were set when SCxSR1 was read will
be cleared by the subsequent read of the transmit/receive data
register low byte. The transmit related bits in SCxSR1 (TDRE and TC)
are cleared by a read of the SCxSR1 register followed by a write to
the transmit/receive data register low byte.
Read anytime (used in auto clearing mechanism). Write has no
meaning or effect.
TDRE — Transmit Data Register Empty Flag
New data will not be transmitted unless SCxSR1 is read before writing
to the transmit data register. Reset sets this bit.
0 = SCxDR busy
1 = Any byte in the transmit data register is transferred to the serial
shift register so new data may now be written to the transmit
data register.
TC — Transmit Complete Flag
Flag is set when the transmitter is idle (no data, preamble, or break
transmission in progress). Clear by reading SCxSR1 with TC set and
then writing to SCxDR.
0 = Transmitter busy
1 = Transmitter is idle
10-msi
MC68HC912DT128A Rev 2.0
232
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Communication Interface (SCI)
RDRF — Receive Data Register Full Flag
Once cleared, IDLE is not set again until the RxD line has been active
and becomes idle again. RDRF is set if a received character is ready
to be read from SCxDR. Clear the RDRF flag by reading SCxSR1 with
RDRF set and then reading SCxDR.
0 = SCxDR empty
1 = SCxDR full
IDLE — Idle Line Detected Flag
Receiver idle line is detected (the receipt of a minimum of 10/11
consecutive ones). This bit will not be set by the idle line condition
when the RWU bit is set. Once cleared, IDLE will not be set again until
after RDRF has been set (after the line has been active and becomes
idle again).
0 = RxD line is idle
1 = RxD line is active
OR — Overrun Error Flag
New byte is ready to be transferred from the receive shift register to
the receive data register and the receive data register is already full
(RDRF bit is set). Data transfer is inhibited until this bit is cleared.
0 = No overrun
1 = Overrun detected
NF — Noise Error Flag
Set during the same cycle as the RDRF bit but not set in the case of
an overrun (OR).
0 = Unanimous decision
1 = Noise on a valid start bit, any of the data bits, or on the stop bit
FE — Framing Error Flag
Set when a zero is detected where a stop bit was expected. Clear the
FE flag by reading SCxSR1 with FE set and then reading SCxDR.
0 = Stop bit detected
1 = Zero detected rather than a stop bit
11-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
233
Multip le Se ria l Inte rfa c e
PF — Parity Error Flag
Indicates if received data’s parity matches parity bit. This feature is
active only when parity is enabled. The type of parity tested for is
determined by the PT (parity type) bit in SCxCR1.
0 = Parity correct
1 = Incorrect parity detected
SC0SR2/SC1SR2 — SCI Status Register 2
$00C5/$00CD
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
RAF
0
0
0
RESET:
Read anytime. Write has no meaning or effect.
RAF — Receiver Active Flag
This bit is controlled by the receiver front end. It is set during the RT1
time period of the start bit search. It is cleared when an idle state is
detected or when the receiver circuitry detects a false start bit
(generally due to noise or baud rate mismatch).
0 = A character is not being received
1 = A character is being received
If enabled with RIE = 1, RAF set generates an interrupt when
VDDPLL is high while in WAIT mode.
SC0DRH/SC1DRH — SCI Data Register High
$00C6/$00CE
Bit 7
R8
6
5
0
4
0
3
0
2
0
1
0
Bit 0
0
T8
—
RESET:
—
—
—
—
—
—
—
SC0DRL/SC1DRL — SCI Data Register Low
$00C7/$00CF
Bit 7
R7/T7
—
6
R6/T6
—
5
R5/T5
—
4
R4/T4
—
3
R3/T3
—
2
R2/T2
—
1
R1/T1
—
Bit 0
R0/T0
—
RESET:
12-msi
MC68HC912DT128A Rev 2.0
234
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Peripheral Interface (SPI)
R8 — Receive Bit 8
Read anytime. Write has no meaning or affect.
This bit is the ninth serial data bit received when the SCI system is
configured for nine-data-bit operation.
T8 — Transmit Bit 8
Read or write anytime.
This bit is the ninth serial data bit transmitted when the SCI system is
configured for nine-data-bit operation. When using 9-bit data format
this bit does not have to be written for each data word. The same
value will be transmitted as the ninth bit until this bit is rewritten.
R7/T7–R0/T0 — Receive/Transmit Data Bits 7 to 0
Reads access the eight bits of the read-only SCI receive data register
(RDR). Writes access the eight bits of the write-only SCI transmit data
register (TDR). SCxDRL:SCxDRH form the 9-bit data word for the
SCI. If the SCI is being used with a 7- or 8-bit data word, only SCxDRL
needs to be accessed. If a 9-bit format is used, the upper register
should be written first to ensure that it is transferred to the transmitter
shift register with the lower register.
Se ria l Pe rip he ra l Inte rfa c e (SPI)
The serial peripheral interface allows the MC68HC912DT128A to
communicate synchronously with peripheral devices and other
microprocessors. The SPI system in the MC68HC912DT128A can
operate as a master or as a slave. The SPI is also capable of
interprocessor communications in a multiple master system.
When the SPI is enabled, all pins that are defined by the configuration
as inputs will be inputs regardless of the state of the DDRS bits for those
pins. All pins that are defined as SPI outputs will be outputs only if the
DDRS bits for those pins are set. Any SPI output whose corresponding
DDRS bit is cleared can be used as a general-purpose input.
A bidirectional serial pin is possible using the DDRS as the direction
control.
13-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
235
Multip le Se ria l Inte rfa c e
SPI Ba ud Ra te
Ge ne ra tion
The E Clock is input to a divider series and the resulting SPI clock rate
may be selected to be E divided by 2, 4, 8, 16, 32, 64, 128 or 256. Three
bits in the SP0BR register control the SPI clock rate. This baud rate
generator is activated only when SPI is in the master mode and serial
transfer is taking place. Otherwise this divider is disabled to save power.
SPI Op e ra tion
In the SPI system the 8-bit data register in the master and the 8-bit data
register in the slave are linked to form a distributed 16-bit register. When
a data transfer operation is performed, this 16-bit register is serially
shifted eight bit positions by the SCK clock from the master so the data
is effectively exchanged between the master and the slave. Data written
to the SP0DR register of the master becomes the output data for the
slave and data read from the SP0DR register of the master after a
transfer operation is the input data from the slave.
14-msi
MC68HC912DT128A Rev 2.0
236
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Peripheral Interface (SPI)
MCU P CLOCK
(SAME AS E RATE)
S
M
MISO
PS4
M
S
DIVIDER
MOSI
PS5
8-BIT SHIFT REGISTER
READ DATA BUFFER
÷2 ÷4 ÷8 ÷16 ÷32 ÷64 ÷128 ÷256
SP0DR SPI DATA REGISTER
SELECT
LSBF
SHIFT CONTROL LOGIC
PIN
CONTROL
LOGIC
CLOCK
SCK
PS6
S
CLOCK
LOGIC
SP0BR SPI BAUD RATE REGISTER
SPI CONTROL
M
SS
PS7
MSTR
SPE
SWOM
SP0SR SPI STATUS REGISTER
SP0CR1 SPI CONTROL REGISTER 1 SP0CR2 SPI CONTROL REGISTER 2
SPI
INTERRUPT
REQUEST
INTERNAL BUS
HC12 SPI BLOCK
Figure 33 Serial Peripheral Interface Block Diagram
A clock phase control bit (CPHA) and a clock polarity control bit (CPOL)
in the SP0CR1 register select one of four possible clock formats to be
used by the SPI system. The CPOL bit simply selects non-inverted or
inverted clock. The CPHA bit is used to accommodate two
fundamentally different protocols by shifting the clock by one half cycle
or no phase shift.
15-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
237
Multip le Se ria l Inte rfa c e
Transfer
SCK (CPOL=0)
SCK (CPOL=1)
Begin
End
SAMPLE I
(MOSI/MISO)
CHANGE O
(MOSI pin)
CHANGE O
(MISO pin)
SEL SS (O)
(Master only)
SEL SS (I)
tL
tT
tI
tL
MSB first (LSBF=0):
LSB first (LSBF=1):
MSB
LSB
Bit 6
Bit 1
Bit 5
Bit 2
Bit 4
Bit 3
Bit 3
Bit 4
Bit 2
Bit 5
Bit 1
Bit 6
LSB Minimum 1/2 SCK
MSB
for tT, tl, tL
HC12 SPI CLOCK FORM 0
Figure 34 SPI Clock Format 0 (CPHA = 0)
16-msi
MC68HC912DT128A Rev 2.0
238
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Peripheral Interface (SPI)
Transfer
SCK (CPOL=0)
SCK (CPOL=1)
Begin
End
SAMPLE I
(MOSI/MISO)
CHANGE O
(MOSI pin)
CHANGE O
(MISO pin)
SEL SS (O)
(Master only)
SEL SS (I)
tL
tT
tI
tL
MSB first (LSBF=0):
LSB first (LSBF=1):
MSB
LSB
Bit 6
Bit 1
Bit 5
Bit 2
Bit 4
Bit 3
Bit 3
Bit 4
Bit 2
Bit 5
Bit 1
Bit 6
LSB Minimum 1/2 SCK
MSB
for tT, tl, tL
HC12 SPI CLOCK FORM 1
Figure 35 SPI Clock Format 1 (CPHA = 1)
SS Outp ut
Available in master mode only, SS output is enabled with the SSOE bit
in the SP0CR1 register if the corresponding DDRS is set. The SS output
pin will be connected to the SS input pin of the external slave device. The
SS output automatically goes low for each transmission to select the
external device and it goes high during each idling state to deselect
external devices.
Table 35 SS Output Selection
DDRS7
SSOE
Master Mode
SS Input with MODF Feature
Reserved
Slave Mode
SS Input
SS Input
SS Input
SS Input
0
0
1
1
0
1
0
1
General-Purpose Output
SS Output
17-msi
MC68HC912DT128A Rev 2.0
239
MOTOROLA
Multiple Serial Interface
Multip le Se ria l Inte rfa c e
Bid ire c tiona l
Mod e (MOMI or
SISO)
In bidirectional mode, the SPI uses only one serial data pin for external
device interface. The MSTR bit decides which pin to be used. The MOSI
pin becomes 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
direction of each serial I/O pin depends on the corresponding DDRS bit.
Figure 36 Normal Mode and Bidirectional Mode
When SPE=1
Master Mode
MSTR=1
Slave Mode
MSTR=0
Serial Out
Serial In
MO
MI
SI
Normal
Mode
SPC0=0
DDRS4
SPI
SPI
DDRS5
Serial In
Serial Out
SO
SWOM enables open drain output.
SWOM enables open drain output.
Serial Out
Serial In
MOMI
PS4
PS5
Bidirectional
Mode
DDRS4
SPI
SPI
DDRS5
SPC0=1
Serial In
Serial Out
SISO
SWOM enables open drain output. PS4 becomes GPIO.
SWOM enables open drain output. PS5 becomes GPIO.
Re g iste r
De sc rip tions
Control and data registers for the SPI subsystem are described below.
The memory address indicated for each register is the default address
that is in use after reset. For more information refer to Operating
Modes.
SP0CR1 — SPI Control Register 1
$00D0
Bit 7
SPIE
0
6
SPE
0
5
SWOM
0
4
MSTR
0
3
CPOL
0
2
CPHA
1
1
SSOE
0
Bit 0
LSBF
0
RESET:
Read or write anytime.
SPIE — SPI Interrupt Enable
0 = SPI interrupts are inhibited
1 = Hardware interrupt sequence is requested each time the SPIF
or MODF status flag is set
18-msi
MC68HC912DT128A Rev 2.0
240
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Peripheral Interface (SPI)
SPE — SPI System Enable
0 = SPI internal hardware is initialized and SPI system is in a
low-power disabled state.
1 = PS[4:7] are dedicated to the SPI function
When MODF is set, SPE always reads zero. SP0CR1 must be written
as part of a mode fault recovery sequence.
SWOM — Port S Wired-OR Mode
Controls not only SPI output pins but also the general-purpose output
pins (PS[4:7]) which are not used by SPI.
0 = SPI and/or PS[4:7] output buffers operate normally
1 = SPI and/or PS[4:7] output buffers behave as open-drain
outputs
MSTR — SPI Master/Slave Mode Select
0 = Slave mode
1 = Master mode
When MODF is set, MSTR always reads zero. SP0CR1 must be
written as part of a mode fault recovery sequence.
CPOL, CPHA — SPI Clock Polarity, Clock Phase
These two bits are used to specify the clock format to be used in SPI
operations. When the clock polarity bit is cleared and data is not being
transferred, the SCK pin of the master device is low. When CPOL is
set, SCK idles high. See Figure 34 and Figure 35.
SSOE — Slave Select Output Enable
The SS output feature is enabled only in the master mode by
asserting the SSOE and DDRS7.
LSBF — SPI LSB First enable
0 = Data is transferred most significant bit first
1 = Data is transferred least significant bit first
Normally data is transferred most significant bit first.This bit does not
affect the position of the MSB and LSB in the data register. Reads and
writes of the data register will always have MSB in bit 7.
19-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
241
Multip le Se ria l Inte rfa c e
SP0CR2 — SPI Control Register 2
$00D1
Bit 7
6
0
0
5
0
0
4
0
0
3
PUPS
1
2
RDPS
0
1
SSWAI
0
Bit 0
SPC0
0
0
0
RESET:
Read or write anytime.
PUPS — Pull-Up Port S Enable
0 = No internal pull-ups on port S
1 = All port S input pins have an active pull-up device. If a pin is
programmed as output, the pull-up device becomes inactive
RDPS — Reduce Drive of Port S
0 = Port S output drivers operate normally
1 = All port S output pins have reduced drive capability for lower
power and less noise
SSWAI — Serial Interface Stop in WAIT mode
0 = Serial interface clock operates normally
1 = Halt serial interface clock generation in WAIT mode
SPC0 — Serial Pin Control 0
This bit decides serial pin configurations with MSTR control bit.
SPC0(1)
MISO(2)
MOSI(3)
SCK(4)
SS(5)
Pin Mode
MSTR
#1
#2
0
Slave Out Slave In
SCK In
SS In
Normal
0
Master
Master In
1
SCK Out
SCK In
SS I/O
Out
#3
#4
0
1
Slave I/O
GPI/O
GPI/O
SS In
Bidirectional
1
Master I/O SCK Out
SS I/O
1. The serial pin control 0 bit enables bidirectional configurations.
2. Slave output is enabled if DDRS4 = 1, SS = 0 and MSTR = 0. (#1, #3)
3. Master output is enabled if DDRS5 = 1 and MSTR = 1. (#2, #4)
4. SCK output is enabled if DDRS6 = 1 and MSTR = 1. (#2, #4)
5. SS output is enabled if DDRS7 = 1, SSOE = 1 and MSTR = 1. (#2, #4)
20-msi
MC68HC912DT128A Rev 2.0
242
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Serial Peripheral Interface (SPI)
SP0BR — SPI Baud Rate Register
$00D2
Bit 7
6
0
0
5
0
0
4
0
0
3
0
0
2
SPR2
0
1
SPR1
0
Bit 0
SPR0
0
0
0
RESET:
Read anytime. Write anytime.
At reset, E Clock divided by 2 is selected.
SPR[2:0] — SPI Clock (SCK) Rate Select Bits
These bits are used to specify the SPI clock rate.
Table 36 SPI Clock Rate Selection
E Clock
Divisor
Frequency at
Frequency at
SPR2
SPR1
SPR0
E Clock = 4 MHz E Clock = 8 MHz
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
2
4
2.0 MHz
1.0 MHz
500 kHz
250 kHz
125 kHz
62.5 kHz
31.3 kHz
15.6 kHz
4.0 MHz
2.0 MHz
1.0 MHz
500 KHz
250 KHz
125 KHz
62.5 KHz
31.3 KHz
8
16
32
64
128
256
SP0SR — SPI Status Register
$00D3
Bit 7
SPIF
0
6
WCOL
0
5
0
0
4
MODF
0
3
0
0
2
0
0
1
0
0
Bit 0
0
0
RESET:
Read anytime. Write has no meaning or effect.
SPIF — SPI Interrupt Request
SPIF is set after the eighth SCK cycle in a data transfer and it is
cleared by reading the SP0SR register (with SPIF set) followed by an
access (read or write) to the SPI data register.
21-msi
MC68HC912DT128A Rev 2.0
MOTOROLA
Multiple Serial Interface
243
Multip le Se ria l Inte rfa c e
WCOL — Write Collision Status Flag
The MCU write is disabled to avoid writing over the data being
transferred. No interrupt is generated because the error status flag
can be read upon completion of the transfer that was in progress at
the time of the error. Automatically cleared by a read of the SP0SR
(with WCOL set) followed by an access (read or write) to the SP0DR
register.
0 = No write collision
1 = Indicates that a serial transfer was in progress when the MCU
tried to write new data into the SP0DR data register.
MODF — SPI Mode Error Interrupt Status Flag
This bit is set automatically by SPI hardware if the MSTR control bit is
set and the slave select input pin becomes zero. This condition is not
permitted in normal operation. In the case where DDRS bit 7 is set,
the PS7 pin is a general-purpose output pin or SS output pin rather
than being dedicated as the SS input for the SPI system. In this
special case the mode fault function is inhibited and MODF remains
cleared. This flag is automatically cleared by a read of the SP0SR
(with MODF set) followed by a write to the SP0CR1 register.
SP0DR — SPI Data Register
$00D5
Bit 7
Bit 7
6
6
5
5
4
4
3
3
2
2
1
1
Bit 0
Bit 0
Read anytime (normally only after SPIF flag set). Write anytime (see
WCOL write collision flag).
Reset does not affect this address.
This 8-bit register is both the input and output register for SPI data.
Reads of this register are double buffered but writes cause data to
written directly into the serial shifter. In the SPI system the 8-bit data
register in the master and the 8-bit data register in the slave are linked
by the MOSI and MISO wires to form a distributed 16-bit register. When
a data transfer operation is performed, this 16-bit register is serially
shifted eight bit positions by the SCK clock from the master so the data
is effectively exchanged between the master and the slave. Note that
22-msi
MC68HC912DT128A Rev 2.0
244
Multiple Serial Interface
MOTOROLA
Multiple Serial Interface
Port S
some slave devices are very simple and either accept data from the
master without returning data to the master or pass data to the master
without requiring data from the master.
Port S
In all modes, port S bits PS[7:0] can be used for either general-purpose
I/O, or with the SCI and SPI subsystems. During reset, port S pins are
configured as high-impedance inputs (DDRS is cleared).
PORTS — Port S Data Register
$00D6
Bit 7
PS7
6
5
4
3
2
1
Bit 0
PS0
PS6
SCK
PS5
PS4
PS3
TXD1
PS2
RXD1
PS1
TXD0
MSI
SS
CS
MOSI
MOMI
MISO
SISO
RXD0
RESET:
-
-
-
-
-
-
-
-
Read anytime (inputs return pin level; outputs return pin driver input
level). Write data stored in internal latch (drives pins only if configured
for output). Writes do not change pin state when pin configured for SPI
or SCI output.
After reset all bits are configured as general-purpose inputs.
Port S shares function with the on-chip serial systems (SPI and SCI0/1).
DDRS — Data Direction Register for Port S
$00D7
Bit 7
DDS7
0
6
DDS6
0
5
DDS5
0
4
DDS4
0
3
DDS3
0
2
DDS2
0
1
DDS1
0
Bit 0
DDS0
0
RESET:
Read or write anytime.
After reset, all general-purpose I/O are configured for input only.
0 = Configure the corresponding I/O pin for input only
1 = Configure the corresponding I/O pin for output
23-msi
MC68HC912DT128A Rev 2.0
245
MOTOROLA
Multiple Serial Interface
Multip le Se ria l Inte rfa c e
DDS2, DDS0 — Data Direction for Port S Bit 2 and Bit 0
If the SCI receiver is configured for two-wire SCI operation,
corresponding port S pins will be input regardless of the state of these
bits.
DDS3, DDS1 — Data Direction for Port S Bit 3 and Bit 1
If the SCI transmitter is configured for two-wire SCI operation,
corresponding port S pins will be output regardless of the state of
these bits.
DDS[6:4] — Data Direction for Port S Bits 6 through 4
If the SPI is enabled and expects the corresponding port S pin to be
an input, it will be an input regardless of the state of the DDRS bit. If
the SPI is enabled and expects the bit to be an output, it will be an
output ONLY if the DDRS bit is set.
DDS7 — Data Direction for Port S Bit 7
In SPI slave mode, DDRS7 has no meaning or effect; the PS7 pin is
dedicated as the SS input. In SPI master mode, DDRS7 determines
whether PS7 is an error detect input to the SPI or a general-purpose
or slave select output line.
NOTE: If mode fault error occurs bits 5, 6 and 7 are forced to zero.
24-msi
MC68HC912DT128A Rev 2.0
246
Multiple Serial Interface
MOTOROLA
Inte r-IC Bus
Inte r-IC Bus
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
IIC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
IIC System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
IIC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
IIC Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
IIC Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Introd uc tion
The Inter-IC Bus (IIC or I2C) 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 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 100kbps 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 400pF.
1-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
247
Inte r-IC Bus
IIC Fe a ture s
The IIC module has the following key features:
•
•
•
Compatible with I2C Bus standard
Multi-master operation
Software programmable for one of 64 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
Eight-bit general purpose I/O port
A block diagram of the IIC module is shown in Figure 37.
2--iicbus
MC68HC912DT128A Rev 2.0
248
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Features
ADDR & CONTROL
ADDR_DECODE
DATA
INTERRUPT
DATA_MUX
FREQ_REG
ADDR_REG
STATUS_REG
DATA_REG
CTRL_REG
In/Out
Data
Input
Sync
Shift
Start,
Stop &
Register
Arbitration
Control
Clock
Control
Address
Compare
SCL
SDA
Figure 37 IIC Block Diagram
3-iicbus
MC68HC912DT128A Rev 2.0
249
MOTOROLA
Inter-IC Bus
Inte r-IC Bus
IIC Syste m Config ura tion
The IIC 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.
IIC Protoc ol
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 38.
MSB
LSB
8
MSB
1
LSB
8
SCL
SDA
1
2
3
4
5
6
7
9
2
3
4
5
6
7
9
AD7 AD6 AD5 AD4 AD3 AD2 AD1 R/W
XXX
D7 D6 D5 D4 D3 D2 D1 D0
Start
Signal
Calling Address
Read/ Ack
Write
Data Byte
No Stop
Ack Signal
Bit
Bit
MSB
1
LSB
MSB
LSB
8
SCL
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
9
SDA
AD7 AD6 AD5 AD4 AD3 AD2 AD1 R/W
XX
AD7 AD6 AD5 AD4 AD3 AD2 AD1 R/W
Start
Signal
Calling Address
Read/ Ack
Write
Repeated
Start
Signal
New Calling Address
No Stop
Ack Signal
Bit
Read/
Write
Bit
Figure 38 IIC Transmission Signals
4-iicbus
MC68HC912DT128A Rev 2.0
250
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Protocol
START Sig na l
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 38, 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 wakes up all slaves.
Sla ve Ad d re ss
Tra nsm ission
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.
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 38).
Slave address - No two slaves in the system may have the same
address. If the IIC is master, it must not transmit an address that
is equal to its own slave address. The IIC cannot be master and
slave at the same time. If however arbitration is lost during an
address cycle the IIC will revert to slave mode and operate
correctly even if it is being addressed by another master.
Da ta Tra nsfe r
Once 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.
NOTE: All transfers that come after an address cycle are referred to as data
transfers, even if they carry sub-address information for the slave
device.
Each data byte is 8 bits long. Data may be changed only while SCL is
low and must be held stable while SCL is high as shown in Figure 38.
There is one clock pulse on SCL for each data bit, the MSB being
transferred first. Each data byte has to be followed by an acknowledge
5-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
251
Inte r-IC Bus
bit, which is signalled from the receiving device by pulling the SDA low
at the ninth clock. So one complete data byte transfer needs nine clock
pulses.
If the slave receiver does not acknowledge the master, the SDA line
must be left high by the slave. The master can then generate a stop
signal to abort the data transfer or a start signal (repeated start) to
commence a new calling.
If the master receiver does not acknowledge the slave transmitter after
a byte transmission, it means ’end of data’ to the slave, so the slave
releases the SDA line for the master to generate STOP or START signal.
STOP Sig na l
The master can terminate the communication by generating a STOP
signal to free the bus. However, the master may generate a START
signal followed by a calling command without generating a STOP signal
first. This is called repeated START. A STOP signal is defined as a
low-to-high transition of SDA while SCL at logical “1” (see Figure 38).
The master can generate a STOP even if the slave has generated an
acknowledge at which point the slave must release the bus.
Re p e a te d START
Sig na l
As shown in Figure 38, a repeated START signal is a START signal
generated without first generating a STOP signal to terminate the
communication. This is used by the master to communicate with another
slave or with the same slave in different mode (transmit/receive mode)
without releasing the bus.
Arb itra tion
Proc e d ure
IIC is a true multi-master bus that allows more than one master to be
connected on it. If two or more masters try to control the bus at the same
time, a clock synchronization procedure determines the bus clock, for
which the low period is equal to the longest clock low period and the high
is equal to the shortest one among the masters. The relative priority of
the contending masters is determined by a data arbitration procedure, a
bus master loses arbitration if it transmits logic “1” while another master
transmits logic “0”. The losing masters immediately switch over to slave
receive mode and stop driving SDA output. In this case the transition
6-iicbus
MC68HC912DT128A Rev 2.0
252
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Protocol
from master to slave mode does not generate a STOP condition.
Meanwhile, a status bit is set by hardware to indicate loss of arbitration.
Cloc k
Sync hroniza tion
Since wire-AND logic is performed on SCL line, a high-to-low transition
on SCL line affects all the devices connected on the bus. The devices
start counting their low period and once a device’s clock has gone low,
it holds the SCL line low until the clock high state is reached. However,
the change of low to high in this device clock may not change the state
of the SCL line if another device clock is still within its low period.
Therefore, synchronized clock SCL is held low by the device with the
longest low period. Devices with shorter low periods enter a high wait
state during this time (see Figure 39). When all devices concerned have
counted off their low period, the synchronized clock SCL line is released
and pulled high. There is then no difference between the device clocks
and the state of the SCL line and all the devices start counting their high
periods. The first device to complete its high period pulls the SCL line low
again.
Start Counting High Period
WAIT
SCL1
SCL2
SCL
Internal Counter Reset
Figure 39 IIC Clock Synchronization
Ha nd sha king
The clock synchronization mechanism can be used as a handshake in
data transfer. Slave devices may hold the SCL low after completion of
7-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
253
Inte r-IC Bus
one byte transfer (9 bits). In such case, it halts the bus clock and forces
the master clock into wait states until the slave releases the SCL line.
Cloc k Stre tc hing
The clock synchronization mechanism can be used by slaves to slow
down the bit rate of a transfer. After the master has driven SCL low the
slave can drive SCL low for the required period and then release it. If the
slave SCL low period is greater than the master SCL low period then the
resulting SCL bus signal low period is stretched.
IIC Re g iste r De sc rip tions
.
IBAD — IIC Bus Address Register
$00E0
Bit 7
ADR7
0
6
ADR6
0
5
ADR5
0
4
ADR4
0
3
ADR3
0
2
ADR2
0
1
ADR1
0
Bit 0
0
0
RESET:
Read and write anytime
This register contains the address the IIC will respond to when
addressed as a slave; note that it is not the address sent on the bus
during the address transfer
ADR7–ADR1 — Slave Address
Bit 1 to bit 7 contain the specific slave address to be used by the IIC
module.
The default mode of IIC is slave mode for an address match on the
bus.
IBFD — IIC Bus Frequency Divider Register
$00E1
Bit 7
6
0
0
5
IBC5
0
4
IBC4
0
3
IBC3
0
2
IBC2
0
1
IBC1
0
Bit 0
IBC0
0
0
0
RESET:
Read and write anytime
8-iicbus
MC68HC912DT128A Rev 2.0
254
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Register Descriptions
IBC5–IBC0 — IIC Bus Clock Rate 5–0
This field is used to prescale the clock for bit rate selection. The bit
clock generator is implemented as a 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 37.
NOTE: At 8 MHz system bus frequency, the IIC bus frequency will slow down by
as much as 5%. However, the communications rate of the IIC system will
be automatically adjusted to a slower rate.
Table 37 IIC Tap and Prescale Values
IBC2-0
(bin)
SCL Tap SDA Tap
IBC5-3
(bin)
scl2tap
(clocks)
tap2tap
(clocks)
(clocks)
(clocks)
000
001
010
011
100
101
110
111
5
6
1
1
2
2
3
3
4
4
000
001
010
011
100
101
110
111
4
4
1
2
7
6
4
8
6
8
9
14
30
62
126
16
32
64
128
10
12
15
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 37, all subsequent tap points are separated by 2IBC5-3 as
shown in the tap2tap column in Table 37. 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.
The serial bit clock frequency is equal to the CPU clock frequency
divided by the divider shown in Table 3. The equation used to
generate the divider values from the IBFD bits is:
SCL Divider = 2 x ( scl2tap + [ ( SCL_Tap -1 ) x tap2tap ] + 2 )
9-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
255
Inte r-IC Bus
The SDA hold delay is equal to the CPU clock period multiplied by the
SDA Hold value shown in Figure 3. The equation used to generate the
SDA Hold value from the IBFD bits is:
SDA Hold = scl2tap + [ ( SDA_Tap - 1 ) x tap2tap ] + 3
Table 3 IIC Divider and SDA Hold values
IBC5-0
(hex)
SCL Divider SDA Hold
IBC5-0
(hex)
SCL Divider SDA Hold
(clocks)
(clocks)
(clocks)
(clocks)
00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
20
7
7
20
21
22
23
24
25
26
27
28
29
2A
2B
2C
2D
2E
2F
30
31
32
33
34
35
36
160
17
22
192
17
24
8
224
33
26
8
256
33
28
9
288
49
30
9
320
49
34
10
10
7
384
65
40
480
65
28
320
33
32
7
384
33
36
9
448
65
40
9
512
65
44
11
11
13
13
9
576
97
48
640
97
56
768
129
129
65
68
960
48
640
56
9
768
65
12
13
14
15
16
64
13
13
17
17
21
896
129
129
193
193
257
72
1024
1152
1280
1536
80
88
104
10-iicbus
MC68HC912DT128A Rev 2.0
256
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Register Descriptions
Table 3 IIC Divider and SDA Hold values
IBC5-0
(hex)
SCL Divider SDA Hold
IBC5-0
(hex)
SCL Divider SDA Hold
(clocks)
128
80
(clocks)
(clocks)
1920
1280
1536
1792
2048
2304
2560
3072
3840
(clocks)
17
18
19
1A
1B
1C
1D
1E
1F
21
9
37
38
39
3A
3B
3C
3D
3E
3F
257
129
96
9
129
112
17
17
25
25
33
33
257
128
144
160
192
240
257
385
385
513
513
IBCR — IIC Bus Control Register
$00E2
Bit 7
IBEN
0
6
IBIE
0
5
4
3
TXAK
0
2
1
0
0
Bit 0
MS/SL
0
Tx/Rx
0
RSTA
0
IBSWAI
0
RESET:
Read and write anytime
IBEN — IIC Bus Enable
This bit controls the software reset of the entire IIC module.
0 = The module is reset and disabled. This is the power-on reset
situation. When low the IIC system is held in reset but registers
can still be accessed.
1 = The IIC system is enabled. This bit must be set before any other
IBCR bits have any effect.
If the IIC 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 module losing arbitration, after which bus operation
would return to normal.
11-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
257
Inte r-IC Bus
NOTE: To prevent glitches from appearing on the SDA & SCL lines during reset
of the IIC module, set PORTIB bit 6 & 7 to 1 before clearing the IBEN bit.
IBIE — IIC Bus Interrupt Enable
0 = Interrupts from the IIC module are disabled. Note that this does
not clear any currently pending interrupt condition.
1 = Interrupts from the IIC module are enabled. An IIC interrupt
occurs provided the IBIF bit in the status register is also set.
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.
MS/SL is cleared without generating a STOP signal when the master
loses arbitration.
0 = Slave Mode
1 = Master Mode
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
TXAK — Transmit Acknowledge enable
This bit specifies the value driven onto SDA during acknowledge
cycles for both master and slave receivers. Note that values written to
this bit are only used when the IIC 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)
12-iicbus
MC68HC912DT128A Rev 2.0
258
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Register Descriptions
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
IBSWAI — IIC Stop in WAIT mode
0 = IIC module operates normally
1 = Halt clock generation of IIC module in WAIT mode
IBSR — IIC Bus Status Register
$00E3
Bit 7
TCF
1
6
IAAS
0
5
IBB
0
4
IBAL
0
3
0
0
2
SRW
0
1
IBIF
0
Bit 0
RXAK
0
RESET:
This status register is read-only with exception of bit 1 (IBIF) and bit 4
(IBAL), which are software clearable
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.
0 = Transfer in progress
1 = Transfer complete
IAAS — Addressed as a slave bit
When its own specific address (IIC Bus Address Register) is matched
with the calling address, 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 IIC Bus Control
Register clears this bit.
0 = Not addressed
1 = Addressed as a slave
IBB — IIC Bus busy bit
This bit indicates the status of the bus. When a START signal is
detected, the IBB is set. If a STOP signal is detected, it is cleared.
0 = Bus is idle
1 = Bus is busy
13-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
259
Inte r-IC Bus
NOTE: If, after trying to generate a START signal and neither the IBB nor IBAL
bits are set after several cycles, the IIC should be disabled and
re-enabled with IBEN bit.
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 as low when the master drives a high during an
address or data transmit cycle.
2. SDA sampled as a 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.
NOTE: If, after trying to generate a START signal and neither the IBB nor IBAL
bits are set after several cycles, the IIC should be disabled and
re-enabled with IBEN bit.
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.
CAUTION: This bit is only valid when the IIC 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
IBIF — IIC Bus Interrupt Flag
The IBIF bit is set when an interrupt is pending, which will cause a
processor interrupt request provided IBIE is set. IBIF is set when one
of the following events occurs:
14-iicbus
MC68HC912DT128A Rev 2.0
260
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Register Descriptions
1. Complete one byte transfer (set at the falling edge of the 9th
clock).
2. Receive a calling address that matches its own specific address in
slave receive mode.
3. Arbitration lost.
This bit must be cleared by software, writing a one to it, in the interrupt
routine.
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
.
IBDR — IIC Bus Data I/O Register
$00E4
Bit 7
D7
0
6
D6
0
5
D5
0
4
D4
0
3
D3
0
2
D2
0
1
D1
0
Bit 0
D0
0
High
RESET:
Read and write anytime
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: 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 comprise
of the calling address (in position D7-D1) concatenated with the required
R/W bit (in position D0).
15-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
261
Inte r-IC Bus
IBPURD — Pull-Up and Reduced Drive for Port IB
$00E5
Bit 7
6
0
0
5
0
0
4
RDPIB
0
3
0
0
2
0
0
1
0
0
Bit 0
PUPIB
0
0
0
RESET:
Read and write anytime
RDPIB - Reduced Drive of Port IB
0 = All port IB output pins have full drive enabled.
1 = All port IB output pins have reduced drive capability.
PUPIB - Pull-Up Port IB Enable
0 = Port IB pull-ups are disabled.
1 = Enable pull-up devices for port IB input pins [7:6]. Pull-ups for
port IB input pins [5:0] are always enabled.
PORTIB — Port Data IB Register
$00E6
Bit 7
PIB7
SCL
-
6
PIB6
SDA
-
5
4
3
2
1
Bit 0
PIB5
PIB4
PIB3
PIB2
PIB1
PIB0
IIC
-
-
-
-
-
-
-
-
-
-
-
-
RESET:
Read and write anytime.
IIC functions SCL and SDA share port IB pins 7 and 6 and take
precedence over the general-purpose port when IIC is enabled. The
SCL and SDA output buffers behave as open-drain outputs.
When port is configured as input, a read will return the pin level. Port bits
5 through 0 have internal pull ups when configured as inputs so they will
read ones.
When configured as output, a read will return the latched output data.
Port bits 5 through 0 will read the last value written. A write will drive
associated pins only if configured for output and IIC is not enabled.
Port bits 5 through 0 do not have available external pins for
MC68HC912DT128A.
16-iicbus
MC68HC912DT128A Rev 2.0
262
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Programming Examples
DDRIB — Data Direction for Port IB Register
$00E7
Bit 7
DDRIB7
0
6
DDRIB6
0
5
DDRIB5
0
4
DDRIB4
0
3
DDRIB3
0
2
DDRIB2
0
1
DDRIB1
0
Bit 0
DDRIB0
0
RESET:
Read and write anytime
DDRIB[7:2]— Port IB [7:2] Data direction
Each bit determines the primary direction for each pin configured as
general-purpose I/O.
0 = Associated pin is a high-impedance input.
1 = Associated pin is an output.
DDRIB[5:0] — These bits served as memory locations since there are
no corresponding external port pins for MC68HC912DT128A.
IIC Prog ra m m ing Exa m p le s
Initia liza tion
Se q ue nc e
Reset will put the IIC Bus Control Register to its default status. Before
the interface can be used to transfer serial data, an initialization
procedure must be carried out, as follows:
1. Update the Frequency Divider Register (IBFD) and select the
required division ratio to obtain SCL frequency from system clock.
2. Update the IIC Bus Address Register (IBAD) to define its slave
address.
3. Set the IBEN bit of the IIC Bus Control Register (IBCR) to enable
the IIC interface system.
4. Modify the bits of the IIC Bus Control Register (IBCR) to select
Master/Slave mode, Transmit/Receive mode and interrupt enable
or not.
Ge ne ra tion of
START
After completion of the initialization procedure, serial data can be
transmitted by selecting the 'master transmitter' mode. If the device is
17-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
263
Inte r-IC Bus
connected to a multi-master bus system, the state of the IIC Bus Busy
bit (IBB) must be tested to check whether the serial bus is free.
If the bus is free (IBB=0), the start condition and the first byte (the slave
address) can be sent. The data written to the data register comprises the
slave calling address and the LSB set to indicate the direction of transfer
required from the slave.
The bus free time (i.e., the time between a STOP condition and the
following START condition) is built into the hardware that generates the
START cycle. Depending on the relative frequencies of the system clock
and the SCL period it may be necessary to wait until the IIC is busy after
writing the calling address to the IBDR before proceeding with the
following instructions. This is illustrated in the following example.
An example of a program which generates the START signal and
transmits the first byte of data (slave address) is shown below:
CHFLAG
BRSET
BSET
IBSR,#$20,*
IBCR,#$30
;WAIT FOR IBB FLAG TO CLEAR
;SET TRANSMIT AND MASTER MODE
;i.e. GENERATE START CONDITION
;TRANSMIT THE CALLING
TXSTART
MOVB
CALLING,IBDR
IBSR,#$20,*
;ADDRESS, D0=R/W
IBFREE
BRCLR
;WAIT FOR IBB FLAG TO SET
Post-Tra nsfe r
Softwa re
Re sp onse
Transmission or reception of a byte will set the data transferring bit
(TCF) to 1, which indicates one byte communication is finished. The IIC
Bus interrupt bit (IBIF) is set also; an interrupt will be generated if the
interrupt function is enabled during initialization by setting the IBIE bit.
Software must clear the IBIF bit in the interrupt routine first. The TCF bit
will be cleared by reading from the IIC Bus Data I/O Register (IBDR) in
receive mode or writing to IBDR in transmit mode.
Software may service the IIC I/O in the main program by monitoring the
IBIF bit if the interrupt function is disabled. Note that polling should
monitor the IBIF bit rather than the TCF bit since their operation is
different when arbitration is lost.
Note that when an interrupt occurs at the end of the address cycle the
master will always be in transmit mode, i.e. the address is transmitted. If
18-iicbus
MC68HC912DT128A Rev 2.0
264
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Programming Examples
master receive mode is required, indicated by R/W bit in IBDR, then the
Tx/Rx bit should be toggled at this stage.
During slave mode address cycles (IAAS=1) the SRW bit in the status
register is read to determine the direction of the subsequent transfer and
the Tx/Rx bit is programmed accordingly. For slave mode data cycles
(IAAS=0) the SRW bit is not valid, the Tx/Rx bit in the control register
should be read to determine the direction of the current transfer.
The following is an example of a software response by a ’master
transmitter’ in the interrupt routine (see Figure 40).
ISR
BCLR
IBSR,#$02
;CLEAR THE IBIF FLAG
BRCLR
BRCLR
BRSET
IBCR,#$20,SLAVE
;BRANCH IF IN SLAVE MODE
IBCR,#$10,RECEIVE ;BRANCH IF IN RECEIVE MODE
IBSR,#$01,END
DATABUF,IBDR
;IF NO ACK, END OF TRANSMISSION
;TRANSMIT NEXT BYTE OF DATA
TRANSMIT MOVB
Ge ne ra tion of
STOP
A data transfer ends with a STOP signal generated by the ’master’
device. A master transmitter can simply generate a STOP signal after all
the data has been transmitted. The following is an example showing how
a stop condition is generated by a master transmitter.
MASTX
TST
TXCNT
;GET VALUE FROM THE
;TRANSMITING COUNTER
;END IF NO MORE DATA
;END IF NO ACK
BEQ
END
BRSET
MOVB
DEC
IBSR,#$01,END
DATABUF,IBDR
TXCNT
;TRANSMIT NEXT BYTE OF DATA
;DECREASE THE TXCNT
;EXIT
BRA
EMASTX
END
BCLR
RTI
IBCR,#$20
;GENERATE A STOP CONDITION
;RETURN FROM INTERRUPT
EMASTX
If a master receiver wants to terminate a data transfer, it must inform the
slave transmitter by not acknowledging the last byte of data which can
be done by setting the transmit acknowledge bit (TXAK) before reading
the 2nd last byte of data. Before reading the last byte of data, a STOP
19-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
265
Inte r-IC Bus
signal must be generated first. The following is an example showing how
a STOP signal is generated by a master receiver.
MASR
DEC
RXCNT
;DECREASE THE RXCNT
;LAST BYTE TO BE READ
;CHECK SECOND LAST BYTE
;TO BE READ
BEQ
ENMASR
RXCNT,D1
D1
MOVB
DEC
BNE
NXMAR
;NOT LAST OR SECOND LAST
;SECOND LAST, DISABLE ACK
;TRANSMITTING
LAMAR
BSET
IBCR,#$08
BRA
NXMAR
ENMASR
NXMAR
BCLR
MOVB
RTI
IBCR,#$20
;LAST ONE, GENERATE ‘STOP’ SIGNAL
IBDR,RXBUF ;READ DATA AND STORE
Ge ne ra tion of
Re p e a te d START
At the end of data transfer, if the master still wants to communicate on
the bus, it can generate another START signal followed by another slave
address without first generating a STOP signal. A program example is
as shown.
RESTART
BSET
MOVB
IBCR,#$04
ANOTHER START (RESTART)
;TRANSMIT THE CALLING ADDRESS
;D0=R/W
CALLING,IBDR
Sla ve Mod e
In the slave interrupt service routine, the module addressed as slave bit
(IAAS) should be tested to check if a calling of its own address has just
been received (see Figure 40). If IAAS is set, software should set the
transmit/receive mode select bit (Tx/Rx bit of IBCR) according to the R/
W command bit (SRW). Writing to the IBCR clears the IAAS
automatically. Note that the only time IAAS is read as set is from the
interrupt at the end of the address cycle where an address match
occurred, interrupts resulting from subsequent data transfers will have
IAAS cleared. A data transfer may now be initiated by writing information
to IBDR, for slave transmits, or dummy reading from IBDR, in slave
receive mode. The slave will drive SCL low in-between byte transfers,
SCL is released when the IBDR is accessed in the required mode.
In slave transmitter routine, the received acknowledge bit (RXAK) must
be tested before transmitting the next byte of data. Setting RXAK means
20-iicbus
MC68HC912DT128A Rev 2.0
266
Inter-IC Bus
MOTOROLA
Inter-IC Bus
IIC Programming Examples
an ’end of data’ signal from the master receiver, after which it must be
switched from transmitter mode to receiver mode by software. A dummy
read then releases the SCL line so that the master can generate a STOP
signal.
Arb itra tion Lost
If several masters try to engage the bus simultaneously, only one master
wins and the others lose arbitration. The devices which lost arbitration
are immediately switched to slave receive mode by the hardware. Their
data output to the SDA line is stopped, but SCL is still generated until the
end of the byte during which arbitration was lost. An interrupt occurs at
the falling edge of the ninth clock of this transfer with IBAL=1 and MS/
SL=0. If one master attempts to start transmission while the bus is being
engaged by another master, the hardware will inhibit the transmission;
switch the MS/SL bit from 1 to 0 without generating STOP condition;
generate an interrupt to CPU and set the IBAL to indicate that the
attempt to engage the bus is failed. When considering these cases, the
slave service routine should test the IBAL first and the software should
clear the IBAL bit if it is set.
21-iicbus
MC68HC912DT128A Rev 2.0
MOTOROLA
Inter-IC Bus
267
Inte r-IC Bus
Clear
IBIF
Master
Mode
?
Y
N
Arbitration
Lost
?
Y
TX
RX
Tx/Rx
?
N
Last Byte
Clear IBAL
Transmitted
?
Y
N
N
Last
Byte To Be Read
?
N
Y
RXAK=0
?
IAAS=1
?
IAAS=1
?
Y
N
Y
Y
N
Data Transfer
Address Transfer
Y
End Of
Addr Cycle
(Master Rx)
?
2nd Last
Byte To Be Read
?
(Read)
Y
Y
SRW=1
?
RX
TX/RX
?
TX
(Write)
N
N
N
Y
ACK From
Receiver
?
Write Next
Byte To IBDR
Generate
Stop Signal
Set TX
Mode
Set TXAK =1
N
Read Data
From IBDR
And Store
Tx Next
Byte
Write Data
To IBDR
Switch To
Rx Mode
Set RX
Mode
Switch To
Rx Mode
Read Data
From IBDR
And Store
Dummy Read
From IBDR
Generate
Stop Signal
Dummy Read
From IBDR
Dummy Read
From IBDR
RTI
Figure 40 Flow-Chart of Typical IIC Interrupt Routine
22-iicbus
MC68HC912DT128A Rev 2.0
268
Inter-IC Bus
MOTOROLA
MSCAN Controlle r
MSCAN Controlle r
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
External Pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Identifier Acceptance Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Protocol Violation Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Low Power Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Timer Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Clock System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Programmer’s Model of Message Storage . . . . . . . . . . . . . . . . . . . . 289
Programmer’s Model of Control Registers . . . . . . . . . . . . . . . . . . . . 294
Introd uc tion
The MC68HC912DT128A has three identical msCAN12 modules,
identified as CAN0, CAN1 and CAN2. The MC68HC912DG128A has
two: CAN0 and CAN1. The information to follow describes one msCAN
unless specifically noted and register locations specifically relate to
CAN0. CAN1 registers are located 512 bytes from CAN0, and on the
MC68HC912DT128A, CAN2 registers are located 256 bytes from
CAN0.
The msCAN12 is the specific implementation of the Motorola scalable
CAN (msCAN) concept targeted for the Motorola M68HC12
microcontroller family.
1-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
269
MSCAN Controlle r
The module is a communication controller implementing the CAN 2.0 A/
B protocol as defined in the BOSCH specification dated September
1991.
The CAN protocol was primarily, but not only, designed to be used as a
vehicle serial data bus, meeting the specific requirements of this field:
real-time processing, reliable operation in the EMI environment of a
vehicle, cost-effectiveness and required bandwidth.
msCAN12 utilizes an advanced buffer arrangement resulting in a
predictable real-time behavior and simplifies the application software.
Exte rna l Pins
The msCAN12 uses 2 external pins, 1 input (RxCAN) and 1 output
(TxCAN). The TxCAN output pin represents the logic level on the CAN:
0 is for a dominant state, and 1 is for a recessive state.
RxCAN is on bit 0 of Port CAN, TxCAN is on bit 1. The remaining six pins
of Port CAN are controlled by registers in the msCAN12 address space
(see msCAN12 Port CAN Control Register (PCTLCAN) and msCAN12
Port CAN Data Direction Register (DDRCAN)).
A typical CAN system with msCAN12 is shown in Figure 41 below.
Each CAN station is connected physically to the CAN bus lines through
a transceiver chip. The transceiver is capable of driving the large current
needed for the CAN and has current protection, against defected CAN
or defected stations.
2--mscan12
MC68HC912DT128A Rev 2.0
270
MSCAN Controller
MOTOROLA
MSCAN Controller
Message Storage
CAN station 1
CAN system
CAN station 2
.....
CAN station n
msCAN12
Controller
RxCAN
TxCAN
Transceiver
CAN
Figure 41 The CAN System
Me ssa g e Stora g e
msCAN12 facilitates a sophisticated message storage system which
addresses the requirements of a broad range of network applications.
Ba c kg round
Modern application layer software is built upon two fundamental
assumptions:
1. Any CAN node is able to send out a stream of scheduled
messages without releasing the bus between two messages.
Such nodes will arbitrate for the bus right after sending the
previous message and will only release the bus in case of lost
arbitration.
2. The internal message queue within any CAN node is organized
such that if more than one message is ready to be sent, the
highest priority message will be sent out first.
Above behavior can not be achieved with a single transmit buffer. That
buffer must be reloaded right after the previous message has been sent.
3-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
271
MSCAN Controlle r
This loading process lasts a definite amount of time and has to be
completed within the inter-frame sequence (IFS) in order 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 would de-couple the re-loading of the transmit
buffers from the actual message sending and as such reduces the
reactiveness requirements on the CPU. Problems may arise if the
sending of a message would be finished just while the CPU re-loads the
second buffer, no buffer would then be ready for transmission and the
bus would be released.
At least three transmit buffers are required to meet the first of above
requirements under all circumstances. The msCAN12 has three transmit
buffers.
The second requirement calls for some sort of internal prioritizing which
the msCAN12 implements with the local priority concept described
below.
Re c e ive Struc ture s
The received messages are stored in a two stage input FIFO. The two
message buffers are mapped using a ping-pong arrangement into a
single memory area (see Figure 42). While the background receive
buffer (RxBG) is exclusively associated to the msCAN12, the foreground
receive buffer (RxFG) is addressed by the CPU12. This scheme
simplifies the handler software as only one address area is applicable for
the receive process.
Both buffers have a size of 13 bytes to store the CAN control bits, the
identifier (standard or extended) and the data contents (for details see
Programmer’s Model of Message Storage).
The receiver full flag (RXF) in the msCAN12 receiver flag register
(CRFLG) (see msCAN12 Receiver Flag Register (CRFLG)) signals the
status of the foreground receive buffer. When the buffer contains a
correctly received message with matching identifier this flag is set.
After the msCAN12 successfully received a message into the
background buffer and if the message passes the filter, it copies the
4-mscan12
MC68HC912DT128A Rev 2.0
272
MSCAN Controller
MOTOROLA
MSCAN Controller
Message Storage
content of RxBG into RxFG1, sets the RXF flag, and emits a receive
interrupt to the CPU2. A new message (which may follow immediately
after the IFS field of the CAN frame) will be received into RxBG. The
over-writing of the background buffer is independent of the identifier filter
function.
The user’s receive handler has to read the received message from
RxFG and to reset the RXF flag in order to acknowledge the interrupt
and to release the foreground buffer.
An overrun condition occurs when both the foreground and the
background receive message buffers are filled with correctly received
messages with accepted identifiers and a further correctly received
message with accepted identifier is received from the bus. The latter
message will be discarded and an error interrupt with overrun indication
will occur if enabled. As long as both buffers remain filled, the msCAN12
is able to transmit messages but it will discard all incoming messages.
NOTE: The msCAN12 will receive its own messages into the background
receive buffer RxBG but will not overwrite RxFG and will not emit a
receive interrupt nor will it acknowledge (ACK) its own messages on the
CAN bus. The exception to this rule is that when in loop-back mode
msCAN12 will treat its own messages exactly like all other incoming
messages.
1. Only if the RXF flag is not set.
2. The receive interrupt will occur only if not masked. A polling scheme can be applied on RXF
also.
5-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
273
MSCAN Controlle r
msCAN12
CPU bus
RxBG
RXF
RxFG
TXE
Tx0
Tx1
Tx2
PRIO
TXE
PRIO
TXE
PRIO
Figure 42 User Model for Message Buffer Organization
Tra nsm it Struc ture s
The msCAN12 has a triple transmit buffer scheme in order to allow
multiple messages to be set up in advance and to achieve an optimized
real-time performance. The three buffers are arranged as shown in
Figure 42.
All three buffers have a 13 byte data structure similar to the outline of the
receive buffers (see Programmer’s Model of Message Storage). An
additional transmit buffer priority register (TBPR) contains an 8-bit so
called local priority field (PRIO) (see Transmit Buffer Priority Registers
(TBPR)).
6-mscan12
MC68HC912DT128A Rev 2.0
274
MSCAN Controller
MOTOROLA
MSCAN Controller
Message Storage
In order to transmit a message, the CPU12 has to identify an available
transmit buffer which is indicated by a set transmit buffer empty (TXE)
flag in the msCAN12 transmitter flag register (CTFLG) (see msCAN12
Transmitter Flag Register (CTFLG)).
The CPU12 then stores the identifier, the control bits and the data
content into one of the transmit buffers. Finally, the buffer has to be
flagged as being ready for transmission by clearing the TXE flag.
The msCAN12 will then schedule the message for transmission and will
signal the successful transmission of the buffer by setting the TXE flag.
A transmit interrupt will be emitted1 when TXE is set and this can be
used to drive the application software to re-load the buffer.
In case more than one buffer is scheduled for transmission when the
CAN bus becomes available for arbitration, the msCAN12 uses the local
priority setting of the three buffers for prioritizing. For this purpose every
transmit buffer has an 8-bit local priority field (PRIO). The application
software sets 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 emitted from this node. The lowest binary value of the
PRIO field is defined to be the highest priority.
The internal scheduling process takes places whenever the msCAN12
arbitrates for the 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 being set up
in one of the three transmit buffers. As messages that are already under
transmission can not be aborted, the user has to request the abort by
setting the corresponding abort request flag (ABTRQ) in the
transmission control register (CTCR). The msCAN12 grants the request,
if possible, by setting the corresponding abort request acknowledge
(ABTAK) and the TXE flag in order to release the buffer and by emitting
a transmit interrupt. The transmit interrupt handler software can tell from
1. The transmit interrupt will occur only if not masked. A polling scheme can be applied on TXE
also.
7-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
275
MSCAN Controlle r
the setting of the ABTAK flag whether the message was actually aborted
(ABTAK=1) or sent in the meantime (ABTAK=0).
Id e ntifie r Ac c e p ta nc e Filte r
A very flexible programmable generic identifier acceptance filter has
been introduced in order 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 identifier and to the following bits of the CAN frame:
RTR, IDE, SRR. This mode implements a two filters for a full
length CAN 2.0B compliant extended identifier. Figure 43 shows
how the first 32-bit filter bank (CIDAR0–3, CIDMR0–3) produces a
filter 0 hit. Similarly, the second filter bank (CIDAR4–7,
CIDMR4–7) produces a filter 1 hit.
Four identifier acceptance filters, each to be applied to a) the 11
bits of the identifier and the RTR bit of CAN 2.0A messages or b)
the 14 most significant bits of the identifier of CAN 2.0B
messages. Figure 44 shows how the first 32-bit filter bank
(CIDAR0–3, CIDMR0–3) produces filter 0 and 1 hits. Similarly, the
second filter bank (CIDAR4–7, CIDMR4–7) 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 bit of a CAN 2.0A compliant standard identifier
or of a CAN 2.0B compliant extended identifier. Figure 45 shows
how the first 32-bit filter bank (CIDAR0–3, CIDMR0–3) produces
filter 0 to 3 hits. Similarly, the second filter bank (CIDAR4–7,
CIDMR4–7) produces filter 4 to 7 hits.
Closed filter. No CAN message will be copied into the foreground
buffer RxFG, and the RXF flag will never be set.
8-mscan12
MC68HC912DT128A Rev 2.0
276
MSCAN Controller
MOTOROLA
MSCAN Controller
Identifier Acceptance Filter
ID28 IDR0 ID21 ID20 IDR1 ID15 ID14 IDR2
ID10 IDR0 ID3 ID2 IDR1 IDE
ID7 ID6 IDR3 RTR
AM7 CIDMRO AM0 AM7 CIDMR1 AM0 AM7CIDMR2 AM0 AM7CIDMR3 AM0
AC7 CIDARO AC0 AC7 CIDAR1 AC0 AC7 CIDAR2 AC0 AC7 CIDAR3 AC0
ID accepted (Filter 0 hit)
Figure 43 32-bit Maskable Identifier Acceptance Filters
ID28 IDR0 ID21 ID20 IDR1 ID15 ID14 IDR2
ID10 IDR0 ID3 ID2 IDR1 IDE
ID7 ID6 IDR3 RTR
AM7 CIDMRO AM0 AM7 CIDMR1 AM0
AC7 CIDARO AC0 AC7 CIDAR1 AC0
ID accepted (Filter 0 hit)
AM7 CIDMR2 AM0 AM7 CIDMR3 AM0
AC7 CIDAR2 AC0 AC7 CIDAR3 AC0
ID accepted (Filter 1 hit)
Figure 44 16-bit Maskable Acceptance Filters
9-mscan12
MC68HC912DT128A Rev 2.0
277
MOTOROLA
MSCAN Controller
MSCAN Controlle r
ID28 IDR0 ID21 ID20 IDR1 ID15 ID14 IDR2
ID10 IDR0 ID3 ID2 IDR1 IDE
ID7 ID6 IDR3 RTR
AM7 CIDMRO AM0
AC7 CIDARO AC0
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
Figure 45 8-bit Maskable Acceptance Filters
The identifier acceptance registers (CIDAR0–7) define the acceptable
patterns of the standard or extended identifier (ID10–ID0 or ID28–ID0).
Any of these bits can be marked don’t care in the identifier mask
registers (CIDMR0–7).
A filter hit is indicated to the application software by a set RXF (receive
buffer full flag, see msCAN12 Receiver Flag Register (CRFLG)) and
10-mscan12
MC68HC912DT128A Rev 2.0
278
MSCAN Controller
MOTOROLA
MSCAN Controller
Interrupts
three bits in the identifier acceptance control register (see msCAN12
Identifier Acceptance Control Register (CIDAC)). These identifier hit
flags (IDHIT2–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. In case that more than one hit occurs
(two or more filters match) the lower hit has priority.
A hit will also cause a receiver interrupt if enabled.
Inte rrup ts
The msCAN12 supports four interrupt vectors mapped onto eleven
different interrupt sources, any of which can be individually masked (for
details see msCAN12 Receiver Flag Register (CRFLG) to msCAN12
Transmitter Control Register (CTCR)):
•
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 TXE flags of the empty message buffers are
set.
•
Receive interrupt: A message has been successfully received and
loaded into the foreground receive buffer. This interrupt will be
emitted immediately after receiving the EOF symbol. The RXF flag
is set.
•
•
Wake-up interrupt: An activity on the CAN bus occurred during
msCAN12 internal SLEEP mode.
Error interrupt: An overrun, error or warning condition occurred.
The receiver flag register (CRFLG) will indicate one of the
following conditions:
– Overrun: an overrun condition as described in Receive
Structures has occurred.
– Receiver warning: the receive error counter has reached the
CPU warning limit of 96.
– Transmitter warning: the transmit error counter has reached
the CPU warning limit of 96.
11-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
279
MSCAN Controlle r
– Receiver error passive: the receive error counter has
exceeded the error passive limit of 127 and msCAN12 has
gone to error passive state.
– Transmitter error passive: the transmit error counter has
exceeded the error passive limit of 127 and msCAN12 has
gone to error passive state.
– Bus off: the transmit error counter has exceeded 255 and
msCAN12 has gone to BUSOFF state.
Inte rrup t
Ac knowle d g e
Interrupts are directly associated with one or more status flags in either
the msCAN12 receiver flag register (CRFLG) or the msCAN12
transmitter flag register (CTFLG). Interrupts are pending as long as one
of the corresponding flags is set. The flags in above registers must be
reset within the interrupt handler in order to handshake the interrupt. The
flags are reset through writing a 1 to the corresponding bit position. A
flag can not be cleared if the respective condition still prevails.
NOTE: Bit manipulation instructions (BSET) shall not be used to clear interrupt
flags.
Inte rrup t Ve c tors
The msCAN12 supports four interrupt vectors as shown in Table 38. The
vector addresses and the relative interrupt priority are dependent on the
chip integration and to be defined.
12-mscan12
MC68HC912DT128A Rev 2.0
280
MSCAN Controller
MOTOROLA
MSCAN Controller
Protocol Violation Protection
Table 38 msCAN12 Interrupt Vectors
Function
Source
WUPIF
RWRNIF
TWRNIF
RERRIF
TERRIF
BOFFIF
OVRIF
RXF
Local Mask
WUPIE
Global Mask
Wake-Up
RWRNIE
TWRNIE
RERRIE
TERRIE
BOFFIE
OVRIE
Error
Interrupts
I Bit
Receive
Transmit
RXFIE
TXE0
TXEIE0
TXEIE1
TXEIE2
TXE1
TXE2
Protoc ol Viola tion Prote c tion
The msCAN12 will protect 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 msCAN12 can
not be modified while the msCAN12 is on-line. The SFTRES bit in
CMCR0 (see msCAN12 Module Control Register (CMCR0))
serves as a lock to protect the following registers:
– msCAN12 module control register 1 (CMCR1)
– msCAN12 bus timing register 0 and 1 (CBTR0, CBTR1)
– msCAN12 identifier acceptance control register (CIDAC)
– msCAN12 identifier acceptance registers (CIDAR0–7)
– msCAN12 identifier mask registers (CIDMR0–7)
•
The TxCAN pin is forced to recessive when the msCAN12 is in any
of the low power modes.
13-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
281
MSCAN Controlle r
Low Powe r Mod e s
The msCAN12 has three modes with reduced power consumption
compared to normal mode. In SLEEP and SOFT_RESET mode, power
consumption is reduced by stopping all clocks except those to access
the registers. In POWER_DOWN mode, all clocks are stopped and no
power is consumed.
The WAI and STOP instructions put the MCU in low power consumption
stand-by modes. Table 39 summarizes the combinations of msCAN12
and CPU modes. A particular combination of modes is entered for the
given settings of the bits CSWAI, SLPAK, and SFTRES. For all modes,
an msCAN wake-up interrupt can occur only if SLPAK=WUPIE=1. While
the CPU is in Wait Mode, the msCAN12 can be operated in Normal
Mode and emit interrupts (registers can be accessed via background
debug mode).
Table 39 msCAN12 vs. CPU operating modes
CPU Mode
msCAN Mode
STOP
WAIT
RUN
CSWAI = X(1)
POWER_DOWN SLPAK = X
SFTRES = X
CSWAI = 1
SLPAK = X
SFTRES = X
CSWAI = 0
SLPAK = 1
SFTRES = 0
CSWAI = X
SLPAK = 1
SFTRES = 0
SLEEP
CSWAI = 0
SLPAK = 0
SFTRES = 1
CSWAI = X
SLPAK = 0
SFTRES = 1
SOFT_RESET
CSWAI = 0
SLPAK = 0
SFTRES = 0
CSWAI = X
SLPAK = 0
SFTRES = 0
Normal
1. X means don’t care.
m sCAN12 SLEEP
Mod e
The CPU can request the msCAN12 to enter this low-power mode by
asserting the SLPRQ bit in the module configuration register (see
Figure 46). The time when the msCAN12 will then enter SLEEP mode
depends on its current activity:
14-mscan12
MC68HC912DT128A Rev 2.0
282
MSCAN Controller
MOTOROLA
MSCAN Controller
Low Power Modes
•
•
•
if it is transmitting, it will continue to transmit until there is no more
message to be transmitted, and then go into SLEEP mode
if it receiving, it will wait for the end of this message and then go
into SLEEP mode
if it is neither transmitting nor receiving, it will immediately go into
SLEEP mode
The application software must avoid setting up a transmission (by
clearing one or more TXE flag(s)) and immediately request SLEEP
mode (by setting SLPRQ). It will then depend on the exact sequence of
operations whether the msCAN12 will start transmitting or go into
SLEEP mode directly.
During SLEEP mode, the SLPAK flag is set. The application software
should use SLPAK as a handshake indication for the request (SLPRQ)
to go into SLEEP mode. When in SLEEP mode, the msCAN12 stops its
internal clocks. Clocks to allow register accesses will still run. The
TxCAN pin will stay in recessive state. If RXF=1, the message can be
read and RXF can be cleared. However, if the msCAN12 is in bus-off
state, it stops counting 128*11 consecutive recessive bits due to the
stopped clocks. Likewise, copying of RxBG into RxFG will not take place
while in sleep mode. It is possible to access the transmit buffers and to
clear the TXE flags. No message abort will take place while in sleep
mode.
The msCAN12 will leave SLEEP mode (wake-up) when
•
•
•
bus activity occurs or
the MCU clears the SLPRQ bit or
the MCU sets SFTRES.
NOTE: The MCU cannot clear the SLPRQ bit before the msCAN12 is in SLEEP
mode (SLPAK = 1).
After wake-up, the msCAN12 waits for 11 consecutive recessive bits to
synchronize to the bus. As a consequence, if the msCAN12 is woken-up
by a CAN frame, this frame will not be received. The receive message
buffers (RxBG and RxFG) will contain messages if they were received
before sleep mode was entered. Pending copying of RxBG and RxFG,
15-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
283
MSCAN Controlle r
as well as pending message aborts and pending message
transmissions, will now be executed. If the msCAN12 is still in bus-off
state after sleep mode was left, it continues counting the 128*11
consecutive recessive bits.
msCAN12 Running
SLPRQ = 0
SLPAK = 0
MCU
MCU
or msCAN12
msCAN12 Sleeping
SLEEP Request
SLPRQ = 1
SLPAK = 1
SLPRQ = 1
SLPAK = 0
msCAN12
Figure 46 SLEEP Request / Acknowledge Cycle
m sCAN12
SOFT_RESET Mod e
In SOFT_RESET mode, the msCAN12 is stopped. Registers can still be
accessed. This mode is used to initialize the module configuration, bit
timing, and the CAN message filter. See msCAN12 Module Control
Register (CMCR0) for a complete description of the SOFT_RESET
mode.
When setting the SFTRES bit, the msCAN12 immediately stops all
ongoing transmissions and receptions, potentially causing the CAN
protocol violations. The user is responsible to take care that the
msCAN12 is not active when SOFT_RESET mode is entered. The
recommended procedure is to bring the msCAN12 into SLEEP mode
before the SFTRES bit is set.
16-mscan12
MC68HC912DT128A Rev 2.0
284
MSCAN Controller
MOTOROLA
MSCAN Controller
Timer Link
m sCAN12
POWER_DOWN
Mod e
The msCAN12 is in POWER_DOWN mode when
•
•
the CPU is in STOP mode or
the CPU is in WAIT mode and the CSWAI bit is set (see msCAN12
Module Control Register (CMCR0)).
When entering the POWER_DOWN mode, the msCAN12 immediately
stops all ongoing transmissions and receptions, potentially causing CAN
protocol violations. The user is responsible to take care that the
msCAN12 is not active when POWER_DOWN mode is entered. The
recommended procedure is to bring the msCAN12 into SLEEP mode
before the STOP instruction (or the WAI instruction, if CSWAI is set) is
executed.
To protect the CAN bus system from fatal consequences of violations to
above rule, the msCAN12 will drive the TxCAN pin into recessive state.
In POWER_DOWN mode, no registers can be accessed.
Prog ra m m a b le
Wa ke -Up Func tion
The msCAN12 can be programmed to apply a low-pass filter function to
the RxCAN input line while in SLEEP mode (see control bit WUPM in the
module control register, msCAN12 Module Control Register (CMCR0)).
This feature can be used to protect the msCAN12 from wake-up due to
short glitches on the CAN bus lines. Such glitches can result from
electromagnetic inference within noisy environments.
Tim e r Link
The msCAN12 will generate a timer signal whenever a valid frame has
been received. Because the CAN specification defines a frame to be
valid if no errors occurred before the EOF field has been transmitted
successfully, the timer signal will be generated right after the EOF. A
pulse of one bit time is generated. As the msCAN12 receiver engine
receives also the frames being sent by itself, a timer signal will also be
generated after a successful transmission.
17-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
285
MSCAN Controlle r
The previously described timer signal can be routed into the on-chip
timer module (ECT). Under the control of the timer link enable (TLNKEN)
bit in the CMCR0, this signal will be connected to the ECT timer channel
m input1.
After ECT timer has been programmed to capture rising edge events, it
can be used under software control to generate 16-bit time stamps which
can be stored with the received message.
Cloc k Syste m
Figure 47 shows the structure of the msCAN12 clock generation
circuitry. With this flexible clocking scheme the msCAN12 is able to
handle CAN bus rates ranging from 10 kbps up to 1 Mbps.
CGM
msCAN12
SYSCLK
EXTALi
Time quanta
clock
CGMCANCLK
Prescaler
(1...64)
CLKSRC
CLKSRC
Figure 47 Clocking Scheme
The clock source bit (CLKSRC) in the msCAN12 module control register
(CMCR1) (see msCAN12 Bus Timing Register 0 (CBTR0)) defines
whether the msCAN12 is connected to the output of the crystal oscillator
(EXTALi) or to the system clock (SYSCLK).
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 50% duty cycle of the clock is required.
1. The timer channel being used for the timer link for CAN0 is channel 4 and for CAN1 is channel
5.
18-mscan12
MC68HC912DT128A Rev 2.0
286
MSCAN Controller
MOTOROLA
MSCAN Controller
Clock System
For microcontrollers without the CGM module, CGMCANCLK is driven
from the crystal oscillator (EXTALi).
A programmable prescaler is used to generate out of msCANCLK the
time quanta (Tq) clock. A time quantum is the atomic unit of time handled
by the msCAN12. A bit time is subdivided into three segments1:
•
•
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.
The synchronization jump width can be programmed in a range of 1 to 4
time quanta by setting the SJW parameter.
Above parameters can be set by programming the bus timing registers
(CBTR0–1, see msCAN12 Bus Timing Register 0 (CBTR0) and
msCAN12 Bus Timing Register 1 (CBTR1)).
It is the user’s responsibility to make sure that his bit time settings are in
compliance with the CAN standard. Figure 49 gives an overview on the
CAN conforming segment settings and the related parameter values.
1. For further explanation of the under-lying concepts please refer to ISO/DIS 11519-1, Section
10.3.
19-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
287
MSCAN Controlle r
NRZ Signal
SYNC
_SEG
Time segment 1
(PROP_SEG + PHASE_SEG1)
Time Seg. 2
(PHASE_SEG2)
1
4 ... 16
2 ... 8
8... 25 Time Quanta
= 1 Bit Time
Transmit point
Sample point
(single or triple sampling)
Figure 48 Segments within the Bit Time
Figure 49 CAN Standard Compliant Bit Time Segment Settings
Synchron.
Jump Width
Time Segment 1 TSEG1 Time Segment 2 TSEG2
SJW
5 .. 10
4 .. 11
5 .. 12
6 .. 13
7 .. 14
8 .. 15
9 .. 16
4 .. 9
3 .. 10
4 .. 11
5 .. 12
6 .. 13
7 .. 14
8 .. 15
2
3
4
5
6
7
8
1
2
3
4
5
6
7
1 .. 2
0 .. 1
0 .. 2
0 .. 3
0 .. 3
0 .. 3
0 .. 3
0 .. 3
1 .. 3
1 .. 4
1 .. 4
1 .. 4
1 .. 4
1 .. 4
Me m ory Ma p
The msCAN12 occupies 128 bytes in the CPU12 memory space. The
background receive buffer can only be read in test mode.
20-mscan12
MC68HC912DT128A Rev 2.0
288
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Message Storage
Figure 50 msCAN12 Memory Map
$0100
$0108
$0109
$010D
$010E
$010F
$0110
$011F
$0120
$013C
$013D
$013F
$0140
$014F
$0150
$015F
$0160
$016F
$0170
$017F
Control registers
9 bytes
Reserved
5 bytes
Error counters
2 bytes
Identifier filter
16 bytes
Reserved
29 bytes
Port CAN registers
3 bytes
Foreground Receive buffer
Transmit buffer 0
Transmit buffer 1
Transmit buffer 2
Prog ra m m e r’s Mod e l of Me ssa g e Stora g e
The following section details the organization of the receive and transmit
message buffers and the associated control registers. For reasons of
programmer interface simplification 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.
21-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
289
MSCAN Controlle r
Figure 51 Message Buffer Organization
Address
Register name
(1)
01x0
01x1
01x2
01x3
01x4
01x5
01x6
01x7
01x8
01x9
01xA
01xB
01xC
01xD
01xE
01xF
Identifier register 0
Identifier register 1
Identifier register 2
Identifier register 3
Data segment register 0
Data segment register 1
Data segment register 2
Data segment register 3
Data segment register 4
Data segment register 5
Data segment register 6
Data segment register 7
Data length register
Transmit buffer priority register(2)
Unused
Unused
1. x is 4, 5, 6, or 7 depending on which buffer RxFG,
Tx0, Tx1, or Tx2 respectively.
2. Not applicable for receive buffers
Me ssa g e Buffe r
Outline
Figure 52 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 53. All bits of the 13
byte data structure are undefined out of reset.
NOTE: The foreground receive buffer can be read anytime but can not be
written. The transmit buffers can be read or written anytime.
22-mscan12
MC68HC912DT128A Rev 2.0
290
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Message Storage
Figure 52 Receive/Transmit Message Buffer Extended Identifier
ADDR(1)
REGISTER
R/W BIT 7
6
5
4
3
2
1
BIT 0
R
$01x0
IDR0
ID28
W
ID27
ID26
ID25
ID24
ID23
ID22
ID21
R
$01x1
$01x2
$01x3
$01x4
$01x5
$01x6
$01x7
$01x8
$01x9
$01xA
$01xB
$01xC
IDR1
IDR2
ID20
W
ID19
ID13
ID5
ID18 SRR (1) IDE (1)
ID17
ID9
ID16
ID8
ID15
ID7
R
ID14
W
ID12
ID4
ID11
ID3
ID10
ID2
R
IDR3
ID6
W
ID1
ID0
RTR
DB0
DB0
DB0
DB0
DB0
DB0
DB0
DB0
DLC0
R
DSR0
DSR1
DSR2
DSR3
DSR4
DSR5
DSR6
DSR7
DLR
DB7
W
DB6
DB6
DB6
DB6
DB6
DB6
DB6
DB6
DB5
DB5
DB5
DB5
DB5
DB5
DB5
DB5
DB4
DB4
DB4
DB4
DB4
DB4
DB4
DB4
DB3
DB3
DB3
DB3
DB3
DB3
DB3
DB3
DLC3
DB2
DB2
DB2
DB2
DB2
DB2
DB2
DB2
DLC2
DB1
DB1
DB1
DB1
DB1
DB1
DB1
DB1
DLC1
R
DB7
W
R
DB7
W
R
DB7
W
R
DB7
W
R
DB7
W
R
DB7
W
R
DB7
W
R
W
1. x is 4, 5, 6, or 7 depending on which buffer RxFG, Tx0, Tx1, or Tx2 respectively.
23-mscan12
MC68HC912DT128A Rev 2.0
291
MOTOROLA
MSCAN Controller
MSCAN Controlle r
Figure 53 Standard Identifier Mapping
ADDR(1)
REGISTER
R/W BIT 7
6
5
4
3
2
1
BIT 0
R
$01x0
$01x1
$01x2
$01x3
IDR0
IDR1
IDR2
IDR3
ID10
W
ID9
ID8
ID7
ID6
ID5
ID4
ID3
R
ID2
W
ID1
ID0
RTR
IDE(0)
R
W
R
W
1. x is 4, 5, 6, or 7 depending on which buffer RxFG, Tx0, Tx1, or Tx2 respectively.
Id e ntifie r Re g iste rs
(IDRn)
The identifiers consist of either 11 bits (ID10–ID0) for the standard, or 29
bits (ID28–ID0) for the extended format. ID10/28 is the most significant
bit and is transmitted first on the bus during the arbitration procedure.
The priority of an identifier is defined to be highest for the smallest binary
number.
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 will be stored as received
on the CAN bus for receive buffers.
IDE — ID Extended
This flag indicates whether the extended or standard identifier format
is applied in this buffer. In case of a receive buffer the flag is set as
being received and indicates to the CPU how to process the buffer
identifier registers. In case of a transmit buffer the flag indicates to the
msCAN12 what type of identifier to send.
0 = Standard format (11-bit)
1 = Extended format (29-bit)
24-mscan12
MC68HC912DT128A Rev 2.0
292
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Message Storage
RTR — Remote transmission request
This flag reflects the status of the Remote Transmission Request bit
in the CAN frame. In case of a receive buffer it indicates the status of
the received frame and allows to support the transmission of an
answering frame in software. In case of a transmit buffer this flag
defines the setting of the RTR bit to be sent.
0 = Data frame
1 = Remote frame
Da ta Le ng th
This register keeps the data length field of the CAN frame.
Re g iste r (DLR)
DLC3 – DLC0 — Data length code bits
The data length code contains the number of bytes (data byte count)
of the respective message. At transmission of a remote frame, the
data length code is transmitted as programmed while the number of
transmitted bytes is always 0. The data byte count ranges from 0 to 8
for a data frame. Table 40 shows the effect of setting the DLC bits.
Table 40 Data length codes
Data length code
Data
byte
count
DLC3
DLC2
DLC1
DLC0
0
0
0
0
0
0
0
0
1
0
0
0
0
1
1
1
1
0
0
0
1
1
0
0
1
1
0
0
1
0
1
0
1
0
1
0
0
1
2
3
4
5
6
7
8
Da ta Se g m e nt
Re g iste rs (DSRn)
The eight data segment registers contain the data to be transmitted or
being received. The number of bytes to be transmitted or being received
is determined by the data length code in the corresponding DLR.
25-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
293
MSCAN Controlle r
Tra nsm it Buffe r Priority Re g iste rs (TBPR)
BIT 7
PRIO7
-
BIT 6
PRIO6
-
BIT 5
PRIO5
-
BIT 4
PRIO4
-
BIT 3
PRIO3
-
BIT 2
PRIO2
-
BIT 1
PRIO1
-
BIT 0
PRIO0
-
TBPR(1)
$01xD
R
W
RESET
1. x is 5, 6, or 7 depending on which buffer Tx0, Tx1, or Tx2 respectively.
PRIO7 – PRIO0 — Local Priority
This field defines the local priority of the associated message buffer.
The local priority is used for the internal prioritizing process of the
msCAN12 and is defined to be highest for the smallest binary number.
The msCAN12 implements the following internal priorization
mechanism:
•
•
•
All transmission buffers with a cleared TXE flag participate in the
priorisation right before the SOF (Start of Frame) is sent.
The transmission buffer with the lowest local priority field wins the
priorisation.
In case of more than one buffer having the same lowest priority the
message buffer with the lower index number wins.
NOTE: To ensure data integrity, no registers of the transmit buffers shall be
written while the associated TXE flag is cleared.
To ensure data integrity, no registers of the receive buffer shall be read
while the RXF flag is cleared.
Prog ra m m e r’s Mod e l of Control Re g iste rs
Ove rvie w
The programmer’s model has been laid out for maximum simplicity and
efficiency.
26-mscan12
MC68HC912DT128A Rev 2.0
294
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
m sCAN12 Mod ule Control Re g iste r (CMCR0)
Bit 7
0
6
0
5
CSWAI
1
4
3
TLNKEN
0
2
1
SLPRQ
0
Bit 0
SFTRES
1
CMCR0
$0100
R
SYNCH
SLPAK
W
RESET
0
0
0
0
CSWAI — CAN Stops in Wait Mode
0 = The module is not affected during WAIT mode.
1 = The module ceases to be clocked during WAIT mode.
SYNCH — Synchronized Status
This bit indicates whether the msCAN12 is synchronized to the CAN
bus and as such can participate in the communication process.
0 = msCAN12 is not synchronized to the CAN bus
1 = msCAN12 is synchronized to the CAN bus
TLNKEN — Timer Enable
This flag is used to establish a link between the msCAN12 and the
on-chip timer (see Timer Link).
0 = The port is connected to the timer input.
1 = The msCAN12 timer signal output is connected to the timer
input.
SLPAK — SLEEP Mode Acknowledge
This flag indicates whether the msCAN12 is in module internal
SLEEP Mode. It shall be used as a handshake for the SLEEP Mode
request (see msCAN12 SLEEP Mode).
0 = Wake-up – The msCAN12 is not in SLEEP Mode.
1 = SLEEP – The msCAN12 is in SLEEP Mode.
SLPRQ — SLEEP request
This flag allows to request the msCAN12 to go into an internal
power-saving mode (see msCAN12 SLEEP Mode).
0 = Wake-up – The msCAN12 will function normally.
1 = SLEEP request – The msCAN12 will go into SLEEP Mode.
27-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
295
MSCAN Controlle r
SFTRES— SOFT_RESET
When this bit is set by the CPU, the msCAN12 immediately enters the
SOFT_RESET state. Any ongoing transmission or reception is
aborted and synchronization to the bus is lost.
The following registers will go into and stay in the same state as out
of hard reset: CMCR0, CRFLG, CRIER, CTFLG, CTCR.
The registers CMCR1, CBTR0, CBTR1, CIDAC, CIDAR0–3,
CIDMR0–3 can only be written by the CPU when the msCAN12 is in
SOFT_RESET state. The values of the error counters are not affected
by SOFT_RESET.
When this bit is cleared by the CPU, the msCAN12 will try to
synchronize to the CAN bus: If the msCAN12 is not in BUSOFF state
it will be synchronized after 11 recessive bits on the bus; if the
msCAN12 is in BUSOFF state it continues to wait for 128 occurrences
of 11 recessive bits.
Clearing SFTRES and writing to other bits in CMCR0 must be in
separate instructions.
0 = Normal operation
1 = msCAN12 in SOFT_RESET state.
m sCAN12 Mod ule Control Re g iste r (CMCR1)
Bit 7
0
6
0
5
0
4
0
3
0
2
LOOPB
0
1
WUPM
0
Bit 0
CLKSRC
0
CMCR1
$0101
R
W
RESET
0
0
0
0
0
LOOPB — Loop Back Self Test Mode
When this bit is set the msCAN12 performs an internal loop back
which can be used for self test operation: the bit stream output of the
transmitter is fed back to the receiver. The RxCAN input pin is ignored
and the TxCAN output goes to the recessive state (1). Note that in this
state the msCAN12 ignores the bit sent during the ACK slot of the
CAN frame Acknowledge field to insure proper reception of its own
message and will treat messages being received while in
transmission as received messages from remote nodes.
0 = Normal operation
1 = Activate loop back self test mode
28-mscan12
MC68HC912DT128A Rev 2.0
296
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
WUPM — Wake-Up Mode
This flag defines whether the integrated low-pass filter is applied to
protect the msCAN12 from spurious wake-ups (see Programmable
Wake-Up Function).
0 = msCAN12 will wake up the CPU after any recessive to
dominant edge on the CAN bus.
1 = msCAN12 will wake up the CPU only in case of dominant pulse
on the bus which has a length of at least approximately Twup
.
CLKSRC — msCAN12 Clock Source
This flag defines which clock source the msCAN12 module is driven
from (only for system with CGM module; see Clock System,
Figure 47).
0 = The msCAN12 clock source is EXTALi.
1 = The msCAN12 clock source is SYSCLK, twice the frequency of
ECLK.
NOTE: The CMCR1 register can only be written if the SFTRES bit in CMCR0 is
set.
m sCAN12 Bus Tim ing Re g iste r 0 (CBTR0)
Bit 7
SJW1
0
6
SJW0
0
5
BRP5
0
4
BRP4
0
3
BRP3
0
2
BRP2
0
1
BRP1
0
Bit 0
BRP0
0
CBTR0
$0102
R
W
RESET
SJW1, SJW0 — Synchronization Jump Width
The synchronization jump width defines the maximum number of time
quanta (Tq) clock cycles by which a bit may be shortened, or
lengthened, to achieve resynchronization on data transitions on the
bus (see Table 41).
29-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
297
MSCAN Controlle r
Table 41 Synchronization jump width
SJW1
SJW0
Synchronization jump width
0
0
1
1
0
1
0
1
1 Tq clock cycle
2 Tq clock cycles
3 Tq clock cycles
4 Tq clock cycles
BRP5 – BRP0 — Baud Rate Prescaler
These bits determine the time quanta (Tq) clock, which is used to
build up the individual bit timing, according to Table 42.
Table 42 Baud rate prescaler
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0 Prescaler value (P)
0
0
0
0
:
0
0
0
0
:
0
0
0
0
:
0
0
0
0
:
0
0
1
1
:
0
1
0
1
:
1
2
3
4
:
:
:
:
:
:
:
:
1
1
1
1
1
1
64
NOTE: The CBTR0 register can only be written if the SFTRES bit in CMCR0 is
set.
m sCAN12 Bus Tim ing Re g iste r 1 (CBTR1)
Bit 7
SAMP
0
6
TSEG22
0
5
TSEG21
0
4
TSEG20
0
3
TSEG13
0
2
TSEG12
0
1
TSEG11
0
Bit 0
TSEG10
0
CBTR1
$0103
R
W
RESET
SAMP — Sampling
This bit determines the number of samples of the serial bus to be
taken per bit time. If set three samples per bit are taken, the regular
one (sample point) and two preceding samples, using a majority rule.
For higher bit rates SAMP should be cleared, which means that only
one sample will be taken per bit.
30-mscan12
MC68HC912DT128A Rev 2.0
298
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
0 = One sample per bit.
1 = Three samples per bit1.
TSEG22 – TSEG10 — Time Segment
Time segments within the bit time fix the number of clock cycles per
bit time, and the location of the sample point.
Table 43 Time segment syntax
SYNC_SEG System expects transitions to occur on the bus during this period.
A node in transmit mode will transfer a new value to the CAN bus at
Transmit point
this point.
A node in receive mode will sample the bus at this point. If the three
Sample point samples per bit option is selected then this point marks the position
of the third sample.
Time segment 1 (TSEG1) and time segment 2 (TSEG2) are
programmable as shown in Table 44.
Table 44 Time segment values
TSEG13 TSEG12 TSEG11 TSEG10 Time segment 1
TSEG22 TSEG21 TSEG20 Time segment 2
0
0
0
0
.
0
0
0
0
.
0
0
1
1
.
0
1
0
1
.
1 Tq clock cycle
2 Tq clock cycles
3 Tq clock cycles
4 Tq clock cycles
.
0
0
.
0
0
.
0
1
.
1 Tq clock cycle
2 Tq clock cycles
.
.
.
.
.
1
1
1
8 Tq clock cycles
.
.
.
.
.
1
1
1
1
16 Tq clock cycles
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 above).
NOTE: The CBTR1 register can only be written if the SFTRES bit in CMCR0 is
set.
m sCAN12
All bits of this register are read and clear only. A flag can be cleared by
Re c e ive r Fla g
Re g iste r (CRFLG)
writing a 1 to the corresponding bit position. A flag can only be cleared
when the condition which caused the setting is no more valid. Writing a
1. In this case PHASE_SEG1 must be at least 2 TimeQuanta.
MC68HC912DT128A Rev 2.0
31-mscan12
MOTOROLA
MSCAN Controller
299
MSCAN Controlle r
0 has no effect on the flag setting. Every flag has an associated interrupt
enable flag in the CRIER register. A hard or soft reset will clear the
register.
Bit 7
6
RWRNIF
0
5
TWRNIF
0
4
RERRIF
0
3
TERRIF
0
2
BOFFIF
0
1
OVRIF
0
Bit 0
RXF
0
CRFLG
$0104
R
WUPIF
0
W
RESET
WUPIF — Wake-up Interrupt Flag
If the msCAN12 detects bus activity while it is in SLEEP Mode, it
clears the SLPAK bit in the CMCR0 register; the WUPIF bit will then
be set. If not masked, a Wake-Up interrupt is pending while this flag
is set.
0 = No wake-up activity has been observed while in SLEEP Mode.
1 = msCAN12 has detected activity on the bus and requested
wake-up.
RWRNIF — Receiver Warning Interrupt Flag
This bit will be set when the msCAN12 goes into warning status due
to the Receive Error counter (REC) exceeding 96 and neither one of
the Error interrupt flags or the Bus-Off interrupt flag is set1. If not
masked, an Error interrupt is pending while this flag is set.
0 = No receiver warning status has been reached.
1 = msCAN12 went into receiver warning status.
TWRNIF — Transmitter Warning Interrupt Flag
This bit will be set when the msCAN12 goes into warning status due
to the Transmit Error counter (TEC) exceeding 96 and neither one of
the Error interrupt flags or the Bus-Off interrupt flag is set2. If not
masked, an Error interrupt is pending while this flag is set.
0 = No transmitter warning status has been reached.
1 = msCAN12 went into transmitter warning status.
1. RWRNIF = (96 < REC) & RERRIF& TERRIF & BOFFIF
2. TWRNIF = (96 < TEC) & RERRIF& TERRIF & BOFFIF
32-mscan12
MC68HC912DT128A Rev 2.0
300
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
RERRIF — Receiver Error Passive Interrupt Flag
This bit will be set when the msCAN12 goes into error passive status
due to the Receive Error counter (REC) exceeding 127 and the
Bus-Off interrupt flag is not set1. If not masked, an Error interrupt is
pending while this flag is set.
0 = No receiver error passive status has been reached.
1 = msCAN12 went into receiver error passive status.
TERRIF — Transmitter Error Passive Interrupt Flag
This bit will be set when the msCAN12 goes into error passive status
due to the Transmit Error counter (TEC) exceeding 127 and the
Bus-Off interrupt flag is not set2. If not masked, an Error interrupt is
pending while this flag is set.
0 = No transmitter error passive status has been reached.
1 = msCAN12 went into transmitter error passive status.
BOFFIF — BUSOFF Interrupt Flag
This bit will be set when the msCAN12 goes into BUSOFF status, due
to the Transmit Error counter exceeding 255. It cannot be cleared
before the msCAN12 has monitored 128*11 consecutive recessive
bits on the bus. If not masked, an Error interrupt is pending while this
flag is set.
0 = No BUSOFF status has been reached.
1 = msCAN12 went into BUSOFF status.
OVRIF — Overrun Interrupt Flag
This bit will be set when a data overrun condition occurred. If not
masked, an Error interrupt is pending while this flag is set.
0 = No data overrun has occurred.
1 = A data overrun has been detected.
RXF — Receive Buffer Full
The RXF flag is set by the msCAN12 when a new message is
available in the foreground receive buffer. This flag indicates whether
the buffer is loaded with a correctly received message. After the CPU
1. RERRIF = (128 < REC < 255) & BOFFIF
2. TERRIF = (128 < TEC < 255) & BOFFIF
33-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
301
MSCAN Controlle r
has read that message from the receive buffer the RXF flag must be
handshaked (cleared) in order to release the buffer. A set RXF flag
prohibits the exchange of the background receive buffer into the
foreground buffer. If not masked, a Receive interrupt is pending while
this flag is set.
0 = The receive buffer is released (not full).
1 = The receive buffer is full. A new message is available.
NOTE: The CRFLG register is held in the reset state if the SFTRES bit in
CMCR0 is set.
m sCAN12 Re c e ive r Inte rrup t Ena b le Re g iste r (CRIER)
Bit 7
WUPIE
0
6
RWRNIE
0
5
TWRNIE
0
4
RERRIE
0
3
TERRIE
0
2
BOFFIE
0
1
OVRIE
0
Bit 0
RXFIE
0
CRIER
$0105
R
W
RESET
WUPIE — Wake-up Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A wake-up event will result in a wake-up interrupt.
RWRNIE — Receiver Warning Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A receiver warning status event will result in an error interrupt.
TWRNIE — Transmitter Warning Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A transmitter warning status event will result in an error
interrupt.
RERRIE — Receiver Error Passive Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A receiver error passive status event will result in an error
interrupt.
TERRIE — Transmitter Error Passive Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A transmitter error passive status event will result in an error
interrupt.
34-mscan12
MC68HC912DT128A Rev 2.0
302
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
BOFFIE — BUSOFF Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A BUSOFF event will result in an error interrupt.
OVRIE — Overrun Interrupt Enable
0 = No interrupt will be generated from this event.
1 = An overrun event will result in an error interrupt.
RXFIE — Receiver Full Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A receive buffer full (successful message reception) event will
result in a receive interrupt.
NOTE: The CRIER register is held in the reset state if the SFTRES bit in CMCR0
is set.
m sCAN12
The Abort Acknowledge flags are read only. The Transmitter Buffer
Tra nsm itte r Fla g
Re g iste r (CTFLG)
Empty flags are read and clear only. A flag can be cleared by writing a1
to the corresponding bit position. Writing a zero has no effect on the flag
setting. The Transmitter Buffer Empty flags each have an associated
interrupt enable flag in the CTCR register. A hard or soft reset will reset
the register.
Bit 7
6
5
4
3
0
2
TXE2
1
1
TXE1
1
Bit 0
TXE0
1
CTFLG
$0106
R
0
ABTAK2
ABTAK1
ABTAK0
W
RESET
0
0
0
0
0
ABTAK2 – ABTAK0 — Abort Acknowledge
This flag acknowledges that a message has been aborted due to a
pending abort request from the CPU. After a particular message
buffer has been flagged empty, this flag can be used by the
application software to identify whether the message has been
aborted successfully or has been sent in the meantime. The flag is
reset implicitly whenever the associated TXE flag is set to 0.
0 = The massage has not been aborted, thus has been sent out.
1 = The message has been aborted.
35-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
303
MSCAN Controlle r
TXE2 – TXE0 —Transmitter Buffer Empty
This flag indicates that the associated transmit message buffer is
empty, thus not scheduled for transmission. The CPU must
handshake (clear) the flag after a message has been set up in the
transmit buffer and is due for transmission. The msCAN12 will set the
flag after the message has been sent successfully. The flag will also
be set by the msCAN12 when the transmission request was
successfully aborted due to a pending abort request (msCAN12
Transmitter Control Register (CTCR)). If not masked, a transmit
interrupt is pending while this flag is set.
Clearing this flag will also clear the corresponding Abort Acknowledge
flag (ABTAK, see above). Setting this flag will clear the corresponding
Abort Request flag (ABTRQ, msCAN12 Transmitter Control Register
(CTCR)).
0 = The associated message buffer is full (loaded with a message
due for transmission).
1 = The associated message buffer is empty (not scheduled).
NOTE: The CTFLG register is held in the reset state if the SFTRES bit in
CMCR0 is set.
m sCAN12 Tra nsm itte r Control Re g iste r (CTCR)
Bit 7
6
ABTRQ2
0
5
ABTRQ1
0
4
ABTRQ0
0
3
0
2
TXEIE2
0
1
TXEIE1
0
Bit 0
TXEIE0
0
CTCR
$0107
RESET
R
0
W
0
0
ABTRQ2 – ABTRQ0 — Abort Request
The CPU sets this bit to request that an already scheduled message
buffer (TXE = 0) shall be aborted. The msCAN12 will grant the
request when the message is not already under transmission. When
a message is aborted the associated TXE and the abort acknowledge
flag (ABTAK, see msCAN12 Transmitter Flag Register (CTFLG)) will
be set and an TXE interrupt will occur if enabled. The CPU can not
reset ABTRQx. ABTRQx is reset implicitly whenever the associated
TXE flag is set.
0 = No abort request.
1 = Abort request pending.
36-mscan12
MC68HC912DT128A Rev 2.0
304
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
NOTE: The software must not clear one or more of the TXE flags in CTFGL and
simultaneously set the respective ABTRQ bit(s).
TXEIE2 – TXEIE0 — Transmitter Empty Interrupt Enable
0 = No interrupt will be generated from this event.
1 = A transmitter empty (transmit buffer available for transmission)
event will result in a transmitter empty interrupt.
NOTE: The CTCR register is held in the reset state if the SFTRES bit in CMCR0
is set.
m sCAN12 Id e ntifie r Ac c e p ta nc e Control Re g iste r (CIDAC)
Bit 7
0
6
0
5
IDAM1
0
4
IDAM0
0
3
0
2
1
Bit 0
CIDAC
$0108
R
IDHIT2
IDHIT1
IDHIT0
W
RESET
0
0
0
0
0
0
IDAM1 – IDAM0 — Identifier Acceptance Mode
The CPU sets these flags to define the identifier acceptance filter
organization (see Identifier Acceptance Filter). Table 44 summarizes
the different settings. In Filter Closed mode no messages will be
accepted such that the foreground buffer will never be reloaded.
Table 45 Identifier Acceptance Mode Settings
IDAM1
IDAM0
Identifier Acceptance Mode
Two 32 bit Acceptance Filters
Four 16 bit Acceptance Filters
Eight 8 bit Acceptance Filters
Filter Closed
0
0
1
1
0
1
0
1
IDHIT2 – IDHIT0 — Identifier Acceptance Hit Indicator
The msCAN12 sets these flags to indicate an identifier acceptance hit
(see Identifier Acceptance Filter). Table 44 summarizes the different
settings.
37-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
305
MSCAN Controlle r
Table 46 Identifier Acceptance Hit Indication
IDHIT2
IDHIT1
IDHIT0
Identifier Acceptance Hit
Filter 0 Hit
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
Filter 1 Hit
Filter 2 Hit
Filter 3 Hit
Filter 4 Hit
Filter 5 Hit
Filter 6 Hit
Filter 7 Hit
The IDHIT indicators are always related to the message in the
foreground buffer. When a message gets copied from the background to
the foreground buffer the indicators are updated as well.
NOTE: The CIDAC register can only be written if the SFTRES bit in CMCR0 is
set.
m sCAN12 Re c e ive Error Counte r (CRXERR)
Bit 7
RXERR7
6
5
4
3
2
1
Bit 0
CRXERR
$010E
R
RXERR6
RXERR5
RXERR4
0
RXERR3
RXERR2
RXERR1
RXERR0
W
RESET
0
0
0
0
0
0
0
This register reflects the status of the msCAN12 receive error counter.
The register is read only.
m sCAN12 Tra nsm it Error Counte r (CTXERR)
Bit 7
6
5
4
3
2
1
Bit 0
CTXERR
$010F
R
TXERR7
TXERR6
TXERR5
TXERR4
TXERR3
TXERR2
TXERR1
TXERR0
W
RESET
0
0
0
0
0
0
0
0
This register reflects the status of the msCAN12 transmit error counter.
The register is read only.
NOTE: Both error counters must only be read when in SLEEP or SOFT_RESET
mode.
38-mscan12
MC68HC912DT128A Rev 2.0
306
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
m sCAN12
Id e ntifie r
Ac c e p ta nc e
Re g iste rs
On reception each message is written into the background receive
buffer. The CPU is only signalled to read the message however, if it
passes the criteria in the identifier acceptance and identifier mask
registers (accepted); otherwise, the message will be overwritten by the
next message (dropped).
(CIDAR0–7)
The acceptance registers of the msCAN12 are applied on the IDR0 to
IDR3 registers of incoming messages in a bit by bit manner.
For extended identifiers all four acceptance and mask registers are
applied. For standard identifiers only the first two (CIDMR0/1 and
CIDAR0/1) are applied. In the latter case it is required to program the
three last bits (AM2 – AM0) in the mask register CIDMR1 to ‘don’t care’.
Figure 54 Identifier Acceptance Registers (1st bank)
Bit 7
6
5
4
3
2
1
Bit 0
AC0
CIDAR0
$0110
R
W
R
AC7
AC6
AC5
AC4
AC3
AC2
AC1
CIDAR1
$0111
AC7
AC7
AC6
AC6
AC5
AC5
AC4
AC4
AC3
AC3
AC2
AC2
AC1
AC1
AC0
AC0
W
R
CIDAR2
$0112
W
R
CIDAR3
$0113
AC7
-
AC6
-
AC5
-
AC4
-
AC3
-
AC2
-
AC1
-
AC0
-
W
RESET
Figure 55 Identifier Acceptance Registers (2nd bank)
Bit 7
6
5
4
3
2
1
Bit 0
AC0
CIDAR4
$0118
R
W
R
AC7
AC6
AC5
AC4
AC3
AC2
AC1
CIDAR5
$0119
AC7
AC7
AC6
AC6
AC5
AC5
AC4
AC4
AC3
AC3
AC2
AC2
AC1
AC1
AC0
AC0
W
R
CIDAR6
$011A
W
R
CIDAR7
$011B
AC7
-
AC6
-
AC5
-
AC4
-
AC3
-
AC2
-
AC1
-
AC0
-
W
RESET
39-mscan12
MC68HC912DT128A Rev 2.0
307
MOTOROLA
MSCAN Controller
MSCAN Controlle r
AC7 – AC0 — Acceptance Code Bits
AC7 – AC0 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.
NOTE: The CIDAR0–7 registers can only be written if the SFTRES bit in
CMCR0 is set.
m sCAN12
The identifier mask register specifies which of the corresponding bits in
Id e ntifie r Ma sk
Re g iste rs
the identifier acceptance register are relevant for acceptance filtering.
(CIDMR0–7)
Figure 56 Identifier Mask Registers (1st bank)
Bit 7
AM7
6
5
4
3
2
1
Bit 0
AM0
CIDMR0
$0114
R
W
R
AM6
AM5
AM4
AM3
AM2
AM1
CIDMR1
$0115
AM7
AM7
AM6
AM6
AM5
AM5
AM4
AM4
AM3
AM3
AM2
AM2
AM1
AM1
AM0
AM0
W
R
CIDMR2
$0116
W
R
CIDMR3
$0117
AM7
-
AM6
-
AM5
-
AM4
-
AM3
-
AM2
-
AM1
-
AM0
-
W
RESET
Figure 57 Identifier Mask Registers (2nd bank)
Bit 7
AM7
6
5
4
3
2
1
Bit 0
AM0
CIDMR4
$011C
R
W
R
AM6
AM5
AM4
AM3
AM2
AM1
CIDMR5
$011D
AM7
AM7
AM6
AM6
AM5
AM5
AM4
AM4
AM3
AM3
AM2
AM2
AM1
AM1
AM0
AM0
W
R
CIDMR6
$011E
W
R
CIDMR7
$011F
AM7
-
AM6
-
AM5
-
AM4
-
AM3
-
AM2
-
AM1
-
AM0
-
W
RESET
40-mscan12
MC68HC912DT128A Rev 2.0
308
MSCAN Controller
MOTOROLA
MSCAN Controller
Programmer’s Model of Control Registers
AM7 – AM0 — 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 will be detected. The
message will be 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 will 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.
NOTE: The CIDMR0–7 registers can only be written if the SFTRES bit in
CMCR0 is set.
m sCAN12 Port CAN Control Re g iste r (PCTLCAN)
Bit 7
0
6
0
5
0
4
0
3
0
2
0
1
PUPCAN
0
Bit 0
RDPCAN
0
PCTLCAN
$013D
R
W
RESET
0
0
0
0
0
0
The following bits control pins 7 through 2 of Port CAN when they are
implemented externally.
PUPCAN — Pull-Up Enable Port CAN
0 = Pull mode disabled for Port CAN.
1 = Pull mode enabled for Port CAN.
RDPCAN — Reduced Drive Port CAN
0 = Reduced drive disabled for Port CAN.
1 = Reduced drive enabled for Port CAN.
41-mscan12
MC68HC912DT128A Rev 2.0
MOTOROLA
MSCAN Controller
309
MSCAN Controlle r
m sCAN12 Port CAN Da ta Re g iste r (PORTCAN)
Bit 7
PCAN7
-
6
5
4
3
2
1
Bit 0
PORTCAN
$013E
R
TxCAN
RxCAN
PCAN6
PCAN5
-
PCAN4
PCAN3
-
PCAN2
W
RESET
-
-
Port bits 7 to 2 will read zero when configured as inputs because they
are not implemented externally.
When configured as output, port bits 7 to 2 will read the last value
written.
Reading bits 1 and 0 returns the value of the TxCan and RxCan pins,
respectively.
m sCAN12 Port CAN Da ta Dire c tion Re g iste r (DDRCAN)
Bit 7
DDCAN7
0
6
DDCAN6
0
5
DDCAN5
0
4
DDCAN4
0
3
DDCAN3
0
2
DDCAN2
0
1
0
Bit 0
0
DDRCAN
$013F
R
W
RESET
0
0
DDCAN7 – DDCAN2 — This bits served as memory locations since
there are no corresponding external port pins.
42-mscan12
MC68HC912DT128A Rev 2.0
310
MSCAN Controller
MOTOROLA
Ana log -To-Dig ita l Conve rte r (ATD)
Ana log -To-Dig ita l Conve rte r
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Functional Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
ATD Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
ATD Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Introd uc tion
The MC68HC912DT128A has two identical ATD modules identified as
ATD0 and ATD1. Except for the VDDA and VSSA Analog supply voltage,
all pins are duplicated and indexed with ‘0’ or ‘1’ in the following
description. An ‘x’ indicates either ‘0’ or ‘1’.
The ATD module is an 8-channel, 10-bit or 8-bit, multiplexed-input
successive-approximation analog-to-digital converter. It does not
require external sample and hold circuits because of the type of charge
redistribution technique used. The ATD converter timing can be
synchronized to the system P clock. The ATD module consists of a
16-word (32-byte) memory-mapped control register block used for
control, testing and configuration.
1-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
311
Ana log -To-Dig ita l Conve rte r (ATD)
V
RHx
RC DAC ARRAY
AND COMPARATOR
REFERENCE
SUPPLY
V
RLx
V
DDA
V
SSA
SAR
ANx7/PADx7
ANx6/PADx6
ANx5/PADx5
ANx4/PADx4
ANx3/PADx3
ANx2/PADx2
ANx1/PADx1
ANx0/PADx0
ATD 0
ATD 1
ATD 2
ATD 3
ATD 4
ATD 5
ATD 6
ATD 7
ANALOG MUX
AND
SAMPLE BUFFER AMP
PORT AD
DATA INPUT REGISTER
CLOCK
SELECT/PRESCALE
INTERNAL BUS
HC12 ATD BLOCK
Figure 58 Analog-to-Digital Converter Block Diagram
Func tiona l De sc rip tion
A single conversion sequence consists of four or eight conversions,
depending on the state of the select 8 channel mode (S8CM) bit when
ATDCTL5 is written. There are eight basic conversion modes. In the
non-scan modes, the SCF bit is set after the sequence of four or eight
conversions has been performed and the ATD module halts. In the scan
modes, the SCF bit is set after the first sequence of four or eight
conversions has been performed, and the ATD module continues to
restart the sequence. In both modes, the CCF bit associated with each
register is set when that register is loaded with the appropriate
conversion result. That flag is cleared automatically when that result
register is read. The conversions are started by writing to the control
registers.
2--atd
MC68HC912DT128A Rev 2.0
312
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Registers
ATD Re g iste rs
Control and data registers for the ATD modules are described below.
Both ATDs have identical control registers mapped in two blocks of 16
bytes.
ATD0CTL0/ATD1CTL0 — Reserved
$0060/$01E0
Bit 7
6
5
0
4
0
3
0
2
0
1
0
Bit 0
0
RESET:
0
0
Writes to this register will abort current conversion sequence.
Read or write any time.
ATD0CTL1/ATD1CTL1 — Reserved
$0061/$01E1
Bit 7
6
5
0
4
0
3
0
2
0
1
0
Bit 0
0
RESET:
0
0
WRITE: Write to this register has no meaning.
READ: Special Mode only.
ATD0CTL2/ATD1CTL2 — ATD Control Register 2
$0062/$01E2
Bit 7
ADPU
0
6
AFFC
0
5
ASWAI
0
4
DJM
0
3
DSGN
0
2
Reserved
0
1
ASCIE
0
Bit 0
ASCIF
0
RESET:
Writes to these registers abort any current conversion sequence.
Read or write anytime except ASCIF bit, which cannot be written.
ADPU — ATD Disable
0 = Disables the ATD, including the analog section for reduction in
power consumption.
1 = Allows the ATD to function normally.
3-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
313
Ana log -To-Dig ita l Conve rte r (ATD)
Software can disable the clock signal to the A/D converter and power
down the analog circuits to reduce power consumption. When reset
to zero, the ADPU bit aborts any conversion sequence in progress.
Because the bias currents to the analog circuits are turned off, the
ATD requires a period of recovery time to stabilize the analog circuits
after setting the ADPU bit.
AFFC — ATD Fast Flag Clear All
0 = ATD flag clearing operates normally (read the status register
before reading the result register to clear the associated CCF
bit).
1 = Changes all ATD conversion complete flags to a fast clear
sequence. Any access to a result register (ATD0–7) will cause
the associated CCF flag to clear automatically if it was set at
the time.
ASWAI — ATD Stops in Wait Mode
0 = ATD continues to run when the MCU is in wait mode
1 = ATD stops to save power when the MCU is in wait mode
When the ASWAI bit is set and the module enters wait mode, most of the
clocks stop and the analog portion powers down. When the module
comes out of wait, it is recommended that a stabilization delay (stop and
ATD power up recovery time, tSR) is allowed before new conversions are
started. Additionally, the ATD does not re-initialize automatically on
leaving wait mode.
DJM — Result Register Data Justification Mode
0 = Left justified
1 = Right justified
For 10-bit resolution, left justified mode maps a result register
into data bus bits 6 through 15; bit 15 is the MSB. In right justified
mode, the result registers maps onto data bus bits 0 through 9;
bit 9 is the MSB.
For 8-bit resolution, left justified mode maps a result into the high
byte (bits 8 though 15; bit 15 is the MSB). Right justified maps a
result into the low byte (bits 0 through 7; bit 7 is the MSB).
4-atd
MC68HC912DT128A Rev 2.0
314
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Registers
DSGN — Signed/Unsigned Result Data Mode
0 = Unsigned result register data
1 = Signed result register data
Note that signed data is not available for right justified data.
Therefore, sign extension hardware is not required.
Table 47 summarizes the result data formats available and how they
are set up using the control bits. Table 48 illustrates the difference
between the signed and unsigned, left justified output codes for an
input signal range between 0 and 5.1 Volts.
Result Data Formats
Description and Bus Bit Mapping
SRES10
DJM
DSGN
0
0
0
1
1
1
0
0
1
0
0
1
0
1
X
0
1
X
8-bit/left justified/unsign - bits 8-15
8-bit/ left justified/signed - bits 8-15
8-bit/right justified/unsign - bits 0-7
10-bit/left justified/unsign - bits 6-15
10-bit/left justified/signed - bits 6-15
10-bit/right justified/unsign - bits 0-9
Table 47 Result Data Formats Available.
Input Signal
Vrl = 0 Volts
Vrh = 5.12 Volts
Signed
8-Bit
Codes
Unsigned
8-Bit
Codes
Signed
10-Bit
Codes
Unsigned
10-Bit
Codes
5.120 Volts
5.100
7F
7F
7E
FF
FF
FE
7FC0
7F00
7E00
FFC0
FF00
FE00
5.080
2.580
2.560
2.540
01
00
FF
81
80
7F
0100
0000
FF00
8100
8000
7F00
0.020
0.000
81
80
01
00
8100
8000
0100
0000
Table 48 Left Justified, Signed and Unsigned ATD Output Codes.
ASCIE — ATD Sequence Complete Interrupt Enable
0 = Disables ATD interrupt
1 = Enables ATD interrupt on sequence complete
5-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
315
Ana log -To-Dig ita l Conve rte r (ATD)
ASCIF — ATD Sequence Complete Interrupt Flag
Cannot be written in any mode.
0 = No ATD interrupt occurred
1 = ATD sequence complete
ATD0CTL3/ATD1CTL3 — ATD Control Register 3
$0063/$01E3
Bit 7
6
0
0
5
0
0
4
0
0
3
S1C
0
2
FIFO
0
1
FRZ1
0
Bit 0
FRZ0
0
0
0
RESET:
Read or write any time.
S1C — Conversion Sequence Length (Least Significant Bit)
This control bit works with control bit S8C in ATDCTL5 in determining
how many conversion are performed per sequence. When the S1C bit
is set, a sequence length of 1 is defined. However, if the S8C bit is
also set, the S8C bit takes precedence. For sequence length coding
information see the description for S8C bit in ATDCTL5.
FIFO — Result Register FIFO Mode
0 = result registers do not map to the conversion sequence
1 = result registers map to the conversion sequence
In normal operation, the A/D conversion results map into the result
registers based on the conversion sequence; the result of the first
conversion appears in the first result register, the second result in the
second result register, and so on. In FIFO mode the result register
counter is not reset at the beginning or ending of a conversion
sequence; conversion results are placed in consecutive result
registers between sequences. The result register counter wraps
around when it reaches the end of the result register file. The
conversion counter value in ATDSTAT0 can be used to determine
where in the result register file, the next conversion result will be
placed.
The results register counter is initialized to zero on three events: on
reset, the beginning of a normal (non-FIFO) conversion sequence,
and the end of a normal (non-FIFO) conversion sequence. Therefore,
the reset bit in register ATDTEST1 can be toggled to zero the result
register counter; any sequence allowed to complete normally will zero
6-atd
MC68HC912DT128A Rev 2.0
316
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Registers
the result register counter; a new sequence (non-FIFO) initiated with
a write to ATDCTL4/5 followed by a write to ATDCTL3 to set the FIFO
bit will start a FIFO sequence with the result register initialized.
Finally, which result registers hold valid data can be tracked using the
conversion complete flags. Fast flag clear mode may or may not be
useful in a particular application to track valid data.
FRZ1, FRZ0 — Background Debug (Freeze) Enable (suspend module
operation at breakpoint)
When debugging an application, it is useful in many cases to have the
ATD pause when a breakpoint is encountered. These two bits
determine how the ATD will respond when background debug mode
becomes active.
Table 49 ATD Response to Background Debug Enable
FRZ1
FRZ0
ATD Response
Continue conversions in active background mode
Reserved
0
0
1
1
0
1
0
1
Finish current conversion, then freeze
Freeze when BDM is active
ATD0CTL4/ATD1CTL4 — ATD Control Register 4
$0064/$01E4
Bit 7
RES10
0
6
SMP1
0
5
SMP0
0
4
PRS4
0
3
PRS3
0
2
PRS2
0
1
PRS1
0
Bit 0
PRS0
1
RESET:
The ATD control register 4 is used to select the clock source and set
up the prescaler. Writes to the ATD control registers initiate a new
conversion sequence. If a write occurs while a conversion is in
progress, the conversion is aborted and ATD activity halts until a write
to ATDCTL5 occurs.
RES10 — 10 bit Mode
0 = 8 bit operation
1 = 1= 10 bit operation
SMP1, SMP0 — Select Sample Time
Used to select one of four sample times after the buffered sample and
transfer has occurred.
7-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
317
Ana log -To-Dig ita l Conve rte r (ATD)
Table 50 Final Sample Time Selection
SMP1 SMP0
Final Sample Time
2 A/D clock periods
4 A/D clock periods
8 A/D clock periods
16 A/D clock periods
0
0
1
1
0
1
0
1
PRS4, PRS3, PRS2, PRS1, PRS0 — Select Divide-By Factor for ATD
P-Clock Prescaler.
The binary value written to these bits (1 to 31) selects the divide-by
factor for the modulo counter-based prescaler. The P clock is divided
by this value plus one and then fed into a ÷2 circuit to generate the
ATD module clock. The divide-by-two circuit insures symmetry of the
output clock signal. Clearing these bits causes the prescale value
default to one which results in a ÷2 prescale factor. This signal is then
fed into the ÷2 logic. The reset state divides the P clock by a total of
four and is appropriate for nominal operation at 2 MHz. Table 51
shows the divide-by operation and the appropriate range of system
clock frequencies.
Table 51 Clock Prescaler Values
Prescale
Value
Total
Divisor
Max P Clock(1)
Min P Clock(2)
00000
00001
00010
00011
00100
00101
00110
00111
01xxx
1xxxx
÷2
÷4
4 MHz
8 MHz
8 MHz
8 MHz
8 MHz
8 MHz
8 MHz
8 MHz
1 MHz
2 MHz
3 MHz
4 MHz
5 MHz
6 MHz
7 MHz
8 MHz
÷6
÷8
÷10
÷12
÷14
÷16
Do Not Use
1. Maximum conversion frequency is 2 MHz. Maximum P clock divisor value will become
maximum conversion rate that can be used on this ATD module.
2. Minimum conversion frequency is 500 kHz. Minimum P clock divisor value will become
minimum conversion rate that this ATD can perform.
8-atd
MC68HC912DT128A Rev 2.0
318
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Registers
ATD0CTL5/ATD1CTL5 — ATD Control Register 5
$0065/$01E5
Bit 7
6
S8CM
0
5
SCAN
0
4
MULT
0
3
CD
0
2
CC
0
1
CB
0
Bit 0
CA
0
0
0
RESET:
The ATD control register 5 is used to select the conversion modes,
the conversion channel(s), and initiate conversions.
Read or write any time. Writes to the ATD control registers initiate a
new conversion sequence. If a conversion sequence is in progress
when a write occurs, that sequence is aborted and the SCF and CCF
bits are reset.
S8C — Conversion Sequence Length (Most Significant Bit)
The S8C/S1C bits define the length of a conversion sequence.
Table 52 lists the coding combinations implemented.
Number of Conversions per
S8C
S1C
Sequence
0
0
1
0
1
X
4
1
8
Table 52 Conversion Sequence Length Coding.
The result register assignments made to a conversion sequence
follow a few simple rules. Normally, the first result is placed in the first
register; the second result is placed in the second register, and so on.
Table 53 presents the result register assignments for the various
conversion lengths that are normally made. If FIFO mode is used, the
result register assignments differ. The results are placed in
consecutive registers between conversion sequences; the result
register mapping wraps around when the end of the register file is
reached.
9-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
319
Ana log -To-Dig ita l Conve rte r (ATD)
Number of Conversions
Result Register
Assignment
per Sequence
1
4
8
ADR0
ADR0 through ADR3
ADR0 through ADR7
Table 53 Result Register Assignment for Different Conversion
Sequences.
SCAN — Enable Continuous Channel Scan
0 = Single conversion sequence
1 = Continuous conversion sequences (scan mode)
When a conversion sequence is initiated by a write to the ATDCTL
register, the user has a choice of performing a sequence of four (or
eight, depending on the S8C bit) conversions or continuously
performing four (or eight) conversion sequences.
MULT — Enable Multichannel Conversion
0 = ATD sequencer runs all four or eight conversions on a single
input channel selected via the CD, CC, CB, and CA bits.
1 = ATD sequencer runs each of the four or eight conversions on
sequential channels in a specific group. Refer to Table 54.
10-atd
MC68HC912DT128A Rev 2.0
320
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Registers
CD, CC, CB, and CA — Channel Select for Conversion
Table 54 Multichannel Mode Result Register Assignment
Result in ADRxx
if MULT = 1
S8CM
CD
CC
CB
CA
Channel Signal
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
AN0
AN1
ADRx0
ADRx1
ADRx2
ADRx3
ADRx0
ADRx1
ADRx2
ADRx3
ADRx0
ADRx1
ADRx2
ADRx3
ADRx0
ADRx1
ADRx2
ADRx3
ADRx0
ADRx1
ADRx2
ADRx3
ADRx4
ADRx5
ADRx6
ADRx7
ADRx0
ADRx1
ADRx2
ADRx3
ADRx4
ADRx5
ADRx6
ADRx7
0
0
0
AN2
AN3
AN4
AN5
0
0
0
0
1
1
1
0
1
0
1
0
1
AN6
AN7
Reserved
Reserved
Reserved
Reserved
VRH
VRL
(VRH + VRL)/2
TEST/Reserved
AN0
AN1
AN2
AN3
1
0
AN4
AN5
AN6
AN7
Reserved
Reserved
Reserved
Reserved
VRH
1
1
VRL
(VRH + VRL)/2
TEST/Reserved
Shaded bits are “don’t care” if MULT = 1 and the entire block of four or eight channels make up
a conversion sequence. When MULT = 0, all four bits (CD, CC, CB, and CA) must be specified
and a conversion sequence consists of four or eight consecutive conversions of the single spec-
ified channel.
11-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
321
Ana log -To-Dig ita l Conve rte r (ATD)
ATD0STAT0/ATD1STAT0 — ATD Status Register
$0066/$01E6
$0067/$01E7
Bit 7
SCF
0
6
0
0
5
0
0
4
0
0
3
0
0
2
CC2
0
1
CC1
0
Bit 0
CC0
0
RESET:
ATD0STAT1/ATD1STAT1 — ATD Status Register
Bit 7
CCF7
0
6
CCF6
0
5
CCF5
0
4
CCF4
0
3
CCF3
0
2
CCF2
0
1
CCF1
0
Bit 0
CCF0
0
RESET:
The ATD status registers contain the flags indicating the completion of
ATD conversions.
Normally, it is read-only. In special mode, the SCF bit and the CCF bits
may also be written.
SCF — Sequence Complete Flag
This bit is set at the end of the conversion sequence when in the
single conversion sequence mode (SCAN = 0 in ATDCTL5) and is set
at the end of the first conversion sequence when in the continuous
conversion mode (SCAN = 1 in ATDCTL5). When AFFC = 0, SCF is
cleared when a write is performed to ATDCTL5 to initiate a new
conversion sequence. When AFFC = 1, SCF is cleared after the first
result register is read.
CC[2:0] — Conversion Counter for Current Sequence of Four or Eight
Conversions
This 3-bit value reflects the contents of the conversion counter pointer
in a four or eight count sequence. This value also reflects which result
register will be written next, indicating which channel is currently
being converted.
CCF[7:0] — Conversion Complete Flags
Each of these bits are associated with an individual ATD result
register. For each register, this bit is set at the end of conversion for
the associated ATD channel and remains set until that ATD result
register is read. It is cleared at that time if AFFC bit is set, regardless
of whether a status register read has been performed (i.e., a status
12-atd
MC68HC912DT128A Rev 2.0
322
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Registers
register read is not a pre-qualifier for the clearing mechanism when
AFFC = 1). Otherwise the status register must be read to clear the
flag.
ATD0TESTH/ATD1TESTH — ATD Test Register
$0068/$01E8
Bit 7
SAR9
0
6
SAR8
0
5
SAR7
0
4
SAR6
0
3
SAR5
0
2
SAR4
0
1
SAR3
0
Bit 0
SAR2
0
RESET:
ATD0TESTL/ATD1TESTL — ATD Test Register
$0069/$01E9
Bit 7
SAR1
0
6
SAR0
0
5
RST
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 0
0
0
RESET:
The test registers control various special modes which are used
during manufacturing. The test register can be read or written only in
the special modes. In the normal modes, reads of the test register
return zero and writes have no effect.
SAR[9:0] — SAR Data
Reads of this byte return the current value in the SAR. Writes to this
byte change the SAR to the value written. Bits SAR[9:0] reflect the ten
SAR bits used during the resolution process for a 10-bit result.
RST — Module Reset Bit
When set, this bit causes all registers and activity in the module to
assume the same state as out of power-on reset (except for ADPU bit
in ATDCTL2, which remains set, allowing the ATD module to remain
enabled).
13-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
323
Ana log -To-Dig ita l Conve rte r (ATD)
PORTAD0/PORTAD1 — Port AD Data Input Register
$006F/$01EF
Bit 7
PADx7
-
6
PADx6
-
5
PADx5
-
4
PADx4
-
3
PADx3
-
2
PADx2
-
1
PADx1
-
Bit 0
PADx0
-
RESET:
PADx[7:0] — Port AD Data Input Bits
After reset these bits reflect the state of the input pins.
May be used for general-purpose digital input. When the software
reads PORTAD, it obtains the digital levels that appear on the
corresponding port AD pins. Pins with signals not meeting VIL or VIH
specifications will have an indeterminate value. Writes to this register
have no meaning at any time.
ADRx0H — A/D Converter Result Register 0
ADRx0L — A/D Converter Result Register 0
ADRx1H — A/D Converter Result Register 1
ADRx1L — A/D Converter Result Register 1
ADRx2H — A/D Converter Result Register 2
ADRx2L — A/D Converter Result Register 2
ADRx3H — A/D Converter Result Register 3
ADRx3L — A/D Converter Result Register 3
ADRx4H — A/D Converter Result Register 4
ADRx4L — A/D Converter Result Register 4
ADRx5H — A/D Converter Result Register 5
ADRx5L — A/D Converter Result Register 5
ADRx6H — A/D Converter Result Register 6
ADRx6L — A/D Converter Result Register 6
ADRx7H — A/D Converter Result Register 7
ADRx7L — A/D Converter Result Register 7
$0070/$01F0
$0071/$01F1
$0072/$01F2
$0073/$01F3
$0074/$01F4
$0075/$01F5
$0076/$01F6
$0077/$01F7
$0078/$01F8
$0079/$01F9
$007A/$01FA
$007B/$01FB
$007C/$01FC
$007D/$01FD
$007E/$01FE
$007F/$01FF
ADRxxH
ADRxxL
RESET:
Bit 15
Bit 7
0
6
Bit 6
0
5
0
0
4
0
0
3
0
0
2
0
0
1
0
0
Bit 8
0
0
ADRxxH[15:8], ADRxxL[7:0] — ATD Conversion result
The reset condition for these registers is undefined.
These bits contain the left justified, unsigned result from the ATD
conversion. The channel from which this result was obtained is
dependent on the conversion mode selected. These registers are
always read-only in normal mode.
14-atd
MC68HC912DT128A Rev 2.0
324
Analog-To-Digital Converter (ATD)
MOTOROLA
Analog-To-Digital Converter (ATD)
ATD Mode Operation
ATD Mod e Op e ra tion
STOP — causes all clocks to halt (if the S bit in the CCR is zero). The
system is placed in a minimum-power standby mode. This aborts any
conversion sequence in progress.
WAIT — ATD conversion continues unless AWAI bit in ATDCTL2
register is set.
BDM — Debug options available as set in register ATDCTL3.
USER — ATD continues running unless ADPU is cleared.
ADPU — ATD operations are stopped if ADPU = 0, but registers are
accessible.
15-atd
MC68HC912DT128A Rev 2.0
MOTOROLA
Analog-To-Digital Converter (ATD)
325
Ana log -To-Dig ita l Conve rte r (ATD)
16-atd
MC68HC912DT128A Rev 2.0
326
Analog-To-Digital Converter (ATD)
MOTOROLA
De ve lop m e nt Sup p ort
De ve lop m e nt Sup p ort
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Instruction Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Background Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Instruction Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Introd uc tion
Development support involves complex interactions between
MC68HC912DT128A resources and external development systems.
The following section concerns instruction queue and queue tracking
signals, background debug mode, and instruction tagging.
Instruc tion Que ue
The CPU12 instruction queue provides at least three bytes of program
information to the CPU when instruction execution begins. The CPU12
always completely finishes executing an instruction before beginning to
execute the next instruction. Status signals IPIPE[1:0] provide
information about data movement in the queue and indicate when the
CPU begins to execute instructions. This makes it possible to monitor
CPU activity on a cycle-by-cycle basis for debugging. Information
available on the IPIPE[1:0] pins is time multiplexed. External circuitry
can latch data movement information on rising edges of the E-clock
signal; execution start information can be latched on falling edges.
Table 55 shows the meaning of data on the pins.
1-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
327
De ve lop m e nt Sup p ort
Table 55 IPIPE Decoding
Data Movement — IPIPE[1:0] Captured at Rising Edge of E Clock(1)
IPIPE[1:0]
0:0
Mnemonic
—
Meaning
No Movement
0:1
LAT
Latch Data From Bus
1:0
ALD
Advance Queue and Load From Bus
Advance Queue and Load From Latch
1:1
ALL
Execution Start — IPIPE[1:0] Captured at Falling Edge of E Clock(2)
IPIPE[1:0]
0:0
Mnemonic
—
Meaning
No Start
0:1
INT
Start Interrupt Sequence
Start Even Instruction
Start Odd Instruction
1:0
SEV
1:1
SOD
1. Refers to data that was on the bus at the previous E falling edge.
2. Refers to bus cycle starting at this E falling edge.
Program information is fetched a few cycles before it is used by the CPU.
In order to monitor cycle-by-cycle CPU activity, it is necessary to
externally reconstruct what is happening in the instruction queue.
Internally the MCU only needs to buffer the data from program fetches.
For system debug it is necessary to keep the data and its associated
address in the reconstructed instruction queue. The raw signals required
for reconstruction of the queue are ADDR, DATA, R/W, ECLK, and
status signals IPIPE[1:0].
The instruction queue consists of two 16-bit queue stages and a holding
latch on the input of the first stage. To advance the queue means to
move the word in the first stage to the second stage and move the word
from either the holding latch or the data bus input buffer into the first
stage. To start even (or odd) instruction means to execute the opcode in
the high-order (or low-order) byte of the second stage of the instruction
queue.
2--dev
MC68HC912DT128A Rev 2.0
328
Development Support
MOTOROLA
Development Support
Background Debug Mode
Ba c kg round De b ug Mod e
Background debug mode (BDM) is used for system development,
in-circuit testing, field testing, and programming. BDM is implemented in
on-chip hardware and provides a full set of debug options.
Because BDM control logic does not reside in the CPU, BDM hardware
commands can be executed while the CPU is operating normally. The
control logic generally uses CPU dead cycles to execute these
commands, but can steal cycles from the CPU when necessary. Other
BDM commands are firmware based, and require the CPU to be in
active background mode for execution. While BDM is active, the CPU
executes a firmware program located in a small on-chip ROM that is
available in the standard 64-Kbyte memory map only while BDM is
active.
The BDM control logic communicates with an external host development
system serially, via the BKGD pin. This single-wire approach minimizes
the number of pins needed for development support.
Ena b ling BDM
Firm wa re
Com m a nd s
BDM is available in all operating modes, but must be made active before
firmware commands can be executed. BDM is enabled by setting the
ENBDM bit in the BDM STATUS register via the single wire interface
(using a hardware command; WRITE_BD_BYTE at $FF01). BDM must
then be activated to map BDM registers and ROM to addresses $FF00
to $FFFF and to put the MCU in active background mode.
After the firmware is enabled, BDM can be activated by the hardware
BACKGROUND command, by the BDM tagging mechanism, or by the
CPU BGND instruction. An attempt to activate BDM before firmware has
been enabled causes the MCU to resume normal instruction execution
after a brief delay.
BDM becomes active at the next instruction boundary following
execution of the BDM BACKGROUND command, but tags activate BDM
before a tagged instruction is executed.
3-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
329
De ve lop m e nt Sup p ort
In special single-chip mode, background operation is enabled and active
immediately out of reset. This active case replaces the M68HC11 boot
function, and allows programming a system with blank memory.
While BDM is active, a set of BDM control registers are mapped to
addresses $FF00 to $FF06. The BDM control logic uses these registers
which can be read anytime by BDM logic, not user programs. Refer to
BDM Registers for detailed descriptions.
Some on-chip peripherals have a BDM control bit which allows
suspending the peripheral function during BDM. For example, if the timer
control is enabled, the timer counter is stopped while in BDM. Once
normal program flow is continued, the timer counter is re-enabled to
simulate real-time operations.
BDM Se ria l
Inte rfa c e
The BDM serial interface requires the external controller to generate a
falling edge on the BKGD pin to indicate the start of each bit time. The
external controller provides this falling edge whether data is transmitted
or received.
BKGD is a pseudo-open-drain pin that can be driven either by an
external controller or by the MCU. Data is transferred MSB first at 16
BCLK cycles per bit (nominal speed). The interface times out if 512
BCLK cycles occur between falling edges from the host. The hardware
clears the command register when a time-out occurs.
The BKGD pin can receive a high or low level or transmit a high or low
level. The following diagrams show timing for each of these cases.
Interface timing is synchronous to MCU clocks but asynchronous to the
external host. The internal clock signal is shown for reference in counting
cycles.
Figure 59 shows an external host transmitting a logic one or zero to the
BKGD pin of a target MC68HC912DT128A MCU. The host is
asynchronous to the target so there is a 0-to-1 cycle delay from the
host-generated falling edge to where the target perceives the beginning
of the bit time. Ten target B cycles later, the target senses the bit level
on the BKGD pin. Typically the host actively drives the
pseudo-open-drain BKGD pin during host-to-target transmissions to
4-dev
MC68HC912DT128A Rev 2.0
330
Development Support
MOTOROLA
Development Support
Background Debug Mode
speed up rising edges. Since the target does not drive the BKGD pin
during this period, there is no need to treat the line as an open-drain
signal during host-to-target transmissions.
BCLK
(TARGET MCU)
HOST
TRANSMIT 1
HOST
TRANSMIT 0
PERCEIVED
START
TARGET SENSES BIT
OF BIT TIME
EARLIEST
START OF
NEXT BIT
10 CYCLES
SYNCHRONIZATION
UNCERTAINTY
HC12A4 BDM HOST TO TARGET TIM
Figure 59 BDM Host to Target Serial Bit Timing
BCLK
(TARGET
MCU)
HOST
DRIVE TO
BKGD PIN
HIGH-IMPEDANCE
TARGET MCU
SPEEDUP PULSE
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
HC12A4 BDM TARGET TO HOST TIM 1
Figure 60 BDM Target to Host Serial Bit Timing (Logic 1)
5-dev
MC68HC912DT128A Rev 2.0
331
MOTOROLA
Development Support
De ve lop m e nt Sup p ort
Figure 60 shows the host receiving a logic one from the target
MC68HC912DT128A MCU. Since the host is asynchronous to the target
MCU, there is a 0-to-1 cycle delay from the host-generated falling edge
on BKGD to the perceived start of the bit time in the target MCU. The
host holds the BKGD pin low long enough for the target to recognize it
(at least two target B cycles). The host must release the low drive before
the target MCU drives a brief active-high speed-up pulse seven cycles
after the perceived start of the bit time. The host should sample the bit
level about ten cycles after it started the bit time.
BCLK
(TARGET
MCU)
HOST
DRIVE TO
BKGD PIN
HIGH-IMPEDANCE
SPEEDUP PULSE
TARGET MCU
DRIVE AND
SPEEDUP PULSE
PERCEIVED
START OF BIT TIME
BKGD PIN
10 CYCLES
10 CYCLES
EARLIEST
START OF
NEXT BIT
HOST SAMPLES
BKGD PIN
HC12A4 BDM TARGET TO HOST TIM 0
Figure 61 BDM Target to Host Serial Bit Timing (Logic 0)
Figure 61 shows the host receiving a logic zero from the target
MC68HC912DT128A MCU. Since the host is asynchronous to the target
MCU, there is a 0-to-1 cycle delay from the host-generated falling edge
on BKGD to the start of the bit time as perceived by the target MCU. The
host initiates the bit time but the target MC68HC912DT128A finishes it.
Since the target wants the host to receive a logic zero, it drives the
BKGD pin low for 13 BCLK cycles, then briefly drives it high to speed up
the rising edge. The host samples the bit level about ten cycles after
starting the bit time.
6-dev
MC68HC912DT128A Rev 2.0
332
Development Support
MOTOROLA
Development Support
Background Debug Mode
BDM Com m a nd s
The BDM command set consists of two types: hardware and firmware.
Hardware commands allow target system memory to be read or
written.Target system memory includes all memory that is accessible by
the CPU12 including EEPROM, on-chip I/O and control registers, and
external memory that is connected to the target HC12 MCU.Hardware
commands are implemented in hardware logic and do not require the
HC12 MCU to be in BDM mode for execution.The control logic watches
the CPU12 buses to find a free bus cycle to execute the command so the
background access does not disturb the running application programs. If
a free cycle is not found within 128 BCLK cycles, the CPU12 is
momentarily frozen so the control logic can steal a cycle.Commands
implemented in BDM control logic are listed in Table 56.
Table 56 Hardware Commands(1)
Command
Opcode (Hex)
Data
Description
BACKGROUND
90
None
Enter background mode if firmware enabled.
Read from memory with BDM in map (may steal cycles
if external access) data for odd address on low byte,
data for even address on high byte.
16-bit address
16-bit data out
READ_BD_BYTE(1)
READ_BD_WORD(1)
READ_BYTE
E4
EC
E0
E8
C4
CC
C0
C8
16-bit address Read from memory with BDM in map (may steal cycles
16-bit data out if external access). Must be aligned access.
Read from memory with BDM out of map (may steal
16-bit address
cycles if external access) data for odd address on low
16-bit data out
byte, data for even address on high byte.
16-bit address Read from memory with BDM out of map (may steal
16-bit data out cycles if external access). Must be aligned access.
READ_WORD
Write to memory with BDM in map (may steal cycles if
16-bit address
WRITE_BD_BYTE(1)
WRITE_BD_WORD(1)
WRITE_BYTE
external access) data for odd address on low byte, data
16-bit data in
for even address on high byte.
16-bit address Write to memory with BDM in map (may steal cycles if
16-bit data in external access). Must be aligned access.
Write to memory with BDM out of map (may steal
16-bit address
cycles if external access) data for odd address on low
16-bit data in
byte, data for even address on high byte.
16-bit address Write to memory with BDM out of map (may steal
16-bit data in cycles if external access). Must be aligned access.
WRITE_WORD
1. Use these commands only for reading/writing to BDM locations.The BDM firmware ROM and BDM registers are not nor-
mally in the HC12 MCU memory map.Since these locations have the same addresses as some of the normal application
memory map, there needs to be a way to decide which physical locations are being accessed by the hardware BDM com-
mands.This gives rise to needing separate memory access commands for the BDM locations as opposed to the normal
application locations.In logic, this is accomplished by momentarily enabling the BDM memory resources, just for the ac-
cess cycles of the READ_BD and WRITE_BD commands.This logic allows the debugging system to unobtrusively access
the BDM locations even if the application program is running out of the same memory area in the normal application mem-
ory map.
7-dev
MC68HC912DT128A Rev 2.0
333
MOTOROLA
Development Support
De ve lop m e nt Sup p ort
The second type of BDM commands are called firmware commands
implemented in a small ROM within the HC12 MCU.The CPU must be in
background mode to execute firmware commands. The usual way to get
to background mode is by the hardware command BACKGROUND. The
BDM ROM is located at $FF20 to $FFFF while BDM is active. There are
also seven bytes of BDM registers located at $FF00 to $FF06 while BDM
is active. The CPU executes code in the BDM firmware to perform the
requested operation. The BDM firmware watches for serial commands
and executes them as they are received. The firmware commands are
shown in Table 57.
Table 57 BDM Firmware Commands
Command
READ_NEXT
READ_PC
READ_D
Opcode (Hex)
Data
Description
X = X + 2; Read next word pointed to by X
Read program counter
62
63
64
65
66
67
42
43
44
45
46
47
08
10
18
16-bit data out
16-bit data out
16-bit data out
16-bit data out
16-bit data out
16-bit data out
16-bit data in
16-bit data in
16-bit data in
16-bit data in
16-bit data in
16-bit data in
None
Read D accumulator
READ_X
Read X index register
READ_Y
Read Y index register
READ_SP
WRITE_NEXT
WRITE_PC
WRITE_D
WRITE_X
WRITE_Y
WRITE_SP
GO
Read stack pointer
X = X + 2; Write next word pointed to by X
Write program counter
Write D accumulator
Write X index register
Write Y index register
Write stack pointer
Go to user program
TRACE1
None
Execute one user instruction then return to BDM
Enable tagging and go to user program
TAGGO
None
Each of the hardware and firmware BDM commands start with an 8-bit
command code (opcode). Depending upon the commands, a 16-bit
address and/or a 16-bit data word is required as indicated in the tables
by the command. All the read commands output 16-bits of data despite
the byte/word implication in the command name.
The external host should wait 150 BCLK cycles for a non-intrusive BDM
command to execute before another command is sent. This delay
includes 128 BCLK cycles for the maximum delay for a free cycle.For
data read commands, the host must insert this delay between sending
8-dev
MC68HC912DT128A Rev 2.0
334
Development Support
MOTOROLA
Development Support
Background Debug Mode
the address and attempting to read the data.In the case of a write
command, the host must delay after the data portion, before sending a
new command, to be sure the write has finished.
The external host should delay about 32 target BCLK cycles between a
firmware read command and the data portion of these commands. This
allows the BDM firmware to execute the instructions needed to get the
requested data into the BDM SHIFTER register.
The external host should delay about 32 target BCLK cycles after the
data portion of firmware write commands to allow BDM firmware to
complete the requested write operation before a new serial command
disturbs the BDM SHIFTER register.
The external host should delay about 64 target BCLK cycles after a
TRACE1 or GO command before starting any new serial command. This
delay is needed because the BDM SHIFTER register is used as a
temporary data holding register during the exit sequence to user code.
BDM logic retains control of the internal buses until a read or write is
completed.If an operation can be completed in a single cycle, it does not
intrude on normal CPU12 operation.However, if an operation requires
multiple cycles, CPU12 clocks are frozen until the operation is complete.
BDM Loc kout
The access to the MCU resources by BDM may be prevented by
enabling the BDM lockout feature. When enabled, the BDM lockout
mechanism prevents the BDM from being active. In this case the BDM
ROM is disabled and does not appear in the MCU memory map.
The BDM lockout is enabled by clearing NOBDML bit of EEMCR
register. The NOBDML bit is loaded at reset from the SHADOW word of
EEPROM module. Modifying the state of the NOBDML and
corresponding EEPROM SHADOW bit is only possible in special modes.
Please refer to EEPROM for NOBDML information.
9-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
335
De ve lop m e nt Sup p ort
Ena b ling the BDM
lo c ko ut
Enabling the BDM lockout feature is only possible in special modes
(SMODN=0) and is accomplished by the following steps.
1. Remove the SHADOW word protection by clearing SHPROT bit in
EEPROT register.
2. Clear NOSHW bit in EEMCR register to make the SHADOW word
visible at $0FC0-$0FC1.
3. Program bit 7 of the high byte of the SHADOW word like a regular
EEPROM location at address $0FC0 (write $7F into address
$0FC0). Do not program other bits of the high byte of the
SHADOW word (location $0FC0); otherwise some regular
EEPROM array locations will not be visible. At the next reset, the
high byte of the SHADOW word is loaded into the EEMCR
register. NOBDML bit in EEMCR will be cleared and BDM will not
be operational.
4. Protect the SHADOW word by setting SHPROT bit in EEPROT
register.
Disa b ling the BDM
lo c ko ut
Disabling the BDM lockout is only possible in special modes
(SMODN=0) except in special single chip. Follow the same steps as for
enabling the BDM lockout, but erase the SHADOW word.
At the next reset, the high byte of SHADOW word is loaded into the
EEMCR register. NOBDML bit in EEMCR will be set and BDM becomes
operational.
NOTE: When the BDM lockout is enabled it is not possible to run code from the
reset vector in special single chip mode.
BDM Re g iste rs
Seven BDM registers are mapped into the standard 64-Kbyte address
space when BDM is active. Mapping is shown in Table 58.
Table 58 BDM registers
Address
$FF00
Register
BDM Instruction Register
BDM Status Register
$FF01
10-dev
MC68HC912DT128A Rev 2.0
336
Development Support
MOTOROLA
Development Support
Background Debug Mode
Table 58 BDM registers
Address
Register
$FF02 - $FF03
$FF04 - $FF05
$FF06
BDM Shift Register
BDM Address Register
BDM CCR Holding Register
The content of the INSTRUCTION register is determined by the type of
background command being executed.The STATUS register indicates
BDM operating conditions.The SHIFT register contains data being
received or transmitted via the serial interface. The ADDRESS register
is temporary storage for BDM commands.The CCRSAV register
preserves the content of the CPU12 CCR while BDM is active.
The only registers of interest to users are the STATUS register and the
CCRSAV register.The other BDM registers are only used by the BDM
firmware to execute commands.The registers are accessed by means of
the hardware READ_BD and WRITE_BD commands, but should not be
written during BDM operation (except the CCRSAV register which could
be written to modify the CCR value).
STATUS
The STATUS register is read and written by the BDM hardware as a
result of serial data shifted in on the BKGD pin.
Read: all modes.
Write: Bits 3 through 5, and bit 7 are writable in all modes. Bit 6,
BDMACT, can only be written if bit 7 H/F in the INSTRUCTION register
is a zero. Bit 2, CLKSW, can only be written if bit 7 H/F in the
INSTRUCTION register is a one. A user would never write ones to bits
3 through 5 because these bits are only used by BDM firmware.
(1)
STATUS— BDM Status Register
$FF01
BIT 7
6
5
4
3
2
1
-
BIT 0
-
ENBDM
BDMACT
ENTAG
SDV
TRACE
CLKSW
Special Single
Chip & Periph
0
RESET:
RESET:
1
0
0
0
0
0
0
0
0
0
0
0
0
0
(NOTE 1)
0
All other modes
11-dev
MC68HC912DT128A Rev 2.0
337
MOTOROLA
Development Support
De ve lop m e nt Sup p ort
1. ENBDM is set to 1 by the firmware in Special Single Chip mode.
ENBDM — Enable BDM (permit active background debug mode)
0 = BDM cannot be made active (hardware commands still
allowed).
1 = BDM can be made active to allow firmware commands.
BDMACT — Background Mode Active Status
BDMACT becomes set as active BDM mode is entered so that the
BDM firmware ROM is enabled and put into the map. BDMACT is
cleared by a carefully timed store instruction in the BDM firmware as
part of the exit sequence to return to user code and remove the BDM
memory from the map. This bit has 4 clock cycles write delay.
0 = BDM is not active. BDM ROM and registers are not in map.
1 = BDM is active and waiting for serial commands. BDM ROM and
registers are in map
The user should be careful that the state of the BDMACT bit is not
unintentionally changed with the WRITE_NEXT firmware command. If it
is unintentionally changed from 1 to 0, it will cause a system runaway
because it would disable the BDM firmware ROM while the CPU12 was
executing BDM firmware. The following two commands show how
BDMACT may unintentionally get changed from 1 to 0.
WRITE_X with data $FEFE
WRITE_NEXT with data $C400
The first command writes the data $FEFE to the X index register. The
second command writes the data $C4 to the $FF00 INSTRUCTION
register and also writes the data $00 to the $FF01 STATUS register.
ENTAG — Tagging Enable
Set by the TAGGO command and cleared when BDM mode is
entered. The serial system is disabled and the tag function enabled
16 cycles after this bit is written.
0 = Tagging not enabled, or BDM active.
1 = Tagging active. BDM cannot process serial commands while
tagging is active.
12-dev
MC68HC912DT128A Rev 2.0
338
Development Support
MOTOROLA
Development Support
Background Debug Mode
SDV — Shifter Data Valid
Shows that valid data is in the serial interface shift register. Used by
the BDM firmware.
0 = No valid data. Shift operation is not complete.
1 = Valid Data. Shift operation is complete.
TRACE — Asserted by the TRACE1 command
CLKSW — Clock Switch
0 = BDM system operates with BCLK.
1 = BDM system operates with ECLK.
The WRITE_BD_BYTE@FF01 command that changes CLKSW
including 150 cycles after the data portion of the command should be
timed at the old speed. Beginning with the start of the next BDM
command, the new clock can be used for timing BDM
communications.
If ECLK rate is slower than BCLK rate, CLKSW is ignored and BDM
system is forced to operate with ECLK.
INSTRUCTION -
Ha rd wa re
Instruc tio n
De c o d e
The INSTRUCTION register is written by the BDM hardware as a result
of serial data shifted in on the BKGD pin. It is readable and writable in
Special Peripheral mode on the parallel bus. It is discussed here for two
conditions: when a hardware command is executed and when a
firmware command is executed.
Read and write: all modes
. The hardware clears the INSTRUCTION register if 512 BCLK cycles
occur between falling edges from the host.
INSTRUCTION— BDM Instruction Register (hardware command explanation)
$FF00
BIT 7
H/F
0
6
DATA
0
5
R/W
0
4
BKGND
0
3
W/B
0
2
BD/U
0
1
0
0
BIT 0
0
0
RESET:
The bits in the BDM instruction register have the following meanings
when a hardware command is executed.
13-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
339
De ve lop m e nt Sup p ort
H/F — Hardware/Firmware Flag
0 = Firmware command
1 = Hardware command
DATA — Data Flag - Shows that data accompanies the command.
0 = No data
1 = Data follows the command
R/W — Read/Write Flag
0 = Write
1 = Read
BKGND — Hardware request to enter active background mode
0 = Not a hardware background command
1 = Hardware background command (INSTRUCTION = $90)
W/B — Word/Byte Transfer Flag
0 = Byte transfer
1 = Word transfer
BD/U — BDM Map/User Map Flag
Indicates whether BDM registers and ROM are mapped to addresses
$FF00 to $FFFF in the standard 64-Kbyte address space. Used only
by hardware read/write commands.
0 = BDM resources not in map
1 = BDM ROM and registers in map
INSTRUCTION — BDM Instruction Register (firmware command bit explanation)
$FF00
Bit 7
H/F
6
5
4
3
2
1
Bit 0
DATA
R/W
TTAGO
REGN
The bits in the BDM instruction register have the following meanings
when a firmware command is executed.
H/F — Hardware/Firmware Flag
0 = Firmware command
1 = Hardware command
DATA — Data Flag – Shows that data accompanies the command.
0 = No data
14-dev
MC68HC912DT128A Rev 2.0
340
Development Support
MOTOROLA
Development Support
Background Debug Mode
1 = Data follows the command
R/W — Read/Write Flag
0 = Write
1 = Read
TTAGO — Trace, Tag, Go Field
Table 59 TTAGO Decoding
TTAGO Value
Instruction
—
00
01
10
11
GO
TRACE1
TAGGO
REGN — Register/Next Field
Indicates which register is being affected by a command. In the case of
a READ_NEXT or WRITE_NEXT command, index register X is
pre-incriminated by 2 and the word pointed to by X is then read or
written.
Table 60 REGN Decoding
REGN Value
000
Instruction
—
001
—
010
READ/WRITE NEXT
011
PC
D
100
101
X
110
Y
111
SP
15-dev
MC68HC912DT128A Rev 2.0
341
MOTOROLA
Development Support
De ve lop m e nt Sup p ort
SHIFTER
This 16-bit shift register contains data being received or transmitted via
the serial interface. It is also used by the BDM firmware for temporary
storage.
Read: all modes (but not normally accessed by users)
Write: all modes (but not normally accessed by users)
SHIFTER — BDM Shift Register – High Byte
$FF02
$FF03
BIT 15
S15
14
13
12
11
10
9
BIT 8
S8
S14
S13
S12
S11
S10
S9
X
X
X
X
X
X
X
X
RESET:
SHIFTER — BDM Shift Register – Low Byte
BIT 7
S7
6
5
4
3
2
1
BIT 0
S0
S6
S5
S4
S3
S2
S1
X
X
X
X
X
X
X
X
RESET:
ADDRESS
This 16-bit address register is temporary storage for BDM hardware and
firmware commands.
Read: all modes (but not normally accessed by users)
Write: only by BDM hardware (state machine)
ADDRESS — BDM Address Register – High Byte
$FF04
$FF05
BIT 15
A15
14
13
12
11
10
9
BIT 8
A8
A14
A13
A12
A11
A10
A9
X
X
X
X
X
X
X
X
RESET:
ADDRESS — BDM Address Register – High Byte
BIT 7
A7
6
5
4
3
2
1
BIT 0
A0
A6
A5
A4
A3
A2
A1
X
X
X
X
X
X
X
X
RESET:
16-dev
MC68HC912DT128A Rev 2.0
342
Development Support
MOTOROLA
Development Support
Breakpoints
CCRSAV
The CCRSAV register is used to save the CCR of the users program
when entering BDM. It is also used for temporary storage in the BDM
firmware.
Read and write: all modes
CCRSAV— BDM CCR Holding Register
$FF06
BIT 7
6
5
4
3
2
1
BIT 0
CCR7
CCR6
CCR5
CCR4
CCR3
CCR2
CCR1
CCR0
RESET:
NOTE 1 (1)
X
X
X
X
X
X
X
X
1. Initialized to equal the CPU12 CCR register by the firmware.
Bre a kp oints
Hardware breakpoints are used to debug software on the
MC68HC912DT128A by comparing actual address and data values to
predetermined data in setup registers. A successful comparison will
place the CPU in background debug mode (BDM) or initiate a software
interrupt (SWI). Breakpoint features designed into the
MC68HC912DT128A include:
•
•
•
•
•
•
•
•
Mode selection for BDM or SWI generation
Program fetch tagging for cycle of execution breakpoint
Second address compare in dual address modes
Range compare by disable of low byte address
Data compare in full feature mode for non-tagged breakpoint
Byte masking for high/low byte data compares
R/W compare for non-tagged compares
Tag inhibit on BDM TRACE
17-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
343
De ve lop m e nt Sup p ort
Bre a kp oint Mod e s
Three modes of operation determine the type of breakpoint in effect.
•
•
•
Dual address-only breakpoints, each of which will cause a
software interrupt (SWI)
Single full-feature breakpoint which will cause the part to enter
background debug mode (BDM)
Dual address-only breakpoints, each of which will cause the part
to enter BDM
Breakpoints will not occur when BDM is active.
SWI Dua l Ad d re ss
Mod e
In this mode, dual address-only breakpoints can be set, each of which
cause a software interrupt. This is the only breakpoint mode which can
force the CPU to execute a SWI. Program fetch tagging is the default in
this mode; data breakpoints are not possible. In the dual mode each
address breakpoint is affected by the BKPM bit and the BKALE bit. The
BKxRW and BKxRWE bits are ignored. In dual address mode the
BKDBE becomes an enable for the second address breakpoint. The
BKSZ8 bit will have no effect when in a dual address mode.
BDM Full
Bre a kp o int Mo d e
A single full feature breakpoint which causes the part to enter
background debug mode. BDM mode may be entered by a breakpoint
only if an internal signal from the BDM indicates background debug
mode is enabled.
•
•
Breakpoints are not allowed if the BDM mode is already active.
Active mode means the CPU is executing out of the BDM ROM.
BDM should not be entered from a breakpoint unless the ENABLE
bit is set in the BDM. This is important because even if the
ENABLE bit in the BDM is negated the CPU actually does execute
the BDM ROM code. It checks the ENABLE and returns if not set.
If the BDM is not serviced by the monitor then the breakpoint
would be re-asserted when the BDM returns to normal CPU flow.
•
There is no hardware to enforce restriction of breakpoint operation
if the BDM is not enabled.
18-dev
MC68HC912DT128A Rev 2.0
344
Development Support
MOTOROLA
Development Support
Breakpoints
BDM Dua l Ad d re ss
Mo d e
Dual address-only breakpoints, each of which cause the part to enter
background debug mode. In the dual mode each address breakpoint is
affected, consistent across modes, by the BKPM bit, the BKALE bit, and
the BKxRW and BKxRWE bits. In dual address mode the BKDBE
becomes an enable for the second address breakpoint. The BKSZ8 bit
will have no effect when in a dual address mode. BDM mode may be
entered by a breakpoint only if an internal signal from the BDM indicates
background debug mode is enabled.
•
•
•
BKDBE will be used as an enable for the second address only
breakpoint.
Breakpoints are not allowed if the BDM mode is already active.
Active mode means the CPU is executing out of the BDM ROM.
BDM should not be entered from a breakpoint unless the ENABLE
bit is set in the BDM. This is important because even if the
ENABLE bit in the BDM is negated the CPU actually does execute
the BDM ROM code. It checks the ENABLE and returns if not set.
If the BDM is not serviced by the monitor then the breakpoint
would be re-asserted when the BDM returns to normal CPU flow.
There is no hardware to enforce restriction of breakpoint operation
if the BDM is not enabled.
Bre a kp oint
Re g iste rs
Breakpoint operation consists of comparing data in the breakpoint
address registers (BRKAH/BRKAL) to the address bus and comparing
data in the breakpoint data registers (BRKDH/BRKDL) to the data bus.
The breakpoint data registers can also be compared to the address bus.
The scope of comparison can be expanded by ignoring the least
significant byte of address or data matches.
The scope of comparison can be limited to program data only by setting
the BKPM bit in breakpoint control register 0.
To trace program flow, setting the BKPM bit causes address comparison
of program data only. Control bits are also available that allow checking
read/write matches.
19-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
345
De ve lop m e nt Sup p ort
BRKCT0 — Breakpoint Control Register 0
$0020
Bit 7
BKEN1
0
6
BKEN0
0
5
BKPM
0
4
0
0
3
BK1ALE
0
2
BK0ALE
0
1
0
0
Bit 0
0
0
RESET:
Read and write anytime.
This register is used to control the breakpoint logic.
BKEN1, BKEN0 — Breakpoint Mode Enable
Table 61 Breakpoint Mode Control
BRKDH/L
BKEN1 BKEN0
Mode Selected
Breakpoints Off
BRKAH/L Usage
R/W
Range
Usage
0
0
1
1
0
1
0
1
—
—
—
—
SWI — Dual Address Mode
BDM — Full Breakpoint Mode
BDM — Dual Address Mode
Address Match
Address Match
Address Match
Address Match
Data Match
Address Match
No
Yes
Yes
Yes
Yes
Yes
BKPM — Break on Program Addresses
This bit controls whether the breakpoint will cause a break on a match
(next instruction boundary) or on a match that will be an executable
opcode. Data and non-executed opcodes cannot cause a break if this
bit is set. This bit has no meaning in SWI dual address mode. The
SWI mode only performs program breakpoints.
0 = On match, break at the next instruction boundary
1 = On match, break if the match is an instruction that will be
executed. This uses tagging as its breakpoint mechanism.
BK1ALE — Breakpoint 1 Range Control
Only valid in dual address mode.
0 = BRKDL will not be used to compare to the address bus.
1 = BRKDL will be used to compare to the address bus.
BK0ALE — Breakpoint 0 Range Control
Valid in all modes.
0 = BRKAL will not be used to compare to the address bus.
20-dev
MC68HC912DT128A Rev 2.0
346
Development Support
MOTOROLA
Development Support
Breakpoints
1 = BRKAL will be used to compare to the address bus.
Table 62 Breakpoint Address Range Control
BK1ALE BK0ALE
Address Range Selected
–
–
0
1
0
1
–
–
Upper 8-bit address only for full mode or dual mode BKP0
Full 16-bit address for full mode or dual mode BKP0
Upper 8-bit address only for dual mode BKP1
Full 16-bit address for dual mode BKP1
BRKCT1 — Breakpoint Control Register 1
$0021
Bit 7
6
BKDBE
0
5
BKMBH
0
4
BKMBL
0
3
BK1RWE
0
2
BK1RW
0
1
BK0RWE
0
Bit 0
BK0RW
0
0
0
RESET:
This register is read/write in all modes.
BKDBE — Enable Data Bus
Enables comparing of address or data bus values using the BRKDH/
L registers.
0 = The BRKDH/L registers are not used in any comparison
1 = The BRKDH/L registers are used to compare address or data
(depending upon the mode selections BKEN1,0)
BKMBH — Breakpoint Mask High
Disables the comparing of the high byte of data when in full breakpoint
mode. Used in conjunction with the BKDBE bit (which should be set)
0 = High byte of data bus (bits 15:8) are compared to BRKDH
1 = High byte is not used to in comparisons
BKMBL — Breakpoint Mask Low
Disables the matching of the low byte of data when in full breakpoint
mode. Used in conjunction with the BKDBE bit (which should be set)
0 = Low byte of data bus (bits 7:0) are compared to BRKDL
1 = Low byte is not used to in comparisons.
21-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
347
De ve lop m e nt Sup p ort
BK1RWE — R/W Compare Enable
Enables the comparison of the R/W signal to further specify what
causes a match. This bit is NOT useful in program breakpoints or in
full breakpoint mode. This bit is used in conjunction with a second
address in dual address mode when BKDBE=1.
0 = R/W is not used in comparisons
1 = R/W is used in comparisons
BK1RW — R/W Compare Value
When BK1RWE = 1, this bit determines the type of bus cycle to
match.
0 = A write cycle will be matched
1 = A read cycle will be matched
BK0RWE — R/W Compare Enable
Enables the comparison of the R/W signal to further specify what
causes a match. This bit is not useful in program breakpoints.
0 = R/W is not used in the comparisons
1 = R/W is used in comparisons
BK0RW — R/W Compare Value
When BK0RWE = 1, this bit determines the type of bus cycle to match
on.
0 = Write cycle will be matched
1 = Read cycle will be matched
Table 63 Breakpoint Read/Write Control
BK1RWE BK1RW BK0RWE BK0RW
Read/Write Selected
R/W is don’t care for full mode or dual mode
BKP0
–
–
0
X
–
–
0
1
1
–
–
X
0
1
1
1
–
–
–
0
1
–
–
–
R/W is write for full mode or dual mode BKP0
R/W is read for full mode or dual mode BKP0
R/W is don’t care for dual mode BKP1
R/W is write for dual mode BKP1
R/W is read for dual mode BKP1
22-dev
MC68HC912DT128A Rev 2.0
348
Development Support
MOTOROLA
Development Support
Breakpoints
BRKAH — Breakpoint Address Register, High Byte
$0022
Bit 7
Bit 15
0
6
14
0
5
13
0
4
12
0
3
11
0
2
10
0
1
9
0
Bit 0
Bit 8
0
RESET:
These bits are used to compare against the most significant byte of the
address bus.
BRKAL — Breakpoint Address Register, Low Byte
$0023
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
These bits are used to compare against the least significant byte of the
address bus. These bits may be excluded from being used in the match
if BK0ALE = 0.
BRKDH — Breakpoint Data Register, High Byte
$0024
Bit 7
Bit 15
0
6
14
0
5
13
0
4
12
0
3
11
0
2
10
0
1
9
0
Bit 0
Bit 8
0
RESET:
These bits are compared to the most significant byte of the data bus or
the most significant byte of the address bus in dual address modes.
BKEN[1:0], BKDBE, and BKMBH control how this byte will be used in the
breakpoint comparison.
BRKDL — Breakpoint Data Register, Low Byte
$0025
Bit 7
Bit 7
0
6
6
0
5
5
0
4
4
0
3
3
0
2
2
0
1
1
0
Bit 0
Bit 0
0
RESET:
These bits are compared to the least significant byte of the data bus or
the least significant byte of the address bus in dual address modes.
23-dev
MC68HC912DT128A Rev 2.0
MOTOROLA
Development Support
349
De ve lop m e nt Sup p ort
BKEN[1:0], BKDBE, BK1ALE, and BKMBL control how this byte will be
used in the breakpoint comparison.
Instruc tion Ta g g ing
The instruction queue and cycle-by-cycle CPU activity can be
reconstructed in real time or from trace history that was captured by a
logic analyzer. However, the reconstructed queue cannot be used to
stop the CPU at a specific instruction, because execution has already
begun by the time an operation is visible outside the MCU. A separate
instruction tagging mechanism is provided for this purpose.
Executing the BDM TAGGO command configures two MCU pins for
tagging. The TAGLO signal shares a pin with the LSTRB signal, and the
TAGHI signal shares a pin with the BKGD signal. Tagging information is
latched on the falling edge of ECLK.
Table 64 shows the functions of the two tagging pins. The pins operate
independently - the state of one pin does not affect the function of the
other. The presence of logic level zero on either pin at the fall of ECLK
performs the indicated function. Tagging is allowed in all modes.
Tagging is disabled when BDM becomes active and BDM serial
commands are not processed while tagging is active.
Table 64 Tag Pin Function
TAGHI
TAGLO
Tag
1
1
0
0
1
0
1
0
no tag
low byte
high byte
both bytes
The tag follows program information as it advances through the queue.
When a tagged instruction reaches the head of the queue, the CPU
enters active background debugging mode rather than execute the
instruction.
24-dev
MC68HC912DT128A Rev 2.0
350
Development Support
MOTOROLA
Ele c tric a l Cha ra c te ristic s
Ele c tric a l Cha ra c te ristic s
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Tables of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Thermal Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
DC Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Supply Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
ATD DC Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 356
Analog Converter Characteristics (Operating) . . . . . . . . . . . . . . . 357
ATD AC Characteristics (Operating). . . . . . . . . . . . . . . . . . . . . . . 358
ATD Maximum Ratings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
EEPROM Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Flash EEPROM Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Pulse Width Modulator Characteristics. . . . . . . . . . . . . . . . . . . . . 360
Control Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Peripheral Port Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Multiplexed Expansion Bus Timing. . . . . . . . . . . . . . . . . . . . . . . . 367
SPI Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
CGM Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
STOP Key Wake-up Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
1-elec
MC68HC912DT128A Rev 2.0
MOTOROLA
Electrical Characteristics
351
Ele c tric a l Cha ra c te ristic s
Introd uc tion
The MC68HC912DT128A microcontroller unit (MCU) is a16-bit device
composed of standard on-chip peripherals including a 16-bit central
processing unit (CPU12), 128-Kbyte flash EEPROM, 8K byte RAM, 2K
byte EEPROM, two asynchronous serial communications interfaces
(SCI), a serial peripheral interface (SPI), an 8-channel, 16-bit timer,
two16-bit pulse accumulators and 16-bit down counter (ECT), two 10-bit
analog-to-digital converter (ADC), a four-channel pulse-width modulator
(PWM), an IIC interface module, and three MSCAN modules. The chip
is the first 16-bit microcontroller to include both byte-erasable EEPROM
and flash EEPROM on the same device. System resource mapping,
clock generation, interrupt control and bus interfacing are managed by
the Lite integration module (LIM). The MC68HC912DT128A has full
16-bit data paths throughout, however, the multiplexed external bus can
operate in an 8-bit narrow mode so single 8-bit wide memory can be
interfaced for lower cost systems.
2--elec
MC68HC912DT128A Rev 2.0
352
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Ta b le s of Da ta
Table 65 Maximum Ratings(1)
Rating
Symbol
Value
Unit
V
V
DD, VDDA
VDDX
,
Supply voltage
−0.3 to +6.5
−0.3 to +6.5
Input voltage
VIN
V
TL to TH
0 to +70
Operating temperature range
TA
°C
−40 to +85
Storage temperature range
Tstg
IIN
DD−VDDX
−55 to +150
±25
°C
mA
V
Current drain per pin(2)
Excluding VDD and VSS
V
DD differential voltage
V
6.5
1. Permanent damage can occur if maximum ratings are exceeded. Exposures to voltages or currents in excess of recom-
mended values affects device reliability. Device modules may not operate normally while being exposed to electrical ex-
tremes.
2. One pin at a time, observing maximum power dissipation limits. Internal circuitry protects the inputs against damage caused
by high static voltages or electric fields; however, normal precautions are necessary to avoid application of any voltage high-
er than maximum-rated voltages to this high-impedance circuit. Extended operation at the maximum ratings can adversely
affect device reliability. Tying unused inputs to an appropriate logic voltage level (either GND or VDD) enhances reliability
of operation.
NOTE: Four pins (VRL0, VRH0, VRL1, and VRH1) show ESD susceptibility
below the Motorola standards. Care should be exercised in handling
these pins.
3-elec
MC68HC912DT128A Rev 2.0
353
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Table 66 Thermal Characteristics
Characteristic
Average junction temperature
Symbol
TJ
Value
Unit
°C
TA + (PD × ΘJA)
User-determined
Ambient temperature
TA
°C
Package thermal resistance (junction-to-ambient)
112-pin quad flat pack (QFP)
ΘJA
40
°C/W
P
INT + PI/O or
Total power dissipation(1)
PD
W
K
-------------------------
TJ + 273°C
Device internal power dissipation
I/O pin power dissipation(2)
A constant(3)
PINT
PI/O
K
I
DD × VDD
W
W
User-determined
2
PD × (TA + 273°C) + ΘJA × PD
W · °C
1. This is an approximate value, neglecting PI/O
.
2. For most applications PI/O « PINT and can be neglected.
3. K is a constant pertaining to the device. Solve for K with a known TA and a measured PD (at equilibrium). Use this value of
K to solve for PD and TJ iteratively for any value of TA.
Table 67 DC Electrical Characteristics
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
Symbol
Characteristic
Min
Max
Unit
V
Input high voltage, all inputs
Input low voltage, all inputs
VIH
VIL
0.7 × VDD
V
DD + 0.3
V
SS−0.3
0.2 × VDD
V
Output high voltage, all I/O and output pins except XTAL
Normal drive strength
I
I
OH = −10.0 µA
OH = −0.8 mA
V
V
DD − 0.2
DD − 0.8
—
—
V
V
VOH
Reduced drive strength
I
I
OH = −4.0 µA
OH = −0.3 mA
V
V
DD − 0.2
DD − 0.8
—
—
V
V
Output low voltage, all I/O and output pins except XTAL
Normal drive strength
I
I
OL = 10.0 µA
OL = 1.6 mA
—
—
V
V
SS+0.2
SS+0.4
V
V
VOL
Reduced drive strength
I
I
OL = 3.6 µA
OL = 0.6 mA
—
—
V
V
SS+0.2
SS+0.4
V
V
4-elec
MC68HC912DT128A Rev 2.0
354
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Table 67 DC Electrical Characteristics
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
Symbol
Characteristic
Min
Max
Unit
Input leakage current(1)
Vin = VDD or VSSAll input only pins except IRQ, ATD(2) and
VFP
Vin = VDD or VSSIRQ
Iin
—
—
±2.5
±10
µA
µA
Three-state leakage, I/O ports, BKGD, and RESET
IOZ
—
±2.5
µA
Input capacitance
All input pins and ATD pins (non-sampling)
ATD pins (sampling)
All I/O pins
—
—
—
10
15
20
pF
pF
pF
Cin
Output load capacitance
All outputs except PS[7:4]
PS[7:4] when configured as SPI
CL
—
—
90
200
pF
pF
Programmable active pull-up/pull-down current
IRQ, XIRQ, DBE, LSTRB, R/W. ports A, B, H, J, K, P, S, T
MODA, MODB active pull down during reset
BKGD passive pull up
50
50
50
500
500
500
µA
µA
µA
IAPU
RAM standby voltage, power down
RAM standby current
VSB
ISB
1.5
—
V
—
50
µA
1. Specification is for parts in the -40 to +85°C range. Higher temperature ranges will result in increased
current leakage.
2. See ATD DC Electrical Characteristics.
Table 68 Supply Current
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
Characteristic
Symbol
2 MHz
4 MHz
8 MHz
Unit
Maximum total supply current
RUN:
IDD
Single-chip mode
Expanded mode
20
30
30
50
55
90
mA
mA
WAIT: (All peripheral functions shut down)
Single-chip mode
WIDD
3
4
5
6.5
10
15
mA
mA
Expanded mode
STOP:
SIDD
Single-chip mode, no clocks
150
150
150
µA
5-elec
MC68HC912DT128A Rev 2.0
355
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Table 69 ATD DC Electrical Characteristics
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, ATD Clock = 2 MHz, unless otherwise noted
Characteristic
Symbol
Min
Max
Unit
Analog supply voltage
VDDA
4.5
5.5
V
Analog supply currentNormal operation
STOP
1.0
10
mA
µA
IDDA
Reference voltage, low
Reference voltage, high
VREF differential reference voltage(1)
Input voltage(2)
VRL
VRH
VSSA
V
DDA/2
VDDA
5.5
V
V
VDDA/2
V
RH−VRL
VINDC
IOFF
4.5
V
VSSA
VDDA
100
V
Input current, off channel(3)
µA
µA
Reference supply current
IREF
250
Input capacitanceNot Sampling
Sampling
CINN
CINS
10
15
pF
pF
1. Accuracy is guaranteed at VRH − VRL = 5.0V ±10%.
2. To obtain full-scale, full-range results, VSSA ≤ VRL ≤ VINDC ≤ VRH ≤ VDDA
.
3. Maximum leakage occurs at maximum operating temperature. Current decreases by approximately one-half for each 10°C
decrease from maximum temperature.
6-elec
MC68HC912DT128A Rev 2.0
356
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Table 70 Analog Converter Characteristics (Operating)
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, ATD Clock = 2 MHz, unless otherwise noted
Characteristic
Symbol
1 count
DNL
Min
Typical
Max
Unit
mV
8-bit resolution(1)
20
8-bit differential non-linearity(2)
−0.5
−1
+0.5
+1
count
count
count
8-bit integral non-linearity(2)
INL
8-bit absolute error,(3)2, 4, 8, and 16 ATD sample clocks
AE
−1
+1
10-bit resolution(1)
1 count
DNL
INL
5
mV
10-bit differential non-linearity(2)
10-bit integral non-linearity(2)
–2
–2
2
2
count
count
count
10-bit absolute error(3) 2, 4, 8, and 16 ATD sample clocks
AE
–2.5
2.5
See
Maximum source impedance
RS
20
KΩ
note(4)
1. VRH − VRL ≥ 5.12V; VDDA − VSSA = 5.12V
2. At VREF = 5.12V, one 8-bit count = 20 mV, and one 10-bit count = 5mV.
INL and DNL are characterized using the process window parameters affecting the ATD accuracy, but they are not tested.
3. These values include quantization error which is inherently 1/2 count for any A/D converter.
4. Maximum source impedance is application-dependent. Error resulting from pin leakage depends on junction leakage into
the pin and on leakage due to charge-sharing with internal capacitance.
Error from junction leakage is a function of external source impedance and input leakage current. Expected error in result
value due to junction leakage is expressed in voltage (VERRJ):
VERRJ = RS × IOFF
where IOFF is a function of operating temperature. Charge-sharing effects with internal capacitors are a function of ATD
clock speed, the number of channels being scanned, and source impedance. For 8-bit conversions, charge pump leakage
is computed as follows:
VERRJ = .25pF × VDDA × RS × ATDCLK/(8 × number of channels)
7-elec
MC68HC912DT128A Rev 2.0
357
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Table 71 ATD AC Characteristics (Operating)
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, ATD Clock = 2 MHz, unless otherwise noted
Characteristic
Symbol
Min
Max
Unit
ATD operating clock frequency
fATDCLK
0.5
2.0
MHz
Conversion time per channel
0.5 MHz ≤ fATDCLK ≤ 2 MHz
16 ATD clocks
tCONV
8.0
15.0
32.0
60.0
µs
µs
30 ATD clocks
Stop and ATD power up recovery time(1)
V
DDA = 5.0V
tSR
10
µs
1. From the time ADPU is asserted until the time an ATD conversion can begin.
Table 72 ATD Maximum Ratings
Characteristic
Symbol
Value
Units
ATD reference voltage
V
V
RH ≤ VDDA
RL ≥ VSSA
VRH
VRL
−0.3 to +6.5
−0.3 to +6.5
V
V
V
SS differential voltage
DD differential voltage
|VSS−VSSA
|
0.1
V
VDD−VDDA
DDA−VDD
6.5
0.3
V
V
V
V
VREF differential voltage
|VRH−VRL
|
6.5
6.5
V
V
Reference to supply differential voltage
|VRH−VDDA
|
8-elec
MC68HC912DT128A Rev 2.0
358
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Table 73 EEPROM Characteristics
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
Characteristic
Symbol
fPROG
Min
Max
Unit
hz
Minimum programming clock frequency
Programming time
250K
tPROG
10
PROG+ 1
10
ms
Clock recovery time, following STOP, to continue programming tCRSTOP
t
ms
Erase time
tERASE
ms
Write/erase endurance
10,000
10(1)
—
cycles
years
µs
Data retention
EEPROM Programming Maximum Time to ‘AUTO’ Bit Set
EEPROM Erasing Maximum Time to ‘AUTO’ Bit Set
1. Based on the average life time operating temperature of 70°C.
—
—
500
10
—
ms
Table 74 Flash EEPROM Characteristics
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
Characteristic
Symbol
—
Min
64
32K
8
Max
64
8M
—
Units
Bytes
hz
Bytes per row
Read bus clock frequency
Erase time
fREAD
tERAS
tNVS
tNVH
tNVHL
tPGS
tFPGM
tRCV
tHV
ms
PGM/ERAS to HVEN set up time
High-voltage hold time
10
5
—
µs
—
µs
High-voltage hold time (erase)
Program hold time
100
5
—
µs
—
µs
Program time
30
1
40
—
µs
Return to read time
µs
Cumulative program hv period
Row program/erase endurance
Data retention
—
8
ms
—
100
10(1)
cycles
years
—
1. Based on the average life time operating temperature of 70°C.
9-elec
MC68HC912DT128A Rev 2.0
359
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Table 75 Pulse Width Modulator Characteristics
V
DD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
Characteristic
Symbol
Min
Max
Unit
E-clock frequency
feclk
0.004
8.0
MHz
A-clock frequency
Selectable
faclk
fbclk
feclk
feclk
Hz
Hz
feclk/128
feclk/128
BCLK frequency
Selectable
Left-aligned PWM frequency
8-bit
16-bit
flpwm
rlpwm
fcpwm
rcpwm
feclk/1M
feclk/256M
f
eclk/2
Hz
Hz
feclk/2
Left-aligned PWM resolution
feclk/4K
feclk
Hz
Center-aligned PWM frequency
8-bit
16-bit
feclk/2M
feclk/512M
feclk
feclk
Hz
Hz
Center-aligned PWM resolution
feclk/4K
feclk
Hz
10-elec
MC68HC912DT128A Rev 2.0
360
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Table 76 Control Timing
8.0 MHz
Unit
Characteristic
Symbol
Min
0.004
0.125
0.5
Max
Frequency of operation
E-clock period
fo
tcyc
fXTAL
feo
8.0
MHz
µs
250
16.0
16.0
Crystal frequency
MHz
MHz
External oscillator frequency
0.5
Processor control setup time
tPCSU
92
—
tPCSU = tcyc/2+ 30
ns
Reset input pulse width
To guarantee external reset vector
Minimum input time (can be preempted by internal reset)
PWRSTL
32
2
—
—
tcyc
tcyc
Mode programming setup time
tMPS
tMPH
4
—
—
tcyc
ns
Mode programming hold time
20
Interrupt pulse width, IRQ edge-sensitive mode
PWIRQ = 2tcyc + 20
PWIRQ
270
—
ns
Wait recovery startup time
tWRS
—
4
cycles
ns
Timer input capture pulse width
PWTIM
270
—
1. RESET is recognized during the first clock cycle it is held low. Internal circuitry then drives
the pin low for 16 clock cycles, releases the pin, and samples the pin level 8 cycles later
to determine the source of the interrupt.
1
PT[7:0]
PW
TIM
2
PT[7:0]
1
PT7
PW
PA
2
PT7
NOTES:
1. Rising edge sensitive input
2. Falling edge sensitive input
Figure 62 Timer Inputs
11-elec
MC68HC912DT128A Rev 2.0
361
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Figure 63 POR and External Reset Timing Diagram
12-elec
MC68HC912DT128A Rev 2.0
362
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Figure 64 STOP Recovery Timing Diagram
13-elec
MC68HC912DT128A Rev 2.0
363
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Figure 65 WAIT Recovery Timing Diagram
14-elec
MC68HC912DT128A Rev 2.0
364
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Figure 66 Interrupt Timing Diagram
15-elec
MC68HC912DT128A Rev 2.0
365
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Table 77 Peripheral Port Timing
8.0 MHz
Characteristic
Symbol
Unit
Min
Max
8.0
Frequency of operation (E-clock frequency)
E-clock period
fo
0.004
0.125
MHz
tcyc
250
µs
Peripheral data setup time
MCU read of ports
tPDSU
tPDH
tPWD
tPWD
81
0
—
—
40
71
ns
ns
ns
ns
Peripheral data hold time
MCU read of ports
Delay time, peripheral data write
MCU write to ports except Port CAN
—
—
Delay time, peripheral data write
MCU write to Port CAN
MCU READ OF PORT
ECLK
t
t
PDSU
PDH
PORTS
PORT RD TIM
Figure 67 Port Read Timing Diagram
MCU WRITE TO PORT
ECLK
t
PWD
PREVIOUS PORT DATA
NEW DATA VALID
PORT A
PORT WR TIM
Figure 68 Port Write Timing Diagram
16-elec
MC68HC912DT128A Rev 2.0
366
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Table 78 Multiplexed Expansion Bus Timing
DD = 5.0 Vdc ± 10%, VSS = 0 Vdc, TA = TL to TH, unless otherwise noted
V
8 MHz
Characteristic(1), (2), (3), (4)
Delay Symbol
Num
Unit
Min
Max
8.0
Frequency of operation (E-clock frequency)
Cycle time
fo
0.004
0.125
60
MHz
µs
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
1
t
cyc = 1/fo
—
−2
−2
14
—
tcyc
250
2
Pulse width, E low
Pulse width, E high(5)
PWEL = tcyc/2 + delay
PWEH = tcyc/2 + delay
PWEL
PWEH
tAD
3
60
5
Address delay time
t
AD = tcyc/4 + delay
AV = PWEL − tAD
MAH = tcyc/4 + delay
45
7
Address valid time to ECLK rise
Multiplexed address hold time
Address Hold to Data Valid
Data Hold to High Z
t
tAV
15
15
5
8
t
−16
—
tMAH
tAHDS
tDHZ
tDSR
tDHR
tDDW
tDHW
tDSW
tRWD
tRWV
tRWH
tLSD
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
t
DHZ = tAD − 20
—
20
45
50
57
Read data setup time
—
38
0
Read data hold time
—
Write data delay time
t
DDW = tcyc/4 + delay
DHW = tcyc/4 + delay
tDSW = PWEH − tDDW
14
−11
—
Write data hold time
t
20
15
Write data setup time(5)
Read/write delay time
Read/write valid time to E rise
Read/write hold time
t
RWD = tcyc/4 + delay
RWV = PWEL − tRWD
RWH = tcyc/4 + delay
19
—
t
10
5
t
−26
26
—
Low strobe(6) delay time
Low strobe(6) valid time to E rise
Low strobe(6) hold time
Address access time(5)
Access time from E rise(5)
DBE delay from ECLK rise(5)
DBE valid time
t
LSD = tcyc/4 + delay
LSV = PWEL − tLSD
LSH = tcyc/4 + delay
t
tLSV
3
5
t
−26
—
tLSH
t
ACCA = tcyc − tAD − tDSR
ACCE = PWEH − tDSR
DBED = tcyc/4 + delay
DBE = PWEH − tDBED
tACCA
tACCE
tDBED
tDBE
tDBEH
26
22
51
t
—
t
20
—
t
9
0
DBE hold time from ECLK fall
10
1. All timings are calculated for normal port drives.
2. Crystal input is required to be within 45% to 55% duty.
3. Reduced drive must be off to meet these timings.
4. Unequalled loading of pins will affect relative timing numbers.
5. This characteristic is affected by clock stretch.
Add N × tcyc where N = 0, 1, 2, or 3, depending on the number of clock stretches.
6. Without TAG enabled.
17-elec
MC68HC912DT128A Rev 2.0
367
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
1
2
3
ECLK
16
17
20
18
21
R/W
19
LSTRB
(W/O TAG ENABLED)
23
11
5
7
10
22
12
READ
ADDRESS
DATA
ADDRESS/DATA
MULTIPLEXED
9
8
13
15
14
WRITE
ADDRESS
DATA
24
25
26
DBE
NOTE: Measurement points shown are 20% and 70% of V
DD
Figure 69 Multiplexed Expansion Bus Timing Diagram
18-elec
MC68HC912DT128A Rev 2.0
368
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
Table 79 SPI Timing
(VDD = 5.0 Vdc ±10%, VSS = 0 Vdc, TA = TL to TH , 200 pF load on all SPI pins)(1)
Num
Function
Operating Frequency
Symbol
Min
Max
Unit
Master
Slave
fop
1/256
1/256
1/2
1/2
feclk
SCK Period
Master
Slave
tsck
tlead
tlag
twsck
ttd
2
2
256
—
tcyc
tcyc
Enable Lead Time
Master
Slave
1/2
1
—
—
tsck
tcyc
Enable Lag Time
Master
Slave
1/2
1
—
—
tsck
tcyc
Clock (SCK) High or Low Time
Master
Slave
t
t
cyc − 60
cyc − 30
128 tcyc
ns
ns
—
Sequential Transfer Delay
Master
Slave
1/2
1
—
—
tsck
tcyc
Data Setup Time (Inputs)
Master
Slave
tsu
30
30
—
—
ns
ns
Data Hold Time (Inputs)
Master
Slave
thi
0
30
—
—
ns
ns
Slave Access Time
ta
—
—
1
1
tcyc
tcyc
Slave MISO Disable Time
tdis
Data Valid (after SCK Edge)
Master
Slave
tv
—
—
50
50
ns
ns
Data Hold Time (Outputs)
Master
Slave
tho
0
0
—
—
ns
ns
Rise Time
Input
Output
tri
tro
—
—
t
cyc − 30
30
ns
ns
Fall Time
Input
Output
tfi
tfo
—
—
t
cyc − 30
30
ns
ns
1. All AC timing is shown with respect to 20% VDD and 70% VDD levels unless otherwise noted.
19-elec
MC68HC912DT128A Rev 2.0
369
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
1
SS
(OUTPUT)
5
2
1
12
13
3
SCK
(CPOL = 0)
(OUTPUT)
4
4
SCK
(CPOL = 1)
(OUTPUT)
6
7
MISO
(INPUT)
2
BIT 6 . . . 1
10
MSB IN
LSB IN
10
11
MOSI
(OUTPUT)
2
BIT 6 . . . 1
LSB OUT
MSB OUT
1.
output mode (DDS7 = 1, SSOE = 1).
SS
2. LSBF = 0. For LSBF = 1, bit order is LSB, bit 1, ..., bit 6, MSB.
A) SPI Master Timing (CPHA = 0)
1
SS
(OUTPUT)
5
1
13
12
12
13
3
2
SCK
(CPOL = 0)
(OUTPUT)
4
4
SCK
(CPOL = 1)
(OUTPUT)
6
7
MISO
(INPUT)
2
MSB IN
BIT 6 . . . 1
11
BIT 6 . . . 1
LSB IN
10
MOSI
(OUTPUT)
2
PORT DATA
MASTER LSB OUT
PORT DATA
MASTER MSB OUT
1.
output mode (DDS7 = 1, SSOE = 1).
SS
2. LSBF = 0. For LSBF = 1, bit order is LSB, bit 1, ..., bit 6, MSB.
B) SPI Master Timing (CPHA = 1)
Figure 70 SPI Timing Diagram (1 of 2)
20-elec
MC68HC912DT128A Rev 2.0
370
Electrical Characteristics
MOTOROLA
Electrical Characteristics
Tables of Data
SS
(INPUT)
5
1
13
12
12
13
3
SCK
(CPOL = 0)
(INPUT)
4
4
2
SCK
(CPOL = 1)
(INPUT)
9
8
10
11
11
MISO
(OUTPUT)
SEE
NOTE
BIT 6 . . . 1
SLAVE LSB OUT
MSB OUT
7
SLAVE
6
MOSI
(INPUT)
BIT 6 . . . 1
MSB IN
LSB IN
NOTE: Not defined but normally MSB of character just received.
A) SPI Slave Timing (CPHA = 0)
SS
(INPUT)
5
3
1
13
12
13
2
SCK
(CPOL = 0)
(INPUT)
4
4
12
11
SCK
(CPOL = 1)
(INPUT)
9
10
MISO
(OUTPUT)
SEE
BIT 6 . . . 1
SLAVE LSB OUT
LSB IN
SLAVE
6
MSB OUT
7
NOTE
8
MOSI
(INPUT)
MSB IN
BIT 6 . . . 1
NOTE: Not defined but normally LSB of character just received.
SPI SLAVE CPHA1
B) SPI Slave Timing (CPHA = 1)
Figure 71 SPI Timing Diagram (2 of 2)
MC68HC912DT128A Rev 2.0
371
MOTOROLA
Electrical Characteristics
Ele c tric a l Cha ra c te ristic s
Table 80 CGM Characteristics
5.0 Volts +/- 10%
Symbol
Characteristic
Min.
0.5
Max.
8
Unit
MHz
MHz
MHz
MHz
—
PLL reference frequency, crystal oscillator range(1)
fREF
fBUS
Bus frequency
0.004
2.5
8
VCO range
fVCO
8
VCO Limp-Home frequency
fVCOMIN
0.5
2.5
4%
1.5%
2.5%
8%
Lock Detector transition from Acquisition to Tracking mode
Lock Detection
∆
3%
trk
∆
0%
—
Lock
Un-Lock Detection
∆
0.5%
6%
—
unl
Lock Detector transition from Tracking to Acquisition mode
PLLON Stabilization delay(2)
∆
—
unt
PLLON Total Stabilization delay(3)
PLLON Acquisition mode stabilization delay(3)
PLLON Tracking mode stabilization delay(3)
1. VDDPLL at VDD level.
tstab
tacq
tal
3
1
2
ms
ms
ms
2. PLL stabilization delay is highly dependent on operational requirement and external component values (e.e. crystal, XFC
filter component values). Note (3) shows typical delay values for a typical configuration. Appropriate XFC filter values
should be chosen based on operational requirement of system.
3. fREF = 4MHz, fSYS = 8MHz (REFDV = #$00, SYNR = #$01), XFC: Cs = 33nF, Cp - 3.3nF, Rs = 2.7KΩ.
Table 81 STOP Key Wake-up Filter
Characteristic
Symbol
tKWSTP
tKWSP
Min.
2
Max.
Unit
µs
STOP Key Wake-Up Filter time
STOP Key Wake-Up Filter pulse interval
10
-
20
µs
MC68HC912DT128A Rev 2.0
372
Electrical Characteristics
MOTOROLA
Ap p e nd ix A: MC68HC912DT128A
Ap p e nd ix A: MC68HC912DT128A
Conte nts
6. Port ADx 375
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
1. Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
2. EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
3. STOP mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
4. WAIT mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
5. KWU Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
6. Port ADx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
7. ATD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Sig nific a nt c ha ng e s from the MC68HC912DG128 (non-A suffix d e vic e )
1. Fla sh
1a . Fla sh
Arc hite c ture
The flash arrays are made from a new non-volatile memory (NVM)
technology. An external VFP is no longer used. Programming is now
carried out on a whole row (64 bytes) at a time. Erasing is still a bulk
erase of the entire array.
1b . Fla sh C o ntro l
Re g iste r
The Flash Control Register (FEECTL) is in the same location. However,
the individual bit functions have changed significantly to support the new
technology.
1c . Fla sh
Pro g ra m m ing
Pro c e d ure
Programming of the flash is greatly simplified over previous HC12s. The
read / verify / re-pulse programming algorithm is replaced by a much
simpler method.
1-appA
MC68HC912DT128A Rev 2.0
MOTOROLA
Appendix A: MC68HC912DT128A
373
Ap p e nd ix A: MC68HC912DT128A
1d . Fla sh
The most significant change resulting from the new flash technology is
Pro g ra m m ing Tim e
that the bulk erase and program times are now fixed. The erase time is
at least twice as fast while the word programming time is at least 20%
faster.
1e . Fla sh Exte rna l
Pro g ra m m ing
Vo lta g e
The new flash does not require an external high voltage supply. All
voltages required for programming and erase are now generated
internally. Pin 97 that was the VFP pin on the 68HC912DG128 is now a
factory TEST pin. On ealy production devices it is recommended that
this pin is not connected within the application, but it may be connected
to VSS or 5.5V max without issue. On later production parts this pin is
not bonded out.
2. EEPROM
2a . EEPROM
Arc hite c ture
Like the flash, the EEPROM is also made from this new NVM
technology. The architecture and basic programming and erase
operations are unchanged. However, there is a new optional
programming method that allows faster programming of the EEPROM.
3b . EEPROM Clo c k
So urc e a nd
Pre -sc a le r
The first major difference on the new EEPROM is that it requires a
constant time base source to ensure secure programming and erase
operations. The clock source that is going to drive the clock divider input
is the external clock input, EXTALi. The divide ratio from this source has
to be set by programming an 10-bit time base pre-scalar into bits spread
over two new registers, EEDIVH and EEDIVL.
The EEDIVH and EEDIVL registers are volatile. However, they are
loaded upon reset by the contents of the non-volatile SHADOW word
much in the same way as the EEPROM module control register
(EEMCR) bits interact with the SHADOW word for configuration control
on the existing revision.
2c . EEPROM AUTO
p ro g ra m m ing &
e ra sing
The second major change to the EEPROM is the inclusion in the
EEPROM control register (EEPROG) of an AUTO function using the
previously unused bit 5 of this register.
2-appA
MC68HC912DT128A Rev 2.0
374
Appendix A: MC68HC912DT128A
MOTOROLA
Appendix A: MC68HC912DT128A
Significant changes from the MC68HC912DG128 (non-A suffix device)
The AUTO function enables the logic of the MCU to automatically use
the optimum programming or erasing time for the EEPROM. If using
AUTO, the user does not need to wait for the normal minimum specified
programming or erasing time. After setting the EEPGM bit as normal the
user just has to poll that bit again, waiting for the MCU to clear it
indicating that programming or erasing is complete.
2d . EEPROM
Se le c tive Write
Mo re Ze ro s
For some applications it may be advantageous to track more than 10k
events with a single byte of EEPROM by programming one bit at a time.
For that purpose, a special selective bit programming technique is
available.
When this technique is utilized, a program / erase cycle is defined as
multiple writes (up to eight) to a unique location followed by a single
erase sequence.
3. STOP m od e
4. WAIT m od e
This new version will correctly exit STOP mode without having to
synchronize the start of STOP with the RTI clock.
This new version will correctly exit WAIT mode using short XIRQ or IRQ
inputs.
5. KWU Filte r
6. Port ADx
The KWU filter will now ignore pulses shorter than 2 microseconds.
Power must be applied to VDDA at all times even if the ADC is not being
used. This is necessary for port AD0 and port AD1 to function correctly
as digital inputs.
7. ATD
Bit CC of ATDxCTL5 is not masked when bit S8CM = 1.
3-appA
MC68HC912DT128A Rev 2.0
MOTOROLA
Appendix A: MC68HC912DT128A
375
Ap p e nd ix A: MC68HC912DT128A
4-appA
MC68HC912DT128A Rev 2.0
376
Appendix A: MC68HC912DT128A
MOTOROLA
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
Conte nts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
A Few Hints For The CGM Crystal Oscillator Application. . . . . . . . . 377
Practical Aspects For The PLL Usage . . . . . . . . . . . . . . . . . . . . . . . 380
Printed Circuit Board Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Introd uc tion
This sections provides useful and practical pieces of information
concerning the implementation of the CGM module.
A Fe w Hints For The CGM Crysta l Osc illa tor Ap p lic a tion
Wha t Loa d ing
Ca p a c itors To
Choose ?
First, from small-signal analysis, it is known that relatively large values
for C1 and C2 have a positive impact on the phase margin. However, the
higher loading they represent decreases the loop gain. Alternatively,
small values for these capacitors will lead to higher open loop gain, but
as the frequency of oscillation approaches the parallel resonance, the
phase margin, and consequently the ability to start-up correctly, will
decrease. From this it is clear that relatively large capacitor values
(>33pF), are reserved for low frequency crystals in the MHz range.
NOTE: Using the recommended loading capacitor CL value from the crystal
manufacturer is a good starting point. Taking into account unavoidable
strays, this equates to about (CL-2pF).
1-cgmpa
MC68HC912DT128A Rev 2.0
MOTOROLA
Appendix B: CGM Practical Aspects
377
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
Theoretically speaking, nothing precludes the use of non-identical
values for C1 and C2. As this complicate a bit the management of the
final board device list, this is not recommended. However, if
asymmetrical capacitors are chosen, the value of C1 should be higher
than C2 (because the reflected loading is proportional to the square of
the impedance of C2).
DC Bia s
Due to the nature of the translated ground Colpitts oscillator a DC
voltage bias is applied to the crystal.
Please contact the crystal manufacturer for specific DC bias conditions
and recommended capacitance value (if applicable).
Wha t Is the Fina l
Osc illa tion
Fre q ue nc y?
The exact calculation is not straightforward as it takes into account the
resonator characteristics and the loading capacitors values as well as
internal design parameters which can vary with Process Voltage
Temperature (PVT) conditions. Nevertheless, if L is the series
inductance, R is the series resistance, C is the series capacitance and
Cc the parallel capacitance of the crystal, we can then use the following
simplified equation:
1
2π
1
1
Fosc = ------ ------- + ---------------------------------------------
||
LC L (Cc + C1 C2)
C1=C2=Cl yields to
1
1
1
Fosc = ------ ------- + --------------------------------------
2π LC L (Cc + Cl ⁄ 2)
How Do I Control
The Pe a k to Pe a k
Osc illa tion
The CGM oscillator is equipped with an Amplitude Limitation Control
loop which integrates the peak to peak ‘extal’ amplitude and in return
reduces the steady current of the transconductor device until a stable
quiescent point is reached. Controlling this final peak to peak amplitude
can be performed by three means:
Am p litud e ?
1. Reducing the values of C1 and C2. This decreases the loading so
that the necessary gm value required to sustain oscillation can be
2-cgmpa
MC68HC912DT128A Rev 2.0
378
Appendix B: CGM Practical Aspects
MOTOROLA
Appendix B: CGM Practical Aspects
A Few Hints For The CGM Crystal Oscillator Application
smaller. The consequently smaller current will be reached with a
larger ‘extal’ swing.
2. Using VDDPLL=VSS (i.e. shutting off the PLL). Doing so
increases the starting current by approximately 50%. All other
parameters staying the same, a larger ‘extal’ swing will be required
to reduce this starting current to its quiescent value.
3. Also, placing a high value resistor (>1MΩ) across the EXTAL and
XTAL pins significantly increased the oscillation amplitude.
Because this complicates the design analysis as it transforms a
pure susceptance jωC1 into a complex admittance G+jωC1,
Motorola cannot promote this application trick.
Wha t Do I Do In
Ca se The
Osc illa tor Doe s
Not Sta rt-up ?
1. First, verify that the application schematic respects the principle of
operation, i.e. crystal mounted between EXTAL and VSS,
Capacitor C1 between XTAL and EXTAL, Capacitor C2 between
XTAL and VSS, nothing else. This is not the conventional MCU
application schematic of the Pierce oscillator as it can be seen on
other HC12 derivatives!
2. Re-consider the choice of the tuning capacitors.
3. If the quartz or resonator is of a high frequency type (e.g. above
10MHz), consider using VDDPLL=0V. Obviously, this choice
precludes the use of the PLL. However, in this case the oscillator
circuitry has more quiescent current available and the starting
transconductance is thus significantly higher.
4. The oscillator circuitry is powered internally from a core VDD pad
and the return path is the VSSPLL pad. Verify on the application
PCB the correct connection of these pads (especially VSSPLL),
but also verify the waveform of the VDD voltage as it is imposed
on the pad. Sometimes external components (for instance choke
inductors), can cause oscillations on the power line. This is of
course detrimental to the oscillator circuitry.
5. If possible, consider using a resonator with built-in tuning
capacitors. They may offer better performances with respect to
their discrete elements implementation.
3-cgmpa
MC68HC912DT128A Rev 2.0
MOTOROLA
Appendix B: CGM Practical Aspects
379
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
Pra c tic a l Asp e c ts For The PLL Usa g e
Synthe size d Bus
Fre q ue nc y
Starting from a ceramic resonator or quartz crystal frequency FXTAL, if
‘refdv’ and ‘synr’ are the decimal content of the REFDV and SYNR
registers respectively, then the MCU bus frequency will simply be:
FXTAL (synr + 1)
FBUS = FVCO = ---------------------------------------------
(refdv + 1)
synr {0,1,2,3...63}
refdv {0,1,2,3...7}
NOTE: It is not allowed to synthesize a bus frequency that is lower than the
crystal frequency, as the correct functioning of some internal
synchronizers would be jeopardized (e.g. the MCLK and XCLK clock
generators).
Op e ra tion Und e r
Ad ve rse
Environm e nta l
Cond itions
The normal operation for the PLL is the so-called ‘automatic bandwidth
selection mode’ which is obtained by having the AUTO bit set in the
PLLCR register. When this mode is selected and as the VCO frequency
approaches its target, the charge pump current level will automatically
switch from a relatively high value of around 40 µA to a lower value of
about 3 µA. It can happen that this low level of charge pump current is
not enough to overcome leakages present at the XFC pin due to adverse
environmental conditions. These conditions are frequently encountered
for uncoated PCBs in automotive applications. The main symptom for
this failure is an unstable characteristic of the PLL which in fact ‘hunts’
between acquisition and tracking modes. It is then advised for the
running software to place the PLL in manual, forced acquisition mode by
clearing both the AUTO and the ACQ bits in the PLLCR register. Doing
so will maintain the high current level in the charge pump constantly and
will permit to sustain higher levels of leakages at the XFC pin. This latest
revision of the Clock Generator Module maintains the lock detection
feature even in manual bandwidth control, offering then to the
application software the same flexibility for the clocking control as the
automatic mode.
4-cgmpa
MC68HC912DT128A Rev 2.0
380
Appendix B: CGM Practical Aspects
MOTOROLA
Appendix B: CGM Practical Aspects
Practical Aspects For The PLL Usage
Filte r Com p one nts
Se le c tion Guid e
Eq ua tio ns Se t
These equations can be used to select a set of filter components. Two
cases are considered:
1. The ‘tracking’ mode. This situation is reached normally when the
PLL operates in automatic bandwidth selection mode (AUTO=1 in
the PLLCR register).
2. The ‘acquisition’ mode. This situation is reached when the PLL
operates in manual bandwidth selection mode and forced
acquisition (AUTO=0, ACQ=0 in the PLLCR register).
In both equations, the power supply should be 5V. Start with the target
loop bandwidth as a function of the other parameters, but obviously,
nothing prevents the user from starting with the capacitor value for
example. Also, remember that the smoothing capacitor is always
assumed to be one tenth of the series capacitance value.
So with:
m:
R:
C:
the multiplying factor for the reference frequency (i.e. (synr+1))
the series resistance of the low pass filter in Ω
the series capacitance of the low pass filter in nF
Fbus: the target bus frequency expressed in MHz
ζ:
the desired damping factor
Fc:
the desired loop bandwidth expressed in Hz
for the ‘tracking’ mode:
1.675 – Fbus
-----------------------------
10.795
2 109 ζ2
37.78 e
R
Fc = ------------------------- = -----------------------------------------------------
2 π m
π R C
and for the ‘acquisition’ mode:
2 109 ζ2
1.675 – Fbus
-----------------------------
10.795
415.61 e
R
Fc = ------------------------- = --------------------------------------------------------
π R C
2 π m
5-cgmpa
MC68HC912DT128A Rev 2.0
381
MOTOROLA
Appendix B: CGM Practical Aspects
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
Pa rtic ula r Ca se o f
a n 8MHz Synthe sis
Assume that a desired value for the damping factor of the second order
system is close to 0.9 as this leads to a satisfactory transient response.
Then, derived from the equations above, Table 82 and Table 83 suggest
sets of values corresponding to several loop bandwidth possibilities in
the case of an 8MHz synthesis for the two cases mentioned above.
The filter components values are chosen from standard series (e.g. E12
for resistors). The operating voltage is assumed to be 5V (although there
is only a minor difference between 3V and 5V operation). The smoothing
capacitor Cp in parallel with R and C is set to be 1/10 of the value of C.
The reference frequencies mentioned in this table correspond to the
output of the fine granularity divider controlled by the REFDV register.
This means that the calculations are irrespective of the way the
reference frequency is generated (directly for the crystal oscillator or
after division). The target frequency value also has an influence on the
calculations of the filter components because the VCO gain is NOT
constant over its operating range.
The bandwidth limit corresponds to the so-called Gardner’s criteria. It
corresponds to the maximum value that can be chosen before the
continuous time approximation ceases to be justified. It is of course
advisable to stay far away from this limit.
6-cgmpa
MC68HC912DT128A Rev 2.0
382
Appendix B: CGM Practical Aspects
MOTOROLA
Appendix B: CGM Practical Aspects
Practical Aspects For The PLL Usage
Table 82 Suggested 8MHz Synthesis PLL Filter Elements (Tracking Mode)
Loop Bandwidth
[kHz]
Bandwidth
Limit [kHz]
Reference [MHz]
SYNR
Fbus [MHz] C [nF]
R [kΩ]
0.614
0.614
0.614
0.614
0.8
0.8
0.8
0.8
1
$0C
$0C
$0C
$0C
$09
$09
$09
$09
$07
$07
$07
$07
$05
$05
$05
$05
$03
$03
$03
$03
$02
$02
$02
$02
$01
$01
$01
$01
7.98
7.98
7.98
7.98
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
100
4.7
1
4.3
20
43
75
2.7
12
27
56
2.4
11
1.1
5.3
11.5
20
157
157
157
157
201
201
201
201
251
251
251
251
402
402
402
402
502
502
502
502
668
668
668
668
1005
1005
1005
1005
0.33
220
10
0.9
4.2
8.6
19.2
1
2.2
0.47
220
10
1
4.7
9.9
21.4
1
1
2.2
0.47
330
10
24
51
1.5
9.1
15
27
1.1
5.1
11
1
1.6
1.6
1.6
1.6
2
5.9
10.2
18.6
0.96
4.4
9.6
20.8
1.6
5.1
11
3.3
1
470
22
2
2
4.7
1
2
24
1.5
4.7
10
22
1.2
3
2.66
2.66
2.66
2.66
4
220
22
4.7
1
24
220
33
1.98
5.1
9.3
19.8
4
4
10
5.6
12
4
2.2
7-cgmpa
MC68HC912DT128A Rev 2.0
383
MOTOROLA
Appendix B: CGM Practical Aspects
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
Table 83 Suggested 8MHz Synthesis PLL Filter Elements (Acquisition Mode)
Loop Bandwidth
[kHz]
Bandwidth
Limit [kHz]
Reference [MHz]
SYNR
Fbus [MHz] C [nF]
R [kΩ]
0.614
0.614
0.614
0.614
0.8
0.8
0.8
0.8
1
$0C
$0C
$0C
$0C
$09
$09
$09
$09
$07
$07
$07
$07
$05
$05
$05
$05
$03
$03
$03
$03
$02
$02
$02
$02
$01
$01
$01
$01
7.98
7.98
7.98
7.98
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
8.00
1000
47
0.43
2
1.2
5.5
12
157
157
157
157
201
201
201
201
251
251
251
251
402
402
402
402
502
502
502
502
668
668
668
668
1005
1005
1005
1005
10
4.3
7.5
0.27
1.2
2.4
5.6
0.22
1
3.3
21
2200
100
22
0.9
4.4
9.3
20.1
1
4.7
2200
100
2.
1
4.8
10.4
22.5
1.1
6.2
10.7
19.5
1
1
2.2
4.7
0.15
0.82
1.5
2.7
0.1
0.51
1
1
4.7
1.6
1.6
1.6
1.6
2
3300
100
33
10
4700
220
47
2
4.6
10
2
2
10
2.4
0.12
0.43
1
21.8
1.7
5.3
11.6
25.1
2.1
5.4
9.7
20.8
2.66
2.66
2.66
2.66
4
2200
220
47
10
2
2200
330
100
22
0.1
0.27
0.51
1
4
4
4
8-cgmpa
MC68HC912DT128A Rev 2.0
384
Appendix B: CGM Practical Aspects
MOTOROLA
Appendix B: CGM Practical Aspects
Printed Circuit Board Guidelines
Printe d Circ uit Boa rd Guid e line s
Printed Circuit Boards (PCBs) are the board of choice for volume
applications. If designed correctly, a very low noise system can be built
on a PCB with consequently good EMI/EMC performances. If designed
incorrectly, PCBs can be extremely noisy and sensitive modules, and
the CGM could be disrupted. Some common sense rules can be used to
prevent such problems.
•
Use a ‘star’ style power routing plan as opposed to a ‘daisy chain’.
Route power and ground from a central location to each chip
individually, and use the widest trace practical (the more the chip
draws current, the wider the trace). NEVER place the MCU at the
end of a long string of serially connected chips.
•
When using PCB layout software, first direct the routing of the
power supply lines as well as the CGM wires (crystal oscillator and
PLL). Layout constraints must be then reported on the other
signals and not on these ‘hot’ nodes. Optimizing the ‘hot’ nodes at
the end of the routing process usually gives bad results.
•
•
Avoid notches in power traces. These notches not only add
resistance (and are not usually accounted for in simulations), but
they can also add unnecessary transmission line effects.
Avoid ground and power loops. This has been one of the most
violated guidelines of PCB layout. Loops are excellent noise
transmitters and can be easily avoided. When using multiple layer
PCBs, the power and ground plane concept works well but only
when strictly adhered to (do not compromise the ground plane by
cutting a hole in it and running signals on the ground plane layer).
Keep the spacing around via holes to a minimum (but not so small
as to add capacitive effects).
•
•
Be aware of the three dimensional capacitive effects of
multi-layered PCBs.
Bypass (decouple) the power supplies of all chips as close to the
chip as possible. Use one decoupling capacitor per power supply
pair (VDD/VSS, VDDX/VSSX...). Two capacitors with a ratio of
about 100 sometimes offer better performances over a broader
9-cgmpa
MC68HC912DT128A Rev 2.0
MOTOROLA
Appendix B: CGM Practical Aspects
385
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
spectrum. This is especially the case for the power supply pins
close to the E port, when the E clock and/or the calibration clock
are used.
•
•
On the general VDD power supply input, a ‘T’ low pass filter LCL
can be used (e.g. 10µH-47µF-10µH). The ‘T’ is preferable to the
‘Π’ version as the exhibited impedance is more constant with
respect to the VDD current. Like many modular micro controllers,
HC12 devices have a power consumption which not only varies
with clock edges but also with the functioning modes.
Keep high speed clock and bus trace length to a minimum. The
higher the clock speed, the shorter the trace length. If noisy
signals are sent over long tracks, impedance adjustments should
be considered at both ends of the line (generally, simple resistors
suffice).
•
•
Bus drivers like the CAN physical interface should be installed
close to their connector, with dedicated filtering on their power
supply.
Mount components as close to the board as possible. Snip excess
lead length as close to the board as possible. Preferably use
Surface Mount Devices (SMDs).
•
•
Mount discrete components as close to the chip that uses them as
possible.
Do not cross sensitive signals ON ANY LAYER. If a sensitive
signal must be crossed by another signal, do it as many layers
away as possible and at right angles.
•
•
Always keep PCBs clean. Solder flux, oils from fingerprints,
humidity and general dirt can conduct electricity. Sensitive circuits
can easily be disrupted by small amounts of leakage.
Choose PCB coatings with care. Certain epoxies, paints, gelatins,
plastics and waxes can conduct electricity. If the manufacturer
cannot provide the electrical characteristics of the substance, do
not use it.
10-cgmpa
MC68HC912DT128A Rev 2.0
386
Appendix B: CGM Practical Aspects
MOTOROLA
Appendix B: CGM Practical Aspects
Printed Circuit Board Guidelines
In addition to the above general pieces of advice, the following
guidelines should be followed for the CGM pins (but also more generally
for any sensitive analog circuitry):
•
•
Mount the PLL filter and oscillator components as close to the
MCU as possible.
Do not allow the EXTAL and XTAL signals to interfere with the
XFC node. Keep these tracks as short as possible.
•
•
Do not cross the CGM signals with any other signal on any level.
Remember that the reference voltage for the XFC filter is
VDDPLL.
•
As the return path for the oscillator circuitry is VSSPLL, it is
extremely important to CONNECT VSSPLL to VSS even if the
PLL is not to be powered.Surface mount components reduce the
susceptibility of signal contamination.
•
Ceramic resonators with built-in capacitors are available. This is
an interesting solution because the parasitic components involved
are minimized due to the close proximity of the resonating
elements.
11-cgmpa
MC68HC912DT128A Rev 2.0
MOTOROLA
Appendix B: CGM Practical Aspects
387
Ap p e nd ix B: CGM Pra c tic a l Asp e c ts
12-cgmpa
MC68HC912DT128A Rev 2.0
388
Appendix B: CGM Practical Aspects
MOTOROLA
Glossa ry
Glossa ry
A — See “accumulators (A and B or D).”
accumulators (A and B or D) — Two 8-bit (A and B) or one 16-bit (D) general-purpose registers
in the CPU. The CPU uses the accumulators to hold operands and results of arithmetic
and logic operations.
acquisition mode — A mode of PLL operation with large loop bandwidth. Also see ’tracking
mode’.
address bus — The set of wires that the CPU or DMA uses to read and write memory locations.
addressing mode — The way that the CPU determines the operand address for an instruction.
The M68HC12 CPU has 15 addressing modes.
ALU — See “arithmetic logic unit (ALU).”
analogue-to-digital converter (ATD) — The ATD module is an 8-channel, multiplexed-input
successive-approximation analog-to-digital converter.
arithmetic logic unit (ALU) — The portion of the CPU that contains the logic circuitry to perform
arithmetic, logic, and manipulation operations on operands.
asynchronous — Refers to logic circuits and operations that are not synchronized by a common
reference signal.
ATD — See “analogue-to-digital converter”.
MC68HC912DT128A Rev 1.0
MOTOROLA
Glossary
389
Glossa ry
B — See “accumulators (A and B or D).”
baud rate — The total number of bits transmitted per unit of time.
BCD — See “binary-coded decimal (BCD).”
binary — Relating to the base 2 number system.
binary number system — The base 2 number system, having two digits, 0 and 1. Binary
arithmetic is convenient in digital circuit design because digital circuits have two
permissible voltage levels, low and high. The binary digits 0 and 1 can be interpreted to
correspond to the two digital voltage levels.
binary-coded decimal (BCD) — A notation that uses 4-bit binary numbers to represent the 10
decimal digits and that retains the same positional structure of a decimal number. For
example,
234 (decimal) = 0010 0011 0100 (BCD)
bit — A binary digit. A bit has a value of either logic 0 or logic 1.
branch instruction — An instruction that causes the CPU to continue processing at a memory
location other than the next sequential address.
break module — The break module allows software to halt program execution at a
programmable point in order to enter a background routine.
breakpoint — A number written into the break address registers of the break module. When a
number appears on the internal address bus that is the same as the number in the break
address registers, the CPU executes the software interrupt instruction (SWI).
break interrupt — A software interrupt caused by the appearance on the internal address bus
of the same value that is written in the break address registers.
bus — A set of wires that transfers logic signals.
bus clock — See "CPU clock".
byte — A set of eight bits.
MC68HC912DT128A Rev 1.0
390
Glossary
MOTOROLA
Glossary
CAN — See "Motorola scalable CAN."
CCR — See “condition code register.”
central processor unit (CPU) — The primary functioning unit of any computer system. The
CPU controls the execution of instructions.
CGM — See “clock generator module (CGM).”
clear — To change a bit from logic 1 to logic 0; the opposite of set.
clock — A square wave signal used to synchronize events in a computer.
clock generator module (CGM) — The CGM module generates a base clock signal from which
the system clocks are derived. The CGM may include a crystal oscillator circuit and/or
phase-locked loop (PLL) circuit.
comparator — A device that compares the magnitude of two inputs. A digital comparator defines
the equality or relative differences between two binary numbers.
computer operating properly module (COP) — A counter module that resets the MCU if
allowed to overflow.
condition code register (CCR) — An 8-bit register in the CPU that contains the interrupt mask
bit and five bits that indicate the results of the instruction just executed.
control bit — One bit of a register manipulated by software to control the operation of the
module.
control unit — One of two major units of the CPU. The control unit contains logic functions that
synchronize the machine and direct various operations. The control unit decodes
instructions and generates the internal control signals that perform the requested
operations. The outputs of the control unit drive the execution unit, which contains the
arithmetic logic unit (ALU), CPU registers, and bus interface.
MC68HC912DT128A Rev 1.0
MOTOROLA
Glossary
391
Glossa ry
COP — See "computer operating properly module (COP)."
CPU — See “central processor unit (CPU).”
CPU12 — The CPU of the MC68HC12 Family.
CPU clock — Bus clock select bits BCSP and BCSS in the clock select register (CLKSEL)
determine which clock drives SYSCLK for the main system, including the CPU and buses.
When EXTALi drives the SYSCLK, the CPU or bus clock frequency (fo) is equal to the
EXTALi frequency divided by 2.
CPU cycles — A CPU cycle is one period of the internal bus clock, normally derived by dividing
a crystal oscillator source by two or more so the high and low times will be equal. The
length of time required to execute an instruction is measured in CPU clock cycles.
CPU registers — Memory locations that are wired directly into the CPU logic instead of being
part of the addressable memory map. The CPU always has direct access to the
information in these registers. The CPU registers in an M68HC12 are:
•
•
A (8-bit accumulator)
B (8-bit accumulator)
–
D (16-bit accumulator formed by concatenation of accumulators A and B)
•
•
•
•
•
IX (16-bit index register)
IY (16-bit index register)
SP (16-bit stack pointer)
PC (16-bit program counter)
CCR (8-bit condition code register)
cycle time — The period of the operating frequency: tCYC = 1/fOP.
D — See “accumulators (A and B or D).”
decimal number system — Base 10 numbering system that uses the digits zero through nine.
duty cycle — A ratio of the amount of time the signal is on versus the time it is off. Duty cycle is
usually represented by a percentage.
MC68HC912DT128A Rev 1.0
392
Glossary
MOTOROLA
Glossary
ECT — See “enhanced capture timer.”
EEPROM — Electrically erasable, programmable, read-only memory. A nonvolatile type of
memory that can be electrically erased and reprogrammed.
EPROM — Erasable, programmable, read-only memory. A nonvolatile type of memory that can
be erased by exposure to an ultraviolet light source and then reprogrammed.
enhanced capture timer (ECT) — The HC12 Enhanced Capture Timer module has the features
of the HC12 Standard Timer module enhanced by additional features in order to enlarge
the field of applications.
exception — An event such as an interrupt or a reset that stops the sequential execution of the
instructions in the main program.
fetch — To copy data from a memory location into the accumulator.
firmware — Instructions and data programmed into nonvolatile memory.
flash EEPROM — Electrically erasable, programmable, read-only memory. A nonvolatile type of
memory that can be electrically erased and reprogrammed. Does not support byte or word
erase.
free-running counter — A device that counts from zero to a predetermined number, then rolls
over to zero and begins counting again.
full-duplex transmission — Communication on a channel in which data can be sent and
received simultaneously.
hexadecimal — Base 16 numbering system that uses the digits 0 through 9 and the letters A
through F.
high byte — The most significant eight bits of a word.
illegal address — An address not within the memory map
illegal opcode — A nonexistent opcode.
index registers (IX and IY) — Two 16-bit registers in the CPU. In the indexed addressing
modes, the CPU uses the contents of IX or IY to determine the effective address of the
operand. IX and IY can also serve as a temporary data storage locations.
input/output (I/O) — Input/output interfaces between a computer system and the external world.
A CPU reads an input to sense the level of an external signal and writes to an output to
change the level on an external signal.
MC68HC912DT128A Rev 1.0
MOTOROLA
Glossary
393
Glossa ry
instructions — Operations that a CPU can perform. Instructions are expressed by programmers
as assembly language mnemonics. A CPU interprets an opcode and its associated
operand(s) and instruction.
interrupt — A temporary break in the sequential execution of a program to respond to signals
from peripheral devices by executing a subroutine.
interrupt request — A signal from a peripheral to the CPU intended to cause the CPU to
execute a subroutine.
I/O — See “input/output (I/0).”
jitter — Short-term signal instability.
latch — A circuit that retains the voltage level (logic 1 or logic 0) written to it for as long as power
is applied to the circuit.
latency — The time lag between instruction completion and data movement.
least significant bit (LSB) — The rightmost digit of a binary number.
logic 1 — A voltage level approximately equal to the input power voltage (VDD).
logic 0 — A voltage level approximately equal to the ground voltage (VSS).
low byte — The least significant eight bits of a word.
M68HC12 — A Motorola family of 16-bit MCUs.
mark/space — The logic 1/logic 0 convention used in formatting data in serial communication.
mask — 1. A logic circuit that forces a bit or group of bits to a desired state. 2. A photomask used
in integrated circuit fabrication to transfer an image onto silicon.
MCU — Microcontroller unit. See “microcontroller.”
memory location — Each M68HC12 memory location holds one byte of data and has a unique
address. To store information in a memory location, the CPU places the address of the
location on the address bus, the data information on the data bus, and asserts the write
signal. To read information from a memory location, the CPU places the address of the
location on the address bus and asserts the read signal. In response to the read signal,
the selected memory location places its data onto the data bus.
memory map — A pictorial representation of all memory locations in a computer system.
MC68HC912DT128A Rev 1.0
394
Glossary
MOTOROLA
Glossary
MI-Bus — See "Motorola interconnect bus".
microcontroller — Microcontroller unit (MCU). A complete computer system, including a CPU,
memory, a clock oscillator, and input/output (I/O) on a single integrated circuit.
modulo counter — A counter that can be programmed to count to any number from zero to its
maximum possible modulus.
most significant bit (MSB) — The leftmost digit of a binary number.
Motorola interconnect bus (MI-Bus) — The Motorola Interconnect Bus (MI Bus) is a serial
communications protocol which supports distributed real-time control efficiently and with
a high degree of noise immunity.
Motorola scalable CAN (msCAN) — The Motorola scalable controller area network is a serial
communications protocol that efficiently supports distributed real-time control with a very
high level of data integrity.
msCAN — See "Motorola scalable CAN".
MSI — See "multiple serial interface".
multiple serial interface — A module consisting of multiple independent serial I/O sub-systems,
e.g. two SCI and one SPI.
multiplexer — A device that can select one of a number of inputs and pass the logic level of that
input on to the output.
nibble — A set of four bits (half of a byte).
object code — The output from an assembler or compiler that is itself executable machine code,
or is suitable for processing to produce executable machine code.
opcode — A binary code that instructs the CPU to perform an operation.
open-drain — An output that has no pullup transistor. An external pullup device can be
connected to the power supply to provide the logic 1 output voltage.
operand — Data on which an operation is performed. Usually a statement consists of an
operator and an operand. For example, the operator may be an add instruction, and the
operand may be the quantity to be added.
oscillator — A circuit that produces a constant frequency square wave that is used by the
computer as a timing and sequencing reference.
MC68HC912DT128A Rev 1.0
MOTOROLA
Glossary
395
Glossa ry
OTPROM — One-time programmable read-only memory. A nonvolatile type of memory that
cannot be reprogrammed.
overflow — A quantity that is too large to be contained in one byte or one word.
page zero — The first 256 bytes of memory (addresses $0000–$00FF).
parity — An error-checking scheme that counts the number of logic 1s in each byte transmitted.
In a system that uses odd parity, every byte is expected to have an odd number of logic
1s. In an even parity system, every byte should have an even number of logic 1s. In the
transmitter, a parity generator appends an extra bit to each byte to make the number of
logic 1s odd for odd parity or even for even parity. A parity checker in the receiver counts
the number of logic 1s in each byte. The parity checker generates an error signal if it finds
a byte with an incorrect number of logic 1s.
PC — See “program counter (PC).”
peripheral — A circuit not under direct CPU control.
phase-locked loop (PLL) — A clock generator circuit in which a voltage controlled oscillator
produces an oscillation which is synchronized to a reference signal.
PLL — See "phase-locked loop (PLL)."
pointer — Pointer register. An index register is sometimes called a pointer register because its
contents are used in the calculation of the address of an operand, and therefore points to
the operand.
polarity — The two opposite logic levels, logic 1 and logic 0, which correspond to two different
voltage levels, VDD and VSS.
polling — Periodically reading a status bit to monitor the condition of a peripheral device.
port — A set of wires for communicating with off-chip devices.
prescaler — A circuit that generates an output signal related to the input signal by a fractional
scale factor such as 1/2, 1/8, 1/10 etc.
MC68HC912DT128A Rev 1.0
396
Glossary
MOTOROLA
Glossary
program — A set of computer instructions that cause a computer to perform a desired operation
or operations.
program counter (PC) — A 16-bit register in the CPU. The PC register holds the address of the
next instruction or operand that the CPU will use.
pull — An instruction that copies into the accumulator the contents of a stack RAM location. The
stack RAM address is in the stack pointer.
pullup — A transistor in the output of a logic gate that connects the output to the logic 1 voltage
of the power supply.
pulse-width — The amount of time a signal is on as opposed to being in its off state.
pulse-width modulation (PWM) — Controlled variation (modulation) of the pulse width of a
signal with a constant frequency.
push — An instruction that copies the contents of the accumulator to the stack RAM. The stack
RAM address is in the stack pointer.
PWM period — The time required for one complete cycle of a PWM waveform.
RAM — Random access memory. All RAM locations can be read or written by the CPU. The
contents of a RAM memory location remain valid until the CPU writes a different value or
until power is turned off.
RC circuit — A circuit consisting of capacitors and resistors having a defined time constant.
read — To copy the contents of a memory location to the accumulator.
register — A circuit that stores a group of bits.
reserved memory location — A memory location that is used only in special factory test modes.
Writing to a reserved location has no effect. Reading a reserved location returns an
unpredictable value.
reset — To force a device to a known condition.
ROM — Read-only memory. A type of memory that can be read but cannot be changed (written).
The contents of ROM must be specified before manufacturing the MCU.
MC68HC912DT128A Rev 1.0
MOTOROLA
Glossary
397
Glossa ry
SCI — See "serial communication interface module (SCI)."
serial — Pertaining to sequential transmission over a single line.
serial communications interface module (SCI) — A module that supports asynchronous
communication.
serial peripheral interface module (SPI) — A module that supports synchronous
communication.
set — To change a bit from logic 0 to logic 1; opposite of clear.
shift register — A chain of circuits that can retain the logic levels (logic 1 or logic 0) written to
them and that can shift the logic levels to the right or left through adjacent circuits in the
chain.
signed — A binary number notation that accommodates both positive and negative numbers.
The most significant bit is used to indicate whether the number is positive or negative,
normally logic 0 for positive and logic 1 for negative. The other seven bits indicate the
magnitude of the number.
software — Instructions and data that control the operation of a microcontroller.
software interrupt (SWI) — An instruction that causes an interrupt and its associated vector
fetch.
SPI — See "serial peripheral interface module (SPI)."
stack — A portion of RAM reserved for storage of CPU register contents and subroutine return
addresses.
stack pointer (SP) — A 16-bit register in the CPU containing the address of the next available
storage location on the stack.
start bit — A bit that signals the beginning of an asynchronous serial transmission.
status bit — A register bit that indicates the condition of a device.
stop bit — A bit that signals the end of an asynchronous serial transmission.
MC68HC912DT128A Rev 1.0
398
Glossary
MOTOROLA
Glossary
subroutine — A sequence of instructions to be used more than once in the course of a program.
The last instruction in a subroutine is a return from subroutine (RTS) instruction. At each
place in the main program where the subroutine instructions are needed, a jump or branch
to subroutine (JSR or BSR) instruction is used to call the subroutine. The CPU leaves the
flow of the main program to execute the instructions in the subroutine. When the RTS
instruction is executed, the CPU returns to the main program where it left off.
synchronous — Refers to logic circuits and operations that are synchronized by a common
reference signal.
timer — A module used to relate events in a system to a point in time.
toggle — To change the state of an output from a logic 0 to a logic 1 or from a logic 1 to a logic 0.
tracking mode — A mode of PLL operation with narrow loop bandwidth. Also see ‘acquisition
mode.’
two’s complement — A means of performing binary subtraction using addition techniques. The
most significant bit of a two’s complement number indicates the sign of the number (1
indicates negative). The two’s complement negative of a number is obtained by inverting
each bit in the number and then adding 1 to the result.
unbuffered — Utilizes only one register for data; new data overwrites current data.
unimplemented memory location — A memory location that is not used. Writing to an
unimplemented location has no effect. Reading an unimplemented location returns an
unpredictable value.
variable — A value that changes during the course of program execution.
VCO — See "voltage-controlled oscillator."
vector — A memory location that contains the address of the beginning of a subroutine written
to service an interrupt or reset.
voltage-controlled oscillator (VCO) — A circuit that produces an oscillating output signal of a
frequency that is controlled by a dc voltage applied to a control input.
waveform — A graphical representation in which the amplitude of a wave is plotted against time.
wired-OR — Connection of circuit outputs so that if any output is high, the connection point is
high.
word — A set of two bytes (16 bits).
write — The transfer of a byte of data from the CPU to a memory location.
MC68HC912DT128A Rev 1.0
MOTOROLA
Glossary
399
Glossa ry
MC68HC912DT128A Rev 1.0
400
Glossary
MOTOROLA
Lite ra ture Up d a te s
Lite ra ture Up d a te s
This document contains the latest data available at publication time. For
updates, contact one of the centers listed below:
Lite ra ture Distrib ution Ce nte rs
Order literature by mail or phone.
USA/ Europ e
Motorola Literature Distribution
P.O. Box 5405
Denver, Colorado, 80217
Phone 1-303-675-2140
Ja p a n
Motorola Japan Ltd.
Tatsumi-SPD-JLDC
Toshikatsu Otsuki
6F Seibu-Butsuryu Center
3-14-2 Tatsumi Koto-Ku
Tokyo 135, Japan
Phone 03-3521-8315
Hong Kong
Motorola Semiconductors H.K. Ltd.
8B Tai Ping Industrial Park
51 Ting Kok Road
Tai Po, N.T., Hong Kong
Phone 852-26629298
MC68HC912DT128A Rev 2.0
401
MOTOROLA
Literature Updates
Lite ra ture Up d a te s
Custom e r Foc us Ce nte r
1-800-521-6274
Mic roc ontrolle r Division’s We b Site
Directly access the Microcontroller Division’s web site with the following
URL:
http://mcu.motsps.com/
MC68HC912DT128A Rev 2.0
402
Literature Updates
MOTOROLA
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Motorola reserves the right to make changes without further notice to any products herein. Motorola makes no warranty, representation or guarantee regarding the
suitability of its products for any particular purpose, nor does Motorola 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 which may be provided in Motorola
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. Motorola does not convey any license under its patent rights nor the rights of
others. Motorola 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 Motorola product could create a situation where personal injury
or death may occur. Should Buyer purchase or use Motorola products for any such unintended or unauthorized application, Buyer shall indemnify and hold Motorola
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 Motorola was
negligent regarding the design or manufacture of the part. Motorola and
Opportunity/Affirmative Action Employer.
are registered trademarks of Motorola, Inc. Motorola, Inc. is an Equal
How to reach us:
USA/EUROPE: Motorola Literature Distribution; P.O. Box 5405, Denver, Colorado 80217. 1-303-675-2140
JAPAN: Motorola Japan Ltd.; Tatsumi-SPD-JLDC, 6F Seibu-Butsuryu-Center, 3-14-2 Tatsumi Koto-Ku,
Tokyo 135, Japan. 81-3-3521-8315
HONG KONG: Motorola Semiconductors H.K. Ltd.; 8B Tai Ping Industrial Park, 51 Ting Kok Road, Tai Po, N.T.,
Hong Kong. 852-26629298
CUSTOMER FOCUS CENTER: 1-800-521-6274
© Motorola, Inc., 1999
MC68HC912DT128A/ D
相关型号：
©2020 ICPDF网 联系我们和版权申明