MC9S12KC64CPU

MC9S12KG128 Data Sheet HCS12 Microcontrollers MC9S12KG128 Rev. 1.15 06/2006 freescale.com MC9S12KG128 Data Sheet MC9S12KG128V1 Rev. Rev. 1.15 06/2006 To provide the most up-to-date information, the revision of our documents on the World Wide Web will be the most current. Your printed copy may be an earlier revision. To verify you have the latest information available, refer to: http://freescale.com/ The following revision history table summarizes changes contained in this document. Revision History Date Oct 21, 2005 Jun 23, 2006 Revision Level Rev. 1.14 Rev. 1.15 New data sheet 1. Update PE0/PE1 pull up/down status in table 1_2 2. Update Vreg_3v3 V(lvia)/V(lvid) limit in table A-9 3. Other minor update. Description Freescale™ and the Freescale logo are trademarks of Freescale Semiconductor, Inc. This product incorporates SuperFlash® technology licensed from SST. © Freescale Semiconductor, Inc., 2005,2006 All rights reserved. MC9S12KG128 Data Sheet, Rev. 1.15 4 Freescale Semiconductor Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14 Chapter 15 Chapter 16 Chapter 17 Chapter 18 Chapter 19 MC9S12KG128 Device Overview (MC9S12KG128V1) . . . . . . . 19 128 Kbyte ECC Flash Module (FTS128K1ECCV1) . . . . . . . . . . 75 2 Kbyte EEPROM Module (EETS2KV1). . . . . . . . . . . . . . . . . . 117 Port Integration Module (PIM9KG128V1) . . . . . . . . . . . . . . . . 137 Clocks and Reset Generator (CRGV4) . . . . . . . . . . . . . . . . . . 177 Pierce Oscillator (S12OSCLCPV1) . . . . . . . . . . . . . . . . . . . . . 213 Analog-to-Digital Converter (ATD10B16CV1) . . . . . . . . . . . . 219 Inter-Integrated Circuit (IICV2) . . . . . . . . . . . . . . . . . . . . . . . . 247 Freescale’s Scalable Controller Area Network (MSCANV2) . 271 Serial Communications Interface (SCIV1) . . . . . . . . . . . . . . . 325 Serial Peripheral Interface (SPIV3) . . . . . . . . . . . . . . . . . . . . . 357 Pulse-Width Modulator (PWM8B8CV1). . . . . . . . . . . . . . . . . . 379 Timer Module (TIM16B8CV1) . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Dual Output Voltage Regulator (VREG3V3V2). . . . . . . . . . . . 437 Background Debug Module (BDMV4). . . . . . . . . . . . . . . . . . . 445 Debug Module (DBGV1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Interrupt (INTV1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 Multiplexed External Bus Interface (MEBIV3) . . . . . . . . . . . . 511 Module Mapping Control (MMCV4) . . . . . . . . . . . . . . . . . . . . . 539 Appendix A Electrical Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Appendix B Recommended PCB Layout . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Appendix C Package Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 5 MC9S12KG128 Data Sheet, Rev. 1.15 6 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 1.1.3 MC9S12KG128 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1.2.1 Signal Properties Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 1.2.2 Detailed Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 1.2.3 Power Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.3.1 Device Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.3.2 Detailed Register Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 1.3.3 Part ID Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 System Clock Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 1.5.1 Chip Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 1.5.2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 1.5.3 Low Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Resets and Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 1.6.1 Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 1.6.2 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 1.2 1.3 1.4 1.5 1.6 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 2.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 2.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 2.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 2.4.1 Flash Command Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.5.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.5.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.5.3 Background Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 7 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Flash Module Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.6.1 Unsecuring the MCU using Backdoor Key Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 2.6.2 Unsecuring the Flash Module in Special Single-Chip Mode using BDM . . . . . . . . . . . 114 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 2.7.1 Flash Reset Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 2.7.2 Reset While Flash Command Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 2.8.1 Description of Flash Interrupt Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 3.4.1 Program and Erase Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 3.5.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 3.5.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 3.5.3 Background Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 3.2 3.3 3.4 3.5 3.6 3.7 Chapter 4 Port Integration Module (PIM9KG128V1) 4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 4.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 4.1.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 4.2.1 Signal Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 4.3.1 Port T Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 4.3.2 Port S Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 4.3.3 Port M Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 4.3.4 Port P Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 4.3.5 Port H Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 4.3.6 Port J Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 4.2 4.3 4.4 MC9S12KG128 Data Sheet, Rev. 1.15 8 Freescale Semiconductor 4.5 4.6 4.4.1 I/O Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 4.4.2 Input Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 4.4.3 Data Direction Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 4.4.4 Reduced Drive Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 4.4.5 Pull Device Enable Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 4.4.6 Polarity Select Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 4.4.7 Pin Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.5.1 Reset Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.6.2 Interrupt Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 4.6.3 Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Chapter 5 Clocks and Reset Generator (CRGV4) 5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 5.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.2.1 VDDPLL, VSSPLL — PLL Operating Voltage, PLL Ground . . . . . . . . . . . . . . . . . . . . . . 179 5.2.2 XFC — PLL Loop Filter Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.2.3 RESET — Reset Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 5.4.1 Phase Locked Loop (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 5.4.2 System Clocks Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 5.4.3 Clock Monitor (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 5.4.4 Clock Quality Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 5.4.5 Computer Operating Properly Watchdog (COP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 5.4.6 Real-Time Interrupt (RTI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 5.4.7 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 5.4.8 Low-Power Operation in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 5.4.9 Low-Power Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 5.4.10 Low-Power Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 5.5.1 Clock Monitor Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 5.5.2 Computer Operating Properly Watchdog (COP) Reset . . . . . . . . . . . . . . . . . . . . . . . . . 210 5.5.3 Power-On Reset, Low Voltage Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 5.6.1 Real-Time Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 5.6.2 PLL Lock Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 9 5.2 5.3 5.4 5.5 5.6 5.6.3 Self-Clock Mode Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Chapter 6 Pierce Oscillator (S12OSCLCPV1) 6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 6.2.1 VDDPLL and VSSPLL — Operating and Ground Voltage Pins . . . . . . . . . . . . . . . . . . . . 214 6.2.2 EXTAL and XTAL — Input and Output Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 6.2.3 XCLKS — Input Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.4.1 Gain Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.4.2 Clock Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.4.3 Wait Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 6.4.4 Stop Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 6.2 6.3 6.4 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 7.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 7.1.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 7.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 7.2.1 Detailed Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 7.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 7.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.4.1 Analog Sub-Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.4.2 Digital Sub-Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 7.2 7.3 7.4 7.5 7.6 MC9S12KG128 Data Sheet, Rev. 1.15 10 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 8.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 8.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 8.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.2.1 IIC_SCL — Serial Clock Line Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.2.2 IIC_SDA — Serial Data Line Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 8.4.1 I-Bus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 8.4.2 Operation in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 8.4.3 Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 8.4.4 Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.7.1 IIC Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.2 8.3 8.4 8.5 8.6 8.7 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 9.1.1 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 9.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 9.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 9.2.1 RXCAN — CAN Receiver Input Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 9.2.2 TXCAN — CAN Transmitter Output Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9.2.3 CAN System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 9.3.3 Programmer’s Model of Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 9.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 9.4.2 Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 9.4.3 Identifier Acceptance Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 9.4.4 Timer Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 9.4.5 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 9.4.6 Low-Power Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 9.4.7 Reset Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 9.2 9.3 9.4 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 11 9.5 9.4.8 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Initialization/Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 9.5.1 MSCAN initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Chapter 10 Serial Communications Interface (SCIV1) 10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 10.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 10.1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 10.1.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 10.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 10.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 10.2.1 TXD-SCI Transmit Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 10.2.2 RXD-SCI Receive Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 10.3 Memory Map and Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 10.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 10.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 10.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 10.4.1 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 10.4.2 Baud Rate Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 10.4.3 Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 10.4.4 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 10.4.5 Single-Wire Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.4.6 Loop Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.5 Initialization Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.5.1 Reset Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.5.2 Interrupt Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 10.5.3 Recovery from Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Chapter 11 Serial Peripheral Interface (SPIV3) 11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 11.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 11.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 11.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 11.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 11.2.1 MOSI — Master Out/Slave In Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 11.2.2 MISO — Master In/Slave Out Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.2.3 SS — Slave Select Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.2.4 SCK — Serial Clock Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 11.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 MC9S12KG128 Data Sheet, Rev. 1.15 12 Freescale Semiconductor 11.4.1 Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 11.4.2 Slave Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 11.4.3 Transmission Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 11.4.4 SPI Baud Rate Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 11.4.5 Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 11.4.6 Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 11.4.7 Operation in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 11.4.8 Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 11.4.9 Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 11.5 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6.1 MODF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6.2 SPIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6.3 SPTEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 12.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 12.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 12.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2.1 PWM7 — PWM Channel 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2.2 PWM6 — PWM Channel 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2.3 PWM5 — PWM Channel 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.4 PWM4 — PWM Channel 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.5 PWM3 — PWM Channel 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.6 PWM3 — PWM Channel 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.7 PWM3 — PWM Channel 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.8 PWM3 — PWM Channel 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 12.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 12.4.1 PWM Clock Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 12.4.2 PWM Channel Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 12.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 12.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 13 Chapter 13 Timer Module (TIM16B8CV1) 13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 13.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 13.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 13.1.3 Block Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 13.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 13.2.1 IOC7 — Input Capture and Output Compare Channel 7 Pin . . . . . . . . . . . . . . . . . . . . 414 13.2.2 IOC6 — Input Capture and Output Compare Channel 6 Pin . . . . . . . . . . . . . . . . . . . . 414 13.2.3 IOC5 — Input Capture and Output Compare Channel 5 Pin . . . . . . . . . . . . . . . . . . . . 414 13.2.4 IOC4 — Input Capture and Output Compare Channel 4 Pin . . . . . . . . . . . . . . . . . . . . 414 13.2.5 IOC3 — Input Capture and Output Compare Channel 3 Pin . . . . . . . . . . . . . . . . . . . . 414 13.2.6 IOC2 — Input Capture and Output Compare Channel 2 Pin . . . . . . . . . . . . . . . . . . . . 415 13.2.7 IOC1 — Input Capture and Output Compare Channel 1 Pin . . . . . . . . . . . . . . . . . . . . 415 13.2.8 IOC0 — Input Capture and Output Compare Channel 0 Pin . . . . . . . . . . . . . . . . . . . . 415 13.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 13.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 13.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 13.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 13.4.1 Prescaler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 13.4.2 Input Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 13.4.3 Output Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 13.4.4 Pulse Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 13.4.5 Event Counter Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.4.6 Gated Time Accumulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.6.1 Channel [7:0] Interrupt (C[7:0]F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 13.6.2 Pulse Accumulator Input Interrupt (PAOVI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 13.6.3 Pulse Accumulator Overflow Interrupt (PAOVF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 13.6.4 Timer Overflow Interrupt (TOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 14.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 14.2.1 VDDR — Regulator Power Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 14.2.2 VDDA, VSSA — Regulator Reference Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 14.2.3 VDD, VSS — Regulator Output1 (Core Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.2.4 VDDPLL, VSSPLL — Regulator Output2 (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.2.5 VREGEN — Optional Regulator Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 MC9S12KG128 Data Sheet, Rev. 1.15 14 Freescale Semiconductor 14.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.4.1 REG — Regulator Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.4.2 Full-Performance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.3 Reduced-Power Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.4 LVD — Low-Voltage Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.5 POR — Power-On Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.6 LVR — Low-Voltage Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.7 CTRL — Regulator Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.5.1 Power-On Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.5.2 Low-Voltage Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.6.1 LVI — Low-Voltage Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Chapter 15 Background Debug Module (BDMV4) 15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 15.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 15.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 15.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 15.2.1 BKGD — Background Interface Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 15.2.2 TAGHI — High Byte Instruction Tagging Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 15.2.3 TAGLO — Low Byte Instruction Tagging Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 15.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 15.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 15.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 15.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 15.4.1 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 15.4.2 Enabling and Activating BDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 15.4.3 BDM Hardware Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 15.4.4 Standard BDM Firmware Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 15.4.5 BDM Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 15.4.6 BDM Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 15.4.7 Serial Interface Hardware Handshake Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 15.4.8 Hardware Handshake Abort Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 15.4.9 SYNC — Request Timed Reference Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 15.4.10Instruction Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 15.4.11Instruction Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 15.4.12Serial Communication Time-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 15.4.13Operation in Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 15.4.14Operation in Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 15 Chapter 16 Debug Module (DBGV1) 16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 16.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 16.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 16.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 16.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 16.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 16.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 16.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 16.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 16.4.1 DBG Operating in BKP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 16.4.2 DBG Operating in DBG Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 16.4.3 Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 16.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 16.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 Chapter 17 Interrupt (INTV1) 17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 17.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 17.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 17.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 17.4.1 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 17.5 Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6.1 Interrupt Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6.2 Highest Priority I-Bit Maskable Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6.3 Interrupt Priority Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.7 Exception Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 MC9S12KG128 Data Sheet, Rev. 1.15 16 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 18.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 18.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 18.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 18.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 18.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 18.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 18.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 18.4.1 Detecting Access Type from External Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 18.4.2 Stretched Bus Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 18.4.3 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 18.4.4 Internal Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 18.4.5 Low-Power Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 Chapter 19 Module Mapping Control (MMCV4) 19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539 19.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.1.2 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.2 External Signal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.3 Memory Map and Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.3.1 Module Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.3.2 Register Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 19.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 19.4.1 Bus Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 19.4.2 Address Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 19.4.3 Memory Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 17 Appendix A Electrical Characteristics A.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 A.1.1 Parameter Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 A.1.2 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 A.1.3 Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 A.1.4 Current Injection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 A.1.5 Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 A.1.6 ESD Protection and Latch-up Immunity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 A.1.7 Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 A.1.8 Power Dissipation and Thermal Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564 A.1.9 I/O Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 A.1.10 Supply Currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 A.2 Voltage Regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 A.3 Chip Power-up and LVI/LVR Graphical Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 A.4 Output Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 A.4.1 Resistive Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 A.4.2 Capacitive Loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 A.5 ATD Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 A.5.1 ATD Operating Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 A.5.2 Factors Influencing Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 A.5.3 ATD Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 A.6 NVM, Flash and EEPROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 A.6.1 NVM Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 A.6.2 NVM Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 A.7 Reset, Oscillator and PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 A.7.1 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 A.7.2 Oscillator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 A.7.3 Phase Locked Loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 A.8 MSCAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 A.9 SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 A.9.1 Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 A.9.2 Slave Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 A.10 External Bus Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 A.10.1 General Muxed Bus Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 Appendix B Recommended PCB Layout Appendix C Package Information C.1 112-Pin LQFP Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 C.2 80-Pin QFP Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 MC9S12KG128 Data Sheet, Rev. 1.15 18 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.1 Introduction The MC9S12KG128 is a 112/80 pin 16-bit Flash-based microcontroller family targeted for high reliability systems. The MC9S12KG128 has an increased performance in reliability over the life of the product due to a built-in Error Checking and Correction Code (ECC) in the Flash memory. The program and erase operations automatically generate six parity bits per word making ECC transparent to the user. The MC9S12KG128 is comprised of standard on-chip peripherals including a 16-bit central processing unit (CPU12), 128K bytes of Flash EEPROM, 2K bytes of EEPROM, 8K bytes of RAM, two asynchronous serial communications interface (SCI), three serial peripheral interface (SPI), IIC-bus, an 8-channel IC/OC timer, one 16-channel 10-bit analog-to-digital converter (ADC), an 8-channel pulse-width modulator (PWM), two CAN 2.0 A, B software compatible modules, 29 discrete digital I/O channels (Port A, Port B, Port E and Port K), and 20 discrete digital I/O lines with interrupt and wakeup capability. The MC9S12KG128 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. 1.1.1 • Features HCS12 Core — 16-bit HCS12 CPU – Upward compatible with M68HC11 instruction set – Interrupt stacking and programmer’s model identical to M68HC11 – Instruction queue – Enhanced indexed addressing — MEBI (Multiplexed External Bus Interface) — MMC (Memory Map and Interface) — INT (Interrupt Controller) — DBG (Debugger) — BDM (Background Debug Mode) Oscillator — 4MHz to 16MHz frequency range — Pierce with amplitude loop control — Clock monitor • MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 19 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) • • Clock and Reset Generator (CRG) — Phase-locked loop clock frequency multiplier — Self Clock mode in absence of external clock — COP watchdog — Real Time interrupt (RTI) Memory — 128K Byte Flash EEPROM – Internal program/erase voltage generation – Security and Block Protect bits – Hamming Error Correction Coding (ECC) — 2K Byte EEPROM — 8K Byte static RAM Single-cycle misaligned word accesses without wait states Analog-to-Digital Converter (ADC) — One 16-channel module with 10-bit resolution — External conversion trigger capability 8-channel Timer (TIM) — Programmable input capture or output compare channels — Simple PWM mode — Counter Modulo Reset — External Event Counting — Gated Time Accumulation 8-channel Pulse Width Modulator (PWM) — Programmable period and duty cycle per channel — 8-bit 8-channel or 16-bit 4-channel — Edge and center aligned PWM signals — Emergency shutdown input Two 1M bit per second, CAN 2.0 A, B software compatible modules — Five receive and three transmit buffers — 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 — Low-pass filter wake-up function — Loop-back for self test operation Serial interfaces — Two asynchronous serial communication interface (SCI) — Three synchronous serial peripheral interface (SPI) — Inter-IC Bus (IIC) Internal 2.5V Regulator — Input voltage range from 3.15V to 5.5V MC9S12KG128 Data Sheet, Rev. 1.15 • • • • • • 20 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) • • • — Low power mode capability — Low Voltage Reset (LVR) and Low Voltage Interrupt (LVI) 20 key wake up inputs — Rising or falling edge triggered interrupt capability — Digital filter to prevent short pulses from triggering interrupts — Programmable pull ups and pull downs Operating frequency for ambient temperatures (TA -40°C to 125°C) — 50MHz equivalent to 25MHz Bus Speed 112-Pin LQFP or 80-Pin QFP package — I/O lines with 3.3V/5V input and drive capability — 3.3V/5V A/D converter inputs 1.1.2 • Modes of Operation Normal modes — Normal Single-Chip Mode — Normal Expanded Wide Mode — Normal Expanded Narrow Mode — Emulation Expanded Wide Mode — Emulation Expanded Narrow Mode Special Operating Modes — Special Single-Chip Mode with active Background Debug Mode — Special Test Mode (Freescale use only) — Special Peripheral Mode (Freescale use only) Each of the above modes of operation can be configured for three Low power submodes — Stop Mode — Pseudo Stop Mode — Wait Mode Secure operation, preventing the unauthorized read and write of the memory contents. • • • MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 21 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-1 shows a feature overview of the MC9S12KG128 members. Table 1-1. List of MC9S12KG128 members Device MC9S12KG128 MC9S12KL128 MC9S12KL64 MC9S12KL32 MC9S12KC128 MC9S12KC64 1 Temp Options1 Flash RAM EEPROM C, V, M C, V, M C, V, M C, V, M C, V, M C, V, M 128K 128K 64K 32K 128K 64K 8K 6K 4K 2K 6K 4K 2K 2K 1K 1K None None Package CAN SCI SPI IIC A/D2 PWM2 TIM2 I/O3 112 LQFP 80 QFP 112 LQFP 80 QFP 112 LQFP 80 QFP 80 QFP 112 LQFP 80 QFP 112 LQFP 80 QFP 2 2 1 1 1 1 1 1 1 1 1 2 2 2 1 2 1 1 2 1 2 1 3 3 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 1 16 8 16 8 16 8 8 16 8 16 8 8 7 8 7 8 7 7 8 7 8 7 8 8 8 8 8 8 8 8 8 8 8 91 59 91 59 91 59 59 91 59 91 59 C: TA = 85˚C, f = 25MHz. V: TA=105˚C, f = 25MHz. M: TA= 125˚C, f = 25MHz Number of channels 3 I/O is the sum of ports capable to act as digital input or output. 2 Figure 1-1 shows the part number coding based on the package and temperature options for the MC9S12KG128. MC9S12 KG128 C FU Package Option Temperature Option Device Title Controller Family Figure 1-1. Order Part number Coding Temperature Options C = -40˚C to 85˚C V = -40˚C to 105˚C M = -40˚C to 125˚C Package Options PV = 112LQFP FU = 80QFP MC9S12KG128 Data Sheet, Rev. 1.15 22 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.1.3 MC9S12KG128 Block Diagram 128K Byte Flash EEPROM 2K Byte EEPROM 8K Byte RAM AN00 AN01 AN02 AN03 AN04 AN05 AN06 AN07 PAD00 PAD01 PAD02 PAD03 PAD04 PAD05 PAD06 PAD07 AN08 AN09 AN10 AN11 AN12 AN13 AN14 AN15 ATD VRH VRL VDDA VSSA VRH VRL VDDA VSSA PAD08 PAD09 PAD10 PAD11 PAD12 PAD13 PAD14 PAD15 PK0 PK1 PK2 PK3 PK4 PK5 PK7 PT0 PT1 PT2 PT3 PT4 PT5 PT6 PT7 PS0 PS1 PS2 PS3 PS4 PS5 PS6 PS7 PM0 PM1 PM2 PM3 PM4 PM5 PM6 PM7 PJ0 PJ1 PJ6 PJ7 PP0 PP1 PP2 PP3 PP4 PP5 PP6 PP7 PH0 PH1 PH2 PH3 PH4 PH5 PH6 PH7 Signals shown in Bold are not available on n the 80-Pin Package XADDR14 XADDR15 XADDR16 XADDR17 XADDR18 XADDR19 ECS PAD VDDR VSSR VREGEN VDD1,2 VSS1,2 BKGD XTAL EXTAL VSSPLL VDDPLL XFC RESET PE0 PE1 PE2 PE3 PE4 PE5 PE6 PE7 TEST Voltage Regulator DDRK DDRT DDRS DDRM DDRJ DDRP DDRH PPAGE Single-Wire BDM OSC PLL CRG Breakpoints XIRQ Debugger IRQ R/W System LSTRB Integration ECLK Module MODA (SIM) MODB NOACC/XCLKS TIM Periodic Interrupt COP Watchdog Clock Monitor CPU12 PIX0 PIX1 PIX2 PIX3 PIX4 PIX5 ECS IOC0 IOC1 IOC2 IOC3 IOC4 IOC5 IOC6 IOC7 RXD TXD RXD TXD DDRE PTE SCI0 SCI1 MISO MOSI SCK SS SPI0 Multiplexed Address/Data Bus CAN0 DDRA PTA DDRB PTB CAN4 PB7 PB6 PB5 PB4 PB3 PB2 PB1 PB0 PA7 PA6 PA5 PA4 PA3 PA2 PA1 PA0 Module to Port Routing RxCAN TxCAN RxCAN TxCAN ADDR15 ADDR14 ADDR13 ADDR12 ADDR11 ADDR10 ADDR9 ADDR8 Multiplexed Wide Bus Multiplexed Narrow Bus IIC DATA15 DATA14 DATA13 DATA12 DATA11 DATA10 DATA9 DATA8 SDA SCL PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 MISO MOSI SCK SS MISO MOSI SCK SS KWJ0 KWJ1 KWJ6 KWJ7 KWP0 KWP1 KWP2 KWP3 KWP4 KWP5 KWP6 KWP7 KWH0 KWH1 KWH2 KWH3 KWH4 KWH5 KWH6 KWH7 ADDR7 ADDR6 ADDR5 ADDR4 ADDR3 ADDR2 ADDR1 ADDR0 DATA7 DATA6 DATA5 DATA4 DATA3 DATA2 DATA1 DATA0 DATA7 DATA6 DATA5 DATA4 DATA3 DATA2 DATA1 DATA0 Internal Logic 2.5V VDD1,2 VSS1,2 I/O Driver 3.3V/5V VDDX VSSX OSC/PLL 2.5V VDDPLL VSSPLL SPI1 Voltage Regulator 3.3V/5V A/D Converter 3.3V/5V VDDR Voltage Reference VSSR VDDA VSSA SPI2 Figure 1-2. MC9S12KG128 Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 23 PTH PTP PWM PTJ PTM PTS PTT PTK PAD Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2 Signal Description The MC9S12KG128 is available in a 112-pin low profile quad flat pack (LQFP) and a 80-pin quad flat pack (QFP). Most pins perform two or more functions, as described in Section 1.2.1, “Signal Properties Summary”. Figure 1-3 and Figure 1-4 show the pin assignments for different packages. PP4/KWP4/PWM4/MISO2 PP5/KWP5/PWM5/MOSI2 PP6/KWP6/PWM6/SS2 PP7/KWP7/PWM7/SCK2 PK7/ECS VDDX VSSX PM0/RXCAN0 PM1/TXCAN0 PM2/RXCAN0/MISO0 PM3/TXCAN0/SS0 PM4/RXCAN0/RXCAN4/MOSI0 PM5/TXCAN0/TXCAN4/SCK0 PJ6/KWJ6/RXCAN4/SDA PJ7/KWJ7/TXCAN4/SCL VREGEN PS7/SS0 PS6/SCK0 PS5/MOSI0 PS4/MISO0 PS3/TXD1 PS2/RXD1 PS1/TXD0 PS0/RXD0 PM6/RXCAN4 PM7/TXCAN4 VSSA VRL SS1/PWM3/KWP3/PP3 SCK1/PWM2/KWP2/PP2 MOSI1/PWM1/KWP1/PP1 MISO1/PWM0/KWP0/PP0 XADDR17/PK3 XADDR16/PK2 XADDR15/PK1 XADDR14/PK0 IOC0/PT0 IOC1/PT1 IOC2/PT2 IOC3/PT3 VDD1 VSS1 IOC4/PT4 IOC5/PT5 IOC6/PT6 IOC7/PT7 XADDR19/PK5 XADDR18/PK4 KWJ1/PJ1 KWJ0/PJ0 MODC/TAGHI/BKGD ADDR0/DATA0/PB0 ADDR1/DATA1/PB1 ADDR2/DATA2/PB2 ADDR3/DATA3/PB3 ADDR4/DATA4/PB4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 MC9S12KG128 112LQFP Signals shown in Bold are not available on the 80-pin package 24 ADDR5/DATA5/PB5 ADDR6/DATA6/PB6 ADDR7/DATA7/PB7 SS2/KWH7/PH7 SCK2/KWH6/PH6 MOSI2/KWH5/PH5 MISO2/KWH4/PH4 XCLKS/NOACC/PE7 MODB/IPIPE1/PE6 MODA/IPIPE0/PE5 ECLK/PE4 VSSR VDDR RESET VDDPLL XFC VSSPLL EXTAL XTAL TEST SS1/KWH3/PH3 SCK1/KWH2/PH2 MOSI1/KWH1/PH1 MISO1/KWH0/PH0 LSTRB/TAGLO/PE3 R/W/PE2 IRQ/PE1 XIRQ/PE0 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 VRH VDDA PAD15/AN15 PAD07/AN07 PAD14/AN14 PAD06/AN06 PAD13/AN13 PAD05/AN05 PAD12/AN12 PAD04/AN04 PAD11/AN11 PAD03/AN03 PAD10/AN10 PAD02/AN02 PAD09/AN09 PAD01/AN01 PAD08/AN08 PAD00/AN00 VSS2 VDD2 PA7/ADDR15/DATA15 PA6/ADDR14/DATA14 PA5/ADDR13/DATA13 PA4/ADDR12/DATA12 PA3/ADDR11/DATA11 PA2/ADDR10/DATA10 PA1/ADDR9/DATA9 PA0/ADDR8/DATA8 Figure 1-3. Pin Assignments for 112 LQFP MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) PP4/KWP4/PWM4/MISO2 PP5/KWP5/PWM5/MOSI2 PP7/KWP7/PWM7/SCK2 VDDX VSSX PM0/RXCAN0 PM1/TXCAN0 PM2/RXCAN0/MISO0 PM3/TXCAN0/SS0 PM4/RXCAN0/RXCAN4/MOSI0 PM5/TXCAN0/TXCAN4/SCK0 PJ6/KWJ6/RXCAN4/SDA PJ7/KWJ7/TXCAN4/SCL VREGEN PS3/TXD1 PS2/RXD1 PS1/TXD0 PS0/RXD0 VSSA VRL PWM3/KWP3/PP3 PWM2/KWP2/PP2 PWM1/KWP1/PP1 PWM0/KWP0/PP0 IOC0/PT0 IOC1/PT1 IOC2/PT2 IOC3/PT3 VDD1 VSS1 IOC4/PT4 IOC5/PT5 IOC6/PT6 IOC7/PT7 MODC/TAGHI/BKGD ADDR0/DATA0/PB0 ADDR1/DATA1/PB1 ADDR2/DATA2/PB2 ADDR3/DATA3/PB3 ADDR4/DATA4/PB4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 MC9S12KG128 80 QFP VRH VDDA PAD07/AN07 PAD06/AN06 PAD05/AN05 PAD04/AN04 PAD03/AN03 PAD02/AN02 PAD01/AN01 PAD00/AN00 VSS2 VDD2 PA7/ADDR15/DATA15 PA6/ADDR14/DATA14 PA5/ADDR13/DATA13 PA4/ADDR12/DATA12 PA3/ADDR11/DATA11 PA2/ADDR10/DATA10 PA1/ADDR9/DATA9 PA0/ADDR8/DATA8 Freescale Semiconductor ADDR5/DATA5/PB5 ADDR6/DATA6/PB6 ADDR7/DATA7/PB7 XCLKS/NOACC/PE7 MODB/IPIPE1/PE6 MODA/IPIPE0/PE5 ECLK/PE4 VSSR VDDR RESET VDDPLL XFC VSSPLL EXTAL XTAL TEST LSTRB/TAGLO/PE3 R/W/PE2 IRQ/PE1 XIRQ/PE0 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Figure 1-4. Pin Assignments for 80 QFP MC9S12KG128 Data Sheet, Rev. 1.15 25 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.1 Signal Properties Summary Table 1-2 summarizes the pin functionality. Signals shown in bold are not available in the 80-pin package. Table 1-3 summarizes the power and ground pins. Table 1-2. Signal Properties (Sheet 1 of 3) Internal Pull Resistor Description CTRL EXTAL XTAL RESET TEST VREGEN XFC BKGD PAD[15:8] PAD[7:0] PA[7:0] PB[7:0] PE7 PE6 — — — — — — TAGHI AN[15:8] AN[7:0] ADDR[15:8]/ DATA[15:8] ADDR[7:0]/ DATA[7:0] NOACC IPIPE1 — — — — — — MODC — — — — XCLKS MODB — — — — — — — — — — — — — VDDPLL VDDPLL VDDR NA VDDX VDDPLL VDDR VDDA VDDA VDDR VDDR VDDR VDDR NA NA None NA NA NA Always Up None None PUCR PUCR PUCR Reset State NA NA None NA NA NA Up None None External Reset Test Input Voltage Regulator Enable Input PLL Loop Filter Background Debug, Tag High, Mode Input Port AD Input, Analog Inputs of ATD Port AD Input, Analog Inputs of ATD Oscillator Pins Pin Name Function 1 Pin Name Function 2 Pin Name Pin Name Powered Function 3 Function 4 by Disabled Port A I/O, Multiplexed Address/Data Disabled Port B I/O, Multiplexed Address/Data Up Port E I/O, Access, Clock Select Port E I/O, Pipe Status, Mode Input Port E I/O, Pipe Status, Mode Input Port E I/O, Bus Clock Output Port E I/O, Byte Strobe, Tag Low Port E I/O, R/W in expanded modes Port E Input, Maskable Interrupt Port E Input, Non Maskable Interrupt While RESET pin is low: Down While RESET pin is low: Down PUCR PUCR PUCR PUCR PUCR PERH/ PPSH PERH/ PPSH PERH/ PPSH Up Up Up Up Up PE5 IPIPE0 MODA — VDDR PE4 PE3 PE2 PE1 PE0 PH7 PH6 PH5 ECLK LSTRB R/W IRQ XIRQ KWH7 KWH6 KWH5 — TAGLO — — — SS2 SCK2 MOSI2 — — — — — — — — VDDR VDDR VDDR VDDR VDDR VDDR VDDR VDDR Disabled Port H I/O, Interrupt, SS of SPI2 Disabled Port H I/O, Interrupt, SCK of SPI2 Disabled Port H I/O, Interrupt, MOSI of SPI2 MC9S12KG128 Data Sheet, Rev. 1.15 26 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-2. Signal Properties (Sheet 2 of 3) Internal Pull Resistor Description CTRL PH4 PH3 PH2 PH1 PH0 PJ7 PJ6 PJ[1:0] PK7 KWH4 KWH3 KWH2 KWH1 KWH0 KWJ7 KWJ6 KWJ[1:0] ECS MISO2 SS1 SCK1 MOSI1 MISO1 TXCAN4 RXCAN4 — ROMCTL — — — — — SCL SDA — — VDDR VDDR VDDR VDDR VDDR VDDX VDDX VDDX VDDX PERH/ PPSH PERH/ PPSH PERH/ PPSH PERH/ PPSH PERH/ PPSH PERJ/ PPSJ PERJ/ PPSJ PERJ/ PPSJ PUCR Reset State Disabled Port H I/O, Interrupt, MISO of SPI2 Disabled Port H I/O, Interrupt, SS of SPI1 Disabled Port H I/O, Interrupt, SCK of SPI1 Disabled Port H I/O, Interrupt, MOSI of SPI1 Disabled Port H I/O, Interrupt, MISO of SPI1 Up Up Up Up Port J I/O, Interrupt, TX of CAN4, SCL of IIC Port J I/O, Interrupt, RX of CAN4, SDA of IIC Port J I/O, Interrupts Port K I/O, Emulation Chip Select, ROM On Enable Port K I/O, Extended Addresses Pin Name Function 1 Pin Name Function 2 Pin Name Pin Name Powered Function 3 Function 4 by PK[5:0] PM7 PM6 PM5 PM4 PM3 PM2 PM1 PM0 PP7 XADDR[19:14] TXCAN4 RXCAN4 TXCAN0 RXCAN0 TXCAN0 RXCAN0 TXCAN0 RXCAN0 KWP7 — — — TXCAN4 RXCAN4 — — — — PWM7 — — — SCK0 MOSI0 SS0 MISO0 — — SCK2 VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX PUCR PERM/ PPSM PERM/ PPSM PERM/ PPSM PERM/ PPSM PERM/ PPSM PERM/ PPSM PERM/ PPSM PERM/ PPSM PERP/ PPSP PERP/ PPSP Up Disabled Port M I/O, CAN4 TX Disabled Port M I/O, CAN4 RX Disabled Port M I/O, CAN0 TX, CAN4 TX, SPI0 SCK Disabled Port M I/O, CAN0 RX, CAN4 RX, SPI0 MOSI Disabled Port M I/O, CAN0 TX, SPI0 SS Disabled Port M I/O, CAN0 RX, SPI0 MISO Disabled Port M I/O, CAN0 TX Disabled Port M I/O, CAN0 RX Disabled Port P I/O, Interrupt, PWM Channel 7, SCK of SPI2 Disabled Port P I/O, Interrupt, PWM Channel 6, SPI2 SS PP6 KWP6 PWM6 SS2 VDDX MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 27 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-2. Signal Properties (Sheet 3 of 3) Internal Pull Resistor Description CTRL PP5 KWP5 PWM5 MOSI2 VDDX PERP/ PPSP PERP/ PPSP PERP/ PPSP PERP/ PPSP PERP/ PPSP PERP/ PPSP PERS/ PPSS PERS/ PPSS PERS/ PPSS PERS/ PPSS PERS/ PPSS PERS/ PPSS PERS/ PPSS PERS/ PPSS Up or Down Reset State Disabled Port P I/O, Interrupt, PWM Channel 5, SPI2 MOSI Disabled Port P I/O, Interrupt, PWM Channel 4, SPI2 MISO Disabled Port P I/O, Interrupt, PWM Channel 3, SPI1 SS Disabled Port P I/O, Interrupt, PWM Channel 2, SPI1 SCK Disabled Port P I/O, Interrupt, PWM Channel 1, SPI1 MOSI Disabled Port P I/O, Interrupt, PWM Channel 0, SPI1 MISO Up Up Up Up Up Up Up Up Port S I/O, SPI0 SS Port S I/O, SPI0 SCK Port S I/O, SPI0 MOSI Port S I/O, SPI0 MISO Port S I/O, SCI1TXD Port S I/O, SCI1RXD Port S I/O, SCI0 TXD Port S I/O, SCI0 RXD Pin Name Function 1 Pin Name Function 2 Pin Name Pin Name Powered Function 3 Function 4 by PP4 PP3 PP2 PP1 PP0 PS7 PS6 PS5 PS4 PS3 PS2 PS1 PS0 PT[7:0] KWP4 KWP3 KWP2 KWP1 KWP0 SS0 SCK0 MOSI0 MISO0 TXD1 RXD1 TXD0 RXD0 IOC[7:0] PWM4 PWM3 PWM2 PWM1 PWM0 — — — — — — — — — MISO2 SS1 SCK1 MOSI1 MISO1 — — — — — — — — — VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX VDDX Disabled Port T I/O, Timer channels MC9S12KG128 Data Sheet, Rev. 1.15 28 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-3. Power and Ground Mnemonic VDD1 VDD2 VSS1 VSS2 VDDR VSSR VDDX VSSX VDDA VSSA VRH VRL VDDPLL VSSPLL Nominal Voltage 2.5 V 0V 3.3/5.0 V 0V 3.3/5.0 V 0V 3.3/5.0 V 0V 3.3/5.0 V 0V 2.5 V 0V Operating voltage and ground for the analog-to-digital converter and the reference for the internal voltage regulator, allows the supply voltage to the A/D to be bypassed independently. Reference voltage high for the ATD converter. Reference voltage low for the ATD converter. Provides operating voltage and ground for the Phased-Locked Loop. This allows the supply voltage to the PLL to be bypassed independently. Internal power and ground generated by internal regulator. External power and ground, supply to pin drivers. Description Internal power and ground generated by internal regulator. These also allow an external source to supply the core VDD/VSS voltages and bypass the internal voltage regulator. External power and ground, supply to pin drivers and internal voltage regulator. NOTE All VSS pins must be connected together in the application. 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 MCU pin load. 1.2.2 1.2.2.1 Detailed Signal Descriptions EXTAL, XTAL — Oscillator Pins EXTAL and XTAL are the crystal driver and external clock pins. On reset all the device clocks are derived from the EXTAL input frequency. XTAL is the crystal output. 1.2.2.2 RESET — External Reset Pin An active low bidirectional control signal, it acts as an input to initialize the MCU to a known start-up state, and an output when an internal MCU function causes a reset. 1.2.2.3 TEST — Test Pin NOTE The TEST pin must be tied to VSS in all applications. This input only pin is reserved for test. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 29 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.2.4 VREGEN — Voltage Regulator Enable Pin This input only pin enables or disables the on-chip voltage regulator. 1.2.2.5 XFC — PLL Loop Filter Pin PLL loop filter. Please ask your Freescale representative for the interactive application note to compute PLL loop filter elements. Any current leakage on this pin must be avoided. XFC R CP MCU CS VDDPLL VDDPLL Figure 1-5. PLL Loop Filter Connections 1.2.2.6 BKGD / TAGHI / MODC — Background Debug, Tag High, and Mode Pin The BKGD/TAGHI/MODC pin is used as a pseudo-open-drain pin for the background debug communication. In MCU expanded modes of operation when instruction tagging is on, an input low on this pin during the falling edge of E-clock tags the high half of the instruction word being read into the instruction queue. It is used as a MCU operating mode select pin during reset. The state of this pin is latched to the MODC bit at the rising edge of RESET. 1.2.2.7 PAD[15:0] / AN[15:0] — Port AD Input Pins PAD15 - PAD0 are general purpose input pins and analog inputs of the analog to digital converter with 16 channels (ATD). 1.2.2.8 PA[7:0] / ADDR[15:8] / DATA[15:8] — Port A I/O Pins PA7–PA0 are general purpose input or output pins. In MCU expanded modes of operation, these pins are used for the multiplexed external address and data bus. 1.2.2.9 PB[7:0] / ADDR[7:0] / DATA[7:0] — Port B I/O Pins PB7–PB0 are general purpose input or output pins. In MCU expanded modes of operation, these pins are used for the multiplexed external address and data bus. 1.2.2.10 PE7 / NOACC / XCLKS — Port E I/O Pin 7 PE7 is a general purpose input or output pin. During MCU expanded modes of operation, the NOACC signal, when enabled, is used to indicate that the current bus cycle is an unused or “free” cycle. This signal will assert when the CPU is not using the bus. MC9S12KG128 Data Sheet, Rev. 1.15 30 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) The XCLKS is an input signal which controls whether a crystal in combination with the internal Loop Controlled Pierce (low power) oscillator is used or whether Full Swing Pierce oscillator/external clock circuitry is used. The state of this pin is latched at the rising edge of RESET. If the input is a logic low the EXTAL pin is configured for an external clock drive or Full Swing Pierce Oscillator. If input is a logic high a Loop Controlled Pierce oscillator circuit is configured on EXTAL and XTAL. Since this pin is an input with a pull-up device during reset, if the pin is left floating, the default configuration is a Loop Controlled Pierce oscillator circuit on EXTAL and XTAL. Table 1-4. Clock Selection Based on PE7 During Reset PE7 1 0 Description Loop Controlled Pierce Oscillator selected Full Swing Pierce Oscillator or external clock selected EXTAL C7 MCU CRYSTAL OR CERAMIC RESONATOR C8 VSSPLL XTAL Figure 1-6. Loop Controlled Pierce Oscillator Connections (PE7 = 1) EXTAL C7 MCU RS* XTAL C8 VSSPLL * Rs can be zero (shorted) when use with higher frequency crystals. Refer to manufacturer’s data. RB CRYSTAL OR CERAMIC RESONATOR Figure 1-7. Full Swing Pierce Oscillator Connections (PE7 = 0) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 31 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) EXTAL MCU CMOS-COMPATIBLE EXTERNAL OSCILLATOR (VDDPLL-LEVEL) XTAL NOT CONNECTED Figure 1-8. External Clock Connections (PE7 = 0) 1.2.2.11 PE6 / MODB / IPIPE1 — Port E I/O Pin 6 PE6 is a general purpose input or output pin. It is used as a MCU operating mode select pin during reset. The state of this pin is latched to the MODB bit at the rising edge of RESET. This pin is shared with the instruction queue tracking signal IPIPE1. 1.2.2.12 PE5 / MODA / IPIPE0 — Port E I/O Pin 5 PE5 is a general purpose input or output pin. It is used as a MCU operating mode select pin during reset. The state of this pin is latched to the MODA bit at the rising edge of RESET. This pin is shared with the instruction queue tracking signal IPIPE0. 1.2.2.13 PE4 / ECLK — Port E I/O Pin 4 PE4 is a general purpose input or output pin. It can be configured to drive the internal bus clock ECLK. ECLK can be used as a timing reference. 1.2.2.14 PE3 / LSTRB / TAGLO — Port E I/O Pin 3 PE3 is a general purpose input or output pin. In MCU expanded modes of operation, LSTRB can be used for the low-byte strobe function to indicate the type of bus access and when instruction tagging is on, TAGLO is used to tag the low half of the instruction word being read into the instruction queue. 1.2.2.15 PE2 / R/W — Port E I/O Pin 2 PE2 is a general purpose input or output pin. In MCU expanded modes of operations, this pin drives the read/write output signal for the external bus. It indicates the direction of data on the external bus. 1.2.2.16 PE1 / IRQ — Port E Input Pin 1 PE1 is a general purpose input pin and the maskable interrupt request input that provides a means of applying asynchronous interrupt requests. This will wake up the MCU from STOP or WAIT mode. MC9S12KG128 Data Sheet, Rev. 1.15 32 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.2.17 PE0 / XIRQ — Port E Input Pin 0 PE0 is a general purpose input pin and the non-maskable interrupt request input that provides a means of applying asynchronous interrupt requests. This will wake up the MCU from STOP or WAIT mode. 1.2.2.18 PH7 / KWH7 / SS2 — Port H I/O Pin 7 PH7 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as slave select pin SS of the Serial Peripheral Interface 2 (SPI2). 1.2.2.19 PH6 / KWH6 / SCK2 — Port H I/O Pin 6 PH6 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as serial clock pin SCK of the Serial Peripheral Interface 2 (SPI2). 1.2.2.20 PH5 / KWH5 / MOSI2 — Port H I/O Pin 5 PH5 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as master output (during master mode) or slave input pin (during slave mode) MOSI of the Serial Peripheral Interface 2 (SPI2). 1.2.2.21 PH4 / KWH4 / MISO2 — Port H I/O Pin 2 PH4 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as master input (during master mode) or slave output (during slave mode) pin MISO of the Serial Peripheral Interface 2 (SPI2). 1.2.2.22 PH3 / KWH3 / SS1 — Port H I/O Pin 3 PH3 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as slave select pin SS of the Serial Peripheral Interface 1 (SPI1). 1.2.2.23 PH2 / KWH2 / SCK1 — Port H I/O Pin 2 PH2 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as serial clock pin SCK of the Serial Peripheral Interface 1 (SPI1). 1.2.2.24 PH1 / KWH1 / MOSI1 — Port H I/O Pin 1 PH1 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as master output (during master mode) or slave input pin (during slave mode) MOSI of the Serial Peripheral Interface 1 (SPI1). MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 33 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.2.25 PH0 / KWH0 / MISO1 — Port H I/O Pin 0 PH0 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as master input (during master mode) or slave output (during slave mode) pin MISO of the Serial Peripheral Interface 1 (SPI1). 1.2.2.26 PJ7 / KWJ7 / TXCAN4 / SCL — PORT J I/O Pin 7 PJ7 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as the transmit pin TXCAN for the Scalable Controller Area Network controller 4 (CAN4) or the serial clock pin SCL of the IIC module. 1.2.2.27 PJ6 / KWJ6 / RXCAN4 / SDA — PORT J I/O Pin 6 PJ6 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as the receive pin RXCAN for the Scalable Controller Area Network controller 4 (CAN4) or the serial data pin SDA of the IIC module. 1.2.2.28 PJ[1:0] / KWJ[1:0] — Port J I/O Pins [1:0] PJ1 and PJ0 are general purpose input or output pins. They can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. 1.2.2.29 PK7 / ECS / ROMCTL — Port K I/O Pin 7 PK7 is a general purpose input or output pin. During MCU expanded modes of operation, this pin is used as the emulation chip select output (ECS). During MCU expanded modes of operation, this pin is used to enable the Flash EEPROM memory in the memory map (ROMCTL). At the rising edge of RESET, the state of this pin is latched to the ROMON bit. MC9S12KG128 Data Sheet, Rev. 1.15 34 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) For all other modes the reset state of the ROMON bit is as follows: • Special single: ROMCTL = 1 • Normal single: ROMCTL = 1 • Emulation expanded wide: ROMCTL = 0 • Emulation expanded narrow: ROMCTL = 0 • Special test: ROMCTL = 0 • Peripheral test: ROMCTL = 1 1.2.2.30 PK[5:0] / XADDR[19:14] — Port K I/O Pins [5:0] PK5-PK0 are general purpose input or output pins. In MCU expanded modes of operation, these pins provide the expanded address XADDR[19:14] for the external bus. 1.2.2.31 PM7 / TXCAN4 — Port M I/O Pin 7 PM7 is a general purpose input or output pin. It can be configured as the transmit pin TXCAN of the Scalable Controller Area Network controllers 4 (CAN4). 1.2.2.32 PM6 / RXCAN4 — Port M I/O Pin 6 PM6 is a general purpose input or output pin. It can be configured as the receive pin RXCAN of the Scalable Controller Area Network controllers 4 (CAN4). 1.2.2.33 PM5 / TXCAN0 / TXCAN4 / SCK0 — Port M I/O Pin 5 PM5 is a general purpose input or output pin. It can be configured as the transmit pin TXCAN of the Scalable Controller Area Network controllers 0 or 4 (CAN0 or CAN4). It can be configured as the serial clock pin SCK of the Serial Peripheral Interface 0 (SPI0). 1.2.2.34 PM4 / RXCAN0 / RXCAN4/ MOSI0 — Port M I/O Pin 4 PM4 is a general purpose input or output pin. It can be configured as the receive pin RXCAN of the Scalable Controller Area Network controllers 0 or 4 (CAN0 or CAN4). It can be configured as the master output (during master mode) or slave input pin (during slave mode) MOSI for the Serial Peripheral Interface 0 (SPI0). 1.2.2.35 PM3 / TXCAN0 / SS0 — Port M I/O Pin 3 PM3 is a general purpose input or output pin. It can be configured as the transmit pin TXCAN of the Scalable Controller Area Network controller 0 (CAN0). It can be configured as the slave select pin SS of the Serial Peripheral Interface 0 (SPI0). MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 35 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.2.36 PM2 / RXCAN0 / MISO0 — Port M I/O Pin 2 PM2 is a general purpose input or output pin. It can be configured as the receive pin RXCAN of the Scalable Controller Area Network controller 0 ( CAN0). It can be configured as the master input (during master mode) or slave output pin (during slave mode) MISO for the Serial Peripheral Interface 0 (SPI0). 1.2.2.37 PM1 / TXCAN0 — Port M I/O Pin 1 PM1 is a general purpose input or output pin. It can be configured as the transmit pin TXCAN of the Scalable Controller Area Network controller 0 (CAN0). 1.2.2.38 PM0 / RXCAN0 — Port M I/O Pin 0 PM0 is a general purpose input or output pin. It can be configured as the receive pin RXCAN of the Scalable Controller Area Network controller 0 (CAN0). 1.2.2.39 PP7 / KWP7 / PWM7 / SCK2 — Port P I/O Pin 7 PP7 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 7 output. It can be configured as serial clock pin SCK of the Serial Peripheral Interface 2 (SPI2). 1.2.2.40 PP6 / KWP6 / PWM6 / SS2 — Port P I/O Pin 6 PP6 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 6 output. It can be configured as slave select pin SS of the Serial Peripheral Interface 2 (SPI2). 1.2.2.41 PP5 / KWP5 / PWM5 / MOSI2 — Port P I/O Pin 5 PP5 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 5 output. It can be configured as master output (during master mode) or slave input pin (during slave mode) MOSI of the Serial Peripheral Interface 2 (SPI2). 1.2.2.42 PP4 / KWP4 / PWM4 / MISO2 — Port P I/O Pin 4 PP4 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 4 output. It can be configured as master input (during master mode) or slave output (during slave mode) pin MISO of the Serial Peripheral Interface 2 (SPI2). 1.2.2.43 PP3 / KWP3 / PWM3 / SS1 — Port P I/O Pin 3 PP3 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 3 output. It can be configured as slave select pin SS of the Serial Peripheral Interface 1 (SPI1). MC9S12KG128 Data Sheet, Rev. 1.15 36 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.2.44 PP2 / KWP2 / PWM2 / SCK1 — Port P I/O Pin 2 PP2 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 2 output. It can be configured as serial clock pin SCK of the Serial Peripheral Interface 1 (SPI1). 1.2.2.45 PP1 / KWP1 / PWM1 / MOSI1 — Port P I/O Pin 1 PP1 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 1 output. It can be configured as master output (during master mode) or slave input pin (during slave mode) MOSI of the Serial Peripheral Interface 1 (SPI1). 1.2.2.46 PP0 / KWP0 / PWM0 / MISO1 — Port P I/O Pin 0 PP0 is a general purpose input or output pin. It can be configured to generate an interrupt causing the MCU to exit STOP or WAIT mode. It can be configured as Pulse Width Modulator (PWM) channel 0 output. It can be configured as master input (during master mode) or slave output (during slave mode) pin MISO of the Serial Peripheral Interface 1 (SPI1). 1.2.2.47 PS7 / SS0 — Port S I/O Pin 7 PS6 is a general purpose input or output pin. It can be configured as the slave select pin SS of the Serial Peripheral Interface 0 (SPI0). 1.2.2.48 PS6 / SCK0 — Port S I/O Pin 6 PS6 is a general purpose input or output pin. It can be configured as the serial clock pin SCK of the Serial Peripheral Interface 0 (SPI0). 1.2.2.49 PS5 / MOSI0 — Port S I/O Pin 5 PS5 is a general purpose input or output pin. It can be configured as master output (during master mode) or slave input pin (during slave mode) MOSI of the Serial Peripheral Interface 0 (SPI0). 1.2.2.50 PS4 / MISO0 — Port S I/O Pin 4 PS4 is a general purpose input or output pin. It can be configured as master input (during master mode) or slave output pin (during slave mode) MOSI of the Serial Peripheral Interface 0 (SPI0). 1.2.2.51 PS3 / TXD1 — Port S I/O Pin 3 PS3 is a general purpose input or output pin. It can be configured as the transmit pin TXD of Serial Communication Interface 1 (SCI1). MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 37 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.2.2.52 PS2 / RXD1 — Port S I/O Pin 2 PS2 is a general purpose input or output pin. It can be configured as the receive pin RXD of Serial Communication Interface 1 (SCI1). 1.2.2.53 PS1 / TXD0 — Port S I/O Pin 1 PS1 is a general purpose input or output pin. It can be configured as the transmit pin TXD of Serial Communication Interface 0 (SCI0). 1.2.2.54 PS0 / RXD0 — Port S I/O Pin 0 PS0 is a general purpose input or output pin. It can be configured as the receive pin RXD of Serial Communication Interface 0 (SCI0). 1.2.2.55 PT[7:0] / IOC[7:0] — Port T I/O Pins [7:0] PT7-PT0 are general purpose input or output pins. They can be configured as input capture or output compare pins IOC7-IOC0 of the Timer (TIM). 1.2.3 Power Supply Pins NOTE All VSS pins must be connected together in the application. MC9S12KG128 power and ground pins are described below. 1.2.3.1 VDDX,VSSX — Power Supply Pins for I/O Drivers 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. 1.2.3.2 VDDR, VSSR — Power Supply Pins for I/O Drivers & for Internal Voltage Regulator External power and ground for I/O drivers and input to the internal voltage regulator. 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. 1.2.3.3 VDD1, VDD2, VSS1, VSS2 — Power Supply Pins for Internal Logic 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. This 2.5V supply is derived from the MC9S12KG128 Data Sheet, Rev. 1.15 38 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) internal voltage regulator. There is no static load on those pins allowed. The internal voltage regulator is turned off, if VREGEN is tied to ground. NOTE No load allowed except for bypass capacitors. 1.2.3.4 VDDA, VSSA — Power Supply Pins for ATD and VREG VDDA, VSSA are the power supply and ground input pins for the voltage regulator and the analog to digital converter. It also provides the reference for the internal voltage regulator. This allows the supply voltage to the ATD and the reference voltage to be bypassed independently. 1.2.3.5 VRH, VRL — ATD Reference Voltage Input Pins VRH and VRL are the reference voltage input pins for the analog to digital converter. 1.2.3.6 VDDPLL, VSSPLL — Power Supply Pins for PLL Provides operating voltage and ground for the Oscillator and the Phased-Locked Loop. This allows the supply voltage to the Oscillator and PLL to be bypassed independently. This 2.5V voltage is generated by the internal voltage regulator. NOTE No load allowed except for bypass capacitors. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 39 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.3 1.3.1 Memory Map and Register Definition Device Memory Map Table 1-5. MC9S12KT256 Device Memory Map Address 0x0000–0x0017 0x0018 0x0019 0x001A–0x001B 0x001C–0x001F 0x0020–0x002F 0x0030–0x0033 0x0034–0x003F 0x0040–0x006F 0x0070–0x007F 0x0080–0x00AF 0x00B0–0x00C7 0x00C8–0x00CF 0x00D0–0x00D7 0x00D8–0x00DF 0x00E0–0x00E7 0x00E8–0x00EF 0x00F0–0x00F7 0x00F8–0x00FF 0x0100–0x010F 0x0110- 0x011B 0x011C–0x013F 0x0140–0x017F 0x0180–0x023F 0x0240–0x027F 0x0280–0x02BF 0x02C0–0x02E7 0x02E8–0x03FF Module CORE (Ports A, B, E, Modes, Inits, Test) Reserved Voltage Regulator (VREG) Device ID register (PARTID) CORE (MEMSIZ, IRQ, HPRIO) CORE (DBG) CORE (PPAGE, Port K) Clock and Reset Generator (PLL, RTI, COP) Standard Timer 16-bit 8 channels (TIM) Reserved Analog to Digital Converter 10-bit 16 channels (ATD) Reserved Serial Communications Interface 0 (SCI0) Serial Communications Interface 1 (SCI1) Serial Peripheral Interface 0 (SPI0) Inter Integrated Circuit Bus (IIC) Reserved Serial Peripheral Interface 1 (SPI1) Serial Peripheral Interface 2 (SPI2) Flash Control Register EEPROM Control Register Reserved Scalable Controller Area Network 0 (CAN0) Reserved Port Integration Module (PIM) Scalable Controller Area Network 4 (CAN4) Pulse Width Modulator 8-bit 8 channels (PWM) Reserved Size 24 1 1 2 4 16 4 12 48 16 48 24 8 8 8 8 8 8 8 16 12 36 64 192 64 64 40 280 Table 1-5 shows the device register map of the MC9S12KG128 after reset. MC9S12KG128 Data Sheet, Rev. 1.15 40 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Figure 1-9 illustrates the full user configurable device memory map of MC9S12KG128. 0x0000 0x0000 0x0400 0x0800 0x1000 0x2000 1K Register Space 0x03FF Mappable to any 2K Boundary 0x0800 0x0FFF 0x2000 2K Bytes EEPROM Mappable to any 2K Boundary 8K Bytes RAM Mappable to any 8K Boundary 0.5K, 1K, 2K or 4K Protected Sector 0x4000 0x3FFF 0x4000 0x7FFF 0x8000 0x8000 EXT 0xBFFF 0xC000 0xC000 16K Fixed Flash EEPROM 16K Page Window eight * 16K Flash EEPROM Pages 16K Fixed Flash EEPROM 2K, 4K, 8K or 16K Protected Boot Sector BDM (If Active) 0xFFFF 0xFF00 0xFF00 0xFFFF VECTORS NORMAL SINGLE CHIP VECTORS EXPANDED VECTORS SPECIAL SINGLE CHIP 0xFFFF The figure shows a useful map, which is not the map out of reset. After reset the map is: 0x0000–0x03FF: Register Space 0x0000–0x1FFF: 8K RAM (1K RAM hidden behind Register Space) 0x0000–0x07FF: 2K EEPROM (not visible) Figure 1-9. MC9S12KG128 Memory Map MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 41 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Figure 1-10 illustrates the full user configurable device memory map of MC9S12KL64 and MC9S12KC64. 0x0000 0x0000 0x0400 0x0800 0x1000 0x3000 0x4000 1K Register Space 0x03FF Mappable to any 2K Boundary 0x0800 0x0FFF 0x3000 0x3FFF 0x4000 1K Bytes EEPROM Mappable to any 2K Boundary (1K mapped two times in 2K space) 4K Bytes RAM Mappable to any 4K Boundary 0.5K, 1K, 2K or 4K Protected Sector 0x7FFF 0x8000 0x8000 EXT 0xBFFF 0xC000 0xC000 16K Fixed Flash EEPROM 16K Page Window four * 16K Flash EEPROM Pages 16K Fixed Flash EEPROM 2K, 4K, 8K or 16K Protected Boot Sector BDM (If Active) 0xFFFF 0xFF00 0xFF00 0xFFFF VECTORS NORMAL SINGLE CHIP VECTORS EXPANDED VECTORS SPECIAL SINGLE CHIP 0xFFFF The figure shows a useful map, which is not the map out of reset. After reset the map is: 0x0000–0x03FF: Register Space 0x0000–0x0FFF: 4K RAM (1K RAM hidden behind Register Space) 0x0000–0x03FF: 1K EEPROM (not visible) Figure 1-10. MC9S12KL(C)64 Memory Map MC9S12KG128 Data Sheet, Rev. 1.15 42 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Figure 1-11 illustrates the full user configurable device memory map of MC9S12KL32. 0x0000 0x0000 0x0400 0x0800 0x1000 0x3800 0x4000 0x03FF 0x0800 0x0FFF 0x3800 0x3FFF 1K Register Space Mappable to any 2K Boundary 1K Bytes EEPROM Mappable to any 2K Boundary (1K mapped two times in 2K space) 2K Bytes RAM Mappable to any 2K Boundary 0x8000 0x8000 EXT 32K Fixed Flash EEPROM 2K, 4K, 8K or 16K Protected Boot Sector BDM (If Active) 0xFFFF 0xFF00 0xFF00 0xFFFF VECTORS NORMAL SINGLE CHIP VECTORS EXPANDED VECTORS SPECIAL SINGLE CHIP 0xFFFF The figure shows a useful map, which is not the map out of reset. After reset the map is: 0x0000–0x03FF: Register Space 0x0000–0x07FF: 2K RAM (1K RAM hidden behind Register Space) 0x0000–0x03FF: 1K EEPROM (not visible) Figure 1-11. MC9S12KL32 Memory Map MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 43 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.3.2 Detailed Register Map The following tables show the detailed register map of the MC9S12KG128. 0x0000–0x000F MEBI Map 1 of 3 (HCS12 Multiplexed External Bus Interface) Address 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F Name PORTA PORTB DDRA DDRB Reserved Reserved Reserved Reserved PORTE DDRE PEAR MODE PUCR RDRIV EBICTL Reserved Bit 7 R Bit 7 W R Bit 7 W R Bit 7 W R Bit 7 W R 0 W R 0 W R 0 W R 0 W R Bit 7 W R Bit 7 W R NOACCE W R MODC W R PUPKE W R RDPK W R 0 W R 0 W Bit 6 6 6 6 6 0 0 0 0 Bit 5 5 5 5 5 0 0 0 0 Bit 4 4 4 4 4 0 0 0 0 Bit 3 3 3 3 3 0 0 0 0 Bit 2 2 2 2 2 0 0 0 0 Bit 1 1 1 1 1 0 0 0 0 Bit 1 0 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 0 0 0 0 Bit 0 0 0 6 6 0 5 5 PIPOE MODA 0 0 0 0 4 4 NECLK 0 3 3 LSTRE IVIS 0 0 0 0 2 Bit 2 RDWE 0 0 0 0 0 MODB 0 0 0 0 EMK PUPBE RDPB 0 0 EME PUPAE RDPA ESTR 0 PUPEE RDPE 0 0 MC9S12KG128 Data Sheet, Rev. 1.15 44 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0010–0x0014 MMC Map 1 of 4 (HCS12 Module Mapping Control) Address 0x0010 0x0011 0x0012 0x0013 0x0014 Name INITRM INITRG INITEE MISC Reserved R W R W R W R W R W Bit 7 RAM15 0 Bit 6 RAM14 REG14 EE14 0 0 Bit 5 RAM13 REG13 EE13 0 0 Bit 4 RAM12 REG12 EE12 0 0 Bit 3 RAM11 REG11 EE11 EXSTR1 0 Bit 2 0 0 0 Bit 1 0 0 0 Bit 0 RAMHAL 0 EE15 0 0 EEON ROMON 0 EXSTR0 0 ROMHM 0 0x0015–0x0016 INT Map 1 of 2 (HCS12 Interrupt) Address 0x0015 0x0016 Name ITCR ITEST R W R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 WRINT INT8 Bit 3 ADR3 INT6 Bit 2 ADR2 INT4 Bit 1 ADR1 INT2 Bit 0 ADR0 INT0 INTE INTC INTA 0x0017–0x0017 MMC Map 2 of 4 (HCS12 Module Mapping Control) Address 0x0017 Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 0x0018–0x0018 Miscellaneous Peripherals (Device Guide) Address 0x0018 Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 0x0019–0x0019 VREG3V3 (Voltage Regulator) Address 0x0019 Name VREGCTRL R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 LVDS Bit 1 LVIE Bit 0 LVIF 0x001A–0x001B Miscellaneous Peripherals (Device Guide) Address 0x001A 0x001B Name PARTIDH PARTIDL R W R W Bit 7 ID15 ID7 Bit 6 ID14 ID6 Bit 5 ID13 ID5 Bit 4 ID12 ID4 Bit 3 ID11 ID3 Bit 2 ID10 ID2 Bit 1 ID9 ID1 Bit 0 ID8 ID0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 45 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x001C–0x001D MMC Map 3 of 4 (HCS12 Module Mapping Control, Device Guide) Address 0x001C 0x001D Name MEMSIZ0 MEMSIZ1 Bit 7 R reg_sw0 W R rom_sw1 W Bit 6 0 rom_sw0 Bit 5 eep_sw1 0 Bit 4 eep_sw0 0 Bit 3 0 0 Bit 2 ram_sw2 0 Bit 1 ram_sw1 pag_sw1 Bit 0 ram_sw0 pag_sw0 0x001E–0x001E MEBI Map 2 of 3 (HCS12 Multiplexed External Bus Interface) Address 0x001E Name INTCR R W Bit 7 IRQE Bit 6 IRQEN Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 0x001F–0x001F INT Map 2 of 2 (HCS12 Interrupt) Address 0x001F Name HPRIO R W Bit 7 PSEL7 Bit 6 PSEL6 Bit 5 PSEL5 Bit 4 PSEL4 Bit 3 PSEL3 Bit 2 PSEL2 Bit 1 PSEL1 Bit 0 0 0x0020–0x002F DBG Map 1 of 1 (HCS12 Debug) Address 0x0020 0x0021 0x0022 0x0023 0x0024 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B Name DBGC1 — DBGSC — DBGTBH — DBGTBL — DBGCNT — DBGCCX — DBGCCH — DBGCCL — DBGC2 BKPCT0 DBGC3 BKPCT1 DBGCAX BKP0X DBGCAH BKP0H Bit 7 Bit 6 Bit 5 TRGSEL CF Bit 13 Bit 5 Bit 4 BEGIN 0 Bit 12 Bit 4 Bit 11 Bit 3 CNT Bit 10 Bit 2 Bit 3 DBGBRK Bit 2 0 Bit 1 Bit 0 R DBGEN ARM W R AF BF W R Bit 15 Bit 14 W R Bit 7 Bit 6 W R TBF 0 W R PAGSEL W R Bit 15 14 W R Bit 7 6 W R BKABEN FULL W R BKAMBH BKAMBL W R PAGSEL W R Bit 15 14 W CAPMOD TRG Bit 9 Bit 1 Bit 8 Bit 0 EXTCMP 13 5 BDM BKBMBH 12 4 TAGAB BKBMBL 11 3 BKCEN RWAEN 10 2 TAGC RWA 9 1 RWCEN RWBEN Bit 8 Bit 0 RWC RWB EXTCMP 13 12 11 10 9 Bit 8 MC9S12KG128 Data Sheet, Rev. 1.15 46 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0020–0x002F DBG Map 1 of 1 (HCS12 Debug) (continued) Address 0x002C 0x002D 0x002E 0x002F Name DBGCAL BKP0L DBGCBX BKP1X DBGCBH BKP1H DBGCBL BKP1L R W R W R W R W Bit 7 Bit 7 PAGSEL Bit 15 Bit 7 14 6 13 5 12 4 Bit 6 6 Bit 5 5 Bit 4 4 Bit 3 3 EXTCMP 11 3 10 2 9 1 Bit 8 Bit 0 Bit 2 2 Bit 1 1 Bit 0 Bit 0 0x0030–0x0031 MMC Map 4 of 4 (HCS12 Module Mapping Control) Address 0x0030 0x0031 Name PPAGE Reserved R W R W Bit 7 0 0 Bit 6 0 0 Bit 5 PIX5 0 Bit 4 PIX4 0 Bit 3 PIX3 0 Bit 2 PIX2 0 Bit 1 PIX1 0 Bit 0 PIX0 0 0x0032–0x0033 MEBI Map 3 of 3 (HCS12 Multiplexed External Bus Interface) Address 0x0032 0x0033 Name PORTK DDRK R W R W Bit 7 Bit 7 Bit 7 Bit 6 6 6 Bit 5 5 5 Bit 4 4 4 Bit 3 3 3 Bit 2 2 2 Bit 1 1 1 Bit 0 Bit 0 Bit 0 0x0034–0x003F CRG (Clock and Reset Generator) Address 0x0034 0x0035 0x0036 0x0037 0x0038 0x0039 0x003A 0x003B Name SYNR REFDV CTFLG TEST ONLY CRGFLG CRGINT CLKSEL PLLCTL RTICTL R W R W R W R W R W R W R W R W Bit 7 0 0 TOUT7 Bit 6 0 0 TOUT6 Bit 5 SYN5 0 TOUT5 0 0 Bit 4 SYN4 0 TOUT4 Bit 3 SYN3 REFDV3 TOUT3 LOCK 0 Bit 2 SYN2 REFDV2 TOUT2 TRACK 0 Bit 1 SYN1 REFDV1 TOUT1 Bit 0 SYN0 REFDV0 TOUT0 SCM 0 RTIF RTIE PLLSEL CME 0 PROF 0 LOCKIF LOCKIE ROAWAI ACQ RTR4 SCMIF SCMIE RTIWAI PCE RTR1 PSTP PLLON RTR6 SYSWAI AUTO RTR5 PLLWAI 0 CWAI PRE RTR2 COPWAI SCME RTR0 RTR3 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 47 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0034–0x003F CRG (Clock and Reset Generator) (continued) Address 0x003C 0x003D 0x003E 0x003F Name COPCTL FORBYP TEST ONLY CTCTL TEST ONLY ARMCOP R W R W R W R W Bit 7 WCOP RTIBYP TCTL7 0 Bit 7 Bit 6 RSBCK COPBYP TCTL6 0 6 Bit 5 0 0 TCTL5 0 5 Bit 4 0 Bit 3 0 0 TCLT3 0 3 Bit 2 CR2 0 TCTL2 0 2 Bit 1 CR1 FCM TCTL1 0 1 Bit 0 CR0 0 TCTL0 0 Bit 0 PLLBYP TCTL4 0 4 0x0040–0x006FTIM (Timer 16 Bit 8 Channels) (Sheet 1 of 3) Address 0x0040 0x0041 0x0042 0x0043 0x0044 0x0045 0x0046 0x0047 0x0048 0x0049 0x004A 0x004B 0x004C 0x004D 0x004E 0x004F Name TIOS CFORC OC7M OC7D TCNT (hi) TCNT (lo) TSCR1 TTOV TCTL1 TCTL2 TCTL3 TCTL4 TIE TSCR2 TFLG1 TFLG2 R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 IOS7 0 FOC7 OC7M7 OC7D7 Bit 15 Bit 7 Bit 6 IOS6 0 FOC6 OC7M6 OC7D6 14 6 Bit 5 IOS5 0 FOC5 OC7M5 OC7D5 13 5 Bit 4 IOS4 0 FOC4 OC7M4 OC7D4 12 4 Bit 3 IOS3 0 FOC3 OC7M3 OC7D3 11 3 0 Bit 2 IOS2 0 FOC2 OC7M2 OC7D2 10 2 0 Bit 1 IOS1 0 FOC1 OC7M1 OC7D1 9 1 0 Bit 0 IOS0 0 FOC0 OC7M0 OC7D0 Bit 8 Bit 0 0 TEN TOV7 OM7 OM3 EDG7B EDG3B C7I TOI C7F TOF TSWAI TOV6 OL7 OL3 EDG7A EDG3A C6I 0 TSFRZ TOV5 OM6 OM2 EDG6B EDG2B C5I 0 TFFCA TOV4 OL6 OL2 EDG6A EDG2A C4I 0 TOV3 OM5 OM1 EDG5B EDG1B C3I TCRE C3F 0 TOV2 OL5 OL1 EDG5A EDG1A C2I PR2 C2F 0 TOV1 OM4 OM0 EDG4B EDG0B C1I PR1 C1F 0 TOV0 OL4 OL0 EDG4A EDG0A C0I PR0 C0F 0 C6F 0 C5F 0 C4F 0 MC9S12KG128 Data Sheet, Rev. 1.15 48 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0040–0x006FTIM (Timer 16 Bit 8 Channels) (Sheet 2 of 3) Address 0x0050 0x0051 0x0052 0x0053 0x0054 0x0055 0x0056 0x0057 0x0058 0x0059 0x005A 0x005B 0x005C 0x005D 0x005E 0x005F 0x0060 0x0061 0x0062 0x0063 0x0064 0x0065 0x0066 Name TC0 (hi) TC0 (lo) TC1 (hi) TC1 (lo) TC2 (hi) TC2 (lo) TC3 (hi) TC3 (lo) TC4 (hi) TC4 (lo) TC5 (hi) TC5 (lo) TC6 (hi) TC6 (lo) TC7 (hi) TC7 (lo) PACTL PAFLG PACNT (hi) PACNT (lo) Reserved Reserved Reserved R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 0 0 Bit 6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 PAEN 0 Bit 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 PAMOD 0 Bit 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 PEDGE 0 Bit 3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 CLK1 0 Bit 2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 CLK0 0 Bit 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 PAOVI PAOVF 1 1 0 0 0 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 Bit 8 Bit 0 PAI PAIF Bit 0 Bit 0 0 0 0 Bit 7 Bit 7 0 0 0 6 6 0 0 0 5 5 0 0 0 4 4 0 0 0 3 3 0 0 0 2 2 0 0 0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 49 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0040–0x006FTIM (Timer 16 Bit 8 Channels) (Sheet 3 of 3) Address 0x0067 0x0068 0x0069 0x006A 0x006B 0x006C 0x006D 0x006E 0x006F Name Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved R W R W R W R W R W R W R W R W R W Bit 7 0 0 0 0 0 0 0 0 0 Bit 6 0 0 0 0 0 0 0 0 0 Bit 5 0 0 0 0 0 0 0 0 0 Bit 4 0 0 0 0 0 0 0 0 0 Bit 3 0 0 0 0 0 0 0 0 0 Bit 2 0 0 0 0 0 0 0 0 0 Bit 1 0 0 0 0 0 0 0 0 0 Bit 0 0 0 0 0 0 0 0 0 0 0x0070–0x007FReserved Space Address 0x0070– 0x007F Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 0x0080–0x00AF ATD (Analog to Digital Converter 10 Bit 16 Channel) Address 0x0080 0x0081 0x0082 0x0083 0x0084 0x0085 0x0086 0x0087 Name ATDCTL0 ATDCTL1 ATDCTL2 ATDCTL3 ATDCTL4 ATDCTL5 ATDSTAT0 Reserved Bit 7 R 0 W R ETRIGSEL W R ADPU W R 0 W R SRES8 W R DJM W R SCF W R 0 W Bit 6 0 0 Bit 5 0 0 Bit 4 0 0 Bit 3 WRAP3 Bit 2 WRAP2 Bit 1 WRAP1 Bit 0 WRAP0 ETRIGCH3 ETRIGCH2 ETRIGCH1 ETRIGCH0 AFFC S8C SMP1 DSGN 0 0 AWAI S4C SMP0 SCAN ETORF 0 ETRIGLE S2C PRS4 MULT FIFOR 0 ETRIGP S1C PRS3 0 0 0 ETRIG FIFO PRS2 CC CC2 0 ASCIE FRZ1 PRS1 CB CC1 0 ASCIF FRZ0 PRS0 CA CC0 0 MC9S12KG128 Data Sheet, Rev. 1.15 50 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0080–0x00AF ATD (Analog to Digital Converter 10 Bit 16 Channel) (continued) Address 0x0088 0x0089 0x008A 0x008B 0x008C 0x008D 0x008E 0x008F 0x0090 0x0091 0x0092 0x0093 0x0094 0x0095 0x0096 0x0097 0x0098 0x0099 0x009A 0x009B 0x009C 0x009D 0x009E Name ATDTEST0 ATDTEST1 ATDSTAT0 ATDSTAT1 ATDDIEN1 ATDDIEN0 PORTAD1 PORTAD0 ATDDR0H ATDDR0L ATDDR1H ATDDR1L ATDDR2H ATDDR2L ATDDR3H ATDDR3L ATDDR4H ATDDR4L ATDDR5H ATDDR5L ATDDR6H ATDDR6L ATDDR7H R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 0 0 CCF15 CCF7 Bit 6 0 0 CCF14 CCF6 Bit 5 0 0 CCF13 CCF5 Bit 4 0 0 CCF12 CCF4 Bit 3 0 0 CCF11 CCF3 Bit 2 0 Bit 1 0 0 CCF9 CCF1 Bit 0 0 0 CCF10 CCF2 SC CCF8 CCF0 IEN15 IEN7 PTAD15 PTAD7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 IEN14 IEN6 PTAD14 PTAD6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 IEN13 IEN5 PTAD13 PTAD5 13 0 13 0 13 0 13 0 13 0 13 0 13 0 13 IEN12 IEN4 PTAD12 PTAD4 12 0 12 0 12 0 12 0 12 0 12 0 12 0 12 IEN11 IEN3 PTAD11 PTAD3 11 0 11 0 11 0 11 0 11 0 11 0 11 0 11 IEN10 IEN2 PTAD10 PTAD2 10 0 10 0 10 0 10 0 10 0 10 0 10 0 10 IEN9 IEN1 PTAD9 PTAD1 9 0 9 0 9 0 9 0 9 0 9 0 9 0 9 IEN8 IEN0 PTAD8 PTAD0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 51 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0080–0x00AF ATD (Analog to Digital Converter 10 Bit 16 Channel) (continued) Address 0x009F 0x00A0 0x00A1 0x00A2 0x00A3 0x00A4 0x00A5 0x00A6 0x00A7 0x00A8 0x00A9 0x00AA 0x00AB 0x00AC 0x00AD 0x00AE 0x00AF Name ATDDR7L ATDDR8H ATDDR8L ATDDR9H ATDDR9L ATDDR10H ATDDR10L ATDDR11H ATDDR11L ATDDR12H ATDDR12L ATDDR13H ATDDR13L ATDDR14H ATDDR14L ATDDR15H ATDDR15L R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 15 Bit 7 Bit 6 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 14 Bit 6 Bit 5 0 13 0 13 0 13 0 13 0 13 0 13 0 13 0 13 0 Bit 4 0 12 0 12 0 12 0 12 0 12 0 12 0 12 0 12 0 Bit 3 0 11 0 11 0 11 0 11 0 11 0 11 0 11 0 11 0 Bit 2 0 10 0 10 0 10 0 10 0 10 0 10 0 10 0 10 0 Bit 1 0 9 0 9 0 9 0 9 0 9 0 9 0 9 0 9 0 Bit 0 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 Bit 8 0 0x00B0–0x00C7 Address 0x00B0– 0x00C7 Name Reserved R W Bit 7 0 Reserved space Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 MC9S12KG128 Data Sheet, Rev. 1.15 52 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x00C8–0x00CF SCI0 (Asynchronous Serial Interface) Address 0x00C8 0x00C9 0x00CA 0x00CB 0x00CC 0x00CD 0x00CE 0x00CF Name SCI0BDH SCI0BDL SCI0CR1 SCI0CR2 SCI0SR1 SCI0SR2 SCI0DRH SCI0DRL R W R W R W R W R W R W R W R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 SBR12 SBR4 M ILIE IDLE 0 0 R4 T4 Bit 3 SBR11 SBR3 WAKE TE OR 0 0 R3 T3 Bit 2 SBR10 SBR2 ILT RE NF Bit 1 SBR9 SBR1 PE RWU FE Bit 0 SBR8 SBR0 PT SBK PF RAF 0 R0 T0 SBR7 LOOPS TIE TDRE 0 R8 R7 T7 SBR6 SCISWAI TCIE TC 0 SBR5 RSRC RIE RDRF 0 0 R5 T5 BRK13 0 R2 T2 TXDIR 0 R1 T1 T8 R6 T6 0x00D0–0x00D7 SCI1 (Asynchronous Serial Interface) Address 0x00D0 0x00D1 0x00D2 0x00D3 0x00D4 0x00D5 0x00D6 0x00D7 Name SCI1BDH SCI1BDL SCI1CR1 SCI1CR2 SCI1SR1 SCI1SR2 SCI1DRH SCI1DRL R W R W R W R W R W R W R W R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 SBR12 SBR4 M ILIE IDLE 0 0 R4 T4 Bit 3 SBR11 SBR3 WAKE TE OR 0 0 R3 T3 Bit 2 SBR10 SBR2 ILT RE NF Bit 1 SBR9 SBR1 PE RWU FE Bit 0 SBR8 SBR0 PT SBK PF RAF 0 R0 T0 SBR7 LOOPS TIE TDRE 0 R8 R7 T7 SBR6 SCISWAI TCIE TC 0 SBR5 RSRC RIE RDRF 0 0 R5 T5 BRK13 0 R2 T2 TXDIR 0 R1 T1 T8 R6 T6 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 53 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x00D8–0x00DF SPI0 (Serial Peripheral Interface) Address 0x00D8 0x00D9 0x00DA 0x00DB 0x00DC 0x00DD 0x00DE 0x00DF Name SPI0CR1 SPI0CR2 SPI0BR SPI0SR Reserved SPI0DR Reserved Reserved R W R W R W R W R W R W R W R W Bit 7 SPIE 0 0 SPIF 0 Bit 6 SPE 0 Bit 5 SPTIE 0 Bit 4 MSTR MODFEN SPPR0 MODF 0 Bit 3 CPOL BIDIROE 0 0 0 Bit 2 CPHA 0 Bit 1 SSOE SPISWAI SPR1 0 0 Bit 0 LSBFE SPC0 SPR0 0 0 SPPR2 0 0 SPPR1 SPTEF 0 SPR2 0 0 Bit 7 0 0 6 0 0 5 0 0 4 0 0 3 0 0 2 0 0 1 0 0 Bit 0 0 0 0x00E0–0x00E7 IIC (Inter IC Bus) Address 0x00E0 0x00E1 0x00E2 0x00E3 0x00E4 0x00E5 0x00E6 0x00E7 Name IBAD IBFD IBCR IBSR IBDR Reserved Reserved Reserved R W R W R W R W R W R W R W R W Bit 7 ADR7 IBC7 IBEN TCF Bit 6 ADR6 IBC6 IBIE IAAS Bit 5 ADR5 IBC5 MS/SL IBB Bit 4 ADR4 IBC4 TX/RX IBAL D4 0 0 0 Bit 3 ADR3 IBC3 TXAK 0 Bit 2 ADR2 IBC2 0 RSTA SRW Bit 1 ADR1 IBC1 0 Bit 0 0 IBC0 IBSWAI RXAK IBIF D1 0 0 0 D7 0 0 0 D6 0 0 0 D5 0 0 0 D3 0 0 0 D2 0 0 0 D0 0 0 0 0x00E8–0x00EF Reserved Space Address 0x00E8– 0x00EF Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 MC9S12KG128 Data Sheet, Rev. 1.15 54 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x00F0–0x00F7 SPI1 (Serial Peripheral Interface) Address 0x00F0 0x00F1 0x00F2 0x00F3 0x00F4 0x00F5 0x00F6 0x00F7 Name SPI1CR1 SPI1CR2 SPI1BR SPI1SR Reserved SPI1DR Reserved Reserved R W R W R W R W R W R W R W R W Bit 7 SPIE 0 0 SPIF 0 Bit 6 SPE 0 Bit 5 SPTIE 0 Bit 4 MSTR MODFEN SPPR0 MODF 0 Bit 3 CPOL BIDIROE 0 0 0 Bit 2 CPHA 0 Bit 1 SSOE SPISWAI SPR1 0 0 Bit 0 LSBFE SPC0 SPR0 0 0 SPPR2 0 0 SPPR1 SPTEF 0 SPR2 0 0 Bit 7 0 0 6 0 0 5 0 0 4 0 0 3 0 0 2 0 0 1 0 0 Bit 0 0 0 0x00F8–0x00FF SPI2 (Serial Peripheral Interface) Address 0x00F8 0x00F9 0x00FA 0x00FB 0x00FC 0x00FD 0x00FE 0x00FF Name SPI2CR1 SPI2CR2 SPI2BR SPI2SR Reserved SPI2DR Reserved Reserved R W R W R W R W R W R W R W R W Bit 7 SPIE 0 0 SPIF 0 Bit 6 SPE 0 Bit 5 SPTIE 0 Bit 4 MSTR MODFEN SPPR0 MODF 0 Bit 3 CPOL BIDIROE 0 0 0 Bit 2 CPHA 0 Bit 1 SSOE SPISWAI SPR1 0 0 Bit 0 LSBFE SPC0 SPR0 0 0 SPPR2 0 0 SPPR1 SPTEF 0 SPR2 0 0 Bit 7 0 0 6 0 0 5 0 0 4 0 0 3 0 0 2 0 0 1 0 0 Bit 0 0 0 0x0100–0x010F Flash Control Register Address 0x0100 0x0101 Name FCLKDIV FSEC R W R W Bit 7 FDIVLD Bit 6 PRDIV8 Bit 5 FDIV5 RNV5 Bit 4 FDIV4 RNV4 Bit 3 FDIV3 RNV3 Bit 2 FDIV2 RNV2 Bit 1 FDIV1 SEC Bit 0 FDIV0 KEYEN MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 55 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0100–0x010F Flash Control Register (continued) Address 0x0102 0x0103 0x0104 0x0105 0x0106 0x0107 0x0108 0x0109 0x010A 0x010B 0x010C 0x010D 0x010E 0x010F Name FTSTMOD FCNFG FPROT FSTAT FCMD Reserved FADDRHI FADDRLO FDATAHI FDATALO Reserved Reserved Reserved Reserved Bit 7 R 0 W R CBEIE W R FPOPEN W R CBEIF W R 0 W R 0 W R W R W R W R W R 0 W R 0 W R 0 W R 0 W Bit 6 0 Bit 5 0 Bit 4 0 0 Bit 3 FDFD DFDIE FPHS ACCERR DFDIF CMDB 0 0 0 FADDRHI FADDRLO FDATAHI FDATALO 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Bit 2 0 0 Bit 1 0 0 Bit 0 0 0 CCIE RNV6 CCIF KEYACC FPHDIS PVIOL FPLDIS BLANK 0 FPLS 0 0x0110–0x011B EEPROM Control Register Address 0x0110 0x0111 0x0112 0x0113 0x0114 0x0115 Name ECLKDIV Bit 7 Bit 6 PRDIV8 0 0 Bit 5 EDIV5 0 0 0 NV5 Bit 4 EDIV4 0 0 0 NV4 Bit 3 EDIV3 0 0 0 Bit 2 EDIV2 0 0 0 Bit 1 EDIV1 0 0 0 Bit 0 EDIV0 0 0 0 R EDIVLD W R 0 Reserved W 0 Reserved for R Factory Test W R ECNFG CBEIE W R EPROT EPOPEN W R ESTAT CBEIF W CCIE NV6 CCIF EPDIS 0 EP2 BLANK EP1 0 EP0 0 PVIOL ACCERR MC9S12KG128 Data Sheet, Rev. 1.15 56 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0110–0x011B EEPROM Control Register (continued) Address 0x0116 0x0117 0x0118 0x0119 0x011A 0x011B Name R W Reserved for R Factory Test W R EADDRHI W R EADDRLO W R EDATAHI W R EDATALO W ECMD Bit 7 0 0 0 Bit 6 CMDB6 0 0 Bit 5 CMDB5 0 0 Bit 4 0 0 0 Bit 3 0 0 0 Bit 2 CMDB2 0 Bit 1 0 0 Bit 0 CMDB0 0 10 2 10 2 9 1 9 1 Bit 8 Bit 0 Bit 8 Bit 0 Bit 7 Bit 15 Bit 7 6 14 6 5 13 5 4 12 4 3 11 3 0x011C–0x013F Reserved Space Address 0x011C– 0x013F Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 0x0140–0x017F CAN0 (MSCAN) Address 0x0140 0x0141 0x0142 0x0143 0x0144 0x0145 0x0146 0x0147 0x0148 0x0149 0x014A Name R W R CAN0CTL1 W R CAN0BTR0 W R CAN0BTR1 W R CAN0RFLG W R CAN0RIER W R CAN0TFLG W R CAN0TIER W R CAN0TARQ W R CAN0TAAK W R CAN0TBSEL W CAN0CTL0 Bit 7 RXFRM CANE SJW1 SAMP WUPIF WUPIE 0 0 0 0 0 Bit 6 RXACT Bit 5 CSWAI LOOPB BRP5 TSEG21 RSTAT1 Bit 4 SYNCH Bit 3 TIME 0 Bit 2 WUPE WUPM BRP2 TSEG12 TSTAT0 Bit 1 SLPRQ SLPAK Bit 0 INITRQ INITAK CLKSRC SJW0 TSEG22 CSCIF CSCIE 0 0 0 0 0 LISTEN BRP4 TSEG20 RSTAT0 BRP3 TSEG13 TSTAT1 BRP1 TSEG11 OVRIF OVRIE TXE1 TXEIE1 ABTRQ1 ABTAK1 BRP0 TSEG10 RXF RXFIE TXE0 TXEIE0 ABTRQ0 ABTAK0 RSTATE1 RSTATE0 0 0 0 0 0 0 0 0 0 0 TSTATE1 0 0 0 0 0 TSTATE0 TXE2 TXEIE2 ABTRQ2 ABTAK2 TX2 TX1 TX0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 57 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0140–0x017F CAN0 (MSCAN) Address 0x014B 0x014C 0x014D 0x014E 0x014F 0x0150– 0x0153 0x0154– 0x0157 0x0158– 0x015B 0x015C– 0x015F 0x0160– 0x016F 0x0170– 0x017F Name CAN0IDAC Reserved Reserved CAN0RXERR CAN0TXERR CAN0IDAR0– CAN0IDAR3 CAN0IDMR0– CAN0IDMR3 CAN0IDAR4– CAN0IDAR7 CAN0IDMR4– CAN0IDMR7 CAN0RXFG CAN0TXFG Bit 7 R 0 W R 0 W R 0 W R RXERR7 W R TXERR7 W R AC7 W R AM7 W R AC7 W R AM7 W R W R W Bit 6 0 0 0 RXERR6 TXERR6 Bit 5 IDAM1 0 0 RXERR5 TXERR5 Bit 4 IDAM0 0 0 RXERR4 TXERR4 Bit 3 0 0 0 RXERR3 TXERR3 Bit 2 IDHIT2 0 0 RXERR2 TXERR2 Bit 1 IDHIT1 0 0 RXERR1 TXERR1 Bit 0 IDHIT0 0 0 RXERR0 TXERR0 AC6 AM6 AC6 AM6 AC5 AM5 AC5 AM5 AC4 AM4 AC4 AM4 AC3 AM3 AC3 AM3 AC2 AM2 AC2 AM2 AC1 AM1 AC1 AM1 AC0 AM0 AC0 AM0 FOREGROUND RECEIVE BUFFER (see Table 1-6) FOREGROUND TRANSMIT BUFFER (see Table 1-6) Table 1-6. Detailed MSCAN Foreground Receive and Transmit Buffer Layout Address 0x00 Name R R W R R W R R W R R W CANxRDSR0– R CANxRDSR7 W R CANRxDLR W R Reserved W R CANxRTSRH W Extended ID Standard ID CANxRIDR0 Extended ID Standard ID CANxRIDR1 Extended ID Standard ID CANxRIDR2 Extended ID Standard ID CANxRIDR3 Bit 7 ID28 ID10 ID20 ID2 ID14 Bit 6 ID27 ID9 ID19 ID1 ID13 Bit 5 ID26 ID8 ID18 ID0 ID12 Bit 4 ID25 ID7 SRR=1 RTR ID11 Bit 3 ID24 ID6 IDE=1 IDE=0 ID10 Bit 2 ID23 ID5 ID17 Bit 1 ID22 ID4 ID16 Bit 0 ID21 ID3 ID15 0x01 ID9 ID8 ID7 0x02 ID6 ID5 ID4 ID3 ID2 ID1 ID0 RTR 0x03 0x04– 0x0B 0x0C 0x0D 0x0E DB7 DB6 DB5 DB4 DB3 DLC3 DB2 DLC2 DB1 DLC1 DB0 DLC0 TSR15 TSR14 TSR13 TSR12 TSR11 TSR10 TSR9 TSR8 MC9S12KG128 Data Sheet, Rev. 1.15 58 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-6. Detailed MSCAN Foreground Receive and Transmit Buffer Layout (continued) Address 0x0F Name CANxRTSRL Extended ID CANxTIDR0 Standard ID Extended ID CANxTIDR1 Standard ID Extended ID CANxTIDR2 Standard ID Extended ID CANxTIDR3 Standard ID CANxTDSR0– CANxTDSR7 CANxTDLR CONxTTBPR CANxTTSRH CANxTTSRL R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 TSR7 Bit 6 TSR6 Bit 5 TSR5 Bit 4 TSR4 Bit 3 TSR3 Bit 2 TSR2 Bit 1 TSR1 Bit 0 TSR0 ID28 ID10 ID20 ID2 ID14 ID27 ID9 ID19 ID1 ID13 ID26 ID8 ID18 ID0 ID12 ID25 ID7 SRR=1 RTR ID11 ID24 ID6 IDE=1 IDE=0 ID10 ID23 ID5 ID17 ID22 ID4 ID16 ID21 ID3 ID15 0x10 0x10 ID9 ID8 ID7 0x12 ID6 ID5 ID4 ID3 ID2 ID1 ID0 RTR 0x13 0x14– 0x1B 0x1C 0x1D 0x1E 0x1F DB7 DB6 DB5 DB4 DB3 DLC3 DB2 DLC2 PRIO2 TSR10 TSR2 DB1 DLC1 PRIO1 TSR9 TSR1 DB0 DLC0 PRIO0 TSR8 TSR0 PRIO7 TSR15 TSR7 PRIO6 TSR14 TSR6 PRIO5 TSR13 TSR5 PRIO4 TSR12 TSR4 PRIO3 TSR11 TSR3 0x0180–0x023F Reserved Space Address 0x0180– 0x023F Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 0x0240–0x027F PIM (Port Integration Module) (Sheet 1 of 3) Address 0x0240 0x0241 0x0242 Name PTT PTIT DDRT R W R W R W Bit 7 PTT7 PTIT7 Bit 6 PTT6 PTIT6 Bit 5 PTT5 PTIT5 Bit 4 PTT4 PTIT4 Bit 3 PTT3 PTIT3 Bit 2 PTT2 PTIT2 Bit 1 PTT1 PTIT1 Bit 0 PTT0 PTIT0 DDRT7 DDRT7 DDRT5 DDRT4 DDRT3 DDRT2 DDRT1 DDRT0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 59 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0240–0x027F PIM (Port Integration Module) (Sheet 2 of 3) Address 0x0243 0x0244 0x0245 0x0246 0x0247 0x0248 0x0249 0x024A 0x024B 0x024C 0x024D 0x024E 0x024F 0x0250 0x0251 0x0252 0x0253 0x0254 0x0255 0x0256 0x0257 0x0258 0x0259 Name RDRT PERT PPST Reserved Reserved PTS PTIS DDRS RDRS PERS PPSS WOMS Reserved PTM PTIM DDRM RDRM PERM PPSM WOMM MODRR PTP PTIP Bit 7 R RDRT7 W R PERT7 W R PPST7 W R 0 W R 0 W R PTS7 W R PTIS7 W R DDRS7 W R RDRS7 W R PERS7 W R PPSS7 W R WOMS7 W R 0 W R PTM7 W R PTIM7 W R DDRM7 W R RDRM7 W R PERM7 W R PPSM7 W R WOMM7 W R 0 W R PTP7 W R PTIP7 W Bit 6 RDRT6 PERT6 PPST6 0 0 Bit 5 RDRT5 PERT5 PPST5 0 0 Bit 4 RDRT4 PERT4 PPST4 0 0 Bit 3 RDRT3 PERT3 PPST3 0 0 Bit 2 RDRT2 PERT2 PPST2 0 0 Bit 1 RDRT1 PERT1 PPST1 0 0 Bit 0 RDRT0 PERT0 PPST0 0 0 PTS6 PTIS6 PTS5 PTIS5 PTS4 PTIS4 PTS3 PTIS3 PTS2 PTIS2 PTS1 PTIS1 PTS0 PTIS0 DDRS7 RDRS6 PERS6 PPSS6 WOMS6 0 DDRS5 RDRS5 PERS5 PPSS5 WOMS5 0 DDRS4 RDRS4 PERS4 PPSS4 WOMS4 0 DDRS3 RDRS3 PERS3 PPSS3 WOMS3 0 DDRS2 RDRS2 PERS2 PPSS2 WOMS2 0 DDRS1 RDRS1 PERS1 PPSS1 WOMS1 0 DDRS0 RDRS0 PERS0 PPSS0 WOMS0 0 PTM6 PTIM6 PTM5 PTIM5 PTM4 PTIM4 PTM3 PTIM3 PTM2 PTIM2 PTM1 PTIM1 PTM0 PTIM0 DDRM7 RDRM6 PERM6 PPSM6 WOMM6 DDRM5 RDRM5 PERM5 PPSM5 WOMM5 DDRM4 RDRM4 PERM4 PPSM4 WOMM4 DDRM3 RDRM3 PERM3 PPSM3 WOMM3 DDRM2 RDRM2 PERM2 PPSM2 WOMM2 DDRM1 RDRM1 PERM1 PPSM1 WOMM1 DDRM0 RDRM0 PERM0 PPSM0 WOMM0 MODRR6 MODRR5 MODRR4 MODRR3 MODRR2 MODRR1 MODRR0 PTP6 PTIP6 PTP5 PTIP5 PTP4 PTIP4 PTP3 PTIP3 PTP2 PTIP2 PTP1 PTIP1 PTP0 PTIP0 MC9S12KG128 Data Sheet, Rev. 1.15 60 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0240–0x027F PIM (Port Integration Module) (Sheet 3 of 3) Address 0x025A 0x025B 0x025C 0x025D 0x025E 0x025F 0x0260 0x0261 0x0262 0x0263 0x0264 0x0265 0x0266 0x0267 0x0268 0x0269 0x026A 0x026B 0x026C 0x026D 0x026E 0x026F 0x0270– 0x027F Name DDRP RDRP PERP PPSP PIEP PIFP PTH PTIH DDRH RDRH PERH PPSH PIEH PIFH PTJ PTIJ DDRJ RDRJ PERJ PPSJ PIEJ PIFJ Reserved R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R Bit 7 DDRP7 RDRP7 PERP7 PPSP7 PIEP7 PIFP7 PTH7 PTIH7 Bit 6 DDRP7 RDRP6 PERP6 PPSP6 PIEP6 PIFP6 PTH6 PTIH6 Bit 5 DDRP5 RDRP5 PERP5 PPSP5 PIEP5 PIFP5 PTH5 PTIH5 Bit 4 DDRP4 RDRP4 PERP4 PPSP4 PIEP4 PIFP4 PTH4 PTIH4 Bit 3 DDRP3 RDRP3 PERP3 PPSP3 PIEP3 PIFP3 PTH3 PTIH3 Bit 2 DDRP2 RDRP2 PERP2 PPSP2 PIEP2 PIFP2 PTH2 PTIH2 Bit 1 DDRP1 RDRP1 PERP1 PPSP1 PIEP1 PIFP1 PTH1 PTIH1 Bit 0 DDRP0 RDRP0 PERP0 PPSS0 PIEP0 PIFP0 PTH0 PTIH0 DDRH7 RDRH7 PERH7 PPSH7 PIEH7 PIFH7 PTJ7 PTIJ7 DDRH7 RDRH6 PERH6 PPSH6 PIEH6 PIFH6 PTJ6 PTIJ6 DDRH5 RDRH5 PERH5 PPSH5 PIEH5 PIFH5 0 0 0 0 0 0 0 0 DDRH4 RDRH4 PERH4 PPSH4 PIEH4 PIFH4 0 0 0 0 0 0 0 0 DDRH3 RDRH3 PERH3 PPSH3 PIEH3 PIFH3 0 0 0 0 0 0 0 0 DDRH2 RDRH2 PERH2 PPSH2 PIEH2 PIFH2 0 0 0 0 0 0 0 0 DDRH1 RDRH1 PERH1 PPSH1 PIEH1 PIFH1 PTJ1 PTIJ1 DDRH0 RDRH0 PERH0 PPSH0 PIEH0 PIFH0 PTJ0 PTIJ0 DDRJ7 RDRJ7 PERJ7 PPSJ7 PIEJ7 PIFJ7 DDRJ7 RDRJ6 PERJ6 PPSJ6 PIEJ6 PIFJ6 DDRJ1 RDRJ1 PERJ1 PPSJ1 PIEJ1 PIFJ1 DDRJ0 RDRJ0 PERJ0 PPSJ0 PIEJ0 PIFJ0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 61 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0280–0x02BF CAN4 (MSCAN) Address 0x0280 0x0281 0x0282 0x0283 0x0284 0x0285 0x0286 0x0287 0x0288 0x0289 0x028A 0x028B 0x028C 0x028D 0x028E 0x028F 0x0290 0x0291 0x0292 0x0293 0x0294 0x0295 Name CAN4CTL0 CAN4CTL1 CAN4BTR0 CAN4BTR1 CAN4RFLG CAN4RIER CAN4TFLG CAN4TIER CAN4TARQ CAN4TAAK CAN4TBSEL CAN4IDAC Reserved Reserved CAN4RXERR CAN4TXERR CAN4IDAR0 CAN4IDAR1 CAN4IDAR2 CAN4IDAR3 CAN4IDMR0 CAN4IDMR1 Bit 7 R RXFRM W R CANE W R SJW1 W R SAMP W R WUPIF W R WUPIE W R 0 W R 0 W R 0 W R 0 W R 0 W R 0 W R 0 W R 0 W R RXERR7 W R TXERR7 W R AC7 W R AC7 W R AC7 W R AC7 W R AM7 W R AM7 W Bit 6 RXACT Bit 5 CSWAI LOOPB BRP5 TSEG21 RSTAT1 Bit 4 SYNCH Bit 3 TIME 0 Bit 2 WUPE WUPM BRP2 TSEG12 TSTAT0 Bit 1 SLPRQ SLPAK Bit 0 INITRQ INITAK CLKSRC SJW0 TSEG22 CSCIF CSCIE 0 0 0 0 0 0 0 0 RXERR6 TXERR6 LISTEN BRP4 TSEG20 RSTAT0 BRP3 TSEG13 TSTAT1 BRP1 TSEG11 OVRIF OVRIE TXE1 TXEIE1 ABTRQ1 ABTAK1 BRP0 TSEG10 RXF RXFIE TXE0 TXEIE0 ABTRQ0 ABTAK0 RSTATE1 RSTATE0 0 0 0 0 0 0 0 0 0 0 TSTATE1 0 0 0 0 0 0 0 0 RXERR3 TXERR3 TSTATE0 TXE2 TXEIE2 ABTRQ2 ABTAK2 TX2 IDHIT2 0 0 RXERR2 TXERR2 TX1 IDHIT1 0 0 RXERR1 TXERR1 TX0 IDHIT0 0 0 RXERR0 TXERR0 IDAM1 0 0 RXERR5 TXERR5 IDAM0 0 0 RXERR4 TXERR4 AC6 AC6 AC6 AC6 AM6 AM6 AC5 AC5 AC5 AC5 AM5 AM5 AC4 AC4 AC4 AC4 AM4 AM4 AC3 AC3 AC3 AC3 AM3 AM3 AC2 AC2 AC2 AC2 AM2 AM2 AC1 AC1 AC1 AC1 AM1 AM1 AC0 AC0 AC0 AC0 AM0 AM0 MC9S12KG128 Data Sheet, Rev. 1.15 62 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x0280–0x02BF CAN4 (MSCAN) (continued) Address 0x0296 0x0297 0x0298 0x0299 0x029A 0x029B 0x029C 0x029D 0x029E 0x029F 0x02A0– 0x02AF 0x02B0– 0x02BF Name CAN4IDMR2 CAN4IDMR3 CAN4IDAR4 CAN4IDAR5 CAN4IDAR6 CAN4IDAR7 CAN4IDMR4 CAN4IDMR5 CAN4IDMR6 CAN4IDMR7 CAN4RXFG CAN4TXFG R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 AM7 AM7 AC7 AC7 AC7 AC7 AM7 AM7 AM7 AM7 Bit 6 AM6 AM6 AC6 AC6 AC6 AC6 AM6 AM6 AM6 AM6 Bit 5 AM5 AM5 AC5 AC5 AC5 AC5 AM5 AM5 AM5 AM5 Bit 4 AM4 AM4 AC4 AC4 AC4 AC4 AM4 AM4 AM4 AM4 Bit 3 AM3 AM3 AC3 AC3 AC3 AC3 AM3 AM3 AM3 AM3 Bit 2 AM2 AM2 AC2 AC2 AC2 AC2 AM2 AM2 AM2 AM2 Bit 1 AM1 AM1 AC1 AC1 AC1 AC1 AM1 AM1 AM1 AM1 Bit 0 AM0 AM0 AC0 AC0 AC0 AC0 AM0 AM0 AM0 AM0 FOREGROUND RECEIVE BUFFER (see Table 1-6) FOREGROUND TRANSMIT BUFFER (see Table 1-6) 0x02C0–0x02E7 PWM (Pulse Width Modulator 8 Bit 8 Channel) Address 0x02C0 0x02C1 0x02C2 0x02C3 0x02C4 0x02C5 0x02C6 0x02C7 Name R W R PWMPOL W R PWMCLK W R PWMPRCLK W R PWMCAE W R PWMCTL W R PWMTST Test Only W R PWMPRSC W PWME Bit 7 PWME7 PPOL7 PCLK7 0 Bit 6 PWME6 PPOL6 PCLK6 PCKB2 CAE6 CON45 0 0 Bit 5 PWME5 PPOL5 PCLK5 PCKB1 CAE5 CON23 0 0 Bit 4 PWME4 PPOL4 PCLK4 PCKB0 CAE4 CON01 0 0 Bit 3 PWME3 PPOL3 PCLK3 0 Bit 2 PWME2 PPOL2 PCLK2 PCKA2 CAE2 PFRZ 0 0 Bit 1 PWME1 PPOL1 PCLK1 PCKA1 CAE1 0 0 0 Bit 0 PWME0 PPOL0 PCLK0 PCKA0 CAE0 0 0 0 CAE7 CON67 0 0 CAE3 PSWAI 0 0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 63 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x02C0–0x02E7 PWM (Pulse Width Modulator 8 Bit 8 Channel) (continued) Address 0x02C8 0x02C9 0x02CA 0x02CB 0x02CC 0x02CD 0x02CE 0x02CF 0x02D0 0x02D1 0x02D2 0x02D3 0x02D4 0x02D5 0x02D6 0x02D7 0x02D8 0x02D9 0x02DA 0x02DB 0x02DC 0x02DD 0x02DE Name R W R PWMSCLB W R PWMSCNTA W R PWMSCNTB W R PWMCNT0 W R PWMCNT1 W R PWMCNT2 W R PWMCNT3 W R PWMCNT4 W R PWMCNT5 W R PWMCNT6 W R PWMCNT7 W R PWMPER0 W R PWMPER1 W R PWMPER2 W R PWMPER3 W R PWMPER4 W R PWMPER5 W R PWMPER6 W R PWMPER7 W R PWMDTY0 W R PWMDTY1 W R PWMDTY2 W PWMSCLA Bit 7 Bit 7 Bit 7 0 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 6 6 6 0 0 6 0 6 0 6 0 6 0 6 0 6 0 6 0 6 0 6 6 6 6 6 6 6 6 6 6 6 Bit 5 5 5 0 0 5 0 5 0 5 0 5 0 5 0 5 0 5 0 5 0 5 5 5 5 5 5 5 5 5 5 5 Bit 4 4 4 0 0 4 0 4 0 4 0 4 0 4 0 4 0 4 0 4 0 4 4 4 4 4 4 4 4 4 4 4 Bit 3 3 3 0 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 3 3 3 3 3 3 3 3 3 3 Bit 2 2 2 0 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 2 2 2 2 2 2 2 2 2 2 Bit 1 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 1 1 1 1 1 1 1 1 1 Bit 0 Bit 0 Bit 0 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 MC9S12KG128 Data Sheet, Rev. 1.15 64 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 0x02C0–0x02E7 PWM (Pulse Width Modulator 8 Bit 8 Channel) (continued) Address 0x02DF 0x02E0 0x02E1 0x02E2 0x02E3 0x02E4 0x02E5 0x02E6 0x02E7 Name PWMDTY3 PWMDTY4 PWMDTY5 PWMDTY6 PWMDTY7 PWMSDN Reserved Reserved Reserved R W R W R W R W R W R W R W R W R W Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 Bit 7 PWMIF 0 0 0 Bit 6 6 6 6 6 6 PWMIE 0 0 0 Bit 5 5 5 5 5 5 Bit 4 4 4 4 4 4 Bit 3 3 3 3 3 3 0 0 0 0 Bit 2 2 2 2 2 2 Bit 1 1 1 1 1 1 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 Bit 0 PWMRSTRT PWMLVL 0 0 0 0 0 0 PWM7IN PWM7INL PWM7ENA 0 0 0 0 0 0 0 0 0 0x02E8–0x03FF Reserved Space Address 0x02E8– 0x03FF Name Reserved R W Bit 7 0 Bit 6 0 Bit 5 0 Bit 4 0 Bit 3 0 Bit 2 0 Bit 1 0 Bit 0 0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 65 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.3.3 Part ID Assignments The part ID is located in two 8-bit registers PARTIDH and PARTIDL (addresses 0x001A and 0x001B after reset. The read-only value is a unique part ID for each revision of the chip. Table 1-7 shows the assigned part ID number. Table 1-7. Assigned Part ID Numbers Device MC9S12KG128 1 Mask Set Number 0L74N Part ID1 0x7100 The coding is as follows: Bit 15-12: Major family identifier Bit 11-8: Minor family identifier Bit 7-4: Major mask set revision number including FAB transfers Bit 3-0: Minor - non full - mask set revision The device memory sizes are located in two 8-bit registers MEMSIZ0 and MEMSIZ1 (addresses 0x001C and 0x001D after reset). Table 1-8 shows the read-only values of these registers. Refer to HCS12 Module Mapping and Control (MMC) block description chapter for further details. Table 1-8. Memory Size Registers Device MC9S12KG128 MC9S12KG128 Register Name MEMSIZ0 MEMSIZ1 Value 0x13 0x80 MC9S12KG128 Data Sheet, Rev. 1.15 66 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.4 System Clock Description The Clock and Reset Generator provides the internal clock signals for the core and all peripheral modules. Figure 1-12 shows the clock connections from the CRG to all modules. Consult the CRG Block Guide for details on clock generation. HCS12 CORE BDM CORE CLOCK MEBI INT CPU MMC DBG Flash RAM EEPROM TIM ATD OSC CRG BUS CLOCK OSCILLATOR CLOCK XTAL PWM SCI0, SCI1 SPI0, SPI1, SPI2 EXTAL CAN0, CAN4 IIC PIM Figure 1-12. Clock Connections 1.5 Modes of Operation Eight possible modes determine the operating configuration of the MC9S12KG128. Each mode has an associated default memory map and external bus configuration controlled by a further pin. Three low power modes exist for the device. 1.5.1 Chip Configuration Summary The operating mode out of reset is determined by the states of the MODC, MODB, and MODA pins during reset (Table 1-9). The MODC, MODB, and MODA bits in the MODE register show the current operating mode and provide limited mode switching during operation. The states of the MODC, MODB, and MODA pins are latched into these bits on the rising edge of the reset signal. The ROMCTL signal allows the setting of the ROMON bit in the MISC register thus controlling whether the internal Flash is visible in the memory MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 67 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) map. ROMON = 1 mean the Flash is visible in the memory map. The state of the ROMCTL pin is latched into the ROMON bit in the MISC register on the rising edge of the reset signal. For further explanation on the modes refer to the HCS12 MEBI block description chapter. Table 1-9. Mode Selection BKGD = MODC 0 PE6 = MODB 0 PE5 = MODA 0 PK7 = ROMCTL X ROMON Bit 1 Mode Description Special Single Chip, BDM allowed and ACTIVE. BDM is allowed in all other modes but a serial command is required to make BDM active. Emulation Expanded Narrow, BDM allowed Special Test (Expanded Wide), BDM allowed Emulation Expanded Wide, BDM allowed Normal Single Chip, BDM allowed Normal Expanded Narrow, BDM allowed Peripheral; BDM allowed but bus operations would cause bus conflicts (must not be used) Normal Expanded Wide, BDM allowed 0 0 0 1 1 1 1 0 1 1 0 0 1 1 1 0 1 0 1 0 1 0 1 X 0 1 X 0 1 X 0 1 1 0 0 1 0 1 0 1 1 0 1 Table 1-10. Clock Selection Based on PE7 PE7 = XCLKS 1 0 Description Loop Controlled Pierce Oscillator selected Full Swing Pierce Oscillator or external clock selected Table 1-11. Voltage Regulator VREGEN VREGEN 1 0 Description Internal Voltage Regulator enabled Internal Voltage Regulator disabled, VDD1,2 and VDDPLL must be supplied externally with 2.5V MC9S12KG128 Data Sheet, Rev. 1.15 68 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.5.2 Security The device will make available a security feature preventing the unauthorized read and write of the memory contents. This feature allows: • Protection of the contents of FLASH, • Protection of the contents of EEPROM, • Operation in single-chip mode, • Operation from external memory with internal FLASH and EEPROM disabled. The user must be reminded that part of the security must lie with the user’s code. An extreme example would be user’s code that dumps the contents of the internal program. This code would defeat the purpose of security. At the same time the user may also wish to put a back door in the user’s program. An example of this is the user downloads a key through the SCI which allows access to a programming routine that updates parameters stored in EEPROM. 1.5.2.1 Securing the Microcontroller Once the user has programmed the FLASH and EEPROM (if desired), the part can be secured by programming the security bits located in the FLASH module. These non-volatile bits will keep the part secured through resetting the part and through powering down the part. The security byte resides in a portion of the Flash array. Check the Flash Block Guide for more details on the security configuration. 1.5.2.2 1.5.2.2.1 Operation of the Secured Microcontroller Normal Single Chip Mode This will be the most common usage of the secured part. Everything will appear the same as if the part was not secured with the exception of BDM operation. The BDM operation will be blocked. 1.5.2.2.2 Executing from External Memory The user may wish to execute from external space with a secured microcontroller. This is accomplished by resetting directly into expanded mode. The internal FLASH and EEPROM will be disabled. BDM operations will be blocked. 1.5.2.3 Unsecuring the Microcontroller In order to unsecure the microcontroller, the internal FLASH and EEPROM must be erased. This can be done through an external program in expanded mode. Once the user has erased the FLASH and EEPROM, the part can be reset into special single chip mode. This invokes a program that verifies the erasure of the internal FLASH and EEPROM. Once this program completes, the user can erase and program the FLASH security bits to the unsecured state. This is generally done through the BDM, but the user could also change to expanded mode (by writing the mode bits through the BDM) and jumping to an external program (again through BDM commands). Note that if the MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 69 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) part goes through a reset before the security bits are reprogrammed to the unsecure state, the part will be secured again. 1.5.3 Low Power Modes The microcontroller features three main low power modes. Consult the respective Block Guide for information on the module behavior in Stop, Pseudo Stop, and Wait Mode. An important source of information about the clock system is the Clock and Reset Generator Guide (CRG). 1.5.3.1 Stop Executing the CPU STOP instruction stops all clocks and the oscillator thus putting the chip in fully static mode. Wake up from this mode can be done via reset or external interrupts. 1.5.3.2 Pseudo Stop This mode is entered by executing the CPU STOP instruction. In this mode the oscillator is still running and the Real Time Interrupt (RTI) or Watchdog (COP) sub module can stay active. Other peripherals are turned off. This mode consumes more current than the full STOP mode, but the wake up time from this mode is significantly shorter. 1.5.3.3 Wait This mode is entered by executing the CPU WAI instruction. In this mode the CPU will not execute instructions. The internal CPU signals (address and data bus) will be fully static. All peripherals stay active. For further power consumption the peripherals can individually turn off their local clocks. 1.5.3.4 Run Although this is not a low power mode, unused peripheral modules should not be enabled in order to save power. 1.6 Resets and Interrupts Consult the Exception Processing section of the CPU12 Reference Manual for information on resets and interrupts. Both local masking and CCR masking are included as listed in Table 1-12. System resets can be generated through external control of the RESET pin, through the clock and reset generator module CRG or through the low voltage reset (LVR) generator of the voltage regulator module. Refer to the CRG and VREG block description chapters for detailed information on reset generation. 1.6.1 1.6.1.1 Vectors Vector Table Table 1-12 lists interrupt sources and vectors in default order of priority. MC9S12KG128 Data Sheet, Rev. 1.15 70 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-12. Interrupt Vector Locations Vector Address 0xFFFE, 0xFFFF Interrupt Source External Reset, Power On Reset or Low Voltage Reset (see CRG Flags Register to determine reset source) Clock Monitor fail reset COP failure reset Unimplemented instruction trap SWI XIRQ IRQ Real Time Interrupt Standard Timer channel 0 Standard Timer channel 1 Standard Timer channel 2 Standard Timer channel 3 Standard Timer channel 4 Standard Timer channel 5 Standard Timer channel 6 Standard Timer channel 7 Standard Timer overflow Pulse accumulator overflow Pulse accumulator input edge SPI0 SCI0 SCI1 ATD Reserved Port J Port H Reserved 0xFFC8, 0xFFC9 0xFFC6, 0xFFC7 0xFFC4, 0xFFC5 0xFFC2, 0xFFC3 CRG PLL lock CRG Self Clock Mode FLASH Double Fault Detect I Bit I Bit I Bit I Bit CRGINT (LOCKIE) CRGINT (SCMIE) FCNFG (DFDIE) CCR Mask None Local Enable None HPRIO Value to Elevate — 0xFFFC, 0xFFFD 0xFFFA, 0xFFFB 0xFFF8, 0xFFF9 0xFFF6, 0xFFF7 0xFFF4, 0xFFF5 0xFFF2, 0xFFF3 0xFFF0, 0xFFF1 0xFFEE, 0xFFEF 0xFFEC, 0xFFED 0xFFEA, 0xFFEB 0xFFE8, 0xFFE9 0xFFE6, 0xFFE7 0xFFE4, 0xFFE5 0xFFE2, 0xFFE3 0xFFE0, 0xFFE1 0xFFDE, 0xFFDF 0xFFDC, 0xFFDD 0xFFDA, 0xFFDB 0xFFD8, 0xFFD9 0xFFD6, 0xFFD7 0xFFD4, 0xFFD5 0xFFD2, 0xFFD3 0xFFD0, 0xFFD1 0xFFCE, 0xFFCF 0xFFCC, 0xFFCD 0xFFCA, 0xFFCB None None None None X Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit PLLCTL (CME, FCME) COP rate select None None None IRQCR (IRQEN) CRGINT (RTIE) TIE (C0I) TIE (C1I) TIE (C2I) TIE (C3I) TIE (C4I) TIE (C5I) TIE (C6I) TIE (C7I) TSCR2 (TOI) PACTL (PAOVI) PACTL (PAI) SPICR1 (SPIE, SPTIE) SCICR2 (TIE, TCIE, RIE, ILIE) SCICR2 (TIE, TCIE, RIE, ILIE) ATDCTL2 (ASCIE) Reserved PIEJ (PIEJ7, PIEJ6, PIEJ1, PIEJ0) PIEH (PIEH7–0) Reserved — — — — — 0xF2 0xF0 0xEE 0xEC 0xEA 0xE8 0xE6 0xE4 0xE2 0xE0 0xDE 0xDC 0xDA 0xD8 0xD6 0xD4 0xD2 0xD0 0xCE 0xCC 0xCA 0xC8 0xC6 0xC4 0xC2 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 71 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) Table 1-12. Interrupt Vector Locations (continued) Vector Address 0xFFC0, 0xFFC1 0xFFBE, 0xFFBF 0xFFBC, 0xFFBD 0xFFBA, 0xFFBB 0xFFB8, 0xFFB9 0xFFB6, 0xFFB7 0xFFB4, 0xFFB5 0xFFB2, 0xFFB3 0xFFB0, 0xFFB1 0xFFAE, 0xFFAF 0xFFAC, 0xFFAD 0xFFAA, 0xFFAB 0xFFA8, 0xFFA9 0xFFA6, 0xFFA7 0xFFA4, 0xFFA5 Reserved 0xFFA2, 0xFFA3 0xFFA0, 0xFFA1 0xFF9E, 0xFF9F 0xFF9C, 0xFF9D 0xFF9A, 0xFF9B 0xFF98, 0xFF99 0xFF96, 0xFF97 0xFF94, 0xFF95 0xFF92, 0xFF93 0xFF90, 0xFF91 0xFF8E, 0xFF8F 0xFF8C, 0xFF8D 0xFF8A, 0xFF8B 0xFF80 - 0xFF89 CAN4 wake-up CAN4 errors CAN4 receive CAN4 transmit Port P PWM Emergency Shutdown VREG Low Voltage Interrupt Reserved I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit CAN4RIER (WUPIE) CAN4RIER (CSCIE, OVRIE) CAN4RIER (RXFIE) CAN4TIER (TXEIE2–TXEIE0) PIEP (PIEP7–0) PWMSDN (PWMIE) CTRL0 (LVIE) Reserved Interrupt Source IIC Bus SPI1 SPI2 EEPROM command FLASH command CAN0 wake-up CAN0 errors CAN0 receive CAN0 transmit CCR Mask I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit I Bit Reserved 0xA2 0xA0 0x9E 0x9C 0x9A 0x98 0x96 0x94 0x92 0x90 0x8E 0x8C 0x8A 0x80 - 0x89 Local Enable IBCR (IBIE) SPICR1 (SPIE, SPTIE) SPICR1 (SPIE, SPTIE) ECNFG (CCIE, CBEIE) FCNFG (CCIE, CBEIE) CAN0RIER (WUPIE) CAN0RIER (CSCIE, OVRIE) CAN0RIER (RXFIE) CAN0TIER (TXEIE2–TXEIE0) HPRIO Value to Elevate 0xC0 0xBE 0xBC 0xBA 0xB8 0xB6 0xB4 0xB2 0xB0 0xAE 0xAC 0xAA 0xA8 0xA6 0xA4 MC9S12KG128 Data Sheet, Rev. 1.15 72 Freescale Semiconductor Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) 1.6.2 Resets Resets are a subset of the interrupts featured inTable 1-12. The different sources capable of generating a system reset are summarized in Table 1-13. Table 1-13. Reset Summary Reset Power-on Reset External Reset Low Voltage Reset Clock Monitor Reset COP Watchdog Reset Priority 1 1 1 2 3 Source CRG Module RESET pin VREG Module CRG Module CRG Module Vector 0xFFFE, 0xFFFF 0xFFFE, 0xFFFF 0xFFFE, 0xFFFF 0xFFFC, 0xFFFD 0xFFFA, 0xFFFB 1.6.2.1 Effects of Reset When a reset occurs, MCU registers and control bits are changed to known start-up states. Refer to the respective module block description chapters for register reset states. Refer to the PIM block description chapter for reset configurations of all peripheral module ports. Refer to Table 1-5 for locations of the memories depending on the operating mode after reset. The RAM array is not automatically initialized out of reset. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 73 Chapter 1 MC9S12KG128 Device Overview (MC9S12KG128V1) MC9S12KG128 Data Sheet, Rev. 1.15 74 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.1 Introduction This document describes the FTS128K1ECC module that includes a 128Kbyte Flash (nonvolatile) memory with built-in Error Code Correction (ECC). The Flash memory may be read as either bytes, aligned words, or misaligned words. Read access time is one bus cycle for bytes and aligned words, and two bus cycles for misaligned words. The Flash memory is ideal for program and data storage for single-supply applications allowing for field reprogramming without requiring external voltage sources for program or erase. Program and erase functions are controlled by a command driven interface. The Flash module supports both block erase and sector erase. An erased bit reads 1 and a programmed bit reads 0. The high voltage required to program and erase the Flash memory is generated internally. It is not possible to read from a Flash block while it is being erased or programmed. The ECC logic is included in the Flash module with the program and erase operations automatically generating the ECC parity bits. The ECC logic implements a modified Hamming code capable of correcting single bit faults and detecting double bit faults in each word of the Flash memory. CAUTION A Flash word must be in the erased state before being programmed. Cumulative programming of bits within a Flash word is not allowed and will result in invalid data stored. 2.1.1 Glossary Command Write Sequence — A three-step MCU instruction sequence to execute built-in algorithms (including program and erase) on the Flash memory. 2.1.2 • • • • • • Features 128 Kbytes of Flash memory comprised of one 128 Kbyte block divided into 128 sectors of 1024 bytes with every word (two bytes) accompanied by 6 ECC parity bits Single bit fault correction per word during read operations Automated program and erase algorithm with generation of ECC parity bits Interrupts on Flash command completion, command buffer empty and double bit fault detection Fast sector erase and word program operation 2-stage command pipeline for faster multi-word program times MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 75 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) • • • • • Sector erase abort feature for critical interrupt response Flexible protection scheme to prevent accidental program or erase Single power supply for all Flash operations including program and erase Security feature to prevent unauthorized access to the Flash memory Code integrity check using built-in data compression 2.1.3 Modes of Operation Program, erase, erase verify, and data compress operations (please refer to Section 2.4.1 for details). 2.1.4 Block Diagram A block diagram of the Flash module is shown in Figure 2-1. MC9S12KG128 Data Sheet, Rev. 1.15 76 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) FTS128K1ECC Command Interface Command Pipeline Command Interrupt Request comm2 addr2 data2 comm1 addr1 data1 Flash Block 64K * 22 Bits sector 0 sector 1 sector 127 Protection Double Fault Detect Interrupt Request Error Detection and Correction Security Oscillator Clock Clock Divider FCLK Figure 2-1. FTS128K1ECC Block Diagram 2.2 External Signal Description The Flash module contains no signals that connect off-chip. 2.3 Memory Map and Register Definition This subsection describes the memory map and registers for the Flash module. 2.3.1 Module Memory Map The Flash memory map is shown in Figure 2-2. The HCS12 architecture places the Flash memory addresses between 0x4000 and 0xFFFF which corresponds to three 16-Kbyte pages. The content of the MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 77 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) HCS12 core PPAGE register is used to map the logical middle page ranging from address 0x8000 to 0xBFFF to any physical 16 Kbyte page in the Flash memory. By placing 0x3E or 0x3F in the HCS12 Core PPAGE register, the associated 16 Kbyte pages appear twice in the MCU memory map. The FPROT register, described in Section 2.3.2.5, “Flash Protection Register (FPROT)”, can be set to globally protect a Flash block. However, three separate memory regions, one growing upward from the first address in the next-to-last page in the Flash block (called the lower region), one growing downward from the last address in the last page in the Flash block (called the higher region), and the remaining addresses in the Flash block, can be activated for protection. The Flash locations of these protectable regions are shown in Table 2-2. The higher address region is mainly targeted to hold the boot loader code because it covers the vector space. The lower address region can be used for EEPROM emulation in an MCU without an EEPROM module because it can remain unprotected while the remaining addresses are protected from program or erase. Security information that allows the MCU to restrict access to the Flash module is stored in the Flash configuration field, described in Table 2-1. Table 2-1. Flash Configuration Field Unpaged Flash Address 0xFF00 - 0xFF07 Paged Flash Address (PPAGE 0x3F) 0xBF00-0xBF07 Size (bytes) 8 Description Backdoor Comparison Key Refer to Section Section 2.6.1, “Unsecuring the MCU using Backdoor Key Access” Reserved Flash Protection byte Refer to Section 2.3.2.5, “Flash Protection Register (FPROT)” Reserved Flash Security byte Refer to Section 2.3.2.2, “Flash Security Register (FSEC)” 0xFF08 - 0xFF0C 0xFF0D 0xBF08-0xBF0C 0xBF0D 5 1 0xFF0E 0xFF0F 0xBF0E 0xBF0F 1 1 MC9S12KG128 Data Sheet, Rev. 1.15 78 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) (16 bytes) MODULE BASE + 0x0000 Flash Registers MODULE BASE + 0x000F FLASH_START = 0x4000 0x4400 0x4800 0x5000 Flash Protected Low Sectors 1, 2, 4, 8 Kbytes 0x6000 0x3E 0x8000 Flash Block 16K PAGED MEMORY 0x38 0x39 0x3A 0x3B 0x3C 0x3D 0x3E 0x3F 0xC000 0xE000 0x3F Flash Protected High Sectors 2, 4, 8, 16 Kbytes 0xF000 0xF800 FLASH_END = 0xFFFF 0xFF00 - 0xFF0F, Flash Configuration Field Note: 0x38-0x3F correspond to the PPAGE register content Figure 2-2. Flash Memory Map MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 79 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-2. Detailed Flash Memory Map Summary MCU Address Range 0x4000-0x7FFF PPAGE Unpaged (0x3E) ProtectableLower Range 0x4000-0x43FF 0x4000-0x47FF 0x4000-0x4FFF 0x4000-0x5FFF 0x8000-0xBFFF 0x38 0x39 0x3A 0x3B 0x3C 0x3D 0x3E N.A. N.A. N.A. N.A. N.A. N.A. 0x8000-0x83FF 0x8000-0x87FF 0x8000-0x8FFF 0x8000-0x9FFF 0x3F N.A. 0xB800-0xBFFF 0xB000-0xBFFF 0xA000-0xBFFF 0x8000-0xBFFF 0xC000-0xFFFF Unpaged (0x3F) N.A. 0xF800-0xFFFF 0xF000-0xFFFF 0xE000-0xFFFF 0xC000-0xFFFF 1 Protectable Higher Range N.A. Block Relative Address1 0x18000-0x1BFFF N.A. N.A. N.A. N.A. N.A. N.A. N.A. 0x00000-0x03FFF 0x04000-0x07FFF 0x08000-0x0BFFF 0x0C000-0x0FFFF 0x10000-0x13FFF 0x14000-0x17FFF 0x18000-0x1BFFF 0x1C000-0x1FFFF 0x1C000-0x1FFFF Block Relative Address for 128 Kbyte Flash block consists of 17 address bits. The Flash module also contains a set of 16 control and status registers located in address space module base + 0x0000 to module base + 0x000F. A summary of these registers is given in Table 2-3 while their accessibility in normal and special modes is detailed in Section 2.3.2, “Register Descriptions”. Table 2-3. Flash Register Map MODULE BASE + 0x0000 0x0001 0x0002 0x0003 0x0004 Use Flash Clock Divider Register (FCLKDIV) Flash Security Register (FSEC) Flash Test Mode Register (FTSTMOD) Flash Configuration Register (FCNFG) Flash Protection Register (FPROT) Normal Mode Access R/W R R/W R/W R/W MC9S12KG128 Data Sheet, Rev. 1.15 80 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-3. Flash Register Map 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 1 Flash Status Register (FSTAT) Flash Command Register (FCMD) RESERVED11 Flash High Address Register (FADDRHI) Flash Low Address Register (FADDRLO) Flash High Data Register (FDATAHI) Flash Low Data Register (FDATALO) RESERVED2 RESERVED4 1 R/W R/W R R R R R R R R R RESERVED31 1 RESERVED51 Intended for factory test purposes only. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 81 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.3.2 Register Descriptions Bit 7 R W FDIVLD PRDIV8 FDIV5 FDIV4 FDIV3 FDIV2 FDIV1 FDIV0 6 5 4 3 2 1 Bit 0 Register Name FCLKDIV FSEC R W KEYEN RNV5 RNV4 RNV3 RNV2 SEC FTSTMOD R W 0 0 0 0 0 0 0 0 FCNFG R CBEIE W CCIE KEYACC 0 0 0 0 0 FPROT R FPOPEN W RNV6 FPHDIS FPHS FPLDIS FPLS FSTAT R CBEIF W CCIF PVIOL ACCERR 0 BLANK 0 0 FCMD R W 0 CMDB FCTL R W NV7 NV6 NV5 NV4 NV3 NV2 NV1 NV0 FADDRHI R W FADDRHI FADDRLO R W FADDRLO FDATAHI R W FDATAHI FDATALO R W FDATALO RESERVED1 R W 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 2-3. FTS128K1ECC Register Summary MC9S12KG128 Data Sheet, Rev. 1.15 82 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Register Name RESERVED2 R W RESERVED3 R W RESERVED4 R W Bit 7 0 6 0 5 0 4 0 3 0 2 0 1 0 Bit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 2-3. FTS128K1ECC Register Summary (continued) 2.3.2.1 Flash Clock Divider Register (FCLKDIV) The FCLKDIV register is used to control timed events in program and erase algorithms. 7 R W Reset 0 0 0 0 0 0 0 0 FDIVLD PRDIV8 FDIV5 FDIV4 FDIV3 FDIV2 FDIV1 FDIV0 6 5 4 3 2 1 0 = Unimplemented or Reserved Figure 2-4. Flash Clock Divider Register (FCLKDIV) All bits in the FCLKDIV register are readable, bits 6-0 are write once and bit 7 is not writable. Table 2-4. FCLKDIV Field Descriptions Field 7 FDIVLD 6 PRDIV8 5-0 FDIV[5:0] Description Clock Divider Loaded. 0 Register has not been written. 1 Register has been written to since the last reset. Enable Prescalar by 8. 0 The oscillator clock is directly fed into the clock divider. 1 The oscillator clock is divided by 8 before feeding into the clock divider. Clock Divider Bits — The combination of PRDIV8 and FDIV[5:0] must divide the oscillator clock down to a frequency of 150 kHz–200 kHz. The maximum divide ratio is 512. Please refer to Section 2.4.1.1, “Writing the FCLKDIV Register” for more information. 2.3.2.2 Flash Security Register (FSEC) The FSEC register holds all bits associated with the security of the MCU and Flash module. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 83 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 7 R W Reset F KEYEN 6 5 RNV5 4 RNV4 3 RNV3 2 RNV2 1 SEC 0 F F F F F F F = Unimplemented or Reserved Figure 2-5. Flash Security Register (FSEC) All bits in the FSEC register are readable but are not writable. The FSEC register is loaded from the Flash Configuration Field at address $FF0F during the reset sequence, indicated by F in Figure 2-5. If the DFDIF flag in the FSTAT register is set while reading the security field location during the reset sequence, all bits in the FSEC register will be set to leave the module in a secured state with backdoor key access disabled. Table 2-5. FSEC Field Descriptions Field Description 1-0 Backdoor Key Security Enable Bits —The KEYEN[1:0] bits define the enabling of backdoor key access to the KEYEN[1:0] Flash module as shown in Table 2-6. 5-2 RNV[5:2] 1-0 SEC[1:0] Reserved Nonvolatile Bits — The RNV[5:2] bits must remain in the erased 1 state for future enhancements. Flash Security Bits — The SEC[1:0] bits define the security state of the MCU as shown in Table 2-7. If the Flash module is unsecured using backdoor key access, the SEC bits are forced to 10. Table 2-6. Flash KEYEN States KEYEN[1:0] 00 011 10 11 1 Status of Backdoor Key Access DISABLED DISABLED ENABLED DISABLED Preferred KEYEN state to disable Backdoor Key Access. Table 2-7. Flash Security States SEC[1:0] 00 01 1 Status of Security SECURED SECURED UNSECURED SECURED 10 11 1 Preferred SEC state to set MCU to secured state. The security function in the Flash module is described in Section 2.6, “Flash Module Security”. MC9S12KG128 Data Sheet, Rev. 1.15 84 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.3.2.3 Flash Test Mode Register (FTSTMOD) The FTSTMOD register is used to control Flash test features. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 FDFD 3 2 0 1 0 0 0 = Unimplemented or Reserved Figure 2-6. Flash Test Mode Register (FTSTMOD) FDFD is readable and writable while all remaining bits read 0 and are not writable in normal mode. Table 2-8. FTSTMOD Field Descriptions Field 3 FDFD Description Force Double Fault Detect — The FDFD bit allows the user to simulate a double bit fault during Flash array read operations and check the associated interrupt routine. The FDFD bit is cleared by writing a 0 to FDFD. 0 Flash array read operations will set the DFDIF flag in the FSTAT register only if a double bit fault is detected. 1 Any Flash array read operation will force the DFDIF flag in the FSTAT register to be set and an interrupt will be generated as long as the DFDIE interrupt enable in the FCNFG register is set. 2.3.2.4 Flash Configuration Register (FCNFG) The FCNFG register enables the Flash interrupts and gates the security backdoor writes. 7 R CBEIE W Reset 0 0 0 0 0 0 0 0 CCIE KEYACC 6 5 4 0 3 0 2 0 BKSEL 1 0 = Unimplemented or Reserved Figure 2-7. Flash Configuration Register (FCNFG) CBEIE, CCIE, KEYACC and DFDIE bits are readable and writable while all remaining bits read 0 and are not writable. KEYACC is only writable if KEYEN (see Section 2.3.2.2) is set to the enabled state. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 85 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-9. FCNFG Field Descriptions Field 7 CBEIE Description Command Buffer Empty Interrupt Enable — The CBEIE bit enables an interrupt in case of an empty command buffer in the Flash module. 0 Command buffer empty interrupt disabled. 1 An interrupt will be requested whenever the CBEIF flag (see Section 2.3.2.7, “Flash Status Register (FSTAT)”) is set. Command Complete Interrupt Enable — The CCIE bit enables an interrupt in case all commands have been completed in the Flash module. 0 Command complete interrupt disabled. 1 An interrupt will be requested whenever the CCIF flag (see Section 2.3.2.7, “Flash Status Register (FSTAT)”) is set. Enable Security Key Writing 0 Flash writes are interpreted as the start of a command write sequence. 1 Writes to Flash array are interpreted as keys to open the backdoor. Reads of the Flash array return invalid data. Double Fault Detect Interrupt Enable — The DFDIE bit enables an interrupt in case a double bit fault is detected during a Flash block operation. 0 Double bit fault detect interrupt disabled. 1 An interrupt will be requested whenever the DFDIF flag is set (see Section 2.3.2.7, “Flash Status Register (FSTAT)”). 6 CCIE 5 KEYACC 3 DFDIE 2.3.2.5 Flash Protection Register (FPROT) The FPROT register defines which Flash sectors are protected against program or erase operations. All bits in the FPROT register are readable and writable with restrictions except for RNV[6] which is only readable (see Section 2.3.2.6, “Flash Protection Restrictions”). During reset, the FPROT register is loaded from the Flash Configuration Field at address 0xFF0D. To change the Flash protection that will be loaded during the reset sequence, the upper sector of the Flash memory must be unprotected, then the Flash Protect/Security byte located as described in Table 2-1 must be reprogrammed. If the DFDIF flag in the FSTAT register is set while reading the protection field location during the reset sequence, the FPOPEN bit will be cleared and remaining bits in the FPROT register will be set to leave the Flash block fully protected. Trying to alter data in any of the protected areas in the Flash block will result in a protection violation error and the PVIOL flag will be set in the FSTAT register. A mass erase of the Flash block is not possible if any of the contained Flash sectors are protected. MC9S12KG128 Data Sheet, Rev. 1.15 86 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-10. FPROT Field Descriptions Field 7 FPOPEN Description Protection Function Bit — The FPOPEN bit determines the protection function for program or erase as shown in Table 2-11. 0 FPHDIS and FPLDIS bits define unprotected address ranges as specified by the corresponding FPHS[1:0] and FPLS[1:0] bits. For an MCU without an EEPROM module, the FPOPEN clear state allows the main part of the Flash block to be protected while a small address range can remain unprotected for EEPROM emulation. 1 FPHDIS and FPLDIS bits enable protection for the address range specified by the corresponding FPHS[1:0] and FPLS[1:0] bits. Reserved Nonvolatile Bit — The RNV[6] bit must remain in the erased state 1 for future enhancements. Flash Protection Higher Address Range Disable — The FPHDIS bit determines whether there is a protected/unprotected area in the higher address space of the Flash block. 0 Protection/Unprotection enabled 1 Protection/Unprotection disabled Flash Protection Higher Address Size — The FPHS[1:0] bits determine the size of the protected/unprotected area as shown in Table 2-12. The FPHS[1:0] bits can only be written to while the FPHDIS bit is set. Flash Protection Lower address range Disable — The FPLDIS bit determines whether there is a protected/unprotected area in the lower address space of the Flash block. 0 Protection/Unprotection enabled 1 Protection/Unprotection disabled Flash Protection Lower Address Size — The FPLS[1:0] bits determine the size of the protected/unprotected area as shown in Table 2-13. The FPLS[1:0] bits can only be written to while the FPLDIS bit is set. 6 RNV[6] 5 FPHDIS 4:3 FPHS[1:0] 2 FPLDIS 1:0 FPLS[1:0] Table 2-11. Flash Protection Function FPOPEN 1 1 1 1 0 0 0 0 1 FPHDIS 1 1 0 0 1 1 0 0 FPLDIS 1 0 1 0 1 0 1 0 No Protection Function1 Protected Low Range Protected High Range Protected High and Low Ranges Full Block Protected Unprotected Low Range Unprotected High Range Unprotected High and Low Ranges For range sizes, refer to and . MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 87 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-12. Flash Protection Higher Address Range FPHS[1:0] 00 01 10 11 Unpaged Address Range 0xF800-0xFFFF 0xF000-0xFFFF 0xE000-0xFFFF 0xC000-0xFFFF Paged Address Range 0x3F: 0xC800-0xCFFF 0x3F: 0xC000-0xCFFF 0x3F: 0xB000-0xCFFF 0x3F: 0x8000-0xCFFF Protected Size 2 Kbytes 4 Kbytes 8 Kbytes 16 Kbytes Table 2-13. Flash Protection Lower Address Range FPLS[1:0] 00 01 10 11 Unpaged Address Range 0x4000-0x43FF 0x4000-0x47FF 0x4000-0x4FFF 0x4000-0x5FFF Paged Address Range 0x3E: 0x8000-0x83FF 0x3E: 0x8000-0x87FF 0x3E: 0x8000-0x8FFF 0x3E: 0x8000-0x9FFF Protected Size 1 Kbyte 2 Kbytes 4 Kbytes 8 Kbytes All possible Flash protection scenarios are illustrated in Figure 2-8. Although the protection scheme is loaded from the Flash array after reset, it can be changed by the user. This protection scheme can be used by applications requiring re-programming in single-chip mode while providing as much protection as possible if re-programming is not required. MC9S12KG128 Data Sheet, Rev. 1.15 88 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) FPHDIS=1 FPLDIS=1 Scenario 7 FPHDIS=1 FPLDIS=0 6 FPHDIS=0 FPLDIS=1 5 FPHDIS=0 FPLDIS=0 4 PPAGE 0x38-0x3D PPAGE 0x3E-0x3F Scenario 3 2 1 0 PPAGE 0x38-0x3D FPHS[1:0] FPHS[1:0] FPLS[1:0] FPOPEN=0 89 PPAGE 0x3E-0x3F Unprotected region Protected region not defined by FPLS, FPHS Protected region with size defined by FPLS Protected region with size defined by FPHS Figure 2-8. Flash Protection Scenarios MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor FPLS[1:0] FPOPEN=1 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.3.2.6 Flash Protection Restrictions The general guideline is that Flash protection can only be added and not removed. Table 2-14 specifies all valid transitions between Flash protection scenarios. Any attempt to write an invalid scenario to the FPROT register will be ignored and the FPROT register will remain unchanged. The contents of the FPROT register reflect the active protection scenario. See the FPHS and FPLS descriptions for additional restrictions. Table 2-14. Flash Protection Scenario Transitions From Protection Scenario 0 1 2 3 4 5 6 7 1 To Protection Scenario1 0 X 1 X X X 2 X 3 X X X X X X X X X X X X X X X X X X X X X X 4 5 6 7 Allowed transitions marked with X. 2.3.2.7 Flash Status Register (FSTAT) The FSTAT register defines the operational status of the module. 7 R CBEIF W Reset 1 1 0 0 0 0 0 0 6 CCIF PVIOL ACCERR DFDIF 5 4 3 2 BLANK 1 0 0 0 = Unimplemented or Reserved Figure 2-9. Flash Status Register (FSTAT - Normal Mode) 7 R CBEIF W Reset 1 1 0 0 0 0 0 0 6 CCIF PVIOL ACCERR DFDIF 5 4 3 2 BLANK FAIL 1 0 0 = Unimplemented or Reserved Figure 2-10. Flash Status Register (FSTAT - Special Mode) MC9S12KG128 Data Sheet, Rev. 1.15 90 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) CBEIF, PVIOL, ACCERR and DFDIF are readable and writable, CCIF and BLANK are readable and not writable, remaining bits read 0 and are not writable in normal mode. FAIL is readable and writable in special mode. FAIL must be clear when starting a command write sequence. Table 2-15. FSTAT Field Descriptions Field 7 CBEIF Description Command Buffer Empty Interrupt Flag — The CBEIF flag indicates that the address, data and command buffers are empty so that a new command write sequence can be started. The CBEIF flag is cleared by writing a 1 to CBEIF. Writing a 0 to the CBEIF flag has no effect on CBEIF. Writing a 0 to CBEIF after writing an aligned word to the Flash address space but before CBEIF is cleared will abort a command write sequence and cause the ACCERR flag to be set. Writing a 0 to CBEIF outside of a command write sequence will not set the ACCERR flag. The CBEIF flag is used together with the CBEIE bit in the FCNFG register to generate an interrupt request (see Figure 2-30). 0 Buffers are full. 1 Buffers are ready to accept a new command. Command Complete Interrupt Flag — The CCIF flag indicates that there are no more commands pending. The CCIF flag is cleared when CBEIF is clear and sets automatically upon completion of all active and pending commands. The CCIF flag does not set when an active commands completes and a pending command is fetched from the command buffer. Writing to the CCIF flag has no effect on CCIF. The CCIF flag is used together with the CCIE bit in the FCNFG register to generate an interrupt request (see Figure 2-30). 0 Command in progress. 1 All commands are completed. Protection Violation Flag — The PVIOL flag indicates an attempt was made to program or erase an address in a protected area of the Flash block during a command write sequence. The PVIOL flag is cleared by writing a 1 to PVIOL. Writing a 0 to the PVIOL flag has no effect on PVIOL. While PVIOL is set, it is not possible to launch a command or start a command write sequence. 0 No failure. 1 A protection violation has occurred. Access Error Flag — The ACCERR flag indicates an illegal access to the Flash array caused by either a violation of the command write sequence, issuing an illegal command (illegal combination of the CMDBx bits in the FCMD register), launching the sector erase abort command terminating a sector erase operation early, detection of a double fault or the execution of a CPU STOP instruction while a command is executing (CCIF = 0). The ACCERR flag is cleared by writing a 1 to ACCERR. Writing a 0 to the ACCERR flag has no effect on ACCERR. While ACCERR is set, it is not possible to launch a command or start a command write sequence. If ACCERR is set by the detection of a double fault, an erase verify operation or a data compress operation, any buffered command will not launch. 0 No access error detected. 1 Access error has occurred. 6 CCIF 5 PVIOL 4 ACCERR MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 91 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-15. FSTAT Field Descriptions Field 3 DFDIF Description Double Fault Detect Interrupt Flag — The DFDIF flag indicates that one of the following Flash block operations has detected a double bit fault in the stored parity and data bits. • Array Read. • Erase Verify. • Data Compress. • Reset Sequence (reads of the protection and security fields stored in the Flash memory). When the DFDIF flag is set during a Flash array read operation, the data read from the Flash module are the data bits read out of the Flash array without correction and should be considered invalid. When the DFDIF flag is set during a Flash array read, erase verify, data compress or reset sequence operation, the Flash block address containing the parity and data bits that caused the DFDIF flag to set will be stored in the FADDR register and the parity bits will be stored in the FDATA register. The DFDIF flag is cleared by writing a 1 to the ACCERR bit which is set when the DFDIF flag is set. Writing a 0 to the DFDIF flag has no effect on DFDIF. The DFDIF flag is used together with the DFDIE enable bit to generate an interrupt request (see Figure 2-30). While DFDIF is set, Flash array read operations are allowed. If DFDIF is not cleared and another double bit fault is detected, the FADDR and FDATA registers will maintain the contents from the fault that caused the DFDIF bit to set. 0 No double bit fault detected. 1 Double bit fault detected. Erase Verify Operation Status Flag — When the CCIF flag is set after completion of an erase verify command, the BLANK flag indicates the result of the erase verify operation. The BLANK flag is cleared by the Flash module when CBEIF is cleared as part of a new valid command write sequence. Writing to the BLANK flag has no effect on BLANK. 0 Flash block verified as not erased. 1 Flash block verified as erased. Flag Indicating a Failed Flash Operation — The FAIL flag will set if the erase verify operation fails (Flash block verified as not erased). The FAIL flag will also set if a double bit fault is detected during an array read, erase verify, or data compress operation. The FAIL flag is cleared by writing a 1 to FAIL. Writing a 0 to the FAIL flag has no effect on FAIL. 0 Flash operation completed without error. 1 Flash operation failed. 2 BLANK 1 FAIL 2.3.2.8 Flash Command Register (FCMD) The FCMD register is the Flash command register. 7 R W Reset 0 0 0 0 = Unimplemented or Reserved 0 6 5 4 3 CMDB 0 0 0 0 2 1 0 Figure 2-11. Flash Command Register (FCMD - NVM User Mode) All CMDB bits are readable and writable during a command write sequence while bit 7 reads 0 and is not writable. MC9S12KG128 Data Sheet, Rev. 1.15 92 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Table 2-16. FCMD Field Descriptions Field 6-0 CMDB[6:0] Description Flash Command — Valid Flash commands are shown in Table 2-17. Writing any command other than those listed in Table 2-17 sets the ACCERR flag in the FSTAT register. Table 2-17. Valid Flash Command List CMDB[6:0] 0x05 0x06 0x20 0x40 0x41 0x47 NVM Command Erase Verify Data Compress Word Program Sector Erase Mass Erase Sector Erase Abort 2.3.2.9 RESERVED1 7 6 0 0 5 0 0 4 0 0 3 0 0 2 0 0 1 0 0 0 0 0 This register is reserved for factory testing and is not accessible. R W Reset 0 = Unimplemented or Reserved 0 Figure 2-12. RESERVED1 All bits read 0 and are not writable. Table 2-18. FCTL Field Descriptions Field 7-0 NV[7:0] Description Nonvolatile Bits — The NV[7:0] bits are available as nonvolatile bits. Refer to the Device User Guide for proper use of the NV bits. 2.3.2.10 Flash Address Registers (FADDR) The FADDRHI and FADDRLO registers are the Flash address registers. 7 R W Reset 0 0 0 0 0 0 0 0 6 5 4 FADDRHI 3 2 1 0 = Unimplemented or Reserved Figure 2-13. Flash Address High Register (FADDRHI) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 93 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 7 R W Reset 0 6 5 4 FADDRLO 3 2 1 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 2-14. Flash Address Low Register (FADDRLO) All FADDRHI and FADDRLO bits are readable but are not writable. After an array write as part of a command write sequence, the FADDR registers will contain the mapped MCU address written. If a double bit fault is detected, as indicated by the setting of the DFDIF bit in the FSTAT register, the faulty Flash block address is stored in the FADDR registers as a word address. The faulty Flash block address remains readable until the start of the next command write sequence. The mapping of the FADDR registers to the MCU address is shown in Figure 2-15 and Figure 2-16. Byte Select MCU Address PPAGE Register FADDR Register 1 1 1 1 0 AB13 AB12 AB11 AB10 AB9 AB8 AB7 AB6 AB5 AB4 AB3 AB2 AB1 AB0 PIX2 PIX1 PIX0 FADDRHI[7:0] FADDRLO[7:0] Figure 2-15. FADDR to MCU Address Mapping (Paged) Byte Select MCU Address (0x4000-0x7FFF) 0 1 AB13 AB12 AB11 AB10 AB9 AB8 AB7 AB6 AB5 AB4 AB3 AB2 AB1 AB0 0 FADDR Register 1 1 1 FADDRHI[4:0] FADDRLO[7:0] MCU Address (0xC000-0xFFFF) 1 1 AB13 AB12 AB11 AB10 AB9 AB8 AB7 AB6 AB5 AB4 AB3 AB2 AB1 AB0 Byte Select Figure 2-16. FADDR to MCU Address Mapping (Unpaged) MC9S12KG128 Data Sheet, Rev. 1.15 94 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.3.2.11 Flash Data Registers (FDATA) The FDATAHI and FDATALO registers are the Flash data registers. 7 R W Reset 0 0 0 0 0 0 0 0 6 5 4 FDATAHI 3 2 1 0 = Unimplemented or Reserved Figure 2-17. Flash Data High Register (FDATAHI) 7 R W Reset 0 0 0 0 0 0 0 0 6 5 4 FDATALO 3 2 1 0 = Unimplemented or Reserved Figure 2-18. Flash Data Low Register (FDATALO) All FDATAHI and FDATALO bits are readable but are not writable. After an array write as part of a command write sequence, the FDATA registers will contain the data written. At the completion of a data compress operation, the resulting 16-bit signature is stored in the FDATA registers. The data compression signature is readable in the FDATA registers until a new command write sequence is started or a double bit fault is detected in a Flash array read operation. If a double bit fault is detected during a Flash array read, erase verify or data compress operation, the parity bits stored in the Flash array at the failed location will be stored in the lower six bits of FDATALO. The faulty parity bits remain readable until the start of the next command write sequence. 2.3.2.12 RESERVED2 This register is reserved for factory testing and is not accessible. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 2-19. RESERVED2 All bits read 0 and are not writable. 2.3.2.13 RESERVED3 This register is reserved for factory testing and is not accessible. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 95 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 7 R W Reset 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 2-20. RESERVED3 All bits read 0 and are not writable. 2.3.2.14 RESERVED4 This register is reserved for factory testing and is not accessible. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 2-21. RESERVED4 All bits read 0 and are not writable. 2.3.2.15 RESERVED5 This register is reserved for factory testing and is not accessible. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 2-22. RESERVED5 All bits read 0 and are not writable. 2.4 2.4.1 Functional Description Flash Command Operations Write and read operations are both used for the program, erase, erase verify, and data compress algorithms described in this subsection. The program and erase algorithms are time controlled by a state machine whose timebase, FCLK, is derived from the oscillator clock via a programmable divider. The command MC9S12KG128 Data Sheet, Rev. 1.15 96 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) register as well as the associated address and data registers operate as a buffer and a register (2-stage FIFO) so that a second command along with the necessary data and address can be stored to the buffer while the first command remains in progress. This pipelined operation allows a time optimization when programming more than one word on a specific row in the Flash block as the high voltage generation can be kept active in between two programming commands. The pipelined operation also allows a simplification of command launching. Buffer empty as well as command completion are signalled by flags in the Flash status register with interrupts generated, if enabled. The next paragraphs describe: 1. How to write the FCLKDIV register. 2. Command write sequences used to program, erase, and verify the Flash memory. 3. Valid Flash commands. 4. Effects resulting from illegal Flash command write sequences or aborting Flash operations. 2.4.1.1 Writing the FCLKDIV Register Prior to issuing any program, erase, erase verify, or data compress command, it is first necessary to write the FCLKDIV register to divide the oscillator clock down to within the 150 kHz to 200 kHz range. Because the program and erase timings are also a function of the bus clock, the FCLKDIV determination must take this information into account. If we define: • FCLK as the clock of the Flash timing control block, • Tbus as the period of the bus clock, and • INT(x) as taking the integer part of x (e.g. INT(4.323)=4). Then, FCLKDIV register bits PRDIV8 and FDIV[5:0] are to be set as described in Figure 2-23. For example, if the oscillator clock frequency is 950 kHz and the bus clock frequency is 10 MHz, FCLKDIV bits FDIV[5:0] must be set to 4 (000100) and bit PRDIV8 set to 0. The resulting FCLK frequency is then 190 kHz. As a result, the Flash program and erase algorithm timings are increased over the optimum target by: ( 200 – 190 ) ⁄ 200 × 100 = 5% CAUTION Program and erase command execution time will increase proportionally with the period of FCLK. Because of the impact of clock synchronization on the accuracy of the functional timings, programming or erasing the Flash memory cannot be performed if the bus clock runs at less than 1 MHz. Programming or erasing the Flash memory with FCLK < 150 kHz must be avoided. Setting FCLKDIV to a value such that FCLK < 150 kHz can destroy the Flash memory due to overstress. Setting FCLKDIV to a value such that (1/FCLK + Tbus) < 5µs can result in incomplete programming or erasure of the Flash memory cells. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 97 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) If the FCLKDIV register is written, the FDIVLD bit is set automatically. If the FDIVLD bit is 0, the FCLKDIV register has not been written since the last reset. Flash commands will not be executed if the FCLKDIV register has not been written to. MC9S12KG128 Data Sheet, Rev. 1.15 98 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) START Tbus < 1µs? YES PRDIV8=0 (reset) NO ALL COMMANDS IMPOSSIBLE OSCILLATOR CLOCK > 12.8 MHZ? YES PRDIV8=1 PRDCLK=oscillator_clock/8 NO PRDCLK=oscillator_clock PRDCLK[MHz]*(5+Tbus[µs]) an integer? YES NO FDIV[5:0]=INT(PRDCLK[MHz]*(5+Tbus[µs])) FDIV[5:0]=PRDCLK[MHz]*(5+Tbus[µs])-1 TRY TO DECREASE Tbus FCLK=(PRDCLK)/(1+FDIV[5:0]) 1/FCLK[MHz] + Tbus[µs] > 5 AND FCLK > 0.15 MHz ? NO YES END YES FDIV[5:0] > 4? NO ALL COMMANDS IMPOSSIBLE Figure 2-23. Determination Procedure for PRDIV8 and FDIV Bits MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 99 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.2 Command Write Sequence The Flash command controller is used to supervise the command write sequence to execute program, erase, erase verify, and data compress algorithms. Before starting a command write sequence, the ACCERR and PVIOL flags in the FSTAT register must be clear (see Section 2.3.2.7, “Flash Status Register (FSTAT)”) and the CBEIF flag must be tested to determine the state of the address, data, and command buffers. If the CBEIF flag is set, indicating the buffers are empty, a new command write sequence can be started. If the CBEIF flag is clear, indicating the buffers are not available, a new command write sequence will overwrite the contents of the address, data, and command buffers. A command write sequence consists of three steps which must be strictly adhered to with writes to the Flash module not permitted between the steps. However, Flash register and array reads are allowed during a command write sequence. A command write sequence consists of the following steps: 1. Write an aligned data word to a valid Flash array address. The address and data will be stored in the address and data buffers, respectively. If the CBEIF flag is clear when the Flash array write occurs, the contents of the address and data buffers will be overwritten and the CBEIF flag will be set. 2. Write a valid command to the FCMD register. a) For the erase verify command (see Section 2.4.1.3.1, “Erase Verify Command”), the contents of the data buffer are ignored and all address bits in the address buffer are ignored. b) For the data compress command (see Section 2.4.1.3.2, “Data Compress Command”), the contents of the data buffer represents the number of consecutive words to read for data compression and the contents of the address buffer represents the starting address. c) For the program command (see Section 2.4.1.3.3, “Program Command”), the contents of the data buffer will be programmed to the address specified in the address buffer with all address bits valid. d) For the sector erase command (see Section 2.4.1.3.4, “Sector Erase Command”), the contents of the data buffer are ignored and address bits [9:0] contained in the address buffer are ignored. e) For the mass erase command (see Section 2.4.1.3.5, “Mass Erase Command”), the contents of the data buffer and address buffer are ignored. f) For the sector erase abort command (see Section 2.4.1.3.6, “Sector Erase Abort Command”), the contents of the data buffer and address buffer are ignored. 3. Clear the CBEIF flag by writing a 1 to CBEIF to launch the command. When the CBEIF flag is cleared, the CCIF flag is cleared on the same bus cycle by internal hardware indicating that the command was successfully launched. For all command write sequences except data compress and sector erase abort, the CBEIF flag will set four bus cycles after the CCIF flag is cleared indicating that the address, data, and command buffers are ready for a new command write sequence to begin. For data compress and sector erase abort operations, the CBEIF flag will remain clear until the operation completes. A command write sequence can be aborted prior to clearing the CBEIF flag by writing a 0 to the CBEIF flag and will result in the ACCERR flag being set. MC9S12KG128 Data Sheet, Rev. 1.15 100 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Except for the sector erase abort command, a buffered command will wait for the active operation to be completed before being launched. The sector erase abort command is launched when the CBEIF flag is cleared as part of a sector erase abort command write sequence. After a command is launched, the completion of the command operation is indicated by the setting of the CCIF flag. The CCIF flag only sets when all active and buffered commands have been completed. 2.4.1.3 Valid Flash Commands Table 2-19 summarizes the valid Flash commands along with the effects of the commands on the Flash block. Table 2-19. Valid Flash Command Description FCMDB 0x05 0x06 0x20 0x40 0x41 NVM Command Erase Verify Function on Flash Memory Verify all memory bytes in the Flash block are erased. If the Flash block is erased, the BLANK flag in the FSTAT register will set upon command completion. Data Compress data from a selected portion of the Flash block. The resulting signature is stored in Compress the FDATA register. Program Sector Erase Mass Erase Sector Erase Abort Program a word (two bytes) in the Flash block. Erase all memory bytes in a sector of the Flash block. Erase all memory bytes in the Flash block. A mass erase of the full Flash block is only possible when FPLDIS, FPHDIS, and FPOPEN bits in the FPROT register are set prior to launching the command. Abort the sector erase operation. The sector erase operation will terminate according to a set procedure. The Flash sector must not be considered erased if the ACCERR flag is set upon command completion. 0x47 CAUTION A Flash word must be in the erased state before being programmed. Cumulative programming of bits within a Flash word is not allowed and will result in invalid data stored. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 101 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.3.1 Erase Verify Command The erase verify operation is used to confirm that a Flash block is erased. After launching the erase verify command, the CCIF flag in the FSTAT register will set after the operation has completed unless a second command has been buffered. The number of bus cycles required to execute the erase verify operation is equal to the number of addresses in the Flash block plus 12 bus cycles as measured from the time the CBEIF flag is cleared until the CCIF flag is set. The result of the erase verify operation is reflected in the state of the BLANK flag in the FSTAT register. If the BLANK flag is set in the FSTAT register, the Flash memory is erased. If the ECC logic detects a double bit fault during the erase verify operation, the operation will terminate immediately and set the DFDIF and ACCERR flags in the FSTAT register. The faulty address will be stored in the FADDR registers and the ECC parity bits read at the faulty address will be stored in the FDATALO register. The CCIF flag will set after the DFDIF flag is set and the faulty information is stored in the FADDR and FDATALO registers. MC9S12KG128 Data Sheet, Rev. 1.15 102 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Read: Register FCLKDIV Clock Register Loaded Check Bit FDIVLD set? yes no Write: Register FCLKDIV 1. Write: Flash Block Address and Dummy Data Write: Register FCMD Erase Verify Command 0x05 Write: Register FSTAT Clear bit CBEIF 0x80 Read: Register FSTAT NOTE: command write sequence aborted by writing 0x00 to FSTAT register. NOTE: command write sequence aborted by writing 0x00 to FSTAT register. 2. 3. Write: Register FSTAT Clear bit ACCERR 0x10 no Access Error Check Bit ACCERR Set? no yes Bit DFDIF Set? yes Bit Polling for Command Completion Check Bit CCIF Set? yes no Read: Register FSTAT Double Bit Fault Detection Check Bit DFDIF Set? no yes Write: Register FSTAT Clear bit DFDIF 0x08 Mass Erase Flash Block Blank Status Check Bit BLANK Set? yes no Flash Block not erased EXIT Figure 2-24. Example Erase Verify Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 103 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.3.2 Data Compress Command The data compress command is used to check Flash code integrity by compressing data from a selected portion of the Flash block into a signature analyzer. The starting address for the data compress operation is defined by the address written during the command write sequence. The number of consecutive word addresses compressed is defined by the data written during the command write sequence. If the data value written is 0x0000, 64K addresses or 128 Kbytes will be compressed. After launching the data compress command, the CCIF flag in the FSTAT register will set after the data compress operation has completed. The number of bus cycles required to execute the data compress operation is equal to two times the number of addresses read plus 20 bus cycles as measured from the time the CBEIF flag is cleared until the CCIF flag is set. After the CCIF flag is set, the signature generated by the data compress operation is available in the FDATA register. The signature in the FDATA register can be compared to the expected signature to determine the integrity of the selected data stored in the Flash block. If the last address of the Flash block is reached during the data compress operation, data compression will continue with the starting address of the Flash block. NOTE Since the FDATA register (or data buffer) is written to as part of the data compress operation, a command write sequence is not allowed to be buffered behind a data compress command write sequence. The CBEIF flag will not set after launching the data compress command to indicate that a command must not be buffered behind it. If an attempt is made to start a new command write sequence with a data compress operation active, the ACCERR flag in the FSTAT register will be set. A new command write sequence must only be started after reading the signature stored in the FDATA register. A Flash array read that generates a double bit fault will overwrite the contents of the FDATA register. In order to take corrective action, it is recommended that the data compress command be executed on a Flash sector or subset of a Flash sector. If the data compress operation on a Flash sector returns an invalid signature, the Flash sector must be erased using the sector erase command and then reprogrammed using the program command. The data compress command can be used to verify that a sector or sequential set of sectors are erased. If the ECC logic detects a double bit fault during the data compress operation, the operation will terminate immediately and set the DFDIF and ACCERR flags in the FSTAT register. The faulty address will be stored in the FADDR registers and the ECC parity bits read at the faulty address will be stored in the FDATALO register. The CCIF flag will set after the DFDIF flag is set and the faulty information is stored in the FADDR and FDATALO registers. MC9S12KG128 Data Sheet, Rev. 1.15 104 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Read: Register FCLKDIV Clock Register Loaded Check Bit FDIVLD set? yes no Write: Register FCLKDIV 1. Write: Flash address to start compression and number of word addresses to compress NOTE: command write sequence Write: Register FCMD aborted by writing 0x00 to Data Compress Command 0x06 FSTAT register. Write: Register FSTAT Clear bit CBEIF 0x80 Read: Register FSTAT NOTE: command write sequence aborted by writing 0x00 to FSTAT register. 2. 3. Write: Register FSTAT Clear bit ACCERR 0x10 no Access Error Check Bit ACCERR Set? no yes Bit DFDIF Set? yes Bit Polling for Command Completion Check Bit CCIF Set? yes no Read: Register FSTAT Double Bit Fault Detection Check Bit DFDIF Set? no yes Write: Register FSTAT Clear bit DFDIF 0x08 Read: Register FDATA Data Compress Signature Signature Compared to Known Value Signature Valid? yes EXIT no Erase and Reprogram Flash Region Compressed Figure 2-25. Example Data Compress Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 105 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.3.3 Program Command The program command is used to program a previously erased word in the Flash memory using an embedded algorithm. If the word to be programmed is in a protected area of the Flash block, the PVIOL flag in the FSTAT register will set and the program command will not launch. After the program command has successfully launched, the CCIF flag in the FSTAT register will set after the program operation has completed unless a second command has been buffered. A summary of the launching of a program operation is shown in Figure 2-26. Read: Register FCLKDIV Clock Register Loaded Check Bit FDIVLD set? yes no Write: Register FCLKDIV 1. Write: Flash Address and Program Data Write: Register FCMD Program Command 0x20 Write: Register FSTAT Clear bit CBEIF 0x80 Read: Register FSTAT Bit PVIOL Set? no yes NOTE: command write sequence aborted by writing 0x00 to FSTAT register. NOTE: command write sequence aborted by writing 0x00 to FSTAT register. 2. 3. Protection Violation Check Write: Register FSTAT Clear bit PVIOL 0x20 Access Error Check Bit ACCERR Set? no yes Write: Register FSTAT Clear bit ACCERR 0x10 yes Address, Data, Command Buffer Empty Check Bit CBEIF Set? no yes Next Write? no Bit Polling for Command Completion Check Bit CCIF Set? yes EXIT no Read: Register FSTAT Figure 2-26. Example Program Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 106 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.3.4 Sector Erase Command The sector erase command is used to erase the addressed sector in the Flash memory using an embedded algorithm. If the Flash sector to be erased is in a protected area of the Flash block, the PVIOL flag in the FSTAT register will set and the sector erase command will not launch. After the sector erase command has successfully launched, the CCIF flag in the FSTAT register will set after the sector erase operation has completed unless a second command has been buffered. Read: Register FCLKDIV Clock Register Loaded Check Bit FDIVLD set? yes no Write: Register FCLKDIV 1. Write: Flash Sector Address and Dummy Data Write: Register FCMD Sector Erase Command 0x40 Write: Register FSTAT Clear bit CBEIF 0x80 Read: Register FSTAT Bit PVIOL Set? no yes NOTE: command write sequence aborted by writing 0x00 to FSTAT register. NOTE: command write sequence aborted by writing 0x00 to FSTAT register. 2. 3. Protection Violation Check Write: Register FSTAT Clear bit PVIOL 0x20 Access Error Check Bit ACCERR Set? no yes Write: Register FSTAT Clear bit ACCERR 0x10 yes Address, Data, Command Buffer Empty Check Bit CBEIF Set? no yes Next Write? no Bit Polling for Command Completion Check Bit CCIF Set? yes EXIT no Read: Register FSTAT Figure 2-27. Example Sector Erase Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 107 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.3.5 Mass Erase Command The mass erase command is used to erase a Flash memory block using an embedded algorithm. If the Flash block to be erased contains any protected area, the PVIOL flag in the FSTAT register will set and the mass erase command will not launch. After the mass erase command has successfully launched, the CCIF flag in the FSTAT register will set after the mass erase operation has completed unless a second command has been buffered. Read: Register FCLKDIV Clock Register Loaded Check Bit FDIVLD set? yes no Write: Register FCLKDIV 1. Write: Flash Block Address and Dummy Data Write: Register FCMD Mass Erase Command 0x41 Write: Register FSTAT Clear bit CBEIF 0x80 Read: Register FSTAT Bit PVIOL Set? no Bit ACCERR Set? no yes yes NOTE: command write sequence aborted by writing 0x00 to FSTAT register. NOTE: command write sequence aborted by writing 0x00 to FSTAT register. 2. 3. Protection Violation Check Write: Register FSTAT Clear bit PVIOL 0x20 Access Error Check Write: Register FSTAT Clear bit ACCERR 0x10 yes Address, Data, Command Buffer Empty Check Bit CBEIF Set? no yes Next Write? no Bit Polling for Command Completion Check Bit CCIF Set? yes EXIT no Read: Register FSTAT Figure 2-28. Example Mass Erase Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 108 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.3.6 Sector Erase Abort Command The sector erase abort command is used to terminate the sector erase operation so that other sectors in the Flash block are available for read and program operations without waiting for the sector erase operation to complete. If the sector erase abort command is launched resulting in the early termination of an active sector erase operation, the ACCERR flag will set after the operation completes as indicated by the CCIF flag being set. The ACCERR flag sets to inform the user that the sector may not be fully erased and a new sector erase command must be launched before programming any location in that specific sector. If the sector erase abort command is launched but the active sector erase operation completes normally, the ACCERR flag will not set upon completion of the operation as indicated by the CCIF flag being set. Therefore, if the ACCERR flag is not set after the sector erase abort command has completed, the sector being erased when the abort command was launched is fully erased. The maximum number of cycles required to abort a sector erase operation is equal to four FCLK periods (see Section 2.4.1.1, “Writing the FCLKDIV Register”) plus five bus cycles as measured from the time the CBEIF flag is cleared until the CCIF flag is set. NOTE Since the ACCERR bit in the FSTAT register may be set at the completion of the sector erase abort operation, a command write sequence is not allowed to be buffered behind a sector erase abort command write sequence. The CBEIF flag will not set after launching the sector erase abort command to indicate that a command must not be buffered behind it. If an attempt is made to start a new command write sequence with a sector erase abort operation active, the ACCERR flag in the FSTAT register will be set. A new command write sequence may be started after clearing the ACCERR flag, if set. NOTE The sector erase abort command must be used sparingly because a sector erase operation that is aborted counts as a complete program/erase cycle. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 109 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Execute Sector Erase Command Flow Bit Polling for Command Completion Check Bit CCIF Set? yes EXIT 1. no Erase Abort Needed? yes no Read: Register FSTAT Write: Dummy Flash Address and Dummy Data Write: Register FCMD Sector Erase Abort Cmd 0x47 Write: Register FSTAT Clear bit CBEIF 0x80 Read: Register FSTAT NOTE: command write sequence aborted by writing 0x00 to 2. FSTAT register. NOTE: command write sequence aborted by writing 0x00 to 3. FSTAT register. Bit Polling for Command Completion Check Bit CCIF Set? yes no Read: Register FSTAT Access Error Check Bit ACCERR Set? no yes Write: Register FSTAT Clear bit ACCERR 0x10 EXIT Sector Erase Completed EXIT Sector Erase Aborted Figure 2-29. Example Sector Erase Abort Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 110 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2.4.1.4 Illegal Flash Operations The ACCERR flag will be set during the command write sequence if any of the following illegal steps are performed, causing the command write sequence to immediately abort: 1. Writing to a Flash address before initializing the FCLKDIV register. 2. Writing a byte or misaligned word to a valid Flash address. 3. Starting a command write sequence while a data compress operation is active. 4. Starting a command write sequence while a sector erase abort operation is active. 5. Writing a second word to a Flash address in the same command write sequence. 6. Writing to any Flash register other than FCMD after writing a word to a Flash address. 7. Writing a second command to the FCMD register in the same command write sequence. 8. Writing an invalid command to the FCMD register. 9. When security is enabled, writing a command other than mass erase to the FCMD register when the write originates from a non-secure memory location or from the Background Debug Mode. 10. Writing to any Flash register other than FSTAT (to clear CBEIF) after writing to the FCMD register. 11. Writing a 0 to the CBEIF flag in the FSTAT register to abort a command write sequence. The ACCERR flag will not be set if any Flash register is read during a valid command write sequence. The ACCERR flag will also be set if any of the following events occur: 1. Launching the sector erase abort command while a sector erase operation is active which results in the early termination of the sector erase operation (see Section 2.4.1.3.6, “Sector Erase Abort Command”) 2. A double bit fault is detected in any of the following Flash operations: a) Array read b) Erase Verify c) Data Compress d) Reset Sequence Array Read (Configuration Field) 3. The MCU enters stop mode and a program or erase operation is in progress. The operation is aborted immediately and any pending command is purged (see Section 2.5.2, “Stop Mode”). If the Flash memory is read during execution of an algorithm (i.e., CCIF flag in the FSTAT register is low), the read operation will return invalid data and the ACCERR flag will not be set. If the ACCERR flag is set in the FSTAT register, the user must clear the ACCERR flag before starting another command write sequence (see Section 2.3.2.7, “Flash Status Register (FSTAT)”). The PVIOL flag will be set after the command is written to the FCMD register during a command write sequence if any of the following illegal operations are attempted, causing the command write sequence to immediately abort: 1. Writing the program command if the address written in the command write sequence was in a protected area of the Flash memory. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 111 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) 2. Writing the sector erase command if the address written in the command write sequence was in a protected area of the Flash memory. 3. Writing the mass erase command while any Flash protection is enabled. If the PVIOL flag is set in the FSTAT register, the user must clear the PVIOL flag before starting another command write sequence (see Section 2.3.2.7, “Flash Status Register (FSTAT)”). 2.5 2.5.1 Operating Modes Wait Mode If a command is active (CCIF = 0) when the MCU enters wait mode, the active command and any buffered command will be completed. The Flash module can recover the MCU from wait mode if the CBEIF and CCIF interrupts are enabled (Section 2.8, “Interrupts”). 2.5.2 Stop Mode If a command is active (CCIF = 0) when the MCU enters stop mode, the operation will be aborted and, if the operation is program or erase, the Flash array data being programmed or erased may be corrupted and the CCIF and ACCERR flags will be set. If active, the high voltage circuitry to the Flash memory will immediately be switched off when entering stop mode. Upon exit from stop mode, the CBEIF flag is set and any buffered command will not be launched. The ACCERR flag must be cleared before starting a command write sequence (see Section 2.4.1.2, “Command Write Sequence”). NOTE As active commands are immediately aborted when the MCU enters stop mode, it is strongly recommended that the user does not use the STOP instruction during program or erase operations. 2.5.3 Background Debug Mode In background debug mode (BDM), the FPROT register is writable. If the MCU is unsecured, then all Flash commands listed in Table 2-19 can be executed. 2.6 Flash Module Security The Flash module provides the necessary security information to the MCU. After each reset, the Flash module determines the security state of the MCU as defined in Section 2.3.2.2, “Flash Security Register (FSEC)”. The contents of the Flash security byte at 0xFF0F in the Flash configuration field must be changed directly by programming 0xFF0F when the MCU is unsecured and the higher address sector is unprotected. If the MC9S12KG128 Data Sheet, Rev. 1.15 112 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) Flash security byte remains in a secured state, any reset will cause the MCU to initialize to a secure operating mode. 2.6.1 Unsecuring the MCU using Backdoor Key Access The MCU may be unsecured by using the backdoor key access feature which requires knowledge of the contents of the backdoor keys (four 16-bit words programmed at addresses 0xFF00–0xFF07). If the KEYEN[1:0] bits are in the enabled state (see Section 2.3.2.2, “Flash Security Register (FSEC)”) and the KEYACC bit is set, a write to a backdoor key address in the Flash memory triggers a comparison between the written data and the backdoor key data stored in the Flash memory. If all four words of data are written to the correct addresses in the correct order and the data matches the backdoor keys stored in the Flash memory, the MCU will be unsecured. The data must be written to the backdoor keys sequentially starting with 0xFF00–0xFF01 and ending with 0xFF06–0xFF07. 0x0000 and 0xFFFF are not permitted as backdoor keys. While the KEYACC bit is set, reads of the Flash memory will return invalid data. The user code stored in the Flash memory must have a method of receiving the backdoor key from an external stimulus. This external stimulus would typically be through one of the on-chip serial ports. If the KEYEN[1:0] bits are in the enabled state (see Section 2.3.2.2, “Flash Security Register (FSEC)”), the MCU can be unsecured by the backdoor access sequence described below: 1. Set the KEYACC bit in the Flash configuration register (FCNFG). 2. Write the correct four 16-bit words to Flash addresses 0xFF00–0xFF07 sequentially starting with 0xFF00. 3. Clear the KEYACC bit. 4. If all four 16-bit words match the backdoor keys stored in Flash addresses 0xFF00–0xFF07, the MCU is unsecured and the SEC[1:0] bits in the FSEC register are forced to the unsecure state of 1:0. The backdoor key access sequence is monitored by an internal security state machine. An illegal operation during the backdoor key access sequence will cause the security state machine to lock, leaving the MCU in the secured state. A reset of the MCU will cause the security state machine to exit the lock state and allow a new backdoor key access sequence to be attempted. The following operations during the backdoor key access sequence will lock the security state machine: 1. If any of the four 16-bit words does not match the backdoor keys programmed in the Flash array. Double bit faults detected while reading the backdoor keys from the Flash array are ignored. 2. If the four 16-bit words are written in the wrong sequence. 3. If more than four 16-bit words are written. 4. If any of the four 16-bit words written are 0x0000 or 0xFFFF. 5. If the KEYACC bit does not remain set while the four 16-bit words are written. 6. If any two of the four 16-bit words are written on successive MCU clock cycles. After the backdoor keys have been correctly matched, the MCU will be unsecured. After the MCU is unsecured, the Flash security byte can be programmed to the unsecure state, if desired. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 113 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) In the unsecure state, the user has full control of the contents of the backdoor keys by programming addresses 0xFF00–0xFF07 in the Flash configuration field. The security as defined in the Flash security byte (0xFF0F) is not changed by using the backdoor key access sequence to unsecure. The backdoor keys stored in addresses 0xFF00–0xFF07 are unaffected by the backdoor key access sequence. After the next reset of the MCU, the security state of the Flash module is determined by the Flash security byte (0xFF0F). The backdoor key access sequence has no effect on the program and erase protections defined in the Flash protection register. It is not possible to unsecure the MCU in special single-chip mode by using the backdoor key access sequence via the background debug mode (BDM). 2.6.2 Unsecuring the Flash Module in Special Single-Chip Mode using BDM The MCU can be unsecured in special single-chip mode by erasing the Flash module by the following method : • Reset the MCU into special single-chip mode, delay while the erase test is performed by the BDM secure ROM, send BDM commands to disable protection in the Flash module, and execute a mass erase command write sequence to erase the Flash memory. After the CCIF flag sets to indicate that the mass operation has completed, reset the MCU into special single-chip mode. The BDM secure ROM will verify that the Flash memory is erased and will assert the UNSEC bit in the BDM status register. This BDM action will cause the MCU to override the Flash security state and the MCU will be unsecured. All BDM commands will be enabled and the Flash security byte may be programmed to the unsecure state by the following method: • Send BDM commands to execute a word program sequence to program the Flash security byte to the unsecured state and reset the MCU. 2.7 2.7.1 Resets Flash Reset Sequence On each reset, the Flash module executes a reset sequence to hold CPU activity while loading the following registers from the Flash memory according to Table 2-1: • FPROT — Flash Protection Register (see Section 2.3.2.5). If a double bit fault is detected during the read of the protection field as part of the reset sequence, the FPOPEN bit in the FPROT register will be clear and remaining bits will be set leaving the Flash block fully protected from program and erase. • FSEC — Flash Security Register (see Section 2.3.2.2). If a double bit fault is detected during the read of the security field as part of the reset sequence, all bits in the FSEC register will be set leaving the Flash module in a secure state with Backdoor Key Access disabled. MC9S12KG128 Data Sheet, Rev. 1.15 114 Freescale Semiconductor Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) If a double bit fault is detected during array reads as part of the reset sequence, the ACCERR flag will set in the FSTAT register. 2.7.2 Reset While Flash Command Active If a reset occurs while any Flash command is in progress, that command will be immediately aborted. The state of the word being programmed or the sector / block being erased is not guaranteed. 2.8 Interrupts The Flash module can generate an interrupt when all Flash command operations have completed, when the Flash address, data, and command buffers are empty, or when a Flash array read or operation has detected a double bit fault. Table 2-20. Flash Interrupt Sources Interrupt Source Flash Address, Data and Command Buffers empty All Flash commands completed Flash array read or verify operation detected a double bit fault Interrupt Flag CBEIF (FSTAT register) CCIF (FSTAT register) DFDIF (FSTAT register) Local Enable CBEIE (FCNFG register) CCIE (FCNFG register) DFDIE (FCNFG register) Global (CCR) Mask I-Bit I-Bit I-Bit NOTE Vector addresses and their relative interrupt priority are determined at the MCU level. 2.8.1 Description of Flash Interrupt Operation The logic used for generating interrupts is shown in Figure 2-30. The Flash module uses the CBEIF and CCIF flags in combination with the CBIE and CCIE enable bits to generate the Flash command interrupt request. The Flash module uses the DFDIF flag in combination with the DFDIE enable bit to generate the Flash double fault detect interrupt request. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 115 Chapter 2 128 Kbyte ECC Flash Module (FTS128K1ECCV1) CBEIF CBEIE Flash Command Interrupt Request CCIF CCIE DFDIF DFDIE Flash Double Fault Detect Interrupt Request Figure 2-30. Flash Interrupt Implementation For a detailed description of the register bits, refer to Section 2.3.2.4, “Flash Configuration Register (FCNFG)” and Section 2.3.2.7, “Flash Status Register (FSTAT)”. MC9S12KG128 Data Sheet, Rev. 1.15 116 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.1 Introduction This document describes the EETS2K module which is a 2 Kbyte EEPROM (nonvolatile) memory. The EETS2K block uses a small sector Flash memory to emulate EEPROM functionality. It is an array of electrically erasable and programmable, nonvolatile memory. The EEPROM memory is organized as 1024 rows of 2 bytes (1 word). The EEPROM memory’s erase sector size is 2 rows or 2 words (4 bytes). The EEPROM memory may be read as either bytes, aligned words, or misaligned words. Read access time is one bus cycle for byte and aligned word, and two bus cycles for misaligned words. Program and erase functions are controlled by a command driven interface. Both sector erase and mass erase of the entire EEPROM memory are supported. An erased bit reads 1 and a programmed bit reads 0. The high voltage required to program and erase is generated internally by on-chip charge pumps. It is not possible to read from the EEPROM memory while it is being erased or programmed. The EEPROM memory is ideal for data storage for single-supply applications allowing for field reprogramming without requiring external programming voltage sources. CAUTION An EEPROM word must be in the erased state before being programmed. Cumulative programming of bits within a word is not allowed. 3.1.1 Glossary Command Write Sequence — A three-step MCU instruction sequence to program, erase, or erase verify the EEPROM. 3.1.2 • • • • • • • • Features 2 Kbytes of EEPROM memory Minimum erase sector of 4 bytes Automated program and erase algorithms Interrupts on EEPROM command completion and command buffer empty Fast sector erase and word program operation 2-stage command pipeline Flexible protection scheme for protection against accidental program or erase Single power supply program and erase MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 117 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.1.3 Modes of Operation Program and erase operation (please refer to Section 3.4.1 for details). 3.1.4 Block Diagram Figure 3-1 shows a block diagram of the EETS2K module. EETS2K Command Interface Registers EEPROM Array 1024 * 16 Bits row0 row1 Command Pipeline comm2 addr2 data2 comm1 addr1 data1 row1023 Command Complete Interrupt Command Buffer Empty Interrupt Oscillator Clock Clock Divider EECLK Figure 3-1. EETS2K Block Diagram 3.2 External Signal Description The EETS2K module contains no signals that connect off chip. 3.3 Memory Map and Register Definition This section describes the EETS2K memory map and registers. 3.3.1 Module Memory Map Figure 3-2 shows the EETS2K memory map. Location of the EEPROM array in the MCU memory map is defined in the Device Overview chapter and is reflected in the INITEE register contents defined in the INT block description chapter. Shown within the EEPROM array are: a protection/reserved field and user-defined EEPROM protected sectors. The 16-byte protection/reserved field is located in the EEPROM array from address 0x07F0 to 0x07FF. A description of this protection/reserved field is given in Table 3-1. MC9S12KG128 Data Sheet, Rev. 1.15 118 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) Table 3-1. EEPROM Protection/Reserved Field Address Offset 0x07F0 – 0x07FC 0x07FD 0x07FE – 0x07FF Size (Bytes) 13 1 2 Description Reserved EEPROM protection byte Reserved The EEPROM module has hardware interlocks which protect data from accidental corruption. A protected sector is located at the higher address end of the EEPROM array, just below address 0x07FF. The protected sector in the EEPROM array can be sized from 64 bytes to 512 bytes. In addition, the EPOPEN bit in the EPROT register, described in Section 3.3.2.5, “EEPROM Protection Register (EPROT)”, can be set to globally protect the entire EEPROM array. Chip security is defined at the MCU level. (12 BYTES) MODULE BASE + 0x0000 EEPROM Registers MODULE BASE + 0x000B EEPROM BASE + 0x0000 1536 BYTES EEPROM ARRAY 0x0600 0x0640 0x0680 0x06C0 0x0700 0x0740 0x0780 0x07C0 EEPROM BASE + 0x07FF 0x07F0 – 0x07FF, EEPROM Protection/Reserved Field EEPROM Protected High Sectors 64, 128, 192, 256, 320, 384, 448, 512 bytes Figure 3-2. EEPROM Memory Map MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 119 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) The EEPROM module also contains a set of 12 control and status registers located in address space module base + 0x0000 to module base + 0x000B. Table 3-2 gives an overview of all EETS2K registers. Table 3-2. EEPROM Register Map Module Base + 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 1 1 Register Name EEPROM Clock Divider Register (ECLKDIV) RESERVED1 RESERVED21 EEPROM Configuration Register (ECNFG) EEPROM Protection Register (EPROT) EEPROM Status Register (ESTAT) EEPROM Command Register (ECMD) RESERVED31 EEPROM High Address Register (EADDRHI) EEPROM Low Address Register (EADDRLO) EEPROM High Data Register (EDATAHI) EEPROM Low Data Register (EDATALO) Normal Mode Access R/W R R R/W R/W R/W R/W R R/W R/W R/W R/W Intended for factory test purposes only. MC9S12KG128 Data Sheet, Rev. 1.15 120 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.3.2 Register Descriptions Bit 7 R W EDIVLD 6 PRDIV8 0 5 EDIV5 0 4 EDIV4 0 3 EDIV3 0 2 EDIV2 0 1 EDIV1 0 Bit 0 EDIV0 0 Register Name ECLKDIV RESERVED1 R W 0 RESERVED2 R W 0 0 0 0 0 0 0 0 ECNFG R W CBEIE CCIE NV6 0 0 0 0 0 0 EPROT R W EPOPEN NV5 NV4 EPDIS 0 EP2 BLANK EP1 0 EPO 0 ESTAT R W CBEIF 0 CCIF PVIOL ACCERR 0 ECMD R W CMDB6 0 CMDB5 0 0 CMDB2 0 0 CMDB0 0 RESERVED3 R W 0 0 0 0 EADDRHI R W 0 0 0 0 0 0 EABHI EADDRLO R W EABLO EDATAHI R W EDHI EDATALO R W = Unimplemented or Reserved EDLO Figure 3-3. EETS2K Register Summary 3.3.2.1 EEPROM Clock Divider Register (ECLKDIV) The ECLKDIV register is used to control timed events in program and erase algorithms. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 121 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 7 R W Reset 0 EDIVLD 6 PRDIV8 0 5 EDIV5 0 4 EDIV4 0 3 EDIV3 0 2 EDIV2 0 1 EDIV1 0 0 EDIV0 0 = Unimplemented or Reserved Figure 3-4. EEPROM Clock Divider Register (ECLKDIV) All bits in the ECLKDIV register are readable while bits 6-0 are write once and bit 7 is not writable. Table 3-3. ECLKDIV Field Descriptions Field 7 EDIVLD 6 PRDIV8 5:0 EDIV[5:0] Description Clock Divider Loaded 0 Register has not been written. 1 Register has been written to since the last reset. Enable Prescaler by 8 0 The oscillator clock is directly fed into the ECLKDIV divider. 1 The oscillator clock is divided by 8 before feeding into the clock divider. Clock Divider Bits — The combination of PRDIV8 and EDIV[5:0] must divide the oscillator clock down to a frequency of 150 kHz – 200 kHz. The maximum divide ratio is 512. Please refer to Section 3.4.1.1, “Writing the ECLKDIV Register” for more information. 3.3.2.2 RESERVED1 This register is reserved for factory testing and is not accessible to the user. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 3-5. RESERVED1 All bits read 0 and are not writable. 3.3.2.3 RESERVED2 This register is reserved for factory testing and is not accessible to the user. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 3-6. RESERVED2 MC9S12KG128 Data Sheet, Rev. 1.15 122 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) All bits read 0 and are not writable. 3.3.2.4 EEPROM Configuration Register (ECNFG) The ECNFG register enables the EEPROM interrupts. 7 R CBEIE W Reset 0 0 0 0 0 0 0 0 CCIE 6 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 3-7. EEPROM Configuration Register (ECNFG) CBEIE and CCIE bits are readable and writable while bits 5-0 read 0 and are not writable. Table 3-4. ECNFG Field Descriptions Field 7 CBEIE Description Command Buffer Empty Interrupt Enable — The CBEIE bit enables the interrupts in case of an empty command buffer in the EEPROM. 0 Command buffer empty interrupts disabled. 1 An interrupt will be requested whenever the CBEIF flag is set (see Section 3.3.2.6, “EEPROM Status Register (ESTAT)”). Command Complete Interrupt Enable — The CCIE bit enables the interrupts in case of all commands being completed in the EEPROM. 0 Command complete interrupts disabled. 1 An interrupt will be requested whenever the CCIF flag is set (see Section 3.3.2.6, “EEPROM Status Register (ESTAT)”). 6 CCIE 3.3.2.5 EEPROM Protection Register (EPROT) The EPROT register defines which EEPROM sectors are protected against program or erase. 7 R EPOPEN W Reset F F F F F F F F 6 NV6 5 NV5 4 NV4 EPDIS EP2 EP1 EP0 3 2 1 0 = Unimplemented or Reserved Figure 3-8. EEPROM Protection Register (EPROT) The EPROT register is loaded from EEPROM array address 0x07FD during reset, as indicated by the F in Figure 3-8. All bits in the EPROT register are readable. Bits NV[6:4] are not writable. The EPOPEN and EPDIS bits in the EPROT register can only be written to the protected state (i.e., 0). The EP[2:0] bits can be written anytime until bit EPDIS is cleared. If the EPOPEN bit is cleared, then the state of the EPDIS and EP[2:0] bits is irrelevant. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 123 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) To change the EEPROM protection that will be loaded on reset, the upper sector of EEPROM must first be unprotected, then the EEPROM protect byte located at address 0x07FD must be written to. A protected EEPROM sector is disabled by the EPDIS bit while the size of the protected sector is defined by the EP bits in the EPROT register. Trying to alter any of the protected areas will result in a protect violation error and PVIOL flag will be set in the ESTAT register. A mass erase of a whole EEPROM block is only possible when protection is fully disabled by setting the EPOPEN and EPDIS bits. An attempt to mass erase an EEPROM block while protection is enabled will set the PVIOL flag in the ESTAT register. Table 3-5. EPROT Field Descriptions Field 7 EPOPEN Description Opens EEPROM for Program or Erase 0 The whole EEPROM array is protected. In this case, the EPDIS and EP bits within the protection register are ignored. 1 The EEPROM sectors not protected are enabled for program or erase. Nonvolatile Flag Bits — These three bits are available to the user as nonvolatile flags. EEPROM Protection Address Range Disable — The EPDIS bit determines whether there is a protected area in the space of the EEPROM address map. 0 Protection enabled 1 Protection disabled EEPROM Protection Address Size — The EP[2:0] bits determine the size of the protected sector. Refer to Table 3-6. 6:4 NV[6:4] 3 EPDIS 2:0 EP[2:0] Table 3-6. EEPROM Address Range Protection EP[2:0] 000 001 010 011 100 101 110 111 Protected Address Range 0x07C0-0x07FF 0x0780-0x07FF 0x0740-0x07FF 0x0700-0x07FF 0x06C0-0x07FF 0x0680-0x07FF 0x0640-0x07FF 0x0600-0x07FF Protected Size 64 bytes 128 bytes 192 bytes 256 bytes 320 bytes 384 bytes 448 bytes 512 bytes 3.3.2.6 EEPROM Status Register (ESTAT) The ESTAT register defines the EEPROM state machine command status and EEPROM array access, protection and erase verify status. MC9S12KG128 Data Sheet, Rev. 1.15 124 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 7 R CBEIF W Reset 1 6 CCIF 5 PVIOL 4 ACCERR 0 3 0 2 BLANK 1 0 0 0 1 0 0 0 0 0 = Unimplemented or Reserved Figure 3-9. EEPROM Status Register (ESTAT - Normal Mode) 7 R CBEIF W Reset 1 1 0 0 0 0 0 1 6 CCIF PVIOL ACCERR 5 4 3 0 2 BLANK FAIL 1 0 DONE = Unimplemented or Reserved Figure 3-10. EEPROM Status Register (ESTAT - Special Mode) CBEIF, PVIOL, and ACCERR bits are readable and writable, CCIF and BLANK bits are readable but not writable, remaining bits read 0 and are not writable in normal mode. FAIL is readable and writable in special mode. FAIL must be clear when starting a command write sequence. DONE is readable but not writable in special mode. Table 3-7. ESTAT Field Descriptions Field 7 CBEIF Description Command Buffer Empty Interrupt Flag — The CBEIF flag indicates that the address, data, and command buffers are empty so that a new command sequence can be started. The CBEIF flag is cleared by writing a 1 to CBEIF. Writing a 0 to the CBEIF flag has no effect on CBEIF. Writing a 0 to CBEIF after writing an aligned word to the EEPROM address space but before CBEIF is cleared will abort a command sequence and cause the ACCERR flag in the ESTAT register to be set. Writing a 0 to CBEIF outside of a command sequence will not set the ACCERR flag. The CBEIF flag is used together with the CBEIE bit in the ECNFG register to generate an interrupt request. 0 Buffers are full 1 Buffers are ready to accept a new command Command Complete Interrupt Flag — The CCIF flag indicates that there are no more commands pending. The CCIF flag is cleared when CBEIF is cleared and sets automatically upon completion of all active and pending commands. The CCIF flag does not set when an active command completes and a pending command is fetched from the command buffer. Writing to the CCIF flag has no effect. The CCIF flag is used together with the CCIE bit in the ECNFG register to generate an interrupt request. 0 Command in progress 1 All commands are completed Protection Violation — The PVIOL flag indicates an attempt was made to program or erase an address in a protected EEPROM memory area (Section 3.4.1.4, “Illegal EEPROM Operations”). The PVIOL flag is cleared by writing a 1 to PVIOL. Writing a 0 to the PVIOL flag has no effect on PVIOL. While PVIOL is set, it is not possible to launch another command in the EEPROM. 0 No failure 1 A protection violation has occurred 6 CCIF 5 PVIOL MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 125 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) Table 3-7. ESTAT Field Descriptions (continued) Field 4 ACCERR Description EEPROM Access Error — The ACCERR flag indicates an illegal access to the selected EEPROM array (Section 3.4.1.4, “Illegal EEPROM Operations). This can be either a violation of the command sequence, issuing an illegal command (illegal combination of the CMDBx bits in the ECMD register) or the execution of a CPU STOP instruction while a command is executing (CCIF = 0). The ACCERR flag is cleared by writing a 1 to ACCERR. Writing a 0 to the ACCERR flag has no effect on ACCERR. While ACCERR is set, it is not possible to launch another command in the EEPROM. 0 No failure 1 Access error has occurred Array Has Been Verified as Erased — The BLANK flag indicates that an erase verify command has checked the EEPROM array and found it to be erased. The BLANK flag is cleared by hardware when CBEIF is cleared as part of a new valid command sequence. Writing to the BLANK flag has no effect on BLANK. 0 If an erase verify command has been requested and the CCIF flag is set, then a 0 in BLANK indicates array is not erased 1 EEPROM array verifies as erased Flag Indicating a Failed EEPROM Operation — The FAIL flag will set if the erase verify operation fails (EEPROM block verified as not erased). The FAIL flag is cleared writing a 1 to FAIL. Writing a 0 to the FAIL flag has no effect on FAIL. 0 EEPROM operation completed without error 1 EEPROM operation failed Flag Indicating a Completed EEPROM Operation 0 EEPROM operation is active (program, erase, erase verify) 1 EEPROM operation not active 2 BLANK 1 FAIL 0 DONE 3.3.2.7 EEPROM Command Register (ECMD) The ECMD register defines the EEPROM commands. 7 R W Reset 0 0 0 0 0 0 0 0 0 CMDB6 CMDB5 6 5 4 0 3 0 CMDB2 2 1 0 CMDB0 0 = Unimplemented or Reserved Figure 3-11. EEPROM Command Register (ECMD) CMDB6, CMDB5, CMDB2, and CMDB0 bits are readable and writable during a command sequence while bits 7, 4, 3, and 1 read 0 and are not writable. Table 3-8. ECMD Field Descriptions Field 6, 5, 2, 0 CMDB[6:5] CMDB2 CMDB0 Description EEPROM Command — Valid EEPROM commands are shown in Table 3-9. Any other command written than those mentioned in Table 3-9 sets the ACCERR bit in the ESTAT register. MC9S12KG128 Data Sheet, Rev. 1.15 126 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) Table 3-9. Valid EEPROM Command List Command 0x05 0x20 0x40 0x41 0x60 Meaning Erase verify Word program Sector erase Mass erase Sector modify 3.3.2.8 RESERVED3 This register is reserved for factory testing and is not accessible to the user. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0 = Unimplemented or Reserved Figure 3-12. RESERVED3 All bits read 0 and are not writable. 3.3.2.9 EEPROM Address Register (EADDR) EADDRHI and EADDRLO are the EEPROM address registers. 7 R W Reset 0 0 0 0 0 0 0 0 0 6 0 5 0 4 0 3 0 2 0 EABHI 1 0 = Unimplemented or Reserved Figure 3-13. EEPROM Address High Register (EADDRHI) 7 R EABLO W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 1 0 Figure 3-14. EEPROM Address Low Register (EADDRLO) In normal modes, all EADDRHI and EADDRLO bits read 0 and are not writable. In special modes, all EADDRHI and EADDRLO bits are readable and writable except EADDRHI[7:2] which are not writable and always read 0. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 127 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) For sector erase, the MCU address bits AB[1:0] are ignored. For mass erase, any address within the block is valid to start the command. MC9S12KG128 Data Sheet, Rev. 1.15 128 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.3.2.10 EEPROM Data Register (EDATA) EDATAHI and EDATALO are the EEPROM data registers. 7 R EDHI W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 1 0 Figure 3-15. EEPROM Data High Register (EDATAHI) 7 R EDLO W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 1 0 Figure 3-16. EEPROM Data Low Register (EDATALO) In normal modes, all EDATAHI and EDATALO bits read 0 and are not writable. In special modes, all EDATAHI and EDATALO bits are readable and writable. 3.4 3.4.1 Functional Description Program and Erase Operation Write and read operations are both used for the program and erase algorithms described in this subsection. These algorithms are controlled by a state machine whose timebase, EECLK, is derived from the oscillator clock via a programmable divider. The command register as well as the associated address and data registers operate as a buffer and a register (2-stage FIFO) so that a new command along with the necessary data and address can be stored to the buffer while the previous command is remains in progress. The pipelined operation allows a simplification of command launching. Buffer empty as well as command completion are signalled by flags in the EEPROM status register. Interrupts for the EEPROM will be generated if enabled. The next four subsections describe: • How to write the ECLKDIV register. • Command write sequences used to program, erase, and verify the EEPROM memory. • Valid EEPROM commands. • Errors resulting from illegal EEPROM operations. 3.4.1.1 Writing the ECLKDIV Register Prior to issuing any program or erase command, it is first necessary to write the ECLKDIV register to divide the oscillator down to within 150 kHz to 200 kHz range. The program and erase timings are also a MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 129 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) function of the bus clock, such that the ECLKDIV determination must take this information into account. If we define: • EECLK as the clock of the EEPROM timing control block • Tbus as the period of the bus clock • INT(x) as taking the integer part of x (e.g., INT(4.323)=4), then ECLKDIV register bits PRDIV8 and EDIV[5:0] are to be set as described in Figure 3-17. For example, if the oscillator clock is 950 kHz and the bus clock is 10 MHz, ECLKDIV bits EDIV[5:0] must be set to 4 (binary 000100) and bit PRDIV8 set to 0. The resulting EECLK is then 190 kHz. As a result, the EEPROM algorithm timings are increased over optimum target by: ( 200 – 190 ) ⁄ 200 × 100 = 5% Command execution time will increase proportionally with the period of EECLK. CAUTION Because of the impact of clock synchronization on the accuracy of the functional timings, programming or erasing the EEPROM cannot be performed if the bus clock runs at less than 1 MHz. Programming the EEPROM with an oscillator clock < 150 kHz must be avoided. Setting ECLKDIV to a value such that EECLK < 150 kHz can reduce the lifetime of the EEPROM due to overstress. Setting ECLKDIV to a value such that (1/EECLK+Tbus) < 5µs can result in incomplete programming or erasure of the memory array cells. If the ECLKDIV register is written, the bit EDIVLD is set automatically. If this bit is 0, the register has not been written since the last reset. EEPROM commands will not be executed if this register has not been written to. MC9S12KG128 Data Sheet, Rev. 1.15 130 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) START Tbus ≤ 1 µs? NO PROGRAM/ERASE IMPOSSIBLE yes PRDIV8 = 0 (reset) OSCILLATOR CLOCK > 12.8 MHz? yes PRDIV8 = 1 PRDCLK = oscillator clock/8 NO PRDCLK = oscillator clock PRDCLK[MHz]*(5+Tbus[µs]) an integer? YES NO EDIV[5:0] = INT(PRDCLK[MHz]*(5+Tbus[µs])) EDIV[5:0] = PRDCLK[MHz]*(5+Tbus[µs])-1 TRY TO DECREASE Tbus EECLK = (PRDCLK)/(1+EDIV[5:0]) 1/EECLK [MHz] + Tbus[ms] ≥5 AND EECLK > 0.15 MHz ? NO YES END YES EDIV[5:0] ≥ 4? NO PROGRAM/ERASE IMPOSSIBLE Figure 3-17. PRDIV8 and EDIV Bits Determination Procedure MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 131 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.4.1.2 Command Write Sequence The EEPROM command controller is used to supervise the command write sequence to execute program, erase, mass erase, sector modify, and erase verify operations. Before starting a command write sequence, it is necessary to check that there is no pending access error or protection violation (the ACCERR and PVIOL flags must be cleared in the ESTAT register). After this initial step, the CBEIF flag must be tested to ensure that the address, data and command buffers are empty. If so, the command sequence can be started. The following 3-step command write sequence must be strictly adhered to and no intermediate access to the EEPROM array is permitted between the 3 steps. It is possible to read any EEPROM register during a command sequence. The command write sequence is as follows: 1. Write an aligned word to be to a valid EEPROM array address. The address and data will be stored in internal buffers. — For program and sector modify, all address and data bits are valid. — For erase, the value of the data bytes are ignored. — For mass erase and erase verify, the address can be anywhere in the available address space of the array. — For sector erase, the address bits[1:0] are ignored. 2. Write a valid command, listed in Table 3-10, to the ECMD register. 3. Clear the CBEIF flag by writing a 1 to CBEIF to launch the command. When the CBEIF flag is cleared, the CCIF flag is cleared by hardware indicating that the command was successfully launched. The CBEIF flag will be set again indicating the address, data, and command buffers are ready for a new command write sequence to begin. The completion of the command is indicated by the CCIF flag setting. The CCIF flag only sets when all active and pending commands have been completed. The EEPROM command controller will flag errors in command write sequences by means of the ACCERR (access error) and PVIOL (protection violation) flags in the ESTAT register. An erroneous command write sequence will abort and set the appropriate flag. If set, the user must clear the ACCERR or PVIOL flags before commencing another command write sequence. By writing a 0 to the CBEIF flag the command sequence can be aborted after the word write to the EEPROM address space or after writing a command to the ECMD register and before the command is launched. Writing a 0 to the CBEIF flag in this way will set the ACCERR flag. A summary of the launching of a program operation is shown in Figure 3-18. For other operations, the user writes the appropriate command to the ECMD register. MC9S12KG128 Data Sheet, Rev. 1.15 132 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) Read: Register ECLKDIV Clock Register Written Check Bit EDIVLD set? yes no Write: Register ECLKDIV 1. Write: Array Address and Program Data Write: Register ECMD Program Command 0x20 Write: Register ESTAT Clear bit CBEIF 0x80 Read: Register ESTAT Bit PVIOL Set? no NOTE: command sequence aborted by writing 0x00 to ESTAT register. NOTE: command sequence aborted by writing 0x00 to ESTAT register. 2. 3. Protection Violation Check yes Write: Register ESTAT Clear bit PVIOL 0x20 Access Error Check Bit ACCERR Set? no yes Write: Register ESTAT Clear bit ACCERR 0x10 yes yes Next Write? no Address, Data, Command Buffer Empty Check Bit CBEIF Set? no Bit Polling for Command Completion Check Bit CCIF Set? yes EXIT no Read: Register ESTAT Figure 3-18. Example Program Command Flow MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 133 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.4.1.3 Valid EEPROM Commands Table 3-10 summarizes the valid EEPROM commands. Also shown are the effects of the commands on the EEPROM array. Table 3-10. Valid EEPROM Commands ECMD 0x05 0x20 0x40 0x41 0x60 Meaning Erase Verify Program Sector Erase Mass Erase Sector Modify Function on EEPROM Array Verify all memory bytes of the EEPROM array are erased. If the array is erased, the BLANK bit will set in the ESTAT register upon command completion. Program a word (two bytes). Erase two words (four bytes) of EEPROM array. Erase all of the EEPROM array. A mass erase of the full array is only possible when EPDIS and EPOPEN are set. Erase two words of EEPROM, re-program one word. CAUTION An EEPROM word must be in an erased state before being programmed. Cumulative programming of bits within a word is not allowed. The sector modify command (0x60) is a two-step command which first erases a sector (2 words) of the EEPROM array and then re-programs one of the words in that sector. The EEPROM sector which is erased by the sector modify command is the sector containing the address of the aligned array write which starts the valid command sequence. That same address is re-programmed with the data which is written. By launching a sector modify command and then pipelining a program command it is possible to completely replace the contents of an EEPROM sector. 3.4.1.4 Illegal EEPROM Operations The ACCERR flag will be set during the command write sequence if any of the following illegal operations are performed causing the command write sequence to immediately abort: 1. Writing to the EEPROM address space before initializing ECLKDIV. 2. Writing a misaligned word or a byte to the valid EEPROM address space. 3. Writing to the EEPROM address space while CBEIF is not set. 4. Writing a second word to the EEPROM address space before executing a program or erase command on the previously written word. 5. Writing to any EEPROM register other than ECMD after writing a word to the EEPROM address space. 6. Writing a second command to the ECMD register before executing the previously written command. 7. Writing an invalid command to the ECMD register in normal mode. 8. Writing to any EEPROM register other than ESTAT (to clear CBEIF) after writing to the command register (ECMD). MC9S12KG128 Data Sheet, Rev. 1.15 134 Freescale Semiconductor Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 9. The part enters stop mode and a program or erase command is in progress. The command is aborted and any pending command is killed. 10. A 0 is written to the CBEIF bit in the ESTAT register. The ACCERR flag will not be set if any EEPROM register is read during the command sequence. If the EEPROM array is read during execution of an algorithm (i.e., CCIF bit in the ESTAT register is low), the read will return non-valid data and the ACCERR flag will not be set. When an ACCERR flag is set in the ESTAT register, the command state machine is locked. It is not possible to launch another command until the ACCERR flag is cleared. The PVIOL flag will be set during the command write sequence after the word write to the EEPROM address space and the command sequence will be aborted if any of the following illegal operations are performed. 1. Writing a EEPROM address to program in a protected area of the EEPROM. 2. Writing a EEPROM address to erase in a protected area of the EEPROM. 3. Writing the mass erase command to ECMD while any protection is enabled. When the PVIOL flag is set in the ESTAT register the command state machine is locked. It is not possible to launch another command until the PVIOL flag is cleared. 3.5 3.5.1 Operating Modes Wait Mode If an EEPROM command is active (CCIF = 0) when the MCU enters wait mode, that command and any pending command will be completed. The EETS2K module can recover the MCU from wait mode if the interrupts are enabled (see Section 3.7, “Interrupts”). 3.5.2 Stop Mode If a command is active (CCIF = 0) when the MCU enters stop mode, the operation will be aborted and if the operation is program, erase, or sector modify, the data being programmed or erased may be corrupted and the CCIF and ACCERR flags will be set. If active, the high voltage circuitry to the EEPROM array will be switched off when entering stop mode. Upon exit from stop mode, the CBEIF flag is set and any pending command will not be launched. The ACCERR flag must be cleared before starting a new command write sequence. NOTE As active commands are immediately aborted when the MCU enters stop mode, it is strongly recommended that the user does not use the STOP instruction during program, erase, or sector modify operations. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 135 Chapter 3 2 Kbyte EEPROM Module (EETS2KV1) 3.5.3 Background Debug Mode In background debug mode (BDM), the EPROT register is writable. If the chip is unsecured then all EEPROM commands listed in Table 3-10 can be executed. If the chip is secured in special single-chip mode, then the only possible command to execute is mass erase. 3.6 Resets If a reset occurs while any EEPROM command is in progress, that command will be immediately aborted. The state of the word being programmed or the sector / block being erased is not guaranteed. 3.7 Interrupts The EEPROM module can generate an interrupt when all EEPROM commands are completed or the address, data, and command buffers are empty. Table 3-11. EEPROM Interrupt Sources Interrupt Source EEPROM address, data and command buffers empty All commands are completed on EEPROM Interrupt Flag CBEIF (ESTAT register) CCIF (ESTAT register) Local Enable CBEIE CCIE Global (CCR) Mask I Bit I Bit NOTE Vector addresses and their relative interrupt priority are determined at the MCU level. For a detailed description of the register bits, refer to Section 3.3.2.4, “EEPROM Configuration Register (ECNFG)” and Section 3.3.2.6, “EEPROM Status Register (ESTAT)”. MC9S12KG128 Data Sheet, Rev. 1.15 136 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.1 Introduction The Port Integration Module (PIM) establishes the interface between the peripheral modules and the I/O pins for ports H, J, M, P, S and T. This section covers: • Port H associated with the two SPI modules — SPI1 and SPI2. These ports can also be used as external interrupt sources. • Port J associated with 1 IIC module and the CAN4 module, which can also be used as an external interrupt source • Port M associated with 2 CAN modules — CAN0 and CAN4, the SPI module associated with port S • Port P connected to either the PWM or the two SPI modules associated with Port H, which also can be used as an external interrupt source • Port S associated with 2 SCI and 1 SPI module • Port T connected to TIM module Each I/O pin can be configured by several registers in order to select data direction and drive strength, to enable and select pull-up or pull-down resistors. On certain pins also interrupts can be enabled which result in status flags. The I/O’s of 2 CAN and all 3 SPI modules can be routed from their default location to determined pins. 4.1.1 Features A standard port has the following minimum features: • Input/output selection • 3.3V/5V output drive with two selectable drive strength • 3.3V/5V digital and analog input • Input with selectable pull-up or pull-down device Optional features: • Open drain for wired-OR connections • Interrupt inputs with glitch filtering MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 137 Chapter 4 Port Integration Module (PIM9KG128V1) 4.1.2 Block Diagram Figure 4-1 is a block diagram of the PIM9KG128. IP-Bus INTH INTP INTJ Port Integration Module PS0 PS1 PS2 PS3 PS4 PS5 PS6 PS7 PM0 PM1 PM2 PM3 PM4 PM5 PM6 PM7 PJ0 PJ1 RXD TXDSCI0 RXD TXDSCI1 SDI/MISO SDO/MOSI SCK SS SPI0 RxCAN TxCAN RxCAN TxCAN IOC0 IOC1 IOC2 IOC3 IOC4 IOC5 IOC6 IOC7 KWP0 KWP1 KWP2 KWP3 KWP4 KWP5 KWP6 KWP7 KWH0 KWH1 KWH2 KWH3 KWH4 KWH5 KWH6 KWH7 PT0 PT1 PT2 PT3 PT4 PT5 PT6 PT7 PP0 PP1 PP2 PP3 PP4 PP5 PP6 PP7 PH0 PH1 PH2 PH3 PH4 PH5 PH6 PH7 CAN4 KWJ0 KWJ1 PJ6 PJ7 KWW6 KWW7 SDA SCL IIC SDI/MISO SDO/MOSI SCK SPI1 SS SDI/MISO SDO/MOSI SCK SPI2 SS Figure 4-1. PIM9KG128 Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 138 Freescale Semiconductor Port H Port P CAN0 PWM PW0 PW1 PW2 PW3 PW4 PW5 PW6 PW7 Port T TIM Port S Module to Port Routing Port M Port J Chapter 4 Port Integration Module (PIM9KG128V1) 4.2 External Signal Description This section lists and describes the signals that do connect off chip. 4.2.1 Signal Properties Table 4-1 shows all the pins and their functions that are controlled by the PIM9KG128. If there is more than one function associated with a pin, the priority is indicated by the position in the table from top (highest priority) to down (lowest priority). All pins have reset state as input. Table 4-1. Pin Functions and Priorities (Sheet 1 of 4) Port Port T Port S Pin Name PT[7:0] PS7 Pin Function and Priority IOC[7:0] GPIO SS0 GPIO PS6 PS5 PS4 PS3 PS2 PS1 PS0 SCK0 GPIO MOSI0 GPIO MISO0 GPIO TXD1 GPIO RXD1 GPIO TXD0 GPIO RXD0 GPIO Description Timer Channels 7 to 0 General-purpose I/O Serial Peripheral Interface 0 slave select output in master mode, input in slave mode or master mode. General-purpose I/O Serial Peripheral Interface 0 serial clock pin General-purpose I/O Serial Peripheral Interface 0 master out/slave in pin General-purpose I/O Serial Peripheral Interface 0 master in/slave out pin General-purpose I/O Serial Communication Interface 1 transmit pin General-purpose I/O Serial Communication Interface 1 receive pin General-purpose I/O Serial Communication Interface 0 transmit pin General-purpose I/O Serial Communication Interface 0 receive pin General-purpose I/O Pull-up GPIO Pull Mode after Reset Hi-Z Pin Function after Reset GPIO MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 139 Chapter 4 Port Integration Module (PIM9KG128V1) Table 4-1. Pin Functions and Priorities (Sheet 2 of 4) Port Pin Name PM7 PM6 Pin Function and Priority TXCAN4 GPIO RXCAN4 GPIO TXCAN0 PM5 TXCAN4 SCK0 GPIO RXCAN0 PM4 Port M RXCAN4 MOSI0 GPIO TXCAN0 PM3 SS01 GPIO RXCAN0 PM2 MISO0 GPIO PM1 PM0 TXCAN0 GPIO RXCAN0 GPIO 1 Description MSCAN4 transmit pin General-purpose I/O MSCAN4 receive pin General-purpose I/O MSCAN0 transmit pin MSCAN4 transmit pin Serial Peripheral Interface 0 serial clock pin General-purpose I/O MSCAN0 receive pin MSCAN4 receive pin Serial Peripheral Interface 0 master out/slave in pin General-purpose I/O MSCAN0 transmit pin Serial Peripheral Interface 0 slave select output in master mode, input for slave mode or master mode. General-purpose I/O MSCAN0 receive pin Serial Peripheral Interface 0 master in/slave out pin General-purpose I/O MSCAN0 transmit pin General-purpose I/O MSCAN0 receive pin General-purpose I/O Pull Mode after Reset Pin Function after Reset Hi-Z GPIO MC9S12KG128 Data Sheet, Rev. 1.15 140 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) Table 4-1. Pin Functions and Priorities (Sheet 3 of 4) Port Pin Name Pin Function and Priority PWM7 PP7 SCK2 GPIO/KWP7 PWM6 PP6 SS2 GPIO/KWP6 PWM5 PP5 MOSI2 GPIO/KWP5 PWM4 PP4 Port P PP3 MISO2 GPIO/KWP4 PWM3 SS1 GPIO/KWP3 PWM2 PP2 SCK1 GPIO/KWP2 PWM1 PP1 MOSI1 GPIO/KWP1 PWM0 PP0 MISO1 GPIO/KWP0 Description Pulse Width Modulator channel 7 Serial Peripheral Interface 2 serial clock pin General-purpose I/O with interrupt Pulse Width Modulator channel 6 Serial Peripheral Interface 2 slave select output in master mode, input in slave mode or master mode. General-purpose I/O with interrupt Pulse Width Modulator channel 5 Serial Peripheral Interface 2 master out/slave in pin General-purpose I/O with interrupt Pulse Width Modulator channel 4 Serial Peripheral Interface 2 master in/slave out pin General-purpose I/O with interrupt Pulse Width Modulator channel 3 Serial Peripheral Interface 1 slave select output in master mode, input in slave mode or master mode. General-purpose I/O with interrupt Pulse Width Modulator channel 2 Serial Peripheral Interface 1 serial clock pin General-purpose I/O with interrupt Pulse Width Modulator channel 1 Serial Peripheral Interface 1 master out/slave in pin General-purpose I/O with interrupt Pulse Width Modulator channel 0 Serial Peripheral Interface 1 master in/slave out pin General-purpose I/O with interrupt Hi-Z GPIO Pull Mode after Reset Pin Function after Reset MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 141 Chapter 4 Port Integration Module (PIM9KG128V1) Table 4-1. Pin Functions and Priorities (Sheet 4 of 4) Port Pin Name Pin Function and Priority SS2 GPIO/KWH7 PH6 PH5 PH4 Port H PH3 SCK2 GPIO/KWH6 MOSI2 GPIO/KWH5 MISO2 GPIO/KWH4 SS1 GPIO/KWH3 PH2 PH1 PH0 SCK1 GPIO/KWH2 MOSI1 GPIO/KWH1 MISO1 GPIO/KWH0 TXCAN4 PJ7 SCL GPIO/KWJ7 Port J RXCAN4 PJ6 PJ1 PJ0 1 Description Serial Peripheral Interface 2 slave select output in master mode, input in slave mode or master mode. General-purpose I/O with interrupt Serial Peripheral Interface 2 serial clock pin General-purpose I/O with interrupt Serial Peripheral Interface 2 master out/slave in pin General-purpose I/O with interrupt Serial Peripheral Interface 2 master in/slave out pin General-purpose I/O with interrupt Serial Peripheral Interface 1 slave select output in master mode, input in slave mode or master mode. General-purpose I/O with interrupt Serial Peripheral Interface 1 serial clock pin General-purpose I/O with interrupt Serial Peripheral Interface 1 master out/slave in pin General-purpose I/O with interrupt Serial Peripheral Interface 1 master in/slave out pin General-purpose I/O with interrupt MSCAN4 transmit pin Inter Integrated Circuit serial clock line General-purpose I/O with interrupt MSCAN4 receive pin Inter Integrated Circuit serial data line General-purpose I/O with interrupt General-purpose I/O with interrupt General-purpose I/O with interrupt Pull Mode after Reset Pin Function after Reset PH7 Hi-Z GPIO SDA GPIO/KWJ6 GPIO/KWJ1 GPIO/KWJ0 Pull-up GPIO If CAN0 is routed to PM[3:2] the SPI0 can still be used in bidirectional master mode. MC9S12KG128 Data Sheet, Rev. 1.15 142 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3 Memory Map and Register Definition This section provides a detailed description of all registers. Table 4-2 is a standard memory map of PIM9KG128. Table 4-2. PIM9KG128 Memory Map Address Offset 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 - 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F Port T I/O Register (PTT) Port T Input Register (PTIT) Port T Data Direction Register (DDRT) Port T Reduced Drive Register (RDRT) Port T Pull Device Enable Register (PERT) Port T Polarity Select Register (PPST) Reserved Port S I/O Register (PTS) Port S Input Register (PTIS) Port S Data Direction Register (DDRS) Port S Reduced Drive Register (RDRS) Port S Pull Device Enable Register (PERS) Port S Polarity Select Register (PPSS) Port S Wired-OR Mode Register (WOMS) Reserved Port M I/O Register (PTM) Port M Input Register (PTIM) Port M Data Direction Register (DDRM) Port M Reduced Drive Register (RDRM) Port M Pull Device Enable Register (PERM) Port M Polarity Select Register (PPSM) Port M Wired-OR Mode Register (WOMM) Port M Module Routing Register (MODRR) Port P I/O Register (PTP) Port P Input Register (PTIP) Port P Data Direction Register (DDRP) Port P Reduced Drive Register (RDRP) Port P Pull Device Enable Register (PERP) Port P Polarity Select Register (PPSP) Port P Interrupt Enable Register (PIEP) Port P Interrupt Flag Register (PIFP) Use Access R/W R R/W R/W R/W R/W — R/W R R/W R/W R/W R/W R/W — R/W R R/W R/W R/W R/W R/W R/W R/W R R/W R/W R/W R/W R/W R/W MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 143 Chapter 4 Port Integration Module (PIM9KG128V1) Table 4-2. PIM9KG128 Memory Map (continued) Address Offset 0x0020 0x0021 0x0022 0x0023 0x0024 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B 0x002C 0x002D 0x002E 0x002F 0x0030 - 0x003F Port H I/O Register (PTH) Port H Input Register (PTIH) Port H Data Direction Register (DDRH) Port H Reduced Drive Register (RDRH) Port H Pull Device Enable Register (PERH) Port H Polarity Select Register (PPSH) Port H Interrupt Enable Register (PIEH) Port H Interrupt Flag Register (PIFH) Port J I/O Register (PTJ) Port J Input Register (PTIJ) Port J Data Direction Register (DDRJ) Port J Reduced Drive Register (RDRJ) Port J Pull Device Enable Register (PERJ) Port J Polarity Select Register (PPSJ) Port J Interrupt Enable Register (PIEJ) Port J Interrupt Flag Register (PIFJ) Reserved Use Access R/W R R/W R/W R/W R/W R/W R/W R/W R R/W R/W R/W R/W R/W R/W — MC9S12KG128 Data Sheet, Rev. 1.15 144 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.1 Port T Registers Port T is associated with the 8-channel timer (TIM). Each pin is assigned to these modules according to the following priority: Timer > general-purpose I/O. If the timer is enabled, the timer channels configured for output compare are available on port T pins PT[7:0]. Refer to the TIM block description chapter for information on enabling and disabling the TIM module. During reset, port T pins are configured as high-impedance inputs. 4.3.1.1 Port T I/O Register (PTT) Module Base + 0x0000 7 6 5 4 3 2 1 0 R PTT7 W Timer Reset IOC7 0 IOC6 0 IOC5 0 IOC4 0 IOC3 0 IOC2 0 IOC1 0 IOC0 0 PTT6 PTT5 PTT4 PTT3 PTT2 PTT1 PTT0 Figure 4-2. Port T I/O Register (PTT)) Read: Anytime. Write: Anytime. If the data direction bits of the associated I/O pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. 4.3.1.2 Port T Input Register (PTIT) Module Base + 0x0001 7 6 5 4 3 2 1 0 R W Reset PTIT7 PTIT6 PTIT5 PTIT4 PTIT3 PTIT2 PTIT1 PTIT0 u u u u u u u u = Reserved or Unimplemented u = Unaffected by reset Figure 4-3. Port T Input Register (PTIT) Read: Anytime. Write: Never, writes to this register have no effect. This register always reads back the status of the associated pins. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 145 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.1.3 Port T Data Direction Register (DDRT) Module Base + 0x0002 7 6 5 4 3 2 1 0 R W Reset DDRT7 0 DDRT6 0 DDRT5 0 DDRT4 0 DDRT3 0 DDRT2 0 DDRT1 0 DDRT0 0 Figure 4-4. Port T Data Direction Register (DDRT) Read: Anytime. Write: Anytime. This register configures each port T pin as either input or output. The TIM forces the I/O state to be an output for each timer port associated with an enabled output compare. In these cases the data direction bits will not change. The DDRT bits revert to controlling the I/O direction of a pin when the associated timer output compare is disabled. The timer input capture always monitors the state of the pin. Table 4-3. DDRT Field Descriptions Field 7–0 DDRT[7:0] Data Direction Port T 0 Associated pin is configured as input. 1 Associated pin is configured as output. Description 4.3.1.4 Port T Reduced Drive Register (RDRT) Module Base + 0x0003 7 6 5 4 3 2 1 0 R W Reset RDRT7 0 RDRT6 0 RDRT5 0 RDRT4 0 RDRT3 0 RDRT2 0 RDRT1 0 RDRT0 0 Figure 4-5. Port T Reduced Drive Register (RDRT) Read: Anytime. Write: Anytime. This register configures the drive strength of each port T output pin as either full or reduced. If the port is used as input this bit is ignored. Table 4-4. RDRT Field Descriptions Field 7–0 RDRT[7:0] Description Reduced Drive Port T 0 Full drive strength at output. 1 Associated pin drives at about 1/6 of the full drive strength. MC9S12KG128 Data Sheet, Rev. 1.15 146 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.1.5 Port T Pull Device Enable Register (PERT) Module Base + 0x0004 7 6 5 4 3 2 1 0 R PERT7 W Reset 0 0 0 0 0 0 0 0 PERT6 PERT5 PERT4 PERT3 PERT2 PERT1 PERT0 Figure 4-6. Port T Pull Device Enable Register (PERT) Read: Anytime. Write: Anytime. This register configures whether a pull-up or a pull-down device is activated, if the port is used as input. This bit has no effect if the port is used as output. Out of reset no pull device is enabled. Table 4-5. PERT Field Descriptions Field 7–0 PERT[7:0] Description Pull Device Enable Port T 0 Pull-up or pull-down device is disabled. 1 Either a pull-up or pull-down device is enabled. 4.3.1.6 Port T Polarity Select Register (PPST) Module Base + 0x0005 7 6 5 4 3 2 1 0 R PPST7 W Reset 0 0 0 0 0 0 0 0 PPST6 PPST5 PPST4 PPST3 PPST2 PPST1 PPST0 Figure 4-7. Port T Polarity Select Register (PPST) Read: Anytime. Write: Anytime. This register selects whether a pull-down or a pull-up device is connected to the pin. Table 4-6. PPST Field Descriptions Field 7–0 PPST[7:0] Description Pull Select Port T 0 A pull-up device is connected to the associated port T pin, if enabled by the associated bit in register PERT and if the port is used as input. 1 A pull-down device is connected to the associated port T pin, if enabled by the associated bit in register PERT and if the port is used as input. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 147 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.2 Port S Registers Port S is associated with the serial peripheral interface (SPI0) and serial communication interfaces (SCI1, SCI0). Each pin is assigned to these modules according to the following priority: SPI0/SCI1/SCI0 > general-purpose I/O. When the SPI0 is enabled, the PS[7:4] pins become SS0, SCK0, MOSI0, and MISO0 respectively. Refer to the SPI block description chapter for information on enabling and disabling the SPI0. The SPI0 pins can be re-routed. Refer to Section 4.3.3.8, “Module Routing Register (MODRR)”. When the SCI1 receiver and transmitter are enabled, the PS[3:2] pins become TXD1 and RXD1 respectively. When the SCI0 receiver and transmitter are enabled, the PS[1:0] pins become TXD0 and RXD0 respectively. Refer to the SCI block description chapter for information on enabling and disabling the SCI receiver and transmitter. During reset, port S pins are configured as inputs with pull-up. 4.3.2.1 Port S I/O Register (PTS) Module Base + 0x0008 7 6 5 4 3 2 1 0 R PTS7 W SPI/SCI Reset SS0 0 SCK0 0 MOSI0 0 MISO0 0 TXD1 0 RXD1 0 TXD0 0 RXD0 0 PTS6 PTS5 PTS4 PTS3 PTS2 PTS1 PTS0 Figure 4-8. Port S I/O Register (PTS) Read: Anytime. Write: Anytime. If the data direction bits of the associated I/O pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. The SPI0 function takes precedence over the general-purpose I/O function if the SPI0 is enabled. If enabled, the SCI0(1) transmitter takes precedence over the general-purpose I/O function, and the corresponding TXD0(1) pin is configured as an output. If enabled, the SCI0(1) receiver takes precedence over the general-purpose I/O function, and the corresponding RXD0(1) pin is configured as an input. MC9S12KG128 Data Sheet, Rev. 1.15 148 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.2.2 Port S Input Register (PTIS) Module Base + 0x0009 7 6 5 4 3 2 1 0 R W Reset PTIS7 PTIS6 PTIS5 PTIS4 PTIS3 PTIS2 PTIS1 PTIS0 u u u u u u u u = Reserved or Unimplemented u = Unaffected by reset Figure 4-9. Port S Input Register (PTIS) Read: Anytime. Write: Never, writes to this register have no effect. This register always reads back the status of the associated pins. 4.3.2.3 Port S Data Direction Register (DDRS) Module Base + 0x000A 7 6 5 4 3 2 1 0 R W Reset DDRS7 0 DDRS6 0 DDRS5 0 DDRS4 0 DDRS3 0 DDRS2 0 DDRS1 0 DDRS0 0 Figure 4-10. Port S Data Direction Register (DDRS) Read: Anytime. Write: Anytime. This register configures each port S pin as either input or output. When the SPI0 is enabled, the PS[7:4] pins become the SPI bidirectional pins. The associated Data Direction Register bits have no effect. When the SCI0(1) transmitter is enabled, the PS[1](PS[3]) pin becomes the TXD0(1) output pin and the associated Data Direction Register bit has no effect. When the SCI0(1) receiver is enabled, the PS[0](PS[2]) pin becomes the RXD0(1) input pin and the associated Data Direction Register bit has no effect. If the SPI0, SCI0 and SCI1 functions are disabled, the corresponding Data Direction Register bit reverts to control the I/O direction of the associated pin. Table 4-7. DDRS Field Descriptions Field 7–0 DDRS[7:0] Data Direction Port S 0 Associated pin is configured as input. 1 Associated pin is configured as output. Description MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 149 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.2.4 Port S Reduced Drive Register (RDRS) Module Base + 0x000B 7 6 5 4 3 2 1 0 R W Reset RDRS7 0 RDRS6 0 RDRS5 0 RDRS4 0 RDRS3 0 RDRS2 0 RDRS1 0 RDRS0 0 Figure 4-11. Port S Reduced Drive Register (RDRS) Read: Anytime. Write: Anytime. This register configures the drive strength of each port S output pin as either full or reduced. If the port is used as input this bit is ignored. Table 4-8. RDRS Field Descriptions Field 7–0 RDRS[7:0] Description Reduced Drive Port S 0 Full drive strength at output. 1 Associated pin drives at about 1/6 of the full drive strength. 4.3.2.5 Port S Pull Device Enable Register (PERS) Module Base + 0x000C 7 6 5 4 3 2 1 0 R PERS7 W Reset 1 1 1 1 1 1 1 1 PERS6 PERS5 PERS4 PERS3 PERS2 PERS1 PERS0 Figure 4-12. Port S Pull Device Enable Register (PERS) Read: Anytime. Write: Anytime. This register configures whether a pull-up or a pull-down device is activated, if the port is used as input or as output in wired-OR (open drain) mode. This bit has no effect if the port is used as push-pull output. Out of reset a pull-up device is enabled. Table 4-9. PERS Field Descriptions Field 7–0 PERS[7:] Description Pull Device Enable Port S 0 Pull-up or pull-down device is disabled. 1 Either a pull-up or pull-down device is enabled. MC9S12KG128 Data Sheet, Rev. 1.15 150 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.2.6 Port S Polarity Select Register (PPSS) Module Base + 0x000D 7 6 5 4 3 2 1 0 R PPSS7 W Reset 0 0 0 0 0 0 0 0 PPSS6 PPSS5 PPSS4 PPSS3 PPSS2 PPSS1 PPSS0 Figure 4-13. Port S Polarity Select Register (PPSS) Read: Anytime. Write: Anytime. This register selects whether a pull-down or a pull-up device is connected to the pin. Table 4-10. PPSS Field Descriptions Field 7–0 PPSS[7:0] Description Pull Select Port S 0 A pull-up device is connected to the associated port S pin, if enabled by the associated bit in register PERS and if the port is used as input or as wired-OR output. 1 A pull-down device is connected to the associated port S pin, if enabled by the associated bit in register PERS and if the port is used as input. 4.3.2.7 Port S Wired-OR Mode Register (WOMS) Module Base + 0x000E 7 6 5 4 3 2 1 0 R WOMS7 W Reset 0 0 0 0 0 0 0 0 WOMS6 WOMS5 WOMS4 WOMS3 WOMS2 WOMS1 WOMS0 Figure 4-14. Port S Wired-OR Mode Register (WOMS) Read: Anytime. Write: Anytime. This register configures the output pins as wired-OR. If enabled the output is driven active low only (open-drain). A logic level of “1” is not driven. It applies also to the SPI and SCI outputs and allows a multipoint connection of several serial modules. This bit has no influence on pins used as inputs. Table 4-11. WOMS Field Descriptions Field 7–0 Wired-OR Mode Port S WOMS[7:0] 0 Output buffers operate as push-pull outputs. 1 Output buffers operate as open-drain outputs. Description MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 151 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.3 Port M Registers Port M is associated with two Freescale’s scalable controller area network (CAN4, CAN0) and one serial peripheral interface (SPI0) modules. Each pin is assigned to these modules according to the following priority: CAN0 > CAN4 > SPI0 > general-purpose I/O. Refer to the SPI block description chapter for information on enabling and disabling the SPI0. Refer to the MSCAN block description chapter for information on enabling and disabling CAN0 or CAN4. The SPI0, CAN0 and CAN4 pins can be re-routed. Refer to Section 4.3.3.8, “Module Routing Register (MODRR)”. During reset, port M pins are configured as high-impedance inputs. 4.3.3.1 Port M I/O Register (PTM) Module Base + 0x0010 7 6 5 4 3 2 1 0 R PTM7 W SPI0 CAN4 CAN0 Reset 0 0 TXCAN4 RXCAN4 SCK0 TXCAN4 TXCAN0 0 MOSI0 RXCAN4 RXCAN0 0 TXCAN0 0 RXCAN0 0 TXCAN0 0 RXCAN0 0 SS0 MISO0 PTM6 PTM5 PTM4 PTM3 PTM2 PTM1 PTM0 Figure 4-15. Port M I/O Register (PTM) Read: Anytime. Write: Anytime. If the data direction bits of the associated I/O pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. 4.3.3.2 Port M Input Register (PTIM) Module Base + 0x0011 7 6 5 4 3 2 1 0 R W Reset PTIM7 PTIM6 PTIM5 PTIM4 PTIM3 PTIM2 PTIM1 PTIM0 u u u u u u u u = Reserved or Unimplemented u = Unaffected by reset Figure 4-16. Port M Input Register (PTIM) Read: Anytime. Write: Never, writes to this register have no effect. This register always reads back the status of the associated pins. MC9S12KG128 Data Sheet, Rev. 1.15 152 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.3.3 Port M Data Direction Register (DDRM) Module Base + 0x0012 7 6 5 4 3 2 1 0 R DDRM7 W Reset 0 0 0 0 0 0 0 0 DDRM6 DDRM5 DDRM4 DDRM3 DDRM2 DDRM1 DDRM0 Figure 4-17. Port M Data Direction Register (DDRM) Read: Anytime. Write: Anytime. This register configures each port M pin as either input or output. The CAN forces the I/O state to be an output for each port line associated with an enabled output (TXCAN4 and TXCAN0). It also forces the I/O state to be an input for each port line associated with an enabled input (RXCAN4 and RXCAN0). In those cases the data direction bits will not change. The DDRM bits revert to controlling the I/O direction of a pin when the associated peripheral module is disabled. Table 4-12. DDRM Field Descriptions Field 7–0 DDRM[7:0] Data Direction Port M 0 Associated pin is configured as input. 1 Associated pin is configured as output. Description 4.3.3.4 Port M Reduced Drive Register (RDRM) Module Base + 0x0013 7 6 5 4 3 2 1 0 R RDRM7 W Reset 0 0 0 0 0 0 0 0 RDRM6 RDRM5 RDRM4 RDRM3 RDRM2 RDRM1 RDRM0 Figure 4-18. Port M Reduced Drive Register (RDRM) Read: Anytime. Write: Anytime. This register configures the drive strength of each port M output pin as either full or reduced. If the port is used as input this bit is ignored. Table 4-13. RDRM Field Descriptions Field 7–0 RDRM[7:0] Description Reduced Drive Port M 0 Full drive strength at output. 1 Associated pin drives at about 1/6 of the full drive strength. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 153 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.3.5 Port M Pull Device Enable Register (PERM) Module Base + 0x0014 7 6 5 4 3 2 1 0 R PERM7 W Reset 0 0 0 0 0 0 0 0 PERM6 PERM5 PERM4 PERM3 PERM2 PERM1 PERM0 Figure 4-19. Port M Pull Device Enable Register (PERM) Read: Anytime. Write: Anytime. This register configures whether a pull-up or a pull-down device is activated, if the port is used as input or wired-OR output. This bit has no effect if the port is used as push-pull output. Out of reset no pull device is enabled. Table 4-14. PERM Field Descriptions Field 7–0 PERM[7:0] Description Pull Device Enable Port M 0 Pull-up or pull-down device is disabled. 1 Either a pull-up or pull-down device is enabled. 4.3.3.6 Port M Polarity Select Register (PPSM) Module Base + 0x0015 7 6 5 4 3 2 1 0 R W Reset PPSM7 0 PPSM6 0 PPSM5 0 PPSM4 0 PPSM3 0 PPSM2 0 PPSM1 0 PPSM0 0 Figure 4-20. Port M Polarity Select Register (PPSM) Read: Anytime. Write: Anytime. This register selects whether a pull-down or a pull-up device is connected to the pin. If CAN is active a pull-up device can be activated on the receiver inputs, but not a pull-down. Table 4-15. PPSM Field Descriptions Field 7–0 PPSM[7:0] Description Pull Select Port M 0 A pull-up device is connected to the associated port M pin, if enabled by the associated bit in register PERM and if the port is used as general purpose, RXCAN input. 1 A pull-down device is connected to the associated port M pin, if enabled by the associated bit in register PERM and if the port is used as a general purpose but not as RXCAN. MC9S12KG128 Data Sheet, Rev. 1.15 154 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.3.7 Port M Wired-OR Mode Register (WOMM) 7 6 5 4 3 2 1 0 Module Base + 0x0016 R W Reset WOMM7 0 WOMM6 0 WOMM5 0 WOMM4 0 WOMM3 0 WOMM2 0 WOMM1 0 WOMM0 0 Figure 4-21. Port M Wired-OR Mode Register (WOMM) Read: Anytime. Write: Anytime. This register configures the output pins as wired-OR. If enabled the output is driven active low only (open-drain). A logic level of “1” is not driven. It applies also to the CAN outputs and allows a multipoint connection of several serial modules. This bit has no influence on pins used as inputs. Table 4-16. WOMM Field Descriptions Field 7–0 Wired-OR Mode Port M WOMM[7:0] 0 Output buffers operate as push-pull outputs. 1 Output buffers operate as open-drain outputs. Description 4.3.3.8 Module Routing Register (MODRR) Module Base + 0x0017 7 6 5 4 3 2 1 0 R W Reset 0 MODRR6 0 0 MODRR5 0 MODRR4 0 MODRR3 0 MODRR2 0 MODRR1 0 MODRR0 0 = Unimplemented or Reserved Figure 4-22. Module Routing Register (MODRR) Read: Anytime. Write: Anytime. This register configures the re-routing of CAN0, CAN4, SPI0, SPI1 and SPI2 on defined port pins. Table 4-17. MODRR Field Descriptions Field 6 MODRR6 5 MODRR5 4 MODRR4 SPI2 Routing Bit — See Table 4-22. SPI1 Routing Bit — See Table 4-21. SPI0 Routing Bit — See Table 4-20. Description MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 155 Chapter 4 Port Integration Module (PIM9KG128V1) Table 4-17. MODRR Field Descriptions (continued) Field 3–2 CAN4 Routing Bits — See Table 4-19. MODRR[3:2] 1–0 CAN0 Routing Bits — See Table 4-18. MODRR[1:0] Description Table 4-18. CAN0 Routing MODRR[1] 0 0 1 1 MODRR[0] 0 1 0 1 RXCAN0 PM0 PM2 PM4 Reserved TXCAN0 PM1 PM3 PM5 Table 4-19. CAN4 Routing MODRR[3] 0 0 1 1 MODRR[2] 0 1 0 1 RXCAN4 PJ6 PM4 PM6 Reserved TXCAN4 PJ7 PM5 PM7 Table 4-20. SPI0 Routing MODRR[4] 0 1 MISO0 PS4 PM2 MOSI0 PS5 PM4 SCK0 PS6 PM5 SS0 PS7 PM3 Table 4-21. SPI1 Routing MODRR[5] 0 1 MISO1 PP0 PH0 MOSI1 PP1 PH1 SCK1 PP2 PH2 SS1 PP3 PH3 Table 4-22. SPI2 Routing MODRR[6] 0 1 MISO2 PP4 PH4 MOSI2 PP5 PH5 SCK2 PP6 PH6 SS2 PP7 PH7 MC9S12KG128 Data Sheet, Rev. 1.15 156 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) Table 4-23. Implemented Modules on Derivatives Number of Modules 3 2 1 MSCAN Modules CAN0 X X X CAN4 X X — SPI0 X X X SPI Modules SPI1 X X — SPI2 X — — If the SPI0 module is routed on PM[5:4] and used in bidirectional master mode with disabled SS output, PM[3:2] are free to be used with CAN or GPIO. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 157 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.4 Port P Registers Port P is associated with the Pulse Width Modulator (PWM) and two serial peripheral interfaces (SPI1, SPI2). Each pin is assigned to these modules according to the following priority: PWM > SPI2/SP1 > general-purpose I/O. When a PWM channel is enabled, the corresponding pin becomes a PWM output with the exception of of pin 7 which can be PWM input or output. Refer to the PWM block description chapter for information on enabling and disabling the PWM channels. When SPI2 is enabled and the corresponding PWM channels are disabled, the respective pin configuration for PP[7:4] is determined by several status bits in the SPI2 module. When SPI1 is enabled and the corresponding PWM channels are disabled, the respective pin configuration for PP[3:0] is determined by several status bits in the SPI1 module. Refer to the SPI block description chapter for information on enabling and disabling the SPI. The SPI1 and SPI2 pins can be re-routed. Refer to Section 4.3.3.8, “Module Routing Register (MODRR)”. During reset, port P pins are configured as high-impedance inputs. 4.3.4.1 Port P I/O Register (PTP) Module Base + 0x0018 7 6 5 4 3 2 1 0 R PTP7 W PWM SPI Reset PWM7 SCK2 0 PWM6 SS2 0 PWM5 MOSI2 0 PWM4 MISO2 0 PWM3 SS1 0 PWM2 SCK1 0 PWM1 MOSI1 0 PWM0 MISO1 0 PTP6 PTP5 PTP4 PTP3 PTP2 PTP1 PTP0 Figure 4-23. Port P I/O Register (PTP) Read: Anytime. Write: Anytime. If the data direction bits of the associated I/O pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. The PWM function takes precedence over the general purpose I/O function if the associated PWM channel is enabled. While channels 6-0 are output only if the respective channel is enabled, channel 7 can be PWM output or input if the shutdown feature is enabled. The SPI function takes precedence over the general purpose I/O function associated with if enabled. If both PWM and SPI are enabled the PWM functionality takes precedence. MC9S12KG128 Data Sheet, Rev. 1.15 158 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.4.2 Port P Input Register (PTIP) Module Base + 0x0019 7 6 5 4 3 2 1 0 R W Reset PTIP7 PTIP6 PTIP5 PTIP4 PTIP3 PTIP2 PTIP1 PTIP0 u u u u u u u u = Reserved or Unimplemented u = Unaffected by reset Figure 4-24. Port P Input Register (PTIP) Read: Anytime. Write: Never, writes to this register have no effect. This register always reads back the status of the associated pins. 4.3.4.3 Port P Data Direction Register (DDRP) Module Base + 0x001A 7 6 5 4 3 2 1 0 R DDRP7 W Reset 0 0 0 0 0 0 0 0 DDRP6 DDRP5 DDRP4 DDRP3 DDRP2 DDRP1 DDRP0 Figure 4-25. Port P Data Direction Register (DDRP) Read: Anytime. Write: Anytime. This register configures each port P pin as either input or output. If the associated PWM channel or SPI module is enabled this register has no effect on the pins. The PWM forces the I/O state to be an output for each port line associated with an enabled PWM7-0 channel. Channel 7 can force the pin to input if the shutdown feature is enabled. If a SPI module is enabled, the SPI determines the pin direction If the PWM, SPI1 and SPI2 functions are disabled, the corresponding Data Direction Register bit reverts to control the I/O direction of the associated pin. Table 4-24. DDRP Field Descriptions Field 7–0 DDRP[7:0] Data Direction Port P 0 Associated pin is configured as input. 1 Associated pin is configured as output. Description MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 159 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.4.4 Port P Reduced Drive Register (RDRP) Module Base + 0x001B 7 6 5 4 3 2 1 0 R RDRP7 W Reset 0 0 0 0 0 0 0 0 RDRP6 RDRP5 RDRP4 RDRP3 RDRP2 RDRP1 RDRP0 Figure 4-26. Port P Reduced Drive Register (RDRP) Read: Anytime. Write: Anytime. This register configures the drive strength of each port P output pin as either full or reduced. If the port is used as input this bit is ignored. Table 4-25. RDRP Field Descriptions Field 7–0 RDRP[7:0] Description Reduced Drive Port P 0 Full drive strength at output. 1 Associated pin drives at about 1/6 of the full drive strength. 4.3.4.5 Port P Pull Device Enable Register (PERP) Module Base + 0x001C 7 6 5 4 3 2 1 0 R PERP7 W Reset 0 0 0 0 0 0 0 0 PERP6 PERP5 PERP4 PERP3 PERP2 PERP1 PERP0 Figure 4-27. Port P Pull Device Enable Register (PERP) Read: Anytime. Write: Anytime. This register configures whether a pull-up or a pull-down device is activated, if the port is used as input. This bit has no effect if the port is used as output. Out of reset no pull device is enabled. Table 4-26. PERP Field Descriptions Field 7–0 PERP[7:0] Description Pull Device Enable Port P 0 Pull-up or pull-down device is disabled. 1 Either a pull-up or pull-down device is enabled. MC9S12KG128 Data Sheet, Rev. 1.15 160 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.4.6 Port P Polarity Select Register (PPSP) Module Base + 0x001D 7 6 5 4 3 2 1 0 R PPSP7 W Reset 0 0 0 0 0 0 0 0 PPSP6 PPSP5 PPSP4 PPSP3 PPSP2 PPSP1 PPSP0 Figure 4-28. Port P Polarity Select Register (PPSP) Read: Anytime. Write: Anytime. This register serves a dual purpose by selecting the polarity of the active interrupt edge as well as selecting a pull-up or pull-down device if enabled. Table 4-27. PPSP Field Descriptions Field 7–0 PPSP[7:0] Description Polarity Select Port P 0 Falling edge on the associated port P pin sets the associated flag bit in the PIFP register.A pull-up device is connected to the associated port P pin, if enabled by the associated bit in register PERP and if the port is used as input. 1 Rising edge on the associated port P pin sets the associated flag bit in the PIFP register.A pull-down device is connected to the associated port P pin, if enabled by the associated bit in register PERP and if the port is used as input. 4.3.4.7 Port P Interrupt Enable Register (PIEP) Module Base + 0x001E 7 6 5 4 3 2 1 0 R PIEP7 W Reset 0 0 0 0 0 0 0 0 PIEP6 PIEP5 PIEP4 PIEP3 PIEP2 PIEP1 PIEP0 Figure 4-29. Port P Interrupt Enable Register (PIEP) Read: Anytime. Write: Anytime. This register disables or enables on a per pin basis the edge sensitive external interrupt associated with port P. Table 4-28. PIEP Field Descriptions Field 7–0 PIEP[7:0] Interrupt Enable Port P 0 Interrupt is disabled (interrupt flag masked). 1 Interrupt is enabled. Description MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 161 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.4.8 Port P Interrupt Flag Register (PIFP) Module Base + 0x001F 7 6 5 4 3 2 1 0 R PIFP7 W Reset 0 0 0 0 0 0 0 0 PIFP6 PIFP5 PIFP4 PIFP3 PIFP2 PIFP1 PIFP0 Figure 4-30. Port P Interrupt Flag Register (PIFP) Read: Anytime. Write: Anytime. Each flag is set by an active edge on the associated input pin. This could be a rising or a falling edge based on the state of the PPSP register. To clear this flag, write “1” to the corresponding bit in the PIFP register. Writing a “0” has no effect. Table 4-29. Field Descriptions Field 7–0 PIFP[7:0] Description Interrupt Flags Port P 0 No active edge pending. Writing a “0” has no effect. 1 Active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set). Writing a “1” clears the associated flag. MC9S12KG128 Data Sheet, Rev. 1.15 162 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.5 Port H Registers Port H is associated with two serial peripheral interfaces (SPI1, SPI2). Each pin is assigned to these modules according to the following priority: SPI2/SP1 > general-purpose I/O. When SPI2 is enabled, the respective pin configuration for PH[7:4] is determined by several status bits in the SPI2 module. When SPI1 is enabled, the respective pin configuration for PH[3:0] is determined by several status bits in the SPI1 module. Refer to the SPI block description chapter for information on enabling and disabling the SPI. The SPI1 and SPI2 pins can be re-routed. Refer to Section 4.3.3.8, “Module Routing Register (MODRR)”. During reset, port H pins are configured as high-impedance inputs. 4.3.5.1 Port H I/O Register (PTH) Module Base + 0x0020 7 6 5 4 3 2 1 0 R PTH7 W SPI Reset SS2 0 SCK2 0 MOSI2 0 MISO2 0 SS1 0 SCK1 0 MOSI1 0 MISO1 0 PTH6 PTH5 PTH4 PTH3 PTH2 PTH1 PTH0 Figure 4-31. Port H I/O Register (PTH) Read: Anytime. Write: Anytime. If the data direction bits of the associated I/O pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. The SPI function takes precedence over the general purpose I/O if enabled.. 4.3.5.2 Port H Input Register (PTIH) Module Base + 0x0021 7 6 5 4 3 2 1 0 R W Reset PTIH7 PTIH6 PTIH5 PTIH4 PTIH3 PTIH2 PTIH1 PTIH0 u u u u u u u u = Reserved or Unimplemented u = Unaffected by reset Figure 4-32. Port H Input Register (PTIH) Read: Anytime. Write: Never, writes to this register have no effect. This register always reads back the status of the associated pins. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 163 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.5.3 Port H Data Direction Register (DDRH) Module Base + 0x0022 7 6 5 4 3 2 1 0 R DDRH7 W Reset 0 0 0 0 0 0 0 0 DDRH6 DDRH5 DDRH4 DDRH3 DDRH2 DDRH1 DDRH0 Figure 4-33. Port H Data Direction Register (DDRH) Read: Anytime. Write: Anytime. This register configures each port H pin as either input or output. Table 4-30. DDRH Field Descriptions Field 7–0 DDRH]7:0] Data Direction Port H 0 Associated pin is configured as input. 1 Associated pin is configured as output. Description 4.3.5.4 Port H Reduced Drive Register (RDRH) Module Base + 0x0023 7 6 5 4 3 2 1 0 R RDRH7 W Reset 0 0 0 0 0 0 0 0 RDRH6 RDRH5 RDRH4 RDRH3 RDRH2 RDRH1 RDRH0 Figure 4-34. Port H Reduced Drive Register (RDRH) Read: Anytime. Write: Anytime. This register configures the drive strength of each port H output pin as either full or reduced. If the port is used as input this bit is ignored. Table 4-31. RDRH Field Descriptions Field 7–0 RDRH[7:0] Description Reduced Drive Port H 0 Full drive strength at output. 1 Associated pin drives at about 1/6 of the full drive strength. MC9S12KG128 Data Sheet, Rev. 1.15 164 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.5.5 Port H Pull Device Enable Register (PERH) Module Base + 0x0024 7 6 5 4 3 2 1 0 R PERH7 W Reset 0 0 0 0 0 0 0 0 PERH6 PERH5 PERH4 PERH3 PERH2 PERH1 PERH0 Figure 4-35. Port H Pull Device Enable Register (PERH) Read: Anytime. Write: Anytime. This register configures whether a pull-up or a pull-down device is activated, if the port is used as input. This bit has no effect if the port is used as output. Out of reset no pull device is enabled. Table 4-32. PERH Field Descriptions Field 7–0 PERH[7:0] Description Pull Device Enable Port H 0 Pull-up or pull-down device is disabled. 1 Either a pull-up or pull-down device is enabled. 4.3.5.6 Port H Polarity Select Register (PPSH) Module Base + 0x0025 7 6 5 4 3 2 1 0 R PPSH7 W Reset 0 0 0 0 0 0 0 0 PPSH6 PPSH5 PPSH4 PPSH3 PPSH2 PPSH1 PPSH0 Figure 4-36. Port H Polarity Select Register (PPSH) Read: Anytime. Write: Anytime. This register serves a dual purpose by selecting the polarity of the active interrupt edge as well as selecting a pull-up or pull-down device if enabled. Table 4-33. PPSH Field Descriptions Field 7–0 PPSH[7:0] Description Polarity Select Port H 0 Falling edge on the associated port H pin sets the associated flag bit in the PIFH register. A pull-up device is connected to the associated port H pin, if enabled by the associated bit in register PERH and if the port is used as input. 1 Rising edge on the associated port H pin sets the associated flag bit in the PIFH register. A pull-down device is connected to the associated port H pin, if enabled by the associated bit in register PERH and if the port is used as input. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 165 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.5.7 Port H Interrupt Enable Register (PIEH) Module Base + 0x0026 7 6 5 4 3 2 1 0 R PIEH7 W Reset 0 0 0 0 0 0 0 0 PIEH6 PIEH5 PIEH4 PIEH3 PIEH2 PIEH1 PIEH0 Figure 4-37. Port H Interrupt Enable Register (PIEH) Read: Anytime. Write: Anytime. This register disables or enables on a per pin basis the edge sensitive external interrupt associated with port H. Table 4-34. PIEH Field Descriptions Field 7–0 PIEH[7:0] Interrupt Enable Port H 0 Interrupt is disabled (interrupt flag masked). 1 Interrupt is enabled. Description 4.3.5.8 Port H Interrupt Flag Register (PIFH) Module Base + 0x0027 7 6 5 4 3 2 1 0 R PIFH7 W Reset 0 0 0 0 0 0 0 0 PIFH6 PIFH5 PIFH4 PIFH3 PIFH2 PIFH1 PIFH0 Figure 4-38. Port H Interrupt Flag Register (PIFH) Read: Anytime. Write: Anytime. Each flag is set by an active edge on the associated input pin. This could be a rising or a falling edge based on the state of the PPSH register. To clear this flag, write “1” to the corresponding bit in the PIFH register. Writing a “0” has no effect. Table 4-35. PIFH Field Descriptions Field 7–0 PIFH[7:0] Description Interrupt Flags Port H 0 No active edge pending. Writing a “0” has no effect. 1 Active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set). Writing a “1” clears the associated flag. MC9S12KG128 Data Sheet, Rev. 1.15 166 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.6 Port J Registers Port J is associated with Freescale’s scalable controller area network (CAN4) and Inter-IC bus (IIC) modules. Each pin is assigned to these modules according to the following priority: CAN4 > IIC > general-purpose I/O. The CAN4 function (TXCAN4 and RXCAN4) takes precedence over the IIC and the general purpose I/O function if the CAN4 module is enabled. Refer to the MSCAN block description chapter for information on enabling and disabling CAN4. The IIC function (SCL and SDA) takes precedence over the general purpose I/O function if the IIC is enabled. If the IIC module takes precedence the SDA and SCL outputs are configured as open drain outputs. Refer to the IIC block description chapter for information on enabling and disabling the IIC. During reset, port J pins are configured as inputs with pull-up. 4.3.6.1 Port J I/O Register (PTJ) Module Base + 0x0028 7 6 5 4 3 2 1 0 R PTJ7 W CAN4 IIC Reset TXCAN4 SCL 0 RXCAN4 SDA 0 PTJ6 0 0 0 0 PTJ1 PTJ0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 4-39. Port J I/O Register (PTJ) Read: Anytime. Write: Anytime. If the data direction bits of the associated I/O pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. 4.3.6.2 Port J Input Register (PTIJ) Module Base + 0x0029 7 6 5 4 3 2 1 0 R W Reset PTIJ7 PTIJ6 0 0 0 0 PTIJ1 PTIJ0 u u 0 0 0 0 u u = Reserved or Unimplemented u = Unaffected by reset Figure 4-40. Port J Input Register (PTIJ) Read: Anytime. Write: Never, writes to this register have no effect. This register always reads back the status of the associated pins. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 167 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.6.3 Port J Data Direction Register (DDRJ) Module Base + 0x002A 7 6 5 4 3 2 1 0 R DDRJ7 W Reset 0 0 DDRJ6 0 0 0 0 DDRJ1 DDRJ0 0 — — — — 0 = Unimplemented or Reserved Figure 4-41. Port J Data Direction Register (DDRJ) Read: Anytime. Write: Anytime. This register configures each port J pin as either input or output. If enable, CAN4 forces the I/O state to be an output on PJ7 (TXCAN4) and an input on pin PJ6 (RXCAN4). If CAN4 is disabled, the IIC takes control of the I/O if enabled. In these cases the data direction bits will not change. The DDRJ bits revert to controlling the I/O direction of a pin when the associated peripheral module is disabled. Table 4-36. Field Descriptions Field 7, 6, 1, 0 DDRJ[7:6] DDRJ[1:0] Data Direction Port J 0 Associated pin is configured as input. 1 Associated pin is configured as output. Description 4.3.6.4 Port J Reduced Drive Register (RDRJ) Module Base + 0x002B 7 6 5 4 3 2 1 0 R W Reset RDRJ7 0 RDRJ6 0 0 — 0 — 0 — 0 — RDRJ1 0 RDRJ0 0 = Unimplemented or Reserved Figure 4-42. Port J Reduced Drive Register (RDRJ) Read: Anytime. Write: Anytime. This register configures the drive strength of each port J output pin as either full or reduced. If the port is used as input this bit is ignored. Table 4-37. RDRJ Field Descriptions Field 7, 6, 1, 0 RDRJ[7:6] RDRJ[1:0] Description Reduced Drive Port J 0 Full drive strength at output. 1 Associated pin drives at about 1/6 of the full drive strength. MC9S12KG128 Data Sheet, Rev. 1.15 168 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.6.5 Port J Pull Device Enable Register (PERJ) Module Base + 0x002C 7 6 5 4 3 2 1 0 R W Reset PERJ7 1 PERJ6 1 0 — 0 — 0 — 0 — PERJ1 1 PERJ0 1 = Unimplemented or Reserved Figure 4-43. Port J Pull Device Enable Register (PERJ) Read: Anytime. Write: Anytime. This register configures whether a pull-up or a pull-down device is activated, if the port is used as input or as wired-OR output. This bit has no effect if the port is used as push-pull output. Out of reset a pull-up device is enabled. Table 4-38. PERJ Field Descriptions Field 7, 6, 1, 0 PERJ[7:6] PERJ[1:0] Description Pull Device Enable Port J 0 Pull-up or pull-down device is disabled. 1 Either a pull-up or pull-down device is enabled. 4.3.6.6 Port J Polarity Select Register (PPSJ) Module Base + 0x002D 7 6 5 4 3 2 1 0 R W Reset PPSJ7 0 PPSJ6 0 0 — 0 — 0 — 0 — PPSJ1 0 PPSJ0 0 = Unimplemented or Reserved Figure 4-44. Port J Polarity Select Register (PPSJ) Read: Anytime. Write: Anytime. This register serves a dual purpose by selecting the polarity of the active interrupt edge as well as selecting a pull-up or pull-down device if enabled. Table 4-39. PPSJ Field Descriptions Field 7, 6, 1, 0 PPSJ[7:6] PPSJ[1:0] Description Polarity Select Port J 0 Falling edge on the associated port J pin sets the associated flag bit in the PIFJ register. A pull-up device is connected to the associated port J pin, if enabled by the associated bit in register PERJ and if the port is used as general purpose input or as IIC port. 1 Rising edge on the associated port J pin sets the associated flag bit in the PIFJ register. A pull-down device is connected to the associated port J pin, if enabled by the associated bit in register PERJ and if the port is used as input. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 169 Chapter 4 Port Integration Module (PIM9KG128V1) 4.3.6.7 Port J Interrupt Enable Register (PIEJ) Module Base + 0x002E 7 6 5 4 3 2 1 0 R W Reset PIEJ7 0 PIEJ6 0 0 — 0 — 0 — 0 — PIEJ1 0 PIEJ0 0 = Unimplemented or Reserved Figure 4-45. Port J Interrupt Enable Register (PIEJ) Read: Anytime. Write: Anytime. This register disables or enables on a per pin basis the edge sensitive external interrupt associated with port J. Table 4-40. PIEJ Field Descriptions Field 7, 6, 1, 0 PIEJ[7:6] PIEJ[1:0] Interrupt Enable Port J 0 Interrupt is disabled (interrupt flag masked). 1 Interrupt is enabled. Description 4.3.6.8 Port J Interrupt Flag Register (PIFJ) Module Base + 0x002F 7 6 5 4 3 2 1 0 R PIFJ7 W Reset 0 0 PIFJ6 0 0 0 0 PIFJ1 PIFJ0 0 — — — — 0 = Unimplemented or Reserved Figure 4-46. Port J Interrupt Flag Register (PIFJ) Read: Anytime. Write: Anytime. Each flag is set by an active edge on the associated input pin. This could be a rising or a falling edge based on the state of the PPSJ register. To clear this flag, write “1” to the corresponding bit in the PIFJ register. Writing a “0” has no effect. Table 4-41. PIFJ Field Descriptions Field 7, 6, 1, 0 PIFJ[7:6] PIFJ[1:0] Description Interrupt Flags Port J 0 No active edge pending. Writing a “0” has no effect. 1 Active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set). Writing a “1” clears the associated flag. MC9S12KG128 Data Sheet, Rev. 1.15 170 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.4 Functional Description Each pin can act as general purpose I/O. In addition the pin can act as an output from a peripheral module or an input to a peripheral module. Table 4-42 summarizes the priority in case of multiple enabled modules trying to control a shared port. Table 4-42. Summary of Functional Priority Port T S M Priority1 TIMER > GPIO SCI0, SCI1, SPI0 > GPIO CAN0 > GPIO CAN0 (routed) > SPI0 (routed) > GPIO CAN0 (routed) > CAN4 (routed) > SPI0 (routed) > GPIO CAN4 (routed) > GPIO PWM > SPI1, SPI2 > GPIO SPI1, SPI2 > GPIO CAN4 > IIC > GPIO P H J 1 Highest priority >... > lowest priority A set of configuration registers is common to all ports. All registers can be written at any time, however a specific configuration might not become active. Example: A selected pull-up resistor does not become active while the port is used as a push-pull output. 4.4.1 I/O Register The I/O Register holds the value driven out to the pin if the port is used as a general-purpose I/O. Writing to the I/O Register only has an effect on the pin if the port is used as general-purpose output. When reading the I/O Register, the value of each pin is returned if the corresponding Data Direction Register bit is set to 0 (pin configured as input). If the data direction register bits is set to 1, the content of the I/O Register bit is returned. This is independent of any other configuration (Figure 4-47). Due to internal synchronization circuits, it can take up to 2 bus cycles until the correct value is read on the I/O Register when changing the data direction register. 4.4.2 Input Register The Input Register is a read-only register and generally returns the value of the pin (Figure 4-47). It can be used to detect overload or short circuit conditions. Due to internal synchronization circuits, it can take up to 2 bus cycles until the correct value is read on the Input Register when changing the Data Direction Register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 171 Chapter 4 Port Integration Module (PIM9KG128V1) 4.4.3 Data Direction Register The Data Direction Register defines whether the pin is used as an input or an output. A Data Direction Register bit set to 0 configures the pin as an input. A Data Direction Register bit set to 0 configures the pin as an output. If a peripheral module controls the pin the contents of the data direction register is ignored (Figure 4-47). PTIx 0 1 PTx 0 1 PAD DDRx Digital Module data out output enable 0 1 module enable Figure 4-47. Illustration of I/O Pin Functionality Figure 4-48 shows the state of digital inputs and outputs when an analog module drives the port. When the analog module is enabled all associated digital output ports are disabled and all associated digital input ports read “1”. 1 Digital Input 1 0 Module Enable Analog Module Digital Output Analog Output 0 1 PAD PIM Boundary Figure 4-48. Digital Ports and Analog Module 4.4.4 Reduced Drive Register If the port is used as an output the Reduced Drive Register allows the configuration of the drive strength. MC9S12KG128 Data Sheet, Rev. 1.15 172 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) 4.4.5 Pull Device Enable Register The Pull Device Enable Register turns on a pull-up or pull-down device. The pull device becomes active only if the pin is used as an input or as a wired-or output. 4.4.6 Polarity Select Register The Polarity Select Register selects either a pull-up or pull-down device if enabled. The pull device becomes active only if the pin is used as an input or as a wired-or output. 4.4.7 Pin Configuration Summary The following table summarizes the effect on the various configuration bits, data direction (DDR), output level (I/O), reduced drive (RDR), pull enable (PE), pull select (PS) and interrupt enable (IE) for the ports. The configuration bit PS is used for two purposes: 1. Configure the sensitive interrupt edge (rising or falling), if interrupt is enabled. 2. Select either a pull-up or pull-down device if PE is active. Table 4-43. Pin Configuration Summary DDR 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 IO X X X X X X X 0 1 0 1 0 1 0 1 RDR X X X X X X X 0 0 1 1 0 0 1 1 PE 0 1 1 0 0 1 1 X X X X X X X X PS X 0 1 0 1 0 1 X X X X 0 1 0 1 IE1 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 Function Input Input Input Input Input Input Input Output, full drive to 0 Output, full drive to 1 Output, reduced drive to 0 Output, reduced drive to 1 Output, full drive to 0 Output, full drive to 1 Output, reduced drive to 0 Output, reduced drive to 1 Pull Device Disabled Pull Up Pull Down Disabled Disabled Pull Up Pull Down Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Interrupt Disabled Disabled Disabled Falling edge Rising edge Falling edge Rising edge Disabled Disabled Disabled Disabled Falling edge Rising edge Falling edge Rising edge Applicable only on port P, H, and J. NOTE All bits of all registers in this module are completely synchronous to internal clocks during a register read. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 173 Chapter 4 Port Integration Module (PIM9KG128V1) 4.5 Resets The reset values of all registers are given in the Register Description in Section 4.3, “Memory Map and Register Definition”. 4.5.1 Reset Initialization All registers including the data registers get set/reset asynchronously. Table 4-44 summarizes the port properties after reset initialization. Table 4-44. Port Reset State Summary Reset States Port T S M P H J Data Direction Input Input Input Input Input Input Pull Mode Hi-Z Pull-up Hi-Z Hi-Z Hi-Z Pull-up Reduced Drive Disabled Disabled Disabled Disabled Disabled Disabled Wired-OR Mode N/A Disabled Disabled N/A N/A N/A Interrupt N/A N/A N/A Disabled Disabled Disabled 4.6 4.6.1 Interrupts General Port P, H and J generate a separate edge sensitive interrupt if enabled. Each port offers I/O pins with edge triggered interrupt capability in wired-or fashion. The interrupt enable as well as the sensitivity to rising or falling edges can be individually configured on per pin basis. All bits/pins per port share the same interrupt vector. Interrupts can be used with the pins configured as inputs or outputs. An interrupt is generated when a bit in the port interrupt flag register and its corresponding port interrupt enable bit are both set. This external interrupt feature is capable to wake up the CPU when it is in stop or wait mode. A digital filter on each pin prevents pulses (Figure 4-49) shorter than a specified time from generating an interrupt. The minimum time varies over process conditions, temperature and voltage (Figure 4-50 and Table 4-45). tpulse Figure 4-49. Pulse Illustration MC9S12KG128 Data Sheet, Rev. 1.15 174 Freescale Semiconductor Chapter 4 Port Integration Module (PIM9KG128V1) Glitch, filtered out, no interrupt flag set Valid pulse, interrupt flag set tifmin tifmax Figure 4-50. Interrupt Glitch Filter (PPS = 0) Table 4-45. Pulse Detection Criteria Mode Pulse STOP Unit Ignored Uncertain Valid 1 STOP1 Unit tpulse Scenario 1: OSCCLK recovers prior to exiting Wait Mode. – MCU remains in Wait Mode, – VREG enabled, – PLL enabled, – SCM activated, – Start Clock Quality Check, – Set SCMIF interrupt flag. Some time later OSCCLK recovers. – CM no longer indicates a failure, – 4096 OSCCLK cycles later Clock Quality Check indicates clock o.k., – SCM deactivated, – PLL disabled depending on PLLWAI, – VREG remains enabled (never gets disabled in Wait Mode). – MCU remains in Wait Mode. Some time later either a wakeup interrupt occurs (no SCM interrupt) – Exit Wait Mode using OSCCLK as system clock (SYSCLK), – Continue normal operation. or an External Reset is applied. – Exit Wait Mode using OSCCLK as system clock, – Start reset sequence. Scenario 2: OSCCLK does not recover prior to exiting Wait Mode. – MCU remains in Wait Mode, – VREG enabled, – PLL enabled, – SCM activated, – Start Clock Quality Check, – Set SCMIF interrupt flag, – Keep performing Clock Quality Checks (could continue infinitely) while in Wait Mode. Some time later either a wakeup interrupt occurs (no SCM interrupt) – Exit Wait Mode in SCM using PLL clock (fSCM) as system clock, – Continue to perform additional Clock Quality Checks until OSCCLK is o.k. again. or an External RESET is applied. – Exit Wait Mode in SCM using PLL clock (fSCM) as system clock, – Start reset sequence, – Continue to perform additional Clock Quality Checks until OSCCLK is o.k.again. CRG Actions MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 203 Chapter 5 Clocks and Reset Generator (CRGV4) Table 5-11. Outcome of Clock Loss in Wait Mode (continued) CME 1 SCME 1 SCMIE 1 Clock failure --> – VREG enabled, – PLL enabled, – SCM activated, – Start Clock Quality Check, – SCMIF set. SCMIF generates Self-Clock Mode wakeup interrupt. – Exit Wait Mode in SCM using PLL clock (fSCM) as system clock, – Continue to perform a additional Clock Quality Checks until OSCCLK is o.k. again. CRG Actions 5.4.10 Low-Power Operation in Stop Mode All clocks are stopped in STOP mode, dependent of the setting of the PCE, PRE and PSTP bit. The oscillator is disabled in STOP mode unless the PSTP bit is set. All counters and dividers remain frozen but do not initialize. If the PRE or PCE bits are set, the RTI or COP continues to run in pseudo-stop mode. In addition to disabling system and core clocks the CRG requests other functional units of the MCU (e.g. voltage-regulator) to enter their individual power-saving modes (if available). This is the main difference between pseudo-stop mode and wait mode. After executing the STOP instruction the core requests the CRG to switch the MCU into stop mode. If the PLLSEL bit remains set when entering stop mode, the CRG will switch the system and core clocks to OSCCLK by clearing the PLLSEL bit. Then the CRG disables the PLL, disables the core clock and finally disables the remaining system clocks. As soon as all clocks are switched off, stop mode is active. If pseudo-stop mode (PSTP = 1) is entered from self-clock mode the CRG will continue to check the clock quality until clock check is successful. The PLL and the voltage regulator (VREG) will remain enabled. If full stop mode (PSTP = 0) is entered from self-clock mode an ongoing clock quality check will be stopped. A complete timeout window check will be started when stop mode is exited again. Wake-up from stop mode also depends on the setting of the PSTP bit. MC9S12KG128 Data Sheet, Rev. 1.15 204 Freescale Semiconductor Chapter 5 Clocks and Reset Generator (CRGV4) Core req’s Stop Mode. Clear PLLSEL, Disable PLL Exit Stop w. ext.RESET Wait Mode left due to external Enter Stop Mode no INT ? no PSTP=1 ? yes CME=1 ? no INT ? no yes yes CM fail ? yes no no Clock OK ? Exit Stop w. CMRESET no SCME=1 ? yes yes Exit Stop w. CMRESET yes no SCME=1 ? yes SCMIE=1 ? Generate SCM Interrupt (Wakeup from Stop) no Exit Stop Mode yes Exit Stop Mode SCM=1 ? Exit Stop Mode Exit Stop Mode no yes Enter SCM Enter SCM Enter SCM Continue w. normal OP Figure 5-24. Stop Mode Entry/Exit Sequence 5.4.10.1 Wake-Up from Pseudo-Stop (PSTP=1) Wake-up from pseudo-stop is the same as wake-up from wait mode. There are also three different scenarios for the CRG to restart the MCU from pseudo-stop mode: • • • External reset Clock monitor fail Wake-up interrupt MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 205 Chapter 5 Clocks and Reset Generator (CRGV4) If the MCU gets an external reset during pseudo-stop mode active, the CRG asynchronously restores all configuration bits in the register space to its default settings and starts the reset generator. After completing the reset sequence processing begins by fetching the normal reset vector. Pseudo-stop mode is exited and the MCU is in run mode again. If the clock monitor is enabled (CME = 1) the MCU is able to leave pseudo-stop mode when loss of oscillator/external clock is detected by a clock monitor fail. If the SCME bit is not asserted the CRG generates a clock monitor fail reset (CMRESET). The CRG’s behavior for CMRESET is the same compared to external reset, but another reset vector is fetched after completion of the reset sequence. If the SCME bit is asserted the CRG generates a SCM interrupt if enabled (SCMIE=1). After generating the interrupt the CRG enters self-clock mode and starts the clock quality checker (see Section 5.4.4, “Clock Quality Checker”). Then the MCU continues with normal operation. If the SCM interrupt is blocked by SCMIE = 0, the SCMIF flag will be asserted but the CRG will not wake-up from pseudo-stop mode. If any other interrupt source (e.g. RTI) triggers exit from pseudo-stop mode the MCU immediately continues with normal operation. Because the PLL has been powered-down during stop mode the PLLSEL bit is cleared and the MCU runs on OSCCLK after leaving stop mode. The software must set the PLLSEL bit again, in order to switch system and core clocks to the PLLCLK. Table 5-12 summarizes the outcome of a clock loss while in pseudo-stop mode. MC9S12KG128 Data Sheet, Rev. 1.15 206 Freescale Semiconductor Chapter 5 Clocks and Reset Generator (CRGV4) Table 5-12. Outcome of Clock Loss in Pseudo-Stop Mode CME 0 1 1 SCME X 0 1 SCMIE X X 0 Clock failure --> No action, clock loss not detected. Clock failure --> CRG performs Clock Monitor Reset immediately Clock Monitor failure --> Scenario 1: OSCCLK recovers prior to exiting Pseudo-Stop Mode. – MCU remains in Pseudo-Stop Mode, – VREG enabled, – PLL enabled, – SCM activated, – Start Clock Quality Check, – Set SCMIF interrupt flag. Some time later OSCCLK recovers. – CM no longer indicates a failure, – 4096 OSCCLK cycles later Clock Quality Check indicates clock o.k., – SCM deactivated, – PLL disabled, – VREG disabled. – MCU remains in Pseudo-Stop Mode. Some time later either a wakeup interrupt occurs (no SCM interrupt) – Exit Pseudo-Stop Mode using OSCCLK as system clock (SYSCLK), – Continue normal operation. or an External Reset is applied. – Exit Pseudo-Stop Mode using OSCCLK as system clock, – Start reset sequence. Scenario 2: OSCCLK does not recover prior to exiting Pseudo-Stop Mode. – MCU remains in Pseudo-Stop Mode, – VREG enabled, – PLL enabled, – SCM activated, – Start Clock Quality Check, – Set SCMIF interrupt flag, – Keep performing Clock Quality Checks (could continue infinitely) while in Pseudo-Stop Mode. Some time later either a wakeup interrupt occurs (no SCM interrupt) – Exit Pseudo-Stop Mode in SCM using PLL clock (fSCM) as system clock – Continue to perform additional Clock Quality Checks until OSCCLK is o.k. again. or an External RESET is applied. – Exit Pseudo-Stop Mode in SCM using PLL clock (fSCM) as system clock – Start reset sequence, – Continue to perform additional Clock Quality Checks until OSCCLK is o.k.again. CRG Actions MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 207 Chapter 5 Clocks and Reset Generator (CRGV4) Table 5-12. Outcome of Clock Loss in Pseudo-Stop Mode (continued) CME 1 SCME 1 SCMIE 1 Clock failure --> – VREG enabled, – PLL enabled, – SCM activated, – Start Clock Quality Check, – SCMIF set. SCMIF generates Self-Clock Mode wakeup interrupt. – Exit Pseudo-Stop Mode in SCM using PLL clock (fSCM) as system clock, – Continue to perform a additional Clock Quality Checks until OSCCLK is o.k. again. CRG Actions 5.4.10.2 Wake-up from Full Stop (PSTP=0) The MCU requires an external interrupt or an external reset in order to wake-up from stop mode. If the MCU gets an external reset during full stop mode active, the CRG asynchronously restores all configuration bits in the register space to its default settings and will perform a maximum of 50 clock check_windows (see Section 5.4.4, “Clock Quality Checker”). After completing the clock quality check the CRG starts the reset generator. After completing the reset sequence processing begins by fetching the normal reset vector. Full stop mode is exited and the MCU is in run mode again. If the MCU is woken-up by an interrupt, the CRG will also perform a maximum of 50 clock check_windows (see Section 5.4.4, “Clock Quality Checker”). If the clock quality check is successful, the CRG will release all system and core clocks and will continue with normal operation. If all clock checks within the timeout-window are failing, the CRG will switch to self-clock mode or generate a clock monitor reset (CMRESET) depending on the setting of the SCME bit. Because the PLL has been powered-down during stop mode the PLLSEL bit is cleared and the MCU runs on OSCCLK after leaving stop mode. The software must manually set the PLLSEL bit again, in order to switch system and core clocks to the PLLCLK. NOTE In full stop mode, the clock monitor is disabled and any loss of clock will not be detected. 5.5 Resets This section describes how to reset the CRG and how the CRG itself controls the reset of the MCU. It explains all special reset requirements. Because the reset generator for the MCU is part of the CRG, this section also describes all automatic actions that occur during or as a result of individual reset conditions. The reset values of registers and signals are provided in Section 5.3, “Memory Map and Register MC9S12KG128 Data Sheet, Rev. 1.15 208 Freescale Semiconductor Chapter 5 Clocks and Reset Generator (CRGV4) Definition.” All reset sources are listed in Table 5-13. Refer to the device overview chapter for related vector addresses and priorities. Table 5-13. Reset Summary Reset Source Power-on Reset Low Voltage Reset External Reset Clock Monitor Reset COP Watchdog Reset Local Enable None None None PLLCTL (CME=1, SCME=0) COPCTL (CR[2:0] nonzero) The reset sequence is initiated by any of the following events: • • • • • Low level is detected at the RESET pin (external reset). Power on is detected. Low voltage is detected. COP watchdog times out. Clock monitor failure is detected and self-clock mode was disabled (SCME = 0). Upon detection of any reset event, an internal circuit drives the RESET pin low for 128 SYSCLK cycles (see Figure 5-25). Because entry into reset is asynchronous it does not require a running SYSCLK. However, the internal reset circuit of the CRG cannot sequence out of current reset condition without a running SYSCLK. The number of 128 SYSCLK cycles might be increased by n = 3 to 6 additional SYSCLK cycles depending on the internal synchronization latency. After 128+n SYSCLK cycles the RESET pin is released. The reset generator of the CRG waits for additional 64 SYSCLK cycles and then samples the RESET pin to determine the originating source. Table 5-14 shows which vector will be fetched. Table 5-14. Reset Vector Selection Sampled RESET Pin (64 Cycles After Release) 1 1 1 0 Clock Monitor Reset Pending 0 1 0 X COP Reset Pending 0 X 1 X Vector Fetch POR / LVR / External Reset Clock Monitor Reset COP Reset POR / LVR / External Reset with rise of RESET pin NOTE 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 1 within 64 SYSCLK cycles after the low drive is released. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 209 Chapter 5 Clocks and Reset Generator (CRGV4) The internal reset of the MCU remains asserted while the reset generator completes the 192 SYSCLK long reset sequence. The reset generator circuitry always makes sure the internal reset is deasserted synchronously after completion of the 192 SYSCLK cycles. In case the RESET pin is externally driven low for more than these 192 SYSCLK cycles (external reset), the internal reset remains asserted too. RESET )( )( RESET pin released CRG drives RESET pin low SYSCLK ) ( 128+n cycles possibly SYSCLK not running with n being min 3 / max 6 cycles depending on internal synchronization delay ) ( 64 cycles ) ( possibly RESET driven low externally Figure 5-25. RESET Timing 5.5.1 • • • Clock Monitor Reset Clock monitor is enabled (CME=1) Loss of clock is detected Self-clock mode is disabled (SCME=0) The CRG generates a clock monitor reset in case all of the following conditions are true: The reset event asynchronously forces the configuration registers to their default settings (see Section 5.3, “Memory Map and Register Definition”). In detail the CME and the SCME are reset to logical ‘1’ (which doesn’t change the state of the CME bit, because it has already been set). As a consequence, the CRG immediately enters self-clock mode and starts its internal reset sequence. In parallel the clock quality check starts. As soon as clock quality check indicates a valid oscillator clock the CRG switches to OSCCLK and leaves self-clock mode. Because the clock quality checker is running in parallel to the reset generator, the CRG may leave self-clock mode while completing the internal reset sequence. When the reset sequence is finished the CRG checks the internally latched state of the clock monitor fail circuit. If a clock monitor fail is indicated processing begins by fetching the clock monitor reset vector. 5.5.2 Computer Operating Properly Watchdog (COP) Reset When COP is enabled, the CRG expects sequential write of 0x0055 and 0x00AA (in this order) to the ARMCOP register during the selected time-out period. As soon as this is done, the COP time-out period restarts. If the program fails to do this the CRG will generate a reset. Also, if any value other than 0x0055 or 0x00AA is written, the CRG immediately generates a reset. In case windowed COP operation is enabled MC9S12KG128 Data Sheet, Rev. 1.15 210 Freescale Semiconductor Chapter 5 Clocks and Reset Generator (CRGV4) writes (0x0055 or 0x00AA) to the ARMCOP register must occur in the last 25% of the selected time-out period. A premature write the CRG will immediately generate a reset. As soon as the reset sequence is completed the reset generator checks the reset condition. If no clock monitor failure is indicated and the latched state of the COP timeout is true, processing begins by fetching the COP vector. 5.5.3 Power-On Reset, Low Voltage Reset The on-chip voltage regulator detects when VDD to the MCU has reached a certain level and asserts power-on reset or low voltage reset or both. As soon as a power-on reset or low voltage reset is triggered the CRG performs a quality check on the incoming clock signal. As soon as clock quality check indicates a valid oscillator clock signal the reset sequence starts using the oscillator clock. If after 50 check windows the clock quality check indicated a non-valid oscillator clock the reset sequence starts using self-clock mode. Figure 5-26 and Figure 5-27 show the power-up sequence for cases when the RESET pin is tied to VDD and when the RESET pin is held low. RESET Clock Quality Check (no Self-Clock Mode) )( Internal POR )( 128 SYSCLK Internal RESET )( 64 SYSCLK Figure 5-26. RESET Pin Tied to VDD (by a Pull-Up Resistor) RESET Clock Quality Check (no Self-Clock Mode) )( Internal POR )( 128 SYSCLK Internal RESET )( 64 SYSCLK Figure 5-27. RESET Pin Held Low Externally MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 211 Chapter 5 Clocks and Reset Generator (CRGV4) 5.6 Interrupts The interrupts/reset vectors requested by the CRG are listed in Table 5-15. Refer to the device overview chapter for related vector addresses and priorities. Table 5-15. CRG Interrupt Vectors Interrupt Source Real-time interrupt LOCK interrupt SCM interrupt CCR Mask I bit I bit I bit Local Enable CRGINT (RTIE) CRGINT (LOCKIE) CRGINT (SCMIE) 5.6.1 Real-Time Interrupt The CRG generates a real-time interrupt when the selected interrupt time period elapses. RTI interrupts are locally disabled by setting the RTIE bit to 0. The real-time interrupt flag (RTIF) is set to 1 when a timeout occurs, and is cleared to 0 by writing a 1 to the RTIF bit. The RTI continues to run during pseudo-stop mode if the PRE bit is set to 1. This feature can be used for periodic wakeup from pseudo-stop if the RTI interrupt is enabled. 5.6.2 PLL Lock Interrupt The CRG generates a PLL lock interrupt when the LOCK condition of the PLL has changed, either from a locked state to an unlocked state or vice versa. Lock interrupts are locally disabled by setting the LOCKIE bit to 0. The PLL Lock interrupt flag (LOCKIF) is set to1 when the LOCK condition has changed, and is cleared to 0 by writing a 1 to the LOCKIF bit. 5.6.3 Self-Clock Mode Interrupt The CRG generates a self-clock mode interrupt when the SCM condition of the system has changed, either entered or exited self-clock mode. SCM conditions can only change if the self-clock mode enable bit (SCME) is set to 1. SCM conditions are caused by a failing clock quality check after power-on reset (POR) or low voltage reset (LVR) or recovery from full stop mode (PSTP = 0) or clock monitor failure. For details on the clock quality check refer to Section 5.4.4, “Clock Quality Checker.” If the clock monitor is enabled (CME = 1) a loss of external clock will also cause a SCM condition (SCME = 1). SCM interrupts are locally disabled by setting the SCMIE bit to 0. The SCM interrupt flag (SCMIF) is set to 1 when the SCM condition has changed, and is cleared to 0 by writing a 1 to the SCMIF bit. MC9S12KG128 Data Sheet, Rev. 1.15 212 Freescale Semiconductor Chapter 6 Pierce Oscillator (S12OSCLCPV1) 6.1 Introduction The Pierce oscillator (XOSC) module provides a robust, low-noise and low-power clock source. The module will be operated from the VDDPLL supply rail (2.5 V nominal) and require the minimum number of external components. It is designed for optimal start-up margin with typical crystal oscillators. 6.1.1 Features The XOSC will contain circuitry to dynamically control current gain in the output amplitude. This ensures a signal with low harmonic distortion, low power and good noise immunity. • High noise immunity due to input hysteresis • Low RF emissions with peak-to-peak swing limited dynamically • Transconductance (gm) sized for optimum start-up margin for typical oscillators • Dynamic gain control eliminates the need for external current limiting resistor • Integrated resistor eliminates the need for external bias resistor • Low power consumption: — Operates from 2.5 V (nominal) supply — Amplitude control limits power • Clock monitor 6.1.2 Modes of Operation Two modes of operation exist: 1. Loop controlled Pierce oscillator 2. External square wave mode featuring also full swing Pierce without internal feedback resistor MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 213 Chapter 6 Pierce Oscillator (S12OSCLCPV1) 6.1.3 Block Diagram Figure 6-1 shows a block diagram of the XOSC. Monitor_Failure Clock Monitor OSCCLK Peak Detector Gain Control VDDPLL = 2.5 V Rf EXTAL XTAL Figure 6-1. XOSC Block Diagram 6.2 External Signal Description This section lists and describes the signals that connect off chip 6.2.1 VDDPLL and VSSPLL — Operating and Ground Voltage Pins Theses pins provides operating voltage (VDDPLL) and ground (VSSPLL) for the XOSC circuitry. This allows the supply voltage to the XOSC to be independently bypassed. 6.2.2 EXTAL and XTAL — Input and Output Pins These pins provide the interface for either a crystal or a CMOS compatible clock to control the internal clock generator circuitry. EXTAL is the external clock input or the input to the crystal oscillator amplifier. XTAL is the output of the crystal oscillator amplifier. The MCU internal system clock is derived from the MC9S12KG128 Data Sheet, Rev. 1.15 214 Freescale Semiconductor Chapter 6 Pierce Oscillator (S12OSCLCPV1) EXTAL input frequency. In full stop mode (PSTP = 0), the EXTAL pin is pulled down by an internal resistor of typical 200 kΩ. NOTE Freescale recommends an evaluation of the application board and chosen resonator or crystal by the resonator or crystal supplier. Loop controlled circuit is not suited for overtone resonators and crystals. EXTAL C1 MCU XTAL C2 VSSPLL Crystal or Ceramic Resonator Figure 6-2. Loop Controlled Pierce Oscillator Connections (XCLKS = 0) NOTE Full swing Pierce circuit is not suited for overtone resonators and crystals without a careful component selection. EXTAL C1 MCU RS* XTAL C2 VSSPLL * Rs can be zero (shorted) when use with higher frequency crystals. Refer to manufacturer’s data. RB Crystal or Ceramic Resonator Figure 6-3. Full Swing Pierce Oscillator Connections (XCLKS = 1) EXTAL MCU XTAL CMOS Compatible External Oscillator (VDDPLL Level) Not Connected Figure 6-4. External Clock Connections (XCLKS = 1) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 215 Chapter 6 Pierce Oscillator (S12OSCLCPV1) 6.2.3 XCLKS — Input Signal The XCLKS is an input signal which controls whether a crystal in combination with the internal loop controlled (low power) Pierce oscillator is used or whether full swing Pierce oscillator/external clock circuitry is used. Refer to the Device Overview chapter for polarity and sampling conditions of the XCLKS pin. Table 6-1 lists the state coding of the sampled XCLKS signal. . Table 6-1. Clock Selection Based on XCLKS XCLKS 0 1 Description Loop controlled Pierce oscillator selected Full swing Pierce oscillator/external clock selected 6.3 Memory Map and Register Definition The CRG contains the registers and associated bits for controlling and monitoring the oscillator module. 6.4 Functional Description The XOSC module has control circuitry to maintain the crystal oscillator circuit voltage level to an optimal level which is determined by the amount of hysteresis being used and the maximum oscillation range. The oscillator block has two external pins, EXTAL and XTAL. The oscillator input pin, EXTAL, is intended to be connected to either a crystal or an external clock source. The selection of loop controlled Pierce oscillator or full swing Pierce oscillator/external clock depends on the XCLKS signal which is sampled during reset. The XTAL pin is an output signal that provides crystal circuit feedback. A buffered EXTAL signal becomes the internal clock. To improve noise immunity, the oscillator is powered by the VDDPLL and VSSPLL power supply pins. 6.4.1 Gain Control A closed loop control system will be utilized whereby the amplifier is modulated to keep the output waveform sinusoidal and to limit the oscillation amplitude. The output peak to peak voltage will be kept above twice the maximum hysteresis level of the input buffer. Electrical specification details are provided in the Electrical Characteristics appendix. 6.4.2 Clock Monitor The clock monitor circuit is based on an internal RC time delay so that it can operate without any MCU clocks. If no OSCCLK edges are detected within this RC time delay, the clock monitor indicates failure which asserts self-clock mode or generates a system reset depending on the state of SCME bit. If the clock monitor is disabled or the presence of clocks is detected no failure is indicated.The clock monitor function is enabled/disabled by the CME control bit, described in the CRG block description chapter. MC9S12KG128 Data Sheet, Rev. 1.15 216 Freescale Semiconductor Chapter 6 Pierce Oscillator (S12OSCLCPV1) 6.4.3 Wait Mode Operation During wait mode, XOSC is not impacted. 6.4.4 Stop Mode Operation XOSC is placed in a static state when the part is in stop mode except when pseudo-stop mode is enabled. During pseudo-stop mode, XOSC is not impacted. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 217 Chapter 6 Pierce Oscillator (S12OSCLCPV1) MC9S12KG128 Data Sheet, Rev. 1.15 218 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.1 Introduction The ATD is an 16-channel, 10-bit, multiplexed input successive approximation analog-to-digital converter. Refer to device electrical specifications for ATD accuracy. The block is designed to be upwards compatible with the 68HC11 standard 10/8-bit A/D converter. In addition, there are new operating modes that are unique to the HC12 design. 7.1.1 • • • • • • • • • • • • • • Features 8/10-bit resolution. 7 µs, 10-bit single conversion time. Sample buffer amplifier. Programmable sample time. Left/right justified, signed/unsigned result data. External trigger control. Conversion completion interrupt generation. Analog input multiplexer for 16 analog input channels. Analog/digital input pin multiplexing. 1-to-16 conversion sequence lengths. Continuous conversion mode. Multiple channel scans. Configurable external trigger functionality on any ATD channel. Configurable location for channel wrap around (when converting multiple channels in a sequence). MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 219 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.1.2 Block Diagram ATD BUS CLOCK CLOCK PRESCALER ATD CLOCK CONVERSION COMPLETE INTERRUPT ETRIG (See device specification for availablity) VRH VRL VDDA VSSA AN15 / PAD15 AN14 / PAD14 AN13 / PAD13 AN12 / PAD12 AN11 / PAD11 AN10 / PAD10 AN9 / PAD9 AN8 / PAD8 ANALOG MUX 1 1 – COMPARATOR SAMPLE AND HOLD + SUCCESSIVE APPR0XIMATION REGISTER (SAR) AND DAC MODE AND TIMING CONTROL RESULTS ATD 0 ATD 1 ATD 2 ATD 3 ATD 4 ATD 5 ATD 6 ATD 7 ATD 8 ATD 9 ATD 10 ATD 11 ATD 12 ATD 13 ATD 14 ATD 15 AN7 / PAD7 AN6 / PAD6 AN5 / PAD5 AN4 / PAD4 AN3 / PAD3 AN2 / PAD2 AN1 / PAD1 AN0 / PAD0 ATD INPUT ENABLE REGISTERS PORT AD DATA REGISTERS Figure 7-1. ATD Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 220 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.1.3 7.1.3.1 Modes of Operation Conversion Modes There is software programmable selection between performing single or continuous conversion on a single channel or multiple channels. 7.1.3.2 • MCU Operating Modes • • Stop Mode Entering Stop Mode causes all clocks to halt and thus the system is placed in a minimum power standby mode. This halts any conversion sequence in progress. During recovery from Stop Mode, there must be a minimum delay for the Stop Recovery Time tSR before initiating a new ATD conversion sequence. Wait Mode Entering Wait Mode the ATD conversion either continues or halts for low power depending on the logical value of the AWAIT bit. Freeze Mode In Freeze Mode the ATD will behave according to the logical values of the FRZ1 and FRZ0 bits. This is useful for debugging and emulation. 7.2 Signal Description The ATD has a total of 21 external pins. 7.2.1 7.2.1.1 Detailed Signal Descriptions ANx / PADx (x = 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0) This pin serves as the analog input Channel x. It can also be configured as general purpose digital input and/or external trigger for the ATD conversion. 7.2.1.2 ETRIG This pin can be configured to serve as an external trigger for the ATD conversion. Refer to device specification for availability and connectivity of this pin. 7.2.1.3 VRH, VRL VRH is the high reference voltage, VRL is the low reference voltage for ATD conversion. 7.2.1.4 VDDA, VSSA These pins are the power supplies for the analog circuitry of the ATD10B16C block. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 221 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3 Memory Map and Register Definition This section provides a detailed description of all registers accessible in the ATD. 7.3.1 Module Memory Map Figure 7-2 gives an overview of all ATD registers Address 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 Name ATDCTL0 ATDCTL1 ATDCTL2 ATDCTL3 ATDCTL4 ATDCTL5 ATDSTAT0 R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W = Unimplemented or Reserved IEN15 IEN7 PTAD15 IEN14 IEN6 PTAD14 IEN13 IEN5 PTAD13 IEN12 IEN4 PTAD12 IEN11 IEN3 PTAD11 IEN10 IEN2 PTAD10 IEN9 IEN1 PTAD9 IEN8 IEN0 PTAD8 CCF7 CCF6 CCF5 CCF4 CCF3 CCF2 CCF1 CCF0 CCF15 CCF14 CCF13 CCF12 CCF11 CCF10 CCF9 U U 0 0 0 0 0 U U U U U U U U SRES8 DJM SCF ETRIGSEL ADPU 0 0 0 0 Bit 7 0 6 0 5 0 4 0 3 WRAP3 2 WRAP2 1 WRAP1 Bit 0 WRAP0 ETRIGCH3 ETRIGCH2 ETRIGCH1 ETRIGCH0 ETRIGP S1C PRS3 CD CC3 ETRIGE FIFO PRS2 CC CC2 ASCIE FRZ1 PRS1 CB CC1 ASCIF AFFC S8C SMP1 DSGN 0 AWAI S4C SMP0 SCAN ETORF ETRIGLE S2C PRS4 MULT FIFOR FRZ0 PRS0 CA CC0 0x0007 Unimplemented 0x0008 1 ATDTEST01 ATDTEST0 is intended for factory test purposes only. ATDTEST1 ATDSTAT2 ATDSTAT1 ATDDIEN0 ATDDOEN1 PORTAD0 SC CCF8 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E Figure 7-2. ATD Register Summary (Sheet 1 of 3) MC9S12KG128 Data Sheet, Rev. 1.15 222 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Address 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F 0x0020 0x0021 Name PORTAD1 ATDDR0H ATDDR0L ATDDR1H ATDDR1L ATDDR2H ATDDR2L ATDDR3H ATDDR3L ATDDR4H ATDDR4L ATDDR5H ATDDR5L ATDDR6H ATDDR6L ATDDR7H ATDDR7L ATDDR8H ATDDR8L R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 PTAD7 6 PTAD6 5 PTAD5 4 PTAD4 3 PTAD3 2 PTAD2 1 PTAD1 Bit 0 PTAD0 See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” = Unimplemented or Reserved Figure 7-2. ATD Register Summary (Sheet 2 of 3) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 223 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Address 0x0022 0x0023 0x0024 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B 0x002C 0x002D 0x002E 0x002F Name ATDDR9H ATDDR9L ATDDR10H ATDDR10L ATDDR11H ATDDR11L ATDDR12H ATDDR12L ATDDR13H ATDDR13L ATDDR14H ATDDR14L ATDDR15H ATDDR15L R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 6 5 4 3 2 1 Bit 0 See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” See Section 7.3.2.16.1, “Left Justified Result Data” and Section 7.3.2.16.2, “Right Justified Result Data” = Unimplemented or Reserved Figure 7-2. ATD Register Summary (Sheet 3 of 3) NOTE Register Address = Base Address + Address Offset, where the Base Address is defined at the MCU level and the Address Offset is defined at the module level. MC9S12KG128 Data Sheet, Rev. 1.15 224 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2 Register Descriptions This section describes in address order all the ATD registers and their individual bits. 7.3.2.1 ATD Control Register 0 (ATDCTL0) Writes to this register will abort current conversion sequence but will not start a new sequence. Module Base + 0x0000 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 WRAP3 1 WRAP2 1 WRAP1 1 WRAP0 1 = Unimplemented or Reserved Figure 7-3. ATD Control Register 0 (ATDCTL0) Read: Anytime Write: Anytime Table 7-1. ATDCTL0 Field Descriptions Field 3–0 WRAP[3:0] Description Wrap Around Channel Select Bits — These bits determine the channel for wrap around when doing multi-channel conversions. The coding is summarized in Table 7-2. Table 7-2. Multi-Channel Wrap Around Coding WRAP3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 WRAP2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 WRAP1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 WRAP0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Multiple Channel Conversions (MULT = 1) Wrap Around to AN0/PAD0 After Converting Reserved AN1 / PAD1 AN2 / PAD2 AN3 / PAD3 AN4 / PAD4 AN5 / PAD5 AN6 / PAD6 AN7 / PAD7 AN8 / PAD8 AN9 / PAD9 AN10 / PAD10 AN11 / PAD11 AN12 / PAD12 AN13 / PAD13 AN14 / PAD14 AN15 / PAD15 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 225 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.2 ATD Control Register 1 (ATDCTL1) Writes to this register will abort current conversion sequence but will not start a new sequence. Module Base + 0x0001 7 6 5 4 3 2 1 0 R W Reset ETRIGSEL 0 0 0 0 0 0 0 ETRIGCH3 1 ETRIGCH2 1 ETRIGCH1 1 ETRIGCH0 1 = Unimplemented or Reserved Figure 7-4. ATD Control Register 1 (ATDCTL1) Read: Anytime Write: Anytime Table 7-3. ATDCTL1 Field Descriptions Field 7 ETRIGSEL Description External Trigger Source Select — This bit selects the external trigger source to be either one of the AD channels or a specific port pin ETRIG. See device specification for availability and connectivity of ETRIG pin. If ETRIG pin option is not available, writing a 1 to ETRISEL only sets the bit but has not effect, that means still one of the AD channels (selected by ETRIGCH3-0) is the source for external trigger. 0 External Trigger source is the AD channel selected by ETRIGCH3-0 (see Table 7-4). 1 External trigger source is ETRIG pin. 3–0 External Trigger Channel Select — If ETRIGSEL = 0 then these bits select one of the AD channels as the ETRIGCH[3:0] source for external trigger. The coding is summarized Table 7-4. Table 7-4. External Trigger Channel Select Coding ETRIGSEL 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 ETRIGCH3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 X ETRIGCH2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 X ETRIGCH1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 X ETRIGCH0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 X External Trigger Source AN0 / PAD0 AN1 / PAD1 AN2 / PAD2 AN3 / PAD3 AN4 / PAD4 AN5 / PAD5 AN6 / PAD6 AN7 / PAD7 AN8 / PAD8 AN9 / PAD9 AN10 / PAD10 AN11 / PAD11 AN12 / PAD12 AN13 / PAD13 AN14 / PAD14 AN15 / PAD15 ETRIG1 Only if ETRIG pin option available (see device specification), else external trigger source is still on one of the AD channels selected by ETRIGCH3–0 MC9S12KG128 Data Sheet, Rev. 1.15 226 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.3 ATD Control Register 2 (ATDCTL2) This register controls power down, interrupt and external trigger. Writes to this register will abort current conversion sequence but will not start a new sequence. Module Base + 0x0002 7 6 5 4 3 2 1 0 R ADPU W Reset 0 0 0 0 0 0 0 AFFC AWAI ETRIGLE ETRIGP ETRIGE ASCIE ASCIF 0 = Unimplemented or Reserved Figure 7-5. ATD Control Register 2 (ATDCTL2) Read: Anytime Write: Anytime Table 7-5. ATDCTL2 Field Descriptions Field 7 ADPU Description ATD Power Down — This bit provides on/off control over the ATD block allowing reduced MCU power consumption. Because analog electronic is turned off when powered down, the ATD requires a recovery time period after ADPU bit is enabled. 0 Power down ATD 1 Normal ATD functionality ATD Fast Flag Clear All 0 ATD flag clearing operates normally (read the status register ATDSTAT1 before reading the result register to clear the associate CCF flag). 1 Changes all ATD conversion complete flags to a fast clear sequence. Any access to a result register will cause the associate CCF flag to clear automatically. ATD Power Down in Wait Mode — When entering Wait Mode this bit provides on/off control over the ATD block allowing reduced MCU power. Because analog electronic is turned off when powered down, the ATD requires a recovery time period after exit from Wait mode. 0 ATD continues to run in Wait mode 1 Halt conversion and power down ATD during Wait mode After exiting Wait mode with an interrupt conversion will resume. But due to the recovery time the result of this conversion should be ignored. External Trigger Level/Edge Control — This bit controls the sensitivity of the external trigger signal. See Table 7-6 for details. External Trigger Polarity — This bit controls the polarity of the external trigger signal. See Table 7-6 for details. External Trigger Mode Enable — This bit enables the external trigger on ETRIG pin or one of the ATD channels as described in Table 7-4. If external trigger source is one the ATD channels, the digital input buffer of this channel is enabled. The external trigger allows to synchronize sample and ATD conversions processes with external events. 0 Disable external trigger 1 Enable external trigger Note: If using one of the ATD channel as external trigger (ETRIGSEL = 0) the conversion results for this channel have no meaning while external trigger mode is enabled. 6 AFFC 5 AWAI 4 ETRIGLE 3 ETRIGP 2 ETRIGE MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 227 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Table 7-5. ATDCTL2 Field Descriptions (continued) Field 1 ASCIE 0 ASCIF Description ATD Sequence Complete Interrupt Enable 0 ATD Sequence Complete interrupt requests are disabled. 1 ATD Interrupt will be requested whenever ASCIF = 1 is set. ATD Sequence Complete Interrupt Flag — If ASCIE = 1 the ASCIF flag equals the SCF flag (see Section 7.3.2.7, “ATD Status Register 0 (ATDSTAT0)”), else ASCIF reads zero. Writes have no effect. 0 No ATD interrupt occurred 1 ATD sequence complete interrupt pending Table 7-6. External Trigger Configurations ETRIGLE 0 0 1 1 ETRIGP 0 1 0 1 External Trigger Sensitivity Falling edge Rising edge Low level High level 7.3.2.4 ATD Control Register 3 (ATDCTL3) This register controls the conversion sequence length, FIFO for results registers and behavior in Freeze Mode. Writes to this register will abort current conversion sequence but will not start a new sequence. Module Base + 0x0003 7 6 5 4 3 2 1 0 R W Reset 0 0 S8C 0 S4C 1 S2C 0 S1C 0 FIFO 0 FRZ1 0 FRZ0 0 = Unimplemented or Reserved Figure 7-6. ATD Control Register 3 (ATDCTL3) Read: Anytime Write: Anytime Table 7-7. ATDCTL3 Field Descriptions Field 6–3 S8C, S4C, S2C, S1C Description Conversion Sequence Length — These bits control the number of conversions per sequence. Table 7-8 shows all combinations. At reset, S4C is set to 1 (sequence length is 4). This is to maintain software continuity to HC12 Family. MC9S12KG128 Data Sheet, Rev. 1.15 228 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Table 7-7. ATDCTL3 Field Descriptions (continued) Field 2 FIFO Description Result Register FIFO Mode — If this bit is zero (non-FIFO mode), 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. If this bit is one (FIFO mode) the conversion 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 current conversion result will be placed. 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. 0 Conversion results are placed in the corresponding result register up to the selected sequence length. 1 Conversion results are placed in consecutive result registers (wrap around at end). Background Debug Freeze Enable — When debugging an application, it is useful in many cases to have the ATD pause when a breakpoint (Freeze Mode) is encountered. These 2 bits determine how the ATD will respond to a breakpoint as shown in Table 7-9. Leakage onto the storage node and comparator reference capacitors may compromise the accuracy of an immediately frozen conversion depending on the length of the freeze period. 1–0 FRZ[1:0] Table 7-8. Conversion Sequence Length Coding S8C 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 S4C 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 S2C 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 S1C 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Number of Conversions per Sequence 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Table 7-9. ATD Behavior in Freeze Mode (Breakpoint) FRZ1 0 0 1 1 FRZ0 0 1 0 1 Behavior in Freeze Mode Continue conversion Reserved Finish current conversion, then freeze Freeze Immediately MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 229 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.5 ATD Control Register 4 (ATDCTL4) This register selects the conversion clock frequency, the length of the second phase of the sample time and the resolution of the A/D conversion (i.e., 8-bits or 10-bits). Writes to this register will abort current conversion sequence but will not start a new sequence. Module Base + 0x0004 7 6 5 4 3 2 1 0 R SRES8 W Reset 0 0 0 0 0 1 0 1 SMP1 SMP0 PRS4 PRS3 PRS2 PRS1 PRS0 Figure 7-7. ATD Control Register 4 (ATDCTL4) Read: Anytime Write: Anytime Table 7-10. ATDCTL4 Field Descriptions Field 7 SRES8 Description A/D Resolution Select — This bit selects the resolution of A/D conversion results as either 8 or 10 bits. The A/D converter has an accuracy of 10 bits. However, if low resolution is required, the conversion can be speeded up by selecting 8-bit resolution. 0 10-bit resolution 1 8-bit resolution Sample Time Select — These two bits select the length of the second phase of the sample time in units of ATD conversion clock cycles. Note that the ATD conversion clock period is itself a function of the prescaler value (bits PRS4–0). The sample time consists of two phases. The first phase is two ATD conversion clock cycles long and transfers the sample quickly (via the buffer amplifier) onto the A/D machine’s storage node. The second phase attaches the external analog signal directly to the storage node for final charging and high accuracy. Table 7-11 lists the lengths available for the second sample phase. ATD Clock Prescaler —These 5 bits are the binary value prescaler value PRS. The ATD conversion clock frequency is calculated as follows: [ BusClock ] ATDclock = ------------------------------- × 0.5 [ PRS + 1 ] Note: The maximum ATD conversion clock frequency is half the Bus Clock. The default (after reset) prescaler value is 5 which results in a default ATD conversion clock frequency that is Bus Clock divided by 12. Table 7-12 illustrates the divide-by operation and the appropriate range of the Bus Clock. 6–5 SMP[1:0] 4–0 PRS[4:0] Table 7-11. Sample Time Select SMP1 0 0 1 1 SMP0 0 1 0 1 Length of 2nd Phase of Sample Time 2 A/D conversion clock periods 4 A/D conversion clock periods 8 A/D conversion clock periods 16 A/D conversion clock periods MC9S12KG128 Data Sheet, Rev. 1.15 230 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Table 7-12. Clock Prescaler Values Prescale Value 00000 00001 00010 00011 00100 00101 00110 00111 01000 01001 01010 01011 01100 01101 01110 01111 10000 10001 10010 10011 10100 10101 10110 10111 11000 11001 11010 11011 11100 11101 11110 11111 1 Total Divisor Value divide by 2 divide by 4 divide by 6 divide by 8 divide by 10 divide by 12 divide by 14 divide by 16 divide by 18 divide by 20 divide by 22 divide by 24 divide by 26 divide by 28 divide by 30 divide by 32 divide by 34 divide by 36 divide by 38 divide by 40 divide by 42 divide by 44 divide by 46 divide by 48 divide by 50 divide by 52 divide by 54 divide by 56 divide by 58 divide by 60 divide by 62 divide by 64 Maximum Bus Clock1 4 MHz 8 MHz 12 MHz 16 MHz 20 MHz 24 MHz 28 MHz 32 MHz 36 MHz 40 MHz 44 MHz 48 MHz 52 MHz 56 MHz 60 MHz 64 MHz 68 MHz 72 MHz 76 MHz 80 MHz 84 MHz 88 MHz 92 MHz 96 MHz 100 MHz 104 MHz 108 MHz 112 MHz 116 MHz 120 MHz 124 MHz 128 MHz Minimum Bus Clock2 1 MHz 2 MHz 3 MHz 4 MHz 5 MHz 6 MHz 7 MHz 8 MHz 9 MHz 10 MHz 11 MHz 12 MHz 13 MHz 14 MHz 15 MHz 16 MHz 17 MHz 18 MHz 19 MHz 20 MHz 21 MHz 22 MHz 23 MHz 24 MHz 25 MHz 26 MHz 27 MHz 28 MHz 29 MHz 30 MHz 31 MHz 32 MHz Maximum ATD conversion clock frequency is 2 MHz. The maximum allowed bus clock frequency is shown in this column. 2 Minimum ATD conversion clock frequency is 500 kHz. The minimum allowed bus clock frequency is shown in this column. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 231 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.6 ATD Control Register 5 (ATDCTL5) This register selects the type of conversion sequence and the analog input channels sampled. Writes to this register will abort current conversion sequence and start a new conversion sequence. Module Base + 0x0005 7 6 5 4 3 2 1 0 R DJM W Reset 0 0 0 0 0 0 0 0 DSGN SCAN MULT CD CC CB CA Figure 7-8. ATD Control Register 5 (ATDCTL5) Read: Anytime Write: Anytime Table 7-13. ATDCTL5 Field Descriptions Field 7 DJM Description Result Register Data Justification — This bit controls justification of conversion data in the result registers. See Section 7.3.2.16, “ATD Conversion Result Registers (ATDDRx)” for details. 0 Left justified data in the result registers. 1 Right justified data in the result registers. Result Register Data Signed or Unsigned Representation — This bit selects between signed and unsigned conversion data representation in the result registers. Signed data is represented as 2’s complement. Signed data is not available in right justification. See Section 7.3.2.16, “ATD Conversion Result Registers (ATDDRx)” for details. 0 Unsigned data representation in the result registers. 1 Signed data representation in the result registers. Table 7-14summarizes the result data formats available and how they are set up using the control bits. Table 7-15 illustrates the difference between the signed and unsigned, left justified output codes for an input signal range between 0 and 5.12 Volts. Continuous Conversion Sequence Mode — This bit selects whether conversion sequences are performed continuously or only once. 0 Single conversion sequence 1 Continuous conversion sequences (scan mode) Multi-Channel Sample Mode — When MULT is 0, the ATD sequence controller samples only from the specified analog input channel for an entire conversion sequence. The analog channel is selected by channel selection code (control bits CC/CB/CA located in ATDCTL5). When MULT is 1, the ATD sequence controller samples across channels. The number of channels sampled is determined by the sequence length value (S8C, S4C, S2C, S1C). The first analog channel examined is determined by channel selection code (CC, CB, CA control bits); subsequent channels sampled in the sequence are determined by incrementing the channel selection code or wrapping around to AN0 (channel 0. 0 Sample only one channel 1 Sample across several channels 6 DSGN 5 SCAN 4 MULT MC9S12KG128 Data Sheet, Rev. 1.15 232 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Table 7-13. ATDCTL5 Field Descriptions (continued) Field 3–0 CD, CC, CB, CA Description Analog Input Channel Select Code — These bits select the analog input channel(s) whose signals are sampled and converted to digital codes. Table 7-16 lists the coding used to select the various analog input channels. In the case of single channel conversions (MULT = 0), this selection code specified the channel to be examined. In the case of multiple channel conversions (MULT = 1), this selection code represents the first channel to be examined in the conversion sequence. Subsequent channels are determined by incrementing the channel selection code or wrapping around to AN0 (after converting the channel defined by the Wrap Around Channel Select Bits WRAP3-0 in ATDCTL0). In case starting with a channel number higher than the one defined by WRAP3–0 the first wrap around will be AN15 to AN0. Table 7-14. Available Result Data Formats SRES8 1 1 1 0 0 0 DJM 0 0 1 0 0 1 DSGN 0 1 X 0 1 X Result Data Formats Description and Bus Bit Mapping 8-bit / left justified / unsigned — bits 8–15 8-bit / left justified / signed — bits 8–15 8-bit / right justified / unsigned — bits 0–7 10-bit / left justified / unsigned — bits 6–15 10-bit / left justified / signed — bits 6–15 10-bit / right justified / unsigned — bits 0–9 Table 7-15. Left Justified, Signed and Unsigned ATD Output Codes Input Signal Vrl = 0 Volts Vrh = 5.12 Volts 5.120 Volts 5.100 Volts 5.080 Volts 2.580 Volts 2.560 Volts 2.540 Volts 0.020 Volts 0.000 Volts Signed 8-Bit Codes 7F 7F 7E 01 00 FF 81 80 Unsigned 8-Bit Codes FF FF FE 81 80 7F 01 00 Signed 10-Bit Codes 7FC0 7F00 7E00 0100 0000 FF00 8100 8000 Unsigned 10-Bit Codes FFC0 FF00 FE00 8100 8000 7F00 0100 0000 Table 7-16. Analog Input Channel Select Coding CD 0 0 0 0 0 0 CC 0 0 0 0 1 1 CB 0 0 1 1 0 0 CA 0 1 0 1 0 1 Analog Input Channel AN0 AN1 AN2 AN3 AN4 AN5 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 233 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Table 7-16. Analog Input Channel Select Coding (continued) CD 0 0 1 1 1 1 1 1 1 1 CC 1 1 0 0 0 0 1 1 1 1 CB 1 1 0 0 1 1 0 0 1 1 CA 0 1 0 1 0 1 0 1 0 1 Analog Input Channel AN6 AN7 AN8 AN9 AN10 AN11 AN12 AN13 AN14 AN15 7.3.2.7 ATD Status Register 0 (ATDSTAT0) This read-only register contains the Sequence Complete Flag, overrun flags for external trigger and FIFO mode, and the conversion counter. Module Base + 0x0006 7 6 5 4 3 2 1 0 R SCF W Reset 0 0 ETORF 0 0 FIFOR 0 CC3 CC2 CC1 CC0 0 0 0 0 = Unimplemented or Reserved Figure 7-9. ATD Status Register 0 (ATDSTAT0) Read: Anytime Write: Anytime (No effect on CC3, CC2, CC1, CC0) Table 7-17. ATDSTAT0 Field Descriptions Field 7 SCF Description Sequence Complete Flag — This flag is set upon completion of a conversion sequence. If conversion sequences are continuously performed (SCAN = 1), the flag is set after each one is completed. This flag is cleared when one of the following occurs: A) Write “1” to SCF B) Write to ATDCTL5 (a new conversion sequence is started) C) If AFFC = 1 and read of a result register 0 Conversion sequence not completed 1 Conversion sequence has completed MC9S12KG128 Data Sheet, Rev. 1.15 234 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) Table 7-17. ATDSTAT0 Field Descriptions (continued) Field 5 ETORF Description External Trigger Overrun Flag — While in edge trigger mode (ETRIGLE = 0), if additional active edges are detected while a conversion sequence is in process the overrun flag is set. This flag is cleared when one of the following occurs: A) Write “1” to ETORF B) Write to ATDCTL0,1,2,3,4 (a conversion sequence is aborted) C) Write to ATDCTL5 (a new conversion sequence is started) 0 No External trigger over run error has occurred 1 External trigger over run error has occurred FIFO Over Run Flag — This bit indicates that a result register has been written to before its associated conversion complete flag (CCF) has been cleared. This flag is most useful when using the FIFO mode because the flag potentially indicates that result registers are out of sync with the input channels. However, it is also practical for non-FIFO modes, and indicates that a result register has been over written before it has been read (i.e., the old data has been lost). This flag is cleared when one of the following occurs: A) Write “1” to FIFOR B) Start a new conversion sequence (write to ATDCTL5 or external trigger) 0 No over run has occurred 1 Overrun condition exists (result register has been written while associated CCFx flag was still set) Conversion Counter — These 4 read-only bits are the binary value of the conversion counter. The conversion counter points to the result register that will receive the result of the current conversion. E.g. CC3 = 0, CC2 = 1, CC1 = 1, CC0 = 0 indicates that the result of the current conversion will be in ATD Result Register 6. If in non-FIFO mode (FIFO = 0) the conversion counter is initialized to zero at the begin and end of the conversion sequence. If in FIFO mode (FIFO = 1) the register counter is not initialized. The conversion counters wraps around when its maximum value is reached. 4 FIFOR 3–0 CC[3:0] 7.3.2.8 Reserved Register (ATDTEST0) Module Base + 0x0008 7 6 5 4 3 2 1 0 R W Reset U U U U U U U U 1 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 7-10. Reserved Register (ATDTEST0) Read: Anytime, returns unpredictable values Write: Anytime in special modes, unimplemented in normal modes NOTE Writing to this registers when in special modes can alter functionality. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 235 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.9 ATD Test Register 1 (ATDTEST1) This register contains the SC bit used to enable special channel conversions. Module Base + 0x0009 7 6 5 4 3 2 1 0 R W Reset U U 0 0 0 0 0 SC 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 7-11. ATD Test Register 1 (ATDTEST1) Read: Anytime, returns unpredictable values for Bit7 and Bit6 Write: Anytime NOTE Writing to this registers when in special modes can alter functionality. Table 7-18. ATDTEST1 Field Descriptions Field 0 SC Description Special Channel Conversion Bit — If this bit is set, then special channel conversion can be selected using CC, CB and CA of ATDCTL5. Table 7-19 lists the coding. 0 Special channel conversions disabled 1 Special channel conversions enabled Table 7-19. Special Channel Select Coding SC 1 1 1 1 1 1 CD 0 0 0 0 0 1 CC 0 1 1 1 1 X CB X 0 0 1 1 X CA X 0 1 0 1 X Analog Input Channel Reserved VRH VRL (VRH+VRL) / 2 Reserved Reserved MC9S12KG128 Data Sheet, Rev. 1.15 236 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.10 ATD Status Register 2 (ATDSTAT2) This read-only register contains the Conversion Complete Flags CCF15 to CCF8. Module Base + 0x000A 7 6 5 4 3 2 1 0 R W Reset CCF15 CCF14 CCF13 CCF12 CCF11 CCF10 CCF9 CCF8 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 7-12. ATD Status Register 2 (ATDSTAT2) Read: Anytime Write: Anytime, no effect Table 7-20. ATDSTAT2 Field Descriptions Field 7–0 CCF[15:8] Description Conversion Complete Flag x (x = 15, 14, 13, 12, 11, 10, 9, 8) — A conversion complete flag is set at the end of each conversion in a conversion sequence. The flags are associated with the conversion position in a sequence (and also the result register number). Therefore, CCF8 is set when the ninth conversion in a sequence is complete and the result is available in result register ATDDR8; CCF9 is set when the tenth conversion in a sequence is complete and the result is available in ATDDR9, and so forth. A flag CCFx (x = 15, 14, 13, 12, 11, 10, 9, 8) is cleared when one of the following occurs: A) Write to ATDCTL5 (a new conversion sequence is started) B) If AFFC = 0 and read of ATDSTAT2 followed by read of result register ATDDRx C) If AFFC = 1 and read of result register ATDDRx 0 Conversion number x not completed 1 Conversion number x has completed, result ready in ATDDRx MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 237 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.11 ATD Status Register 1 (ATDSTAT1) This read-only register contains the Conversion Complete Flags CCF7 to CCF0. Module Base + 0x000B 7 6 5 4 3 2 1 0 R W Reset CCF7 CCF6 CCF5 CCF4 CCF3 CCF2 CCF1 CCF0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 7-13. ATD Status Register 1 (ATDSTAT1) Read: Anytime Write: Anytime, no effect Table 7-21. ATDSTAT1 Field Descriptions Field 7–0 CCF[7:0] Description Conversion Complete Flag x (x = 7, 6, 5, 4, 3, 2, 1, 0) — A conversion complete flag is set at the end of each conversion in a conversion sequence. The flags are associated with the conversion position in a sequence (and also the result register number). Therefore, CCF0 is set when the first conversion in a sequence is complete and the result is available in result register ATDDR0; CCF1 is set when the second conversion in a sequence is complete and the result is available in ATDDR1, and so forth. A flag CCFx (x = 7, 6, 5, 4, 3, 2, 1, 0) is cleared when one of the following occurs: A) Write to ATDCTL5 (a new conversion sequence is started) B) If AFFC=0 and read of ATDSTAT1 followed by read of result register ATDDRx C) If AFFC=1 and read of result register ATDDRx 0 Conversion number x not completed 1 Conversion number x has completed, result ready in ATDDRx MC9S12KG128 Data Sheet, Rev. 1.15 238 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.12 ATD Input Enable Register 0 (ATDDIEN0) Module Base + 0x000C 7 6 5 4 3 2 1 0 R IEN15 W Reset 0 0 0 0 0 0 0 0 IEN14 IEN13 IEN12 IEN11 IEN10 IEN9 IEN8 Figure 7-14. Input Enable Register 0 (ATDDIEN0) Read: Anytime Write: Anytime Table 7-22. ATDDIEN0 Field Descriptions Field 7–0 IEN[15:0] Description ATD Digital Input Enable on Channel x (x = 15, 14, 13, 12, 11, 10, 9, 8) — This bit controls the digital input buffer from the analog input pin (ANx) to PTADx data register. 0 Disable digital input buffer to PTADx 1 Enable digital input buffer to PTADx. Note: Setting this bit will enable the corresponding digital input buffer continuously. If this bit is set while simultaneously using it as an analog port, there is potentially increased power consumption because the digital input buffer maybe in the linear region. 7.3.2.13 ATD Input Enable Register 1 (ATDDIEN1) Module Base + 0x000D 7 6 5 4 3 2 1 0 R IEN7 W Reset 0 0 0 0 0 0 0 0 IEN6 IEN5 IEN4 IEN3 IEN2 IEN1 IEN0 Figure 7-15. Input Enable Register 1 (ATDDIEN1) Read: Anytime Write: Anytime Table 7-23. ATDDIEN1 Field Descriptions Field 7–0 IEN[7:0] Description ATD Digital Input Enable on Channel x (x = 7, 6, 5, 4, 3, 2, 1, 0) — This bit controls the digital input buffer from the analog input pin (ANx) to PTADx data register. 0 Disable digital input buffer to PTADx 1 Enable digital input buffer to PTADx. Note: Setting this bit will enable the corresponding digital input buffer continuously. If this bit is set while simultaneously using it as an analog port, there is potentially increased power consumption because the digital input buffer maybe in the linear region. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 239 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.14 Port Data Register 0 (PORTAD0) The data port associated with the ATD is input-only. The port pins are shared with the analog A/D inputs AN15-8. Read: Anytime Write: Anytime, no effect Module Base + 0x000E 7 6 5 4 3 2 1 0 R W Reset Pin Function PTAD15 PTAD14 PTAD13 PTAD12 PTAD11 PTAD10 PTAD9 PTAD8 1 AN 15 1 AN14 1 AN13 1 AN12 1 AN11 1 AN10 1 AN9 1 AN8 = Unimplemented or Reserved Figure 7-16. Port Data Register 0 (PORTAD0) The A/D input channels may be used for general-purpose digital input. Table 7-24. PORTAD0 Field Descriptions Field 7–0 PTAD[15:0] Description A/D Channel x (ANx) Digital Input (x = 15, 14, 13, 12, 11, 10, 9, 8) — If the digital input buffer on the ANx pin is enabled (IENx = 1) or channel x is enabled as external trigger (ETRIGE = 1, ETRICH[3-0] = x, ETRIGSEL = 0) read returns the logic level on ANx pin (signal potentials not meeting VIL or VIH specifications will have an indeterminate value)). If the digital input buffers are disabled (IENx = 0) and channel x is not enabled as external trigger, read returns a “1”. Reset sets all PORTAD0 bits to “1”. MC9S12KG128 Data Sheet, Rev. 1.15 240 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.15 Port Data Register 1 (PORTAD1) The data port associated with the ATD is input-only. The port pins are shared with the analog A/D inputs AN7-0. Read: Anytime Write: Anytime, no effect Module Base + 0x000F 7 6 5 4 3 2 1 0 R W Reset Pin Function PTAD7 PTAD6 PTAD5 PTAD4 PTAD3 PTAD2 PTAD1 PTAD0 1 AN 7 1 AN6 1 AN5 1 AN4 1 AN3 1 AN2 1 AN1 1 AN0 = Unimplemented or Reserved Figure 7-17. Port Data Register 1 (PORTAD1) The A/D input channels may be used for general purpose digital input. Table 7-25. PORTAD1 Field Descriptions Field 7–0 PTAD[7:0] Description A/D Channel x (ANx) Digital Input (x = 7, 6, 5, 4, 3, 2, 1, 0) — If the digital input buffer on the ANx pin is enabled (IENx = 1) or channel x is enabled as external trigger (ETRIGE = 1, ETRICH[3-0] = x, ETRIGSEL = 0) read returns the logic level on ANx pin (signal potentials not meeting VIL or VIH specifications will have an indeterminate value)). If the digital input buffers are disabled (IENx = 0) and channel x is not enabled as external trigger, read returns a “1”. Reset sets all PORTAD1 bits to “1”. 7.3.2.16 ATD Conversion Result Registers (ATDDRx) The A/D conversion results are stored in 16 read-only result registers. The result data is formatted in the result registers bases on two criteria. First there is left and right justification; this selection is made using the DJM control bit in ATDCTL5. Second there is signed and unsigned data; this selection is made using the DSGN control bit in ATDCTL5. Signed data is stored in 2’s complement format and only exists in left justified format. Signed data selected for right justified format is ignored. Read: Anytime Write: Anytime in special mode, unimplemented in normal modes MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 241 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.3.2.16.1 Left Justified Result Data Module Base + 0x0010 = ATDDR0H, 0x0012 = ATDDR1H, 0x0014 = ATDDR2H, 0x0016 = ATDDR3H 0x0018 = ATDDR4H, 0x001A = ATDDR5H, 0x001C = ATDDR6H, 0x001E = ATDDR7H 0x0020 = ATDDR8H, 0x0022 = ATDDR9H, 0x0024 = ATDDR10H, 0x0026 = ATDDR11H 0x0028 = ATDDR12H, 0x002A = ATDDR13H, 0x002C = ATDDR14H, 0x002E = ATDDR15H 7 6 5 4 3 2 1 0 R BIT 9 MSB W BIT 7 MSB Reset 0 BIT 8 BIT 6 0 BIT 7 BIT 5 0 BIT 6 BIT 4 0 BIT 5 BIT 3 0 BIT 4 BIT 2 0 BIT 3 BIT 1 0 BIT 2 BIT 0 0 10-bit data 8-bit data Figure 7-18. Left Justified, ATD Conversion Result Register, High Byte (ATDDRxH) Module Base + 0x0011 = ATDDR0L, 0x0013 = ATDDR1L, 0x0015 = ATDDR2L, 0x0017 = ATDDR3L 0x0019 = ATDDR4L, 0x001B = ATDDR5L, 0x001D = ATDDR6L, 0x001F = ATDDR7L 0x0021 = ATDDR8L, 0x0023 = ATDDR9L, 0x0025 = ATDDR10L, 0x0027 = ATDDR11L 0x0029 = ATDDR12L, 0x002B = ATDDR13L, 0x002D = ATDDR14L, 0x002F = ATDDR15L 7 6 5 4 3 2 1 0 R W Reset BIT 1 U 0 BIT 0 U 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10-bit data 8-bit data Figure 7-19. Left Justified, ATD Conversion Result Register, Low Byte (ATDDRxL) 7.3.2.16.2 Right Justified Result Data Module Base + 0x0010 = ATDDR0H, 0x0012 = ATDDR1H, 0x0014 = ATDDR2H, 0x0016 = ATDDR3H 0x0018 = ATDDR4H, 0x001A = ATDDR5H, 0x001C = ATDDR6H, 0x001E = ATDDR7H 0x0020 = ATDDR8H, 0x0022 = ATDDR9H, 0x0024 = ATDDR10H, 0x0026 = ATDDR11H 0x0028 = ATDDR12H, 0x002A = ATDDR13H, 0x002C = ATDDR14H, 0x002E = ATDDR15H 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 BIT 9 MSB 0 0 BIT 8 0 0 10-bit data 8-bit data Figure 7-20. Right Justified, ATD Conversion Result Register, High Byte (ATDDRxH) Module Base + 0x0011 = ATDDR0L, 0x0013 = ATDDR1L, 0x0015 = ATDDR2L, 0x0017 = ATDDR3L 0x0019 = ATDDR4L, 0x001B = ATDDR5L, 0x001D = ATDDR6L, 0x001F = ATDDR7L 0x0021 = ATDDR8L, 0x0023 = ATDDR9L, 0x0025 = ATDDR10L, 0x0027 = ATDDR11L 0x0029 = ATDDR12L, 0x002B = ATDDR13L, 0x002D = ATDDR14L, 0x002F = ATDDR15L 7 6 5 4 3 2 1 0 R BIT 7 W BIT 7 MSB Reset 0 BIT 6 BIT 6 0 BIT 5 BIT 5 0 BIT 4 BIT 4 0 BIT 3 BIT 3 0 BIT 2 BIT 2 0 BIT 1 BIT 1 0 BIT 0 BIT 0 0 10-bit data 8-bit data Figure 7-21. Right Justified, ATD Conversion Result Register, Low Byte (ATDDRxL) MC9S12KG128 Data Sheet, Rev. 1.15 242 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.4 Functional Description The ATD is structured in an analog and a digital sub-block. 7.4.1 Analog Sub-Block The analog sub-block contains all analog electronics required to perform a single conversion. Separate power supplies VDDA and VSSA allow to isolate noise of other MCU circuitry from the analog sub-block. 7.4.1.1 Sample and Hold Machine The Sample and Hold (S/H) Machine accepts analog signals from the external world and stores them as capacitor charge on a storage node. The sample process uses a two stage approach. During the first stage, the sample amplifier is used to quickly charge the storage node.The second stage connects the input directly to the storage node to complete the sample for high accuracy. When not sampling, the sample and hold machine disables its own clocks. The analog electronics still draw their quiescent current. The power down (ADPU) bit must be set to disable both the digital clocks and the analog power consumption. The input analog signals are unipolar and must fall within the potential range of VSSA to VDDA. 7.4.1.2 Analog Input Multiplexer The analog input multiplexer connects one of the 16 external analog input channels to the sample and hold machine. 7.4.1.3 Sample Buffer Amplifier The sample amplifier is used to buffer the input analog signal so that the storage node can be quickly charged to the sample potential. 7.4.1.4 Analog-to-Digital (A/D) Machine The A/D Machine performs analog to digital conversions. The resolution is program selectable at either 8 or 10 bits. The A/D machine uses a successive approximation architecture. It functions by comparing the stored analog sample potential with a series of digitally generated analog potentials. By following a binary search algorithm, the A/D machine locates the approximating potential that is nearest to the sampled potential. When not converting the A/D machine disables its own clocks. The analog electronics still draws quiescent current. The power down (ADPU) bit must be set to disable both the digital clocks and the analog power consumption. Only analog input signals within the potential range of VRL to VRH (A/D reference potentials) will result in a non-railed digital output codes. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 243 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) 7.4.2 Digital Sub-Block This subsection explains some of the digital features in more detail. See register descriptions for all details. 7.4.2.1 External Trigger Input The external trigger feature allows the user to synchronize ATD conversions to the external environment events rather than relying on software to signal the ATD module when ATD conversions are to take place. The external trigger signal (out of reset ATD channel 15, configurable in ATDCTL1) is programmable to be edge or level sensitive with polarity control. Table 7-26 gives a brief description of the different combinations of control bits and their affect on the external trigger function. Table 7-26. External Trigger Control Bits ETRIGLE X X 0 0 1 1 ETRIGP X X 0 1 0 1 ETRIGE 0 0 1 1 1 1 SCAN 0 1 X X X X Description Ignores external trigger. Performs one conversion sequence and stops. Ignores external trigger. Performs continuous conversion sequences. Falling edge triggered. Performs one conversion sequence per trigger. Rising edge triggered. Performs one conversion sequence per trigger. Trigger active low. Performs continuous conversions while trigger is active. Trigger active high. Performs continuous conversions while trigger is active. During a conversion, if additional active edges are detected the overrun error flag ETORF is set. In either level or edge triggered modes, the first conversion begins when the trigger is received. In both cases, the maximum latency time is one Bus Clock cycle plus any skew or delay introduced by the trigger circuitry. Once ETRIGE is enabled, conversions cannot be started by a write to ATDCTL5, but rather must be triggered externally. If the level mode is active and the external trigger both de-asserts and re-asserts itself during a conversion sequence, this does not constitute an overrun. Therefore, the flag is not set. If the trigger is left asserted in level mode while a sequence is completing, another sequence will be triggered immediately. 7.4.2.2 General-Purpose Digital Input Port Operation The input channel pins can be multiplexed between analog and digital data. As analog inputs, they are multiplexed and sampled to supply signals to the A/D converter. As digital inputs, they supply external input data that can be accessed through the digital port registers (PORTAD0 & PORTAD1) (input-only). MC9S12KG128 Data Sheet, Rev. 1.15 244 Freescale Semiconductor Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) The analog/digital multiplex operation is performed in the input pads. The input pad is always connected to the analog inputs of the ATD. The input pad signal is buffered to the digital port registers. This buffer can be turned on or off with the ATDDIEN0 & ATDDIEN1 register. This is important so that the buffer does not draw excess current when analog potentials are presented at its input. 7.4.2.3 Low-Power Modes The ATD can be configured for lower MCU power consumption in three different ways: • Stop Mode: This halts A/D conversion. Exit from Stop mode will resume A/D conversion, But due to the recovery time the result of this conversion should be ignored. • Wait Mode with AWAI = 1: This halts A/D conversion. Exit from Wait mode will resume A/D conversion, but due to the recovery time the result of this conversion should be ignored. • Writing ADPU = 0 (Note that all ATD registers remain accessible.): This aborts any A/D conversion in progress. NOTE The reset value for the ADPU bit is zero. Therefore, when this module is reset, it is reset into the power down state. 7.5 Resets At reset the ATD is in a power down state. The reset state of each individual bit is listed within the register description section (see Section 7.3, “Memory Map and Register Definition”) which details the registers and their bit-field. 7.6 Interrupts The interrupt requested by the ATD is listed in Table 7-27. Refer to MCU specification for related vector address and priority. Table 7-27. ATD Interrupt Vectors Interrupt Source Sequence Complete Interrupt CCR Mask I bit Local Enable ASCIE in ATDCTL2 See Section 7.3, “Memory Map and Register Definition for further details. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 245 Chapter 7 Analog-to-Digital Converter (ATD10B16CV1) MC9S12KG128 Data Sheet, Rev. 1.15 246 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.1 Introduction The inter-IC bus (IIC) is a two-wire, bidirectional serial bus that provides a simple, efficient method of data exchange between devices. Being a two-wire device, the IIC bus minimizes the need for large numbers of connections between devices, and eliminates the need for an address decoder. This bus is suitable for applications requiring occasional communications over a short distance between a number of devices. It also provides flexibility, allowing additional devices to be connected to the bus for further expansion and system development. The interface is designed to operate up to 100 kbps with maximum bus loading and timing. The device is capable of operating at higher baud rates, up to a maximum of clock/20, with reduced bus loading. The maximum communication length and the number of devices that can be connected are limited by a maximum bus capacitance of 400 pF. 8.1.1 Features The IIC module has the following key features: • Compatible with I2C bus standard • Multi-master operation • Software programmable for one of 256 different serial clock frequencies • Software selectable acknowledge bit • Interrupt driven byte-by-byte data transfer • Arbitration lost interrupt with automatic mode switching from master to slave • Calling address identification interrupt • Start and stop signal generation/detection • Repeated start signal generation • Acknowledge bit generation/detection • Bus busy detection MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 247 Chapter 8 Inter-Integrated Circuit (IICV2) 8.1.2 Modes of Operation The IIC functions the same in normal, special, and emulation modes. It has two low power modes: wait and stop modes. 8.1.3 Block Diagram The block diagram of the IIC module is shown in Figure 8-1. IIC Start Stop Arbitration Control Registers Interrupt Clock Control bus_clock In/Out Data Shift Register SCL SDA Address Compare Figure 8-1. IIC Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 248 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.2 External Signal Description The IIC module has two external pins. 8.2.1 IIC_SCL — Serial Clock Line Pin This is the bidirectional serial clock line (SCL) of the module, compatible to the IIC bus specification. 8.2.2 IIC_SDA — Serial Data Line Pin This is the bidirectional serial data line (SDA) of the module, compatible to the IIC bus specification. 8.3 Memory Map and Register Definition This section provides a detailed description of all memory and registers for the IIC module. 8.3.1 Module Memory Map The memory map for the IIC module is given below in Table 8-1. The address listed for each register is the address offset.The total address for each register is the sum of the base address for the IIC module and the address offset for each register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 249 Chapter 8 Inter-Integrated Circuit (IICV2) 8.3.2 Register Descriptions This section consists of register descriptions in address order. Each description includes a standard register diagram with an associated figure number. Details of register bit and field function follow the register diagrams, in bit order. Register Name IBAD R W IBFD R W IBCR R W IBSR R W IBDR R W D7 D6 D5 Bit 7 ADR7 6 ADR6 5 ADR5 4 ADR4 3 ADR3 2 ADR2 1 ADR1 Bit 0 0 IBC7 IBC6 IBC5 IBC4 IBC3 IBC2 0 IBC1 0 IBC0 IBEN TCF IBIE IAAS MS/SL IBB Tx/Rx TXAK 0 RSTA SRW IBIF IBSWAI RXAK IBAL D4 D3 D2 D1 D0 = Unimplemented or Reserved Table 8-1. IIC Register Summary 8.3.2.1 IIC Address Register (IBAD) 7 6 5 4 3 2 1 0 R ADR7 W Reset 0 0 0 0 0 0 0 ADR6 ADR5 ADR4 ADR3 ADR2 ADR1 0 0 = Unimplemented or Reserved Figure 8-2. IIC Bus Address Register (IBAD) Read and write anytime This register contains the address the IIC bus will respond to when addressed as a slave; note that it is not the address sent on the bus during the address transfer. Table 8-2. IBAD Field Descriptions Field 7:1 ADR[7:1] 0 Reserved Description Slave Address — Bit 1 to bit 7 contain the specific slave address to be used by the IIC bus module.The default mode of IIC bus is slave mode for an address match on the bus. Reserved — Bit 0 of the IBAD is reserved for future compatibility. This bit will always read 0. MC9S12KG128 Data Sheet, Rev. 1.15 250 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.3.2.2 IIC Frequency Divider Register (IBFD) 7 6 5 4 3 2 1 0 R IBC7 W Reset 0 0 0 0 0 0 0 0 IBC6 IBC5 IBC4 IBC3 IBC2 IBC1 IBC0 = Unimplemented or Reserved Figure 8-3. IIC Bus Frequency Divider Register (IBFD) Read and write anytime Table 8-3. IBFD Field Descriptions Field 7:0 IBC[7:0] Description I Bus Clock Rate 7:0 — This field is used to prescale the clock for bit rate selection. The bit clock generator is implemented as a prescale divider — IBC7:6, prescaled shift register — IBC5:3 select the prescaler divider and IBC2-0 select the shift register tap point. The IBC bits are decoded to give the tap and prescale values as shown in Table 8-4. Table 8-4. I-Bus Tap and Prescale Values IBC2-0 (bin) 000 001 010 011 100 101 110 111 IBC5-3 (bin) 000 001 010 011 100 101 110 111 scl2start (clocks) 2 2 2 6 14 30 62 126 SCL Tap (clocks) 5 6 7 8 9 10 12 15 scl2stop (clocks) 7 7 9 9 17 33 65 129 SDA Tap (clocks) 1 1 2 2 3 3 4 4 scl2tap (clocks) 4 4 6 6 14 30 62 126 tap2tap (clocks) 1 2 4 8 16 32 64 128 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 251 Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-5. Multiplier Factor IBC7-6 00 01 10 11 MUL 01 02 04 RESERVED The number of clocks from the falling edge of SCL to the first tap (Tap[1]) is defined by the values shown in the scl2tap column of Table 8-4, all subsequent tap points are separated by 2IBC5-3 as shown in the tap2tap column in Table 8-4. The SCL Tap is used to generated the SCL period and the SDA Tap is used to determine the delay from the falling edge of SCL to SDA changing, the SDA hold time. IBC7–6 defines the multiplier factor MUL. The values of MUL are shown in the Table 8-5. SCL Divider SCL SDA SDA Hold SDA SCL Hold(start) SCL Hold(stop) SCL START condition STOP condition Figure 8-4. SCL Divider and SDA Hold The equation used to generate the divider values from the IBFD bits is: SCL Divider = MUL x {2 x (scl2tap + [(SCL_Tap -1) x tap2tap] + 2)} MC9S12KG128 Data Sheet, Rev. 1.15 252 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) The SDA hold delay is equal to the CPU clock period multiplied by the SDA Hold value shown in Table 8-6. The equation used to generate the SDA Hold value from the IBFD bits is: SDA Hold = MUL x {scl2tap + [(SDA_Tap - 1) x tap2tap] + 3} The equation for SCL Hold values to generate the start and stop conditions from the IBFD bits is: SCL Hold(start) = MUL x [scl2start + (SCL_Tap - 1) x tap2tap] SCL Hold(stop) = MUL x [scl2stop + (SCL_Tap - 1) x tap2tap] Table 8-6. IIC Divider and Hold Values (Sheet 1 of 5) IBC[7:0] (hex) SCL Divider (clocks) 20 22 24 26 28 30 34 40 28 32 36 40 44 48 56 68 48 56 64 72 80 88 104 128 80 96 112 128 144 160 192 240 160 192 224 SDA Hold (clocks) 7 7 8 8 9 9 10 10 7 7 9 9 11 11 13 13 9 9 13 13 17 17 21 21 9 9 17 17 25 25 33 33 17 17 33 SCL Hold (start) 6 7 8 9 10 11 13 16 10 12 14 16 18 20 24 30 18 22 26 30 34 38 46 58 38 46 54 62 70 78 94 118 78 94 110 SCL Hold (stop) 11 12 13 14 15 16 18 21 15 17 19 21 23 25 29 35 25 29 33 37 41 45 53 65 41 49 57 65 73 81 97 121 81 97 113 MUL=1 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 253 Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-6. IIC Divider and Hold Values (Sheet 2 of 5) IBC[7:0] (hex) 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F SCL Divider (clocks) 256 288 320 384 480 320 384 448 512 576 640 768 960 640 768 896 1024 1152 1280 1536 1920 1280 1536 1792 2048 2304 2560 3072 3840 40 44 48 52 56 60 68 80 56 64 72 80 88 96 112 SDA Hold (clocks) 33 49 49 65 65 33 33 65 65 97 97 129 129 65 65 129 129 193 193 257 257 129 129 257 257 385 385 513 513 14 14 16 16 18 18 20 20 14 14 18 18 22 22 26 SCL Hold (start) 126 142 158 190 238 158 190 222 254 286 318 382 478 318 382 446 510 574 638 766 958 638 766 894 1022 1150 1278 1534 1918 12 14 16 18 20 22 26 32 20 24 28 32 36 40 48 SCL Hold (stop) 129 145 161 193 241 161 193 225 257 289 321 385 481 321 385 449 513 577 641 769 961 641 769 897 1025 1153 1281 1537 1921 22 24 26 28 30 32 36 42 30 34 38 42 46 50 58 MUL=2 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E MC9S12KG128 Data Sheet, Rev. 1.15 254 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-6. IIC Divider and Hold Values (Sheet 3 of 5) IBC[7:0] (hex) 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B SCL Divider (clocks) 136 96 112 128 144 160 176 208 256 160 192 224 256 288 320 384 480 320 384 448 512 576 640 768 960 640 768 896 1024 1152 1280 1536 1920 1280 1536 1792 2048 2304 2560 3072 3840 2560 3072 3584 4096 SDA Hold (clocks) 26 18 18 26 26 34 34 42 42 18 18 34 34 50 50 66 66 34 34 66 66 98 98 130 130 66 66 130 130 194 194 258 258 130 130 258 258 386 386 514 514 258 258 514 514 SCL Hold (start) 60 36 44 52 60 68 76 92 116 76 92 108 124 140 156 188 236 156 188 220 252 284 316 380 476 316 380 444 508 572 636 764 956 636 764 892 1020 1148 1276 1532 1916 1276 1532 1788 2044 SCL Hold (stop) 70 50 58 66 74 82 90 106 130 82 98 114 130 146 162 194 242 162 194 226 258 290 322 386 482 322 386 450 514 578 642 770 962 642 770 898 1026 1154 1282 1538 1922 1282 1538 1794 2050 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 255 Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-6. IIC Divider and Hold Values (Sheet 4 of 5) IBC[7:0] (hex) 7C 7D 7E 7F SCL Divider (clocks) 4608 5120 6144 7680 80 88 96 104 112 120 136 160 112 128 144 160 176 192 224 272 192 224 256 288 320 352 416 512 320 384 448 512 576 640 768 960 640 768 896 1024 1152 1280 1536 1920 SDA Hold (clocks) 770 770 1026 1026 28 28 32 32 36 36 40 40 28 28 36 36 44 44 52 52 36 36 52 52 68 68 84 84 36 36 68 68 100 100 132 132 68 68 132 132 196 196 260 260 SCL Hold (start) 2300 2556 3068 3836 24 28 32 36 40 44 52 64 40 48 56 64 72 80 96 120 72 88 104 120 136 152 184 232 152 184 216 248 280 312 376 472 312 376 440 504 568 632 760 952 SCL Hold (stop) 2306 2562 3074 3842 44 48 52 56 60 64 72 84 60 68 76 84 92 100 116 140 100 116 132 148 164 180 212 260 164 196 228 260 292 324 388 484 324 388 452 516 580 644 772 964 MUL=4 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 MC9S12KG128 Data Sheet, Rev. 1.15 256 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-6. IIC Divider and Hold Values (Sheet 5 of 5) IBC[7:0] (hex) A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF SCL Divider (clocks) 1280 1536 1792 2048 2304 2560 3072 3840 2560 3072 3584 4096 4608 5120 6144 7680 5120 6144 7168 8192 9216 10240 12288 15360 SDA Hold (clocks) 132 132 260 260 388 388 516 516 260 260 516 516 772 772 1028 1028 516 516 1028 1028 1540 1540 2052 2052 SCL Hold (start) 632 760 888 1016 1144 1272 1528 1912 1272 1528 1784 2040 2296 2552 3064 3832 2552 3064 3576 4088 4600 5112 6136 7672 SCL Hold (stop) 644 772 900 1028 1156 1284 1540 1924 1284 1540 1796 2052 2308 2564 3076 3844 2564 3076 3588 4100 4612 5124 6148 7684 8.3.2.3 IIC Control Register (IBCR) 7 6 5 4 3 2 1 0 R IBEN W Reset 0 0 0 0 0 IBIE MS/SL Tx/Rx TXAK 0 0 IBSWAI RSTA 0 0 0 = Unimplemented or Reserved Figure 8-5. IIC Bus Control Register (IBCR) Read and write anytime MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 257 Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-7. IBCR Field Descriptions Field 7 IBEN Description I-Bus Enable — This bit controls the software reset of the entire IIC bus module. 0 The module is reset and disabled. This is the power-on reset situation. When low the interface is held in reset but registers can be accessed 1 The IIC bus module is enabled.This bit must be set before any other IBCR bits have any effect If the IIC bus module is enabled in the middle of a byte transfer the interface behaves as follows: slave mode ignores the current transfer on the bus and starts operating whenever a subsequent start condition is detected. Master mode will not be aware that the bus is busy, hence if a start cycle is initiated then the current bus cycle may become corrupt. This would ultimately result in either the current bus master or the IIC bus module losing arbitration, after which bus operation would return to normal. I-Bus Interrupt Enable 0 Interrupts from the IIC bus module are disabled. Note that this does not clear any currently pending interrupt condition 1 Interrupts from the IIC bus module are enabled. An IIC bus interrupt occurs provided the IBIF bit in the status register is also set. Master/Slave Mode Select Bit — Upon reset, this bit is cleared. When this bit is changed from 0 to 1, a START signal is generated on the bus, and the master mode is selected. When this bit is changed from 1 to 0, a STOP signal is generated and the operation mode changes from master to slave.A STOP signal should only be generated if the IBIF flag is set. MS/SL is cleared without generating a STOP signal when the master loses arbitration. 0 Slave Mode 1 Master Mode 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 Transmit Acknowledge Enable — This bit specifies the value driven onto SDA during data acknowledge cycles for both master and slave receivers. The IIC module will always acknowledge address matches, provided it is enabled, regardless of the value of TXAK. Note that values written to this bit are only used when the IIC bus is a receiver, not a transmitter. 0 An acknowledge signal will be sent out to the bus at the 9th clock bit after receiving one byte data 1 No acknowledge signal response is sent (i.e., acknowledge bit = 1) 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 6 IBIE 5 MS/SL 4 Tx/Rx 3 TXAK 2 RSTA 1 Reserved — Bit 1 of the IBCR is reserved for future compatibility. This bit will always read 0. RESERVED 0 IBSWAI I Bus Interface Stop in Wait Mode 0 IIC bus module clock operates normally 1 Halt IIC bus module clock generation in wait mode Wait mode is entered via execution of a CPU WAI instruction. In the event that the IBSWAI bit is set, all clocks internal to the IIC will be stopped and any transmission currently in progress will halt.If the CPU were woken up by a source other than the IIC module, then clocks would restart and the IIC would resume MC9S12KG128 Data Sheet, Rev. 1.15 258 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) from where was during the previous transmission. It is not possible for the IIC to wake up the CPU when its internal clocks are stopped. If it were the case that the IBSWAI bit was cleared when the WAI instruction was executed, the IIC internal clocks and interface would remain alive, continuing the operation which was currently underway. It is also possible to configure the IIC such that it will wake up the CPU via an interrupt at the conclusion of the current operation. See the discussion on the IBIF and IBIE bits in the IBSR and IBCR, respectively. 8.3.2.4 IIC Status Register (IBSR) 7 6 5 4 3 2 1 0 R W Reset TCF IAAS IBB IBAL 0 SRW IBIF RXAK 1 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 8-6. IIC Bus Status Register (IBSR) This status register is read-only with exception of bit 1 (IBIF) and bit 4 (IBAL), which are software clearable. Table 8-8. IBSR Field Descriptions Field 7 TCF Description Data Transferring Bit — While one byte of data is being transferred, this bit is cleared. It is set by the falling edge of the 9th clock of a byte transfer. Note that this bit is only valid during or immediately following a transfer to the IIC module or from the IIC module. 0 Transfer in progress 1 Transfer complete Addressed as a Slave Bit — When its own specific address (I-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 I-bus control register clears this bit. 0 Not addressed 1 Addressed as a slave Bus Busy Bit 0 This bit indicates the status of the bus. When a START signal is detected, the IBB is set. If a STOP signal is detected, IBB is cleared and the bus enters idle state. 1 Bus is busy Arbitration Lost — The arbitration lost bit (IBAL) is set by hardware when the arbitration procedure is lost. Arbitration is lost in the following circumstances: 1. SDA sampled low when the master drives a high during an address or data transmit cycle. 2. SDA sampled low when the master drives a high during the acknowledge bit of a data receive cycle. 3. A start cycle is attempted when the bus is busy. 4. A repeated start cycle is requested in slave mode. 5. A stop condition is detected when the master did not request it. This bit must be cleared by software, by writing a one to it. A write of 0 has no effect on this bit. 6 IAAS 5 IBB 4 IBAL 3 Reserved — Bit 3 of IBSR is reserved for future use. A read operation on this bit will return 0. RESERVED MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 259 Chapter 8 Inter-Integrated Circuit (IICV2) Table 8-8. IBSR Field Descriptions (continued) Field 2 SRW Description Slave Read/Write — When IAAS is set this bit indicates the value of the R/W command bit of the calling address sent from the master This bit is only valid when the I-bus is in slave mode, a complete address transfer has occurred with an address match and no other transfers have been initiated. Checking this bit, the CPU can select slave transmit/receive mode according to the command of the master. 0 Slave receive, master writing to slave 1 Slave transmit, master reading from slave I-Bus Interrupt — The IBIF bit is set when one of the following conditions occurs: — Arbitration lost (IBAL bit set) — Byte transfer complete (TCF bit set) — Addressed as slave (IAAS bit set) It will cause a processor interrupt request if the IBIE bit is set. This bit must be cleared by software, writing a one to it. A write of 0 has no effect on this bit. 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 1 IBIF 0 RXAK 8.3.2.5 IIC Data I/O Register (IBDR) 7 6 5 4 3 2 1 0 R D7 W Reset 0 0 0 0 0 0 0 0 D6 D5 D4 D3 D2 D1 D0 Figure 8-7. IIC Bus Data I/O Register (IBDR) In master transmit mode, when data is written to the IBDR a data transfer is initiated. The most significant bit is sent first. In master receive mode, reading this register initiates next byte data receiving. In slave mode, the same functions are available after an address match has occurred.Note that the Tx/Rx bit in the IBCR must correctly reflect the desired direction of transfer in master and slave modes for the transmission to begin. For instance, if the IIC is configured for master transmit but a master receive is desired, then reading the IBDR will not initiate the receive. Reading the IBDR will return the last byte received while the IIC is configured in either master receive or slave receive modes. The IBDR does not reflect every byte that is transmitted on the IIC bus, nor can software verify that a byte has been written to the IBDR correctly by reading it back. In master transmit mode, the first byte of data written to IBDR following assertion of MS/SL is used for the address transfer and should com.prise of the calling address (in position D7:D1) concatenated with the required R/W bit (in position D0). MC9S12KG128 Data Sheet, Rev. 1.15 260 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.4 Functional Description This section provides a complete functional description of the IIC. 8.4.1 I-Bus Protocol The IIC bus system uses a serial data line (SDA) and a serial clock line (SCL) for data transfer. All devices connected to it must have open drain or open collector outputs. Logic AND function is exercised on both lines with external pull-up resistors. The value of these resistors is system dependent. Normally, a standard communication is composed of four parts: START signal, slave address transmission, data transfer and STOP signal. They are described briefly in the following sections and illustrated in Figure 8-8. MSB SCL 1 2 3 4 5 6 7 LSB 8 9 MSB 1 2 3 4 5 6 7 LSB 8 9 SDA AD7 AD6 AD5 AD4 AD3 AD2 AD1 R/W XXX D7 D6 D5 D4 D3 D2 D1 D0 Start Signal Calling Address Read/ Write Ack Bit Data Byte No Stop Ack Signal Bit LSB MSB SCL 1 2 3 4 5 6 7 LSB 8 9 MSB 1 2 3 4 5 6 7 8 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/ Write Ack Bit Repeated Start Signal New Calling Address Read/ Write No Stop Ack Signal Bit Figure 8-8. IIC-Bus Transmission Signals 8.4.1.1 START Signal When the bus is free, i.e. no master device is engaging the bus (both SCL and SDA lines are at logical high), a master may initiate communication by sending a START signal.As shown in Figure 8-8, a START signal is defined as a high-to-low transition of SDA while SCL is high. This signal denotes the beginning of a new data transfer (each data transfer may contain several bytes of data) and brings all slaves out of their idle states. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 261 Chapter 8 Inter-Integrated Circuit (IICV2) SDA SCL START Condition STOP Condition Figure 8-9. Start and Stop Conditions 8.4.1.2 Slave Address Transmission The first byte of data transfer immediately after the START signal is the slave address transmitted by the master. This is a seven-bit calling address followed by a R/W bit. The R/W bit tells the slave the desired direction of data transfer. 1 = Read transfer, the slave transmits data to the master. 0 = Write transfer, the master transmits data to the slave. 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 8-8). No two slaves in the system may have the same address. If the IIC bus is master, it must not transmit an address that is equal to its own slave address. The IIC bus cannot be master and slave at the same time.However, if arbitration is lost during an address cycle the IIC bus will revert to slave mode and operate correctly even if it is being addressed by another master. 8.4.1.3 Data Transfer As soon as successful slave addressing is achieved, the data transfer can proceed byte-by-byte in a direction specified by the R/W bit sent by the calling master All transfers that come after an address cycle are referred to as data transfers, even if they carry sub-address information for 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 8-8. 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 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. MC9S12KG128 Data Sheet, Rev. 1.15 262 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 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. 8.4.1.4 STOP Signal 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 8-8). The master can generate a STOP even if the slave has generated an acknowledge at which point the slave must release the bus. 8.4.1.5 Repeated START Signal As shown in Figure 8-8, 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. 8.4.1.6 Arbitration Procedure The Inter-IC bus 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 from master to slave mode does not generate a STOP condition. Meanwhile, a status bit is set by hardware to indicate loss of arbitration. 8.4.1.7 Clock Synchronization Because 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 as soon as 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 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 8-9). 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. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 263 Chapter 8 Inter-Integrated Circuit (IICV2) Start Counting High Period WAIT SCL1 SCL2 SCL Internal Counter Reset Figure 8-10. IIC-Bus Clock Synchronization 8.4.1.8 Handshaking The clock synchronization mechanism can be used as a handshake in data transfer. Slave devices may hold the SCL low after completion of 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. 8.4.1.9 Clock Stretching 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. 8.4.2 Operation in Run Mode This is the basic mode of operation. 8.4.3 Operation in Wait Mode IIC operation in wait mode can be configured. Depending on the state of internal bits, the IIC can operate normally when the CPU is in wait mode or the IIC clock generation can be turned off and the IIC module enters a power conservation state during wait mode. In the later case, any transmission or reception in progress stops at wait mode entry. 8.4.4 Operation in Stop Mode The IIC is inactive in stop mode for reduced power consumption. The STOP instruction does not affect IIC register states. MC9S12KG128 Data Sheet, Rev. 1.15 264 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.5 Resets The reset state of each individual bit is listed in Section 8.3, “Memory Map and Register Definition,” which details the registers and their bit-fields. 8.6 Interrupts Table 8-9. Interrupt Summary Interrupt IIC Interrupt Offset — Vector — Priority — Source Description IIC uses only one interrupt vector. IBAL, TCF, IAAS When either of IBAL, TCF or IAAS bits is set bits in IBSR may cause an interrupt based on arbitration register lost, transfer complete or address detect conditions Internally there are three types of interrupts in IIC. The interrupt service routine can determine the interrupt type by reading the status register. IIC Interrupt can be generated on 1. Arbitration lost condition (IBAL bit set) 2. Byte transfer condition (TCF bit set) 3. Address detect condition (IAAS bit set) The IIC interrupt is enabled by the IBIE bit in the IIC control register. It must be cleared by writing 0 to the IBF bit in the interrupt service routine. 8.7 8.7.1 8.7.1.1 Initialization/Application Information IIC Programming Examples Initialization Sequence 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. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 265 Chapter 8 Inter-Integrated Circuit (IICV2) 8.7.1.2 Generation of START After completion of the initialization procedure, serial data can be transmitted by selecting the 'master transmitter' mode. If the device is 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 TXSTART IBFREE BRSET BSET MOVB BRCLR IBSR,#$20,* IBCR,#$30 CALLING,IBDR IBSR,#$20,* ;WAIT FOR IBB FLAG TO CLEAR ;SET TRANSMIT AND MASTER MODE;i.e. GENERATE START CONDITION ;TRANSMIT THE CALLING ADDRESS, D0=R/W ;WAIT FOR IBB FLAG TO SET 8.7.1.3 Post-Transfer Software Response 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 because 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 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. ISR BCLR BRCLR BRCLR BRSET MOVB IBSR,#$02 IBCR,#$20,SLAVE IBCR,#$10,RECEIVE IBSR,#$01,END DATABUF,IBDR ;CLEAR THE IBIF FLAG ;BRANCH IF IN SLAVE MODE ;BRANCH IF IN RECEIVE MODE ;IF NO ACK, END OF TRANSMISSION ;TRANSMIT NEXT BYTE OF DATA TRANSMIT MC9S12KG128 Data Sheet, Rev. 1.15 266 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) 8.7.1.4 Generation 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 BEQ BRSET MOVB DEC BRA BCLR RTI TXCNT END IBSR,#$01,END DATABUF,IBDR TXCNT EMASTX IBCR,#$20 ;GET VALUE FROM THE TRANSMITING COUNTER ;END IF NO MORE DATA ;END IF NO ACK ;TRANSMIT NEXT BYTE OF DATA ;DECREASE THE TXCNT ;EXIT ;GENERATE A STOP CONDITION ;RETURN FROM INTERRUPT END 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 signal must be generated first. The following is an example showing how a STOP signal is generated by a master receiver. MASR DEC BEQ MOVB DEC BNE BSET BRA BCLR MOVB RTI RXCNT ENMASR RXCNT,D1 D1 NXMAR IBCR,#$08 NXMAR IBCR,#$20 IBDR,RXBUF ;DECREASE THE RXCNT ;LAST BYTE TO BE READ ;CHECK SECOND LAST BYTE ;TO BE READ ;NOT LAST OR SECOND LAST ;SECOND LAST, DISABLE ACK ;TRANSMITTING ;LAST ONE, GENERATE ‘STOP’ SIGNAL ;READ DATA AND STORE LAMAR ENMASR NXMAR 8.7.1.5 Generation of Repeated START At the end of data transfer, if the master continues to want 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 CALLING,IBDR ;ANOTHER START (RESTART) ;TRANSMIT THE CALLING ADDRESS;D0=R/W 8.7.1.6 Slave Mode 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. 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. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 267 Chapter 8 Inter-Integrated Circuit (IICV2) In slave transmitter routine, the received acknowledge bit (RXAK) must be tested before transmitting the next byte of data. Setting RXAK means 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. 8.7.1.7 Arbitration 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 continues to be 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. MC9S12KG128 Data Sheet, Rev. 1.15 268 Freescale Semiconductor Chapter 8 Inter-Integrated Circuit (IICV2) Clear IBIF Y Master Mode ? N TX Tx/Rx ? RX Y Arbitration Lost ? N Last Byte Transmitted ? N Y Clear IBAL RXAK=0 ? Y End Of Addr Cycle (Master Rx) ? N N Last Byte To Be Read ? N Y N IAAS=1 ? Y Y IAAS=1 ? N Address Transfer Y Y 2nd Last Byte To Be Read ? N Y (Read) SRW=1 ? N (Write) Y Data Transfer TX/RX ? TX ACK From Receiver ? N Read Data From IBDR And Store RX Write Next Byte To IBDR Set TXAK =1 Generate Stop Signal Set TX Mode Write Data To IBDR Tx Next Byte Switch To Rx Mode Set RX Mode Switch To Rx Mode Dummy Read From IBDR Generate Stop Signal Read Data From IBDR And Store Dummy Read From IBDR Dummy Read From IBDR RTI Figure 8-11. Flow-Chart of Typical IIC Interrupt Routine MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 269 Chapter 8 Inter-Integrated Circuit (IICV2) MC9S12KG128 Data Sheet, Rev. 1.15 270 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.1 Introduction Freescale’s scalable controller area network (MSCAN) definition is based on the MSCAN12 definition, which is the specific implementation of the MSCAN concept targeted for the M68HC12 microcontroller family. The module is a communication controller implementing the CAN 2.0A/B protocol as defined in the Bosch specification dated September 1991. For users to fully understand the MSCAN specification, it is recommended that the Bosch specification be read first to familiarize the reader with the terms and concepts contained within this document. Though not exclusively intended for automotive applications, CAN protocol is designed to meet the specific requirements of a vehicle serial data bus: real-time processing, reliable operation in the EMI environment of a vehicle, cost-effectiveness, and required bandwidth. MSCAN uses an advanced buffer arrangement resulting in predictable real-time behavior and simplified application software. 9.1.1 Block Diagram MSCAN Oscillator Clock Bus Clock CANCLK MUX Presc. Tq Clk Receive/ Transmit Engine RXCAN TXCAN Transmit Interrupt Req. Receive Interrupt Req. Errors Interrupt Req. Wake-Up Interrupt Req. Control and Status Message Filtering and Buffering Configuration Registers Wake-Up Low Pass Filter Figure 9-1. MSCAN Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 271 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.1.2 Features The basic features of the MSCAN are as follows: • Implementation of the CAN protocol — Version 2.0A/B — Standard and extended data frames — Zero to eight bytes data length — Programmable bit rate up to 1 Mbps1 — Support for remote frames • Five receive buffers with FIFO storage scheme • Three transmit buffers with internal prioritization using a “local priority” concept • Flexible maskable identifier filter supports two full-size (32-bit) extended identifier filters, or four 16-bit filters, or eight 8-bit filters • Programmable wakeup functionality with integrated low-pass filter • Programmable loopback mode supports self-test operation • Programmable listen-only mode for monitoring of CAN bus • Separate signalling and interrupt capabilities for all CAN receiver and transmitter error states (warning, error passive, bus-off) • Programmable MSCAN clock source either bus clock or oscillator clock • Internal timer for time-stamping of received and transmitted messages • Three low-power modes: sleep, power down, and MSCAN enable • Global initialization of configuration registers 9.1.3 Modes of Operation The following modes of operation are specific to the MSCAN. See Section 9.4, “Functional Description,” for details. • Listen-Only Mode • MSCAN Sleep Mode • MSCAN Initialization Mode • MSCAN Power Down Mode 9.2 External Signal Description The MSCAN uses two external pins: 9.2.1 RXCAN — CAN Receiver Input Pin RXCAN is the MSCAN receiver input pin. 1. Depending on the actual bit timing and the clock jitter of the PLL. MC9S12KG128 Data Sheet, Rev. 1.15 272 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.2.2 TXCAN — CAN Transmitter Output Pin TXCAN is the MSCAN transmitter output pin. The TXCAN output pin represents the logic level on the CAN bus: 0 = Dominant state 1 = Recessive state 9.2.3 CAN System A typical CAN system with MSCAN is shown in Figure 9-2. Each CAN station is connected physically to the CAN bus lines through a transceiver device. The transceiver is capable of driving the large current needed for the CAN bus and has current protection against defective CAN or defective stations. CAN node 1 MCU CAN Controller (MSCAN) CAN node 2 CAN node n TXCAN RXCAN Transceiver CAN_H CAN_L CAN Bus Figure 9-2. CAN System 9.3 Memory Map and Register Definition This section provides a detailed description of all registers accessible in the MSCAN. 9.3.1 Module Memory Map Table 9-1 gives an overview on all registers and their individual bits in the MSCAN memory map. The register address results from the addition of base address and address offset. The base address is determined at the MCU level and can be found in the Memory block description chapter. The address offset is defined at the module level. The MSCAN occupies 64 bytes in the memory space. The base address of the MSCAN module is determined at the MCU level when the MCU is defined. The register decode map is fixed and begins at the first address of the module address offset. Table 9-1 shows the individual registers associated with the MSCAN and their relative offset from the base address. The detailed register descriptions follow in the order they appear in the register map. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 273 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-1. MSCAN Memory Map Address Offset 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F 0x0020 -0x002F 0x0030 -0x003F 1 2 Register MSCAN Control Register 0 (CANCTL0) MSCAN Control Register 1 (CANCTL1) MSCAN Bus Timing Register 0 (CANBTR0) MSCAN Bus Timing Register 1 (CANBTR1) MSCAN Receiver Flag Register (CANRFLG) MSCAN Receiver Interrupt Enable Register (CANRIER) MSCAN Transmitter Flag Register (CANTFLG) MSCAN Transmitter Interrupt Enable Register (CANTIER) MSCAN Transmitter Message Abort Request Register (CANTARQ) MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK) MSCAN Transmit Buffer Selection Register (CANTBSEL) MSCAN Identifier Acceptance Control Register (CANIDAC) RESERVED RESERVED MSCAN Receive Error Counter (CANRXERR) MSCAN Transmit Error Counter (CANTXERR) MSCAN Identifier Acceptance Register 0(CANIDAR0) MSCAN Identifier Acceptance Register 1(CANIDAR1) MSCAN Identifier Acceptance Register 2 (CANIDAR2) MSCAN Identifier Acceptance Register 3 (CANIDAR3) MSCAN Identifier Mask Register 0 (CANIDMR0) MSCAN Identifier Mask Register 1 (CANIDMR1) MSCAN Identifier Mask Register 2 (CANIDMR2) MSCAN Identifier Mask Register 3 (CANIDMR3) MSCAN Identifier Acceptance Register 4 (CANIDAR4) MSCAN Identifier Acceptance Register 5 (CANIDAR5) MSCAN Identifier Acceptance Register 6 (CANIDAR6) MSCAN Identifier Acceptance Register 7 (CANIDAR7) MSCAN Identifier Mask Register 4 (CANIDMR4) MSCAN Identifier Mask Register 5 (CANIDMR5) MSCAN Identifier Mask Register 6 (CANIDMR6) MSCAN Identifier Mask Register 7 (CANIDMR7) Foreground Receive Buffer (CANRXFG) Foreground Transmit Buffer (CANTXFG) Access R/W1 R/W1 R/W R/W R/W1 R/W R/W1 R/W1 R/W1 R R/W1 R/W1 R R R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R2 R2/W Refer to detailed register description for write access restrictions on per bit basis. Reserved bits and unused bits within the TX- and RX-buffers (CANTXFG, CANRXFG) will be read as “X”, because of RAM-based implementation. MC9S12KG128 Data Sheet, Rev. 1.15 274 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-2. MSCAN Memory Map Offset Address 0x0000 Register This section describes in detail all the registers and register bits in the MSCAN module. Each description includes a standard register diagram with an associated figure number. Details of register bit and field function follow the register diagrams, in bit order. All bits of all registers in this module are completely synchronous to internal clocks during a register read. MSCAN Control Register 1 (CANCTL1) MSCAN Bus Timing Register 0 (CANBTR0) MSCAN Bus Timing Register 1 (CANBTR1) MSCAN Receiver Flag Register (CANRFLG) MSCAN Receiver Interrupt Enable Register (CANRIER) MSCAN Transmitter Flag Register (CANTFLG) MSCAN Transmitter Interrupt Enable Register (CANTIER) MSCAN Transmitter Message Abort Request Register (CANTARQ) MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK) MSCAN Transmit Buffer Selection Register (CANTBSEL) MSCAN Identifier Acceptance Control Register (CANIDAC) RESERVED RESERVED MSCAN Receive Error Counter (CANRXERR) MSCAN Transmit Error Counter (CANTXERR) MSCAN Identifier Acceptance Register 0(CANIDAR0) MSCAN Identifier Acceptance Register 1(CANIDAR1) MSCAN Identifier Acceptance Register 2 (CANIDAR2) MSCAN Identifier Acceptance Register 3 (CANIDAR3) MSCAN Identifier Mask Register 0 (CANIDMR0) MSCAN Identifier Mask Register 1 (CANIDMR1) MSCAN Identifier Mask Register 2 (CANIDMR2) MSCAN Identifier Mask Register 3 (CANIDMR3) MSCAN Identifier Acceptance Register 4 (CANIDAR4) MSCAN Identifier Acceptance Register 5 (CANIDAR5) MSCAN Identifier Acceptance Register 6 (CANIDAR6) MSCAN Identifier Acceptance Register 7 (CANIDAR7) MSCAN Identifier Mask Register 4 (CANIDMR4) MSCAN Identifier Mask Register 5 (CANIDMR5) MSCAN Identifier Mask Register 6 (CANIDMR6) MSCAN Identifier Mask Register 7 (CANIDMR7) Foreground Receive Buffer (CANRXFG) Foreground Transmit Buffer (CANTXFG) R R R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R2 R2/W Access R/W1 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F 0x0020 -0x002F 0x0030 -0x003F 1 R/W1 R/W R/W R/W1 R/W R/W1 R/W1 R/W1 R R/W1 R/W1 Refer to detailed register description for write access restrictions on per bit basis. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 275 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 2 Reserved bits and unused bits within the TX- and RX-buffers (CANTXFG, CANRXFG) will be read as “x”, because of RAM-based implementation. 9.3.2 Register Descriptions This section describes in detail all the registers and register bits in the MSCAN module. Each description includes a standard register diagram with an associated figure number. Details of register bit and field function follow the register diagrams, in bit order. All bits of all registers in this module are completely synchronous to internal clocks during a register read. 9.3.2.1 MSCAN Control Register 0 (CANCTL0) The CANCTL0 register provides various control bits of the MSCAN module as described below. 7 6 5 4 3 2 1 0 R RXFRM W Reset: 0 RXACT CSWAI 0 = Unimplemented 0 SYNCH TIME 0 0 WUPE 0 SLPRQ 0 INITRQ 1 Figure 9-3. MSCAN Control Register 0 (CANCTL0) NOTE The CANCTL0 register, except WUPE, INITRQ, and SLPRQ, is held in the reset state when the initialization mode is active (INITRQ = 1 and INITAK = 1). This register is writable again as soon as the initialization mode is exited (INITRQ = 0 and INITAK = 0). Read: Anytime Write: Anytime when out of initialization mode; exceptions are read-only RXACT and SYNCH, RXFRM (which is set by the module only), and INITRQ (which is also writable in initialization mode). Table 9-3. CANCTL0 Register Field Descriptions Field 7 RXFRM1 Description Received Frame Flag — This bit is read and clear only. It is set when a receiver has received a valid message correctly, independently of the filter configuration. After it is set, it remains set until cleared by software or reset. Clearing is done by writing a 1. Writing a 0 is ignored. This bit is not valid in loopback mode. 0 No valid message was received since last clearing this flag 1 A valid message was received since last clearing of this flag Receiver Active Status — This read-only flag indicates the MSCAN is receiving a message. The flag is controlled by the receiver front end. This bit is not valid in loopback mode. 0 MSCAN is transmitting or idle2 1 MSCAN is receiving a message (including when arbitration is lost)2 CAN Stops in Wait Mode — Enabling this bit allows for lower power consumption in wait mode by disabling all the clocks at the CPU bus interface to the MSCAN module. 0 The module is not affected during wait mode 1 The module ceases to be clocked during wait mode 6 RXACT 5 CSWAI3 MC9S12KG128 Data Sheet, Rev. 1.15 276 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-3. CANCTL0 Register Field Descriptions (continued) Field 4 SYNCH Description Synchronized Status — This read-only flag indicates whether the MSCAN is synchronized to the CAN bus and able to participate in the communication process. It is set and cleared by the MSCAN. 0 MSCAN is not synchronized to the CAN bus 1 MSCAN is synchronized to the CAN bus Timer Enable — This bit activates an internal 16-bit wide free running timer which is clocked by the bit clock rate. If the timer is enabled, a 16-bit time stamp will be assigned to each transmitted/received message within the active TX/RX buffer. As soon as a message is acknowledged on the CAN bus, the time stamp will be written to the highest bytes (0x000E, 0x000F) in the appropriate buffer (see Section 9.3.3, “Programmer’s Model of Message Storage”). The internal timer is reset (all bits set to 0) when disabled. This bit is held low in initialization mode. 0 Disable internal MSCAN timer 1 Enable internal MSCAN timer Wake-Up Enable — This configuration bit allows the MSCAN to restart from sleep mode when traffic on CAN is detected (see Section 9.4.6.4, “MSCAN Sleep Mode”). 0 Wake-up disabled — The MSCAN ignores traffic on CAN 1 Wake-up enabled — The MSCAN is able to restart Sleep Mode Request — This bit requests the MSCAN to enter sleep mode, which is an internal power saving mode (see Section 9.4.6.4, “MSCAN Sleep Mode”). The sleep mode request is serviced when the CAN bus is idle, i.e., the module is not receiving a message and all transmit buffers are empty. The module indicates entry to sleep mode by setting SLPAK = 1 (see Section 9.3.2.2, “MSCAN Control Register 1 (CANCTL1)”). Sleep mode will be active until SLPRQ is cleared by the CPU or, depending on the setting of WUPE, the MSCAN detects activity on the CAN bus and clears SLPRQ itself. 0 Running — The MSCAN functions normally 1 Sleep mode request — The MSCAN enters sleep mode when CAN bus idle Initialization Mode Request — When this bit is set by the CPU, the MSCAN skips to initialization mode (see Section 9.4.6.5, “MSCAN Initialization Mode”). Any ongoing transmission or reception is aborted and synchronization to the CAN bus is lost. The module indicates entry to initialization mode by setting INITAK = 1 (Section 9.3.2.2, “MSCAN Control Register 1 (CANCTL1)”). The following registers enter their hard reset state and restore their default values: CANCTL08, CANRFLG9, CANRIER10, CANTFLG, CANTIER, CANTARQ, CANTAAK, and CANTBSEL. The registers CANCTL1, CANBTR0, CANBTR1, CANIDAC, CANIDAR0-7, and CANIDMR0-7 can only be written by the CPU when the MSCAN is in initialization mode (INITRQ = 1 and INITAK = 1). The values of the error counters are not affected by initialization mode. When this bit is cleared by the CPU, the MSCAN restarts and then tries to synchronize to the CAN bus. If the MSCAN is not in bus-off state, it synchronizes after 11 consecutive recessive bits on the CAN bus; if the MSCAN is in bus-off state, it continues to wait for 128 occurrences of 11 consecutive recessive bits. Writing to other bits in CANCTL0, CANRFLG, CANRIER, CANTFLG, or CANTIER must be done only after initialization mode is exited, which is INITRQ = 0 and INITAK = 0. 0 Normal operation 1 MSCAN in initialization mode 3 TIME 2 WUPE4 1 SLPRQ5 0 INITRQ6,7 1 2 3 4 5 6 7 The MSCAN must be in normal mode for this bit to become set. See the Bosch CAN 2.0A/B specification for a detailed definition of transmitter and receiver states. In order to protect from accidentally violating the CAN protocol, the TXCAN pin is immediately forced to a recessive state when the CPU enters wait (CSWAI = 1) or stop mode (see Section 9.4.6.2, “Operation in Wait Mode” and Section 9.4.6.3, “Operation in Stop Mode”). The CPU has to make sure that the WUPE register and the WUPIE wake-up interrupt enable register (see Section 9.3.2.6, “MSCAN Receiver Interrupt Enable Register (CANRIER)) is enabled, if the recovery mechanism from stop or wait is required. The CPU cannot clear SLPRQ before the MSCAN has entered sleep mode (SLPRQ = 1 and SLPAK = 1). The CPU cannot clear INITRQ before the MSCAN has entered initialization mode (INITRQ = 1 and INITAK = 1). In order to protect from accidentally violating the CAN protocol, the TXCAN pin is immediately forced to a recessive state when the initialization mode is requested by the CPU. Thus, the recommended procedure is to bring the MSCAN into sleep mode (SLPRQ = 1 and SLPAK = 1) before requesting initialization mode. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 277 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 8 9 Not including WUPE, INITRQ, and SLPRQ. TSTAT1 and TSTAT0 are not affected by initialization mode. 10 RSTAT1 and RSTAT0 are not affected by initialization mode. 9.3.2.2 MSCAN Control Register 1 (CANCTL1) The CANCTL1 register provides various control bits and handshake status information of the MSCAN module as described below. Read: Anytime Write: Anytime when INITRQ = 1 and INITAK = 1, except CANE which is write once in normal and anytime in special system operation modes when the MSCAN is in initialization mode (INITRQ = 1 and INITAK = 1). Table 9-4. CANCTL1 Register Field Descriptions Field 7 CANE 6 CLKSRC MSCAN Enable 0 MSCAN module is disabled 1 MSCAN module is enabled MSCAN Clock Source — This bit defines the clock source for the MSCAN module (only for systems with a clock generation module; Section 9.4.3.2, “Clock System,” and Section Figure 9-40., “MSCAN Clocking Scheme,”). 0 MSCAN clock source is the oscillator clock 1 MSCAN clock source is the bus clock Loopback Self Test Mode — When this bit is set, the MSCAN performs an internal loopback which can be used for self test operation. The bit stream output of the transmitter is fed back to the receiver internally. The RXCAN input pin is ignored and the TXCAN output goes to the recessive state (logic 1). The MSCAN behaves as it does normally when transmitting and treats its own transmitted message as a message received from a remote node. In this state, the MSCAN ignores the bit sent during the ACK slot in the CAN frame acknowledge field to ensure proper reception of its own message. Both transmit and receive interrupts are generated. 0 Loopback self test disabled 1 Loopback self test enabled Listen Only Mode — This bit configures the MSCAN as a CAN bus monitor. When LISTEN is set, all valid CAN messages with matching ID are received, but no acknowledgement or error frames are sent out (see Section 9.4.5.4, “Listen-Only Mode”). In addition, the error counters are frozen. Listen only mode supports applications which require “hot plugging” or throughput analysis. The MSCAN is unable to transmit any messages when listen only mode is active. 0 Normal operation 1 Listen only mode activated Wake-Up Mode — If WUPE in CANCTL0 is enabled, this bit defines whether the integrated low-pass filter is applied to protect the MSCAN from spurious wake-up (see Section 9.4.6.4, “MSCAN Sleep Mode”). 0 MSCAN wakes up the CPU after any recessive to dominant edge on the CAN bus 1 MSCAN wakes up the CPU only in case of a dominant pulse on the CAN bus that has a length of Twup Description 5 LOOPB 4 LISTEN 2 WUPM MC9S12KG128 Data Sheet, Rev. 1.15 278 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-4. CANCTL1 Register Field Descriptions (continued) Field 1 SLPAK Description Sleep Mode Acknowledge — This flag indicates whether the MSCAN module has entered sleep mode (see Section 9.4.6.4, “MSCAN Sleep Mode”). It is used as a handshake flag for the SLPRQ sleep mode request. Sleep mode is active when SLPRQ = 1 and SLPAK = 1. Depending on the setting of WUPE, the MSCAN will clear the flag if it detects activity on the CAN bus while in sleep mode. 0 Running — The MSCAN operates normally 1 Sleep mode active — The MSCAN has entered sleep mode Initialization Mode Acknowledge — This flag indicates whether the MSCAN module is in initialization mode (see Section 9.4.6.5, “MSCAN Initialization Mode”). It is used as a handshake flag for the INITRQ initialization mode request. Initialization mode is active when INITRQ = 1 and INITAK = 1. The registers CANCTL1, CANBTR0, CANBTR1, CANIDAC, CANIDAR0–CANIDAR7, and CANIDMR0–CANIDMR7 can be written only by the CPU when the MSCAN is in initialization mode. 0 Running — The MSCAN operates normally 1 Initialization mode active — The MSCAN has entered initialization mode 0 INITAK MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 279 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.3 MSCAN Bus Timing Register 0 (CANBTR0) The CANBTR0 register configures various CAN bus timing parameters of the MSCAN module. 7 6 5 4 3 2 1 0 R SJW1 W Reset: 0 0 0 0 0 0 0 0 SJW0 BRP5 BRP4 BRP3 BRP2 BRP1 BRP0 Figure 9-4. MSCAN Bus Timing Register 0 (CANBTR0) Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1) Table 9-5. CANBTR0 Register Field Descriptions Field 7:6 SJW[1:0] 5:0 BRP[5:0] Description Synchronization Jump Width — The synchronization jump width defines the maximum number of time quanta (Tq) clock cycles a bit can be shortened or lengthened to achieve resynchronization to data transitions on the CAN bus (see Table 9-6). Baud Rate Prescaler — These bits determine the time quanta (Tq) clock which is used to build up the bit timing (see Table 9-7). Table 9-6. Synchronization Jump Width SJW1 0 0 1 1 SJW0 0 1 0 1 Synchronization Jump Width 1 Tq clock cycle 2 Tq clock cycles 3 Tq clock cycles 4 Tq clock cycles Table 9-7. Baud Rate Prescaler BRP5 0 0 0 0 : 1 BRP4 0 0 0 0 : 1 BRP3 0 0 0 0 : 1 BRP2 0 0 0 0 : 1 BRP1 0 0 1 1 : 1 BRP0 0 1 0 1 : 1 Prescaler value (P) 1 2 3 4 : 64 MC9S12KG128 Data Sheet, Rev. 1.15 280 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.4 MSCAN Bus Timing Register 1 (CANBTR1) The CANBTR1 register configures various CAN bus timing parameters of the MSCAN module. 7 6 5 4 3 2 1 0 R SAMP W Reset: 0 0 0 0 0 0 0 0 TSEG22 TSEG21 TSEG20 TSEG13 TSEG12 TSEG11 TSEG10 Figure 9-5. MSCAN Bus Timing Register 1 (CANBTR1) Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1) Table 9-8. CANBTR1 Register Field Descriptions Field 7 SAMP Description Sampling — This bit determines the number of CAN bus samples taken per bit time. 0 One sample per bit. 1 Three samples per bit1. If SAMP = 0, the resulting bit value is equal to the value of the single bit positioned at the sample point. If SAMP = 1, the resulting bit value is determined by using majority rule on the three total samples. For higher bit rates, it is recommended that only one sample is taken per bit time (SAMP = 0). 6:4 Time Segment 2 — Time segments within the bit time fix the number of clock cycles per bit time and the location TSEG2[2:0] of the sample point (see Figure 9-41). Time segment 2 (TSEG2) values are programmable as shown in Table 9-9. 3:0 Time Segment 1 — Time segments within the bit time fix the number of clock cycles per bit time and the location TSEG1[3:0] of the sample point (see Figure 9-41). Time segment 1 (TSEG1) values are programmable as shown in Table 9-10. 1 In this case, PHASE_SEG1 must be at least 2 time quanta (Tq). Table 9-9. Time Segment 2 Values TSEG22 0 0 : 1 1 1 TSEG21 0 0 : 1 1 TSEG20 0 1 : 0 1 Time Segment 2 1 Tq clock cycle1 2 Tq clock cycles : 7 Tq clock cycles 8 Tq clock cycles This setting is not valid. Please refer to Table 9-36 for valid settings. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 281 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-10. Time Segment 1 Values TSEG13 0 0 0 0 : 1 1 1 TSEG12 0 0 0 0 : 1 1 TSEG11 0 0 1 1 : 1 1 TSEG10 0 1 0 1 : 0 1 Time segment 1 1 Tq clock cycle1 2 Tq clock cycles1 3 Tq clock cycles1 4 Tq clock cycles : 15 Tq clock cycles 16 Tq clock cycles This setting is not valid. Please refer to Table 9-36 for valid settings. The bit time is determined by the oscillator frequency, the baud rate prescaler, and the number of time quanta (Tq) clock cycles per bit (as shown in Table 9-9 and Table 9-10). Eqn. 9-1 ( Prescaler value ) Bit Time = ----------------------------------------------------- • ( 1 + TimeSegment1 + TimeSegment2 ) f CANCLK 9.3.2.5 MSCAN Receiver Flag Register (CANRFLG) A flag can be cleared only by software (writing a 1 to the corresponding bit position) when the condition which caused the setting is no longer valid. Every flag has an associated interrupt enable bit in the CANRIER register. 7 6 5 4 3 2 1 0 R WUPIF W Reset: 0 0 CSCIF RSTAT1 RSTAT0 TSTAT1 TSTAT0 OVRIF RXF 0 0 0 0 0 0 = Unimplemented Figure 9-6. MSCAN Receiver Flag Register (CANRFLG) NOTE The CANRFLG register is held in the reset state1 when the initialization mode is active (INITRQ = 1 and INITAK = 1). This register is writable again as soon as the initialization mode is exited (INITRQ = 0 and INITAK = 0). Read: Anytime Write: Anytime when out of initialization mode, except RSTAT[1:0] and TSTAT[1:0] flags which are read-only; write of 1 clears flag; write of 0 is ignored. 1. The RSTAT[1:0], TSTAT[1:0] bits are not affected by initialization mode. MC9S12KG128 Data Sheet, Rev. 1.15 282 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-11. CANRFLG Register Field Descriptions Field 7 WUPIF Description Wake-Up Interrupt Flag — If the MSCAN detects CAN bus activity while in sleep mode (see Section 9.4.6.4, “MSCAN Sleep Mode,”) and WUPE = 1 in CANTCTL0 (see Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”), the module will set WUPIF. If not masked, a wake-up interrupt is pending while this flag is set. 0 No wake-up activity observed while in sleep mode 1 MSCAN detected activity on the CAN bus and requested wake-up CAN Status Change Interrupt Flag — This flag is set when the MSCAN changes its current CAN bus status due to the actual value of the transmit error counter (TEC) and the receive error counter (REC). An additional 4-bit (RSTAT[1:0], TSTAT[1:0]) status register, which is split into separate sections for TEC/REC, informs the system on the actual CAN bus status (see Section 9.3.2.6, “MSCAN Receiver Interrupt Enable Register (CANRIER)”). If not masked, an error interrupt is pending while this flag is set. CSCIF provides a blocking interrupt. That guarantees that the receiver/transmitter status bits (RSTAT/TSTAT) are only updated when no CAN status change interrupt is pending. If the TECs/RECs change their current value after the CSCIF is asserted, which would cause an additional state change in the RSTAT/TSTAT bits, these bits keep their status until the current CSCIF interrupt is cleared again. 0 No change in CAN bus status occurred since last interrupt 1 MSCAN changed current CAN bus status 6 CSCIF 5:4 Receiver Status Bits — The values of the error counters control the actual CAN bus status of the MSCAN. As RSTAT[1:0] soon as the status change interrupt flag (CSCIF) is set, these bits indicate the appropriate receiver related CAN bus status of the MSCAN. The coding for the bits RSTAT1, RSTAT0 is: 00 RxOK: 0 ≤ receive error counter ≤ 96 01 RxWRN: 96 < receive error counter ≤ 127 10 RxERR: 127 < receive error counter 11 Bus-off1: transmit error counter > 255 3:2 Transmitter Status Bits — The values of the error counters control the actual CAN bus status of the MSCAN. TSTAT[1:0] As soon as the status change interrupt flag (CSCIF) is set, these bits indicate the appropriate transmitter related CAN bus status of the MSCAN. The coding for the bits TSTAT1, TSTAT0 is: 00 TxOK: 0 ≤ transmit error counter ≤ 96 01 TxWRN: 96 < transmit error counter ≤ 127 10 TxERR: 127 < transmit error counter ≤ 255 11 Bus-Off: transmit error counter > 255 1 OVRIF Overrun Interrupt Flag — This flag is set when a data overrun condition occurs. If not masked, an error interrupt is pending while this flag is set. 0 No data overrun condition 1 A data overrun detected Receive Buffer Full Flag — RXF is set by the MSCAN when a new message is shifted in the receiver FIFO. This flag indicates whether the shifted buffer is loaded with a correctly received message (matching identifier, matching cyclic redundancy code (CRC) and no other errors detected). After the CPU has read that message from the RxFG buffer in the receiver FIFO, the RXF flag must be cleared to release the buffer. A set RXF flag prohibits the shifting of the next FIFO entry into the foreground buffer (RxFG). If not masked, a receive interrupt is pending while this flag is set. 0 No new message available within the RxFG 1 The receiver FIFO is not empty. A new message is available in the RxFG 0 RXF2 1 Redundant Information for the most critical CAN bus status which is “bus-off”. This only occurs if the Tx error counter exceeds a number of 255 errors. Bus-off affects the receiver state. As soon as the transmitter leaves its bus-off state the receiver state skips to RxOK too. Refer also to TSTAT[1:0] coding in this register. 2 To ensure data integrity, do not read the receive buffer registers while the RXF flag is cleared. For MCUs with dual CPUs, reading the receive buffer registers while the RXF flag is cleared may result in a CPU fault condition. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 283 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.6 MSCAN Receiver Interrupt Enable Register (CANRIER) This register contains the interrupt enable bits for the interrupt flags described in the CANRFLG register. 7 6 5 4 3 2 1 0 R WUPIE W Reset: 0 0 0 0 0 0 0 0 CSCIE RSTATE1 RSTATE0 TSTATE1 TSTATE0 OVRIE RXFIE Figure 9-7. MSCAN Receiver Interrupt Enable Register (CANRIER) NOTE The CANRIER register is held in the reset state when the initialization mode is active (INITRQ=1 and INITAK=1). This register is writable when not in initialization mode (INITRQ=0 and INITAK=0). The RSTATE[1:0], TSTATE[1:0] bits are not affected by initialization mode. Read: Anytime Write: Anytime when not in initialization mode Table 9-12. CANRIER Register Field Descriptions Field 7 WUPIE1 6 CSCIE Description Wake-Up Interrupt Enable 0 No interrupt request is generated from this event. 1 A wake-up event causes a Wake-Up interrupt request. CAN Status Change Interrupt Enable 0 No interrupt request is generated from this event. 1 A CAN Status Change event causes an error interrupt request. 5:4 Receiver Status Change Enable — These RSTAT enable bits control the sensitivity level in which receiver state RSTATE[1:0] changes are causing CSCIF interrupts. Independent of the chosen sensitivity level the RSTAT flags continue to indicate the actual receiver state and are only updated if no CSCIF interrupt is pending. 00 Do not generate any CSCIF interrupt caused by receiver state changes. 01 Generate CSCIF interrupt only if the receiver enters or leaves “bus-off” state. Discard other receiver state changes for generating CSCIF interrupt. 10 Generate CSCIF interrupt only if the receiver enters or leaves “RxErr” or “bus-off”2 state. Discard other receiver state changes for generating CSCIF interrupt. 11 Generate CSCIF interrupt on all state changes. 3:2 Transmitter Status Change Enable — These TSTAT enable bits control the sensitivity level in which transmitter TSTATE[1:0] state changes are causing CSCIF interrupts. Independent of the chosen sensitivity level, the TSTAT flags continue to indicate the actual transmitter state and are only updated if no CSCIF interrupt is pending. 00 Do not generate any CSCIF interrupt caused by transmitter state changes. 01 Generate CSCIF interrupt only if the transmitter enters or leaves “bus-off” state. Discard other transmitter state changes for generating CSCIF interrupt. 10 Generate CSCIF interrupt only if the transmitter enters or leaves “TxErr” or “bus-off” state. Discard other transmitter state changes for generating CSCIF interrupt. 11 Generate CSCIF interrupt on all state changes. MC9S12KG128 Data Sheet, Rev. 1.15 284 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-12. CANRIER Register Field Descriptions (continued) Field 1 OVRIE 0 RXFIE 1 Description Overrun Interrupt Enable 0 No interrupt request is generated from this event. 1 An overrun event causes an error interrupt request. Receiver Full Interrupt Enable 0 No interrupt request is generated from this event. 1 A receive buffer full (successful message reception) event causes a receiver interrupt request. WUPIE and WUPE (see Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”) must both be enabled if the recovery mechanism from stop or wait is required. 2 Bus-off state is defined by the CAN standard (see Bosch CAN 2.0A/B protocol specification: for only transmitters. Because the only possible state change for the transmitter from bus-off to TxOK also forces the receiver to skip its current state to RxOK, the coding of the RXSTAT[1:0] flags define an additional bus-off state for the receiver (see Section 9.3.2.5, “MSCAN Receiver Flag Register (CANRFLG)”). 9.3.2.7 MSCAN Transmitter Flag Register (CANTFLG) The transmit buffer empty flags each have an associated interrupt enable bit in the CANTIER register. 7 6 5 4 3 2 1 0 R W Reset: 0 0 0 0 0 TXE2 TXE1 1 TXE0 1 0 0 0 0 0 1 = Unimplemented Figure 9-8. MSCAN Transmitter Flag Register (CANTFLG) NOTE The CANTFLG register is held in the reset state when the initialization mode is active (INITRQ = 1 and INITAK = 1). This register is writable when not in initialization mode (INITRQ = 0 and INITAK = 0). Read: Anytime Write: Anytime for TXEx flags when not in initialization mode; write of 1 clears flag, write of 0 is ignored MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 285 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-13. CANTFLG Register Field Descriptions Field 2:0 TXE[2:0] Description Transmitter Buffer Empty — This flag indicates that the associated transmit message buffer is empty, and thus not scheduled for transmission. The CPU must clear the flag after a message is set up in the transmit buffer and is due for transmission. The MSCAN sets the flag after the message is sent successfully. The flag is also set by the MSCAN when the transmission request is successfully aborted due to a pending abort request (see Section 9.3.2.9, “MSCAN Transmitter Message Abort Request Register (CANTARQ)”). If not masked, a transmit interrupt is pending while this flag is set. Clearing a TXEx flag also clears the corresponding ABTAKx (see Section 9.3.2.10, “MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK)”). When a TXEx flag is set, the corresponding ABTRQx bit is cleared (see Section 9.3.2.9, “MSCAN Transmitter Message Abort Request Register (CANTARQ)”). When listen-mode is active (see Section 9.3.2.2, “MSCAN Control Register 1 (CANCTL1)”) the TXEx flags cannot be cleared and no transmission is started. Read and write accesses to the transmit buffer will be blocked, if the corresponding TXEx bit is cleared (TXEx = 0) and the buffer is scheduled for transmission. 0 The associated message buffer is full (loaded with a message due for transmission) 1 The associated message buffer is empty (not scheduled) 9.3.2.8 MSCAN Transmitter Interrupt Enable Register (CANTIER) This register contains the interrupt enable bits for the transmit buffer empty interrupt flags. 7 6 5 4 3 2 1 0 R W Reset: 0 0 0 0 0 TXEIE2 TXEIE1 0 TXEIE0 0 0 0 0 0 0 0 = Unimplemented Figure 9-9. MSCAN Transmitter Interrupt Enable Register (CANTIER) NOTE The CANTIER register is held in the reset state when the initialization mode is active (INITRQ = 1 and INITAK = 1). This register is writable when not in initialization mode (INITRQ = 0 and INITAK = 0). Read: Anytime Write: Anytime when not in initialization mode Table 9-14. CANTIER Register Field Descriptions Field 2:0 TXEIE[2:0] Description Transmitter Empty Interrupt Enable 0 No interrupt request is generated from this event. 1 A transmitter empty (transmit buffer available for transmission) event causes a transmitter empty interrupt request. MC9S12KG128 Data Sheet, Rev. 1.15 286 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.9 MSCAN Transmitter Message Abort Request Register (CANTARQ) The CANTARQ register allows abort request of queued messages as described below. 7 6 5 4 3 2 1 0 R W Reset: 0 0 0 0 0 ABTRQ2 ABTRQ1 0 ABTRQ0 0 0 0 0 0 0 0 = Unimplemented Figure 9-10. MSCAN Transmitter Message Abort Request Register (CANTARQ) NOTE The CANTARQ register is held in the reset state when the initialization mode is active (INITRQ = 1 and INITAK = 1). This register is writable when not in initialization mode (INITRQ = 0 and INITAK = 0). Read: Anytime Write: Anytime when not in initialization mode Table 9-15. CANTARQ Register Field Descriptions Field Description 2:0 Abort Request — The CPU sets the ABTRQx bit to request that a scheduled message buffer (TXEx = 0) be ABTRQ[2:0] aborted. The MSCAN grants the request if the message has not already started transmission, or if the transmission is not successful (lost arbitration or error). When a message is aborted, the associated TXE (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and abort acknowledge flags (ABTAK, see Section 9.3.2.10, “MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK)”) are set and a transmit interrupt occurs if enabled. The CPU cannot reset ABTRQx. ABTRQx is reset whenever the associated TXE flag is set. 0 No abort request 1 Abort request pending MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 287 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.10 MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK) The CANTAAK register indicates the successful abort of a queued message, if requested by the appropriate bits in the CANTARQ register. 7 6 5 4 3 2 1 0 R W Reset: 0 0 0 0 0 ABTAK2 ABTAK1 ABTAK0 0 0 0 0 0 0 0 0 = Unimplemented Figure 9-11. MSCAN Transmitter Message Abort Acknowledge Register (CANTAAK) NOTE The CANTAAK register is held in the reset state when the initialization mode is active (INITRQ = 1 and INITAK = 1). Read: Anytime Write: Unimplemented for ABTAKx flags Table 9-16. CANTAAK Register Field Descriptions Field Description 2:0 Abort Acknowledge — This flag acknowledges that a message was aborted due to a pending abort request ABTAK[2:0] from the CPU. After a particular message buffer is flagged empty, this flag can be used by the application software to identify whether the message was aborted successfully or was sent anyway. The ABTAKx flag is cleared whenever the corresponding TXE flag is cleared. 0 The message was not aborted. 1 The message was aborted. MC9S12KG128 Data Sheet, Rev. 1.15 288 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.11 MSCAN Transmit Buffer Selection Register (CANTBSEL) The CANTBSEL register allows the selection of the actual transmit message buffer, which then will be accessible in the CANTXFG register space. 7 6 5 4 3 2 1 0 R W Reset: 0 0 0 0 0 TX2 TX1 0 TX0 0 0 0 0 0 0 0 = Unimplemented Figure 9-12. MSCAN Transmit Buffer Selection Register (CANTBSEL) NOTE The CANTBSEL register is held in the reset state when the initialization mode is active (INITRQ = 1 and INITAK=1). This register is writable when not in initialization mode (INITRQ = 0 and INITAK = 0). Read: Find the lowest ordered bit set to 1, all other bits will be read as 0 Write: Anytime when not in initialization mode Table 9-17. CANTBSEL Register Field Descriptions Field 2:0 TX[2:0] Description Transmit Buffer Select — The lowest numbered bit places the respective transmit buffer in the CANTXFG register space (e.g., TX1 = 1 and TX0 = 1 selects transmit buffer TX0; TX1 = 1 and TX0 = 0 selects transmit buffer TX1). Read and write accesses to the selected transmit buffer will be blocked, if the corresponding TXEx bit is cleared and the buffer is scheduled for transmission (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”). 0 The associated message buffer is deselected 1 The associated message buffer is selected, if lowest numbered bit The following gives a short programming example of the usage of the CANTBSEL register: To get the next available transmit buffer, application software must read the CANTFLG register and write this value back into the CANTBSEL register. In this example Tx buffers TX1 and TX2 are available. The value read from CANTFLG is therefore 0b0000_0110. When writing this value back to CANTBSEL, the Tx buffer TX1 is selected in the CANTXFG because the lowest numbered bit set to 1 is at bit position 1. Reading back this value out of CANTBSEL results in 0b0000_0010, because only the lowest numbered bit position set to 1 is presented. This mechanism eases the application software the selection of the next available Tx buffer. • • • LDD CANTFLG; value read is 0b0000_0110 STD CANTBSEL; value written is 0b0000_0110 LDD CANTBSEL; value read is 0b0000_0010 If all transmit message buffers are deselected, no accesses are allowed to the CANTXFG registers. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 289 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.12 MSCAN Identifier Acceptance Control Register (CANIDAC) The CANIDAC register is used for identifier acceptance control as described below. 7 6 5 4 3 2 1 0 R W Reset: 0 0 IDAM1 IDAM0 0 0 IDHIT2 IDHIT1 IDHIT0 0 0 0 0 0 0 0 = Unimplemented Figure 9-13. MSCAN Identifier Acceptance Control Register (CANIDAC) Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1), except bits IDHITx, which are read-only Table 9-18. CANIDAC Register Field Descriptions Field 5:4 IDAM[1:0] 2:0 IDHIT[2:0] Description Identifier Acceptance Mode — The CPU sets these flags to define the identifier acceptance filter organization (see Section 9.4.3, “Identifier Acceptance Filter”). Table 9-19 summarizes the different settings. In filter closed mode, no message is accepted such that the foreground buffer is never reloaded. Identifier Acceptance Hit Indicator — The MSCAN sets these flags to indicate an identifier acceptance hit (see Section 9.4.3, “Identifier Acceptance Filter”). Table 9-20 summarizes the different settings. Table 9-19. Identifier Acceptance Mode Settings IDAM1 0 0 1 1 IDAM0 0 1 0 1 Identifier Acceptance Mode Two 32-bit acceptance filters Four 16-bit acceptance filters Eight 8-bit acceptance filters Filter closed Table 9-20. Identifier Acceptance Hit Indication IDHIT2 0 0 0 0 1 1 1 1 IDHIT1 0 0 1 1 0 0 1 1 IDHIT0 0 1 0 1 0 1 0 1 Identifier Acceptance Hit Filter 0 hit Filter 1 hit Filter 2 hit Filter 3 hit Filter 4 hit Filter 5 hit Filter 6 hit Filter 7 hit The IDHITx indicators are always related to the message in the foreground buffer (RxFG). When a message gets shifted into the foreground buffer of the receiver FIFO the indicators are updated as well. MC9S12KG128 Data Sheet, Rev. 1.15 290 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.13 MSCAN Reserved Register reserved for factory testing of the MSCAN module and is not available in normal system operation modes. 7 6 5 4 3 2 1 0 R W Reset: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented Figure 9-14. MSCAN Reserved Register Read: Always read 0x0000 in normal system operation modes Write: Unimplemented in normal system operation modes NOTE Writing to this register when in special modes can alter the MSCAN functionality. 9.3.2.14 MSCAN Receive Error Counter (CANRXERR) This register reflects the status of the MSCAN receive error counter. 7 6 5 4 3 2 1 0 R W Reset: RXERR7 RXERR6 RXERR5 RXERR4 RXERR3 RXERR2 RXERR1 RXERR0 0 0 0 0 0 0 0 0 = Unimplemented Figure 9-15. MSCAN Receive Error Counter (CANRXERR) Read: Only when in sleep mode (SLPRQ = 1 and SLPAK = 1) or initialization mode (INITRQ = 1 and INITAK = 1) Write: Unimplemented NOTE Reading this register when in any other mode other than sleep or initialization mode may return an incorrect value. For MCUs with dual CPUs, this may result in a CPU fault condition. Writing to this register when in special modes can alter the MSCAN functionality. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 291 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.15 MSCAN Transmit Error Counter (CANTXERR) This register reflects the status of the MSCAN transmit error counter. 7 6 5 4 3 2 1 0 R W Reset: TXERR7 TXERR6 TXERR5 TXERR4 TXERR3 TXERR2 TXERR1 TXERR0 0 0 0 0 0 0 0 0 = Unimplemented Figure 9-16. MSCAN Transmit Error Counter (CANTXERR) Read: Only when in sleep mode (SLPRQ = 1 and SLPAK = 1) or initialization mode (INITRQ = 1 and INITAK = 1) Write: Unimplemented NOTE Reading this register when in any other mode other than sleep or initialization mode, may return an incorrect value. For MCUs with dual CPUs, this may result in a CPU fault condition. Writing to this register when in special modes can alter the MSCAN functionality. MC9S12KG128 Data Sheet, Rev. 1.15 292 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.16 MSCAN Identifier Acceptance Registers (CANIDAR0-7) On reception, each message is written into the background receive buffer. The CPU is only signalled to read the message if it passes the criteria in the identifier acceptance and identifier mask registers (accepted); otherwise, the message is overwritten by the next message (dropped). The acceptance registers of the MSCAN are applied on the IDR0–IDR3 registers (see Section 9.3.3.1, “Identifier Registers (IDR0–IDR3)”) of incoming messages in a bit by bit manner (see Section 9.4.3, “Identifier Acceptance Filter”). For extended identifiers, all four acceptance and mask registers are applied. For standard identifiers, only the first two (CANIDAR0/1, CANIDMR0/1) are applied. Module Base + 0x0010 (CANIDAR0) 0x0011 (CANIDAR1) 0x0012 (CANIDAR2) 0x0013 (CANIDAR3) 7 6 5 4 3 2 1 0 R W Reset AC7 0 7 AC6 0 6 AC5 0 5 AC4 0 4 AC3 0 3 AC2 0 2 AC1 0 1 AC0 0 0 R W Reset AC7 0 7 AC6 0 6 AC5 0 5 AC4 0 4 AC3 0 3 AC2 0 2 AC1 0 1 AC0 0 0 R W Reset AC7 0 7 AC6 0 6 AC5 0 5 AC4 0 4 AC3 0 3 AC2 0 2 AC1 0 1 AC0 0 0 R W Reset AC7 0 AC6 0 AC5 0 AC4 0 AC3 0 AC2 0 AC1 0 AC0 0 Figure 9-17. MSCAN Identifier Acceptance Registers (First Bank) — CANIDAR0–CANIDAR3 Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1) Table 9-21. CANIDAR0–CANIDAR3 Register Field Descriptions Field 7:0 AC[7:0] Description Acceptance Code Bits — AC[7:0] comprise a user-defined sequence of bits with which the corresponding bits of the related identifier register (IDRn) of the receive message buffer are compared. The result of this comparison is then masked with the corresponding identifier mask register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 293 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Module Base + 0x0018 (CANIDAR4) 0x0019 (CANIDAR5) 0x001A (CANIDAR6) 0x001B (CANIDAR7) 7 6 5 4 3 2 1 0 R W Reset AC7 0 7 AC6 0 6 AC5 0 5 AC4 0 4 AC3 0 3 AC2 0 2 AC1 0 1 AC0 0 0 R W Reset AC7 0 7 AC6 0 6 AC5 0 5 AC4 0 4 AC3 0 3 AC2 0 2 AC1 0 1 AC0 0 0 R W Reset AC7 0 7 AC6 0 6 AC5 0 5 AC4 0 4 AC3 0 3 AC2 0 2 AC1 0 1 AC0 0 0 R W Reset AC7 0 AC6 0 AC5 0 AC4 0 AC3 0 AC2 0 AC1 0 AC0 0 Figure 9-18. MSCAN Identifier Acceptance Registers (Second Bank) — CANIDAR4–CANIDAR7 Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1) Table 9-22. CANIDAR4–CANIDAR7 Register Field Descriptions Field 7:0 AC[7:0] Description Acceptance Code Bits — AC[7:0] comprise a user-defined sequence of bits with which the corresponding bits of the related identifier register (IDRn) of the receive message buffer are compared. The result of this comparison is then masked with the corresponding identifier mask register. MC9S12KG128 Data Sheet, Rev. 1.15 294 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.2.17 MSCAN Identifier Mask Registers (CANIDMR0–CANIDMR7) The identifier mask register specifies which of the corresponding bits in the identifier acceptance register are relevant for acceptance filtering. To receive standard identifiers in 32 bit filter mode, it is required to program the last three bits (AM[2:0]) in the mask registers CANIDMR1 and CANIDMR5 to “don’t care.” To receive standard identifiers in 16 bit filter mode, it is required to program the last three bits (AM[2:0]) in the mask registers CANIDMR1, CANIDMR3, CANIDMR5, and CANIDMR7 to “don’t care.” Module Base + 0x0014 (CANIDMR0) 0x0015 (CANIDMR1) 0x0016 (CANIDMR2) 0x0017 (CANIDMR3) 7 6 5 4 3 2 1 0 R W Reset AM7 0 7 AM6 0 6 AM5 0 5 AM4 0 4 AM3 0 3 AM2 0 2 AM1 0 1 AM0 0 0 R W Reset AM7 0 7 AM6 0 6 AM5 0 5 AM4 0 4 AM3 0 3 AM2 0 2 AM1 0 1 AM0 0 0 R W Reset AM7 0 7 AM6 0 6 AM5 0 5 AM4 0 4 AM3 0 3 AM2 0 2 AM1 0 1 AM0 0 0 R W Reset AM7 0 AM6 0 AM5 0 AM4 0 AM3 0 AM2 0 AM1 0 AM0 0 Figure 9-19. MSCAN Identifier Mask Registers (First Bank) — CANIDMR0–CANIDMR3 Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1) Table 9-23. CANIDMR0–CANIDMR3 Register Field Descriptions Field 7:0 AM[7:0] Description Acceptance Mask Bits — If a particular bit in this register is cleared, this indicates that the corresponding bit in the identifier acceptance register must be the same as its identifier bit before a match is detected. The message is accepted if all such bits match. If a bit is set, it indicates that the state of the corresponding bit in the identifier acceptance register does not affect whether or not the message is accepted. 0 Match corresponding acceptance code register and identifier bits 1 Ignore corresponding acceptance code register bit MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 295 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Module Base + 0x001C (CANIDMR4) 0x001D (CANIDMR5) 0x001E (CANIDMR6) 0x001F (CANIDMR7) 7 6 5 4 3 2 1 0 R W Reset AM7 0 7 AM6 0 6 AM5 0 5 AM4 0 4 AM3 0 3 AM2 0 2 AM1 0 1 AM0 0 0 R W Reset AM7 0 7 AM6 0 6 AM5 0 5 AM4 0 4 AM3 0 3 AM2 0 2 AM1 0 1 AM0 0 0 R W Reset AM7 0 7 AM6 0 6 AM5 0 5 AM4 0 4 AM3 0 3 AM2 0 2 AM1 0 1 AM0 0 0 R W Reset AM7 0 AM6 0 AM5 0 AM4 0 AM3 0 AM2 0 AM1 0 AM0 0 Figure 9-20. MSCAN Identifier Mask Registers (Second Bank) — CANIDMR4–CANIDMR7 Read: Anytime Write: Anytime in initialization mode (INITRQ = 1 and INITAK = 1) Table 9-24. CANIDMR4–CANIDMR7 Register Field Descriptions Field 7:0 AM[7:0] Description Acceptance Mask Bits — If a particular bit in this register is cleared, this indicates that the corresponding bit in the identifier acceptance register must be the same as its identifier bit before a match is detected. The message is accepted if all such bits match. If a bit is set, it indicates that the state of the corresponding bit in the identifier acceptance register does not affect whether or not the message is accepted. 0 Match corresponding acceptance code register and identifier bits 1 Ignore corresponding acceptance code register bit MC9S12KG128 Data Sheet, Rev. 1.15 296 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.3.3 Programmer’s Model of Message Storage The following section details the organization of the receive and transmit message buffers and the associated control registers. To simplify the programmer interface, the receive and transmit message buffers have the same outline. Each message buffer allocates 16 bytes in the memory map containing a 13 byte data structure. An additional transmit buffer priority register (TBPR) is defined for the transmit buffers. Within the last two bytes of this memory map, the MSCAN stores a special 16-bit time stamp, which is sampled from an internal timer after successful transmission or reception of a message. This feature is only available for transmit and receiver buffers, if the TIME bit is set (see Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”). The time stamp register is written by the MSCAN. The CPU can only read these registers. Table 9-25. Message Buffer Organization Offset Address 0x00X0 0x00X1 0x00X2 0x00X3 0x00X4 0x00X5 0x00X6 0x00X7 0x00X8 0x00X9 0x00XA 0x00XB 0x00XC 0x00XD 0x00XE 0x00XF 1 2 Register 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 Register1 Time Stamp Register (High Byte)2 Time Stamp Register (Low Byte)3 Access Not applicable for receive buffers Read-only for CPU 3 Read-only for CPU Figure 9-21 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 9-22. All bits of the receive and transmit buffers are ‘x’ out of reset because of RAM-based implementation1. All reserved or unused bits of the receive and transmit buffers always read ‘x’. 1. Exception: The transmit priority registers are 0 out of reset. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 297 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Register Name IDR0 R W R W R IDR2 W R IDR3 W R DSR0 W R DSR1 W R DSR2 W R DSR3 W R DSR4 W R DSR5 W R DSR6 W R DSR7 W R DLR W Bit 7 ID28 6 ID27 5 ID26 4 ID25 3 ID24 2 ID23 1 ID22 Bit0 ID21 IDR1 ID20 ID19 ID18 SRR (=1) IDE (=1) ID17 ID16 ID15 ID14 ID13 ID12 ID11 ID10 ID9 ID8 ID7 ID6 ID5 ID4 ID3 ID2 ID1 ID0 RTR DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DB7 DB6 DB5 DB4 DB3 DB2 DB1 DB0 DLC3 DLC2 DLC1 DLC0 = Unused, always read ‘x’ Figure 9-21. Receive/Transmit Message Buffer — Extended Identifier Mapping Read: For transmit buffers, anytime when TXEx flag is set (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 9.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”). For receive buffers, only when RXF flag is set (see Section 9.3.2.5, “MSCAN Receiver Flag Register (CANRFLG)”). MC9S12KG128 Data Sheet, Rev. 1.15 298 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Write: For transmit buffers, anytime when TXEx flag is set (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 9.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”). Unimplemented for receive buffers. Reset: Undefined (0x00XX) because of RAM-based implementation Register Name IDR0 R W R W R W R W Bit 7 ID10 6 ID9 5 ID8 4 ID7 3 ID6 2 ID5 1 ID4 Bit 0 ID3 IDR1 ID2 ID1 ID0 RTR IDE (=0) IDR2 IDR3 = Unused, always read ‘x’ Figure 9-22. Receive/Transmit Message Buffer — Standard Identifier Mapping 9.3.3.1 Identifier Registers (IDR0–IDR3) The identifier registers for an extended format identifier consist of a total of 32 bits; ID[28:0], SRR, IDE, and RTR bits. The identifier registers for a standard format identifier consist of a total of 13 bits; ID[10:0], RTR, and IDE bits. 9.3.3.1.1 IDR0–IDR3 for Extended Identifier Mapping 7 6 5 4 3 2 1 0 R ID28 W Reset: x x x x x x x x ID27 ID26 ID25 ID24 ID23 ID22 ID21 Figure 9-23. Identifier Register 0 (IDR0) — Extended Identifier Mapping Table 9-26. IDR0 Register Field Descriptions — Extended Field 7:0 ID[28:21] Description Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 299 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 7 6 5 4 3 2 1 0 R ID20 W Reset: x x x x x x x x ID19 ID18 SRR (=1) IDE (=1) ID17 ID16 ID15 Figure 9-24. Identifier Register 1 (IDR1) — Extended Identifier Mapping Table 9-27. IDR1 Register Field Descriptions — Extended Field 7:5 ID[20:18] 4 SRR 3 IDE Description Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. Substitute Remote Request — This fixed recessive bit is used only in extended format. It must be set to 1 by the user for transmission buffers and is stored as received on the CAN bus for receive buffers. ID Extended — This flag indicates whether the extended or standard identifier format is applied in this buffer. In the case of a receive buffer, the flag is set as received and indicates to the CPU how to process the buffer identifier registers. In the case of a transmit buffer, the flag indicates to the MSCAN what type of identifier to send. 0 Standard format (11 bit) 1 Extended format (29 bit) Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. 2:0 ID[17:15] 7 6 5 4 3 2 1 0 R ID14 W Reset: x x x x x x x x ID13 ID12 ID11 ID10 ID9 ID8 ID7 Figure 9-25. Identifier Register 2 (IDR2) — Extended Identifier Mapping Table 9-28. IDR2 Register Field Descriptions — Extended Field 7:0 ID[14:7] Description Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. MC9S12KG128 Data Sheet, Rev. 1.15 300 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 7 6 5 4 3 2 1 0 R ID6 W Reset: x x x x x x x x ID5 ID4 ID3 ID2 ID1 ID0 RTR Figure 9-26. Identifier Register 3 (IDR3) — Extended Identifier Mapping Table 9-29. IDR3 Register Field Descriptions — Extended Field 7:1 ID[6:0] 0 RTR Description Extended Format Identifier — The identifiers consist of 29 bits (ID[28:0]) for the extended format. ID28 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. Remote Transmission Request — This flag reflects the status of the remote transmission request bit in the CAN frame. In the case of a receive buffer, it indicates the status of the received frame and supports the transmission of an answering frame in software. In the case of a transmit buffer, this flag defines the setting of the RTR bit to be sent. 0 Data frame 1 Remote frame 9.3.3.1.2 IDR0–IDR3 for Standard Identifier Mapping 7 6 5 4 3 2 1 0 R ID10 W Reset: x x x x x x x x ID9 ID8 ID7 ID6 ID5 ID4 ID3 Figure 9-27. Identifier Register 0 — Standard Mapping Table 9-30. IDR0 Register Field Descriptions — Standard Field 7:0 ID[10:3] Description Standard Format Identifier — The identifiers consist of 11 bits (ID[10:0]) for the standard format. ID10 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. See also ID bits in Table 9-31. 7 6 5 4 3 2 1 0 R ID2 W Reset: x x x x x x x x ID1 ID0 RTR IDE (=0) = Unused; always read ‘x’ Figure 9-28. Identifier Register 1 — Standard Mapping MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 301 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-31. IDR1 Register Field Descriptions Field 7:5 ID[2:0] 4 RTR Description Standard Format Identifier — The identifiers consist of 11 bits (ID[10:0]) for the standard format. ID10 is the most significant bit and is transmitted first on the CAN bus during the arbitration procedure. The priority of an identifier is defined to be highest for the smallest binary number. See also ID bits in Table 9-30. Remote Transmission Request — This flag reflects the status of the Remote Transmission Request bit in the CAN frame. In the case of a receive buffer, it indicates the status of the received frame and supports the transmission of an answering frame in software. In the case of a transmit buffer, this flag defines the setting of the RTR bit to be sent. 0 Data frame 1 Remote frame ID Extended — This flag indicates whether the extended or standard identifier format is applied in this buffer. In the case of a receive buffer, the flag is set as received and indicates to the CPU how to process the buffer identifier registers. In the case of a transmit buffer, the flag indicates to the MSCAN what type of identifier to send. 0 Standard format (11 bit) 1 Extended format (29 bit) 3 IDE 7 6 5 4 3 2 1 0 R W Reset: x x x x x x x x = Unused; always read ‘x’ Figure 9-29. Identifier Register 2 — Standard Mapping 7 6 5 4 3 2 1 0 R W Reset: x x x x x x x x = Unused; always read ‘x’ Figure 9-30. Identifier Register 3 — Standard Mapping 9.3.3.2 Data Segment Registers (DSR0-7) The eight data segment registers, each with bits DB[7:0], contain the data to be transmitted or received. The number of bytes to be transmitted or received is determined by the data length code in the corresponding DLR register. MC9S12KG128 Data Sheet, Rev. 1.15 302 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Module Base + 0x0004 (DSR0) 0x0005 (DSR1) 0x0006 (DSR2) 0x0007 (DSR3) 0x0008 (DSR4) 0x0009 (DSR5) 0x000A (DSR6) 0x000B (DSR7) 7 6 5 4 3 2 1 0 R DB7 W Reset: x x x x x x x x DB6 DB5 DB4 DB3 DB2 DB1 DB0 Figure 9-31. Data Segment Registers (DSR0–DSR7) — Extended Identifier Mapping Table 9-32. DSR0–DSR7 Register Field Descriptions Field 7:0 DB[7:0] Data bits 7:0 Description 9.3.3.3 Data Length Register (DLR) This register keeps the data length field of the CAN frame. 7 6 5 4 3 2 1 0 R DLC3 W Reset: x x x x x x x x DLC2 DLC1 DLC0 = Unused; always read “x” Figure 9-32. Data Length Register (DLR) — Extended Identifier Mapping Table 9-33. DLR Register Field Descriptions Field 3:0 DLC[3:0] Description Data Length Code Bits — The data length code contains the number of bytes (data byte count) of the respective message. During the transmission of a remote frame, the data length code is transmitted as programmed while the number of transmitted data bytes is always 0. The data byte count ranges from 0 to 8 for a data frame. Table 9-34 shows the effect of setting the DLC bits. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 303 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-34. Data Length Codes Data Length Code DLC3 0 0 0 0 0 0 0 0 1 DLC2 0 0 0 0 1 1 1 1 0 DLC1 0 0 1 1 0 0 1 1 0 DLC0 0 1 0 1 0 1 0 1 0 Data Byte Count 0 1 2 3 4 5 6 7 8 9.3.3.4 Transmit Buffer Priority Register (TBPR) This register defines the local priority of the associated message buffer. The local priority is used for the internal prioritization process of the MSCAN and is defined to be highest for the smallest binary number. The MSCAN implements the following internal prioritization mechanisms: • All transmission buffers with a cleared TXEx flag participate in the prioritization immediately before the SOF (start of frame) is sent. • The transmission buffer with the lowest local priority field wins the prioritization. In cases of more than one buffer having the same lowest priority, the message buffer with the lower index number wins. 7 6 5 4 3 2 1 0 R PRIO7 W Reset: 0 0 0 0 0 0 0 0 PRIO6 PRIO5 PRIO4 PRIO3 PRIO2 PRIO1 PRIO0 Figure 9-33. Transmit Buffer Priority Register (TBPR) Read: Anytime when TXEx flag is set (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 9.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”). Write: Anytime when TXEx flag is set (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 9.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”). 9.3.3.5 Time Stamp Register (TSRH–TSRL) If the TIME bit is enabled, the MSCAN will write a special time stamp to the respective registers in the active transmit or receive buffer as soon as a message has been acknowledged on the CAN bus (see MC9S12KG128 Data Sheet, Rev. 1.15 304 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”). The time stamp is written on the bit sample point for the recessive bit of the ACK delimiter in the CAN frame. In case of a transmission, the CPU can only read the time stamp after the respective transmit buffer has been flagged empty. The timer value, which is used for stamping, is taken from a free running internal CAN bit clock. A timer overrun is not indicated by the MSCAN. The timer is reset (all bits set to 0) during initialization mode. The CPU can only read the time stamp registers. 7 6 5 4 3 2 1 0 R W Reset: TSR15 TSR14 TSR13 TSR12 TSR11 TSR10 TSR9 TSR8 x x x x x x x x Figure 9-34. Time Stamp Register — High Byte (TSRH) 7 6 5 4 3 2 1 0 R W Reset: TSR7 TSR6 TSR5 TSR4 TSR3 TSR2 TSR1 TSR0 x x x x x x x x Figure 9-35. Time Stamp Register — Low Byte (TSRL) Read: Anytime when TXEx flag is set (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”) and the corresponding transmit buffer is selected in CANTBSEL (see Section 9.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”). Write: Unimplemented 9.4 9.4.1 Functional Description General This section provides a complete functional description of the MSCAN. It describes each of the features and modes listed in the introduction. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 305 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.2 Message Storage CAN Receive / Transmit Engine CPU12 Memory Mapped I/O Rx0 Rx1 Rx2 Rx3 Rx4 RXF RxBG MSCAN Receiver Tx0 RxFG CPU bus TXE0 TxBG Tx1 PRIO TXE1 TxFG MSCAN CPU bus PRIO Tx2 TXE2 Transmitter TxBG PRIO Figure 9-36. User Model for Message Buffer Organization MSCAN facilitates a sophisticated message storage system which addresses the requirements of a broad range of network applications. MC9S12KG128 Data Sheet, Rev. 1.15 306 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.2.1 Message Transmit Background Modern application layer software is built upon two fundamental assumptions: • Any CAN node is able to send out a stream of scheduled messages without releasing the CAN bus between the two messages. Such nodes arbitrate for the CAN bus immediately after sending the previous message and only release the CAN bus in case of lost arbitration. • The internal message queue within any CAN node is organized such that the highest priority message is sent out first, if more than one message is ready to be sent. The behavior described in the bullets above cannot be achieved with a single transmit buffer. That buffer must be reloaded immediately after the previous message is sent. This loading process lasts a finite amount of time and must be completed within the inter-frame sequence (IFS) to be able to send an uninterrupted stream of messages. Even if this is feasible for limited CAN bus speeds, it requires that the CPU reacts with short latencies to the transmit interrupt. A double buffer scheme de-couples the reloading of the transmit buffer from the actual message sending and, therefore, reduces the reactiveness requirements of the CPU. Problems can arise if the sending of a message is finished while the CPU re-loads the second buffer. No buffer would then be ready for transmission, and the CAN bus would be released. At least three transmit buffers are required to meet the first of the above requirements under all circumstances. The MSCAN has three transmit buffers. The second requirement calls for some sort of internal prioritization which the MSCAN implements with the “local priority” concept described in Section 9.4.2.2, “Transmit Structures.” 9.4.2.2 Transmit Structures The MSCAN triple transmit buffer scheme optimizes real-time performance by allowing multiple messages to be set up in advance. The three buffers are arranged as shown in Figure 9-36. All three buffers have a 13-byte data structure similar to the outline of the receive buffers (see Section 9.3.3, “Programmer’s Model of Message Storage”). An additional Section 9.3.3.4, “Transmit Buffer Priority Register (TBPR) contains an 8-bit local priority field (PRIO) (see Section 9.3.3.4, “Transmit Buffer Priority Register (TBPR)”). The remaining two bytes are used for time stamping of a message, if required (see Section 9.3.3.5, “Time Stamp Register (TSRH–TSRL)”). To transmit a message, the CPU must identify an available transmit buffer, which is indicated by a set transmitter buffer empty (TXEx) flag (see Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG)”). If a transmit buffer is available, the CPU must set a pointer to this buffer by writing to the CANTBSEL register (see Section 9.3.2.11, “MSCAN Transmit Buffer Selection Register (CANTBSEL)”). This makes the respective buffer accessible within the CANTXFG address space (see Section 9.3.3, “Programmer’s Model of Message Storage”). The algorithmic feature associated with the CANTBSEL register simplifies the transmit buffer selection. In addition, this scheme makes the handler software simpler because only one address area is applicable for the transmit process, and the required address space is minimized. The CPU then stores the identifier, the control bits, and the data content into one of the transmit buffers. Finally, the buffer is flagged as ready for transmission by clearing the associated TXE flag. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 307 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) The MSCAN then schedules the message for transmission and signals the successful transmission of the buffer by setting the associated TXE flag. A transmit interrupt (see Section 9.4.8.2, “Transmit Interrupt”) is generated1 when TXEx is set and can be used to drive the application software to re-load the buffer. If more than one buffer is scheduled for transmission when the CAN bus becomes available for arbitration, the MSCAN uses the local priority setting of the three buffers to determine the prioritization. For this purpose, every transmit buffer has an 8-bit local priority field (PRIO). The application software programs this field when the message is set up. The local priority reflects the priority of this particular message relative to the set of messages being transmitted from this node. The lowest binary value of the PRIO field is defined to be the highest priority. The internal scheduling process takes place whenever the MSCAN arbitrates for the CAN bus. This is also the case after the occurrence of a transmission error. When a high priority message is scheduled by the application software, it may become necessary to abort a lower priority message in one of the three transmit buffers. Because messages that are already in transmission cannot be aborted, the user must request the abort by setting the corresponding abort request bit (ABTRQ) (see Section 9.3.2.9, “MSCAN Transmitter Message Abort Request Register (CANTARQ)”.) The MSCAN then grants the request, if possible, by: 1. Setting the corresponding abort acknowledge flag (ABTAK) in the CANTAAK register. 2. Setting the associated TXE flag to release the buffer. 3. Generating a transmit interrupt. The transmit interrupt handler software can determine from the setting of the ABTAK flag whether the message was aborted (ABTAK = 1) or sent (ABTAK = 0). 9.4.2.3 Receive Structures The received messages are stored in a five stage input FIFO. The five message buffers are alternately mapped into a single memory area (see Figure 9-36). The background receive buffer (RxBG) is exclusively associated with the MSCAN, but the foreground receive buffer (RxFG) is addressable by the CPU (see Figure 9-36). This scheme simplifies the handler software because only one address area is applicable for the receive process. All receive buffers have a size of 15 bytes to store the CAN control bits, the identifier (standard or extended), the data contents, and a time stamp, if enabled (see Section 9.3.3, “Programmer’s Model of Message Storage”). The receiver full flag (RXF) (see Section 9.3.2.5, “MSCAN Receiver Flag Register (CANRFLG)”) signals the status of the foreground receive buffer. When the buffer contains a correctly received message with a matching identifier, this flag is set. On reception, each message is checked to see whether it passes the filter (see Section 9.4.3, “Identifier Acceptance Filter”) and simultaneously is written into the active RxBG. After successful reception of a valid message, the MSCAN shifts the content of RxBG into the receiver FIFO2, sets the RXF flag, and generates a receive interrupt (see Section 9.4.8.3, “Receive Interrupt”) to the CPU3. The user’s receive handler must read the received message from the RxFG and then reset the RXF flag to acknowledge the interrupt and to release the foreground buffer. A new message, which can follow immediately after the IFS 1. The transmit interrupt occurs only if not masked. A polling scheme can be applied on TXEx also. 2. Only if the RXF flag is not set. 3. The receive interrupt occurs only if not masked. A polling scheme can be applied on RXF also. MC9S12KG128 Data Sheet, Rev. 1.15 308 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) field of the CAN frame, is received into the next available RxBG. If the MSCAN receives an invalid message in its RxBG (wrong identifier, transmission errors, etc.) the actual contents of the buffer will be over-written by the next message. The buffer will then not be shifted into the FIFO. When the MSCAN module is transmitting, the MSCAN receives its own transmitted messages into the background receive buffer, RxBG, but does not shift it into the receiver FIFO, generate a receive interrupt, or acknowledge its own messages on the CAN bus. The exception to this rule is in loopback mode (see Section 9.3.2.2, “MSCAN Control Register 1 (CANCTL1)”) where the MSCAN treats its own messages exactly like all other incoming messages. The MSCAN receives its own transmitted messages in the event that it loses arbitration. If arbitration is lost, the MSCAN must be prepared to become a receiver. An overrun condition occurs when all receive message buffers in the FIFO are filled with correctly received messages with accepted identifiers and another message is correctly received from the CAN bus with an accepted identifier. The latter message is discarded and an error interrupt with overrun indication is generated if enabled (see Section 9.4.8.5, “Error Interrupt”). The MSCAN remains able to transmit messages while the receiver FIFO being filled, but all incoming messages are discarded. As soon as a receive buffer in the FIFO is available again, new valid messages will be accepted. 9.4.3 Identifier Acceptance Filter The MSCAN identifier acceptance registers (see Section 9.3.2.12, “MSCAN Identifier Acceptance Control Register (CANIDAC)”) define the acceptable patterns of the standard or extended identifier (ID[10:0] or ID[28:0]). Any of these bits can be marked ‘don’t care’ in the MSCAN identifier mask registers (see Section 9.3.2.17, “MSCAN Identifier Mask Registers (CANIDMR0–CANIDMR7)”). A filter hit is indicated to the application software by a set receive buffer full flag (RXF = 1) and three bits in the CANIDAC register (see Section 9.3.2.12, “MSCAN Identifier Acceptance Control Register (CANIDAC)”). These identifier hit flags (IDHIT[2:0]) clearly identify the filter section that caused the acceptance. They simplify the application software’s task to identify the cause of the receiver interrupt. If more than one hit occurs (two or more filters match), the lower hit has priority. A very flexible programmable generic identifier acceptance filter has been introduced to reduce the CPU interrupt loading. The filter is programmable to operate in four different modes (see Bosch CAN 2.0A/B protocol specification): • Two identifier acceptance filters, each to be applied to: — The full 29 bits of the extended identifier and to the following bits of the CAN 2.0B frame: – Remote transmission request (RTR) – Identifier extension (IDE) – Substitute remote request (SRR) — The 11 bits of the standard identifier plus the RTR and IDE bits of the CAN 2.0A/B messages1. This mode implements two filters for a full length CAN 2.0B compliant extended identifier. Figure 9-37 shows how the first 32-bit filter bank (CANIDAR0–CANIDAR3, CANIDMR0–CANIDMR3) produces a filter 0 hit. Similarly, the second filter bank (CANIDAR4–CANIDAR7, CANIDMR4–CANIDMR7) produces a filter 1 hit. 1.Although this mode can be used for standard identifiers, it is recommended to use the four or eight identifier acceptance filters for standard identifiers MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 309 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) • • • Four identifier acceptance filters, each to be applied to — a) the 14 most significant bits of the extended identifier plus the SRR and IDE bits of CAN 2.0B messages or — b) the 11 bits of the standard identifier, the RTR and IDE bits of CAN 2.0A/B messages. Figure 9-38 shows how the first 32-bit filter bank (CANIDAR0–CANIDA3, CANIDMR0–3CANIDMR) produces filter 0 and 1 hits. Similarly, the second filter bank (CANIDAR4–CANIDAR7, CANIDMR4–CANIDMR7) produces filter 2 and 3 hits. Eight identifier acceptance filters, each to be applied to the first 8 bits of the identifier. This mode implements eight independent filters for the first 8 bits of a CAN 2.0A/B compliant standard identifier or a CAN 2.0B compliant extended identifier. Figure 9-39 shows how the first 32-bit filter bank (CANIDAR0–CANIDAR3, CANIDMR0–CANIDMR3) produces filter 0 to 3 hits. Similarly, the second filter bank (CANIDAR4–CANIDAR7, CANIDMR4–CANIDMR7) produces filter 4 to 7 hits. Closed filter. No CAN message is copied into the foreground buffer RxFG, and the RXF flag is never set. IDR0 IDR0 ID21 ID3 ID20 ID2 IDR1 IDR1 ID15 IDE ID14 ID10 IDR2 IDR2 ID7 ID3 ID6 ID10 IDR3 IDR3 RTR ID3 CAN 2.0B Extended Identifier ID28 CAN 2.0A/B Standard Identifier ID10 AM7 CANIDMR0 AM0 AM7 CANIDMR1 AM0 AM7 CANIDMR2 AM0 AM7 CANIDMR3 AM0 AC7 CANIDAR0 AC0 AC7 CANIDAR1 AC0 AC7 CANIDAR2 AC0 AC7 CANIDAR3 AC0 ID Accepted (Filter 0 Hit) Figure 9-37. 32-bit Maskable Identifier Acceptance Filter MC9S12KG128 Data Sheet, Rev. 1.15 310 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) CAN 2.0B Extended Identifier CAN 2.0A/B Standard Identifier ID28 ID10 IDR0 IDR0 ID21 ID3 ID20 ID2 IDR1 IDR1 ID15 IDE ID14 ID10 IDR2 IDR2 ID7 ID3 ID6 ID10 IDR3 IDR3 RTR ID3 AM7 CANIDMR0 AM0 AM7 CANIDMR1 AM0 AC7 CANIDAR0 AC0 AC7 CANIDAR1 AC0 ID Accepted (Filter 0 Hit) AM7 CANIDMR2 AM0 AM7 CANIDMR3 AM0 AC7 CANIDAR2 AC0 AC7 CANIDAR3 AC0 ID Accepted (Filter 1 Hit) Figure 9-38. 16-bit Maskable Identifier Acceptance Filters MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 311 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) CAN 2.0B Extended Identifier ID28 CAN 2.0A/B Standard Identifier ID10 IDR0 IDR0 ID21 ID3 ID20 ID2 IDR1 IDR1 ID15 IDE ID14 ID10 IDR2 IDR2 ID7 ID3 ID6 ID10 IDR3 IDR3 RTR ID3 AM7 CIDMR0 AM0 AC7 CIDAR0 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 ID Accepted (Filter 3 Hit) Figure 9-39. 8-bit Maskable Identifier Acceptance Filters MC9S12KG128 Data Sheet, Rev. 1.15 312 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.3.1 Protocol Violation Protection The MSCAN protects the user from accidentally violating the CAN protocol through programming errors. The protection logic implements the following features: • The receive and transmit error counters cannot be written or otherwise manipulated. • All registers which control the configuration of the MSCAN cannot be modified while the MSCAN is on-line. The MSCAN has to be in Initialization Mode. The corresponding INITRQ/INITAK handshake bits in the CANCTL0/CANCTL1 registers (see Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”) serve as a lock to protect the following registers: — MSCAN control 1 register (CANCTL1) — MSCAN bus timing registers 0 and 1 (CANBTR0, CANBTR1) — MSCAN identifier acceptance control register (CANIDAC) — MSCAN identifier acceptance registers (CANIDAR0–CANIDAR7) — MSCAN identifier mask registers (CANIDMR0–CANIDMR7) • The TXCAN pin is immediately forced to a recessive state when the MSCAN goes into the power down mode or initialization mode (see Section 9.4.6.6, “MSCAN Power Down Mode,” and Section 9.4.6.5, “MSCAN Initialization Mode”). • The MSCAN enable bit (CANE) is writable only once in normal system operation modes, which provides further protection against inadvertently disabling the MSCAN. 9.4.3.2 Clock System Figure 9-40 shows the structure of the MSCAN clock generation circuitry. MSCAN Bus Clock CANCLK CLKSRC Prescaler (1 .. 64) Time quanta clock (Tq) CLKSRC Oscillator Clock Figure 9-40. MSCAN Clocking Scheme The clock source bit (CLKSRC) in the CANCTL1 register (9.3.2.2/9-278) defines whether the internal CANCLK is connected to the output of a crystal oscillator (oscillator clock) or to the bus clock. The clock source has to be chosen such that the tight oscillator tolerance requirements (up to 0.4%) of the CAN protocol are met. Additionally, for high CAN bus rates (1 Mbps), a 45% to 55% duty cycle of the clock is required. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 313 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) If the bus clock is generated from a PLL, it is recommended to select the oscillator clock rather than the bus clock due to jitter considerations, especially at the faster CAN bus rates. For microcontrollers without a clock and reset generator (CRG), CANCLK is driven from the crystal oscillator (oscillator clock). A programmable prescaler generates the time quanta (Tq) clock from CANCLK. A time quantum is the atomic unit of time handled by the MSCAN. Eqn. 9-2 f CANCLK = ----------------------------------------------------Tq ( Prescaler value ) A bit time is subdivided into three segments as described in the Bosch CAN specification. (see Figure 9-41): • SYNC_SEG: This segment has a fixed length of one time quantum. Signal edges are expected to happen within this section. • Time Segment 1: This segment includes the PROP_SEG and the PHASE_SEG1 of the CAN standard. It can be programmed by setting the parameter TSEG1 to consist of 4 to 16 time quanta. • Time Segment 2: This segment represents the PHASE_SEG2 of the CAN standard. It can be programmed by setting the TSEG2 parameter to be 2 to 8 time quanta long. Eqn. 9-3 f Tq Bit Rate = -------------------------------------------------------------------------------( number of Time Quanta ) NRZ Signal SYNC_SEG Time Segment 1 (PROP_SEG + PHASE_SEG1) 4 ... 16 8 ... 25 Time Quanta = 1 Bit Time Time Segment 2 (PHASE_SEG2) 2 ... 8 1 Transmit Point Sample Point (single or triple sampling) Figure 9-41. Segments within the Bit Time MC9S12KG128 Data Sheet, Rev. 1.15 314 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-35. Time Segment Syntax Syntax SYNC_SEG Transmit Point Description System expects transitions to occur on the CAN bus during this period. A node in transmit mode transfers a new value to the CAN bus at this point. A node in receive mode samples the CAN bus at this point. If the three samples per bit option is selected, then this point marks the position of the third sample. Sample Point The synchronization jump width (see the Bosch CAN specification for details) can be programmed in a range of 1 to 4 time quanta by setting the SJW parameter. The SYNC_SEG, TSEG1, TSEG2, and SJW parameters are set by programming the MSCAN bus timing registers (CANBTR0, CANBTR1) (see Section 9.3.2.3, “MSCAN Bus Timing Register 0 (CANBTR0)” and Section 9.3.2.4, “MSCAN Bus Timing Register 1 (CANBTR1)”). Table 9-36 gives an overview of the CAN compliant segment settings and the related parameter values. NOTE It is the user’s responsibility to ensure the bit time settings are in compliance with the CAN standard. Table 9-36. CAN Standard Compliant Bit Time Segment Settings Time Segment 1 5 .. 10 4 .. 11 5 .. 12 6 .. 13 7 .. 14 8 .. 15 9 .. 16 TSEG1 4 .. 9 3 .. 10 4 .. 11 5 .. 12 6 .. 13 7 .. 14 8 .. 15 Time Segment 2 2 3 4 5 6 7 8 TSEG2 1 2 3 4 5 6 7 Synchronization Jump Width 1 .. 2 1 .. 3 1 .. 4 1 .. 4 1 .. 4 1 .. 4 1 .. 4 SJW 0 .. 1 0 .. 2 0 .. 3 0 .. 3 0 .. 3 0 .. 3 0 .. 3 9.4.4 Timer Link The MSCAN generates an internal time stamp whenever a valid frame is received or transmitted and the TIME bit is enabled. Because the CAN specification defines a frame to be valid if no errors occur before the end of frame (EOF) field is transmitted successfully, the actual value of an internal timer is written at EOF to the appropriate time stamp position within the transmit buffer. For receive frames, the time stamp is written to the receive buffer. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 315 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.5 9.4.5.1 Modes of Operation Normal Modes The MSCAN module behaves as described within this specification in all normal system operation modes. 9.4.5.2 Special Modes The MSCAN module behaves as described within this specification in all special system operation modes. 9.4.5.3 Emulation Modes In all emulation modes, the MSCAN module behaves just like normal system operation modes as described within this specification. 9.4.5.4 Listen-Only Mode In an optional CAN bus monitoring mode (listen-only), the CAN node is able to receive valid data frames and valid remote frames, but it sends only “recessive” bits on the CAN bus. In addition, it cannot start a transmision. If the MAC sub-layer is required to send a “dominant” bit (ACK bit, overload flag, or active error flag), the bit is rerouted internally so that the MAC sub-layer monitors this “dominant” bit, although the CAN bus may remain in recessive state externally. 9.4.5.5 Security Modes The MSCAN module has no security features. 9.4.6 Low-Power Options If the MSCAN is disabled (CANE = 0), the MSCAN clocks are stopped for power saving. If the MSCAN is enabled (CANE = 1), the MSCAN has two additional modes with reduced power consumption, compared to normal mode: sleep and power down mode. In sleep mode, power consumption is reduced by stopping all clocks except those to access the registers from the CPU side. In power down mode, all clocks are stopped and no power is consumed. Table 9-37 summarizes the combinations of MSCAN and CPU modes. A particular combination of modes is entered by the given settings on the CSWAI and SLPRQ/SLPAK bits. For all modes, an MSCAN wake-up interrupt can occur only if the MSCAN is in sleep mode (SLPRQ = 1 and SLPAK = 1), wake-up functionality is enabled (WUPE = 1), and the wake-up interrupt is enabled (WUPIE = 1). MC9S12KG128 Data Sheet, Rev. 1.15 316 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) Table 9-37. CPU vs. MSCAN Operating Modes MSCAN Mode CPU Mode Normal Sleep CSWAI = X1 SLPRQ = 0 SLPAK = 0 CSWAI = 0 SLPRQ = 0 SLPAK = 0 CSWAI = X SLPRQ = 1 SLPAK = 1 CSWAI = 0 SLPRQ = 1 SLPAK = 1 CSWAI = 1 SLPRQ = X SLPAK = X CSWAI = X SLPRQ = X SLPAK = X Power Down Reduced Power Consumption Disabled (CANE=0) CSWAI = X SLPRQ = X SLPAK = X CSWAI = X SLPRQ = X SLPAK = X CSWAI = X SLPRQ = X SLPAK = X RUN WAIT STOP 1 ‘X’ means don’t care. 9.4.6.1 Operation in Run Mode As shown in Table 9-37, only MSCAN sleep mode is available as low power option when the CPU is in run mode. 9.4.6.2 Operation in Wait Mode The WAI instruction puts the MCU in a low power consumption stand-by mode. If the CSWAI bit is set, additional power can be saved in power down mode because the CPU clocks are stopped. After leaving this power down mode, the MSCAN restarts its internal controllers and enters normal mode again. While the CPU is in wait mode, the MSCAN can be operated in normal mode and generate interrupts (registers can be accessed via background debug mode). The MSCAN can also operate in any of the low-power modes depending on the values of the SLPRQ/SLPAK and CSWAI bits as seen in Table 9-37. 9.4.6.3 Operation in Stop Mode The STOP instruction puts the MCU in a low power consumption stand-by mode. In stop mode, the MSCAN is set in power down mode regardless of the value of the SLPRQ/SLPAK and CSWAI bits Table 9-37. 9.4.6.4 MSCAN Sleep Mode The CPU can request the MSCAN to enter this low power mode by asserting the SLPRQ bit in the CANCTL0 register. The time when the MSCAN enters sleep mode depends on a fixed synchronization delay and its current activity: MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 317 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) • • • If there are one or more message buffers scheduled for transmission (TXEx = 0), the MSCAN will continue to transmit until all transmit message buffers are empty (TXEx = 1, transmitted successfully or aborted) and then goes into sleep mode. If the MSCAN is receiving, it continues to receive and goes into sleep mode as soon as the CAN bus next becomes idle. If the MSCAN is neither transmitting nor receiving, it immediately goes into sleep mode. Bus Clock Domain CAN Clock Domain SLPRQ Flag SLPRQ CPU Sleep Request SYNC sync. SLPRQ SLPAK Flag sync. SLPAK SYNC SLPAK MSCAN in Sleep Mode Figure 9-42. Sleep Request / Acknowledge Cycle NOTE The application software must avoid setting up a transmission (by clearing one or more TXEx flag(s)) and immediately request sleep mode (by setting SLPRQ). Whether the MSCAN starts transmitting or goes into sleep mode directly depends on the exact sequence of operations. If sleep mode is active, the SLPRQ and SLPAK bits are set (Figure 9-42). The application software must use SLPAK as a handshake indication for the request (SLPRQ) to go into sleep mode. When in sleep mode (SLPRQ = 1 and SLPAK = 1), the MSCAN stops its internal clocks. However, clocks that allow register accesses from the CPU side continue to run. If the MSCAN is in bus-off state, it stops counting the 128 occurrences of 11 consecutive recessive bits due to the stopped clocks. The TXCAN pin remains in a recessive state. If RXF = 1, the message can be read and RXF can be cleared. Shifting a new message into the foreground buffer of the receiver FIFO (RxFG) does not take place while in sleep mode. It is possible to access the transmit buffers and to clear the associated TXE flags. No message abort takes place while in sleep mode. If the WUPE bit in CANCLT0 is not asserted, the MSCAN will mask any activity it detects on CAN. The RXCAN pin is therefore held internally in a recessive state. This locks the MSCAN in sleep mode (Figure 9-43). MC9S12KG128 Data Sheet, Rev. 1.15 318 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) The MSCAN is able to leave sleep mode (wake up) only when: • CAN bus activity occurs and WUPE = 1 or • the CPU clears the SLPRQ bit NOTE The CPU cannot clear the SLPRQ bit before sleep mode (SLPRQ = 1 and SLPAK = 1) is active. After wake-up, the MSCAN waits for 11 consecutive recessive bits to synchronize to the CAN bus. As a consequence, if the MSCAN is woken-up by a CAN frame, this frame is not received. The receive message buffers (RxFG and RxBG) contain messages if they were received before sleep mode was entered. All pending actions will be executed upon wake-up; copying of RxBG into RxFG, message aborts and message transmissions. If the MSCAN remains in bus-off state after sleep mode was exited, it continues counting the 128 occurrences of 11 consecutive recessive bits. CAN Activity StartUp Wait for Idle CAN Activity SLPRQ (CAN Activity & WUPE) | SLPRQ CAN Activity & SLPRQ Idle Sleep (CAN Activity & WUPE) | CAN Activity & SLPRQ CAN Activity CAN Activity Tx/Rx Message Active CAN Activity Figure 9-43. Simplified State Transitions for Entering/Leaving Sleep Mode MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 319 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.6.5 MSCAN Initialization Mode In initialization mode, any on-going transmission or reception is immediately aborted and synchronization to the CAN bus is lost, potentially causing CAN protocol violations. To protect the CAN bus system from fatal consequences of violations, the MSCAN immediately drives the TXCAN pin into a recessive state. NOTE The user is responsible for ensuring that the MSCAN is not active when initialization mode is entered. The recommended procedure is to bring the MSCAN into sleep mode (SLPRQ = 1 and SLPAK = 1) before setting the INITRQ bit in the CANCTL0 register. Otherwise, the abort of an on-going message can cause an error condition and can impact other CAN bus devices. In initialization mode, the MSCAN is stopped. However, interface registers remain accessible. This mode is used to reset the CANCTL0, CANRFLG, CANRIER, CANTFLG, CANTIER, CANTARQ, CANTAAK, and CANTBSEL registers to their default values. In addition, the MSCAN enables the configuration of the CANBTR0, CANBTR1 bit timing registers; CANIDAC; and the CANIDAR, CANIDMR message filters. See Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0),” for a detailed description of the initialization mode. Bus Clock Domain CAN Clock Domain INIT Flag INITRQ CPU Init Request SYNC sync. INITRQ INITAK Flag sync. INITAK SYNC INITAK Figure 9-44. Initialization Request/Acknowledge Cycle Due to independent clock domains within the MSCAN, INITRQ must be synchronized to all domains by using a special handshake mechanism. This handshake causes additional synchronization delay (see Section Figure 9-44., “Initialization Request/Acknowledge Cycle”). If there is no message transfer ongoing on the CAN bus, the minimum delay will be two additional bus clocks and three additional CAN clocks. When all parts of the MSCAN are in initialization mode, the INITAK flag is set. The application software must use INITAK as a handshake indication for the request (INITRQ) to go into initialization mode. NOTE The CPU cannot clear INITRQ before initialization mode (INITRQ = 1 and INITAK = 1) is active. MC9S12KG128 Data Sheet, Rev. 1.15 320 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.6.6 MSCAN Power Down Mode The MSCAN is in power down mode (Table 9-37) when • CPU is in stop mode or • CPU is in wait mode and the CSWAI bit is set When entering the power down mode, the MSCAN immediately stops all ongoing transmissions and receptions, potentially causing CAN protocol violations. To protect the CAN bus system from fatal consequences of violations to the above rule, the MSCAN immediately drives the TXCAN pin into a recessive state. NOTE The user is responsible for ensuring that the MSCAN is not active when power down mode is entered. The recommended procedure is to bring the MSCAN into Sleep mode before the STOP or WAI instruction (if CSWAI is set) is executed. Otherwise, the abort of an ongoing message can cause an error condition and impact other CAN bus devices. In power down mode, all clocks are stopped and no registers can be accessed. If the MSCAN was not in sleep mode before power down mode became active, the module performs an internal recovery cycle after powering up. This causes some fixed delay before the module enters normal mode again. 9.4.6.7 Programmable Wake-Up Function The MSCAN can be programmed to wake up the MSCAN as soon as CAN bus activity is detected (see control bit WUPE in Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”). The sensitivity to existing CAN bus action can be modified by applying a low-pass filter function to the RXCAN input line while in sleep mode (see control bit WUPM in Section 9.3.2.2, “MSCAN Control Register 1 (CANCTL1)”). This feature can be used to protect the MSCAN from wake-up due to short glitches on the CAN bus lines. Such glitches can result from—for example—electromagnetic interference within noisy environments. 9.4.7 Reset Initialization The reset state of each individual bit is listed in Section 9.3.2, “Register Descriptions,” which details all the registers and their bit-fields. 9.4.8 Interrupts This section describes all interrupts originated by the MSCAN. It documents the enable bits and generated flags. Each interrupt is listed and described separately. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 321 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) 9.4.8.1 Description of Interrupt Operation The MSCAN supports four interrupt vectors (see Table 9-38), any of which can be individually masked (for details see sections from Section 9.3.2.6, “MSCAN Receiver Interrupt Enable Register (CANRIER),” to Section 9.3.2.8, “MSCAN Transmitter Interrupt Enable Register (CANTIER)”). NOTE The dedicated interrupt vector addresses are defined in the Resets and Interrupts chapter. Table 9-38. Interrupt Vectors Interrupt Source Wake-Up Interrupt (WUPIF) Error Interrupts Interrupt (CSCIF, OVRIF) Receive Interrupt (RXF) Transmit Interrupts (TXE[2:0]) CCR Mask I bit I bit I bit I bit Local Enable CANRIER (WUPIE) CANRIER (CSCIE, OVRIE) CANRIER (RXFIE) CANTIER (TXEIE[2:0]) 9.4.8.2 Transmit Interrupt At least one of the three transmit buffers is empty (not scheduled) and can be loaded to schedule a message for transmission. The TXEx flag of the empty message buffer is set. 9.4.8.3 Receive Interrupt A message is successfully received and shifted into the foreground buffer (RxFG) of the receiver FIFO. This interrupt is generated immediately after receiving the EOF symbol. The RXF flag is set. If there are multiple messages in the receiver FIFO, the RXF flag is set as soon as the next message is shifted to the foreground buffer. 9.4.8.4 Wake-Up Interrupt A wake-up interrupt is generated if activity on the CAN bus occurs during MSCN internal sleep mode. WUPE (see Section 9.3.2.1, “MSCAN Control Register 0 (CANCTL0)”) must be enabled. 9.4.8.5 Error Interrupt An error interrupt is generated if an overrun of the receiver FIFO, error, warning, or bus-off condition occurrs. Section 9.3.2.5, “MSCAN Receiver Flag Register (CANRFLG) indicates one of the following conditions: • Overrun — An overrun condition of the receiver FIFO as described in Section 9.4.2.3, “Receive Structures,” occurred. • CAN Status Change — The actual value of the transmit and receive error counters control the CAN bus state of the MSCAN. As soon as the error counters skip into a critical range (Tx/Rx-warning, Tx/Rx-error, bus-off) the MSCAN flags an error condition. The status change, which caused the error condition, is indicated by the TSTAT and RSTAT flags (see Section 9.3.2.5, MC9S12KG128 Data Sheet, Rev. 1.15 322 Freescale Semiconductor Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) “MSCAN Receiver Flag Register (CANRFLG)” and Section 9.3.2.6, “MSCAN Receiver Interrupt Enable Register (CANRIER)”). 9.4.8.6 Interrupt Acknowledge Interrupts are directly associated with one or more status flags in either the Section 9.3.2.5, “MSCAN Receiver Flag Register (CANRFLG)” or the Section 9.3.2.7, “MSCAN Transmitter Flag Register (CANTFLG).” Interrupts are pending as long as one of the corresponding flags is set. The flags in CANRFLG and CANTFLG must be reset within the interrupt handler to handshake the interrupt. The flags are reset by writing a 1 to the corresponding bit position. A flag cannot be cleared if the respective condition prevails. NOTE It must be guaranteed that the CPU clears only the bit causing the current interrupt. For this reason, bit manipulation instructions (BSET) must not be used to clear interrupt flags. These instructions may cause accidental clearing of interrupt flags which are set after entering the current interrupt service routine. 9.4.8.7 Recovery from Stop or Wait The MSCAN can recover from stop or wait via the wake-up interrupt. This interrupt can only occur if the MSCAN was in sleep mode (SLPRQ = 1 and SLPAK = 1) before entering power down mode, the wake-up option is enabled (WUPE = 1), and the wake-up interrupt is enabled (WUPIE = 1). 9.5 9.5.1 Initialization/Application Information MSCAN initialization The procedure to initially start up the MSCAN module out of reset is as follows: 1. Assert CANE 2. Write to the configuration registers in initialization mode 3. Clear INITRQ to leave initialization mode and enter normal mode If the configuration of registers which are writable in initialization mode needs to be changed only when the MSCAN module is in normal mode: 1. Bring the module into sleep mode by setting SLPRQ and awaiting SLPAK to assert after the CAN bus becomes idle. 2. Enter initialization mode: assert INITRQ and await INITAK 3. Write to the configuration registers in initialization mode 4. Clear INITRQ to leave initialization mode and continue in normal mode MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 323 Chapter 9 Freescale’s Scalable Controller Area Network (MSCANV2) MC9S12KG128 Data Sheet, Rev. 1.15 324 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) 10.1 Introduction This block guide provide an overview of serial communication interface (SCI) module. The SCI allows asynchronous serial communications with peripheral devices and other CPUs. 10.1.1 Glossary IRQ — Interrupt Request LSB — Least Significant Bit MSB — Most Significant Bit NRZ — Non-Return-to-Zero RZI — Return-to-Zero-Inverted RXD — Receive Pin SCI — Serial Communication Interface TXD — Transmit Pin 10.1.2 Features The SCI includes these distinctive features: • Full-duplex operation • Standard mark/space non-return-to-zero (NRZ) format • 13-bit baud rate selection • Programmable 8-bit or 9-bit data format • Separately enabled transmitter and receiver • Programmable transmitter output parity • Two receiver wake up methods: — Idle line wake-up — Address mark wake-up • Interrupt-driven operation with eight flags: — Transmitter empty — Transmission complete MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 325 Chapter 10 Serial Communications Interface (SCIV1) • • • — Receiver full — Idle receiver input — Receiver overrun — Noise error — Framing error — Parity error Receiver framing error detection Hardware parity checking 1/16 bit-time noise detection 10.1.3 Modes of Operation The SCI operation is the same independent of device resource mapping and bus interface mode. Different power modes are available to facilitate power saving. 10.1.3.1 Run Mode Normal mode of operation. 10.1.3.2 Wait Mode SCI operation in wait mode depends on the state of the SCISWAI bit in the SCI control register 1 (SCICR1). • If SCISWAI is clear, the SCI operates normally when the CPU is in wait mode. • If SCISWAI is set, SCI clock generation ceases and the SCI module enters a power-conservation state when the CPU is in wait mode. Setting SCISWAI does not affect the state of the receiver enable bit, RE, or the transmitter enable bit, TE. • If SCISWAI is set, any transmission or reception in progress stops at wait mode entry. The transmission or reception resumes when either an internal or external interrupt brings the CPU out of wait mode. Exiting wait mode by reset aborts any transmission or reception in progress and resets the SCI. 10.1.3.3 Stop Mode The SCI is inactive during stop mode for reduced power consumption. The STOP instruction does not affect the SCI register states, but the SCI module clock will be disabled. The SCI operation resumes from where it left off after an external interrupt brings the CPU out of stop mode. Exiting stop mode by reset aborts any transmission or reception in progress and resets the SCI. 10.1.4 Block Diagram Figure 10-1 is a high level block diagram of the SCI module, showing the interaction of various functional blocks. MC9S12KG128 Data Sheet, Rev. 1.15 326 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) SCI DATA REGISTER IRQ GENERATION IDLE IRQ RX DATA IN RECEIVE SHIFT REGISTER BUS CLOCK RECEIVE & WAKE UP CONTROL RDR/OR IRQ BAUD GENERATOR ÷16 DATA FORMAT CONTROL TRANSMIT CONTROL IRQ GENERATION TDRE IRQ TRANSMIT SHIFT REGISTER TC IRQ SCI DATA REGISTER TXDATA OUT Figure 10-1. SCI Block Diagram 10.2 External Signal Description The SCI module has a total of two external pins: 10.2.1 TXD-SCI Transmit Pin This pin serves as transmit data output of SCI. 10.2.2 RXD-SCI Receive Pin This pin serves as receive data input of the SCI. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 327 ORING IRQ TO CPU Chapter 10 Serial Communications Interface (SCIV1) 10.3 Memory Map and Registers This section provides a detailed description of all memory and registers. 10.3.1 Module Memory Map The memory map for the SCI module is given below in Figure 10-2. The Address listed for each register is the address offset. The total address for each register is the sum of the base address for the SCI module and the address offset for each register. Address 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 Name SCIBDH SCIBDL SCICR1 SCICR2 SCISR1 SCISR2 SCIDRH SCIDRL R W R W R W R W R W R W R W R W Bit 7 0 6 0 5 0 4 SBR12 SBR4 M ILIE IDLE 0 0 R4 T4 3 SBR11 SBR3 WAKE TE OR 0 0 R3 T3 2 SBR10 SBR2 ILT RE NF 1 SBR9 SBR1 PE RWU FE Bit 0 SBR8 SBR0 PT SBK PF RAF 0 R0 T0 SBR7 LOOPS TIE TDRE 0 R8 R7 T7 SBR6 SCISWAI TCIE TC 0 SBR5 RSRC RIE RDRF 0 0 R5 T5 BRK13 0 R2 T2 TXDIR 0 R1 T1 T8 R6 T6 = Unimplemented or Reserved Figure 10-2. SCI Register Summary 10.3.2 Register Descriptions This section consists of register descriptions in address order. Each description includes a standard register diagram with an associated figure number. Writes to a reserved register location do not have any effect and reads of these locations return a zero. Details of register bit and field function follow the register diagrams, in bit order. MC9S12KG128 Data Sheet, Rev. 1.15 328 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) 10.3.2.1 SCI Baud Rate Registers (SCIBDH and SCHBDL) Module Base + 0x_0000 7 6 5 4 3 2 1 0 R W Reset 0 0 0 SBR12 SBR11 0 SBR10 0 SBR9 0 SBR8 0 0 0 0 0 Module Base + 0x_0001 7 6 5 4 3 2 1 0 R SBR7 W Reset 0 0 0 0 0 1 0 0 SBR6 SBR5 SBR4 SBR3 SBR2 SBR1 SBR0 = Unimplemented or Reserved Figure 10-3. SCI Baud Rate Registers (SCIBDH and SCIBDL) The SCI Baud Rate Register is used by the counter to determine the baud rate of the SCI. The formula for calculating the baud rate is: SCI baud rate = SCI module clock / (16 x BR) where: BR is the content of the SCI baud rate registers, bits SBR12 through SBR0. The baud rate registers can contain a value from 1 to 8191. Read: Anytime. If only SCIBDH is written to, a read will not return the correct data until SCIBDL is written to as well, following a write to SCIBDH. Write: Anytime Table 10-1. SCIBDH AND SCIBDL Field Descriptions Field 4–0 7–0 SBR[12:0] Description SCI Baud Rate Bits — The baud rate for the SCI is determined by these 13 bits. Note: The baud rate generator is disabled until the TE bit or the RE bit is set for the first time after reset. The baud rate generator is disabled when BR = 0. Writing to SCIBDH has no effect without writing to SCIBDL, since writing to SCIBDH puts the data in a temporary location until SCIBDL is written to. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 329 Chapter 10 Serial Communications Interface (SCIV1) 10.3.2.2 SCI Control Register 1 (SCICR1) Module Base + 0x_0002 7 6 5 4 3 2 1 0 R LOOPS W Reset 0 0 0 0 0 0 0 0 SCISWAI RSRC M WAKE ILT PE PT Figure 10-4. SCI Control Register 1 (SCICR1) Read: Anytime Write: Anytime Table 10-2. SCICR1 Field Descriptions Field 7 LOOPS Description Loop Select Bit — LOOPS enables loop operation. In loop operation, the RXD pin is disconnected from the SCI and the transmitter output is internally connected to the receiver input. Both the transmitter and the receiver must be enabled to use the loop function.See Table 10-3. 0 Normal operation enabled 1 Loop operation enabled Note: The receiver input is determined by the RSRC bit. SCI Stop in Wait Mode Bit — SCISWAI disables the SCI in wait mode. 0 SCI enabled in wait mode 1 SCI disabled in wait mode Receiver Source Bit — When LOOPS = 1, the RSRC bit determines the source for the receiver shift register input. 0 Receiver input internally connected to transmitter output 1 Receiver input connected externally to transmitter Data Format Mode Bit — MODE determines whether data characters are eight or nine bits long. 0 One start bit, eight data bits, one stop bit 1 One start bit, nine data bits, one stop bit Wakeup Condition Bit — WAKE determines which condition wakes up the SCI: a logic 1 (address mark) in the most significant bit position of a received data character or an idle condition on the RXD. 0 Idle line wakeup 1 Address mark wakeup Idle Line Type Bit — ILT determines when the receiver starts counting logic 1s as idle character bits. The counting begins either after the start bit or after the stop bit. If the count begins after the start bit, then a string of logic 1s preceding the stop bit may cause false recognition of an idle character. Beginning the count after the stop bit avoids false idle character recognition, but requires properly synchronized transmissions. 0 Idle character bit count begins after start bit 1 Idle character bit count begins after stop bit Parity Enable Bit — PE enables the parity function. When enabled, the parity function inserts a parity bit in the most significant bit position. 0 Parity function disabled 1 Parity function enabled Parity Type Bit — PT determines whether the SCI generates and checks for even parity or odd parity. With even parity, an even number of 1s clears the parity bit and an odd number of 1s sets the parity bit. With odd parity, an odd number of 1s clears the parity bit and an even number of 1s sets the parity bit. 0 Even parity 1 Odd parity 6 SCISWAI 5 RSRC 4 M 3 WAKE 2 ILT 1 PE 0 PT MC9S12KG128 Data Sheet, Rev. 1.15 330 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) Table 10-3. Loop Functions LOOPS 0 1 1 RSRC x 0 1 Normal operation Loop mode with Rx input internally connected to Tx output Single-wire mode with Rx input connected to TXD Function 10.3.2.3 SCI Control Register 2 (SCICR2) Module Base + 0x_0003 7 6 5 4 3 2 1 0 R TIE W Reset 0 0 0 0 0 0 0 0 TCIE RIE ILIE TE RE RWU SBK Figure 10-5. SCI Control Register 2 (SCICR2) Read: Anytime Write: Anytime Table 10-4. SCICR2 Field Descriptions Field 7 TIE Description Transmitter Interrupt Enable Bit — TIE enables the transmit data register empty flag, TDRE, to generate interrupt requests. 0 TDRE interrupt requests disabled 1 TDRE interrupt requests enabled Transmission Complete Interrupt Enable Bit — TCIE enables the transmission complete flag, TC, to generate interrupt requests. 0 TC interrupt requests disabled 1 TC interrupt requests enabled Receiver Full Interrupt Enable Bit — RIE enables the receive data register full flag, RDRF, or the overrun flag, OR, to generate interrupt requests. 0 RDRF and OR interrupt requests disabled 1 RDRF and OR interrupt requests enabled Idle Line Interrupt Enable Bit — ILIE enables the idle line flag, IDLE, to generate interrupt requests. 0 IDLE interrupt requests disabled 1 IDLE interrupt requests enabled Transmitter Enable Bit — TE enables the SCI transmitter and configures the TXD pin as being controlled by the SCI. The TE bit can be used to queue an idle preamble. 0 Transmitter disabled 1 Transmitter enabled Receiver Enable Bit — RE enables the SCI receiver. 0 Receiver disabled 1 Receiver enabled 6 TCIE 5 RIE 4 ILIE 3 TE 2 RE MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 331 Chapter 10 Serial Communications Interface (SCIV1) Table 10-4. SCICR2 Field Descriptions (continued) Field 1 RWU Description Receiver Wakeup Bit — Standby state 0 Normal operation. 1 RWU enables the wakeup function and inhibits further receiver interrupt requests. Normally, hardware wakes the receiver by automatically clearing RWU. Send Break Bit — Toggling SBK sends one break character (10 or 11 logic 0s, respectively 13 or 14 logics 0s if BRK13 is set). Toggling implies clearing the SBK bit before the break character has finished transmitting. As long as SBK is set, the transmitter continues to send complete break characters (10 or 11 bits, respectively 13 or 14 bits). 0 No break characters 1 Transmit break characters 0 SBK 10.3.2.4 SCI Status Register 1 (SCISR1) The SCISR1 and SCISR2 registers provides inputs to the MCU for generation of SCI interrupts. Also, these registers can be polled by the MCU to check the status of these bits. The flag-clearing procedures require that the status register be read followed by a read or write to the SCI Data Register.It is permissible to execute other instructions between the two steps as long as it does not compromise the handling of I/O, but the order of operations is important for flag clearing. Module Base + 0x_0004 7 6 5 4 3 2 1 0 R W Reset TDRE TC RDRF IDLE OR NF FE PF 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 10-6. SCI Status Register 1 (SCISR1) Read: Anytime Write: Has no meaning or effect Table 10-5. SCISR1 Field Descriptions Field 7 TDRE Description Transmit Data Register Empty Flag — TDRE is set when the transmit shift register receives a byte from the SCI data register. When TDRE is 1, the transmit data register (SCIDRH/L) is empty and can receive a new value to transmit.Clear TDRE by reading SCI status register 1 (SCISR1), with TDRE set and then writing to SCI data register low (SCIDRL). 0 No byte transferred to transmit shift register 1 Byte transferred to transmit shift register; transmit data register empty Transmit Complete Flag — TC is set low when there is a transmission in progress or when a preamble or break character is loaded. TC is set high when the TDRE flag is set and no data, preamble, or break character is being transmitted.When TC is set, the TXD out signal becomes idle (logic 1). Clear TC by reading SCI status register 1 (SCISR1) with TC set and then writing to SCI data register low (SCIDRL). TC is cleared automatically when data, preamble, or break is queued and ready to be sent. TC is cleared in the event of a simultaneous set and clear of the TC flag (transmission not complete). 0 Transmission in progress 1 No transmission in progress MC9S12KG128 Data Sheet, Rev. 1.15 332 Freescale Semiconductor 6 TC Chapter 10 Serial Communications Interface (SCIV1) Table 10-5. SCISR1 Field Descriptions (continued) Field 5 RDRF Description Receive Data Register Full Flag — RDRF is set when the data in the receive shift register transfers to the SCI data register. Clear RDRF by reading SCI status register 1 (SCISR1) with RDRF set and then reading SCI data register low (SCIDRL). 0 Data not available in SCI data register 1 Received data available in SCI data register Idle Line Flag — IDLE is set when 10 consecutive logic 1s (if M=0) or 11 consecutive logic 1s (if M=1) appear on the receiver input. Once the IDLE flag is cleared, a valid frame must again set the RDRF flag before an idle condition can set the IDLE flag.Clear IDLE by reading SCI status register 1 (SCISR1) with IDLE set and then reading SCI data register low (SCIDRL). 0 Receiver input is either active now or has never become active since the IDLE flag was last cleared 1 Receiver input has become idle Note: When the receiver wakeup bit (RWU) is set, an idle line condition does not set the IDLE flag. Overrun Flag — OR is set when software fails to read the SCI data register before the receive shift register receives the next frame. The OR bit is set immediately after the stop bit has been completely received for the second frame. The data in the shift register is lost, but the data already in the SCI data registers is not affected. Clear OR by reading SCI status register 1 (SCISR1) with OR set and then reading SCI data register low (SCIDRL). 0 No overrun 1 Overrun Note: OR flag may read back as set when RDRF flag is clear. This may happen if the following sequence of events occurs: 1. After the first frame is received, read status register SCISR1 (returns RDRF set and OR flag clear); 2. Receive second frame without reading the first frame in the data register (the second frame is not received and OR flag is set); 3. Read data register SCIDRL (returns first frame and clears RDRF flag in the status register); 4. Read status register SCISR1 (returns RDRF clear and OR set). Event 3 may be at exactly the same time as event 2 or any time after. When this happens, a dummy SCIDRL read following event 4 will be required to clear the OR flag if further frames are to be received. Noise Flag — NF is set when the SCI detects noise on the receiver input. NF bit is set during the same cycle as the RDRF flag but does not get set in the case of an overrun. Clear NF by reading SCI status register 1(SCISR1), and then reading SCI data register low (SCIDRL). 0 No noise 1 Noise Framing Error Flag — FE is set when a logic 0 is accepted as the stop bit. FE bit is set during the same cycle as the RDRF flag but does not get set in the case of an overrun. FE inhibits further data reception until it is cleared. Clear FE by reading SCI status register 1 (SCISR1) with FE set and then reading the SCI data register low (SCIDRL). 0 No framing error 1 Framing error Parity Error Flag — PF is set when the parity enable bit (PE) is set and the parity of the received data does not match the parity type bit (PT). PF bit is set during the same cycle as the RDRF flag but does not get set in the case of an overrun. Clear PF by reading SCI status register 1 (SCISR1), and then reading SCI data register low (SCIDRL). 0 No parity error 1 Parity error 4 IDLE 3 OR 2 NF 1 FE 0 PF MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 333 Chapter 10 Serial Communications Interface (SCIV1) 10.3.2.5 SCI Status Register 2 (SCISR2) Module Base + 0x_0005 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 BK13 TXDIR 0 RAF 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 10-7. SCI Status Register 2 (SCISR2) Read: Anytime Write: Anytime; writing accesses SCI status register 2; writing to any bits except TXDIR and BRK13 (SCISR2[1] & [2]) has no effect Table 10-6. SCISR2 Field Descriptions Field 2 BK13 Description Break Transmit Character Length — This bit determines whether the transmit break character is 10 or 11 bit respectively 13 or 14 bits long. The detection of a framing error is not affected by this bit. 0 Break Character is 10 or 11 bit long 1 Break character is 13 or 14 bit long Transmitter Pin Data Direction in Single-Wire Mode. — This bit determines whether the TXD pin is going to be used as an input or output, in the Single-Wire mode of operation. This bit is only relevant in the Single-Wire mode of operation. 0 TXD pin to be used as an input in Single-Wire mode 1 TXD pin to be used as an output in Single-Wire mode Receiver Active Flag — RAF is set when the receiver detects a logic 0 during the RT1 time period of the start bit search. RAF is cleared when the receiver detects an idle character. 0 No reception in progress 1 Reception in progress 1 TXDIR 0 RAF MC9S12KG128 Data Sheet, Rev. 1.15 334 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) 10.3.2.6 SCI Data Registers (SCIDRH and SCIDRL) Module Base + 0x_0006 7 6 5 4 3 2 1 0 R W Reset R8 T8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Module Base + 0x_0007 7 6 5 4 3 2 1 0 R W Reset R7 T7 0 R6 T6 0 R5 T5 0 R4 T4 0 R3 T3 0 R2 T2 1 R1 T1 0 R0 T0 0 = Unimplemented or Reserved Figure 10-8. SCI Data Registers (SCIDRH and SCIDRL) Read: Anytime; reading accesses SCI receive data register Write: Anytime; writing accesses SCI transmit data register; writing to R8 has no effect Table 10-7. SCIDRH AND SCIDRL Field Descriptions Field 7 R8 6 T8 7–0 R[7:0] T[7:0] Description Received Bit 8 — R8 is the ninth data bit received when the SCI is configured for 9-bit data format (M = 1). Transmit Bit 8 — T8 is the ninth data bit transmitted when the SCI is configured for 9-bit data format (M = 1). Received Bits — Received bits seven through zero for 9-bit or 8-bit data formats Transmit Bits — Transmit bits seven through zero for 9-bit or 8-bit formats NOTE If the value of T8 is the same as in the previous transmission, T8 does not have to be rewritten.The same value is transmitted until T8 is rewritten In 8-bit data format, only SCI data register low (SCIDRL) needs to be accessed. When transmitting in 9-bit data format and using 8-bit write instructions, write first to SCI data register high (SCIDRH), then SCIDRL. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 335 Chapter 10 Serial Communications Interface (SCIV1) 10.4 Functional Description This section provides a complete functional description of the SCI block, detailing the operation of the design from the end user perspective in a number of subsections. Figure 10-9 shows the structure of the SCI module. The SCI allows full duplex, asynchronous, NRZ serial communication between the CPU and remote devices, including other CPUs. The SCI transmitter and receiver operate independently, although they use the same baud rate generator. The CPU monitors the status of the SCI, writes the data to be transmitted, and processes received data. SCI DATA REGISTER R8 RXD RECEIVE SHIFT REGISTER RE RECEIVE AND WAKEUP CONTROL RWU LOOPS RSRC M BUS CLOCK BAUD RATE GENERATOR WAKE DATA FORMAT CONTROL ILT PE PT TE ÷16 TRANSMIT CONTROL LOOPS SBK RSRC T8 TRANSMIT SHIFT REGISTER SCI DATA REGISTER TDRE TC TCIE TIE RIE NF FE PF RAF IDLE RDRF RDRF/OR IRQ IDLE IRQ OR ILIE SBR12–SBR0 IRQ TO CPU TDRE IRQ TXD Figure 10-9. SCI Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 336 Freescale Semiconductor TC IRQ Chapter 10 Serial Communications Interface (SCIV1) 10.4.1 Data Format 8-BIT DATA FORMAT BIT M IN SCICR1 CLEAR START BIT BIT 0 BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 PARITY OR DATA BIT BIT 7 STOP BIT PARITY OR DATA BIT BIT 7 BIT 8 STOP BIT The SCI uses the standard NRZ mark/space data format illustrated in Figure 10-10 below. NEXT START BIT 9-BIT DATA FORMAT BIT M IN SCICR1 SET START BIT BIT 0 BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 NEXT START BIT Figure 10-10. SCI Data Formats Each data character is contained in a frame that includes a start bit, eight or nine data bits, and a stop bit. Clearing the M bit in SCI control register 1 configures the SCI for 8-bit data characters.A frame with eight data bits has a total of 10 bits. Setting the M bit configures the SCI for nine-bit data characters. A frame with nine data bits has a total of 11 bits Table 10-8. Example of 8-Bit Data Formats Start Bit 1 1 1 1 Data Bits 8 7 7 Address Bits 0 0 1 1 Parity Bits 0 1 0 Stop Bit 1 1 1 The address bit identifies the frame as an address character. See Section 10.4.4.6, “Receiver Wakeup”. When the SCI is configured for 9-bit data characters, the ninth data bit is the T8 bit in SCI data register high (SCIDRH). It remains unchanged after transmission and can be used repeatedly without rewriting it. A frame with nine data bits has a total of 11 bits. Table 10-9. Example of 9-Bit Data Formats Start Bit 1 1 1 1 Data Bits 9 8 8 Address Bits 0 0 11 Parity Bits 0 1 0 Stop Bit 1 1 1 The address bit identifies the frame as an address character. See Section 10.4.4.6, “Receiver Wakeup”. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 337 Chapter 10 Serial Communications Interface (SCIV1) 10.4.2 Baud Rate Generation A 13-bit modulus counter in the baud rate generator derives the baud rate for both the receiver and the transmitter. The value from 0 to 8191 written to the SBR12–SBR0 bits determines the module clock divisor. The SBR bits are in the SCI baud rate registers (SCIBDH and SCIBDL). The baud rate clock is synchronized with the bus clock and drives the receiver. The baud rate clock divided by 16 drives the transmitter. The receiver has an acquisition rate of 16 samples per bit time. Baud rate generation is subject to one source of error: Integer division of the module clock may not give the exact target frequency. Table 10-10 lists some examples of achieving target baud rates with a module clock frequency of 25 MHz SCI baud rate = SCI module clock / (16 * SCIBR[12:0]) Table 10-10. Baud Rates (Example: Module Clock = 25 MHz) Bits SBR[12-0] 41 81 163 326 651 1302 2604 5208 Receiver Clock (Hz) 609,756.1 308,642.0 153,374.2 76,687.1 38,402.5 19,201.2 9600.6 4800.0 Transmitter Clock (Hz) 38,109.8 19,290.1 9585.9 4792.9 2400.2 1200.1 600.0 300.0 Target Baud Rate 38,400 19,200 9600 4800 2400 1200 600 300 Error (%) .76 .47 .16 .15 .01 .01 .00 .00 MC9S12KG128 Data Sheet, Rev. 1.15 338 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) 10.4.3 Transmitter INTERNAL BUS BUS CLOCK BAUD DIVIDER ÷ 16 SCI DATA REGISTERS 11-BIT TRANSMIT SHIFT REGISTER 8 7 6 5 4 3 2 1 0 START SBR12–SBR0 STOP M H L TXD MSB PREAMBLE (ALL ONES) T8 LOAD FROM SCIDR LOOP CONTROL BREAK (ALL 0s) TO RXD PT PARITY GENERATION SHIFT ENABLE PE LOOPS RSRC TRANSMITTER CONTROL TDRE INTERRUPT REQUEST TDRE TIE TC TCIE TE SBK TC INTERRUPT REQUEST Figure 10-11. Transmitter Block Diagram 10.4.3.1 Transmitter Character Length The SCI transmitter can accommodate either 8-bit or 9-bit data characters. The state of the M bit in SCI control register 1 (SCICR1) determines the length of data characters. When transmitting 9-bit data, bit T8 in SCI data register high (SCIDRH) is the ninth bit (bit 8). 10.4.3.2 Character Transmission To transmit data, the MCU writes the data bits to the SCI data registers (SCIDRH/SCIDRL), which in turn are transferred to the transmitter shift register. The transmit shift register then shifts a frame out through the Tx output signal, after it has prefaced them with a start bit and appended them with a stop bit. The SCI data registers (SCIDRH and SCIDRL) are the write-only buffers between the internal data bus and the transmit shift register. The SCI also sets a flag, the transmit data register empty flag (TDRE), every time it transfers data from the buffer (SCIDRH/L) to the transmitter shift register.The transmit driver routine may respond to this flag by MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 339 Chapter 10 Serial Communications Interface (SCIV1) writing another byte to the Transmitter buffer (SCIDRH/SCIDRL), while the shift register is still shifting out the first byte. To initiate an SCI transmission: 1. Configure the SCI: a) Select a baud rate. Write this value to the SCI baud registers (SCIBDH/L) to begin the baud rate generator. Remember that the baud rate generator is disabled when the baud rate is zero. Writing to the SCIBDH has no effect without also writing to SCIBDL. b) Write to SCICR1 to configure word length, parity, and other configuration bits (LOOPS,RSRC,M,WAKE,ILT,PE,PT). c) Enable the transmitter, interrupts, receive, and wake up as required, by writing to the SCICR2 register bits (TIE,TCIE,RIE,ILIE,TE,RE,RWU,SBK). A preamble or idle character will now be shifted out of the transmitter shift register. 2. Transmit Procedure for Each Byte: a. Poll the TDRE flag by reading the SCISR1 or responding to the TDRE interrupt. Keep in mind that the TDRE bit resets to one. d) If the TDRE flag is set, write the data to be transmitted to SCIDRH/L, where the ninth bit is written to the T8 bit in SCIDRH if the SCI is in 9-bit data format. A new transmission will not result until the TDRE flag has been cleared. 3. Repeat step 2 for each subsequent transmission. NOTE The TDRE flag is set when the shift register is loaded with the next data to be transmitted from SCIDRH/L, which happens, generally speaking, a little over half-way through the stop bit of the previous frame. Specifically, this transfer occurs 9/16ths of a bit time AFTER the start of the stop bit of the previous frame. Writing the TE bit from 0 to a 1 automatically loads the transmit shift register with a preamble of 10 logic 1s (if M = 0) or 11 logic 1s (if M = 1). After the preamble shifts out, control logic transfers the data from the SCI data register into the transmit shift register. A logic 0 start bit automatically goes into the least significant bit position of the transmit shift register. A logic 1 stop bit goes into the most significant bit position. Hardware supports odd or even parity. When parity is enabled, the most significant bit (msb) of the data character is the parity bit. The transmit data register empty flag, TDRE, in SCI status register 1 (SCISR1) becomes set when the SCI data register transfers a byte to the transmit shift register. The TDRE flag indicates that the SCI data register can accept new data from the internal data bus. If the transmit interrupt enable bit, TIE, in SCI control register 2 (SCICR2) is also set, the TDRE flag generates a transmitter interrupt request. When the transmit shift register is not transmitting a frame, the Tx output signal goes to the idle condition, logic 1. If at any time software clears the TE bit in SCI control register 2 (SCICR2), the transmitter enable signal goes low and the transmit signal goes idle. MC9S12KG128 Data Sheet, Rev. 1.15 340 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) If software clears TE while a transmission is in progress (TC = 0), the frame in the transmit shift register continues to shift out. To avoid accidentally cutting off the last frame in a message, always wait for TDRE to go high after the last frame before clearing TE. To separate messages with preambles with minimum idle line time, use this sequence between messages: 1. Write the last byte of the first message to SCIDRH/L. 2. Wait for the TDRE flag to go high, indicating the transfer of the last frame to the transmit shift register. 3. Queue a preamble by clearing and then setting the TE bit. 4. Write the first byte of the second message to SCIDRH/L. 10.4.3.3 Break Characters Writing a logic 1 to the send break bit, SBK, in SCI control register 2 (SCICR2) loads the transmit shift register with a break character. A break character contains all logic 0s and has no start, stop, or parity bit. Break character length depends on the M bit in SCI control register 1 (SCICR1). As long as SBK is at logic 1, transmitter logic continuously loads break characters into the transmit shift register. After software clears the SBK bit, the shift register finishes transmitting the last break character and then transmits at least one logic 1. The automatic logic 1 at the end of a break character guarantees the recognition of the start bit of the next frame. The SCI recognizes a break character when a start bit is followed by eight or nine logic 0 data bits and a logic 0 where the stop bit should be. Receiving a break character has these effects on SCI registers: • Sets the framing error flag, FE • Sets the receive data register full flag, RDRF • Clears the SCI data registers (SCIDRH/L) • May set the overrun flag, OR, noise flag, NF, parity error flag, PE, or the receiver active flag, RAF (see Section 10.3.2.4, “SCI Status Register 1 (SCISR1)” and Section 10.3.2.5, “SCI Status Register 2 (SCISR2)” 10.4.3.4 Idle Characters An idle character contains all logic 1s and has no start, stop, or parity bit. Idle character length depends on the M bit in SCI control register 1 (SCICR1). The preamble is a synchronizing idle character that begins the first transmission initiated after writing the TE bit from 0 to 1. If the TE bit is cleared during a transmission, the Tx output signal becomes idle after completion of the transmission in progress. Clearing and then setting the TE bit during a transmission queues an idle character to be sent after the frame currently being transmitted. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 341 Chapter 10 Serial Communications Interface (SCIV1) NOTE When queueing an idle character, return the TE bit to logic 1 before the stop bit of the current frame shifts out through the Tx output signal. Setting TE after the stop bit appears on Tx output signal causes data previously written to the SCI data register to be lost. Toggle the TE bit for a queued idle character while the TDRE flag is set and immediately before writing the next byte to the SCI data register. NOTE If the TE bit is clear and the transmission is complete, the SCI is not the master of the TXD pin 10.4.4 Receiver INTERNAL BUS SBR12–SBR0 SCI DATA REGISTER 11-BIT RECEIVE SHIFT REGISTER 8 7 6 5 4 3 2 1 0 RXD LOOP CONTROL RE RAF LOOPS RSRC M WAKE ILT PE PT DATA RECOVERY ALL ONES H FROM TXD MSB FE NF WAKEUP LOGIC PE RWU PARITY CHECKING IDLE ILIE RDRF R8 IDLE INTERRUPT REQUEST RDRF/OR INTERRUPT REQUEST RIE OR Figure 10-12. SCI Receiver Block Diagram 10.4.4.1 Receiver Character Length The SCI receiver can accommodate either 8-bit or 9-bit data characters. The state of the M bit in SCI control register 1 (SCICR1) determines the length of data characters. When receiving 9-bit data, bit R8 in SCI data register high (SCIDRH) is the ninth bit (bit 8). MC9S12KG128 Data Sheet, Rev. 1.15 342 Freescale Semiconductor START L STOP BUS CLOCK BAUD DIVIDER Chapter 10 Serial Communications Interface (SCIV1) 10.4.4.2 Character Reception During an SCI reception, the receive shift register shifts a frame in from the Rx input signal. The SCI data register is the read-only buffer between the internal data bus and the receive shift register. After a complete frame shifts into the receive shift register, the data portion of the frame transfers to the SCI data register. The receive data register full flag, RDRF, in SCI status register 1 (SCISR1) becomes set, indicating that the received byte can be read. If the receive interrupt enable bit, RIE, in SCI control register 2 (SCICR2) is also set, the RDRF flag generates an RDRF interrupt request. 10.4.4.3 Data Sampling The receiver samples the Rx input signal at the RT clock rate. The RT clock is an internal signal with a frequency 16 times the baud rate. To adjust for baud rate mismatch, the RT clock (see Figure 10-13) is re-synchronized: • After every start bit • After the receiver detects a data bit change from logic 1 to logic 0 (after the majority of data bit samples at RT8, RT9, and RT10 returns a valid logic 1 and the majority of the next RT8, RT9, and RT10 samples returns a valid logic 0) To locate the start bit, data recovery logic does an asynchronous search for a logic 0 preceded by three logic 1s.When the falling edge of a possible start bit occurs, the RT clock begins to count to 16. START BIT Rx Input Signal SAMPLES 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 LSB START BIT QUALIFICATION START BIT VERIFICATION DATA SAMPLING RT CLOCK RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT1 RT2 RT3 RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK COUNT RESET RT CLOCK RT16 RT4 Figure 10-13. Receiver Data Sampling To verify the start bit and to detect noise, data recovery logic takes samples at RT3, RT5, and RT7. Table 10-11 summarizes the results of the start bit verification samples. Table 10-11. Start Bit Verification RT3, RT5, and RT7 Samples 000 001 010 011 Start Bit Verification Yes Yes Yes No Noise Flag 0 1 1 0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 343 Chapter 10 Serial Communications Interface (SCIV1) Table 10-11. Start Bit Verification RT3, RT5, and RT7 Samples 100 101 110 111 Start Bit Verification Yes No No No Noise Flag 1 0 0 0 If start bit verification is not successful, the RT clock is reset and a new search for a start bit begins. To determine the value of a data bit and to detect noise, recovery logic takes samples at RT8, RT9, and RT10. Table 10-12 summarizes the results of the data bit samples. Table 10-12. Data Bit Recovery RT8, RT9, and RT10 Samples 000 001 010 011 100 101 110 111 Data Bit Determination 0 0 0 1 0 1 1 1 Noise Flag 0 1 1 1 1 1 1 0 NOTE The RT8, RT9, and RT10 samples do not affect start bit verification. If any or all of the RT8, RT9, and RT10 start bit samples are logic 1s following a successful start bit verification, the noise flag (NF) is set and the receiver assumes that the bit is a start bit (logic 0). To verify a stop bit and to detect noise, recovery logic takes samples at RT8, RT9, and RT10. Table 10-13 summarizes the results of the stop bit samples. Table 10-13. Stop Bit Recovery RT8, RT9, and RT10 Samples 000 001 010 011 100 101 110 111 Framing Error Flag 1 1 1 0 1 0 0 0 Noise Flag 0 1 1 1 1 1 1 0 MC9S12KG128 Data Sheet, Rev. 1.15 344 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) In Figure 10-14 the verification samples RT3 and RT5 determine that the first low detected was noise and not the beginning of a start bit. The RT clock is reset and the start bit search begins again. The noise flag is not set because the noise occurred before the start bit was found. START BIT Rx Input Signal SAMPLES 1 1 1 0 1 1 1 0 0 0 0 0 0 0 LSB RT CLOCK RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT1 RT2 LSB RT6 RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK COUNT RESET RT CLOCK RT16 RT3 RT7 Figure 10-14. Start Bit Search Example 1 In Figure 10-15, verification sample at RT3 is high. The RT3 sample sets the noise flag. Although the perceived bit time is misaligned, the data samples RT8, RT9, and RT10 are within the bit time and data recovery is successful. PERCEIVED START BIT ACTUAL START BIT Rx Input Signal SAMPLES 1 1 1 1 1 0 1 0 0 0 0 0 RT CLOCK RT1 RT1 RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT1 RT2 RT3 RT4 RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK COUNT RESET RT CLOCK RT16 RT5 Figure 10-15. Start Bit Search Example 2 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 345 Chapter 10 Serial Communications Interface (SCIV1) In Figure 10-16, a large burst of noise is perceived as the beginning of a start bit, although the test sample at RT5 is high. The RT5 sample sets the noise flag. Although this is a worst-case misalignment of perceived bit time, the data samples RT8, RT9, and RT10 are within the bit time and data recovery is successful. PERCEIVED START BIT ACTUAL START BIT Rx input Signal SAMPLES 1 1 1 0 0 1 0 0 0 0 LSB RT CLOCK RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 LSB RT2 RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK COUNT RESET RT CLOCK RT16 RT9 RT3 Figure 10-16. Start Bit Search Example 3 Figure 10-17 shows the effect of noise early in the start bit time. Although this noise does not affect proper synchronization with the start bit time, it does set the noise flag. PERCEIVED AND ACTUAL START BIT Rx Input Signal SAMPLES 1 1 1 1 1 1 1 1 1 0 1 0 RT CLOCK RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK COUNT RESET RT CLOCK RT16 RT1 Figure 10-17. Start Bit Search Example 4 MC9S12KG128 Data Sheet, Rev. 1.15 346 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) Figure 10-18 shows a burst of noise near the beginning of the start bit that resets the RT clock. The sample after the reset is low but is not preceded by three high samples that would qualify as a falling edge. Depending on the timing of the start bit search and on the data, the frame may be missed entirely or it may set the framing error flag. START BIT NO START BIT FOUND 1 1 1 1 1 1 1 1 1 0 0 1 1 0 0 0 0 0 0 0 0 LSB Rx Input Signal SAMPLES RT CLOCK RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 LSB RT2 RT CLOCK COUNT RESET RT CLOCK RT1 RT3 Figure 10-18. Start Bit Search Example 5 In Figure 10-19, a noise burst makes the majority of data samples RT8, RT9, and RT10 high. This sets the noise flag but does not reset the RT clock. In start bits only, the RT8, RT9, and RT10 data samples are ignored. START BIT Rx Input Signal SAMPLES 1 1 1 1 1 1 1 1 1 0 0 0 0 1 0 1 RT CLOCK RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK COUNT RESET RT CLOCK RT16 RT1 Figure 10-19. Start Bit Search Example 6 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 347 Chapter 10 Serial Communications Interface (SCIV1) 10.4.4.4 Framing Errors If the data recovery logic does not detect a logic 1 where the stop bit should be in an incoming frame, it sets the framing error flag, FE, in SCI status register 1 (SCISR1). A break character also sets the FE flag because a break character has no stop bit. The FE flag is set at the same time that the RDRF flag is set. 10.4.4.5 Baud Rate Tolerance A transmitting device may be operating at a baud rate below or above the receiver baud rate. Accumulated bit time misalignment can cause one of the three stop bit data samples (RT8, RT9, and RT10) to fall outside the actual stop bit.A noise error will occur if the RT8, RT9, and RT10 samples are not all the same logical values. A framing error will occur if the receiver clock is misaligned in such a way that the majority of the RT8, RT9, and RT10 stop bit samples are a logic zero. As the receiver samples an incoming frame, it re-synchronizes the RT clock on any valid falling edge within the frame. Re synchronization within frames will correct a misalignment between transmitter bit times and receiver bit times. 10.4.4.5.1 Slow Data Tolerance Figure 10-20 shows how much a slow received frame can be misaligned without causing a noise error or a framing error. The slow stop bit begins at RT8 instead of RT1 but arrives in time for the stop bit data samples at RT8, RT9, and RT10. MSB STOP RECEIVER RT CLOCK RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT10 RT11 RT12 RT13 RT14 RT15 RT16 DATA SAMPLES Figure 10-20. Slow Data Let’s take RTr as receiver RT clock and RTt as transmitter RT clock. For an 8-bit data character, it takes the receiver 9 bit times x 16 RTr cycles +7 RTr cycles =151 RTr cycles to start data sampling of the stop bit. With the misaligned character shown in Figure 10-20, the receiver counts 151 RTr cycles at the point when the count of the transmitting device is 9 bit times x 16 RTt cycles = 144 RTt cycles. The maximum percent difference between the receiver count and the transmitter count of a slow 8-bit data character with no errors is: ((151 – 144) / 151) x 100 = 4.63% For a 9-bit data character, it takes the receiver 10 bit times x 16 RTr cycles + 7 RTr cycles = 167 RTr cycles to start data sampling of the stop bit. MC9S12KG128 Data Sheet, Rev. 1.15 348 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) With the misaligned character shown in Figure 10-20, the receiver counts 167 RTr cycles at the point when the count of the transmitting device is 10 bit times x 16 RTt cycles = 160 RTt cycles. The maximum percent difference between the receiver count and the transmitter count of a slow 9-bit character with no errors is: ((167 – 160) / 167) X 100 = 4.19% 10.4.4.5.2 Fast Data Tolerance Figure 10-21 shows how much a fast received frame can be misaligned. The fast stop bit ends at RT10 instead of RT16 but is still sampled at RT8, RT9, and RT10. STOP IDLE OR NEXT FRAME RECEIVER RT CLOCK RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT10 RT11 RT12 RT13 RT14 RT15 RT16 DATA SAMPLES Figure 10-21. Fast Data For an 8-bit data character, it takes the receiver 9 bit times x 16 RTr cycles + 10 RTr cycles = 154 RTr cycles to finish data sampling of the stop bit. With the misaligned character shown in Figure 10-21, the receiver counts 154 RTr cycles at the point when the count of the transmitting device is 10 bit times x 16 RTt cycles = 160 RTt cycles. The maximum percent difference between the receiver count and the transmitter count of a fast 8-bit character with no errors is: ((160 – 154) / 160) x 100 = 3.75% For a 9-bit data character, it takes the receiver 10 bit times x 16 RTr cycles + 10 RTr cycles = 170 RTr cycles to finish data sampling of the stop bit. With the misaligned character shown in Figure 10-21, the receiver counts 170 RTr cycles at the point when the count of the transmitting device is 11 bit times x 16 RTt cycles = 176 RTt cycles. The maximum percent difference between the receiver count and the transmitter count of a fast 9-bit character with no errors is: ((176 – 170) / 176) x 100 = 3.40% 10.4.4.6 Receiver Wakeup To enable the SCI to ignore transmissions intended only for other receivers in multiple-receiver systems, the receiver can be put into a standby state. Setting the receiver wakeup bit, RWU, in SCI control register 2 (SCICR2) puts the receiver into standby state during which receiver interrupts are disabled.The SCI will still load the receive data into the SCIDRH/L registers, but it will not set the RDRF flag. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 349 Chapter 10 Serial Communications Interface (SCIV1) The transmitting device can address messages to selected receivers by including addressing information in the initial frame or frames of each message. The WAKE bit in SCI control register 1 (SCICR1) determines how the SCI is brought out of the standby state to process an incoming message. The WAKE bit enables either idle line wakeup or address mark wakeup. 10.4.4.6.1 Idle Input Line Wakeup (WAKE = 0) In this wakeup method, an idle condition on the Rx Input signal clears the RWU bit and wakes up the SCI. The initial frame or frames of every message contain addressing information. All receivers evaluate the addressing information, and receivers for which the message is addressed process the frames that follow. Any receiver for which a message is not addressed can set its RWU bit and return to the standby state. The RWU bit remains set and the receiver remains on standby until another idle character appears on the Rx Input signal. Idle line wakeup requires that messages be separated by at least one idle character and that no message contains idle characters. The idle character that wakes a receiver does not set the receiver idle bit, IDLE, or the receive data register full flag, RDRF. The idle line type bit, ILT, determines whether the receiver begins counting logic 1s as idle character bits after the start bit or after the stop bit. ILT is in SCI control register 1 (SCICR1). 10.4.4.6.2 Address Mark Wakeup (WAKE = 1) In this wakeup method, a logic 1 in the most significant bit (msb) position of a frame clears the RWU bit and wakes up the SCI. The logic 1 in the msb position marks a frame as an address frame that contains addressing information. All receivers evaluate the addressing information, and the receivers for which the message is addressed process the frames that follow.Any receiver for which a message is not addressed can set its RWU bit and return to the standby state. The RWU bit remains set and the receiver remains on standby until another address frame appears on the Rx Input signal. The logic 1 msb of an address frame clears the receiver’s RWU bit before the stop bit is received and sets the RDRF flag. Address mark wakeup allows messages to contain idle characters but requires that the msb be reserved for use in address frames.{sci_wake} NOTE With the WAKE bit clear, setting the RWU bit after the Rx Input signal has been idle can cause the receiver to wake up immediately. MC9S12KG128 Data Sheet, Rev. 1.15 350 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) 10.4.5 Single-Wire Operation Normally, the SCI uses two pins for transmitting and receiving. In single-wire operation, the RXD pin is disconnected from the SCI. The SCI uses the TXD pin for both receiving and transmitting. TRANSMITTER Tx OUTPUT SIGNAL Tx INPUT SIGNAL RECEIVER RXD Figure 10-22. Single-Wire Operation (LOOPS = 1, RSRC = 1) Enable single-wire operation by setting the LOOPS bit and the receiver source bit, RSRC, in SCI control register 1 (SCICR1). Setting the LOOPS bit disables the path from the Rx Input signal to the receiver. Setting the RSRC bit connects the receiver input to the output of the TXD pin driver. Both the transmitter and receiver must be enabled (TE = 1 and RE = 1).The TXDIR bit (SCISR2[1]) determines whether the TXD pin is going to be used as an input (TXDIR = 0) or an output (TXDIR = 1) in this mode of operation. 10.4.6 Loop Operation In loop operation the transmitter output goes to the receiver input. The Rx Input signal is disconnected from the SCI . TRANSMITTER Tx OUTPUT SIGNAL RECEIVER RXD Figure 10-23. Loop Operation (LOOPS = 1, RSRC = 0) Enable loop operation by setting the LOOPS bit and clearing the RSRC bit in SCI control register 1 (SCICR1). Setting the LOOPS bit disables the path from the Rx Input signal to the receiver. Clearing the RSRC bit connects the transmitter output to the receiver input. Both the transmitter and receiver must be enabled (TE = 1 and RE = 1). 10.5 10.5.1 Initialization Information Reset Initialization The reset state of each individual bit is listed in Section 10.3, “Memory Map and Registers” which details the registers and their bit fields. All special functions or modes which are initialized during or just following reset are described within this section. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 351 Chapter 10 Serial Communications Interface (SCIV1) 10.5.2 10.5.2.1 Interrupt Operation System Level Interrupt Sources There are five interrupt sources that can generate an SCI interrupt in to the CPU. They are listed in Table 10-14. Table 10-14. SCI Interrupt Source Interrupt Source Transmitter Transmitter Receiver Receiver Flag TDRE TC RDRF OR IDLE ILIE Local Enable TIE TCIE RIE MC9S12KG128 Data Sheet, Rev. 1.15 352 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) 10.5.2.2 Interrupt Descriptions The SCI only originates interrupt requests. The following is a description of how the SCI makes a request and how the MCU should acknowledge that request. The interrupt vector offset and interrupt number are chip dependent. The SCI only has a single interrupt line (SCI Interrupt Signal, active high operation) and all the following interrupts, when generated, are ORed together and issued through that port. 10.5.2.2.1 TDRE Description The TDRE interrupt is set high by the SCI when the transmit shift register receives a byte from the SCI data register. A TDRE interrupt indicates that the transmit data register (SCIDRH/L) is empty and that a new byte can be written to the SCIDRH/L for transmission.Clear TDRE by reading SCI status register 1 with TDRE set and then writing to SCI data register low (SCIDRL). 10.5.2.2.2 TC Description The TC interrupt is set by the SCI when a transmission has been completed.A TC interrupt indicates that there is no transmission in progress. TC is set high when the TDRE flag is set and no data, preamble, or break character is being transmitted. When TC is set, the TXD pin becomes idle (logic 1). Clear TC by reading SCI status register 1 (SCISR1) with TC set and then writing to SCI data register low (SCIDRL).TC is cleared automatically when data, preamble, or break is queued and ready to be sent. 10.5.2.2.3 RDRF Description The RDRF interrupt is set when the data in the receive shift register transfers to the SCI data register. A RDRF interrupt indicates that the received data has been transferred to the SCI data register and that the byte can now be read by the MCU. The RDRF interrupt is cleared by reading the SCI status register one (SCISR1) and then reading SCI data register low (SCIDRL). 10.5.2.2.4 OR Description The OR interrupt is set when software fails to read the SCI data register before the receive shift register receives the next frame. The newly acquired data in the shift register will be lost in this case, but the data already in the SCI data registers is not affected. The OR interrupt is cleared by reading the SCI status register one (SCISR1) and then reading SCI data register low (SCIDRL). 10.5.2.3 IDLE Description The IDLE interrupt is set when 10 consecutive logic 1s (if M = 0) or 11 consecutive logic 1s (if M = 1) appear on the receiver input. Once the IDLE is cleared, a valid frame must again set the RDRF flag before an idle condition can set the IDLE flag. Clear IDLE by reading SCI status register 1 (SCISR1) with IDLE set and then reading SCI data register low (SCIDRL). 10.5.3 Recovery from Wait Mode The SCI interrupt request can be used to bring the CPU out of wait mode. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 353 Chapter 10 Serial Communications Interface (SCIV1) MC9S12KG128 Data Sheet, Rev. 1.15 354 Freescale Semiconductor Chapter 10 Serial Communications Interface (SCIV1) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 355 Chapter 10 Serial Communications Interface (SCIV1) MC9S12KG128 Data Sheet, Rev. 1.15 356 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) 11.1 Introduction The SPI module allows a duplex, synchronous, serial communication between the MCU and peripheral devices. Software can poll the SPI status flags or the SPI operation can be interrupt driven. 11.1.1 Features The SPI includes these distinctive features: • Master mode and slave mode • Bidirectional mode • Slave select output • Mode fault error flag with CPU interrupt capability • Double-buffered data register • Serial clock with programmable polarity and phase • Control of SPI operation during wait mode 11.1.2 Modes of Operation The SPI functions in three modes, run, wait, and stop. • Run Mode This is the basic mode of operation. • Wait Mode SPI operation in wait mode is a configurable low power mode, controlled by the SPISWAI bit located in the SPICR2 register. In wait mode, if the SPISWAI bit is clear, the SPI operates like in Run Mode. If the SPISWAI bit is set, the SPI goes into a power conservative state, with the SPI clock generation turned off. If the SPI is configured as a master, any transmission in progress stops, but is resumed after CPU goes into Run Mode. If the SPI is configured as a slave, reception and transmission of a byte continues, so that the slave stays synchronized to the master. • Stop Mode The SPI is inactive in stop mode for reduced power consumption. If the SPI is configured as a master, any transmission in progress stops, but is resumed after CPU goes into run mode. If the SPI is configured as a slave, reception and transmission of a byte continues, so that the slave stays synchronized to the master. This is a high level description only, detailed descriptions of operating modes are contained in Section 11.4, “Functional Description.” MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 357 Chapter 11 Serial Peripheral Interface (SPIV3) 11.1.3 Block Diagram Figure 11-1 gives an overview on the SPI architecture. The main parts of the SPI are status, control, and data registers, shifter logic, baud rate generator, master/slave control logic, and port control logic. SPI 2 SPI Control Register 1 BIDIROE SPI Control Register 2 2 SPC0 SPI Status Register SPIF SPI Interrupt Request Baud Rate Generator Counter Bus Clock Prescaler Clock Select SPPR 3 SPR 3 Shifter SPI Baud Rate Register LSBFE=1 8 SPI Data Register 8 LSBFE=0 MSB LSBFE=0 LSBFE=1 LSBFE=0 LSBFE=1 LSB data out data in Baud Rate Shift Clock Sample Clock MODF SPTEF Slave Control CPOL CPHA MOSI Interrupt Control Phase + SCK in Slave Baud Rate Polarity Control Master Baud Rate Phase + SCK out Polarity Control Master Control Port Control Logic SCK SS Figure 11-1. SPI Block Diagram 11.2 External Signal Description This section lists the name and description of all ports including inputs and outputs that do, or may, connect off chip. The SPI module has a total of four external pins. 11.2.1 MOSI — Master Out/Slave In Pin This pin is used to transmit data out of the SPI module when it is configured as a master and receive data when it is configured as slave. MC9S12KG128 Data Sheet, Rev. 1.15 358 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) 11.2.2 MISO — Master In/Slave Out Pin This pin is used to transmit data out of the SPI module when it is configured as a slave and receive data when it is configured as master. 11.2.3 SS — Slave Select Pin This pin is used to output the select signal from the SPI module to another peripheral with which a data transfer is to take place when its configured as a master and its used as an input to receive the slave select signal when the SPI is configured as slave. 11.2.4 SCK — Serial Clock Pin This pin is used to output the clock with respect to which the SPI transfers data or receive clock in case of slave. 11.3 Memory Map and Register Definition This section provides a detailed description of address space and registers used by the SPI. The memory map for the SPI is given below in Table 11-1. The address listed for each register is the sum of a base address and an address offset. The base address is defined at the SoC level and the address offset is defined at the module level. Reads from the reserved bits return zeros and writes to the reserved bits have no effect. 11.3.1 Module Memory Map Table 11-1. SPI Memory Map Address 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 SPI Control Register 1 (SPICR1) SPI Control Register 2 (SPICR2) SPI Baud Rate Register (SPIBR) SPI Status Register (SPISR) Reserved SPI Data Register (SPIDR) Reserved Reserved Use Access R/W R/W1 R/W1 R2 — 2,3 R/W — 2,3 — 2,3 Certain bits are non-writable. Writes to this register are ignored. 3 Reading from this register returns all zeros. 2 1 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 359 Chapter 11 Serial Peripheral Interface (SPIV3) 11.3.2 Register Descriptions This section consists of register descriptions in address order. Each description includes a standard register diagram with an associated figure number. Details of register bit and field function follow the register diagrams, in bit order. Name SPICR1 R W R W R W R W R W R W R W R W = Unimplemented or Reserved Bit 7 6 5 4 3 2 2 Bit 0 SPIF 0 SPPR2 0 SPPR1 SPTEF 7 SPIE 0 6 SPE 0 5 SPTIE 0 4 MSTR 3 CPOL 2 CPHA 0 1 SSOE 0 LSBFE SPICR2 MODFEN BIDIROE 0 SPISWAI SPC0 SPIBR SPPR0 MODF SPR2 0 SPR1 0 SPR0 0 SPISR 0 Reserved SPIDR Reserved Reserved Figure 11-2. SPI Register Summary 11.3.2.1 SPI Control Register 1 (SPICR1) 7 6 5 4 3 2 1 0 R SPIE W Reset 0 0 0 0 0 1 0 0 SPE SPTIE MSTR CPOL CPHA SSOE LSBFE Figure 11-3. SPI Control Register 1 (SPICR1) Read: anytime Write: anytime MC9S12KG128 Data Sheet, Rev. 1.15 360 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) Table 11-2. SPICR1 Field Descriptions Field 7 SPIE 6 SPE Description SPI Interrupt Enable Bit — This bit enables SPI interrupt requests, if SPIF or MODF status flag is set. 0 SPI interrupts disabled. 1 SPI interrupts enabled. SPI System Enable Bit — This bit enables the SPI system and dedicates the SPI port pins to SPI system functions. If SPE is cleared, SPI is disabled and forced into idle state, status bits in SPISR register are reset. 0 SPI disabled (lower power consumption). 1 SPI enabled, port pins are dedicated to SPI functions. SPI Transmit Interrupt Enable — This bit enables SPI interrupt requests, if SPTEF flag is set. 0 SPTEF interrupt disabled. 1 SPTEF interrupt enabled. SPI Master/Slave Mode Select Bit — This bit selects, if the SPI operates in master or slave mode. Switching the SPI from master to slave or vice versa forces the SPI system into idle state. 0 SPI is in slave mode 1 SPI is in master mode SPI Clock Polarity Bit — This bit selects an inverted or non-inverted SPI clock. To transmit data between SPI modules, the SPI modules must have identical CPOL values. In master mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state. 0 Active-high clocks selected. In idle state SCK is low. 1 Active-low clocks selected. In idle state SCK is high. SPI Clock Phase Bit — This bit is used to select the SPI clock format. In master mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state. 0 Sampling of data occurs at odd edges (1,3,5,...,15) of the SCK clock 1 Sampling of data occurs at even edges (2,4,6,...,16) of the SCK clock Slave Select Output Enable — The SS output feature is enabled only in master mode, if MODFEN is set, by asserting the SSOE as shown in Table 11-3. In master mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state. LSB-First Enable — This bit does not affect the position of the MSB and LSB in the data register. Reads and writes of the data register always have the MSB in bit 7. In master mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state. 0 Data is transferred most significant bit first. 1 Data is transferred least significant bit first. 5 SPTIE 4 MSTR 3 CPOL 2 CPHA 1 SSOE 0 LSBFE Table 11-3. SS Input / Output Selection MODFEN 0 0 1 1 SSOE 0 1 0 1 Master Mode SS not used by SPI SS not used by SPI SS input with MODF feature SS is slave select output Slave Mode SS input SS input SS input SS input MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 361 Chapter 11 Serial Peripheral Interface (SPIV3) 11.3.2.2 SPI Control Register 2 (SPICR2) 7 6 5 4 3 2 1 0 R W Reset 0 0 0 MODFEN BIDIROE 0 0 SPISWAI 0 0 SPC0 0 0 0 0 0 = Unimplemented or Reserved Figure 11-4. SPI Control Register 2 (SPICR2) Read: anytime Write: anytime; writes to the reserved bits have no effect Table 11-4. SPICR2 Field Descriptions Field 4 MODFEN Description Mode Fault Enable Bit — This bit allows the MODF failure being detected. If the SPI is in master mode and MODFEN is cleared, then the SS port pin is not used by the SPI. In slave mode, the SS is available only as an input regardless of the value of MODFEN. For an overview on the impact of the MODFEN bit on the SS port pin configuration refer to Table 11-3. In master mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state. 0 SS port pin is not used by the SPI 1 SS port pin with MODF feature Output Enable in the Bidirectional Mode of Operation — This bit controls the MOSI and MISO output buffer of the SPI, when in bidirectional mode of operation (SPC0 is set). In master mode this bit controls the output buffer of the MOSI port, in slave mode it controls the output buffer of the MISO port. In master mode, with SPC0 set, a change of this bit will abort a transmission in progress and force the SPI into idle state. 0 Output buffer disabled 1 Output buffer enabled SPI Stop in Wait Mode Bit — This bit is used for power conservation while in wait mode. 0 SPI clock operates normally in wait mode 1 Stop SPI clock generation when in wait mode Serial Pin Control Bit 0 — This bit enables bidirectional pin configurations as shown in Table 11-5. In master mode, a change of this bit will abort a transmission in progress and force the SPI system into idle state 3 BIDIROE 1 SPISWAI 0 SPC0 Table 11-5. Bidirectional Pin Configurations Pin Mode SPC0 BIDIROE MISO MOSI Master Mode of Operation Normal Bidirectional 0 1 X 0 1 Slave Mode of Operation Normal Bidirectional 0 1 X 0 1 Slave Out Slave In Slave I/O Slave In MOSI not used by SPI Master In MISO not used by SPI Master Out Master In Master I/O MC9S12KG128 Data Sheet, Rev. 1.15 362 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) 11.3.2.3 SPI Baud Rate Register (SPIBR) 7 6 5 4 3 2 1 0 R W Reset 0 SPPR2 0 0 SPPR1 0 SPPR0 0 0 SPR2 0 0 SPR1 0 SPR0 0 = Unimplemented or Reserved Figure 11-5. SPI Baud Rate Register (SPIBR) Read: anytime Write: anytime; writes to the reserved bits have no effect Table 11-6. SPIBR Field Descriptions Field 6:4 SPPR[2:0] 2:0 SPR[2:0} Description SPI Baud Rate Preselection Bits — These bits specify the SPI baud rates as shown in Table 11-7. In master mode, a change of these bits will abort a transmission in progress and force the SPI system into idle state. SPI Baud Rate Selection Bits — These bits specify the SPI baud rates as shown in Table 11-7. In master mode, a change of these bits will abort a transmission in progress and force the SPI system into idle state. The baud rate divisor equation is as follows: BaudRateDivisor = ( SPPR + 1 ) • 2 ( SPR + 1 ) The baud rate can be calculated with the following equation: Baud Rate = BusClock ⁄ BaudRateDivisor MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 363 Chapter 11 Serial Peripheral Interface (SPIV3) Table 11-7. Example SPI Baud Rate Selection (25 MHz Bus Clock) SPPR2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 SPPR1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 SPPR0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 SPR2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 SPR1 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 0 1 1 0 0 1 SPR0 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 0 1 0 1 0 1 0 Baud Rate Divisor 2 4 8 16 32 64 128 256 4 8 16 32 64 128 256 512 6 12 24 48 96 192 384 768 8 16 32 64 128 256 512 1024 10 20 40 80 160 320 640 Baud Rate 12.5 MHz 6.25 MHz 3.125 MHz 1.5625 MHz 781.25 kHz 390.63 kHz 195.31 kHz 97.66 kHz 6.25 MHz 3.125 MHz 1.5625 MHz 781.25 kHz 390.63 kHz 195.31 kHz 97.66 kHz 48.83 kHz 4.16667 MHz 2.08333 MHz 1.04167 MHz 520.83 kHz 260.42 kHz 130.21 kHz 65.10 kHz 32.55 kHz 3.125 MHz 1.5625 MHz 781.25 kHz 390.63 kHz 195.31 kHz 97.66 kHz 48.83 kHz 24.41 kHz 2.5 MHz 1.25 MHz 625 kHz 312.5 kHz 156.25 kHz 78.13 kHz 39.06 kHz MC9S12KG128 Data Sheet, Rev. 1.15 364 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) Table 11-7. Example SPI Baud Rate Selection (25 MHz Bus Clock) (continued) SPPR2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 SPPR1 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 SPPR0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 SPR2 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 SPR1 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 SPR0 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 Baud Rate Divisor 1280 12 24 48 96 192 384 768 1536 14 28 56 112 224 448 896 1792 16 32 64 128 256 512 1024 2048 Baud Rate 19.53 kHz 2.08333 MHz 1.04167 MHz 520.83 kHz 260.42 kHz 130.21 kHz 65.10 kHz 32.55 kHz 16.28 kHz 1.78571 MHz 892.86 kHz 446.43 kHz 223.21 kHz 111.61 kHz 55.80 kHz 27.90 kHz 13.95 kHz 1.5625 MHz 781.25 kHz 390.63 kHz 195.31 kHz 97.66 kHz 48.83 kHz 24.41 kHz 12.21 kHz NOTE In slave mode of SPI S-clock speed DIV2 is not supported. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 365 Chapter 11 Serial Peripheral Interface (SPIV3) 11.3.2.4 SPI Status Register (SPISR) 7 6 5 4 3 2 1 0 R W Reset SPIF 0 SPTEF MODF 0 0 0 0 0 0 1 0 0 0 0 0 = Unimplemented or Reserved Figure 11-6. SPI Status Register (SPISR) Read: anytime Write: has no effect Table 11-8. SPISR Field Descriptions Field 7 SPIF Description SPIF Interrupt Flag — This bit is set after a received data byte has been transferred into the SPI Data Register. This bit is cleared by reading the SPISR register (with SPIF set) followed by a read access to the SPI Data Register. 0 Transfer not yet complete 1 New data copied to SPIDR SPI Transmit Empty Interrupt Flag — If set, this bit indicates that the transmit data register is empty. To clear this bit and place data into the transmit data register, SPISR has to be read with SPTEF = 1, followed by a write to SPIDR. Any write to the SPI Data Register without reading SPTEF = 1, is effectively ignored. 0 SPI Data register not empty 1 SPI Data register empty Mode Fault Flag — This bit is set if the SS input becomes low while the SPI is configured as a master and mode fault detection is enabled, MODFEN bit of SPICR2 register is set. Refer to MODFEN bit description in Section 11.3.2.2, “SPI Control Register 2 (SPICR2).” The flag is cleared automatically by a read of the SPI Status Register (with MODF set) followed by a write to the SPI Control Register 1. 0 Mode fault has not occurred. 1 Mode fault has occurred. 5 SPTEF 4 MODF 11.3.2.5 SPI Data Register (SPIDR) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 2 Bit 0 = Unimplemented or Reserved Figure 11-7. SPI Data Register (SPIDR) Read: anytime; normally read only after SPIF is set Write: anytime MC9S12KG128 Data Sheet, Rev. 1.15 366 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) The SPI Data Register is both the input and output register for SPI data. A write to this register allows a data byte to be queued and transmitted. For a SPI configured as a master, a queued data byte is transmitted immediately after the previous transmission has completed. The SPI Transmitter Empty Flag SPTEF in the SPISR register indicates when the SPI Data Register is ready to accept new data. Reading the data can occur anytime from after the SPIF is set to before the end of the next transfer. If the SPIF is not serviced by the end of the successive transfers, those data bytes are lost and the data within the SPIDR retains the first byte until SPIF is serviced. 11.4 Functional Description The SPI module allows a duplex, synchronous, serial communication between the MCU and peripheral devices. Software can poll the SPI status flags or SPI operation can be interrupt driven. The SPI system is enabled by setting the SPI enable (SPE) bit in SPI Control Register 1. While SPE bit is set, the four associated SPI port pins are dedicated to the SPI function as: • Slave select (SS) • Serial clock (SCK) • Master out/slave in (MOSI) • Master in/slave out (MISO) The main element of the SPI system is the SPI Data Register. The 8-bit data register in the master and the 8-bit data register in the slave are linked by the MOSI and MISO pins 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 S-clock from the master, so data is exchanged between the master and the slave. Data written to the master SPI Data Register becomes the output data for the slave, and data read from the master SPI Data Register after a transfer operation is the input data from the slave. A read of SPISR with SPTEF = 1 followed by a write to SPIDR puts data into the transmit data register. When a transfer is complete, received data is moved into the receive data register. Data may be read from this double-buffered system any time before the next transfer has completed. This 8-bit data register acts as the SPI receive data register for reads and as the SPI transmit data register for writes. A single SPI register address is used for reading data from the read data buffer and for writing data to the transmit data register. The clock phase control bit (CPHA) and a clock polarity control bit (CPOL) in the SPI Control Register 1 (SPICR1) select one of four possible clock formats to be used by the SPI system. The CPOL bit simply selects a non-inverted or inverted clock. The CPHA bit is used to accommodate two fundamentally different protocols by sampling data on odd numbered SCK edges or on even numbered SCK edges (see Section 11.4.3, “Transmission Formats”). The SPI can be configured to operate as a master or as a slave. When the MSTR bit in SPI Control Register1 is set, master mode is selected, when the MSTR bit is clear, slave mode is selected. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 367 Chapter 11 Serial Peripheral Interface (SPIV3) 11.4.1 Master Mode The SPI operates in master mode when the MSTR bit is set. Only a master SPI module can initiate transmissions. A transmission begins by writing to the master SPI Data Register. If the shift register is empty, the byte immediately transfers to the shift register. The byte begins shifting out on the MOSI pin under the control of the serial clock. • S-clock The SPR2, SPR1, and SPR0 baud rate selection bits in conjunction with the SPPR2, SPPR1, and SPPR0 baud rate preselection bits in the SPI Baud Rate register control the baud rate generator and determine the speed of the transmission. The SCK pin is the SPI clock output. Through the SCK pin, the baud rate generator of the master controls the shift register of the slave peripheral. • MOSI and MISO Pins In master mode, the function of the serial data output pin (MOSI) and the serial data input pin (MISO) is determined by the SPC0 and BIDIROE control bits. • SS Pin If MODFEN and SSOE bit are set, the SS pin is configured as slave select output. The SS output becomes low during each transmission and is high when the SPI is in idle state. If MODFEN is set and SSOE is cleared, the SS pin is configured as input for detecting mode fault error. If the SS input becomes low this indicates a mode fault error where another master tries to drive the MOSI and SCK lines. In this case, the SPI immediately switches to slave mode, by clearing the MSTR bit and also disables the slave output buffer MISO (or SISO in bidirectional mode). So the result is that all outputs are disabled and SCK, MOSI and MISO are inputs. If a transmission is in progress when the mode fault occurs, the transmission is aborted and the SPI is forced into idle state. This mode fault error also sets the mode fault (MODF) flag in the SPI Status Register (SPISR). If the SPI interrupt enable bit (SPIE) is set when the MODF flag gets set, then an SPI interrupt sequence is also requested. When a write to the SPI Data Register in the master occurs, there is a half SCK-cycle delay. After the delay, SCK is started within the master. The rest of the transfer operation differs slightly, depending on the clock format specified by the SPI clock phase bit, CPHA, in SPI Control Register 1 (see Section 11.4.3, “Transmission Formats”). NOTE A change of the bits CPOL, CPHA, SSOE, LSBFE, MODFEN, SPC0, BIDIROE with SPC0 set, SPPR2–SPPR0 and SPR2–SPR0 in master mode will abort a transmission in progress and force the SPI into idle state. The remote slave cannot detect this, therefore the master has to ensure that the remote slave is set back to idle state. MC9S12KG128 Data Sheet, Rev. 1.15 368 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) 11.4.2 Slave Mode The SPI operates in slave mode when the MSTR bit in SPI Control Register1 is clear. • SCK Clock In slave mode, SCK is the SPI clock input from the master. • MISO and MOSI Pins In slave mode, the function of the serial data output pin (MISO) and serial data input pin (MOSI) is determined by the SPC0 bit and BIDIROE bit in SPI Control Register 2. • SS Pin The SS pin is the slave select input. Before a data transmission occurs, the SS pin of the slave SPI must be low. SS must remain low until the transmission is complete. If SS goes high, the SPI is forced into idle state. The SS input also controls the serial data output pin, if SS is high (not selected), the serial data output pin is high impedance, and, if SS is low the first bit in the SPI Data Register is driven out of the serial data output pin. Also, if the slave is not selected (SS is high), then the SCK input is ignored and no internal shifting of the SPI shift register takes place. Although the SPI is capable of duplex operation, some SPI peripherals are capable of only receiving SPI data in a slave mode. For these simpler devices, there is no serial data out pin. NOTE When peripherals with duplex capability are used, take care not to simultaneously enable two receivers whose serial outputs drive the same system slave’s serial data output line. As long as no more than one slave device drives the system slave’s serial data output line, it is possible for several slaves to receive the same transmission from a master, although the master would not receive return information from all of the receiving slaves. If the CPHA bit in SPI Control Register 1 is clear, odd numbered edges on the SCK input cause the data at the serial data input pin to be latched. Even numbered edges cause the value previously latched from the serial data input pin to shift into the LSB or MSB of the SPI shift register, depending on the LSBFE bit. If the CPHA bit is set, even numbered edges on the SCK input cause the data at the serial data input pin to be latched. Odd numbered edges cause the value previously latched from the serial data input pin to shift into the LSB or MSB of the SPI shift register, depending on the LSBFE bit. When CPHA is set, the first edge is used to get the first data bit onto the serial data output pin. When CPHA is clear and the SS input is low (slave selected), the first bit of the SPI data is driven out of the serial data output pin. After the eighth shift, the transfer is considered complete and the received data is transferred into the SPI Data Register. To indicate transfer is complete, the SPIF flag in the SPI Status Register is set. NOTE A change of the bits CPOL, CPHA, SSOE, LSBFE, MODFEN, SPC0 and BIDIROE with SPC0 set in slave mode will corrupt a transmission in progress and has to be avoided. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 369 Chapter 11 Serial Peripheral Interface (SPIV3) 11.4.3 Transmission Formats During an SPI transmission, data is transmitted (shifted out serially) and received (shifted in serially) simultaneously. The serial clock (SCK) synchronizes shifting and sampling of the information on the two serial data lines. A slave select line allows selection of an individual slave SPI device, slave devices that are not selected do not interfere with SPI bus activities. Optionally, on a master SPI device, the slave select line can be used to indicate multiple-master bus contention. MASTER SPI MISO MOSI SCK BAUD RATE GENERATOR SS MISO MOSI SCK SS SLAVE SPI SHIFT REGISTER SHIFT REGISTER VDD Figure 11-8. Master/Slave Transfer Block Diagram 11.4.3.1 Clock Phase and Polarity Controls Using two bits in the SPI Control Register1, software selects one of four combinations of serial clock phase and polarity. The CPOL clock polarity control bit specifies an active high or low clock and has no significant effect on the transmission format. The CPHA clock phase control bit selects one of two fundamentally different transmission formats. Clock phase and polarity should be identical for the master SPI device and the communicating slave device. In some cases, the phase and polarity are changed between transmissions to allow a master device to communicate with peripheral slaves having different requirements. 11.4.3.2 CPHA = 0 Transfer Format The first edge on the SCK line is used to clock the first data bit of the slave into the master and the first data bit of the master into the slave. In some peripherals, the first bit of the slave’s data is available at the slave’s data out pin as soon as the slave is selected. In this format, the first SCK edge is issued a half cycle after SS has become low. A half SCK cycle later, the second edge appears on the SCK line. When this second edge occurs, the value previously latched from the serial data input pin is shifted into the LSB or MSB of the shift register, depending on LSBFE bit. After this second edge, the next bit of the SPI master data is transmitted out of the serial data output pin of the master to the serial input pin on the slave. This process continues for a total of 16 edges on the SCK line, with data being latched on odd numbered edges and shifted on even numbered edges. MC9S12KG128 Data Sheet, Rev. 1.15 370 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) Data reception is double buffered. Data is shifted serially into the SPI shift register during the transfer and is transferred to the parallel SPI Data Register after the last bit is shifted in. After the 16th (last) SCK edge: • Data that was previously in the master SPI Data Register should now be in the slave data register and the data that was in the slave data register should be in the master. • The SPIF flag in the SPI Status Register is set indicating that the transfer is complete. Figure 11-9 is a timing diagram of an SPI transfer where CPHA = 0. SCK waveforms are shown for CPOL = 0 and CPOL = 1. The diagram may be interpreted as a master or slave timing diagram because the SCK, MISO, and MOSI pins are connected directly between the master and the slave. The MISO signal is the output from the slave and the MOSI signal is the output from the master. The SS pin of the master must be either high or reconfigured as a general-purpose output not affecting the SPI. End of Idle State SCK Edge Nr. SCK (CPOL = 0) SCK (CPOL = 1) 1 2 Begin 3 4 5 6 Transfer 7 8 9 10 11 12 End 13 14 15 16 Begin of Idle State CHANGE O MOSI pin CHANGE O MISO pin SEL SS (O) Master only SEL SS (I) tL MSB first (LSBFE = 0): MSB Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 LSB first (LSBFE = 1): LSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 tL = Minimum leading time before the first SCK edge tT = Minimum trailing time after the last SCK edge tI = Minimum idling time between transfers (minimum SS high time) tL, tT, and tI are guaranteed for the master mode and required for the slave mode. Bit 1 Bit 6 tT tI tL LSB Minimum 1/2 SCK for tT, tl, tL MSB Figure 11-9. SPI Clock Format 0 (CPHA = 0) In slave mode, if the SS line is not deasserted between the successive transmissions then the content of the SPI Data Register is not transmitted, instead the last received byte is transmitted. If the SS line is deasserted for at least minimum idle time (half SCK cycle) between successive transmissions then the content of the SPI Data Register is transmitted. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 371 If next transfer begins here SAMPLE I MOSI/MISO Chapter 11 Serial Peripheral Interface (SPIV3) In master mode, with slave select output enabled the SS line is always deasserted and reasserted between successive transfers for at least minimum idle time. 11.4.3.3 CPHA = 1 Transfer Format Some peripherals require the first SCK edge before the first data bit becomes available at the data out pin, the second edge clocks data into the system. In this format, the first SCK edge is issued by setting the CPHA bit at the beginning of the 8-cycle transfer operation. The first edge of SCK occurs immediately after the half SCK clock cycle synchronization delay. This first edge commands the slave to transfer its first data bit to the serial data input pin of the master. A half SCK cycle later, the second edge appears on the SCK pin. This is the latching edge for both the master and slave. When the third edge occurs, the value previously latched from the serial data input pin is shifted into the LSB or MSB of the SPI shift register, depending on LSBFE bit. After this edge, the next bit of the master data is coupled out of the serial data output pin of the master to the serial input pin on the slave. This process continues for a total of 16 edges on the SCK line with data being latched on even numbered edges and shifting taking place on odd numbered edges. Data reception is double buffered, data is serially shifted into the SPI shift register during the transfer and is transferred to the parallel SPI Data Register after the last bit is shifted in. After the 16th SCK edge: • Data that was previously in the SPI Data Register of the master is now in the data register of the slave, and data that was in the data register of the slave is in the master. • The SPIF flag bit in SPISR is set indicating that the transfer is complete. Figure 11-10 shows two clocking variations for CPHA = 1. The diagram may be interpreted as a master or slave timing diagram because the SCK, MISO, and MOSI pins are connected directly between the master and the slave. The MISO signal is the output from the slave, and the MOSI signal is the output from the master. The SS line is the slave select input to the slave. The SS pin of the master must be either high or reconfigured as a general-purpose output not affecting the SPI. The SS line can remain active low between successive transfers (can be tied low at all times). This format is sometimes preferred in systems having a single fixed master and a single slave that drive the MISO data line. • Back-to-back transfers in master mode In master mode, if a transmission has completed and a new data byte is available in the SPI Data Register, this byte is send out immediately without a trailing and minimum idle time. The SPI interrupt request flag (SPIF) is common to both the master and slave modes. SPIF gets set one half SCK cycle after the last SCK edge. MC9S12KG128 Data Sheet, Rev. 1.15 372 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) End of Idle State SCK Edge Nr. SCK (CPOL = 0) SCK (CPOL = 1) 1 2 3 Begin 4 5 6 7 Transfer 8 9 10 11 12 End 13 14 15 16 Begin of Idle State CHANGE O MOSI pin CHANGE O MISO pin SEL SS (O) Master only SEL SS (I) tL MSB first (LSBFE = 0): LSB first (LSBFE = 1): tT tI tL MSB Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 LSB Minimum 1/2 SCK for tT, tl, tL LSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 MSB tL = Minimum leading time before the first SCK edge, not required for back to back transfers tT = Minimum trailing time after the last SCK edge tI = Minimum idling time between transfers (minimum SS high time), not required for back to back transfers Figure 11-10. SPI Clock Format 1 (CPHA = 1) 11.4.4 SPI Baud Rate Generation Baud rate generation consists of a series of divider stages. Six bits in the SPI Baud Rate register (SPPR2, SPPR1, SPPR0, SPR2, SPR1, and SPR0) determine the divisor to the SPI module clock which results in the SPI baud rate. The SPI clock rate is determined by the product of the value in the baud rate preselection bits (SPPR2–SPPR0) and the value in the baud rate selection bits (SPR2–SPR0). The module clock divisor equation is shown in Figure 11-11 When all bits are clear (the default condition), the SPI module clock is divided by 2. When the selection bits (SPR2–SPR0) are 001 and the preselection bits (SPPR2–SPPR0) are 000, the module clock divisor becomes 4. When the selection bits are 010, the module clock divisor becomes 8 etc. When the preselection bits are 001, the divisor determined by the selection bits is multiplied by 2. When the preselection bits are 010, the divisor is multiplied by 3, etc. See Table 11-7 for baud rate calculations for all bit conditions, based on a 25-MHz bus clock. The two sets of selects allows the clock to be divided by a non-power of two to achieve other baud rates such as divide by 6, divide by 10, etc. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 373 If next transfer begins here SAMPLE I MOSI/MISO Chapter 11 Serial Peripheral Interface (SPIV3) The baud rate generator is activated only when the SPI is in the master mode and a serial transfer is taking place. In the other cases, the divider is disabled to decrease IDD current. BaudRateDivisor = ( SPPR + 1 ) • 2 ( SPR + 1 ) Figure 11-11. Baud Rate Divisor Equation 11.4.5 11.4.5.1 Special Features SS Output The SS output feature automatically drives the SS pin low during transmission to select external devices and drives it high during idle to deselect external devices. When SS output is selected, the SS output pin is connected to the SS input pin of the external device. The SS output is available only in master mode during normal SPI operation by asserting SSOE and MODFEN bit as shown in Table 11-3. The mode fault feature is disabled while SS output is enabled. NOTE Care must be taken when using the SS output feature in a multimaster system because the mode fault feature is not available for detecting system errors between masters. 11.4.5.2 Bidirectional Mode (MOSI or MISO) The bidirectional mode is selected when the SPC0 bit is set in SPI Control Register 2 (see Table 11-9). In this mode, the SPI uses only one serial data pin for the interface with external device(s). The MSTR bit decides which pin to use. The MOSI pin becomes the serial data I/O (MOMI) pin for the master mode, and the MISO pin becomes serial data I/O (SISO) pin for the slave mode. The MISO pin in master mode and MOSI pin in slave mode are not used by the SPI. Table 11-9. Normal Mode and Bidirectional Mode When SPE = 1 Master Mode MSTR = 1 Serial Out MOSI Slave Mode MSTR = 0 Serial In SPI MISO Serial Out MISO MOSI Normal Mode SPC0 = 0 SPI Serial In Serial Out MOMI BIDIROE Serial In BIDIROE SPI Serial Out SISO Bidirectional Mode SPC0 = 1 SPI Serial In MC9S12KG128 Data Sheet, Rev. 1.15 374 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) The direction of each serial I/O pin depends on the BIDIROE bit. If the pin is configured as an output, serial data from the shift register is driven out on the pin. The same pin is also the serial input to the shift register. The SCK is output for the master mode and input for the slave mode. The SS is the input or output for the master mode, and it is always the input for the slave mode. The bidirectional mode does not affect SCK and SS functions. NOTE In bidirectional master mode, with mode fault enabled, both data pins MISO and MOSI can be occupied by the SPI, though MOSI is normally used for transmissions in bidirectional mode and MISO is not used by the SPI. If a mode fault occurs, the SPI is automatically switched to slave mode, in this case MISO becomes occupied by the SPI and MOSI is not used. This has to be considered, if the MISO pin is used for other purpose. 11.4.6 Error Conditions The SPI has one error condition: • Mode fault error 11.4.6.1 Mode Fault Error If the SS input becomes low while the SPI is configured as a master, it indicates a system error where more than one master may be trying to drive the MOSI and SCK lines simultaneously. This condition is not permitted in normal operation, the MODF bit in the SPI Status Register is set automatically provided the MODFEN bit is set. In the special case where the SPI is in master mode and MODFEN bit is cleared, the SS pin is not used by the SPI. In this special case, the mode fault error function is inhibited and MODF remains cleared. In case the SPI system is configured as a slave, the SS pin is a dedicated input pin. Mode fault error doesn’t occur in slave mode. If a mode fault error occurs the SPI is switched to slave mode, with the exception that the slave output buffer is disabled. So SCK, MISO and MOSI pins are forced to be high impedance inputs to avoid any possibility of conflict with another output driver. A transmission in progress is aborted and the SPI is forced into idle state. If the mode fault error occurs in the bidirectional mode for a SPI system configured in master mode, output enable of the MOMI (MOSI in bidirectional mode) is cleared if it was set. No mode fault error occurs in the bidirectional mode for SPI system configured in slave mode. The mode fault flag is cleared automatically by a read of the SPI Status Register (with MODF set) followed by a write to SPI Control Register 1. If the mode fault flag is cleared, the SPI becomes a normal master or slave again. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 375 Chapter 11 Serial Peripheral Interface (SPIV3) 11.4.7 Operation in Run Mode In run mode with the SPI system enable (SPE) bit in the SPI control register clear, the SPI system is in a low-power, disabled state. SPI registers remain accessible, but clocks to the core of this module are disabled. 11.4.8 Operation in Wait Mode SPI operation in wait mode depends upon the state of the SPISWAI bit in SPI Control Register 2. • If SPISWAI is clear, the SPI operates normally when the CPU is in wait mode • If SPISWAI is set, SPI clock generation ceases and the SPI module enters a power conservation state when the CPU is in wait mode. — If SPISWAI is set and the SPI is configured for master, any transmission and reception in progress stops at wait mode entry. The transmission and reception resumes when the SPI exits wait mode. — If SPISWAI is set and the SPI is configured as a slave, any transmission and reception in progress continues if the SCK continues to be driven from the master. This keeps the slave synchronized to the master and the SCK. If the master transmits several bytes while the slave is in wait mode, the slave will continue to send out bytes consistent with the operation mode at the start of wait mode (i.e. If the slave is currently sending its SPIDR to the master, it will continue to send the same byte. Else if the slave is currently sending the last received byte from the master, it will continue to send each previous master byte). NOTE Care must be taken when expecting data from a master while the slave is in wait or stop mode. Even though the shift register will continue to operate, the rest of the SPI is shut down (i.e. a SPIF interrupt will not be generated until exiting stop or wait mode). Also, the byte from the shift register will not be copied into the SPIDR register until after the slave SPI has exited wait or stop mode. A SPIF flag and SPIDR copy is only generated if wait mode is entered or exited during a tranmission. If the slave enters wait mode in idle mode and exits wait mode in idle mode, neither a SPIF nor a SPIDR copy will occur. 11.4.9 Operation in Stop Mode Stop mode is dependent on the system. The SPI enters stop mode when the module clock is disabled (held high or low). If the SPI is in master mode and exchanging data when the CPU enters stop mode, the transmission is frozen until the CPU exits stop mode. After stop, data to and from the external SPI is exchanged correctly. In slave mode, the SPI will stay synchronized with the master. The stop mode is not dependent on the SPISWAI bit. MC9S12KG128 Data Sheet, Rev. 1.15 376 Freescale Semiconductor Chapter 11 Serial Peripheral Interface (SPIV3) 11.5 Reset The reset values of registers and signals are described in the Memory Map and Registers section (see Section 11.3, “Memory Map and Register Definition”) which details the registers and their bit-fields. • If a data transmission occurs in slave mode after reset without a write to SPIDR, it will transmit garbage, or the byte last received from the master before the reset. • Reading from the SPIDR after reset will always read a byte of zeros. 11.6 Interrupts The SPI only originates interrupt requests when SPI is enabled (SPE bit in SPICR1 set). The following is a description of how the SPI makes a request and how the MCU should acknowledge that request. The interrupt vector offset and interrupt priority are chip dependent. The interrupt flags MODF, SPIF and SPTEF are logically ORed to generate an interrupt request. 11.6.1 MODF MODF occurs when the master detects an error on the SS pin. The master SPI must be configured for the MODF feature (see Table 11-3). After MODF is set, the current transfer is aborted and the following bit is changed: • MSTR = 0, The master bit in SPICR1 resets. The MODF interrupt is reflected in the status register MODF flag. Clearing the flag will also clear the interrupt. This interrupt will stay active while the MODF flag is set. MODF has an automatic clearing process which is described in Section 11.3.2.4, “SPI Status Register (SPISR).” 11.6.2 SPIF SPIF occurs when new data has been received and copied to the SPI Data Register. After SPIF is set, it does not clear until it is serviced. SPIF has an automatic clearing process which is described in Section 11.3.2.4, “SPI Status Register (SPISR).” In the event that the SPIF is not serviced before the end of the next transfer (i.e. SPIF remains active throughout another transfer), the latter transfers will be ignored and no new data will be copied into the SPIDR. 11.6.3 SPTEF SPTEF occurs when the SPI Data Register is ready to accept new data. After SPTEF is set, it does not clear until it is serviced. SPTEF has an automatic clearing process which is described in Section 11.3.2.4, “SPI Status Register (SPISR).” MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 377 Chapter 11 Serial Peripheral Interface (SPIV3) MC9S12KG128 Data Sheet, Rev. 1.15 378 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.1 Introduction The PWM definition is based on the HC12 PWM definitions. It contains the basic features from the HC11 with some of the enhancements incorporated on the HC12: center aligned output mode and four available clock sources.The PWM module has eight channels with independent control of left and center aligned outputs on each channel. Each of the eight channels has a programmable period and duty cycle as well as a dedicated counter. A flexible clock select scheme allows a total of 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% to 100%. The PWM outputs can be programmed as left aligned outputs or center aligned outputs. 12.1.1 Features The PWM block includes these distinctive features: • Eight independent PWM channels with programmable period and duty cycle • Dedicated counter for each PWM channel • Programmable PWM enable/disable for each channel • Software selection of PWM duty pulse polarity for each channel • Period and duty cycle are double buffered. Change takes effect when the end of the effective period is reached (PWM counter reaches zero) or when the channel is disabled. • Programmable center or left aligned outputs on individual channels • Eight 8-bit channel or four 16-bit channel PWM resolution • Four clock sources (A, B, SA, and SB) provide for a wide range of frequencies • Programmable clock select logic • Emergency shutdown 12.1.2 Modes of Operation There is a software programmable option for low power consumption in wait mode that disables the input clock to the prescaler. In freeze mode there is a software programmable option to disable the input clock to the prescaler. This is useful for emulation. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 379 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.1.3 Block Diagram Figure 12-1 shows the block diagram for the 8-bit 8-channel PWM block. PWM8B8C PWM Channels Channel 7 Period and Duty Channel 6 Counter PWM7 PWM6 Counter Bus Clock Clock Select PWM Clock Period and Duty Channel 5 Period and Duty Control Channel 4 Period and Duty Counter Counter PWM5 PWM4 Channel 3 Enable Period and Duty Counter PWM3 Polarity Channel 2 Period and Duty Counter PWM2 Alignment Channel 1 Period and Duty Channel 0 Period and Duty Counter Counter PWM1 PWM0 Figure 12-1. PWM Block Diagram 12.2 External Signal Description The PWM module has a total of 8 external pins. 12.2.1 PWM7 — PWM Channel 7 This pin serves as waveform output of PWM channel 7 and as an input for the emergency shutdown feature. 12.2.2 PWM6 — PWM Channel 6 This pin serves as waveform output of PWM channel 6. MC9S12KG128 Data Sheet, Rev. 1.15 380 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.2.3 PWM5 — PWM Channel 5 This pin serves as waveform output of PWM channel 5. 12.2.4 PWM4 — PWM Channel 4 This pin serves as waveform output of PWM channel 4. 12.2.5 PWM3 — PWM Channel 3 This pin serves as waveform output of PWM channel 3. 12.2.6 PWM3 — PWM Channel 2 This pin serves as waveform output of PWM channel 2. 12.2.7 PWM3 — PWM Channel 1 This pin serves as waveform output of PWM channel 1. 12.2.8 PWM3 — PWM Channel 0 This pin serves as waveform output of PWM channel 0. 12.3 Memory Map and Register Definition This section describes in detail all the registers and register bits in the PWM module. The special-purpose registers and register bit functions that are not normally available to device end users, such as factory test control registers and reserved registers, are clearly identified by means of shading the appropriate portions of address maps and register diagrams. Notes explaining the reasons for restricting access to the registers and functions are also explained in the individual register descriptions. 12.3.1 Module Memory Map This section describes the content of the registers in the PWM module. The base address of the PWM module is determined at the MCU level when the MCU is defined. The register decode map is fixed and begins at the first address of the module address offset. The figure below shows the registers associated with the PWM and their relative offset from the base address. The register detail description follows the order they appear in the register map. Reserved bits within a register will always read as 0 and the write will be unimplemented. Unimplemented functions are indicated by shading the bit. . MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 381 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) NOTE Register Address = Base Address + Address Offset, where the Base Address is defined at the MCU level and the Address Offset is defined at the module level. 12.3.2 Register Descriptions This section describes in detail all the registers and register bits in the PWM module. Register Name PWME R W PWMPOL R W PWMCLK R W PWMPRCLK R W PWMCAE R W PWMCTL R W PWMTST1 R W PWMPRSC1 R W PWMSCLA R W PWMSCLB R W PWMSCNTA R 1 Bit 7 PWME7 6 PWME6 5 PWME5 4 PWME4 3 PWME3 2 PWME2 1 PWME1 Bit 0 PWME0 PPOL7 PPOL6 PPOL5 PPOL4 PPOL3 PPOL2 PPOL1 PPOL0 PCLK7 0 PCLKL6 PCLK5 PCLK4 PCLK3 0 PCLK2 PCLK1 PCLK0 PCKB2 PCKB1 PCKB0 PCKA2 PCKA1 PCKA0 CAE7 CAE6 CAE5 CAE4 CAE3 CAE2 CAE1 0 CAE0 0 CON67 0 CON45 0 CON23 0 CON01 0 PSWAI 0 PFRZ 0 0 0 0 0 0 0 0 0 0 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 0 6 0 5 0 4 0 3 0 2 0 1 0 Bit 0 0 W 0 0 0 0 0 0 0 0 PWMSCNTB R 1 W = Unimplemented or Reserved Figure 12-2. PWM Register Summary (Sheet 1 of 3) MC9S12KG128 Data Sheet, Rev. 1.15 382 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Register Name PWMCNT0 R W PWMCNT1 R W PWMCNT2 R W PWMCNT3 R W PWMCNT4 R W PWMCNT5 R W PWMCNT6 R W PWMCNT7 R W PWMPER0 R W PWMPER1 R W PWMPER2 R W PWMPER3 R W PWMPER4 R W PWMPER5 R W PWMPER6 R W Bit 7 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 0 Bit 7 6 6 0 6 0 6 0 6 0 6 0 6 0 6 0 6 0 6 5 5 0 5 0 5 0 5 0 5 0 5 0 5 0 5 0 5 4 4 0 4 0 4 0 4 0 4 0 4 0 4 0 4 0 4 3 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 0 3 2 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Bit 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 0 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 = Unimplemented or Reserved Figure 12-2. PWM Register Summary (Sheet 2 of 3) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 383 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Register Name PWMPER7 R W PWMDTY0 R W PWMDTY1 R W PWMDTY2 R W PWMDTY3 R W PWMDTY4 R W PWMDTY5 R W PWMDTY6 R W PWMDTY7 R W PWMSDN R W Bit 7 Bit 7 6 6 5 5 4 4 3 3 2 2 1 1 Bit 0 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 4 3 2 1 Bit 0 Bit 7 6 5 0 PWMRSTRT 4 3 0 2 PWM7IN 1 Bit 0 PWMIF PWMIE PWMLVL PWM7INL PWM7ENA = Unimplemented or Reserved Figure 12-2. PWM Register Summary (Sheet 3 of 3) 1 Intended for factory test purposes only. 12.3.2.1 PWM Enable Register (PWME) Each PWM channel has an enable bit (PWMEx) to start its waveform output. When any of the PWMEx bits are set (PWMEx = 1), the associated PWM output is enabled immediately. However, the actual PWM waveform is not available on the associated PWM output until its clock source begins its next cycle due to the synchronization of PWMEx and the clock source. NOTE The first PWM cycle after enabling the channel can be irregular. An exception to this is when channels are concatenated. Once concatenated mode is enabled (CONxx bits set in PWMCTL register), enabling/disabling the corresponding 16-bit PWM channel is controlled by the MC9S12KG128 Data Sheet, Rev. 1.15 384 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) low order PWMEx bit.In this case, the high order bytes PWMEx bits have no effect and their corresponding PWM output lines are disabled. While in run mode, if all eight PWM channels are disabled (PWME7–0 = 0), the prescaler counter shuts off for power savings. 7 6 5 4 3 2 1 0 R W Reset PWME7 0 PWME6 0 PWME5 0 PWME4 0 PWME3 0 PWME2 0 PWME1 0 PWME0 0 Figure 12-3. PWM Enable Register (PWME) Read: Anytime Write: Anytime Table 12-1. PWME Field Descriptions Field 7 PWME7 Description Pulse Width Channel 7 Enable 0 Pulse width channel 7 is disabled. 1 Pulse width channel 7 is enabled. The pulse modulated signal becomes available at PWM output bit 7 when its clock source begins its next cycle. Pulse Width Channel 6 Enable 0 Pulse width channel 6 is disabled. 1 Pulse width channel 6 is enabled. The pulse modulated signal becomes available at PWM output bit6 when its clock source begins its next cycle. If CON67=1, then bit has no effect and PWM output line 6 is disabled. Pulse Width Channel 5 Enable 0 Pulse width channel 5 is disabled. 1 Pulse width channel 5 is enabled. The pulse modulated signal becomes available at PWM output bit 5 when its clock source begins its next cycle. Pulse Width Channel 4 Enable 0 Pulse width channel 4 is disabled. 1 Pulse width channel 4 is enabled. The pulse modulated signal becomes available at PWM, output bit 4 when its clock source begins its next cycle. If CON45 = 1, then bit has no effect and PWM output bit4 is disabled. Pulse Width Channel 3 Enable 0 Pulse width channel 3 is disabled. 1 Pulse width channel 3 is enabled. The pulse modulated signal becomes available at PWM, output bit 3 when its clock source begins its next cycle. Pulse Width Channel 2 Enable 0 Pulse width channel 2 is disabled. 1 Pulse width channel 2 is enabled. The pulse modulated signal becomes available at PWM, output bit 2 when its clock source begins its next cycle. If CON23 = 1, then bit has no effect and PWM output bit2 is disabled. Pulse Width Channel 1 Enable 0 Pulse width channel 1 is disabled. 1 Pulse width channel 1 is enabled. The pulse modulated signal becomes available at PWM, output bit 1 when its clock source begins its next cycle. Pulse Width Channel 0 Enable 0 Pulse width channel 0 is disabled. 1 Pulse width channel 0 is enabled. The pulse modulated signal becomes available at PWM, output bit 0 when its clock source begins its next cycle. If CON01 = 1, then bit has no effect and PWM output line0 is disabled. 6 PWME6 5 PWME5 4 PWME4 3 PWME3 2 PWME2 1 PWME1 0 PWME0 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 385 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.3.2.2 PWM Polarity Register (PWMPOL) The starting polarity of each PWM channel waveform is determined by the associated PPOLx bit in the PWMPOL register. If the polarity bit is one, the PWM channel output is high at the beginning of the cycle and then goes low when the duty count is reached. Conversely, if the polarity bit is zero, the output starts low and then goes high when the duty count is reached. 7 6 5 4 3 2 1 0 R W Reset PPOL7 0 PPOL6 0 PPOL5 0 PPOL4 0 PPOL3 0 PPOL2 0 PPOL1 0 PPOL0 0 Figure 12-4. PWM Polarity Register (PWMPOL) Read: Anytime Write: Anytime NOTE PPOLx register bits can be written anytime. If the polarity is changed while a PWM signal is being generated, a truncated or stretched pulse can occur during the transition Table 12-2. PWMPOL Field Descriptions Field 7–0 PPOL[7:0] Description Pulse Width Channel 7–0 Polarity Bits 0 PWM channel 7–0 outputs are low at the beginning of the period, then go high when the duty count is reached. 1 PWM channel 7–0 outputs are high at the beginning of the period, then go low when the duty count is reached. 12.3.2.3 PWM Clock Select Register (PWMCLK) Each PWM channel has a choice of two clocks to use as the clock source for that channel as described below. 7 6 5 4 3 2 1 0 R W Reset PCLK7 0 PCLKL6 0 PCLK5 0 PCLK4 0 PCLK3 0 PCLK2 0 PCLK1 0 PCLK0 0 Figure 12-5. PWM Clock Select Register (PWMCLK) Read: Anytime Write: Anytime MC9S12KG128 Data Sheet, Rev. 1.15 386 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) NOTE Register bits PCLK0 to PCLK7 can be written anytime. If a clock select is changed while a PWM signal is being generated, a truncated or stretched pulse can occur during the transition. Table 12-3. PWMCLK Field Descriptions Field 7 PCLK7 6 PCLK6 5 PCLK5 4 PCLK4 3 PCLK3 2 PCLK2 1 PCLK1 0 PCLK0 Description Pulse Width Channel 7 Clock Select 0 Clock B is the clock source for PWM channel 7. 1 Clock SB is the clock source for PWM channel 7. Pulse Width Channel 6 Clock Select 0 Clock B is the clock source for PWM channel 6. 1 Clock SB is the clock source for PWM channel 6. Pulse Width Channel 5 Clock Select 0 Clock A is the clock source for PWM channel 5. 1 Clock SA is the clock source for PWM channel 5. Pulse Width Channel 4 Clock Select 0 Clock A is the clock source for PWM channel 4. 1 Clock SA is the clock source for PWM channel 4. Pulse Width Channel 3 Clock Select 0 Clock B is the clock source for PWM channel 3. 1 Clock SB is the clock source for PWM channel 3. Pulse Width Channel 2 Clock Select 0 Clock B is the clock source for PWM channel 2. 1 Clock SB is the clock source for PWM channel 2. Pulse Width Channel 1 Clock Select 0 Clock A is the clock source for PWM channel 1. 1 Clock SA is the clock source for PWM channel 1. Pulse Width Channel 0 Clock Select 0 Clock A is the clock source for PWM channel 0. 1 Clock SA is the clock source for PWM channel 0. 12.3.2.4 PWM Prescale Clock Select Register (PWMPRCLK) This register selects the prescale clock source for clocks A and B independently. 7 6 5 4 3 2 1 0 R W Reset 0 0 PCKB2 0 PCKB1 0 PCKB0 0 0 0 PCKA2 0 PCKA1 0 PCKA0 0 = Unimplemented or Reserved Figure 12-6. PWM Prescale Clock Select Register (PWMPRCLK) Read: Anytime Write: Anytime MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 387 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) NOTE PCKB2–0 and PCKA2–0 register bits can be written anytime. If the clock pre-scale is changed while a PWM signal is being generated, a truncated or stretched pulse can occur during the transition. Table 12-4. PWMPRCLK Field Descriptions Field 6–4 PCKB[2:0] 2–0 PCKA[2:0] s Description Prescaler Select for Clock B — Clock B is one of two clock sources which can be used for channels 2, 3, 6, or 7. These three bits determine the rate of clock B, as shown in Table 12-5. Prescaler Select for Clock A — Clock A is one of two clock sources which can be used for channels 0, 1, 4 or 5. These three bits determine the rate of clock A, as shown in Table 12-6. Table 12-5. Clock B Prescaler Selects PCKB2 0 0 0 0 1 1 1 1 PCKB1 0 0 1 1 0 0 1 1 PCKB0 0 1 0 1 0 1 0 1 Value of Clock B Bus clock Bus clock / 2 Bus clock / 4 Bus clock / 8 Bus clock / 16 Bus clock / 32 Bus clock / 64 Bus clock / 128 Table 12-6. Clock A Prescaler Selects PCKA2 0 0 0 0 1 1 1 1 PCKA1 0 0 1 1 0 0 1 1 PCKA0 0 1 0 1 0 1 0 1 Value of Clock A Bus clock Bus clock / 2 Bus clock / 4 Bus clock / 8 Bus clock / 16 Bus clock / 32 Bus clock / 64 Bus clock / 128 12.3.2.5 PWM Center Align Enable Register (PWMCAE) The PWMCAE register contains eight control bits for the selection of center aligned outputs or left aligned outputs for each PWM channel. If the CAEx bit is set to a one, the corresponding PWM output will be center aligned. If the CAEx bit is cleared, the corresponding PWM output will be left aligned. See Section 12.4.2.5, “Left Aligned Outputs” and Section 12.4.2.6, “Center Aligned Outputs” for a more detailed description of the PWM output modes. 7 6 5 4 3 2 1 0 R W Reset CAE7 0 CAE6 0 CAE5 0 CAE4 0 CAE3 0 CAE2 0 CAE1 0 CAE0 0 Figure 12-7. PWM Center Align Enable Register (PWMCAE) MC9S12KG128 Data Sheet, Rev. 1.15 388 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Read: Anytime Write: Anytime NOTE Write these bits only when the corresponding channel is disabled. Table 12-7. PWMCAE Field Descriptions Field 7–0 CAE[7:0] Description Center Aligned Output Modes on Channels 7–0 0 Channels 7–0 operate in left aligned output mode. 1 Channels 7–0 operate in center aligned output mode. 12.3.2.6 PWM Control Register (PWMCTL) The PWMCTL register provides for various control of the PWM module. 7 6 5 4 3 2 1 0 R W Reset CON67 0 CON45 0 CON23 0 CON01 0 PSWAI 0 PFRZ 0 0 0 0 0 = Unimplemented or Reserved Figure 12-8. PWM Control Register (PWMCTL) Read: Anytime Write: Anytime There are three control bits for concatenation, each of which is used to concatenate a pair of PWM channels into one 16-bit channel. When channels 6 and 7are concatenated, channel 6 registers become the high order bytes of the double byte channel. When channels 4 and 5 are concatenated, channel 4 registers become the high order bytes of the double byte channel. When channels 2 and 3 are concatenated, channel 2 registers become the high order bytes of the double byte channel. When channels 0 and 1 are concatenated, channel 0 registers become the high order bytes of the double byte channel. See Section 12.4.2.7, “PWM 16-Bit Functions” for a more detailed description of the concatenation PWM Function. NOTE Change these bits only when both corresponding channels are disabled. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 389 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Table 12-8. PWMCTL Field Descriptions Field 7 CON67 Description Concatenate Channels 6 and 7 0 Channels 6 and 7 are separate 8-bit PWMs. 1 Channels 6 and 7 are concatenated to create one 16-bit PWM channel. Channel 6 becomes the high order byte and channel 7 becomes the low order byte. Channel 7 output pin is used as the output for this 16-bit PWM (bit 7 of port PWMP). Channel 7 clock select control-bit determines the clock source, channel 7 polarity bit determines the polarity, channel 7 enable bit enables the output and channel 7 center aligned enable bit determines the output mode. Concatenate Channels 4 and 5 0 Channels 4 and 5 are separate 8-bit PWMs. 1 Channels 4 and 5 are concatenated to create one 16-bit PWM channel. Channel 4 becomes the high order byte and channel 5 becomes the low order byte. Channel 5 output pin is used as the output for this 16-bit PWM (bit 5 of port PWMP). Channel 5 clock select control-bit determines the clock source, channel 5 polarity bit determines the polarity, channel 5 enable bit enables the output and channel 5 center aligned enable bit determines the output mode. Concatenate Channels 2 and 3 0 Channels 2 and 3 are separate 8-bit PWMs. 1 Channels 2 and 3 are concatenated to create one 16-bit PWM channel. Channel 2 becomes the high order byte and channel 3 becomes the low order byte. Channel 3 output pin is used as the output for this 16-bit PWM (bit 3 of port PWMP). Channel 3 clock select control-bit determines the clock source, channel 3 polarity bit determines the polarity, channel 3 enable bit enables the output and channel 3 center aligned enable bit determines the output mode. Concatenate Channels 0 and 1 0 Channels 0 and 1 are separate 8-bit PWMs. 1 Channels 0 and 1 are concatenated to create one 16-bit PWM channel. Channel 0 becomes the high order byte and channel 1 becomes the low order byte. Channel 1 output pin is used as the output for this 16-bit PWM (bit 1 of port PWMP). Channel 1 clock select control-bit determines the clock source, channel 1 polarity bit determines the polarity, channel 1 enable bit enables the output and channel 1 center aligned enable bit determines the output mode. PWM Stops in Wait Mode — Enabling this bit allows for lower power consumption in wait mode by disabling the input clock to the prescaler. 0 Allow the clock to the prescaler to continue while in wait mode. 1 Stop the input clock to the prescaler whenever the MCU is in wait mode. PWM Counters Stop in Freeze Mode — In freeze mode, there is an option to disable the input clock to the prescaler by setting the PFRZ bit in the PWMCTL register. If this bit is set, whenever the MCU is in freeze mode, the input clock to the prescaler is disabled. This feature is useful during emulation as it allows the PWM function to be suspended. In this way, the counters of the PWM can be stopped while in freeze mode so that once normal program flow is continued, the counters are re-enabled to simulate real-time operations. Since the registers can still be accessed in this mode, to re-enable the prescaler clock, either disable the PFRZ bit or exit freeze mode. 0 Allow PWM to continue while in freeze mode. 1 Disable PWM input clock to the prescaler whenever the part is in freeze mode. This is useful for emulation. 6 CON45 5 CON23 4 CON01 3 PSWAI 2 PFREZ 12.3.2.7 Reserved Register (PWMTST) This register is reserved for factory testing of the PWM module and is not available in normal modes. MC9S12KG128 Data Sheet, Rev. 1.15 390 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 12-9. Reserved Register (PWMTST) Read: Always read $00 in normal modes Write: Unimplemented in normal modes NOTE Writing to this register when in special modes can alter the PWM functionality. 12.3.2.8 Reserved Register (PWMPRSC) This register is reserved for factory testing of the PWM module and is not available in normal modes. 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 12-10. Reserved Register (PWMPRSC) Read: Always read $00 in normal modes Write: Unimplemented in normal modes NOTE Writing to this register when in special modes can alter the PWM functionality. 12.3.2.9 PWM Scale A Register (PWMSCLA) PWMSCLA is the programmable scale value used in scaling clock A to generate clock SA. Clock SA is generated by taking clock A, dividing it by the value in the PWMSCLA register and dividing that by two. Clock SA = Clock A / (2 * PWMSCLA) NOTE When PWMSCLA = $00, PWMSCLA value is considered a full scale value of 256. Clock A is thus divided by 512. Any value written to this register will cause the scale counter to load the new scale value (PWMSCLA). MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 391 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 7 6 5 4 3 2 1 0 R W Reset Bit 7 0 6 0 5 0 4 0 3 0 2 0 1 0 Bit 0 0 Figure 12-11. PWM Scale A Register (PWMSCLA) Read: Anytime Write: Anytime (causes the scale counter to load the PWMSCLA value) 12.3.2.10 PWM Scale B Register (PWMSCLB) PWMSCLB is the programmable scale value used in scaling clock B to generate clock SB. Clock SB is generated by taking clock B, dividing it by the value in the PWMSCLB register and dividing that by two. Clock SB = Clock B / (2 * PWMSCLB) NOTE When PWMSCLB = $00, PWMSCLB value is considered a full scale value of 256. Clock B is thus divided by 512. Any value written to this register will cause the scale counter to load the new scale value (PWMSCLB). 7 6 5 4 3 2 1 0 R W Reset Bit 7 0 6 0 5 0 4 0 3 0 2 0 1 0 Bit 0 0 Figure 12-12. PWM Scale B Register (PWMSCLB) Read: Anytime Write: Anytime (causes the scale counter to load the PWMSCLB value). 12.3.2.11 Reserved Registers (PWMSCNTx) The registers PWMSCNTA and PWMSCNTB are reserved for factory testing of the PWM module and are not available in normal modes. 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 12-13. Reserved Registers (PWMSCNTx) Read: Always read $00 in normal modes Write: Unimplemented in normal modes MC9S12KG128 Data Sheet, Rev. 1.15 392 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) NOTE Writing to these registers when in special modes can alter the PWM functionality. 12.3.2.12 PWM Channel Counter Registers (PWMCNTx) Each channel has a dedicated 8-bit up/down counter which runs at the rate of the selected clock source. The counter can be read at any time without affecting the count or the operation of the PWM channel. In left aligned output mode, the counter counts from 0 to the value in the period register - 1. In center aligned output mode, the counter counts from 0 up to the value in the period register and then back down to 0. Any value written to the counter causes the counter to reset to $00, the counter direction to be set to up, the immediate load of both duty and period registers with values from the buffers, and the output to change according to the polarity bit. The counter is also cleared at the end of the effective period (see Section 12.4.2.5, “Left Aligned Outputs” and Section 12.4.2.6, “Center Aligned Outputs” for more details). When the channel is disabled (PWMEx = 0), the PWMCNTx register does not count. When a channel becomes enabled (PWMEx = 1), the associated PWM counter starts at the count in the PWMCNTx register. For more detailed information on the operation of the counters, see Section 12.4.2.4, “PWM Timer Counters”. In concatenated mode, writes to the 16-bit counter by using a 16-bit access or writes to either the low or high order byte of the counter will reset the 16-bit counter. Reads of the 16-bit counter must be made by 16-bit access to maintain data coherency. NOTE Writing to the counter while the channel is enabled can cause an irregular PWM cycle to occur. 7 6 5 4 3 2 1 0 R W Reset Bit 7 0 0 6 0 0 5 0 0 4 0 0 3 0 0 2 0 0 1 0 0 Bit 0 0 0 Figure 12-14. PWM Channel Counter Registers (PWMCNTx) Read: Anytime Write: Anytime (any value written causes PWM counter to be reset to $00). 12.3.2.13 PWM Channel Period Registers (PWMPERx) There is a dedicated period register for each channel. The value in this register determines the period of the associated PWM channel. The period registers for each channel are double buffered so that if they change while the channel is enabled, the change will NOT take effect until one of the following occurs: • The effective period ends • The counter is written (counter resets to $00) • The channel is disabled MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 393 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) In this way, the output of the PWM will always be either the old waveform or the new waveform, not some variation in between. If the channel is not enabled, then writes to the period register will go directly to the latches as well as the buffer. NOTE Reads of this register return the most recent value written. Reads do not necessarily return the value of the currently active period due to the double buffering scheme. See Section 12.4.2.3, “PWM Period and Duty” for more information. To calculate the output period, take the selected clock source period for the channel of interest (A, B, SA, or SB) and multiply it by the value in the period register for that channel: • Left aligned output (CAEx = 0) • PWMx Period = Channel Clock Period * PWMPERx Center Aligned Output (CAEx = 1) PWMx Period = Channel Clock Period * (2 * PWMPERx) For boundary case programming values, please refer to Section 12.4.2.8, “PWM Boundary Cases”. 7 6 5 4 3 2 1 0 R W Reset Bit 7 1 6 1 5 1 4 1 3 1 2 1 1 1 Bit 0 1 Figure 12-15. PWM Channel Period Registers (PWMPERx) Read: Anytime Write: Anytime 12.3.2.14 PWM Channel Duty Registers (PWMDTYx) There is a dedicated duty register for each channel. The value in this register determines the duty of the associated PWM channel. The duty value is compared to the counter and if it is equal to the counter value a match occurs and the output changes state. The duty registers for each channel are double buffered so that if they change while the channel is enabled, the change will NOT take effect until one of the following occurs: • The effective period ends • The counter is written (counter resets to $00) • The channel is disabled In this way, the output of the PWM will always be either the old duty waveform or the new duty waveform, not some variation in between. If the channel is not enabled, then writes to the duty register will go directly to the latches as well as the buffer. MC9S12KG128 Data Sheet, Rev. 1.15 394 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) NOTE Reads of this register return the most recent value written. Reads do not necessarily return the value of the currently active duty due to the double buffering scheme. See Section 12.4.2.3, “PWM Period and Duty” for more information. NOTE Depending on the polarity bit, the duty registers will contain the count of either the high time or the low time. If the polarity bit is one, the output starts high and then goes low when the duty count is reached, so the duty registers contain a count of the high time. If the polarity bit is zero, the output starts low and then goes high when the duty count is reached, so the duty registers contain a count of the low time. To calculate the output duty cycle (high time as a% of period) for a particular channel: • Polarity = 0 (PPOL x =0) Duty Cycle = [(PWMPERx-PWMDTYx)/PWMPERx] * 100% • Polarity = 1 (PPOLx = 1) Duty Cycle = [PWMDTYx / PWMPERx] * 100% For boundary case programming values, please refer to Section 12.4.2.8, “PWM Boundary Cases”. 7 6 5 4 3 2 1 0 R W Reset Bit 7 1 6 1 5 1 4 1 3 1 2 1 1 1 Bit 0 1 Figure 12-16. PWM Channel Duty Registers (PWMDTYx) Read: Anytime Write: Anytime 12.3.2.15 PWM Shutdown Register (PWMSDN) The PWMSDN register provides for the shutdown functionality of the PWM module in the emergency cases. For proper operation, channel 7 must be driven to the active level for a minimum of two bus clocks. 7 6 5 4 3 2 1 0 R W Reset PWMIF 0 PWMIE 0 0 PWMRSTRT 0 PWMLVL 0 0 0 PWM7IN 0 PWM7INL 0 PWM7ENA 0 = Unimplemented or Reserved Figure 12-17. PWM Shutdown Register (PWMSDN) Read: Anytime Write: Anytime MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 395 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Table 12-9. PWMSDN Field Descriptions Field 7 PWMIF Description PWM Interrupt Flag — Any change from passive to asserted (active) state or from active to passive state will be flagged by setting the PWMIF flag = 1. The flag is cleared by writing a logic 1 to it. Writing a 0 has no effect. 0 No change on PWM7IN input. 1 Change on PWM7IN input PWM Interrupt Enable — If interrupt is enabled an interrupt to the CPU is asserted. 0 PWM interrupt is disabled. 1 PWM interrupt is enabled. 6 PWMIE 5 PWM Restart — The PWM can only be restarted if the PWM channel input 7 is de-asserted. After writing a logic PWMRSTRT 1 to the PWMRSTRT bit (trigger event) the PWM channels start running after the corresponding counter passes next “counter == 0” phase. Also, if the PWM7ENA bit is reset to 0, the PWM do not start before the counter passes $00. The bit is always read as “0”. 4 PWMLVL PWM Shutdown Output Level If active level as defined by the PWM7IN input, gets asserted all enabled PWM channels are immediately driven to the level defined by PWMLVL. 0 PWM outputs are forced to 0 1 Outputs are forced to 1. PWM Channel 7 Input Status — This reflects the current status of the PWM7 pin. PWM Shutdown Active Input Level for Channel 7 — If the emergency shutdown feature is enabled (PWM7ENA = 1), this bit determines the active level of the PWM7channel. 0 Active level is low 1 Active level is high PWM Emergency Shutdown Enable — If this bit is logic 1, the pin associated with channel 7 is forced to input and the emergency shutdown feature is enabled. All the other bits in this register are meaningful only if PWM7ENA = 1. 0 PWM emergency feature disabled. 1 PWM emergency feature is enabled. 2 PWM7IN 1 PWM7INL 0 PWM7ENA 12.4 12.4.1 Functional Description PWM Clock Select There are four available clocks: clock A, clock B, clock SA (scaled A), and clock SB (scaled B). These four clocks are based on the bus clock. Clock A and B can be software selected to be 1, 1/2, 1/4, 1/8,..., 1/64, 1/128 times the bus clock. Clock SA uses clock A as an input and divides it further with a reloadable counter. Similarly, clock SB uses clock B as an input and divides it further with a reloadable counter. The rates available for clock SA are software selectable to be clock A divided by 2, 4, 6, 8,..., or 512 in increments of divide by 2. Similar rates are available for clock SB. Each PWM channel has the capability of selecting one of two clocks, either the pre-scaled clock (clock A or B) or the scaled clock (clock SA or SB). The block diagram in Figure 12-18 shows the four different clocks and how the scaled clocks are created. MC9S12KG128 Data Sheet, Rev. 1.15 396 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.4.1.1 Prescale The input clock to the PWM prescaler is the bus clock. It can be disabled whenever the part is in freeze mode by setting the PFRZ bit in the PWMCTL register. If this bit is set, whenever the MCU is in freeze mode (freeze mode signal active) the input clock to the prescaler is disabled. This is useful for emulation in order to freeze the PWM. The input clock can also be disabled when all eight PWM channels are disabled (PWME7-0 = 0). This is useful for reducing power by disabling the prescale counter. Clock A and clock B are scaled values of the input clock. The value is software selectable for both clock A and clock B and has options of 1, 1/2, 1/4, 1/8, 1/16, 1/32, 1/64, or 1/128 times the bus clock. The value selected for clock A is determined by the PCKA2, PCKA1, PCKA0 bits in the PWMPRCLK register. The value selected for clock B is determined by the PCKB2, PCKB1, PCKB0 bits also in the PWMPRCLK register. 12.4.1.2 Clock Scale The scaled A clock uses clock A as an input and divides it further with a user programmable value and then divides this by 2. The scaled B clock uses clock B as an input and divides it further with a user programmable value and then divides this by 2. The rates available for clock SA are software selectable to be clock A divided by 2, 4, 6, 8,..., or 512 in increments of divide by 2. Similar rates are available for clock SB. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 397 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Clock A Clock A/2, A/4, A/6,....A/512 M U X PCLK0 M U X Clock to PWM Ch 0 PCKA2 PCKA1 PCKA0 8-Bit Down Counter Count = 1 Load PWMSCLA M U X 2 4 8 16 32 64 128 DIV 2 Clock SA Clock to PWM Ch 1 PCLK1 M U X PCLK2 M U X PCLK3 Clock to PWM Ch 3 Clock to PWM Ch 2 Divide by Prescaler Taps: Clock B Clock B/2, B/4, B/6,....B/512 M U X PCLK4 Clock to PWM Ch 4 M U X 8-Bit Down Counter Count = 1 Load PWMSCLB DIV 2 Clock SB M U X PCLK5 M U X PCLK6 M U X PCLK7 Clock to PWM Ch 5 Clock to PWM Ch 6 Bus Clock PFRZ Freeze Mode Signal PWME7-0 PCKB2 PCKB1 PCKB0 Clock to PWM Ch 7 Prescale Scale Clock Select Figure 12-18. PWM Clock Select Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 398 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Clock A is used as an input to an 8-bit down counter. This down counter loads a user programmable scale value from the scale register (PWMSCLA). When the down counter reaches one, a pulse is output and the 8-bit counter is re-loaded. The output signal from this circuit is further divided by two. This gives a greater range with only a slight reduction in granularity. Clock SA equals clock A divided by two times the value in the PWMSCLA register. NOTE Clock SA = Clock A / (2 * PWMSCLA) When PWMSCLA = $00, PWMSCLA value is considered a full scale value of 256. Clock A is thus divided by 512. Similarly, clock B is used as an input to an 8-bit down counter followed by a divide by two producing clock SB. Thus, clock SB equals clock B divided by two times the value in the PWMSCLB register. NOTE Clock SB = Clock B / (2 * PWMSCLB) When PWMSCLB = $00, PWMSCLB value is considered a full scale value of 256. Clock B is thus divided by 512. As an example, consider the case in which the user writes $FF into the PWMSCLA register. Clock A for this case will be E divided by 4. A pulse will occur at a rate of once every 255x4 E cycles. Passing this through the divide by two circuit produces a clock signal at an E divided by 2040 rate. Similarly, a value of $01 in the PWMSCLA register when clock A is E divided by 4 will produce a clock at an E divided by 8 rate. Writing to PWMSCLA or PWMSCLB causes the associated 8-bit down counter to be re-loaded. Otherwise, when changing rates the counter would have to count down to $01 before counting at the proper rate. Forcing the associated counter to re-load the scale register value every time PWMSCLA or PWMSCLB is written prevents this. NOTE Writing to the scale registers while channels are operating can cause irregularities in the PWM outputs. 12.4.1.3 Clock Select Each PWM channel has the capability of selecting one of two clocks. For channels 0, 1, 4, and 5 the clock choices are clock A or clock SA. For channels 2, 3, 6, and 7 the choices are clock B or clock SB. The clock selection is done with the PCLKx control bits in the PWMCLK register. NOTE Changing clock control bits while channels are operating can cause irregularities in the PWM outputs. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 399 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.4.2 PWM Channel Timers The main part of the PWM module are the actual timers. Each of the timer channels has a counter, a period register and a duty register (each are 8-bit). The waveform output period is controlled by a match between the period register and the value in the counter. The duty is controlled by a match between the duty register and the counter value and causes the state of the output to change during the period. The starting polarity of the output is also selectable on a per channel basis. Shown below in Figure 12-19 is the block diagram for the PWM timer. Clock Source 8-Bit Counter Gate (Clock Edge Sync) Up/Down Reset 8-bit Compare = T PWMDTYx R 8-bit Compare = PWMPERx PPOLx Q Q M U X M U X To Pin Driver PWMCNTx From Port PWMP Data Register Q Q T R CAEx PWMEx Figure 12-19. PWM Timer Channel Block Diagram 12.4.2.1 PWM Enable Each PWM channel has an enable bit (PWMEx) to start its waveform output. When any of the PWMEx bits are set (PWMEx = 1), the associated PWM output signal is enabled immediately. However, the actual PWM waveform is not available on the associated PWM output until its clock source begins its next cycle due to the synchronization of PWMEx and the clock source. An exception to this is when channels are concatenated. Refer to Section 12.4.2.7, “PWM 16-Bit Functions” for more detail. NOTE The first PWM cycle after enabling the channel can be irregular. MC9S12KG128 Data Sheet, Rev. 1.15 400 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) On the front end of the PWM timer, the clock is enabled to the PWM circuit by the PWMEx bit being high. There is an edge-synchronizing circuit to guarantee that the clock will only be enabled or disabled at an edge. When the channel is disabled (PWMEx = 0), the counter for the channel does not count. 12.4.2.2 PWM Polarity Each channel has a polarity bit to allow starting a waveform cycle with a high or low signal. This is shown on the block diagram as a mux select of either the Q output or the Q output of the PWM output flip flop. When one of the bits in the PWMPOL register is set, the associated PWM channel output is high at the beginning of the waveform, then goes low when the duty count is reached. Conversely, if the polarity bit is zero, the output starts low and then goes high when the duty count is reached. 12.4.2.3 PWM Period and Duty Dedicated period and duty registers exist for each channel and are double buffered so that if they change while the channel is enabled, the change will NOT take effect until one of the following occurs: • The effective period ends • The counter is written (counter resets to $00) • The channel is disabled In this way, the output of the PWM will always be either the old waveform or the new waveform, not some variation in between. If the channel is not enabled, then writes to the period and duty registers will go directly to the latches as well as the buffer. A change in duty or period can be forced into effect “immediately” by writing the new value to the duty and/or period registers and then writing to the counter. This forces the counter to reset and the new duty and/or period values to be latched. In addition, since the counter is readable, it is possible to know where the count is with respect to the duty value and software can be used to make adjustments NOTE When forcing a new period or duty into effect immediately, an irregular PWM cycle can occur. Depending on the polarity bit, the duty registers will contain the count of either the high time or the low time. 12.4.2.4 PWM Timer Counters Each channel has a dedicated 8-bit up/down counter which runs at the rate of the selected clock source (see Section 12.4.1, “PWM Clock Select” for the available clock sources and rates). The counter compares to two registers, a duty register and a period register as shown in Figure 12-19. When the PWM counter matches the duty register, the output flip-flop changes state, causing the PWM waveform to also change state. A match between the PWM counter and the period register behaves differently depending on what output mode is selected as shown in Figure 12-19 and described in Section 12.4.2.5, “Left Aligned Outputs” and Section 12.4.2.6, “Center Aligned Outputs”. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 401 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Each channel counter can be read at anytime without affecting the count or the operation of the PWM channel. Any value written to the counter causes the counter to reset to $00, the counter direction to be set to up, the immediate load of both duty and period registers with values from the buffers, and the output to change according to the polarity bit. When the channel is disabled (PWMEx = 0), the counter stops. When a channel becomes enabled (PWMEx = 1), the associated PWM counter continues from the count in the PWMCNTx register. This allows the waveform to continue where it left off when the channel is re-enabled. When the channel is disabled, writing “0” to the period register will cause the counter to reset on the next selected clock. NOTE If the user wants to start a new “clean” PWM waveform without any “history” from the old waveform, the user must write to channel counter (PWMCNTx) prior to enabling the PWM channel (PWMEx = 1). Generally, writes to the counter are done prior to enabling a channel in order to start from a known state. However, writing a counter can also be done while the PWM channel is enabled (counting). The effect is similar to writing the counter when the channel is disabled, except that the new period is started immediately with the output set according to the polarity bit. NOTE Writing to the counter while the channel is enabled can cause an irregular PWM cycle to occur. The counter is cleared at the end of the effective period (see Section 12.4.2.5, “Left Aligned Outputs” and Section 12.4.2.6, “Center Aligned Outputs” for more details). Table 12-10. PWM Timer Counter Conditions Counter Clears ($00) When PWMCNTx register written to any value Effective period ends Counter Counts When PWM channel is enabled (PWMEx = 1). Counts from last value in PWMCNTx. Counter Stops When PWM channel is disabled (PWMEx = 0) 12.4.2.5 Left Aligned Outputs The PWM timer provides the choice of two types of outputs, left aligned or center aligned. They are selected with the CAEx bits in the PWMCAE register. If the CAEx bit is cleared (CAEx = 0), the corresponding PWM output will be left aligned. In left aligned output mode, the 8-bit counter is configured as an up counter only. It compares to two registers, a duty register and a period register as shown in the block diagram in Figure 12-19. When the PWM counter matches the duty register the output flip-flop changes state causing the PWM waveform to also change state. A match between the PWM counter and the period register resets the counter and the output flip-flop, as shown in Figure 12-19, as well as performing a load from the double buffer period and duty register to the associated registers, as described in Section 12.4.2.3, “PWM Period and Duty”. The counter counts from 0 to the value in the period register – 1. MC9S12KG128 Data Sheet, Rev. 1.15 402 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) NOTE Changing the PWM output mode from left aligned to center aligned output (or vice versa) while channels are operating can cause irregularities in the PWM output. It is recommended to program the output mode before enabling the PWM channel. PPOLx = 0 PPOLx = 1 PWMDTYx Period = PWMPERx Figure 12-20. PWM Left Aligned Output Waveform To calculate the output frequency in left aligned output mode for a particular channel, take the selected clock source frequency for the channel (A, B, SA, or SB) and divide it by the value in the period register for that channel. • PWMx Frequency = Clock (A, B, SA, or SB) / PWMPERx • PWMx Duty Cycle (high time as a% of period): — Polarity = 0 (PPOLx = 0) • Duty Cycle = [(PWMPERx-PWMDTYx)/PWMPERx] * 100% — Polarity = 1 (PPOLx = 1) Duty Cycle = [PWMDTYx / PWMPERx] * 100% As an example of a left aligned output, consider the following case: Clock Source = E, where E = 10 MHz (100 ns period) PPOLx = 0 PWMPERx = 4 PWMDTYx = 1 PWMx Frequency = 10 MHz/4 = 2.5 MHz PWMx Period = 400 ns PWMx Duty Cycle = 3/4 *100% = 75% The output waveform generated is shown in Figure 12-21. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 403 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) E = 100 ns Duty Cycle = 75% Period = 400 ns Figure 12-21. PWM Left Aligned Output Example Waveform 12.4.2.6 Center Aligned Outputs For center aligned output mode selection, set the CAEx bit (CAEx = 1) in the PWMCAE register and the corresponding PWM output will be center aligned. The 8-bit counter operates as an up/down counter in this mode and is set to up whenever the counter is equal to $00. The counter compares to two registers, a duty register and a period register as shown in the block diagram in Figure 12-19. When the PWM counter matches the duty register, the output flip-flop changes state, causing the PWM waveform to also change state. A match between the PWM counter and the period register changes the counter direction from an up-count to a down-count. When the PWM counter decrements and matches the duty register again, the output flip-flop changes state causing the PWM output to also change state. When the PWM counter decrements and reaches zero, the counter direction changes from a down-count back to an up-count and a load from the double buffer period and duty registers to the associated registers is performed, as described in Section 12.4.2.3, “PWM Period and Duty”. The counter counts from 0 up to the value in the period register and then back down to 0. Thus the effective period is PWMPERx*2. NOTE Changing the PWM output mode from left aligned to center aligned output (or vice versa) while channels are operating can cause irregularities in the PWM output. It is recommended to program the output mode before enabling the PWM channel. PPOLx = 0 PPOLx = 1 PWMDTYx PWMPERx Period = PWMPERx*2 PWMDTYx PWMPERx Figure 12-22. PWM Center Aligned Output Waveform MC9S12KG128 Data Sheet, Rev. 1.15 404 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) To calculate the output frequency in center aligned output mode for a particular channel, take the selected clock source frequency for the channel (A, B, SA, or SB) and divide it by twice the value in the period register for that channel. • PWMx Frequency = Clock (A, B, SA, or SB) / (2*PWMPERx) • PWMx Duty Cycle (high time as a% of period): — Polarity = 0 (PPOLx = 0) Duty Cycle = [(PWMPERx-PWMDTYx)/PWMPERx] * 100% — Polarity = 1 (PPOLx = 1) Duty Cycle = [PWMDTYx / PWMPERx] * 100% MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 405 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) As an example of a center aligned output, consider the following case: Clock Source = E, where E = 10 MHz (100 ns period) PPOLx = 0 PWMPERx = 4 PWMDTYx = 1 PWMx Frequency = 10 MHz/8 = 1.25 MHz PWMx Period = 800 ns PWMx Duty Cycle = 3/4 *100% = 75% Shown in Figure 12-23 is the output waveform generated. E = 100 ns E = 100 ns DUTY CYCLE = 75% PERIOD = 800 ns Figure 12-23. PWM Center Aligned Output Example Waveform 12.4.2.7 PWM 16-Bit Functions The PWM timer also has the option of generating 8-channels of 8-bits or 4-channels of 16-bits for greater PWM resolution. This 16-bit channel option is achieved through the concatenation of two 8-bit channels. The PWMCTL register contains four control bits, each of which is used to concatenate a pair of PWM channels into one 16-bit channel. Channels 6 and 7 are concatenated with the CON67 bit, channels 4 and 5 are concatenated with the CON45 bit, channels 2 and 3 are concatenated with the CON23 bit, and channels 0 and 1 are concatenated with the CON01 bit. NOTE Change these bits only when both corresponding channels are disabled. When channels 6 and 7 are concatenated, channel 6 registers become the high order bytes of the double byte channel, as shown in Figure 12-24. Similarly, when channels 4 and 5 are concatenated, channel 4 registers become the high order bytes of the double byte channel. When channels 2 and 3 are concatenated, channel 2 registers become the high order bytes of the double byte channel. When channels 0 and 1 are concatenated, channel 0 registers become the high order bytes of the double byte channel. When using the 16-bit concatenated mode, the clock source is determined by the low order 8-bit channel clock select control bits. That is channel 7 when channels 6 and 7 are concatenated, channel 5 when channels 4 and 5 are concatenated, channel 3 when channels 2 and 3 are concatenated, and channel 1 when channels 0 and 1 are concatenated. The resulting PWM is output to the pins of the corresponding low order 8-bit channel as also shown in Figure 12-24. The polarity of the resulting PWM output is controlled by the PPOLx bit of the corresponding low order 8-bit channel as well. MC9S12KG128 Data Sheet, Rev. 1.15 406 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Clock Source 7 High PWMCNT6 Low PWCNT7 Period/Duty Compare PWM7 Clock Source 5 High PWMCNT4 Low PWCNT5 Period/Duty Compare PWM5 Clock Source 3 High PWMCNT2 Low PWCNT3 Period/Duty Compare PWM3 Clock Source 1 High PWMCNT0 Low PWCNT1 Period/Duty Compare PWM1 Figure 12-24. PWM 16-Bit Mode Once concatenated mode is enabled (CONxx bits set in PWMCTL register), enabling/disabling the corresponding 16-bit PWM channel is controlled by the low order PWMEx bit. In this case, the high order bytes PWMEx bits have no effect and their corresponding PWM output is disabled. In concatenated mode, writes to the 16-bit counter by using a 16-bit access or writes to either the low or high order byte of the counter will reset the 16-bit counter. Reads of the 16-bit counter must be made by 16-bit access to maintain data coherency. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 407 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) Either left aligned or center aligned output mode can be used in concatenated mode and is controlled by the low order CAEx bit. The high order CAEx bit has no effect. Table 12-11 is used to summarize which channels are used to set the various control bits when in 16-bit mode. Table 12-11. 16-bit Concatenation Mode Summary CONxx CON67 CON45 CON23 CON01 PWMEx PWME7 PWME5 PWME3 PWME1 PPOLx PPOL7 PPOL5 PPOL3 PPOL1 PCLKx PCLK7 PCLK5 PCLK3 PCLK1 CAEx CAE7 CAE5 CAE3 CAE1 PWMx Output PWM7 PWM5 PWM3 PWM1 12.4.2.8 PWM Boundary Cases Table 12-12 summarizes the boundary conditions for the PWM regardless of the output mode (left aligned or center aligned) and 8-bit (normal) or 16-bit (concatenation). Table 12-12. PWM Boundary Cases PWMDTYx $00 (indicates no duty) $00 (indicates no duty) XX XX >= PWMPERx >= PWMPERx 1 PWMPERx >$00 >$00 $001 (indicates no period) $001 (indicates no period) XX XX PPOLx 1 0 1 0 1 0 PWMx Output Always low Always high Always high Always low Always high Always low Counter = $00 and does not count. 12.5 Resets The reset state of each individual bit is listed within the Section 12.3.2, “Register Descriptions” which details the registers and their bit-fields. All special functions or modes which are initialized during or just following reset are described within this section. • The 8-bit up/down counter is configured as an up counter out of reset. • All the channels are disabled and all the counters do not count. MC9S12KG128 Data Sheet, Rev. 1.15 408 Freescale Semiconductor Chapter 12 Pulse-Width Modulator (PWM8B8CV1) 12.6 Interrupts The PWM module has only one interrupt which is generated at the time of emergency shutdown, if the corresponding enable bit (PWMIE) is set. This bit is the enable for the interrupt. The interrupt flag PWMIF is set whenever the input level of the PWM7 channel changes while PWM7ENA = 1 or when PWMENA is being asserted while the level at PWM7 is active. In stop mode or wait mode (with the PSWAI bit set), the emergency shutdown feature will drive the PWM outputs to their shutdown output levels but the PWMIF flag will not be set. A description of the registers involved and affected due to this interrupt is explained in Section 12.3.2.15, “PWM Shutdown Register (PWMSDN)”. The PWM block only generates the interrupt and does not service it. The interrupt signal name is PWM interrupt signal. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 409 Chapter 12 Pulse-Width Modulator (PWM8B8CV1) MC9S12KG128 Data Sheet, Rev. 1.15 410 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 13.1 Introduction The basic timer consists of a 16-bit, software-programmable counter driven by a seven-stage programmable prescaler. This timer can be used for many purposes, including input waveform measurements while simultaneously generating an output waveform. Pulse widths can vary from microseconds to many seconds. This timer contains 8 complete input capture/output compare channels and one pulse accumulator. The input capture function is used to detect a selected transition edge and record the time. The output compare function is used for generating output signals or for timer software delays. The 16-bit pulse accumulator is used to operate as a simple event counter or a gated time accumulator. The pulse accumulator shares timer channel 7 when in event mode. A full access for the counter registers or the input capture/output compare registers should take place in one clock cycle. Accessing high byte and low byte separately for all of these registers may not yield the same result as accessing them in one word. 13.1.1 Features The TIM16B8C includes these distinctive features: • Eight input capture/output compare channels. • Clock prescaling. • 16-bit counter. • 16-bit pulse accumulator. 13.1.2 Stop: Freeze: Wait: Normal: Modes of Operation Timer is off because clocks are stopped. Timer counter keep on running, unless TSFRZ in TSCR (0x0006) is set to 1. Counters keep on running, unless TSWAI in TSCR (0x0006) is set to 1. Timer counter keep on running, unless TEN in TSCR (0x0006) is cleared to 0. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 411 Chapter 13 Timer Module (TIM16B8CV1) 13.1.3 Block Diagrams Channel 0 Input capture Output compare Channel 1 Input capture Output compare Channel 2 Input capture Output compare Channel 3 Input capture Output compare Registers Channel 4 Input capture Output compare Channel 5 Input capture Output compare Bus clock Prescaler IOC0 16-bit Counter IOC1 Timer overflow interrupt Timer channel 0 interrupt IOC2 IOC3 IOC4 IOC5 Timer channel 7 interrupt Channel 6 Input capture Output compare 16-bit Pulse accumulator Channel 7 Input capture Output compare IOC6 PA overflow interrupt PA input interrupt IOC7 Figure 13-1. TIM16B8C Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 412 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) TIMCLK (Timer clock) CLK1 CLK0 4:1 MUX PACLK / 256 Prescaled clock (PCLK) PACLK / 65536 Clock select (PAMOD) PACLK Edge detector PT7 Intermodule Bus Interrupt PACNT MUX Divide by 64 M clock Figure 13-2. 16-Bit Pulse Accumulator Block Diagram 16-bit Main Timer PTn Edge detector Set CnF Interrupt TCn Input Capture Reg. Figure 13-3. Interrupt Flag Setting MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 413 Chapter 13 Timer Module (TIM16B8CV1) PULSE ACCUMULATOR CHANNEL 7 OUTPUT COMPARE OM7 OL7 OC7M7 PAD Figure 13-4. Channel 7 Output Compare/Pulse Accumulator Logic NOTE For more information see the respective functional descriptions in Section 13.4, “Functional Description,” of this document. 13.2 External Signal Description The TIM16B8C module has a total of eight external pins. 13.2.1 IOC7 — Input Capture and Output Compare Channel 7 Pin This pin serves as input capture or output compare for channel 7. This can also be configured as pulse accumulator input. 13.2.2 IOC6 — Input Capture and Output Compare Channel 6 Pin This pin serves as input capture or output compare for channel 6. 13.2.3 IOC5 — Input Capture and Output Compare Channel 5 Pin This pin serves as input capture or output compare for channel 5. 13.2.4 IOC4 — Input Capture and Output Compare Channel 4 Pin This pin serves as input capture or output compare for channel 4. Pin 13.2.5 IOC3 — Input Capture and Output Compare Channel 3 Pin This pin serves as input capture or output compare for channel 3. MC9S12KG128 Data Sheet, Rev. 1.15 414 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 13.2.6 IOC2 — Input Capture and Output Compare Channel 2 Pin This pin serves as input capture or output compare for channel 2. 13.2.7 IOC1 — Input Capture and Output Compare Channel 1 Pin This pin serves as input capture or output compare for channel 1. 13.2.8 IOC0 — Input Capture and Output Compare Channel 0 Pin NOTE For the description of interrupts see Section 13.6, “Interrupts”. This pin serves as input capture or output compare for channel 0. 13.3 Memory Map and Register Definition This section provides a detailed description of all memory and registers. 13.3.1 Module Memory Map The memory map for the TIM16B8C module is given below in Table 13-1. The address listed for each register is the address offset. The total address for each register is the sum of the base address for the TIM16B8C module and the address offset for each register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 415 Chapter 13 Timer Module (TIM16B8CV1) Table 13-1. TIM16B8C Memory Map Address Offset 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F 0x0020 0x0021 0x0022 0x0023 0x002D 1 2 Use Timer Input Capture/Output Compare Select (TIOS) Timer Compare Force Register (CFORC) Output Compare 7 Mask Register (OC7M) Output Compare 7 Data Register (OC7D) Timer Count Register (TCNT(hi)) Timer Count Register (TCNT(lo)) Timer System Control Register1 (TSCR1) Timer Toggle Overflow Register (TTOV) Timer Control Register1 (TCTL1) Timer Control Register2 (TCTL2) Timer Control Register3 (TCTL3) Timer Control Register4 (TCTL4) Timer Interrupt Enable Register (TIE) Timer System Control Register2 (TSCR2) Main Timer Interrupt Flag1 (TFLG1) Main Timer Interrupt Flag2 (TFLG2) Timer Input Capture/Output Compare Register 0 (TC0(hi)) Timer Input Capture/Output Compare Register 0 (TC0(lo)) Timer Input Capture/Output Compare Register 1 (TC1(hi)) Timer Input Capture/Output Compare Register 1 (TC1(lo)) Timer Input Capture/Output Compare Register 2 (TC2(hi)) Timer Input Capture/Output Compare Register 2 (TC2(lo)) Timer Input Capture/Output Compare Register 3 (TC3(hi)) Timer Input Capture/Output Compare Register 3 (TC3(lo)) Timer Input Capture/Output Compare Register4 (TC4(hi)) Timer Input Capture/Output Compare Register 4 (TC4(lo)) Timer Input Capture/Output Compare Register 5 (TC5(hi)) Timer Input Capture/Output Compare Register 5 (TC5(lo)) Timer Input Capture/Output Compare Register 6 (TC6(hi)) Timer Input Capture/Output Compare Register 6 (TC6(lo)) Timer Input Capture/Output Compare Register 7 (TC7(hi)) Timer Input Capture/Output Compare Register 7 (TC7(lo)) 16-Bit Pulse Accumulator Control Register (PACTL) Pulse Accumulator Flag Register (PAFLG) Pulse Accumulator Count Register (PACNT(hi)) Pulse Accumulator Count Register (PACNT(lo)) Timer Test Register (TIMTST) Access R/W R/W1 R/W R/W R/W2 R/W2 R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W3 R/W R/W R/W R/W —4 R/W2 —4 0x0024 – 0x002C Reserved 0x002E – 0x002F Reserved Always read 0x0000. Only writable in special modes (test_mode = 1). 3 Write to these registers have no meaning or effect during input capture. MC9S12KG128 Data Sheet, Rev. 1.15 416 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 4 Write has no effect; return 0 on read 13.3.2 Register Descriptions This section consists of register descriptions in address order. Each description includes a standard register diagram with an associated figure number. Details of register bit and field function follow the register diagrams, in bit order. Register Name 0x0000 TIOS R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 6 5 4 3 2 1 Bit 0 IOS7 IOS6 IOS5 IOS4 IOS3 IOS2 IOS1 IOS0 0x0001 CFORC 0x0002 OC7M 0x0003 OC7D 0x0004 TCNTH 0x0005 TCNTL 0x0006 TSCR2 0x0007 TTOV 0x0008 TCTL1 0x0009 TCTL2 0x000A TCTL3 0x000B TCTL4 0 FOC7 OC7M7 0 FOC6 OC7M6 0 FOC5 OC7M5 0 FOC4 OC7M4 0 FOC3 OC7M3 0 FOC2 OC7M2 0 FOC1 OC7M1 0 FOC0 OC7M0 OC7D7 OC7D6 OC7D5 OC7D4 OC7D3 OC7D2 OC7D1 OC7D0 TCNT15 TCNT14 TCNT13 TCNT12 TCNT11 TCNT10 TCNT9 TCNT8 TCNT7 TCNT6 TCNT5 TCNT4 TCNT3 0 TCNT2 0 TCNT1 0 TCNT0 0 TEN TSWAI TSFRZ TFFCA TOV7 TOV6 TOV5 TOV4 TOV3 TOV2 TOV1 TOV0 OM7 OL7 OM6 OL6 OM5 OL5 OM4 OL4 OM3 OL3 OM2 OL2 OM1 OL1 OM0 OL0 EDG7B EDG7A EDG6B EDG6A EDG5B EDG5A EDG4B EDG4A EDG3B EDG3A EDG2B EDG2A EDG1B EDG1A EDG0B EDG0A = Unimplemented or Reserved Figure 13-5. TIM16B8C Register Summary MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 417 Chapter 13 Timer Module (TIM16B8CV1) Register Name 0x000C TIE 0x000D TSCR2 0x000E TFLG1 0x000F TFLG2 R W R W R W R W R 0x0010–0x001F TCxH–TCxL W R W 0x0020 PACTL 0x0021 PAFLG 0x0022 PACNTH 0x0023 PACNTL 0x0024–0x002F Reserved R W R W R W R W R W Bit 7 C7I 6 C6I 0 5 C5I 0 4 C4I 0 3 C3I 2 C2I 1 C1I Bit 0 C0I TOI TCRE PR2 PR1 PR0 C7F C6F 0 C5F 0 C4F 0 C3F 0 C2F 0 C1F 0 C0F 0 TOF Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 0 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 PAEN 0 PAMOD 0 PEDGE 0 CLK1 0 CLK0 0 PAOVI PAI 0 PAOVF PAIF PACNT15 PACNT14 PACNT13 PACNT12 PACNT11 PACNT10 PACNT9 PACNT8 PACNT7 PACNT6 PACNT5 PACNT4 PACNT3 PACNT2 PACNT1 PACNT0 = Unimplemented or Reserved Figure 13-5. TIM16B8C Register Summary (continued) 13.3.2.1 Timer Input Capture/Output Compare Select (TIOS) 7 6 5 4 3 2 1 0 R IOS7 W Reset 0 0 0 0 0 0 0 0 IOS6 IOS5 IOS4 IOS3 IOS2 IOS1 IOS0 Figure 13-6. Timer Input Capture/Output Compare Select (TIOS) MC9S12KG128 Data Sheet, Rev. 1.15 418 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) Read: Anytime Write: Anytime Table 13-2. TIOS Field Descriptions Field 7:0 IOS[7:0] Description 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. 13.3.2.2 Timer Compare Force Register (CFORC) 7 6 5 4 3 2 1 0 R W Reset 0 FOC7 0 0 FOC6 0 0 FOC5 0 0 FOC4 0 0 FOC3 0 0 FOC2 0 0 FOC1 0 0 FOC0 0 Figure 13-7. Timer Compare Force Register (CFORC) Read: Anytime but will always return 0x0000 (1 state is transient) Write: Anytime Table 13-3. CFORC Field Descriptions Field 7:0 FOC[7:0] Description Force Output Compare Action for Channel 7:0 — A write to this register with the corresponding data bit(s) set causes the action which is programmed for output compare “x” to occur immediately. The action taken is the same as if a successful comparison had just taken place with the TCx register except the interrupt flag does not get set. Note: A successful channel 7 output compare overrides any channel 6:0 compares. If forced output compare on any channel occurs at the same time as the successful output compare then forced output compare action will take precedence and interrupt flag won’t get set. 13.3.2.3 Output Compare 7 Mask Register (OC7M) 7 6 5 4 3 2 1 0 R OC7M7 W Reset 0 0 0 0 0 0 0 0 OC7M6 OC7M5 OC7M4 OC7M3 OC7M2 OC7M1 OC7M0 Figure 13-8. Output Compare 7 Mask Register (OC7M) Read: Anytime Write: Anytime MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 419 Chapter 13 Timer Module (TIM16B8CV1) Table 13-4. OC7M Field Descriptions Field 7:0 OC7M[7:0] Description Output Compare 7 Mask — Setting the OC7Mx (x ranges from 0 to 6) will set the corresponding port to be an output port when the corresponding TIOSx (x ranges from 0 to 6) bit is set to be an output compare. Note: A successful channel 7 output compare overrides any channel 6:0 compares. For each OC7M bit that is set, the output compare action reflects the corresponding OC7D bit. 13.3.2.4 Output Compare 7 Data Register (OC7D) 7 6 5 4 3 2 1 0 R OC7D7 W Reset 0 0 0 0 0 0 0 0 OC7D6 OC7D5 OC7D4 OC7D3 OC7D2 OC7D1 OC7D0 Figure 13-9. Output Compare 7 Data Register (OC7D) Read: Anytime Write: Anytime Table 13-5. OC7D Field Descriptions Field 7:0 OC7D[7:0] Description Output Compare 7 Data — A channel 7 output compare can cause bits in the output compare 7 data register to transfer to the timer port data register depending on the output compare 7 mask register. 13.3.2.5 Timer Count Register (TCNT) 15 14 13 12 11 10 9 9 R TCNT15 W Reset 0 0 0 0 0 0 0 0 TCNT14 TCNT13 TCNT12 TCNT11 TCNT10 TCNT9 TCNT8 Figure 13-10. Timer Count Register High (TCNTH) 7 6 5 4 3 2 1 0 R TCNT7 W Reset 0 0 0 0 0 0 0 0 TCNT6 TCNT5 TCNT4 TCNT3 TCNT2 TCNT1 TCNT0 Figure 13-11. Timer Count Register Low (TCNTL) The 16-bit main timer is an up counter. A full access for the counter register should take place in one clock cycle. A separate read/write for high byte and low byte will give a different result than accessing them as a word. MC9S12KG128 Data Sheet, Rev. 1.15 420 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) Read: Anytime Write: Has no meaning or effect in the normal mode; only writable in special modes (test_mode = 1). 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. 13.3.2.6 Timer System Control Register 1 (TSCR1) 7 6 5 4 3 2 1 0 R TEN W Reset 0 0 0 0 TSWAI TSFRZ TFFCA 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 13-12. Timer System Control Register 1 (TSCR2) Read: Anytime Write: Anytime Table 13-6. TSCR1 Field Descriptions Field 7 TEN Description Timer Enable 0 Disables the main timer, including the counter. Can be used for reducing power consumption. 1 Allows the timer to function normally. If for any reason the timer is not active, there is no ÷64 clock for the pulse accumulator because the ÷64 is generated by the timer prescaler. Timer Module Stops While in Wait 0 Allows the timer module to continue running during wait. 1 Disables the timer module when the MCU is in the wait mode. Timer interrupts cannot be used to get the MCU out of wait. TSWAI also affects pulse accumulator. Timer Stops While in Freeze Mode 0 Allows the timer counter to continue running while in freeze mode. 1 Disables the timer counter whenever the MCU is in freeze mode. This is useful for emulation. TSFRZ does not stop the pulse accumulator. Timer Fast Flag Clear All 0 Allows the timer flag clearing to function normally. 1 For TFLG1(0x000E), a read from an input capture or a write to the output compare channel (0x0010–0x001F) causes the corresponding channel flag, CnF, to be cleared. For TFLG2 (0x000F), any access to the TCNT register (0x0004, 0x0005) clears the TOF flag. Any access to the PACNT registers (0x0022, 0x0023) clears the PAOVF and PAIF flags in the PAFLG register (0x0021). 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. 6 TSWAI 5 TSFRZ 4 TFFCA MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 421 Chapter 13 Timer Module (TIM16B8CV1) 13.3.2.7 Timer Toggle On Overflow Register 1 (TTOV) 7 6 5 4 3 2 1 0 R TOV7 W Reset 0 0 0 0 0 0 0 0 TOV6 TOV5 TOV4 TOV3 TOV2 TOV1 TOV0 Figure 13-13. Timer Toggle On Overflow Register 1 (TTOV) Read: Anytime Write: Anytime Table 13-7. TTOV Field Descriptions Field 7:0 TOV[7:0] Description Toggle On Overflow Bits — TOVx toggles output compare pin on overflow. This feature only takes effect when in output compare mode. When set, it takes precedence over forced output compare but not channel 7 override events. 0 Toggle output compare pin on overflow feature disabled. 1 Toggle output compare pin on overflow feature enabled. 13.3.2.8 Timer Control Register 1/Timer Control Register 2 (TCTL1/TCTL2) 7 6 5 4 3 2 1 0 R OM7 W Reset 0 0 0 0 0 0 0 0 OL7 OM6 OL6 OM5 OL5 OM4 OL4 Figure 13-14. Timer Control Register 1 (TCTL1) 7 6 5 4 3 2 1 0 R OM3 W Reset 0 0 0 0 0 0 0 0 OL3 OM2 OL2 OM1 OL1 OM0 OL0 Figure 13-15. Timer Control Register 2 (TCTL2) Read: Anytime Write: Anytime MC9S12KG128 Data Sheet, Rev. 1.15 422 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) Table 13-8. TCTL1/TCTL2 Field Descriptions Field 7:0 OMx Description Output Mode — These eight pairs of control bits are encoded to specify the output action to be taken as a result of a successful OCx compare. When either OMx or OLx is 1, the pin associated with OCx becomes an output tied to OCx. Note: To enable output action by OMx bits on timer port, the corresponding bit in OC7M should be cleared. Output Level — These eight pairs of control bits are encoded to specify the output action to be taken as a result of a successful OCx compare. When either OMx or OLx is 1, the pin associated with OCx becomes an output tied to OCx. Note: To enable output action by OLx bits on timer port, the corresponding bit in OC7M should be cleared. 7:0 OLx Table 13-9. Compare Result Output Action OMx 0 0 1 1 OLx 0 1 0 1 Action Timer disconnected from output pin logic Toggle OCx output line Clear OCx output line to zero Set OCx output line to one To operate the 16-bit pulse accumulator independently of input capture or output compare 7 and 0 respectively the user must set the corresponding bits IOSx = 1, OMx = 0 and OLx = 0. OC7M7 in the OC7M register must also be cleared. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 423 Chapter 13 Timer Module (TIM16B8CV1) 13.3.2.9 Timer Control Register 3/Timer Control Register 4 (TCTL3 and TCTL4) 7 6 5 4 3 2 1 0 R EDG7B W Reset 0 0 0 0 0 0 0 0 EDG7A EDG6B EDG6A EDG5B EDG5A EDG4B EDG4A Figure 13-16. Timer Control Register 3 (TCTL3) 7 6 5 4 3 2 1 0 R EDG3B W Reset 0 0 0 0 0 0 0 0 EDG3A EDG2B EDG2A EDG1B EDG1A EDG0B EDG0A Figure 13-17. Timer Control Register 4 (TCTL4) Read: Anytime Write: Anytime. Table 13-10. TCTL3/TCTL4 Field Descriptions Field 7:0 EDGnB EDGnA Description Input Capture Edge Control — These eight pairs of control bits configure the input capture edge detector circuits. Table 13-11. Edge Detector Circuit Configuration EDGnB 0 0 1 1 EDGnA 0 1 0 1 Configuration Capture disabled Capture on rising edges only Capture on falling edges only Capture on any edge (rising or falling) MC9S12KG128 Data Sheet, Rev. 1.15 424 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 13.3.2.10 Timer Interrupt Enable Register (TIE) 7 6 5 4 3 2 1 0 R C7I W Reset 0 0 0 0 0 0 0 0 C6I C5I C4I C3I C2I C1I C0I Figure 13-18. Timer Interrupt Enable Register (TIE) Read: Anytime Write: Anytime. Table 13-12. TIE Field Descriptions Field 7:0 C7I:C0I Description Input Capture/Output Compare “x” Interrupt Enable — The bits in TIE correspond bit-for-bit with the bits in the TFLG1 status register. If cleared, the corresponding flag is disabled from causing a hardware interrupt. If set, the corresponding flag is enabled to cause a interrupt. 13.3.2.11 Timer System Control Register 2 (TSCR2) 7 6 5 4 3 2 1 0 R TOI W Reset 0 0 0 0 TCRE PR2 0 PR1 0 PR0 0 0 0 0 0 = Unimplemented or Reserved Figure 13-19. Timer System Control Register 2 (TSCR2) Read: Anytime Write: Anytime. Table 13-13. TSCR2 Field Descriptions Field 7 TOI 3 TCRE Description Timer Overflow Interrupt Enable 0 Interrupt inhibited. 1 Hardware interrupt requested when TOF flag set. 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 = 0x0000 and TCRE = 1, TCNT will stay at 0x0000 continuously. If TC7 = 0xFFFF and TCRE = 1, TOF will never be set when TCNT is reset from 0xFFFF to 0x0000. Timer Prescaler Select — These three bits select the frequency of the timer prescaler clock derived from the Bus Clock as shown in Table 13-14. 2 PR[2:0] MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 425 Chapter 13 Timer Module (TIM16B8CV1) Table 13-14. Timer Clock Selection PR2 0 0 0 0 1 1 1 1 PR1 0 0 1 1 0 0 1 1 PR0 0 1 0 1 0 1 0 1 Timer Clock Bus Clock / 1 Bus Clock / 2 Bus Clock / 4 Bus Clock / 8 Bus Clock / 16 Bus Clock / 32 Bus Clock / 64 Bus Clock / 128 NOTE The newly selected prescale factor will not take effect until the next synchronized edge where all prescale counter stages equal zero. 13.3.2.12 Main Timer Interrupt Flag 1 (TFLG1) 7 6 5 4 3 2 1 0 R C7F W Reset 0 0 0 0 0 0 0 0 C6F C5F C4F C3F C2F C1F C0F Figure 13-20. Main Timer Interrupt Flag 1 (TFLG1) Read: Anytime Write: Used in the clearing mechanism (set bits cause corresponding bits to be cleared). Writing a zero will not affect current status of the bit. Table 13-15. TRLG1 Field Descriptions Field 7:0 C[7:0]F Description Input Capture/Output Compare Channel “x” Flag — These flags are set when an input capture or output compare event occurs. Clear a channel flag by writing one to it. When TFFCA bit in TSCR register is set, a read from an input capture or a write into an output compare channel (0x0010–0x001F) will cause the corresponding channel flag CxF to be cleared. MC9S12KG128 Data Sheet, Rev. 1.15 426 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 13.3.2.13 Main Timer Interrupt Flag 2 (TFLG2) 7 6 5 4 3 2 1 0 R TOF W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Unimplemented or Reserved Figure 13-21. Main Timer Interrupt Flag 2 (TFLG2) TFLG2 indicates when interrupt conditions have occurred. To clear a bit in the flag register, write the bit to one. 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. Table 13-16. TRLG2 Field Descriptions Field 7 TOF Description Timer Overflow Flag — Set when 16-bit free-running timer overflows from 0xFFFF to 0x0000. This bit is cleared automatically by a write to the TFLG2 register with bit 7 set. (See also TCRE control bit explanation.) 13.3.2.14 Timer Input Capture/Output Compare Registers High and Low 0–7 (TCxH and TCxL) 15 14 13 12 11 10 9 0 R Bit 15 W Reset 0 0 0 0 0 0 0 0 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Figure 13-22. Timer Input Capture/Output Compare Register x High (TCxH) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Figure 13-23. Timer Input Capture/Output Compare Register x Low (TCxL) 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 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 427 Chapter 13 Timer Module (TIM16B8CV1) Write: Anytime for output compare function.Writes to these registers have no meaning or effect during input capture. All timer input capture/output compare registers are reset to 0x0000. NOTE Read/Write access in byte mode for high byte should takes place before low byte otherwise it will give a different result. 13.3.2.15 16-Bit Pulse Accumulator Control Register (PACTL) 7 6 5 4 3 2 1 0 R W Reset 0 PAEN 0 0 PAMOD 0 PEDGE 0 CLK1 0 CLK0 0 PAOVI 0 PAI 0 Unimplemented or Reserved Figure 13-24. 16-Bit Pulse Accumulator Control Register (PACTL) When PAEN is set, the PACT is enabled.The PACT shares the input pin with IOC7. Read: Any time Write: Any time Table 13-17. PACTL Field Descriptions Field 6 PAEN Description Pulse Accumulator System Enable — PAEN is independent from TEN. With timer disabled, the pulse accumulator can function unless pulse accumulator is disabled. 0 16-Bit Pulse Accumulator system disabled. 1 Pulse Accumulator system enabled. Pulse Accumulator Mode — This bit is active only when the Pulse Accumulator is enabled (PAEN = 1). See Table 13-18. 0 Event counter mode. 1 Gated time accumulation mode. Pulse Accumulator Edge Control — This bit is active only when the Pulse Accumulator is enabled (PAEN = 1). For PAMOD bit = 0 (event counter mode). See Table 13-18. 0 Falling edges on IOC7 pin cause the count to be incremented. 1 Rising edges on IOC7 pin cause the count to be incremented. For PAMOD bit = 1 (gated time accumulation mode). 0 IOC7 input pin high enables M (bus clock) divided by 64 clock to Pulse Accumulator and the trailing falling edge on IOC7 sets the PAIF flag. 1 IOC7 input pin low enables M (bus clock) divided by 64 clock to Pulse Accumulator and the trailing rising edge on IOC7 sets the PAIF flag. Clock Select Bits — Refer to Table 13-19. 5 PAMOD 4 PEDGE 3:2 CLK[1:0] MC9S12KG128 Data Sheet, Rev. 1.15 428 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) Table 13-17. PACTL Field Descriptions (continued) Field 1 PAOVI 0 PAI Pulse Accumulator Overflow Interrupt Enable 0 Interrupt inhibited. 1 Interrupt requested if PAOVF is set. Pulse Accumulator Input Interrupt Enable 0 Interrupt inhibited. 1 Interrupt requested if PAIF is set. Description Table 13-18. Pin Action PAMOD 0 0 1 1 PEDGE 0 1 0 1 Pin Action Falling edge Rising edge Div. by 64 clock enabled with pin high level Div. by 64 clock enabled with pin low level NOTE If the timer is not active (TEN = 0 in TSCR), there is no divide-by-64 because the ÷64 clock is generated by the timer prescaler. Table 13-19. Timer Clock Selection CLK1 0 0 1 1 CLK0 0 1 0 1 Timer Clock 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 For the description of PACLK please refer Figure 13-24. 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. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 429 Chapter 13 Timer Module (TIM16B8CV1) 13.3.2.16 Pulse Accumulator Flag Register (PAFLG) 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 PAOVF PAIF 0 0 0 0 0 0 0 0 Unimplemented or Reserved Figure 13-25. Pulse Accumulator Flag Register (PAFLG) Read: Anytime Write: Anytime When the TFFCA bit in the TSCR register is set, any access to the PACNT register will clear all the flags in the PAFLG register. Table 13-20. PAFLG Field Descriptions Field 1 PAOVF 0 PAIF Description Pulse Accumulator Overflow Flag — Set when the 16-bit pulse accumulator overflows from 0xFFFF to 0x0000. This bit is cleared automatically by a write to the PAFLG register with bit 1 set. Pulse Accumulator Input edge Flag — Set when the selected edge is detected at the IOC7 input pin.In event mode the event edge triggers PAIF and in gated time accumulation mode the trailing edge of the gate signal at the IOC7 input pin triggers PAIF. This bit is cleared by a write to the PAFLG register with bit 0 set. Any access to the PACNT register will clear all the flags in this register when TFFCA bit in register TSCR(0x0006) is set. MC9S12KG128 Data Sheet, Rev. 1.15 430 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 13.3.2.17 Pulse Accumulators Count Registers (PACNT) 15 14 13 12 11 10 9 0 R PACNT15 W Reset 0 0 0 0 0 0 0 0 PACNT14 PACNT13 PACNT12 PACNT11 PACNT10 PACNT9 PACNT8 Figure 13-26. Pulse Accumulator Count Register High (PACNTH) 7 6 5 4 3 2 1 0 R PACNT7 W Reset 0 0 0 0 0 0 0 0 PACNT6 PACNT5 PACNT4 PACNT3 PACNT2 PACNT1 PACNT0 Figure 13-27. Pulse Accumulator Count Register Low (PACNTL) Read: Anytime Write: Anytime These registers contain the number of active input edges on its input pin since the last reset. When PACNT overflows from 0xFFFF to 0x0000, the Interrupt flag PAOVF in PAFLG (0x0021) is set. Full count register access should take place in one clock cycle. A separate read/write for high byte and low byte will give a different result than accessing them as a word. NOTE Reading the pulse accumulator counter registers immediately after an active edge on the pulse accumulator input pin may miss the last count because the input has to be synchronized with the bus clock first. 13.4 Functional Description This section provides a complete functional description of the timer TIM16B8C block. Please refer to the detailed timer block diagram in Figure 13-28 as necessary. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 431 Chapter 13 Timer Module (TIM16B8CV1) Bus Clock CLK[1:0] PR[2:1:0] PACLK PACLK/256 PACLK/65536 channel 7 output compare MUX TCRE CxI CxF PRESCALER TCNT(hi):TCNT(lo) CLEAR COUNTER 16-BIT COUNTER TE CHANNEL 0 16-BIT COMPARATOR TC0 EDG0A EDG0B EDGE DETECT C0F OM:OL0 TOV0 TOF TOI INTERRUPT LOGIC TOF C0F CH. 0 CAPTURE IOC0 PIN LOGIC CH. 0COMPARE IOC0 PIN IOC0 C1F OM:OL1 TOV1 CH. 1 CAPTURE IOC1 PIN LOGIC CH. 1 COMPARE IOC1 PIN CHANNEL 1 16-BIT COMPARATOR TC1 EDG1A EDG1B EDGE DETECT C1F CHANNEL2 IOC1 CHANNEL7 16-BIT COMPARATOR TC7 EDG7A EDG7B EDGE DETECT C7F OM:O73 TOV7 C7F CH.7 CAPTURE IOC7 PIN PA INPUT LOGIC CH. 7 COMPARE IOC7 PIN IOC7 PAOVF PACNT(hi):PACNT(lo) PEDGE PAE EDGE DETECT PACLK/65536 PACLK/256 INTERRUPT REQUEST PAOVI PAOVF 16-BIT COUNTER PACLK PAMOD INTERRUPT LOGIC DIVIDE-BY-64 PAI PAIF PAIF Bus Clock PAOVF PAOVI Figure 13-28. Detailed Timer Block Diagram 13.4.1 Prescaler The prescaler divides the bus clock by 1,2,4,8,16,32,64 or 128. The prescaler select bits, PR[2:0], select the prescaler divisor. PR[2:0] are in timer system control register 2 (TSCR2). MC9S12KG128 Data Sheet, Rev. 1.15 432 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) 13.4.2 Input Capture Clearing the I/O (input/output) select bit, IOSx, configures channel x as an input capture channel. The input capture function captures the time at which an external event occurs. When an active edge occurs on the pin of an input capture channel, the timer transfers the value in the timer counter into the timer channel registers, TCx. The minimum pulse width for the input capture input is greater than two bus clocks. An input capture on channel x sets the CxF flag. The CxI bit enables the CxF flag to generate interrupt requests. 13.4.3 Output Compare Setting the I/O select bit, IOSx, configures channel x as an output compare channel. The output compare function can generate a periodic pulse with a programmable polarity, duration, and frequency. When the timer counter reaches the value in the channel registers of an output compare channel, the timer can set, clear, or toggle the channel pin. An output compare on channel x sets the CxF flag. The CxI bit enables the CxF flag to generate interrupt requests. The output mode and level bits, OMx and OLx, select set, clear, toggle on output compare. Clearing both OMx and OLx disconnects the pin from the output logic. Setting a force output compare bit, FOCx, causes an output compare on channel x. A forced output compare does not set the channel flag. A successful output compare on channel 7 overrides output compares on all other output compare channels. The output compare 7 mask register masks the bits in the output compare 7 data register. The timer counter reset enable bit, TCRE, enables channel 7 output compares to reset the timer counter. A channel 7 output compare can reset the timer counter even if the IOC7 pin is being used as the pulse accumulator input. Writing to the timer port bit of an output compare pin does not affect the pin state. The value written is stored in an internal latch. When the pin becomes available for general-purpose output, the last value written to the bit appears at the pin. 13.4.4 Pulse Accumulator The pulse accumulator (PACNT) is a 16-bit counter that can operate in two modes: Event counter mode — Counting edges of selected polarity on the pulse accumulator input pin, PAI. Gated time accumulation mode — Counting pulses from a divide-by-64 clock. The PAMOD bit selects the mode of operation. The minimum pulse width for the PAI input is greater than two bus clocks. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 433 Chapter 13 Timer Module (TIM16B8CV1) 13.4.5 Event Counter Mode Clearing the PAMOD bit configures the PACNT for event counter operation. An active edge on the IOC7 pin increments the pulse accumulator counter. The PEDGE bit selects falling edges or rising edges to increment the count. NOTE The PACNT input and timer channel 7 use the same pin IOC7. To use the IOC7, disconnect it from the output logic by clearing the channel 7 output mode and output level bits, OM7 and OL7. Also clear the channel 7 output compare 7 mask bit, OC7M7. The Pulse Accumulator counter register reflect the number of active input edges on the PACNT input pin since the last reset. The PAOVF bit is set when the accumulator rolls over from 0xFFFF to 0x0000. The pulse accumulator overflow interrupt enable bit, PAOVI, enables the PAOVF flag to generate interrupt requests. NOTE The pulse accumulator counter can operate in event counter mode even when the timer enable bit, TEN, is clear. 13.4.6 Gated Time Accumulation Mode Setting the PAMOD bit configures the pulse accumulator for gated time accumulation operation. An active level on the PACNT input pin enables a divided-by-64 clock to drive the pulse accumulator. The PEDGE bit selects low levels or high levels to enable the divided-by-64 clock. The trailing edge of the active level at the IOC7 pin sets the PAIF. The PAI bit enables the PAIF flag to generate interrupt requests. The pulse accumulator counter register reflect the number of pulses from the divided-by-64 clock since the last reset. NOTE The timer prescaler generates the divided-by-64 clock. If the timer is not active, there is no divided-by-64 clock. 13.5 Resets The reset state of each individual bit is listed within Section 13.3, “Memory Map and Register Definition” which details the registers and their bit fields. 13.6 Interrupts This section describes interrupts originated by the TIM16B8C block. Table 13-21 lists the interrupts generated by the TIM16B8C to communicate with the MCU. MC9S12KG128 Data Sheet, Rev. 1.15 434 Freescale Semiconductor Chapter 13 Timer Module (TIM16B8CV1) Table 13-21. TIM16B8CV1 Interrupts Interrupt C[7:0]F PAOVI PAOVF TOF 1 Offset1 — — — — Vector1 — — — — Priority1 — — — — Source Timer Channel 7–0 Pulse Accumulator Input Pulse Accumulator Overflow Timer Overflow Description Active high timer channel interrupts 7–0 Active high pulse accumulator input interrupt Pulse accumulator overflow interrupt Timer Overflow interrupt Chip Dependent. The TIM16B8C uses a total of 11 interrupt vectors. The interrupt vector offsets and interrupt numbers are chip dependent. 13.6.1 Channel [7:0] Interrupt (C[7:0]F) This active high outputs will be asserted by the module to request a timer channel 7 – 0 interrupt to be serviced by the system controller. 13.6.2 Pulse Accumulator Input Interrupt (PAOVI) This active high output will be asserted by the module to request a timer pulse accumulator input interrupt to be serviced by the system controller. 13.6.3 Pulse Accumulator Overflow Interrupt (PAOVF) This active high output will be asserted by the module to request a timer pulse accumulator overflow interrupt to be serviced by the system controller. 13.6.4 Timer Overflow Interrupt (TOF) This active high output will be asserted by the module to request a timer overflow interrupt to be serviced by the system controller. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 435 Chapter 13 Timer Module (TIM16B8CV1) MC9S12KG128 Data Sheet, Rev. 1.15 436 Freescale Semiconductor Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.1 Introduction The VREG3V3 is a dual output voltage regulator providing two separate 2.5 V (typical) supplies differing in the amount of current that can be sourced. The regulator input voltage range is from 3.3 V up to 5 V (typical). 14.1.1 Features The block VREG3V3 includes these distinctive features: • Two parallel, linear voltage regulators — Bandgap reference • Low-voltage detect (LVD) with low-voltage interrupt (LVI) • Power-on reset (POR) • Low-voltage reset (LVR) 14.1.2 Modes of Operation There are three modes VREG3V3 can operate in: • Full-performance mode (FPM) (MCU is not in stop mode) The regulator is active, providing the nominal supply voltage of 2.5 V with full current sourcing capability at both outputs. Features LVD (low-voltage detect), LVR (low-voltage reset), and POR (power-on reset) are available. • Reduced-power mode (RPM) (MCU is in stop mode) The purpose is to reduce power consumption of the device. The output voltage may degrade to a lower value than in full-performance mode, additionally the current sourcing capability is substantially reduced. Only the POR is available in this mode, LVD and LVR are disabled. • Shutdown mode Controlled by VREGEN (see device overview chapter for connectivity of VREGEN). This mode is characterized by minimum power consumption. The regulator outputs are in a high impedance state, only the POR feature is available, LVD and LVR are disabled. This mode must be used to disable the chip internal regulator VREG3V3, i.e., to bypass the VREG3V3 to use external supplies. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 437 Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.1.3 Block Diagram Figure 14-1 shows the function principle of VREG3V3 by means of a block diagram. The regulator core REG consists of two parallel sub-blocks, REG1 and REG2, providing two independent output voltages. REG2 VDDR VDDA REG VDDPLL VSSPLL REG1 VDD LVD LVR LVR POR POR VSSA VSS VREGEN CTRL LVI REG: Regulator Core LVD: Low Voltage Detect CTRL: Regulator Control LVR: Low Voltage Reset POR: Power-on Reset PIN Figure 14-1. VREG3V3 Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 438 Freescale Semiconductor Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.2 External Signal Description Due to the nature of VREG3V3 being a voltage regulator providing the chip internal power supply voltages most signals are power supply signals connected to pads. Table 14-1 shows all signals of VREG3V3 associated with pins. Table 14-1. VREG3V3 — Signal Properties Name VDDR VDDA VSSA VDD VSS VDDPLL VSSPLL VREGEN (optional) Port — — — — — — — — Function VREG3V3 power input (positive supply) VREG3V3 quiet input (positive supply) VREG3V3 quiet input (ground) VREG3V3 primary output (positive supply) VREG3V3 primary output (ground) VREG3V3 secondary output (positive supply) VREG3V3 secondary output (ground) VREG3V3 (Optional) Regulator Enable Reset State — — — — — — — — Pull Up — — — — — — — — NOTE Check device overview chapter for connectivity of the signals. 14.2.1 VDDR — Regulator Power Input Signal VDDR is the power input of VREG3V3. All currents sourced into the regulator loads flow through this pin. A chip external decoupling capacitor (100 nF...220 nF, X7R ceramic) between VDDR and VSSR can smoothen ripple on VDDR. For entering Shutdown Mode, pin VDDR should also be tied to ground on devices without a VREGEN pin. 14.2.2 VDDA, VSSA — Regulator Reference Supply Signals VDDA/VSSA which are supposed to be relatively quiet are used to supply the analog parts of the regulator. Internal precision reference circuits are supplied from these signals. A chip external decoupling capacitor (100 nF...220 nF, X7R ceramic) between VDDA and VSSA can further improve the quality of this supply. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 439 Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.2.3 VDD, VSS — Regulator Output1 (Core Logic) Signals VDD/VSS are the primary outputs of VREG3V3 that provide the power supply for the core logic. These signals are connected to device pins to allow external decoupling capacitors (100 nF...220 nF, X7R ceramic). In Shutdown Mode an external supply at VDD/VSS can replace the voltage regulator. 14.2.4 VDDPLL, VSSPLL — Regulator Output2 (PLL) Signals VDDPLL/VSSPLL are the secondary outputs of VREG3V3 that provide the power supply for the PLL and oscillator. These signals are connected to device pins to allow external decoupling capacitors (100 nF...220 nF, X7R ceramic). In Shutdown Mode an external supply at VDDPLL/VSSPLL can replace the voltage regulator. 14.2.5 VREGEN — Optional Regulator Enable This optional signal is used to shutdown VREG3V3. In that case VDD/VSS and VDDPLL/VSSPLL must be provided externally. Shutdown Mode is entered with VREGEN being low. If VREGEN is high, the VREG3V3 is either in Full Performance Mode or in Reduced Power Mode. For the connectivity of VREGEN see device overview chapter. NOTE Switching from FPM or RPM to shutdown of VREG3V3 and vice versa is not supported while the MCU is powered. 14.3 Memory Map and Register Definition This subsection provides a detailed description of all registers accessible in VREG3V3. 14.3.1 Module Memory Map Figure 14-2 provides an overview of all used registers. Table 14-2. VREG3V3 Memory Map Address Offset 0x0000 Use VREG3V3 Control Register (VREGCTRL) Access R/W MC9S12KG128 Data Sheet, Rev. 1.15 440 Freescale Semiconductor Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.3.2 Register Descriptions The following paragraphs describe, in address order, all the VREG3V3 registers and their individual bits. 14.3.2.1 VREG3V3 — Control Register (VREGCTRL) The VREGCTRL register allows to separately enable features of VREG3V3. 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 LVDS LVIE LVIF 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 14-2. VREG3V3 — Control Register (VREGCTRL) Table 14-3. MCCTL1 Field Descriptions Field 2 LVDS 1 LVIE 0 LVIF Description Low-Voltage Detect Status Bit — This read-only status bit reflects the input voltage. Writes have no effect. 0 Input voltage VDDA is above level VLVID or RPM or shutdown mode. 1 Input voltage VDDA is below level VLVIA and FPM. Low-Voltage Interrupt Enable Bit 0 Interrupt request is disabled. 1 Interrupt will be requested whenever LVIF is set. Low-Voltage Interrupt Flag — LVIF is set to 1 when LVDS status bit changes. This flag can only be cleared by writing a 1. Writing a 0 has no effect. If enabled (LVIE = 1), LVIF causes an interrupt request. 0 No change in LVDS bit. 1 LVDS bit has changed. NOTE On entering the Reduced Power Mode the LVIF is not cleared by the VREG3V3. 14.4 Functional Description Block VREG3V3 is a voltage regulator as depicted in Figure 14-1. The regulator functional elements are the regulator core (REG), a low-voltage detect module (LVD), a power-on reset module (POR) and a low-voltage reset module (LVR). There is also the regulator control block (CTRL) which represents the interface to the digital core logic but also manages the operating modes of VREG3V3. 14.4.1 REG — Regulator Core VREG3V3, respectively its regulator core has two parallel, independent regulation loops (REG1 and REG2) that differ only in the amount of current that can be sourced to the connected loads. Therefore, only REG1 providing the supply at VDD/VSS is explained. The principle is also valid for REG2. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 441 Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) The regulator is a linear series regulator with a bandgap reference in its Full Performance Mode and a voltage clamp in Reduced Power Mode. All load currents flow from input VDDR to VSS or VSSPLL, the reference circuits are connected to VDDA and VSSA. 14.4.2 Full-Performance Mode In Full Performance Mode, a fraction of the output voltage (VDD) and the bandgap reference voltage are fed to an operational amplifier. The amplified input voltage difference controls the gate of an output driver which basically is a large NMOS transistor connected to the output. 14.4.3 Reduced-Power Mode In Reduced Power Mode, the driver gate is connected to a buffered fraction of the input voltage (VDDR). The operational amplifier and the bandgap are disabled to reduce power consumption. 14.4.4 LVD — Low-Voltage Detect sub-block LVD is responsible for generating the low-voltage interrupt (LVI). LVD monitors the input voltage (VDDA–VSSA) and continuously updates the status flag LVDS. Interrupt flag LVIF is set whenever status flag LVDS changes its value. The LVD is available in FPM and is inactive in Reduced Power Mode and Shutdown Mode. 14.4.5 POR — Power-On Reset This functional block monitors output VDD. If VDD is below VPORD, signal POR is high, if it exceeds VPORD, the signal goes low. The transition to low forces the CPU in the power-on sequence. Due to its role during chip power-up this module must be active in all operating modes of VREG3V3. 14.4.6 LVR — Low-Voltage Reset Block LVR monitors the primary output voltage VDD. If it drops below the assertion level (VLVRA) signal LVR asserts and when rising above the deassertion level (VLVRD) signal LVR negates again. The LVR function is available only in Full Performance Mode. 14.4.7 CTRL — Regulator Control This part contains the register block of VREG3V3 and further digital functionality needed to control the operating modes. CTRL also represents the interface to the digital core logic. MC9S12KG128 Data Sheet, Rev. 1.15 442 Freescale Semiconductor Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) 14.5 Resets This subsection describes how VREG3V3 controls the reset of the MCU.The reset values of registers and signals are provided in Section 14.3, “Memory Map and Register Definition”. Possible reset sources are listed in Table 14-4. Table 14-4. VREG3V3 — Reset Sources Reset Source Power-on reset Low-voltage reset Always active Available only in Full Performance Mode Local Enable 14.5.1 Power-On Reset During chip power-up the digital core may not work if its supply voltage VDD is below the POR deassertion level (VPORD). Therefore, signal POR which forces the other blocks of the device into reset is kept high until VDD exceeds VPORD. Then POR becomes low and the reset generator of the device continues the start-up sequence. The power-on reset is active in all operation modes of VREG3V3. 14.5.2 Low-Voltage Reset For details on low-voltage reset see Section 14.4.6, “LVR — Low-Voltage Reset”. 14.6 Interrupts This subsection describes all interrupts originated by VREG3V3. The interrupt vectors requested by VREG3V3 are listed in Table 14-5. Vector addresses and interrupt priorities are defined at MCU level. Table 14-5. VREG3V3 — Interrupt Vectors Interrupt Source Low Voltage Interrupt (LVI) Local Enable LVIE = 1; Available only in Full Performance Mode 14.6.1 LVI — Low-Voltage Interrupt In FPM VREG3V3 monitors the input voltage VDDA. Whenever VDDA drops below level VLVIA the status bit LVDS is set to 1. Vice versa, LVDS is reset to 0 when VDDA rises above level VLVID. An interrupt, indicated by flag LVIF = 1, is triggered by any change of the status bit LVDS if interrupt enable bit LVIE = 1. NOTE On entering the Reduced Power Mode, the LVIF is not cleared by the VREG3V3. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 443 Chapter 14 Dual Output Voltage Regulator (VREG3V3V2) MC9S12KG128 Data Sheet, Rev. 1.15 444 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) 15.1 Introduction This section describes the functionality of the background debug module (BDM) sub-block of the HCS12 core platform. A block diagram of the BDM is shown in Figure 15-1. HOST SYSTEM BKGD 16-BIT SHIFT REGISTER ADDRESS ENTAG BDMACT TRACE INSTRUCTION DECODE AND EXECUTION BUS INTERFACE AND CONTROL LOGIC DATA CLOCKS SDV ENBDM STANDARD BDM FIRMWARE LOOKUP TABLE CLKSW Figure 15-1. BDM Block Diagram The background debug module (BDM) sub-block is a single-wire, background debug system implemented in on-chip hardware for minimal CPU intervention. All interfacing with the BDM is done via the BKGD pin. BDMV4 has enhanced capability for maintaining synchronization between the target and host while allowing more flexibility in clock rates. This includes a sync signal to show the clock rate and a handshake signal to indicate when an operation is complete. The system is backwards compatible with older external interfaces. 15.1.1 • • • • • • Features Single-wire communication with host development system BDMV4 (and BDM2): Enhanced capability for allowing more flexibility in clock rates BDMV4: SYNC command to determine communication rate BDMV4: GO_UNTIL command BDMV4: Hardware handshake protocol to increase the performance of the serial communication Active out of reset in special single-chip mode MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 445 Chapter 15 Background Debug Module (BDMV4) • • • • • • • Nine hardware commands using free cycles, if available, for minimal CPU intervention Hardware commands not requiring active BDM 15 firmware commands execute from the standard BDM firmware lookup table Instruction tagging capability Software control of BDM operation during wait mode Software selectable clocks When secured, hardware commands are allowed to access the register space in special single-chip mode, if the FLASH and EEPROM erase tests fail. 15.1.2 Modes of Operation BDM is available in all operating modes but must be enabled before firmware commands are executed. Some system peripherals may have a control bit which allows suspending the peripheral function during background debug mode. 15.1.2.1 Regular Run Modes All of these operations refer to the part in run mode. The BDM does not provide controls to conserve power during run mode. • Normal operation General operation of the BDM is available and operates the same in all normal modes. • Special single-chip mode In special single-chip mode, background operation is enabled and active out of reset. This allows programming a system with blank memory. • Special peripheral mode BDM is enabled and active immediately out of reset. BDM can be disabled by clearing the BDMACT bit in the BDM status (BDMSTS) register. The BDM serial system should not be used in special peripheral mode. • Emulation modes General operation of the BDM is available and operates the same as in normal modes. 15.1.2.2 Secure Mode Operation If the part is in secure mode, the operation of the BDM is reduced to a small subset of its regular run mode operation. Secure operation prevents access to FLASH or EEPROM other than allowing erasure. 15.2 External Signal Description A single-wire interface pin is used to communicate with the BDM system. Two additional pins are used for instruction tagging. These pins are part of the multiplexed external bus interface (MEBI) sub-block and all interfacing between the MEBI and BDM is done within the core interface boundary. Functional descriptions of the pins are provided below for completeness. MC9S12KG128 Data Sheet, Rev. 1.15 446 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) • • • • • BKGD — Background interface pin TAGHI — High byte instruction tagging pin TAGLO — Low byte instruction tagging pin BKGD and TAGHI share the same pin. TAGLO and LSTRB share the same pin. NOTE Generally these pins are shared as described, but it is best to check the device overview chapter to make certain. All MCUs at the time of this writing have followed this pin sharing scheme. 15.2.1 BKGD — Background Interface Pin Debugging control logic communicates with external devices serially via the single-wire background interface pin (BKGD). During reset, this pin is a mode select input which selects between normal and special modes of operation. After reset, this pin becomes the dedicated serial interface pin for the background debug mode. 15.2.2 TAGHI — High Byte Instruction Tagging Pin This pin is used to tag the high byte of an instruction. When instruction tagging is on, a logic 0 at the falling edge of the external clock (ECLK) tags the high half of the instruction word being read into the instruction queue. 15.2.3 TAGLO — Low Byte Instruction Tagging Pin This pin is used to tag the low byte of an instruction. When instruction tagging is on and low strobe is enabled, a logic 0 at the falling edge of the external clock (ECLK) tags the low half of the instruction word being read into the instruction queue. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 447 Chapter 15 Background Debug Module (BDMV4) 15.3 Memory Map and Register Definition A summary of the registers associated with the BDM is shown in Figure 15-2. Registers are accessed by host-driven communications to the BDM hardware using READ_BD and WRITE_BD commands. Detailed descriptions of the registers and associated bits are given in the subsections that follow. 15.3.1 Module Memory Map Table 15-1. INT Memory Map Register Address Reserved BDM Status Register (BDMSTS) Reserved BDM CCR Holding Register (BDMCCR) 7 8– BDM Internal Register Position (BDMINR) Reserved Use Access — R/W — R/W R — MC9S12KG128 Data Sheet, Rev. 1.15 448 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) 15.3.2 Register Name Reserved Register Descriptions Bit 7 R W R W R W R W R W R W R W R W R W R W R W R W X 6 X 5 X 4 X 3 X 2 X 1 0 Bit 0 0 BDMSTS ENBDM X BDMACT ENTAG X SDV TRACE CLKSW X UNSEC 0 Reserved X X X X X Reserved X X X X X X X X Reserved X X X X X X X X Reserved X X X X X X X X BDMCCR CCR7 0 CCR6 REG14 CCR5 REG13 CCR4 REG12 CCR3 REG11 CCR2 0 CCR1 0 CCR0 0 BDMINR Reserved 0 0 0 0 0 0 0 0 Reserved 0 0 0 0 0 0 0 0 Reserved X X X X X X X X Reserved X X X X X X X X = Unimplemented, Reserved X = Indeterminate 0 = Implemented (do not alter) = Always read zero Figure 15-2. BDM Register Summary MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 449 Chapter 15 Background Debug Module (BDMV4) 15.3.2.1 BDM Status Register (BDMSTS) 7 6 5 4 3 2 1 0 R ENBDM W Reset: Special single-chip mode: Special peripheral mode: All other modes: 11 0 0 0 BDMACT ENTAG SDV TRACE CLKSW UNSEC 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 02 0 0 0 0 0 0 0 = Unimplemented or Reserved = Implemented (do not alter) Figure 15-3. BDM Status Register (BDMSTS) Note: 1 ENBDM is read as "1" by a debugging environment in Special single-chip mode when the device is not secured or secured but fully erased (Flash and EEPROM).This is because the ENBDM bit is set by the standard firmware before a BDM command can be fully transmitted and executed. UNSEC is read as "1" by a debugging environment in Special single-chip mode when the device is secured and fully erased, else it is "0" and can only be read if not secure (see also bit description). 2 Read: All modes through BDM operation Write: All modes but subject to the following: • BDMACT can only be set by BDM hardware upon entry into BDM. It can only be cleared by the standard BDM firmware lookup table upon exit from BDM active mode. • CLKSW can only be written via BDM hardware or standard BDM firmware write commands. • All other bits, while writable via BDM hardware or standard BDM firmware write commands, should only be altered by the BDM hardware or standard firmware lookup table as part of BDM command execution. • ENBDM should only be set via a BDM hardware command if the BDM firmware commands are needed. (This does not apply in special single-chip mode). Table 15-2. BDMSTS Field Descriptions Field 7 ENBDM Description Enable BDM — This bit controls whether the BDM is enabled or disabled. When enabled, BDM can be made active to allow firmware commands to be executed. When disabled, BDM cannot be made active but BDM hardware commands are allowed. 0 BDM disabled 1 BDM enabled Note: ENBDM is set by the firmware immediately out of reset in special single-chip mode. In secure mode, this bit will not be set by the firmware until after the EEPROM and FLASH erase verify tests are complete. BDM Active Status — This bit becomes set upon entering BDM. The standard BDM firmware lookup table is then enabled and put into the memory map. BDMACT is cleared by a carefully timed store instruction in the standard BDM firmware as part of the exit sequence to return to user code and remove the BDM memory from the map. 0 BDM not active 1 BDM active 6 BDMACT MC9S12KG128 Data Sheet, Rev. 1.15 450 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) Table 15-2. BDMSTS Field Descriptions (continued) Field 5 ENTAG Description Tagging Enable — This bit indicates whether instruction tagging in enabled or disabled. It is set when the TAGGO command is executed and cleared when BDM is entered. The serial system is disabled and the tag function enabled 16 cycles after this bit is written. BDM cannot process serial commands while tagging is active. 0 Tagging not enabled or BDM active 1 Tagging enabled Shift Data Valid — This bit is set and cleared by the BDM hardware. It is set after data has been transmitted as part of a firmware read command or after data has been received as part of a firmware write command. It is cleared when the next BDM command has been received or BDM is exited. SDV is used by the standard BDM firmware to control program flow execution. 0 Data phase of command not complete 1 Data phase of command is complete TRACE1 BDM Firmware Command is Being Executed — This bit gets set when a BDM TRACE1 firmware command is first recognized. It will stay set as long as continuous back-to-back TRACE1 commands are executed. This bit will get cleared when the next command that is not a TRACE1 command is recognized. 0 TRACE1 command is not being executed 1 TRACE1 command is being executed Clock Switch — The CLKSW bit controls which clock the BDM operates with. It is only writable from a hardware BDM command. A 150 cycle delay at the clock speed that is active during the data portion of the command will occur before the new clock source is guaranteed to be active. The start of the next BDM command uses the new clock for timing subsequent BDM communications. Table 15-3 shows the resulting BDM clock source based on the CLKSW and the PLLSEL (Pll select from the clock and reset generator) bits. Note: The BDM alternate clock source can only be selected when CLKSW = 0 and PLLSEL = 1. The BDM serial interface is now fully synchronized to the alternate clock source, when enabled. This eliminates frequency restriction on the alternate clock which was required on previous versions. Refer to the device overview section to determine which clock connects to the alternate clock source input. Note: If the acknowledge function is turned on, changing the CLKSW bit will cause the ACK to be at the new rate for the write command which changes it. Unsecure — This bit is only writable in special single-chip mode from the BDM secure firmware and always gets reset to zero. It is in a zero state as secure mode is entered so that the secure BDM firmware lookup table is enabled and put into the memory map along with the standard BDM firmware lookup table. The secure BDM firmware lookup table verifies that the on-chip EEPROM and FLASH EEPROM are erased. This being the case, the UNSEC bit is set and the BDM program jumps to the start of the standard BDM firmware lookup table and the secure BDM firmware lookup table is turned off. If the erase test fails, the UNSEC bit will not be asserted. 0 System is in a secured mode 1 System is in a unsecured mode Note: When UNSEC is set, security is off and the user can change the state of the secure bits in the on-chip FLASH EEPROM. Note that if the user does not change the state of the bits to “unsecured” mode, the system will be secured again when it is next taken out of reset. 4 SDV 3 TRACE 2 CLKSW 1 UNSEC Table 15-3. BDM Clock Sources PLLSEL 0 0 CLKSW 0 1 Bus clock Bus clock BDMCLK MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 451 Chapter 15 Background Debug Module (BDMV4) Table 15-3. BDM Clock Sources PLLSEL 1 1 CLKSW 0 1 BDMCLK Alternate clock (refer to the device overview chapter to determine the alternate clock source) Bus clock dependent on the PLL MC9S12KG128 Data Sheet, Rev. 1.15 452 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) 15.3.2.2 BDM CCR Holding Register (BDMCCR) 7 6 5 4 3 2 1 0 R CCR7 W Reset 0 0 0 0 0 0 0 0 CCR6 CCR5 CCR4 CCR3 CCR2 CCR1 CCR0 Figure 15-4. BDM CCR Holding Register (BDMCCR) Read: All modes Write: All modes NOTE When BDM is made active, the CPU stores the value of the CCR register in the BDMCCR register. However, out of special single-chip reset, the BDMCCR is set to 0xD8 and not 0xD0 which is the reset value of the CCR register. When entering background debug mode, the BDM CCR holding register is used to save the contents of the condition code register of the user’s program. It is also used for temporary storage in the standard BDM firmware mode. The BDM CCR holding register can be written to modify the CCR value. 15.3.2.3 BDM Internal Register Position Register (BDMINR) 7 6 5 4 3 2 1 0 R W Reset 0 REG14 REG13 REG12 REG11 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 15-5. BDM Internal Register Position (BDMINR) Read: All modes Write: Never Table 15-4. BDMINR Field Descriptions Field Description 6:3 Internal Register Map Position — These four bits show the state of the upper five bits of the base address for REG[14:11] the system’s relocatable register block. BDMINR is a shadow of the INITRG register which maps the register block to any 2K byte space within the first 32K bytes of the 64K byte address space. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 453 Chapter 15 Background Debug Module (BDMV4) 15.4 Functional Description The BDM receives and executes commands from a host via a single wire serial interface. There are two types of BDM commands, namely, hardware commands and firmware commands. Hardware commands are used to read and write target system memory locations and to enter active background debug mode, see Section 15.4.3, “BDM Hardware Commands.” Target system memory includes all memory that is accessible by the CPU. Firmware commands are used to read and write CPU resources and to exit from active background debug mode, see Section 15.4.4, “Standard BDM Firmware Commands.” The CPU resources referred to are the accumulator (D), X index register (X), Y index register (Y), stack pointer (SP), and program counter (PC). Hardware commands can be executed at any time and in any mode excluding a few exceptions as highlighted, see Section 15.4.3, “BDM Hardware Commands.” Firmware commands can only be executed when the system is in active background debug mode (BDM). 15.4.1 Security If the user resets into special single-chip mode with the system secured, a secured mode BDM firmware lookup table is brought into the map overlapping a portion of the standard BDM firmware lookup table. The secure BDM firmware verifies that the on-chip EEPROM and FLASH EEPROM are erased. This being the case, the UNSEC bit will get set. The BDM program jumps to the start of the standard BDM firmware and the secured mode BDM firmware is turned off and all BDM commands are allowed. If the EEPROM or FLASH do not verify as erased, the BDM firmware sets the ENBDM bit, without asserting UNSEC, and the firmware enters a loop. This causes the BDM hardware commands to become enabled, but does not enable the firmware commands. This allows the BDM hardware to be used to erase the EEPROM and FLASH. After execution of the secure firmware, regardless of the results of the erase tests, the CPU registers, INITEE and PPAGE, will no longer be in their reset state. 15.4.2 Enabling and Activating BDM The system must be in active BDM to execute standard BDM firmware commands. BDM can be activated only after being enabled. BDM is enabled by setting the ENBDM bit in the BDM status (BDMSTS) register. The ENBDM bit is set by writing to the BDM status (BDMSTS) register, via the single-wire interface, using a hardware command such as WRITE_BD_BYTE. After being enabled, BDM is activated by one of the following1: • Hardware BACKGROUND command • BDM external instruction tagging mechanism • CPU BGND instruction • Breakpoint sub-block’s force or tag mechanism2 When BDM is activated, the CPU finishes executing the current instruction and then begins executing the firmware in the standard BDM firmware lookup table. When BDM is activated by the breakpoint 1. BDM is enabled and active immediately out of special single-chip reset. 2. This method is only available on systems that have a a breakpoint or a debug sub-block. MC9S12KG128 Data Sheet, Rev. 1.15 454 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) sub-block, the type of breakpoint used determines if BDM becomes active before or after execution of the next instruction. NOTE If an attempt is made to activate BDM before being enabled, the CPU resumes normal instruction execution after a brief delay. If BDM is not enabled, any hardware BACKGROUND commands issued are ignored by the BDM and the CPU is not delayed. In active BDM, the BDM registers and standard BDM firmware lookup table are mapped to addresses 0xFF00 to 0xFFFF. BDM registers are mapped to addresses 0xFF00 to 0xFF07. The BDM uses these registers which are readable anytime by the BDM. However, these registers are not readable by user programs. 15.4.3 BDM Hardware Commands Hardware commands are used to read and write target system memory locations and to enter active background debug mode. Target system memory includes all memory that is accessible by the CPU such as on-chip RAM, EEPROM, FLASH EEPROM, I/O and control registers, and all external memory. Hardware commands are executed with minimal or no CPU intervention and do not require the system to be in active BDM for execution, although they can continue to be executed in this mode. When executing a hardware command, the BDM sub-block waits for a free CPU bus cycle so that the background access does not disturb the running application program. If a free cycle is not found within 128 clock cycles, the CPU is momentarily frozen so that the BDM can steal a cycle. When the BDM finds a free cycle, the operation does not intrude on normal CPU operation provided that it can be completed in a single cycle. However, if an operation requires multiple cycles the CPU is frozen until the operation is complete, even though the BDM found a free cycle. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 455 Chapter 15 Background Debug Module (BDMV4) The BDM hardware commands are listed in Table 15-5. Table 15-5. Hardware Commands Command BACKGROUND ACK_ENABLE ACK_DISABLE READ_BD_BYTE READ_BD_WORD READ_BYTE READ_WORD WRITE_BD_BYTE WRITE_BD_WORD WRITE_BYTE WRITE_WORD Opcode (hex) 90 D5 D6 E4 EC E0 E8 C4 CC C0 C8 Data None None None 16-bit address 16-bit data out 16-bit address 16-bit data out 16-bit address 16-bit data out 16-bit address 16-bit data out 16-bit address 16-bit data in 16-bit address 16-bit data in 16-bit address 16-bit data in 16-bit address 16-bit data in Description Enter background mode if firmware is enabled. If enabled, an ACK will be issued when the part enters active background mode. Enable handshake. Issues an ACK pulse after the command is executed. Disable handshake. This command does not issue an ACK pulse. Read from memory with standard BDM firmware lookup table in map. Odd address data on low byte; even address data on high byte. Read from memory with standard BDM firmware lookup table in map. Must be aligned access. Read from memory with standard BDM firmware lookup table out of map. Odd address data on low byte; even address data on high byte. Read from memory with standard BDM firmware lookup table out of map. Must be aligned access. Write to memory with standard BDM firmware lookup table in map. Odd address data on low byte; even address data on high byte. Write to memory with standard BDM firmware lookup table in map. Must be aligned access. Write to memory with standard BDM firmware lookup table out of map. Odd address data on low byte; even address data on high byte. Write to memory with standard BDM firmware lookup table out of map. Must be aligned access. NOTE: If enabled, ACK will occur when data is ready for transmission for all BDM READ commands and will occur after the write is complete for all BDM WRITE commands. The READ_BD and WRITE_BD commands allow access to the BDM register locations. These locations are not normally in the system memory map but share addresses with the application in memory. To distinguish between physical memory locations that share the same address, BDM memory resources are enabled just for the READ_BD and WRITE_BD access cycle. This allows the BDM to access BDM locations unobtrusively, even if the addresses conflict with the application memory map. 15.4.4 Standard BDM Firmware Commands Firmware commands are used to access and manipulate CPU resources. The system must be in active BDM to execute standard BDM firmware commands, see Section 15.4.2, “Enabling and Activating BDM.” Normal instruction execution is suspended while the CPU executes the firmware located in the standard BDM firmware lookup table. The hardware command BACKGROUND is the usual way to activate BDM. As the system enters active BDM, the standard BDM firmware lookup table and BDM registers become visible in the on-chip memory map at 0xFF00–0xFFFF, and the CPU begins executing the standard BDM MC9S12KG128 Data Sheet, Rev. 1.15 456 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) firmware. The standard BDM firmware watches for serial commands and executes them as they are received. The firmware commands are shown in Table 15-6. Table 15-6. Firmware Commands Command1 READ_NEXT READ_PC READ_D READ_X READ_Y READ_SP WRITE_NEXT WRITE_PC WRITE_D WRITE_X WRITE_Y WRITE_SP GO GO_UNTIL2 TRACE1 TAGGO 1 Opcode (hex) 62 63 64 65 66 67 42 43 44 45 46 47 08 0C 10 18 Data 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 None None None Description Increment X by 2 (X = X + 2), then read word X points to. Read program counter. Read D accumulator. Read X index register. Read Y index register. Read stack pointer. Increment X by 2 (X = X + 2), then write word to location 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. If enabled, ACK will occur when leaving active background mode. Go to user program. If enabled, ACK will occur upon returning to active background mode. Execute one user instruction then return to active BDM. If enabled, ACK will occur upon returning to active background mode. Enable tagging and go to user program. There is no ACK pulse related to this command. If enabled, ACK will occur when data is ready for transmission for all BDM READ commands and will occur after the write is complete for all BDM WRITE commands. 2 Both WAIT (with clocks to the S12 CPU core disabled) and STOP disable the ACK function. The GO_UNTIL command will not get an Acknowledge if one of these two CPU instructions occurs before the “UNTIL” instruction. This can be a problem for any instruction that uses ACK, but GO_UNTIL is a lot more difficult for the development tool to time-out. 15.4.5 BDM Command Structure Hardware and firmware BDM commands start with an 8-bit opcode followed by a 16-bit address and/or a 16-bit data word depending on the command. All the read commands return 16 bits of data despite the byte or word implication in the command name. NOTE 8-bit reads return 16-bits of data, of which, only one byte will contain valid data. If reading an even address, the valid data will appear in the MSB. If reading an odd address, the valid data will appear in the LSB. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 457 Chapter 15 Background Debug Module (BDMV4) NOTE 16-bit misaligned reads and writes are not allowed. If attempted, the BDM will ignore the least significant bit of the address and will assume an even address from the remaining bits. For hardware data read commands, the external host must wait 150 bus clock cycles after sending the address before attempting to obtain the read data. This is to be certain that valid data is available in the BDM shift register, ready to be shifted out. For hardware write commands, the external host must wait 150 bus clock cycles after sending the data to be written before attempting to send a new command. This is to avoid disturbing the BDM shift register before the write has been completed. The 150 bus clock cycle delay in both cases includes the maximum 128 cycle delay that can be incurred as the BDM waits for a free cycle before stealing a cycle. For firmware read commands, the external host should wait 44 bus clock cycles after sending the command opcode and before attempting to obtain the read data. This includes the potential of an extra 7 cycles when the access is external with a narrow bus access (+1 cycle) and / or a stretch (+1, 2, or 3 cycles), (7 cycles could be needed if both occur). The 44 cycle wait allows enough time for the requested data to be made available in the BDM shift register, ready to be shifted out. NOTE This timing has increased from previous BDM modules due to the new capability in which the BDM serial interface can potentially run faster than the bus. On previous BDM modules this extra time could be hidden within the serial time. For firmware write commands, the external host must wait 32 bus clock cycles after sending the data to be written before attempting to send a new command. This is to avoid disturbing the BDM shift register before the write has been completed. The external host should wait 64 bus clock cycles after a TRACE1 or GO command before starting any new serial command. This is to allow the CPU to exit gracefully from the standard BDM firmware lookup table and resume execution of the user code. Disturbing the BDM shift register prematurely may adversely affect the exit from the standard BDM firmware lookup table. NOTE If the bus rate of the target processor is unknown or could be changing, it is recommended that the ACK (acknowledge function) be used to indicate when an operation is complete. When using ACK, the delay times are automated. Figure 15-6 represents the BDM command structure. The command blocks illustrate a series of eight bit times starting with a falling edge. The bar across the top of the blocks indicates that the BKGD line idles in the high state. The time for an 8-bit command is 8 × 16 target clock cycles.1 1. Target clock cycles are cycles measured using the target MCU’s serial clock rate. See Section 15.4.6, “BDM Serial Interface,” and Section 15.3.2.1, “BDM Status Register (BDMSTS),” for information on how serial clock rate is selected. MC9S12KG128 Data Sheet, Rev. 1.15 458 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) 8 BITS AT ∼16 TC/BIT HARDWARE READ COMMAND 16 BITS AT ∼16 TC/BIT ADDRESS 150-BC DELAY 16 BITS AT ∼16 TC/BIT DATA 150-BC DELAY NEXT COMMAND HARDWARE WRITE COMMAND 44-BC DELAY ADDRESS DATA NEXT COMMAND FIRMWARE READ COMMAND DATA 32-BC DELAY NEXT COMMAND FIRMWARE WRITE COMMAND 64-BC DELAY DATA NEXT COMMAND GO, TRACE COMMAND NEXT COMMAND BC = BUS CLOCK CYCLES TC = TARGET CLOCK CYCLES Figure 15-6. BDM Command Structure 15.4.6 BDM Serial Interface The BDM communicates with external devices serially via the BKGD pin. During reset, this pin is a mode select input which selects between normal and special modes of operation. After reset, this pin becomes the dedicated serial interface pin for the BDM. The BDM serial interface is timed using the clock selected by the CLKSW bit in the status register see Section 15.3.2.1, “BDM Status Register (BDMSTS).” This clock will be referred to as the target clock in the following explanation. The BDM serial interface uses a clocking scheme in which the external host generates a falling edge on the BKGD pin to indicate the start of each bit time. This falling edge is sent for every bit whether data is transmitted or received. Data is transferred most significant bit (MSB) first at 16 target clock cycles per bit. The interface times out if 512 clock cycles occur between falling edges from the host. The BKGD pin is a pseudo open-drain pin and has an weak on-chip active pull-up that is enabled at all times. It is assumed that there is an external pull-up and that drivers connected to BKGD do not typically drive the high level. Because R-C rise time could be unacceptably long, the target system and host provide brief driven-high (speedup) pulses to drive BKGD to a logic 1. The source of this speedup pulse is the host for transmit cases and the target for receive cases. The timing for host-to-target is shown in Figure 15-7 and that of target-to-host in Figure 15-8 and Figure 15-9. All four cases begin when the host drives the BKGD pin low to generate a falling edge. Because the host and target are operating from separate clocks, it can take the target system up to one full clock cycle to recognize this edge. The target measures delays from this perceived start of the bit time while the host measures delays from the point it actually drove BKGD low to start the bit up to one target MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 459 Chapter 15 Background Debug Module (BDMV4) clock cycle earlier. Synchronization between the host and target is established in this manner at the start of every bit time. Figure 15-7 shows an external host transmitting a logic 1 and transmitting a logic 0 to the BKGD pin of a target system. The host is asynchronous to the target, so there is up to a one clock-cycle delay from the host-generated falling edge to where the target recognizes this edge as the beginning of the bit time. Ten target clock cycles later, the target senses the bit level on the BKGD pin. Internal glitch detect logic requires the pin be driven high no later that eight target clock cycles after the falling edge for a logic 1 transmission. Because the host drives the high speedup pulses in these two cases, the rising edges look like digitally driven signals. CLOCK TARGET SYSTEM HOST TRANSMIT 1 HOST TRANSMIT 0 PERCEIVED START OF BIT TIME 10 CYCLES SYNCHRONIZATION UNCERTAINTY TARGET SENSES BIT EARLIEST START OF NEXT BIT Figure 15-7. BDM Host-to-Target Serial Bit Timing The receive cases are more complicated. Figure 15-8 shows the host receiving a logic 1 from the target system. Because the host is asynchronous to the target, there is up to one clock-cycle delay from the host-generated falling edge on BKGD to the perceived start of the bit time in the target. The host holds the BKGD pin low long enough for the target to recognize it (at least two target clock cycles). The host must release the low drive before the target drives a brief high speedup pulse seven target clock cycles after the perceived start of the bit time. The host should sample the bit level about 10 target clock cycles after it started the bit time. MC9S12KG128 Data Sheet, Rev. 1.15 460 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) CLOCK TARGET SYSTEM HOST DRIVE TO BKGD PIN TARGET SYSTEM SPEEDUP PULSE PERCEIVED START OF BIT TIME R-C RISE BKGD PIN HIGH-IMPEDANCE HIGH-IMPEDANCE HIGH-IMPEDANCE 10 CYCLES 10 CYCLES EARLIEST START OF NEXT BIT HOST SAMPLES BKGD PIN Figure 15-8. BDM Target-to-Host Serial Bit Timing (Logic 1) Figure 15-9 shows the host receiving a logic 0 from the target. Because the host is asynchronous to the target, there is up to a one clock-cycle delay from the host-generated falling edge on BKGD to the start of the bit time as perceived by the target. The host initiates the bit time but the target finishes it. Because the target wants the host to receive a logic 0, it drives the BKGD pin low for 13 target clock cycles then briefly drives it high to speed up the rising edge. The host samples the bit level about 10 target clock cycles after starting the bit time. CLOCK TARGET SYS. HOST DRIVE TO BKGD PIN TARGET SYS. DRIVE AND SPEEDUP PULSE PERCEIVED START OF BIT TIME BKGD PIN HIGH-IMPEDANCE SPEEDUP PULSE 10 CYCLES 10 CYCLES EARLIEST START OF NEXT BIT HOST SAMPLES BKGD PIN Figure 15-9. BDM Target-to-Host Serial Bit Timing (Logic 0) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 461 Chapter 15 Background Debug Module (BDMV4) 15.4.7 Serial Interface Hardware Handshake Protocol BDM commands that require CPU execution are ultimately treated at the MCU bus rate. Because the BDM clock source can be asynchronously related to the bus frequency, when CLKSW = 0, it is very helpful to provide a handshake protocol in which the host could determine when an issued command is executed by the CPU. The alternative is to always wait the amount of time equal to the appropriate number of cycles at the slowest possible rate the clock could be running. This sub-section will describe the hardware handshake protocol. The hardware handshake protocol signals to the host controller when an issued command was successfully executed by the target. This protocol is implemented by a 16 serial clock cycle low pulse followed by a brief speedup pulse in the BKGD pin. This pulse is generated by the target MCU when a command, issued by the host, has been successfully executed (see Figure 15-10). This pulse is referred to as the ACK pulse. After the ACK pulse has finished: the host can start the bit retrieval if the last issued command was a read command, or start a new command if the last command was a write command or a control command (BACKGROUND, GO, GO_UNTIL, or TRACE1). The ACK pulse is not issued earlier than 32 serial clock cycles after the BDM command was issued. The end of the BDM command is assumed to be the 16th tick of the last bit. This minimum delay assures enough time for the host to perceive the ACK pulse. Note also that, there is no upper limit for the delay between the command and the related ACK pulse, because the command execution depends upon the CPU bus frequency, which in some cases could be very slow compared to the serial communication rate. This protocol allows a great flexibility for the POD designers, because it does not rely on any accurate time measurement or short response time to any event in the serial communication. BDM CLOCK (TARGET MCU) 16 CYCLES TARGET TRANSMITS ACK PULSE HIGH-IMPEDANCE 32 CYCLES SPEEDUP PULSE MINIMUM DELAY FROM THE BDM COMMAND BKGD PIN EARLIEST START OF NEXT BIT HIGH-IMPEDANCE 16th TICK OF THE LAST COMMAD BIT Figure 15-10. Target Acknowledge Pulse (ACK) NOTE If the ACK pulse was issued by the target, the host assumes the previous command was executed. If the CPU enters WAIT or STOP prior to executing a hardware command, the ACK pulse will not be issued meaning that the BDM command was not executed. After entering wait or stop mode, the BDM command is no longer pending. MC9S12KG128 Data Sheet, Rev. 1.15 462 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) Figure 15-11 shows the ACK handshake protocol in a command level timing diagram. The READ_BYTE instruction is used as an example. First, the 8-bit instruction opcode is sent by the host, followed by the address of the memory location to be read. The target BDM decodes the instruction. A bus cycle is grabbed (free or stolen) by the BDM and it executes the READ_BYTE operation. Having retrieved the data, the BDM issues an ACK pulse to the host controller, indicating that the addressed byte is ready to be retrieved. After detecting the ACK pulse, the host initiates the byte retrieval process. Note that data is sent in the form of a word and the host needs to determine which is the appropriate byte based on whether the address was odd or even. TARGET HOST NEW BDM COMMAND HOST BDM ISSUES THE ACK PULSE (OUT OF SCALE) BDM EXECUTES THE READ_BYTE COMMAND TARGET BKGD PIN READ_BYTE HOST BYTE ADDRESS TARGET (2) BYTES ARE RETRIEVED BDM DECODES THE COMMAND Figure 15-11. Handshake Protocol at Command Level Differently from the normal bit transfer (where the host initiates the transmission), the serial interface ACK handshake pulse is initiated by the target MCU by issuing a falling edge in the BKGD pin. The hardware handshake protocol in Figure 15-10 specifies the timing when the BKGD pin is being driven, so the host should follow this timing constraint in order to avoid the risk of an electrical conflict in the BKGD pin. NOTE The only place the BKGD pin can have an electrical conflict is when one side is driving low and the other side is issuing a speedup pulse (high). Other “highs” are pulled rather than driven. However, at low rates the time of the speedup pulse can become lengthy and so the potential conflict time becomes longer as well. The ACK handshake protocol does not support nested ACK pulses. If a BDM command is not acknowledge by an ACK pulse, the host needs to abort the pending command first in order to be able to issue a new BDM command. When the CPU enters WAIT or STOP while the host issues a command that requires CPU execution (e.g., WRITE_BYTE), the target discards the incoming command due to the WAIT or STOP being detected. Therefore, the command is not acknowledged by the target, which means that the ACK pulse will not be issued in this case. After a certain time the host should decide to abort the ACK sequence in order to be free to issue a new command. Therefore, the protocol should provide a mechanism in which a command, and therefore a pending ACK, could be aborted. NOTE Differently from a regular BDM command, the ACK pulse does not provide a time out. This means that in the case of a WAIT or STOP instruction being executed, the ACK would be prevented from being issued. If not aborted, the ACK would remain pending indefinitely. See the handshake abort procedure described in Section 15.4.8, “Hardware Handshake Abort Procedure.” MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 463 Chapter 15 Background Debug Module (BDMV4) 15.4.8 Hardware Handshake Abort Procedure The abort procedure is based on the SYNC command. In order to abort a command, which had not issued the corresponding ACK pulse, the host controller should generate a low pulse in the BKGD pin by driving it low for at least 128 serial clock cycles and then driving it high for one serial clock cycle, providing a speedup pulse. By detecting this long low pulse in the BKGD pin, the target executes the SYNC protocol, see Section 15.4.9, “SYNC — Request Timed Reference Pulse,” and assumes that the pending command and therefore the related ACK pulse, are being aborted. Therefore, after the SYNC protocol has been completed the host is free to issue new BDM commands. Although it is not recommended, the host could abort a pending BDM command by issuing a low pulse in the BKGD pin shorter than 128 serial clock cycles, which will not be interpreted as the SYNC command. The ACK is actually aborted when a falling edge is perceived by the target in the BKGD pin. The short abort pulse should have at least 4 clock cycles keeping the BKGD pin low, in order to allow the falling edge to be detected by the target. In this case, the target will not execute the SYNC protocol but the pending command will be aborted along with the ACK pulse. The potential problem with this abort procedure is when there is a conflict between the ACK pulse and the short abort pulse. In this case, the target may not perceive the abort pulse. The worst case is when the pending command is a read command (i.e., READ_BYTE). If the abort pulse is not perceived by the target the host will attempt to send a new command after the abort pulse was issued, while the target expects the host to retrieve the accessed memory byte. In this case, host and target will run out of synchronism. However, if the command to be aborted is not a read command the short abort pulse could be used. After a command is aborted the target assumes the next falling edge, after the abort pulse, is the first bit of a new BDM command. NOTE The details about the short abort pulse are being provided only as a reference for the reader to better understand the BDM internal behavior. It is not recommended that this procedure be used in a real application. Because the host knows the target serial clock frequency, the SYNC command (used to abort a command) does not need to consider the lower possible target frequency. In this case, the host could issue a SYNC very close to the 128 serial clock cycles length. Providing a small overhead on the pulse length in order to assure the SYNC pulse will not be misinterpreted by the target. See Section 15.4.9, “SYNC — Request Timed Reference Pulse.” Figure 15-12 shows a SYNC command being issued after a READ_BYTE, which aborts the READ_BYTE command. Note that, after the command is aborted a new command could be issued by the host computer. NOTE Figure 15-12 does not represent the signals in a true timing scale MC9S12KG128 Data Sheet, Rev. 1.15 464 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) READ_BYTE CMD IS ABORTED BY THE SYNC REQUEST (OUT OF SCALE) SYNC RESPONSE FROM THE TARGET (OUT OF SCALE) BKGD PIN READ_BYTE HOST MEMORY ADDRESS TARGET READ_STATUS HOST TARGET NEW BDM COMMAND HOST TARGET BDM DECODE AND STARTS TO EXECUTES THE READ_BYTE CMD NEW BDM COMMAND Figure 15-12. ACK Abort Procedure at the Command Level Figure 15-13 shows a conflict between the ACK pulse and the SYNC request pulse. This conflict could occur if a POD device is connected to the target BKGD pin and the target is already in debug active mode. Consider that the target CPU is executing a pending BDM command at the exact moment the POD is being connected to the BKGD pin. In this case, an ACK pulse is issued along with the SYNC command. In this case, there is an electrical conflict between the ACK speedup pulse and the SYNC pulse. Because this is not a probable situation, the protocol does not prevent this conflict from happening. AT LEAST 128 CYCLES BDM CLOCK (TARGET MCU) ACK PULSE TARGET MCU DRIVES TO BKGD PIN HOST DRIVES SYNC TO BKGD PIN HOST AND TARGET DRIVE TO BKGD PIN HOST SYNC REQUEST PULSE BKGD PIN HIGH-IMPEDANCE ELECTRICAL CONFLICT SPEEDUP PULSE 16 CYCLES Figure 15-13. ACK Pulse and SYNC Request Conflict NOTE This information is being provided so that the MCU integrator will be aware that such a conflict could eventually occur. The hardware handshake protocol is enabled by the ACK_ENABLE and disabled by the ACK_DISABLE BDM commands. This provides backwards compatibility with the existing POD devices which are not able to execute the hardware handshake protocol. It also allows for new POD devices, that support the hardware handshake protocol, to freely communicate with the target device. If desired, without the need for waiting for the ACK pulse. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 465 Chapter 15 Background Debug Module (BDMV4) The commands are described as follows: • ACK_ENABLE — enables the hardware handshake protocol. The target will issue the ACK pulse when a CPU command is executed by the CPU. The ACK_ENABLE command itself also has the ACK pulse as a response. • ACK_DISABLE — disables the ACK pulse protocol. In this case, the host needs to use the worst case delay time at the appropriate places in the protocol. The default state of the BDM after reset is hardware handshake protocol disabled. All the read commands will ACK (if enabled) when the data bus cycle has completed and the data is then ready for reading out by the BKGD serial pin. All the write commands will ACK (if enabled) after the data has been received by the BDM through the BKGD serial pin and when the data bus cycle is complete. See Section 15.4.3, “BDM Hardware Commands,” and Section 15.4.4, “Standard BDM Firmware Commands,” for more information on the BDM commands. The ACK_ENABLE sends an ACK pulse when the command has been completed. This feature could be used by the host to evaluate if the target supports the hardware handshake protocol. If an ACK pulse is issued in response to this command, the host knows that the target supports the hardware handshake protocol. If the target does not support the hardware handshake protocol the ACK pulse is not issued. In this case, the ACK_ENABLE command is ignored by the target because it is not recognized as a valid command. The BACKGROUND command will issue an ACK pulse when the CPU changes from normal to background mode. The ACK pulse related to this command could be aborted using the SYNC command. The GO command will issue an ACK pulse when the CPU exits from background mode. The ACK pulse related to this command could be aborted using the SYNC command. The GO_UNTIL command is equivalent to a GO command with exception that the ACK pulse, in this case, is issued when the CPU enters into background mode. This command is an alternative to the GO command and should be used when the host wants to trace if a breakpoint match occurs and causes the CPU to enter active background mode. Note that the ACK is issued whenever the CPU enters BDM, which could be caused by a breakpoint match or by a BGND instruction being executed. The ACK pulse related to this command could be aborted using the SYNC command. The TRACE1 command has the related ACK pulse issued when the CPU enters background active mode after one instruction of the application program is executed. The ACK pulse related to this command could be aborted using the SYNC command. The TAGGO command will not issue an ACK pulse because this would interfere with the tagging function shared on the same pin. MC9S12KG128 Data Sheet, Rev. 1.15 466 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) 15.4.9 SYNC — Request Timed Reference Pulse The SYNC command is unlike other BDM commands because the host does not necessarily know the correct communication speed to use for BDM communications until after it has analyzed the response to the SYNC command. To issue a SYNC command, the host should perform the following steps: 1. Drive the BKGD pin low for at least 128 cycles at the lowest possible BDM serial communication frequency (the lowest serial communication frequency is determined by the crystal oscillator or the clock chosen by CLKSW.) 2. Drive BKGD high for a brief speedup pulse to get a fast rise time (this speedup pulse is typically one cycle of the host clock.) 3. Remove all drive to the BKGD pin so it reverts to high impedance. 4. Listen to the BKGD pin for the sync response pulse. Upon detecting the SYNC request from the host, the target performs the following steps: 1. Discards any incomplete command received or bit retrieved. 2. Waits for BKGD to return to a logic 1. 3. Delays 16 cycles to allow the host to stop driving the high speedup pulse. 4. Drives BKGD low for 128 cycles at the current BDM serial communication frequency. 5. Drives a one-cycle high speedup pulse to force a fast rise time on BKGD. 6. Removes all drive to the BKGD pin so it reverts to high impedance. The host measures the low time of this 128 cycle SYNC response pulse and determines the correct speed for subsequent BDM communications. Typically, the host can determine the correct communication speed within a few percent of the actual target speed and the communication protocol can easily tolerate speed errors of several percent. As soon as the SYNC request is detected by the target, any partially received command or bit retrieved is discarded. This is referred to as a soft-reset, equivalent to a time-out in the serial communication. After the SYNC response, the target will consider the next falling edge (issued by the host) as the start of a new BDM command or the start of new SYNC request. Another use of the SYNC command pulse is to abort a pending ACK pulse. The behavior is exactly the same as in a regular SYNC command. Note that one of the possible causes for a command to not be acknowledged by the target is a host-target synchronization problem. In this case, the command may not have been understood by the target and so an ACK response pulse will not be issued. 15.4.10 Instruction Tracing When a TRACE1 command is issued to the BDM in active BDM, the CPU exits the standard BDM firmware and executes a single instruction in the user code. As soon as this has occurred, the CPU is forced to return to the standard BDM firmware and the BDM is active and ready to receive a new command. If the TRACE1 command is issued again, the next user instruction will be executed. This facilitates stepping or tracing through the user code one instruction at a time. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 467 Chapter 15 Background Debug Module (BDMV4) If an interrupt is pending when a TRACE1 command is issued, the interrupt stacking operation occurs but no user instruction is executed. Upon return to standard BDM firmware execution, the program counter points to the first instruction in the interrupt service routine. 15.4.11 Instruction Tagging The instruction queue and cycle-by-cycle CPU activity are reconstructible in real time or from trace history that is captured by a logic analyzer. However, the reconstructed queue cannot be used to stop the CPU at a specific instruction. This is because execution already has begun by the time an operation is visible outside the system. A separate instruction tagging mechanism is provided for this purpose. The tag follows program information as it advances through the instruction queue. When a tagged instruction reaches the head of the queue, the CPU enters active BDM rather than executing the instruction. NOTE Tagging is disabled when BDM becomes active and BDM serial commands are not processed while tagging is active. Executing the BDM TAGGO command configures two system pins for tagging. The TAGLO signal shares a pin with the LSTRB signal, and the TAGHI signal shares a pin with the BKGD signal. Table 15-7 shows the functions of the two tagging pins. The pins operate independently, that is the state of one pin does not affect the function of the other. The presence of logic level 0 on either pin at the fall of the external clock (ECLK) performs the indicated function. High tagging is allowed in all modes. Low tagging is allowed only when low strobe is enabled (LSTRB is allowed only in wide expanded modes and emulation expanded narrow mode). Table 15-7. Tag Pin Function TAGHI 1 1 0 0 TAGLO 1 0 1 0 Tag No tag Low byte High byte Both bytes 15.4.12 Serial Communication Time-Out The host initiates a host-to-target serial transmission by generating a falling edge on the BKGD pin. If BKGD is kept low for more than 128 target clock cycles, the target understands that a SYNC command was issued. In this case, the target will keep waiting for a rising edge on BKGD in order to answer the SYNC request pulse. If the rising edge is not detected, the target will keep waiting forever without any time-out limit. Consider now the case where the host returns BKGD to logic one before 128 cycles. This is interpreted as a valid bit transmission, and not as a SYNC request. The target will keep waiting for another falling edge marking the start of a new bit. If, however, a new falling edge is not detected by the target within 512 clock cycles since the last falling edge, a time-out occurs and the current command is discarded without affecting memory or the operating mode of the MCU. This is referred to as a soft-reset. MC9S12KG128 Data Sheet, Rev. 1.15 468 Freescale Semiconductor Chapter 15 Background Debug Module (BDMV4) If a read command is issued but the data is not retrieved within 512 serial clock cycles, a soft-reset will occur causing the command to be disregarded. The data is not available for retrieval after the time-out has occurred. This is the expected behavior if the handshake protocol is not enabled. However, consider the behavior where the BDC is running in a frequency much greater than the CPU frequency. In this case, the command could time out before the data is ready to be retrieved. In order to allow the data to be retrieved even with a large clock frequency mismatch (between BDC and CPU) when the hardware handshake protocol is enabled, the time out between a read command and the data retrieval is disabled. Therefore, the host could wait for more then 512 serial clock cycles and continue to be able to retrieve the data from an issued read command. However, as soon as the handshake pulse (ACK pulse) is issued, the time-out feature is re-activated, meaning that the target will time out after 512 clock cycles. Therefore, the host needs to retrieve the data within a 512 serial clock cycles time frame after the ACK pulse had been issued. After that period, the read command is discarded and the data is no longer available for retrieval. Any falling edge of the BKGD pin after the time-out period is considered to be a new command or a SYNC request. Note that whenever a partially issued command, or partially retrieved data, has occurred the time out in the serial communication is active. This means that if a time frame higher than 512 serial clock cycles is observed between two consecutive negative edges and the command being issued or data being retrieved is not complete, a soft-reset will occur causing the partially received command or data retrieved to be disregarded. The next falling edge of the BKGD pin, after a soft-reset has occurred, is considered by the target as the start of a new BDM command, or the start of a SYNC request pulse. 15.4.13 Operation in Wait Mode The BDM cannot be used in wait mode if the system disables the clocks to the BDM. There is a clearing mechanism associated with the WAIT instruction when the clocks to the BDM (CPU core platform) are disabled. As the clocks restart from wait mode, the BDM receives a soft reset (clearing any command in progress) and the ACK function will be disabled. This is a change from previous BDM modules. 15.4.14 Operation in Stop Mode The BDM is completely shutdown in stop mode. There is a clearing mechanism associated with the STOP instruction. STOP must be enabled and the part must go into stop mode for this to occur. As the clocks restart from stop mode, the BDM receives a soft reset (clearing any command in progress) and the ACK function will be disabled. This is a change from previous BDM modules. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 469 Chapter 15 Background Debug Module (BDMV4) MC9S12KG128 Data Sheet, Rev. 1.15 470 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.1 Introduction This section describes the functionality of the debug (DBG) sub-block of the HCS12 core platform. The DBG module is designed to be fully compatible with the existing BKP_HCS12_A module (BKP mode) and furthermore provides an on-chip trace buffer with flexible triggering capability (DBG mode). The DBG module provides for non-intrusive debug of application software. The DBG module is optimized for the HCS12 16-bit architecture. 16.1.1 Features The DBG module in BKP mode includes these distinctive features: • Full or dual breakpoint mode — Compare on address and data (full) — Compare on either of two addresses (dual) • BDM or SWI breakpoint — Enter BDM on breakpoint (BDM) — Execute SWI on breakpoint (SWI) • Tagged or forced breakpoint — Break just before a specific instruction will begin execution (TAG) — Break on the first instruction boundary after a match occurs (Force) • Single, range, or page address compares — Compare on address (single) — Compare on address 256 byte (range) — Compare on any 16K page (page) • At forced breakpoints compare address on read or write • High and/or low byte data compares • Comparator C can provide an additional tag or force breakpoint (enhancement for BKP mode) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 471 Chapter 16 Debug Module (DBGV1) The DBG in DBG mode includes these distinctive features: • Three comparators (A, B, and C) — Dual mode, comparators A and B used to compare addresses — Full mode, comparator A compares address and comparator B compares data — Can be used as trigger and/or breakpoint — Comparator C used in LOOP1 capture mode or as additional breakpoint • Four capture modes — Normal mode, change-of-flow information is captured based on trigger specification — Loop1 mode, comparator C is dynamically updated to prevent redundant change-of-flow storage. — Detail mode, address and data for all cycles except program fetch (P) and free (f) cycles are stored in trace buffer — Profile mode, last instruction address executed by CPU is returned when trace buffer address is read • Two types of breakpoint or debug triggers — Break just before a specific instruction will begin execution (tag) — Break on the first instruction boundary after a match occurs (force) • BDM or SWI breakpoint — Enter BDM on breakpoint (BDM) — Execute SWI on breakpoint (SWI) • Nine trigger modes for comparators A and B —A — A or B — A then B — A and B, where B is data (full mode) — A and not B, where B is data (full mode) — Event only B, store data — A then event only B, store data — Inside range, A ≤ address ≤ B — Outside range, address < Α or address > B • Comparator C provides an additional tag or force breakpoint when capture mode is not configured in LOOP1 mode. • Sixty-four word (16 bits wide) trace buffer for storing change-of-flow information, event only data and other bus information. — Source address of taken conditional branches (long, short, bit-conditional, and loop constructs) — Destination address of indexed JMP, JSR, and CALL instruction. — Destination address of RTI, RTS, and RTC instructions — Vector address of interrupts, except for SWI and BDM vectors MC9S12KG128 Data Sheet, Rev. 1.15 472 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) — — — — Data associated with event B trigger modes Detail report mode stores address and data for all cycles except program (P) and free (f) cycles Current instruction address when in profiling mode BGND is not considered a change-of-flow (cof) by the debugger 16.1.2 Modes of Operation There are two main modes of operation: breakpoint mode and debug mode. Each one is mutually exclusive of the other and selected via a software programmable control bit. In the breakpoint mode there are two sub-modes of operation: • Dual address mode, where a match on either of two addresses will cause the system to enter background debug mode (BDM) or initiate a software interrupt (SWI). • Full breakpoint mode, where a match on address and data will cause the system to enter background debug mode (BDM) or initiate a software interrupt (SWI). In debug mode, there are several sub-modes of operation. • Trigger modes There are many ways to create a logical trigger. The trigger can be used to capture bus information either starting from the trigger or ending at the trigger. Types of triggers (A and B are registers): — A only — A or B — A then B — Event only B (data capture) — A then event only B (data capture) — A and B, full mode — A and not B, full mode — Inside range — Outside range • Capture modes There are several capture modes. These determine which bus information is saved and which is ignored. — Normal: save change-of-flow program fetches — Loop1: save change-of-flow program fetches, ignoring duplicates — Detail: save all bus operations except program and free cycles — Profile: poll target from external device 16.1.3 Block Diagram Figure 16-1 is a block diagram of this module in breakpoint mode. Figure 16-2 is a block diagram of this module in debug mode. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 473 Chapter 16 Debug Module (DBGV1) CLOCKS AND CONTROL SIGNALS CONTROL BLOCK BREAKPOINT MODES AND GENERATION OF SWI, FORCE BDM, AND TAGS CONTROL SIGNALS RESULTS SIGNALS CONTROL BITS READ/WRITE CONTROL BKP CONTROL SIGNALS ...... ...... EXPANSION ADDRESS ADDRESS WRITE DATA READ DATA REGISTER BLOCK BKPCT0 BKPCT1 COMPARE BLOCK BKP READ DATA BUS WRITE DATA BUS BKP0X COMPARATOR EXPANSION ADDRESSES BKP0H COMPARATOR ADDRESS HIGH ADDRESS LOW BKP0L COMPARATOR EXPANSION ADDRESSES BKP1X COMPARATOR DATA HIGH BKP1H COMPARATOR DATA/ADDRESS HIGH MUX DATA/ADDRESS LOW MUX READ DATA HIGH COMPARATOR READ DATA LOW COMPARATOR ADDRESS HIGH DATA LOW ADDRESS LOW BKP1L COMPARATOR Figure 16-1. DBG Block Diagram in BKP Mode MC9S12KG128 Data Sheet, Rev. 1.15 474 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) DBG READ DATA BUS ADDRESS BUS CONTROL WRITE DATA BUS READ DATA BUS READ/WRITE DBG MODE ENABLE CHANGE-OF-FLOW INDICATORS MCU IN BDM DETAIL EVENT ONLY CPU PROGRAM COUNTER STORE POINTER INSTRUCTION LAST CYCLE REGISTER BUS CLOCK M U X 64 x 16 BIT WORD TRACE BUFFER PROFILE CAPTURE MODE TRACE BUFFER OR PROFILING DATA ADDRESS/DATA/CONTROL REGISTERS COMPARATOR A COMPARATOR B COMPARATOR C CONTROL MATCH_A MATCH_B MATCH_C LOOP1 TRACER BUFFER CONTROL LOGIC TAG FORCE M U X WRITE DATA BUS READ DATA BUS M U X M U X LAST INSTRUCTION ADDRESS PROFILE CAPTURE REGISTER READ/WRITE Figure 16-2. DBG Block Diagram in DBG Mode 16.2 External Signal Description The DBG sub-module relies on the external bus interface (generally the MEBI) when the DBG is matching on the external bus. The tag pins in Table 16-1 (part of the MEBI) may also be a part of the breakpoint operation. Table 16-1. External System Pins Associated with DBG and MEBI Pin Name BKGD/MODC/ TAGHI PE3/LSTRB/ TAGLO Pin Functions TAGHI TAGLO Description When instruction tagging is on, a 0 at the falling edge of E tags the high half of the instruction word being read into the instruction queue. In expanded wide mode or emulation narrow modes, when instruction tagging is on and low strobe is enabled, a 0 at the falling edge of E tags the low half of the instruction word being read into the instruction queue. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 475 Chapter 16 Debug Module (DBGV1) 16.3 Memory Map and Register Definition A summary of the registers associated with the DBG sub-block is shown in Figure 16-3. Detailed descriptions of the registers and bits are given in the subsections that follow. 16.3.1 Module Memory Map Table 16-2. DBG Memory Map Address Offset Debug Control Register (DBGC1) Debug Status and Control Register (DBGSC) Debug Trace Buffer Register High (DBGTBH) Debug Trace Buffer Register Low (DBGTBL) 4 5 6 8 9 A B Debug Count Register (DBGCNT) Debug Comparator C Extended Register (DBGCCX) Debug Comparator C Register High (DBGCCH) Debug Comparator C Register Low (DBGCCL) Debug Control Register 2 (DBGC2) / (BKPCT0) Debug Control Register 3 (DBGC3) / (BKPCT1) Debug Comparator A Extended Register (DBGCAX) / (/BKP0X) Debug Comparator A Register High (DBGCAH) / (BKP0H) Debug Comparator A Register Low (DBGCAL) / (BKP0L) Debug Comparator B Extended Register (DBGCBX) / (BKP1X) E F Debug Comparator B Register High (DBGCBH) / (BKP1H) Debug Comparator B Register Low (DBGCBL) / (BKP1L) Use Access R/W R/W R R R R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 16.3.2 Register Descriptions This section consists of the DBG register descriptions in address order. Most of the register bits can be written to in either BKP or DBG mode, although they may not have any effect in one of the modes. However, the only bits in the DBG module that can be written while the debugger is armed (ARM = 1) are DBGEN and ARM Name1 DBGC1 R W R W = Unimplemented or Reserved Bit 7 DBGEN AF 6 ARM BF 5 TRGSEL CF 4 BEGIN 0 3 DBGBRK 2 0 1 Bit 0 CAPMOD DBGSC TRG Figure 16-3. DBG Register Summary MC9S12KG128 Data Sheet, Rev. 1.15 476 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) Name1 DBGTBH R W R W R W R W R W R W R W R W R W R W R W R W R W R W Bit 7 Bit 15 6 Bit 14 5 Bit 13 4 Bit 12 3 Bit 11 2 Bit 10 1 Bit 9 Bit 0 Bit 8 DBGTBL Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 DBGCNT TBF 0 CNT DBGCCX(2) PAGSEL EXTCMP DBGCCH(2) Bit 15 14 13 12 11 10 9 Bit 8 DBGCCL(2) Bit 7 6 5 4 3 2 1 Bit 0 DBGC2 BKPCT0 DBGC3 BKPCT1 DBGCAX BKP0X DBGCAH BKP0H DBGCAL BKP0L DBGCBX BKP1X DBGCBH BKP1H DBGCBL BKP1L BKABEN FULL BDM TAGAB BKCEN TAGC RWCEN RWC BKAMBH BKAMBL BKBMBH BKBMBL RWAEN RWA RWBEN RWB PAGSEL EXTCMP Bit 15 14 13 12 11 10 9 Bit 8 Bit 7 6 5 4 3 2 1 Bit 0 PAGSEL EXTCMP Bit 15 14 13 12 11 10 9 Bit 8 Bit 7 6 5 4 3 2 1 Bit 0 = Unimplemented or Reserved Figure 16-3. DBG Register Summary (continued) 1 The DBG module is designed for backwards compatibility to existing BKP modules. Register and bit names have changed from the BKP module. This column shows the DBG register name, as well as the BKP register name for reference. 2 Comparator C can be used to enhance the BKP mode by providing a third breakpoint. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 477 Chapter 16 Debug Module (DBGV1) 16.3.2.1 Debug Control Register 1 (DBGC1) NOTE All bits are used in DBG mode only. 7 6 5 4 3 2 1 0 R DBGEN W Reset 0 0 0 0 0 ARM TRGSEL BEGIN DBGBRK 0 CAPMOD 0 0 0 = Unimplemented or Reserved Figure 16-4. Debug Control Register (DBGC1) NOTE This register cannot be written if BKP mode is enabled (BKABEN in DBGC2 is set). Table 16-3. DBGC1 Field Descriptions Field 7 DBGEN Description DBG Mode Enable Bit — The DBGEN bit enables the DBG module for use in DBG mode. This bit cannot be set if the MCU is in secure mode. 0 DBG mode disabled 1 DBG mode enabled Arm Bit — The ARM bit controls whether the debugger is comparing and storing data in the trace buffer. See Section 16.4.2.4, “Arming the DBG Module,” for more information. 0 Debugger unarmed 1 Debugger armed Note: This bit cannot be set if the DBGEN bit is not also being set at the same time. For example, a write of 01 to DBGEN[7:6] will be interpreted as a write of 00. Trigger Selection Bit — The TRGSEL bit controls the triggering condition for comparators A and B in DBG mode. It serves essentially the same function as the TAGAB bit in the DBGC2 register does in BKP mode. See Section 16.4.2.1.2, “Trigger Selection,” for more information. TRGSEL may also determine the type of breakpoint based on comparator A and B if enabled in DBG mode (DBGBRK = 1). Please refer to Section 16.4.3.1, “Breakpoint Based on Comparator A and B.” 0 Trigger on any compare address match 1 Trigger before opcode at compare address gets executed (tagged-type) Begin/End Trigger Bit — The BEGIN bit controls whether the trigger begins or ends storing of data in the trace buffer. See Section 16.4.2.8.1, “Storing with Begin-Trigger,” and Section 16.4.2.8.2, “Storing with End-Trigger,” for more details. 0 Trigger at end of stored data 1 Trigger before storing data 6 ARM 5 TRGSEL 4 BEGIN MC9S12KG128 Data Sheet, Rev. 1.15 478 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) Table 16-3. DBGC1 Field Descriptions (continued) Field 3 DBGBRK Description DBG Breakpoint Enable Bit — The DBGBRK bit controls whether the debugger will request a breakpoint based on comparator A and B to the CPU upon completion of a tracing session. Please refer to Section 16.4.3, “Breakpoints,” for further details. 0 CPU break request not enabled 1 CPU break request enabled Capture Mode Field — See Table 16-4 for capture mode field definitions. In LOOP1 mode, the debugger will automatically inhibit redundant entries into capture memory. In detail mode, the debugger is storing address and data for all cycles except program fetch (P) and free (f) cycles. In profile mode, the debugger is returning the address of the last instruction executed by the CPU on each access of trace buffer address. Refer to Section 16.4.2.6, “Capture Modes,” for more information. 1:0 CAPMOD Table 16-4. CAPMOD Encoding CAPMOD 00 01 10 11 Description Normal LOOP1 DETAIL PROFILE MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 479 Chapter 16 Debug Module (DBGV1) 16.3.2.2 Debug Status and Control Register (DBGSC) 7 6 5 4 3 2 1 0 R W Reset AF BF CF 0 TRG 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 16-5. Debug Status and Control Register (DBGSC) Table 16-5. DBGSC Field Descriptions Field 7 AF Description Trigger A Match Flag — The AF bit indicates if trigger A match condition was met since arming. This bit is cleared when ARM in DBGC1 is written to a 1 or on any write to this register. 0 Trigger A did not match 1 Trigger A match Trigger B Match Flag — The BF bit indicates if trigger B match condition was met since arming.This bit is cleared when ARM in DBGC1 is written to a 1 or on any write to this register. 0 Trigger B did not match 1 Trigger B match Comparator C Match Flag — The CF bit indicates if comparator C match condition was met since arming.This bit is cleared when ARM in DBGC1 is written to a 1 or on any write to this register. 0 Comparator C did not match 1 Comparator C match Trigger Mode Bits — The TRG bits select the trigger mode of the DBG module as shown Table 16-6. See Section 16.4.2.5, “Trigger Modes,” for more detail. 6 BF 5 CF 3:0 TRG Table 16-6. Trigger Mode Encoding TRG Value 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 ↓ 1111 Meaning A only A or B A then B Event only B A then event only B A and B (full mode) A and Not B (full mode) Inside range Outside range Reserved (Defaults to A only) MC9S12KG128 Data Sheet, Rev. 1.15 480 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.3.2.3 Debug Trace Buffer Register (DBGTB) 15 14 13 12 11 10 9 8 R W Reset Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 u u u u u u u u = Unimplemented or Reserved Figure 16-6. Debug Trace Buffer Register High (DBGTBH) 7 6 5 4 3 2 1 0 R W Reset Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 u u u u u u u u = Unimplemented or Reserved Figure 16-7. Debug Trace Buffer Register Low (DBGTBL) Table 16-7. DBGTB Field Descriptions Field 15:0 Description Trace Buffer Data Bits — The trace buffer data bits contain the data of the trace buffer. This register can be read only as a word read. Any byte reads or misaligned access of these registers will return 0 and will not cause the trace buffer pointer to increment to the next trace buffer address. The same is true for word reads while the debugger is armed. In addition, this register may appear to contain incorrect data if it is not read with the same capture mode bit settings as when the trace buffer data was recorded (See Section 16.4.2.9, “Reading Data from Trace Buffer”). Because reads will reflect the contents of the trace buffer RAM, the reset state is undefined. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 481 Chapter 16 Debug Module (DBGV1) 16.3.2.4 Debug Count Register (DBGCNT) 7 6 5 4 3 2 1 0 R W Reset TBF 0 CNT 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 16-8. Debug Count Register (DBGCNT) Table 16-8. DBGCNT Field Descriptions Field 7 TBF 5:0 CNT Description Trace Buffer Full — The TBF bit indicates that the trace buffer has stored 64 or more words of data since it was last armed. If this bit is set, then all 64 words will be valid data, regardless of the value in CNT[5:0]. The TBF bit is cleared when ARM in DBGC1 is written to a 1. Count Value — The CNT bits indicate the number of valid data words stored in the trace buffer. Table 16-9 shows the correlation between the CNT bits and the number of valid data words in the trace buffer. When the CNT rolls over to 0, the TBF bit will be set and incrementing of CNT will continue if DBG is in end-trigger mode. The DBGCNT register is cleared when ARM in DBGC1 is written to a 1. Table 16-9. CNT Decoding Table TBF 0 0 0 CNT 000000 000001 000010 .. .. 111110 111111 000000 Description No data valid 1 word valid 2 words valid .. .. 62 words valid 63 words valid 64 words valid; if BEGIN = 1, the ARM bit will be cleared. A breakpoint will be generated if DBGBRK = 1 64 words valid, oldest data has been overwritten by most recent data 0 1 1 000001 .. .. 111111 MC9S12KG128 Data Sheet, Rev. 1.15 482 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.3.2.5 Debug Comparator C Extended Register (DBGCCX) 7 6 5 4 3 2 1 0 R PAGSEL W Reset 0 0 0 0 0 0 0 0 EXTCMP Figure 16-9. Debug Comparator C Extended Register (DBGCCX) Table 16-10. DBGCCX Field Descriptions Field 7:6 PAGSEL Description Page Selector Field — In both BKP and DBG mode, PAGSEL selects the type of paging as shown in Table 16-11. DPAGE and EPAGE are not yet implemented so the value in bit 7 will be ignored (i.e., PAGSEL values of 10 and 11 will be interpreted as values of 00 and 01, respectively). Comparator C Extended Compare Bits — The EXTCMP bits are used as comparison address bits as shown in Table 16-11 along with the appropriate PPAGE, DPAGE, or EPAGE signal from the core. Note: Comparator C can be used when the DBG module is configured for BKP mode. Extended addressing comparisons for comparator C use PAGSEL and will operate differently to the way that comparator A and B operate in BKP mode. 5:0 EXTCMP Table 16-11. PAGSEL Decoding1 PAGSEL 00 01 103 112 1 2 Description Normal (64k) PPAGE (256 — 16K pages) DPAGE (reserved) (256 — 4K pages) EPAGE (reserved) (256 — 1K pages) EXTCMP Not used EXTCMP[5:0] is compared to address bits [21:16]2 EXTCMP[3:0] is compared to address bits [19:16] EXTCMP[1:0] is compared to address bits [17:16] Comment No paged memory PPAGE[7:0] / XAB[21:14] becomes address bits [21:14]1 DPAGE / XAB[21:14] becomes address bits [19:12] EPAGE / XAB[21:14] becomes address bits [17:10] See Figure 16-10. Current HCS12 implementations have PPAGE limited to 6 bits. Therefore, EXTCMP[5:4] should be set to 00. 3 Data page (DPAGE) and Extra page (EPAGE) are reserved for implementation on devices that support paged data and extra space. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 483 Chapter 16 Debug Module (DBGV1) DBGCXX PAGSEL 7 6 0 5 0 4 3 EXTCMP 2 1 BIT 0 BIT 15 DBGCXH[15:12] BIT 14 BIT 13 BIT 12 BKP/DBG MODE 9 8 SEE NOTE 1 PORTK/XAB XAB21 XAB20 XAB19 XAB18 XAB17 XAB16 XAB15 XAB14 PPAGE PIX7 PIX6 PIX5 PIX4 PIX3 PIX2 PIX1 PIX0 SEE NOTE 2 NOTES: 1. In BKP and DBG mode, PAGSEL selects the type of paging as shown in Table 16-11. 2. Current HCS12 implementations are limited to six PPAGE bits, PIX[5:0]. Therefore, EXTCMP[5:4] = 00. Figure 16-10. Comparator C Extended Comparison in BKP/DBG Mode 16.3.2.6 Debug Comparator C Register (DBGCC) 15 14 13 12 11 10 R W Reset Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 16-11. Debug Comparator C Register High (DBGCCH) 7 6 5 4 3 2 1 0 R W Reset Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 16-12. Debug Comparator C Register Low (DBGCCL) Table 16-12. DBGCC Field Descriptions Field 15:0 Description Comparator C Compare Bits — The comparator C compare bits control whether comparator C will compare the address bus bits [15:0] to a logic 1 or logic 0. See Table 16-13. 0 Compare corresponding address bit to a logic 0 1 Compare corresponding address bit to a logic 1 Note: This register will be cleared automatically when the DBG module is armed in LOOP1 mode. MC9S12KG128 Data Sheet, Rev. 1.15 484 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) Table 16-13. Comparator C Compares PAGSEL x0 x1 EXTCMP Compare No compare EXTCMP[5:0] = XAB[21:16] High-Byte Compare DBGCCH[7:0] = AB[15:8] DBGCCH[7:0] = XAB[15:14],AB[13:8] 16.3.2.7 Debug Control Register 2 (DBGC2) 7 6 5 4 3 2 1 0 R W Reset 1 BKABEN1 0 FULL 0 BDM 0 TAGAB 0 BKCEN2 0 TAGC2 0 RWCEN2 0 RWC2 0 When BKABEN is set (BKP mode), all bits in DBGC2 are available. When BKABEN is cleared and DBG is used in DBG mode, bits FULL and TAGAB have no meaning. 2 These bits can be used in BKP mode and DBG mode (when capture mode is not set in LOOP1) to provide a third breakpoint. Figure 16-13. Debug Control Register 2 (DBGC2) Table 16-14. DBGC2 Field Descriptions Field 7 BKABEN Description Breakpoint Using Comparator A and B Enable — This bit enables the breakpoint capability using comparator A and B, when set (BKP mode) the DBGEN bit in DBGC1 cannot be set. 0 Breakpoint module off 1 Breakpoint module on Full Breakpoint Mode Enable — This bit controls whether the breakpoint module is in dual mode or full mode. In full mode, comparator A is used to match address and comparator B is used to match data. See Section 16.4.1.2, “Full Breakpoint Mode,” for more details. 0 Dual address mode enabled 1 Full breakpoint mode enabled Background Debug Mode Enable — This bit determines if the breakpoint causes the system to enter background debug mode (BDM) or initiate a software interrupt (SWI). 0 Go to software interrupt on a break request 1 Go to BDM on a break request Comparator A/B Tag Select — This bit controls whether the breakpoint will cause a break on the next instruction boundary (force) or on a match that will be an executable opcode (tagged). Non-executed opcodes cannot cause a tagged breakpoint. 0 On match, break at the next instruction boundary (force) 1 On match, break if/when the instruction is about to be executed (tagged) Breakpoint Comparator C Enable Bit — This bit enables the breakpoint capability using comparator C. 0 Comparator C disabled for breakpoint 1 Comparator C enabled for breakpoint Note: This bit will be cleared automatically when the DBG module is armed in loop1 mode. Comparator C Tag Select — This bit controls whether the breakpoint will cause a break on the next instruction boundary (force) or on a match that will be an executable opcode (tagged). Non-executed opcodes cannot cause a tagged breakpoint. 0 On match, break at the next instruction boundary (force) 1 On match, break if/when the instruction is about to be executed (tagged) 6 FULL 5 BDM 4 TAGAB 3 BKCEN 2 TAGC MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 485 Chapter 16 Debug Module (DBGV1) Table 16-14. DBGC2 Field Descriptions (continued) Field 1 RWCEN Description Read/Write Comparator C Enable Bit — The RWCEN bit controls whether read or write comparison is enabled for comparator C. RWCEN is not useful for tagged breakpoints. 0 Read/Write is not used in comparison 1 Read/Write is used in comparison Read/Write Comparator C Value Bit — The RWC bit controls whether read or write is used in compare for comparator C. The RWC bit is not used if RWCEN = 0. 0 Write cycle will be matched 1 Read cycle will be matched 0 RWC 16.3.2.8 Debug Control Register 3 (DBGC3) 7 6 5 4 3 2 1 0 R W Reset 1 2 BKAMBH1 0 BKAMBL1 0 BKBMBH2 0 BKBMBL2 0 RWAEN 0 RWA 0 RWBEN 0 RWB 0 In DBG mode, BKAMBH:BKAMBL has no meaning and are forced to 0’s. In DBG mode, BKBMBH:BKBMBL are used in full mode to qualify data. Figure 16-14. Debug Control Register 3 (DBGC3) Table 16-15. DBGC3 Field Descriptions Field Description 7:6 Breakpoint Mask High Byte for First Address — In dual or full mode, these bits may be used to mask (disable) BKAMB[H:L] the comparison of the high and/or low bytes of the first address breakpoint. The functionality is as given in Table 16-16. The x:0 case is for a full address compare. When a program page is selected, the full address compare will be based on bits for a 20-bit compare. The registers used for the compare are {DBGCAX[5:0], DBGCAH[5:0], DBGCAL[7:0]}, where DBGAX[5:0] corresponds to PPAGE[5:0] or extended address bits [19:14] and CPU address [13:0]. When a program page is not selected, the full address compare will be based on bits for a 16-bit compare. The registers used for the compare are {DBGCAH[7:0], DBGCAL[7:0]} which corresponds to CPU address [15:0]. Note: This extended address compare scheme causes an aliasing problem in BKP mode in which several physical addresses may match with a single logical address. This problem may be avoided by using DBG mode to generate breakpoints. The 1:0 case is not sensible because it would ignore the high order address and compare the low order and expansion addresses. Logic forces this case to compare all address lines (effectively ignoring the BKAMBH control bit). The 1:1 case is useful for triggering a breakpoint on any access to a particular expansion page. This only makes sense if a program page is being accessed so that the breakpoint trigger will occur only if DBGCAX compares. MC9S12KG128 Data Sheet, Rev. 1.15 486 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) Table 16-15. DBGC3 Field Descriptions (continued) Field Description 5:4 Breakpoint Mask High Byte and Low Byte of Data (Second Address) — In dual mode, these bits may be BKBMB[H:L] used to mask (disable) the comparison of the high and/or low bytes of the second address breakpoint. The functionality is as given in Table 16-17. The x:0 case is for a full address compare. When a program page is selected, the full address compare will be based on bits for a 20-bit compare. The registers used for the compare are {DBGCBX[5:0], DBGCBH[5:0], DBGCBL[7:0]} where DBGCBX[5:0] corresponds to PPAGE[5:0] or extended address bits [19:14] and CPU address [13:0]. When a program page is not selected, the full address compare will be based on bits for a 16-bit compare. The registers used for the compare are {DBGCBH[7:0], DBGCBL[7:0]} which corresponds to CPU address [15:0]. Note: This extended address compare scheme causes an aliasing problem in BKP mode in which several physical addresses may match with a single logical address. This problem may be avoided by using DBG mode to generate breakpoints. The 1:0 case is not sensible because it would ignore the high order address and compare the low order and expansion addresses. Logic forces this case to compare all address lines (effectively ignoring the BKBMBH control bit). The 1:1 case is useful for triggering a breakpoint on any access to a particular expansion page. This only makes sense if a program page is being accessed so that the breakpoint trigger will occur only if DBGCBX compares. In full mode, these bits may be used to mask (disable) the comparison of the high and/or low bytes of the data breakpoint. The functionality is as given in Table 16-18. 3 RWAEN Read/Write Comparator A Enable Bit — The RWAEN bit controls whether read or write comparison is enabled for comparator A. See Section 16.4.2.1.1, “Read or Write Comparison,” for more information. This bit is not useful for tagged operations. 0 Read/Write is not used in comparison 1 Read/Write is used in comparison Read/Write Comparator A Value Bit — The RWA bit controls whether read or write is used in compare for comparator A. The RWA bit is not used if RWAEN = 0. 0 Write cycle will be matched 1 Read cycle will be matched Read/Write Comparator B Enable Bit — The RWBEN bit controls whether read or write comparison is enabled for comparator B. See Section 16.4.2.1.1, “Read or Write Comparison,” for more information. This bit is not useful for tagged operations. 0 Read/Write is not used in comparison 1 Read/Write is used in comparison Read/Write Comparator B Value Bit — The RWB bit controls whether read or write is used in compare for comparator B. The RWB bit is not used if RWBEN = 0. 0 Write cycle will be matched 1 Read cycle will be matched Note: RWB and RWBEN are not used in full mode. 2 RWA 1 RWBEN 0 RWB Table 16-16. Breakpoint Mask Bits for First Address BKAMBH:BKAMBL x:0 0:1 1:1 1 Address Compare Full address compare 256 byte address range 16K byte address range DBGCAX Yes1 Yes1 Yes 1 DBGCAH Yes Yes No DBGCAL Yes No No If PPAGE is selected. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 487 Chapter 16 Debug Module (DBGV1) Table 16-17. Breakpoint Mask Bits for Second Address (Dual Mode) BKBMBH:BKBMBL x:0 0:1 1:1 1 Address Compare Full address compare 256 byte address range 16K byte address range DBGCBX Yes 1 DBGCBH Yes Yes No DBGCBL Yes No No Yes1 Yes1 If PPAGE is selected. Table 16-18. Breakpoint Mask Bits for Data Breakpoints (Full Mode) BKBMBH:BKBMBL 0:0 0:1 1:0 1:1 1 Data Compare High and low byte compare High byte Low byte No compare DBGCBX No No 1 1 DBGCBH Yes Yes No No DBGCBL Yes No Yes No No1 No1 Expansion addresses for breakpoint B are not applicable in this mode. MC9S12KG128 Data Sheet, Rev. 1.15 488 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.3.2.9 Debug Comparator A Extended Register (DBGCAX) 7 6 5 4 3 2 1 0 R PAGSEL W Reset 0 0 0 0 0 0 0 0 EXTCMP Figure 16-15. Debug Comparator A Extended Register (DBGCAX) Table 16-19. DBGCAX Field Descriptions Field 7:6 PAGSEL Description Page Selector Field — If DBGEN is set in DBGC1, then PAGSEL selects the type of paging as shown in Table 16-20. DPAGE and EPAGE are not yet implemented so the value in bit 7 will be ignored (i.e., PAGSEL values of 10 and 11 will be interpreted as values of 00 and 01, respectively). In BKP mode, PAGSEL has no meaning and EXTCMP[5:0] are compared to address bits [19:14] if the address is in the FLASH/ROM memory space. 5:0 EXTCMP Comparator A Extended Compare Bits — The EXTCMP bits are used as comparison address bits as shown in Table 16-20 along with the appropriate PPAGE, DPAGE, or EPAGE signal from the core. Table 16-20. Comparator A or B Compares Mode BKP 1 EXTCMP Compare No compare EXTCMP[5:0] = XAB[19:14] No compare EXTCMP[5:0] = XAB[21:16] High-Byte Compare DBGCxH[7:0] = AB[15:8] DBGCxH[5:0] = AB[13:8] DBGCxH[7:0] = AB[15:8] DBGCxH[7:0] = XAB[15:14], AB[13:8] Not FLASH/ROM access FLASH/ROM access PAGSEL = 00 PAGSEL = 01 DBG2 1 2 See Figure 16-16. See Figure 16-10 (note that while this figure provides extended comparisons for comparator C, the figure also pertains to comparators A and B in DBG mode only). PAGSEL DBGCXX 0 0 5 4 EXTCMP 3 2 1 BIT 0 PORTK/XAB XAB21 XAB20 XAB19 XAB18 XAB17 XAB16 XAB15 XAB14 PPAGE PIX7 PIX6 PIX5 PIX4 PIX3 PIX2 PIX1 PIX0 SEE NOTE 2 NOTES: 1. In BKP mode, PAGSEL has no functionality. Therefore, set PAGSEL to 00 (reset state). 2. Current HCS12 implementations are limited to six PPAGE bits, PIX[5:0]. Figure 16-16. Comparators A and B Extended Comparison in BKP Mode MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 489 BKP MODE SEE NOTE 1 Chapter 16 Debug Module (DBGV1) 16.3.2.10 Debug Comparator A Register (DBGCA) 15 14 13 12 11 10 9 8 R Bit 15 W Reset 0 0 0 0 0 0 0 0 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Figure 16-17. Debug Comparator A Register High (DBGCAH) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Figure 16-18. Debug Comparator A Register Low (DBGCAL) Table 16-21. DBGCA Field Descriptions Field 15:0 15:0 Description Comparator A Compare Bits — The comparator A compare bits control whether comparator A compares the address bus bits [15:0] to a logic 1 or logic 0. See Table 16-20. 0 Compare corresponding address bit to a logic 0 1 Compare corresponding address bit to a logic 1 16.3.2.11 Debug Comparator B Extended Register (DBGCBX) 7 6 5 4 3 2 1 0 R PAGSEL W Reset 0 0 0 0 0 0 0 0 EXTCMP Figure 16-19. Debug Comparator B Extended Register (DBGCBX) Table 16-22. DBGCBX Field Descriptions Field 7:6 PAGSEL Description Page Selector Field — If DBGEN is set in DBGC1, then PAGSEL selects the type of paging as shown in Table 16-11. DPAGE and EPAGE are not yet implemented so the value in bit 7 will be ignored (i.e., PAGSEL values of 10 and 11 will be interpreted as values of 00 and 01, respectively.) In BKP mode, PAGSEL has no meaning and EXTCMP[5:0] are compared to address bits [19:14] if the address is in the FLASH/ROM memory space. 5:0 EXTCMP Comparator B Extended Compare Bits — The EXTCMP bits are used as comparison address bits as shown in Table 16-11 along with the appropriate PPAGE, DPAGE, or EPAGE signal from the core. Also see Table 16-20. MC9S12KG128 Data Sheet, Rev. 1.15 490 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.3.2.12 Debug Comparator B Register (DBGCB) 15 14 13 12 11 10 9 8 R Bit 15 W Reset 0 0 0 0 0 0 0 0 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Figure 16-20. Debug Comparator B Register High (DBGCBH) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Figure 16-21. Debug Comparator B Register Low (DBGCBL) Table 16-23. DBGCB Field Descriptions Field 15:0 15:0 Description Comparator B Compare Bits — The comparator B compare bits control whether comparator B compares the address bus bits [15:0] or data bus bits [15:0] to a logic 1 or logic 0. See Table 16-20. 0 Compare corresponding address bit to a logic 0, compares to data if in Full mode 1 Compare corresponding address bit to a logic 1, compares to data if in Full mode 16.4 Functional Description This section provides a complete functional description of the DBG module. The DBG module can be configured to run in either of two modes, BKP or DBG. BKP mode is enabled by setting BKABEN in DBGC2. DBG mode is enabled by setting DBGEN in DBGC1. Setting BKABEN in DBGC2 overrides the DBGEN in DBGC1 and prevents DBG mode. If the part is in secure mode, DBG mode cannot be enabled. 16.4.1 DBG Operating in BKP Mode In BKP mode, the DBG will be fully backwards compatible with the existing BKP_ST12_A module. The DBGC2 register has four additional bits that were not available on existing BKP_ST12_A modules. As long as these bits are written to either all 1s or all 0s, they should be transparent to the user. All 1s would enable comparator C to be used as a breakpoint, but tagging would be enabled. The match address register would be all 0s if not modified by the user. Therefore, code executing at address 0x0000 would have to occur before a breakpoint based on comparator C would happen. The DBG module in BKP mode supports two modes of operation: dual address mode and full breakpoint mode. Within each of these modes, forced or tagged breakpoint types can be used. Forced breakpoints occur at the next instruction boundary if a match occurs and tagged breakpoints allow for breaking just before the tagged instruction executes. The action taken upon a successful match can be to either place the CPU in background debug mode or to initiate a software interrupt. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 491 Chapter 16 Debug Module (DBGV1) The breakpoint can operate in dual address mode or full breakpoint mode. Each of these modes is discussed in the subsections below. 16.4.1.1 Dual Address Mode When dual address mode is enabled, two address breakpoints can be set. Each breakpoint can cause the system to enter background debug mode or to initiate a software interrupt based upon the state of BDM in DBGC2 being logic 1 or logic 0, respectively. BDM requests have a higher priority than SWI requests. No data breakpoints are allowed in this mode. TAGAB in DBGC2 selects whether the breakpoint mode is forced or tagged. The BKxMBH:L bits in DBGC3 select whether or not the breakpoint is matched exactly or is a range breakpoint. They also select whether the address is matched on the high byte, low byte, both bytes, and/or memory expansion. The RWx and RWxEN bits in DBGC3 select whether the type of bus cycle to match is a read, write, or read/write when performing forced breakpoints. 16.4.1.2 Full Breakpoint Mode Full breakpoint mode requires a match on address and data for a breakpoint to occur. Upon a successful match, the system will enter background debug mode or initiate a software interrupt based upon the state of BDM in DBGC2 being logic 1 or logic 0, respectively. BDM requests have a higher priority than SWI requests. R/W matches are also allowed in this mode. TAGAB in DBGC2 selects whether the breakpoint mode is forced or tagged. When TAGAB is set in DBGC2, only addresses are compared and data is ignored. The BKAMBH:L bits in DBGC3 select whether or not the breakpoint is matched exactly, is a range breakpoint, or is in page space. The BKBMBH:L bits in DBGC3 select whether the data is matched on the high byte, low byte, or both bytes. RWA and RWAEN bits in DBGC2 select whether the type of bus cycle to match is a read or a write when performing forced breakpoints. RWB and RWBEN bits in DBGC2 are not used in full breakpoint mode. NOTE The full trigger mode is designed to be used for either a word access or a byte access, but not both at the same time. Confusing trigger operation (seemingly false triggers or no trigger) can occur if the trigger address occurs in the user program as both byte and word accesses. 16.4.1.3 Breakpoint Priority Breakpoint operation is first determined by the state of the BDM module. If the BDM module is already active, meaning the CPU is executing out of BDM firmware, breakpoints are not allowed. In addition, while executing a BDM TRACE command, tagging into BDM is not allowed. If BDM is not active, the breakpoint will give priority to BDM requests over SWI requests. This condition applies to both forced and tagged breakpoints. In all cases, BDM related breakpoints will have priority over those generated by the Breakpoint sub-block. This priority includes breakpoints enabled by the TAGLO and TAGHI external pins of the system that interface with the BDM directly and whose signal information passes through and is used by the breakpoint sub-block. MC9S12KG128 Data Sheet, Rev. 1.15 492 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) NOTE BDM should not be entered from a breakpoint unless the ENABLE bit is set in the BDM. Even if the ENABLE bit in the BDM is cleared, the CPU actually executes the BDM firmware code. It checks the ENABLE and returns if ENABLE is 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. When program control returns from a tagged breakpoint through an RTI or a BDM GO command, it will return to the instruction whose tag generated the breakpoint. Unless breakpoints are disabled or modified in the service routine or active BDM session, the instruction will be tagged again and the breakpoint will be repeated. In the case of BDM breakpoints, this situation can also be avoided by executing a TRACE1 command before the GO to increment the program flow past the tagged instruction. 16.4.1.4 Using Comparator C in BKP Mode The original BKP_ST12_A module supports two breakpoints. The DBG_ST12_A module can be used in BKP mode and allow a third breakpoint using comparator C. Four additional bits, BKCEN, TAGC, RWCEN, and RWC in DBGC2 in conjunction with additional comparator C address registers, DBGCCX, DBGCCH, and DBGCCL allow the user to set up a third breakpoint. Using PAGSEL in DBGCCX for expanded memory will work differently than the way paged memory is done using comparator A and B in BKP mode. See Section 16.3.2.5, “Debug Comparator C Extended Register (DBGCCX),” for more information on using comparator C. 16.4.2 DBG Operating in DBG Mode Enabling the DBG module in DBG mode, allows the arming, triggering, and storing of data in the trace buffer and can be used to cause CPU breakpoints. The DBG module is made up of three main blocks, the comparators, trace buffer control logic, and the trace buffer. NOTE In general, there is a latency between the triggering event appearing on the bus and being detected by the DBG circuitry. In general, tagged triggers will be more predictable than forced triggers. 16.4.2.1 Comparators The DBG contains three comparators, A, B, and C. Comparator A compares the core address bus with the address stored in DBGCAH and DBGCAL. Comparator B compares the core address bus with the address stored in DBGCBH and DBGCBL except in full mode, where it compares the data buses to the data stored in DBGCBH and DBGCBL. Comparator C can be used as a breakpoint generator or as the address comparison unit in the loop1 mode. Matches on comparator A, B, and C are signaled to the trace buffer MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 493 Chapter 16 Debug Module (DBGV1) control (TBC) block. When PAGSEL = 01, registers DBGCAX, DBGCBX, and DBGCCX are used to match the upper addresses as shown in Table 16-11. NOTE If a tagged-type C breakpoint is set at the same address as an A/B tagged-type trigger (including the initial entry in an inside or outside range trigger), the C breakpoint will have priority and the trigger will not be recognized. 16.4.2.1.1 Read or Write Comparison Read or write comparisons are useful only with TRGSEL = 0, because only opcodes should be tagged as they are “read” from memory. RWAEN and RWBEN are ignored when TRGSEL = 1. In full modes (“A and B” and “A and not B”) RWAEN and RWA are used to select read or write comparisons for both comparators A and B. Table 16-24 shows the effect for RWAEN, RWA, and RW on the DBGCB comparison conditions. The RWBEN and RWB bits are not used and are ignored in full modes. Table 16-24. Read or Write Comparison Logic Table RWAEN bit 0 0 1 1 1 1 RWA bit x x 0 0 1 1 RW signal 0 1 0 1 0 1 Comment Write data bus Read data bus Write data bus No data bus compare since RW=1 No data bus compare since RW=0 Read data bus 16.4.2.1.2 Trigger Selection The TRGSEL bit in DBGC1 is used to determine the triggering condition in DBG mode. TRGSEL applies to both trigger A and B except in the event only trigger modes. By setting TRGSEL, the comparators A and B will qualify a match with the output of opcode tracking logic and a trigger occurs before the tagged instruction executes (tagged-type trigger). With the TRGSEL bit cleared, a comparator match forces a trigger when the matching condition occurs (force-type trigger). NOTE If the TRGSEL is set, the address stored in the comparator match address registers must be an opcode address for the trigger to occur. 16.4.2.2 Trace Buffer Control (TBC) The TBC is the main controller for the DBG module. Its function is to decide whether data should be stored in the trace buffer based on the trigger mode and the match signals from the comparator. The TBC also determines whether a request to break the CPU should occur. MC9S12KG128 Data Sheet, Rev. 1.15 494 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.4.2.3 Begin- and End-Trigger The definitions of begin- and end-trigger as used in the DBG module are as follows: • Begin-trigger: Storage in trace buffer occurs after the trigger and continues until 64 locations are filled. • End-trigger: Storage in trace buffer occurs until the trigger, with the least recent data falling out of the trace buffer if more than 64 words are collected. 16.4.2.4 Arming the DBG Module In DBG mode, arming occurs by setting DBGEN and ARM in DBGC1. The ARM bit in DBGC1 is cleared when the trigger condition is met in end-trigger mode or when the Trace Buffer is filled in begin-trigger mode. The TBC logic determines whether a trigger condition has been met based on the trigger mode and the trigger selection. 16.4.2.5 Trigger Modes The DBG module supports nine trigger modes. The trigger modes are encoded as shown in Table 16-6. The trigger mode is used as a qualifier for either starting or ending the storing of data in the trace buffer. When the match condition is met, the appropriate flag A or B is set in DBGSC. Arming the DBG module clears the A, B, and C flags in DBGSC. In all trigger modes except for the event-only modes and DETAIL capture mode, change-of-flow addresses are stored in the trace buffer. In the event-only modes only the value on the data bus at the trigger event B will be stored. In DETAIL capture mode address and data for all cycles except program fetch (P) and free (f) cycles are stored in trace buffer. 16.4.2.5.1 A Only In the A only trigger mode, if the match condition for A is met, the A flag in DBGSC is set and a trigger occurs. 16.4.2.5.2 A or B In the A or B trigger mode, if the match condition for A or B is met, the corresponding flag in DBGSC is set and a trigger occurs. 16.4.2.5.3 A then B In the A then B trigger mode, the match condition for A must be met before the match condition for B is compared. When the match condition for A or B is met, the corresponding flag in DBGSC is set. The trigger occurs only after A then B have matched. NOTE When tagging and using A then B, if addresses A and B are close together, then B may not complete the trigger sequence. This occurs when A and B are in the instruction queue at the same time. Basically the A trigger has not yet occurred, so the B instruction is not tagged. Generally, if address B is at MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 495 Chapter 16 Debug Module (DBGV1) least six addresses higher than address A (or B is lower than A) and there are not changes of flow to put these in the queue at the same time, then this operation should trigger properly. 16.4.2.5.4 Event-Only B (Store Data) In the event-only B trigger mode, if the match condition for B is met, the B flag in DBGSC is set and a trigger occurs. The event-only B trigger mode is considered a begin-trigger type and the BEGIN bit in DBGC1 is ignored. Event-only B is incompatible with instruction tagging (TRGSEL = 1), and thus the value of TRGSEL is ignored. Please refer to Section 16.4.2.7, “Storage Memory,” for more information. This trigger mode is incompatible with the detail capture mode so the detail capture mode will have priority. TRGSEL and BEGIN will not be ignored and this trigger mode will behave as if it were “B only”. 16.4.2.5.5 A then Event-Only B (Store Data) In the A then event-only B trigger mode, the match condition for A must be met before the match condition for B is compared, after the A match has occurred, a trigger occurs each time B matches. When the match condition for A or B is met, the corresponding flag in DBGSC is set. The A then event-only B trigger mode is considered a begin-trigger type and BEGIN in DBGC1 is ignored. TRGSEL in DBGC1 applies only to the match condition for A. Please refer to Section 16.4.2.7, “Storage Memory,” for more information. This trigger mode is incompatible with the detail capture mode so the detail capture mode will have priority. TRGSEL and BEGIN will not be ignored and this trigger mode will be the same as A then B. 16.4.2.5.6 A and B (Full Mode) In the A and B trigger mode, comparator A compares to the address bus and comparator B compares to the data bus. In the A and B trigger mode, if the match condition for A and B happen on the same bus cycle, both the A and B flags in the DBGSC register are set and a trigger occurs. If TRGSEL = 1, only matches from comparator A are used to determine if the trigger condition is met and comparator B matches are ignored. If TRGSEL = 0, full-word data matches on an odd address boundary (misaligned access) do not work unless the access is to a RAM that manages misaligned accesses in a single clock cycle (which is typical of RAM modules used in HCS12 MCUs). 16.4.2.5.7 A and Not B (Full Mode) In the A and not B trigger mode, comparator A compares to the address bus and comparator B compares to the data bus. In the A and not B trigger mode, if the match condition for A and not B happen on the same bus cycle, both the A and B flags in DBGSC are set and a trigger occurs. If TRGSEL = 1, only matches from comparator A are used to determine if the trigger condition is met and comparator B matches are ignored. As described in Section 16.4.2.5.6, “A and B (Full Mode),” full-word data compares on misaligned accesses will not match expected data (and thus will cause a trigger in this mode) unless the access is to a RAM that manages misaligned accesses in a single clock cycle. MC9S12KG128 Data Sheet, Rev. 1.15 496 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.4.2.5.8 Inside Range (A ≤ address ≤ B) In the inside range trigger mode, if the match condition for A and B happen on the same bus cycle, both the A and B flags in DBGSC are set and a trigger occurs. If a match condition on only A or only B occurs no flags are set. If TRGSEL = 1, the inside range is accurate only to word boundaries. If TRGSEL = 0, an aligned word access which straddles the range boundary will cause a trigger only if the aligned address is within the range. 16.4.2.5.9 Outside Range (address < A or address > B) In the outside range trigger mode, if the match condition for A or B is met, the corresponding flag in DBGSC is set and a trigger occurs. If TRGSEL = 1, the outside range is accurate only to word boundaries. If TRGSEL = 0, an aligned word access which straddles the range boundary will cause a trigger only if the aligned address is outside the range. 16.4.2.5.10 Control Bit Priorities The definitions of some of the control bits are incompatible with each other. Table 16-25 and the notes associated with it summarize how these incompatibilities are managed: • Read/write comparisons are not compatible with TRGSEL = 1. Therefore, RWAEN and RWBEN are ignored. • Event-only trigger modes are always considered a begin-type trigger. See Section 16.4.2.8.1, “Storing with Begin-Trigger,” and Section 16.4.2.8.2, “Storing with End-Trigger.” • Detail capture mode has priority over the event-only trigger/capture modes. Therefore, event-only modes have no meaning in detail mode and their functions default to similar trigger modes. Table 16-25. Resolution of Mode Conflicts Normal / Loop1 Mode Tag A only A or B A then B Event-only B A then event-only B A and B (full mode) A and not B (full mode) Inside range Outside range 1 2 5 5 6 6 1, 3 4 5 5 6 6 3 4 Force Tag Force Detail 1 — Ignored — same as force 2 — Ignored for comparator B 3 — Reduces to effectively “B only” 4 — Works same as A then B 5 — Reduces to effectively “A only” — B not compared 6 — Only accurate to word boundaries MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 497 Chapter 16 Debug Module (DBGV1) 16.4.2.6 Capture Modes The DBG in DBG mode can operate in four capture modes. These modes are described in the following subsections. 16.4.2.6.1 Normal Mode In normal mode, the DBG module uses comparator A and B as triggering devices. Change-of-flow information or data will be stored depending on TRG in DBGSC. 16.4.2.6.2 Loop1 Mode The intent of loop1 mode is to prevent the trace buffer from being filled entirely with duplicate information from a looping construct such as delays using the DBNE instruction or polling loops using BRSET/BRCLR instructions. Immediately after address information is placed in the trace buffer, the DBG module writes this value into the C comparator and the C comparator is placed in ignore address mode. This will prevent duplicate address entries in the trace buffer resulting from repeated bit-conditional branches. Comparator C will be cleared when the ARM bit is set in loop1 mode to prevent the previous contents of the register from interfering with loop1 mode operation. Breakpoints based on comparator C are disabled. Loop1 mode only inhibits duplicate source address entries that would typically be stored in most tight looping constructs. It will not inhibit repeated entries of destination addresses or vector addresses, because repeated entries of these would most likely indicate a bug in the user’s code that the DBG module is designed to help find. NOTE In certain very tight loops, the source address will have already been fetched again before the C comparator is updated. This results in the source address being stored twice before further duplicate entries are suppressed. This condition occurs with branch-on-bit instructions when the branch is fetched by the first P-cycle of the branch or with loop-construct instructions in which the branch is fetched with the first or second P cycle. See examples below: LOOP INCX ; 1-byte instruction fetched by 1st P-cycle of BRCLR BRCLR CMPTMP,#$0c,LOOP ; the BRCLR instruction also will be fetched by 1st P-cycle of BRCLR * A,LOOP2 ; 2-byte instruction fetched by 1st P-cycle of DBNE ; 1-byte instruction fetched by 2nd P-cycle of DBNE ; this instruction also fetched by 2nd P-cycle of DBNE LOOP2 BRN NOP DBNE NOTE Loop1 mode does not support paged memory, and inhibits duplicate entries in the trace buffer based solely on the CPU address. There is a remote possibility of an erroneous address match if program flow alternates between paged and unpaged memory space. MC9S12KG128 Data Sheet, Rev. 1.15 498 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) 16.4.2.6.3 Detail Mode In the detail mode, address and data for all cycles except program fetch (P) and free (f) cycles are stored in trace buffer. This mode is intended to supply additional information on indexed, indirect addressing modes where storing only the destination address would not provide all information required for a user to determine where his code was in error. 16.4.2.6.4 Profile Mode This mode is intended to allow a host computer to poll a running target and provide a histogram of program execution. Each read of the trace buffer address will return the address of the last instruction executed. The DBGCNT register is not incremented and the trace buffer does not get filled. The ARM bit is not used and all breakpoints and all other debug functions will be disabled. 16.4.2.7 Storage Memory The storage memory is a 64 words deep by 16-bits wide dual port RAM array. The CPU accesses the RAM array through a single memory location window (DBGTBH:DBGTBL). The DBG module stores trace information in the RAM array in a circular buffer format. As data is read via the CPU, a pointer into the RAM will increment so that the next CPU read will receive fresh information. In all trigger modes except for event-only and detail capture mode, the data stored in the trace buffer will be change-of-flow addresses. change-of-flow addresses are defined as follows: • Source address of conditional branches (long, short, BRSET, and loop constructs) taken • Destination address of indexed JMP, JSR, and CALL instruction • Destination address of RTI, RTS, and RTC instructions • Vector address of interrupts except for SWI and BDM vectors In the event-only trigger modes only the 16-bit data bus value corresponding to the event is stored. In the detail capture mode, address and then data are stored for all cycles except program fetch (P) and free (f) cycles. 16.4.2.8 16.4.2.8.1 Storing Data in Memory Storage Buffer Storing with Begin-Trigger Storing with begin-trigger can be used in all trigger modes. When DBG mode is enabled and armed in the begin-trigger mode, data is not stored in the trace buffer until the trigger condition is met. As soon as the trigger condition is met, the DBG module will remain armed until 64 words are stored in the trace buffer. If the trigger is at the address of the change-of-flow instruction the change-of-flow associated with the trigger event will be stored in the trace buffer. 16.4.2.8.2 Storing with End-Trigger Storing with end-trigger cannot be used in event-only trigger modes. When DBG mode is enabled and armed in the end-trigger mode, data is stored in the trace buffer until the trigger condition is met. When the trigger condition is met, the DBG module will become de-armed and no more data will be stored. If MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 499 Chapter 16 Debug Module (DBGV1) the trigger is at the address of a change-of-flow address the trigger event will not be stored in the trace buffer. 16.4.2.9 Reading Data from Trace Buffer The data stored in the trace buffer can be read using either the background debug module (BDM) module or the CPU provided the DBG module is enabled and not armed. The trace buffer data is read out first-in first-out. By reading CNT in DBGCNT the number of valid words can be determined. CNT will not decrement as data is read from DBGTBH:DBGTBL. The trace buffer data is read by reading DBGTBH:DBGTBL with a 16-bit read. Each time DBGTBH:DBGTBL is read, a pointer in the DBG will be incremented to allow reading of the next word. Reading the trace buffer while the DBG module is armed will return invalid data and no shifting of the RAM pointer will occur. NOTE The trace buffer should be read with the DBG module enabled and in the same capture mode that the data was recorded. The contents of the trace buffer counter register (DBGCNT) are resolved differently in detail mode verses the other modes and may lead to incorrect interpretation of the trace buffer data. 16.4.3 Breakpoints There are two ways of getting a breakpoint in DBG mode. One is based on the trigger condition of the trigger mode using comparator A and/or B, and the other is using comparator C. External breakpoints generated using the TAGHI and TAGLO external pins are disabled in DBG mode. 16.4.3.1 Breakpoint Based on Comparator A and B A breakpoint request to the CPU can be enabled by setting DBGBRK in DBGC1. The value of BEGIN in DBGC1 determines when the breakpoint request to the CPU will occur. When BEGIN in DBGC1 is set, begin-trigger is selected and the breakpoint request will not occur until the trace buffer is filled with 64 words. When BEGIN in DBGC1 is cleared, end-trigger is selected and the breakpoint request will occur immediately at the trigger cycle. There are two types of breakpoint requests supported by the DBG module, tagged and forced. Tagged breakpoints are associated with opcode addresses and allow breaking just before a specific instruction executes. Forced breakpoints are not associated with opcode addresses and allow breaking at the next instruction boundary. The type of breakpoint based on comparators A and B is determined by TRGSEL in the DBGC1 register (TRGSEL = 1 for tagged breakpoint, TRGSEL = 0 for forced breakpoint). Table 16-26 illustrates the type of breakpoint that will occur based on the debug run. MC9S12KG128 Data Sheet, Rev. 1.15 500 Freescale Semiconductor Chapter 16 Debug Module (DBGV1) Table 16-26. Breakpoint Setup BEGIN 0 0 0 0 1 1 1 1 TRGSEL 0 0 1 1 0 0 1 1 DBGBRK 0 1 0 1 0 1 0 1 Type of Debug Run Fill trace buffer until trigger address (no CPU breakpoint — keep running) Fill trace buffer until trigger address, then a forced breakpoint request occurs Fill trace buffer until trigger opcode is about to execute (no CPU breakpoint — keep running) Fill trace buffer until trigger opcode about to execute, then a tagged breakpoint request occurs Start trace buffer at trigger address (no CPU breakpoint — keep running) Start trace buffer at trigger address, a forced breakpoint request occurs when trace buffer is full Start trace buffer at trigger opcode (no CPU breakpoint — keep running) Start trace buffer at trigger opcode, a forced breakpoint request occurs when trace buffer is full 16.4.3.2 Breakpoint Based on Comparator C A breakpoint request to the CPU can be created if BKCEN in DBGC2 is set. Breakpoints based on a successful comparator C match can be accomplished regardless of the mode of operation for comparator A or B, and do not affect the status of the ARM bit. TAGC in DBGC2 is used to select either tagged or forced breakpoint requests for comparator C. Breakpoints based on comparator C are disabled in LOOP1 mode. NOTE Because breakpoints cannot be disabled when the DBG is armed, one must be careful to avoid an “infinite breakpoint loop” when using tagged-type C breakpoints while the DBG is armed. If BDM breakpoints are selected, executing a TRACE1 instruction before the GO instruction is the recommended way to avoid re-triggering a breakpoint if one does not wish to de-arm the DBG. If SWI breakpoints are selected, disarming the DBG in the SWI interrupt service routine is the recommended way to avoid re-triggering a breakpoint. 16.5 Resets The DBG module is disabled after reset. The DBG module cannot cause a MCU reset. 16.6 Interrupts The DBG contains one interrupt source. If a breakpoint is requested and BDM in DBGC2 is cleared, an SWI interrupt will be generated. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 501 Chapter 16 Debug Module (DBGV1) MC9S12KG128 Data Sheet, Rev. 1.15 502 Freescale Semiconductor Chapter 17 Interrupt (INTV1) 17.1 Introduction This section describes the functionality of the interrupt (INT) sub-block of the S12 core platform. A block diagram of the interrupt sub-block is shown in Figure 17-1. INT WRITE DATA BUS HPRIO (OPTIONAL) HIGHEST PRIORITY I-INTERRUPT INTERRUPTS XMASK IMASK INTERRUPT INPUT REGISTERS AND CONTROL REGISTERS READ DATA BUS WAKEUP HPRIO VECTOR QUALIFIED INTERRUPTS INTERRUPT PENDING RESET FLAGS VECTOR REQUEST PRIORITY DECODER VECTOR ADDRESS Figure 17-1. INT Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 503 Chapter 17 Interrupt (INTV1) The interrupt sub-block decodes the priority of all system exception requests and provides the applicable vector for processing the exception. The INT supports I-bit maskable and X-bit maskable interrupts, a non-maskable unimplemented opcode trap, a non-maskable software interrupt (SWI) or background debug mode request, and three system reset vector requests. All interrupt related exception requests are managed by the interrupt sub-block (INT). 17.1.1 Features The INT includes these features: • Provides two to 122 I-bit maskable interrupt vectors (0xFF00–0xFFF2) • Provides one X-bit maskable interrupt vector (0xFFF4) • Provides a non-maskable software interrupt (SWI) or background debug mode request vector (0xFFF6) • Provides a non-maskable unimplemented opcode trap (TRAP) vector (0xFFF8) • Provides three system reset vectors (0xFFFA–0xFFFE) (reset, CMR, and COP) • Determines the appropriate vector and drives it onto the address bus at the appropriate time • Signals the CPU that interrupts are pending • Provides control registers which allow testing of interrupts • Provides additional input signals which prevents requests for servicing I and X interrupts • Wakes the system from stop or wait mode when an appropriate interrupt occurs or whenever XIRQ is active, even if XIRQ is masked • Provides asynchronous path for all I and X interrupts, (0xFF00–0xFFF4) • (Optional) selects and stores the highest priority I interrupt based on the value written into the HPRIO register 17.1.2 Modes of Operation The functionality of the INT sub-block in various modes of operation is discussed in the subsections that follow. • Normal operation The INT operates the same in all normal modes of operation. • Special operation Interrupts may be tested in special modes through the use of the interrupt test registers. • Emulation modes The INT operates the same in emulation modes as in normal modes. • Low power modes See Section 17.4.1, “Low-Power Modes,” for details MC9S12KG128 Data Sheet, Rev. 1.15 504 Freescale Semiconductor Chapter 17 Interrupt (INTV1) 17.2 External Signal Description Most interfacing with the interrupt sub-block is done within the core. However, the interrupt does receive direct input from the multiplexed external bus interface (MEBI) sub-block of the core for the IRQ and XIRQ pin data. 17.3 Memory Map and Register Definition Detailed descriptions of the registers and associated bits are given in the subsections that follow. 17.3.1 Module Memory Map Table 17-1. INT Memory Map Address Offset 0x0015 0x0016 0x001F Use Interrupt Test Control Register (ITCR) Interrupt Test Registers (ITEST) Highest Priority Interrupt (Optional) (HPRIO) Access R/W R/W R/W 17.3.2 17.3.2.1 Register Descriptions Interrupt Test Control Register 7 6 5 4 3 2 1 0 R W Reset 0 0 0 WRTINT ADR3 1 ADR2 1 ADR1 1 ADR0 1 0 0 0 0 = Unimplemented or Reserved Figure 17-2. Interrupt Test Control Register (ITCR) Read: See individual bit descriptions Write: See individual bit descriptions MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 505 Chapter 17 Interrupt (INTV1) Table 17-2. ITCR Field Descriptions Field 4 WRTINT Description Write to the Interrupt Test Registers Read: anytime Write: only in special modes and with I-bit mask and X-bit mask set. 0 Disables writes to the test registers; reads of the test registers will return the state of the interrupt inputs. 1 Disconnect the interrupt inputs from the priority decoder and use the values written into the ITEST registers instead. Note: Any interrupts which are pending at the time that WRTINT is set will remain until they are overwritten. Test Register Select Bits Read: anytime Write: anytime These bits determine which test register is selected on a read or write. The hexadecimal value written here will be the same as the upper nibble of the lower byte of the vector selects. That is, an “F” written into ADR[3:0] will select vectors 0xFFFE–0xFFF0 while a “7” written to ADR[3:0] will select vectors 0xFF7E–0xFF70. 3:0 ADR[3:0] 17.3.2.2 Interrupt Test Registers 7 6 5 4 3 2 1 0 R INTE W Reset 0 0 0 0 0 0 0 0 INTC INTA INT8 INT6 INT4 INT2 INT0 = Unimplemented or Reserved Figure 17-3. Interrupt TEST Registers (ITEST) Read: Only in special modes. Reads will return either the state of the interrupt inputs of the interrupt sub-block (WRTINT = 0) or the values written into the TEST registers (WRTINT = 1). Reads will always return 0s in normal modes. Write: Only in special modes and with WRTINT = 1 and CCR I mask = 1. Table 17-3. ITEST Field Descriptions Field 7:0 INT[E:0] Description Interrupt TEST Bits — These registers are used in special modes for testing the interrupt logic and priority independent of the system configuration. Each bit is used to force a specific interrupt vector by writing it to a logic 1 state. Bits are named INTE through INT0 to indicate vectors 0xFFxE through 0xFFx0. These bits can be written only in special modes and only with the WRTINT bit set (logic 1) in the interrupt test control register (ITCR). In addition, I interrupts must be masked using the I bit in the CCR. In this state, the interrupt input lines to the interrupt sub-block will be disconnected and interrupt requests will be generated only by this register. These bits can also be read in special modes to view that an interrupt requested by a system block (such as a peripheral block) has reached the INT module. There is a test register implemented for every eight interrupts in the overall system. All of the test registers share the same address and are individually selected using the value stored in the ADR[3:0] bits of the interrupt test control register (ITCR). Note: When ADR[3:0] have the value of 0x000F, only bits 2:0 in the ITEST register will be accessible. That is, vectors higher than 0xFFF4 cannot be tested using the test registers and bits 7:3 will always read as a logic 0. If ADR[3:0] point to an unimplemented test register, writes will have no effect and reads will always return a logic 0 value. MC9S12KG128 Data Sheet, Rev. 1.15 506 Freescale Semiconductor Chapter 17 Interrupt (INTV1) 17.3.2.3 Highest Priority I Interrupt (Optional) 7 6 5 4 3 2 1 0 R PSEL7 W Reset 1 1 1 1 0 0 1 PSEL6 PSEL5 PSEL4 PSEL3 PSEL2 PSEL1 0 0 = Unimplemented or Reserved Figure 17-4. Highest Priority I Interrupt Register (HPRIO) Read: Anytime Write: Only if I mask in CCR = 1 Table 17-4. HPRIO Field Descriptions Field 7:1 PSEL[7:1] Description Highest Priority I Interrupt Select Bits — The state of these bits determines which I-bit maskable interrupt will be promoted to highest priority (of the I-bit maskable interrupts). To promote an interrupt, the user writes the least significant byte of the associated interrupt vector address to this register. If an unimplemented vector address or a non I-bit masked vector address (value higher than 0x00F2) is written, IRQ (0xFFF2) will be the default highest priority interrupt. 17.4 Functional Description The interrupt sub-block processes all exception requests made by the CPU. These exceptions include interrupt vector requests and reset vector requests. Each of these exception types and their overall priority level is discussed in the subsections below. 17.4.1 Low-Power Modes The INT does not contain any user-controlled options for reducing power consumption. The operation of the INT in low-power modes is discussed in the following subsections. 17.4.1.1 Operation in Run Mode The INT does not contain any options for reducing power in run mode. 17.4.1.2 Operation in Wait Mode Clocks to the INT can be shut off during system wait mode and the asynchronous interrupt path will be used to generate the wake-up signal upon recognition of a valid interrupt or any XIRQ request. 17.4.1.3 Operation in Stop Mode Clocks to the INT can be shut off during system stop mode and the asynchronous interrupt path will be used to generate the wake-up signal upon recognition of a valid interrupt or any XIRQ request. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 507 Chapter 17 Interrupt (INTV1) 17.5 Resets The INT supports three system reset exception request types: normal system reset or power-on-reset request, crystal monitor reset request, and COP watchdog reset request. The type of reset exception request must be decoded by the system and the proper request made to the core. The INT will then provide the service routine address for the type of reset requested. 17.6 Interrupts As shown in the block diagram in Figure 17-1, the INT contains a register block to provide interrupt status and control, an optional highest priority I interrupt (HPRIO) block, and a priority decoder to evaluate whether pending interrupts are valid and assess their priority. 17.6.1 Interrupt Registers The INT registers are accessible only in special modes of operation and function as described in Section 17.3.2.1, “Interrupt Test Control Register,” and Section 17.3.2.2, “Interrupt Test Registers,” previously. 17.6.2 Highest Priority I-Bit Maskable Interrupt When the optional HPRIO block is implemented, the user is allowed to promote a single I-bit maskable interrupt to be the highest priority I interrupt. The HPRIO evaluates all interrupt exception requests and passes the HPRIO vector to the priority decoder if the highest priority I interrupt is active. RTI replaces the promoted interrupt source. 17.6.3 Interrupt Priority Decoder The priority decoder evaluates all interrupts pending and determines their validity and priority. When the CPU requests an interrupt vector, the decoder will provide the vector for the highest priority interrupt request. Because the vector is not supplied until the CPU requests it, it is possible that a higher priority interrupt request could override the original exception that caused the CPU to request the vector. In this case, the CPU will receive the highest priority vector and the system will process this exception instead of the original request. NOTE Care must be taken to ensure that all exception requests remain active until the system begins execution of the applicable service routine; otherwise, the exception request may not be processed. If for any reason the interrupt source is unknown (e.g., an interrupt request becomes inactive after the interrupt has been recognized but prior to the vector request), the vector address will default to that of the last valid interrupt that existed during the particular interrupt sequence. If the CPU requests an interrupt vector when there has never been a pending interrupt request, the INT will provide the software interrupt (SWI) vector address. MC9S12KG128 Data Sheet, Rev. 1.15 508 Freescale Semiconductor Chapter 17 Interrupt (INTV1) 17.7 Exception Priority The priority (from highest to lowest) and address of all exception vectors issued by the INT upon request by the CPU is shown in Table 17-5. Table 17-5. Exception Vector Map and Priority Vector Address 0xFFFE–0xFFFF 0xFFFC–0xFFFD 0xFFFA–0xFFFB 0xFFF8–0xFFF9 0xFFF6–0xFFF7 0xFFF4–0xFFF5 0xFFF2–0xFFF3 0xFFF0–0xFF00 System reset Crystal monitor reset COP reset Unimplemented opcode trap Software interrupt instruction (SWI) or BDM vector request XIRQ signal IRQ signal Device-specific I-bit maskable interrupt sources (priority in descending order) Source MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 509 Chapter 17 Interrupt (INTV1) MC9S12KG128 Data Sheet, Rev. 1.15 510 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.1 Introduction This section describes the functionality of the multiplexed external bus interface (MEBI) sub-block of the S12 core platform. The functionality of the module is closely coupled with the S12 CPU and the memory map controller (MMC) sub-blocks. Figure 18-1 is a block diagram of the MEBI. In Figure 18-1, the signals on the right hand side represent pins that are accessible externally. On some chips, these may not all be bonded out. The MEBI sub-block of the core serves to provide access and/or visibility to internal core data manipulation operations including timing reference information at the external boundary of the core and/or system. Depending upon the system operating mode and the state of bits within the control registers of the MEBI, the internal 16-bit read and write data operations will be represented in 8-bit or 16-bit accesses externally. Using control information from other blocks within the system, the MEBI will determine the appropriate type of data access to be generated. 18.1.1 Features The block name includes these distinctive features: • External bus controller with four 8-bit ports A,B, E, and K • Data and data direction registers for ports A, B, E, and K when used as general-purpose I/O • Control register to enable/disable alternate functions on ports E and K • Mode control register • Control register to enable/disable pull resistors on ports A, B, E, and K • Control register to enable/disable reduced output drive on ports A, B, E, and K • Control register to configure external clock behavior • Control register to configure IRQ pin operation • Logic to capture and synchronize external interrupt pin inputs MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 511 Chapter 18 Multiplexed External Bus Interface (MEBIV3) REGS Port K ADDR PK[7:0]/ECS/XCS/X[19:14] Internal Bus Data[15:0] EXT BUS I/F CTL ADDR DATA Port A Addr[19:0] PA[7:0]/A[15:8]/ D[15:8]/D[7:0] (Control) Port B ADDR PB[7:0]/A[7:0]/ D[7:0] DATA PE[7:2]/NOACC/ IPIPE1/MODB/CLKTO IPIPE0/MODA/ ECLK/ LSTRB/TAGLO R/W PE1/IRQ PE0/XIRQ ECLK CTL CPU pipe info IRQ interrupt XIRQ interrupt PIPE CTL IRQ CTL TAG CTL mode BDM tag info Port E BKGD BKGD/MODC/TAGHI Control signal(s) Data signal (unidirectional) Data signal (bidirectional) Data bus (unidirectional) Data bus (bidirectional) Figure 18-1. MEBI Block Diagram MC9S12KG128 Data Sheet, Rev. 1.15 512 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.1.2 • Modes of Operation • • • • • • • Normal expanded wide mode Ports A and B are configured as a 16-bit multiplexed address and data bus and port E provides bus control and status signals. This mode allows 16-bit external memory and peripheral devices to be interfaced to the system. Normal expanded narrow mode Ports A and B are configured as a 16-bit address bus and port A is multiplexed with 8-bit data. Port E provides bus control and status signals. This mode allows 8-bit external memory and peripheral devices to be interfaced to the system. Normal single-chip mode There is no external expansion bus in this mode. The processor program is executed from internal memory. Ports A, B, K, and most of E are available as general-purpose I/O. Special single-chip mode This mode is generally used for debugging single-chip operation, boot-strapping, or security related operations. The active background mode is in control of CPU execution and BDM firmware is waiting for additional serial commands through the BKGD pin. There is no external expansion bus after reset in this mode. Emulation expanded wide mode Developers use this mode for emulation systems in which the users target application is normal expanded wide mode. Emulation expanded narrow mode Developers use this mode for emulation systems in which the users target application is normal expanded narrow mode. Special test mode Ports A and B are configured as a 16-bit multiplexed address and data bus and port E provides bus control and status signals. In special test mode, the write protection of many control bits is lifted so that they can be thoroughly tested without needing to go through reset. Special peripheral mode This mode is intended for Freescale Semiconductor factory testing of the system. The CPU is inactive and an external (tester) bus master drives address, data, and bus control signals. 18.2 External Signal Description In typical implementations, the MEBI sub-block of the core interfaces directly with external system pins. Some pins may not be bonded out in all implementations. Table 18-1 outlines the pin names and functions and gives a brief description of their operation reset state of these pins and associated pull-ups or pull-downs is dependent on the mode of operation and on the integration of this block at the chip level (chip dependent). MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 513 Chapter 18 Multiplexed External Bus Interface (MEBIV3) . Table 18-1. External System Pins Associated With MEBI Pin Name Pin Functions MODC BKGD TAGHI Description At the rising edge on RESET, the state of this pin is registered into the MODC bit to set the mode. (This pin always has an internal pullup.) Pseudo open-drain communication pin for the single-wire background debug mode. There is an internal pull-up resistor on this pin. When instruction tagging is on, a 0 at the falling edge of E tags the high half of the instruction word being read into the instruction queue. General-purpose I/O pins, see PORTA and DDRA registers. High-order address lines multiplexed during ECLK low. Outputs except in special peripheral mode where they are inputs from an external tester system. High-order bidirectional data lines multiplexed during ECLK high in expanded wide modes, special peripheral mode, and visible internal accesses (IVIS = 1) in emulation expanded narrow mode. Direction of data transfer is generally indicated by R/W. Alternate high-order and low-order bytes of the bidirectional data lines multiplexed during ECLK high in expanded narrow modes and narrow accesses in wide modes. Direction of data transfer is generally indicated by R/W. General-purpose I/O pins, see PORTB and DDRB registers. Low-order address lines multiplexed during ECLK low. Outputs except in special peripheral mode where they are inputs from an external tester system. Low-order bidirectional data lines multiplexed during ECLK high in expanded wide modes, special peripheral mode, and visible internal accesses (with IVIS = 1) in emulation expanded narrow mode. Direction of data transfer is generally indicated by R/W. General-purpose I/O pin, see PORTE and DDRE registers. CPU No Access output. Indicates whether the current cycle is a free cycle. Only available in expanded modes. At the rising edge of RESET, the state of this pin is registered into the MODB bit to set the mode. General-purpose I/O pin, see PORTE and DDRE registers. Instruction pipe status bit 1, enabled by PIPOE bit in PEAR. System clock test output. Only available in special modes. PIPOE = 1 overrides this function. The enable for this function is in the clock module. At the rising edge on RESET, the state of this pin is registered into the MODA bit to set the mode. General-purpose I/O pin, see PORTE and DDRE registers. Instruction pipe status bit 0, enabled by PIPOE bit in PEAR. BKGD/MODC/ TAGHI PA7/A15/D15/D7 thru PA0/A8/D8/D0 PA7–PA0 A15–A8 D15–D8 D15/D7 thru D8/D0 PB7/A7/D7 thru PB0/A0/D0 PB7–PB0 A7–A0 D7–D0 PE7/NOACC PE7 NOACC PE6/IPIPE1/ MODB/CLKTO MODB PE6 IPIPE1 CLKTO PE5/IPIPE0/MODA MODA PE5 IPIPE0 MC9S12KG128 Data Sheet, Rev. 1.15 514 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) Table 18-1. External System Pins Associated With MEBI (continued) Pin Name PE4/ECLK Pin Functions PE4 ECLK Description General-purpose I/O pin, see PORTE and DDRE registers. Bus timing reference clock, can operate as a free-running clock at the system clock rate or to produce one low-high clock per visible access, with the high period stretched for slow accesses. ECLK is controlled by the NECLK bit in PEAR, the IVIS bit in MODE, and the ESTR bit in EBICTL. General-purpose I/O pin, see PORTE and DDRE registers. Low strobe bar, 0 indicates valid data on D7–D0. In special peripheral mode, this pin is an input indicating the size of the data transfer (0 = 16-bit; 1 = 8-bit). In expanded wide mode or emulation narrow modes, when instruction tagging is on and low strobe is enabled, a 0 at the falling edge of E tags the low half of the instruction word being read into the instruction queue. General-purpose I/O pin, see PORTE and DDRE registers. Read/write, indicates the direction of internal data transfers. This is an output except in special peripheral mode where it is an input. General-purpose input-only pin, can be read even if IRQ enabled. Maskable interrupt request, can be level sensitive or edge sensitive. General-purpose input-only pin. Non-maskable interrupt input. General-purpose I/O pin, see PORTK and DDRK registers. Emulation chip select General-purpose I/O pin, see PORTK and DDRK registers. External data chip select General-purpose I/O pins, see PORTK and DDRK registers. Memory expansion addresses PE3/LSTRB/ TAGLO PE3 LSTRB SZ8 TAGLO PE2/R/W PE2 R/W PE1/IRQ PE1 IRQ PE0/XIRQ PE0 XIRQ PK7/ECS PK7 ECS PK6/XCS PK6 XCS PK5/X19 thru PK0/X14 PK5–PK0 X19–X14 Detailed descriptions of these pins can be found in the device overview chapter. 18.3 Memory Map and Register Definition A summary of the registers associated with the MEBI sub-block is shown in Table 18-2. Detailed descriptions of the registers and bits are given in the subsections that follow. On most chips the registers are mappable. Therefore, the upper bits may not be all 0s as shown in the table and descriptions. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 515 Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.1 Module Memory Map Table 18-2. MEBI Memory Map Address Offset 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x001E 0x00032 0x00033 Port A Data Register (PORTA) Port B Data Register (PORTB) Data Direction Register A (DDRA) Data Direction Register B (DDRB) Reserved Reserved Reserved Reserved Port E Data Register (PORTE) Data Direction Register E (DDRE) Port E Assignment Register (PEAR) Mode Register (MODE) Pull Control Register (PUCR) Reduced Drive Register (RDRIV) External Bus Interface Control Register (EBICTL) Reserved IRQ Control Register (IRQCR) Port K Data Register (PORTK) Data Direction Register K (DDRK) Use Access R/W R/W R/W R/W R R R R R/W R/W R/W R/W R/W R/W R/W R R/W R/W R/W 18.3.2 18.3.2.1 Register Descriptions Port A Data Register (PORTA) 7 6 5 4 3 2 1 0 R Bit 7 W Reset Single Chip 0 PA7 0 PA6 AB/DB14 0 PA5 AB/DB13 0 PA4 AB/DB12 0 PA3 AB/DB11 0 PA2 AB/DB10 0 PA1 AB/DB9 AB9 and DB9/DB1 0 PA0 AB/DB8 AB8 and DB8/DB0 6 5 4 3 2 1 Bit 0 Expanded Wide, Emulation Narrow with AB/DB15 IVIS, and Peripheral Expanded Narrow AB15 and AB14 and AB13 and AB12 and AB11 and AB10 and DB15/DB7 DB14/DB6 DB13/DB5 DB12/DB4 DB11/DB3 DB10/DB2 Figure 18-2. Port A Data Register (PORTA) MC9S12KG128 Data Sheet, Rev. 1.15 516 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) Read: Anytime when register is in the map Write: Anytime when register is in the map Port A bits 7 through 0 are associated with address lines A15 through A8 respectively and data lines D15/D7 through D8/D0 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. Data direction register A (DDRA) determines the primary direction of each pin. DDRA also determines the source of data for a read of PORTA. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. NOTE To ensure that you read the value present on the PORTA pins, always wait at least one cycle after writing to the DDRA register before reading from the PORTA register. 18.3.2.2 Port B Data Register (PORTB) 7 6 5 4 3 2 1 0 R Bit 7 W Reset Single Chip Expanded Wide, Emulation Narrow with IVIS, and Peripheral Expanded Narrow 0 PB7 AB/DB7 AB7 0 PB6 AB/DB6 AB6 0 PB5 AB/DB5 AB5 0 PB4 AB/DB4 AB4 0 PB3 AB/DB3 AB3 0 PB2 AB/DB2 AB2 0 PB1 AB/DB1 AB1 0 PB0 AB/DB0 AB0 6 5 4 3 2 1 Bit 0 Figure 18-3. Port A Data Register (PORTB) Read: Anytime when register is in the map Write: Anytime when register is in the map Port B bits 7 through 0 are associated with address lines A7 through A0 respectively and data lines D7 through D0 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. Data direction register B (DDRB) determines the primary direction of each pin. DDRB also determines the source of data for a read of PORTB. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. NOTE To ensure that you read the value present on the PORTB pins, always wait at least one cycle after writing to the DDRB register before reading from the PORTB register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 517 Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.3 Data Direction Register A (DDRA) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 1 Bit 0 Figure 18-4. Data Direction Register A (DDRA) Read: Anytime when register is in the map Write: Anytime when register is in the map This register controls the data direction for port A. When port A is operating as a general-purpose I/O port, DDRA determines the primary direction for each port A pin. A 1 causes the associated port pin to be an output and a 0 causes the associated pin to be a high-impedance input. The value in a DDR bit also affects the source of data for reads of the corresponding PORTA register. If the DDR bit is 0 (input) the buffered pin input state is read. If the DDR bit is 1 (output) the associated port data register bit state is read. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. It is reset to 0x00 so the DDR does not override the three-state control signals. Table 18-3. DDRA Field Descriptions Field 7:0 DDRA Description Data Direction Port A 0 Configure the corresponding I/O pin as an input 1 Configure the corresponding I/O pin as an output MC9S12KG128 Data Sheet, Rev. 1.15 518 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.4 Data Direction Register B (DDRB) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 1 Bit 0 Figure 18-5. Data Direction Register B (DDRB) Read: Anytime when register is in the map Write: Anytime when register is in the map This register controls the data direction for port B. When port B is operating as a general-purpose I/O port, DDRB determines the primary direction for each port B pin. A 1 causes the associated port pin to be an output and a 0 causes the associated pin to be a high-impedance input. The value in a DDR bit also affects the source of data for reads of the corresponding PORTB register. If the DDR bit is 0 (input) the buffered pin input state is read. If the DDR bit is 1 (output) the associated port data register bit state is read. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. It is reset to 0x00 so the DDR does not override the three-state control signals. Table 18-4. DDRB Field Descriptions Field 7:0 DDRB Description Data Direction Port B 0 Configure the corresponding I/O pin as an input 1 Configure the corresponding I/O pin as an output MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 519 Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.5 Reserved Registers 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-6. Reserved Register 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-7. Reserved Register 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-8. Reserved Register 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-9. Reserved Register These register locations are not used (reserved). All unused registers and bits in this block return logic 0s when read. Writes to these registers have no effect. These registers are not in the on-chip map in special peripheral mode. MC9S12KG128 Data Sheet, Rev. 1.15 520 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.6 Port E Data Register (PORTE) 7 6 5 4 3 2 1 0 R Bit 7 W Reset Alternate Pin Function 0 NOACC 0 MODB or IPIPE1 or CLKTO 0 MODA or IPIPE0 0 ECLK 0 LSTRB or TAGLO 0 R/W 6 5 4 3 2 Bit 1 Bit 0 u IRQ u XIRQ = Unimplemented or Reserved u = Unaffected by reset Figure 18-10. Port E Data Register (PORTE) Read: Anytime when register is in the map Write: Anytime when register is in the map Port E is associated with external bus control signals and interrupt inputs. These include mode select (MODB/IPIPE1, MODA/IPIPE0), E clock, size (LSTRB/TAGLO), read/write (R/W), IRQ, and XIRQ. When not used for one of these specific functions, port E pins 7:2 can be used as general-purpose I/O and pins 1:0 can be used as general-purpose input. The port E assignment register (PEAR) selects the function of each pin and DDRE determines whether each pin is an input or output when it is configured to be general-purpose I/O. DDRE also determines the source of data for a read of PORTE. Some of these pins have software selectable pull resistors. IRQ and XIRQ can only be pulled up whereas the polarity of the PE7, PE4, PE3, and PE2 pull resistors are determined by chip integration. Please refer to the device overview chapter (Signal Property Summary) to determine the polarity of these resistors. A single control bit enables the pull devices for all of these pins when they are configured as inputs. This register is not in the on-chip map in special peripheral mode or in expanded modes when the EME bit is set. Therefore, these accesses will be echoed externally. NOTE It is unwise to write PORTE and DDRE as a word access. If you are changing port E pins from being inputs to outputs, the data may have extra transitions during the write. It is best to initialize PORTE before enabling as outputs. NOTE To ensure that you read the value present on the PORTE pins, always wait at least one cycle after writing to the DDRE register before reading from the PORTE register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 521 Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.7 Data Direction Register E (DDRE) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 6 5 4 3 Bit 2 0 0 0 0 = Unimplemented or Reserved Figure 18-11. Data Direction Register E (DDRE) Read: Anytime when register is in the map Write: Anytime when register is in the map Data direction register E is associated with port E. For bits in port E that are configured as general-purpose I/O lines, DDRE determines the primary direction of each of these pins. A 1 causes the associated bit to be an output and a 0 causes the associated bit to be an input. Port E bit 1 (associated with IRQ) and bit 0 (associated with XIRQ) cannot be configured as outputs. Port E, bits 1 and 0, can be read regardless of whether the alternate interrupt function is enabled. The value in a DDR bit also affects the source of data for reads of the corresponding PORTE register. If the DDR bit is 0 (input) the buffered pin input state is read. If the DDR bit is 1 (output) the associated port data register bit state is read. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. Also, it is not in the map in expanded modes while the EME control bit is set. Table 18-5. DDRE Field Descriptions Field 7:2 DDRE Description Data Direction Port E 0 Configure the corresponding I/O pin as an input 1 Configure the corresponding I/O pin as an output Note: It is unwise to write PORTE and DDRE as a word access. If you are changing port E pins from inputs to outputs, the data may have extra transitions during the write. It is best to initialize PORTE before enabling as outputs. MC9S12KG128 Data Sheet, Rev. 1.15 522 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.8 Port E Assignment Register (PEAR) 7 6 5 4 3 2 1 0 R NOACCE W Reset Special Single Chip Special Test Peripheral Emulation Expanded Narrow Emulation Expanded Wide Normal Single Chip Normal Expanded Narrow Normal Expanded Wide 0 0 0 1 1 0 0 0 0 PIPOE NECLK LSTRE RDWE 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 1 0 0 0 0 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-12. Port E Assignment Register (PEAR) Read: Anytime (provided this register is in the map). Write: Each bit has specific write conditions. Please refer to the descriptions of each bit on the following pages. Port E serves as general-purpose I/O or as system and bus control signals. The PEAR register is used to choose between the general-purpose I/O function and the alternate control functions. When an alternate control function is selected, the associated DDRE bits are overridden. 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, only the E clock is configured for its alternate bus control function and the other bits of port E are configured for general-purpose I/O. As the reset vector is located in external memory, the E clock is required for this access. R/W is only needed by the system when there are external writable resources. 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 test and emulation modes, IPIPE1, IPIPE0, E, LSTRB, and R/W are configured out of reset as bus control signals. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 523 Chapter 18 Multiplexed External Bus Interface (MEBIV3) Table 18-6. PEAR Field Descriptions Field 7 NOACCE Description CPU No Access Output Enable Normal: write once Emulation: write never Special: write anytime 1 The associated pin (port E, bit 7) is general-purpose I/O. 0 The associated pin (port E, bit 7) is output and indicates whether the cycle is a CPU free cycle. This bit has no effect in single-chip or special peripheral modes. Pipe Status Signal Output Enable Normal: write once Emulation: write never Special: write anytime. 0 The associated pins (port E, bits 6:5) are general-purpose I/O. 1 The associated pins (port E, bits 6:5) are outputs and indicate the state of the instruction queue This bit has no effect in single-chip or special peripheral modes. No External E Clock Normal and special: write anytime Emulation: write never 0 The associated pin (port E, bit 4) is the external E clock pin. External E clock is free-running if ESTR = 0 1 The associated pin (port E, bit 4) is a general-purpose I/O pin. External E clock is available as an output in all modes. Low Strobe (LSTRB) Enable Normal: write once Emulation: write never Special: write anytime. 0 The associated pin (port E, bit 3) is a general-purpose I/O pin. 1 The associated pin (port E, bit 3) is configured as the LSTRB bus control output. If BDM tagging is enabled, TAGLO is multiplexed in on the rising edge of ECLK and LSTRB is driven out on the falling edge of ECLK. This bit has no effect in single-chip, peripheral, or normal expanded narrow modes. Note: LSTRB is used during external writes. After reset in normal expanded mode, LSTRB is disabled to provide an extra I/O pin. If LSTRB is needed, it should be enabled before any external writes. External reads do not normally need LSTRB because all 16 data bits can be driven even if the system only needs 8 bits of data. Read/Write Enable Normal: write once Emulation: write never Special: write anytime 0 The associated pin (port E, bit 2) is a general-purpose I/O pin. 1 The associated pin (port E, bit 2) is configured as the R/W pin This bit has no effect in single-chip or special peripheral modes. Note: R/W is used for external writes. After reset in normal expanded mode, R/W is disabled to provide an extra I/O pin. If R/W is needed it should be enabled before any external writes. 5 PIPOE 4 NECLK 3 LSTRE 2 RDWE MC9S12KG128 Data Sheet, Rev. 1.15 524 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.9 Mode Register (MODE) 7 6 5 4 3 2 1 0 R MODC W Reset Special Single Chip Emulation Expanded Narrow Special Test Emulation Expanded Wide Normal Single Chip Normal Expanded Narrow Peripheral Normal Expanded Wide 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 MODB MODA 0 IVIS 0 EMK EME 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 1 0 1 0 0 0 0 = Unimplemented or Reserved Figure 18-13. Mode Register (MODE) Read: Anytime (provided this register is in the map). Write: Each bit has specific write conditions. Please refer to the descriptions of each bit on the following pages. The MODE register is used to establish the operating mode and other miscellaneous functions (i.e., internal visibility and emulation of port E and K). In special peripheral mode, this register is not accessible but it is reset as shown to system configuration features. Changes to bits in the MODE register are delayed one cycle after the write. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 525 Chapter 18 Multiplexed External Bus Interface (MEBIV3) Table 18-7. MODE Field Descriptions Field 7:5 MOD[C:A] Description Mode Select Bits — These bits indicate the current operating mode. If MODA = 1, then MODC, MODB, and MODA are write never. If MODC = MODA = 0, then MODC, MODB, and MODA are writable with the exception that you cannot change to or from special peripheral mode If MODC = 1, MODB = 0, and MODA = 0, then MODC is write never. MODB and MODA are write once, except that you cannot change to special peripheral mode. From normal single-chip, only normal expanded narrow and normal expanded wide modes are available. See Table 18-8 and Table 18-16. 3 IVIS Internal Visibility (for both read and write accesses) — This bit determines whether internal accesses generate a bus cycle that is visible on the external bus. Normal: write once Emulation: write never Special: write anytime 0 No visibility of internal bus operations on external bus. 1 Internal bus operations are visible on external bus. Emulate Port K Normal: write once Emulation: write never Special: write anytime 0 PORTK and DDRK are in the memory map so port K can be used for general-purpose I/O. 1 If in any expanded mode, PORTK and DDRK are removed from the memory map. In single-chip modes, PORTK and DDRK are always in the map regardless of the state of this bit. In special peripheral mode, PORTK and DDRK are never in the map regardless of the state of this bit. Emulate Port E Normal and Emulation: write never Special: write anytime 0 PORTE and DDRE are in the memory map so port E can be used for general-purpose I/O. 1 If in any expanded mode or special peripheral mode, PORTE and DDRE are removed from the memory map. Removing the registers from the map allows the user to emulate the function of these registers externally. In single-chip modes, PORTE and DDRE are always in the map regardless of the state of this bit. 1 EMK 0 EME MC9S12KG128 Data Sheet, Rev. 1.15 526 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) Table 18-8. MODC, MODB, and MODA Write Capability1 MODC 0 0 0 0 1 MODB 0 0 1 1 0 MODA 0 1 0 1 0 Mode Special single chip Emulation narrow Special test Emulation wide Normal single chip MODx Write Capability MODC, MODB, and MODA write anytime but not to 1102 No write MODC, MODB, and MODA write anytime but not to 110(2) No write MODC write never, MODB and MODA write once but not to 110 No write No write No write 1 1 1 1 2 0 1 1 1 0 1 Normal expanded narrow Special peripheral Normal expanded wide No writes to the MOD bits are allowed while operating in a secure mode. For more details, refer to the device overview chapter. If you are in a special single-chip or special test mode and you write to this register, changing to normal single-chip mode, then one allowed write to this register remains. If you write to normal expanded or emulation mode, then no writes remain. 18.3.2.10 Pull Control Register (PUCR) 7 6 5 4 3 2 1 0 R PUPKE W Reset1 1 0 0 PUPEE 0 0 PUPBE PUPAE 0 0 0 1 0 0 0 NOTES: 1. The default value of this parameter is shown. Please refer to the device overview chapter to determine the actual reset state of this register. = Unimplemented or Reserved Figure 18-14. Pull Control Register (PUCR) Read: Anytime (provided this register is in the map). Write: Anytime (provided this register is in the map). This register is used to select pull resistors for the pins associated with the core ports. Pull resistors are assigned on a per-port basis and apply to any pin in the corresponding port that is currently configured as an input. The polarity of these pull resistors is determined by chip integration. Please refer to the device overview chapter to determine the polarity of these resistors. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 527 Chapter 18 Multiplexed External Bus Interface (MEBIV3) This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. NOTE These bits have no effect when the associated pin(s) are outputs. (The pull resistors are inactive.) Table 18-9. PUCR Field Descriptions Field 7 PUPKE 4 PUPEE Pull resistors Port K Enable 0 Port K pull resistors are disabled. 1 Enable pull resistors for port K input pins. Pull resistors Port E Enable 0 Port E pull resistors on bits 7, 4:0 are disabled. 1 Enable pull resistors for port E input pins bits 7, 4:0. Note: Pins 5 and 6 of port E have pull resistors which are only enabled during reset. This bit has no effect on these pins. Pull resistors Port B Enable 0 Port B pull resistors are disabled. 1 Enable pull resistors for all port B input pins. Pull resistors Port A Enable 0 Port A pull resistors are disabled. 1 Enable pull resistors for all port A input pins. Description 1 PUPBE 0 PUPAE 18.3.2.11 Reduced Drive Register (RDRIV) 7 6 5 4 3 2 1 0 R RDRK W Reset 0 0 0 RDPE 0 0 RDPB RDPA 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-15. Reduced Drive Register (RDRIV) Read: Anytime (provided this register is in the map) Write: Anytime (provided this register is in the map) This register is used to select reduced drive for the pins associated with the core ports. This gives reduced power consumption and reduced RFI with a slight increase in transition time (depending on loading). This feature would be used on ports which have a light loading. The reduced drive function is independent of which function is being used on a particular port. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. MC9S12KG128 Data Sheet, Rev. 1.15 528 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) Table 18-10. RDRIV Field Descriptions Field 7 RDRK 4 RDPE 1 RDPB 0 RDPA Description Reduced Drive of Port K 0 All port K output pins have full drive enabled. 1 All port K output pins have reduced drive enabled. Reduced Drive of Port E 0 All port E output pins have full drive enabled. 1 All port E output pins have reduced drive enabled. Reduced Drive of Port B 0 All port B output pins have full drive enabled. 1 All port B output pins have reduced drive enabled. Reduced Drive of Ports A 0 All port A output pins have full drive enabled. 1 All port A output pins have reduced drive enabled. 18.3.2.12 External Bus Interface Control Register (EBICTL) 7 6 5 4 3 2 1 0 R W Reset: Peripheral All other modes 0 0 0 0 0 0 0 ESTR 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 = Unimplemented or Reserved Figure 18-16. External Bus Interface Control Register (EBICTL) Read: Anytime (provided this register is in the map) Write: Refer to individual bit descriptions below The EBICTL register is used to control miscellaneous functions (i.e., stretching of external E clock). This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. Table 18-11. EBICTL Field Descriptions Field 0 ESTR Description E Clock Stretches — This control bit determines whether the E clock behaves as a simple free-running clock or as a bus control signal that is active only for external bus cycles. Normal and Emulation: write once Special: write anytime 0 E never stretches (always free running). 1 E stretches high during stretched external accesses and remains low during non-visible internal accesses. This bit has no effect in single-chip modes. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 529 Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.13 Reserved Register 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-17. Reserved Register This register location is not used (reserved). All bits in this register return logic 0s when read. Writes to this register have no effect. This register is not in the on-chip memory map in expanded and special peripheral modes. Therefore, these accesses will be echoed externally. 18.3.2.14 IRQ Control Register (IRQCR) 7 6 5 4 3 2 1 0 R IRQE W Reset 0 1 IRQEN 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 18-18. IRQ Control Register (IRQCR) Read: See individual bit descriptions below Write: See individual bit descriptions below Table 18-12. IRQCR Field Descriptions Field 7 IRQE Description IRQ Select Edge Sensitive Only Special modes: read or write anytime Normal and Emulation modes: read anytime, write once 0 IRQ configured for low level recognition. 1 IRQ configured to respond only to falling edges. Falling edges on the IRQ pin will be detected anytime IRQE = 1 and will be cleared only upon a reset or the servicing of the IRQ interrupt. External IRQ Enable Normal, emulation, and special modes: read or write anytime 0 External IRQ pin is disconnected from interrupt logic. 1 External IRQ pin is connected to interrupt logic. Note: When IRQEN = 0, the edge detect latch is disabled. 6 IRQEN MC9S12KG128 Data Sheet, Rev. 1.15 530 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.15 Port K Data Register (PORTK) 7 6 5 4 3 2 1 0 R Bit 7 W Reset Alternate Pin Function 0 ECS 0 XCS 0 XAB19 0 XAB18 0 XAB17 0 XAB16 0 XAB15 0 XAB14 6 5 4 3 2 1 Bit 0 Figure 18-19. Port K Data Register (PORTK) Read: Anytime Write: Anytime This port is associated with the internal memory expansion emulation pins. When the port is not enabled to emulate the internal memory expansion, the port pins are used as general-purpose I/O. When port K is operating as a general-purpose I/O port, DDRK determines the primary direction for each port K pin. A 1 causes the associated port pin to be an output and a 0 causes the associated pin to be a high-impedance input. The value in a DDR bit also affects the source of data for reads of the corresponding PORTK register. If the DDR bit is 0 (input) the buffered pin input is read. If the DDR bit is 1 (output) the output of the port data register is read. This register is not in the map in peripheral or expanded modes while the EMK control bit in MODE register is set. Therefore, these accesses will be echoed externally. When inputs, these pins can be selected to be high impedance or pulled up, based upon the state of the PUPKE bit in the PUCR register. Table 18-13. PORTK Field Descriptions Field 7 Port K, Bit 7 Description Port K, Bit 7 — This bit is used as an emulation chip select signal for the emulation of the internal memory expansion, or as general-purpose I/O, depending upon the state of the EMK bit in the MODE register. While this bit is used as a chip select, the external bit will return to its de-asserted state (VDD) for approximately 1/4 cycle just after the negative edge of ECLK, unless the external access is stretched and ECLK is free-running (ESTR bit in EBICTL = 0). See the MMC block description chapter for additional details on when this signal will be active. Port K, Bit 6 — This bit is used as an external chip select signal for most external accesses that are not selected by ECS (see the MMC block description chapter for more details), depending upon the state the of the EMK bit in the MODE register. While this bit is used as a chip select, the external pin will return to its deasserted state (VDD) for approximately 1/4 cycle just after the negative edge of ECLK, unless the external access is stretched and ECLK is free-running (ESTR bit in EBICTL = 0). 6 Port K, Bit 6 5:0 Port K, Bits 5:0 — These six bits are used to determine which FLASH/ROM or external memory array page Port K, Bits 5:0 is being accessed. They can be viewed as expanded addresses XAB19–XAB14 of the 20-bit address used to access up to1M byte internal FLASH/ROM or external memory array. Alternatively, these bits can be used for general-purpose I/O depending upon the state of the EMK bit in the MODE register. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 531 Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.3.2.16 Port K Data Direction Register (DDRK) 7 6 5 4 3 2 1 0 R Bit 7 W Reset 0 0 0 0 0 0 0 0 6 5 4 3 2 1 Bit 0 Figure 18-20. Port K Data Direction Register (DDRK) Read: Anytime Write: Anytime This register determines the primary direction for each port K pin configured as general-purpose I/O. This register is not in the map in peripheral or expanded modes while the EMK control bit in MODE register is set. Therefore, these accesses will be echoed externally. Table 18-14. EBICTL Field Descriptions Field 7:0 DDRK Description Data Direction Port K Bits 0 Associated pin is a high-impedance input 1 Associated pin is an output Note: It is unwise to write PORTK and DDRK as a word access. If you are changing port K pins from inputs to outputs, the data may have extra transitions during the write. It is best to initialize PORTK before enabling as outputs. Note: To ensure that you read the correct value from the PORTK pins, always wait at least one cycle after writing to the DDRK register before reading from the PORTK register. 18.4 18.4.1 Functional Description Detecting Access Type from External Signals The external signals LSTRB, R/W, and AB0 indicate the type of bus access that is taking place. Accesses to the internal RAM module are the only type of access that would produce LSTRB = AB0 = 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. This is summarized in Table 18-15. Table 18-15. Access Type vs. Bus Control Pins LSTRB 1 0 1 0 0 AB0 0 1 0 1 0 R/W 1 1 0 0 1 Type of Access 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 MC9S12KG128 Data Sheet, Rev. 1.15 532 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) Table 18-15. Access Type vs. Bus Control Pins LSTRB 1 0 1 AB0 1 0 1 R/W 1 0 0 Type of Access 16-bit read of an odd address (low/high data swapped) 16-bit write to an even address 16-bit write to an odd address (low/high data swapped) 18.4.2 Stretched Bus Cycles In order to allow fast internal bus cycles to coexist in a system with slower external memory resources, the HCS12 supports the concept of stretched bus cycles (module timing reference clocks for timers and baud rate generators are not affected by this stretching). Control bits in the MISC register in the MMC sub-block of the core specify the amount of stretch (0, 1, 2, or 3 periods of the internal bus-rate clock). While stretching, the CPU state machines are all held in their current state. At this point in the CPU bus cycle, write data would already be driven onto the data bus so the length of time write data is valid is extended in the case of a stretched bus cycle. Read data would not be captured by the system until the E clock falling edge. In the case of a stretched bus cycle, read data is not required until the specified setup time before the falling edge of the stretched E clock. The chip selects, and R/W signals remain valid during the period of stretching (throughout the stretched E high time). NOTE The address portion of the bus cycle is not stretched. 18.4.3 Modes of Operation The operating mode out of reset is determined by the states of the MODC, MODB, and MODA pins during reset (Table 18-16). The MODC, MODB, and MODA bits in the MODE register show the current operating mode and provide limited mode switching during operation. The states of the MODC, MODB, and MODA pins are latched into these bits on the rising edge of the reset signal. Table 18-16. Mode Selection MODC 0 0 0 0 1 1 1 1 MODB 0 0 1 1 0 0 1 1 MODA 0 1 0 1 0 1 0 1 Mode Description Special Single Chip, BDM allowed and ACTIVE. BDM is allowed in all other modes but a serial command is required to make BDM active. Emulation Expanded Narrow, BDM allowed Special Test (Expanded Wide), BDM allowed Emulation Expanded Wide, BDM allowed Normal Single Chip, BDM allowed Normal Expanded Narrow, BDM allowed Peripheral; BDM allowed but bus operations would cause bus conflicts (must not be used) Normal Expanded Wide, BDM allowed MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 533 Chapter 18 Multiplexed External Bus Interface (MEBIV3) There are two basic types of operating modes: 1. Normal modes: Some registers and bits are protected against accidental changes. 2. Special modes: Allow greater access to protected control registers and bits for special purposes such as testing. 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. Some aspects of Port E are not mode dependent. Bit 1 of Port E is a general purpose input or the IRQ interrupt input. IRQ can be enabled by bits in the CPU’s condition codes register but it is inhibited at reset so this pin is initially configured as a simple input with a pull-up. Bit 0 of Port E is a general purpose input or the XIRQ interrupt input. XIRQ can be enabled by bits in the CPU’s condition codes register but it is inhibited at reset so this pin is initially configured as a simple input with a pull-up. The ESTR bit in the EBICTL register is set to one by reset in any user mode. This assures that the reset vector can be fetched even if it is located in an external slow memory device. The PE6/MODB/IPIPE1 and PE5/MODA/IPIPE0 pins act as high-impedance mode select inputs during reset. The following paragraphs discuss the default bus setup and describe which aspects of the bus can be changed after reset on a per mode basis. 18.4.3.1 Normal Operating Modes 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. 18.4.3.1.1 Normal Single-Chip Mode There is no external expansion bus in this mode. All pins of Ports A, B and E are configured as general purpose I/O pins Port E bits 1 and 0 are available as general purpose input only pins with internal pull resistors enabled. All other pins of Port E are bidirectional I/O pins that are initially configured as high-impedance inputs with internal pull resistors enabled. Ports A and B are configured as high-impedance inputs with their internal pull resistors disabled. The pins associated with Port E bits 6, 5, 3, and 2 cannot be configured for their alternate functions IPIPE1, IPIPE0, LSTRB, and R/W while the MCU is in single chip modes. In single chip modes, the associated control bits PIPOE, LSTRE, and RDWE are reset to zero. Writing the opposite state into them in single chip mode does not change the operation of the associated Port E pins. In normal single chip mode, the MODE register is writable one time. This allows a user program to change the bus mode to narrow or wide expanded mode and/or turn on visibility of internal accesses. Port E, bit 4 can be configured for a free-running E clock output by clearing NECLK=0. Typically the only use for an E clock output while the MCU is in single chip modes would be to get a constant speed clock for use in the external application system. MC9S12KG128 Data Sheet, Rev. 1.15 534 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.4.3.1.2 Normal Expanded Wide Mode In expanded wide modes, Ports A and B are configured as a 16-bit multiplexed address and data bus and Port E bit 4 is configured as the E clock output signal. These signals allow external memory and peripheral devices to be interfaced to the MCU. Port E pins other than PE4/ECLK are configured as general purpose I/O pins (initially high-impedance inputs with internal pull resistors enabled). Control bits PIPOE, NECLK, LSTRE, and RDWE in the PEAR register can be used to configure Port E pins to act as bus control outputs instead of general purpose I/O pins. It is possible to enable the pipe status signals on Port E bits 6 and 5 by setting the PIPOE bit in PEAR, but it would be unusual to do so in this mode. Development systems where pipe status signals are monitored would typically use the special variation of this mode. The Port E bit 2 pin can be reconfigured as the R/W bus control signal by writing “1” to the RDWE bit in PEAR. If the expanded system includes external devices that can be written, such as RAM, the RDWE bit would need to be set before any attempt to write to an external location. If there are no writable resources in the external system, PE2 can be left as a general purpose I/O pin. The Port E bit 3 pin can be reconfigured as the LSTRB bus control signal by writing “1” to the LSTRE bit in PEAR. The default condition of this pin is a general purpose input because the LSTRB function is not needed in all expanded wide applications. The Port E bit 4 pin is initially configured as ECLK output with stretch. The E clock output function depends upon the settings of the NECLK bit in the PEAR register, the IVIS bit in the MODE register and the ESTR bit in the EBICTL register. The E clock is available for use in external select decode logic or as a constant speed clock for use in the external application system. 18.4.3.1.3 Normal Expanded Narrow Mode This mode is used for lower cost production systems that use 8-bit wide external EPROMs or RAMs. Such systems take extra bus cycles to access 16-bit locations but this may be preferred over the extra cost of additional external memory devices. Ports A and B are configured as a 16-bit address bus and Port A is multiplexed with data. Internal visibility is not available in this mode because the internal cycles would need to be split into two 8-bit cycles. Since the PEAR register can only be written one time in this mode, use care to set all bits to the desired states during the single allowed write. The PE3/LSTRB pin is always a general purpose I/O pin in normal expanded narrow mode. Although it is possible to write the LSTRE bit in PEAR to “1” in this mode, the state of LSTRE is overridden and Port E bit 3 cannot be reconfigured as the LSTRB output. It is possible to enable the pipe status signals on Port E bits 6 and 5 by setting the PIPOE bit in PEAR, but it would be unusual to do so in this mode. LSTRB would also be needed to fully understand system activity. Development systems where pipe status signals are monitored would typically use special expanded wide mode or occasionally special expanded narrow mode. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 535 Chapter 18 Multiplexed External Bus Interface (MEBIV3) The PE4/ECLK pin is initially configured as ECLK output with stretch. The E clock output function depends upon the settings of the NECLK bit in the PEAR register, the IVIS bit in the MODE register and the ESTR bit in the EBICTL register. In normal expanded narrow mode, the E clock is available for use in external select decode logic or as a constant speed clock for use in the external application system. The PE2/R/W pin is initially configured as a general purpose input with an internal pull resistor enabled but this pin can be reconfigured as the R/W bus control signal by writing “1” to the RDWE bit in PEAR. If the expanded narrow system includes external devices that can be written such as RAM, the RDWE bit would need to be set before any attempt to write to an external location. If there are no writable resources in the external system, PE2 can be left as a general purpose I/O pin. 18.4.3.1.4 Emulation Expanded Wide Mode In expanded wide modes, Ports A and B are configured as a 16-bit multiplexed address and data bus and Port E provides bus control and status signals. These signals allow external memory and peripheral devices to be interfaced to the MCU. These signals can also be used by a logic analyzer to monitor the progress of application programs. The bus control related pins in Port E (PE7/NOACC, PE6/MODB/IPIPE1, PE5/MODA/IPIPE0, PE4/ECLK, PE3/LSTRB/TAGLO, and PE2/R/W) are all configured to serve their bus control output functions rather than general purpose I/O. Notice that writes to the bus control enable bits in the PEAR register in emulation mode are restricted. 18.4.3.1.5 Emulation Expanded Narrow Mode Expanded narrow modes are intended to allow connection of single 8-bit external memory devices for lower cost systems that do not need the performance of a full 16-bit external data bus. Accesses to internal resources that have been mapped external (i.e. PORTA, PORTB, DDRA, DDRB, PORTE, DDRE, PEAR, PUCR, RDRIV) will be accessed with a 16-bit data bus on Ports A and B. Accesses of 16-bit external words to addresses which are normally mapped external will be broken into two separate 8-bit accesses using Port A as an 8-bit data bus. Internal operations continue to use full 16-bit data paths. They are only visible externally as 16-bit information if IVIS=1. Ports A and B are configured as multiplexed address and data output ports. During external accesses, address A15, data D15 and D7 are associated with PA7, address A0 is associated with PB0 and data D8 and D0 are associated with PA0. During internal visible accesses and accesses to internal resources that have been mapped external, address A15 and data D15 is associated with PA7 and address A0 and data D0 is associated with PB0. The bus control related pins in Port E (PE7/NOACC, PE6/MODB/IPIPE1, PE5/MODA/IPIPE0, PE4/ECLK, PE3/LSTRB/TAGLO, and PE2/R/W) are all configured to serve their bus control output functions rather than general purpose I/O. Notice that writes to the bus control enable bits in the PEAR register in emulation mode are restricted. The main difference between special modes and normal modes is that some of the bus control and system control signals cannot be written in emulation modes. MC9S12KG128 Data Sheet, Rev. 1.15 536 Freescale Semiconductor Chapter 18 Multiplexed External Bus Interface (MEBIV3) 18.4.3.2 Special Operating Modes There are two special operating modes that correspond to normal operating modes. These operating modes are commonly used in factory testing and system development. 18.4.3.2.1 Special Single-Chip Mode When the MCU is reset in this mode, the background debug mode is enabled and active. The MCU does not fetch the reset vector and execute application code as it would in other modes. Instead the active background mode is in control of CPU execution and BDM firmware is waiting for additional serial commands through the BKGD pin. When a serial command instructs the MCU to return to normal execution, the system will be configured as described below unless the reset states of internal control registers have been changed through background commands after the MCU was reset. There is no external expansion bus after reset in this mode. Ports A and B are initially simple bidirectional I/O pins that are configured as high-impedance inputs with internal pull resistors disabled; however, writing to the mode select bits in the MODE register (which is allowed in special modes) can change this after reset. All of the Port E pins (except PE4/ECLK) are initially configured as general purpose high-impedance inputs with internal pull resistors enabled. PE4/ECLK is configured as the E clock output in this mode. The pins associated with Port E bits 6, 5, 3, and 2 cannot be configured for their alternate functions IPIPE1, IPIPE0, LSTRB, and R/W while the MCU is in single chip modes. In single chip modes, the associated control bits PIPOE, LSTRE and RDWE are reset to zero. Writing the opposite value into these bits in single chip mode does not change the operation of the associated Port E pins. Port E, bit 4 can be configured for a free-running E clock output by clearing NECLK=0. Typically the only use for an E clock output while the MCU is in single chip modes would be to get a constant speed clock for use in the external application system. 18.4.3.2.2 Special Test Mode In expanded wide modes, Ports A and B are configured as a 16-bit multiplexed address and data bus and Port E provides bus control and status signals. In special test mode, the write protection of many control bits is lifted so that they can be thoroughly tested without needing to go through reset. 18.4.3.3 Test Operating Mode There is a test operating mode in which an external master, such as an I.C. tester, can control the on-chip peripherals. 18.4.3.3.1 Peripheral Mode This mode is intended for factory testing of the MCU. In this mode, the CPU is inactive and an external (tester) bus master drives address, data and bus control signals in through Ports A, B and E. In effect, the whole MCU acts as if it was a peripheral under control of an external CPU. This allows faster testing of on-chip memory and peripherals than previous testing methods. Since the mode control register is not accessible in peripheral mode, the only way to change to another mode is to reset the MCU into a different MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 537 Chapter 18 Multiplexed External Bus Interface (MEBIV3) mode. 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. 18.4.4 Internal Visibility Internal visibility is available when the MCU is operating in expanded wide modes or emulation narrow mode. It is not available in single-chip, peripheral or normal expanded narrow modes. Internal visibility is enabled by setting the IVIS bit in the MODE register. If an internal access is made while E, R/W, and LSTRB are configured as bus control outputs and internal visibility is off (IVIS=0), E will remain low for the cycle, R/W will remain high, and address, data and the LSTRB pins will remain at their previous state. When internal visibility is enabled (IVIS=1), certain internal cycles will be blocked from going external. During cycles when the BDM is selected, R/W will remain high, data will maintain its previous state, and address and LSTRB pins will be updated with the internal value. During CPU no access cycles when the BDM is not driving, R/W will remain high, and address, data and the LSTRB pins will remain at their previous state. NOTE When the system is operating in a secure mode, internal visibility is not available (i.e., IVIS = 1 has no effect). Also, the IPIPE signals will not be visible, regardless of operating mode. IPIPE1–IPIPE0 will display 0es if they are enabled. In addition, the MOD bits in the MODE control register cannot be written. 18.4.5 Low-Power Options The MEBI does not contain any user-controlled options for reducing power consumption. The operation of the MEBI in low-power modes is discussed in the following subsections. 18.4.5.1 Operation in Run Mode The MEBI does not contain any options for reducing power in run mode; however, the external addresses are conditioned to reduce power in single-chip modes. Expanded bus modes will increase power consumption. 18.4.5.2 Operation in Wait Mode The MEBI does not contain any options for reducing power in wait mode. 18.4.5.3 Operation in Stop Mode The MEBI will cease to function after execution of a CPU STOP instruction. MC9S12KG128 Data Sheet, Rev. 1.15 538 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) 19.1 Introduction This section describes the functionality of the module mapping control (MMC) sub-block of the S12 core platform. The block diagram of the MMC is shown in Figure 19-1. MMC SECURE BDM_UNSECURE STOP, WAIT SECURITY MMC_SECURE ADDRESS DECODE READ & WRITE ENABLES CLOCKS, RESET MODE INFORMATION INTERNAL MEMORY EXPANSION REGISTERS PORT K INTERFACE MEMORY SPACE SELECT(S) PERIPHERAL SELECT EBI ALTERNATE ADDRESS BUS EBI ALTERNATE WRITE DATA BUS EBI ALTERNATE READ DATA BUS ALTERNATE ADDRESS BUS (BDM) CPU ADDRESS BUS CPU READ DATA BUS CPU WRITE DATA BUS CPU CONTROL BUS CONTROL ALTERNATE WRITE DATA BUS (BDM) ALTERNATE READ DATA BUS (BDM) CORE SELECT (S) Figure 19-1. MMC Block Diagram The MMC is the sub-module which controls memory map assignment and selection of internal resources and external space. Internal buses between the core and memories and between the core and peripherals is controlled in this module. The memory expansion is generated in this module. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 539 Chapter 19 Module Mapping Control (MMCV4) 19.1.1 • • • • • • • • • • • Features Registers for mapping of address space for on-chip RAM, EEPROM, and FLASH (or ROM) memory blocks and associated registers Memory mapping control and selection based upon address decode and system operating mode Core address bus control Core data bus control and multiplexing Core security state decoding Emulation chip select signal generation (ECS) External chip select signal generation (XCS) Internal memory expansion External stretch and ROM mapping control functions via the MISC register Reserved registers for test purposes Configurable system memory options defined at integration of core into the system-on-a-chip (SoC). 19.1.2 Modes of Operation Some of the registers operate differently depending on the mode of operation (i.e., normal expanded wide, special single chip, etc.). This is best understood from the register descriptions. 19.2 External Signal Description All interfacing with the MMC sub-block is done within the core, it has no external signals. 19.3 Memory Map and Register Definition A summary of the registers associated with the MMC sub-block is shown in Figure 19-2. Detailed descriptions of the registers and bits are given in the subsections that follow. 19.3.1 Module Memory Map Table 19-1. MMC Memory Map Address Offset Register Initialization of Internal RAM Position Register (INITRM) Initialization of Internal Registers Position Register (INITRG) Initialization of Internal EEPROM Position Register (INITEE) Miscellaneous System Control Register (MISC) Reserved . . . . Access R/W R/W R/W R/W — — MC9S12KG128 Data Sheet, Rev. 1.15 540 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) Table 19-1. MMC Memory Map (continued) Address Offset Reserved . . Memory Size Register 0 (MEMSIZ0) Memory Size Register 1 (MEMSIZ1) . . . . Program Page Index Register (PPAGE) Reserved R/W — . . Register Access — — R R MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 541 Chapter 19 Module Mapping Control (MMCV4) 19.3.2 Name INITRM Register Descriptions Bit 7 R W RAM15 0 6 RAM14 5 RAM13 4 RAM12 3 RAM11 2 0 1 0 Bit 0 RAMHAL 0 INITRG R W REG14 REG13 REG12 REG11 0 0 INITEE R W EE15 0 EE14 0 EE13 0 EE12 0 EE11 0 0 EEON MISC R W EXSTR1 3 EXSTR0 2 ROMHM 1 ROMON Bit 0 MTSTO R W Bit 7 6 5 4 MTST1 R W Bit 7 6 5 4 3 2 1 Bit 0 MEMSIZ0 R REG_SW0 W 0 EEP_SW1 EEP_SW0 0 RAM_SW2 RAM_SW1 RAM_SW0 MEMSIZ1 R ROM_SW1 ROM_SW0 W 0 0 0 0 PAG_SW1 PAG_SW0 PPAGE R W 0 0 PIX5 0 PIX4 0 PIX3 0 PIX2 0 PIX1 0 PIX0 0 Reserved R W 0 0 = Unimplemented Figure 19-2. MMC Register Summary 19.3.2.1 Initialization of Internal RAM Position Register (INITRM) 7 6 5 4 3 2 1 0 R RAM15 W Reset 0 0 0 0 1 RAM14 RAM13 RAM12 RAM11 0 0 RAMHAL 0 0 1 = Unimplemented or Reserved Figure 19-3. Initialization of Internal RAM Position Register (INITRM) Read: Anytime MC9S12KG128 Data Sheet, Rev. 1.15 542 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) Write: Once in normal and emulation modes, anytime in special modes NOTE Writes to this register take one cycle to go into effect. This register initializes the position of the internal RAM within the on-chip system memory map. Table 19-2. INITRM Field Descriptions Field Description 7:3 Internal RAM Map Position — These bits determine the upper five bits of the base address for the system’s RAM[15:11] internal RAM array. 0 RAMHAL RAM High-Align — RAMHAL specifies the alignment of the internal RAM array. 0 Aligns the RAM to the lowest address (0x0000) of the mappable space 1 Aligns the RAM to the higher address (0xFFFF) of the mappable space MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 543 Chapter 19 Module Mapping Control (MMCV4) 19.3.2.2 Initialization of Internal Registers Position Register (INITRG) 7 6 5 4 3 2 1 0 R W Reset 0 REG14 0 0 REG13 0 REG12 0 REG11 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 19-4. Initialization of Internal Registers Position Register (INITRG) Read: Anytime Write: Once in normal and emulation modes and anytime in special modes This register initializes the position of the internal registers within the on-chip system memory map. The registers occupy either a 1K byte or 2K byte space and can be mapped to any 2K byte space within the first 32K bytes of the system’s address space. Table 19-3. INITRG Field Descriptions Field Description 6:3 Internal Register Map Position — These four bits in combination with the leading zero supplied by bit 7 of REG[14:11] INITRG determine the upper five bits of the base address for the system’s internal registers (i.e., the minimum base address is 0x0000 and the maximum is 0x7FFF). MC9S12KG128 Data Sheet, Rev. 1.15 544 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) 19.3.2.3 Initialization of Internal EEPROM Position Register (INITEE) 7 6 5 4 3 2 1 0 R EE15 W Reset1 — — — — — EE14 EE13 EE12 EE11 0 0 EEON — — — 1. The reset state of this register is controlled at chip integration. Please refer to the device overview section to determine the actual reset state of this register. = Unimplemented or Reserved Figure 19-5. Initialization of Internal EEPROM Position Register (INITEE) Read: Anytime Write: The EEON bit can be written to any time on all devices. Bits E[11:15] are “write anytime in all modes” on most devices. On some devices, bits E[11:15] are “write once in normal and emulation modes and write anytime in special modes”. See device overview chapter to determine the actual write access rights. NOTE Writes to this register take one cycle to go into effect. This register initializes the position of the internal EEPROM within the on-chip system memory map. Table 19-4. INITEE Field Descriptions Field 7:3 EE[15:11] 0 EEON Description Internal EEPROM Map Position — These bits determine the upper five bits of the base address for the system’s internal EEPROM array. Enable EEPROM — This bit is used to enable the EEPROM memory in the memory map. 0 Disables the EEPROM from the memory map. 1 Enables the EEPROM in the memory map at the address selected by EE[15:11]. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 545 Chapter 19 Module Mapping Control (MMCV4) 19.3.2.4 Miscellaneous System Control Register (MISC) 7 6 5 4 3 2 1 0 R W Reset: Expanded or Emulation Reset: Peripheral or Single Chip Reset: Special Test 0 0 0 0 EXSTR1 EXSTR0 ROMHM ROMON —1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 1. The reset state of this bit is determined at the chip integration level. = Unimplemented or Reserved Figure 19-6. Miscellaneous System Control Register (MISC) Read: Anytime Write: As stated in each bit description NOTE Writes to this register take one cycle to go into effect. This register initializes miscellaneous control functions. Table 19-5. INITEE Field Descriptions Field Description 3:2 External Access Stretch Bits 1 and 0 EXSTR[1:0] Write: once in normal and emulation modes and anytime in special modes This two-bit field determines the amount of clock stretch on accesses to the external address space as shown in Table 19-6. In single chip and peripheral modes these bits have no meaning or effect. 1 ROMHM FLASH EEPROM or ROM Only in Second Half of Memory Map Write: once in normal and emulation modes and anytime in special modes 0 The fixed page(s) of FLASH EEPROM or ROM in the lower half of the memory map can be accessed. 1 Disables direct access to the FLASH EEPROM or ROM in the lower half of the memory map. These physical locations of the FLASH EEPROM or ROM remain accessible through the program page window. ROMON — Enable FLASH EEPROM or ROM Write: once in normal and emulation modes and anytime in special modes This bit is used to enable the FLASH EEPROM or ROM memory in the memory map. 0 Disables the FLASH EEPROM or ROM from the memory map. 1 Enables the FLASH EEPROM or ROM in the memory map. 0 ROMON Table 19-6. External Stretch Bit Definition Stretch Bit EXSTR1 0 0 1 1 Stretch Bit EXSTR0 0 1 0 1 MC9S12KG128 Data Sheet, Rev. 1.15 546 Freescale Semiconductor Number of E Clocks Stretched 0 1 2 3 Chapter 19 Module Mapping Control (MMCV4) 19.3.2.5 Reserved Test Register 0 (MTST0) 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = Unimplemented or Reserved Figure 19-7. Reserved Test Register 0 (MTST0) Read: Anytime Write: No effect — this register location is used for internal test purposes. 19.3.2.6 Reserved Test Register 1 (MTST1) 7 6 5 4 3 2 1 0 R W Reset 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 = Unimplemented or Reserved Figure 19-8. Reserved Test Register 1 (MTST1) Read: Anytime Write: No effect — this register location is used for internal test purposes. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 547 Chapter 19 Module Mapping Control (MMCV4) 19.3.2.7 Memory Size Register 0 (MEMSIZ0) 7 6 5 4 3 2 1 0 R REG_SW0 W Reset — 0 EEP_SW1 EEP_SW0 0 RAM_SW2 RAM_SW1 RAM_SW0 — — — — — — — = Unimplemented or Reserved Figure 19-9. Memory Size Register 0 (MEMSIZ0) Read: Anytime Write: Writes have no effect Reset: Defined at chip integration, see device overview section. The MEMSIZ0 register reflects the state of the register, EEPROM and RAM memory space configuration switches at the core boundary which are configured at system integration. This register allows read visibility to the state of these switches. Table 19-7. MEMSIZ0 Field Descriptions Field 7 REG_SW0 Description Allocated System Register Space 0 Allocated system register space size is 1K byte 1 Allocated system register space size is 2K byte 5:4 Allocated System EEPROM Memory Space — The allocated system EEPROM memory space size is as EEP_SW[1:0] given in Table 19-8. 2 Allocated System RAM Memory Space — The allocated system RAM memory space size is as given in RAM_SW[2:0] Table 19-9. Table 19-8. Allocated EEPROM Memory Space eep_sw1:eep_sw0 00 01 10 11 Allocated EEPROM Space 0K byte 2K bytes 4K bytes 8K bytes Table 19-9. Allocated RAM Memory Space ram_sw2:ram_sw0 000 001 010 011 100 Allocated RAM Space 2K bytes 4K bytes 6K bytes 8K bytes 10K bytes RAM Mappable Region 2K bytes 4K bytes 8K bytes 2 INITRM Bits Used RAM[15:11] RAM[15:12] RAM[15:13] RAM[15:13] RAM[15:14] RAM Reset Base Address1 0x0800 0x0000 0x0800 0x0000 0x1800 8K bytes 16K bytes 2 MC9S12KG128 Data Sheet, Rev. 1.15 548 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) Table 19-9. Allocated RAM Memory Space (continued) ram_sw2:ram_sw0 101 110 111 1 2 Allocated RAM Space 12K bytes 14K bytes 16K bytes RAM Mappable Region 16K bytes 2 16K bytes 2 INITRM Bits Used RAM[15:14] RAM[15:14] RAM[15:14] RAM Reset Base Address1 0x1000 0x0800 0x0000 16K bytes The RAM Reset BASE Address is based on the reset value of the INITRM register, 0x0009. Alignment of the Allocated RAM space within the RAM mappable region is dependent on the value of RAMHAL. NOTE As stated, the bits in this register provide read visibility to the system physical memory space allocations defined at system integration. The actual array size for any given type of memory block may differ from the allocated size. Please refer to the device overview chapter for actual sizes. 19.3.2.8 Memory Size Register 1 (MEMSIZ1) 7 6 5 4 3 2 1 0 R ROM_SW1 W Reset — ROM_SW0 0 0 0 0 PAG_SW1 PAG_SW0 — — — — — — — = Unimplemented or Reserved Figure 19-10. Memory Size Register 1 (MEMSIZ1) Read: Anytime Write: Writes have no effect Reset: Defined at chip integration, see device overview section. The MEMSIZ1 register reflects the state of the FLASH or ROM physical memory space and paging switches at the core boundary which are configured at system integration. This register allows read visibility to the state of these switches. Table 19-10. MEMSIZ0 Field Descriptions Field Description 7:6 Allocated System FLASH or ROM Physical Memory Space — The allocated system FLASH or ROM ROM_SW[1:0] physical memory space is as given in Table 19-11. 1:0 Allocated Off-Chip FLASH or ROM Memory Space — The allocated off-chip FLASH or ROM memory space PAG_SW[1:0] size is as given in Table 19-12. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 549 Chapter 19 Module Mapping Control (MMCV4) Table 19-11. Allocated FLASH/ROM Physical Memory Space rom_sw1:rom_sw0 00 01 10 11 Allocated FLASH or ROM Space 0K byte 16K bytes 48K bytes(1) 64K bytes(1) NOTES: 1. The ROMHM software bit in the MISC register determines the accessibility of the FLASH/ROM memory space. Please refer to Section 19.3.2.8, “Memory Size Register 1 (MEMSIZ1),” for a detailed functional description of the ROMHM bit. Table 19-12. Allocated Off-Chip Memory Options pag_sw1:pag_sw0 00 01 10 11 Off-Chip Space 876K bytes 768K bytes 512K bytes 0K byte On-Chip Space 128K bytes 256K bytes 512K bytes 1M byte NOTE As stated, the bits in this register provide read visibility to the system memory space and on-chip/off-chip partitioning allocations defined at system integration. The actual array size for any given type of memory block may differ from the allocated size. Please refer to the device overview chapter for actual sizes. 19.3.2.9 Program Page Index Register (PPAGE) 7 6 5 4 3 2 1 0 R W Reset1 0 0 PIX5 PIX4 — PIX3 — PIX2 — PIX1 — PIX0 — — — — 1. The reset state of this register is controlled at chip integration. Please refer to the device overview section to determine the actual reset state of this register. = Unimplemented or Reserved Figure 19-11. Program Page Index Register (PPAGE) Read: Anytime Write: Determined at chip integration. Generally it’s: “write anytime in all modes;” on some devices it will be: “write only in special modes.” Check specific device documentation to determine which applies. Reset: Defined at chip integration as either 0x00 (paired with write in any mode) or 0x3C (paired with write only in special modes), see device overview chapter. MC9S12KG128 Data Sheet, Rev. 1.15 550 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) The HCS12 core architecture limits the physical address space available to 64K bytes. The program page index register allows for integrating up to 1M byte of FLASH or ROM into the system by using the six page index bits to page 16K byte blocks into the program page window located from 0x8000 to 0xBFFF as defined in Table 19-14. CALL and RTC instructions have special access to read and write this register without using the address bus. NOTE Normal writes to this register take one cycle to go into effect. Writes to this register using the special access of the CALL and RTC instructions will be complete before the end of the associated instruction. Table 19-13. MEMSIZ0 Field Descriptions Field 5:0 PIX[5:0] Description Program Page Index Bits 5:0 — These page index bits are used to select which of the 64 FLASH or ROM array pages is to be accessed in the program page window as shown in Table 19-14. Table 19-14. Program Page Index Register Bits PIX5 0 0 0 0 . . . . . 1 1 1 1 PIX4 0 0 0 0 . . . . . 1 1 1 1 PIX3 0 0 0 0 . . . . 1 1 1 1 PIX2 0 0 0 0 . . . . . 1 1 1 1 PIX1 0 0 1 1 . . . . . 0 0 1 1 PIX0 0 1 0 1 . . . . . 0 1 0 1 Program Space Selected 16K page 0 16K page 1 16K page 2 16K page 3 . . . . . 16K page 60 16K page 61 16K page 62 16K page 63 19.4 Functional Description The MMC sub-block performs four basic functions of the core operation: bus control, address decoding and select signal generation, memory expansion, and security decoding for the system. Each aspect is described in the following subsections. 19.4.1 Bus Control The MMC controls the address bus and data buses that interface the core with the rest of the system. This includes the multiplexing of the input data buses to the core onto the main CPU read data bus and control MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 551 Chapter 19 Module Mapping Control (MMCV4) of data flow from the CPU to the output address and data buses of the core. In addition, the MMC manages all CPU read data bus swapping operations. 19.4.2 Address Decoding As data flows on the core address bus, the MMC decodes the address information, determines whether the internal core register or firmware space, the peripheral space or a memory register or array space is being addressed and generates the correct select signal. This decoding operation also interprets the mode of operation of the system and the state of the mapping control registers in order to generate the proper select. The MMC also generates two external chip select signals, emulation chip select (ECS) and external chip select (XCS). 19.4.2.1 Select Priority and Mode Considerations Although internal resources such as control registers and on-chip memory have default addresses, each can be relocated by changing the default values in control registers. Normally, I/O addresses, control registers, vector spaces, expansion windows, and on-chip memory are mapped so that their address ranges do not overlap. The MMC will make only one select signal active at any given time. This activation is based upon the priority outlined in Table 19-15. If two or more blocks share the same address space, only the select signal for the block with the highest priority will become active. An example of this is if the registers and the RAM are mapped to the same space, the registers will have priority over the RAM and the portion of RAM mapped in this shared space will not be accessible. The expansion windows have the lowest priority. This means that registers, vectors, and on-chip memory are always visible to a program regardless of the values in the page select registers. Table 19-15. Select Signal Priority Priority Highest ... ... ... ... Lowest Address Space BDM (internal to core) firmware or register space Internal register space RAM memory block EEPROM memory block On-chip FLASH or ROM Remaining external space In expanded modes, all address space not used by internal resources is by default external memory space. The data registers and data direction registers for ports A and B are removed from the on-chip memory map and become external accesses. If the EME bit in the MODE register (see MEBI block description chapter) is set, the data and data direction registers for port E are also removed from the on-chip memory map and become external accesses. In special peripheral mode, the first 16 registers associated with bus expansion are removed from the on-chip memory map (PORTA, PORTB, DDRA, DDRB, PORTE, DDRE, PEAR, MODE, PUCR, RDRIV, and the EBI reserved registers). MC9S12KG128 Data Sheet, Rev. 1.15 552 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) In emulation modes, if the EMK bit in the MODE register (see MEBI block description chapter) is set, the data and data direction registers for port K are removed from the on-chip memory map and become external accesses. 19.4.2.2 Emulation Chip Select Signal When the EMK bit in the MODE register (see MEBI block description chapter) is set, port K bit 7 is used as an active-low emulation chip select signal, ECS. This signal is active when the system is in emulation mode, the EMK bit is set and the FLASH or ROM space is being addressed subject to the conditions outlined in Section 19.4.3.2, “Extended Address (XAB19:14) and ECS Signal Functionality.” When the EMK bit is clear, this pin is used for general purpose I/O. 19.4.2.3 External Chip Select Signal When the EMK bit in the MODE register (see MEBI block description chapter) is set, port K bit 6 is used as an active-low external chip select signal, XCS. This signal is active only when the ECS signal described above is not active and when the system is addressing the external address space. Accesses to unimplemented locations within the register space or to locations that are removed from the map (i.e., ports A and B in expanded modes) will not cause this signal to become active. When the EMK bit is clear, this pin is used for general purpose I/O. 19.4.3 Memory Expansion The HCS12 core architecture limits the physical address space available to 64K bytes. The program page index register allows for integrating up to 1M byte of FLASH or ROM into the system by using the six page index bits to page 16K byte blocks into the program page window located from 0x8000 to 0xBFFF in the physical memory space. The paged memory space can consist of solely on-chip memory or a combination of on-chip and off-chip memory. This partitioning is configured at system integration through the use of the paging configuration switches (pag_sw1:pag_sw0) at the core boundary. The options available to the integrator are as given in Table 19-16 (this table matches Table 19-12 but is repeated here for easy reference). Table 19-16. Allocated Off-Chip Memory Options pag_sw1:pag_sw0 00 01 10 11 Off-Chip Space 876K bytes 768K bytes 512K bytes 0K byte On-Chip Space 128K bytes 256K bytes 512K bytes 1M byte Based upon the system configuration, the program page window will consider its access to be either internal or external as defined in Table 19-17. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 553 Chapter 19 Module Mapping Control (MMCV4) Table 19-17. External/Internal Page Window Access pag_sw1:pag_sw0 00 Partitioning 876K off-Chip, 128K on-Chip 768K off-chip, 256K on-chip 512K off-chip, 512K on-chip 0K off-chip, 1M on-chip PIX5:0 Value 0x0000–0x0037 0x0038–0x003F 0x0000–0x002F 0x0030–0x003F 0x0000–0x001F 0x0020–0x003F N/A 0x0000–0x003F Page Window Access External Internal External Internal External Internal External Internal 01 10 11 NOTE The partitioning as defined in Table 19-17 applies only to the allocated memory space and the actual on-chip memory sizes implemented in the system may differ. Please refer to the device overview chapter for actual sizes. The PPAGE register holds the page select value for the program page window. The value of the PPAGE register can be manipulated by normal read and write (some devices don’t allow writes in some modes) instructions as well as the CALL and RTC instructions. Control registers, vector spaces, and a portion of on-chip memory are located in unpaged portions of the 64K byte physical address space. The stack and I/O addresses should also be in unpaged memory to make them accessible from any page. The starting address of a service routine must be located in unpaged memory because the 16-bit exception vectors cannot point to addresses in paged memory. However, a service routine can call other routines that are in paged memory. The upper 16K byte block of memory space (0xC000–0xFFFF) is unpaged. It is recommended that all reset and interrupt vectors point to locations in this area. 19.4.3.1 CALL and Return from Call Instructions CALL and RTC are uninterruptable instructions that automate page switching in the program expansion window. CALL is similar to a JSR instruction, but the subroutine that is called can be located anywhere in the normal 64K byte address space or on any page of program expansion memory. CALL calculates and stacks a return address, stacks the current PPAGE value, and writes a new instruction-supplied value to PPAGE. The PPAGE value controls which of the 64 possible pages is visible through the 16K byte expansion window in the 64K byte memory map. Execution then begins at the address of the called subroutine. During the execution of a CALL instruction, the CPU: • Writes the old PPAGE value into an internal temporary register and writes the new instruction-supplied PPAGE value into the PPAGE register. MC9S12KG128 Data Sheet, Rev. 1.15 554 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) • • • Calculates the address of the next instruction after the CALL instruction (the return address), and pushes this 16-bit value onto the stack. Pushes the old PPAGE value onto the stack. Calculates the effective address of the subroutine, refills the queue, and begins execution at the new address on the selected page of the expansion window. This sequence is uninterruptable; there is no need to inhibit interrupts during CALL execution. A CALL can be performed from any address in memory to any other address. The PPAGE value supplied by the instruction is part of the effective address. For all addressing mode variations except indexed-indirect modes, the new page value is provided by an immediate operand in the instruction. In indexed-indirect variations of CALL, a pointer specifies memory locations where the new page value and the address of the called subroutine are stored. Using indirect addressing for both the new page value and the address within the page allows values calculated at run time rather than immediate values that must be known at the time of assembly. The RTC instruction terminates subroutines invoked by a CALL instruction. RTC unstacks the PPAGE value and the return address and refills the queue. Execution resumes with the next instruction after the CALL. During the execution of an RTC instruction, the CPU: • Pulls the old PPAGE value from the stack • Pulls the 16-bit return address from the stack and loads it into the PC • Writes the old PPAGE value into the PPAGE register • Refills the queue and resumes execution at the return address This sequence is uninterruptable; an RTC can be executed from anywhere in memory, even from a different page of extended memory in the expansion window. The CALL and RTC instructions behave like JSR and RTS, except they use more execution cycles. Therefore, routinely substituting CALL/RTC for JSR/RTS is not recommended. JSR and RTS can be used to access subroutines that are on the same page in expanded memory. However, a subroutine in expanded memory that can be called from other pages must be terminated with an RTC. And the RTC unstacks a PPAGE value. So any access to the subroutine, even from the same page, must use a CALL instruction so that the correct PPAGE value is in the stack. 19.4.3.2 Extended Address (XAB19:14) and ECS Signal Functionality If the EMK bit in the MODE register is set (see MEBI block description chapter) the PIX5:0 values will be output on XAB19:14 respectively (port K bits 5:0) when the system is addressing within the physical program page window address space (0x8000–0xBFFF) and is in an expanded mode. When addressing anywhere else within the physical address space (outside of the paging space), the XAB19:14 signals will be assigned a constant value based upon the physical address space selected. In addition, the active-low emulation chip select signal, ECS, will likewise function based upon the assigned memory allocation. In the cases of 48K byte and 64K byte allocated physical FLASH/ROM space, the operation of the ECS signal will additionally depend upon the state of the ROMHM bit (see Section 19.3.2.4, “Miscellaneous System Control Register (MISC)”) in the MISC register. Table 19-18, Table 19-19, Table 19-20, and MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 555 Chapter 19 Module Mapping Control (MMCV4) Table 19-21 summarize the functionality of these signals based upon the allocated memory configuration. Again, this signal information is only available externally when the EMK bit is set and the system is in an expanded mode. Table 19-18. 0K Byte Physical FLASH/ROM Allocated Address Space 0x0000–0x3FFF 0x4000–0x7FFF 0x8000–0xBFFF 0xC000–0xFFFF Page Window Access N/A N/A N/A N/A ROMHM N/A N/A N/A N/A ECS 1 1 0 0 XAB19:14 0x3D 0x3E PIX[5:0] 0x3F Table 19-19. 16K Byte Physical FLASH/ROM Allocated Address Space 0x0000–0x3FFF 0x4000–0x7FFF 0x8000–0xBFFF 0xC000–0xFFFF Page Window Access N/A N/A N/A N/A ROMHM N/A N/A N/A N/A ECS 1 1 1 0 XAB19:14 0x3D 0x3E PIX[5:0] 0x3F Table 19-20. 48K Byte Physical FLASH/ROM Allocated Address Space 0x0000–0x3FFF 0x4000–0x7FFF 0x8000–0xBFFF 0xC000–0xFFFF Page Window Access N/A N/A N/A External Internal N/A ROMHM N/A 0 1 N/A N/A N/A ECS 1 0 1 1 0 0 0x3F PIX[5:0] XAB19:14 0x3D 0x3E Table 19-21. 64K Byte Physical FLASH/ROM Allocated Address Space 0x0000–0x3FFF 0x4000–0x7FFF 0x8000–0xBFFF 0xC000–0xFFFF Page Window Access N/A N/A N/A N/A External Internal N/A ROMHM 0 1 0 1 N/A N/A N/A ECS 0 1 0 1 1 0 0 0x3F PIX[5:0] 0x3E XAB19:14 0x3D MC9S12KG128 Data Sheet, Rev. 1.15 556 Freescale Semiconductor Chapter 19 Module Mapping Control (MMCV4) A graphical example of a memory paging for a system configured as 1M byte on-chip FLASH/ROM with 64K allocated physical space is given in Figure 19-12. 0x0000 61 16K FLASH (UNPAGED) 0x4000 62 16K FLASH (UNPAGED) ONE 16K FLASH/ROM PAGE ACCESSIBLE AT A TIME (SELECTED BY PPAGE = 0 TO 63) 0x8000 0 1 2 3 59 60 61 62 63 16K FLASH (PAGED) 0xC000 63 These 16K FLASH/ROM pages accessible from 0x0000 to 0x7FFF if selected by the ROMHM bit in the MISC register. 16K FLASH (UNPAGED) 0xFF00 0xFFFF VECTORS NORMAL SINGLE CHIP Figure 19-12. Memory Paging Example: 1M Byte On-Chip FLASH/ROM, 64K Allocation MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 557 Chapter 19 Module Mapping Control (MMCV4) MC9S12KG128 Data Sheet, Rev. 1.15 558 Freescale Semiconductor Appendix A Electrical Characteristics Appendix A Electrical Characteristics A.1 General NOTE The electrical characteristics given in this section are preliminary and should be used as a guide only. Values cannot be guaranteed by Freescale and are subject to change without notice. This supplement contains the most accurate electrical information for the MC9S12KG128 microcontroller available at the time of publication. The information should be considered PRELIMINARY and is subject to change. This introduction is intended to give an overview on several common topics like power supply, current injection, etc. A.1.1 Parameter Classification The electrical parameters shown in this supplement are guaranteed by various methods. To give the customer a better understanding the following classification is used and the parameters are tagged accordingly in the tables where appropriate. NOTE This classification is shown in the column labeled “C” in the parameter tables where appropriate. P: Those parameters are guaranteed during production testing on each individual device. C: Those parameters are achieved by the design characterization by measuring a statistically relevant sample size across process variations. They are regularly verified by production monitors. T: Those parameters are achieved by design characterization on a small sample size from typical devices. All values shown in the typical column are within this category. D: Those parameters are derived mainly from simulations. A.1.2 Power Supply The MC9S12KG128 utilizes several pins to supply power to the I/O ports, A/D converter, oscillator, PLL and internal logic. The VDDA, VSSA pair supplies the A/D converter. The VDDX, VSSX pair supplies the I/O pins. The VDDR, VSSR pair supplies the internal voltage regulator. VDD1, VSS1, VDD2 and VSS2 are the supply pins for the digital logic. VDDPLL, VSSPLL supply the oscillator and the PLL. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 559 Appendix A Electrical Characteristics VSS1 and VSS2 are internally connected by metal. VDD1 and VDD2 are internally connected by metal. VDDA, VDDX, VDDR as well as VSSA, VSSX, VSSR are connected by anti-parallel diodes for ESD protection. NOTE In the following context VDD5 is used for either VDDA, VDDR and VDDX; VSS5 is used for either VSSA, VSSR and VSSX unless otherwise noted. IDD5 denotes the sum of the currents flowing into the VDDA, VDDX and VDDR pins. VDD is used for VDD1, VDD2 and VDDPLL, VSS is used for VSS1, VSS2 and VSSPLL. IDD is used for the sum of the currents flowing into VDD1 and VDD2. A.1.3 Pins There are four groups of functional pins. A.1.3.1 3.3V/5V I/O Pins Those I/O pins have a nominal level of 3.3V or 5V depending on the application operating point. This group of pins is comprised of all port I/O pins, the analog inputs, BKGD pin and the RESET inputs.The internal structure of all those pins is identical, however some of the functionality may be disabled. E.g. for the analog inputs the output drivers, pull-up and pull-down resistors are disabled permanently. A.1.3.2 Analog Reference This group of pins is comprised of the VRH and VRL pins. A.1.3.3 Oscillator The pins EXTAL, XTAL dedicated to the oscillator have a nominal 2.5V level. They are supplied by VDDPLL. A.1.3.4 PLL The pin XFC dedicated to the oscillator have a nominal 2.5V level. It is supplied by VDDPLL. A.1.3.5 TEST This pin is used for production testing only. A.1.4 Current Injection Power supply must maintain regulation within operating VDD5 or VDD range during instantaneous and operating maximum current conditions. If positive injection current (Vin > VDD5) is greater than IDD5, the injection current may flow out of VDD5 and could result in external power supply going out of regulation. MC9S12KG128 Data Sheet, Rev. 1.15 560 Freescale Semiconductor Appendix A Electrical Characteristics Insure external VDD5 load will shunt current greater than maximum injection current. This will be the greatest risk when the MCU is not consuming power; e.g., if no system clock is present, or if clock rate is very low which would reduce overall power consumption. A.1.5 Absolute Maximum Ratings Absolute maximum ratings are stress ratings only. A functional operation under or outside those maxima is not guaranteed. Stress beyond those limits may affect the reliability or cause permanent damage of the device. This device contains circuitry protecting against damage due to high static voltage or electrical fields; however, it is advised that normal precautions be taken to avoid application of any voltages higher than maximum-rated voltages to this high-impedance circuit. Reliability of operation is enhanced if unused inputs are tied to an appropriate logic voltage level (e.g., either VSS5 or VDD5). Table A-1. Absolute Maximum Ratings Num 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 1 Rating I/O, Regulator and Analog Supply Voltage Internal Logic Supply Voltage1 PLL Supply Voltage 1 Symbol VDD5 VDD VDDPLL ∆VDDX ∆VSSX VIN VRH, VRL VILV VTEST ID IDL IDT TA TJ Tstg Min –0.3 –0.3 –0.3 –0.3 –0.3 –0.3 –0.3 –0.3 –0.3 –25 –25 –0.25 –40 –40 –65 Max 6.5 3.0 3.0 0.3 0.3 6.5 6.5 3.0 10.0 +25 +25 0 125 140 155 Unit V V V V V V V V V mA mA mA °C °C °C Voltage difference VDDX to VDDR and VDDA Voltage difference VSSX to VSSR and VSSA Digital I/O Input Voltage Analog Reference XFC, EXTAL, XTAL inputs TEST input Instantaneous Maximum Current Single pin limit for all digital I/O pins 2 Instantaneous Maximum Current Single pin limit for XFC, EXTAL, XTAL3 Instantaneous Maximum Current Single pin limit for TEST4 Operating Temperature Range (packaged) Operating Temperature Range (junction) Storage Temperature Range The device contains an internal voltage regulator to generate the logic and PLL supply out of the I/O supply. The absolute maximum ratings apply when the device is powered from an external source. 2 All digital I/O pins are internally clamped to VSSX and VDDX, VSSR and VDDR or VSSA and VDDA. 3These pins are internally clamped to V SSPLL and VDDPLL 4This pin is clamped low to V SSR, but not clamped high. This pin must be tied low in applications. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 561 Appendix A Electrical Characteristics A.1.6 ESD Protection and Latch-up Immunity All ESD testing is in conformity with CDF-AEC-Q100 Stress test qualification for Automotive Grade Integrated Circuits. During the device qualification ESD stresses were performed for the Human Body Model (HBM), the Machine Model (MM) and the Charge Device Model. A device will be defined as a failure if after exposure to ESD pulses the device no longer meets the device specification. Complete DC parametric and functional testing is performed per the applicable device specification at room temperature followed by hot temperature, unless specified otherwise in the device specification. Table A-2. ESD and Latch-up Test Conditions Model Human Body Series Resistance Storage Capacitance Number of Pulse per pin Positive Negative Machine Series Resistance Storage Capacitance Number of Pulse per pin Positive Negative Latch-up Minimum input voltage limit Maximum input voltage limit Description Symbol R1 C — — R1 C — — Value 1500 100 3 3 0 200 3 3 –2.5 7.5 V V Ohm pF Unit Ohm pF Table A-3. ESD and Latch-Up Protection Characteristics Num 1 2 3 4 C C C C C Human Body Model (HBM) Machine Model (MM) Charge Device Model (CDM) Latch-up Current at 125°C Positive Negative Latch-up Current at 27°C Positive Negative Rating Symbol VHBM VMM VCDM ILAT +100 –100 ILAT +200 –200 — — — — mA Min 2000 200 500 Max — — — Unit V V V mA 5 C MC9S12KG128 Data Sheet, Rev. 1.15 562 Freescale Semiconductor Appendix A Electrical Characteristics A.1.7 Operating Conditions This chapter describes the operating conditions of the device. Unless otherwise noted those conditions apply to all the following data. NOTE Instead of specifying ambient temperature all parameters are specified for the more meaningful silicon junction temperature. For power dissipation calculations refer to Section A.1.8, “Power Dissipation and Thermal Characteristics”. Table A-4. Operating Conditions Rating I/O, Regulator and Analog Supply Voltage Internal Logic Supply Voltage PLL Supply Voltage 1 Voltage Difference VDDX to VDDA Voltage Difference VSSX to VSSR and VSSA Oscillator Bus Frequency MC9S12KG128C Operating Junction Temperature Range Operating Ambient Temperature Range MC9S12KG128V Operating Junction Temperature Range Operating Ambient Temperature Range MC9S12KG128M Operating Junction Temperature Range Operating Ambient Temperature Range 1 2 2 2 1 Symbol VDD5 VDD VDDPLL ∆VDDX ∆VSSX fosc fbus TJ TA TJ TA TJ TA Min 3.15 2.35 2.35 –0.1 –0.1 0.5 0.5 –40 –40 –40 –40 –40 –40 Typ 3.3/5 2.5 2.5 0 0 — — — 27 — 27 — 27 Max 5.5 2.75 2.75 0.1 0.1 16 25 100 85 120 105 140 125 Unit V V V V V MHz MHz °C °C °C °C °C °C The device contains an internal voltage regulator to generate the logic and PLL supply out of the I/O supply. The absolute maximum ratings apply when this regulator is disabled and the device is powered from an external source. 2 Please refer to Section A.1.8, “Power Dissipation and Thermal Characteristics” for more details about the relation between ambient temperature TA and device junction temperature TJ. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 563 Appendix A Electrical Characteristics A.1.8 Power Dissipation and Thermal Characteristics Power dissipation and thermal characteristics are closely related. The user must assure that the maximum operating junction temperature is not exceeded. The average chip-junction temperature (TJ) in °C can be obtained from: T T T J = Junction Temperature, [ ° C ] J = T + (P • Θ ) A D JA = Ambient Temperature, [ ° C ] A P = Total Chip Power Dissipation, [W] D Θ = Package Thermal Resistance, [ ° C/W] JA The total power dissipation can be calculated from: P P INT D =P INT +P IO = Chip Internal Power Dissipation, [W] Two cases with internal voltage regulator enabled and disabled must be considered: 1. Internal Voltage Regulator disabled P INT =I DD ⋅V DD +I DDPLL ⋅V DDPLL +I DDA ⋅V DDA P IO = ∑ RDSON ⋅ IIOi2 i PIO is the sum of all output currents on I/O ports associated with VDDX and VDDR. For RDSON is valid: R V OL = ----------- ;for outputs driven low DSON I OL respectively R V –V DD5 OH = ----------------------------------- ;for outputs driven high DSON I OH 2. Internal voltage regulator enabled P INT =I DDR ⋅V DDR +I DDA ⋅V DDA IDDR is the current shown in Table A-8 and not the overall current flowing into VDDR, which additionally contains the current flowing into the external loads with output high. P IO = ∑ RDSON ⋅ IIOi2 i Freescale Semiconductor PIO is the sum of all output currents on I/O ports associated with VDDX and VDDR. MC9S12KG128 Data Sheet, Rev. 1.15 564 Appendix A Electrical Characteristics Table A-5. Thermal Package Characteristics1 Num 1 2 3 4 1 C Rating Symbol θJA θJA θJA θJA Min — — — — Typ — — — — Max 54 41 51 41 Unit o o T Thermal Resistance LQFP112, single sided PCB2 T Thermal Resistance LQFP112, double sided PCB with 2 internal planes3 T Thermal Resistance QFP 80, single sided PCB T Thermal Resistance QFP 80, double sided PCB with 2 internal planes C/W C/W C/W C/W o o The values for thermal resistance are achieved by package simulations PC Board according to EIA/JEDEC Standard 51-2 3 PC Board according to EIA/JEDEC Standard 51-7 2 MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 565 Appendix A Electrical Characteristics A.1.9 I/O Characteristics This section describes the characteristics of all 3.3V/5V I/O pins. All parameters are not always applicable, e.g., not all pins feature pull up/down resistances. Table A-6. 5V I/O Characteristics Conditions are shown in Table A-4 unless otherwise noted Num 1 2 3 4 C P P Input High Voltage Input Low Voltage Rating Symbol VIH VIL VHYS Iin –2.5 Min 0.65*VDD5 VSS5 - 0.3 Typ — — 250 — 2.5 Max VDD5 + 0.3 0.35*VDD5 Unit V V mV µA C Input Hysteresis P Input Leakage Current (pins in high impedance input mode) Vin = VDD5 or VSS5 Output High Voltage (pins in output mode) Partial Drive IOH = –2.0mA Full Drive IOH = –10.0mA Output Low Voltage (pins in output mode) Partial Drive IOL = +2.0mA Full Drive IOL = +10.0mA Internal Pull Up Device Current, tested at VIL Max. Internal Pull Up Device Current, tested at VIH Min. Internal Pull Down Device Current, tested at VIH Min. Internal Pull Down Device Current, tested at VIL Max. 1 5 P VOH VDD5 – 0.8 — — V 6 P VOL — — 0.8 V 7 8 9 10 11 12 P P P P IPUL IPUH IPDH IPDL Cin IICS IICP tpign tpval — 10 — 10 — –2.5 –25 — 10 — — — — 7 — — — — –130 — 130 — — 2.5 25 3 — µA µA µA µA pF mA D Input Capacitance T Injection current Single Pin limit Total Device Limit. Sum of all injected currents Port H, J, P Interrupt Input Pulse filtered2 Port H, J, P Interrupt Input Pulse passed 2 13 14 1 2 P P µs µs Refer to Section A.1.4, “Current Injection”, for more details Parameter only applies in STOP or Pseudo STOP mode. MC9S12KG128 Data Sheet, Rev. 1.15 566 Freescale Semiconductor Appendix A Electrical Characteristics Table A-7. 3.3V I/O Characteristics Conditions are shown in Table A-4 unless otherwise noted Num 1 2 3 4 C P Input High Voltage P Input Low Voltage C Input Hysteresis P Input Leakage Current (pins in high impedance input mode) Vin = VDD5 or VSS5 P Output High Voltage (pins in output mode) Partial Drive IOH = –0.75mA Full Drive IOH = –4.0mA P Output Low Voltage (pins in output mode) Partial Drive IOL = +0.9mA Full Drive IOL = +4.75mA P Internal Pull Up Device Current, tested at VIL Max. P Internal Pull Up Device Current, tested at VIH Min. P Internal Pull Down Device Current, tested at VIH Min. P Internal Pull Down Device Current, tested at VIL Max. D Input Capacitance T Injection current1 Single Pin limit Total Device Limit. Sum of all injected currents P Port P, J Interrupt Input Pulse filtered2 P Port P, J Interrupt Input Pulse passed2 Rating Symbol VIH VIL VHYS Iin Min 0.65*VDD5 VSS5 - 0.3 — –1 Typ — — 250 — Max VDD5 + 0.3 0.35*VDD5 — 1 Unit V V mV µA 5 VOH VDD5 – 0.4 — — V 6 VOL — — 0.4 V 7 8 9 10 11 12 IPUL IPUH IPDH IPDL Cin IICS IICP tPULSE tPULSE — –6 — 6 — –2.5 –25 — 10 — — — — 7 — — — –60 — 60 — — 2.5 25 3 µA µA µA µA pF mA 13 14 1 2 µs µs Refer to Section A.1.4, “Current Injection”, for more details Parameter only applies in STOP or Pseudo STOP mode. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 567 Appendix A Electrical Characteristics A.1.10 Supply Currents This section describes the current consumption characteristics of the device as well as the conditions for the measurements. 19.4.3.3 Measurement Conditions All measurements are without output loads. Unless otherwise noted the currents are measured in single chip mode, internal voltage regulator enabled and at 25MHz bus frequency using a 4MHz oscillator. 19.4.3.4 Additional Remarks In expanded modes the currents flowing in the system are highly dependent on the load at the address, data and control signals as well as on the duty cycle of those signals. No generally applicable numbers can be given. A very good estimate is to take the single chip currents and add the currents due to the external loads. MC9S12KG128 Data Sheet, Rev. 1.15 568 Freescale Semiconductor Appendix A Electrical Characteristics Table A-8. Supply Current Characteristics Conditions are shown in Table A-4 unless otherwise noted Num 1 2 Rating Run supply currents Single Chip, Internal regulator enabled Wait Supply current All modules enabled only RTI enabled1 3 Pseudo Stop Current (RTI and COP enabled)1,2 –40°C 27°C 70°C 85°C "C" Temp Option 100°C 105°C "V" Temp Option 120°C 125°C "M" Temp Option 140°C Pseudo Stop Current (RTI and COP disabled)1,2 –40°C 27°C 70°C 85°C "C" Temp Option 100°C 105°C "V" Temp Option 120°C 125°C "M" Temp Option 140°C Stop Current2 –40°C 27°C 70°C 85°C "C" Temp Option 100°C 105°C "V" Temp Option 120°C 125°C "M" Temp Option 140°C 1 2 Symbol IDD5 IDDW Min — — — Typ — — — 90 130 155 180 250 295 470 520 1000 40 80 105 130 200 245 420 470 800 20 60 85 110 180 225 400 450 600 Max 65 Unit mA mA 40 5 µA 350 — — — 1200 — 2400 — 5000 µA 200 — — — 1000 — 2000 — 5000 µA 100 — — — 800 — 1800 — 5000 IDDPS — — — — — — — — — IDDPS — — — — — — — — — IDDS — — — — — — — — — 4 5 PLL off All those low power dissipation levels TJ = TA can be assumed. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 569 Appendix A Electrical Characteristics A.2 Voltage Regulator This section describes the characteristics of the on chip voltage regulator. Table A-9. VREG_3V3 — Operating Conditions Num 1 2 3 4 C P P P P Input Voltages Output Voltage Core Full Performance Mode Output Voltage PLL Full Performance Mode Low Voltage Interrupt Assert Level Deassert Level Low Voltage Reset2 Assert Level Deassert Level Power-on Reset3 Assert Level Deassert Level 1 Characteristic Symbol VVDDR,A VDD Min 3.15 2.35 Typical — 2.5 2.5 4.37 4.52 — — — -— Max 5.5 2.75 2.75 4.66 4.77 — 2.55 — 2.05 Unit V V V V V V V V V VDDPLL 2.35 VLVIA VLVID VLVRA VLVRD VPORA VPORD 4.0 4.15 2.25 — 0.97 — 5 P 6 C 1 2 Monitors VDDA, active only in Full Performance Mode. Indicates I/O & ADC performance degradation due to low supply voltage. Monitors VDD, active only in Full Performance Mode. VLVRA and VPORD must overlap 3 Monitors V . Active in all modes. DD The electrical characteristics given in this section are preliminary and should be used as a guide only. Values in this section cannot be guaranteed by Freescale and are subject to change without notice. MC9S12KG128 Data Sheet, Rev. 1.15 570 Freescale Semiconductor Appendix A Electrical Characteristics A.3 Chip Power-up and LVI/LVR Graphical Explanation Voltage regulator sub modules LVI (low voltage interrupt), POR (power-on reset), and LVR (low voltage reset) handle chip power-up or drops of the supply voltage. Their function is described in Figure A-1. V VLVID VLVIA VDD VDDA VLVRD VLVRA VPORD t LVI LVI Enabled POR LVI Disabled due to LVR LVR Figure A-1. Voltage Regulator — Chip Power-up and Voltage Drops (not scaled) MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 571 Appendix A Electrical Characteristics A.4 A.4.1 Output Loads Resistive Loads The on-chip voltage regulator is intended to supply the internal logic and oscillator circuits allows no external DC loads. A.4.2 Capacitive Loads The capacitive loads are specified in Table A-10. Ceramic capacitors with X7R dielectricum are required. Table A-10. Voltage Regulator — Capacitive Loads Num 1 2 Characteristic VDD external capacitive load VDDPLL external capacitive load Symbol CDDext CDDPLLext Min 200 90 Typical 440 220 Max 12000 5000 Unit nF nF MC9S12KG128 Data Sheet, Rev. 1.15 572 Freescale Semiconductor Appendix A Electrical Characteristics A.5 ATD Characteristics This section describes the characteristics of the analog to digital converter. A.5.1 ATD Operating Characteristics The Table A-11 shows conditions under which the ATD operates. The following constraints exist to obtain full-scale, full range results: VSSA ≤ VRL ≤ VIN ≤ VRH ≤ VDDA. This constraint exists since the sample buffer amplifier can not drive beyond the power supply levels that it ties to. If the input level goes outside of this range it will effectively be clipped. Table A-11. 5V ATD Operating Characteristics Conditions are shown in Table A-4 unless otherwise noted Num C 1 D Reference Potential Low High 2 3 4 C Differential Reference Voltage1 D ATD Clock Frequency D ATD 10-Bit Conversion Period Clock Cycles2 Conv, Time at 2.0MHz ATD Clock fATDCLK Conv, Time at 4.0MHz3 ATD Clock fATDCLK 5 D ATD 8-Bit Conversion Period Clock Cycles1 Conv, Time at 2.0MHz ATD Clock fATDCLK 6 7 8 1 2 Rating Symbol VRL VRH VRH-VRL fATDCLK NCONV10 TCONV10 TCONV10 NCONV8 TCONV8 tSR IREF IREF Min VSSA VDDA/2 4.75 0.5 14 7 3.5 12 6 — — — Typ — — 5.0 — — — — — — — — — Max VDDA/2 VDDA 5.25 2.0 28 14 7 26 13 20 0.750 0.375 Unit V V V MHz Cycles µs µs Cycles µs µs mA mA D Stop Recovery Time (VDDA=5.0 Volts) P Reference Supply current (two ATD modules) P Reference Supply current (one ATD module) Full accuracy is not guaranteed when differential voltage is less than 4.75V The minimum time assumes a final sample period of 2 ATD clocks cycles while the maximum time assumes a final sample period of 16 ATD clocks. 3 Reduced accuracy see Table A-14 and Table A-15. MC9S12KG128 Data Sheet, Rev. 1.15 Freescale Semiconductor 573 Appendix A Electrical Characteristics Table A-12. 3.3V ATD Operating Characteristics Conditions are shown in Table A-4 unless otherwise noted; Supply Voltage 3.3V-10%