Part Number Hot Search : 
1N4934 AT2002 CA3094AT G105EI 15500 GOG95020 MC908QY 100BF
Product Description
Full Text Search
 

To Download HD6417616 Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
 REJ09B0292-0200
The revision list can be viewed directly by clicking the title page. The revision list summarizes the locations of revisions and additions. Details should always be checked by referring to the relevant text.
32
SH7616
SH7616
Hardware Manual Renesas 32-Bit RISC Microcomputer SuperHTM RISC engine Family/SH7600 Series HD6417616
Rev. 2.00 Revision Date: Mar 09, 2006
Keep safety first in your circuit designs!
1. Renesas Technology Corp. puts the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them. Trouble with semiconductors may lead to personal injury, fire or property damage. Remember to give due consideration to safety when making your circuit designs, with appropriate measures such as (i) placement of substitutive, auxiliary circuits, (ii) use of nonflammable material or (iii) prevention against any malfunction or mishap.
Notes regarding these materials
1. These materials are intended as a reference to assist our customers in the selection of the Renesas Technology Corp. product best suited to the customer's application; they do not convey any license under any intellectual property rights, or any other rights, belonging to Renesas Technology Corp. or a third party. 2. Renesas Technology Corp. assumes no responsibility for any damage, or infringement of any thirdparty's rights, originating in the use of any product data, diagrams, charts, programs, algorithms, or circuit application examples contained in these materials. 3. All information contained in these materials, including product data, diagrams, charts, programs and algorithms represents information on products at the time of publication of these materials, and are subject to change by Renesas Technology Corp. without notice due to product improvements or other reasons. It is therefore recommended that customers contact Renesas Technology Corp. or an authorized Renesas Technology Corp. product distributor for the latest product information before purchasing a product listed herein. The information described here may contain technical inaccuracies or typographical errors. Renesas Technology Corp. assumes no responsibility for any damage, liability, or other loss rising from these inaccuracies or errors. Please also pay attention to information published by Renesas Technology Corp. by various means, including the Renesas Technology Corp. Semiconductor home page (http://www.renesas.com). 4. When using any or all of the information contained in these materials, including product data, diagrams, charts, programs, and algorithms, please be sure to evaluate all information as a total system before making a final decision on the applicability of the information and products. Renesas Technology Corp. assumes no responsibility for any damage, liability or other loss resulting from the information contained herein. 5. Renesas Technology Corp. semiconductors are not designed or manufactured for use in a device or system that is used under circumstances in which human life is potentially at stake. Please contact Renesas Technology Corp. or an authorized Renesas Technology Corp. product distributor when considering the use of a product contained herein for any specific purposes, such as apparatus or systems for transportation, vehicular, medical, aerospace, nuclear, or undersea repeater use. 6. The prior written approval of Renesas Technology Corp. is necessary to reprint or reproduce in whole or in part these materials. 7. If these products or technologies are subject to the Japanese export control restrictions, they must be exported under a license from the Japanese government and cannot be imported into a country other than the approved destination. Any diversion or reexport contrary to the export control laws and regulations of Japan and/or the country of destination is prohibited. 8. Please contact Renesas Technology Corp. for further details on these materials or the products contained therein.
Rev. 2.00 Mar 09, 2006 page ii of xxvi
Preface
The SH7616 is a microprocessor that integrates peripheral functions necessary for system configuration with a 32-bit internal architecture SH2-DSP CPU as its core. The SH7616's on-chip peripheral functions include a cache memory, an interrupt controller, timers, an ethernet controller (EtherC), DSP, a serial communication interface with FIFO (SCIF), a USB function module, a user break controller (UBC), a bus state controller (BSC), a direct memory access cntroller (DMAC), and I/O ports, making it ideal for use as a microcomputer in electronic devices that require high speed together with low power consumption. Intended Readership: This manual is intended for users undertaking the design of an application system using the SH7616. Readers using this manual require a basic knowledge of electrical circuits, logic circuits, and microcomputers. Purpose: The purpose of this manual is to give users an understanding of the hardware functions and electrical characteristics of the SH7616. Details of execution instructions can be found in the SH-1, SH-2, SH-DSP Programming Manual, which should be read in conjunction with the present manual.
Using this Manual: * For an overall understanding of the SH7616's functions Follow the Table of Contents. This manual is broadly divided into sections on the CPU, system control functions, peripheral functions, and electrical characteristics. * For a detailed understanding of CPU functions Refer to the separate publication SH-1, SH-2, SH-DSP Programming Manual. Note on bit notation: Bits are shown in high-to-low order from left to right. Related Material: The latest information is available at our Web Site. Please make sure that you have the most up-to-date information available. http://www.renesas.com/
Rev. 2.00 Mar 09, 2006 page iii of xxvi
User's Manuals on the SH7616:
Manual Title SH7616 Hardware Manual SH-1/ SH-2/SH-DSP Software Manual ADE No. This manual REJ09B0171-0500O
Users manuals for development tools:
Manual Title C/C++ Complier, Assembler, Optimized Linkage Editor User's Manual Simulator Debugger Users Manual High-performance Embedded Workshop Users Manual ADE No. REJ10B0152-0101 REJ10B0210-0200 REJ10J0886-0300
Application Note:
Manual Title C/C++ Complier ADE No. REJ05B0463-0300
Rev. 2.00 Mar 09, 2006 page iv of xxvi
Main Revisions in This Edition
Item All Page Revision (See Manual for Details) * * 2.1.4 DSP Registers 37 Company name amended Hitachi, Ltd. Renesas Technology Corp. Amendments made due to change in package code FP-208C PRQP0208KA-A
Description added Figure 2.4 shows the DSP registers. The DSR register bit functions are shown in table 2.2. Registers A0, X0, X1, Y0, Y1, and DSR are handled as system registers by CPU core instructions.
7.1.5 Address Map Table 7.3 Address Map 7.2.7 Individual Memory Control Register (MCR) Bits 1 and 15 * For synchronous DRAM interface
255
Table amended
Address H'1000E000-H'1000EFFF H'1001E000-H'1001EFFF Space On-chip X RAM area On-chip Y RAM area Memory Size 4 kbytes 4 kbytes
269 to Description replaced 274
Bits 7, 5, and 4 7.5.11 64 Mbit 323 Synchronous DRAM (2 Mword x 32-bit) Connection Description amended Synchronous DRAM Mode Settings: To make mode settings for the synchronous DRAM, write to address X+H'FFFF0000 or X+H'FFFF8000 from the CPU. (X represents the setting value.) Whether to use X+H'FFFF0000 or X+H'FFFF8000 determines on the synchronous DRAM used. Figure amended
Associative purge: Bit Address 31 29 28 010 Tag address 19 10 9 Entry address 6 43 -- 4 0
8.4.7 Associative Purges Figure 8.11 Associative Purge Access
369
Number of bits 3
Rev. 2.00 Mar 09, 2006 page v of xxvi
Item 10.2.8 Transmit/Receive Status Copy Enable Register (TRSCER)
Page 437
Revision (See Manual for Details) Description amended
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 -- 0 R 7 RMAFCE 0 R/W 30 -- 0 R 14 -- 0 R 6 -- 0 R 29 -- 0 R 13 -- 0 R 5 -- 0 R ... ... ... ... 12 -- 0 R 4 -- 0 R 19 -- 0 R 11 -- 0 R 3 -- 0 R 18 -- 0 R 10 -- 0 R 2 -- 0 R 17 -- 0 R 9 -- 0 R 1 -- 0 R 16 -- 0 R 8 -- 0 R 0 -- 0 R
Bits 31 to 8--Reserved These bits are always read as 0. The write value should always be 0. Bit 7--Multicast Address Frame Receive (RMAF): Bit Copy Enable (RMAFCE)
Bit 7: RMAFCE 0 1 Description Enables the RMAF bit status to be indicated in the RFS7 bit in the receive descriptor. Disables occurrence of corresponding source to be indicated in the RFS7 bit in the receive descriptor.
Bits 6 to 0--Reserved: These bits are always read as 0. The write value should always be 0.
10.3.1 Descriptor 450 List and Data Buffers Transmit Descriptor 0 (TD0)
Description amended
Bit 27--Transmit Frame Error (TFE): Indicates that one or other bit of the transmit frame status indicated by bits 26 to 0 is set.
Bit 27: TFE 0 1 Description No error during transmission An error of some kind occurred during transmission (see bits 26 to 0)
Bits 26 to 0--Transmit Frame Status 26 to 0 (TFS26 to TFS0): These bits indicate the error status during frame transmission. * TFS26 to TFS9--Reserved * TFS8--Teransmit Abort Detect Note: This bit is set to 1 when any of Transmit Frame Status bits 4 to 0 is set. When this bit is set, the Transmit Frame Error bit (bit 27: TFE) is set to 1. * TFS7 to TFS5--Reserved
Rev. 2.00 Mar 09, 2006 page vi of xxvi
Item
Page
Revision (See Manual for Details) Figure amended
Receive descriptor 31 30 29 28 27 26 RD0
10.3.1 Descriptor 451 List and Data Buffers Receive Descriptor Figure 10.3 Relationship between Receive Descriptor and Receive Buffer
RACT RDLE RFP1 RFP0 RFE
RFS 26 to RFS0
RD1 RD2
31 31
RBL
16 15
RDL
0 0
RBA Padding (4 bytes)
Rev. 2.00 Mar 09, 2006 page vii of xxvi
Item
Page
Revision (See Manual for Details) Description amended Bit 27--Receive Frame Error (RFE): Indicates that one or other bit of the receive frame status indicated by bits 26 to 0 is set. Whether or not the multicast address frame receive information which is part of the frame status, is copied into this bit is specified by the transmit/receive status copy enable register.
Bit 27: RFE 0 1 Description No error during reception (Initial value) An error of some kind occurred during reception (see bits 26 to 0)
10.3.1 Descriptor 453 List and Data Buffers Receive Descriptor 0 (TD0)
* * * *
Bits 26 to 0--Receive Frame Status 26 to 0 (RFS26 to RFS0): These bits indicate the error status during frame reception. RFS26 to RFS10--Reserved RFS9--Receive FIFO Overflow (corresponds to RFOF bit in EESR) RFS8--Reserve Abort Detect Note: This bit is set to 1 when any of Receive Frame Status bit 9, bit 7, bits 4 to 0 is set. When this bit is set, the Receive Frame Error bit (bit 27: RFE) is set to 1.
* * * * * * * *
RFS7-- Receive Multicast Address Frame (corresponds to RMAF bit in EESR) 1 RFS6--Reserved* RSF5-- Receive Frame Discard Request Assertion 1 (corresponds to RFAR bit in EESR)* RFS4--Receive Residual-Bit Frame (corresponds to RRF bit in EESR) RFS3--Receive Too-Long Frame (corresponds to RTLF bit in EESR) RFS2--Receive Too-Short Frame (corresponds to RTSF bit in EESR) RFS1--PHY-LSI Receive Error (corresponds to PRE bit in EESR) RFS0--CRC Error on Received Frame (corresponds to CERF bit in EESR) Note: 1. Only HD6417616 is effective. HD6417615 is Reserved bit.
Rev. 2.00 Mar 09, 2006 page viii of xxvi
Item
Page
Revision (See Manual for Details) Figure replaced
Clock
11.3.6 DMA Transfer 496 Request Acknowledge Signal Output Timing Figure 11.13 Example of DACKn Output Timing
DACKn (Active high)
0.5 cycles CPU DMAC
Address bus
14.3.4 Operation in 613 Synchronous Mode 15.4 SIOF Interrupt 663 Sources and DMAC
Description amended In synchronous mode, the SCIF receives data in synchronization with the rise of the serial clock. Description amended Each SIOF channel has four interrupt sources: the receive-overrunerror interrupt (RERI0) request, transmit-underrun-error interrupt (TERI0) request, receive-data-full interrupt/receive-control-dataregister-full interrupt (RDFI0) request, and transmit-data-empty interrupt/transmit-control-data-register-empty interrupt (TDEI0) request. Table 15.3 shows the interrupt sources and their relative priorities. The RDFI0 and TDEI0 interrupts are enabled by the RIE, RCIE, TIE, and TCIE bits, respectively, in SICTR. The RERI0 and TERI0 interrupts cannot be disabled. Table amended
Interrupt Source RERI0 TERI0 RDFI0 TDEI0 Description Receive overrun error (RERR) Transmit underrun error (TERR) Receive data register full (RDRF)/ Receive Control Data Register Full (RCD) Transmit data register empty (TDRE)/ Transmit Control Data Register Empty (TCD) DMAC Activation Not possible Not possible Possible* Possible* Priority High Low
Table 15.3 SIOF Interrupt Sources
664
Appendix C Table C.1 SH7616 Product Lineup
904
Table amended
Abbreviation SH7616 Voltage 3.3 V Operating Frequency 62.5 MHz Mark Code HD6417616SF Package PLQP0208KA-A
Rev. 2.00 Mar 09, 2006 page ix of xxvi
Rev. 2.00 Mar 09, 2006 page x of xxvi
Contents
Section 1 Overview.............................................................................................................
1.1 1.2 1.3 Features of SuperH Microcomputer with On-Chip Ethernet Controller ........................... Block Diagram .................................................................................................................. Pin Description.................................................................................................................. 1.3.1 Pin Arrangement .................................................................................................. 1.3.2 Pin Functions ....................................................................................................... 1.3.3 Pin Multiplexing .................................................................................................. Processing States............................................................................................................... 1 1 13 14 14 15 21 27
1.4
Section 2 CPU ...................................................................................................................... 31
2.1 Register Configuration ...................................................................................................... 2.1.1 General Registers ................................................................................................. 2.1.2 Control Registers ................................................................................................. 2.1.3 System Registers .................................................................................................. 2.1.4 DSP Registers ...................................................................................................... 2.1.5 Notes on Guard Bits and Overflow Treatment..................................................... 2.1.6 Initial Values of Registers.................................................................................... Data Formats ..................................................................................................................... 2.2.1 Data Format in Registers...................................................................................... 2.2.2 Data Formats in Memory ..................................................................................... 2.2.3 Immediate Data Format ....................................................................................... 2.2.4 DSP Type Data Formats ...................................................................................... 2.2.5 DSP Type Instructions and Data Formats ............................................................ CPU Core Instruction Features ......................................................................................... Instruction Formats ........................................................................................................... 2.4.1 CPU Instruction Addressing Modes..................................................................... 2.4.2 DSP Data Addressing........................................................................................... 2.4.3 Instruction Formats for CPU Instructions ............................................................ 2.4.4 Instruction Formats for DSP Instructions............................................................. Instruction Set ................................................................................................................... 2.5.1 CPU Instruction Set ............................................................................................. 2.5.2 DSP Data Transfer Instruction Set ....................................................................... 2.5.3 DSP Operation Instruction Set ............................................................................. 2.5.4 Various Operation Instructions ............................................................................ Usage Notes ...................................................................................................................... 2.6.1 When not using DSP instructions ........................................................................ 31 31 33 36 37 40 40 41 41 41 42 42 44 48 52 52 56 62 66 72 73 89 93 96 105 105
2.2
2.3 2.4
2.5
2.6
Rev. 2.00 Mar 09, 2006 page xi of xxvi
2.6.2
When executing a combination of double-precision multiplication or double-precision product-sum operation (CPU instruction) and DSP computing instruction .......................................................................................... 105
Section 3 Oscillator Circuits and Operating Modes .................................................. 107
3.1 3.2 Overview........................................................................................................................... On-Chip Clock Pulse Generator and Operating Modes .................................................... 3.2.1 Clock Pulse Generator ......................................................................................... 3.2.2 Clock Operating Mode Settings........................................................................... 3.2.3 Connecting a Crystal Resonator........................................................................... 3.2.4 External Clock Input ............................................................................................ 3.2.5 Operating Frequency Selection by Register......................................................... 3.2.6 Clock Modes and Frequency Ranges................................................................... 3.2.7 Notes on Board Design ........................................................................................ Bus Width of the CS0 Area............................................................................................... 107 107 107 109 112 113 114 122 123 124
3.3
Section 4 Exception Handling ......................................................................................... 125
4.1 Overview........................................................................................................................... 4.1.1 Types of Exception Handling and Priority Order ................................................ 4.1.2 Exception Handling Operations ........................................................................... 4.1.3 Exception Vector Table ....................................................................................... Resets ................................................................................................................................ 4.2.1 Types of Resets .................................................................................................... 4.2.2 Power-On Reset ................................................................................................... 4.2.3 Manual Reset ....................................................................................................... Address Errors .................................................................................................................. 4.3.1 Sources of Address Errors ................................................................................... 4.3.2 Address Error Exception Handling ...................................................................... Interrupts ........................................................................................................................... 4.4.1 Interrupt Sources.................................................................................................. 4.4.2 Interrupt Priority Levels....................................................................................... 4.4.3 Interrupt Exception Handling............................................................................... Exceptions Triggered by Instructions ............................................................................... 4.5.1 Instruction-Triggered Exception Types ............................................................... 4.5.2 Trap Instructions .................................................................................................. 4.5.3 Illegal Slot Instructions ........................................................................................ 4.5.4 General Illegal Instructions.................................................................................. When Exception Sources Are Not Accepted .................................................................... 4.6.1 Immediately after a Delayed Branch Instruction ................................................. 4.6.2 Immediately after an Interrupt-Disabled Instruction............................................ 125 125 127 128 131 131 131 132 132 132 134 135 135 136 136 137 137 137 138 138 139 139 139
4.2
4.3
4.4
4.5
4.6
Rev. 2.00 Mar 09, 2006 page xii of xxvi
4.7 4.8
4.6.3 Instructions in Repeat Loops................................................................................ Stack Status after Exception Handling.............................................................................. Usage Notes ...................................................................................................................... 4.8.1 Value of Stack Pointer (SP) ................................................................................. 4.8.2 Value of Vector Base Register (VBR) ................................................................. 4.8.3 Address Errors Caused by Stacking of Address Error Exception Handling ........ 4.8.4 Manual Reset during Register Access..................................................................
140 141 142 142 142 142 142
Section 5 Interrupt Controller (INTC)........................................................................... 143
5.1 Overview........................................................................................................................... 5.1.1 Features ................................................................................................................ 5.1.2 Block Diagram ..................................................................................................... 5.1.3 Pin Configuration................................................................................................. 5.1.4 Register Configuration......................................................................................... Interrupt Sources ............................................................................................................... 5.2.1 NMI Interrupt....................................................................................................... 5.2.2 User Break Interrupt............................................................................................. 5.2.3 H-UDI Interrupt ................................................................................................... 5.2.4 IRL Interrupts....................................................................................................... 5.2.5 IRQ Interrupts ...................................................................................................... 5.2.6 On-chip Peripheral Module Interrupts ................................................................. 5.2.7 Interrupt Exception Vectors and Priority Order ................................................... Register Descriptions ........................................................................................................ 5.3.1 Interrupt Priority Level Setting Register A (IPRA) ............................................. 5.3.2 Interrupt Priority Level Setting Register B (IPRB).............................................. 5.3.3 Interrupt Priority Level Setting Register C (IPRC).............................................. 5.3.4 Interrupt Priority Level Setting Register D (IPRD) ............................................. 5.3.5 Interrupt Priority Level Setting Register E (IPRE) .............................................. 5.3.6 Vector Number Setting Register WDT (VCRWDT) ........................................... 5.3.7 Vector Number Setting Register A (VCRA)........................................................ 5.3.8 Vector Number Setting Register B (VCRB) ........................................................ 5.3.9 Vector Number Setting Register C (VCRC) ........................................................ 5.3.10 Vector Number Setting Register D (VCRD)........................................................ 5.3.11 Vector Number Setting Register E (VCRE) ........................................................ 5.3.12 Vector Number Setting Register F (VCRF) ......................................................... 5.3.13 Vector Number Setting Register G (VCRG)........................................................ 5.3.14 Vector Number Setting Register H (VCRH)........................................................ 5.3.15 Vector Number Setting Register I (VCRI)........................................................... 5.3.16 Vector Number Setting Register J (VCRJ) .......................................................... 5.3.17 Vector Number Setting Register K (VCRK)........................................................ 143 143 143 145 145 146 147 147 147 147 148 152 152 159 159 160 161 162 163 164 165 166 166 167 168 169 170 171 172 173 174
5.2
5.3
Rev. 2.00 Mar 09, 2006 page xiii of xxvi
5.4
5.5 5.6 5.7
5.3.18 Vector Number Setting Register L (VCRL) ........................................................ 5.3.19 Vector Number Setting Register M (VCRM) ...................................................... 5.3.20 Vector Number Setting Register N (VCRN)........................................................ 5.3.21 Vector Number Setting Register O (VCRO)........................................................ 5.3.22 Vector Number Setting Register P (VCRP)......................................................... 5.3.23 Vector Number Setting Register Q (VCRQ)........................................................ 5.3.24 Vector Number Setting Register R (VCRR) ........................................................ 5.3.25 Vector Number Setting Register S (VCRS)......................................................... 5.3.26 Vector Number Setting Register T (VCRT) ........................................................ 5.3.27 Vector Number Setting Register U (VCRU)........................................................ 5.3.28 Interrupt Control Register (ICR).......................................................................... 5.3.29 IRQ Control/Status Register (IRQCSR) .............................................................. Interrupt Operation............................................................................................................ 5.4.1 Interrupt Sequence ............................................................................................... 5.4.2 Stack State after Interrupt Exception Handling.................................................... Interrupt Response Time................................................................................................... Sampling of Pins IRL3-IRL0 ........................................................................................... Usage Notes ......................................................................................................................
175 176 177 178 179 180 181 182 183 184 187 188 190 190 192 192 194 195
Section 6 User Break Controller (UBC) ....................................................................... 199
6.1 Overview........................................................................................................................... 6.1.1 Features................................................................................................................ 6.1.2 Block Diagram..................................................................................................... 6.1.3 Register Configuration......................................................................................... Register Descriptions ........................................................................................................ 6.2.1 Break Address Register A (BARA) ..................................................................... 6.2.2 Break Address Mask Register A (BAMRA)........................................................ 6.2.3 Break Bus Cycle Register A (BBRA).................................................................. 6.2.4 Break Address Register B (BARB) ..................................................................... 6.2.5 Break Address Mask Register B (BAMRB) ........................................................ 6.2.6 Break Bus Cycle Register B (BBRB) .................................................................. 6.2.7 Break Address Register C (BARC)...................................................................... 6.2.8 Break Address Mask Register C (BAMRC) ........................................................ 6.2.9 Break Data Register C (BDRC) ........................................................................... 6.2.10 Break Data Mask Register C (BDMRC).............................................................. 6.2.11 Break Bus Cycle Register C (BBRC) .................................................................. 6.2.12 Break Execution Times Register C (BETRC) ..................................................... 6.2.13 Break Address Register D (BARD) ..................................................................... 6.2.14 Break Address Mask Register D (BAMRD)........................................................ 6.2.15 Break Data Register D (BDRD)........................................................................... 199 199 200 201 203 203 204 205 207 208 209 211 212 214 215 217 218 219 220 222
6.2
Rev. 2.00 Mar 09, 2006 page xiv of xxvi
6.3
6.2.16 Break Data Mask Register D (BDMRD) ............................................................. 6.2.17 Break Bus Cycle Register D (BBRD) .................................................................. 6.2.18 Break Execution Times Register D (BETRD) ..................................................... 6.2.19 Break Control Register (BRCR) .......................................................................... 6.2.20 Branch Flag Registers (BRFR) ............................................................................ 6.2.21 Branch Source Registers (BRSR) ........................................................................ 6.2.22 Branch Destination Registers (BRDR) ................................................................ Operation........................................................................................................................... 6.3.1 User Break Operation Sequence .......................................................................... 6.3.2 Instruction Fetch Cycle Break.............................................................................. 6.3.3 Data Access Cycle Break ..................................................................................... 6.3.4 Saved Program Counter (PC) Value .................................................................... 6.3.5 X Memory Bus or Y Memory Bus Cycle Break .................................................. 6.3.6 Sequential Break .................................................................................................. 6.3.7 PC Traces............................................................................................................. 6.3.8 Examples of Use .................................................................................................. 6.3.9 Usage Notes .........................................................................................................
223 225 226 227 233 234 235 236 236 237 238 239 239 240 241 243 247
Section 7 Bus State Controller (BSC) ........................................................................... 249
7.1 Overview........................................................................................................................... 7.1.1 Features ................................................................................................................ 7.1.2 Block Diagram ..................................................................................................... 7.1.3 Pin Configuration................................................................................................. 7.1.4 Register Configuration......................................................................................... 7.1.5 Address Map ........................................................................................................ Register Descriptions ........................................................................................................ 7.2.1 Bus Control Register 1 (BCR1) ........................................................................... 7.2.2 Bus Control Register 2 (BCR2) ........................................................................... 7.2.3 Bus Control Register 3 (BCR3) ........................................................................... 7.2.4 Wait Control Register 1 (WCR1)......................................................................... 7.2.5 Wait Control Register 2 (WCR2)......................................................................... 7.2.6 Wait Control Register 3 (WCR3)......................................................................... 7.2.7 Individual Memory Control Register (MCR)....................................................... 7.2.8 Refresh Timer Control/Status Register (RTCSR) ................................................ 7.2.9 Refresh Timer Counter (RTCNT)........................................................................ 7.2.10 Refresh Time Constant Register (RTCOR) ......................................................... Access Size and Data Alignment ...................................................................................... 7.3.1 Connection to Ordinary Devices.......................................................................... 7.3.2 Connection to Little-Endian Devices ................................................................... Accessing Ordinary Space ................................................................................................ 249 249 251 252 254 255 257 257 260 261 263 265 267 268 276 278 278 279 279 280 282
7.2
7.3
7.4
Rev. 2.00 Mar 09, 2006 page xv of xxvi
7.4.1 Basic Timing........................................................................................................ 7.4.2 Wait State Control................................................................................................ 7.4.3 CS Assertion Period Extension ............................................................................ 7.5 Synchronous DRAM Interface.......................................................................................... 7.5.1 Synchronous DRAM Direct Connection ............................................................. 7.5.2 Address Multiplexing........................................................................................... 7.5.3 Burst Reads .......................................................................................................... 7.5.4 Single Reads ........................................................................................................ 7.5.5 Single Writes........................................................................................................ 7.5.6 Burst Write Mode ................................................................................................ 7.5.7 Bank Active Function .......................................................................................... 7.5.8 Refreshes.............................................................................................................. 7.5.9 Overlap Between Auto Precharge Cycle (Tap) and Next Access ........................ 7.5.10 Power-On Sequence............................................................................................. 7.5.11 64 Mbit Synchronous DRAM (2 Mword x 32-bit) Connection........................... 7.6 DRAM Interface ............................................................................................................... 7.6.1 DRAM Direct Connection ................................................................................... 7.6.2 Address Multiplexing........................................................................................... 7.6.3 Basic Timing........................................................................................................ 7.6.4 Wait State Control................................................................................................ 7.6.5 Burst Access ........................................................................................................ 7.6.6 EDO Mode........................................................................................................... 7.6.7 DRAM Single Transfer........................................................................................ 7.6.8 Refreshing............................................................................................................ 7.6.9 Power-On Sequence............................................................................................. 7.7 Burst ROM Interface......................................................................................................... 7.8 Idles between Cycles......................................................................................................... 7.9 Bus Arbitration.................................................................................................................. 7.9.1 Master Mode ........................................................................................................ 7.10 Additional Items................................................................................................................ 7.10.1 Resets................................................................................................................... 7.10.2 Access as Viewed from CPU, DMAC or E-DMAC ............................................ 7.10.3 STATS1 and STATS0 Pins ................................................................................. 7.10.4 BUSHiZ Specification ......................................................................................... 7.11 Usage Notes ...................................................................................................................... 7.11.1 Normal Space Access after Synchronous DRAM Write when Using DMAC..... 7.11.2 When Using I: E Clock Ratio of 1: 1, 8-Bit Bus Width, and External Wait Input ....................................................................................... 7.11.3 When connecting external device to synchronous DRAM ..................................
282 287 291 292 292 294 296 301 303 304 306 317 320 321 323 324 324 325 326 327 329 332 336 337 339 339 343 345 349 350 350 351 352 353 354 354 356 356
Rev. 2.00 Mar 09, 2006 page xvi of xxvi
Section 8 Cache.................................................................................................................... 357
8.1 8.2 8.3 8.4 Introduction....................................................................................................................... 8.1.1 Register Configuration......................................................................................... Register Description.......................................................................................................... 8.2.1 Cache Control Register (CCR)............................................................................. Address Space and the Cache............................................................................................ Cache Operation................................................................................................................ 8.4.1 Cache Reads......................................................................................................... 8.4.2 Write Access ........................................................................................................ 8.4.3 Cache-Through Access ........................................................................................ 8.4.4 The TAS Instruction............................................................................................. 8.4.5 Pseudo-LRU and Cache Replacement ................................................................. 8.4.6 Cache Initialization .............................................................................................. 8.4.7 Associative Purges ............................................................................................... 8.4.8 Cache Flushing..................................................................................................... 8.4.9 Data Array Access ............................................................................................... 8.4.10 Address Array Access.......................................................................................... Cache Use ......................................................................................................................... 8.5.1 Initialization ......................................................................................................... 8.5.2 Purge of Specific Lines ........................................................................................ 8.5.3 Cache Data Coherency......................................................................................... 8.5.4 Two-Way Cache Mode ........................................................................................ Usage Notes ...................................................................................................................... 8.6.1 Standby ................................................................................................................ 8.6.2 Cache Control Register ........................................................................................ 357 358 358 358 360 361 361 363 366 366 366 368 368 369 369 370 371 371 372 372 373 374 374 374
8.5
8.6
Section 9 Ethernet Controller (EtherC)......................................................................... 375
9.1 Overview........................................................................................................................... 9.1.1 Features ................................................................................................................ 9.1.2 Configuration ....................................................................................................... 9.1.3 Pin Configuration................................................................................................. 9.1.4 Ethernet Controller Register Configuration ......................................................... Register Descriptions ........................................................................................................ 9.2.1 EtherC Mode Register (ECMR)........................................................................... 9.2.2 EtherC Status Register (ECSR)............................................................................ 9.2.3 EtherC Interrupt Permission Register (ECSIPR) ................................................. 9.2.4 PHY Interface Register (PIR) .............................................................................. 9.2.5 MAC Address High Register (MAHR)................................................................ 9.2.6 MAC Address Low Register (MALR)................................................................. 9.2.7 Receive Frame Length Register (RFLR) ............................................................. 375 375 376 378 379 380 380 383 384 385 386 387 388
9.2
Rev. 2.00 Mar 09, 2006 page xvii of xxvi
9.3
9.4
9.2.8 PHY Interface Status Register (PSR)................................................................... 9.2.9 Transmit Retry Over Counter Register (TROCR) ............................................... 9.2.10 Single Collision Detect Counter Register (SCDCR)............................................ 9.2.11 Delay Collision Detect Counter Register (CDCR) .............................................. 9.2.12 Lost Carrier Counter Register (LCCR) ................................................................ 9.2.13 Carrier Not Detect Counter Register (CNDCR) .................................................. 9.2.14 Illegal Frame Length Counter Register (IFLCR) ................................................. 9.2.15 CRC Error Frame Counter Register (CEFCR)..................................................... 9.2.16 Frame Receive Error Counter Register (FRECR )............................................... 9.2.17 Too-Short Frame Receive Counter Register (TSFRCR)...................................... 9.2.18 Too-Long Frame Receive Counter Register (TLFRCR)...................................... 9.2.19 Residual-Bit Frame Counter Register (RFCR) .................................................... 9.2.20 Multicast Address Frame Counter Register (MAFCR)........................................ Operation .......................................................................................................................... 9.3.1 Transmission........................................................................................................ 9.3.2 Reception ............................................................................................................. 9.3.3 MII Frame Timing ............................................................................................... 9.3.4 Accessing MII Registers ...................................................................................... 9.3.5 Magic Packet Detection ....................................................................................... 9.3.6 CPU Operating Mode and Ethernet Controller Operation ................................... 9.3.7 CAM Match Signal Input Function...................................................................... Connection to PHY-LSI....................................................................................................
389 390 391 392 393 394 395 396 397 398 399 400 401 402 402 404 406 408 411 412 413 415
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC) ....................................................................................................... 417
10.1 Overview........................................................................................................................... 10.1.1 Features................................................................................................................ 10.1.2 Configuration ....................................................................................................... 10.1.3 Descriptor Management System .......................................................................... 10.1.4 Register Configuration......................................................................................... 10.2 Register Descriptions ........................................................................................................ 10.2.1 E-DMAC Mode Register (EDMR) ...................................................................... 10.2.2 E-DMAC Transmit Request Register (EDTRR).................................................. 10.2.3 E-DMAC Receive Request Register (EDRRR) ................................................... 10.2.4 Transmit Descriptor List Address Register (TDLAR) ......................................... 10.2.5 Receive Descriptor List Address Register (RDLAR) .......................................... 10.2.6 EtherC/E-DMAC Status Register (EESR) ........................................................... 10.2.7 EtherC/E-DMAC Status Interrupt Permission Register (EESIPR) ...................... 10.2.8 Transmit/Receive Status Copy Enable Register (TRSCER) ................................ 10.2.9 Receive Missed-Frame Counter Register (RMFCR) ...........................................
Rev. 2.00 Mar 09, 2006 page xviii of xxvi
417 417 418 419 419 421 421 422 423 424 425 426 432 437 438
10.2.10 Transmit FIFO Threshold Register (TFTR)......................................................... 10.2.11 FIFO Depth Register (FDR)................................................................................. 10.2.12 Receiver Control Register (RCR) ........................................................................ 10.2.13 E-DMAC Operation Control Register (EDOCR) ................................................ 10.2.14 Receiving-Buffer Write Address Register (RBWAR) ......................................... 10.2.15 Receiving-Descriptor Fetch Address Register (RDFAR) .................................... 10.2.16 Transmission-Buffer Read Address Register (TBRAR) ...................................... 10.2.17 Transmission-Descriptor Fetch Address Register (TDFAR) ............................... 10.3 Operation........................................................................................................................... 10.3.1 Descriptor List and Data Buffers ......................................................................... 10.3.2 Transmission ........................................................................................................ 10.3.3 Reception ............................................................................................................. 10.3.4 Multi-Buffer Frame Transmit/Receive Processing ..............................................
439 441 442 443 444 445 446 447 448 448 455 457 459
Section 11 Direct Memory Access Controller (DMAC).......................................... 461
11.1 Overview........................................................................................................................... 11.1.1 Features ................................................................................................................ 11.1.2 Block Diagram ..................................................................................................... 11.1.3 Pin Configuration................................................................................................. 11.1.4 Register Configuration......................................................................................... 11.2 Register Descriptions ........................................................................................................ 11.2.1 DMA Source Address Registers 0 and 1 (SAR0, SAR1)..................................... 11.2.2 DMA Destination Address Registers 0 and 1 (DAR0, DAR1) ............................ 11.2.3 DMA Transfer Count Registers 0 and 1 (TCR0, TCR1) ..................................... 11.2.4 DMA Channel Control Registers 0 and 1 (CHCR0, CHCR1) ............................. 11.2.5 DMA Vector Number Registers 0 and 1 (VCRDMA0, VCRDMA1) ................. 11.2.6 DMA Request/Response Selection Control Registers 0 and 1 (DRCR0, DRCR1) ............................................................................................... 11.2.7 DMA Operation Register (DMAOR)................................................................... 11.3 Operation........................................................................................................................... 11.3.1 DMA Transfer Flow............................................................................................. 11.3.2 DMA Transfer Requests ...................................................................................... 11.3.3 Channel Priorities................................................................................................. 11.3.4 DMA Transfer Types ........................................................................................... 11.3.5 Number of Bus Cycles ......................................................................................... 11.3.6 DMA Transfer Request Acknowledge Signal Output Timing ............................. 11.3.7 DREQn Pin Input Detection Timing.................................................................... 11.3.8 DMA Transfer End .............................................................................................. 11.3.9 BH Pin Output Timing......................................................................................... 11.4 Usage Examples................................................................................................................ 461 461 463 464 465 466 466 466 467 467 472 473 475 477 477 479 483 486 496 496 507 513 514 516
Rev. 2.00 Mar 09, 2006 page xix of xxvi
11.4.1 Example of DMA Data Transfer Between SCIF and External Memory.............. 516 11.5 Usage Notes ...................................................................................................................... 516
Section 12 16-Bit Free-Running Timer (FRT)............................................................ 519
12.1 Overview........................................................................................................................... 12.1.1 Features................................................................................................................ 12.1.2 Block Diagram..................................................................................................... 12.1.3 Pin Configuration................................................................................................. 12.1.4 Register Configuration......................................................................................... 12.2 Register Descriptions ........................................................................................................ 12.2.1 Free-Running Counter (FRC) .............................................................................. 12.2.2 Output Compare Registers A and B (OCRA and OCRB).................................... 12.2.3 Input Capture Register (FICR)............................................................................. 12.2.4 Timer Interrupt Enable Register (TIER) .............................................................. 12.2.5 Free-Running Timer Control/Status Register (FTCSR)....................................... 12.2.6 Timer Control Register (TCR)............................................................................. 12.2.7 Timer Output Compare Control Register (TOCR) .............................................. 12.3 CPU Interface.................................................................................................................... 12.4 Operation .......................................................................................................................... 12.4.1 FRC Count Timing .............................................................................................. 12.4.2 Output Timing for Output Compare .................................................................... 12.4.3 FRC Clear Timing................................................................................................ 12.4.4 Input Capture Input Timing ................................................................................. 12.4.5 Input Capture Flag (ICF) Setting Timing............................................................. 12.4.6 Output Compare Flag (OCFA, OCFB) Setting Timing ....................................... 12.4.7 Timer Overflow Flag (OVF) Setting Timing....................................................... 12.5 Interrupt Sources ............................................................................................................... 12.6 Example of FRT Use......................................................................................................... 12.7 Usage Notes ...................................................................................................................... 12.7.1 Contention between FRC Write and Clear........................................................... 12.7.2 Contention between FRC Write and Increment ................................................... 12.7.3 Contention between OCR Write and Compare Match......................................... 12.7.4 Internal Clock Switching and Counter Operation ................................................ 12.7.5 Timer Output (FTOA, FTOB) ............................................................................. 519 519 520 521 521 522 522 522 523 523 524 526 527 528 531 531 532 532 533 534 534 535 536 536 537 537 538 539 540 541
Section 13 Watchdog Timer (WDT).............................................................................. 543
13.1 Overview........................................................................................................................... 13.1.1 Features................................................................................................................ 13.1.2 Block Diagram..................................................................................................... 13.1.3 Pin Configuration.................................................................................................
Rev. 2.00 Mar 09, 2006 page xx of xxvi
543 543 544 544
13.1.4 Register Configuration......................................................................................... 13.2 Register Descriptions ........................................................................................................ 13.2.1 Watchdog Timer Counter (WTCNT)................................................................... 13.2.2 Watchdog Timer Control/Status Register (WTCSR) ........................................... 13.2.3 Reset Control/Status Register (RSTCSR) ............................................................ 13.2.4 Notes on Register Access..................................................................................... 13.3 Operation........................................................................................................................... 13.3.1 Operation in Watchdog Timer Mode ................................................................... 13.3.2 Operation in Interval Timer Mode ....................................................................... 13.3.3 Operation when Standby Mode is Cleared........................................................... 13.3.4 Timing of Overflow Flag (OVF) Setting ............................................................. 13.3.5 Timing of Watchdog Timer Overflow Flag (WOVF) Setting.............................. 13.4 Usage Notes ...................................................................................................................... 13.4.1 Contention between WTCNT Write and Increment............................................. 13.4.2 Changing CKS2 to CKS0 Bit Values................................................................... 13.4.3 Switching between Watchdog Timer Mode and Interval Timer Mode................ 13.4.4 System Reset with WDTOVF.............................................................................. 13.4.5 Internal Reset in Watchdog Timer Mode.............................................................
545 545 545 546 547 549 550 550 552 552 553 553 554 554 554 554 555 555
Section 14 Serial Communication Interface with FIFO (SCIF)............................. 557
14.1 Overview........................................................................................................................... 14.1.1 Features ................................................................................................................ 14.1.2 Block Diagrams ................................................................................................... 14.1.3 Pin Configuration................................................................................................. 14.1.4 Register Configuration......................................................................................... 14.2 Register Descriptions ........................................................................................................ 14.2.1 Receive Shift Register (SCRSR).......................................................................... 14.2.2 Receive FIFO Data Register (SCFRDR) ............................................................. 14.2.3 Transmit Shift Register (SCTSR) ........................................................................ 14.2.4 Transmit FIFO Data Register (SCFTDR) ............................................................ 14.2.5 Serial Mode Register (SCSMR)........................................................................... 14.2.6 Serial Control Register (SCSCR)......................................................................... 14.2.7 Serial Status 1 Register (SC1SSR)....................................................................... 14.2.8 Serial Status 2 Register (SC2SSR)....................................................................... 14.2.9 Bit Rate Register (SCBRR).................................................................................. 14.2.10 FIFO Control Register (SCFCR) ......................................................................... 14.2.11 FIFO Data Count Register (SCFDR) ................................................................... 14.2.12 FIFO Error Register (SCFER) ............................................................................. 14.2.13 IrDA Mode Register (SCIMR)............................................................................. 14.3 Operation........................................................................................................................... 557 557 559 560 561 562 562 562 563 563 564 567 570 575 578 586 588 589 589 591
Rev. 2.00 Mar 09, 2006 page xxi of xxvi
14.3.1 Overview.............................................................................................................. 14.3.2 Operation in Asynchronous Mode ....................................................................... 14.3.3 Multiprocessor Communication Function............................................................ 14.3.4 Operation in Synchronous Mode ......................................................................... 14.3.5 Use of Transmit/Receive FIFO Buffers ............................................................... 14.3.6 Operation in IrDA Mode...................................................................................... 14.4 SCIF Interrupt Sources and the DMAC ............................................................................ 14.5 Usage Notes ......................................................................................................................
591 593 605 613 623 626 630 631
Section 15 Serial I/O with FIFO (SIOF)....................................................................... 637
15.1 Overview........................................................................................................................... 15.1.1 Features................................................................................................................ 15.2 Register Configuration...................................................................................................... 15.2.1 Receive Shift Register (SIRSR) ........................................................................... 15.2.2 Receive Data Register (SIRDR) .......................................................................... 15.2.3 Transmit Shift Register (SITSR).......................................................................... 15.2.4 Transmit Data Register (SITDR) ......................................................................... 15.2.5 Serial Control Register (SICTR).......................................................................... 15.2.6 Serial Status Register (SISTR)............................................................................. 15.2.7 Receive Control Data Register (SIRCDR)........................................................... 15.2.8 Transmit Control Data Register (SITCDR) ......................................................... 15.2.9 FIFO Control Register (SIFCR)........................................................................... 15.2.10 FIFO Data Count Register (SIFDR) .................................................................... 15.3 Operation .......................................................................................................................... 15.3.1 Input when TRMD = 0 in SIFCR......................................................................... 15.3.2 Output when TRMD = 0 in SIFCR...................................................................... 15.3.3 Output when TRMD = 1 in SIFCR...................................................................... 15.4 SIOF Interrupt Sources and DMAC.................................................................................. 637 637 639 639 640 641 641 642 645 648 649 649 653 654 654 657 661 663
Section 16 Serial I/O (SIO)............................................................................................... 665
16.1 Overview........................................................................................................................... 16.1.1 Features................................................................................................................ 16.2 Register Configuration...................................................................................................... 16.2.1 Receive Shift Register (SIRSR) ........................................................................... 16.2.2 Receive Data Register (SIRDR) .......................................................................... 16.2.3 Transmit Shift Register (SITSR).......................................................................... 16.2.4 Transmit Data Register (SITDR) ......................................................................... 16.2.5 Serial Control Register (SICTR).......................................................................... 16.2.6 Serial Status Register (SISTR)............................................................................. 16.3 Operation ..........................................................................................................................
Rev. 2.00 Mar 09, 2006 page xxii of xxvi
665 665 668 669 669 670 670 671 673 675
16.3.1 Input ..................................................................................................................... 675 16.3.2 Output .................................................................................................................. 676 16.4 SIO Interrupt Sources and DMAC .................................................................................... 679
Section 17 16-Bit Timer Pulse Unit (TPU).................................................................. 681
17.1 Overview........................................................................................................................... 17.1.1 Features ................................................................................................................ 17.1.2 Block Diagram ..................................................................................................... 17.1.3 Pin Configuration................................................................................................. 17.1.4 Register Configuration......................................................................................... 17.2 Register Descriptions ........................................................................................................ 17.2.1 Timer Control Register (TCR) ............................................................................. 17.2.2 Timer Mode Register (TMDR) ............................................................................ 17.2.3 Timer I/O Control Register (TIOR) ..................................................................... 17.2.4 Timer Interrupt Enable Register (TIER) .............................................................. 17.2.5 Timer Status Register (TSR)................................................................................ 17.2.6 Timer Counter (TCNT)........................................................................................ 17.2.7 Timer General Register (TGR) ............................................................................ 17.2.8 Timer Start Register (TSTR)................................................................................ 17.2.9 Timer Synchronous Register (TSYR) .................................................................. 17.3 Interface to Bus Master ..................................................................................................... 17.3.1 16-Bit Registers ................................................................................................... 17.3.2 8-Bit Registers ..................................................................................................... 17.4 Operation........................................................................................................................... 17.4.1 Overview.............................................................................................................. 17.4.2 Basic Functions.................................................................................................... 17.4.3 Synchronous Operation........................................................................................ 17.4.4 Buffer Operation .................................................................................................. 17.4.5 PWM Modes ........................................................................................................ 17.4.6 Phase Counting Mode .......................................................................................... 17.5 Interrupts ........................................................................................................................... 17.5.1 Interrupt Sources and Priorities............................................................................ 17.5.2 DMAC Activation................................................................................................ 17.6 Operation Timing .............................................................................................................. 17.6.1 Input/Output Timing ............................................................................................ 17.6.2 Interrupt Signal Timing........................................................................................ 17.7 Usage Notes ...................................................................................................................... 17.8 Usage Notes ...................................................................................................................... 17.8.1 Clearing Flags in TSR0 to TSR2 ......................................................................... 17.8.2 DMA Transfer by TPU0 ...................................................................................... 681 681 684 685 686 687 687 690 692 699 701 704 705 705 706 707 707 707 709 709 710 716 718 721 726 731 731 732 733 733 737 740 750 750 750
Rev. 2.00 Mar 09, 2006 page xxiii of xxvi
Section 18 User Debug Interface (H-UDI) .................................................................. 751
18.1 Overview........................................................................................................................... 18.1.1 Features................................................................................................................ 18.1.2 H-UDI Block Diagram......................................................................................... 18.1.3 Pin Configuration................................................................................................. 18.1.4 Register Configuration......................................................................................... 18.2 External Signals ................................................................................................................ 18.2.1 Test Clock (TCK) ................................................................................................ 18.2.2 Test Mode Select (TMS)...................................................................................... 18.2.3 Test Data Input (TDI) .......................................................................................... 18.2.4 Test Data Output (TDO) ...................................................................................... 18.2.5 Test Reset (TRST) ............................................................................................... 18.3 Register Descriptions ........................................................................................................ 18.3.1 Instruction Register (SDIR) ................................................................................. 18.3.2 Status Register (SDSR)........................................................................................ 18.3.3 Data Register (SDDR) ......................................................................................... 18.3.4 Bypass Register (SDBPR) ................................................................................... 18.3.5 Boundary scan register (SDBSR) ........................................................................ 18.3.6 ID code register (SDIDR) .................................................................................... 18.4 Operation .......................................................................................................................... 18.4.1 TAP Controller .................................................................................................... 18.4.2 H-UDI Interrupt and Serial Transfer.................................................................... 18.4.3 H-UDI Reset ........................................................................................................ 18.5 Boundary Scan .................................................................................................................. 18.5.1 Supported Instructions ......................................................................................... 18.5.2 Notes on Use........................................................................................................ 18.6 Usage Notes ...................................................................................................................... 751 751 752 753 753 754 754 754 754 755 755 755 755 757 758 758 758 770 771 771 772 775 775 775 777 777
Section 19 Pin Function Controller (PFC) ................................................................... 781
19.1 Overview........................................................................................................................... 781 19.2 Register Configuration...................................................................................................... 783 19.3 Register Descriptions ........................................................................................................ 783 19.3.1 Port A Control Register (PACR) ......................................................................... 783 19.3.2 Port A I/O Register (PAIOR)............................................................................... 786 19.3.3 Port B Control Registers (PBCR, PBCR2) .......................................................... 787 19.3.4 Port B I/O Register (PBIOR) ............................................................................... 793
Section 20 I/O Ports............................................................................................................ 795
20.1 Overview........................................................................................................................... 795 20.2 Port A................................................................................................................................ 795
Rev. 2.00 Mar 09, 2006 page xxiv of xxvi
20.2.1 Register Configuration......................................................................................... 20.2.2 Port A Data Register (PADR) .............................................................................. 20.3 Port B ................................................................................................................................ 20.3.1 Register Configuration......................................................................................... 20.3.2 Port B Data Register (PBDR) ..............................................................................
796 796 797 797 798
Section 21 Power-Down Modes...................................................................................... 799
21.1 Overview........................................................................................................................... 21.1.1 Power-Down Modes ............................................................................................ 21.1.2 Register ................................................................................................................ 21.2 Register Descriptions ........................................................................................................ 21.2.1 Standby Control Register 1 (SBYCR1) ............................................................... 21.2.2 Standby Control Register 2 (SBYCR2) ............................................................... 21.3 Sleep Mode ....................................................................................................................... 21.3.1 Transition to Sleep Mode..................................................................................... 21.3.2 Canceling Sleep Mode ......................................................................................... 21.4 Standby Mode ................................................................................................................... 21.4.1 Transition to Standby Mode................................................................................. 21.4.2 Canceling Standby Mode ..................................................................................... 21.4.3 Standby Mode Cancellation by NMI Interrupt..................................................... 21.4.4 Clock Pause Function........................................................................................... 21.4.5 Notes on Standby Mode....................................................................................... 21.5 Module Standby Function ................................................................................................. 21.5.1 Transition to Module Standby Function............................................................... 21.5.2 Clearing the Module Standby Function ............................................................... 799 799 800 801 801 803 805 805 805 805 805 807 807 808 811 812 812 812
Section 22 Electrical Characteristics.............................................................................. 813
22.1 Absolute Maximum Ratings.............................................................................................. 22.2 DC Characteristics ............................................................................................................ 22.3 AC Characteristics ............................................................................................................ 22.3.1 Clock Timing ....................................................................................................... 22.3.2 Control Signal Timing ......................................................................................... 22.3.3 Bus Timing........................................................................................................... 22.3.4 Direct Memory Access Controller Timing........................................................... 22.3.5 Free-Running Timer Timing ................................................................................ 22.3.6 Serial Communication Interface Timing.............................................................. 22.3.7 Watchdog Timer Timing...................................................................................... 22.3.8 Serial I/O with FIFO / Serial I/O Timing............................................................. 22.3.9 User Debug Interface Timing............................................................................... 22.3.10 I/O Port Timing.................................................................................................... 813 814 816 817 821 823 861 862 864 868 869 872 873
Rev. 2.00 Mar 09, 2006 page xxv of xxvi
22.3.11 Ethernet Controller Timing.................................................................................. 875 22.3.12 STATS, BH, and BUSHiZ Signal Timing ........................................................... 878 22.4 AC Characteristic Test Conditions.................................................................................... 880
Appendix A On-Chip Peripheral Module Registers.................................................. 881
A.1 Addresses .......................................................................................................................... 881
Appendix B Pin States ....................................................................................................... 900
B.1 Pin States in Reset, Power-Down State, and Bus-Released State ..................................... 900
Appendix C Product Lineup............................................................................................. 904 Appendix D Package Dimensions .................................................................................. 905
Rev. 2.00 Mar 09, 2006 page xxvi of xxvi
Section 1 Overview
Section 1 Overview
1.1 Features of SuperH Microcomputer with On-Chip Ethernet Controller
The SH7616 is a CMOS single-chip microcontroller that integrates a high-speed CPU core using an original Renesas architecture with supporting functions required for an Ethernet system. The CPU has a RISC (Reduced Instruction Set Computer) type instruction set. The CPU basically operates at a rate of one instruction per cycle, offering a great improvement in instruction execution speed. In addition, the 32-bit internal architecture provides improved data processing power, and DSP functions have also been enhanced with the implementation of extended Harvard architecture DSP data bus functions. With this CPU, it has become possible to assemble low-cost, high-performance/high-functionality systems even for applications such as realtime control, which could not previously be handled by microcontrollers because of their high-speed processing requirements. The SH7616 also includes a maximum 4-kbyte cache, for greater CPU processing power when accessing external memory. The SH7616 is equipped with a media access controller (MAC) conforming to the IEEE802.3u standard, and an Ethernet controller that includes a media independent interface (MII) standard unit, enabling 10/100 Mbps LAN connection. Supporting functions necessary for system configuration are also provided, including RAM, timers, a serial communication interface with FIFO (SCIF), interrupt controller (INTC), and I/O ports. To improve the efficiency of frame transmission/reception, the processing power of the DMAC for the Ethernet controller is improved and the FIFO for the DMAC has 2 kbytes. A CAM match signal input function is provided for systems that require multiple MAC addresses. In serial I/O with three channels, one operates with the FIFO for better data processing power when connected to the codec.
Rev. 2.00 Mar 09, 2006 page 1 of 906 REJ09B0292-0200
Section 1 Overview
Table 1.1
Item CPU
Features
Specifications * * * Original Renesas architecture 32-bit internal architecture General register machine Sixteen 32-bit general registers Six 32-bit control registers (including 3 added for DSP use) Ten 32-bit system registers * RISC (Reduced Instruction Set Computer) type instruction set Fixed 16-bit instruction length for improved code efficiency Load-store architecture (basic operations are executed between registers) Delayed branch instructions reduce pipeline disruption during branches C-oriented instruction set * * * Instruction execution time: One instruction per cycle (16.0 ns/instruction at 62.5 MHz operation) Address space: Architecture supports 4 Gbytes On-chip multiplier: Multiply operations (32 bits x 32 bits 64 bits) and multiply-and-accumulate operations (32 bits x 32 bits + 64 bits 64 bits) executed in two to four cycles Five-stage pipeline
*
Rev. 2.00 Mar 09, 2006 page 2 of 906 REJ09B0292-0200
Section 1 Overview Item DSP Specifications * DSP engine Multiplier Arithmetic logic unit (ALU) Shifter DSP registers * Multiplier 16 bits x 16 bits 32 bits Single-cycle multiplier * DSP registers Two 40-bit data registers Six 32-bit data registers Modulo register (MOD, 32 bits) added to control registers Repeat counter (RC) added to status register (SR) Repeat start register (RS, 32 bits) and repeat end register (RE, 32 bits) added to control registers * DSP data bus Extended Harvard architecture Simultaneous access to two data buses and one instruction bus * Parallel processing Maximum of four parallel processes ALU operations, multiplication, and two loads or stores
* Address processors
Two address processors Address operations to access two memories * DSP data addressing modes Increment and index Each with or without modulo addressing * * Repeat control: Zero-overhead repeat (loop) control Instruction set 16-bit length (in case of load or store only) 32-bit length (including ALU operations and multiplication) Added SuperH microcontroller instructions for accessing DSP registers * Fifth and last pipeline stage is DSP stage
Rev. 2.00 Mar 09, 2006 page 3 of 906 REJ09B0292-0200
Section 1 Overview Item Cache Specifications * * * * * * * * * * * Interrupt controller (INTC) * * * * Mixed instruction/data type cache Maximum of 4 kbytes 4-way set-associative type 16-byte line length 64 cache tag entries 16-byte write-back buffer Selection of write-through or write-back mode for data writes LRU replacement algorithm Can also be used as 2-kbyte cache and 2-kbyte RAM (2-way cache mode) Mixed instruction/data cache, instruction cache, or data cache mode can be set 1-cycle reads, 2-cycle writes (in write-back mode) 16 priority levels can be set On-chip supporting module interrupt vector numbers can be set 41 internal interrupt sources The E-DMAC interrupt (EINT) is input to the INTC as the OR of 22 EtherC and E-DMAC interrupt sources (max.). Thus, from the viewpoint of the INTC, there is one EtherC/E-DMAC interrupt source. Five external interrupt pins (NMI, IRL0 to IRL3) 15 external interrupt sources (encoded input) can also be selected for pins IRL0 to IRL3 (IRL interrupts) IRL interrupt vector number setting can also be selected (selection of auto vector or external vector) Provision for IRQ interrupt setting (low-level, rising-edge, falling-edge, both-edge detection)
* * * *
Rev. 2.00 Mar 09, 2006 page 4 of 906 REJ09B0292-0200
Section 1 Overview Item User break controller (UBC), 4 channels (A, B, C, D) Specifications * Interrupt generation based on independent or sequential conditions for channels A, B, C, D Three sequential setting patterns: A B C D, B C D, CD * Settable break conditions: Address, data (channels C and D only), bus master (CPU/DMAC), bus cycle (instruction fetch/data access), read/write, operand cycle (byte/word/longword) User break interrupt generated on occurrence of break condition Processing can be stopped before or after instruction execution in instruction fetch cycle Break with specification of number of executions (channels C and D only) Settable number of executions: max. 2 * PC trace function Branch source/branch destination can be traced in branch instruction fetch (max. 8 addresses (4 pairs))
12
* * *
- 1 (4095)
Rev. 2.00 Mar 09, 2006 page 5 of 906 REJ09B0292-0200
Section 1 Overview Item Specifications Address space divided into five areas (CS0 to CS4, max. linear 32 Mbytes each) Memory types such as DRAM, synchronous DRAM, burst ROM, can be specified for each area Two synchronous DRAM spaces (CS2, CS3); CS3 also supports DRAM Bus width (8, 16, 32 bits) can be selected for each area Wait state insertion control for each area Control signal output for each area Endian can be set for CS2 and CS4 * Cache Cache area/cache-through area selection by access address Selection of write-through or write-back mode * Refresh functions CAS-before-RAS refreshing (auto refreshing) or self-refreshing Refresh interval settable by means of refresh counter and clock select setting Concentrated refreshing according to refresh count setting (1, 2, 4, 6, 8) Refresh request output possible (REFOUT) * Direct DRAM interface Multiplexed row address/column address output Fast page mode burst transfer and continuous access when reading EDO mode TP cycle generation to secure RAS precharge time * Direct synchronous DRAM interface Multiplexed row address/column address output Bank-active mode (valid for CS3 only) Selection of burst read/single write mode or burst read/burst write mode * * Bus arbitration (BRLS, BGR) Refresh counter can be used as interval timer Interrupt request generated on compare match (CMI interrupt request signal)
Bus state controller * (BSC)
Rev. 2.00 Mar 09, 2006 page 6 of 906 REJ09B0292-0200
Section 1 Overview Item Direct memory access controller (DMAC), 2 channels Specifications * * * * 4-Gbyte address space, maximum 16M (16,777,216) transfers Selection of 8-bit, 16-bit, 32-bit, or 16-byte transfer data length Parallel execution of CPU instruction processing and DMA operation possible in case of cache hit Selection of dual address or single address mode Single address (data transfer rate of one transfer unit in one bus cycle) Dual address (data transfer rate of one transfer unit in two bus cycles) When synchronous DRAM is connected, 16-byte continuous read continuous write transfer is possible (dual) * * * * When SDRAM is connected, clocked single-address transfer is possible at rates up to 31.25 MHz Cycle stealing or burst transfer Relative channel priorities can be set (fixed mode/round robin mode) DMA transfer is possible for the following devices: External memory, on-chip memory, on-chip supporting modules (excluding DMAC, BSC, UBC, cache, E-DMAC, EtherC) * * * On-chip RAM Ethernet controller direct memory access controller (E-DMAC), 2 channels * * * * * * * * * * External requests, DMA transfer requests from on-chip supporting modules, auto requests Interrupt request (DEIn) can be issued to CPU at end of data transfer DACK used for DREQ sampling (however, there is always one overrun as there is one acceptance before first DACK) 4-kbyte X-RAM 4-kbyte Y-RAM Transfer possible between EtherC and external memory/on-chip memory 16-byte burst transfer possible Single address transfer Chain block transfer 32-bit transfer data width 4-Gbyte address space Data transfer possible from across byte boundaries in transmission Each transmit and receive FIFO includes 2 kbytes
Rev. 2.00 Mar 09, 2006 page 7 of 906 REJ09B0292-0200
Section 1 Overview Item Ethernet controller (EtherC) Specifications * MAC (Media Access Control) functions Data frame assembly/disassembly (IEEE802.3-compliant frames) CSMA/CD link management (collision avoidance, processing in case of collision) CRC processing Supports full-duplex transmission/reception Transmitting and receiving short and long packets * Compatible with MII (Media Independent Interface) standard Converts 8-bit stream data from MAC level to MII nibble stream (4 bits) Station management (STA) functions 18 TTL-level signals * * Serial communication interface with FIFO (SCIF), 2 channels * Variable transfer rate: 10/100 Mbps Magic PacketTM* (with WOL (Wake On LAN) output) CAM match signal input function Asynchronous mode Data length: 7 or 8 bits Stop bit length: 1 or 2 Parity: Even, odd, or none Receive error detection: Parity errors, framing errors, overrun errors Break detection * Synchronous mode One serial communication format (8-bit data length) Receive error detection: Overrun errors * * * * * IrDA mode (conforming to IrDA 1.0) Simultaneous transmission/reception (full-duplex) capability Half-duplex communication used for IrDA communication Built-in dedicated baud rate generator allows selection of bit rate Built-in 16-stage transmit and receive FIFOs enable high-speed, continuous communication Internal or external (SCK) transmit/receive clock source
Note: * Magic Packet is a registered trademark of Advanced Micro Devices, Inc.
Rev. 2.00 Mar 09, 2006 page 8 of 906 REJ09B0292-0200
Section 1 Overview Item Serial communication interface with FIFO (SCIF), 2 channels Specifications * Four interrupt sources Transmit FIFO data empty Break Receive FIFO data full Receive error * * * Serial I/O with FIFO * (SIOF) * * * * * Serial I/O (SIO), 2 channels * * * * * * Built-in modem control functions (RTS, CTS) Detection of transmit and receive FIFO register data quantity and number of receive FIFO register transmit data errors Timeout error (DR) can be detected during reception Full-duplex operation (independent transmit and receive registers, and independent transmit and receive clocks) Transmit and receive FIFO for primary data/transmit and receive buffer for control data (enabling continuous transmission/reception) Interval transfer mode and continuous transfer mode Choice of 8- or 16-bit data length Data transfer communication by means of polling or interrupts Choice of MSB- or LSB-first transfer for data I/O Full-duplex operation (independent transmit and receive registers, and independent transmit and receive clocks) Transmit/receive ports with double-buffer structure (enabling continuous transmission/reception) Interval transfer mode and continuous transfer mode Choice of 8- or 16-bit data length Data transfer communication by means of polling or interrupts MSB-first transfer between SIO and data I/O
Rev. 2.00 Mar 09, 2006 page 9 of 906 REJ09B0292-0200
Section 1 Overview Item User debug interface (H-UDI) Specifications * Conforms to IEEE1149.1 standard Five test signals (TCK, TDI, TDO, TMS, TRST) TAP controller Instruction register Data register Bypass register * Test mode that conforms to the IEEE1149.1 standard Standard instructions: BYPASS, SAMPLE/PRELOAD, and EXTEST Optional instructions: CLAMP, HIGHZ, and IDCODE * * Timer pulse unit (TPU), 3 channels * * H-UDI interrupt
H-UDI interrupt request to INTC
Reset hold Maximum 8-pulse input/output Total of eight timer general registers (TGR) (four for channel 0, two each for channels 1 and 2) Waveform output by compare match: Selection of 0, 1, or toggle output Input capture function: Selection of rising-edge, falling-edge, or bothedge detection Counter clear operation: Counter clearing possible by compare match or input capture Synchronous operation: Multiple timer counters (TCNT) can be written to simultaneously; simultaneous clearing by compare match and input capture possible; simultaneous register input/output possible by counter synchronous operation PWM mode: Any PWM output duty can be set; maximum 7-phase PWM output possible by combination with synchronous operation * Buffer operation settable for channel 0 Input capture register double-buffering possible Automatic rewriting of output compare register possible * * Phase counting mode settable independently for channels 1 and 2 Two-phase encoder pulse up/down-count possible 13 interrupt sources For channel 0, four compare match/input capture dual-function interrupts and one overflow interrupt can be requested independently For channels 1 and 2, two compare match/input capture dual-function interrupts, one overflow interrupt, and one underflow interrupt can be requested independently
Rev. 2.00 Mar 09, 2006 page 10 of 906 REJ09B0292-0200
Section 1 Overview Item 16-bit free-running timer (FRT), 1 channel Specifications * Choice of four counter input clocks Three internal clocks (P/8, P/32, P/128) External clock (enabling external event counting) * * * * Two independent comparators (allowing generation of two waveform outputs) Input capture (choice of rising edge or falling edge) Counter clear specification Counter value can be cleared by compare match A Four interrupt sources Two compare match sources (OCIA, OCIB) One input capture source (ICI) One overflow source (OVI) Watchdog timer (WDT), 1 channel * * * * Clock pulse generator (CPG) * * * * * Can be switched between watchdog timer mode and interval timer mode Internal reset, external signal (WDTOVF), or interrupt generated on count overflow Used when standby mode is cleared or the clock frequency is changed, and in clock pause mode Selection of eight counter input clocks Built-in clock pulse generator Selection of crystal or external clock as clock source Built-in clock-multiplication PLL circuits Built-in PLL circuit for phase synchronization between external clock and internal clock CPU/DSP core clock (I), peripheral module clock (P), and external interface clock (E) frequencies can be scaled independently
Rev. 2.00 Mar 09, 2006 page 11 of 906 REJ09B0292-0200
Section 1 Overview Item System controller (SYSC) Specifications * * Selection of seven operating mode settings, three power-down modes Operating modes Control the method of clock generation (PLL ON/OFF) and clock division ratio * Power-down mode Sleep mode: CPU functions halted Standby mode: All functions halted Module standby function: Operation of FRT, SCIF, DMAC, UBC, DSP, TPU, and SIO on-chip supporting modules is halted selectively I/O ports * 29 input/output ports
Rev. 2.00 Mar 09, 2006 page 12 of 906 REJ09B0292-0200
Section 1 Overview
1.2
Block Diagram
32-bit cache data bus
16-bit internal data bus
CPU
16-bit internal data bus
Cache address bus
Internal address bus
Internal address bus
Interrupt controller DSP
Serial I/O with FIFO
User debug interface X-RAM Serial I/O Y-RAM Serial communication interface with FIFO Timer pulse unit User break controller Free-running timer Watchdog timer Clock pulse generator
Cache address array/data array
Cache controller
Bus state controller Direct memory access controller Ethernet controller Ethernet controller direct memory access controller
System controller
16-bit peripheral data bus
External bus interface
Figure 1.1 Block Diagram of SH7616
Rev. 2.00 Mar 09, 2006 page 13 of 906 REJ09B0292-0200
32-bit internal data bus
Peripheral address bus
I/O ports
Internal address bus
Section 1 Overview
1.3
1.3.1
Pin Description
Pin Arrangement
Figure 1.2 shows the pin arrangement.
PB11/SRS2/CTS/STATS0 PVCC PB12/SRCK2/RTS/STATS1 PB13/TXD1 PB14/RXD1 PB15/SCK1 VSS VSS BGR VCC VCC BRLS DACK0 DACK1 DREQ0 DREQ1 BH BUSHiZ CS4 CS3 CS2 CS1 CS0 RD/WR VCC BS VSS REFOUT RD CKE CAS0 CAS1 CAS2 CAS3 DQMLL/WE0 DQMLU/WE1 DQMUL/WE2 DQMUU/WE3 CAS/OE RAS VCC WAIT VSS VSS VSS A24 VCC VCC A23 A22 A21 A20 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105
PVSS TIOCA1/SRXD2/PB10 TCLKC/TIOCB1/STCK2/PB9 TIOCA2/STS2/PB8 TCLKD/TIOCB2/STXD2/PB7 SCK2/SRCK1/PB6 RXD2/SRS1/PB5 TXD2/SRXD1/PB4 TIOCA0/STCK1/PB3 TIOCB0/STS1/PB2 PVCC TCLKA/TIOCC0/STXD1/PB1 PVSS WOL/TCLKB/TIOCD0/PB0 SRCK0/PA13 SRS0/PA12 SRXD0/PA11 STCK0/PA10 STS0/PA9 STXD0/PA8 WDTOVF/PA7 FTCI/PA6 PVCC FTI/PA5 PVSS FTOA/PA4 FTOB/CKPO LNKSTA/PA2 EXOUT/PA1 PA0/CAMSEN RXER RXDV COL CRS PVSS RXCLK PVCC ERXD0 ERXD1 ERXD2 ERXD3 MDIO MDC PVCC TXCLK PVSS TXEN ETXD0 ETXD1 ETXD2 ETXD3 TXER
157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208
PLQP0208KA-A (Top view)
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 56 55 54 53
A19 A18 A17 VSS A16 VCC A15 A14 A13 A12 A11 A10 A9 VSS A8 VCC A7 A6 A5 A4 A3 A2 A1 VCC A0 VSS VSS D31 VCC D30 D29 D28 D27 D26 D25 VSS D24 VCC VCC D23 D22 D21 D20 VSS VSS D19 VCC D18 D17 D16 D15 D14
Note: * When doing debugging using the E10A emulator, this pin is used for mode switching. It should be connected to Vss when using the E10A emulator and connected to Vcc when using a normal user system.
Figure 1.2 SH7616 Pin Arrangement (PLQP0208KA-A)
Rev. 2.00 Mar 09, 2006 page 14 of 906 REJ09B0292-0200
IRL3 IRL2 IRL1 IRL0 NMI ASEMODE* VSS RES PLLVSS PLLCAP2 PLLCAP1 PLLVCC MD4 MD3 MD2 MD1 MD0 VCC EXTAL VSS XTAL VCC CKIO CKPREQ/CKM CKPACK VSS IVECF TDO TDI TCK TMS TRST VCC D0 VSS D1 D2 D3 D4 D5 D6 VCC D7 D8 VSS D9 D10 D11 D12 VCC D13 VSS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
Body size Height Pin pitch
28 x 28 (mm) 1.7 (mm) 0.5 (mm)
Section 1 Overview
1.3.2 Table 1.2
Type Power
Pin Functions Pin Functions
Symbol VCC I/O Input Name Power Function For connection to the power supply. Connect all VCC pins to the system power supply. The chip will not operate if there are any open pins For connection to ground. Connect all VSS pins to the system ground. The chip will not operate if there are any open pins Power supply for the I/O circuits Ground for the I/O circuits For connection to a crystal resonator For connection to a crystal resonator, or used as external clock input pin System clock input/output pin Clock pause request input Clock pause acknowledge signal On-chip peripheral clock (P) output Used as the external clock input or internal clock output pin Used as the clock pause request pin for changing the frequency of the clock input from the CKIO pin, or halting the clock Indicates that the chip is in the clock pause state (standby state) internally Outputs the on-chip peripheral clock (P)
VSS
Input
Ground
PVCC PVSS Clock XTAL EXTAL CKIO
Input Input Output Input I/O
I/O circuit power I/O circuit ground Crystal input/ output pin
CKPREQ/ CKM CKPACK
Input
Output
CKPO
Output
PLLCAP1 PLLCAP2 PLLVCC PLLVSS
Input Input Input Input
PLL capacitance Connects capacitance for operation of connection pins PLL circuit 1 Connects capacitance for operation of PLL circuit 2 PLL power PLL ground PLL oscillator power supply PLL oscillator ground
Rev. 2.00 Mar 09, 2006 page 15 of 906 REJ09B0292-0200
Section 1 Overview Type System control Symbol RES I/O Input Name Reset Function When RES = 0 and NMI = 1, the chip enters the power-on reset state. When RES = 0 and NMI = 0, the chip enters the manual reset state Counter overflow signal output in watchdog timer mode Indicates that the bus has been released to an external device. The device that output the BRLS signal recognizes that the bus has been acquired when it receives the BGR signal Driven low when an external device requests release of the bus The operating mode is specified by the levels at these pins Inputs the nonmaskable interrupt request signal These pins input maskable interrupt request signals
WDTOVF BGR
Output Output
Watchdog timer overflow Bus grant
BRLS Operating mode Interrupts MD0-MD4 NMI IRL3-IRL0
Input Input Input Input
Bus release Mode setting Nonmaskable interrupt External interrupt request input 0 to 3 Interrupt vector fetch cycle Bus cycle start Chip select 0 to 4 Wait Read Row address strobe
IVECF
Output
Indicates an external vector read cycle
Bus control
BS
Output
Signal indicating the start of a bus cycle Asserted every data cycle in burst transfer Chip select signals indicating the area being accessed Wait state request signal Strobe signal indicating a read cycle DRAM/synchronous DRAM RAS signal
CS4-CS0 WAIT RD RAS
Output Input Output Output
Rev. 2.00 Mar 09, 2006 page 16 of 906 REJ09B0292-0200
Section 1 Overview Type Bus control Symbol CAS OE DQMUU/ WE3 DQMUL/ WE2 DQMLU/ WE1 DQMLL/ WE0 CAS3 CAS2 CAS1 CAS0 CKE REFOUT RD/WR BUSHiZ I/O Output Output Output Output Output Output Output Output Output Output Output Output Output Input Name Column address strobe Output enable Highest byte access Second byte access Third byte access Lowest byte access Column address strobe 3 Column address strobe 2 Column address strobe 1 Column address strobe 0 Clock enable Refresh out Read/write Bus high impedance Function Synchronous DRAM CAS signal EDO DRAM output enable signal Used in access in RAS down mode SRAM/synchronous DRAM highest byte select signal SRAM/synchronous DRAM second byte select signal SRAM/synchronous DRAM third byte select signal SRAM/synchronous DRAM lowest byte select signal DRAM highest byte select signal DRAM second byte select signal DRAM third byte select signal DRAM lowest byte select signal Synchronous DRAM clock enable signal Signal requesting refresh execution when the bus is released DRAM/synchronous DRAM write signal Signal used in combination with WAIT signal to place bus and strobe signals in the high-impedance state without the ending bus cycle Asserted at the start of a DMA burst, negated one bus cycle before the end of the burst CPU, DMAC, and E-DMAC status information
BH
Output
Burst hint
STATS0, 1
Output
Status
Rev. 2.00 Mar 09, 2006 page 17 of 906 REJ09B0292-0200
Section 1 Overview Type Bus control H-UDI Symbol A24-A0 D31-D0 TCK TMS TDI TDO TRST Ethernet controller (EtherC) I/O Output I/O Input Input Input Output Name Address bus Data bus Test clock Test mode select Test data input Test data output Test reset ASE mode input Transmitter clock Receive clock Transmit enable Transmit data 0-3 Transmit error Receive data enable Receive data 0-3 Receive error Carrier sense Collision Management data clock Function Address output Data input/output Test clock input Test mode select input signal Serial data input Serial data output Test reset input signal ASE mode/user mode select signal TX-EN, ETXD0-3, TX-ER timing reference signal RX-DV, ERXD0-3, RX-ER timing reference signal Signal indicating that transmit data on ETXD0-3 is ready 4-bit receive data Signal sending error status to another port Indicates that enable receive data on ERXD0-3 exist 4-bit receive data Reports error state that occurred during transfer of frame data Carrier detection notification signal Collision detection signal Reference clock signal for information transfer by MDIO
Input * Input ASEMODE TX-CLK RX-CLK TX-EN ETXD0-3 TX-ER RX-DV ERXD0-3 RX-ER CRS COL MDC MDIO Input Input Output Output Output Input Input Input Input Input Output I/O
Management Bidirectional signal for exchanging data input/output management information between STA and PHY
Note: * When carrying out debugging using the E10A emulator, this pin is used for mode switching. It should be connected to VSS when using the E10A emulator and connected to VCC when using a normal user system. When a boundary scan test is performed with the H-UDI, user mode must be used. A boundary scan test cannot be performed in ASE mode.
Rev. 2.00 Mar 09, 2006 page 18 of 906 REJ09B0292-0200
Section 1 Overview Type Ethernet controller (EtherC) Symbol LNKSTA EXOUT WOL CAMSEN Direct memory access controller (DMAC) DACK0, 1 I/O Input Output Output Input Output Name Link status Function Link status input from PHY
General-purpose General-purpose external output pin external output Wake on LAN CAM sense DMAC channel 0, 1 acknowledge DMAC channel 0, 1 request Transmit data output channel 1, 2 Receive data output channel 1, 2 Serial clock input/output channel 1, 2 Transmit request Transmit enable TPU timer clock input A, B, C, D Signal indicating detection of a Magic Packet CAM sense signal These pins output receiving a DMA transfer request to an external device
DREQ0, 1
Input
Pins that input DMA transfer requests from an external device SCIF channel 1 and 2 transmit data output pins SCIF channel 1 and 2 receive data input pins SCIF clock input/output pins
Serial comTXD1, 2 munication interface with FIFO (SCIF) RXD1, 2
Output
Input
SCK1, 2
I/O
RTS CTS Timer pulse unit (TPU) TCLKA TCLKB TCLKC TCLKD TIOCA0 TIOCB0 TIOCC0 TIOCD0 TIOCA1 TIOCB1
Output Input Input
SCIF channel 1 transmit request output pin SCIF channel 1 transmit enable input pin Pins that input an external clock to the TPU counter
I/O
TPU input capture/output compare (channel 0) TPU input capture/output compare (channel 1)
Channel 0 input capture input/ output compare output/PWM output pins
I/O
Channel 1 input capture input/ output compare output/PWM output pins
Rev. 2.00 Mar 09, 2006 page 19 of 906 REJ09B0292-0200
Section 1 Overview Type Timer pulse unit (TPU) Symbol TIOCA2 TIOCB2 I/O I/O Name TPU input capture/output compare (channel 2) Counter clock input Output compare A output Output compare B output Input capture input Serial receive data input 0 Serial receive clock input 0 Serial receive synchronization clock input 0 Serial transmit data output 0 Serial transmit clock input 0 Function Channel 2 input capture input/output compare output/PWM output pins
16-bit free-running timer (FRT)
FTCI FTOA FTOB FTI
Input Output Output Input Input Input Input
FRC counter clock input pin Output compare A output pin Output compare B output pin Input capture input pin Serial receive data input ports Serial receive clock ports Serial receive synchronization input ports Serial data output ports Serial transmit clock ports
Serial I/O with FIFO (SIOF)
SRXD0 SRCK0 SRS0
STXD0 STCK0 STS0
Output Input I/O
Serial transmit Serial transmit synchronization synchronization input/output ports clock input/output 0 Serial receive data input 1, 2 Serial receive clock input 1, 2 Serial receive synchronization input 1, 2 Serial transmit data output 1, 2 Serial transmit clock input 1, 2 Serial transmit synchronization input/output 1, 2 Serial receive data input ports Serial receive clock ports Serial receive synchronization input ports Serial data output ports Serial transmit clock ports Serial transmit synchronization input/output ports
Serial I/O (SIO)
SRXD1, 2 SRCK1, 2 SRS1, 2
Input Input Input
STXD1, 2 STCK1, 2 STS1, 2
Output Input I/O
Rev. 2.00 Mar 09, 2006 page 20 of 906 REJ09B0292-0200
Section 1 Overview Type I/O ports Symbol I/O Name General port General port Function General input/output port pins Input or output can be specified bit by bit PB0-PB15 I/O General input/output port pins Input or output can be specified bit by bit Note: * PA3 cannot be used; CKPO is valid instead.
PA0-PA13* I/O
1.3.3 Table 1.3
No. 12 9 11 10 19 21 23 24 25 8 13 14 15 16 17 5 1 2 3 4 27
Pin Multiplexing Pin Multiplexing
Function 2 Function 3 Function 4 Type Clocks
Function 1 PLLVCC PLLVSS PLLCAP1 PLLCAP2 EXTAL XTAL CKIO CKPREQ/CKM CKPACK RES MD4 MD3 MD2 MD1 MD0 NMI IRL3 IRL2 IRL1 IRL0 IVECF
9 pins System control
6 pins Interrupts
6 pins
Rev. 2.00 Mar 09, 2006 page 21 of 906 REJ09B0292-0200
Section 1 Overview No. 131 138 137 136 135 134 148 145 115 128 117 118 119 120 121 122 123 124 125 126 127 129 133 139 140 Function 1 BS CS4 CS3 CS2 CS1 CS0 BGR BRLS WAIT RD RAS CAS/OE DQMUU/WE3 DQMUL/WE2 DQMLU/WE1 DQMLL/WE0 CAS3 CAS2 CAS1 CAS0 CKE REFOUT RD/WR BUSHiZ BH 25 pins Function 2 Function 3 Function 4 Type Bus control
Rev. 2.00 Mar 09, 2006 page 22 of 906 REJ09B0292-0200
Section 1 Overview No. 111 108 107 106 105 104 103 102 100 98 97 96 95 94 93 92 90 88 87 86 85 84 83 82 80 Function 1 A24 A23 A22 A21 A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 25 pins Function 2 Function 3 Function 4 Type Address bus
Rev. 2.00 Mar 09, 2006 page 23 of 906 REJ09B0292-0200
Section 1 Overview No. 77 75 74 73 72 71 70 68 65 64 63 62 59 57 56 55 54 53 51 49 48 47 46 44 43 41 40 39 38 37 36 34 Function 1 D31 D30 D29 D28 D27 D26 D25 D24 D23 D22 D21 D20 D19 D18 D17 D16 D15 D14 D13 D12 D11 D10 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0 32 pins Function 2 Function 3 Function 4 Type Data bus
Rev. 2.00 Mar 09, 2006 page 24 of 906 REJ09B0292-0200
Section 1 Overview No. 30 31 29 28 32 6 201 192 203 207 206 205 204 208 188 197 196 195 194 187 190 189 199 198 143 144 141 142 Function 1 TCK TMS TDI TDO TRST ASEMODE* TX-CLK RX-CLK TX-EN ETXD3 ETXD2 ETXD1 ETXD0 TX-ER RX-DV ERXD3 ERXD2 ERXD1 ERXD0 RX-ER CRS COL MDC MDIO DACK1 DACK0 DREQ1 DREQ0 4 pins 18 pins DMAC 5 V I/O compatibility 6 pins EtherC Function 2 Function 3 Function 4 Type H-UDI
Note: * When carrying out debugging using the E10A emulator, this pin is used for mode switching. It should be connected to VSS when using the E10A emulator (ASE mode). When using the chip in the normal user system, and not using the E10A emulator (user mode), connect this pin to VCC. When a boundary scan test is performed with the H-UDI, user mode must be used. A boundary scan test cannot be performed in ASE mode.
Rev. 2.00 Mar 09, 2006 page 25 of 906 REJ09B0292-0200
Section 1 Overview Function 1 [00]* PB15 PB14 PB13 PB12 PB11 PB10 PB9 PB8 PB7 PB6 PB5 PB4 PB3 PB2 PB1 PB0 PA13 PA12 PA11 PA10 PA9 PA8 WDTOVF PA6 PA5 PA4 CKPO PA2 PA1 PA0 SRCK0 SRS0 SRXD0 STCK0 STS0 STXD0 PA7 FTCI FTI FTOA FTOB LNKSTA EXOUT CAMSEN 14 pins SRCK2 SRS2 SRXD2 STCK2 STS2 STXD2 SRCK1 SRS1 SRXD1 STCK1 STS1 STXD1 Function 2 [01]* Function 3 [10]* SCK1 RXD1 TXD1 RTS CTS TIOCA1 TIOCB1/TCLKC TIOCA2 TIOCB2/TCLKD SCK2 RXD2 TXD2 TIOCA0 TIOCB0 TIOCC0/TCLKA TIOCD0/TCLKB WOL 16 pins Port A SIOF, FRT, WDT, EtherC 5 V I/O compatibility STATS1 STATS0 5 V I/O compatibility Function 4 [11]*
No. 151 152 153 154 156 158 159 160 161 162 163 164 165 166 168 170 171 172 173 174 175 176 177 178 180 182 183 184 185 186
Type Port B SCIF, SIO, TPU
Note: * Figures in square brackets indicate the settings of the mode bits (MD0, MD1) in the PFC in order to select the multiplex functions in port A [0:13] and port B [0:15]. WDTOVF: In a reset, this pin becomes an output pin. Rev. 2.00 Mar 09, 2006 page 26 of 906 REJ09B0292-0200
Section 1 Overview When used for general input/output, attention must be paid to the polarity of this pin.
1.4
Processing States
State Transitions: The CPU has five processing states: the reset state, exception handling state, bus-released state, program execution state, and power-down state. Figure 1.3 shows the state transitions.
From any state when RES = 0 and NMI = 1 From any state when RES = 0 and NMI = 0 RST = 0, NMI = 0 Power-on reset state RST = 0, NMI = 1 RST = 1, NMI = 1 Interrupt or DMA address error RST = 1, NMI = 0 Reset states Manual reset state
Exception-handling state
NMI interrupt Bus request cleared
Bus request
Exception End of exception handling
Bus-released state
Bus request received
Bus request cleared
CKPREQ = 1*
Program execution state
Bus request received
Bus request cleared SLEEP instruction (SBY = 0) MSTP bit cleared MSTP bit set
SBY bit set and CKPREQ = 0*
SLEEP instruction (SBY = 1)
Sleep mode
Standby mode
Module standby Power-down state Note: * clock pause function
Figure 1.3 Processing State Transitions
Rev. 2.00 Mar 09, 2006 page 27 of 906 REJ09B0292-0200
Section 1 Overview
* Reset State In this state, the CPU is reset. The reset state is entered when the RES pin goes low. The power-on reset state is entered if the NMI pin is high, and the manual reset state is entered if the NMI pin is low. * Exception Handling State The exception handling state is a transient state that occurs when the CPU alters the normal programming flow dues to a reset, interrupt, or other exception handling source. In the case of a reset, the CPU fetches the execution start address as the initial value of the program counter (PC) from the exception vector table, and the initial value of the stack pointer (SP), stores these values, branches to the start address, and begins program execution at that address. In the case of an interrupt, etc., the CPU references the SP and saves the PC and status register (SR) in the stack area. It fetches the start address of the exception service routine from the exception vector table, branches to that address, and begins program execution. Subsequently, the processing state is the program execution state. * Program Execution State In the program execution state the CPU executes program instructions in normal sequence. * Power-Down State In the power-down state the CPU stops operating to conserve power. The power-down state is entered by executing a SLEEP instruction. The power-down state includes two modes--sleep mode and standby mode--and a module standby function. * Bus-Released State In the bus-released state, the CPU releases the bus to a device that has requested it. Power-Down State: In addition to the normal program execution state, another CPU processing state called the power-down state is provided. In this state, CPU operation is halted and power consumption is reduced. The power-down state includes two modes--sleep mode and standby mode--and a module standby function. * Sleep Mode A transition to sleep mode is made if the SLEEP instruction is executed while the standby bit (SBY) is cleared to 0 in standby control register 1 (SBYCR1). In sleep mode CPU operations stop but data in the CPU's internal registers and in on-chip cache memory and on-chip RAM is retained. The functions of the on-chip supporting modules do not stop.
Rev. 2.00 Mar 09, 2006 page 28 of 906 REJ09B0292-0200
Section 1 Overview
* Standby Mode A transition to standby mode is made if the SLEEP instruction is executed while SBY is set to 1 in SBYCR1. In standby mode the CPU, the on-chip modules, and the oscillator all stop. When entering standby mode, the DMAC's DMA master enable bit should be cleared to 0. Also, the cache should be turned off before entering this mode. The contents of the cache and on-chip RAM are not retained in this mode. Standby mode is exited by means of a reset or an external NMI interrupt. When standby mode is exited, the normal program execution state is entered via the exception handling state after the elapse of the oscillation settling time. If a transition is made to standby mode using the clock pause function, it is possible to change the frequency of the CKIO pin input clock, or to stop the clock itself. When SBY in SBYCR1 is set to 1 and a low level is applied to the CKPREQ/CKM pin, a transition is made to standby mode and a low level is output from the CKPACK pin. The clock can then be stopped, or its frequency changed. On-chip supporting module states and pin states are the same as in the normal standby mode entered by means of the SLEEP instruction. A transition to the program execution state is made by applying a high level to the CKPREQ/CKM pin. In this mode the oscillator is halted, greatly reducing power consumption. * Module Standby Function A module standby function is provided for the following on-chip supporting modules: the direct memory access controller (DMAC), DSP, 16-bit free-running timer (FRT), serial communication interface with FIFO (SCIF), serial I/O with FIFO (SIOF), serial I/O (SIO), user break controller (UBC), and timer pulse unit (TPU). A module standby function is not supported for the Ethernet controller (EtherC) or the Ethernet direct memory access controller (E-DMAC). Setting one of module stop bits 11 to 3 and 1 (MSTP11 to MSTP3, MSTP1) to 1 in the standby control register (SBYCR1/2) stops the clock supply to the corresponding on-chip supporting module. Use of this function enables power consumption to be reduced. The module standby function is cleared by clearing the corresponding MSTP bit to 0. DSP instructions must not be used when the DSP has been placed in the module standby state. When using the DMAC module standby function, the direct memory access controller's DMA master enable bit should be cleared to 0.
Rev. 2.00 Mar 09, 2006 page 29 of 906 REJ09B0292-0200
Section 1 Overview
Table 1.4
Power-Down State
State On-chip Supporting Modules Operating On-Chip Cache or On-Chip RAM Held
Mode Sleep mode
Entering Conditions
Clock
CPU Halted
CPU Registers Held
Exiting Conditions 1. Interrupt 2. DMA address error 3. Power-on reset 4. Manual reset
Operating Executing SLEEP instruction while SBY bit is cleared in SBYCR1 Executing SLEEP instruction while SBY bit is set in SBYCR1 Halted
Standby mode
Halted
Halted and initialized*1
Held
Undefined
1. NMI interrupt 2. Power-on reset 3. Manual reset
Module standby function
Setting Operating MSTP bit corresponding to individual module
Operating (DSP halted)
Clock supply Held to specified module halted, module initialized*2
Held
1. Clearing MSTP bit 2. Power-on reset 3. Manual reset
Notes: 1. Depends on individual supporting module or pin. 2. DMAC and DSP registers and specified module interrupt vectors retain their set values.
Rev. 2.00 Mar 09, 2006 page 30 of 906 REJ09B0292-0200
Section 2 CPU
Section 2 CPU
2.1 Register Configuration
The register set consists of sixteen 32-bit general registers, six 32-bit control registers and ten 32bit system registers. This chip is upwardly compatible with the SH-1, SH-2 on the object code level. For this reason, several registers have been added to the previous SuperH microcontroller registers. The added registers are the three control registers: repeat start register (RS), repeat end register (RE), and modulo register (MOD) and the six system registers: DSP status register (DSR), and A0, A1, X0, X1, Y0 and Y1 among the DSP data registers. The general registers are used in the same manner as the SH-1, SH-2 with regard to SuperH microcontroller-type instructions. With regard to DSP type instructions, they are used as address and index registers for accessing memory. 2.1.1 General Registers
There are 16 general registers (Rn) numbered R0-R15, which are 32 bits in length. General registers are used for data processing and address calculation. With SuperH microcomputer type instructions, R0 is also used as an index register. Several instructions are limited to use of R0 only. R15 is used as the hardware stack pointer (SP). Saving and recovering the status register (SR) and program counter (PC) in exception processing is accomplished by referencing the stack using R15. With DSP type instructions, eight of the 16 general registers are used for the addressing of X, Y data memory and data memory (single data) using the I bus. R4, R5 are used as an X address register (Ax) for X memory accesses, and R8 is used as an X index register (Ix). R6, R7 are used as a Y address register (Ay) for Y memory accesses, and R9 is used as a Y index register (Iy). R2, R3, R4, R5 are used as a single data address register (As) for accessing single data using the I bus, and R8 is used as a single data index register (Is). DSP type instructions can simultaneously access X and Y data memory. There are two groups of address pointers for designating X and Y data memory addresses. Figure 2.1 shows the general registers.
Rev. 2.00 Mar 09, 2006 page 31 of 906 REJ09B0292-0200
Section 2 CPU
31 R0*1 R1 R2, [As]*3 R3, [As]*3 R4, [As, Ax]*3 R5, [As, Ax]*3 R6, [Ay]*3 R7, [Ay]*3 R8, [Ix, Is]*3 R9, [Iy]*3 R10 R11 R12 R13 R14 R15, SP *2 Notes: 1. R0 also functions as an index register in the indirect indexed register addressing mode and indirect indexed GBR addressing mode. In some instructions, only the R0 functions as a source register or destination register. 2. R15 functions as a hardware stack pointer (SP) during exception processing. 3. Used as memory address registers, memory index registers with DSP type instructions. 0
Figure 2.1 General Register Configuration With the assembler, symbol names are used for R2, R3 ... R9. If it is wished to use a name that makes clear the role of a register for DSP type instructions, a different register name (alias) can be used. This is written in the following manner for the assembler.
Ix: .REG (R8)
Rev. 2.00 Mar 09, 2006 page 32 of 906 REJ09B0292-0200
Section 2 CPU
The name Ix is an alias for R8. The other aliases are assigned as follows:
Ax0: Ax1: Ix: Ay0: Ay1: Iy: As0: As1: As2: As3: Is: .REG (R4) .REG (R5) .REG (R8) .REG (R6) .REG (R7) .REG (R9) .REG (R4) defined when an alias is required for single data transfer .REG (R5) defined when an alias is required for single data transfer .REG (R2) defined when an alias is required for single data transfer .REG (R3) defined when an alias is required for single data transfer .REG (R8) defined when an alias is required for single data transfer
2.1.2
Control Registers
The six 32-bit control registers consist of the status register (SR), repeat start register (RS), repeat end register (RE), global base register (GBR), vector base register (VBR), and modulo register (MOD). The SR register indicates processing states. The GBR register functions as a base address for the indirect GBR addressing mode, and is used for such as on-chip peripheral module register data transfers. The VBR register functions as the base address of the exception processing vector area (including interrupts). The RS and RE registers are used for program repeat (loop) control. The repeat count is designated in the SR register repeat counter (RC), the repeat start address in the RS register, and the repeat end address in the RE register. However, note that the address values stored in the RS and RE registers are not necessarily always the same as the physical start and end address values of the repeat. The MOD register is used for modulo addressing to buffer the repeat data. The modulo addressing designation is made by DMX or DMY, the modulo end address (ME) is designated in the upper 16 bits of the MOD register, and the modulo start address (MS) is designated in the lower 16 bits. Note that the DMX and DMY bits cannot simultaneously designate modulo addressing. Modulo addressing is possible with X and Y data transfer instructions (MOVX, MOVY). It is not possible with single data transfer instructions (MOVS).
Rev. 2.00 Mar 09, 2006 page 33 of 906 REJ09B0292-0200
Section 2 CPU
Figure 2.2 shows the control registers. Table 2.1 indicates the SR register bits.
Status register (SR) 31 28 27 16 15 12 11 10 9 8 7 43 210 0000 RC 0000 DMY DMX M Q I3 I2 I1 I0 RF1 RF0 S T Repeat start register (RS) 31 RS Repeat end register (RE) 31 RE Global base register (GBR) 31 GBR Vector base register (VBR) 31 VBR Modulo register (MOD) 31 ME ME: Modulo end address MS: Modulo start address
0
0
0
0
16 15 MS
0
Figure 2.2 Control Register Configuration
Rev. 2.00 Mar 09, 2006 page 34 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.1
Bit 27-16 11
SR Register Bits
Name (Abbreviation) Repeat counter (RC) Y pointer usage modulo addressing designation (DMY) X pointer usage modulo addressing designation (DMX) M bit Q bit Interrupt request mask (I3-I0) Repeat flags (RF1, RF0) Function Designate the repeat count (2-4095) for repeat (loop) control 1: modulo addressing mode becomes valid for Y memory address pointer, Ay (R6, R7) 1: modulo addressing mode becomes valid for X memory address pointer, Ax (R4, R5) Used by the DIV0S/U, DIV1 instructions Used by the DIV0S/U, DIV1 instructions Indicate the receive level of an interrupt request (0 to 15) Used in zero overhead repeat (loop) control. Set as below for an SETRC instruction For 1 step repeat 00 RE--RS=-4 For 2 step repeat 01 RE--RS=-2 For 3 step repeat 11 RE--RS=0 For 4 steps or more 10 RE--RS>0
10
9 8 7-4 3-2
1
Saturation arithmetic bit (S) T bit
Used with MAC instructions and DSP instructions 1: Designates saturation arithmetic (prevents overflows) For MOVT, CMP/cond, TAS, TST, BT, BT/S, BF, BF/S, SETT, CLRT and DT instructions, 0: represents false 1: represents true For ADDV/ADDC, SUBV/SUBC, DIV0U/DIV0S, DIV1, NEGC, SHAR/SHAL, SHLR/SHLL, ROTR/ROTL and ROTCR/ROTCL instructions, 1: represents occurrence of carry, borrow, overflow or underflow
0
31-28 15-12
0 bit
0: 0 is always read out; write a 0
Rev. 2.00 Mar 09, 2006 page 35 of 906 REJ09B0292-0200
Section 2 CPU
There are dedicated load/store instructions for accessing the RS, RE and MOD registers. For example, the RS register is accessed as follows.
LDC LDC.L STC STC.L Rm,RS; @Rm+,RS; RS,Rn; RS,@-Rn; RmRS (Rm)RS,Rm+4Rm RSRn Rn-4Rn,RS(Rn)
The following instructions set addresses in the RS, RE registers for zero overhead repeat control:
LDRS LDRE @(disp,PC); @(disp,PC); dispx2 + PCRS dispx2 + PCRE
The GBR register and VBR register are the same as the previous SuperH microprocessor registers. An RC counter and four control bits (DMX bit, DMY bit, RF1 bit, RF0 bit) have been added to the SR register. The RS, RE and MOD registers are new registers. 2.1.3 System Registers
System registers consist of four 32-bit registers: high and low multiply and accumulate registers (MACH and MACL), the procedure register (PR), and the program counter (PC). The MACH and MACL store the results of multiplication or multiply and accumulate operations*. The PR stores the return address from the subroutine procedure. The PC indicates the address of the program in execution; it controls the flow of the processing. The PC indicates the fourth byte after the instruction currently being executed. These registers are the same as those in the SuperH microprocessor. Note: These are used only when executing an instruction that was supported by SH-1 and SH-2. They are not used for newly added multiplication instructions (PMULS).
31 MACH MACL 0
Multiply and accumulate register high (MACH) Multiply and accumulate register low (MACL)
31 PR
0 Procedure register (PR)
31 PC
0 Program counter (PC)
Figure 2.3 System Register Configuration
Rev. 2.00 Mar 09, 2006 page 36 of 906 REJ09B0292-0200
Section 2 CPU
In addition, among the DSP unit usage registers (DSP registers) described in 2.1.4 DSP Registers, the DSP status register (DSR) and the five registers A0, X0, X1, Y0 and Y1 of the eight data registers are treated as system registers. Among these, the A0 is a 40-bit register, but when data is output from the A0 register, the guard bit section (A0G) is disregarded; when data is input to the A0 register, the MSB of the data is copied into the guard bit section (A0G). 2.1.4 DSP Registers
The DSP unit has eight data registers and one control register as its DSP registers. The DSP data registers are comprised of the two 40-bit registers A0 and A1, and the six 32-bit registers M0, M1, X0, X1, Y0 and Y1. The A0 and A1 registers have the 8-bit guard bits A0G and A1G, respectively. The DSP data registers are used for the transfer and processing of the DSP data of DSP instruction operands. There are three types of instructions that access DSP data registers: those for DSP data processing, and those for X or Y data transfer processing. The control register is the 32-bit DSP status register (DSR) that represents operation results. The DSR register has bits that represent operation results, a signed greater than bit (GT), a zero bit (Z), a negative value bit (N), an overflow bit (V), a DSP status bit (DC: DSP condition), and a status selection bit (CS: condition select) for controlling DC bit setting. The DC bit represents one status flag and is very similar to the SuperH microprocessor CPU core T bit. For conditional DSP type instructions, DSP data processing execution is controlled in accordance with the DC bit. This control is related to execution in the DSP unit only, and only DSP registers are updated. It bears no relation to address calculation or such SuperH microprocessor CPU core execution instructions as load/store instructions. The control bits CS (bits 2 to 0) designate the status for setting the DC bit. DSP type instructions are comprised of unconditional DSP type instructions and conditional DSP type instructions. The status and DC bits are updated in unconditional DSP type data processing, with the exception of the PMULS, MOVX, MOVY and MOVS instructions. Conditional DSP type instructions are executed according to the status of the DC bit, but regardless of whether or not they are executed, the DSR register is not updated. Figure 2.4 shows the DSP registers. The DSR register bit functions are shown in table 2.2. Registers A0, X0, X1, Y0, Y1, and DSR are handled as system registers by CPU core instructions.
Rev. 2.00 Mar 09, 2006 page 37 of 906 REJ09B0292-0200
Section 2 CPU
39 A0G A1G 32 31 A0 A1 M0 M1 X0 X1 Y0 Y1 31 87 6 5 4 321 0 DSP status register (DSR) 0 DSP data registers
GT Z N
V CS[2:0] DC
Figure 2.4 DSP Register Configuration
Rev. 2.00 Mar 09, 2006 page 38 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.2
Bit 31-8 7
DSR Register Bits
Name (Abbreviation) Reserved bits Signed greater than bit (GT) Function 0: Always read out; always use 0 as a write value Indicates that the operation result is positive (excepting 0), or that operand 1 is greater than operand 2 1: Operation result is positive, or operand 1 is greater Indicates that the operation result is zero (0), or that operand 1 is equal to operand 2 1: Operation result is zero (0), or equivalence Indicates that the operation result is negative, or that operand 1 is smaller than operand 2 1: Operation result is negative, or operand 1 is smaller
6
Zero bit (Z)
5
Negative bit (N)
4 3-1
Overflow bit (V)
Indicates that the operation result has overflowed 1: Operation result has overflowed
Status selection bits (CS) Designate the mode for selecting the operation result status set in the DC bit Do not set either 110 or 111 000: Carry/borrow mode 001: Negative value mode 010: Zero mode 011: Overflow mode 100: Signed greater mode 101: Signed above mode
0
DSP status bit (DC)
Sets the status of the operation result in the mode designated by the CS bits 0: Designated mode status not realized (unrealized) 1: Designated mode status realized
Rev. 2.00 Mar 09, 2006 page 39 of 906 REJ09B0292-0200
Section 2 CPU
2.1.5
Notes on Guard Bits and Overflow Treatment
DSP unit data operations are fundamentally performed as 32-bit, but these operations are always executed with a 40-bit length including the 8-bit guard section. When the guard bit section does not match the value of the 32-bit section MSB, the operation result is treated as an overflow. In this case, the N bit indicates the correct status of the operation result regardless of the existence or not of an overflow. This is so even if the destination operand is a 32-bit length register. The 8-bit section guard bits are always presupposed and each status flag is updated. When place overflows occur so that the correct result cannot be displayed even when the guard bits are used, the N flag cannot indicate the correct status. 2.1.6 Initial Values of Registers
Table 2.3 lists the values of the registers after reset. Table 2.3 Initial Values of Registers
Register R0-R14 R15 (SP) Control registers SR RS RE GBR VBR MOD System registers MACH, MACL, PR PC DSP registers Undefined H'00000000 Undefined Undefined Value of the PC in the vector address table Initial Value Undefined Value of the SP in the vector address table Bits I3-I0 are 1111 (H'F), the reserved bits, RC, DMY, and DMX are 0, and other bits are undefined Undefined
Classification General registers
A0, A0G, A1, A1G, M0, Undefined M1, X0, X1, Y0, Y1 DSR H'00000000
Rev. 2.00 Mar 09, 2006 page 40 of 906 REJ09B0292-0200
Section 2 CPU
2.2
2.2.1
Data Formats
Data Format in Registers
Register operand data size is always longword (32 bits). When loading data from memory into a register, if the memory operand is a byte (8 bits) or a word (16 bits), it is sign-extended into a longword, then loaded into the register.
31 Longword 0
Figure 2.5 Register Data Format 2.2.2 Data Formats in Memory
These formats are classified into bytes, words, and longwords. Place byte data in any address, word data from 2n addresses, and longword data from 4n addresses. An address error will occur if accesses are made from any other boundary. In such cases, the access results cannot be guaranteed. In particular, the stack area referred to by the hardware stack pointer (SP, R15) stores the program counter (PC) and status register (SR) as longwords, so establish the hardware stack pointer so that a 4n value will always result. To enable sharing of the processor accessing memory in little-endian mode and memory, the CS2, 4 space (area 2, 4) has a function that allows access in little-endian mode. The order of byte data differs between little-endian mode and normal big-endian mode.
Address m + 1 Address m 31 Byte Address 2n Address 4n Word Longword 23 Byte Address m + 3 Address m + 3 Address m + 1 Address m 7 Byte Word Longword Address 2n Address 4n 0
Address m + 2 15 Byte 7 Byte Word 0 31 Byte
Address m + 2 23 Byte Word 15 Byte
Big endian
Little endian
Figure 2.6 Data Formats in Memory
Rev. 2.00 Mar 09, 2006 page 41 of 906 REJ09B0292-0200
Section 2 CPU
2.2.3
Immediate Data Format
Byte immediate data is placed in an instruction code. With the MOV, ADD, and CMP/EQ instructions, immediate data is sign-extended and operated in registers as longword data. Immediate data accessed by the TST, AND, OR, and XOR instructions is zero-extended and handled as longword data. Consequently, AND instructions with immediate data always clear the upper 24 bits of the destination register. Word or longword immediate data is not located in the instruction code; it should be placed in a memory table. Use an immediate data transfer instruction (MOV) to refer the memory table using the PC relative addressing mode with displacement. 2.2.4 DSP Type Data Formats
This chip has three different types of data format that correspond to various instructions. These are the fixed-point data format, the integer data format, and the logical data format. The DSP type fixed-point data format has a binary point fixed between bits 31 and 30. There are three types: with guard bits, without guard bits, and multiplication input; each with different valid bit lengths and value ranges. The DSP type integer data format has a binary point fixed between bits 16 and 15. There are three types: with guard bits, without guard bits, and shift amount; each with different valid bit lengths and value ranges. The shift amount of the arithmetic shift (PSHA) has a 7 bit range and can express values from -64 to +63, but the actual valid values are from -32 to +32. In the same manner, the shift amount of the logical shift has a 6 bit range, but the actual valid values are from -16 to +16. The DSP type logical data format does not have a decimal point. The data format and valid data length are determined by the instructions and DSP registers. Figure 2.7 shows the three DSP type data formats and binary point positions. The SuperH type data format is also shown for reference.
Rev. 2.00 Mar 09, 2006 page 42 of 906 REJ09B0292-0200
Section 2 CPU
DSP fixed decimal point data With guard bits 39 S 32 31 30 0 -28 to +28 - 2-31 31 30 No guard bits 39 Multiplication input S 31 30 S 16 15 0 -1 to +1 - 2-15 0 -1 to +1 - 2-31
DSP integer data 39 With guard bits S 31 No guard bits S 31 Arithmetic shift (PSHA) 31 Logical shift (PSHL) 22 S 21 16 15 S 0 -16 to +16 16 15 0 -32 to +32 16 15 0 -215 to +215 -1 32 31 16 15 0 -223 to +223 -1
39 DSP logical data
31
16 15
0 (16 bits)
31 SuperH integer (word) (Reference) S
0 -231 to +231 -1
S : Sign bit : Binary decimal point : Unrelated to processing (ignored)
Figure 2.7 DSP Type Data Formats
Rev. 2.00 Mar 09, 2006 page 43 of 906 REJ09B0292-0200
Section 2 CPU
2.2.5
DSP Type Instructions and Data Formats
The DSP data format and valid data length are determined by DSP type instructions and DSP registers. There are three types of instructions that access DSP data registers, DSP data processing, X, Y data transfer processing, and single data transfer processing instructions. DSP Data Processing: The guard bits (bits 39-32) are valid when the A0 and A1 registers are used as source registers in DSP fixed-point data processing. When any registers other than A0, A1 (e.i., M0, M1, X0, X1, Y0, Y1 registers) are used as source registers, the sign-extended part of that register data becomes the bits 39 to 32 data. When the A0 and A1 registers are used as destination registers, the guard bits (bits 39-32) are valid. When any registers other than A0, A1 are used as destination registers, bits 39 to 32 of the result data are disregarded. Processing for DSP integer data is the same as the DSP fixed-point data processing. However, the lower word (the lower 16 bits, bits 15-0) of the source register is disregarded. The lower word of the destination register is cleared to 0. In DSP logical data processing, the upper word (the upper 16 bits, bits 31-16) of the source register is valid. The lower word and the guard bits of the A0, A1 registers are disregarded. The upper word of the destination register is valid. The lower word and the guard bits of the A0, A1 registers are cleared to 0. X, Y Data Transfers: The MOVX.W and MOVY.W instructions access X, Y memory via the 16-bit X, Y data buses. The data loaded into registers and data stored from registers is always the upper word (the upper 16 bits, bits 31-16). When loading, the MOVX.W instruction loads X memory, with the X0 and X1 registers as the destination registers. The MOVY.W instruction loads Y memory, with the Y0 and Y1 registers as the destination registers. Data is stored in the upper word of the register; the lower word is cleared to 0. The upper word data of the A0, A1 registers can be stored in X or Y memory with these data transfer instructions, but storing is not possible from any other registers. The guard bits and the lower word of the A0, A1 registers are disregarded. Single Data Transfers: The MOVS.W and MOVS.L instructions can access any memory via the data bus (CDB). All DSP registers are connected to the CDB bus, and they can become source or destination registers during data transfers. The two data transfer modes are word and longword. In word mode, data is loaded to and stored in the upper word of the DSP register, with the exception of the A0G, A1G registers. In longword mode, data is loaded to and stored in the 32 bits of the DSP register, with the exception of the A0G, A1G registers. The A0G, A1G registers can be
Rev. 2.00 Mar 09, 2006 page 44 of 906 REJ09B0292-0200
Section 2 CPU
treated as independent registers during single data transfers. The load/store data length for the A0G, A1G registers is 8 bits. If DSP registers are used as source registers in word mode, when data is stored from any registers other than A0G, A1G, the data in the upper word of the register is transferred. In the case of the A0, A1 registers, the guard bits are disregarded. When the A0G, A1G registers are the source registers in word mode, only 8 bits of the data are stored from the registers; the upper bits are signextended. If the DSP registers are used as destination registers in word mode, the load is to the upper word of the register, with the exception of A0G, A1G. When data is loaded to any register other than A0G, A1G, the lower word of the register is cleared to 0. In the case of the A0, A1 registers, the data sign is extended and stored in the guard bits; the lower word is cleared to 0. When the A0G, A1G registers are the destination registers in word mode, the least significant 8 bits of the data are loaded into the registers; the A0, A1 registers are not zero cleared but retain their previous values. If the DSP registers are used as source registers in longword mode, when data is stored from any registers other than A0G, A1G, the 32 bits (data) of the register are transferred. When the A0, A1 registers are used as the source registers the guard bits are disregarded. When the A0G, A1G registers are the source registers in longword mode, only 8 bits of the data are stored from the registers; the upper bits are sign-extended. If the DSP registers are used as destination registers in longword mode, the load is to the 32 bits of the register, with the exception of A0G, A1G. In the case of the A0, A1 registers, the data sign is extended and stored in the guard bits. When the A0G, A1G registers are the destination registers in longword mode, the least significant 8 bits of the data are loaded into the registers; the A0, A1 registers are not zero cleared but retain their previous values. Tables 2.4 and 2.5 indicate the register data formats for DSP instructions. Some registers cannot be accessed by certain instructions. For example, the PMULS instruction can designate the A1 register as a source register but cannot designate A0 as such. Refer to the instruction explanations for details. Figure 2.8 shows the relationship between the buses and the DSP registers during transfers.
Rev. 2.00 Mar 09, 2006 page 45 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.4
Source Register Data Formats for DSP Instructions
Guard Bits 39-32 40-bit data Register Bits 31-16 15-0
Register A0, A1 DSP operation
Instruction Fixed decimal, PDMSB, PSHA Integer Logic, PSHL, PMULS Data transfer MOVX.W, MOVY.W, MOVS.W MOVS.L
24-bit data -- 16-bit data
--
32-bit data Data Sign* -- 32-bit data --
A0G, A1G X0, X1, Y0, Y1, M0, M1
Data transfer DSP operation
MOVS.W MOVS.L Fixed decimal, PDMSB, PSHA Integer Logic, PSHL, PMULS
16-bit data --
--
Data transfer
MOVS.W MOVS.L 32-bit data
Note: * The sign is extended and stored in the ALU's guard bits.
Rev. 2.00 Mar 09, 2006 page 46 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.5
Destination Register Data Formats for DSP Instructions
Guard Bits 39-32 (Sign extend) Register Bits 31-16 40-bit result 15-0
Register A0, A1 DSP operation
Instruction Fixed decimal, PSHA, PMULS Integer, PDMSB Logic, PSHL Data transfer MOVS.W MOVS.L MOVS.W MOVS.L Fixed decimal, PSHA, PMULS Integer, logic, PDMSB, PSHL Data transfer MOVX.W, MOVY.W, MOVS.W MOVS.L
24-bit result Clear to 0 Sign extend 32-bit data Data -- Not updated 32-bit result 16-bit result
Clear to 0
A0G, A1G X0, X1, Y0, Y1, M0, M1
Data transfer DSP operation
Not updated
16-bit result
Clear to 0
32-bit data
Rev. 2.00 Mar 09, 2006 page 47 of 906 REJ09B0292-0200
Section 2 CPU
32 bits 16 bits 16 bits [7:0] 8 bits 16 bits MOVX.W, MOVY.W 31 16 A0 32 A0G A1G DSR 7 0 A1 M0 M1 X0 X1 Y0 Y1
CDB XDB YDB 32 bits MOVS.W, MOVS.L 0
MOVS.W, MOVS.L 39
Figure 2.8 DSP Register-Bus Relationship during Data Transfers
2.3
CPU Core Instruction Features
The CPU core instructions are RISC type. The characteristics are as follows. 16-Bit Fixed Length: All instructions are 16 bits long, increasing program code efficiency. One Instruction per Cycle: The microprocessor can execute basic instructions in one cycle using the pipeline system. One state equals 16.0 ns when operating at 62.5 MHz. Data Length: Longword is the basic data length for all operations. Memory can be accessed in bytes, words, or longwords. Byte or word data accessed from memory is sign-extended and handled as longword data. Immediate data is sign-extended for arithmetic operations or zeroextended for logic operations. It also is handled as longword data.
Rev. 2.00 Mar 09, 2006 page 48 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.6
Sign Extension of Word Data
Description Example of Conventional CPU #H'1234,R0
SH7616 CPU MOV.W ADD ........ .DATA.W H'1234 @(disp,PC),R1 R1,R0
Data is sign-extended to 32 ADD.W bits, and R1 becomes H'00001234. It is next operated upon by an ADD instruction
Note: @(disp, PC) accesses the immediate data.
Load-Store Architecture: Basic operations are executed between registers. For operations that involve memory access, data is loaded to the registers and executed (load-store architecture). However, Instructions such as AND manipulating bits, are executed directly in memory. Delayed Branches: Such instructions as unconditional branches are delayed branch instructions. In the case of delayed branch instructions, the branch occurs after execution of the instruction immediately following the delayed branch instruction (slot instruction). This reduces pipeline disruption during branching. The branching operation of the delayed branch occurs after execution of the slot instruction. However, with the exception of such branch operations as register updating, execution of instructions is performed with the order of delayed branch instruction, then delayed slot instruction. For example, even if the contents of a register storing a branch destination address are modified by a delayed slot, the branch destination address will still be the contents of the register before the modification. Table 2.7 Delayed Branch Instructions
Description Executes an ADD before branching to TRGET Example of Conventional CPU ADD.W BRA R1,R0 TRGET
SH7616 CPU BRA ADD TRGET R1,R0
Multiplication/Multiply-Accumulate Operation: 16 x 16 32 multiplications execute in one to three cycles, and 16 x 16 + 64 64 multiply-accumulate operations execute in two to three cycles. 32 x 32 64 multiplications and 32 x 32 + 64 64 multiply-accumulate operations execute in two to four cycles.
Rev. 2.00 Mar 09, 2006 page 49 of 906 REJ09B0292-0200
Section 2 CPU
T Bit: The T bit in the status register (SR) changes according to the result of a comparison, and conditional branches occur in accordance with its true or false status. The number of instructions modifying the T bit is kept to a minimum to improve the processing speed. Table 2.8 T Bit
Description T bit is set when R0 R1. Example of Conventional CPU CMP.W R1,R0 TRGET0 TRGET1
SH7616 CPU CMP/GE BT BF ADD CMP/EQ BT R1,R0 TRGET0 TRGET1 #-1,R0 #0,R0 TRGET
The program branches to TRGET0 BGE when R0 R1. The program branches to TRGET1 BLT when R0 < R1 T bit is not changed by ADD. T bit is set when R0 = 0. The program branches when R0 = 0 BEQ
SUB.W #1,R0 TRGET
Immediate Data: Byte immediate data resides in instruction code. Word or longword immediate data is not input in instruction codes but is stored in a memory table. An immediate data transfer instruction (MOV) accesses the memory table using the PC relative addressing mode with displacement. Table 2.9 Immediate Data Accessing
SH7616 CPU MOV MOV.W ........ .DATA.W H'1234 32-bit immediate MOV.L ........ .DATA.L H'12345678 Note: @(disp, PC) accesses the immediate data. @(disp,PC),R0 MOV.L #H'12345678,R0 #H'12,R0 @(disp,PC),R0 Example of Conventional CPU MOV.B MOV.W #H'12,R0 #H'1234,R0
Classification 8-bit immediate 16-bit immediate
Rev. 2.00 Mar 09, 2006 page 50 of 906 REJ09B0292-0200
Section 2 CPU
Absolute Address: When data is accessed by absolute address, the value already in the absolute address is placed in the memory table. Loading the immediate data when the instruction is executed transfers that value to the register and the data is accessed in the indirect register addressing mode. Table 2.10 Absolute Address Accessing
Classification Absolute address SH7616 CPU MOV.L MOV.B ........ .DATA.L H'12345678 @(disp,PC),R1 @R1,R0 Example of Conventional CPU MOV.B @H'12345678,R0
16-Bit/32-Bit Displacement: When data is accessed by 16-bit or 32-bit displacement, the preexisting displacement value is placed in the memory table. Loading the immediate data when the instruction is executed transfers that value to the register and the data is accessed in the indirect indexed register addressing mode. Table 2.11 Displacement Accessing
Classification 16-bit displacement SH7616 CPU MOV.W MOV.W ........ .DATA.W H'1234 @(disp,PC),R0 @(R0,R1),R2 Example of Conventional CPU MOV.W @(H'1234,R1),R2
Rev. 2.00 Mar 09, 2006 page 51 of 906 REJ09B0292-0200
Section 2 CPU
2.4
2.4.1
Instruction Formats
CPU Instruction Addressing Modes
The addressing modes and effective address calculation for instructions executed by the CPU core are listed in table 2.12. Table 2.12 CPU Instruction Addressing Modes and Effective Addresses
Addressing Mode Direct register addressing Instruction Format Effective Addresses Calculation Rn The effective address is register Rn (The operand is the contents of register Rn) The effective address is the content of register Rn
Rn Rn
Equation -- Rn
Indirect register @Rn addressing
Post-increment @Rn+ indirect register addressing
The effective address is the content of register Rn Rn. A constant is added to the content of Rn after (After the the instruction is executed. 1 is added for a byte instruction operation, 2 for a word operation, and 4 for a executes) longword operation Byte: Rn + 1 Rn Rn Rn Word: Rn + 2 Rn
Rn + 1/2/4 1/2/4 +
Longword: Rn + 4 Rn Byte: Rn - 1 Rn Word: Rn - 2 Rn Longword: Rn - 4 Rn (Instruction executed with Rn after calculation)
Pre-decrement @-Rn indirect register addressing
The effective address is the value obtained by subtracting a constant from Rn. 1 is subtracted for a byte operation, 2 for a word operation, and 4 for a longword operation
Rn Rn - 1/2/4 1/2/4 - Rn - 1/2/4
Rev. 2.00 Mar 09, 2006 page 52 of 906 REJ09B0292-0200
Section 2 CPU Addressing Mode Instruction Format Effective Addresses Calculation The effective address is Rn plus a 4-bit displacement (disp). The value of disp is zeroextended, and remains the same for a byte operation, is doubled for a word operation, and is quadrupled for a longword operation
Rn disp (zero-extended) x 1/2/4 + Rn + disp x 1/2/4
Equation Byte: Rn + disp Word: Rn + disp x 2 Longword: Rn + disp x 4
Indirect register @(disp:4, addressing Rn) with displacement
Indirect indexed @(R0, Rn) The effective address is the Rn value plus R0 register Rn addressing
+ R0 Rn + R0
Rn + R0
Indirect GBR @(disp:8, addressing with GBR) displacement
The effective address is the GBR value plus an 8-bit displacement (disp). The value of disp is zero-extended, and remains the same for a byte operation, is doubled for a word operation, and is quadrupled for a longword operation
GBR disp (zero-extended) x 1/2/4 + GBR + disp x 1/2/4
Byte: GBR + disp Word: GBR + disp x2 Longword: GBR + disp x 4
Rev. 2.00 Mar 09, 2006 page 53 of 906 REJ09B0292-0200
Section 2 CPU Addressing Mode Indirect indexed GBR addressing Instruction Format Effective Addresses Calculation @(R0, GBR) The effective address is the GBR value plus the R0
GBR + R0 GBR + R0
Equation GBR + R0
PC relative addressing with displacement
@(disp:8, PC)
The effective address is the PC value plus an 8-bit displacement (disp). The value of disp is zeroextended, is doubled for a word operation, and is quadrupled for a longword operation. For a longword operation, the lowest two bits of the PC value are masked
PC (for longword) & H'FFFFFFFC + disp (zero-extended) x 2/4 PC + disp x 2 or PC&H'FFFFFFFC + disp x 4
Word: PC + disp x2 Longword: PC & H'FFFFFFFC + disp x 4
Rev. 2.00 Mar 09, 2006 page 54 of 906 REJ09B0292-0200
Section 2 CPU PC relative addressing disp:8 The effective address is the PC value sign-extended PC + disp x 2 with an 8-bit displacement (disp), doubled, and added to the PC value
PC disp (sign-extended) x 2 + PC + disp x 2
disp:12
The effective address is the PC value sign-extended PC + disp x 2 with a 12-bit displacement (disp), doubled, and added to the PC value
PC disp (sign-extended) x 2 + PC + disp x 2
Rn
The effective address is the register PC value plus Rn
PC + Rn PC + Rn
PC + Rn
Immediate addressing
#imm:8 #imm:8 #imm:8
The 8-bit immediate data (imm) for the TST, AND, OR, and XOR instructions are zero-extended The 8-bit immediate data (imm) for the MOV, ADD, and CMP/EQ instructions are sign-extended The 8-bit immediate data (imm) for the TRAPA instruction is zero-extended and is quadrupled
-- -- --
Rev. 2.00 Mar 09, 2006 page 55 of 906 REJ09B0292-0200
Section 2 CPU
2.4.2
DSP Data Addressing
There are two different kinds of memory accesses with DSP instructions. One type is with the X, Y data transfer instructions (MOVX.W, MOVY.W), and the other is with the single data transfer instructions (MOVS.W, MOVS.L). The data addressing differs between these two types of instructions. Table 2.13 shows a summary of the data transfer instructions. Table 2.13 Overview of Data Transfer Instructions
Classification Address registers Index registers Addressing X, Y Data Transfer Processing (MOVX.W, MOVY.W) Ax: R4, R5; Ay: R6, R7 Ix: R8, Iy: R9 Nop/Inc(+2)/index addition: postupdate -- Modulo addressing Data bus Data length Bus contention Memory Source registers Destination registers Possible XDB, YDB 16 bit (word) None X, Y data memory Dx, Dy: A0, A1 Dx: X0/X1; Dy: Y0/Y1 Single Data Transfer Processing (MOVS.W, MOVS.L) As: R2, R3, R4, R5 Is: R8 Nop/Inc(+2,+4)/index addition: postupdate Dec(-2,-4): pre-update Not possible CDB 16 bit/32 bit (word/longword) Yes All memory spaces Ds: A0/A1, M0/M1, X0/X1, Y0/Y1, A0G, A1G Ds: A0/A1, M0/M1, X0/X1, Y0/Y1, A0G, A1G
X, Y Data Addressing: Among the DSP instructions, the MOVX.W and MOVY.W instructions can be used to simultaneously access X, Y data memory. The DSP instructions have two address pointers for simultaneous accessing of X, Y data memory. Only pointer addressing is possible with DSP instructions; there is no immediate addressing. The address registers are divided into two; the R4, R5 registers become the X memory address register (Ax), and the R6, R7 registers become the Y memory address register (Ay). The following three types of addressing exist with X, Y data transfer instructions. 1. Non-updated address registers: The Ax, Ay registers are address pointers. They are not updated. 2. Add index registers: The Ax, Ay registers are address pointers. The Ix, Iy register values are added to them, respectively, after the data transfer (post-update).
Rev. 2.00 Mar 09, 2006 page 56 of 906 REJ09B0292-0200
Section 2 CPU
3. Increment address registers: The Ax, Ay registers are address pointers. The value +2 is added to each of them after the data transfer (post-update). Each of the address pointers has an index register. The R8 register becomes the index register (Ix) of the X memory address register (Ax), and the R9 register becomes the index register (Iy) of the Y memory address register (Ay). The X, Y data transfer instructions are processed in word lengths. X, Y data memory is accessed in 16 bit lengths. This is why the increment processing adds 2 to the address registers. In order to decrement, set -2 in the index register and designate add index register addressing. During X, Y data addressing, only bits 1 to 15 of the address pointer are valid. Always write a 0 to bit 0 of the address pointer and the index register during X, Y data addressing. Figure 2.9 shows the X, Y data transfer addressing. When X memory and Y memory are accessed using the X, Y bus, the upper word of Ax (R4 or R5) and Ay (R6 or R7) is ignored. The result of @Ay+ and @Ay+Iy is stored in the lower word of Ay, and the upper word retains its original value.
R8[Ix] +2 (INC) +0 (No update)
R4[Ax] R5[Ax]
R9[Iy] +2 (INC) +0 (No update)
R6[Ay] R7[Ay]
ALU
AU*
Notes:
All three addressing methods (increment, index register addition (Ix, Iy), and no update) are post-updating methods. To decrement the address pointer, set the index register to -2 or -4. * Adder added for DSP addressing.
Figure 2.9 X, Y Data Transfer Addressing
Rev. 2.00 Mar 09, 2006 page 57 of 906 REJ09B0292-0200
Section 2 CPU
Single Data Addressing: Among the DSP instructions, the single data transfer instructions (MOVS.W and MOVS.L) are used to either load data into DSP registers or to store it from them. With these instructions, the registers R2 to R5 are used as address registers (As) for the single data transfers. The four following data addressing instructions exist for single data transfer instructions. 1. Non-updated address registers: The As registers are address pointers. They are not updated. 2. Add index registers: The As registers are address pointers. The Is register values are added to them after the data transfer (post-update). 3. Increment address registers: The As registers are address pointers. The value +2 or +4 is added after the data transfer (post-update). 4. Decrement address registers: The As registers are address pointers. The value -2 or -4 is added (+2 or +4 is subtracted) before the data transfer (pre-update). The address pointer (As) uses the R8 register as an index register (Is). Figure 2.10 shows the single data transfer addressing.
31 R2[As] 31 R8[Is] -2/-4 (DEC) +2/+4 (INC) +0 (No update) 0 R3[As] R4[As] R5[As] 0
ALU 31 MAB CAB 0 Note: There are four addressing methods (no update, index register addition (Is), increment, and decrement). Index register addition and increment are post-updating methods. Decrement is a pre-updating method.
Figure 2.10 Single Data Transfer Addressing
Rev. 2.00 Mar 09, 2006 page 58 of 906 REJ09B0292-0200
Section 2 CPU
Modulo Addressing: The chip has a modulo addressing mode, just as other DSPs do. Address registers are updated in the same manner as with other modes. When the address pointer value becomes the same as a previously established modulo end address, the address pointer becomes the modulo start address. Modulo addressing is valid only with X, Y data transfer instructions (MOVX.W, MOVY.W). When the DMX bit of the SR register is set, the X address register enters modulo addressing mode; when the DMY bit of the SR register is set, the Y address register does so. Modulo addressing is valid only for either the X or the Y address register; it is not possible to make them both modulo addressing mode at the same time. Therefore, do not simultaneously set the DMX and DMY. If they happen to be set at the same time, only the DMY side is valid. The MOD register is used to designate the start and end addresses of the modulo address area; it stores the MS (modulo start) and ME (modulo end). An example of MOD register (MS, ME) usage is indicated below.
MOV.L ModAddr,Rn; LDC Rn,MOD; ModAddr: .DATA.W .DATA.W mEnd; mStart; Rn=ModEnd, ModStart ME=ModEnd, MS=ModStart ModEnd ModStart
ModStart: .DATA : ModEnd: .DATA
Designate the start and end addresses in MS and ME, and then set the DMX or DMY bit to 1. The contents of the address register are compared with ME. If they match ME, the start address MS is stored in the address register. The lower 16 bits of the address register are compared with ME. The maximum modulo size is 64 kbytes. This is sufficient for X, Y data memory accesses. Figure 2.11 shows a block diagram of modulo addressing.
Rev. 2.00 Mar 09, 2006 page 59 of 906 REJ09B0292-0200
Section 2 CPU
Instruction (MOVX/MOVY) 31 31 R8[Ix] +2 +0 0 16 15 R4[Ax] R5[Ax] 0 DMX DMY 31 16 15 R6[Ay] CONT 15 MS ALU CMP ABx 15 XAB 1 15 ME 1 15 YAB ABy 1 AU 1 R7[Ay] 0 31 R9[Iy] +2 +0 0
Figure 2.11 Modulo Addressing An example of modulo addressing is indicated below:
MS=H'E008; ME=H'E00C; R4=H'1000E008; DMX=1; DMY=0; (sets modulo addressing for address register Ax (R4, R5))
The R4 register changes as follows due to the above settings.
R4: H'1000E008 Inc. Inc. Inc. R4: H'1000E00A R4: H'1000E00C R4: H'1000E008
(becomes the modulo start address because the modulo end address occurred)
Data is placed so that the upper 16 bits of the modulo start and end addresses become identical. This is so because the modulo start address replaces only the lower 15 bits of the address register, excepting bit 0. Note: When using add index with DSP data addressing, there are cases where the value is exceeded without the address pointer matching the ME. In such cases, the address pointer does not return to the modulo start address. Bit 0 is disregarded not only for modulo addressing, but also during X, Y data addressing, so always write 0 to the 0 bits of the address pointer, index register, MS, and ME.
Rev. 2.00 Mar 09, 2006 page 60 of 906 REJ09B0292-0200
Section 2 CPU
DSP Addressing Operation: The DSP addressing operation in the item stage (EX) of the pipeline, including modulo addressing, is indicated below.
if ( Operation is MOVX.W MOVY.W ) { ABx=Ax; ABy=Ay; /* memory access cycle uses ABx and ABy. The addresses to be used have not been updated */
/* Ax is one of R4,5 */ if ( DMX==0 || DMX==1 && DMY==1 )} Ax=Ax+(+2 or R8[Ix} or +0); /* Inc,Index,Not-Update */ else if (!not-update) Ax=modulo( Ax, (+2 or R8[Ix]) );
/* Ay is one of R6,7 */ if ( DMY==0 ) Ay=Ay+(+2 or R9[Iy] or +0; /* Inc,Index,Not-Update */ else if (! not-update) Ay=modulo( Ay, (+2 or R9[Iy]) ); } else if ( Operation is MOVS.W or MOVS.L ) { if ( Addressing is Nop, Inc, Add-index-reg ) { MAB=As; /* memory access cycle uses MAB. The address to be used has not been updated */ /* As is one of R2-5 */ As=As+(+2 or +4 or R8[Is] or +0); /* Inc.Index,Not-Update */ else { /* Decrement, Pre-update */ /* As is one of R2-5 */ As=As+(-2 or -4); MAB=As; /* memory access cycle uses MAB. The address to be used has been updated */ }
/* The value to be added to the address register depends on addressing operations. For example, (+2 or R8[Ix] or +0) means that +2: R8[Ix}: if operation is increment if operation is add-index-reg Rev. 2.00 Mar 09, 2006 page 61 of 906 REJ09B0292-0200
Section 2 CPU +0: */ if operation is not-update
function modulo ( AddrReg, Index ) { if ( AdrReg[15:0]==ME ) AdrReg[15:0]=MS; else AdrReg=AdrReg+Index; return AddrReg; }
2.4.3
Instruction Formats for CPU Instructions
The instruction format of instructions executed by the CPU core and the meanings of the source and destination operands are indicated below. The meaning of the operand depends on the instruction code. The symbols are used as follows: * xxxx: Instruction code * mmmm: Source register * nnnn: Destination register * iiii: Immediate data * dddd: Displacement
Rev. 2.00 Mar 09, 2006 page 62 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.14 Instruction Formats for CPU Instructions
Instruction Formats 0 format
15 xxxx xxxx xxxx xxxx 0
Source Operand --
Destination Operand --
Example NOP
n format
15 xxxx nnnn xxxx xxxx 0
--
nnnn: Direct register
MOVT Rn
Control register or nnnn: Direct system register register
STS MACH,Rn
Control register or nnnn: Indirect pre- STC.L SR,@-Rn system register decrement register m format
15 xxxx mmmm xxxx xxxx 0
mmmm: Direct register
Control register or LDC system register
Rm,SR
mmmm: Indirect post- Control register or LDC.L @Rm+,SR increment register system register mmmm: Indirect register mmmm: PC relative using Rm -- -- JMP @Rm BRAF Rm
Rev. 2.00 Mar 09, 2006 page 63 of 906 REJ09B0292-0200
Section 2 CPU Destination Operand nnnn: Direct register nnnn: Indirect register
Instruction Formats nm format
15 xxxx nnnn mmmm xxxx 0
Source Operand mmmm: Direct register mmmm: Direct register
Example ADD Rm,Rn
MOV.L Rm,@Rn MAC.W @Rm+,@Rn+
mmmm: Indirect post- MACH, MACL increment register (multiply/ accumulate) nnnn: Indirect postincrement register (multiply/ accumulate)* mmmm: Indirect post- nnnn: Direct increment register register mmmm: Direct register mmmm: Direct register md format
15 xxxx xxxx mmmm dddd 0
MOV.L @Rm+,Rn
nnnn: Indirect pre- MOV.L Rm,@-Rn decrement register nnnn: Indirect indexed register MOV.L Rm,@(R0,Rn)
mmmmdddd: indirect R0 (Direct register) MOV.B register with @(disp,Rm),R0 displacement R0 (Direct register) nnnndddd: Indirect MOV.B register with R0,@(disp,Rn) displacement mmmm: Direct register nnnndddd: Indirect MOV.L register with Rm,@(disp,Rn) displacement MOV.L @(disp,Rm),Rn
nd4 format
15 xxxx xxxx nnnn dddd 0
nmd format
15 xxxx nnnn mmmm dddd 0
mmmmdddd: Indirect nnnn: Direct register register with displacement
Rev. 2.00 Mar 09, 2006 page 64 of 906 REJ09B0292-0200
Section 2 CPU Destination Operand
Instruction Formats d format
15 xxxx xxxx dddd dddd 0
Source Operand
Example
dddddddd: Indirect R0 (Direct register) MOV.L GBR with @(disp,GBR),R0 displacement R0(Direct register) dddddddd: Indirect MOV.L GBR with R0,@(disp,GBR) displacement dddddddd: PC relative with displacement dddddddd: PC relative R0 (Direct register) MOVA @(disp,PC),R0 -- -- BF BRA label label
d12 format
15 xxxx dddd dddd dddd 0
dddddddddddd: PC relative
(label=disp+PC) nnnn: Direct register MOV.L @(disp,PC),Rn
nd8 format
15 xxxx nnnn dddd dddd 0
dddddddd: PC relative with displacement iiiiiiii: Immediate
i format
15 xxxx xxxx iiii iiii 0
Indirect indexed GBR
AND.B #imm,@(R0,GBR) #imm,R0
iiiiiiii: Immediate iiiiiiii: Immediate
R0 (Direct register) AND -- nnnn: Direct register
TRAPA #imm ADD #imm,Rn
ni format
15 xxxx nnnn iiii iiii 0
iiiiiiii: Immediate
Note: * In multiply/accumulate instructions, nnnn is the source register.
Rev. 2.00 Mar 09, 2006 page 65 of 906 REJ09B0292-0200
Section 2 CPU
2.4.4
Instruction Formats for DSP Instructions
New instructions have been added for digital signal processing. The new instructions are divided into the two following types. 1. Memory and DSP register double, single data transfer instructions (16 bit length) 2. Parallel processing instructions processed by the DSP unit (32 bit length) Figure 2.12 shows each of the instruction formats.
15 CPU core instructions 0000 to 1110 15 10 9 A field 0 A field 16 15 A field B field 0 0 0
Double data transfer instructions Single data transfer instructions Parallel processing instructions
111100 15 10 9
111101 31 26 25
111110
Figure 2.12 Instruction Formats for DSP Instructions Double, Single Data Transfer Instructions: Table 2.15 indicates the data formats for double data transfer instructions, and table 2.16 indicates the data formats for single data transfer instructions.
Rev. 2.00 Mar 09, 2006 page 66 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.15 Instruction Formats for Double Data Transfers
Category X memory data transfers Mnemonic NOPX MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W Y memory data transfers NOPY MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W Category X memory data transfers Mnemonic NOPX MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W Y memory data transfers NOPY MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W @Ay,Dy @Ay+,Dy @Ay+Iy,Dy Da,@Ay Da,@Ay+ Da,@Ay+Iy @Ax,Dx @Ax+,Dx @Ax+Ix,Dx Da,@Ax Da,@Ax+ Da,@Ax+Ix @Ay,Dy @Ay+,Dy @Ay+Iy,Dy Da,@Ay Da,@Ay+ Da,@Ay+Iy 7 0 Dx 6 5 0 0 4 3 0 0 1 1 0 1 1 0 0 2 0 1 0 1 1 0 1 0 0 1 1 0 1 1 0 1 0 1 1 0 1 1 0 @Ax,Dx @Ax+,Dx @Ax+Ix,Dx Da,@Ax Da,@Ax+ Da,@Ax+Ix 1 1 1 1 0 0 0 Ay 15 1 14 1 13 1 12 1 11 0 10 0 9 0 Ax 8
Da
1
0 Dy
Da
1
Ax: 0=R4, 1=R5 Ay: 0=R6, 1=R7 Dx: 0=X0, 1=X1 Dy: 0=Y0, 1=Y1 Da: 0=A0, 1=A1
Rev. 2.00 Mar 09, 2006 page 67 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.16 Instruction Formats for Single Data Transfers
Category Single data transfer Mnemonic MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L Category Single data transfer @-As,Ds @As,Ds @As+,Ds @As+Is,Ds Ds,@-As Ds,@As Ds,@As+ Ds,@As+Is @-As,Ds @As,Ds @As+,Ds @As+Is,Ds Ds,@-As Ds,@As Ds,@As+ Ds,@As+Is 7 @-As,Ds @As,Ds @As+,Ds @As+Is,Ds Ds,@-As Ds,@As Ds,@As+ Ds,@As+Is @-As,Ds @As,Ds @As+,Ds @As+Is,Ds Ds,@-As Ds,@As Ds,@As+ Ds,@As+Is 6 Ds 5 4 0: (*) 1: (*) 2: (*) 3: (*) 4: (*) 5: A1 6: (*) 7: A0 8: X0 9: X1 A: Y0 B: Y1 C: M0 D: A1G E: M1 F: A0G 3 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 2 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 1 0 0 0 15 1 14 1 13 1 12 1 11 0 10 1 9 8 As 0: R4 1: R5 2: R2 3: R3
Mnemonic MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.W MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L MOVS.L
1
0
1
Note: * System reserved code
Rev. 2.00 Mar 09, 2006 page 68 of 906 REJ09B0292-0200
Section 2 CPU
Parallel Processing Instructions: The parallel processing instructions allow for more efficient execution of digital signal processing using the DSP unit. They are 32 bit length, allowing simultaneously in parallel four processes, ALU operations, multiplications or 2 data transfers. The parallel processing instructions are divided into A fields and B fields. The A field defines data transfer instructions; the B field defines ALU operation instructions and multiplication instructions. These instructions can be defined independently, the processes can be independent, and furthermore, they can be executed simultaneously in parallel. Table 2.17 indicates the A field parallel data transfer instructions, and table 2.18 indicates the B field ALU operation instructions and multiplication instructions. A fields instruction is the same as double data transfers in table 2.15. Table 2.17 A Field Parallel Data Transfer Instructions
Category X memory data transfers Mnemonic NOPX MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W Y memory data transfers NOPY MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W @Ay,Dy @Ay+,Dy @Ay+Iy,Dy Da,@Ay Da,@Ay+ Da,@Ay+Iy @Ax,Dx @Ax+,Dx @Ax+Ix,Dx Da,@Ax Da,@Ax+ Da,@Ax+Ix 0 Ay 31 1 30 1 29 1 28 1 27 1 26 0 25 0 Ax 24 23 0 Dx
Da
Rev. 2.00 Mar 09, 2006 page 69 of 906 REJ09B0292-0200
Section 2 CPU Category X memory data transfers Mnemonic NOPX MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W MOVX.W Y memory data transfers NOPY MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W MOVY.W @Ay,Dy @Ay+,Dy @Ay+Iy,Dy Da,@Ay Da,@Ay+ Da,@Ay+Iy @Ax,Dx @Ax+,Dx @Ax+Ix,Dx Da,@Ax Da,@Ax+ Da,@Ax+Ix 0 Dy 22 21 0 0 20 19 0 0 1 1 0 1 1 0 0 18 0 1 0 1 1 0 1 0 0 1 1 0 1 1 0 1 0 1 1 0 1 17 16 15-0 B field
1
Da
1
Ax: 0 = R4, 1 = R5 Ay: 0 = R6, 1 = R7 Dx: 0 = X0, 1 = X1 Dy: 0 = Y0, 1 = Y1 Da: 0 = A0, 1 = A1
Rev. 2.00 Mar 09, 2006 page 70 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.18 B Field ALU Operation Instructions, Multiplication Instructions
Category Imm. shift Mnemonic PSHL #lmm, Dz PSHA #lmm, Dz Reserved PMULS Se, Sf, Dg Reserved PSUB Sx, Sy, Du PMULS Se, Sf, Dg PADD Sx, Sy, Du PMULS Se, Sf, Dg Three operand instructions Reserved PSUBC Sx, Sy, Dz PADDC Sx, Sy, Dz PCMP Sx, Sy Reserved Reserved Reserved PABS Sx, Dz PRND Sx, Dz PABS Sy, Dz PRND Sy, Dz 31-27 1 26 0 25-16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 A field 0 0 0 0 0 -16 lmm +16 Dz 00010 000 1 001 0100 Se Sf 0:Y0 1:Y1 2:X0 3:A1 Sx 0:X0 1:X1 2:A0 3:A1 Sy 0:Y0 1:Y1 2:M0 3:M1 Dg 0:M0 1:M1 2:A0 3:A1 Du 0:X0 1:Y0 2:A0 3:A1 - 32 lmm +32
Six operand parallel instruction
0 1 0 1 0:X0 1:X1 0 1 1 0 2:Y0 3:A1 0111 10 0000 01 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 1 001 1 0 1 010 1 0 1 011 1 0 1
0
0
Dz 0: (*1) 1: (*1) 2: (*1) 3: (*1) 4: (*1) 5: A1 6: (*1) 7: A0 8: X0 9: X1 A: Y0 B: Y1 C: M0 D: (*1) E: M1 F: (*1)
Reserved
Rev. 2.00 Mar 09, 2006 page 71 of 906 REJ09B0292-0200
Section 2 CPU
Mnemonic 31-27 26 (if cc) PSHL Sx, Sy, Dz 1 0 Conditional (if cc) PSHA Sx, Sy, Dz three operand (if cc) PSUB Sx, Sy, Dz instructions (if cc) PADD Sx, Sy, Dz Reserved (if cc) PAND Sx, Sy, Dz (if cc) PXOR Sx, Sy, Dz (if cc) POR Sx, Sy, Dz (if cc) PDEC Sx, Dz (if cc) PINC Sx, Dz (if cc) PDEC Sy, Dz (if cc) PINC Sy, Dz (if cc) PCLR Dz (if cc) PDMSB Sx, Dz Reserved (if cc) PDMSB Sy, Dz (if cc) PNEG Sx, Dz (if cc) PCOPY Sx, Dz (if cc) PNEG Sy, Dz (if cc) PCOPY Sy, Dz Reserved (if cc) PSTS MACH, Dz (if cc) PSTS MACL, Dz (if cc) PLDS Dz, MACH (if cc) PLDS Dz, MACL Reserved*2 Reserved 1 Category 25-16 15 14 13 12 11 10 0000 A field 01 10 11 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 001 1 0 1 010 1 0 1 011 1 0 1 010 1 0 1 98 if cc 7 6 54 3210
01: Uncondition
10:DCT
11:DCF
11
0 0011 01 10 11 0 0*
0 if cc
0
* : Don't care Notes: 1. System reserved code 2. (if cc): DCT (DC bit true), DCF (DC bit false), or none (unconditional instruction)
2.5
Instruction Set
The instructions are divided into three groups: CPU instructions executed by the CPU core, DSP data transfer instructions executed by the DSP unit, and DSP operation instructions. There are a number of CPU instructions for supporting the DSP functions. The instruction set is explained below in terms of each of the three groups.
Rev. 2.00 Mar 09, 2006 page 72 of 906 REJ09B0292-0200
Section 2 CPU
2.5.1
CPU Instruction Set
Table 2.19 lists the CPU instructions by classification. Table 2.19 Classification of CPU Instructions
Operation Classification Types Code Function Data transfer 5 MOV MOVA MOVT SWAP XTRCT Arithmetic operations 21 ADD ADDC ADDV DIV1 DIV0S DIV0U DMULS DMULU DT EXTS EXTU MAC MUL MULS MULU NEG NEGC SUB SUBC SUBV No. of Instructions
Data transfer, immediate data transfer, peripheral 39 module data transfer, structure data transfer Effective address transfer T bit transfer Swap of upper and lower bytes Extraction of the middle of registers connected Binary addition Binary addition with carry Binary addition with overflow Division Initialization of signed division Initialization of unsigned division Signed double-length multiplication Unsigned double-length multiplication Decrement and test Sign extension Zero extension Multiply/accumulate, double-length multiply/accumulate operation Double-length multiply operation Signed multiplication Unsigned multiplication Negation Negation with borrow Binary subtraction Binary subtraction with borrow Binary subtraction with underflow 33
CMP/cond Comparison
Rev. 2.00 Mar 09, 2006 page 73 of 906 REJ09B0292-0200
Section 2 CPU Operation Classification Types Code Function Logic operations 6 AND NOT OR TAS TST XOR Shift 10 ROTCL ROTCR ROTL ROTR SHAL SHAR SHLL SHLLn SHLR SHLRn Branch 9 BF BT BRA BRAF BSR BSRF JMP JSR RTS Logical AND Bit inversion Logical OR Memory test and bit set Logical AND and T bit set Exclusive OR One-bit left rotation with T bit One-bit right rotation with T bit One-bit left rotation One-bit right rotation One-bit arithmetic left shift One-bit arithmetic right shift One-bit logical left shift n-bit logical left shift One-bit logical right shift n-bit logical right shift Conditional branch, conditional branch with delay 11 (Branch when T = 0) Conditional branch, conditional branch with delay (Branch when T = 1) Unconditional branch Unconditional branch Branch to subroutine procedure Branch to subroutine procedure Unconditional branch Branch to subroutine procedure Return from subroutine procedure 14 No. of Instructions 14
Rev. 2.00 Mar 09, 2006 page 74 of 906 REJ09B0292-0200
Section 2 CPU Operation Classification Types Code Function System control 14 CLRMAC MAC register clear CLRT LDC LDRE LDRS LDS NOP RTE SETRC SETT SLEEP STC STS TRAPA Total:65 T bit clear Load to control register Load to repeat end register Load to repeat start register Load to system register No operation Return from exception processing Repeat count setting T bit set Shift into power-down mode Storing control register data Storing system register data Trap exception handling 182 No. of Instructions 71
Rev. 2.00 Mar 09, 2006 page 75 of 906 REJ09B0292-0200
Section 2 CPU
The instruction codes, operation, and execution states of the CPU instructions are listed by classification with the formats listed in below.
Instruction Indicated by mnemonic Instruction Code Indicated in MSB LSB order Explanation of Symbols mmmm: Source register Operation Indicates summary of operation Explanation of Symbols , : Transfer direction Execution Cycles Value when no wait states are inserted*1 T Bit Value of T bit after instruction is executed
Explanation of Symbols OP.Sz SRC, DEST OP: Operation code Sz: Size SRC: Source DEST: Destination Rm: Source register Rn: Destination register imm: Immediate data disp: Displacement*2
nnnn: Destination register (xx): Memory operand 0000: R0 M/Q/T: Flag bits in the SR 0001: R1 &: Logical AND of each bit ......... |: Logical OR of each bit 1111: R15 iiii: Immediate data dddd: Displacement ^: Exclusive OR of each bit ~: Logical NOT of each bit <>n: n-bit right shift
Explanation of Symbols --: No change
Notes: 1. Instruction execution cycles: The execution cycles shown in the table are minimums. The actual number of cycles may be increased when (1) contention occurs between instruction fetches and data access, or (2) when the destination register of the load instruction (memory register) and the register used by the next instruction are the same. 2. Depending on the instruction's operand size, scaling is x1, x2, or x4. For details, see the SH-1/SH-2/SH-DSP Software Manual.
Rev. 2.00 Mar 09, 2006 page 76 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.20 Data Transfer Instructions
Instruction MOV MOV.W MOV.L MOV MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W #imm,Rn @(disp,PC),Rn @(disp,PC),Rn Rm,Rn Rm,@Rn Rm,@Rn Rm,@Rn @Rm,Rn @Rm,Rn @Rm,Rn Rm,@-Rn Rm,@-Rn Rm,@-Rn @Rm+,Rn @Rm+,Rn @Rm+,Rn R0,@(disp,Rn) R0,@(disp,Rn) Rm,@(disp,Rn) @(disp,Rm),R0 @(disp,Rm),R0 @(disp,Rm),Rn Rm,@(R0,Rn) Rm,@(R0,Rn) Instruction Code Operation Cycles 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 T Bit -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1110nnnniiiiiiii imm Sign extension Rn 1001nnnndddddddd (disp x 2 + PC) Sign extension Rn 1101nnnndddddddd (disp x 4 + PC) Rn 0110nnnnmmmm0011 Rm Rn 0010nnnnmmmm0000 Rm (Rn) 0010nnnnmmmm0001 Rm (Rn) 0010nnnnmmmm0010 Rm (Rn) 0110nnnnmmmm0000 (Rm) Sign extension Rn 0110nnnnmmmm0001 (Rm) Sign extension Rn 0110nnnnmmmm0010 (Rm) Rn 0010nnnnmmmm0100 Rn-1 Rn, Rm (Rn) 0010nnnnmmmm0101 Rn-2 Rn, Rm (Rn) 0010nnnnmmmm0110 Rn-4 Rn, Rm (Rn) 0110nnnnmmmm0100 (Rm) Sign extension Rn,Rm + 1 Rm 0110nnnnmmmm0101 (Rm) Sign extension Rn,Rm + 2 Rm 0110nnnnmmmm0110 (Rm) Rn,Rm + 4 Rm 10000000nnnndddd R0 (disp + Rn) 10000001nnnndddd R0 (disp x 2 + Rn) 0001nnnnmmmmdddd Rm (disp x 4 + Rn) 10000100mmmmdddd (disp + Rm) Sign extension R0 10000101mmmmdddd (disp x 2 + Rm) Sign extension R0 0101nnnnmmmmdddd (disp x 4 + Rm) Rn 0000nnnnmmmm0100 Rm (R0 + Rn) 0000nnnnmmmm0101 Rm (R0 + Rn)
Rev. 2.00 Mar 09, 2006 page 77 of 906 REJ09B0292-0200
Section 2 CPU Instruction MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOV.B MOV.W MOV.L MOVA MOVT Rm,@(R0,Rn) @(R0,Rm),Rn @(R0,Rm),Rn @(R0,Rm),Rn Instruction Code 0000nnnnmmmm0110 0000nnnnmmmm1100 0000nnnnmmmm1101 0000nnnnmmmm1110 Operation Rm (R0 + Rn) (R0 + Rm) Sign extension Rn (R0 + Rm) Sign extension Rn (R0 + Rm) Rn R0 (disp + GBR) R0 (disp x 2 + GBR) R0 (disp x 4 + GBR) (disp + GBR) Sign extension R0 (disp x 2 + GBR) Sign extension R0 (disp x 4 + GBR) R0 disp x 4 + PC R0 T Rn Rm Swap the bottom two bytes Rn Rm Swap upper and lower words Rn Rm: Middle 32 bits of Rn Rn Cycles 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 T Bit -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
R0,@(disp,GBR) 11000000dddddddd R0,@(disp,GBR) 11000001dddddddd R0,@(disp,GBR) 11000010dddddddd @(disp,GBR),R0 11000100dddddddd @(disp,GBR),R0 11000101dddddddd @(disp,GBR),R0 11000110dddddddd @(disp,PC),R0 Rn 11000111dddddddd 0000nnnn00101001 0110nnnnmmmm1000 0110nnnnmmmm1001 0010nnnnmmmm1101
SWAP.B Rm,Rn SWAP.W Rm,Rn XTRCT Rm,Rn
Rev. 2.00 Mar 09, 2006 page 78 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.21 Arithmetic Instructions
Instruction ADD ADD ADDC ADDV CMP/EQ CMP/EQ CMP/HS CMP/GE CMP/HI CMP/GT CMP/PL CMP/PZ Rm,Rn #imm,Rn Rm,Rn Rm,Rn #imm,R0 Rm,Rn Rm,Rn Rm,Rn Rm,Rn Rm,Rn Rn Rn Instruction Code 0011nnnnmmmm1100 0111nnnniiiiiiii 0011nnnnmmmm1110 0011nnnnmmmm1111 10001000iiiiiiii 0011nnnnmmmm0000 0011nnnnmmmm0010 0011nnnnmmmm0011 0011nnnnmmmm0110 0011nnnnmmmm0111 0100nnnn00010101 0100nnnn00010001 0010nnnnmmmm1100 Operation Rn + Rm Rn Rn + imm Rn Rn + Rm + T Rn, Carry T Rn + Rm Rn, Overflow T If R0 = imm, 1 T If Rn = Rm, 1 T If Rn Rm with unsigned data, 1 T Cycles 1 1 1 1 1 1 1 T Bit -- -- Carry Overflow Comparison result Comparison result Comparison result Comparison result Comparison result Comparison result Comparison result Comparison result Comparison result Calculation result Calculation result 0
If Rn Rm with signed 1 data, 1 T If Rn > Rm with unsigned data, 1 T If Rn > Rm with signed data, 1 T If Rn > 0, 1 T If Rn 0, 1 T If Rn and Rm contain an identical byte, 1T Single-step division (Rn/Rm) 1 1 1 1 1
CMP/STR Rm,Rn
DIV1 DIV0S DIV0U
Rm,Rn Rm,Rn
0011nnnnmmmm0100 0010nnnnmmmm0111 0000000000011001
1
MSB of Rn Q, MSB 1 of Rm M, M ^ Q T 0 M/Q/T 1
Rev. 2.00 Mar 09, 2006 page 79 of 906 REJ09B0292-0200
Section 2 CPU
Instruction DMULS.L Rm,Rn
Instruction Code
Operation
Cycles 2 to 4*
T Bit --
0011nnnnmmmm1101 Signed operation of Rn x Rm MACH, MACL 32 x 32 64 bits 0011nnnnmmmm0101 Unsigned operation of Rn x Rm MACH, MACL 32 x 32 64 bits 0100nnnn00010000 Rn - 1 Rn, when Rn is 0, 1 T When Rn is nonzero, 0T 0110nnnnmmmm1110 A byte in Rm is signextended Rn 0110nnnnmmmm1111 A word in Rm is signextended Rn 0110nnnnmmmm1100 A byte in Rm is zeroextended Rn 0110nnnnmmmm1101 A word in Rm is zeroextended Rn 0000nnnnmmmm1111 Signed operation of (Rn) x (Rm) + MAC MAC 32 x 32 + 64 64 bits 0100nnnnmmmm1111 Signed operation of (Rn) x (Rm) + MAC MAC 16 x 16 + 64 64 bits 0000nnnnmmmm0111 Rn x Rm MACL, 32 x 32 32 bits 0010nnnnmmmm1111 Signed operation of Rn x Rm MAC 16 x 16 32 bits 0010nnnnmmmm1110 Unsigned operation of Rn x Rm MAC 16 x 16 32 bits 0110nnnnmmmm1011 0-Rm Rn 0110nnnnmmmm1010 0-Rm-T Rn, Borrow T
DMULU.L Rm,Rn
2 to 4*
--
DT
Rn
1
Comparison result
EXTS.B Rm,Rn EXTS.W Rm,Rn EXTU.B Rm,Rn EXTU.W Rm,Rn MAC.L @Rm+,@Rn+
1 1 1 1
-- -- -- --
3/(2 to 4)* --
MAC.W
@Rm+,@Rn+
3/(2)*
--
MUL.L
Rm,Rn
2 to 4* 1 to 3*
-- --
MULS.W Rm,Rn
MULU.W Rm,Rn
1 to 3*
--
NEG NEGC
Rm,Rn Rm,Rn
1 1
-- Borrow
Rev. 2.00 Mar 09, 2006 page 80 of 906 REJ09B0292-0200
Section 2 CPU Instruction SUB SUBC SUBV Rm,Rn Rm,Rn Rm,Rn Instruction Code 0011nnnnmmmm1000 0011nnnnmmmm1010 0011nnnnmmmm1011 Operation Rn-Rm Rn Rn-Rm-T Rn, Borrow T Rn-Rm Rn, Underflow T Cycles 1 1 1 T Bit -- Borrow Underflow
Note: * The normal number of execution cycles. The number in parentheses is the number of execution cycles in the case of contention with preceding or following instructions.
Table 2.22 Logic Operation Instructions
Instruction AND AND AND.B NOT OR OR OR.B TAS.B TST TST TST.B XOR XOR XOR.B Rm,Rn #imm,R0 #imm,@(R0,GBR) Rm,Rn Rm,Rn #imm,R0 #imm,@(R0,GBR) @Rn Rm,Rn #imm,R0 #imm,@(R0,GBR) Rm,Rn #imm,R0 #imm,@(R0,GBR) Instruction Code 0010nnnnmmmm1001 11001001iiiiiiii 11001101iiiiiiii 0110nnnnmmmm0111 0010nnnnmmmm1011 11001011iiiiiiii 11001111iiiiiiii 0100nnnn00011011 0010nnnnmmmm1000 11001000iiiiiiii 11001100iiiiiiii 0010nnnnmmmm1010 11001010iiiiiiii 11001110iiiiiiii Operation Rn & Rm Rn R0 & imm R0 (R0 + GBR) & imm (R0 + GBR) ~Rm Rn Rn | Rm Rn R0 | imm R0 (R0 + GBR) | imm (R0 + GBR) If (Rn) is 0, 1 T, 1 MSB of (Rn) Rn & Rm, if the result is 0, 1 T R0 & imm, if the result is 0, 1 T Cycles 1 1 3 1 1 1 3 4 1 1 T Bit -- -- -- -- -- -- -- Test result Test result Test result Test result -- -- --
(R0 + GBR) & imm, if the 3 result is 0, 1 T Rn ^ Rm Rn R0 ^ imm R0 (R0 + GBR) ^ imm (R0 + GBR) 1 1 3
Rev. 2.00 Mar 09, 2006 page 81 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.23 Shift Instructions
Instruction ROTL ROTR ROTCL ROTCR SHAL SHAR SHLL SHLR SHLL2 SHLR2 SHLL8 SHLR8 Rn Rn Rn Rn Rn Rn Rn Rn Rn Rn Rn Rn Instruction Code 0100nnnn00000100 0100nnnn00000101 0100nnnn00100100 0100nnnn00100101 0100nnnn00100000 0100nnnn00100001 0100nnnn00000000 0100nnnn00000001 0100nnnn00001000 0100nnnn00001001 0100nnnn00011000 0100nnnn00011001 0100nnnn00101000 0100nnnn00101001 Operation T Rn MSB LSB Rn T T Rn T T Rn T T Rn 0 MSB Rn T T Rn 0 0 Rn T Rn<<2 Rn Rn>>2 Rn Rn<<8 Rn Rn>>8 Rn Rn<<16 Rn Rn>>16 Rn Cycles 1 1 1 1 1 1 1 1 1 1 1 1 1 1 T Bit MSB LSB MSB LSB MSB LSB MSB LSB -- -- -- -- -- --
SHLL16 Rn SHLR16 Rn
Rev. 2.00 Mar 09, 2006 page 82 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.24 Branch Instructions
Instruction BF BF/S BT BT/S label label label label Instruction Code 10001011dddddddd 10001111dddddddd 10001001dddddddd 10001101dddddddd Operation If T = 0, disp x 2 + PC PC, if T = 1, nop Delayed branch, if T = 0, disp x 2 + PC PC, if T = 1, nop If T = 1, disp x 2 + PC PC, if T = 0, nop Delayed branch, if T = 1, disp x 2 + PC PC, if T = 0, nop Delayed branch, disp x 2 + PC PC Delayed branch, Rm + PC PC Delayed branch, PC PR, disp x 2 + PC PC Delayed branch, PC PR, Rm + PC PC Delayed branch, Rm PC Delayed branch, PC PR, Rm PC Delayed branch, PR PC Cycles 3/1* 2/1* 3/1* 2/1* T Bit -- -- -- --
BRA BRAF BSR BSRF JMP JSR RTS
label Rm label Rm @Rm @Rm
1010dddddddddddd 0000mmmm00100011 1011dddddddddddd 0000mmmm00000011 0100mmmm00101011 0100mmmm00001011 0000000000001011
2 2 2 2 2 2 2
-- -- -- -- -- -- --
Note: * One state when it does not branch.
Rev. 2.00 Mar 09, 2006 page 83 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.25 System Control Instructions
Instruction CLRMAC CLRT LDC LDC LDC LDC LDC LDC LDC.L LDC.L LDC.L LDC.L LDC.L LDC.L LDRE LDRS LDS LDS LDS LDS LDS LDS LDS LDS LDS LDS.L LDS.L LDS.L Rm,SR Rm,GBR Rm,VBR Rm,MOD Rm,RE Rm,RS @Rm+,SR @Rm+,GBR @Rm+,VBR @Rm+,MOD @Rm+,RE @Rm+,RS Instruction Code 0000000000101000 0000000000001000 0100mmmm00001110 0100mmmm00011110 0100mmmm00101110 0100mmmm01011110 0100mmmm01111110 0100mmmm01101110 0100mmmm00000111 0100mmmm00010111 0100mmmm00100111 0100mmmm01010111 0100mmmm01110111 0100mmmm01100111 Operation 0 MACH, MACL 0T Rm SR Rm GBR Rm VBR Rm MOD Rm RE Rm RS (Rm) SR, Rm + 4 Rm (Rm) GBR, Rm + 4 Rm (Rm) VBR, Rm + 4 Rm (Rm) MOD, Rm + 4 Rm (Rm) RE, Rm + 4 Rm (Rm) RS, Rm + 4 Rm disp x 2 + PC RE disp x 2 + PC RS Rm MACH Rm MACL Rm PR Rm DSR Rm A0 Rm X0 Rm X1 Rm Y0 Rm Y1 (Rm) MACH, Rm + 4 Rm (Rm) MACL, Rm + 4 Rm (Rm) PR, Rm + 4 Rm Cycles 1 1 1 1 1 1 1 1 3 3 3 3 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 T Bit -- 0 LSB -- -- -- -- -- LSB -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
@(disp,PC) 10001110dddddddd @(disp,PC) 10001100dddddddd Rm,MACH Rm,MACL Rm,PR Rm,DSR Rm,A0 Rm,X0 Rm,X1 Rm,Y0 Rm,Y1 @Rm+,MACH @Rm+,MACL @Rm+,PR 0100mmmm00001010 0100mmmm00011010 0100mmmm00101010 0100mmmm01101010 0100mmmm01111010 0100mmmm10001010 0100mmmm10011010 0100mmmm10101010 0100mmmm10111010 0100mmmm00000110 0100mmmm00010110 0100mmmm00100110
Rev. 2.00 Mar 09, 2006 page 84 of 906 REJ09B0292-0200
Section 2 CPU Instruction LDS.L LDS.L LDS.L LDS.L LDS.L LDS.L NOP RTE SETRC Rm @Rm+,DSR @Rm+,A0 @Rm+,X0 @Rm+,X1 @Rm+,Y0 @Rm+,Y1 Instruction Code 0100mmmm01100110 0100mmmm01110110 0100mmmm10000110 0100mmmm10010110 0100mmmm10100110 0100mmmm10110110 0000000000001001 0000000000101011 0100mmmm00010100 Operation (Rm) DSR, Rm + 4 Rm (Rm) A0, Rm + 4 Rm (Rm) X0, Rm + 4 Rm (Rm) X1, Rm + 4 Rm (Rm) Y0, Rm + 4 Rm (Rm) Y1, Rm + 4 Rm No operation Delayed branch, stack area PC/SR RE-RS operation result (repeat status) RF1, RF0 Rm[11:0] RC (SR[27:16]) SETRC #imm 10000010iiiiiiii RE-RS operation result (repeat status) RF1, RF0 imm RC (SR[23:16]), 0 SR[27:24] SETT SLEEP STC STC STC STC STC STC STC.L STC.L STC.L STC.L STC.L STC.L SR,Rn GBR,Rn VBR,Rn MOD,Rn RE,Rn RS,Rn SR,@-Rn GBR,@-Rn VBR,@-Rn MOD,@-Rn RE,@-Rn RS,@-Rn 0000000000011000 0000000000011011 0000nnnn00000010 0000nnnn00010010 0000nnnn00100010 0000nnnn01010010 0000nnnn01110010 0000nnnn01100010 0100nnnn00000011 0100nnnn00010011 0100nnnn00100011 0100nnnn01010011 0100nnnn01110011 0100nnnn01100011 1T Sleep SR Rn GBR Rn VBR Rn MOD Rn RE Rn RS Rn Rn-4 Rn, SR (Rn) Rn-4 Rn, GBR (Rn) Rn-4 Rn, VBR (Rn) Rn-4 Rn, MOD (Rn) Rn-4 Rn, RE (Rn) Rn-4 Rn, RS (Rn) 1 3* 1 1 1 1 1 1 2 2 2 2 2 2 1 -- -- -- -- -- -- -- -- -- -- -- -- -- 1 1 Cycles T Bit 1 1 1 1 1 1 1 4 1 -- -- -- -- -- -- -- LSB --
Rev. 2.00 Mar 09, 2006 page 85 of 906 REJ09B0292-0200
Section 2 CPU Instruction STS STS STS STS STS STS STS STS STS STS.L STS.L STS.L STS.L STS.L STS.L STS.L STS.L STS.L TRAPA MACH,Rn MACL,Rn PR,Rn DSR,Rn A0,Rn X0,Rn X1,Rn Y0,Rn Y1,Rn MACH,@-Rn MACL,@-Rn PR,@-Rn DSR,@-Rn A0,@-Rn X0,@-Rn X1,@-Rn Y0,@-Rn Y1,@-Rn #imm Instruction Code 0000nnnn00001010 0000nnnn00011010 0000nnnn00101010 0000nnnn01101010 0000nnnn01111010 0000nnnn10001010 0000nnnn10011010 0000nnnn10101010 0000nnnn10111010 0100nnnn00000010 0100nnnn00010010 0100nnnn00100010 0100nnnn01100010 0100nnnn01110010 0100nnnn10000010 0100nnnn10010010 0100nnnn10100010 0100nnnn10110010 11000011iiiiiiii Operation MACH Rn MACL Rn PR Rn DSR Rn A0 Rn X0 Rn X1 Rn Y0 Rn Y1 Rn Rn-4 Rn, MACH (Rn) Rn-4 Rn, MACL (Rn) Rn-4 Rn, PR (Rn) Rn-4 Rn, DSR (Rn) Rn-4 Rn, A0 (Rn) Rn-4 Rn, X0 (Rn) Rn-4 Rn, X1 (Rn) Rn-4 Rn, Y0 (Rn) Rn-4 Rn, Y1 (Rn) PC/SR stack area, (imm x 4 + VBR) PC Cycles T Bit 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 8 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Note: * The number of execution cycles before the chip enters sleep mode.
Rev. 2.00 Mar 09, 2006 page 86 of 906 REJ09B0292-0200
Section 2 CPU
Precautions Concerning the Number of Instruction Execution Cycles: The execution cycles listed in the tables are minimum values. In practice, the number of execution cycles increases under such conditions as 1) when the instruction fetch is in contention with a data access, 2) when the destination register of a load instruction (memory register) is the same as the register used by the next instruction, 3) when the branch destination address of a branch instruction is a 4n + 2 address. CPU Instructions That Support DSP Functions: A number of system control instructions have been added to the CPU core instructions to support DSP functions. The RS, RE and MOD registers have been added to support repeat control and modulo addressing, and the repeat counter (RC) has been added to the status register (SR). The LDC and STC instructions have been added in order to access the aforementioned. The LDS and STS instructions have been added in order to access the DSP registers DSR, A0, X0, X1, Y0 and Y1. The SETRC instruction has been added to set the repeat counter (RC, bits 27 to 16) and repeat flags (RF1, RF0, bits 3 and 2) of the SR register. When the SETRC instruction operand is immediate, the 8-bit immediate data is stored in bits 23 to 16 of the SR register and bits 27 to 24 are cleared to 0. When the operand is a register, bits 11 to 0 (12 bits) of the register are stored in bits 27 to 16 of the SR register. Additionally, the status of 1 instruction repeat (00), 2 instruction repeat (01), 3 instruction repeat (11) or 4 instruction or greater repeat (10) is set from the RS and RE set values. In addition to the LDC instruction, the LDRS and LDRE instructions have been added for establishing the repeat start and repeat end addresses in the RS and RE registers. The added instructions are listed in table 2.26.
Rev. 2.00 Mar 09, 2006 page 87 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.26 Added CPU Instructions
Instruction LDC LDC LDC LDC.L LDC.L LDC.L STC STC STC STC.L STC.L STC.L LDS LDS.L LDS LDS.L LDS LDS.L LDS LDS.L LDS LDS.L LDS LDS.L STS STS.L STS STS.L STS STS.L STS Rm,MOD Rm,RE Rm,RS @Rm+,MOD @Rm+,RE @Rm+,RS MOD,Rn RE,Rn RS,Rn MOD,@-Rn RE,@-Rn RS,@-Rn Rm,DSR @Rm+,DSR Rm,A0 @Rm+,A0 Rm,X0 @Rm+,X0 Rm,X1 @Rm+,X1 Rm,Y0 @Rm+,Y0 Rm,Y1 @Rm+,Y1 DSR,Rn DSR,@-Rn A0,Rn A0,@-Rn X0,Rn X0,@-Rn X1,Rn Code 0100mmmm01011110 0100mmmm01111110 0100mmmm01101110 0100mmmm01010111 0100mmmm01110111 0100mmmm01100111 0000nnnn01010010 0000nnnn01110010 0000nnnn01100010 0100nnnn01010011 0100nnnn01110011 0100nnnn01100011 0100mmmm01101010 0100mmmm01100110 0100mmmm01111010 0100mmmm01110110 0100mmmm10001010 0100mmmm10000110 0100mmmm10011010 0100mmmm10010110 0100mmmm10101010 0100mmmm10100110 0100mmmm10111010 0100mmmm10110110 0000nnnn01101010 0100nnnn01100010 0000nnnn01111010 0100nnnn01110010 0000nnnn10001010 0100nnnn10000010 0000nnnn10011010 Operation RmMOD RmRE RmRS (Rm)MOD,Rm+4Rm (Rm)RE,Rm+4Rm (Rm)RS,Rm+4Rm MODRn RERn RSRn Rn-4Rn,MOD(Rn) Rn-4Rn,RE(Rn) Rn-4Rn,RS(Rn) RmDSR (Rm)DSR,Rm+4Rm RmA0 (Rm)A0,Rm+4Rm RmX0 (Rm)X0,Rm+4Rm RmX1 (Rm)X1,Rm+4Rm RmY0 (Rm)Y0,Rm+4Rm RmY1 (Rm)Y1,Rm+4Rm DSRRn Rn-4Rn,DSR(Rn) A0Rn Rn-4Rn,A0(Rn) X0Rn Rn-4Rn,X0(Rn) X1Rn Cycles 1 1 1 3 3 3 1 1 1 2 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 T Bit -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rev. 2.00 Mar 09, 2006 page 88 of 906 REJ09B0292-0200
Section 2 CPU Instruction STS.L STS STS.L STS STS.L SETRC SETRC LDRS LDRE X1,@-Rn Y0,Rn Y0,@-Rn Y1,Rn Y1,@-Rn Rm #imm @(disp,PC) @(disp,PC) Code 0100nnnn10010010 0000nnnn10101010 0100nnnn10100010 0000nnnn10111010 0100nnnn10110010 0100mmmm00010100 10000010iiiiiiii 10001100dddddddd 10001110dddddddd Operation Rn-4Rn,X1(Rn) Y0Rn Rn-4Rn,Y0(Rn) Y1Rn Rn-4Rn,Y1(Rn) immRC(SR[23:16]), 0SR[27:24] disp x 2+PCRS disp x 2+PCRE Cycles 1 1 1 1 1 1 1 1 T Bit -- -- -- -- -- -- -- -- --
Rm[11:0]RC (SR[27:16]) 1
2.5.2
DSP Data Transfer Instruction Set
Table 2.27 lists the DSP data transfer instructions by classification. Table 2.27 Classification of DSP Data Transfer Instructions
Classification Types Operation Code NOPX MOVX NOPY MOVY Single data transfer instructions 1 MOVS Function X memory no operation X memory data transfer Y memory no operation Y memory data transfer Single data transfer 16 No. of Instructions 14
Double 4 datatransferinstr uctions
Total: 5
Total: 30
The data transfer instructions are divided into two groups, double data transfers and single data transfers. Double data transfers can be combined with DSP operation instructions to perform DSP parallel processing. The parallel processing instructions are 32 bit length, and the double data transfer instructions are incorporated into their A fields. Double data transfers that are not parallel processing instructions are 16 bit length, as are the single data transfer instructions. The X memory and Y memory can be accessed simultaneously in parallel in double data transfers. One instruction each is designated from among the X and Y memory data accesses. The Ax
Rev. 2.00 Mar 09, 2006 page 89 of 906 REJ09B0292-0200
Section 2 CPU
pointer is used to access X memory; the Ay pointer is used to access Y memory. Double data transfers can only access X, Y memory. Single data transfers can be accessed from any area. Single data transfers use the Ax pointer and two other pointers as an As pointer. Table 2.28 Double Data Transfer Instructions (X Memory Data)
Instruction NOPX MOVX.W @Ax,Dx MOVX.W @Ax+,Dx MOVX.W @Ax+Ix,Dx MOVX.W Da,@Ax MOVX.W Da,@Ax+ MOVX.W Da,@Ax+Ix Operation No Operation (Ax)MSW of Dx,0LSW of Dx (Ax)MSW of Dx,0LSW of Dx,Ax+2Ax (Ax)MSW of Dx,0LSW of Dx,Ax+IxAx MSW of Da(Ax) MSW of Da(Ax),Ax+2Ax MSW of Da(Ax),Ax+IxAx Code 1111000*0*0*00** 111100A*D*0*01** 111100A*D*0*10** 111100A*D*0*11** 111100A*D*1*01** 111100A*D*1*10** 111100A*D*1*11** Cycles 1 1 1 1 1 1 1 DC Bit -- -- -- -- -- -- --
Table 2.29 Double Data Transfer Instructions (Y Memory Data)
Instruction NOPY MOVY.W @Ay,Dy MOVY.W @Ay+,Dy MOVY.W @Ay+Iy,Dy MOVY.W Da,@Ay MOVY.W Da,@Ay+ MOVY.W Da,@Ay+Iy Operation No Operation (Ay)MSW of Dy,0LSW of Dy (Ay)MSW of Dy,0LSW of Dy, Ay+2Ay (Ay)MSW of Dy,0LSW of Dy, Ay+IyAy MSW of Da(Ay) MSW of Da(Ay),Ay+2Ay MSW of Da(Ay),Ay+IyAy Code 111100*0*0*0**00 111100*A*D*0**01 111100*A*D*0**10 111100*A*D*0**11 111100*A*D*1**01 111100*A*D*1**10 111100*A*D*1**11 Cycles 1 1 1 1 1 1 1 DC Bit -- -- -- -- -- -- --
Rev. 2.00 Mar 09, 2006 page 90 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.30 Single Data Transfer Instructions
Instruction MOVS.W @-As,Ds MOVS.W @As,Ds MOVS.W @As+,Ds MOVS.W @As+Ix,Ds MOVS.W Ds,@-As MOVS.W Ds,@As MOVS.W Ds,@As+ MOVS.W Ds,@As+Is MOVS.L @-As,Ds MOVS.L @As,Ds MOVS.L @As+,Ds MOVS.L @As+Is,Ds MOVS.L Ds, @-As MOVS.L Ds,@As MOVS.L Ds,@As+ MOVS.L Ds,@As+Is Operation As-2As,(As)MSW of Ds,0LSW of Ds (As)MSW of Ds,0LSW of Ds (As)MSW of Ds,0LSW of Ds, As+2As (As)MSW of Ds,0LSW of Ds, As+IxAs As-2As,MSW of Ds(As)* MSW of Ds(As)* MSW of Ds(As)*,As+2As MSW of Ds(As)*,As+IsAs As-4As,(As)Ds (As)Ds (As)Ds,As+4As (As)Ds,As+IsAs As-4As,Ds(As)* Ds(As)* Ds(As)*,As+4As Ds(As)*,As+IsAs Code 111101AADDDD0000 111101AADDDD0100 111101AADDDD1000 111101AADDDD1100 111101AADDDD0001 111101AADDDD0101 111101AADDDD1001 111101AADDDD1101 111101AADDDD0010 111101AADDDD0110 111101AADDDD1010 111101AADDDD1110 111101AADDDD0011 111101AADDDD0111 111101AADDDD1011 111101AADDDD1111 Cycles 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 DC Bit -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Note: * When guard bit registers A0G and A1G are specified for the source operand Ds, data is sign-extended before being transferred.
Rev. 2.00 Mar 09, 2006 page 91 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.31 shows the correspondence between the DSP data transfer operands and registers. CPU core registers are used as pointer addresses indicating memory addresses. Table 2.31 Correspondence between DSP Data Transfer Operands and Registers
SH (CPU Core) Registers Operand Ax Ix (Is) Dx Ay Iy Dy Da As Ds R2 (As2) -- -- -- -- -- -- -- Yes -- R3 (As3) -- -- -- -- -- -- -- Yes -- R4 (Ax0) (As0) Yes -- -- -- -- -- -- Yes -- R5 (Ax1) (As0) Yes -- -- -- -- -- -- Yes -- DSP Registers X0 -- -- Yes -- -- -- -- -- Yes X1 -- -- Yes -- -- -- -- -- Yes Y0 -- -- -- -- -- Yes -- -- Yes Y1 -- -- -- -- -- Yes -- -- Yes M0 -- -- -- -- -- -- -- -- Yes M1 -- -- -- -- -- -- -- -- Yes A0 -- -- -- -- -- -- Yes -- Yes A1 -- -- -- -- -- -- Yes -- Yes A0G -- -- -- -- -- -- -- -- Yes A1G -- -- -- -- -- -- -- -- Yes R6 (Ay0) -- -- -- Yes -- -- -- -- -- R7 (Ay1) -- -- -- Yes -- -- -- -- -- R8 (Ix) (Is) -- Yes -- -- -- -- -- -- -- R9 (Iy) -- -- -- -- Yes -- -- -- --
R0 -- -- -- -- -- -- -- -- --
R1 -- -- -- -- -- -- -- -- --
Operand Ax Ix (Is) Dx Ay Iy Dy Da As Ds
Note: Yes indicates that the register can be set.
Rev. 2.00 Mar 09, 2006 page 92 of 906 REJ09B0292-0200
Section 2 CPU
2.5.3
DSP Operation Instruction Set
DSP operation instructions are digital signal processing instructions processed by the DSP unit. These instructions use 32-bit instruction codes, and multiple instructions are executed in parallel. The instruction codes are divided into an A field and a B field; parallel data transfer instructions are designated in the A field, and single or double data operation instructions are designated in the B field. Instructions can be independently designated and execution can also be carried out independently. A parallel data transfer instruction designated in the A field is exactly the same as a double data transfer instruction. The B field data operation instructions are divided into three groups: double data operation instructions, conditional single data operation instructions, and unconditional single data operation instructions. Table 2.32 lists the instruction formats of the DSP operation instructions. Each of the operands can be independently selected from the DSP registers. Table 2.33 shows the correspondence between the DSP operation instruction operands and registers. Table 2.32 DSP Operation Instruction Formats
Classification Double data operation instructions (6 operands) Conditional single data operation instructions 3 operands Instruction Forms Instruction
ALUop. Sx, Sy, Du PADD PMULS, MLTop. Se, Sf, Dg PSUB PMULS ALUop. Sx, Sy, Dz PADD, PAND, POR, DCT ALUop. Sx, Sy, Dz PSHA, PSHL, PSUB, PXOR DCF ALUop. Sx, Sy, Dz ALUop. Sx, Dz DCT ALUop. Sx, Dz DCF ALUop. Sx, Dz ALUop. Sy, Dz DCT ALUop. Sy, Dz DCF ALUop. Sy, Dz PCOPY, PDEC, PDMSB, PINC, PLDS, PSTS, PNEG
2 operands
1 operand
ALUop. Dz DCT ALUop. Dz DCF ALUop. Dz
PCLR, PSHA #imm, PSHL #imm
Unconditional single data operation instructions
3 operands 2 operands
ALUop. Sx, Sy, Du PADDC, PSUBC, MLTop. Se, Sf, Dg PMULS ALUop. Sx, Dz ALUop. Sy, Dz ALUop. Sx, Sy PCMP, PABS, PRND
1 operand
ALUop. Dz
PSHA #imm, PSHL #imm
Rev. 2.00 Mar 09, 2006 page 93 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.33 Correspondence between DSP Instruction Operands and Registers
ALU and BPU Instructions Register A0 A1 M0 M1 X0 X1 Y0 Y1 Sx Yes Yes -- -- Yes Yes -- -- Sy -- -- Yes Yes -- -- Yes Yes Dz Yes Yes Yes Yes Yes Yes Yes Yes Du Yes Yes -- -- Yes -- Yes -- Se -- Yes -- -- Yes Yes Yes -- Multiplication Instructions Sf -- Yes -- -- Yes -- Yes Yes Dg Yes Yes Yes Yes -- -- -- --
When writing parallel instructions, write the B field instructions first, then write the A field instructions:
PADD A0,M0,A0 PMULS X0,Y0,M0 DCF PINC X1,A1 PCMP X1,M0 MOVX.W @R4+,X0 MOVX.W A0,@R5+R8 MOVX.W @R4+R8 MOVY.W @R6+,Y0[;] MOVY.W @R7+,Y0[;] [NOPY][;]
Text in brackets ([]) can be omitted. The no operation instructions NOPX and NOPY can be omitted. Semicolons (;) are used to demarcate instruction lines, but can be omitted. If semicolons are used, the space after the semicolon can be used for comments. The individual status codes (DC, N, Z, V, GT) of the DSR register are always updated by unconditional ALU operation instructions and shift operation instructions. Conditional instructions do not update the status codes, even if the conditions have been met. Multiplication instructions also do not update the status codes. DC bit definitions are determined by the specifications of the CS bits in the DSR register. Table 2.34 lists the DSP operation instructions by classification.
Rev. 2.00 Mar 09, 2006 page 94 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.34 Classification of DSP Instructions
Classification Instruction Types Operation Code PABS PADD PADD PMULS PADDC PCLR PCMP PCOPY PNEG PSUB PSUB PMULS PSUBC ALU integer operation instructions MSB detection instruction Rounding operation instruction ALU logical operation instructions Fixed decimal point multiplication instruction Shift Arithmetic shift operation instruction Logical shift operation instruction System control instructions 2 PDEC PINC 1 1 PDMSB PRND Function Absolute value operation Addition Addition and signed multiplication Addition with carry Clear Compare Copy Invert sign Subtraction Subtraction and signed multiplication Subtraction with borrow Decrement Increment MSB detection Rounding 6 2 12 No. of Instructions 28
ALU arith- ALU fixed decimal 11 metic point operation operation instructions instructions instructions
3
PAND POR PXOR
Logical AND Logical OR Logical exclusive OR Signed multiplication Arithmetic shift
9
1 1
PMULS PSHA
1 4
1
PSHL
Logical shift
4
2
PLDS PSTS
System register load Store from system register
12
Total 23
Total 78
Rev. 2.00 Mar 09, 2006 page 95 of 906 REJ09B0292-0200
Section 2 CPU
2.5.4
Various Operation Instructions
ALU Arithmetic Operation Instructions: Tables 2.35-2.44 list various operation instructions. Table 2.35 ALU Fixed Point Operation Instructions
Instruction PABS Sx,Dz Operation If Sx0,SxDz If Sx<0,0- SxDz PABS Sy,Dz If Sy0,SyDz If Sy<0,0-SyDz PADD Sx,Sy,Dz Sx+SyDz if DC=1,Sx+SyDz if 0,nop if DC=0,Sx+SyDz if 1,nop Sx+SyDu MSW of Se x MSW of SfDg Sx+Sy+DCDz H'00000000Dz if DC=1,H'00000000Dz if 0,nop DCF PCLR Dz if DC=0,H'00000000Dz if 1,nop PCMP Sx,Sy Sx-Sy SxDz SyDz if DC=1,SxDz if 0,nop Code 111110********** 10001000xx00zzzz 111110********** 1010100000yyzzzz 111110********** 10110001xxyyzzzz DCT PADD Sx,Sy,Dz DCF PADD Sx,Sy,Dz PADD Sx,Sy,Du PMULS Se,Sf,Dg PADDC Sx,Sy,Dz PCLR Dz 111110********** 10110010xxyyzzzz 111110********** 10110011xxyyzzzz 111110********** 0111eeffxxyygguu 111110********** 10110000xxyyzzzz 111110********** 100011010000zzzz DCT PCLR Dz 111110********** 100011100000zzzz 111110********** 100011110000zzzz 111110********** 10000100xxyy0000 PCOPY Sx,Dz 111110********** 11011001xx00zzzz PCOPY Sy,Dz 111110********** 1111100100yyzzzz DCT PCOPY Sx,Dz 111110********** 11011010xx00zzzz 1 -- 1 Update 1 Update 1 Update 1 -- 1 -- 1 Update 1 Update 1 Update 1 -- 1 -- 1 Update 1 Update Cycles 1 DC Bit Update
Rev. 2.00 Mar 09, 2006 page 96 of 906 REJ09B0292-0200
Section 2 CPU Instruction DCT PCOPY Sy,Dz DCF PCOPY Sx,Dz DCF PCOPY Sy,Dz PNEG Sx,Dz Operation if DC=1,SyDz if 0,nop if DC=0,SxDz if 1,nop if DC=0,SyDz if 1,nop 0-SxDz 0-SyDz if DC=1,0-SxDz if 0,nop if DC=1,0-SyDz if 0,nop if DC=0,0-SxDz if 1,nop if DC=0,0-SyDz if 1,nop Sx-SyDz if DC=1,Sx-SyDz if 0,nop if DC=0,Sx-SyDz if 1,nop Sx-SyDu MSW of Se x MSW of SfDg Sx-Sy-DCDz Code 111110********** 1111101000yyzzzz 111110********** 11011011xx00zzzz 111110********** 1111101100yyzzzz 111110********** 11001001xx00zzzz PNEG Sy,Dz 111110********** 1110100100yyzzzz DCT PNEG Sx,Dz DCT PNEG Sy,Dz DCF PNEG Sx,Dz DCF PNEG Sy,Dz PSUB Sx,Sy,Dz 111110********** 11001010xx00zzzz 111110********** 1110101000yyzzzz 111110********** 11001011xx00zzzz 111110********** 1110101100yyzzzz 111110********** 10100001xxyyzzzz DCT PSUB Sx,Sy,Dz DCF PSUB Sx,Sy,Dz PSUB Sx,Sy,Du PMULS Se,Sf,Dg PSUBC Sx,Sy,Dz 111110********** 10100010xxyyzzzz 111110********** 10100011xxyyzzzz 111110********** 0110eeffxxyygguu 111110********** 10100000xxyyzzzz 1 Update 1 Update 1 -- 1 -- 1 Update 1 -- 1 -- 1 -- 1 -- 1 Update 1 Update 1 -- 1 -- Cycles 1 DC Bit --
Rev. 2.00 Mar 09, 2006 page 97 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.36 ALU Integer Operation Instructions
Instruction PDEC Sx,Dz Operation MSW of Sx - 1 MSW of Dz, clear LSW of Dz MSW of Sy - 1 MSW of Dz, clear LSW of Dz If DC=1, MSW of Sx - 1 MSW of Dz, clear LSW of Dz; if 0, nop If DC=1, MSW of Sy - 1 MSW of Dz, clear LSW of Dz; if 0, nop If DC=0, MSW of Sx - 1 MSW of Dz, clear LSW of Dz; if 1, nop If DC=0, MSW of Sy - 1 MSW of Dz, clear LSW of Dz; if 1, nop MSW of Sx + 1 MSW of Dz, clear LSW of Dz MSW of Sy + 1 MSW of Dz, clear LSW of Dz If DC=1, MSW of Sx + 1 MSW of Dz, clear LSW of Dz; if 0, nop If DC=1, MSW of Sy + 1 MSW of Dz, clear LSW of Dz; if 0, nop If DC=0, MSW of Sx + 1 MSW of Dz, clear LSW of Dz; if 1, nop If DC=0, MSW of Sy + 1 MSW of Dz, clear LSW of Dz; if 1, nop Code 111110********** 10001001xx00zzzz 111110********** 1010100100yyzzzz 111110********** 10001010xx00zzzz 111110********** 1010101000yyzzzz 111110********** 10001011xx00zzzz 111110********** 1010101100yyzzzz 111110********** 10011001xx00zzzz 111110********** 1011100100yyzzzz 111110********** 10011010xx00zzzz 111110********** 1011101000yyzzzz 111110********** 10011011xx00zzzz 111110********** 1011101100yyzzzz 1 -- 1 -- 1 -- 1 -- 1 Update 1 Update 1 -- 1 -- 1 -- 1 -- 1 Update Cycles 1 DC Bit Update
PDEC Sy,Dz
DCT PDEC Sx,Dz DCT PDEC Sy,Dz DCF PDEC Sx,Dz DCF PDEC Sy,Dz PINC Sx,Dz
PINC Sy,Dz
DCT PINC Sx,Dz DCT PINC Sy,Dz DCF PINC Sx,Dz DCF PINC Sy,Dz
Rev. 2.00 Mar 09, 2006 page 98 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.37 MSB Detection Instructions
Instruction PDMSB Sx,Dz Operation Sx data MSB position MSW of Dz, clear LSW of Dz Sy data MSB position MSW of Dz, clear LSW of Dz If DC=1, Sx data MSB position MSW of Dz, clear LSW of Dz; if 0, nop If DC=1, Sy data MSB position MSW of Dz, clear LSW of Dz; if 0, nop If DC=0, Sx data MSB position MSW of Dz, clear LSW of Dz; if 1, nop If DC=0, Sy data MSB position MSW of Dz, clear LSW of Dz; if 1, nop Code 111110********** 10011101xx00zzzz 111110********** 1011110100yyzzzz 111110********** 10011110xx00zzzz 111110********** 1011111000yyzzzz 111110********** 10011111xx00zzzz 111110********** 1011111100yyzzzz 1 -- 1 -- 1 -- 1 -- 1 Update Cycles 1 DC Bit Update
PDMSB Sy,Dz
DCT PDMSB Sx,Dz DCT PDMSB Sy,Dz DCF PDMSB Sx,Dz DCF PDMSB Sy,Dz
Table 2.38 Rounding Operation Instructions
Instruction PRND Sx,Dz Operation Sx+H'00008000Dz clear LSW of Dz PRND Sy,Dz Sy+H'00008000Dz clear LSW of Dz Code 111110********** 10011000xx00zzzz 111110********** 1011100000yyzzzz 1 Update Cycles 1 DC Bit Update
Rev. 2.00 Mar 09, 2006 page 99 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.39 ALU Logical Operation Instructions
Instruction PAND Sx,Sy,Dz Operation Sx & Sy Dz, clear LSW of Dz If DC=1, Sx & Sy Dz, clear LSW of Dz; if 0, nop If DC=0, Sx & Sy Dz, clear LSW of Dz; if 1, nop Sx | Sy Dz, clear LSW of Dz If DC=1, Sx | Sy Dz, clear LSW of Dz; if 0, nop If DC=0, Sx | Sy Dz, clear LSW of Dz; if 1, nop Sx ^ Sy Dz, clear LSW of Dz If DC=1, Sx ^ Sy Dz, clear LSW of Dz; if 0, nop If DC=0, Sx ^ Sy Dz, clear LSW of Dz; if 1, nop Code 111110********** 10010101xxyyzzzz 111110********** 10010110xxyyzzzz 111110********** 10010111xxyyzzzz 111110********** 10110101xxyyzzzz 111110********** 10110110xxyyzzzz 111110********** 10110111xxyyzzzz 111110********** 10100101xxyyzzzz 111110********** 10100110xxyyzzzz 111110********** 10100111xxyyzzzz 1 -- 1 -- 1 Update 1 -- 1 -- 1 Update 1 -- 1 -- Cycles 1 DC Bit Update
DCT PAND Sx,Sy,Dz DCF PAND Sx,Sy,Dz POR Sx,Sy,Dz
DCT POR Sx,Sy,Dz DCF POR Sx,Sy,Dz PXOR Sx,Sy,Dz
DCT PXOR Sx,Sy,Dz DCF PXOR Sx,Sy,Dz
Table 2.40 Fixed Point Multiplication Instructions
Instruction PMULS Se,Sf,Dg Operation MSW of Se x MSW of SfDg Code 111110********** 0100eeff0000gg00 Cycles 1 DC Bit --
Rev. 2.00 Mar 09, 2006 page 100 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.41 Arithmetic Shift Operation Instructions
Instruction PSHA Sx,Sy,Dz Operation if Sy0,Sx<>SyDz DCT PSHA Sx,Sy,Dz if DC=1 & Sy0,Sx<>SyDz if DC=0,nop DCF PSHA Sx,Sy,Dz if DC=0 & Sy0,Sx<>SyDz if DC=1,nop PSHA #imm,Dz if imm0,Dz<>immDz 111110********** 00010iiiiiiizzzz 1 Update 111110********** 10010011xxyyzzzz 1 -- Code 111110********** 10010001xxyyzzzz 111110********** 10010010xxyyzzzz 1 -- Cycles 1 DC Bit Update
Rev. 2.00 Mar 09, 2006 page 101 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.42 Logical Shift Operation Instructions
Instruction PSHL Sx,Sy,Dz Operation if Sy0,Sx<>SyDz, clear LSW of Dz DCT PSHL Sx,Sy,Dz if DC=1 & Sy0,Sx<>SyDz, clear LSW of Dz if DC=0,nop DCF PSHL Sx,Sy,Dz if DC=0 & Sy0,Sx<>SyDz, clear LSW of Dz if DC=1,nop PSHL #imm,Dz if imm0,Dz<>immDz, clear LSW of Dz 111110********** 00000iiiiiiizzzz 1 Update 111110********** 10000011xxyyzzzz 1 -- 111110********** 10000010xxyyzzzz 1 -- Code 111110********** 10000001xxyyzzzz Cycles 1 DC Bit Update
Rev. 2.00 Mar 09, 2006 page 102 of 906 REJ09B0292-0200
Section 2 CPU
Table 2.43 System Control Instructions
Instruction PLDS Dz,MACH PLDS Dz,MACL DCT PLDS Dz,MACH DCT PLDS Dz,MACL DCF PLDS Dz,MACH DCF PLDS Dz,MACL PSTS MACH,Dz PSTS MACL,Dz DCT PSTS MACH,Dz DCT PSTS MACL,Dz DCF PSTS MACH,Dz DCF PSTS MACL,Dz Operation DzMACH DzMACL if DC=1,DzMACH if 0,nop if DC=1,DzMACL if 0,nop if DC=0,DzMACH if 1,nop if DC=0,DzMACL if 1,nop MACHDz MACLDz if DC=1,MACHDz if 0,nop if DC=1,MACLDz if 0,nop if DC=0,MACHDz if 1,nop if DC=0,MACLDz if 1,nop Code 111110********** 111011010000zzzz 111110********** 111111010000zzzz 111110********** 111011100000zzzz 111110********** 111111100000zzzz 111110********** 111011110000zzzz 111110********** 111111110000zzzz 111110********** 110011010000zzzz 111110********** 110111010000zzzz 111110********** 110011100000zzzz 111110********** 110111100000zzzz 111110********** 110011110000zzzz 111110********** 110111110000zzzz 1 -- 1 -- 1 -- 1 -- 1 -- 1 -- 1 -- 1 -- 1 -- 1 -- 1 -- Cycles 1 DC Bit --
Rev. 2.00 Mar 09, 2006 page 103 of 906 REJ09B0292-0200
Section 2 CPU
When there are no data transfer instructions being processed simultaneously in parallel with DSP operation instructions, it is possible to either write NOPX, NOPY instructions or to omit the instructions. The instruction codes are the same regardless of whether the NOPX, NOPY instructions are written or omitted. Table 2.44 gives some examples of NOPX and NOPY instruction codes. Table 2.44 NOPX and NOPY Instruction Codes
Instruction PADD X0, Y0, A0 MOVX.W @R4+, X0 MOVY.W @R6+R9, Y0 Code 1111100000001011 1011000100000111 PADD X0, Y0, A0 NOPX MOVY.W @R6+R9, Y0 1111100000000011 1011000100000111 PADD X0, Y0, A0 NOPX NOPY 1111100000000000 1011000100000111 PADD X0, Y0, A0 NOPX 1111100000000000 1011000100000111 PADD X0, Y0, A0 1111100000000000 1011000100000111 MOVX.W @R4+, X0 MOVY.W @R6+R9, Y0 MOVX.W @R4+, X0 NOPY MOVS.W @R4+, X0 NOPX MOVY.W @R6+R9, Y0 MOVY.W @R6+R9, Y0 NOPX NOP NOPY 1111000000001011 1111000000001000 1111010010001000 1111000000000011 1111000000000011 1111000000000000 0000000000001001
Rev. 2.00 Mar 09, 2006 page 104 of 906 REJ09B0292-0200
Section 2 CPU
2.6
2.6.1
Usage Notes
When not using DSP instructions
When DSP instructions are not used, execute the following dummy instruction in the initialization section of application software in order to reduce the operating current.
PCLR PSHA A0 : Clear the A0 register. #5, A0 : 5 bit shift to left.
2.6.2
When executing a combination of double-precision multiplication or doubleprecision product-sum operation (CPU instruction) and DSP computing instruction
When double-precision multiplication (MUL.L, DMULU.L, DMULS.L) or double-precision product-sum operation (MAC.L) in CPU instructions is executed in combination with DSP computing instruction (when the following conditions 1 and 2 are met simultaneously), a malfunction may occur in the instructions indicated in 2-b. 1. Execution of instructions from the internal memory or cache. 2. Execution of the following instruction strings in the order of a, b and c. a. Double-precision multiplication (MUL.L, DMULU.L, DMULS.L) or double-precision product-sum operation (MAC.L) b. DSP computing instruction excluding PMULS, PSTS and PLDS c. Execution of PMLS, PSTS or PLDS instruction
The above caution also applies when there is a delayed jump instruction immediately before the above 2-a, and the instruction 2-a is in a delayed slot, and the instructions 2-b and 2-c are described continuously at the jump destination. To prevent the malfunction, take one of the following measures. 1 Do not execute the instruction string described in the above condition 2. 2. When the instruction string described in the above condition 2 exists on the instruction code and if no problem is caused by switching instructions b and c, switch the locations of instructions b and c. 3. When the instruction string described in the above condition 2 exists on the instruction code and if a problem is caused by switching instructions b and c, insert one or more NOP instructions or CPU instructions that are not related to the multiplier.
Rev. 2.00 Mar 09, 2006 page 105 of 906 REJ09B0292-0200
Section 2 CPU
Rev. 2.00 Mar 09, 2006 page 106 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
Section 3 Oscillator Circuits and Operating Modes
3.1 Overview
Operation of the on-chip clock pulse generator, and CS0 area bus width specification, are controlled by the operating mode pins. A crystal resonator or external clock can be selected as the clock source.
3.2
3.2.1
On-Chip Clock Pulse Generator and Operating Modes
Clock Pulse Generator
A block diagram of the on-chip clock pulse generator circuit is shown in figure 3.1.
system clock CAP1 CKIO PLL circuit 1 DIVM 1/1 1/2 1/4 On/Off CAP2 EXTAL Oscillator XTAL CKPREQ/CKM The relationship between the internal clock frequencies is: I E P. Maximum frequencies are: I, E 62.5 MHz, P 31.25 MHz. DIVP 1/1 1/2 1/4 P Peripheral module clock DIVE 1/1 1/2 1/4 E External interface clock
I CPU/DSP core clock
PLL circuit 2 x1, x2, x4
MD2 MD1 MD0 CKPACK* Note: See section 21.4.4, Clock Pause Function. Clock mode control circuit
Figure 3.1 Block Diagram of Clock Pulse Generator Circuit
Rev. 2.00 Mar 09, 2006 page 107 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
Pin Configuration: Table 3.1 lists the functions relating to the pins relating to the oscillator circuit. Table 3.1
Pin Name CKIO XTAL EXTAL CAP1 CAP2 MD0 MD1 MD2 CKPREQ/CKM CKPACK
Pin Configuration
I/O I/O O I I I I I I I O Used as the clock pause request pin, or specifies operation of the crystal resonator Clock pause function Function External clock input pin or internal clock output pin Connects to the crystal resonator Connects to the crystal resonator or to the external clock input when using PLL circuit 2 Connects to capacitance for operating PLL circuit 1 Connects to capacitance for operating PLL circuit 2 The level applied to these pins specifies the clock mode
PLL Circuit 1: PLL circuit 1 eliminates phase differences between external clocks and clocks supplied internally within the chip. In high-speed operation, the phase difference between the reference clocks and operating clocks in the chip directly affects the interface margin with peripheral devices. On-chip PLL circuit 1 is provided to eliminate this effect. PLL Circuit 2: PLL circuit 2 either leaves unchanged, doubles, or quadruples the frequency of clocks provided from the crystal resonator or the EXTAL pin external clock input for the chip operating frequency. The frequency modification register sets the clock frequency multiplication factor.
Rev. 2.00 Mar 09, 2006 page 108 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
3.2.2
Clock Operating Mode Settings
Table 3.2 lists the functions and operation of clock modes 0 to 6. Table 3.2
Clock Mode 0
Operating Modes
Function/Operation Clock Source
PLL circuits 1 and 2 operate. A clock is output with the same Crystal resonator/ phase (with the same frequency as E) as the internal clocks external clock input (I, E, P) from the CKIO pin PLL circuits 1 and 2 can be switched between the operating and halted states by means of control bits in the frequency modification register (FMR). The CKIO pin can also be placed in the high-impedance state Normally, mode 0 should be used.
1
PLL circuits 1 and 2 operate. A clock (with the same frequency as E) 1/4 cycle in advance of the chip's internal system clock is output from the CKIO pin. PLL circuits 1 and 2 can be switched between the operating and halted states by means of control bits in the frequency modification register (FMR). The CKIO pin can also be placed in the high-impedance state. However, clock phase shifting is not performed when PLL circuit 1 is halted. Normally, mode 0 should be used.
2
Only PLL circuit 2 operates. The clock from PLL circuit 2 is output from the CKIO pin (having the same frequency as the E). As PLL circuit 1 does not operate, phases are not matched in this mode PLL circuit 2 can be switched between the operating and halted states by means of a control bit in the frequency modification register (FMR). The CKIO pin can also be placed in the high-impedance state
3
Only PLL circuit 2 operates. The CKIO pin is high-impedance PLL circuit 2 can be switched between the operating and halted states by means of a control bit in the frequency modification register (FMR)
4
Only PLL circuit 1 operates. Operate PLL circuit 1 when operating with synchronization of the phases of the clock input from the CKIO pin and the internal clocks (I, E, P). PLL circuit 2 does not operate in this mode PLL circuit 1 can be switched between the operating and halted states by means of a control bit in the frequency modification register (FMR)
External clock input
Rev. 2.00 Mar 09, 2006 page 109 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes Clock Mode 5 Function/Operation Only PLL circuit 1 operates. Operate PLL circuit 1 when operating with a 1/4 cycle lag of the clock input from the CKIO pin and the internal clocks (I, E, P) with respect to system clock . PLL circuit 2 does not operate in this mode PLL circuit 1 can be switched between the operating and halted states by means of control bits in the frequency modification register (FMR). However, clock phase shifting is not performed when PLL circuit 1 is halted. Normally, mode 4 should be used. 6 PLL circuits 1 and 2 do not operate. Set this mode when a clock having a frequency equal to that of clocks the clock input from the CKIO pin is used Clock Source External clock input
The internal clock frequency can be changed in each clock mode (see section 3.2.5, Operating Frequency Selection by Register). In clock modes 4 to 6, the frequency of the clock input from the CKIO pin can be changed, or the clock can be stopped (see section 21.4.4, Clock Pause Function). Table 3.3 lists the relationship between pins MD2 to MD0 and the clock operating mode. Do not switch the MD2-MD0 pins while they are operating. Switching will cause operating errors.
Rev. 2.00 Mar 09, 2006 page 110 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
Table 3.3
Clock Mode Pin Settings and States
Pin CKPREQ/ CKPREQ CKM 0 1
Clock Mode 0
MD2 0
MD1 0
MD0 0
EXTAL Clock input Crystal oscillation Clock input Crystal oscillation Clock input Crystal oscillation Clock input Crystal oscillation Open Open Open
XTAL Open Crystal oscillation Open Crystal oscillation Open Crystal oscillation Open Crystal oscillation Open Open Open
CKIO Output/high impedance Output/high impedance Output/high impedance High impedance Clock input Clock input Clock input
1
0
0
1
0 1
2
0
1
0
0 1
3
0
1
1
0 1
4 5 6
1 1 1
0 0 1
0 1 0
*
Notes: Do not use in combinations other than those listed. * In clock modes 4, 5, and 6, CKPREQ/CKM functions as the clock pause request pin.
Rev. 2.00 Mar 09, 2006 page 111 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
3.2.3
Connecting a Crystal Resonator
Connecting a Crystal Resonator: Figure 3.2 shows an example of crystal resonator connection. The values of damping resistance R and load capacitances CL1 and CL2 should be decided after investigating the components in collaboration with the manufacturer of the crystal oscillator to be used. The crystal resonator should be an AT-cut parallel-oscillator type. Place the crystal resonator and its load capacitors as close as possible to the XTAL and EXTAL pins. Other signal lines should be routed away from the oscillator circuit to prevent induction from interfering with correct oscillation.
High level CKPREQ/CKM CKIO EXTAL CL2 XTAL R Notes: 1. The CKIO pin is an output in clock modes 0,1, and 2. In mode 3, it is high impedance. 2. The values for CL1, CL2, and the damping resistance should be determined after consultation with the crystal resonator manufacturer. Output or high impedance CL1
Figure 3.2 Example of Crystal Oscillator Connection
Rev. 2.00 Mar 09, 2006 page 112 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
3.2.4
External Clock Input
An external clock is input from the EXTAL pin or the CKIO pin, depending on the clock mode. Clock Input from EXTAL Pin: This method can be used in clock modes 0, 1, 2, and 3.
Ground level The CKIO pin is an output in clock modes 0, 1, and 2, and is high-impedance in clock mode 3.
CKPREQ/CKM
CKIO
Output or high-impedance
EXTAL
External Clock Input
XTAL
Open
Figure 3.3 External Clock Input Method Clock Input from CKIO Pin: This method can be used in clock modes 4, 5, and 6.
CKPREQ/CKM
The CKPREQ/CKM pin is the clock pause request input pin. External Clock Input
CKIO
EXTAL
Open
XTAL
Open
Figure 3.4 External Clock Input Method
Rev. 2.00 Mar 09, 2006 page 113 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
3.2.5
Operating Frequency Selection by Register
Using the frequency modification register (FMR), it is possible to specify the operating frequency division ratio for the internal clocks (I, E, P). The internal clock frequency is determined under the control of PLL circuits 1 and 2 and dividers DIVM, DIVE, and DIVP. Frequency Modification Register (FMR): The frequency modification register is initialized only by a power-on reset via the RES pin, and not by an internal reset resulting from WDT overflow. Its initial value depends on the settings of pins MD2-MD0. Table 3.4 shows the relationship between the MD2-MD0 pin combinations and the initial value of the frequency modification register. Table 3.4
Clock Mode Mode 0 Mode 1 Mode 2 Mode 3 Mode 4 Mode 5 Mode 6
Relationship between Clock Mode Pin Settings and Initial Value of Frequency Modification Register
MD2 0 0 0 0 1 1 1 MD1 0 0 1 1 0 0 1 MD0 0 1 0 1 0 1 0 H'E0 H'40 H'60 H'A6 Initial Value H'00
The register configuration is shown in table 3.5. Table 3.5
Name Frequency modification register
Register Configuration
Abbreviation FMR R/W R/W Initial Value See table 3.4* Address H'FFFFFE90
Note: * The initial value depends on the clock mode.
Rev. 2.00 Mar 09, 2006 page 114 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes Bit: Initial value: R/W: 7 PLL2ST -- R/W 6 PLL1ST -- R/W 5 CKIOST -- R/W 4 -- 0 R 3 FR3 0 R/W 2 FR2 -- R/W 1 FR1 -- R/W 0 FR0 0 R/W
Bit 7--PLL2ST: Switching is possible in modes 0 to 3. In modes 4 to 6, PLL circuit 2 cannot be used. In these modes, this bit always reads 1.
Bit 7: PLL2ST 0 1 Description PLL circuit 2 used PLL circuit 2 not used
Bit 6--PLL1ST: Switching is possible in modes 0, 1, 4, and 5. In modes 2, 3, and 6, PLL circuit 1 cannot be used. In these modes, this bit always reads 1.
Bit 6: PLL1ST 0 1 Description PLL circuit 1 is used PLL circuit 1 is not used
Bit 5--CKIOST: Setting is possible in modes 0 to 3. In modes 4 to 6, the CKIO pin is an input pin. In these modes, this bit always reads 1.
Bit 5: CKIOST 0 1 Description The CKIO pin outputs E The CKIO pin is in the high-impedance state (Do not place CKIO in the highimpedance state when PLL circuit 1 is operating)
Bit 4--Reserved: This bit is always read as 0. The write value should always be 0. Bits 3 to 0--FR3 to FR0: The internal clock frequency and CKIO output frequency (modes 0-2) can be set by frequency setting bits FR3-FR0. The values that can be set in bits FR3-FR0 depend on the mode and whether PLL circuit 1 and PLL circuit 2 are operating or halted. The following tables show the values that can be set in FR3-FR0, and the internal clock and CKIO output frequency ratios, taking the external input clock frequency as 1.
Rev. 2.00 Mar 09, 2006 page 115 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
* Modes 0 and 1 PLL circuits 1 and 2 operating EXTAL input or crystal resonator used
FR3 0 0 0 0 1 1 1 1 1 FR2 0 1 1 1 0 0 0 1 1 FR1 0 0 0 1 0 0 1 0 1 FR0 0 0 1 0 0 1 0 0 0 x4 x4 x4 x4 x4 x4 x4 x4 x4 I x1 x2 x2 x2 x4 x4 x4 x4 x4 E x1 x1 x2 x2 x1 x2 x2 x4 x4 P x1 x1 x1 x2 x1 x1 x2 x1 x2 CKIO E E E E E E E E E
Note: Do not use combinations other than those shown above. * Modes 0 to 3 PLL circuit 1 halted, PLL circuit 2 operating EXTAL input or crystal resonator used
FR3 0 0 0 1 1 FR2 0 1 1 1 1 FR1 0 0 1 0 1 FR0 0 1 0 0 0 x1 x2 x2 x4 x4 I x1 x2 x2 x4 x4 E x1 x2 x2 x4 x4 P x1 x1 x2 x1 x2 CKIO E E E E E
Note: Do not use combinations other than those shown above.
Rev. 2.00 Mar 09, 2006 page 116 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
* Modes 0 and 1 PLL circuit 1 operating, PLL circuit 2 halted EXTAL input or crystal resonator used
FR3 0 0 1 FR2 0 1 0 FR1 0 0 0 FR0 0 0 0 x4 x4 x4 I x1 x2 x4 E x1 x1 x1 P x1 x1 x1 CKIO E E E
Note: Do not use combinations other than those shown above. * Modes 4 and 5 PLL circuit 1 operating, PLL circuit 2 halted CKIO input
FR3 0 0 1 1 FR2 1 1 0 0 FR1 0 1 0 1 FR0 1 0 1 0 x2 x2 x2 x2 I x1 x1 x2 x2 E x1 x1 x1 x1 P x1/2 x1 x1/2 x1 CKIO E E E E
Note: Do not use combinations other than those shown above.
Rev. 2.00 Mar 09, 2006 page 117 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
* Modes 0-6 PLL circuits 1 and 2 halted EXTAL input or crystal resonator used (modes 0-3) CKIO input (modes 4-6)
FR3 0 0 0 0 1 1 1 1 1 1 FR2 0 1 1 1 0 0 0 1 1 1 FR1 0 0 0 1 0 0 1 0 1 1 FR0 0 0 1 0 0 1 0 0 0 1 x1 x1 x1 x1 x1 x1 x1 x1 x1 x1 I x1/4 x1/2 x1/2 x1/2 x1 x1 x1 x1 x1 x1 E x1/4 x1/4 x1/2 x1/2 x1/4 x1/2 x1/2 x1 x1 x1 P x1/4 x1/4 x1/4 x1/2 x1/4 x1/4 x1/2 x1/4 x1/2 x1 CKIO x1 x1 x1 x1 x1 x1 x1 x1 x1 x1
Note:
Do not use combinations other than those shown above.
Frequency Change: When PLL circuit 1 or PLL circuit 2 becomes operational after modifying the frequency modification register (including modification the frequency modification register in the operating state), access the frequency modification register using the following procedure, and noting the cautions listed below. Frequency change procedure * Set the on-chip watchdog timer (WDT) overflow time to secure the PLL circuit oscillation settling time (CKS2-CKS0 bits in WTCSR). * Clear the WT/IT and TME bit to 0 in WTCSR. * Perform a read anywhere in an external memory area 0-4 cache-through area. * Change the frequency modification register to the target frequency, or change the operating/halted state of the PLL circuits 1 and 2 (the clocks will stop temporarily inside the chip). * The oscillation circuits operate, and the clock is supplied to the WDT. This clock increments the WDT. * On WDT overflow, supply of a clock with the frequency set in frequency setting bits FR3-FR0 begins. In this case, the OVF bit in WTSCR and the WOVF bit in RSTCSR are not set, an interval timer interrupt (ITI) is not requested, and the WDTOVF signal is not asserted.
Rev. 2.00 Mar 09, 2006 page 118 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
Sample code for changing the frequency is shown below.
; ; ; FMR WTCSR .equ .equ h'fffffe90 h'fffffe80 h'fffffe83 SH7616 frequency change
RSTCSR .equ
PACR
.equ
h'fffffc80
XRAM
.equ
h'1000e000
.export _init_FMR
_init_FMR: mov.l mov.l mov.l mov.l #XRAM,r1 r1,r5 #FREQUENCY,r2 #FREQUENCY_END,r3
program_move: mov.w mov.w add add @r2,r0 r0,@r1 #2,r1 #2,r2
cmp/eq r2,r3 bf nop program_move
mov.l mov.w mov.w
#PACR,r1 #h'0008,r0 r0,@r1 Rev. 2.00 Mar 09, 2006 page 119 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
MOV.L MOV.W MOV.L MOV.L
#WTCSR,R1 #H'A51F,R2 #H'26200000,R3 #FMR,R4
jmp nop nop nop nop nop clock4_err: bra nop nop nop nop ; ; ;
@r5
clock4_err
Main portion of frequency change code. First copy this to XRAM and then run it in XRAM. ; ; Clear TME bit. ; Clock input to WTCNT is /16384 ; (Overflow frequency = 262.144 ms) MOV.W R2,@R1
FREQUENCY:
; ; Cache through area of external member space 3: H'26200000 MOV.L @R3,R0
; ; PLL circuit 1 Disabled. ; PLL circuit 1 Enabled. Rev. 2.00 Mar 09, 2006 page 120 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes ; I (x4) = 62.5 MHz, E (x4) = 62.5 MHz, ; P (x2) = 31.25 MHz, CKIO (E) = 62.5 MHz, ; MOV #H'4E,R0
; PLL circuits 1 and 2 Enabled. ; I (x4) = 62.5 MHz, E (x2) = 31.25 MHz, ; P (x2 ) = 31.25 MHz, CKIO (E) = 31.25 MHz, MOV #H'0A,R0
; PLL circuits 1 and 2 Enabled. ; I (x4) = 62.5 MHz, E (x1) = 15.625 MHz, ; P (x1) = 15.625 MHz, CKIO (E) = 15.625 MHz, ; MOV #H'08,R0
MOV.B rts nop
R0,@R4
FREQUENCY_END: NOP
.END
Cautions * The read from the external memory space 0-4 cache-through area and the write to the frequency modification register should be performed in on-chip X/Y memory. After reading from the external memory space 0-4 cache-through area, do not perform any write operations in external memory spaces 0-4 until the write to the frequency modification register. * When the write access to the frequency modification register is executed, the WDT starts automatically. * Do not turn off the CKIO output when PLL circuit 1 is in the operating state. * The CKIO output will be unstable until the PLL circuit stabilizes. * When a frequency is modified, halt the on-chip DMAC (E-DMAC and DMAC) operation before the frequency modification.
Rev. 2.00 Mar 09, 2006 page 121 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
If PLL circuit 1 or PLL circuit 2 does not become operational after modifying the frequency modification register (including modification in the operating state), it means that the above procedure or cautions have not been properly observed. In this case, the WDT will not operate even though the frequency modification register is modified. 3.2.6 Clock Modes and Frequency Ranges
The following table shows the operating modes and the associated frequency ranges for input clocks.
Clock Input Mode Pin 0, 1 Input Frequency Range (MHz) PLL Circuit PLL1 PLL2 On Off On 1-31.25 2 8-15.625 1-31.25 3 8-15.625 1-31.25 4, 5 CKIO 16-31.25 1-31.25 6 1-31.25 On Off Off Off Off On On Off Off On Off On Off Off
23 Internal Clock* *
I E P (MHZ) (MHZ) (MHZ) 8- 62.5 8- 62.5 8- 62.5 8- 62.5 8- 62.5 8- 31.25 8- 31.25
CKIO Output (MHz) 8-62.5 8-62.5
EXTAL or crystal 8-15.625 1 resonator*
8- 8- 8-15.625 15.625 15.625 1-31.25 8-62.5 1-31.25 --
1- 1- 1- 31.25 31.25 31.25 8- 62.5 8- 62.5 8- 31.25
1- 1- 1- 31.25 31.25 31.25 8- 62.5 8- 62.5 8- 31.25
1- 1- 1- 31.25 31.25 31.25 16- 62.5 16- 16- 31.25 31.25 --
1- 1- 1- 31.25 31.25 31.25 1- 1- 1- 31.25 31.25 31.25
Notes: 1. When a crystal resonator is used, set the frequency in the range of 8 to 15.625 MHz. 2. Set the frequency modification register so that the frequency of all internal clocks is 1 MHz or higher. 3. Use internal clock frequencies such that I E P. Rev. 2.00 Mar 09, 2006 page 122 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
3.2.7
Notes on Board Design
When Using an External Crystal Oscillator: Place the crystal resonator, capacitors CL1 and CL2, and damping resistor R close to the EXTAL and XTAL pins. To prevent induction from interfering with correct oscillation, use a common grounding point for the capacitors connected to the resonator, and do not locate a wiring pattern near these components.
Avoid crossing signal lines CL1 CL2
R EXTAL XTAL
Note: The values for CL1, CL2, and the damping resistance should be determined after consultation with the crystal resonator manufacturer.
Figure 3.5 Points for Attention when Using Crystal Resonator Bypass Capacitors: As far as possible, insert a laminated ceramic capacitor of 0.01 to 0.1 F as a bypass capacitor for each VSS/VCC pair. Mount the bypass capacitors as close as possible to the LSI power supply pins, and use components with a frequency characteristic suitable for the LSI operating frequency, as well as a suitable capacitance value. VSS/VCC pairs PLL system: 9-12 3 V digital system: 20-18, 26-22, 35-33, 45-42, 52-50, 60-58, 61-67, 69-66, 78-76, 79-81, 91-89, 101-99, 112-109, 113-110, 114-116, 130-132, 149-146, 150-147 5 V digital system: 157-155, 169-167, 181-179, 191-193, 202-200
Rev. 2.00 Mar 09, 2006 page 123 of 906 REJ09B0292-0200
Section 3 Oscillator Circuits and Operating Modes
When Using a PLL Oscillator Circuit: Keep the wiring short from the PLL VCC and VSS connection pattern to the power supply pins, and make the pattern width large, to minimize the inductance component. Ground the oscillation stabilization capacitors C1 and C2 to VSS (PLL1) and VSS (PLL2), respectively. Place C1 and C2 close to the CAP1 and CAP2 pins and do not locate a wiring pattern in the vicinity.
Avoid crossing signal lines VCC (PLL) CAP1 Reference values C1 = 470 pF C2 = 470 pF VSS VCC
Power supply
CAP2 C2 VSS (PLL)
C1
Figure 3.6 Points for Attention when Using PLL Oscillator Circuit
3.3
Bus Width of the CS0 Area
Pins MD3 and MD4 are used to specify the bus width of the CS0 area. The pin combination and functions are listed in table 3.6. Do not switch the MD4 and MD3 pins while they are operating. Switching them will cause operating errors. Table 3.6 Bus Width of the CS0 Area
Pin MD4 0 0 1 1 MD3 0 1 0 1 Function 8-bit bus width selected 16-bit bus width selected 32-bit bus width selected Setting prohibited
Rev. 2.00 Mar 09, 2006 page 124 of 906 REJ09B0292-0200
Section 4 Exception Handling
Section 4 Exception Handling
4.1
4.1.1
Overview
Types of Exception Handling and Priority Order
Exception handling is initiated by four sources: resets, address errors, interrupts, and instructions (table 4.1). When several exception sources occur simultaneously, they are accepted and processed according to the priority order shown in table 4.1.
Rev. 2.00 Mar 09, 2006 page 125 of 906 REJ09B0292-0200
Section 4 Exception Handling
Table 4.1
Exception Reset Address error Interrupt
Types of Exception Handling and Priority Order
Source Power-on reset Manual reset CPU address error DMA address error (DMAC and E-DMAC) NMI User break User debug interface (H-UDI) External interrupts (IRL1-IRL15, IRQ0-IRQ3 (set with IRL3, IRL2, IRL1, IRL0 pins)) On-chip peripheral modules Direct memory access controller (DMAC) Watchdog timer (WDT) Compare match interrupt (part of the bus state controller) Ethernet controller (EtherC) and Ethernet controller direct memory access controller (E-DMAC) 16-bit free-running timer (FRT) Serial communication interface with FIFO (SCIF) 16-bit timer pulse unit (TPU) Serial I/O with FIFO (SIOF) Serial I/O (SIO) Priority High
Instructions Trap instruction (TRAPA) General illegal instructions (undefined code) Illegal slot instructions (undefined code placed directly following a delayed Low branch instruction*1 or instructions that rewrite the PC*2) Notes: 1. Delayed branch instructions: JMP, JSR, BRA, BSR, RTS, RTE, BF/S, BT/S, BSRF, BRAF 2. Instructions that rewrite the PC: JMP, JSR, BRA, BSR, RTS, RTE, BT, BF, TRAPA, BF/S, BT/S, BSRF, BRAF
Rev. 2.00 Mar 09, 2006 page 126 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.1.2
Exception Handling Operations
Exception handling sources are detected, and exception handling started, according to the timing shown in table 4.2. Table 4.2 Timing of Exception Source Detection and Start of Exception Handling
Timing of Source Detection and Start of Handling Starts when the NMI pin is high and the RES pin changes from low to high Starts when the NMI pin is low and the RES pin changes from low to high Detected when instruction is decoded and starts when the previous executing instruction finishes executing Detected when instruction is decoded and starts when the previous executing instruction finishes executing Trap instruction General illegal instructions Illegal slot instructions Starts from the execution of a TRAPA instruction Starts from the decoding of undefined code anytime except after a delayed branch instruction (delay slot) Starts from the decoding of undefined code placed directly following a delayed branch instruction (delay slot) or of an instruction that rewrites the PC
Exception Source Reset Power-on reset Manual reset Address error Interrupts Instructions
When exception handling starts, the CPU operates as follows: 1. Exception handling triggered by reset The initial values of the program counter (PC) and stack pointer (SP) are fetched from the exception vector table (PC and SP are respectively addresses H'00000000 and H'00000004 for a power-on reset and addresses H'00000008 and H'0000000C addresses for a manual reset). See section 4.1.3, Exception Vector Table, for more information. 0 is then written to the vector base register (VBR) and 1111 is written to the interrupt mask bits (I3-I0) of the status register (SR). The program begins running from the PC address fetched from the exception vector table. 2. Exception handling triggered by address errors, interrupts, and instructions SR and PC are saved to the stack address indicated by R15. For interrupt exception handling, the interrupt priority level is written to the SR's interrupt mask bits (I3-I0). For address error and instruction exception handling, the I3-I0 bits are not affected. The start address is then fetched from the exception vector table and the program begins running from that address.
Rev. 2.00 Mar 09, 2006 page 127 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.1.3
Exception Vector Table
Before exception handling begins, the exception vector table must be written in memory. The exception vector table stores the start addresses of exception service routines. (The reset exception table holds the initial values of PC and SP.) All exception sources are given different vector numbers and vector table address offsets, from which the vector table addresses are calculated. In exception handling, the start address of the exception service routine is fetched from the exception vector table as indicated by the vector table address. Table 4.3 lists the vector numbers and vector table address offsets. Table 4.4 shows vector table address calculations. Table 4.3 (a)Exception Vector Table
Exception Source Power-on reset Manual reset PC SP PC SP General illegal instruction (Reserved by system) Slot illegal instruction (Reserved by system) CPU address error DMA address error (DMAC and E-DMAC) Interrupt NMI User break H-UDI (Reserved by system) Vector Number 0 1 2 3 4 5 6 7 8 9 10*5 11 12 13 14 : 31 Trap instruction (user vector) 32 : 63 Rev. 2.00 Mar 09, 2006 page 128 of 906 REJ09B0292-0200 Vector Table Address Offset H'00000000-H'00000003 H'00000004-H'00000007 H'00000008-H'0000000B H'0000000C-H'0000000F H'00000010-H'00000013 H'00000014-H'00000017 H'00000018-H'0000001B H'0000001C-H'0000001F H'00000020-H'00000023 H'00000024-H'00000027 H'00000028-H'0000002B H'0000002C-H'0000002F H'00000030-H'00000033 H'00000034-H'00000037 H'00000038-H'0000003B : H'0000007C-H'0000007F H'00000080-H'00000083 : H'000000FC-H'000000FF VBR + (vector number x 4) Vector Address Vector number x 4
Section 4 Exception Handling
Table 4.3 (b) Exception Processing Vector Table (IRQ Mode)
Exception Source Interrupt IRQ0 IRQ1 IRQ2 IRQ3 On-chip peripheral 3 module* Vector Number 64* 2 65*
2
Vector Table Address Offset H'00000100-H'00000103 H'00000104-H'00000107 H'00000108-H'0000010B H'0000010C-H'0000010F H'00000000-H'00000003 :
Vector Addresses
66
*2
2 67* 4 0*
: 127 *4
H'000001FC-H'000001FF
Table 4.3 (c) Exception Processing Vector Table (IRL Mode)
Exception Source Interrupt
1 IRL1* 1 IRL2*
Vector Number
2 64* 2 65*
Vector Table Address Offset H'00000100-H'00000103 H'00000104-H'00000107 H'00000108-H'0000010B H'0000010C-H'0000010F H'00000110-H'00000113 H'00000114-H'00000117 H'00000118-H'0000011B H'0000011C-H'0000011F H'00000000-H'00000003 : H'000001FC-H'000001FF
Vector Addresses VBR + (vector number x 4)
IRL3* 1 IRL4*
1
66* 67* 68*
1
2
IRL5
*1
1 2
IRL6* 1 IRL7* IRL8* 1 IRL9*
1
2
IRL10* 1 IRL11* IRL12* 1 IRL13*
1
69* 70* 71* 0*4 :
2
2
IRL14* 1 IRL15*
1
2
On-chip peripheral 3 module*
4 127*
Notes: 1. When 1110 is input to the IRL3, IRL2, IRL1, and IRL0 pins, an IRL1 interrupt results. When 0000 is input, an IRL15 interrupt results.
Rev. 2.00 Mar 09, 2006 page 129 of 906 REJ09B0292-0200
Section 4 Exception Handling 2. External vector number fetches can be performed without using the auto-vector numbers in this table. 3. The vector numbers and vector table address offsets for each on-chip peripheral module interrupt are given table 5.4, Interrupt Exception Vectors and Priorities, in section 5, Interrupt Controller. 4. Vector numbers are set in the on-chip vector number register. See section 5.3, Register Descriptions, in section 5, Interrupt Controller, and section 11, Direct Memory Access Controller, for more information. 5. The same vector number, 10, is generated for a DMAC DMA address error and an EDMAC DMA address error. (See table 4.3 (a).) Both the address error flag (AE) in the DMAC's DMA operation register (DMAOR) and the address error control bit (AEC) in the E-DMAC's E-DMAC operation control register (EDOCR) must therefore be read in the exception service routine to determine which DMA address error has occurred.
Table 4.4
Calculating Exception Vector Table Addresses
Vector Table Address Calculation (Vector table address) = (vector table address offset) = (vector number) x 4 (Vector table address) = VBR + (vector table address offset) = VBR + (vector number) x 4
Exception Source Power-on reset Manual reset Other exception handling
Note: VBR: Vector base register Vector table address offset: See table 4.3. Vector number: See table 4.3.
Rev. 2.00 Mar 09, 2006 page 130 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.2
4.2.1
Resets
Types of Resets
Resets have the highest priority of any exception source. There are two types of resets: manual resets and power-on resets. As table 4.5 shows, both types of resets initialize the internal status of the CPU. In power-on resets, all registers of the on-chip peripheral modules are initialized; in manual resets, registers of all on-chip peripheral modules except the bus state controller (BSC), user break controller (UBC), pin function controller (PFC), and frequency modification register (FMR) are initialized. (Use the power-on reset when turning the power on.) Table 4.5 Types of Resets
Conditions for Transition to Reset Status Type Power-on reset Manual reset NMI Pin High Low RES Pin Low Low CPU Initialized Initialized Internal Status On-Chip Peripheral Modules Initialized Initialized except for BSC, UBC, PFC, and frequency modification register (FMR)
4.2.2
Power-On Reset
When the NMI pin is high and the RES pin is driven low, the device performs a power-on reset. For a reliable reset, the RES pin should be kept low for at least the duration of the oscillation settling time (when the PLL circuit is halted) or for 20tpcyc (when the PLL circuit is running). During a power-on reset, the CPU's internal state and all on-chip peripheral module registers are initialized. See appendix B, Pin States, for the state of individual pins in the power-on reset state. In a power-on reset, power-on reset exception handling starts when the NMI pin is kept high and the RES pin is first driven low for a set period of time and then returned to high. The CPU will then operate as follows: 1. The initial value (execution start address) of the program counter (PC) is fetched from the exception vector table. 2. The initial value of the stack pointer (SP) is fetched from the exception vector table. 3. The vector base register (VBR) is cleared to H'00000000 and the interrupt mask bits (I3-I0) of the status register (SR) are set to H'F (1111). 4. The values fetched from the exception vector table are set in the program counter (PC) and stack pointer (SP), and the program begins executing.
Rev. 2.00 Mar 09, 2006 page 131 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.2.3
Manual Reset
When the NMI pin is low and the RES pin is driven low, the device executes a manual reset. For a reliable reset, the RES pin should be kept low for at least 20 clock cycles. During a manual reset, the CPU's internal state is initialized. All on-chip peripheral module registers are initialized, except for the bus state controller (BSC), user break controller (UBC), and pin function controller (PFC) registers, and the frequency modification register (FMR). When the chip enters the manual reset state in the middle of a bus cycle, manual reset exception handling does not start until the bus cycle has ended. Thus, manual resets do not abort bus cycles. See appendix B, Pin States, for the state of individual pins in the manual reset state. In a manual reset, manual reset exception handling starts when the NMI pin is kept low and the RES pin is first kept low for a set period of time and then returned to high. The CPU will then operate in the same way as for a power-on reset.
4.3
4.3.1
Address Errors
Sources of Address Errors
Address errors occur when instructions are fetched or data read or written, as shown in table 4.6.
Rev. 2.00 Mar 09, 2006 page 132 of 906 REJ09B0292-0200
Section 4 Exception Handling
Table 4.6
Bus Cycles and Address Errors
Bus Master
Bus Cycle Type Bus Cycle Description Instruction fetched from even address Instruction fetched from odd address Instruction fetched from other than on-chip peripheral module space Instruction fetched from on-chip peripheral module space CPU or Data read/write DMAC, E-DMAC Word data accessed from even address Word data accessed from odd address Longword data accessed from a longword boundary Longword data accessed from other than a longword boundary Access of cache purge space, address array read/write space, on-chip peripheral module space, or synchronous DRAM mode setting space by PC-relative addressing Access of cache purge space, address array read/write space, data array read/write space, on-chip peripheral module space, or synchronous DRAM mode setting space by a TAS.B instruction Byte, word, or longword data accessed in on-chip peripheral module space at addresses H'FFFFFC00 to H'FFFFFCFF Longword data accessed in on-chip peripheral module space at addresses H'FFFFFE00 to H'FFFFFEFF Word or byte data accessed in on-chip peripheral module space at addresses H'FFFFFE00 to H'FFFFFEFF Address Errors None (normal) Address error occurs None (normal) Address error occurs None (normal) Address error occurs None (normal) Address error occurs Address error occurs
Instruction CPU fetch
Address error occurs
None (normal)
Address error occurs None (normal)
Byte data accessed in on-chip peripheral module space Address error at addresses H'FFFF0000 to H'FFFFF0FF or occurs H'FFFFFF00 to H'FFFFFFFF Word or longword data accessed in on-chip peripheral module space at addresses H'FFFF0000 to H'FFFFF0FF or H'FFFFFF00 to H'FFFFFFFF None (normal)
Notes: 1. Address errors do not occur during the synchronous DRAM mode register write cycle. 2. 16-byte DMAC transfers use longword accesses. Rev. 2.00 Mar 09, 2006 page 133 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.3.2
Address Error Exception Handling
When an address error occurs, address error exception handling begins after the end of the bus cycle in which the error occurred and completion of the executing instruction. The CPU operates as follows: 1. The status register (SR) is saved to the stack. 2. The program counter (PC) is saved to the stack. The PC value saved is the start address of the instruction to be executed after the last instruction executed . 3. The exception service routine start address is fetched from the exception vector table entry that corresponds to the address error that occurred, and the program starts executing from that address. The jump that occurs is not a delayed branch. Note: The same vector number, 10, is generated for a DMAC DMA address error and an EDMAC DMA address error. (See table 4.3 (a).) Both the address error flag (AE) in the DMAC's DMA operation register (DMAOR) and the address error control bit (AEC) in the E-DMAC's E-DMAC operation control register (EDOCR) must therefore be read in the exception service routine to determine which DMA address error has occurred.
Rev. 2.00 Mar 09, 2006 page 134 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.4
4.4.1
Interrupts
Interrupt Sources
Table 4.7 shows the sources that initiate interrupt exception handling. These are divided into NMI, user breaks, H-UDI, IRL, IRQ, and on-chip peripheral modules. Table 4.7
Type NMI User break H-UDI IRL IRQ On-chip peripheral module
Types of Interrupt Sources
Request Source NMI pin (external input) User break controller (UBC) User debug interface (H-UDI) IRL1-IRL15 (external input) IRQ0-IRQ3 (external input) Direct memory access controller (DMAC) Ethernet controller (EtherC) and Ethernet controller direct memory access controller (E-DMAC) 16-bit free-running timer (FRT) Watchdog timer (WDT) Bus state controller (BSC) Serial I/O with FIFO (SIOF) Serial I/O (SIO) Serial communication interface with FIFO (SCIF) 16-bit timer pulse unit (TPU) Number of Sources 1 1 1 15 4 2 1
3 1 1 4 4 4 13
Each interrupt source is allocated a different vector number and vector table address offset. See table 5.4, Interrupt Exception Vectors and Priority Order, in section 5, Interrupt Controller, for more information.
Rev. 2.00 Mar 09, 2006 page 135 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.4.2
Interrupt Priority Levels
The interrupt priority order is predetermined. When multiple interrupts occur simultaneously, the interrupt controller (INTC) determines their relative priorities and begins exception handling accordingly. The priority order of interrupts is expressed as priority levels 0-16, with priority 0 the lowest and priority 16 the highest. The NMI interrupt has priority 16 and cannot be masked, so it is always accepted. The user break interrupt priority level is 15 and IRL interrupts have priorities of 1-15. On-chip peripheral module interrupt priority levels can be set freely using the INTC's interrupt priority level setting registers A-E (IPRA-IPRE) as shown in table 4.8. The priority levels that can be set are 0-15. Level 16 cannot be set. For more information on IPRA-IPRE, see sections 5.3.1, Interrupt Priority Level Setting Register A (IPRA), to 5.3.5, Interrupt Priority Level Setting Register E (IPRE). Table 4.8
Type NMI User break H-UDI IRL IRQ On-chip peripheral module
Interrupt Priority Order
Priority Level Comment 16 15 15 1-15 0-15 0-15 Fixed priority level. Cannot be masked Fixed priority level Fixed priority level Set with IRL3-IRL0 pins Set with interrupt priority level setting register C (IPRC) Set with interrupt priority level setting registers A, B, D, and E (IPRA, IPRB, IPRD, IPRE)
4.4.3
Interrupt Exception Handling
When an interrupt occurs, its priority level is ascertained by the interrupt controller (INTC). NMI is always accepted, but other interrupts are only accepted if they have a priority level higher than the priority level set in the interrupt mask bits (I3-I0) of the status register (SR). When an interrupt is accepted, exception handling begins. In interrupt exception handling, the CPU saves SR and the program counter (PC) to the stack. The priority level value of the accepted interrupt is written to SR bits I3-I0. For NMI, however, the priority level is 16, but the value set in I3-I0 is H'F (level 15). Next, the start address of the exception service routine is fetched from the exception vector table for the accepted interrupt, that address is jumped to and execution begins. For more information about interrupt exception handling, see section 5.4, Interrupt Operation.
Rev. 2.00 Mar 09, 2006 page 136 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.5
4.5.1
Exceptions Triggered by Instructions
Instruction-Triggered Exception Types
Exception handling can be triggered by a trap instruction, general illegal instruction or illegal slot instruction, as shown in table 4.9. Table 4.9
Type Trap instruction Illegal slot instruction
Types of Exceptions Triggered by Instructions
Source Instruction TRAPA Undefined code placed immediately after a delayed branch instruction (delay slot) and instructions that rewrite the PC Undefined code anywhere besides in a delay slot Comment -- Delayed branch instructions: JMP, JSR, BRA, BSR, RTS, RTE, BF/S, BT/S, BSRF, BRAF Instructions that rewrite the PC: JMP, JSR, BRA, BSR, RTS, RTE, BT, BF, TRAPA, BF/S, BT/S, BSRF, BRAF --
General illegal instruction
4.5.2
Trap Instructions
When a TRAPA instruction is executed, trap instruction exception handling starts. The CPU operates as follows: 1. The status register (SR) is saved to the stack. 2. The program counter (PC) is saved to the stack. The PC value saved is the start address of the instruction to be executed after the TRAPA instruction. 3. The exception service routine start address is fetched from the exception vector table entry that corresponds to the vector number specified by the TRAPA instruction. That address is jumped to and the program starts executing. The jump that occurs is not a delayed branch.
Rev. 2.00 Mar 09, 2006 page 137 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.5.3
Illegal Slot Instructions
An instruction placed immediately after a delayed branch instruction is said to be placed in a delay slot. If the instruction placed in the delay slot is undefined code, illegal slot exception handling begins when the undefined code is decoded. Illegal slot exception handling is also started when an instruction that rewrites the program counter (PC) is placed in a delay slot. The exception handling starts when the instruction is decoded. The CPU handles an illegal slot instruction as follows: 1. The status register (SR) is saved to the stack. 2. The program counter (PC) is saved to the stack. The PC value saved is the jump address of the delayed branch instruction immediately before the undefined code or the instruction that rewrites the PC. 3. The exception service routine start address is fetched from the exception vector table entry that corresponds to the exception that occurred. That address is jumped to and the program starts executing. The jump that occurs is not a delayed branch. 4.5.4 General Illegal Instructions
When undefined code placed anywhere other than immediately after a delayed branch instruction (i.e., in a delay slot) is decoded, general illegal instruction exception handling starts. The CPU handles general illegal instructions in the same way as illegal slot instructions. Unlike processing of illegal slot instructions, however, the program counter value saved is the start address of the undefined code.
Rev. 2.00 Mar 09, 2006 page 138 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.6
When Exception Sources Are Not Accepted
When an address error or interrupt is generated after a delayed branch instruction or interruptdisabled instruction, it is sometimes not immediately accepted but is stored instead, as described in table 4.10. When this happens, it will be accepted when an instruction for which exception acceptance is possible is decoded. Table 4.10 Exception Source Generation Immediately after a Delayed Branch Instruction or Interrupt-Disabled Instruction
Exception Source Point of Occurrence
1 Immediately after a delayed branch instruction* 2 Immediately after an interrupt-disabled instruction*
Address Error Not accepted Accepted
Interrupt Not accepted Not accepted Not accepted
A repeat loop comprising up to three instructions (instruction Not accepted fetch cycle not generated) First instruction or last three instructions in a repeat loop containing four or more instructions Fourth from last instruction in a repeat loop containing four or more instructions Accepted
Not accepted
Notes: 1. Delayed branch instructions: JMP, JSR, BRA, BSR, RTS, RTE, BF/S, BT/S, BSRF, BRAF 2. Interrupt-disabled instructions: LDC, LDC.L, STC, STC.L, LDS, LDS.L, STS, STS.L
4.6.1
Immediately after a Delayed Branch Instruction
When an instruction placed immediately after a delayed branch instruction (delay slot) is decoded, neither address errors nor interrupts are accepted. The delayed branch instruction and the instruction located immediately after it (delay slot) are always executed consecutively, so no exception handling occurs between the two. 4.6.2 Immediately after an Interrupt-Disabled Instruction
When an instruction immediately following an interrupt-disabled instruction is decoded, interrupts are not accepted. Address errors are accepted.
Rev. 2.00 Mar 09, 2006 page 139 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.6.3
Instructions in Repeat Loops
If a repeat loop comprises up to three instructions, neither exceptions nor interrupts are accepted. If a repeat loop contains four or more instructions, neither exceptions nor interrupts are accepted during the execution cycle of the first instruction or the last three instructions. If a repeat loop contains four or more instructions, address errors only are accepted during the execution cycle of the fourth from last instruction. For more information, see the SH-1/SH-2/SH-DSP Software Manual.
A. All interrupts and address errors are accepted. B. Address errors only are accepted. C. No interrupts or address errors are accepted. When RC 1 (1) One instruction instr0 Start (End): instr1 instr2 A B C A (2) Two instructions instr0 Start: instr1 End: instr2 instr3
A B C C A
(4) Four or more instructions A instr0 A or C (on return from instr n) Start:instr1 A : : : A instr n-3 B instr n-2 C instr n-1 C End: instr n C instr n+1 A When RC = 0 All interrupts and address errors are accepted.
(3) Three instructions A instr0 B Start: instr1 C instr2 C End: instr3 C instr4 A
Figure 4.1 Interrupt Acceptance Restrictions in Repeat Mode
Rev. 2.00 Mar 09, 2006 page 140 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.7
Stack Status after Exception Handling
The status of the stack after exception handling ends is as shown in table 4.11. Table 4.11 Stack Status after Exception Handling
Type Address error Trap instruction Stack Status SP Address of instruction after executed instruction SR SP Address of instruction after TRAPA instruction SR General illegal instruction SP Start address of illegal instruction SR Interrupt Illegal slot instruction SP Address of instruction after executed instruction SR SR 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits
SP Jump destination address of delayed branch instruction 32 bits
Rev. 2.00 Mar 09, 2006 page 141 of 906 REJ09B0292-0200
Section 4 Exception Handling
4.8
4.8.1
Usage Notes
Value of Stack Pointer (SP)
The value of the stack pointer must always be a multiple of four, otherwise an address error will occur when the stack is accessed during exception handling. 4.8.2 Value of Vector Base Register (VBR)
The value of the vector base register must always be a multiple of four, otherwise an address error will occur when the vector table is accessed during exception handling. 4.8.3 Address Errors Caused by Stacking of Address Error Exception Handling
If the stack pointer value is not a multiple of four, an address error will occur during stacking of the exception handling (interrupts, etc.). Address error exception handling will begin after the original exception handling ends, but address errors will continue to occur. To ensure that address error exception handling does not go into an endless loop, no address errors are accepted at that point. This allows program control to be shifted to the address error exception service routine and enables error handling to be carried out. When an address error occurs during exception handling stacking, the stacking bus cycle (write) is executed. In stacking of the status register (SR) and program counter (PC), the SP is decremented by 4 for both, so the value of SP will not be a multiple of four after the stacking either. The address value output during stacking is the SP value, so the address where the error occurred is itself output. This means that the write data stacked will be undefined. 4.8.4 Manual Reset during Register Access
Do not initiate a manual reset during access of a bus state controller (BSC), user break controller (UBC), or pin function controller (PFC) register, or the frequency modification register (FMR), otherwise a write error may result.
Rev. 2.00 Mar 09, 2006 page 142 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Section 5 Interrupt Controller (INTC)
5.1 Overview
The interrupt controller (INTC) ascertains the priority order of interrupt sources and controls interrupt requests to the CPU. The INTC has registers for setting the priority of each interrupt which allow the user to set the order of priority in which interrupt requests are handled. 5.1.1 Features
The INTC has the following features: * Sixteen interrupt priority levels can be set By setting the five interrupt priority registers, the priorities of on-chip peripheral module interrupts can be selected at 16 levels for different request sources. * Vector numbers for on-chip peripheral module interrupt can be set By setting the 24 vector number setting registers, the vector numbers of on-chip peripheral module interrupts can be set to values from 0 to 127 for different request sources. * The IRL interrupt vector number setting method can be selected: Either of two modes can be selected by a register setting: auto-vector mode in which vector numbers are determined internally, and external vector mode in which vector numbers are set externally. * IRQ interrupt settings can be made (low level, rising-, falling-, or both-edge detection) 5.1.2 Block Diagram
Figure 5.1 shows a block diagram of the INTC.
Rev. 2.00 Mar 09, 2006 page 143 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
NMI IRL3-IRL0 A3-A0 IVECF D7-D0
Input/ output control Comparator Priority decision logic Interrupt request SR I3 I2 I1 I0
UBC H-UDI DMAC FRT WDT REF SCIF TPU SIO E-DMAC (Including EtherC interrupt) SIOF
(Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request) (Interrupt request)
CPU
ICR IRQCSR
IPR IPRA-IPRE
Module bus
Bus interface
VCRWDT VCRWDT, VCRA-VCRU
Vector number INTC
Internal bus
Peripheral bus
Vector number
DMAC
UBC: H-UDI: DMAC: FRT: WDT: REF: SCIF: TPU: SIO: SIOF:
User break controller User debug interface Direct memory access controller 16-bit free-running timer Watchdog timer Refresh request within bus state controller Serial communication interface with FIFO 16-bit timer pulse unit Serial I/O Serial I/O with FIFO
Ethernet controller direct memory access controller EtherC: Ethernet controller ICR: Interrupt control register IRQCSR: IRQ control/status register IPRA-IPRE: Interrupt priority level setting registers A-E VCRWDT: Vector number setting register WDT VCRA-VCRU: Vector number setting registers A-U SR: Status register
E-DMAC:
Figure 5.1 INTC Block Diagram
Rev. 2.00 Mar 09, 2006 page 144 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.1.3
Pin Configuration
Table 5.1 shows the INTC pin configuration. Table 5.1
Name Nonmaskable interrupt input pin Level request interrupt input pins Interrupt acceptance level output pins External vector fetch pin External vector number input pins
Pin Configuration
Abbreviation NMI IRL3-IRL0 A3-A0 I/O I I O Function Input of nonmaskable interrupt request signal Input of maskable interrupt request signals In external vector mode, output an interrupt level signal when an IRL/IRQ interrupt is accepted Indicates external vector read cycle Input external vector number
IVECF D7-D0
O I
5.1.4
Register Configuration
The INTC has the 31 registers shown in table 5.2. These registers perform various INTC functions including setting interrupt priority, and controlling external interrupt input signal detection. Table 5.2
Name Interrupt priority register setting register A Interrupt priority register setting register B
Register Configuration
Abbr. IPRA IPRB 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 Initial Value H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 Address H'FFFFFEE2 H'FFFFFE60 H'FFFFFEE6 H'FFFFFE40 H'FFFFFE62 H'FFFFFE64 H'FFFFFE66 H'FFFFFE68 H'FFFFFE42 H'FFFFFE44 H'FFFFFE46 Access Size 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16
Interrupt priority register setting register C IPRC Interrupt priority register setting register D IPRD Interrupt priority register setting register E Vector number setting register A Vector number setting register B *3 Vector number setting register C Vector number setting register D Vector number setting register E Vector number setting register F Vector number setting register G IPRE VCRA VCRB VCRC VCRD VCRE VCRF VCRG
H'FFFFFEC0 8, 16
Rev. 2.00 Mar 09, 2006 page 145 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC) Initial Value H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 Access Size 8, 16 8, 16 8, 16 8, 16 8, 16 8, 16
Name Vector number setting register H Vector number setting register I Vector number setting register J Vector number setting register K Vector number setting register L Vector number setting register M Vector number setting register N Vector number setting register O Vector number setting register P Vector number setting register Q Vector number setting register R Vector number setting register S Vector number setting register T Vector number setting register U Vector number setting register WDT Vector number setting register DMA0* 4 Vector number setting register DMA1*
4
Abbr. VCRH VCRI VCRJ VCRK VCRL VCRM VCRN VCRO VCRP VCRQ VCRR VCRS VCRT VCRU VCRWDT
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
Address H'FFFFFE48 H'FFFFFE4A H'FFFFFE4E H'FFFFFE52 H'FFFFFE54 H'FFFFFE56
H'FFFFFE4C 8, 16 H'FFFFFE 50 8, 16
H'FFFFFEC2 8, 16 H'FFFFFEC4 8, 16 H'FFFFFEC6 8, 16 H'FFFFFEC8 8, 16 H'FFFFFECA 8, 16 H'FFFFFECC 8, 16 H'FFFFFEE4 8, 16 32 32 8, 16 8, 16
VCRDMA0 R/W VCRDMA1 R/W ICR IRQCSR R/W R/W
Undefined H'FFFFFFA0 Undefined H'FFFFFFA8 H'8000/ 1 H'0000* 2 * H'FFFFFEE0 H'FFFFFEE8
Interrupt control register IRQ control/status register
Notes: 1. The value when the NMI pin is high is H'8000; when the NMI pin is low, it is H'0000. 2. When pins IRL3-IRL0 are high, bits 7-4 in IRQCSR are set to 1. When pins IRL3-IRL0 are low, bits 7-4 in IRQCSR are cleared to 0. The initial value of bits other than 7-4 is 0. 3. In the SH7616, VCRB is a reserved register and must not be accessed. 4. See section 11, Direct Memory Access Controlle for more information on VCRDMA0, and VCRDMA1.
5.2
Interrupt Sources
There are five types of interrupt sources: NMI, user breaks, H-UDI, IRL/IRQ and on-chip peripheral modules. Each interrupt has a priority expressed as a priority level (0 to 16, with 0 the lowest and 16 the highest). Giving an interrupt a priority level of 0 masks it.
Rev. 2.00 Mar 09, 2006 page 146 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.2.1
NMI Interrupt
The NMI interrupt has priority 16 and is always accepted. Input at the NMI pin is detected by edge. Use the NMI edge select bit (NMIE) in the interrupt control register (ICR) to select either the rising or falling edge. NMI interrupt exception handling sets the interrupt mask level bits (I3- I0) in the status register (SR) to level 15. 5.2.2 User Break Interrupt
A user break interrupt has priority level 15 and occurs when the break condition set in the user break controller (UBC) is satisfied. User break interrupt exception handling sets the interrupt mask level bits (I3-I0) in the status register (SR) to level 15. For more information about the user break interrupt, see section 6, User Break Controller. 5.2.3 H-UDI Interrupt
The H-UDI interrupt has a priority level of 15, and is generated when an H-UDI interrupt instruction is serially input. H-UDI interrupt exception processing sets the interrupt mask bits (I3- I0) in the status register (SR) to level 15. See section 18, User Debug Interface, for details of the H-UDI interrupt. 5.2.4 IRL Interrupts
IRL interrupts are requested by input from pins IRL3-IRL0. Fifteen interrupts, IRL15-IRL1, can be input externally via pins IRL3-IRL0. The priority levels of interrupts IRL15-IRL0 are 15-1, respectively, and their vector numbers are 71-64. Set the vector numbers with the interrupt vector mode select (VECMD) bit of the interrupt control register (ICR) to enable external input. External input of vector numbers consists of vector numbers 0-127 from the external vector input pins (D7-D0). When an external vector is used, 0 is input to D7. Internal vectors are called autovectors and vectors input externally are called external vectors. Table 5.3 lists IRL priority levels and auto vector numbers. When an IRL interrupt is accepted in external vector mode, the IRL interrupt level is output from the interrupt acceptance level output pins (A3-A0). The external vector fetch pin (IVECF) is also asserted. The external vector number is read from pins D7-D0 at this time. IRL interrupt exception processing sets the interrupt mask level bits (I3 to I0) in the status register (SR) to the priority level value of the IRL interrupt that was accepted.
Rev. 2.00 Mar 09, 2006 page 147 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.2.5
IRQ Interrupts
An IRQ interrupt is requested when the external interrupt vector mode select bit (EXIMD) of the interrupt control register (ICR) is set to 1. An IRQ interrupt corresponds to input at one of pins IRL3-IRL0. Low-level sensing or rising/falling/both-edge sensing can be selected independently for each pin by the IRQ sense select bits (IRQ31S-IRQ00S) in the IRQ control/status register (IRQCSR), and a priority level of 0 to 15 can be selected independently for each pin by means of interrupt priority register C (IPRC). Set the interrupt vector mode select bit (VECMD) of the interrupt control register (ICR) to enable external input of vector numbers. External vector numbers are 0 to 127, and are input to the external vector input pins (D7-D0) during the interrupt vector fetch bus cycle. When an external vector is used, 0 is input to D7. When an IRQ interrupt is accepted in external vector mode, the IRQ interrupt priority level is output from the interrupt acceptance level output pins (A3-A0). The external vector fetch signal (IVECF) is also asserted. The external vector number is read from signals D7-D0 at this time. IRQ interrupt exception processing sets the interrupt mask bits (I3-I0) in the status register (SR) to the priority level value of the IRQ interrupt that was accepted. Table 5.3
IRL3 0
IRL Interrupt Priority Levels and Auto-Vector Numbers
Pin IRL2 0 IRL1 0 1 1 0 1 IRL0 0 1 0 1 0 1 0 1 0 1 1 1 0 1 0 1 0 1 0 Priority Level 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 64 65 66 67 68 69 70 Vector Number 71
1
0
0
Rev. 2.00 Mar 09, 2006 page 148 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
An example of connections for external vector mode interrupts is shown in figure 5.2, and an example of connections for auto-vector mode interrupts in figure 5.3.
Chip
Interrupt requests
Priority encoder
4 IRL0-IRL3 IRL0-IRL3
Vector number generator circuit D0-D7
A0-A3 IVECF RD D0-D7
Figure 5.2 Example of Connections for External Vector Mode Interrupts
Chip
Interrupt requests
Priority encoder
4 IRL0-IRL3 IRL0-IRL3
Figure 5.3 Example of Connections for Auto-Vector Mode Interrupts Figures 5.4 to 5.7 show the interrupt vector fetch cycle for the external vector mode. During this cycle, CS0-CS4 stay high. A24-A4 output undefined values. The WAIT pin is sampled, but programmable waits are not valid.
Rev. 2.00 Mar 09, 2006 page 149 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
T1 CKIO CS0-CS4 BS A3-A0 IVECF RD/WR RD D7-D0 Vector number input Accepted interrupt level High T2 T3 T4
Figure 5.4 External Vector Fetch (I : E = 1 : 1)
T1 CKIO CS0-CS4 BS A3-A0 IVECF RD/WR RD D7-D0 Vector number input Accepted interrupt level High T2
Figure 5.5 External Vector Fetch (I : E 1 : 1)
Rev. 2.00 Mar 09, 2006 page 150 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
T1 CKIO CS0-CS4 BS A3-A0 IVECF RD/WR RD D7-D0 WAIT Vector number input Accepted interrupt level High
T2 T3 Tw T4
Figure 5.6 External Vector Fetch (I : E = 1 : 1 (WAIT Input)) WAIT
T1 CKIO CS0-CS4 BS A3-A0 IVECF RD/WR RD D7-D0 WAIT Vector number input Accepted interrupt level High Tw T2
Figure 5.7 External Vector Fetch (I : E 1 : 1 (WAIT Input)) WAIT
Rev. 2.00 Mar 09, 2006 page 151 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.2.6
On-chip Peripheral Module Interrupts
On-chip peripheral module interrupts are interrupts generated by the following 9 on-chip peripheral modules: * Direct memory access controller (DMAC) * Bus state controller (BSC) * Watchdog timer (WDT) * 16-bit free-running timer (FRT) * Ethernet controller direct memory access controller (E-DMAC) (Including EtherC interrupt) * 16-bit timer pulse unit (TPU) * Serial communication interface with FIFO (SCIF) * Serial I/O with FIFO (SIOF) * Serial I/O (SIO) A different interrupt vector is assigned to each interrupt source, so the exception service routine does not have to decide which interrupt has occurred. Priority levels between 0 and 15 can be assigned to individual on-chip peripheral modules in interrupt priority registers A, B, D, and E (IPRA, IPRB, IPRD, IPRE). On-chip peripheral module interrupt exception handling sets the interrupt mask level bits (I3-I0) in the status register (SR) to the priority level value of the on-chip peripheral module interrupt that was accepted. 5.2.7 Interrupt Exception Vectors and Priority Order
Table 5.4 lists interrupt sources and their vector numbers, vector table address offsets and interrupt priorities. Each interrupt source is allocated a different vector number and vector table address offset. Vector table addresses are calculated from vector numbers and vector table address offsets. In interrupt exception handling, the exception service routine start address is fetched from the vector table entry indicated by the vector table address. See table 4.4, Calculating Exception Vector Table Addresses, in section 4, Exception Handling, for more information on this calculation. IRL interrupts IRL15-IRL1 have interrupt priority levels of 15-1, respectively. IRQ interrupt and on-chip peripheral module interrupt priorities can be set freely between 0 and 15 for each module by setting interrupt priority registers A-E (IPRA-IPRE). The ranking of interrupt sources for IPRA-IPRE, however, must be the order listed under Priority within IPR Setting Unit in table 5.4 and cannot be changed. A reset assigns priority level 0 to on-chip peripheral module interrupts. If the same priority level is assigned to two or more interrupt sources and interrupts from those
Rev. 2.00 Mar 09, 2006 page 152 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
sources occur simultaneously, their priority order is the default priority order indicated at the right in table 5.4. Table 5.4 (a) Interrupt Exception Vectors and Priority Order (IRL Mode)
Vectors Vector Vector Table No. Address 11 12 13 71*
1
Interrupt Source NMI User break H-UDI 4 IRL15* IRL14* 4 IRL13*
4 4 IRL12* 4 IRL11*
Interrupt Priority Order (Initial IPR (Bit Value) Numbers) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Priority within IPR Setting VCR (Bit Unit Numbers) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- High Low -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- VCRDMA0 (6-0)
Default Priority High
VBR + 16 (vector No. 15 x 4) 15 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
1 70*
1 69*
IRL10* 4 IRL9* IRL8 *4
4 IRL7* 4 IRL6*
4
68
*1
1 67*
IRL5* 4 IRL4*
4
66* 65
1
IRL3
*4
*1
4 IRL2* 4 IRL1* 1 64* 2 Transfer 0-127* end
DMAC0
15-0 (0) IPRA (11-8)
DMAC1
2 Transfer 0-127* end
15-0 (0)
High Low
VCRDMA1 (6-0) Low
Rev. 2.00 Mar 09, 2006 page 153 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC) Interrupt Priority Order (Initial IPR (Bit Value) Numbers) Priority within IPR Setting VCR (Bit Unit Numbers) High Low
3 REF*
Interrupt Source WDT ITI
Vectors Vector Vector Table No. Address 0-127*
2
Default Priority High
VBR + 15-0 (0) IPRA (vector No. (7-4) x 4)
VCRWDT (14-8)
CMI
2 0-127*
15-0 (0)
High Low
VCRWDT (6-0)
6 E-DMAC EINT*
2 0-127*
15-0 (0) IPRB (15-12)
High Low
VCRA (14-8) VCRB (14- 5 0)* VCRC (14-8) VCRC (6-0) VCRD (14-8) VCRE (14-8) VCRE (6-0) VCRF (14-8) VCRF (6-0) VCRG (14-8) VCRH (14-8) VCRH (6-0) VCRI (14-8) VCRI (6-0) VCRJ (14-8) VCRJ (6-0) VCRK (14-8) VCRK (6-0) Low
Reserved
FRT
ICI OCI OVI
2 0-127*
0-127* 2 0-127*
2 2 0-127* 2 0-127*
15-0 (0) IPRB (11-8)
High Low
TPU0
TGI0A TGI0B TGI0C TGI0D TCI0V
15-0 (0) IPRD (15-12)
High Low
0-127* 2 0-127*
2
0-127
*2 15-0 (0) IPRD (11-8)
TPU1
TGI1A TGI1B TCI1V TCI1U
2 0-127* 2 0-127* 2 0-127*
High Low
TPU2
TGI2A TGI2B TCI2V TCI2U
0-127* 2 0-127*
2 2 0-127* 2 0-127* 2 0-127*
15-0 (0) IPRD (7-4)
High Low
Rev. 2.00 Mar 09, 2006 page 154 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC) Interrupt Priority Order (Initial IPR (Bit Value) Numbers) 15-0 (0) IPRD (3-0) Priority within IPR Setting VCR (Bit Unit Numbers) High Low 15-0 (0) IPRE (15-12) High Low 15-0 (0) IPRE (11-8) High Low 15-0 (0) IPRE (7-4) High Low 15-0 (0) IPRE (3-0) High Low -- -- -- VCRL (14-8) VCRL (6-0) VCRM (14-8) VCRM (6-0) VCRN (14-8) VCRN (6-0) VCRO (14-8) VCRO (6-0) VCRP (14-8) VCRP (6-0) VCRQ (14-8) VCRQ (6-0) VCRR (14-8) VCRR (6-0) VCRS (14-8) VCRS (6-0) VCRT (14-8) VCRT (6-0) VCRU (14-8) VCRU (6-0) -- Low
Interrupt Source SCIF1 ERI1 RXI1 BRI1 TXI1 SCIF2 ERI2 RXI2 BRI2 TXI2 SIOF RERI0 TERI0 RDFI0 TDEI0 SIO1 RERI1 TERI1 RDFI1 TDEI1 SIO2 RERI2 TERI2 RDFI2 TDEI2 Reserved
Vectors Vector Vector Table No. Address 0-127*
2
Default Priority High
VBR +
2 0-127* (vector No. 2 0-127* x 4)
0-127* 2 0-127*
2 2 0-127* 2 0-127* 2 0-127*
0-127* 2 0-127*
2 2 0-127* 2 0-127* 2 0-127*
0-127* 2 0-127*
2 2 0-127* 2 0-127* 2 0-127*
0-127* 2 0-127*
2
128-255 --
Notes: 1. An external vector number fetch can be performed without using the auto-vector numbers shown in this table. The external vector numbers are 0-127. 2. Vector numbers are set in the on-chip vector number register. 3. REF is the refresh control unit within the bus state controller. 4. Set to IRL1-IRL15 or IRQ0-IRQ3 by the EXIMD bit in ICR. 5. In the SH7616, VCRB is a reserved register and must not be accessed. 6. The E-DMAC interrupt (EINT) is the OR of those of the 19 interrupt sources in the EtherC/E-DMAC status register (EESR) that are enabled by the EtherC/E-DMAC status interrupt permission register (EESIPR). As the three status bits in the EtherC status register (ECSR) can be copied into the ECI bit in EESR as an interrupt source, EINT is input to the INTC as the OR of a maximum of 22 interrupt sources.
Rev. 2.00 Mar 09, 2006 page 155 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Table 5.4 (b) Interrupt Exception Vectors and Priority Order (IRQ Mode)
Vectors Vector Vector Table No. Address 11 12 13 64* 65* 66* 67*
1
Interrupt Source NMI User break H-UDI 4 IRQ0* IRQ1* IRQ2* IRQ3*
4
Interrupt Priority Order (Initial IPR (Bit Value) Numbers) -- -- -- IPRC (15-12) IPRC (11-8) IPRC (7-4) IPRC (3-0) IPRA (11-8)
Priority within IPR Setting VCR (Bit Unit Numbers) -- -- -- -- -- -- -- High Low -- -- -- -- -- -- -- VCRDMA0 (6-0)
Default Priority High
VBR + 16 (vector No. 15 x 4) 15 15-0 (0) 15-0 (0) 15-0 (0) 15-0 (0)
2
1
4
1
4
1
DMAC0
Transfer 0-127* end
15-0 (0)
DMAC1
2 Transfer 0-127* end
15-0 (0)
High Low
VCRDMA1 (6-0)
WDT
ITI
2 0-127*
15-0 (0)
IPRA (7-4)
High Low
VCRWDT (14-8)
3 REF*
CMI
2 0-127*
15-0 (0)
High Low
VCRWDT (6-0) Low
Rev. 2.00 Mar 09, 2006 page 156 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC) Interrupt Priority Order (Initial IPR (Bit Value) Numbers) IPRB (15-12) Priority within IPR Setting VCR (Bit Unit Numbers) High Low FRT ICI OCIA/B OVI TPU0 TGI0A TGI0B TGI0C TGI0D TCI0V TPU1 TGI1A TGI1B TCI1V TCI1U TPU2 TGI2A TGI2B TCI2V TCI2U SCIF1 ERI1 RXI1 BRI1 TXI1 SCIF2 ERI2 RXI2 BRI2 TXI2
2 0-127* 2 0-127*
Interrupt Source E-DMAC EINT* Reserved
6
Vectors Vector Vector Table No. Address 0-127*
2
Default Priority
VBR + 15-0 (0) (vector No. x 4)
VCRA (14-8) High VCRB 5 (14-0)* VCRC (14-8) VCRC (6-0) VCRD (14-8) VCRE (14-8) VCRE (6-0) VCRF (14-8) VCRF (6-0) VCRG (14-8) VCRH (14-8) VCRH (6-0) VCRI (14-8) VCRI (6-0) VCRJ (14-8) VCRJ (6-0) VCRK (14-8) VCRK (6-0) VCRL (14-8) VCRL (6-0) VCRM (14- 8) VCRM (6-0) VCRN (14-8) VCRN (6-0) VCRO (14-8) VCRO (6-0) Low
15-0 (0)
IPRB (11-8)
High Low
0-127*
2
2 0-127* 2 0-127* 2 0-127*
15-0 (0)
IPRD (15-12)
High Low
0-127* 2 0-127*
2
0-127
*2
15-0 (0)
2 0-127* 2 0-127*
IPRD (11-8)
High Low
0-127* 2 0-127*
2
15-0 (0)
0-127
*2
IPRD (7-4)
High Low
2 0-127* 2 0-127* 2 0-127*
15-0 (0)
0-127* 2 0-127*
2
IPRD (3-0)
High Low
0-127* 2 0-127*
2
15-0 (0)
0-127* 2 0-127*
2 2 0-127*
IPRE (15-12)
High Low
Rev. 2.00 Mar 09, 2006 page 157 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC) Interrupt Priority Order (Initial IPR (Bit Value) Numbers) IPRE (11-8) Priority within IPR Setting VCR (Bit Unit Numbers) High Low 15-0 (0) IPRE (7-4) High Low 15-0 (0) IPRE (3-0) High Low -- -- -- VCRP (6-0) VCRQ (14-8) VCRQ (6-0) VCRR (14-8) VCRR (6-0) VCRS (14-8) VCRS (6-0) VCRT (14-8) VCRT (6-0) VCRU (14-8) VCRU (6-0) -- Low
Interrupt Source SIOF RERI0 TERI0 RDFI0 TDEI0 SIO1 RERI1 TERI1 RDFI1 TDEI1 SIO2 RERI2 TERI2 RDFI2 TDEI2 Reserved
Vectors Vector Vector Table No. Address
2
Default Priority
0-127* VBR + 15-0 (0) 2 0-127* (vector No. 2 0-127* x 4) 0-127 *2
2 0-127* 2 0-127* 2 0-127*
VCRP (14-8) High
0-127* 2 0-127*
2 2 0-127* 2 0-127* 2 0-127*
128-255 --
Notes: 1. An external vector number fetch can be performed without using the auto-vector numbers shown in this table. The external vector numbers are 0-127. 2. Vector numbers are set in the on-chip vector number register. 3. REF is the refresh control unit within the bus state controller. 4. Set to IRL1-IRL15 or IRQ0-IRQ3 by the EXIMD bit in ICR. 5. In the SH7616, VCRB is a reserved register and must not be accessed. 6. The E-DMAC interrupt (EINT) is the OR of those of the 19 interrupt sources in the EtherC/E-DMAC status register (EESR) that are enabled by the EtherC/E-DMAC status interrupt permission register (EESIPR). As the three status bits in the EtherC status register (ECSR) can be copied into the ECI bit in EESR as an interrupt source, EINT is input to the INTC as the OR of a maximum of 22 interrupt sources.
Rev. 2.00 Mar 09, 2006 page 158 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3
5.3.1
Register Descriptions
Interrupt Priority Level Setting Register A (IPRA)
Interrupt priority level setting register A (IPRA) is a 16-bit read/write register that assigns priority levels from 0 to 15 to on-chip peripheral module interrupts. IPRA is initialized to H'0000 by a reset. It is not initialized in standby mode. Unless otherwise specified, `reset' refers to both poweron and manual resets throughout this manual.
Bit: 15 -- Initial value: R/W: Bit: 0 R 7 WDT IP3 Initial value: R/W: 0 R/W 14 -- 0 R 6 WDT IP2 0 R/W 13 -- 0 R 5 WDT IP1 0 R/W 12 -- 0 R 4 WDT IP0 0 R/W 11 DMAC IP3 0 R/W 3 -- 0 R 10 DMAC IP2 0 R/W 2 -- 0 R 9 DMAC IP1 0 R/W 1 -- 0 R 8 DMAC IP0 0 R/W 0 -- 0 R
Bits 15 to 12--Reserved: These bits are always read as 0. The write value should always be 0. Bits 11 to 8--Direct Memory Access Controller (DMAC) Interrupt Priority Level 3 to 0 (DMACIP3-DMACIP0): These bits set the direct memory access controller (DMAC) interrupt priority level. There are four bits, so levels 0-15 can be set. The same level is set for both two DMAC channels. When interrupts occur simultaneously, channel 0 has priority. Bits 7 to 4--Watchdog Timer (WDT) Interrupt Priority Level 3 to 0 (WDTIP3-WDTIP0): These bits set the watchdog timer (WDT) interrupt priority level and bus state controller (BSC) interrupt priority level. There are four bits, so levels 0-15 can be set. When WDT and BSC interrupts occur simultaneously, the WDT interrupt has priority. Bits 3 to 0--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 159 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.2
Interrupt Priority Level Setting Register B (IPRB)
Interrupt priority level setting register B (IPRB) is a 16-bit read/write register that assigns priority levels from 0 to 15 to on-chip peripheral module interrupts. IPRB is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: 15 14 13 12 11 FRTIP3 0 R/W 3 -- 0 R 10 FRTIP2 0 R/W 2 -- 0 R 9 FRTIP1 0 R/W 1 -- 0 R 8 FRTIP0 0 R/W 0 -- 0 R
E-DMAC E-DMAC E-DMAC E-DMAC IP3 IP2 IP1 IP0 Initial value: R/W: Bit: Initial value: R/W: 0 R/W 7 -- 0 R 0 R/W 6 -- 0 R 0 R/W 5 -- 0 R 0 R/W 4 -- 0 R
Bits 15 to 12--Ethernet Controller Direct Memory Access Controller (E-DMAC) Interrupt Priority Level 3 to 0 (E-DMACIP3-E-DMACIP0): These bits set the ethernet controller direct memory access controller (E-DMAC) interrupt priority level. There are four bits, so levels 0-15 can be set. Bits 11 to 8--16-Bit Free-Running Timer (FRT) Interrupt Priority Level 3 to 0 (FRTIP3- FRTIP0): These bits set the 16-bit free-running timer (FRT) interrupt priority level. There are four bits, so levels 0-15 can be set. Bits 7 to 0--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 160 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.3
Interrupt Priority Level Setting Register C (IPRC)
Interrupt priority level setting register C (IPRC) is a 16-bit read/write register that sets the priority levels (0-15) of IRQ0-IRQ3 interrupts. IPRC is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
IRQ0IP3 IRQ0IP2 IRQ0IP1 IRQ0IP0 IRQ1IP3 IRQ1IP2 IRQ1IP1 IRQ1IP0
IRQ2IP3 IRQ2IP2 IRQ2IP1 IRQ2IP0 IRQ3IP3 IRQ3IP2 IRQ3IP1 IRQ3IP0
Bits 15 to 0-IRQ0 to IRQ3 Priority Level 3 to 0 (IRQnIP3-IRQnIP0, n = 0-3): These bits set the IRQ0-IRQ3 priority levels. There are four bits for each interrupt, so the value can be set between 0 and 15.
Rev. 2.00 Mar 09, 2006 page 161 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.4
Interrupt Priority Level Setting Register D (IPRD)
Interrupt priority level setting register D (IPRD) is a 16-bit read/write register that sets the priority levels (0-15) of on-chip peripheral module interrupts. IPRD is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TPU0IP3 TPU0IP2 TPU0IP1 TPU0IP0 TPU1IP3 TPU1IP2 TPU1IP1 TPU1IP0
TPU2IP3 TPU2IP2 TPU2IP1 TPU2IP0 SCF1IP3 SCF1IP2 SCF1IP1 SCF1IP0
Bits 15 to 4--16-Bit Timer Pulse Unit 0 to 2 (TPU0-TPU2) Interrupt Priority Level 3 to 0 (TPUnIP3-TPUnIP0, n = 0-2): These bits set the 16-bit timer pulse unit 0 to 2 (TPU0-TPU2) interrupt priority levels. There are four bits for each interrupt, so the value can be set between 0 and 15. Bits 3 to 0--Serial Communication Interface with FIFO 1 (SCIF1) Interrupt Priority Level 3 to 0 (SCF1IP3-SCF1IP0): These bits set the serial communication interface with FIFO 1 (SCIF1) interrupt priority level. There are four bits, so the value can be set between 0 and 15.
Rev. 2.00 Mar 09, 2006 page 162 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.5
Interrupt Priority Level Setting Register E (IPRE)
Interrupt priority level setting register E (IPRE) is a 16-bit read/write register that sets the priority levels (0-15) of on-chip peripheral module interrupts. IPRE is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
SCF2IP3 SCF2IP2 SCF2IP1 SCF2IP0 SIOFIP3 SIOFIP2 SIOFIP1 SIOFIP0
SIO1IP3 SIO1IP2 SIO1IP1 SIO1IP0 SIO2IP3 SIO2IP2 SIO2IP1 SIO2IP0
Bits 15 to 12--Serial Communication Interface with FIFO 2 (SCIF2) Interrupt Priority Level 3 to 0 (SCF2IP3-SCF2IP0): These bits set the serial communication interface with FIFO 2 (SCIF2) interrupt priority levels. There are four bits, so the value can be set between 0 and 15. Bits 11 to 8--Serial I/O with FIFO (SIOF) Interrupt Priority Level 3 to 0 (SIOFIP3(SIOFIP0): These bits set the serial I/O with FIFO (SIOF) interrupt priority levels. There are four bits, so the value can be set between 0 and 15. Bits 7 to 0--Serial I/O 1 to 2 (SIO1-SIO2) Interrupt Priority Level 3 to 0 (SIOnIP3-SIOnIP0, n = 0-2): These bits set the serial I/O 0 to 2 (SIO0-SIO2) interrupt priority levels. There are four bits for each interrupt, so the value can be set between 0 and 15. Table 5.5 shows the relationship between on-chip peripheral module interrupts and interrupt priority level setting registers.
Rev. 2.00 Mar 09, 2006 page 163 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Table 5.5
Register
Interrupt Request Sources and IPRA-IPRE
Bits 15 to 12 Reserved E-DMAC IRQ0 TPU0 SCIF2 Bits 11 to 8 DMAC0, DMAC1 FRT IRQ1 TPU1 SIOF Bits 7 to 4 WDT, REF Reserved IRQ2 TPU2 SIO1 Bits 3 to 0 Reserved Reserved IRQ3 SCIF1 SIO2
Interrupt priority level setting register A Interrupt priority level setting register B Interrupt priority level setting register C Interrupt priority level setting register D Interrupt priority level setting register E
As table 5.5 shows, between two and four on-chip peripheral modules are assigned to each interrupt priority level setting register. Set the priority levels by setting the corresponding 4-bit groups with values in the range of H'0 (0000) to H'F (1111). H'0 is interrupt priority level 0 (the lowest); H'F is level 15 (the highest). When two on-chip peripheral modules are assigned to the same bits (DMAC0 and DMAC1, or WDT and BSC refresh control unit), those two modules have the same priority. A reset initializes IPRA-IPRE to H'0000. They are not initialized in standby mode. 5.3.6 Vector Number Setting Register WDT (VCRWDT)
Vector number setting register WDT (VCRWDT) is a 16-bit read/write register that sets the WDT interval interrupt and BSC compare match interrupt vector numbers (0-127). VCRWDT is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 WITV6 0 R/W 6 0 R/W 13 WITV5 0 R/W 5 0 R/W 12 WITV4 0 R/W 4 0 R/W 11 WITV3 0 R/W 3 0 R/W 10 WITV2 0 R/W 2 0 R/W 9 WITV1 0 R/W 1 0 R/W 8 WITV0 0 R/W 0 0 R/W
BCMV6 BCMV5 BCMV4 BCMV3 BCMV2 BCMV1 BCMV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 164 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Bits 14 to 8--Watchdog Timer (WDT) Interval Interrupt Vector Number 6 to 0 (WITV6- WITV0): These bits set the vector number for the interval interrupt (ITI) of the watchdog timer (WDT). There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Bus State Controller (BSC) Compare Match Interrupt Vector Number 6 to 0 (BCMV6-BCMV0): These bits set the vector number for the compare match interrupt (CMI) of the bus state controller (BSC). There are seven bits, so the value can be set between 0 and 127. 5.3.7 Vector Number Setting Register A (VCRA)
Vector number setting register A (VCRA) is a 16-bit read/write register that sets the E-DMAC interrupt vector numbers (0-127). VCRA is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 EINV6 0 R/W 6 -- 0 R 13 EINV5 0 R/W 5 -- 0 R 12 EINV4 0 R/W 4 -- 0 R 11 EINV3 0 R/W 3 -- 0 R 10 EINV2 0 R/W 2 -- 0 R 9 EINV1 0 R/W 1 -- 0 R 8 EINV0 0 R/W 0 -- 0 R
Bits 15 and 7 to 0--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Ethernet Controller Direct Memory Access Controller (E-DMAC) Interrupt Vector Number 6 to 0 (EINV6-EINV0): These bits set the vector number for ethernet controller direct memory access controller (E-DMAC) interrupt (EINT). There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 165 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.8
Vector Number Setting Register B (VCRB)
Vector number setting register B (VCRB) is a 16-bit reserved register. Access to this register is prohibited. VCRB is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 -- 0 R 6 -- 0 R 13 -- 0 R 5 -- 0 R 12 -- 0 R 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 -- 0 R
5.3.9
Vector Number Setting Register C (VCRC)
Vector number setting register C (VCRC) is a 16-bit read/write register that sets the 16-bit freerunning timer (FRT) input-capture interrupt and output-compare interrupt vector numbers (0-127). VCRC is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 FICV6 0 R/W 6 FOCV6 0 R/W 13 FICV5 0 R/W 5 FOCV5 0 R/W 12 FICV4 0 R/W 4 FOCV4 0 R/W 11 FICV3 0 R/W 3 FOCV3 0 R/W 10 FICV2 0 R/W 2 FOCV2 0 R/W 9 FICV1 0 R/W 1 FOCV1 0 R/W 8 FICV0 0 R/W 0 FOCV0 0 R/W
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Free-Running Timer (FRT) Input-Capture Interrupt Vector Number 6 to 0 (FICV6-FICV0): These bits set the vector number for the 16-bit free-running timer (FRT) inputcapture interrupt (ICI). There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 166 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Bits 6 to 0--16-Bit Free-Running Timer (FRT) Output-Compare Interrupt Vector Number 6 to 0 (FOCV6-FOCV0): These bits set the vector number for the 16-bit free-running timer (FRT) output-compare interrupt (OCI). There are seven bits, so the value can be set between 0 and 127. 5.3.10 Vector Number Setting Register D (VCRD)
Vector number setting register D (VCRD) is a 16-bit read/write register that sets the 16-bit freerunning timer (FRT) overflow interrupt vector number (0-127). VCRD is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 FOVV6 0 R/W 6 -- 0 R 13 FOVV5 0 R/W 5 -- 0 R 12 FOVV4 0 R/W 4 -- 0 R 11 FOVV3 0 R/W 3 -- 0 R 10 FOVV2 0 R/W 2 -- 0 R 9 FOVV1 0 R/W 1 -- 0 R 8 FOVV0 0 R/W 0 -- 0 R
Bits 15 and 7 to 0--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Free-Running Timer (FRT) Overflow Interrupt Vector Number 6 to 0 (FOVV6-FOVV0): These bits set the vector number for the 16-bit free-running timer (FRT) overflow interrupt (OVI). There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 167 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.11
Vector Number Setting Register E (VCRE)
Vector number setting register E (VCRE) is a 16-bit read/write register that sets the 16-bit timer pulse unit 0 (TPU0) TGR0A and TGR0B input capture/compare match interrupt vector numbers (0-127). VCRE is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TG0AV6 TG0AV5 TG0AV4 TG0AV3 TG0AV2 TG0AV1 TG0AV0
TG0BV6 TG0BV5 TG0BV4 TG0BV3 TG0BV2 TG0BV1 TG0BV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 0 (TPU0) TGR0A Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG0AV6-TG0AV0): These bits set the vector number for the 16-bit timer pulse unit 0 (TPU0) TGR0A input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--16-Bit Timer pulse unit 0 (TPU0) TGR0B Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG0BV6-TG0BV0): These bits set the vector number for the 16-bit timer pulse unit 0 (TPU0) TGR0B input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 168 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.12
Vector Number Setting Register F (VCRF)
Vector number setting register F (VCRF) is a 16-bit read/write register that sets the 16-bit timer pulse unit 0 (TPU0) TGR0C and TGR0D input capture/compare match interrupt vector numbers (0-127). VCRF is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TG0CV6 TG0CV5 TG0CV4 TG0CV3 TG0CV2 TG0CV1 TG0CV0
TG0DV6 TG0DV5 TG0DV4 TG0DV3 TG0DV2 TG0DV1 TG0DV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 0 (TPU0) TGR0C Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG0CV6-TG0CV0): These bits set the vector number for the 16-bit timer pulse unit 0 (TPU0) TGR0C input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--16-Bit Timer pulse unit 0 (TPU0) TGR0D Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG0DV6-TG0DV0): These bits set the vector number for the 16-bit timer pulse unit 0 (TPU0) TGR0D input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 169 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.13
Vector Number Setting Register G (VCRG)
Vector number setting register G (VCRG) is a 16-bit read/write register that sets the 16-bit timer pulse unit 0 (TPU0) TCNT0 overflow interrupt vector number (0-127). VCRG is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 -- 0 R 13 0 R/W 5 -- 0 R 12 0 R/W 4 -- 0 R 11 0 R/W 3 -- 0 R 10 0 R/W 2 -- 0 R 9 0 R/W 1 -- 0 R 8 0 R/W 0 -- 0 R
TC0VV6 TC0VV5 TC0VV4 TC0VV3 TC0VV2 TC0VV1 TC0VV0
Bits 15 and 7 to 0--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 0 (TPU0) TCNT0 Overflow Interrupt Vector Number 6 to 0 (TC0VV6-TV0VV0): These bits set the vector number for the 16-bit timer pulse unit 0 (TPU0) TCNT0 overflow interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 170 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.14
Vector Number Setting Register H (VCRH)
Vector number setting register H (VCRH) is a 16-bit read/write register that sets the 16-bit timer pulse unit 1 (TPU1) TGR1A and TGR1B input capture/compare match interrupt vector numbers (0-127). VCRH is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TG1AV6 TG1AV5 TG1AV4 TG1AV3 TG1AV2 TG1AV1 TG1AV0
TG1BV6 TG1BV5 TG1BV4 TG1BV3 TG1BV2 TG1BV1 TG1BV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 1 (TPU1) TGR1A Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG1AV6-TG1AV0): These bits set the vector number for the 16-bit timer pulse unit 1 (TPU1) TGR1A input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--16-Bit Timer pulse unit 1 (TPU1) TGR1B Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG1BV6-TG1BV0): These bits set the vector number for the 16-bit timer pulse unit 1 (TPU1) TGR1B input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 171 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.15
Vector Number Setting Register I (VCRI)
Vector number setting register I (VCRI) is a 16-bit read/write register that sets the 16-bit timer pulse unit 1 (TPU1) TCNT1 overflow/underflow interrupt vector numbers (0-127). VCRI is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TC1VV6 TC1VV5 TC1VV4 TC1VV3 TC1VV2 TC1VV1 TC1VV0
TC1UV6 TC1UV5 TC1UV4 TC1UV3 TC1UV2 TC1UV1 TC1UV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 1 (TPU1) TCNT1 Overflow Interrupt Vector Number 6 to 0 (TC1VV6-TC1VV0): These bits set the vector number for the 16-bit timer pulse unit 1 (TPU1) TCNT1 overflow interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--16-Bit Timer pulse unit 1 (TPU1) TCNT1 Underflow Interrupt Vector Number 6 to 0 (TC1UV6-TC1UV0): These bits set the vector number for the 16-bit timer pulse unit 1 (TPU1) TCNT1 underflow interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 172 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.16
Vector Number Setting Register J (VCRJ)
Vector number setting register J (VCRJ) is a 16-bit read/write register that sets the 16-bit timer pulse unit 2 (TPU2) TGR2A and TGR2B input capture/compare match interrupt vector numbers (0-127). VCRJ is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TG2AV6 TG2AV5 TG2AV4 TG2AV3 TG2AV2 TG2AV1 TG2AV0
TG2BV6 TG2BV5 TG2BV4 TG2BV3 TG2BV2 TG2BV1 TG2BV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 2 (TPU2) TGR2A Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG2AV6-TG2AV0): These bits set the vector number for the 16-bit timer pulse unit 2 (TPU2) TGR2A input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--16-Bit Timer pulse unit 2 (TPU2) TGR2B Input Capture/Compare Match Interrupt Vector Number 6 to 0 (TG2BV6-TG2BV0): These bits set the vector number for the 16-bit timer pulse unit 2 (TPU2) TGR2B input capture/compare match interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 173 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.17
Vector Number Setting Register K (VCRK)
Vector number setting register K (VCRK) is a 16-bit read/write register that sets the 16-bit timer pulse unit 2 (TPU2) TCNT2 overflow/underflow interrupt vector numbers (0-127). VCRK is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
TC2VV6 TC2VV5 TC2VV4 TC2VV3 TC2VV2 TC2VV1 TC2VV0
TC2UV6 TC2UV5 TC2UV4 TC2UV3 TC2UV2 TC2UV1 TC2UV0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--16-Bit Timer pulse unit 2 (TPU2) TCNT2 Overflow Interrupt Vector Number 6 to 0 (TC2VV6-TC2VV0): These bits set the vector number for the 16-bit timer pulse unit 2 (TPU2) TCNT2 overflow interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--16-Bit Timer pulse unit 2 (TPU2) TCNT2 Underflow Interrupt Vector Number 6 to 0 (TC2UV6-TC2UV0): These bits set the vector number for the 16-bit timer pulse unit 2 (TPU2) TCNT2 underflow interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 174 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.18
Vector Number Setting Register L (VCRL)
Vector number setting register L (VCRL) is a 16-bit read/write register that sets the serial communication interface with FIFO 1 (SCIF1) receive-error interrupt and receive-data-full/dataready interrupt vector numbers (0-127). VCRL is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
SER1V6 SER1V5 SER1V4 SER1V3 SER1V2 SER1V1 SER1V0
SRX1V6 SRX1V5 SRX1V4 SRX1V3 SRX1V2 SRX1V1 SRX1V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial Communication Interface with FIFO 1 (SCIF1) Receive-Error Interrupt Vector Number 6 to 0 (SER1V6-SER1V0): These bits set the vector number for the serial communication interface with FIFO 1 (SCIF1) receive-error interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial Communication Interface with FIFO 1 (SCIF1) Receive-Data-Full/Data-Ready Interrupt Vector Number 6 to 0 (SRX1V6-SRX1V0): These bits set the vector number for the serial communication interface with FIFO 1 (SCIF1) receive-data-full/data-ready interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 175 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.19
Vector Number Setting Register M (VCRM)
Vector number setting register M (VCRM) is a 16-bit read/write register that sets the serial communication interface with FIFO 1 (SCIF1) break interrupt and transmit-data-empty interrupt vector numbers (0-127). VCRM is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
SBR1V6 SBR1V5 SBR1V4 SBR1V3 SBR1V2 SBR1V1 SBR1V0
STX1V6 STX1V5 STX1V4 STX1V3 STX1V2 STX1V1 STX1V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial Communication Interface with FIFO 1 (SCIF1) Break Interrupt Vector Number 6 to 0 (SBR1V6-SBR1V0): These bits set the vector number for the serial communication interface with FIFO 1 (SCIF1) break interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial Communication Interface with FIFO 1 (SCIF1) Transmit-Data-Empty Interrupt Vector Number 6 to 0 (STE1V6-STE1V0): These bits set the vector number for the serial communication interface with FIFO 1 (SCIF1) transmit-data-empty interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 176 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.20
Vector Number Setting Register N (VCRN)
Vector number setting register N (VCRN) is a 16-bit read/write register that sets the serial communication interface with FIFO 2 (SCIF2) receive-error interrupt and receive-data-full/dataready interrupt vector numbers (0-127). VCRN is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
SER2V6 SER2V5 SER2V4 SER2V3 SER2V2 SER2V1 SER2V0
SRX2V6 SRX2V5 SRX2V4 SRX2V3 SRX2V2 SRX2V1 SRX2V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial Communication Interface with FIFO 2 (SCIF2) Receive-Error Interrupt Vector Number 6 to 0 (SER2V6-SER2V0): These bits set the vector number for the serial communication interface with FIFO 2 (SCIF2) receive-error interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial Communication Interface with FIFO 2 (SCIF2) Receive-Data-Full/Data-Ready Interrupt Vector Number 6 to 0 (SRX2V6-SRX2V0): These bits set the vector number for the serial communication interface with FIFO 2 (SCIF2) receive-data-full/data-ready interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 177 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.21
Vector Number Setting Register O (VCRO)
Vector number setting register O (VCRO) is a 16-bit read/write register that sets the serial communication interface with FIFO 2 (SCIF2) break interrupt and transmit-data-empty interrupt vector numbers (0-127). VCRO is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
SBR2V6 SBR2V5 SBR2V4 SBR2V3 SBR2V2 SBR2V1 SBR2V0
STX2V6 STX2V5 STX2V4 STX2V3 STX2V2 STX2V1 STX2V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial Communication Interface with FIFO 2 (SCIF2) Break Interrupt Vector Number 6 to 0 (SBR2V6-SBR2V0): These bits set the vector number for the serial communication interface with FIFO 2 (SCIF2) break interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial Communication Interface with FIFO 2 (SCIF2) Transmit-Data-Empty Interrupt Vector Number 6 to 0 (STE2V6-STE2V0): These bits set the vector number for the serial communication interface with FIFO 2 (SCIF2) transmit-data-empty interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 178 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.22
Vector Number Setting Register P (VCRP)
Vector number setting register P (VCRP) is a 16-bit read/write register that sets the serial I/O with FIFO (SIOF) receive overrun error interrupt and transmit underrun error interrupt vector numbers (0-127). VCRP is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
RER0V6 RER0V5 RER0V4 RER0V3 RER0V2 RER0V1 RER0V0
TER0V6 TER0V5 TER0V4 TER0V3 TER0V2 TER0V1 TER0V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial I/O with FIFO (SIOF) Receive Overrun Error Interrupt Vector Number 6 to 0 (RER0V6-RER0V0): These bits set the vector number for the serial I/O with FIFO (SIOF) receive overrun error interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial I/O with FIFO (SIOF) Transmit Underrun Error Interrupt Vector Number 6 to 0 (TER0V6-TER0V0): These bits set the vector number for the serial I/O with FIFO (SIOF) transmit underrun error interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 179 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.23
Vector Number Setting Register Q (VCRQ)
Vector number setting register Q (VCRQ) is a 16-bit read/write register that sets the serial I/O with FIFO (SIOF) receive-data-full interrupt and transmit-data-empty interrupt vector numbers (0- 127). VCRQ is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
RDF0V6 RDF0V5 RDF0V4 RDF0V3 RDF0V2 RDF0V1 RDF0V0
TDE0V6 TDE0V5 TDE0V4 TDE0V3 TDE0V2 TDE0V1 TDE0V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial I/O with FIFO (SIOF) Receive-Data-Full Interrupt Vector Number 6 to 0 (RDF0V6-RDF0V0): These bits set the vector number for the serial I/O with FIFO (SIOF) receive-data-full interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial I/O with FIFO (SIOF) Transmit-Data-Empty Interrupt Vector Number 6 to 0 (TDE0V6-TDE0V0): These bits set the vector number for the serial I/O with FIFO (SIOF) transmit-data-empty interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 180 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.24
Vector Number Setting Register R (VCRR)
Vector number setting register R (VCRR) is a 16-bit read/write register that sets the serial I/O 1 (SIO1) receive overrun error interrupt and transmit underrun error interrupt vector numbers (0- 127). VCRR is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
RER1V6 RER1V5 RER1V4 RER1V3 RER1V2 RER1V1 RER1V0
TER1V6 TER1V5 TER1V4 TER1V3 TER1V2 TER1V1 TER1V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial I/O 1 (SIO1) Receive Overrun Error Interrupt Vector Number 6 to 0 (RER1V6-RER1V0): These bits set the vector number for the serial I/O 1 (SIO1) receive overrun error interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial I/O 1 (SIO1) Transmit Underrun Error Interrupt Vector Number 6 to 0 (TER1V6-TER1V0): These bits set the vector number for the serial I/O 1 (SIO1) transmit underrun error interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 181 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.25
Vector Number Setting Register S (VCRS)
Vector number setting register S (VCRS) is a 16-bit read/write register that sets the serial I/O 1 (SIO1) receive-data-full interrupt and transmit-data-empty interrupt vector numbers (0-127). VCRS is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
RDF1V6 RDF1V5 RDF1V4 RDF1V3 RDF1V2 RDF1V1 RDF1V0
TDE1V6 TDE1V5 TDE1V4 TDE1V3 TDE1V2 TDE1V1 TDE1V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial I/O 1 (SIO1) Receive-Data-Full Interrupt Vector Number 6 to 0 (RDF1V6- RDF1V0): These bits set the vector number for the serial I/O 1 (SIO1) receive-data-full interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial I/O 1 (SIO1) Transmit-Data-Empty Interrupt Vector Number 6 to 0 (TDE1V6- TDE1V0): These bits set the vector number for the serial I/O 1 (SIO1) transmit-data-empty interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 182 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.26
Vector Number Setting Register T (VCRT)
Vector number setting register T (VCRT) is a 16-bit read/write register that sets the serial I/O 2 (SIO2) receive overrun error interrupt and transmit underrun error interrupt vector numbers (0- 127). VCRT is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
RER2V6 RER2V5 RER2V4 RER2V3 RER2V2 RER2V1 RER2V0
TER2V6 TER2V5 TER2V4 TER2V3 TER2V2 TER2V1 TER2V0
Bits 15 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial I/O 2 (SIO2) Receive Overrun Error Interrupt Vector Number 6 to 0 (RER2V6-RER2V0): These bits set the vector number for the serial I/O 2 (SIO2) receive overrun error interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial I/O 2 (SIO2) Transmit Underrun Error Interrupt Vector Number 6 to 0 (TER2V6-TER2V0): These bits set the vector number for the serial I/O 2 (SIO2) transmit underrun error interrupt. There are seven bits, so the value can be set between 0 and 127.
Rev. 2.00 Mar 09, 2006 page 183 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.27
Vector Number Setting Register U (VCRU)
Vector number setting register U (VCRU) is a 16-bit read/write register that sets the serial I/O 2 (SIO2) receive-data-full interrupt and transmit-data-empty interrupt vector numbers (0-127). VCRU is initialized to H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
RDF2V6 RDF2V5 RDF2V4 RDF2V3 RDF2V2 RDF2V1 RDF2V0
TDE2V6 TDE2V5 TDE2V4 TDE2V3 TDE2V2 TDE2V1 TDE2V0
Bits 15 and 7--Reserved. These bits are always read as 0. The write value should always be 0. Bits 14 to 8--Serial I/O 2 (SIO2) Receive-Data-Full Interrupt Vector Number 6 to 0 (RDF2V6- RDF2V0): These bits set the vector number for the serial I/O 2 (SIO2) receive-data-full interrupt. There are seven bits, so the value can be set between 0 and 127. Bits 6 to 0--Serial I/O 2 (SIO2) Transmit-Data-Empty Interrupt Vector Number 6 to 0 (TDE2V6- TDE2V0): These bits set the vector number for the serial I/O 2 (SIO2) transmit-data-empty interrupt. There are seven bits, so the value can be set between 0 and 127. Tables 5.6 and 5.7 show the relationship between on-chip peripheral module interrupts and interrupt vector number setting registers.
Rev. 2.00 Mar 09, 2006 page 184 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Table 5.6
Interrupt Request Sources and Vector Number Setting Registers (1)
Bits
Register Vector number setting register WDT Vector number setting register A Vector number setting register B Vector number setting register C Vector number setting register D Vector number setting register E Vector number setting register F Vector number setting register G Vector number setting register H Vector number setting register I Vector number setting register J Vector number setting register K Vector number setting register L Vector number setting register M Vector number setting register N Vector number setting register O Vector number setting register P Vector number setting register Q
14-8 Interval interrupt (WDT) E-DMAC interrupt (E-DMAC) Reserved Input-capture interrupt (FRT) Overflow interrupt (FRT) Input capture/compare match interrupt (TPU0/TGR0A) Input capture/compare match interrupt (TPU0/TGR0C) Overflow interrupt (TPU0/TCNT0) Input capture/compare match interrupt (TPU1/TGR1A) Overflow interrupt (TPU1/TCNT1) Input capture/compare match interrupt (TPU2/TGR2A) Overflow interrupt (TPU2/TCNT2)
6-0 Compare-match interrupt (BSC) Reserved Reserved Output-compare interrupt (FRT) Reserved Input capture/compare match interrupt (TPU0/TGR0B) Input capture/compare match interrupt (TPU0/TGR0D) Reserved Input capture/compare match interrupt (TPU1/TGR1B) Underflow interrupt (TPU1/TCNT1) Input capture/compare match interrupt (TPU2/TGR2B) Underflow interrupt (TPU2/TCNT2)
Receive-error interrupt (SCIF1) Receive-data-full/data-ready interrupt (SCIF1) Break interrupt (SCIF1) Transmit-data-empty interrupt (SCIF1)
Receive-error interrupt (SCIF2) Receive-data-full/data-ready interrupt (SCIF2) Break interrupt (SCIF2) Transmit-data-empty interrupt (SCIF2)
Receive overrun error interrupt Transmit underrun error (SIOF) interrupt (SIOF) Receive-data-full interrupt (SIOF) Transmit-data-empty interrupt (SIOF)
Rev. 2.00 Mar 09, 2006 page 185 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC) Bits Register Vector number setting register R Vector number setting register S Vector number setting register T Vector number setting register U 14-8 6-0 Receive overrun error interrupt Transmit underrun error (SIO1) interrupt (SIO1) Receive-data-full interrupt (SIO1) Transmit-data-empty interrupt (SIO1)
Receive overrun error interrupt Transmit underrun error (SIO2) interrupt (SIO2) Receive-data-full interrupt (SIO2) Transmit-data-empty interrupt (SIO2)
As table 5.6 shows, two on-chip peripheral module interrupts are assigned to each register. Set the vector numbers by setting the corresponding 7-bit groups (bits 14 to 8 and bits 6 to 0) with values in the range of H'00 (0000000) to H'7F (1111111). H'00 is vector number 0 (the lowest); H'7F is vector number 127 (the highest). The vector table address is calculated by the following equation.
Vector table address = VBR + (vector number x 4)
A reset initializes a vector number setting register to H'0000. They are not initialized in standby mode. Table 5.7
Register Vector number setting register DMA0 (VCRDMA0) Vector number setting register DMA1 (VCRDMA1)
Interrupt Request Sources and Vector Number Setting Registers (2)
Setting Function Channel 0 transfer end interrupt for DMAC Channel 1 transfer end interrupt for DMAC
As shown in table 5.7 the vector numbers for direct memory access controller transfer-end interrupts are set in VCRDMA0 and VCRDMA1. See sections 11, Direct Memory Access Controller, for more details.
Rev. 2.00 Mar 09, 2006 page 186 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.3.28
Interrupt Control Register (ICR)
ICR is a 16-bit register that sets the input signal detection mode of external interrupt input pin NMI and indicates the input signal level at the NMI pin. It can also specify IRQ or IRL mode by means of the External Interrupt Vector Mode Select bit. The IRQ/IRL interrupt vector number can be selected for setting in accordance with either auto vector mode or external vector mode by means of the Interrupt Vector Mode Select bit. ICR is initialized to H'8000 or H'0000 by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 NMIL 0/1* R 7 -- 0 R 14 -- 0 R 6 -- 0 R 13 -- 0 R 5 -- 0 R 12 -- 0 R 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 EXIMD 0 R/W 8 NMIE 0 R/W 0 VECMD 0 R/W
Note: * When NMI input is high: 1; when NMI input is low: 0
Bit 15--NMI Input Level (NMIL): Sets the level of the signal input at the NMI pin. This bit can be read to determine the NMI pin level. This bit cannot be modified.
Bit 15: NMIL 0 1 Description NMI input level is low NMI input level is high
Bits 14 to 9--Reserved: These bits are always read as 0. The write value should always be 0. Bit 8--NMI Edge Select (NMIE): Selects whether the falling or rising edge of the interrupt request signal to the NMI pin is detected.
Bit 8: NMIE 0 1 Description Interrupt request is detected on falling edge of NMI input (Initial value) Interrupt request is detected on rising edge of NMI input
Bits 7 to 2--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 187 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Bit 1--External Interrupt Vector Mode Select (EXIMD): This bit selects IRQ mode or IRL mode. In IRQ mode, each of signals IRL3 to IRL0 functions as a separate interrupt source. In IRL mode, these signals can specify interrupt priority levels 1 to 15.
Bit 1: EXIMD 0 1 Description IRL mode IRQ mode (Initial value)
Bit 0--Interrupt Vector Mode Select (VECMD): This bit selects auto-vector mode or external vector mode for IRL/IRQ interrupt vector number setting. In auto-vector mode, an internally determined vector number is set. The IRL15 and IRL14 interrupt vector numbers are set to 71 and the IRL1 vector number is set to 64. In external vector mode, a value between 0 and 127 can be input as the vector number from the external vector number input pins (D7-D0).
Bit 0: VECMD 0 1 Description Auto vector mode, vector number automatically set internally (Initial value) External vector mode, vector number set by external input
5.3.29
IRQ Control/Status Register (IRQCSR)
The IRQ control/status register (IRQCSR) is a 16-bit register that sets the IRL0-IRL3 input signal detection mode, indicates the input signal levels at pins IRL0-IRL3, and also indicates the IRQ interrupt status. IRQCSR is initialized by a reset. It is not initialized in standby mode.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0/1 R 14 0 R/W 6 0/1 R 13 0 R/W 5 0/1 R 12 0 R/W 4 0/1 R 11 0 R/W 3 IRQ3F 0 R/(W)* 10 0 R/W 2 IRQ2F 0 R/(W)* 9 0 R/W 1 IRQ1F 0 R/(W)* 8 0 R/W 0 IRQ0F 0 R/(W)*
IRQ31S IRQ30S IRQ21S IRQ20S IRQ11S IRQ10S IRQ01S IRQ00S
IRL3PS IRL2PS IRL1PS IRL0PS
Note: * Only 0 can be written, to clear the flag (in case of edge detection).
Rev. 2.00 Mar 09, 2006 page 188 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Bits 15 to 8--IRQ Sense Select Bits (IRQ31S-IRQ00S): These bits set the IRQ detection mode for IRL3-IRL0.
Bit 15-8: IRQn1S 0 1 Note: n = 0 to 3 Bit 15-8: IRQn0S 0 1 0 1 Description Low-level detection Rising-edge detection Falling-edge detection Both-edge detection (Initial value)
Bits 7 to 4--IRL Pin Status Bits (IRL3PS-IRL0PS): These bits indicate the IRL3-IRL0 pin status. The IRL3-IRL0 pin levels can be ascertained by reading these bits. These bits cannot be modified.
Bit 7-4: IRLnPS 0 1 Note: n = 0 to 3 Description Low level is being input to pin IRLn High level is being input to pin IRLn
Bits 3 to 0--IRQ3 to IRQ0 Flags (IRQ3F-IRQ0F): These bits indicate the IRQ3-IRQ0 interrupt request status.
Bit 3-0: IRQ3F-IRQ0F 0 Detection Setting Level detection Description There is no IRQn interrupt request [Clearing condition] When IRLn input is high Edge detection An IRQn interrupt request has not been detected (Initial value) [Clearing conditions] * When 0 is written to IRQnF after reading IRQnF = 1 * When an IRQn interrupt is accepted 1 Level detection There is an IRQn interrupt request [Setting condition] When IRLn input is low Edge detection An IRQn interrupt request has been detected [Setting condition] When an IRLn input edge is detected Note: n = 0 to 3 Rev. 2.00 Mar 09, 2006 page 189 of 906 REJ09B0292-0200 (Initial value)
Section 5 Interrupt Controller (INTC)
5.4
5.4.1
Interrupt Operation
Interrupt Sequence
The sequence of operations in interrupt generation is described below and illustrated in figure 5.8. 1. The interrupt request sources send interrupt request signals to the interrupt controller. 2. The interrupt controller selects the highest-priority interrupt among the interrupt requests sent, according to the priority levels set in interrupt priority level setting registers A to E (IPRA- IPRE). Lower-priority interrupts are held pending. If two or more of these interrupts have the same priority level or if multiple interrupts occur within a single module, the interrupt with the highest default priority or the highest priority within its IPR setting unit (as indicated in table 5.4) is selected. 3. The interrupt controller compares the priority level of the selected interrupt request with the interrupt mask bits (I3-I0) in the CPU's status register (SR). If the request priority level is equal to or less than the level set in I3-I0, the request is held pending. If the request priority level is higher than the level in bits I3-I0, the interrupt controller accepts the interrupt and sends an interrupt request signal to the CPU. 4. The CPU detects the interrupt request sent from the interrupt controller when it decodes the next instruction to be executed. Instead of executing the decoded instruction, the CPU starts interrupt exception handling. 5. Status register (SR) and program counter (PC) are saved onto the stack. 6. The priority level of the accepted interrupt is copied to the interrupt mask level bits (I3 to I0) in the status register (SR). 7. When external vector mode is specified for the IRL/IRQ interrupt, the vector number is read from the external vector number input pins (D7-D0). 8. The CPU reads the start address of the exception service routine from the exception vector table entry for the accepted interrupt, jumps to that address, and starts executing the program there. This jump is not a delayed branch.
Rev. 2.00 Mar 09, 2006 page 190 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Program execution state
Interrupt generated? Yes NMI? Yes
No
No
User break?
No
Yes
H-UDI interrupt?
No
Yes
Level 15 interrupt? Yes
No
Yes Save SR to stack Save PC to stack Copy accepted interrupt level to I3-I0 Read vector number* Read exception vector table Branch to exception service routine
Level 14 interrupt? Yes I3 to I0 level 13? No Yes
No No
I3 to I0 level 14? No Yes
Level 1 interrupt? Yes I3 to I0 = level 0? No
I3-I0: Status register interrupt mask bits. Note: * The vector number is only read from an external source when an external vector number is specified for the IRL/IRQ interrupt vector number.
Figure 5.8 Interrupt Sequence Flowchart
Rev. 2.00 Mar 09, 2006 page 191 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.4.2
Stack State after Interrupt Exception Handling
The state of the stack after interrupt exception handling is completed is shown in figure 5.9.
Address 4n-8 4n-4 4n PC SR 32 bits 32 bits SP
PC: Start address of return destination instruction (instruction after executing instruction)
Figure 5.9 Stack State after Interrupt Exception Handling
5.5
Interrupt Response Time
Table 5.8 shows the interrupt response time, which is the time from the occurrence of an interrupt request until interrupt exception handling starts and fetching of the first instruction of the interrupt service routine begins.
Rev. 2.00 Mar 09, 2006 page 192 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Table 5.8
Interrupt Response Time
Number of States Peripheral Module
Item Compare identified interrupt priority with SR mask level Wait for completion of sequence currently being executed by CPU
NMI 2.0 x Icyc
IRL/IRQ 0.5 x Icyc + 1.0 x Ecyc + 1.5 x Pcyc X ( 0)
A 0.5 x Icyc + 1.0 x Pcyc X ( 0)
B 1.0 x Pcyc
Notes
X ( 0)
X ( 0)
The longest sequence is for interrupt or addresserror exception handling (X = 4.0 x Icyc + m1 + m2 + m3 + m4). If an interrupt-making instruction follows, however, the time may be even longer during repeat instruction execution
5.0 x Icyc Time from interrupt + m1 + m2 exception handling (SR + m3 and PC saves and vector address fetch) until fetch of first instruction of exception service routine starts Response time
5.0 x Icyc + m1 + m2 + m3
5.0 x Icyc + m1 + m2 + m3
5.0 x Icyc + m1 + m2 + m3
Total: X + 7.0 x Icyc X + 5.5 x Icyc + m1 + m2 + 1.0 x Ecyc + m3 + 1.5 x Pcyc + m1 + m2 + m3 Minimum: 10 Maximum: 11 + 2 (m1 + m2 + m3) + m4 11 19.5 + 2 (m1 + m2 + m3) + m4
X + 5.5 x Icyc + 1.0 x Pcyc + m1 + m2 + m3 9.5 13.5 + 2 (m1 + m2 + m3) + m4
X + 5.0 x Icyc + 1.0 x Pcyc + m1 + m2 + m3 9 13.0 + 2 (m1 + m2 + m3) + m4 I:E:P = 1:1:1 I:E:P = 1:1/4:1/4
Notes: m1-m4 are the number of states needed for the following memory accesses m1: SR save (longword write) m2: PC save (longword write) m3: Vector address read (longword read) m4: Fetch of first instruction of interrupt service routine Icyc: I cycle time Ecyc: E cycle time Pcyc: P cycle time Peripheral modules A: DMAC, REF (BSC) Peripheral modules B: WDT, FRT, TPU, SCIF, SIOF, SIO, E-DMAC Rev. 2.00 Mar 09, 2006 page 193 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.6
Sampling of Pins IRL3 IRL0 IRL3-IRL0
Signals on interrupt pins IRL3 to IRL0 pass through the noise canceler before being sent by the interrupt controller to the CPU as interrupt requests, as shown in figure 5.10. The noise canceler cancels noise that changes in short cycles. The CPU samples the interrupt requests between executing instructions. During this period, the noise canceler output changes according to the noise-eliminated pin level, so the pin level must be held until the CPU samples it. This means that interrupt sources generally must not be cleared inside interrupt routines. When an external vector is fetched, the interrupt source can also be cleared when the external vector fetch cycle is detected.
Interrupt request Noise canceler Interrupt controller Interrupt accepted CPU
IRL0 IRL1 IRL2 IRL3
IRL3-IRL0 pin level 1111
1011 for 1 clock due to noise 1111
Level 2 interrupt 1101
Level 6 interrupt 1001
Noise canceler output 1111
Cleared when interrupt is accepted 1101
1001
Interrupt request to CPU
Interrupt acceptance signal from CPU
Figure 5.10 IRL3 IRL0 Pin Sampling IRL3-IRL0
Rev. 2.00 Mar 09, 2006 page 194 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
5.7
Usage Notes
1. Note on module standby execution Do not execute module standby for modules that have the module standby function when the possibility remains that an interrupt request may be output. 2. Notes on interrupt source clearing A. When clearing external interrupt source If interrupt source clearing is performed by writing to an IO address (external), the next instruction will be executed before completion of the write operation because of the write buffer. To ensure that the write operation is completed before the next instruction is executed, synchronization is achieved when a read is performed from the same address following the write. a. When returning from interrupt handling by means of RTE instruction When the RTE instruction is used to return from interrupt handling, as shown in figure 5.11, consider the cycles to be inserted between the read instruction for synchronization and the RTE instruction, according to the set clock ratio (I : E : P) and external bus cycle. IRL3--IRL0 should be negated at least 0.5 Icyc + 1.0 Ecyc + 1.5 Pcyc before next interrupt acceptance becomes possible. For example, if clock ratio I : E : P is 4 : 2 : 2, at least 5.5 Icyc should be inserted. b. When changing level during interrupt handling When the SR value is changed by means of an LDC instruction and multiple implementation of other interrupts is enabled, also, consider the cycles to be inserted between the synchronization instruction and the LDC instruction as shown in figure 5.12, according to the set clock ratio (I : E : P) and external bus cycle. IRL3-IRL0 should be negated at least 0.5 Icyc + 1.0 Ecyc + 1.5 Pcyc before next interrupt acceptance becomes possible. For example, if clock ratio I : E : P is 4 : 2 : 2, at least 5.5 Icyc should be inserted.
Rev. 2.00 Mar 09, 2006 page 195 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Write completed Interrupt clear instruction Synchronization instruction RTE instruction Delay slot instruction Interrupt return destination instruction D E D M E D M E Next interrupt can be accepted
External write cycle W M External read cycle M D F E D E
0.5Icyc + 1.0Ecyc + 1.5Pcyc IRL3-IRL0 F: Instruction fetch ............... Instruction is fetched from memory in which program is stored D: Instruction decode ........... Fetched instruction is decoded E: Instruction execution ........ Data operation or address operation is performed in accordance with result of decoding M: Memory access ................ Memory data access is performed W: Write-back ....................... Data read from memory is written to register
Figure 5.11 Pipeline Operation when Returning by Means of RTE Instruction
Write completed Interrupt clear instruction Synchronization instruction
* * *
Next interrupt can be accepted
D
E D
M E M
External write cycle W External read cycle
LDC instruction Interrupt disable instruction Normal instruction
D
E D E D E
0.5Icyc + 1.0Ecyc + 1.5Pcyc IRL3-IRL0
Figure 5.12 Pipeline Operation when Interrupts are Enabled by Means of SR Modification When an interrupt source is cleared by the program, pipeline operation must be considered to ensure that the same interrupt is not implemented again.
Rev. 2.00 Mar 09, 2006 page 196 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
B. When clearing on-chip interrupt source When an interrupt source is from an on-chip peripheral module, also, pipeline operation must be considered to ensure that the same interrupt is not implemented again. An interval of 0.5 Icyc + 1.0 Pcyc is required until an on-chip peripheral module interrupt is identified by the CPU. Similarly, an interval of 0.5 Icyc + 1.0 Pcyc is also necessary to report the fact that an interrupt request is no longer present. a. When returning from interrupt handling by means of RTE instruction When the RTE instruction is used to return from interrupt handling, as shown in figure 5.13, consider the cycles to be inserted between the read instruction for synchronization and the RTE instruction, according to the set clock ratio (I : E : P). The on-chip peripheral interrupt signal should be negated at least 0.5 Icyc + 1.0 Pcyc before next interrupt acceptance becomes possible. For example, if clock ratio I : E : P is 4 : 2 : 2, at least 2.5 Icyc should be inserted. b. When changing level during interrupt handling When the SR value is changed by means of an LDC instruction and multiple implementation of other interrupts is enabled, consider the cycles to be inserted between the synchronization instruction and the LDC instruction as shown in figure 5.14, according to the set clock ratio (I : E : P). The on-chip peripheral interrupt signal should be negated at least 0.5 Icyc + 1.0 Pcyc before next interrupt acceptance becomes possible. For example, if clock ratio I : E : P is 4 : 2 : 2, at least 2.5 Icyc should be inserted.
Write completed Interrupt clear instruction Synchronization instruction RTE instruction Delay slot instruction Interrupt return destination instruction D E D M E D M E Next interrupt can be accepted
On-chip peripheral write, min. 1 Icyc On-chip peripheral W read, min. 1 Icyc M M D F 0.5Icyc + 1.0Pcyc E D E
On-chip peripheral interrupt
Figure 5.13 Pipeline Operation when Returning by Means of RTE Instruction
Rev. 2.00 Mar 09, 2006 page 197 of 906 REJ09B0292-0200
Section 5 Interrupt Controller (INTC)
Write completed Interrupt clear instruction Synchronization instruction
* * *
Next interrupt can be accepted
D
E D
M E
On-chip peripheral write, min. 1 Icyc On-chip peripheral M W read, min. 1 Icyc
LDC instruction Interrupt disable instruction Normal instruction
D
E D E D E
0.5Icyc + 1.0Pcyc On-chip peripheral interrupt
Figure 5.14 Pipeline Operation when Interrupts are Enabled by Means of SR Modification In the above figure, the stage in which the instruction fetch occurs cannot be specified because of the mix of DSP instructions in this chip, so instruction fetch F is omitted in most cases during pipeline operation.
Rev. 2.00 Mar 09, 2006 page 198 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Section 6 User Break Controller (UBC)
6.1 Overview
The user break controller (UBC) provides functions that simplify program debugging. When break conditions are set in the UBC, a user break interrupt is generated according to the conditions of the bus cycle generated by the CPU or on-chip DMAC (DMAC or E-DMAC). This function makes it easy to design a sophisticated self-monitoring debugger, enabling programs to be debugged with the chip alone, without using an in-circuit emulator. 6.1.1 Features
The UBC has the following features: * The following can be set as break conditions: Number of break channels: Four (channels A, B, C, and D) User break interrupts can be generated on independent or sequential conditions for channels A, B, C, and D. Sequential break settings * Channel A channel B channel C channel D * Channel B channel C channel D * Channel C channel D 1. Address: 32-bit masking capability, individual address setting possible (cache bus (CPU), internal bus (DMAC, E-DMAC), X/Y bus) 2. Data (channels C and D only,): 32-bit masking capability, individual address setting possible (cache bus (CPU), internal bus (DMAC, E-DMAC), X/Y bus) 3. Bus master: CPU cycle/on-chip DMAC (DMAC, E-DMAC) cycle 4. Bus cycle: Instruction fetch/data access 5. Read/write 6. Operand cycle: Byte/word/longword * User break interrupt generation on occurrence of break condition A user-written user break interrupt exception routine can be executed. * Processing can be stopped before or after instruction execution in an instruction fetch cycle. * Break with specification of number of executions (channels C and D only) Settable number of executions: maximum 212 - 1 (4095) * PC trace function
Rev. 2.00 Mar 09, 2006 page 199 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
The branch source/branch destination can be traced when a branch instruction is fetched (maximum 8 addresses (4 pairs)). 6.1.2 Block Diagram
BARAH
BARAL
Address
BAMRAH BAMRAL
Access Channel A
BBRA
BARBH
BARBL
Address
BAMRBH BAMRBL
Access
Internal address bus Cache address bus
BBRB
Channel B
X/Y address bus
Internal data bus
Cache data bus
X/Y data bus
BARCH
BARCL
Access
Address
BAMRCH BAMRCL
BDRCH
BDRCL
Data
BDMRCH BDMRCL
Access Channel C
BBRC BETRC
BARDH
BARDL
Address
BAMRDH BAMRDL
BDRDH
BDRDL
Data
BDMRDH BDMRDL
Access Channel D
BBRD BETRD
BRSRH
BRSRL BRDRL
PC trace
BRDRH BRFR
Control
BRCRH
BRCRL
Internal interrupt signal Legend BARAH/L: BAMRAH/L: BBRA: BARBH/L: BAMRBH/L: BBRB: BARCH/L: BAMRCH/L: BDRCH/L: BDMRCH/L: BBRC: Break address register AH/L Break address mask register AH/L Break bus cycle register A Break address register BH/L Break address mask register BH/L Break bus cycle register B Break address register CH/L Break address mask register CH/L Break data register CH/L Break data mask register CH/L Break bus cycle register C BETRC: BARDH/L: BAMRDH/L: BDRDH/L: BDMRDH/L: BBRD: BETRD: BRCRH/L: BRFR: BRSRH/L: BRDRH/L: Break execution times register C Break address register DH/L Break address mask register DH/L Break data register DH/L Break data mask register DH/L Break bus cycle register D Break execution times register D Break control register H/L Branch flag register Branch source register H/L Branch destination register H/L
Figure 6.1 Block Diagram of User Break Controller
Rev. 2.00 Mar 09, 2006 page 200 of 906 REJ09B0292-0200
Module data bus
Section 6 User Break Controller (UBC)
6.1.3 Table 6.1
Name
Register Configuration UBC Registers
Abbreviation BARAH BARAL BAMRAH BAMRAL BBRA BARBH BARBL BAMRBH BAMRBL BBRB BARCH BARCL BAMRCH BAMRCL BDRCH BDRCL BDMRCH BDMRCL BBRC BETRC BARDH BARDL BAMRDH BAMRDL BDRDH BDRDL BDMRDH BDMRDL 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 R/W R/W R/W R/W R/W R/W Initial 1 Value* H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 Address H'FFFFFF00 H'FFFFFF02 H'FFFFFF04 H'FFFFFF06 H'FFFFFF08 H'FFFFFF20 H'FFFFFF22 H'FFFFFF24 H'FFFFFF26 H'FFFFFF28 H'FFFFFF40 H'FFFFFF42 H'FFFFFF44 H'FFFFFF46 H'FFFFFF50 H'FFFFFF52 H'FFFFFF54 H'FFFFFF56 H'FFFFFF48 H'FFFFFF58 H'FFFFFF60 H'FFFFFF62 H'FFFFFF64 H'FFFFFF66 H'FFFFFF70 H'FFFFFF72 H'FFFFFF74 H'FFFFFF76
2 Access Size*
Break address register AH Break address register AL Break address mask register AH Break address mask register AL Break bus cycle register A Break address register BH Break address register BL Break address mask register BH Break address mask register BL Break bus cycle register B Break address register CH Break address register CL Break address mask register CH Break address mask register CL Break data register CH Break data register CL Break data mask register CH Break data mask register CL Break bus cycle register C Break execution times register C Break address register DH Break address register DL Break address mask register DH Break address mask register DL Break data register DH Break data register DL Break data mask register DH Break data mask register DL
16 16 16 16 16, 32 16 16 16 16 16, 32 16 16 16 16 16 16 16 16 16, 32 16, 32 16 16 16 16 16 16 16 16
32 32
32 32
32 32 32 32
32 32 32 32
Rev. 2.00 Mar 09, 2006 page 201 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC) Abbreviation BBRD BETRD BRCRH BRCRL BRFR BRSRH BRSRL BRDRH BRDRL Initial 1 Value* H'0000 H'0000 H'0000 H'0000 *3
Name Break bus cycle register D Break execution times register D Break control register H Break control register L Branch flag register Branch source register H Branch source register L Branch destination register H Branch destination register L
R/W R/W R/W R/W R/W R R R R R
Address H'FFFFFF68 H'FFFFFF78 H'FFFFFF30 H'FFFFFF32 H'FFFFFF10
Access Size* 16, 32 16, 32 16 16 16, 32 16 16 16 16 32 32 32
2
Undefined H'FFFFFF14 Undefined H'FFFFFF16 Undefined H'FFFFFF18 Undefined H'FFFFFF1A
Notes: 1. Initialized by a power-on reset. Value is retained in standby mode, and is undefined after a manual reset. 2. Byte access cannot be used. 3. Bits SVF and DVF in BRFR are initialized by a power-on reset; the other bits in BRFR are not initialized.
Rev. 2.00 Mar 09, 2006 page 202 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2
6.2.1
BARAH
Register Descriptions
Break Address Register A (BARA)
Bit: Initial value: R/W: Bit: Initial value: R/W: BARAL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 BAA31 0 R/W 7 BAA23 0 R/W
14 BAA30 0 R/W 6 BAA22 0 R/W
13 BAA29 0 R/W 5 BAA21 0 R/W
12 BAA28 0 R/W 4 BAA20 0 R/W
11 BAA27 0 R/W 3 BAA19 0 R/W
10 BAA26 0 R/W 2 BAA18 0 R/W
9 BAA25 0 R/W 1 BAA17 0 R/W
8 BAA24 0 R/W 0 BAA16 0 R/W
15 BAA15 0 R/W 7 BAA7 0 R/W
14 BAA14 0 R/W 6 BAA6 0 R/W
13 BAA13 0 R/W 5 BAA5 0 R/W
12 BAA12 0 R/W 4 BAA4 0 R/W
11 BAA11 0 R/W 3 BAA3 0 R/W
10 BAA10 0 R/W 2 BAA2 0 R/W
9 BAA9 0 R/W 1 BAA1 0 R/W
8 BAA8 0 R/W 0 BAA0 0 R/W
Break address register A (BARA) consists of two 16-bit readable/writable registers: break address register AH (BARAH) and break address register AL (BARAL). BARAH specifies the upper half (bits 31 to 16) of the address used as a channel A break condition, and BARAL specifies the lower half (bits 15 to 0). BARAH and BARAL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined. BARAH Bits 15 to 0--Break Address A31 to A16 (BAA31 to BAA16): These bits store the upper half (bits 31 to 16) of the address used as a channel A break condition. BARAL Bits 15 to 0--Break Address A15 to A0 (BAA15 to BAA0): These bits store the lower half (bits 15 to 0) of the address used as a channel A break condition.
Rev. 2.00 Mar 09, 2006 page 203 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.2
BAMRAH
Break Address Mask Register A (BAMRA)
Bit: Initial value: R/W: Bit: Initial value: R/W: BAMRAL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 0 R/W 7 0 R/W
14 0 R/W 6 0 R/W
13 0 R/W 5 0 R/W
12 0 R/W 4 0 R/W
11 0 R/W 3 0 R/W
10 0 R/W 2 0 R/W
9 0 R/W 1 0 R/W
8 0 R/W 0 0 R/W
BAMA31 BAMA30 BAMA29 BAMA28 BAMA27 BAMA26 BAMA25 BAMA24
BAMA23 BAMA22 BAMA21 BAMA20 BAMA19 BAMA18 BAMA17 BAMA16
15 0 R/W 7 BAMA7 0 R/W
14 0 R/W 6 BAMA6 0 R/W
13 0 R/W 5 BAMA5 0 R/W
12 0 R/W 4 BAMA4 0 R/W
11 0 R/W 3 BAMA3 0 R/W
10 0 R/W 2 BAMA2 0 R/W
9 0 R/W 1 BAMA1 0 R/W
8 BAMA8 0 R/W 0 BAMA0 0 R/W
BAMA15 BAMA14 BAMA13 BAMA12 BAMA11 BAMA10 BAMA9
Break address mask register A (BAMRA) consists of two 16-bit readable/writable registers: break address mask register AH (BAMRAH) and break address mask register AL (BAMRAL). BAMRAH specifies which bits of the break address set in BARAH are to be masked, and BAMRAL specifies which bits of the break address set in BARAL are to be masked. BAMRAH and BAMRAL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined. BAMRAH Bits 15 to 0--Break Address Mask A31 to A16 (BAMA31 to BAMA16): These bits specify whether or not corresponding channel A break address bits 31 to 16 (BAA31 to BAA16) set in BARAH are to be masked.
Rev. 2.00 Mar 09, 2006 page 204 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
BAMRAL Bits 15 to 0--Break Address Mask A15 to A0 (BAMA15 to BAMA0): These bits specify whether or not corresponding channel A break address bits 15 to 0 (BAA15 to BAA0) set in BARAL are to be masked.
Bit 31 to 0: BAMAn 0 1 Note: n = 31 to 0 Description Channel A break address bit BAAn is included in break condition (Initial value) Channel A break address bit BAAn is masked, and not included in condition
6.2.3
Break Bus Cycle Register A (BBRA)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 CPA1 0 R/W 14 -- 0 R 6 CPA0 0 R/W 13 -- 0 R 5 IDA1 0 R/W 12 -- 0 R 4 IDA0 0 R/W 11 -- 0 R 3 RWA1 0 R/W 10 -- 0 R 2 RWA0 0 R/W 9 -- 0 R 1 SZA1 0 R/W 8 -- 0 R 0 SZA0 0 R/W
Break bus cycle register A (BBRA) is a 16-bit readable/writable register that sets four channel A break conditions: (1) CPU cycle/on-chip DMAC (DMAC, E-DMAC) cycle, (2) instruction fetch/data access, (3) read/write, and (4) operand size. BBRA is initialized to H'0000 by a poweron reset; after a manual reset, its value is undefined. Bits 15 to 8--Reserved: These bits are always read as 0. The write value should always be 0. Bits 7 and 6--CPU/DMAC, E-DMAC Cycle Select A (CPA1, CPA0): These bits specify whether a CPU cycle, or a DMAC or E-DMAC cycle, is to be selected as the bus cycle used as a channel A break condition.
Bit 7: CPA1 0 1 Bit 6: CPA0 0 1 0 1 Description Channel A user break interrupt is not generated CPU cycle is selected as user break condition DMAC or E-DMAC cycle is selected as user break condition CPU, DMAC, or E-DMAC cycle is selected as user break condition Rev. 2.00 Mar 09, 2006 page 205 of 906 REJ09B0292-0200 (Initial value)
Section 6 User Break Controller (UBC)
Bits 5 and 4--Instruction Fetch/Data Access Select A (IDA1, IDA0): These bits specify whether an instruction fetch cycle or data access cycle is to be selected as the bus cycle used as a channel A break condition.
Bit 5: IDA1 0 1 Bit 4: IDA0 0 1 0 1 Description Channel A user break interrupt is not generated Instruction fetch cycle is selected as break condition Data access cycle is selected as break condition Instruction fetch cycle or data access cycle is selected as break condition (Initial value)
Bits 3 and 2--Read/Write Select A (RWA1, RWA0): These bits specify whether a read cycle or write cycle is to be selected as the bus cycle used as a channel A break condition.
Bit 3: RWA1 0 1 Bit 2: RWA0 0 1 0 1 Description Channel A user break interrupt is not generated Read cycle is selected as break condition Write cycle is selected as break condition Read cycle or write cycle is selected as break condition (Initial value)
Bits 1 and 0--Operand Size Select A (SZA1, SZA0): These bits select the operand size of the bus cycle used as a channel A break condition.
Bit 1: SZA1 0 1 Bit 0: SZA0 0 1 0 1 Description Operand size is not included in break conditions Byte access is selected as break condition Word access is selected as break condition Longword access is selected as break condition (Initial value)
Notes: When a break is to be executed on an instruction fetch, clear the SZA0 bit to 0. All instructions are regarded as being accessed using word size (instruction fetches are always performed as longword). In the case of an instruction, the operand size is word; in the case of a CPU/DMAC, EDMAC data access, it is determined by the specified operand size. Note that the operand size is not determined by the bus width of the space accessed.
Rev. 2.00 Mar 09, 2006 page 206 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.4
BARBH
Break Address Register B (BARB)
Bit: Initial value: R/W: Bit: Initial value: R/W: BARBL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 BAB31 0 R/W 7 BAB23 0 R/W
14 BAB30 0 R/W 6 BAB22 0 R/W
13 BAB29 0 R/W 5 BAB21 0 R/W
12 BAB28 0 R/W 4 BAB20 0 R/W
11 BAB27 0 R/W 3 BAB19 0 R/W
10 BAB26 0 R/W 2 BAB18 0 R/W
9 BAB25 0 R/W 1 BAB17 0 R/W
8 BAB24 0 R/W 0 BAB16 0 R/W
15 BAB15 0 R/W 7 BAB7 0 R/W
14 BAB14 0 R/W 6 BAB6 0 R/W
13 BAB13 0 R/W 5 BAB5 0 R/W
12 BAB12 0 R/W 4 BAB4 0 R/W
11 BAB11 0 R/W 3 BAB3 0 R/W
10 BAB10 0 R/W 2 BAB2 0 R/W
9 BAB9 0 R/W 1 BAB1 0 R/W
8 BAB8 0 R/W 0 BAB0 0 R/W
Break address register B (BARB) consists of two 16-bit readable/writable registers: break address register BH (BARBH) and break address register BL (BARBL). BARBH specifies the upper half (bits 31 to 16) of the address used as a channel B break condition, and BARBL specifies the lower half (bits 15 to 0). BARBH and BARBL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined. BARBH Bits 15 to 0--Break Address B31 to B16 (BAB31 to BAB16): These bits store the upper half (bits 31 to 16) of the address used as a channel B break condition. BARBL Bits 15 to 0--Break Address B15 to B0 (BAB15 to BAB0): These bits store the lower half (bits 15 to 0) of the address used as a channel B break condition.
Rev. 2.00 Mar 09, 2006 page 207 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.5
BAMRBH
Break Address Mask Register B (BAMRB)
Bit: Initial value: R/W: Bit: Initial value: R/W: BAMRBL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 0 R/W 7 0 R/W
14 0 R/W 6 0 R/W
13 0 R/W 5 0 R/W
12 0 R/W 4 0 R/W
11 0 R/W 3 0 R/W
10 0 R/W 2 0 R/W
9 0 R/W 1 0 R/W
8 0 R/W 0 0 R/W
BAMB31 BAMB30 BAMB29 BAMB28 BAMB27 BAMB26 BAMB25 BAMB24
BAMB23 BAMB22 BAMB21 BAMB20 BAMB19 BAMB18 BAMB17 BAMB16
15 0 R/W 7 BAMB7 0 R/W
14 0 R/W 6 BAMB6 0 R/W
13 0 R/W 5 BAMB5 0 R/W
12 0 R/W 4 BAMB4 0 R/W
11 0 R/W 3 BAMB3 0 R/W
10 0 R/W 2 BAMB2 0 R/W
9 0 R/W 1 BAMB1 0 R/W
8 BAMB8 0 R/W 0 BAMB0 0 R/W
BAMB15 BAMB14 BAMB13 BAMB12 BAMB11 BAMB10 BAMB9
Break address mask register B (BAMRB) consists of two 16-bit readable/writable registers: break address mask register BH (BAMRBH) and break address mask register BL (BAMRBL). BAMRBH specifies which bits of the break address set in BARBH are to be masked, and BAMRBL specifies which bits of the break address set in BARBL are to be masked. BAMRBH and BAMRBL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined. BAMRBH Bits 15 to 0--Break Address Mask B31 to B16 (BAMB31 to BAMB16): These bits specify whether or not corresponding channel B break address bits 31 to 16 (BAB31 to BAB16) set in BARBH are to be masked.
Rev. 2.00 Mar 09, 2006 page 208 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
BAMRBL Bits 15 to 0--Break Address Mask B15 to B0 (BAMB15 to BAMB0): These bits specify whether or not corresponding channel B break address bits 15 to 0 (BAB15 to BAB0) set in BARBL are to be masked.
Bit 31 to 0: BAMBn 0 1 Note: n = 31 to 0 Description Channel B break address bit BABn is included in break condition (Initial value) Channel B break address bit BABn is masked, and not included in condition
6.2.6
Break Bus Cycle Register B (BBRB)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 CPB1 0 R/W 14 -- 0 R 6 CPB0 0 R/W 13 -- 0 R 5 IDB1 0 R/W 12 -- 0 R 4 IDB0 0 R/W 11 -- 0 R 3 RWB1 0 R/W 10 -- 0 R 2 RWB0 0 R/W 9 -- 0 R 1 SZB1 0 R/W 8 -- 0 R 0 SZB0 0 R/W
Break bus cycle register B (BBRB) is a 16-bit readable/writable register that sets four channel B break conditions: (1) CPU cycle/on-chip DMAC (DMAC, E-DMAC) cycle, (2) instruction fetch/data access, (3) read/write, and (4) operand size. BBRB is initialized to H'0000 by a poweron reset; after a manual reset, its value is undefined. Bits 15 to 8--Reserved: These bits are always read as 0. The write value should always be 0. Bits 7 and 6--CPU/DMAC, E-DMAC Cycle Select B (CPB1, CPB0): These bits specify whether a CPU cycle, or a DMAC or E-DMAC cycle, is to be selected as the bus cycle used as a channel B break condition.
Bit 7: CPB1 0 1 Bit 6: CPB0 0 1 0 1 Description Channel B user break interrupt is not generated CPU cycle is selected as user break condition DMAC or E-DMAC cycle is selected as user break condition CPU, DMAC, or E-DMAC cycle is selected as user break condition Rev. 2.00 Mar 09, 2006 page 209 of 906 REJ09B0292-0200 (Initial value)
Section 6 User Break Controller (UBC)
Bits 5 and 4--Instruction Fetch/Data Access Select B (IDB1, IDB0): These bits specify whether an instruction fetch cycle or data access cycle is to be selected as the bus cycle used as a channel B break condition.
Bit 5: IDB1 0 1 Bit 4: IDB0 0 1 0 1 Description Channel B user break interrupt is not generated Instruction fetch cycle is selected as break condition Data access cycle is selected as break condition Instruction fetch cycle or data access cycle is selected as break condition (Initial value)
Bits 3 and 2--Read/Write Select B (RWB1, RWB0): These bits specify whether a read cycle or write cycle is to be selected as the bus cycle used as a channel B break condition.
Bit 3: RWB1 0 1 Bit 2: RWB0 0 1 0 1 Description Channel B user break interrupt is not generated Read cycle is selected as break condition Write cycle is selected as break condition Read cycle or write cycle is selected as break condition (Initial value)
Bits 1 and 0--Operand Size Select B (SZB1, SZB0): These bits select the operand size of the bus cycle used as a channel B break condition.
Bit 1: SZB1 0 1 Bit 0: SZB0 0 1 0 1 Description Operand size is not included in break conditions Byte access is selected as break condition Word access is selected as break condition Longword access is selected as break condition (Initial value)
Notes: When a break is to be executed on an instruction fetch, clear the SZB0 bit to 0. All instructions are regarded as being accessed using word size (instruction fetches are always performed as longword). In the case of an instruction, the operand size is word; in the case of a CPU/DMAC, EDMAC data access, it is determined by the specified operand size. Note that the operand size is not determined by the bus width of the space accessed.
Rev. 2.00 Mar 09, 2006 page 210 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.7
BARCH
Break Address Register C (BARC)
Bit: Initial value: R/W: Bit: Initial value: R/W: BARCL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 BAC31 0 R/W 7 BAC23 0 R/W
14 BAC30 0 R/W 6 BAC22 0 R/W
13 BAC29 0 R/W 5 BAC21 0 R/W
12 BAC28 0 R/W 4 BAC20 0 R/W
11 BAC27 0 R/W 3 BAC19 0 R/W
10 BAC26 0 R/W 2 BAC18 0 R/W
9 BAC25 0 R/W 1 BAC17 0 R/W
8 BAC24 0 R/W 0 BAC16 0 R/W
15 BAC15 0 R/W 7 BAC7 0 R/W
14 BAC14 0 R/W 6 BAC6 0 R/W
13 BAC13 0 R/W 5 BAC5 0 R/W
12 BAC12 0 R/W 4 BAC4 0 R/W
11 BAC11 0 R/W 3 BAC3 0 R/W
10 BAC10 0 R/W 2 BAC2 0 R/W
9 BAC9 0 R/W 1 BAC1 0 R/W
8 BAC8 0 R/W 0 BAC0 0 R/W
Break address register C (BARC) consists of two 16-bit readable/writable registers: break address register CH (BARCH) and break address register CL (BARCL). BARCH specifies the upper half (bits 31 to 16) of the address used as a channel C break condition, and BARCL specifies the lower half (bits 15 to 0). The address bus connected to the X/Y memory can also be specified as a break condition by making a setting in the XYEC bit/XYSC bit in break bus cycle register C (BBRC). When XYEC = 0, BAC31 to BAC0 specify the address. When XYEC = 1, the upper 16 bits (BAC31 to BAC16) of BARC specify the X address bus, and the lower 16 bits (BAC15 to BAC0) specify the Y address bus. BARCH and BARCL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined.
Rev. 2.00 Mar 09, 2006 page 211 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
BARC Configuration
Upper 16 Bits (BAC31 to BAC16) XYEC = 0 XYEC = 1 Address X address (when XYSC = 0) Y address (when XYSC = 1) Upper 16 bits of address bus X address (XAB15 to XAB1)* -- Lower 16 Bits (BAC15 to BAC0) Lower 16 bits of address bus -- Y address (YAB15 to YAB1)*
Note: * As an X/Y bus access is always a word access, the values of XAB0 and YAB0 is not included in the break condition.
6.2.8
BAMRCH
Break Address Mask Register C (BAMRC)
Bit: Initial value: R/W: Bit: Initial value: R/W: BAMRCL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 0 R/W 7 0 R/W
14 0 R/W 6 0 R/W
13 0 R/W 5 0 R/W
12 0 R/W 4 0 R/W
11 0 R/W 3 0 R/W
10 0 R/W 2 0 R/W
9 0 R/W 1 0 R/W
8 0 R/W 0 0 R/W
BAMC31 BAMC30 BAMC29 BAMC28 BAMC27 BAMC26 BAMC25 BAMC24
BAMC23 BAMC22 BAMC21 BAMC20 BAMC19 BAMC18 BAMC17 BAMC16
15 0 R/W 7 BAMC7 0 R/W
14 0 R/W 6 BAMC6 0 R/W
13 0 R/W 5 BAMC5 0 R/W
12 0 R/W 4 BAMC4 0 R/W
11 0 R/W 3 BAMC3 0 R/W
10 0 R/W 2 BAMC2 0 R/W
9 0 R/W 1 BAMC1 0 R/W
8 BAMC8 0 R/W 0 BAMC0 0 R/W
BAMC15 BAMC14 BAMC13 BAMC12 BAMC11 BAMC10 BAMC9
Rev. 2.00 Mar 09, 2006 page 212 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Break address mask register C (BAMRC) consists of two 16-bit readable/writable registers: break address mask register CH (BAMRCH) and break address mask register CL (BAMRCL). BAMRCH specifies which bits of the break address set in BARCH are to be masked, and BAMRCL specifies which bits of the break address set in BARCL are to be masked. Operation also depends on bits XYEC and XYSC in BBRC as shown below. BAMRC Configuration
Upper 16 Bits (BAMC31 to BAMC16) XYEC = 0 XYEC = 1 Address X address (when XYSC = 0) Y address (when XYSC = 1 Bit 31 to 0: BAMCn 0 1 Note: n = 31 to 0 Upper 16 bits maskable Maskable -- Lower 16 Bits (BAMC15 to BAMC0) Lower 16 bits maskable -- Maskable
Description Channel C break address bit BACn is included in break condition (Initial value) Channel C break address bit BACn is masked, and not included in condition
Rev. 2.00 Mar 09, 2006 page 213 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.9
BDRCH
Break Data Register C (BDRC)
Bit: Initial value: R/W: Bit: Initial value: R/W: BDRCL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 BDC31 0 R/W 7 BDC23 0 R/W
14 BDC30 0 R/W 6 BDC22 0 R/W
13 BDC29 0 R/W 5 BDC21 0 R/W
12 BDC28 0 R/W 4 BDC20 0 R/W
11 BDC27 0 R/W 3 BDC19 0 R/W
10 BDC26 0 R/W 2 BDC18 0 R/W
9 BDC25 0 R/W 1 BDC17 0 R/W
8 BDC24 0 R/W 0 BDC16 0 R/W
15 BDC15 0 R/W 7 BDC7 0 R/W
14 BDC14 0 R/W 6 BDC6 0 R/W
13 BDC13 0 R/W 5 BDC5 0 R/W
12 BDC12 0 R/W 4 BDC4 0 R/W
11 BDC11 0 R/W 3 BDC3 0 R/W
10 BDC10 0 R/W 2 BDC2 0 R/W
9 BDC9 0 R/W 1 BDC1 0 R/W
8 BDC8 0 R/W 0 BDC0 0 R/W
Break data register C (BDRC) consists of two 16-bit readable/writable registers: break data register CH (BDRCH) and break data register CL (BDRCL). BDRCH specifies the upper half (bits 31 to 16) of the data used as a channel C break condition, and BDRCL specifies the lower half (bits 15 to 0). The data bus connected to the X/Y memory can also be specified as a break condition by making a setting in the XYEC bit/XYSC bit in break bus cycle register C (BBRC). When XYEC = 1, the upper 16 bits (BDC31 to BDC16) of BDRC specify the X data bus, and the lower 16 bits (BDC15 to BDC0) specify the Y data bus.
Rev. 2.00 Mar 09, 2006 page 214 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
BDRC Configuration
Upper 16 Bits (BDC31 to BDC16) XYEC = 0 XYEC = 1 Data X data (when XYSC = 0) Y data (when XYSC = 1) Upper 16 bits of data bus X data (XDB15 to XDB0) -- Lower 16 Bits (BDC15 to BDC0) Lower 16 bits of data bus -- Y data (YDB15 to YDB0)
6.2.10
Break Data Mask Register C (BDMRC)
BDMRCH Bit: Initial value: R/W: Bit: Initial value: R/W: BDMRCL Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W BDMC15 BDMC14 BDMC13 BDMC12 BDMC11 BDMC10 BDMC9 BDMC8 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W BDMC31 BDMC30 BDMC29 BDMC28 BDMC27 BDMC26 BDMC25 BDMC24
BDMC23 BDMC22 BDMC21 BDMC20 BDMC19 BDMC18 BDMC17 BDMC16
BDMC7 BDMC6 BDMC5 BDMC4 BDMC3 BDMC2 BDMC1 BDMC0
Break data mask register C (BDMRC) consists of two 16-bit readable/writable registers: break data mask register CH (BDMRCH) and break data mask register CL (BDMRCL). BDMRCH specifies which bits of the break data set in BDRCH are to be masked, and BDMRCL specifies
Rev. 2.00 Mar 09, 2006 page 215 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
which bits of the break data set in BDRCL are to be masked. Operation also depends on bits XYEC and XYSC in BBRC as shown below. BDMRCH and BDMRCL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined. BDMRC Configuration
Upper 16 Bits (BDMC31 to BDMC16) XYEC = 0 XYEC = 1 Data X data (when XYSC = 0) Y data (when XYSC = 1) Bit 31 to 0: BDMCn 0 1 Upper 16 bits maskable Maskable -- Lower 16 Bits (BDMC15 to BDMC0) Lower 16 bits maskable -- Maskable
Description Channel C break data bit BDCn is included in break condition (Initial value) Channel C break data bit BDCn is masked, and not included in condition
Notes: 1. n = 31 to 0 2. When including the data bus value in the break condition, specify the operand size. 3. When specifying byte size, and using odd-address data as a break condition, set the value in bits 7 to 0 of BDRC and BDMRC. When using even-address data as a break condition, set the value in bits 15 to 8. The unused 8 bits of these registers have no effect on the break condition.
Rev. 2.00 Mar 09, 2006 page 216 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.11
Break Bus Cycle Register C (BBRC)
Bit: 15 -- 0 R 7 CPC1 0 R/W 14 -- 0 R 6 CPC0 0 R/W 13 -- 0 R 5 IDC1 0 R/W 12 -- 0 R 4 IDC0 0 R/W 11 -- 0 R 3 RWC1 0 R/W 10 -- 0 R 2 RWC0 0 R/W 9 XYEC 0 R/W 1 SZC1 0 R/W 8 XYSC 0 R/W 0 SZC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W:
Break bus cycle register C (BBRC) is a 16-bit readable/writable register that sets five channel C break conditions: (1) internal bus (C-bus, I-bus)/X memory bus/Y memory bus), (2) CPU cycle/on-chip DMAC (DMAC, E-DMAC) cycle, (3) instruction fetch/data access, (4) read/write, and (5) operand size. BBRC is initialized to H'0000 by a power-on reset; after a manual reset, its value is undefined. Bits 15 to 10--Reserved: These bits are always read as 0. The write value should always be 0. Bit 9--X/Y Memory Bus Enable C (XYEC): Selects whether the X/Y bus is used as a channel C break condition.
Bit 9: XYEC 0 1 Description Cache bus or internal bus is selected as condition for channel C address/data (Initial value) X/Y bus is selected as condition for channel C address/data
Bit 8--X Bus/Y Bus Select C (XYSC): Selects whether the X bus or the Y bus is used as a channel C break condition. This bit is valid only when bit XYEC = 1.
Bit 8: XYSC 0 1 Description X bus is selected as channel C break condition Y bus is selected as channel C break condition (Initial value)
The configuration of bits 7 to 0 is the same as for BBRA.
Rev. 2.00 Mar 09, 2006 page 217 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.12
Break Execution Times Register C (BETRC)
Bit: 15 -- 0 R 7 ETRC7 0 R/W 14 -- 0 R 6 ETRC6 0 R/W 13 -- 0 R 5 ETRC5 0 R/W 12 -- 0 R 4 ETRC4 0 R/W 11 0 R/W 3 ETRC3 0 R/W 10 0 R/W 2 ETRC2 0 R/W 9 0 R/W 1 ETRC1 0 R/W 8 ETRC8 0 R/W 0 ETRC0 0 R/W
ETRC11 ETRC10 ETRC9
Initial value: R/W: Bit: Initial value: R/W:
When a channel C execution-times break condition is enabled (by setting the ETBEC bit in BRCR), this 16-bit register specifies the number of times a channel C break condition occurs before a user break interrupt is requested. The maximum value is 212 - 1 times. Each time a channel C break condition occurs, the value in BETRC is decremented by 1. After the BETRC value reaches H'0001, an interrupt is requested when a break condition next occurs. As exceptions and interrupts cannot be accepted for instructions in a repeat loop comprising no more than three instructions, BETRC is not decremented by the occurrence of a break condition for an instruction in such a repeat loop (see 4.6, When Exception Sources Are Not Accepted). Bits 15 to 12 are always read as 0, and should only be written with 0. BETRC is initialized to H'0000 by a power-on reset.
Rev. 2.00 Mar 09, 2006 page 218 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.13
BARDH
Break Address Register D (BARD)
Bit Initial value Read/Write Bit Initial value Read/Write BARDL Bit Initial value Read/Write Bit Initial value Read/Write
15 BAD31 0 R/W 7 BAD23 0 R/W
14 BAD30 0 R/W 6 BAD22 0 R/W
13 BAD29 0 R/W 5 BAD21 0 R/W
12 BAD28 0 R/W 4 BAD20 0 R/W
11 BAD27 0 R/W 3 BAD19 0 R/W
10 BAD26 0 R/W 2 BAD18 0 R/W
9 BAD25 0 R/W 1 BAD17 0 R/W
8 BAD24 0 R/W 0 BAD16 0 R/W
15 BAD15 0 R/W 7 BAD7 0 R/W
14 BAD14 0 R/W 6 BAD6 0 R/W
13 BAD13 0 R/W 5 BAD5 0 R/W
12 BAD12 0 R/W 4 BAD4 0 R/W
11 BAD11 0 R/W 3 BAD3 0 R/W
10 BAD10 0 R/W 2 BAD2 0 R/W
9 BAD9 0 R/W 1 BAD1 0 R/W
8 BAD8 0 R/W 0 BAD0 0 R/W
Break address register D (BARD) consists of two 16-bit readable/writable registers: break address register DH (BARDH) and break address register DL (BARDL). BARDH specifies the upper half (bits 31 to 16) of the address used as a channel D break condition, and BARDL specifies the lower half (bits 15 to 0). The address bus connected to the X/Y memory can also be specified as a break condition by making a setting in the XYED bit/XYSD bit in break bus cycle register D (BBRD). When XYED = 0, BAD31 to BAD0 specify the address. When XYED = 1, the upper 16 bits (BAD31 to BAD16) of BARD specify the X address bus, and the lower 16 bits (BAD15 to BAD0) specify the Y address bus. BARDH and BARDL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined.
Rev. 2.00 Mar 09, 2006 page 219 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
BARD Configuration
Upper 16 Bits (BAD31 to BAD16) XYED = 0 XYED = 1 Address X address (when XYSD = 0) Y address (when XYSD = 1) Upper 16 bits of address bus X address (XAB15 to XAB1)* -- Lower 16 Bits (BAD15 to BAD0) Lower 16 bits of address bus -- Y address (YAB15 to YAB1)*
Note: * As an X/Y bus access is always a word access, the values of XAB0 and YAB0 is not included in the break condition.
6.2.14
BAMRDH
Break Address Mask Register D (BAMRD)
Bit: Initial value: R/W: Bit: Initial value: R/W: BAMRDL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 0 R/W 7 0 R/W
14 0 R/W 6 0 R/W
13 0 R/W 5 0 R/W
12 0 R/W 4 0 R/W
11 0 R/W 3 0 R/W
10 0 R/W 2 0 R/W
9 0 R/W 1 0 R/W
8 0 R/W 0 0 R/W
BAMD31 BAMD30 BAMD29 BAMD28 BAMD27 BAMD26 BAMD25 BAMD24
BAMD23 BAMD22 BAMD21 BAMD20 BAMD19 BAMD18 BAMD17 BAMD16
15 0 R/W 7 BAMD7 0 R/W
14 0 R/W 6 BAMD6 0 R/W
13 0 R/W 5 BAMD5 0 R/W
12 0 R/W 4 BAMD4 0 R/W
11 0 R/W 3 BAMD3 0 R/W
10 0 R/W 2 BAMD2 0 R/W
9 0 R/W 1 BAMD1 0 R/W
8 BAMD8 0 R/W 0 BAMD0 0 R/W
BAMD15 BAMD14 BAMD13 BAMD12 BAMD11 BAMD10 BAMD9
Rev. 2.00 Mar 09, 2006 page 220 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Break address mask register D (BAMRD) consists of two 16-bit readable/writable registers: break address mask register DH (BAMRDH) and break address mask register DL (BAMRDL). BAMRDH specifies which bits of the break address set in BARDH are to be masked, and BAMRDL specifies which bits of the break address set in BARDL are to be masked. Operation also depends on bits XYED and XYSD in BBRD as shown below. BAMRD Configuration
Upper 16 Bits (BAMD31 to BAMD16) XYED = 0 XYED = 1 Address X address (when XYSD = 0) Y address (when XYSD = 1) Bit 31 to 0: BAMDn 0 1 Note: n = 31 to 0 Upper 16 bits maskable Maskable -- Lower 16 Bits (BAMD15 to BAMD0) Lower 16 bits maskable -- Maskable
Description Channel D break address bit BADn is included in break condition (Initial value) Channel D break address bit BADn is masked, and not included in condition
Rev. 2.00 Mar 09, 2006 page 221 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.15
BDRDH
Break Data Register D (BDRD)
Bit: Initial value: R/W: Bit: Initial value: R/W: BDRDL Bit: Initial value: R/W: Bit: Initial value: R/W:
15 BDD31 0 R/W 7 BDD23 0 R/W
14 BDD30 0 R/W 6 BDD22 0 R/W
13 BDD29 0 R/W 5 BDD21 0 R/W
12 BDD28 0 R/W 4 BDD20 0 R/W
11 BDD27 0 R/W 3 BDD19 0 R/W
10 BDD26 0 R/W 2 BDD18 0 R/W
9 BDD25 0 R/W 1 BDD17 0 R/W
8 BDD24 0 R/W 0 BDD16 0 R/W
15 BDD15 0 R/W 7 BDD7 0 R/W
14 BDD14 0 R/W 6 BDD6 0 R/W
13 BDD13 0 R/W 5 BDD5 0 R/W
12 BDD12 0 R/W 4 BDD4 0 R/W
11 BDD11 0 R/W 3 BDD3 0 R/W
10 BDD10 0 R/W 2 BDD2 0 R/W
9 BDD9 0 R/W 1 BDD1 0 R/W
8 BDD8 0 R/W 0 BDD0 0 R/W
Break data register D (BDRD) consists of two 16-bit readable/writable registers: break data register DH (BDRDH) and break data register DL (BDRDL). BDRDH specifies the upper half (bits 31 to 16) of the data used as a channel D break condition, and BDRDL specifies the lower half (bits 15 to 0). The data bus connected to the X/Y memory can also be specified as a break condition by making a setting in the XYED bit/XYSD bit in break bus cycle register D (BBRD). When XYED = 1, the upper 16 bits (BDD31 to BDD16) of BDRD specify the X data bus, and the lower 16 bits (BDD15 to BDD0) specify the Y data bus.
Rev. 2.00 Mar 09, 2006 page 222 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
BDRD Configuration
Upper 16 Bits (BDD31 to BDD16) XYED = 0 XYED = 1 Data X data (when XYSD = 0) Y data (when XYSD = 1) Upper 16 bits of data bus X data (XDB15 to XDB0) -- Lower 16 Bits (BDD15 to BDD0) Lower 16 bits of data bus -- Y data (YDB15 to YDB0)
6.2.16
Break Data Mask Register D (BDMRD)
BDMRDH Bit: Initial value: R/W: Bit: Initial value: R/W: BDMRDL Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W BDMD15 BDMD14 BDMD13 BDMD12 BDMD11 BDMD10 BDMD9 BDMD8 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W BDMD31 BDMD30 BDMD29 BDMD28 BDMD27 BDMD26 BDMD25 BDMD24
BDMD23 BDMD22 BDMD21 BDMD20 BDMD19 BDMD18 BDMD17 BDMD16
BDMD7 BDMD6 BDMD5 BDMD4 BDMD3 BDMD2 BDMD1 BDMD0
Break data mask register D (BDMRD) consists of two 16-bit readable/writable registers: break data mask register DH (BDMRDH) and break data mask register DL (BDMRDL). BDMRDH
Rev. 2.00 Mar 09, 2006 page 223 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
specifies which bits of the break data set in BDRDH are to be masked, and BDMRDL specifies which bits of the break data set in BDRDL are to be masked. Operation also depends on bits XYED and XYSD in BBRD as shown below. BDMRDH and BDMRDL are initialized to H'0000 by a power-on reset; after a manual reset, their values are undefined. BDMRD Configuration
Upper 16 Bits (BDMD31 to BDMD16) XYED = 0 XYED = 1 Data X data (when XYSD = 0) Y data (when XYSD = 1) Bit 31 to 0: BDMDn 0 1 Upper 16 bits maskable Maskable -- Lower 16 Bits (BDMD15 to BDMD0) Lower 16 bits maskable -- Maskable
Description Channel D break data bit BDDn is included in break condition (Initial value) Channel D break data bit BDDn is masked, and not included in condition
Notes: 1. n = 31 to 0 2. When including the data bus value in the break condition, specify the operand size. 3. When specifying byte size, and using odd-address data as a break condition, set the value in bits 7 to 0 of BDRD and BDMRD. When using even-address data as a break condition, set the value in bits 15 to 8. The unused 8 bits of these registers have no effect on the break condition.
Rev. 2.00 Mar 09, 2006 page 224 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.17
Break Bus Cycle Register D (BBRD)
Bit: 15 -- 0 R 7 CPD1 0 R/W 14 -- 0 R 6 CPD0 0 R/W 13 -- 0 R 5 IDD1 0 R/W 12 -- 0 R 4 IDD0 0 R/W 11 -- 0 R 3 RWD1 0 R/W 10 -- 0 R 2 RWD0 0 R/W 9 XYED 0 R/W 1 SZD1 0 R/W 8 XYSD 0 R/W 0 SZD0 0 R/W
Initial value: R/W: Bit: Initial value: R/W:
Break bus cycle register D (BBRD) is a 16-bit readable/writable register that sets five channel D break conditions: (1) internal bus (C-bus, I-bus)/X memory bus/Y memory bus), (2) CPU cycle/on-chip DMAC (DMAC, E-DMAC) cycle, (3) instruction fetch/data access, (4) read/write, and (5) operand size. BBRD is initialized to H'0000 by a power-on reset; after a manual reset, its value is undefined. Bits 15 to 10--Reserved: These bits are always read as 0. The write value should always be 0. Bit 9--X/Y Memory Bus Enable D (XYED): Selects whether the X/Y bus is used as a channel D break condition.
Bit 9: XYED 0 1 Description Cache bus or internal bus is selected as condition for channel D address/data (Initial value) X/Y bus is selected as condition for channel D address/data
Bit 8--X Bus/Y Bus Select D (XYSD): Selects whether the X bus or the Y bus is used as a channel D break condition. This bit is valid only when bit XYED = 1.
Bit 8: XYSD 0 1 Description X bus is selected as channel D break condition Y bus is selected as channel D break condition (Initial value)
The configuration of bits 7 to 0 is the same as for BBRA.
Rev. 2.00 Mar 09, 2006 page 225 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.18
Break Execution Times Register D (BETRD)
Bit: 15 -- 0 R 7 ETRD7 0 R/W 14 -- 0 R 6 ETRD6 0 R/W 13 -- 0 R 5 ETRD5 0 R/W 12 -- 0 R 4 ETRD4 0 R/W 11 0 R/W 3 ETRD3 0 R/W 10 0 R/W 2 ETRD2 0 R/W 9 0 R/W 1 ETRD1 0 R/W 8 ETRD8 0 R/W 0 ETRD0 0 R/W
ETRD11 ETRD10 ETRD9
Initial value: R/W: Bit: Initial value: R/W:
When a channel D execution-times break condition is enabled (by setting the ETBED bit in BRCR), this 16-bit register specifies the number of times a channel D break condition occurs before a user break interrupt is requested. The maximum value is 212 - 1 times. Each time a channel D break condition occurs, the value in BETRD is decremented by 1. After the BETRD value reaches H'0001, an interrupt is requested when a break condition next occurs. As exceptions and interrupts cannot be accepted for instructions in a repeat loop comprising no more than three instructions, BETRD is not decremented by the occurrence of a break condition for an instruction in such a repeat loop (see 4.6, When Exception Sources Are Not Accepted). Bits 15 to 12 are always read as 0, and should only be written with 0. BETRD is initialized to H'0000 by a power-on reset.
Rev. 2.00 Mar 09, 2006 page 226 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.19
BRCRH
Break Control Register (BRCR)
Bit: Initial value: R/W: Bit: Initial value: R/W: BRCRL Bit: Initial value: R/W: Bit: Initial value: R/W:
31 0 R/W 23 0 R/W
30 0 R/W 22 0 R/W
29 -- 0 R/W 21 -- 0 R/W
28 -- 0 R/W 20 SEQ1 0 R/W
27 PCTE 0 R/W 19 SEQ0 0 R/W
26 PCBA 0 R/W 18 PCBB 0 R/W
25 -- 0 R/W 17 -- 0 R/W
24 -- 0 R/W 16 -- 0 R/W
CMFCA CMFPA
CMFCB CMFPB
15 0 R/W 7 0 R/W
14 0 R/W 6 0 R/W
13 ETBEC 0 R/W 5 ETBED 0 R/W
12 -- 0 R/W 4 -- 0 R/W
11 DBEC 0 R/W 3 DBED 0 R/W
10 PCBC 0 R/W 2 PCBD 0 R/W
9 -- 0 R/W 1 -- 0 R/W
8 -- 0 R/W 0 -- 0 R/W
CMFCC CMFPC
CMFCD CMFPD
The break control register (BRCR) is used to make the following settings: 1. Setting of independent channel mode or sequential condition mode for channels A, B, C, and D 2. Selection of pre- or post-instruction-execution break in case of an instruction fetch cycle 3. Selection of whether the data bus is to be included in the comparison conditions for channels C and D 4. Selection of whether an execution-times break is to be set for channels C and D 5. Selection of whether a PC trace is to be executed BRCR also contains flags that are set when a condition is satisfied. BRCR is initialized to H'00000000 by a power-on reset; after a manual reset, its value is undefined.
Rev. 2.00 Mar 09, 2006 page 227 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Bit 31--CPU Condition Match Flag A (CMFCA): This flag is set to 1 when a CPU bus cycle condition, among the break conditions set for channel A, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 31: CMFCA 0 1 Description User break interrupt has not been generated by a channel A CPU cycle condition (Initial value) User break interrupt has been generated by a channel A CPU cycle condition
Bit 30--DMAC Condition Match Flag A (CMFPA): This flag is set to 1 when an on-chip DMAC bus cycle condition, among the break conditions set for channel A, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 30: CMFPA 0 1 Description User break interrupt has not been generated by a channel A on-chip DMAC cycle condition (Initial value) User break interrupt has been generated by a channel A on-chip DMAC cycle condition
Bits 29 and 28--Reserved: These bits are always read as 0. The write value should always be 0. Bit 27--PC Trace Enable (PCTE): Selects whether a PC trace is to be executed.
Bit 27: PCTE 0 1 Description PC trace is not executed PC trace is executed (Initial value)
Bit 26--PC Break Select A (PCBA): Selects whether a channel A instruction fetch cycle break is effected before or after execution of the instruction.
Bit 26: PCBA 0 1 Description Channel A instruction fetch cycle break is effected before instruction execution (Initial value) Channel A instruction fetch cycle break is effected after instruction execution
Bits 25 and 24--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 228 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Bit 23--CPU Condition Match Flag B (CMFCB): This flag is set to 1 when a CPU bus cycle condition, among the break conditions set for channel B, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 23: CMFCB 0 1 Description User break interrupt has not been generated by a channel B CPU cycle condition (Initial value) User break interrupt has been generated by a channel B CPU cycle condition
Bit 22--DMAC Condition Match Flag B (CMFPB): This flag is set to 1 when an on-chip DMAC bus cycle condition, among the break conditions set for channel B, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 22: CMFPB 0 1 Description User break interrupt has not been generated by a channel B on-chip DMAC cycle condition (Initial value) User break interrupt has been generated by a channel B on-chip DMAC cycle condition
Bit 21--Reserved: This bit is always read as 0. The write value should always be 0. Bits 20 and 19--Sequence Condition Select (SEQ1, SEQ0): These bits select independent or sequential conditions for channels A, B, C, and D.
Bit 20: SEQ1 0 Bit 19: SEQ0 0 1 1 0 1 Description Comparison based on independent conditions for channels A, B, C, and D (Initial value) Channel C D sequential condition; channels A and B independent Channel B C D sequential condition; channel A independent Channel A B C D sequential condition
Rev. 2.00 Mar 09, 2006 page 229 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Bit 18--PC Break Select B (PCBB): Selects whether a channel B instruction fetch cycle break is effected before or after execution of the instruction.
Bit 18: PCBB 0 1 Description Channel B instruction fetch cycle break is effected before instruction execution (Initial value) Channel B instruction fetch cycle break is effected after instruction execution
Bits 17 and 16--Reserved: These bits are always read as 0. The write value should always be 0. Bit 15--CPU Condition Match Flag C (CMFCC): This flag is set to 1 when a CPU bus cycle condition, among the break conditions set for channel C, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 15: CMFCC 0 1 Description User break interrupt has not been generated by a channel C CPU cycle condition (Initial value) User break interrupt has been generated by a channel C CPU cycle condition
Bit 14--DMAC Condition Match Flag C (CMFPC): This flag is set to 1 when an on-chip DMAC bus cycle condition, among the break conditions set for channel C, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 14: CMFPC 0 1 Description User break interrupt has not been generated by a channel C on-chip DMAC cycle condition (Initial value) User break interrupt has been generated by a channel C on-chip DMAC cycle condition
Bit 13--Execution-Times Break Enable C (ETBEC): Enables a channel C execution-times break condition. When this bit is 1, a user break interrupt is generated when the number of break conditions that have occurred equals the number of executions specified by the break execution times register (BETRC).
Bit 13: ETBEC 0 1 Description Channel C execution-times break condition is disabled Channel C execution-times break condition is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 230 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Bit 12--Reserved: This bit is always read as 0. The write value should always be 0. Bit 11--Data Break Enable C (DBEC): Selects whether a data bus condition is to be included in the channel C break conditions.
Bit 11: DBEC 0 1 Description Data bus condition is not included in channel C conditions Data bus condition is included in channel C conditions (Initial value)
Bit 10--PC Break Select C (PCBC): Selects whether a channel C instruction fetch cycle break is effected before or after execution of the instruction.
Bit 10: PCBC 0 1 Description Channel C instruction fetch cycle break is effected before instruction execution (Initial value) Channel C instruction fetch cycle break is effected after instruction execution
Bits 9 and 8--Reserved: These bits are always read as 0. The write value should always be 0. Bit 7--CPU Condition Match Flag D (CMFCD): This flag is set to 1 when a CPU bus cycle condition, among the break conditions set for channel D, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 7: CMFCD 0 1 Description User break interrupt has not been generated by a channel D CPU cycle condition (Initial value) User break interrupt has been generated by a channel D CPU cycle condition
Bit 6--DMAC Condition Match Flag D (CMFPD): This flag is set to 1 when a DMAC bus cycle condition, among the break conditions set for channel D, is satisfied. This flag is not cleared to 0 (if the flag setting is to be checked again after it has once been set, the flag must be cleared by a write).
Bit 6: CMFPD 0 1 Description User break interrupt has not been generated by a channel D on-chip DMAC cycle condition (Initial value) User break interrupt has been generated by a channel D on-chip DMAC cycle condition
Rev. 2.00 Mar 09, 2006 page 231 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Bit 5--Execution-Times Break Enable D (ETBED): Enables a channel D execution-times break condition. When this bit is 1, a user break interrupt is generated when the number of break conditions that have occurred equals the number of executions specified by the break execution times register (BETRD).
Bit 5: ETBED 0 1 Description Channel D execution-times break condition is disabled Channel D execution-times break condition is enabled (Initial value)
Bit 4--Reserved: This bit is always read as 0. The write value should always be 0. Bit 3--Data Break Enable D (DBED): Selects whether a data bus condition is to be included in the channel D break conditions.
Bit 3: DBED 0 1 Description Data bus condition is not included in channel D conditions Data bus condition is included in channel D conditions (Initial value)
Bit 2--PC Break Select D (PCBD): Selects whether a channel D instruction fetch cycle break is effected before or after execution of the instruction.
Bit 2: PCBD 0 1 Description Channel D instruction fetch cycle break is effected before instruction execution (Initial value) Channel D instruction fetch cycle break is effected after instruction execution
Bits 1 and 0--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 232 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.2.20
Branch Flag Registers (BRFR)
Bit: 15 SVF 0 R 7 DVF 0 R 14 PID2 R 6 -- 0 R 13 PID1 R 5 -- 0 R 12 PID0 R 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 -- 0 R
Initial value: R/W: Bit: Initial value: R/W:
Undefined Undefined Undefined
The branch flag registers (BRFR) comprise a set of four 16-bit read-only registers. The BRFR registers contain flags indicating whether the actual branch addresses (in a branch instruction, repeat, interrupt, etc.) have been saved in BRSR and BRDR, and a 3-bit pointer indicating the number of cycles from fetch to execution of the last instruction executed. The BRFR registers form a FIFO (first-in first-out) queue for PC trace use. The queue is shifted at each branch. Bits SVF and DVF are initialized by a power-on reset, but bits PID2 to PID0 are not. Bit 15--Source Verify Flag (SVF): Indicates whether the address and pointer that enable the branch source address to be calculated have been stored in BRSR. This flag is set when the instruction at the branch destination address is fetched, and reset when BRSR is read.
Bit 15: SVF 0 1 Description BRSR value is invalid BRSR value is valid (Initial value)
Bits 14 to 12--PID2 to PID0: These bits comprise a pointer that indicates the instruction buffer number of the instruction executed immediately before a branch occurred.
Bits 14 to 12: PID2 to PID0 Odd Even Description PID indicates instruction buffer number PID+2 indicates instruction buffer number (Initial value)
Bits 11 to 8, 6 to 0--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 233 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Bit 7--Destination Verify Flag (DVF): Indicates whether the branch source address has been stored in BRDR. This flag is set when the instruction at the branch destination address is fetched, and reset when BRDR is read.
Bit 7: DVF 0 1 Description BRDR value is invalid BRDR value is valid (Initial value)
See the PC trace description for the method of executing a PC trace using the branch source registers (BRSR), branch destination registers (BRDR), and branch flag registers (BRFR). 6.2.21
BRSRH Bit: 31 BSA31 R/W: Bit: R 23 BSA23 R/W: BRSRL Bit: 15 BSA15 R/W: Bit: R 7 BSA7 R/W: R 14 BSA14 R 6 BSA6 R 13 BSA13 R 5 BSA5 R 12 BSA12 R 4 BSA4 R 11 BSA11 R 3 BSA3 R 10 BSA10 R 2 BSA2 R 9 BSA9 R 1 BSA1 R 8 BSA8 R 0 BSA0 R R 30 BSA30 R 22 BSA22 R 29 BSA29 R 21 BSA21 R 28 BSA28 R 20 BSA20 R 27 BSA27 R 19 BSA19 R 26 BSA26 R 18 BSA18 R 25 BSA25 R 17 BSA17 R 24 BSA24 R 16 BSA16 R
Branch Source Registers (BRSR)
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Rev. 2.00 Mar 09, 2006 page 234 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
The branch source registers (BRSR) comprise a set of four 32-bit read-only registers. The values in these registers are used to calculate the address of the last instruction executed before a branch when performing a PC trace. The BRSR registers form a FIFO (first-in first-out) queue for PC trace use. The queue is shifted at each branch. The BRSR registers are not initialized by a reset. 6.2.22
BRDRH Bit: 31 BDA31 R/W: Bit: R 23 BDA23 R/W: BRDRL Bit: 15 BDA15 R/W: Bit: R 7 BDA7 R/W: R 14 BDA14 R 6 BDA6 R 13 BDA13 R 5 BDA5 R 12 BDA12 R 4 BDA4 R 11 BDA11 R 3 BDA3 R 10 BDA10 R 2 BDA2 R 9 BDA9 R 1 BDA1 R 8 BDA8 R 0 BDA0 R R 30 BDA30 R 22 BDA22 R 29 BDA29 R 21 BDA21 R 28 BDA28 R 20 BDA20 R 27 BDA27 R 19 BDA19 R 26 BDA26 R 18 BDA18 R 25 BDA25 R 17 BDA17 R 24 BDA24 R 16 BDA16 R
Branch Destination Registers (BRDR)
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
Initial value: Undefined Undefined Undefined Undefined Undefined Undefined Undefined Undefined
The branch destination registers (BRDR) comprise a set of four 32-bit read-only registers. These registers store the branch destination fetch addresses used when performing a PC trace. The BRDR registers form a FIFO (first-in first-out) queue for PC trace use. The queue is shifted at each branch. The BRDR registers are not initialized by a reset.
Rev. 2.00 Mar 09, 2006 page 235 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.3
6.3.1
Operation
User Break Operation Sequence
The sequence of operations from setting of break conditions to user break interrupt exception handling is described below. 1. Set the break address in the break address register (BARA/BARB/BARC/BARD), the bits to be masked in the break address mask register (BAMRA/BAMRB/BAMRC/BAMRD), the break bits in the break data register (BDRC/BDRD), and the data to be masked in the break data mask register (BDMRC/BDMRD). Set the break bus conditions in the break bus cycle register (BBRA/BBRB/BBRC/BBRD). Make three settings--CPU cycle/on-chip DMAC cycle select, instruction fetch/data access select, and read/write select--for each of BBRA, BBRB, BBRC, and BBRD. A user break interrupt will not be generated for a channel for which any one of these settings is 00. Set the respective conditions in the corresponding BRCR register bits. 2. When a set condition is satisfied, the UBC sends a user break interrupt request to the interrupt controller (INTC). The CPU condition match flag (CMFCA/CMFCB/CMFCC/CMFCD) and DMAC condition match flag (CMFPA/CMFPB/CMFPC/CMFPD) is also set for the matched condition for the respective channel. 3. The INTC determines the priority of the user break interrupt. As the priority level of a user break interrupt is 15, the interrupt is accepted if the level set in the interrupt mask bits (I3 to I0) in the status register (SR) is 14 or less. If the level set in bits I3 to I0 is 15, the user break interrupt is not accepted, but is held pending until it can be. For details of priority determination, see section 5, Interrupt Controller (INTC). 4. If the user break interrupt is accepted after its priority is determined, the CPU begins user break interrupt exception handling. 5. Whether a set condition is matched or not can be ascertained from the respective condition match flag (CMFCA, CMFPA, CMFCB, CMFPB, CMFCC, CMFPC, CMFCD, or CMFPD). These flags are set by a match with the set condition, but are not reset. Therefore, if the setting of a particular flag is to be checked again, the flag must be cleared by writing 0. When an execution-times break is specified for channel C or D, the CMFCC, CMFPC, CMFCD, or CMFPD flag is set when the number of executions matches the number of executions specified by BETRC or BETRD.
Rev. 2.00 Mar 09, 2006 page 236 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.3.2
Instruction Fetch Cycle Break
1. If a CPU/instruction fetch/read/word setting is made in the break bus cycle register (BBRA, BBRB, BBRC, or BBRD), a CPU instruction fetch cycle can be selected as a break condition. In this case, it is possible to specify whether the break is to be effected before or after execution of the relevant instruction by means of the PCBA/PCBB/PCBC/PCBD bit in the break control register (BRCR). 2. In the case of an instruction for which pre-execution is set as the break condition, the break is performed when it has been confirmed that the instruction has been fetched and is to be executed. Consequently, a break cannot be set for an overrun-fetched instruction (an instruction fetched but not executed in the event of a branch or interrupt transition). If a break is set for the delay slot of a delayed branch instruction, or for the instruction following an instruction for which interrupts are prohibited, such as LCD, an interrupt is generated before execution of the next instruction at which interrupts are accepted. 3. With the post-execution condition, an interrupt is generated after execution of the instruction set as the break condition, and before execution of the following instruction. As in 2 above, a break cannot be set for an overrun-fetched instruction. If a break is set for a delayed branch instruction, or for an instruction for which interrupts are prohibited, such as LCD, an interrupt is generated before execution of the next instruction at which interrupts are accepted. 4. When an instruction fetch cycle is set for channel C or D, break data register C (BDRC) or break data register D (BDRD) is ignored. Therefore, break data need not be set for an instruction fetch cycle break. 5. When an instruction fetch cycle is set, the start address at which that instruction is located should be set for the break. A break will not occur if a different address is set. Also, a break will not occur if the address of the lower word of a 32-bit instruction is set.
Rev. 2.00 Mar 09, 2006 page 237 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.3.3
Data Access Cycle Break
1. Memory cycles for which a CPU data access break can be set are memory cycles due to instructions and stack operations and vector reads when exception handling is executed. A CPU data access break cannot be set for a vector fetch cycle of an external vector interrupt, for burst write of a synchronous DRAM, or for a dammy access cycle of a single read. 2. Table 6.2 shows the bits of the break address register and the address bus that are compared for each operand size to determine whether a break condition has been matched. Table 6.2
Access Size Longword Word Byte
Data Access Cycle Address and Operand Size Comparison Conditions
Compared Address Bits Bits 31 to 2 of break address register compared with bits 31 to 2 of address bus Bits 31 to 1 of break address register compared with bits 31 to 1 of address bus Bits 31 to 0 of break address register compared with bits 31 to 0 of address bus
This means, for example, that if address H'00001003 is set without specifying a size condition, bus cycles that satisfy the break conditions are as follows (assuming that all other conditions are satisfied): Longword access at address H'00001000 Word access at address H'00001002 Byte access at address H'00001003 3. When data value is included in break condition in channel C When the data value is included in the break conditions, specify longword, word, or byte as the operand size in break bus cycle register C (BBRC). When the data value is included in the break conditions, a break interrupt is generated on a match of the address condition and the data condition. When byte data is specified, set the same data in the two bytes comprising bits 15 to 8 and bits 7 to 0 in break data register C (BDRC) and break data mask register C (BDMRC). If word or byte is designated, bits 31 to 16 of BDRC and BDMRC are ignored. Similar conditions apply when the data value is included in the break conditions for channel D.
Rev. 2.00 Mar 09, 2006 page 238 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.3.4
Saved Program Counter (PC) Value
1. When instruction fetch (pre-instruction-execution) is set as break condition The program counter (PC) value saved to the stack in user break interrupt exception handling is the address of the instruction for which the break condition matched. In this case, the fetched instruction is not executed, a user break interrupt being generated prior to its execution. If a setting is made for an instruction following an instruction for which interrupts are prohibited, the break is effected before execution of the next instruction at which interrupts are accepted, so that the saved PC value is the address at which the break occurs. 2. When instruction fetch (post-instruction-execution) is set as break condition The program counter (PC) value saved to the stack in user break interrupt exception handling is the address of the next instruction to be executed after the instruction for which the break condition matched. In this case, the fetched instruction is executed, and a user break interrupt is generated before execution of the next instruction. However, if a setting is made for an instruction for which interrupts are prohibited, the break is effected before execution of the next instruction at which interrupts are accepted, so that the saved PC value is the address at which the break occurs. 3. When data access (CPU/on-chip DMAC) is set as break condition The value saved is the start address of the next instruction after the instruction for which execution has been completed when user break exception handling is initiated. When data access (CPU/on-chip DMAC) is set as a break condition, the point at which the break is to be made cannot be specified. A break is effected before execution of the instruction about to be fetched around the time of the break data access. 6.3.5 X Memory Bus or Y Memory Bus Cycle Break
A break condition for an X bus cycle or Y bus cycle can only be specified for channel C or D. When XYEC in BBRC or XYED in BBRD is set to 1, break addresses and break data on the X memory bus or Y memory bus are selected. Either the X memory bus or the Y memory bus must be selected with the XYSC bit in BBRC or the XYSD bit in BBRD; the X and Y memory buses cannot both be included in the break conditions at the same time. The break conditions are applied to X memory bus cycles or Y memory bus cycles by setting the CPU bus master, data access cycle, read or write access, and word operand size or no operand size specification. When an X memory address is selected as a break condition, specify the X memory address in the upper 16 bits of BARC and BAMRC or BARD and BAMRD; when a Y memory address is selected, specify the Y memory address in the lower 16 bits of BARC and BAMRC or BARD and BAMRD. The same method is used to specify X memory data or Y memory data for BDRC and BDMRC or BDRD and BMRD.
Rev. 2.00 Mar 09, 2006 page 239 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
6.3.6
Sequential Break
Channel C to Channel D: When SEQ1 in BRCR is set to 0 and SEQ0 is set to 1, a sequential break occurs when the conditions are met for channel C and then channel D, in that order. This causes the BRCR condition match flag for each channel to be set to 1. If the break conditions for channels C and D are met at the same time, and the conditions had not already been met for channel C, the conditions are considered to be met for channel C alone, in the same manner as if the conditions were met for channel C first. Also, if the conditions for channel C have already been met when the break conditions for channels C and D are met at the same time, the conditions for channel D are considered to be met and a break occurs. Channel B to Channel C to Channel D: When SEQ1 in BRCR is set to 1 and SEQ0 is set to 0, a sequential break occurs when the conditions are met for channel B, channel C, and then channel D, in that order. This causes the BRCR condition match flag for each channel to be set to 1. If the break conditions for channels B and C are met at the same time, and the conditions had not already been met for channel B, the conditions are considered to be met for channel B. Also, if the conditions for channel B have already been met when the break conditions for channels B and C are met at the same time, the conditions for channel C are considered to be met. If the break conditions for channels C and D are met at the same time, and the conditions had not already been met for channel C, the conditions are considered to be met for channel C. Also, if the conditions for channel C have already been met when the break conditions for channels C and D are met at the same time, the conditions for channel D are considered to be met and a break occurs. Channel A to Channel B to Channel C to Channel D: When SEQ1 in BRCR is set to 1 and SEQ0 is set to 1, a sequential break occurs when the conditions are met for channel A, channel B, channel C, and then channel D, in that order. This causes the BRCR condition match flag for each channel to be set to 1. If the break conditions for channels A and B are met at the same time, and the conditions had not already been met for channel A, the conditions are considered to be met for channel A. Also, if the conditions for channel A have already been met when the break conditions for channels A and B are met at the same time, the conditions for channel B are considered to be met. If the break conditions for channels B and C are met at the same time, and the conditions had not already been met for channel B, the conditions are considered to be met for channel B. Also, if the conditions for channel B have already been met when the break conditions for channels B and C are met at the same time, the conditions for channel C are considered to be met.
Rev. 2.00 Mar 09, 2006 page 240 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
If the break conditions for channels C and D are met at the same time, and the conditions had not already been met for channel C, the conditions are considered to be met for channel C. Also, if the conditions for channel C have already been met when the break conditions for channels C and D are met at the same time, the conditions for channel D are considered to be met and a break occurs. However, if bus cycle conditions match for two of the channels included in the sequential conditions, and if the bus cycle conditions (which is the first break condition for the adjacent channel) have been specified as pre-execution break (PCB bit of BRCR set to 0) and (using the break bus cycle register) instruction fetch, a break occurs and the BRCR condition match flag is set to 1. Bus X or bus Y may be selected in the sequential break setting, and it is also possible to set the number of executions as a brake condition. For example, if an execution-times break is set for channels C and D, a user break interrupt will be issued if, after the execution-times set for channel set in BETRC has occurred, the execution-times condition set in BETRD for channel D is met. 6.3.7 PC Traces
1. A PC trace is started by setting the PC trace enable bit (PCTE) to 1 in BRCR. When a branch (branch instruction, repeat, or interrupt) occurs the address that enables the branch source address to be calculated and the branch destination address are stored in the branch source register (BRSR) and branch destination register (BRDR). The address stored in BRDR is the branch destination instruction fetch address. The address stored in BRSR is the last instruction fetch address prior to the branch. A pointer indicating the relationship to the instruction executed immediately before the branch is stored in the branch flag register (BRFR). 2. The address of the instruction executed immediately before the branch occurred can be calculated from the address stored in BRSR and the pointer stored in BRFR. Designating the address stored in BRSR as BSA, the pointer stored in BRFR as PID, and the address prior to the branch as IA, then IA is found from the following equation: IA = BSA - 2 x PID Caution is necessary if an interrupt (branch) occurs before the instruction at the branch destination is executed. In the case illustrated in figure 6.2., the address of instruction "Exec", executed immediately before the branch, is calculated from the equation IA = BSA - 2 x PID. However, if branch "branch" is a delayed branch instruction with a delay slot and the branch destination is a 4n+2 address, branch destination address "Dest" specified by the branch instruction is stored directly in BRSR. In this case, therefore, equation IA = BSA - 2 x PID is not applied, and PID is invalid. BSA is at a 4n+2 boundary in this case only, categorized as shown in table 6.3.
Rev. 2.00 Mar 09, 2006 page 241 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Exec:
branch Dest
Dest:
instr;
Interrupt
Not executed
Int:
interrupt routine
Figure 6.2 When Interrupt Occurs before Branch Instruction Is Executed Table 6.3 BSA Values Stored in Exception Handling before Execution of Branch Destination Instruction
Branch Destination (Dest) 4n 4n + 2 No delay 4n or 4n + 2 BSA 4n 4n + 2 4n Branch Source Address Calculable by Means of BRSR and BRFR Exec = IA = BSA - 2 x PID Dest = BSA Exec = IA = BSA - 2 x PID
Branch Delay
If PID is an odd number, the value incremented by 2 indicates the instruction buffer, but the equations in the table do not take this into account. Therefore, the calculation can be performed using the values of BSA stored in BRSR and PID stored in BRFR. 3. The location indicated by the address before branch occurrence, IA, differs according to the kind of branch. a. Branch instruction: Branch instruction address b. Repeat loop: 2nd instruction from last in repeat loop Repeat_Start: inst (1); BRDR inst(2); : inst (n-1); Address calculated from BRSR and BRFR Repeat End: inst (n);
c. Interrupt: Instruction executed immediately before interrupt The address of the first instruction in the interrupt routine is stored in BRDR. In a repeat loop consisting of no more than three instructions, an instruction fetch cycle is not generated. As the branch destination address is unknown, a PC trace cannot be performed.
Rev. 2.00 Mar 09, 2006 page 242 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
4. BRSR, BRDR, and BRFR have a four-queue structure. When the stored address is read in a PC trace, the read is performed from the head of the queue. Reads should be performed in the order BRFR, BRSR, BRDR. After BRDR is read, the queue shifts by one. Use longword access to read BRSR and BRDR. 6.3.8 Examples of Use
CPU Instruction Fetch Cycle Break Condition Settings A. Register settings: BARA = H'00000404 / BAMRA = H'00000000 / BBRA = H'0054 BARB = H'00003080 / BAMRB = H'0000007F / BBRB = H'0054 BARC = H'00008010 / BAMRC = H'00000006 / BBRC = H'0054 BDRC = H'00000000 / BDMRC = H'00000000 BARD =H'0000FF04 / BAMRD = H'00000000 / BBRD = H'0054 BDRD = H'00000000 / BDMRD = H'00000000 BRCR = H'04000400 Set conditions: All channels independent Channel A: Address: H'00000404; address mask: H'00000000 Bus cycle: CPU, instruction fetch (post-execution), read (operand size not included in conditions) Channel B: Address: H'00003080; address mask: H'0000007F Bus cycle: CPU, instruction fetch (pre-execution), read (operand size not included in conditions) Channel C: Address: H'00008010; address mask: H'00000006 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (post-execution), read (operand size not included in conditions) Channel D: Address: H'0000FF04; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read (operand size not included in conditions) A user break interrupt is generated after execution of the instruction at address H'00000404, before execution of instructions at addresses H'00003080 to H'000030FF, after execution of instructions at addresses H'00008010 to H'00008016, or before execution of the instruction at address H'0000FF04.
Rev. 2.00 Mar 09, 2006 page 243 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
B. Register settings: BARA = H'00027128 / BAMRA = H'00000000 / BBRA = H'005A BARB = H'00031415 / BAMRB = H'00000000 / BBRB = H'0054 BARC = H'00037226 / BAMRC = H'00000000 / BBRC = H'0056 BDRC = H'00000000 / BDMRC = H'00000000 BARD = H'0003722E / BAMRD = H'00000000 / BBRD = H'0056 BDRD = H'00000000 / BDMRD = H'00000000 BRCR = H'00080000 Set conditions: Channels A and B independent, channel C channel D sequential mode Channel A: Address: H'00027128; address mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), write, word Channel B: Address: H'00031415; address mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read (operand size not included in conditions) Channel C: Address: H'00037226; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read, word Channel D: Address: H'0003722E; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read, word On channel A, a user break interrupt is not generated as an instruction fetch is not a write cycle. On channel B, a user break interrupt is not generated as an instruction fetch is performed on an even address. A user break interrupt is generated by a channel C and D sequential condition match before execution of the instruction at address H'0003722E following execution of the instruction at address H'00037226. C. Register settings: BBRA = H'0000 BBRB = H'0000 BARC = H'00037226 / BAMRC = H'00000000 / BBRC = H'005A BDRC = H'00000000 / BDMRC = H'00000000 BARD = H'0003722E / BAMRD = H'00000000 / BBRD = H'0056 BDRD = H'00000000 / BDMRD = H'00000000 BRCR = H'00080000
Rev. 2.00 Mar 09, 2006 page 244 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
Set conditions:
Channels A and B independent, channel C channel D sequential mode Channel A: Not used Channel B: Not used Channel C: Address: H'00037226; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), write, word Channel D: Address: H'0003722E; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read, word
As the channel C break condition is a write cycle, the condition is not matched, and as the sequential conditions are not satisfied, a user break interrupt is not generated. D. Register settings: BBRA = H'0000 BARB = H'00000500 / BAMRB = H'00000000 / BBRB = H'0057 BARC = H'00000A00 / BAMRC = H'00000000 / BBRC = H'0057 BDRC = H'00000000 / BDMRC = H'00000000 BARD = H'00001000 / BAMRD = H'00000000 / BBRD = H'0057 BDRD = H'00000000 / BDMRD = H'00000000 BRCR = H'00102020 / BETRC = H'0005 / BETRD = H'000A Channel A: Not used Channel B: Address: H'00000500; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read, word Channel C: Address: H'00000A00; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read, word Execution-times break enabled (5 times) Channel D: Address: H'00001000; address mask: H'00000000 Data: H'00000000; data mask: H'00000000 Bus cycle: CPU, instruction fetch (pre-execution), read, word Execution-times break enabled (10 times)
Rev. 2.00 Mar 09, 2006 page 245 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
After the instruction at address H'0000500 is executed, and the instruction at address H'00000A00 is executed five times, a user break interrupt is generated after the instruction at address H'00001000 has been executed nine times, but before it is executed a tenth time. CPU Data Access Cycle Break Condition Settings Register settings: BARA = H'00123456 / BAMRA = H'00000000 / BBRA = H'0064 BARB = H'01000000 / BAMRB = H'00000000 / BBRB = H'0066 BARC = H'000ABCDE / BAMRC = H'000000FF / BBRC = H'006A BDRC = H'0000A512 / BDMRC = H'00000000 BARD = H'1001E000 / BAMRD = H'FFFF0000 / BBRD = H'036A BDRD = H'00004567 / BDMRD = H'00000000 BRCR = H'00000808 Set conditions: All channels independent Channel A: Address: H'00123456; address mask: H'00000000 Bus cycle: CPU, data access, read (operand size not included in conditions) Channel B: Address: H'01000000; address mask: H'00000000 Bus cycle: CPU, data access, read, word Channel C: Address: H'000ABCDE; address mask: H'00000000 Data: H'0000A512; data mask: H'00000000 Bus cycle: CPU, data access, write, word Channel D: Y address: H'1001E000; address mask: H'FFFF0000 Data: H'00004567; data mask: H'00000000 Bus cycle: CPU, data access, write, word On channel A, a user break interrupt is generated by a longword read at address H'00123456, a word read at address H'00123456, or a byte read at address H'00123456. On channel B, a user break interrupt is generated by a word read at address H'01000000. On channel C, a user break interrupt is generated when H'A512 is written by word access to an address from H'000ABC00 to H'000ABCFE. On channel D, a user break interrupt is generated when H'4567 is written by word access to address H'1001E000 in Y memory space.
Rev. 2.00 Mar 09, 2006 page 246 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
DMA Data Access Cycle Break Condition Settings Register settings: BARA = H'00314156 / BAMRA = H'00000000 / BBRA = H'0094 BBRB = H'0000 BBRC = H'0000 BARD = H'00055555 / BAMRD = H'00000000 / BBRD = H'00A9 BDRD = H'00007878 / BDMRD = H'00000F0F BRCR = H'00000008 Set conditions: All channels independent Channel A: Address: H'00314156; address mask: H'00000000 Bus cycle: DMAC, instruction fetch, read (operand not included in conditions) Channel B: Not used Channel C: Not used Channel D: Address: H'00055555; address mask: H'00000000 Data: H'00007878; data mask: H'00000F0F Bus cycle: DMAC, data access, write, byte On channel A, a user break interrupt is not generated as an instruction fetch is not performed in a DMAC cycle. On channel D, a user break interrupt is generated when the DMAC writes H'7* (*: Don't care) is written by byte access to address H'00055555. 6.3.9 Usage Notes
1. UBC registers can be read and written to only by the CPU. 2. Note the following concerning sequential break specifications: a. As the CPU has a pipeline structure, the order of instruction fetch cycles and memory cycles is determined by the pipeline. Therefore, a break will occur if channel condition matches in the bus cycle order satisfy the sequential condition. b. If, of the channels included in a sequential condition, the channel bus cycle conditions constituting the first break conditions of adjacent channels are specified as a pre-execution break (PCB bit cleared to 0 in BRCR) and an instruction fetch (designated by the break bus cycle register), note that when the bus cycle conditions for the two channels are matched simultaneously, a break is effected and the BRCR condition match flags are set to 1.
Rev. 2.00 Mar 09, 2006 page 247 of 906 REJ09B0292-0200
Section 6 User Break Controller (UBC)
3. When changing a register setting, the written value normally becomes effective in three cycles. In an on-chip memory fetch, two instructions are fetched simultaneously. If the fetch of the second instruction has been set as a break condition, even if the break condition is changed by modifying the relevant UBC registers immediately after the fetch of the first instruction, a user break interrupt will still be generated prior to the second instruction. To fix a timing at which the setting is definitely changed, the last register value written should be read with a dummy access. The changed setting will be valid from this point on. 4. If a user break interrupt is generated by an instruction fetch condition match, and the condition is matched again in the UBC during execution of the exception service routine, exception handling for that break will be executed when the interrupt request mask value in SR becomes 14 or below. Therefore, when masking addresses and setting an instruction fetch/postexecution condition to perform step-execution, ensure that an address match does not occur during execution of the UBC's exception service routine. 5. Note the following when specifying an instruction in a repeat loop that includes a repeat instruction as a break condition. When an instruction in a repeat loop is specified as a break condition: a. A break will not occur during execution of a repeat loop comprising no more than three instructions. b. When an execution-times break is set, an instruction fetch from memory will not occur during execution of a repeat loop comprising no more than three instructions. Consequently, the value in the break execution times register (BETRC or BETRD) will not be decremented. 6. Do not execute a branch instruction immediately after reading a PC trace register (BRFR, BRSR, or BRDR). 7. If CPU and DMAC bus cycles are set as break conditions when an execution-times break has been set, BETR will only be decremented once even if CPU and DMAC condition matches occur simultaneously. 8. UBC and H-UDI are used by the emulator. For this reason, the operation of UBC and H-UDI may differ in some cases between the emulator and the actual device. If UBC and H-UDI are not used on the user's system, no register setting should be performed.
Rev. 2.00 Mar 09, 2006 page 248 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Section 7 Bus State Controller (BSC)
7.1 Overview
The bus state controller (BSC) manages the address spaces and outputs control signals to allow optimum memory accesses to the five spaces. This enables memories like DRAM, and SDRAM, and peripheral chips, to be linked directly. 7.1.1 Features
The BSC has the following features: * Address space is managed as five spaces Maximum linear 32 Mbytes for each of the address spaces CS0 to CS4 Memory type (DRAM, synchronous DRAM, burst ROM, etc.) can be specified for each space. Bus width (8, 16, or 32 bits) can be selected for each space. Wait state insertion can be controlled for each space. Control signals are output for each space. * Cache Cache area and cache-through area can be selected by access address. In cache access, in the event of a cache access miss 16 bytes are read consecutively in 4byte units to fill the cache. Write-through mode/write-back mode can be selected for writes. In cache-through access, access is performed according to access size. * Refresh Supports CAS-before-RAS refresh (auto-refresh) and self-refresh. Refresh interval can be set by the refresh counter and clock selection. Intensive refreshing by means of refresh count setting (1, 2, 4, 6, or 8) * Direct interface to DRAM Row/column address multiplex output. Burst transfer during reads, fast page mode for consecutive accesses. TP cycle generation to secure RAS precharge time. EDO mode * Direct interface to synchronous DRAM Row/column address multiplex output.
Rev. 2.00 Mar 09, 2006 page 249 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Selection of burst read, single write mode or burst read, burst write mode Bank active mode * Bus arbitration All resources are shared with the CPU, and use of the bus is granted on reception of a bus release request from off-chip. * Refresh counter can be used as an interval timer Interrupt request generation on compare match (CMI interrupt request signal).
Rev. 2.00 Mar 09, 2006 page 250 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.1.2
Block Diagram
Figure 7.1 shows a block diagram of the BSC.
Bus interface
WCR1 Wait control unit WCR2 WCR3 BCR1 CS4-CS0 Area control unit BCR2 BCR3 STATS1, 0 BS RD CAS RAS RD/WR WE3-WE0 CKE IVECF REFOUT CMI interrupt request RTCOR
Peripheral bus
WAIT
MCR RTCSR Memory control unit RTCNT Comparator
Interrupt controller
Module bus
BSC
WCR: Wait control register BCR: Bus control register MCR: Individual memory control register
RTCSR: Refresh timer control/status register RTCNT: Refresh timer counter RTCOR: Refresh time constant register
Figure 7.1 BSC Block Diagram
Rev. 2.00 Mar 09, 2006 page 251 of 906 REJ09B0292-0200
Internal bus
Section 7 Bus State Controller (BSC)
7.1.3
Pin Configuration
Table 7.1 shows the BSC pin configuration. Table 7.1
Signal A24-A0 D31-D0
Pin Configuration
I/O O I/O With Bus Released Hi-Z Hi-Z Description Address bus. 32 Mbytes of memory space can be specified with 25 bits 32-bit data bus. When reading or writing a 16-bit width area, use D15-D0; when reading or writing a 8-bit width area, use D7-D0. With 8-bit accesses that read or write a 32-bit width area, input and output the data via the byte position determined by the lower address bits of the 32-bit bus Indicates start of bus cycle or monitor. With the basic interface (device interfaces except for DRAM, synchronous DRAM), signal is asserted for a single clock cycle simultaneous with address output. The start of the bus cycle can be determined by this signal Chip select. CS3 is not asserted when the CS3 space is DRAM space Read/write signal. Signal that indicates access cycle direction (read/write). Connected to WE pin when DRAM/synchronous DRAM is connected RAS pin for DRAM/synchronous DRAM Open when using DRAM Connected to OE pin when using EDO RAM Connected to CAS pin when using synchronous DRAM
BS
O
Hi-Z
CS0-CS4 O RD/WR O
Hi-Z Hi-Z
RAS CAS/OE
O O
Hi-Z Hi-Z
RD
O
Hi-Z
Read pulse signal (read data output enable signal). Normally, connected to the device's OE pin; when there is an external data buffer, the read cycle data can only be output when this signal is low Hardware wait input Bus release request input Bus grant output Synchronous DRAM clock enable control. Signal for supporting synchronous DRAM self-refresh Interrupt vector fetch DMA request 0 DMA acknowledge 0
WAIT BRLS BGR CKE IVECF DREQ0 DACK0
I I O O O I O
Don't care I O O O I O
Rev. 2.00 Mar 09, 2006 page 252 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC) With Bus Released I O O Hi-Z
Signal DREQ1 DACK1 REFOUT DQMUU/ WE3 DQMUL/ WE2 DQMLU/ WE1 DQMLL/ WE0 CAS3 CAS2 CAS1 CAS0
I/O I O O O
Description DMA request 1 DMA acknowledge 1 Refresh execution request output when bus is released When synchronous DRAM is used, connected to DQM pin for the most significant byte (D31-D24). For ordinary space, indicates writing to the most significant byte When synchronous DRAM is used, connected to DQM pin for the second byte (D23-D16). For ordinary space, indicates writing to the second byte When synchronous DRAM is used, connected to DQM pin for the third byte (D15-D8). For ordinary space, indicates writing to the third byte When synchronous DRAM is used, connected to DQM pin for the least significant byte (D7-D0). For ordinary space, indicates writing to the least significant byte When DRAM is used, connected to CAS pin for the most significant byte (D31-D24) When DRAM is used, connected to CAS pin for the second byte (D23-D16) When DRAM is used, connected to CAS pin for the third byte (D15- D8) When DRAM is used, connected to CAS pin for the least significant byte (D7-D0) Bus master identification 00: CPU 01: DMAC 10: E-DMAC 11: Other Signal used in combination with WAIT signal to place bus and strobe signals in the high-impedance state without the ending bus cycle.
O
Hi-Z
O
Hi-Z
O
Hi-Z
O O O O
Hi-Z Hi-Z Hi-Z Hi-Z O
STATS0, 1 O
BUSHIZ
I
I
Note: Hi-Z: High impedance
Rev. 2.00 Mar 09, 2006 page 253 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.1.4
Register Configuration
The BSC has ten registers. These registers are used to control wait states, bus width, interfaces with memories like DRAM, synchronous DRAM, and burst ROM, and DRAM and synchronous DRAM refreshing. The register configurations are shown in table 7.2. The size of the registers themselves is 16 bits. If read as 32 bits, the upper 16 bits are 0. In order to prevent writing mistakes, 32-bit writes are accepted only when the value of the upper 16 bits of the write data is H'A55A; no other writes are performed. Initialize the reserved bits. Initialization Procedure: Do not access a space other than CS0 until the settings for the interface to memory are completed. Table 7.2
Name Bus control register 1 Bus control register 2 Bus control register 3 Wait control register 1 Wait control register 2 Wait control register 3 Individual memory control register Refresh timer counter Refresh time constant register
Register Configuration
Abbr. BCR1 BCR2 BCR3 WCR1 WCR2 WCR3 MCR RTCNT RTCOR R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Initial Value Address* H'03F0 H'00FC H'0F00 H'AAFF H'000B H'0000 H'0000 H'0000 H'0000 H'0000
1
Access Size
2
H'FFFFFFE0 16* , 32 2 H'FFFFFFE4 16* , 32 H'FFFFFFFC 16* , 32 2 H'FFFFFFE8 16* , 32
2
H'FFFFFFC0 16* , 32 2 H'FFFFFFC4 16* , 32
2
Refresh timer control/status register RTCSR
H'FFFFFFEC 16* , 32 2 H'FFFFFFF0 16* , 32
2
H'FFFFFFF4 16* , 32 2 H'FFFFFFF8 16* , 32
2
Notes: 1. This address is for 32-bit accesses; for 16-bit accesses add 2. 2. 16-bit access is for read only.
Rev. 2.00 Mar 09, 2006 page 254 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.1.5
Address Map
The address map, which has a memory space of 320 Mbytes, is divided into five spaces. The types and data width of devices that can be connected are specified for each space. The overall space address map is shown in table 7.3. Since the spaces of the cache area and the cache-through area are actually the same, and the maximum memory space that can be connected is 160 Mbytes. This means that when address H'20000000 is accessed in a program, the data accessed is actually in H'00000000. The chip has 16-kbyte RAM as on-chip memory. The on-chip RAM is divided into an X area and a Y area, which can be accessed in parallel with the DSP instruction. See the SH-1/SH-2/SH-DSP Programming Manual for more information. There are several spaces for cache control. These include the associative purge space for cache purges, address array read/write space for reading and writing addresses (address tags), and data array read/write space for forced reads and writes of data arrays. Table 7.3
Address H'00000000-H'01FFFFFF H'02000000-H'03FFFFFF H'04000000-H'05FFFFFF H'06000000-H'07FFFFFF
Address Map
Space CS0 space, cache area CS1 space, cache area CS2 space, cache area CS3 space, cache area Memory Ordinary space or burst ROM Ordinary space Ordinary space or 2 synchronous DRAM* Ordinary space, 2 synchronous DRAM* , or DRAM Ordinary space (I/O device) Size 32 Mbytes 32 Mbytes 32 Mbytes 32 Mbytes
H'08000000-H'09FFFFFF
CS4 space, cache area
1
32 Mbytes
H'0A000000-H'0FFFFFFF Reserved* 1 H'10000000-H'1000DFFF Reserved* H'1000E000-H'1000EFFF H'1000F000-H'1001DFFF H'1001E000-H'1001EFFF H'1001F000-H'1FFFFFFF H'20000000-H'21FFFFFF H'22000000-H'23FFFFFF On-chip X RAM area 1 Reserved* On-chip Y RAM area 1 Reserved* CS0 space, cache-through area CS1 space, cache-through area Ordinary space or burst ROM Ordinary space 4 kbytes 4 kbytes 32 Mbytes 32 Mbytes
Rev. 2.00 Mar 09, 2006 page 255 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC) Address H'24000000-H'25FFFFFF H'26000000-H'27FFFFFF Space CS2 space, cache-through area CS3 space, cache-through area Memory Ordinary space or 2 synchronous DRAM* Ordinary space, 2 synchronous DRAM* , or DRAM Ordinary space (I/O device) Size 32 Mbytes 32 Mbytes
H'28000000-H'29FFFFFF
CS4 space, cache-through area 1 H'2A000000-H'3FFFFFFF Reserved* H'40000000-H'49FFFFFF Associative purge space 1 H'4A000000-H'5FFFFFFF Reserved* H'60000000-H'7FFFFFFF Address array, read/write space 1 H'80000000-H'BFFFFFFF Reserved* H'C0000000-H'C0000FFF Data array, read/write space 1 H'C0001000-H'DFFFFFFF Reserved* H'E0000000-H'FFFEFFFF Reserved*
1
32 Mbytes
160 Mbytes 512 Mbytes
4 kbytes
H'FFFF0000-H'FFFF0FFF For setting synchronous DRAM mode 1 H'FFFF1000-H'FFFF7FFF Reserved* H'FFFF8000-H'FFFF8FFF For setting synchronous DRAM mode 1 H'FFFFC000-H'FFFFBFFF Reserved* H'FFFFFC00-H'FFFFFFFF On-chip peripheral modules
4 kbytes
4 kbytes
Notes: 1. Do not access reserved spaces, as operation cannot be guaranteed. 2. Bank-active mode is not supported for CS2 space synchronous DRAM access; autoprecharge mode is always used. Bank-active mode is supported for CS3 space synchronous DRAM access.
Rev. 2.00 Mar 09, 2006 page 256 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.2
7.2.1
Register Descriptions
Bus Control Register 1 (BCR1)
Bit: 15 -- Initial value: R/W: Bit: 0 R 7 A1LW1 Initial value: R/W: 1 R/W 14 A4LW1 0 R/W 6 A1LW0 1 R/W 13 A4LW0 0 R/W 5 A0LW1 1 R/W 12 A2EN DIAN 0 R/W 4 A0LW0 1 R/W 11 BST ROM 0 R/W 3 A4EN DIAN 0 R/W 10 -- 0 R 2 9 8
AHLW1 AHLW0 1 R/W 1 1 R/W 0
DRAM2 DRAM1 DRAM0 0 R/W 0 R/W 0 R/W
Initialize the ENDIAN, BSTROM, PSHR, and DRAM2-DRAM0 bits after a power-on reset, and do not change their values thereafter. To change other bits by writing to them, write the same value as they are initialized to. Do not access any space other than CS0 until the register initialization ends. Bit 15--Reserved: This bit is always read as 0. The write value should always be 0. Bits 14 and 13--Long Wait Specification for Area 4 (A4LW1, A4LW0): From 3 to 14 wait cycles are inserted in CS4 space accesses when the wait control bits (W41, W40) in wait control register 2 (WCR2) are set as long wait (i.e., are set to 11) (see table 7.4). Bit 12--Endian Specification for Area 2 (A2ENDIAN): In big-endian format, the MSB of byte data is the lowest byte address and byte data goes in order toward the LSB. For little-endian format, the LSB of byte data is the lowest byte address and byte data goes in order toward the MSB. When this bit is 1, the data is rearranged into little-endian format before transfer when the CS2 space is read or written to. It is used when handling data with little-endian processors or running programs written with conscious use of little-endian format.
Bit 12: A2ENDIAN 0 1 Description Big-endian Little-endian (Initial value)
Rev. 2.00 Mar 09, 2006 page 257 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bit 11--Area 0 Burst ROM Enable (BSTROM)
Bit 11: BSTROM 0 1 Description Area 0 is accessed normally Area 0 is accessed as burst ROM (Initial value)
Bit 10--Reserved: This bit is always read as 0. The write value should always be 0. Bits 9 and 8--Long Wait Specification for Areas 2 and 3 (AHLW1, AHLW0): When the basic memory interface setting is made for CS2 and CS3, from 3 to 14 wait cycles are inserted in CS2 or CS3 accesses when the bits specifying the respective area waits in the wait control bits (W21, W20 or W31, W30) in wait control register 1 (WCR1) are set as long waits (i.e., are set to 11) (see table 7.4). Bits 7 and 6--Long Wait Specification for Area 1 (A1LW1, A1LW0): From 3 to 14 wait cycles are inserted in area 1 accesses when the wait control bits (W11, W10) in wait control register 1 (WCR1) are set as long wait (i.e., are set to 11) (see table 7.4). Bits 5 and 4--Long Wait Specification for Area 0 (A0LW1, A0LW0): When the basic memory interface setting is made for CS0, from 3 to 14 wait cycles are inserted in CS0 accesses when the wait control bits (W01, W00) in wait control register 1 (WCR1) are set as long wait (i.e., are set to 11) (see table 7.4). Bit 3--Endian Specification for Area 4 (A4ENDIAN): In big-endian mode, the most significant byte (MSB) is the lowest byte address, and byte data is aligned in order toward the least significant byte (LSB). In little-endian mode, the LSB is the lowest byte address, and byte data is aligned in order toward the MSB. When this bit is set to 1, data in read/write accesses to the CS4 space is rearranged into little endian order before being transferred. This is used for data exchange with a little-endian processor or when executing a program written with awareness of little-endian mode.
Bit 3: A4ENDIAN 0 1 Description Big endian Little endian (Initial value)
Rev. 2.00 Mar 09, 2006 page 258 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bits 2 to 0--Enable for DRAM and Other Memory (DRAM2-DRAM0)
DRAM2 0 DRAM1 0 DRAM0 0 1 1 1 0 1 0 1 0 1 0 1 Description CS2 and CS3 are ordinary spaces value) CS2 is ordinary space; CS3 is DRAM space Reserved (do not set) CS2 is synchronous DRAM space, CS3 is ordinary space CS2 and CS3 are synchronous DRAM spaces Reserved (do not set) Reserved (do not set) (Initial
CS2 is ordinary space; CS3 is synchronous DRAM space
Table 7.4
BCR3 AnLW2 0
Wait Values Corresponding to BCR1 and BCR3 Register Settings (All Spaces)
BCR1 AnLW1 0 1 AnLW0 0 1 0 1 0 1 1 0 1 Wait Value 3 cycles inserted 4 cycles inserted 5 cycles inserted 6 cycles inserted 8 cycles inserted 10 cycles inserted 12 cycles inserted 14 cycles inserted (Initial value)
1
0
Note: n = 0 to 4 AHLW2, AHLW1, and AHLW0 are common to CS2 and CS3.
Rev. 2.00 Mar 09, 2006 page 259 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.2.2
Bus Control Register 2 (BCR2)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 A3SZ1 1 R/W 14 -- 0 R 6 A3SZ0 1 R/W 13 -- 0 R 5 A2SZ1 1 R/W 12 -- 0 R 4 A2SZ0 1 R/W 11 -- 0 R 3 A1SZ1 1 R/W 10 -- 0 R 2 A1SZ0 1 R/W 9 A4SZ1 0 R/W 1 -- 0 R 8 A4SZ0 0 R/W 0 -- 0 R
Initialize BCR2 after a power-on reset and do not write to it thereafter. When writing to it, write the same values as those the bits are initialized to. Do not access any space other than CS0 until the register initialization ends. The CS0 space bus size specification is set with pins MD4 and MD3. See section 3.3, CS0 Space Bus Width of the CS0 Area, for details. Bits 15 to 10--Reserved: These bits are always read as 0. The write value should always be 0. Bits 9 and 8--Bus Size Specification for Area 4 (CS4) (A4SZ1, A4SZ0)
Bit 9: A4SZ1 0 1 Bit 8: A4SZ0 0 1 0 1 Description Longword (32-bit) size Byte (8-bit) size Word (16-bit) size Longword (32-bit) size (Initial value)
Bits 7 and 6--Bus Size Specification for Area 3 (CS3) (A3SZ1, A3SZ0). Effective only when ordinary space is set.
Bit 7: A3SZ1 0 1 Bit 6: A3SZ0 0 1 0 1 Description Reserved (do not set) Byte (8-bit) size Word (16-bit) size Longword (32-bit) size (Initial value)
Rev. 2.00 Mar 09, 2006 page 260 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bits 5 and 4--Bus Size Specification for Area 2 (CS2) (A2SZ1, A2SZ0): Effective only when ordinary space is set.
Bit 5: A2SZ1 0 1 Bit 4: A2SZ0 0 1 0 1 Description Reserved (do not set) Byte (8-bit) size Word (16-bit) size Longword (32-bit) size (Initial value)
Bits 3 and 2--Bus Size Specification for Area 1 (CS1) (A1SZ1, A1SZ0)
Bit 3: A1SZ1 0 1 Bit 2: A1SZ0 0 1 0 1 Description Reserved (do not set) Byte (8-bit) size Word (16-bit) size Longword (32-bit) size (Initial value)
Bits 1 and 0--Reserved: These bits are always read as 0. The write value should always be 0. 7.2.3 Bus Control Register 3 (BCR3)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 0 R/W 14 -- 0 R 6 0 R/W 13 -- 0 R 5 -- 0 R 12 -- 0 R 4 -- 0 R 11 A4LW2 1 R/W 3 -- 0 R 10 AHLW2 1 R/W 2 BASEL 0 R/W 9 A1LW2 1 R/W 1 EDO 0 R/W 8 A0LW2 1 R/W 0 BWE 0 R/W
DSWW1 DSWW0
Initialize the BASEL, EDO, and BWE bits after a power-on reset and do not write to them thereafter. To change other bits by writing to them, write the same value as they are initialized to. Do not access any space other than CS0 until the register initialization ends. Bits 15 to 12--Reserved bits: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 261 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bits 11 to 8--Long Wait Specification for Areas 0 to 4 (AnLW2): When the basic memory interface setting is made for CS n, from 3 to 14 wait cycles are inserted in CS n accesses, according to the combination with the long wait specification bits (AnLW1 and AnLW0) in BCR1, when the bits specifying the wait in the wait control register are set as long wait (i.e., are set to 11). For a basic description of long waits, see section 7.2.1, Bus Control Register 1 (BCR1). Bits 7 and 6--DMA Single-Write Wait (DSWW1, DSWW0): These bits determine the number of wait states inserted between DACK assertion and CASn assertion when writing to DRAM or EDO RAM in DMA single address mode.
Bit 7: DSWW1 0 1 Bit 6: DSWW0 0 1 0 1 Description 0 waits 1 wait 2 waits Reserved (do not set) (Initial value)
Bits 5 to 3--Reserved bits: These bits are always read as 0. The write value should always be 0. Bit 2--Number of Banks Specification when Using 64M Synchronous DRAM (BASEL): When 64M synchronous DRAM is specified by AMX2-AMX0 in MCR, the number of banks can be specified.
Bit 2: BASEL 0 1 Description 4 banks 2 banks (Initial value)
Bit 1--EDO Mode Specification (EDO): Enables EDO mode to be specified when DRAM is specified for CS3 space.
Bit 1: EDO 0 1 Description High-speed page mode EDO mode (Initial value)
Rev. 2.00 Mar 09, 2006 page 262 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bit 0--Synchronous DRAM Burst Write Specification (BWE): Enables burst write mode to be specified when synchronous DRAM is specified for CS2 or CS3 space.
Bit 0: BWE 0 1 Description Single write mode Burst write mode (Initial value)
7.2.4
Wait Control Register 1 (WCR1)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 IW31 1 R/W 7 W31 1 R/W 14 IW30 0 R/W 6 W30 1 R/W 13 IW21 1 R/W 5 W21 1 R/W 12 IW20 0 R/W 4 W20 1 R/W 11 IW11 1 R/W 3 W11 1 R/W 10 IW10 0 R/W 2 W10 1 R/W 9 IW01 1 R/W 1 W01 1 R/W 8 IW00 0 R/W 0 W00 1 R/W
Do not access a space other than CS0 until the settings for register initialization are completed. Bits 15 to 8--Idles between Cycles for Areas 3 to 0 (IW31-IW00): These bits specify idle cycles inserted between consecutive accesses to different CS spaces. Idles are used to prevent data conflict between ROM or the like, which is slow to turn the read buffer off, and fast memories and I/O interfaces. Even when access is to the same space, idle cycles must be inserted when a read access is followed immediately by a write access. The idle cycles to be inserted comply with the specification for the previously accessed space. The set values below show the minimum number of idle cycles; more cycles than indicated by the Idles between Cycles setting may actually be inserted.
IW31, IW21, IW11, IW01 0 1 IW30, IW20, IW10, IW00 0 1 0 1 Description No idle cycle One idle cycle inserted Two idle cycles inserted Four idle cycles inserted (Initial value)
Rev. 2.00 Mar 09, 2006 page 263 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bits 7 to 0--Wait Control for Areas 3 to 0 (W31-W00) * When the CSn space is set as ordinary space, the number of CSn space waits can be specified with Wn1 and Wn0.
W31, W21, W11, W01 0 1 W30, W20, W10, W00 0 1 0 1 Description External wait input disabled without wait External wait input enabled with one wait External wait input enabled with two waits Complies with the long wait specification of bus control register 1, 3 (BCR1, BCR3). External wait input is enabled (Initial value)
* When CS3 is DRAM, the number of CAS assert cycles is specified by wait control bits W31 and W30
Bit 7: W31 0 1 Bit 6: W30 0 1 0 1 Description 1 cycle 2 cycles 3 cycles Reserved (do not set)
When external wait mask bit A3WM in WCR2 is 0 and the number of CAS assert cycles is set to 2 or more, external wait input is enabled. * When CS2 or CS3 is synchronous DRAM, CAS latency is specified by wait control bits W31 and W30, and W21 and W20, respectively
W31, W21 0 1 W30, W20 0 1 0 1 Description 1 cycle 2 cycles 3 cycles 4 cycles (Initial value)
With synchronous DRAM, external wait input is ignored regardless of any setting.
Rev. 2.00 Mar 09, 2006 page 264 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.2.5
Wait Control Register 2 (WCR2)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 -- 0 R 14 0 R/W 6 -- 0 R 13 -- 0 R 5 -- 0 R 12 A4WM 0 R/W 4 -- 0 R 11 A3WM 0 R/W 3 IW41 1 R/W 10 A2WM 0 R/W 2 IW40 0 R/W 9 A1WM 0 R/W 1 W41 1 R/W 8 A0WM 0 R/W 0 W40 1 R/W
A4WD1 A4WD0
Bits 15 and 14--Number of External Waits Specification for Area 4 (A4WD1, A4WD0): These bits specify the number of cycles between acceptance of CS4 space external wait negation and RD or WEn negation.
Bit 15: A4WD1 0 1 Bit 14: A4WD0 0 1 0 1 Description 1 cycle 2 cycles 4 cycles Reserved (do not set) (Initial value)
Bit 13--Reserved bit. This bit is always read as 0. The write value should always be 0. Bits 12 to 8--External Wait Mask Specification for Areas 0 to 4 (A4WM-A0WM): These bits enable waits to be masked for CS spaces 0 to 4. When a value other than 00 is set in the wait control bits for CS spaces 0 to 4 (W41-W00), external wait input can be enabled, but the wait input can be masked by setting these bits to 1. With synchronous DRAM, external wait input is ignored regardless of the settings.
Rev. 2.00 Mar 09, 2006 page 265 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC) A4WM A3WM A2WM A1WM A0WM 0 W41 W31 W21 W11 W01 0 1 1 Don't care W40 W30 W20 W10 W00 0 1 0 1 Don't care
Description External wait input ignored External wait input enabled External wait input enabled External wait input enabled External wait input ignored (Initial value)
Bits 7 to 4--Reserved bits: These bits are always read as 0. The write value should always be 0. Bits 3 and 2--Idles between Cycles for Area 4 (IW41, IW40): These bits specify idle cycles inserted between cycles in CS4 in the same way as for CS 0 to 3. The set values below show the minimum number of idle cycles; more cycles than indicated by the Idles between Cycles setting may actually be inserted.
Bit 3: IW41 0 1 Bit 2: IW40 0 1 0 1 Description No idle cycle One idle cycle inserted Two idle cycles inserted Four idle cycles inserted (Initial value)
Bits 1 and 0--Wait Control for Area 4 (W41, W40): These bits specify waits for CS4 in the same way as for areas 0 to 3.
Bit 1: W41 0 1 Bit 0: W40 0 1 0 1 Description No wait. External wait input disabled without wait One wait. External wait input enabled with one wait Two waits. External wait input enabled with two waits Complies with the long wait specification of bus control registers 1 and 3 (BCR1, BCR3). External wait input is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 266 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.2.6
Wait Control Register 3 (WCR3)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 0 R/W 14 -- 0 R 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 -- 0 R 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
A4SW2 A4SW1 A4SW0
A4HW1 A4HW0
A3SHW1 A3SHW0 A2SHW1 A2SHW0 A1SHW1 A1SHW0 A0SHW1 A0SHW0
Bits 15 and 14--Reserved bits: These bits are always read as 0. The write value should always be 0. Bits 13 to 11--CS4 Address/CS4 to RD/WEn Assertion (A4SW2-A4SW0): These bits specify the number of cycles from address/CS4 output to RD/WEn assertion for the CS4 space.
Bit 13: A4SW2 0 Bit 12: A4SW1 0 1 1 0 1 Bit 11: A4SW0 0 1 0 1 0 1 0 1 Description 0.5 cycles 1.5 cycles 3.5 cycles 5.5 cycles 7.5 cycles Reserved (do not set) Reserved (do not set) Reserved (do not set) (Initial value)
Bit 10--Reserved bit: This bit is always read as 0. The write value should always be 0. Bits 9 and 8--Area 4 RD/WEn Negation to Address/CS4 Hold (A4HW1, A4HW0): These bits specify the number of cycles from RD/WEn negation to address/CS4 hold for the CS4 space.
Bit 9: A4HW1 0 1 Bit 8: A4HW0 0 1 0 1 Description 0.5 cycle, CS4 hold cycle = 0 cycles 1.5 cycle, CS4 hold cycle = 1 cycle 3.5 cycle, CS4 hold cycle = 3 cycles 5.5 cycle, CS4 hold cycle = 5 cycles Rev. 2.00 Mar 09, 2006 page 267 of 906 REJ09B0292-0200 (Initial value)
Section 7 Bus State Controller (BSC)
Bits 7 to 0--Area 3 to 0 CSn Assert Period Extension (A3SHW1-A0SHW0): These bits specify the number of cycles from address/CSn output to RD/WEn assertion and from RD/WEn negation to address/CSn hold for areas 3 to 0.
A3SHW1 A2SHW1 A1SHW1 A0SHW1 0 1 Note: * n = 0 to 3 A3SHW0 A2SHW0 A1SHW0 A0SHW0 0 1 0 1
Description 0.5 cycle, CSn* hold cycle = 0 cycles 1.5 cycle, CSn* hold cycle = 1 cycle 2.5 cycle, CSn* hold cycle = 2 cycles Reserved (do not set) (Initial value)
7.2.7
Individual Memory Control Register (MCR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 TRP0 0 R/W 7 AMX2 0 R/W 14 RCD0 0 R/W 6 SZ 0 R/W 13 TRWL0 0 R/W 5 AMX1 0 R/W 12 TRAS1 0 R/W 4 AMX0 0 R/W 11 TRAS0 0 R/W 3 RFSH 0 R/W 10 BE 0 R/W 2 RMODE 0 R/W 9 RASD 0 R/W 1 TRP1 0 R/W 8 TRWL1 0 R/W 0 RCD1 0 R/W
The TRP1-TRP0, RCD1-RCD0, TRWL1-TRWL0, TRAS1-TRAS0, BE, RASD, AMX2-AMX0 and SZ bits are initialized after a power-on reset. Do not write to them thereafter. When writing to them, write the same values as they are initialized to. Do not access CS2 or CS3 until register initialization is completed. Bits 1 and 15--RAS Precharge Time (TRP1, TRP0): When DRAM is connected, specifies the minimum number of cycles after RAS is negated before the next assert. When synchronous DRAM is connected, specifies the minimum number of cycles after precharge until a bank active command is output. See section 7.5, Synchronous DRAM Interface, for details.
Rev. 2.00 Mar 09, 2006 page 268 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
* For DRAM interface
Bit 1: TRP1 0 1 Bit 15: TRP0 0 1 0 1 Description 1 cycle 2 cycles Reserved (do not set) Reserved (do not set) (Initial value)
* For Synchronous DRAM interface
Bit 1: TRP1 0 1 Bit 15: TRP0 0 1 0 1 Description 1 cycle 2 cycles 3 cycles 4 cycles (Initial value)
Bits 0 and 14--RAS-CAS Delay (RCD1, RCD0): When DRAM is connected, specifies the number of cycles after RAS is asserted before CAS is asserted. When synchronous DRAM is connected, specifies the number of cycles after a bank active (ACTV) command is issued until a read or write command (READ, READA, WRIT, WRITA) is issued.
Bit 0: RCD1 0 1 Bit 14: RCD0 0 1 0 1 Description 1 cycle 2 cycles 3 cycles Reserved (do not set) (Initial value)
Bits 8 and 13--Write-Precharge Delay (TRWL1, TRWL0): When the synchronous DRAM is not in the bank active mode, this bit specifies the number of cycles after the write cycle before the start-up of the auto-precharge. Based on this number of cycles, the timing at which the next active command can be issued is calculated within the bus controller. In bank active mode, this bit specifies the number of cycles before the precharge command is issued after the write command is issued. This bit is ignored when memory other than synchronous DRAM is connected.
Bit 8: TRWL1 0 1 Bit 13: TRWL0 0 1 0 1 Description 1 cycle 2 cycles 3 cycles Reserved (do not set) Rev. 2.00 Mar 09, 2006 page 269 of 906 REJ09B0292-0200 (Initial value)
Section 7 Bus State Controller (BSC)
Bits 12 and 11--CAS-Before-RAS Refresh RAS Assert Time (TRAS1, TRAS0): These bits specify the RAS assertion width when DRAM is connected.
Bit 12: TRAS1 0 1 Bit 11: TRAS0 0 1 0 1 Description 2 cycles 3 cycles 4 cycles 5 cycles (Initial value)
After an auto-refresh command is issued, a bank active command is not issued for TRAS cycles, regardless of the TRP bit setting. For synchronous DRAM, there is no RAS assertion period, but there is a limit for the time from the issue of a refresh command until the next access. This value is set to observe this limit. Commands are not issued for TRAS cycles when self-refresh is cleared.
Bit 12: TRAS1 0 1 Bit 11: TRAS0 0 1 0 1 Description 3 cycles 4 cycles 6 cycles 9 cycles (Initial value)
Bit 10--Burst Enable (BE)
Bit 10: BE 0 1 Description Burst disabled Burst access conditions are as follows: * * Longword access, cache fill access, or DMAC 16-byte transfer, with 16-bit bus width Cache fill access or DMAC 16-byte transfer, with 32-bit bus width (Initial value) High-speed page mode during DRAM and ED0 interfacing is enabled.
During synchronous DRAM access, burst operation is always enabled regardless of this bit
Rev. 2.00 Mar 09, 2006 page 270 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bit 9--Bank Active Mode (RASD)
Bit 9: RASD 0 Description For DRAM, RAS is negated after access ends (normal operation) For synchronous DRAM, a read or write is performed using auto-precharge mode. The next access always starts with a bank active command (Initial value) 1 For DRAM, after access ends RAS down mode is entered in which RAS is left asserted. When using this mode with an external device connected which performs writes other than to DRAM, see section 7.6.5, Burst Access For synchronous DRAM, access ends in the bank active state. This is only valid for area 3. When area 2 is synchronous DRAM, the mode is always autoprecharge
Bits 7, 5, and 4--Address Multiplex (AMX2-AMX0) * For DRAM interface
Bit 7: AMX2 0 Bit 5: AMX1 0 1 1 0 1 Bit 4: AMX0 0 1 0 1 0 1 0 1 Description 8-bit column address DRAM 9-bit column address DRAM 10-bit column address DRAM 11-bit column address DRAM Reserved (do not set) Reserved (do not set) Reserved (do not set) Reserved (do not set)
Rev. 2.00 Mar 09, 2006 page 271 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
* For synchronous DRAM interface
Bit 7: AMX2 0 Bit 5: AMX1 0 Bit 4: AMX0 0 1 1 1 0 0 1 0 1 Description 16-Mbit DRAM (1 M x 16 bits), 2 64-Mbit DRAM (2 M x 32 bits)* 1 16-Mbit DRAM (2 M x 8 bits)* 16-Mbit DRAM (4 M x 4 bits)*
1
4-Mbit DRAM (256 k x 16 bits) 64-Mbit DRAM (4 M x 16 bits), 3 128-Mbit DRAM (4 M x 32 bits)* 1 64-Mbit DRAM (8 M x 8 bits)* , 14 128-Mbit DRAM (8 M x 16 bits)* * 14 256-Mbit DRAM (8 M x 32 bits)* * Reserved (do not set) 2-Mbit DRAM (128 k x 16 bits)
1
0 1
Notes: 1. Reserved. Do not set when SZ bit in MCR is 0 (16-bit bus width). 2. See sction 7.5.11 for the method of connection to a 64-Mbit DRAM with a 2 M x 32-bit configuration. 3. See figure 7.2 for the method of connection to a 128-Mbit DRAM with a 4 M x 32-bit configuration. 4. In the case of a 128-Mbit DRAM (8 M x 16-bit), connect to two 128 M bit DRAM 5. s (8 M x 16-bit) by 32-bit data width as Figure2. 5. See figure 7.4 for the method of connection to a 256-Mbit DRAM with an 8 M x 32-bit configuration.
Rev. 2.00 Mar 09, 2006 page 272 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
128 Mbit (1 Mword x 32 bit x 4 Bank) synchronous DRAM A15 A14 A13
... ... ... ...
Chip
BA1 BA0 A11 A0 CLK CKE CS RAS CAS WE I/O31
... ... ...
A2 CKIO CKE CSn RAS CAS RD/WR D31 D0 DQMUU/WE3 DQMUL/WE2 DQMLU/WE1 DQMLL/WE0
...
I/O0 DQMUU DQMUL DQMLU DQMLL
Figure 7.2 128 Mbit Synchronous DRAM (4 Mword x 32 bit) Connection Example
Rev. 2.00 Mar 09, 2006 page 273 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
128 Mbit (2 Mword x 16-bit x 4 bank) synchronous DRAM
A15 A14 A13
... ... ... ... ...
Chip
BA1 BA0 A11
... ...
A2 CKIO CKE CSn RAS CAS RD/WR D31
... ...
A0 CLK CKE CS RAS CAS WE I/O15
...
D16 DQMUU/WE3 DQMUL/WE2 D15
... ...
I/O0 DQMU DQML
D0 DQMLU/WE1 DQMLL/WE0
BA1 BA0 A11
...
A0 CLK CKE CS CAS WE I/O15
...
I/O0 DQMU DQML
Figure 7.3 128 Mbit Synchronous DRAM (8 Mword x 16 bit) Connection Example
Rev. 2.00 Mar 09, 2006 page 274 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Chip
256 Mbit (2 Mword x 32-bit x 4 Bank) synchronous DRAM A15 A14 A13 A2 CKIO CKE CSn RAS CAS RD/WR D31 BA1 BA0 A11 A0 CLK CKE CS RAS CAS WE I/O31 I/O0 DQMUU DQMUL DQMLU DQMLL
D0 DQMUU/WE3 DQMUL/WE2 DQMLU/WE1 DQMLL/WE0
Figure 7.4 256 Mbit Synchronous DRAM (8 Mword x 32 bit) Connection Example Bit 6--Memory Data Size (SZ): For synchronous DRAM and DRAM space, the data bus width of BCR2 is ignored in favor of the specification of this bit.
Bit 6: SZ 0 1 Description Word (16 bits) Longword (32 bits) (Initial value)
Bit 3--Refresh Control (RFSH): This bit determines whether or not the refresh operation of DRAM/synchronous DRAM is performed.
Bit 3: RFSH 0 1 Description No refresh Refresh (Initial value)
Bit 2--Refresh Mode (RMODE): When the RFSH bit is 1, this bit selects normal refresh or selfrefresh. When the RFSH bit is 0, do not set this bit to 1. When the RFSH bit is 1, self-refresh mode is entered immediately after the RMODE bit is set to 1. When the RFSH bit is 1 and this bit
Rev. 2.00 Mar 09, 2006 page 275 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
is 0, a CAS-before-RAS refresh or auto-refresh is performed at the interval set in the 8-bit interval timer. When a refresh request occurs during an external area access, the refresh is performed after the access cycle is completed. When set for self-refresh, self-refresh mode is entered immediately unless the chip is in the middle of a synchronous DRAM area access, in which case self-refresh mode is entered when the access ends. Refresh requests from the interval timer are ignored during self-refresh.
Bit 2: RMODE 0 1 Description Normal refresh Self-refresh (Initial value)
7.2.8
Refresh Timer Control/Status Register (RTCSR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 CMF 0 R/W 14 -- 0 R 6 CMIE 0 R/W 13 -- 0 R 5 CKS2 0 R/W 12 -- 0 R 4 CKS1 0 R/W 11 -- 0 R 3 CKS0 0 R/W 10 -- 0 R 2 RRC2 0 R/W 9 -- 0 R 1 RRC1 0 R/W 8 -- 0 R 0 RRC0 0 R/W
Bits 15 to 8--Reserved: These bits are always read as 0. The write value should always be 0. Bit 7--Compare Match Flag (CMF): This status flag, which indicates that the values of RTCNT and RTCOR match, is set/cleared under the following conditions:
Bit 7: CMF 0 1 Description [Clearing condition] After RTCSR is read when CMF is 1, 0 is written in CMF [Setting condition] RTCNT = RTCOR
Rev. 2.00 Mar 09, 2006 page 276 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bit 6--Compare Match Interrupt Enable (CMIE): Enables or disables an interrupt request caused by the CMF bit of RTCSR when CMF is set to 1.
Bit 6: CMIE 0 1 Description Interrupt request caused by CMF is disabled Interrupt request caused by CMF is enabled (Initial value)
Bits 5 to 3--Clock Select Bits (CKS2-CKS0)
Bit 5: CKS2 0 Bit 4: CKS1 0 1 1 0 1 Bit 3: CKS0 0 1 0 1 0 1 0 1 Description Count-up disabled P/4 P/16 P/64 P/256 P/1024 P/2048 P/4096 (Initial value)
Bits 2 to 0--Refresh Count (RRC2-RRC0): These bits specify the number of consecutive refreshes to be performed when the refresh timer counter (RTCNT) and refresh time constant register (RTCOR) values match and a refresh request is issued.
Bit 2: RRC2 0 Bit 1: RRC1 0 1 1 0 1 Bit 0: RRC0 0 1 0 1 0 1 0 1 Description 1 refresh 2 refreshes 4 refreshes 6 refreshes 8 refreshes Reserved (do not set) Reserved (do not set) Reserved (do not set) (Initial value)
Rev. 2.00 Mar 09, 2006 page 277 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.2.9
Refresh Timer Counter (RTCNT)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 0 R/W 14 -- 0 R 6 0 R/W 13 -- 0 R 5 0 R/W 12 -- 0 R 4 0 R/W 11 -- 0 R 3 0 R/W 10 -- 0 R 2 0 R/W 9 -- 0 R 1 0 R/W 8 -- 0 R 0 0 R/W
The 8-bit counter RTCNT counts up with input clocks. The clock select bit of RTCSR selects an input clock. RTCNT values can always be read/written by the CPU. When RTCNT matches RTCOR, RTCNT is cleared. Returns to 0 after it counts up to 255. Bits 15 to 8--Reserved: These bits are always read as 0. The write value should always be 0. 7.2.10 Refresh Time Constant Register (RTCOR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 0 R/W 14 -- 0 R 6 0 R/W 13 -- 0 R 5 0 R/W 12 -- 0 R 4 0 R/W 11 -- 0 R 3 0 R/W 10 -- 0 R 2 0 R/W 9 -- 0 R 1 0 R/W 8 -- 0 R 0 0 R/W
RTCOR is an 8-bit read/write register. The values of RTCOR and RTCNT are constantly compared. When the values correspond, the compare match flag (CMF) in RTCSR is set and RTCNT is cleared to 0. When the refresh bit (RFSH) in the individual memory control register (MCR) is set to 1, a refresh request signal occurs. The refresh request signal is held until refresh operation is actually performed. If the refresh request is not processed before the next match, the previous request becomes ineffective.
Rev. 2.00 Mar 09, 2006 page 278 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
When the CMIE bit in RTCSR is set to 1, an interrupt request is sent to the controller by this match signal. The interrupt request is output continuously until the CMF bit in RTCSR is cleared. When the CMF bit clears, it only affects the interrupt; the refresh request is not cleared by this operation. When a refresh is performed and refresh requests are counted using interrupts, a refresh can be set simultaneously with the interval timer interrupt. Bits 15 to 8--Reserved: These bits are always read as 0. The write value should always be 0.
7.3
7.3.1
Access Size and Data Alignment
Connection to Ordinary Devices
Byte, word, and longword are supported as access units. Data is aligned based on the data width of the device. Therefore, reading longword data from a byte-width device requires four read operations. The bus state controller automatically converts data alignment and data length between interfaces. An 8-bit, 16-bit, or 32-bit external device data width can be connected by using the mode pins for the CS0 space, or by setting BCR2 for the CS1-CS4 spaces. However, the data width of devices connected to the respective spaces is specified statically, and the data width cannot be changed for each access cycle. Figures 7.5 to 7.7 show the relationship between device data widths and access units.
32-bit external device (ordinary) A24-A0 000000 000001 000002 000003 000000 000002 000000 D31 7 0 7 0 7 15 31 8 24 7 23 0 15 16 15 87 87 0 0 0 7 0 D23 D15 D7 D0 Data input/output pin Byte read/write of address 0 Byte read/write of address 1 Byte read/write of address 2 Byte read/write of address 3 Word read/write of address 0 Word read/write of address 2 Longword read/write of address 0
Figure 7.5 32-Bit External Devices and Their Access Units
Rev. 2.00 Mar 09, 2006 page 279 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
16-bit external device (ordinary) A24-A0 000000 000001 000002 000003 000000 000002 000000 000002 D15 7 7 15 15 31 15 0 7 0 7 0 0 0 16 0 0 D7 D0 Data input/output pin Byte read/write of address 0 Byte read/write of address 1 Byte read/write of address 2 Byte read/write of address 3 Word read/write of address 0 Word read/write of address 2 Longword read/write of address 0
Figure 7.6 16-Bit External Devices and Their Access Units
8-bit external device (ordinary) A24-A0 000000 000001 000002 000003 000000 000001 000002 000003 000000 000001 000002 000003 D7 7 7 7 7 15 7 15 7 31 23 15 7 D0 0 0 0 0 8 0 8 0 24 16 8 0 Data input/output pin Byte read/write of address 0 Byte read/write of address 1 Byte read/write of address 2 Byte read/write of address 3 Word read/write of address 0 Word read/write of address 2
Longword read/write of address 0
Figure 7.7 8-Bit External Devices and Their Access Units 7.3.2 Connection to Little-Endian Devices
The chip provides a conversion function in CS2, CS4 space for connection to and to maintain data compatibility with devices that use little-endian format (in which the LSB is the 0 position in the byte data lineup). When the endian specification bit of BCR1 is set to 1, CS2, CS4 space is littleendian. The relationship between device data width and access unit for little-endian format is shown in figures 7.8, 7.9, and 7.10. When sharing memory or the like with a little-endian bus master, the SH7616 connects D31-D24 to the least significant byte (LSB) of the other bus master and D7-D0 to the most significant byte (MSB), when the bus width is 32 bits. When the width is
Rev. 2.00 Mar 09, 2006 page 280 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
16 bits, the SH7616 connects D15-D8 to the least significant byte of the other bus master and D7- D0 to the most significant byte. Only data conversion is supported by this function. For this reason, be careful not to place program code or constants in the CS2, CS4 space. When this function is used, make sure that the access unit is the same for writing and reading. For example, data written by longword access should be read by longword access. If the read access unit is different from the write access unit, an incorrect value will be read.
32-bit external device (little-endian) A24-A0 000000 000001 000002 000003 000000 000002 000000 D31 7 0 7 0 7 7 7 0 15 0 15 8 8 7 23 0 15 16 31 8 24 0 7 0 D23 D15 D7 D0 Data input/output pin Byte read/write of address 0 Byte read/write of address 1 Byte read/write of address 2 Byte read/write of address 3 Word read/write of address 0 Word read/write of address 2 Longword read/write of address 0
Figure 7.8 32-Bit External Devices and Their Access Units
16-bit external device (little-endian) A24-A0 000000 000001 000002 000003 000000 000002 000000 000002 D15 7 7 7 7 7 23 0 7 0 7 0 15 0 15 0 15 16 31 0 8 8 8 24 0 D7 D0 Data input/output pin Byte read/write of address 0 Byte read/write of address 1 Byte read/write of address 2 Byte read/write of address 3 Word read/write of address 0 Word read/write of address 2 Longword read/write of address 0
Figure 7.9 16-Bit External Devices and Their Access Units
Rev. 2.00 Mar 09, 2006 page 281 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
8-bit external device (little-endian) A24-A0 000000 000001 000002 000003 000000 000001 000002 000003 000000 000001 000002 000003 D7 7 7 7 7 7 15 7 15 7 15 23 31 D0 0 0 0 0 0 8 0 8 0 8 16 24 Data input/output pin Byte read/write of address 0 Byte read/write of address 1 Byte read/write of address 2 Byte read/write of address 3 Word read/write of address 0 Word read/write of address 2
Longword read/write of address 0
Figure 7.10 8-Bit External Devices and Their Access Units
7.4
7.4.1
Accessing Ordinary Space
Basic Timing
A strobe signal is output by ordinary space accesses of CS0-CS4 spaces to provide primarily for SRAM direct connections. Figure 7.11 shows the basic timing of ordinary space accesses. Ordinary accesses without waits end in 2 cycles. The BS signal is asserted for 1 cycle to indicate the start of the bus cycle. The CSn signal is negated by the fall of clock T2 to ensure the negate period. The negate period is thus half a cycle when accessed at the minimum pitch. The access size is not specified during a read. The correct access start address will be output to the LSB of the address, but since no access size is specified, the read will always be 32 bits for 32-bit devices and 16 bits for 16-bit devices. For writes, only the WE signal of the byte that will be written is asserted. For 32-bit devices, WE3 specifies writing to a 4n address and WE0 specifies writing to a 4n+3 address. For 16-bit devices, WE1 specifies writing to a 2n address and WE0 specifies writing to a 2n+1 address. For 8-bit devices, only WE0 is used. When data buses are provided with buffers, the RD signal must be used for data output in the read direction. When RD/WR signals do not perform accesses, the chip stays in read status, so there is a danger of conflicts occurring with output when this is used to control the external data buffer.
Rev. 2.00 Mar 09, 2006 page 282 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
T1 T2
CKIO
A24-A0
CSn
RD/WR
RD Read D31-D0
WEn Write D31-D0
BS
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.11 Basic Timing of Ordinary Space Access When making a word or longword access with an 8-bit bus width, or a longword access with a 16bit bus width, the bus state controller performs multiple accesses. When clock ratio I : E is other than 1 : 1, the basic timing shown in figure 7.11 is repeated, but when clock ratio I : E is 1 : 1, burst access with no CSn negate period is performed as shown in figure 7.12.
Rev. 2.00 Mar 09, 2006 page 283 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
T1 T2
T1
T2
CKIO
A24-A0
CSn
RD/WR
RD
Read
D15-D0
WEn
Write
D15-D0
BS
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.12 Timing of Longword Access in Ordinary Space Using 16-Bit Bus Width (Clock Ratio I : E = 1 : 1) Figure 7.13 shows an example of 32-bit data width SRAM connection, figure 7.14 an example of 16-bit data width SRAM connection, and figure 7.15 an example of 8-bit data width SRAM connection.
Rev. 2.00 Mar 09, 2006 page 284 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
128 k x 8-bit SRAM A18 A16
Chip
...
...
... ... ... ... ... ... ... ...
A2 CSn RD D31
A0 CS OE I/O7
...
...
D24 DQMUU/WE3 D23
I/O0 WE
...
D16 DQMUL/WE2 D15
...
A16 A0 CS OE I/O7 I/O0 WE
...
...
D0 DQMLL/WE0
...
A16 A0 CS OE I/O7 I/O0 WE
A16 A0 CS OE I/O7 I/O0 WE
Figure 7.13 Example of 32-Bit Data Width SRAM Connection
Rev. 2.00 Mar 09, 2006 page 285 of 906 REJ09B0292-0200
...
...
...
...
...
D8 DQMLU/WE1 D7
...
...
...
...
Section 7 Bus State Controller (BSC)
128 k x 8-bit SRAM A17 A16
Chip
...
...
... ... ... ...
A1 CSn RD D15
A0 CS OE I/O7
...
...
D8 DQMLU/WE1 D7
I/O0 WE
...
A0 CS OE I/O7 I/O0 WE
Figure 7.14 Example of 16-Bit Data Width SRAM Connection
128 k x 8-bit SRAM A16 A16
Chip
...
...
... ...
A0 CSn RD D7
A0 CS OE I/O7
...
...
D0 DQMLL/WE0
I/O0 WE
Figure 7.15 Example of 8-Bit Data Width SRAM Connection
Rev. 2.00 Mar 09, 2006 page 286 of 906 REJ09B0292-0200
...
...
...
...
D0 DQMLL/WE0
...
A16
...
...
Section 7 Bus State Controller (BSC)
7.4.2
Wait State Control
The number of wait states inserted into ordinary space access states can be controlled using the WCR1, WCR2, BCR1 and BCR3 register settings. When the Wn1 and Wn0 wait specification bits in WCR1, WCR2 for the given CS space are 01 or 10, software waits are inserted according to the wait specification. When Wn1 and Wn0 are 11, wait cycles are inserted according to the long wait specification bit AnLW in BCR1, BCR3. The long wait specification in BCR1, BCR3 can be made independently for CS0, CS1 and CS4 spaces, but the same value must be specified for CS2 and CS3 spaces. All WCR1 specifications are independent. By means of WCR1, WCR2, BCR1, and BCR3, a Tw cycle is inserted as a wait cycle as long as the number of specified cycles at the wait timing for ordinary access space shown in figure 7.16. The names of the control bits that specify Tw for each CS space are shown in table 7.5.
T1 CKIO Tw T2
A24-A0
CSn
RD/WR
RD Read D31-D0
WEn Write D31-D0
BS
DACKn* Note: * DACKn waveform when active-low is specified.
Figure 7.16 Wait Timing of Ordinary Space Access (Software Wait Only)
Rev. 2.00 Mar 09, 2006 page 287 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Table 7.5
CSn Spaces and Tw Specification Bits
BCR3 BCR1 A0LW1 A1LW1 AHLW1 AHLW1 A4LW1 A0LW0 A2LW0 AHLW0 AHLW0 A4LW0 WCR1 W01 W11 W21 W31 -- W00 W10 W20 W30 -- WCR2 -- -- -- -- W41 -- -- -- -- W40 Tw 0-14 0-14 0-14 0-14 0-14
CS0 CS1 CS2 CS3 CS4
A0LW2 A1LW2 AHLW2 AHLW2 A4LW2
When a wait is specified by software using WCR1 and WCR2 (Wn1, Wn0), and the external wait mask bit (AnWM) is cleared to 0 in WCR2, the wait input WAIT signal from outside is sampled. Figure 7.17 shows WAIT signal sampling. A 2-cycle wait is specified as a software wait. The sampling is performed when the Tw state shifts to the T2 state, so there is no effect even when the WAIT signal is asserted in the T1 cycle or the first Tw cycle. The WAIT signal is sampled at the clock fall.
Rev. 2.00 Mar 09, 2006 page 288 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Wait states from WAIT signal input T1 Tw Tw Twx T2
CKIO
A24-A0
CSn
RD/WR
RD Read D31-D0
WEn Write D31-D0
WAIT
BS
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.17 Wait State Timing of Ordinary Space Access (Wait States from WAIT Signal)
Rev. 2.00 Mar 09, 2006 page 289 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
For the CS0-CS3 spaces, CSn, RD, and WEn are negated for one cycle after negation of the external wait signal is accepted, as shown in figure 7.17. For the CS4 space, the number of cycles before CSn, RD, and WEn are negated after acceptance of external wait negation can be set as 1, 2, or 4 by means of bits A4WD1 and A4WD0 in WCR2. Figure 7.18 shows an example.
Specified by A4WD1 and A4WD0 in WCR2 (A4WD1, A4WD0 = 01) T1 Tw Twx Twx T2
CKIO
A24-A0
CSn
RD/WR
RD Read D15-D0
WEn Write D15-D0
WAIT
BS
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.18 Wait State Timing of Ordinary Space in CS4 Space
Rev. 2.00 Mar 09, 2006 page 290 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.4.3
CS Assertion Period Extension
Idle cycles can be inserted to prevent extension of the RD or WEn assertion period beyond the length of the CSn assertion period by setting control bits in WCR3. This allows for flexible interfacing to external circuit. The timing is shown in figure 7.19. Th and Tf cycles are added respectively before and after the ordinary cycle. Signals other than RD and WEn are asserted in this cycle, but RD and WEn are not. In addition, data is extended up to the Tf cycle, which is effective for devices with slow write operations.
Th CKIO T1 T2 Tf
Address
CSn BS
RD Read Data
WEn Write Data RD/WR DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.19 CS Assertion Period Extension Function
Rev. 2.00 Mar 09, 2006 page 291 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
For the CS0-CS4 spaces, For spaces CS0--CS4, Th and Tf can be set as follows.
Th CS0--3 CS4 0--2 0--7 Tf 0--2 0--5 WCR3 AnSW1, AnSW0 (Th = Tf) n =0--3 Th: A4SW2--0 Tf: A4HW1--0
7.5
7.5.1
Synchronous DRAM Interface
Synchronous DRAM Direct Connection
Seven kinds of synchronous DRAM can be connected: 2-Mbit (128 k x 16), 4-Mbit (256 k x 16), 16-Mbit (1 M x 16, 2 M x 8, and 4 M x 4), and 64-Mbit (4 M x 16 and 8 M x 8). This chip supports 64-Mbit synchronous DRAMs internally divided into two or four banks, and other synchronous DRAMs internally divided into two banks. Since synchronous DRAM can be selected by the CS signal, CS2 and CS3 spaces can be connected using a common RAS or other control signal. When the memory enable bits for DRAM and other memory (DRAM2-DRAM0) in BCR1 are set to 001, CS2 is ordinary space and CS3 is synchronous DRAM space. When the DRAM2-0 bits are set to 100, CS2 is synchronous DRAM space and CS3 is ordinary space. When the bits are set to 101, both CS2 and CS3 are synchronous DRAM spaces. Supported synchronous DRAM operating modes are burst read/single write mode (initial setting) and burst read/burst write mode. The burst length depends on the data bus width, comprising 8 bursts for a 16-bit width, and 4 bursts for a 32-bit width. The data bus width is specified by the SZ bit in MCR. Burst operation is always performed, so the burst enable (BE) bit in MCR is ignored. Switching to burst write mode is performed by means of the BWE bit in BCR3. Control signals for directly connecting synchronous DRAM are the RAS, CAS/OE, RD/WR, CS2 or CS3, DQMUU, DQMUL, DQMLU, DQMLL, and CKE signals. Signals other than CS2 and CS3 are common to every area, and signals other than CKE are valid and fetched only when CS2 or CS3 is true. Therefore, synchronous DRAM can be connected in parallel in multiple areas. CKE is negated (to the low level) only when a self-refresh is performed; otherwise it is always asserted (to the high level). Commands can be specified for synchronous DRAM using the RAS, CAS/OE, RD/WR, and certain address signals. These commands are NOP, auto-refresh (REF), self-refresh (SELF), allbank precharge (PALL), specific bank precharge (PRE), row address strobe/bank active (ACTV), read (READ), read with precharge (READA), write (WRIT), write with precharge (WRITA), and mode register write (MRS).
Rev. 2.00 Mar 09, 2006 page 292 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Bytes are specified using DQMUU, DQMUL, DQMLU, and DQMLL. The read/write is performed on the byte whose DQM is low. For 32-bit data, DQMUU specifies 4n address access and DQMLL specifies 4n + 3 address access. For 16-bit data, only DQMLU and DQMLL are used. Figure 7.20 shows an example in which a 32-bit connection uses a 256 k x 16 bit synchronous DRAM. Figure 7.21 shows an example with a 16-bit connection.
256 k x 16-bit synchronous DRAM A11
... ... ... ... ... ...
Chip
A9 A0 CLK CKE CS RAS CAS WE I/O15
... ...
A2 CKIO CKE CSn RAS CAS/OE RD/WR D31
...
D16 DQMUU/WE3 DQMUL/WE2 D15
... ...
I/O0 DQMU DQML A9 A0 CLK CKE CS RAS CAS WE I/O15 I/O0 DQMU DQML
... ...
D0 DQMLU/WE1 DQMLL/WE0
Figure 7.20 Synchronous DRAM 32-bit Device Connection
Rev. 2.00 Mar 09, 2006 page 293 of 906 REJ09B0292-0200
...
Section 7 Bus State Controller (BSC)
256 k x 16-bit synchronous DRAM A10 A9
Chip
...
...
... ...
A1 CKIO CKE CSn RAS CAS/OE RD/WR D15
A0 CLK CKE CS RAS CAS WE I/O15
...
...
D0 DQMLU/WE1 DQMLL/WE0
I/O0 DQMU DQML
Figure 7.21 Synchronous DRAM 16-bit Device Connection 7.5.2 Address Multiplexing
Addresses are multiplexed according to the MCR's address multiplex specification bits AMX2- AMX0 and size specification bit SZ so that synchronous DRAMs can be connected to the SH7616 directly without an external multiplex circuit. Table 7.6 shows the relationship between the multiplex specification bits and bit output to the address pins. A24-A16 always output the original value regardless of multiplexing. When SZ = 0, the data width on the synchronous DRAM side is 16 bits and the LSB of the device's address pins (A0) specifies word address. The A0 pin of the synchronous DRAM is thus connected to the A1 pin of the SH7616, the rest of the connection proceeding in the same order, beginning with the A1 pin to the A2 pin. When SZ = 1, the data width on the synchronous DRAM side is 32 bits and the LSB of the device's address pins (A0) specifies longword address. The A0 pin of the synchronous DRAM is thus connected to the A2 pin of the SH7616, the rest of the connection proceeding in the same order, beginning with the A1 pin to the A3 pin.
Rev. 2.00 Mar 09, 2006 page 294 of 906 REJ09B0292-0200
...
...
Section 7 Bus State Controller (BSC)
Table 7.6
SZ and AMX Bits and Address Multiplex Output
Setting External Address Pins Output Timing A1-A8 A9 A9 A10 A10 A18 A10 A19 A10 A20 L/H* A18 A10 A18 A10 A19 L/H* A17 A10 A18
1 1
SZ AMX2 AMX1 AMX0 1 0 0 0
A11 A11 A19 A11 A20 A11 A21
2
A12 L/H *1
A13 A21 *2
2
A14 A14
A15 A15 A23 A15 A24 A15 A25 A15 A23
3 2
Column A1-A8 address
Row A9-A16 A17 address 1 0 0 1 Column A1-A8 address A9
A20 L/H* A21 L/H* A22
1 1
A21* A22 A22* A14
2
Row A10-A17 A18 address 1 0 1 0 Column A1-A8 address A9
A22* A23
2
A23* A14
2
Row A11-A18 A19 address 1 0 1 1 Column A1-A8 address A9
A23* A24
2
A19* A12 A19* A20
2
A13 A21
1
A14 A22
Row A9-A16 A17 address 1 1 0 0 Column A1-A8 address A9
A11 A19 A11 A20
2
L/H* A20 L/H* A21
A13 A21
A22* A23* A22* A23*
3
Row A9-A16 A17 address 1 1 0 1 Column A1-A8 address A9
2
1
A13 A22 A13 A21
A23* A24*
3
2
Row A10-A17 A18 address 1 1 1 1 Column A1-A8 address A9
A23* A24*
3
2
A18* A12 A18* A20
2
A14 A22 A14 A22
A15 A23 A15 A23
Row A9-A16 A17 address 0 0 0 0 Column A1-A8 address A9
L/H* A19
1
A20* A13
2
Row A9-A16 A17 address
A20* A21
2
Rev. 2.00 Mar 09, 2006 page 295 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC) Setting SZ AMX2 AMX1 AMX0 0 1 0 0 Output Timing A1-A8 A9 A9 External Address Pins A10 A10 A11 1 LH* A19 A11 A19 A11 A19 A12 A12 A20 A12 A20 A12 A20 A13 A14 A15 3 2 A21* A22* A15 A21* A22* A23
3 2
Column A1-A8 address
0
0
1
1
0
1
1
1
A9-A16 A17 A18 Row address 1 2 Column A1-A8 L/H* A18* address 2 Row A9-A16 A17 A18* address 1 2 L/H* A17* Column A1-A8 address 2 Row A9-A16 A16 A17* address
A13 A21 A13 A21
A14 A22 A14 A22
A15 A23 A15 A23
Notes: AMX2-AMX0 setting 110 is reserved and must not be used. When SZ = 0, AMX2-AMX0 settings 001, 010, and 101 are also reserved and must not be used. 1. L/H is a bit used to specify commands. It is fixed at L or H according to the access mode. 2. Bank address specification. 3. Bank address specification when using four banks.
7.5.3
Burst Reads
Figure 7.22 (a) and (b) show the timing charts for burst reads. In the following example, 2 synchronous DRAMs of 256k x 16 bits are connected, the data width is 32 bits and the burst length is 4. After a Tr cycle that performs ACTV command output, a READA command is issued in the Tc cycle, read data is accepted in cycles Td1 to Td4, and the end of the read sequence is waited for in the Tde cycle. One Tde cycle is issued when I : E 1 : 1, and two cycles when I : E = 1 : 1. Tap is a cycle for waiting for the completion of the auto-precharge based on the READA command within the synchronous DRAM. During this period, no new access commands are issued to the same bank. Accesses of the other bank of the synchronous DRAM by another CS space are possible. Depending on the TRP1, TRP0 specification in MCR, the chip determines the number of Tap cycles and does not issue a command to the same bank during that period. Figure 7.22 (a) and (b) show examples of the basic cycle. Because a slower synchronous DRAM is connected, setting WCR1 and MCR bits can extend the cycle. The number of cycles from the ACTV command output cycle Tr to the READA command output cycle Tc can be specified by bits RCD1 and RCD0 in MCR. 00 specifies 1 cycle, 01 specifies 2 cycles, and 10 specifies 3 cycles. For 2 or 3 cycles, a NOP command issue cycle Trw for the synchronous DRAM is inserted between the Tr cycle and the Tc cycle. The number of cycles between the READA command
Rev. 2.00 Mar 09, 2006 page 296 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
output cycle Tc and the initial read data fetch cycle Td1 can be specified between 1 cycle and 4 cycles using the W21/W20 and W31/W30 bits in WCR1. The number of cycles at this time corresponds to the number of CAS latency cycles of the synchronous DRAM. When 2 cycles or more, a NOP command issue cycle Tw is inserted between the Tc cycle and the Td1 cycle. The number of cycles in the precharge completion waiting cycle Tap is specified by bits TRP1 and TRP0 in MCR. When CAS latency is 1, a Tap cycle comprising the number of cycles specified by TRP1 and TRP0 is generated. When the CAS latency is 2 or more, a Tap cycle equal to the TRP specification - 1 is generated. During the Tap cycle, no commands other than NOP are issued to the same bank. Figure 7.23 (a) and (b) show examples of burst read timing when RCD1/RCD0 is 01, W31/W30 is 01, and TRP1/TRP0 is 01. When the data width is 16 bits, 8 burst cycles are required for a 16-byte data transfer. The data fetch cycle goes from Td1 to Td8. Synchronous DRAM CAS latency is up to 3 cycles, but the CAS latency of the bus state controller can be specified up to 4. This is so that circuits containing latches can be installed between synchronous DRAMs and the chip.
Tr CKIO A24-A11 A10 A9-A1 CS2 or CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Note: * DACKn waveform when active-low is specified. Tc Td1 Td2 Td3 Td4 Tde Tap
Figure 7.22 (a) Basic Burst Read Timing (Auto-Precharge) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 297 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr Tc Td1 Td2 Td3 Td4 Tde Tde Tap
CKIO
A24-A11
A10
A9-A1
CS2 or CS3
RAS
CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.22 (b) Basic Burst Read Timing (Auto-Precharge) I : E = 1 : 1
Rev. 2.00 Mar 09, 2006 page 298 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO A24-A11 A10 A9-A1 CS2 or CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* TrW Tc Tw Td1 Td2 Td3 Td4 Tde Tap
Note: * DACKn waveform when active-low is specified.
Figure 7.23 (a) Burst Read Wait Specification Timing (Auto-Precharge) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 299 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO TrW Tc Tw Td1 Td2 Td3 Td4 Tde Tde Tap
A24-A11
A10
A9-A1
CS2 or CS3
RAS CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.23 (b) Burst Read Wait Specification Timing (Auto-Precharge) I : E = 1 : 1
Rev. 2.00 Mar 09, 2006 page 300 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.5.4
Single Reads
When a cache area is accessed and there is a cache miss, the cache fill cycle is performed in 16byte units. This means that all the data read in the burst read is valid. On the other hand, when a cache-through area is accessed the required data is a maximum length of 32 bits, and the remaining 12 bytes are wasted. The same kind of wasted data access is produced when synchronous DRAM is specified as the source in a DMA transfer by the DMAC and the transfer unit is other than 16 bytes. Figure 7.24 (a) and (b) show the timings of a single address read. Because the synchronous DRAM is set to the burst read mode, the read data output continues after the required data is received. To avoid data conflict, an empty read cycle is performed from Td2 to Td4 after the required data is read in Td1 and the device waits for the end of synchronous DRAM operation. When the data width is 16 bits, the number of burst transfers during a read is 8. Data is fetched in cache-through and other DMA read cycles only in the Td1 and Td2 cycles (of the 8 cycles from Td1 to Td8) for longword accesses, and only in the Td1 cycle for word or byte accesses. Empty cycles tend to increase the memory access time, lower the program execution speed, and lower the DMA transfer speed, so it is important to avoid accessing unnecessary cache-through areas and to use data structures that enable 16-byte unit transfers by placing data on 16-byte boundaries when performing DMA transfers that specify synchronous DRAM as the source.
Rev. 2.00 Mar 09, 2006 page 301 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO A24-A11 A10 A9-A1 CS2 or CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Tc Td1 Td2 Td3 Td4 Tde Tap
Note: * DACKn waveform when active-low is specified.
Figure 7.24 (a) Single Read Timing (Auto-Precharge) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 302 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO Tc Td1 Td2 Td3 Td4 Tde Tde Tap
A24-A11
A10
A9-A1
CS2 or CS3
RAS CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.24 (b) Single Read Timing (Auto-Precharge) I : E = 1 : 1 7.5.5 Single Writes
Synchronous DRAM writes are executed as single writes or burst writes according to the specification by the BWE bit in BCR3. Figure 7.25 shows the basic timing chart for single write accesses. After the ACTV command Tr, a WRITA command is issued in Tc to perform an autoprecharge. In the write cycle, the write data is output simultaneously with the write command. When writing with an auto-precharge, the bank is precharged after the completion of the write command within the synchronous DRAM, so no command can be issued to that bank until the precharge is completed. For that reason, besides a Tap cycle to wait for the precharge during read accesses, a Trw1 cycle is added to wait until the precharge is started, and the issuing of any new commands to the same bank is delayed during this period. The number of cycles in the Trw1 cycle can be specified using the TRWL1 and TRWL0 bits in MCR.
Rev. 2.00 Mar 09, 2006 page 303 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO Tc Trwl Tap
A24-A11
A10
A9-A1 CS2 or CS3 RAS CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.25 Basic Single Write Cycle Timing (Auto-Precharge) 7.5.6 Burst Write Mode
Burst write mode can be selected by setting the BWE bit to 1 in BCR3. The basic timing charts for burst write access is shown in figure 7.26 (a) and (b). This example assumes a 32-bit bus width and a burst length of 4. In the burst write cycle, the WRITA command that performs autoprecharge is issued in Tc1 following the ACTV command Tr cycle. The first 4 bytes of write data are output simultaneously with the WRITA command in Tc1, and the remaining 12 bytes of data are output consecutively in Tc2, Tc3, and Tc4. In a write with auto-precharge, as with a single write, a Trw1 cycle that provides the waiting time until precharge is started is inserted after output of the write data, followed by a Tap cycle for the precharge wait in a write access. The Trw1 and
Rev. 2.00 Mar 09, 2006 page 304 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tap cycles can be set respectively in MCR by bits TRWL1 and TRWL0, and bits TRP1 and TRP0. When a single write is performed in burst write mode, the synchronous DRAM setting is for a burst length of 4. After data is written in Tc1, empty writes are performed in Tc2, Tc3, and Tc4 by driving the DQMxx signal high. These empty cycles increase the memory access time and tend to reduce program execution speed and DMA transfer speed. Therefore, unnecessary cache-through area accesses should be avoided, and copy-back should be selected for the cache setting. Also, in DMA transfer, it is important to use a data structure that allows transfer in 16-bit units.
Tr CKIO A24-A11 A10 A9-A1 CS2 or CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Tc1 Tc2 Tc3 Tc4 Trwl Tap
Note: * DACKn waveform when active-low is specified.
Figure 7.26 (a) Basic Burst Write Timing (Auto-Precharge) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 305 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO Tc1 Tc2 Tc3 Tc4 Tde Trwl Tap
A24-A11
A10
A9-A1
CS2 or CS3
RAS
CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.26 (b) Basic Burst Write Timing (Auto-Precharge) I : E = 1 : 1 7.5.7 Bank Active Function
A synchronous DRAM bank function is used to support high-speed accesses of the same row address. When the RASD bit in MCR is set to 1, read/write accesses are performed using commands without auto-precharge (READ, WRIT). In this case, even when the access is completed, no precharge is performed. This function is not supported in the CS2 space. When the bank active function is used, no precharge is performed when the access is completed. When accessing the same row address in the same bank, a READ or WRIT command can be called immediately without calling an ACTV command, just like the RAS down mode of the DRAM's high-speed page mode. Synchronous DRAM is divided into two banks, so one row address in each can stay active. When the next access is to a different row address, a PRE command is called first to precharge the bank, and access is performed by an ACTV command and READ or WRIT command in order, after the precharge is completed. With successive accesses to different row
Rev. 2.00 Mar 09, 2006 page 306 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
addresses, the precharge is performed after the access request occurs, so the access time is longer. When writing, performing an auto-precharge means that no command can be called for tRWL + tAP cycles after a WRITA command is called. When the bank active mode is used, READ or WRIT commands can be issued consecutively if the row address is the same. This shortens the number of cycles by tRWL + tAP for each write. The number of cycles between the issue of the precharge command and the row address strobe command is determined by the TRP1, TRP0 in MCR. Whether execution is faster when the bank active mode is used or when basic access is used is determined by the proportion of accesses to the same row address (P1) and the average number of cycles from the end of one access to the next access (tA). When tA is longer than tAP, the delay waiting for the precharge during a read becomes invisible. If tA is longer than tRWL + tAP, the delay waiting for the precharge also becomes invisible during writes. The difference between the bank active mode and basic access speeds in these cases is the number of cycles between the start of access and the issue of the read/write command: (tRP + tRCD) x (1 - P1) and tRCD, respectively. The time that a bank can be kept active, tRAS, is limited. When the period will be provided by program execution, and it is not assured that another row address will be accessed without a hit to the cache, the synchronous DRAM must be set to auto-refresh and the refresh cycle must be set to the maximum value tRAS or less. This enables the limit on the maximum active period for each bank to be ensured. When auto-refresh is not being used, some measure must be taken in the program to ensure that the bank does not stay active for longer than the prescribed period. Figure 7.27 (a) and (b) show burst read cycles that is not an auto-precharge cycle, figure 7.28 (a) and (b) show burst read cycles to a same row address, figure 7.29 (a) and (b) show burst read cycles to different row addresses, figure 7.30 shows a write cycle without auto-precharge, figure 7.31 shows a write cycle to a same row address, and figure 7.32 shows a write cycle to different row addresses. In figure 7.28, a cycle that does nothing, Tnop, is inserted before the Tc cycle that issues the READ command. Synchronous DRAMs have a 2 cycle latency during reads for the DQMxx signals that specify bytes. If the Tc cycle is performed immediately without inserting a Tnop cycle, the DQMxx signal for the Td1 cycle data output cannot be specified. This is why the Tnop cycle is inserted. When the CAS latency is 2 or more, however, the Tnop cycle is not inserted so that timing requirements will be met even when a DQMxx signal is set after the Tc cycle. When the bank active mode is set, the access will start with figure 7.27 or figure 7.30 and repeat figure 7.28 or figure 7.31 for as long as the same row address continues to be accessed when only accesses to the respective banks of the CS3 space are considered. Accesses to other CS spaces during this period do not affect this operation. When an access occurs to a different row address while the bank is active, figure 7.29 or figure 7.32 will be substituted for figures 7.28 and 7.31
Rev. 2.00 Mar 09, 2006 page 307 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
after this is detected. Both banks will become inactive even in the bank active mode after the refresh cycle ends or after the bus is released by bus arbitration.
Tr CKIO A24-A11 A10 A9-A1 CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Tc Td1 Td2 Td3 Td4 Tde
Note: * DACKn waveform when active-low is specified.
Figure 7.27 (a) Burst Read Timing (No Precharge) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 308 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO Tc Td1 Td2 Td3 Td4 Tde Tde
A24-A11
A10
A9-A1
CS3
RAS
CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.27 (b) Burst Read Timing (No Precharge) I : E = 1 : 1
Rev. 2.00 Mar 09, 2006 page 309 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tnop CKIO Tc Td1 Td2 Td3 Td4 Tde
A24-A11
A10
A9-A1
CS3
RAS CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.28 (a) Burst Read Timing (Bank Active, Same Row Address) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 310 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tnop CKIO Tc Td1 Td2 Td3 Td4 Tde Tde
A24-A11
A10
A9-A1
CS3 RAS CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.28 (b) Burst Read Timing (Bank Active, Same Row Address) I : E = 1 : 1
Rev. 2.00 Mar 09, 2006 page 311 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp CKIO A24-A11 A10 A9-A1 CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Tr Tc Td1 Td2 Td3 Td4 Tde
Note: * DACKn waveform when active-low is specified.
Figure 7.29 (a) Burst Read Timing (Bank Active, Different Row Addresses) I : E other than 1 : 1
Rev. 2.00 Mar 09, 2006 page 312 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp CKIO Tr Tc Td1 Td2 Td3 Td4 Tde Tde
A24-A11
A10
A9-A1
CS3 RAS CAS
RD/WR
DQMxx
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.29 (b) Burst Read Timing (Bank Active, Different Row Addresses) I : E = 1 : 1
Rev. 2.00 Mar 09, 2006 page 313 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO A24-A11 A10 A9-A1 CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Tc
Note: * DACKn waveform when active-low is specified.
Figure 7.30 Single Write Mode Timing (No Precharge)
Rev. 2.00 Mar 09, 2006 page 314 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tc CKIO A24-A11 A10 A9-A1 CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.31 Single Write Mode Timing (Bank Active, Same Row Address)
Rev. 2.00 Mar 09, 2006 page 315 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp CKIO A24-A11 A10 A9-A1 CS3 RAS CAS RD/WR DQMxx D31-D0 DACKn* Tr Tc
Note: * DACKn waveform when active-low is specified.
Figure 7.32 Single Write Mode Timing (Bank Active, Different Row Addresses)
Rev. 2.00 Mar 09, 2006 page 316 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.5.8
Refreshes
The bus state controller is equipped with a function to control refreshes of synchronous DRAM. Auto-refreshes can be performed by setting the RMODE bit to 0 and the RFSH bit to 1 in MCR. Consecutive refreshes can also be generated by setting the RRC2-RRC0 bits in RTCSR. When the synchronous DRAM is not accessed for a long period of time, set the RFSH bit and RMODE bit both to 1 to generate self-refresh mode, which uses low power consumption to retain data. Auto-Refresh: The number of refreshes set in the RRC2-RRC0 bits in RTCSR are performed at the interval determined by the input clock selected by the CKS2-CKS0 bits in RTCSR and the value set in RTCOR. Set the CKS2-CKS0 bits and RTCOR so that the refresh interval specifications of the synchronous DRAM being used are satisfied. First , set RTCOR, RTCNT, and the RMODE and RFSH bits in MCR, then set the CKS2-CKS0 and RRC2-RRC0 bits in RTCSR. When a clock is selected with the CKS2-CKS0 bits, RTCNT starts counting up from the value at that time. The RTCNT value is constantly compared to the RTCOR value, and when the two values match, a refresh request is made, and the number of auto-refreshes set in RRC2-RRC0 are performed. RTCNT is cleared to 0 at that time and the count up starts again. Figure 7.33 shows the timing for the auto-refresh cycle. First, a PALL command is issued during the Tp cycle to change all the banks from active to precharge states. Then number of idle cycles equal to one less than the value set in TRP1 and TRP0 are inserted, and a REF command is issued in the Trr cycle. After the Trr cycle, no new commands are output for the number of cycles specified in the TRAS bit in MCR. The TRAS bit must be set to satisfy the refresh cycle time specifications (active/active command delay time) of the synchronous DRAM. When the set value of the TRP1 and TRP0 bits in MCR is 2 or more, an NOP cycle is inserted between the Tp cycle and Trr cycle. During a manual reset, no refresh request is issued, since there is no RTCNT count-up. To perform a refresh properly, make the manual reset period shorter than the refresh cycle interval and set RTCNT to (RTCOR - 1) so that the refresh is performed immediately after the manual reset is cleared.
Rev. 2.00 Mar 09, 2006 page 317 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp CKIO Trr Trc Trc Trc Tre
A10 CS2 or CS3 RAS CAS
RD/WR
DQMxx
Figure 7.33 Auto-Refresh Timing Self-Refreshes: The self-refresh mode is a type of standby mode that produces refresh timing and refresh addresses within the synchronous DRAM. It is started up by setting the RMODE and RFSH bits to 1. The synchronous DRAM is in self-refresh mode when the CKE signal level is low. During the self-refresh, the synchronous DRAM cannot be accessed. To clear the self-refresh, set the RMODE bit to 0. After self-refresh mode is cleared, issuing of commands is prohibited for the number of cycles specified in the TRAS1 and TRAS0 bits in MCR. Figure 7.34 shows the selfrefresh timing. Settings must be made so that self-refresh clearing and data retention are performed correctly, and auto-refreshing is performed without delay at the correct intervals. When self-refresh mode is entered while the synchronous DRAM is set for auto-refresh or when leaving the standby mode with a manual reset or NMI, auto-refresh can be re-started if RFSH is 1 and RMODE is 0 when the self-refresh mode is cleared. When time is required between clearing the self-refresh mode and starting the auto-refresh mode, this time must be reflected in the initial RTCNT setting. When the RTCNT value is set to RTCOR - 1, the refresh can be started immediately. If the standby function of the chip is used to enter the standby mode after the self-refresh mode is set, the self-refresh state continues; the self-refresh state will also be maintained after returning from a standby using an NMI. A manual reset cannot be used to exit the self-refresh state either. During a power-on reset, the bus state controller register is initialized, so the self-refresh state is ended.
Rev. 2.00 Mar 09, 2006 page 318 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Refresh Requests and Bus Cycle Requests: When a refresh request occurs while a bus cycle is executing, the refresh will not be executed until the bus cycle is completed. When a refresh request occurs while the bus is released using the bus arbitration function, the refresh will not be executed until the bus is recaptured. In the SH7616, the REFOUT pin is provided to send a signal requesting the bus right during the wait for refreshing to be executed. REFOUT is asserted until the bus is acquired. If RTCNT and RTCOR match and a new refresh request occurs while waiting for the refresh to execute, the previous refresh request is erased. To make sure the refresh executes properly, be sure that the bus cycle and bus capture do not exceed the refresh interval. If a bus arbitration request occurs during a self-refresh, the bus is not released until the self-refresh is cleared.
Tp CKIO CKE A10 CS2 or CS3 RAS CAS RD/WR DQMxx Trr Trc Trc Trc Trc Trc Tre
Figure 7.34 Self-Refresh Timing
Rev. 2.00 Mar 09, 2006 page 319 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.5.9
Overlap Between Auto Precharge Cycle (Tap) and Next Access
If the CPU and DMAC or E-DMAC are accessed sequentially and the first access is to SDRAM and also in the auto precharge mode, the auto precharge cycle (Tap) of the first access may overlap the second access if the second access is to a different memory space or to a different bank of the same SDRAM. (Even if the second access is to the normal space, there may be an overlap with the Tap cycle.) For this reason, it appears for the number of cycles of the second access as if access takes place sooner (by the number of Tap cycles) than it actually does. Specific cases in which an overlap occurs are listed in table 7.7. Also, figure 7.35 shows is a conceptual diagram of an overlap that occurs when memory spaces CS2 and CS3 are connected to SDRAM (table 7.7, No. 3). Table 7.7
No. 1 2 3 4
Cases of Overlap Between Tap Cycle and Next Access
Second Access
First Access
Space CS3, auto precharge Access to different space among CS0, CS1, CS2, and CS3 mode Access to different bank in CS3 Space CS2, auto precharge Access to different space among CS0, CS1, CS2, and CS3 mode Access to different bank in CS2
First access to CS2 space
Tr
Tc
Td1
Td2
Td3
Td4
Tde Second access to CS3 space
Tap
Tap
Tr Overlap
Tc
Td1
Td2
Figure 7.35 Conceptual Diagram of Overlap (Conditions: SDRAM Connected to CS2 Space (RAS Precharge Time Set to 2 Cycles) and SDRAM Connected to CS3 Space) RAS
Rev. 2.00 Mar 09, 2006 page 320 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.5.10
Power-On Sequence
To use synchronous DRAM, the mode must first be set after the power is turned on. To properly initialize the synchronous DRAM, the synchronous DRAM mode register must be written to after the registers of the bus state controller have first been set. The synchronous DRAM mode register is set using a combination of the CS2 or CS3 signal and the RAS, CAS/OE, and RD/WR signals. They fetch the value of the address signal at that time. If the value to be set is X, the bus state controller operates by writing to address X + H'FFFF0000 or X + H'FFFF8000 from the CPU, which allows the value X to be written to the synchronous DRAM mode register. Whether X + H'FFFF0000 or X + H'FFFF8000 is used depends on the specifications of the synchronous DRAM. Use a value in the range H'000 to H'FFF for X. Data is ignored at this time, but the mode is written using word as the size. Write any data in word size to the following addresses to select the burst read single write supported by the chip, a CAS latency of 1 to 3, a sequential wrap type, and a burst length of 8 or 4 (depending on whether the width is 16 bits or 32 bits). * Burst Read/Single Write For 16 bits: CAS latency 1 CAS latency 2 CAS latency 3 CAS latency 1 CAS latency 2 CAS latency 3 H'FFFF0426 H'FFFF0446 H'FFFF0466 H'FFFF0848 H'FFFF0888 H'FFFF08C8 (H'FFFF8426) (H'FFFF8446) (H'FFFF8466) (H'FFFF8848) (H'FFFF8888) (H'FFFF88C8)
For 32 bits:
To set burst read, burst write, CAS latency 1 to 3, wrap-type sequential, and burst length 8 or 4 (depending on whether the width is 16 bits or 32 bits), arbitrary data is written to the following addresses, using the word size. * Burst Read/Burst Write 16-bit width: CAS latency 1 CAS latency 2 CAS latency 3 CAS latency 1 CAS latency 2 CAS latency 3 H'FFFF0026 H'FFFF0046 H'FFFF0066 H'FFFF0048 H'FFFF0088 H'FFFF00C8 (H'FFFF8026) (H'FFFF8046) (H'FFFF8066) (H'FFFF8048) (H'FFFF8088) (H'FFFF80C8)
32-bit width:
Figure 7.36 shows the mode register setting timing.
Rev. 2.00 Mar 09, 2006 page 321 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Writing to address X + H'FFFF0000 or X + H'FFFF8000 first issues an all-bank precharge command (PALL), then issues eight dummy auto-refresh commands (REF) required for the synchronous DRAM power-on sequence. Lastly, a mode register write command (MRS) is issued. Three idle cycles are inserted between the all-bank precharge command and the first auto-refresh command, and eight idle cycles between auto-refresh commands, and between the eighth autorefresh command and the mode register write command, regardless of the MCR setting. After writing to the synchronous DRAM mode register, perform a dummy read to each synchronous DRAM bank before starting normal access. This will initialize the SH7616's internal address comparator. Synchronous DRAM requires a fixed idle time after powering on before the all-bank precharge command is issued. Refer to the synchronous DRAM manual for the necessary idle time. When the pulse width of the reset signal is longer than the idle time, the mode register may be set immediately without problem. However, care is required if the pulse width of the reset signal is shorter than the idle time.
Tp Tpw Tpw Tpw Trr Trc Trc Trr Trc Trc Tmw
CKIO PALL A24-A11 REF REF MRS
A10
A9-A1
CS2 or CS3
RAS
CAS
RD/WR
DQMxx
Figure 7.36 Synchronous DRAM Mode Write Timing
Rev. 2.00 Mar 09, 2006 page 322 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.5.11
64 Mbit Synchronous DRAM (2 Mword x 32-bit) Connection
64 Mbit Synchronous DRAM (x 32-bit) Connection Example: Figure 7.37 shows an example x connection between the SH7616 and 64 Mbit synchronous DRAM (x 32-bit).
2 Mword x 32-bit SDRAM A22 A13 A12 A12 A11 A10
Chip
A2 CKIO CKE CSn RAS CAS/OE RD/WR D31
A0 CLK CKE CS RAS CAS WE I/O31
D0 DQMUU/WE3 DQMUL/WE2 DQMLU/WE1 DQMLL/WE0
I/O0 DQMUU DQMUL DQMLU DQMLL
Figure 7.37 64 Mbit Synchronous DRAM (2 Mword x 32-bit) Connection Example Bus Status Controller (BSC) Register Settings: Set the individual bits in the memory control register (MCR) as follows. MCR (bit 6) SZ = 1 MCR (bit 7) AMX2 = 0 MCR (bit 5) AMX1 = 0 MCR (bit 4) AMX0 = 0 Synchronous DRAM Mode Settings: To make mode settings for the synchronous DRAM, write to address X+H'FFFF0000 or X+H'FFFF8000 from the CPU. (X represents the setting value.) Whether to use X+H'FFFF0000 or X+H'FFFF8000 determines on the synchronous DRAM used.
Rev. 2.00 Mar 09, 2006 page 323 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.6
7.6.1
DRAM Interface
DRAM Direct Connection
When the DRAM and other memory enable bits (DRAM2-DRAM0) in BCR1 are set to 010, the CS3 space becomes DRAM space, and a DRAM interface function can be used to directly connect DRAM. The data width of an interface can be 16 or 32 bits (figures 7.38 and 7.39). Two-CAS 16-bit DRAMs can be connected, since CAS is used to control byte access. The RAS, CAS3-CAS0, and RD/WR signals are used to connect the DRAM. When the data width is 16 bits, CAS3, and CAS2 are not used. In addition to ordinary read and write access, burst access using high-speed page mode is also supported.
256 k x 16-bit DRAM A10
... ... ... ... ... ...
Chip
A8
...
A2
A0
RAS RD/WR D31
...
...
D16 CAS3 CAS2 D15
...
D0 CAS1 CAS0
...
Figure 7.38 Example of DRAM Connection (32-Bit Data Width)
Rev. 2.00 Mar 09, 2006 page 324 of 906 REJ09B0292-0200
...
...
...
RAS OE WE I/O15 I/O0 UCAS LCAS
A8 A0
RAS OE WE I/O15 I/O0 UCAS LCAS
Section 7 Bus State Controller (BSC)
256 k x 16-bit DRAM A9
... ... ... ...
Chip
A8
...
A1
A0
RAS RD/WR D15
... ...
RAS OE WE I/O15
...
D0 CAS1 CAS0
I/O0 UCAS LCAS
Figure 7.39 Example of DRAM Connection (16-Bit Data Width) 7.6.2 Address Multiplexing
When the CS3 space is set to DRAM, addresses are always multiplexed. This allows DRAMs that require multiplexing of row and column addresses to be connected directly without additional address multiplexing circuits. There are four ways of multiplexing, which can be selected using the AMX1-AMX0 bits in MCR. Table 7.8 illustrates the relationship between the AMX1-AMX0 bits and address multiplexing. Address multiplexing is performed on address output pins A15-A1. The original addresses are output to pins A24-A16. During DRAM accesses, AMX2 is reserved, so set it to 0. Table 7.8
AMX1 0 1
Relationship between AMX1-AMX0 and Address Multiplexing
AMX0 0 1 0 1 No. of Column Address Bits 8 bits 9 bits 10 bits 11 bits Row Address Output A23-A9 A24-A10 A24-A11* 2 A24-A12*
1
Column Address Output A15-A1 A15-A1 A15-A1 A15-A1
Notes: 1. Address output pin A15 is high. 2. Address output pins A15 and A14 are high.
Rev. 2.00 Mar 09, 2006 page 325 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.6.3
Basic Timing
The basic timing of a DRAM access is 3 cycles. Figure 7.40 shows the basic DRAM access timing. Tp is the precharge cycle, Tr is the RAS assert cycle, Tc1 is the CAS assert cycle, and Tc2 is the read data fetch cycle. When accesses are consecutive, the Tp cycle of the next access overlaps the Tc2 cycle of the previous access, so accesses can be performed in a minimum of 3 cycles each.
Tp CKIO A24-A16 A15-A1 RAS CASn RD/WR Read RD D31-D0 RD/WR Write RD D31-D0 DACKn* Tr Tc1 Tc2
Note: * DACKn waveform when active-low is specified.
Figure 7.40 Basic Access Timing
Rev. 2.00 Mar 09, 2006 page 326 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.6.4
Wait State Control
When the clock frequency is raised, 1 cycle may not always be sufficient for all states to end, as in basic access. Setting bits in WCR1, WCR2 and MCR enables the state to be lengthened. Figure 7.41 shows an example of lengthening a state using settings. The Tp cycle (which ensures a sufficient RAS precharge time) can be extended from 1 cycle to 2 cycles by insertion of a Tpw cycle by means of the TRP1, TRP0 bit in MCR. The number of cycles between RAS assert and CASn assert can be extended from 1 cycle to 3 cycles by inserting a Trw cycle by means of the RCD1, RCD0 bit in MCR. The number of cycles from CASn assert to the end of access can be extended from 1 cycle to 3 cycles by setting the W31/W30 bits in WCR1. When external wait mask bit A3WM in WCR2 is cleared to 0 and bits W31 and W30 in WCR1 are set to a value other than 00, the external wait pin is also sampled, so the number of cycles can be further increased. When bit A3WM in WCR2 is set to 1, external wait input is ignored regardless of the setting of W31 and W30 in WCR1. Figure 7.42 shows the timing of wait state control using the WAIT pin. In either case, when consecutive accesses occur, the Tp cycle access overlaps the Tc2 cycle of the previous access. In DRAM access, BS is not asserted, and so RAS, CASn, RD, etc., should be used for WAIT pin control.
Rev. 2.00 Mar 09, 2006 page 327 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp CKIO A24-A16 A15-A1 RAS CASn RD/WR Read RD D31-D0 RD/WR Write RD D31-D0 DACKn* Tpw Tr Trw Tc1 Tw Tc2
Note: * DACKn waveform when active-low is specified
Figure 7.41 Wait State Timing
Rev. 2.00 Mar 09, 2006 page 328 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp CKIO Tr Tc1 Tw Twx Tc2
A24-A16
A15-A1 RAS CASn RD/WR RD D31-D0
Read
RD/WR Write RD D31-D0 DACKn* WAIT
Note: * DACKn waveform when active-low is specified
Figure 7.42 External Wait State Timing 7.6.5 Burst Access
In addition to the ordinary mode of DRAM access, in which row addresses are output at every access and data is then accessed, DRAM also has a high-speed page mode for use when continuously accessing the same row that enables fast access of data by changing only the column address after the row address is output. Select ordinary access or high-speed page mode by setting
Rev. 2.00 Mar 09, 2006 page 329 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
the burst enable bit (BE) in MCR. Figure 7.43 shows the timing of burst access in high-speed page mode. When performing burst access, cycles can be inserted using the wait state control function. An address comparator is provided to detect matches of row addresses in burst mode. When this function is used and the BE bit in MCR is set to 1, setting the MCR's RASD bit (which specifies RAS down mode) to 1 places the SH7616 in RAS down mode, which leaves the RAS signal asserted. The access timing in RAS down mode is shown in figures 7.44 and 7.45. When RAS down mode is used, the refresh cycle must be less than the maximum DRAM RAS assert time tRAS when the refresh cycle is longer than the tRAS maximum.
Tp CKIO Tr Tc1 Tc2 Tc1 Tc2
A24-A16
A15-A1 RAS CASn RD/WR RD D31-D0
Read
RD/WR Write RD D31-D0 DACKn*
Note: * DACKn waveform when active-low is specified
Figure 7.43 Burst Access Timing
Rev. 2.00 Mar 09, 2006 page 330 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tc1 Tc2
CKIO
A24-A14
A13-A1
RAS CASn
RD/WR
Read
RD
D31-D0
RD/WR
Write
RD
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified
Figure 7.44 RAS Down Mode Same Row Access Timing
Rev. 2.00 Mar 09, 2006 page 331 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tp Tr Tc1 Tc2
CKIO
A24-A16
A15-A1
RAS
CASn
RD/WR
Read
RD
D31-D0
RD/WR
Write
RD
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified
Figure 7.45 RAS Down Mode Different Row Access Timing 7.6.6 EDO Mode
In addition to the kind of DRAM in which data is output to the data bus only while the CASn signal is asserted in a data read cycle, there is another kind provided with an EDO mode in which, while both RAS and OE are asserted, once the CASn signal is asserted data is output to the data bus until CASn is next asserted, even though CASn is negated during this time.
Rev. 2.00 Mar 09, 2006 page 332 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
The EDO mode bit (EDO) in MCR allows selection of ordinary access/high-speed page mode burst access or ordinary access/burst access using EDO mode. Since OE control is performed in EDO mode DRAM access, the CAS and OE pins of the SH7616 must be connected to the OE pin of the DRAM. Ordinary access in EDO mode is shown in figure 7.48, and burst access in figure 7.49. In EDO mode, in order to extend the timing for data output to the data bus in a read cycle until the next assertion of CASn, the DRAM access time can be increased by delaying the data latch timing by 1/2 cycle, making it at the rise of the CKIO clock.
256 k x 16-bit DRAM A10 . . . . A2 . . . . . . . . A8 . . . . A0
Chip
RAS RD/WR D31 D16 CAS3 CAS2 D15 . . . . D0 CAS1 CAS0 CAS/OE
. . . .
RAS OE WE I/O15 . . . . I/O0 UCAS LCAS
. . . . . . . . A8 . . . . A0
. . . .
RAS OE WE I/O15 . . . . I/O0 UCAS LCAS
Figure 7.46 Example of EDO DRAM Connection (32-Bit Data Width)
Rev. 2.00 Mar 09, 2006 page 333 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
256 k x 16-bit DRAM A9 . . . . A1 . . . . . . . . A8 . . . . A0
Chip
RAS RD/WR D15 . . . . D0 CAS1 CAS0 CAS/OE
. . . .
. . . .
RAS OE WE I/O15 . . . . I/O0 UCAS LCAS
Figure 7.47 Example of EDO DRAM Connection (16-Bit Data Width)
Rev. 2.00 Mar 09, 2006 page 334 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr Tc1 Tc2 (Tpc)
CKIO
A24-A16
Row address
A15-A1
Row address
Column address
RD/WR
RAS
CASn
D15-D0 Read CAS/OE
D15-D0 Write CAS/OE High level
DACKn*
Note: * DACKn waveform when active-low is specified
Figure 7.48 DRAM EDO Mode Ordinary Access Timing
Rev. 2.00 Mar 09, 2006 page 335 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tr CKIO A24-A16 A15-A1 RD/WR RAS CASn D15-D0
Read
Row address
Tc1
Tc2
Tc1
Tc2
Tc1
Tc2
Tc1
Tc2
(Tpc)
Row address
Column address Column address Column address Column address
CAS/OE D15-D0
Write
CAS/OE DACKn*
High
Note: * DACKn waveform when active-low is specified
Figure 7.49 DRAM EDO Mode Burst Access Timing 7.6.7 DRAM Single Transfer
Wait states equivalent to the value set in bits DSWW1 and DSWW0 in BCR3 can be inserted between DACKn assertion and CASn assertion in a write in DMA single address transfer mode. Inserting wait states allows the data setup time for external device memory. Figure 7.50 shows the write cycle timing in DMA single transfer mode when DSWW1/DSWW0 = 01 and RASD = 1. The DMA single transfer mode read cycle is the same as a CPU or DMA dual transfer mode read cycle.
Rev. 2.00 Mar 09, 2006 page 336 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Tdsww Tc1 Tc2
CKIO
A24-A16
A15-A1
RAS
Low level
CASn
RD/WR
D31-D0
DACKn*
Note: * DACKn waveform when active-low is specified
Figure 7.50 DMA Single Transfer Mode Write Cycle Timing (RAS Down Mode, Same Row Address) RAS 7.6.8 Refreshing
The bus state controller includes a function for controlling DRAM refreshing. Distributed refreshing using a CAS-before-RAS refresh cycle can be performed by clearing the RMODE bit to 0 and setting the RFSH bit to 1 in MCR. Consecutive refreshes can be generated by setting bits RRC2-RRC0 in RTCSR. If DRAM is not accessed for a long period, self-refresh mode, which uses little power consumption for data retention, can be activated by setting both the RMODE and RFSH bits to 1. CAS-Before-RAS Refreshing: Refreshing is performed at intervals determined by the input clock RAS CAS selected by bits CKS2-CKS0 in RTCSR, and the value set in RTCOR. The RTCOR value and the value of bits CKS2-CKS0 in RTCSR should be set so as to satisfy the refresh interval
Rev. 2.00 Mar 09, 2006 page 337 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
specification for the DRAM used. First make the settings for RTCOR, RTCNT, and the RMODE and RFSH bits in MCR, then make the CKS2-CKS0 and RRC2-RRC0 settings in RTCSR. When the clock is selected by CKS2-CKS0, RTCNT starts counting up from the value at that time. The RTCNT value is constantly compared with the RTCOR value, and when the two values match, a refresh request is generated and the number of CAS-before-RAS refreshes set in bits RRC2-RRC0 are performed. At the same time, RTCNT is cleared to zero and the count-up is restarted. Figure 7.51 shows the CAS-before-RAS refresh cycle timing. The number of RAS assert cycles in the refresh cycle is specified by bits TRAS1 and TRAS0 in MCR. As with ordinary accesses, the specification of the RAS precharge time in the refresh cycle follows the setting of bits TRP1 and TRP0 in MCR.
Tp Trr Trc1 Trc2 Tre
CKIO
RAS CASn
RD/WR
RD
Figure 7.51 DRAM CAS CAS-before-RAS Refresh Cycle Timing RAS Self-Refreshing: A self-refresh is started by setting both the RMODE bit and the RFSH bit to 1. During the self-refresh, DRAM cannot be accessed. Self-refreshing is cleared by clearing the RMODE bit to 0. Self-refresh timing is shown in figure 7.52. Settings must be made so that selfrefresh clearing and data retention are performed correctly, and CAS-before-RAS refreshing is immediately performed at the correct intervals. When self-refreshing is started from the state in which CAS-before-RAS refreshing is set, or when exiting standby mode by means of a manual reset or NMI, auto-refreshing is restarted if RFSH is set to 1 and RMODE is cleared to 0 when self-refresh mode is cleared. If the transition from clearing of self-refresh mode to starting autorefresh takes time, this time should be taken into consideration when setting the initial value of RTCNT. When the RTCNT value is set to RTCOR-1, the refresh can be started immediately.
Rev. 2.00 Mar 09, 2006 page 338 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
After self-refreshing has been set, the self-refresh state continues even if the chip standby state is entered using the chip's standby function. The self-refresh state is also maintained even after recovery from standby mode by means of NMI input. In the case of a power-on reset, the bus state controller's registers are initialized, and therefore the self-refresh state is cleared.
Tp CKIO RAS CASn
Trr
Trc1
Trc2
Trc2
Tre
Figure 7.52 DRAM Self-Refresh Cycle Timing 7.6.9 Power-On Sequence
When DRAM is used after the power is turned on, there is a requirement for a waiting period during which accesses cannot be performed (100 s or 200 s minimum) followed by at least the prescribed number of dummy CAS-before-RAS refresh cycles (usually 8). The bus state controller (BSC) does not perform any special operations for the power-on reset, so the required power-on sequence must be implemented by the initialization program executed after a power-on reset.
7.7
Burst ROM Interface
Set the BSTROM bit in BCR1 to set the CS0 space for connection to burst ROM. The burst ROM interface is used to permit fast access to ROMs that have the nibble access function. Figure 7.54 shows the timing of nibble accesses to burst ROM. Set for two wait cycles. The access is basically the same as an ordinary access, but when the first cycle ends, only the address is changed. The CS0 signal is not negated, enabling the next access to be conducted without the T1 cycle required for ordinary space access. From the second time on, the T1 cycle is omitted, so access is 1 cycle faster than ordinary accesses. Currently, the nibble access can only be used on 4-address ROM. This function can only be utilized for word or longword reads to 8-bit ROM and longword reads to 16-bit ROM. Mask ROMs have slow access speeds and require 4 instruction fetches for 8-bit widths and 16 accesses for cache filling. Limited support of nibble access was thus added to alleviate this problem. When connecting to an 8-bit width ROM, a maximum of 4 consecutive
Rev. 2.00 Mar 09, 2006 page 339 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
accesses are performed; when connecting to a 16-bit width ROM, a maximum of 2 consecutive accesses are performed. Figure 7.53 shows the relationship between data width and access size. For cache filling and DMAC 16-byte transfers, longword accesses are repeated 4 times. When one or more wait states are set for a burst ROM access, the WAIT pin is sampled. When the burst ROM is set and 0 specified for waits, there are 2 access cycles from the second time on. Figure 7.55 shows the timing.
T1 T1 T1 T1 T1 T1 T1 T1 T1
Tw Tw Tw Tw Tw Tw Tw Tw Tw
T2 T2 T2 T2 T2 T2 T2 T2 T2
Tw Tw
T2 T2
Tw
T2
Tw
T2
8-bit bus-width longword access 8-bit bus-width word access 8-bit bus-width byte access Tw T2 16-bit bus-width longword access 16-bit bus-width word access 16-bit bus-width byte access 32-bit bus-width longword access 32-bit bus-width word access 32-bit bus-width byte access
Figure 7.53 Data Width and Burst ROM Access (1 Wait State)
Rev. 2.00 Mar 09, 2006 page 340 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
T1 Tw1 Tw2 T2 Tw1 Tw2 T2
CKIO
A24-A0
CS0
RD/WR
RD
D31-D0
BS
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.54 Burst ROM Nibble Access (2 Wait States)
Rev. 2.00 Mar 09, 2006 page 341 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
T1 T2 T1' T2
CKIO
A24-A0
CS0
RD/WR
RD
D31-D0
BS
DACKn*
Note: * DACKn waveform when active-low is specified.
Figure 7.55 Burst ROM Nibble Access (No Wait States)
Rev. 2.00 Mar 09, 2006 page 342 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.8
Idles between Cycles
Because operating frequencies have become high, when a read from a slow device is completed, data buffers may not go off in time to prevent data conflicts with the next access. This lowers device reliability and causes errors. To prevent this, a function has been added to avoid data conflicts that memorizes the space and read/write state of the preceding access and inserts an idle cycle in the access cycle for those cases in which problems are found to occur when the next access starts up. The BSC checks whether a wait is to be inserted in two cases: if a read cycle is followed immediately by a read access to a different CS space, and if a read access is followed immediately by a write from the chip. When the chip is writing continuously, the data direction is always from the chip to other memory, and there are no particular problems. Neither is there any particular problem if the following read access is to the same CS space, since data is output from the same data buffer. The number of idle cycles to be inserted into the access cycle when reading from another CS space, or performing a write, after a read from the CS3 space, is specified by the IW31 and IW30 bits in WCR1. Likewise, IW21 and IW20 specify the number of idle cycles after CS2 reads, IW11 and IW10 specify the number after CS1 reads, and IW01 and IW00 specify the number after CS0 reads. The number of idle cycles after a CS4 read is specified by the IW41 and IW40 bits in WCR2. From 0, 1, 2, or 4 cycles can be specified. When there is already a gap between accesses, the number of empty cycles is subtracted from the number of idle cycles before insertion. When a write cycle is performed immediately after a read access, 1 idle cycle is inserted even when 0 is specified for waits between access cycles. When the chip shifts to a read cycle immediately after a write, the write data becomes high impedance when the clock rises, but the RD signal, which indicates read cycle data output enable, is not asserted until the clock falls. The result is that no idles are inserted into the cycle. When bus arbitration is being performed, an empty cycle is inserted for arbitration, so no is inserted between cycles.
Rev. 2.00 Mar 09, 2006 page 343 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
T1 CKIO A24-A0 CSm CSn BS RD/WR RD D31-D0
CSm space read CSn space read CSn space write
T2
Twait
T1
T2
Twait
T1
T2
Specification of waits between CSm accesses (reading different spaces)
Specification of waits between CSn accesses (read followed by write)
Figure 7.56 Idles between Cycles
Rev. 2.00 Mar 09, 2006 page 344 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.9
Bus Arbitration
The chip has a bus arbitration function that, when a bus release request is received from an external device, releases the bus to that device after the bus cycle being executed is completed. The chip keeps the bus under normal conditions and permits other devices to use the bus by releasing it when they request its use. In the following explanation, external devices requesting the bus are called slaves. The chip has three internal bus masters, the CPU, the DMAC and the E-DMAC. When synchronous DRAM or DRAM is connected and refresh control is performed, the refresh request becomes a fourth master. In addition to these, there are also bus requests from external devices. The priority for bus requests when they occur simultaneously is as follows.
Refresh request External device E-DMAC DMAC CPU
However, only one E-DMAC channel can hold the bus during one bus-mastership cycle. The E-DMAC has two channels to handle both transmission and reception. Arbitration between the channels is performed automatically within the E-DMAC module, with bus mastership alternating between the transmit channel and the receive channel. For arbitration between the two DMAC channels, either fixed priority mode or round robin mode can be selected by means of the priority mode bit (PR) in the DMA operation register (DMAOR). When the bus is being passed between slave and master, all bus control signals are negated before the bus is released to prevent erroneous operation of the connected devices. When the bus is transferred, also, the bus control signals begin bus driving from the negated state. The master and slave passing the bus between them drive the same signal values, so output buffer conflict is avoided. A pull-up resistance is required for the bus control signals to prevent malfunction caused by external noise when they are at high impedance. Bus permission is granted at the end of the bus cycle. When the bus is requested, the bus is released immediately if there is no ongoing bus cycle. If there is a current bus cycle, the bus is not released until the bus cycle ends. Even when a bus cycle does not appear to be in progress when viewed from off-chip, it is not possible to determine immediately whether the bus has been released by looking at CSn or other control signals, since a bus cycle (such as wait insertion between access cycles) may have been started internally. The bus cannot be released during burst transfers for cache filling, DMAC 16-byte block transfers (16 + 16 = 32-byte transfers in dual address mode), or E-DMAC 16-byte block transfers. Likewise, the bus cannot be released between the read and write cycles of a TAS instruction. Arbitration is also not performed between multiple
Rev. 2.00 Mar 09, 2006 page 345 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
bus cycles produced by a data width smaller than the access size, such as a longword access to an 8-bit data width memory. Bus arbitration is performed between external vector fetch, PC save, and SR save cycles during interrupt handling, which are all independent accesses. Because the CPU is connected to cache memory by a dedicated internal bus, cache memory can be read even when the bus is being used by another bus master on the chip or externally. When writing from the CPU, an external write cycle is produced. Since the internal bus that connects the CPU, DMAC, and on-chip peripheral modules can operate in parallel to the external bus, both read and write accesses from the CPU to on-chip peripheral modules and from the DMAC to on-chip peripheral modules are possible even if the external bus is not held. Figures 7.57 (a) and 7.57 (b) show the timing charts in the cases that bus requests occur simultaneously from the E-DMAC, DMAC, and CPU. These cases are based on the following settings: * The CS2 and CS3 spaces are set for synchronous DRAM. * The CAS latency is one cycle. * The E-DMAC is enabled at both the transmitter and receiver (the buffer and descriptor use the CS3 space). * The DMAC is enabled in only one channel that is set to auto-request mode, cycle-steal mode, and 16-byte dual-address transmission (CS2 space). * Burst read and single write are set to synchronous DRAM.
Rev. 2.00 Mar 09, 2006 page 346 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
CPU
E-DMAC
DMAC
CPU
Figure 7.57 (a) Bus Arbitration Timing (E-DMAC Read DMAC 16-Byte Transmission CPU Read)
Rev. 2.00 Mar 09, 2006 page 347 of 906 REJ09B0292-0200
D31-D0
A24-A0
RD/WR
CKIO
RAS
CAS
CS0
CS2
CS3
RD
Section 7 Bus State Controller (BSC)
CPU
E-DMAC
DMAC
CPU
Figure 7.57 (b) Bus Arbitration Timing (E-DMAC Write DMAC 16-Byte Transmission CPU Read)
Rev. 2.00 Mar 09, 2006 page 348 of 906 REJ09B0292-0200
D31-D0
A24-A0
RD/WR
CKIO
RAS
CAS
CS0
CS2
CS3
RD
Section 7 Bus State Controller (BSC)
7.9.1
Master Mode
The chip keeps the bus unless it receives a bus request. When a bus release request (BRLS) assertion (low level) is received from an external device, buses are released and a bus grant (BGR) is asserted (low level) as soon as the bus cycle being executed is completed. When it receives a negated (high level) BRLS signal, indicating that the slave has released the bus, it negates the BGR (to high level) and begins using the bus. When the bus is released, all output and I/O signals related to the bus interface are changed to high impedance, except for the CKE signal for the synchronous DRAM interface, the BGR signal for bus arbitration, and DMA transfer control signals DACK0 and DACK1. When the DRAM has finished precharging, the bus is released. The synchronous DRAM also issues a precharge command to the active bank. After this is completed, the bus is released. The specific bus release sequence is as follows. First, the address bus and data bus become high impedance synchronously with a rise of the clock. Half a cycle later, the bus use enable signal is asserted synchronously with a fall of the clock. Thereafter the bus control signals (BS, CSn, RAS, CASn, WEn, RD, RD/WR) become high impedance at a rise of the clock. These bus control signals are driven high at least 2 cycles before they become high impedance. Sampling for bus request signals occurs at the clock fall. The sequence when the bus is taken back from the slave is as follows. When the negation of BRLS is detected at a clock fall, high-level driving of the bus control signals starts half a cycle later. The bus use enable signal is then negated at the next clock fall. The address bus and data bus are driven starting at the next clock rise. The bus control signals are asserted and the bus cycle actually starts from the same clock rise at which the address and data signals are driven, at the earliest. Figure 7.58 shows the timing of bus arbitration. To reduce the overhead due to arbitration with a user-designed slave, a number of consecutive bus accesses may be attempted. In this case, to insure dependable refreshing, the design must provide for the slave to release the bus before it has held it for a period exceeding the refresh cycle. The SH7616 is provided with the REFOUT pin to send a signal requesting the bus while refresh execution is being kept waiting. REFOUT is asserted while refresh execution is being kept waiting until the bus is acquired. When the external slave device receives this signal and releases the bus, the bus is returned to the chip and refreshing can be executed.
Rev. 2.00 Mar 09, 2006 page 349 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
CKIO BRLS BGR Address data
CSn Other bus control signals
Figure 7.58 Bus Arbitration
7.10
7.10.1
Additional Items
Resets
The bus state controller is completely initialized only in a power-on reset. All signals are immediately negated, regardless of whether or not the chip is in the middle of a bus cycle. Signal negation is simultaneous with turning the output buffer off. All control registers are initialized. In standby mode, sleep mode, and a manual reset, no bus state controller control registers are initialized. When a manual reset is performed, the currently executing bus cycle only is completed, and then the chip waits for an access. When a cache-filling or DMAC/E-DMAC 16-byte transfer is executing, the CPU, DMAC, or E-DMAC that is the bus master ends the access in a longword unit, since the access request is canceled by the manual reset.This means that when a manual reset is executed during a cache filling, the cache contents can no longer be guaranteed. During a manual reset, the RTCNT does not count up, so no refresh request is generated, and a refresh cycle is not initiated. To preserve the data of the DRAM and synchronous DRAM, the pulse width of the manual reset must be shorter than the refresh interval. The bus-release operation of this LSI during a manual reset is described below. * BRLS signal is asserted before transition to manual reset state and continues to be asserted during manual reset In this LSI, the BGR signal is continuously asserted to retain the bus-release state. * BRLS signal is asserted before transition to manual reset state and negated during manual reset In this LSI, the BGR signal is negated to acquire the bus. * BRLS signal is asserted during manual reset In this LSI, the BGR signal is not asserted until the manual reset is released.
Rev. 2.00 Mar 09, 2006 page 350 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.10.2
Access as Viewed from CPU, DMAC or E-DMAC
The chip is internally divided into three buses: cache, internal, and peripheral. The CPU and cache memory are connected to the cache bus, the DMAC, E-DMAC and bus state controller are connected to the internal bus, and the low-speed peripheral devices and mode registers are connected to the peripheral bus. On-chip memory other than cache memory and the user break controller are connected to both the cache bus and the internal bus. The internal bus can be accessed from the cache bus, but not the other way around. The peripheral bus can be accessed from the internal bus, but not the other way around. This results in the following. The DMAC can access on-chip memory other than cache memory, but cannot access cache memory. When the DMAC causes a write to external memory, the external memory contents and the cache contents may be different. When external memory contents are rewritten by a DMA transfer, the cache memory must be purged by software if there is a possibility that the data for that address is present in the cache. When the CPU starts a read access, if the access is to a cache area, a cache search is first performed. This takes one cycle. If there is data in the cache, it fetches it and completes the access. If there is no data in the cache, a cache filling is performed via the internal bus, so four consecutive longword reads occur. For misses that occur when byte or word operands are accessed or branches occur to odd word boundaries (4n + 2 addresses), the filling is always performed by longword accesses on the chip-external interface. In the cache-through area, the access is to the actual access address. When the access is an instruction fetch, the access size is always longword. For cache-through areas and on-chip peripheral module read cycles, after an extra cycle is added to determine the cycle, the read cycle is started through the internal bus. Read data is sent to the CPU through the cache bus. When write cycles access the cache area, the cache is searched. When the data of the relevant address is found, it is written here. The actual write occurs in parallel to this via the internal bus in write-through mode. In write-back mode, the actual write is not performed until a replace operation occurs for the relevant address. When the right to use the internal bus is held, the CPU is notified that the write is completed without waiting for the end of the actual off-chip write. When the right to use the internal bus is not held, as when it is being used by the DMAC or the like, there is a wait until the bus is acquired before the CPU is notified of completion. Accesses to cache-through areas and on-chip peripheral modules work the same as in the cache area, except for the cache search and write. Because the bus state controller has one level of write buffer, the internal bus can be used for another access even when the chip-external bus cycle has not ended. After a write has been performed to low-speed memory off the chip, performing a read or write with an on-chip
Rev. 2.00 Mar 09, 2006 page 351 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
peripheral module enables an access to the on-chip peripheral module without having to wait for the completion of the write to low-speed memory. During reads, the CPU always has to wait for the end of the operation. To immediately continue processing after checking that the write to the device of actual data has ended, perform a dummy read access to the same address consecutively to check that the write has ended. The bus state controller's write buffer functions in the same way during accesses from the DMAC. A dual-address DMA transfer thus starts in the next read cycle without waiting for the end of the write cycle. When both the source address and destination address of the DMA are external spaces to the chip, however, it must wait until the completion of the previous write cycle before starting the next read cycle. The E-DMAC can perform access involving external memory, but not access involving any onchip memory or peripheral modules. 7.10.3 STATS1 and STATS0 Pins
The SH7616 has two pins, STATS1 and STATS0, to identify the bus master status. The signals output from these pins show the external access status. Encoded output is provided for the following categories: CPU (cache hit/cache disable), DMAC (external access only), E-DMAC, and Others (refresh, internal access, etc..). All output is synchronized with the address signals. The encoding patterns are shown in table 7.9, and the output timing in figure 7.59. Table 7.9 Encoding Patterns
STATS1 0 1 STATS0 0 1 0 1
Identification CPU DMAC E-DMAC Others
Rev. 2.00 Mar 09, 2006 page 352 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
CKIO Address CSn STATS1, 0 00 10 01 CPU CPU E-DMAC E-DMAC E-DMAC E-DMAC G-DMAC G-DMAC G-DMAC
Note: In on-chip I/O on-chip RAM or on-chip I/O memory transfers using the DMAC, accesses to on-chip I/O and on-chip RAM are included in the "Others" category.
Figure 7.59 STATS Output Timing 7.10.4 BUSHiZ Specification
The BUSHiZ pin is needed when the SH7616 is connected to a PCI controller via a PCI bridge, and the PCI master and SH7616 share local memory on the SH7616 bus. By using this pin in combination with the WAIT pin, it is possible to place the bus and specific control signals in the high-impedance state while keeping the SH7616's internal state halted. The conditions for establishing the high-impedance state, the applicable pins, and the bus timing (figure 7.60) are shown below. See the Application Note for an example of PCI bridge connection. * High-impedance conditions: Not dependent on BCR settings etc. when WAIT = L and BUSHiZ = L * Applicable pins: A[24:0], D[31:0], CS3, RD/WR, RD, RAS, CAS/OE, DQMLL/WE0, DQMLU/WE1, DQMUL/WE2, DQMUU/WE3 (total of 66 pins)
CKIO WAIT BUSHiZ Target pins Period
Figure 7.60 BUSHiZ Bus Timing 1. Can be used when memory is shared by the CPU and an external device. 2. When BUSHiZ is asserted after asserting WAIT, the CPU appears to release the bus. 3. When it becomes possible to access the shared memory, BUSHiZ is negated. 4. When the data is ready, WAIT is negated. This procedure allows the CPU and an external device to share memory.
Rev. 2.00 Mar 09, 2006 page 353 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.11
7.11.1
Usage Notes
Normal Space Access after Synchronous DRAM Write when Using DMAC
Negation of the DQMn/WEn signal in a synchronous DRAM write and CSn assertion in an immediately following normal space access both occur at the same rising edge of CKIO (figure 7.61). As there is a risk of an erroneous write to normal space in this case, when synchronous DRAM or a high-speed device is connected to normal space, it is recommended that CSn be delayed on the system side. Cases in which a synchronous DRAM write and normal space access occur consecutively are shown in table 7.10. Table 7.10 access sequence
Write to Synchronous DRAM CPU DMA DMA Normal Space Access DMA CPU DMA
Note: When an access by the CPU is performed immediately after a write by the CPU, internally the accesses are not consecutive.
Rev. 2.00 Mar 09, 2006 page 354 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
Normal space access T1
Synchronous DRAM write access Tr CKIO CS2 or CS3 RAS CAS RD/WR DQM/WEn CSn (a) Burst write mode Tc1 Tc2 Tc3 Tc4
Synchronous DRAM write access Tr CKIO CS2 or CS3 RAS CAS RD/WR DQM/WEn CSn Tc1
Normal space access T1
(b) Single write mode
Figure 7.61 Normal Space Access Immediately after Synchronous DRAM Write
Rev. 2.00 Mar 09, 2006 page 355 of 906 REJ09B0292-0200
Section 7 Bus State Controller (BSC)
7.11.2
When Using I: E Clock Ratio of 1: 1, 8-Bit Bus Width, and External Wait Input
When using an I: E clock ratio of 1: 1 and an 8-bit bus width, at least 1.5 address hold cycles should be set. Set a value other than the initial value in bits AnSHW1, AnSHW0, A4HW1, and A4HW0 for the relevant space. 7.11.3 When connecting external device to synchronous DRAM
When connecting an external device to the synchronous DRAM, not only CSnN and DACKn but also other instructions for the synchronous DRAM such as CSnN, RASN, CASN and RDWRN must be recognized for the estimation of an access sequence. In some cases, it is difficult to specify read and write cycles only with CSnN and DACKn.
Rev. 2.00 Mar 09, 2006 page 356 of 906 REJ09B0292-0200
Section 8 Cache
Section 8 Cache
8.1 Introduction
This chip incorporates 4 kbytes of four-way, mixed instruction/data type cache memory. This memory can also be used as 2-kbyte RAM and 2 kbyte mixed instruction/data type cache memory by making a setting in the cache control register (CCR) (two-way cache mode). CCR can specify that either instructions or data do not use cache. Both write-through and write-back modes are supported for cache operation. Each line of cache memory consists of 16 bytes. Cache memory is always updated in line units. Four 32-bit accesses are required to update a line. Since the number of entries is 64, the six bits (A9 to A4) in each address determine the entry. A four-way set associative configuration is used, so up to four different instructions/data can be stored in the cache even when entry addresses match. To efficiently use four ways having the same entry address, replacement is provided based on a pseudo-LRU (least-recently used) replacement algorithm. The cache configuration is shown in figure 8.1, and addresses in figure 8.2.
Cache address array Cache data array
Cache address bus LRU information Tag address
Cache data bus
U
V
Data (16 bytes/line)
Way 0 Way 1 Way 2 Way 3
64 entries
Tag address match signal V: Valid bit U: Update bit
Internal address bus
Internal data bus
Figure 8.1 Cache Configuration
Rev. 2.00 Mar 09, 2006 page 357 of 906 REJ09B0292-0200
Section 8 Cache
Bit Address Number of bits 3 Access space specification address 19 Tag address 6 4 Byte address in line 31 28 9 3 0
Entry address
Figure 8.2 Address Configuration 8.1.1 Register Configuration
Table 8.1 shows the cache register configuration. Table 8.1
Name Cache control register
Register Configuration
Abbrev. CCR R/W R/W Initial Value H'00 Address H'FFFFFE92
8.2
8.2.1
Register Description
Cache Control Register (CCR)
The cache control register (CCR) is used for cache control. CCR must be set and the cache must be initialized before use. CCR is initialized to H'00 by a power-on reset or manual reset.
Bit: Initial value: R/W: 7 W1 0 R/W 6 W0 0 R/W 5 WB 0 R/W 4 CP 0 R/W 3 TW 0 R/W 2 OD 0 R/W 1 ID 0 R/W 0 CE 0 R/W
Bits 7 and 6--Way Specification Bit (W1, W0): W1 and W0 specify the way when an address array is directly accessed by address specification.
Bit 7: W1 0 1 Bit 6: W0 0 1 0 1 Description Way 0 Way 1 Way 2 Way 3 (Initial value)
Rev. 2.00 Mar 09, 2006 page 358 of 906 REJ09B0292-0200
Section 8 Cache
Bit 5--Write-Back Bit (WB): Specifies the cache operation method when the cache area is accessed.
Bit 5: WB 0 1 Description Write-through Write-back (Initial value)
Bit 4--Cache Purge Bit (CP): When 1 is written to the CP bit, all cache entries and the valid bits, and LRU information of all ways are initialized to 0. After initialization is completed, the CP bit reverts to 0. The CP bit always reads 0.
Bit 4: CP 0 1 Description Normal operation Cache purge (Initial value)
Note: Always read 0.
Bit 3--Two-Way Mode (TW): TW is the two-way mode bit. The cache operates as a four-way set associative cache when TW is 0 and as a two-way set associative cache and 2-kbyte RAM when TW is 1. In the two-way mode, ways 2 and 3 are cache and ways 0 and 1 are RAM. Ways 0 and 1 are read or written by direct access of the data array according to address space specification.
Bit 3: TW 0 1 Description Four-way mode Two-way mode (Initial value)
Bit 2--Data Replacement Disable Bit (OD): OD is the bit for disabling data replacement. When this bit is 1, data fetched from external memory is not written to the cache even if there is a cache miss. Cache data is, however, read or updated during cache hits. OD is valid only when CE is 1.
Bit 2: OD 0 1 Description Normal operation Data not replaced even when cache miss occurs in data access (Initial value)
Rev. 2.00 Mar 09, 2006 page 359 of 906 REJ09B0292-0200
Section 8 Cache
Bit 1--Instruction Replacement Disable Bit (ID): ID is the bit for disabling instruction replacement. When this bit is 1, an instruction fetched from external memory is not written to the cache even if there is a cache miss. Cache data is, however, read or updated during cache hits. ID is valid only when CE is 1.
Bit 1: ID 0 1 Description Normal operation (Initial value) Data not replaced even when cache miss occurs in instruction fetch
Bit 0--Cache Enable Bit (CE): CE is the cache enable bit. Cache can be used when CE is set to 1.
Bit 0: CE 0 1 Description Cache disabled Cache enabled (Initial value)
8.3
Address Space and the Cache
The address space is divided into six partitions. The cache access operation is specified by addresses. Table 8.2 lists the partitions and their cache operations. For more information on address spaces, see section 7, Bus State Controller. Note that the spaces of the cache area and cache-through area are the same. Table 8.2 Address Space and Cache Operation
Cache Operation Cache is used when the CE bit in CCR is 1 Cache is not used Cache line of the specified address is purged (disabled) Cache address array is accessed directly Cache data array is accessed directly Cache is not used
Addresses A31-A29 Partition 000 001 010 011 110 111 Cache area Cache-through area Associative purge area Address array read/write area Data array read/write area I/O area
Rev. 2.00 Mar 09, 2006 page 360 of 906 REJ09B0292-0200
Section 8 Cache
8.4
8.4.1
Cache Operation
Cache Reads
This section describes cache operation when the cache is enabled and data is read from the CPU. One of the 64 entries is selected by the entry address part of the address output from the CPU on the cache address bus. The tag addresses of ways 0 through 3 are compared to the tag address parts of the addresses output from the CPU. When there is a way for which the tag address matches, this is called a cache hit (when any one of the way tag addresses and the tag address of the address output from the CPU match). In proper use, the tag addresses of each way differ from each other, and the tag address of only one way will match. When none of the way tag addresses match, it is called a cache miss. Tag addresses of entries with valid bits of 0 will not match in any case. When a cache hit occurs, data is read from the data array of the way that was matched according to the entry address, the byte address within the line, and the access data size, and is sent to the CPU. The address output on the cache address bus is calculated in the CPU's instruction execution phase and the results of the read are written during the CPU's write-back stage. The cache address bus and cache data bus both operate as pipelines in concert with the CPU's pipeline structure. From address comparison to data read requires 1 cycle; since the address and data operate as a pipeline, consecutive reads can be performed at each cycle with no waits (figure 8.3).
I CPU pipeline stage EX MA EX WB MA EX Cache address bus Address A Address B
Cache tag comparison Cache data bus Address A Address B
Data array read EX: Instruction execution MA: Memory access WB: Write-back
Figure 8.3 Read Access in Case of a Cache Hit
Rev. 2.00 Mar 09, 2006 page 361 of 906 REJ09B0292-0200
Section 8 Cache
When a cache miss occurs, the way for replacement is determined using the LRU information, and the read address from the CPU is written in the address array for that way. Simultaneously, the valid bit is set to 1. Since the 16 bytes of data for replacing the data array are simultaneously read, the address on the cache address bus is output to the internal address bus and 4 longwords are read consecutively. The access order is such that, for the address output to the internal address, the byte address within the line is sequentially incremented by 4, so that the longword that contains the address to be read from the cache comes last. The read data on the internal data bus is written sequentially to the cache data array. One cycle after the last data is written to the cache data array, it is also output to the cache data bus and the read data is sent to the CPU. The internal address bus and internal data bus also function as pipelines, just like the cache bus (figure 8.4).
I
CPU pipeline stage
EX
MA EX
WB MA
Cache address bus
Address A Cache tag comparison
Address B
Cache data bus Internal address bus Internal data bus
Data array write
Address A
Address A +4
Address A +8 Address A +4
Address A Address A +12 Address A +8 Address A +12
Address A
EX: Instruction execution MA: Memory access WB: Write-back
Figure 8.4 Read Access in Case of a Cache Miss
Rev. 2.00 Mar 09, 2006 page 362 of 906 REJ09B0292-0200
Section 8 Cache
8.4.2
Write Access
Write-Through Mode: Writing to external memory is performed regardless of whether or not there is a cache hit. The write address output to the cache address bus is used for comparison to the tag address of the cache's address array. If they match, the write data output to the cache data bus in the following cycle is written to the cache data array. If they do not match, nothing is written to the cache data array. The write address is output to the internal address bus 1 cycle later than the cache address bus. The write data is similarly output to the internal data bus 1 cycle later than the cache data bus. The CPU waits until the writes on the internal buses are completed (figure 8.5).
I EX MA EX MA
CPU pipeline stage Cache address bus Cache data bus
Address A
Address B
Cache tag comparison Address A Data array write Internal address bus Internal data bus EX: Instruction execution MA: Memory access Address A Address A Address B Address B
Figure 8.5 Write Access (Write-Through)
Rev. 2.00 Mar 09, 2006 page 363 of 906 REJ09B0292-0200
Section 8 Cache
Write-Back Mode: When a cache hit occurs, the data is written to the data array of the matching way according to the entry address, byte address in the line, and access data size, and the update bit of that entry is set to 1. A write is performed only to the data array, not to external memory. A write hit is completed in 2 cycles (figure 8.6).
I CPU pipeline stage EX MA EX MA EX Cache address bus
Address A
Address B
Address C
Cache tag comparison Cache data bus
Cache tag comparison Address B
Address A Data array write
EX: Instruction execution MA: Memory access
Figure 8.6 Write Access in Case of a Cache Hit (Write-Back) When a cache miss occurs, the way for replacement is determined using the LRU information, and the write address from the CPU is written in the address array for that way. Simultaneously, the valid bit and update bit are set to 1. Since the 16 bytes of data for replacing the data array are simultaneously read when the data on the cache bus is written to the cache, the address on the cache address bus is output to the internal address bus and 4 longwords are read consecutively. The access order is such that, for the address output to the internal address, the byte address within the line is sequentially incremented by 4, so that the longword that contains the address to be read from the cache comes last. The read data on the internal data bus is written sequentially to the cache data array. The internal address bus and internal data bus also function as pipelines, just like the cache bus (figure 8.7).
Rev. 2.00 Mar 09, 2006 page 364 of 906 REJ09B0292-0200
Section 8 Cache
I
CPU pipeline stage
EX
MA EX MA
Cache address bus Cache data bus
Address A Cache tag comparison
Address B Cache tag comparison Address A
Data array write Internal address bus Internal data bus
Address A +4
Address A +8 Address A +4
Address A +12 Address A +8
Address A
Address A +12
Address A
EX: Instruction execution MA: Memory access
Figure 8.7 Write Access in Case of a Cache Miss (Write-Back) When the update bit of an entry to be replaced in write-back mode is 1, write-back to external memory is necessary. To improve performance, the entry to be replaced is first transferred to the write-back buffer, and fetching of the new entry into the cache is given priority over the writeback. When the new entry has been fetched into the cache, the write-back buffer contents are written back to external memory. The cache can be accessed during this write-back. The write-back buffer can hold one cache line (16 bytes) of data and its address. The configuration of the write-back buffer is shown in figure 8.8.
A (31-4)
Longword 0
Longword 1
Longword 2
Longword 3
A (31-4): Address for write-back to external memory Longwords 0-3: One cache line of data for write-back to external memory
Figure 8.8 Write-Back Buffer Configuration
Rev. 2.00 Mar 09, 2006 page 365 of 906 REJ09B0292-0200
Section 8 Cache
8.4.3
Cache-Through Access
When reading or writing a cache-through area, the cache is not accessed. Instead, the cache address value is output to the internal address bus. For read operations, the read data output to the internal data bus is fetched and output to the cache data bus, as shown in figure 8.9. The read of the cache-through area is only performed on the address in question. For write operations, the write data on the cache data bus is output to the internal data bus. Writes on the cache through area are compared to the address tag; except for the fact that nothing is written to the data array, the operation is the same as the write shown in figure 8.5.
I CPU pipeline stage Cache address bus Cache data bus Internal address bus Internal data bus EX: Instruction execution MA: Memory access WB: Write-back Address A Address A EX MA EX Address B WB MA
Address A
Address A
Figure 8.9 Reading Cache-Through Areas 8.4.4 The TAS Instruction
The TAS instruction reads data from memory, compares it to 0, reflects the result in the T bit of the status register (SR), and sets the most significant bit to 1. It is an instruction that writes to the same address. Accesses to the cache area are handled in the same way as ordinary data accesses. 8.4.5 Pseudo-LRU and Cache Replacement
When a cache miss occurs during a read, the data of the missed address is read from 1 line (16 bytes) of memory and replaced. It is therefore necessary to decide which of the four ways is to be replaced. It can generally be expected that a way that has been infrequently used recently is also unlikely to be used next. This algorithm for replacing ways is called the least recently used replacement algorithm, or LRU. The hardware to implement it, however, is complex. For that
Rev. 2.00 Mar 09, 2006 page 366 of 906 REJ09B0292-0200
Section 8 Cache
reason, this cache uses a pseudo-LRU replacement algorithm that keeps track of the order of way access and replaces the oldest way. Six bits of data are used as the LRU information. The bits indicate the access order for 2 ways, as shown in figure 8.10. When the value is 1, access occurred in the direction of the appropriate arrow in the figure. The direction of the arrow can be determined by reading the bit. Access to the way to which all the arrows are pointing is the oldest, and that way becomes subject to replacement. The access order is recorded in the LRU information bits, so the LRU information is rewritten when a cache hit occurs during a read, when a cache hit occurs during a write, and when replacement occurs after a cache miss. Table 8.3 shows the rewrite values; table 8.4 shows how the way to be replaced is selected. After a cache purge by means of the CP bit in CCR, all the LRU information is zeroized, so the initial order of use is way 3 way 2 way 1 way 0. Thereafter, the way is selected according to the order of access in the program. Since the replacement will not be correct if the LRU gets an inappropriate value, the address array write function can be used to rewrite. When this is done, be sure not to write a value other than 0 as the LRU information. When the OD bit or ID bit in CCR is 1, cache replacement is not performed even if a cache miss occurs during data read or instruction fetch. Instead of replacing, the missed address data is read and directly transferred to the CPU. The two-way mode of the cache set by CCR's TW bit can only be implemented by replacing ways 2 and 3. Comparisons of address array tag addresses are carried out on all four ways even in twoway mode, so the valid bits of ways 1 and 0 must be cleared to 0 before beginning operation in two-way mode. Writing for the tag address and valid bit for cache replacement does not wait for the read from memory to be completed. If a memory access is aborted due to a reset, etc., during replacement, there will be a discrepancy between the cache contents and memory contents, so a purge must be performed.
Way 0 Bit 5 Bit 4 Way 1 Bit 2 Way 2 Bit 1 Way 3 Bit 0 Bit 3
Figure 8.10 LRU Information and Access Sequence
Rev. 2.00 Mar 09, 2006 page 367 of 906 REJ09B0292-0200
Section 8 Cache
Table 8.3
LRU Information after Update
Bit 5 Bit 4 0 -- 1 -- Bit 3 0 -- -- 1 Bit 2 -- 0 1 -- Bit 1 -- 0 -- 1 Bit 0 -- -- 0 1
Way 0 Way 1 Way 2 Way 3
0 1 -- --
Note: --: Holds the value before update.
Table 8.4
Selection Conditions for Replaced Way
Bit 5 Bit 4 1 -- 0 -- Bit 3 1 -- -- 0 Bit 2 -- 1 0 -- Bit 1 -- 1 -- 0 Bit 0 -- -- 1 0
Way 0 Way 1 Way 2 Way 3
1 0 -- --
Note: --: Don't care.
8.4.6
Cache Initialization
Purges of the entire cache area can only be carried out by writing 1 to the CP bit in CCR. Writing 1 to the CP bit initializes the valid bit of the address array, and all bits of the LRU information, to 0. Cache purges are completed in 1 cycle, but additional time is required for writing to CCR. Always initialize the valid bit and LRU before enabling the cache. When the cache is enabled, instructions are read from the cache even during writing to CCR. This means that the prefetched instructions are read from the cache. To do a proper purge, write 0 to CCR's CE bit, then disable the cache and purge. Since CCR's CE bit is cleared to 0 by a power-on reset or manual reset, the cache can be purged immediately by a reset. 8.4.7 Associative Purges
Associative purges invalidate 1 line (16 bytes) corresponding to specific address contents when the contents are in the cache. When the contents of a shared address are rewritten by one CPU in a multiprocessor configuration or a configuration in which the chip's internal E-DMAC (or DMAC) and CPU share memory, that address must be invalidated in the cache of the other CPU if it is present there.
Rev. 2.00 Mar 09, 2006 page 368 of 906 REJ09B0292-0200
Section 8 Cache
When writing to or reading the address obtained by adding H'40000000 to the address to be purged, the valid bit of the entry storing the address prior to addition are initialized to 0. 16 bytes are purged in each write, so a purge of 256 bytes of consecutive areas can be accomplished in 16 writes. Access sizes when associative purges are performed should be longword. A purge of 1 line requires 2 cycles. Also note that write-back (flushing) to the main memory is not performed if there is a dirty line in the cache.
Associative purge: Bit Address 31 29 28 010 Tag address 19 10 9 Entry address 6 43 -- 4 0
Number of bits 3
Figure 8.11 Associative Purge Access 8.4.8 Cache Flushing
When the CPU rewrites the contents of a specific shared address in the cache by write-back in a multiprocessor configuration or a configuration in which the chip's internal E-DMAC (or DMAC) and CPU share memory, the rewritten data must be written back to the main memory, and the cache contents invalidated, before the bus is granted by the CPU in the chip to another master (external master, E-DMAC, or DMAC). The chip does not support an instruction or procedure for flushing the contents of specific addresses, so in order to execute a cache flush it is necessary to perform reads in a 4-kbyte space (cache area) other than the address space to be flushed from cache, and intentionally create cache misses. For this purpose, cache accesses should be performed every 16 bytes. By this means, write-backs are generated and the contents written to the cache by the CPU in the chip are written back to the main memory, enabling flushing to be executed. However, this method incurs an overhead consisting of the cache fill time due to read misses and the time for rereading data to be left in the cache. Therefore, if the overhead due to use of the write-back method is of concern when constructing a system in which a number of masters share memory, the shared area should be made a cache-through area in order to maintain coherency. 8.4.9 Data Array Access
The cache data array can be read or written directly via the data array read/write area. Byte, word, or longword access can be used on the data array. Data array accesses are completed in 1 cycle for a read and 2 cycles for a write. Since only the cache bus is used, the operation can proceed in parallel even when another master, such as the DMAC, is using the bus. The data array of way 0 is
Rev. 2.00 Mar 09, 2006 page 369 of 906 REJ09B0292-0200
Section 8 Cache
mapped on H'C0000000 to H'C00003FF, way 1 on H'C0000400 to H'C00007FF, way 2 on H'C0000800 to H'C0000BFF and way 3 on H'C0000C00 to H'C0000FFF. When the two-way mode is being used, the area H'C0000000 to H'C00007FF is accessed as 2 kbytes of on-chip RAM. When the cache is disabled, the area H'C0000000 to H'C0000FFF can be used as 4 kbytes of on-chip RAM. When the contents of the way being used as cache are rewritten using a data array access, the contents of external memory and cache will not match, so this operation should be avoided.
Data array read/write: Bit Address 31 110 28 Tag address 19 31 Data 32 W: Way specification 12 11 10 9 Entry W address 6 3 BA 4 0 0
Number of bits 3 Bit Data Number of bits BA: Byte address within line
Figure 8.12 Data Array Access 8.4.10 Address Array Access
The address array of the cache can be accessed so that the contents fetched to the cache can be checked for purposes of program debugging or the like. The address array is mapped on H'60000000 to H'600003FF. Since all of the ways are mapped to the same addresses, ways are selected by rewriting the W1 and W0 bits in CCR. The address array can only be accessed in longwords. When the address array is read, the tag address, LRU information, and valid bit are output as data. When the address array is written to, the tag address, and valid bit are written from the cache address bus. The write address must therefore be calculated before the write is performed. LRU information is written from the cache data bus, but 0 must always be written to prevent malfunctions.
Rev. 2.00 Mar 09, 2006 page 370 of 906 REJ09B0292-0200
Section 8 Cache
Address array read: Bit Address 31 29 28 011 -- 19 31 29 28 -- Tag address 19 10 9 Entry address 6 43 -- 4 10 9 43 2 1 0 LRU -- V -- information 6 11 2 0
Number of bits 3 Bit Data Number of bits 3 Address array write: Bit Address 31 29 28 011
10 9 Tag address 19 31 -- 22
Number of bits 3 Bit Data Number of bits V: Valid bit
43 2 1 0 Entry -- V -- address 6 11 2 10 9 43 0 LRU -- information 6 4
Figure 8.13 Address Array Access
8.5
8.5.1
Cache Use
Initialization
Cache memory is not initialized in a reset. Therefore, the cache must be initialized by software before use. The cache is initialized by zeroizing all address array valid bits and LRU information. The address array write function can be used to initialize each line, but it is simpler to initialize it once by writing 1 to the CP bit in CCR. Figure 8.14 shows how to initialize the cache.
MOV.W MOV.B AND MOV.B OR MOV.B OR MOV.B #H'FE92, R1 @R1, R0 #H'FE, R0 #R0, @R1 #H'10, R0 R0, @R1 #H'01, R0 R0, R1 ; Cache enable ; Cache purge ; ; ; Cache disable
Figure 8.14 Cache Initialization
Rev. 2.00 Mar 09, 2006 page 371 of 906 REJ09B0292-0200
Section 8 Cache
8.5.2
Purge of Specific Lines
There is no snoop function (for monitoring data rewrites), so specific lines of cache must be purged when the contents of cache memory and external memory differ as a result of an operation. For instance, when a DMA transfer is performed to the cache area, cache lines corresponding to the rewritten address area must be purged. All entries of the cache can be purged by setting the CP bit in CCR to 1. However, it is efficient to purge only specific lines if only a limited number of entries are to be purged. An associative purge is used to purge specific lines. Since cache lines are 16 bytes long, purges are performed in a 16-byte units. The four ways are checked simultaneously, and only lines holding data corresponding to specified addresses are purged. When addresses do not match, the data at the specified address is not fetched to the cache, so no purge occurs.
; Purging 32 bytes from address R3 MOV.L XOR MOV.L ADD MOV.L #H'40000000, R0 R1, R1 R1, @(R0, R3) #16, R3 R1, @(R0, R3)
Figure 8.15 Purging Specific Addresses When it is troublesome to purge the cache after every DMA transfer, it is recommended that the OD bit in CCR be set to 1 in advance. When the OD bit is 1, the cache operates as cache memory only for instructions. However, when data is already fetched into cache memory, specific lines of cache memory must be purged for DMA transfers. 8.5.3 Cache Data Coherency
The cache memory does not have a snoop function. This means that when data is shared with a bus master other than the CPU, software must be used to ensure the coherency of data. For this purpose, the cache-through area can be used, or a cache purge can be performed with program logic using write-through. When the cache-through area is to be used, the data shared by the bus masters is placed in the cache-through area. This makes it easy to maintain data coherency, since access of the cachethrough area does not fetch data into the cache. When the shared data is accessed repeatedly and the frequency of data rewrites is low, a lower access speed can adversely affect performance.
Rev. 2.00 Mar 09, 2006 page 372 of 906 REJ09B0292-0200
Section 8 Cache
To purge the cache using program logic, the data updates are detected by the program flow and the cache is then purged. For example, if the program inputs data from a disk, whenever reading of a unit (such as a sector) is completed, the buffer address used for reading or the entire cache is purged, thereby maintaining coherency. When data is to be exchanged between two processors, only flags that provide mutual notification of completion of data preparation or completion of a fetch are placed in the cache-through area. The data actually to be transferred is placed in the cache area and the cache is purged before the first data read to maintain the coherency of the data. When semaphores are used as the means of communication, data coherency can be maintained even when the cache is not purged by utilizing the TAS instruction. Direct external access must always be used for a TAS instruction read. When the update unit is small, specific addresses can be purged, so only the relevant addresses are purged. When the update unit is larger, it is faster to purge the entire cache rather than purging all the addresses in order, and then read the data that previously existed in the cache again from external memory. When write-back is used, coherency can be maintained by executing write-backs (flushing) to memory by means of intentional cache miss reads, but since executing flushing incurs an overhead, use of write-through or accessing the cache-through area is recommended in a system in which a number of masters share memory. 8.5.4 Two-Way Cache Mode
The 4-kbyte cache can be used as 2-kbyte RAM and 2-kbyte mixed instruction/data cache memory by setting the TW bit in CCR to 1. Ways 2 and 3 become cache, and ways 0 and 1 become RAM. Initialization is performed by writing 1 to the CP bit in CCR, in the same way as with 4 ways. The valid bit, and LRU bits are cleared to 0. When LRU information is initialized to zero, the initial order of use is way 3 way 2. Thereafter, way 3 or way 2 is selected for replacement in accordance with the LRU information. The conditions for updating the LRU information are the same as for four-way mode, except that the number of ways is two. When designated as 2-kbyte RAM, ways 0 and 1 are accessed by data array access. Figure 8.16 shows the address mapping.
Rev. 2.00 Mar 09, 2006 page 373 of 906 REJ09B0292-0200
Section 8 Cache
H'00000000
H'C0000000 Way 0 H'C00003FF H'C0000400 Way 1 H'C00007FF
H'FFFFFFFF
Figure 8.16 Address Mapping of 2-kbyte RAM in the Two-Way Mode
8.6
8.6.1
Usage Notes
Standby
Disable the cache before entering the standby mode for power-down operation. After returning from standby, initialize the cache before use. 8.6.2 Cache Control Register
Changing the contents of CCR also changes cache operation. The chip makes full use of pipeline operations, so it is difficult to synchronize access. For this reason, change the contents of the cache control register simultaneously when disabling the cache or after the cache is disabled. After changing the CCR contents, perform a CCR read.
Rev. 2.00 Mar 09, 2006 page 374 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Section 9 Ethernet Controller (EtherC)
9.1 Overview
The SH7616 has an on-chip Ethernet controller (EtherC) conforming to the IEEE802.3 MAC (Media Access Control) layer standard. Connecting a physical-layer LSI (PHY-LSI) complying with this standard enables the Ethernet controller (EtherC) to perform transmission and reception of Ethernet/IEEE802.3 frames. The Ethernet controller is connected to dedicated transmit and receive Ethernet DMACs (E-DMACs) in the SH7616, and carries out high-speed data transfer to and from memory. 9.1.1 Features
The EtherC has the following features: * Transmission and reception of Ethernet/IEEE802.3 frames * Supports 10/100 Mbps transfer * Supports full-duplex and half-duplex modes * Conforms to IEEE802.3u standard MII (Media Independent Interface) * Magic Packet detection and Wake On LAN (WOL) signal output * CAM (Content Addressable Memory) match signal input function
Rev. 2.00 Mar 09, 2006 page 375 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.1.2
Configuration
Figure 9.1 shows the configuration of the Ethernet controller.
Transmit controller
MII
Receive controller
Command status interface
Figure 9.1 Configuration of Ethernet Controller (EtherC) Transmit Controller: Transmit data is stored in the transmit FIFO from memory via the transmit E-DMAC. The transmit controller assembles this data into an Ethernet/IEEE802.3 frame, which it outputs to the MII. After passing through the MII, the transmit data is sent onto the line by a PHYLSI. The main functions of the transmit controller are as follows: * Frame assembly and transmission * CRC calculation and provision to frames * Data retransmission in case of a collision (up to 15 times) * Compliant with MII in IEEE802.3u standard * Byte-nibble conversion supporting PHY-LSI speed
Rev. 2.00 Mar 09, 2006 page 376 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Receive Controller: After a frame is received via the MII, the receive controller carries out address information, frame length, CRC, and other checks, and the receive data is transferred to memory by the receive E-DMAC. The main functions of the receive controller are as follows: * Checking received frame format * Checking receive frame CRC and frame length * Transfer of own-address, multicast, or broadcast receive frames to memory * Compliant with MII in IEEE802.3u standard * Nibble-byte conversion supporting PHY-LSI speed * Magic Packet monitoring * CAM (Content Addressable Memory) match signal input function Command/Status Interface: This interface provides various command/status registers to control the EtherC, and performs access to PHY-LSI internal registers via the MII.
Rev. 2.00 Mar 09, 2006 page 377 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.1.3
Pin Configuration
The EtherC has signal pins compatible with the 18-pin MII specified in the IEEE802.3u standard, and three related signal pins to simplify connection to the PHY-LSI. The pin configuration are shown in table 9.1. Table 9.1
Type MII
MII Pin Functions
Name Transmit clock Receive clock Transmit enable I/O Input Input Output Function TX-EN, ETXD0 to ETXD3, TX-ER timing reference signal RX-DV, ERXD0 to ERXD3, RX-ER timing reference signal Indicates that transmit data is ready on ETXD0 to ETXD3 4-bit transmit data Notifies PHY-LSI of error during transmission Indicates that there is valid receive data on ERXD0 to ERXD3 4-bit receive data Identifies error state occurring during data reception Carrier detection signal Collision detection signal Reference clock signal for information transfer via MDIO Bidirectional signal for exchange of management information between STA and PHY Inputs link status from PHY-LSI External output pin Magic packet reception CAM match signal input function
Abbreviation TX-CLK RX-CLK TX-EN ETXD0- ETXD3 TX-ER RX-DV ERXD0- ERXD3 RX-ER CRS COL MDC MDIO
Transmit data (4-bit) Output Transmit error Receive data valid Receive data (4-bit) Receive error Carrier detect Collision detect Management data clock Management data input/output Link status General-purpose external output Wake-On-LAN CAM input Output Input Input Input Input Input Output Input/ output Input Output Output Input
Other
LNKSTA EXOUT WOL CAMSEN
Rev. 2.00 Mar 09, 2006 page 378 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.1.4
Ethernet Controller Register Configuration
The Ethernet controller (EtherC) has the nineteen 32-bit registers shown in table 9.2. Table 9.2
Name EtherC mode register EtherC status register EtherC interrupt permission register PHY interface register MAC address high register MAC address low register Receive flame length register PHY status register Transmit retry over counter register Single Collision detect counter register Delay Collision detect counter register Lost carrier counter register Carrier not detect counter register Illegal frame length counter register CRC error frame receive counter register Frame receive error counter register Too-short frame receive counter register Too-long frame receive counter register Residual-bit frame counter register Multicast address frame counter register
EtherC Registers
Abbreviation ECMR ECSR ECSIPR PIR MAHR MALR RFLR PSR TROCR SCDCR CDCR LCCR CNDCR IFLCR CEFCR FRECR TSFRCR TLFRCR RFCR MAFCR R/W R/W R/W * R/W R/W R/W R/W R/W R
2 R/W * 2 R/W * 2 R/W * 1
Initial Value H'00000000 H'00000000 H'00000000 H'0000000X H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000
Address H'FFFFFD60 H'FFFFFD64 H'FFFFFD68 H'FFFFFD6C H'FFFFFD70 H'FFFFFD74 H'FFFFFD78 H'FFFFFD7C H'FFFFFD80 H'FFFFFDB4 H'FFFFFD84 H'FFFFFD88 H'FFFFFD8C H'FFFFFD90 H'FFFFFD94 H'FFFFFD98 H'FFFFFD9C H'FFFFFDA0 H'FFFFFDA4 H'FFFFFDA8
R/W * 2 R/W *
2
R/W
*2
2 R/W * 2 R/W *
R/W * 2 R/W *
2
R/W
*2
2 R/W *
Notes: All registers must be accessed as 32-bit units. Reserved bits in a register should only be written with 0. The value read from a reserved bit is not guaranteed. 1. Individual bits are cleared by writing 1. 2. Cleared by a write to the register.
Rev. 2.00 Mar 09, 2006 page 379 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2
9.2.1
Register Descriptions
EtherC Mode Register (ECMR)
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 -- 0 R 7 -- 0 R 30 -- 0 R 14 -- 0 R 6 RE 0 R/W 29 -- 0 R 13 -- 0 R 5 TE 0 R/W ... ... ... ... 12 PRCEF 0 R/W 4 -- 0 R 19 -- 0 R 11 -- 0 R 3 ILB 0 R/W 18 -- 0 R 10 -- 0 R 2 ELB 0 R/W 17 -- 0 R 9 MPDE 0 R/W 1 DM 0 R/W 16 -- 0 R 8 -- 0 R 0 PRM 0 R/W
The EtherC mode register specifies the operating mode of the Ethernet controller. The settings in this register are normally made in the initialization process following a reset. Notes: Operation mode settings must not be changed while the transmitting and receiving functions are enabled. To modify bits other than the ECMR's RE and TE bits, follow the procedures below. 1. Return EtherC and E-DMAC to their initial state by means of the software reset bit (SWR) in the E-DMAC mode register (EDMR), and make new settings. 2. Set the RE and TE bits to 0 to disable them before modifying bits. Since a frame may be transmitted or received, wait for at least a maximum frame transfer time before changing bits other than the RE and TE bits. Bits 31 to 13--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 380 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Bit 12--Permit Receive CRC Error Frame (PRCEF): Specifies the treatment of a receive frame containing a CRC error.
Bit 12: PRCEF 0 1 Description Reception of a frame with a CRC error is treated as an error Reception of a frame with a CRC error is not treated as an error (Initial value)
Note: When this bit is set to 1, the CRC error frame counter register (CEFCR: see section 9.2.14) is not incremented when a CRC error is detected.
Bits 11 and 10--Reserved: These bits are always read as 0. The write value should always be 0. Bit 9--Magic Packet Detection Enable (MPDE): Enables or disables Magic Packet detection by hardware to allow activation from the Ethernet. When the Magic Packet is detected, it is reflected to the EtherC status register and the WOL pin notifies peripheral LSIs that the Magic Packet has been received.
Bit 9: MPDE 0 1 Description Magic Packet detection is not enabled Magic Packet detection is enabled (Initial value)
Bits 8 and 7--Reserved: These bits are always read as 0. The write value should always be 0. Bit 6--Receiver Enable (RE): Enables or disables the receiver.
Bit 6: RE 0 1 Description Receiver is disabled Receiver is enabled (Initial value)
Note: If a switch is made from the receiver-enabled state (RE = 1) to the receiver-disabled state (RE = 0) while a frame is being received, the receiver will not be disabled until reception of the frame is completed.
Bit 5--Transmitter Enable (TE): Enables or disables the transmitter.
Bit 5: TE 0 1 Description Transmitter is disabled Transmitter is enabled (Initial value)
Note: If a switch is made from the transmitter-enabled state (TE = 1) to the transmitter-disabled state (TE = 0) while a frame is being transmitted, the transmitter will not be disabled until transmission of the frame is completed.
Rev. 2.00 Mar 09, 2006 page 381 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Bit 4--Reserved: This bit is always read as 0. The write value should always be 0. Bit 3--Internal Loop Back Mode (ILB): Specifies loopback mode in the EtherC.
Bit 3: ILB 0 1 Description Normal data transmission/reception is performed Data loopback is performed inside the EtherC (Initial value)
Note: A loopback mode specification can only be made with full-duplex transfer (DM = 1 in this register).
Bit 2--External Loop Back Mode (ELB): The value in this register is output directly to the SH7616's general-purpose external output pin (EXOUT). This is used for loopback mode directives, etc., in the PHY-LSI, using the EXOUT pin.
Bit 2: ELB 0 1 Description Low-level output from EXOUT pin High-level output from EXOUT pin (Initial value)
Note: In order for PHY loopback to be implemented using this function, the PHY-LSI must have a pin corresponding to the EXOUT pin.
Bit 1--Duplex Mode (DM): Specifies the EtherC transfer method.
Bit 1: DM 0 1 Description Half-duplex transfer is specified Full-duplex transfer is specified (Initial value)
Note: When internal loopback mode is specified (ILB = 1), full-duplex transfer (DM = 1) must be used.
Bit 0--Promiscuous Mode (PRM): Setting this bit enables all Ethernet frames to be received.
Bit 0: PRM 0 1 Description EtherC performs normal operation EtherC performs promiscuous mode operation (Initial value)
Note: "All Ethernet frames" means all receivable frames, irrespective of differences or enabled/disabled status (destination address, broadcast address, multicast bit, etc.).
Rev. 2.00 Mar 09, 2006 page 382 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.2
EtherC Status Register (ECSR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 LCHNG 0 R/W * 9 -- 0 R 1 MPD 0 R/W * 8 -- 0 R 0 ICD 0 R/W *
Note: * The flag is cleared by writing 1. Writing 0 does not affect the flag.
The EtherC status register shows the internal status of the EtherC. This status information can be reported to the CPU by means of interrupts. Individual bits are cleared by writing 1 to them. For bits that generate an interrupt, the interrupt can be enabled or disabled by means of the corresponding bit in the EtherC status interrupt permission register (ECSIPR). Bits 31 to 3--Reserved: These bits are always read as 0. The write value should always be 0. Bit 2--LINK Signal Changed (LCHNG): Indicates that the LNKSTA signal input from the PHYLSI has changed from high to low, or from low to high. This bit is cleared by writing 1 to it. Writing 0 to this bit has no effect.
Bit 2: LCHNG 0 1 Description LNKSTA signal change has not been detected (Initial value) LNKSTA signal change (high-to-low or low-to-high) has been detected
Notes: 1. The current link status can be checked by referencing the LMON bit in the PHY interface status register (PSR). 2. Signal variation may be detected when the LNKSTA function is selected by the port A control register (PACR) of the pin function controller (PFC).
Bit 1--Magic Packet Detection (MPD): Indicates that a Magic Packet has been detected on the line. This bit is cleared by writing 1 to it. Writing 0 to this bit has no effect.
Bit 1: MPD 0 1 Description Magic Packet has not been detected Magic Packet has been detected (Initial value)
Rev. 2.00 Mar 09, 2006 page 383 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Bit 0--Illegal Carrier Detection (ICD): Indicates that PHY-LSI has detected an illegal carrier on the line. This bit is cleared by writing 1 to it. Writing 0 to this bit has no effect.
Bit 0: ICD 0 1 Description PHY-LSI has not detected an illegal carrier on the line PHY-LSI has detected an illegal carrier on the line (Initial value)
Note: If a change in the signal input from the PHY-LSI occurs before the software recognition period, the correct information may not be obtained. Refer to the timing specification for the PHY-LSI used.
9.2.3
EtherC Interrupt Permission Register (ECSIPR)
Bit: Initial value: R/W: Bit: 31 -- 0 R 7 -- Initial value: R/W: 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 LCHNGI P 0 R/W 9 -- 0 R 1 MPDIP 0 R/W 8 -- 0 R 0 ICDIP 0 R/W
This register enables or disables the interrupt sources indicated by the EtherC status register. Each bit in this register enables or disables the interrupt indicated by the corresponding bit in the EtherC status register. Bits 31 to 3--Reserved: These bits are always read as 0. The write value should always be 0. Bit 2-- LINK Signal Changed Interrupt Permission (LCHNGIP): Controls interrupt notification by the LINK Signal Changed bit.
Bit 2: LCHNGIP 0 1 Description Interrupt notification by LCHNG bit in ECSR is disabled Interrupt notification by LCHNG bit in ECSR is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 384 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Bit 1--Magic Packet Detection Interrupt Permission (MPDIP): Controls interrupt notification by the Magic Packet Detection bit.
Bit 1: MPDIP 0 1 Description Interrupt notification by MPD bit in ECSR is disabled Interrupt notification by MPD bit in ECSR is enabled (Initial value)
Bit 0--Illegal Carrier Detection Interrupt Permission (ICDIP): Controls interrupt notification by the Illegal Carrier Detection bit.
Bit 0: ICDIP 0 1 Description Interrupt notification by ICD bit in ECSR is disabled Interrupt notification by ICD bit in ECSR is enabled (Initial value)
9.2.4
PHY Interface Register (PIR)
Bit: Initial value: R/W: Bit: Initial value: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 MDI * R 10 -- 0 R 2 MDO 0 R/W 9 -- 0 R 1 MMD 0 R/W 8 -- 0 R 0 MDC 0 R/W
R/W: Note: * Undefined
PIR provides a means of accessing PHY-LSI internal registers via the MII. Bits 31 to 4--Reserved: These bits are always read as 0. The write value should always be 0. Bit 3-- MII Management Data-In (MDI): Indicates the level of the MDIO pin. Bit 2-- MII Management Data-Out (MDO): Outputs the value set to this bit by the MDIO pin when the MMD bit is 1. Bit 1-- MII Management Mode (MMD): Specifies the data read/write direction with respect to the MII. Read direction is indicated by 0, and write direction by 1.
Rev. 2.00 Mar 09, 2006 page 385 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Bit 0-- MII Management Data Clock (MDC): Outputs the value set to this bit by the MDC pin and supplies the MII with the management data clock. For the method of accessing MII registers, see section 9.3.4, Accessing MII Registers. 9.2.5 MAC Address High Register (MAHR)
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 MA47 0 R/W 23 MA39 0 R/W 15 MA31 0 R/W 7 MA23 0 R/W 30 MA46 0 R/W 22 MA38 0 R/W 14 MA30 0 R/W 6 MA22 0 R/W 29 MA45 0 R/W 21 MA37 0 R/W 13 MA29 0 R/W 5 MA21 0 R/W 28 MA44 0 R/W 20 MA36 0 R/W 12 MA28 0 R/W 4 MA20 0 R/W 27 MA43 0 R/W 19 MA35 0 R/W 11 MA27 0 R/W 3 MA19 0 R/W 26 MA42 0 R/W 18 MA34 0 R/W 10 MA26 0 R/W 2 MA18 0 R/W 25 MA41 0 R/W 17 MA33 0 R/W 9 MA25 0 R/W 1 MA17 0 R/W 24 MA40 0 R/W 16 MA32 0 R/W 8 MA24 0 R/W 0 MA16 0 R/W
The upper 32 bits of the 48-bit MAC address are set in MARH. The setting in this register is normally made in the initialization process after a reset. Note: The MAC address setting must not be changed while the transmitter and receiver are enabled. First return the EtherC and E-DMAC modules to their initial state by means of the SWR bit in the E-DMAC mode register (EDMR), then make the new setting. Bits 31 to 0--MAC Address Bits 47 to 16 (MA47 to MA16): Used to set the upper 32 bits of the MAC address. Note: If the MAC address to be set in the SH7616 is 01-23-45-67-89-AB (hexadecimal), the value set in this register is H'01234567.
Rev. 2.00 Mar 09, 2006 page 386 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.6
MAC Address Low Register (MALR)
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 MA15 0 R/W 7 MA7 0 R/W 30 -- 0 R 14 MA14 0 R/W 6 MA6 0 R/W 29 -- 0 R 13 MA13 0 R/W 5 MA5 0 R/W 12 MA12 0 R/W 4 MA4 0 R/W ... ... ... 19 -- 0 R 11 MA11 0 R/W 3 MA3 0 R/W 18 -- 0 R 10 MA10 0 R/W 2 MA2 0 R/W 17 -- 0 R 9 MA9 0 R/W 1 MA1 0 R/W 16 -- 0 R 8 MA8 0 R/W 0 MA0 0 R/W
The lower 16 bits of the 48-bit MAC address are set in MARL. The setting in this register is normally made in the initialization process after a reset. Note: The MAC address setting must not be changed while the transmitter and receiver are enabled. First return the EtherC and E-DMAC modules to their initial state by means of the SWR bit in the E-DMAC mode register (EDMR), then make the new setting. Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--MAC Address Bits 15 to 0 (MA15 to MA0): Used to set the lower 16 bits of the MAC address. Note: If the MAC address to be set in the SH7616 is 01-23-45-67-89-AB (hexadecimal), the value set in this register is H'000089AB.
Rev. 2.00 Mar 09, 2006 page 387 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.7
Receive Frame Length Register (RFLR)
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 -- 0 R 7 RFL7 0 R/W 30 -- 0 R 14 -- 0 R 6 RFL6 0 R/W 29 -- 0 R 13 -- 0 R 5 RFL5 0 R/W ... ... ... ... 12 -- 0 R 4 RFL4 0 R/W 19 -- 0 R 11 RFL11 0 R/W 3 RFL3 0 R/W 18 -- 0 R 10 RFL10 0 R/W 2 RFL2 0 R/W 17 -- 0 R 9 RFL9 0 R/W 1 RFL1 0 R/W 16 -- 0 R 8 RFL8 0 R/W 0 RFL0 0 R/W
This register specifies the maximum frame length (in bytes) that can be received by the SH7616 Bits 31 to 12--Reserved: These bits are always read as 0. The write value should always be 0. Bits 11 to 0--Receive Frame Length (RFL)
H'000-H'5EE H'5EF H'5F0 . . . H'7FF H'800-H'FFF 1,518 bytes 1,519 bytes 1,520 bytes . . . 2,047 bytes 2,048 bytes
Notes: 1. The frame length refers to all fields from the destination address up to and including the CRC data. 2. When data that exceeds the specified value is received, the part of the data that is higher than the specified value is discarded. Frame contents from the destination address up to and including the data are actually transferred to memory. CRC data is not included in the transfer.
Rev. 2.00 Mar 09, 2006 page 388 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.8
PHY Interface Status Register (PSR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 LMON 0 R
PSR enables interface signals from the PHY-LSI to be read. Bits 31 to 1--Reserved: These bits are always read as 0. The write value should always be 0. Bit 0-- Link Monitor (LMON): The link status can be read by connecting the LINK signal output from the PHY-LSI. For information on the polarity, refer to the specifications for the PHY-LSI to be connected. Note: The LMON bit is set to 0 when the LNKSTA pin is at high level, and it is set to 1 when the LNKSTA pin is at low level.
Rev. 2.00 Mar 09, 2006 page 389 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.9
Transmit Retry Over Counter Register (TROCR)
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 0 R/W 7 TROC7 0 R/W 30 -- 0 R 14 0 R/W 6 TROC6 0 R/W 29 -- 0 R 13 0 R/W 5 TROC5 0 R/W ... ... ... ... 12 0 R/W 4 TROC4 0 R/W 19 -- 0 R 11 0 R/W 3 TROC3 0 R/W 18 -- 0 R 10 0 R/W 2 TROC2 0 R/W 17 -- 0 R 9 0 R/W 1 TROC1 0 R/W 16 -- 0 R 8 TROC8 0 R/W 0 TROC0 0 R/W
TROC15 TROC14 TROC13 TROC12 TROC11 TROC10 TROC9
TROCR is a 16-bit counter that indicates the number of frames that were unable to be transmitted in 16 retransmission attempts. When 16 transmission attempts have failed, TROCR is incremented by 1. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Transmit Retry Over Count 15 to 0 (TROC15 to TROC0): These bits indicate the number of frames that were unable to be transmitted in 16 retransmission attempts.
Rev. 2.00 Mar 09, 2006 page 390 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.10
Single Collision Detect Counter Register (SCDCR)
This register is a 32-bit counter that indicates the number of collisions on all lines from a start of transmission. When the value in this register reaches H'FFFFFFFF, count-up is halted. The counter's value is cleared to 0 by writing to this register. The value written is "don't care".
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R/W 23 0 R/W 15 0 R/W 7 0 R/W 30 0 R/W 22 0 R/W 14 0 R/W 6 0 R/W 29 0 R/W 21 0 R/W 13 0 R/W 5 0 R/W 28 0 R/W 20 0 R/W 12 0 R/W 4 0 R/W 27 0 R/W 19 0 R/W 11 0 R/W 3 0 R/W 26 0 R/W 18 0 R/W 10 0 R/W 2 0 R/W 25 0 R/W 17 0 R/W 9 0 R/W 1 0 R/W 24 0 R/W 16 0 R/W 8 0 R/W 0 0 R/W
COSDC31 COSDC30 COSDC29 COSDC28 COSDC27 COSDC26 COSDC25 COSDC24
COSDC23 COSDC22 COSDC21 COSDC20 COSDC19 COSDC18 COSDC17 COSDC16
COSDC15 COSDC14 COSDC13 COSDC12 COSDC11 COSDC10 COSDC9 COSDC8
COSDC7 COSDC6 COSDC5 COSDC4 COSDC3 COSDC2 COSDC1 COSDC0
Bits 31 to 0-- Collision Detect Count 31 to 0 (COSDC31 to COSDC0): These bits indicate the number of collisions from a start of transmission.
Rev. 2.00 Mar 09, 2006 page 391 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.11
Delay Collision Detect Counter Register (CDCR)
Bit: 31 -- 0 R 15 30 -- 0 R 14 29 -- 0 R 13 ... ... ... ... 12 19 -- 0 R 11 18 -- 0 R 10 17 -- 0 R 9 16 -- 0 R 8
Initial value: R/W: Bit:
COLDC1 COLDC1 COLDC1 COLDC1 COLDC1 COLDC1 COLDC9 COLDC8 5 4 3 2 1 0 Initial value: R/W: Bit: Initial value: R/W: 0 R/W 7 0 R/W 0 R/W 6 0 R/W 0 R/W 5 0 R/W 0 R/W 4 0 R/W 0 R/W 3 0 R/W 0 R/W 2 0 R/W 0 R/W 1 0 R/W 0 R/W 0 0 R/W
COLDC7 COLDC6 COLDC5 COLDC4 COLDC3 COLDC2 COLDC1 COLDC0
CDCR is a 16-bit counter that indicates the number of collisions that occurred on the line, counting from a point 512 bits after the start of data transmission. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Collision Detect Count 15 to 0 (COLDC15 to COLDC0): These bits indicate the count of collisions from a point 512 bits after the start of data transmission.
Rev. 2.00 Mar 09, 2006 page 392 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.12
Lost Carrier Counter Register (LCCR)
Bit: 31 -- 0 R 15 LCC15 0 R/W 7 LCC7 0 R/W 30 -- 0 R 14 LCC14 0 R/W 6 LCC6 0 R/W 29 -- 0 R 13 LCC13 0 R/W 5 LCC5 0 R/W ... ... ... ... 12 LCC12 0 R/W 4 LCC4 0 R/W 19 -- 0 R 11 LCC11 0 R/W 3 LCC3 0 R/W 18 -- 0 R 10 LCC10 0 R/W 2 LCC2 0 R/W 17 -- 0 R 9 LCC9 0 R/W 1 LCC1 0 R/W 16 -- 0 R 8 LCC8 0 R/W 0 LCC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
LCCR is a 16-bit counter that indicates the number of times the carrier was lost during data transmission. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Lost Carrier Count 15 to 0 (LCC15 to LCC0): These bits indicate the number of times the carrier was lost during data transmission.
Rev. 2.00 Mar 09, 2006 page 393 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.13
Carrier Not Detect Counter Register (CNDCR)
Bit: 31 -- 0 R 15 0 R/W 7 CNDC7 0 R/W 30 -- 0 R 14 0 R/W 6 CNDC6 0 R/W 29 -- 0 R 13 0 R/W 5 CNDC5 0 R/W ... ... ... ... 12 0 R/W 4 CNDC4 0 R/W 19 -- 0 R 11 0 R/W 3 CNDC3 0 R/W 18 -- 0 R 10 0 R/W 2 CNDC2 0 R/W 17 -- 0 R 9 0 R/W 1 CNDC1 0 R/W 16 -- 0 R 8 CNDC8 0 R/W 0 CNDC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
CNDC15 CNDC14 CNDC13 CNDC12 CNDC11 CNDC10 CNDC9
CNDCR is a 16-bit counter that indicates the number of times the carrier could not be detected while the preamble was being sent. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Carrier Not Detect Count 15 to 0 (CNDC15 to CNDC0): These bits indicate the number of times the carrier was not detected.
Rev. 2.00 Mar 09, 2006 page 394 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.14
Illegal Frame Length Counter Register (IFLCR)
Bit: 31 -- 0 R 15 IFLC15 0 R/W 7 IFLC7 0 R/W 30 -- 0 R 14 IFLC14 0 R/W 6 IFLC6 0 R/W 29 -- 0 R 13 IFLC13 0 R/W 5 IFLC5 0 R/W ... ... ... ... 12 IFLC12 0 R/W 4 IFLC4 0 R/W 19 -- 0 R 11 IFLC11 0 R/W 3 IFLC3 0 R/W 18 -- 0 R 10 IFLC10 0 R/W 2 IFLC2 0 R/W 17 -- 0 R 9 IFLC9 0 R/W 1 IFLC1 0 R/W 16 -- 0 R 8 IFLC8 0 R/W 0 IFLC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
IFLCR is a 16-bit counter that indicates the number of times transmission of a packet with a frame length of less than four bytes was attempted during data transmission. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Illegal Frame Length Count 15 to 0 (IFLC15 to IFLC0): These bits indicate the count of illegal frame length transmission attempts.
Rev. 2.00 Mar 09, 2006 page 395 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.15
CRC Error Frame Counter Register (CEFCR)
Bit: 31 -- 0 R 15 0 R/W 7 CEFC7 0 R/W 30 -- 0 R 14 0 R/W 6 CEFC6 0 R/W 29 -- 0 R 13 0 R/W 5 CEFC5 0 R/W ... ... ... ... 12 0 R/W 4 CEFC4 0 R/W 19 -- 0 R 11 0 R/W 3 CEFC3 0 R/W 18 -- 0 R 10 0 R/W 2 CEFC2 0 R/W 17 -- 0 R 9 0 R/W 1 CEFC1 0 R/W 16 -- 0 R 8 CEFC8 0 R/W 0 CEFC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
CEFC15 CEFC14 CEFC13 CEFC12 CEFC11 CEFC10 CEFC9
CEFCR is a 16-bit counter that indicates the number of times a frame with a CRC error was received. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--CRC Error Frame Count 15 to 0 (CEFC15 to CEFC0): These bits indicate the count of CRC error frames received. Note: When the Permit Receive CRC Error Frame bit (PRCEF) is set to 1 in the EtherC Mode Register (ECMR), CEFCR is not incremented by reception of a frame with a CRC error.
Rev. 2.00 Mar 09, 2006 page 396 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.16
Frame Receive Error Counter Register (FRECR )
Bit: 31 -- 0 R 15 0 R/W 7 FREC7 0 R/W 30 -- 0 R 14 0 R/W 6 FREC6 0 R/W 29 -- 0 R 13 0 R/W 5 FREC5 0 R/W ... ... ... ... 12 0 R/W 4 FREC4 0 R/W 19 -- 0 R 11 0 R/W 3 FREC3 0 R/W 18 -- 0 R 10 0 R/W 2 FREC2 0 R/W 17 -- 0 R 9 0 R/W 1 FREC1 0 R/W 16 -- 0 R 8 FREC8 0 R/W 0 FREC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
FREC15 FREC14 FREC13 FREC12 FREC11 FREC10 FREC9
FRECR is a 16-bit counter that indicates the number of frames input from the PHY-LSI for which a receive error was indicated by the RX-ER pin. FRECR is incremented each time this pin becomes active. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Frame Receive Error Count 15 to 0 (FREC15 to FREC0): These bits indicate the count of errors during frame reception.
Rev. 2.00 Mar 09, 2006 page 397 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.17
Too-Short Frame Receive Counter Register (TSFRCR)
Bit: 31 -- 0 R 15 0 R/W 7 TSFC7 0 R/W 30 -- 0 R 14 0 R/W 6 TSFC6 0 R/W 29 -- 0 R 13 0 R/W 5 TSFC5 0 R/W ... ... ... ... 12 0 R/W 4 TSFC4 0 R/W 19 -- 0 R 11 0 R/W 3 TSFC3 0 R/W 18 -- 0 R 10 0 R/W 2 TSFC2 0 R/W 17 -- 0 R 9 TSFC9 0 R/W 1 TSFC1 0 R/W 16 -- 0 R 8 TSFC8 0 R/W 0 TSFC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
TSFC15 TSFC14 TSFC13 TSFC12 TSFC11 TSFC10
TSFRCR is a 16-bit counter that indicates the number of frames of fewer than 64 bytes that have been received. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Too-Short Frame Receive Count 15 to 0 (TSFC15 to TSFC0): These bits indicate the count of frames received with a length of less than 64 bytes.
Rev. 2.00 Mar 09, 2006 page 398 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.18
Too-Long Frame Receive Counter Register (TLFRCR)
Bit: 31 -- 0 R 15 0 R/W 7 TLFC7 0 R/W 30 -- 0 R 14 0 R/W 6 TLFC6 0 R/W 29 -- 0 R 13 0 R/W 5 TLFC5 0 R/W ... ... ... ... 12 0 R/W 4 TLFC4 0 R/W 19 -- 0 R 11 0 R/W 3 TLFC3 0 R/W 18 -- 0 R 10 0 R/W 2 TLFC2 0 R/W 17 -- 0 R 9 TLFC9 0 R/W 1 TLFC1 0 R/W 16 -- 0 R 8 TLFC8 0 R/W 0 TLFC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
TLFC15 TLFC14 TLFC13 TLFC12 TLFC11 TLFC10
TLFRCR is a 16-bit counter that indicates the number of frames received with a length exceeding the value specified by the receive frame length register (RFLR). When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Too-Long Frame Receive Count 15 to 0 (TLFC15 to TLFC0): These bits indicate the count of frames received with a length exceeding the value in RFLR. Notes: If the value specified by RFLR is 1518 bytes, TLFRCR is incremented by reception of a frame with a length of 1519 bytes or more. TLFRCR is not incremented when a frame containing residual bits is received. In this case, the reception of the frame is indicated in the residual-bit frame counter register (RFCR).
Rev. 2.00 Mar 09, 2006 page 399 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.19
Residual-Bit Frame Counter Register (RFCR)
Bit: 31 -- 0 R 15 RFC15 0 R/W 7 RFC7 0 R/W 30 -- 0 R 14 RFC14 0 R/W 6 RFC6 0 R/W 29 -- 0 R 13 RFC13 0 R/W 5 RFC5 0 R/W ... ... ... ... 12 RFC12 0 R/W 4 RFC4 0 R/W 19 -- 0 R 11 RFC11 0 R/W 3 RFC3 0 R/W 18 -- 0 R 10 RFC10 0 R/W 2 RFC2 0 R/W 17 -- 0 R 9 RFC9 0 R/W 1 RFC1 0 R/W 16 -- 0 R 8 RFC8 0 R/W 0 RFC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
RFCR is a 16-bit counter that indicates the number of frames received containing residual bits (less than an 8-bit unit). When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Residual-Bit Frame Count 15 to 0 (RFC15 to RFC0): These bits indicate the count of frames received containing residual bits.
Rev. 2.00 Mar 09, 2006 page 400 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.2.20
Multicast Address Frame Counter Register (MAFCR)
Bit: 31 -- 0 R 15 0 R/W 7 MAFC7 0 R/W 30 -- 0 R 14 0 R/W 6 MAFC6 0 R/W 29 -- 0 R 13 0 R/W 5 MAFC5 0 R/W ... ... ... ... 12 0 R/W 4 MAFC4 0 R/W 19 -- 0 R 11 0 R/W 3 MAFC3 0 R/W 18 -- 0 R 10 0 R/W 2 MAFC2 0 R/W 17 -- 0 R 9 0 R/W 1 MAFC1 0 R/W 16 -- 0 R 8 MAFC8 0 R/W 0 MAFC0 0 R/W
Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W:
MAFC15 MAFC14 MAFC13 MAFC12 MAFC11 MAFC10 MAFC9
MAFCR is a 16-bit counter that indicates the number of frames received with a multicast address specified. When the value in this register reaches H'FFFF (65,535), the count is halted. The counter value is cleared to 0 by a write to this register (the write value is immaterial). Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 to 0--Multicast Address Frame Count 15 to 0 (MAFC15 to MAFC0): These bits indicate the count of multicast frames received.
Rev. 2.00 Mar 09, 2006 page 401 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.3
Operation
When a transmit command is issued from the transmit E-DMAC, the EtherC starts transmission in accordance with a predetermined transmission procedure. When the specified number of words have been transferred, transmission of one frame is terminated. When an own-address frame (including a broadcast frame) is received, the EtherC transfers the frame to the receive E-DMAC while carrying out format checks. At the end of frame reception the EtherC carries out a CRC check, completing reception of one frame. Notes: 1. In actual EtherC operation, frame transmission and reception is performed continuously in combination with the E-DMACs. For details of continuous operation, see the description of E-DMAC operation. 2. The receive data transferred to memory by the receive data E-DMAC does not include CRC data. 9.3.1 Transmission
The main transmit functions of the EtherC are as follows: * Frame generation and transmission: Monitors the line status, then adds the preamble, SFD, and CRC to the data to be transmitted, and sends it to the MII * CRC generation: Generates the CRC for the data field, and adds it to the transmit frame * Transmission retry: when a collision is detected in the collision window (during the transmission of the 512-bit data that includes the preamble and SFD from the start of transmission), transmission is retried up to 15 times based on the back-off algorithm The state transitions of the EtherC transmitter are shown in figure 9.2.
Rev. 2.00 Mar 09, 2006 page 402 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
TE set
Idle
FDPX
Start of transmission (preamble transmission)
Transmission halted
HDPX TE reset
Carrier Carrier detection non-detection Retransmission initiation Collision Carrier detection Retransmission processing*1 Carrier non-detection Collision Carrier detection HDPX FDPX
Carrier detection Reset
Failure of 15 retransmission attempts or collision after 512-bit time Error detection
SFD transmission Error Collision*2 Error Data transmission
Error notification
Collision*2 Error
Normal transmission
CRC transmission
Notes: 1. Transmission retry processing includes both jam transmission that depends on collision detection and the adjustment of transmission intervals based on the back-off algorithm. 2. Transmission is retried only when data of 512 bits or less (including the preamble and SFD) is transmitted. When a collision is detected during the transmission of data greater than 512 bits, only jam is transmitted and transmission based on the back-off algorithm is not retried.
Figure 9.2 EtherC Transmitter State Transitions 1. When the transmit enable (TE) bit is set, the transmitter enters the transmit idle state. 2. When a transmit request is issued by the transmit E-DMAC, the EtherC sends the preamble after a transmission delay equivalent to the frame interval time.
Note: If full-duplex transfer is selected, which does not require carrier detection, the preamble is sent as soon as a transmit request is issued by the transmit E-DMAC. 3. The transmitter sends the SFD, data, and CRC sequentially. At the end of transmission, the transmit E-DMAC generates a transmission complete interrupt (TC).
Rev. 2.00 Mar 09, 2006 page 403 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Note: If a collision or the carrier-not-detected state occurs during data transmission, these are reported as interrupt sources. 4. After waiting for the frame interval time, the transmitter enters the idle state, and if there is more transmit data, continues transmitting. 9.3.2 Reception
The EtherC receiver separates a received frame into preamble, SFD, data, and CRC, and the fields from DA (destination address) to the CRC data are transferred to the receive E-DMAC. The main receive functions of the EtherC are as follows: * Receive frame header check: Checks the preamble and SFD, and discards a frame with an invalid pattern * Receive frame data check: Checks the data length in the header, and reports an error status if the data length is less than 64 bytes or greater than the specified number of bytes * Receive CRC check: Performs a CRC check on the frame data field, and reports an error status in the case of an abnormality * Line status monitoring: Reports an error status if an illegal carrier is detected by means of the fault detection signal from the PHY-LSI * Magic Packet monitoring: Detects a Magic Packet from all receive frames The state transitions of the EtherC receiver are shown in figure 9.3.
Rev. 2.00 Mar 09, 2006 page 404 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
Illegal carrier detection Rx-DV negation
Idle RE set Preamble detection
Start of frame reception
Wait for SFD reception SFD reception
Reception halted
RE reset
Promiscuous and other station destination address
Destination address reception Own destination address or broadcast or multicast or promiscuous
Reset
Error notification
Error detection
Receive error detection
Data reception
Receive error detection
End of reception
Normal reception SFD: Start frame delimiter Note: The error frame also transmits data to the buffer.
CRC reception
Figure 9.3 EtherC Receiver State Transitions 1. When the receive enable (RE) bit is set, the receiver enters the receive idle state. 2. When an SFD (start frame delimiter) is detected after a receive packet preamble, the receiver starts receive processing. 3. If the destination address matches the receiver's own address, or if broadcast or multicast transmission or promiscuous mode is specified, the receiver starts data reception. 4. Following data reception, the receiver carries out a CRC check. The result is indicated as a status bit in the descriptor after the frame data has been written to memory. 5. After one frame has been received, if the receive enable bit is set (RE = 1) in the EtherC mode register, the receiver prepares to receive the next frame.
Rev. 2.00 Mar 09, 2006 page 405 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.3.3
MII Frame Timing
Figures 9.4 (a) to (f) show the timing for various kinds of MII frames. The normal timing for frame transmission is shown in figure 9.4 (a), the timing in the case of a collision during transmission in figure 9.4 (b), and the timing in the case of an error during transmission in figure 9.4 (c). The normal timing for frame reception is shown in figure 9.4 (d), and the timing in the case of errors during transmission in figures 9.4 (e) and (f).
TX-CLK TX-EN TXD3 - TXD0 TX-ER CRS COL Preamble SFD Data CRC
Figure 9.4 (a) MII Frame Transmit Timing (Normal Transmission)
TX-CLK TX-EN TXD3 - TXD0 TX-ER CRS COL Preamble JAM
Figure 9.4 (b) MII Frame Transmit Timing (Collision)
Rev. 2.00 Mar 09, 2006 page 406 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
TX-CLK TX-EN TXD3 - TXD0 TX-ER CRS COL Preamble SFD Data
Figure 9.4 (c) MII Frame Transmit Timing (Transmit Error)
RX-CLK RX-DV RXD3 - RXD0 RX-ER Preamble SFD Data CRC
Figure 9.4 (d) MII Frame Receive Timing (Normal Reception)
RX-CLK RX-DV RXD3 - RXD0 RX-ER Preamble SFD Data XXXX
Figure 9.4 (e) MII Frame Receive Timing (Receive Error (1))
RX-CLK RX-DV RXD3 - RXD0 RX-ER XXXX 1110 XXXX
Figure 9.4 (f) MII Frame Receive Timing (Receive Error (2))
Rev. 2.00 Mar 09, 2006 page 407 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.3.4
Accessing MII Registers
MII registers in the PHY-LSI are accessed via the SH7616's PHY interface register (PIR). Connection is made as a serial interface in accordance with the MII frame format specified in IEEE802.3u. MII Management Frame Format: The format of an MII management frame is shown in figure 9.5. To access an MII register, a management frame is implemented by the program in accordance with the procedures shown in MII Register Access Procedure.
Access Type Item Number of bits Read Write PRE: ST: OP: PRE 32 1..1 1..1 32 consecutive 1s Write of 01 indicating start of frame ST 2 01 01 OP 2 10 01
MII Management Frame PHYAD 5 00001 00001 REGAD 5 RRRRR RRRRR TA 2 Z0 10 DATA 16 D..D D..D X IDLE
Write of code indicating access type
PHYAD: Write of 0001 if the PHY-LSI address is 1 (sequential write starting with the MSB). This bit changes depending on the PHY-LSI address. REGAD: Write of 0001 if the register address is 1 (sequential write starting with the MSB). This bit changes depending on the PHY-LSI register address. TA: Time for switching data transmission source on MII interface (a) Write: 10 written (b) Read: Bus release (notation: Z0) performed 16-bit data. Sequential write or read from MSB (a) Write: 16-bit data write (b) Read: 16-bit data read Wait time until next MII management format input (a) Write: Independent bus release (notation: X) performed (b) Read: Bus already released in TA; control unnecessary
DATA:
IDLE:
Figure 9.5 MII Management Frame Format MII Register Access Procedure: The program accesses MII registers via the PHY interface register (PIR). Access is implemented by a combination of 1-bit-unit data write, 1-bit-unit data read, bus release, and independent bus release. Examples 1 through 4 below show the register access timing. The timing will differ depending on the PHY-LSI type.
Rev. 2.00 Mar 09, 2006 page 408 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
1. The MII register write procedure is shown in figure 9.6 (a). 2. The bus release procedure is shown in figure 9.6 (b). 3. The MII register read procedure is shown in figure 9.6 (c). 4. The independent bus release procedure is shown in figure 9.6 (d).
(1) Write to PHY interface register MMD = 1 MDO = write data MDC = 0 MDC MDO
(2) Write to PHY interface register MMD = 1 MDO = write data MDC = 1
(1) (2)
(3)
1-bit data write timing relationship
(3) Write to PHY interface register MMD = 1 MDO = write data MDC = 0
Figure 9.6 (a) 1-Bit Data Write Flowchart
(1) Write to PHY interface register MMD = 0 MDC = 0 MDC MDO (2) Write to PHY interface register MMD = 0 MDC = 1 (1) (2) (3) Bus release timing relationship
(3) Write to PHY interface register MMD = 0 MDC = 0
Figure 9.6 (b) Bus Release Flowchart (TA in Read in Figure 9.5)
Rev. 2.00 Mar 09, 2006 page 409 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
(1) Write to PHY interface register MMD = 0 MDC = 1 MDC MDI
(2) Read from PHY interface register read MMD = 0 MMC = 1 MDI is read data
(1) (2)
(3)
1-bit data read timing relationship
(3) Write to PHY interface register MMD = 0 MDC = 0
Figure 9.6 (c) 1-Bit Data Read Flowchart
(1) Write to PHY interface register MMD = 0 MDC = 0 MDC MDO
(1) Independent bus release timing relationship
Figure 9.6 (d) Independent Bus Release Flowchart (IDLE in Write in Figure 9.5)
Rev. 2.00 Mar 09, 2006 page 410 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.3.5
Magic Packet Detection
The EtherC has a Magic Packet detection function. This function provides a Wake-On-LAN (WOL) facility that activates various peripheral devices connected to a LAN from the host device or other source. This makes it possible to construct a system in which a peripheral device receives a Magic Packet sent from the host device or other source, and activates itself. Further information on Magic Packets can be found in the technical documentation published by AMD Corporation. The procedure for using the WOL function with the SH7616 is as follows. 1. Disable interrupt source output by means of the various interrupt enable/mask registers. 2. Set the Magic Packet detection enable bit (MPDE) in the EtherC mode register (ECMR). 3. Set the Magic Packet detection interrupt enable bit (MPDIP) in the EtherC interrupt enable register (ECSIPR) to the enable setting. 4. If necessary, set the CPU operating mode to sleep mode or set supporting functions to module standby mode. 5. When a Magic Packet is detected, an interrupt is sent to the CPU. The WOL pin notifies peripheral LSIs that the Magic Packet has been detected. Notes: 1. When the Magic Packet is detected, data is stored in the receive FIFO by the broadcast packet that has received data previously and the EtherC is notified of the receiving status. To return to normal operation from the interrupt processing, initialize the EtherC and E-DMAC by using the software reset bit (SWR) in the E-DMAC mode register (EDMR). 2. With a Magic Packet, reception is performed regardless of the destination address. As a result, this function is valid, and the WOL pin enabled, only in the case of a match with the destination address specified by the format in the Magic Packet.
Rev. 2.00 Mar 09, 2006 page 411 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.3.6
CPU Operating Mode and Ethernet Controller Operation
The SH7616 enables a low-power-consumption system to be constructed by selecting or combining three functions: a module standby function that halts the operation of unnecessary onchip modules, a sleep mode that halts CPU functions, and a standby function that halts all the chip's functions. Details of each operating mode are given in section 21, Power-Down State. Here, features and points for attention when these functions are used in combination with the Ethernet controller are described. Sleep Mode: In sleep mode, the operation of the CPU and DSP is halted. The EtherC, on-chip supporting functions, and external pins continue to operate. Recovery from sleep mode can be carried out by means of an interrupt from the EtherC or a supporting module, or a reset. In order to control external pins and the WOL pin by means of Magic Packet reception, the relevant pins must be set beforehand. Note: In order to specify recovery by means of a magic packet, supporting function interrupt sources should be masked before sleep mode is entered. See section 9.3.5, Magic Packet Detection, for the setting procedure. Standby Mode: In standby mode, the on-chip oscillation circuit is halted. Consequently, the clock is not supplied to the EtherC, and interrupts from the EtherC and other supporting modules cannot be reported. It is therefore not possible to restore normal operation by these means, and so the WOL function cannot be used. Notes: This mode can be selected to halt all functions including the EtherC. However, an NMI interrupt, power-on reset, or manual reset is necessary in order to restore normal operation. When the SH7616 has been placed in standby mode, the CPU, DSP, and bus state controller are among the functions halted. When DRAM is connected, refreshing is also halted, and therefore initialization of memory, etc., is necessary after recovery, in the same way as in a reset. Module Standby Mode: Module standby mode allows individual supporting modules to be run or halted. However, due to the nature of its function, the operation of the EtherC cannot be stopped. During normal operation, module standby mode can be used to halt unnecessary supporting functions. The CPU and DSP continue to operate in this mode.
Rev. 2.00 Mar 09, 2006 page 412 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.3.7
CAM Match Signal Input Function
The EtherC is equipped with a CAM (Content Addressable Memory) match signal input function. A CAM circuit is externally connected to compare a destination address in a receive frame (see figure 9.7). The EtherC receives the result of comparison of a destination address corresponding to signals (RXD3 to RXD0) fetched from the MII as a signal from a CAMSEN pin and selects whether the current frame is received or discarded.
SH7616
MII (RX-DV, RXD3 to RXD0) EtherC
PHY-LSI
CAMSEN
CAM logic
Figure 9.7 CAM Circuit Connection Table 9.3 shows types of frames received and discarded in the two states of the CAMSEN signal. The CAM holds the MAC address besides this LSI. When the MAC address which is received from the PHY-LSI is matched with the destination address held in the CAM, the CAMSEN signal is asserted. The EtherC recognizes that the CAMSEN signal has been asserted then receives a frame for the reception. Some of the frame's data will have already been stored in the receive FIFO when the CAMSEN signal is asserted. Therefore, when the E-DMAC is requested that the received data be discarded, the E-DMAC discards the frame. The frame must be discarded before DMA transfer starts because the E-DMAC starts transferring to main memory by DMA when at least 16 bytes of data is stored in the receive FIFO. In this case, according to the MII receive signal timing, the RX-DV is asserted and the CAMSEN signal must be asserted within 35 clock cycles of the start timing of a
Rev. 2.00 Mar 09, 2006 page 413 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
destination address. The fact that the CAMSEN is asserted is reflected in the RFAR bit in the EtherC/E-DMAC status register (EESR) and this can be reflected as the write-back information of the descriptor. Table 9.3 Processing of Receive Frames
CAMSEN Input Asserted (address is matched) Negated (address is not matched) Frame Type SH7616 MAC address Broadcast address Multicast address CAM MAC addresses SH7616 MAC address Broadcast address Multicast address CAM MAC addresses Normal Mode Discarded Discarded Discarded Received Received Received Received Discarded Promise-CAS Mode Discarded Discarded Discarded Discarded Received Received Received Received
RX-CLK RX-DV RXD3 to RXD0 CAMSEN Preamble SFD Destination address
Within 35 clock cycles
Figure 9.8 CAM Signal Timing
Rev. 2.00 Mar 09, 2006 page 414 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
9.4
Connection to PHY-LSI
Figure 9.9 shows example of connection to an PHY-LSI AM79C873 (Advanced Micro Devices, Inc). Figure 9.10 shows example of connection to a DP83843 (National Semiconductor Corporation).
MII (Media independent interface) SH7616 TX-ER ETXD3 ETXD2 ETXD1 ETXD0 TX-EN TX-CLK MDC MDIO ERXD3 ERXD2 ERXD1 ERXD0 RX-CLK CRS COL RX-DV RX-ER AM79C873 TXER ETXD3 ETXD2 ETXD1 ETXD0 TXEN TXCLK MDC MDIO ERXD3 ERXD2 ERXD1 ERXD0 RXCLK CRS COL RXDV RXER
Figure 9.9 Example of Connection to AM79C873
Rev. 2.00 Mar 09, 2006 page 415 of 906 REJ09B0292-0200
Section 9 Ethernet Controller (EtherC)
MII (Media independent interface) SH7616 TX-ER ETXD3 ETXD2 ETXD1 ETXD0 TX-EN TX-CLK MDC MDIO ERXD3 ERXD2 ERXD1 ERXD0 RX-CLK CRS COL RX-DV RX-ER DP83843 TX_ER TXD3 TXD2 TXD1 TXD0 TX_EN TX_CLK MDC MDIO RXD3 RXD2 RXD1 RXD0 RX_CLK CRS COL RX_DV RX_ER
Figure 9.10 Example of Connection to DP83843
Rev. 2.00 Mar 09, 2006 page 416 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.1 Overview
The SH7616 has an on-chip two-channel direct memory access controller (E-DMAC) directly connected to the Ethernet controller (EtherC). A large proportion of buffer management is controlled by the E-DMAC itself using descriptors. This lightens the load on the CPU and enables efficient data transfer control to be achieved. 10.1.1 Features
The E-DMAC has the following features: * The load on the CPU is reduced by means of a descriptor management system * Transmit/receive frame status information is indicated in descriptors * Achieves efficient system bus utilization through the use of block transfer (16-byte units) * Supports single-frame/multi-buffer operation Note: The E-DMAC cannot access peripheral modules.
Rev. 2.00 Mar 09, 2006 page 417 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.1.2
Configuration
Figure 10.1 shows the configuration of the E-DMAC, and the descriptors and transmit/receive buffers in memory.
SH7616
E-DMAC Tx FIFO Descriptor information Transmit DMAC Internal bus interface Rx FIFO Descriptor information Receive DMAC
EtherC
External bus interface
Transmit descriptors
Transmit buffer
Receive descriptors
Receive buffer
Memory
Figure 10.1 Configuration of E-DMAC, and Descriptors and Buffers
Rev. 2.00 Mar 09, 2006 page 418 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.1.3
Descriptor Management System
The E-DMAC manages the transmit/receive buffers by means of corresponding transmit/receive descriptor lists. Transmission: The transmit E-DMAC fetches a transmit buffer address from the top of the transmit descriptor list, and transfers the transmit data in the buffer to the transmit FIFO. If a transmit directive follows in the descriptor, the E-DMAC reads the next descriptor and transfers the data in the corresponding buffer to the transmit FIFO. In this way, continuous data transmission can be carried out. Reception: For each start of a receive DMA transfer, the receive E-DMAC fetches a receive buffer address from the top of the receive descriptor list. When receive data is stored in the receive FIFO, the E-DMAC transfers this data to the receive buffer. When reception of one frame is finished, the E-DMAC performs a receive status write and fetches the receive buffer address from the next descriptor. By repeating this sequence, consecutive frames can be received. 10.1.4 Register Configuration
The E-DMAC has the seventeen 32-bit registers shown in table 10.1. Notes: 1. All registers must be accessed as 32-bit units. 2. Reserved bits in a register should only be written with 0. 3. The value read from a reserved bit is not guaranteed.
Rev. 2.00 Mar 09, 2006 page 419 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Table 10.1 E-DMAC Registers
Name E-DMAC mode register E-DMAC transmit request register E-DMAC receive request register Transmit descriptor list address register Receive descriptor list address register EtherC/E-DMAC status register EtherC/E-DMAC status interrupt permission register Transmit/receive status copy enable register Receive missed-frame counter register Transmit FIFO threshold register FIFO depth register Receiver control register E-DMAC operation control register Receive buffer write address register Receive descriptor fetch address register Transmit buffer read address register Transmit descriptor fetch address register Abbreviation EDMR EDTRR EDRRR TDLAR RDLAR EESR EESIPR TRSCER RMFCR TFTR FDR RCR EDOCR RBWAR RDFAR TBRAR TDFAR R/W R/W R/W R/W R/W R/W
1 R/W *
Initial Value H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000
2
Address H'FFFFFD00 H'FFFFFD04 H'FFFFFD08 H'FFFFFD0C H'FFFFFD10 H'FFFFFD14 H'FFFFFD18 H'FFFFFD1C H'FFFFFD20 H'FFFFFD24 H'FFFFFD28 H'FFFFFD2C H'FFFFFD30 H'FFFFFD40 H'FFFFFD44 H'FFFFFD4C H'FFFFFD50
R/W R/W R/W * R/W R/W R/W R/W R R R R
H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000 H'00000000
Notes: 1. Individual bits are cleared by writing 1. 2. Cleared by reading the register.
Rev. 2.00 Mar 09, 2006 page 420 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2
10.2.1
Register Descriptions
E-DMAC Mode Register (EDMR)
The E-DMAC mode register specifies the operating mode of the E-DMAC. The settings in this register are normally made in the initialization process following a reset. Note: Operating mode settings must not be changed while the transmitter and receiver are enabled. To change the operating mode, first return the EtherC and E-DMAC modules to their initial state by means of the software reset bit (SWR) in this register, then make new settings.
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 DL1 0 R/W ... ... ... ... 4 DL0 0 R/W 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 SWR 0 R/W
Bits 31 to 6--Reserved: These bits are always read as 0. The write value should always be 0. Bits 5 and 4--Descriptor Length 1, 0 (DL1, DL0): These bits specify the descriptor length,
Bit 5: DL1 0 1 Bit 4: DL0 0 1 0 1 Description 16 bytes 32 bytes 64 bytes Reserved (setting prohibited) (Initial value)
Bits 3 to 1--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 421 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 0--Software Reset (SWR): The EtherC and E-DMAC can be initialized by software. These bits should only be written with 0.
Bit 0: SWR 0 1 Description EtherC and E-DMAC reset is cleared EtherC and E-DMAC are reset (Initial value)
Notes: 1. If the EtherC and E-DMAC are initialized by means of this register during data transmission, etc., abnormal data may be sent onto the line. 2. The EtherC and E-DMAC are initialized in 16 internal clocks. Therefore, before accessing registers in the EtherC and E-DMAC, 16 internal clocks must be waited for. 3. The E-DMAC's TDLAR, RDLAR, and RMFCRL registers are not initialized. All other EtherC and E-DMAC registers are initialized.
10.2.2
E-DMAC Transmit Request Register (EDTRR)
The E-DMAC transmit request register issues transmit directives to the E-DMAC.
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 TR 0 R/W
Bits 31 to 1--Reserved: These bits are always read as 0. The write value should always be 0. Bit 0--Transmit Request (TR): When 1 is written to this bit, the E-DMAC reads a descriptor, and in the case of an active descriptor, transfers the data in the transmit buffer to the EtherC.
Bit 0: TR 0 Description
Transmission-halted state. Writing 0 does not stop transmission. Termination of transmission is controlled by the active bit in the transmit descriptor 1 Start of transmission. The relevant descriptor is read and a frame is sent with the transmit active bit set to 1 Note: When transmission of one frame is completed, the next descriptor is read. If the transmit descriptor active bit in this descriptor has the "active" setting, transmission is continued. If the transmit descriptor active bit has the "inactive" setting, the TR bit is cleared and operation of the transmit DMAC is halted. Rev. 2.00 Mar 09, 2006 page 422 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.3
E-DMAC Receive Request Register (EDRRR)
The E-DMAC receive request register issues receive directives to the E-DMAC.
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 RR 0 R/W
Bits 31 to 1--Reserved: These bits are always read as 0. The write value should always be 0. Bit 0--Receive Request (RR): When 1 is written to this bit, the E-DMAC reads a descriptor, and then transfers receive data to the buffer in response to receive requests from the EtherC.
Bit 0: RR 0 1 Description After frame reception is completed, the receiver is disabled A receive descriptor is read, and transfer is enabled
Notes: In order to receive a frame in response to a receive request, the receive descriptor active bit in the receive descriptor must be set to "active" beforehand. 1. When the receive request bit is set, the E-DMAC reads the relevant receive descriptor. 2. If the receive descriptor active bit in the descriptor has the "active" setting, the E-DMAC prepares for a receive request from the EtherC. 3. When one receive buffer of data has been received, the E-DMAC reads the next descriptor and prepares to receive the next frame. If the receive descriptor active bit in the descriptor has the "inactive" setting, the RR bit is cleared and operation of the receive DMAC is halted.
Rev. 2.00 Mar 09, 2006 page 423 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.4
Transmit Descriptor List Address Register (TDLAR)
TDLAR specifies the start address of the transmit descriptor list. Descriptors have a boundary configuration in accordance with the descriptor length indicated by the DL bit in EDMR.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R/W 23 0 R/W 15 0 R/W 7 TDLA7 0 R/W 30 0 R/W 22 0 R/W 14 0 R/W 6 TDLA6 0 R/W 29 0 R/W 21 0 R/W 13 0 R/W 5 TDLA5 0 R/W 28 0 R/W 20 0 R/W 12 0 R/W 4 TDLA4 0 R/W 27 0 R/W 19 0 R/W 11 0 R/W 3 TDLA3 0 R/W 26 0 R/W 18 0 R/W 10 0 R/W 2 TDLA2 0 R/W 25 0 R/W 17 0 R/W 9 TDLA9 0 R/W 1 TDLA1 0 R/W 24 0 R/W 16 0 R/W 8 TDLA8 0 R/W 0 TDLA0 0 R/W
TDLA31 TDLA30 TDLA29 TDLA28 TDLA27 TDLA26 TDLA25 TDLA24
TDLA23 TDLA22 TDLA21 TDLA20 TDLA19 TDLA18 TDLA17 TDLA16
TDLA15 TDLA14 TDLA13 TDLA12 TDLA11 TDLA10
Bits 31 to 0--Transmit Descriptor Start Address 31 to 0 (TDLA31 to TDLA0) : These bits should only be written with 0. Notes: The lower bits are set as follows according to the specified descriptor length. 16-byte boundary: TDLA[3:0] = 0000 32-byte boundary: TDLA[4:0] = 00000 64-byte boundary: TDLA[5:0] = 000000 This register must not be written to during transmission. Modifications to this register should only be made while transmission is disabled.
Rev. 2.00 Mar 09, 2006 page 424 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.5
Receive Descriptor List Address Register (RDLAR)
RDLAR specifies the start address of the receive descriptor list. Descriptors have a boundary configuration in accordance with the descriptor length indicated by the DL bit in EDMR.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R/W 23 0 R/W 15 0 R/W 7 RDLA7 0 R/W 30 0 R/W 22 0 R/W 14 0 R/W 6 RDLA6 0 R/W 29 0 R/W 21 0 R/W 13 0 R/W 5 RDLA5 0 R/W 28 0 R/W 20 0 R/W 12 0 R/W 4 RDLA4 0 R/W 27 0 R/W 19 0 R/W 11 0 R/W 3 RDLA3 0 R/W 26 0 R/W 18 0 R/W 10 0 R/W 2 RDLA2 0 R/W 25 0 R/W 17 0 R/W 9 0 R/W 1 RDLA1 0 R/W 24 0 R/W 16 0 R/W 8 RDLA8 0 R/W 0 RDLA0 0 R/W
RDLA31 RDLA30 RDLA29 RDLA28 RDLA27 RDLA26 RDLA25 RDLA24
RDLA23 RDLA22 RDLA21 RDLA20 RDLA19 RDLA18 RDLA17 RDLA16
RDLA15 RDLA14 RDLA13 RDLA12 RDLA11 RDLA10 RDLA9
Bits 31 to 0--Receive Descriptor Start Address 31 to 0 (RDLA31 to RDLA0) Notes: The lower bits are set as follows according to the specified descriptor length. 16-byte boundary: RDLA[3:0] = 0000 32-byte boundary: RDLA[4:0] = 00000 64-byte boundary: RDLA[5:0] = 000000 Modifications made to this register during reception are invalid. This register should only be modified while reception is disabled.
Rev. 2.00 Mar 09, 2006 page 425 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.6
EtherC/E-DMAC Status Register (EESR)
EESR shows communication status information for both the E-DMAC and the EtherC. The information in this register is reported in the form of interrupt sources. Individual bits are cleared by writing 1 to them. Each bit can also be masked by means of the corresponding bit in the EtherC/E-DMAC status interrupt permission register.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 23 -- 0 R 15 -- 0 R 7 RMAF 0 R/W 30 -- 0 R 22 ECI 0 R 14 -- 0 R 6 -- 0 R 29 -- 0 R 21 TC 0 R/W 13 -- 0 R 5 RFAR 0 R/W 28 -- 0 R 20 TDE 0 R/W 12 ITF 0 R/W 4 RRF 0 R/W 27 -- 0 R 19 TFUF 0 R/W 11 CND 0 R/W 3 RTLF 0 R/W 26 -- 0 R 18 FR 0 R/W 10 DLC 0 R/W 2 RTSF 0 R/W 25 -- 0 R 17 RDE 0 R/W 9 CD 0 R/W 1 PRE 0 R/W 24 RFCOF 0 R/W 16 RFOF 0 R/W 8 TRO 0 R/W 0 CERF 0 R/W
Bits 31 to 25--Reserved: These bits are always read as 0. The write value should always read as 0. Bit 24--Receive Frame Counter Overflow (RFCOF): Indicates that the receive FIFO frame counter has overflowed.
Bit 24: RFCOF 0 1 Description Receive frame counter has not overflowed Receive frame counter overflow (interrupt source) (Initial value)
Note: The receive FIFO in the E-DMAC can hold up to eight frames. If a ninth frame is received when there are already eight frames in the receive FIFO, the receive frame counter overflows and the ninth frame is discarded. Discarded frames are counted by the missedframe counter register. The eight frames in the receive FIFO are retained, and are Rev. 2.00 Mar 09, 2006 page 426 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC) transferred to memory when DMA transfer becomes possible. When the frame counter value falls below 8, another frame is received.
Bit 23--Reserved: These bits are always read as 0. The write value should always be 0. Bit 22--EtherC States Register Interrupt (ECI): Indicates that an interrupt due to an EtherC status register (ECSR) source has been detected.
Bit 22: ECI 0 1 Description EtherC status interrupt source not detected EtherC status interrupt source detected (interrupt source) (Initial value)
Note: EESR is a read-only register. When this register is cleared by a source in ECSR in the EtherC, this bit is also cleared.
Bit 21--Frame Transmit Complete (TC): Indicates that all the data specified by the transmit descriptor has been transmitted to the EtherC. The transfer status is written back to the relevant descriptor. When 1-frame transmission is completed for 1-frame/1-buffer processing, or when the last data in the frame is transmitted and the transmission descriptor valid bit (TACT) in the next descriptor is not set for multiple-frame buffer processing, transmission is completed and this bit is set to 1. After frame transmission, the E-DMAC writes the transmission status back to the descriptor.
Bit 21: TC 0 1 Description Transfer not complete, or no transfer directive Transfer complete (interrupt source) (Initial value)
Note: As data is sent onto the line by the PHY-LSI from the EtherC via the MII, the actual transmission completion time is longer.
Bit 20--Transmit Descriptor Exhausted (TDE): Indicates that the transmission descriptor valid bit (TACT) in the descriptor is not set when the E-DMAC reads the transmission descriptor when the previous descriptor is not the last one of the frame for multiple- buffer frame processing. As a result, an incomplete frame may be transmitted.
Bit 20: TDE 0 1 Description "1" transmit descriptor active bit (TACT) detected (Initial value) "0" transmit descriptor active bit (TACT) detected (interrupt source)
Note: When transmission descriptor empty (TDE = 1) occurs, execute a software reset and initiate transmission. In this case, the address that is stored in the transmit descriptor list address register (TDLAR) is transmitted first.
Rev. 2.00 Mar 09, 2006 page 427 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 19--Transmit FIFO Underflow (TFUF): Indicates that underflow has occurred in the transmit FIFO during frame transmission. Incomplete data is sent onto the line.
Bit 19: TFUF 0 1 Description Underflow has not occurred Underflow has occurred (interrupt source) (Initial value)
Note: Whether E-DMAC operation continues or halts after underflow is controlled by the E-DMAC operation control register (EDOCR).
Bit 18--Frame Received (FR): Indicates that a frame has been received and the receive descriptor has been updated. This bit is set to 1 each time a frame is received. Note: The actual receive frame status is indicated in the receive status field in the descriptor.
Bit 18: FR 0 1 Description Frame not received Frame received (interrupt source) (Initial value)
Bit 17--Receive Descriptor Exhausted (RDE): This bit is set if the receive descriptor active bit (RACT) setting is "inactive" (RACT = 0) when the E-DMAC reads a receive descriptor.
Bit 17: RDE 0 1 Description "1" receive descriptor active bit (RACT) detected (Initial value) "0" receive descriptor active bit (RACT) detected (interrupt source)
Note: When receive descriptor empty (RDE = 1) occurs, receiving can be restarted by setting RACT = 1 in the receive descriptor and initiating receiving.
Bit 16--Receive FIFO Overflow (RFOF): Indicates that the receive FIFO has overflowed during frame reception.
Bit 16: RFOF 0 1 Description Overflow has not occurred Overflow has occurred (interrupt source) (Initial value)
Notes: 1. If there are a number of receive frames in the receive FIFO, they will not be sent to memory correctly. The status of the frame that caused the overflow is written back to the receive descriptor. 2. Whether E-DMAC operation continues or halts after overflow is controlled by the EDMAC operation control register (EDOCR).
Rev. 2.00 Mar 09, 2006 page 428 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bits 15 to 13--Reserved: These bits are always read as 0. The write value should always be 0. Bit 12--Illegal Transmit Frame (ITF): Indicates that the transmit frame length specification is less than four bytes.
Bit 12: ITF 0 1 Description Normal transmit frame length Illegal transmit frame length (interrupt source) (Initial value)
Bit 11--Carrier Not Detect (CND): Indicates the carrier detection status.
Bit 11: CND 0 1 Description A carrier is detected when transmission starts Carrier not detected (interrupt source) (Initial value)
Bit 10--Detect Loss of Carrier (DLC): Indicates that loss of the carrier has been detected during frame transmission.
Bit 10: DLC 0 1 Description Loss of carrier not detected Loss of carrier detected (interrupt source) (Initial value)
Bit 9--Collision Detect (CD): Indicates that a collision has been detected during frame transmission.
Bit 9: CD 0 1 Description Collision not detected Collision detected (interrupt source) (Initial value)
Bit 8--Transmit Retry Over (TRO): Indicates that a retry-over condition has occurred during frame transmission. Total 16 transmission retries including 15 retries based on the back-off algorithm are failed after the EtherC transmission starts.
Bit 8: TRO 0 1 Description Transmit retry-over condition not detected Transmit retry-over condition detected (interrupt source) (Initial value)
Rev. 2.00 Mar 09, 2006 page 429 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 7--Receive Multicast Address Frame (RMAF): Indicates that a multicast address frame has been received.
Bit 7: RMAF 0 1 Description Multicast address frame has not been received Multicast address frame has been received (interrupt source) (Initial value)
Bits 6--Reserved: This bit should only be written with 0. Bit 5--Receive Frame Discard Request Assertion (RFAR): Indicates that a frame discard request has been asserted by the EtherC as a result of a signal from the CAM, however, it is not possible to discard the frame in the E-DMAC.
Bit 5: RFAR 0 1 Description Receive frame discard request assertion has not been received (Initial value) Receive frame discard request assertion has been received (interrupt source)
Bit 4--Receive Residual-Bit Frame (RRF): Indicates that a residual-bit frame has been received.
Bit 4: RRF 0 1 Description Residual-bit frame has not been received Residual-bit frame has been received (interrupt source) (Initial value)
Bit 3--Receive Too-Long Frame (RTLF): Indicates that a frame of 1519 bytes or longer has been received.
Bit 3: RTLF 0 1 Description Too-long frame has not been received Too-long frame has been received (interrupt source) (Initial value)
Bit 2--Receive Too-Short Frame (RTSF): Indicates that a frame of fewer than 64 bytes has been received.
Bit 2: RTSF 0 1 Description Too-short frame has not been received Too-short frame has been received (interrupt source) (Initial value)
Rev. 2.00 Mar 09, 2006 page 430 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 1--PHY-LSI Receive Error (PRE): Indicates an error notification from the MII (PHY-LSI)
Bit 1: PRE 0 1 Description PHY-LSI receive error not detected PHY-LSI receive error detected (interrupt source) (Initial value)
Bit 0--CRC Error on Received Frame (CERF): Indicates that a CRC error has been detected in the received frame.
Bit 0: CERF 0 1 Description CRC error not detected CRC error detected (interrupt source) (Initial value)
Rev. 2.00 Mar 09, 2006 page 431 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.7
EtherC/E-DMAC Status Interrupt Permission Register (EESIPR)
EESIPR enables interrupts corresponding to individual bits in the EtherC/E-DMAC status register. An interrupt is enabled by writing 1 to the corresponding bit. In the initial state, interrupts are not enabled.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 23 -- 0 R 15 -- 0 R 7 RMAFIP 0 R/W 30 -- 0 R 22 ECIIP 0 R/W 14 -- 0 R 6 -- 0 R 29 -- 0 R 21 TCIP 0 R/W 13 -- 0 R 5 RFARIP 0 R/W 28 -- 0 R 20 TDEIP 0 R/W 12 ITFIP 0 R/W 4 RRFIP 0 R/W 27 -- 0 R 19 TFUFIP 0 R/W 11 CNDIP 0 R/W 3 0 R/W 26 -- 0 R 18 FRIP 0 R/W 10 DLCIP 0 R/W 2 0 R/W 25 -- 0 R 17 RDEIP 0 R/W 9 CDIP 0 R/W 1 PREIP 0 R/W 24 RFCOFIP 0 R/W 16 RFOFIP 0 R/W 8 TROIP 0 R/W 0 CERFIP 0 R/W
RTLFIP RTSFIP
Bits 31 to 25--Reserved: These bits are always read as 0. The write value should always be 0. Bit 24--Receive Frame Counter Overflow Interrupt Permission (RFCOFIP): Enables the receive frame counter overflow interrupt.
Bit 24: RFCOFIP Description 0 1 Receive frame counter overflow interrupt is disabled Receive frame counter overflow interrupt is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 432 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 23--Reserved: This bit is always read as 0. The write value should always be 0. Bit 22--EtherC Status Register Interrupt Permission (ECIP): Enables interrupts due to EtherC status register sources.
Bit 22: ECIP 0 1 Description EtherC status interrupts are disabled EtherC status interrupts are enabled (Initial value)
Bit 21--Frame Transmit Complete Interrupt Permission (TCIP): Enables the frame transmit complete interrupt.
Bit 21: TCIP 0 1 Description Frame transmit complete interrupt is disabled Frame transmit complete interrupt is enabled (Initial value)
Bit 20--Transmit Descriptor Exhausted Interrupt Permission (TDEIP): Enables the transmit descriptor exhausted interrupt.
Bit 20: TDEIP 0 1 Description Transmit descriptor exhausted interrupt is disabled Transmit descriptor exhausted interrupt is enabled (Initial value)
Bit 19--Transmit FIFO Underflow Interrupt Permission (TFUFIP): Enables the transmit FIFO underflow interrupt.
Bit 19: TFUFIP 0 1 Description Transmit FIFO underflow interrupt is disabled Transmit FIFO underflow interrupt is enabled (Initial value)
Bit 18--Frame Received Interrupt Permission (FRIP): Enables the frame received interrupt.
Bit 18: FRIP 0 1 Description Frame received interrupt is disabled Frame received interrupt is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 433 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 17--Receive Descriptor Exhausted Interrupt Permission (RDEIP): Enables the receive descriptor exhausted interrupt.
Bit 17: RDEIP 0 1 Description Receive descriptor exhausted interrupt is disabled Receive descriptor exhausted interrupt is enabled (Initial value)
Bit 16--Receive FIFO Overflow Interrupt Permission (RFOFIP): Enables the receive FIFO overflow interrupt.
Bit 16: RFOFIP 0 1 Description Receive FIFO overflow interrupt is disabled Receive FIFO overflow interrupt is enabled (Initial value)
Bits 15 to 13--Reserved: These bits are always read as 0. The write value should always be 0. Bit 12--Illegal Transmit Frame Interrupt Permission (ITFIP): Enables the illegal transmit frame interrupt.
Bit 12: ITFIP 0 1 Description Illegal transmit frame interrupt is disabled Illegal transmit frame interrupt is enabled (Initial value)
Bit 11--Carrier Not Detect Interrupt Permission (CNDIP): Enables the carrier not detect interrupt.
Bit 11: CNDIP 0 1 Description Carrier not detect interrupt is disabled Carrier not detect interrupt is enabled (Initial value)
Bit 10--Detect Loss of Carrier Interrupt Permission (DLCIP): Enables the detect loss of carrier interrupt.
Bit 10: DLCIP 0 1 Description Detect loss of carrier interrupt is disabled Detect loss of carrier interrupt is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 434 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 9--Collision Detect Interrupt Permission (CDIP): Enables the collision detect interrupt.
Bit 9: CDIP 0 1 Description Collision detect interrupt is disabled Collision detect interrupt is enabled (Initial value)
Bit 8--Transmit Retry Over Interrupt Permission (TROIP): Enables the transmit retry over interrupt.
Bit 8: TROIP 0 1 Description Transmit retry over interrupt is disabled Transmit retry over interrupt is enabled (Initial value)
Bit 7--Receive Multicast Address Frame Interrupt Permission (RMAFIP): Enables the receive multicast address frame interrupt.
Bit 7: RMAFIP 0 1 Description Receive multicast address frame interrupt is disabled Receive multicast address frame interrupt is enabled (Initial value)
Bits 6--Reserved: This bit is always read as 0. The write value should always be 0. Bit 5--Receive Frame Discard Request Assertion Interrupt Permission (RFARIP): Enables the receive frame discard request assertion interrupt.
Bit 5: RFARIP 0 1 Description Receive frame discard request assertion interrupt is disabled Receive frame discard request assertion interrupt is enabled (Initial value)
Bit 4--Receive Residual-Bit Frame Interrupt Permission (RRFIP): Enables the receive residual-bit frame interrupt.
Bit 4: RRFIP 0 1 Description Receive residual-bit frame interrupt is disabled Receive residual-bit frame interrupt is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 435 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 3--Receive Too-Long Frame Interrupt Permission (RTLFIP): Enables the receive too-long frame interrupt.
Bit 3: RTLFIP 0 1 Description Receive too-long frame interrupt is disabled Receive too-long frame interrupt is enabled (Initial value)
Bit 2--Receive Too-Short Frame Interrupt Permission (RTSFIP): Enables the receive too-short frame interrupt.
Bit 2: RTSFIP 0 1 Description Receive too-short frame interrupt is disabled Receive too-short frame interrupt is enabled (Initial value)
Bit 1--PHY-LSI Receive Error Interrupt Permission (PREIP): Enables the PHY-LSI receive error interrupt.
Bit 1: PREIP 0 1 Description PHY-LSI receive error interrupt is disabled PHY-LSI receive error interrupt is enabled (Initial value)
Bit 0--CRC Error on Received Frame Interrupt Permission (PREIP): Enables the CRC error on received frame interrupt.
Bit 0: CERFIP 0 1 Description CRC error on received frame interrupt is disabled CRC error on received frame interrupt is enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 436 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.8
Transmit/Receive Status Copy Enable Register (TRSCER)
TRSCER specifies whether or not transmit and receive status information reported by bits in the EtherC/E-DMAC status register is to be indicated in the corresponding descriptor. The bits in this register correspond to EtherC/E-DMAC status register EESR[15 to 0]. When a bit is cleared to 0, the transmit status (EESR[15 to 8]) is indicated in the TFE bit of the transmit descriptor, and the receive status (EESR[7 to 0]) is indicated in the RFE bit of the receive descriptor. When a bit is set to 1, the occurrence of the corresponding source is not indicated in the descriptor. After the chip is reset, all bits are cleared to 0.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 -- 0 R 7 RMAFCE 0 R/W 30 -- 0 R 14 -- 0 R 6 -- 0 R 29 -- 0 R 13 -- 0 R 5 -- 0 R ... ... ... ... 12 -- 0 R 4 -- 0 R 19 -- 0 R 11 -- 0 R 3 -- 0 R 18 -- 0 R 10 -- 0 R 2 -- 0 R 17 -- 0 R 9 -- 0 R 1 -- 0 R 16 -- 0 R 8 -- 0 R 0 -- 0 R
Bits 31 to 8--Reserved: These bits are always read as 0. The write value should always be 0. Bit 7--Multicast Address Frame Receive (RMAF): Bit Copy Enable (RMAFCE)
Bit 7: RMAFCE 0 1 Description Enables the RMAF bit status to be indicated in the RFS7 bit in the receive descriptor. Disables occurrence of corresponding source to be indicated in the RFS7 bit in the receive descriptor.
Bits 6 to 0--Reserved: These bits are always read as 0. The write value should always be 0. For the corresponding bit sources, see section 10.2.6, EtherC/E-DMAC Status Register (EESR).
Rev. 2.00 Mar 09, 2006 page 437 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.9
Receive Missed-Frame Counter Register (RMFCR)
RMFCR is a 16-bit counter that indicates the number of frames missed (discarded, and not transferred to the receive buffer) during reception. When the receive FIFO overflows, the receive frames in the FIFO are discarded. The number of frames discarded at this time are counted. When the value in this register reaches H'FFFF (65,535), the count is halted. When this register is read, the counter value is cleared to 0. Writes to this register have no effect.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 MFC15 0 R 7 MFC7 0 R 30 -- 0 R 14 MFC14 0 R 6 MFC6 0 R 29 -- 0 R 13 MFC13 0 R 5 MFC5 0 R ... ... ... ... 12 MFC12 0 R 4 MFC4 0 R 19 -- 0 R 11 MFC11 0 R 3 MFC3 0 R 18 -- 0 R 10 MFC10 0 R 2 MFC2 0 R 17 -- 0 R 9 MFC9 0 R 1 MFC1 0 R 16 -- 0 R 8 MFC8 0 R 0 MFC0 0 R
Rev. 2.00 Mar 09, 2006 page 438 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.10 Transmit FIFO Threshold Register (TFTR) TFTR specifies the transmit FIFO threshold at which the first transmission is started. The actual threshold is 4 times the set value. The EtherC starts transmission when the amount of data in the transmit FIFO exceeds the number of bytes specified by this register, when the transmit FIFO is full, or when 1-frame write is executed. Note: When setting this register, do so in the transmission-halt state.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 -- 0 R 7 TFT7 0 R/W 30 -- 0 R 14 -- 0 R 6 TFT6 0 R/W 29 -- 0 R 13 -- 0 R 5 TFT5 0 R/W ... ... ... ... 12 -- 0 R 4 TFT4 0 R/W 19 -- 0 R 11 -- 0 R 3 TFT3 0 R/W 18 -- 0 R 10 TFT10 0 R/W 2 TFT2 0 R/W 17 -- 0 R 9 TFT9 0 R/W 1 TFT1 0 R/W 16 -- 0 R 8 TFT8 0 R/W 0 TFT0 0 R/W
Bits 31 to 11--Reserved: These bits should only be written with 0.
Rev. 2.00 Mar 09, 2006 page 439 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bits 10 to 0--Transmit FIFO Threshold 10 to 0 (TFT10 to TFT0)
Bits 10 to 0: TFT H'00 H'01 H'02 : H'1F H'20 : H'3F H'40 : H'7F H'80 : H'FF H'100 : H'1FF H'200 Description Store-and-forward mode (transmission starts when one frame of data is written or transmit FIFO is full) (Initial value) 4 bytes 8 bytes : 124 bytes 128 bytes : 252 bytes 256 bytes : 508 bytes 512 bytes : 1023 bytes 1024 bytes : 2047 bytes 2048 bytes
Note: Note: When setting a transmit FIFO, the FIFO must be set to a smaller value than the specified value of the FIFO's capacity.
Rev. 2.00 Mar 09, 2006 page 440 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.11 FIFO Depth Register (FDR) FDR specifies the depth (size) of the transmit and receive FIFOs.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 -- 0 R 7 -- 0 R 30 -- 0 R 14 -- 0 R 6 -- 0 R 29 -- 0 R 13 -- 0 R 5 -- 0 R ... ... ... ... 12 -- 0 R 4 -- 0 R 19 -- 0 R 11 -- 0 R 3 -- 0 R 18 -- 0 R 10 TFD2 0 R/W 2 RFD2 0 R/W 17 -- 0 R 9 TFD1 0 R/W 1 RFD1 0 R/W 16 -- 0 R 8 TFD0 0 R/W 0 RFD0 0 R/W
Bits 31 to 11--Reserved: These bits are always read as 0. The write value should always be 0. Bit 10 to 8--Transmit FIFO Depth (TFD): Specifies 256 bytes to 2 kbytes in 256-byte units as the depth (size) of the transmit FIFO. The setting cannot be changed after transmission/reception has started.
Bits 10 to 8: TFD2 to TFD0 H'0 H'1 : H'7 Description 256 bytes 512 bytes : 2048 bytes (Initial value)
Bits 7 to 3--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 441 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 2 to 0--Receive FIFO Depth (RFD): Specifies 256 bytes to 2 kbytes in 256-byte units as the depth (size) of the receive FIFO. The actual FIFO depth is 256 times the set value. The setting cannot be changed after transmission/reception has started.
Bits 2 to 0: RFD2 to RFD0 H'0 H'1 : H'7 Description 256 bytes 512 bytes : 2048 bytes (Initial value)
10.2.12 Receiver Control Register (RCR) RCR specifies the control method for the RE bit in ECMR when a frame is received. Note: When setting this register, do so in the receiving-halt state.
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 RNC 0 R/W
Bits 31 to 1--Reserved: These bits are always read as 0. The write value should always be 0. Bit 0--Receive Enable Control (RNC)
Bit 0: RNC 0 1 Description When reception of one frame is completed, the E-DMAC writes the receive status into the descriptor and clears the RR bit in EDRRR (Initial value) When reception of one frame is completed, the E-DMAC writes the receive status into the descriptor, reads the next descriptor, and prepares to receive the next frame*
Note: * This setting is normally used for continuous frame reception.
Rev. 2.00 Mar 09, 2006 page 442 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.13 E-DMAC Operation Control Register (EDOCR) EDOCR specifies the control methods used in E-DMAC operation.
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 FEC 0 R/W 10 -- 0 R 2 AEC 0 R/W 9 -- 0 R 1 EDH 0 R/W 8 -- 0 R 0 -- 0 R
Bits 31 to 4, and 0--Reserved: These bits are always read as 0. The write value should always be 0. Bit 3--FIFO Error Control (FEC): Specifies E-DMAC operation when transmit FIFO underflow or receive FIFO overflow occurs.
Bit 3: FEC 0 1 Description E-DMAC operation continues when underflow or overflow occurs (Initial value) E-DMAC operation halts when underflow or overflow occurs
Bit 2--Address Error Control (AEC): Indicates detection of an illegal memory address in an attempted E-DMAC transfer.
Bit 2: AEC 0 1 Description Illegal memory address not detected (normal operation) Illegal memory address detected. Can be cleared by writing 0 (Initial value)
Note: This error occurs if the memory address setting in the descriptor used by the E-DMAC is illegal.
Bit 1--E-DMAC Halted (EDH): When the SH7616's NMI input pin is asserted, E-DMAC operation is halted.
Bit 1: EDH 0 1 Description The E-DMAC is operating normally (Initial value) The E-DMAC has been halted by NMI pin assertion. E-DMAC operation is restarted by writing 0 Rev. 2.00 Mar 09, 2006 page 443 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bits 0--Reserved: This bit is always read as 0. The write value should always be 0. 10.2.14 Receiving-Buffer Write Address Register (RBWAR) This is the register for storing the buffer address to be written in the receiving buffer when the EDMAC writes data in the receiving buffer. Which addresses in the receiving buffer are processed by the E-DMAC can be recognized by monitoring addresses displayed in this register.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R 23 0 R 15 0 R 7 0 R 30 0 R 22 0 R 14 0 R 6 0 R 29 0 R 21 0 R 13 0 R 5 0 R 28 0 R 20 0 R 12 0 R 4 0 R 27 0 R 19 0 R 11 0 R 3 0 R 26 0 R 18 0 R 10 0 R 2 0 R 25 0 R 17 0 R 9 0 R 1 0 R 24 0 R 16 0 R 8 0 R 0 0 R
RBWA31 RBWA30 RBWA29 RBWA28 RBWA27 RBWA26 RBWA25 RBWA24
RBWA23 RBWA22 RBWA21 RBWA20 RBWA19 RBWA18 RBWA17 RBWA16
RBWA15 RBWA14 RBWA13 RBWA12 RBWA11 RBWA10 RBWA9 RBWA8
RBWA7 RBWA6 RBWA5 RBWA4 RBWA3 RBWA2 RBWA1 RBWA0
Bits 31 to 0--Receiving-buffer write address (RBWA): This bit can only be read. Writing is disabled. Note: The buffer write processing result from the E-DMAC and the value read by the register may not be the same.
Rev. 2.00 Mar 09, 2006 page 444 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.15 Receiving-Descriptor Fetch Address Register (RDFAR) This is the register for storing the descriptor start address that is required when the E-DMAC fetches descriptor information from the receiving descriptor . Which receiving descriptor information is used for processing by the E-DMAC can be recognized by monitoring addresses displayed in this register.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R 23 0 R 15 0 R 7 RDFA7 0 R 30 0 R 22 0 R 14 0 R 6 RDFA6 0 R 29 0 R 21 0 R 13 0 R 5 RDFA5 0 R 28 0 R 20 0 R 12 0 R 4 RDFA4 0 R 27 0 R 19 0 R 11 0 R 3 RDFA3 0 R 26 0 R 18 0 R 10 0 R 2 RDFA2 0 R 25 0 R 17 0 R 9 0 R 1 RDFA1 0 R 24 0 R 16 0 R 8 RDFA8 0 R 0 RDFA0 0 R
RDFA31 RDFA30 RDFA29 RDFA28 RDFA27 RDFA26 RDFA25 RDFA24
RDFA23 RDFA22 RDFA21 RDFA20 RDFA19 RDFA18 RDFA17 RDFA16
RDFA15 RDFA14 RDFA13 RDFA12 RDFA11 RDFA10 RDFA9
Bits 31 to 0--Receiving-descriptor fetch address (RDFA): This bit can only be read. Writing is disabled. Note: The descriptor fetch processing result from the E-DMAC and the value read by the register may not be the same.
Rev. 2.00 Mar 09, 2006 page 445 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.16 Transmission-Buffer Read Address Register (TBRAR) This is the register for storing the buffer address to be read in the transmission buffer when the EDMAC reads data from the transmission buffer. Which addresses in the transmission buffer are processed by the E-DMAC can be recognized by monitoring addresses displayed in this register.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R 23 0 R 15 0 R 7 TBRA7 0 R 30 0 R 22 0 R 14 0 R 6 TBRA6 0 R 29 0 R 21 0 R 13 0 R 5 TBRA5 0 R 28 0 R 20 0 R 12 0 R 4 TBRA4 0 R 27 0 R 19 0 R 11 0 R 3 TBRA3 0 R 26 0 R 18 0 R 10 0 R 2 TBRA2 0 R 25 0 R 17 0 R 9 0 R 1 TBRA1 0 R 24 0 R 16 0 R 8 TBRA8 0 R 0 TBRA0 0 R
TBRA31 TBRA30 TBRA29 TBRA28 TBRA27 TBRA26 TBRA25 TBRA24
TBRA23 TBRA22 TBRA21 TBRA20 TBRA19 TBRA18 TBRA17 TBRA16
TBRA15 TBRA14 TBRA13 TBRA12 TBRA11 TBRA10 TBRA9
Bits 31 to 0--Transmission-buffer read address (TBRD): This bit can only be read. Writing is disabled. Note: The buffer read processing result from the E-DMAC and the value read by the register may not be the same.
Rev. 2.00 Mar 09, 2006 page 446 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.2.17 Transmission-Descriptor Fetch Address Register (TDFAR) This is the register for storing the descriptor start address that is required when the E-DMAC fetches descriptor information from the transmission descriptor . Which transmission descriptor information is used for processing by the E-DMAC can be recognized by monitoring addresses displayed in this register.
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 0 R 23 0 R 15 0 R 7 TDFA7 0 R 30 0 R 22 0 R 14 0 R 6 TDFA6 0 R 29 0 R 21 0 R 13 0 R 5 TDFA5 0 R 28 0 R 20 0 R 12 0 R 4 TDFA4 0 R 27 0 R 19 0 R 11 0 R 3 TDFA3 0 R 26 0 R 18 0 R 10 0 R 2 TDFA2 0 R 25 0 R 17 0 R 9 TDFA9 0 R 1 TDFA1 0 R 24 0 R 16 0 R 8 TDFA8 0 R 0 TDFA0 0 R
TDFA31 TDFA30 TDFA29 TDFA28 TDFA27 TDFA26 TDFA25 TDFA24
TDFA23 TDFA22 TDFA21 TDFA20 TDFA19 TDFA18 TDFA17 TDFA16
TDFA15 TDFA14 TDFA13 TDFA12 TDFA11 TDFA10
Bits 31 to 0--Transmission-descriptor fetch address (TDFA): This bit can only be read. Writing is disabled. Note: The descriptor fetch processing result from the E-DMAC and the value read by the register may not be the same.
Rev. 2.00 Mar 09, 2006 page 447 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.3
Operation
The E-DMAC is connected to the EtherC, and performs efficient transfer of transmit/receive data between the EtherC and memory (buffers) without the intervention of the CPU. The E-DMAC itself reads control information, including buffer pointers called descriptors, relating to the buffers. The E-DMAC reads transmit data from the transmit buffer and writes receive data to the receive buffer in accordance with this control information. By setting up a number of consecutive descriptors (a descriptor list), it is possible to execute transmission and reception continuously. 10.3.1 Descriptor List and Data Buffers
Before starting transmission/reception, the communication program creates transmit and receive descriptor lists in memory. The start addresses of these lists are then set in the transmit and receive descriptor list start address registers. Transmit Descriptor Figure 10.2 shows the relationship between a transmit descriptor and the transmit buffer. According to the specification in this descriptor, the relationship between the transmit frame and transmit buffer can be defined as one frame/one buffer or one frame/multi-buffer. Notes: 1. The descriptor's start address setting must be aligned with an address boundary that corresponds with the descriptor's length as set by the E-DMAC mode register (EDMR). 2. The transmit buffer's start address setting must be aligned with a longword boundary. However, when SDRAM is connected, the setting must be aligned with a 16-byte boundary.
Transmit descriptor 31 30 29 28 27 26 0 TFS26 to TFS0 Valid transmit data TD1 TD2 31 31 TDL 16 0 Transmit buffer
TD0
TACT TDLE TFP1 TFP0 TFE
TBA Padding (4 bytes)
Figure 10.2 Relationship between Transmit Descriptor and Transmit Buffer
Rev. 2.00 Mar 09, 2006 page 448 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Transmit Descriptor 0 (TD0): TD0 indicates the transmit frame status. The CPU and E-DMAC use TD0 to report the frame transmission status. Bit 31--Transmit Descriptor Active (TACT): Indicates that this descriptor is active. The CPU sets this bit after transmit data has been transferred to the transmit buffer. The E-DMAC resets this bit on completion of a frame transfer or when transmission is suspended.
Bit 31: TACT 0 Description The transmit descriptor is invalid Indicates that valid data has not been written to the transmit buffer by the CPU, or this bit has been reset by a write-back operation on termination of E-DMAC frame transfer processing (completion or suspension of transmission) If this state is recognized in an E-DMAC descriptor read, the E-DMAC terminates transmit processing and transmit operations cannot be continued (a restart is necessary) 1 The transmit descriptor is valid Indicates that valid data has been written to the transmit buffer by the CPU and frame transfer processing has not yet been executed, or that frame transfer is in progress When this state is recognized in an E-DMAC descriptor read, the E-DMAC continues with the transmit operation
Bit 30--Transmit Descriptor List Last (TDLE): Indicates that this descriptor is the last in the transmit descriptor list. After completion of the corresponding buffer transfer, the E-DMAC references the first descriptor. This specification is used to set a ring configuration for the transmit descriptors.
Bit 30: TDLE 0 1 Description This is not the last transmit descriptor list This is the last transmit descriptor list
Bits 29 and 28--Transmit Frame Position 1, 0 (TFP1, TFP0): These two bits specify the relationship between the transmit buffer and transmit frame.
Rev. 2.00 Mar 09, 2006 page 449 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC) Bit 29: TFP1 0 Bit 28: TFP0 0 1 1 0 1
Description Frame transmission for transmit buffer indicated by this descriptor continues (frame is not concluded) Transmit buffer indicated by this descriptor contains end of frame (frame is concluded) Transmit buffer indicated by this descriptor is start of frame (frame is not concluded) Contents of transmit buffer indicated by this descriptor are equivalent to one frame (one frame/one buffer)
Note: In the preceding and following descriptors, a logically positive relationship must be maintained between the settings of this bit and the TDLE bit.
Bit 27--Transmit Frame Error (TFE): Indicates that one or other bit of the transmit frame status indicated by bits 26 to 0 is set.
Bit 27: TFE 0 1 Description No error during transmission An error of some kind occurred during transmission (see bits 26 to 0)
Bits 26 to 0--Transmit Frame Status 26 to 0 (TFS26 to TFS0): These bits indicate the error status during frame transmission. * TFS26 to TFS9--Reserved * TFS8--Teransmit Abort Detect Note: This bit is set to 1 when any of Transmit Frame Status bits 4 to 0 is set. When this bit is set, the Transmit Frame Error bit (bit 27: TFE) is set to 1. * TFS7 to TFS5--Reserved * TFS4--Illegal Transmit Frame (corresponds to ITF bit in EESR) * TFS3--Carrier Not Detect (corresponds to CND bit in EESR) * TFS2--Detect Loss of Carrier (corresponds to DLC bit in EESR) * TFS1--Collision Detect (corresponds to CD bit in EESR) * TFS0--Transmit Retry Over (corresponds to TRO bit in EESR)
Rev. 2.00 Mar 09, 2006 page 450 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Transmit Descriptor 1 (TD1): Specifies the transmit buffer length (maximum 64 kbytes). Bits 31 to 16--Transmit Buffer Data Length (TDL): These bits specify the valid transfer byte length in the corresponding transmit buffer. Note: When the one frame/multi-buffer system is specified (TD0 and TFP = 10 or 00), the transfer byte length specified in the descriptors at the start and midway can be set in byte units. Bits 15 to 0--Reserved: The bits are always read as 0. The write value should always be 0. Transmit Descriptor 2 (TD2): Specifies the 32-bit transmit buffer start address. Note: The transmit buffer's start address setting must be aligned with a longword boundary. However, when SDRAM is connected, the setting must be aligned with a 16-byte boundary. Bits 31 to 0--Transmit Buffer Address (TBA) Receive Descriptor Figure 10.3 shows the relationship between a receive descriptor and the receive buffer. In frame reception, the E-DMAC performs data rewriting up to a receive buffer 16-byte boundary, regardless of the receive frame length. Finally, the actual receive frame length is reported in the lower 16 bits of RD1 in the descriptor. Data transfer to the receive buffer is performed automatically by the E-DMAC to give a one frame/one buffer or one frame/multi-buffer configuration according to the size of one received frame. Notes: 1. The descriptor's start address setting must be aligned with an address boundary that corresponds with the descriptor's length as set by the E-DMAC mode register (EDMR). 2. The receive buffer's start address setting must be aligned with a longword boundary. However, when SDRAM is connected, the setting must be aligned with a 16-byte boundary. Make the setting so that the size of the receive buffer is aligned with a 16byte boundary. Example: H'0500 (= 1280 bytes)
Rev. 2.00 Mar 09, 2006 page 451 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Receive descriptor 31 30 29 28 27 26 RD0 Receive buffer
RACT RDLE RFP1 RFP0 RFE
RFS 26 to RFS0 Valid receive data
RD1 RD2
31 31
RBL
16 15
RDL
0 0
RBA Padding (4 bytes)
Figure 10.3 Relationship between Receive Descriptor and Receive Buffer Receive Descriptor 0 (RD0): RD0 indicates the receive frame status. The CPU and E-DMAC use RD0 to report the frame transmission status. Bit 31--Receive Descriptor Active (RACT): Indicates that this descriptor is active. The E-DMAC resets this bit after receive data has been transferred to the receive buffer. On completion of receive frame processing, the CPU sets this bit to prepare for reception.
Bit 31: RACT 0 Description The receive descriptor is invalid Indicates that the receive buffer is not ready (access disabled by E-DMAC), or this bit has been reset by a write-back operation on termination of E-DMAC frame transfer processing (completion or suspension of reception) If this state is recognized in an E-DMAC descriptor read, the E-DMAC terminates receive processing and receive operations cannot be continued Reception can be restarted by setting RACT to 1 and executing receive initiation. 1 The receive descriptor is valid Indicates that the receive buffer is ready (access enabled) and processing for frame transfer from the FIFO has not been executed, or that frame transfer is in progress When this state is recognized in an E-DMAC descriptor read, the E-DMAC continues with the receive operation
Rev. 2.00 Mar 09, 2006 page 452 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Bit 30--Receive Descriptor List Last (RDLE): Indicates that this descriptor is the last in the receive descriptor list. After completion of the corresponding buffer transfer, the E-DMAC references the first receive descriptor. This specification is used to set a ring configuration for the receive descriptors.
Bit 30: RDLE 0 1 Description This is not the last receive descriptor list This is the last receive descriptor list (the next descriptor is inactive)
Bits 29 and 28--Receive Frame Position 1, 0 (RFP1, RFP0): These two bits specify the relationship between the receive buffer and receive frame.
Bit 29: RFP 0 Bit 28: RFP 0 1 1 0 1 Description Frame reception for receive buffer indicated by this descriptor continues (frame is not concluded) Receive buffer indicated by this descriptor contains end of frame (frame is concluded) Receive buffer indicated by this descriptor is start of frame (frame is not concluded) Contents of receive buffer indicated by this descriptor are equivalent to one frame (one frame/one buffer)
Bit 27--Receive Frame Error (RFE): Indicates that one or other bit of the receive frame status indicated by bits 26 to 0 is set. Whether or not the multicast address frame receive information which is part of the frame status, is copied into this bit is specified by the transmit/receive status copy enable register.
Bit 27: RFE 0 1 Description No error during reception (Initial value) An error of some kind occurred during reception (see bits 26 to 0)
Bits 26 to 0--Receive Frame Status 26 to 0 (RFS26 to RFS0): These bits indicate the error status during frame reception. * RFS26 to RFS10--Reserved * RFS9--Receive FIFO Overflow (corresponds to RFOF bit in EESR) * RFS8--Reserve Abort Detect
Rev. 2.00 Mar 09, 2006 page 453 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Note: This bit is set to 1 when any of Receive Frame Status bit 9, bit 7, bits 4 to 0 is set. When this bit is set, the Receive Frame Error bit (bit 27: RFE) is set to 1. * RFS7--Receive Multicast Address Frame (corresponds to RMAF bit in EESR) * RFS6--Reserved*1 * RSF5-- Receive Frame Discard Request Assertion (corresponds to RFAR bit in EESR)*1 * RFS4--Receive Residual-Bit Frame (corresponds to RRF bit in EESR) * RFS3--Receive Too-Long Frame (corresponds to RTLF bit in EESR) * RFS2--Receive Too-Short Frame (corresponds to RTSF bit in EESR) * RFS1--PHY-LSI Receive Error (corresponds to PRE bit in EESR) * RFS0--CRC Error on Received Frame (corresponds to CERF bit in EESR) Note: 1. Only HD6417616 is effective. HD6417615 is Reserved bit. Receive Descriptor 1 (RD1): Specifies the receive buffer length (maximum 64 kbytes). Bits 31 to 16--Receive Buffer Length (RBL): These bits specify the maximum transfer byte length in the corresponding receive buffer. Notes: The transfer byte length must align with a 16-byte boundary (bits 19 to 16 cleared to 0). The maximum receive frame length with one frame per buffer is 1,514 bytes, excluding the CRC data. Therefore, for the receive buffer length specification, a value of 1,520 bytes (H'05F0) that takes account of a 16-byte boundary is set as the maximum receive frame length. Bits 15 to 0--Receive Data Length (RDL): These bits specify the data length of a receive frame stored in the receive buffer. Note: The receive data transferred to the receive buffer does not include the 4-byte CRC data at the end of the frame. The receive frame length is reported as the number of words (valid data bytes) not including this CRC data. Receive Descriptor 2 (RD2): Specifies the 32-bit receive buffer start address. Note: The receive buffer's start address setting must be aligned with a longword boundary. However, when SDRAM is connected, the setting must be aligned with a 16-byte boundary. Bits 31 to 0--Receive Buffer Address (RBA)
Rev. 2.00 Mar 09, 2006 page 454 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.3.2
Transmission
When the transmitter is enabled and the transmit request bit (TR) is set in the E-DMAC transmit request register (EDTRR), the E-DMAC reads the descriptor used last time from the transmit descriptor list (in the initial state, the descriptor indicated by the transmission descriptor start address register (TDLAR)). If the setting of the TACT bit in the read descriptor is "active," the EDMAC reads transmit frame data sequentially from the transmit buffer start address specified by TD2, and transfers it to the EtherC. The EtherC creates a transmit frame and starts transmission to the MII. After DMA transfer of data equivalent to the buffer length specified in the descriptor, the following processing is carried out according to the TFP value. 1. TFP = 00 or 01 (frame continuation): Descriptor write-back is performed after DMA transfer. 2. TFP = 01 or 11 (frame end): Descriptor write-back is performed after completion of frame transmission. The E-DMAC continues reading descriptors and transmitting frames as long as the setting of the TACT bit in the read descriptors is "active." When a descriptor with an "inactive" TACT bit is read, the E-DMAC resets the transmit request bit (TR) in the transmit register and ends transmit processing (EDTRR).
Rev. 2.00 Mar 09, 2006 page 455 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Transmission flowchart SH7616 + memory E-DMAC Transmit FIFO EtherC Ethernet
EtherC/E-DMAC initialization Descriptor and transmit buffer setting Transmit directive Descriptor read
Transmit data transfer Descriptor write-back Descriptor read
Transmit data transfer Frame transmission
Descriptor write-back Transmission completed
Figure 10.4 Sample Transmission Flowchart
Rev. 2.00 Mar 09, 2006 page 456 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.3.3
Reception
When the receiver is enabled and the CPU sets the receive request bit (RR) in the E-DMAC receive request register (EDRRR), the E-DMAC reads the descriptor following the previously used one from the receive descriptor list (in the initial state, the descriptor indicated by the transmission descriptor start address register (TDLAR)), and then enters the receive-standby state. If the setting of the RACT bit is "active" and an own-address frame is received, the E-DMAC transfers the frame to the receive buffer specified by RD2. If the data length of the received frame is greater than the buffer length given by RD1, the E-DMAC performs write-back to the descriptor when the buffer is full (RFP = 10 or 00), then reads the next descriptor. The E-DMAC then continues to transfer data to the receive buffer specified by the new RD2. When frame reception is completed, or if frame reception is suspended because of an error of some kind, the E-DMAC performs write-back to the relevant descriptor (RFP = 11 or 01), and then ends the receive processing. The E-DMAC then reads the next descriptor and enters the receive-standby state again. Note: To receive frames continuously, the receive enable control bit (RNC) must be set to 1 in the receive control register (RCR). After initialization, this bit is cleared to 0.
Rev. 2.00 Mar 09, 2006 page 457 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
Reception flowchart SH7616 + memory E-DMAC Receive FIFO EtherC Ethernet
EtherC/E-DMAC initialization Descriptor and transmit buffer setting Start of reception Descriptor read
Frame reception
Receive data transfer Descriptor write-back Descriptor read
Receive data transfer Descriptor write-back
Descriptor read (preparation for receiving next frame)
Reception completed
Figure 10.5 Sample Reception Flowchart
Rev. 2.00 Mar 09, 2006 page 458 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
10.3.4
Multi-Buffer Frame Transmit/Receive Processing
Multi-Buffer Frame Transmit Processing: If an error occurs during multi-buffer frame transmission, the processing shown in figure 10.6 is carried out. Where the transmit descriptor is shown as inactive (TACT bit = 0) in the figure, buffer data has already been transmitted normally, and where the transmit descriptor is shown as active (TACT bit = 1), buffer data has not been transmitted. If a frame transmit error occurs in the first descriptor part where the transmit descriptor is active (TACT bit = 1), transmission is halted, and the TACT bit cleared to 0, immediately. The next descriptor is then read, and the position within the transmit frame is determined on the basis of bits TFP1 and TFP0 (continuing [00] or end [01]). In the case of a continuing descriptor, the TACT bit is cleared to 0, only, and the next descriptor is read immediately. If the descriptor is the final descriptor, not only is the TACT bit cleared to 0, but write-back is also performed to the TFE and TFS bits at the same time. Data in the buffer is not transmitted between the occurrence of an error and write-back to the final descriptor. If error interrupts are enabled in the EtherC/E-DMAC status interrupt permission register (EESIPR), an interrupt is generated immediately after the final descriptor write-back.
Descriptors
TACT TDLE
00 00 00
Inactivates TACT (changes 1 to 0)
TFP1 TFP0
10 00 00 00 00 00 00 01 10
Buffer Untransmitted data is not transmitted after error occurrence. Descriptor Transmit error occurrence
E-DMAC
10 10 10 10 10 11
Descriptor read Inactivates TACT Descriptor read Inactivates TACT Descriptor read Inactivates TACT Descriptor read Inactivates TACT and writes TFE, TFS
One frame
Transmitted data Untransmitted data
Figure 10.6 E-DMAC Operation after Transmit Error Multi-Buffer Frame Receive Processing: If an error occurs during multi-buffer frame reception, the processing shown in figure 10.7 is carried out. Where the receive descriptor is shown as inactive (RACT bit = 0) in the figure, buffer data has already been received normally, and where the receive descriptor is shown as active (RACT bit =
Rev. 2.00 Mar 09, 2006 page 459 of 906 REJ09B0292-0200
Section 10 Ethernet Controller Direct Memory Access Controller (E-DMAC)
1), this indicates a buffer for which reception has not yet been performed. If a frame receive error occurs in the first descriptor part where the RACT bit = 1 in the figure, reception is halted immediately and a status write-back to the descriptor is performed. If error interrupts are enabled in the EtherC/E-DMAC status interrupt permission register (EESIPR), an interrupt is generated immediately after the write-back. If there is a new frame receive request, reception is continued from the buffer after that in which the error occurred.
Descriptors
RACT RDLE
00 00 00
Inactivates RACT and writes RFE, RFS
10 00 00 00 00 00 00 00 00
RFP1 RFP0
Start of frame
E-DMAC
00
Descriptor read Write-back : : : : :
Receive error occurrence
10 10 10 10 11
New frame reception continues from this buffer
Buffer
Received data Unreceived data
Figure 10.7 E-DMAC Operation after Receive Error
Rev. 2.00 Mar 09, 2006 page 460 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Section 11 Direct Memory Access Controller (DMAC)
11.1 Overview
A two-channel direct memory access controller (DMAC) is included on-chip. The DMAC can be used in place of the CPU to perform high-speed data transfers between external devices equipped with DACK (transfer request acknowledge signal), external memories, on-chip memory, and memory-mapped external devices. Using the DMAC reduces the burden on the CPU and increases the operating efficiency of the chip as a whole. 11.1.1 Features
The DMAC has the following features: * Two channels * Address space: Architecturally 4 Gbytes * Choice of data transfer unit: Byte, word (2-byte), longword (4-byte) or 16-byte unit (In a 16byte transfer, four longword reads are executed, followed by four longword writes.) * Maximum of 16,777,216 (16M) transfers * In the event of a cache hit, CPU instruction processing and DMA operation can be executed in parallel * Single address mode transfers: Either the transfer source or transfer destination (peripheral device) is accessed by a DACK signal (selectable) while the other is accessed by address. One transfer unit of data is transferred in one bus cycle. Possible transfer devices: External devices with DACK and memory-mapped external devices (including external memory) * Dual address mode transfer: Both the transfer source and transfer destination are accessed by address. One transfer unit of data is transferred in two bus cycles. Possible transfer devices: Two external memories External memory and memory-mapped external device Two memory-mapped external devices External memory and on-chip peripheral module (excluding DMAC, BSC, UBC, cachememory, E-DMAC, and EtherC) Memory-mapped external device and on-chip peripheral module (excluding DMAC, BSC, UBC, cache-memory, E-DMAC, and EtherC)
Rev. 2.00 Mar 09, 2006 page 461 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Two on-chip peripheral modules (excluding DMAC, BSC, UBC, cache-memory, EDMAC, and EtherC) On-chip memory and memory-mapped external device Two on-chip memories On-chip memory and on-chip peripheral modules (excluding DMAC, BSC, UBC, cachememory, E-DMAC, and EtherC) On-chip memory and external memory * Transfer requests External request: from the DREQn pins. Edge or level detection, and active-low or activehigh mode, can be specified for DREQn. On-chip peripheral module requests: serial communication interface with FIFO (SCIF), 16-bit timer pulse unit (TPU), serial I/O with FIFO (SIOF), serial I/O (SIO) Auto-request: the transfer request is generated automatically within the DMAC * Choice of bus mode Cycle steal mode Burst mode * Choice of channel priority order Fixed mode Round robin mode * An interrupt request can be sent to the CPU on completion of data transfer
Rev. 2.00 Mar 09, 2006 page 462 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.1.2
Block Diagram
Figure 11.1 shows the DMAC block diagram.
On-chip memory
Internal bus
On-chip peripheral module
Peripheral bus
SARn DARn Iteration control Register control Start-up control Request priority control TCRn
DMAC module bus
DREQn
On-chip peripheral module request BH DACKn DEIn External ROM External RAM External I/O (memory mapped) External I/O (with acknowledge) Bus controller DMAOR: SARn: DARn: TCRn: CHCRn: VCRDMAn: DEIn: On-chip peripheral module request: BH: n:
CHCRn
DMAOR
External bus
Interrupt control
VCRDMAn
Bus interface
DMAC
DMA operation register DMA source address register DMA destination address register DMA transfer count register DMA channel control register DMA vector number register DMA transfer end interrupt request to CPU Interrupt transfer request from on-chip SCIF, SIOF, SIO, TPU Burst hint 0, 1
Figure 11.1 DMAC Block Diagram
Rev. 2.00 Mar 09, 2006 page 463 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.1.3
Pin Configuration
Table 11.1 shows the DMAC pin configuration. Table 11.1 Pin Configuration
Channel 0 Name DMA transfer request DMA transfer request acknowledge 1 DMA transfer request DMA transfer request acknowledge All Burst hint Symbol DREQ0 DACK0 DREQ1 DACK1 BH I/O I O I O O Function DMA transfer request input from external device to channel 0 DMA transfer request acknowledge output from channel 0 to external device DMA transfer request input from external device to channel 1 DMA transfer request acknowledge output from channel 1 to external device Burst transfer in 16-byte transfer mode
Rev. 2.00 Mar 09, 2006 page 464 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.1.4
Register Configuration
Table 11.2 summarizes the DMAC registers. The DMAC has a total of 13 registers. Each channel has six control registers. One control register is shared by both channels. Table 11.2 Register Configuration
Channel Name 0 DMA destination address register 0 DMA transfer count register 0 DMA vector number register 0 DMA request/response selection control register 0 1 DMA destination address register 1 DMA transfer count register 1 DMA vector number register 1 DMA request/response selection control register 1 All DMA operation register Abbr. DAR0 TCR0 R/W R/W R/W R/W Initial Value Undefined Undefined Address Access 3 Size*
DMA source address register 0 SAR0
H'FFFFFF80 32 H'FFFFFF84 32
DMA channel control register 0 CHCR0 DRCR0
Undefined H'FFFFFF88 32 *1 H'00000000 H'FFFFFF8C 32 R/(W) Undefined H'00 Undefined Undefined Undefined
1
VCRDMA0 R/W R/W R/W R/W R/W
H'FFFFFFA0 32 3 H'FFFFFE71 8* H'FFFFFF90 32
DMA source address register 1 SAR1 DAR1 TCR1
H'FFFFFF94 32 H'FFFFFF98 32 H'FFFFFFA8 32 3 H'FFFFFE72 8*
DMA channel control register 1 CHCR1 DRCR1 DMAOR
R/(W)* H'00000000 H'FFFFFF9C 32 Undefined H'00
2
VCRDMA1 R/(W) R/(W)
R/(W)* H'00000000 H'FFFFFFB0 32
Notes: 1. Only 0 can be written to bit 1 of CHCR0 and CHCR1, after reading 1, to clear the flags. 2. Only 0 can be written to bits 1 and 2 of the DMAOR, after reading 1, to clear the flags. 3. Access DRCR0 and DRCR1 in byte units. Access all other registers in longword units.
Rev. 2.00 Mar 09, 2006 page 465 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.2
11.2.1
Register Descriptions
DMA Source Address Registers 0 and 1 (SAR0, SAR1)
Bit: Initial value: R/W: 31 -- R/W 30 -- R/W 29 -- R/W ... ... ... ... -- R/W -- R/W -- R/W -- R/W 3 2 1 0
DMA source address registers 0 and 1 (SAR0 and SAR1) are 32-bit read/write registers that specify the source address of a DMA transfer. During a DMA transfer, these registers indicate the next source address. (In single-address mode, SAR is ignored in transfers from external devices with DACK to memory-mapped external devices or external memory). In 16-byte unit transfers, always set the value of the source address to a 16-byte boundary (16n address). Operation results cannot be guaranteed if other values are used. Transmission in 16-byte units can be set only in auto-request mode and at edge detection in external request mode. Values are retained in a reset, in standby mode, and when the module standby function is used. 11.2.2 DMA Destination Address Registers 0 and 1 (DAR0, DAR1)
Bit: Initial value: R/W: 31 -- R/W 30 -- R/W 29 -- R/W ... ... ... ... -- R/W -- R/W -- R/W -- R/W 3 2 1 0
DMA destination address registers 0 and 1 (DAR0 and DAR1) are 32-bit read/write registers that specify the destination address of a DMA transfer. During a DMA transfer, these registers indicate the next destination address. (In single-address mode, DAR is ignored in transfers from memorymapped external devices or external memory to external devices with DACK). In 16-byte unit transfers, always set the value of the source address to a 16-byte boundary (16n address). Operation results cannot be guaranteed if other values are used. Transmission in 16-byte units can be set only in auto-request mode and at edge detection in external request mode. Values are retained in a reset, in standby mode, and when the module standby function is used. If synchronous DRAM is accessed when performing 16-byte-unit transfer, a 16-byte boundary (address 16n) value must be set for the destination address.
Rev. 2.00 Mar 09, 2006 page 466 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.2.3
DMA Transfer Count Registers 0 and 1 (TCR0, TCR1)
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 23 -- R/W 30 -- 0 R 22 -- R/W 29 -- 0 R 21 -- R/W 28 -- 0 R ... ... ... ... -- R/W -- R/W -- R/W -- R/W 27 -- 0 R 3 26 -- 0 R 2 25 -- 0 R 1 24 -- 0 R 0
DMA transfer count registers 0 and 1 (TCR0 and TCR1) are 32-bit read/write registers that specify the DMA transfer count. The lower 24 of the 32 bits are valid. The value is written as 32 bits, including the upper eight bits. The number of transfers is 1 when the setting is H'00000001, 16,777,215 when the setting is H'00FFFFFF and 16, 777,216 (the maximum) when H'00000000 is set. During a DMA transfer, these registers indicate the remaining transfer count. Set the initial value as the write value in the upper eight bits. These bits always read 0. Values are retained in a reset, in standby mode, and when the module standby function is used. For 16-byte transfers, set the count to 4 times the number of transfers. Operation is not guaranteed if an incorrect value is set. 11.2.4 DMA Channel Control Registers 0 and 1 (CHCR0, CHCR1)
Bit: Initial value: R/W: Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 15 DM1 0 R/W 7 AL 0 R/W 30 -- 0 R 14 DM0 0 R/W 6 DS 0 R/W 29 -- 0 R 13 SM1 0 R/W 5 DL 0 R/W ... ... ... ... 12 SM0 0 R/W 4 TB 0 R/W 19 -- 0 R 11 TS1 0 R/W 3 TA 0 R/W 18 -- 0 R 10 TS0 0 R/W 2 IE 0 R/W 17 -- 0 R 9 AR 0 R/W 1 TE 0 R/(W)* 16 -- 0 R 8 AM 0 R/W 0 DE 0 R/W
Note: Only 0 can be written, to clear the flag. Rev. 2.00 Mar 09, 2006 page 467 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
DMA channel control registers 0 and 1 (CHCR0 and CHCR1) are 32-bit read/write registers that control the DMA transfer mode. They also indicate the DMA transfer status. Only the lower 16 of the 32 bits are valid. They should be read and written as 32-bit values, including the upper 16 bits. The registers are initialized to H'00000000 by a reset and in standby mode. Values are retained during a module standby. Bits 31 to 16--Reserved: These bits are always read as 0. The write value should always be 0. Bits 15 and 14--Destination Address Mode Bits 1, 0 (DM1, DM0): Select whether the DMA destination address is incremented, decremented or left fixed (in single address mode, DM1 and DM0 are ignored when transfers are made from a memory-mapped external device, or external memory to an external device with DACK). DM1 and DM0 are initialized to 00 by a reset and in standby mode. Values are retained during a module standby.
Bit 15: DM1 0 Bit 14: DM0 0 1 Description Fixed destination address (Initial value) Destination address is incremented (+1 for byte transfer size, +2 for word transfer size, +4 for longword transfer size, +16 for 16-byte transfer size) Destination address is decremented (-1 for byte transfer size, -2 for word transfer size, -4 for longword transfer size, -16 for 16-byte transfer size) Reserved (setting prohibited)
1
0
1
Bits 13 and 12--Source Address Mode Bits 1, 0 (SM1, SM0): Select whether the DMA source address is incremented, decremented or left fixed. (In single address mode, SM1 and SM0 are ignored when transfers are made from an external device with DACK to a memory-mapped external device, or external memory.) For a 16-byte transfer, the address is incremented by +16 regardless of the SM1 and SM0 values. SM1 and SM0 are initialized to 00 by a reset and in standby mode. Values are retained during a module standby.
Bit 13: SM1 0 Bit 12: SM0 0 1 Description Fixed source address (+16 for 16-byte transfer size) (Initial value) Source address is incremented (+1 for byte transfer size, +2 for word transfer size, +4 for longword transfer size, +16 for 16-byte transfer size) Source address is decremented (-1 for byte transfer size, -2 for word transfer size, -4 for longword transfer size, +16 for 16-byte transfer size) Reserved (setting prohibited)
1
0
1
Rev. 2.00 Mar 09, 2006 page 468 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bits 11 and 10--Transfer Size Bits (TS1, TS0): Select the DMA transfer size. When 11 is set to bits TS1 and TS0 (in the 16-byte unit), request mode is available only in auto-request mode and at edge detection in external request mode. When 11 is set to bits TS1 and TS0 (in the 16-byte unit) and level detection in external request mode and internal peripheral-module request mode are set, system operations are not guaranteed. TS1 and TS0 are initialized to 00 by a reset and in standby mode. Values are retained during a module standby.
Bit 11: TS1 0 1 Bit 10: TS0 0 1 0 1 Description Byte unit* Word (2-byte) unit Longword (4-byte) unit 16-byte unit (4 longword transfers) (initial value)
Note: * The byte unit setting should not be used if a destination address has been set in internal memory for the dual address mode.
Bit 9--Auto Request Mode Bit (AR): Selects either auto-request mode (in which transfer requests are generated automatically within the DMAC) or a mode using external requests or requests from on-chip peripheral modules (SCIF, TPU, SIOF, SIO). The AR bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 9: AR 0 1 Description External/on-chip peripheral module request mode Auto-request mode (Initial value)
Bit 8--Acknowledge/Transfer Mode Bit (AM): In dual address mode, this bit selects whether the DACKn signal is output during the data read cycle or write cycle. In single-address mode, it selects whether to transfer data from memory to device or from device to memory. The AM bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 8: AM 0 1 Description DACKn output in read cycle (dual address mode)/transfer from memory to device (single address mode) (Initial value) DACKn output in write cycle (dual address mode)/transfer from device to memory (single address mode)
Rev. 2.00 Mar 09, 2006 page 469 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bit 7--Acknowledge Level Bit (AL): Selects whether the DACKn signal is an active-high signal or an active-low signal. The AL bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 7: AL 0 1 Description DACKn is an active-low signal DACKn is an active-high signal (Initial value)
Bit 6--DREQn Select Bit (DS): Selects the DREQn input detection used. When 0 (level detection) is set to bit DS, set 0 (cycle-steal mode) to the transfer bus mode bit (TB). When 0 is set to bit DS and 1 (burst mode) is set to bit TB, system operations are not guaranteed. The DS bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 6: DS 0 1 Description Detected by level Can be set only in cycle-steal mode Detected by edge (Initial value)
Bit 5--DREQn Level Bit (DL): Selects the DREQn input detection level. The DL bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 5: DL 0 1 Description When DS is 0, DREQ is detected by low level; when DS is 1, DREQ is detected at falling edge (Initial value) When DS is 0, DREQ is detected by high level; when DS is 1, DREQ is detected at rising edge
Bit 4--Transfer Bus Mode Bit (TB): Selects the bus mode for DMA transfers. When 1 (burst mode) is set to bit TB, set 1 (edge detection) to the DREQ select bit (DS). When 1 is set to bit TB and 0 (level detection) is set to bit DS, system operations are not guaranteed. The TB bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 4: TB 0 1 Description Cycle-steal mode Burst mode (Initial value)
Rev. 2.00 Mar 09, 2006 page 470 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bit 3--Transfer Address Mode Bit (TA): Selects the DMA transfer address mode. The TA bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 3: TA 0 1 Description Dual address mode Single address mode (Initial value)
Bit 2--Interrupt Enable Bit (IE): Determines whether or not to request a CPU interrupt at the end of a DMA transfer. When the IE bit is set to 1, an interrupt (DEI) request is sent to the CPU when the TE bit is set. The IE bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 2: IE 0 1 Description Interrupt request disabled Interrupt request enabled (Initial value)
Bit 1--Transfer-End Flag Bit (TE): Indicates that the transfer has ended. When the value in the DMA transfer count register (TCR) becomes 0, the DMA transfer ends normally and the TE bit is set to 1. When TCR is not 0, the TE bit is not set if the transfer ends because of an NMI interrupt or DMA address error, or because the DME bit in the DMA operation register (DMAOR) or the DE bit was cleared. To clear the TE bit, read 1 from it and then write 0. When the TE bit is set, setting the DE bit to 1 will not enable a transfer. The TE bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 1: TE 0 1 Description DMA has not ended or was aborted Cleared by reading 1 from the TE bit and then writing 0 DMA has ended normally (by TCR = 0) (Initial value)
Rev. 2.00 Mar 09, 2006 page 471 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bit 0--DMA Enable Bit (DE): Enables or disables DMA transfers. In auto-request mode, the transfer starts when this bit or the DME bit in DMAOR is set to 1. The NMIF and AE bits in DMAOR and the TE bit must be all set to 0. In external request mode or on-chip peripheral module request mode, the transfer begins when the DMA transfer request is received from the relevant device or on-chip peripheral module, provided this bit and the DME bit are set to 1. As with the auto-request mode, the TE bit and the NMIF and AE bits in DMAOR must all be set to 0. The transfer can be stopped by clearing this bit to 0. The DE bit is initialized to 0 by a reset and in standby mode. Its value is retained during a module standby.
Bit 0: DE 0 1 Description DMA transfer disabled DMA transfer enabled (Initial value)
11.2.5
DMA Vector Number Registers 0 and 1 (VCRDMA0, VCRDMA1)
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 VC7 -- R/W 30 -- 0 R 6 VC6 -- R/W 29 -- 0 R 5 VC5 -- R/W ... ... ... ... 4 VC4 -- R/W 11 -- 0 R 3 VC3 -- R/W 10 -- 0 R 2 VC2 -- R/W 9 -- 0 R 1 VC1 -- R/W 8 -- 0 R 0 VC0 -- R/W
DMA vector number registers 0 and 1 (VCRDMA0, VCRDMA1) are 32-bit read/write registers that set the DMAC transfer-end interrupt vector number. Only the lower eight bits of the 32 are valid. They are written as 32-bit values, including the upper 24 bits. Values are retained in a reset, in standby mode, and when the module standby function is used. Bits 31 to 8--Reserved: These bits are always read as 0. The write value should always be 0. Bits 7 to 0--Vector Number Bits 7-0 (VC7-VC0): Set the interrupt vector numbers at the end of a DMAC transfer. Interrupt vector numbers of 0-127 can be set. When a transfer-end interrupt occurs, the vector number is fetched and control is transferred to the specified interrupt handling routine. The VC7-VC0 bits retain their values in a reset and in standby mode. As the maximum vector number is 127, 0 must always be written to VC7.
Rev. 2.00 Mar 09, 2006 page 472 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.2.6
DMA Request/Response Selection Control Registers 0 and 1 (DRCR0, DRCR1)
Bit: Initial value: R/W: 7 -- 0 R 6 -- 0 R 5 -- 0 R 4 RS4 0 R/W 3 RS3 0 R/W 2 RS2 0 R/W 1 RS1 0 R/W 0 RS0 0 R/W
DMA request/response selection control registers 0 and 1 (DRCR0, DRCR1) are 8-bit read/write registers that set the DMAC transfer request source. They are written as 8-bit values. They are initialized to H'00 by a reset, but retain their values in standby mode and a module standby. Bits 7 to 5--Reserved: These bits are always read as 0. The write value should always be 0. Bits 4 to 0--Resource Select Bits 4 to 0 (RS4-RS0): Specify which transfer request to input to the DMAC. Changing the transfer request source must be done when the DMA enable bit (DE) is 0. See section 11.3.4, DMA Transfer Types, for the possible setting combinations. Bits RS4 to RS0 are initialized to 001 by a reset.
Bit 4: RS4 0 Bit 3: RS3 0 Bit 2: RS2 0 Bit 1: RS1 0 1 1 0 Bit 0: RS0 0 1 0 1 0 1 1 1 1 0 1 Description DREQ (external request) Reserved (setting prohibited) Reserved (setting prohibited) Reserved (setting prohibited) Reserved (setting prohibited) SCIF channel 1 RXI (on-chip SCI with FIFO channel 1 receive-data-full interrupt request)* SCIF channel 1 TXI (on-chip SCI with FIFO channel 1 transmit-data-empty interrupt request)* Reserved (setting prohibited) (Initial value)
Rev. 2.00 Mar 09, 2006 page 473 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC) Bit 4: RS4 0 Bit 3: RS3 1 Bit 2: RS2 0 Bit 1: RS1 0 Bit 0: RS0 0 1 1 0 1 1 0 0 1 0 0 1 0 1 1 0 0 0 0 1 1 0 1 1 0 0 1 1 0 1 1 0 0 0 1 1 0 1 *
Description Reserved (setting prohibited) SCIF channel 2 RXI (on-chip SCI with FIFO channel 2 receive-data-full interrupt request)* SCIF channel 2 TXI (on-chip SCI with FIFO channel 2 transmit-data-empty interrupt request)* Reserved (setting prohibited) TPU TGI0A (TPU input capture channel 0A interrupt request)* TPU TGI0B (TPU input capture channel 0B interrupt request)* TPU TGI0C (TPU input capture channel 0C interrupt request)* TPU TGI0D (TPU input capture channel 0D interrupt request)* Reserved (setting prohibited) SIOF RDFI (SIO with FIFO receive-data-full interrupt request)* SIOF TDEI (SIO with FIFO transmit-data-empty interrupt request)* Reserved (setting prohibited) Reserved (setting prohibited) SIO channel 1 RDFI (SIO channel 1 receive-datafull interrupt request)* SIO channel 1 TDEI (SIO channel 1 transmit-dataempty interrupt request)* Reserved (setting prohibited) Reserved (setting prohibited) SIO channel 2 RDFI (SIO channel 2 receive-datafull interrupt request)* SIO channel 2 TDEI (SIO channel 2 transmit-dataempty interrupt request)* Reserved (setting prohibited) Reserved (setting prohibited)
1
*
Note: * When a transfer request is generated by an on-chip module, select cycle-steal as the bus mode, dual transfer as the transfer mode, and falling edge detection for the DREQn setting.
Rev. 2.00 Mar 09, 2006 page 474 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.2.7
DMA Operation Register (DMAOR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 31 -- 0 R 7 -- 0 R 30 -- 0 R 6 -- 0 R 29 -- 0 R 5 -- 0 R ... ... ... ... 4 -- 0 R 11 -- 0 R 3 PR 0 R/W 10 -- 0 R 2 AE 0 R/(W)* 9 -- 0 R 1 NMIF 0 R/(W)* 8 -- 0 R 0 DME 0 R/W
Note: * Only 0 can be written, to clear the flag.
The DMA operation register (DMAOR) is a 32-bit read/write register that controls the DMA transfer mode. It also indicates the DMA transfer status. Only the lower four of the 32 bits are valid. DMAOR is written as a 32-bit value, including the upper 28 bits. DMAOR is initialized to H'00000000 by a reset and in standby mode. It retains its value when the module standby function is used. Bits 31 to 4--Reserved: These bits are always read as 0. The write value should always be 0. Bit 3--Priority Mode Bit (PR): Specifies whether a fixed channel priority order or round-robin mode is to be used there are simultaneous transfer requests for multiple channels. It is initialized to 0 by a reset and in standby mode. It retains its value when the module standby function is used.
Bit 3: PR 0 1 Description Fixed priority (channel 0 > channel 1) (Initial value) Round-robin (Top priority shifts to bottom after each transfer. The priority for the first DMA transfer after a reset is channel 1 > channel 0)
Rev. 2.00 Mar 09, 2006 page 475 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bit 2--Address Error Flag Bit (AE): This flag indicates that an address error has occurred in the DMAC. When the AE bit is set to 1, DMA transfer cannot be enabled even if the DE bit in the DMA channel control register (CHCR) is set to 1. To clear the AE bit, read 1 from it and then write 0. Operation is performed up to the DMAC transfer being executed when the address error occurred. AE is initialized to 0 by a reset and in standby mode. It retains its value when the module standby function is used.
Bit 2: AE 0 1 Description No DMAC address error To clear the AE bit, read 1 from it and then write 0 Address error by DMAC (Initial value)
Bit 1--NMI Flag Bit (NMIF): This flag indicates that an NMI interrupt has occurred. When the NMIF bit is set to 1, DMA transfer cannot be enabled even if the DE bit in the DMA channel control register (CHCR) and the DME bit are set to 1. To clear the NMIF bit, read 1 from it and then write 0. Operation is completed up to the end of the DMAC transfer being executed when NMI was input. When the NMI interrupt is input while the DMAC is not operating, the NMIF bit is set to 1. The NMIF bit is initialized to 0 by a reset or in the standby mode. It retains its value when the module standby function is used.
Bit 1: NMIF 0 1 Description No NMIF interrupt To clear the NMIF bit, read 1 from it and then write 0 NMIF interrupt has occurred (Initial value)
Bit 0--DMA Master Enable Bit (DME): Enables or disables DMA transfers on all channels. A DMA transfer becomes enabled when the DE bit in the CHCR and the DME bit are set to 1. For this to be effective, the TE bit in CHCR and the NMIF and AE bits must all be 0. When the DME bit is cleared, all channel DMA transfers are aborted. DME is initialized to 0 by a reset and in standby mode. It retains its value when the module standby function is used.
Bit 0: DME 0 1 Description DMA transfers disabled on all channels DMA transfers enabled on all channels (Initial value)
Rev. 2.00 Mar 09, 2006 page 476 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.3
Operation
When there is a DMA transfer request, the DMAC starts the transfer according to the predetermined channel priority; when the transfer-end conditions are satisfied, it ends the transfer. Transfers can be requested in three modes: auto-request, external request, and on-chip module request. A transfer can be in either single address mode or dual address mode. The bus mode can be either burst or cycle-steal. 11.3.1 DMA Transfer Flow
After the DMA source address registers (SAR), DMA destination address registers (DAR), DMA transfer count registers (TCR), DMA channel control registers (CHCR), DMA vector number registers (VCRDMA), DMA request/response selection control registers (DRCR), and DMA operation register (DMAOR) are initialized (initializing sets each register so that ultimately the condition (DE = 1, DME = 1, TE = 0, NMIF = 0, AE = 0) is satisfied), the DMAC transfers data according to the following procedure: 1. Checks to see if transfer is enabled (DE = 1, DME = 1, TE = 0, NMIF = 0, AE = 0) 2. When a transfer request occurs and transfer is enabled, the DMAC transfers 1 transfer unit of data. (In auto-request mode, the transfer begins automatically after register initialization. The TCR value will be decremented by 1.) The actual transfer flows vary depending on the address mode and bus mode. 3. When the specified number of transfers have been completed (when TCR reaches 0), the transfer ends normally. If the IE bit in CHCR is set to 1 at this time, a DEI interrupt request is sent to the CPU. 4. When an address error occurs in the DMAC or an NMI interrupt is generated, the transfer is aborted. Transfers are also aborted when the DE bit in CHCR or the DME bit in DMAOR is changed to 0.
Figure 11.2 shows a flowchart illustrating this procedure.
Rev. 2.00 Mar 09, 2006 page 477 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Start Initial settings (SAR, DAR, TCR, CHCR, VCRDMA, DRCR, DMAOR)
DE, DME = 1 and NMIF, AE, TE = 0? Yes Has a transfer request been generated?*1 Yes
No
No *3
*2 Bus mode, transfer request mode, DREQ detection method?
Transfer TCR-1 TCR, SAR, and DAR updated *4 No TCR = 0? Yes DEI interrupt request (when IE = 1) NMIF = 1, or AE = 1, or DE = 0, or DME = 0? Yes TE = 1 TE = 1 16-byte transfer in progress? *5
NMIF = 1, No or AE = 1, or DE = 0, or DME = 0? Yes No Transfer aborted
End transfer
End normally
Notes: 1. In auto-request mode, the transfer will start when the NMIF, AE, and TE bits are all 0 and the DE and DME bits are then set to 1. 2. Cycle-steal mode. 3. In burst mode, DREQ = edge detection (external request), or auto-request mode in burst mode. 4. 16-byte transfer cycle in progress. 5. End of a 16-byte transfer cycle.
Figure 11.2 DMA Transfer Flow
Rev. 2.00 Mar 09, 2006 page 478 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.3.2
DMA Transfer Requests
DMA transfer requests are usually generated in either the data transfer source or destination, but they can also be generated by devices that are neither the source nor the destination. Transfers can be requested in three modes: auto-request, external request, and on-chip peripheral module request. The request mode is selected with the AR bit in DMA channel control registers 0 and 1 (CHCR0, CHCR1) and the RS0, RS1, RS2, RS3 and RS4 bits in DMA request/response selection control registers 0 and 1 (DRCR0, DRCR1). Table 11.3 Selecting the DMA Transfer Request Using the AR and RS Bits
CHCR AR 0 RS4 0 RS3 0 DRCR RS2 0 1 1 0 1 RS1 0 0 1 0 1 0 1 1 1 0 0 1 1 1 * * 0 * 0 1 0 1 0 1 * Note: * Don't care 0 1 0 1 0 * Auto-request mode 0 1 RS0 0 1 0 1 0 Request Mode Module request mode Resource Selection DREQ (external request) SCIF channel 1 RXI SCIF channel 1 TXI SCIF channel 2 RXI SCIF channel 2 TXI TPU TGI0A TPU TGI0B TPU TGI0C TPU TGI0D SIOF RDFI SIOF TDEI SIO channel 1 RDFI SIO channel 1 TDEI SIO channel 2 RDFI SIO channel 2 TDEI
Auto-Request Mode: When there is no transfer request signal from an external source (as in a memory-to-memory transfer, the auto-request mode allows the DMAC to automatically generate a transfer request signal internally. When the DE bits in CHCR0 and CHCR1 and the DME bit in the DMA operation register (DMAOR) are set to 1, the transfer begins (so long as the TE bits in CHCR0 and CHCR1 and the NMIF and AE bits in DMAOR are all 0).
Rev. 2.00 Mar 09, 2006 page 479 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
External Request Mode: In this mode a transfer is started by a transfer request signal (DREQn) from an external device. Choose one of the modes shown in table 11.4 according to the application system. When DMA transfer is enabled (DE = 1, DME = 1, TE = 0, NMIF = 0, AE = 0), a transfer is performed upon input of a DREQn signal. Table 11.4 Selecting External Request Modes with the TA and AM Bits
CHCR TA 0 AM 0 1 1 0 Transfer Address Mode Dual address mode Dual address mode Single address mode Single address mode
Acknowledge Mode DACKn output in read cycle DACKn output in write cycle Data transferred from memory to device Data transferred from device to memory
Source Any* Any*
Destination Any* Any*
External memory or External device memory-mapped with DACK external device External device with DACK External memory or memory-mapped external device
1
Note: * External memory, memory-mapped external device, and on-chip peripheral module (excluding DMAC, BSC, UBC, cache memory, E-DMAC, and EtherC).
Choose to detect DREQn either by the falling edge or by level using the DS and DL bits in CHCR0 and CHCR1 (DS = 0 is level detection, DS = 1 is edge detection; DL = 0 is active-low, DL = 1 is active-high). The source of the transfer request does not have to be the data transfer source or destination. When 0 (level detection) is set to the DS bit of CHCR0 and CHCR1, set the TB bit to 0 (cyclesteal mode) and set the TS1 and TS0 bits of CHCR0 and CHCR1 to either 00 (byte unit), 01 (word unit), or 10 (long word unit). When 0 is set to the DS bit of CHCR0 and CHCR1, when 1 (burst mode) is set to the TB bit of CHCR0 and CHCR1, and when 11 (16 byte unit) is set to the TS1 and TS0 bits of CHCR1 and CHCR1, operation is not guaranteed.
Rev. 2.00 Mar 09, 2006 page 480 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Table 11.5 Selecting the External Request Signal with the DS and DL Bits
CHCR DS 0 1 DL 0 1 0 1 External Request Low-level detection (can only be set in cycle-steal mode) High-level detection (can only be set in cycle-steal mode) Falling-edge detection Rising-edge detection
On-Chip Module Request Mode: In this mode, transfers are started by a transfer request signal (interrupt request signal) from an on-chip peripheral module. Transfer request signals include SCIF, SIOF or SIO receive-data-full interrupts (RXI, RDFI), SCIF, SIOF or SIO transmit-dataempty interrupts (TXI, TDEI), and TPU general registers (table 11.6). If DMA transfer is enabled (DE = 1, DME = 1, TE = 0, NMIF = 0, AE = 0), DMA transfer starts upon input of a transfer request signal. When RXI or RDFI (transfer request due to an SCIF, SIOF or SIO receive-data-full condition) is set as a transfer request, the transfer source must be the receive data register of the corresponding module (SCFRDR or SIRDR). When TXI or TDEI (transfer request due to an SCIF, SIOF or SIO transmit-data-empty condition) is set as a transfer request, the transfer destination must be the transmit data register of the corresponding module (SCFTDR or SITDR). These restrictions do not apply to TPU transfer requests. When on-chip module request mode is used, an access size permitted by the peripheral module register used as the transfer source or transfer destination must be set in bits TS1 and TS0 of CHCR0 and CHCR1.
Rev. 2.00 Mar 09, 2006 page 481 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Table 11.6 Selecting On-Chip Peripheral Module Request Mode with the AR and RS Bits
DMA DMA Transfer Transfer Request Request RS4 RS3 RS2 RS1 RS0 Source Signal 0 0 1 0 1 1 0 0 1 1 0 1 0 1 0 0 SCIF channel 1 RXI receiver SCIF channel 1 TXI transmitter SCIF channel 2 RXI receiver SCIF channel 2 TXI transmitter TPU channel 0A TGI0A Transfer Destination
AR 0
Transfer Source
Bus Mode Cyclesteal
DREQ Setting Edge, active-low Edge, active-low Edge, active-low Edge, active-low Edge, active-low
SCFRDR1 Any Any
SCFTDR1 Cyclesteal Cyclesteal
SCFRDR2 Any Any Any (excluding on-chip RAM) Any (excluding on-chip RAM) Any (excluding on-chip RAM) Any (excluding on-chip RAM) SIRDR Any SIRDR1 Any SIRDR2 Any
SCFTDR2 Cyclesteal Any Cycle(excluding steal on-chip RAM) Any Cycle(excluding steal on-chip RAM) Any Cycle(excluding steal on-chip RAM) Any Cycle(excluding steal on-chip RAM) Any SITDR Any SITDR1 Any SITDR2 Cyclesteal Cyclesteal Cyclesteal Cyclesteal Cyclesteal Cyclesteal
1
TPU channel 0B
TGI0B
Edge, active-low
1
0
TPU channel 0C
TGI0C
Edge, active-low
1
TPU channel 0D
TGI0D
Edge, active-low
1
0
0
0 1
1 0 1 0 1 0
SIOF receiver SIOF transmitter SIO channel 1 receiver SIO channel 1 transmitter SIO channel 2 receiver SIO channel 2 transmitter
RDFI TDEI RDFI TDEI RDFI TDEI
Edge, active-low Edge, active-low Edge, active-low Edge, active-low Edge, active-low Edge, active-low
1
0 1
1
0
0 1
Rev. 2.00 Mar 09, 2006 page 482 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
For outputting transfer request from the SCIF, SIOF, SIO, and TPU, the corresponding interrupt enable bits must be set to output the interrupt signals. Note that transfer request signals from onchip peripheral modules (interrupt request signals) are sent not just to the DMAC but to the CPU as well. When an on-chip peripheral module is specified as the transfer request source, set the priority level values in the interrupt priority level registers (IPRC-IPRE) of the interrupt controller (INTC) at or below the levels set in the I3-I0 bits of the CPU's status register so that the CPU does not accept the interrupt request signal. With the DMA transfer request signals in table 11.6, when DMA transfer is performed a DMA transfer request (interrupt request) from any module will be cleared at the first transfer. 11.3.3 Channel Priorities
When the DMAC receives simultaneous transfer requests on two channels, it selects a channel according to a predetermined priority order. There is a choice of two priority modes, fixed or round-robin. The mode is selected by the priority bit, PR, in the DMA operation register (DMAOR). Fixed Priority Mode: In this mode, the relative channel priority levels are fixed. When PR is set to 0, channel 0 has higher priority than channel 1. Figure 11.3 shows an example of a transfer in burst mode.
DREQ0 DREQ1 Channel 0 destination CPU CPU CPU Channel 0 source Channel 0 source Channel 1 source Channel 0 destination Channel 1 destination
Bus cycle
Figure 11.3 Fixed Mode DMA Transfer in Burst Mode (Dual Address, DREQn Falling-Edge Detection) In cycle-steal mode, once a channel 0 request is accepted, channel 1 requests are also accepted until the next request is accepted, which makes more effective use of the bus cycle. If requests come simultaneously for channel 0 and channel 1 when DMA operation is starting, the first is transmitted with channel 0, and thereafter channel 1 and channel 0 transfers are performed alternately.
Rev. 2.00 Mar 09, 2006 page 483 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
DREQ0 DREQ1 Channel 0 source CPU CPU CPU Channel 0 destination CPU Channel 1 destination Channel 1 source Channel 0 source CPU
Bus cycle
Figure 11.4 Fixed Mode DMA Transfer in Cycle-Steal Mode (Dual Address, DREQn Low-Level Detection) Round-Robin Mode: Switches the priority of channel 0 and channel 1, shifting their ability to receive transfer requests. Each time one transfer ends on one channel, the priority shifts to the other channel. The channel on which the transfer just finished is assigned low priority. After reset, channel 1 has higher priority than channel 0. Figure 11.5 shows how the priority changes when channel 0 and channel 1 transfers are requested simultaneously and another channel 0 transfer is requested after the first two transfers end. The DMAC operates as follows: 1. Transfer requests are generated simultaneously to channels 1 and 0. 2. Channel 1 has the higher priority, so the channel 1 transfer begins first (channel 0 waits for transfer). 3. When the channel 1 transfer ends, channel 1 becomes the lower-priority channel. 4. The channel 0 transfer begins. 5. When the channel 0 transfer ends, channel 0 becomes the lower-priority channel. 6. A channel 0 transfer is requested. 7. The channel 0 transfer begins. 8. When the channel 0 transfer ends, channel 0 is already the lower-priority channel, so the order remains the same.
Rev. 2.00 Mar 09, 2006 page 484 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Transfer requests 1. Requests occur in channels 0 and 1
Waiting channel
DMAC operation 2. Channel 1 transfer starts
Channel priority order
1>0 Priority changes
0 3. Channel 1 transfer ends
0>1
4. Channel 0 transfer starts None 5. Channel 0 transfer ends Priority changes
1>0
6. Request occurs in channel 0 None
7. Channel 0 transfer starts
Waiting for transfer request
8. Channel 0 transfer ends
Priority does not change
1>0
Figure 11.5 Channel Priority in Round-Robin Mode
Rev. 2.00 Mar 09, 2006 page 485 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.3.4
DMA Transfer Types
It can operate in single address mode or dual address mode, as defined by how many bus cycles the DMAC takes to access the transfer source and transfer destination. The actual transfer operation timing varies with the DMAC bus mode used: cycle-steal mode or burst mode. The DMAC supports all the transfers shown in table 11.7. Table 11.7 Supported DMA Transfers
Destination Source External device with DACK External memory Memory-mapped external device On-chip peripheral module On-chip memory External Device with DACK Not available Single Single Not available Not available External Memory Single Dual Dual Dual* Dual On-Chip Memory-Mapped Peripheral External Device Module Single Dual Dual Dual* Dual On-Chip Memory
Not available Not available Dual* Dual* Dual* Dual* Dual Dual Dual* Dual
Single: Single address mode Dual: Dual address mode Note: * Access size permitted by peripheral module register used as transfer source or transfer destination (excluding DMAC, BSC, UBC, cache memory, E-DMAC, and EtherC).
Address Modes: * Single Address Mode In single address mode, both the transfer source and destination are external; one (selectable) is accessed by a DACKn signal while the other is accessed by address. In this mode, the DMAC performs the DMA transfer in one bus cycle by simultaneously outputting a transfer request acknowledge DACKn signal to one external device to access it, while outputting an address to the other end of the transfer. Figure 11.6 shows an example of a transfer between external memory and external device with DACK. That data is written in external memory in the same bus cycle while the external device outputs data to the data bus.
Rev. 2.00 Mar 09, 2006 page 486 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
External address bus External data bus Chip DMAC External memory
External device with DACK
DACKn DREQn : Data flow
Figure 11.6 Data Flow in Single Address Mode Two types of transfers are possible in single address mode: 1) transfers between external devices with DACK and memory-mapped external devices; and 2) transfers between external devices with DACK and external memory. For both of them, transfer must be requested by the external request signal (DREQn). For the combination of the specifiable setting to perform data transfer using an external request (DREQn), see table 11.9. Figure 11.7 shows the DMA transfer timing for single address mode.
Rev. 2.00 Mar 09, 2006 page 487 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
CKIO A24-A0 CS WE D31-D0 DACKn BS a. External device with DACK to external memory space CKIO A24-A0 CS RD D31-D0 DACKn BS b. External memory space to external device with DACK Address output to external memory space Read strobe signal to external memory space Data output from external memory space DACK signal (active low) to external device with DACK Write strobe signal to external memory space Data output from external device with DACK DACK signal (active low) to external device with DACK Address output to external memory space
Figure 11.7 DMA Transfer Timing in Single Address Mode
Rev. 2.00 Mar 09, 2006 page 488 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
* Dual Address Mode In dual address mode, both the transfer source and destination are accessed (selectable) by address. The source and destination can be located externally or internally. The DMAC accesses the source in the read cycle and the destination in the write cycle, so the transfer is performed in two separate bus cycles. The transfer data is temporarily stored in the DMAC. Figure 11.8 shows an example of a transfer between two external memories in which data is read from one external memory in the read cycle and written to the other external memory in the following write cycle.
External data bus Chip DMAC 2 External memory
External memory 1
: Data flow 1: Read cycle 2: Write cycle
Figure 11.8 Data Flow in Dual Address Mode In dual address mode transfers, external memory and memory-mapped external devices can be mixed without restriction. Specifically, this enables transfers between the following: Transfer between external memory and external memory Transfer between external memory and memory-mapped external device Transfer between memory-mapped external device and memory-mapped external device Transfer between external memory and on-chip peripheral module (excluding DMAC, BSC, UBC, cache, E-DMAC, and EtherC)* Transfer between memory-mapped external device and on-chip peripheral module (excluding DMAC, BSC, UBC, cache, E-DMAC, and EtherC)* Transfer between on-chip memory and on-chip memory Transfer between on-chip memory and memory-mapped external device Transfer between on-chip memory and on-chip peripheral module (excluding DMAC, BSC, UBC, cache, E-DMAC, and EtherC)*
Rev. 2.00 Mar 09, 2006 page 489 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Transfer between on-chip memory and external memory Transfer between on-chip peripheral module (excluding DMAC, BSC, UBC, cache, EDMAC, and EtherC) and on-chip peripheral module (excluding DMAC, BSC, UBC, cache, E-DMAC, and EtherC)* Note: * Access size permitted by peripheral module register used as transfer source or transfer destination (excluding DMAC, BSC, UBC, cache, E-DMAC, and EtherC). Transfer requests can be auto-request, external requests, or on-chip peripheral module requests. If the transfer request source is the SCIF, SIOF or SIO, an SCIF, SIOF or SIO register, respectively, must be the transfer destination or transfer source (see table 11.6). For the combination of the specifiable setting to perform data transfer using an external request (DREQn), see table 11.9. Dual address mode outputs DACKn in either the read cycle or write cycle. The acknowledge/transfer mode bit (AM) of the DMA channel control registers 0 and 1 (CHCR0 and 1) specifies whether DACK is output in either the read cycle or the write cycle. Figure 11.9 shows the DMA transfer timing in dual address mode.
CKIO A24-A0 CS RD WE D31-D0 DACKn BS Read strobe signal to external memory space Write strobe signal to external memory space I/O data of external memory space DMAC acknowledge signal (active-low) Address output to external memory space
Figure 11.9 DMA Transfer Timing in Dual Address Mode (External Memory Space External Memory Space, DACKn Output in Read Cycle)
Rev. 2.00 Mar 09, 2006 page 490 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bus Modes: There are two bus modes: cycle-steal and burst. Select the mode with the TB bits in CHCR0 and CHCR1. * Cycle-Steal Mode In cycle-steal mode, the bus right is given to another bus master each time the DMAC completes one transfer. When another transfer request occurs, the bus right is retrieved from the other bus master and another transfer is performed for one transfer unit. When that transfer ends, the bus right is passed to the other bus master. This is repeated until the transfer end conditions are satisfied. (in the case of 16-byte transfer in dual address mode, the DMAC continues to hold the bus) Cycle-steal mode can be used with all categories of transfer destination, transfer source, and transfer request source. (with the exception of transfers between on-chip peripheral modules) The CPU may take the bus twice when an acknowledge signal is output during the write cycle or in single address mode. Figure 11.10 shows an example of DMA transfer timing in cyclesteal mode. The transfer conditions for the example in the figure are as shown below. When the transfer request source is an external request mode with level detection in the cyclesteal mode, set the TS1 and TS0 bits of CHCR0 and CHCR1 to either 00 (byte unit), 01 (word unit), or 01 (longword unit). If the TS1 and TS0 bits of CHCR0 and CHCR1 are set to 11 (16byte transfer), operation is not guaranteed.
* Dual address mode * DREQn level detection DREQn Bus right returned to CPU Bus cycle CPU CPU CPU DMAC DMAC Read Write CPU DMAC Read DMAC Write CPU
Figure 11.10 DMA Transfer Timing in Cycle-Steal Mode (Dual Address Mode, DREQn Low Level Detection)
Rev. 2.00 Mar 09, 2006 page 491 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
* Burst Mode In burst mode, once the DMAC gets the bus, the transfer continues until the transfer end condition is satisfied. When external request mode is used with level detection of the DREQ pin, however, negating DREQ will pass the bus to the other bus master after completion of the bus cycle of the DMAC that currently has an acknowledged request, even if the transfer end conditions have not been satisfied. When the transfer request source is an on-chip peripheral module, however, cycle-steal mode is always used. Figure 11.11 shows an example of DMA transfer timing in burst mode. The transfer conditions for the example in the figure are as shown below.
* Single address mode * DREQn level detection DREQn
Bus cycle
CPU
CPU
CPU
DMAC DMAC DMAC DMAC
CPU
CPU
CPU
Figure 11.11 DMA Transfer Timing in Burst Mode (Single Address, DREQn Falling-Edge Detection) Refreshes cannot be performed during a burst transfer, so ensure that the number of transfers satisfies the refresh request period when a memory requiring refreshing is used. When the transfer request source is an external request (DREQn) in burst mode, set the DS bit of CHCR0 and CHCR1 to 1 (edge detection). If the DS bits of CHCR0 and CHCR1 are set to 0 (level detection), operation is not guaranteed.
Rev. 2.00 Mar 09, 2006 page 492 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Relationship of Request Modes and Bus Modes by DMA Transfer Category: Table 11.8 shows the relationship between request modes, bus modes, etc., by DMA transfer category. Table 11.8 Relationship of Request Modes and Bus Modes by DMA Transfer Category
Address Mode Single Transfer Range Between external memory and external device with DACK Between external device with DACK, and memory mapped external device Dual Between external memories
3 Request Mode*
Bus Transfer 7 Mode* Size (Byte) B/C B/C B/C B/C C B/C B/C C B/C B/C C B/C B/C C B/C B/C C B/C B/C B/C C 1/2/4/16* 1/2/4/16* 1/2/4/16* 1/2/4/16 1/2/4 1/2/4/16* 1/2/4/16 1/2/4 1/2/4/16* 1/2/4/16 1/2/4 1/2/4* 4 1/2/4*
4 8 8 8
External External External Automatic Internal peripheral 1 module*
8
8
Between external memory and memory mapped external device
External Automatic Internal peripheral 1 module*
Between memory mapped external devices External Automatic Internal peripheral 1 module* Between external memory and internal peripheral module External Automatic Internal peripheral 2 module* Between memory mapped external device and internal peripheral module External Automatic Internal peripheral 2 module* Between internal memories Between internal memory and memory 5 mapped external device* Automatic External Automatic Internal peripheral 1 module*
1/2/4*
4
1/2/4* 4 1/2/4*
4
1/2/4*
4
1/2/4/16 1/2/4/16* 1/2/4/16 1/2/4
8
Rev. 2.00 Mar 09, 2006 page 493 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC) Address Mode Dual Bus Transfer 7 Mode* Size (Byte) B/C C B/C B/C C B/C C 1/2/4* 4 1/2/4*
4
Transfer Range Between internal memory and internal peripheral module Between internal memory and external 6 memory*
Request Mode* Automatic
3
Internal peripheral 2 module* External Automatic Internal peripheral 1 module*
1/2/4/16* 1/2/4/16 1/2/4 1/2/4* 4 1/2/4*
4
8
Between internal peripheral modules
Automatic Internal peripheral 2 module*
Notes: B: Burst mode C: Cycle steal mode 1. For on-chip peripheral module requests, do not specify SCIF, SIOF and SIO as a transfer request source. 2. When the transfer request source is SCIF, SIOF or SIO, the transfer source or transfer destination must be SCIF, SIOF and SIO, respectively. 3. When the request mode is set to internal peripheral module request, set the DS bit and the DL bit of CHCR0 and CHCR1 to 1 and 0, respectively (detection at the falling edge of DREQn). In addition, the bus mode can only be set to cycle-steal mode. 4. Specify the access size that is allowed by the internal peripheral-module registers, which are a transfer source or a transfer destination. 5. When transferring data from internal memory to a memory mapped external device, set DACKn to write-time output. When transferring from a memory mapped external device to internal memory, set DACKn to read-time output. 6. When transferring data from internal memory to external memory, set DACKn to writetime output. When transferring from external memory to internal memory, set DACKn to read-time output. 7. When B (burst mode) is set in the external request mode, set the DS bits of CHCR0 and CHCR1 to 1 (edge detection). If they are set to 0 (level detection), operation cannot be guaranteed. 8. Transfer in units of 16 bytes is enabled only when edge detection has been specified. If transfer is attempted in units of 16 bytes when level detection has been specified, operation cannot be guaranteed.
Rev. 2.00 Mar 09, 2006 page 494 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Table 11.9 shows the combinations of request mode, bus mode, and address mode that can be specified in the external request mode. Table 11.9 Combinations of Request Mode, Bus Mode, and Address Mode Specifiable in the External Request Mode
Dual Address Mode Request Mode External request Level 1 detection* Byte Word Longword 16-byte unit Edge 2 detection* Byte Word Longword 16-byte unit Burst Mode -- -- -- -- O O O O Cycle-Steal Mode O O O -- O O O O Single Address Mode Burst Mode -- -- -- -- O O O O Cycle-Steal Mode O O O -- O O O O
Notes: O: Can be set --: Cannot be set 1. The same for high-level and low-level detection. 2. The same for rising-edge detection and falling-edge detection.
Bus Mode and Channel Priority: When a given channel (1) is transferring in burst mode and there is a transfer request to a channel (0) with a higher priority, the transfer of the channel with higher priority (0) will begin immediately. When channel 0 is also operating in the burst mode, the channel 1 transfer will continue as soon as the channel 0 transfer has completely finished. When channel 0 is in cycle-steal mode, channel 1 will begin operating again after channel 0 completes the transfer of one transfer unit, but the bus will then switch between the two in the order channel 1, channel 0, channel 1, channel 0. Since channel 1 is in burst mode, it will not give the bus to the CPU. This example is illustrated in Figure 11.12.
Bus state
CPU
DMAC ch1 DMAC ch1 DMAC ch0 DMAC ch1 DMAC ch1 DMAC ch0 DMAC ch1 DMAC ch1 DMAC ch0 DMAC ch1 DMAC ch1 ch0 ch1 ch0 DMAC ch1/ch0 bus right transfers ch1 ch0
CPU
CPU
DMAC ch1 Burst mode
DMAC ch1 Burst mode
CPU
Figure 11.12 Bus Status when Multiple Channels are Operating (when priority order is ch0 > ch1, ch1 is set to burst mode, and ch0 to cycle-steal mode)
Rev. 2.00 Mar 09, 2006 page 495 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.3.5
Number of Bus Cycles
The number of states in the bus cycle when the DMAC is the bus master is controlled by the bus state controller (BSC) just as it is when the CPU is the bus master. For details, see section 7, Bus State Controller (BSC). 11.3.6 DMA Transfer Request Acknowledge Signal Output Timing
DMA transfer request acknowledge signal DACKn is output synchronous to the DMA address output specified by the channel control register AM bit of the address bus. Normally, the acknowledge signal becomes valid when DMA address output begins, and becomes invalid 0.5 cycles before the address output ends. (See figure 11.13.) The output timing of the acknowledge signal varies with the settings of the connected memory space. The output timing of acknowledge signals in the memory spaces is shown in figure 11.13.
Clock
DACKn (Active high)
0.5 cycles CPU DMAC
Address bus
Figure 11.13 Example of DACKn Output Timing Acknowledge Signal Output when External Memory Is Set as Ordinary Memory Space: The timing at which the acknowledge signal is output is the same in the DMA read and write cycles specified by the AM bit (figures 11.14 and 11.15). When DMA address output begins, the acknowledge signal becomes valid; 0.5 cycles before address output ends, it becomes invalid. If a wait is inserted in this period and address output is extended, the acknowledge signal is also extended.
Rev. 2.00 Mar 09, 2006 page 496 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
T1 Clock TW T2
DACKn (Active high) DMAC read CPU Basic timing
0.5 cycles Invalid write DMAC write CPU DMAC read 1 wait inserted
Address bus
Figure 11.14 DACKn Output in Ordinary Space Accesses (AM = 0)
Clock
DACKn (Active high) Address bus DMAC read Invalid DMAC write write CPU Basic timing DMAC read 1 wait inserted Invalid write DMAC write
Figure 11.15 DACKn Output in Ordinary Space Accesses (AM = 1) In a longword access of a 16-bit external device (figure 11.16) or an 8-bit external device (figure 11.17), or a word access of an 8-bit external device (figure 11.18), the lower and upper addresses are output 2 and 4 times in each DMAC access in order to align the data. For all of these addresses, the acknowledge signal becomes valid simultaneous with the start of output and the signal becomes invalid 0.5 cycles before the address output ends. When multiple addresses are output in a single access to align data for synchronous DRAM, DRAM, or burst ROM, an acknowledge signal is output to those addresses as well.
Rev. 2.00 Mar 09, 2006 page 497 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock
DACKn (Active high) Address bus *1 DMAC read H *2 DMAC read L
Invalid write DMAC write
CPU H
Basic timing Notes: 1. H: MSB side 2. L: LSB side
Figure 11.16 DACKn Output in Ordinary Space Accesses (AM = 0, Longword Access to 16-Bit External Device)
Clock
DACKn (Active high) Address bus DMAC read HH CPU Basic timing DMAC read HL DMAC read LH DMAC read LL
Figure 11.17 DACKn Output in Ordinary Space Accesses (AM = 0, Longword Access to 8-Bit External Device)
Clock
DACKn (Active high) Address bus
Invalid write CPU DMAC read H DMAC read L DMAC write
Basic timing
Figure 11.18 DACKn Output in Ordinary Space Accesses (AM = 0, Word Access to 8-Bit External Device)
Rev. 2.00 Mar 09, 2006 page 498 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Acknowledge Signal Output when External Memory Is Set as Synchronous DRAM: When external memory is set as synchronous DRAM, DACKn output becomes valid simultaneously with the start of the DMA address, and becomes invalid when the address output ends. When external memory is set as synchronous DRAM auto-precharge and AM = 0, the acknowledge signal is output across the row address, read command, wait and read address of the DMAC read (figure 11.19). Since the synchronous DRAM read has only burst mode, during a single read an invalid address is output; the acknowledge signal, however, is output on the same timing (figure 11.20). At this time, the acknowledge signal is extended until the write address is output after the invalid read. A synchronous DRAM burst read is performed in the case of 16-byte transfer. As 16-byte transfer is enabled only in auto-request mode and in external request mode with edge detection, when using on-chip peripheral module requests or external request mode with level detection, byte, word, or longword should be set as the transfer unit. Operation is not guaranteed if a 16-byte unit is set when using on-chip peripheral module requests or external request mode with level detection. When AM = 1, the acknowledge signal is output across the row address and column address of the DMAC write (figure 11.21).
Clock
DACKn (Active high)
Read command Row address
Address bus
CPU
Read 1
Read 2
Read 3
Read 4
DMAC read (basic timing)
Figure 11.19 DACKn Output in Synchronous DRAM Burst Read (Auto-Precharge, AM = 0)
Rev. 2.00 Mar 09, 2006 page 499 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock
DACKn (Active high)
Address bus
Read command Row address CPU Read Invalid read
Row Column address address
DMAC read (basic timing)
DMAC write (basic timing)
Figure 11.20 DACKn Output in Synchronous DRAM Single Read (Auto-Precharge, AM = 0)
Clock
DACKn (Active high) Row Column address address Address bus DMAC write (basic timing)
Figure 11.21 DACKn Output in Synchronous DRAM Write (Auto-Precharge, AM = 1)
Rev. 2.00 Mar 09, 2006 page 500 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
When external memory is set as bank active synchronous DRAM, during a burst read the acknowledge signal is output across the read command, wait and read address when the row address is the same as the previous address output (figure 11.22). When the row address is different from the previous address, the acknowledge signal is output across the precharge, row address, read command, wait and read address (figure 11.23).
Clock
DACKn (Active high) Read command Address bus CPU Read 1 Read 2 Read 3 Read 4
DMAC read (basic timing)
Figure 11.22 DACKn Output in Synchronous DRAM Burst Read (Bank Active, Same Row Address, AM = 0)
Clock
DACKn (Active high) PreRead Row charge address command CPU DMAC read (basic timing) Read 1 Read 2 Read 3 Read 4
Address bus
Figure 11.23 DACKn Output in Synchronous DRAM Burst Read (Bank Active, Different Row Address, AM = 0)
Rev. 2.00 Mar 09, 2006 page 501 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
When external memory is set as bank active synchronous DRAM, during a single read the acknowledge signal is output across the read command, wait and read address when the row address is the same as the previous address output (figure 11.24). When the row address is different from the previous address, the acknowledge signal is output across the precharge, row address, read command, wait and read address (figure 11.25). Since the synchronous DRAM read has only burst mode, during a single read an invalid address is output; the acknowledge signal is output on the same timing. At this time, the acknowledge signal is extended until the write address is output after the invalid read.
Clock
DACKn (Active high) Address bus
Read command CPU Read Invalid read
Row Column address address
DMAC read (basic timing)
DMAC write (basic timing)
Figure 11.24 DACKn Output in Synchronous DRAM Single Read (Bank Active, Same Row Address, AM = 0)
Clock
DACKn (Active high) Address bus
Row address PreRead charge command Read CPU DMAC read (basic timing) Invalid read
Row Column address address
DMAC write (basic timing)
Figure 11.25 DACKn Output in Synchronous DRAM Single Read (Bank Active, Different Row Address, AM = 0)
Rev. 2.00 Mar 09, 2006 page 502 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
When external memory is set as bank active synchronous DRAM, during a write the acknowledge signal is output across the wait and column address when the row address is the same as the previous address output (figure 11.26). When the row address is different from the previous address, the acknowledge signal is output across the precharge, row address, wait and column address (figure 11.27).
Clock
DACKn (Active high) Column address
Address bus
DMAC write (basic timing)
Figure 11.26 DACKn Output in Synchronous DRAM Write (Bank Active, Same Row Address, AM = 1)
Clock
DACKn (Active high) Row Column Precharge address address Address bus DMAC write (basic timing)
Figure 11.27 DACKn Output in Synchronous DRAM Write (Bank Active, Different Row Address, AM = 1)
Rev. 2.00 Mar 09, 2006 page 503 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
* Synchronous DRAM one-cycle write When a one-cycle write is performed to synchronous DRAM, the DACKn signal is synchronized with the rising edge of the clock. A request by the request signal is accepted while the clock is high during DACKn output.
Transfer Width Transfer bus mode Transfer address mode Byte/Word/Longword 1 Transfer* Cycle-steal mode Single mode *2 DREQn Detection Method DACKn output timing Bus cycle Level Detection Write DACK Basic bus cycle
Notes: 1. Do not set a 16-byte unit; operation is not guaranteed if this setting is made. 2. Cycle-steal mode must be set when DREQ is level-detected.
Clock
Bus cycle
CPU
CPU
DMAC1
CPU
DMAC2
CPU
DMAC3 CPU
DREQn (Active high)
Blind zone
1st acceptance 2nd acceptance 3rd acceptance 4th acceptance
....
DACKn (Active high) RAS
DACK1
DACK2
DACK3
CAS
RD/WR
WEn/DQMxx
Figure 11.28 (a) Synchronous DRAM One-Cycle Write Timing
Transfer Width Transfer bus mode Transfer address mode Byte/Word/Longword Transfer Burst mode Single mode DREQn Detection Method DACKn output timing Bus cycle Edge Detection* Write DACK Basic bus cycle
Note: * Edge detection must be set when burst mode is selected as the transfer bus mode.
Rev. 2.00 Mar 09, 2006 page 504 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock
Bus cycle
CPU
CPU
DMAC1
DMAC2 DMAC3 DMAC4
CPU
CPU
DREQn (Active high) DACKn (Active high) RAS
Blind zone
Acceptance
....
DACK1
DACK2
DACK3
DACK4
CAS
RD/WR
WEn/DQMxx
Figure 11.28 (b) Synchronous DRAM One-Cycle Write Timing Acknowledge Signal Output when External Memory Is Set as DRAM: When external memory is set as DRAM and a row address is output during a read or write, the acknowledge signal is output across the row address and column address (figures 11.29-11.31).
Clock
DACKn (Active high) Address bus
Row Precharge address Column address DMAC read or write (basic timing)
Figure 11.29 DACKn Output in Normal DRAM Accesses (AM = 0 or 1)
Rev. 2.00 Mar 09, 2006 page 505 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock DACKn (Active high) Address bus Column address
DMAC read or write (basic timing)
Figure 11.30 DACKn Output in DRAM Burst Accesses (Same Row Address, AM = 0 or 1)
Clock
DACKn (Active high) PreRow charge address Address bus Column address DMAC read or write (basic timing)
Figure 11.31 DACKn Output in DRAM Burst Accesses (Different Row Address, AM = 0 or 1)
Rev. 2.00 Mar 09, 2006 page 506 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Acknowledge Signal Output When External Memory Is Set as Burst ROM: When external memory is set as burst ROM, the acknowledge signal is output synchronous to the DMA address (no dual writes allowed) (figure 11.32).
Clock
DACKn (Active high) Address bus DMAC cycle DMAC cycle
DMAC (1 wait state)
Figure 11.32 DACKn Output in Nibble Accesses of Burst ROM 11.3.7 DREQn Pin Input Detection Timing
In external request mode, DREQn pin signals are usually detected at the falling edge of the clock pulse (CKIO). When a request is detected, a DMAC bus cycle is produced four cycles later at the earliest and a DMA transfer performed. After the request is detected, the timing of the next input detection varies with the bus mode, address mode, DREQn input detection, and the memory connected. DREQn Pin Input Detection Timing in Cycle-Steal Mode: In cycle-steal mode, once a request is detected from the DREQn pin, the request signal is not detected until DACKn signal output in the next external bus cycle. In cycle-steal mode, request detection is performed from DACKn signal output until a request is detected. Once a request has been accepted, it cannot be canceled midway. The timing from the detection of a request until the next time requests are detectable is shown below. * Cycle-Steal Mode Edge Detection When transfer control is performed using edge detection, perform DREQn/DACKn handshaking as shown in figure 11.33, and perform DREQn input control so that there is a one-to-one relationship between DREQn and DACKn. Operation is not guaranteed if DREQn is input before the corresponding DACKn is output.
Rev. 2.00 Mar 09, 2006 page 507 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
If the DACKn signal is output a number of times, the first DACKn signal for the input DREQn signal indicates the request acceptance start timing, and subsequently each clock edge is sampled.
Clock
Bus cycle DREQn (Rising-edge detection) DACKn (Active high)
CPU 1st acceptance
CPU
DMAC 2nd acceptance
DMAC
CPU
CPU
DMAC 3rd acceptance
DMAC
Figure 11.33 DREQn/DACKn Handshaking
Transfer Width Transfer bus mode Transfer address mode Byte/Word/Longword Cycle-steal mode Dual/single mode DREQn Detection Method DACKn output timing Bus cycle Edge Detection Read DACK/write DACK Basic bus cycle
Clock
Bus cycle
CPU
CPU
DMAC
CPU
DREQn (Active high) DACKn (Active high)
Blind zone 1st acceptance 2nd acceptance
Requests acceptable
Figure 11.34 DREQn Pin Input Detection Timing in Cycle-Steal Mode with Edge Detection
Rev. 2.00 Mar 09, 2006 page 508 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock
Bus cycle
CPU
CPU
DMAC H
DMAC L
DREQn (Active high)
Blind zone 1st 2nd acceptance acceptance
DACKn (Active high)
DACK H
DACK L
Figure 11.35 When a16-Bit External Device is Connected (Edge Detection)
Clock
Bus cycle
CPU
CPU
DMAC HH
DMAC HL
DMAC LH
DMAC LL
DREQn (Active high)
Blind zone 1st 2nd acceptance acceptance
DACK HH DACK HL DACK LH DACK LL
Blind zone
DACKn (Active high)
Figure 11.36 When an 8-Bit External Device is Connected (Edge Detection)
Rev. 2.00 Mar 09, 2006 page 509 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
* Cycle-Steal Mode Edge Detection--16-Bit Transfer With 16-byte transfer, the first request signal is the first transfer request, and the second transfer request is accepted when the next request signal is accepted. The third and fourth requests are accepted in the same way.
Transfer Width Transfer bus mode Transfer address mode 16-Byte Transfer Cycle-steal mode Dual/single mode DREQn Detection Method DACKn output timing Bus cycle Edge Detection Read DACK/write DACK Basic bus cycle
Clock
Bus cycle
CPU
CPU
DMAC*1
DMAC*2 DMAC*3
DMAC*4
DMA
DREQn (Active high)
Blind zone 2nd 1st acceptance acceptance
DACKn (Active high) Note: * n is the nth 16-byte transfer.
DACK*1
DACK*2
DACK*3
DACK*4
Figure 11.37 DREQn Pin Input Detection Timing in Cycle-Steal Mode with Edge Detection (16-Byte Transfer Setting) * Cycle-Steal Mode Level Detection In level detection mode, too, a request cannot be canceled once accepted.
Transfer Width Transfer bus mode Transfer address mode Byte/Word/Longword* Cycle-steal mode Dual/single mode DREQn Detection Method DACKn output timing Bus cycle Level Detection Read DACK/write DACK Basic bus cycle
Note: * Do not set a 16-byte unit; operation is not guaranteed if this setting is made.
Rev. 2.00 Mar 09, 2006 page 510 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock
Bus cycle
CPU
CPU
DMAC
CPU
DREQn (Active high) 1st acceptance DACKn (Active high)
Blind zone
Blind zone 2nd acceptance
Requests acceptable
Figure 11.38 DREQn Pin Input Detection Timing in Cycle-Steal Mode with Level Detection (Byte/Word/Longword Setting)
Clock
Bus cycle
CPU
CPU
DMAC H
DMAC L
DREQn (Active high)
Blind zone 1st acceptance
Blind zone 2nd acceptance
DACKn (Active high)
DACK H
DACK L
Figure 11.39 When a 16-Bit External Device is Connected (Level Detection)
Rev. 2.00 Mar 09, 2006 page 511 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Clock
Bus cycle
CPU
CPU
DMAC HH
DMAC HL
DMAC LH
DMAC LL
DREQn (Active high)
Blind zone 1st acceptance
Blind zone 2nd acceptance
DACKn (Active high)
DACK HH
DACK HL
DACK LH
DACK LL
Figure 11.40 When an 8-Bit External Device is Connected (Level Detection) DREQn Pin Input Detection Timing in Burst Mode: In burst mode, only edge detection is valid for DREQn input. Operation is not guaranteed if level detection is set. With edge detection of DREQn input, once a request is detected, DMA transfer continues until the transfer end condition is satisfied, regardless of the state of the DREQn pin. Request detection is not performed during this time. When the transfer start conditions are fulfilled after the end of transfer, request detection is performed again every cycle.
Clock
Bus cycle
CPU
CPU
DMAC1
DMAC2
DMAC3
DMAC4
CPU
Bus DREQn (Active high) DACKn (Active high)
Blind zone Acceptance
Figure 11.41 DREQn Pin Input Detection Timing in Burst Mode with Edge Detection
Rev. 2.00 Mar 09, 2006 page 512 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.3.8
DMA Transfer End
The DMA transfer ending conditions vary when channels end individually and when both channels end together. Conditions for Channels Ending Individually: When either of the following conditions is met, the transfer will end in the relevant channel only: The DMA transfer count register (TCR) value becomes 0. The DMA enable bit (DE) of the DMA channel control register (CHCR) is cleared to 0. * Transfer end when TCR = 0 When the TCR value becomes 0, the DMA transfer for that channel ends and the transfer-end flag bit (TE) is set in CHCR. If the IE (interrupt enable) bit has already been set, a DMAC interrupt (DEI) request is sent to the CPU. For 16-byte transfer, set the number of transfers x 4. Operation is not guaranteed if an incorrect value is set. A 16-byte transfer is valid only in auto-request mode or in external request mode with edge detection. When using an external request with level detection or on-chip peripheral module request, do not specify a 16-byte transfer. * Transfer end when DE = 0 in CHCR When the DMA enable bit (DE) in CHCR is cleared, DMA transfers in the affected channel are halted. The TE bit is not set when this happens. Conditions for Both Channels Ending Simultaneously: Transfers on both channels end when either of the following conditions is met: The NMIF (NMI flag) bit or AE (address error flag) bit in DMAOR is set to 1. The DMA master enable (DME) bit is cleared to 0 in DMAOR. * Transfer end when NMIF = 1 or AE = 1 in DMAOR When an NMI interrupt or DMAC address error occurs and the NMIF or AE bit is set to 1 in DMAOR, all channels stop their transfers. The DMA source address register (SAR), destination address register (DAR), and transfer count register (TCR) are all updated by the transfer immediately preceding the halt. When this transfer is the final transfer, TE = 1 and the transfer ends. To resume transfer after NMI interrupt exception handling or address error exception handling, clear the appropriate flag bit. When the DE bit is then set to 1, the transfer on that channel will restart. To avoid this, keep its DE bit at 0. In dual address mode, DMA transfer will be halted after the completion of the following write cycle even when the address error occurs in the initial read cycle. SAR, DAR and TCR are updated by the final transfer.
Rev. 2.00 Mar 09, 2006 page 513 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
* Transfer end when DME = 0 in DMAOR Clearing the DME bit in DMAOR forcibly aborts the transfers on both channels at the end of the current bus cycle. When the transfer is the final transfer, TE = 1 and the transfer ends. 11.3.9 BH Pin Output Timing
Purpose of New Specifications for BH When the SH7616 is connected to the PCI bus as an BH: external bus, Grew logic must be used externally because the SH7616 is not equipped with a PCI bus interface. The PCI bus uses burst transfer principally, and performance is poor if data is transferred in small increments. Due to these properties of the PCI bus, it is necessary to use Grew logic externally to compare the present address and the next address and determine whether burst transfer is possible. However, the size of the external Grew logic increases if address comparisons are required, and there is also the possibility that delays may interfere with timing requirements. The specifications for BH have therefore been updated in order to solve these problems. Now if burst transfer is possible using the present address this information is passed to the external Grew logic. This provides enhanced support for PCI bus connections. Register Settings When Using BH Pin: BH is output from only when the 16-byte transfer mode is selected using the DMAC built into the SH7616. However, it is not output when SDRAM or DRAM are accessed. When using the 16-byte transfer mode, specify auto-request mode or the external request mode with edge detection. If external request mode with level detection or onchip module request mode is specified, operation is not guaranteed. To use BH, the settings for the CHCR0 register or CHCR1 register in the on-chip DMAC of the SH7616 must be as shown in figure 11.43. BH is not output unless the settings for the CHCR0 register or CHCR1 register are as indicated in figure 11.42.
Rev. 2.00 Mar 09, 2006 page 514 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
Bit 31 Bit name -- Setting 0 Bit 15 Bit name DM1 Setting 0 30 -- 0 14 DM0 1 29 28 27 26 25 -- -- -- -- -- 0 0 0 0 0 13 12 11 10 9 SM1 SM0 TS1 TS0 AR 0 1 1 1 * 24 -- 0 8 AM * 23 -- 0 7 AL * 22 -- 0 6 DS * 21 -- 0 5 DL * 20 -- 0 4 TB * 19 -- 0 3 TA * 18 -- 0 2 IE * 17 -- 0 1 TE * 16 -- 0 0 DE 1
16-byte unit (four long words transferred) Source address is incremented Destination address is incremented
DMA transfer allowed * Don't care
Figure 11.42 Register Settings When Using BH Summary of BH Timing: Figure 11.43 is a summary of the BH output timing.
External bus cycle BH
CPU
DMAC read 0
DMAC read 1
DMAC read 2
DMAC read 3
DMAC write 0
DMAC write 1
DMAC write 2
DMAC write 3
CPU
Figure 11.43 Summary of BH Output Timing
Rev. 2.00 Mar 09, 2006 page 515 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
11.4
11.4.1
Usage Examples
Example of DMA Data Transfer Between SCIF and External Memory
In this example data received by the serial communication interface with FIFO (SCIF) is sent to external memory using DMAC channel 1. Table 11.10 lists the transfer conditions and register setting values. Table 11.10 Transfer Conditions and Register Setting Values for Data Transfer Between On-chip SCIF and External Memory
Transfer Condition Transfer source: SCFRDR1 in SCIF Transfer destination: External memory (word space) Number of transfers: 64 Transfer destination address: Increment Transfer source address: Fixed Bus mode: Cycle-steal Transfer unit: Byte DEI interrupt request at end of transfer DE = 1 Channel priority: Fixed (0 > 1) DME = 1 DMAOR H'0001 H'05 Transfer request source (transfer request signal): SCIF DRCR1 (RXI) Register SAR1 DAR1 TCR1 CHCR1 Setting Value H'FFFFFCCC Transfer destination address H'0040 H'4045
Note: Make sure the SCIF settings have interrupts enabled and the appropriate CPU interrupt level.
11.5
Usage Notes
1. DMA request/response selection control registers 0 and 1 (DRCR0 and DRCR1) should be accessed in bytes. All other registers should be accessed in longword units. 2. Before rewriting the registers in the DMAC (CHCR0, CHCR1, DRCR0, DRCR1), first clear the DE bit to 0 in the CHCR register for the specified channel, or clear the DME bit in DMAOR to 0. 3. When the DMAC is not operating, the NMIF bit in DMAOR is set even when an NMI interrupt is input. 4. The DMAC cannot access the cache memory.
Rev. 2.00 Mar 09, 2006 page 516 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
5. Before changing the frequency or changing to standby mode, set the DME bit of DMAOR to 0 and stop operation of the DMAC. 6. Do not use the DMAC, BSC, UBC, E-DMAC, and EtherC for on-chip peripheral module transfers. 7. Do not access the cache (address array, data array, associative purge area). 8. Note that when level detection of the request signal is used in single address mode, the request signal may be detected before DACKn is output. 9. When E exceeds 31.25 MHz, do not use transfer involving DACKn output on ordinary space for word or longword access with an 8-bit bus width, or longword access with a 16-bit bus width. 10. When DMA transfer is performed in response to a DMA transfer request signal from a peripheral module, if clearing of the DMA transfer request signal from the peripheral module by the DMA transfer is not completed before the next transfer request signal from that module, subsequent DMA transfers may not be possible. 11. The following restrictions apply when using dual address mode for 16-byte transfer in cyclesteal mode: a. When external request and level detection are set, do not input DREQn during cycles in which DACKn is not active after the start of DMA transfer. b. When external request DREQ edge detection is set, if DREQn is input continuously the DMAC continues to operate without insertion of a CPU cycle. (However, a CPU cycle will begin if there is no request from DREQn.)
Bus cycle DACKn (active high) DREQn (active high) CPU CPU DMA DMA DMA DMA DMA DMA DMA DMA CPU DMA DMA DMA DMA DMA DMA DMA DMA CPU (R) (R) (R) (R) (W) (W) (W) (W) (R) (R) (R) (R) (W) (W) (W) (W)
* DACK output in read cycle
Bus cycle DACKn (active high) DREQn (active high)
CPU CPU DMA DMA DMA DMA DMA DMA DMA DMA CPU DMA DMA DMA DMA DMA DMA DMA DMA CPU (R) (R) (R) (R) (W) (W) (W) (W) (R) (R) (R) (R) (W) (W) (W) (W)
*
DACK output in write cycle Note: * In addition to CPU cycles, E-DMAC cycles may be inserted in some cases.
Rev. 2.00 Mar 09, 2006 page 517 of 906 REJ09B0292-0200
Section 11 Direct Memory Access Controller (DMAC)
12. When setting DMAC channel 0 to cycle-steal mode, and channel 1 to cycle-steel mode, dual address mode or built-in peripheral module request, set the priority mode to priority order fixed mode. 13. When SDRAM is connected, set the upper limit of external bus frequency in DMA single address mode transfers to 31.25 MHz. 14. In the dual address mode, bits TS1 and TS0 (transfer size) in CHCR0 and CHCR1 should be cleared to 00 (byte unit setting) if a destination address as been set in internal memory.
Rev. 2.00 Mar 09, 2006 page 518 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
Section 12 16-Bit Free-Running Timer (FRT)
12.1 Overview
A single-channel, 16-bit free-running timer (FRT) is included on-chip. The FRT is based on a 16-bit free-running counter (FRC) and can output two types of independent waveforms. The FRT can also measure the width of input pulses and the cycle of external clocks. 12.1.1 Features
The FRT has the following features: * Choice of four counter input clocks The counter input clock can be selected from three internal clocks (P/8, P/32, P/128) and an external clock (enabling external event counting). * Two independent comparators Two waveform outputs can be generated. * Input capture Choice of rising edge or falling edge * Counter clear specification The counter value can be cleared by compare match A. * Four interrupt sources Two compare match sources, one input capture source, and one overflow source can issue requests independently.
Rev. 2.00 Mar 09, 2006 page 519 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.1.2
Block Diagram
Figure 12.1 shows a block diagram of the FRT.
Internal clock /8 /32 /128 Clock select Clock Compare match A FTOA FTOB FRC (H/L) Clear FTI Compare match B Comparator B
Bus interface
FTCI
OCRA (H/L)
Comparator A
Overflow
Internal data bus
Control logic
OCRB (H/L) Capture
FICR (H/L) FTCSR TIER TCR TOCR Module data bus
ICI OCIA OCIB OVI OCRA,B: FRC: FICR: FTCSR: TIER: TCR: TOCR:
Interrupt signals
Output compare registers A,B (16 bits) Free-running counter (16 bits) Input capture register (16 bits) Free-running timer control/status register (8 bits) Timer interrupt enable register (8 bits) Timer control register (8 bits) Timer output compare control register (8 bits)
Figure 12.1 FRT Block Diagram
Rev. 2.00 Mar 09, 2006 page 520 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.1.3
Pin Configuration
Table 12.1 lists FRT I/O pins and their functions. Table 12.1 Pin Configuration
Channel Counter clock input pin Output compare A output pin Output compare B output pin Input capture input pin Pin FTCI FTOA FTOB FTI I/O I O O I Function FRC counter clock input pin Output pin for output compare A Output pin for output compare B Input pin for input capture
12.1.4
Register Configuration
Table 12.2 shows the FRT register configuration. Table 12.2 Register Configuration
Register Timer interrupt enable register Free-running counter H Free-running counter L Output compare register A H Output compare register A L Output compare register B H Output compare register B L Timer control register Timer output compare control register Input capture register H Input capture register L Abbreviation TIER FRC H FRC L OCRA H OCRA L OCRB H OCRB L TCR TOCR FICR H FICR L R/W R/W R/(W) R/W R/W R/W R/W R/W R/W R/W R/W R R *1 Initial Value H'01 H'00 H'00 H'00 H'FF H'FF H'FF H'FF H'00 H'E0 H'00 H'00 Address HFFFFFE10 HFFFFFE11 HFFFFFE12 HFFFFFE13 HFFFFFE14* 2 HFFFFFE15*
2
Free-running timer control/status register FTCSR
HFFFFFE14* 2 HFFFFFE15*
2
HFFFFFE16 HFFFFFE17 HFFFFFE18 HFFFFFE19
Notes: Use byte-size access for all registers. 1. Bits 7 to 1 are read-only. The only value that can be written is a 0, which is used to clear flags. Bit 0 can be read or written. 2. OCRA and OCRB have the same address. The OCRS bit in TOCR is used to switch between them.
Rev. 2.00 Mar 09, 2006 page 521 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.2
12.2.1
Register Descriptions
Free-Running Counter (FRC)
Bit: Initial value: R/W: 15 0 R/W 14 0 R/W 13 0 R/W ... ... ... ... 0 R/W 0 R/W 0 R/W 0 R/W 3 2 1 0
FRC is a 16-bit read/write register. It increments upon input of a clock. The input clock can be selected using clock select bits 1 and 0 (CKS1, CKS0) in TCR. FRC can be cleared upon compare match A. When FRC overflows (H'FFFF H'0000), the overflow flag (OVF) in FTCSR is set to 1. FRC can be read or written to by the CPU, but because it is 16 bits long, data transfers involving the CPU are performed via a temporary register (TEMP). See section 12.3, CPU Interface, for more detailed information. FRC is initialized to H'0000 by a reset, in standby mode, and when the module standby function is used. 12.2.2 Output Compare Registers A and B (OCRA and OCRB)
Bit: Initial value: R/W: 15 1 R/W 14 1 R/W 13 1 R/W ... ... ... ... 1 R/W 1 R/W 1 R/W 1 R/W 3 2 1 0
OCR is composed of two 16-bit read/write registers (OCRA and OCRB). The contents of OCR are always compared to the FRC value. When the two values are the same, the output compare flags in FTCSR (OCFA and OCFB) are set to 1. When the OCR and FRC values are the same (compare match), the output level values set in the output level bits (OLVLA and OLVLB) are output to the output compare pins (FTOA and FTOB). After a reset, FTOA and FTOB output 0 until the first compare match occurs. Because OCR is a 16-bit register, data transfers involving the CPU are performed via a temporary register (TEMP). See section 12.3, CPU Interface, for more detailed information.
Rev. 2.00 Mar 09, 2006 page 522 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
OCR is initialized to H'FFFF by a reset, in standby mode, and when the module standby function is used. 12.2.3 Input Capture Register (FICR)
Bit: Initial value: R/W: 15 0 R 14 0 R 13 0 R ... ... ... ... 0 R 0 R 0 R 0 R 3 2 1 0
FICR is a 16-bit read-only register. When a rising edge or falling edge of the input capture signal (FTI pin) is detected, the current FRC value is transferred to FICR. At the same time, the input capture flag (ICF) in FTCSR is set to 1. The edge of the input signal can be selected using the input edge select bit (IEDG) in TCR. Because FICR is a 16-bit register, data transfers involving the CPU are performed via a temporary register (TEMP). See Section 12.3, CPU Interface, for more detailed information. To ensure that the input capture operation is reliably performed, set the pulse width of the input capture input signal to six system clocks () or more. FICR is initialized to H'0000 by a reset, in standby mode, and when the module standby function is used. 12.2.4 Timer Interrupt Enable Register (TIER)
Bit: Initial value: R/W: 7 ICIE 0 R/W 6 -- 0 R 5 -- 0 R 4 -- 0 R 3 OCIAE 0 R/W 2 OCIBE 0 R/W 1 OVIE 0 R/W 0 -- 1 R
TIER is an 8-bit read/write register that controls enabling of all interrupt requests. TIER is initialized to H'01 by a reset, in standby mode, and when the module standby function is used. Bit 7--Input Capture Interrupt Enable (ICIE): Selects enabling/disabling of the ICI interrupt request when the input capture flag (ICF) in FTCSR is set to 1.
Bit 7: ICIE 0 1 Description Interrupt request (ICI) caused by ICF disabled Interrupt request (ICI) caused by ICF enabled Rev. 2.00 Mar 09, 2006 page 523 of 906 REJ09B0292-0200 (Initial value)
Section 12 16-Bit Free-Running Timer (FRT)
Bits 6 to 4--Reserved: These bits are always read as 0. The write value should always be 0. Bit 3--Output Compare Interrupt A Enable (OCIAE): Selects enabling/disabling of the OCIA interrupt request when the output compare flag A (OCFA) in FTCSR is set to 1.
Bit 3: OCIAE 0 1 Description Interrupt request (OCIA) caused by OCFA disabled Interrupt request (OCIA) caused by OCFA enabled (Initial value)
Bit 2--Output Compare Interrupt B Enable (OCIBE): Selects enabling/disabling of the OCIB interrupt request when the output compare flag B (OCFB) in FTCSR is set to 1.
Bit 2: OCIBE 0 1 Description Interrupt request (OCIB) caused by OCFB disabled Interrupt request (OCIB) caused by OCFB enabled (Initial value)
Bit 1--Timer Overflow Interrupt Enable (OVIE): Selects enabling/disabling of the OVI interrupt request when the overflow flag (OVF) in FTCSR is set to 1.
Bit 1: OVIE 0 1 Description Interrupt request (OVI) caused by OVF disabled Interrupt request (OVI) caused by OVF enabled (initial value)
Bit 0--Reserved: This bit is always read as 1. The write value should always be 1. 12.2.5 Free-Running Timer Control/Status Register (FTCSR)
Bit: Initial value: R/W: 7 ICF 0 R/(W)* 6 -- 0 R 5 -- 0 R 4 -- 0 R 3 OCFA 0 R/(W)* 2 OCFB 0 R/(W)* 1 OVF 0 R/(W)* 0 CCLRA 0 R/W
Note: * For bits 7, and 3 to 1, the only value that can be written is 0 (to clear the flags).
FTCSR is an 8-bit register that selects counter clearing and controls interrupt request signals. FTCSR is initialized to H'00 by a reset, in standby mode, and when the module standby function is used. See section 12.4, Operation, for the timing.
Rev. 2.00 Mar 09, 2006 page 524 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
Bit 7--Input Capture Flag (ICF): Status flag that indicates that the FRC value has been sent to FICR by the input capture signal. This flag is cleared by software and set by hardware. It cannot be set by software.
Bit 7: ICF 0 Description [Clearing condition] When ICF is read while set to 1, and then 0 is written to it (Initial value) 1 [Setting condition] When the FRC value is sent to FICR by the input capture signal
Bits 6 to 4--Reserved: These bits always read 0. The write value should always be 0. Bit 3--Output Compare Flag A (OCFA): Status flag that indicates when the values of the FRC and OCRA match. This flag is cleared by software and set by hardware. It cannot be set by software.
Bit 3: OCFA 0 Description [Clearing condition] When OCFA is read while set to 1, and then 0 is written to it (Initial value) 1 [Setting condition] When the FRC value becomes equal to OCRA
Bit 2--Output Compare Flag B (OCFB): Status flag that indicates when the values of FRC and OCRB match. This flag is cleared by software and set by hardware. It cannot be set by software.
Bit 2: OCFB 0 Description [Clearing condition] When OCFB is read while set to 1, and then 0 is written to it (Initial value) 1 [Setting condition] When the FRC value becomes equal to OCRB
Rev. 2.00 Mar 09, 2006 page 525 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
Bit 1--Timer Overflow Flag (OVF): Status flag that indicates when FRC overflows (from H'FFFF to H'0000). This flag is cleared by software and set by hardware. It cannot be set by software.
Bit 1: OVF 0 Description [Clearing condition] When OVF is read while set to 1, and then 0 is written to it (Initial value) 1 [Setting condition] When the FRC value changes from H'FFFF to H'0000
Bit 0--Counter Clear A (CCLRA): Selects whether or not to clear FRC on compare match A (signal indicating match of FRC and OCRA).
Bit 0: CCLRA 0 1 Description FRC clear disabled FRC cleared on compare match A (Initial value)
12.2.6
Timer Control Register (TCR)
Bit: Initial value: R/W: 7 IEDG 0 R/W 6 -- 0 R 5 -- 0 R 4 -- 0 R 3 -- 0 R 2 -- 0 R 1 CKS1 0 R/W 0 CKS0 0 R/W
TCR is an 8-bit read/write register that selects the input edge for input capture and selects the input clock for FRC. TCR is initialized to H'00 by a reset, in standby mode, and when the module standby function is used. Bit 7--Input Edge Select (IEDG): Selects whether to capture the input capture input (FTI) on the falling edge or rising edge.
Bit 7: IEDG 0 1 Description Input captured on falling edge Input captured on rising edge (Initial value)
Bits 6 to 2--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 526 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
Bits 1 and 0--Clock Select (CKS1, CKS0): These bits select whether to use an external clock or one of three internal clocks for input to FRC. The external clock is counted at the rising edge.
Bit 1: CKS1 0 1 Bit 0: CKS0 0 1 0 1 Description Internal clock: count at /8 Internal clock: count at /32 Internal clock: count at /128 External clock: count at rising edge (Initial value)
12.2.7
Timer Output Compare Control Register (TOCR)
Bit: Initial value: R/W: 7 -- 1 R 6 -- 1 R 5 -- 1 R 4 OCRS 0 R/W 3 -- 0 R 2 -- 0 R 1 OLVLA 0 R/W 0 OLVLB 0 R/W
TOCR is an 8-bit read/write register that selects the output level for output compare and controls switching between access of output compare registers A and B. TOCR is initialized to H'E0 by a reset, in standby mode, and when the module standby function is used. Bits 7 to 5--Reserved: These bits are always read as 1. The write value should always be 1. Bit 4--Output Compare Register Select (OCRS): OCRA and OCRB share the same address. The OCRS bit controls which register is selected when reading/writing to this address. It does not affect the operation of OCRA and OCRB.
Bit 4: OCRS 0 1 Description OCRA register selected OCRB register selected (Initial value)
Bits 3 and 2--Reserved: These bits are always read as 0. The write value should always be 0. Bit 1--Output Level A (OLVLA): Selects the level output to the output compare A output pin upon compare match A (signal indicating match of FRC and OCRA).
Bit 1: OLVLA 0 1 Description 0 output on compare match A 1 output on compare match A Rev. 2.00 Mar 09, 2006 page 527 of 906 REJ09B0292-0200 (Initial value)
Section 12 16-Bit Free-Running Timer (FRT)
Bit 0--Output Level B (OLVLB): Selects the level output to the output compare B output pin upon compare match B (signal indicating match of FRC and OCRB).
Bit 0: OLVLB 0 1 Description 0 output on compare match B 1 output on compare match B (Initial value)
12.3
CPU Interface
FRC, OCRA, OCRB, and FICR are 16-bit registers. The data bus width between the CPU and FRT, however, is only 8 bits. Access of these three types of registers from the CPU therefore needs to be performed via an 8-bit temporary register called TEMP. The following describes how these registers are read from and written to: * Writing to 16-bit Registers The upper byte is written, which results in the upper byte of data being stored in TEMP. The lower byte is then written, which results in 16 bits of data being written to the register when combined with the upper byte value in TEMP. * Reading from 16-bit Registers The upper byte of data is read, which results in the upper byte value being transferred to the CPU. The lower byte value is transferred to TEMP. The lower byte is then read, which results in the lower byte value in TEMP being sent to the CPU. When registers of these three types are accessed, two byte accesses should always be performed, first to the upper byte, then the lower byte. If only the upper byte or lower byte is accessed, the data will not be transferred properly. Figure 12.2 and 12.3 show the flow of data when FRC is accessed. Other registers function in the same way. When reading OCRA and OCRB, however, both upper and lower-byte data is transferred directly to the CPU without passing through TEMP.
Rev. 2.00 Mar 09, 2006 page 528 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
(Write to upper byte)
CPU (H'AA) upper byte
Data bus within module Bus interface
TEMP (H'AA)
FRC H ( ) (Write to lower byte) CPU (H'55) lower byte
FRC L ( )
Data bus within module Bus interface
TEMP (H'AA)
FRC H (H'AA)
FRC L (H'55)
Figure 12.2 FRC Access Operation (CPU Writes H'AA55 to FRC)
Rev. 2.00 Mar 09, 2006 page 529 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
(Read from upper byte)
CPU (H'AA) upper byte
Data bus within module Bus interface
TEMP (H'55)
FRC H (H'AA) (Read from lower byte)
FRC L (H'55)
CPU (H'55) lower byte
Data bus within module Bus interface
TEMP (H'AA)
FRC H ( )
FRC L ( )
Figure 12.3 FRC Access Operation (CPU Reads H'AA55 from FRC)
Rev. 2.00 Mar 09, 2006 page 530 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.4
12.4.1
Operation
FRC Count Timing
The FRC increments on clock input (internal or external). Internal Clock Operation: Set the CKS1 and CKS0 bits in TCR to select which of the three internal clocks created by dividing system clock (/8, /32, /128) is used. Figure 12.4 shows the timing.
P Internal clock FRC input clock FRC N-1 N N+1
Figure 12.4 Count Timing (Internal Clock Operation) External Clock Operation: Set the CKS1 and CKS0 bits in TCR to select the external clock. External clock pulses are counted on the rising edge. The pulse width of the external clock must be at least 6 system clocks (). A smaller pulse width will result in inaccurate operation. Figures 12.5 shows the timing.
P
External clock input pin FRC input clock FRC
N
N+1
Figure 12.5 Count Timing (External Clock Operation)
Rev. 2.00 Mar 09, 2006 page 531 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.4.2
Output Timing for Output Compare
When a compare match occurs, the output level set in the OLVL bit in TOCR is output from the output compare output pins (FTOA, FTOB). Figure 12.6 shows the timing for output of output compare A.
P FRC N N N+1 N N N+1
OCRA Compare match A signal OLVLA Output compare A output pin FTOA
Clear*
Note: * Indicates instruction execution by software
Figure 12.6 Output Timing for Output Compare A 12.4.3 FRC Clear Timing
FRC can be cleared on compare match A. Figure 12.7 shows the timing.
P Compare match A signal FRC N H'0000
Figure 12.7 Compare Match A Clear Timing
Rev. 2.00 Mar 09, 2006 page 532 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.4.4
Input Capture Input Timing
Either the rising edge or falling edge can be selected for input capture input using the IEDG bit in TCR. Figure 12.8 shows the timing when the rising edge is selected (IEDG = 1).
P
Input capture input pin Input capture signal
Figure 12.8 Input Capture Signal Timing (Normal) When the input capture signal is input when FICR is read (upper-byte read), the input capture signal is delayed by one cycle of P. Figure 12.9 shows the timing.
FICR upper-byte read cycle P
Input capture input pin Input capture signal
Figure 12.9 Input Capture Signal Timing (Input Capture Input when FICR is Read)
Rev. 2.00 Mar 09, 2006 page 533 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.4.5
Input Capture Flag (ICF) Setting Timing
Input capture input sets the input capture flag (ICF) to 1 and simultaneously transfers the FRC value to FICR. Figure 12.10 shows the timing.
P
Input capture signal
ICF
FRC
N
FICR
N
Figure 12.10 ICF Setting Timing 12.4.6 Output Compare Flag (OCFA, OCFB) Setting Timing
The compare match signal output (when OCRA or OCRB matches the FRC value) sets output compare flag OCFA or OCFB to 1. The compare match signal is generated in the last state in which the values matched (at the timing for updating the count value that matched the FRC). After OCRA or OCRB matches the FRC, no compare match is generated until the next increment occurs. Figure 12.11 shows the timing for setting OCFA and OCFB.
Rev. 2.00 Mar 09, 2006 page 534 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
P
FRC
N
N+1
OCRA, OCRB
N
Compare match signal
OCFA, OCFB
Figure 12.11 OCF Setting Timing 12.4.7 Timer Overflow Flag (OVF) Setting Timing
FRC overflow (from H'FFFF to H'0000) sets the timer overflow flag (OVF) to 1. Figure 12.12 shows the timing.
P
FRC
H'FFFF
H'0000
Overflow signal
OVF
Figure 12.12 OVF Setting Timing
Rev. 2.00 Mar 09, 2006 page 535 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.5
Interrupt Sources
There are four FRT interrupt sources of three types (ICI, OCIA/OCIB, and OVI). Table 12.3 lists the interrupt sources and their priorities after a reset is cleared. The interrupt enable bits in TIER are used to enable or disable the interrupt bits. Each interrupt request is sent to the interrupt controller independently. See section 5, Interrupt Controller (INTC), for more information about priorities and the relationship to interrupts other than those of the FRT. Table 12.3 FRT Interrupt Sources and Priorities
Interrupt Source ICI OCIA, OCIB OVI Description Interrupt by ICF Interrupt by OCFA or OCFB Interrupt by OVF Priority High Low
12.6
Example of FRT Use
Figure 12.13 shows an example in which pulses with a 50% duty factor and arbitrary phase relationship are output. The procedure is as follows: 1. Set the CCLRA bit in FTCSR to 1. 2. The OLVLA and OLVLB bits are inverted by software whenever a compare match occurs.
FRC H'FFFF OCRA OCRB H'0000 Counter clear
FTOA
FTOB
Figure 12.13 Example of Pulse Output
Rev. 2.00 Mar 09, 2006 page 536 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.7
Usage Notes
Note that the following contention and operations occur when the FRT is operating: 12.7.1 Contention between FRC Write and Clear
When a counter clear signal is generated with the timing shown in figure 12.14 during the write cycle for the lower byte of FRC, writing does not occur to the FRC, and the FRC clear takes priority.
FRC lower-byte write cycle P
Address Internal write signal Counter clear signal
FRC address
FRC
N
H'0000
Figure 12.14 Contention between FRC Write and Clear
Rev. 2.00 Mar 09, 2006 page 537 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.7.2
Contention between FRC Write and Increment
When an increment occurs with the timing shown in figure 12.15 during the write cycle for the lower byte of FRC, no increment is performed and the counter write takes priority.
FRC lower-byte write cycle P
Address
FRC address
Internal write signal FRC input clock
FRC
N Write data
M
Figure 12.15 Contention between FRC Write and Increment
Rev. 2.00 Mar 09, 2006 page 538 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.7.3
Contention between OCR Write and Compare Match
When a compare match occurs with the timing shown in figure 12.16, during the write cycle for the lower byte of OCRA or OCRB, the OCR write takes priority and the compare match signal is disabled.
FRC lower-byte write cycle P
Address
OCR address
Internal write signal
FRC
N
N+1
OCR
N Write data
M
Compare match signal Disabled
Figure 12.16 Contention between OCR and Compare Match
Rev. 2.00 Mar 09, 2006 page 539 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
12.7.4
Internal Clock Switching and Counter Operation
FRC will sometimes begin incrementing because of the timing of switching between internal clocks. Table 12.4 shows the relationship between internal clock switching timing (CKS1 and CKS0 bit rewrites) and FRC operation. When an internal clock is used, the FRC clock is generated when the falling edge of an internal clock (created by dividing the system clock ()) is detected. When a clock is switched to high before the switching and to low after switching, as shown in case 3 in table 12.4, the switchover is considered a falling edge and an FRC clock pulse is generated, causing FRC to increment. FRC may also increment when switching between an internal clock and an external clock. Table 12.4 Internal Clock Switching and FRC Operation
No. 1 Timing of Rewrite of CKS1 and CKS0 Bits Low-to-low switch
Clock before switching
FRC Operation
Clock after switching
FRC clock
FRC
N Rewrite of CKS bit
N+1
2
Low-to-high switch
Clock before switching
Clock after switching
FRC clock
FRC
N
N+1
N+2
Rewrite of CKS bit
Rev. 2.00 Mar 09, 2006 page 540 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT) Timing of Rewrite of CKS1 and CKS0 Bits High-to-low switch
Clock before switching
No. 3
FRC Operation
Clock after switching
FRC clock
FRC
N
N+1 Rewrite of CKS bit
N+2
4
High-to-high switch
Clock before switching
Clock after switching
FRC clock
FRC
N
N+1
N+2 Rewrite of CKS bit
Note: Because the switchover is considered a falling edge, FRC starts counting up.
12.7.5
Timer Output (FTOA, FTOB)
During a power-on reset, the timer outputs (FTOA, FTOB) will be unreliable until the oscillation stabilizes. The initial value is output after the oscillation settling time has elapsed.
Rev. 2.00 Mar 09, 2006 page 541 of 906 REJ09B0292-0200
Section 12 16-Bit Free-Running Timer (FRT)
Rev. 2.00 Mar 09, 2006 page 542 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
Section 13 Watchdog Timer (WDT)
13.1 Overview
A single-channel watchdog timer (WDT) is provided on-chip for monitoring system operations. If a system becomes uncontrolled and the timer counter overflows without being rewritten correctly by the CPU, an overflow signal (WDTOVF) is output externally. The WDT can simultaneously generate an internal reset signal for the entire chip. When this watchdog function is not needed, the WDT can be used as an interval timer. In the interval timer operation, an interval timer interrupt is generated at each counter overflow. The WDT is also used when recovering from standby mode, in modifying a clock frequency, and in clock pause mode. 13.1.1 Features
The WDT includes the following features. * Can be switched between watchdog timer mode and interval timer mode. * WDTOVF output in watchdog timer mode The WDTOVF signal is output externally when the counter overflows, and a simultaneous internal reset of the chip can also be selected (either a power-on reset or manual reset can be specified). * Interrupt generation in interval timer mode An interval timer interrupt is generated when the counter overflows. * Used when standby mode is cleared or the clock frequency is changed, and in clock pause mode. * Choice of eight counter input clocks
Rev. 2.00 Mar 09, 2006 page 543 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.1.2
Block Diagram
Figure 13.1 shows a block diagram of the WDT.
ITI (Interrupt request signal)
Overflow Interrupt control Clock Clock select
WDTOVF Internal reset signal*
Reset control
/4 /128 /256 /512 /1024 /2048 /8192 /16384 Internal clock
RSTCSR
WTCNT
WTCSR
Module bus WDT : See figure 3.1, Block Diagram of Clock Pulse Generator Circuit. WTCSR: Watchdog timer control/status register WTCNT: Watchdog timer counter RSTCSR: Reset control/status register
Bus interface
Note: * The internal reset signal can be generated by a register setting. The type of reset can be selected (power-on or manual reset).
Figure 13.1 WDT Block Diagram 13.1.3 Pin Configuration
Table 13.1 shows the pin configuration. Table 13.1 Pin Configuration
Pin Watchdog timer overflow Abbreviation WDTOVF I/O O Function Outputs the counter overflow signal in watchdog timer mode
Rev. 2.00 Mar 09, 2006 page 544 of 906 REJ09B0292-0200
Interna bus
Section 13 Watchdog Timer (WDT)
13.1.4
Register Configuration
Table 13.2 summarizes the three WDT registers. They are used to select the clock, switch the WDT mode, and control the reset signal. Table 13.2 Register Configuration
Address Name Abbreviation R/W R/(W)* R/W R/(W)*
3 3 1 Write*
Initial Value H'18 H'00 H'1D
Read*
2
Watchdog timer WTCSR control/status register Watchdog timer counter Reset control/status register WTCNT RSTCSR
H'FFFFFE80 H'FFFFFE80 H'FFFFFE82
H'FFFFFE80 H'FFFFFE81 H'FFFFFE83
Notes: 1. Write by word access. It cannot be written by byte or longword access. 2. Read by byte access. The correct value cannot be read by word or longword access. 3. Only 0 can be written in bit 7 to clear the flag.
13.2
13.2.1
Register Descriptions
Watchdog Timer Counter (WTCNT)
Bit: Initial value: R/W: 7 0 R/W 6 0 R/W 5 0 R/W 4 0 R/W 3 0 R/W 2 0 R/W 1 0 R/W 0 0 R/W
WTCNT is an 8-bit read/write register. The method of writing to WTCNT differs from that of most other registers to prevent inadvertent rewriting. See section 13.2.4, Notes on Register Access, for details. When the timer enable bit (TME) in the watchdog timer control/status register (WTCSR) is set to 1, the watchdog timer counter starts counting pulses of an internal clock source selected by clock select bits 2 to 0 (CKS2 to CKS0) in WTCSR. When the value of WTCNT overflows (changes from H'FF to H'00), a watchdog timer overflow signal (WDTOVF) or interval timer interrupt (ITI) is generated, depending on the mode selected in the WT/IT bit in WTCSR. WTCNT is initialized to H'00 by a reset and when the TME bit is cleared to 0. It is not initialized in standby mode, when the clock frequency is changed, or in clock pause mode.
Rev. 2.00 Mar 09, 2006 page 545 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.2.2
Watchdog Timer Control/Status Register (WTCSR)
Bit: Initial value: R/W: 7 OVF 0 R/(W)* 6 WT/IT 0 R/W 5 TME 0 R/W 4 -- 1 R 3 -- 1 R 2 CKS2 0 R/W 1 CKS1 0 R/W 0 CKS0 0 R/W
Note: * Only 0 can be written in bit 7, to clear the flag.
The watchdog timer control/status register (WTCSR) is an 8-bit read/write register. The method of writing to WTCSR differs from that of most other registers to prevent inadvertent rewriting. See section 13.2.4, Notes on Register Access, for details. Its functions include selecting the timer mode and clock source. Bits 7 to 5 are initialized to 000 by a reset, in standby mode, when the clock frequency is changed, and in clock pause mode. Bits 2 to 0 are initialized to 000 by a reset, but are not initialized in standby mode, when the clock frequency is changed, or in clock pause mode. Bit 7--Overflow Flag (OVF): Indicates that WTCNT has overflowed from H'FF to H'00 in interval timer mode. It is not set in watchdog timer mode.
Bit 7: OVF 0 1 Description No overflow of WTCNT in interval timer mode Cleared by reading OVF, then writing 0 in OVF WTCNT overflow in interval timer mode (Initial value)
Bit 6--Timer Mode Select (WT/IT): Selects whether to use the WDT as a watchdog timer or interval timer. When WTCNT overflows, the WDT either generates an interval timer interrupt (ITI) or generates a WDTOVF signal, depending on the mode selected.
Bit 6: WT/IT IT 0 1 Description Interval timer mode: interval timer interrupt (ITI) request to the CPU when WTCNT overflows (Initial value) Watchdog timer mode: WDTOVF signal output externally when WTCNT overflows. Section 13.2.3, Reset Control/Status Register (RSTCSR), describes in detail what happens when WTCNT overflows in watchdog timer mode
Rev. 2.00 Mar 09, 2006 page 546 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
Bit 5--Timer Enable (TME): Enables or disables the timer.
Bit 5: TME 0 1 Description Timer disabled: WTCNT is initialized to H'00 and count-up stops (Initial value) Timer enabled: WTCNT starts counting. A WDTOVF signal or interrupt is generated when WTCNT overflows
Bits 4 and 3--Reserved: These bits are always read as 1. The write value should always be 1. Bits 2 to 0--Clock Select 2 to 0 (CKS2 to CKS0): These bits select one of eight internal clock sources for input to WTCNT. The clock signals are obtained by dividing the frequency of the system clock ().
Description Bit 2: CKS2 Bit 1: CKS1 Bit 0: CKS0 Clock Source 0 0 1 1 0 1 0 1 0 1 0 1 0 1 /4 (Initial value) /128 /256 /512 /1024 /2048 /8192 /16384 Overflow Interval* ( = 60 MHz) 17.0 s 544 s 1.1 ms 2.2 ms 4.4 ms 8.7 ms 34.8 ms 69.6 ms
Note: * The overflow interval listed is the time from when the WTCNT begins counting at H'00 until an overflow occurs.
13.2.3
Reset Control/Status Register (RSTCSR)
Bit: Initial value: R/W: 7 WOVF 0 R/(W)* 6 RSTE 0 R/W 5 RSTS 0 R/W 4 -- 1 R 3 -- 1 R 2 -- 1 R 1 -- 0 R 0 -- 1 R
Note: * Only 0 can be written in bit 7, to clear the flag.
RSTCSR is an 8-bit read/write register that controls output of the reset signal generated by watchdog timer counter (WTCNT) overflow and selects the internal reset signal type. The method
Rev. 2.00 Mar 09, 2006 page 547 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
of writing to RSTCSR differs from that of most other registers to prevent inadvertent rewriting. See section 13.2.4, Notes on Register Access, for details. RSTCR is initialized to H'1D by input of a reset signal from the RES pin, but is not initialized by the internal reset signal generated by overflow of the WDT. It is initialized to H'1D in standby mode, when the clock frequency is changed, and in clock pause mode. Bit 7--Watchdog Timer Overflow Flag (WOVF): Indicates that WTCNT has overflowed (from H'FF to H'00) in watchdog timer mode. It is not set in interval timer mode.
Bit 7: WOVF 0 1 Description No WTCNT overflow in watchdog timer mode Cleared by reading WOVF, then writing 0 in WOVF Set by WTCNT overflow in watchdog timer mode (Initial value)
Bit 6--Reset Enable (RSTE): Selects whether to reset the chip internally if WTCNT overflows in watchdog timer mode.
Bit 6: RSTE 0 1 Description Not reset when WTCNT overflows Reset when WTCNT overflows (Initial value) LSI not reset internally, but WTCNT and WTCSR reset within WDT
Bit 5--Reset Select (RSTS): Selects the type of internal reset generated if WTCNT overflows in watchdog timer mode.
Bit 5: RSTS 0 1 Description Power-on reset Manual reset (Initial value)
Bits 4 to 2, bit 0--Reserved: These bits are always read as 1. The write value should always be 1. Bit 1-- Reserved: This bit is always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 548 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.2.4
Notes on Register Access
The watchdog timer's WTCNT, WTCSR, and RSTCSR registers differ from other registers in that they are more difficult to write. The procedures for writing and reading these registers are given below. Writing to WTCNT and WTCSR: These registers must be written by a word transfer instruction. They cannot be written by byte or longword transfer instructions. WTCNT and WTCSR both have the same write address. The write data must be contained in the lower byte of the written word. The upper byte must be H'5A (for WTCNT) or H'A5 (for WTCSR) (figure 13.2). This transfers the write data from the lower byte to WTCNT or WTCSR.
Writing to WTCNT 15 Address: Writing to WTCSR 15 Address: H'FFFFFE80 H'A5 87 Write data 0 H'FFFFFE80 H'5A 87 Write data 0
Figure 13.2 Writing to WTCNT and WTCSR Writing to RSTCSR: RSTCSR must be written by a word access to address H'FFFFFE82. It cannot be written by byte or longword transfer instructions. Procedures for writing 0 in WOVF (bit 7) and for writing to RSTE (bit 6) and RSTS (bit 5) are different, as shown in figure 13.3. To write 0 in the WOVF bit, the write data must be H'A5 in the upper byte and H'00 in the lower byte. This clears the WOVF bit to 0. The RSTE and RSTS bits are not affected. To write to the RSTE and RSTS bits, the upper byte must be H'5A and the lower byte must be the write data. The values of bits 6 and 5 of the lower byte are transferred to the RSTE and RSTS bits, respectively. The WOVF bit is not affected.
Rev. 2.00 Mar 09, 2006 page 549 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
Writing 0 to the WOVF bit 15 Address: H'FFFFFE82 H'A5 87 H'00 0
Writing to the RSTE and RSTS bits 15 Address: H'FFFFFE82 H'5A 87 Write data 0
Figure 13.3 Writing to RSTCSR Reading from WTCNT, WTCSR, and RSTCSR: WTCNT, WTCSR, and RSTCSR are read like other registers. Use byte transfer instructions. The read addresses are H'FFFFFE80 for WTCSR, H'FFFFFE81 for WTCNT, and H'FFFFFE83 for RSTCSR.
13.3
13.3.1
Operation
Operation in Watchdog Timer Mode
To use the WDT as a watchdog timer, set the WT/IT and TME bits in WTCSR to 1. Software must prevent WTCNT overflow by rewriting the WTCNT value (normally by writing H'00) before overflow occurs. Thus, WTCNT will not overflow while the system is operating normally, but if WTCNT fails to be rewritten and overflows occur due to a system crash or the like, a WDTOVF signal is output (figure 13.4). The WDTOVF signal can be used to reset the system. The WDTOVF signal is output for 512 clock cycles. If the RSTE bit in RSTCSR is set to 1, a signal to reset the chip will be generated internally simultaneously with the WDTOVF signal when WTCNT overflows. Either a power-on reset or a manual reset can be selected by the RSTS bit. The internal reset signal is output for 2048 clock cycles. If a reset due to the input signal from the RES pin and a reset due to WDT overflow occur simultaneously, the RES reset takes priority and the WOVF bit in RSTCSR is cleared to 0.
Rev. 2.00 Mar 09, 2006 page 550 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
WTCNT value H'FF Overflow
H'00 WT/IT = 1 TME = 1 H'00 written in WTCNT WOVF = 1
Time WT/IT = 1 H'00 written TME = 1 in WTCNT
WDTOVF and internal reset generated
WDTOVF signal 512 clocks Internal reset signal*
2048 clocks
WT/IT: Timer mode select bit TME: Timer enable bit Note: * Internal reset signal is generated only when the RSTE bit is set to 1.
Figure 13.4 Operation in Watchdog Timer Mode
Rev. 2.00 Mar 09, 2006 page 551 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.3.2
Operation in Interval Timer Mode
To use the WDT as an interval timer, clear WT/IT to 0 and set TME to 1 in WTCSR. An interval timer interrupt (ITI) is generated each time the watchdog timer counter (WTCNT) overflows. This function can be used to generate interval timer interrupts at regular intervals (figure 13.5).
WTCNT value H'FF Overflow Overflow Overflow Overflow
H'00 WT/IT = 0 TME = 1 ITI ITI ITI ITI
Time
ITI: Interval timer interrupt request generation
Figure 13.5 Operation in Interval Timer Mode 13.3.3 Operation when Standby Mode is Cleared
The watchdog timer has a special function to clear standby mode with an NMI interrupt. When using standby mode, set the WDT as described below. Transition to Standby Mode: The TME bit in WTCSR must be cleared to 0 to stop the watchdog timer counter before it enters standby mode. The chip cannot enter standby mode while the TME bit is set to 1. Set bits CKS2 to CKS0 in WTCSR so that the counter overflow interval is equal to or longer than the oscillation settling time. See section 22, Electrical Characteristics, for the oscillation settling time. Recovery from Standby Mode: When an NMI request signal is received in standby mode the clock oscillator starts running and the watchdog timer starts counting at the rate selected by bits CKS2 to CKS0 before standby mode was entered. When WTCNT overflows (changes from H'FF to H'00) the system clock () is presumed to be stable and usable; clock signals are supplied to the entire chip and standby mode ends. For details on standby mode, see section 21, Power Down Modes.
Rev. 2.00 Mar 09, 2006 page 552 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.3.4
Timing of Overflow Flag (OVF) Setting
In interval timer mode, when WTCNT overflows, the OVF flag in WTCSR is set to 1 and an interval timer interrupt (ITI) is requested (figure 13.6).
WTCNT
H'FF
H'00
Overflow signal (internal signal)
OVF
Figure 13.6 Timing of OVF Setting 13.3.5 Timing of Watchdog Timer Overflow Flag (WOVF) Setting
When WTCNT overflows the WOVF flag in RSTCSR is set to 1 and a WDTOVF signal is output. When the RSTE bit is set to 1, WTCNT overflow enables an internal reset signal to be generated for the entire chip (figure 13.7).
WTCNT
H'FF
H'00
Overflow signal (internal signal)
WOVF
Figure 13.7 Timing of WOVF Setting
Rev. 2.00 Mar 09, 2006 page 553 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.4
13.4.1
Usage Notes
Contention between WTCNT Write and Increment
If a count-up pulse is generated at the timing shown in figure 13.8 during a watchdog timer counter (WTCNT) write cycle, the write takes priority and the timer counter is not incremented (figure 13.8).
Address
WTCNT address
Internal write signal WTCNT input clock
WTCNT
N
M Counter write data
Figure 13.8 Contention between WTCNT Write and Increment 13.4.2 Changing CKS2 to CKS0 Bit Values
If the values of bits CKS2 to CKS0 are altered while the WDT is running, the count may increment incorrectly. Always stop the watchdog timer (by clearing the TME bit to 0) before changing the values of bits CKS2 to CKS0. 13.4.3 Switching between Watchdog Timer Mode and Interval Timer Mode
The WDT may not operate correctly if it is switched between watchdog timer mode and interval timer mode while it is running. To ensure correct operation, always stop the watchdog timer (by clearing the TME bit to 0) before switching between watchdog timer mode and interval timer mode.
Rev. 2.00 Mar 09, 2006 page 554 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
13.4.4
System Reset with WDTOVF
If a WDTOVF signal is input to the RES pin, the device cannot initialize correctly. Avoid logical input of the WDTOVF output signal to the RES input pin. To reset the entire system with the WDTOVF signal, use the circuit shown in figure 13.9.
Chip
Reset input RES
Reset signal to entire system
WDTOVF
Figure 13.9 Example of Circuit for System Reset with WDTOVF Signal 13.4.5 Internal Reset in Watchdog Timer Mode
If the RSTE bit is cleared to 0 in watchdog timer mode, the chip will not reset internally when a WTCNT overflow occurs, but WTCNT and WTCSR in the WDT will reset. When using sleep mode, do not use internal reset. Instead, use the RES pin for resetting. (See section13.4.4, System Reset with WDTOVF.) Internal reset can be used only when sleep mode is not used.
Rev. 2.00 Mar 09, 2006 page 555 of 906 REJ09B0292-0200
Section 13 Watchdog Timer (WDT)
Rev. 2.00 Mar 09, 2006 page 556 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Section 14 Serial Communication Interface with FIFO (SCIF)
14.1 Overview
The SH7616 is equipped with a two-channel serial communication interface with built-in FIFO buffers (SCIF: SCI with FIFO). The SCIF can handle both asynchronous and synchronous serial communication. A function is also provided for serial communication between processors (multiprocessor communication function). An on-chip Infrared Data Association (IrDA) interface based on the IrDA 1.0 system is also provided, enabling infrared communication. Sixteen-stage FIFO registers are provided for both transmission and reception, enabling fast, efficient, and continuous communication. 14.1.1 Features
The SCIF has the following features: * Choice of synchronous or asynchronous serial communication mode Asynchronous mode Serial data communication is executed using an asynchronous system in which synchronization is achieved character by character. Serial data communication can be carried out with standard asynchronous communication chips such as a Universal Asynchronous Receiver/Transmitter (UART) or Asynchronous Communication Interface Adapter (ACIA). A multiprocessor communication function is also provided that enables serial data communication with a number of processors. There is a choice of 12 serial data communication formats. * Data length: * Stop bit length: * Parity: * Multiprocessor bit: 7 or 8 1 or 2 bits Even/odd/none 1 or 0
* Receive error detection: Parity, overrun, and framing errors * Automatic break detection
Rev. 2.00 Mar 09, 2006 page 557 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Synchronous mode Serial data communication is synchronized with a clock. Serial data communication can be carried out with other chips that have a synchronous communication function. There is a single serial data communication format. * Data length: * IrDA 1.0 compliance * Full-duplex communication capability The transmitter and receiver are mutually independent, enabling transmission and reception to be executed simultaneously. In addition, the transmitter and receiver both have a 16-stage FIFO buffer structure, enabling continuous serial data transmission and reception. (However, IrDA communication is carried out in half-duplex mode.) * Built-in baud rate generator allows a choice of bit rates. * Choice of transmit/receive clock source: internal clock from baud rate generator or external clock from SCK pin * Four interrupt sources There are four interrupt sources--transmit-FIFO-data-empty, break, receive-FIFO-data-full, and receive-error--that can issue requests independently. The transmit-FIFO-data-empty and receive-FIFO-data-full interrupts can activate the on-chip DMAC to execute data transfer. * When not in use, the SCIF can be stopped by halting its clock supply to reduce power consumption. * Choice of LSB-first or MSB-first mode * In asynchronous mode, operation can be selected on a base clock of 4, 8, or 16 times the bit rate. * Built-in modem control functions (RTS and CTS) 8 bits * Receive error detection: Overrun errors
Rev. 2.00 Mar 09, 2006 page 558 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.1.2
Block Diagrams
A block diagram of the SCIF is shown in figure 14.1, and a diagram of the IrDA block in figure 14.2.
Module data bus
Bus interface
Internal data bus
SCFRDR (16-stage)
SCFTDR (16-stage)
SCFDR SCFCR SC1SSR SC2SSR SCSCR SCSMR SCFER SCIMR Transmission/ reception control
SCBRR P Baud rate generator P/4 P/16 P/64
RxD
SCRSR
SCTSR
TxD Parity generation Parity check SCK
Clock External clock BRI TxI RxI ERI
SCIF
IrDA/SCI switchover (to IrDA block)
Legend SCRSR: SCFRDR: SCTSR: SCFTDR: SCSMR: SCSCR:
Receive shift register Receive FIFO data register Transmit shift register Transmit FIFO data register Serial mode register Serial control register
SC1SSR: SC2SSR: SCBRR: SCFCR: SCFDR: SCFER: SCIMR:
Serial status 1 register Serial status 2 register Bit rate register FIFO control register FIFO data count register FIFO error register IrDA mode register
Figure 14.1 Block Diagram of SCIF
Rev. 2.00 Mar 09, 2006 page 559 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Clock input SCK
TxD Transmit clock SCIF Modulation unit TxD
RxD
Demodulation unit IrDA
RxD
IrDA/SCIF switchover
Figure 14.2 Diagram of IrDA Block 14.1.3 Pin Configuration
The SCIF has the serial pins shown in table 14.1. Table 14.1 SCIF Pins
Channel 1 Name Serial clock pin Receive data pin Transmit data pin Transmit request pin Transmit enable pin 2 Serial clock pin Receive data pin Transmit data pin Abbreviation SCK1 RxD1 TxD1 RTS CTS SCK2 RxD2 TxD2 I/O Input/ output Input Output Output Input Input/ output Input Output Function Clock input/output Receive data input Transmit data output Transmit request Transmit enable Clock input/output Receive data input Transmit data output
Rev. 2.00 Mar 09, 2006 page 560 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.1.4
Register Configuration
The SCIF has the internal registers shown in table 14.2. These registers are used to specify asynchronous mode/synchronous mode and the IrDA communication mode, the data format and the bit rate, and to perform transmitter/receiver control. Table 14.2 SCIF Registers
Channel 1 Name Serial mode register Bit rate register Serial control register Transmit FIFO data register Serial status 1 register Serial status 2 register Receive FIFO data register FIFO control register FIFO data count register FIFO error register IrDA mode register 2 Serial mode register Bit rate register Serial control register Transmit FIFO data register Serial status 1 register Serial status 2 register Receive FIFO data register FIFO control register FIFO data count register FIFO error register IrDA mode register Abbreviation SCSMR1 SCBRR1 SCSCR1 SCFTDR1 SC1SSR1 SC2SSR1 SCFRDR1 SCFCR1 SCFDR1 SCFER1 SCIFMR1 SCSMR2 SCBRR2 SCSCR2 SCFTDR2 SC1SSR2 SC2SSR2 SCFRDR2 SCFCR2 SCFDR2 SCFER2 SCIMR2 R/W R/W R/W R/W W Initial Value H'00 H'FF H'00 -- Address Access Size
H'FFFFFCC0 8 H'FFFFFCC2 8 H'FFFFFCC4 8 H'FFFFFCC6 8 H'FFFFFCC8 16 H'FFFFFCCA 8 H'FFFFFCCE 8 H'FFFFFCD0 16 H'FFFFFCD2 16 H'FFFFFCD4 8 H'FFFFFCE0 8 H'FFFFFCE2 8 H'FFFFFCE4 8 H'FFFFFCE6 8 H'FFFFFCE8 16 H'FFFFFCEA 8 H'FFFFFCEE 8 H'FFFFFCF0 16 H'FFFFFCF2 16 H'FFFFFCF4 8
R/(W)* H'0060 R/(W)* H'20 R R/W R R R/W R/W R/W R/W W H'00 H'0000 H'0000 H'00 H'00 H'FF H'00 --
Undefined H'FFFFFCCC 8
R/(W)* H'0060 R/(W)* H'20 R R/W R R R/W H'00 H'0000 H'0000 H'00
Undefined H'FFFFFCEC 8
Note: * Only 0 can be written, to clear flags. Use byte access on registers with an access size of 8, and word access on registers with an access size of 16.
Rev. 2.00 Mar 09, 2006 page 561 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2
Register Descriptions
With the exception of the IrDA mode register (SCIMR) and bits 6 to 3 (ICK3 to ICK0) of the serial mode register (SCSMR), IrDA communication mode settings are the same as for asynchronous mode. 14.2.1 Receive Shift Register (SCRSR)
Bit: R/W: 7 -- 6 -- 5 -- 4 -- 3 -- 2 -- 1 -- 0 --
The receive shift register (SCRSR) is the register used to receive serial data. The SCIF sets serial data input from the RxD pin in SCRSR in the order received, starting with the LSB (bit 0) or MSB (bit 7), and converts it to parallel data. When one byte of data has been received, it is transferred to the receive FIFO data register (SCFRDR) automatically. SCRSR cannot be read or written to directly. 14.2.2 Receive FIFO Data Register (SCFRDR)
Bit: R/W: 7 R 6 R 5 R 4 R 3 R 2 R 1 R 0 R
The receive FIFO data register (SCFRDR) is a 16-stage FIFO register (8 bits per stage) that stores received serial data. When the SCIF has received one byte of serial data, it transfers the received data from SCRSR to SCFRDR where it is stored, and completes the receive operation. SCRSR is then enabled for reception, and consecutive receive operations can be performed until the receive FIFO data register is full (16 data bytes). SCFRDR is a read-only register, and cannot be written to. If a read is performed when there is no receive data in the receive FIFO data register, an undefined value will be returned. When the receive FIFO data register is full of receive data, subsequent serial data is lost.
Rev. 2.00 Mar 09, 2006 page 562 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2.3
Transmit Shift Register (SCTSR)
Bit: R/W: 7 -- 6 -- 5 -- 4 -- 3 -- 2 -- 1 -- 0 --
The transmit shift register (SCTSR) is the register used to transmit serial data. To perform serial data transmission, the SCIF first transfers transmit data from SCFTDR to SCTSR, then sends the data to the TxD pin starting with the LSB (bit 0) or MSB (bit 7). When transmission of one byte is completed, the next transmit data is transferred from SCFTDR to SCTSR, and transmission started, automatically. SCTSR cannot be read or written to directly. 14.2.4 Transmit FIFO Data Register (SCFTDR)
Bit: R/W: 7 W 6 W 5 W 4 W 3 W 2 W 1 W 0 W
The transmit FIFO data register (SCFTDR) is a 16-stage FIFO register (8 bits per stage) that stores data for serial transmission. When the SCIF detects that SCTSR is empty, it transfers the transmit data written in SCFTDR to SCTSR and starts serial transmission. Serial transmission is performed continuously until there is no transmit data left in SCFTDR. SCFTDR is a write-only register, and cannot be read. The next data cannot be written when SCFTDR is filled with 16 bytes of transmit data. Data written in this case is ignored.
Rev. 2.00 Mar 09, 2006 page 563 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2.5
Serial Mode Register (SCSMR)
Bit: 7 C/A 6 CHR/ ICK3 0 R/W 5 PE/ ICK2 0 R/W 4 O/E/ ICK1 0 R/W 3 STOP/ ICK0 0 R/W 2 MP 0 R/W 1 CKS1 0 R/W 0 CKS0 0 R/W
Initial value: R/W:
0 R/W
The serial mode register (SCSMR) is an 8-bit register used to set the SCIF's serial communication format and select the baud rate generator clock source. In IrDA communication mode, it is used to select the output pulse width. SCSMR can be read or written to by the CPU at all times. SCSMR is initialized to H'00 by a reset, by the module standby function, and in standby mode. Bit 7--Communication Mode (C/A): Selects asynchronous mode or synchronous mode as the SCIF operating mode. In IrDA communication mode, this bit must be cleared to 0.
Bit 7: C/A A 0 1 Description Asynchronous mode Synchronous mode (Initial value)
Bit 6--Character Length (CHR)/IrDA Clock Select 3 (ICK3): Selects 7 or 8 bits as the data length in asynchronous mode. In synchronous mode, a fixed data length of 8 bits is used regardless of the CHR setting,
Bit 6: CHR 0 1 Description 8-bit data 7-bit data* (Initial value)
Note: * When 7-bit data is selected, the MSB (bit 7) of the transmit FIFO data register (SCFTDR) is not transmitted.
In IrDA communication mode, bit 6 is the IrDA clock select 3 (ICK3) bit, enabling appropriate clock pulses to be generated according to its setting. See Pulse Width Selection, in section 14.3.6, Operation in IrDA Mode, for details.
Rev. 2.00 Mar 09, 2006 page 564 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 5--Parity Enable (PE)/IrDA Clock Select 2 (ICK2): In asynchronous mode, selects whether or not parity bit addition is performed in transmission, and parity bit checking in reception. In synchronous mode, parity bit addition and checking is not performed, regardless of the PE bit setting.
Bit 5: PE 0 1 Description Parity bit addition and checking disabled Parity bit addition and checking enabled* (Initial value)
Note: * When the PE bit is set to 1, the parity (even or odd) specified by the O/E bit is added to transmit data before transmission. In reception, the parity bit is checked for the parity (even or odd) specified by the O/E bit.
In IrDA communication mode, bit 5 is the IrDA clock select 2 (ICK2) bit, enabling appropriate clock pulses to be generated according to its setting. See Pulse Width Selection, in section 14.3.6, Operation in IrDA Mode, for details. Bit 4--Parity Mode (O/E)/IrDA Clock Select 1 (ICK1): Selects either even or odd parity for use in parity addition and checking. The O/E bit setting is only valid when the PE bit is set to 1, enabling parity bit addition and checking, in asynchronous mode. The O/E bit setting is invalid in synchronous mode, and when parity addition and checking is disabled in asynchronous mode.
Bit 4: O/E E 0 1 Description Even parity* 2 Odd parity*
1
(Initial value)
Notes: 1. When even parity is set, parity bit addition is performed in transmission so that the total number of 1-bits in the transmit character plus the parity bit is even. In reception, a check is performed to see if the total number of 1-bits in the receive character plus the parity bit is even. 2. When odd parity is set, parity bit addition is performed in transmission so that the total number of 1-bits in the transmit character plus the parity bit is odd. In reception, a check is performed to see if the total number of 1-bits in the receive character plus the parity bit is odd.
In IrDA communication mode, bit 4 is the IrDA clock select 1 (ICK1) bit, enabling appropriate clock pulses to be generated according to its setting. See Pulse Width Selection, in section 14.3.6, Operation in IrDA Mode, for details.
Rev. 2.00 Mar 09, 2006 page 565 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 3--Stop Bit Length (STOP)/IrDA Clock Select 0 (ICK0): Selects 1 or 2 bits as the stop bit length in asynchronous mode. The STOP bit setting is only valid in asynchronous mode. When synchronous mode is set, the STOP bit setting is invalid since stop bits are not added.
Bit 3: STOP 0 1 Description 1 stop bit* 2 2 stop bits*
1
(Initial value)
Notes: 1. In transmission, a single 1-bit (stop bit) is added to the end of a transmit character before it is sent. 2. In transmission, two 1-bits (stop bits) are added to the end of a transmit character before it is sent.
In reception, only the first stop bit is checked, regardless of the STOP bit setting. If the second stop bit is 1, it is treated as a stop bit; if it is 0, it is treated as the start bit of the next transmit character. In IrDA communication mode, bit 3 is the IrDA clock select 0 (ICK0) bit, enabling appropriate clock pulses to be generated according to its setting. See Pulse Width Selection, in section 14.3.6, Operation in IrDA Mode, for details. Bit 2--Multiprocessor Mode (MP): Selects a multiprocessor format. When a multiprocessor format is selected, the PE bit and O/E bit parity settings are invalid. The MP bit setting is only valid in asynchronous mode; it is invalid in synchronous mode and IrDA mode. For details of the multiprocessor communication function, see section 14.3.3, Multiprocessor Communication Function.
Bit 2: MP 0 1 Description Multiprocessor function disabled Multiprocessor format selected (Initial value)
Bits 1 and 0--Clock Select 1 and 0 (CKS1, CKS0): These bits select the clock source for the builtin baud rate generator. The clock source can be selected from P, P/4, P/16, and P/64, according to the setting of bits CKS1 and CKS0.
Rev. 2.00 Mar 09, 2006 page 566 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
For the relationship between the clock source, the bit rate register setting, and the baud rate, see section 14.2.9, Bit Rate Register (SCBRR).
Bit 1: CKS1 0 1 Bit 0: CKS0 0 1 0 1 Description P clock P/4 clock P/16 clock P/64 clock (Initial value)
Note: P = peripheral clock
14.2.6
Serial Control Register (SCSCR)
Bit: 7 TIE 0 R/W 6 RIE 0 R/W 5 TE 0 R/W 4 RE 0 R/W 3 MPIE 0 R/W 2 -- 0 R 1 CKE1 0 R/W 0 CKE0 0 R/W
Initial value: R/W:
The serial control register (SCSCR) performs enabling or disabling of SCIF transmit/receive operations, serial clock output in asynchronous mode, and interrupt requests, and selection of the transmit/receive clock source. SCSCR can be read or written to by the CPU at all times. SCSCR is initialized to H'00 by a reset, by the module standby function, and in standby mode. Bit 7--Transmit Interrupt Enable (TIE): Enables or disables transmit-FIFO-data-empty interrupt (TXI) request generation when, after serial transmit data is transferred from the transmit FIFO data register (SCFTDR) to the transmit shift register (SCTSR), the number of data bytes in SCFTDR falls to or below the transmit trigger set number, and the TDFE flag is set to 1 in the serial status 1 register (SC1SSR).
Bit 7: TIE 0 1 Description Transmit-FIFO-data-empty interrupt (TXI) request disabled* Transmit-FIFO-data-empty interrupt (TXI) request enabled (Initial value)
Note: * TXI interrupt requests can be cleared by writing transmit data exceeding the transmit trigger set number to SCFTDR, reading 1 from the TDFE flag, then clearing it to 0, or by clearing the TIE bit to 0. When transmit data is written to SCFTDR using the on-chip DMAC, the TDFE flag is cleared automatically. Rev. 2.00 Mar 09, 2006 page 567 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 6--Receive Interrupt Enable (RIE): Enables or disables generation of a receive-FIFO-data-full interrupt (RXI) request and receive-error interrupt (ERI) request when, after serial receive data is transferred from the receive shift register (SCRSR) to the receive FIFO data register (SCFRDR), the number of data bytes in SCFRDR reaches or exceeds the receive trigger set number, and the RDF flag is set to 1 in SC1SSR.
Bit 6: RIE 0 1 Description Receive-FIFO-data-full interrupt (RXI) request, receive-error interrupt (ERI) request, and break interrupt (BRI) request disabled* (Initial value) Receive-FIFO-data-full interrupt (RXI) request, receive-error interrupt (ERI) request, and break interrupt (BRI) request enabled
Note: * RXI, ERI, and BRI interrupt requests can be cleared by reading 1 from the RDF or DR flag, the FER, PER, ORER, or ER flag, or the BRK flag, then clearing the flag to 0, or by clearing the RIE bit to 0. With the RDF flag, read receive data from SCFRDR until the number of receive data bytes is less than the receive trigger set number, then read 1 from the RDF flag and clear it to 0.
Bit 5--Transmit Enable (TE): Enables or disables the start of serial transmission by the SCIF.
Bit 5: TE 0 1 Description Transmission disabled* 2 Transmission enabled*
1
(Initial value)
Notes: 1. The TDRE flag in SC1SSR is fixed at 1. 2. Serial transmission is started when transmit data is written to SCFTDR in this state. Serial mode register (SCSMR) and FIFO control register (SCFCR) settings must be made, the transmission format decided, and the transmit FIFO reset, before the TE bit is set to 1.
Bit 4--Receive Enable (RE): Enables or disables the start of serial reception by the SCIF.
Bit 4: RE 0 1 Description Reception disabled* 2 Reception enabled*
1
(Initial value)
Notes: 1. Clearing the RE bit to 0 does not affect the RDF, DR, FER, PER, ORER, ER, and BRK flags, which retain their states. 2. Serial reception is started in this state when a start bit is detected in asynchronous mode or serial clock input is detected in synchronous mode. SCSMR settings must be made to decide the reception format before setting the RE bit to 1.
Rev. 2.00 Mar 09, 2006 page 568 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 3--Multiprocessor Interrupt Enable (MPIE): Enables or disables multiprocessor interrupts. The MPIE bit setting is only valid in asynchronous mode when the MP bit in SCSMR is set to 1. The MPIE bit setting is invalid in synchronous mode and IrDA mode, and when the MP bit is 0.
Bit 3: MPIE 0 Description Multiprocessor interrupts disabled (normal reception performed) (Initial value) [Clearing conditions] * * 1 When the MPIE bit is cleared to 0 When data with MPB = 1 is received
Multiprocessor interrupts enabled* Receive interrupt (RXI) requests, receive-error interrupt (ERI) requests, and setting of the RDF and FER in SC1SSR and ORER in SC2SSR are disabled until data with the multiprocessor bit set to 1 is received.
Note: * Receive data transfer from SCRSR to SCFRDR, receive error detection, and setting of the RDF and FER in SC1SSR and ORER flags in SC2SSR, is not performed. When receive data with MPB = 1 is received, the MPB flag in SC2SSR is set to 1, the MPIE bit is cleared to 0 automatically, and generation of RXI and ERI (when the RIE bit in SCSCR is set to 1) and FER and ORER flag setting is enabled.
Bit 2--Reserved: This bit is always read as 0. The write value should always be 0. Bits 1 and 0--Clock Enable 1 and 0 (CKE1, CKE0): These bits are used to select the SCIF clock source and enable or disable clock output from the SCK pin. The combination of the CKE1 and CKE0 bits determines whether the SCK pin functions as the serial clock output pin or the serial clock input pin. The function of the SCK pin should be selected with the pin function controller (PFC). The setting of the CKE0 bit, however, is only valid for internal clock operation (CKE1 = 0) in asynchronous mode. The CKE0 bit setting is invalid in synchronous mode and in the case of external clock operation (CKE1 = 1). The CKE1 and CKE0 bits must be set before determining the SCIF's operating mode with SCSMR. For details of clock source selection, see table 14.9 in section 14.3, Operation.
Rev. 2.00 Mar 09, 2006 page 569 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF) Bit 1: CKE1 0 Bit 0: CKE0 0
Description Asynchronous mode Synchronous mode Internal clock/SCK pin functions as input pin (input 1 signal ignored)* Internal clock/SCK pin functions as serial clock 1 output* Internal clock/SCK pin functions as clock output* Internal clock/SCK pin functions as serial clock output External clock/SCK pin functions as clock input* External clock/SCK pin functions as serial clock input
3 2
1
Asynchronous mode Synchronous mode
1
*4
Asynchronous mode Synchronous mode
Notes: 1. 2. 3. 4.
Initial value Outputs a clock with a frequency of 16/8/4 times the bit rate. Inputs a clock with a frequency of 16/8/4 times the bit rate. Don't care
14.2.7
Serial Status 1 Register (SC1SSR)
Bit: 15 PER3 0 R 7 ER 0 R/(W)* 14 PER2 0 R 6 TEND 1 R 13 PER1 0 R 5 TDFE 1 R/(W)* 12 PER0 0 R 4 BRK 0 R/(W)* 11 FER3 0 R 3 FER 0 R 10 FER2 0 R 2 PER 0 R 9 FER1 0 R 1 RDF 0 R/(W)* 8 FER0 0 R 0 DR 0 R/(W)*
Initial value: R/W: Bit: Initial value: R/W:
Note: * Only 0 can be written, to clear the flag.
The serial status 1 register (SC1SSR) is a 16-bit register in which the lower 8 bits consist of status flags that indicate the operating status of the SCIF, and the upper 8 bits indicate the number of receive errors in the data in the receive FIFO register. SC1SSR can be read or written to at all times. However, 1 cannot be written to the ER, TDFE, BRK, RDF, and DR status flags. Also note that in order to clear these flags to 0, they must first be read as 1. The TEND, FER, and PER flags are read-only and cannot be modified.
Rev. 2.00 Mar 09, 2006 page 570 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
SC1SSR is initialized to H'0084 by a reset, by the module standby function, and in standby mode. Bits 15 to 12--Parity Error Count 3 to 0 (PER3 to PER0): These bits indicate the number of data bytes in which a parity error occurred in the receive data in the receive FIFO data register. These bits are cleared by reading all the receive data in the receive FIFO data register, or by setting the RFRST bit to 1 in SCFCR and resetting the receive FIFO data register to the empty state. Bits 11 to 8--Framing Error Count 3 to 0 (FER3 to FER0): These bits indicate the number of data bytes in which a framing error occurred in the receive data in the receive FIFO data register. These bits are cleared by reading all the receive data in the receive FIFO data register, or by setting the RFRST bit to 1 in SCFCR and resetting the receive FIFO data register to the empty state. Bit 7--Receive Error (ER)
Bit 7: ER 0 Description Reception in progress, or reception has ended normally* [Clearing conditions] * * 1 In a reset or in standby mode When 0 is written to ER after reading ER = 1
1
(Initial value)
A framing error, parity error, or overrun error occurred during reception [Setting conditions] * * When the SCIF checks whether the stop bit at the end of the receive data is 2 1 when reception ends, and the stop bit is 0* When, in reception, the number of 1-bits in the receive data plus the parity bit does not match the parity setting (even or odd) specified by the O/E bit in the serial mode register (SCSMR) When the next serial receive operation is completed while there are 16 receive data bytes in SCFRDR
*
Notes: 1. The ER flag is not affected and retains its previous state when the RE bit in SCSCR is cleared to 0. When a framing error or parity error occurs, the receive data is still transferred to SCFRDR, and reception is then halted or continued according to the setting of the EI bit. When an overrun error occurs, the receive data is not transferred to SCFRDR and reception cannot be continued. 2. In 2-stop-bit mode, only the first stop bit is checked for a value of 1; the second stop bit is not checked.
Rev. 2.00 Mar 09, 2006 page 571 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 6--Transmit End (TEND): Indicates that there is no valid data in SCFTDR when the last bit of the transmit character is sent, and transmission has been ended.
Bit 6: TEND 0 Description Transmission is in progress [Clearing condition] When data is written to SCFTDR while TE = 1 1 Transmission has been ended [Setting conditions] * * * In a reset or in standby mode When the TE bit in SCSCR is 0 When there is no transmit data in SCFTDR on transmission of the last bit of a 1-byte serial transmit character (Initial value)
Bit 5--Transmit Data FIFO Empty (TDFE): Indicates that data has been transferred from the transmit FIFO data register (SCFTDR) to the transmit shift register (SCTSR), the number of data bytes in SCFTDR has fallen to or below the transmit trigger data number set by bits TTRG1 and TTRG0 in the FIFO control register (SCFCR), and transmit data can be written to SCFTDR.
Bit 5: TDFE 0 Description A number of transmit data bytes exceeding the transmit trigger set number have been written to SCFTDR [Clearing conditions] * * 1 When transmit data exceeding the transmit trigger set number is written to SCFTDR, and 0 is written to TDFE after reading TDFE = 1 When transmit data exceeding the transmit trigger set number is written to SCFTDR by the on-chip DMAC
The number of transmit data bytes in SCFTDR does not exceed the transmit trigger set number (Initial value) [Setting conditions] * * In a reset or in standby mode When the number of SCFTDR transmit data bytes falls to or below the transmit trigger set number as the result of a transmit operation*
Note: * As SCFTDR is a 16-byte FIFO register, the maximum number of bytes that can be written when TDFE = 0 is {16 - (transmit trigger set number)}. Data written in excess of this will be ignored. The number of data bytes in SCFTDR is indicated by the upper 8 bits of SCFDR.
Rev. 2.00 Mar 09, 2006 page 572 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 4--Break Detect (BRK): Indicates that a receive data break signal has been detected.
Bit 4: BRK 0 Description A break signal has not been received [Clearing conditions] * * 1 In a reset or in standby mode When 0 is written to BRK after reading BRK = 1 (Initial value)
A break signal has been received [Setting condition] When data with a framing error is received, and a framing error also occurs in the next receive data (all space "0")
Note: When a break is detected, transfer to SCFRDR of the receive data (H'00) following detection is halted. When the break ends and the receive signal returns to mark "1", receive data transfer is resumed.
Bit 3--Framing Error (FER): Indicates a framing error in the data read from the receive FIFO data register (SCFRDR).
Bit 3: FER 0 Description There is no framing error in the receive data read from SCFRDR (Initial value) [Clearing conditions] * * 1 In a reset or in standby mode When there is no framing error in SCFRDR read data
There is a framing error in the receive data read from SCFRDR [Setting condition] When there is a framing error in SCFRDR read data
Bit 2--Parity Error (PER): In asynchronous mode, indicates a parity error in the data read from the receive FIFO data register (SCFRDR).
Bit 2: PER 0 Description There is no parity error in the receive data read from SCFRDR [Clearing conditions] * In a reset or in standby mode * When there is no parity error in SCFRDR read data 1 There is a parity error in the receive data read from SCFRDR [Setting condition] When there is a parity error in SCFRDR read data Rev. 2.00 Mar 09, 2006 page 573 of 906 REJ09B0292-0200 (Initial value)
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 1--Receive Data Register Full (RDF): Indicates that the received data has been transferred to the receive FIFO data register (SCFRDR), and the number of receive data bytes in SCFRDR is equal to or greater than the receive trigger number set by bits RTRG1 and RTRG0 in the FIFO control register (SCFCR).
Bit 1: RDF 0 Description The number of receive data bytes in SCFRDR is less than the receive trigger set number (Initial value) [Clearing conditions] * * In a reset or in standby mode When SCFRDR is read until the number of receive data bytes in SCFRDR falls below the receive trigger set number, and 0 is written to RDF after reading RDF = 1 When SCFRDR is read by the on-chip DMAC until the number of receive data bytes in SCFRDR falls below the receive trigger set number
* 1
The number of receive data bytes in SCFRDR is equal to or greater than the receive trigger set number [Setting condition] When SCFRDR contains at least the receive trigger set number of receive data bytes
Note: SCFRDR is a 16-byte FIFO register. When RDF = 1, at least the receive trigger set number of data bytes can be read. If all the data in SCFRDR is read and another read is performed, the data value will be undefined. The number of receive data bytes in SCFRDR is indicated by the lower 8 bits of SCFDR.
Rev. 2.00 Mar 09, 2006 page 574 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 0--Receive Data Ready (DR): Indicates that there are fewer than the receive trigger set number of data bytes in the receive FIFO data register (SCFRDR), and no further data has arrived for at least 16 etu after the stop bit of the last data received.
Bit 0: DR 0 Description Reception is in progress or has ended normally and there is no receive data left in SCFRDR (Initial value) [Clearing conditions] * * 1 In a reset or in standby mode When 0 is written to DR after all the remaining receive data has been 1 read*
No further receive data has arrived, and SCFRDR contains fewer than the receive trigger set number of data bytes [Setting condition] When SCFRDR contains fewer than the receive trigger set number of receive data bytes, and no further data has arrived for at least 16 etu after the stop bit 2 of the last data received*
Notes: 1. All remaining receive data should be read before clearing the DR flag. 2. Equivalent to 1.6 frames when using an 8-bit, 1-stop-bit format. etu: Elementary time unit = sec/bit
14.2.8
Serial Status 2 Register (SC2SSR)
Bit: 7 TLM 0 R/W 6 RLM 0 R/W 5 N1 1 R/W 4 N0 0 R/W 3 MPB 0 R 2 MPBT 0 R/W 1 EI 0 R/W 0 ORER 0 R/(W)*
Initial value: R/W:
Note: * Only 0 can be written, to clear the flag.
The serial status 2 register (SC2SSR) is an 8-bit register. SC2SSR can be read or written to at all times. However, 1 cannot be written to the ORER flag. Also note that in order to clear this flag to 0, they must first be read as 1. SC2SSR is initialized to H'20 by a reset, by the module standby function, and in standby mode.
Rev. 2.00 Mar 09, 2006 page 575 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 7--Transmit LSB/MSB-First Select (TLM): Selects LSB-first or MSB-first mode in data transmission.
Bit 7: TLM 0 1 Description LSB-first transmission MSB-first transmission (Initial value)
Bit 6--Receive LSB/MSB-First Select (RLM): Selects LSB-first or MSB-first mode in data reception.
Bit 6: RLM 0 1 Description LSB-first reception MSB-first reception (Initial value)
Bits 5 and 4--Clock Bit Rate Ratio (N1, N0): These bits select the ratio of the base clock to the bit rate.
Bit 5: N1 0 1 Bit 4: N0 0 1 0 1 Description SCIF operates on base clock of 4 times the bit rate SCIF operates on base clock of 8 times the bit rate SCIF operates on base clock of 16 times the bit rate Setting prohibited (Initial value)
Bit 3--Multiprocessor bit (MPB): When reception is performed using a multiprocessor format in asynchronous mode, MPB stores the multiprocessor bit in the receive data. The MPB flag is read-only and cannot be modified.
Bit 3: MPB 0 1 Description Data with a 0 multiprocessor bit has been received* Data with a 1 multiprocessor bit has been received (Initial value)
Note: * Retains its previous state when the RE bit is cleared to 0 while using a multiprocessor format.
Bit 2--Multiprocessor Bit Transfer (MPBT): When transmission is performed using a multiprocessor format in asynchronous mode, MPBT stores the multiprocessor bit to be added to the transmit data.
Rev. 2.00 Mar 09, 2006 page 576 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
The MPBT bit setting is invalid in synchronous mode and IrDA mode, when a multiprocessor format is not used, and when the operation is not transmission.
Bit 2: MPBT 0 1 Description Data with a 0 multiprocessor bit is transmitted Data with a 1 multiprocessor bit is transmitted (Initial value)
Bit 1--Receive Data Error Ignore Enable (EI): Selects whether or not the receive operation is to be continued when a framing error or parity error occurs in receive data (ER = 1).
Bit 1: EI 0 1 Description Receive operation is halted when framing error or parity error occurs during reception (ER = 1) (Initial value) Receive operation is continued when framing error or parity error occurs during reception (ER = 1)
Note: When EI = 0, only the last data in SCFRDR is treated as data containing an error. When EI = 1, receive data is sent to SCFRDR even if it contains an error.
Bit 0--Overrun Error (ORER): Indicates that an overrun error occurred during reception, causing abnormal termination.
Bit 0: ORER 0 Description Reception in progress, or reception has ended normally* [Clearing conditions] * * 1 In a reset or in standby mode When 0 is written to ORER after reading ORER = 1 2 An overrun error occurred during reception* [Setting condition] When the next serial receive operation is completed while there are 16 receive data bytes in SCFRDR Notes: 1. The ORER flag is not affected and retains its previous state when the RE bit in SCSCR is cleared to 0. 2. The receive data prior to the overrun error is retained in SCFRDR, and the data received subsequently is lost. Serial reception cannot be continued while the ORER flag is set to 1. Also, serial transmission cannot be continued in synchronous mode.
1
(Initial value)
Rev. 2.00 Mar 09, 2006 page 577 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2.9
Bit Rate Register (SCBRR)
Bit: 7 1 R/W 6 1 R/W 5 1 R/W 4 1 R/W 3 1 R/W 2 1 R/W 1 1 R/W 0 1 R/W
Initial value: R/W:
The bit rate register (SCBRR) is an 8-bit register that sets the serial transmit/receive bit rate in accordance with the baud rate generator operating clock selected by bits CKS1 and CKS0 in the serial mode register (SCSMR). SCBRR can be read or written to by the CPU at all times. SCBRR is initialized to H'FF by a reset, by the module standby function, and in standby mode. The SCBRR setting is found from the following equations. Asynchronous mode:
N= P 64 x 22n-1 x B P 32 x 22n-1 x B P 16 x 22n-1 x B x 106 - 1 (When operating on a base clock of 16 times the bit rate)
N=
x 106 - 1 (When operating on a base clock of 8 times the bit rate)
N=
x 106 - 1 (When operating on a base clock of 4 times the bit rate)
Synchronous mode:
N= P 8 x 22n-1 x B x 106 - 1
Where B: N: P: n:
Bit rate (bits/s) SCBRR setting for baud rate generator (0 N 255) Peripheral module operating frequency (MHz) Baud rate generator input clock (n = 0, 1, 2, or 3) (See the table below for the relation between n and the clock.)
Rev. 2.00 Mar 09, 2006 page 578 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF) SCSMR Settings n 0 1 2 3 Clock P P/4 P/16 P/64 1 CKS1 0 CKS0 0 1 0 1
The bit rate error in asynchronous mode is found from the following equations:
P x 106 (N + 1) x B x 64 x 22n-1 - 1 x 100
Error (%) =
(When operating on a base clock of 16 times the bit rate) P x 106 (N + 1) x B x 32 x 22n-1 - 1 x 100
Error (%) =
(When operating on a base clock of 8 times the bit rate) P x 106 (N + 1) x B x 16 x 22n-1 - 1 x 100
Error (%) =
(When operating on a base clock of 4 times the bit rate)
Table 14.3 shows sample SCBRR settings in asynchronous mode, and table 14.4 shows sample SCBRR settings in synchronous mode. In both tables, the values are for operation on a base clock of 16 times the bit rate.
Rev. 2.00 Mar 09, 2006 page 579 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.3 Examples of Bit Rates and SCBRR Settings in Asynchronous Mode
P (MHz) 2 Bit Rate (Bits/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 1 1 0 0 0 0 0 0 0 0 0 N 141 103 207 103 51 25 12 6 2 1 1 Error (%) 0.03 0.16 0.16 0.16 0.16 0.16 0.16 -6.99 8.51 0.00 -18.62 n 1 1 0 0 0 0 0 0 0 0 0 2.097152 N 148 108 217 108 54 26 13 6 2 1 1 Error (%) -0.04 0.21 0.21 0.21 -0.70 1.14 -2.48 -2.48 13.78 4.86 -14.67 n 1 1 0 0 0 0 0 0 0 0 0 2.4576 N 174 127 255 127 63 31 15 7 3 1 1 Error (%) -0.26 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 22.88 0.00 n 1 1 1 0 0 0 0 0 0 0 -- N 212 155 77 155 77 38 19 9 4 2 -- 3 Error (%) 0.03 0.16 0.16 0.16 0.16 0.16 -2.34 -2.34 -2.34 0.00 --
P (MHz) 3.6864 Bit Rate (Bits/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 2 1 1 0 0 0 0 0 0 -- 0 N 64 191 95 191 95 47 23 11 5 -- 2 Error (%) 0.70 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -- 0.00 n 2 1 1 0 0 0 0 0 0 0 0 N 70 207 103 207 103 51 25 12 6 3 2 4 Error (%) 0.03 0.16 0.16 0.16 0.16 0.16 0.16 0.16 -6.99 0.00 8.51 n 2 1 1 0 0 0 0 0 0 0 0 4.9152 N 86 255 127 255 127 63 31 15 7 4 3 Error (%) 0.31 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -1.70 0.00 n 2 2 1 1 0 0 0 0 0 0 0 N 88 64 129 64 129 64 32 15 7 4 3 5 Error (%) -0.25 0.16 0.16 0.16 0.16 0.16 -1.36 1.73 1.73 0.00 1.73
Rev. 2.00 Mar 09, 2006 page 580 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF) P (MHz) 6 Bit Rate (Bits/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 2 2 1 1 0 0 0 0 0 0 0 N 106 77 155 77 155 77 38 19 9 5 4 Error (%) -0.44 0.16 0.16 0.16 0.16 0.16 0.16 -2.34 -2.34 0.00 -2.34 n 2 2 1 1 0 0 0 0 0 0 0 N 108 79 159 79 159 79 39 19 9 5 4 6.144 Error (%) 0.08 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 2.40 0.00 n 2 2 1 1 0 0 0 0 0 0 0 7.37288 N 130 95 191 95 191 95 47 23 11 6 5 Error (%) -0.07 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 5.33 0.00 n 2 2 1 1 0 0 0 0 0 0 0 N 141 103 207 103 207 103 51 25 12 7 6 8 Error (%) 0.03 0.16 0.16 0.16 0.16 0.16 0.16 0.16 0.16 0.00 -6.99
P (MHz) 9.8304 Bit Rate (Bits/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 2 2 1 1 0 0 0 0 0 0 0 N 174 127 255 127 255 127 63 31 15 9 7 Error (%) -0.26 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -1.70 0.00 n 2 2 2 1 1 0 0 0 0 0 0 N 177 129 64 129 64 129 64 32 15 9 7 10 Error (%) -0.25 0.16 0.16 0.16 0.16 0.16 0.16 -1.36 1.73 0.00 1.73 n 2 2 2 1 1 0 0 0 0 0 0 N 212 155 77 155 77 155 77 38 19 11 9 12 Error (%) 0.03 0.16 0.16 0.16 0.16 0.16 0.16 0.16 -2.34 0.00 -2.34 n 2 2 2 1 1 0 0 0 0 0 0 12.288 N 217 159 79 159 79 159 79 39 19 11 9 Error (%) 0.08 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 2.40 0.00
Rev. 2.00 Mar 09, 2006 page 581 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF) P (MHz) 14.7456 Bit Rate (Bits/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 3 2 2 1 1 0 0 0 0 0 0 N 64 191 95 191 95 191 95 47 23 14 11 Error (%) 0.70 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -1.70 0.00 n 3 2 2 1 1 0 0 0 0 0 0 N 70 207 103 207 103 207 103 51 25 15 12 16 Error (%) 0.03 0.16 0.16 0.16 0.16 0.16 0.16 0.16 0.16 0.00 0.16 n 3 3 2 2 1 1 0 0 0 0 0 N 132 97 194 97 194 97 194 97 48 29 23 30 Error (%) 0.13 -0.35 0.16 -0.35 0.16 -0.35 0.16 -0.35 -0.35 0.00 1.73
Rev. 2.00 Mar 09, 2006 page 582 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.4 Examples of Bit Rates and SCBRR Settings in Synchronous Mode
P (MHz) 4 Bit Rate (Bits/s) 110 250 500 1k 2.5 k 5k 10 k 25 k 50 k 100 k 250 k 500 k 1M 2M n -- 2 2 1 1 0 0 0 0 0 0 0 0 N -- 249 124 249 99 199 99 39 19 9 3 1 0* n -- 3 2 2 1 1 0 0 0 0 0 0 0 0 8 N -- 124 249 124 199 99 199 79 39 19 7 3 1 0* n -- 3 3 2 2 1 1 0 0 0 0 0 0 0 16 N -- 249 124 249 99 199 99 159 79 39 15 7 3 1 n -- -- 3 3 2 2 1 1 0 0 0 0 0 0 32 N -- -- 249 124 199 99 199 79 159 79 31 15 7 3
Note: As far as possible, the setting should be made so that the error is within 1%. Legend Blank: No setting is available. --: A setting is available but error occurs. * Continuous transmission/reception is not possible.
Rev. 2.00 Mar 09, 2006 page 583 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.5 shows the maximum bit rate for various frequencies in asynchronous mode when using the baud rate generator. Tables 14.6 and 14.7 show the maximum bit rates when using external clock input. Table 14.5 Maximum Bit Rate for Various Frequencies with Baud Rate Generator (Asynchronous Mode)
Settings P (MHz) 2 2.097152 2.4576 3 3.6864 4 4.9152 8 9.8304 12 14.7456 16 19.66080 20 24 24.57600 28 30 Maximum Bit Rate (Bits/s) 62500 65536 76800 93750 115200 125000 153600 250000 307200 375000 460800 500000 614400 625000 750000 768000 896875 937500 n 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 N 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Rev. 2.00 Mar 09, 2006 page 584 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.6 Maximum Bit Rate with External Clock Input (Asynchronous Mode)
P (MHz) 2 2.097152 2.4576 3 3.6864 4 4.9152 8 9.8304 12 14.7456 16 30 External Input Clock (MHz) 0.5000 0.5243 0.6144 0.7500 0.9216 1.0000 1.2288 2.0000 2.4576 3.0000 3.6864 4.0000 7.5000 Maximum Bit Rate (Bits/s) 31250 32768 38400 46875 57600 62500 76800 125000 153600 187500 230400 250000 468750
Table 14.7 Maximum Bit Rate with External Clock Input (Synchronous Mode)
P (MHz) 8 16 30 External Input Clock (MHz) 1.3333 2.6667 5.0 Maximum Bit Rate (Bits/s) 1333333.3 2666666.7 5000000.0
Rev. 2.00 Mar 09, 2006 page 585 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2.10 FIFO Control Register (SCFCR)
Bit: Initial value: R/W: 7 RTRG1 0 R/W 6 RTRG0 0 R/W 5 TTRG1 0 R/W 4 TTRG0 0 R/W 3 MCE 0 R/W 2 TFRST 0 R/W 1 RFRST 0 R/W 0 LOOP 0 R/W
The FIFO control register (SCFCR) performs data count resetting and trigger data number setting for the transmit and receive FIFO registers, and also contains a loopback test enable bit. SCFCR can be read or written to at all times. SCFCR is initialized to H'00 by a reset, by the module standby function, and in standby mode. Bits 7 and 6--Receive FIFO Data Number Trigger (RTRG1, RTRG0): These bits are used to set the number of receive data bytes that sets the receive data full (RDF) flag in the serial status 1 register (SC1SSR). The RDF flag is set when the number of receive data bytes in the receive FIFO data register (SCFRDR) is equal to or greater than the trigger set number shown in the following table.
Bit 7: RTRG1 0 1 Note: * Initial value Bit 6: RTRG0 0 1 0 1 Receive Trigger Number 1* 4 8 14
Bits 5 and 4--Transmit FIFO Data Number Trigger (TTRG1, TTRG0): These bits are used to set the number of remaining transmit data bytes that sets the transmit FIFO data register empty (TDFE) flag in the serial status 1 register (SC1SSR). The TDFE flag is set when the number of transmit data bytes in the transmit FIFO data register (SCFTDR) is equal to or less than the trigger set number shown in the following table.
Bit 5: TTRG1 0 Bit 4: TTRG0 Transmit Trigger Number 8 (8)*
0 1 4 (12) 1 0 2 (14) 1 1 (15) Note: * Initial value. Figures in parentheses are the number of empty bytes in SCFTDR when the flag is set. Rev. 2.00 Mar 09, 2006 page 586 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Bit 3--Modem Control Enable (MCE): Enables or disables the CTS and RTS modem control signals.
Bit 3: MCE 0 1 Description Modem signals disabled* Modem signals enabled (Initial value)
Note: * CTS is fixed at active-0 regardless of the input value, and RTS output is also fixed at 0.
Bit 2--Transmit FIFO Data Register Reset (TFRST): Invalidates the transmit data in the transmit FIFO data register and resets it to the empty state.
Bit 2: TFRST 0 1 Description Reset operation disabled Reset operation enabled (Initial value)
Note: A reset operation is performed in the event of a reset, module standby, or in standby mode.
Bit 1--Receive FIFO Data Register Reset (RFRST): Invalidates the receive data in the receive FIFO data register and resets it to the empty state.
Bit 1: RFRST 0 1 Description Reset operation disabled Reset operation enabled (Initial value)
Note: A reset operation is performed in the event of a reset, module standby, or in standby mode.
Bit 0--Loopback Test (LOOP): Internally connects the transmit output pin (TxD) and receive input pin (RxD), enabling loopback testing.
Bit 0: LOOP 0 1 Description Loopback test disabled Loopback test enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 587 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2.11 FIFO Data Count Register (SCFDR) The FIFO data count register (SCFDR) is a 16-bit register that indicates the number of data bytes stored in the transmit FIFO data register (SCFTDR) and receive FIFO data register (SCFRDR). The upper 8 bits show the number of transmit data bytes in SCFTDR, and the lower 8 bits show the number of receive data bytes in SCFRDR. SCFDR can be read by the CPU at all times. SCFDR is initialized to H'00 by a reset, by the module standby function, and in standby mode. It is also initialized to H'00 by setting the TFRST and RFRST bits to 1 in SCFCR to reset SCFTDR and SCFRDR to the empty state.
Upper 8 bits: Initial value: R/W: 15 -- 0 R 14 -- 0 R 13 -- 0 R 12 T4 0 R 11 T3 0 R 10 T2 0 R 9 T1 0 R 8 T0 0 R
Bits 15 to 13--Reserved: These bits are always read as 0. The write value should always be 0. Bits 12 to 8--Transmit FIFO Data Count 4 to 0 (T4 to T0): These bits show the number of untransmitted data bytes in SCFTDR. A value of H'00 indicates that there is no transmit data, and a value of H'10 indicates that SCFTDR is full of transmit data. The value is cleared to H'00 by transmitting all the data, as well as by the above initialization conditions.
Lower 8 bits: Initial value: R/W: 7 -- 0 R 6 -- 0 R 5 -- 0 R 4 R4 0 R 3 R3 0 R 2 R2 0 R 1 R1 0 R 0 R0 0 R
Bits 7 to 5--Reserved: These bits are always read as 0. The write value should always be 0. Bits 4 to 0--Receive FIFO Data Count 4 to 0 (R4 to R0): These bits show the number of receive data bytes in SCFRDR. A value of H'00 indicates that there is no receive data, and a value of H'10 indicates that SCFRDR is full of receive data. The value is cleared to H'00 by reading all the receive data from SCFRDR, as well as by the above initialization conditions.
Rev. 2.00 Mar 09, 2006 page 588 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.2.12 FIFO Error Register (SCFER) The FIFO error register (SCFER) indicates the data location at which a parity error or framing error occurred in receive data stored in the receive FIFO data register (SCFRDR). SCFER can be read at all times.
Upper 8 bits: Initial value: R/W: Lower 8 bits: Initial value: R/W: 15 ED15 0 R 7 ED7 0 R 14 ED14 0 R 6 ED6 0 R 13 ED13 0 R 5 ED5 0 R 12 ED12 0 R 4 ED4 0 R 11 ED11 0 R 3 ED3 0 R 10 ED10 0 R 2 ED2 0 R 9 ED9 0 R 1 ED1 0 R 8 ED8 0 R 0 ED0 0 R
Bits 15 to 0--Error Data Flags 15 to 0 (ED15 to ED0): These flags indicate the data location in the receive FIFO data register at which an error occurred. When data in the nth stage of the buffer contains an error, the nth bit is set to 1. Note that this register is not cleared by setting the RFRST bit to 1 in SCFCR.
Bits 15 to 0: ED15 to ED0 0 1 Description No parity or framing error in data in corresponding stage of register FIFO (Initial value) Parity or framing error present in data in corresponding stage of register FIFO
Note: A reset operation is performed in the event of a reset, when the module standby function is used, or in standby mode. These flags are also cleared by reading the data in which the parity error or framing error occurred from SCFRDR.
14.2.13 IrDA Mode Register (SCIMR) The IrDA mode register (SCIFMR) allows selection of the IrDA mode and the IrDA output pulse width, and inversion of the IrDA receive data polarity. SCIMR can be read and written to at all times. SCIMR is initialized to H'00 by a reset, by the module standby function, and inop standby mode.
Rev. 2.00 Mar 09, 2006 page 589 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF) Bit: Initial value: R/W: 7 IRMOD 0 R/W 6 PSEL 0 R/W 5 RIVS 0 R/W 4 -- 0 R 3 -- 0 R 2 -- 0 R 1 -- 0 R 0 -- 0 R
Bit 7--IrDA Mode (IRMOD): Selects operation as an IrDA serial communication interface.
Bit 7: IRMOD 0 1 Description Operation as SCIF is selected Operation as IrDA is selected* (Initial value)
Note: * When operation as an IrDA interface is selected, bit 7 (C/A) of the serial mode register (SCSMR) must be cleared to 0.
Bit 6--Output Pulse Width Select (PSEL): Selects either 3/16 of the bit length set by bits ICK3 to ICK0 in the serial mode register (SCSMR), or 3/16 of the bit length corresponding to the selected baud rate, as the IrDA output pulse width. The setting is shown together with bits 6 to 3 (ICK3 to ICK0) of the serial mode register (SCSMR).
Serial Mode Register (SCSMR) Bit 6: ICK3 ICK3 Don't care Bit 5: ICK2 ICK2 Don't care Bit 4: ICK1 ICK1 Don't care Bit 3: ICK0 ICK0 Don't care SCIMR Bit 2: PSEL 1 0 Description Pulse width: 3/16 of bit length set in bits ICK3 to ICK0 Pulse width: 3/16 of bit length set in SCBRR (Initial value)
Note: A fixed clock pulse signal, IRCLK, must be generated by multiplying the P clock by 1/2 N + 2 (where N is determined by the value set in ICK3 to ICK0). For details, see section 14.3.6 Pulse Width Selection.
Bit 5--IrDA Receive Data Inverse (RIVS): Allows inversion of the receive data polarity to be selected in IrDA communication.
Bit 5: RIVS 0 1 Description Receive data polarity inverted in reception Receive data polarity not inverted in reception (Initial value)
Note: Make the selection according to the characteristics of the IrDA modulation/demodulation module.
Bits 4 to 0--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 590 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.3
14.3.1
Operation
Overview
The SCIF can carry out serial communication in two modes: asynchronous mode in which synchronization is achieved character by character, and synchronous mode in which synchronization is achieved with clock pulses. An IrDA block is also provided, enabling infrared communication conforming to IrDA 1.0 to be executed by connecting an infrared transmission/reception unit. Sixteen-stage FIFO buffers are provided for both transmission and reception, reducing the CPU overhead and enabling fast, continuous communication to be performed. Selection of asynchronous, synchronous, or IrDA mode and the transmission format is made by means of the serial mode register (SCSMR) and IrDA mode register (SCIMR) as shown in table 14.8. The SCIF clock source is determined by a combination of the C/A bit in SCSMR, the IRMOD bit in SCIMR, and the CKE1 and CKE0 bits in the serial control register (SCSCR), as shown in table 14.9. * Asynchronous Mode Data length: Choice of 7 or 8 bits Choice of parity addition, multiprocessor bit addition, and addition of 1 or 2 stop bits (the combination of these parameters determines the transmit/receive format and character length) Detection of framing, parity, and overrun errors, receive FIFO data full and receive data ready conditions, and breaks, during reception Detection of transmit FIFO data empty condition during transmission Choice of internal or external clock as SCIF clock source When internal clock is selected: The SCIF operates on a clock with a frequency of 16, 8, or 4 times the bit rate of the baud rate generator, and can output this operating clock. When external clock is selected: A clock with a frequency of 16, 8, or 4 times the bit rate must be input (the built-in baud rate generator is not used). * Synchronous Mode Transmit/receive format: Fixed 8-bit data Detection of overrun errors during reception Choice of internal or external clock as SCIF clock source When internal clock is selected: The SCIF operates on the baud rate generator clock and can output a serial clock to external devices.
Rev. 2.00 Mar 09, 2006 page 591 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
When external clock is selected: The on-chip baud rate generator is not used, and the SCIF operates on the input serial clock. * IrDA Mode IrDA 1.0 compliance Data length: 8 bits Stop bit length: 1 bit Protection function to prevent receiver being affected during transmission Clock source: Internal clock Table 14.8 SCSMR and SCIMR Settings for Serial Transmit/Receive Format Selection
SCIMR Bit 7: IRMOD 0 SCSMR Settings Bit 7: Bit 6: Bit 2: Bit 5: Bit 3: C/A CHR MP PE STOP Mode A 0 0 0 0 1 1 0 1 0 1 * * 1 0 1 1 0 1 * ICK3 * * * * * 0 1 0 1 0 1 0 1 0 1 0 1 * ICK0 * Synchronous mode IrDA mode Setting prohibited Asynchronous 8-bit mode (multi- data processor format) 7-bit data 8-bit data 8-bit data -- Absent Absent -- Present 7-bit data SCIF Transmit/Receive Format Data Length MP Bit Absent Parity Bit Stop Bit Length 2 bits Present 1 bit 2 bits Absent 1 bit 2 bits Present 1 bit 2 bits Absent 1 bit 2 bits 1 bit 2 bits Absent None Absent 1 bit -- --
Asynchronous 8-bit mode data
Absent 1 bit
ICK2 ICK1 * *
Note: An asterisk in the table means "Don't care."
Rev. 2.00 Mar 09, 2006 page 592 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.9 SCSMR and SCSCR Settings for SCIF Clock Source Selection
SCSMR Bit 7: C/A A 0 SCSCR Setting Bit 1: CKE1 0 Bit 0: CKE0 0 1 1 1 0 1 0 1 0 1 0 1 Synchronous mode Internal External External Mode Asynchronous mode Clock Source Internal SCIF Transmit/Receive Clock SCK Pin Function SCIF does not use SCK pin Outputs clock with frequency of 16/8/4 times bit rate Inputs clock with frequency of 16/8/4 times bit rate Outputs serial clock Inputs serial clock
14.3.2
Operation in Asynchronous Mode
In asynchronous mode, characters are sent or received, each preceded by a start bit indicating the start of communication and followed by one or two stop bits indicating the end of communication. Serial communication is thus carried out with synchronization established on a character-bycharacter basis. Inside the SCIF, the transmitter and receiver are independent units, enabling full-duplex communication. Both the transmitter and the receiver also have a 16-stage FIFO buffer structure, so that data can be read or written during transmission or reception, enabling continuous data transfer. Figure 14.3 shows the general format for asynchronous serial communication. In asynchronous serial communication, the communication line is usually held in the mark state (high level). The SCIF monitors the line, and when it goes to the space state (low level), recognizes a start bit and starts serial communication. One serial communication character consists of a start bit (low level), followed by data (LSB-first or MSB-first order selectable), a parity bit or multiprocessor bit (high or low level), and finally one or two stop bits (high level).
Rev. 2.00 Mar 09, 2006 page 593 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
In asynchronous mode, the SCIF performs synchronization at the falling edge of the start bit in reception. The SCIF samples the data on the eighth (fourth, second) pulse of a clock with a frequency of 16 (8, 4) times the length of one bit, so that the transfer data is latched at the center of each bit.
Idle state (mark state) 1 0/1 Parity bit 1 bit, or none 1 Stop bit(s) 1 or 2 bits 1
1 Serial data 0 Start bit 1 bit
(LSB) D0 D1 D2 D3 D4 D5 D6
(MSB) D7
Transmit/receive data 7 or 8 bits
One unit of transfer data (character or frame)
Figure 14.3 Data Format in Asynchronous Communication (Example with 8-Bit Data, Parity, Two Stop Bits, LSB-First Transfer) Transmit/Receive Format: Table 14.10 shows the transmit/receive formats that can be used in asynchronous mode. Any of 12 transmit/receive formats can be selected by means of settings in the serial mode register (SCSMR).
Rev. 2.00 Mar 09, 2006 page 594 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.10 Serial Transmit/Receive Formats (Asynchronous Mode)
SCSMR Settings CHR PE MP STOP
0 0 0 0 1 1 0 1 1 0 0 1 1 0 1 0 * * 1 * * 1 0 1 0 1
Serial Transmit/Receive Format and Frame Length 1
S S S S S S S S S S S S
2
3
4
5 8-bit data 8-bit data 8-bit data 8-bit data 8-bit data 8-bit data 7-bit data 7-bit data 8-bit data 8-bit data 7-bit data 7-bit data
6
7
8
9
10
STOP
11
12
STOP STOP P P STOP STOP STOP P P STOP STOP STOP MPB STOP MPB STOP STOP MPB STOP MPB STOP STOP STOP STOP STOP
Note: An asterisk in the table means "Don't care." Legend S: Start bit STOP: Stop bit P: Parity bit MPB: Multiprocessor bit
Rev. 2.00 Mar 09, 2006 page 595 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Clock: Either an internal clock generated by the built-in baud rate generator or an external clock input at the SCK pin can be selected as the SCI's serial clock, according to the setting of the C/A bit in SCSMR and the CKE1 and CKE0 bits in SCSCR. For details of SCIF clock source selection, see table 14.9. When an external clock is input at the SCK pin, the input clock frequency should be 16, 8, or 4 times the bit rate used. When the SCIF is operated on an internal clock, the clock can be output from the SCK pin. The frequency of the clock output in this case is 16, 8, or 4 times the bit rate. Data Transmit/Receive Operations * SCIF Initialization (Asynchronous Mode) Before transmitting and receiving data, it is necessary to clear the TE and RE bits to 0 in SCSCR, then initialize the SCIF as described below. When the operating mode, communication format, etc., is changed, the TE and RE bits must be cleared to 0 before making the change using the following procedure. When the TE bit is cleared to 0, the transmit shift register (SCTSR) is initialized. Note that clearing the TE and RE bits to 0 does not change the contents of the serial status 1 register (SC1SSR), the transmit FIFO data register (SCFTDR), or the receive FIFO data register (SCFRDR). The TE bit should not be cleared to 0 until all transmit data has been transmitted and the TEND flag has been set in SC1SSR. It is possible to clear the TE bit to 0 during transmission, but the data being transmitted will go to the high-impedance state after TE is cleared. Also, before starting transmission by setting TE again, the TFRST bit should first be set to 1 in SCFCR to reset SCFTDR. When an external clock is used the clock should not be stopped during operation, including initialization, since operation will be unreliable in this case. Figure 14.4 shows a sample SCIF initialization flowchart.
Rev. 2.00 Mar 09, 2006 page 596 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization Clear TE and RE bits to 0 in SCSCR Set TFRST and RFRST bits to 1 in SCFCR Set CKE1 and CKE0 bits in SCSCR (leaving TE and RE bits cleared to 0) Set transmit/receive format in SCSMR Set value in SCBRR Wait 1-bit interval elapsed? Yes Set RTRG1-0 and TTRG1-0 bits in SCFCR, and clear TFRST and RFRST bits to 0 Set TE or RE bit to 1 in SCSCR, and set RIE, TIE, and MPIE bits End No
1. Set the clock selection in SCSCR. Be sure to clear bits RIE, TIE, and MPIE, and bits TE and RE, to 0. When clock output is selected in asynchronous mode, it is output immediately after SCSCR settings are made. Select input or output for the SCK pin with the PFC. 2. Set the transmit/receive format in SCSMR. When using IrDA mode, also set SCIFMR. 3. Write a value corresponding to the bit rate into the bit rate register (SCBRR). (Not necessary if an external clock is used.) 4. Wait at least one bit interval, then set the TE bit or RE bit in SCSCR to 1. Also set the RIE, TIE, and MPIE bits. Setting the TE and RE bits enables the TxD and RxD pins to be used. When transmitting, the SCIF will go to the mark state; when receiving, it will go to the idle state, waiting for a start bit.
1
2
3
4
Figure 14.4 Sample SCIF Initialization Flowchart * Serial Data Transmission (Asynchronous Mode) Figure 14.5 shows a sample flowchart for serial transmission. Use the following procedure for serial data transmission after enabling the SCIF for transmission.
Rev. 2.00 Mar 09, 2006 page 597 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization Start of transmission
1
1. PFC initialization: Set the TxD pin, and the SCK pin if necessary, with the PFC. 2. SCIF status check and transmit data write: Read the serial status 1 register (SC1SSR) and check that the TDFE bit is set to 1, then write transmit data to the transmit FIFO data register (SCFTDR) and clear the TDFE bit to 0 after reading TDFE = 1. The TEND bit is cleared automatically when transmission is started by writing transmit data. The number of data bytes that can be written is {16 - (transmit trigger set number)}. 3. Serial transmission continuation procedure: To continue serial transmission, read 1 from the TDFE bit to confirm that writing is possible, then write data to SCFTDR, and then clear the TDFE bit to 0. (Checking and clearing of the TDFE bit is automatic when the DMAC is activated by a transmit-FIFOdata-empty interrupt (TXI) request, and data is written to SCFTDR.) 4. Break output at the end of serial transmission: To output a break in serial transmission, clear the port data register (DR) to 0, then clear the TE bit to 0 in SCSCR, and set the TxD pin as an output port with the PFC. In steps 2 and 3, the number of transmit data bytes that can be written can be ascertained from the number of transmit data bytes in SCFTDR indicated in the upper 8 bits of the FIFO data count register (SCFDR).
Read TDFE bit in SC1SSR
2 No
TDFE = 1? Yes Write {16 - (transmit trigger set number)} bytes of transmit data to SCFTDR, and clear TDFE bit to 0 in SC1SSR after reading TDFE = 1 3 All data transmitted? Yes Read TEND bit in SC1SSR TEND = 1? Yes Break output? Yes Clear DR to 0 Clear TE bit to 0 in SCSCR, and set TxD pin as output port with PFC 4
No
No
No
End of transmission
Figure 14.5 Sample Serial Transmission Flowchart
Rev. 2.00 Mar 09, 2006 page 598 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
In serial transmission, the SCIF operates as described below. 1. When data is written to the transmit FIFO data register (SCFTDR), the SCIF transfers the data to the transmit shift register (SCTSR), and starts transmitting. Check that the TDFE flag is set to 1 in the serial status 1 register (SC1SSR) before writing transmit data to SCFTDR. The number of data bytes that can be written is at least {16 - (transmit trigger set number)}. 2. When data is transferred from SCFTDR to SCTSR and transmission is started, transmit operations are performed continually until there is no transmit data left in SCFTDR. If the number of data bytes in SCFTDR falls to or below the transmit trigger number set in the FIFO control register (SCFCR) during transmission, the TDFE flag is set. If the TE bit setting in the serial control register (SCSCR) is 1 at this time, a transmit-FIFO-data-empty interrupt (TXI) is requested. The serial transmit data is sent from the TxD pin in the following order. a. Start bit: One 0-bit is output. b. Transmit data: 8-bit or 7-bit data is output in LSB-first or MSB-first order according to the setting of the TLM bit in SC2SSR. c. Parity bit or multiprocessor bit: One parity bit (even or odd parity), or one multiprocessor bit is output. (A format in which neither a parity bit nor a multiprocessor bit is output can also be selected.) d. Stop bit(s): One or two 1-bits (stop bits) are output. e. Mark state: 1 is output continuously until the start bit that starts the next transmission is sent. 3. The SCIF checks for transmit data in SCFTDR at the timing for sending the stop bit. If there is data in SCFTDR, it is transferred to SCTSR, the stop bit is sent, and then serial transmission of the next frame is started. If there is no transmit data in SCFTDR, the TEND flag is set to 1 in the serial status 1 register (SC1SSR), the stop bit is sent, and then the line goes to the mark state in which 1 is output continuously. Figure 14.6 shows an example of the operation for transmission in asynchronous mode.
Rev. 2.00 Mar 09, 2006 page 599 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Start bit Data Parity Stop Start bit bit bit Data Parity Stop bit bit
1 Serial data
1 Idle state (mark state)
0
D0
D1
D7
0/1
1
0
D0
D1
D7
0/1
1
TDFE
TEND TXI interrupt request TXI interrupt request
Data written to SCFTDR and TDFE flag cleared to 0 by TXI interrupt handler One frame
Figure 14.6 Example of Transmit Operation in Asynchronous Mode (Example with 8-Bit Data, Parity, One Stop Bit, LSB-First Transfer) 4. When modem control is enabled, transmission can be stopped and restarted in accordance with the CTS input value. When CTS is set to 1, if transmission is in progress, the line goes to the mark state after transmission of one frame. When CTS is set to 0, the next transmit data is output starting from the start bit. Figure 14.7 shows an example of the operation when modem control is used.
Start bit Parity Stop bit bit Start bit
Serial data
0
D0
D1
D7
0/1
0
D0
D1
D7
0/1
CTS
Drive high at this point before stop bit
Figure 14.7 Example of Operation Using Modem Control (CTS CTS) CTS
Rev. 2.00 Mar 09, 2006 page 600 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
* Serial Data Reception (Asynchronous Mode) Figure 14.8 shows a sample flowchart for serial reception. Use the following procedure for serial data reception after enabling the SCIF for reception.
Initialization 1 1. PFC initialization: Set the RxD pin, and the SCK pin if necessary, with the PFC.
2. Receive error handling and break detection: Read ER, BRK, FER, PER, and DR in SC1SSR, and ORER in SC2SSR, to check whether a receive error has occurred. If a receive error has occurred, read the Read ER, BRK, FER, PER, ER, BRK, FER, PER, and DR flags in and DR bits in SC1SSR, and 2 SC1SSR and the ORER flag in SC2SSR ORER bit in SC2SSR to identify the error. After performing the appropriate error handling, ensure that the ORER, BRK, DR, and ER bits are all ER BRK Yes cleared to 0. Reception cannot be FER PER DR resumed if the ORER bit is set to 1. The ORER = 1? setting of the EI bit in SC2SSR determines whether reception is Error handling No continued or halted when any of PER3-0 or FER3-0 is set to 1. In the case of a framing error, a break 3 Read RDF flag in SC1SSR can be detected by reading the value of the RxD pin. Start of reception No RDF = 1? Yes Read receive data from SCFRDR, and clear RDF flag to 0 in SC1SSR 3. SCIF status check and receive data read: Read the serial status 1 register (SC1SSR) and check that RDF = 1, then read receive data from the receive FIFO data register (SCFRDR) and clear the RDF bit to 0. Transition of the RDF bit from 0 to 1 can also be identified by means of an RXI interrupt. 4. Serial reception continuation procedure: To continue serial reception, read at least the receive trigger set number of data bytes from SCFRDR, and write 0 to the RDF flag after reading 1 from it. The number of receive data bytes in SCFRDR can be ascertained by reading the lower bits of the FIFO data count register (SCFDR). (The RDF bit is cleared automatically when the DMAC is activated by an RXI interrupt and the SCFRDR value is read.)
4
No
All data received? Yes Clear RE bit to 0 in SCSCR
End of reception
Figure 14.8 Sample Serial Reception Flowchart (1)
Rev. 2.00 Mar 09, 2006 page 601 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
1. Whether a framing error or parity error has occurred in the receive data read from SCFRDR can be ascertained from the FER and PER bits in SC1SSR. 2. When a break signal is received, receive data is not transferred to SCFRDR while the BRK flag is set. However, note that the H'00 break data in which a framing error occurred is stored as the last data in SCFRDR.
Error handling
No
ORER = 1? Yes Overrun error handling
No
BRK = 1? Yes Clear RE bit to 0 in SCSCR
No
DR = 1? Yes Read receive data from SCFRDR 1
No
FER = 1? Yes Framing error handling 2
No
PER = 1? Yes Parity error handling
No
All data read? Yes Clear ORER, BRK, DR, and ER flags to 0
End
Figure 14.8 Sample Serial Reception Flowchart (2)
Rev. 2.00 Mar 09, 2006 page 602 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
In serial reception, the SCIF operates as described below. 1. The SCIF monitors the communication line, and if a 0 start bit is detected, performs internal synchronization and starts reception. 2. The received data is stored in SCRSR in LSB-to-MSB order or MSB-to-LSB order according to the setting of the RLM bit in SC2SSR. 3. The parity bit and stop bit are received. After receiving these bits, the SCIF carries out the following checks. a. Parity check: The SCIF checks whether the number of 1-bits in the receive data agrees with the parity (even or odd) set in the O/E bit in the serial mode register (SCSMR). b. Stop bit check: The SCIF checks whether the stop bit is 1. If there are two stop bits, only the first is checked. c. Status check: The SCIF checks whether receive data can be transferred from the receive shift register (SCRSR) to SCFRDR. d. Break check: The SCIF checks that the BRK flag is 0, indicating no break.
If all the above checks are passed, the receive data is stored in SCFRDR. If a receive error is detected in the error check, the operation is as shown in table 14.11. Note: No further receive operations can be performed when an overrun error has occurred. The setting of the EI bit in SC2SSR determines whether reception is continued or halted when a framing error or parity error occurs. Also, as the RDF flag is not set to 1 when receiving, the error flags must be cleared to 0. 4. If the RIE bit setting in SCSCR is 1 when the RDF or DR flag is set to 1, a receive-FIFO-datafull interrupt (RXI) is requested. If the RIE bit setting in SCSCR is 1 when the ORER, PER, or FER flag is set to 1, a receiveerror interrupt (ERI) is requested. If the RIE bit setting in SCSCR is 1 when the BRK flag is set to 1, a break-receive interrupt (BRI) is requested.
Rev. 2.00 Mar 09, 2006 page 603 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.11 Receive Error Conditions
Receive Error Overrun error Abbreviation ORER Condition Data Transfer
Next serial receive operation is Receive data is not transferred completed while there are 16 from SCRSR to SCFRDR receive data bytes in SCFRDR Stop bit is 0 Received data parity differs from that (even or odd) set in SCSMR Receive data is transferred from SCRSR to SCFRDR Receive data is transferred from SCRSR to SCFRDR
Framing error Parity error
FER PER
Figure 14.9 shows an example of the operation for reception in asynchronous mode.
1 Serial data
Start bit Data Parity Stop Start bit bit bit Data Parity Stop bit bit
1
0
D0
D1
D7
0/1
1
0
D0
D1
D7
0/1
1
Idle state (mark state)
RDF
FER
RXI interrupt request One frame
Data read and RDF flag cleared to 0 by RXI interrupt handler
ERI interrupt request due to framing error
Figure 14.9 Example of SCIF Receive Operation (Example with 8-Bit Data, Parity, One Stop Bit, LSB-First Transfer) 5. When modem control is enabled, the RTS signal is output when SCFRDR is empty. When RTS is 0, reception is possible. When RTS is 1, this indicates that SCFRDR is full and reception is not possible. Figure 14.10 shows an example of the operation when modem control is used.
Rev. 2.00 Mar 09, 2006 page 604 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Start bit Parity bit Start bit
Serial data
0
D0
D1
D2
D7
0/1
1
0
RTS
Figure 14.10 Example of Operation Using Modem Control (RTS RTS) RTS 14.3.3 Multiprocessor Communication Function
The multiprocessor communication function performs serial communication using a multiprocessor format, in which a multiprocessor bit is added to the transfer data, in asynchronous mode. Use of this function enables data transfer to be performed among a number of processors sharing a serial communication line. When multiprocessor communication is carried out, each receiving station is addressed by a unique ID code. The serial communication cycle consists of two cycles: an ID transmission cycle which specifies the receiving station, and a data transmission cycle. The multiprocessor bit is used to differentiate between the ID transmission cycle and the data transmission cycle. The transmitting station first sends the ID of the receiving station with which it wants to perform serial communication as data with a 1 multiprocessor bit added. It then sends transmit data as data with a 0 multiprocessor bit added. The receiving stations skip the data until data with a 1 multiprocessor bit is sent. When data with a 1 multiprocessor bit is received, each receiving stations compares that data with its own ID. The station whose ID matches then receives the data sent next. Stations whose ID does not match continue to skip the data until data with a 1 multiprocessor bit is again received. In this way, data communication is carried out among a number of processors. Figure 14.11 shows an example of inter-processor communication using a multiprocessor format.
Rev. 2.00 Mar 09, 2006 page 605 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Transmitting station Serial communication line
Receiving station A (ID = 01)
Receiving station B (ID = 02)
Receiving station C (ID = 03)
Receiving station D (ID = 04)
Serial data
H'01 (MPB = 1) ID transmission cycle: Receiving station specification
H'AA (MPB = 0) Data transmission cycle: Data transmission to receiving station specified by ID
Legend MPB: Multiprocessor bit
Figure 14.11 Example of Inter-Processor Communication Using Multiprocessor Format (Transmission of Data H'AA to Receiving Station A) Transmit/Receive Formats: There are four transmit/receive formats. When the multiprocessor format is specified, the parity bit specification is invalid. For details, see table 14.10. Clock: See the section on asynchronous mode. Data Transmit/Receive Operations * SCI Initialization See the section on asynchronous mode. * Multiprocessor Serial Data Transmission Figure 14.12 shows a sample flowchart for multiprocessor serial data transmission. Use the following procedure for multiprocessor serial data transmission after enabling the SCIF for transmission.
Rev. 2.00 Mar 09, 2006 page 606 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization Start of transmission
1
1. PFC initialization: Set the TxD pin, and the SCK pin if necessary, with the PFC. 2. SCIF status check and transmit data write: Read the serial status 1 register (SC1SSR) and check that the TDFE bit is set to 1, then write transmit data to the transmit FIFO data register (SCFTDR). Set the MPBT bit to 0 or 1 in SC1SSR. Finally, clear the TDFE and TEND flags to 0 after reading 1 from them. The number of data bytes that can be written is {16 - (transmit trigger set number)}. 3. Serial transmission continuation procedure: To continue serial transmission, read 1 from the TDFE bit to confirm that writing is possible, then write data to SCFTDR, and then clear the TDFE bit to 0. (Checking and clearing of the TDFE bit is automatic when the DMAC is activated by a transmit-FIFO-data-empty interrupt (TXI) request, and data is written to SCFTDR.) 4. Break output at the end of serial transmission: To output a break in serial transmission, clear the port data register (DR) to 0, then clear the TE bit to 0 in SCSCR, and set the TxD pin as an output port with the PFC. In steps 2 and 3, the number of transmit data bytes that can be written can be ascertained from the number of transmit data bytes in SCFTDR indicated in the upper 8 bits of the FIFO data count register (SCFDR).
Read TDFE bit in SC1SSR
2 No
TDFE = 1? Yes Write {16 - (transmit trigger set number)} bytes of transmit data to SCFTDR, and set MPBT in SC2SSR Clear TDFE and TEND flags to 0
End of transmission? 3 Yes Read TEND bit in SC2SSR
No
TEND = 1? Yes Break output? Yes Clear DR to 0 Clear TE bit to 0 in SCSCR, and set TxD pin as output port with PFC 4
No
No
End of transmission
Figure 14.12 Sample Multiprocessor Serial Transmission Flowchart
Rev. 2.00 Mar 09, 2006 page 607 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
In serial transmission, the SCIF operates as described below. 1. When data is written to SCFTDR, the SCIF transfers the data to SCTSR and starts transmitting. Check that the TDFE flag is set to 1 in SC1SSR before writing transmit data to SCFTDR. The number of data bytes that can be written is at least {16 - (transmit trigger set number)}. 2. When data is transferred from SCFTDR to SCTSR and transmission is started, transmit operations are performed continually until there is no transmit data left in SCFTDR. If the number of data bytes in SCFTDR falls to or below the transmit trigger number set in SCFCR during transmission, the TDFE flag is set to 1. If the TIE bit setting in SCSCR is 1 at this time, a transmit-FIFO-data-empty interrupt (TXI) is requested. The serial transmit data is sent from the TxD pin in the following order. a. Start bit: One 0-bit is output. b. Transmit data: 8-bit or 7-bit data is output in LSB-first or MSB-first order according to the setting of the TLM bit in SC2SSR. c. Multiprocessor bit: One multiprocessor bit (MPBT value) is output. d. Stop bit(s): One or two 1-bits (stop bits) are output. e. Mark state: 1 is output continuously until the start bit that starts the next transmission is sent. 3. The SCIF checks for transmit data in SCFTDR at the timing for sending the stop bit. If there is data in SCFTDR, it is transferred to SCTSR, the stop bit is sent, and then serial transmission of the next frame is started. If there is no transmit data in SCFTDR, the TEND flag is set to 1 in SC1SSR, the stop bit is sent, and then the line goes to the mark state in which 1 is output continuously. Figure 14.13 shows an example of SCIF operation for transmission using a multiprocessor format.
Rev. 2.00 Mar 09, 2006 page 608 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Multiproces- Stop Start sor bit bit bit Multiproces- Stop sor bit bit
1 Serial data
Start bit
Data
1
0
D0
D1
D7
0/1
1
0
D0
D1
D7
0/1
1
Idle state (mark state)
TDFE
TEND TXI interrupt TXI interrupt request request Data written to SCFTDR and TDFE flag cleared to 0 by TXI interrupt handler
One frame
Figure 14.13 Example of SCIF Transmit Operation (Example with 8-Bit Data, Multiprocessor Bit, One Stop Bit, LSB-First Transfer) * Multiprocessor Serial Data Reception Figure 14.14 shows a sample flowchart for multiprocessor serial reception. Use the following procedure for multiprocessor serial data reception after enabling the SCIF for reception.
Rev. 2.00 Mar 09, 2006 page 609 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization Start of reception
1
1. PFC initialization: Set the RxD pin, and the SCK pin if necessary, with the PFC. 2. ID reception cycle: Set the MPIE bit to 1 in SCSCR. 3. SCIF status check, ID reception and comparison: Read SC1SSR and check that the RDF bit is set to 1, then read the receive data in the receive FIFO data register (SCFRDR) and compare it with this station's ID. If the data is not this station's ID, set the MPIE bit to 1 again, and clear the RDF bit to 0. If the data is this station's ID, clear the RDF bit to 0. 4. Receive error handling and break detection: Read the ER, BRK, FER, and DR flags in SC1SSR and the ORER flag in SC2SSR to check whether a receive error has occurred. If a receive error has occurred, read the ER, BRK, FER, and DR flags in SC1SSR and the ORER flag in SC2SSR to identify the error. After performing the appropriate error handling, ensure that ER, BRK, DR, and ORER are all cleared to 0. The setting of the EI bit in SC2SSR determines whether reception is continued or halted when the ORER bit is set to 1. In the case of a framing error, a break can be detected by reading the value of the RxD pin. 5. SCIF status check and receive data read: Read the serial status 1 register (SC1SSR) and check that RDF = 1, then read receive data from the receive FIFO data register (SCFRDR).
Set MPIE bit to 1 in SCSCR Read ER, BRK, FER, and DR bits in SC1SSR, and ORER bit in SC2SSR BRK DR ER ORER = 1? No Read RDF flag in SC1SSR No RDF = 1? Yes Read receive data from SCFRDR, and clear RDF flag to 0 in SC1SSR No This station's ID? Yes Read BRK and DR bits in SC1SSR, and ER bit in SC2SSR BRK DR ER = 1? No Read RDF flag in SC1SSR RDF = 1? Yes Read receive data from SCFRDR No All data received? Yes Clear RE bit to 0 in SCSCR End of reception No 5 Yes 4 3
2
Yes
Error handling
Figure 14.14 Sample Multiprocessor Serial Reception Flowchart (1)
Rev. 2.00 Mar 09, 2006 page 610 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Error handling
No
1. Whether a framing error has occurred in the receive data read from SCFRDR can be ascertained from the FER bit in SC1SSR. 2. When a break signal is received, receive data is not transferred to SCFRDR while the BRK flag is set. However, note that the last data in SCFRDR is H'00 and the break data in which a framing error occurred is stored. However, note that the H'00 break data in which a framing error occurred is stored as the last data in SCFRDR.
ORER = 1? Yes Overrun error handling
No
BRK = 1? Yes Clear RE bit to 0 in SCSCR
No
DR = 1? Yes Read receive data from SCFRDR 1
No
FER = 1? Yes Framing error handling 2
No
All data read? Yes Clear ORER, BRK, DR, and ER flags to 0
End
Figure 14.14 Sample Multiprocessor Serial Reception Flowchart (2)
Rev. 2.00 Mar 09, 2006 page 611 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Figure 14.15 shows an example of SCIF operation for multiprocessor format reception.
Start bit Stop Start bit Data (Data1) MPB bit Stop MPB bit
1 Serial data
Data (ID1)
1 Idle state (mark state)
0
D0
D1
D7
1
1
0
D0
D1
D7
0
1
MPIE
RDF
SCFRDR value
ID1
RXI interrupt request (multiprocessor interrupt) MPIE = 0
SCFRDR data read and RDF flag cleared to 0 by RXI interrupt handler
As data is not this station's ID, MPIE bit is set to 1 again
RXI interrupt request is not generated, and SCFRDR retains its state
(a) Data does not match station's ID
1 Serial data
Start bit
Data (ID2)
Stop Start bit Data (Data2) MPB bit
Stop MPB bit
1 Idle state (mark state)
0
D0
D1
D7
1
1
0
D0
D1
D7
0
1
MPIE
RDF
SCFRDR value
ID1
ID2
Data2
RXI interrupt request (multiprocessor interrupt) MPIE = 0
SCFRDR data read and RDF flag cleared to 0 by RXI interrupt handler
As data matches this station's ID, reception continues and data is received by RXI interrupt handler
MPIE bit set to 1 again
(b) Data matches station's ID
Figure 14.15 Example of SCIF Receive Operation (Example with 8-Bit Data, Multiprocessor Bit, One Stop Bit, LSB-First Transfer)
Rev. 2.00 Mar 09, 2006 page 612 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.3.4
Operation in Synchronous Mode
In synchronous mode, data is transmitted or received in synchronization with clock pulses, making it suitable for high-speed serial communication. Inside the SCIF, the transmitter and receiver are independent units, enabling full-duplex communication using a common clock. Both the transmitter and the receiver also have a 16-stage FIFO buffer structure, so that data can be read or written during transmission or reception, enabling continuous data transfer. Figure 14.16 shows the general format for synchronous serial communication.
One unit of transfer data (character or frame) * Serial clock *
LSB
MSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Don't care
Serial data
Don't care
Bit 0
Note: * High except in continuous transmission/reception
Figure 14.16 Data Format in Synchronous Communication (Example of LSB-First Transfer) In synchronous serial communication, data on the communication line is output from one fall of the serial clock to the next. Data is guaranteed valid at the rise of the serial clock. In serial communication, each character is output starting with the LSB and ending with the MSB, or vice versa, according to the setting of the TLM bit in the serial status 2 register (SC2SSR). After the last data is output, the communication line remains in the state of the last data. In synchronous mode, the SCIF receives data in synchronization with the rise of the serial clock.
Rev. 2.00 Mar 09, 2006 page 613 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Transmit/Receive Format: A fixed 8-bit data format is used. No parity or multiprocessor bits are added. Clock: Either an internal clock generated by the built-in baud rate generator or an external serial clock input at the SCK pin can be selected, according to the setting of the C/A bit in SCSMR and the CKE1 and CKE0 bits in SCSCR. For details of SCIF clock source selection, see table 14.9. When the SCIF is operated on an internal clock, the serial clock is output from the SCK pin. Eight serial clock pulses are output in the transfer of one character, and when no transmission/reception is performed the clock is fixed high. In receive-only operation, however, the SCIF receives two characters as one unit, and so a 16-pulse serial clock is output. To perform single-character receive operations, an external clock should be selected as the clock source. Transmit/Receive Operations * SCIF Initialization (Synchronous Mode) Before transmitting and receiving data, it is necessary to clear the TE and RE bits to 0 in the serial control register (SCSCR), then initialize the SCIF as described below. When the operating mode, communication format, etc., is changed, the TE and RE bits must be cleared to 0 before making the change using the following procedure. When the TE bit is cleared to 0, the TDFE flag is set to 1 and the transmit shift register (SCTSR) is initialized. Note that clearing the RE bit to 0 does not change the contents of the RDF, PER, FER, and ORER flags, or the receive FIFO data register (SCFRDR). Figure 14.17 shows a sample SCIF initialization flowchart.
Rev. 2.00 Mar 09, 2006 page 614 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization Clear TE and RE bits to 0 in SCSCR Clear TFRST and RFRST bits to 1 in SCFCR Set RIE, TIE, MPIE, CKE1, and CKE0 bits in SCSCR (leaving TE and RE bits cleared to 0) Set data transmit/receive format in SCSMR Set value in SCBRR Wait No
1. Set the clock selection in SCSCR. Be sure to clear bits RIE, TIE, MPIE, TE, and RE to 0. 2. Set the transmit/receive format in the serial mode register (SCSMR). 3. Write a value corresponding to the bit rate into the bit rate register (SCBRR). (Not necessary if an external clock is used.)
1
2
4. Wait at least one bit interval, then set the TE bit or RE bit to 1 in SCSCR. Also set the RIE, TIE, and MPIE bits. Setting the TE and RE bits simultaneously enables the TxD and RxD pins to be used.
3
1-bit interval elapsed? Yes Set RTRG1-0 bits and TTRG1-0 bits in SCFCR, and clear TFRST and RFRST bits to 0 Set TE or RE bit to 1 in SCSCR, and set RIE, TIE, and MPIE bits End
4
Figure 14.17 Sample SCIF Initialization Flowchart
Rev. 2.00 Mar 09, 2006 page 615 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
* Serial Data Transmission (Synchronous Mode) Figure 14.18 shows a sample flowchart for serial transmission. Use the following procedure for serial data transmission after enabling the SCIF for transmission.
Initialization 1 1. PFC initialization: Set the TxD pin, and the SCK pin if necessary, with the PFC. 2. SCIF status check and transmit data write: Read SC1SSR and check that TDFE =1, then write transmit data to the transmit FIFO data register (SCFTDR) and clear the TDFE flag to 0. 3. Serial transmission continuation procedure: To continue serial transmission, read 1 from the TDFE flag to confirm that writing is possible, then write data to SCFTDR, and then clear the TDFE flag to 0.
Start of transmission
Read TDFE flag in SC1SSR
2 No
TDFE = 1? Yes Write transmit data to SCFTDR and clear TDFE flag to 0 in SC1SSR
All data transmitted? Yes Read TEND flag in SC1SSR
No 3
TEND = 1? Yes Clear TE bit to 0 in SCSCR
No
End
Figure 14.18 Sample Serial Transmission Flowchart
Rev. 2.00 Mar 09, 2006 page 616 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
In serial transmission, the SCIF operates as described below. 1. When data is written to the transmit FIFO data register (SCFTDR), the SCIF transfers the data from SCFTDR to the transmit shift register (SCTSR), and starts transmitting. Check that the TDFE flag is set to 1 in the serial status 1 register (SC1SSR) before writing transmit data to SCFTDR. The number of data bytes that can be written is at least {16 - (transmit trigger set number)}. 2. When data is transferred from SCFTDR to SCTSR and transmission is started, transmit operations are performed continually until there is no transmit data left in SCFTDR. If the number of data bytes in SCFTDR falls to or below the transmit trigger number set in the FIFO control register (SCFCR) during transmission, the TDFE flag is set. If the TIE bit setting in the serial control register (SCSCR) is 1 at this time, a transmit-FIFO-data-empty interrupt (TXI) is requested. When clock output mode has been set, the SCIF outputs eight serial clock pulses for one unit of data. When use of an external clock has been specified, data is output in synchronization with the input clock. The serial transmit data is sent from the TxD pin starting with the LSB (bit 0) or MSB (bit 7) according to the setting of the TLM bit in the serial status 2 register (SC2SSR). 3. The SCIF checks for transmit data in SCFTDR at the timing for sending the last bit. If there is transmit data in SCFTDR, it is transferred to SCTSR and then serial transmission of the next frame is started. If there is no transmit data in SCFTDR, the TEND flag is set to 1 in the serial status 1 register (SC1SSR), the last bit is sent, and then the transmit data pin (TxD) holds its state. 4. After completion of serial transmission, the SCK pin is fixed high. Figure 14.19 shows an example of SCIF operation in transmission.
Rev. 2.00 Mar 09, 2006 page 617 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Transfer direction Serial clock LSB Serial data Bit 0 Bit 1 MSB Bit 7 Bit 0 Bit 1 Bit 6 Bit 7
TDFE
TEND TXI interrupt request Data written to SCFTDR and TDFE flag cleared to 0 by TXI interrupt handler One frame TXI interrupt request
Figure 14.19 Example of SCIF Transmit Operation (Example of LSB-First Transfer) * Serial Data Reception (Synchronous Mode) Figure 14.20 shows a sample flowchart for serial reception. Use the following procedure for serial data reception after enabling the SCIF for reception. When changing the operating mode from asynchronous to synchronous without resetting SCFRDR and SCFTDR by means of SCIF initialization, be sure to check that the ORER, PER3 to PER0, and FER3 to FER0 flags are all cleared to 0. The RDF flag will not be set if any of flags FER3 to FER0 or PER3 to PER0 are set to 1, and neither transmit nor receive operations will be possible.
Rev. 2.00 Mar 09, 2006 page 618 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization
1
1. PFC initialization: Set the RxD pin, and the SCK pin if necessary, with the PFC. 2. Receive error handling: If a receive error occurs, read the ORER flag in SC2SSR, and after performing the appropriate error handling, clear the ORER flag to 0. Transmission/reception cannot be resumed if the ORER flag is set to 1. 2 3. SCIF status check and receive data read: Read the serial status 1 register (SC1SSR) and check that RDF = 1, then read receive data from the receive FIFO data register (SCFRDR) and clear the RDF flag to 0. Transition of the RDF flag from 0 to 1 can also be identified by an RXI interrupt. 4. Serial reception continuation procedure: To continue serial reception, read at least the receive trigger set number of data bytes from SCFRDR, and write 0 to the RDF flag after reading 1 from it. The number of receive data bytes in SCFRDR can be ascertained by reading the lower 8 bits of the FIFO data count register (SCFDR). (The RDF bit is cleared automatically when the DMAC is activated by an RXI interrupt and the SCFRDR value is read.)
Start of reception
Read ORER flag in SC2SSR
ORER = 1? No
Yes
Error handling 3
Read RDF flag in SC1SSR
No
RDF = 1? Yes Read receive data from SCFRDR, and clear RDF flag to 0 in SC1SSR 4
No
All data received? Yes Clear RE bit to 0 in SCSCR
End of reception
Figure 14.20 Sample Serial Reception Flowchart (1)
Rev. 2.00 Mar 09, 2006 page 619 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Error handling
No
ORER = 1? Yes Overrun error handling
Clear ORER flag to 0 in SC2SSR
End
Figure 14.20 Sample Serial Reception Flowchart (2) In serial reception, the SCIF operates as described below. 1. The SCIF performs internal initialization in synchronization with serial clock input or output. 2. The received data is stored in the receive shift register (SCRSR) in LSB-to-MSB order or MSB-to-LSB order according to the setting of the RLM bit in SC2SSR. After reception, the SCIF checks whether the receive data can be transferred from SCRSR to the receive FIFO data register (SCFRDR). If this check is passed, the receive data is stored in SCFRDR. If a receive error is detected in the error check, the operation is as shown in table 14.11. Neither transmit nor receive operations can be performed subsequently when a receive error has been found in the error check. Also, as the RDF flag is not set to 1 when receiving, the flag must be cleared to 0. 3. If the RIE bit setting in the serial control register (SCSCR) is 1 when the RDF flag is set to 1, a receive-FIFO-data-full interrupt (RXI) is requested. If the RIE bit setting in SCRSR is 1 when the ORER flag is set to 1, a receive-error interrupt (ERI) is requested. Figure 14.21 shows an example of SCIF operation in reception.
Rev. 2.00 Mar 09, 2006 page 620 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Transfer direction Serial clock
Serial data
Bit 7
Bit 0
Bit 7
Bit 0
Bit 1
Bit 6
Bit 7
RDF
ORER RXI interrupt request Data read from SCFRDR and RDF flag cleared to 0 by RXI interrupt handler One frame RXI interrupt request ERI interrupt request due to overrun error
Figure 14.21 Example of SCIF Receive Operation (Example of LSB-First Transfer) * Simultaneous Serial Data Transmission and Reception (Synchronous Mode) Figure 14.22 shows a sample flowchart for simultaneous serial transmit and receive operations. Use the following procedure for simultaneous serial data transmit and receive operations after enabling the SCIF for transmission and reception.
Rev. 2.00 Mar 09, 2006 page 621 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Initialization Start of transmission/ reception
1
1. PFC initialization: Set the TxD and RxD pins, and the SCK pin if necessary, with the PFC. 2. SCIF status check and transmit data write: Read SC1SSR and check that the TDFE flag is set to 1, then write transmit data to SCFTDR and clear the TDFE flag to 0. Transition of the TDFE flag from 0 to 1 can also be identified by a TXI interrupt. 3. Receive error handling: If a receive error occurs, read the ORER flag in SC2SSR, and after performing the appropriate error handling, clear the ORER flag to 0. Transmission/reception cannot be resumed if the ORER flag is set to 1. 4. SCIF status check and receive data read: Read SC1SSR and check that the RDF flag is set to 1, then read receive data from SCFRDR and clear the RDF flag to 0. Transition of the RDF flag from 0 to 1 can also be identified by an RXI interrupt. 5. Serial transmission/reception continuation procedure: To continue serial transmission/reception, finish reading the RDF flag, reading SCFRDR, and clearing the RDF flag to 0, before the MSB (bit 7) of the current frame is received. Also, before the MSB (bit 7) of the current frame is transmitted, read 1 from the TDFE flag to confirm that writing is possible, then write data to SCFTDR and clear the TDFE flag to 0. Note: When switching from transmitting or receiving to simultaneous transmitting and receiving, first clear the TE bit and RE bit to 0, then set the TE bit and RE bit to 1 simultaneously.
Read TDFE flag in SC1SSR No
2
TDFE = 1? Yes Write transmit data to SCFTDR and clear TDRE flag to 0 in SC1SSR
Read ORER flag in SC2SSR Yes 3 No Error handling
ORER = 1?
Read RDF flag in SC1SSR No
RDF = 1? Yes Read receive data from SCFRDR, and clear RDF flag to 0 in SC1SSR 4
No
All data transferred? Yes Clear TE and RE bits to 0 in SCSCR
5
End of transmission/ reception
Figure 14.22 Sample Flowchart for Serial Data Transmission and Reception
Rev. 2.00 Mar 09, 2006 page 622 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.3.5
Use of Transmit/Receive FIFO Buffers
The SCIF has independent 16-stage FIFO buffers for transmission and reception. The configuration of these buffers is shown in figure 14.23.
TxD RxD
SCTSR
P P/G
SCRSR
PF
SCFTDR 1st stage 2nd stage 3rd stage
SCFRDR 1st stage 2nd stage 3rd stage
Error counter
SC1SSR PER3-PER0 FER3-FER0
16th stage
16th stage Data counter SCFDR T3-T0 R3-R0
SCFER ED15-ED0
Transmit data writes by CPU or DMAC
Receive data reads by CPU or DMAC
Figure 14.23 Transmit/Receive FIFO Configuration
Rev. 2.00 Mar 09, 2006 page 623 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
In Serial Data Transmit Operations: In transmission, when transmit data is written to the transmit FIFO by the CPU or DMAC and the TE bit is set to 1 in the serial control register (SCSCR), the data is first transferred to the transmit shift register (SCTSR) in the order of writing to the transmit FIFO, a parity bit is added by the parity generator (P/G), and then serial data is transmitted from the TxD pin. Each time data is written into the transmit FIFO, the value in bits T4 to T0 in the FIFO data count register (SCFDR) is incremented, and each time data is transferred to SCTSR the value in bits T4 to T0 is decremented. The current number of data bytes in the transmit FIFO can thus be found by reading bits T4 to T0 in SCFDR. A value of H'10 in bits T4 to T0 means that data has been written into all 16 stages of the transmit FIFO. If additional data is written to the FIFO in this state, bits T4 to T0 will not be incremented and the written data will be lost. When the transmit trigger number is set and transmit data is written to the FIFO by the DMAC, care must be taken not to write data exceeding the number of empty bytes in SCFTDR indicated by the FIFO control register (SCFCR) (see section 14.2.10). In Serial Data Receive Operations: In reception, serial data input from the RxD pin is first captured in the receive shift register (SCRSR) in the order specified by the RLM bit in the serial status 2 register (SC2SSR). A parity bit check is carried out, and if there is a parity error the P (parity error) flag for that data is set to 1. A stop bit check is also performed, and if a framing error is found the F (framing error) flag for that data is set to 1. The receive FIFO buffer has a 10-bit configuration, with the P and F flags for each 8-bit data unit stored together with that data. * Receive FIFO Control in Normal Operation Receive data held in the receive FIFO buffer is read by the CPU or DMAC. Each time data is transferred from SCRSR to the receive FIFO, the value in bits R4 to R0 in SCFDR is incremented, and each time the CPU or DMAC reads receive data from the receive FIFO, the value in bits R4 to R0 is decremented. The current number of data bytes in the receive FIFO can thus be found by reading bits R4 to R0 in SCFDR. A value of H'10 in bits R4 to R0 means that receive data has been transferred to all 16 stages of the receive FIFO. If the next serial receive operation is completed before the CPU or DMAC reads data from the receive FIFO, an overrun error will result and the serial data will be lost. If receive FIFO data is read when the value of bits R4 to R0 is H'00, an undefined value will be returned.
Rev. 2.00 Mar 09, 2006 page 624 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
* Receive FIFO Control in Error Data Reception When data is transferred from SCRSR to the receive FIFO, the P and F flags are also transferred. If either of these flags is set to 1, the error counter is incremented and the corresponding bit (PER3 to PER0, FER3 to FER0) is updated in the serial status 1 register (SC1SSR). The error counter is decremented if the P or F flag is 1 when data in the receive FIFO is read by the CPU or DMAC. The settings of the P and F flags for the read receive data are also reflected in the PER and FER flags in SC1SSR. PER and FER are set when data containing a parity error or framing error is read from the receive FIFO; they are not set when serial data containing a parity error or framing error is received from the RxD pin. PER and FER are cleared when data with no parity error or framing error is read from the receive FIFO. This data is transferred to the receive FIFO even if it contains a parity error or framing error. Whether or not the receive operation is to be continued at this point can be specified with the EI bit in SC2SSR. If the EI bit is set to 1, specifying continuation of the receive operation, receive data is still transferred sequentially to the receive FIFO after an error occurs. The stage of the 16-stage FIFO buffer in which the data with the error is located can be determined by reading bits ED15 to ED0 in the FIFO error register (SCFER). When the receive trigger number is set and receive data is read from the receive FIFO by the DMAC, care must be taken not to read data exceeding the receive trigger number indicated by the FIFO control register (SCFCR) (see section 14.2.10). * Receive FIFO Control by DR Flag When a number of data bytes equal to or exceeding the receive trigger number have been received, a receive data read request is issued to the CPU or DMAC by means of an RXI interrupt (RDF only). However, an RXI interrupt is not requested if all reception has been completed with fewer than the receive trigger number of data bytes having been received. In this case, the DR flag is set and an ERI interrupt is requested 16 etu after reception of the last data is completed. The CPU should therefore read bits R4 to R0 in SCFDR to find the number of data bytes left in the receive FIFO, and read all the data in the FIFO. Note: With an 8-bit, 1-stop-bit format, one etu is equivalent to 1.6 frames. etu: Elementary time unit = sec/bit
Rev. 2.00 Mar 09, 2006 page 625 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.3.6
Operation in IrDA Mode
In IrDA mode, the waveform of TxD/RxD transmit/receive data is modified to comply with the IrDA 1.0 infrared communication specification. This makes it possible to carry out infrared transmission and reception conforming to the IrDA 1.0 standard by connecting an infrared transmission/reception transceiver/receiver. In the IrDA 1.0 specification, communication is initially executed at 9600 bps, and then the transfer rate can be changed as required. However, the communication speed is not changed automatically in this module. When executing communication, therefore, it is necessary to check the communication speed and have the appropriate speed set in this module by software. Note: In IrDA mode, reception is not possible when the TE bit is set to 1 (enabling communication) in the serial control register (SCSCR). When performing reception, the TE bit in SCSCR must be cleared to 0. Transmission: In the case of a serial output signal (UART frame) from the SCIF, the waveform is corrected and the signal is converted to an IR frame serial output signal by the IrDA module as shown in figure 14.24. When the serial data is 0, if the PSEL bit is 0 in the IrDA mode register (SCIMR) a pulse of 3/16 the IR frame bit width is generated and output, and if the PSEL bit is 1 a pulse of 3/16 the bit width of the bit rate set in bits ICK3 to 0 in the serial mode register (SCSMR) is generated and output. When the serial data is 1, a pulse is not output. An infrared LED is driven by a signal demodulated to a 3/16 width. Reception: Pulses of 3/16 the received IR frame bit width are converted to UART frames after demodulation as shown in figure 14.24. Demodulation to 0 is executed for pulse output and demodulation to 1 when there is no pulse output.
Rev. 2.00 Mar 09, 2006 page 626 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
UART frame Start bit Data Stop bit
0
1
0
1
0
0
1
1
0
1
Transmission
Reception IR frame Start bit Data Stop bit
0
1
0
1
0
0
1
1
0
1
3/16 bit cycle pulse width Bit cycle
Figure 14.24 IrDA Mode Transmit/Receive Operations Pulse Width Selection: In transmission, the IR frame pulse width can be selected as either 3/16 of the transmission bit rate or a smaller pulse width by means of the PSEL bit in the IrDA mode register (SCIMR). The SCIF includes a baud rate generator that generates the transmit frame bit rate and a baud rate generator that generates the IRCLK signal for varying the pulse width. When the PSEL bit is cleared to 0 in SCIMR, a width of 3/16 the bit rate set in the bit rate register (SCBRR) is output as the IR frame pulse width. As the pulse width is the direct infrared emission time; if the user wishes to minimize the pulse width in order to reduce power consumption, the PSEL bit should be set to 1 in SCIMR and a setting should also be made in bits ICK3 to ICK0 in the serial mode register (SCSMR) to generate the IRCLK signal, resulting in output with the minimum settable pulse width.
Rev. 2.00 Mar 09, 2006 page 627 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
The minimum IR frame pulse width must be 3/16 of the 115.2 kbps bit rate (= 1.63 sec). With this minimum pulse width, IRCLK = 921.6 kHz, and so the setting for bits ICK3 to ICK0 to give the minimum settable pulse width is given by the following equation.
N P 2 x IRCLK -1
P: Operating clock frequency IRCLK: 921.6 kHz (fixed) N: Set value of ICK3 to ICK0 (0 N 15)
For example, when P = 20 MHz, N = 10. Table 14.12 shows the settings of bits ICK3 to ICK0 that can be used to obtain the minimum pulse width for various operating frequencies.
Rev. 2.00 Mar 09, 2006 page 628 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Table 14.12 Bits ICK3 to ICK0 and Operating Frequencies in IrDA mode (When PSEL = 1)
Operating Frequency P (MHz) 2 3 5 6 8 10 12 14 16 18 20 21 22 23 24 25 26 27 28 1 1 0 1 1 0 0 1 1 0 1 Setting of Bits ICK3 to ICK0 in SCSMR ICK3 0 ICK2 0 ICK1 0 ICK0 0 1 0 1 0 1 0 1 0 1 0 1 1 0 1 1 0 0 1
Rev. 2.00 Mar 09, 2006 page 629 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.4
SCIF Interrupt Sources and the DMAC
The SCIF has four interrupt sources: the break interrupt (BRI) request, receive-error interrupt (ERI) request, receive-FIFO-data-full interrupt (RXI) request, and transmit-FIFO-data-empty interrupt (TXI) request. Table 14.13 shows the interrupt sources and their relative priorities. The interrupt sources can be enabled or disabled with the TIE or RIE bit in SCSCR. Each kind of interrupt request is sent to the interrupt controller independently. When the TDFE flag is set to 1 in the serial status 1 register (SC1SSR), a TXI interrupt is requested. A TXI interrupt request can activate the DMAC to perform data transfer. The TDFE bit is cleared to 0 automatically when all writes to the transmit FIFO data register (SCFTDR) by the DMAC are completed. When the RDF flag is set to 1 in SC1SSR, an RXI interrupt is requested. An RXI interrupt request can activate the DMAC to perform data transfer. The RDF bit is cleared to 0 automatically when all receive FIFO data register (SCFRDR) reads by the DMAC are completed. When the ER flag is set to 1, an ERI interrupt is requested. The DMAC cannot be activated by an ERI interrupt request. When the BRK flag is set to 1, a BRI interrupt is requested. The DMAC cannot be activated by a BRI interrupt request. A TXI interrupt indicates that transmit data can be written, and an RXI interrupt indicates that there is receive data in SCFRDR. Table 14.13 SCIF Interrupt Sources
Interrupt Source ERI RXI BRI TXI Description Receive error (ER) Receive data full (RDF) or data ready (DR) Break (BRK) Transmit data FIFO empty (TDFE) DMAC Activation Not possible Possible (RDF only) Not possible Possible Priority on Reset Release High Low
Rev. 2.00 Mar 09, 2006 page 630 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
14.5
Usage Notes
The following points should be noted when using the SCIF. SCFTDR Writing and the TDFE Flag: The TDFE flag in the serial status 1 register (SC1SSR) is set when the number of transmit data bytes written in the transmit FIFO data register (SCFTDR) has fallen to or below the transmit trigger number set by bits TTRG1 and TTRG0 in the FIFO control register (SCFCR). After TDFE is set, transmit data up to the number of empty bytes in SCFTDR can be written, allowing efficient continuous transmission. However, if the number of data bytes written in SCFTDR is equal to or less than the transmit trigger number, the TDFE flag will be set to 1 again after being read as 1 and cleared to 0. TDFE clearing should therefore be carried out when SCFTDR contains more than the transmit trigger number of transmit data bytes. The number of transmit data bytes in SCFTDR can be found from the upper 8 bits of the FIFO data count register (SCFDR). Simultaneous Multiple Receive Errors: If a number of receive errors occur at the same time, the state of the status flags in SC1SSR and SC2SSR is as shown in table 14.14. If there is an overrun error, data is not transferred from the receive shift register (SCRSR) to the receive FIFO data register (SCFRDR), and the receive data is lost. Table 14.14 SC1SSR/SC2SSR Status Flags and Transfer of Receive Data
SC1SSR/SC2SSR Status Flags Receive Errors Overrun error Framing error Parity error Overrun error + framing error Overrun error + parity error Framing error + parity error Overrun error + framing error + parity error RDF 1 0 0 1 1 0 1 ORER 1 0 0 1 1 0 1 FER 0 1 0 1 0 1 1 PER 0 0 1 0 1 1 1 Receive Data Transfer SCRSR SCFRDR x O O x x O x
Notes: O: Receive data is transferred from SCRSR to SCFRDR. x : Receive data is not transferred from SCRSR to SCFRDR.
Rev. 2.00 Mar 09, 2006 page 631 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Break Detection and Processing: Break signals can be detected by reading the RxD pin directly when a framing error (FER) is detected. In the break state the input from the RxD pin consists of all 0s, so the FER flag is set and the parity error flag (PER) may also be set. Note that although the SCIF stops transferring receive data to SCFRDR after receiving a break, the receive operation continues, so if the FER and BRK flags are cleared to 0 they will be set to 1 again. Sending a Break Signal: The TxD pin is a general I/O pin whose input/output direction and level are determined by the I/O port data register (DR) and the control register (CR) of the pin function controller (PFC). This fact can be used to send a break signal. The DR value substitutes for the mark state until the PFC setting is made. The initial setting should therefore be as an output port outputting 1. To send a break signal during serial transmission, clear DR, then set the TxD pin as an output port with the PFC. When the TE bit is cleared to 0, the transmitter is initialized regardless of the current transmission state. Receive Error Flags and Transmit Operations (Synchronous Mode Only): Transmission cannot be started when any of the receive error flags (ORER, PER3 to PER0, FER3 to FER0) is set to 1, even if the TDFE flag is set to 1. Be sure to clear the receive error flags to 0 before starting transmission. Note also that the receive error flags are not cleared to 0 by clearing the RE bit to 0. Receive Data Sampling Timing and Receive Margin in Asynchronous Mode: In asynchronous mode, the SCIF operates on a base clock with a frequency of 16, 8, or 4 times the transfer rate. In reception, the SCIF synchronizes internally with the fall of the start bit, which it samples on the base clock. Receive data is latched at the rising edge of the eighth, fourth, or second base clock pulse. The timing is shown in figure 14.25.
Rev. 2.00 Mar 09, 2006 page 632 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
16 clocks 8 clocks
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5
Base clock -7.5 clocks Receive data (RxD) Start bit +7.5 clocks
D0
D1
Synchronization sampling timing
Data sampling timing
Figure 14.25 Receive Data Sampling Timing in Asynchronous Mode (Using base clock with frequency of 16 times the transfer rate, sampled in 8th clock cycle) The receive margin in asynchronous mode can therefore be expressed as shown in equation (1).
M = 0.5 - 1 D - 0.5 (1 + F) x 100% - (L - 0.5) F - 2N N
................. ............ (1)
M: N: D: L: F:
Receive margin (%) Ratio of clock frequency to bit rate (N = 16, 8, or 4) Clock duty cycle (D = 0 to 1.0) Frame length (L = 9 to 12) Absolute deviation of clock frequency
From equation (1), if F = 0 and D = 0.5, the receive margin is 46.875%, as given by equation (2). When D = 0.5, F = 0, and N = 16:
M = (0.5 - 1/(2 x 16)) x 100% = 46.875%...................................................................................................... (2)
This is a theoretical value. A reasonable margin to allow in system designs is 20% to 30%. When Using Synchronous External Clock Mode * Do not set TE or RE to 1 until at least 4 peripheral operating clock cycles after external clock SCK has changed from 0 to 1. * Only set both TE and RE to 1 when external clock SCK is 1.
Rev. 2.00 Mar 09, 2006 page 633 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
* In reception, note that if RE is cleared to 0 from 2.3 to 3.5 peripheral operating clock cycles after the rising edge of the RxD D7 bit SCK input, RDF will be set to 1 but copying to SCFRDR will not be possible. When Using Synchronous Internal Clock Mode: In reception, note that if RE is cleared to zero 1.5 peripheral operating clock cycles after the rising edge of the RxD D7 bit SCK output, RDF will be set to 1 but copying to SCFRDR will not be possible. When Using the DMAC: When an external clock source is used as the serial clock, the transmit clock should not be input until at least 5 P clock cycles after SCFTDR is updated by the DMAC. Incorrect operation may result if the transmit clock is input within 4 P cycles after SCFTDR is updated. (See figure 14.26.) When performing SCFRDR reads by the DMAC, be sure to set the relevant SCIF receive-FIFOdata-full interrupt (RXI) as an activation source.
SCK t TDFE
TXD
D0
D1
D2
D3
D4
D5
D6
Figure 14.26 Example of Synchronous Transmission by DMAC SCFRDR Reading and the RDF Flag: The RDF flag in the serial status 1 register (SC1SSR) is set when the number of receive data bytes in the receive FIFO data register (SCFRDR) has become equal to or greater than the receive trigger number set by bits RTRG1 and RTRG0 in the FIFO control register (SCFCR). After RDF is set, receive data equivalent to the trigger number can be read from SCFRDR, allowing efficient continuous reception. However, if the number of data bytes in SCFRDR is equal to or greater than the trigger number, the RDF flag will be set to 1 again if it is cleared to 0. RDF should therefore be cleared to 0 after being read as 1 after receive data has been read to reduce the number of data bytes in SCFRDR to less than the trigger number.
Rev. 2.00 Mar 09, 2006 page 634 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
The number of receive data bytes in SCFRDR can be found from the lower 8 bits of the FIFO data count register (SCFDR). SCFRDR Reading when Overrun Occurs: If a receive operation is continued despite the fact that the receive FIFO data register (SCFRDR) contains 16 bytes of data, overrun will occur. If SCFRDR is read in this state, the data that caused the overrun is read in the 17th read. The value returned in the 18th and subsequent reads will be undefined. Also note that, from the first SCFRDR read onward, the number of receive data bytes in SCFRDR indicated by the lower 8 bits of the FIFO data count register (SCFDR) is one more than the actual number of receive data bytes.
Rev. 2.00 Mar 09, 2006 page 635 of 906 REJ09B0292-0200
Section 14 Serial Communication Interface with FIFO (SCIF)
Rev. 2.00 Mar 09, 2006 page 636 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Section 15 Serial I/O with FIFO (SIOF)
15.1 Overview
The serial I/O with FIFO functions mainly as an interface between the chip and a codec or modem analog front-end. 15.1.1 Features
The serial I/O has the following features: * Full-duplex operation Independent transmit/receive registers and independent transmit/receive clocks * Primary data transmit/receive FIFO/Double-buffered transmit/receive ports Continuous data transmission/reception possible * Interval transfer mode and continuous transfer mode * Memory-mapped receive data register, transmit data register, serial control register, and serial status register, receive control data register, transmit control data register, FIFO control register, FIFO data count register With the exception of SIRSR and SITSR, these registers are memory-mapped and can be accessed by a MOV instruction. * Choice of 8- or 16-bit data length * Data transfer communication by means of polling or interrupts Data transfer can be monitored by polling the receive data register full flag (RDRF), the receive data register empty flag (RDRE), the receive control data register full flag (RCD), and the transmit control data register empty flag (TCD). Interrupt requests can be generated during data transfer by setting the receive interrupt request flag and the transmit interrupt request flag. * Either MSB-first or LSB transfer can be selected for data I/O operations. Figure 15.1 shows a block diagram of the serial I/O with FIFO.
Rev. 2.00 Mar 09, 2006 page 637 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
16bits Peripheral bus
SISTR SIRDR SICTR SIFCR SIFDR SITDR
SIRCDR Bit counter I/O control unit MSB/LSB Conversion circuit SIRSR selector
SITCDR
MSB/LSB Conversion circuit SITSR Serial I/O with FIFO module (SIOF)
SRXD SIRDR: SIRCDR: SIRSR: SITDR: SITCDR:
SRCK SRS STS STCK SITSR: SISTR: SICTR: SIFCR: SIFDR:
STXD
Receive data register Receive control data register Receive shift register Transmit data register Transmit control data register
Transmit shift register Serial status register Serial control register FIFO control register FIFO data count register
Figure 15.1 SIOF Block Diagram Table 15.1 shows the functions of the external pins. Table 15.1 Serial I/O with FIFO (SIOF) External Pins
Name Serial receive data input pin Serial receive clock input pin Serial reception synchronization input pin Serial transmit data output pin Serial transmit clock input pin Pin SRxD0 SRCK0 SRS0 STxD0 STCK0 I/O Input Input Input Output Input I/O Function Serial data input port Serial receive clock port Serial reception synchronization input port Serial data output port Serial transmit clock port Serial transmission synchronization input/output port
Serial transmission synchronization STS0 input/output pin Rev. 2.00 Mar 09, 2006 page 638 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
15.2
Register Configuration
Table 15.2 shows the SIOF's registers. Table 15.2 Register Configuration
Register Receive shift register Receive data register Transmit shift register Transmit data register Serial control register Serial status register Receive control data register Transmit control data register FIFO control register Abbreviation SIRSR0 SIRDR0 SITSR0 SITDR0 SICTR0 SISTR0 SIRCDR SITCDR SIFCR R/W -- R -- R/W R/W R/(W)* R R/W R/W R Initial Value -- Address -- Access Size (Bits) -- 8, 16, 32 -- 8, 16, 32 8, 16, 32 8, 16, 32 8, 16, 32 8, 16, 32 8, 16, 32 8, 16, 32
Not H'FFFFFC00 specified -- H'0000 H'0000 H'0002 H'0000 H'0000 H'0000 H'0000 -- H'FFFFFC02 H'FFFFFC04 H'FFFFFC06 H'FFFFFC0C H'FFFFFC0E H'FFFFFC08 H'FFFFFC0A
FIFO data count register SIFDR
Note: * Only 0 should be written, to clear flags (after reading 1 from the flag).
15.2.1
Receive Shift Register (SIRSR)
Bit: Initial value: R/W: 15 -- -- 14 -- -- 13 -- -- ... ... ... ... -- -- -- -- -- -- -- -- 3 2 1 0
SIRSR is a 16-bit register used to receive serial data. The data is fetched in MSB first from the SRxD pin in synchronization with the fall of the serial receive clock (SRCK), and is shifted into SIRSR. The data length is set by the transmit/receive data length select bit (DL) in the corresponding serial control register (SICTR). If the DL bit is cleared to 0 (data length 8 bits), the receive data is fetched to the lower 8 bits, and the upper 8 bits are cleared to 0. When data transfer to SIRSR is completed, the data contents are automatically transferred to the receive data register (SIRDR), and the receive data register full flag (RDRF) is set in the serial status register (SISTR), based on the settings of the receive FIFO watermark bits (RFWM3 to RFWM0) in SIFCR.
Rev. 2.00 Mar 09, 2006 page 639 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
When transfer of control data to SIRSR is completed, the data contents are automatically transferred to the receive control data register (SIRCDR), and the receive control data register full flag (RCD) is set in SISTR. If the next data word input operation ends before the RDRF flag is cleared, an overrun error occurs, the receive overrun error flag (RERR) is set in SISTR, and an overrun error signal is sent to the interrupt controller (INTC). The data in SIRSR overwrites the data in SIRDR. If SIRCDR contains valid control data, SIRCDR is overwritten after the next control data input operation completes. 15.2.2 Receive Data Register (SIRDR)
Bit: Initial value: R/W: 15 0 R 14 0 R 13 0 R ... ... ... ... 0 R 0 R 0 R 0 R 3 2 1 0
SIRDR is a 16-bit x 16-stage FIFO register that stores primary receive data. When primary data is transferred from SIRSR to SIRDR, the receive data register full flag (RDRF) is set in the serial status register (SISTR), based on the settings of RFWM3 to RFWM0 in SIFCR. If the receive interrupt enable flag (RIE) is set in SICTR, a receive-data-full interrupt (RDFI) request is sent to the interrupt controller (INTC) and the DMA controller (DMAC). When the flag is cleared, this interrupt request signal is not generated. When SIRDR is read by the DMAC, the RDRF flag is cleared automatically if the value is less than or equal to the setting of bits RFWM3 to RFWM0 in SIFCR. When SIRDR is reset, its status is empty. The status of SIRDR is also empty when the value of the receive FIFO data registry reset bit (RFRST) in SIFCR is 1. Note: Do not read from SIRDR when it contains no primary receive data (when the value of the receive data register data count bits 4 to 0 (R4 to R0) in the FIFO data count register (SIFDR) is 00000).
Rev. 2.00 Mar 09, 2006 page 640 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
15.2.3
Transmit Shift Register (SITSR)
Bit: Initial value: R/W: 15 -- -- 14 -- -- 13 -- -- ... ... ... ... -- -- -- -- -- -- -- -- 3 2 1 0
SITSR is a 16-bit register used to transmit serial data. The contents of this register are shifted in MSB-first or LSB-first order, based on the LM bit in SIFCR, in synchronization with the rising edge of the serial transmit clock (STCK), and output from the serial transmit data STXD pin. The transfer data length is set by the DL bit in SICTR. The transmit mode bit (TRMD) in SIFCR controls the LSB of the transmitted primary data or control data. When the TRMD bit is cleared to 0 and the DL bit is cleared to 0 (8-bit data length), the lower 8 bits in the transmit data register (SITDR) are output. When the DL bit is set to 1 (16-bit data length), all 16 bits in SITDR are output. Setting the TRMD bit to 1 causes the LSB of the primary data to be output as 0. Performing write access to the transmit control data register (SITCDR) in this case, if the DL bit is cleared to 0, causes the lower 8 bits in SITDR to be output, with the LSB as 1, after which the lower 8 bits in SITCDR are output. If the DL bit is set to 1, all 16 bits in SITDR are output, with the LSB as 1, after which all 16 bits in SITCDR are output. When transmit primary data with a value less than or equal to the transmit FIFO watermark bits (TFWM3 to TFWM0) in SIFCR is transferred from SITDR to SITSR, the transmit data register empty flag (TDRE) is set in SISTR. If output of the next primary data begins when the amount of transmit primary data in SITDR is 0, an underrun error occurs, the transmit underrun error flag (TERR) in SISTR is set, and an error interrupt request is sent to the INTC. 15.2.4 Transmit Data Register (SITDR)
Bit: Initial value: R/W: 15 0 W 14 0 W 13 0 W ... ... ... ... 0 W 0 W 0 W 0 W 3 2 1 0
SITDR is a 16-bit x 16-stage FIFO register that stores primary transmit data. Data should be written to SITDR when the transmit data register empty flag (TDRE) is set to 1 in SISTR. If data is written to SITDR when TDRE is 0, a SITDR overflow may occur. When transmit primary data
Rev. 2.00 Mar 09, 2006 page 641 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
with a value less than or equal to the setting of TFWM3 to TFWM0 in SIFCR is transferred from SITDR to SITSR, TDRE is set in SISTR. If at this point the transmit interrupt enable flag (TIE) is set, a transmit-data-empty interrupt (TDEI) request is sent to the INTC and DMAC. If TIE is cleared, this interrupt request is not generated. When the DMAC writes to SITDR data with a value greater than the setting of TFWM3 to TFWM0 in SIFCR, the TDRE flag is cleared automatically. The TDRE flag is set only by hardware. When SITDR is reset, its status is empty. The status of SITDR is also empty when the value of the transmit FIFO data registry reset bit (TFRST) in SITDR is 1. Note: Do not write to SITDR when it is full of primary transmit data (when the value of the transmit data register data count bits 4 to 0 (T4 to T0) in SIFDR is 10000). Data should be written to SITDR in the size specified by the setting of the DL bit in SICTR. Always set the TE bit to 1 before writing to this register. 15.2.5 Serial Control Register (SICTR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 -- 0 R 6 TM 0 R/W 13 -- 0 R 5 SE 0 R/W 12 -- 0 R 4 DL 0 R/W 11 -- 0 R 3 TIE 0 R/W 10 DMACE 0 R/W 2 RIE 0 R/W 9 TCIE 0 R/W 1 TE 0 R/W 8 RCIE 0 R/W 0 RE 0 R/W
SICTR is a 16-bit register used to set parameters for serial port control. SICTR is initialized to H'0000 by a reset. When modifying bit 4, 5, 6,or 10 (DMACE, TM, SE, or DL), TE and RE (bit 1, 0) should be cleared to 0 beforehand. Bits 15 to 11--Reserved: These bits are always read as 0. The write value should always be 0. Bit 10--DMAC Activation Enable (DMACE): Specifies whether the DMAC is activated by interrupts triggered by the RDRF and TDRE bits in SISTR. Set this bit to 1 if SIRCDR and SITCDR are used. This will cause interrupts triggered by the RDRF and TDRE bits in SISTR to be processed by the DMAC and interrupts triggered by the RCD and TCD bits in SISTR to be processed by the CPU.
Rev. 2.00 Mar 09, 2006 page 642 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Clear this bit to 0 if SIRCDR and SITCDR are not used, or if all interrupts triggered by the RDRF, TDRE, RCD and TCD bits in SISTR are to be processed by the CPU. The initial value of this bit is 0.
Bit 10: DMACE 0 1 Description DMAC is activated by RDRF and TDRE interrupts DMAC is not activated by RDRF and TDRE interrupts (Initial value)
Bit 9--Transmit-Control-Data-Register-Empty Interrupt Enable (TCIE): Enables the transmitcontrol-data-register-empty interrupt. The initial value of this bit is 0.
Bit 9: TCIE 0 1 Description Transmit-control-data-register-empty interrupt disabled Transmit-control-data-register-empty interrupt enabled (Initial value)
Bit 8--Receive-Control-Data-Register-Full Interrupt Enable (RCIE): Enables the receive-controldata-register-full interrupt. The initial value of this bit is 0.
Bit 8: RCIE 0 1 Description Receive-control-data-register-full interrupt disabled Receive-control-data-register-full interrupt enabled (Initial value)
Bit 7--Reserved: This bit is always read as 0. The write value should always be 0. Bit 6--Transfer Mode Control (TM): Specifies whether the transmission synchronization signal is to be input from an external source or generated internally by the chip. When this flag is cleared, the transmission synchronization signal is STS pin input. When this flag is set, the transmission synchronization signal is generated by the chip, and is output to an external device from the STS pin. This bit does not affect reception.
Bit 6: TM 0 1 Description External signal input from STS pin is used as transmission start indication (Initial value) Internal signal output from STS pin is used as transmission start indication
Note: If the transmit mode bit (TRMD) in SIFCR is set to 1, this bit must be cleared to 0. If TM is set to 1 and SE is set to 1 (interval mode), output of the sync signal stops at the point at which bits T4 to T0 in SIFDR are cleared to 0 (data count of transmit data register is zero). If TE remains set to 1 and data is written to SITDR, output of the sync signal resumes when the value of T4 to T0 in SIFDR becomes H'01 or above. Rev. 2.00 Mar 09, 2006 page 643 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 5--Synchronization Signal Enable (SE): Specifies whether the synchronization signals are to be used for all serial data transfers, or only for the first transfer. When this bit is cleared to 0, the synchronization signals (SRS and STS) are necessary only for the first data transfer, and are not required for subsequent transfers. When this bit is set to 1, the synchronization signals are necessary for all data transfers.
Bit 5: SE 0 1 Description Continuous mode: SRS and STS are used only for the first data transfer (Initial value) Interval mode: SRS and STS are used for all data transfers
Note: If TRMD in SIFCR is set to 1, this bit must be cleared to 1. When TM is cleared to 0 and SE is cleared to 0, after data is input SRS/STS once nothing further should be input to SRS/STS between the start and completion of transmission/receiving (transmit FIFO empty/receive FIFO full).
Bit 4--Transmit/Receive Data Length Select (DL): Specifies the serial I/O module's transfer data length. The initial value of this bit is 0, indicating an 8-bit data length. When an 8-bit data length is specified, the lower 8 bits in the receive shift register, receive data register, transmit shift register, transmit data register, receive control data register, and transmit control data register are used.
Bit 4: DL 0 1 Description 8-bit transfer data length 16-bit transfer data length (Initial value)
Bit 3--Transmit Interrupt Enable (TIE): Enables the transmit-data-empty interrupt. The initial value of this bit is 0.
Bit 3: TIE 0 1 Description Transmit interrupt disabled Transmit interrupt enabled (Initial value)
Bit 2--Receive Interrupt Enable (RIE): Enables the receive-data-full interrupt. The initial value of this bit is 0.
Bit 2: RIE 0 1 Description Receive interrupt disabled Receive interrupt enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 644 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 1--Enables data transmission. When this flag is cleared, the STXD pin goes to the highimpedance state. When TM is set to 1, the STS pin also goes to the high-impedance state.
Bit 1: TE 0 1 Description Transmission disabled: STxD pin goes to high-impedance state (Initial value) When TM is set to 1, STS pin goes to high-impedance state Transmission enabled
Bit 0--Receive Enable (RE): Enables data reception.
Bit 0: RE 0 1 Description Reception disabled Reception enabled (Initial value)
15.2.6
Serial Status Register (SISTR)
Bit: Initial value: R/W: 15 -- 0 R 14 -- 0 R ... ... ... 9 TCD 1 8 RCD 0 ... ... ... 4 -- 0 R 3 0 2 0 1 1 0 RDRF 0
TERR RERR TDRE
... R/(W)* R/(W)* ...
R/(W)* R/(W)* R/(W)* R/(W)*
Note: * Only 0 should be written, to clear the flag.
SISTR is a 16-bit register that indicates the status of the serial I/O module. SISTR is initialized to H'0002 by a reset. When the TFRST bit in SIFCR is set to 1, the TERR and TDRE bits are also initialized. When the RFRST bit in SIFCR is set to 1, the RERR and RDRF bits are also initialized. Bits 15 to 4--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 645 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 9--Transmit Control Data Register Empty (TCD): This flag indicates when SITCDR is empty and can be written to.
Bit 9: TCD 0 Description SITCDR transmit data is valid TCD is cleared to 0 in the following cases: * 1 When 0 is written to TCD after reading TCD = 1 (Initial value) SITCDR transmit data is invalid TCD is set to 1 in the following cases: * * After data is transferred from SITCDR to SITSR When the processor is reset
Bit 8--Receive Control Data Register Full (RCD): This flag indicates when SIRCDR is in wait status.
Bit 8: RCD 0 Description SIRCDR receive data is invalid RCD is cleared to 0 in the following cases: * * 1 When 0 is written to RCD after reading RCD = 1 When the processor is reset (Initial value)
SIRCDR transmit data is valid RCD is set to 1 in the following cases: * After control data has been received normally and data has been transferred from SIRSR to SIRCDR
Bit 7 to 4--Reserved: This bit is always read as 0. The write value should always be 0. Bit 3--Transmit Underrun Error (TERR): Flag that indicates the occurrence of a transmit underrun.
Bit 3: TERR 0 Description Transmission is in progress, or has ended normally [Clearing conditions] * When 0 is written to the TERR bit after reading TERR = 1 * When the TFRST bit in SIFCR is set to 1 * When the processor enters the reset state 1 A transmit underrun error has occurred * When the amount of primary transmit data in SITDR is 0 and data is transferred from SITDR to SITSR using a transmit operation (Initial value)
Rev. 2.00 Mar 09, 2006 page 646 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 2--Receive Overrun Error (RERR): Flag that indicates the occurrence of a receive overrun.
Bit 2: RERR 0 Description Reception is in progress, or has ended normally [Clearing conditions] * * * 1 When 0 is written to the RERR bit after reading RERR = 1 When the RFRST bit in SIFCR is set to 1 When the processor enters the reset state (Initial value)
A receive overrun error has occurred RERR is set to 1 in the following cases: * When the amount of primary receive data in SIRDR is 16 and the next primary data receive operation completes
Bit 1--Transmit Data Register Empty (TDRE): Flag that indicates that primary data has been transferred from SITDR to SITSR and the amount of data inside SITDR is less than or equal to the setting of TFWM3 to TFWM0 in SIFCR.
Bit 1: TDRE 0 Description Indicates that primary send data exceeding the transmit FIFO watermark setting has been written to SITDR TDRE is cleared to 0 in the following cases: * When primary send data exceeding the setting of the transmit FIFO watermark bits has been written to SITDR and 0 is written to TDRE after reading TDRE = 1 When the DMAC has written primary send data exceeding the setting of the transmit FIFO watermark bits to SITDR
* 1
Indicates that the amount of primary send data in SITDR is less than or equal to the transmit FIFO watermark setting (Initial value) TDRE is set to 1 in the following cases: * * * When the amount of primary send data in SITDR is less than or equal to the transmit FIFO watermark setting When the TFRST bit in SIFCR is set to 1 When the processor is reset
Rev. 2.00 Mar 09, 2006 page 647 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 0--Receive Data Register Full (RDRF): Flag that indicates that SIRDR receive data is waiting.
Bit 0: RDRF 0 Description Indicates that the amount of primary receive data in SIRDR is less than the receive FIFO watermark setting (Initial value) RDRF is cleared to 0 in the following cases: * When the received primary data in SIRDR has been read to the point that the amount of remaining data is less than the receive FIFO watermark setting and 0 is written to RDRF after reading RDRF = 1 When the DMAC has read the received primary data in SIRDR to the point that the amount of remaining data is less than the receive FIFO watermark setting When the RFRST bit in SIFCR is set to 1 When the processor is reset
*
* * 1
Indicates that the amount of primary receive data in SIRDR is greater than or equal to the receive FIFO watermark setting RDRF is set to 1 in the following cases: * When the received primary data stored in SIRDR is greater than or equal to the receive FIFO watermark setting
15.2.7
Receive Control Data Register (SIRCDR)
Bit: Initial value: R/W: 15 0 R 14 0 R 13 0 R 12 0 R 11 0 R 10 0 R 9 0 R 8 0 R 7 0 R 6 0 R 5 0 R 4 0 R 3 0 R 2 0 R 1 0 R 0 0 R
SIRCDR is a register that stores receive control data. Received data is stored in SIRCDR as receive control data, synchronized with the timing used for transmission of transmit control data from SITCDR. The RCD bit in SISTR is set at the same time as control data is being transferred from SIRSR to SIRCDR. When the RCIE pin in SICTR is set, a receive-control-data-full interrupt request (RDFI) is sent to the INTC. No interrupt request signal is issued if the flag is cleared. SIRCDR is initialized to H'0000 by a reset. If the DL bit is cleared to 0 (data length 8 bits), the received control data is fetched to the lower 8 bits, and the upper 8 bits are cleared to 0.
Rev. 2.00 Mar 09, 2006 page 648 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
15.2.8
Transmit Control Data Register (SITCDR)
Bit: Initial value: 15 0 14 0 13 0 12 0 11 0 10 0 9 0 8 0 7 0 6 0 5 0 4 0 3 0 2 0 1 0 0 0
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
SITCDR is a register that stores transmit control data. Data should be written to SITCDR when the TCD bit is set to 1 in SISTR (SITCDR transmit data invalid). If data is written to SITCDR when TCD in SISTR is cleared to 0, the previous data will be overwritten. After writing transmit control data to SITCDR, 1 should be read from TCD in SISTR and then 0 written to it. This makes the transmit data in SITCDR valid and causes the transmit control data to be transmitted. After TRMD in SIFCR is set to 1 transmission starts, a read interrupt is issued to SITCDR. STS goes high and primary data bit 0 is transmitted as 1. When STS next goes high the control data stored in SITCDR is transferred to SITSR. If the TCD bit is 0 at this point, and TCD bit is set to 1. After this the control data previously transferred from SITCDR to SITSR is transmitted. If the TRMD bit is cleared to 0, no control data is transmitted even if data is written to SITCDR. If the TCD bit in SISTR is set to 1 and the TCIE bit in SICTR is set to 1, a transmit-control-dataempty interrupt (TDEI0) request is sent to the INTC. If the flag is cleared, this interrupt request is not generated. The TCD bit in SISTR is set only by hardware. SITCDR is initialized to H'0000 by a reset. 15.2.9 FIFO Control Register (SIFCR)
Bit: 15 14 13 12 11 10 TRMD LM Initial value: 0 0 0 0 0 0 9
RFR ST
8
7
6
5
4
3
2
1
0
TFR RFWM RFWM RFWM RFWM TFWM TFWM TFWM TFWM ST 3 2 1 0 3 2 1 0
0
0
0
0
0
0
0
0
0
0
R/W: R 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 R/W
SIFCR is a register used to perform software resets and to make threshold settings for SIRDR and SITDR.
Rev. 2.00 Mar 09, 2006 page 649 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
It also contains a bit used to select LSB first or MSB first when transmitting and receiving to match the connected codec, as well as a bit for controlling the LSB for transmitted primary data and control data. SIFCR is initialized to H'0000 by a reset. Note that the TE and RE bits in SICTR must be cleared to 0 before changing the values of bits 11 to 10 and 7 to 0 (TRMD, LM, RFWM3 to RFWM0, TFWM3 to TFWM0). Bit 15 to 12--Reserved: These bits are always read as 0. The write value should always be 0. Bit 11--Transfer Mode (TRMD): Controls the LSB (bit 0) for transmitted primary data and control data.
Bit 11: TRMD 0 1 Description Value stored in SITDR is always transmitted as LSB of primary data (Initial value) LSB of primary data is always transmitted as 0 However, the LSB is 1 when the primary data immediately precedes control data Note: If the TRMD bit is set to 1, in SICTR the TM bit (STS pin input) should be cleared to 0, the SE bit (interval mode) set to 1, and the LM bit (transmit/receive MSB format) cleared to 0. The sync signal output from the connected codec should be input to pins STS and SRS. The serial clock output from the connected codec should be input to pins STCK and SRCK.
Bit 10--LSB/MSB First Select (LM): Used to select LSB first or MSB first for transmitting and receiving.
Bit 10: LM 0 1 Description MSB first for transmitting and receiving LSB first for transmitting and receiving (Initial value)
Note: This bit must be cleared to 0 if the TRMD bit is set to 1.
Bit 9--Receive FIFO Data Register Reset (RFRST): Invalidates the primary receive data in SIRDR and resets it to empty status. Also initializes the RERR and RDRF bits in SISTR. Note that SICTR is not initialized, so receiving continues if the RE bit is set to 1.
Bit 9: RFRST 0 1 Note: Description Reset disabled Reset enabled Reset status persists while this bit is set to 1. Clear this bit to 0 to cancel reset status. (Initial value)
Rev. 2.00 Mar 09, 2006 page 650 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 8--Transmit FIFO Data Register Reset (TFRST): Invalidates the transmit data in SITDR and resets it to empty status. Also initializes the TERR and TDRE bits in SISTR. Note that SICTR is not initialized, so transmitting continues if the TE bit is set to 1.
Bit 8: TFRST 0 1 Description Reset disabled Reset enabled (Initial value)
Note: Reset status persists while this bit is set to 1. Clear this bit to 0 to cancel reset status.
Bit 7 to 4--Receive FIFO Watermark (RFWM3 to RFWM0): These bits are used to make threshold settings, which are used to set the RDRF bit in SISTR. When the amount of primary receive data in SIRDR is equal to or greater than the watermark setting, as shown in the table below, the RDRF bit is set to 1.
Bit 7: RFWM3 0 Bit 6: RFWM2 0 Bit 5: RFWM1 0 1 1 0 1 1 0 0 1 1 0 1 Bit 4: RFWM0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Watermark setting 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 (Initial value)
Rev. 2.00 Mar 09, 2006 page 651 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Bit 3 to 0-- Transmit FIFO Watermark (TFWM3 to TFWM0): These bits are used to make threshold settings, which are used to set the TDRE bit in SISTR. When the amount of primary send data in SITDR is less than or equal to the watermark setting, as shown in the table below, the TDRE bit is set to 1.
Bit 3: TFWM3 0 Bit 2: TFWM2 0 Bit 1: TFWM1 0 1 1 0 1 1 0 0 1 1 0 1 Bit 0: TFWM0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Watermark setting 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 (Initial value)
Rev. 2.00 Mar 09, 2006 page 652 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
15.2.10 FIFO Data Count Register (SIFDR)
Bit: Initial value: R/W: 15 0 R 14 0 R 13 0 R 12 0 R 11 0 R 10 0 R 9 0 R 8 0 R 7 0 R 6 0 R 5 0 R 4 T4 0 R 3 T3 0 R 2 T2 0 R 1 T1 0 R 0 T0 0 R
R4 R3 R2 R1 R0
SIFDR is a register that indicates the amount of primary data stored in SIRDR and SITDR. The upper 8 bits indicate the amount of primary receive data stored in SIRDR, and the lower 8 bits indicate the amount of primary transmit data stored in SITDR. SIFDR is initialized to H'0000 by a reset. Also, it can be initialized to H'0000 by setting bits RFRST and TFRST of SIFCR to 1. Bit 15 to 13--Reserved: These bits are always read as 0. Bit 12 to 8--Receive Data Register Data Count Bits 4 to 0 (R4 to R0): These bits indicate the amount of primary receive data stored in SIRDR. When the value of bits R4 to R0 is H'00 there is no primary receive data stored in SIRDR, and when the value is H'10 SIRDR is full. In addition to the initialized status mentioned above, bits R4 to R0 can be cleared to H'00 by reading all the primary receive data from SIRDR. Bit 7 to 5--Reserved: These bits are always read as 0. Bit 4 to 0--Transmit Data Register Data Count Bits 4 to 0 (T4 to T0): These bits indicate the amount of untransmitted primary data stored in SITDR. When the value of bits T4 to T0 is H'00 there is no primary transmit data waiting to be transmitted, and when the value is H'10 SITDR is full. In addition to the initialized status mentioned above, bits T4 to T0 can be cleared to H'00 by transmitting all the primary transmit data.
Rev. 2.00 Mar 09, 2006 page 653 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
15.3
15.3.1
Operation
Input when TRMD = 0 in SIFCR
Figure 15.2 shows interval transfer mode (SE set to 1 in SICTR) with MSB first (LM cleared to 0 in SIFCR). Figure 15.3 shows continuous transfer mode (SE cleared to 0 in SICTR) with MSB first (LM cleared to 0 in SIFCR).
Set to 1 when an amount of data equal to or greater than the setting of bits RFWM3 to RFWM0 in SIFCR is received
RDRF
Synchronous internal clock
SIRDR SIRSR SRCK SRS SRXD
A[7] A[6] A[5] A[0] Invalid Undefined A[7] A[7:6] A[7:1] A[7:0]
A[7:0] B[7]
B[7]
B[6]
Note: DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 0: MSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.2 Reception: Interval Transfer Mode/MSB First
Rev. 2.00 Mar 09, 2006 page 654 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Set to 1 when an amount of data equal to or greater than the setting of bits RFWM3 to RFWM0 in SIFCR is received
RDRF
Synchronous internal clock
SIRDR SIRSR SRCK SRS SRXD
A[7] A[6] A[5] A[0] B[7] Undefined A[7] A[7:6] A[7:1] A[7:0] B[7]
A[7:0] B[7:6] B[7:5]
B[6]
B[5]
B[4]
Note: DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode LM = 0: MSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.3 Reception: Continuous Transfer Mode/MSB First
Rev. 2.00 Mar 09, 2006 page 655 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Figure 15.4 shows interval transfer mode (SE set to 1 in SICTR) with LSB first (LM set to 1 in SIFCR). Figure 15.5 shows continuous transfer mode (SE cleared to 0 in SICTR) with LSB first (LM set to 1 in SIFCR).
Set to 1 when an amount of data equal to or greater than the setting of bits RFWM3 to RFWM0 in SIFCR is received
RDRF
Synchronous internal clock
SIRDR SIRSR SRCK SRS SRXD
A[0] A[1] A[2] A[7] Invalid Undefined A[0] A[0:1] A[0:6] A[0:7]
A[7:0] B[0]
B[0]
B[1]
Note: DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 1: LSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.4 Reception: Interval Transfer Mode/LSB First
Set to 1 when an amount of data equal to or greater than the setting of bits RFWM3 to RFWM0 in SIFCR is received
RDRF
Synchronous internal clock
SIRDR SIRSR SRCK SRS SRXD
A[0] A[1] A[2] A[7] B[0] Undefined A[0] A[0:1] A[0:6] A[0:7] B[0]
A[7:0] B[0:1] B[0:2]
B[1]
B[2]
B[3]
Note: DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode LM = 1: LSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.5 Reception: Continuous Transfer Mode/LSB First
Rev. 2.00 Mar 09, 2006 page 656 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
15.3.2
Output when TRMD = 0 in SIFCR
Figure 15.6 shows interval transfer mode when TM is cleared to 0 in SICTR and with MSB first. Figure 15.7 shows continuous transfer mode when TM is cleared to 0 in SICTR and with MSB first. Figure 15.8 shows interval transfer mode when TM is set to 1 in SICTR and with MSB first. Figure 15.9 shows continuous transfer mode when TM is set to 1 in SICTR and with MSB first.
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[7:0]
D[7:0] C[6:0] C[5:0]
D[7:0] C[0] D[7:0]
E[7:0] D[6:0]
C[7]
C[6]
C[5]
C[0]
D[7]
D[6]
Note: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 0: MSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.6 Transmission: Interval Transfer Mode (TM = 0 Mode)/MSB First
Rev. 2.00 Mar 09, 2006 page 657 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[7:0]
D[7:0] C[6:0] C[5:0]
D[7:0] C[0] D[7:0] D[6:0]
E[7:0] D[5:0] D[4:0]
C[7]
C[6]
C[5]
C[0]
D[7]
D[6]
D[5]
D[4]
Note: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode LM = 0: MSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.7 Transmission: Continuous Transfer Mode (TM = 0 Mode)/MSB First
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[7:0]
D[7:0] C[6:0] C[5:0]
D[7:0] C[1:0] C[0] D[7:0]
E[7:0] D[6:0] D[5:0]
C[7]
C[6]
C[5]
C[1]
C[0]
D[7]
D[6]
D[5]
Note: TM = 1: STS is output DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 0: MSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.8 Transmission: Interval Transfer Mode (TM = 1 Mode)/MSB First
Rev. 2.00 Mar 09, 2006 page 658 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[7:0]
D[7:0] C[6:0] C[5:0]
D[7:0] C[0] D[7:0] D[6:0]
E[7:0] D[5:0] D[4:0]
C[7]
C[6]
C[5]
C[0]
D[7]
D[6]
D[5]
D[4]
Note: TM = 1: STS is output DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode LM = 0: MSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.9 Transmission: Continuous Transfer Mode (TM = 1 Mode)/MSB First Figure 15.10 shows interval transfer mode when TM is cleared to 0 in SICTR and with LSB first. Figure 15.11 shows continuous transfer mode when TM is cleared to 0 in SICTR and with LSB first. Figure 15.12 shows interval transfer mode when TM is set to 1 in SICTR and with LSB first. Figure 15.13 shows continuous transfer mode when TM is set to 1 in SICTR and with LSB first.
Rev. 2.00 Mar 09, 2006 page 659 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[0:7]
D[7:0] C[1:7] C[2:7]
D[7:0] C[7] D[0:7]
E[7:0] D[1:7]
C[0]
C[1]
C[2]
C[7]
D[0]
D[1]
Note: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 1: LSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.10 Transmission: Interval Transfer Mode (TM = 0 Mode)/LSB First
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[0:7]
D[7:0] C[1:7] C[2:7]
D[7:0] C[7] D[0:7] D[1:7]
E[7:0] D[2:7] D[3:7]
C[0]
C[1]
C[2]
C[7]
D[0]
D[1]
D[2]
D[3]
Note: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer in start signal mode LM = 1: LSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.11 Transmission: Continuous Transfer Mode (TM = 0 Mode)/LSB First
Rev. 2.00 Mar 09, 2006 page 660 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[0:7]
D[7:0] C[1:7] C[2:7]
D[7:0] C[6:7] C[7] D[0:7]
E[7:0] D[1:7] D[2:7]
C[0]
C[1]
C[2]
C[6]
C[7]
D[0]
D[1]
D[2]
Note: TM = 1: STS is output DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 1: LSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.12 Transmission: Interval Transfer Mode (TM = 1 Mode)/LSB First
Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR
Cleared to 0 when an amount of data exceeding the setting of bits TFWM3 to TFWM0 in SIFCR has been written to SITDR
TDRE
Synchronous internal clock
SITDR SITSR STCK STS STXD
C[7:0] Undefined C[0:7]
D[7:0] C[1:7] C[2:7]
D[7:0] C[7] D[0:7] D[1:7]
E[7:0] D[2:7] D[3:7]
C[0]
C[1]
C[2]
C[7]
D[0]
D[1]
D[2]
D[3]
Note: TM = 1: STS is output DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode LM = 1: LSB first TRMD = 0: LSB of transmitted primary data is value in SITDR
Figure 15.13 Transmission: Continuous Transfer Mode (TM = 1 Mode)/LSB First 15.3.3 Output when TRMD = 1 in SIFCR
Figure 15.14 shows output timing when TM is set to 1 in SIFTR.
Rev. 2.00 Mar 09, 2006 page 661 of 906 REJ09B0292-0200
Set to 1 when an amount of data equal to or greater than the setting of bits RFWM3 to RFWM0 in SIFCR is received
RDRF Synchronous internal clock A[7:0] B[7:0] B[7:0]
SIRDR
SIRCDR A[7] A[7:1] A[7:0] B[7] B[7:1] B[7:0] C[7] C[7:1]
C[7:0] C[7:0]
SIRSR
Undefined
SRCK
Section 15 Serial I/O with FIFO (SIOF)
Rev. 2.00 Mar 09, 2006 page 662 of 906 REJ09B0292-0200
A[7] Set to 1 when the amount of data in SITDR is less than or equal to the setting of bits TFWM3 to TFWM0 in SIFCR A[6] A[0] Invalid B[7] B[6] B[0] Invalid C[7] C[6] C[0] Invalid E[7:0] E[7:0] F[7:0] F[7:0] F[7:0] Z[7:0] D[7:0] D[6:0] D[0] E[7:0] E[6:0] Z[7:0] E[0] Z[7:0] Z[7:0] Z[6:0] Z[7:0] Z[0] F[7:0] D[7] D[6] D[0] E[7] E[6] E[0] Z[7] Z[6] Z[0]
SRS
SRXD
TDRE Synchronous internal clock
SITDR
D[7:0]
SITCDR
SITSR
Undefined
STCK
Figure 15.14 Transmission: TRMD = 1 Mode
STS
STXD
Note: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode LM = 0: MSB first TRMD = 1: LSB of transmitted primary data is 0
Section 15 Serial I/O with FIFO (SIOF)
15.4
SIOF Interrupt Sources and DMAC
Each SIOF channel has four interrupt sources: the receive-overrun-error interrupt (RERI0) request, transmit-underrun-error interrupt (TERI0) request, receive-data-full interrupt/receive-control-dataregister-full interrupt (RDFI0) request, and transmit-data-empty interrupt/transmit-control-dataregister-empty interrupt (TDEI0) request. Table 15.3 shows the interrupt sources and their relative priorities. The RDFI0 and TDEI0 interrupts are enabled by the RIE, RCIE, TIE, and TCIE bits, respectively, in SICTR. The RERI0 and TERI0 interrupts cannot be disabled. An RDFI0 interrupt request is generated when the RDRF bit is set to 1 or the RCD bit is set to 1 in SISTR. The DMACE bit should be cleared to 0 in SICTR to have interrupts triggered by both the RDRF bit and the RCD bit processed by the CPU. In this case the CPU should process interrupts after reading SISTR and determining which bit triggered them. Set the DMACE bit to 1 in SICTR to have interrupts triggered by the RDRF bit processed by the DMAC and interrupts triggered by the RCD bit processed by the CPU. In addition, the priority of interrupts from SIOF should be set to a high level in order to activate the interrupt controller (INTC). This will cause interrupts triggered by the RDRF bit to be sent to the DMAC and interrupts triggered by the RCD bit to be sent to the INTC. The data in SIRDR is read and if the amount of primary data is less than the setting of bits RFWM3 to RFWM0 in SIFCR, RDRF is automatically cleared to 0. Interrupts triggered by the RCD bit cannot be processed by the DMAC. An TDEI0 interrupt request is generated when the TDRE bit is set to 1 or the TCD bit is set to 1 in SISTR. The DMACE bit should be cleared to 0 in SICTR to have interrupts triggered by both the TDRE bit and the TCD bit processed by the CPU. In this case the CPU should process interrupts after reading SISTR and determining which bit triggered them. Set the DMACE bit to 1 in SICTR to have interrupts triggered by the TDRE bit processed by the DMAC and interrupts triggered by the TCD bit processed by the CPU. In addition, the priority of interrupts from SIOF should be set to a high level in order to activate the INTC. This will cause interrupts triggered by the TDRE bit to be sent to the DMAC and interrupts triggered by the TCD bit to be sent to the INTC. The DMAC writes data to SIRDR and if the amount of primary data is equal to or greater than the setting of bits TFWM3 to TFWM0 in SIFCR, TDRE is automatically cleared to 0. Interrupts triggered by the TCD bit cannot be processed by the DMAC. When the RERR bit is set to 1 in SISTR, an RERI0 interrupt request is generated. When the TERR bit is set to 1 in SISTR, a TERI0 interrupt request is generated.
Rev. 2.00 Mar 09, 2006 page 663 of 906 REJ09B0292-0200
Section 15 Serial I/O with FIFO (SIOF)
Channel interrupt priority levels are set by means of the IRPE register, as described in section 5, Interrupt Controller (INTC). Table 15.3 SIOF Interrupt Sources
Interrupt Source Description RERI0 TERI0 RDFI0 TDEI0 Receive overrun error (RERR) Transmit underrun error (TERR) Receive data register full (RDRF)/ Receive Control Data Register Full (RCD) Transmit data register empty (TDRE)/ Transmit Control Data Register Empty (TCD) DMAC Activation Not possible Not possible Possible* Possible* Priority High Low
Note: * The interrupt sources that can activate the DMAC are receive data full (RDRF) and transmit data empty (TDRE). It is not possible for receive control data full (RCD) or transmit control data empty (TCD) to activate the DMAC. The DMAC should be used to process RDRF and TDRE interrupts when using SIRCDR and SITCDR, and the DMACE bit must be set to 1 in SICTR when using the CPU to process RCD and TCD interrupts. The DMACE bit should be cleared to 0 in SICTR if neither SIRCDR nor SITCDR is used and both RDRF and TDRE interrupts as well as RCD and TCD interrupts are to be processed by the CPU.
Rev. 2.00 Mar 09, 2006 page 664 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
Section 16 Serial I/O (SIO)
16.1 Overview
A two-channel simple synchronous serial I/O is provided on-chip. The serial I/O functions mainly as an interface between the chip and a codec or modem analog front-end. 16.1.1 Features
The serial I/O has the following features: * Full-duplex operation Independent transmit/receive registers and independent transmit/receive clocks * Double-buffered transmit/receive ports Continuous data transmission/reception possible * Interval transfer mode and continuous transfer mode * Memory-mapped receive register, transmit register, control register, and status register With the exception of SIRSR and SITSR, these registers are memory-mapped and can be accessed by a MOV instruction. * Choice of 8- or 16-bit data length * Data transfer communication by means of polling or interrupts Data transfer can be monitored by polling the receive data register full flag (RDRF) and transmit data register empty flag (TDRE) in the serial status register. Interrupt requests can be generated during data transfer by setting the receive interrupt request flag and transmit interrupt request flag. * MSB-first transfer between SIO and data I/O Figure 16.1 shows a block diagram of the serial I/O.
Rev. 2.00 Mar 09, 2006 page 665 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
Peripheral bus
16
SIRDR
SISTR SICTR Bit counter I/O control unit
SITDR
SIRSR
MSB LSB
SITSR
MSB LSB
Serial I/O module (SIO) SRxD SIRDR: SIRSR: SISTR: SICTR: SITDR: SITSR: SRCK SRS STS STCK STxD
Receive data register Receive shift register Serial status register Serial control register Transmit data register Transmit shift register
Figure 16.1 SIO Block Diagram
Rev. 2.00 Mar 09, 2006 page 666 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
Table 16.1 shows the functions of the external pins. As the channels are independent, the channel numbers are omitted from the signal names in the rest of this section. Table 16.1 Serial I/O (SIO) External Pins
Channel 1 Name Serial receive data input pin Serial receive clock input pin Serial reception synchronization input pin Serial transmit data output pin Serial transmit clock input pin Serial transmission synchronization input/output pin 2 Serial receive data input pin Serial receive clock input pin Serial reception synchronization input pin Serial transmit data output pin Serial transmit clock input pin Serial transmission synchronization input/output pin Pin SRxD1 SRCK1 SRS1 STxD1 STCK1 STS1 SRxD2 SRCK2 SRS2 STxD2 STCK2 STS2 I/O Input Input Input Output Input I/O Input Input Input Output Input I/O Function Serial data input port 1 Serial receive clock port 1 Serial reception synchronization input port 1 Serial data output port 1 Serial transmit clock port 1 Serial transmission synchronization input/output port 1 Serial data input port 2 Serial receive clock port 2 Serial reception synchronization input port 2 Serial data output port 2 Serial transmit clock port 2 Serial transmission synchronization input/output port 2
Note: In a reset, all pins are initialized to the high-impedance state.
Rev. 2.00 Mar 09, 2006 page 667 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.2
Register Configuration
Table 16.2 shows the SIO's registers. As the channels are independent, the channel numbers are omitted from the signal names in the rest of this section. Table 16.2 Register Configuration
Channel 1 Register Receive shift register 1 Receive data register 1 Transmit shift register 1 Transmit data register 1 Serial control register 1 Serial status register 1 2 Receive shift register 2 Receive data register 2 Transmit shift register 2 Transmit data register 2 Serial control register 2 Serial status register 2 Abbreviation SIRSR1 SIRDR1 SITSR1 SITDR1 SICTR1 SISTR1 SIRSR2 SIRDR2 SITSR2 SITDR2 SICTR2 SISTR2 R/W -- R -- R/W R/W R/(W)* -- R -- R/W R/W R/(W)* Initial Value -- H'0000 -- H'0000 H'0000 H'0002 -- H'0000 -- H'0000 H'0000 H'0002 Address -- -- Access Size (Bits) -- --
H'FFFFFC10 8, 16, 32 H'FFFFFC12 8, 16, 32 H'FFFFFC14 8, 16, 32 H'FFFFFC16 8, 16, 32 -- -- -- -- H'FFFFFC20 8, 16, 32 H'FFFFFC22 8, 16, 32 H'FFFFFC24 8, 16, 32 H'FFFFFC26 8, 16, 32
Note: * Only 0 should be written, to clear flags (after reading 1 from the flag).
Rev. 2.00 Mar 09, 2006 page 668 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.2.1
Receive Shift Register (SIRSR)
Bit: Initial value: R/W: 15 -- -- 14 -- -- 13 -- -- ... ... ... ... -- -- -- -- -- -- -- -- 3 2 1 0
SIRSR is a 16-bit register used to receive serial data. The data is fetched in MSB first from the SRxD pin in synchronization with the fall of the serial receive clock (SRCK), and is shifted into SIRSR. The data length is set by the transmit/receive data length select bit (DL) in the corresponding serial control register (SICTR). When data transfer to SIRSR is completed, the data contents are automatically transferred to the receive data register (SIRDR), and the receive data register full flag (RDRF) is set in the serial status register (SISTR). If the next data word input operation ends before the RDRF flag is cleared, an overrun error occurs, the receive overrun error flag (RERR) is set in SISTR, and an overrun error signal is sent to the interrupt controller (INTC). The data in SIRSR overwrites the data in SIRDR. 16.2.2 Receive Data Register (SIRDR)
Bit: Initial value: R/W: 15 0 R 14 0 R 13 0 R ... ... ... ... 0 R 0 R 0 R 0 R 3 2 1 0
SIRDR is a 16-bit register that stores serial receive data. When data is transferred from SIRSR to SIRDR, the receive data register full flag (RDRF) is set in the serial status register (SISTR). If the receive interrupt enable flag (RIE) is set in SICTR, a receive-data-full interrupt (RDFI) request is sent to the interrupt controller (INTC) and the DMA controller (DMAC). When the flag is cleared, this interrupt request signal is not generated. When SIRDR is read by the DMAC, the RDRF flag is cleared automatically. SIRDR is initialized to H'0000 by a reset.
Rev. 2.00 Mar 09, 2006 page 669 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.2.3
Transmit Shift Register (SITSR)
Bit: Initial value: R/W: 15 -- -- 14 -- -- 13 -- -- ... ... ... ... -- -- -- -- -- -- -- -- 3 2 1 0
SITSR is a 16-bit register used to transmit serial data. The contents of this register are shifted in MSB-first order in synchronization with the rising edge of the serial transmit clock (STCK), and output from the STxD pin. The transfer data length is set by the transmit/receive data length select bit (DL) in the serial control register (SICTR). When the DL bit is cleared to 0 (8-bit data length), the lower 8 bits of SITDR are output. When the serial transmission synchronization signal (STS) goes high, or the last data transmission ends without the synchronization enable (SE) bit being set in SICTR, the contents of the transmit data register (SITDR) are transferred to SITSR, and if TDRE is 0, TDRE is then set. If output of the next data begins before TDRE is cleared, an overrun error occurs, the transmit overrun error flag (TERR) is set in SISTR, and a transmit overrun error interrupt request is sent to the INTC. 16.2.4 Transmit Data Register (SITDR)
Bit: Initial value: R/W: 15 0 R/W 14 0 R/W 13 0 R/W ... ... ... ... 0 R/W 0 R/W 0 R/W 0 R/W 3 2 1 0
SITDR is a 16-bit register that stores serial transmit data. Data should be written to SITDR when the transmit data register empty flag (TDRE) is set to 1 in SISTR. If data is written to SITDR when TDRE is 0, the previous data will be overwritten. When STS goes high or data output from transmit shift register SITSR ends with the SE bit cleared to 0 in SICTR, the data in SITDR is automatically transferred to SITSR, and if TDRE is 0, TDRE is then set. If the transmit interrupt enable flag (TIE) is set, a transmit-data-empty interrupt (TDEI) request is sent to the INTC and DMAC. When TIE is cleared, this interrupt request is not generated. When the DMAC writes to SITDR, the TDRE flag is cleared automatically. The TDRE flag is set only by hardware. SITDR is initialized to H'0000 by a reset.
Rev. 2.00 Mar 09, 2006 page 670 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.2.5
Serial Control Register (SICTR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 -- 0 R 6 TM 0 R/W 13 -- 0 R 5 SE 0 R/W 12 -- 0 R 4 DL 0 R/W 11 -- 0 R 3 TIE 0 R/W 10 -- 0 R 2 RIE 0 R/W 9 -- 0 R 1 TE 0 R/W 8 -- 0 R 0 RE 0 R/W
SICTR is a 16-bit register used to set parameters for serial port control. SICTR is initialized to H'0000 by a reset. When modifying bit 4, 5, or 6 (TM, SE, or DL), TE and RE should be cleared to 0 beforehand. Bits 15 to 7--Reserved: These bits are always read as 0. The write value should always be 0. Bit 6--Transfer Mode Control (TM): Specifies whether the transmission synchronization signal is to be input from an external source or generated internally by the chip. When this flag is cleared, the transmission synchronization signal is STS pin input. When this flag is set, the transmission synchronization signal is generated by the chip, and is output to an external device from the STS pin. This bit does not affect reception.
Bit 6: TM 0 1 Description External signal input from STS pin is used as transmission start indication (Initial value) Internal signal output from STS pin is used as transmission start indication
Bit 5--Synchronization Signal Enable (SE): Specifies whether the synchronization signals are to be used for all serial data transfers, or only for the first transfer. When this bit is cleared to 0, the synchronization signals (SRS and STS) are necessary only for the first data transfer, and are not required for subsequent transfers. When this bit is set to 1, the synchronization signals are necessary for all data transfers.
Bit 5: SE 0 1 Description Continuous mode: SRS and STS are used only for the first data transfer (Initial value) Interval mode: SRS and STS are used for all data transfers Rev. 2.00 Mar 09, 2006 page 671 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
Bit 4--Transmit/Receive Data Length Select (DL): Specifies the serial I/O module's transfer data length. The initial value of this bit is 0, indicating an 8-bit data length. When an 8-bit data length is specified, the lower 8 bits of each I/O register are used.
Bit 4: DL 0 1 Description 8-bit transfer data length 16-bit transfer data length (Initial value)
Bit 3--Transmit Interrupt Enable (TIE): Enables the transmit-data-empty interrupt. The initial value of this bit is 0.
Bit 3: TIE 0 1 Description Transmit interrupt disabled Transmit interrupt enabled (Initial value)
Bit 2--Receive Interrupt Enable (RIE): Enables the receive-data-full interrupt. The initial value of this bit is 0.
Bit 2: RIE 0 1 Description Receive interrupt disabled Receive interrupt enabled (Initial value)
Bit 1--Transmit Enable (TE): Enables data transmission. When this flag is cleared, the STxD, STCK, and STS pins go to the high-impedance state.
Bit 1: TE 0 1 Description Transmission disabled: STxD, STCK, and STS pins go to high-impedance state (Initial value) Transmission enabled
Bit 0--Receive Enable (RE): Enables data reception. When this flag is cleared, the SRxD, SRCK, and SRS pins go to the high-impedance state.
Bit 0: RE 0 1 Description Reception disabled: SRxD, SRCK, and SRS pins go to high-impedance state (Initial value) Reception enabled
Rev. 2.00 Mar 09, 2006 page 672 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.2.6
Serial Status Register (SISTR)
Bit: Initial value: R/W: 15 -- 0 R 14 -- 0 R ... ... ... ... 4 -- 0 R 3 TERR 0 R/(W)* 2 RERR 0 R/(W)* 1 TDRE 1 R/(W)* 0 RDRF 0 R/(W)*
Note: * Only 0 should be written, to clear the flag.
SISTR is a 16-bit register that indicates the status of the serial I/O module. SISTR is initialized to H'0002 by a reset. Bits 15 to 4--Reserved: These bits are always read as 0. The write value should always be 0. Bit 3--Transmit Underrun Error (TERR): Flag that indicates the occurrence of a transmit underrun.
Bit 3: TERR 0 Description Transmission is in progress, or has ended normally [Clearing conditions] * * 1 When 0 is written to the TERR bit after reading TERR = 1 When the processor enters the reset state (Initial value)
A transmit underrun error has occurred TERR is set to 1 if data transmission is started while TDRE = 1
Bit 2--Receive Overrun Error (RERR): Flag that indicates the occurrence of a receive overrun.
Bit 2: RERR 0 Description Reception is in progress, or has ended normally [Clearing conditions] * * 1 When 0 is written to the RERR bit after reading RERR = 1 When the processor enters the reset state (Initial value)
A receive overrun error has occurred RERR is set to 1 if data reception ends while RDRF = 1
Rev. 2.00 Mar 09, 2006 page 673 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
Bit 1--Transmit Data Register Empty (TDRE): Flag that indicates that the SITDR register is empty and the next data can be written.
Bit 1: TDRE 0 Description SITDR transmit data is valid [Clearing conditions] * * 1 When 0 is written to the TDRE bit after reading TDRE = 1 When the DMAC writes data to SITDR (Initial value)
SITDR transmit data is invalid TDRE is set to 1 in the following cases: * * * When data is transferred from SITDR to SITSR
When the TE bit is cleared to 0 in the serial control register (SICTR) When the processor enters the reset state
Bit 0--Receive Data Register Full (RDRF): Flag that indicates that SIRDR receive data is waiting.
Bit 0: RDRF 0 Description SIRDR receive data is invalid [Clearing conditions] * * * * 1 When the DMAC reads data from SIRDR When 1 is read from RDRF and 0 is written When the RE bit is cleared to 0 in the serial control register (SICTR) When the processor enters the reset state (Initial value)
SIRDR receive data is valid RDRF is set to 1 when serial data reception ends normally and the data is transferred from SIRSR to SIRDR
Rev. 2.00 Mar 09, 2006 page 674 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.3
16.3.1
Operation
Input
Figure 16.2 shows interval transfer mode (SE set to 1 in SICTR), and figure 16.3 shows continuous transfer mode (SE cleared to 0 in SICTR).
RDRF
synchronous internal clock
SIRDR SIRSR SRCK SRS SRxD
A[7] A[6] A[5] A[1] A[0] Undefined A[7] A[7:6] A[7:1]
A[7:0]
A[7:0]
B[7]
Invalid
B[7]
Notes: DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode
Figure 16.2 Reception: Interval Transfer Mode
RDRF
synchronous internal clock
SIRDR SIRSR SRCK SRS SRxD
A[7] A[6] A[5] A[1] A[0] Undefined A[7] A[7:6] A[7:1]
A[7:0] A[7:0] B[7] B[7:6] B[7:5]
B[7]
B[6]
B[5]
Notes: DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode
Figure 16.3 Reception: Continuous Transfer Mode
Rev. 2.00 Mar 09, 2006 page 675 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.3.2
Output
Figure 16.4 shows interval transfer mode (SE set to 1 in SICTR) when TM is cleared to 0 in SICTR. Figure 16.5 shows continuous transfer mode (SE cleared to 0 in SICTR) when TM is cleared to 0 in SICTR. Figure 16.6 shows interval transfer mode (SE set to 1 in SICTR) when TM is set to 1 in SICTR. Figure 16.7 shows continuous transfer mode (SE cleared to 0 in SICTR) when TM is set to 1 in SICTR.
TDRE
synchronous internal clock
SITDR SITSR STCK STS STxD
Data C Undefined C[7:0] C[6:0] C[5:0] C[0] D[7:0] D[6:0]
C[7]
C[6]
C[5]
C[1]
C[0]
Invalid
D[7]
Notes: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode
Figure 16.4 Transmission: Interval Transfer Mode (TM = 0 Mode)
Rev. 2.00 Mar 09, 2006 page 676 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
TDRE
synchronous internal clock
SITDR SITSR STCK STS STxD
Data C Undefined C[7:0] C[6:0] C[5:0] C[0] D[7:0] D[6:0] D[5:0] D[4:0]
C[7]
C[6]
C[5]
C[1]
C[0]
D[7]
D[6]
D[5]
Notes: TM = 0: STS is input DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode
Figure 16.5 Transmission: Continuous Transfer Mode (TM = 0 Mode)
TDRE
synchronous internal clock
SITDR SITSR STCK STS STxD
Undefined
Data C C[7:0] C[6:0] C[5:0] C[0]
Data D D[7:0] D[6:0]
C[7]
C[6]
C[5]
C[1]
C[0]
Invalid
D[7]
Notes: TM = 1: STS is output DL = 0: 8-bit data transfer SE = 1: Synchronous transfer in start signal mode
Figure 16.6 Transmission: Interval Transfer Mode (TM = 1 Mode)
Rev. 2.00 Mar 09, 2006 page 677 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
TDRE
synchronous internal clock
SITDR SITSR
Undefined
Data C C[7:0] C[6:0] C[5:0] C[0] D[7:0] D[6:0] D[5:0] D[4:0]
STCK STS STxD
C[7] C[6] C[5] C[1] C[0] D[7] D[6] D[5]
Notes: TM = 1: STS is output DL = 0: 8-bit data transfer SE = 0: Asynchronous transfer, no start signal mode
Figure 16.7 Transmission: Continuous Transfer Mode (TM = 1 Mode)
Rev. 2.00 Mar 09, 2006 page 678 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
16.4
SIO Interrupt Sources and DMAC
Each SIO channel has four interrupt sources: the receive-overrun-error interrupt (RERI) request, transmit-underrun-error interrupt (TERI) request, receive-data-full interrupt (RDFI) request, and transmit-data-empty interrupt (TDEI) request. Table 16.3 shows the interrupt sources and their relative priorities. The RDFI and TDEI interrupts are enabled by the RIE and TIE bits, respectively, in SICTR. The RERI and TERI interrupts cannot be disabled. An RDFI interrupt request is generated when the RDRF bit is set to 1 in SISTR. RDFI can activate the DMA controller (DMAC) to read the data in SIRDR. RDRF is cleared to 0 automatically when the DMAC reads data from SIRDR. A TDEI interrupt request is generated when the TDRE bit is set to 1 in SISTR. TDEI can activate the DMAC to write the next data to SITDR. TDRE is cleared to 0 automatically when the DMAC writes data to SITDR. When TDEI and RDFI interrupt requests are handled by the DMAC, and not by the interrupt controller, a low priority level should be given to interrupts from the SIO to prevent the interrupt controller from operating. When the RERR bit is set to 1 in SISTR, an RERI interrupt request is generated. When the TERR bit is set to 1 in SISTR, a TERI interrupt request is generated. Channel interrupt priority levels are set by means of the IRPE register, as described in section 5, Interrupt Controller (INTC). Table 16.3 SIO Interrupt Sources
Interrupt Source RERI TERI RDFI TDEI Description Receive overrun error (RERR) Transmit underrun error (TERR) Receive data register full (RDRF) Transmit data register empty (TDRE) DMAC Activation Not possible Not possible Possible Possible Priority High Low
Rev. 2.00 Mar 09, 2006 page 679 of 906 REJ09B0292-0200
Section 16 Serial I/O (SIO)
Rev. 2.00 Mar 09, 2006 page 680 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Section 17 16-Bit Timer Pulse Unit (TPU)
17.1 Overview
An on-chip 16-bit timer pulse unit (TPU) is provided that comprises three 16-bit timer channels. 17.1.1 Features
The TPU has the following features: * Maximum 8-pulse input/output * A total of eight timer general registers (TGRs) are provided (four for channel 0 and two each for channels 1, and 2). Each register can be set independently as an output compare/input capture register. TGRC and TGRD for channel 0 can be used as buffer registers * Choice of seven or eight counter input clocks for each channel * The following operations can be set for each channel: Waveform output by compare match: Selection of 0, 1, or toggle output Input capture function: Choice of rising edge, falling edge, or both edge detection Counter clear operation: Counter clearing possible by compare match or input capture Synchronous operation: Multiple timer counters (TCNT) can be written to simultaneously simultaneous clearing by compare match and input capture possible register simultaneous input/output possible by counter synchronous operation PWM mode: Any PWM output duty can be set maximum of 7-phase PWM output possible by combination with synchronous operation * Buffer operation settable for channel 0 Input capture register double-buffering possible Automatic rewriting of output compare register possible * Phase counting mode settable independently for each of channels 1, and 2 Two-phase encoder pulse up/down-count possible * Fast access via internal 16-bit bus Fast access is possible via a 16-bit bus interface * 13 interrupt sources For channel 0 four compare match/input capture dual-function interrupts and one overflow interrupt can be requested independently
Rev. 2.00 Mar 09, 2006 page 681 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
For channels 1, and 2, two compare match/input capture dual-function interrupts, one overflow interrupt, and one underflow interrupt can be requested independently * Automatic transfer of register data Block transfer, 1-word data transfer, and 1-byte data transfer possible by direct memory access controller (DMAC) activation Table 17.1 lists the functions of the TPU. Table 17.1 TPU Functions
Item Count clock Channel 0 P/1 P/4 P/16 P/64 TCLKA TCLKB TCLKC TCLKD TGR0A TGR0B TGR0C TGR0D TIOCA0 TIOCB0 TIOCC0 TIOCD0 Channel 1 P/1 P/4 P/16 P/64 P/256 TCLKA TCLKB TGR1A TGR1B -- TIOCA1 TIOCB1 Channel 2 P/1 P/4 P/16 P/64 P/1024 TCLKA TCLKB TCLKC TGR2A TGR2B -- TIOCA2 TIOCB2
General registers General registers/ buffer registers I/O pins
Counter clear function Compare 0 output match 1 output output Toggle output Input capture function Synchronous operation PWM mode Phase counting mode Buffer operation
TGR compare match or TGR compare match or TGR compare match or input capture input capture input capture O O O O O O -- O O O O O O O O -- O O O O O O O --
Notes: O : Possible -- : Not possible Rev. 2.00 Mar 09, 2006 page 682 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) Item DMAC activation Interrupt sources Channel 0 Channel 1 Channel 2 -- 4 sources * * * * Compare match or input capture 2A Compare match or input capture 2B Overflow Underflow
TGR compare match or -- input capture 5 sources * * * * * Compare match or input capture 0A Compare match or input capture 0B Compare match or input capture 0C Compare match or input capture 0D Overflow 4 sources * * * * Compare match or input capture 1A Compare match or input capture 1B Overflow Underflow
Note: -- : Not possible
Rev. 2.00 Mar 09, 2006 page 683 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.1.2
Block Diagram
Figure 17.1 shows a block diagram of the TPU.
Clock input Internal clock: P/1 P/4 P/16 P/64 P/256 P/1024 External clock: TCLKA TCLKB TCLKC TCLKD
TSTR TSYR
Bus interface
Common
TMDR
Control logic
Internal data bus
Channel 2
TSR
TGRA
Module data bus
TIOR
TIER
TCR
TGRB
TCNT
Channel 0:
Control logic for channels 0 to 2
Channel 2:
TCR
Channel 1:
TIORH TIORL
TMDR
I/O pins TIOCA0 TIOCB0 TIOCC0 TIOCD0 TIOCA1 TIOCB1 TIOCA2 TIOCB2
Interrupt request signals Channel 0: TGI0A TGI0B TGI0C TGI0D TCI0V Channel 1: TGI1A TGI1B TCI1V TCI1U Channel 2: TGI2A TGI2B TCI2V TCI2U
TMDR
Channel 1
TSR
TGRA
TIOR
Channel 0
TSR
TIER
TGRB TGRC TGRD TGRB
TCNT TCNT
TCR: TMDR: TIOR: TIER: TSR: TCNT: TGR: TSTR: TSYR:
Timer Control Register Timer Mode Register Timer I/O Control Register Timer Interrupt Enable Register Timer Status Register Timer Counter Timer General Register Timer Start Register Timer Synchro Register
Figure 17.1 TPU Block Diagram
Rev. 2.00 Mar 09, 2006 page 684 of 906 REJ09B0292-0200
TIER
TCR
TGRA
Section 17 16-Bit Timer Pulse Unit (TPU)
17.1.3
Pin Configuration
Table 17.2 shows the pin configuration of the TPU. Table 17.2 Pin Configuration
Channel All Name Clock input A Abbreviation TCLKA I/O Input Function External clock A input pin (Channel 1 phase counting mode A phase input) External clock B input pin (Channel 1 phase counting mode B phase input) External clock C input pin (Channel 2 phase counting mode A phase input) External clock D input pin (Channel 2 phase counting mode B phase input) TGR0A input capture input/output compare output/PWM output pin TGR0B input capture input/output compare output/PWM output pin TGR0C input capture input/output compare output/PWM output pin TGR0D input capture input/output compare output/PWM output pin TGR1A input capture input/output compare output/PWM output pin TGR1B input capture input/output compare output/PWM output pin TGR2A input capture input/output compare output/PWM output pin TGR2B input capture input/output compare output/PWM output pin
Clock input B
TCLKB
Input
Clock input C
TCLKC
Input
Clock input D
TCLKD
Input
0
Input capture/output compare match A0 Input capture/output compare match B0 Input capture/output compare match C0 Input capture/output compare match D0
TIOCA0 TIOCB0 TIOCC0 TIOCD0 TIOCA1 TIOCB1 TIOCA2 TIOCB2
I/O I/O I/O I/O I/O I/O I/O I/O
1
Input capture/output compare match A1 Input capture/output compare match B1
2
Input capture/output compare match A2 Input capture/output compare match B2
Rev. 2.00 Mar 09, 2006 page 685 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.1.4
Register Configuration
Table 17.3 shows the register configuration of the TPU. Table 17.3 Register Configuration
Channel Name 0 Abbreviation 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 Initial Value H'00 H'C0 H'00 H'00 H'40 H'C0 H'0000 H'FFFF H'FFFF H'FFFF H'FFFF H'00 H'C0 H'00 H'40 H'C0 H'0000 H'FFFF H'FFFF Address H'FFFFFC50 H'FFFFFC51 H'FFFFFC52 H'FFFFFC53 H'FFFFFC54 H'FFFFFC55 H'FFFFFC56 H'FFFFFC58 H'FFFFFC5A H'FFFFFC5C H'FFFFFC5E H'FFFFFC60 H'FFFFFC61 H'FFFFFC62 H'FFFFFC64 H'FFFFFC65 H'FFFFFC66 H'FFFFFC68 H'FFFFFC6A Access size (Bits) 8,16 8,16 8,16 8,16 8,16 8,16 16 16 16 16 16 8,16 8,16 8,16 8,16 8,16 16 16 16
Timer control register 0 TCR0 Timer mode register 0 TMDR0 Timer I/O control register 0H Timer I/O control register 0L TIOR0H TIOR0L
Timer interrupt enable TIER0 register 0 Timer status register 0 TSR0 Timer counter 0 TCNT0 Timer general register TGR0A 0A Timer general register TGR0B 0B Timer general register TGR0C 0C Timer general register TGR0D 0D 1 Timer control register 1 TCR1 Timer mode register 1 TMDR1 Timer I/O control register 1 TIOR1
Timer interrupt enable TIER1 register 1 Timer status register 1 TSR1 Timer counter 1 TCNT1 Timer general register TGR1A 1A Timer general register TGR1B 1B
Rev. 2.00 Mar 09, 2006 page 686 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) Initial Value H'00 H'C0 H'00 H'40 Access size (Bits) 8, 16 8, 16 8, 16 8, 16 8, 16 16 16 16 8, 16 8, 16
Channel Name 2 Timer mode register 2 Timer I/O control register 2 Timer interrupt enable register 2 Timer status register 2 Timer counter 2 Timer general register 2A Timer general register 2B All Timer start register Timer synchro register
Abbreviation R/W R/W R/W R/W R/W TMDR2 TIOR2 TIER2 TSR2 TCNT2 TGR2A TGR2B TSTR TSYR
Address H'FFFFFC70 H'FFFFFC71 H'FFFFFC72 H'FFFFFC74 H'FFFFFC75 H'FFFFFC76
Timer control register 2 TCR2
R/(W)* H'C0 R/W R/W R/W R/W R/W H'0000
H'FFFF H'FFFFFC78 H'FFFF H'FFFFFC7A H'00 H'00 H'FFFFFC40 H'FFFFFC41
Note: * Only 0 can be written, to clear the flags.
17.2
17.2.1
Register Descriptions
Timer Control Register (TCR)
Channel 0: TCR0 Bit: Initial value: R/W: Channel 1: TCR1 Channel 2: TCR2 Bit: Initial value: R/W: 7 -- 0 R 6 CCLR1 0 R/W 5 CCLR0 0 R/W 4 CKEG1 0 R/W 3 CKEG0 0 R/W 2 TPSC2 0 R/W 1 TPSC1 0 R/W 0 TPSC0 0 R/W 7 CCLR2 0 R/W 6 CCLR1 0 R/W 5 CCLR0 0 R/W 4 CKEG1 0 R/W 3 CKEG0 0 R/W 2 TPSC2 0 R/W 1 TPSC1 0 R/W 0 TPSC0 0 R/W
Rev. 2.00 Mar 09, 2006 page 687 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
The TCR registers are 8-bit registers that control the TCNT channels. The TPU has three TCR registers, one for each of channels 0 to 2. The TCR registers are initialized to H'00 by a reset. TCNT operation should be stopped when making TCR settings. Bits 7 to 5--Counter Clear 2 to 0 (CCLR2 to CCLR0): These bits select the TCNT counter clearing source.
Channel 0 Bit 7: CCLR2 0 Bit 6: CCLR1 0 Bit 5: CCLR0 0 1 1 0 1 Description TCNT clearing disabled (Initial value) TCNT cleared by TGRA compare match/input capture TCNT cleared by TGRB compare match/input capture TCNT cleared by counter clearing for another channel performing synchronous 1 clearing/synchronous operation* TCNT clearing disabled TCNT cleared by TGRC compare match/input 2 capture* TCNT cleared by TGRD compare match/input 2 capture* TCNT cleared by counter clearing for another channel performing synchronous 1 clearing/synchronous operation*
1
0
0 1
1
0 1
Channel 1, 2
Bit 6: Bit 7: 3 Reserved* CCLR1 0 0
Bit 5: CCLR0 0 1
Description TCNT clearing disabled (Initial value) TCNT cleared by TGRA compare match/input capture TCNT cleared by TGRB compare match/input capture TCNT cleared by counter clearing for another channel performing synchronous clearing/ 1 synchronous operation*
1
0 1
Notes: 1. Synchronous operation setting is performed by setting the SYNC bit in TSYR to 1. 2. When TGRC or TGRD is used as a buffer register, TCNT is not cleared because the buffer register setting has priority, and compare match/input capture does not occur. 3. Bit 7 is reserved in channels 1and 2. It is always read as 0. The write value should always be 0. Rev. 2.00 Mar 09, 2006 page 688 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bits 4 and 3--Clock Edge 1 and 0 (CKEG1, CKEG0): These bits select the input clock edge. When a both-edges count is selected, a clock divided by two from the input clock can be selected. (e.g. P/4 both edges = P/2 rising edge). If phase counting mode is used on channels 1, and 2, this setting is ignored and the phase counting mode setting has priority.
Bit 4: CKEG1 0 1 Bit 3: CKEG0 0 1 -- Description Count at rising edge Count at falling edge Count at both edges (Initial value)
Note: Internal clock edge selection is valid when the input clock is P/4 or slower. If P/1 is selected for the input clock, this setting is ignored and a rising-edge count is selected.
Bits 2 to 0--Time Prescaler 2 to 0 (TPSC2 to TPSC0): These bits select the TCNT counter clock. The clock source can be selected independently for each channel. Table 17.4 shows the clock sources that can be set for each channel. Table 17.4 TPU Clock Sources
Internal Clock Channel
0 1 2
External Clock TCLKA TCLKB TCLKC TCLKD
O O O O O O O O O O
P/1
O O O
P/4
O O O
P/16 P/64 P/256 P/1024
O O O O O O O
Notes: O: Setting Blank: No setting Bit 2: TPSC2 0 Bit 1: TPSC1 0 1 1 0 1 Bit 0: TPSC0 0 1 0 1 0 1 0 1
Channel 0
Description Internal clock: counts on P/1 Internal clock: counts on P/4 Internal clock: counts on P/16 Internal clock: counts on P/64 External clock: counts on TCLKA pin input External clock: counts on TCLKB pin input External clock: counts on TCLKC pin input External clock: counts on TCLKD pin input (Initial value)
Rev. 2.00 Mar 09, 2006 page 689 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) Bit 2: TPSC2 0 Bit 1: TPSC1 0 1 1 0 1 Bit 0: TPSC0 0 1 0 1 0 1 0 1
Channel 1
Description Internal clock: counts on P/1 Internal clock: counts on P/4 Internal clock: counts on P/16 Internal clock: counts on P/64 External clock: counts on TCLKA pin input External clock: counts on TCLKB pin input Internal clock: counts on P/256 Setting prohibited (Initial value)
Note: This setting is ignored when channel 1 is in phase counting mode. Bit 2: TPSC2 0 Bit 1: TPSC1 0 1 1 0 1 Bit 0: TPSC0 0 1 0 1 0 1 0 1
Channel 2
Description Internal clock: counts on P/1 Internal clock: counts on P/4 Internal clock: counts on P/16 Internal clock: counts on P/64 External clock: counts on TCLKA pin input External clock: counts on TCLKB pin input External clock: counts on TCLKC pin input Internal clock: counts on P/1024 (Initial value)
Note: This setting is ignored when channel 2 is in phase counting mode.
17.2.2
Timer Mode Register (TMDR)
Channel 0: TMDR0 Bit: Initial value: R/W: Channel 1: TMDR1 Channel 2: TMDR2 Bit: Initial value: R/W: 7 -- 1 R 6 -- 1 R 5 -- 0 R 4 -- 0 R 3 MD3 0 R/W 2 MD2 0 R/W 1 MD1 0 R/W 0 MD0 0 R/W 7 -- 1 R 6 -- 1 R 5 BFB 0 R/W 4 BFA 0 R/W 3 MD3 0 R/W 2 MD2 0 R/W 1 MD1 0 R/W 0 MD0 0 R/W
Rev. 2.00 Mar 09, 2006 page 690 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
The TMDR registers are 8-bit readable/writable registers that are used to set the operating mode for each channel. The TPU has three TMDR registers, one for each channel. The TMDR registers are initialized to H'C0 by a reset. TCNT operation should be stopped when making TMDR settings. Bits 7 and 6--Reserved: These bits are always read as 1. The write value should always be 1. Bit 5--Buffer Operation B (BFB): Specifies whether TGRB is to operate in the normal way, or TGRB and TGRD are to be used together for buffer operation. When TGRD is used as a buffer register, TGRD input capture/output compare is not generated. In channels 1 and 2, which have no TGRD, bit 5 is reserved. It is always read as 0 and cannot be modified.
Bit 5: BFB 0 1 Description TGRB operates normally TGRB and TGRD used together for buffer operation (Initial value)
Bit 4--Buffer Operation A (BFA): Specifies whether TGRA is to operate in the normal way, or TGRA and TGRC are to be used together for buffer operation. When TGRC is used as a buffer register, TGRC input capture/output compare is not generated. In channels 1 and 2, which have no TGRC, bit 4 is reserved. It is always read as 0 and cannot be modified.
Bit 4: BFA 0 1 Description TGRA operates normally TGRA and TGRC used together for buffer operation (Initial value)
Rev. 2.00 Mar 09, 2006 page 691 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bits 3 to 0--Modes 3 to 0 (MD3 to MD0): These bits are used to set the timer operating mode.
Bit 3: 1 MD3* 0 Bit 2: 2 MD2* 0 Bit 1: MD1 0 1 1 0 1 1 * * Bit 0: MD0 0 1 0 1 0 1 0 1 * Description Normal operation Reserved PWM mode 1 PWM mode 2 Phase counting mode 1 Phase counting mode 2 Phase counting mode 3 Phase counting mode 4 -- (Initial value)
*: Don't care Notes: 1. MD3 is a reserved bit. In a write, it should always be written with 0. 2. Phase counting mode cannot be set for channel 0. In this case, 0 should always be written to MD2.
17.2.3
Timer I/O Control Register (TIOR)
Channel 0: TIOR0H Channel 1: TIOR1 Channel 2: TIOR2 Bit: Initial value: R/W: Channel 0: TIOR0L Bit: Initial value: R/W: 7 IOD3 0 R/W 6 IOD2 0 R/W 5 IOD1 0 R/W 4 IOD0 0 R/W 3 IOC3 0 R/W 2 IOC2 0 R/W 1 IOC1 0 R/W 0 IOC0 0 R/W 7 IOB3 0 R/W 6 IOB2 0 R/W 5 IOB1 0 R/W 4 IOB0 0 R/W 3 IOA3 0 R/W 2 IOA2 0 R/W 1 IOA1 0 R/W 0 IOA0 0 R/W
Note: When TGRC or TGRD is designated for buffer operation, this setting is invalid and the register operates as a buffer register.
Rev. 2.00 Mar 09, 2006 page 692 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
The TIOR registers are 8-bit registers that control the TGR registers. The TPU has four TIOR registers, two for channel 0 and one each for channels 1, and 2. The TIOR registers are initialized to H'00 by a reset. Note that TIOR is affected by the TMDR setting. The initial output specified by TIOR becomes valid when the counter is halted (i.e. when the CST bit is cleared to 0 in TSTR). In PWM mode 2, the output at the point at which the counter is cleared to 0 is specified. Bits 7 to 4-- I/O Control B3 to B0 (IOB3 to IOB0) I/O Control D3 to D0 (IOD3 to IOD0): Bits IOB3 to IOB0 specify the function of TGRB. Bits IOD3 to IOD0 specify the function of TGRD.
TIOR0H Bit 7: Bit 6: Bit 5: Bit 4: IOB3 IOB2 IOB1 IOB0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 0 0 1 1 * 0 1 * * TGR0B is Output disabled output Initial output is 0 compare output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match TGR0B is Capture input Input capture at rising edge input source is Input capture at falling edge capture TIOCB0 pin Input capture at both edges register Setting prohibited *: Don't care
Channel 0
Output disabled Initial output is 1 output
Rev. 2.00 Mar 09, 2006 page 693 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) TIOR0L Bit 7: Bit 6: Bit 5: Bit 4: IOD3 IOD2 IOD1 IOD0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 0 0 1 1 * 0 1 * * TGR0D Output disabled isoutput Initial output is 0 compare output 1 register* (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match TGR0D is Capture input Input capture at rising edge input source is Input capture at falling edge capture TIOCD0 pin 1 Input capture at both edges register* Setting prohibited
Channel 0
Output disabled Initial output is 1 output
*: Don't care Note: 1. When the BFB bit in TMDR0 is set to 1 and TGR0D is used as a buffer register, this setting is invalid and input capture/output compare is not generated.
Rev. 2.00 Mar 09, 2006 page 694 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) TIOR1 Channel 1 Bit 7: Bit 6: Bit 5: Bit 4: IOB3 IOB2 IOB1 IOB0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 0 0 1 1 * 0 1 * * TGR1B is Output disabled output Initial output is 0 compare output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match TGR1B is Capture input Input capture at rising edge input source is Input capture at falling edge capture TIOCB1 pin Input capture at both edges register Setting prohibited *: Don't care TIOR2 Channel 2 Bit 7: Bit 6: Bit 5: Bit 4: IOB3 IOB2 IOB1 IOB0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 * 0 1 0 1 * TGR2B is Capture input input source is capture TIOCB2 pin register TGR2B is Output disabled output Initial output is 0 compare output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match Input capture at rising edge Input capture at falling edge Input capture at both edges *: Don't care Rev. 2.00 Mar 09, 2006 page 695 of 906 REJ09B0292-0200
Output disabled Initial output is 1 output
Output disabled Initial output is 1 output
Section 17 16-Bit Timer Pulse Unit (TPU)
Bits 3 to 0-- I/O Control A3 to A0 (IOA3 to IOA0) I/O Control C3 to C0 (IOC3 to IOC0): IOA3 to IOA0 specify the function of TGRA. IOC3 to IOC0 specify the function of TGRC.
TIOR0H Bit 3: Bit 2: Bit 1: Bit 0: IOA3 IOA2 IOA1 IOA0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 0 0 1 1 * 0 1 * * TGR0A is Output disabled output Initial output is 0 compare output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match TGR0A is Capture input Input capture at rising edge input source is Input capture at falling edge capture TIOCA0 pin Input capture at both edges register Setting prohibited *: Don't care
Channel 0
Output disabled Initial output is 1 output
Rev. 2.00 Mar 09, 2006 page 696 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) TIOR0L Bit 3: Bit 2: Bit 1: Bit 0: IOC3 IOC2 IOC1 IOC0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 0 0 1 1 * 0 1 * * Output disabled Initial output is 1 output 0 output at compare match 1 output at compare match Toggle output at compare match Input capture at rising edge TGR0C is Capture input input source is Input capture at falling edge capture TIOCC0 pin Input capture at both edges *1 register Setting prohibited TGR0C is Output disabled output Initial output is 0 compare *1 output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match
Channel 0
*: Don't care Note: 1. When the BFA bit in TMDR0 is set to 1 and TGR0C is used as a buffer register, this setting is invalid and input capture/output compare is not generated.
Rev. 2.00 Mar 09, 2006 page 697 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU) TIOR1 Channel 1 Bit 3: Bit 2: Bit 1: Bit 0: IOA3 IOA2 IOA1 IOA0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 0 0 1 1 * 0 1 * * TGR1A is Output disabled output Initial output is 0 compare output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match TGR1A is Capture input Input capture at rising edge input source is Input capture at falling edge capture TIOCA1 pin Input capture at both edges register Setting prohibited *: Don't care TIOR2 Channel 2 Bit 3: Bit 2: Bit 1: Bit 0: IOA3 IOA2 IOA1 IOA0 Description 0 0 0 1 0 1 0 1 1 0 1 0 1 0 1 1 * 0 1 0 1 * TGR2A is Capture input input source is capture TIOCA2 pin register TGR2A is Output disabled output Initial output is 0 compare output register (Initial value) 0 output at compare match 1 output at compare match Toggle output at compare match 0 output at compare match 1 output at compare match Toggle output at compare match Input capture at rising edge Input capture at falling edge Input capture at both edges *: Don't care Rev. 2.00 Mar 09, 2006 page 698 of 906 REJ09B0292-0200
Output disabled Initial output is 1 output
Output disabled Initial output is 1 output
Section 17 16-Bit Timer Pulse Unit (TPU)
17.2.4
Timer Interrupt Enable Register (TIER)
Channel 0: TIER0 Bit: Initial value: R/W: Channel 1: TIER1 Channel 2: TIER2 Bit: Initial value: R/W: 7 -- 0 R 6 -- 1 R 5 TCIEU 0 R/W 4 TCIEV 0 R/W 3 -- 0 R 2 -- 0 R 1 TGIEB 0 R/W 0 TGIEA 0 R/W 7 -- 0 R 6 -- 1 R 5 -- 0 R 4 TCIEV 0 R/W 3 TGIED 0 R/W 2 TGIEC 0 R/W 1 TGIEB 0 R/W 0 TGIEA 0 R/W
The TIER registers are 8-bit registers that control enabling or disabling of interrupt requests for each channel. The TPU has three TIER registers, one for each channel. The TIER registers are initialized to H'40 by a reset. Bit 7--Reserved: This bit is always read as 0. The write value should always be 0. Bit 6--Reserved: This bit is always read as 1. The write value should always be 1. Bit 5--Underflow Interrupt Enable (TCIEU): Enables or disables interrupt requests (TCIU) by the TCFU flag when the TCFU flag in TSR is set to 1 in channels 1 and 2. In channel 0, bit 5 is reserved. It is always read as 0 and cannot be modified.
Bit 5: TCIEU 0 1 Description Interrupt requests (TCIU) by TCFU disabled Interrupt requests (TCIU) by TCFU enabled (Initial value)
Bit 4--Overflow Interrupt Enable (TCIEV): Enables or disables interrupt requests (TCIV) by the TCFV flag when the TCFV flag in TSR is set to 1.
Bit 4: TCIEV 0 1 Description Interrupt requests (TCIV) by TCFV disabled Interrupt requests (TCIV) by TCFV enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 699 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bit 3--TGR Interrupt Enable D (TGIED): Enables or disables interrupt requests (TGID) by the TGFD bit when the TGFD bit in TSR is set to 1 in channel 0. In channels 1, and 2, bit 3 is reserved. It is always read as 0 and cannot be modified.
Bit 3: TGIED 0 1 Description Interrupt requests (TGID) by TGFD bit disabled Interrupt requests (TGID) by TGFD bit enabled (Initial value)
Bit 2--TGR Interrupt Enable C (TGIEC): Enables or disables interrupt requests (TGIC) by the TGFC bit when the TGFC bit in TSR is set to 1 in channel 0. In channels 1 and 2, bit 2 is reserved. It is always read as 0 and cannot be modified.
Bit 2: TGIEC 0 1 Description Interrupt requests (TGIC) by TGFC bit disabled Interrupt requests (TGIC) by TGFC bit enabled (Initial value)
Bit 1--TGR Interrupt Enable B (TGIEB): Enables or disables interrupt requests (TGIB) by the TGFB bit when the TGFB bit in TSR is set to 1.
Bit 1: TGIEB 0 1 Description Interrupt requests (TGIB) by TGFB bit disabled Interrupt requests (TGIB) by TGFB bit enabled (Initial value)
Bit 0--TGR Interrupt Enable A (TGIEA): Enables or disables interrupt requests (TGIA) by the TGFA bit when the TGFA bit in TSR is set to 1.
Bit 0: TGIEA 0 1 Description Interrupt requests (TGIA) by TGFA bit disabled Interrupt requests (TGIA) by TGFA bit enabled (Initial value)
Rev. 2.00 Mar 09, 2006 page 700 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.2.5
Timer Status Register (TSR)
Channel 0: TSR0 Bit: Initial value: R/W: 7 -- 1 R 6 -- 1 R 5 -- 0 R 4 TCFV 0 R/(W)* 3 TGFD 0 R/(W)* 2 TGFC 0 R/(W)* 1 TGFB 0 R/(W)* 0 TGFA 0 R/(W)*
Note: * Only 0 can be written, to clear the flags. Channel 1: TSR1 Channel 2: TSR2 Bit: Initial value: R/W: 7 TCFD 1 R 6 -- 1 R 5 TCFU 0 R/(W)* 4 TCFV 0 R/(W)* 3 -- 0 R 2 -- 0 R 1 TGFB 0 R/(W)* 0 TGFA 0 R/(W)*
Note: * Only 0 can be written, to clear the flags.
The TSR registers are 8-bit registers that indicate the status of each channel. The TPU has three TSR registers, one for each channel. The TSR registers are initialized to H'C0 by a reset. Bit 7--Count Direction Flag (TCFD): Status flag that shows the direction in which TCNT counts in channels 1, and 2. In channel 0, bit 7 is reserved. It is always read as 1 and cannot be modified.
Bit 7: TCFD 0 1 Description TCNT counts down TCNT counts up (Initial value)
Bit 6--Reserved: This bit is always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 701 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bit 5--Underflow Flag (TCFU): Status flag that indicates that TCNT underflow has occurred when channels 1 and 2 are set to phase counting mode. In channel 0, bit 5 is reserved. It is always read as 0 and cannot be modified.
Bit 5: TCFU 0 1 Description [Clearing condition] When 0 is written to TCFU after reading TCFU = 1 [Setting condition] When the TCNT value underflows (changes from H'0000 to H'FFFF) (Initial value)
Bit 4--Overflow Flag (TCFV): Status flag that indicates that TCNT overflow has occurred.
Bit 4: TCFV 0 1 Description [Clearing condition] When 0 is written to TCFV after reading TCFV = 1 [Setting condition] When the TCNT value overflows (changes from H'FFFF to H'0000 ) (Initial value)
Bit 3--Input Capture/Output Compare Flag D (TGFD): Status flag that indicates the occurrence of TGRD input capture or compare match in channel 0. In channels 1 and 2, bit 3 is reserved. It is always read as 0 and cannot be modified.
Bit 3: TGFD 0 Description [Clearing conditions] * * 1 * * (Initial value) When DMAC is activated by TGID interrupt while DRCR setting in DMAC is TGI0D When 0 is written to TGFD after reading TGFD = 1 When TCNT = TGRD while TGRD is functioning as output compare register When TCNT value is transferred to TGRD by input capture signal while TGRD is functioning as input capture register
[Setting conditions]
Rev. 2.00 Mar 09, 2006 page 702 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bit 2--Input Capture/Output Compare Flag C (TGFC): Status flag that indicates the occurrence of TGRC input capture or compare match in channel 0. In channels 1 and 2, bit 2 is reserved. It is always read as 0 and cannot be modified.
Bit 2: TGFC 0 Description [Clearing conditions] * * 1 * * (Initial value) When DMAC is activated by TGIC interrupt while DRCR setting in DMAC is TGI0C When 0 is written to TGFC after reading TGFC = 1 When TCNT = TGRC while TGRC is functioning as output compare register When TCNT value is transferred to TGRC by input capture signal while TGRC is functioning as input capture register
[Setting conditions]
Bit 1--Input Capture/Output Compare Flag B (TGFB): Status flag that indicates the occurrence of TGRB input capture or compare match.
Bit 1: TGFB 0 Description [Clearing conditions] * * 1 * * (Initial value) When DMAC is activated by TGIB interrupt while DRCR setting in DMAC is TGI0B When 0 is written to TGFB after reading TGFB = 1 When TCNT = TGRB while TGRB is functioning as output compare register When TCNT value is transferred to TGRB by input capture signal while TGRB is functioning as input capture register
[Setting conditions]
Rev. 2.00 Mar 09, 2006 page 703 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bit 0--Input Capture/Output Compare Flag A (TGFA): Status flag that indicates the occurrence of TGRA input capture or compare match.
Bit 0: TGFA 0 Description [Clearing conditions] * * 1 * * (Initial value) When DMAC is activated by TGIA interrupt while DRCR setting in DMAC is TGI0A When 0 is written to TGFA after reading TGFA = 1 When TCNT = TGRA while TGRA is functioning as output compare register When TCNT value is transferred to TGRA by input capture signal while TGRA is functioning as input capture register
[Setting conditions]
17.2.6
Timer Counter (TCNT)
Channel 0: TCNT0 (up-counter) Channel 1: TCNT1 (up/down-counter*) Channel 2: TCNT2 (up/down-counter*) Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 0 R/W 14 0 R/W 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
Note: * These counters can be used as up/down-counters only in phase counting mode. In other cases they function as up-counters.
The TCNT registers are 16-bit counters. The TPU has three TCNT counters, one for each channel. The TCNT counters are initialized to H'0000 by a reset. The TCNT counters cannot be accessed in 8-bit units; they must always be accessed as a 16-bit unit.
Rev. 2.00 Mar 09, 2006 page 704 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.2.7
Timer General Register (TGR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 1 R/W 7 1 R/W 14 1 R/W 6 1 R/W 13 1 R/W 5 1 R/W 12 1 R/W 4 1 R/W 11 1 R/W 3 1 R/W 10 1 R/W 2 1 R/W 9 1 R/W 1 1 R/W 8 1 R/W 0 1 R/W
The TGR registers are 16-bit registers with a dual function as output compare and input capture registers. The TPU has 8 TGR registers, four for channel 0 and two each for channels 1, and 2. TGRC and TGRD for channel 0 can also be designated for operation as buffer registers*. The TGR registers are initialized to H'FFFF by a reset. The TGR registers cannot be accessed in 8-bit units; they must always be accessed as a 16-bit unit. Note: * TGR buffer register combinations are TGRA-TGRC and TGRB-TGRD. 17.2.8 Timer Start Register (TSTR)
Bit: Initial value: R/W: 7 -- 0 R 6 -- 0 R 5 -- 0 R 4 -- 0 R 3 -- 0 R 2 CST2 0 R/W 1 CST1 0 R/W 0 CST0 0 R/W
TSTR is an 8-bit readable/writable register that selects operation/stoppage for channels 0 to 2. TSTR is initialized to H'00 by a reset. TCNT counter operation should be stopped when setting the operating mode in TMDR or the TCNT count clock in TCR. Bits 7 to 3--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 705 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Bits 2 to 0--Counter Start 2 to 0 (CST2 to CST0): These bits select operation or stoppage for TCNT.
Bit n: CSTn 0 1 Description TCNTn count operation is stopped TCNTn performs count operation (Initial value)
Note: n = 2 to 0 If 0 is written to the CST bit during operation with the TIOC pin designated for output, the counter stops, but the TIOC pin output compare output level is retained. If TIOR is written to when the CST bit is cleared to 0, the pin output level will be changed to the set initial output value.
17.2.9
Timer Synchronous Register (TSYR)
Bit: Initial value: R/W: 7 -- 0 R 6 -- 0 R 5 -- 0 R 4 -- 0 R 3 -- 0 R 2 SYNC2 0 R/W 1 SYNC1 0 R/W 0 SYNC0 0 R/W
TSYR is an 8-bit readable/writable register that selects independent operation or synchronous operation for the channel 0 to 2 TCNT counters. A channel performs synchronous operation when the corresponding bit in TSYR is set to 1. TSYR is initialized to H'00 by a reset. Bits 7 to 3--Reserved: These bits are always read as 0. The write value should always be 0. Bits 2 to 0--Timer Synchro 2 to 0 (SYNC2 to SYNC0): These bits select whether operation is independent of or synchronized with other channels.
1 When synchronous operation is selected, synchronous presetting of multiple channels* , and 2 synchronous clearing through counter clearing on another channel* are possible.
Bit n: SYNCn 0 1
Description TCNTn operates independently (Initial value) TCNT presetting/clearing is unrelated to other channels TCNTn performs synchronous operation TCNT synchronous presetting/synchronous clearing is possible
Notes: n = 2 to 0 1. To set synchronous operation, the SYNC bits for two channels at least must be set to 1. 2. To set synchronous clearing, in addition to the SYNC bit , the TCNT clearing source must also be set by means of bits CCLR2 to CCLR0 in TCR. Rev. 2.00 Mar 09, 2006 page 706 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.3
17.3.1
Interface to Bus Master
16-Bit Registers
TCNT and TGR are 16-bit registers. As the data bus to the bus master is 16 bits wide, these registers can be read and written to in 16-bit units. These registers cannot be read or written to in 8-bit units; 16-bit access must always be used. An example of 16-bit register access operation is shown in figure 17.2.
Internal data bus H Bus master Module data bus
L
Bus interface
TCNTH
TCNTL
Figure 17.2 16-Bit Register Access Operation [Bus Master TCNT (16 Bits)] 17.3.2 8-Bit Registers
Registers other than TCNT and TGR are 8-bit. As the data bus to the CPU is 16 bits wide, these registers can be read and written to in 16-bit units. They can also be read and written to in 8-bit units.
Rev. 2.00 Mar 09, 2006 page 707 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Examples of 8-bit register access operation are shown in figures 17.3, 17.4, and 17.5.
Internal data bus H Bus master Module data bus
L
Bus interface
TCR
Figure 17.3 8-Bit Register Access Operation [Bus Master TCR (Upper 8 Bits)]
Internal data bus H Bus master Module data bus
L
Bus interface
TMDR
Figure 17.4 8-Bit Register Access Operation [Bus Master TMDR (Lower 8 Bits)]
Internal data bus H Bus master Module data bus
L
Bus interface
TCR
TMDR
Figure 17.5 8-Bit Register Access Operation [Bus Master TCR and TMDR (16 Bits)]
Rev. 2.00 Mar 09, 2006 page 708 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.4
17.4.1
Operation
Overview
Operation in each mode is outlined below. Normal Operation: Each channel has a TCNT and TGR register. TCNT performs up-counting, and is also capable of free-running operation, synchronous counting, and external event counting. Each TGR can be used as an input capture register or output compare register. Synchronous Operation: The TCNT counter for a channel designated for synchronous operation by means of TSYR performs synchronous presetting. That is, when TCNT for a channel designated for synchronous operation is rewritten, the TCNT counters for the other channels are also rewritten at the same time. Synchronous clearing of the TCNT counters is also possible by setting the counter clear bits in TCR for channels designated for synchronous operation. Buffer Operation * When TGR is an output compare register When a compare match occurs, the value in the buffer register for the relevant channel is transferred to TGR. * When TGR is an input capture register When input capture occurs, the value in TCNT is transfer to TGR and the value previously held in TGR is transferred to the buffer register. PWM Mode: In this mode, a PWM waveform is output. The output level can be set by means of TIOR. A PWM waveform with a duty of between 0% and 100% can be output, according to the setting of each TGR register. Phase Counting Mode: In this mode, TCNT is incremented or decremented by detecting the phases of two clocks input from the external clock input pins in channels 1, and 2. When phase counting mode is set, the corresponding TCLK pin functions as the clock input, and TCNT performs up- or down-counting. This can be used for two-phase encoder pulse input.
Rev. 2.00 Mar 09, 2006 page 709 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.4.2
Basic Functions
Counter Operation: When one of bits CST0 to CST2 is set to 1 in TSTR, the TCNT counter for the corresponding channel starts counting. TCNT can operate as a free-running counter, periodic counter, and so on. * Example of count operation setting procedure Figure 17.6 shows an example of the count operation setting procedure.
1 Operation selection Select the counter clock with bits TPSC2 to TPSC0 in TCR. At the same time, select the input clock edge with bits CKEG1 and CKEG0 in TCR. For periodic counter operation, select the TGR to be used as the TCNT clearing source with bits CCLR2 to CCLR0 in TCR. Designate the TGR selected in [2] as an output compare register by means of TIOR. Set the periodic counter cycle in the TGR selected in (2). Set the CST bit in TSTR to 1 to start the count operation.
Select counter clock
1
Periodic counter
Free-running counter
2
Select counter clearing source
2
Select output compare register
3
3
Set period
4 4
Start count operation
5
Start count operation
5 5
Figure 17.6 Example of Counter Operation Setting Procedure
Rev. 2.00 Mar 09, 2006 page 710 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* Free-running count operation and periodic count operation Immediately after a reset, the TPU's TCNT counters are all designated as free-running counters. When the relevant bit in TSTR is set to 1 the corresponding TCNT counter starts upcount operation as a free-running counter. When TCNT overflows (from H'FFFF to H'0000), the TCFV bit in TSR is set to 1. If the value of the corresponding TCIEV bit in TIER is 1 at this point, the TPU requests an interrupt. After overflow, TCNT starts counting up again from H'0000. Figure 17.7 illustrates free-running counter operation.
TCNT value H'FFFF
H'0000
Time
CST bit
TCFV
Figure 17.7 Free-Running Counter Operation When compare match is selected as the TCNT clearing source, the TCNT counter for the relevant channel performs periodic count operation. The TGR register for setting the period is designated as an output compare register, and counter clearing by compare match is selected by means of bits CCLR2 to CCLR0 in TCR. After the settings have been made, TCNT starts up-count operation as periodic counter when the corresponding bit in TSTR is set to 1. When the count value matches the value in TGR, the TGF bit in TSR is set to 1 and TCNT is cleared to H'0000. If the value of the corresponding TGIE bit in TIER is 1 at this point, the TPU requests an interrupt. After a compare match, TCNT starts counting up again from H'0000.
Rev. 2.00 Mar 09, 2006 page 711 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Figure 17.8 illustrates periodic counter operation.
TCNT value TGR Counter cleared by TGR compare match
H'0000
Time
CST bit Flag cleared by software or DMAC activation TGF
Figure 17.8 Periodic Counter Operation Waveform Output by Compare Match: The TPU can perform 0, 1, or toggle output from the corresponding output pin using compare match. * Example of setting procedure for waveform output by compare match Figure 17.9 shows an example of the setting procedure for waveform output by compare match
Output selection
1 Select initial value 0 output or 1 output, and compare match output value 0 output, 1 output, or toggle output, by means of TIOR. The set initial value is output at the TIOC pin until the first compare match occurs. 1 2 Set the timing for compare match generation in TGR. 2 3 Set the CST bit in TSTR to 1 to start the count operation.
Select waveform output mode
Set output timing
Start count operation
3

Figure 17.9 Example of Setting Procedure for Waveform Output by Compare Match
Rev. 2.00 Mar 09, 2006 page 712 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* Examples of waveform output operation Figure 17.10 shows an example of 0 output/1 output. In this example TCNT has been designated as a free-running counter, and settings have been made so that 1 is output by compare match A, and 0 is output by compare match B. When the set level and the pin level coincide, the pin level does not change.
TCNT value H'FFFF TGRA TGRB H'0000 No change TIOCA TIOCB No change No change No change 1 output 0 output Time
Figure 17.10 Example of 0 Output/1 Output Operation Figure 17.11 shows an example of toggle output. In this example TCNT has been designated as a periodic counter (with counter clearing performed by compare match B), and settings have been made so that output is toggled by both compare match A and compare match B.
TCNT value Counter cleared by TGRB compare match H'FFFF TGRB TGRA H'0000 Time Toggle output Toggle output
TIOCB TIOCA
Figure 17.11 Example of Toggle Output Operation
Rev. 2.00 Mar 09, 2006 page 713 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Input Capture Function: The TCNT value can be transferred to TGR on detection of the TIOC pin input edge. Rising edge, falling edge, or both edges can be selected as the detected edge. * Example of input capture operation setting procedure Figure 17.12 shows an example of the input capture operation setting procedure.
Input selection
1 Designate TGR as an input capture register by means of TIOR, and select rising edge, falling edge, or both edges as the input capture source and input signal edge. 1 2 Set the CST bit in TSTR to 1 to start the count operation.
Select input capture input
Start count
2

Figure 17.12 Example of Input Capture Operation Setting Procedure
Rev. 2.00 Mar 09, 2006 page 714 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* Example of input capture operation Figure 17.13 shows an example of input capture operation. In this example both rising and falling edges have been selected as the TIOCA pin input capture input edge, falling edge has been selected as the TIOCB pin input capture input edge, and counter clearing by TGRB input capture has been designated for TCNT.
TCNT value H'0180 H'0160 Counter cleared by TIOCB input (falling edge)
H'0010 H'0005 H'0000 Time
TIOCA
TGRA
H'0005
H'0160
H'0010
TIOCB TGRB H'0180
Figure 17.13 Example of Input Capture Operation
Rev. 2.00 Mar 09, 2006 page 715 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.4.3
Synchronous Operation
In synchronous operation, the values in a number of TCNT counters can be rewritten simultaneously (synchronous presetting). Also, a number of TCNT counters can be cleared simultaneously by making the appropriate setting in TCR (synchronous clearing). Synchronous operation enables TGR to be incremented with respect to a single time base. Channels 0 to 2 can all be designated for synchronous operation. Example of Synchronous Operation Setting Procedure: Figure 17.14 shows an example of the synchronous operation setting procedure.
Synchronous operation selection Set synchronous operation
1
Synchronous presetting
Synchronous clearing
Set TCNT
2
Clearing source generation channel? Yes Select counter clearing source Start count
No
3 5
Set synchronous counter clearing Start count
4 5



1 2 3 4 5
Set to 1 the SYNC bits in TSYR corresponding to the channels to be designated for synchronous operation. When the TCNT counter of any of the channels designated for synchronous operation is written to, the same value is simultaneously written to the other TCNT counters. Use bits CCLR2 to CCLR0 in TCR to specify TCNT clearing by input capture/output compare, etc. Use bits CCLR2 to CCLR0 in TCR to designate synchronous clearing for the counter clearing source. Set to 1 the CST bits in TSTR for the relevant channels, to start the count operation.
Figure 17.14 Example of Synchronous Operation Setting Procedure
Rev. 2.00 Mar 09, 2006 page 716 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Example of Synchronous Operation: Figure 17.15 shows an example of synchronous operation. In this example, synchronous operation and PWM mode 1 have been designated for channels 0 to 2, TGR0B compare match has been set as the channel 0 counter clearing source, and synchronous clearing has been set for the channel 1 and 2 counter clearing source. Three-phase PWM waveforms are output from pins TIOC0A, TIOC1A, and TIOC2A. At this time, synchronous presetting, and synchronous clearing by TGR0B compare match, is performed for channel 0 to 2 TCNT counters, and the data set in TGR0B is used as the PWM cycle. For details of PWM modes, see section 17.4.5, PWM Modes.
Synchronous clearing by TGR0B compare match TCNT0 to TCNT2 values TGR0B TGR1B TGR0A TGR2B TGR1A TGR2A H'0000 Time
TIOC0A TIOC1A TIOC2A
Figure 17.15 Example of Synchronous Operation
Rev. 2.00 Mar 09, 2006 page 717 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.4.4
Buffer Operation
Buffer operation, provided for channel 0 enables TGRC and TGRD to be used as buffer registers. Buffer operation differs depending on whether TGR has been designated as an input capture register or as a compare match register. Table 17.5 shows the register combinations used in buffer operation. Table 17.5 Register Combinations in Buffer Operation
Channel 0 Timer General Register TGR0A TGR0B Buffer Register TGR0C TGR0D
* When TGR is an output compare register When a compare match occurs, the value in the buffer register for the corresponding channel is transferred to the timer general register. This operation is illustrated in figure 17.16.
Compare match signal
Buffer register
Timer general register
Comparator
TCNT
Figure 17.16 Compare Match Buffer Operation
Rev. 2.00 Mar 09, 2006 page 718 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* When TGR is an input capture register When input capture occurs, the value in TCNT is transferred to TGR and the value previously held in the timer general register is transferred to the buffer register. This operation is illustrated in figure 17.17.
Input capture signal Timer general register
Buffer register
TCNT
Figure 17.17 Input Capture Buffer Operation Example of Buffer Operation Setting Procedure: Figure 17.18 shows an example of the buffer operation setting procedure.
Buffer operation
1 Designate TGR as an input capture register or output compare register by means of TIOR. 1 2 Designate TGR for buffer operation with bits BFA and BFB in TMDR. 3 Set the CST bit in TSTR to 1 to start the count operation.
Select TGR function
Set buffer operation
2
Start count
3

Figure 17.18 Example of Buffer Operation Setting Procedure
Rev. 2.00 Mar 09, 2006 page 719 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Examples of Buffer Operation * When TGR is an output compare register Figure 17.19 shows an operation example in which PWM mode 1 has been designated for channel 0, and buffer operation has been designated for TGRA and TGRC. The settings used in this example are TCNT clearing by compare match B, 1 output at compare match A, and 0 output at compare match B. As buffer operation has been set, when compare match A occurs the output changes and the value in buffer register TGRC is simultaneously transferred to timer general register TGRA. This operation is repeated each time compare match A occurs. For details of PWM modes, see section 17.4.5, PWM Modes.
TCNT value TGR0B H'0200 TGR0A H'0000 TGR0C H'0200 Transfer TGR0A H'0200 H'0450 H'0450 H'0520 Time H'0520
H'0450
TIOCA
Figure 17.19 Example of Buffer Operation (1)
Rev. 2.00 Mar 09, 2006 page 720 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* When TGR is an input capture register Figure 17.20 shows an operation example in which TGRA has been designated as an input capture register, and buffer operation has been designated for TGRA and TGRC. Counter clearing by TGRA input capture has been set for TCNT, and both rising and falling edges have been selected as the TIOCA pin input capture input edge. As buffer operation has been set, when the TCNT value is stored in TGRA upon occurrence of input capture A, the value previously stored in TGRA is simultaneously transferred to TGRC.
TCNT value H'0F07 H'09FB H'0532 H'0000 Time
TIOCA
TGRA
H'0532
H'0F07
H'09FB
TGRC
H'0532
H'0F07
Figure 17.20 Example of Buffer Operation (2) 17.4.5 PWM Modes
In PWM mode, PWM waveforms are output from the output pins. 0, 1, or toggle output can be selected as the output level in response to compare match of each TGR. Designating TGR compare match as the counter clearing source enables the period to be set in that register. All channels can be designated for PWM mode independently. Synchronous operation is also possible. There are two PWM modes, as described below.
Rev. 2.00 Mar 09, 2006 page 721 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* PWM mode 1 PWM output is generated by pairing TGRA with TGRB and TGRC with TGRD. The output specified by bits IOA3-IOA0 and IOC3-IOC0 in TIOR is performed in response to compare match A and C, and the output specified by bits IOB3-IOB0 and IOD3-IOD0 in TIOR in response to compare match B and D, from pins TIOCA and TIOCC. The initial output value is the value set in TGRA or TGRC. If the set values of paired TGRs are identical, the output value does not change when a compare match occurs. In PWM mode 1, a maximum 4-phase PWM output is possible. * PWM mode 2 PWM output is generated using one TGR as the cycle register and the others as duty registers. The output specified by TIOR is performed in response to a compare match. Also, when the counter is cleared by a synchronization register compare match, pin output values are the initial values set in TIOR. If the set values of the period and duty registers are identical, the output value does not change when a compare match occurs. In PWM mode 2, a maximum 7-phase PWM output is possible by combined use with synchronous operation. The correspondence between PWM output pins and registers is shown in table 17.6. Table 17.6 PWM Output Registers and Output Pins
Output Pins Channel 0 Registers TGR0A TGR0B TGR0C TGR0D 1 2 TGR1A TGR1B TGR2A TGR2B TIOCA2 TIOCA1 TIOCC0 PWM Mode 1 TIOCA0 PWM Mode 2 TIOCA0 TIOCB0 TIOCC0 TIOCD0 TIOCA1 TIOCB1 TIOCA2 TIOCB2
Note: In PWM mode 2, PWM output is not possible for the TGR register in which the period is set.
Rev. 2.00 Mar 09, 2006 page 722 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Example of PWM Mode Setting Procedure: Figure 17.21 shows an example of the PWM mode setting procedure.
1 Select the counter clock with bits TPSC2 to TPSC0 in TCR. At the same time, select the input clock edge with bits CKEG1 and CKEG0 in TCR. 2 Use bits CCLR2 to CCLR0 in TCR to select the TGR to be used as the TCNT clearing source. 3 Use TIOR to designate the TGR as an output compare register, and select the initial value and output value. 4 Set the cycle in the TGR selected in [2], and set the duty in the other the TGR. 5 Select the PWM mode with bits MD3 to MD0 in TMDR.
Set PWM mode
PWM mode
Select counter clock
1
Select counter clearing source
2
Select waveform output level
3
Set TGR
4
5
6 Set the CST bit in TSTR to 1 to start the count operation.
Start count
6

Figure 17.21 Example of PWM Mode Setting Procedure Examples of PWM Mode Operation: Figure 17.22 shows an example of PWM mode 1 operation. In this example, TGRA compare match is set as the TCNT clearing source, 0 is set for the TGRA initial output value and output value, and 1 output is set as the TGRB output value. In this case, the value set in TGRA is used as the period, and the values set in TGRB registers as the duty.
Rev. 2.00 Mar 09, 2006 page 723 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
TCNT value TGRA
Counter cleared by TGRA compare match
TGRB H'0000 Time
TIOCA
Figure 17.22 Example of PWM Mode Operation (1) Figure 17.23 shows an example of PWM mode 2 operation. In this example, synchronous operation is designated for channels 0 and 1, TGR1B compare match is set as the TCNT clearing source, and 0 is set for the initial output value and 1 for the output value of the other TGR registers, to output a 5-phase PWM waveform. In this case, the value set in TGR1B is used as the cycle, and the values set in the other TGRs as the duty.
Counter cleared by TGR1B compare match
TCNT value TGR1B TGR1A TGR0D TGR0C TGR0B TGR0A H'0000
TIOCA0 TIOCB0 TIOCC0 TIOCD0 TIOCA1
Figure 17.23 Example of PWM Mode Operation (2)
Rev. 2.00 Mar 09, 2006 page 724 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Figure 17.24 shows examples of PWM waveform output with 0% duty and 100% duty in PWM mode.
TCNT value TGRA
TGRB rewritten
TGRB H'0000 0% duty
TGRB rewritten
TGRB rewritten Time
TIOCA
Output does not change when cycle register and duty register compare matches occur simultaneously TCNT value TGRB rewritten TGRA TGRB rewritten TGRB H'0000 100% duty TGRB rewritten Time
TIOCA
Output does not change when cycle register and duty register compare matches occur simultaneously TCNT value TGRB rewritten TGRA TGRB rewritten TGRB H'0000 100% duty 0% duty
TGRB rewritten Time
TIOCA
Figure 17.24 Example of PWM Mode Operation (3)
Rev. 2.00 Mar 09, 2006 page 725 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.4.6
Phase Counting Mode
In phase counting mode, the phase difference between two external clock inputs is detected and TCNT is incremented/decremented accordingly. This mode can be set for channels 1, and 2. When phase counting mode is set, an external clock is selected as the counter input clock and TCNT operates as an up/down-counter regardless of the setting of bits TPSC2 to TPSC0 and bits CKEG1 and CKEG0 in TCR. However, the functions of bits CCLR1 and CCLR0 in TCR, and of TIOR, TIER, and TGR are valid, and input capture/compare match and interrupt functions can be used. When overflow occurs while TCNT is counting up, the TCFV flag in TSR is set; when underflow occurs while TCNT is counting down, the TCFU flag is set. The TCFD bit in TSR is the count direction flag. Reading the TCFD flag provides an indication of whether TCNT is counting up or down. Table 17.7 shows the correspondence between external clock pins and channels. Table 17.7 Phase Counting Mode Clock Input Pins
External Clock Pins Channels When channel 1 is set to phase counting mode When channel 2 is set to phase counting mode A-Phase TCLKA TCLKC B-Phase TCLKB TCLKD
Example of Phase Counting Mode Setting Procedure: Figure 17.25 shows an example of the phase counting mode setting procedure.
1 Select phase counting mode with bits MD3 to MD0 in TMDR. 2 Set the CST bit in TSTR to 1 to start the count operation.
Phase counting mode
Select phase counting mode
1
Start count
2

Figure 17.25 Example of Phase Counting Mode Setting Procedure
Rev. 2.00 Mar 09, 2006 page 726 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Examples of Phase Counting Mode Operation: In phase counting mode, TCNT counts up or down according to the phase difference between two external clocks. There are four modes, according to the count conditions. * Phase counting mode 1 Figure 17.26 shows an example of phase counting mode 1 operation, and table 17.8 summarizes the TCNT up/down-count conditions.
TCLKA (channel 1) TCLKC (channel 2) TCLKB (channel 1) TCLKD (channel 2) TCNT value Up-count Down-count
Time
Figure 17.26 Example of Phase Counting Mode 1 Operation Table 17.8 Up/Down-Count Conditions in Phase Counting Mode 1
TCLKA (Channel 1) TCLKC (Channel 2) High level Low level Low level High level High level Low level High level Low level Notes: : Rising edge : Falling edge Down-count TCLKB (Channel 1) TCLKD (Channel 2) Operation Up-count
Rev. 2.00 Mar 09, 2006 page 727 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* Phase counting mode 2 Figure 17.27 shows an example of phase counting mode 2 operation, and table 17.9 summarizes the TCNT up/down-count conditions.
TCLKA (Channel 1) TCLKC (Channel 2) TCLKB (Channel 1) TCLKD (Channel 2) TCNT value Up-count Down-count
Time
Figure 17.27 Example of Phase Counting Mode 2 Operation Table 17.9 Up/Down-Count Conditions in Phase Counting Mode 2
TCLKA (Channel 1) TCLKC (Channel 2) High level Low level Low level High level High level Low level High level Low level Notes: : Rising edge : Falling edge TCLKB (Channel 1) TCLKD (Channel 2) Operation Don't care Don't care Don't care Up-count Don't care Don't care Don't care Down-count
Rev. 2.00 Mar 09, 2006 page 728 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* Phase counting mode 3 Figure 17.28 shows an example of phase counting mode 3 operation, and table 17.10 summarizes the TCNT up/down-count conditions.
TCLKA (channel 1) TCLKC (channel 2) TCLKB (channel 1) TCLKD (channel 2) TCNT value
Up-count
Down-count
Time
Figure 17.28 Example of Phase Counting Mode 3 Operation Table 17.10 Up/Down-Count Conditions in Phase Counting Mode 3
TCLKA (Channel 1) TCLKC (Channel 2) High level Low level Low level High level High level Low level High level Low level Notes: : Rising edge : Falling edge TCLKB (Channel 1) TCLKD (Channel 2) Operation Don't care Don't care Don't care Up-count Down-count Don't care Don't care Don't care
Rev. 2.00 Mar 09, 2006 page 729 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
* Phase counting mode 4 Figure 17.29 shows an example of phase counting mode 4 operation, and table 17.11 summarizes the TCNT up/down-count conditions.
TCLKA (channel 1) TCLKC (channel 2) TCLKB (channel 1) TCLKD (channel 2) TCNT value Down-count
Up-count
Time
Figure 17.29 Example of Phase Counting Mode 4 Operation Table 17.11 Up/Down-Count Conditions in Phase Counting Mode 4
TCLKA (Channel 1) TCLKC (Channel 2) High level Low level Low level High level High level Low level High level Low level Notes: : Rising edge : Falling edge Don't care Down-count Don't care TCLKB (Channel 1) TCLKD (Channel 2) Operation Up-count
Rev. 2.00 Mar 09, 2006 page 730 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.5
17.5.1
Interrupts
Interrupt Sources and Priorities
There are three kinds of TPU interrupt source: TGR input capture/compare match, TCNT overflow, and TCNT underflow. Each interrupt source has its own status flag and enable/disabled bit, allowing generation of interrupt request signals to be enabled or disabled individually. When an interrupt request is generated, the corresponding status flag in TSR is set to 1. If the corresponding enable/disable bit in TIER is set to 1 at this time, an interrupt is requested. The interrupt request is cleared by clearing the status flag to 0. Relative channel priorities can be changed by the interrupt controller, but the priority order within a channel is fixed. For details, see section 5, Interrupt Controller (INTC). Table 17.12 lists the TPU interrupt sources. Table 17.12 TPU Interrupts
Channel 0 Interrupt Source TGI0A TGI0B TGI0C TGI0D TCI0V 1 TGI1A TGI1B TCI1V TCI1U 2 TGI2A TGI2B TCI2V TCI2U Description TGR0A input capture/compare match TGR0B input capture/compare match TGR0C input capture/compare match TGR0D input capture/compare match TCNT0 overflow TGR1A input capture/compare match TGR1B input capture/compare match TCNT1 overflow TCNT1 underflow TGR2A input capture/compare match TGR2B input capture/compare match TCNT2 overflow TCNT2 underflow DMAC Activation Possible Possible Possible Possible Not possible Not possible Not possible Not possible Not possible Not possible Not possible Not possible Not possible Low Priority High
Note: This table shows the initial state immediately after a reset. The relative channel priorities can be changed by the interrupt controller.
Rev. 2.00 Mar 09, 2006 page 731 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Input Capture/Compare Match Interrupt: An interrupt is requested if the TGIE bit in TIER is set to 1 when the TGF flag in TSR is set to 1 by the occurrence of a TGR input capture/compare match on a particular channel. The interrupt request is cleared by clearing the TGF flag to 0. The TPU has 8 input capture/compare match interrupts, four for channel 0, and two each for channels 1, and 2. Overflow Interrupt: An interrupt is requested if the TCIEV bit in TIER is set to 1 when the TCFV flag in TSR is set to 1 by the occurrence of TCNT overflow on a particular channel. The interrupt request is cleared by clearing the TCFV flag to 0. The TPU has three overflow interrupts, one for each channel. Underflow Interrupt: An interrupt is requested if the TCIEU bit in TIER is set to 1 when the TCFU flag in TSR is set to 1 by the occurrence of TCNT underflow on channel. The interrupt request is cleared by clearing the TCFU flag to 0. The TPU has two underflow interrupts, one each for channels 1 and 2. 17.5.2 DMAC Activation
The DMAC can be activated by the TGR input capture/compare match interrupt for a channel. For details, see section 11, Direct Memory Access Controller (DMAC). A total of four TPU input capture/compare match interrupts can be used as DMAC activation sources for channel 0.
Rev. 2.00 Mar 09, 2006 page 732 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.6
17.6.1
Operation Timing
Input/Output Timing
TCNT Count Timing: Figure 17.30 shows TCNT count timing in internal clock operation, and figure 17.31 shows TCNT count timing in external clock operation.
P
Internal clock
Falling edge
Rising edge
TCNT input clock TCNT N-1 N N+1 N+2
Figure 17.30 Count Timing in Internal Clock Operation
P
External clock
Falling edge
Rising edge
Falling edge
TCNT input clock TCNT N-1 N N+1 N+2
Figure 17.31 Count Timing in External Clock Operation
Rev. 2.00 Mar 09, 2006 page 733 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Output Compare Output Timing: A compare match signal is generated in the final state in which TCNT and TGR match (the point at which the count value matched by TCNT is updated). When a compare match signal is generated, the output value set in TIOR is output at the output compare output pin (TIOC pin). After a match between TCNT and TGR, the compare match signal is not generated until the TCNT input clock is generated. Figure 17.32 shows output compare output timing.
P
TCNT input clock TCNT N N+1
TGR
N
Compare match signal TIOC pin
Figure 17.32 Output Compare Output Timing Input Capture Signal Timing: Figure 17.33 shows input capture signal timing.
P Input capture input Input capture signal
TCNT
N
N+1
N+2
TGR
N
N+2
Figure 17.33 Input Capture Input Signal Timing
Rev. 2.00 Mar 09, 2006 page 734 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Timing for Counter Clearing by Compare Match/Input Capture: Figure 17.34 shows the timing when counter clearing by compare match occurrence is specified, and figure 17.35 shows the timing when counter clearing by input capture occurrence is specified.
P
Compare match signal Counter clear signal N H'0000
TCNT
TGR
N
Figure 17.34 Counter Clear Timing (Compare Match)
P Input capture signal
Counter clear signal N H'0000
TCNT
TGR
N
Figure 17.35 Counter Clear Timing (Input Capture)
Rev. 2.00 Mar 09, 2006 page 735 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Buffer Operation Timing: Figures 17.36 and 17.37 show the timing in buffer operation.
P
TCNT
n
n+1
Compare match signal TGRA, TGRB TGRC, TGRD
n
N
N
Figure 17.36 Buffer Operation Timing (Compare Match)
P Input capture signal
TCNT TGRA, TGRB TGRC, TGRD
N
N+1
n
N
N+1
n
N
Figure 17.37 Buffer Operation Timing (Input Capture)
Rev. 2.00 Mar 09, 2006 page 736 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.6.2
Interrupt Signal Timing
TGF Flag Setting Timing in Case of Compare Match: Figure 17.38 shows the timing for setting of the TGF flag in TSR by compare match occurrence, and TGI interrupt request signal timing.
P
TCNT input clock
TCNT
N
N+1
TGR
N
Compare match signal
TGF flag
TGI interrupt
Figure 17.38 TGI Interrupt Timing (Compare Match)
Rev. 2.00 Mar 09, 2006 page 737 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
TGF Flag Setting Timing in Case of Input Capture: Figure 17.39 shows the timing for setting of the TGF flag in TSR by input capture occurrence, and TGI interrupt request signal timing.
P Input capture signal
TCNT
N
TGR
N
TGF flag
TGI interrupt
Figure 17.39 TGI Interrupt Timing (Input Capture) TCFV Flag/TCFU Flag Setting Timing: Figure 17.40 shows the timing for setting of the TCFV flag in TSR by overflow occurrence, and TCIV interrupt request signal timing. Figure 17.41 shows the timing for setting of the TCFU flag in TSR by underflow occurrence, and TCIU interrupt request signal timing.
P
TCNT input clock TCNT (overflow) Overflow signal TCFV flag
H'FFFF
H'0000
TCIV interrupt
Figure 17.40 TCIV Interrupt Setting Timing
Rev. 2.00 Mar 09, 2006 page 738 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
P
TCNT input clock TCNT (underflow) Underflow signal
H'0000
H'FFFF
TCFU flag
TCIU interrupt
Figure 17.41 TCIU Interrupt Setting Timing Status Flag Clearing Timing: After a status flag is read as 1 by the CPU, it is cleared by writing 0 to it. When the DMAC is activated, the flag is cleared automatically. Figure 17.42 shows the timing for status flag clearing by the CPU, and figure 17.43 shows the timing for status flag clearing by the DMAC.
TSR write cycle T1 T2 P
Address
TSR address
Write signal
Status flag
Interrupt request signal
Figure 17.42 Timing for Status Flag Clearing by CPU
Rev. 2.00 Mar 09, 2006 page 739 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
DMAC read cycle T1 P T2 DMAC write cycle T1 T2
Address
Source address
Destination address
Status flag
Interrupt request signal
Figure 17.43 Timing for Status Flag Clearing by DMAC Activation
17.7
Usage Notes
Note that the kinds of operation and contention described below occur during TPU operation. Input Clock Restrictions: The input clock pulse width must be at least 1.5 states in the case of single-edge detection, and at least 2.5 states in the case of both-edge detection. The TPU will not operate properly with a narrower pulse width. In phase counting mode, the phase difference and overlap between the two input clocks must be at least 1.5 states, and the pulse width must be at least 2.5 states. Figure 17.44 shows the input clock conditions in phase counting mode.
Phase Phase differdifference Overlap ence
Overlap TCLKA (TCLKC) TCLKB (TCLKD)
Pulse width
Pulse width
Pulse width
Pulse width
Notes: Phase difference and overlap : 1.5 states or more Pulse width : 2.5 states or more
Figure 17.44 Phase Difference, Overlap, and Pulse Width in Phase Counting Mode
Rev. 2.00 Mar 09, 2006 page 740 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Caution on Period Setting: When counter clearing by compare match is set, TCNT is cleared in the final state in which it matches the TGR value (the point at which the count value matched by TCNT is updated). Consequently, the actual counter frequency is given by the following formula:
f= P (N + 1)
Where
f : Counter frequency P : Peripheral module clock N : TGR set value
Contention between TCNT Write and Clear Operations: If the counter clear signal is generated in the T2 state of a TCNT write cycle, TCNT clearing takes precedence and the TCNT write is not performed. Figure 17.45 shows the timing in this case.
TCNT write cycle T1 T2 P
Address
TCNT address
Write signal Counter clear signal
TCNT
N
H'0000
Figure 17.45 Contention between TCNT Write and Clear Operations
Rev. 2.00 Mar 09, 2006 page 741 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between TCNT Write and Increment Operations: If incrementing occurs in the T2 state of a TCNT write cycle, the TCNT write takes precedence and TCNT is not incremented. Figure 17.46 shows the timing in this case.
TCNT write cycle T1 T2 P
Address
TCNT address
Write signal TCNT input clock N TCNT write data M
TCNT
Figure 17.46 Contention between TCNT Write and Increment Operations
Rev. 2.00 Mar 09, 2006 page 742 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between TGR Write and Compare Match: If a compare match occurs in the T2 state of a TGR write cycle, the TGR write takes precedence and the compare match signal is inhibited. A compare match does not occur even if the same value as before is written. Figure 17.47 shows the timing in this case.
TGR write cycle T1 T2 P Address TGR address
Write signal Compare match signal TCNT N N+1
Inhibited
TGR
N TGR write data
M
Figure 17.47 Contention between TGR Write and Compare Match
Rev. 2.00 Mar 09, 2006 page 743 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between Buffer Register Write and Compare Match: If a compare match occurs in the T2 state of a TGR write cycle, the data transferred to TGR by the buffer operation will be the write data. Figure 17.48 shows the timing in this case.
TGR write cycle T1 T2 P Address Buffer register address
Write signal Compare match signal Buffer register write data Buffer register TGR N M
M
Figure 17.48 Contention between Buffer Register Write and Compare Match
Rev. 2.00 Mar 09, 2006 page 744 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between TGR Read and Input Capture: If the input capture signal is generated in the T1 state of a TGR read cycle, the data that is read will be the data before input capture transfer. Figure 17.49 shows the timing in this case.
TGR read cycle T1 T2 P Address TGR address
Read signal Input capture signal TGR Internal data bus N M
N
Figure 17.49 Contention between TGR Read and Input Capture
Rev. 2.00 Mar 09, 2006 page 745 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between TGR Write and Input Capture: If the input capture signal is generated in the T2 state of a TGR write cycle, the input capture operation takes precedence and the write to TGR is not performed. Figure 17.50 shows the timing in this case.
TGR write cycle T1 T2 P Address TGR address
Write signal Input capture signal TCNT M
TGR
M
Figure 17.50 Contention between TGR Write and Input Capture
Rev. 2.00 Mar 09, 2006 page 746 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between Buffer Register Write and Input Capture: If the input capture signal is generated in the T2 state of a buffer register write cycle, the buffer operation takes precedence and the write to the buffer register is not performed. Figure 17.51 shows the timing in this case.
Buffer register write cycle T1 T2 P Address Buffer register address
Write signal Input capture signal TCNT N
TGR Buffer register
M
N
M
Figure 17.51 Contention between Buffer Register Write and Input Capture
Rev. 2.00 Mar 09, 2006 page 747 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between Overflow/Underflow and Counter Clearing: If overflow/underflow and counter clearing occur simultaneously, the TCFV/TCFU flag in TSR is not set and TCNT clearing takes precedence. Figure 17.52 shows the operation timing when a TGR compare match is specified as the clearing source, and H'FFFF is set in TGR.
P TCNT input clock TCNT Counter clear signal TGF Disabled TCFV H'FFFF H'0000
Figure 17.52 Contention between Overflow and Counter Clearing
Rev. 2.00 Mar 09, 2006 page 748 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
Contention between TCNT Write and Overflow/Underflow: If there is an up-count or downcount in the T2 state of a TCNT write cycle, and overflow/underflow occurs, the TCNT write takes precedence and the TCFV/TCFU flag in TSR is not set . Figure 17.53 shows the operation timing in the case of contention between a TCNT write and overflow.
TCNT write cycle T1 T2 P
Address
TCNT address
Write signal
TCNT write data H'FFFF Disabled M
TCNT
TCFV flag
Figure 17.53 Contention between TCNT Write and Overflow Multiplexing of I/O Pins: In the Chip, the TCLKA input pin is multiplexed with the TIOCC0 I/O pin, the TCLKB input pin with the TIOCD0 I/O pin, the TCLKC input pin with the TIOCB1 I/O pin, and the TCLKD input pin with the TIOCB2 I/O pin. When an external clock is input, compare match output should not be performed from a multiplexed pin. Interrupts and Module Stop Mode: If module stop mode is entered when an interrupt has been requested, it will not be possible to clear the CPU interrupt source or DMAC activation source. Interrupts should therefore be disabled before entering module stop mode.
Rev. 2.00 Mar 09, 2006 page 749 of 906 REJ09B0292-0200
Section 17 16-Bit Timer Pulse Unit (TPU)
17.8
17.8.1
Usage Notes
Clearing Flags in TSR0 to TSR2
When bits TCFV, TGFD, TGFC, TGFB, and TGFA in TSR0, and bits TCFU, TCFV, TGFB, and TGFA in TSR1 and TSR2, are cleared, it may happen that the interrupt request in the internal logic cannot be cleared although the flag is cleared. In this case, if interrupt acceptance is enabled, another interrupt will be generated. Either of the following measures should therefore be taken when clearing flags in TSR0 to TSR2. 1. Execute clearing while the TPU timer is counting up. 2. If clearing when the TPU timer is stopped, write 0 to the flag again after executing clearing. DMA Transfer by TPU0
17.8.2
When DMA transfer is performed by means of TPU channel 0 compare match or input capture, internal logic interrupt requests (transfer requests) may not be cleared correctly. Therefore, it may not be possible to execute DMA transfer when a subsequent transfer request is generated by TPU channel 0 compare match or input capture. Either of the following measures should therefore be taken when performing DMA transfer by means of TPU channel 0 compare match or input capture. 1. Do not set on-chip RAM as the DMA transfer source or destination. 2. When on-chip RAM has not been set as the DMA transfer source or destination, execute the transfer while the TPU channel 0 timer is counting up.
Rev. 2.00 Mar 09, 2006 page 750 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
Section 18 User Debug Interface (H-UDI)
18.1 Overview
The user debug interface (H-UDI) provides data transfer and interrupt request functions. The HUDI performs serial transfer by means of external signal control. 18.1.1 Features
The H-UDI has the following features conforming to the IEEE 1149.1 standard. * Five test signals (TCK, TDI, TDO, TMS, and TRST) * TAP controller * Instruction register * Data register * Bypass register * Boundary scan register The H-UDI has seven instructions. * Bypass mode Test mode conforming to IEEE 1149.1 * EXTEST mode Test mode corresponding to IEEE1149.1. * SAMPLE/PRELOAD mode Test mode corresponding to IEEE1149.1. * CLAMP mode Test mode corresponding to IEEE1149.1. * HIGHZ mode Test mode corresponding to IEEE1149.1. * IDCODE mode Test mode corresponding to IEEE1149.1. * H-UDI interrupt H-UDI interrupt request to INTC This chip does not support test modes other than bypass mode.
Rev. 2.00 Mar 09, 2006 page 751 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.1.2
H-UDI Block Diagram
Figure 18.1 shows a block diagram of the H-UDI.
TCK
TMS
TAP controller
Internal bus controller
H-UDI interrupt signal
TRST
TDI
Decoder
SDIR
Peripheral bus
Shift register
SDSR
SDBPR
SDBSR
SDDRH
16 SDDRL
SDIDR
TDO Mux
SDIR: SDSR: SDDRH: SDDRL: SDBPR: SDBSR:
Instruction register Status register Data register H Data register L Bypass register Boundary scan register
TCK: TMS: TRST: TDI: TDO: SDIDR:
Test clock Test mode select Test reset Test data input Test data output ID code register
Figure 18.1 H-UDI Block Diagram
Rev. 2.00 Mar 09, 2006 page 752 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.1.3
Pin Configuration
Table 18.1 shows the H-UDI pin configuration. Table 18.1 Pin Configuration
Pin Name Test clock Test mode select Test data input Test data output Test reset Abbreviation TCK TMS TDI TDO TRST I/O Input Input Input Output Input Function Test clock input Test mode select input signal Serial data input Serial data output Test reset input signal
18.1.4
Register Configuration
Table 18.2 shows the H-UDI registers. Table 18.2 Register Configuration
Register Instruction register Status register Data register H Data register L Bypass register Boundary scan register ID code register Abbreviation SDIR SDSR SDDRH SDDRL SDBPR SDBSR SDIDR
1 R/W*
Initial Value* H'E000 H'0701 Undefined Undefined -- -- H'0005200F
2
Address H'FFFFFCB0 H'FFFFFCB2 H'FFFFFCB4 H'FFFFFCB6 -- -- --
Access Size (Bits) 8/16/32 8/16/32 8/16/32 8/16/32 -- -- --
R R/W R/W R/W -- -- --
Notes: 1. Indicates whether the register can be read/written to by the CPU. 2. Initial value when the TRST signal is input. Registers are not initialized by a reset (power-on or manual) or in standby mode.
Instructions and data can be input to the instruction register (SDIR) and data register (SDDR) by serial transfer from the test data input pin (TDI). Data from SDIR, the status register (SDSR), and SDDR can be output via the test data output pin (TDO). The bypass register (SDBPR) is a 1-bit register to which TDI and TDO are connected in bypass mode. The boundary scan register (SDBSR) is a 330-bit register, and is connected to TDI and TDO in the SAMPLE/PRELOAD or EXTEST mode. The ID code register (SDIDR) is a 32-bit register; a fixed code can be output via
Rev. 2.00 Mar 09, 2006 page 753 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
TDO in the IDCODE mode. All registers, except SDBPR, SDBSR, and SDIDR, can be accessed from the CPU. Table 18.3 shows the kinds of serial transfer possible with each register. Table 18.3 H-UDI Register Serial Transfer
Register SDIR SDSR SDDRH SDDRL SDBPR SDBSR SDIDR Serial Input Possible Impossible Possible Possible Possible Possible Impossible Serial Output Possible Possible Possible Possible Possible Possible Possible
18.2
18.2.1
External Signals
Test Clock (TCK)
The test clock pin (TCK) provides an independent clock supply to the H-UDI. As the clock input to TCK is supplied directly to the H-UDI, a clock waveform with a duty cycle close to 50% should be input (for details, see section 22, Electrical Characteristics). If no clock is input, TCK is fixed at 1 by internal pull-up. 18.2.2 Test Mode Select (TMS)
The test mode select pin (TMS) is sampled on the rise of TCK. TMS controls the internal state of the TAP controller. If no signal is input, TMS is fixed at 1 by internal pull-up. 18.2.3 Test Data Input (TDI)
The test data input pin (TDI) performs serial input of instructions and data for H-UDI registers. TDI is sampled on the rise of TCK. If no signal is input, TDI is fixed at 1 by internal pull-up.
Rev. 2.00 Mar 09, 2006 page 754 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.2.4
Test Data Output (TDO)
The test data output pin (TDO) performs serial output of instructions and data from H-UDI registers. Transfer is performed in synchronization with TCK. If there is no output, TDO goes to the high-impedance state. 18.2.5 Test Reset (TRST TRST) TRST
The test reset pin (TRST) initializes the H-UDI asynchronously. If no signal is input, TRST is fixed at 1 by internal pull-up.
18.3
18.3.1
Register Descriptions
Instruction Register (SDIR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 TS3 1 R 7 -- 0 R 14 TS2 1 R 6 -- 0 R 13 TS1 1 R 5 -- 0 R 12 TS0 0 R 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 0 R 2 -- 0 R 9 -- 0 R 1 -- 0 R 8 -- 0 R 0 -- 0 R
The instruction register (SDIR) is a 16-bit register that can only be read by the CPU. H-UDI instructions can be transferred to SDIR by serial input from TDI. SDIR can be initialized by the TRST signal, but is not initialized by a reset or in standby mode. SDIR defines 4 valid bits for instruction. If an instruction exceeding 4 bits is input, the last 4 bits of the serial data will be stored in SDIR. Operation is not guaranteed if a reserved instruction is set in this register. Bits 15 to 12--Test Set Bits (TS3-TS0): Table 18.4 shows the instruction configuration.
Rev. 2.00 Mar 09, 2006 page 755 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
Table 18.4 Instruction Configuration
Bit 15: TS3 0 Bit 14: TS2 0 Bit 13: TS1 0 1 1 0 1 1 0 0 1 1 0 1 Bit 12: TS0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Description EXTEST mode Reserved CLAMP mode HIGHZ mode SAMPLE/PRELOAD mode Reserved Reserved Reserved Reserved Reserved H-UDI interrupt Reserved Reserved Reserved IDCODE mode BYPASS mode (Initial value)
Bits 11 to 0--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 756 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.3.2
Status Register (SDSR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 -- 0 R 14 -- 0 R 6 -- 0 R 13 -- 0 R 5 -- 0 R 12 -- 0 R 4 -- 0 R 11 -- 0 R 3 -- 0 R 10 -- 1 R 2 -- 0 R 9 -- 1 R 1 -- 0 R 8 -- 1 R 0 SDTRF 1 R/W
The status register (SDSR) is a 16-bit register that can be read and written to by the CPU. Output from TDO is possible for SDSR, but serial data cannot be written to SDSR via TDI. The SDTRF bit is output by means of a 1-bit shift. In the case of a 2-bit shift, the SDTRF bit is first output, followed by a reserved bit. SDSR is initialized by TRST signal input, but is not initialized by a reset or in standby mode. Bits 15 to 1--Reserved: Bits 15 to 11 and 7 to 1 are always read as 0, and the write value should always be 0. Bits 10 to 8 are always read as 1, and the write value should always be 1. Bit 0--Serial Data Transfer Control Flag (SDTRF): Indicates whether H-UDI registers can be accessed by the CPU. The SDTRF bit is reset by the TRST signal , but is not initialized by a reset or in standby mode.
Bit 0: SDTRF 0 1 Description Serial transfer to SDDR has ended, and SDDR can be accessed Serial transfer to SDDR in progress (Initial value)
Rev. 2.00 Mar 09, 2006 page 757 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.3.3
Data Register (SDDR)
The data register (SDDR) comprises data register H (SDDRH) and data register L (SDDRL), each of which has the following configuration.
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- R/W 7 -- R/W 14 -- R/W 6 -- R/W 13 -- R/W 5 -- R/W 12 -- R/W 4 -- R/W 11 -- R/W 3 -- R/W 10 -- R/W 2 -- R/W 9 -- R/W 1 -- R/W 8 -- R/W 0 -- R/W
SDDRH and SDDRL are 16-bit registers that can be read and written to by the CPU. SDDR is connected to TDO and TDI for serial data transfer to and from an external device. 32-bit data is input and output in serial data transfer. If data exceeding 32 bits is input, only the last 32 bits will be stored in SDDR. Serial data is input starting from the MSB of SDDR (bit 15 of SDDRH), and output starting from the LSB (bit 0 of SDDRL). This register is not initialized by a reset, in standby mode, or by the TRST signal. 18.3.4 Bypass Register (SDBPR)
The bypass register (SDBPR) is a one-bit shift register. In bypass mode, SDBPR is connected to TDI and TDO, and the chip is excluded from the board test when a boundary scan test is conducted. SDBPR cannot be read or written to by the CPU. 18.3.5 Boundary scan register (SDBSR)
The boundary scan register (SDBSR), a shift register that controls the I/O terminals of this LSI, is provided on the PAD. Using the EXTEST mode or the SAMPLE/PRELOAD mode, a boundary scan test conforming to the IEEE1149.1 standard can be performed. For SDBSR, read/write by the CPU cannot be performed.
Rev. 2.00 Mar 09, 2006 page 758 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
Table 18.5 shows the relationship between the terminals of the LSI and the boundary scan register. Table 18.5 Correspondence between Pins and Boundary Scan Register Bits
Pin No. from TDI 34 D0 Input Output Output enable 36 D1 Input Output Output enable 37 D2 Input Output Output enable 38 D3 Input Output Output enable 39 D4 Input Output Output enable 40 D5 Input Output Output enable 41 D6 Input Output Output enable 43 D7 Input Output Output enable 44 D8 Input Output Output enable 46 D9 Input Output Output enable 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 Pin Name Input/Output Bit No.
Rev. 2.00 Mar 09, 2006 page 759 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 47 Pin Name D10 Input/Output Input Output Output enable 48 D11 Input Output Output enable 49 D12 Input Output Output enable 51 D13 Input Output Output enable 53 D14 Input Output Output enable 54 D15 Input Output Output enable 55 D16 Input Output Output enable 56 D17 Input Output Output enable 57 D18 Input Output Output enable 59 D19 Input Output Output enable Bit No. 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270
Rev. 2.00 Mar 09, 2006 page 760 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 62 Pin Name D20 Input/Output Input Output Output enable 63 D21 Input Output Output enable 64 D22 Input Output Output enable 65 D23 Input Output Output enable 68 D24 Input Output Output enable 70 D25 Input Output Output enable 71 D26 Input Output Output enable 72 D27 Input Output Output enable 73 D28 Input Output Output enable 74 D29 Input Output Output enable Bit No. 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240
Rev. 2.00 Mar 09, 2006 page 761 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 75 Pin Name D30 Input/Output Input Output Output enable 77 D31 Input Output Output enable 80 82 83 84 85 86 87 88 90 92 93 94 A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Bit No. 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210
Rev. 2.00 Mar 09, 2006 page 762 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 95 96 97 98 100 102 103 104 105 106 107 108 111 115 117 118 Pin Name A12 A13 A14 A15 A16 A17 A18 A19 A20 A21 A22 A23 A24 WAIT RAS CAS Input/Output Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Input Output Output enable Output Output enable Bit No. 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179
Rev. 2.00 Mar 09, 2006 page 763 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 119 120 121 122 123 124 125 126 127 128 129 131 133 134 135 Pin Name DQMUU/WE3 DQMUL/WE2 DQMLU/WE1 DQMLL/WE0 CAS3 CAS2 CAS1 CAS0 CKE RD REFOUT BS RD/WR CS0 CS1 Input/Output Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Bit No. 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149
Rev. 2.00 Mar 09, 2006 page 764 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 136 137 138 139 140 141 142 143 144 145 148 151 Pin Name CS2 CS3 CS4 BUSHIZ BH DREQ1 DREQ0 DACK1 DACK0 BRLS BGR PB15 Input/Output Output Output enable Output Output enable Output Output enable Input Output Output enable Input Input Output Output enable Output Output enable Input Output Output enable Input Output Output enable 152 PB14 Input Output Output enable 153 PB13 Input Output Output enable 154 PB12 Input Output Output enable Bit No. 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119
Rev. 2.00 Mar 09, 2006 page 765 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 156 Pin Name PB11 Input/Output Input Output Output enable 158 PB10 Input Output Output enable 159 PB9 Input Output Output enable 160 PB8 Input Output Output enable 161 PB7 Input Output Output enable 162 PB6 Input Output Output enable 163 PB5 Input Output Output enable 164 PB4 Input Output Output enable 165 PB3 Input Output Output enable 166 PB2 Input Output Output enable Bit No. 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89
Rev. 2.00 Mar 09, 2006 page 766 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 168 Pin Name PB1 Input/Output Input Output Output enable 170 PB0 Input Output Output enable 171 PA13 Input Output Output enable 172 PA12 Input Output Output enable 173 PA11 Input Output Output enable 174 PA10 Input Output Output enable 175 PA9 Input Output Output enable 176 PA8 Input Output Output enable 177 PA7 Input Output Output enable 178 PA6 Input Output Output enable Bit No. 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
Rev. 2.00 Mar 09, 2006 page 767 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 180 Pin Name PA5 Input/Output Input Output Output enable 182 PA4 Input Output Output enable 183 184 CKPO PA2 Output Output enable Input Output Output enable 185 PA1 Input Output Output enable 186 PA0 Input Output Output enable 187 188 189 190 192 194 195 196 197 198 RX-ER RX-DV COL CRS RX-CLK ERXD0 ERXD1 ERXD2 ERXD3 MDIO Input Input Input Input Input Input Input Input Input Input Output Output enable 199 MDC Output Output enable Bit No. 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28
Rev. 2.00 Mar 09, 2006 page 768 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI) Pin No. 201 203 204 205 206 207 208 1 2 3 4 5 13 14 15 16 17 24 25 27 to TDO Note: The output enable signals are active-low. When an output enable signal is driven low, the corresponding pin is driven. The exception is the output enable signal for the MDIO pin, which is active-high. Pin Name TX-CLK TX-EN ETXD0 ETXD1 ETXD2 ETXD3 TX-ER IRL3 IRL2 IRL1 IRL0 NMI MD4 MD3 MD2 MD1 MD0 CKPREQ/CKM CKPACK IVECF Input/Output Input Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Output Output enable Input Input Input Input Input Input Input Input Input Input Input Output Output enable Output Output enable Bit No. 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Rev. 2.00 Mar 09, 2006 page 769 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.3.6
ID code register (SDIDR)
The ID code register (SDIDR) is a 32-bit register. In the IDCODE mode, SDIDR can output H'0005200F, which is a fixed code, from TDO. However, no serial data can be written to SDIDR via TDI. For SDIDR, read/write by the CPU cannot be performed.
31 0000 Version (4 bits) 28 27 0001 0000 0101 Part Number (16 bits) 12 0010 11 0000 0000 Manufacture Identify (11 bits) 1 111 0 1 Fixed Code (1 bit)
Rev. 2.00 Mar 09, 2006 page 770 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.4
18.4.1
Operation
TAP Controller
Figure 18.2 shows the internal states of TAP controller. State transitions basically conform with the JTAG standard.
1
Test-logic-reset 0 1 Select-DR-scan 1 Select-IR-scan 0 1 Capture-DR 0 Shift-DR 1 Exit1-DR 0 Pause-DR 1 0 Exit2-DR 1 Update-DR 1 0 0 1 1 Capture-IR 0 Shift-IR 1 Exit1-IR 0 Pause-IR 1 0 Exit2-IR 1 Update-IR 1 0 0 1 1
0
Run-test/idle
0
0
Figure 18.2 TAP Controller State Transitions
Rev. 2.00 Mar 09, 2006 page 771 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.4.2
H-UDI Interrupt and Serial Transfer
When an H-UDI interrupt instruction is transferred to SDIR via TDI, an interrupt is generated. Data transfer can be controlled by means of the H-UDI interrupt service routine. Transfer can be performed by means of SDDR. Control of data input/output between an external device and the H-UDI is performed by monitoring the SDTRF bit in SDSR externally and internally. Internal SDTRF bit monitoring is carried out by having SDSR read by the CPU. The H-UDI interrupt and serial transfer procedure is as follows. 1. An instruction is input to SDIR by serial transfer, and an H-UDI interrupt request is generated. 2. After the H-UDI interrupt request is issued, the SDTRF bit in SDSR is monitored externally. After output of SDTRF = 1 from TDO is observed, serial data is transferred to SDDR. 3. On completion of the serial transfer to SDDR, the SDTRF bit is cleared to 0, and SDDR can be accessed by the CPU. After SDDR has been accessed, SDDR serial transfer is enabled by setting the SDTRF bit to 1 in SDSR. 4. Serial data transfer between an external device and the H-UDI can be carried out by constantly monitoring the SDTRF bit in SDSR externally and internally.
Figures 18.3, 18.4, and 18.5 show the timing of data transfer between an external device and the H-UDI.
Rev. 2.00 Mar 09, 2006 page 772 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
Serial data
Instruction SDTRF 1
Input 0 1
Input/ output
H-UDI interrupt request Shift disabled SDTRF (in SDSR)*1 SDSR and SDDR MUX*2 SDDR access state Shift enabled SDSR SDDR Shift enabled SDSR SDDR
Shift
CPU
Shift
CPU
SDSR serial transfer (monitoring) Notes: 1. SDTRF flag (in SDSR): Indicates whether SDDR access by the CPU or serial transfer data input/output to SDDR is possible. 1 2 SDDR is shift-disabled. SDDR access by the CPU is enabled. SDDR is shift-enabled. Do not access SDDR until SDTRF = 0. Conditions: * SDTRF = 1 -- When TRST = 0 -- When the CPU writes 1 -- In bypass mode * SDTRF = 0 -- End of SDDR shift access in serial transfer 2. SDSR/SDDR (Update-DR state) internal MUX switchover timing * Switchover from SDSR to SDDR: On completion of serial transfer in which SDTRF = 1 is output from TDO * Switchover from SDDR to SDSR: On completion of serial transfer to SDDR
Figure 18.3 Data Input/Output Timing Chart (1)
Rev. 2.00 Mar 09, 2006 page 773 of 906 REJ09B0292-0200
TDI
TCK
TMS
TDO
TDI
Select-DR Capture-DR Shift-DR Exit1-DR Update-DR Select-DR Capture-DR Shift-DR
TS0
TCK
TMS
TRST
TDO
Test-Logic-Reset Run-Test/Idle Select-DR Select-IR Capture-IR Shift-IR
TS3
TRST
SDTRF
Bit 0
Bit 0
Rev. 2.00 Mar 09, 2006 page 774 of 906 REJ09B0292-0200
Exit1-DR Update-DR Select-DR Capture-DR Shift-DR Exit1-DR Update-DR Select-DR Capture-DR Shift-DR Exit1-DR Update-DR
Section 18 User Debug Interface (H-UDI)
Bit 31
Bit 31
Exit1-IR Update-IR Select-DR Capture-DR
SDTRF
SDTRF
Figure 18.5 Data Input/Output Timing Chart (3)
Figure 18.4 Data Input/Output Timing Chart (2)
Shift-DR Exit1-DR Update-DR Run-Test/Idle
Bit 0
Bit 0
Bit 31
Bit 31
Test-Logic-Reset
Section 18 User Debug Interface (H-UDI)
18.4.3
H-UDI Reset
The H-UDI can be reset in two ways. * The H-UDI is reset when the TRST signal is held at 0. * When TRST = 1, the H-UDI can be reset by inputting at least five TCK clock cycles while TMS = 1.
18.5
Boundary Scan
The H-UDI pins can be placed in the boundary scan mode stipulated by IEEE1149.1 by setting a command in SDIR. 18.5.1 Supported Instructions
The SH7616 supports the three essential instructions defined in IEEE1149.1 (BYPASS, SAMPLE/PRELOAD, and EXTEST) and optional instructions (CLAMP, HIGHZ, and IDCODE). BYPASS: The BYPASS instruction is an essential standard instruction that operates the bypass register. This instruction shortens the shift path to speed up serial data transfer involving other chips on the printed circuit board. While this instruction is executing, the test circuit has no effect on the system circuits. The instruction code is 1111. SAMPLE/PRELOAD: The SAMPLE/PRELOAD instruction inputs values from the SH7616's internal circuitry to the boundary scan register, outputs values from the scan path, and loads data onto the scan path. When this instruction is executing, the SH7616's input pin signals are transmitted directly to the internal circuitry, and internal circuit values are directly output externally from the output pins. The SH7616's system circuits are not affected by execution of this instruction. The instruction code is 0100. In a SAMPLE operation, a snapshot of a value to be transferred from an input pin to the internal circuitry, or a value to be transferred from the internal circuitry to an output pin, is latched into the boundary scan register and read from the scan path. Snapshot latching is performed in synchronization with the rise of TCK in the Capture-DR state. Snapshot latching does not affect normal operation of the SH7616. In a PRELOAD operation, an initial value is set in the parallel output latch of the boundary scan register from the scan path prior to the EXTEST instruction. Without a PRELOAD operation, when the EXTEST instruction was executed an undefined value would be output from the output pin until completion of the initial scan sequence (transfer to the output latch) (with the EXTEST instruction, the parallel output latch value is constantly output to the output pin).
Rev. 2.00 Mar 09, 2006 page 775 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
EXTEST: This instruction is provided to test external circuitry when the SH7616 is mounted on a printed circuit board. When this instruction is executed, output pins are used to output test data (previously set by the SAMPLE/PRELOAD instruction) from the boundary scan register to the printed circuit board, and input pins are used to latch test results into the boundary scan register from the printed circuit board. If testing is carried out by using the EXTEST instruction N times, the Nth test data is scanned-in when test data (N-1) is scanned out. Data loaded into the output pin boundary scan register in the Capture-DR state is not used for external circuit testing (it is replaced by a shift operation). The instruction code is 0000. CLAMP: When the CLAMP instruction is enabled, the output pin outputs the value of the boundary scan register that has been set by the SAMPLE/PRELOAD instruction. While the CLAMP instruction is enabled, the state of the boundary scan register maintains the previous state regardless of the state of the TAP controller. A bypass register is connected between TDI and TDO. The related circuit operates in the same way when the BYPASS instruction is enabled. The instruction code is 0010. HIGHZ: When the HIGHZ instruction is enabled, all output pins enter a high-impedance state. While the HIGHZ instruction is enabled, the state of the boundary scan register maintains the previous state regardless of the state of the TAP controller. A bypass register is connected between TDI and TDO. The related circuit operates in the same way when the BYPASS instruction is enabled. The instruction code is 0010. IDCODE: When the IDCODE instruction is enabled, the value of the ID code register is output from TDO with LSB first when the TAP controller is in the Shift-DR state. While this instruction is being executed, the test circuit does not affect the system circuit. When the TAP controller is in the Test-Logic-Reset state, the instruction register is initialized to the IDCODE instruction. The instruction code is 0010.
Rev. 2.00 Mar 09, 2006 page 776 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
18.5.2
Notes on Use
1. Boundary scan mode does not cover clock-related signals (EXTAL, XTAL, CKIO, CAP1, CAP2). 2. Boundary scan mode does not cover reset-related signals (RES, ASEMODE). 3. Boundary scan mode does not cover H-UDI-related signals (TCK, TDI, TDO, TMS, TRST). 4. Fix the ASEMODE pin high.
18.6
Usage Notes
* A reset must always be executed by driving the TRST signal to 0, regardless of whether or not the H-UDI is to be activated. TRST must be held low for 20 TCK clock cycles. For details, see section 22, Electrical Characteristics. * The registers are not initialized in standby mode. If TRST is set to 0 in standby mode, bypass mode will be entered. * The frequency of TCK must be lower than that of the peripheral module clock (P). For details, see section 22, Electrical Characteristics. * In data transfer, data input/output starts with the LSB. Figure 18.6 shows serial data input/output. * When data that exceeds the number of bits of the register connected between TDI and TDO is serially transferred, the serial data that exceeds the number of register bits and output from TDO is the same as that input from TDI. * If the H-UDI serial transfer sequence is disrupted, a TRST reset must be executed. Transfer should then be retried, regardless of the transfer operation. * TDO is output at the falling edge of TCK when one of six instructions defined in IEEE1149.1 is selected. Otherwise, it is output at the rising edge of TCK.
Rev. 2.00 Mar 09, 2006 page 777 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
* SDIR and SDSR serial data input/output In Capture-IR, SDIR and SDSR are captured into the shift register, and in Shift-IR bits 0 to 15 of SDSR and bits 0 to 15 of SDIR are output in that order from TDO. In Update-IR, data input from TDI is written to SDIR, but not to SDSR. TDI Shift register SDIR Bit 16 Bit 15 SDSR Bit 0 Bit 31 Bit 15 TDI Shift register SDIR Bit 0 Bit 15 TDI input data SDSR Bit 0 Bit 0 Bit 16 Bit 15 SDSR Bit 31 Bit 15
. . .
. . .
Bit 0
SDIR
. . .
TDO
Capture-IR
TDO
Update-IR
Figure 18.6 Serial Data Input/Output (1)
Rev. 2.00 Mar 09, 2006 page 778 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
* SDDRH and SDDRL serial data input/output (1) In H-UDI interrupt mode, before SDTRF = 1 is read from TDO when an H-UDI interrupt is generated, SDSR and SDIR are captured into the shift register in Capture-DR, and in Shift-DR bits 0 to 15 of SDSR and bits 0 to 15 of SDIR are output in that order from TDO. In Update-DR, TDI input data is not written to any register. TDI Shift register SDIR Bit 16 Bit 15 SDSR Bit 0 Bit 31 Bit 15
. . .
Bit 0 Bit 15
SDIR
. . .
Bit 0
SDSR
TDO
Capture-DR
(2) In H-UDI interrupt mode, after SDTRF = 1 is read from TDO when an H-UDI interrupt is generated, SDDRH and SDDRL are captured into the shift register in Capture-DR, and in Shift-DR bits 0 to 15 of SDDRL and bits 0 to 15 of SDDRH are output in that order from TDO. Data input from TDI is written to SDDRH and SDDRL in Update-DR. TDI Shift register SDDRH Bit 16 Bit 15 SDDRL Bit 0 Bit 31 Bit 15 TDI Shift register SDDRH Bit 0 Bit 15 TDI input data SDDRL Bit 0 Bit 0 Bit 16 Bit 15 Bit 31 Bit 15
. . .
. . .
Bit 0 Bit 15
SDDRH
. . .
. . .
Bit 0
SDDRL
TDO
Capture-DR
TDO
Update-DR
Figure 18.6 Serial Data Input/Output (2)
Rev. 2.00 Mar 09, 2006 page 779 of 906 REJ09B0292-0200
Section 18 User Debug Interface (H-UDI)
* SDIDR serial data input/output In IDCODE mode, SDIDR is captured into the shift register in Capture-DR, and in Shift-DR bits 0 to 31 of SDIDR are output in that order from TDO. In Update-DR, data input from TDI is not written to any register. TDI Shift register Bit 31 Bit 15
SDIDR
. . . .
SDIDR
Bit 0
Bit 0
TDO
Capture-DR
Figure 18.6 Serial Data Input/Output (3)
Rev. 2.00 Mar 09, 2006 page 780 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Section 19 Pin Function Controller (PFC)
19.1 Overview
The pin function controller (PFC) consists of registers to select multiplexed pin functions and input/output direction. The pin function and input/output direction can be selected for individual pins regardless of the operating mode of the chip. Table 19.1 shows the chip's multiplex pins.
Rev. 2.00 Mar 09, 2006 page 781 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Table 19.1 Multiplex Pins
Function 1 [00]*
Signal Port Name A A A A A A A A A A A A A A B B B B B B B B B B B B B B B B PA13 PA12 PA11 PA10 PA9 PA8 PA6 PA5 PA4 CKPO PA2 PA1 PA0 PB15 PB14 PB13 PB12 PB11 PB10 PB9 PB8 PB7 PB6 PB5 PB4 PB3 PB2 PB1 PB0 I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O
Function 2 [01]*
I/O I I I I I/O O I/O I I O O I O -- -- -- I I I I I/O O I I I I I/O O --
Function 3 [10]*
I/O -- -- -- -- -- -- -- -- -- -- -- -- -- -- I/O I O O I I/O I/O I/O I/O I/O I O I/O I/O I/O I/O
Function 4 [11]*
I/O -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- O O -- -- -- -- -- -- -- -- -- -- O Related Module -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- BSC BSC -- -- -- -- -- -- -- -- -- -- EtherC
Related Signal Module Name Port Port Port Port Port Port WDT Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port Port SRCK0 SRS0 SRXD0 STCK0 STS0 STXD0 PA7 FTCI FTI FTOA FTOB LNKSTA EXOUT -- -- -- SRCK2 SRS2 SRXD2 STCK2 STS2 STXD2 SRCK1 SRS1 SRXD1 STCK1 STS1 STXD1 --
Related Signal Module Name SIO0 SIO0 SIO0 SIO0 SIO0 SIO0 Port FRT FRT FRT FRT EtherC EtherC EtherC -- -- -- SIO2 SIO2 SIO2 SIO2 SIO2 SIO2 SIO1 SIO1 SIO1 SIO1 SIO1 SIO1 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- SCK1 RXD1 TXD1 RTS CTS TIOCA1 TIOCB1 TIOCA2 TIOCB2 SCK2 RXD2 TXD2 TIOCA0 TIOCB0 TIOCC0 TIOCD0
Related Signal Module Name -- -- -- -- -- -- -- -- -- -- -- -- -- -- SCIF1 SCIF1 SCIF1 SCIF1 SCIF1 TPU1 TPU1 TPU2 TPU2 SCIF2 SCIF2 SCIF2 TPU2 TPU2 TPU2 TPU2 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- STATS1 STATS0 -- -- -- -- -- -- -- -- -- -- WOL
WDTOVF O
CAMSEN I
Notes: In the initial state, function 1 is selected. * The initial value is "input." The figures in brackets indicate the settings of the mode bits (MD1, MD0) in the PFC to select multiplexed functions in port A[0:13] and port B[0:15]. Rev. 2.00 Mar 09, 2006 page 782 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
19.2
Register Configuration
Table 19.2 shows the PFC registers. Table 19.2 Register Configuration
Name Port A control register Port A I/O register Port B control register Port B I/O register Port B control register 2 Abbreviation PACR PAIOR PBCR PBIOR PBCR2 R/W R/W R/W R/W R/W R/W Initial Value H'0000 H'0000 H'0000 H'0000 H'0000 Address H'FFFFFC80 H'FFFFFC82 H'FFFFFC88 H'FFFFFC8A H'FFFFFC8E Access Size 8, 16 8, 16 8, 16 8, 16 8, 16
19.3
19.3.1
Register Descriptions
Port A Control Register (PACR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 0 R/W 14 -- 0 R 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 0 R/W 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
PA13MD PA12MD PA11MD PA10MD PA9MD PA8MD
PA7MD PA6MD PA5MD PA4MD PA3MD PA2MD PA1MD PA0MD
The port A control register (PACR) is a 16-bit read/write register that selects the functions of the 14 multiplex pins in port A. PACR is initialized to H'0000 by a power-on reset. It is not initialized by a manual reset or in standby mode or sleep mode. Bits 15 and 14--Reserved: These bits are always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 783 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bit 13--PA13 Mode Bit (PA13MD): Selects the function of pin PA13/SRCK0.
Bit 13: PA13MD 0 1 Description General input/output (PA13) SIOF serial receive clock input (SRCK0) (Initial value)
Bit 12--PA12 Mode Bit (PA12MD): Selects the function of pin PA12/SRS0.
Bit 12: PA12MD 0 1 Description General input/output (PA12) SIOF serial receive synchronous input (SRS0) (Initial value)
Bit 11--PA11 Mode Bit (PA11MD): Selects the function of pin PA11/SRXD0.
Bit 11: PA11MD 0 1 Description General input/output (PA11) SIOF serial receive data (SRXD0) (Initial value)
Bit 10--PA10 Mode Bit (PA10MD): Selects the function of pin PA10/STCK0.
Bit 10: PA10MD 0 1 Description General input/output (PA10) SIOF serial transmit clock (STCK0) (Initial value)
Bit 9--PA9 Mode Bit (PA9MD): Selects the function of pin PA9/STS0.
Bit 9: PA9MD 0 1 Description General input/output (PA9) SIOF serial transmit synchronous input/output (STS0) (Initial value)
Bit 8--PA8 Mode Bit (PA8MD): Selects the function of pin PA8/STXD0.
Bit 8: PA8MD 0 1 Description General input/output (PA8) SIOF serial transmit data output (STXD0) (Initial value)
Rev. 2.00 Mar 09, 2006 page 784 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bit 7--PA7 Mode Bit (PA7MD): Selects the function of pin WDTOVF/PA7.
Bit 7: PA7MD 0 1 Description WDT overflow signal output (WDTOVF)* General input/output (PA7) (Initial value)
Note: * WDTOVF is an output pin after a reset, so care is required when using this pin as a general input port (PA7).
Bit 6--PA6 Mode Bit (PA6MD): Selects the function of pin PA6/FTCI.
Bit 6: PA6MD 0 1 Description General input/output (PA6) FRT clock input (FTCI) (Initial value)
Bit 5--PA5 Mode Bit (PA5MD): Selects the function of pin PA5/FTI.
Bit 5: PA5MD 0 1 Description General input/output (PA5) FRT input capture input (FTI) (Initial value)
Bit 4--PA4 Mode Bit (PA4MD): Selects the function of pin PA4/FTO4.
Bit 4: PA4MD 0 1 Description General input/output (PA4) FRT output compare output (FTOA) (Initial value)
Bit 3--PA3 Mode Bit (PA3MD): Selects the function of pin CKPO/FTOB.
Bit 3: PA3MD 0 1 Description Peripheral module clock output (CKPO) FRT output compare output (FTOB) (Initial value)
Bit 2--PA2 Mode Bit (PA2MD): Selects the function of pin PA2/LNKSTA.
Bit 2: PA2MD 0 1 Description General input/output (PA2) EtherC rink status input (LNKSTA) (Initial value)
Rev. 2.00 Mar 09, 2006 page 785 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bit 1--PA1 Mode Bit (PA1MD): Selects the function of pin PA1/EXOUT.
Bit 1: PA1MD 0 1 Description General input/output (PA1) EtherC general external output (EXOUT) (Initial value)
Bit 0--PA0 Mode Bit (PA0MD): Selects the function of pin PA0.
Bit 0: PA0MD 0 1 Description General input/output (PA0) EtherC CAM sense input (CAMSEN) (Initial value)
19.3.2
Port A I/O Register (PAIOR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 0 R/W 14 -- 0 R 6 0 R/W 13 0 R/W 5 0 R/W 12 0 R/W 4 0 R/W 11 0 R/W 3 -- 0 R 10 0 R/W 2 0 R/W 9 0 R/W 1 0 R/W 8 0 R/W 0 0 R/W
PA13IOR PA12IOR PA11IOR PA10IOR PA9IOR PA8IOR
PA7IOR PA6IOR PA5IOR PA4IOR
PA2IOR PA1IOR PA0IOR
The port A I/O register (PAIOR) is a 16-bit read/write register that selects the input/output direction of the 14 multiplex pins in port A. Bits PA13IOR to PA4IOR and PA2IOR to PA0IOR correspond to individual pins in port A. PAIOR is enabled when port A pins function as general input pins (PA13 to PA4 and PA2 to PA0), and disabled otherwise. When port A pins function as PA13 to PA4 and PA2 to PA0, a pin becomes an output when the corresponding bit in PAIOR is set to 1, and an input when the bit is cleared to 0. PAIOR is initialized to H'0000 by a power-on reset. It is not initialized by a manual reset or in standby mode or sleep mode.
Rev. 2.00 Mar 09, 2006 page 786 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
19.3.3
Port B Control Registers (PBCR, PBCR2)
The port B control registers (PBCR and PBCR2) are 16-bit read/write registers that select the functions of the 16 multiplex pins in port B. PBCR selects the functions of the pins for the upper 8 bits in port B, and PBCR2 selects the functions of the pins for the lower 8 bits in port B. PBCR and PBCR2 are initialized to H'0000 by a power-on reset. They are not initialized by a manual reset or in standby mode or sleep mode. Port B Control Register (PBCR)
Bit: 15 PB15 MD1 Initial value: R/W: Bit: 0 R/W 7 PB11 MD1 Initial value: R/W: 0 R/W 14 PB15 MD0 0 R/W 6 PB11 MD0 0 R/W 13 PB14 MD1 0 R/W 5 PB10 MD1 0 R/W 12 PB14 MD0 0 R/W 4 PB10 MD0 0 R/W 11 PB13 MD1 0 R/W 3 PB9 MD1 0 R/W 10 PB13 MD0 0 R/W 2 PB9 MD0 0 R/W 9 PB12 MD1 0 R/W 1 PB8 MD1 0 R/W 8 PB12 MD0 0 R/W 0 PB8 MD0 0 R/W
Bits 15 and 14--PB15 Mode Bits 1 and 0 (PB15MD1, PB15MD0): These bits select the function of pin PB15/SCK1.
Bit 15: PB15MD1 0 1 Bit 14: PB15MD0 0 1 0 1 Description General input/output (PB15) Reserved SCIF1 serial clock input/output (SCK1) Reserved (Initial value)
Rev. 2.00 Mar 09, 2006 page 787 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bits 13 and 12--PB14 Mode Bits 1 and 0 (PB14MD1, PB14MD0): These bits select the function of pin PB14/RXD1.
Bit 13: PB14MD1 0 1 Bit 12: PB14MD0 0 1 0 1 Description General input/output (PB14) Reserved SCIF1 serial data input (RXD1) Reserved (Initial value)
Bits 11 and 10--PB13 Mode Bits 1 and 0 (PB13MD1, PB13MD0): These bits select the function of pin PB13/TXD1.
Bit 11: PB13MD1 0 1 Bit 10: PB13MD0 0 1 0 1 Description General input/output (PB13) Reserved SCIF1 serial data output (TXD1) Reserved (Initial value)
Bits 9 and 8--PB12 Mode Bits 1 and 0 (PB12MD1, PB12MD0): These bits select the function of pin PB12/SRCK2/RTS/STATS1.
Bit 9: PB12MD1 0 1 Bit 8: PB12MD0 0 1 0 1 Description General input/output (PB12) SIO2 serial receive clock input (SRCK2) SCIF1 transmit request (RTS) BSC status 1 output (STATS1) (Initial value)
Bits 7 and 6--PB11 Mode Bits 1 and 0 (PB11MD1, PB11MD0): These bits select the function of pin PB11/SRS2/CTS/STATS0.
Bit 7: PB11MD1 0 1 Bit 6: PB11MD0 0 1 0 1 Description General input/output (PB11) SCIF1 transmit permission (CTS) BSC status 0 output (STATS0) (Initial value) SIO2 serial receive synchronous input (SRS2)
Rev. 2.00 Mar 09, 2006 page 788 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bits 5 and 4--PB10 Mode Bits 1 and 0 (PB10MD1, PB10MD0): These bits select the function of pin PB10/SRXD2/TIOCA1.
Bit 5: PB10MD1 0 1 Bit 4: PB10MD0 0 1 0 1 Description General input/output (PB10) SIO2 serial receive data input (SRXD2) TPU1 input capture input/output compare output (TIOCA1) Reserved (Initial value)
Bits 3 and 2--PB9 Mode Bits 1 and 0 (PB9MD1, PB9MD0): These bits select the function of pin PB9/STCK2/TIOCB1, TCLKC.
Bit 3: PB9MD1 0 1 Bit 2: PB9MD0 0 1 0 1 Description General input/output (PB9) (Initial value) SIO2 serial transmit clock input (STCK2) TPU1 input capture input/output compare output (TIOCB1)* Reserved
Note: * Timer clock input C (TCLKC) is selected when the TPU phase counting mode is set, or according to the setting of bits TPSC2 to TPSC0 in TCR.
Bits 1 and 0--PB8 Mode Bits 1 and 0 (PB8MD1, PB8MD0): These bits select the function of pin PB8/STS2/TIOCA2.
Bit 1: PB8MD1 0 1 Bit 0: PB8MD0 0 1 0 1 Description General input/output (PB8) (Initial value) SIO2 serial transmit synchronous input/output (STS2) TPU2 input capture input/output compare output (TIOCA2) Reserved
Rev. 2.00 Mar 09, 2006 page 789 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Port B Control Register 2 (PBCR2)
Bit: 15 PB7 MD1 Initial value: R/W: Bit: 0 R/W 7 PB3 MD1 Initial value: R/W: 0 R/W 14 PB7 MD0 0 R/W 6 PB3 MD0 0 R/W 13 PB6 MD1 0 R/W 5 PB2 MD1 0 R/W 12 PB6 MD0 0 R/W 4 PB2 MD0 0 R/W 11 PB5 MD1 0 R/W 3 PB1 MD1 0 R/W 10 PB5 MD0 0 R/W 2 PB1 MD0 0 R/W 9 PB4 MD1 0 R/W 1 PB0 MD1 0 R/W 8 PB4 MD0 0 R/W 0 PB0 MD0 0 R/W
Bits 15 and 14--PB7 Mode Bits 1 and 0 (PB7MD1, PB7MD0): These bits select the function of pin PB7/STXD2/TIOCB2, TCLKD.
Bit 15: PB7MD1 0 1 Bit 14: PB7MD0 0 1 0 1 Description General input/output (PB7) (Initial value) SIO2 serial transmit data output (STXD2) TPU2 input capture input/output compare output (TIOCB2)* Reserved
Note: * Timer clock input D (TCLKD) is selected when the TPU phase counting mode is set, or according to the setting of bits TPSC2 to TPSC0 in TCR.
Bits 13 and 12--PB6 Mode Bits 1 and 0 (PB6MD1, PB6MD0): These bits select the function of pin PB6/SRCK1/SCK2.
Bit 13: PB6MD1 0 1 Bit 12: PB6MD0 0 1 0 1 Description General input/output (PB6) SIO1 serial receive clock input (SRCK1) SCIF2 serial clock input/output (SCK2) Reserved (Initial value)
Rev. 2.00 Mar 09, 2006 page 790 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bits 11 and 10--PB5 Mode Bits 1 and 0 (PB5MD1, PB5MD0): These bits select the function of pin PB5/SRS1/RXD2.
Bit 11: PB5MD1 0 1 Bit 10: PB5MD0 0 1 0 1 Description General input/output (PB5) SCIF2 serial data input (RXD2) Reserved (Initial value) SIO1 serial receive synchronous input (SRS1)
Bits 9 and 8--PB4 Mode Bits 1 and 0 (PB4MD1, PB4MD0): These bits select the function of pin PB4/SRXD1/TXD2.
Bit 9: PB4MD1 0 1 Bit 8: PB4MD0 0 1 0 1 Description General input/output (PB4) SIO1 serial receive data input (SRXD1) SCIF2 serial data output (TXD2) Reserved (Initial value)
Bits 7 and 6--PB3 Mode Bits 1 and 0 (PB3MD1, PB3MD0): These bits select the function of pin PB3/STCK1/TIOCA0.
Bit 7: PB3MD1 0 1 Bit 6: PB3MD0 0 1 0 1 Description General input/output (PB3) (Initial value) SIO1 serial transmit clock input (STCK1) TPU0 input capture input/output compare output (TIOCA0) Reserved
Bits 5 and 4--PB2 Mode Bits 1 and 0 (PB2MD1, PB2MD0): These bits select the function of pin PB2/STS1/TIOCB0.
Bit 5: PB2MD1 0 1 Bit 4: PB2MD0 0 1 0 1 Description General input/output (PB2) (Initial value) SIO1 serial transmit synchronous input/output (STS1) TPU0 input capture input/output compare output (TIOCB0) Reserved Rev. 2.00 Mar 09, 2006 page 791 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Bits 3 and 2--PB1 Mode Bits 1 and 0 (PB1MD1, PB1MD0): These bits select the function of pin PB1/STXD1/TIOCC0/TCLKA.
Bit 3: PB1MD1 0 1 Bit 2: PB1MD0 0 1 0 1 Description General input/output (PB1) (Initial value) SIO1 serial transmit data output (STXD1) TPU0 input capture input/output compare output (TIOCC0)* Reserved
Note: * Timer clock input A (TCLKA) is selected when the TPU phase counting mode is set, or according to the setting of bits TPSC2 to TPSC0 in TCR.
Bits 1 and 0--PB0 Mode Bits 1 and 0 (PB0MD1, PB0MD0): These bits select the function of pin PB0/TIOCD0/TCLKB.
Bit 1: PB0MD1 0 1 Bit 0: PB0MD0 0 1 0 1 Description General input/output (PB0) Reserved TPU0 input capture input/output compare output (TIOCD0)* EtherC Wake-On-LAN output (WOL) (Initial value)
Note: * Timer clock input B (TCLKB) is selected when the TPU phase counting mode is set, or according to the setting of bits TPSC2 to TPSC0 in TCR.
Rev. 2.00 Mar 09, 2006 page 792 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
19.3.4
Port B I/O Register (PBIOR)
Bit: 15 PB15 IOR Initial value: R/W: Bit: 0 R/W 7 PB7 IOR Initial value: R/W: 0 R/W 14 PB14 IOR 0 R/W 6 PB6 IOR 0 R/W 13 PB13 IOR 0 R/W 5 PB5 IOR 0 R/W 12 PB12 IOR 0 R/W 4 PB4 IOR 0 R/W 11 PB11 IOR 0 R/W 3 PB3 IOR 0 R/W 10 PB10 IOR 0 R/W 2 PB2 IOR 0 R/W 9 PB9 IOR 0 R/W 1 PB1 IOR 0 R/W 8 PB8 IOR 0 R/W 0 PB0 IOR 0 R/W
The port B I/O register (PBIOR) is a 16-bit read/write register that selects the input/output direction of the 16 multiplex pins in port B. Bits PB15IOR to PB0IOR correspond to individual pins in port B. PBIOR is enabled when port B pins function as general input pins (PB15 to PB0), and disabled otherwise. When port B pins function as PB15 to PB0, a pin becomes an output when the corresponding bit in PBIOR is set to 1, and an input when the bit is cleared to 0. PBIOR is initialized to H'0000 by a power-on reset. It is not initialized by a manual reset or in standby mode or sleep mode.
Rev. 2.00 Mar 09, 2006 page 793 of 906 REJ09B0292-0200
Section 19 Pin Function Controller (PFC)
Rev. 2.00 Mar 09, 2006 page 794 of 906 REJ09B0292-0200
Section 20 I/O Ports
Section 20 I/O Ports
20.1 Overview
This chip has two ports, designated A and B. Port A is a 14-bit input/output port, and port B is a 16-bit input/output port. The port pins are multiplexed as general input/output and other functions. (The function of multiplexed multiplex pins is selected by means of the pin function controller (PFC).) Ports A and B are each provided with a data register for storing pin data.
20.2
Port A
Port A is an input/output port with the 14 pins shown in figure 20.1. Of the 14 pins, the CKPO pin has no port data register bit, and is multiplexed as an internal clock pin.
PA13 (input/output) / SRCK0 PA12 (input/output) / SRS0 PA11 (input/output) / SRXD0 PA10 (input/output) / STCK0 PA9 PA8 Port A PA6 PA5 PA4 PA2 PA1 PA0 (input/output) / STS0 (input/output) / STXD0 (input/output) / FTCI (input/output) / FTI (input/output) / FTOA / FTOB
(input) (input) (input) (input) (input/output) (output) (input/output) (input) (input) (output) (output)
WDTOVF* (output) / PA7
CKPO (output)
(input/output) / LNKSTA (input) (input/output) / EXOUT (output) (input/output)
Note: * The fact that the WDTOVF pin is set to output mode after a reset must be noted when it is to be used as a general I/O port (PA7).
Figure 20.1 Port A
Rev. 2.00 Mar 09, 2006 page 795 of 906 REJ09B0292-0200
Section 20 I/O Ports
20.2.1
Register Configuration
The port A register is shown in table 20.1. Table 20.1 Register Configuration
Name Port A data register Abbreviation PADR R/W R/W Initial Value H'0000 Address H'FFFFFC84 Access Size 8, 16
20.2.2
Port A Data Register (PADR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 -- 0 R 7 PA7DR 0 R/W 14 -- 0 R 6 PA6DR 0 R/W 13 0 R/W 5 PA5DR 0 R/W 12 0 R/W 4 PA4DR 0 R/W 11 0 R/W 3 -- 0 R 10 0 R/W 2 PA2DR 0 R/W 9 0 R/W 1 PA1DR 0 R/W 8 PA8DR 0 R/W 0 PA0DR 0 R/W
PA13DR PA12DR PA11DR PA10DR PA9DR
The port A data register (PADR) is a 16-bit read/write register that stores port A data. Bits 15, 14, and 3 are reserved: they always read 0, and the write value should always be 0. Bits PA13DR to PA0DR correspond to pins PA13 to PA0. When a pin functions as a general output, if a value is written to PADR, that value is output directly from the pin, and if PADR is read, the register value is returned directly regardless of the pin state. When a pin functions as a general input, if PADR is read the pin state, not the register value, is returned directly. If a value is written to PADR, although that value is written into PADR it does not affect the pin state. Table 20.2 summarizes port A data register read/write operations. PADR is initialized to H'0000 by a power-on reset. It is not initialized by a manual reset or in standby mode or sleep mode.
Rev. 2.00 Mar 09, 2006 page 796 of 906 REJ09B0292-0200
Section 20 I/O Ports
Table 20.2 Port A Data Register (PADR) Read/Write Operations
PAIOR 0 Pin Function General input Other than general input 1 General output Other than general output Read Pin state Pin state PADR value PADR value Write Value is written to PADR, but does not affect pin state Value is written to PADR, but does not affect pin state Write value is output from pin Value is written to PADR, but does not affect pin state
20.3
Port B
Port B is an input/output port with the 16 pins shown in figure 20.2.
PB15 (input/output) / Reserved PB14 (input/output) / Reserved PB13 (input/output) / Reserved PB12 (input/output) / SRCK2 (input) PB11 (input/output) / SRS2 (input) PB10 (input/output) / SRXD2 (input) PB9 (input/output) / STCK2 (input) Port B PB8 (input/output) / STS2 PB7 (input/output) / STXD2 (output) PB6 (input/output) / SRCK1 (input) PB5 (input/output) / SRS1 (input) PB4 (input/output) / SRXD1 (input) PB3 (input/output) / STCK1 (input) PB2 (input/output) / STS1 PB1 (input/output) / STXD1 (output) PB0 (input/output) / Reserved
/ SCK1 / RXD1 / TXD1 / RTS / CTS
(input/output) (input) (output) (output) (input) / STATS1 (output) / STATS0 (output)
/ TIOCA1 (input/output) / TIOCB1 (input/output) / TIOCB2 (input/output) / SCK2 / RXD2 / TXD2 (input/output) (input) (output)
(input/output) / TIOCA2 (input/output)
/ TIOCA0 (input/output) / TIOCD0 (input/output) / TIOCD0 (input/output) / WOL (output)
(input/output) / TIOCB0 (input/output)
Figure 20.2 Port B 20.3.1 Register Configuration
Table 20.3 shows the port B register.
Rev. 2.00 Mar 09, 2006 page 797 of 906 REJ09B0292-0200
Section 20 I/O Ports
Table 20.3 Register Configuration
Name Port B data register Abbreviation PBDR R/W R/W Initial Value H'0000 Address H'FFFFFC8C Access Size 8, 16
20.3.2
Port B Data Register (PBDR)
Bit: Initial value: R/W: Bit: Initial value: R/W: 15 0 R/W 7 PB7DR 0 R/W 14 0 R/W 6 PB6DR 0 R/W 13 0 R/W 5 PB5DR 0 R/W 12 0 R/W 4 PB4DR 0 R/W 11 0 R/W 3 PB3DR 0 R/W 10 0 R/W 2 PB2DR 0 R/W 9 0 R/W 1 PB1DR 0 R/W 8 PB8DR 0 R/W 0 PB0DR 0 R/W
PB15DR PB14DR PB13DR PB12DR PB11DR PB10DR PB9DR
The port B data register (PBDR) is a 16-bit read/write register that stores port B data. Bits PB15DR to PB0DR correspond to pins PB15 to PB0. When a pin functions as a general output, if a value is written to PBDR, that value is output directly from the pin, and if PBDR is read, the register value is returned directly regardless of the pin state. When a pin functions as a general input, if PBDR is read the pin state, not the register value, is returned directly. If a value is written to PBDR, although that value is written into PBDR it does not affect the pin state. Table 20.4 shows port B data register read/write operations. PBDR is initialized to H'0000 by a power-on reset. It is not initialized by a manual reset or in standby mode or sleep mode. Table 20.4 Port B Data Register (PBDR) Read/Write Operations
PBIOR 0 Pin Function General input Other than general input 1 General output Other than general output Read Pin state Pin state PBDR value PBDR value Write Value is written to PBDR, but does not affect pin state Value is written to PBDR, but does not affect pin state Write value is output from pin Value is written to PBDR, but does not affect pin state
Rev. 2.00 Mar 09, 2006 page 798 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Section 21 Power-Down Modes
21.1 Overview
This chip has a module standby function (which reduces power consumption by selectively halting operation of unnecessary modules among the on-chip peripheral modules and the DSP unit), a sleep mode (which halts CPU functions), and a standby mode (which halts all functions). 21.1.1 Power-Down Modes
The following modes and function are provided as power-down modes: 1. Sleep mode 2. Standby mode 3. Module standby function (UBC, DMAC, DSP, FRT, SCIF1-2, TPU, SIOF, SIO1-2) Table 21.1 shows the transition conditions for entering the modes from the program execution state, as well as the CPU and peripheral module states in each mode and the procedures for canceling each mode.
Rev. 2.00 Mar 09, 2006 page 799 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Table 21.1 Power-Down Modes
State On-Chip Oscillation Circuit, Transition E-DMAC, CPU, Condition EtherC Cache DSP SLEEP Runs instruction executed with SBY bit set to 0 in SBYCR1 Halted Halted UBC, DMAC, FRT, SCIF1-2, TPU, SIOF, SIO1-2 Pins Runs Runs
Mode Sleep mode
BSC Runs
Canceling Procedure
Standby SLEEP Halted mode instruction executed with SBY bit set to 1 in SBYCR1 Module MSTP bit Runs standby for relevant function module is set to 1
1. Interrupt 2. DMA address error 3. Poweron reset 4. Manual reset 1. NMI Halted Halted Halted, UBC: Halted, Held or interrupt and and register high register values held impedance 2. Powervalues Other than on reset held 3. Manual UBC: Halted reset 1. Clear Runs When Runs When an FRT, and MSTP bit MSTP MSTP bit is SCIF1, 2 to 0 is 1, 1, the clock pins are the clock supply to initialized, 2. Powersupply is the relevant and others on reset halted module is operate 3. Manual halted reset
21.1.2
Register
Table 21.2 shows the register configuration. Table 21.2 Register Configuration
Name Standby control register 1 Standby control register 2 Abbreviation SBYCR1 SBYCR2 R/W R/W R/W Initial Value H'00 H'00 Address H'FFFFFE91 H'FFFFFE93 Access Size 8 8
Rev. 2.00 Mar 09, 2006 page 800 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
21.2
21.2.1
Register Descriptions
Standby Control Register 1 (SBYCR1)
Bit: 7 SBY Initial value: R/W: 0 R/W 6 HIZ 0 R/W 5 MSTP5 (UBC) 0 R/W 4 MSTP4 (DMAC) 0 R/W 3 MSTP3 (DSP) 0 R/W 0 R 2 -- 1 MSTP1 (FRT) 0 R/W 0 R 0 --
Standby control register 1 (SBYCR1) is an 8-bit read/write register that sets the power-down mode. SBYCR is initialized to H'00 by a reset. Bit 7--Standby (SBY): Specifies transition to standby mode. To enter the standby mode, halt the WDT (set the TME bit in WTCSR to 0) and set the SBY bit.
Bit 7: SBY 0 1 Description Executing a SLEEP instruction puts the chip into sleep mode Executing a SLEEP instruction puts the chip into standby mode (Initial value)
Bit 6--Port High Impedance (HIZ): Selects whether output pins are set to high impedance or retain the output state in standby mode. When HIZ = 0 (initial state), the specified pin retains its output state. When HIZ = 1, the pin goes to the high-impedance state. See Appendix B.1, Pin States during Resets, Power-Down States and Bus Release State, for which pins are controlled.
Bit 6: HIZ 0 1 Description Pin state retained in standby mode Pin goes to high impedance in standby mode (Initial value)
Bit 5--Module Stop 5 (MSTP5): Specifies halting the clock supply to the user break controller (UBC). When the MSTP5 bit is set to 1, the supply of the clock to the UBC is halted. When the clock halts, the UBC registers retain their pre-halt state. Do not set this bit while the UBC is running.
Bit 5: MSTP5 0 1 Description UBC running Clock supply to UBC halted (Initial value)
Rev. 2.00 Mar 09, 2006 page 801 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Bit 4--Module Stop 4 (MSTP4): Specifies halting the clock supply to the DMAC. When MSTP4 bit is set to 1, the supply of the clock to the DMAC is halted. When the clock halts, the DMAC retains its pre-halt state. When MSTP4 is cleared to 0 and the DMAC begins running again, its starts operating from its pre-halt state. Set this bit while the DMAC is halted; this bit cannot be set while the DMAC is operating (transferring data).
Bit 4: MSTP4 0 1 Description DMAC running Clock supply to DMAC halted (Initial value)
Bit 3--Module Stop 3 (MSTP3): Specifies halting the clock supply to the DSP unit. When the MSTP3 bit is set to 1, the supply of the clock to the DSP unit is halted. When the clock halts, the operation result prior to the halt is retained. This bit should be set when the DSP unit is halted. When the DSP unit is halted, no instructions with a DSP register, MACH, or MACL as an operand can be used.
Bit 3: MSTP3 0 1 Description DSP running Clock supply to DSP halted (Initial value)
Bit 2--Reserved: This bit is always read as 0. The write value should always be 0. Bit 1--Module Stop 1 (MSTP1): Specifies halting the clock supply to the 16-bit free-running timer (FRT). When the MSTP1 bit is set to 1, the supply of the clock to the FRT is halted. When the clock halts, all FRT registers are initialized except the FRT interrupt vector register in INTC, which holds its previous value. When MSTP1 is cleared to 0 and the FRT begins running again, its starts operating from its initial state.
Bit 1: MSTP1 0 1 Description FRT running Clock supply to FRT halted (Initial value)
Bit 0--Reserved: This bit is always read as 0. The write value should always be 0.
Rev. 2.00 Mar 09, 2006 page 802 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
21.2.2
Standby Control Register 2 (SBYCR2)
Bit: 7 -- Initial value: R/W: 0 R 6 -- 0 R 5 4 3 2 1 0
MSTP11 MSTP10 MSTP9 (TPU) (SIO2) (SIO1) 0 R/W 0 R/W 0 R/W
MSTP8 MSTP7 MSTP6 (SIOF) (SCIF2) (SCIF1) 0 R/W 0 R/W 0 R/W
Standby control register 2 (SBYCR2) is an 8-bit read/write register that sets the power-down mode state. SBYCR2 is initialized to H'00 by a reset. Bits 7 and 6--Reserved: These bits are always read as 0. The write value should always be 0. Bit 5--Module Stop 11 (MSTP11): Specifies halting the clock supply to the 16-bit timer pulse unit (TPU). When the MSTP11 bit is set to 1, the supply of the clock to the TPU is halted. When the clock halts, the TPU retains its pre-halt state, and the TPU interrupt vector register in the INTC retains its pre-halt value. Therefore, when MSTP11 is cleared to 0 and the clock supply to the TPU is resumed, the TPU starts operating again.
Bit 5: MSTP11 0 1 Description TPU running Clock supply to TPU halted (Initial value)
Bit 4--Module Stop 10 (MSTP10): Specifies halting the clock supply to SIO channel 2. When the MSTP10 bit is set to 1, the supply of the clock to SIO channel 2 is halted. When the clock halts, SIO channel 2 retains its pre-halt state, and the SIO channel 2 interrupt vector register in the INTC retains its pre-halt value. Therefore, when MSTP10 is cleared to 0 and the clock supply to SIO channel 2 is restarted, operation starts again.
Bit 4: MSTP10 0 1 Description SIO channel 2 running Clock supply to SIO channel 2 halted (Initial value)
Rev. 2.00 Mar 09, 2006 page 803 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Bit 3--Module Stop 9 (MSTP9): Specifies halting the clock supply to SIO channel 1. When the MSTP9 bit is set to 1, the supply of the clock to SIO channel 1 is halted. When the clock halts, SIO channel 1 retains its pre-halt state, and the SIO channel 1 interrupt vector register in the INTC retains its pre-halt value. Therefore, when MSTP9 is cleared to 0 and the clock supply to SIO channel 1 is restarted, operation starts again.
Bit 3: MSTP9 0 1 Description SIO channel 1 running Clock supply to SIO channel 1 halted (Initial value)
Bit 2--Module Stop 8 (MSTP8): Specifies halting the clock supply to SIOF. When the MSTP8 bit is set to 1, the supply of the clock to SIOF is halted. When the clock halts, SIOF retains its pre-halt state, and the SIOF interrupt vector register in the INTC retains its pre-halt value. Therefore, when MSTP8 is cleared to 0 and the clock supply to SIOF is restarted, operation starts again.
Bit 2: MSTP8 0 1 Description SIOF running Clock supply to SIOF halted (Initial value)
Bit 1--Module Stop 7 (MSTP7): Specifies halting the clock supply to SCIF2. When the MSTP7 bit is set to 1, the supply of the clock to SCIF2 is halted. When the clock halts, the SCIF2 registers are initialized, but the SCIF2 interrupt vector register in the INTC retains its pre-halt value. Therefore, when MSTP7 is cleared to 0 and SCIF2 begins running again, it starts operating from its initial state.
Bit 1: MSTP7 0 1 Description SCIF2 running Clock supply to SCIF2 halted (Initial value)
Bit 0--Module Stop 6 (MSTP6): Specifies halting the clock supply to SCIF1. When the MSTP6 bit is set to 1, the supply of the clock to SCIF1 is halted. When the clock halts, the SCIF1 registers are initialized, but the SCIF1 interrupt vector register in the INTC retains its pre-halt value. Therefore, when MSTP6 is cleared to 0 and SCIF1 begins running again, it starts operating from its initial state.
Bit 0: MSTP6 0 1 Description SCIF1 running Clock supply to SCIF1 halted (Initial value)
Rev. 2.00 Mar 09, 2006 page 804 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
21.3
21.3.1
Sleep Mode
Transition to Sleep Mode
Executing the SLEEP instruction when the SBY bit in SBYCR1 is 0 causes a transition from the program execution state to sleep mode. Although the CPU halts immediately after executing the SLEEP instruction, the contents of its internal registers remain unchanged. The on-chip peripheral modules continue to run in sleep mode. 21.3.2 Canceling Sleep Mode
Sleep mode is canceled by an interrupt, DMA address error, power-on reset, or manual reset. Cancellation by an Interrupt: When an interrupt occurs, sleep mode is canceled and interrupt exception handling is executed. Sleep mode is not canceled if the interrupt cannot be accepted because its priority level is equal to or less than the mask level set in the CPU's status register (SR) or if an interrupt by an on-chip peripheral module is disabled at the peripheral module. Cancellation by a DMA Address Error: If a DMA address error occurs, sleep mode is canceled and DMA address error exception handling is executed. Cancellation by a Power-On Reset: A power-on reset cancels sleep mode. Cancellation by a Manual Reset: A manual reset cancels sleep mode.
21.4
21.4.1
Standby Mode
Transition to Standby Mode
To enter standby mode, set the SBY bit to 1 in SBYCR1, then execute the SLEEP instruction. The chip switches from the program execution state to standby mode. The NMI interrupt cannot be accepted when the SLEEP instruction is executed, or for the following five cycles. In standby mode, the clock supply to all on-chip peripheral modules is halted as well as the CPU. CPU register contents are held, and some on-chip peripheral modules are initialized.
Rev. 2.00 Mar 09, 2006 page 805 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Table 21.3 Register States in Standby Mode
Registers that Retain Data All registers All registers Registers with Undefined Contents -- --
Module Interrupt controller (INTC) User break controller (UBC) Bus state controller (BSC) Direct memory access controller (DMAC)
Registers Initialized -- -- --
All registers -- * DMA source DMA channel control -- address registers 0 register 0, 1 and 1 DMA operation register * DMA destination address registers 0 and 1 * DMA transfer count registers 0 and 1 * DMA request/ response selection control registers 0 and 1 * Vector number setting registers DMA0 and DMA1 Bits 7-5 of the timer control/status register Reset control/status register Bits 2-0 of the timer control/status register Timer counter -- -- All registers All registers All registers All registers All registers -- -- -- -- -- -- -- -- -- --
Watchdog timer (WDT)
16-bit free-running timer (FRT)
All registers
Serial communication interface All registers with FIFO (SCIF1-2) Serial I/O with FIFO (SIOF) Serial I/O (SIO1-2) User debug interface (H-UDI) 16-bit timer pulse unit (TPU) Pin function controller (PFC) Ethernet controller direct memory access controller (EDMAC) Ethernet controller (EtherC) Others -- -- -- -- -- All registers
All registers --
--
--
Standby control register -- 1, 2 Frequency modification register
Rev. 2.00 Mar 09, 2006 page 806 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
21.4.2
Canceling Standby Mode
Standby mode is canceled by an NMI interrupt, a power-on reset, or a manual reset. Cancellation by an NMI Interrupt: When a rising edge or falling edge is detected in the NMI signal, after the elapse of the time set in the WDT timer control/status register, clocks are supplied to the entire chip, standby mode is canceled, and NMI exception handling begins. Insure that the interval set for the WDT is at least as long as the oscillation stabilization time. When standby mode is canceled by a falling edge in the NMI signal, insure that the NMI pin goes high when standby mode is entered (when the clock is halted), and goes low on recovering from standby mode (when the clock starts after oscillation has stabilized). The low level at the NMI pin should be held for at least 3 cycles after the start of clock signal output from the CKIO pin. When standby mode is canceled by a rising edge in the NMI signal, insure that the NMI pin goes low when standby mode is entered (when the clock is halted), and goes high on recovering from standby mode (when the clock starts after oscillation has stabilized). The high level at the NMI pin should be held for at least 3 cycles after the start of clock signal output from the CKIO pin. Cancellation by a Power-On Reset: A power-on reset cancels standby mode. Cancellation by a Manual Reset: A manual reset cancels standby mode. 21.4.3 Standby Mode Cancellation by NMI Interrupt
The following example describes moving to the standby mode upon the fall of the NMI signal and clearing the standby mode when the NMI signal rises. Figure 21.1 shows the timing. When the NMI pin level changes from high to low after the NMI edge select bit (NMIE) of the interrupt control register (ICR) has been set to 0 (detect falling edge), an NMI interrupt is accepted. When the NMIE bit is set to 1 (detect rising edge) by the NMI exception service routine, the standby bit (SBY) of the standby control register 1 (SBYCR1) is set to 1 and a SLEEP instruction is executed, the standby mode is entered. The standby mode is cleared the next time the NMI pin level changes from low level to high level. The high level at the NMI pin should be held for at least 3 cycles after the start of clock signal output from the CKIO pin.
Rev. 2.00 Mar 09, 2006 page 807 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Oscillator CKIO (output) NMI
NMIE
SBY NMI exception handling Exception service routine, SBY = 1, SLEEP instruction
Oscillation settling time Standby mode Start of oscillation WDT set time NMI exception handling
Figure 21.1 Standby Mode Cancellation by NMI Interrupt 21.4.4 Clock Pause Function
When the clock is input from the CKIO pin, the clock frequency can be modified or the clock stopped. The CKPREQ/CKM pin is provided for this purpose. Note that clock pauses are not accepted while the watchdog timer (WDT) is operating (i.e. when the timer enable bit (TME) in the WDT's timer control/status register (WTCSR) is 1). When the clock pause request function is used, the standby bit (SBY) in the standby control register 1 (SBYCR1) must be set to 1 before inputting the request signal. The clock pause function is used as described below. 1. Set the TME bit in the watchdog timer's WTCSR register to 0, and set the SBY bit in SBYCR1 to 1. 2. Apply a low level to the CKPREQ/CKM pin. 3. When the chip enters the standby state internally, a low level is output from the CKPACK pin. 4. After confirming that the CKPACK pin has gone low, perform clock halting or frequency modification. 5. To cancel the clock pause state (standby state), apply a high level to the CKPREQ/CKM pin. (Inside the chip , the standby state is canceled by detecting a rising edge at the CKPREQ/CKM pin.)
Rev. 2.00 Mar 09, 2006 page 808 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
6. When PLL circuit 1 is operational, the WDT starts counting up inside the chip. When PLL circuit 1 is halted, the WDT is not activated. 7. When the internal clock stabilizes, the CKPACK pin goes high, giving external notification that the chip can be operated.
The standby state, all on-chip peripheral module states, and all pin states during clock pause are the same as in the normal standby mode. Figure 21.2 shows the timing chart for the clock pause function.
Frequency modification CKIO input CKPREQ/CKM input CKPACK output Clock pause request cancellation
WDT count-up Clock pause acceptance processing Clock pause state
Normal state
Figure 21.2 Clock Pause Function Timing Chart (PLL Circuit 1 Operating)
Rev. 2.00 Mar 09, 2006 page 809 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Figure 21.3 shows the clock pause function timing chart when the PLL circuit is halted.
Frequency modification
CKIO input CKPREQ/ CKM input Clock pause request cancellation
CKPACK output
Clock pause acceptance processing
Clock pause state
Normal state
Figure 21.3 Clock Pause Function Timing Chart (PLL Circuit 1 Halted) The clock pause state can be canceled by means of NMI input, in the same way as the normal standby state. The clock pause request should be canceled within four CKIO clock cycles after NMI input. Figure 21.4 shows the timing chart for clock pause state cancellation by means of NMI input (in the case of rising edge detection).
Rev. 2.00 Mar 09, 2006 page 810 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
Frequency modification Max. 4 cycles
CKIO input
CKPREQ/ CKM input NMI input Clock pause request cancellation
CKPACK output
NMI interrupt
Clock pause acceptance processing
Clock pause state
Normal state
Figure 21.4 Clock Pause Function Timing Chart (Cancellation by NMI Input) 21.4.5 Notes on Standby Mode
1. When the chip enters standby mode during use of the cache, disable the cache before making the mode transition. Initialize the cache beforehand when the cache is used after returning to standby mode. The contents of the on-chip RAM are not retained in standby mode when cache is used as on-chip RAM. 2. If an on-chip peripheral register is written in the 10 clock cycles before the chip transits to standby mode, read the register before executing the SLEEP instruction. 3. When using clock mode 0, 1, or 2, the CKIO pin is the clock output pin. Note the following when standby mode is used in these clock modes. When standby mode is canceled by NMI, an unstable clock is output from the CKIO pin during the oscillation settling time after NMI input. This also applies to clock output in the case of cancellation by a power-on reset or manual reset. Power-on reset and manual reset input should be continued for a period at least equal to for the oscillation settling time. 4. Before entering the standby mode, stop operation of the internal DMAC (E-DMAC or DMAC).
Rev. 2.00 Mar 09, 2006 page 811 of 906 REJ09B0292-0200
Section 21 Power-Down Modes
21.5
21.5.1
Module Standby Function
Transition to Module Standby Function
By setting one of bits MSTP11-MSTP3, MSTP1 to 1 in standby control register 1 or 2, the supply of the clock to the corresponding on-chip peripheral module or DSP unit can be halted. This function can be used to reduce the power consumption. Do not perform read/write operations for a module in module standby mode. With the module standby function, the external pins of the DMAC and SIO0-SIO2 on-chip peripheral modules retain their states prior to halting, as do DMAC, DSP, and SIO0-SIO2 registers. The external pins of the FRT, SCIF1-2, and TPU are reset and all their registers are initialized. An on-chip peripheral module corresponding to a module standby bit must not be switched to the module standby state while it is running. Also, interrupts from a module placed in the module stop state should be disabled. 21.5.2 Clearing the Module Standby Function
Clear the module standby function by clearing the MSTP11-MSTP3, MSTP1 bits, or by a poweron reset or manual reset.
Rev. 2.00 Mar 09, 2006 page 812 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Section 22 Electrical Characteristics
22.1 Absolute Maximum Ratings
Table 22.1 shows the absolute maximum ratings. Table 22.1 Absolute Maximum Ratings
Item Power supply voltage (internal) Power supply voltage (5 V I/O) Input voltage (excluding 5 V I/O) Input voltage (5 V I/O) Operating temperature Storage temperature Symbol VCC PVCC Vin Vin Topr Tstg Value -0.3 to +4.2 -0.3 to +7.0 -0.3 to Vcc +0.3 -0.3 to PVcc +0.3 -20 to +75 -55 to +125 Unit V V V V C C
Notes: 1. Permanent damage to the chip may result if the maximum ratings are exceeded. 2. When powering on, turn on the 5 V I/O power supply (PVCC) after, or at the same time as, the internal power supply (VCC). When powering off, cut Vcc after, or at the same time as, PVCC.
Rev. 2.00 Mar 09, 2006 page 813 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.2
DC Characteristics
Tables 22.2 and 22.3 show the DC characteristics. Table 22.2 DC Characteristics Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Input high voltage Symbol Min RES, NMI, VIH MD4 to MD0, TRST, CKPREQ/CKM Both 3.3 V and 5 V EXTAL, CKIO Other input pins Input low voltage RES, NMI, VIL MD4 to MD0, TRST, CKPREQ/CKM Other input pins Schmitt trigger input voltage PB14/RXD1, PB5/SRS1/RXD2 VT VT VT Input leakage current All input pins
-
Typ Max -- VCC + 0.3
Unit Test Conditions V
VCC x 0.9
2.6 VCC x 0.9 VCC x 0.7 -0.3
-- -- -- --
PVCC + 0.3 V VCC + 0.3 VCC + 0.3 VCC x 0.1 V V V
-0.3 -- 4.0 2.6
-
-- -- -- -- -- --
0.8 0.8 -- -- -- 1.0
V V V V V A Vin = 0.5 to VCC - 0.5 V Vin = 0.5 to PVCC - 0.5 V PVCC = 5 V 0.5 V Other than above
+
+ +
VT - VT 0.3 lin --
Three-state All I/O and output leakage pins (off status) current Output high voltage Both 3.3 V and 5 V Other output pins
lTSI
--
--
1.0
A
Vin = 0.5 to VCC - 0.5 V Vin = 0.5 to PVCC - 0.5 V
VOH
PVCC - 0.7 -- VCC - 0.5 VCC - 1.0 -- -- -- --
-- -- -- 0.6 0.4
V V V V V
IOH = -200 A IOH = -200 A IOH = -1 mA IOL = 1.6 mA IOL = 1.6 mA
Output low Both 3.3 V and 5 V voltage Other output pins
VOL
-- --
Rev. 2.00 Mar 09, 2006 page 814 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Pin CAP1, CAP2 capacitance Other input pins Current Normal operation dissipation Symbol Min Cin lcc -- -- -- Typ Max -- -- -- 40 15 350 Unit Test Conditions pF pF mA 3.6 V, CPU operating clock = 62.5 MHz, DMAC used 3.6 V, CPU operating clock = 62.5 MHz, DMAC not used 3.6 V, CPU operating clock = 62.5 MHz, peripheral modules not used Ta = 25C
--
--
300
mA
Sleep mode
--
--
250
mA
Standby mode
--
--
990
A
Note: Do not leave the PLLVcc and PLLVss pins open when the PLL circuit is not used. Connect the PLLVcc pin to Vcc and the PLLVss pin to Vss.
Table 22.3 Permissible Output Currents Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Permissible output low current (per pin) Permissible output low current (total) Permissible output high current (per pin) Permissible output high current (total) Symbol IOL IOL -IOH (-IOH) Min -- -- -- -- Typ -- -- -- -- Max 2.0 80 2.0 25 Unit mA mA mA mA
Note: To protect chip reliability, do not exceed the output current values in table 22.3.
Rev. 2.00 Mar 09, 2006 page 815 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3
AC Characteristics
In principle, input is synchronous. Unless specified otherwise, ensure that the setup time and hold times for each input signal are observed. Table 22.4 Maximum Operating Frequencies Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Operating frequency CPU, DSP External bus (SDRAM not used) External bus (SDRAM used) Peripheral modules Symbol f Min 1 1 1 1 Typ -- -- -- -- Max 62.5 31.25 62.5 31.25 Unit MHz Notes tIcyc tEcyc tEcyc tPcyc
Rev. 2.00 Mar 09, 2006 page 816 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.1
Clock Timing
Table 22.5 Clock Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item EXTAL clock input frequency EXTAL clock input cycle time EXTAL clock input low-level pulse width EXTAL clock input high-level pulse width EXTAL clock input rise time EXTAL clock input fall time CKIO clock input frequency CKIO clock input cycle time CKIO clock input low-level pulse width CKIO clock input high-level pulse width CKIO clock input rise time CKIO clock input fall time CKIO clock output frequency CKIO clock output cycle time CKIO clock output low-level pulse width CKIO clock output high-level pulse width CKIO clock rise time CKIO clock fall time Power-on oscillation stabilization time Standby recovery oscillation stabilization time 1 Standby recovery oscillation stabilization time 2 PLL synchronization stabilization time Notes: 1. 2. 3. 4. 5. 6. Symbol fEX tEXcyc tEXL tEXH tEXR tEXF fCKI tCKIcyc tCKIL tCKIH tCKIR tCKIF fOP tcyc tCKOL tCKOH tCKOR tCKOF tOSC1 tOSC2 tOSC3 tPLL Min 1 32 1 2 8* , 12*
1 2 8* , 12*
Max 31.25 1000 -- -- 4 4 31.25 1000 -- -- 4 4 62.5
5 1000* , *6 125
Unit MHz ns ns ns ns ns MHz ns ns ns ns ns MHz ns ns ns ns ns ms ms ms ms
Figure 22.1
-- -- 1 32 3 4 8* , 12* 8 , 12 -- -- 5 6 1* , 8* 16 3 3 -- -- 10 10 10 1 *3 *4
22.2
22.3
-- -- 5 5 -- -- -- --
22.4 22.5 22.6 22.7
When PLL circuit 2 is operating When PLL circuit 2 is not used When PLL circuit 1 is operating When PLL circuit 1 is not used When PLL circuit 1 and 2 are not used When PLL circuit 1 or 2 is operating Rev. 2.00 Mar 09, 2006 page 817 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
tEXcyc tEXH EXTAL* (input) tEXL VIH 1/2 VCC tEXR
1/2 VCC
VIH
VIH VIL tEXF VIL
Note: * When clock is input from EXTAL pin
Figure 22.1 EXTAL Clock Input Timing
tCKIcyc tCKIH CKIO (input) VIH VIH VIL tCKIF VIL tCKIL VIH 1/2 VCC tCKIR
1/2 VCC
Figure 22.2 CKIO Clock Input Timing
tcyc tCKOH CKIO (output) tCKOL VOH 1/2VCC tCKOR
1/2VCC
VOH
VOH VOL tCKOF VOL
Figure 22.3 CKIO Clock Output Timing
Rev. 2.00 Mar 09, 2006 page 818 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Stable oscillation
CKIO, internal clock
Vcc min
Vcc
tRESW tOSC1
RES
Note: Oscillation stabilization time when using on-chip crystal oscillator
Figure 22.4 Power-On Oscillation Stabilization Time at Power-On
Stable oscillation
Standby CKIO, internal clock
tRESW tOSC2
RES
Note: Oscillation stabilization time when using on-chip crystal oscillator
Figure 22.5 Oscillation Stabilization Time after Standby Recovery (Recovery by RES RES)
Rev. 2.00 Mar 09, 2006 page 819 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Standby CKIO, internal clock Stable oscillation
tOSC3
NMI
Note: Oscillation stabilization time when using on-chip crystal oscillator
Figure 22.6 Oscillation Stabilization Time after Standby Recovery (Recovery by NMI)
Change of oscillation frequency
Stable oscillation
Stable oscillation
EXTAL or CKIO
PLL synchronization
tPLL
PLL synchronization
Internal clock
Figure 22.7 PLL Synchronization Stabilization Time
Rev. 2.00 Mar 09, 2006 page 820 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.2
Control Signal Timing
Table 22.6 Control Signal Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item RES rise and fall time RES pulse width NMI reset setup time NMI reset hold time NMI rise and fall time RES setup time* NMI setup time* IRL3-IRL0 setup time* NMI hold time IRL3-IRL0 hold time* BRLS setup time BRLS hold time BGR delay time Bus tri-state delay time Bus buffer on time Symbol tRESr, tRESf tRESW tNMIRS tNMIRH tNMIr, tNMIf tRESS tNMIS tIRLS tNMIH tIRLH tBLSS tBLSH tBGRD tBOFF tBON Min -- 20 tPcyc + 10 tPcyc + 10 -- 3tEcyc + 40 40 30 20 20 10 5 -- 0 0 Max 200 -- -- -- 200 -- -- -- -- -- -- -- 15 35 35 Unit ns tPcyc ns ns ns ns ns ns ns ns ns ns ns ns ns 22.10 22.9 Figure 22.8
Note: * The RES, NMI, and IRL3-IRL0 signals are asynchronous inputs. If the setup times shown here are observed, a transition is judged to have occurred at the fall of the clock; if the setup times cannot be observed, recognition may be delayed until the next fall of the clock.
tRESf RES tNMIr tNMIf NMI tNMIRS VIH VIL VIH VIL tRESW VIL
tRESr VIH tNMIRH VIH VIL
Figure 22.8 Reset Input Timing
Rev. 2.00 Mar 09, 2006 page 821 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
CKIO
tRESS
RES
VIH VIL tNMIH tNMIS VIH
NMI
tIRLH
IRL3-IRL0
VIL tIRLS VIH VIL
Figure 22.9 Interrupt Signal Input Timing
CKIO
tBLSH
BRLS (input)
tBLSS
tBLSH tBGRD
tBLSS
tBGRD
BGR (output)
tBOFF
RD, RD/WR, RAS, CAS, CSn, WEn, BS, IVECF A24-A0, D31-D0
tBON
tBOFF
tBON
Figure 22.10 Bus Release Timing
Rev. 2.00 Mar 09, 2006 page 822 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.3
Bus Timing
Table 22.7 PLL-On Bus Timing [Modes 0 and 4] (1) Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Address delay time BS delay time CS delay time 1 CS delay time 2 Read/write delay time Read strobe delay time 1 Read data setup time 1 Read data setup time 2 (EDO) Read data hold time 2 Read data hold time 4 (SDRAM) Read data hold time 5 (DRAM) Read data hold time 6 (EDO) Read data hold time 7 (EDO) Read data hold time 8 (interrupt vector) Write enable delay time 1 Write data delay time 1 (except Eo: Io = 1:1) Write data delay time 2 (Eo: Io = 1:1) Write data hold time 1 Data buffer on time Data buffer off time Symbol Min tAD tBSD tCSD1 tCSD2 tRWD tRSD1 tRDS1 tRDS2 tRDH2 tRDH4 tRDH5 tRDH6 tRDH7 tRDH8 tWED1 tWDD1 tWDD2 tWDH1 tDON tDOF 1 -- 1 -- 1 -- 8 8 6.5 0 2 0 3 1 2 -- -- -- 2 -- -- Max Unit Figure 14 15 14 14 14 14 -- -- -- -- -- -- -- -- -- 14 22 12 -- 15 15 ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns 22.11, 12, 15, 16, 18, 20, 22, 24 to 28, 30 to 34, 37 to 40, 42 to 44 22.11, 12, 15, 16, 18, 20, 22, 24, 25, 28, 30, 31, 33, 34, 39, 42 to 44 22.11, 12, 15, 16, 18, 20, 22 to 25, 28, 30 to 34, 39, 41, 42 22.11, 12, 33, 34, 39, 42 22.11, 12, 15 ,16, 18, 20 to 22, 24, 25, 28 to 34, 39, 42 to 44 22.11, 12, 15, 16, 22, 30, 33, 34, 37, 39, 40, 42 to 44 22.11, 33, 37, 42 to 44 22.39, 40 22.15, 16 22.11, 42 22.15, 16 22.33, 37 22.39, 40 22.39 22.43, 44 22.11, 12 22.12, 22, 24, 26, 34, 38 22.25, 27 22.12, 22, 24 to 27, 34, 38 22.12, 22, 24, 25, 34 22.12, 22, 24, 25, 34
Read data setup time 3 (SDRAM) tRDS3
Rev. 2.00 Mar 09, 2006 page 823 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item DACK delay time 1 DACK delay time 2 WAIT setup time WAIT hold time RAS delay time 1 (SDRAM) RAS delay time 2 (DRAM, EDO) RAS delay time 3 (EDO) CAS delay time 1 (SDRAM) CAS delay time 2 (DRAM) DQM delay time CKE delay time OE delay time 1 OE delay time 2 IVECF delay time Row address setup time Column address setup time Data input setup time Read/write address setup time REFOUT delay time Symbol Min tDACD1 tDACD2 tWTS tWTH tRASD1 tRASD2 tRASD3 tCASD1 tCASD2 tDQMD tCKED tOED1 tOED2 tIVD tASR tASC tDS tAS tREFOD -- -- 10 5 1 -- -- 1 -- 1 1 -- -- -- 0 0 0 0 -- Max 14 14 -- -- 14 14 14 14 14 14 14 14 14 15 -- -- -- -- 15 Unit ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns Figure 22.11, 12, 15, 18, 20, 22, 24, 25, 28, 33, 34, 37 to 40, 42 22.11, 12, 33, 34, 37 to 40, 42 22.13, 14, 35, 36, 42 to 45 22.13, 14, 35, 36, 42 to 45 22.15 to 18, 20 to 25, 28 to 32 22.33, 34, 39, 41 22.39 22.15, 16, 17, 18, 22 to 28, 30 to 32, 42 22.33, 34, 37 to 41 22.15, 16, 18 to 20, 22, 24 to 29 22.32 22.39 22.39 22.43, 44 22.33, 34, 39 22.33, 34, 37, 38, 39 22.34, 38 22.11, 12 22.46
Rev. 2.00 Mar 09, 2006 page 824 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Table 22.7 PLL-On Bus Timing [Modes 0 and 4] (2) Conditions: VCC = PLLVCC = 3.3 V 5%, PVCC = 5.0 V 5%/3.3 V 5%, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -5 to +70C, SDRAM bus cycle
Item Read data setup time 3 (SDRAM) Read data hold time 4 (SDRAM) Write data delay time 2 (Eo: Io = 1:1) Write data hold time 1 Address delay time CS delay time 1 Read/write delay time DQM delay time RAS delay time 1 (SDRAM) CAS delay time 1 (SDRAM) CKE delay time Symbol tRDS3 tRDH4 tWDD2 tWDH1 tAD tCSD1 tRWD tDQMD tRASD1 tCASD1 tCKED Min 6.5 1.5 -- 2 4 2.5 2.5 2.5 2.5 2.5 2.5 Max -- -- 9.5 -- 11 9.5 9.5 9.5 9.5 9.5 9.5 Unit ns ns ns ns ns ns ns ns ns ns ns Figure 22.15, 16 22.15, 16 22.25, 27 22.25, 27 22.15, 16, 18, 20, 22, 24, 25, 26, 27, 28, 30, 31, 32 22.15, 16, 18, 20, 22, 23, 24, 25, 28, 30, 31, 32 22.15, 16, 18, 20, 21, 22, 24, 25, 28, 29, 30, 31, 32 22.15, 16, 18, 19, 20, 22, 24, 25, 26, 27, 28, 29 22.15, 16, 17, 20, 21, 22, 23, 24, 25, 28, 29, 30, 31, 32 22.15, 16, 17, 18, 22, 23, 24, 25, 26, 27, 28, 30, 31, 32 22.32
Rev. 2.00 Mar 09, 2006 page 825 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1
T2
CKIO
tAD tAD tAS
tBSD tBSD
A24-A0
BS
tCSD1 tCSD2
CSn
tRWD tRWD
RD/WR
tRSD1
tRSD1
RD WEn DQMxx
tWED1 tWED1
tRDH2*1 tRDS1
D31-D0
tDACD1
tDACD2
DACKn*2
WAIT
RAS
CAS OE
CKE
Notes: 1. tRDH2 is measured from the rise of CSn or RD, whichever comes first. 2. DACKn waveform when active-high is specified
Figure 22.11 Basic Read Cycle (No Wait)
Rev. 2.00 Mar 09, 2006 page 826 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 T2
CKIO
tAD tAD
A24-A0
tBSD tAS tBSD
BS
tCSD1
tCSD2
CSn
tRWD tRWD
RD/WR
tRSD1
tRSD1
RD
tWED1 tWED1
WEn DQMxx
tWDD1 tDON tDOF tWDH1
D31-D0
tDACD1
tDACD2
DACKn*
WAIT
RAS
CAS OE
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.12 Basic Write Cycle (No Wait)
Rev. 2.00 Mar 09, 2006 page 827 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 Tw T2
CKIO
A24-A0
BS
CSn
RD/WR
RD
WEn DQMxx
D31-D0
DACKn*
tWTS tWTH
WAIT
RAS
CAS OE
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.13 Basic Bus Cycle (1 Wait Cycle)
Rev. 2.00 Mar 09, 2006 page 828 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 Tw Twx T2
CKIO
A24-A0
BS
CSn
RD/WR
RD WEn DQMxx
D31-D0
DACKn*
tWTS tWTH tWTS tWTH
WAIT
RAS
CAS OE
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.14 Basic Bus Cycle (External Wait Input)
Rev. 2.00 Mar 09, 2006 page 829 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tr
Tc
Td1
Td2
Td3
Td4
Tde
CKIO
tAD tAD
Address upper bits
tAD
Address lower bits
tBSD tBSD
BS
tCSD1 tCSD1
CSn
tRWD tRWD
RD/WR
tRSD1
RD WEn DQMxx
tDQMD tDQMD
tRDS3
tRDH4 tRDS3 tRDH4 tRDS3
tRDH4 tRDS3
tRDH4
D31-D0
tDACD1 tDACD1
DACKn*2
WAIT
tRASD1 tRASD1 tRASD1
RAS
tCASD1 tCASD1 tCASD1 tCASD1
CAS * OE
*1
CKE
Notes: 1. Dotted line shows the case where synchronous DRAM in a different CS space is accessed. 2. DACKn waveform when active-high is specified
Figure 22.15 Synchronous DRAM Read Bus Cycle (RCD = 1 Cycle, CAS Latency = 1 Cycle, Burst = 4)
Rev. 2.00 Mar 09, 2006 page 830 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tr
Tc
Td1
Td2
Td3
Td4
Tde
CKIO
tAD tAD
Address upper bits
tAD
Address lower bits
tBSD tBSD
BS
tCSD1 tCSD1
CSn
tRWD tRWD
RD/WR
tRSD1
RD
tDQMD
WEn DQMxx
tRDS3 tRDH4
tDQMD
tDQMD
D31-D0
DACKn*2
WAIT
tRASD1 tRASD1 tRASD1
RAS CAS OE CKE
tCASD1 tCASD1 tCASD1 tCASD1
*1
Notes: 1. Dotted line shows the case where synchronous DRAM in a different CS space is accessed. 2. DACKn waveform when active-high is specified
Figure 22.16 Synchronous DRAM Single Read Bus Cycle (RCD = 1 Cycle, CAS Latency = 1 Cycle, Burst = 4)
Rev. 2.00 Mar 09, 2006 page 831 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tr CKIO
Trw
Tc
Tw
Td1
Td2
Td3
Td4
TdE
Address upper bits Address lower bits
BS
CSn RD/WR
RD
WEn DQMxx D31-D0
DACKn*2 WAIT tRASD1 RAS tCASD1 CAS-OE tCASD1 *1 tRASD1
CKE
Notes: 1. Dotted line shows the case where synchronous DRAM in a different CS space is accessed. 2. DACKn waveform when active-high is specified
Figure 22.17 Synchronous DRAM Read Bus Cycle (RCD = 2 Cycles, CAS Latency = 2 Cycles, Burst = 4)
Rev. 2.00 Mar 09, 2006 page 832 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tnop
Tc
Td1
Td2
Td3
Td4
Tde
CKIO
tAD
Address upper bits Address lower bits BS
tCSD1
tBSD
CSn
tRWD
RD/WR
RD
tDQMD
WEn DQMxx D31-D0
tDACD1
DACKn* WAIT
tRASD1
RAS
tCASD1 tCASD1 tCASD1 tCASD1
CAS
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.18 Synchronous DRAM Read Bus Cycle (Bank Active, Same Row Access, CAS Latency = 1 Cycle)
Rev. 2.00 Mar 09, 2006 page 833 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
TC
TW
Td1
Td2
Td3
Td4
Tde
CKIO Address upper bits Address lower bits BS
CSn
RD/WR
RD
tDQMD
WEn DQMxx D31-D0
DACKn*
WAIT
RAS CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.19 Synchronous DRAM Read Bus Cycle (Bank Active, Same Row Access, CAS Latency = 2 Cycles)
Rev. 2.00 Mar 09, 2006 page 834 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp
Tr
Tc
Td1
Td2
Td3
Td4
Tde
CKIO
tAD
Address upper bits
tAD
Address lower bits
tBSD
BS
tCSD1
CSn
tRWD tRWD
RD/WR
RD WEn DQMxx D31-D0
tDACD1 tDQMD
DACKn*
WAIT
tRASD1 tRASD1
RAS CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.20 Synchronous DRAM Read Bus Cycle (Bank Active, Different Row Access, TRP = 1 Cycle, RCD = 1 Cycle, CAS Latency = 1 Cycle)
Rev. 2.00 Mar 09, 2006 page 835 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tpw Tr Tc Td1 Tde
CKIO Address upper bits Address lower bits BS
CSn
tRWD
RD/WR
RD WEn DQMxx D31-D0
DACKn*
WAIT
tRASD1 tRASD1
RAS CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.21 Synchronous DRAM Read Bus Cycle (Bank Active, Different Row Access, TRP = 2 Cycles, RCD = 1 Cycle, CAS Latency = 1 Cycle)
Rev. 2.00 Mar 09, 2006 page 836 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tr
Tc
Tap
CKIO
tAD tAD
Address upper bits
tAD
Address lower bits
tBSD tBSD
BS
tCSD1 tCSD1 tCSD1
CSn
tRWD tRWD tRWD
*1
RD/WR
tRSD1
RD
tDQMD tDQMD
WEn DQMxx
tWDD1 tDON tDOF tWDH1
D31-D0
tDACD1 tDACD1 tDACD1
DACKn*2
*1
WAIT
tRASD1 tRASD1 tRASD1 tRASD1
RAS CAS OE CKE
tCASD1 tCASD1 tCASD1
*1
Notes: 1. Dotted line shows the case where synchronous DRAM in a different CS space is accessed. 2. DACKn waveform when active-high is specified
Figure 22.22 Synchronous DRAM Write Bus Cycle (RASD = 0, RCD = 1 Cycle, TRWL = 1 Cycle)
Rev. 2.00 Mar 09, 2006 page 837 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tr Trw Tc Trwl Tap
CKIO
Address upper bits Address lower bits BS
tCSD1
CSn
RD/WR
RD WEn DQMxx
D31-D0
DACKn*2
WAIT
tRASD1 tRASD1
RAS CAS OE
tCASD1
*1
*1
CKE
Notes: 1. Dotted line shows the case where synchronous DRAM in a different CS space is accessed. 2. DACKn waveform when active-high is specified
Figure 22.23 Synchronous DRAM Write Bus Cycle (RASD = 0, RCD = 2 Cycles, TRWL = 2 Cycles)
Rev. 2.00 Mar 09, 2006 page 838 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tc
CKIO
tAD tAD
Address upper bits Address lower bits BS
tCSD1 tCSD1
tBSD
tBSD
CSn
tRWD tRWD
RD/WR
RD
tDQMD tDQMD
WEn DQMxx
tWDD1 tDON tDOF tWDH1
D31-D0
tDACD1
tDACD1
DACKn* WAIT
tRASD1
RAS
tCASD1 tCASD1
CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.24 Synchronous DRAM Write Bus Cycle (Bank Active, Same Row Access, I:E other than 1:1)
Rev. 2.00 Mar 09, 2006 page 839 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tc
CKIO
tAD tAD
Address upper bits Address lower bits
tBSD tBSD
BS
tCSD1 tCSD1
CSn
tRWD tRWD
RD/WR
RD
tDQMD tDQMD
WEn DQMxx
tWDD2 tDON tDOF tWDH1
D31-D0
tDACD1
tDACD1
DACKn* WAIT
tRASD1
RAS
tCASD1 tCASD1
CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.25 Synchronous DRAM Write Cycle (Bank Active, Same Row Access, I:E = 1:1)
Rev. 2.00 Mar 09, 2006 page 840 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tc Tc
CKIO
tAD
Address upper bits Address lower bits
BS
CSn
RD/WR
RD
tDQMD
WEn DQMxx
tWDD1 tWDH1
D31-D0
DACKn*
WAIT
RAS
tCASD1
tCASD1
CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.26 Synchronous DRAM Continuous Write Cycle (Bank Active, Same Row Access, I:E other than 1:1)
Rev. 2.00 Mar 09, 2006 page 841 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tc Tc
CKIO
tAD
Address upper bits Address lower bits
BS
CSn
RD/WR
RD
tDQMD
WEn DQMxx
tWDD2 tWDH1
D31-D0
DACKn*
WAIT
RAS
tCASD1
tCASD1
CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.27 Synchronous DRAM Continuous Write Cycle (Bank Active, Same Row Access, I:E = 1:1)
Rev. 2.00 Mar 09, 2006 page 842 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc
CKIO
tAD
Address upper bits Address lower bits
tBSD
BS
tCSD1
CSn
tRWD tRWD
RD/WR
RD
tDQMD tDQMD
WEn DQMxx
D31-D0
tDACD1
DACKn*
WAIT
tRASD1
RAS
tCASD1
CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.28 Synchronous DRAM Write Bus Cycle (Bank Active, Different Row Access, TRP = 1 Cycle, RCD = 1 Cycle)
Rev. 2.00 Mar 09, 2006 page 843 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp
Tpw
Tr
Trw
Tc
CKIO
Address upper bits Address lower bits
BS
CSn
tRWD
RD/WR
RD
tDQMD
WEn DQMxx
D31-D0
DACKn*
WAIT
tRASD1 tRASD1
RAS CAS OE
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.29 Synchronous DRAM Write Bus Cycle (Bank Active, Different Row Access, TRP = 2 Cycles, RCD = 2 Cycles)
Rev. 2.00 Mar 09, 2006 page 844 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Trr Trc1 Trc2 Tre
CKIO
Address upper bits
tAD tAD
Address lower bits
tBSD
BS
tCSD1
tCSD1
CSn
tRWD
tRWD
RD/WR
RD WEn DQMxx
D31-D0
DACKn
WAIT
tRASD1 tRASD1
tRSD1
RAS
tCASD1 tCASD1
CAS OE CKE
Note: An auto-refresh cycle is always preceded by a precharge cycle. The number of cycles between the two is determined by the number of cycles specified by TRP.
Figure 22.30 Synchronous DRAM Auto-Refresh Cycle (TRAS = 4 Cycles)
Rev. 2.00 Mar 09, 2006 page 845 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Trr Trc1 Trc2 Tre
CKIO Address upper bits
tAD tAD
Address lower bits
tBSD
BS
tCSD1
CSn
tRWD tRWD
RD/WR
RD WEn DQMxx
D31-D0
DACKn
WAIT
tRASD1
RAS
tCASD1
CAS OE CKE
Figure 22.31 Synchronous DRAM Auto-Refresh Cycle (Shown from Precharge Cycle, TRP = 1 Cycle, TRAS = 4 Cycles)
Rev. 2.00 Mar 09, 2006 page 846 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Trr Trc1 Trc2 Tre Trc1 Tre
CKIO Address upper bits
tAD tAD
Address lower bits BS
tCSD1
tCSD1
CSn
tRWD
RD/WR
RD WEn DQMxx D31-D0 DACKn
WAIT
tRASD1 tRASD1
tRASD1
RAS CAS OE CKE
tCASD1 tCASD1
tCKED
tCKED
Note: A self-refresh cycle is always preceded by a precharge cycle. The number of cycles between the two is determined by the number of cycles specified by TRP.
Figure 22.32 Synchronous DRAM Self-Refresh Cycle (TRAS = 3)
Rev. 2.00 Mar 09, 2006 page 847 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc1 Tc2
CKIO
tAD tAD
Address upper bits
tASR tAD
Address lower bits
tBSD
BS
tCSD2 tCSD1
CSn
tRWD tRWD
RD/WR
tRSD1 tRSD1 tRSD1
RD
tCASD2 tCASD2 tCASD2 tASC tRDS1 tRDH5*1
CASxx
D31-D0
tDACD1 tDACD2
DACKn*2
WAIT
tRASD2 tRASD2 tRASD2
RAS CAS OE CKE
Notes: 1. tRDH5 is measured from the rise of RD or CASxx, whichever comes first. 2. DACKn waveform when active-high is specified
Figure 22.33 DRAM Read Cycle (TRP = 1 Cycle, RCD = 1 Cycle, No Wait)
Rev. 2.00 Mar 09, 2006 page 848 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc1 Tc2
CKIO
tAD tAD
Address upper bits
tASR
tAD
Address lower bits
tBSD
BS
tCSD2 tCSD1
CSn
tRWD tRWD
RD/WR
tRSD1
RD
tCASD2
tASC
tCASD2 tWDD1 tDON tCASD2
CASxx
tDOF
tDS
tWDH1
D31-D0
tDACD1 tDACD2
DACKn*
WAIT
tRASD2 tRASD2 tRASD2
RAS CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.34 DRAM Write Cycle (TRP = 1 Cycle, RCD = 1 Cycle, No Wait)
Rev. 2.00 Mar 09, 2006 page 849 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp CKIO Tpw Tr Trw Tc1 Tw Tc2
Address upper bits Address lower bits
BS
CSn
RD/WR
RD
CASxx
D31-D0
DACKn* tWTS WAIT tWTH
RAS
CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.35 DRAM Bus Cycle (TRP = 2 Cycles, RCD = 2 Cycles, 1 Wait)
Rev. 2.00 Mar 09, 2006 page 850 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc1 Tw Twx Tc2
CKIO Address upper bits Address lower bits
BS
CSn
RD/WR
RD
CASxx
D31-D0
DACKn*
tWTS tWTH tWTS tWTH
WAIT
RAS CAS OE
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.36 DRAM Bus Cycle (TRP = 1 Cycle, RCD = 1 Cycle, External Wait Input)
Rev. 2.00 Mar 09, 2006 page 851 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp
Tr
Tc1
Tc2
Tc1
Tc2
CKIO Address upper bits
tAD tAD
Address lower bits
BS
CSn
RD/WR
tRSD1 tRSD1
RD
tCASD2 tCASD2
CASxx
tASC tRDS1 tRDH5*1 tASC tRDS1 tRDH5*1
D31-D0
tDACD2 tDACD1
DACKn*2
WAIT
RAS CAS OE CKE
Notes: 1. tRDH5 is measured from the rise of RD or CASxx, whichever comes first. 2. DACKn waveform when active-high is specified
Figure 22.37 DRAM Burst Read Cycle (TRP = 1 Cycle, RCD = 1 Cycle, No Wait)
Rev. 2.00 Mar 09, 2006 page 852 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc1 Tc2 Tc1 Tc2
CKIO Address upper bits
tAD
Address lower bits
BS
CSn
RD/WR
RD
tCASD2
tASC tCASD2
CASxx
tWDD1 tDS tWDH1 tDS
D31-D0
tDACD2 tDACD1
DACKn*
WAIT
RAS CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.38 DRAM Burst Write Cycle (TRP = 1 Cycle, RCD = 1 Cycle, No Wait)
Rev. 2.00 Mar 09, 2006 page 853 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc1 Tc2
CKIO
tAD tAD
Address upper bits
tASR tAD
Address lower bits
tBSD
BS
tCSD2 tCSD1
CSn
tRWD tRWD
RD/WR
tRSD1 tRSD1 tRSD1
RD
tCASD2 tCASD2 tCASD2
CASxx
tASC tRDS2
tRDH6
D31-D0
tDACD1
tDACD2
tRDH7*2
DACKn*1
WAIT
tRASD2 tRASD2
tRASD3
RAS CAS OE CKE
tOED1 tOED1 tOED2
Notes: 1. DACKn waveform when active-high is specified 2. tRDH7 is measured from the rise of RAS or CAS * OE, whichever comes first.
Figure 22.39 EDO Read Cycle (TRP = 1 Cycle, RCD = 1 Cycle, No Wait)
Rev. 2.00 Mar 09, 2006 page 854 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Tr Tc1 Tc2 Tc1 Tc2
CKIO Address upper bits
tAD
Address lower bits
BS
CSn
RD/WR
tRSD1 tRSD1
RD
tCASD2 tCASD2
CASxx
tASC tRDS2 tRDH6 tRDS2 tRDH6
D31-D0
tDACD2 tDACD1
DACKn*
WAIT
RAS CAS OE CKE
Note: * DACKn waveform when active-high is specified
Figure 22.40 EDO Burst Read Cycle (TRP = 1 Cycle, RCD = 1 Cycle, No Wait)
Rev. 2.00 Mar 09, 2006 page 855 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Tp Trr Trc1 Trc2 Tre
CKIO
Address upper bits Address lower bits
BS
tCSD1 tCSD1
CSn
RD/WR
RD
tCASD2 tCASD2 tCASD2
CASxx
D31-D0
DACKn
WAIT
tRASD2 tRASD2 tRASD2
RAS CAS OE CKE
Figure 22.41 DRAM CAS CAS-Before-RAS Refresh Cycle RAS (TRP = 1 Cycle, TRAS = 2 Cycles)
Rev. 2.00 Mar 09, 2006 page 856 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 TW T2 TW T2
CKIO
tAD tAD tAD
A24-A0
tBSD tBSD tBSD tBSD
BS
tCSD1 tCSD2
CSn
tRWD tRWD
RD/WR
tRSD1 tRSD1 tRSD1 tRSD1
RD
tCASD1 tCASD1 tRDH2 tRDS1 tRDS1 tRDH2
CASxx
D31-D0
tDACD1 tDACD2 tDACD1 tDACD2
DACKn*
tWTS tWTH tWTS tWTH
WAIT
RAS CAS OE
CKE
Note: * DACKn waveform when active-high is specified
Figure 22.42 Burst ROM Read Cycle (Wait = 1)
Rev. 2.00 Mar 09, 2006 page 857 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 CKIO
tAD tAD
T2
T3
T4
A3-A0
tBSD
tBSD
BS
tIVD tIVD
IVECF
tRWD
tRWD
RD/WR
tRSD1
tRSD1
RD
tRSD1
tRDH8
D7-D0
tWTS tWTH
WAIT
Figure 22.43 Interrupt Vector Fetch Cycle (No Wait, I:E = 1:1)
Rev. 2.00 Mar 09, 2006 page 858 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 CKIO
tAD tAD
T2
A3-A0
tBSD
tBSD
BS
tIVD tIVD
IVECF
tRWD
RD/WR
tRSD1 tRSD1
RD
tRSD1 tRDH8
D7-D0
tWTS tWTH
WAIT
Figure 22.44 Interrupt Vector Fetch Cycle (No Wait, I:E other than 1:1)
Rev. 2.00 Mar 09, 2006 page 859 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
T1 CKIO TW T2
A3-A0
BS
IVECF
RD/WR
RD
D7-D0
tWTS tWTH tWTS tWTH
WAIT
Figure 22.45 Interrupt Vector Fetch Cycle (External Wait Input, I:E other than 1:1)
CKIO
tREFOD REFOUT
Figure 22.46 REFOUT Delay Time
Rev. 2.00 Mar 09, 2006 page 860 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.4
Direct Memory Access Controller Timing
Table 22.8 Direct Memory Access Controller Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item DREQ0, DREQ1 setup time DREQ0, DREQ1 hold time Symbol tDRQS tDRQH Min 10 5 Max -- -- Unit ns ns Figure 22.47
CKIO
tDRQS
DREQ0, DREQ1
tDRQH
Figure 22.47 DREQ0, DREQ1 Input Timing
Rev. 2.00 Mar 09, 2006 page 861 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.5
Free-Running Timer Timing
Table 22.9 Free-Running Timer Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Output compare output delay time Input capture input setup time (tEcyc:tPcyc = 1:1) Input capture input setup time (tEcyc:tPcyc = 1:2) Input capture input setup time (tEcyc:tPcyc = 1:4) Input capture input hold time Timer clock input setup time (tEcyc:tPcyc = 1:1) Timer clock input setup time (tEcyc:tPcyc = 1:2) Timer clock input setup time (tEcyc:tPcyc = 1:4) Timer clock pulse width (single edge specified) Timer clock pulse width (both edges specified) Symbol tFOCD tFICS tFICS tFICS tFICH tFCKS tFCKS tFCKS tFCKWH tFCKWL Min -- 50 tcyc + 50 3tcyc + 50 50 50 tcyc + 50 3tcyc + 50 4.5 8.5 Max 100 -- -- -- -- -- -- -- -- -- Unit ns ns ns ns ns ns ns ns tPcyc tPcyc Figure 22.48, 22.49 22.48 22.49 22.49 22.48, 22.49 22.50 22.51 22.51 22.50, 22.51
CKIO tFOCD FTOA, FTOB tFICS FTI tFICH
Figure 22.48 FRT Input/Output Timing (tEcyc:tPcyc = 1:1)
Rev. 2.00 Mar 09, 2006 page 862 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
CKIO tFOCD FTOA, FTOB tFICS FTI tFICH
Figure 22.49 FRT Input/Output Timing (tEcyc:tPcyc other than 1:1)
CKIO tFCKS FTCI tFCKWL tFCKWH
Figure 22.50 FRT Clock Input Timing (tEcyc:tPcyc = 1:1)
CKIO tFCKS FTCI tFCKWL tFCKWH
Figure 22.51 FRT Clock Input Timing (tEcyc:tPcyc other than 1:1)
Rev. 2.00 Mar 09, 2006 page 863 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.6
Serial Communication Interface Timing
Table 22.10 Serial Communication Interface Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Input clock cycle Input clock cycle (synchronous mode) Input clock pulse width Transmit data delay time (synchronous mode) Receive data setup time (synchronous mode) Receive data hold time (synchronous mode) RTS delay time CTS setup time (synchronous mode) CTS hold time (synchronous mode) Symbol tscyc tscyc tSCKW tTXD tRXS tRXH tRTSD tCTSS tCTSH Min 4 6 0.4 -- 100 100 -- 100 100 Max -- -- 0.6 100 -- -- 100 -- -- Unit tPcyc tPcyc tcscyc ns ns ns ns ns ns 22.54 Figure 22.52 22.53 22.52 22.53
tSCKW SCK SCK1 SCK2
tscyc
Figure 22.52 Input Clock Input/Output Timing
Rev. 2.00 Mar 09, 2006 page 864 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
tscyc SCK tTXD TxD (transmit data) tRXS RxD (receive data) tRXH
Figure 22.53 SCI Input/Output Timing (Synchronous Mode)
tscyc SCK1 tRTSD RTS tCTSS CTS tCTSH
Figure 22.54 RTS and CTS Input/Output Timing
Rev. 2.00 Mar 09, 2006 page 865 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
Table 22.11 16-Bit Timer-Pulse Unit Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Timer output delay time Timer input setup time (tEcyc:tPcyc = 1:1) Timer input setup time (tEcyc:tPcyc = 1:2) Timer input setup time (tEcyc:tPcyc = 1:4) Timer clock input setup time (tEcyc:tPcyc = 1:1) Timer clock input setup time (tEcyc:tPcyc = 1:2) Timer clock input setup time (tEcyc:tPcyc = 1:4) Timer clock pulse width Single edge specified Both edges specified Symbol tTOCD tTICS tTICS tTICS tTCKS tTCKS tTCKS tTCKWH tTCKWL Min -- 50 tcyc + 50 3tcyc + 50 50 tcyc + 50 3tcyc + 50 1.5 2.5 Max 100 -- -- -- -- -- -- -- -- Unit ns ns ns ns ns ns ns tcyc 22.57 22.55, 22.56 Figure 22.55, 22.56
CKIO
tTOCD
Output compare output*
tTICS
Input capture input* Note: * TIOCA0-TIOCA2, TIOCB0-TIOCB2, TIOCC0, TIOCD0
Figure 22.55 TPU Input/Output Timing (tEcyc:tPcyc = 1:1)
Rev. 2.00 Mar 09, 2006 page 866 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
CKIO
tTOCD
Output compare output*
tTICS
Input capture input* Note: * TIOCA0-TIOCA2, TIOCB0-TIOCB2, TIOCC0, TIOCD0
Figure 22.56 TPU Input/Output Timing (tEcyc:tPcyc other than 1:1)
CKIO
tTCKS tTCKS
TCLKA-TCLKD
tTCKWL tTCKWH
Figure 22.57 TPU Clock Input Timing
Rev. 2.00 Mar 09, 2006 page 867 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.7
Watchdog Timer Timing
Table 22.12 Watchdog Timer Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item WDTOVF delay time Symbol tWOVD Min -- Max 70 Unit ns Figure 22.58, 22.59
CKIO
tWOVD
tWOVD
WDTOVF
Figure 22.58 Watchdog Timer Output Timing (tEcyc:tPcyc = 1:1)
CKIO tWOVD WDTOVF tWOVD
Figure 22.59 Watchdog Timer Output Timing (tEcyc:tPcyc other than 1:1)
Rev. 2.00 Mar 09, 2006 page 868 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.8
Serial I/O with FIFO / Serial I/O Timing
Table 22.13 Serial I/O with FIFO / Serial I/O Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item SRCK0, STCK0 clock input cycle time SRCKn, STCKn clock input cycle time (n = 1 or 2) SRCK0, STCK0 clock input low-level width SRCKn, STCKn clock input low-level width (n = 1 or 2) Symbol tSFcyc tSIcyc tSFWL tWL Min -- tPcyc or* 66.7 0.4 x tSFcyc 0.4 x tSIcyc 0.4 x tSFcyc 0.4 x tSIcyc 15 10 15 10 1 15 10 0 0 Max 2 -- -- -- -- -- -- -- -- -- -- -- -- 20 20 Unit tPcyc ns ns ns ns ns ns ns ns ns tPcyc ns ns ns ns 22.63 22.62, 22.63 22.62 22.61 Figure 22.60
SRCK0, STCK0 clock input high-level width tSFWH SRCKn, STCKn clock input high-level width tWH (n = 1 or 2) SRS input setup time SRS input hold time SRXD input setup time SRXD input hold time STS0 input setup time STSn input setup time (n = 1 or 2) STS input hold time STS output delay time STXD output delay time tRSS tRSH tSRDS tSRDH tSFTSS tTSS tTSH tTSD tTDD
Note: * Specified as tPcyc or 66.7, whichever is greater.
Rev. 2.00 Mar 09, 2006 page 869 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
[SIOF] tSFcyc tSFWL STCK0, SRCK0 tSFWH [SIO] tWL STCKn, SRCKn n = 1 or 2 tWH
tSIcyc
Figure 22.60 SIOF / SIO Input Clock Timing
SRCKn (input) tRSS SRSn (input) SRXDn (input) n = 0, 1, or 2 tRSH tSRDS tSRDH
Figure 22.61 SIOF / SIO Receive Timing
Rev. 2.00 Mar 09, 2006 page 870 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
[SIOF] STCK0 (input) tSFTSS STS0 (input) tTDD STXD0 (output) [SIO] STCKn (input) tTSS STSn (input) tTDD STXDn (output) n = 1, or 2 tTDD tTSH tTDD tTSH
Figure 22.62 SIOF / SIO Transmit Timing (TMn = 0 Mode)
STCKn (input) tTSD STSn (output) tTDD STXDn (output) n = 0, 1, or 2 tTDD tTSD
Figure 22.63 SIOF / SIO Transmit Timing (TMn = 1 Mode)
Rev. 2.00 Mar 09, 2006 page 871 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.9
User Debug Interface Timing
Table 22.14 User Debug Interface Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item TCK clock input cycle time TCK clock input high-level width TCK clock input low-level width TRST pulse width TRST setup time TMS setup time TMS hold time TDI setup time TDI hold time TDO delay time Symbol ttcyc tTCKH tTCKL tTRSW tTRSS tTMSS tTMSH tTDIS tTDIH tTDOD Min tPcyc or* 66.7 ns 0.4 0.4 20 40 30 10 30 10 0 Max -- 0.6 0.6 -- -- -- -- -- -- 30 Unit ns ttcyc ttcyc ttcyc ns ns ns ns ns ns 22.66 22.65 Figure 22.64
Note: * Specified as tPcyc or 66.7, whichever is greater.
ttcyc tTCKH TCK tTCKL
Figure 22.64 H-UDI Clock Timing
TCK
tTRSS TRST tTRSW
tTRSS
Figure 22.65 H-UDI TRST Timing
Rev. 2.00 Mar 09, 2006 page 872 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
TCK tTMSS TMS tTDIS TDI tTDOD TDO tTDOD tTDIH tTMSH
Figure 22.66 H-UDI Input/Output Timing 22.3.10 I/O Port Timing Table 22.15 I/O Port Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item Port output data delay time Port input data setup time (tEcyc:tPcyc = 1:1) Port input data setup time (tEcyc:tPcyc = 1:2) Port input data setup time (tEcyc:tPcyc = 1:4) Port input data hold time Symbol tPWD tPRS tPRS tPRS tPRH Min -- 50 tcyc + 50 3tcyc + 50 50 Max 50 -- -- -- -- Unit ns ns ns ns ns 22.67, 22.68 Figure 22.67, 22.68 22.67 22.68
Rev. 2.00 Mar 09, 2006 page 873 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
CKIO tPRS PA0-PA13 PB0-PB15 (read) PA0-PA13 PB0-PB15 (write) tPRH
tPWD
Figure 22.67 I/O Port Input/Output Timing (tEcyc:tPcyc = 1:1)
CKIO tPRS PA0-PA13 PB0-PB15 (read) PA0-PA13 PB0-PB15 (write) tPRH
tPWD
Figure 22.68 I/O Port Input/Output Timing (tEcyc:tPcyc 1:1)
Rev. 2.00 Mar 09, 2006 page 874 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.3.11 Ethernet Controller Timing Table 22.16 Ethernet Controller Timing Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item TX-CLK cycle time TX-EN output delay time ETXD[3:0] output delay time CRS setup time CRS hold time COL setup time COL hold time RX-CLK cycle time RX-DV setup time RX-DV hold time ERXD[3:0] setup time ERXD[3:0] hold time RX-ER setup time RX-ER hold time MDIO setup time MDIO hold time MDIO output data hold time* WOL output delay time EXOUT output delay time CAMSEN setup time CAMSEN hold time Symbol tTcyc tTENd tETDd tCRSs tCRSh tCOLs tCOLh tRcyc tRDVs tRDVh tERDs tERDh tRERs tRERh tMDIOs tMDIOh tMDIOdh tWOLd tEXOUTd tCAMs tCAMh Min 2.4 3 3 10 10 10 10 2.4 10 3 10 3 10 3 10 10 5 1 1 10 3 Typ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Max -- 20 20 -- -- -- -- -- -- -- -- -- -- -- -- -- 18 18 28 -- -- Unit tcyc ns ns ns ns ns ns tcyc ns ns ns ns ns ns ns ns ns ns ns ns ns 22.74 22.75 22.76 22.77 22.73 22.72 22.71 22.70 Figure 22.69
Note: * The user must ensure that the code satisfies this condition.
Rev. 2.00 Mar 09, 2006 page 875 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
TX-CLK tTENd TX-EN tETDd ETXD[3:0] Preamble SFD DATA CRC
TX-ER tCRSs CRS tCRSh
COL
Figure 22.69 MII Send Timing (Normal Operation)
TX-CLK
TX-EN
ETXD[3:0]
Preamble
JAM
TX-ER
CRS tCOLs COL tCOLh
Figure 22.70 MII Send Timing (Case of Conflict)
RX-CLK tRDVs RX-DV tERDh tERDs ERXD[3:0] Preamble SFD DATA CRC tRDVh
RX-ER
Figure 22.71 MII Receive Timing (Normal Operation)
Rev. 2.00 Mar 09, 2006 page 876 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
RX-CLK
RX-DV Preamble SFD DATA tRERs RX-ER tRERh XXXX
ERXD[3:0]
Figure 22.72 MII Receive Timing (Case of Error)
MDC tMDIOs MDIO tMDIOh
Figure 22.73 MDIO Input Timing
MDC tMDIOdh MDIO
Figure 22.74 MDIO Output Timing
RX-CLK tWOLd WOL
Figure 22.75 WOL Output Timing
CKIO tEXOUTd EXOUT
Figure 22.76 EXOUT Output Timing
Rev. 2.00 Mar 09, 2006 page 877 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
RX-CLK
RX-DV SFD Dest Address tCAMS CAMSEN Source Address tCAMh DATA
ERXD[3:0]
Preamble
Figure 22.77 CAMSEN Input Timing 22.3.12 STATS, BH and BUSHiZ Signal Timing BH,
Table 22.17 STATS, BH and BUSHiZ Signal Timing BH, Conditions: VCC = PLLVCC = 3.3 V 0.3 V, PVCC = 5.0 V 0.5 V/3.3 V 0.3 V, PVCC VCC, VSS = PVSS = PLLVSS = 0 V, Ta = -20 to +75C
Item STAS1 and STAS0 output delay time BH output rising edge delay time BH output falling edge delay time BUSHiZ setup time BUSHiZ hold time Output delay time of target pins Symbol tSTATd tBHNrd tBHNfd tBHIZs tBHIZh tBHIZd Min -- -- -- 7 8 -- Typ -- -- -- -- -- -- Max 16 16 16 -- -- 16 Unit ns ns ns ns ns ns 22.79 Figure 22.77 22.78
CKI0
Address
CPU
CPU
E-DMAC E-DMAC E-DMAC
E-DMAC G-DMAC
G-DMAC G-DMAC G-DMAC
CSn tSTATd STATS1, 0
Figure 22.78 STATS Output Timing
Rev. 2.00 Mar 09, 2006 page 878 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
CKI0 Read0 Address CPU G-DMAC tBHNfd BH Read1 Read2 Read3 Write0 Write1 Write2 Write3 CPU
G-DMAC G-DMAC G-DMAC tBHNrd
G-DMAC G-DMAC
G-DMAC G-DMAC
Figure 22.79 BH Output Timing
CKI0
WAIT tBHIZs BUSHiZ tBHIZd Target Pins tBHIZh
Figure 22.80 BUSHiZ Bus Timing
Rev. 2.00 Mar 09, 2006 page 879 of 906 REJ09B0292-0200
Section 22 Electrical Characteristics
22.4
AC Characteristic Test Conditions
The AC characteristic test conditions are as follows: * Input/output signal reference level: 1.5 V (Vcc = 3.3 to 3.6 V) * Input pulse level: Vss to 3.0 V (Vss to Vcc for RES, TRST, EXTAL, CKIO, MD0-MD4, and NMI) * Input rise/fall time: 1 ns The output load circuit is shown in figure 22.81.
IOL
SH7616 output pin CL V
DUT output VREF
IOH CL is the total value, including the capacitance of the test jig, etc. The capacitance of each pin is as follows: 30 pF: CKIO, A24-A0, D31-D0, BS, RD, CS4-CS0, DQMUU/WE3-DQMLL/WE0, CAS3-CAS0, RAS, CAS/OE, DACK1, DACK0 50 pF: All other pins IOL and IOH values are as shown in table 22.3, Permissible Output Currents.
Figure 22.81 Output Load Circuit
Rev. 2.00 Mar 09, 2006 page 880 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Appendix A On-Chip Peripheral Module Registers
A.1 Addresses
On-chip peripheral module register addresses and bit names are shown in the following table. 16bit registers and 32-bit registers are shown, respectively, in two and four lines of 8 bits.
Register Name SIRDR Bit Names Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Module SIOF
Address H'FFFFFC00 H'FFFFFC01 H'FFFFFC02 H'FFFFFC03 H'FFFFFC04 H'FFFFFC05 H'FFFFFC06 H'FFFFFC07 H'FFFFFC08 H'FFFFFC09 H'FFFFFC0A H'FFFFFC0B H'FFFFFC0C H'FFFFFC0D H'FFFFFC0E H'FFFFFC0F H'FFFFFC10 H'FFFFFC11 H'FFFFFC12 H'FFFFFC13 H'FFFFFC14 H'FFFFFC15 H'FFFFFC16 H'FFFFFC17 H'FFFFFC18 to H'FFFFFC1F
SITDR
SICTR
-- --
-- TM -- -- -- RFWM2 -- --
-- SE -- -- -- RFWM1 -- --
-- DL -- -- -- RFWM0 R4 T4
-- TIE -- TERR TRMD TFWM3 R3 T3
DMACE RIE -- RERR LM TFWM2 R2 T2
TCIE TE TCD TDRE RFRST TFWM1 R1 T1
RCIE RE RCD RDRF TFRST TFWM0 R0 T0
SISTR
-- --
SIFCR
-- RFWM3
SIFDR
-- --
SIRCDR
SITCDR
SIRDR1
SIO1
SITDR1
SICTR1
-- --
-- TM -- -- --
-- SE -- -- --
-- DL -- -- --
-- TIE -- TERR --
-- RIE -- RERR --
-- TE -- TDRE --
-- RE -- RDRF -- --
SISTR1
-- --
--
--
Rev. 2.00 Mar 09, 2006 page 881 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name SIRDR2 Bit Names Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Module SIO2
Address H'FFFFFC20 H'FFFFFC21 H'FFFFFC22 H'FFFFFC23 H'FFFFFC24 H'FFFFFC25 H'FFFFFC26 H'FFFFFC27 H'FFFFFC28 to H'FFFFFC3F H'FFFFFC40 H'FFFFFC41 H'FFFFFC42 to H'FFFFFC4F H'FFFFFC50 H'FFFFFC51 H'FFFFFC52 H'FFFFFC53 H'FFFFFC54 H'FFFFFC55 H'FFFFFC56 H'FFFFFC57 H'FFFFFC58 H'FFFFFC59 H'FFFFFC5A H'FFFFFC5B H'FFFFFC5C H'FFFFFC5D H'FFFFFC5E H'FFFFFC5F H'FFFFFC60 H'FFFFFC61 H'FFFFFC62 H'FFFFFC63 H'FFFFFC64 H'FFFFFC65
SITDR2
SICTR2
-- --
-- TM -- -- --
-- SE -- -- --
-- DE -- -- --
-- TIE -- TERR --
-- RIE -- RERR --
-- TE -- TDRE --
-- RE -- RDRF -- --
SISTR2
-- --
--
--
TSTR TSYR --
-- -- --
-- -- --
-- -- --
-- -- --
-- -- --
CST2 SYNC2 --
CST1 SYNC1 --
CST0 SYNC0 --
TPU
--
TCR0 TMDR0 TIOR0H TIOR0L TIER0 TSR0 TCNT0
CCLR2 -- IOB3 IOD3 -- --
CCLR1 -- IOB2 IOD2 -- --
CCLR0 BFB IOB1 IOD1 -- --
CKEG1 BFA IOB0 IOD0 TCIEV TCFV
CKEG0 MD3 IOA3 IOC3 TGIED TGFD
TPSC2 MD2 IOA2 IOC2 TGIEC TGFC
TPSC1 MD1 IOA1 IOC1 TGIEB TGFB
TPSC0 MD0 IOA0 IOC0 TGIEA TGFA
TPU
TGR0A
TGR0B
TGR0C
TGR0D
TCR1 TMDR1 TIOR1 -- TIER1 TSR1
-- -- IOB3 -- -- TCFD
CCLR1 -- IOB2 -- -- --
CCLR0 -- IOB1 -- TCIEU TCFU
CKEG1 -- IOB0 -- TCIEV TCFV
CKEG0 MD3 IOA3 -- -- --
TPSC2 MD2 IOA2 -- -- --
TPSC1 MD1 IOA1 -- TGIEB TGFB
TPSC0 MD0 IOA0 -- TGIEA TGFA
Rev. 2.00 Mar 09, 2006 page 882 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name TCNT1 Bit Names Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Module TPU
Address H'FFFFFC66 H'FFFFFC67 H'FFFFFC68 H'FFFFFC69 H'FFFFFC6A H'FFFFFC6B H'FFFFFC6C to H'FFFFFC6F H'FFFFFC70 H'FFFFFC71 H'FFFFFC72 H'FFFFFC73 H'FFFFFC74 H'FFFFFC75 H'FFFFFC76 H'FFFFFC77 H'FFFFFC78 H'FFFFFC79 H'FFFFFC7A H'FFFFFC7B H'FFFFFC7C to H'FFFFFC7F H'FFFFFC80 H'FFFFFC81 H'FFFFFC82 H'FFFFFC83 H'FFFFFC84 H'FFFFFC85 H'FFFFFC86 to H'FFFFFC87 H'FFFFFC88 H'FFFFFC89 H'FFFFFC8A H'FFFFFC8B
TGR1A
TGR1B
--
--
--
--
--
--
--
--
--
--
TCR2 TMDR2 TIOR2 -- TIER2 TSR2 TCNT2
-- -- IOB3 -- -- TCFD
CCLR1 -- IOB2 -- -- --
CCLR0 -- IOB1 -- TCIEU TCFU
CKEG1 -- IOB0 -- TCIEV TCFV
CKEG0 MD3 IOA3 -- -- --
TPSC2 MD2 IOA2 -- -- --
TPSC1 MD1 IOA1 -- TGIEB TGFB
TPSC0 MD0 IOA0 -- TGIEA TGFA
TPU
TGR2A
TGR2B
--
--
--
--
--
--
--
--
--
--
PACR
-- PA7MD
-- PA6MD -- PA6IOR -- PA6DR --
PA13MD PA12MD PA11MD PA10MD PA9MD PA5MD PA4MD PA3MD PA2MD PA1MD
PA8MD PA0MD PA8IOR PA0IOR PA8DR PA0DR --
PFC
PAIOR
-- PA7IOR
PA13IOR PA12IOR PA11IOR PA10IOR PA9IOR PA5IOR PA4IOR -- PA2IOR PA1IOR
PADR
-- PA7DR
PA13DR PA12DR PA11DR PA5DR -- PA4DR -- -- --
PA10DR PA9DR PA2DR -- PA1DR --
I/O port
--
--
--
PBCR
PB15MD PB15MD PB14MD PB14MD PB13MD PB13MD PB12MD PB12MD PFC 1 0 1 0 1 0 1 0 PB11MD PB11MD PB10MD PB10MD PB9MD1 PB9MD0 PB8MD1 PB8MD0 1 0 1 0
PBIOR
PB15IOR PB14IOR PB13IOR PB12IOR PB11IOR PB10IOR PB9IOR PB7IOR PB6IOR PB5IOR PB4IOR PB3IOR PB2IOR PB1IOR
PB8IOR PB0IOR
Rev. 2.00 Mar 09, 2006 page 883 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name PBDR Bit Names Bit 7 PB15DR PB7DR PBCR2 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 PB8DR PB0DR Module I/O port
Address H'FFFFFC8C H'FFFFFC8D H'FFFFFC8E H'FFFFFC8F H'FFFFFC90 to H'FFFFFCAF
PB14DR PB13DR PB12DR PB11DR PB6DR PB5DR PB4DR PB3DR
PB10DR PB9DR PB2DR PB1DR
PB7MD1 PB7MD0 PB6MD1 PB6MD0 PB5MD1 PB5MD0 PB4MD1 PB4MD0 PFC PB3MD1 PB3MD0 PB2MD1 PB2MD0 PB1MD1 PB1MD0 PB0MD1 PB0MD0
--
--
--
--
--
--
--
--
--
--
H'FFFFF CB0 SDIR H'FFFFF CB1 H'FFFFF CB2 SDSR H'FFFFF CB3 H'FFFFF CB4 SDDRH H'FFFFF CB5 H'FFFFF CB6 SDDRL H'FFFFF CB7 H'FFFFF CB8 -- to H'FFFFF CBF H'FFFF FCC0 SCBRR1 H'FFFF FCC1 -- H'FFFF FCC2 SCBRR1 H'FFFF FCC3 -- H'FFFF FCC4 SCSCR1 H'FFFF FCC5 -- H'FFFF FCC6 SCFTDR1 H'FFFF FCC7 --
TS3 -- -- --
TS2 -- -- --
TS1 -- -- --
TS0 -- -- --
-- -- -- --
-- -- -- --
-- -- -- --
-- -- -- SDTRF
H-UDI
--
--
--
--
--
--
--
--
--
C/A --
CHR/ICK PE/ICK1 3 -- --
O/E/ICK1 STOP/ ICK0 -- --
MP --
CKS1 --
CKS0 --
SCIF1
-- TIE --
-- RIE --
-- TE --
-- RE --
-- MPIE --
-- -- --
-- CKE1 --
-- CKE0 --
--
-- PER2 TEND RLM --
-- PER1 TDFE N1 --
-- PER0 BRK N0 --
-- FER3 FER MPB --
-- FER2 PER MPBT --
-- FER1 RDF EI --
-- FER0 DR ORER --
H'FFFF FCC8 SC1SSR1 PER3 H'FFFF FCC9 ER
H'FFFF FCCA SC2SSR1 TLM H'FFFF FCCB -- H'FFFF FCCC SCFRDR1 H'FFFF FCCD -- H'FFFF FCCE SCFCR1 H'FFFF FCCF -- H'FFFF FCD0 SCFDR1 H'FFFF FCD1 -- RTRG1 -- -- -- --
-- RTRG0 -- -- --
-- TTRG1 -- -- --
-- TTRG0 -- T4 R4
-- MCE -- T3 R3
-- TFRST -- T2 R2
-- RFRST -- T1 R1
-- LOOP -- T0 R0
Rev. 2.00 Mar 09, 2006 page 884 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name Bit Names Bit 7 ED15 ED7 IRMOD -- Bit 6 ED14 ED6 PSEL -- Bit 5 ED13 ED5 RIVS -- Bit 4 ED12 ED4 -- -- Bit 3 ED11 ED3 -- -- Bit 2 ED10 ED2 -- -- Bit 1 ED9 ED1 -- -- Bit 0 ED8 ED0 -- -- -- Module SCIF1
Address
H'FFFF FCD2 SCFER1 H'FFFF FCD3 H'FFFF FCD4 SCIMR1 H'FFFF FCD5 -- to H'FFFF FCDF H'FFFF FCE0 SCSMR2 H'FFFF FCE1 -- H'FFFF FCE2 SCBRR2 H'FFFF FCE3 -- H'FFFF FCE4 SCSCR2 H'FFFF FCE5 -- H'FFFF FCE6 SCFTDR2 H'FFFF FCE7 --
C/A --
CHR/ICK PE/ICK2 3 -- --
O/E/ICK1 STOP/ ICK0 -- --
MP --
CKS1 --
CKS0 --
SCIF2
-- TIE --
-- RIE --
-- TE --
-- RE --
-- MPIE --
-- -- --
-- CKE1 --
-- CKE0 --
--
-- PER2 TEND RLM --
-- PER1 TDFE N1 --
-- PER0 BRK N0 --
-- FER3 FER MPB --
-- FER2 PER MPBT --
-- FER1 RDF EI --
-- FER0 DR ORER --
H'FFFF FCE8 SC1SSR2 PER3 H'FFFF FCE9 ER
H'FFFF FCEA SC2SSR2 TLM H'FFFF FCEB -- H'FFFF FCEC SCFRDR2 H'FFFF FCED -- H'FFFF FCEE SCFCR2 H'FFFF FCEF -- H'FFFF FCF0 SCFDR2 H'FFFF FCF1 H'FFFF FCF2 SCFER2 H'FFFF FCF3 H'FFFF FCF4 SCIMR2 H'FFFF FCF5 -- to H'FFFF FCFF -- RTRG1 -- -- -- ED15 ED7 IRMOD -- --
-- RTRG0 -- -- -- ED14 ED6 PSEL --
-- TTRG1 -- -- -- ED13 ED5 RIVS --
-- TTRG0 -- T4 R4 ED12 ED4 -- --
-- MCE -- T3 R3 ED11 ED3 -- --
-- TFRST -- T2 R2 ED10 ED2 -- --
-- RFRST -- T1 R1 ED9 ED1 -- --
-- LOOP -- T0 R0 ED8 ED0 -- -- --
Rev. 2.00 Mar 09, 2006 page 885 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name EDMR Bit Names Bit 7 -- -- -- -- EDTRR -- -- -- -- EDRRR -- -- -- -- TDLA31 TDLA23 TDLA15 TDLA7 RDLAR RDLA31 RDLA23 RDLA15 RDLA7 EESR -- -- -- RMAF EESIPR -- -- -- RMAFIP -- -- -- Bit 6 -- -- -- -- -- -- -- -- -- -- -- -- TDLA30 TDLA22 TDLA14 TDLA6 RDLA30 RDLA22 RDLA14 RDLA6 -- ECI -- -- -- ECIIP -- -- -- -- -- Bit 5 -- -- -- DL1 -- -- -- -- -- -- -- -- TDLA29 TDLA21 TDLA13 TDLA5 RDLA29 RDLA21 RDLA13 RDLA5 -- TC -- RFAR -- TCIP -- RFARIP -- -- -- Bit 4 -- -- -- DL0 -- -- -- -- -- -- -- -- TDLA28 TDLA20 TDLA12 TDLA4 RDLA28 RDLA20 RDLA12 RDLA4 -- TDE ITF RRF -- TDEIP ITFIP RRFIP -- -- ITFCE Bit 3 -- -- -- -- -- -- -- -- -- -- -- -- TDLA27 TDLA19 TDLA11 TDLA3 RDLA27 RDLA19 RDLA11 RDLA3 -- TFUF CND RTLF -- TFUFIP CNDIP RTLFIP -- -- CNDCE Bit 2 -- -- -- -- -- -- -- -- -- -- -- -- TDLA26 TDLA18 TDLA10 TDLA2 RDLA26 RDLA18 RDLA10 RDLA2 -- FR DLC RTSF -- FRIP DLCIP RTSFIP -- -- DLCCE Bit 1 -- -- -- -- -- -- -- -- -- -- -- -- TDLA25 TDLA17 TDLA9 TDLA1 RDLA25 RDLA17 RDLA9 RDLA1 -- RDE CD PRE -- RDEIP CDIP PREIP -- -- CDCE Bit 0 -- -- -- SWR -- -- -- TR -- -- -- RR TDLA24 TDLA16 TDLA8 TDLA0 RDLA24 RDLA16 RDLA8 RDLA0 RFCOF RFOF TRO CERF RFCOFIP RFOFIP TROIP CERFIP -- -- TROCE CERFCE Module E-DMAC
Address H'FFFF FD00 H'FFFF FD01 H'FFFF FD02 H'FFFF FD03 H'FFFF FD04 H'FFFF FD05 H'FFFF FD06 H'FFFF FD07 H'FFFF FD08 H'FFFF FD09 H'FFFF FD0A H'FFFF FD0B
H'FFFF FD0C TDLAR H'FFFF FD0D H'FFFF FD0E H'FFFF FD0F H'FFFF FD10 H'FFFF FD11 H'FFFF FD12 H'FFFF FD13 H'FFFF FD14 H'FFFF FD15 H'FFFF FD16 H'FFFF FD17 H'FFFF FD18 H'FFFF FD19 H'FFFF FD1A H'FFFF FD1B H'FFFF FD1C TRSCER H'FFFF FD1D H'FFFF FD1E H'FFFF FD1F
RMAFCE --
RFARCE RRFCE
RTLFCE RTSFCE PRECE
Rev. 2.00 Mar 09, 2006 page 886 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name RMFCR Bit Names Bit 7 -- -- MFC15 MFC7 TFTR -- -- -- TFT7 FDR -- -- -- -- -- -- -- -- EDOCR -- -- -- -- -- Bit 6 -- -- MFC14 MFC6 -- -- -- TFT6 -- -- -- -- -- -- -- -- -- -- -- -- -- Bit 5 -- -- MFC13 MFC5 -- -- -- TFT5 -- -- -- -- -- -- -- -- -- -- -- -- -- Bit 4 -- -- MFC12 MFC4 -- -- -- TFT4 -- -- -- -- -- -- -- -- -- -- -- -- -- Bit 3 -- -- MFC11 MFC3 -- -- -- TFT3 -- -- -- -- -- -- -- -- -- -- -- FEC -- Bit 2 -- -- MFC10 MFC2 -- -- TFT10 TFT2 -- -- TFD2 RFD2 -- -- -- -- -- -- -- AEC -- Bit 1 -- -- MFC9 MFC1 -- -- TFT9 TFT1 -- -- TFD1 RFD1 -- -- -- -- -- -- -- EDH -- Bit 0 -- -- MFC8 MFC0 -- -- TFT8 TFT0 -- -- TFD0 RFD0 -- -- -- RNC -- -- -- -- -- Module E-DMAC
Address H'FFFF FD20 H'FFFF FD21 H'FFFF FD22 H'FFFF FD23 H'FFFF FD24 H'FFFF FD25 H'FFFF FD26 H'FFFF FD27 H'FFFF FD28 H'FFFF FD29 H'FFFF FD2A H'FFFF FD2B
H'FFFF FD2C RCR H'FFFF FD2D H'FFFF FD2E H'FFFF FD2F H'FFFF FD30 H'FFFF FD31 H'FFFF FD32 H'FFFF FD33 H'FFFF FD34 -- to H'FFFF FD3F H'FFFF FD40 H'FFFF FD41 H'FFFF FD42 H'FFFF FD43 H'FFFF FD44 H'FFFF FD45 H'FFFF FD46 H'FFFF FD47 RDFAR RBWAR
RBWA31 RBWA30 RBWA29 RBWA28 RBWA27 RBWA26 RBWA25 RBWA23 RBWA22 RBWA21 RBWA20 RBWA19 RBWA18 RBWA17 RBWA15 RBWA14 RBWA13 RBWA12 RBWA11 RBWA10 RBWA9 RBWA7 RDFA31 RDFA23 RDFA15 RDFA7 RBWA6 RDFA30 RDFA22 RDFA14 RDFA6 RBWA5 RDFA29 RDFA21 RDFA13 RDFA5 RBWA4 RDFA28 RDFA20 RDFA12 RDFA4 RBWA3 RDFA27 RDFA19 RDFA11 RDFA3 RBWA2 RDFA26 RDFA18 RDFA10 RDFA2 RBWA1 RDFA25 RDFA17 RDFA9 RDFA1
RBWA24 RBWA16 RBWA8 RBWA0 RDFA24 RDFA16 RDFA8 RDFA0
Rev. 2.00 Mar 09, 2006 page 887 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name Bit Names Bit 7 -- Bit 6 -- Bit 5 -- Bit 4 -- Bit 3 -- Bit 2 -- Bit 1 -- Bit 0 -- Module E-DMAC
Address
H'FFFF FD48 -- to H'FFFF FD4B H'FFFF FD4C TBRAR H'FFFF FD4D H'FFFF FD4E H'FFFF FD4F H'FFFF FD50 H'FFFF FD51 H'FFFF FD52 H'FFFF FD53 H'FFFF FD54 -- to H'FFFF FD5F H'FFFF FD60 H'FFFF FD61 H'FFFF FD62 H'FFFF FD63 H'FFFF FD64 H'FFFF FD65 H'FFFF FD66 H'FFFF FD67 H'FFFF FD68 H'FFFF FD69 H'FFFF FD6A H'FFFF FD6B H'FFFF FD6C PIR H'FFFF FD6D H'FFFF FD6E H'FFFF FD6F H'FFFF FD70 H'FFFF FD71 H'FFFF FD72 H'FFFF FD73 MAHR ECSIPR ECSR ECMR TDFAR
TBRA31 TBRA23 TBRA15 TBRA7 TDFA31 TDFA23 TDFA15 TDFA7 --
TBRA30 TBRA22 TBRA14 TBRA6 TDFA30 TDFA22 TDFA14 TDFA6 --
TBRA29 TBRA21 TBRA13 TBRA5 TDFA29 TDFA21 TDFA13 TDFA5 --
TBRA28 TBRA20 TBRA12 TBRA4 TDFA28 TDFA20 TDFA12 TDFA4 --
TBRA27 TBRA19 TBRA11 TBRA3 TDFA27 TDFA19 TDFA11 TDFA3 --
TBRA26 TBRA18 TBRA10 TBRA2 TDFA26 TDFA18 TDFA10 TDFA2 --
TBRA25 TBRA17 TBRA9 TBRA1 TDFA25 TDFA17 TDFA9 TDFA1 --
TBRA24 TBRA16 TBRA8 TBRA0 TDFA24 TDFA16 TDFA8 TDFA0 --
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- MA47 MA39 MA31 MA23
-- -- -- RE -- -- -- -- -- -- -- -- -- -- -- -- MA46 MA38 MA30 MA22
-- -- -- TE -- -- -- -- -- -- -- -- -- -- -- -- MA45 MA37 MA29 MA21
-- -- PRCEF -- -- -- -- -- -- -- -- -- -- -- -- -- MA44 MA36 MA28 MA20
-- -- -- ILB -- -- -- -- -- -- -- -- -- -- -- MDI MA43 MA35 MA27 MA19
-- -- -- ELB -- -- -- LCHNG -- -- --
-- -- MPDE DM -- -- -- MPD -- -- --
-- -- -- PRM -- -- -- ICD -- -- -- ICDIP -- -- -- MMC MA40 MA32 MA24 MA16
EtherC
LCHNGIP MPDIP -- -- -- MDO MA42 MA34 MA26 MA18 -- -- -- MMD MA41 MA33 MA25 MA17
Rev. 2.00 Mar 09, 2006 page 888 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name MALR Bit Names Bit 7 -- -- MA15 MA7 RFLR -- -- -- RFL7 -- -- -- -- TROCR -- -- TROC15 TROC7 CDCR -- -- Bit 6 -- -- MA14 MA6 -- -- -- RFL6 -- -- -- -- -- -- Bit 5 -- -- MA13 MA5 -- -- -- RFL5 -- -- -- -- -- -- Bit 4 -- -- MA12 MA4 -- -- -- RFL4 -- -- -- -- -- -- TROC12 TROC4 -- -- Bit 3 -- -- MA11 MA3 -- -- RFL11 RFL3 -- -- -- -- -- -- TROC11 TROC3 -- -- Bit 2 -- -- MA10 MA2 -- -- RFL10 RFL2 -- -- -- -- -- -- TROC10 TROC2 -- -- Bit 1 -- -- MA9 MA1 -- -- RFL9 RFL1 -- -- -- -- -- -- TROC9 TROC1 -- -- Bit 0 -- -- MA8 MA0 -- -- RFL8 RFL0 -- -- -- LMON -- -- TROC8 TROC0 -- -- Module EtherC
Address H'FFFF FD74 H'FFFF FD75 H'FFFF FD76 H'FFFF FD77 H'FFFF FD78 H'FFFF FD79 H'FFFF FD7A H'FFFF FD7B
H'FFFF FD7C PSR H'FFFF FD7D H'FFFF FD7E H'FFFF FD7F H'FFFF FD80 H'FFFF FD81 H'FFFF FD82 H'FFFF FD83 H'FFFF FD84 H'FFFF FD85 H'FFFF FD86 H'FFFF FD87 H'FFFF FD88 H'FFFF FD89 H'FFFF FD8A H'FFFF FD8B H'FFFF FD8C CNDCR H'FFFF FD8D H'FFFF FD8E H'FFFF FD8F H'FFFF FD90 H'FFFF FD91 H'FFFF FD92 H'FFFF FD93 IFLCR LCCR
TROC14 TROC13 TROC6 -- -- TROC5 -- --
COLDC15 COLDC14 COLDC13 COLDC12 COLDC11 COLDC10 COLDC9 COLDC8 COLDC7 -- -- LCC15 LCC7 -- -- CNDC15 CNDC7 -- -- IFLC15 IFLC7 COLDC6 COLDC5 COLDC4 COLDC3 COLDC2 COLDC1 COLDC0 -- -- LCC14 LCC6 -- -- -- -- LCC13 LCC5 -- -- -- -- LCC12 LCC4 -- -- -- -- LCC11 LCC3 -- -- -- -- LCC10 LCC2 -- -- -- -- LCC9 LCC1 -- -- -- -- LCC8 LCC0 -- -- CNDC8 CNDC0 -- -- IFLC8 IFLC0
CNDC14 CNDC13 CNDC12 CNDC11 CNDC10 CNDC9 CNDC6 -- -- IFLC14 IFLC6 CNDC5 -- -- IFLC13 IFLC5 CNDC4 -- -- IFLC12 IFLC4 CNDC3 -- -- IFLC11 IFLC3 CNDC2 -- -- IFLC10 IFLC2 CNDC1 -- -- IFLC9 IFLC1
Rev. 2.00 Mar 09, 2006 page 889 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name Bit 7 CEFCR -- -- CEFC15 CEFC7 FRECR -- -- FREC15 FREC7 Bit Names Bit 6 -- -- CEFC14 CEFC6 -- -- FREC14 FREC6 -- -- TSFC14 TSFC6 -- -- TLFC14 TLFC6 -- -- RFC14 RFC6 -- -- Bit 5 -- -- CEFC13 CEFC5 -- -- FREC13 FREC5 -- -- TSFC13 TSFC5 -- -- TLFC13 TLFC5 -- -- RFC13 RFC5 -- -- Bit 4 -- -- CEFC12 CEFC4 -- -- FREC12 FREC4 -- -- TSFC12 TSFC4 -- -- TLFC12 TLFC4 -- -- RFC12 RFC4 -- -- Bit 3 -- -- CEFC11 CEFC3 -- -- FREC11 FREC3 -- -- TSFC11 TSFC3 -- -- TLFC11 TLFC3 -- -- RFC11 RFC3 -- -- Bit 2 -- -- CEFC10 CEFC2 -- -- FREC10 FREC2 -- -- TSFC10 TSFC2 -- -- TLFC10 TLFC2 -- -- RFC10 RFC2 -- -- Bit 1 -- -- CEFC9 CEFC1 -- -- FREC9 FREC1 -- -- TSFC9 TSFC1 -- -- TLFC9 TLFC1 -- -- RFC9 RFC1 -- -- Bit 0 -- -- CEFC8 CEFC0 -- -- FREC8 FREC0 -- -- TSFC8 TSFC0 -- -- TLFC8 TLFC0 -- -- RFC8 RFC0 -- -- MAFC8 MAFC0 -- -- Module EtherC
Address H'FFFF FD94 H'FFFF FD95 H'FFFF FD96 H'FFFF FD97 H'FFFF FD98 H'FFFF FD99 H'FFFF FD9A H'FFFF FD9B
H'FFFF FD9C TSFRCR -- H'FFFF FD9D H'FFFF FD9E H'FFFF FD9F -- TSFC15 TSFC7
H'FFFF FDA0 TLFRCR -- H'FFFF FDA1 H'FFFF FDA2 H'FFFF FDA3 H'FFFF FDA4 RFCR H'FFFF FDA5 H'FFFF FDA6 H'FFFF FDA7 H'FFFF FDA8 MAFCR H'FFFF FDA9 H'FFFF FDAA H'FFFF FDAB H'FFFF FDAC -- to H'FFFF FDB3 H'FFFF FDB4 SCDCR H'FFFF FDB5 H'FFFF FDB6 H'FFFF FDB7 -- TLFC15 TLFC7 -- -- RFC15 RFC7 -- --
MAFC15 MAFC14 MAFC13 MAFC12 MAFC11 MAFC7 -- MAFC6 -- MAFC5 -- MAFC4 -- MAFC3 --
MAFC10 MAFC9 MAFC2 -- MAFC1 --
COSDC 31 COSDC 23 COSDC 15
COSDC 30 COSDC 22 COSDC 14
COSDC 29 COSDC 21 COSDC 13
COSDC 28 COSDC 20 COSDC 12
COSDC 27 COSDC 19 COSDC 11
COSDC 26 COSDC 18 COSDC 10
COSDC 25 COSDC 17
COSDC 24 COSDC 16
EtherC
COSDC9 COSDC8
COSDC7 COSDC6 COSDC5 COSDC4 COSDC3 COSDC2 COSDC1 COSDC0
Rev. 2.00 Mar 09, 2006 page 890 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name Bit Names Bit 7 -- Bit 6 -- Bit 5 -- Bit 4 -- Bit 3 -- Bit 2 -- Bit 1 -- Bit 0 -- Module --
Address
H'FFFF FDB8 -- to H'FFFF FE0F H'FFFFFE10 H'FFFFFE11 H'FFFFFE12 H'FFFFFE13 H'FFFFFE14 TIER FTCSR FRC H FRC L OCRA H OCRB H H'FFFFFE15 OCRA L OCRB L H'FFFFFE16 H'FFFFFE17 H'FFFFFE18 H'FFFFFE19 H'FFFFFE1A to H'FFFFFE3F H'FFFFFE40 H'FFFFFE41 H'FFFFFE42 H'FFFFFE43 H'FFFFFE44 H'FFFFFE45 H'FFFFFE46 H'FFFFFE47 H'FFFFFE48 H'FFFFFE49 H'FFFFFE4A H'FFFFFE4B H'FFFFFE4C H'FFFFFE4D H'FFFFFE4E H'FFFFFE4F H'FFFFFE50 H'FFFFFE51 H'FFFFFE52 H'FFFFFE53 VCRM VCRL VCRK VCRJ VCRI VCRH VCRG VCRF VCRE TCR TOCR FICR H FICR L --
ICIE ICF
-- --
-- --
-- --
OCIAE OCFA
OCIBE OCFB
OVIE OVF
-- CCLRA
FRT
IEDG --
-- --
-- --
-- OCRS
-- --
-- --
CKS1 OLVLA
CKS0 OLVLB
--
--
--
--
--
--
--
--
--
IPRD
TPU0IP3 TPU0IP2 TPU0IP1 TPU0IP0 TPU1IP3 TPU1IP2 TPU1IP1 TPU1IP0 INTC TPU2IP3 TPU2IP2 TPU2IP1 TPU2IP0 SCF1IP3 SCF1IP2 SCF1IP1 SCF1IP0 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- TG0AV6 TG0BV6 TG0AV5 TG0BV5 TG0AV4 TG0BV4 TG0AV3 TG0BV3 TG0AV2 TG0BV2 TG0AV1 TG0BV1 TG0AV0 TG0BV0
TG0CV6 TG0CV5 TG0CV4 TG0CV3 TG0CV2 TG0CV1 TG0CV0 TG0DV6 TG0DV5 TG0DV4 TG0DV3 TG0DV2 TG0DV1 TG0DV0 TC0VV6 -- TG1AV6 TG1BV6 TC1VV6 TC1UV6 TG2AV6 TG2BV6 TC2VV6 TC2UV6 SER1V6 SRX1V6 SBR1V6 STX1V6 TC0VV5 -- TG1AV5 TG1BV5 TC1VV5 TC1UV5 TG2AV5 TG2BV5 TC2VV5 TC0VV4 -- TG1AV4 TG1BV4 TC1VV4 TC1UV4 TG2AV4 TG2BV4 TC2VV4 TC0VV3 -- TG1AV3 TG1BV3 TC1VV3 TC1UV3 TG2AV3 TG2BV3 TC2VV3 TC2UV3 SER1V3 SRX1V3 SBR1V3 STX1V3 TC0VV2 -- TG1AV2 TG1BV2 TC1VV2 TC1UV2 TG2AV2 TG2BV2 TC2VV2 TC2UV2 SER1V2 SRX1V2 SBR1V2 STX1V2 TC0VV1 -- TG1AV1 TG1BV1 TC1VV1 TC1UV1 TG2AV1 TG2BV1 TC2VV1 TC2UV1 SER1V1 SRX1V1 SBR1V1 STX1V1 TC0VV0 -- TG1AV0 TG1BV0 TC1VV0 TC1UV0 TG2AV0 TG2BV0 TC2VV0 TC2UV0 SER1V0 SER1V0 SBR1V0 STX1V0
TC2UV 5 TC2UV4 SER1V5 SRX1V5 SBR1V5 STX1V5 SER1V4 SRX1V4 SBR1V4 STX1V4
Rev. 2.00 Mar 09, 2006 page 891 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name VCRN Bit Names Bit 7 -- -- VCRO -- -- -- -- Bit 6 SER2V6 SRX2V6 SBR2V6 STX2V6 -- Bit 5 SER2V5 SRX2V5 SBR2V5 STX2V5 -- Bit 4 SER2V4 SRX2V4 SBR2V4 STX2V4 -- Bit 3 SER2V3 SRX2V3 SBR2V3 STX2V3 -- Bit 2 SER2V2 SRX2V2 SBR2V2 STX2V2 -- Bit 1 SER2V1 SRX2V1 SBR2V1 STX2V1 -- Bit 0 SER2V0 SRX2V0 SBR2V0 STX2V0 -- -- Module INTC
Address H'FFFFFE54 H'FFFFFE55 H'FFFFFE56 H'FFFFFE57 H'FFFFFE58 to H'FFFFFE5F H'FFFFFE60 H'FFFFFE61 H'FFFFFE62 H'FFFFFE63 H'FFFFFE64 H'FFFFFE65 H'FFFFFE66 H'FFFFFE67 H'FFFFFE68 H'FFFFFE69 H'FFFFFE6A to H'FFFFFE70 H'FFFFFE71 H'FFFFFE72 H'FFFFFE73 to H'FFFFFE7F H'FFFFFE80 H'FFFFFE81 H'FFFFFE82 H'FFFFFE83 H'FFFFFE84 to H'FFFFFE8F H'FFFFFE90
IPRB
EEEEFRTIP3 DMACIP3 DMACIP2 DMACIP1 DMACIP0 -- -- EINV6 -- -- -- FICV6 FOCV6 FOVV6 -- -- -- EINV5 -- -- -- FICV5 FOCV5 FOVV5 -- -- -- EINV4 -- -- -- FICV4 FOCV4 FOVV4 -- -- -- EINV3 -- -- -- FICV3 FOCV3 FOVV3 -- --
FRTIP2 -- EINV2 -- -- -- FICV2 FOCV2 FOVV2 -- --
FRTIP1 -- EINV1 -- -- -- FICV1 FOCV1 FOVV1 -- --
FRTIP0 -- EINV0 -- -- -- FICV0 FOCV0 FOVV0 -- --
INTC
VCRA
-- --
VCRB
-- --
VCRC
-- --
VCRD
-- --
--
--
--
DRCR0 DRCR1 --
-- -- --
-- -- --
-- -- --
RS4 RS4 --
RS3 RS3 --
RS2 RS2 --
RS1 RS1 --
RS0 RS0 --
DMAC
--
WTCSR WTCNT -- RSTCSR --
OVF
WT/IT
TME
--
--
CKS2
CKS1
CKS0
WDT
-- WOVF --
-- RSTE --
-- RSTS --
-- -- --
-- -- --
-- -- --
-- -- --
-- -- -- --
FMR
PLL2ST
PLL1ST
CKIOST
--
FR3
FR2
FR1
FR0
On-chip oscillation circuit Powerdown state CACHE Powerdown state
H'FFFFFE91 H'FFFFFE92 H'FFFFFE93
SBYCR1 CCR SBYCR2
SBY W1 --
HIZ W0 --
MSTP5 WB
MSTP4 CP
MSTP3 TW
-- OD MSTP8
MSTP1 ID MSTP7
-- CE MSTP6
MSTP11 MSTP10 MSTP9
Rev. 2.00 Mar 09, 2006 page 892 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name -- Bit Names Bit 7 -- Bit 6 -- Bit 5 -- Bit 4 -- Bit 3 -- Bit 2 -- Bit 1 -- Bit 0 -- Module --
Address H'FFFFFE94 to H'FFFFFEBF H'FFFFFEC0 H'FFFFFEC1 H'FFFFFEC2 H'FFFFFEC3 H'FFFFFEC4 H'FFFFFEC5 H'FFFFFEC6 H'FFFFFEC7 H'FFFFFEC8 H'FFFFFEC9 H'FFFFFECA H'FFFFFECB H'FFFFFECC H'FFFFFECD H'FFFFFECE to H'FFFFFEDF H'FFFFFEE0 H'FFFFFEE1 H'FFFFFEE2 H'FFFFFEE3 H'FFFFFEE4 H'FFFFFEE5 H'FFFFFEE6 H'FFFFFEE7 H'FFFFFEE8 H'FFFFFEE9 H'FFFFFEEA to H'FFFFFEFF H'FFFF FF00 H'FFFF FF01 H'FFFF FF02 H'FFFF FF03
IPRE
SCF2IP3 SCF2IP2 SCF2IP1 SCF2IP0 SIOFIP3 SIO1IP3 SIO1P2 SIO2P1 SIO1IP0 SIO2IP3
SIOFIP2 SIO2IP2
SIOFIP1 SIO2IP1
SIOFIP0 SIO2IP0
INTC
VCRP
-- --
RER0V6 RER0V5 RER0V4 RER0V3 RER0V2 RER0V1 RER0V0 TER0V6 RDF0V6 TDE0V6 TER0V5 RDF0V5 TDE0V5 TER0V4 RDF0V4 TDE0V4 TER0V3 RDF0V3 TDE0V3 TER0V2 RDF0V2 TDE0V2 TER0V1 RDF0V1 TDE0V1 TER0V0 RDF0V0 TDE0V0
VCRQ
-- --
VCRR
-- --
RER1V6 RER1V5 RER1V4 RER1V3 RER1V2 RER1V1 RER1V0 TER1V6 RDF1V6 TDE1V6 TER1V5 RDF1V5 TDE1V5 TER1V4 RDF1V4 TDE1V4 TER1V3 RDF1V3 TDE1V3 TER1V2 RDF1V2 TDE1V2 TER1V1 RDF1V1 TDE1V1 TER1V0 RDF1V0 TDE1V0
VCRS
-- --
VCRT
-- --
RER2V6 RER2V5 RER2V4 RER2V3 RER2V2 RER2V1 RER2V0 TER2V6 RDF2V6 TDE2V6 -- TER2V5 RDF2V5 TDE2V5 -- TER2V4 RDF2V4 TDE2V4 -- TER2V3 RDF2V3 TDE2V3 -- TER2V2 RDF2V2 TDE2V2 -- TER2V1 RDF2V1 TDE2V1 -- TER2V0 RDF2V0 TDE2V0 -- --
VCRU
-- --
--
--
ICR
NMIL --
-- -- -- WDTIP2 WITV6 BCMV6 IRQ0IP2 IRQ2IP2 IRQ30S IRL2PS --
-- -- -- WDTIP1 WITV5 BCMV5 IRQ0IP1 IRQ2IP1 IRQ21S IRL1PS --
-- -- -- WDTIP0 WITV4 BCMV4 IRQ0IP0 IRQ2IP0 IRQ20S IRL0PS --
-- --
-- --
-- EXIMD
NMIE VECMD
INTC
IPRA
-- WDTIP3
DMACIP3 DMACIP2 DMACIP1 DMACIP0 -- WITV3 BCMV3 IRQ1IP3 IRQ3IP3 IRQ11S IRQ3F -- -- WITV2 BCMV2 IRQ1IP2 IRQ3IP2 IRQ10S IRQ2F -- -- WITV1 BCMV1 IRQ1IP1 IRQ3IP1 IRQ01S IRQ1F -- -- WITV0 BCMV0 IRQ1IP0 IRQ3IP0 IRQ00S IRQ0F -- --
VCRWDT
-- --
IPRC
IRQ0IP3 IRQ2IP3
IRQCSR
IRQ31S IRL3PS
--
--
BARAH
BAA31 BAA23
BAA30 BAA22 BAA14 BAA6
BAA29 BAA21 BAA13 BAA5
BAA28 BAA20 BAA12 BAA4
BAA27 BAA19 BAA11 BAA3
BAA26 BAA18 BAA10 BAA2
BAA25 BAA17 BAA9 BAA1
BAA24 BAA16 BAA8 BAA0
UBC
BARAL
BAA15 BAA7
Rev. 2.00 Mar 09, 2006 page 893 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name BAMRAH Bit Names Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Module
Address H'FFFF FF04 H'FFFF FF05 H'FFFF FF06 H'FFFF FF07 H'FFFF FF08 H'FFFF FF09 H'FFFF FF0A to H'FFFF FF0F H'FFFF FF10 H'FFFF FF11 H'FFFF FF12 to H'FFFF FF13 H'FFFF FF14 H'FFFF FF15 H'FFFF FF16 H'FFFF FF17 H'FFFF FF18 H'FFFF FF19 H'FFFF FF1A H'FFFF FF1B
BAMA31 BAMA30 BAMA29 BAMA28 BAMA27 BAMA26 BAMA25 BAMA24 UBC BAMA23 BAMA22 BAMA21 BAMA20 BAMA19 BAMA18 BAMA17 BAMA16
BAMRAL
BAMA15 BAMA14 BAMA13 BAMA12 BAMA11 BAMA10 BAMA9 BAMA7 BAMA6 -- CPA0 -- BAMA5 -- IDA1 -- BAMA4 -- IDA0 -- BAMA3 -- RWA1 -- BAMA2 -- RWA0 -- BAMA1 -- SZA1 --
BAMA8 BAMA0 -- SZA0 -- --
BBRA
-- CPA1
--
--
BRFR
SVF DVF
PID2 -- --
PID1 -- --
PID0 -- --
-- -- --
-- -- --
-- -- --
-- -- --
UBC
--
--
--
BRSRH
BSA31 BSA23
BSA30 BSA22 BSA14 BSA6 BDA30 BDA22 BDA14 BDA6 --
BSA29 BSA21 BSA13 BSA5 BDA29 BDA21 BDA13 BDA5 --
BSA28 BSA20 BSA12 BSA4 DA28 BDA20 BDA12 BDA4 --
BSA27 BSA19 BSA11 BSA3 BDA27 BDA19 BDA11 BDA3 --
BSA26 BSA18 BSA10 BSA2 BDA26 BDA18 BDA10 BDA2 --
BSA25 BSA17 BSA9 BSA1 BDA25 BDA17 BDA9 BDA1 --
BSA24 BSA16 BSA8 BSA0 BDA24 BDA16 BDA8 BDA0 --
UBC
BRSRL
BSA15 BSA7
BRDRH
BDA31 BDA23
BRDRL
BDA15 BDA7 --
H'FFFF FF1C -- to H'FFFF FF1F H'FFFF FF20 H'FFFF FF21 H'FFFF FF22 H'FFFF FF23 H'FFFF FF24 H'FFFF FF25 H'FFFF FF26 H'FFFF FF27 H'FFFF FF28 H'FFFF FF29 BBRB BAMRBL BAMRBH BARBL BARBH
--
BAB31 BAB23 BAB15 BAB7
BAB30 BAB22 BAB14 BAB6
BAB29 BAB21 BAB13 BAB5
BAB28 BAB20 BAB12 BAB4
BAB27 BAB19 BAB11 BAB3
BAB26 BAB18 BAB10 BAB2
BAB25 BAB17 BAB9 BAB1
BAB24 BAB16 BAB8 BAB0
UBC
BAMB31 BAMB30 BAMB29 BAMB28 BAMB27 BAMB26 BAMB25 BAMB24 BAMB23 BAMB22 BAMB21 BAMB20 BAMB19 BAMB18 BAMB17 BAMB16 BAMB15 BAMB14 BAMB13 BAMB12 BAMB11 BAMB10 BAMB9 BAMB7 -- CPB1 BAMB6 -- CPB0 BAMB5 -- IDB1 BAMB4 -- IDB0 BAMB3 -- RWB1 BAMB2 -- RWB0 BAMB1 -- SZB1 BAMB8 BAMB0 -- SZB0
Rev. 2.00 Mar 09, 2006 page 894 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name -- Bit Names Bit 7 -- Bit 6 -- Bit 5 -- Bit 4 -- Bit 3 -- Bit 2 -- Bit 1 -- Bit 0 -- Module --
Address H'FFFF FF2A to H'FFFF FF2F H'FFFF FF30 H'FFFF FF31 H'FFFF FF32 H'FFFF FF33 H'FFFF FF34 to H'FFFF FF3F H'FFFFFF40 H'FFFFFF41 H'FFFFFF42 H'FFFFFF43 H'FFFFFF44 H'FFFFFF45 H'FFFFFF46 H'FFFFFF47 H'FFFFFF48 H'FFFFFF49 H'FFFFFF4A to H'FFFFFF4F H'FFFF FF50 H'FFFF FF51 H'FFFF FF52 H'FFFF FF53 H'FFFF FF54 H'FFFF FF55 H'FFFF FF56 H'FFFF FF57 H'FFFF FF58 H'FFFF FF59 H'FFFF FF5A to H'FFFF FF5F
BRCRH
CMFCA CMFCB
CMFPA CMFPB CMFPC CMFPD --
-- -- ETBEC ETBED --
-- SEQ1 -- -- --
PCTE SEQ0 DBEC DBED --
PCBA PCBB PCBC PCBD --
-- -- -- -- --
-- -- -- -- --
UBC
BRCRL
CMFCC CMFCD
--
--
--
BARCH
BAC31 BAC23
BAC30 BAC22 BAC14 BAC6
BAC29 BAC21 BAC13 BAC5
BAC28 BAC20 BAC12 BAC4
BAC27 BAC19 BAC11 BAC3
BAC26 BAC18 BAC10 BAC2
BAC25 BAC17 BAC9 BAC1
BAC24 BAC16 BAC8 BAC0
UBC
BARCL
BAC15 BAC7
BAMRCH
BAMC31 BAMC30 BAMC29 BAMC28 BAMC27 BAMC26 BAMC25 BAMC24 BAMC23 BAMC22 BAMC21 BAMC20 BAMC19 BAMC18 BAMC17 BAMC16
BAMRCL
BAMC15 BAMC14 BAMC13 BAMC12 BAMC11 BAMC10 BAMC9 BAMC7 BAMC6 -- CPC0 -- BAMC5 -- IDC1 -- BAMC4 -- IDC0 -- BAMC3 -- RWC1 -- BAMC2 -- RWC0 -- BAMC1 -- SZC1 --
BAMC8 BAMC0 -- SZC0 -- --
BBRC
-- CPC1
--
--
BDRCH
BDC31 BDC23
BDC30 BDC22 BDC14 BDC6
BDC29 BDC21 BDC13 BDC5
BDC28 BDC20 BDC12 BDC4
BDC27 BDC19 BDC11 BDC3
BDC26 BDC18 BDC10 BDC2
BDC25 BDC17 BDC9 BDC1
BDC24 BDC16 BDC8 BDC0
UBC
BDRCL
BDC15 BDC7
BDMRCH
BDMC31 BDMC30 BDMC29 BDMC28 BDMC27 BDMC26 BDMC25 BDMC24 BDMC23 BDMC22 BDMC21 BDMC20 BDMC19 BDMC18 BDMC17 BDMC16
BDMRCL
BDMC15 BDMC14 BDMC13 BDMC12 BDMC11 BDMC10 BDMC9 BDMC7 BDMC6 -- ETRC6 -- BDMC5 -- ETRC5 -- BDMC4 -- ETRC4 -- BDMC3 ETRC11 ETRC3 -- BDMC2 ETRC10 ETRC2 -- BDMC1 ETRC9 ETRC1 --
BDMC8 BDMC0 ETRC8 ETRC0 -- --
BETRC
-- ETRC7
--
--
Rev. 2.00 Mar 09, 2006 page 895 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name Bit Names Bit 7 BAD31 BAD23 BAD15 BAD7 Bit 6 BAD30 BAD22 BAD14 BAD6 Bit 5 BAD29 BAD21 BAD13 BAD5 Bit 4 BAD28 BAD20 BAD12 BAD4 Bit 3 BAD27 BAD19 BAD11 BAD3 Bit 2 BAD26 BAD18 BAD10 BAD2 Bit 1 BAD25 BAD17 BAD9 BAD1 Bit 0 BAD24 BAD16 BAD8 BAD0 Module UBC
Address
H'FFFF FF60 BARDH H'FFFF FF61 H'FFFF FF62 BARDL H'FFFF FF63 H'FFFF FF64 BAMRDH H'FFFF FF65 H'FFFF FF66 BAMRDL H'FFFF FF67 H'FFFF FF68 BBRD H'FFFF FF69 H'FFFF FF6A -- to H'FFFF FF6F H'FFFF FF70 BDRDH H'FFFF FF71 H'FFFF FF72 BDRDL H'FFFF FF73 H'FFFF FF74 BDMRDH H'FFFF FF75 H'FFFF FF76 H'FFFF FF77 H'FFFF FF78 H'FFFF FF79 H'FFFF FF7A to H'FFFF FF7F H'FFFFFF80 H'FFFFFF81 H'FFFFFF82 H'FFFFFF83 H'FFFFFF84 H'FFFFFF85 H'FFFFFF86 H'FFFFFF87 DAR0 -- BETRD BDMRDL
BAMD31 BAMD30 BAMD29 BAMD28 BAMD27 BAMD26 BAMD25 BAMD24 BAMD23 BAMD22 BAMD21 BAMD20 BAMD19 BAMD18 BAMD17 BAMD16 BAMD15 BAMD14 BAMD13 BAMD12 BAMD11 BAMD10 BAMD9 BAMD7 -- CPD1 -- BAMD6 -- CPD0 -- BAMD5 -- IDD1 -- BAMD4 -- IDD0 -- BAMD3 -- RWD1 -- BAMD2 -- RWD0 -- BAMD1 XYED SZD1 -- BAMD8 BAMD0 XYSD SZD0 -- --
BDD31 BDD23 BDD15 BDD7
BDD30 BDD22 BDD14 BDD6
BDD29 BDD21 BDD13 BDD5
BDD28 BDD20 BDD12 BDD4
BDD27 BDD19 BDD11 BDD3
BDD26 BDD18 BDD10 BDD2
BDD25 BDD17 BDD9 BDD1
BDD24 BDD16 BDD8 BDD0
UBC
BDMD31 BDMD30 BDMD29 BDMD28 BDMD27 BDMD26 BDMD25 BDMD24 BDMD23 BDMD22 BDMD21 BDMD20 BDMD19 BDMD18 BDMD17 BDMD16 BDMD15 BDMD14 BDMD13 BDMD12 BDMD11 BDMD10 BDMD9 BDMD7 -- ETRD7 -- BDMD6 -- ETRD6 -- BDMD5 -- ETRD5 -- BDMD4 -- ETRD4 -- BDMD3 BDMD2 BDMD1 ETRD9 ETRD1 -- BDMD8 BDMD0 ETRD8 ETRD0 -- --
ETRD11 ETRD10 ETRD3 -- ETRD2 --
SAR0
DMAC
Rev. 2.00 Mar 09, 2006 page 896 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name TCR0 Bit Names Bit 7 -- Bit 6 -- Bit 5 -- Bit 4 -- Bit 3 -- Bit 2 -- Bit 1 -- Bit 0 -- Module DMAC
Address H'FFFFFF88 H'FFFFFF89 H'FFFFFF8A H'FFFFFF8B H'FFFFFF8C H'FFFFFF8D H'FFFFFF8E H'FFFFFF8F H'FFFFFF90 H'FFFFFF91 H'FFFFFF92 H'FFFFFF93 H'FFFFFF94 H'FFFFFF95 H'FFFFFF96 H'FFFFFF97 H'FFFFFF98 H'FFFFFF99 H'FFFFFF9A H'FFFFFF9B H'FFFFFF9C H'FFFFFF9D H'FFFFFF9E H'FFFFFF9F H'FFFFFFA0 H'FFFFFFA1 H'FFFFFFA2 H'FFFFFFA3 H'FFFFFFA4 to H'FFFFFFA7 H'FFFFFFA8 H'FFFFFFA9 H'FFFFFFAA H'FFFFFFAB H'FFFFFFAC to H'FFFFFFAF
CHCR0
-- -- DM1 AL
-- -- DM0 DS
-- -- SM1 DL
-- -- SM0 TB
-- -- TS1 TA
-- -- TS0 IE
-- -- AR TE
-- -- AM DE
SAR1
DAR1
TCR1
--
--
--
--
--
--
--
--
CHCR1
-- -- DM1 AL
-- -- DM0 DS -- -- -- VC6 --
-- -- SM1 DL -- -- -- VC5 --
-- -- SM0 TB -- -- -- VC4 --
-- -- TS1 TA -- -- -- VC3 --
-- -- TS0 IE -- -- -- VC2 --
-- -- AR TE -- -- -- VC1 --
-- -- AM DE -- -- -- VC0 -- --
VCRDMA0 -- -- -- VC7 -- --
VCRDMA1 -- -- -- VC7 -- --
-- -- -- VC6 --
-- -- -- VC5 --
-- -- -- VC4 --
-- -- -- VC3 --
-- -- -- VC2 --
-- -- -- VC1 --
-- -- -- VC0 --
DMAC
--
Rev. 2.00 Mar 09, 2006 page 897 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name DMAOR Bit Names Bit 7 -- -- -- -- -- -- Bit 6 -- -- -- -- -- Bit 5 -- -- -- -- -- Bit 4 -- -- -- -- -- Bit 3 -- -- -- PR -- Bit 2 -- -- -- AE -- Bit 1 -- -- -- NMIF -- Bit 0 -- -- -- DME -- -- Module DMAC
Address H'FFFFFFB0 H'FFFFFFB1 H'FFFFFFB2 H'FFFFFFB3 H'FFFFFFB4 to H'FFFFFFBF H'FFFFFFC0 H'FFFFFFC1 H'FFFFFFC2 to H'FFFFFFC3 H'FFFFFFC4 H'FFFFFFC5 H'FFFFFFC6 to H'FFFFFFDF H'FFFFFFE0 H'FFFFFFE1 H'FFFFFFE2 to H'FFFFFFE3 H'FFFFFFE4 H'FFFFFFE5 H'FFFFFFE6 to H'FFFFFFE7 H'FFFFFFE8 H'FFFFFFE9 H'FFFFFFEA to H'FFFFFFEB H'FFFFFFEC H'FFFFFFED H'FFFFFFEE to H'FFFFFFEF H'FFFFFFF0 H'FFFFFFF1
WCR2
A4WD1 --
A4WD0 -- --
-- -- --
A4WM -- --
A3WM IW41 --
A2WM IW40 --
A1WM W41 --
A0WM W40 --
BSC
--
--
--
WCR3
-- A3SHW1
--
A4SW2
A4SW1
A4SW0
--
A4HW1
A4HW0
BSC
A3SHW0 A2SHW1 A2SHW0 A1SHW1 A1SHW0 A0SHW1 A0SHW0 -- -- -- -- -- -- -- --
--
--
BCR1
-- A1LW1
A4LW1 A1LW0 --
A4LW0 A0LW1 --
A2ENDIA BSTROM -- N A0LW0 -- A4ENDIA DRAM2 N -- --
AHLW1 DRAM1 --
AHLW0 DRAM0 --
BSC
--
--
--
BCR2
-- A3SZ1
-- A3SZ0 --
-- A2SZ1 --
-- A2SZ0 --
-- A1SZ1 --
-- A1SZ0 --
A4SZ1 -- --
A4SZ0 -- --
BSC
--
--
--
WCR1
IW31 W31
IW30 W30 --
IW21 W21 --
IW20 W20 --
IW11 W11 --
IW10 W10 --
IW01 W01 --
IW00 W00 --
BSC
--
--
--
MCR
TRP0 AMX2
RCD0 SZ --
TRWL0 AMX1 --
TRAS1 AMX0 --
TRAS0 RFSH --
BE RMD --
RASD TRP1 --
TRWL1 RCD1 --
BSC
--
--
--
RTCSR
-- CMF
-- CMIE
-- CKS2
-- CKS1
-- CKS0
-- RRC2
-- RRC1
-- RRC0
BSC
Rev. 2.00 Mar 09, 2006 page 898 of 906 REJ09B0292-0200
Appendix A On-Chip Peripheral Module Registers
Register Name -- Bit Names Bit 7 -- Bit 6 -- Bit 5 -- Bit 4 -- Bit 3 -- Bit 2 -- Bit 1 -- Bit 0 -- Module --
Address H'FFFFFFF2 to H'FFFFFFF3 H'FFFFFFF4 H'FFFFFFF5 H'FFFFFFF6 to H'FFFFFFF7 H'FFFFFFF8 H'FFFFFFF9 H'FFFFFFFA to H'FFFFFFFB H'FFFFFFFC H'FFFFFFFD H'FFFFFFFE to H'FFFFFFFF
RTCNT
--
--
--
--
--
--
--
--
BSC
--
--
--
--
--
--
--
--
--
--
RTCOR
--
--
--
--
--
--
--
--
BSC
--
--
--
--
--
--
--
--
--
--
BCR3
-- DSWW1
--
--
-- -- --
A4LW2 -- --
AHLW2 BASEL --
A1LW2 EDO --
A0LW2 BWE --
BSC
DSWW0 -- -- --
--
--
--
Rev. 2.00 Mar 09, 2006 page 899 of 906 REJ09B0292-0200
Appendix B Pin States
Appendix B Pin States
B.1 Pin States in Reset, Power-Down State, and Bus-Released State
Pin State Manual Reset Power-Down State BusReleased State Z Z Z Z Z Z Ignored Z Z O I H Z Z Z Z O Z Z Ignored I I H
Pin Type
Pin Name
PowerStandby Standby On Bus Bus Mode Mode Sleep Reset Acquired Released (HIZ = 0) (HIZ = 1) Mode O Z H H H H Z H H H Z H H H H H L H H Z I Z H O IO O O O O I O O O I O O O O O O O O I I Z H Z Z Z Z Z Z Z Z Z O I H Z Z Z Z O Z Z Z I Z H Z Z H H H H Z H H H Z O H H H H L H H Z I I H Z Z H H H H Z H H H Z O H H H H Z H H Z I I Z O IO H H H H I H H O I O H H H H O H H I I I H
Bus control A24-A0 D31-D0 CS4-CS0 RD/WR RAS CAS/OE WAIT BS RD BGR BRLS CKE DQMUU/WE3 DQMUL/WE2 DQMLU/WE1 DQMLL/WE0 REFOUT CAS3-CAS0 BH BUSHiZ Interrupt NMI IRL3-IRL0 IVECF
Rev. 2.00 Mar 09, 2006 page 900 of 906 REJ09B0292-0200
Appendix B Pin States
Pin State Manual Reset Power-Down State BusReleased State O* I* IO* H I IO I O I I IO IO/I IO/O IO/I/O/O IO/I/I/O IO/I/IO IO/I/IO IO/IO/IO IO/O/IO IO/I/IO IO/I/I IO/I/O IO/I/IO IO/IO/IO IO/O/IO
Pin Type Clock
Pin Name XTAL EXTAL CKIO CKPACK CKPREQ/CKM PLLCAP2, PLLCAP1
PowerStandby Standby On Bus Bus Mode Mode Sleep Reset Acquired Released (HIZ = 0) (HIZ = 1) Mode O* I* IO* H I IO Z H I I Z Z Z Z Z O* I* IO* H I IO Z H I I IO/Z IO/Z IO/Z O* I* IO* H I IO Z H I I IO/Z IO/Z IO/Z O* I* IO* H I IO Z K I I K K K O* I* IO* H I IO Z Z I I Z Z Z O* I* IO* H I IO I O I I IO IO/I IO/O IO/I/O/O IO/I/I/O IO/I/IO IO/I/IO IO/IO/IO IO/O/IO IO/I/IO IO/I/I IO/I/O IO/I/IO IO/IO/IO IO/O/IO
DMAC
DREQ1, DREQ0 DACK1, DACK0
System control Port, Internal
RES MD4-MD0 PB15/SCK1 PB14/RXD1
peripheral PB13/TXD1 module PB12/SRCK2/RTS/ STATS1 PB11/SRS2/CTS/ STATS0
IO/Z/Z/O IO/Z/Z/O IO/Z/Z/O IO/Z/Z/O IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z IO/Z/Z
K/K/K/O Z K/K/K/O Z K/K/K K/K/K K/K/K K/K/K K/K/K K/K/K K/K/K K/K/K K/K/K K/K/K Z Z Z Z Z Z Z Z Z Z
PB10/SRXD2/TIOCA1 Z PB9/STCK2/TIOCB1, TCLKC PB8/STS2/TIOCA2 PB7/STXD2/TIOCB2, TCLKD PB6/SRCK1/SCK2 PB5/SRS1/RXD2 PB4/SRXD1/TXD2 PB3/STCK1/TIOCA0 PB2/STS1/TIOCB0 PB1/STXD1/TIOCC0, TCLKA Z Z Z Z Z Z Z Z Z
Rev. 2.00 Mar 09, 2006 page 901 of 906 REJ09B0292-0200
Appendix B Pin States
Pin State Manual Reset Power-Down State BusReleased State IO/IO/O IO/I IO/I IO/I IO/I IO/IO IO/O O/IO IO/I IO/I IO/O O/O IO/I IO/O IO/I I I I I O I
Pin Type Port, Internal
Pin Name PB0/TIOCD0, TCLKB/WOL
PowerStandby Standby On Bus Bus Mode Mode Sleep Reset Acquired Released (HIZ = 0) (HIZ = 1) Mode Z Z Z Z Z Z Z H Z Z Z H Z Z Z I I I I O I IO/Z/O IO/Z IO/Z IO/Z IO/Z IO/Z IO/Z H/IO IO/Z IO/Z IO/L H/L IO/I IO/O IO/I I I I I O I IO/Z/O IO/Z IO/Z IO/Z IO/Z IO/Z IO/Z H/IO IO/Z IO/Z IO/L H/L IO/I IO/O IO/I I I I I O I K/K/O K/K K/K K/K K/K K/K K/K O/K K K K K K K K I I I I O I Z Z Z Z Z Z Z O/Z Z Z Z Z Z Z Z I I I I O I IO/IO/O IO/I IO/I IO/I IO/I IO/IO IO/O O/IO IO/I IO/I IO/O O/O IO/I IO/O IO/I I I I I O I
peripheral PA13/SRCK0 module PA12/SRS0 PA11/SRXD0 PA10/STCK0 PA9/STS0 PA8/STXD0 WDTOVF/PA7 PA6/FTCI PA5/FTI PA4/FTOA CKPO/FTOB PA2/LNKSTA PA1/EXOUT PA0/CAMSEN HUDI TRST TCK TMS TDI TDO ASEMODE
Rev. 2.00 Mar 09, 2006 page 902 of 906 REJ09B0292-0200
Appendix B Pin States
Pin State Manual Reset Power-Down State BusReleased State I O O O I I O IO I I I I
Pin Type EtherC
Pin Name TX-CLK TX-EN TX-ER ETXD-ETXD0 CRS COL MDC MDIO RX-CLK RX-DV RX-ER ERXD-ERXD0
PowerStandby Standby On Bus Bus Mode Mode Sleep Reset Acquired Released (HIZ = 0) (HIZ = 1) Mode I O O O I I O IO I I I I I O O O I I O IO I I I I I O O O I I O IO I I I I I O O O I I O IO I I I I I O O O I I O IO I I I I I O O O I I O IO I I I I
I: O: H: L: Z: K:
Input Output High-level output Low-level output High-impedance state Input pins are in the high-impedance state; output pins maintain their previous state.
Notes: In sleep mode, if the DMAC is operating the address/data bus and bus control signals vary according to the operation of the DMAC. (The same applies when refreshing is performed.) * Depends on the clock mode (CKPREQN, MD2-MD0 setting).
Rev. 2.00 Mar 09, 2006 page 903 of 906 REJ09B0292-0200
Appendix C Product Lineup
Appendix C Product Lineup
Table C.1 SH7616 Product Lineup
Voltage 3.3 V Operating Frequency 62.5 MHz Mark Code HD6417616SF Package PLQP0208KA-A
Abbreviation SH7616
Rev. 2.00 Mar 09, 2006 page 904 of 906 REJ09B0292-0200
Appendix D Package Dimensions
Appendix D Package Dimensions
Figure D.1 shows the PLQP0208KA-A package dimensions.
JEITA Package Code P-LQFP208-28x28-0.50 RENESAS Code PLQP0208KA-A Previous Code FP-208C/FP-208CV MASS[Typ.] 2.7g
HD
*1
D 105 104 bp b1
156 157
NOTE) 1. DIMENSIONS"*1"AND"*2" DO NOT INCLUDE MOLD FLASH 2. DIMENSION"*3"DOES NOT INCLUDE TRIM OFFSET.
c1
2
HE
E
c
Terminal cross section
ZE
208 1 ZD Index mark 52 53
Reference Symbol
Dimension in Millimeters
F
A1
L L1
e
*3
y
bp
x
M
Detail F
D E A2 HD HE A A1 bp b1 c c1 e x y ZD ZE L L1
Nom Max 28 28 1.40 29.8 30.0 30.2 29.8 30.0 30.2 1.70 0.05 0.10 0.15 0.17 0.22 0.27 0.20 0.12 0.17 0.22 0.15 0 8 0.5 0.08 0.08 1.25 1.25 0.4 0.5 0.6 1.0
Min
A
A2
Figure D.1 Package Dimensions (PLQP0208KA-A)
Rev. 2.00 Mar 09, 2006 page 905 of 906 REJ09B0292-0200
c
Appendix D Package Dimensions
Rev. 2.00 Mar 09, 2006 page 906 of 906 REJ09B0292-0200
Renesas 32-Bit RISC Microcomputer Hardware Manual SH7616
Publication Date: 1st Edition, November 2001 Rev.2.00, March 09, 2006 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Customer Support Department Global Strategic Communication Div. Renesas Solutions Corp.
(c)2006. Renesas Technology Corp., All rights reserved. Printed in Japan.
Sales Strategic Planning Div.
Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japan
RENESAS SALES OFFICES
Refer to "http://www.renesas.com/en/network" for the latest and detailed information. Renesas Technology America, Inc. 450 Holger Way, San Jose, CA 95134-1368, U.S.A Tel: <1> (408) 382-7500, Fax: <1> (408) 382-7501 Renesas Technology Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K. Tel: <44> (1628) 585-100, Fax: <44> (1628) 585-900 Renesas Technology (Shanghai) Co., Ltd. Unit 204, 205, AZIACenter, No.1233 Lujiazui Ring Rd, Pudong District, Shanghai, China 200120 Tel: <86> (21) 5877-1818, Fax: <86> (21) 6887-7898 Renesas Technology Hong Kong Ltd. 7th Floor, North Tower, World Finance Centre, Harbour City, 1 Canton Road, Tsimshatsui, Kowloon, Hong Kong Tel: <852> 2265-6688, Fax: <852> 2730-6071 Renesas Technology Taiwan Co., Ltd. 10th Floor, No.99, Fushing North Road, Taipei, Taiwan Tel: <886> (2) 2715-2888, Fax: <886> (2) 2713-2999 Renesas Technology Singapore Pte. Ltd. 1 Harbour Front Avenue, #06-10, Keppel Bay Tower, Singapore 098632 Tel: <65> 6213-0200, Fax: <65> 6278-8001 Renesas Technology Korea Co., Ltd. Kukje Center Bldg. 18th Fl., 191, 2-ka, Hangang-ro, Yongsan-ku, Seoul 140-702, Korea Tel: <82> (2) 796-3115, Fax: <82> (2) 796-2145
http://www.renesas.com
Renesas Technology Malaysia Sdn. Bhd Unit 906, Block B, Menara Amcorp, Amcorp Trade Centre, No.18, Jalan Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia Tel: <603> 7955-9390, Fax: <603> 7955-9510
Colophon 6.0
SH7616 Hardware Manual


▲Up To Search▲   

 
Price & Availability of HD6417616

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X