To our customers,
Old Company Name in Catalogs and Other Documents
On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding.
Renesas Electronics website: http://www.renesas.com
April 1st, 2010 Renesas Electronics Corporation
Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry.
Notice
1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from the use of these circuits, software, or information. When exporting the products or technology described in this document, you should comply with the applicable export control laws and regulations and follow the procedures required by such laws and regulations. You should not use Renesas Electronics products or the technology described in this document for any purpose relating to military applications or use by the military, including but not limited to the development of weapons of mass destruction. Renesas Electronics products and technology may not be used for or incorporated into any products or systems whose manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations. Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics does not warrant that such information is error free. Renesas Electronics assumes no liability whatsoever for any damages incurred by you resulting from errors in or omissions from the information included herein. Renesas Electronics products are classified according to the following three quality grades: “Standard”, “High Quality”, and “Specific”. The recommended applications for each Renesas Electronics product depends on the product’s quality grade, as indicated below. You must check the quality grade of each Renesas Electronics product before using it in a particular application. You may not use any Renesas Electronics product for any application categorized as “Specific” without the prior written consent of Renesas Electronics. Further, you may not use any Renesas Electronics product for any application for which it is not intended without the prior written consent of Renesas Electronics. Renesas Electronics shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for an application categorized as “Specific” or for which the product is not intended where you have failed to obtain the prior written consent of Renesas Electronics. The quality grade of each Renesas Electronics product is “Standard” unless otherwise expressly specified in a Renesas Electronics data sheets or data books, etc. Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots. “High Quality”: Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anticrime systems; safety equipment; and medical equipment not specifically designed for life support. “Specific”: Aircraft; aerospace equipment; submersible repeaters; nuclear reactor control systems; medical equipment or systems for life support (e.g. artificial life support devices or systems), surgical implantations, or healthcare intervention (e.g. excision, etc.), and any other applications or purposes that pose a direct threat to human life. You should use the Renesas Electronics products described in this document within the range specified by Renesas Electronics, especially with respect to the maximum rating, operating supply voltage range, movement power voltage range, heat radiation characteristics, installation and other product characteristics. Renesas Electronics shall have no liability for malfunctions or damages arising out of the use of Renesas Electronics products beyond such specified ranges. Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further, Renesas Electronics products are not subject to radiation resistance design. Please be sure to implement safety measures to guard them against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a Renesas Electronics product, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures. Because the evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or system manufactured by you. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. Please use Renesas Electronics products in compliance with all applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive. Renesas Electronics assumes no liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations. This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written consent of Renesas Electronics. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products, or if you have any other inquiries. “Standard”:
2.
3. 4.
5.
6.
7.
8.
9.
10.
11. 12.
(Note 1) “Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its majorityowned subsidiaries. (Note 2) “Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.
H8S/2172 Group 16
Hardware Manual Renesas 16-Bit Single-Chip Microcomputer H8S Family/H8S/2100 Series
H8S/2170 HD64F2170
User’s Manual
The revision list can be viewed directly by cliking the title page. The revision list summarizes the locations of revisions and additions. Details should always be checked by referring to the relevant text.
Rev.2.00 2004.03
Rev. 2.00, 03/04, page ii of xxxii
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, 03/04, page iii of xxxii
General Precautions on Handling of Product
1. Treatment of NC Pins Note: Do not connect anything to the NC pins. The NC (not connected) pins are either not connected to any of the internal circuitry or are used as test pins or to reduce noise. If something is connected to the NC pins, the operation of the LSI is not guaranteed. 2. Treatment of Unused Input Pins Note: Fix all unused input pins to high or low level. Generally, the input pins of CMOS products are high-impedance input pins. If unused pins are in their open states, intermediate levels are induced by noise in the vicinity, a passthrough current flows internally, and a malfunction may occur. 3. Processing before Initialization Note: When power is first supplied, the product's state is undefined. The states of internal circuits are undefined until full power is supplied throughout the chip and a low level is input on the reset pin. During the period where the states are undefined, the register settings and the output state of each pin are also undefined. Design your system so that it does not malfunction because of processing while it is in this undefined state. For those products which have a reset function, reset the LSI immediately after the power supply has been turned on. 4. Prohibition of Access to Undefined or Reserved Addresses Note: Access to undefined or reserved addresses is prohibited. The undefined or reserved addresses may be used to expand functions, or test registers may have been be allocated to these addresses. Do not access these registers; the system's operation is not guaranteed if they are accessed.
Rev. 2.00, 03/04, page iv of xxxii
Configuration of This Manual
This manual comprises the following items: 1. 2. 3. 4. 5. 6. General Precautions on Handling of Product Configuration of This Manual Preface Contents Overview Description of Functional Modules • CPU and System-Control Modules • On-Chip Peripheral Modules The configuration of the functional description of each module differs according to the module. However, the generic style includes the following items: i) Feature ii) Input/Output Pin iii) Register Description iv) Operation v) Usage Note
When designing an application system that includes this LSI, take notes into account. Each section includes notes in relation to the descriptions given, and usage notes are given, as required, as the final part of each section. 7. List of Registers 8. Electrical Characteristics 9. Appendix 10. Main Revisions and Additions in this Edition (only for revised versions) The list of revisions is a summary of points that have been revised or added to earlier versions. This does not include all of the revised contents. For details, see the actual locations in this manual. 11. Index
Rev. 2.00, 03/04, page v of xxxii
Preface
This LSI is a microcomputer (MCU) made up of the H8S/2000 CPU employing Renesas Technolgy's original architecture as its core, and the peripheral functions required to configure a system. The H8S/2000 CPU has an internal 32-bit configuration, sixteen 16-bit general registers, and a simple and optimized instruction set for high-speed operation. The H8S/2000 CPU can handle a 16-Mbyte linear address space. This LSI is equipped with ROM and RAM memory, direct memory access controller (DMAC) bus master, an 8-bit timer (TMR), a watchdog timer (WDT), a universal serial bus 2 (USB2), a serial communication interface for boot mode (SCI), and I/O ports as on-chip peripheral modules required for system configuration. A flash memory (F-ZTATTM*) version is available for this LSI's ROM. The F-ZTAT version provides flexibility as it can be reprogrammed in no time to cope with all situations from the early stages of mass production to full-scale mass production. This is particularly applicable to application devices with specifications that will most probably change. This manual describes this LSI's hardware. Note: * F-ZTATTM is a trademark of Renesas Technolgy. Corp. Target Users: This manual was written for users who will be using this LSI in the design of application systems. Target users are expected to understand the fundamentals of electrical circuits, logical circuits, and microcomputers. Objective: This manual was written to explain the hardware functions and electrical characteristics of this LSI to the target users. Refer to the H8S/2600 Series, H8S/2000 Series Programming Manual for a detailed description of the instruction set.
Notes on reading this manual: • In order to understand the overall functions of the chip Read the manual according to the contents. This manual can be roughly categorized into parts on the CPU, system control functions, peripheral functions, and electrical characteristics. • In order to understand the details of the CPU's functions Read the H8S/2600 Series, H8S/2000 Series Programming Manual. • In order to understand the details of a register when its name is known Read the index that is the final part of the manual to find the page number of the entry on the register. The addresses, bits, and initial values of the registers are summarized in section 17, List of Registers.
Rev. 2.00, 03/04, page vi of xxxii
Examples:
Register name:
Bit order: Number notation: Signal notation: Related Manuals:
The following notation is used for cases when the same or a similar function, e.g. DMAC or serial communication interface, is implemented on more than one channel: XXX_N (XXX is the register name and N is the channel number) The MSB is on the left and the LSB is on the right. Binary is B’xxxx, hexadecimal is H’xxxx. An overbar is added to a low-active signal: xxxx
The latest versions of all related manuals are available from our web site. Please ensure you have the latest versions of all documents you require. (http://www.renesas.com/eng/)
H8S/2170 F-ZTATTM manuals:
Document Title H8S/2172 Series H8S/2170 F-ZTAT
TM
Document No. Hardware Manual This manual ADE-602-083
H8S/2600 Series, H8S/2000 Series Programming Manual
User's manuals for development tools:
Document Title H8S, H8/300 Series C/C++ Compiler, Assembler, Optimizing Linkage Editor User's Manual H8S, H8/300 Series Simulator/Debugger User's Manual H8S, H8/300 Series High-performance Embedded Workshop, High-performance Debugging Interface Tutorial High-performance Embedded Workshop User's Manual Document No. ADE-702-247 ADE-702-282 ADE-702-231 ADE-702-201
Rev. 2.00, 03/04, page vii of xxxii
Rev. 2.00, 03/04, page viii of xxxii
Contents
Section 1 Overview............................................................................................1
1.1 1.2 1.3 Features............................................................................................................................. 1 Internal Block Diagram..................................................................................................... 2 Pin Description.................................................................................................................. 3 1.3.1 Pin Arrangement .................................................................................................. 3 1.3.2 Pin Arrangements in Each Mode ......................................................................... 4 1.3.3 Pin Functions ....................................................................................................... 8
Section 2 CPU....................................................................................................13
2.1 Features............................................................................................................................. 13 2.1.1 Differences between H8S/2600 CPU and H8S/2000 CPU .................................. 14 2.1.2 Differences from H8/300 CPU ............................................................................ 15 2.1.3 Differences from H8/300H CPU.......................................................................... 15 CPU Operating Modes...................................................................................................... 16 2.2.1 Normal Mode....................................................................................................... 16 2.2.2 Advanced Mode................................................................................................... 18 Address Space................................................................................................................... 20 Register Configuration...................................................................................................... 21 2.4.1 General Registers................................................................................................. 22 2.4.2 Program Counter (PC) ......................................................................................... 23 2.4.3 Extended Control Register (EXR) ....................................................................... 23 2.4.4 Condition-Code Register (CCR).......................................................................... 24 2.4.5 Initial Register Values.......................................................................................... 25 Data Formats..................................................................................................................... 26 2.5.1 General Register Data Formats ............................................................................ 26 2.5.2 Memory Data Formats ......................................................................................... 28 Instruction Set ................................................................................................................... 29 2.6.1 Table of Instructions Classified by Function ....................................................... 30 2.6.2 Basic Instruction Formats .................................................................................... 39 Addressing Modes and Effective Address Calculation..................................................... 40 2.7.1 Register DirectRn ............................................................................................ 41 2.7.2 Register Indirect@ERn .................................................................................... 41 2.7.3 Register Indirect with Displacement@(d:16, ERn) or @(d:32, ERn).............. 41 2.7.4 Register Indirect with Post-Increment or Pre-Decrement @ERn+ or @-ERn ........................................................................................... 41 2.7.5 Absolute Address@aa:8, @aa:16, @aa:24, or @aa:32.................................... 41 2.7.6 Immediate#xx:8, #xx:16, or #xx:32................................................................. 42 2.7.7 Program-Counter Relative@(d:8, PC) or @(d:16, PC).................................... 42 2.7.8 Memory Indirect@@aa:8 ................................................................................ 42
Rev. 2.00, 03/04, page ix of xxxii
2.2
2.3 2.4
2.5
2.6
2.7
2.8 2.9
2.7.9 Effective Address Calculation ............................................................................. 44 Processing States............................................................................................................... 46 Usage Note........................................................................................................................ 47 2.9.1 Note on Bit Manipulation Instructions ................................................................ 47
Section 3 MCU Operating Modes ..................................................................... 49
3.1 3.2 Operating Mode Selection ................................................................................................ 49 Register Descriptions........................................................................................................ 50 3.2.1 Mode Control Register (MDCR) ......................................................................... 50 3.2.2 System Control Register (SYSCR)...................................................................... 51 Operating Modes............................................................................................................... 52 3.3.1 Mode 2................................................................................................................. 52 3.3.2 Pin Functions ....................................................................................................... 52 Address Map ..................................................................................................................... 53
3.3
3.4
Section 4 Exception Handling ........................................................................... 55
4.1 4.2 4.3 Exception Handling Types and Priority............................................................................ 55 Exception Sources and Exception Vector Table ............................................................... 56 Reset ................................................................................................................................. 57 4.3.1 Reset Exception Handling ................................................................................... 57 4.3.2 Interrupts after Reset............................................................................................ 58 4.3.3 On-Chip Peripheral Modules after Reset is Cancelled ........................................ 58 Interrupt Exception Handling ........................................................................................... 59 Trap Instruction Exception Handling................................................................................ 59 Stack Status after Exception Handling.............................................................................. 60 Usage Note........................................................................................................................ 60
4.4 4.5 4.6 4.7
Section 5 Interrupt Controller............................................................................ 63
5.1 5.2 5.3 Features............................................................................................................................. 63 Input/Output Pins.............................................................................................................. 64 Register Descriptions........................................................................................................ 64 5.3.1 Interrupt Control Registers A to C (ICRA to ICRC) ........................................... 64 5.3.2 Address Break Control Register (ABRKCR) ...................................................... 65 5.3.3 Break Address Registers A to C (PBARA to PBARC) ....................................... 66 5.3.4 IRQ Sense Control Registers H, L (ISCRH, ISCRL) .......................................... 67 5.3.5 IRQ Enable Register (IER) .................................................................................. 68 5.3.6 IRQ Status Register (ISR).................................................................................... 68 Interrupt Sources............................................................................................................... 69 5.4.1 External Interrupts ............................................................................................... 69 5.4.2 Internal Interrupts ................................................................................................ 70 Interrupt Exception Handling Vector Table...................................................................... 70 Interrupt Control Modes and Interrupt Operation ............................................................. 72 5.6.1 Interrupt Control Mode 0..................................................................................... 74
5.4
5.5 5.6
Rev. 2.00, 03/04, page x of xxxii
5.7
5.6.2 Interrupt Control Mode 1 ..................................................................................... 76 5.6.3 Interrupt Exception Handling Sequence .............................................................. 78 5.6.4 Interrupt Response Times .................................................................................... 80 Usage Notes ...................................................................................................................... 81 5.7.1 Conflict between Interrupt Generation and Disabling ......................................... 81 5.7.2 Instructions that Disable Interrupts ...................................................................... 82 5.7.3 Interrupts during Execution of EEPMOV Instruction.......................................... 82
Section 6 Bus Controller (BSC).........................................................................83
6.1 6.2 6.3 Features............................................................................................................................. 83 Input/Output Pins .............................................................................................................. 85 Register Descriptions ........................................................................................................ 86 6.3.1 Access Control Register (ACSCR) ...................................................................... 87 6.3.2 CS Assertion Period Control Register (CSACR)................................................. 88 6.3.3 Wait Control Register (WTCR) ........................................................................... 90 6.3.4 Bus Control Register (BCR) ................................................................................ 92 6.3.5 Read Strobe Timing Control Register (RDNCR) ................................................ 93 6.3.6 DRAM Control Register (DRAMCR) ................................................................. 94 6.3.7 DRAM Access Control Register (DRACCR)...................................................... 97 6.3.8 Refresh Control Register (REFCR) ..................................................................... 98 6.3.9 Refresh Timer Counter (RTCNT)........................................................................ 101 6.3.10 Refresh Time Constant Register (RTCOR) ......................................................... 101 Bus Control ....................................................................................................................... 102 6.4.1 Area Division....................................................................................................... 102 6.4.2 Address Map ........................................................................................................ 103 6.4.3 Bus Specifications................................................................................................ 105 6.4.4 Memory Interfaces............................................................................................... 107 6.4.5 Chip Select Signals .............................................................................................. 108 Basic Bus Interface ........................................................................................................... 109 6.5.1 Data Size and Data Alignment............................................................................. 109 6.5.2 Valid Strobes ....................................................................................................... 110 6.5.3 Basic Timing........................................................................................................ 110 6.5.4 Wait Control ........................................................................................................ 119 6.5.5 Read Strobe (RD) Timing.................................................................................... 120 6.5.6 Extension of Chip Select (CS) Assertion Period.................................................. 121 DRAM Interface ............................................................................................................... 122 6.6.1 Setting DRAM Space........................................................................................... 122 6.6.2 Address Multiplexing .......................................................................................... 122 6.6.3 Data Bus............................................................................................................... 123 6.6.4 Pins Used for DRAM Interface............................................................................ 123 6.6.5 Basic Timing........................................................................................................ 124 6.6.6 Column Address Output Cycle Control ............................................................... 125 6.6.7 Row Address Output State Control...................................................................... 126
Rev. 2.00, 03/04, page xi of xxxii
6.4
6.5
6.6
6.6.8 Precharge State Control ....................................................................................... 128 6.6.9 Wait Control ........................................................................................................ 129 6.6.10 Byte Access Control ............................................................................................ 131 6.6.11 Burst Operation.................................................................................................... 132 6.6.12 Refresh Control.................................................................................................... 137 6.6.13 DMAC Single Address Transfer Mode and DRAM Interface............................. 140 6.7 Idle Cycle.......................................................................................................................... 142 6.7.1 Operation ............................................................................................................. 142 6.7.2 Pin States in Idle Cycle........................................................................................ 149 6.8 Write Data Buffer Function .............................................................................................. 150 6.9 Bus Arbitration ................................................................................................................. 151 6.9.1 Operation ............................................................................................................. 151 6.9.2 Bus Transfer Timing............................................................................................ 151 6.10 Bus Controller Operation in Reset .................................................................................... 152
Section 7 DMA Controller (DMAC)................................................................. 153
7.1 7.2 7.3 Features............................................................................................................................. 153 Input/Output Pins.............................................................................................................. 155 Register Descriptions........................................................................................................ 157 7.3.1 DMA Source Address Register (DMSAR).......................................................... 158 7.3.2 DMA Destination Address Register (DMDAR) .................................................. 158 7.3.3 DMA Transfer Count Register (DMTCR)........................................................... 158 7.3.4 DMA Mode Control Register (DMMDR) ........................................................... 160 7.3.5 DMA Address Control Register (DMACR) ........................................................ 165 7.3.6 USB Transfer Control Register (USTCR) ........................................................... 169 Operation .......................................................................................................................... 171 7.4.1 Transfer Modes.................................................................................................... 171 7.4.2 Address Modes (Dual Address Mode/Single Address Mode) ............................. 172 7.4.3 DMA Transfer Requests (Auto Request Mode/External Request Mode/USB Transfer Request) ............... 176 7.4.4 Bus Modes (Cycle Steal Mode/Burst Mode) ....................................................... 177 7.4.5 Transfer Modes (Normal Transfer Mode/Block Transfer Mode) ........................ 178 7.4.6 Repeat Area Function .......................................................................................... 179 7.4.7 Registers during DMA Transfer Operation ......................................................... 182 7.4.8 Channel Priority................................................................................................... 186 7.4.9 DMAC Bus Cycles (Dual Address Mode)........................................................... 189 7.4.10 DMAC Bus Cycles (Single Address Mode) ........................................................ 196 7.4.11 Examples of Operation Timing in Each Mode .................................................... 201 7.4.12 Ending DMA Transfer ......................................................................................... 212 7.4.13 Relationship between DMAC and Other Bus Masters ........................................ 213 Interrupt Sources............................................................................................................... 213 Usage Notes ...................................................................................................................... 216
7.4
7.5 7.6
Rev. 2.00, 03/04, page xii of xxxii
Section 8 I/O Ports .............................................................................................219
8.1 Port 1................................................................................................................................. 222 8.1.1 Port 1 Data Direction Register (P1DDR)............................................................. 222 8.1.2 Port 1 Data Register (P1DR)................................................................................ 223 8.1.3 Port 1 Register (PORT1)...................................................................................... 223 8.1.4 Pin Functions ....................................................................................................... 224 Port 2................................................................................................................................. 226 8.2.1 Port 2 Data Direction Register (P2DDR)............................................................. 226 8.2.2 Port 2 Data Register (P2DR)................................................................................ 226 8.2.3 Port 2 Register (PORT2)...................................................................................... 227 8.2.4 Pin Functions ....................................................................................................... 227 Port 3................................................................................................................................. 230 8.3.1 Port 3 Data Direction Register (P3DDR)............................................................. 230 8.3.2 Port 3 Data Register (P3DR)................................................................................ 230 8.3.3 Port 3 Register (PORT3)...................................................................................... 231 8.3.4 Pin Functions ....................................................................................................... 231 Port 4................................................................................................................................. 233 8.4.1 Port 4 Data Direction Register (P4DDR)............................................................. 233 8.4.2 Port 4 Data Register (P4DR)................................................................................ 234 8.4.3 Port 4 Register (PORT4)...................................................................................... 234 8.4.4 Pin Functions ....................................................................................................... 235 Port 5................................................................................................................................. 237 8.5.1 Port 5 Data Direction Register (P5DDR)............................................................. 237 8.5.2 Port 5 Data Register (P5DR)................................................................................ 237 8.5.3 Port 5 Register (PORT5)...................................................................................... 238 8.5.4 Pin Functions ....................................................................................................... 238 Port 6................................................................................................................................. 242 8.6.1 Port 6 Data Direction Register (P6DDR)............................................................. 242 8.6.2 Port 6 Data Register (P6DR)................................................................................ 242 8.6.3 Port 6 Register (PORT6)...................................................................................... 243 8.6.4 Pin Functions ....................................................................................................... 243 Port 7................................................................................................................................. 246 8.7.1 Port 7 Data Direction Register (P7DDR)............................................................. 246 8.7.2 Port 7 Data Register (P7DR)................................................................................ 247 8.7.3 Port 7 Register (PORT7)...................................................................................... 247 8.7.4 Pin Functions ....................................................................................................... 248 Port 8................................................................................................................................. 251 8.8.1 Port 8 Data Direction Register (P8DDR)............................................................. 251 8.8.2 Port 8 Data Register (P8DR)................................................................................ 251 8.8.3 Port 8 Register (PORT8)...................................................................................... 252 8.8.4 Pin Functions ....................................................................................................... 252 Port 9................................................................................................................................. 254 8.9.1 Port 9 Data Direction Register (P9DDR)............................................................. 254
Rev. 2.00, 03/04, page xiii of xxxii
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
8.9.2 Port 9 Data Register (P9DR) ............................................................................... 255 8.9.3 Port 9 Register (PORT9)...................................................................................... 255 8.9.4 Pin Functions ....................................................................................................... 256 8.10 Port A................................................................................................................................ 258 8.10.1 Port A Data Direction Register (PADDR)........................................................... 258 8.10.2 Port A Data Register (PADR).............................................................................. 258 8.10.3 Port A Register (PORTA).................................................................................... 259 8.10.4 Pin Functions ....................................................................................................... 259 8.11 Pin Selection ..................................................................................................................... 261 8.11.1 Port Function Control Register 1 (PFCR1).......................................................... 261 8.11.2 IRQ Sense Port Select Register (ISSR) ............................................................... 262
Section 9 8-Bit Timer (TMR)............................................................................ 263
9.1 9.2 9.3 Features............................................................................................................................. 263 Input/Output Pins.............................................................................................................. 265 Register Descriptions........................................................................................................ 265 9.3.1 Timer Counter (TCNT)........................................................................................ 265 9.3.2 Time Constant Register A (TCORA) .................................................................. 266 9.3.3 Time Constant Register B (TCORB)................................................................... 266 9.3.4 Timer Control Register (TCR)............................................................................. 266 9.3.5 Timer Control/Status Register (TCSR)................................................................ 268 Operation .......................................................................................................................... 270 9.4.1 Pulse Output ........................................................................................................ 270 Operation Timing.............................................................................................................. 271 9.5.1 TCNT Incrementation Timing ............................................................................. 271 9.5.2 Timing of CMFA and CMFB Setting when Compare-Match Occurs ................. 272 9.5.3 Timing of Timer Output when Compare-Match Occurs...................................... 272 9.5.4 Timing of Compare Match Clear......................................................................... 273 9.5.5 Timing of TCNT External Reset.......................................................................... 273 9.5.6 Timing of Overflow Flag (OVF) Setting ............................................................. 273 Operation with Cascaded Connection............................................................................... 274 9.6.1 16-Bit Counter Mode ........................................................................................... 274 9.6.2 Compare Match Count Mode .............................................................................. 275 Interrupt Sources............................................................................................................... 275 9.7.1 Interrupt Sources.................................................................................................. 275 Usage Notes ...................................................................................................................... 276 9.8.1 Contention between TCNT Write and Clear........................................................ 276 9.8.2 Contention between TCNT Write and Increment ................................................ 277 9.8.3 Contention between TCOR Write and Compare Match ...................................... 278 9.8.4 Contention between Compare Matches A and B ................................................. 279 9.8.5 Switching of Internal Clocks and TCNT Operation ............................................ 279 9.8.6 Mode Setting with Cascaded Connection ............................................................ 281 9.8.7 Interrupts in Module Stop Mode.......................................................................... 281
9.4 9.5
9.6
9.7 9.8
Rev. 2.00, 03/04, page xiv of xxxii
Section 10 Watchdog Timer (WDT)..................................................................283
10.1 Features............................................................................................................................. 283 10.2 Register Descriptions ........................................................................................................ 284 10.2.1 Timer Counter (TCNT)........................................................................................ 284 10.2.2 Timer Control/Status Register (TCSR)................................................................ 284 10.3 Operation .......................................................................................................................... 286 10.3.1 Watchdog Timer Mode ........................................................................................ 286 10.3.2 Interval Timer Mode............................................................................................ 287 10.3.3 Watchdog Timer Overflow Flag (OVF) Timing.................................................. 288 10.4 Interrupt Sources............................................................................................................... 288 10.5 Usage Notes ...................................................................................................................... 289 10.5.1 Notes on Register Access..................................................................................... 289 10.5.2 Conflict between Timer Counter (TCNT) Write and Increment.......................... 290 10.5.3 Changing Values of CKS2 to CKS0 Bits............................................................. 290 10.5.4 Switching between Watchdog Timer Mode and Interval Timer Mode................ 290
Section 11 Serial Communication Interface for Boot Mode (SCI) ...................291
11.1 Features............................................................................................................................. 291 11.2 Input/Output Pins .............................................................................................................. 292 11.3 Register Descriptions ........................................................................................................ 293 11.3.1 Receive Shift Register (RSR) .............................................................................. 293 11.3.2 Receive Data Register (RDR) .............................................................................. 293 11.3.3 Transmit Data Register (TDR)............................................................................. 293 11.3.4 Transmit Shift Register (TSR) ............................................................................. 294 11.3.5 Serial Mode Register (SMR) ............................................................................... 294 11.3.6 Serial Control Register (SCR) ............................................................................. 295 11.3.7 Serial Status Register (SSR) ................................................................................ 297 11.3.8 Bit Rate Register (BRR) ...................................................................................... 300 11.4 Operation in Asynchronous Mode .................................................................................... 304 11.4.1 Data Transfer Format........................................................................................... 305 11.4.2 Receive Data Sampling Timing and Reception Margin in Asynchronous Mode ............................................................................................ 306 11.4.3 Clock.................................................................................................................... 307 11.4.4 SCI Initialization (Asynchronous Mode) ............................................................. 307 11.4.5 Data Transmission (Asynchronous Mode)........................................................... 308 11.4.6 Serial Data Reception (Asynchronous Mode)...................................................... 310 11.5 Interrupt Sources............................................................................................................... 314 11.5.1 Interrupts in Normal Serial Communication Interface Mode .............................. 314 11.6 Usage Notes ...................................................................................................................... 315 11.6.1 Module Stop Mode Setting .................................................................................. 315 11.6.2 Relation between Writes to TDR and the TDRE Flag ......................................... 315 11.6.3 Operation in Case of Mode Transition................................................................. 315
Rev. 2.00, 03/04, page xv of xxxii
Section 12 Universal Serial Bus 2 (USB2)........................................................ 319
12.1 Features............................................................................................................................. 319 12.2 Input/Output Signals ......................................................................................................... 321 12.3 Register Descriptions........................................................................................................ 322 12.3.1 Interrupt Flag Register 0 (IFR0) .......................................................................... 323 12.3.2 Interrupt Select Register 0 (ISR0)........................................................................ 328 12.3.3 Interrupt Enable Register 0 (IER0) ...................................................................... 329 12.3.4 EP0o Receive Data Size Register (EPSZ0o) ....................................................... 329 12.3.5 EP1 Receive Data Size Register (EPSZ1) ........................................................... 330 12.3.6 EP0i Data Register (EPDR0i).............................................................................. 330 12.3.7 EP0o Data Register (EPDR0o) ............................................................................ 330 12.3.8 EP0s Data Register (EPDR0s) ............................................................................. 331 12.3.9 EP1 Data Register (EPDR1) ................................................................................ 331 12.3.10 EP2 Data Register (EPDR2) ................................................................................ 331 12.3.11 EP3 Data Register (EPDR3) ................................................................................ 332 12.3.12 Data Status Register 0 (DASTS0)........................................................................ 332 12.3.13 Packet Enable Register 0i (PKTE0i).................................................................... 333 12.3.14 Packet Enable Register 2 (PKTE2)...................................................................... 333 12.3.15 Packet Enable Register 3 (PKTE3)...................................................................... 333 12.3.16 FIFO Clear Register 0 (FCLR0) .......................................................................... 334 12.3.17 Endpoint Stall Register 0 (EPSTL0).................................................................... 336 12.3.18 DMA Set Register 0 (DMA0).............................................................................. 336 12.3.19 Control Register (CTRL) ..................................................................................... 337 12.3.20 Port Function Control Register 3 (PFCR3).......................................................... 338 12.3.21 USB Suspend Status Register (USBSUSP) ......................................................... 338 12.4 Interrupt Pins .................................................................................................................... 340 12.4.1 USBI0 Interrupt ................................................................................................... 340 12.4.2 USBI1 Interrupt ................................................................................................... 340 12.5 Communication Operation................................................................................................ 341 12.5.1 USB Cable Connection........................................................................................ 341 12.5.2 USB Cable Disconnection ................................................................................... 342 12.5.3 Control Transfer................................................................................................... 343 12.5.4 EP1 Bulk-Out Transfer (Dual FIFO) ................................................................... 349 12.5.5 EP2 Bulk-In Transfer (Dual FIFO)...................................................................... 351 12.5.6 EP3 Interrupt-In Transfer..................................................................................... 353 12.5.7 Processing of USB Standard Requests and Class/Vendor Requests.................... 354 12.5.8 Stall Operations ................................................................................................... 355 12.5.9 Tree Configuration............................................................................................... 358 12.5.10 Power Supply Specification................................................................................. 358 12.6 Notes on Using DMA ....................................................................................................... 358 12.7 Transition to USB Suspend Mode .................................................................................... 359 12.7.1 Suspend Signal Output......................................................................................... 359 12.7.2 Software Standby in Suspend Mode .................................................................... 361
Rev. 2.00, 03/04, page xvi of xxxii
12.8 Usage Notes ...................................................................................................................... 364 12.8.1 Setup Data Reception........................................................................................... 364 12.8.2 FIFO Clear ........................................................................................................... 364 12.8.3 Operating Frequency............................................................................................ 364 12.8.4 Interrupts.............................................................................................................. 364 12.8.5 Register Access Size ............................................................................................ 364 12.8.6 Data Register Overread or Overwrite .................................................................. 365 12.8.7 EP0 Interrupt Sources Assignment ...................................................................... 365 12.8.8 FIFO Size at Full Speed Mode............................................................................. 365 12.8.9 Level Shifter for VBUS Pin................................................................................. 366 12.8.10 USB 2.0 Transceiver (Physical Layer) ................................................................ 366 12.8.11 EPDR0s Read ...................................................................................................... 366 12.8.12 USB Bus Idle in High-Speed Mode..................................................................... 366 12.8.13 Note on USB Bus Disconnection......................................................................... 367 12.8.14 Example of External Circuit ................................................................................ 367 12.8.15 External Physical Layer LSI ................................................................................ 368 12.8.16 Operation at the Bus Reset Reception.................................................................. 368 12.8.17 Usage Notes in Control IN Transfer .................................................................... 369 12.8.18 USB Interrupt During Software Standby ............................................................. 369
Section 13 RAM ................................................................................................371 Section 14 Flash Memory (0.18-µm F-ZTAT Version) ....................................373
14.1 Features............................................................................................................................. 373 14.1.1 Operating Mode ................................................................................................... 375 14.1.2 Mode Comparison................................................................................................ 376 14.1.3 Flash MAT Configuration.................................................................................... 377 14.1.4 Block Division ..................................................................................................... 378 14.1.5 Programming/Erasing Interface ........................................................................... 379 14.2 Input/Output Pins .............................................................................................................. 381 14.3 Register Descriptions ........................................................................................................ 381 14.3.1 Programming/Erasing Interface Register............................................................. 382 14.3.2 Programming/Erasing Interface Parameter .......................................................... 391 14.4 On-Board Programming Mode ......................................................................................... 401 14.4.1 Boot Mode ........................................................................................................... 401 14.4.2 User Program Mode............................................................................................. 405 14.4.3 User Boot Mode................................................................................................... 415 14.4.4 Procedure Program and Storable Area for Programming Data ............................ 418 14.5 Protection .......................................................................................................................... 428 14.5.1 Hardware Protection ............................................................................................ 428 14.5.2 Software Protection.............................................................................................. 429 14.5.3 Error Protection.................................................................................................... 429 14.6 Switching between User MAT and User Boot MAT ........................................................ 431
Rev. 2.00, 03/04, page xvii of xxxii
14.7 Flash Memory Emulation in RAM ................................................................................... 432 14.7.1 Emulation in RAM .............................................................................................. 432 14.7.2 RAM Overlap ...................................................................................................... 433 14.8 Programmer Mode ............................................................................................................ 434 14.9 Serial Communication Interface Specification for Boot Mode......................................... 435 14.10 Usage Notes ...................................................................................................................... 461
Section 15 Clock Pulse Generator..................................................................... 463
15.1 Oscillator........................................................................................................................... 463 15.1.1 Connecting Crystal Resonator ............................................................................. 463 15.1.2 External Clock Input............................................................................................ 464 15.2 PLL Circuit ....................................................................................................................... 466 15.3 Usage Notes ...................................................................................................................... 467 15.3.1 Notes on Resonator.............................................................................................. 467 15.3.2 Notes on Board Design ........................................................................................ 467 15.3.3 Note on confirming the operation ........................................................................ 467
Section 16 Power-Down Modes........................................................................ 469
16.1 Register Descriptions........................................................................................................ 472 16.1.1 Standby Control Register (SBYCR) .................................................................... 472 16.1.2 Module Stop Control Registers H and L (MSTPCRH, MSTPCRL) ................... 473 16.2 Operation .......................................................................................................................... 474 16.2.1 Sleep Mode .......................................................................................................... 474 16.2.2 Software Standby Mode....................................................................................... 474 16.2.3 Hardware Standby Mode ..................................................................................... 476 16.2.4 Module Stop Mode .............................................................................................. 477 16.3 Usage Notes ...................................................................................................................... 478 16.3.1 I/O Port Status...................................................................................................... 478 16.3.2 Current Consumption during Oscillation Stabilization Standby Period .............. 478 16.3.3 On-Chip Peripheral Module Interrupts ................................................................ 478 16.3.4 Writing to MSTPCR ............................................................................................ 478
Section 17 List of Registers............................................................................... 479
17.1 Register Addresses (Address Order)................................................................................. 480 17.2 Register Bits...................................................................................................................... 485 17.3 Register States in Each Operating Mode .......................................................................... 493
Section 18 Electrical Characteristics ................................................................. 497
18.1 Absolute Maximum Ratings ............................................................................................. 497 18.2 DC Characteristics ............................................................................................................ 498 18.3 AC Characteristics ............................................................................................................ 501 18.3.1 Clock Timing ....................................................................................................... 501 18.3.2 Control Signal Timing ......................................................................................... 503
Rev. 2.00, 03/04, page xviii of xxxii
18.3.3 Bus Timing .......................................................................................................... 504 18.3.4 DMAC Timing..................................................................................................... 515 18.3.5 Timing of On-Chip Peripheral Modules .............................................................. 518 18.4 Flash Memory Characteristics .......................................................................................... 521 18.4.1 Flash Memory Characteristics ............................................................................. 521 18.5 Use Note (Internal Voltage Step Down) ........................................................................... 522
Appendix
A. B. C.
.........................................................................................................523
Port States in Each Processing State ................................................................................. 523 Product Lineup.................................................................................................................. 525 Package Dimensions ......................................................................................................... 526
Main Revisions and Additions in this Edition .....................................................527 Index .........................................................................................................531
Rev. 2.00, 03/04, page xix of xxxii
Rev. 2.00, 03/04, page xx of xxxii
Figures
Section 1 Overview Figure 1.1 Internal Block Diagram ................................................................................................. 2 Figure 1.2 Pin Arrangement (TFP-100B) ....................................................................................... 3 Section 2 CPU Figure 2.1 Exception Vector Table (Normal Mode)..................................................................... 17 Figure 2.2 Stack Structure in Normal Mode ................................................................................. 17 Figure 2.3 Exception Vector Table (Advanced Mode)................................................................. 18 Figure 2.4 Stack Structure in Advanced Mode ............................................................................. 19 Figure 2.5 Memory Map............................................................................................................... 20 Figure 2.6 CPU Internal Registers ................................................................................................ 21 Figure 2.7 Usage of General Registers ......................................................................................... 22 Figure 2.8 Stack............................................................................................................................ 23 Figure 2.9 General Register Data Formats (1).............................................................................. 26 Figure 2.9 General Register Data Formats (2).............................................................................. 27 Figure 2.10 Memory Data Formats............................................................................................... 28 Figure 2.11 Instruction Formats (Examples) ................................................................................ 40 Figure 2.12 Branch Address Specification in Memory Indirect Addressing Mode ...................... 43 Figure 2.13 State Transitions ........................................................................................................ 47 Section 3 MCU Operating Modes Figure 3.1 Address Map ............................................................................................................... 53 Section 4 Figure 4.1 Figure 4.2 Figure 4.3 Section 5 Figure 5.1 Figure 5.2 Figure 5.3 Figure 5.4 Figure 5.5 Figure 5.6 Figure 5.7 Figure 5.8 Exception Handling Reset Sequence............................................................................................................ 58 Stack Status after Exception Handling ........................................................................ 60 Operation when SP Value is Odd................................................................................ 61 Interrupt Controller Block Diagram of Interrupt Controller........................................................................ 63 Block Diagram of Interrupts IRQ7 to IRQ0 ................................................................ 69 Block Diagram of Interrupt Control Operation ........................................................... 72 Flowchart of Procedure up to Interrupt Acceptance in Interrupt Control Mode 0....... 75 State Transition in Interrupt Control Mode 1 .............................................................. 76 Flowchart of Procedure Up to Interrupt Acceptance in Interrupt Control Mode 1..... 78 Interrupt Exception Handling ...................................................................................... 79 Conflict between Interrupt Generation and Disabling................................................. 81
Section 6 Bus Controller (BSC) Figure 6.1 Block Diagram of Bus Controller................................................................................ 84 Figure 6.2 CS and Address Assertion Period Extension (Example of 3-State Access Space and RDNn = 0)..................................................... 89
Rev. 2.00, 03/04, page xxi of xxxii
Figure 6.3 Read Strobe Negation Timing (Example of 3-State Access Space) ............................ 93 Figure 6.4 RAS Signal Assertion Timing (2-State Column Address Output Cycle, Full Access)................................................. 97 Figure 6.5 Area Divisions........................................................................................................... 102 Figure 6.6 Address Format ......................................................................................................... 103 Figure 6.7 Address Map ............................................................................................................. 105 Figure 6.8 CSn Signal Output Timing (n = 3 to 0) ..................................................................... 108 Figure 6.9 Access Sizes and Data Alignment Control (8-Bit Access Space) ............................. 109 Figure 6.10 Access Sizes and Data Alignment Control (16-bit Access Space) .......................... 110 Figure 6.11 Bus Timing for 8-Bit, 2-State Access Space ........................................................... 111 Figure 6.12 Bus Timing for 8-Bit, 3-State Access Space ........................................................... 112 Figure 6.13 Bus Timing for 16-Bit, 2-State Access Space (Even Address Byte Access)........... 113 Figure 6.14 Bus Timing for 16-Bit, 2-State Access Space (Odd Address Byte Access)............ 114 Figure 6.15 Bus Timing for 16-Bit, 2-State Access Space (Word Access) ................................ 115 Figure 6.16 Bus Timing for 16-Bit, 3-State Access Space (Even Address Byte Access)........... 116 Figure 6.17 Bus Timing for 16-Bit, 3-State Access Space (Odd Address Byte Access)............ 117 Figure 6.18 Bus Timing for 16-Bit, 3-State Access Space (Word Access) ................................ 118 Figure 6.19 Example of Wait State Insertion Timing................................................................. 119 Figure 6.20 Example of Read Strobe Timing ............................................................................. 120 Figure 6.21 Example of Timing when Chip Select Assertion Period is Extended ..................... 121 Figure 6.22 DRAM Basic Access Timing (RAST = 0, CAST = 0)............................................ 124 Figure 6.23 Example of Access Timing with 3-State Column Address Output Cycle (RAST = 0).............................................................................................................. 125 Figure 6.24 Example of Access Timing when RAS Signal Goes Low from Beginning of Tr State (CAST = 0) ................................................................................................ 126 Figure 6.25 Example of Timing with One Row Address Output Hold State (RAST = 0, CAST = 0)........................................................................................... 127 Figure 6.26 Example of Timing with Two-State Precharge Cycle (RAST = 0, CAST = 0)....... 128 Figure 6.27 Example of Wait State Insertion Timing (2-State Column Address Output) .......... 129 Figure 6.28 Example of Wait State Insertion Timing (3-State Column Address Output) .......... 130 Figure 6.29 2-CAS Control Timing (Write Access to Even Address: RAST = 0, CAST = 0) ... 131 Figure 6.30 Example of 2-CAS DRAM Connection .................................................................. 132 Figure 6.31 Operation Timing in Fast Page Mode (RAST = 0, CAST = 0) ............................... 133 Figure 6.32 Operation Timing in Fast Page Mode (RAST = 0, CAST = 1) ............................... 133 Figure 6.33 Example of Operation Timing in RAS Down Mode (RAST = 0, CAST = 0)......... 135 Figure 6.34 Example of Idle Cycle Insertion when RAS Down Mode cannot be Continued..... 135 Figure 6.35 Example of Operation Timing in RAS Up Mode (RAST = 0, CAST = 0).............. 136 Figure 6.36 RTCNT Operation................................................................................................... 137 Figure 6.37 Compare Match Timing .......................................................................................... 138 Figure 6.38 CBR Refresh Timing............................................................................................... 138 Figure 6.39 CBR Refresh Timing (RCW1 = 0, RCW0 = 1, RLW1 = 0, RLW0 = 0)................. 138 Figure 6.40 Self-Refresh Timing ................................................................................................ 139
Rev. 2.00, 03/04, page xxii of xxxii
Figure 6.41 Example of Timing when Precharge Time after Self-Refreshing is Extended by 2 States................................................................................................................ 140 Figure 6.42 Example of DACK Output Timing when DDS = 1 (RAST = 0, CAST = 0) .......... 141 Figure 6.43 Example of DACK Output Timing when DDS = 0 (RAST = 0, CAST = 1) .......... 142 Figure 6.44 Example of Idle Cycle Operation (Consecutive Reads in Different Areas) ............ 143 Figure 6.45 Example of Idle Cycle Operation (Write after Read) .............................................. 144 Figure 6.46 Example of Idle Cycle Operation (Read after Write) .............................................. 145 Figure 6.47 Relationship between Chip Select (CS) and Read (RD).......................................... 145 Figure 6.48 Example of DRAM Full Access after External Read (CAST = 0) .......................... 146 Figure 6.49 Example of Idle Cycle Operation in RAS Down Mode (Consecutive Reads in Different Areas) (IDLE1 = 0, IDLE0 = 1, IDLC1 = 0, IDLC0 = 1, RAST = 0, and CAST = 0)........ 147 Figure 6.50 Example of Timing when Write Data Buffer Function is Used .............................. 150 Section 7 DMA Controller (DMAC) Figure 7.1 Block Diagram of DMAC ......................................................................................... 155 Figure 7.2 Example of Timing in Dual Address Mode............................................................... 173 Figure 7.3 Data Flow in Single Address Mode........................................................................... 174 Figure 7.4 Example of Timing in Single Address Mode ............................................................ 175 Figure 7.5 Example of Timing in Cycle Steal Mode .................................................................. 177 Figure 7.6 Examples of Timing in Burst Mode .......................................................................... 178 Figure 7.7 Examples of Timing in Normal Transfer Mode ........................................................ 178 Figure 7.8 Example of Timing in Block Transfer Mode ............................................................ 179 Figure 7.9 Example of Repeat Area Function Operation............................................................ 180 Figure 7.10 Example of Repeat Area Function Operation in Block Transfer Mode .................. 181 Figure 7.11 DMTCR Update Operations in Normal Transfer Mode and Block Transfer Mode............................................................................................... 184 Figure 7.12 Procedure for Changing Register Settings in Operating Channel ........................... 185 Figure 7.13 Example of Channel Priority Timing ...................................................................... 187 Figure 7.14 Examples of Channel Priority Timing..................................................................... 188 Figure 7.15 Example of Normal Transfer Mode (Cycle Steal Mode) Transfer .......................... 189 Figure 7.16 Example of Normal Transfer Mode (Burst Mode) Transfer.................................... 190 Figure 7.17 Example of Normal Transfer Mode (Cycle Steal Mode) Transfer (Transfer Source: USB) ........................................................................................... 190 Figure 7.18 Example of Normal Transfer Mode (Cycle Steal Mode) Transfer (Transfer Destination: USB).................................................................................... 191 Figure 7.19 Example of Block Transfer Mode (Cycle Steal Mode) Transfer............................. 191 Figure 7.20 Example of Normal Mode Transfer Activated by DREQ Pin Falling Edge............ 192 Figure 7.21 Example of Block Transfer Mode Transfer Activated by DREQ Pin Falling Edge............................................................................................................. 193 Figure 7.22 Example of Normal Mode Transfer Activated by DREQ Pin Low Level............... 194 Figure 7.23 Example of Block Transfer Mode Transfer Activated by DREQ Pin Low Level ... 195 Figure 7.24 Example of Single Address Mode (Byte Read) Transfer ........................................ 196
Rev. 2.00, 03/04, page xxiii of xxxii
Figure 7.25 Figure 7.26 Figure 7.27 Figure 7.28 Figure 7.29 Figure 7.30 Figure 7.31 Figure 7.32 Figure 7.33 Figure 7.34 Figure 7.35 Figure 7.36 Figure 7.37 Figure 7.38 Figure 7.39 Figure 7.40 Figure 7.41 Figure 7.42 Figure 7.43 Figure 7.44 Figure 7.45 Figure 7.46 Figure 7.47
Example of Single Address Mode (Word Read) Transfer....................................... 196 Example of Single Address Mode (Longword Read) Transfer ............................... 197 Example of Single Address Mode (Byte Write) Transfer ....................................... 197 Example of Single Address Mode (Word Write) Transfer...................................... 198 Example of Single Address Mode (Longword Write) Transfer .............................. 198 Example of Single Address Mode Transfer Activated by DREQ Pin Falling Edge ............................................................................................................ 199 Example of Single Address Mode Transfer Activated by DREQ Pin Low Level ............................................................................................................... 200 Auto Request/Cycle Steal Mode/Normal Transfer Mode (No Contention/Dual Address Mode)...................................................................... 201 Auto Request/Cycle Steal Mode/Normal Transfer Mode (CPU Cycles/Single Address Mode) ....................................................................... 202 Auto Request/Cycle Steal Mode/Normal Transfer Mode (Contention with Another Channel/Single Address Mode)..................................... 202 Auto Request/Burst Mode/Normal Transfer Mode (CPU Cycles/Dual Address Mode).......................................................................... 203 Auto Request/Burst Mode/Normal Transfer Mode (CPU Cycles/Single Address Mode) ....................................................................... 203 Auto Request/Burst Mode/Normal Transfer Mode (Contention with Another Channel/Single Address Mode)..................................... 204 External Request/Cycle Steal Mode/Normal Transfer Mode (No Contention/Dual Address Mode/Low Level Sensing)...................................... 205 External Request/Cycle Steal Mode/Normal Transfer Mode (CPU Cycles/Single Address Mode/Low Level Sensing) ....................................... 205 External Request/Cycle Steal Mode/Normal Transfer Mode (No Contention/Single Address Mode/Falling Edge Sensing) ................................ 206 External Request/Cycle Steal Mode/Normal Transfer Mode (Contention with Another Channel/Dual Address Mode/Low Level Sensing) ....... 206 External Request/Cycle Steal Mode/Block Transfer Mode (No Contention/Dual Address Mode/Low Level Sensing)...................................... 208 External Request/Cycle Steal Mode/Block Transfer Mode (No Contention/Single Address Mode/Falling Edge Sensing) ................................ 209 External Request/Cycle Steal Mode/Block Transfer Mode (CPU Cycles/Single Address Mode/Low Level Sensing) ....................................... 210 External Request/Cycle Steal Mode/Block Transfer Mode (Contention with Another Channel/Dual Address Mode/Low Level Sensing) ....... 211 Transfer End Interrupt Logic................................................................................... 214 Example of Procedure for Restarting Transfer on Channel in which Transfer End Interrupt Occurred ................................................................................................... 215
Rev. 2.00, 03/04, page xxiv of xxxii
Section 9 8-Bit Timer (TMR) Figure 9.1 Block Diagram of 8-Bit Timer Module..................................................................... 264 Figure 9.2 Example of Pulse Output........................................................................................... 270 Figure 9.3 Count Timing for Internal Clock Input...................................................................... 271 Figure 9.4 Count Timing for External Clock Input .................................................................... 271 Figure 9.5 Timing of CMF Setting ............................................................................................. 272 Figure 9.6 Timing of Timer Output ............................................................................................ 272 Figure 9.7 Timing of Compare Match Clear............................................................................... 273 Figure 9.8 Timing of Clearance by External Reset..................................................................... 273 Figure 9.9 Timing of OVF Setting.............................................................................................. 274 Figure 9.10 Contention between TCNT Write and Clear ........................................................... 276 Figure 9.11 Contention between TCNT Write and Increment.................................................... 277 Figure 9.12 Contention between TCOR Write and Compare Match.......................................... 278 Section 10 Figure 10.1 Figure 10.2 Figure 10.3 Figure 10.4 Figure 10.5 Figure 10.6 Figure 10.7 Watchdog Timer (WDT) Block Diagram of WDT .......................................................................................... 283 Watchdog Timer Mode (RST/NMI = 1) Operation................................................. 286 Interval Timer Mode Operation............................................................................... 287 OVF Flag Set Timing .............................................................................................. 287 Output Timing of OVF............................................................................................ 288 Writing to TCNT and TCSR ................................................................................... 289 Conflict between TCNT Write and Increment ........................................................ 290
Section 11 Serial Communication Interface for Boot Mode (SCI) Figure 11.1 Block Diagram of SCI............................................................................................. 292 Figure 11.2 Data Format in Asynchronous Communication (Example with 8-Bit Data, Parity, Two Stop Bits) .................................................. 304 Figure 11.3 Receive Data Sampling Timing in Asynchronous Mode ........................................ 306 Figure 11.4 Sample SCI Initialization Flowchart ....................................................................... 307 Figure 11.5 Example of Operation in Transmission in Asynchronous Mode (Example with 8-Bit Data, Parity, One Stop Bit) .................................................... 308 Figure 11.6 Sample Serial Transmission Flowchart ................................................................... 309 Figure 11.7 Example of SCI Operation in Reception (Example with 8-Bit Data, Parity, One Stop Bit) .................................................... 310 Figure 11.8 Sample Serial Reception Data Flowchart (1) .......................................................... 312 Figure 11.8 Sample Serial Reception Data Flowchart (2) .......................................................... 313 Figure 11.9 Sample Flowchart for Mode Transition during Transmission................................. 316 Figure 11.10 Sample Flowchart for Mode Transition during Reception .................................... 317 Section 12 Figure 12.1 Figure 12.2 Figure 12.3 Figure 12.4 Universal Serial Bus 2 (USB2) Block Diagram of USB2 ......................................................................................... 320 USB Cable Connection ........................................................................................... 341 USB Cable Disconnection....................................................................................... 342 Control Transfer Stage Configuration ..................................................................... 343
Rev. 2.00, 03/04, page xxv of xxxii
Figure 12.5 Setup Stage Operation ............................................................................................. 344 Figure 12.6 Data Stage Operation (Control-In) .......................................................................... 345 Figure 12.7 Data Stage Operation (Control-Out) ....................................................................... 346 Figure 12.8 Status Stage Operation (Control-In)........................................................................ 347 Figure 12.9 Status Stage Operation (Control-Out) ..................................................................... 348 Figure 12.10 EP1 Bulk-Out Transfer Operation......................................................................... 350 Figure 12.11 EP2 Bulk-In Transfer Operation ........................................................................... 352 Figure 12.12 EP3 Interrupt-In Transfer Operation ..................................................................... 353 Figure 12.13 Forcible Stall by Firmware.................................................................................... 356 Figure 12.14 Automatic Stall by USB Function Module............................................................ 357 Figure 12.15 PKTE2 Operation for EP2..................................................................................... 359 Figure 12.16 Enter/Recover Sequence of USB Suspend State ................................................... 360 Figure 12.17 Enter/Recover Sequence of USB Suspend State and Software Standby Mode..... 362 Figure 12.18 Connection Example of External Circuit............................................................... 367 Figure 12.19 Bus Reset Following Completion of First Bus Reset ............................................ 368 Figure 12.20 Bus Reset Detection Flow ..................................................................................... 369 Section 14 Flash Memory (0.18-µm F-ZTAT Version) Figure 14.1 Block Diagram of Flash Memory............................................................................ 374 Figure 14.2 Mode Transition of Flash Memory.......................................................................... 375 Figure 14.3 Flash Memory Configuration .................................................................................. 377 Figure 14.4 Block Division of User MAT.................................................................................. 378 Figure 14.5 Overview of User Procedure Program .................................................................... 379 Figure 14.6 System Configuration in Boot Mode....................................................................... 402 Figure 14.7 Automatic-Bit-Rate Adjustment Operation of SCI ................................................. 402 Figure 14.8 Overview of Boot Mode State Transition Diagram................................................. 404 Figure 14.9 Programming/Erasing Overview Flow.................................................................... 405 Figure 14.10 RAM Map When Programming/Erasing is Executed ........................................... 406 Figure 14.11 Programming Procedure........................................................................................ 407 Figure 14.12 Erasing Procedure ................................................................................................. 412 Figure 14.13 Repeating Procedure of Erasing and Programming............................................... 414 Figure 14.14 Procedure for Programming User MAT in User Boot Mode ................................ 416 Figure 14.15 Procedure for Erasing User MAT in User Boot Mode .......................................... 417 Figure 14.16 Transitions to Error-Protection State..................................................................... 430 Figure 14.17 Switching between the User MAT and User Boot MAT ...................................... 431 Figure 14.18 Flowchart for Flash Memory Emulation in RAM ................................................. 432 Figure 14.19 Example of RAM Overlap Operation (256-kbyte Flash Memory)........................ 433 Figure 14.20 Memory Map in Programmer Mode...................................................................... 434 Figure 14.21 Boot Program States.............................................................................................. 436 Figure 14.22 Bit-Rate-Adjustment Sequence ............................................................................. 437 Figure 14.23 Communication Protocol Format .......................................................................... 438 Figure 14.24 New Bit-Rate Selection Sequence......................................................................... 448 Figure 14.25 Programming Sequence......................................................................................... 451
Rev. 2.00, 03/04, page xxvi of xxxii
Figure 14.26 Erasure Sequence .................................................................................................. 454 Section 15 Figure 15.1 Figure 15.2 Figure 15.3 Figure 15.4 Figure 15.5 Figure 15.6 Figure 15.7 Section 16 Figure 16.1 Figure 16.2 Figure 16.3 Clock Pulse Generator Block Diagram of Clock Pulse Generator ............................................................... 463 Connection of Crystal Resonator (Example)........................................................... 464 Crystal Resonator Equivalent Circuit ...................................................................... 464 External Clock Input (Examples) ............................................................................ 465 External Clock Input Timing................................................................................... 465 Timing of External Clock Output Stabilization Delay Time ................................... 466 Note on Board Design for Oscillation Circuit ......................................................... 467 Power-Down Modes Mode Transitions..................................................................................................... 471 Software Standby Mode Application Example ....................................................... 476 Hardware Standby Mode Timing ............................................................................ 477
Section 18 Electrical Characteristics Figure 18.1 Sample of Dalington Transistor Drive Circuit......................................................... 500 Figure 18.2 Output Load Circuit................................................................................................. 501 Figure 18.3 System Clock Timing .............................................................................................. 502 Figure 18.4 Oscillation Stabilization Timing (1) ........................................................................ 502 Figure 18.5 Oscillation Stabilization Timing (2) ........................................................................ 502 Figure 18.6 Reset Input Timing.................................................................................................. 503 Figure 18.7 Interrupt Input Timing............................................................................................. 503 Figure 18.8 Basic Bus Timing: Two-State Access ..................................................................... 506 Figure 18.9 Basic Bus Timing: Three-State Access ................................................................... 507 Figure 18.10 Basic Bus Timing: Two-State Access (CS Assertion Period Extended) ............... 508 Figure 18.11 Basic Bus Timing: Three-State Access (CS Assertion Period Extended) ............. 509 Figure 18.12 DRAM Access Timing: Two-State Access ........................................................... 510 Figure 18.13 DRAM Access Timing: Two-State Burst Access ................................................. 511 Figure 18.14 DRAM Access Timing: Three-State Access (RAST = 1) ..................................... 512 Figure 18.15 DRAM Access Timing: Three-State Burst Access ............................................... 513 Figure 18.16 CAS-Before-RAS Refresh Timing......................................................................... 514 Figure 18.17 CAS-Before-RAS Refresh Timing (with Wait Cycle Insertion) ........................... 514 Figure 18.18 Self-Refresh Timing (Return from Software Standby Mode: RAST = 0) ............. 514 Figure 18.19 Self-Refresh Timing (Return from Software Standby Mode: RAST = 1) ............. 515 Figure 18.20 DMAC Single Address Transfer Timing: Two-State Access................................ 516 Figure 18.21 DMAC Single Address Transfer Timing: Three-State Access.............................. 517 Figure 18.22 DMAC, TEND Output Timing.............................................................................. 517 Figure 18.23 DMAC, DREQ Input Timing ................................................................................ 518 Figure 18.24 I/O Port Input/Output Timing................................................................................ 519 Figure 18.25 8-Bit Timer Output Timing ................................................................................... 519 Figure 18.26 8-Bit Timer Clock Input Timing ........................................................................... 519 Figure 18.27 8-Bit Timer Reset Input Timing ............................................................................ 519
Rev. 2.00, 03/04, page xxvii of xxxii
Figure 18.28 USB2 Input/output Timing.................................................................................... 520 Figure 18.29 VCL Capacitor Connection Method...................................................................... 522 Appendix Figure C.1 Package Dimensions (TFP-100B) ............................................................................ 526
Rev. 2.00, 03/04, page xxviii of xxxii
Tables
Section 1 Overview Table 1.1 Pin Arrangements in Each Mode............................................................................. 4 Table 1.2 Pin Functions........................................................................................................... 8 Section 2 CPU Table 2.1 Instruction Classification....................................................................................... 29 Table 2.2 Operation Notation ................................................................................................ 30 Table 2.3 Data Transfer Instructions ..................................................................................... 31 Table 2.4 Arithmetic Operations Instructions (1).................................................................. 32 Table 2.4 Arithmetic Operations Instructions (2).................................................................. 33 Table 2.5 Logic Operations Instructions ............................................................................... 34 Table 2.6 Shift Instructions ................................................................................................... 34 Table 2.7 Bit Manipulation Instructions (1) .......................................................................... 35 Table 2.7 Bit Manipulation Instructions (2) .......................................................................... 36 Table 2.8 Branch Instructions................................................................................................ 37 Table 2.9 System Control Instructions .................................................................................. 38 Table 2.10 Block Data Transfer Instructions........................................................................... 39 Table 2.11 Addressing Modes................................................................................................. 40 Table 2.12 Absolute Address Access Ranges ......................................................................... 42 Table 2.13 Effective Address Calculation (1) ......................................................................... 44 Table 2.13 Effective Address Calculation (2) ......................................................................... 45 Section 3 MCU Operating Modes Table 3.1 MCU Operating Mode Selection........................................................................... 49 Table 3.2 Pin Functions in Operating Mode 2....................................................................... 52 Section 4 Exception Handling Table 4.1 Exception Types and Priority ................................................................................ 55 Table 4.2 Exception Handling Vector Table ......................................................................... 56 Table 4.3 Status of CCR after Trap Instruction Exception Handling .................................... 59 Section 5 Interrupt Controller Table 5.1 Pin Configuration .................................................................................................. 64 Table 5.2 Correspondence between Interrupt Source and ICR ............................................. 65 Table 5.3 Interrupt Sources, Vector Addresses, and Interrupt Priorities ............................... 70 Table 5.4 Interrupt Control Modes........................................................................................ 72 Table 5.5 Interrupts Acceptable in Each Interrupt Control Mode ......................................... 73 Table 5.6 Operations and Control Signal Functions in Each Interrupt Control Mode .......... 73 Table 5.7 Interrupt Response Times...................................................................................... 80 Table 5.8 Number of States in Interrupt Handling Routine Execution Status....................... 80
Rev. 2.00, 03/04, page xxix of xxxii
Section 6 Bus Controller (BSC) Table 6.1 Pin Configuration .................................................................................................. 85 Table 6.2 Address Map ....................................................................................................... 104 Table 6.3 Bus Specifications for Each Area (Basic Bus Interface) ..................................... 106 Table 6.4 Data Buses Used and Valid Strobes .................................................................... 110 Table 6.5 Relation between Settings of Bits MXC2 to MXC0 and Address Multiplexing ......................................................................................... 122 Table 6.6 DRAM Interface Pins.......................................................................................... 123 Table 6.7 Idle Cycles in Mixed Accesses to Normal Space and DRAM Space.................. 148 Table 6.8 Pin States in Idle Cycle ....................................................................................... 149 Section 7 DMA Controller (DMAC) Table 7.1 Pin Configuration ................................................................................................ 156 Table 7.2 DMAC Transfer Modes ...................................................................................... 171 Table 7.3 DMAC Channel Priority ..................................................................................... 186 Table 7.4 Interrupt Sources and Priority Order ................................................................... 213 Section 8 I/O Ports Table 8.1 Port Functions ..................................................................................................... 220 Section 9 8-Bit Timer (TMR) Table 9.1 Pin Configuration ................................................................................................ 265 Table 9.2 Clock Input to TCNT and Count Condition ........................................................ 268 Table 9.3 8-Bit Timer Interrupt Sources ............................................................................. 275 Table 9.4 Timer Output Priorities ....................................................................................... 279 Table 9.5 Switching of Internal Clock and TCNT Operation ............................................. 280 Section 10 Watchdog Timer (WDT) Table 10.1 WDT Interrupt Source......................................................................................... 288 Section 11 Serial Communication Interface for Boot Mode (SCI) Table 11.1 Pin Configuration ................................................................................................ 292 Table 11.2 Relationships between N Setting in BRR and Bit Rate B ................................... 300 Table 11.3 BRR Settings for Various Bit Rates (Asynchronous Mode) (1).......................... 301 Table 11.3 BRR Settings for Various Bit Rates (Asynchronous Mode) (2).......................... 302 Table 11.4 Maximum Bit Rate for Each Frequency (Asynchronous Mode)......................... 303 Table 11.5 Serial Transfer Formats (Asynchronous Mode) .................................................. 305 Table 11.6 SSR Status Flags and Receive Data Handling..................................................... 311 Table 11.7 SCI Interrupt Sources .......................................................................................... 314 Section 12 Universal Serial Bus 2 (USB2) Table 12.1 Input/Output Signals ........................................................................................... 321 Table 12.2 Request Decoding by Firmware .......................................................................... 354 Table 12.3 Tree Configuration .............................................................................................. 358 Table 12.4 FIFO Size in Each Transfer Mode ...................................................................... 366
Rev. 2.00, 03/04, page xxx of xxxii
Section 14 Flash Memory (0.18-µm F-ZTAT Version) Table 14.1 Comparison of Programming Modes .................................................................. 376 Table 14.2 Pin Configuration ................................................................................................ 381 Table 14.3 Register/Parameter and Target Mode .................................................................. 382 Table 14.4 Flash Memory Area Divisions............................................................................. 391 Table 14.5 Parameters and Target Modes ............................................................................. 392 Table 14.6 Setting On-Board Programming Mode................................................................ 401 Table 14.7 System Clock Frequency for Automatic-Bit-Rate Adjustment by This LSI ....... 403 Table 14.8 Executable MAT ................................................................................................. 419 Table 14.9 (1) Useable Area for Programming in User Program Mode ..................................... 420 Table 14.9 (2) Useable Area for Erasure in User Program Mode ............................................... 422 Table 14.9 (3) Useable Area for Programming in User Boot Mode ........................................... 424 Table 14.9 (4) Useable Area for Erasure in User Boot Mode ..................................................... 426 Table 14.10 Hardware Protection............................................................................................ 428 Table 14.11 Software Protection ............................................................................................. 429 Table 14.12 Inquiry and Selection Commands ....................................................................... 439 Table 14.13 Programming/Erasing Command ........................................................................ 450 Table 14.14 Status Code.......................................................................................................... 459 Table 14.15 Error Code ........................................................................................................... 460 Section 15 Clock Pulse Generator Table 15.1 Damping Resistance Value.................................................................................. 464 Table 15.2 Crystal Resonator Characteristics........................................................................ 464 Table 15.3 External Clock Input Conditions ......................................................................... 465 Table 15.4 External Clock Output Stabilization Delay Time ................................................ 466 Section 16 Power-Down Modes Table 16.1 Operating Modes and Internal States of LSI ....................................................... 470 Table 16.2 Operating Frequency and Standby Time ............................................................. 475 Section 18 Electrical Characteristics Table 18.1 Absolute Maximum Ratings................................................................................ 497 Table 18.2 DC Characteristics (1) ......................................................................................... 498 Table 18.3 DC Characteristics (2) ......................................................................................... 499 Table 18.4 Permissible Output Currents................................................................................ 500 Table 18.5 Clock Timing....................................................................................................... 501 Table 18.6 Control Signal Timing......................................................................................... 503 Table 18.7 Bus Timing (1) .................................................................................................... 504 Table 18.8 Bus Timing (2) .................................................................................................... 505 Table 18.9 DMAC Timing .................................................................................................... 515 Table 18.10 Timing of On-Chip Peripheral Modules.............................................................. 518 Table 18.11 Flash Memory Characteristics............................................................................. 521
Rev. 2.00, 03/04, page xxxi of xxxii
Rev. 2.00, 03/04, page xxxii of xxxii
Section 1 Overview
1.1 Features
• High-speed H8S/2000 CPU with an internal 16-bit architecture Upward-compatible with H8/300 and H8/300H CPUs on an object level Sixteen 16-bit general registers 65 basic instructions • Various peripheral functions DMA controller (DMAC) 8-bit timer (TMR) Watchdog timer (WDT) Serial communication interface (SCI) Universal serial bus 2 (USB2) Clock pulse generator • On-chip memory
ROM Type Flash memory version Model HD64F2170 ROM 256 kbytes RAM 32 kbytes Remarks
• General I/O ports I/O pins: 76 • Supports various power-down states • Compact package
Package TQFP-100 (Code) TFP-100B Body Size 14.0 × 14.0 mm Pin Pitch 0.5 mm Remarks
Rev. 2.00, 03/04, page 1 of 534
1.2
Internal Block Diagram
Figure 1.1 shows the internal block diagram.
VCL VCC VCC VCC VCC VSS VSS VSS VSS VSS
NMI HUDITCK RxD0/HUDITDI TxD0/HUDITDO HUDIMS
32-bit internal address bus
32-bit internal data bus
ROM (flash memory)
Interrupt controller
Port 1
MD1 FWE EXTAL XTAL
PLL H8S/2000 CPU Clock pulse generator
16-bit internal address bus
16-bit internal data bus
P17/USD15 P16/USD14 P15/USD13 P14/USD12 P13/USD11 P12/USD10 P11/USD9 P10/USD8 P27/USD7/ P26/USD6/ P25/USD5/ P24/USD4/ P23/USD3/ P22/USD2/ P21/USD1/ P20/USD0/ P37/USOPM1 P36/USOPM0 P35/( )/USVBUS P34/( )/USTXV P33/USLSTA1 P32/USLSTA0 P31/USCLK P30/USWDVLD P47/USXCVRS P46/USTXRDY P45/USTSEL P44/ P43/USRXV P42/USRXERR P41/USRXACT P40/
PA3/A19/ PA2/A18/ PA1/A17/ /( PA0/A16/(
RAM
) )
Port A
P87/D15 P86/D14 P85/D13 P84/D12 P83/D11 P82/D10 P81/D9 P80/D8
SCI
32-bit internal address bus
P97/φ P96/ P95/ P94/ P93/ P92/ / P91/ P90/
DMAC
Port 9
WDT
USB2.0 interface
32-bit internal data bus
Port 8
8-bit timer
Port 7
Port 6
Port 5
P67/A15 P66/A14/TMO1 P65/A13/TMRI1 P64/A12/TMCI1 P63/A11 P62/A10/TMO0 P61/A9/TMRI0 P60/A8/TMCI0
P77/A7/ P76/A6/ P75/A5/ P74/A4/ P73/A3/ P72/A2/ P71/A1/ P70/A0/
Figure 1.1 Internal Block Diagram
Rev. 2.00, 03/04, page 2 of 534
P57/D7/( )/ P56/D6/( )/ P55/D5/ P54/D4/ P53/D3/( )/ P52/D2/( )/ P51/D1/ P50/D0/
Port 4
Port 3
Port 2
Bus controller
1.3
1.3.1
Pin Description
Pin Arrangement
Figure 1.2 shows the pin arrangement.
P73/A3/ P74/A4/ P75/A5/ P76/A6/ P77/A7/ VSS HUDITDO/TxD0 VCC HUDITMS P60/A8/TMCI0 P61/A9/TMRI0 P62/A10/TMO0 P63/A11 P64/A12/TMCI1 P65/A13/TMRI1 P66/A14/TMO1 P67/A15 P47/USXCVRS P46/USTXRDY P45/USTSEL P44/ P43/USRXV P42/USRXERR P41/USRXACT P40/
P72/A2/ P71/A1/ P70/A0/ P87/D15 P86/D14 P85/D13 P84/D12 P83/D11 P82/D10 P81/D9 P80/D8 VCC FWE VSS )/ P57/D7/( P56/D6/( )/ P55/D5/ P54/D4/ P53/D3/( )/ P52/D2/( )/ P51/D1/ P50/D0/ PA0/A16/( PA1/A17/ /( 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51
50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26
TFP-100B (Top view)
) )
Figure 1.2 Pin Arrangement (TFP-100B)
VSS EXTAL XTAL VCC P97/φ P96/ P95/ P94/ P93/ P92/ / P91/ P90/ P30/USWDVLD P31/USCLK P32/USLSTA0
MD1 NC NMI VSS
PA2/A18/ PA3/A19/
VCL
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
P17/USD15 P16/USD14 P15/USD13 P14/USD12 P13/USD11 P12/USD10 P11/USD9 P10/USD8 VCC HUDITCK VSS HUDITDI/RxD0 P27/USD7/ P26/USD6/ P25/USD5/ P24/USD4/ P23/USD3/ P22/USD2/ P21/USD1/ P20/USD0/ P37/USOPM1 P36/USOPM0 )/USVBUS P35/( )/USTXV P34/( P33/USLSTA1
Rev. 2.00, 03/04, page 3 of 534
1.3.2
Pin Arrangements in Each Mode
Table 1.1 lists the pin arrangements in each mode. Table 1.1
Pin No. TFP100B 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
Pin Arrangements in Each Mode
Pin Name Extended Mode (EXPE = 1) PA2/A18/UCAS PA3/A19/CS3 MD2 MD1 NC NMI VSS STBY VCL RES VSS EXTAL XTAL VCC P97/φ P96/AS P95/RD P94/HWR P93/LWR P92/CS2/RAS P91/CS1 P90/CS0 P30/USWDVLD P31/USCLK P32/USLSTA0 P33/USLSTA1 P34/(IRQ4)/USTXV Single-Chip Mode (EXPE = 0) PA2 PA3 MD2 MD1 NC NMI VSS STBY VCL RES VSS EXTAL XTAL VCC P97/φ P96 P95 P94 P93 P92 P91 P90 P30/USWDVLD P31/USCLK P32/USLSTA0 P33/USLSTA1 P34/(IRQ4)/USTXV Flash Memory Programmer Mode NC NC VSS VSS NC NC VSS VCC VCL RES VSS EXTAL XTAL VCC NC NC NC NC NC NC NC NC NC NC NC NC NC
Rev. 2.00, 03/04, page 4 of 534
Pin No. TFP100B 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 53 54 55 56 57 58 59
Pin Name Extended Mode (EXPE = 1) P35/(IRQ5)/USVBUS P36/USOPM0 P37/USOPM1 P20/USD0/DREQ0 P21/USD1/TEND0 P22/USD2/DACK0 P23/USD3/DRAK0 P24/USD4/DREQ1 P25/USD5/TEND1 P26/USD6/DACK1 P27/USD7/DRAK1 HUDITDI/RxD0 VSS HUDITCK VCC P10/USD8 P11/USD9 P12/USD10 P13/USD11 P14/USD12 P15/USD13 P16/USD14 P17/USD15 P40/USRST P41/USRXACT P42/USRXERR P43/USRXV P44/USSUSP P45/USTSEL P46/USTXRDY P47/USXCVRS P67/A15 Single-Chip Mode (EXPE = 0) P35/(IRQ5)/USVBUS P36/USOPM0 P37/USOPM1 P20/USD0/DREQ0 P21/USD1/TEND0 P22/USD2/DACK0 P23/USD3/DRAK0 P24/USD4/DREQ1 P25/USD5/TEND1 P26/USD6/DACK1 P27/USD7/DRAK1 HUDITDI/RxD0 VSS HUDITCK VCC P10/USD8 P11/USD9 P12/USD10 P13/USD11 P14/USD12 P15/USD13 P16/USD14 P17/USD15 P40/USRST P41/USRXACT P42/USRXERR P43/USRXV P44/USSUSP P45/USTSEL P46/USTXRDY P47/USXCVRS P67 Flash Memory Programmer Mode NC NC NC NC NC NC NC NC NC NC NC NC VSS NC VCC NC NC NC NC NC NC NC NC NC NC NC NC NC NC NC NC NC
Rev. 2.00, 03/04, page 5 of 534
Pin No. TFP100B 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91
Pin Name Extended Mode (EXPE = 1) P66/A14/TMO1 P65/A13/TMRI1 P64/A12/TMCI1 P63/A11 P62/A10/TMO0 P61/A9/TMRI0 P60/A8/TMCI0 HUDITMS VCC HUDITDO/TxD0 VSS P77/A7/IRQ7 P76/A6/IRQ6 P75/A5/IRQ5 P74/A4/IRQ4 P73/A3/IRQ3 P72/A2/IRQ2 P71/A1/IRQ1 P70/A0/IRQ0 P87/D15 P86/D14 P85/D13 P84/D12 P83/D11 P82/D10 P81/D9 P80/D8 VCC FWE HUDITRST VSS Single-Chip Mode (EXPE = 0) P66/TMO1 P65/TMRI1 P64/TMCI1 P63 P62/TMO0 P61/TMRI0 P60/TMCI0 HUDITMS VCC HUDITDO/TxD0 VSS P77/IRQ7 P76/IRQ6 P75/IRQ5 P74/IRQ4 P73/IRQ3 P72/IRQ2 P71/IRQ1 P70/IRQ0 P87 P86 P85 P84 P83 P82 P81 P80 VCC FWE HUDITRST VSS Flash Memory Programmer Mode NC NC NC NC NC NC NC NC VCC NC VSS NC NC NC NC NC NC NC NC NC NC NC NC NC NC NC NC VCC FWE NC VSS NC
P57/D7/(IRQ7)/MSSRAC/DRAK3 P57/(IRQ7)/MSSRAC/DRAK3
Rev. 2.00, 03/04, page 6 of 534
Pin No. TFP100B 92 93 94 95 96 97 98 99 100
Pin Name Extended Mode (EXPE = 1) P56/D6/(IRQ6)/DACK3 P55/D5/MSBS/TEND3 P54/D4/MSDIO3/DREQ3 Single-Chip Mode (EXPE = 0) P56/(IRQ6)/DACK3 P55/MSBS/TEND3 P54/MSDIO3/DREQ3 Flash Memory Programmer Mode NC NC NC NC NC NC NC NC NC
P53/D3/(IRQ3)/MSDIO2/DRAK2 P53/(IRQ3)/MSDIO2/DRAK2 P52/D2/(IRQ2)/MSDIO1/DACK2 P52/(IRQ2)/MSDIO1/DACK2 P51/D1/MSDIO0/TEND2 P50/D0/MSCLK/DREQ2 PA0/A16/(IRQ0) PA1/A17/LCAS/(IRQ1) P51/MSDIO0/TEND2 P50/MSCLK/DREQ2 PA0/(IRQ0) PA1/LCAS/(IRQ1)
Rev. 2.00, 03/04, page 7 of 534
1.3.3
Pin Functions
Table 1.2 lists the pin functions. Table 1.2
Type Power
Pin Functions
Symbol VCC VSS VCL Pin No. 14, 42, 68, 87 I/O Input Function For connection to the power supply. VCC pins should be connected to the system power supply. For connection to ground. VSS pins should be connected to the system power supply (0 V).
7, 11, 40, Input 70, 90 9
Output The VCL is an external capacity pin for internal stepdown power. Connect this pin to VSS through the external capacitor to stabilize the internal step-down power. Input For connection to a crystal resonator. See section 15, Clock Pulse Generator for typical connection diagrams for a crystal resonator and external clock input. For connection to a crystal resonator. The EXTAL pin can also input an external clock. See section 15, Clock Pulse Generator for typical connection diagrams for a crystal resonator and external clock input.
Clock
XTAL
13
EXTAL
12
Input
φ Operating MD2 mode control MD1 System control RES STBY FWE
15 3 4 10 8 88
Output Supplies the system clock to external devices. Input Input Input Input These pins set the operating mode. These pins should not be changed while the MCU is operating. Reset pin. When this pin is driven low, the chip is reset. When this pin is driven low, a transition is made to hardware standby mode. This pin is only for the flash memory. This pin is available only in the flash memory version.
Rev. 2.00, 03/04, page 8 of 534
Type Interrupt signals
Symbol NMI IRQ7 to IRQ0
Pin No. 6 71 to 78
I/O Input Input
Function Nonmaskable interrupt request pin. Fix high when not used. These pins request a maskable interrupt. The IRQ sense port select register (ISSR) selects whether the signal is input from the IRQn or (IRQn). (n = 7 to 0)
(IRQ7) to (IRQ0)
91, 92, 28, 27, 95, 96, 99, 100
Input
Address bus A19 A18 A17 A16 A15 to A8 A7 to A0 Data bus Bus control
2, Output These pins output an address. 1, 100, 99, 59 to 66, 71 to 78 These pins constitute a bidirectional data bus.
D15 to D8, 79 to 86, Input/ D7 to D0 91 to 98 output CS3 CS2/ RAS CS1 CS0 AS RD HWR 2 20 21 22 16 17 18
Output Strobe signal indicating that area 3 is selected. Output Strobe signal indicating that area 2 is selected. Row address strobe signal for the DRAM. Output Strobe signal indicating that area 1 is selected. Output Strobe signal indicating that area 0 is selected. Output When this pin is low, it indicates that address output on the address bus is valid. Output When this pin is low, it indicates that the normal space is being read. Output Strobe signal indicating that normal space is to be written, and the upper half (D15 to D8) of the data bus is enabled. Output Strobe signal indicating that normal space is to be written, and the lower half (D7 to D0) of the data bus is enabled. Output Upper column address strobe signal for accessing the 16-bit DRAM space or column address strobe signal for accessing the 8-bit DRAM space. Output Lower column address strobe signal for accessing the 16-bit DRAM space.
LWR
19
UCAS
1
LCAS
100
Rev. 2.00, 03/04, page 9 of 534
Type DMA controller (DMAC)
Symbol DREQ3 DREQ2 DREQ1 DREQ0 DACK3 DACK2 DACK1 DACK0 TEND3 TEND2 TEND1 TEND0 DRAK3 DRAK2 DRAK1 DRAK0
Pin No. 94, 98, 35, 31 92 96 37 33 93, 97, 36, 32 91, 95, 38, 34 60, 64 62, 66 61, 65 69 39
I/O Input
Function These signals request DMAC activation for channels 3 to 0.
Output DMAC single address transfer acknowledge signals for channels 3 to 0.
Output These signals indicate the end of DMAC data transfer for channels 3 to 0.
Output These signals notify DMAC external request acknowledge and execution start for channels 3 to 0 to external devices. Output Compare match output pins. Input Input External clock input pins to counters. Counter reset input pins.
8-bit timer (TMR)
TMO1 TMO0 TMCI1 TMCI0 TMRI1 TMRI0
Serial TxD0 communicati- RxD0 on interface for boot mode (SCI) Universal serial bus 2 (USB2) USCLK USVBUS USLSTA0 USLSTA1
Output Data output pin. Input Data input pin.
23 28 25 26
Input Input Input Input Input Input Input Input Input/ output
USB clock. Input pin for connection/disconnection detection of USB cable. Input signal pins from USB2.0 transceiver.
USRXACT 52 USRXERR 53 USRXV 54
USTXRDY 57 USWDVLD 23 USOPM0 USOPM1 29 30
Output Output signal pins for USB2.0 transceiver. Output
Rev. 2.00, 03/04, page 10 of 534
Type Universal serial bus 2 (USB2)
Symbol USRST USTXV USSUSP USTSEL
Pin No. 51 27 55 56
I/O
Function
Output Output signal pins for USB2.0 transceiver. Output Output Output Output Data input/output.
USXCVRS 58 USD15 to USD8 USD7 to USD0 I/O ports
50 to 43, Input/ 38 to 31 output
P17 to P10 50 to 43 P27 to P20 38 to 31 P37 to P30 30 to 23 P47 to P40 58 to 51 P57 to P50 91 to 98 P67 to P60 59 to 66 P77 to P70 71 to 78 P87 to P80 79 to 86 P97 to P90 15 to 22 PA3 PA2 PA1 PA0 2, 1, 100, 99
Input/ output Input/ output Input/ output Input/ output Input/ output Input/ output Input/ output Input/ output Input/ output Input/ output
Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Eight-bit input/output pins. Four-bit input/output pins.
Rev. 2.00, 03/04, page 11 of 534
Rev. 2.00, 03/04, page 12 of 534
Section 2 CPU
The H8S/2000 CPU is a high-speed central processing unit with an internal 32-bit architecture that is upward-compatible with the H8/300 and H8/300H CPUs. The H8S/2000 CPU has sixteen 16-bit general registers, can address a 16-Mbyte linear address space, and is ideal for realtime control. This section describes the H8S/2000 CPU. The usable modes and address spaces differ depending on the product. For details on each product, refer to section 3, MCU Operating Modes.
2.1
Features
• Upward-compatibility with H8/300 and H8/300H CPUs Can execute H8/300 and H8/300H CPU object programs • General-register architecture Sixteen 16-bit general registers also usable as sixteen 8-bit registers or eight 32-bit registers • Sixty-five basic instructions 8/16/32-bit arithmetic and logic instructions Multiply and divide instructions Powerful bit-manipulation instructions • Eight addressing modes Register direct [Rn] Register indirect [@ERn] Register indirect with displacement [@(d:16,ERn) or @(d:32,ERn)] Register indirect with post-increment or pre-decrement [@ERn+ or @–ERn] Absolute address [@aa:8, @aa:16, @aa:24, or @aa:32] Immediate [#xx:8, #xx:16, or #xx:32] Program-counter relative [@(d:8,PC) or @(d:16,PC)] Memory indirect [@@aa:8] • 16-Mbyte address space Program: 16 Mbytes Data: 16 Mbytes • High-speed operation All frequently-used instructions are executed in one or two states 8/16/32-bit register-register add/subtract: 1 state 8 × 8-bit register-register multiply: 12 states (MULXU.B), 13 states (MULXS.B) 16 ÷ 8-bit register-register divide: 12 states (DIVXU.B) 16 × 16-bit register-register multiply: 20 states (MULXU.W), 21 states (MULXS.W) 32 ÷ 16-bit register-register divide: 20 states (DIVXU.W)
Rev. 2.00, 03/04, page 13 of 534
• Two CPU operating modes Normal mode* Advanced mode Note: For this LSI, normal mode is not available. • Power-down state Transition to power-down state by SLEEP instruction 2.1.1 Differences between H8S/2600 CPU and H8S/2000 CPU
The differences between the H8S/2600 CPU and the H8S/2000 CPU are as shown below. • Register configuration The MAC register is supported only by the H8S/2600 CPU. • Basic instructions The four instructions MAC, CLRMAC, LDMAC, and STMAC are supported only by the H8S/2600 CPU. • The number of execution states of the MULXU and MULXS instructions
Execution States Instruction MULXU Mnemonic MULXU.B Rs, Rd MULXU.W Rs, ERd MULXS MULXS.B Rs, Rd MULXS.W Rs, ERd H8S/2600 3 4 4 5 H8S/2000 12 20 13 21
In addition, there are differences in address space, CCR and EXR register functions, power-down modes, etc., depending on the model.
Rev. 2.00, 03/04, page 14 of 534
2.1.2
Differences from H8/300 CPU
In comparison to the H8/300 CPU, the H8S/2000 CPU has the following enhancements. • More general registers and control registers Eight 16-bit extended registers, and one 8-bit and two 32-bit control registers, have been added. • Expanded address space Normal mode supports the same 64-kbyte address space as the H8/300 CPU. Advanced mode supports a maximum 16-Mbyte address space. • Enhanced addressing The addressing modes have been enhanced to make effective use of the 16-Mbyte address space. • Enhanced instructions Addressing modes of bit-manipulation instructions have been enhanced. Signed multiply and divide instructions have been added. Two-bit shift and two-bit rotate instructions have been added. Instructions for saving and restoring multiple registers have been added. A test and set instruction has been added. • Higher speed Basic instructions are executed twice as fast. 2.1.3 Differences from H8/300H CPU
In comparison to the H8/300H CPU, the H8S/2000 CPU has the following enhancements. • Additional control register One 8-bit control register has been added. • Enhanced instructions Addressing modes of bit-manipulation instructions have been enhanced. Two-bit shift and two-bit rotate instructions have been added. Instructions for saving and restoring multiple registers have been added. A test and set instruction has been added. • Higher speed Basic instructions are executed twice as fast.
Rev. 2.00, 03/04, page 15 of 534
2.2
CPU Operating Modes
The H8S/2000 CPU has two operating modes: normal and advanced. Normal mode supports a maximum 64-kbyte address space. Advanced mode supports a maximum 16-Mbyte address space. The mode is selected by the LSI's mode pins. 2.2.1 Normal Mode
The exception vector table and stack have the same structure as in the H8/300 CPU in normal mode. • Address space Linear access to a maximum address space of 64 kbytes is possible. • Extended registers (En) The extended registers (E0 to E7) can be used as 16-bit registers, or as the upper 16-bit segments of 32-bit registers. When extended register En is used as a 16-bit register it can contain any value, even when the corresponding general register (Rn) is used as an address register. (If general register Rn is referenced in the register indirect addressing mode with pre-decrement (@–Rn) or postincrement (@Rn+) and a carry or borrow occurs, the value in the corresponding extended register (En) will be affected.) • Instruction set All instructions and addressing modes can be used. Only the lower 16 bits of effective addresses (EA) are valid. • Exception vector table and memory indirect branch addresses In normal mode, the top area starting at H'0000 is allocated to the exception vector table. One branch address is stored per 16 bits. The exception vector table in normal mode is shown in figure 2.1. For details of the exception vector table, see section 4, Exception Handling. The memory indirect addressing mode (@@aa:8) employed in the JMP and JSR instructions uses an 8-bit absolute address included in the instruction code to specify a memory operand that contains a branch address. In normal mode, the operand is a 16-bit (word) operand, providing a 16-bit branch address. Branch addresses can be stored in the top area from H'0000 to H'00FF. Note that this area is also used for the exception vector table. • Stack structure When the program counter (PC) is pushed onto the stack in a subroutine call, and the PC, condition-code register (CCR), and extended control register (EXR) are pushed onto the stack in exception handling, they are stored as shown in figure 2.2. EXR is not pushed onto the stack in interrupt control mode 0. For details, see section 4, Exception Handling. Note: For this LSI, normal mode is not available.
Rev. 2.00, 03/04, page 16 of 534
H'0000 H'0001 H'0002 H'0003 H'0004 H'0005 H'0006 H'0007 H'0008 H'0009 H'000A H'000B
Reset exception vector (Reserved for system use)
(Reserved for system use)
Exception vector table
Exception vector 1 Exception vector 2
Figure 2.1 Exception Vector Table (Normal Mode)
SP
PC (16 bits)
SP (SP *
2
EXR*1 Reserved*1,*3 ) CCR CCR*3 PC (16 bits)
(a) Subroutine Branch Notes: 1. When EXR is not used, it is not stored on the stack. 2. SP when EXR is not used. 3. lgnored when returning.
(b) Exception Handling
Figure 2.2 Stack Structure in Normal Mode
Rev. 2.00, 03/04, page 17 of 534
2.2.2
Advanced Mode
• Address space Linear access to a maximum address space of 16 Mbytes is possible. • Extended registers (En) The extended registers (E0 to E7) can be used as 16-bit registers. They can also be used as the upper 16-bit segments of 32-bit registers or address registers. • Instruction set All instructions and addressing modes can be used. • Exception vector table and memory indirect branch addresses In advanced mode, the top area starting at H'00000000 is allocated to the exception vector table in 32-bit units. In each 32 bits, the upper 8 bits are ignored and a branch address is stored in the lower 24 bits (see figure 2.3). For details of the exception vector table, see section 4, Exception Handling.
H'00000000 Reserved Reset exception vector H'00000003 H'00000004 Reserved (Reserved for system use) H'00000007 H'00000008 Exception vector table
H'0000000B H'0000000C
(Reserved for system use)
H'00000010
Reserved Exception vector 1
Figure 2.3 Exception Vector Table (Advanced Mode)
Rev. 2.00, 03/04, page 18 of 534
The memory indirect addressing mode (@@aa:8) employed in the JMP and JSR instructions uses an 8-bit absolute address included in the instruction code to specify a memory operand that contains a branch address. In advanced mode, the operand is a 32-bit longword operand, providing a 32-bit branch address. The upper 8 bits of these 32 bits are a reserved area that is regarded as H'00. Branch addresses can be stored in the area from H'00000000 to H'000000FF. Note that the top area of this range is also used for the exception vector table. • Stack structure In advanced mode, when the program counter (PC) is pushed onto the stack in a subroutine call, and the PC, condition-code register (CCR), and extended control register (EXR) are pushed onto the stack in exception handling, they are stored as shown in figure 2.4. EXR is not pushed onto the stack in interrupt control mode 0. For details, see section 4, Exception Handling.
SP SP Reserved PC (24 bits) (SP *2 )
EXR*1 Reserved*1, *3 CCR PC (24 bits)
(a) Subroutine Branch Notes: 1. When EXR is not used, it is not stored on the stack. 2. SP when EXR is not used. 3. Ignored when returning.
(b) Exception Handling
Figure 2.4 Stack Structure in Advanced Mode
Rev. 2.00, 03/04, page 19 of 534
2.3
Address Space
Figure 2.5 shows a memory map of the H8S/2000 CPU. The H8S/2000 CPU provides linear access to a maximum 64-kbyte address space in normal mode, and a maximum 16-Mbyte (architecturally 4-Gbyte) address space in advanced mode. The usable modes and address spaces differ depending on the product. For details on each product, refer to section 3, MCU Operating Modes.
H'0000 64 kbyte H'FFFF H'00000000 16 Mbyte Program area
H'00FFFFFF Not available in this LSI
Data area
H'FFFFFFFF (a) Normal Mode* Note: For this LSI, normal mode is not available. (b) Advanced Mode
Figure 2.5 Memory Map
Rev. 2.00, 03/04, page 20 of 534
2.4
Register Configuration
The H8S/2000 CPU has the internal registers shown in figure 2.6. There are two types of registers: general registers and control registers. Control registers are a 24-bit program counter (PC), an 8-bit extended control register (EXR), and an 8-bit condition code register (CCR).
General Registers (Rn) and Extended Registers (En)
15 ER0 ER1 ER2 ER3 ER4 ER5 ER6 ER7 (SP) E0 E1 E2 E3 E4 E5 E6 E7 07 R0H R1H R2H R3H R4H R5H R6H R7H 07 R0L R1L R2L R3L R4L R5L R6L R7L 0
Control Registers
23 PC 0
EXR T
76543210 - - - - I2 I1 I0
76543210
CCR I UI H U N Z V C
[Legend]
SP: PC: EXR: T: I2 to I0: CCR: I: UI: Stack pointer Program counter Extended control register Trace bit Interrupt mask bits* Condition-code register Interrupt mask bit User bit or interrupt mask bit H: U: N: Z: V: C: Half-carry flag User bit Negative flag Zero flag Overflow flag Carry flag
Note: For this LSI, the interrupt mask bit is not available.
Figure 2.6 CPU Internal Registers
Rev. 2.00, 03/04, page 21 of 534
2.4.1
General Registers
The H8S/2000 CPU has eight 32-bit general registers. These general registers are all functionally alike and can be used as both address registers and data registers. When a general register is used as a data register, it can be accessed as a 32-bit, 16-bit, or 8-bit register. Figure 2.7 illustrates the usage of the general registers. When the general registers are used as 32-bit registers or address registers, they are designated by the letters ER (ER0 to ER7). When the general registers are used as 16-bit registers, the ER registers are divided into 16-bit general registers designated by the letters E (E0 to E7) and R (R0 to R7). These registers are functionally equivalent, providing a maximum sixteen 16-bit registers. The E registers (E0 to E7) are also referred to as extended registers. When the general registers are used as 8-bit registers, the R registers are divided into 8-bit general registers designated by the letters RH (R0H to R7H) and RL (R0L to R7L). These registers are functionally equivalent, providing a maximum sixteen 8-bit registers. The usage of each register can be selected independently. General register ER7 has the function of the stack pointer (SP) in addition to its general-register function, and is used implicitly in exception handling and subroutine calls. Figure 2.8 shows the stack.
• Address registers • 32-bit registers • 16-bit registers • 8-bit registers
E registers (extended registers) (E0 to E7) ER registers (ER0 to ER7) R registers (R0 to R7) RL registers (R0L to R7L) RH registers (R0H to R7H)
Figure 2.7 Usage of General Registers
Rev. 2.00, 03/04, page 22 of 534
Free area SP (ER7)
Stack area
Figure 2.8 Stack 2.4.2 Program Counter (PC)
This 24-bit counter indicates the address of the next instruction the CPU will execute. The length of all CPU instructions is 2 bytes (one word), so the least significant PC bit is ignored. (When an instruction is fetched for read, the least significant PC bit is regarded as 0.) 2.4.3 Extended Control Register (EXR)
EXR is an 8-bit register that can be operated by the LDC, STC, ANDC, ORC, and XORC instructions. When an instruction other than STC is executed, all interrupts including NMI are masked in three states after the instruction is completed.
Bit 7 Bit Name T Initial Value 0 R/W R/W Description Trace Bit When this bit is set to 1, trace exception processing starts every when an instruction is executed. When this bit is cleared to 0, instructions are consecutively executed. 6 to3 2 to 0 I2 I1 I0 All1 1 1 1 R/W R/W R/W Reserved These bits are always read as 1. Interrupt Mask Bits 2 to 0 Specify interrupt request mask levels (0 to 7). In this LSI, these bits cannot be used as the interrupt mask level.
Rev. 2.00, 03/04, page 23 of 534
2.4.4
Condition-Code Register (CCR)
This 8-bit register contains internal CPU status information, including an interrupt mask bit (I) and half-carry (H), negative (N), zero (Z), overflow (V), and carry (C) flags. Operations can be performed on the CCR bits by the LDC, STC, ANDC, ORC, and XORC instructions. The N, Z, V, and C flags are used as branching conditions for conditional branch (Bcc) instructions.
Bit 7 Bit Name I Initial Value 1 R/W R/W Description Interrupt Mask Bit Masks interrupts other than NMI when set to 1. NMI is accepted regardless of the I bit setting. The I bit is set to 1 at the start of an exception-handling sequence. For details, refer to section 5, Interrupt Controller. 6 UI Undefined R/W User Bit or Interrupt Mask Bit Can be written to and read from by software using the LDC, STC, ANDC, ORC, and XORC instructions. 5 H Undefined R/W Half-Carry Flag When the ADD.B, ADDX.B, SUB.B, SUBX.B, CMP.B or NEG.B instruction is executed, this flag is set to 1 if there is a carry or borrow at bit 3, and cleared to 0 otherwise. When the ADD.W, SUB.W, CMP.W, or NEG.W instruction is executed, the H flag is set to 1 if there is a carry or borrow at bit 11, and cleared to 0 otherwise. When the ADD.L, SUB.L, CMP.L, or NEG.L instruction is executed, the H flag is set to 1 if there is a carry or borrow at bit 27, and cleared to 0 otherwise. 4 U Undefined R/W User Bit Can be written to and read from by software using the LDC, STC, ANDC, ORC, and XORC instructions. 3 N Undefined R/W Negative Flag Stores the value of the most significant bit of data as a sign bit. 2 Z Undefined R/W Zero Flag Set to 1 to indicate zero data, and cleared to 0 to indicate non-zero data. 1 V Undefined R/W Overflow Flag Set to 1 when an arithmetic overflow occurs, and cleared to 0 otherwise.
Rev. 2.00, 03/04, page 24 of 534
Bit 0
Bit Name C
Initial Value
R/W
Description Carry Flag Set to 1 when a carry occurs, and cleared to 0 otherwise. Used by: • • • Add instructions, to indicate a carry Subtract instructions, to indicate a borrow Shift and rotate instructions, to indicate a carry
Undefined R/W
The carry flag is also used as a bit accumulator by bit manipulation instructions.
2.4.5
Initial Register Values
Reset exception handling loads the CPU's program counter (PC) from the vector table, clears the trace (T) bit in EXR to 0, and sets the interrupt mask (I) bits in CCR and EXR to 1. The other CCR bits and the general registers are not initialized. Note that the stack pointer (ER7) is undefined. The stack pointer should therefore be initialized by an MOV.L instruction executed immediately after a reset.
Rev. 2.00, 03/04, page 25 of 534
2.5
Data Formats
The H8S/2000 CPU can process 1-bit, 4-bit BCD, 8-bit (byte), 16-bit (word), and 32-bit (longword) data. Bit-manipulation instructions operate on 1-bit data by accessing bit n (n = 0, 1, 2, …, 7) of byte operand data. The DAA and DAS decimal-adjust instructions treat byte data as two digits of 4-bit BCD data. 2.5.1 General Register Data Formats
Figure 2.9 shows the data formats of general registers.
Data Type
1-bit data
Register Number
RnH
Data Format
7 0 Don't care 76 54 32 10
7 1-bit data RnL Don't care
0
76 54 32 10
7 4-bit BCD data RnH Upper
43 Lower
0 Don't care
7 4-bit BCD data RnL Don't care Upper
43 Lower
0
7 Byte data RnH MSB
0 Don't care LSB 7 0 LSB
Byte data
RnL
Don't care MSB
Figure 2.9 General Register Data Formats (1)
Rev. 2.00, 03/04, page 26 of 534
Data Type Word data
Register Number Rn
Data Format
15
0
MSB
LSB
Word data
15
En
0
MSB
LSB
Longword data
31
ERn
16 15 0
MSB
En
Rn
LSB
[Legend]
ERn : General register ER En : Rn : RnL : General register E General register R General register RL
RnH : General register RH MSB : Most significant bit LSB : Least significant bit
Figure 2.9 General Register Data Formats (2)
Rev. 2.00, 03/04, page 27 of 534
2.5.2
Memory Data Formats
Figure 2.10 shows the data formats in memory. The H8S/2000 CPU can access word data and longword data in memory, but word or longword data must begin at an even address. If an attempt is made to access word or longword data at an odd address, no address error occurs but the least significant bit of the address is regarded as 0, so the access starts at the preceding address. This also applies to instruction fetches. When SP (ER7) is used as an address register to access the stack, the operand size should be word size or longword size.
Data Type Address
7 1-bit data Address L 7 6 5 4 3 2 1
Data Format
0 0
Byte data
Address L
MSB
LSB
Word data
Address 2M Address 2M+1
MSB LSB
Longword data
Address 2N Address 2N+1 Address 2N+2 Address 2N+3
MSB
LSB
Figure 2.10 Memory Data Formats
Rev. 2.00, 03/04, page 28 of 534
2.6
Instruction Set
The H8S/2000 CPU has 65 types of instructions. The instructions are classified by function as shown in table 2.1. Table 2.1
Function Data transfer
Instruction Classification
Instructions MOV POP* , PUSH* LDM, STM MOVFPE* , MOVTPE*
3 3 1 1
Size B/W/L W/L L B B/W/L B B/W/L L B/W W/L B B/W/L B/W/L
Types 5
Arithmetic operations
ADD, SUB, CMP, NEG ADDX, SUBX, DAA, DAS INC, DEC ADDS, SUBS MULXU, DIVXU, MULXS, DIVXS EXTU, EXTS TAS*
4
19
Logic operations Shift Bit manipulation Branch System control
AND, OR, XOR, NOT SHAL, SHAR, SHLL, SHLR, ROTL, ROTR, ROTXL, ROTXR
4 8 14 5 9 1 Total: 65
BSET, BCLR, BNOT, BTST, BLD, BILD, BST, BIST, BAND, B BIAND, BOR, BIOR, BXOR, BIXOR BCC*2, JMP, BSR, JSR, RTS TRAPA, RTE, SLEEP, LDC, STC, ANDC, ORC, XORC, NOP
Block data transfer EEPMOV
Notes: B: Byte size; W: Word size; L: Longword size. 1. POP.W Rn and PUSH.W Rn are identical to MOV.W @SP+, Rn and MOV.W Rn, @SP. POP.L ERn and PUSH.L ERn are identical to MOV.L @SP+, ERn and MOV.L ERn, @-SP. 2. BCC is the general name for conditional branch instructions. 3. Cannot be used in this LSI. 4. Only register ER0, ER1, ER4, or ER5 should be used when using the TAS instruction.
Rev. 2.00, 03/04, page 29 of 534
2.6.1
Table of Instructions Classified by Function
Tables 2.3 to 2.10 summarize the instructions in each functional category. The notation used in tables 2.3 to 2.10 is defined below. Table 2.2
Symbol Rd Rs Rn ERn (EAd) (EAs) EXR CCR N Z V C PC SP #IMM disp + – × ÷ ∧ ∨ ⊕ → ∼ :8/:16/:24/:32
Operation Notation
Description General register (destination)* General register (source)* General register* General register (32-bit register) Destination operand Source operand Extended control register Condition-code register N (negative) flag in CCR Z (zero) flag in CCR V (overflow) flag in CCR C (carry) flag in CCR Program counter Stack pointer Immediate data Displacement Addition Subtraction Multiplication Division Logical AND Logical OR Logical exclusive OR Move NOT (logical complement) 8-, 16-, 24-, or 32-bit length
Note: General registers include 8-bit registers (R0H to R7H, R0L to R7L), 16-bit registers (R0 to R7, E0 to E7), and 32-bit registers (ER0 to ER7).
Rev. 2.00, 03/04, page 30 of 534
Table 2.3
Instruction MOV
Data Transfer Instructions
Size* B/W/L Function (EAs) → Rd, Rs → (EAd) Moves data between two general registers or between a general register and memory, or moves immediate data to a general register.
MOVFPE MOVTPE POP
B B W/L
Cannot be used in this LSI. Cannot be used in this LSI. @SP+ → Rn Pops a general register from the stack. POP.W Rn is identical to MOV.W @SP+, Rn. POP.L ERn is identical to MOV.L @SP+, ERn
PUSH
W/L
Rn → @-SP Pushes a general register onto the stack. PUSH.W Rn is identical to MOV.W Rn, @-SP. PUSH.L ERn is identical to MOV.L ERn, @-SP.
LDM STM
L L
@SP+ → Rn (register list) Pops two or more general registers from the stack. Rn (register list) → @-SP Pushes two or more general registers onto the stack.
Note: Size refers to the operand size. B: Byte W: Word L: Longword
Rev. 2.00, 03/04, page 31 of 534
Table 2.4
Instruction ADD SUB
Arithmetic Operations Instructions (1)
Size* B/W/L Function Rd ± Rs → Rd, Rd ± #IMM → Rd Performs addition or subtraction on data in two general registers, or on immediate data and data in a general register. (Subtraction on immediate data and data in a general register cannot be performed in bytes. Use the SUBX or ADD instruction.) B Rd ± Rs ± C → Rd, Rd ± #IMM ± C → Rd Performs addition or subtraction with carry on data in two general registers, or on immediate data and data in a general register. B/W/L Rd ± 1 → Rd, Rd ± 2 → Rd Adds or subtracts the value 1 or 2 to or from data in a general register. (Only the value 1 can be added to or subtracted from byte operands.) L B Rd ± 1 → Rd, Rd ± 2 → Rd, Rd ± 4 → Rd Adds or subtracts the value 1, 2, or 4 to or from data in a 32-bit register. Rd (decimal adjust) → Rd Decimal-adjusts an addition or subtraction result in a general register by referring to CCR to produce 4-bit BCD data. B/W Rd × Rs → Rd Performs unsigned multiplication on data in two general registers: either 8 bits × 8 bits → 16 bits or 16 bits × 16 bits → 32 bits.
ADDX SUBX INC DEC ADDS SUBS DAA DAS MULXU
MULXS
B/W
Rd × Rs → Rd Performs signed multiplication on data in two general registers: either 8 bits × 8 bits → 16 bits or 16 bits × 16 bits → 32 bits.
DIVXU
B/W
Rd ÷ Rs → Rd Performs unsigned division on data in two general registers: either 16 bits ÷ 8 bits → 8-bit quotient and 8-bit remainder or 32 bits ÷ 16 bits → 16-bit quotient and 16-bit remainder.
Note: Size refers to the operand size. B: Byte W: Word L: Longword
Rev. 2.00, 03/04, page 32 of 534
Table 2.4
Instruction DIVXS
Arithmetic Operations Instructions (2)
Size*1 B/W Function Rd ÷ Rs → Rd Performs signed division on data in two general registers: either 16 bits ÷ 8 bits → 8-bit quotient and 8-bit remainder or 32 bits ÷ 16 bits → 16-bit quotient and 16-bit remainder.
CMP
B/W/L
Rd – Rs, Rd – #IMM Compares data in a general register with data in another general register or with immediate data, and sets the CCR bits according to the result.
NEG
B/W/L
0 – Rd → Rd Takes the two's complement (arithmetic complement) of data in a general register.
EXTU
W/L
Rd (zero extension) → Rd Extends the lower 8 bits of a 16-bit register to word size, or the lower 16 bits of a 32-bit register to longword size, by padding with zeros on the left.
EXTS
W/L
Rd (sign extension) → Rd Extends the lower 8 bits of a 16-bit register to word size, or the lower 16 bits of a 32-bit register to longword size, by extending the sign bit.
TAS*2
B
@ERd – 0, 1 → ( of @ERd) Tests memory contents, and sets the most significant bit (bit 7) to 1.
Notes: 1. Size refers to the operand size. B: Byte W: Word L: Longword 2. Only register ER0, ER1, ER4, or ER5 should be used when using the TAS instruction.
Rev. 2.00, 03/04, page 33 of 534
Table 2.5
Logic Operations Instructions
Function Rd ∧ Rs → Rd, Rd ∧ #IMM → Rd Performs a logical AND operation on a general register and another general register or immediate data.
Instruction Size* AND B/W/L
OR
B/W/L
Rd ∨ Rs → Rd, Rd ∨ #IMM → Rd Performs a logical OR operation on a general register and another general register or immediate data.
XOR
B/W/L
Rd ⊕ Rs → Rd, Rd ⊕ #IMM → Rd Performs a logical exclusive OR operation on a general register and another general register or immediate data.
NOT
B/W/L
∼ Rd → Rd Takes the one's complement (logical complement) of data in a general register.
Note: Size refers to the operand size. B: Byte W: Word L: Longword
Table 2.6
Shift Instructions
Function Rd (shift) → Rd Performs an arithmetic shift on data in a general register. 1-bit or 2 bit shift is possible. B/W/L Rd (shift) → Rd Performs a logical shift on data in a general register. 1-bit or 2 bit shift is possible. B/W/L B/W/L Rd (rotate) → Rd Rotates data in a general register. 1-bit or 2 bit rotation is possible. Rd (rotate) → Rd Rotates data including the carry flag in a general register. 1-bit or 2 bit rotation is possible.
Instruction Size* SHAL SHAR SHLL SHLR ROTL ROTR ROTXL ROTXR B/W/L
Note: Size refers to the operand size. B: Byte W: Word L: Longword
Rev. 2.00, 03/04, page 34 of 534
Table 2.7
Bit Manipulation Instructions (1)
Function 1 → ( of ) Sets a specified bit in a general register or memory operand to 1. The bit number is specified by 3-bit immediate data or the lower three bits of a general register.
Instruction Size* BSET B
BCLR
B
0 → ( of ) Clears a specified bit in a general register or memory operand to 0. The bit number is specified by 3-bit immediate data or the lower three bits of a general register.
BNOT
B
∼ ( of ) → ( of ) Inverts a specified bit in a general register or memory operand. The bit number is specified by 3-bit immediate data or the lower three bits of a general register.
BTST
B
∼ ( of ) → Z Tests a specified bit in a general register or memory operand and sets or clears the Z flag accordingly. The bit number is specified by 3-bit immediate data or the lower three bits of a general register.
BAND
B
C ∧ ( of ) → C Logically ANDs the carry flag with a specified bit in a general register or memory operand and stores the result in the carry flag.
BIAND
B
C ∧ ( of ) → C Logically ANDs the carry flag with the inverse of a specified bit in a general register or memory operand and stores the result in the carry flag. The bit number is specified by 3-bit immediate data.
BOR
B
C ∨ ( of ) → C Logically ORs the carry flag with a specified bit in a general register or memory operand and stores the result in the carry flag.
BIOR
B
C ∨ (∼ of ) → C Logically ORs the carry flag with the inverse of a specified bit in a general register or memory operand and stores the result in the carry flag. The bit number is specified by 3-bit immediate data.
Note: Size refers to the operand size. B: Byte
Rev. 2.00, 03/04, page 35 of 534
Table 2.7
Instruction BXOR
Bit Manipulation Instructions (2)
Size* B Function C ⊕ ( of ) → C Logically exclusive-ORs the carry flag with a specified bit in a general register or memory operand and stores the result in the carry flag.
BIXOR
B
C ⊕ ∼ ( of ) → C Logically exclusive-ORs the carry flag with the inverse of a specified bit in a general register or memory operand and stores the result in the carry flag. The bit number is specified by 3-bit immediate data.
BLD
B
( of ) → C Transfers a specified bit in a general register or memory operand to the carry flag.
BILD
B
∼ ( of ) → C Transfers the inverse of a specified bit in a general register or memory operand to the carry flag. The bit number is specified by 3-bit immediate data.
BST
B
C → ( of ) Transfers the carry flag value to a specified bit in a general register or memory operand.
BIST
B
∼ C → (. of ) Transfers the inverse of the carry flag value to a specified bit in a general register or memory operand. The bit number is specified by 3bit immediate data.
Note: Size refers to the operand size. B: Byte
Rev. 2.00, 03/04, page 36 of 534
Table 2.8
Instruction Bcc
Branch Instructions
Size Function Branches to a specified address if a specified condition is true. The branching conditions are listed below. Mnemonic BRA (BT) BRN (BF) BHI BLS BCC (BHS) BCS (BLO) BNE BEQ BVC BVS BPL BMI BGE BLT BGT BLE Description Always (true) Never (false) High Low or same Carry clear (high or same) Carry set (low) Not equal Equal Overflow clear Overflow set Plus Minus Greater or equal Less than Greater than Less or equal Condition Always Never C∨Z=0 C∨Z=1 C=0 C=1 Z=0 Z=1 V=0 V=1 N=0 N=1 N⊕V=0 N⊕V=1 Z ∨ (N ⊕ V) = 0 Z ∨ (N ⊕ V) = 1
JMP BSR JSR RTS
Branches unconditionally to a specified address. Branches to a subroutine at a specified address Branches to a subroutine at a specified address Returns from a subroutine
Rev. 2.00, 03/04, page 37 of 534
Table 2.9
Instruction TRAPA RTE SLEEP LDC
System Control Instructions
Size* B/W Function Starts trap-instruction exception handling. Returns from an exception-handling routine. Causes a transition to a power-down state. (EAs) → CCR, (EAs) → EXR Moves the memory operand contents or immediate data to CCR or EXR. Although CCR and EXR are 8-bit registers, word-size transfers are performed between them and memory. The upper 8 bits are valid.
STC
B/W
CCR → (EAd), EXR → (EAd) Transfers CCR or EXR contents to a general register or memory operand. Although CCR and EXR are 8-bit registers, word-size transfers are performed between them and memory. The upper 8 bits are valid.
ANDC ORC XORC
B B B
CCR ∧ #IMM → CCR, EXR ∧ #IMM → EXR Logically ANDs the CCR or EXR contents with immediate data. CCR ∨ #IMM → CCR, EXR ∨ #IMM → EXR Logically ORs the CCR or EXR contents with immediate data. CCR ⊕ #IMM → CCR, EXR ⊕ #IMM → EXR Logically exclusive-ORs the CCR or EXR contents with immediate data.
NOP
PC + 2 → PC Only increments the program counter.
Note: Size refers to the operand size. B: Byte W: Word
Rev. 2.00, 03/04, page 38 of 534
Table 2.10 Block Data Transfer Instructions
Instruction EEPMOV.B Size Function if R4L ≠ 0 then Repeat @ER5+ → @ER6+ R4L–1 → R4L Until R4L = 0 else next: if R4 ≠ 0 then Repeat @ER5+ → @ER6+ R4–1 → R4 Until R4 = 0 else next: Transfers a data block. Starting from the address set in ER5, transfers data for the number of bytes set in R4L or R4 to the address location set in ER6. Execution of the next instruction begins as soon as the transfer is completed.
EEPMOV.W
2.6.2
Basic Instruction Formats
The H8S/2000 CPU instructions consist of 2-byte (1-word) units. An instruction consists of an operation field (op), a register field (r), an effective address extension (EA), and a condition field (cc). Figure 2.11 shows examples of instruction formats. • Operation field Indicates the function of the instruction, the addressing mode, and the operation to be carried out on the operand. The operation field always includes the first four bits of the instruction. Some instructions have two operation fields. • Register field Specifies a general register. Address registers are specified by 3 bits, and data registers by 3 bits or 4 bits. Some instructions have two register fields, and some have no register field. • Effective address extension 8, 16, or 32 bits specifying immediate data, an absolute address, or a displacement. • Condition field Specifies the branching condition of Bcc instructions.
Rev. 2.00, 03/04, page 39 of 534
(1) Operation field only op NOP, RTS, etc.
(2) Operation field and register fields op rn rm ADD.B Rn, Rm, etc.
(3) Operation field, register fields, and effective address extension op EA (disp) rn rm MOV.B @(d:16, Rn), Rm, etc.
(4) Operation field, effective address extension, and condition field op cc EA (disp) BRA d:16, etc.
Figure 2.11 Instruction Formats (Examples)
2.7
Addressing Modes and Effective Address Calculation
The H8S/2000 CPU supports the eight addressing modes listed in table 2.11. Each instruction uses a subset of these addressing modes. Arithmetic and logic operations instructions can use the register direct and immediate addressing modes. Data transfer instructions can use all addressing modes except program-counter relative and memory indirect. Bit manipulation instructions can use register direct, register indirect, or absolute addressing mode to specify an operand, and register direct (BSET, BCLR, BNOT, and BTST instructions) or immediate (3-bit) addressing mode to specify a bit number in the operand. Table 2.11 Addressing Modes
No. Addressing Mode 1 2 3 4 5 6 7 8 Register direct Register indirect Register indirect with displacement Register indirect with post-increment Register indirect with pre-decrement Absolute address Immediate Program-counter relative Memory indirect Symbol Rn @ERn @(d:16,ERn)/@(d:32,ERn) @ERn+ @–ERn @aa:8/@aa:16/@aa:24/@aa:32 #xx:8/#xx:16/#xx:32 @(d:8,PC)/@(d:16,PC) @@aa:8
Rev. 2.00, 03/04, page 40 of 534
2.7.1
Register DirectRn
The register field of the instruction code specifies an 8-, 16-, or 32-bit general register which contains the operand. R0H to R7H and R0L to R7L can be specified as 8-bit registers. R0 to R7 and E0 to E7 can be specified as 16-bit registers. ER0 to ER7 can be specified as 32-bit registers. 2.7.2 Register Indirect@ERn
The register field of the instruction code specifies an address register (ERn) which contains the address of a memory operand. If the address is a program instruction address, the lower 24 bits are valid and the upper 8 bits are all assumed to be 0 (H'00). 2.7.3 Register Indirect with Displacement@(d:16, ERn) or @(d:32, ERn)
A 16-bit or 32-bit displacement contained in the instruction code is added to an address register (ERn) specified by the register field of the instruction, and the sum gives the address of a memory operand. A 16-bit displacement is sign-extended when added. 2.7.4 Register Indirect with Post-Increment or Pre-Decrement@ERn+ or @-ERn
Register Indirect with Post-Increment@ERn+: The register field of the instruction code specifies an address register (ERn) which contains the address of a memory operand. After the operand is accessed, 1, 2, or 4 is added to the address register contents and the sum is stored in the address register. The value added is 1 for byte access, 2 for word access, and 4 for longword access. For word or longword transfer instructions, the register value should be even. Register Indirect with Pre-Decrement@-ERn: The value 1, 2, or 4 is subtracted from an address register (ERn) specified by the register field in the instruction code, and the result becomes the address of a memory operand. The result is also stored in the address register. The value subtracted is 1 for byte access, 2 for word access, and 4 for longword access. For word or longword transfer instructions, the register value should be even. 2.7.5 Absolute Address@aa:8, @aa:16, @aa:24, or @aa:32
The instruction code contains the absolute address of a memory operand. The absolute address may be 8 bits long (@aa:8), 16 bits long (@aa:16), 24 bits long (@aa:24), or 32 bits long (@aa:32). Table 2.12 indicates the accessible absolute address ranges. To access data, the absolute address should be 8 bits (@aa:8), 16 bits (@aa:16), or 32 bits (@aa:32) long. For an 8-bit absolute address, the upper 24 bits are all assumed to be 1 (H'FFFF). For a 16-bit absolute address, the upper 16 bits are a sign extension. For a 32-bit absolute address, the entire address space is accessed.
Rev. 2.00, 03/04, page 41 of 534
A 24-bit absolute address (@aa:24) indicates the address of a program instruction. The upper 8 bits are all assumed to be 0 (H'00). Table 2.12 Absolute Address Access Ranges
Absolute Address Data address 8 bits (@aa:8) 16 bits (@aa:16) 32 bits (@aa:32) Program instruction address 24 bits (@aa:24) Normal Mode H'FF00 to H'FFFF H'0000 to H'FFFF Advanced Mode H'FFFF00 to H'FFFFFF H'000000 to H'007FFF, H'FF8000 to H'FFFFFF H'000000 to H'FFFFFF
2.7.6
Immediate#xx:8, #xx:16, or #xx:32
The 8-bit (#xx:8), 16-bit (#xx:16), or 32-bit (#xx:32) immediate data contained in a instruction code can be used directly as an operand. The ADDS, SUBS, INC, and DEC instructions implicitly contain immediate data in their instruction codes. Some bit manipulation instructions contain 3-bit immediate data in the instruction code, specifying a bit number. The TRAPA instruction contains 2-bit immediate data in its instruction code, specifying a vector address. 2.7.7 Program-Counter Relative@(d:8, PC) or @(d:16, PC)
This mode can be used by the Bcc and BSR instructions. An 8-bit or 16-bit displacement contained in the instruction code is sign-extended to 24 bits and added to the 24-bit address indicated by the PC value to generate a 24-bit branch address. Only the lower 24 bits of this branch address are valid; the upper 8 bits are all assumed to be 0 (H'00). The PC value to which the displacement is added is the address of the first byte of the next instruction, so the possible branching range is –126 to +128 bytes (–63 to +64 words) or –32766 to +32768 bytes (–16383 to +16384 words) from the branch instruction. The resulting value should be an even number. 2.7.8 Memory Indirect@@aa:8
This mode can be used by the JMP and JSR instructions. The instruction code contains an 8-bit absolute address specifying a memory operand which contains a branch address. The upper bits of the 8-bit absolute address are all assumed to be 0, so the address range is 0 to 255 (H'0000 to H'00FF in normal mode, H'000000 to H'0000FF in advanced mode).
Rev. 2.00, 03/04, page 42 of 534
In normal mode, the memory operand is a word operand and the branch address is 16 bits long. In advanced mode, the memory operand is a longword operand, the first byte of which is assumed to be 0 (H'00). Note that the top area of the address range in which the branch address is stored is also used for the exception vector area. For further details, refer to section 4, Exception Handling. If an odd address is specified in word or longword memory access, or as a branch address, the least significant bit is regarded as 0, causing data to be accessed or the instruction code to be fetched at the address preceding the specified address. (For further information, see section 2.5.2, Memory Data Formats.)
Specified by @aa:8
Branch address
Specified by @aa:8
Reserved Branch address
(a) Normal Mode*
Note: For this LSI, normal mode is not available.
(b) Advanced Mode
Figure 2.12 Branch Address Specification in Memory Indirect Addressing Mode
Rev. 2.00, 03/04, page 43 of 534
2.7.9
Effective Address Calculation
Table 2.13 indicates how effective addresses are calculated in each addressing mode. In normal mode, the upper 8 bits of the effective address are ignored in order to generate a 16-bit address. Table 2.13 Effective Address Calculation (1)
No 1
Addressing Mode and Instruction Format
Register direct (Rn)
Effective Address Calculation
Effective Address (EA)
Operand is general register contents.
op 2
rm
rn 31
General register contents
Register indirect (@ERn)
0
31
24 23
0
Don't care
op 3
r
Register indirect with displacement @(d:16,ERn) or @(d:32,ERn)
31
General register contents
0 31 24 23 0
op
r
disp 31
Sign extension
Don't care 0 disp
4
Register indirect with post-increment or pre-decrement •Register indirect with post-increment @ERn+
31
General register contents
0
31
24 23
0
Don't care
op
r 31
1, 2, or 4
•Register indirect with pre-decrement @-ERn
0
General register contents
31
24 23
0
Don't care op r
Operand Size Byte Word Longword 1, 2, or 4
Offset 1 2 4
Rev. 2.00, 03/04, page 44 of 534
Table 2.13 Effective Address Calculation (2)
No 5
Addressing Mode and Instruction Format
Absolute address
Effective Address Calculation
Effective Address (EA)
@aa:8 op abs
31
24 23 H'FFFF
87
0
Don't care
@aa:16 op abs
31
24 23
16 15
0
Don't care Sign extension
@aa:24 op abs
31
24 23
0
Don't care
@aa:32 op abs 31 24 23 0
Don't care
6
Immediate
#xx:8/#xx:16/#xx:32 op IMM
Operand is immediate data.
7
Program-counter relative @(d:8,PC)/@(d:16,PC)
23
PC contents
0
op
disp
23
Sign extension
0 disp 31 24 23 0
Don't care
8
Memory indirect @@aa:8 • Normal mode*
31 op abs H'000000 15
87 abs
0
0
Memory contents
31
24 23
16 15 H'00
0
Don't care
• Advanced mode
31 op abs 31
Memory contents
87 H'000000 abs
0 31 24 23 Don't care 0
0
Note: For this LSI, normal mode is not available.
Rev. 2.00, 03/04, page 45 of 534
2.8
Processing States
The H8S/2000 CPU has four main processing states: the reset state, exception handling state, program execution state, and program stop state. Figure 2.13 indicates the state transitions. • Reset state In this state the CPU and internal peripheral modules are all initialized and stopped. When the RES input goes low, all current processing stops and the CPU enters the reset state. All interrupts are masked in the reset state. Reset exception handling starts when the RES signal changes from low to high. For details, refer to section 4, Exception Handling. The reset state can also be entered by a watchdog timer overflow. • Exception-handling state The exception-handling state is a transient state that occurs when the CPU alters the normal processing flow due to an exception source, such as, a reset, trace, interrupt, or trap instruction. The CPU fetches a start address (vector) from the exception vector table and branches to that address. For further details, refer to section 4, Exception Handling. • Program execution state In this state the CPU executes program instructions in sequence. • Program stop state This is a power-down state in which the CPU stops operating. The program stop state occurs when a SLEEP instruction is executed or the CPU enters hardware standby mode. For details, refer to section 16, Power-Down Modes.
Rev. 2.00, 03/04, page 46 of 534
Program execution state
=0 BY SS EEP tion SL truc ins
io = 1 ruct BY nst SS EP i E SL
pt ion ha ex nd ce lin pt g ion ha nd lin g
ce
ex
Sleep mode
n
of
or
En d
es tf
rru Inte
Re
pt r
qu
equ
est
Exception handling state
External interrupt request
Software standby mode
= High = High, = Low
Reset state
*1
Hardware standby mode*2 Power-down state*3
Reset state
Notes: 1. From any state except hardware standby mode, a transition to the reset state occurs whenever A transition can also be made to the reset state when the watchdog timer overflows. 2. In every state, when the STBY pin becomes low, the hardware standby mode is entered. 3. For details, refer to section 16, Power-Down Modes.
goes low.
Figure 2.13 State Transitions
2.9
2.9.1
Usage Note
Note on Bit Manipulation Instructions
Bit manipulation instructions such as BSET, BCLR, BNOT, BST, and BIST read data in byte units, perform bit manipulation, and write data in byte units. Thus, care must be taken when these bit manipulation instructions are executed for a register or port including write-only bits. In addition, the BCLR instruction can be used to clear the flag of an internal I/O register. In this case, if the flag to be cleared has been set by an interrupt processing routine, the flag need not be read before executing the BCLR instruction.
Rev. 2.00, 03/04, page 47 of 534
Rev. 2.00, 03/04, page 48 of 534
Section 3 MCU Operating Modes
3.1 Operating Mode Selection
This LSI supports single operating mode (mode 2). The operating mode is determined by the setting of the mode pins (MD2 and MD1). Table 3.1 shows the MCU operating mode selection. Table 3.1 MCU Operating Mode Selection
On-Chip ROM
MCU Operating CPU Operating Mode MD2 MD1 Mode Description 2 1 1
Advanced mode Extended mode with on-chip ROM Enabled Single-chip mode
Mode 2 is single-chip mode after a reset. The CPU can switch to extended mode by setting bit EXPE in MDCR to 1. Modes 0, 1, 3, 5, and 7 cannot be used in this LSI. Modes 4 and 6 are specific modes. Thus, mode pins should be set to enable mode 2 in normal program execution state. Mode pins should not be changed during operation. Mode 4 is a boot mode to program/erase the flash memory. Mode 6 is on-chip emulation mode. This mode is controlled by the on-chip emulator (E10A) via the JTAG interface, and on-chip emulation can be performed.
Rev. 2.00, 03/04, page 49 of 534
3.2
Register Descriptions
The following registers are related to the operating mode. • Mode control register (MDCR) • System control register (SYSCR) 3.2.1 Mode Control Register (MDCR)
MDCR is used to set an operating mode and to monitor the current operating mode.
Bit 7 Bit Name EXPE Initial Value 0 R/W R/W Description Extended Mode Enable Specifies extended mode. 0: Single-chip mode 1: Extended mode 6 to 3 All 0 R Reserved These bits are always read as 0 and cannot be modified. 2 1 MDS2 MDS1 —* —* R R Mode Select 2, 1 These bits indicate the input levels at mode pins (MD2 and MD1) (the current operating mode). Bits MDS2 and MDS1 correspond to MD2 and MD1, respectively. MDS2 and MDS1 are read-only bits and they cannot be written to. The mode pin (MD2 and MD1) input levels are latched into these bits when MDCR is read. These latches are canceled by a reset. Reserved This bit is always read as 0 and cannot be modified. Note: * The initial values are determined by the settings of the MD2 and MD1 pins.
0
0
R
Rev. 2.00, 03/04, page 50 of 534
3.2.2
System Control Register (SYSCR)
SYSCR monitors a reset source, selects the interrupt control mode and the detection edge for NMI, and controls on-chip RAM address space.
Bit 7, 6 5 4 Bit Name INTM1 INTM0 Initial Value All 0 0 0 R/W R/W R R/W Description Reserved The initial value should not be changed. These bits select the control mode of the interrupt controller. For details on the interrupt control modes, see section 5.6, Interrupt Control Modes and Interrupt Operation. 00: Interrupt control mode 0 01: Interrupt control mode 1 10: Setting prohibited 11: Setting prohibited 3 XRST 1 R External Reset This bit indicates the reset source. A reset is caused by an external reset input, or when the watchdog timer overflows. 0: A reset is caused when the watchdog timer overflows. 1: A reset is caused by an external reset. 2 NMIEG 0 R/W NMI Edge Select Selects the valid edge of the NMI interrupt input. 0: An interrupt is requested at the falling edge of NMI input 1: An interrupt is requested at the rising edge of NMI input 1 0 RAME 0 1 R/W R/W Reserved The initial value should not be changed. RAM Enable Enables or disables on-chip RAM. The RAME bit is initialized when the reset state is released. 0: On-chip RAM is disabled 1: On-chip RAM is enabled
Rev. 2.00, 03/04, page 51 of 534
3.3
3.3.1
Operating Modes
Mode 2
The CPU can access a 16-Mbyte address space in advanced mode. The on-chip ROM is enabled. After a reset, the LSI is set to single-chip mode. To access an external address space, bit EXPE in MDCR should be set to 1. In extended mode, ports 6 and 7 function as input ports after a reset. Ports 6 and 7 function as an address bus by setting the AHOE, AMOE, ALOE bits to 1 in the port function control register 1 (PFCR1). Ports 5 and 8 function as a data bus, and parts of ports 9 and A function bus control signals. 3.3.2 Pin Functions
Table 3.2 shows pin functions in operating mode 2. Table 3.2
Port Port 5 Port 6 Port 7 Port 8 Port 9 P97 P96 to P90 Port A PA3 to PA1 PA0 [Legend] *: After a reset
Pin Functions in Operating Mode 2
Mode 2 I/O port*/Data bus I/O I/O port*/Address bus output I/O port*/Address bus output I/O port*/Data bus I/O I/O port*/Clock I/O Input port*/Control signal output I/O port*/Address bus output/Control signal output I/O port*/Address bus output
Rev. 2.00, 03/04, page 52 of 534
3.4
Address Map
Figure 3.1 shows the address map in each operating mode.
ROM: 256 kbytes RAM: 32 kbytes Mode 2 (EXPE = 1) Advanced mode Extended mode with on-chip ROM H'000000 H'000000 ROM: 256 kbytes RAM: 32 kbytes Mode 2 (EXPE = 0) Advanced mode Single chip mode
On-chip ROM
On-chip ROM
H'040000
H'040000
External address space
Reserved area
H'FF7000
On-chip RAM/external address space* External address space Internal I/O registers External address space Internal I/O registers
H'FF7000
On-chip RAM/reserved area* Reserved area Internal I/O registers Reserved area Internal I/O registers
H'FFF000 H'FFFC00 H'FFFF00 H'FFFF40 H'FFFFFF
H'FFF000 H'FFFC00 H'FFFF00 H'FFFF40 H'FFFFFF
Note: * These areas can be used as an on-chip RAM area by setting the RAME bit in SYSCR to 1.
Figure 3.1 Address Map
Rev. 2.00, 03/04, page 53 of 534
Rev. 2.00, 03/04, page 54 of 534
Section 4 Exception Handling
4.1 Exception Handling Types and Priority
As table 4.1 indicates, exception handling may be caused by a reset, interrupt, or trap instruction. Exception handling is prioritized as shown in table 4.1. If two or more exceptions occur simultaneously, they are accepted and processed in order of priority. Table 4.1
Priority High
Exception Types and Priority
Exception Type Reset Interrupt Start of Exception Handling Starts immediately after a low-to-high transition of the RES pin, or when the watchdog timer overflows. Starts when execution of the current instruction or exception handling ends, if an interrupt request has been issued. Interrupt detection is not performed on completion of ANDC, ORC, XORC, or LDC instruction execution, or on completion of reset exception handling. Started by execution of a trap (TRAPA) instruction. Trap instruction exception handling requests are accepted at all times in program execution state.
Trap instruction Low
Rev. 2.00, 03/04, page 55 of 534
4.2
Exception Sources and Exception Vector Table
Different vector addresses are assigned to different exception sources. Table 4.2 lists the exception sources and their vector addresses. Table 4.2 Exception Handling Vector Table
Vector Address Exception Source Reset Reserved for system use Vector Number 0 1 6 7 Advanced Mode H'000000 to H'000003 H'000004 to H'000007 H'000018 to H'00001B H'00001C to H'00001F H'000020 to H'000023 H'000024 to H'000027 H'000028 to H'00002B H'00002C to H'00002F H'000030 to H'000033 H'00003C to H'00003F H'000040 to H'000043 H'000044 to H'000047 H'000048 to H'00004B H'00004C to H'00004F H'000050 to H'000053 H'000054 to H'000057 H'000058 to H'00005B H'00005C to H'00005F H'000060 to H'000063 H'0001B8 to H'0001BB
External interrupt (NMI)
Trap instruction (four sources) 8 9 10 11 Reserved for system use 12 15 16 17 18 19 20 21 22 23 24 110
External interrupt External interrupt External interrupt External interrupt External interrupt External interrupt External interrupt External interrupt Internal interrupt*
IRQ0 IRQ1 IRQ2 IRQ3 IRQ4 IRQ5 IRQ6 IRQ7
Note:
*
For details on the internal interrupt vector table, see section 5.5, Interrupt Exception Handling Vector Table.
Rev. 2.00, 03/04, page 56 of 534
4.3
Reset
A reset has the highest exception priority. When the RES pin goes low, all processing halts and this LSI enters the reset. To ensure that this LSI is reset, hold the RES pin low for at least 20 ms at power-on. To reset the chip during operation, hold the RES pin low for at least 20 states. A reset initializes the internal state of the CPU and the registers of on-chip peripheral modules. The chip can also be reset by overflow of the watchdog timer. For details, see section 10, Watchdog Timer (WDT). 4.3.1 Reset Exception Handling
When the RES pin goes high after being held low for the necessary time, this LSI starts reset exception handling as follows: 1. The internal state of the CPU and the registers of the on-chip peripheral modules are initialized and the I bit is set to 1 in CCR. 2. The reset exception handling vector address is read and transferred to the PC, and program execution starts from the address indicated by the PC. Figure 4.1 shows an example of the reset sequence.
Rev. 2.00, 03/04, page 57 of 534
Vector fetch
Internal processing
Prefetch of first program instruction
φ
RES
Internal address bus
(1)
(3)
(5)
Internal read signal
Internal write signal
High
Internal data bus
(2)
(4)
(6)
(1), (3) (2), (4) (5) (6)
Reset exception handling vector address ((1) = H'000000, (3) = H'000002) Start address (contents of reset exception handling vector address) Start address ((5) = (2)(4)) First program instruction
Figure 4.1 Reset Sequence 4.3.2 Interrupts after Reset
If an interrupt is accepted after a reset and before the stack pointer (SP) is initialized, the PC and CCR will not be saved correctly, leading to a program crash. To prevent this, all interrupt requests, including NMI, are disabled immediately after a reset. Since the first instruction of a program is always executed immediately after the reset state ends, make sure that this instruction initializes the stack pointer (example: MOV.L #xx: 32, SP). 4.3.3 On-Chip Peripheral Modules after Reset is Cancelled
After a reset is cancelled, the module stop control register (MSTPCR) is initialized, and all modules except the DMAC operate in module stop mode. Therefore, the registers of on-chip peripheral modules cannot be read from or written to. To read from and write to these registers, clear module stop mode.
Rev. 2.00, 03/04, page 58 of 534
4.4
Interrupt Exception Handling
Interrupts are controlled by the interrupt controller. The sources to start interrupt exception handling are external interrupt sources (NMI and IRQ7 to IRQ0) and internal interrupt sources from the on-chip peripheral modules. NMI is an interrupt with the highest priority. For details, see section 5, Interrupt Controller. Interrupt exception handling is conducted as follows: 1. The values in the program counter (PC) and condition code register (CCR) are saved to the stack. 2. A vector address corresponding to the interrupt source is generated, the start address is loaded from the vector table to the PC, and program execution begins from that address.
4.5
Trap Instruction Exception Handling
Trap instruction exception handling starts when a TRAPA instruction is executed. Trap instruction exception handling can be executed at all times in the program execution state. Trap instruction exception handling is conducted as follows: 1. The values in the program counter (PC) and condition code register (CCR) are saved to the stack. 2. A vector address corresponding to the interrupt source is generated, the start address is loaded from the vector table to the PC, and program execution starts from that address. The TRAPA instruction fetches a start address from a vector table entry corresponding to a vector number from 0 to 3, as specified in the instruction code. Table 4.3 shows the status of CCR after execution of trap instruction exception handling. Table 4.3 Status of CCR after Trap Instruction Exception Handling
CCR Interrupt Control Mode 0 1 I Set to 1 Set to 1 UI Retains value prior to execution Set to 1
Rev. 2.00, 03/04, page 59 of 534
4.6
Stack Status after Exception Handling
Figure 4.2 shows the stack after completion of trap instruction exception handling and interrupt exception handling.
SP
CCR PC (24 bits)
Figure 4.2 Stack Status after Exception Handling
4.7
Usage Note
When accessing word data or longword data, this LSI assumes that the lowest address bit is 0. The stack should always be accessed in words or longwords, and the value of the stack pointer (SP: ER7) should always be kept even. Use the following instructions to save registers:
PUSH.W PUSH.L Rn ERn
(or MOV.W Rn, @-SP) (or MOV.L ERn, @-SP)
Use the following instructions to restore registers:
POP.W POP.L Rn ERn
(or MOV.W @SP+, Rn) (or MOV.L @SP+, ERn)
Setting SP to an odd value may lead to a malfunction. Figure 4.3 shows an operation example when the SP value is odd.
Rev. 2.00, 03/04, page 60 of 534
Address
CCR SP PC
SP
R1L PC
H'FFFEFA H'FFFEFB H'FFFEFC H'FFFEFD
SP
H'FFFEFF
TRAPA instruction executed SP set to H'FFFEFF Legend
MOV.B R1L, @-ER7 executed Contents of CCR lost
Data saved above SP
CCR : PC : R1L : SP :
Condition code register Program counter General register R1L Stack pointer
Note: This diagram illustrates an example in which the interrupt control mode is 0.
Figure 4.3 Operation when SP Value is Odd
Rev. 2.00, 03/04, page 61 of 534
Rev. 2.00, 03/04, page 62 of 534
Section 5 Interrupt Controller
5.1 Features
• Two interrupt control modes Any of two interrupt control modes can be set by means of the INTM1 and INTM0 bits in the system control register (SYSCR). • Priorities settable with ICR An interrupt control register (ICR) is provided for setting interrupt priorities. Three priority levels can be set for each module for all interrupts except NMI. • Independent vector addresses All interrupt sources are assigned independent vector addresses, making it unnecessary for the source to be identified in the interrupt handling routine. • Nine external interrupts NMI is the highest-priority interrupt, and is accepted at all times. Rising edge or falling edge detection can be selected for NMI. Falling-edge, rising-edge, or both-edge detection, or level sensing, can be selected for IRQ7 to IRQ0.
INTM1, INTM0 SYSCR NMIEG NMI input IRQ input NMI input IRQ input ISR ISCR Internal interrupt sources WOVI0 to USBI2
ICR Interrupt controller [Legend] ICR : ISCR : IER : ISR : SYSCR : Interrupt control register IRQ sense control register IRQ enable register IRQ status register System control register Interrupt request Priority level determination Vector number I, UI
CPU
IER
CCR
Figure 5.1 Block Diagram of Interrupt Controller
Rev. 2.00, 03/04, page 63 of 534
5.2
Input/Output Pins
Table 5.1 summarizes the pins of the interrupt controller. Table 5.1
Symbol NMI IRQ7 to IRQ0
Pin Configuration
I/O Input Input Function Nonmaskable external interrupt Rising edge or falling edge can be selected Maskable external interrupts Rising edge, falling edge, or both edges, or level sensing, can be selected individually for each pin. Whether the IRQn interrupt is input from the IRQn or (IRQn) is selectable. (n = 7 to 0)
5.3
Register Descriptions
The interrupt controller has the following registers. For details on the system control register (SYSCR), see section 3.2.2, System Control Register (SYSCR), and for details on the IRQ sense port select register (ISSR), see section 8.11.2, IRQ Sense Port Select Register (ISSR). • • • • • • Interrupt control registers A to C (ICRA to ICRC) Address break control register (ABRKCR) Break address registers A to C (PBARA to PBARC) IRQ sense control registers H, L (ISCRH, ISCRL) IRQ enable register (IER) IRQ status register (ISR) Interrupt Control Registers A to C (ICRA to ICRC)
5.3.1
The ICR registers set interrupt control levels for interrupts other than NMI. The correspondence between interrupt sources and ICRA to ICRC settings is shown in table 5.2.
Bit 7 to 0 Bit Name ICRn7 to IRCn0 Initial Value All 0 R/W R/W Description Interrupt Control Level 0: Corresponding interrupt source is interrupt control level 0 (no priority) 1: Corresponding interrupt source is interrupt control level 1 (priority) Note: n: A to C Rev. 2.00, 03/04, page 64 of 534
Table 5.2
Correspondence between Interrupt Source and ICR
Register
Bit 7 6 5 4 3 2 1 0
Bit Name ICRn7 ICRn6 ICRn5 ICRn4 ICRn3 ICRn2 ICRn1 ICRn0
ICRA IRQ0 IRQ1 IRQ2, IRQ3 IRQ4, IRQ5 IRQ6, IRQ7 — WDT Refresh timer
ICRB Suspend recover interrupt DMAC TMR_0 TMR_1
ICRC SCI USB2
Note: n: A to C : Reserved. The write value should always be 0.
5.3.2
Address Break Control Register (ABRKCR)
ABRKCR controls the address breaks. When both the CMF flag and BIE flag are set to 1, an address break is requested.
Bit 7 Bit Name CMIF Initial Value R/W Description Condition Match Flag Address break source flag. Indicates that an address specified by BARA to BARC is prefetched. [Clearing condition] When an exception handling is executed for an address break interrupt. [Setting condition] When an address specified by BARA to BARC is prefetched while the BIE flag is set to 1. 6 to 1 All 0 R Reserved These bits are always read as 0 and cannot be modified. 0 BIE 0 R/W Break Interrupt Enable Enables or disables address break. 0: Disabled 1: Enabled Rev. 2.00, 03/04, page 65 of 534
Undefined R/W
5.3.3
Break Address Registers A to C (PBARA to PBARC)
The PBAR registers specify an address that is to be a break address. An address in which the first byte of an instruction exists should be set as a break address. • PBARA
Bit 7 to 0 Bit Name A23 to A16 Initial Value All 0 R/W R/W Description Addresses 23 to 16 The A23 to A16 bits are compared with A23 to A16 in the internal address bus.
• PBARB
Bit 7 to 0 Bit Name A15 to A8 Initial Value All 0 R/W R/W Description Addresses 15 to 8 The A15 to A8 bits are compared with A15 to A8 in the internal address bus.
• PBARC
Bit 7 to 1 Bit Name A7 to A1 Initial Value All 0 R/W R/W Description Addresses 7 to 1 The A7 to A1 bits are compared with A7 to A1 in the internal address bus. 0 0 R Reserved This bit is always read as 0 and cannot be modified.
Rev. 2.00, 03/04, page 66 of 534
5.3.4
IRQ Sense Control Registers H, L (ISCRH, ISCRL)
The ISCR registers select the source that generates an interrupt request at pins IRQ7 to IRQ0. The IRQ7 to IRQ0 pins can be switched to input pins by setting the IRQ sense port select register (ISSR). • ISCRH
Bit 7 6 5 4 3 2 1 0 Bit Name IRQ7SCB IRQ7SCA IRQ6SCB IRQ6SCA IRQ5SCB IRQ5SCA IRQ4SCB IRQ4SCA Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description IRQn Sense Control B IRQn Sense Control A 00: Interrupt request generated at low level of IRQn input 01: Interrupt request generated at falling edge of IRQn input 10: Interrupt request generated at rising edge of IRQn input 11: Interrupt request generated at both falling and rising edges of IRQn input (n = 7 to 4)
• ISCRL
Bit 7 6 5 4 3 2 1 0 Bit Name IRQ3SCB IRQ3SCA IRQ2SCB IRQ2SCA IRQ1SCB IRQ1SCA IRQ0SCB IRQ0SCA Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description IRQn Sense Control B IRQn Sense Control A 00: Interrupt request generated at low level of IRQn input 01: Interrupt request generated at falling edge of IRQn input 10: Interrupt request generated at rising edge of IRQn input 11: Interrupt request generated at both falling and rising edges of IRQn input (n = 3 to 0)
Rev. 2.00, 03/04, page 67 of 534
5.3.5
IRQ Enable Register (IER)
IER controls the enabling and disabling of interrupt requests IRQ7 to IRQ0.
Bit 7 6 5 4 3 2 1 0 Bit Name IRQ7E IRQ6E IRQ5E IRQ4E IRQ3E IRQ2E IRQ1E IRQ0E Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description IRQn Enable (n = 7 to 0) The IRQn interrupt request is enabled when this bit is 1.
5.3.6
IRQ Status Register (ISR)
ISR is a flag register that indicates the status of IRQ7 to IRQ0 interrupt requests.
Bit 7 6 5 4 3 2 1 0 Bit Name IRQ7F IRQ6F IRQ5F IRQ4F IRQ3F IRQ2F IRQ1F IRQ0F Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description [Setting condition] When the interrupt source selected by the ISCR registers occurs [Clearing conditions] • • • When reading IRQnF flag when IRQnF = 1, then writing 0 to IRQnF flag When interrupt exception handling is executed when low-level detection is set and IRQn input is high When IRQn interrupt exception handling is executed when falling-edge, rising-edge, or both-edge detection is set
(n = 7 to 0)
Rev. 2.00, 03/04, page 68 of 534
5.4
5.4.1
Interrupt Sources
External Interrupts
There are two external interrupts: NMI and IRQ7 to IRQ0. These interrupts can be used to restore this LSI from software standby mode. NMI Interrupt: NMI is the highest-priority interrupt, and is always accepted by the CPU regardless of the interrupt control mode or the status of the CPU interrupt mask bits. The NMIEG bit in SYSCR can be used to select whether an interrupt is requested at a rising edge or a falling edge on the NMI pin. IRQ7 to IRQ0 Interrupts: Interrupts IRQ7 to IRQ0 are requested by an input signal at pins IRQ7 to IRQ0. Interrupts IRQ7 to IRQ0 have the following features: • The interrupt exception handling for interrupt requests IRQ7 to IRQ0 can be started at an independent vector address. • Using ISCR, it is possible to select whether an interrupt is generated by a low level, falling edge, rising edge, or both edges, at pins IRQ7 to IRQ0. • Enabling or disabling of interrupt requests IRQ7 to IRQ0 can be selected with IER. • The status of interrupt requests IRQ7 to IRQ0 is indicated in ISR. ISR flags can be cleared to 0 by software. The detection of IRQ7 to IRQ0 interrupts does not depend on whether the relevant pin has been set for input or output. However, when a pin is used as an external interrupt input pin, do not clear the corresponding port DDR to 0 to use the pin as an I/O pin for another function. A block diagram of interrupts IRQ7 to IRQ0 is shown in figure 5.2.
IRQnE IRQnSCA, IRQnSCB IRQnF Edge/level detection circuit input S R Q IRQn interrupt request
Clear signal n = 7 to 0
Figure 5.2 Block Diagram of Interrupts IRQ7 to IRQ0
Rev. 2.00, 03/04, page 69 of 534
5.4.2
Internal Interrupts
Internal interrupts issued from the on-chip peripheral modules have the following features: • For each on-chip peripheral module there are flags that indicate the interrupt request status, and enable bits that individually select enabling or disabling of these interrupts. When the enable bit for a particular interrupt source is set to 1, an interrupt request is sent to the interrupt controller. • The control level for each interrupt can be set by ICR.
5.5
Interrupt Exception Handling Vector Table
Table 5.3 lists interrupt exception handling sources, vector addresses, and interrupt priorities. For default priorities, the lower the vector number, the higher the priority. Modules set at the same priority will conform to their default priorities. Priorities within a module are fixed. An interrupt control level can be specified for a module to which an ICR bit is assigned. Interrupt requests from modules that are set to interrupt control level 1 (priority) by the ICR bit setting and the I and UI bits in CCR are given priority and processed before interrupt requests from modules that are set to interrupt control level 0 (no priority). Table 5.3
Origin of Interrupt Source External pin
Interrupt Sources, Vector Addresses, and Interrupt Priorities
Vector Number Vector Address ICR 7 16 17 18 19 20 21 22 23 24 25 26 27 28 29 H'00001C H'000040 H'000044 H'000048 H'00004C H'000050 H'000054 H'000058 H'00005C H'000060 H'000064 H'000068 H'00006C H'000070 H'000074 ICRA7 ICRA6 ICRA5 ICRA4 ICRA3 ICRA1 ICRA0 Low
Name NMI IRQ0 IRQ1 IRQ2 IRQ3 IRQ4 IRQ5 IRQ6 IRQ7
Priority High
WDT Refresh timer
Reserved for system use WOVI0 (Interval timer) CMI (Compare match) Address break Reserved for system use
Rev. 2.00, 03/04, page 70 of 534
Origin of Interrupt Source External pin DMAC
Name SUSRI (Suspend recover interrupt) Reserved for system use DEND0 DEND1 DEND2 DEND3 Reserved for system use CMIA0 (Compare match A) CMIB0 (Compare match B) OVI0 (Overflow) Reserved for system use CMIA1 (Compare match A) CMIB1 (Compare match B) OVI1 (Overflow) Reserved for system use Reserved for system use ERI0 (Reception error 0) RXI0 (Reception completion 0) TXI0 (Transmission data empty 0) TEI0 (Transmission end 0) Reserved for system use USBI1 USBI0 USBI2 Reserved for system use
Vector Number Vector Address ICR 30 31 to 33 34 35 36 37 38 to 63 64 65 66 67 68 69 70 71 72 to 79 80 81 82 83 84 to 107 108 109 110 111 H'000078 H'00007C to H'000084 H'000088 H'00008C H'000090 H'000094 H'000098 to H'0000FC H'000100 H'000104 H'000108 H'00010C H'000110 H'000114 H'000118 H'00011C H'000120 to H'00013C H'000140 H'000144 H'000148 H'00014C H'000150 to H'0001AC H'0001B0 H'0001B4 H'0001B8 H'0001BC ICRB6 ICRB5
Priority High
TMR_0
ICRB3
TMR_1
ICRB2
SCI
ICRC7
USB2
ICRC0
Low
Rev. 2.00, 03/04, page 71 of 534
5.6
Interrupt Control Modes and Interrupt Operation
The interrupt controller has two modes: Interrupt control mode 0 and interrupt control mode 1. Interrupt operations differ depending on the interrupt control mode. NMI interrupts and address break interrupts are always accepted except for in reset state or in hardware standby mode. The interrupt control mode is selected by SYSCR. Table 5.4 shows the interrupt control modes. Table 5.4 Interrupt Control Modes
Priority Setting Registers ICR Interrupt Mask Bits I
Interrupt SYSCR Control Mode INTM1 INTM0 0 0 0
Description Interrupt mask control is performed by the I bit. Priority levels can be set with ICR. 3-level interrupt mask control is performed by the I bit. Priority levels can be set with ICR.
1
1
ICR
I, UI
Figure 5.3 shows a block diagram of the priority decision circuit.
I UI
ICR
Interrupt source
Interrupt acceptance control and 3-level mask control
Default priority determination
Vector number
Interrupt control modes 0 and 1
Figure 5.3 Block Diagram of Interrupt Control Operation
Rev. 2.00, 03/04, page 72 of 534
Interrupt Acceptance Control and 3-Level Control: In interrupt control modes 0 and 1, interrupt acceptance control and 3-level mask control is performed by means of the I and UI bits in CCR and ICR (control level). Table 5.5 shows the interrupts that can be accepted in each interrupt control mode. Table 5.5 Interrupts Acceptable in Each Interrupt Control Mode
UI Bit 0 1 [Legend] : Note: * NMI, Address Break Peripheral Module Interrupt O O O O O O (All interrupts)* X O (All interrupts)* O (Interrupts with ICR = 1) X
Interrupt Control Mode I Bit 0 0 1 1 0 1
Don't care Interrupt control level 1 has priority.
Default Priority Determination: The priority is determined for the selected interrupt, and a vector number is generated. If the same value is set for ICR, acceptance of multiple interrupts is enabled, and so only the interrupt source with the highest priority according to the preset default priorities is selected and has a vector number generated. Interrupt sources with a lower priority than the accepted interrupt source are held pending. Table 5.6 shows operations and control signal functions in each interrupt control mode. Table 5.6
Interrupt Control Mode 0 1
Operations and Control Signal Functions in Each Interrupt Control Mode
Setting INTM1 INTM0 0 0 1 O O Interrupt Acceptance Control 3-Level Control I IM IM UI IM ICR PR PR Default Priority Determination O O T (Trace)
[Legend] O: Interrupt operation control performed IM: Used as an interrupt mask bit PR: Sets priority : Not used
Rev. 2.00, 03/04, page 73 of 534
5.6.1
Interrupt Control Mode 0
In interrupt control mode 0, interrupt requests other than NMI and address break are masked by ICR and the I bit of the CCR in the CPU. The interrupt requests are held pending when the I bit is set to 1. Figure 5.4 shows a flowchart of the interrupt acceptance operation. 1. If an interrupt source occurs when the corresponding interrupt enable bit is set to 1, an interrupt request is sent to the interrupt controller. 2. According to the interrupt control level specified in ICR, the interrupt controller only accepts an interrupt request with interrupt control level 1 (priority), and holds pending an interrupt request with interrupt control level 0 (no priority). If several interrupt requests are issued, an interrupt request with the highest priority is accepted according to the priority order, an interrupt handling is requested to the CPU, and other interrupt requests are held pending. 3. If the I bit in CCR is set to 1, only NMI and address break interrupts are accepted by the interrupt controller, and other interrupt requests are held pending. If the I bit is cleared to 0, any interrupt request is accepted. 4. When the CPU accepts an interrupt request, it starts interrupt exception handling after execution of the current instruction has been completed. 5. The PC and CCR are saved to the stack area by interrupt exception handling. The PC saved on the stack shows the address of the first instruction to be executed after returning from the interrupt handling routine. 6. Next, the I bit in CCR is set to 1. This masks all interrupts except for NMI and address break interrupts. 7. The CPU generates a vector address for the accepted interrupt and starts execution of the interrupt handling routine at the address indicated by the contents of the vector address in the vector table.
Rev. 2.00, 03/04, page 74 of 534
Program execution state
Interrupt generated? Yes Yes
No
NMI No
An interrupt with interrupt control level 1?
No
Hold pending
Yes No IRQ0 Yes No IRQ1 Yes USBI2 Yes IRQ0 Yes IRQ1 Yes USBI2 Yes No No
I=0 Yes
No
Save PC and CCR
I
1
Read vector address
Branch to interrupt handling routine
Figure 5.4 Flowchart of Procedure up to Interrupt Acceptance in Interrupt Control Mode 0
Rev. 2.00, 03/04, page 75 of 534
5.6.2
Interrupt Control Mode 1
In interrupt control mode 1, mask control is applied to three levels for IRQ and on-chip peripheral module interrupt requests by comparing the I and UI bits in CCR in the CPU, and the ICR setting. The interrupt requests are held pending when the I bit is set to 1. 1. An interrupt request with interrupt control level 0 is accepted when the I bit in CCR is cleared to 0. When the I bit is set to 1, the interrupt request is held pending. 2. An interrupt request with interrupt control level 1 is accepted when the I bit or UI bit in CCR is cleared to 0. When both I and UI bits are set to 1, the interrupt request is held pending. For instance, the state transition when the interrupt enable bit corresponding to each interrupt is set to 1, and ICRA to ICRC are set to H'20, H'00, and H'00, respectively (IRQ2 and IRQ3 interrupts are set to interrupt control level 1, and other interrupts are set to interrupt control level 0) is shown below. Figure 5.5 shows a state transition diagram. 1. All interrupt requests are accepted when I = 0. (Priority order: NMI > IRQ2 > IRQ3 > IRQ0 > IRQ1 > address break …) 2. Only NMI, IRQ2, IRQ3, and address break interrupt requests are accepted when I = 1 and UI = 0. 3. Only NMI and address break interrupt requests are accepted when I = 1 and UI = 1.
I
0 0
All interrupt requests are accepted
I
1, UI
Only NMI, address break, and interrupt control level 1 interrupt requests are accepted
I Exception handling execution or I 1, UI 1
0
UI
0 Exception handling execution or UI 1
Only NMI and address break interrupt requests are accepted
Figure 5.5 State Transition in Interrupt Control Mode 1
Rev. 2.00, 03/04, page 76 of 534
Figure 5.6 shows a flowchart of the interrupt acceptance operation. 1. If an interrupt source occurs when the corresponding interrupt enable bit is set to 1, an interrupt request is sent to the interrupt controller. 2. According to the interrupt control level specified in ICR, the interrupt controller only accepts an interrupt request with interrupt control level 1 (priority), and holds pending an interrupt request with interrupt control level 0 (no priority). If several interrupt requests are issued, an interrupt request with the highest priority is accepted according to the priority order, an interrupt handling is requested to the CPU, and other interrupt requests are held pending. 3. An interrupt request with interrupt control level 1 is accepted when the I bit is cleared to 0, or when the I bit is set to 1 while the UI bit is cleared to 0. An interrupt request with interrupt control level 0 is accepted when the I bit is cleared to 0. When the I bit is set to 1, only an NMI or address break interrupt request is accepted, and other interrupts are held pending. When both the I and UI bits are set to 1, only an NMI or address break interrupt request is accepted, and other interrupts are held pending. When the I bit is cleared to 0, the UI bit is not affected. 4. When the CPU accepts an interrupt request, it starts interrupt exception handling after execution of the current instruction has been completed. 5. The PC and CCR are saved to the stack area by interrupt exception handling. The PC saved on the stack shows the address of the first instruction to be executed after returning from the interrupt handling routine. 6. The I and UI bits in CCR are set to 1. This masks all interrupts except for an NMI or address break interrupt. 7. The CPU generates a vector address for the accepted interrupt and starts execution of the interrupt handling routine at the address indicated by the contents of the vector address in the vector table.
Rev. 2.00, 03/04, page 77 of 534
Program excution state No
Interrupt generated? Yes Yes
NMI No
An interrupt with interrupt control level 1?
No
Hold pending
Yes No No IRQ1 Yes No IRQ0 Yes IRQ1 Yes No
IRQ0 Yes
USBI2
Yes
USBI2
Yes
I=0
Yes
No
I=0 No Yes
No
UI = 0 Yes
Save PC and CCR
I
1, UI
1
Read vector address Branch to interrupt handling routine
Figure 5.6 Flowchart of Procedure Up to Interrupt Acceptance in Interrupt Control Mode 1 5.6.3 Interrupt Exception Handling Sequence
Figure 5.7 shows the interrupt exception handling sequence. The example shown is for the case where interrupt control mode 0 is set in advanced mode, and the program area and stack area are in on-chip memory.
Rev. 2.00, 03/04, page 78 of 534
Interrupt is accepted
Interrupt level decision and wait for end of instruction Instruction prefetch Stack access Vector fetch Internal processing
Internal processing
Prefetch of instruction in interrupt-handling routine
φ
Interrupt request signal
Internal address bus
(1)
(3)
(5)
(7)
(9)
(11)
(13)
Internal read signal
Internal write signal
Figure 5.7 Interrupt Exception Handling
(2)
Internal data bus
(4)
(6)
(8)
(10)
(12)
(14)
(1) Instruction prefetch address (Instruction is not executed. Address is saved as PC contents, becoming return address.) Instruction code (not executed) Instruction prefetch address (Instruction is not executed.) SP – 2 SP – 4
Rev. 2.00, 03/04, page 79 of 534
(2) (4) (3) (5) (7)
(6) (8) (9) (11) (10) (12) (13) (14)
Saved PC and CCR Vector address Starting address of interrupt-handling routine (contents of vector address) Starting address of interrupt-handling routine ((13) = (10) (12)) First instruction in interrupt-handling routine
5.6.4
Interrupt Response Times
Table 5.7 shows interrupt response times − the intervals between generation of an interrupt request and execution of the first instruction in the interrupt handling routine. The execution status symbols used in table 5.7 are explained in table 5.8. Table 5.7
No. 1 2 3 4 5 6
Interrupt Response Times
Advanced Mode
1
Execution Status Interrupt priority determination*
3 1 to (19 + 2·SI) 2·SK 2·SI
Number of wait states until executing instruction ends*2 PC, CCR stack save Vector fetch Instruction fetch*
3 4
2·SI 2 12 to 32
Internal processing*
Total (using on-chip memory) Notes: 1. 2. 3. 4.
Two states in case of internal interrupt. Refers to MULXS and DIVXS instructions. Prefetch after interrupt acceptance and prefetch of interrupt handling routine. Internal processing after interrupt acceptance and internal processing after vector fetch.
Table 5.8
Number of States in Interrupt Handling Routine Execution Status
Object of Access External Device 8-Bit Bus 16-Bit Bus 2-State Access 2 3-State Access 3+m
Symbol Instruction fetch SI Branch address read SJ Stack manipulation SK
Internal Memory 1
2-State Access 4
3-State Access 6 + 2m
[Legend] m: Number of wait states in external device access.
Rev. 2.00, 03/04, page 80 of 534
5.7
5.7.1
Usage Notes
Conflict between Interrupt Generation and Disabling
When an interrupt enable bit is cleared to 0 to disable interrupt requests, the disabling becomes effective after execution of the instruction. When an interrupt enable bit is cleared to 0 by an instruction such as BCLR or MOV, and if an interrupt is generated during execution of the instruction, the interrupt concerned will still be enabled on completion of the instruction, so interrupt exception handling for that interrupt will be executed on completion of the instruction. However, if there is an interrupt request of higher priority than that interrupt, interrupt exception handling will be executed for the higher-priority interrupt, and the lower-priority interrupt will be ignored. The same rule is also applied when an interrupt source flag is cleared to 0. Figure 5.8 shows an example in which the CMIEA bit in the TMR's TCR register is cleared to 0. The above conflict will not occur if an enable bit or interrupt source flag is cleared to 0 while the interrupt is masked.
TCR write cycle by CPU
CMIA exception handling
φ
Internal address bus
TCR address
Internal write signal
CMIEA
CMFA
CMIA interrupt signal
Figure 5.8 Conflict between Interrupt Generation and Disabling
Rev. 2.00, 03/04, page 81 of 534
5.7.2
Instructions that Disable Interrupts
The instructions that disable interrupts are LDC, ANDC, ORC, and XORC. After any of these instructions are executed, all interrupts including NMI are disabled and the next instruction is always executed. When the I bit or UI bit is set by one of these instructions, the new value becomes valid two states after execution of the instruction ends. 5.7.3 Interrupts during Execution of EEPMOV Instruction
Interrupt operation differs between the EEPMOV.B instruction and the EEPMOV.W instruction. With the EEPMOV.B instruction, an interrupt request (including NMI) issued during the transfer is not accepted until the move is completed. With the EEPMOV.W instruction, if an interrupt request is issued during the transfer, interrupt exception handling starts at a break in the transfer cycle. The PC value saved on the stack in this case is the address of the next instruction. Therefore, if an interrupt is generated during execution of an EEPMOV.W instruction, the following coding should be used.
L1: EEPMOV.W MOV.W BNE R4,R4 L1
Rev. 2.00, 03/04, page 82 of 534
Section 6 Bus Controller (BSC)
This LSI has an on-chip bus controller (BSC) that manages the external address space divided into four areas. The bus specifications such as the bus width and number of access states can be set independently for each area. Therefore multiple memories and external I/O devices can be connected easily to each area. The bus controller also has a bus arbitration function, and controls the operation of the bus mastersthe CPU and DMA controller (DMAC). A block diagram of the bus controller is shown in figure 6.1.
6.1
Features
• Manages external address space in area units Manages the external address space divided into four areas of 2/10 Mbytes Bus specifications can be set independently for each area DRAM interface can be set • Basic bus interface Chip select signals (CS0 to CS3) can be output for areas 0 to 3 8-bit access or 16-bit access can be selected for each area 2-state access or 3-state access can be selected for each area Program wait states can be inserted for each area CS assertion period extend states can be inserted for each area • DRAM interface DRAM interface can be set for area 2 Multiplex output of row/column address (8/9/10/11 bits) Byte and word control by CAS2 method Burst operation can be performed in high-speed page mode Tp cycle insertion to ensure RAS precharge time CAS before RAS refresh (CBR refresh) or self refresh can be selected • Idle cycle insertion Idle cycles can be inserted when external read cycles between different areas are continued Idle cycles can be inserted when write cycles are continued after a read cycle Idle cycles can be inserted when accesses between different areas are continued • Write buffer function An external write cycle and internal access can be executed in parallel DMAC single address mode and internal access can be executed in parallel
Rev. 2.00, 03/04, page 83 of 534
• Bus arbitration function Includes a bus arbiter that arbitrates bus mastership between the CPU and DMAC • Others A refresh counter (refresh timer) can be used as an interval timer
Internal address bus
Area decoder
CS3 to CS0
External bus controller
Internal bus control signals Internal bus controller CPU bus request signal DMAC bus request signal CPU bus acknowledge signal DMAC bus acknowledge signal
Internal bus arbiter
Control registers Internal data bus ACSCR CSACR WTCR BCR RDNCR [Legend] ACSCR : CSACR : WTCR : BCR : RDNCR : DRAMCR : DRACCR : REFCR : RTCNT : RTCOR : DRAMCR DRACCR REFCR RTCNT RTCOR
Access control register CS assertion period control register Wait control register Bus control register Read strobe timing control register DRAM control register DRAM access control register Refresh control register Refresh timer counter Refresh time constant register
Figure 6.1 Block Diagram of Bus Controller
Rev. 2.00, 03/04, page 84 of 534
6.2
Input/Output Pins
Table 6.1 shows the pin configuration of the bus controller. Table 6.1
Name Address strobe
Pin Configuration
Symbol AS I/O Output Function Strobe signal indicating that normal space is accessed and address output on address bus is enabled. Strobe signal indicating that normal space is being read. Strobe signal indicating that normal space is written to, and upper half (D15 to D8) of data bus is enabled. Strobe signal indicating that normal space is written to, and lower half (D7 to D0) of data bus is enabled. Strobe signal indicating that area 0 is selected. Strobe signal indicating that area 1 is selected Strobe signal indicating that area 2 is selected/DRAM row address strobe signal Strobe signal indicating that area 3 is selected. 16-bit DRAM space upper column address strobe signal or 8-bit DRAM space column address strobe signal 16-bit DRAM space lower column address strobe signal Data transfer acknowledge signal for single address transfer by DMAC channel 3. Data transfer acknowledge signal for single address transfer by DMAC channel 2. Data transfer acknowledge signal for single address transfer by DMAC channel 1. Data transfer acknowledge signal for single address transfer by DMAC channel 0.
Read High write
RD HWR
Output Output
Low write
LWR
Output
Chip select 0 Chip select 1 Chip select 2/ row address strobe Chip select 3 Upper column address strobe
CS0 CS1 CS2/ RAS CS3 UCAS
Output Output Output Output Output
Lower column address strobe Data transfer acknowledge 3 (DMAC) Data transfer acknowledge 2 (DMAC) Data transfer acknowledge 1 (DMAC) Data transfer acknowledge 0 (DMAC)
LCAS DACK3 DACK2 DACK1 DACK0
Output Output Output Output Output
Rev. 2.00, 03/04, page 85 of 534
6.3
Register Descriptions
The bus controller has the following registers. • • • • • • • • • • Access control register (ACSCR) CS assertion period control register (CSACR) Wait control register (WTCR) Bus control register (BCR) Read strobe timing control register (RDNCR) DRAM control register (DRAMCR) DRAM access control register (DRACCR) Refresh control register (REFCR) Refresh timer counter (RTCNT) Refresh time constant register (RTCOR)
Rev. 2.00, 03/04, page 86 of 534
6.3.1
Access Control Register (ACSCR)
ACSCR designates each area in the external address space as either 8-bit access space or 16-bit access space. ACSCR designates each area in the external address space as either 2-state access space or 3-state access space. ACSCR is initialized to H'FF at a reset or in hardware standby mode but not initialized in software standby mode.
Bit 7 6 5 4 Bit Name ABW3 ABW2 ABW1 ABW0 Initial Value 1 1 1 1 R/W R/W R/W R/W R/W Description Area 3 to 0 Bus Width Control These bits select whether the corresponding area is to be designated as 8-bit access space or 16-bit access space. 0: Area n is designated as 16-bit access space 1: Area n is designated as 8-bit access space 3 2 1 0 AST3 AST2 AST1 AST0 1 1 1 1 R/W R/W R/W R/W Area 3 to 0 Access State Control These bits select whether the corresponding area is to be designated as 2-state access space or 3-state access space. Wait state insertion is enabled or disabled at the same time. 0: Area n is designated as 2-state access space Wait state insertion in area n access is disabled 1: Area n is designated as 3-state access space Wait state insertion in area n access is enabled (n = 3 to 0)
Rev. 2.00, 03/04, page 87 of 534
6.3.2
CS Assertion Period Control Register (CSACR)
CSACR selects whether or not the assertion period of the basic bus interface chip select signals (CSn) and address signals is to be extended. Extending the assertion period of the CSn and address signals allows flexible interfacing to external I/O devices.
Bit 7 6 5 4 Bit Name CSXH3 CSXH2 CSXH1 CSXH0 Initial Value 0 0 0 0 R/W R/W R/W R/W R/W Description CS and Address Signal Assertion Period Control 1 These bits specify whether or not the Th cycle is to be inserted (see figure 6.2). When an area for which the CSXHn bit is set to 1 is accessed, a one-state Th cycle, in which only the CSn and address signals are asserted, is inserted before the normal access cycle. 0: In area n basic bus interface access, the CSn and address assertion period (Th) is not extended 1: In area n basic bus interface access, the CSn and address assertion period (Th) is extended CS and Address Signal Assertion Period Control 2 These bits specify whether or not the Tt cycle is to be inserted (see figure 6.2). When an area for which the CSXTn bit is set to 1 is accessed, a one-state Tt cycle, in which only the CSn and address signals are asserted, is inserted before the normal access cycle. 0: In area n basic bus interface access, the CSn and address assertion period (Tt) is not extended 1: In area n basic bus interface access, the CSn and address assertion period (Tt) is extended (n = 3 to 0)
3 2 1 0
CSXT3 CSXT2 CSXT1 CSXT0
0 0 0 0
R/W R/W R/W R/W
Rev. 2.00, 03/04, page 88 of 534
Bus cycle
Th
T1
T2
T3
Tt
Address
Read (when RDNn = 0) Data bus Read data
,
Write Data bus Write data
Note: n = 3 to 0
Figure 6.2 CS and Address Assertion Period Extension (Example of 3-State Access Space and RDNn = 0)
Rev. 2.00, 03/04, page 89 of 534
6.3.3
Wait Control Register (WTCR)
WTCR selects the number of program wait states for each area in the external address space.
Bit 15 14 13 12 Bit Name W32 W31 W30 Initial Value 0 1 1 1 R/W R R/W R/W R/W Description Reserved This bit is always read as 0 and cannot be modified. Area 3 Wait Control 2 to 0 These bits select the number of program wait states when accessing area 3 while AST3 bit in ACSCR = 1. 000: Program wait not inserted 001: 1 program wait state inserted 010: 2 program wait states inserted 011: 3 program wait states inserted 100: 4 program wait states inserted 101: 5 program wait states inserted 110: 6 program wait states inserted 111: 7 program wait states inserted 11 10 9 8 W22 W21 W20 0 1 1 1 R R/W R/W R/W Reserved This bit is always read as 0 and cannot be modified. Area 2 Wait Control 2 to 0 These bits select the number of program wait states when accessing area 2 while AST2 bit in ACSCR = 1. 000: Program wait not inserted 001: 1 program wait state inserted 010: 2 program wait states inserted 011: 3 program wait states inserted 100: 4 program wait states inserted 101: 5 program wait states inserted 110: 6 program wait states inserted 111: 7 program wait states inserted 7 0 R Reserved This bit is always read as 0 and cannot be modified.
Rev. 2.00, 03/04, page 90 of 534
Bit 6 5 4
Bit Name W12 W11 W10
Initial Value 1 1 1
R/W R/W R/W R/W
Description Area 1 Wait Control 2 to 0 These bits select the number of program wait states when accessing area 1 while AST1 bit in ACSCR = 1. 000: Program wait not inserted 001: 1 program wait state inserted 010: 2 program wait states inserted 011: 3 program wait states inserted 100: 4 program wait states inserted 101: 5 program wait states inserted 110: 6 program wait states inserted 111: 7 program wait states inserted
3 2 1 0
W02 W01 W00
0 1 1 1
R R/W R/W R/W
Reserved This bit is always read as 0 and cannot be modified. Area 0 Wait Control 2 to 0 These bits select the number of program wait states when accessing area 0 while AST0 bit in ACSCR = 1. 000: Program wait not inserted 001: 1 program wait state inserted 010: 2 program wait states inserted 011: 3 program wait states inserted 100: 4 program wait states inserted 101: 5 program wait states inserted 110: 6 program wait states inserted 111: 7 program wait states inserted
Rev. 2.00, 03/04, page 91 of 534
6.3.4
Bus Control Register (BCR)
BCR is used for idle cycle settings and enabling or disabling of the write data buffer function.
Bit 15 to 9 Bit Name Initial Value All 0 R/W R/W Description Reserved These bits can be read from or written to. However, the write value should always be 0. Write Data Buffer Enable The write data buffer function can be used for an external write cycle or DMAC single address transfer cycle. 0: Write data buffer function not used 1: Write data buffer function used 7 to 4 All 0 R/W Reserved These bits can be read from or written to. However, the write value should always be 0. Idle Cycle Enable These bits enable the idle cycle insertion. 00: Idle cycle insertion is disabled. 01: When read accesses to different areas are continued or external accesses are continued after a single address transfer, idle cycle insertion is enabled. 10: When read accesses to different areas are continued, external accesses are continued after a single address transfer, or write accesses are continued after a read, idle cycle insertion is enabled. 11: When read accesses to different areas are continued, external accesses are continued after a single address transfer, write accesses are continued after a read, or read accesses are continued after a write, idle cycle insertion is enabled. 1 0 IDLC1 IDLC0 0 0 R/W R/W Idle Cycle State Number Select These bits specify the number of idle cycle states to be inserted. 00: 1 state 01: 2 states 10: 3 states 11: 4 states Rev. 2.00, 03/04, page 92 of 534
8
WDBE
0
R/W
3 2
IDLE1 IDLE0
0 0
R/W R/W
6.3.5
Read Strobe Timing Control Register (RDNCR)
RDNCR selects the read strobe signal (RD) negation timing in a read access to normal space.
Bit 7 6 5 4 Bit Name RDN3 RDN2 RDN1 RDN0 Initial Value 0 0 0 0 R/W R/W R/W R/W R/W Description Read Strobe Timing Control 3 to 0 These bits set the negation timing of the read strobe in a corresponding area read access. As shown in figure 6.3, the read strobe for an area for which the RDNn bit is set to 1 is negated one half-state earlier than that for an area for which the RDNn bit is cleared to 0. The read data setup and hold time specifications are also one half-state earlier. 0: In an area n read access, the RD is negated at the end of the read cycle 1: In an area n read access, the RD is negated one half-state before the end of the read cycle (n = 3 to 0) Reserved These bits can be read from or written to. However, the write value should always be 0.
3 to 0
All 0
R/W
Bus cycle
T1
T2
T3
RDNn = 0
Data
RDNn = 1
Data
Legend n = 3 to 0
Figure 6.3 Read Strobe Negation Timing (Example of 3-State Access Space)
Rev. 2.00, 03/04, page 93 of 534
6.3.6
DRAM Control Register (DRAMCR)
DRAMCR is used to make DRAM interface settings.
Bit 15 Bit Name Initial Value 0 R/W R/W Description Reserved This bit can be read from or written to. However, the write value should always be 0. 14 RAST 0 R/W RAS Assertion Timing Select Selects whether, in DRAM access, the RAS signal is asserted from the start of the Tr cycle (rising edge of φ) or from the falling edge of φ. Figure 6.4 shows the relationship between the RAST bit setting and the RAS assertion timing. 0: RAS is asserted from φ falling edge in Tr cycle 1: RAS is asserted from start of Tr cycle 13 0 R/W Reserved This bit can be read from or written to. However, the write value should always be 0. 12 CAST 0 R/W Column Address Output Cycle Number Select Selects whether the column address output cycle in DRAM access comprises 3 states or 2 states. 0: Column address output cycle comprises 2 states 1: Column address output cycle comprises 3 states 11 to 9 All 0 R/W Reserved These bits can be read from or written to. However, the write value should always be 0. 8 DSET 0 R/W DRAM Space Setting Specifies area 2 as DRAM space. 0: Area 2 is specified as normal space 1: Area 2 is specifies as DRAM space 7 BE 0 R/W Burst Access Enable Selects enabling or disabling of burst access to areas designated as DRAM space. DRAM space burst access is performed in fast page mode. When using EDO page mode DRAM, the RD signal must be connected as the OE signal. 0: Full access 1: Access in fast page mode
Rev. 2.00, 03/04, page 94 of 534
Bit 6
Bit Name RCDM
Initial Value 0
R/W R/W
Description RAS Down Mode When access to DRAM space is interrupted by an access to normal space, an access to an internal I/O register, etc., this bit selects whether the RAS signal is held low while waiting for the next DRAM access (RAS down mode), or is driven high again (RAS up mode). The setting of this bit is valid only when the BE bit is set to 1. If this bit is cleared to 0 when set to 1 in the RAS down state, the RAS down state is cleared at that point, and RAS goes high. When using DRAM interface in RAS down mode and RAS down state is not continued, a 1-state idle cycle is inserted to drive RAS signal high. 0: RAS up mode selected for DRAM space access 1: RAS down mode selected for DRAM space access
5
DDS
0
R/W
DMAC Single Address Transfer Option Selects whether full access is always performed or burst access is enabled when DMAC single address transfer is performed on the DRAM interface. When the BE bit is cleared to 0 in DRAMCR, disabling DRAM burst access, DMAC single address transfer is performed in full access mode regardless of the setting of this bit. This bit has no effect on other bus master external accesses or DMAC dual address transfers. If this bit is set to 1, the DACK output timing is changed. 0: Full access is always executed 1: Burst access is enabled
4, 3
All 0
R/W
Reserved These bits can be read from or written to. However, the write value should always be 0.
Rev. 2.00, 03/04, page 95 of 534
Bit 2 1 0
Bit Name MXC2 MXC1 MXC0
Initial Value 0 0 0
R/W R/W R/W R/W
Description Address Multiplex Select These bits select the size of the shift toward the lower half of the row address in row address/column address multiplexing. In burst operation on the DRAM interface, these bits also select the row address bits to be used for comparison. 000: 8-bit shift • • When 8-bit access space is designated: Row address bits A23 to A8 used for comparison When 16-bit access space is designated: Row address bits A23 to A9 used for comparison 001: 9-bit shift • • When 8-bit access space is designated: Row address bits A23 to A9 used for comparison When 16-bit access space is designated: Row address bits A23 to A10 used for comparison 010: 10-bit shift • • When 8-bit access space is designated: Row address bits A23 to A10 used for comparison When 16-bit access space is designated: Row address bits A23 to A11 used for comparison 011: 11-bit shift • When 8-bit access space is designated: Row address bits A23 to A11 used for comparison When 16-bit access space is designated: Row address bits A23 to A12 used for comparison
Rev. 2.00, 03/04, page 96 of 534
Bus cycle
Tp
Tr
Tc1
Tc2
Address RAST = 0 RAS
RAST = 1 RAS
Row address
Column address
UCAS, LCAS
Figure 6.4 RAS Signal Assertion Timing (2-State Column Address Output Cycle, Full Access) 6.3.7 DRAM Access Control Register (DRACCR)
DRACCR is used to set the DRAM interface bus specifications.
Bit 7, 6 Bit Name Initial Value All 0 R/W R/W Description Reserved These bits can be read from or written to. However, the write value should always be 0. 5 4 TPC1 TPC0 0 0 R/W R/W Precharge State Control These bits select the number of states in the RAS precharge cycle in normal access and refreshing. 00: 1 state 01: 2 states 10: 3 states 11: 4 states 3, 2 All 0 R/W Reserved These bits can be read from or written to. However, the write value should always be 0.
Rev. 2.00, 03/04, page 97 of 534
Bit 1 0
Bit Name RCD1 RCD0
Initial Value 0 0
R/W R/W R/W
Description RAS-CAS Wait Control These bits select a wait cycle to be inserted between the RAS assert cycle and CAS assert cycle. 00: Wait cycle not inserted 01: 1-state wait cycle inserted 10: 2-state wait cycle inserted 11: 3-state wait cycle inserted
6.3.8
Refresh Control Register (REFCR)
REFCR specifies DRAM interface refresh control.
Bit 15 Bit Name CMF Initial Value 0 R/W Description
R/(W)* Compare Match Flag Status flag that indicates a match between the values of RTCNT and RTCOR. [Clearing conditions] • • When 0 is written to CMF after reading CMF = 1 while the RFSHE bit is cleared to 0 When CBR refreshing is executed while the RFSHE bit is set to 1
[Setting condition] When RTCOR = RTCNT 14 CMIE 0 R/W Compare Match Interrupt Enable Enables or disables interrupt requests (CMI) by the CMF flag when the CMF flag is set to 1. This bit is valid when refresh control is not performed (RFSHE = 0). When the refresh control is performed (RFSHE = 1), this bit is always cleared to 0 and cannot be modified. 0: Interrupt request by CMF flag disabled 1: Interrupt request by CMF flag enabled
Rev. 2.00, 03/04, page 98 of 534
Bit 13 12
Bit Name RCW1 RCW0
Initial Value 0 0
R/W R/W R/W
Description CAS-RAS Wait Control These bits select the number of wait cycles to be inserted between the CAS assert cycle and RAS assert cycle in a DRAM refresh cycle. 00: Wait state not inserted 01: 1 wait state inserted 10: 2 wait states inserted 11: 3 wait states inserted
11
0
R/W
Reserved This bit can be read from or written to. However, the write value should always be 0.
10 9 8
RTCK2 RTCK1 RTCK0
0 0 0
R/W R/W R/W
Refresh Counter Clock Select These bits select the clock to be used to increment the refresh counter. When the input clock is selected with bits RTCK2 to RTCK0, the refresh counter begins counting up. 000: Count operation halted 001: Count on φ/2 010: Count on φ/8 011: Count on φ/32 100: Count on φ/128 101: Count on φ/512 110: Count on φ/2048 111: Count on φ/4096
7
RFSHE
0
R/W
Refresh Control Refresh control can be performed. When refresh control is not performed, the refresh timer can be used as an interval timer. 0: Refresh control is not performed 1: Refresh control is performed
6
0
R/W
Reserved This bit can be read from or written to. However, the write value should always be 0.
Rev. 2.00, 03/04, page 99 of 534
Bit 5 4
Bit Name RLW1 RLW0
Initial Value 0 0
R/W R/W R/W
Description Refresh Cycle Wait Control These bits select the number of wait states to be inserted in a DRAM interface CAS-before-RAS refresh cycle. 00: No wait state inserted 01: 1 wait state inserted 10: 2 wait states inserted 11: 3 wait states inserted
3
SLFRF
0
R/W
Self-Refresh Enable If this bit is set to 1, DRAM self-refresh mode is selected when a transition is made to the software standby state. This bit is valid when the RFSHE bit is set to 1, enabling refresh operations. 0: Self-refreshing is disabled 1: Self-refreshing is enabled
2 1 0
TPCS2 TPCS1 TPCS0
0 0 0
R/W R/W R/W
Self-Refresh Precharge Cycle Control These bits select the number of states in the precharge cycle immediately after self-refreshing. The number of states in the precharge cycle immediately after self-refreshing are added to the number of states set by bits TPC1 and TPC0 in DRACCR. 000: [TPC set value] states 001: [TPC set value + 1] states 010: [TPC set value + 2] states 011: [TPC set value + 3] states 100: [TPC set value + 4] states 101: [TPC set value + 5] states 110: [TPC set value + 6] states 111: [TPC set value + 7] states
Note: Only 0 can be written, to clear the flag.
Rev. 2.00, 03/04, page 100 of 534
6.3.9
Refresh Timer Counter (RTCNT)
RTCNT is an 8-bit readable/writable up-counter. RTCNT counts up using the internal clock selected by bits RTCK2 to RTCK0 in REFCR. When RTCNT matches RTCOR (compare match), the CMF flag in REFCR is set to 1 and RTCNT is cleared to H'00. If the RFSHE bit in REFCR is set to 1 at this time, a refresh cycle is started. If the RFSHE bit is cleared to 0 and the CMIE bit in REFCR is set to 1, a compare match interrupt (CMI) is generated. RTCNT is initialized to H'00 by a reset and in hardware standby mode. It is not initialized in software standby mode. 6.3.10 Refresh Time Constant Register (RTCOR)
RTCOR is an 8-bit readable/writable register that sets the period for compare match operations with RTCNT. The values of RTCOR and RTCNT are constantly compared, and if they match, the CMF flag in REFCR is set to 1 and RTCNT is cleared to H'00. RTCOR is initialized to H'FF by a reset and in hardware standby mode. It is not initialized in software standby mode.
Rev. 2.00, 03/04, page 101 of 534
6.4
6.4.1
Bus Control
Area Division
The bus controller divides the 16-Mbyte address space into areas shown in figure 6.5, and performs bus control for external address space in area units. Chip select signals (CS0 to CS3) can be output for each area.
H'000000 Area 0 (2 Mbytes)
H'200000 Area 1 (2 Mbytes) H'400000 Area 2 (10 Mbytes) H'E00000 Area 3 (2 Mbytes)
H'FFFFFF
Figure 6.5 Area Divisions
Rev. 2.00, 03/04, page 102 of 534
6.4.2
Address Map
Figure 6.6 shows the address format.
A31 to A24
A23 to A21
A20
A19 to A0
Reserved Does not output a signal. CS space Decoded and output CS0 to CS3 signals. A23 A22 A21 Output CS 0 0 0 CS0 0 0 1 CS1 0 1 0 CS2 0 1 1 1 0 0 1 0 1 1 1 0 1 1 1 CS3 Don't care Do not affect the operation.
Output address Signals are output from address pins.
Figure 6.6 Address Format
Rev. 2.00, 03/04, page 103 of 534
Bits A31 to A24 do not affect the operation. Bits A23 to A21 are decoded by the chip select signals (CS3 to CS0) for each area and output. Bit A20 is not output externally. Bits A19 to A0 are output externally. Enabling or disabling external output of bits A19 to A0 can be selected by the setting of PFCR1. For details, refer to section 8.11.1, Port Function Control Register 1 (PFCR1). Table 6.2 and figure 6.7 show the address map. Table 6.2
Address H'000000 to H'1FFFFF H'200000 to H'3FFFFF H'400000 to H'DFFFFF H'E00000 to H'FFFFFF Note: *
Address Map
Space Type CS0 space/ on-chip ROM space CS1 space CS2 space/ DRAM space CS3 space/ on-chip RAM space*/ I/O space Memory Type External space/ on-chip ROM External space External space/ DRAM External space/ on-chip RAM*/I/O space Size 2 Mbytes 2 Mbytes 10 Mbytes 2 Mbytes Bus Width 8/16 8/16 8/16 8/16
On-chip RAM space when the RAME bit in SYSCR is 1.
Rev. 2.00, 03/04, page 104 of 534
H'000000 H'040000
On-chip ROM
Area 0
H'200000
Area 1
H'400000
Area 2
H'E00000
H'FF7000 H'FFF000 On-chip RAM
Area 3
H'FFFC00 H'FFFFFF
I/O
Figure 6.7 Address Map 6.4.3 Bus Specifications
The external address space bus specifications consist of five elements: bus width, number of access states, number of program wait states, read strobe timing, and chip select (CS) assertion period extension states. The bus width and number of access states for on-chip memory and internal I/O registers are fixed, and are not affected by the bus controller. Bus Width: A bus width of 8 or 16 bits can be selected with ACSCR. An area for which an 8-bit bus is selected functions as an 8-bit access space, and an area for which a 16-bit bus is selected functions as a 16-bit access space.
Rev. 2.00, 03/04, page 105 of 534
Number of Access States: Two or three access states can be selected with ACSCR. An area for which 2-state access is selected functions as a 2-state access space, and an area for which 3-state access is selected functions as a 3-state access space. With the DRAM interface, the number of access states may be determined without regard to the setting of ACSCR. When 2-state access space is designated, wait insertion is disabled. When 3-state access space is designated, it is possible to insert program waits by means of WTCR. Number of Program Wait States: When 3-state access space is designated by ACSCR, the number of program wait states to be inserted automatically is selected with WTCR. From 0 to 7 program wait states can be selected. Table 6.3 shows the bus specifications (bus width, and number of access states and program wait states) for each basic bus interface area. Table 6.3 Bus Specifications for Each Area (Basic Bus Interface)
WTCR Wn2 0 Wn1 0 Wn0 0 1 1 0 1 1 0 0 1 1 0 0 0 1 1 0 1 0 1 1 0 1 1 0 0 1 1 Legend n = 3 to 0 0 1 8 2 3 Bus Specifications (Basic Bus Interface) Bus Width 16 Access States 2 3 Program Wait States 0 0 1 2 3 4 5 6 7 0 0 1 2 3 4 5 6 7
ACSCR ABWn 0 ASTn 0 1
Rev. 2.00, 03/04, page 106 of 534
Read Strobe Timing: RDNCR can be used to select either of two negation timings (at the end of the read cycle or one half-state before the end of the read cycle) for the read strobe (RD) used in the basic bus interface space. Chip Select (CS) Assertion Period Extension States: Some external I/O devices require a setup time and hold time between address and CS signals and strobe signals such as RD, HWR, and LWR. CSACR can be used to insert states in which only the CS, AS, and address signals are asserted before and after a basic bus space access cycle. 6.4.4 Memory Interfaces
The memory interfaces in this LSI comprise a basic bus interface that allows direct connection of ROM, SRAM, and so on; and a DRAM interface that allows direct connection of DRAM. The interface can be selected independently for each area. An area for which the basic bus interface is designated functions as normal space and an area for which the DRAM interface is designated functions as DRAM space The initial state of each area is basic bus interface, 3-state access space. The initial bus width is 8 bits. Area 0: Area 0 includes on-chip ROM and the space excluding on-chip ROM is external address space by setting the EXPE bit in MDCR to 1. When area 0 external space is accessed, the CS0 signal can be output. Only basic bus interface can be used for area 0. Area 1: All of area 1 is external address space by setting the EXPE bit in MDCR to 1. When area 1 external address space is accessed, the CS1 signal can be output. Only basic bus interface can be used for area 1. Area 2: All of area 2 is external address space by setting the EXPE bit in MDCR to 1. When area 2 external space is accessed, signal CS2 can be output. Basic bus interface or DRAM interface can be selected for area 2. With the DRAM interface, the CS2 signal is used as the RAS signal. If area 2 is designated as DRAM space, large-capacity (e.g. 64-Mbit) DRAM can be connected. In this case, the CS2 signal is used as the RAS signal for DRAM space.
Rev. 2.00, 03/04, page 107 of 534
Area 3: Area 3 includes the on-chip RAM and internal I/O registers. The space excluding the onchip RAM and internal I/O registers is external address space by setting the EXPE bit in MDCR to 1. The on-chip RAM is enabled when the RAME bit is set to 1 in the system control register (SYSCR); when the RAME bit is cleared to 0, the on-chip RAM is disabled and the corresponding addresses are in external address space. When area 3 external address space is accessed, the CS3 signal can be output. Only the basic bus interface can be used for the area 3 memory interface. 6.4.5 Chip Select Signals
This LSI can output chip select signals (CS3 to CS0) for areas 3 to 0. The signal outputs low when the corresponding external space area is accessed. Figure 6.8 shows an example of CS3 to CS0 signals output timing. The CS0 pin is placed in the output state by setting the EXPE bit in MDCR to 1. Pins CS3 to CS1 are placed in the input state after a reset and so the corresponding CS output should be enabled by setting the PFCR1 register when outputting signals CS3 to CS1. For details, refer to section 8.11.1, Port Function Control Register 1 (PFCR1). When area 2 is designated as DRAM space, output CS2 is used as the RAS signal.
Bus cycle T1 φ Address bus Area n external address T2 T3
Figure 6.8 CSn Signal Output Timing (n = 3 to 0)
Rev. 2.00, 03/04, page 108 of 534
6.5
Basic Bus Interface
The basic bus interface enables direct connection of ROM, SRAM, and so on. 6.5.1 Data Size and Data Alignment
Data sizes for the CPU and other internal bus masters are byte, word, and longword. The bus controller has a data alignment function, and when accessing external address space, controls whether the upper data bus (D15 to D8) or lower data bus (D7 to D0) is used according to the bus specifications for the area being accessed (8-bit access space or 16-bit access space) and the data size. 8-Bit Access Space: Figure 6.9 illustrates data alignment control for the 8-bit access space. With the 8-bit access space, the upper data bus (D15 to D8) is always used for accesses. The amount of data that can be accessed at one time is one byte: a word access is performed as two byte accesses, and a longword access, as four byte accesses.
Upper data bus
D15
Lower data bus
D0
D8 D7
Byte size
1st bus cycle
2nd bus cycle
1st bus cycle
Word size
Longword size
2nd bus cycle 3rd bus cycle 4th bus cycle
Figure 6.9 Access Sizes and Data Alignment Control (8-Bit Access Space) 16-Bit Access Space: Figure 6.10 illustrates data alignment control for the 16-bit access space. With the 16-bit access space, the upper data bus (D15 to D8) and lower data bus (D7 to D0) are used for accesses. The amount of data that can be accessed at one time is one byte or one word, and a longword access is executed as two word accesses. In byte access, whether the upper or lower data bus is used is determined by whether the address is even or odd. The upper data bus is used for an even address, and the lower data bus for an odd address.
Rev. 2.00, 03/04, page 109 of 534
Upper data bus
D15
Lower data bus
D0
D8 D7
Byte size
Byte size
• Even address
• Odd address
Word size
Longword size
1st bus cycle
2nd bus cycle
Figure 6.10 Access Sizes and Data Alignment Control (16-bit Access Space) 6.5.2 Valid Strobes
Table 6.4 shows the data buses used and valid strobes for the access spaces. In a read, the RD signal is valid for both the upper and the lower half of the data bus. In a write, the HWR signal is valid for the upper half of the data bus, and the LWR signal for the lower half. Table 6.4
Area 8-bit access space 16-bit access space
Data Buses Used and Valid Strobes
Access Size Byte Read/ Write Read Write Byte Read Address Even Odd Write Even Odd Word Read Write HWR LWR RD HWR, LWR Valid Strobe RD HWR RD Valid Invalid Valid Hi-Z Valid Valid Upper Data Bus Lower Data (D15 to D8) Bus (D7 to D0) Valid Invalid Hi-Z Invalid Valid Hi-Z Valid Valid Valid
Note: Hi-Z: High-impedance state Invalid: Input state; input value is ignored.
6.5.3
Basic Timing
8-Bit, 2-State Access Space: Figure 6.11 shows the bus timing for an 8-bit, 2-state access space. When an 8-bit access space is accessed, the upper half (D15 to D8) of the data bus is used.
Rev. 2.00, 03/04, page 110 of 534
When all areas are designated as 8-bit space, the LWR pin can be used as the I/O port. However, when all areas are designated as 16-bit space, the LWR pin is always fixed high. Wait states cannot be inserted.
Bus cycle T1 φ T2
Address bus
Read
D15 to D8
Valid
D7 to D0
Invalid
High Write D15 to D8 Valid
D7 to D0
High impedance
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.11 Bus Timing for 8-Bit, 2-State Access Space
Rev. 2.00, 03/04, page 111 of 534
8-Bit, 3-State Access Space: Figure 6.12 shows the bus timing for an 8-bit, 3-state access space. When an 8-bit access space is accessed, the upper half (D15 to D8) of the data bus is used. When all areas are designated as 8-bit space, the LWR pin can be used as the I/O port. However, when all areas are designated as 16-bit space, the LWR pin is always fixed high. Wait states can be inserted.
Bus cycle T1 φ T2
T3
Address bus
Read
D15 to D8
Valid
D7 to D0
Invalid
High
Write
D15 to D8
Valid
High impedance
D7 to D0
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.12 Bus Timing for 8-Bit, 3-State Access Space
Rev. 2.00, 03/04, page 112 of 534
16-Bit, 2-State Access Space: Figures 6.13 to 6.15 show bus timings for a 16-bit, 2-state access space. When a 16-bit access space is accessed, the upper half (D15 to D8) of the data bus is used for even addresses, and the lower half (D7 to D0) for odd addresses. Wait states cannot be inserted.
Bus cycle T1 φ T2
Address bus
Read
D15 to D8
Valid
D7 to D0
Invalid
High Write
D15 to D8
Valid
D7 to D0
High impedance
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.13 Bus Timing for 16-Bit, 2-State Access Space (Even Address Byte Access)
Rev. 2.00, 03/04, page 113 of 534
Bus cycle T1 φ T2
Address bus
Read
D15 to D8
Invalid
D7 to D0
Valid
High
Write High impedance D15 to D8
D7 to D0
Valid
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.14 Bus Timing for 16-Bit, 2-State Access Space (Odd Address Byte Access)
Rev. 2.00, 03/04, page 114 of 534
Bus cycle T1 φ T2
Address bus
Read
D15 to D8
Valid
D7 to D0
Valid
Write D15 to D8 Valid
D7 to D0
Valid
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.15 Bus Timing for 16-Bit, 2-State Access Space (Word Access)
Rev. 2.00, 03/04, page 115 of 534
16-Bit, 3-State Access Space: Figures 6.16 to 6.18 show bus timings for a 16-bit, 3-state access space. When a 16-bit access space is accessed, the upper half (D15 to D8) of the data bus is used for the even address, and the lower half (D7 to D0) for the odd address. Wait states can be inserted.
Bus cycle T1 φ T2
T3
Address bus
Read
D15 to D8
Valid
D7 to D0
Invalid
High Write
D15 to D8
Valid
High impedance
D7 to D0
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.16 Bus Timing for 16-Bit, 3-State Access Space (Even Address Byte Access)
Rev. 2.00, 03/04, page 116 of 534
Bus cycle T1 φ T2
T3
Address bus
Read
D15 to D8
Invalid
D7 to D0
Valid
High
Write
D15 to D8
High impedance
D7 to D0
Valid
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.17 Bus Timing for 16-Bit, 3-State Access Space (Odd Address Byte Access)
Rev. 2.00, 03/04, page 117 of 534
Bus cycle T1 φ T2 T3
Address bus
Read
D15 to D8
Valid
D7 to D0
Valid
Write D15 to D8 Valid
D7 to D0
Valid
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.18 Bus Timing for 16-Bit, 3-State Access Space (Word Access)
Rev. 2.00, 03/04, page 118 of 534
6.5.4
Wait Control
When accessing external space, this LSI can extend the bus cycle by inserting one or more wait states (Tw). From 0 to 7 wait states can be inserted automatically between the T2 state and T3 state on an individual area basis in 3-state access space, according to the setting of WTCR. Figure 6.19 shows an example of wait state insertion timing. The settings after a reset are: 3-state access and insertion of 7 program wait states.
T1
T2
Tw
Tw
Tw
T3
Address bus
Read Data bus Read data
, Write Data bus Write data
Notes: 1. n = 3 to 0 2. When RDNn = 0
Figure 6.19 Example of Wait State Insertion Timing
Rev. 2.00, 03/04, page 119 of 534
6.5.5
Read Strobe (RD) Timing
The read strobe (RD) timing can be changed for individual areas by setting bits RDN3 to RDN0 to 1 in RDNCR. When the DMAC is used in single address mode, note that if the RD timing is changed by setting RDNn to 1, the RD timing will change relative to the rise of DACK. Figure 6.20 shows an example of the timing when the read strobe timing is changed in basic bus 3state access space.
Bus cycle
T1
φ
T2
T3
Address bus
RDNn = 0 Data bus
RDNn = 1 Data bus
Note: n = 3 to 0
Figure 6.20 Example of Read Strobe Timing
Rev. 2.00, 03/04, page 120 of 534
6.5.6
Extension of Chip Select (CS) Assertion Period
Some external I/O devices require a setup time and hold time between address and CS signals and strobe signals such as RD, HWR, and LWR. Settings can be made in the CSACR register to insert states in which only the CS, AS, and address signals are asserted before and after a basic bus space access cycle. Extension of the CS assertion period can be set for individual areas. With the CS assertion extension period in write access, the data setup and hold times are less stringent since the write data is output to the data bus. Figure 6.21 shows an example of the timing when the CS assertion period is extended in basic bus 3-state access space.
Bus cycle
Th
φ Address bus
T1
T2
T3
Tt
Read (when RDNn = 0)
Data bus
Read data
, Write Data bus Write data
Note: n = 3 to 0
Figure 6.21 Example of Timing when Chip Select Assertion Period is Extended Both extension state Th inserted before the basic bus cycle and extension state Tt inserted after the basic bus cycle, or only one of these, can be specified for individual areas. Insertion or noninsertion can be specified for the Th state with the upper 4 bits (CSXH3 to CSXH0) in the CSACR register, and for the Tt state with the lower 4 bits (CSXT3 to CSXT0).
Rev. 2.00, 03/04, page 121 of 534
6.6
DRAM Interface
In this LSI, external space area 2 can be designated as DRAM space, and DRAM interfacing performed. The DRAM interface allows DRAM to be directly connected to this LSI. A DRAM space of 10 Mbytes can be set by means of bit DSET in DRAMCR. Burst operation is also possible, using fast page mode. 6.6.1 Setting DRAM Space
Area 2 is designated as DRAM space by setting bit DSET in DRAMCR to 1. In DRAM space, the RAS signal is valid. The bus specifications for DRAM space such as the bus width, number of wait states, and so on are determined according to the settings for area 2. 6.6.2 Address Multiplexing
With DRAM space, the row address and column address are multiplexed. In address multiplexing, the size of the shift of the row address is selected with bits MXC2 to MXC0 in DRAMCR. Table 6.5 shows the relation between the settings of bits MXC2 to MXC0 and the shift size. Table 6.5 Relation between Settings of Bits MXC2 to MXC0 and Address Multiplexing
DRAMCR A19 to MXC2 MXC1 MXC0 Shift Size A16 Row address 1 9 bits 0 0 0 8 bits A15 A14 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 Address Pins
A19 to A23 A22 A21 A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A10 A9 A8 A16 A19 to A15 A23 A22 A21 A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A10 A9 A16
1
0
10 bits
A19 to A15 A14 A23 A22 A21 A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A10 A16
1
11 bits
A19 to A15 A14 A13 A23 A22 A21 A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A16
1
Reserved (setting prohibited)
Column address
A19 to A15 A14 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 A16
Rev. 2.00, 03/04, page 122 of 534
6.6.3
Data Bus
If the ABW2 bit in ACSCR is set to 1, that area is designated as 8-bit DRAM space; if the bit is cleared to 0, the area is designated as 16-bit DRAM space. In 16-bit DRAM space, ×16-bit configuration DRAM can be connected directly. In 8-bit DRAM space the upper half of the data bus, D15 to D8, is enabled, while in 16-bit DRAM space both the upper and lower halves of the data bus, D15 to D0, are enabled. Access sizes and data alignment are the same as for the basic bus interface: see section 6.5.1, Data Size and Data Alignment. 6.6.4 Pins Used for DRAM Interface
Table 6.6 shows the pins used for DRAM interfacing and their functions. Although the CS2 pin is in the input state after a reset, the RAS signal is output after the DSET bit in DRAMCR is set and DRAM space is designated. For details, refer to section 8, I/O Ports. Table 6.6
Pin HWR CS2 UCAS
DRAM Interface Pins
With DRAM Setting WE RAS UCAS Name Write enable Row address strobe Upper column address strobe I/O Output Output Output Function Write enable for DRAM space access Row address strobe when area 2 is designated as DRAM space Upper column address strobe for 16-bit DRAM space access or column address strobe for 8bit DRAM space access Lower column address strobe signal for 16-bit DRAM space access Output enable signal for DRAM space access Row address/column address multiplexed output Data input/output pins
LCAS
LCAS
Lower column address strobe Output enable Address pins Data pins
Output
RD A15 to A0 D15 to D0
OE A15 to A0 D15 to D0
Output Output I/O
Rev. 2.00, 03/04, page 123 of 534
6.6.5
Basic Timing
Figure 6.22 shows the basic access timing for DRAM space. The four states of the basic timing consist of one Tp (precharge cycle) state, one Tr (row address output cycle) state, and two Tc1 and Tc2 (column address output cycle) states.
Tp
φ
Tr
Tc1
Tc2
Address bus
Row address
Column address
(
)
,
( Read ( ) ) High
Data bus
( Write ( )
)
High
Data bus
Figure 6.22 DRAM Basic Access Timing (RAST = 0, CAST = 0) When DRAM space is accessed, the RD signal is output as the OE signal for DRAM. When connecting DRAM provided with an EDO page mode, the OE signal should be connected to the (OE) pin of the DRAM.
Rev. 2.00, 03/04, page 124 of 534
6.6.6
Column Address Output Cycle Control
The column address output cycle can be changed from 2 states to 3 states by setting the CAST bit to 1 in DRAMCR. Use the setting that gives the optimum specification values (CAS pulse width, etc.) according to the DRAM connected and the operating frequency of this LSI. Figure 6.23 shows an example of the timing when a 3-state column address output cycle is selected.
Tp
Tr Tc1 Tc2
Tc3
φ Address bus
Row address Column address
(
)
,
( ) )
High
Read
(
Data bus
(
) )
High
Write
(
Data bus
Figure 6.23 Example of Access Timing with 3-State Column Address Output Cycle (RAST = 0)
Rev. 2.00, 03/04, page 125 of 534
6.6.7
Row Address Output State Control
If the RAST bit is set to 1 in DRAMCR, the RAS signal goes low from the beginning of the Tr state, and the row address hold time and DRAM read access time are changed relative to the fall of the RAS signal. Use the optimum setting according to the DRAM connected and the operating frequency of this LSI. Figure 6.24 shows an example of the timing when the RAS signal goes low from the beginning of the Tr state.
Tp
φ
Tr
Tc1
Tc2
Address bus
Row address
Column address
(
)
,
( Read ( ) )
High
Data bus
( Write ( )
) High
Data bus
Figure 6.24 Example of Access Timing when RAS Signal Goes Low from Beginning of Tr State (CAST = 0) If a row address hold time or read access time is necessary, making a setting in bits RCD1 and RCD0 in DRACCR allows from one to three Trw states, in which row address output is maintained, to be inserted between the Tr cycle, in which the RAS signal goes low, and the Tc1 cycle, in which the column address is output. Use the setting that gives the optimum row address signal hold time relative to the falling edge of the RAS signal according to the DRAM connected and the operating frequency of this LSI. Figure 6.25 shows an example of the timing when one Trw state is set.
Rev. 2.00, 03/04, page 126 of 534
Tp
Tr
Trw
Tc1
Tc2
φ Address bus Row address Column address
(
)
, High
( Read ( )
)
Data bus
( Write ( )
) High
Data bus
Figure 6.25 Example of Timing with One Row Address Output Hold State (RAST = 0, CAST = 0)
Rev. 2.00, 03/04, page 127 of 534
6.6.8
Precharge State Control
When DRAM is accessed, a RAS precharge time must be secured. With this LSI, one Tp state is always inserted when DRAM space is accessed. From one to four Tp states can be selected by setting bits TPC1 and TPC0 in DRACCR. Set the optimum number of Tp cycles according to the DRAM connected and the operating frequency of this LSI. Figure 6.26 shows the timing when two Tp states are inserted. The setting of bits TPC1 and TPC0 is also valid for Tp states in refresh cycles.
Tp1
φ Address bus
Row address Column address
Tp2
Tr
Tc1
Tc2
(
)
,
(
) )
High
Read
(
Data bus
(
) )
High
Write
(
Data bus
Figure 6.26 Example of Timing with Two-State Precharge Cycle (RAST = 0, CAST = 0)
Rev. 2.00, 03/04, page 128 of 534
6.6.9
Wait Control
When inserting wait states in a DRAM access cycle, program wait insertion is specified. Wait states are inserted to extend the CAS assertion period in a read access to DRAM space, and to extend the write data setup time relative to the falling edge of CAS in a write access. When the AST2 bit in ACSCR is set to 1, from 0 to 7 wait states can be inserted automatically between the Tc1 state and Tc2 state, according to the settings of WTCR. Figures 6.27 and 6.28 show examples of wait cycle insertion timing in the case of 2-state and 3state column address output cycles.
Tp φ Address bus Row address Column address Tr Tc1 Tw Tw Tc2
, ( Read ( ) )
High
Data bus
,
Write
( ( )
) High
Data bus
Figure 6.27 Example of Wait State Insertion Timing (2-State Column Address Output)
Rev. 2.00, 03/04, page 129 of 534
Tp φ Address bus
Tr
Tc1
Tw
Tw
Tc2
Tc3
Row address
Column address
, ( Read ( ) )
High
Data bus , ( Write ( ) High )
Data bus
Figure 6.28 Example of Wait State Insertion Timing (3-State Column Address Output)
Rev. 2.00, 03/04, page 130 of 534
6.6.10
Byte Access Control
When DRAM with a ×16-bit configuration is connected, the 2-CAS access method is used for the control signals needed for byte access. Figure 6.29 shows the control timing for 2-CAS access, and figure 6.30 shows an example of 2-CAS DRAM connection.
Tp
φ Address bus Row address Column address Tr
Tc1
Tc2
(
)
High ( )
(
)
High
D15 to D8
D7 to D0
Figure 6.29 2-CAS Control Timing (Write Access to Even Address: RAST = 0, CAST = 0)
Rev. 2.00, 03/04, page 131 of 534
This LSI (Address shift size set to 11 bits) RAS (CS2) UCAS LCAS WE RD (OE) A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 D15 to D0
2-CAS type 128-Mbit DRAM 8-Mbyte × 16-bit configuration 11-bit column address RAS UCAS LCAS WE OE A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 D15 to D0 Row address input: A11 to A0 Column address input: A10 to A0
Figure 6.30 Example of 2-CAS DRAM Connection 6.6.11 Burst Operation
With DRAM, in addition to full access (normal access) in which data is accessed by outputting a row address for each access, a fast page mode is also provided which can be used when making consecutive accesses to the same row address. This mode enables fast (burst) access of data by simply changing the column address after the row address has been output. Burst access can be selected by setting the BE bit to 1 in DRAMCR. Burst Access (Fast Page Mode): Figures 6.31 and 6.32 show the operation timing for burst access. When there are consecutive access cycles for DRAM space, the CAS signal and column address output cycles (two states) continue as long as the row address is the same for consecutive access cycles. The row address used for the comparison is set with bits MXC2 to MXC0 in DRAMCR. The bus cycle can also be extended in burst access by inserting wait states. The wait state insertion method and timing are the same as for full access. For details, see section 6.6.9, Wait Control.
Rev. 2.00, 03/04, page 132 of 534
Tp
φ Address bus
Tr
Tc1
Tc2
Tc1
Tc2
Row address
Column address 1 Column address 2
(
, ( Read ( )
)
)
High
Data bus
( ) ) High
Write
(
Data bus
Figure 6.31 Operation Timing in Fast Page Mode (RAST = 0, CAST = 0)
Tp
φ Address bus Row address Column address 1 Column address 2
Tr
Tc1
Tc2
Tc3
Tc1
Tc2
Tc3
(
, ( Read ( )
)
)
High
Data bus
( ) ) High
Write
(
Data bus
Figure 6.32 Operation Timing in Fast Page Mode (RAST = 0, CAST = 1)
Rev. 2.00, 03/04, page 133 of 534
RAS Down Mode and RAS Up Mode: Even when burst operation is selected, it may happen that access to DRAM space is not continuous, but is interrupted by access to another space. In this case, if the RAS signal is held low during the access to the other space, burst operation can be resumed when the same row address in DRAM space is accessed again. • RAS Down Mode To select RAS down mode, set both the RCDM bit and the BE bit to 1 in DRAMCR. If access to DRAM space is interrupted and another space is accessed, the RAS signal is held low during the access to the other space, and burst access is performed when the row address of the next DRAM space access is the same as the row address of the previous DRAM space access. Figure 6.33 shows an example of the timing in RAS down mode. When the row address for the next DRAM space access does not match the row address for the previous DRAM space access and the RAS down state cannot be continued, one-state RAS up cycle (TRU) is inserted immediately before the DRAM access. Figure 6.34 shows an example of the idle cycle insertion when RAS down mode is not continued. Note, however, that the RAS signal will go high if: a refresh operation is initiated in the RAS down state self-refreshing is performed the chip enters software standby mode the RCDM bit or BE bit is cleared to 0
Rev. 2.00, 03/04, page 134 of 534
DRAM space read
Normal space read
DRAM space read
Tp
φ
Tr
Tc1
Tc2
T1
T2
Tc1
Tc2
Address bus
Row address
Column address 1
External address Column address 2
(
)
,
(
)
High
(
)
Data bus
Figure 6.33 Example of Operation Timing in RAS Down Mode (RAST = 0, CAST = 0)
DRAM space read Normal space read DRAM space read
Tp
φ
Tr
Tc1
Tc2
T1
T2
TRU
Tp
Tr
Tc1
Tc2
Address bus
Row address 1
Column address 1 External address
Row address 2
Column address 2
(
)
,
(
)
Data bus
Figure 6.34 Example of Idle Cycle Insertion when RAS Down Mode cannot be Continued
Rev. 2.00, 03/04, page 135 of 534
• RAS Up Mode To select RAS up mode, clear the RCDM bit to 0 in DRAMCR. Each time access to DRAM space is interrupted and another space is accessed, the RAS signal goes high again. Burst operation is only performed if DRAM space is continuous. Figure 6.35 shows an example of the timing in RAS up mode.
DRAM space read Normal space read
DRAM space read
Tp
φ
Tr
Tc1
Tc2
Tc1
Tc2
T1
T2
Address bus
Row address
Column address 1 Column address 2
External address
(
)
,
(
)
High
(
)
Data bus
Figure 6.35 Example of Operation Timing in RAS Up Mode (RAST = 0, CAST = 0)
Rev. 2.00, 03/04, page 136 of 534
6.6.12
Refresh Control
This LSI is provided with a DRAM refresh control function. CAS-before-RAS (CBR) refreshing is used. In addition, self-refreshing can be executed when the chip enters the software standby state. Refresh control is enabled when area 2 is designated as DRAM space in accordance with the setting of bit DSET in DRAMCR. CAS-before-RAS (CBR) Refreshing: To select CBR refreshing, set the RFSHE bit to 1 in REFCR. With CBR refreshing, RTCNT counts up using the input clock selected by bits RTCK2 to RTCK0 in REFCR, and when the count matches the value set in RTCOR (compare match), refresh control is performed. At the same time, RTCNT is reset and starts counting up again from H'00. Refreshing is thus repeated at fixed intervals determined by RTCOR and bits RTCK2 to RTCK0. Set a value in RTCOR and bits RTCK2 to RTCK0 that will meet the refreshing interval specification for the DRAM used. When bits RTCK2 to RTCK0 in REFCR are set, RTCNT starts counting up. RTCNT and RTCOR settings should therefore be completed before setting bits RTCK2 to RTCK0. RTCNT operation is shown in figure 6.36, compare match timing in figure 6.37, and CBR refresh timing in figure 6.38. Access to external space other than DRAM space is not possible in parallel during the CBR refresh period.
RTCNT
RTCOR
H'00 Refresh request
Figure 6.36 RTCNT Operation
Rev. 2.00, 03/04, page 137 of 534
φ RTCNT
N
H'00
RTCOR
N
Refresh request signal and CMF bit setting signal
Figure 6.37 Compare Match Timing
TRp
φ
TRr
TRc1
TRc2
(
)
,
Figure 6.38 CBR Refresh Timing A setting can be made in bits RCW1 and RCW0 in REFCR to delay RAS signal output by one to three cycles. Use bits RLW1 and RLW0 in REFCR to adjust the width of the RAS signal. The settings of bits RCW1, RCW0, RLW1, and RLW0 are valid only in refresh operations. Figure 6.39 shows the timing when bits RCW1 and RCW0 are set.
TRp
φ
TRrw TRr TRc1
TRc2
(
)
,
Figure 6.39 CBR Refresh Timing (RCW1 = 0, RCW0 = 1, RLW1 = 0, RLW0 = 0)
Rev. 2.00, 03/04, page 138 of 534
Self-Refreshing: A self-refresh mode (battery backup mode) is provided for DRAM as a kind of standby mode. In this mode, refresh timing and refresh addresses are generated within the DRAM. To select self-refreshing, set the RFSHE bit and SLFRF bit to 1 in REFCR. When a SLEEP instruction is executed to enter software standby mode, the CAS and RAS signals are output and DRAM enters self-refresh mode, as shown in figure 6.40. If a CBR refresh request occurs when making a transition to software standby mode, CBR refreshing is executed, then self-refresh mode is entered.
Software standby
TRp
φ
TRr
TRc3
(
)
,
(
)
High
Figure 6.40 Self-Refresh Timing In some DRAMs provided with a self-refresh mode, the RAS signal precharge time immediately after self-refreshing is longer than the normal precharge time. A setting can be made in bits TPCS2 to TPCS0 in REFCR to make the precharge time immediately after self-refreshing from 1 to 7 states longer than the normal precharge time. In this case, too, normal precharging is performed according to the setting of bits TPC1 and TPC0 in DRACCR, and therefore a setting should be made to give the optimum post-self-refresh precharge time, including this time. Figure 6.41 shows an example of the timing when the precharge time immediately after self-refreshing is extended by 2 states.
Rev. 2.00, 03/04, page 139 of 534
Software standby
DRAM space write
Trc3
φ
Trp1
Trp2
Tp
Tr
Tc1
Tc2
Address bus
(
)
,
(
)
(
)
Data bus
Figure 6.41 Example of Timing when Precharge Time after Self-Refreshing is Extended by 2 States 6.6.13 DMAC Single Address Transfer Mode and DRAM Interface
When burst mode is selected on the DRAM interface, the DACK output timing can be selected with the DDS bit in DRAMCR. When DRAM space is accessed in DMAC single address mode at the same time, this bit selects whether or not burst access is to be performed. When DDS = 1: Burst access is performed by determining the address only, irrespective of the bus master. With the DRAM interface, the DACK output goes low from the Tc1 state. Figure 6.42 shows the DACK output timing for the DRAM interface when DDS = 1.
Rev. 2.00, 03/04, page 140 of 534
Tp
φ
Tr
Tc1
Tc2
Address bus
Row address
Column address
(
)
,
(
) )
High
Read
(
Data bus
(
) )
High
Write
(
Data bus
Figure 6.42 Example of DACK Output Timing when DDS = 1 (RAST = 0, CAST = 0) When DDS = 0: When DRAM space is accessed in DMAC single address transfer mode, full access (normal access) is always performed. With the DRAM interface, the DACK output goes low from the Tr state. In modes other than DMAC single address transfer mode, burst access can be used when accessing DRAM space. Figure 6.43 shows the DACK output timing for the DRAM interface when DDS = 0.
Rev. 2.00, 03/04, page 141 of 534
Tp φ Address bus
Tr
Tc1
Tc2
Tc3
Row address
Column address
(
)
,
( Read ( )
)
High
Data bus
( Write ( )
) High
Data bus
Figure 6.43 Example of DACK Output Timing when DDS = 0 (RAST = 0, CAST = 1)
6.7
6.7.1
Idle Cycle
Operation
When this LSI accesses external address space, it can insert an idle cycle (Ti) between bus cycles in the following three cases: (1) when read accesses in different areas occur consecutively or when an external access cycle occurs after a single address transfer, (2) when (1) occurs and a write cycle occurs immediately after a read cycle, and (3) when (1) and (2) occur and a read cycle occurs immediately after a write cycle. A condition for idle cycle insertion can be selected with the IDLE1 and IDLE0 bits in BCR. The number of idle cycles to be inserted can be set from one to four states by setting the IDLC1 and IDLC0 bits in BCR. By inserting an idle cycle it is possible, for example, to avoid data collisions between ROM, etc., with a long output floating time, and high-speed memory, I/O interfaces, and so on.
Rev. 2.00, 03/04, page 142 of 534
Consecutive Reads in Different Areas: If consecutive reads in different areas occur while the IDLE1 and IDLE0 bits in BCR are set to either B'01, B'10, or B'11, an idle cycle which is set by the IDLC1 and IDLC0 bits in BCR is inserted at the start of the second read cycle. Figure 6.44 shows an example of the operation in this case. In this example, bus cycle A is a read cycle for ROM with a long output floating time, and bus cycle B is a read cycle for SRAM, each being located in a different area. In (a), an idle cycle is not inserted, and a collision occurs in bus cycle B between the read data from ROM and that from SRAM. In (b), an idle cycle is inserted, and a data collision is prevented.
Bus cycle A
Bus cycle B T1 T2
Bus cycle A
Bus cycle B Ti T1
T2
T1
T2
φ Address bus
(area A) (area B)
Data bus
Long output floating time
(a) No idle cycle insertion (IDLE1 = 0, IDLE0 = 0)
y ;
T3
T1
T2
T3
φ Address bus
(area A) (area B)
Data bus
Data collision
Idle cycle
(b) Idle cycle insertion (IDLE1 = 0, IDLE0 = 0, IDLC1 = 0, IDLC0 = 0)
Figure 6.44 Example of Idle Cycle Operation (Consecutive Reads in Different Areas) Write after Read: If an external write occurs after an external read while the IDLE1 and IDLE0 bits in BCR are set to either B'10 or B'11, an idle cycle which is set by the IDLC1 and IDLC0 bits in BCR is inserted at the start of the write cycle. Figure 6.45 shows an example of the operation in this case. In this example, bus cycle A is a read cycle for ROM with a long output floating time, and bus cycle B is a CPU write cycle. In (a), an idle cycle is not inserted, and a collision occurs in bus cycle B between the read data from ROM and the CPU write data. In (b), an idle cycle is inserted, and a data collision is prevented.
Rev. 2.00, 03/04, page 143 of 534
Bus cycle A
Bus cycle B T1 T2
φ Address bus
(area A) (area B)
Bus cycle A
Bus cycle B
Ti
T1
T2
T3
T1
T2
T3
T1
T2
φ Address bus
(area A) (area B)
Data bus
Long output floating time
(a) No idle cycle insertion (IDLE1 = 0, IDLE0 = 0)
y ;
Data bus
Data collision
Idle cycle
(b) Idle cycle insertion (IDLE1 = 0, IDLE0 = 0, IDLC1 = 0, IDLC0 = 0)
Figure 6.45 Example of Idle Cycle Operation (Write after Read) Read after Write: If an external read occurs after an external write while the IDLE1 and IDLE0 bits in BCR are set to B'11, an idle cycle which is set by the IDLC1 and IDLC0 bits in BCR is inserted at the start of the read cycle. Figure 6.46 shows an example of the operation in this case. In this example, bus cycle A is a CPU write cycle and bus cycle B is a read cycle from the SRAM. In (a), an idle cycle is not inserted, and a collision occurs in bus cycle B between the CPU write data and read data from the SRAM. In (b), an idle cycle is inserted, and a data collision is prevented.
Rev. 2.00, 03/04, page 144 of 534
Bus cycle A
Bus cycle B T1 T2
φ Address bus
(area A) (area B)
Bus cycle A
Bus cycle B
Ti
T1
T2
T3
T1
T2
T3
T1
T2
φ Address bus
(area A) (area B)
Data bus
Long output floating time
(a) No idle cycle insertion (IDLE1 = 0, IDLE0 = 0)
Figure 6.46 Example of Idle Cycle Operation (Read after Write) Relationship between Chip Select (CS) Signal and Read (RD) Signal: Depending on the system's load conditions, the RD signal may lag behind the CS signal. An example is shown in figure 6.47. In this case, with the setting for no idle cycle insertion (a), there may be a period of overlap between the bus cycle A RD signal and the bus cycle B CS signal. Setting idle cycle insertion, as in (b), however, will prevent any overlap between the RD and CS signals.
Bus cycle A
Bus cycle B T1 T2
Bus cycle A
Bus cycle B Ti T1
T2
y ;
T3
(area B)
Data bus
Data collision
Idle cycle
(b) Idle cycle insertion (IDLE1 = 0, IDLE0 = 0, IDLC1 = 0, IDLC0 = 0)
T1
T2
T1
T2
T3
φ Address bus
(area A) (area B)
φ Address bus
(area A) (area B)
Overlap period between and may occur
Idle cycle
(a) No idle cycle insertion (IDLE1 = 0, IDLE0 = 0)
(b) Idle cycle insertion (IDLE1 = 0, IDLE0 = 0, IDLC1 = 0, IDLC0 = 0)
Figure 6.47 Relationship between Chip Select (CS) and Read (RD)
Rev. 2.00, 03/04, page 145 of 534
Idle Cycle in Case of DRAM Space Access after Normal Space Access: In a DRAM space access following a normal space access, the settings of bits IDLE1, IDLE0, IDLC1, and IDLC0 in BCR are valid. However, in the case of consecutive reads in different areas, for example, if the second read is a full access to DRAM space, idle cycles include Tp and Ti cycles. The timing when a four-state idle cycle is inserted in a full access to DRAM space is shown in figure 6.48.
External read
DRAM space read
T1
T2
T3
Tp
Tr
Ti
Ti
Tc1
Tc2
φ
Address bus
Data bus
Figure 6.48 Example of DRAM Full Access after External Read (CAST = 0) In burst access in RAS down mode, the settings of bits IDLE1, IDLE0, IDLC1, and IDLC0 are valid and an idle cycle is inserted. The timing in this case is illustrated in figure 6.49.
Rev. 2.00, 03/04, page 146 of 534
DRAM space read
External read
DRAM space read
Tp
Tr
Tc1
Tc2
T1
T2
T3
Ti
Tc1
Tc2
φ
Address bus
,
Data bus
Idle cycle
Figure 6.49 Example of Idle Cycle Operation in RAS Down Mode (Consecutive Reads in Different Areas) (IDLE1 = 0, IDLE0 = 1, IDLC1 = 0, IDLC0 = 1, RAST = 0, and CAST = 0) Table 6.7 shows whether there is an idle cycle insertion or not in the case of mixed accesses to normal space and DRAM space.
Rev. 2.00, 03/04, page 147 of 534
Table 6.7
Idle Cycles in Mixed Accesses to Normal Space and DRAM Space
Next Access IDLC1 IDLC0 IDLE1 IDLE0 Idle cycle 0 0 0 1 0 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 0 0 1 0 1 Disabled 1 state inserted 4 states inserted 3 states inserted 2 states inserted Disabled 1 state inserted Normal/DRAM space read (different area) 0
Previous Access Normal/DRAM space read
Single address transfer
External space access
0 0 1
0 1 0 1
1
0 1
1 0 1
2 states inserted
1
0
0 1
1 0 1
3 states inserted
1
0 1
1 0 1
4 states inserted
Rev. 2.00, 03/04, page 148 of 534
Previous Access Normal/DRAM space read
Next Access
IDLC1 IDLC0 IDLE1 IDLE0 Idle cycle 0 0 1 0 1 0 1 1 1 0 1 1 0 1 0 1 1 1 0 1 4 states inserted 3 states inserted 2 states inserted 1 state inserted Disabled
Normal/DRAM space write 0
Normal/DRAM space write
Normal/DRAM space read
0
0 1
Disabled
1 0 0 1 1 0 1 1 1 1 1
0 1 1 1 1 1 state inserted 2 states inserted 3 states inserted 4 states inserted
6.7.2
Pin States in Idle Cycle
Table 6.8 shows the pin states in an idle cycle. Table 6.8
Pins A19 to A0 D15 to D0 CSn (n = 3 to 0) UCAS, LCAS AS RD HWR, LWR RAS WE DACKn (n = 3 to 0) Note: *
Pin States in Idle Cycle
Pin State Contents of following bus cycle High impedance High* High High High High High* High High Remains low in DRAM space RAS down mode. Rev. 2.00, 03/04, page 149 of 534
6.8
Write Data Buffer Function
This LSI has a write data buffer function for the external data bus. Using the write data buffer function enables external writes and DMA single address mode transfers to be executed in parallel with internal accesses. The write data buffer function is made available by setting the WDBE bit to 1 in BCR. Figure 6.50 shows an example of the timing when the write data buffer function is used. When this function is used, if an external address space write or DMA single address mode transfer continues for two states or longer, and there is an internal access next, an external write only is executed in the first state, but from the next state onward an internal access (on-chip memory or internal I/O register read/write) is executed in parallel with the external address space write rather than waiting until it ends.
On-chip memory read Internal I/O register read
External write cycle T1 T2 TW TW T3
φ
Internal address bus
Internal memory 1
Internal memory 2
Internal I/O register address
Internal read signal
A19 to A0
External address
External space write ,
D15 to D0
Note: n = 3 to 0
Figure 6.50 Example of Timing when Write Data Buffer Function is Used
Rev. 2.00, 03/04, page 150 of 534
6.9
Bus Arbitration
This LSI has a bus arbiter that arbitrates bus master operations (bus arbitration). There are two bus mastersthe CPU and DMACthat perform read/write operations when they have possession of the bus. Each bus master requests the bus by means of a bus request signal. The bus arbiter determines priorities at the prescribed timing, and permits use of the bus by means of a bus request acknowledge signal. The selected bus master then takes possession of the bus and begins its operation. 6.9.1 Operation
The bus arbiter detects the bus masters’ bus request signals, and if the bus is requested, sends a bus request acknowledge signal to the bus master. If there are bus requests from more than one bus master, the bus request acknowledge signal is sent to the one with the highest priority. When a bus master receives the bus request acknowledge signal, it takes possession of the bus until that signal is canceled. The order of priority of the bus master is as follows: (High) DMAC > CPU (Low) 6.9.2 Bus Transfer Timing
Even if a bus request is received from a bus master with a higher priority than that of the bus master that has acquired the bus and is currently operating, the bus is not necessarily transferred immediately. There are specific timings at which each bus master can relinquish the bus. CPU: The CPU is the lowest-priority bus master, and if a bus request is received from the DMAC, the bus arbiter transfers the bus to the bus master that issued the request. The timing for transfer of the bus is as follows: • The bus is transferred at a break between bus cycles. However, if a bus cycle is executed in discrete operations, as in the case of a longword-size access, the bus is not transferred between the component operations. • With bit manipulation instructions such as BSET and BCLR, the sequence of operations is: data read (read), relevant bit manipulation operation (modify), write-back (write). The bus is not transferred during this read-modify-write cycle, which is executed as a series of bus cycles. • If the CPU is in sleep mode, the bus is transferred immediately.
Rev. 2.00, 03/04, page 151 of 534
DMAC: The DMAC sends the bus arbiter a request for the bus when an activation request is generated. In normal transfer mode or in cycle steal transfer mode, the DMAC releases the bus after a single transfer. In block transfer mode, it releases the bus after transfer of one block, and in burst mode, after completion of the transfer.
6.10
Bus Controller Operation in Reset
In a reset, this LSI, including the bus controller, enters the reset state immediately, and any executing bus cycle is aborted.
Rev. 2.00, 03/04, page 152 of 534
Section 7 DMA Controller (DMAC)
This LSI has an on-chip DMA controller (DMAC) which can carry out data transfer on up to 4 channels.
7.1
• • • • •
Features
•
• •
•
Number of channels: Four channels Address space: Physical address space (16-Mbyte external space) Transfer data length: Byte, word, or longword can be selected. Maximum number of transfers: 16,777,215/infinite (free-running) Address mode: Dual address mode or single address mode can be selected. Dual address mode Addresses of transfer source and transfer destination are accessed. Values set in the internal DMAC register are addresses to be accessed for transfer source and transfer destination. Single data transfer requires two bus cycles. Single address mode The peripheral device of transfer source or transfer destination is accessed by the DACK signal and another one is accessed by the address. Single data transfer requires one bus cycle. Transfer request: The DMAC transfer activation requests are as follows. External request Four DREQ pins. Low-level detection or falling-edge detection can be selected. External requests can be accepted on all channels. Auto request A transfer request is automatically generated from the internal DMAC. On-chip USB A transfer request can be accepted from the on-chip USB on all channels. Bus mode: Cycle steal mode or burst mode can be selected. Transfer mode: Normal mode or block transfer mode can be selected. Normal mode Single data transfer is performed for single transfer request. The number of transfers is specified as 24 bits (max. 16 Mbytes) Block transfer mode (only for external request) Single block (specified number) data transfer is performed for single transfer request. Interrupt request: An interrupt request can be sent to the CPU at the end of the specified number of transfers.
Rev. 2.00, 03/04, page 153 of 534
EDMA261A_000120020400
• Repeat area set function This function enables data transfer of ring buffer, etc. efficiently because values in the upper bits of the transfer address register are fixed and address values in the specific range are repeated. Repeat area can be set from one bit (two bytes) to 23 bits (8 Mbytes). Repeat area can be set for both transfer source and transfer destination. Interrupt request generation can be set by overflow determination of repeat area. • Acceptance of a transfer request and the start of transfer processing can be notified to an external device via the DRAK pin.
Rev. 2.00, 03/04, page 154 of 534
Figure 7.1 shows a block diagram of the DMAC.
Bus controller
External pins
Data buffer Control logic
Address buffer Processor
On-chip USB module Internal signals with on-chip USB module Interrupt request signals to CPU for individual channels DMSAR_n DMDAR_n DMMDR_n DMACR_n DMTCR_n
Internal data bus Legend DMSAR_n: DMDAR_n: DMTCR_n: DMMDR_n: DMACR_n: : : : : n = 0 to 3
DMA source address register DMA destination address register DMA transfer count register DMA mode control register DMA address control register DMA transfer request acceptance acknowledge DMA transfer end DMA transfer acknowledge
Figure 7.1 Block Diagram of DMAC
7.2
Input/Output Pins
Table 7.1 shows the pin configuration of the DMAC. The corresponding port to the DACK pin automatically enters the output state by the setting of the single address transfer mode. When the DREQ pin is used, the corresponding port must not enter the output state. Whether the corresponding port to the TEND/DRAK pin is used as TEND/DRAK pin can be set by the register.
Rev. 2.00, 03/04, page 155 of 534
Module data bus
Table 7.1
Pin Configuration
Abbreviation DREQ0 I/O Input Output Output Output Function Channel 0 external request Channel 0 single address transfer acknowledge Channel 0 transfer end Notification to external device of channel 0 external request acceptance and start of transfer processing Channel 1 external request Channel 1 single address transfer acknowledge Channel 1 transfer end Notification to external device of channel 1 external request acceptance and start of transfer processing Channel 2 external request Channel 2 single address transfer acknowledge Channel 2 transfer end Notification to external device of channel 2 external request acceptance and start of transfer processing Channel 3 external request Channel 3 single address transfer acknowledge Channel 3 transfer end Notification to external device of channel 3 external request acceptance and start of transfer processing
Channel Name 0 DMA request 0
DMA transfer acknowledge 0 DACK0 DMA transfer end 0 DREQ0 acceptance acknowledge TEND0 DRAK0
1
DMA request 1
DREQ1
Input Output Output Output
DMA transfer acknowledge 1 DACK1 DMA transfer end 1 DREQ1 acceptance acknowledge TEND1 DRAK1
2
DMA request 2
DREQ2
Input Output Output Output
DMA transfer acknowledge 2 DACK2 DMA transfer end 2 DREQ2 acceptance acknowledge TEND2 DRAK2
3
DMA request 3
DREQ3
Input Output Output Output
DMA transfer acknowledge 3 DACK3 DMA transfer end 3 DREQ3 acceptance acknowledge TEND3 DRAK3
Rev. 2.00, 03/04, page 156 of 534
7.3
Register Descriptions
The DMAC has the following registers. • • • • • • • • • • • • • • • • • • • • • DMA source address register_0 (DMSAR_0) DMA destination address register_0 (DMDAR_0) DMA transfer count register_0 (DMTCR_0) DMA mode control register_0 (DMMDR_0) DMA address control register_0 (DMACR_0) DMA source address register_1 (DMSAR_1) DMA destination address register_1 (DMDAR_1) DMA transfer count register_1 (DMTCR_1) DMA mode control register_1 (DMMDR_1) DMA address control register_1 (DMACR_1) DMA source address register_2 (DMSAR_2) DMA destination address register_2 (DMDAR_2) DMA transfer count register_2 (DMTCR_2) DMA mode control register_2 (DMMDR_2) DMA address control register_2 (DMACR_2) DMA source address register_3 (DMSAR_3) DMA destination address register_3 (DMDAR_3) DMA transfer count register_3 (DMTCR_3) DMA mode control register_3 (DMMDR_3) DMA address control register_3 (DMACR_3) USB transfer control register (USTCR)
Rev. 2.00, 03/04, page 157 of 534
7.3.1
DMA Source Address Register (DMSAR)
DMSAR is a 32-bit readable/writable register that specifies the transfer source address. An address update function is provided that updates the register contents to the next transfer source address each time transfer processing is performed. In single address mode, the DMSAR value is ignored when a device with DACK is specified as the transfer source. The upper 8 bits of DMSAR are reserved; they are always read as 0 and cannot be modified. Only 0 should be written to these bits. The DMSAR value is undefined at a reset or in hardware standby mode. Do not write to DMSAR for a channel on which DMA transfer is in progress. DMSAR can be read at all times by the CPU. When reading DMSAR for a channel on which DMA transfer processing is in progress, a longword-size read must be executed. 7.3.2 DMA Destination Address Register (DMDAR)
DMDAR is a 32-bit readable/writable register that specifies the transfer destination address. An address update function is provided that updates the register contents to the next transfer destination address each time transfer processing is performed. In single address mode, the DMDAR value is ignored when a device with DACK is specified as the transfer destination. The upper 8 bits of DMDAR are reserved; they are always read as 0 and cannot be modified. Only 0 should be written to these bits. The DMDAR value is undefined at a reset or in hardware standby mode. Do not write to DMDAR for a channel on which DMA transfer is in progress. DMDAR can be read at all times by the CPU. When reading DMDAR for a channel on which DMA transfer processing is in progress, a longword-size read must be executed. 7.3.3 DMA Transfer Count Register (DMTCR)
DMTCR specifies the number of transfers. The function differs according to the transfer mode (normal/block). The DMTCR value is undefined at a reset or in hardware standby mode. Do not write to DMTCR for a channel on which DMA transfer is in progress.
Rev. 2.00, 03/04, page 158 of 534
Normal Transfer Mode:
Bit 31 to 24 Bit Name Initial Value All 0 R/W Description Reserved These bits are always read as 0. The write value should always be 0. 23 to 0 Undefined R/W 24-Bit Transfer Counter These bits specify the number of transfers (number of bytes, word, or longwords). Setting H'000001 specifies one transfer. Setting H'000000 means no specification for the number of transfers, and the transfer counter function is halted. In this case, there is no transfer end interrupt by the transfer counter. Setting H'FFFFFF specifies the maximum number of transfers, that is 16,777,215. During DMA transfer, this counter shows the remaining number of transfers. This counter can be read at all times. When reading DMTCR for a channel on which DMA transfer processing is in progress, a longword-size read must be executed.
Block Transfer Mode:
Bit 31 to24 Bit Name Initial Value All 0 R/W Description Reserved These bits are always read as 0. The write value should always be 0. 23 to 16 Undefined R/W Block Size These bits specify the block size (number of bytes, words, or longwords) for block transfer. Setting H'01 specifies one as the block, while setting H'00 specifies the maximum block size, that is 256. The register value always indicates the specified block size. 15 to 0 Undefined R/W 16-Bit Transfer Counter These bits specify the number of block transfers (number of bytes, word, or longwords). Setting H'0001 specifies one block transfer. Setting H'0000 means no specification for the number of transfers, and the transfer counter function is halted. In this case, there is no transfer end interrupt by the transfer counter. Setting H'FFFF specifies the maximum number of block transfers, that is 65,535. During DMA transfer, this counter shows the remaining number of block transfers. Rev. 2.00, 03/04, page 159 of 534
7.3.4
DMA Mode Control Register (DMMDR)
DMMDR specifies the operating mode and transfer type.
Bit 15 Bit Name DA Initial Value 0 R/W
1
Description
R/(W)* DMA Active Controls the DMA operation. When this bit is set to 1, this indicates that an DMA operation is in progress. When auto request mode is specified (by bits MDS1 and MDS0), transfer processing begins when this bit is set to 1. With external requests, transfer processing begins when a transfer request is issued after this bit has been set to 1. When this bit is cleared to 0 during an DMA operation, transfer is halted. If this bit is cleared to 0 during an DMA operation in block transfer mode, transfer processing is continued for the currently executing one-block transfer, and the bit is cleared on completion of the currently executing one-block transfer. If an external source that ends (aborts) transfer occurs, this bit is automatically cleared to 0 and transfer is terminated. Do not change the operating mode, transfer method, or other parameters while this bit is set to 1. 0: Data transfer disabled on corresponding channel [Clearing conditions] • • • When the specified number of transfers end When operation is halted by a repeat area overflow interrupt When 0 is written to DA while DA = 1 (In block transfer mode, write is effective after end of one-block transfer) Reset, NMI interrupt, hardware standby mode
•
1: Data transfer enabled on corresponding channel and during an DMA operation.
Rev. 2.00, 03/04, page 160 of 534
Bit 14
Bit Name BEF
Initial Value 0
R/W
2
Description
R/(W)* Block Transfer Error Flag Flag that indicates the occurrence of an error during block transfer. If an NMI interrupt is generated during block transfer, the DMAC immediately terminates the DMA operation and sets this bit to 1. The address registers indicate the next transfer addresses during block transfer, but the data for which transfer has been performed within the block size is lost. To clear this bit, 0 should be written after reading 1 from this bit. 0: No block transfer error [Clearing condition] Writing 0 to BEF after reading BEF = 1 1: Block transfer error and block transfer is abnormal. [Setting condition] NMI interrupt during block transfer
13
DRAKE
0
R/W
DRAK Pin Output Enable Enables output from the DREQ acknowledge/transfer processing start (DRAK) pin. 0: DRAK pin output disabled 1: DRAK pin output enabled
12
TENDE
0
R/W
TEND Pin Output Enable Enables output from the DMA transfer end (TEND) pin. 0: TEND pin output disabled 1: TEND pin output enabled
11
DREQS
0
R/W
DREQ Select Specifies low level sensing or falling edge sensing as the sampling method for the DREQ pin used in external request mode. 0: Low level sensing (Low level sensing is used for the first transfer after transfer is enabled.) 1: Falling edge sensing
10
AMS
0
R/W
Address Mode Select Selects single address mode or dual address mode. When single address mode is selected, the DACK pin is valid. 0: Dual address mode 1: Single address mode
Rev. 2.00, 03/04, page 161 of 534
Bit 9 8
Bit Name MDS1 MDS0
Initial Value 0 0
R/W R/W R/W
Description Mode Select 1 and 0 These bits specify the activation source, bus mode, and transfer mode.
Activation Source Bus Mode 00 Auto request 01 Auto request 10 External request, on-chip USB 11 External request, on-chip USB Cycle steal mode Burst mode Cycle steal mode Cycle steal mode Transfer Mode Normal transfer mode Normal transfer mode Normal transfer mode Block transfer mode
Note: The transfer from the on-chip USB can be the requested by setting USTCR. See section 7.3.6, USB Transfer Control Register (USTCR). 7 DIE 0 R/W DMA Interrupt Enable Enables or disables interrupt requests. When this bit is set to 1, an interrupt request is generated when the IRF bit in DMMDR is set to 1. The interrupt request is cleared by clearing this bit or the IRF bit in DMMDR to 0. 0: Interrupt request is not generated 1: Interrupt request is generated
Rev. 2.00, 03/04, page 162 of 534
Bit 6
Bit Name IRF
Initial Value 0
R/W
2
Description
R/(W)* Interrupt Request Flag Flag indicating that an interrupt request has occurred and transfer has ended. To clear this bit, the DA bit in DMMDR is set to 1 or 0 is written after reading 1 from this bit. 0: No interrupt request [Clearing conditions] • • Writing 1 to the DA bit in DMMDR Writing 0 to IRF after reading IRF = 1
1: Interrupt request occurrence [Setting conditions] • • • 5 TCEIE 0 R/W Transfer end interrupt request generated by transfer counter Source address repeat area overflow interrupt request Destination address repeat area overflow interrupt request
Transfer Counter End Interrupt Enable Enables or disables transfer end interrupt requests by the transfer counter. When transfer ends according to the transfer counter while this bit is set to 1, the IRF bit in DMMDR is set to 1, indicating that an interrupt request has occurred. 0: Transfer end interrupt requests by transfer counter are disabled 1: Transfer end interrupt requests by transfer counter are enabled
4
SDIR
0
R/W
Single Address Direction Specifies the data transfer direction in single address mode. In dual address mode (AMS = 0), the specification by this bit is ignored. 0: Transfer direction: DMSAR → external device with DACK 1: Transfer direction: External device with DACK → DMDAR
Rev. 2.00, 03/04, page 163 of 534
Bit 3
Bit Name DTSIZE
Initial Value 0
R/W R/W
Description Data Transmit Size Specifies the size of data to be transferred by combination of the LWSIZE bit. LWSIZE DTSIZE 0 0 0 1 0: Byte-size (8-bit) specification 1: Word-size (16-bit) specification 0: Longword-size (32-bit) specification 1: Reserved (setting prohibited)
2
0
R/W
Reserved This bit can be read from or written to. However, the write value should always be 0.
1
LWSIZE
0
R/W
Longword Data Transmit Size Specifies the size of data to be transferred by combination of the DTSIZE bit.
0
0
R/W
Reserved This bit can be read from or written to. However, the write value should always be 0.
Notes: 1. There is a period when the written value is not reflected immediately. 2. Only 0 can be written after reading 1, to clear the flag.
Rev. 2.00, 03/04, page 164 of 534
7.3.5
DMA Address Control Register (DMACR)
DMACR specifies address register incrementing/decrementing and use of the repeat area function.
Bit 15 14 Bit Name SAT1 SAT0 Initial Value 0 0 R/W R/W R/W Description Source Address Update Mode These bits specify incrementing/decrementing of the transfer source address (DMSAR). When an external device with DACK is designated as the transfer source in single address mode, the specification by these bits is ignored. 0X: Source address (DMSAR) is fixed 10: Source address is incremented (+1 in byte transfer, +2 in word transfer, or +4 in longword transfer) 11: Source address is decremented (–1 in byte transfer, –2 in word transfer, or –4 in longword transfer) 13 SARIE 0 R/W Source Address Repeat Interrupt Enable When this bit is set to 1, in the event of source address repeat area overflow, the IRF bit in DMMDR is set to 1 and the DA bit in DMMDR cleared to 0, and transfer is terminated. If the DIE bit in DMMDR is 1 when the IRF bit in DMMDR is set to 1, an interrupt request is sent to the CPU. When used together with block transfer mode, a source address repeat interrupt is requested at the end of a block-size transfer. If the DA bit is set to 1 in DMMDR for the channel on which transfer is terminated by a source address repeat interrupt, transfer can be resumed from the state in which it ended. If a source address repeat area has not been designated, this bit is ignored. 0: Source address repeat interrupt is not requested 1: When source address repeat area overflow occurs, the IRF bit in DMMDR is set to 1 and an interrupt is requested
Rev. 2.00, 03/04, page 165 of 534
Bit 12 11 10 9 8
Bit Name SARA4 SARA3 SARA2 SARA1 SARA0
Initial Value 0 0 0 0 0
R/W R/W R/W R/W R/W R/W
Description Source Address Repeat Area These bits specify the source address (DMSAR) repeat area. The repeat area function updates the specified lower address bits, leaving the remaining upper address bits always the same. A repeat area size of 2 bytes to 8 Mbytes can be specified. The setting interval is a power-of-two number of bytes. When repeat area overflow results from incrementing or decrementing an address, the lower address is the start address of the repeat area in the case of address incrementing, or the last address of the repeat area in the case of address decrementing. If the SARIE bit is set to 1, an interrupt can be requested when repeat area overflow occurs. 00000: Not designated source address (DMSAR) as repeat area 00001: Lower 1 bit (2-byte area) in DMSAR designated as repeat area 00010: Lower 2 bits (4-byte area) in DMSAR designated as repeat area 00011: Lower 3 bits (8-byte area) in DMSAR designated as repeat area 00100: Lower 4 bits (16-byte area) in DMSAR designated as repeat area : : 10011: Lower 19 bits (512-kbyte area) in DMSAR designated as repeat area 10100: Lower 20 bits (1-Mbyte area) in DMSAR designated as repeat area 10101: Lower 21 bits (2-Mbyte area) in DMSAR designated as repeat area 10110: Lower 22 bits (4-Mbyte area) in DMSAR designated as repeat area 10111: Lower 23 bits (8-Mbyte area) in DMSAR designated as repeat area
Rev. 2.00, 03/04, page 166 of 534
Bit 7 6
Bit Name DAT1 DAT0
Initial Value 0 0
R/W R/W R/W
Description Destination Address Update Mode These bits specify incrementing/decrementing of the transfer destination address (DMDAR). When an external device with DACK is designated as the transfer destination in single address mode, the specification by these bits is ignored. 0X: Destination address (DMDAR) is fixed 10: Destination address is incremented (+1 in byte transfer, +2 in word transfer, or +4 in longword transfer) 11: Destination address is decremented (–1 in byte transfer, –2 in word transfer, or –4 in longword transfer)
5
DARIE
0
R/W
Destination Address Repeat Interrupt Enable When this bit is set to 1, in the event of destination address repeat area overflow the IRF bit is set to 1 and the DA bit cleared to 0 in DMMDR, and transfer is terminated. If the DIE bit in DMMDR is 1 when the IRF bit in DMMDR is set to 1, an interrupt request is sent to the CPU. When used together with block transfer mode, a destination address repeat interrupt is requested at the end of a block-size transfer. If the DA bit is set to 1 in DMMDR for the channel on which transfer is terminated by a destination address repeat interrupt, transfer can be resumed from the state in which it ended. If a destination address repeat area has not been designated, this bit is ignored. 0: Destination address repeat interrupt is not requested 1: When destination address repeat area overflow occurs, the IRF bit in DMMDR is set to 1 and an interrupt is requested
Rev. 2.00, 03/04, page 167 of 534
Bit 4 3 2 1 0
Bit Name DARA4 DARA3 DARA2 DARA1 DARA0
Initial Value 0 0 0 0 0
R/W R/W R/W R/W R/W R/W
Description Destination Address Repeat Area These bits specify the destination address (DMDAR) repeat area. The repeat area function updates the specified lower address bits, leaving the remaining upper address bits always the same. A repeat area size of 2 bytes to 8 Mbytes can be specified. The setting interval is a power-of-two number of bytes. When repeat area overflow results from incrementing or decrementing an address, the lower address is the start address of the repeat area in the case of address incrementing, or the last address of the repeat area in the case of address decrementing. If the DARIE bit is set to 1, an interrupt can be requested when repeat area overflow occurs. 00000: Not designated destination address (DMDAR) as repeat area 00001: Lower 1 bit (2-byte area) in DMDAR designated as repeat area 00010: Lower 2 bits (4-byte area) in DMDAR designated as repeat area 00011: Lower 3 bits (8-byte area) designated as repeat area 00100: Lower 4 bits (16-byte area) in DMDAR designated as repeat area : : 10011: Lower 19 bits (512-kbyte area) in DMDAR designated as repeat area 10100: Lower 20 bits (1-Mbyte area) in DMDAR designated as repeat area 10101: Lower 21 bits (2-Mbyte area) in DMDAR designated as repeat area 10110: Lower 22 bits (4-Mbyte area) in DMDAR designated as repeat area 10111: Lower 23 bits (8-Mbyte area) in DMDAR designated as repeat area
Rev. 2.00, 03/04, page 168 of 534
7.3.6
USB Transfer Control Register (USTCR)
USTCR specifies the transfer source from the on-chip USB, etc.
Bit 15 Bit Name EP1DMAE Initial Value 0 R/W R/W Description Endpoint 1 (EP1) DMA Enable Enables a transfer source from the on-chip USB (transfer direction: reading from the on-chip USB (EP1)). When this bit is set to 1, a transfer request from the USB is selected as a transfer source. In block transfer mode, the on-chip USB request must not be set as an activation source. While the DA bit in DMMDR is set to 1, the EP1DMAE value must not be changed. 0: Transfer request from on-chip USB (EP1) not accepted. 1: Transfer request from on-chip USB (EP1) accepted. The DREQ pin on the corresponding channel is not available. 14 13 URCHS1 URCHS0 0 0 R/W R/W USB Read Channel Select When the DMA transfer is performed by a transfer request from the USB (EP1), these bits select the DMAC channel to be used. When the channel which accepts a request is selected and the EP1DMAE bit is set to 1, the corresponding channel accepts a USB request rather than an external request. In this case, the transfer direction is reading from the USB (EP1). Therefore, the source address must be specified as the FIFO in the USB (EP1). While the DA bit in DMMDR is set to 1, these bits must not be changed. A transfer request from the endpoint 1 (EP1) (reading from the on-chip USB) or a transfer request from the endpoint 2 (EP2) (writing to the onchip USB) must not be set to the same channel. 00: Channel 0 can accept the EP1 transfer request. 01: Channel 1 can accept the EP1 transfer request. 10: Channel 2 can accept the EP1 transfer request. 11: Channel 3 can accept the EP1 transfer request.
Rev. 2.00, 03/04, page 169 of 534
Bit 12
Bit Name
Initial Value 0
R/W R/W
Description Reserved This bit can be read from or written to. However, the write value should always be 0.
11
EP2DMAE
0
R/W
Endpoint 2 (EP2) DMA Enable Enables a transfer source from the on-chip USB (transfer direction: writing to the on-chip USB). When this bit is set to 1, a transfer request from the USB is selected as a transfer source. In block transfer mode, the on-chip USB request must not be set as an activation source. While the DA bit in DMMDR is set to 1, the EP2DMAE value must not be changed. 0: Transfer request from on-chip USB (EP2) not accepted. 1: Transfer request from on-chip USB (EP2) accepted. The DREQ pin on the corresponding channel is not available.
10 9
UWCHS1 UWCHS0
0 0
R/W R/W
USB Write Channel Select When the DMA transfer is performed by a transfer request from the USB (EP2), these bits select the DMAC channel to be used. When the channel which accepts a request is selected and the EP2DMAE bit is set to 1, the corresponding channel accepts a USB request rather than an external request. In this case, the transfer direction is writing to the on-chip USB (EP2). Therefore, the destination address must be specified as the FIFO in the on-chip USB (EP2). While the DA bit in DMMDR is set to 1, these bits must not be changed. A transfer request from the endpoint 1 (EP1) (reading from the on-chip USB) or a transfer request from the endpoint 2 (EP2) (writing to the onchip USB) must not be set to the same channel. 00: Channel 0 can accept the EP2 transfer request. 01: Channel 1 can accept the EP2 transfer request. 10: Channel 2 can accept the EP2 transfer request. 11: Channel 3 can accept the EP2 transfer request.
8 to 0
All 0
R/W
Reserved These bits can be read from or written to. However, the write value should always be 0.
Rev. 2.00, 03/04, page 170 of 534
7.4
Operation
All DMAC functions on four channels are common. Each mode can be set independently for each channel. The DMAC functions can be used by combining each function. 7.4.1 Transfer Modes
The transfer modes of the DMAC are summarized in table 7.2. Table 7.2 DMAC Transfer Modes
Transfer Origin Auto request External request On-chip USB Block transfer mode Burst transfer of External specified block size for a request single transfer request Block size: 1 to 256 bytes, words, or longwords Single • address mode • • Direct data transfer to/from external device using DACK pin instead of source or destination address register Above transfer mode can be specified in addition to address register setting One transfer possible in one bus cycle DMSAR/ DACK/ DACK DMDAR 1 to 65,535 or no specification Number of Transfers Address Registers Source Destination DMDAR
Address Transfer Mode Mode Bus Mode Dual Normal address transfer mode mode Burst/cycle steal mode
1 to 16,777,215 DMSAR or no specification
Cycle steal mode
In single address mode, a transfer request from the on-chip USB is not available. (Transfer mode variations are the same as in dual address mode except for a transfer request from the on-chip USB.)
Rev. 2.00, 03/04, page 171 of 534
The transfer mode can be set independently for each channel. In normal transfer mode, a one-byte, one-word, or one-longword transfer is executed in response to one transfer request. With auto requests, burst or cycle steal transfer mode can be set. In normal or burst transfer mode, continuous, high-speed transfer can be performed until the specified number of transfers have been executed or the transfer enable bit is cleared to 0. In block transfer mode, a transfer of the specified block size is executed in response to one transfer request. The block size can be from 1 to 256 bytes, words, or longwords. Within a block, transfer can be performed at the same high speed as in burst transfer mode. When the “no specification” setting (DMTCR = H'000000) is made for the number of transfers, the transfer counter is halted and there is no limit on the number of transfers, allowing transfer to be performed endlessly. Incrementing or decrementing the memory address by 1, 2, or 4, or leaving the address unchanged, can be specified independently for each address register. In all transfer modes, it is possible to set a repeat area comprising a power-of-two number of bytes. 7.4.2 Address Modes (Dual Address Mode/Single Address Mode)
Dual Address Mode: In dual address mode, both the transfer source and transfer destination are specified by registers in the DMAC, and one transfer is executed in two bus cycles. The transfer source address is set in the source address register (DMSAR), and the transfer destination address is set in the destination address register (DMDAR). In a transfer operation, the value in external memory specified by the transfer source address is read in the first bus cycle, and is written to the external memory specified by the transfer destination address in the next bus cycle. These consecutive read and write cycles are indivisible: another bus cycle (external access by an internal bus master or refresh cycle) does not occur between these two cycles. TEND pin output can be enabled or disabled by means of the TENDE bit in DMMDR. TEND is output for two consecutive bus cycles. The DACK signal is not output. Figure 7.2 shows an example of the timing in dual address mode.
Rev. 2.00, 03/04, page 172 of 534
DMA read cycle φ Address bus DMSAR
DMA write cycle
DMDAR
Figure 7.2 Example of Timing in Dual Address Mode Single Address Mode: In single address mode, the DACK signal is used instead of the source or destination address register to transfer data directly between an external device and external memory. In this mode, the DMAC accesses the transfer source or transfer destination external device by outputting the external I/O strobe signal (DACK), and at the same time accesses the other external device in the transfer by outputting an address. In this way, DMA transfer can be executed in one bus cycle. In the example of transfer between external memory and an external device with DACK shown in figure 7.3, data is output to the data bus by the external device and written to external memory in the same bus cycle. The transfer direction, that is whether the external device with DACK is the transfer source or transfer destination, can be specified with the SDIR bit in DMMDR. Transfer is performed from the external memory (DMSAR) to the external device with DACK when SDIR = 0, and from the external device with DACK to the external memory (DMDAR) when SDIR = 1. The setting in the source or destination address register not used in the transfer is ignored. The DACK pin becomes valid automatically when single address mode is selected. The DACK pin is active-low. TEND pin output can be enabled or disabled by means of the TENDE bit in DMMDR. TEND is output for one bus cycle. Figure 7.3 shows the data flow in single address mode, and figure 7.4 shows an example of the timing.
Rev. 2.00, 03/04, page 173 of 534
External address bus
External data bus
Microcomputer
External memory
DMAC
External device with DACK
Data flow
Figure 7.3 Data Flow in Single Address Mode
Rev. 2.00, 03/04, page 174 of 534
Transfer from external memory to external device with DACK
DMA cycle
φ Address bus
DMSAR
Address to external memory space
signal to external memory space
Data bus
Data output from external memory
Transfer from external device with DACK to external memory
DMA cycle
φ Address bus
DMDAR
Address to external memory space
signal to external memory space
Data bus
Data output from external device with DACK
Figure 7.4 Example of Timing in Single Address Mode
Rev. 2.00, 03/04, page 175 of 534
7.4.3
DMA Transfer Requests (Auto Request Mode/External Request Mode/USB Transfer Request)
Auto Request Mode: In auto request mode, transfer request signals are automatically generated within the DMAC in cases where a transfer request signal is not issued from outside, such as in transfer between two memories, or between a peripheral module that is not capable of generating transfer requests and memory. In auto request mode, transfer is started when the DA bit is set to 1 in DMMDR. In auto request mode, either cycle steal mode or burst mode can be selected as the bus mode. Block transfer mode cannot be used. External Request Mode: In external request mode, transfer is started by a transfer request signal (DREQ) from a device external to this LSI. DMA transfer is started when DREQ is input while DMA transfer is enabled (DA = 1). The transfer request source need not be the data transfer source or data transfer destination. The transfer request signal is accepted via the DREQ pin. Either falling edge sensing or low level sensing can be selected for the DREQ pin by means of the DREQS bit in DMMDR (low level sensing when DREQS = 0, falling edge sensing when DREQS = 1). Setting the DRAKE bit to 1 in DMMDR enables a signal confirming transfer request acceptance to be output from the DRAK pin. The DRAK signal is output when acceptance and transfer processing has been started in response to a single external request. The DRAK signal enables the external device to determine the timing of DREQ signal negation, and makes it possible to provide handshaking between the transfer request source and the DMAC. In external request mode, block transfer mode can be used instead of burst mode. Block transfer mode allows continuous execution (burst operation) of the specified number of transfers (the block size) in response to a single transfer request. In block transfer mode, the DRAK signal is output only once for a one-block transfer, since the transfer request via the DREQ pin is for a block unit. USB Request Mode: In USB request mode, DMA transfer can be executed by a transfer request from the on-chip USB. When a transfer request from the USB can be accepted and DMA transfer is enabled (DA = 1), DMA transfer is started after a transfer request from the USB is input. When a transfer request for the endpoint 1 is accepted, the DMAC transfers the endpoint 1 data. When a transfer request for the endpoint 2 is accepted, the DMAC transfers data to the endpoint 2. When a transfer request from the USB is used as a transfer source, single address mode, block transfer mode, and normal/burst transfer mode cannot be used.
Rev. 2.00, 03/04, page 176 of 534
7.4.4
Bus Modes (Cycle Steal Mode/Burst Mode)
There are two bus modes: cycle steal mode and burst mode. When the activation source is an auto request, either cycle steal mode or burst mode can be selected. When the activation source is an external request, cycle steal mode is used. Cycle Steal Mode: In cycle steal mode, the DMAC releases the bus at the end of each transfer of a transfer unit (byte, word, or block). If there is a subsequent transfer request, the DMAC takes back the bus, performs another transfer-unit transfer, and then releases the bus again. This procedure is repeated until the transfer end condition is satisfied. If a transfer request occurs in another channel during DMA transfer, the bus is temporarily released, then transfer is performed on the channel for which the transfer request was issued. If there is no external space bus request from another bus master, a one-cycle bus release interval is inserted. For details on the operation when there are requests for a number of channels, see section 7.4.8, Channel Priority. Figure 7.5 shows an example of the timing in cycle steal mode.
Bus cycle
CPU
CPU
DMAC
CPU
CPU
DMAC
Bus returned temporarily to CPU
Transfer conditions: · Single address mode, normal transfer mode · low level sensing · CPU internal bus master is operating in external space
Figure 7.5 Example of Timing in Cycle Steal Mode Burst Mode: In burst mode, once the DMAC acquires the bus it continues transferring data, without releasing the bus, until the transfer end condition is satisfied. There is no burst mode in external request mode. In burst mode, once transfer is started it is not interrupted even if there is a transfer request from another channel with higher priority. When the burst mode channel finishes its transfer, it releases the bus in the next cycle in the same way as in cycle steal mode. When the DA bit is cleared to 0 in DMMDR, DMA transfer is halted. However, DMA transfer is executed for all transfer requests generated within the DMAC up until the DA bit was cleared to 0. If a repeat area overflow interrupt is generated, the DA bit is cleared to 0 and transfer is terminated.
Rev. 2.00, 03/04, page 177 of 534
Figure 7.6 shows an example of the timing in burst mode.
Bus cycle
CPU
CPU
DMAC
DMAC
DMAC
CPU
CPU
CPU cycle not generated Auto request mode
Figure 7.6 Examples of Timing in Burst Mode 7.4.5 Transfer Modes (Normal Transfer Mode/Block Transfer Mode)
There are two transfer modes: normal transfer mode and block transfer mode. When the activation source is an external request, either normal transfer mode or block transfer mode can be selected. When the activation source is an auto request, normal transfer mode is used. Normal Transfer Mode: In normal transfer mode, transfer of one transfer unit is processed in response to one transfer request. DMTCR functions as a 24-bit transfer counter. The TEND signal is output only for the last DMA transfer. The DRAK signal is output each time a transfer request is accepted and transfer processing is started. Figure 7.7 shows examples of DMA transfer timing in normal transfer mode.
DMA transfer cycle Bus cycle Last DMA transfer cycle
Read
Write
Read
Write
(1) Dual address mode, auto request mode
Bus cycle
DMA
DMA
(2) Single address mode, external request mode
Figure 7.7 Examples of Timing in Normal Transfer Mode
Rev. 2.00, 03/04, page 178 of 534
Block Transfer Mode: In block transfer mode, the number of bytes, words, or longwords specified by the block size is transferred in response to one transfer request. The upper 8 bits of DMTCR specify the block size, and the lower 16 bits function as a 16-bit transfer counter. A block size of 1 to 256 can be specified. During transfer of a block, transfer requests for other higher-priority channels are held pending. When transfer of one block is completed, the bus is released in the next cycle. Address register values are updated in the same way as in normal mode. There is no function for restoring the initial address register values after each block transfer. The TEND signal is output for each block transfer in the DMA transfer cycle in which the block ends. The DRAK signal is output once for one transfer request (for transfer of one block). Caution is required when setting the repeat area overflow interrupt of the repeat area function in block transfer mode. See section 7.4.6, Repeat Area Function, for details. Block transfer is aborted if an NMI interrupt is generated. See section 7.4.12, Ending DMA Transfer, for details. Figure 7.8 shows an example of DMA transfer timing in block transfer mode.
One-block transfer cycle
Bus cycle
CPU
CPU
CPU
DMAC
DMAC
DMAC
CPU
CPU cycle not generated
Transfer conditions: · Single address mode · Block size (DMTCR[23:16]) = 3
Figure 7.8 Example of Timing in Block Transfer Mode 7.4.6 Repeat Area Function
The DMAC has a function for designating a repeat area for source addresses and/or destination addresses. When a repeat area is designated, the address register values repeat within the range specified as the repeat area. Normally, when a ring buffer is involved in a transfer, an operation is required to restore the address register value to the buffer start address each time the address register value is the last address in the buffer (i.e. when ring buffer address overflow occurs), but if
Rev. 2.00, 03/04, page 179 of 534
the repeat area function is used, the operation that restores the address register value to the buffer start address is performed automatically within the DMAC. The repeat area function can be set independently for the source address register and the destination address register. The source address repeat area is specified by bits SARA4 to SARA0 in DMACR, and the destination address repeat area by bits DARA4 to DARA0 in DMACR. The size of each repeat area can be specified independently. When the address register value is the last address in the repeat area and repeat area overflow occurs, DMA transfer can be temporarily halted and an interrupt request sent to the CPU. If the SARIE bit in DMACR is set to 1, when the source address register overflows the repeat area, the IRF bit is set to 1 and the DA bit cleared to 0 in DMMDR, and transfer is terminated. If DIE = 1 in DMMDR, an interrupt is requested. If the DARIE bit in DMACR is set to 1, the above applies to the destination address register. If the DA bit in DMMDR is set to 1 during interrupt generation, transfer is resumed. Figure 7.9 illustrates the operation of the repeat area function.
When lower 3 bits (8-byte area) of DMSAR are designated as repeat area (SARA4 to SARA0 = 3)
External memory
:
Range of DMSAR values
H'23FFFE H'23FFFF H'240000 H'240001 H'240002 H'240003 H'240004 H'240005 H'240006 H'240007 H'240008 H'240009
:
H'240000 H'240001 H'240002 H'240003 H'240004 H'240005 H'240006 H'240007
Repeated
Repeat area overflow interrupt can be requested
Figure 7.9 Example of Repeat Area Function Operation
Rev. 2.00, 03/04, page 180 of 534
Caution is required when the repeat area overflow interrupt function is used together with block transfer mode. If transfer is always terminated when repeat area overflow occurs in block transfer mode, the block size must be a power of two, or alternatively, the address register value must be set so that the end of a block coincides with the end of the repeat area range. If repeat area overflow occurs while a block is being transferred in block transfer mode, the repeat interrupt request is held pending until the end of the block, and transfer overrun will occur. Figure 7.10 shows an example in which block transfer mode is used together with the repeat area function.
When lower 3 bits (8-byte area) of DMSAR are designated as repeat area (SARA4 to SARA0 = 3), and block size of 5 (DMTCR[23–16] = 5) is set in block transfer mode
External memory
:
Range of DMSAR values
First block transfer
Second block transfer
H'23FFFE H'23FFFF H'240000 H'240001 H'240002 H'240003 H'240004 H'240005 H'240006 H'240007 H'240008 H'240009
:
H'240000 H'240001 H'240002 H'240003 H'240004 H'240005 H'240006 H'240007
H'240000 H'240001 H'240002 H'240003 H'240004
H'240000 H'240001
Interrupt requested
H'240005 H'240006 H'240007
Block transfer in progress
Figure 7.10 Example of Repeat Area Function Operation in Block Transfer Mode
Rev. 2.00, 03/04, page 181 of 534
7.4.7
Registers during DMA Transfer Operation
DMAC register values are updated as DMA transfer processing is performed. The updated values depend on various settings and the transfer status. The following registers and bits are updated: DMSAR, DMDAR, DMTCR, and bits DA, BEF, and IRF in DMMDR. DMA Source Address Register (DMSAR): When the DMSAR address is accessed as the transfer source, after the DMSAR value is output, DMSAR is updated with the address to be accessed next. Bits SAT1 and SAT0 in DMACR specify incrementing or decrementing. The address is fixed when SAT1 = 0, incremented when SAT1 = 1 and SAT0 = 0, and decremented when SAT0 = 1. The size of the increment or decrement is determined by the size of the data transferred. When the LWSIZE and DTSIZE bits in DMMDR = 0, the data is byte-size and the address is incremented or decremented by 1; when LWSIZE = 0 and DTSIZE = 1, the data is word-size and the address is incremented or decremented by 2; when LWSIZE = 1 and DTSIZE = 0, the data is longword-size and the address is incremented or decremented by 4. When a repeat area setting is made, the operation conforms to that setting. The upper part of the address set for the repeat area function is fixed, and is not affected by address updating. When DMSAR is read during a transfer operation, a longword access must be used. During a transfer operation, DMSAR may be updated without regard to accesses from the CPU, and the correct values may not be read if the upper and lower words are read separately. In a longword access, the DMAC buffers the DMSAR value to ensure that the correct value is output. Do not write to DMSAR for a channel on which a transfer operation is in progress. DMA Destination Address Register (DMDAR): When the DMDAR address is accessed as the transfer destination, after the DMDAR value is output, DMDAR is updated with the address to be accessed next. Bits DAT1 and DAT0 in DMACR specify incrementing or decrementing. The address is fixed when DAT1 = 0, incremented when DAT1 = 1 and DAT0 = 0, and decremented when DAT0 = 1. The size of the increment or decrement is determined by the size of the data transferred. When the LWSIZE and DTSIZE bits in DMMDR = 0, the data is byte-size and the address is incremented or decremented by 1; when LWSIZE = 0 and DTSIZE = 1, the data is word-size and the address is incremented or decremented by 2; when LWSIZE = 1 and DTSIZE = 0, the data is longword-size and the address is incremented or decremented by 4. When a repeat area setting is made, the operation conforms to that setting. The upper part of the address set for the repeat area function is fixed, and is not affected by address updating. When DMDAR is read during a transfer operation, a longword access must be used. During a transfer operation, DMDAR may be updated without regard to accesses from the CPU, and the
Rev. 2.00, 03/04, page 182 of 534
correct values may not be read if the upper and lower words are read separately. In a longword access, the DMAC buffers the DMDAR value to ensure that the correct value is output. Do not write to DMDAR for a channel on which a transfer operation is in progress. DMA Transfer Count Register (DMTCR): When a DMA transfer is performed, the value in DMTCR is decremented by 1. However, when the DMTCR value is 0, transfers are not counted and the DMTCR value does not change. DMTCR functions differently in block transfer mode. The upper 8 bits, DMTCR23 to DMTCR16, are used to specify the block size, and their value does not change. The lower 16 bits, DMTCR15 to DMTCR0, function as a transfer counter, the value of which is decremented by 1 when a DMA transfer is performed. However, when the DMTCR15 to DMTCR0 value is 0, transfers are not counted and the DMTCR15 to DMTCR0 value does not change. In normal transfer mode, all of the lower 24 bits of DMTCR may change, so when DMTCR is read by the CPU during DMA transfer, a longword access must be used. During a transfer operation, DMTCR may be updated without regard to accesses from the CPU, and the correct values may not be read if the upper and lower words are read separately. In a longword access, the DMAC buffers the DMTCR value to ensure that the correct value is output. In block transfer mode, the upper 8 bits are never updated, so there is no problem with using word access. Do not write to DMTCR for a channel on which a transfer operation is in progress. If there is contention between an address update associated with DMA transfer and a write by the CPU, the CPU write has priority. In the event of contention between an DMTCR update from 1 to 0 and a write (of a nonzero value) by the CPU, the CPU write value has priority as the DMTCR value, but transfer is terminated. Transfer does not end if the CPU writes 0 to DMTCR. Figure 7.11 shows DMTCR update operations in normal transfer mode and block transfer mode.
Rev. 2.00, 03/04, page 183 of 534
DMTCR in normal transfer mode
Before update
After update
23 DMTCR
23 DMTCR 1 to H'FFFFFF
0 0
0
Fixed
23 0
0
–1
23 0 to H'FFFFFE
0
DMTCR in block transfer mode
Before update 23 16 15 Block 0 size 23 16 15 Block 1 to H'FFFF size After update 23 16 15 Block 0 size
23 16 15 Block 0 to H'FFFE size
0
Fixed
0
DMTCR
0
–1
0
DMTCR
Figure 7.11 DMTCR Update Operations in Normal Transfer Mode and Block Transfer Mode DA Bit in DMMDR: The DA bit in DMMDR is written to by the CPU to control enabling and disabling of data transfer, but may be cleared automatically by the DMAC due to the DMA transfer status. There are also periods during transfer when a 0-write to the DA bit by the CPU is not immediately effective. Conditions for DA bit clearing by the DMAC include the following: • • • • • • When the DMTCR value changes from 1 to 0, and transfer ends When a repeat area overflow interrupt is requested, and transfer ends When an NMI interrupt is generated, and transfer halts A reset Hardware standby mode When 0 is written to the DA bit, and transfer halts
When transfer is halted by writing 0 to the DA bit, the DA bit remains at 1 during the DMA transfer period. In block transfer mode, since a block-size transfer is carried out without interruption, the DA bit remains at 1 from the time 0 is written to it until the end of the current block-size transfer. In burst mode, transfer is halted for up to three DMA transfers following the bus cycle in which 0 is written to the DA bit. The DA bit remains set to 1 from the time of the 0-write until the end of the last DMA cycle. Writes (except to the DA bit) are prohibited to registers of a channel for
Rev. 2.00, 03/04, page 184 of 534
which the DA bit is set to 1. When changing register settings after a 0-write to the DA bit, it is necessary to confirm that the DA bit has been cleared to 0. Figure 7.12 shows the procedure for changing register settings in an operating channel.
Changing register settings in operating channel
1. Write 0 to the DA bit in DMMDR. 2. Read the DA bit. 1 3. Confirm that DA = 0. If DA = 1, this indicates that DMA transfer is in progress. 4. Write the required set values to the registers.
Write 0 to DA bit
Read DA bit
2
DA bit = 0?
Yes
3
No
Change register settings
Register setting changes completed
4
Figure 7.12 Procedure for Changing Register Settings in Operating Channel BEF Bit in DMMDR: In block transfer mode, the specified number of transfers (equivalent to the block size) is performed in response to a single transfer request. To ensure that the correct number of transfers is carried out, a block-size transfer is always executed, except in the event of a reset, transition to standby mode, or generation of an NMI interrupt. If an NMI interrupt is generated during block transfer, operation is halted midway through a block-size transfer and the DA bit is cleared to 0, terminating the transfer operation. In this case the BEF bit, which indicates the occurrence of an error during block transfer, is set to 1. IRF Bit in DMMDR: The IRF bit in DMMDR is set to 1 when an interrupt request source occurs. If the DIE bit in DMMDR is 1 at this time, an interrupt is requested. The timing for setting the IRF bit to 1 is when the DA bit in DMMDR is cleared to 0 and transfer ends following the end of the DMA transfer bus cycle in which the source generating the interrupt occurred. If the DA bit is set to 1 and transfer is resumed during interrupt handling, the IRF bit is automatically cleared to 0 and the interrupt request is cleared. For details on interrupts, see section 7.5, Interrupt Sources.
Rev. 2.00, 03/04, page 185 of 534
7.4.8
Channel Priority
The priority of the DMAC channels is: channel 0 > channel 1 > channel 2> channel 3. Table 7.3 shows the DMAC channel priority. Table 7.3
Channel Channel 0 Channel 1 Channel 2 Channel 3 Low
DMAC Channel Priority
Priority High
If transfer requests occur simultaneously for a number of channels, the highest-priority channel according to the priority in table 7.3 is selected for transfer. Transfer Requests from Multiple Channels (Except Auto Request Cycle Steal Mode): If transfer requests for different channels are issued during a transfer operation, the highest-priority channel (excluding the currently transferring channel) is selected. The selected channel begins transfer after the currently transferring channel releases the bus. If there is a bus request from a bus master other than the DMAC at this time, a cycle for the other bus master is initiated. If there is no other bus request, the bus is released for one cycle. Channels are not switched during burst transfer or transfer of a block in block transfer mode. Figure 7.13 shows an example of the transfer timing when transfer requests occur simultaneously for channels 0, 1, and 2. The example in the figure is for external request cycle steal mode.
Rev. 2.00, 03/04, page 186 of 534
Channel 0 transfer φ
Bus release
Channel 1 transfer
Channel 2 transfer
Address bus
Channel 0
Channel 1
Bus release
Channel 2
DMA control
Idle
Channel 0
Channel 1
Channel 2
Channel 0
Request cleared
Channel 1
Request Selected held
Request cleared
Channel 2
Not Request Request selected held held
Selected
Request cleared
Figure 7.13 Example of Channel Priority Timing Transfer Requests from Multiple Channels in Auto Request Cycle Steal Mode: If transfer requests for different channels are issued during a transfer in auto request cycle steal mode, the operation depends on the channel priority. If the channel that made the transfer request is of higher priority than the channel currently performing transfer, the channel that made the transfer request is selected. If the channel that made the transfer request is of lower priority than the channel currently performing transfer, that channel's transfer request is held pending, and the currently transferring channel remains selected. The selected channel begins transfer after the currently transferring channel releases the bus. If there is a bus request from a bus master other than the DMAC at this time, a cycle for the other bus master is initiated. If there is no other bus request, the bus is released for one cycle. Figure 7.14 shows examples of transfer timing in cases that include auto request cycle steal mode.
Rev. 2.00, 03/04, page 187 of 534
Conditions (1) Channel 0: Auto request, cycle steal mode Channel 1: External request, cycle steal mode, low level activation
Bus Channel 0
*
Channel 0
*
Channel 0
*
Channel 1
*
Channel 1
*
Channel 0 DA bit
Channel 1/ pin
Conditions (2) Channel 1: External request, cycle steal mode, low level activation Channel 2: Auto request, cycle steal mode
Bus Channel 2
*
Channel 2
*
Channel 1
*
Channel 2
*
Channel 1
*
Channel 1
Channel 1/ pin
Channel 2 DA bit
Conditions (3) Channel 0: Auto request, cycle steal mode Channel 2: Auto request, cycle steal mode
Bus Channel 2
*
Channel 2
*
Channel 0
*
Channel 0
*
Channel 2
*
Channel 0 DA bit
Channel 2 DA bit
*:
Bus release
Figure 7.14 Examples of Channel Priority Timing
Rev. 2.00, 03/04, page 188 of 534
7.4.9
DMAC Bus Cycles (Dual Address Mode)
Normal Transfer Mode (Cycle Steal Mode): Figure 7.15 shows an example of transfer when TEND output is enabled, and word-size, normal transfer mode (cycle steal mode) is performed from external 16-bit, 2-state access space to external 16-bit, 2-state access space.
DMA read DMA write
φ Address bus DMA read DMA write DMA read DMA write
Bus release
Bus release
Bus release
Last transfer cycle
Bus release
Figure 7.15 Example of Normal Transfer Mode (Cycle Steal Mode) Transfer After one byte, word, or longword has been transferred, the bus is released. While the bus is released, at least one CPU bus cycle is initiated. Normal Transfer Mode (Burst Mode): Figure 7.16 shows an example of transfer when TEND output is enabled, and word-size, normal transfer mode (burst mode) is performed from external 16-bit, 2-state access space to external 16-bit, 2-state access space.
Rev. 2.00, 03/04, page 189 of 534
DMA read DMA write DMA read DMA write DMA read DMA write
φ Address bus
Bus release
Last transfer cycle
Burst transfer
Bus release
Figure 7.16 Example of Normal Transfer Mode (Burst Mode) Transfer In burst mode, one-byte, one-word, or one-longword transfers are executed continuously until transfer ends. Once burst transfer starts, requests from other channels, even of higher priority, are held pending until transfer ends. If an NMI interrupt is generated while a channel designated for burst transfer is enabled for transfer, the DA bit is cleared and transfer is disabled. If a burst transfer has already been initiated within the DMAC, the bus is released on completion of the currently executing byte or word transfer, and burst transfer is aborted. If the last transfer cycle in burst transfer has been initiated within the DMAC, transfer is executed to the end even if the DA bit is cleared. Normal Transfer Mode (Cycle Steal Mode: Transfer Source is USB): Figure 7.17 shows an example of transfer when USB transfer is enabled, and word-size, normal transfer mode (cycle steal mode) is performed from the FIFO in the USB to external 16-bit, 2-state access space.
DMA read DMA write Bus release DMA read DMA write Bus release DMA read DMA write φ Address bus USB read (internal signal) USB
External memory
USB
External memory
USB
External memory
Figure 7.17 Example of Normal Transfer Mode (Cycle Steal Mode) Transfer (Transfer Source: USB)
Rev. 2.00, 03/04, page 190 of 534
After one byte, word, or longword has been transferred, the bus is released. While the bus is released, at least one CPU bus cycle is initiated. Normal Transfer Mode (Cycle Steal Mode: Transfer Destination is USB): Figure 7.18 shows an example of transfer when USB transfer is enabled, and word-size, normal transfer mode (cycle steal mode) is performed from external 16-bit, 2-state access space to the FIFO in the USB.
Bus DMA read DMA write release
φ Address bus
External memory
DMA read DMA write
Bus release
DMA read DMA write
USB
External memory
USB
External memory
USB
USB write (internal signal)
Figure 7.18 Example of Normal Transfer Mode (Cycle Steal Mode) Transfer (Transfer Destination: USB) After one byte, word, or longword has been transferred, the bus is released. While the bus is released, at least one CPU bus cycle is initiated. Block Transfer Mode (Cycle Steal Mode): Figure 7.19 shows an example of transfer when TEND output is enabled, and word-size, block transfer mode (cycle steal mode) is performed from external 16-bit, 2-state access space to external 16-bit, 2-state access space.
DMA read φ Address bus DMA write DMA read DMA Bus DMA write release read
DMA write DMA read DMA write
Figure 7.19 Example of Block Transfer Mode (Cycle Steal Mode) Transfer
Rev. 2.00, 03/04, page 191 of 534
One block is transferred in response to one transfer request, and after the transfer, the bus is released. While the bus is released, one or more CPU bus cycles are initiated. DREQ Pin Falling Edge Activation Timing: Figure 7.20 shows an example of normal mode transfer activated by the DREQ pin falling edge.
Bus release φ DMA read DMA write
Bus release
DMA read DMA write Bus release
Address bus
DMA control
Channel
Idle
Transfer source
Transfer destination
Transfer source
Transfer destination
Read
Write
Idle
Request
Read
Write
Idle
Request
Request clearance period
Request clearance period
Minimum 3 cycles
Minimum 3 cycles
[1]
[2]
[3]
[4]
Acceptance resumed
[5]
[6]
[7]
Acceptance resumed
[1] Acceptance after transfer enabling; pin low level is sampled at rise of φ, and request is held. [2], [5] Request is cleared at end of next bus cycle, and activation is started in DMAC. pin high level sampling is started at rise of φ. [3], [6] DMA cycle start; pin high level has been sampled, acceptance is resumed after completion of write cycle. [4], [7] When pin low level is sampled at rise of φ, and request is held.) (As in [1],
Figure 7.20 Example of Normal Mode Transfer Activated by DREQ Pin Falling Edge DREQ pin sampling is performed in each cycle starting at the next rise of φ after the end of the DMMDR write cycle for setting the transfer-enabled state. When a low level is sampled at the DREQ pin while acceptance via the DREQ pin is possible, the request is held within the DMAC. Then when activation is initiated within the DMAC, the request is cleared, and DREQ pin high level sampling for edge sensing is started. If DREQ pin high level sampling is completed by the end of the DMA write cycle, acceptance resumes after the end of the write cycle, and DREQ pin low level sampling is performed again; this sequence of operations is repeated until the end of the transfer. Figure 7.21 shows an example of block transfer mode transfer activated by the DREQ pin falling edge.
Rev. 2.00, 03/04, page 192 of 534
One block transfer
One block transfer
Bus release φ
DMA read
DMA write
Bus release
DMA read
DMA write
Bus release
Address bus DMA control Idle
Channel
Request
[1] [2]
Transfer source
Transfer destination
Transfer source
Transfer destination
Read
Write
Idle
Request
[4] [5]
Read Write
Idle
Request clearance period
Request clearance period
Minimum 3 cycles
[3]
Minimum 3 cycles [6] [7]
Acceptance resumed
Acceptance resumed
[1] [2], [5] [3], [6] [4], [7]
Acceptance after transfer enabling; pin low level is sampled at rise of φ, and request is held. Request is cleared at end of next bus cycle, and activation is started in DMAC. DMA cycle start; pin high level sampling is started at rise of φ. When pin high level has been sampled, acceptance is resumed after completion of dead cycle. (As in [1], pin low level is sampled at rise of φ, and request is held.)
Figure 7.21 Example of Block Transfer Mode Transfer Activated by DREQ Pin Falling Edge DREQ pin sampling is performed in each cycle starting at the next rise of φ after the end of the DMMDR write cycle for setting the transfer-enabled state. When a low level is sampled at the DREQ pin while acceptance via the DREQ pin is possible, the request is held within the DMAC. Then when activation is initiated within the DMAC, the request is cleared, and DREQ pin high level sampling for edge sensing is started. If DREQ pin high level sampling is completed by the end of the DMA write cycle, acceptance resumes after the end of the write cycle, and DREQ pin low level sampling is performed again; this sequence of operations is repeated until the end of the transfer. DREQ Pin Low Level Activation Timing: Figure 7.22 shows an example of normal mode transfer activated by the DREQ pin low level.
Rev. 2.00, 03/04, page 193 of 534
Bus release φ
DMA read
DMA write
Bus release
DMA read
DMA write Bus release
Address bus
DMA control Idle
Channel
Transfer source
Transfer destination
Transfer source
Transfer destination
Read
Write
Idle
Read
Write
Idle
Request clearance period Request Minimum 3 cycles [1] [2] [3]
Request clearance period Request Minimum 3 cycles [4] [5] [6] [7] Acceptance resumed
Acceptance resumed
[1] [2], [5] [3], [6] [4], [7]
Acceptance after transfer enabling; pin low level is sampled at rise of φ, and request is held. Request is cleared at end of next bus cycle, and activation is started in DMAC. DMA cycle is started. Acceptance is resumed after completion of write cycle. pin low level is sampled at rise of φ, and request is held.) (As in [1],
Figure 7.22 Example of Normal Mode Transfer Activated by DREQ Pin Low Level DREQ pin sampling is performed in each cycle starting at the next rise of φ after the end of the DMMDR write cycle for setting the transfer-enabled state. When a low level is sampled at the DREQ pin while acceptance via the DREQ pin is possible, the request is held within the DMAC. Then when activation is initiated within the DMAC, the request is cleared. At the end of the write cycle, acceptance resumes and DREQ pin low level sampling is performed again; this sequence of operations is repeated until the end of the transfer. Figure 7.23 shows an example of block transfer mode transfer activated by the DREQ pin low level.
Rev. 2.00, 03/04, page 194 of 534
One block transfer
One block transfer
Bus release φ
DMA read
DMA write
Bus release
DMA read
DMA write Bus release
Address bus DMA control
Channel
Transfer source
Transfer destination
Transfer source
Transfer destination
Idle
Request [1] [2]
Read
Write
Idle
Request [4] Acceptance resumed [5]
Read Write
Idle
Request clearance period
Request clearance period
Minimum 3 cycles [3]
Minimum 3 cycles [6] [7] Acceptance resumed
[1] [2], [5] [3], [6] [4], [7]
Acceptance after transfer enabling; pin low level is sampled at rise of φ, and request is held. Request is cleared at end of next bus cycle, and activation is started in DMAC. DMA cycle is started. Acceptance is resumed after completion of dead cycle. (As in [1], pin low level is sampled at rise of φ, and request is held.)
Figure 7.23 Example of Block Transfer Mode Transfer Activated by DREQ Pin Low Level DREQ pin sampling is performed in each cycle starting at the next rise of φ after the end of the DMMDR write cycle for setting the transfer-enabled state. When a low level is sampled at the DREQ pin while acceptance via the DREQ pin is possible, the request is held within the DMAC. Then when activation is initiated within the DMAC, the request is cleared. At the end of the write cycle, acceptance resumes and DREQ pin low level sampling is performed again; this sequence of operations is repeated until the end of the transfer.
Rev. 2.00, 03/04, page 195 of 534
7.4.10
DMAC Bus Cycles (Single Address Mode)
Single Address Mode (Read): Figure 7.24 shows an example of transfer when TEND output is enabled, and byte-size, single address mode transfer (read) is performed from external 8-bit, 2state access space to an external device.
DMA read DMA read DMA read
DMA read
φ Address bus
Bus release
Bus release
Bus release
Bus release
Last Bus release transfer cycle
Figure 7.24 Example of Single Address Mode (Byte Read) Transfer Figure 7.25 shows an example of transfer when TEND output is enabled, and word-size, single address mode transfer (read) is performed from external 8-bit, 2-state access space to an external device.
DMA read DMA read
DMA read
φ Address bus
Bus release
Bus release
Bus release
Last transfer cycle
Bus release
Figure 7.25 Example of Single Address Mode (Word Read) Transfer After one byte or word has been transferred in response to one transfer request, the bus is released. While the bus is released, one or more CPU bus cycles are initiated.
Rev. 2.00, 03/04, page 196 of 534
Figure 7.26 shows an example of transfer when TEND output is enabled, and longword-size, single address mode transfer (read) is performed from external 16-bit, 2-state access space to an external device.
DMA read DMA read
DMA read
φ Address bus
Bus release
Bus release
Bus release
Last transfer cycle
Bus release
Figure 7.26 Example of Single Address Mode (Longword Read) Transfer Single Address Mode (Write): Figure 7.27 shows an example of transfer when TEND output is enabled, and byte-size, single address mode transfer (write) is performed from an external device to external 8-bit, 2-state access space.
DMA write DMA write DMA write
DMA write
φ Address bus
Bus release
Bus release
Bus release
Bus release
Last Bus release transfer cycle
Figure 7.27 Example of Single Address Mode (Byte Write) Transfer Figure 7.28 shows an example of transfer when TEND output is enabled, and word-size, single address mode transfer (write) is performed from an external device to external 8-bit, 2-state access space.
Rev. 2.00, 03/04, page 197 of 534
DMA write
DMA write
DMA write
φ Address bus
Bus release
Bus release
Bus release
Last transfer cycle
Bus release
Figure 7.28 Example of Single Address Mode (Word Write) Transfer After one byte or word has been transferred in response to one transfer request, the bus is released. While the bus is released, one or more CPU bus cycles are initiated. Figure 7.29 shows an example of transfer when TEND output is enabled, and longword-size, single address mode transfer (write) is performed from an external device to external 16-bit, 2state access space.
DMA write DMA write
DMA write
φ Address bus
Bus release
Bus release
Bus Last transfer cycle Bus release release
Figure 7.29 Example of Single Address Mode (Longword Write) Transfer
Rev. 2.00, 03/04, page 198 of 534
DREQ Pin Falling Edge Activation Timing: Figure 7.30 shows an example of single address mode transfer activated by the DREQ pin falling edge.
Bus release φ DMA single Bus release DMA single Bus release
Address bus
Transfer source/ destination
Transfer source/ destination
DMA control Channel
Idle
Request
Single
Idle
Request
Single
Idle
Request clearance period
Request clearance period
Minimum 3 cycles [1] [2] [3]
Minimum 3 cycles [4] Acceptance resumed [5] [6] [7] Acceptance resumed
[1] [2], [5] [3], [6] [4], [7]
Acceptance after transfer enabling; pin low level is sampled at rise of φ, and request is held. Request is cleared at end of next bus cycle, and activation is started in DMAC. pin high level sampling is started at rise of φ. DMA cycle start; pin high level has been sampled, acceptance is resumed after completion of single cycle. When pin low level is sampled at rise of φ, and request is held.) (As in [1],
Figure 7.30 Example of Single Address Mode Transfer Activated by DREQ Pin Falling Edge DREQ pin sampling is performed in each cycle starting at the next rise of φ after the end of the DMMDR write cycle for setting the transfer-enabled state. When a low level is sampled at the DREQ pin while acceptance via the DREQ pin is possible, the request is held within the DMAC. Then when activation is initiated within the DMAC, the request is cleared, and DREQ pin high level sampling for edge sensing is started. If DREQ pin high level sampling is completed by the end of the DMA single cycle, acceptance resumes after the end of the single cycle, and DREQ pin low level sampling is performed again; this sequence of operations is repeated until the end of the transfer.
Rev. 2.00, 03/04, page 199 of 534
DREQ Pin Low Level Activation Timing: Figure 7.31 shows an example of single address mode transfer activated by the DREQ pin low level.
Bus release φ DMA single Bus release DMA single Bus release
Address bus
Transfer source/ destination
Transfer source/ destination
DMA control Channel
Idle
Request
Single
Idle
Request
Single
Idle
Request clearance period
Request clearance period
Minimum 3 cycles [1] [2] [3]
Minimum 3 cycles [4] Acceptance resumed [5] [6] [7] Acceptance resumed
[1] [2], [5] [3], [6] [4], [7]
Acceptance after transfer enabling; pin low level is sampled at rise of φ, and request is held. Request is cleared at end of next bus cycle, and activation is started in DMAC. DMA cycle is started. Acceptance is resumed after completion of single cycle. pin low level is sampled at rise of φ, and request is held.) (As in [1],
Figure 7.31 Example of Single Address Mode Transfer Activated by DREQ Pin Low Level DREQ pin sampling is performed in each cycle starting at the next rise of φ after the end of the DMMDR write cycle for setting the transfer-enabled state. When a low level is sampled at the DREQ pin while acceptance via the DREQ pin is possible, the request is held within the DMAC. Then when activation is initiated within the DMAC, the request is cleared. At the end of the single cycle, acceptance resumes and DREQ pin low level sampling is performed again; this sequence of operations is repeated until the end of the transfer.
Rev. 2.00, 03/04, page 200 of 534
7.4.11
Examples of Operation Timing in Each Mode
Examples of operation timings for various conditions in each mode are shown. The contention with other bus master is described by using the CPU external bus cycle as an example. Auto Request/Cycle Steal Mode/Normal Transfer Mode: When the DA bit is set to 1 in DMMDR, an DMA transfer cycle is started a minimum of three cycles later. There is a one-cycle bus release interval between the end of a one-transfer-unit DMA cycle and the start of the next transfer. If there is a transfer request for another channel of higher priority, the transfer request by the original channel is held pending, and transfer is performed on the higher-priority channel from the next transfer. Transfer on the original channel is resumed on completion of the higher-priority channel transfer. Figures 7.32 to 7.34 show operation timing examples for various conditions. • No contention/dual address mode (see figure 7.32) • CPU cycles/single address mode (see figure 7.33) • Contention with another channel/single address mode (see figure 7.34)
φ pin
3 cycles
1 cycle Last transfer cycle
Bus cycle
Bus release
DMA read
DMA write
Bus release
DMA read
DMA write
Bus release
DMA read
DMA write
CPU operation
DA = 1 write
Sleep
DA bit
0
1
0
Figure 7.32 Auto Request/Cycle Steal Mode/Normal Transfer Mode (No Contention/Dual Address Mode)
Rev. 2.00, 03/04, page 201 of 534
φ pin
1 bus cycle Last transfer cycle DMA single transfer cycle
Bus cycle
CPU cycle
DMA single transfer cycle
CPU cycle
CPU cycle
DMA single transfer cycle
CPU cycle
CPU operation
CPU access
CPU access
CPU access
CPU access
Figure 7.33 Auto Request/Cycle Steal Mode/Normal Transfer Mode (CPU Cycles/Single Address Mode)
φ pin
1 cycle
DMA single cycle
Bus release
1 cycle
DMA single cycle
Bus release
1 cycle
Bus cycle
DMA single cycle
Bus release
Higher-priority channel DMA cycle
Bus release
DMA single cycle
Bus release
Current channel
Other channel transfer request ) (
Figure 7.34 Auto Request/Cycle Steal Mode/Normal Transfer Mode (Contention with Another Channel/Single Address Mode) Auto Request/Burst Mode/Normal Transfer Mode: When the DA bit is set to 1 in DMMDR, an DMA transfer cycle is started a minimum of three cycles later. Once transfer is started, it continues (as a burst) until the transfer end condition is satisfied. Transfer requests for other channels are held pending until the end of transfer on the current channel.
Rev. 2.00, 03/04, page 202 of 534
Figures 7.35 to 7.37 show operation timing examples for various conditions. • CPU cycles/dual address mode (see figure 7.35) • CPU cycles/single address mode (see figure 7.36) • Contention with another channel/dual address mode (see figure 7.37)
φ pin
Last transfer cycle
Bus cycle
CPU cycle CPU cycle
DMA read
DMA write
DMA read
DMA write
Repeated
DMA read
DMA write
CPU cycle
CPU operation
CPU access
CPU access
CPU access
DA bit
1
0
Figure 7.35 Auto Request/Burst Mode/Normal Transfer Mode (CPU Cycles/Dual Address Mode)
φ pin
1 bus cycle
Last transfer cycle
Bus cycle
DMA DMA DMA DMA DMA CPU cycle CPU cycle single cycle single cycle CPU cycle single cycle single cycle CPU cycle single cycle CPU cycle
CPU operation
CPU access
CPU access
CPU access
CPU access
CPU access
Figure 7.36 Auto Request/Burst Mode/Normal Transfer Mode (CPU Cycles/Single Address Mode)
Rev. 2.00, 03/04, page 203 of 534
φ pin
Last transfer cycle
1 cycle
Bus release
Bus cycle
Bus release
DMA single transfer cycle
DMA single transfer cycle
DMA single transfer cycle
Bus release
Other channel DMA cycle
Original channel
Original channel
Other channel transfer request ) (
Figure 7.37 Auto Request/Burst Mode/Normal Transfer Mode (Contention with Another Channel/Single Address Mode) External Request/Cycle Steal Mode/Normal Transfer Mode: In external request mode, an DMA transfer cycle is started a minimum of three cycles after a transfer request is accepted. The next transfer request is accepted after the end of a one-transfer-unit DMA cycle. For external bus space CPU cycles, at least two bus cycles are generated before the next DMA cycle. If a transfer request is generated for another channel, an DMA cycle for the other channel is generated before the next DMA cycle. The DREQ pin sensing timing is different for low level sensing and falling edge sensing. The same applies to transfer request acceptance and transfer start timing. Figures 7.38 to 7.41 show operation timing examples for various conditions. • • • • No contention/dual address mode/low level sensing (see figure 7.38) CPU cycles/single address mode/low level sensing (see figure 7.39) No contention/single address mode/falling edge sensing (see figure 7.40) Contention with another channel/dual address mode/low level sensing (see figure 7.41)
Rev. 2.00, 03/04, page 204 of 534
φ pin
3 cycles
Last transfer cycle
Bus cycle
Bus release
DMA read
DMA write
Bus release
DMA read
DMA write
Bus release
DA bit
1
0
Figure 7.38 External Request/Cycle Steal Mode/Normal Transfer Mode (No Contention/Dual Address Mode/Low Level Sensing)
φ pin
2 bus cycles
Last transfer cycle
DMA single transfer cycle
CPU cycle
Bus cycle
CPU cycle CPU cycle CPU cycle
DMA single transfer cycle
CPU cycle CPU cycle
CPU operation
CPU access
CPU access
CPU access
CPU access
CPU access
CPU access
Figure 7.39 External Request/Cycle Steal Mode/Normal Transfer Mode (CPU Cycles/Single Address Mode/Low Level Sensing)
Rev. 2.00, 03/04, page 205 of 534
φ pin
acceptance internal processing state Bus cycle
Edge confirmation Start of transfer processing
Start of high level sensing
Edge confirmation Start of transfer processing
Start of high level sensing
Edge confirmation Start of transfer processing
Start of high level sensing
Bus release
DMA single transfer cycle
Bus release
DMA single transfer cycle
Bus release
DMA single transfer cycle
Figure 7.40 External Request/Cycle Steal Mode/Normal Transfer Mode (No Contention/Single Address Mode/Falling Edge Sensing)
φ pin
Original channel
Original channel
3 cycles
1 cycle
DMA read DMA write
Bus release
1 cycle
Other channel transfer cycle
Bus release
Bus cycle
DMA transfer cycle
Bus release
DMA read
DMA write
Other channel
Other channel
Figure 7.41 External Request/Cycle Steal Mode/Normal Transfer Mode (Contention with Another Channel/Dual Address Mode/Low Level Sensing)
Rev. 2.00, 03/04, page 206 of 534
External Request/Cycle Steal Mode/Block Transfer Mode: In block transfer mode, transfer of one block is performed continuously in the same way as in burst mode. The timing of the start of the next block transfer is the same as in normal transfer mode. If a transfer request is generated for another channel, an DMA cycle for the other channel is generated before the next block transfer. The DREQ pin sensing timing is different for low level sensing and falling edge sensing. The same applies to transfer request acceptance and transfer start timing. Figures 7.42 to 7.45 show operation timing examples for various conditions. • • • • No contention/dual address mode/low level sensing (see figure 7.42) No contention/single address mode/falling edge sensing (see figure 7.43) CPU cycles/single address mode/low level sensing (see figure 7.44) Contention with another channel/dual address mode/low level sensing (see figure 7.45)
Rev. 2.00, 03/04, page 207 of 534
Rev. 2.00, 03/04, page 208 of 534
φ pin
1-block-size transfer period
Last block
Last transfer in block
3 cycles
Last transfer cycle
Bus cycle
Repeated
Bus release
DMA read
DMA write
DMA read
DMA write
DMA read
DMA write
Bus release
DMA read
DMA write
DMA read
Repeated
DMA write
Bus release
Figure 7.42 External Request/Cycle Steal Mode/Block Transfer Mode (No Contention/Dual Address Mode/Low Level Sensing)
DA bit
1
0
φ pin
1-block-size transfer period
Last block
Last transfer in block
3 cycles
Last transfer cycle
Bus cycle
Bus release
DMA single transfer cycle
Repeated
DMA single transfer cycle
DMA single transfer cycle
Bus release
DMA single transfer cycle
DMA single transfer cycle
Repeated
Bus release
Figure 7.43 External Request/Cycle Steal Mode/Block Transfer Mode (No Contention/Single Address Mode/Falling Edge Sensing)
Rev. 2.00, 03/04, page 209 of 534
Rev. 2.00, 03/04, page 210 of 534
φ pin
1-block-size transfer period
Last transfer in block
2 bus cycles
CPU cycle CPU cycle
1-block-size transfer period
Last transfer in block
DMA single transfer cycle DMA single transfer cycle
Repeated
Bus cycle
Repeated
CPU cycle
CPU cycle
CPU cycle
DMA single transfer cycle
DMA single transfer cycle
CPU cycle
Figure 7.44 External Request/Cycle Steal Mode/Block Transfer Mode (CPU Cycles/Single Address Mode/Low Level Sensing)
CPU operation
CPU access
CPU access
CPU access
CPU access
CPU access
CPU access
φ pin
1-block-size transfer period
1-block-size transfer period
Last transfer in block
Last transfer in block
Other channel DMA cycle
Bus release
Bus release
Bus cycle
Bus release
Repeated
DMA read
DMA write
DMA read
DMA write
DMA read
DMA write
DMA read
Repeated
DMA write
Other channel
Figure 7.45 External Request/Cycle Steal Mode/Block Transfer Mode (Contention with Another Channel/Dual Address Mode/Low Level Sensing)
Other channel
Rev. 2.00, 03/04, page 211 of 534
7.4.12
Ending DMA Transfer
The operation for ending DMA transfer depends on the transfer end conditions. When DMA transfer ends, the DA bit in DMMDR changes from 1 to 0, indicating that DMA transfer has ended. Transfer End by 1 → 0 Transition of DMTCR: When the value of DMTCR changes from 1 to 0, DMA transfer ends on the corresponding channel and the DA bit in DMMDR is cleared to 0. If the TCEIE bit in DMMDR is set at this time, a transfer end interrupt request is generated by the transfer counter and the IRF bit in DMMDR is set to 1. In block transfer mode, DMA transfer ends when the value of bits 15 to 0 in DMTCR changes from 1 to 0. DMA transfer does not end if the DMTCR value has been 0 since before the start of transfer. Transfer End by Repeat Area Overflow Interrupt: If an address overflows the repeat area when a repeat area specification has been made and repeat interrupts have been enabled (with the SARIE or DARIE bit in DMACR), a repeat area overflow interrupt is requested. DMA transfer ends, the DA bit in DMMDR is cleared to 0, and the IRF bit in DMMDR is set to 1. In dual address mode, if a repeat area overflow interrupt is requested during a read cycle, the following write cycle processing is still executed. In block transfer mode, if a repeat area overflow interrupt is requested during transfer of a block, transfer continues to the end of the block. Transfer end by means of a repeat area overflow interrupt occurs between block-size transfers. Transfer End by 0-Write to DA Bit in DMMDR: When 0 is written to the DA bit in DMMDR by the CPU, etc., transfer ends after completion of the DMA cycle in which transfer is in progress or a transfer request was accepted. In block transfer mode, DMA transfer halts after completion of one-block-size transfer. The DA bit in DMMDR is not cleared to 0 until all transfer processing has ended. Up to that point, the value of the DA bit will be read as 1. Transfer Abort by NMI Interrupt: DMA transfer is aborted when an NMI interrupt is generated. The DA bit is cleared to 0 in all channels. In external request mode, DMA transfer is performed for all transfer requests for which DRAK has been output. In dual address mode, processing is executed for the write cycle following the read cycle. In block transfer mode, operation is aborted even in the middle of a block-size transfer. As the transfer is halted midway through a block, the BEF bit in DMMDR is set to 1 to indicate that the block transfer was not carried out normally.
Rev. 2.00, 03/04, page 212 of 534
When transfer is aborted, register values are retained, and as the address registers indicate the next transfer addresses, transfer can be resumed by setting the DA bit to 1 in DMMDR. If the BEF bit is 1 in DMMDR, transfer can be resumed from midway through a block. Hardware Standby Mode and Reset Input: The DMAC is initialized in hardware standby mode and by a reset. DMA transfer is not guaranteed in these cases. 7.4.13 Relationship between DMAC and Other Bus Masters
The read and write operations in a DMA transfer cycle are indivisible, and a refresh cycle or internal bus master (CPU) access cycle never occurs between the two. When read and write cycles occur consecutively, as in burst transfer or block transfer, a refresh may be inserted after the write cycle. As the CPU has lower priority than the DMAC, the CPU access is not executed until the DMAC releases the bus. The DMAC releases the bus in the following cases: 1. 2. 3. 4. When DMA transfer is performed in cycle steal mode When switching to a different channel When transfer ends in burst transfer mode When transfer of one block ends in block transfer mode
7.5
Interrupt Sources
DMAC interrupt sources are a transfer end indicated by the transfer counter, and repeat area overflow interrupts. Table 7.4 shows the interrupt sources and their priority. Table 7.4
Interrupt DMTEND0
Interrupt Sources and Priority Order
Interrupt source Transfer end indicated by channel 0 transfer counter Channel 0 source address repeat area overflow Channel 0 destination address repeat area overflow Transfer end indicated by channel 1 transfer counter Channel 1 source address repeat area overflow Channel 1 destination address repeat area overflow Transfer end indicated by channel 2 transfer counter Channel 2 source address repeat area overflow Channel 2 destination address repeat area overflow Transfer end indicated by channel 3 transfer counter Channel 3 source address repeat area overflow Channel 3 destination address repeat area overflow Interrupt Priority High
DMTEND1
DMTEND2
DMTEND3
Low
Rev. 2.00, 03/04, page 213 of 534
Interrupt sources can be enabled or disabled by means of the DIE bit in DMMDR for the relevant channel, and can be sent to the interrupt controller independently. The relative priority of the channels is determined by the interrupt controller (see table 7.4). Figure 7.46 shows the transfer end interrupt logic. A transfer end interrupt is generated whenever the DIE bit is set to 1 while the IRF bit is set to 1 in DMMDR.
IRF bit Transfer end interrupt DIE bit
Figure 7.46 Transfer End Interrupt Logic Interrupt source settings are made individually with the interrupt enable bits in the registers for the relevant channels. The transfer counter's transfer end interrupt is enabled or disabled by means of the TCEIE bit in DMMDR, the source address register repeat area overflow interrupt by means of the SARIE bit in DMACR, and the destination address register repeat area overflow interrupt by means of the DARIE bit in DMACR. When an interrupt source occurs while the corresponding interrupt enable bit is set to 1, the IRF bit in DMMDR is set to 1. The IRF bit is set by all interrupt sources indiscriminately. The transfer end interrupt can be cleared either by clearing the IRF bit to 0 in DMMDR within the interrupt handling routine, or by re-setting the transfer counter and address registers and then setting the DA bit to 1 in DMMDR to perform transfer continuation processing. An example of the procedure for clearing the transfer end interrupt and restarting transfer is shown in figure 7.47.
Rev. 2.00, 03/04, page 214 of 534
Transfer end interrupt exception handling routine
Transfer continuation processing Change register settings Write 1 to DA bit End of interrupt handling routine (RTE instruction execution) [1] [2]
Transfer restart after end of interrupt handling routine Clear IRF bit to 0 End of interrupt handling routine Change register settings [4]
[5]
[3]
[6]
Write 1 to DA bit End of transfer restart processing
[7]
End of transfer restart processing
[1] Write set values to the registers (transfer counter, address registers, etc.). [2] Write 1 to the DA bit in DMMDR to restart DMA operation. When 1 is written to the DA bit, the IRF bit in DMMDR is automatically cleared to 0 and the interrupt source is cleared. [3] The interrupt handling routine is ended with an RTE instruction, etc. [4] Clear the IRF bit to 0 in DMMDR by first reading 1 from it, then writing 0. [5] After the interrupt handling routine is ended with an RTE instruction, etc., interrupt masking is cleared. [6] Write set values to the registers (transfer counter, address registers, etc.). [7] Write 1 to the DA bit in DMMDR to restart DMA operation.
Figure 7.47 Example of Procedure for Restarting Transfer on Channel in which Transfer End Interrupt Occurred
Rev. 2.00, 03/04, page 215 of 534
7.6
Usage Notes
DMAC Register Access during Operation: Except for clearing the DA bit to 0 in DMMDR, settings should not be changed for a channel in operation (including the transfer standby state). Transfer must be disabled before changing a setting for an operational channel. Module Stop State: When the DMACKSTP bit is set to 1 in MSTPCR, the DMAC clock stops and the DMAC enters the module stop state. However, 1 cannot be written to the DMACKSTP bit when any of the DMAC's channels is enabled for transfer, or when an interrupt is being requested. Before setting the DMACKSTP bit, first clear the DA bit in DMMDR to 0, then clear the IRF or DIE bit in DMMDR to 0. When the DMAC clock stops, DMAC registers can no longer be accessed. The following DMAC register settings remain valid in the module stop state, and so should be changed, if necessary, before making the module stop transition. • TENDE = 1 in DMMDR (TEND pin enable) • DRAKE = 1 in DMMDR (DRAK pin enable) • AMS = 1 in DMMDR (DACK pin enable) DREQ Pin Falling Edge Activation: Falling edge sensing on the DREQ pin is performed in synchronization with DMAC internal operations, as indicated below. [1] Activation request standby state: Waits for low level sensing on DREQ pin, then goes to [2]. [2] Transfer standby state: Waits for DMAC data transfer to become possible, then goes to [3]. [3] Activation request disabled state: Waits for high level sensing on DREQ pin, then goes to [1]. After DMAC transfer is enabled, the DMAC goes to state [1], so low level sensing is used for the initial activation after transfer is enabled. Activation Source Acceptance: At the start of activation source acceptance, low level sensing is used for both falling edge sensing and low level sensing on the DREQ pin. Therefore, a request is accepted in the case of a low level at the DREQ pin that occurs before execution of the DMMDR write for setting the transfer-enabled state. When the DMAC is activated, make sure, if necessary, that a low level does not remain at the DREQ pin from the previous end of transfer, etc. Enabling Interrupt Requests when IRF = 1 in DMMDR: When transfer is started while the IRF bit is set to 1 in DMMDR, if the DIE bit is set to 1 in DMMDR together with the DA bit in DMMDR, enabling interrupt requests, an interrupt will be requested since DIE = 1 and IRF = 1. To prevent the occurrence of an erroneous interrupt request when transfer starts, ensure that the IRF bit is cleared to 0 before the DIE bit is set to 1.
Rev. 2.00, 03/04, page 216 of 534
Source Address/Destination Address: When transfer data size is specified as word or longword, an even (word) value or value multiplied by four (longword) must be set in DMSAR and DMDAR. When transfer data size is specified as word and an odd value is set in DMSAR or DMDAR, the lowest bit of the address is regarded as 0 and accessed. When transfer data size is specified as longword and a value not multiplied by four is set in DMSAR or DMDAR, the lowest two bits of the address are regarded as 0 and accessed.
Rev. 2.00, 03/04, page 217 of 534
Rev. 2.00, 03/04, page 218 of 534
Section 8 I/O Ports
Table 8.1 summarizes the port functions. The pins of each port also have other functions such as input/output or interrupt input pins of on-chip peripheral modules. Each I/O port includes a data direction register (DDR) that controls input/output, a data register (DR) that stores output data, and a port register (PORT) used to read the pin states. Ports 1 to 4 can drive a single TTL load and 30 pF capacity load. Ports 5 to 9, and A can drive a single TTL load and 50 pF capacity load. All of the I/O ports can drive a Darlington transistor when outputting data. Ports 3 (P34, P35), 5 (P52, P53, P56, P57), 7, and A (PA0, PA1) are Schmitt-triggered inputs when used as the IRQ input. Port 3 (P32, P33) is a Schmitt-triggered input when the software standby state is entered by using the USB.
Rev. 2.00, 03/04, page 219 of 534
Table 8.1
Port Port 1
Port Functions
Extended Mode (EXPE = 1) P17/USD15 P16/USD14 P15/USD13 P14/USD12 P13/USD11 P12/USD10 P11/USD9 P10/USD8 Single-Chip Mode (EXPE = 0) P17/USD15 P16/USD14 P15/USD13 P14/USD12 P13/USD11 P12/USD10 P11/USD9 P10/USD8 P27/USD7/DRAK1 P26/USD6/DACK1 P25/USD5/TEND1 P24/USD4/DREQ1 P23/USD3/DRAK0 P22/USD2/DACK0 P21/USD1/TEND0 P20/USD0/DREQ0 P37/USOPM1 P36/USOPM0 P35/(IRQ5)/VBUS P34/(IRQ4)/USTXV P33/USLSTA1 P32/USLSTA0 P31/USCLK P30/USWDVLD P47/USXCVRS P46/USTXRDY P45/USTSEL P44/USSUSP P43/USRXV P42/USRXERR P41/USRXACT P40/USRST
Description General I/O port also functioning as USB2 I/O
Port 2
General I/O port also functioning as USB2 I/O and DMAC I/O
P27/USD7/DRAK1 P26/USD6/DACK1 P25/USD5/TEND1 P24/USD4/DREQ1 P23/USD3/DRAK0 P22/USD2/DACK0 P21/USD1/TEND0 P20/USD0/DREQ0
Port 3
General I/O port also functioning as USB2 I/O and interrupt input
P37/USOPM1 P36/USOPM0 P35/(IRQ5)/VBUS P34/(IRQ4)/USTXV P33/USLSTA1 P32/USLSTA0 P31/USCLK P30/USWDVLD
Port 4
General I/O port also functioning as USB2 I/O
P47/USXCVRS P46/USTXRDY P45/USTSEL P44/USSUSP P43/USRXV P42/USRXERR P41/USRXACT P40/USRST
Rev. 2.00, 03/04, page 220 of 534
Port Port 5
Description
Extended Mode (EXPE = 1)
Single-Chip Mode (EXPE = 0) P57/(IRQ7)/DRAK3 P56/(IRQ6)/DACK3 P55/TEND3 P54/DREQ3 P53/(IRQ3)/DRAK2 P52/(IRQ2)/DACK2 P51/TEND2 P50/DREQ2 P67 P66/TMO1 P65/TMRI1 P64/TMCI1 P63 P62/TMO0 P61/TMRI0 P60/TMCI0 P77/IRQ7 P76/IRQ6 P75/IRQ5 P74/IRQ4 P73/IRQ3 P72/IRQ2 P71/IRQ1 P70/IRQ0 P87 P86 P85 P84 P83 P82 P81 P80
General I/O port also P57/D7/(IRQ7)/DRAK3 functioning as external P56/D6/(IRQ6)/DACK3 data bus I/O, DMAC I/O, P55/D5/TEND3 and interrupt input P54/D4/DREQ3 P53/D3/(IRQ3)/DRAK2 P52/D2/(IRQ2)/DACK2 P51/D1/TEND2 P50/D0/DREQ2
Port 6
General I/O port also functioning as external address bus output and timer I/O
P67/A15 P66/A14/TMO1 P65/A13/TMRI1 P64/A12/TMCI1 P63/A11 P62/A10/TMO0 P61/A9/TMRI0 P60/A8/TMCI0
Port 7
General I/O port also functioning as external address bus output and interrupt input
P77/A7/IRQ7 P76/A6/IRQ6 P75/A5/IRQ5 P74/A4/IRQ4 P73/A3/IRQ3 P72/A2/IRQ2 P71/A1/IRQ1 P70/A0/IRQ0
Port 8
General I/O port also functioning as external data bus I/O
P87/D15 P86/D14 P85/D13 P84/D12 P83/D11 P82/D10 P81/D9 P80/D8
Rev. 2.00, 03/04, page 221 of 534
Port Port 9
Description General I/O port also functioning as external bus control output
Extended Mode (EXPE = 1) P97/φ P96/AS P95/RD P94/HWR P93/LWR P92/CS2/RAS P91/CS1 P90/CS0
Single-Chip Mode (EXPE = 0) P97/φ P96 P95 P94 P93 P92 P91 P90 PA3 PA2 PA1/(IRQ1) PA0/(IRQ0)
Port A
General I/O port also functioning as external address bus output, external bus control output, and interrupt input
PA3/A19/CS3 PA2/A18/UCAS PA1/A17/LCAS/(IRQ1) PA0/A16/(IRQ0)
8.1
Port 1
Port 1 is an 8-bit I/O port that also has other functions. The port 1 has the following registers. • Port 1 data direction register (P1DDR) • Port 1 data register (P1DR) • Port 1 register (PORT1) 8.1.1 Port 1 Data Direction Register (P1DDR)
The individual bits of P1DDR specify input or output for the pins of port 1. P1DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P17DDR P16DDR P15DDR P14DDR P13DDR P12DDR P11DDR P10DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 1 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
Rev. 2.00, 03/04, page 222 of 534
8.1.2
Port 1 Data Register (P1DR)
P1DR stores output data for the port 1 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P17DR P16DR P15DR P14DR P13DR P12DR P11DR P10DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
8.1.3
Port 1 Register (PORT1)
PORT1 shows the pin states of the port 1. PORT1 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P17 P16 P15 P14 P13 P12 P11 P10 * Initial Value
* * * * * * * *
R/W R R R R R R R R
Description If a PORT1 read is performed while P1DDR bits are set to 1, the P1DR values are read. If a PORT1 read is performed while P1DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P17 to P10.
Rev. 2.00, 03/04, page 223 of 534
8.1.4
Pin Functions
Port 1 pins also function as the pins for USB I/O. The correspondence between the register specification and the pin functions is shown below. • P17/USD15 The pin function is switched as shown below according to the combination of the P17DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P17DDR Pin function 0 P17 input 1 1 P17 output 0 USD15 I/O
• P16/USD14 The pin function is switched as shown below according to the combination of the P16DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P16DDR Pin function 0 P16 input 1 1 P16 output 0 USD14 I/O
• P15/USD13 The pin function is switched as shown below according to the combination of the P15DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P15DDR Pin function 0 P15 input 1 1 P15 output 0 USD13 I/O
• P14/USD12 The pin function is switched as shown below according to the combination of the P14DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P14DDR Pin function 0 P14 input 1 1 P14 output 0 USD12 I/O
Rev. 2.00, 03/04, page 224 of 534
• P13/USD11 The pin function is switched as shown below according to the combination of the P13DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P13DDR Pin function 0 P13 input 1 1 P13 output 0 USD11 I/O
• P12/USD10 The pin function is switched as shown below according to the combination of the P12DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P12DDR Pin function 0 P12 input 1 1 P12 output 0 USD10 I/O
• P11/USD9 The pin function is switched as shown below according to the combination of the P11DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P11DDR Pin function 0 P11 input 1 1 P11 output 0 USD9 I/O
• P10/USD8 The pin function is switched as shown below according to the combination of the P10DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P10DDR Pin function 0 P10 input 1 1 P10 output 0 USD8 I/O
Rev. 2.00, 03/04, page 225 of 534
8.2
Port 2
Port 2 is an 8-bit I/O port that also has other functions. The port 2 has the following registers. • Port 2 data direction register (P2DDR) • Port 2 data register (P2DR) • Port 2 register (PORT2) 8.2.1 Port 2 Data Direction Register (P2DDR)
The individual bits of P2DDR specify input or output for the pins of port 2. P2DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P27DDR P26DDR P25DDR P24DDR P23DDR P22DDR P21DDR P20DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 2 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
8.2.2
Port 2 Data Register (P2DR)
P2DR stores output data for the port 2 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P27DR P26DR P25DR P24DR P23DR P22DR P21DR P20DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
Rev. 2.00, 03/04, page 226 of 534
8.2.3
Port 2 Register (PORT2)
PORT2 shows the pin states of the port 2. PORT2 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P27 P26 P25 P24 P23 P22 P21 P20 * Initial Value
* * * * * * * *
R/W R R R R R R R R
Description If a PORT2 read is performed while P2DDR bits are set to 1, the P2DR values are read. If a PORT2 read is performed while P2DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P27 to P20.
8.2.4
Pin Functions
Port 2 pins also function as the pins for DMAC I/O and USB I/O. The correspondence between the register specification and the pin functions is shown below. • P27/USD7/DRAK1 The pin function is switched as shown below according to the combination of the P27DDR bit, the DRAKE bit in DMMDR_1, and the USBCKSTP bit in MSTPCRL.
USBCKSTP DRAKE P27DDR Pin function 0 P27 input 0 1 P27 output 1 1 DRAK1 output 0 USD7 I/O
• P26/USD6/DACK1 The pin function is switched as shown below according to the combination of the P26DDR bit, the AMS bit in DMMDR_1, the EXPE bit in MDCR, and the USBCKSTP bit in MSTPCRL.
USBCKSTP EXPE AMS P26DDR Pin function 0 P26 input 0 1 P26 output 0 P26 input 0 1 P26 output 1 1 1 DACK1 output 0 USD6 I/O
Rev. 2.00, 03/04, page 227 of 534
• P25/USD5/TEND1 The pin function is switched as shown below according to the combination of the P25DDR bit, the TENDE bit in DMMDR_1, and the USBCKSTP bit in MSTPCRL.
USBCKSTP TENDE P25DDR Pin function 0 P25 input 0 1 P25 output 1 1 TEND1 output 0 USD5 I/O
• P24/USD4/DREQ1 The pin function is switched as shown below according to the combination of the P24DDR bit, the DREQS bit in DMMDR_1, and the USBCKSTP bit in MSTPCRL.
USBCKSTP P24DDR Pin function Note: * 0 P24 input 1 1 P24 output DREQ1 input* When DREQS = 1, this pin functions as DREQ1 input. 0 USD4 I/O
• P23/USD3/DRAK0 The pin function is switched as shown below according to the combination of the P23DDR bit, the DRAKE bit in DMMDR_0, and the USBCKSTP bit in MSTPCRL.
USBCKSTP DRAKE P23DDR Pin function 0 P23 input 0 1 P23 output 1 1 DRAK0 output 0 USD3 I/O
• P22/USD2/DACK0 The pin function is switched as shown below according to the combination of the P22DDR bit, the AMS bit in DMMDR_0, the EXPE bit in MDCR, and the USBCKSTP bit in MSTPCRL.
USBCKSTP EXPE AMS P22DDR Pin function 0 0 1 0 P22 input 0 1 P22 output 1 1 1 DACK0 output 0 USD2 I/O
P22 input P22 output
Rev. 2.00, 03/04, page 228 of 534
• P21/USD1/TEND0 The pin function is switched as shown below according to the combination of the P21DDR bit, the TENDE bit in DMMDR_0, and the USBCKSTP bit in MSTPCRL.
USBCKSTP TENDE P21DDR Pin function 0 P21 input 0 1 P21 output 1 1 TEND0 output 0 USD1 I/O
• P20/USD0/DREQ0 • The pin function is switched as shown below according to the combination of the P20DDR bit, the DREQS bit in DMMDR_0, and the USBCKSTP bit in MSTPCRL.
USBCKSTP P20DDR Pin function Note: * 0 P20 input 1 1 P20 output DREQ0 input* When DREQS = 1, this pin functions as DREQ0 input. 0 USD0 I/O
Rev. 2.00, 03/04, page 229 of 534
8.3
Port 3
Port 3 is an 8-bit I/O port that also has other functions. The port 3 has the following registers. • Port 3 data direction register (P3DDR) • Port 3 data register (P3DR) • Port 3 register (PORT3) 8.3.1 Port 3 Data Direction Register (P3DDR)
The individual bits of P3DDR specify input or output for the pins of port 3. P3DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P37DDR P36DDR P35DDR P34DDR P33DDR P32DDR P31DDR P30DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 3 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
8.3.2
Port 3 Data Register (P3DR)
P3DR stores output data for the port 3 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P37DR P36DR P35DR P34DR P33DR P32DR P31DR P30DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
Rev. 2.00, 03/04, page 230 of 534
8.3.3
Port 3 Register (PORT3)
PORT3 shows the pin states of the port 3. PORT3 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P37 P36 P35 P34 P33 P32 P31 P30 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT3 read is performed while P3DDR bits are set to 1, the P3DR values are read. If a PORT3 read is performed while P3DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P37 to P30.
8.3.4
Pin Functions
Port 3 pins also function as the pins for USB I/O and interrupt input. The correspondence between the register specification and the pin functions is shown below. • P37/USOPM1 The pin function is switched as shown below according to the combination of the P37DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P37DDR Pin function 0 P37 input 1 1 P37 output 0 USOPM1 output
• P36/USOPM0 The pin function is switched as shown below according to the combination of the P36DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P36DDR Pin function 0 P36 input 1 1 P36 output 0 USOPM0 output
Rev. 2.00, 03/04, page 231 of 534
• P35/(IRQ5)/USVBUS The pin function is switched as shown below according to the combination of the P35DDR bit, the USBCKSTP bit in MSTPCRL, and the ISS5 bit in ISSR.
USBCKSTP P35DDR Pin function Note: * 0 P35 input 1 1 P35 output IRQ5 interrupt input* When ISS5 = 1, this pin functions as IRQ5 interrupt input. 0 USVBUS input
• P34/(IRQ4)/USTXV The pin function is switched as shown below according to the combination of the P34DDR bit, the USBCKSTP bit in MSTPCRL, and the ISS4 bit in ISSR.
USBCKSTP P34DDR Pin function Note: * 0 P34 input 1 1 P34 output IRQ4 interrupt input* When ISS4 = 1, this pin functions as IRQ4 interrupt input. 0 USTXV output
• P33/USLSTA1 The pin function is switched as shown below according to the combination of the P33DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P33DDR Pin function 0 P33 input 1 1 P33 output 0 USLSTA1 input
• P32/USLSTA0 The pin function is switched as shown below according to the combination of the P32DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P32DDR Pin function 0 P32 input 1 1 P32 output 0 USLSTA0 input
Rev. 2.00, 03/04, page 232 of 534
• P31/USCLK The pin function is switched as shown below according to the combination of the P31DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P31DDR Pin function 0 P31 input 1 1 P31 output 0 USCLK input
• P30/USWDVLD The pin function is switched as shown below according to the combination of the P30DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P30DDR Pin function 0 P30 input 1 1 P30 output 0 USWDVLD I/O
8.4
Port 4
Port 4 is an 8-bit I/O port that also has other functions. The port 4 has the following registers. • Port 4 data direction register (P4DDR) • Port 4 data register (P4DR) • Port 4 register (PORT4) 8.4.1 Port 4 Data Direction Register (P4DDR)
The individual bits of P4DDR specify input or output for the pins of port 4. P4DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P47DDR P46DDR P45DDR P44DDR P43DDR P42DDR P41DDR P40DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Rev. 2.00, 03/04, page 233 of 534 Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 4 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
8.4.2
Port 4 Data Register (P4DR)
P4DR stores output data for the port 4 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P47DR P46DR P45DR P44DR P43DR P42DR P41DR P40DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
8.4.3
Port 4 Register (PORT4)
PORT4 shows the pin states of the port 4. PORT4 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P47 P46 P45 P44 P43 P42 P41 P40 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT4 read is performed while P4DDR bits are set to 1, the P4DR values are read. If a PORT4 read is performed while P4DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P47 to P40.
Rev. 2.00, 03/04, page 234 of 534
8.4.4
Pin Functions
Port 4 pins also function as the pins for USB I/O. The correspondence between the register specification and the pin functions is shown below. • P47/USXCVRS The pin function is switched as shown below according to the combination of the P47DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P47DDR Pin function 0 P47 input 1 1 P47 output 0 USXCVRS output
• P46/USTXRDY The pin function is switched as shown below according to the combination of the P46DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P46DDR Pin function 0 P46 input 1 1 P46 output 0 USTXRDY input
• P45/USTSEL The pin function is switched as shown below according to the combination of the P45DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P45DDR Pin function 0 P45 input 1 1 P45 output 0 USTSEL output
• P44/USSUSP The pin function is switched as shown below according to the combination of the P44DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P44DDR Pin function 0 P44 input 1 1 P44 output 0 USSUSP output
Rev. 2.00, 03/04, page 235 of 534
• P43/USRXV The pin function is switched as shown below according to the combination of the P43DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P43DDR Pin function 0 P43 input 1 1 P43 output 0 USRXV input
• P42/USRXERR The pin function is switched as shown below according to the combination of the P42DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P42DDR Pin function 0 P42 input 1 1 P42 output 0 USRXERR input
• P41/USRXACT The pin function is switched as shown below according to the combination of the P41DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P41DDR Pin function 0 P41 input 1 1 P41 output 0 USRXACT input
• P40/USRST The pin function is switched as shown below according to the combination of the P40DDR bit and the USBCKSTP bit in MSTPCRL.
USBCKSTP P40DDR Pin function 0 P40 input 1 1 P40 output 0 USRST output
Rev. 2.00, 03/04, page 236 of 534
8.5
Port 5
Port 5 is an 8-bit I/O port that also has other functions. The port 5 has the following registers. • Port 5 data direction register (P5DDR) • Port 5 data register (P5DR) • Port 5 register (PORT5) 8.5.1 Port 5 Data Direction Register (P5DDR)
The individual bits of P5DDR specify input or output for the pins of port 5. P5DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P57DDR P56DDR P55DDR P54DDR P53DDR P52DDR P51DDR P50DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 5 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
8.5.2
Port 5 Data Register (P5DR)
P5DR stores output data for the port 5 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P57DR P56DR P55DR P54DR P53DR P52DR P51DR P50DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
Rev. 2.00, 03/04, page 237 of 534
8.5.3
Port 5 Register (PORT5)
PORT5 shows the pin states of the port 5. PORT5 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P57 P56 P55 P54 P53 P52 P51 P50 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT5 read is performed while P5DDR bits are set to 1, the P5DR values are read. If a PORT5 read is performed while P5DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P57 to P50.
8.5.4
Pin Functions
Port 5 pins also function as the pins for external data bus I/O, DMAC I/O, and interrupt input. The correspondence between the register specification and the pin functions is shown below. • P57/D7/(IRQ7)/DRAK3 The pin function is switched as shown below according to the combination of the P57DDR bit, the DRAKE bit in DMMDR_3, the EXPE bit in MDCR, and the ISS7 bit in ISSR.
EXPE Bus mode 0 1 All areas are 8-bit space At least one area is 16-bit space 1 1 P57 output DRAK3 output D7 I/O
DRAKE P57DDR Pin function 0 P57 input
0 1 P57 output 0 P57 input
0
IRQ7 interrupt input* Note: * When ISS7 = 1, this pin functions as IRQ7 interrupt input.
Rev. 2.00, 03/04, page 238 of 534
• P56/D6/(IRQ6)/DACK3 The pin function is switched as shown below according to the combination of the P56DDR bit, the AMS bit in DMMDR_3, the EXPE bit in MDCR, and the ISS6 bit in ISSR.
EXPE Bus mode 0 1 All areas are 8-bit space At least one area is 16-bit space 1 1 P56 output DACK3 output D6 I/O
AMS P56DDR Pin function 0 P56 input
0 1 P56 output 0 P56 input
0
IRQ6 interrupt input* Note: * When ISS6 = 1, this pin functions as IRQ6 interrupt input.
• P55/D5/TEND3 The pin function is switched as shown below according to the combination of the P55DDR bit, the TENDE bit in DMMDR_3, and the EXPE bit in MDCR.
EXPE Bus mode 0 1 All areas are 8-bit space At least one area is 16-bit space 1 1 P55 output TEND3 output D5 I/O
TENDE P55DDR Pin function 0 P55 input
0 1 P55 output 0 P55 input
0
• P54/D4/DREQ3 The pin function is switched as shown below according to the combination of the P54DDR bit, the DREQS bit in DMMDR_3, and the EXPE bit in MDCR.
EXPE Bus mode P54DDR Pin function Note: * 0 P54 input 0 1 P54 output 1 All areas are 8-bit space 0 P54 input DREQ3 input* When DREQS = 1, this pin functions as DREQ3 input. 1 P54 output At least one area is 16-bit space D4 I/O
Rev. 2.00, 03/04, page 239 of 534
• P53/D3/(IRQ3)/DRAK2 The pin function is switched as shown below according to the combination of the P53DDR bit, the DRAKE bit in DMMDR_2, the EXPE bit in MDCR, and the ISS3 bit in ISSR.
EXPE Bus mode 0 1 All areas are 8-bit space At least one area is 16-bit space 1 1 P53 output DRAK2 output D3 I/O
DRAKE P53DDR Pin function 0 P53 input
0 1 P53 output 0 P53 input
0
IRQ3 interrupt input* Note: * When ISS3 = 1, this pin functions as IRQ3 interrupt input.
• P52/D2/(IRQ2)/DACK2 The pin function is switched as shown below according to the combination of the P52DDR bit, the AMS bit in DMMDR_2, the EXPE bit in MDCR, and the ISS2 bit in ISSR.
EXPE Bus mode 0 1 All areas are 8-bit space At least one area is 16-bit space 1 1 P52 output DACK2 output D2 I/O
AMS P52DDR Pin function 0 P52 input
0 1 P52 output 0 P52 input
0
IRQ2 interrupt input* Note: * When ISS2 = 1, this pin functions as IRQ2 interrupt input.
Rev. 2.00, 03/04, page 240 of 534
• P51/D1/TEND2 The pin function is switched as shown below according to the combination of the P51DDR bit, the TENDE bit in DMMDR_2, and the EXPE bit in MDCR.
EXPE Bus mode 0 1 All areas are 8-bit space At least one area is 16-bit space 1 1 P51 output TEND2 output D1 I/O
TENDE P51DDR Pin function 0 P51 input
0 1 P51 output 0 P51 input
0
• P50/D0/DREQ2 The pin function is switched as shown below according to the combination of the P50DDR bit, the DREQS bit in DMMDR_2, and the EXPE bit in MDCR.
EXPE Bus mode P50DDR Pin function Note: * 0 P50 input 0 1 P50 output 1 All areas are 8-bit space 0 P50 input DREQ2 input* When DREQS = 1, this pin functions as DREQ2 input. 1 P50 output At least one area is 16-bit space D0 I/O
Rev. 2.00, 03/04, page 241 of 534
8.6
Port 6
Port 6 is an 8-bit I/O port that also has other functions. The port 6 has the following registers. • Port 6 data direction register (P6DDR) • Port 6 data register (P6DR) • Port 6 register (PORT6) 8.6.1 Port 6 Data Direction Register (P6DDR)
The individual bits of P6DDR specify input or output for the pins of port 6. P6DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P67DDR P66DDR P65DDR P64DDR P63DDR P62DDR P61DDR P60DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 6 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
8.6.2
Port 6 Data Register (P6DR)
P6DR stores output data for the port 6 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P67DR P66DR P65DR P64DR P63DR P62DR P61DR P60DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
Rev. 2.00, 03/04, page 242 of 534
8.6.3
Port 6 Register (PORT6)
PORT6 shows the pin states of the port 6. PORT6 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P67 P66 P65 P64 P63 P62 P61 P60 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT6 read is performed while P6DDR bits are set to 1, the P6DR values are read. If a PORT6 read is performed while P6DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P67 to P60.
8.6.4
Pin Functions
Port 6 pins also function as the pins for external address bus output and timer I/O. The correspondence between the register specification and the pin functions is shown below. • P67/A15 The pin function is switched as shown below according to the combination of the P67DDR bit, the EXPE bit in MDCR, and the AMOE bit in PFCR1.
EXPE AMOE P67DDR Pin function 0 P67 input 0 1 P67 output 0 P67 input 0 1 P67 output 1 1 A15 output
Rev. 2.00, 03/04, page 243 of 534
• P66/A14/TMO1 The pin function is switched as shown below according to the combination of the P66DDR bit, the EXPE bit in MDCR, the AMOE bit in PFCR1, and the OS3 to OS0 bits in TCSR_1.
EXPE AMOE OS3 to OS0 P66DDR Pin function 0 P66 input All 0 1 P66 output 0 Not all 0 TMO1 output 0 P66 input All 0 1 P66 output 0 Not all 0 TMO1 output 1 1 A14 output
• P65/A13/TMRI1 The pin function is switched as shown below according to the combination of the P65DDR bit, the EXPE bit in MDCR, and the AMOE bit in PFCR1.
EXPE AMOE P65DDR Pin function Note: * 0 P65 input 0 1 P65 output 0 P65 input TMRI1 input* When used as a TMR counter reset, set the CCLR1 and CCLR0 bits in TCR_1 to 11. 0 1 P65 output 1 1 A13 output
• P64/A12/TMCI1 The pin function is switched as shown below according to the combination of the P64DDR bit, the EXPE bit in MDCR, and the AMOE bit in PFCR1.
EXPE AMOE P64DDR Pin function Note: * 0 P64 input 0 1 P64 output 0 P64 input TMCI1 input* When used as an external clock input pin of TMR, select the external clock by bits CKS2 to CKS0 in TCR_1. 0 1 P64 output 1 1 A12 output
Rev. 2.00, 03/04, page 244 of 534
• P63/A11 The pin function is switched as shown below according to the combination of the P63DDR bit, the EXPE bit in MDCR, and the AMOE bit in PFCR1.
EXPE AMOE P63DDR Pin function 0 P63 input 0 1 P63 output 0 P63 input 0 1 P63 output 1 1 A11 output
• P62/A10/TMO0 The pin function is switched as shown below according to the combination of the P62DDR bit, the EXPE bit in MDCR, the AMOE bit in PFCR1, and the OS3 to OS0 bits in TCSR_0.
EXPE AMOE OS3 to OS0 P62DDR Pin function 0 All 0 1 0 Not all 0 TMO0 output 0 All 0 1 0 Not all 0 TMO0 output 1 1 A10 output
P62 input P62 output
P62 input P62 output
• P61/A9/TMRI0 The pin function is switched as shown below according to the combination of the P61DDR bit, the EXPE bit in MDCR, and the AMOE bit in PFCR1.
EXPE AMOE P61DDR Pin function Note: * 0 P61 input 0 1 P61 output 0 P61 input TMRI0 input* When used as a TMR counter reset, set the CCLR1 and CCLR0 bits in TCR_0 to 11. 0 1 P61 output 1 1 A9 output
Rev. 2.00, 03/04, page 245 of 534
• P60/A8/TMCI0 The pin function is switched as shown below according to the combination of the P60DDR bit, the EXPE bit in MDCR, and the AMOE bit in PFCR1.
EXPE AMOE P60DDR Pin function Note: * 0 P60 input 0 1 P60 output 0 P60 input 0 1 P60 output 1 1 A8 output
TMCI0 input* When used as an external clock input pin of TMR, select the external clock by bits CKS2 to CKS0 in TCR_0.
8.7
Port 7
Port 7 is an 8-bit I/O port that also has other functions. The port 7 has the following registers. • Port 7 data direction register (P7DDR) • Port 7 data register (P7DR) • Port 7 register (PORT7) 8.7.1 Port 7 Data Direction Register (P7DDR)
The individual bits of P7DDR specify input or output for the pins of port 7. P7DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P77DDR P76DDR P75DDR P74DDR P73DDR P72DDR P71DDR P70DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 7 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
Rev. 2.00, 03/04, page 246 of 534
8.7.2
Port 7 Data Register (P7DR)
P7DR stores output data for the port 7 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P77DR P76DR P75DR P74DR P73DR P72DR P71DR P70DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
8.7.3
Port 7 Register (PORT7)
PORT7 shows the pin states of the port 7. PORT7 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P77 P76 P75 P74 P73 P72 P71 P70 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT7 read is performed while P7DDR bits are set to 1, the P7DR values are read. If a PORT7 read is performed while P7DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P77 to P70.
Rev. 2.00, 03/04, page 247 of 534
8.7.4
Pin Functions
Port 7 pins also function as the pins for external address bus output and interrupt input. The correspondence between the register specification and the pin functions is shown below. • P77/A7/IRQ7 The pin function is switched as shown below according to the combination of the P77DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS7 bit in ISSR.
EXPE ALOE P77DDR Pin function Note: * 0 P77 input 0 1 P77 output 0 P77 input IRQ7 interrupt input* When ISS7 = 0, this pin functions as IRQ7 interrupt input. 0 1 P77 output 1 1 A7 output
• P76/A6/IRQ6 The pin function is switched as shown below according to the combination of the P76DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS6 bit in ISSR.
EXPE ALOE P76DDR Pin function Note: * 0 P76 input 0 1 P76 output 0 P76 input IRQ6 interrupt input* When ISS6 = 0, this pin functions as IRQ6 interrupt input. 0 1 P76 output 1 1 A6 output
• P75/A5/IRQ5 The pin function is switched as shown below according to the combination of the P75DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS5 bit in ISSR.
EXPE ALOE P75DDR Pin function Note: * 0 P75 input 0 1 P75 output 0 P75 input IRQ5 interrupt input* When ISS5 = 0, this pin functions as IRQ5 interrupt input. 0 1 P75 output 1 1 A5 output
Rev. 2.00, 03/04, page 248 of 534
• P74/A4/IRQ4 The pin function is switched as shown below according to the combination of the P74DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS4 bit in ISSR.
EXPE ALOE P74DDR Pin function Note: * 0 P74 input 0 1 P74 output 0 P74 input IRQ4 interrupt input* When ISS4 = 0, this pin functions as IRQ4 interrupt input. 0 1 P74 output 1 1 A4 output
• P73/A3/IRQ3 The pin function is switched as shown below according to the combination of the P73DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS3 bit in ISSR.
EXPE ALOE P73DDR Pin function Note: * 0 P73 input 0 1 P73 output 0 P73 input IRQ3 interrupt input* When ISS3 = 0, this pin functions as IRQ3 interrupt input. 0 1 P73 output 1 1 A3 output
• P72/A2/IRQ2 The pin function is switched as shown below according to the combination of the P72DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS2 bit in ISSR.
EXPE ALOE P72DDR Pin function 0 P72 input 0 1 P72 output 0 P72 input IRQ2 interrupt input* Note: * When ISS2 = 0, this pin functions as IRQ2 interrupt input. 0 1 P72 output 1 1 A2 output
Rev. 2.00, 03/04, page 249 of 534
• P71/A1/IRQ1 The pin function is switched as shown below according to the combination of the P71DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS1 bit in ISSR.
EXPE ALOE P71DDR Pin function Note: * 0 P71 input 0 1 P71 output 0 P71 input IRQ1 interrupt input* When ISS1 = 0, this pin functions as IRQ1 interrupt input. 0 1 P71 output 1 1 A1 output
• P70/A0/IRQ0 The pin function is switched as shown below according to the combination of the P70DDR bit, the EXPE bit in MDCR, the ALOE bit in PFCR1, and the ISS0 bit in ISSR.
EXPE ALOE P70DDR Pin function 0 P70 input 0 1 P70 output 0 P70 input IRQ0 interrupt input* Note: * When ISS0 = 0, this pin functions as IRQ0 interrupt input. 0 1 P70 output 1 1 A0 output
Rev. 2.00, 03/04, page 250 of 534
8.8
Port 8
Port 8 is an 8-bit I/O port that also has other functions. The port 8 has the following registers. • Port 8 data direction register (P8DDR) • Port 8 data register (P8DR) • Port 8 register (PORT8) 8.8.1 Port 8 Data Direction Register (P8DDR)
The individual bits of P8DDR specify input or output for the pins of port 8. P8DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P87DDR P86DDR P85DDR P84DDR P83DDR P82DDR P81DDR P80DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 8 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
8.8.2
Port 8 Data Register (P8DR)
P8DR stores output data for the port 8 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P87DR P86DR P85DR P84DR P83DR P82DR P81DR P80DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
Rev. 2.00, 03/04, page 251 of 534
8.8.3
Port 8 Register (PORT8)
PORT8 shows the pin states of the port 8. PORT8 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P87 P86 P85 P84 P83 P82 P81 P80 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT8 read is performed while P8DDR bits are set to 1, the P8DR values are read. If a PORT8 read is performed while P8DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P87 to P80.
8.8.4
Pin Functions
Port 8 pins also function as the pins for external data bus I/O. The correspondence between the register specification and the pin functions is shown below. • P87/D15 The pin function is switched as shown below according to the combination of the P87DDR bit and the EXPE bit in MDCR.
EXPE P87DDR Pin function 0 P87 input 0 1 P87 output 1 D15 I/O
• P86/D14 The pin function is switched as shown below according to the combination of the P86DDR bit and the EXPE bit in MDCR.
EXPE P86DDR Pin function 0 P86 input 0 1 P86 output 1 D14 I/O
Rev. 2.00, 03/04, page 252 of 534
• P85/D13 The pin function is switched as shown below according to the combination of the P85DDR bit and the EXPE bit in MDCR.
EXPE P85DDR Pin function 0 P85 input 0 1 P85 output 1 D13 I/O
• P84/D12 The pin function is switched as shown below according to the combination of the P84DDR bit and the EXPE bit in MDCR.
EXPE P84DDR Pin function 0 P84 input 0 1 P84 output 1 D12 I/O
• P83/D11 The pin function is switched as shown below according to the combination of the P83DDR bit and the EXPE bit in MDCR.
EXPE P83DDR Pin function 0 P83 input 0 1 P83 output 1 D11 I/O
• P82/D10 The pin function is switched as shown below according to the combination of the P82DDR bit and the EXPE bit in MDCR.
EXPE P82DDR Pin function 0 P82 input 0 1 P82 output 1 D10 I/O
• P81/D9 The pin function is switched as shown below according to the combination of the P81DDR bit and the EXPE bit in MDCR.
EXPE P81DDR Pin function 0 P81 input 0 1 P81 output 1 D9 I/O
Rev. 2.00, 03/04, page 253 of 534
• P80/D8 The pin function is switched as shown below according to the combination of the P80DDR bit and the EXPE bit in MDCR.
EXPE P80DDR Pin function 0 P80 input 0 1 P80 output 1 D8 I/O
8.9
Port 9
Port 9 is an 8-bit I/O port that also has other functions. The port 9 has the following registers. • Port 9 data direction register (P9DDR) • Port 9 data register (P9DR) • Port 9 register (PORT9) 8.9.1 Port 9 Data Direction Register (P9DDR)
The individual bits of P9DDR specify input or output for the pins of port 9. P9DDR cannot be read; if it is, an undefined value will be read.
Bit 7 6 5 4 3 2 1 0 Bit Name P97DDR P96DDR P95DDR P94DDR P93DDR P92DDR P91DDR P90DDR Initial Value 0 0 0 0 0 0 0 0 R/W W W W W W W W W Description When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port 9 pin an output pin, while clearing this bit to 0 makes the pin an input pin.
Rev. 2.00, 03/04, page 254 of 534
8.9.2
Port 9 Data Register (P9DR)
P9DR stores output data for the port 9 pins.
Bit 7 6 5 4 3 2 1 0 Bit Name P97DR P96DR P95DR P94DR P93DR P92DR P91DR P90DR Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Output data for a pin is stored when the pin function is specified to a general purpose output.
8.9.3
Port 9 Register (PORT9)
PORT9 shows the pin states of the port 9. PORT9 cannot be modified.
Bit 7 6 5 4 3 2 1 0 Note: Bit Name P97 P96 P95 P94 P93 P92 P91 P90 * Initial Value * * * * * * * * R/W R R R R R R R R Description If a PORT9 read is performed while P9DDR bits are set to 1, the P9DR values are read. If a PORT9 read is performed while P9DDR bits are cleared to 0, the pin states are read.
Determined by the states of pins P97 to P90.
Rev. 2.00, 03/04, page 255 of 534
8.9.4
Pin Functions
Port 9 pins also function as the pins for external bus control output. The correspondence between the register specification and the pin functions is shown below. • P97/φ The pin function is switched as shown below according to the combination of the P97DDR bit and the CKOE bit in PFCR1.
CKOE P97DDR Pin function 0 P97 input 0 1 P97 output 1 φ output
• P96/AS The pin function is switched as shown below according to the combination of the P96DDR bit and the EXPE bit in MDCR.
EXPE P96DDR Pin function 0 P96 input 0 1 P96 output 1 AS output
• P95/RD The pin function is switched as shown below according to the combination of the P95DDR bit and the EXPE bit in MDCR.
EXPE P95DDR Pin function 0 P95 input 0 1 P95 output 1 RD output
• P94/HWR The pin function is switched as shown below according to the combination of the P94DDR bit and the EXPE bit in MDCR.
EXPE P94DDR Pin function 0 P94 input 0 1 P94 output 1 HWR output
Rev. 2.00, 03/04, page 256 of 534
• P93/LWR The pin function is switched as shown below according to the combination of the P93DDR bit and the EXPE bit in MDCR.
EXPE Bus mode P93DDR Pin function 0 P93 input 0 1 P93 output All areas are 8-bit space 0 P93 input 1 P93 output 1 At least one area is 16-bit space LWR output
• P92/CS2/RAS The pin function is switched as shown below according to the combination of the P92DDR bit, the EXPE bit in MDCR, and the CS2E bit in PFCR1.
EXPE Area 2 CS2E P92DDR Pin function 0 P92 input 0 1 P92 output 0 P92 input 1 Normal space 0 1 P92 output 1 DRAM space
CS2 output RAS output
• P91/CS1 The pin function is switched as shown below according to the combination of the P91DDR bit, the EXPE bit in MDCR, and the CS1E bit in PFCR1.
EXPE CS1E P91DDR Pin function 0 P91 input 0 1 P91 output 0 P91 input 0 1 P91 output 1 1 CS1 output
• P90/CS0 The pin function is switched as shown below according to the combination of the P90DDR bit and the EXPE bit in MDCR.
EXPE P90DDR Pin function 0 P90 input 0 1 P90 output 1 CS0 output
Rev. 2.00, 03/04, page 257 of 534
8.10
Port A
Port A is a 4-bit I/O port that also has other functions. The port A has the following registers. • Port A data direction register (PADDR) • Port A data register (PADR) • Port A register (PORTA) 8.10.1 Port A Data Direction Register (PADDR)
The individual bits of PADDR specify input or output for the pins of port A. PADDR cannot be read; if it is, an undefined value will be read.
Bit 7 to 4 Bit Name Initial Value R/W Description Reserved If these bits are read, an undefined value will be read. These bits cannot be modified. 3 2 1 0 PA3DDR PA2DDR PA1DDR PA0DDR 0 0 0 0 W W W W When a pin function is specified to a general purpose I/O, setting this bit to 1 makes the corresponding port A pin an output pin, while clearing this bit to 0 makes the pin an input pin.
Undefined
8.10.2
Port A Data Register (PADR)
PADR stores output data for the port A pins.
Bit 7 to 4 Bit Name Initial Value R/W Description Reserved If these bits are read, an undefined value will be read. These bits cannot be modified. 3 2 1 0 PA3DR PA2DR PA1DR PA0DR 0 0 0 0 R/W R/W R/W R/W Output data for a pin is stored when the pin function is specified to a general purpose output.
Undefined
Rev. 2.00, 03/04, page 258 of 534
8.10.3
Port A Register (PORTA)
PORTA shows the pin states of the port A. PORTA cannot be modified.
Bit 7 Bit Name RxDMON Initial Value *
1
R/W R
Description This bit is read as the reversed value of the HUDIDI/RxD0 pin. 1 is read when the HUDIDI/RxD0 pin is low, and 0 is read when HUDIDI/RxD0 pin is high. Reserved If these bits are read, an undefined value will be read. If a PORTA read is performed while PADDR bits are set to 1, the PADR values are read. If a PORTA read is performed while PADDR bits are cleared to 0, the pin states are read.
6 to 4 3 2 1 0
PA3 PA2 PA1 PA0
Undefined * * * *
2 2 2 2
R R R R
Notes: 1. Determined by the state of the HUDIDI/RxD0 pin. 2. Determined by the states of pins PA3 to PA0.
8.10.4
Pin Functions
Port A pins also function as the pins for external address bus output, external bus control signal output, and interrupt input. The correspondence between the register specification and the pin functions is shown below. • PA3/A19/CS3 The pin function is switched as shown below according to the combination of the PA3DDR bit, the EXPE bit in MDCR, and the CS3E and AHOE bits in PFCR1.
EXPE CS3E AHOE PA3DDR Pin function 0 PA3 input 0 1 PA3 output 0 PA3 input 0 1 PA3 output 0 1 1 1
A19 output CS3 output
Rev. 2.00, 03/04, page 259 of 534
• PA2/A18/UCAS The pin function is switched as shown below according to the combination of the PA2DDR bit, the EXPE bit in MDCR, and the AHOE bit in PFCR1.
EXPE Area 2 AHOE PA2DDR Pin function 0 PA2 input 0 1 PA2 output 0 PA2 input 1 Normal space 0 1 PA2 output 1 DRAM space
A18 output UCAS output
• PA1/A18/UCAS The pin function is switched as shown below according to the combination of the PA2DDR bit, the EXPE bit in MDCR, and the AHOE bit in PFCR1.
EXPE Area 2 AHOE PA1DDR Pin function 0 PA1 input 0 1 PA1 output 0 PA1 input 1 Normal space 0 1 PA1 output 1 A17 output DRAM space LCAS output
IRQ1 interrupt input* Note: * When ISS1 = 1, this pin functions as IRQ1 interrupt input.
• PA0/A16/(IRQ0) The pin function is switched as shown below according to the combination of the PA0DDR bit, the EXPE bit in MDCR, the AHOE bit in PFCR1, and the ISS0 bit in ISSR.
EXPE AHOE PA0DDR Pin function Note: * 0 PA0 input 0 1 PA0 output 0 PA0 input IRQ0 interrupt input* When ISS0 = 1, this pin functions as IRQ0 interrupt input. 0 1 PA0 output 1 1 A16 output
Rev. 2.00, 03/04, page 260 of 534
8.11
8.11.1
Pin Selection
Port Function Control Register 1 (PFCR1)
PFCR1 performs I/O port control for the external interface pin and φ output pin.
Bit 7 Bit Name Initial Value 0 R/W R/W Description Reserved This bit can be read from or written to. However, the write value should always be 0. 6 CS1E 0 R/W CS1 Enable Enables or disables output for CS1. 0: Set as I/O port 1: Set as CS1 output pin 5 CS2E 0 R/W CS2 Enable Enables or disables output for CS2. 0: Set as I/O port 1: Set as CS2 output pin 4 CS3E 0 R/W CS3 Enable Enables or disables output for CS3. 0: Set as I/O port 1: Set as CS3 output pin 3 CKOE 1 R/W φ Output Enable Enables or disables output for φ. 0: Set as I/O port 1: Set as φ output pin 2 ALOE 1 R/W Address Output Enable Enables or disables address output. 0: Set as I/O port 1: Set A7 to A0 pins as address output pins 1 AMOE 1 R/W Address Output Enable Enables or disables address output. 0: Set as I/O port 1: Set A15 to A8 pins as address output pins
Rev. 2.00, 03/04, page 261 of 534
Bit 0
Bit Name AHOE
Initial Value 0
R/W R/W
Description Address Output Enable Enables or disables address output. 0: Set as I/O port 1: Set A19 to A16 pins as address output pins
8.11.2
IRQ Sense Port Select Register (ISSR)
ISSR selects the input pins for IRQ7 to IRQ0.
Bit 7 Bit Name ISS7 Initial Value 0 R/W R/W Description Selects an input pin for IRQ7. 0: P77 1: P57 6 ISS6 0 R/W Selects an input pin for IRQ6. 0: P76 1: P56 5 ISS5 0 R/W Selects an input pin for IRQ5. 0: P75 1: P35 4 ISS4 0 R/W Selects an input pin for IRQ4. 0: P74 1: P34 3 ISS3 0 R/W Selects an input pin for IRQ3. 0: P73 1: P53 2 ISS2 0 R/W Selects an input pin for IRQ2. 0: P72 1: P52 1 ISS1 0 R/W Selects an input pin for IRQ1. 0: P71 1: PA1 0 ISS0 0 R/W Selects an input pin for IRQ0. 0: P70 1: PA0 Rev. 2.00, 03/04, page 262 of 534
Section 9 8-Bit Timer (TMR)
This LSI has an on-chip 8-bit timer module with two channels operating on the basis of an 8-bit counter. The 8-bit timer module can be used to count external events and be used as a multifunction timer in a variety of applications, such as generation of counter reset, interrupt requests, and pulse output with an arbitrary duty cycle using a compare-match signal with two registers.
9.1
Features
• Selection of four clock sources The counters can be driven by one of three internal clock signals (φ/8, φ/64, or φ/8192) or an external clock input • Selection of three ways to clear the counters The counters can be cleared on compare match A or B, or by an external reset signal • Timer output control by a combination of two compare match signals The timer output signal in each channel is controlled by a combination of two independent compare match signals, enabling the timer to generate output waveforms with an arbitrary duty cycle or PWM output • Provision for cascading of two channels (TMR_0 and TMR_1) Operation as a 16-bit timer is possible, using TMR_0 for the upper 8 bits and TMR_1 for the lower 8 bits (16-bit count mode) TMR_1 can be used to count TMR_0 compare matches (compare match count mode) • Three independent interrupts Compare match A and B and overflow interrupts can be requested independently
Rev. 2.00, 03/04, page 263 of 534
Figure 9.1 shows a block diagram of the 8-bit timer module (TMR_0 and TMR_1).
External clock source
TMCI0 TMCI1
Internal clock sources TMR_0 TMR_1 φ/8 φ/8 φ/64 φ/64 φ/8192 φ/8192
Clock select
Clock 1 Clock 0
TCORA_0 TCORA_1
Compare match A1 Compare match A0 Comparator A_0
TMO0 TMRI0
Overflow 1 Overflow 0 Clear 0 Control logic Compare match B1 Compare match B0 Comparator B_0
Comparator A_1
TCNT_0
TCNT_1
Internal bus
Clear 1
Comparator B_1
TMO1 TMRI1
TCORB_0 TCSR_0 TCR_0
TCORB_1 TCSR_1 TCR_1
CMIA0 CMIB0 OVI0 CMIA1 CMIB1 OVI1 Interrupt signals
[Legend] TCORA_0 : Time constant register A_0 TCORB_0 : Time constant register B_0 TCNT_0 : Timer counter_0 TCSR_0 : Timer control/status register_0 TCR_0 : Timer control register_0
TCORA_1 : Time constant register A_1 TCORB_1 : Time constant register B_1 TCNT_1 : Timer counter_1 TCSR_1 : Timer control/status register_1 TCR_1 : Timer control register_1
Figure 9.1 Block Diagram of 8-Bit Timer Module
Rev. 2.00, 03/04, page 264 of 534
9.2
Input/Output Pins
Table 9.1 shows the pin configuration of the 8-bit timer module. Table 9.1
Channel 0
Pin Configuration
Name Timer output pin Timer clock input pin Timer reset input pin Symbol TMO0 TMCI0 TMRI0 TMO1 TMCI1 TMRI1 I/O Output Input Input Output Input Input Function Outputs at compare match Inputs external clock for counter Inputs external reset to counter Outputs at compare match Inputs external clock for counter Inputs external reset to counter
1
Timer output pin Timer clock input pin Timer reset input pin
9.3
Register Descriptions
The 8-bit timer module has the following registers. For details on the module stop control register, refer to section 16.1.2 Module Stop Control Registers H and L (MSTPCRH, MSTPCRL). • • • • • • • • • • Timer counter_0 (TCNT_0) Time constant register A_0 (TCORA_0) Time constant register B_0 (TCORB_0) Timer control register_0 (TCR_0) Timer control/status register_0 (TCSR_0) Timer counter_1 (TCNT_1) Time constant register A_1 (TCORA_1) Time constant register B_1 (TCORB_1) Timer control register_1 (TCR_1) Timer control/status register_1 (TCSR_1) Timer Counter (TCNT)
9.3.1
TCNT is 8-bit up-counter. TCNT_0 and TCNT_1 comprise a single 16-bit register so they can be accessed together by a word transfer instruction. Bits CKS2 to CKS0 in TCR are used to select a clock. TCNT can be cleared by an external reset input or by a compare match signal A or B. Which signal is to be used for clearing is selected by bits CCLR1 and CCLR0 in TCR. When TCNT overflows from H'FF to H'00, OVF in TCSR is set to 1. TCNT is initialized to H'00.
Rev. 2.00, 03/04, page 265 of 534
9.3.2
Time Constant Register A (TCORA)
TCORA is 8-bit readable/writable register. TCORA_0 and TCORA_1 comprise a single 16-bit register so they can be accessed together by a word transfer instruction. The value in TCORA is continually compared with the value in TCNT. When a match is detected, the corresponding CMFA flag in TCSR is set to 1. Note, however, that comparison is disabled during the T2 state of a TCORA write cycle. The timer output from the TMO pin can be freely controlled by this compare match signal (compare match A) and the settings of bits OS1 and OS0 in TCSR. TCORA is initialized to H'FF. 9.3.3 Time Constant Register B (TCORB)
TCORB is 8-bit readable/writable register. TCORB_0 and TCORB_1 comprise a single 16-bit register so they can be accessed together by a word transfer instruction. TCORB is continually compared with the value in TCNT. When a match is detected, the corresponding CMFB flag in TCSR is set to 1. Note, however, that comparison is disabled during the T2 state of a TCOBR write cycle. The timer output from the TMO pin can be freely controlled by this compare match signal (compare match B) and the settings of bits OS3 and OS2 in TCSR. TCORB is initialized to H'FF. 9.3.4 Timer Control Register (TCR)
TCR selects the clock source and the time at which TCNT is cleared, and controls interrupts.
Bit 7 Bit Name CMIEB Initial Value 0 R/W R/W Description Compare Match Interrupt Enable B Selects whether CMFB interrupt requests (CMIB) are enabled or disabled when the CMFB flag in TCSR is set to 1. 0: CMFB interrupt requests (CMIB) are disabled 1: CMFB interrupt requests (CMIB) are enabled
Rev. 2.00, 03/04, page 266 of 534
Bit 6
Bit Name CMIEA
Initial Value 0
R/W R/W
Description Compare Match Interrupt Enable A Selects whether CMFA interrupt requests (CMIA) are enabled or disabled when the CMFA flag in TCSR is set to 1. 0: CMFA interrupt requests (CMIA) are disabled 1: CMFA interrupt requests (CMIA) are enabled
5
OVIE
0
R/W
Timer Overflow Interrupt Enable Selects whether OVF interrupt requests (OVI) are enabled or disabled when the OVF flag in TCSR is set to 1. 0: OVF interrupt requests (OVI) are disabled 1: OVF interrupt requests (OVI) are enabled
4 3
CCLR1 CCLR0
0 0
R/W R/W
Counter Clear 1 and 0 These bits select the method by which TCNT is cleared 00: Clearing is disabled 01: Clear by compare match A 10: Clear by compare match B 11: Clear by rising edge of external reset input
2 1 0
CKS2 CKS1 CKS0
0 0 0
R/W R/W R/W
Clock Select 2 to 0 These bits select the clock input to TCNT and count condition. See table 9.2.
Rev. 2.00, 03/04, page 267 of 534
Table 9.2
Clock Input to TCNT and Count Condition
TCR
Channel TMR_0
Bit 2 CKS2 0
Bit 1 CKS1 0
Bit 0 CKS0 0 1
Description Clock input disabled Internal clock, counted at falling edge of φ/8 Internal clock, counted at falling edge of φ/64 Internal clock, counted at falling edge of φ/8192 Count at TCNT_1 overflow signal* Clock input disabled Internal clock, counted at falling edge of φ/8 Internal clock, counted at falling edge of φ/64 Internal clock, counted at falling edge of φ/8192 Count at TCNT_0 compare match A* External clock, counted at rising edge External clock, counted at falling edge External clock, counted at both rising and falling edges
1
0 1
1 TMR_1 0
0 0
0 0 1
1
0 1
1 All 1
0 0 1 1
0 1 0 1
Note: If the count input of TMR_0 is the TCNT_1 overflow signal and that of TMR_1 is the TCNT_0 compare match signal, no incrementing clock is generated. Do not use this setting.
9.3.5
Timer Control/Status Register (TCSR)
TCSR displays status flags, and controls compare match output.
Bit 7 Bit Name CMFB Initial Value 0 R/W Description
R/(W)* Compare Match Flag B [Setting condition] • • Set when TCNT matches TCORB Cleared by reading CMFB when CMFB = 1, then writing 0 to CMFB [Clearing condition]
Rev. 2.00, 03/04, page 268 of 534
Bit 6
Bit Name CMFA
Initial Value 0
R/W
Description
R/(W)* Compare Match Flag A [Setting condition] • • Set when TCNT matches TCORA Cleared by reading CMFA when CMFA = 1, then writing 0 to CMFA [Clearing condition]
5
OVF
0
R/(W)* Timer Overflow Flag [Setting condition] • • Set when TCNT overflows from H'FF to H'00 Cleared by reading OVF when OVF = 1, then writing 0 to OVF [Clearing condition]
4
—
Undefined —
Reserved This bit is always read as an undefined value, and cannot be modified.
3 2
OS3 OS2
0 0
R/W R/W
Output Select 3 and 2 These bits select a method of TMO pin output when compare match B of TCORB and TCNT occurs. 00: No change when compare match B occurs 01: 0 is output when compare match B occurs 10: 1 is output when compare match B occurs 11: Output is inverted when compare match B occurs (toggle output)
1 0
OS1 OS0
0 0
R/W R/W
Output Select 1 and 0 These bits select a method of TMO pin output when compare match A of TCORA and TCNT occurs. 00: No change when compare match A occurs 01: 0 is output when compare match A occurs 10: 1 is output when compare match A occurs 11: Output is inverted when compare match A occurs (toggle output)
Note: Only 0 can be written to clear these flags.
Rev. 2.00, 03/04, page 269 of 534
9.4
9.4.1
Operation
Pulse Output
Figure 9.2 shows an example that the 8-bit timer is used to generate a pulse output with a selected duty cycle. The control bits are set as follows: 1 In TCR, bit CCLR1 is cleared to 0 and bit CCLR0 is set to 1 so that the timer counter is cleared at a TCORA compare match. 2 In TCSR, bits OS3 to OS0 are set to B'0110, causing the output to change to 1 at a TCORA compare match and to 0 at a TCORB compare match. With these settings, the 8-bit timer provides output of pulses at a rate determined by TCORA with a pulse width determined by TCORB. No software intervention is required.
TCNT H'FF TCORA TCORB H'00 Counter clear
TMO
Figure 9.2 Example of Pulse Output
Rev. 2.00, 03/04, page 270 of 534
9.5
9.5.1
Operation Timing
TCNT Incrementation Timing
Figure 9.3 shows the count timing for internal clock input. Figure 9.4 shows the count timing for external clock signal. Note that the external clock pulse width must be at least 1.5 states for incrementation at a single edge, and at least 2.5 states for incrementation at both edges. The counter will not increment correctly if the pulse width is less than these values.
φ
Internal clock
Clock input to TCNT
TCNT
N–1
N
N+1
Figure 9.3 Count Timing for Internal Clock Input
φ
External clock input pin
Clock input to TCNT
TCNT
N–1
N
N+1
Figure 9.4 Count Timing for External Clock Input
Rev. 2.00, 03/04, page 271 of 534
9.5.2
Timing of CMFA and CMFB Setting when Compare-Match Occurs
The CMFA and CMFB flags in TCSR are set to 1 by a compare match signal generated when the TCOR and TCNT values match. The compare match signal is generated at the last state in which the match is true, just before the timer counter is updated. Therefore, when TCOR and TCNT match, the compare match signal is not generated until the next incrementation clock input. Figure 9.5 shows this timing.
φ
TCNT
N
N+1
TCOR
Compare match signal
N
CMF
Figure 9.5 Timing of CMF Setting 9.5.3 Timing of Timer Output when Compare-Match Occurs
When compare match A or B occurs, the timer output changes as specified by bits OS3 to OS0 in TCSR. Figure 9.6 shows the timing when the output is set to toggle at compare match A.
φ
Compare match A signal
Timer output pin
Figure 9.6 Timing of Timer Output
Rev. 2.00, 03/04, page 272 of 534
9.5.4
Timing of Compare Match Clear
TCNT is cleared when compare match A or B occurs, depending on the setting of the CCLR1 and CCLR0 bits in TCR. Figure 9.7 shows the timing of this operation.
φ Compare match signal
TCNT
N
H'00
Figure 9.7 Timing of Compare Match Clear 9.5.5 Timing of TCNT External Reset
TCNT is cleared at the rising edge of an external reset input, depending on the settings of the CCLR1 and CCLR0 bits in TCR. The clear pulse width must be at least 1.5 states. Figure 9.8 shows the timing of this operation.
φ External reset input pin
Clear signal
TCNT
N–1
N
H'00
Figure 9.8 Timing of Clearance by External Reset 9.5.6 Timing of Overflow Flag (OVF) Setting
The OVF in TCSR is set to 1 when TCNT overflows (changes from H'FF to H'00). Figure 9.9 shows the timing of this operation.
Rev. 2.00, 03/04, page 273 of 534
φ
TCNT
H'FF
H'00
Overflow signal
OVF
Figure 9.9 Timing of OVF Setting
9.6
Operation with Cascaded Connection
If bits CKS2 to CKS0 in either TCR_0 or TCR_1 are set to B'100, the 8-bit timers of the two channels are cascaded. With this configuration, a single 16-bit timer could be used (16-bit counter mode) or compare matches of the 8-bit channel 0 could be counted by the timer of channel 1 (compare match count mode). In this case, the timer operates as below. 9.6.1 16-Bit Counter Mode
When bits CKS2 to CKS0 in TCR_0 are set to B'100, the timer functions as a single 16-bit timer with channel 0 occupying the upper 8 bits and channel 1 occupying the lower 8 bits. 1 • • 2 • Setting of compare match flags The CMF flag in TCSR_0 is set to 1 when a 16-bit compare match event occurs. The CMF flag in TCSR_1 is set to 1 when a lower 8-bit compare match event occurs. Counter clear specification If the CCLR1 and CCLR0 bits in TCR_0 have been set for counter clear at compare match, the 16-bit counters (TCNT_0 and TCNT_1 together) are cleared when a 16-bit compare match event occurs. The 16-bit counters (TCNT0 and TCNT1 together) are cleared even if counter clear by the TMRI0 pin has also been set. The settings of the CCLR1 and CCLR0 bits in TCR_1 are ignored. The lower 8 bits cannot be cleared independently. Pin output Control of output from the TMO0 pin by bits OS3 to OS0 in TCSR_0 is in accordance with the 16-bit compare match conditions. Control of output from the TMO1 pin by bits OS3 to OS0 in TCSR_1 is in accordance with the lower 8-bit compare match conditions.
• 3 • •
Rev. 2.00, 03/04, page 274 of 534
9.6.2
Compare Match Count Mode
When bits CKS2 to CKS0 in TCR_1 are B'100, TCNT_1 counts compare match A's for channel 0. Channels 0 and 1 are controlled independently. Conditions such as setting of the CMF flag, generation of interrupts, output from the TMO pin, and counter clear are in accordance with the settings for each channel.
9.7
9.7.1
Interrupt Sources
Interrupt Sources
There are three 8-bit timer interrupt sources: CMIA, CMIB, and OVI. Their relative priorities are shown in table 9.3. Each interrupt source is set as enabled or disabled by the corresponding interrupt enable bit in TCR or TCSR, and independent interrupt requests are sent for each to the interrupt controller. Table 9.3
Name CMIA0 CMIB0 OVI0 CMIA1 CMIB1 OVI1
8-Bit Timer Interrupt Sources
Interrupt Source TCORA_0 compare match TCORB_0 compare match TCNT_0 overflow TCORA_1 compare match TCORB_1 compare match TCNT_1 overflow Interrupt Flag CMFA CMFB OVF CMFA CMFB OVF Low Low High Priority High
Rev. 2.00, 03/04, page 275 of 534
9.8
9.8.1
Usage Notes
Contention between TCNT Write and Clear
If a timer counter clock pulse is generated during the T2 state of a TCNT write cycle, the clear takes priority, so that the counter is cleared and the write is not performed. Figure 9.10 shows this operation.
TCNT write cycle by CPU T1 T2
φ
Address
TCNT address
Internal write signal
Counter clear signal
TCNT
N
H'00
Figure 9.10 Contention between TCNT Write and Clear
Rev. 2.00, 03/04, page 276 of 534
9.8.2
Contention between TCNT Write and Increment
If a timer counter clock pulse is generated during the T2 state of a TCNT write cycle, the write takes priority and the counter is not incremented. Figure 9.11 shows this operation.
TCNT write cycle by CPU T1 T2
φ
Address
TCNT address
Internal write signal
TCNT input clock
TCNT
N
M
Counter write data
Figure 9.11 Contention between TCNT Write and Increment
Rev. 2.00, 03/04, page 277 of 534
9.8.3
Contention between TCOR Write and Compare Match
During the T2 state of a TCOR write cycle, the TCOR write has priority and the compare match signal is inhibited even if a compare match event occurs as shown in figure 9.12. In TMR, an ICR imput capture conflicts with a compare match in the same way as with a write to TCOR. In this case also, imput capture has priority and the compare match signal is inhibited.
TCOR write cycle by CPU T1 T2
φ
Address
TCOR address
Internal write signal
TCNT
N
N+1
TCOR
N
M
TCOR write data
Compare match signal
Inhibited
Figure 9.12 Contention between TCOR Write and Compare Match
Rev. 2.00, 03/04, page 278 of 534
9.8.4
Contention between Compare Matches A and B
If compare match events A and B occur at the same time, the 8-bit timer operates in accordance with the priorities for the output statuses set for compare match A and compare match B, as shown in table 9.4. Table 9.4 Timer Output Priorities
Priority High
Output Setting Toggle output 1 output 0 output No change
Low
9.8.5
Switching of Internal Clocks and TCNT Operation
TCNT may increment erroneously when the internal clock is switched over. Table 9.5 shows the relationship between the timing at which the internal clock is switched (by writing to the CKS1 and CKS0 bits) and the TCNT operation. When the TCNT clock is generated from an internal clock, the falling edge of the internal clock pulse is detected. If clock switching causes a change from high to low level, as shown in case 3 in table 9.5, a TCNT clock pulse is generated on the assumption that the switchover is a falling edge. This increments TCNT. The erroneous incrementation can also happen when switching between internal and external clocks.
Rev. 2.00, 03/04, page 279 of 534
Table 9.5
Switching of Internal Clock and TCNT Operation
Timing of Switchover by Means of CKS1 and CKS0 Bits TCNT Clock Operation Switching from 1 low to low*
Clock before switchover Clock after switchover TCNT clock
No. 1
TCNT
N CKS bit write
N+1
2
Switching from low to high*2
Clock before switchover Clock after switchover TCNT clock
TCNT
N
N+1
N+2 CKS bit write
3
Switching from high to low*3
Clock before switchover Clock after switchover *4 TCNT clock
TCNT
N
N+1 CKS bit write
N+2
Rev. 2.00, 03/04, page 280 of 534
No. 4
Timing of Switchover by Means of CKS1 and CKS0 Bits TCNT Clock Operation Switching from high to high
Clock before switchover Clock after switchover TCNT clock
TCNT
N
N+1
N+2 CKS bit write
Notes: 1. 2. 3. 4.
Includes switching from low to stop, and from stop to low. Includes switching from stop to high. Includes switching from high to stop. Generated on the assumption that the switchover is a falling edge; TCNT is incremented.
9.8.6
Mode Setting with Cascaded Connection
If 16-bit counter mode and compare match count mode are specified at the same time, input clocks for TCNT_0 and TCNT_1 are not generated, and the counter stops. Do not specify 16-bit counter and compare match count modes simultaneously. 9.8.7 Interrupts in 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. Interrupts should therefore be disabled before entering module stop mode.
Rev. 2.00, 03/04, page 281 of 534
Rev. 2.00, 03/04, page 282 of 534
Section 10 Watchdog Timer (WDT)
This LSI incorporates an 8-bit watchdog timer with one channel (WDT). If a system crash prevents the CPU from writing to the timer counter, thus allowing it to overflow, the WDT can generate an internal reset signal or an internal NMI interrupt signal. When this watchdog function is not needed, the WDT can be used as an interval timer. In interval timer operation, an interval timer interrupt is generated each time the counter overflows. A block diagram of the WDT is shown in figure 10.1.
10.1
Features
• Selectable from eight counter input clocks. • Switchable between watchdog timer mode and interval timer mode Watchdog Timer Mode: • If the counter overflows, an internal reset or an internal NMI interrupt is generated.
Internal Timer Mode: • If the counter overflows, an internal timer interrupt (WOVI) is generated.
WOVI (Interrupt request signal) Internal NMI (Interrupt request signal) Internal reset signal
Interrupt control Reset control
Overflow
Clock
Clock selection
φ/2 φ/64 φ/128 φ/512 φ/2048 φ/8192 φ/32768 φ/131072 Internal clock
TCNT
TCSR
Module bus
Bus interface
WDT
Legend TCSR : Timer control/status register TCNT : Timer counter
Figure 10.1 Block Diagram of WDT
Rev. 2.00, 03/04, page 283 of 534
Internal bus
10.2
Register Descriptions
The WDT has the following registers. To prevent accidental overwriting, TCSR and TCNT have to be written to in a method different from normal registers. For details, see section 10.5.1, Notes on Register Access. • Timer counter (TCNT) • Timer control/status register (TCSR) 10.2.1 Timer Counter (TCNT)
TCNT is an 8-bit readable/writable up-counter. TCNT is initialized to H'00 when the TME bit in timer control/status register (TCSR) is cleared to 0. 10.2.2 Timer Control/Status Register (TCSR)
TCSR selects the clock source to be input to TCNT, and the timer mode.
Bit 7 Bit Name OVF Initial Value 0 R/W R/(W)*
1
Description Overflow Flag Indicates that TCNT has overflowed (changes from H'FF to H'00). [Setting condition] When TCNT overflows (changes from H'FF to H'00) When internal reset request generation is selected in watchdog timer mode, OVF is cleared automatically by the internal reset. [Clearing conditions] • • When TCSR is read when OVF = 1* , then 0 is written to OVF When 0 is written to TME
2
6
WT/IT
0
R/W
Timer Mode Select Selects whether the WDT is used as a watchdog timer or interval timer. 0: Interval timer mode 1: Watchdog timer mode
Rev. 2.00, 03/04, page 284 of 534
Bit 5
Bit Name TME
Initial Value 0
R/W R/W
Description Timer Enable When this bit is set to 1, TCNT starts counting. When this bit is cleared, TCNT stops counting and is initialized to H'00.
4 3
— RST/NMI
0 0
R/W R/W
Reserved The initial value should not be changed. Reset or NMI Selects to request an internal reset or an NMI interrupt when TCNT has overflowed. 0: An NMI interrupt is requested 1: An internal reset is requested
2 1 0
CKS2 CKS1 CKS0
0 0 0
R/W R/W R/W
Clock Select 2 to 0 Selects the clock source to be input to. The overflow frequency for φ = 33 MHz is enclosed in parentheses. 000: φ/2 (frequency: 15.5 µs) 001: φ/64 (frequency: 496.4 µs) 010: φ/128 (frequency: 992.9 µs) 011: φ/512 (frequency: 3.9 ms) 100: φ/2048 (frequency: 15.8 ms) 101: φ/8192 (frequency: 63.5 ms) 110: φ/32768 (frequency: 254.2 ms) 111: φ/131072 (frequency: 1.01 s)
Notes: 1. Only 0 can be written to clear the flag. 2. When the OVF flag is polled with the interval timer interrupt disabled, OVF = 1 must be read at least twice.
Rev. 2.00, 03/04, page 285 of 534
10.3
10.3.1
Operation
Watchdog Timer Mode
To use the WDT as a watchdog timer, set the WT/IT bit and the TME bit in TCSR to 1. While the WDT is used as a watchdog timer, if TCNT overflows without being rewritten because of a system malfunction or another error, an internal reset or NMI interrupt request is generated. TCNT does not overflow while the system is operating normally. Software must prevent TCNT overflows by rewriting the TCNT value (normally be writing H'00) before overflows occurs. If the RST/NMI bit of TCSR is set to 1, when the TCNT overflows, an internal reset signal for this LSI is issued for 518 system clocks as shown in figure 10.2. If the RST/NMI bit is cleared to 0, when the TCNT overflows, an NMI interrupt request is generated. An internal reset request from the watchdog timer and a reset input from the RES pin are processed in the same vector. Reset source can be identified by the XRST bit status in SYSCR. If a reset caused by a signal input to the RES pin occurs at the same time as a reset caused by a WDT overflow, the RES pin reset has priority and the XRST bit in SYSCR is set to 1. An NMI interrupt request from the watchdog timer and an interrupt request from the NMI pin are processed in the same vector. Do not handle an NMI interrupt request from the watchdog timer and an interrupt request from the NMI pin at the same time.
TCNT value
Overflow
H'FF
H'00
WT/IT = 1 TME = 1
Internal reset signal 518 System clocks WT/IT : Timer mode select bit TME : Timer enable bit OVF : Overflow flag
Note * After the OVF bit becomes 1, it is cleared to 0 by an internal reset. The XRST bit is also cleared to 0.
Time
Write H'00 to TCNT
OVF = 1*
WT/IT = 1 Write H'00 to TME = 1 TCNT
Figure 10.2 Watchdog Timer Mode (RST/NMI = 1) Operation
Rev. 2.00, 03/04, page 286 of 534
10.3.2
Interval Timer Mode
When the WDT is used as an interval timer, an interval timer interrupt (WOVI) is generated each time the TCNT overflows, as shown in figure 10.3. Therefore, an interrupt can be generated at intervals. When the TCNT overflows in interval timer mode, an interval timer interrupt (WOVI) is requested at the same time the OVF bit of TCSR is set to 1. The timing is shown figure 10.4.
TCNT value H'FF Overflow Overflow Overflow Overflow
H'00 WT/ = 0 TME = 1 WOVI WOVI WOVI WOVI
Time
WOVI : Internal timer interrupt request occurrence
Figure 10.3 Interval Timer Mode Operation
φ
TCNT
H'FF
H'00
Overflow signal (internal signal)
OVF
Figure 10.4 OVF Flag Set Timing
Rev. 2.00, 03/04, page 287 of 534
10.3.3
Watchdog Timer Overflow Flag (OVF) Timing
When TCNT overflows in watchdog timer mode, the OVF bit in TCSR is set to 1. When the RST/NMI bit is 1 here, the internal reset signal is generated for the entire LSI. The timing is shown in figure 10.5.
φ
TCNT
H'FF
H'00
Overflow signal (internal signal)
OVF
Internal reset signal
518 states
Figure 10.5 Output Timing of OVF
10.4
Interrupt Sources
During interval timer mode operation, an overflow generates an interval timer interrupt (WOVI). The interval timer interrupt is requested whenever the OVF flag is set to 1 in TCSR. OVF must be cleared to 0 in the interrupt handling routine. When the NMI interrupt request is selected in watchdog timer mode, an NMI interrupt request is generated by an overflow. Table 10.1 WDT Interrupt Source
Name WOVI Interrupt Source TCNT overflow Interrupt Flag OVF
Rev. 2.00, 03/04, page 288 of 534
10.5
10.5.1
Usage Notes
Notes on Register Access
The watchdog timer's registers, TCNT and TCSR differ from other registers in being more difficult to write to. The procedures for writing to and reading from these registers are given below. Writing to TCNT and TCSR: These registers must be written to by a word transfer instruction. They cannot be written to by a byte transfer instruction. TCNT and TCSR both have the same write address. Therefore, satisfy the relative condition shown in figure 10.6 to write to TCNT or TCSR. To write to TCNT, the higher bytes must contain the value H'5A and the lower bytes must contain the write data before the transfer instruction execution. To write to TCSR, the higher bytes must contain the value H'A5 and the lower bytes must contain the write data.
15 Address : H'FE70 0 H'5A 87 Write data 0
15 Address : H'FE70 0 H'A5 87 Write data 0
Figure 10.6 Writing to TCNT and TCSR Reading from TCNT and TCSR: These registers are read in the same way as other registers. The read address is H'FE70 for TCSR and H'FE71 for TCNT.
Rev. 2.00, 03/04, page 289 of 534
10.5.2
Conflict between Timer Counter (TCNT) Write and Increment
If a timer counter clock pulse is generated during the T2 state of a TCNT write cycle, the write takes priority and the timer counter is not incremented. Figure 10.7 shows this operation.
TCNT write cycle T1 T2
φ
Address
Internal write signal
TCNT input clock
TCNT
N
M
Counter write data
Figure 10.7 Conflict between TCNT Write and Increment 10.5.3 Changing Values of CKS2 to CKS0 Bits
If bits CKS2 to CKS0 in TCSR are written to while the WDT is operating, errors could occur in the incrementation. Software must stop the watchdog timer (by clearing the TME bit to 0) before changing the values of bits CKS2 to CKS0. 10.5.4 Switching between Watchdog Timer Mode and Interval Timer Mode
If the mode is switched from watchdog timer to interval timer, while the WDT is operating, errors could occur in the incrementation. Software must stop the watchdog timer (by clearing the TME bit to 0) before switching the mode.
Rev. 2.00, 03/04, page 290 of 534
Section 11 Serial Communication Interface for Boot Mode (SCI)
This LSI has a serial communication interface for boot mode (SCI) which is on-board programming mode of flash memory. The SCI can handle asynchronous serial communication. 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). Figure 11.1 shows a block diagram of the SCI.
11.1
Features
• Choice of asynchronous or clocked synchronous serial communication mode • Full-duplex communication capability The transmitter and receiver are mutually independent, enabling transmission and reception to be executed simultaneously. Double-buffering is used in both the transmitter and the receiver, enabling continuous transmission and continuous reception of serial data. • On-chip baud rate generator allows any bit rate to be selected • Choice of LSB-first • Four interrupt sources Four interrupt sources transmit-end, transmit-data-empty, receive-data-full, and receive error that can issue requests. • Module stop mode can be set Asynchronous mode • • • • • Data length: 7 or 8 bits Stop bit length: 1 or 2 bits Parity: Even, odd, or none Receive error detection: Parity, overrun, and framing errors Break detection: Break can be detected by reading the RxD pin level directly in case of a framing error
Rev. 2.00, 03/04, page 291 of 534
Bus interface
Module data bus
Internal data bus
RDR
TDR
SSR SCR SMR Transmission/ reception control
BRR
φ
Baud rate generator
RxD TxD
RSR
TSR
φ/4 φ/16 φ/64
Parity generation Parity check
Clock
[Legend] RSR : Receive shift register RDR : Receive data register TSR : Transmit shift register TDR : Transmit data register SMR : Serial mode register SCR : Serial control register SSR : Serial status register BRR : Bit rate register
TEI TXI RXI ERI
Figure 11.1 Block Diagram of SCI
11.2
Input/Output Pins
Table 11.1 shows the pin configuration of the SCI. Table 11.1 Pin Configuration
Channel 0 Note: * Pin Name* RxD0 TxD0 I/O Input Output Function Channel 0 receive data input Channel 0 transmit data output
Pin names RxD and TxD are used in the text, omitting the channel designation.
Rev. 2.00, 03/04, page 292 of 534
11.3
Register Descriptions
The SCI has the following registers. For details on the module stop control register, see section 16.1.2, Module Stop Control Registers H and L (MSTPCRH, MSTPCRL). To read the state of the RxD pin, see section 8.10.3, Port A Register (PORTA). • • • • • • • • Receive shift register (RSR) Transmit shift register (TSR) Receive data register (RDR) Transmit data register (TDR) Serial mode register (SMR) Serial control register (SCR) Serial status register (SSR) Bit rate register (BRR) Receive Shift Register (RSR)
11.3.1
RSR is a shift register used to receive serial data that is input to the RxD pin and convert it into parallel data. When one byte of data has been received, it is transferred to RDR automatically. RSR cannot be directly accessed by the CPU. 11.3.2 Receive Data Register (RDR)
RDR is an 8-bit register that stores receive data. When the SCI has received one byte of serial data, it transfers the received serial data from RSR to RDR where it is stored. After this, RSR is receive-enabled. Since RSR and RDR function as a double buffer in this way, enables continuous receive operations to be performed. After confirming that the RDRF bit in SSR is set to 1, read RDR for only once. RDR cannot be written to by the CPU. 11.3.3 Transmit Data Register (TDR)
TDR is an 8-bit register that stores transmit data. When the SCI detects that TSR is empty, it transfers the transmit data written in TDR to TSR and starts transmission. The double-buffered structures of TDR and TSR enable continuous serial transmission. If the next transmit data has already been written to TDR during serial transmission, the SCI transfers the written data to TSR to continue transmission. Although TDR can be read or written to by the CPU at all times, to achieve reliable serial transmission, write transmit data to TDR for only once after confirming that the TDRE bit in SSR is set to 1.
Rev. 2.00, 03/04, page 293 of 534
11.3.4
Transmit Shift Register (TSR)
TSR is a shift register that transmits serial data. To perform serial data transmission, the SCI first transfers transmit data from TDR to TSR, then sends the data to the TxD pin starting. TSR cannot be directly accessed by the CPU. 11.3.5 Serial Mode Register (SMR)
SMR is used to set the SCI's serial transfer format and select the on-chip baud rate generator clock source.
Bit 7 Bit Name C/A Initial Value 0 R/W R/W Description Communication Mode 0: Asynchronous mode 1: Setting prohibited 6 CHR 0 R/W Character Length (enabled only in asynchronous mode) 0: Selects 8 bits as the data length. 1: Selects 7 bits as the data length. The MSB (bit 7) of TDR is not transmitted in transmission. 5 PE 0 R/W Parity Enable (enabled only in asynchronous mode) When this bit is set to 1, the parity bit is added to transmit data before transmission, and the parity bit is checked in reception. 4 O/E 0 R/W Parity Mode (enabled only when the PE bit is 1 in asynchronous mode) 0: Selects even parity. 1: Selects odd parity. 3 STOP 0 R/W Stop Bit Length (enabled only in asynchronous mode) Selects the stop bit length in transmission. 0: 1 stop bit 1: 2 stop bits In reception, only the first stop bit is checked regardless of the STOP bit setting. If the second stop bit is 0, it is treated as the start bit of the next transmit character. 2 0 R/W Reserved The initial value should not be changed.
Rev. 2.00, 03/04, page 294 of 534
Bit 1 0
Bit Name CKS1 CKS0
Initial Value 0 0
R/W R/W R/W
Description Clock Select 1 and 0 These bits select the clock source for the on-chip baud rate generator. 00: φ clock (n = 0) 01: φ/4 clock (n = 1) 10: φ/16 clock (n = 2) 11: φ/64 clock (n = 3) For the relation between the bit rate register setting and the baud rate, see section 11.3.8, Bit Rate Register (BRR). n is the decimal display of the value of n in BRR (see section 11.3.8, Bit Rate Register (BRR)).
11.3.6
Serial Control Register (SCR)
SCR performs enabling or disabling of SCI transfer operations and interrupt requests, and selection of the transfer/receive clock source. For details on interrupt requests, refer to section 11.5, Interrupt Sources.
Bit 7 Bit Name TIE Initial Value 0 R/W R/W Description Transmit Interrupt Enable When this bit is set to 1, TXI interrupt request is enabled. TXI interrupt request cancellation can be performed by reading 1 from the TDRE flag, then clearing it to 0, or clearing the TIE bit to 0. 6 RIE 0 R/W Receive Interrupt Enable When this bit is set to 1, RXI and ERI interrupt requests are enabled. RXI and ERI interrupt request cancellation can be performed by reading 1 from the RDRF flag, or the FER, PER, or ORER flag, then clearing the flag to 0, or by clearing the RIE bit to 0.
Rev. 2.00, 03/04, page 295 of 534
Bit 5
Bit Name TE
Initial Value 0
R/W R/W
Description Transmit Enable When this bit s set to 1, transmission is enabled. In this state, serial transmission is started when transmit data is written to TDR and the TDRE flag in SSR is cleared to 0. SMR setting must be performed to decide the transfer format before setting the TE bit to 1. The TDRE flag in SSR is fixed at 1 if transmission is disabled by clearing this bit to 0.
4
RE
0
R/W
Receive Enable When this bit is set to 1, reception is enabled. Serial reception is started in this state when a start bit is detected in asynchronous mode. SMR setting must be performed to decide the transfer format before setting the RE bit to 1. Clearing the RE bit to 0 does not affect the RDRF, FER, PER, and ORER flags, which retain their states.
3 2
TEIE
0 0
R/W R/W
Reserved The initial value should not be changed. Transmit End Interrupt Enable When this bit is set to 1, TEI interrupt request is enabled. TEI cancellation can be performed by reading 1 from the TDRE flag in SSR, then clearing it to 0 and clearing the TEND flag to 0, or by clearing the TEIE bit to 0.
1 0
CKE1 CKE0
0 0
R/W R/W
Clock Enable 1 and 0 Selects the clock source. Asynchronous mode 0X: On-chip baud rate generator 1X: Setting prohibited
Legend: X: Don't care
Rev. 2.00, 03/04, page 296 of 534
11.3.7
Serial Status Register (SSR)
SSR is a register containing status flags of the SCI. Flags TDRE, RDRF, ORER, PER, and FER can only be cleared.
Bit 7 Bit Name TDRE Initial Value 1 R/W Description
R/(W)* Transmit Data Register Empty Indicates whether TDR contains transmit data. [Setting conditions] • • When the TE bit in SCR is 0 When data is transferred from TDR to TSR, and data writing to TDR is enabled. When 0 is written to TDRE after reading TDRE = 1
[Clearing condition] • 6 RDRF 0 R/(W)* Receive Data Register Full Indicates that the received data is stored in RDR. [Setting condition] • When serial reception ends normally and receive data is transferred from RSR to RDR When 0 is written to RDRF after reading RDRF = 1
[Clearing condition] • The RDRF flag is not affected and retains its previous value when the RE bit in SCR is cleared to 0. Exercise care because if reception of the next data is completed while the RDRF flag is set to 1, an overrun error occurs and receive data will be lost.
Rev. 2.00, 03/04, page 297 of 534
Bit 5
Bit Name ORER
Initial Value 0
R/W
Description
R/(W)* Overrun Error Indicates that an overrun error occurred while receiving and the reception has ended abnormally. [Setting condition] • When the next serial reception is completed while RDRF = 1
The receive data prior to the overrun error is retained in RDR, and the data received subsequently is lost. Also, subsequent serial reception cannot be continued while the ORER flag is set to 1. [Clearing condition] • When 0 is written to ORER after reading ORER = 1 The ORER flag is not affected and retains its previous state when the RE bit in SCR is cleared to 0. 4 FER 0 R/(W)* Framing Error Indicates that a framing error occurred while receiving in asynchronous mode and the reception has ended abnormally. [Setting condition] • When the stop bit is 0 In 2-stop-bit mode, only the first stop bit is checked for a value of 0; the second stop bit is not checked. If a framing error occurs, the receive data is transferred to RDR but the RDRF flag is not set. Also, subsequent serial reception cannot be continued while the FER flag is set to 1. [Clearing condition] • When 0 is written to FER after reading FER = 1 The FER flag is not affected and retains its previous state when the RE bit in SCR is cleared to 0.
Rev. 2.00, 03/04, page 298 of 534
Bit 3
Bit Name PER
Initial Value 0
R/W
Description
R/(W)* Parity Error Indicates that a parity error occurred while receiving in asynchronous mode and the reception has ended abnormally. [Setting condition] • When a parity error is detected during reception If a parity error occurs, the receive data is transferred to RDR but the RDRF flag is not set. Also, subsequent serial reception cannot be continued while the PER flag is set to 1. [Clearing condition] • When 0 is written to PER after reading PER = 1 The PER flag is not affected and retains its previous state when the RE bit in SCR is cleared to 0.
2
TEND
1
R
Transmit End [Setting conditions] • • When the TE bit in SCR is 0 When TDRE = 1 at transmission of the last bit of a 1-byte serial transmit character When 0 is written to TDRE after reading TDRE = 1
[Clearing condition] • 1, 0 Note: * All 0 R/W Reserved The initial value should not be changed. Only 0 can be written to clear the flag.
Rev. 2.00, 03/04, page 299 of 534
11.3.8
Bit Rate Register (BRR)
BRR is an 8-bit register that adjusts the bit rate. As the SCI performs baud rate generator control independently for each channel, different bit rates can be set for each channel. Table 11.2 shows the relationships between the N setting in BRR and bit rate B for asynchronous mode. The initial value of BRR is H'FF, and it can be read or written to by the CPU at all times. Table 11.2 Relationships between N Setting in BRR and Bit Rate B
Mode Asynchronous Mode Bit Rate
B= φ 64 106 (N + 1) 2 2n−1
Error
Error (%) = { φ B 64 10 6 (N + 1) 2 2n−1 −1} 100
Note: B: Bit rate (bit/s) N: BRR setting for baud rate generator (0 ≤ N ≤ 255) φ: Operating frequency (MHz) n: Determined by the SMR settings shown in the following tables. SMR Setting CKS1 0 0 1 1 CKS0 0 1 0 1 n 0 1 2 3
Table 11.3 shows sample N settings in BRR in asynchronous mode. Table 11.4 shows the maximum bit rate for each frequency in asynchronous mode.
Rev. 2.00, 03/04, page 300 of 534
Table 11.3 BRR Settings for Various Bit Rates (Asynchronous Mode) (1)
Operating Frequency φ (MHz) 10 Bit Rate (bit/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 2 2 2 1 1 0 0 0 0 0 0 N 177 129 64 129 64 129 64 32 15 9 7 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
Operating Frequency φ (MHz) 14 Bit Rate (bit/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 2 2 2 1 1 0 0 0 0 0 N 248 181 90 181 90 181 90 45 22 13 Error (%) –0.17 0.16 0.16 0.16 0.16 0.16 0.16 –0.93 –0.93 0.00 n 3 2 2 1 1 0 0 0 0 0 0 14.7456 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 2 2 1 1 0 0 0 0 0 0 17.2032 N 75 223 111 223 111 223 111 55 27 16 13 Error (%) 0.48 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 1.20 0.00
Rev. 2.00, 03/04, page 301 of 534
Table 11.3 BRR Settings for Various Bit Rates (Asynchronous Mode) (2)
Operating Frequency φ (MHz) 18
Bit Rate (bit/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 79 233 116 233 116 233 116 58 28 17 14 Error (%) –0.12 0.16 0.16 0.16 0.16 0.16 0.16 –0.69 1.02 0.00 –2.34 n 3 2 2 1 1 0 0 0 0 0 0
19.6608
N 86 255 127 255 127 255 127 63 31 19 15 Error (%) 0.31 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 –1.70 0.00 n 3 3 2 2 1 1 0 0 0 0 0 N 88 64
20
Error (%) –0.25 0.16 0.16 0.16 0.16 0.16 0.16 0.16 –1.36 0.00 1.73 n 3 3 2 2 1 1 0 0 0 0 0 N 110 80 162 80 162 80 162 80 40 24 19
25
Error (%) –0.02 –0.47 0.15 –0.47 0.15 –0.47 0.15 –0.47 –0.76 0.00 1.73
129 64 129 64 129 64 32 19 15
Operating Frequency φ (MHz)
30 Bit Rate (bit/s) 110 150 300 600 1200 2400 4800 9600 19200 31250 38400 n 3 3 2 2 1 1 0 0 0 0 0 N 132 97 194 97 194 97 194 97 48 29 23 Error (%) 0.13 –0.35 0.16 –0.35 0.16 –0.35 0.16 –0.35 –0.35 0 1.73 n 3 3 2 2 1 1 0 0 0 0 0 N 145 106 214 106 214 106 214 106 53 32 26 33 Error (%) 0.33 0.39 –0.07 0.39 –0.07 0.39 –0.07 0.39 –0.54 0 –0.54
Rev. 2.00, 03/04, page 302 of 534
Table 11.4 Maximum Bit Rate for Each Frequency (Asynchronous Mode)
φ (MHz) 10 12 12.288 14 14.7456 16 17.2032 18 19.6608 20 25 30 33 Maximum Bit Rate (bit/s) 312500 375000 384000 437500 460800 500000 537600 562500 614400 625000 781250 937500 1031250 n 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
Rev. 2.00, 03/04, page 303 of 534
11.4
Operation in Asynchronous Mode
Figure 11.2 shows the general format for asynchronous serial communication. One frame consists of a start bit (low level), followed by transfer data, a parity bit, and finally stop bits (high level). In asynchronous serial communication, the transmission line is usually held in the mark state (high level). The SCI monitors the transmission line, and when it goes to the space state (low level), recognizes a start bit and starts serial communication. In asynchronous serial communication, the communication line is usually held in the mark state (high level). The SCI monitors the communication line, and when it goes to the space state (low level), recognizes a start bit and starts serial communication. Inside the SCI, the transmitter and receiver are independent units, enabling full-duplex communication. Both the transmitter and the receiver also have a doublebuffered structure, so that data can be read or written during transmission or reception, enabling continuous data transfer.
Idle state (mark state)
1
Serial data
LSB 0 Start bit
1 bit
MSB
D1 D2 D3 D4 D5 D6 D7 0/1 1 1
1
D0
Transmit/receive data
7 or 8 bits
Parity Stop bit(s) bit 1 bit, or none 1 or 2 bits
One unit of transfer data (character or frame)
Figure 11.2 Data Format in Asynchronous Communication (Example with 8-Bit Data, Parity, Two Stop Bits)
Rev. 2.00, 03/04, page 304 of 534
11.4.1
Data Transfer Format
Table 11.5 shows the data transfer formats that can be used in asynchronous mode. Any of eight transfer formats can be selected according to the SMR setting. Table 11.5 Serial Transfer Formats (Asynchronous Mode)
SMR Settings CHR 0 0 0 0 1 1 1 1 PE 0 0 1 1 0 0 1 1 STOP 0 1 0 1 0 1 0 1 1
S
Serial Transfer Format and Frame Length 2 3 4 5 6 7 8 9 10
STOP
11
12
8-bit data 8-bit data 8-bit data 8-bit data 7-bit data 7-bit data 7-bit data 7-bit data
STOP
S
STOP STOP
S
P STOP
S
P STOP STOP
S
S
STOP STOP
S
P
STOP
S
P
STOP STOP
[Legend] S: Start bit STOP: Stop bit P: Parity bit
Rev. 2.00, 03/04, page 305 of 534
11.4.2
Receive Data Sampling Timing and Reception Margin in Asynchronous Mode
In asynchronous mode, the SCI operates on a basic clock with a frequency of 16 times the bit rate. In reception, the SCI samples the falling edge of the start bit using the basic clock, and performs internal synchronization. Receive data is latched at the middle of each bit by sampling the data at the rising edge of the 8th pulse of the basic clock as shown in figure 11.3. Thus the reception margin in asynchronous mode is given by formula (1) below.
M = { (0.5 – 1 D – 0.5 ) – (L – 0.5) F – 2N N (1 + F) } 100 [%]
... Formula (1)
Where M: Reception Margin N: Ratio of bit rate to clock (N = 16) D: Clock duty cycle (D = 0.5 to 1.0) L: Frame length (L = 9 to 12) F: Absolute value of clock rate deviation Assuming values of F = 0 and D = 0.5 in formula (1), a reception margin is given by formula below. M = {0.5 – 1/(2 × 16)} × 100 [%] = 46.875% However, this is only the computed value, and a margin of 20% to 30% should be allowed in system design.
16 clocks 8 clocks 0 Internal base clock 7 15 0 7 15 0
Receive data (RxD) Synchronization sampling timing
Start bit
D0
D1
Data sampling timing
Figure 11.3 Receive Data Sampling Timing in Asynchronous Mode
Rev. 2.00, 03/04, page 306 of 534
11.4.3
Clock
An internal clock generated by the on-chip baud rate generator can be selected as the SCI’s serial clock, according to the setting of the C/A bit in SMR and the CKE1 and CKE0 bits in SCR. 11.4.4 SCI Initialization (Asynchronous Mode)
Before transmitting and receiving data, you should first clear the TE and RE bits in SCR to 0, then initialize the SCI as shown in figure 11.4. When the operating mode, transfer format, etc., is changed, the TE and RE bits must be cleared to 0 before making the change. When the TE bit is cleared to 0, the TDRE flag is set to 1. Note that clearing the RE bit to 0 does not initialize the contents of the RDRF, PER, FER, and ORER flags, or the contents of RDR.
Start of initialization
Clear TE and RE bits in SCR to 0
[1] Set the clock selection in SCR. Be sure to clear bits RIE, TIE, and TEIE, and bits TE and RE, to 0. When the clock is selected in asynchronous mode, it is output immediately after SCR settings are made. [2] Set the data transfer format in SMR. [3] Write a value corresponding to the bit rate to BRR. (Not necessary if an external clock is used.) [4] Wait at least one bit interval, then set the TE bit or RE bit in SCR to 1. Also set the RIE, TIE, and TEIE bits. Setting the TE and RE bits enables the TxD and RxD pins to be used.
[4]
Set CKE1 and CKE0 bits in SCR (TE, RE bits = 0)
[1]
Set data transfer format in SMR
[2] [3]
Set value in BRR Wait
No 1-bit interval elapsed? Yes Set TE and RE bits in SCR to 1, and set RIE, TIE, and TEIE bits
Figure 11.4 Sample SCI Initialization Flowchart
Rev. 2.00, 03/04, page 307 of 534
11.4.5
Data Transmission (Asynchronous Mode)
Figure 11.5 shows an example of the operation for transmission in asynchronous mode. In transmission, the SCI operates as described below. 1. The SCI monitors the TDRE flag in SSR, and if is cleared to 0, recognizes that data has been written to TDR, and transfers the data from TDR to TSR. 2. After transferring data from TDR to TSR, the SCI sets the TDRE flag to 1 and starts transmission. If the TIE bit is set to 1 at this time, a transmit data empty interrupt request (TXI) is generated. Because the TXI interrupt routine writes the next transmit data to TDR before transmission of the current transmit data has finished, continuous transmission can be enabled. 3. Data is sent from the TxD pin in the following order: start bit, transmit data, parity bit (may be omitted depending on the format), and stop bit. 4. The SCI checks the TDRE flag at the timing for sending the stop bit. 5. If the TDRE flag is 0, the data is transferred from TDR to TSR, the stop bit is sent, and then serial transmission of the next frame is started. 6. If the TDRE flag is 1, the TEND flag in SSR is set to 1, the stop bit is sent, and then the "mark state" is entered in which 1 is output. If the TEIE bit in SCR is set to 1 at this time, a TEI interrupt request is generated. Figure 11.6 shows a sample flowchart for transmission in asynchronous mode.
1
Start bit
Data
Parity Stop Start bit bit bit
Data
Parity Stop bit bit
0
D0
D1
D7
0/1
1
0
D0
D1
D7
0/1
1
1 Idle state (mark state)
TDRE
TEND
TXI interrupt Data written to TDR and TXI interrupt request generated TDRE flag cleared to 0 in request generated TXI interrupt handling routine
TEI interrupt request generated
1 frame
Figure 11.5 Example of Operation in Transmission in Asynchronous Mode (Example with 8-Bit Data, Parity, One Stop Bit)
Rev. 2.00, 03/04, page 308 of 534
Initialization Start of transmission
[1]
Read TDRE flag in SSR
[2]
[1] SCI initialization: The TxD pin is automatically designated as the transmit data output pin. After the TE bit is set to 1, a frame of 1s is output, and transmission is enabled. [2] SCI status check and transmit data write: Read SSR and check that the TDRE flag is set to 1, then write transmit data to TDR and clear the TDRE flag to 0. [3] Serial transmission continuation procedure: To continue serial transmission, read 1 from the TDRE flag to confirm that writing is possible, then write data to TDR, and then clear the TDRE flag to 0.
No TDRE = 1? Yes Write transmit data to TDR and clear TDRE flag in SSR to 0
No All data transmitted? Yes [3] Read TEND flag in SSR
No TEND = 1? Yes Clear TE bit in SCR to 0
Figure 11.6 Sample Serial Transmission Flowchart
Rev. 2.00, 03/04, page 309 of 534
11.4.6
Serial Data Reception (Asynchronous Mode)
Figure 11.7 shows an example of the operation for reception in asynchronous mode. In serial reception, the SCI operates as described below. 1. The SCI monitors the communication line, and if a start bit is detected, performs internal synchronization, receives receive data in RSR, and checks the parity bit and stop bit. 2. If an overrun error (when reception of the next data is completed while the RDRF flag is still set to 1) occurs, the ORER bit in SSR is set to 1. If the RIE bit in SCR is set to 1 at this time, an ERI interrupt request is generated. Receive data is not transferred to RDR. The RDRF flag remains to be set to 1. 3. If a parity error is detected, the PER bit in SSR is set to 1 and receive data is transferred to RDR. If the RIE bit in SCR is set to 1 at this time, an ERI interrupt request is generated. 4. If a framing error (when the stop bit is 0) is detected, the FER bit in SSR is set to 1 and receive data is transferred to RDR. If the RIE bit in SCR is set to 1 at this time, an ERI interrupt request is generated. 5. If reception finishes successfully, the RDRF bit in SSR is set to 1, and receive data is transferred to RDR. If the RIE bit in SCR is set to 1 at this time, an RXI interrupt request is generated. Because the RXI interrupt routine reads the receive data transferred to RDR before reception of the next receive data has finished, continuous reception can be enabled.
1
Start bit
Data
Parity Stop Start bit bit bit
Data
Parity Stop bit bit
1
Idle state (mark state)
0
D0
D1
D7
0/1
1
0
D0
D1
D7
0/1
0
RDRF
FER
RXI interrupt request generated
RDR data read and RDRF flag cleared to 0 in RXI interrupt handling routine
ERI interrupt request generated by framing error
1 frame
Figure 11.7 Example of SCI Operation in Reception (Example with 8-Bit Data, Parity, One Stop Bit)
Rev. 2.00, 03/04, page 310 of 534
Table 11.6 shows the states of the SSR status flags and receive data handling when a receive error is detected. If a receive error is detected, the RDRF flag retains its state before receiving data. Reception cannot be resumed while a receive error flag is set to 1. Accordingly, clear the ORER, FER, PER, and RDRF bits to 0 before resuming reception. Figure 11.8 shows a sample flowchart for serial data reception. Table 11.6 SSR Status Flags and Receive Data Handling
SSR Status Flag RDRF* 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 Lost Transferred to RDR Transferred to RDR Lost Lost Transferred to RDR Lost Receive Error Type Overrun error Framing error Parity error Overrun error + framing error Overrun error + parity error Framing error + parity error Overrun error + framing error + parity error
Note: The RDRF flag retains its state before data reception.
Rev. 2.00, 03/04, page 311 of 534
Initialization Start of reception
[1]
[1] SCI initialization: The RxD pin is automatically designated as the receive data input pin. [2] [3] Receive error handling: If a receive error occurs, read the ORER, PER, and FER flags in SSR to identify the error. After performing the appropriate error processing, ensure that the ORER, PER, and FER flags are all cleared to 0. Reception cannot be resumed if any of these flags are set to 1. data read : Read SSR and check that RDRF = 1, then read the receive data in RDR and clear the RDRF flag to 0. Transition of the RDRF flag from 0 to 1 can also be identified by an RXI interrupt. [5] Serial reception continuation procedure: To continue serial reception, before the stop bit for the current frame is received, read the RDRF flag, read RDR, and clear the RDRF flag to 0.
Read ORER, PER, and FER flags in SSR
[2]
PER ∨ FER ∨ ORER = 1? No
Yes [3] Error handling
(Continued on next page) [4] SCI status check and receive Read RDRF flag in SSR [4]
No RDRF = 1? Yes Read receive data in RDR, and clear RDRF flag in SSR to 0
No All data received? Yes Clear RE bit in SCR to 0 [5]
Figure 11.8 Sample Serial Reception Data Flowchart (1)
Rev. 2.00, 03/04, page 312 of 534
[3] Error handling
No ORER = 1? Yes Overrun error handling
No FER = 1? Yes Framing error handling
No PER = 1? Yes Parity error handling
Clear ORER, PER, and FER flags in SSR to 0
Figure 11.8 Sample Serial Reception Data Flowchart (2)
Rev. 2.00, 03/04, page 313 of 534
11.5
11.5.1
Interrupt Sources
Interrupts in Normal Serial Communication Interface Mode
Table 11.7 shows the interrupt sources in normal serial communication interface mode. A different interrupt vector is assigned to each interrupt source, and individual interrupt sources can be enabled or disabled using the enable bits in SCR. When the TDRE flag in SSR is set to 1, a TXI interrupt request is generated. When the TEND flag in SSR is set to 1, a TEI interrupt request is generated. When the RDRF flag in SSR is set to 1, an RXI interrupt request is generated. When the ORER, PER, or FER flag in SSR is set to 1, an ERI interrupt request is generated. A TEI interrupt is generated when the TEND flag is set to 1 while the TEIE bit is set to 1. If a TEI interrupt and a TXI interrupt are generated simultaneously, the TXI interrupt has priority for acceptance. However, note that if the TDRE and TEND flags are cleared simultaneously by the TXI interrupt routine, the SCI cannot branch to the TEI interrupt routine later. Table 11.7 SCI Interrupt Sources
Channel 0 Name ERI0 RXI0 TXI0 TEI0 Interrupt Source Receive Error Receive Data Full Transmit Data Empty Transmission End Interrupt Flag ORER, FER, PER RDRF TDRE TEND Low Priority High
Rev. 2.00, 03/04, page 314 of 534
11.6
11.6.1
Usage Notes
Module Stop Mode Setting
SCI operation can be disabled or enabled using the module stop control register. The initial setting is for SCI operation to be halted. Register access is enabled by clearing module stop mode. For details, refer to section 16, Power-Down Modes. 11.6.2 Relation between Writes to TDR and the TDRE Flag
The TDRE flag in SSR is a status flag that indicates that transmit data has been transferred from TDR to TSR. When the SCI transfers data from TDR to TSR, the TDRE flag is set to 1. Data can be written to TDR regardless of the state of the TDRE flag. However, if new data is written to TDR when the TDRE flag is cleared to 0, the data stored in TDR will be lost since it has not yet been transferred to TSR. It is therefore essential to check that the TDRE flag is set to 1 before writing transmit data to TDR. 11.6.3 Operation in Case of Mode Transition
• Transmission Operation should be stopped (by clearing TE, TIE, and TEIE to 0) before making a module stop mode or software standby mode transition. TSR, TDR, and SSR are reset. The output pin states in module stop mode or software standby mode depend on the port settings, and become high-level output after the relevant mode is cleared. If a transition is made during transmission, the data being transmitted will be undefined. When transmitting without changing the transmit mode after the relevant mode is cleared, transmission can be started by setting TE to 1 again, and performing the following sequence: SSR read → TDR write → TDRE clearance. To transmit with a different transmit mode after clearing the relevant mode, the procedure must be started again from initialization. Figure 11.9 shows a sample flowchart for mode transition during transmission. • Reception Receive operation should be stopped (by clearing RE to 0) before making a module stop mode or software standby mode transition. RSR, RDR, and SSR are reset. If a transition is made during reception, the data being received will be invalid. To continue receiving without changing the reception mode after the relevant mode is cleared, set RE to 1 before starting reception. To receive with a different receive mode, the procedure must be started again from initialization. Figure 11.10 shows a sample flowchart for mode transition during reception.
Rev. 2.00, 03/04, page 315 of 534
All data transmitted? Yes
No
[1]
Read TEND flag in SSR
No
[1] Data being transmitted is interrupted. After exiting software standby mode, normal CPU transmission is possible by setting TE to 1, reading SSR, writing TDR, and clearing TDRE to 0. [2] If TIE and TEIE are set to 1, clear them to 0 in the same way. [3] Includes module stop mode.
TEND = 1 Yes
TE = 0
[2]
Transition to software standby mode Exit from software standby mode Change operating mode?
Yes
Initialization
[3]
No
TE = 1
Figure 11.9 Sample Flowchart for Mode Transition during Transmission
Rev. 2.00, 03/04, page 316 of 534
Read RDRF flag in SSR No [1] [1] Receive data being received becomes invalid.
RDRF = 1 Yes Read receive data in RDR
RE = 0
Transition to software standby mode Exit from software standby mode Change operating mode? Yes Initialization
[2]
[2] Includes module stop mode.
No
RE = 1
Figure 11.10 Sample Flowchart for Mode Transition during Reception
Rev. 2.00, 03/04, page 317 of 534
Rev. 2.00, 03/04, page 318 of 534
Section 12 Universal Serial Bus 2 (USB2)
This LSI incorporates a USB2 function module supporting the USB standard. Figure 12.1 shows the block diagram of the USB2.
12.1
Features
• Supports the USB version 2.0 USB standard requests are processed automatically (except for some requests) Get Descriptor, Class, and Vendor requests are processed by firmware • High-speed mode and full-speed mode are supported • Supports four endpoints; EP0, EP1, EP2, and EP3
Max. Packet Size Endpoint EP0s EP0i EP0o EP1 EP2 EP3 Full Speed 8 bytes 64 bytes 64 bytes 64 bytes 64 bytes 64 bytes High Speed 8 bytes 64 bytes 64 bytes 512 bytes 512 bytes 64 bytes FIFO Configuration Single Single Single Dual Dual Single Transfer Method Setup Control Control Bulk Bulk Interrupt Transfer Direction Out In Out Out In In DMA Transfer Possible Possible
• Control, Bulk, and Interrupt transfers are supported • The maximum packet size in high-speed mode and full-speed mode is switched automatically • DMA transfer interface DMA transfer is enabled for endpoints 1 and 2 • Interrupt interface Two interrupt requests (USBI0 and USBI1) are supported as the interrupt request output pins. Each interrupt source can be assigned via the internal registers
Rev. 2.00, 03/04, page 319 of 534
Peripheral bus
USB module
External transceiver
D+
Status and control register Interrupt request DMA transfer request Protocol processor
USCLK (30 MHz)
UTMI
D-
FIFO
Figure 12.1 Block Diagram of USB2
Rev. 2.00, 03/04, page 320 of 534
12.2
Input/Output Signals
Table 12.1 lists the I/O signals of USB2. Table 12.1 Input/Output Signals
Classification Symbol USB bus power USVBUS supply I/O Input Function USB Bus Power Supply Signal This is a connection or disconnection detection pin for the USB cable. This pin is connected to the VBUS pin in the USB connector. High: VBUS pin = low means disconnection Low: VBUS pin = high means connection Note: This signal should be input after the signal of the VBUS pin of the USB connector is inverted. Transceiver signal DrVCC USCLK Input USB Clock This is a USB clock (30 MHz) which is output by the transceiver. USRXV USRXERR USRXACT USTXRDY USLSTA[1:0] USD[15:0] USWDVLD I/O USB 2.0 Transceiver I/O Signal These signals are connected to the USB 2.0 transceiver. They are complied with the UTMI specification. For details, refer to the UTMI Specifications. Output USB 2.0 Transceiver Output Signal These signals are connected to the USB 2.0 transceiver. They are complied with the UTMI specification. For details, refer to the UTMI specification. Input USB 2.0 Transceiver Input Signal These signals are connected to the USB 2.0 transceiver. They are complied with the UTMI specification. For details, refer to the UTMI Specifications.
USTSEL USOPM[1:0] USXCVRS USTXV USSUSP Monitor pin USRST
Output
This is a monitor pin.
Rev. 2.00, 03/04, page 321 of 534
12.3
Register Descriptions
The USB2 has the following registers. • • • • • • • • • • • • • • • • • • • • • Interrupt flag register 0 (IFR0) Interrupt select register 0 (ISR0) Interrupt enable register 0 (IER0) EP0o receive data size register (EPSZ0o) EP1 receive data size register (EPSZ1) EP0i data register (EPDR0i) EP0o data register (EPDR0o) EP0s data register (EPDR0s) EP1 data register (EPDR1) EP2 data register (EPDR2) EP3 data register (EPDR3) Data status register 0 (DASTS0) Packet enable register 0i (PKTE0i) Packet enable register 2 (PKTE2) Packet enable register 3 (PKTE3) FIFO clear register 0 (FCLR0) Endpoint stall register 0 (EPSTL0) DMA set register 0 (DMA0) Control register (CTRL) Port function control register 3 (PFCR3) USB suspend status register (USBSUSP)
Rev. 2.00, 03/04, page 322 of 534
12.3.1
Interrupt Flag Register 0 (IFR0)
IFR0 indicates the setup request reception, EP0i, EP0o, EP1, EP2, and EP3 transmission/reception, and bus reset state and monitors a VBUS interrupt flag and USB mode interrupt flag. If the corresponding flag is set to 1, the corresponding interrupt request is output. A flag in this register can be cleared by writing 0 to it. Writing 1 to a flag is invalid and causes no operation. Note that the EP1FULL and EP2EMPTY bits are status bits indicating the FIFO states of the EP1 and EP2. Therefore these bits cannot be cleared. The VBUS MN and MODE MN bits are also status bits so they cannot be cleared.
Bit 31 to 27 26 Bit Name Initial Value All 0 R/W R R Description Reserved The write value should always be 0. MODE MN1 0 USB Mode Status 1 This bit is a status bit which indicates the USB transfer mode. This bit is used as two bits with the MODE MN0 bit. 0: At a reset or when the cable is disconnected 1: Full-speed mode (12 Mbps) 2: High-speed mode (480 Mbps) 3: Chirp mode Refer to section 12.8.12, USB Bus Idle in High-Speed Mode. This bit cannot be cleared because this bit is a status bit. 25 MODE MN0 0 R USB Mode Status 0 This bit is a status bit which indicates the USB transfer mode. This bit is used as two bits with the MODE MN1 bit. This bit cannot be cleared because this bit is a status bit.
Rev. 2.00, 03/04, page 323 of 534
Bit 24
Bit Name MODE F
Initial Value 0
R/W R/W
Description USB Transfer Mode Change Detection [Setting condition] This bit is set to 1 when the USB mode status bits are changed. [Clearing conditions] • • At a reset When 0 is written to this bit
23 to 18 17
0
R R
Reserved The write value should always be 0. USB Connection Status This bit is a status bit which monitors the state of the USVBUS pin. This bit reflects the state of the USVBUS pin. 1: The USVBUS pin is connected. 0: The USVBUS pin is not connected.
VBUS MN 0
16
VBUS F
0
R/W
USB Connection/disconnection Detection [Setting condition] This bit is set to 1 when the function is connected/disconnected to/from the USB bus. [Clearing conditions] • • At a reset When 0 is written to this bit
15 to 10 9
EP3TR
All 0 0
R R/W
Reserved The write value should always be 0. EP3 Transfer Request [Setting condition] This bit is set to 1 if there is no valid data in the FIFO when an IN token is sent from the host to EP3. [Clearing conditions] • • At a reset When 0 is written to this bit
Rev. 2.00, 03/04, page 324 of 534
Bit 8
Bit Name EP3TS
Initial Value 0
R/W R/W
Description EP3 Transmit Complete [Setting condition] This bit is set to 1 if the data written in EP3 is transmitted to the host normally and the ACK handshake is returned. [Clearing conditions] • • At a reset When 0 is written to this bit
7
BRST
0
R/W
Bus Reset [Setting condition] This bit is set to 1 when the bus reset signal is detected on the USB bus. [Clearing conditions] • • At a reset When 0 is written to this bit
6
EP2TR
0
R/W
EP2 Transfer Request [Setting condition] This bit is set to 1 if there is no valid data in both FIFOs when an IN token is sent from the host to EP2. [Clearing conditions] • • At a reset When 0 is written to this bit
5
EP2EMPTY 0
R
EP2 FIFO Empty*2 [Setting conditions] • At a reset EP2 has a dual FIFO configuration. This bit is set to 1 if there is no valid data at least in the single FIFO. If data is full in both FIFOs, this bit is set to 0. [Clearing condition] This bit cannot be cleared because this bit is a status bit.
Rev. 2.00, 03/04, page 325 of 534
Bit 4
Bit Name EP1FULL
Initial Value 0
R/W R
Description EP1 FIFO Full*1 [Setting condition] EP1 has a dual FIFO configuration. This bit is set to 1 if data is full at least in the single FIFO. If there is no valid data in both FIFOs, this bit is set to 0. [Clearing condition] This bit cannot be cleared because this bit is a status bit.
3
SETUPTS
0
R/W
Setup Request Receive Complete [Setting condition] This bit is set to 1 if EP0s normally receives 8-byte data to be decoded by the function from the host and returns the ACK handshake to the host. [Clearing conditions] • • At a reset When 0 is written to this bit
2
EP0oTS
0
R/W
EP0o Receive Complete [Setting condition] This bit is set to 1 if EP0o receives data from the host normally and returns the NYET or ACK handshake to the host. [Clearing conditions] • • At a reset When 0 is written to this bit
1
EP0iTR
0
R/W
EP0i Transfer Request [Setting condition] This bit is set to 1 if there is no valid data in the FIFO when an IN token is sent from the host to EP0i [Clearing conditions] • • At a reset When 0 is written to this bit
Rev. 2.00, 03/04, page 326 of 534
Bit 0
Bit Name EP0iTS
Initial Value 0
R/W R/W
Description EP0i Transmit Complete [Setting condition] This bit is set to 1 if the data written in EP0i is transmitted to the host normally and the ACK handshake is returned. [Clearing conditions] • • At a reset When 0 is written to this bit
Notes: 1. FIFO Full In case of IN FIFO: In case of OUT FIFO: 2. FIFO Empty In case of IN FIFO: In case of OUT FIFO:
The data which can be transmitted is in the FIFO. The data which is valid is in the FIFO. The data which can be transmitted is not in the FIFO. The data which is valid is not in the FIFO.
Rev. 2.00, 03/04, page 327 of 534
12.3.2
Interrupt Select Register 0 (ISR0)
ISR0 sets interrupt requests indicated in the interrupt flag register. When the corresponding bit is cleared to 0, the USBI0 interrupt request is output. When the corresponding bit is set to 1, the USBI1 interrupt request is output. In the initial value, each interrupt source in the interrupt flag register is requested from USBI0.
Bit 31 to 25 24 23 to 17 16 15 to 10 9 8 7 6 5 4 3 2 1 0 Bit Name MODE F VBUS F EP3TR EP3TS BRST EP2TR Initial Value All 0 0 All 0 0 All 0 0 0 0 0 R/W R R/W R R/W R R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Reserved The write value should always be 0. Selects the MODE F interrupt. Reserved The write value should always be 0. Selects the VBUS F interrupt. Reserved The write value should always be 0. Selects the EP3TR interrupt. Selects the EP3TS interrupt. Selects the BRST interrupt. Selects the EP2TR interrupt. Selects the EP2EMPTY interrupt. Selects the EP1FULL interrupt Selects the SETUPTS interrupt. Selects the EP0oTS interrupt. Selects the EP0iTR interrupt. Selects the EP0iTS interrupt.
EP2EMPTY 0 EP1FULL SETUPTS EP0oTS EP0iTR EP0iTS 0 0 0 0 0
Rev. 2.00, 03/04, page 328 of 534
12.3.3
Interrupt Enable Register 0 (IER0)
IER0 enables the interrupt request indicated in the interrupt flag register. When an interrupt flag is set while the corresponding bit in IER0 is set to 1, an interrupt request selected by the interrupt select register is asserted.
Bit 31 to 25 24 23 to 17 16 15 to 10 9 8 7 6 5 4 3 2 1 0 Bit Name MODE F VBUS F EP3TR EP3TS BRST EP2TR Initial Value All 0 0 All 0 0 All 0 0 0 0 0 R/W R R/W R R/W R R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Reserved The write value should always be 0. Enables the MODE F interrupt. Reserved The write value should always be 0. Enables the VBUS F interrupt. Reserved The write value should always be 0. Enables the EP3TR interrupt. Enables the EP3TS interrupt. Enables the BRST interrupt. Enables the EP2TR interrupt. Enables the EP2EMPTY interrupt. Enables the EP1FULL interrupt Enables the SETUPTS interrupt. Enables the EP0oTS interrupt. Enables the EP0iTR interrupt. Enables the EP0iTS interrupt.
EP2EMPTY 0 EP1FULL SETUPTS EP0oTS EP0iTR EP0iTS 0 0 0 0 0
12.3.4
EP0o Receive Data Size Register (EPSZ0o)
EPSZ0o is a receive data size register for endpoint 0o. EPSZ0o indicates the number of bytes of data to be received from the host.
Bit 31 to 0 Bit Name D31 to D0 Initial Value — R/W R Description EP0o Receive Data Size
Rev. 2.00, 03/04, page 329 of 534
12.3.5
EP1 Receive Data Size Register (EPSZ1)
EPSZ1 is a receive data size register for endpoint 1. EPSZ1 indicates the number of bytes of data to be received from the host. The FIFO for endpoint 1 has a dual-FIFO configuration. The data size indicated by this register refers to the currently selected FIFO.
Bit 31 to 0 Bit Name D31 to D0 Initial Value — R/W R Description EP1 Receive Data Size
12.3.6
EP0i Data Register (EPDR0i)
EPDR0i is a 64-byte transmit FIFO buffer for endpoint 0. EPDR0i stores number of packets of transmit data for control-in. If one packet of data is written and number of transmit data is written in the packet enable register 0i (PKTE0i), transmit data is valid. If data is transmitted and then the ACK handshake is returned from the host, the EP0iTS bit in IFR0 is set. EPDR0i can be initialized by setting the EP0iCLR bit in the FIFO clear register 0. When the setup is received, EPDR0i is cleared. After the setup data is received, transmission is impossible until the SETUP TS bit is cleared.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W W Description 64-Byte Transmit FIFO Buffer for EP0
12.3.7
EP0o Data Register (EPDR0o)
EPDR0o is a 64-byte receive FIFO buffer for endpoint 0 and has a single FIFO buffer. When reception is completed, the USB returns the NYET handshake (high-speed mode) or ACK handshake (full-speed mode) to the host. EPDR0o stores receive data for endpoint 0 except for the setup request. When data is received normally, the EP0oTS bit in IFR0 is set and the number of receive bytes is indicated in the EP0o receive data size register. After the setup data is received, reception is impossible until the SETUP TS bit is cleared. Though the 0-length packet can be received, the ACK handshake (both high-speed and full-speed modes) is returned to the host and data is ignored. However, the EP0oTS flag in IFR0 is set.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W R Description 64-Byte Receive FIFO Buffer for EP0
Rev. 2.00, 03/04, page 330 of 534
12.3.8
EP0s Data Register (EPDR0s)
EPDR0s is a data register only for the setup request for endpoint 0. EPDR0s stores 8-byte request data sent from the host in setup stage. Note that only request data to be processed by the microcomputer is received. When a request processed by the USB automatically is received, data is not stored. When data reception is started in the next setup stage during reading, data is overwritten unconditionally.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W R Description Data Register only for EP0 Setup Request
12.3.9
EP1 Data Register (EPDR1)
EPDR1 consists of two 512-byte receive FIFO buffers for endpoint 1. The size of EPDR1 is as twice as the maximum packet size in high-speed mode and has a dual-FIFO configuration. When there is no data in the single FIFO buffer, the USB returns the ACK handshake (both high-speed and full-speed modes) to the host. When reception is completed and data is full in the both FIFO buffers, the USB returns the NYET handshake (high-speed mode) or ACK handshake (full-speed mode) to the host. The number of receive bytes is indicated in EPSZ1. DMA transfer can be performed for receive data in EPDR1. EPDR1 can be initialized by setting the EP1CLR bit in the FIFO clear register 0. Though the 0-length packet can be received, the FIFO is not full, the ACK handshake (both highspeed and full-speed modes) is returned to the host, and data is ignored. Therefore the EP1 FULL status flag in IFR0 is not set.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W R Description Two 512-byte Receive FIFO Buffers for EP1
12.3.10 EP2 Data Register (EPDR2) EPDR2 consists of two 512-byte transmit FIFO buffer for endpoint 2. The size of EPDR2 is as twice as the maximum packet size in high-speed mode and has a dual-FIFO configuration. When transmit data is written in EPDR2 and number of transmit data is written in the packet enable register 2 (PKTE2), one packet of transmit data is valid and the buffer is switched. DMA transfer can be performed for transmit data to EPDR2. EPDR2 can be initialized by setting the EP2CLR bit in the FIFO clear register 0.
Rev. 2.00, 03/04, page 331 of 534
Bit 31 to 0
Bit Name D31 to D0
Initial Value All 0
R/W W
Description 512-byte Transmit FIFO Buffer for EP2
12.3.11 EP3 Data Register (EPDR3) EPDR3 is a 64-byte transmit FIFO buffer for endpoint 3. EPDR3 stores one packet of transmit data in the interrupt transfer for endpoint 3. If one packet of data is written and number of transmit data is written in the packet enable register 3 (PKTE3), transmit data is valid. If one packet of data is transmitted normally and the ACK handshake is returned from the host, the EP3TS bit in IFR0 is set. EPDR3 can be initialized by setting the EP3CLR bit in the FIFO clear register 0.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W W Description 64-byte Transmit FIFO Buffer for EP3
12.3.12
Data Status Register 0 (DASTS0)
DASTS0 indicates whether the IN FIFO data registers contain valid data or not. A bit in DASTS0 is set to 1 when data written to the corresponding IN FIFO becomes valid after the number of transfer bytes is written in the packet enable register. A bit in DASTS0 is cleared to 0 when all valid data is sent to the host. For endpoint 2, having a dual-FIFO configuration, the corresponding bit in DASTS0 is cleared to 0 when both FIFOs become empty.
Bit 31 to 6 5 Bit Name EP3DE Initial Value All 0 0 R/W R R Description Reserved The write value should always be 0. EP3 Data Enable Set to 1 when EP3 contains valid data and cleared to 0 when EP3 contains no valid data. 4 EP2DE 0 R EP2 Data Enable Set to 1 when EP2 contains valid data and cleared to 0 when EP2 contains no valid data. 3 to 1 0 EP0iDE All 0 0 R R Reserved The write value should always be 0. EP0i Data Enable Set to 1 when EP0i contains valid data and cleared to 0 when EP0i contains no valid data.
Rev. 2.00, 03/04, page 332 of 534
12.3.13 Packet Enable Register 0i (PKTE0i) The number of transmit data is written in PKTE0i after writing transmit data in EPDR0i. Then transmit data becomes valid and data is transmitted by the next IN token. Data is not transmitted only by writing data in EPDR0i. The number of data bytes written in EPDR0i must match the number of transmit data bytes to be written in PKTE0i.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W W Description Number of Transmit Data
12.3.14 Packet Enable Register 2 (PKTE2) The number of transmit data is written in PKTE2 after writing transmit data in EPDR2. Then transmit data becomes valid and data is transmitted by the next IN token. Data is not transmitted only by writing data in EPDR2. The number of data bytes written in EPDR2 must match the number of transmit data bytes to be written in PKTE2.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W W Description Number of Transmit Data
12.3.15 Packet Enable Register 3 (PKTE3) The number of transmit data is written in PKTE3 after writing transmit data in EPDR3. Then transmit data becomes valid and data is transmitted by the next IN token. Data is not transmitted only by writing data in EPDR3. The number of data bytes written in EPDR3 must match the number of transmit data bytes to be written in PKTE3.
Bit 31 to 0 Bit Name D31 to D0 Initial Value All 0 R/W W Description Number of Transmit Data
Rev. 2.00, 03/04, page 333 of 534
12.3.16
FIFO Clear Register 0 (FCLR0)
FCLR0 is a one-shot register used to clear the FIFO for each endpoint. Writing 1 to a bit clears the data in the corresponding FIFO. For IN FIFO, writing 1 to a bit in FCLR0 clears the data for which the corresponding bit in the packet enable register is not set to 1 after data write, or data that is validated by setting the corresponding bit in the packet enable register. For OUT FIFO, writing 1 to a bit in FCLR0 clears data that has been received. EP2 having a dualFIFO configuration is cleared by entire FIFOs. Similarly, as for EP1 FIFO with a dual-FIFO configuration, the only side currently selected is cleared. Note that this trigger does not clear the corresponding interrupt flag. Accordingly, care must be taken not to clear data that is currently being received or transmitted. Bits 6, 5, and 0 are also used as the status bits. The function of the status bit is described in the lower column of the bit description.
Bit Bit Name Initial Value All 0 0 R/W W W Description Reserved The write value should always be 0. 6 EP3CLR EP3 Clear 1 is written when clearing EP3 IN FIFO. Writing 0 is invalid and no operation is performed. R EP3 FIFO Clear Status [Setting condition] This bit is set to 1 when the EP3 FIFO is forcibly cleared by the FCLR register. When this bit is set to 1, access to the EP3 FIFO is prohibited. This bit is cleared to 0 automatically after the FIFO is internally cleared. Confirm that this bit is cleared to 0 and then wait for at least four cycles, before accessing to the EP3. [Clearing condition] This bit cannot be cleared because this bit is a status bit.
31 to 7
Rev. 2.00, 03/04, page 334 of 534
Bit 5
Bit Name EP2CLR
Initial Value 0
R/W W
Description EP2 Clear 1 is written when clearing EP2 IN FIFO. Writing 0 is invalid and no operation is performed.
R
EP2 FIFO Clear Status [Setting condition] This bit is set to 1 when the EP2 FIFO is forcibly cleared by the FCLR register. When this bit is set to 1, access to the EP2 FIFO is prohibited. This bit is cleared to 0 automatically after the FIFO is internally cleared. Confirm that this bit is cleared to 0 and then wait for at least four cycles, before accessing to the EP2. [Clearing condition] This bit cannot be cleared because this bit is a status bit.
4
EP1CLR
0
W
EP1 Clear 1 is written when clearing EP1 OUT FIFO. Writing 0 is invalid and no operation is performed.
3, 2 1
EP0oCLR
All 0 0
W W
Reserved The write value should always be 0. EP0o Clear 1 is written when clearing EP0o OUT FIFO. Writing 0 is invalid and no operation is performed.
0
EP0iCLR
0
W
EP0i Clear 1 is written when clearing EP0i IN FIFO. Writing 0 is invalid and no operation is performed.
R
EP0i FIFO Clear Status [Setting condition] This bit is set to 1 when the EP0i FIFO is forcibly cleared by the FCLR register. When this bit is set to 1, access to the EP0i FIFO is prohibited. This bit is cleared to 0 automatically after the FIFO is internally cleared. Confirm that this bit is cleared to 0 and then wait for at least four cycles, before accessing to the EP0i. [Clearing condition] This bit cannot be cleared because this bit is a status bit.
Rev. 2.00, 03/04, page 335 of 534
12.3.17
Endpoint Stall Register 0 (EPSTL0)
EPSTL0 is used to stall each endpoint. When 1 is written in a bit, the corresponding endpoint returns a stall handshake to the host, following from the next transfer. The stall bit for endpoint 0 is cleared automatically on reception of 8-byte request data for which decoding is performed by the function, and thus the EP0 STL bit is cleared to 0. When the SETUP TS flag in IFR0 is set to 1, a write of 1 to the EP0 STL bit is ignored. For details, refer to section 12.5.8, Stall Operations. When the ASCE bit in CTRL is set to 1, the EPxSTL (x = 0, 1, 2, 3) bit is automatically cleared. For details, refer to section 12.3.19, Control Register (CTRL).
Bit Bit Name Initial Value All 0 0 0 0 0 R/W R R/W R/W R/W R/W Description Reserved The write value should always be 0. 3 2 1 0 EP3STL EP2STL EP1STL EP0STL EP3 Stall Sets the EP3 stall state. EP2 Stall Sets the EP2 stall state. EP1 Stall Sets the EP1 stall state. EP0 Stall Sets the EP0 stall state.
31 to 4
12.3.18
DMA Set Register 0 (DMA0)
DMA0 is set when the DMAC dual address transfer is used for data registers for endpoints 1 and 2. For endpoint 1, if 1 is written in the EP1 DMAE bit, the transfer is requested to the DMAC when the EP1 FIFO is full at least in the single FIFO. That is, when there is valid receive data in the FIFO, the transfer is requested to the DMAC. When all receive data is read and both FIFOs are empty, the transfer is not requested to the DMCA any more. For endpoint 2, if 1 is written in the EP2 DMAE bit, the transfer is requested to the DMAC when the EP2 FIFO is empty at least in the single FIFO. That is, when there is no valid data in the FIFO even with one side, the transfer is requested to the DMAC. When data is written by the microcomputer and both FIFOs are full, the transfer is not requested to the DMCA any more. Since an interrupt request is not masked automatically, the EP1 FULL and EP2 EMPTY bits in IER0 are cleared to 0 and an interrupt should not be requested by an interrupt pin.
Rev. 2.00, 03/04, page 336 of 534
Bit
Bit Name
Initial Value All 0
R/W R R/W R/W
Description Reserved The write value should always be 0. EP2 DMA Enable Enables the DMA transfer for EP2. EP1 DMA Enable Enables the DMA transfer for EP1.
31 to 2 1 0
EP2DMAE 0 EP1DMAE 0
12.3.19 Control Register (CTRL) CTRL controls the USB module.
Bit Bit Name Initial Value All 0 0 R/W R R/W Description Reserved The write value should always be 0. 1 ASCE Automatic Stall Clear Enable When this bit is set to 1, the stall handshake is returned to the host and then the stall set bit (EPxSTL (x = 0, 1, 2, 3) bit in EPSTL0) for the returned endpoint is automatically cleared. The automatic stall clear enabling is common to all endpoints. This function cannot be controlled individually for each endpoint. When this bit is cleared to 0, the EPxSTL (x = 0, 1, 2, 3) bit is not automatically cleared. The user needs to clear the EPxSTL (x = 0, 1, 2, 3) bit. To enable this bit, this bit should be set to 1 before the EPxSTL (x = 0, 1, 2, 3) bit in EPSTL0 is set to 1. 0 PULLUPE 0 R/W Pull-Up Enable Controls pull-up of the PHY complying with the UTMI. If 1 is written in this bit, pull-up is enabled for the PHY.
31 to 2
Rev. 2.00, 03/04, page 337 of 534
12.3.20 Port Function Control Register 3 (PFCR3) PFCR3 controls the USB software reset and suspend reset.
Bit 7 Bit Name SUSRIF Initial Value 0 R/W R/W Description Suspend Recover Interrupt Flag For details on operation, refer to section 12.7.2, Software Standby in Suspend Mode. 6 SUSRIE 0 R/W Suspend Recover Interrupt Enable For details on operation, refer to section 12.7.2, Software Standby in Suspend Mode. 5 to 1 All 0 R/W Reserved These bits can be read from or written to. However, the write value should always be 0. 0 USBSWRST 0 R/W USB Module Software Reset While this bit is set to 1, the USB module is in the reset state.
12.3.21 USB Suspend Status Register (USBSUSP) USBSUSP specifies the USB state and enables or disables a USB suspend interrupt request. USBSUSP is initialized to H'00 at a reset or in hardware standby mode.
Bit 7 Bit Name Initial Value R/W R*
1
Description USB Suspend Monitor This bit is a monitor bit that indicates whether the USB is in the normal state or in the suspend state. This bit can be read from but cannot be modified. 0: Indicates that the USB is in the normal state. 1: Indicates that the USB is in the suspend state.
USUSMONI 0
Rev. 2.00, 03/04, page 338 of 534
Bit 6
Bit Name USUSFG
Initial Value 0
R/W
2
Description
R/(W)* USB Suspend Interrupt (USBI2) Flag This bit is a status flag that indicates the transition from the normal state to the suspend state is made. [Clearing condition] While USUSFG = 1, 0 is written to USUSFG after reading USUSFG [Setting condition] When transition from the normal state to the suspend state is made
5
USUSFGE
0
R/W
USB Suspend Interrupt (USBI2) Enable Enables or disables the USB suspend interrupt (USBI2) request to the CPU. 0: The USB suspend interrupt (USBI2) request is disabled. 1: The USB suspend interrupt (USBI2) request is enabled.
4
USUSOUT
0
R/W
USB Suspend Output Enable Enables or disables the suspend state notification to the external transceiver when the USB enters the suspend state. 0: Not notified that the USB enters the suspend state to the external transceiver. The external pin, USSUSP, is always set to 1. 1: Notified that the USB enters the suspend state to the external transceiver. When the USB is in the suspend state, the external pin, USSUSP, is cleared to 0.
3 to 0
All 0
R/W
Reserved The initial value should not be changed.
Notes: 1. Cannot be modified. 2. Only 0 can be written after reading 1 to clear the flag.
Rev. 2.00, 03/04, page 339 of 534
12.4
Interrupt Pins
This module has two interrupt sources. The interrupt select register 0 is used to set the correspondence between interrupt flags and interrupt sources (USBI1 and USBI0). Basically, all processing is possible by using only one interrupt source. If there is an interrupt source whose response needs to be fast, priority can be set by using the second interrupt source. Among interrupt sources of this module, an interrupt source related to endpoint 0 (bits 3 to 0 in IFR0) must be assigned to the same interrupt source. 12.4.1 USBI0 Interrupt
The USBI0 is an interrupt request for an interrupt source in which 0 is set by the interrupt select register 0. Among interrupt sources assigned to the USBI0, when only one of a corresponding bit in the interrupt flag register 0 is set to 1, an interrupt request occurs. 12.4.2 USBI1 Interrupt
The USBI1 is an interrupt request for an interrupt source in which 1 is set by the interrupt select register 0. Among interrupt sources assigned to the USBI1, when only one of a corresponding bit in the interrupt flag register 0 is set to 1, an interrupt request occurs.
Rev. 2.00, 03/04, page 340 of 534
12.5
12.5.1
Communication Operation
USB Cable Connection
If the USB cable enters the connection state from the disconnection state, perform the operation as shown in figure 12.2.
USB function During USB cable disconnection USVBUS pin = High MODE MN 0/1 in IFR0 = 00 Firmware
USB cable connection VBUS F in IFR0 = 1 VBUS MN in IFR0 = 1 MODE MN 0/1 in IFR0 = 01
Interrupt generated Clear interrupt flag (VBUS F in IFR0 = 0)
Write 1 to PULLUPE bit (PULLUPE in CTRL = 1) D+ pull-up on
Receive bus reset BRST in IFR0 = 1
Interrupt generated Clear interrupt flag (BRST in IFR0 = 0)
Transmit charp MODE MN 0/1 in IFR0 = 11 Clear all FIFOs (EP0i/0o/1/2/3 CLR in FCLR0 = 1) Is charp received? Yes High-speed mode MODE MN 0/1 in IFR0 = 10 Full-speed mode MODE MN 0/1 in IFR0 = 01
No
Wait for control transfer
Figure 12.2 USB Cable Connection
Rev. 2.00, 03/04, page 341 of 534
As not shown in figure 12.2, when the MODE F bit in IER0 is set to 1 and the MODE MN0 and MODE MN1 bits in IFR0 are changed, an interrupt occurs. This interrupt can be used to manage the bulk maximum packet size and descriptor information. 12.5.2 USB Cable Disconnection
If the USB cable enters the disconnection state from the connection state, perform the operation as shown in figure 12.3.
USB function Firmware
During USB cable connection USVBUS pin = low In full-speed mode: MODE MN 0/1 in IFR0 = 01 In high-speed mode: MODE MN 0/1 in IFR0 = 10
USB cable disconnection VBUS F in IFR0 = 1 VBUS MN in IFR0 = 0 MODE MN 0/1 in IFR0 = 00
Interrupt generated Clear interrupt flag (VBUS F in IFR0 = 0)
Write 0 to PULLUPE bit (PULLUPE in CTRL = 0) D+ pull-up off MODE MN 0/1 in IFR0 = 00
Wait for USB cable connection
Figure 12.3 USB Cable Disconnection As not shown in figure 12.3, when the MODE F bit in IER0 is set to 1 and the MODE MN0 and MODE MN1 bits in IFR0 are changed, an interrupt occurs.
Rev. 2.00, 03/04, page 342 of 534
12.5.3
Control Transfer
The control transfer consists of three stages; setup, data (sometimes omitted), and status, as shown in figure 12.4. The data stage consists of multiple bus transactions. Figures 12.5 to 12.9 show operation flows in each stage.
Setup stage Control-in
SETUP(0)
DATA0
Data stage
IN(1)
DATA1
Status stage
...
IN(0/1)
DATA0/1
IN(0)
DATA0
OUT(1)
DATA1
Control-out
SETUP(0)
DATA0
OUT(1)
DATA1
OUT(0)
DATA0
...
OUT(0/1)
DATA0/1
IN(1)
DATA1
No data
SETUP(0)
DATA0
IN(1)
DATA1
Figure 12.4 Control Transfer Stage Configuration
Rev. 2.00, 03/04, page 343 of 534
1. Setup Stage
USB function
Receive setup token
Firmware
Receive 8-byte command data in EP0s
ACK Command to be processed by firmware? Yes No
Automatic processing by this module (end)
Set setup request receive complete flag (SETUP TS in IFR0 = 1)
Interrupt generated
Clear interrupt flag (SETUP TS in IFR0 = 0) Clear EP0i FIFO (EP0iCLR in FCLR0 = 1) Clear EP0o FIFO (EP0oCLR in FCLR0 = 1)
To data stage
Read 8-byte data from EP0s
Decode command data Determine data stage direction*1
*2
To control-in data stage
To control-out data stage
Notes: 1. In the setup stage, the firmware first analyzes the request data that is sent from the host required to be processed by the firmware, and determines subsequent processing. (For example, the data stage direction.) 2. When the transfer direction is control-out, the EP0i transfer request interrupt that is required in the status stage should be enabled. When the transfer direction is control-in, this interrupt is not required and must be disabled.
Figure 12.5 Setup Stage Operation
Rev. 2.00, 03/04, page 344 of 534
2. Data Stage (Control-In) The firmware first analyzes the request data that is sent from the host in the setup stage, and determines the subsequent data stage direction. If the result of request data analysis is that the data stage is in-transfer, one packet of data to be sent to the host is written to the FIFO. If there is more data to be sent, this data is written to the FIFO after the data written first has been sent to the host (EP0i TS bit in IFR0 is set to 1). The end of the data stage is identified when the host transmits an OUT token and the status stage is entered.
USB function
Receive IN token
Firmware
From setup stage
0 written to SETUP TS in IFR0?
Yes
No NAK
Write data to EP0i data register (EPDR0i)
Valid data in EP0i FIFO?
Yes
No NAK
Write number of transmit data bytes to packet enable register 0i (PKTE0i)
Transmit data to host
ACK
Set EP0i transmit complete flag (EP0i TS in IFR0 = 1)
Interrupt generated
Clear interrupt flag (EP0i TS in IFR0 = 0)
Write data to EP0i data register (EPDR0i)
Write number of transmit data bytes to packet enable register 0i (PKTE0i) every packet.
Note:
If the size of the data transmitted by the function is smaller than the data size requested by the host, the function indicates the end of the data stage by returning to the host a packet shorter than the maximum packet size. If the size of the data transmitted by the function is an integral multiple of the maximum packet size, the function indicates the end of the data stage by transmitting a zero-length packet.
Figure 12.6 Data Stage Operation (Control-In)
Rev. 2.00, 03/04, page 345 of 534
3. Data Stage (Control-Out) The firmware first analyzes the request data that is sent from the host in the setup stage, and determines the subsequent data stage direction. If the result of request data analysis is that the data stage is out-transfer, data from the host is waited for, and after data is received (EP0o TS bit in IFR0 is set to 1), data is read from the FIFO. The end of the data stage is identified when the host transmits an IN token and the status stage is entered.
USB function Full speed Receive OUT token High speed Receive PING token Firmware
0 written to SETUP TS in IFR0? Yes
No NAK ACK (for only PING)
Receive data from host NYET (high speed) ACK (full speed and 0-length packet) Set EP0o receive complete flag (EP0o TS in IFR0 = 1) Interrupt generated
Clear interrupt flag (EP0oTS in IFR0 = 0)
Receive PING token (high speed) Receive OUT token (full speed)
Confirm receive data length from EP0o receive data size register (EPSZ0o)
Is all received data in FIFO read? Yes
No NAK ACK (for only PING)
Read data from EP0o data register (EPDR0o)
Figure 12.7 Data Stage Operation (Control-Out)
Rev. 2.00, 03/04, page 346 of 534
4. Status Stage (Control-In) The control-in status stage starts with an OUT token from the host. The firmware receives 0length packet from the host, and ends control transfer.
USB function
Receive OUT token
Firmware
Receive 0-length packet from host
ACK
Set EP0o receive complete flag (EP0o TS in IFR0 = 1)
Interrupt generated
Clear interrupt flag (EP0o TS in IFR0 = 0)
End of control transfer
End of control transfer
Figure 12.8 Status Stage Operation (Control-In)
Rev. 2.00, 03/04, page 347 of 534
5. Status Stage (Control-Out) The control-out status stage starts with an IN token from the host. When an IN-token is received at the start of the status stage, there is not yet any data in the EP0i FIFO, and so an EP0i transfer request interrupt is generated. The firmware recognizes from this interrupt that the status stage has started. Next, in order to transmit 0-length packet to the host, 0 is written in the packet enable register 0i but no data is written to the EP0i FIFO. As a result, the next IN token causes 0-length packet to be transmitted to the host, and control transfer ends. After the firmware has finished all processing relating to the data stage, 0 should be written in the packet enable register 0i.
USB function Firmware
Receive IN token
Is SETUP TS in IFR0 cleared to 0?
Yes
No
NAK Interrupt generated
Valid data in EP0i FIFO?
Yes
No
NAK
Clear interrupt flag (EP0i TR in IFR0 = 0)
EP0i transfer request interrupt prohibited (EP0i TR in IER0 = 0)
Transmit data to host ACK Set EP0i transmit complete flag Interrupt generated (EP0i TS in IFR0 = 1)
Write 0 to packet enable register 0i (PKTE0i)
Clear interrupt flag (EP0i TS in IFR0 = 0)
End of control transfer
End of control transfer
Figure 12.9 Status Stage Operation (Control-Out)
Rev. 2.00, 03/04, page 348 of 534
12.5.4
EP1 Bulk-Out Transfer (Dual FIFO)
EP1 has two 64-byte FIFOs in full-speed mode and two 512-byte FIFOs in high-speed mode, but the user can receive data and read receive data without being aware of this dual-FIFO configuration. Make sure to confirm that the EP1 FULL bit in IFR0 is set to 1 before reading the single FIFO. When one FIFO is full after reception is completed, the EP1 FULL bit in IFR0 is set. After the first receive operation into one of the FIFOs when both FIFOs are empty, the other FIFO is empty, and so the next packet can be received immediately. When both FIFOs are full, NAK is returned to the host automatically. When reading of the receive data is completed following data reception, this operation empties the FIFO that has just been read, and makes it ready to receive the next packet. If 0-length packet is received from the host, the ACK handshake is returned to the host regardless of mode (full-speed or high-speed mode) and the EP1 FULL bit in IFR0 is not set. Note: The dual-configured FIFOs are handled in packet units. Therefore, even if either of FIFOs is empty because of a short packet, when the packet is received successfully, both FIFOs become full.
Rev. 2.00, 03/04, page 349 of 534
USB function
Firmware
Receive OUT token
Full speed
Receive PING token
High speed
Is there any space in EP1 FIFO?
No
NAK
Yes
ACK (for only PING)
Receive data from host
Yes
Is receive data length 0?
No
Is there any space in other EP1 FIFO?
No
NYET (High speed) ACK (Full speed)
Set EP1 FIFO full status (EP1 FULL in IFR0 = 1)
ACK
Yes
Set EP1 FIFO full status (EP1 FULL in IFR0 = 1)
Interrupt generated
Confirm receive data length from EP1 receive data size register (EPSZ1)
Read data from EP1 data register (EPDR1)
Is there any space in both EP1 FIFOs?
No
Interrupt generated
Yes
Clear EP1 FIFO full status (EP1 FULL in IFR0 = 0)
Figure 12.10 EP1 Bulk-Out Transfer Operation
Rev. 2.00, 03/04, page 350 of 534
12.5.5
EP2 Bulk-In Transfer (Dual FIFO)
EP2 has two 64-byte FIFOs in full-speed mode and two 512-byte FIFOs in high-speed mode, but the user can transmit data and write transmit data without being aware of this dual-FIFO configuration. However, one data write should be performed for one FIFO. For example, even if both FIFOs are empty, it is not possible to write the number of transmit data in PKTE2 at one time after consecutively writing 128 bytes of data in full-speed mode or 1024 bytes of data in highspeed mode. The number of transmit data must be written in PKTE2 for each 64-byte write in fullspeed mode or 512-byte write in high-speed mode. Make sure to confirm that the EP2EMPTY bit in IFR0 is set to 1 before writing data. When performing bulk-in transfer is required, write 1 to the EP2 EMPTY bit in IER0 first and then enable the EP2 FIFO empty interrupt. At first, both EP2 FIFOs are empty, and so an EP2 FIFO empty interrupt is generated immediately. The data to be transmitted is written to the data register using this interrupt. After the first transmit data write for one FIFO, the other FIFO is empty, and so the next transmit data can be written to the other FIFO immediately. When both FIFOs are full, the EP2 EMPTY bit is cleared to 0. If at least one FIFO is empty, the EP2 EMPTY bit in IFR0 is set to 1. When ACK is returned from the host after data transmission is completed, the FIFO used in the data transmission becomes empty. If the other FIFO contains valid transmit data at this time, transmission can be continued. When transmission of all data has been completed, write 0 to the EP2 EMPTY bit in IER0 and disable interrupt requests. Note: The dual-configured FIFOs are handled in packet units. Therefore, even if either of FIFOs is empty because of a short packet, when the number of transmit data is written in the packet enable register 2 (PKTE2), both FIFOs become full.
Rev. 2.00, 03/04, page 351 of 534
USB function
Firmware
Receive IN token
Valid data in EP2 FIFO? Yes Transmit data to host ACK
No NAK
Enable EP2 FIFO empty interrupt (EP2 EMPTY in IER0 = 1)
Is there any space in EP2 FIFO? No Clear EP2 empty status (EP2 EMPTY in IFR0 = 0)
Yes
Set EP2 empty status (EP2 EMPTY in IFR0 = 1)
Interrupt generated
Has all data been transmitted to host? No
Yes
Write one-packet data to EP2 data register (EPDR2)
Write number of transmit data bytes to packet enable register 2 (EPDR2)
Disable EP2 FIFO empty interrupt (EP2 EMPTY in IER0 = 0)
Is there No any data to be transmitted to host?
Yes
Figure 12.11 EP2 Bulk-In Transfer Operation
Rev. 2.00, 03/04, page 352 of 534
12.5.6
EP3 Interrupt-In Transfer
USB function Firmware
Is there any data to be transmitted to host? Receive IN token Yes Write data to EP3 data register (EPDR3)
No
Valid data in EP3 FIFO? Yes Transmit data to host ACK Set EP3 transmit complete flag (EP3 TS in IFR0 = 1)
No NAK
Write number of transmit data bytes to packet enable register 3 (PKTE3)
Interrupt generated
Clear EP3 transmit complete flag (EP3 TS in IFR0 = 0)
Is there any data to be transmitted to host? Yes Write data to EP3 data register (EPDR3)
No
Write number of transmit data bytes to packet enable register 3 (PKTE3)
Note:
This flowchart shows just one example of interrupt-in transfer processing. Other possibilities include an operation flow in which, if there is data to be transmitted, the EP3DE bit in DASTS0 is referred to confirm that the FIFO is empty, and then data is written to the FIFO.
Figure 12.12 EP3 Interrupt-In Transfer Operation
Rev. 2.00, 03/04, page 353 of 534
12.5.7
Processing of USB Standard Requests and Class/Vendor Requests
1. Processing of Requests Transmitted by Control Transfer A request transmitted from the host by control transfer may require decoding and execution of request processing by the firmware. Whether or not request decoding is required by the firmware is indicated in table 12.2 below. Table 12.2 Request Decoding by Firmware
Decoding not Necessary by Firmware Clear Feature Get Configuration Get Interface Get Status Set Address Set Configuration Set Feature Set Interface Decoding Necessary by Firmware Get Descriptor Synch Frame Set Descriptor Class/Vendor request
If decoding is not necessary by the firmware, request decoding and data stage and status stage processing are performed automatically. No processing is necessary by the user. An interrupt is not generated in this case. If decoding is necessary by the firmware, this module stores the request in the EP0s FIFO. After normal reception is completed, the SETUPTS flag in IER0 is set and an interrupt request is generated. In the interrupt routine, eight bytes of data must be read from the EP0s data register (EPDR0s) and decoded by the firmware. The necessary data stage and status stage processing should then be carried out according to the result of the decoding operation.
Rev. 2.00, 03/04, page 354 of 534
12.5.8
Stall Operations
This section describes stall operations in the USB module. There are two cases in which the USB module stall function is used: • When the firmware forcibly stalls an endpoint for some reason • When a stall is performed automatically within the USB module due to a USB specification violation The USB module has internal status bits that hold the status (stall or non-stall) of each endpoint. When a transaction is sent from the host, the module refers these internal status bits and determines whether to return a stall to the host. These bits cannot be cleared by the firmware; they must be cleared with a Clear Feature request from the host. However, the internal status bit for EP0 is cleared automatically at the reception of the setup request. 1. Forcible Stall by Firmware The firmware uses EPSTL0 to issue a stall request for the USB module. When the firmware wishes to stall a specific endpoint, it sets the corresponding bit in EPSTL0 (1-1 in figure 12.13). The internal status bits are not changed at this time. When a transaction is sent from the host for the endpoint for which the corresponding bit in EPSTL0 was set, the USB module refers the internal status bit, and if this is not set, refers the corresponding bit in EPSTL0 (1-2 in figure 12.13). If the corresponding bit in EPSTL0 is set, the USB module sets the internal status bit and returns a stall handshake to the host (1-3 in figure 12.13). If the corresponding bit in EPSTL0 is not set, the internal status bit is not changed and the transaction is accepted. Once an internal status bit is set, it remains set until cleared by a Clear Feature request from the host, without regarding to EPSTL0. Even after a corresponding bit is cleared by the Clear Feature request (3-1 in figure 12.13), the USB module continues to return a stall handshake while the bit in EPSTL0 is set, since the internal status bit is set each time a transaction is executed for the corresponding endpoint (1-2 in figure 12.13). To clear a stall, therefore, it is necessary for the corresponding bit in EPSTL0 to be cleared by the firmware and also for the internal status bit to be cleared with a Clear Feature request (2-1, 2-2, and 2-3 in figure 12.13).
Rev. 2.00, 03/04, page 355 of 534
(1) Transition from normal operation to stall (1-1)
USB
USB function module
1. Set EPSTL0 to 1 by firmware
Internal status bit 0
EPSTL0 0→1
(1-2) Reference
Transaction request
Internal status bit 0
EPSTL0 1
1. Receive IN/OUT token from the host 2. Refer to EPSTL0
To (1-3) or (1-4) (1-3) Stall
1. EPSTL0 is set to 1 2. Set internal status bit to 1 3. Transmit stall handshake
Stall handshake
Internal status bit 0→1
EPSTL0 1
To (2-1) or (3-1)
(2) When Clear Feature is sent after EPSTL0 has been cleared (2-1)
Transaction request
Internal status bit 1 EPSTL0 1→0 1. Clear EPSTL0 to 0 by firmware 2. Receive IN/OUT token from the host 3. Internal status bit has been set to 1 4. EPSTL0 is not referred to 5. No change in internal status bit 1. Transmit stall handshake
(2-2)
Stall handshake
Internal status bit 1
EPSTL0 0
(2-3)
Clear Feature command
Internal status bit 1→0
EPSTL0 0
1. Clear internal status bit to 0
Normal status restored
(3) When Clear Feature is sent before EPSTL0 is cleared to 0 (3-1) 1. Clear internal status bit to 0 2. No change in EPSTL0
Clear Feature command
Internal status bit 1→0 To (1-2)
EPSTL0 1
Figure 12.13 Forcible Stall by Firmware
Rev. 2.00, 03/04, page 356 of 534
2. Automatic Stall by USB Function Module When a stall setting is made with the Set Feature request or in the event of a USB specification violation, the USB module automatically sets the internal status bit for the corresponding endpoint without regarding to EPSTL0, and returns a stall handshake (1-1 in figure 12.14). Once an internal status bit is set, it remains set until cleared by a Clear Feature request from the host, without regarding to EPSTL0. After a corresponding bit is cleared by the Clear Feature request, EPSTL0 is referred (3-1 in figure 12.14). The USB module continues to return a stall handshake while the internal status bit is set, since the internal status bit is set even if a transaction is executed for the corresponding endpoint (2-1 and 2-2 in figure 12.14). To clear a stall, therefore, the internal status bit must be cleared with a Clear Feature request (3-1 in figure 12.14). If set by the firmware, EPSTL0 should also be cleared (2-1 in figure 12.14).
(1) Transition from normal operation to stall
USB function module (1-1) 1. In case of USB specification violation, USB function module stalls endpoint automatically.
Stall handshake
Internal status bit 0→1 To (2-1) or (3-1)
EPSTL0 0
(2) When transaction is performed while internal status bit is set
(2-1) Transaction request 1. Clear EPSTL0 to 0 by firmware 2. Receive IN/OUT token from the host 3. Internal status bit has been set to 1 4. EPSTL0 is not referred to 5. No change in internal status bit 1. Transmit stall handshake
Internal status bit 1
EPSTL0 0
(2-2)
Stall handshake
Internal status bit 1
EPSTL0 0
Stall status maintained (3) When Clear Feature is sent before transaction is performed (3-1) Clear Feature command 1. Clear the internal status bit to 0 2. No change in EPSTL0
Internal status bit 1→0
EPSTL0 0
Normal status restored
Figure 12.14 Automatic Stall by USB Function Module
Rev. 2.00, 03/04, page 357 of 534
12.5.9
Tree Configuration
This section describes the tree configuration of this module. The USB determines the tree configuration in the function using three parameters such as Configuration, Interface, and Alternate. The tree configuration of this module is shown in table 12.3. Table 12.3 Tree Configuration
EP Number 0 1 2 3 Conf. 1 1 1 Int. 0 0 0 Alt. 0 0 0 Transfer Method Control Bulk Bulk Interrupt Transfer Direction In/Out Out In In
12.5.10 Power Supply Specification This module functions by self power supply. The bus power supply supplied from the USB cable is not available.
12.6
Notes on Using DMA
• PKTE2 Operation (EP2) When DMA transfer is performed on EP2 transmit data, the USB module automatically performs the same processing as writing the number of transmit data to PKTE2 if one data FIFO (maximum packet size) becomes full. Accordingly, to transfer data of integral multiples of the maximum packet size, the user needs not to write the number of transmit data in PKTE2. To transfer data of less than the maximum packet size, the user must write the number of transmit data in PKTE2 using the DMA transfer end interrupt of the DMAC. If the user writes the number of transmit data in PKTE2 in cases other than the case when data of less than the maximum packet size is transferred, excess transfer occurs and correct operation cannot be guaranteed. Figure 12.15 shows an example for transmitting 1050 bytes of data from EP1 to the host in high-speed mode. In this case, internal processing as the same as writing the number of transmit data to PKTE2 is automatically performed twice. This kind of internal processing is performed when the currently selected data FIFO becomes full. Accordingly, this processing is automatically performed only when the maximum packet size of data is transmitted. This processing is not performed automatically when data less than the maximum packet size is transmitted.
Rev. 2.00, 03/04, page 358 of 534
In this example, when the first 512 bytes of data has not been transmitted to the host at the end of DMA transfer on the first 512 bytes of data and second 512 bytes of data, the DMA request does not occur. If the transmission has been completed, the DMA request occurs because there is space in the one FIFO. When the last 26 bytes of data has been transferred, there is no data to be transferred in the firmware. However, the DMA request occurs if there is space in the FIFO. Therefore, when DMA transfer is completed on all data, the DMA enable state should be cleared by writing 0 to the EP2DMAE bit in DMA0. Note that over-sampling should not be performed by the DMAC. Generally the number of transmit data is set as the number of DMAC transfers and the number of data less than the maximum packet size is written in PKTE2 using the DMA transfer end interrupt. If the number of transmit data is an integral multiple of the maximum packet size (for example, 1024 bytes or 2048 bytes), the number of transmit data is automatically written in PKTE2. In this case, the user must not write the number of transmit data in PKTE2 using the DMA transfer end interrupt. If the writing is performed, correct operation cannot be guaranteed.
512 bytes
512 bytes
26 bytes
PKTE2 (Automatically performed)
PKTE2 (Automatically performed)
PKTE2 is not performed
Executed by DMA transfer end interrupt (user)
Figure 12.15 PKTE2 Operation for EP2
12.7
12.7.1
Transition to USB Suspend Mode
Suspend Signal Output
If the USB continues to be idle for the specified time, the USB enters the suspend state. When the USB enters the suspend state, the USSUSP signal is asserted to low and the suspend state can be notified to the external transceiver. When the external transceiver receives the USSUSP signal, the clock oscillation is stopped and the power-down state is entered. Therefore the USCLK supplied to this LSI is stopped. To operate the USB module, the USCLK supplied by the external transceiver and system clock (φ) should be supplied. While the USCLK is stopped, programming is required so that access to the USB module does not occur.
Rev. 2.00, 03/04, page 359 of 534
To control this, the USB suspend interrupt (USBI2) which notifies that the USB module enters or recovers the suspend state to the CPU and a register bit (USUSOUT bit in USBSUSP) which controls the external USSUSP output are provided. Figure 12.16 shows the enter/recover sequence of suspend mode. And the following 1 to 6 descriptions explain the operation at its each point.
USCLK Internal suspend signal USBI2 interrupt request mask signal Interrupt flag cleared
Initial setting [1] :
[2]
[3]
[4]
[5]
[6]
signal mask period
Figure 12.16 Enter/Recover Sequence of USB Suspend State 1. USBSUSP Output Mask When the USUSOUT bit in USBSUSP is cleared to 0, output of the USSUSP pin is masked (fixed to 1) and notification of the suspend state to the external transceiver is disabled. 2. Entering Suspend State by USB Module If the USB continues to be idle for the specified time, the USB module asserts the internal suspend signal and enters the suspend state. Since the USSUSP output is masked by means of the USUSOUT bit in USBSUSP, the external pin, USSUSP, is not changed. 3. USB Suspend Interrupt (USBI2) When the USUSFGE bit in USBSUSP is set to 1 and the internal suspend signal of the USB module is changed, an interrupt (USBI2) can be requested to the CPU. As the initial setting, the USUSFG bit (interrupt flag) in USBSUSP should be cleared to 0 and then the USUSFGE bit in USBSUSP should be set to 1. The USBI2 interrupt request occurs when the internal suspend signal of the USB module is changed. After the interrupt flag is cleared in the interrupt routine, monitor the USUSMONI bit in USBSUSP and confirm that the interrupt occurs because of transition to the suspend state. Note that an interrupt occurs when transition is made in the following order: normal mode, suspend mode, and normal mode.
Rev. 2.00, 03/04, page 360 of 534
4. Clearing Suspend Signal Output Mask To prevent access to the USB module by the CPU or DMAC from occurring in the interrupt processing routine, the USUSOUT bit in USBSUSP is set to 1 after the setting such as to stop the DMAC is made. Then output of the USSUSP pin goes low and the USCLK input from the external transceiver is stopped. After the USCLK input is stopped, do not access the USB module registers by the CPU or DMAC. 5. USB Suspend Interrupt (USBI2) Even if the USCLK is stopped, the internal suspend signal is negated after the USB bus state is recovered from the suspend state. Since the USBI2 interrupt is requested when the internal suspend signal is changed, if interrupts are enabled, an interrupt is requested to the CPU even when the internal suspend signal is negated. 6. Suspend Signal Output Mask In the interrupt processing routine, output of the USSUSP pin should be masked (fixed to 1) by clearing the USUSOUT bit in USBSUSP to 0. Then access to the USB module registers can be performed by the CPU or DMAC. 12.7.2 Software Standby in Suspend Mode
In the firmware mainly for the USB, if the USB enters suspend mode, this LSI enters software standby mode which is the power-down state because power consumption of the system can be reduced. Since the system clock (φ) is stopped in software standby mode, the suspend recover interrupt (SUSRI) is used to recover from software standby mode. Figure 12.17 shows the enter/recover sequence of suspend mode and software standby mode. And the following 1 to 8 descriptions explain the operation at its each point.
Rev. 2.00, 03/04, page 361 of 534
USCLK Internal suspend signal
Interrupt flag cleared
USBI2 interrupt request
Interrupt flag cleared
mask signal
Software standby mode
φ
Oscillation stabilization time Interrupt flag cleared
SUSRI interrupt request
Initial setting
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
:
signal mask period. During the period other than the signal mask period, the internal suspend signal is inverted and output.
Figure 12.17 Enter/Recover Sequence of USB Suspend State and Software Standby Mode 1. USSUSP Output Mask When the USUSOUT bit in USBSUSP is cleared to 0, output of the USSUSP pin is masked (fixed to 1) and notification of the suspend state to the external transceiver is disabled. 2. Entering Suspend State by USB Module If the USB continues to be idle for the specified time, the USB module asserts the internal suspend signal and enters the suspend state. Since the USSUSP output is masked by means of the USUSOUT bit in USBSUSP, the external pin, USSUSP, is not changed. 3. USB Suspend Interrupt (USBI2) When the USUSFGE bit in USBSUSP is set to 1 and the internal suspend signal of the USB module is changed, an interrupt (USBI2) can be requested to the CPU. As the initial setting, the USUSFG bit (interrupt flag) in USBSUSP should be cleared to 0 and then the USUSFGE bit in USBSUSP should be set to 1. The USBI2 interrupt request occurs when the internal suspend signal of the USB module is changed. After the interrupt flag is cleared in the interrupt routine, monitor the USUSMONI bit in USBSUSP and confirm that the interrupt occurs because of transition to the suspend state. Note that an interrupt occurs when transition is made in the following order: normal mode, suspend mode, and normal mode.
Rev. 2.00, 03/04, page 362 of 534
4. Clearing Suspend Signal Output Mask To prevent access to the USB module by the CPU or DMAC from occurring in the interrupt processing routine, the USUSOUT bit in USBSUSP is set to 1 after the setting such as to stop the DMAC is made. Then output of the USSUSP pin goes low and the USCLK input from the external transceiver is stopped. After the USCLK input is stopped, do not access the USB module registers by the CPU or DMAC. 5. Entering Software Standby Mode When the USB bus state enters the state other than the USB idle state before software standby mode is entered, the suspend recover interrupt (SUSRI) is set in order to clear software standby mode. To enable the suspend recover interrupt (SUSRI), clear the SUSRIF bit in PFCR3 to 0 and then set the SUSRIE bit in PFCR3 to 1. After that, the SLEEP instruction is executed while the SSBY bit in SBYCR is set to 1 in order to enter software standby mode. The system clock (φ) is stopped and this LSI enters the power-down state. 6. Recover Event from Suspend If the USB bus state recovers from the suspend state, the suspend recover interrupt (SUSRI) is requested. By this interrupt request, software standby mode can be cancelled. If the USB bus state recovers from the suspend state, the USSUSP pin is negated and this LSI starts oscillation. After the specified oscillation stabilization time is elapsed, the internal system clock is supplied and the CPU executes the suspend recover interrupt (SUSRI) processing. 7. Suspend Recover Interrupt (SUSRI) In the interrupt processing routine, clear the SUSRIF bit in PFCR3 to 0 and then clear the SUSRIE bit in PFCR3 to 0 in order to disable the suspend recover interrupt (SUSRI). At this time, the USBI2 interrupt is requested. The priority of the SUSRI interrupt must be higher than that of the USBI2 interrupt. 8. USB Suspend Interrupt (USBI2) After recovering from the SUSRI interrupt processing, the pending USBI2 interrupt processing is executed. To mask output of the USSUSP pin (fix to 1), clear the USUSOUT bit in USBSUSP to 0 in the interrupt processing routine. Then access to the USB registers can be performed by the CPU or DMAC.
Rev. 2.00, 03/04, page 363 of 534
12.8
12.8.1
Usage Notes
Setup Data Reception
The following must be noted for the EP0s FIFO used to receive 8-byte setup data. The USB is designed to always receive setup requests. Accordingly, write from the USB bus has higher priority than read from CPU. If the reception of the next setup request starts while CPU is reading data after completing reception, this data read from CPU is forcibly cancelled and the next setup request write starts. After the next setup request write, data read from CPU is thus undefined. 12.8.2 FIFO Clear
If the USB cable is disconnected during communication, old data may be contained in the FIFO. Accordingly, FIFOs must be cleared immediately after USB cable connection. Note, however, that FIFOs that are currently used for data transfer to or from the host must not be cleared. 12.8.3 Operating Frequency
The system clock (φ) must range from 31 MHz to 33 MHz. 12.8.4 Interrupts
This module uses signals in which each bit in IFR0 is logical-ORed as interrupt requests. Thus, even if a flag is cleared, the request is not negated while at least one of other flags is set. 12.8.5 Register Access Size
In this module, all registers should be accessed in 32-bit units using the MOV.L instruction. They cannot be accessed in 8- or 16-bit units using instructions such as MOV.W, MOV.B, or bit manipulation instruction.
Rev. 2.00, 03/04, page 364 of 534
12.8.6
Data Register Overread or Overwrite
When data registers in this module are read from or written to, the following must be noted: 1. Receive Data Register Receive data registers must not read a data size that is greater than the effective size of the read data item. In other words, receive data registers must not read data with data size larger than that specified by the receive data size register. For the receive data register of EP1 having a dual-FIFO configuration, data to be read at any time must be within the maximum packet size. Make sure to confirm that the EP1 FULL bit in IFR0 is set to 1 before reading from data from a single FIFO, because data registers cannot be accessed while FIFOs are switched. 2. Transmit Data Register Data to be written to the transmit data registers must be within the maximum packet size. For the transmit data register of EP2 having a dual-FIFO configuration, data to be written at any time must be within the maximum packet size. In this case, after a data write, the FIFO is switched to the other FIFO, enabling an further data write, when the number of transmit data is written in PKTE2. Accordingly, data of size corresponding to two FIFOs must not be written to the transmit data registers at a time. Make sure to confirm that the EP2EMPTY bit in IFR0 is set to 1 before writing data to a single FIFO, because data registers cannot be accessed while FIFOs are switched. 12.8.7 EP0 Interrupt Sources Assignment
EP0 interrupt sources assigned to bits 3 to 0 in IFR0 must be assigned to the same interrupt signal by setting ISR0. There are no other restrictions on interrupt sources. 12.8.8 FIFO Size at Full Speed Mode
This module operates in high-speed or full-speed mode. The FIFO size to be used in each mode is shown below. Therefore, data more than 64 bytes cannot be read from or written to the one FIFO for EP1 or EP2 in full-speed mode. If the read or write is performed, correct transfer is impossible. Data less than 64 bytes should be read from or written to.
Rev. 2.00, 03/04, page 365 of 534
Table 12.4 FIFO Size in Each Transfer Mode
FIFO Size Endpoint EP0s EP0i EP0o EP1 EP2 EP3 Full Speed 8 bytes 64 bytes 64 bytes 64 bytes 64 bytes 64 bytes High Speed 8 bytes 64 bytes 64 bytes 512 bytes 512 bytes 64 bytes FIFO Configuration Single Single Single Dual Dual Single Transfer Method Setup Control Control Bulk Bulk Interrupt Transfer Direction Out In Out Out In In
12.8.9
Level Shifter for VBUS Pin
The USVBUS pin of this LSI must be connected to the USB connector's VBUS pin via a level shifter. (Make sure the polarity is correct.) This is because the USB module has a circuit that operates by detecting USB cable connection or disconnection. Even if the power of the device incorporating this module is turned off, 5-V power is applied to the USB connector's VBUS pin while the USB cable is connected to the device set. To protect the LSI from destruction, use an external level shifter which allows voltage application to the pin even when the power is off. 12.8.10 USB 2.0 Transceiver (Physical Layer) This module does not include the USB 2.0 transceiver. Therefore an external transceiver should be used. 12.8.11 EPDR0s Read EPDR0s must be read in 8-byte units. Otherwise, the data received in the next setup cannot be read normally. 12.8.12 USB Bus Idle in High-Speed Mode When the USB bus enters the idle state in high-speed mode, this module enters full-speed mode. However, the MODE MN1 and MODE MN0 bits in IFR0 are not changed. Therefore, the MODEF bit in IFR0 is not set.
Rev. 2.00, 03/04, page 366 of 534
12.8.13 Note on USB Bus Disconnection If the connector is disconnected by the user regardless of whether communication is in progress with the host or the idle state is entered, the USB cable may be disconnected. When the USB cable is disconnected and data transfer is performed between the USB module and the host, the correct transfer cannot be performed after the cable is connected again. Therefore, when the cable disconnection is detected, the USB module must be reset. To reset this, set the USBSWRST bit in PFCR3 to 1. The CPU must access PFCR3. After the USBSWRST bit is set to 1 and one clock is elapsed, clear the USBSWRST bit to 0. Then, the USB module operates normally. After a reset, values of all registers in the USB module are returned to the initial values so they should be set again. 12.8.14 Example of External Circuit Since this LSI does not contain the on-chip USB physical layer, the physical layer LSI in the UTMI specification should be connected externally. Figure 12.19 shows a connection example of the external circuit. Figure 12.19 is only an example. The actual connecting differs according to the specifications of the external physical layer LSI in the UTMI specification.
External physical layer LSI in the UTMI specification XcvrSelect TermSelect CLK RXActive RXValid (RXValidH) RXError TXValid (TXValidH) TXReady Data15 to Data0 ValidH SuspendM LineState [1:0] OpMode [1] OpMode [0] RST (assert H)
This LSI USXCVRS USTSEL USCLK USRXACT USRXV USRXERR USTXV USTXRDY USD15 to USD0 USVBUS USWDVLD USSUSP USLSTA1, USLSTA0 USOPM1 USOPM0 RES
DP DM
Reset signal
Level shifter VBUS (5 V)
(3.3 V) Power-supply voltage can be applied to this IC even when the system (LSI) power is off.
USB connector
Figure 12.18 Connection Example of External Circuit
Rev. 2.00, 03/04, page 367 of 534
12.8.15 External Physical Layer LSI The pin name, usage, and type may differ according to each of external physical layer LSI. Check and confirm the specifications of it before connecting to this LSI. 12.8.16 Operation at the Bus Reset Reception When a bus reset is received from the host, there will be a defect in the operation described below. When the first bus reset from the host completes, and then the second bus reset is received without following bus accesses of SOF or data transfer, the second bus reset will not be received successfully (shown in case 2 in figure 12.19).
Bus reset (first) SOF, etc. Bus reset (second)
Case 1
Case 2
Bus reset (first)
No transfer (Idle)
Bus reset (second)
Figure 12.19 Bus Reset Following Completion of First Bus Reset Note: Since the successive bus resets are not normally required, the bus reset does not occur successively with following no data transfer. In order to detect the bus reset correctly, even in the case 2, follow the procedure shown in figure 12.20.
Rev. 2.00, 03/04, page 368 of 534
Normal bus reset processing
Clear USBSUSP/USUSFG flag to 0
Yes
IFR0/SETUP TS=1?
No
Yes
USBSUSP/USUSFG=1?
No
IFR0/VBUS F=1?
Yes
PFCR3/USBSWRST 1 write PFCR3/USBSWRST 0 write USB module initial setting (ISR0/IER0 etc) CTRL/PULLUPE 1 write
End
Figure 12.20 Bus Reset Detection Flow 12.8.17 Usage Notes in Control IN Transfer In the status stage of the control IN transfer, 0-length packet is only received. 12.8.18 USB Interrupt During Software Standby As the USB clock stops during software standby, USBI0 and USBI1 interrupts like VBUS interrupt will not be generated.
Rev. 2.00, 03/04, page 369 of 534
Rev. 2.00, 03/04, page 370 of 534
Section 13 RAM
This LSI has an on-chip high-speed static RAM. The RAM is connected to the CPU by a 16-bit data bus and is connected to the DMAC by a 32-bit data bus, enabling one-state access to byte data, word data, and longword data (note that two-state access is used when the RAM is accessed by using the longword access instruction such as MOV.L by the CPU). The on-chip RAM can be enabled or disabled by means of the RAME bit in the system control register (SYSCR). For details on the system control register (SYSCR), refer to section 3.2.2, System Control Register (SYSCR).
Product Type H8S/2170 HD64F2170 ROM Type Flash memory version RAM Capacity 32 kbytes RAM Address H'FF7000 to H'FFEFFF
Rev. 2.00, 03/04, page 371 of 534
Rev. 2.00, 03/04, page 372 of 534
Section 14 Flash Memory (0.18-µm F-ZTAT Version)
The flash memory has the following features. Figure 14.1 shows a block diagram of the flash memory.
14.1
• Size
Features
ROM Size 256 kbytes ROM Address H'000000 to H'03FFFF
Product Classification H8S/2170 HD64F2170
• Two flash-memory MATs according to LSI initiation mode The on-chip flash memory has two memory spaces in the same address space (hereafter referred to as memory MATs). The mode setting in the initiation determines which memory MAT is initiated first. The MAT can be switched by using the bank-switching method after initiation. The user memory MAT is initiated at a power-on reset in user mode: 256 kbytes The user boot memory MAT is initiated at a power-on reset in user boot mode: 8 kbytes • Programming/erasing interface by the download of on-chip program This LSI has a dedicated programming/erasing program. After downloading this program to the on-chip RAM, programming/erasing can be performed by setting the argument parameter. • Programming/erasing time The flash memory programming time is 3 ms (typ) in 128-byte simultaneous programming and approximately 25 µs per byte. The erasing time is 1000 ms (typ) per 64-kbyte block. • Number of programming The number of flash memory programming can be up to 100 times at the minimum. (The value ranged from 1 to 100 is guaranteed.) • Three on-board programming modes Boot mode This mode is a program mode that uses an on-chip SCI interface. The user MAT and user boot MAT can be programmed. This mode can automatically adjust the bit rate between host and this LSI. User program mode The user MAT can be programmed by using the optional interface. User boot mode The user boot program of the optional interface can be made and the user MAT can be programmed.
Rev. 2.00, 03/04, page 373 of 534
• Programming/erasing protection Sets protection against flash memory programming/erasing via hardware, software, or error protection. • Programmer mode This mode uses the PROM programmer. The user MAT and user boot MAT can be programmed.
Internal address bus
Internal data bus (16 bits)
FCCS FPCS
Module bus
FECS FKEY FMATS FTDAR
Control unit
Memory MAT unit User MAT: 256 kbytes User boot MAT: 8 kbytes
Flash memory
FWE pin Mode pin Legend FCCS: FPCS: FECS: FKEY: FMATS: FTDAR:
Operating mode
Flash code control status register Flash program code select register Flash erase code select register Flash key code register Flash MAT select register Flash transfer destination address register
Figure 14.1 Block Diagram of Flash Memory
Rev. 2.00, 03/04, page 374 of 534
14.1.1
Operating Mode
When each mode pin and the FWE pin are set in the reset state and reset start is performed, this LSI enters each operating mode as shown in figure 14.2. • Flash memory can be read in user mode, but cannot be programmed or erased. • Flash memory can be read, programmed, or erased on the board only in user program mode, user boot mode, and boot mode. • Flash memory can be read, programmed, or erased by means of the PROM programmer in programmer mode.
=0
Reset state
Programmer mode setting
Programmer mode
=0
er Us s de mo
=0
ing ett
Bo ot
mo de
=0
se tt ing
ot g bo tin er set Us de mo
=0
FWE = 0
User mode
FWE = 1
User program mode
User boot mode On-board programming mode
Boot mode
Figure 14.2 Mode Transition of Flash Memory
Rev. 2.00, 03/04, page 375 of 534
14.1.2
Mode Comparison
The comparison table of programming and erasing related items about boot mode, user program mode, user boot mode, and programmer mode is shown in table 14.1. Table 14.1 Comparison of Programming Modes
Boot mode Programming/ erasing environment Programming/ erasing enable MAT All erasure Block division erasure Program data transfer Reset initiation MAT Transition to user mode On-board User program mode On-board User boot mode On-board Programmer mode PROM programmer User MAT User boot MAT (Automatic)
User MAT User boot MAT (Automatic) *
1
User MAT
User MAT
×
From optional device via RAM User MAT From optional device via RAM User boot MAT*
2
From host via SCI Embedded program storage MAT Changing mode setting and reset
Via programmer
Changing FLSHE bit and FWE pin
Changing mode setting and reset
Notes: 1. All-erasure is performed. After that, the specified block can be erased. 2. Firstly, the reset vector is fetched from the embedded program storage MAT. After the flash memory related registers are checked, the reset vector is fetched from the user boot MAT.
• The user boot MAT can be programmed or erased only in boot mode and programmer mode. • The user MAT and user boot MAT are erased in boot mode. Then, the user MAT and user boot MAT can be programmed by means of the command method. However, the contents of the MAT cannot be read until this state. • There are some possible ways in this mode such as, writing only to the user boot MAT while rewriting the user MAT in user boot mode, or rewriting only the user MAT due to not using the user boot mode. The boot operation of the optional interface can be performed by the mode pin setting different from user program mode in user boot mode.
Rev. 2.00, 03/04, page 376 of 534
14.1.3
Flash MAT Configuration
This LSI's flash memory is configured by the 256-kbyte user MAT and 8-kbyte user boot MAT. The start address is allocated to the same address in the user MAT and user boot MAT. Therefore, when the program execution or data access is performed between two MATs, the MAT must be switched by using FMATS. The user MAT or user boot MAT can be read in all modes. However, the user boot MAT can be programmed only in boot mode and programmer mode.
Address H'000000 Address H'000000
Address H'001FFF
8 kbytes
256 kbytes
Address H'03FFFF
Figure 14.3 Flash Memory Configuration The size of the user MAT is different from that of the user boot MAT. An address which exceeds the size of the 8-kbyte user boot MAT should not be accessed. If the attempt is made, data is read as undefined value.
Rev. 2.00, 03/04, page 377 of 534
14.1.4
Block Division
The user MAT is divided into 64 kbytes (three blocks), 32 kbytes (one block), and 4 kbytes (eight blocks) as shown in figure 14.4. The user MAT can be erased in this divided-block units and the erase-block number of EB0 to EB11 is specified when erasing.
EB0 Erase unit: 4 kbytes H'000F80 EB1 Erase unit: 4 kbytes H'001000 H'000F81 H'001001 H'000F82 H'001002 –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– ¬Programming unit: 128 bytes→ –––––––––––––– H'000FFF H'00107F H'001FFF H'00207F
H'000000
H'000001
H'000002
¬Programming unit: 128 bytes→
H'00007F
H'001F80 EB2 Erase unit: 4 kbytes H'002000
H'001F81 H'002001
H'001F82 H'002002
H'002F80 EB3 Erase unit: 4 kbytes H'003F80 EB4 Erase unit: 32 kbytes H'00BF80 EB5 Erase unit: 4 kbytes H'00CF80 EB6 Erase unit: 4 kbytes H'00DF80 EB7 Erase unit: 4 kbytes H'00EF80 EB8 Erase unit: 4 kbytes H'00FF80 EB9 Erase unit: 64 kbytes H'01FF80 EB10 Erase unit: 64 kbytes H'02FF80 EB11 Erase unit: 64 kbytes H'03FF80 H'030000 H'020000 H'010000 H'00F000 H'00E000 H'00D000 H'00C000 H'004000 H'003000
H'002F81 H'003001
H'002F82 H'003002
H'002FFF H'00307F H'003FFF H'00407F H'00BFFF H'00C07F H'00CFFF H'00D07F H'00DFFF H'00E07F
H'003F81 H'004001 H'00BF81 H'00C001 H'00CF81 H'00D001 H'00DF81 H'00E001 H'00EF81 H'00F001
H'003F82 H'004002 H'00BF82 H'00C002 H'00CF82 H'00D002 H'00DF82 H'00E002 H'00EF82 H'00F002
H'00EFFF H'00F07F H'00FFFF H'01007F
H'00FF81 H'010001 H'01FF81 H'020001
H'00FF82 H'010002 H'01FF82 H'020002
H'01FFFF H'02007F H'02FFFF H'03007F
H'02FF81 H'030001 H'03FF81
H'02FF82 H'030002 H'03FF82
H'03FFFF
Figure 14.4 Block Division of User MAT
Rev. 2.00, 03/04, page 378 of 534
14.1.5
Programming/Erasing Interface
Programming/erasing is executed by downloading the on-chip program to the on-chip RAM and specifying the program address/data and erase block by using the interface register/parameter. The procedure program is made by the user in user program mode and user boot mode. An overview of the procedure is given as follows. For details, see section 14.4.2, User Program Mode.
Start user procedure program for programming/erasing.
Select on-chip program to be downloaded and specify the destination.
Download on-chip program by setting FKEY and SCO bits.
Initialization execution (downloaded program execution)
Programming (in 128-byte units) or erasing (in one-block units) (downloaded program execution)
No
Programming/erasing completed?
Yes
End user procedure program
Figure 14.5 Overview of User Procedure Program 1. Selection of on-chip program to be downloaded For programming/erasing execution, the FWE pin must be set to 1 to transition to user program mode. This LSI has programming/erasing programs which can be downloaded to the on-chip RAM. The on-chip program to be downloaded is selected by setting the corresponding bits in the programming/erasing interface register. The address of the programming destination is specified by the flash transfer destination address register (FTDAR).
Rev. 2.00, 03/04, page 379 of 534
2. Download of on-chip program The on-chip program is automatically downloaded by setting the flash key register (FKEY) and the SCO bit in the flash control register (FCCS), which are programming/erasing interface registers. The flash memory is replaced to the embedded program storage area when downloading. Since the flash memory cannot be read when programming/erasing, the procedure program, which is working from download to completion of programming/erasing, must be executed in the space other than the flash memory to be programmed/erased (for example, on-chip RAM). Since the result of download is returned to the programming/erasing interface parameter, whether the normal download is executed or not can be confirmed. 3. Initialization of programming/erasing The operating frequency is set before execution of programming/erasing. This setting is performed by using the programming/erasing interface parameter. 4. Programming/erasing execution For programming/erasing execution, the FWE pin must be set to 1 to transition to user program mode. The program data/programming destination address is specified in 128-byte units when programming. The block to be erased is specified in erase-block units when erasing. These specifications are set by using the programming/erasing interface parameter and the onchip program is initiated. The on-chip program is executed by using the JSR or BSR instruction and performing the subroutine call of the specified address in the on-chip RAM. The execution result is returned to the programming/erasing interface parameter. The area to be programmed must be erased in advance when programming flash memory. All interrupts are prohibited during programming and erasing. Interrupts must be masked within the user system. 5. When programming/erasing is executed consecutively When the processing is not ended by the 128-byte programming or one-block erasure, the program address/data and erase-block number must be updated and consecutive programming/erasing is required. Since the downloaded on-chip program is left in the on-chip RAM after the processing, download and initialization are not required when the same processing is executed consecutively.
Rev. 2.00, 03/04, page 380 of 534
14.2
Input/Output Pins
Table 14.2 shows the flash memory pin configuration. Table 14.2 Pin Configuration
Pin Name RES FWE MD2 MD1 TxD0 RxD0 Input/Output Input Input Input Input Output Input Function Reset Flash memory programming/erasing enable pin Sets operating mode of this LSI Sets operating mode of this LSI Serial transmit data output (used in boot mode) Serial receive data input (used in boot mode)
14.3
Register Descriptions
The registers/parameters which control flash memory are shown in the following. • • • • • • • • • • • • • Flash code control status register (FCCS) Flash program code select register (FPCS) Flash erase code select register (FECS) Flash key code register (FKEY) Flash MAT select register (FMATS) Flash transfer destination address register (FTDAR) RAM emulation register (RAMER) Download pass and fail result (DPFR) Flash pass and fail result (FPFR) Flash multipurpose address area (FMPAR) Flash multipurpose data destination area (FMPDR) Flash erase Block select (FEBS) Flash program and erase frequency control (FPEFEQ)
There are several operating modes for accessing flash memory, for example, read mode/program mode. There are two memory MATs: user MAT and user boot MAT. The dedicated registers/parameters are allocated for each operating mode and MAT selection. The correspondence of operating modes and registers/parameters for use is shown in table 14.3.
Rev. 2.00, 03/04, page 381 of 534
Table 14.3 Register/Parameter and Target Mode
Download FCCS Programming/ Erasing Interface FPCS Register FECS FKEY FMATS FTDAR Programming/ DPFR Erasing Interface FPFR Parameter FPEFEQ FUBRA FMPAR FMPDR FEBS ProgramInitialization ming *1 *1 Erasure Read *2
Notes: 1. The setting is required when programming or erasing user MAT in user boot mode. 2. The setting may be required according to the combination of initiation mode and read target MAT.
14.3.1
Programming/Erasing Interface Register
The programming/erasing interface registers are as described below. They are all 8-bit registers that can be accessed in byte. These registers are initialized at a reset or in hardware standby mode. • Flash Code Control and Status Register (FCCS) FCCS is configured by bits which request the monitor of the FWE pin state and error occurrence during programming or erasing flash memory and the download of on-chip program.
Bit 7 Initial Bit Name Value FWE 1/0 R/W R Description Flash Program Enable Monitors the signal level input to the FWE pin. 0: A low level signal is input to the FWE pin. (Hardware protection state) 1: A high level signal is input to the FWE pin. 6, 5 All 0 R/W Reserved The initial value should not be changed.
Rev. 2.00, 03/04, page 382 of 534
Bit 4
Initial Bit Name Value FLER 0
R/W R
Description Flash Memory Error Indicates an error occurs during programming and erasing flash memory. When FLER is set to 1, flash memory enters the error protection state. When FLER is set to 1, high voltage is applied to the internal flash memory. To reduce the damage to flash memory, the reset must be released after the reset period of 100 µs which is longer than normal. 0: Flash memory operates normally. Programming/erasing protection for flash memory (error protection) is invalid. [Clearing condition] • At a reset or in hardware standby mode 1: An error occurs during programming/erasing flash memory. Programming/erasing protection for flash memory (error protection) is valid. [Setting conditions] • • When an interrupt, such as NMI, occurs during programming/erasing flash memory. When the flash memory is read during programming/erasing flash memory (including a vector read or an instruction fetch). When the SLEEP instruction is executed during programming/erasing flash memory (including software-standby mode) When a bus master other than the CPU, such as the DMAC, gets bus mastership during programming/erasing flash memory.
•
•
Rev. 2.00, 03/04, page 383 of 534
Bit 3
Initial Bit Name Value WEINTE 0
R/W R/W
Description Program/Erase Enable Modifies the space for the interrupt vector table, when interrupt vector data is not read successfully during programming/erasing flash memory or switching between a user MAT and a user boot MAT. When this bit is set to 1, interrupt vector data is read from address spaces H'FF8000 to H'FF807F (on-chip RAM space), instead of from address spaces H'000000 to H'00017F (up to vector number 31). Therefore, make sure to set the vector table in the on-chip RAM space before setting this bit to 1. The interrupt exception handling on and after vector number 32 should not be used because the correct vector is not read, resulting in the CPU runaway. 0: The space for the interrupt vector table is not modified. When interrupt vector data is not read successfully, the operation for the interrupt exception handling cannot be guaranteed. An occurrence of any interrupts should be masked. 1: The space for the interrupt vector table is modified. Even when interrupt vector data is not read successfully, the interrupt exception handling up to vector number 31 is enabled.
2, 1
All 0
R/W
Reserved The initial value should not be changed.
Rev. 2.00, 03/04, page 384 of 534
Bit 0
Initial Bit Name Value SCO 0
R/W (R)/W*
Description Source Program Copy Operation Requests the on-chip programming/erasing program to be downloaded to the on-chip RAM. When this bit is set to 1, the on-chip program which is selected by FPCS/FECS is automatically downloaded in the on-chip RAM specified by FTDAR. In order to set this bit to 1, H'A5 must be written to FKEY and this operation must be executed in the on-chip RAM. Four NOP instructions must be executed immediately after setting this bit to 1. Since this bit is cleared to 0 when download is completed, this bit cannot be read as 1. All interrupts must be disabled. This should be made in the user system. 0:Download of the on-chip programming/erasing program to the on-chip RAM is not executed. [Clearing condition] When download is completed 1: Request that the on-chip programming/erasing program is downloaded to the on-chip RAM is occurred. [Setting conditions] When all of the following conditions are satisfied and 1 is set to this bit • H'A5 is written to FKEY • During execution in the on-chip RAM
Note: * This bit is a write only bit. This bit is always read as 0.
Rev. 2.00, 03/04, page 385 of 534
• Flash Program Code Select Register (FPCS) FPCS selects the on-chip programming program to be downloaded.
Bit 7 to 1 0 Initial Bit Name Value PPVS All 0 0 R/W R/W R/W Description Reserved The initial value should not be changed. Program Pulse Verify Selects the programming program. 0: On-chip programming program is not selected. [Clearing condition] When transfer is completed 1: On-chip programming program is selected.
• Flash Erase Code Select Register (FECS) FECS selects download of the on-chip erasing program.
Bit 7 to 1 0 Initial Bit Name Value EPVB All 0 0 R/W R/W R/W Description Reserved The initial value should not be changed. Erase Pulse Verify Block Selects the erasing program. 0: On-chip erasing program is not selected. [Clearing condition] When transfer is completed 1: On-chip erasing program is selected.
Rev. 2.00, 03/04, page 386 of 534
• Flash Key Code Register (FKEY) FKEY is a register for software protection that enables download of on-chip program and programming/erasing of flash memory. Before setting the SCO bit to 1 in order to download onchip program or executing the downloaded programming/erasing program, these processing cannot be executed if the key code is not written.
Bit 7 6 5 4 3 2 1 0 Bit Name K7 K6 K5 K4 K3 K2 K1 K0 Initial Value 0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description Key Code Only when H'A5 is written, writing to the SCO bit is valid. When the value other than H'A5 is written to FKEY, 1 cannot be set to the SCO bit. Therefore downloading to the on-chip RAM cannot be executed. Only when H'5A is written, programming/erasing can be executed. Even if the on-chip programming/erasing program is executed, the flash memory cannot be programmed or erased when the value other than H'5A is written to FKEY. H'A5: Writing to the SCO bit is enabled. (The SCO bit cannot be set by the value other than H'A5.) H'5A: Programming/erasing is enabled. (The value other than H'A5 is in software protection state.) H'00: Initial value
Rev. 2.00, 03/04, page 387 of 534
• Flash MAT Select Register (FMATS) FMATS specifies whether user MAT or user boot MAT is selected.
Bit 7 6 5 4 3 2 1 0 Bit Name MS7 MS6 MS5 MS4 MS3 MS2 MS1 MS0 Initial Value 0/1* 0 0/1* 0 0/1* 0 0/1* 0 R/W R/W R/W R/W R/W R/W R/W R/W R/W Description MAT Select These bits are in user-MAT selection state when the value other than H'AA is written and in user-boot-MAT selection state when H'AA is written. The MAT is switched by writing the value in FMATS. When the MAT is switched, follow section 14.6, Switching between User MAT and User Boot MAT. (The user boot MAT cannot be programmed in user program mode if user boot MAT is selected by FMATS. The user boot MAT must be programmed in boot mode or in programmer mode.) H'AA: The user boot MAT is selected (in user-MAT selection state when the value of these bits are other than H'AA) Initial value when these bits are initiated in user boot mode. H'00: Initial value when these bits are initiated in a mode except for user boot mode (in user-MAT selection state) [Programmable condition] These bits are in the execution state in the on-chip RAM. Note: * Set to 1 when in user boot mode, otherwise set to 0.
Rev. 2.00, 03/04, page 388 of 534
• Flash Transfer Destination Address Register (FTDAR) FTDAR specifies the on-chip RAM address where an on-chip program is downloaded. This register must be specified before setting the SCO bit in FCCS to 1.
Bit 7 Bit Name TDER Initial Value 0 R/W R/W Description Transfer Destination Address Setting Error This bit is set to 1 when the address specified by bits TDA6 to TDA0, which is the start address where an onchip program is downloaded, is over the range. Whether or not the address specified by bits TDA6 to TDA0 is within the range of H'00 to H'03 is determined when an on-chip program is downloaded by setting the SCO bit in FCCS to 1. Make sure that this bit is cleared to 0 and the value specified by bits TDA6 to TDA0 is within the range of H'00 to H'03 before setting the SCO bit to 1. 0: The value specified by bits TDA6 to TDA0 is within the range. 1: The value specified by bits TDA6 to TDA0 is over the range (H'04 to H'FF) and download is stopped. 6 5 4 3 2 1 0 TDA6 TDA5 TDA4 TDA3 TDA2 TDA1 TDA0 0 0 0 0 0 0 0 R/W R/W R/W R/W R/W R/W R/W Transfer Destination Address Specifies the start address where an on-chip program is downloaded. A value from H'00 to H'03 can be specified as the download start address in the on-chip RAM. H'00: H'FF7000 is specified as the download start address. H'01: H'FFB000 is specified as the download start address. H'02: H'FFD000 is specified as the download start address. H'03: H'FFE800 is specified as the download start address. H'04 to H'FF: Setting prohibited. Specifying this value sets the TDRE bit to 1 during downloading and stops the download.
Rev. 2.00, 03/04, page 389 of 534
• RAM Emulation Register (RAMER) RAMER specifies the area of flash memory to be overlapped with part of RAM when emulating realtime flash memory programming. RAMER is initialized to H'00 by a power-on reset and in hardware standby mode. It is not initialized in software standby mode. RAMER settings should be made in user mode or user program mode. Flash memory area divisions are shown in table 14.4. To ensure correct operation of the emulation function, the ROM for which RAM emulation is performed should not be accessed immediately after this register has been modified. Normal execution of an access immediately after register modification is not guaranteed.
Bit 7 to 4 Initial Bit Name Value All 0 R/W Description Reserved These bits are always read as 0. The write value should always be 0. 3 RAMS 0 R/W RAM Select Specifies selection or non-selection of flash memory emulation in RAM. When RAMS is 1, all flash memory blocks are program/erase-protected. 0: Emulation not selected Program/erase-protection of all flash memory blocks is disabled. 1: Emulation selected Program/erase-protection of all flash memory blocks is enabled. 2 1 0 RAM2 RAM1 RAM0 0 0 0 R/W R/W R/W Flash Memory Area Selection These bits are used together with bit 3 to select the flash memory area to be overlapped with RAM (see table 14.4).
Rev. 2.00, 03/04, page 390 of 534
Table 14.4 Flash Memory Area Divisions
RAM Area H'000000 to H'000FFF H'001000 to H'001FFF H'002000 to H'002FFF H'003000 to H'003FFF H'004000 to H'004FFF H'005000 to H'005FFF H'006000 to H'006FFF H'007000 to H'007FFF Block Name EB0 (4 kbytes) EB1 (4 kbytes) EB2 (4 kbytes) EB3 (4 kbytes) EB4 (4 kbytes) EB5 (4 kbytes) EB6 (4 kbytes) EB7 (4 kbytes) RAM2 0 0 0 0 1 1 1 1 RAM1 0 0 1 1 0 0 1 1 RAM0 0 1 0 1 0 1 0 1
14.3.2
Programming/Erasing Interface Parameter
The programming/erasing interface parameter specifies the operating frequency, storage place for program data, programming destination address, and erase block and exchanges the processing result for the downloaded on-chip program. This parameter uses the general registers of the CPU (ER0 and ER1) or the on-chip RAM area. The initial value is undefined at a reset or in hardware standby mode. When download, initialization, or on-chip program is executed, registers of the CPU except for R0L are stored. The return value of the processing result is written in R0L. Since the stack area is used for storing the registers except for R0L, the stack area must be saved at the processing start. (A maximum size of a stack area to be used is 132 bytes.) The programming/erasing interface parameter is used in the following four items. 1. 2. 3. 4. Download control Initialization before programming or erasing Programming Erasing
These items use different parameters. The correspondence table is shown in table 14.5. The meaning of the bits in FPFR varies in each processing program: initialization, programming, or erasure. For details, see descriptions of FPFR for each process.
Rev. 2.00, 03/04, page 391 of 534
Table 14.5 Parameters and Target Modes
Name of Parameter Download pass and fail result Abbreviation DPFR Down Load Initialization Programming Erasure R/W R/W R/W Initial Value Undefined Undefined Undefined Allocation On-chip RAM* R0L of CPU R0 of CPU
Flash pass and fail FPFR result Flash programming/ erasing frequency control FPEFEQ
R/W
Flash multipurpose FMPAR address area Flash multipurpose FMPDR data destination area Flash erase block select FEBS
R/W R/W
Undefined Undefined
On-chip RAM On-chip RAM R0L of CPU
R/W
Undefined
Note:
*
A single byte of the start address to download an on-chip program, which is specified by FTDAR
Rev. 2.00, 03/04, page 392 of 534
Download Control: The on-chip program is automatically downloaded by setting the SCO bit to 1. The on-chip RAM area to be downloaded is the 2-kbyte area starting from the address specified by FTDAR. Download control is set by the program/erase interface registers, and the DPFR parameter indicates the return value. a Download pass/fail result parameter (DPFR: single byte of start address specified by FTDAR) This parameter indicates the return value of the download result. The value of this parameter can be used to determine if downloading is executed or not. Since the confirmation whether the SCO bit is set to 1 is difficult, the certain determination must be performed by writing the single byte of the start address specified by FTDAR to the value other than the return value of download (for example, H'FF) before the download start (before setting the SCO bit to 1).
Bit 7 to 3 2 Initial Bit Name Value SS R/W R/W Description Unused Return 0 Source Select Error Detect Only one type for the on-chip program which can be downloaded can be specified. When more than two types of the program are selected, the program is not selected, or the program is selected without mapping, error is occurred. 0: Download program can be selected normally 1: Download error is occurred (multi-selection or program which is not mapped is selected) 1 FK R/W Flash Key Register Error Detect Returns the check result whether the value of FKEY is set to H'A5. 0: KEY setting is normal (FKEY = H'A5) 1: Setting value of FKEY becomes error (FKEY = value other than H'A5) 0 SF R/W Success/Fail Returns the result whether download is ended normally or not. The determination result whether program that is downloaded to the on-chip RAM is read back and then transferred to the on-chip RAM is returned. 0: Downloading on-chip program is ended normally (no error) 1: Downloading on-chip program is ended abnormally (error occurs)
Rev. 2.00, 03/04, page 393 of 534
Programming/Erasing Initialization: The on-chip programming/erasing program to be downloaded includes the initialization program. The specified period pulse must be applied when programming or erasing. The specified pulse width is made by the method in which wait loop is configured by the CPU instruction. The operating frequency of the CPU must be set. The initial program is set as a parameter of the programming/erasing program which has downloaded these settings. a Flash programming/erasing frequency parameter (FPEFEQ: general register ER0 of CPU) This parameter sets the operating frequency of the CPU. The settable range of the operating frequency in this LSI is 10 to 33 MHz.
Bit Initial Bit Name Value R/W R/W Description Unused This bit should be cleared to 0. 15 to 0 F15 to F0 Frequency Set Set the operating frequency of the CPU. With the PLL multiplication function, set the frequency multiplied. The setting value must be calculated as the following methods. 1. The operating frequency which is shown in MHz units must be rounded in a number to three decimal places and be shown in a number of two decimal places. 2. The value multiplied by 100 is converted to the binary digit and is written to the FPEFEQ parameter (general register ER0). For example, when the operating frequency of the CPU is 33.000 MHz, the value is as follows. 1. The number to three decimal places of 33.000 is rounded and the value is thus 33.00. 2. The formula that 33.00 × 100 = 3300 is converted to the binary digit and B'0000,1100,1110,0100 (H'0CE4) is set to ER0.
31 to 16
Rev. 2.00, 03/04, page 394 of 534
b Flash pass/fail parameter (FPFR: general register R0L of CPU) This parameter indicates the return value of the initialization result.
Bit 7 to 2 1 Initial Bit Name Value FQ R/W R/W Description Unused Return 0 Frequency Error Detect Returns the check result whether the specified operating frequency of the CPU is in the range of the supported operating frequency. 0: Setting of operating frequency is normal 1: Setting of operating frequency is abnormal 0 SF R/W Success/Fail Indicates whether initialization is completed normally. 0: Initialization is ended normally (no error) 1: Initialization is ended abnormally (error occurs)
Programming Execution: When flash memory is programmed, the programming destination address on the user MAT must be passed to the programming program in which the program data is downloaded. 1. The start address of the programming destination on the user MAT must be stored in a general register ER1. This parameter is called as flash multipurpose address area parameter (FMPAR). Since the program data is always in units of 128 bytes, the lower eight bits (A7 to A0) must be H'00 or H'80 as the boundary of the programming start address on the user MAT. 2. The program data for the user MAT must be prepared in the consecutive area. The program data must be in the consecutive space which can be accessed by using the MOV.B instruction of the CPU and in other than the flash memory space. When data to be programmed does not satisfy 128 bytes, the 128-byte program data must be prepared by filling with the dummy code H'FF. The start address of the area in which the prepared program data is stored must be stored in a general register ER0. This parameter is called as flash multipurpose data destination area parameter (FMPDR). For details on the program processing procedure, see section 14.4.2, User Program Mode.
Rev. 2.00, 03/04, page 395 of 534
a Flash multipurpose address area parameter (FMPAR: general register ER1 of CPU) This parameter stores the start address of the programming destination on the user MAT. When the address in the area other than flash memory space is set, an error occurs. The start address of the programming destination must be at the 128-byte boundary. If this boundary condition is not satisfied, an error occurs. The error occurrence is indicated by the WA bit (bit 1) in FPFR.
Bit 31 to 0 Initial Bit Name Value MOA31 to MOA0 R/W R/W Description Store the start address of the programming destination on the user MAT. The consecutive 128-byte programming is executed starting from the specified start address of the user MAT. Therefore, the specified programming start address becomes a 128-byte boundary and MOA6 to MOA0 are always 0.
b Flash multipurpose data destination parameter (FMPDR: general register ER0 of CPU): This parameter stores the start address in the area which stores the data to be programmed in the user MAT. When the storage destination of the program data is in flash memory, an error occurs. The error occurrence is indicated by the WD bit in FPFR.
Bit 31 to 0 Initial Bit Name Value MOD31 to MOD0 R/W R/W Description Store the start address of the area which stores the program data for the user MAT. The consecutive 128byte data is programmed to the user MAT starting from the specified start address.
c Flash pass/fail parameter (FPFR: general register R0L of CPU) This parameter indicates the return value of the program processing result.
Bit 7 Initial Bit Name Value R/W Description Unused Return 0.
Rev. 2.00, 03/04, page 396 of 534
Bit 6
Initial Bit Name Value MD
R/W R/W
Description Programming Mode Related Setting Error Detect Returns the check result that a high level signal is input to the FWE pin and the error protection state is not entered. When the low level signal is input to the FWE pin or the error protection state is entered, 1 is written to this bit. The state can be confirmed with the FWE and FLER bits in FCCS. For conditions to enter the error protection state, see section 14.5.3, Error Protection. 0: FWE and FLER settings are normal (FWE = 1, FLER = 0) 1: Programming cannot be performed (FWE = 0 or FLER = 1)
5
EE
R/W
Programming Execution Error Detect 1 is returned to this bit when the specified data could not be written because the user MAT was not erased. If this bit is set to 1, there is a high possibility that the user MAT is partially rewritten. In this case, after removing the error factor, erase the user MAT. If FMATS is set to H'AA and the user boot MAT is selected, an error occurs when programming is performed. In this case, both the user MAT and user boot MAT are not rewritten. Programming of the user boot MAT should be performed in boot mode or programmer mode. 0: Programming has ended normally 1: Programming has ended abnormally (programming result is not guaranteed)
4
FK
R/W
Flash Key Register Error Detect Returns the check result of the value of FKEY before the start of the programming processing. 0: FKEY setting is normal (FKEY = H'5A) 1: FKEY setting is error (FKEY = value other than H'5A)
3 2
WD
R/W
Unused Returns 0. Write Data Address Detect When the address in the flash memory area is specified as the start address of the storage destination of the program data, an error occurs. 0: Setting of write data address is normal 1: Setting of write data address is abnormal
Rev. 2.00, 03/04, page 397 of 534
Bit 1
Initial Bit Name Value WA
R/W R/W
Description Write Address Error Detect When the following items are specified as the start address of the programming destination, an error occurs. • • When the programming destination address in the area other than flash memory is specified When the specified address is not in a 128-byte boundary. (The lower eight bits of the address are other than H'00 and H'80.)
0: Setting of programming destination address is normal 1: Setting of programming destination address is abnormal 0 SF R/W Success/Fail Indicates whether the program processing is ended normally or not. 0: Programming is ended normally (no error) 1: Programming is ended abnormally (error occurs)
Erasure Execution: When flash memory is erased, the erase-block number on the user MAT must be passed to the erasing program which is downloaded. This is set to the FEBS parameter (general register ER0). One block is specified from the block number 0 to 11. For details on the erasing processing procedure, see section 14.4.2, User Program Mode. a Flash erase block select parameter (FEBS: general register ER0 of CPU) This parameter specifies the erase-block number. The several block numbers cannot be specified.
Rev. 2.00, 03/04, page 398 of 534
Bit 31 to 8 7 6 5 4 3 2 1 0
Initial Bit Name Value EB7 EB6 EB5 EB4 EB3 EB2 EB1 EB0
R/W R/W R/W R/W R/W R/W R/W R/W R/W
Description Unused These bits should be cleared to H'0. Erase Block Set the erase-block number in the range from 0 to 11. 0 corresponds to the EB0 block and 11 corresponds to the EB11 block. An error occurs when the number other than 0 to 11 is set.
b Flash pass/fail parameter (FPFR: general register R0L of CPU) This parameter returns value of the erasing processing result.
Bit 7 6 Initial Bit Name Value MD R/W R/W Description Unused Return 0. Programming Mode Related Setting Error Detect Returns the check result that a high level signal is input to the FWE pin and the error protection state is not entered. When the low level signal is input to the FWE pin or the error protection state is entered, 1 is written to this bit. The state can be confirmed with the FWE and FLER bits in FCCS. For conditions to enter the error protection state, see section 14.5.3, Error Protection. 0: FWE and FLER settings are normal (FWE = 1, FLER = 0) 1: Programming cannot be performed (FWE = 0 or FLER = 1)
Rev. 2.00, 03/04, page 399 of 534
Bit 5
Bit Name EE
Initial Value
R/W R/W
Description Erasure Execution Error Detect 1 is returned to this bit when the user MAT could not be erased or when flash-memory related register settings are partially changed. If this bit is set to 1, there is a high possibility that the user MAT is partially erased. In this case, after removing the error factor, erase the user MAT. If FMATS is set to H'AA and the user boot MAT is selected, an error occurs when erasure is performed. In this case, both the user MAT and user boot MAT are not erased. Erasing of the user boot MAT should be performed in boot mode or programmer mode. 0: Erasure has ended normally 1: Erasure has ended abnormally (erasure result is not guaranteed)
4
FK
R/W
Flash Key Register Error Detect Returns the check result of FKEY value before start of the erasing processing. 0: FKEY setting is normal (FKEY = H'5A) 1: FKEY setting is error (FKEY = value other than H'5A)
3
EB
R/W
Erase Block Select Error Detect Returns the check result whether the specified eraseblock number is in the block range of the user MAT. 0: Setting of erase-block number is normal 1: Setting of erase-block number is abnormal
2, 1 0
SF
R/W
Unused Return 0. Success/Fail Indicates whether the erasing processing is ended normally or not. 0: Erasure is ended normally (no error) 1: Erasure is ended abnormally (error occurs)
Rev. 2.00, 03/04, page 400 of 534
14.4
On-Board Programming Mode
When the pin is set in on-board programming mode and the reset start is executed, the on-board programming state that can program/erase the on-chip flash memory is entered. On-board programming mode has three operating modes: boot mode, user program mode, and user boot mode. For details of the pin setting for entering each mode, see table 14.6. For details of the state transition of each mode for flash memory, see figure 14.2. Table 14.6 Setting On-Board Programming Mode
Mode Setting Boot mode User program mode User boot mode FWE 1 1 1 MD2 0 1 0 MD1 0 1 0 NMI 1 0/1 0
14.4.1
Boot Mode
Boot mode executes programming/erasing user MAT and user boot MAT by means of the control command and program data transmitted from the host using the on-chip SCI. The tool for transmitting the control command and program data must be prepared in the host. The SCI communication mode is set to asynchronous mode. When reset start is executed after this LSI’s pin is set in boot mode, the boot program in the microcomputer is initiated. After the SCI bit rate is automatically adjusted, the communication with the host is executed by means of the control command method. The system configuration diagram in boot mode is shown in figure 14.6. For details on the pin setting in boot mode, see table 14.6. The NMI and other interrupts are ignored in boot mode. However, the NMI and other interrupts should be disabled in the user system.
Rev. 2.00, 03/04, page 401 of 534
This LSI
Host
Boot Control command, program data programming tool and program data
Reply response
Control command, analysis execution software (on-chip)
Flash memory
RxD0 On-chip SCI TxD0
On-chip RAM
Figure 14.6 System Configuration in Boot Mode SCI Interface Setting by Host: When boot mode is initiated, this LSI measures the low period of asynchronous SCI-communication data (H'00), which is transmitted consecutively by the host. The SCI transmit/receive format is set to 8-bit data, 1 stop bit, and no parity. This LSI calculates the bit rate of transmission by the host by means of the measured low period and transmits the bit adjustment end sign (1 byte of H'00) to the host. The host must confirm that this bit adjustment end sign (H'00) has been received normally and transmits 1 byte of H'55 to this LSI. When reception is not executed normally, boot mode is initiated again (reset) and the operation described above must be executed. The bit rate between the host and this LSI is not matched by the bit rate of transmission by the host and system clock frequency of this LSI. To operate the SCI normally, the transfer bit rate of the host must be set to 4,800 bps, 9,600 bps, or 19,200 bps. The system clock frequency, which can automatically adjust the transfer bit rate of the host and the bit rate of this LSI, is shown in table 14.7. Boot mode must be initiated in the range of this system clock.
Start bit
D0
D1
D2
D3
D4
D5
D6
D7
Stop bit
Measure low period (9 bits) (data is H'00)
High period of at least 1 bit
Figure 14.7 Automatic-Bit-Rate Adjustment Operation of SCI
Rev. 2.00, 03/04, page 402 of 534
Table 14.7 System Clock Frequency for Automatic-Bit-Rate Adjustment by This LSI
Bit Rate of Host 4,800 bps 9,600 bps 19,200 bps System Clock Frequency 10 to 33 MHz 10 to 33 MHz 10 to 33 MHz
State Transition Diagram: The overview of the state transition diagram after boot mode is initiated is shown in figure 14.8. 1. Bit rate adjustment After boot mode is initiated, the bit rate of the SCI interface is adjusted with that of the host. 2. Waiting for inquiry set command For inquiries about user-MAT size and configuration, MAT start address, and support state, the required information is transmitted to the host. 3. Automatic erasure of all user MAT and user boot MAT After inquiries have finished, all user MAT and user boot MAT are automatically erased. 4. Waiting for programming/erasing command When the program preparation notice is received, the state for waiting program data is entered. The programming start address and program data must be transmitted following the programming command. When programming is finished, the programming start address must be set to H'FFFFFFFF and transmitted. Then the state for waiting program data is returned to the state of programming/erasing command wait. When the erasure preparation notice is received, the state for waiting erase-block data is entered. The erase-block number must be transmitted following the erasing command. When the erasure is finished, the erase-block number must be set to H'FF and transmitted. Then the state for waiting erase-block data is returned to the state for waiting programming/erasing command. The erasure must be used when the specified block is programmed without a reset start after programming is executed in boot mode. When programming can be executed by only one operation, all blocks are erased before the state for waiting programming/erasing/other command is entered. The erasing operation is not required. There are many commands other than programming/erasing. Examples are sum check, blank check (erasure check), and memory read of the user MAT/user boot MAT and acquisition of current status information. Note that memory read of the user MAT/user boot MAT can only read the programmed data after all user MAT/user boot MAT has automatically been erased.
Rev. 2.00, 03/04, page 403 of 534
(Bit rate adjustment) H'00.......H'00 reception H'00 transmission (adjustment completed)
Boot mode initiation (reset by boot mode)
Bit rate adjustment
H'55 rece ption
1.
2.
Wait for inquiry setting command
Inquiry command reception
Inquiry command response
Processing of inquiry setting command
3.
All user MAT and user boot MAT erasure
Read/check command reception Command response
4.
Wait for programming/erasing command
Processing of read/check command
(Erasure selection command reception) (Program end notice) (Erasure end selection command reception) (Program command reception) (Program data transmission) (Erase-block specification)
Wait for erase-block data
Wait for program data
Figure 14.8 Overview of Boot Mode State Transition Diagram
Rev. 2.00, 03/04, page 404 of 534
14.4.2
User Program Mode
The user MAT can be programmed/erased in user program mode. (The user boot MAT cannot be programmed/erased.) Programming/erasing is executed by downloading the program in the microcomputer. The overview flow is shown in figure 14.9. High voltage is applied to internal flash memory during the programming/erasing processing. Therefore, transition to reset or hardware standby must not be executed. Doing so may damage or destroy flash memory. If reset is executed accidentally, reset must be released after the reset input period of 100 µs which is longer than normal.
Programming/erasing start
1. Make sure that the program data will not overlap the download destination specified by FTDAR..
When programming, program data is prepared
2. The FWE bit is set to 1 by inputting a high level signal to the FWE pin. 3. Programming/erasing is executed only in the on-chip RAM. However, if program data is in a consecutive area and can be accessed by the MOV.B instruction of the CPU like RAM or ROM, the program data can be in an external space. 4. After programming/erasing is finished, input a low level signal to the FWE pin and transfer to the hardware protection state.
Programming/erasing procedure program is transferred to the on-chip RAM and executed
Programming/erasing end
Figure 14.9 Programming/Erasing Overview Flow
Rev. 2.00, 03/04, page 405 of 534
On-chip RAM Address Map when Programming/Erasing is Executed: Parts of the procedure program that are made by the user, like download request, programming/erasing procedure, and determination of the result, must be executed in the on-chip RAM. The on-chip program that is to be downloaded is all in the on-chip RAM. Note that area in the on-chip RAM must be controlled so that these parts do not overlap. Figure 14.10 shows the program area to be downloaded.
Area that can be used by user DPFR (Return value: 1 byte) FTDAR setting
Address
RAMTOP
Area to be downloaded (Size : 2 kbytes) Unusable area in programming/erasing processing period
System use area (15 bytes)
Programming/erasing program entry Initialization program entry Initialization + programming program or Initialization + erasing program Area that can be used by user FTDAR setting + 2 kbytes RAMEND FTDAR setting + 16 FTDAR setting + 32
Figure 14.10 RAM Map When Programming/Erasing is Executed
Rev. 2.00, 03/04, page 406 of 534
Programming Procedure in User Program Mode: The procedures for download, initialization, and programming are shown in figure 14.11.
Start programming procedure program Select on-chip program to be downloaded and specify download destination by FTDAR Set FKEY to H'A5
1 1. 2. 3. 4. 5.
No
Disable interrupts and bus master operation other than CPU Set FKEY to H'5A
9. 10.
Download
Set SCO to 1 and execute download Clear FKEY to 0
Programming
Set parameters to ER1 and ER0 (FMPAR and FMPDR) Programming JSR FTDAR setting + 16
11. 12. 13.
No
Clear FKEY and programming error processing
DPFR = 0? Yes
Set the FPEFEQ parameter
FPFR = 1? Yes No
Required data programming is completed?
Download error processing
6. 7. 8.
No
Initialization
Initialization JSR FTDAR setting + 32
14. 15.
Yes
Clear FKEY to 0 End programming procedure program
FPFR = 0? Yes
Initialization error processing
1
Figure 14.11 Programming Procedure The procedure program must be executed in an area other than the flash memory to be programmed. Especially the part where the SCO bit in FCCS is set to 1 for downloading must be executed in the on-chip RAM. The area that can be executed in the steps of the user procedure program (on-chip RAM, user MAT, and external space) is shown in section 14.4.4, Procedure Program and Storable Area for Programming Data. The following description assumes the area to be programmed on the user MAT is erased and program data is prepared in the consecutive area. When erasing is not executed, erasing is executed before writing. 128-byte programming is performed in one program processing. When more than 128-byte programming is performed, programming destination address/program data parameter is updated in 128-byte units and programming is repeated.
Rev. 2.00, 03/04, page 407 of 534
When less than 128-byte programming is performed, data must total 128 bytes by adding the invalid data. If the dummy data to be added is H'FF, the program processing period can be shortened. 1. Select the on-chip program to be downloaded and specify a download destination When the PPVS bit of FPCS is set to 1, the programming program is selected. Several programming/erasing programs cannot be selected at one time. If several programs are set, download is not performed and a download error is returned to the SS bit in DPFR. The start address of a download destination is specified by FTDAR. 2. Program H'A5 in FKEY If H'A5 is not written to FKEY for protection, 1 cannot be set to the SCO bit for download request. 3. 1 is set to the SCO bit of FCCS and then download is executed. To set 1 to the SCO bit, the following conditions must be satisfied. H'A5 is written to FKEY. The SCO bit writing is executed in the on-chip RAM. When the SCO bit is set to 1, download is started automatically. When the SCO bit is returned to the user procedure program, the SCO is cleared to 0. Therefore, the SCO bit cannot be confirmed to be 1 in the user procedure program. The download result can be confirmed only by the return value of DPFR. Before the SCO bit is set to 1, incorrect determination must be prevented by setting the one byte of the start address (to be used as DPFR) specified by FTDAR to a value other than the return value (H'FF). When download is executed, particular interrupt processing, which is accompanied by the bank switch as described below, is performed as an internal microcomputer processing. Four NOP instructions are executed immediately after the instructions that set the SCO bit to 1. The user-MAT space is switched to the on-chip program storage area. After the selection condition of the download program and the FTDAR setting are checked, the transfer processing to the on-chip RAM specified by FTDAR is executed. The SCO bit in FCCS is cleared to 0. The return value is set to the DPFR parameter. After the on-chip program storage area is returned to the user-MAT space, the user procedure program is returned. In the download processing, the values of general registers of the CPU are held. In the download processing, any interrupts are not accepted. However, interrupt requests are held. Therefore, when the user procedure program is returned, the interrupts occur. When the level-detection interrupt requests are to be held, interrupts must be input until the download is ended.
Rev. 2.00, 03/04, page 408 of 534
When hardware standby mode is entered during download processing, the normal download cannot be guaranteed in the on-chip RAM. Therefore, download must be executed again. Since a stack area of 128 bytes at the maximum is used, the area must be allocated before setting the SCO bit to 1. If a flash memory access by the DMAC signal is requested during downloading, the operation cannot be guaranteed. Therefore, an access request by the DMAC signal must not be generated. 4. FKEY is cleared to H'00 for protection. 5. The value of the DPFR parameter must be checked and the download result must be confirmed. Check the value of the DPFR parameter (one byte of start address of the download destination specified by FTDAR). If the value is H'00, download has been performed normally. If the value is not H'00, the source that caused download to fail can be investigated by the description below. If the value of the DPFR parameter is the same as before downloading (e.g. H'FF), the address setting of the download destination in FTDAR may be abnormal. In this case, confirm the setting of the TDER bit (bit 7) in FTDAR. If the value of the DPFR parameter is different from before downloading, check the SS bit (bit 2) and the FK bit (bit 1) in the DPFR parameter to ensure that the download program selection and FKEY setting were normal, respectively. 6. The operating frequency and user branch destination are set to the FPEFEQ and FUBRA parameters for initialization. The current frequency of the CPU clock is set to the FPEFEQ parameter (general register ER0). The settable range of the FPEFEQ parameter is 5 to 33 MHz. When the frequency is set to out of this range, an error is returned to the FPFR parameter of the initialization program and initialization is not performed. For details on the frequency setting, see the description in 14.3.2 (2) (a), Flash programming/erasing frequency parameter (FPEFEQ). 7. Initialization When a programming program is downloaded, the initialization program is also downloaded to the on-chip RAM. There is an entry point of the initialization program in the area from the start address specified by FTDAR + 32 bytes of the on-chip RAM. The subroutine is called and initialization is executed by using the following steps. MOV.L JSR NOP #DLTOP+32,ER2 @ER2 ; Set entry address to ER2 ; Call initialization routine
Rev. 2.00, 03/04, page 409 of 534
The general registers other than R0L are held in the initialization program. R0L is a return value of the FPFR parameter. Since the stack area is used in the initialization program, 128-byte stack area at the maximum must be allocated in RAM. Interrupts can be accepted during the execution of the initialization program. The program storage area and stack area in the on-chip RAM and register values must not be destroyed. 8. The return value in the initialization program, FPFR (general register R0L) is determined. 9. All interrupts and the use of a bus master (DMAC) other than the CPU are prohibited. The specified voltage is applied for the specified time when programming or erasing. If interrupts occur or the bus mastership is moved to other than the CPU during this time, the voltage for more than the specified time will be applied and flash memory may be damaged. Therefore, interrupts and bus mastership to the DMAC are prohibited. To prohibit the interrupt, bit 7 (I) in the condition code register (CCR) of the CPU should be set to B'1 in interrupt control mode 0 or bits 2 to 0 (I2 to I0) in the extend control register of the CPU should be set to B′111 in interrupt control mode 2. Then interrupts other than NMI are held and are not executed. The NMI interrupts must be masked within the user system. The interrupts that are held must be executed after all program processing. When the bus mastership is moved to the DMAC, the error protection state is entered. Therefore, taking bus mastership by the DMAC is prohibited. 10. FKEY must be set to H'5A and the user MAT must be prepared for programming. 11. The parameter which is required for programming is set. The start address of the programming destination of the user MAT (FMPAR) is set to general register ER1. The start address of the program data area (FMPDR) is set to general register ER0. Example of the FMPAR setting FMPAR specifies the programming destination address. When an address other than one in the user MAT area is specified, even if the programming program is executed, programming is not executed and an error is returned to the return value parameter FPFR. Since the unit is 128 bytes, the lower eight bits of the address must be H'00 or H'80 as the boundary of 128 bytes.
Rev. 2.00, 03/04, page 410 of 534
Example of the FMPDR setting When the storage destination of the program data is flash memory, even if the program execution routine is executed, programming is not executed and an error is returned to the FPFR parameter. In this case, the program data must be transferred to the on-chip RAM and then programming must be executed. 12. Programming There is an entry point of the programming program in the area from the start address specified by FTDAR + 16 bytes of the on-chip RAM. The subroutine is called and programming is executed by using the following steps. MOV.L JSR NOP #DLTOP+16,ER2 @ER2 ; Set entry address to ER2 ; Call programming routine
The general registers other than R0L are held in the programming program. R0L is a return value of the FPFR parameter. Since the stack area is used in the programming program, a stack area of 128 bytes at the maximum must be allocated in RAM. 13. The return value in the programming program, FPFR (general register R0L) is determined. 14. Determine whether programming of the necessary data has finished. If more than 128 bytes of data are to be programmed, specify FMPAR and FMPDR in 128byte units, and repeat steps 12 to 14. Increment the programming destination address by 128 bytes and update the programming data pointer correctly. If an address which has already been programmed is written to again, not only will a programming error occur, but also flash memory will be damaged. 15. After programming finishes, clear FKEY and specify software protection. If this LSI is restarted by a reset immediately after user MAT programming has finished, secure the reset period (period of RES = 0) of 100 µs which is longer than normal.
Rev. 2.00, 03/04, page 411 of 534
Erasing Procedure in User Program Mode: The procedures for download, initialization, and erasing are shown in figure 14.12.
Start erasing procedure program
1
Select on-chip program to be downloaded and specify download destination by FTDAR
1.
Disable interrupts and bus master operation other than CPU
Set FKEY to H'5A
Set FKEY to H'A5
Download
Set SCO to 1 and execute download
Set FEBS parameter
Erasing JSR FTDAR setting + 16
2. 3. 4.
No
Erasing
Clear FKEY to 0
DPFR = 0?
No
Download error processing
FPFR = 1 ?
Yes
Set the FPEFEQ parameter
Yes
No
Required block erasing is completed?
Clear FKEY and erasing error processing
Initialization
5. 6.
Initialization JSR FTDAR setting + 32
Yes
Clear FKEY to 0
FPFR = 0 ?
No Yes Initialization error processing
End erasing procedure program
1
Figure 14.12 Erasing Procedure The procedure program must be executed in an area other than the user MAT to be erased. Especially the part where the SCO bit in FCCS is set to 1 for downloading must be executed in the on-chip RAM. The area that can be executed in the steps of the user procedure program (on-chip RAM, user MAT, and external space) is shown in section 14.4.4, Procedure Program and Storable Area for Programming Data. For the downloaded on-chip program area, refer to the RAM map for programming/erasing in figure 14.10. A single divided block is erased by one erasing processing. For block divisions, refer to figure 14.4. To erase two or more blocks, update the erase block number and perform the erasing processing for each block.
Rev. 2.00, 03/04, page 412 of 534
1. Select the on-chip program to be downloaded Set the EPVB bit in FECS to 1. Several programming/erasing programs cannot be selected at one time. If several programs are set, download is not performed and a download error is reported to the SS bit in the DPFR parameter. Specify the start address of a download destination by FTDAR. The procedures to be carried out after setting FKEY, e.g. download and initialization, are the same as those in the programming procedure. For details, refer to Programming Procedure in User Program Mode in section 14.4.2, sub-section (2). The procedures after setting parameters for erasing programs are as follows: 2. Set the FEBS parameter necessary for erasure Set the erase block number of the user MAT in the flash erase block select parameter FEBS (general register ER0). If a value other than an erase block number of the user MAT is set, no block is erased even though the erasing program is executed, and an error is returned to the return value parameter FPFR. 3. Erasure Similar to as in programming, there is an entry point of the erasing program in the area from the start address of a download destination specified by FTDAR + 16 bytes of on-chip RAM. The subroutine is called and erasing is executed by using the following steps. MOV.L JSR NOP • • • #DLTOP+16,ER2 @ER2 ; Set entry address to ER2 ; Call erasing routine
The general registers other than R0L are held in the erasing program. R0L is a return value of the FPFR parameter. Since the stack area is used in the erasing program, a stack area of 128 bytes at the maximum must be allocated in RAM. 4. The return value in the erasing program, FPFR (general register R0L) is determined. 5. Determine whether erasure of the necessary blocks has completed. If more than one block is to be erased, update the FEBS parameter and repeat steps 2 to 5. Blocks that have already been erased can be erased again. 6. After erasure completes, clear FKEY and specify software protection. If this LSI is restarted by a reset immediately after user MAT erasure has completed, secure the reset period (period of RES = 0) of 100 µs which is longer than normal.
Rev. 2.00, 03/04, page 413 of 534
Erasing and Programming Procedure in User Program Mode: By changing the on-chip RAM address of the download destination in FTDAR, the erasing program and programming program can be downloaded to separate on-chip RAM areas. Figure 14.13 shows a repeating procedure of erasing and programming.
Start procedure program
Specify a download destination of erasing program by FTDAR
Erasing program download
1
Erase relevant block (execute erasing program)
Download erasing program
Erasing/ Programming
Initialize erasing program
Specify a download destination of programming program by FTDAR
Set FMPDR to program relevant block (execute programming program)
Programming program download
Confirm operation
Download programming program Initialize programming program
End ?
No
Yes
End procedure program
1
Figure 14.13 Repeating Procedure of Erasing and Programming In the above procedure, download and initialization are performed only once at the beginning. In this kind of operation, note the following: Be careful not to damage on-chip RAM with overlapped settings. In addition to the erasing program area and programming program area, areas for the user procedure programs, work area, and stack area are reserved in on-chip RAM. Do not make settings that will overwrite data in these areas. Be sure to initialize both the erasing program and programming program. Initialization by setting the FPEFEQ parameter must be performed for both the erasing program and the programming program. Initialization must be executed for both entry addresses: (download start address for erasing program) + 32 bytes and (download start address for programming program) + 32 bytes.
Rev. 2.00, 03/04, page 414 of 534
14.4.3
User Boot Mode
This LSI has user boot mode which is initiated with different mode pin settings than those in boot mode or user program mode. User boot mode is a user-arbitrary boot mode, unlike boot mode that uses the on-chip SCI. Only the user MAT can be programmed/erased in user boot mode. Programming/erasing of the user boot MAT is only enabled in boot mode or programmer mode. User Boot Mode Initiation: For the mode pin settings to start up user boot mode, see table 14.6. When the reset start is executed in user boot mode, the built-in check routine runs. The user MAT and user boot MAT states are checked by this check routine. While the check routine is running, NMI and all other interrupts cannot be accepted. Next, processing starts from the execution start address of the reset vector in the user boot MAT. At this point, H'AA is set to FMATS because the execution MAT is the user boot MAT. User MAT Programming in User Boot Mode: For programming the user MAT in user boot mode, additional processing made by setting FMATS is required: switching from user-boot-MAT selection state to user-MAT selection state, and switching back to user-boot-MAT selection state after programming completes. Figure 14.14 shows the procedure for programming the user MAT in user boot mode.
Rev. 2.00, 03/04, page 415 of 534
Start programming procedure program
Select on-chip program to be downloaded and specify download destination by FTDAR Set FKEY to H'A5
1
MAT switchover
Set FMATS to value other than H'AA to select user MAT
User-boot-MAT selection state
Download
Set SCO to 1 and execute download
Set FKEY to H'A5
User-MAT selection state
Clear FKEY to 0
DPFR = 0 ? Yes
Set parameter to ER0 and ER1 (FMPAR and FMPDR)
No
Programming
Programming JSR FTDAR setting + 16
FPFR = 0 ?
Download error processing
Initialization
Set the FPEFEQ and FUBRA parameters Initialization JSR FTDAR setting + 32
FPFR = 0 ?
No Yes Clear FKEY and programming error processing *
No
Required data programming is completed?
Yes
No
Clear FKEY to 0
Yes Initialization error processing
Disable interrupts and bus master operation other than CPU
Set FMATS to H'AA to select user boot MAT
End programming procedure program
MAT switchover
1
User-boot-MAT selection state
Note: * The MAT must be switched by FMATS to perform the programming error processing in the user boot MAT.
Figure 14.14 Procedure for Programming User MAT in User Boot Mode The difference between the programming procedures in user program mode and user boot mode is whether the MAT is switched or not as shown in figure 14.14. In user boot mode, the user boot MAT can be seen in the flash memory space with the user MAT hidden in the background. The user MAT and user boot MAT are switched only while the user MAT is being programmed. Because the user boot MAT is hidden while the user MAT is being programmed, the procedure program must be located in an area other than flash memory. After programming completes, switch the MATs again to return to the first state. MAT switching is enabled by writing a specific value to FMATS. However note that while the MATs are being switched, the LSI is in an unstable state, e.g. access to a MAT is not allowed until MAT switching is completed, and if an interrupt occurs, from which MAT the interrupt vector is read is undetermined. Perform MAT switching in accordance with the description in section 14.6, Switching between User MAT and User Boot MAT.
Rev. 2.00, 03/04, page 416 of 534
Except for MAT switching, the programming procedure is the same as that in user program mode. The area that can be executed in the steps of the user procedure program (on-chip RAM, user MAT, and external space) is shown in section 14.4.4, Procedure Program and Storable Area for Programming Data. User MAT Erasing in User Boot Mode: For erasing the user MAT in user boot mode, additional processing made by setting FMATS is required: switching from user-boot-MAT selection state to user-MAT selection state, and switching back to user-boot-MAT selection state after erasing completes. Figure 14.15 shows the procedure for erasing the user MAT in user boot mode.
Start erasing procedure program
Select on-chip program to be downloaded and specify download destination by FTDAR Set FKEY to H'A5
1
MAT switchover
Set FMATS to value other than H'AA to select user MAT
User-boot-MAT selection state
Download
Set SCO to 1 and execute download
Set FKEY to H'A5
User-MAT selection state
Clear FKEY to 0
DPFR = 0 ?
Set FEBS parameter
Programming JSR FTDAR setting + 16
FPFR = 0 ?
No
Yes
Download error processing
Erasing
Initialization
Set the FPEFEQ and FUBRA parameters Initialization JSR FTDAR setting + 32
FPFR = 0 ?
Yes No
No Clear FKEY and erasing error processing *
Required block erasing is completed?
Yes
No
Clear FKEY to 0
Yes Initialization error processing
Disable interrupts and bus master operation other than CPU
Set FMATS to H'AA to select user boot MAT
End erasing procedure program
MAT switchover
1
User-boot-MAT selection state
Note: * The MAT must be switched by FMATS to perform the erasing error processing in the user boot MAT.
Figure 14.15 Procedure for Erasing User MAT in User Boot Mode The difference between the erasing procedures in user program mode and user boot mode depends on whether the MAT is switched or not as shown in figure 14.15.
Rev. 2.00, 03/04, page 417 of 534
MAT switching is enabled by writing a specific value to FMATS. However note that while the MATs are being switched, the LSI is in an unstable state, e.g. access to a MAT is not allowed until MAT switching is completed, and if an interrupt occurs, from which MAT the interrupt vector is read is undetermined. Perform MAT switching in accordance with the description in section 14.6, Switching between User MAT and User Boot MAT. Except for MAT switching, the erasing procedure is the same as that in user program mode. The area that can be executed in the steps of the user procedure program (on-chip RAM, user MAT, and external space) is shown in section 14.4.4, Procedure Program and Storable Area for Programming Data. 14.4.4 Procedure Program and Storable Area for Programming Data
In the descriptions in the previous section, the programming/erasing procedure programs and storable areas for program data are assumed to be in the on-chip RAM. However, the program and the data can be stored in and executed from other areas, such as part of flash memory which is not to be programmed or erased, or somewhere in the external address space. Conditions that Apply to Programming/Erasing: 1. The on-chip programming/erasing program is downloaded from the address in the on-chip RAM specified by FTDAR, therefore, this area is not available for use. 2. The on-chip programming/erasing program will use 128 bytes at the maximum as a stack. So, make sure that this area is secured. 3. Download by setting the SCO bit to 1 will lead to switching of the MAT. If, therefore, this operation is used, it should be executed from the on-chip RAM. 4. The flash memory is accessible until the start of programming or erasing, that is, until the result of downloading has been determined. When in a mode in which the external address space is not accessible, such as single-chip mode, the required procedure programs, NMI handling vector and NMI handler should be transferred to the on-chip RAM before programming/erasing of the flash memory starts. 5. The flash memory is not accessible during programming/erasing operations, therefore, the operation program is downloaded to the on-chip RAM to be executed. The NMI-handling vector and programs such as that which activate the operation program, and NMI handler should thus be stored in on-chip memory other than flash memory or the external address space.
Rev. 2.00, 03/04, page 418 of 534
6. After programming/erasing, the flash memory should be inhibited until FKEY is cleared. The reset state (RES = 0) must be in place for more than 100 µs when the LSI mode is changed to reset on completion of a programming/erasing operation. Transitions to the reset state, and hardware standby mode are inhibited during programming/erasing. When the reset signal is accidentally input to the chip, a longer period in the reset state than usual (100 µs) is needed before the reset signal is released. 7. Switching of the MATs by FMATS should be needed when programming/erasing of the user boot MAT is operated in user-boot mode. The program which switches the MATs should be executed from the on-chip RAM. See section 14.6, Switching between User MAT and User Boot MAT. Please make sure you know which MAT is selected when switching between them. 8. When the data storable area indicated by programming parameter FMPDR is within the flash memory area, an error will occur even when the data stored is normal. Therefore, the data should be transferred to the on-chip RAM to place the address that FMPDR indicates in an area other than the flash memory. In consideration of these conditions, there are three factors; operating mode, the bank structure of the user MAT, and operations. The areas in which the programming data can be stored for execution are shown in tables. Table 14.8 Executable MAT
Initiated Mode Operation Programming Erasing Note: * User Program Mode Table 14.9 (1) Table 14.9 (2) Programming/Erasing is possible to user MATs. User Boot Mode* Table 14.9 (3) Table 14.9 (4)
Rev. 2.00, 03/04, page 419 of 534
Table 14.9 (1)
Useable Area for Programming in User Program Mode
Storable /Executable Area On-chip RAM User MAT ×* Selected MAT
Item Storage Area for Program Data Operation for Selection of On-chip Program to be Downloaded Operation for Writing H'A5 to FKEY Execution of Writing SC0 = 1 to FCCS (Download) Operation for FKEY Clear Determination of Download Result Operation for Download Error Operation for Settings of Initial Parameter Execution of Initialization Determination of Initialization Result Operation for Initialization Error NMI Handling Routine Operation for Inhibit of Interrupt Operation for Writing H'5A to FKEY Operation for Settings of Program Parameter
Embedded External Space Program (Expanded Mode) User MAT Storage Area
×
×
×
×
×
×
Rev. 2.00, 03/04, page 420 of 534
Storable /Executable Area On-chip RAM Target Flash Memory × × × ×
Selected MAT
Item Execution of Programming Determination of Program Result Operation for Program Error Operation for FKEY Clear Note: *
Embedded External Space Program (Expanded Mode) User MAT Storage Area ×
Transferring the data to the on-chip RAM enables this area to be used.
Rev. 2.00, 03/04, page 421 of 534
Table 14.9 (2)
Useable Area for Erasure in User Program Mode
Storable /Executable Area On-chip RAM User MAT Selected MAT
Item Operation for Selection of On-chip Program to be Downloaded Operation for Writing H'A5 to FKEY Execution of Writing SC0 = 1 to FCCS (Download) Operation for FKEY Clear Determination of Download Result Operation for Download Error Operation for Settings of Initial Parameter Execution of Initialization Determination of Initialization Result Operation for Initialization Error NMI Handling Routine Operation for Inhibit of Interrupt Operation for Writing H'5A to FKEY Operation for Settings of Erasure Parameter Execution of Erasure Determination of Erasure Result
Embedded External Space Program (Expanded Mode) User MAT Storage Area
×
×
×
×
×
× × × ×
Rev. 2.00, 03/04, page 422 of 534
Storable /Executable Area On-chip RAM User MAT × ×
Selected MAT
Item Operation for Erasure Error Operation for FKEY Clear
Embedded External Space Program (Expanded Mode) User MAT Storage Area
Rev. 2.00, 03/04, page 423 of 534
Table 14.9 (3)
Useable Area for Programming in User Boot Mode
Storable/Executable Area On-chip RAM External Space User Boot (Expanded MAT Mode) ×*1 User MAT Selected MAT User Boot MAT Embedded Program Storage Area
Item Storage Area for Program Data Operation for Selection of On-chip Program to be Downloaded Operation for Writing H'A5 to FKEY Execution of Writing SC0 = 1 to FCCS (Download) Operation for FKEY Clear Determination of Download Result Operation for Download Error Operation for Settings of Initial Parameter Execution of Initialization Determination of Initialization Result Operation for Initialization Error NMI Handling Routine Operation for Interrupt Inhibit Switching MATs by FMATS Operation for Writing H'5A to FKEY
×
×
×
×
×
× ×
×
Rev. 2.00, 03/04, page 424 of 534
Storable/Executable Area On-chip RAM External Space User Boot (Expanded MAT Mode) × User MAT
Selected MAT User Boot MAT Embedded Program Storage Area
Item Operation for Settings of Program Parameter Execution of Programming Determination of Program Result Operation for Program Error Operation for FKEY Clear Switching MATs by FMATS
× × ×*2 × ×
×
×
Notes: 1. Transferring the data to the on-chip RAM enables this area to be used. 2. Switching FMATS by a program in the on-chip RAM enables this area to be used.
Rev. 2.00, 03/04, page 425 of 534
Table 14.9 (4)
Useable Area for Erasure in User Boot Mode
Storable/Executable Area On-chip RAM External Space User Boot (Expanded MAT Mode) User MAT Selected MAT User Boot MAT Embedded Program Storage Area
Item Operation for Selection of On-chip Program to be Downloaded Operation for Writing H'A5 to FKEY Execution of Writing SC0 = 1 to FCCS (Download) Operation for FKEY Clear Determination of Download Result Operation for Download Error Operation for Settings of Initial Parameter Execution of Initialization Determination of Initialization Result Operation for Initialization Error NMI Handling Routine Operation for Interrupt Inhibit Switching MATs by FMATS Operation for Writing H'5A to FKEY Operation for Settings of Erasure Parameter
×
×
×
×
×
× × ×
×
Rev. 2.00, 03/04, page 426 of 534
Storable/Executable Area On-chip RAM External Space User Boot (Expanded MAT Mode) × × ×* × × × × User MAT
Selected MAT User Boot MAT Embedded Program Storage Area
Item Execution of Erasure Determination of Erasure Result Operation for Erasure Error Operation for FKEY Clear Switching MATs by FMATS Note: *
Switching FMATS by a program in the on-chip RAM enables this area to be used.
Rev. 2.00, 03/04, page 427 of 534
14.5
Protection
There are two kinds of flash memory program/erase protection: hardware and software protection. 14.5.1 Hardware Protection
Programming and erasing of flash memory is forcibly disabled or suspended by hardware protection. In this state, the downloading of an on-chip program and initialization are possible. However, an activated program for programming or erasure cannot program or erase locations in a user MAT, and the error in programming/erasing is reported in the parameter FPFR. Table 14.10 Hardware Protection
Function to be Protected Item FWE pin protection Description • Download Program/Erase When a low level signal is input to the FWE pin, the FWE bit in FCCS is cleared and the program/eraseprotected state is entered. The program/erase interface registers are initialized in the reset state (including a reset by the WDT) and standby mode and the program/eraseprotected state is entered. The reset state will not be entered by a reset using the RES pin unless the RES pin is held low until oscillation has stabilized after power is initially supplied. In the case of a reset during operation, hold the RES pin low for the RES pulse width that is specified in the section on AC characteristics. If a reset is input during programming or erasure, data values in the flash memory are not guaranteed. In this case, execute erasure and then execute program again.
Reset/standby protection
•
•
Rev. 2.00, 03/04, page 428 of 534
14.5.2
Software Protection
Software protection is set up in any of two ways: by disabling the downloading of on-chip programs for programming and erasing and by means of a key code. Table 14.11 Software Protection
Function to be Protected Item Protection by the SCO bit Description • The program/erase-protected state is entered by clearing the SCO bit in FCCS which disables the downloading of the programming/erasing programs. Downloading and programming/erasing are disabled unless the required key code is written in FKEY. Different key codes are used for downloading and for programming/erasing. Download Program/Erase
Protection by the FKEY register
•
14.5.3
Error Protection
Error protection is a mechanism for aborting programming or erasure when an error occurs, in the form of the microcomputer entering runaway during programming/erasing of the flash memory or operations that are not according to the established procedures for programming/erasing. Aborting programming or erasure in such cases prevents damage to the flash memory due to excessive programming or erasing. If the microcomputer malfunctions during programming/erasing of the flash memory, the FLER bit in the FCCS register is set to 1 and the error-protection state is entered, and this aborts the programming or erasure. The FLER bit is set in the following conditions: 1. When an interrupt such as NMI occurs during programming/erasing. 2. When the flash memory is read during programming/erasing (including a vector read or an instruction fetch). 3. When a SLEEP instruction (including software-standby mode) is executed during programming/erasing. 4. When a bus master other than the CPU, such as the DMAC, gets bus mastership during programming/erasing.
Rev. 2.00, 03/04, page 429 of 534
Error protection is cancelled only by a reset or by hardware-standby mode. Note that the reset should be released after the reset period of 100 µs which is longer than normal. Since high voltages are applied during programming/erasing of the flash memory, some voltage may remain after the error-protection state has been entered. For this reason, it is necessary to reduce the risk of damage to the flash memory by extending the reset period so that the charge is released. The state-transition diagram in figure 14.16 shows transitions to and from the error-protection state.
Program mode Erase mode
Read disabled Programming/erasing enabled FLER = 0
= 0 or
=0
Reset or hardware standby (Hardware protection)
Read disabled Programming/erasing disabled FLER = 0
Er ro
Error occurrence
ro c (S curr oft e wa d re sta n
=0
or =0
db
= 0 or =0
y)
Program/erase interface register is in its initial state.
Error protection mode
Read enabled Programming/erasing disabled FLER = 1
Software-standby mode
Error-protection mode (Software standby)
Read disabled Cancel programming/erasing disabled software-standby mode FLER = 1
Program/erase interface register is in its initial state.
Figure 14.16 Transitions to Error-Protection State
Rev. 2.00, 03/04, page 430 of 534
14.6
Switching between User MAT and User Boot MAT
It is possible to alternate between the user MAT and user boot MAT. However, the following procedure is required because these MATs are allocated to address 0. (Switching to the user boot MAT disables programming and erasing. Programming of the user boot MAT should take place in boot mode or programmer mode.) 1. MAT switching by FMATS should always be executed from the on-chip RAM. 2. To ensure that the MAT that has been switched to is accessible, execute four NOP instructions in the on-chip RAM immediately after writing to FMATS of the on-chip RAM (this prevents access to the flash memory during MAT switching). 3. If an interrupt has occurred during switching, there is no guarantee of which memory MAT is being accessed. Always mask the maskable interrupts before switching between MATs. In addition, configure the system so that NMI interrupts do not occur during MAT switching. 4. After the MATs have been switched, take care because the interrupt vector table will also have been switched. If interrupt processing is to be the same before and after MAT switching, transfer the interrupt-processing routines to the on-chip RAM and set the WEINTE bit in FCCS to place the interrupt-vector table in the on-chip RAM. 5. Memory sizes of the user MAT and user boot MAT are different. When accessing the user boot MAT, do not access addresses above the top of its 8-kbyte memory space. If access goes beyond the 8-kbyte space, the values read are undefined.
Procedure for switching to the user boot MAT Procedure for switching to the user MAT Procedure for switching to the user boot MAT (1) Mask interrupts (2) Write H'AA to FMATS. (3) Execute four NOP instructions before accessing the user boot MAT. Procedure for switching to the user MAT (1) Mask interrupts (2) Write a value other than H'AA to FMATS. (3) Execute four NOP instructions before accessing the user MAT.
Figure 14.17 Switching between the User MAT and User Boot MAT
Rev. 2.00, 03/04, page 431 of 534
14.7
14.7.1
Flash Memory Emulation in RAM
Emulation in RAM
Making a setting in the RAM emulation register (RAMER) enables part of RAM to be overlapped onto the flash memory area so that data to be written to flash memory can be emulated in RAM in realtime. After the RAMER setting has been made, accesses can be made from the flash memory area or the RAM area overlapping flash memory. Emulation can be performed in user mode and user program mode. Figure 14.18 shows an example of emulation of realtime flash memory.
Start of emulation program
Set RAMER
Write tuning data to overlap RAM
Execute application program
No
Tuning OK? Yes Clear RAMER
Write to flash memory emulation block
End of emulation program
Figure 14.18 Flowchart for Flash Memory Emulation in RAM
Rev. 2.00, 03/04, page 432 of 534
14.7.2
RAM Overlap
This area can be accessed from both the RAM area and flash memory area H'00000 EB0 H'01000 EB1 H'02000 EB2 H'03000 EB3 H'04000 EB4 H'05000 EB5 H'06000 EB6 H'07000 EB7 H'08000 H'FF7000 Flash memor EB8 to EB11 On-chip RAM H'FFEFFF H'3FFFF H'FF7FFF
Figure 14.19 Example of RAM Overlap Operation (256-kbyte Flash Memory) As the flash memory area to be emulated, bits RAM2 to RAM0 select one area among eight areas, EB0 to EB7, in bank 1 of user MAT. Figure 14.19 shows an example in which flash memory block area, EB1, is overlapped. 1. Set bits RAMS, RAM2, RAM1, and RAM0 in RAMER to 1, 0, 0, 1, to overlap part of RAM onto the area (EB1) for which realtime programming is required. 2. Realtime programming is performed using the overlapping RAM. 3. After the program data has been confirmed, the RAMS bit is cleared, releasing RAM overlap. 4. The data written in the overlapping RAM is written into the flash memory space (EB1). Notes: 1. When the RAMS bit is set to 1, program/erase-protection is enables for all flash memory blocks regardless of the value of RAM2, RAM1, and RAM0 (emulation protection). When actually programming a flash memory area, the RAMS bit should be cleared to 0. 2. The RAM area cannot be erased by execution of software in accordance with the erase algorithm while flash memory emulation in RAM is being used. 3. Block area EB0 includes the vector table. When performing RAM emulation, the vector table is needed by the overlap RAM.
Rev. 2.00, 03/04, page 433 of 534
14.8
Programmer Mode
Along with its on-board programming mode, this LSI also has a programmer mode as a further mode for the writing and erasing of programs and data. In the programmer mode, a generalpurpose PROM programmer can freely be used to write programs to the on-chip ROM. Program/erase is possible on the user MAT and user boot MAT. The PROM programmer must support Renesas Technology’s microcomputers with 258-kbyte flash memory as a device type*. Figure 14.20 shows a memory map in programmer mode. A status-polling system is adopted for operation in automatic program, automatic erase, and status-read modes. In the status-read mode, details of the system's internal signals are output after execution of automatic programming or automatic erasure. In programmer mode, provide a 12MHz input-clock signal. Note: * In this LSI, set the programming voltage of the PROM programmer to 3.3 V.
MCU mode H'000000 This LSI Programmer mode H'00000
On-chip ROM area
H'03FFFF
H'3FFFF
Figure 14.20 Memory Map in Programmer Mode
Rev. 2.00, 03/04, page 434 of 534
14.9
Serial Communication Interface Specification for Boot Mode
Initiating boot mode enables the boot program to communicate with the host by using the internal SCI. The serial communication interface specification is shown below. Status: The boot program has three states. 1. Bit-Rate-Adjustment State In this state, the boot program adjusts the bit rate to communicate with the host. Initiating boot mode enables starting of the boot program and entry to the bit-rate-adjustment state. The program receives the command from the host to adjust the bit rate. After adjusting the bit rate, the program enters the inquiry/selection state. 2. Inquiry/Selection State In this state, the boot program responds to inquiry commands from the host. The device name, clock mode, and bit rate are selected. After selection of these settings, the program is made to enter the programming/erasing state by the command for a transition to the programming/erasing state. The program transfers the libraries required for erasure to the onchip RAM and erases the user MATs and user boot MATs before the transition. 3. Programming/erasing state Programming and erasure by the boot program take place in this state. The boot program is made to transfer the programming/erasing programs to the RAM by commands from the host. Sum checks and blank checks are executed by sending these commands from the host. These boot program states are shown in figure 14.21.
Rev. 2.00, 03/04, page 435 of 534
Reset
Bit-rate-adjustment state
Inquiry/response wait Transition to programming/erasing
Response Inquiry Operations for inquiry and selection Operations for response
Operations for erasing user MATs and user boot MATs
Programming/erasing wait Programming Operations for programming Erasing Operations for erasing Checking
Operations for checking
Figure 14.21 Boot Program States
Rev. 2.00, 03/04, page 436 of 534
Bit-Rate-Adjustment State: The bit rate is calculated by measuring the period of transfer of a low-level byte (H'00) from the host. The bit rate can be changed by the command for a new bit rate selection. After the bit rate has been adjusted, the boot program enters the inquiry and selection state. The bit-rate-adjustment sequence is shown in figure 14.22.
Host
H'00 (30 times maximum)
Boot Program
Measuring the 1-bit length
H'00 (Completion of adjustment)
H'55
H'E6 (Boot response)
(H'FF (error))
Figure 14.22 Bit-Rate-Adjustment Sequence Communications Protocol:After adjustment of the bit rate, the protocol for communications between the host and the boot program is as shown below. 1. One-byte commands and one-byte responses These commands and responses are comprised of a single byte. These are consists of the inquiries and the ACK for successful completion. 2. n-byte commands or n-byte responses These commands and responses are comprised of n bytes of data. These are selections and responses to inquiries. The amount of programming data is not included under this heading because it is determined in another command. 3. Error response The error response is a response to inquiries. It consists of an error response and an error code and comes two bytes. 4. Programming of 128 bytes The size is not specified in commands. The size of n is indicated in response to the programming unit inquiry. 5. Memory read response This response consists of four bytes of data.
Rev. 2.00, 03/04, page 437 of 534
One-byte command or one-byte response n-byte Command or n-byte response
Command or response
Data Size Checksum
Command or response
Error response Error code Error response
128-byte programming
Address
Command
Data (n bytes) Checksum
Memory read response
Size
Response
Data Checksum
Figure 14.23 Communication Protocol Format • Command (one byte): Commands including inquiries, selection, programming, erasing, and checking • Response (one byte): Response to an inquiry • Size (one byte): The amount of data for transmission excluding the command, amount of data, and checksum • Checksum (one byte): The checksum is calculated so that the total of all values from the command byte to the SUM byte becomes H'00. • Data (n bytes): Detailed data of a command or response • Error response (one byte): Error response to a command • Error code (one byte): Type of the error • Address (four bytes): Address for programming • Data (n bytes): Data to be programmed (the size is indicated in the response to the programming unit inquiry.) • Size (four bytes): Four-byte response to a memory read
Rev. 2.00, 03/04, page 438 of 534
Inquiry and Selection States: The boot program returns information from the flash memory in response to the host's inquiry commands and sets the device code, clock mode, and bit rate in response to the host's selection command. Inquiry and selection commands are listed below. Table 14.12 Inquiry and Selection Commands
Command H'20 H'10 H'21 H'11 H'22 Command Name Supported Device Inquiry Device Selection Clock Mode Inquiry Clock Mode Selection Multiplication Ratio Inquiry Description Inquiry regarding device codes Selection of device code Inquiry regarding numbers of clock modes and values of each mode Indication of the selected clock mode Inquiry regarding the number of frequencymultiplied clock types, the number of multiplication ratios, and the values of each multiple
H'23 H'24
Operating Clock Frequency Inquiry Inquiry regarding the maximum and minimum values of the main clock and peripheral clocks User Boot MAT Information Inquiry Inquiry regarding the number of user boot MATs and the start and last addresses of each MAT User MAT Information Inquiry Block for Erasing Information Inquiry Programming Unit Inquiry New Bit Rate Selection Inquiry regarding the a number of user MATs and the start and last addresses of each MAT Inquiry regarding the number of blocks and the start and last addresses of each block Inquiry regarding the unit of programming data Selection of new bit rate
H'25 H'26 H'27 H'3F H'40 H'4F
Transition to Programming/Erasing Erasing of user MAT and user boot MAT, and State entry to programming/erasing state Boot Program Status Inquiry Inquiry into the operated status of the boot program
The selection commands, which are device selection (H'10), clock mode selection (H'11), and new bit rate selection (H'3F), should be sent from the host in that order. These commands will certainly be needed. When two or more selection commands are sent at once, the last command will be valid.
Rev. 2.00, 03/04, page 439 of 534
All of these commands, except for the boot program status inquiry command (H'4F), will be valid until the boot program receives the programming/erasing transition (H'40). The host can choose the needed commands out of the commands and inquiries listed above. The boot program status inquiry command (H'4F) is valid after the boot program has received the programming/erasing transition command (H'40). (a) Supported Device Inquiry The boot program will return the device codes of supported devices and the product code in response to the supported device inquiry.
Command H'20
• Command, H'20, (one byte): Inquiry regarding supported devices
Response H'30 Number of characters ··· SUM Size Number of devices Product name
Device code
• Response, H'30, (one byte): Response to the supported device inquiry • Size (one byte): Number of bytes to be transmitted, excluding the command, size, and checksum, that is, the amount of data contributes by the number of devices, characters, device codes and product names • Number of devices (one byte): The number of device types supported by the boot program • Number of characters (one byte): The number of characters in the device codes and boot program's name • Device code (four bytes): ASCII code of the supporting product • Product name (n bytes): Type name of the boot program in ASCII-coded characters • SUM (one byte): Checksum The checksum is calculated so that the total number of all values from the command byte to the SUM byte becomes H'00.
Rev. 2.00, 03/04, page 440 of 534
(b) Device Selection The boot program will set the supported device to the specified device code. The program will return the selected device code in response to the inquiry after this setting has been made.
Command H'10 Size Device code SUM
• Command, H'10, (one byte): Device selection • Size (one byte): Amount of device-code data This is fixed at 2 • Device code (four bytes): Device code (ASCII code) returned in response to the supported device inquiry • SUM (one byte): Checksum
Response H'06
• Response, H'06, (one byte): Response to the device selection command ACK will be returned when the device code matches.
Error response H'90 ERROR
• Error response, H'90, (one byte): Error response to the device selection command ERROR : (one byte): Error code H'11: Sum check error H'21: Device code error, that is, the device code does not match (c) Clock Mode Inquiry The boot program will return the supported clock modes in response to the clock mode inquiry.
Command H'21
• Command, H'21, (one byte): Inquiry regarding clock mode
Response H'31 Size Number of modes Mode ··· SUM
• Response, H'31, (one byte): Response to the clock-mode inquiry • Size (one byte): Amount of data that represents the number of modes and modes • Number of clock modes (one byte): The number of supported clock modes H'00 indicates no clock mode or the device allows to read the clock mode. • Mode (one byte): Values of the supported clock modes (i.e. H'01 means clock mode 1.) • SUM (one byte): Checksum
Rev. 2.00, 03/04, page 441 of 534
(d) Clock Mode Selection The boot program will set the specified clock mode. The program will return the selected clockmode information after this setting has been made. The clock-mode selection command should be sent after the device-selection commands.
Command H'11 Size Mode SUM
• • • •
Command, H'11, (one byte): Selection of clock mode Size (one byte): Amount of data that represents the modes Mode (one byte): A clock mode returned in reply to the supported clock mode inquiry. SUM (one byte): Checksum
H'06
Response
• Response, H'06, (one byte): Response to the clock mode selection command ACK will be returned when the clock mode matches.
Error Response H'91 ERROR
• Error response, H'91, (one byte) : Error response to the clock mode selection command • ERROR : (one byte): Error code H'11: Checksum error H'22: Clock mode error, that is, the clock mode does not match. Even if the clock mode numbers are H'00 and H'01 by a clock mode inquiry, the clock mode must be selected using these respective values. (e) Multiplication Ratio Inquiry The boot program will return the supported multiplication and division ratios.
Command H'22
• Command, H'22, (one byte): Inquiry regarding multiplication ratio
Response H'32 Number of multiplication ratios ··· SUM Size Multiplication ratio Number of types ···
Rev. 2.00, 03/04, page 442 of 534
• Response, H'32, (one byte): Response to the multiplication ratio inquiry • Size (one byte): The amount of data that represents the number of clock sources and multiplication ratios and the multiplication ratios • Number of types (one byte): The number of supported multiplied clock types (e.g. when there are two multiplied clock types, which are the main and peripheral clocks, the number of types will be H'02.) • Number of multiplication ratios (one byte): The number of multiplication ratios for each type (e.g. the number of multiplication ratios to which the main clock can be set and the peripheral clock can be set.) • Multiplication ratio (one byte) Multiplication ratio: The value of the multiplication ratio (e.g. when the clock-frequency multiplier is four, the value of multiplication ratio will be H'04.) Division ratio: The inverse of the division ratio, i.e. a negative number (e.g. when the clock is divided by two, the value of division ratio will be H'FE. H'FE = D'-2) The number of multiplication ratios returned is the same as the number of multiplication ratios and as many groups of data are returned as there are types. • SUM (one byte): Checksum (f) Operating Clock Frequency Inquiry The boot program will return the number of operating clock frequencies, and the maximum and minimum values.
Command H'23
• Command, H'23, (one byte): Inquiry regarding operating clock frequencies
Response H'33 Size Number of operating clock frequencies
Minimum value of operating Maximum value of operating clock clock frequency frequency ··· SUM
• Response, H'33, (one byte): Response to operating clock frequency inquiry • Size (one byte): The number of bytes that represents the minimum values, maximum values, and the number of frequencies. • Number of operating clock frequencies (one byte): The number of supported operating clock frequency types (e.g. when there are two operating clock frequency types, which are the main and peripheral clocks, the number of types will be H'02.)
Rev. 2.00, 03/04, page 443 of 534
• Minimum value of operating clock frequency (two bytes): The minimum value of the multiplied or divided clock frequency. The minimum and maximum values represent the values in MHz, valid to the hundredths place of MHz, and multiplied by 100. (e.g. when the value is 20.00 MHz, it will be 2000, which is H'07D0.) • Maximum value (two bytes): Maximum value among the multiplied or divided clock frequencies. There are as many pairs of minimum and maximum values as there are operating clock frequencies. • SUM (one byte): Checksum (g) User Boot MAT Information Inquiry The boot program will return the number of user boot MATs and their addresses.
Command H'24
• Command, H'24, (one byte): Inquiry regarding user boot MAT information
Response H'34 ··· SUM Size Number of areas Area-last address
Area-start address
• Response, H'34, (one byte): Response to user boot MAT information inquiry • Size (one byte): The number of bytes that represents the number of areas, area-start addresses, and area-last address • Number of Areas (one byte): The number of consecutive user boot MAT areas When user boot MAT areas are consecutive, the number of areas returned is H'01. • Area-start address (four byte): Start address of the area • Area-last address (four byte): Last address of the area There are as many groups of data representing the start and last addresses as there are areas. • SUM (one byte): Checksum
Rev. 2.00, 03/04, page 444 of 534
(h) User MAT Information Inquiry The boot program will return the number of user MATs and their addresses.
Command H'25
• Command, H'25, (one byte): Inquiry regarding user MAT information
Response H'35 ··· SUM Size Number of areas Last address area
Start address area
• Response, H'35, (one byte): Response to the user MAT information inquiry • Size (one byte): The number of bytes that represents the number of areas, area-start address and area-last address • Number of areas (one byte): The number of consecutive user MAT areas When the user MAT areas are consecutive, the number of areas is H'01. • Area-start address (four bytes): Start address of the area • Area-last address (four bytes): Last address of the area There are as many groups of data representing the start and last addresses as there are areas. • SUM (one byte): Checksum (i) Erased Block Information Inquiry The boot program will return the number of erased blocks and their addresses.
Command H'26
• Command, H'26, (two bytes): Inquiry regarding erased block information
Response H'36 ··· SUM Size Number of blocks Block last address
Block start address
• Response, H'36, (one byte): Response to the number of erased blocks and addresses • Size (three bytes): The number of bytes that represents the number of blocks, block-start addresses, and block-last addresses. • Number of blocks (one byte): The number of erased blocks • Block start address (four bytes): Start address of a block • Block last Address (four bytes): Last address of a block There are as many groups of data representing the start and last addresses as there are areas. • SUM (one byte): Checksum
Rev. 2.00, 03/04, page 445 of 534
(j) Programming Unit Inquiry The boot program will return the programming unit used to program data.
Command H'27
• Command, H'27, (one byte): Inquiry regarding programming unit
Response H'37 Size Programming unit SUM
• Response, H'37, (one byte): Response to programming unit inquiry • Size (one byte): The number of bytes that indicate the programming unit, which is fixed to 2 • Programming unit (two bytes): A unit for programming This is the unit for reception of programming. • SUM (one byte): Checksum (k) New Bit-Rate Selection The boot program will set a new bit rate and return the new bit rate. This selection should be sent after sending the clock mode selection command.
Command H'3F Number of multiplication ratios SUM Size Multiplication ratio 1 Bit rate Multiplication ratio 2 Input frequency
• Command, H'3F, (one byte): Selection of new bit rate • Size (one byte): The number of bytes that represents the bit rate, input frequency, number of multiplication ratios, and multiplication ratio • Bit rate (two bytes): New bit rate One hundredth of the value (e.g. when the value is 19200 bps, it will be 192, which is H'00C0.) • Input frequency (two bytes): Frequency of the clock input to the boot program This is valid to the hundredths place and represents the value in MHz multiplied by 100. (E.g. when the value is 20.00 MHz, it will be 2000, which is H'07D0.) • Number of multiplication ratios (one byte): The number of multiplication ratios to which the device can be set. • Multiplication ratio 1 (one byte): The value of multiplication or division ratios for the main operating frequency Multiplication ratio (one byte): The value of the multiplication ratio (e.g. when the clock frequency is multiplied by four, the multiplication ratio will be H'04.) Division ratio: The inverse of the division ratio, as a negative number (e.g. when the clock frequency is divided by two, the value of division ratio will be H'FE. H'FE = D'-2)
Rev. 2.00, 03/04, page 446 of 534
• Multiplication ratio 2 (one byte): The value of multiplication or division ratios for the peripheral frequency Multiplication ratio (one byte): The value of the multiplication ratio (e.g. when the clock frequency is multiplied by four, the multiplication ratio will be H'04.) (Division ratio: The inverse of the division ratio, as a negative number (E.g. when the clock is divided by two, the value of division ratio will be H'FE. H'FE = D'-2) • SUM (one byte): Checksum
Response H'06
• Response, H'06, (one byte): Response to selection of a new bit rate When it is possible to set the bit rate, the response will be ACK.
Error Response H'BF ERROR
• Error response, H'BF, (one byte): Error response to selection of new bit rate • ERROR: (one byte): Error code H'11: Sum checking error H'24: Bit-rate selection error The rate is not available. H'25: Error in input frequency This input frequency is not within the specified range. H'26: Multiplication-ratio error The ratio does not match an available ratio. H'27: Operating frequency error The frequency is not within the specified range. Received Data Check: The methods for checking of received data are listed below. 1. Input frequency The received value of the input frequency is checked to ensure that it is within the range of minimum to maximum frequencies which matches the clock modes of the specified device. When the value is out of this range, an input-frequency error is generated. 2. Multiplication ratio The received value of the multiplication ratio or division ratio is checked to ensure that it matches the clock modes of the specified device. When the value is out of this range, an inputfrequency error is generated. 3. Operating frequency error Operating frequency is calculated from the received value of the input frequency and the multiplication or division ratio. The input frequency is input to the LSI and the LSI is operated at the operating frequency. The expression is given below. Operating frequency = Input frequency × Multiplication ratio, or Operating frequency = Input frequency ÷ Division ratio
Rev. 2.00, 03/04, page 447 of 534
The calculated operating frequency should be checked to ensure that it is within the range of minimum to maximum frequencies which are available with the clock modes of the specified device. When it is out of this range, an operating frequency error is generated. 4. Bit rate To facilitate error checking, the value (n) of clock select (CKS) in the serial mode register (SMR), and the value (N) in the bit rate register (BRR), which are found from the peripheral operating clock frequency (φ) and bit rate (B), are used to calculate the error rate to ensure that it is less than 4%. If the error is more than 4%, a bit rate error is generated. The error is calculated using the following expression:
Error (%) = {[ φ × 106 (N + 1) × B × 64 × 2(2×n − 1) ] − 1} × 100
When the new bit rate is selectable, the rate will be set in the register after sending ACK in response. The host will send an ACK with the new bit rate for confirmation and the boot program will response with that rate.
Confirmation H'06
• Confirmation, H'06, (one byte): Confirmation of a new bit rate
Response H'06
• Response, H'06, (one byte): Response to confirmation of a new bit rate The sequence of new bit-rate selection is shown in figure 14.24.
Host
Setting a new bit rate
Waiting for one-bit period at the specified bit rate
Setting a new bit rate
Boot program
H'06 (ACK)
Setting a new bit rate
H'06 (ACK) with the new bit rate H'06 (ACK) with the new bit rate
Figure 14.24 New Bit-Rate Selection Sequence
Rev. 2.00, 03/04, page 448 of 534
Transition to Programming/Erasing State: The boot program will transfer the erasing program, and erase the user MATs and user boot MATs in that order. On completion of this erasure, ACK will be returned and will enter the programming/erasing state. The host should select the device code, clock mode, and new bit rate with device selection, clockmode selection, and new bit-rate selection commands, and then send the command for the transition to programming/erasing state. These procedures should be carried out before sending of the programming selection command or program data.
Command H'40
• Command, H'40, (one byte): Transition to programming/erasing state
Response H'06
• Response, H'06, (one byte): Response to transition to programming/erasing state The boot program will send ACK when the user MAT and user boot MAT have been erased by the transferred erasing program.
Error Response H'C0 H'51
• Error response, H'C0, (one byte): Error response for user boot MAT blank check • Error code, H'51, (one byte): Erasing error An error occurred and erasure was not completed. Command Error: A command error will occur when a command is undefined, the order of commands is incorrect, or a command is unacceptable. Issuing a clock-mode selection command before a device selection or an inquiry command after the transition to programming/erasing state command, are examples.
Error Response H'80 H'xx
• Error response, H'80, (one byte): Command error • Command, H'xx, (one byte): Received command Command Order: The order for commands in the inquiry selection state is shown below. 1. A supported device inquiry (H'20) should be made to inquire about the supported devices. 2. The device should be selected from among those described by the returned information and set with a device-selection (H'10) command. 3. A clock-mode inquiry (H'21) should be made to inquire about the supported clock modes. 4. The clock mode should be selected from among those described by the returned information and set. 5. After selection of the device and clock mode, inquiries for other required information should be made, such as the multiplication-ratio inquiry (H'22) or operating frequency inquiry (H'23), which are needed for a new bit-rate selection.
Rev. 2.00, 03/04, page 449 of 534
6. A new bit rate should be selected with the new bit-rate selection (H'3F) command, according to the returned information on multiplication ratios and operating frequencies. 7. After selection of the device and clock mode, the information of the user boot MAT and user MAT should be made to inquire about the user boot MATs information inquiry (H'24), user MATs information inquiry (H'25), erased block information inquiry (H'26), and programming unit inquiry (H'27). 8. After making inquiries and selecting a new bit rate, issue the transition to programming/erasing state command (H'40). The boot program will then enter the programming/erasing state. Programming/Erasing State: A programming selection command makes the boot program select the programming method, a 128-byte programming command makes it program the memory with data, and an erasing selection command and block erasing command make it erase the block. The programming/erasing commands are listed below. Table 14.13 Programming/Erasing Command
Command H'42 H'43 H'50 H'48 H'58 H'52 H'4A H'4B H'4C H'4D H'4C H'4D H'4F Command Name Description
User boot MAT programming selection Transfers the user boot MAT programming program User MAT programming selection 128-byte programming Erasing selection Block erasing Memory read User boot MAT sum check User MAT sum check User boot MAT blank check User MAT blank check User boot MAT blank check User MAT blank check Boot program status inquiry Transfers the user MAT programming program Programs 128 bytes of data Transfers the erasing program Erases a block of data Reads the contents of memory Checks the checksum of the user boot MAT Checks the checksum of the user MAT Checks the blank data of the user boot MAT Checks the blank data of the user MAT Checks whether the contents of the user boot MAT are blank Checks whether the contents of the user MAT are blank Inquires into the boot program’s status
Rev. 2.00, 03/04, page 450 of 534
• Programming Programming is executed by a programming-selection command and a 128-byte programming command. Firstly, the host should send the programming-selection command and select the programming method and programming MATs. There are two programming selection commands, and selection is according to the area and method for programming. 1. User boot MAT programming selection 2. User MAT programming selection After issuing the programming selection command, the host should send the 128-byte programming command. The 128-byte programming command that follows the selection command represents the data programmed according to the method specified by the selection command. When more than 128-byte data is programmed, 128-byte commands should repeatedly be executed. Sending a 128-byte programming command with H'FFFFFFFF as the address will stop the programming. On completion of programming, the boot program will wait for selection of programming or erasing. Where the sequence of programming operations that is executed includes programming with another method or of another MAT, the procedure must be repeated from the programming selection command. The sequence for programming-selection and 128-byte programming commands is shown in figure 14.25.
Host Programming selection (H'42, H'43) Boot program
Transfer of the programming program
ACK
128-byte programming (address, data)
Repeat
Programming ACK 128-byte programming (H'FFFFFFFF) ACK
Figure 14.25 Programming Sequence
Rev. 2.00, 03/04, page 451 of 534
(a) User boot MAT programming selection The boot program will transfer a programming program. The data is programmed to the user boot MATs by the transferred programming program.
Command H'42
• Command, H'42, (one byte): User boot-program programming selection
Response H'06
• Response, H'06, (one byte): Response to user boot-program programming selection When the programming program has been transferred, the boot program will return ACK.
Error Response H'C2 ERROR
• Error response : H'C2 (1 byte): Error response to user boot MAT programming selection • ERROR : (1 byte): Error code H'54: Selection processing error (transfer error occurs and processing is not completed) • User-program programming selection The boot program will transfer a program for programming. The data is programmed to the user MATs by the transferred program for programming.
Command H'43
• Command, H'43, (one byte): User-program programming selection
Response H'06
• Response, H'06, (one byte): Response to user-program programming selection When the programming program has been transferred, the boot program will return ACK.
Error Response H'C3 ERROR
• Error response : H'C3 (1 byte): Error response to user MAT programming selection • ERROR : (1 byte): Error code H'54: Selection processing error (transfer error occurs and processing is not completed) (b) 128-byte programming The boot program will use the programming program transferred by the programming selection to program the user boot MATs or user MATs in response to 128-byte programming.
Command H'50 Data ··· SUM Address ···
• Command, H'50, (one byte): 128-byte programming
Rev. 2.00, 03/04, page 452 of 534
• Programming Address (four bytes): Start address for programming Multiple of the size specified in response to the programming unit inquiry (i.e. H'00, H'01, H'00, H'00 : H'01000000) • Programming Data (128 bytes): Data to be programmed The size is specified in the response to the programming unit inquiry. • SUM (one byte): Checksum
Response H'06
• Response, H'06, (one byte): Response to 128-byte programming On completion of programming, the boot program will return ACK.
Error Response H'D0 ERROR
• Error response, H'D0, (one byte): Error response for 128-byte programming • ERROR: (one byte): Error code H'11: Checksum Error H'2A: Address Error H'53: Programming error A programming error has occurred and programming cannot be continued. The specified address should match the unit for programming of data. For example, when the programming is in 128-byte units, the lower eight bits of the address should be H'00 or H'80. When there are less than 128 bytes of data to be programmed, the host should fill the rest with H'FF. Sending the 128-byte programming command with the address of H'FFFFFFFF will stop the programming operation. The boot program will interpret this as the end of the programming and wait for selection of programming or erasing.
Command H'50 Address SUM
• Command, H'50, (one byte): 128-byte programming • Programming Address (four bytes): End code is H'FF, H'FF, H'FF, H'FF. • SUM (one byte): Checksum
Response H'06
• Response, H'06, (one byte): Response to 128-byte programming On completion of programming, the boot program will return ACK.
Rev. 2.00, 03/04, page 453 of 534
Error Response
H'D0
ERROR
• Error Response, H'D0, (one byte): Error response for 128-byte programming • ERROR: (one byte): Error code H'11: Checksum error H'2A: Address Error H'53: Programming error An error has occurred in programming and programming cannot be continued. Erasure: Erasure is performed with the erasure selection and block erasure command. Firstly, erasure is selected by the erasure selection command and the boot program then erases the specified block. The command should be repeatedly executed if two or more blocks are to be erased. Sending a block-erasure command from the host with the block number H'FF will stop the erasure operating. On completion of erasing, the boot program will wait for selection of programming or erasing. The sequences of the issuing of erasure selection commands and the erasure of data are shown in figure 14.26.
Host Preparation for erasure (H'48) Boot program
Transfer of erasure program
ACK
Erasure (Erasure block number) ACK Erasure (H'FF) ACK
Repeat
Erasure
Figure 14.26 Erasure Sequence
Rev. 2.00, 03/04, page 454 of 534
(a) Erasure Selection The boot program will transfer the erasure program. User MAT data is erased by the transferred erasure program.
Command H'48
• Command, H'48, (one byte): Erasure selection
Response H'06
• Response, H'06, (one byte): Response for erasure selection After the erasure program has been transferred, the boot program will return ACK.
Error Response H'C8 ERROR
• Error Response, H'C8, (one byte): Error response to erasure selection • ERROR: (one byte): Error code H'54: Selection processing error (transfer error occurs and processing is not completed) (b) Block Erasure The boot program will erase the contents of the specified block.
Command H'58 Size Block number SUM
• Command, H'58, (one byte): Erasure • Size (one byte): The number of bytes that represents the erasure block number This is fixed to 1. • Block number (one byte): Number of the block to be erased • SUM (one byte): Checksum
Response H'06
• Response, H'06, (one byte): Response to Erasure After erasure has been completed, the boot program will return ACK.
Error Response H'D8 ERROR
• Error Response, H'D8, (one byte): Response to Erasure • ERROR (one byte): Error code H'11: Sum check error H'29: Block number error Block number is incorrect. H'51: Erasure error An error has occurred during erasure. On receiving block number H′FF, the boot program will stop erasure and wait for a selection command.
Rev. 2.00, 03/04, page 455 of 534
Command
H'58
Size
Block number
SUM
• Command, H'58, (one byte): Erasure • Size, (one byte): The number of bytes that represents the block number This is fixed to 1. • Block number (one byte): H'FF Stop code for erasure • SUM (one byte): Checksum
Response H'06
• Response, H'06, (one byte): Response to end of erasure (ACK) When erasure is to be performed after the block number H′FF has been sent, the procedure should be executed from the erasure selection command. Memory read: The boot program will return the data in the specified address.
Command H'52 Size Area Read address SUM
Read size
• Command: H'52 (1 byte): Memory read • Size (1 byte): Amount of data that represents the area, read address, and read size (fixed at 9) • Area (1 byte) H'00: User boot MAT H'01: User MAT An address error occurs when the area setting is incorrect. • Read address (4 bytes): Start address to be read from • Read size (4 bytes): Size of data to be read • SUM (1 byte): Checksum
Response H'52 Data SUM Read size ···
• • • •
Response: H'52 (1 byte): Response to memory read Read size (4 bytes): Size of data to be read Data (n bytes): Data for the read size from the read address SUM (1 byte): Checksum
Rev. 2.00, 03/04, page 456 of 534
Error Response
H'D2
ERROR
• Error response: H'D2 (1 byte): Error response to memory read • ERROR: (1 byte): Error code H'11: Sum check error H'2A: Address error The read address is not in the MAT. H'2B: Size error The read size exceeds the MAT. User-Boot Program Sum Check: The boot program will return the byte-by-byte total of the contents of the bytes of the user-boot program, as a four-byte value.
Command H'4A
• Command, H'4A, (one byte): Sum check for user-boot program
Response H'5A Size Checksum of user boot program SUM
• Response, H'5A, (one byte): Response to the sum check of user-boot program • Size (one byte): The number of bytes that represents the checksum This is fixed to 4. • Checksum of user boot program (four bytes): Checksum of user boot MATs The total of the data is obtained in byte units. • SUM (one byte): Sum check for data being transmitted User-Program Sum Check: The boot program will return the byte-by-byte total of the contents of the bytes of the user program.
Command H'4B
• Command, H'4B, (one byte): Sum check for user program
Response H'5B Size Checksum of user program SUM
• Response, H'5B, (one byte): Response to the sum check of the user program • Size (one byte): The number of bytes that represents the checksum This is fixed to 4. • Checksum of user boot program (four bytes): Checksum of user MATs The total of the data is obtained in byte units. • SUM (one byte): Sum check for data being transmitted
Rev. 2.00, 03/04, page 457 of 534
User Boot MAT Blank Check: The boot program will check whether or not all user boot MATs are blank and return the result.
Command H'4C
• Command, H'4C, (one byte): Blank check for user boot MAT
Response H'06
• Response, H'06, (one byte): Response to the blank check of user boot MAT If all user MATs are blank (H'FF), the boot program will return ACK.
Error Response H'CC H'52
• Error Response, H'CC, (one byte): Response to blank check for user boot MAT • Error Code, H'52, (one byte): Erasure has not been completed. User MAT Blank Check: The boot program will check whether or not all user MATs are blank and return the result.
Command H'4D
• Command, H'4D, (one byte): Blank check for user MATs
Response H'06
• Response, H'06, (one byte): Response to the blank check for user boot MATs If the contents of all user MATs are blank (H′FF), the boot program will return ACK.
Error Response H'CD H'52
• Error Response, H'CD, (one byte): Error response to the blank check of user MATs. • Error code, H'52, (one byte): Erasure has not been completed. Boot Program State Inquiry: The boot program will return indications of its present state and error condition. This inquiry can be made in the inquiry/selection state or the programming/erasing state.
Command H'4F
• Command, H'4F, (one byte):
Response H'5F Size
Inquiry regarding boot program's state
ERROR SUM
Status
• Response, H'5F, (one byte): Response to boot program state inquiry • Size (one byte): The number of bytes. This is fixed to 2. • Status (one byte): State of the boot program
Rev. 2.00, 03/04, page 458 of 534
• ERROR (one byte): Error status ERROR = 0 indicates normal operation. ERROR = 1 indicates error has occurred. • SUM (one byte): Sum check Table 14.14 Status Code
Code H'11 H'12 H'13 H'1F H'31 H'3F H'4F H'5F Description Device Selection Wait Clock Mode Selection Wait Bit Rate Selection Wait Programming/Erasing State Transition Wait (Bit rate selection is completed) Programming State for Erasure Programming/Erasing Selection Wait (Erasure is completed) Programming Data Receive Wait Erasure Block Specification Wait (Erasure is completed)
Rev. 2.00, 03/04, page 459 of 534
Table 14.15 Error Code
Code H'00 H'11 H'12 H'21 H'22 H'24 H'25 H'26 H'27 H'29 H'2A H'2B H'51 H'52 H'53 H'54 H'80 H'FF Description No Error Sum Check Error Program Size Error Device Code Mismatch Error Clock Mode Mismatch Error Bit Rate Selection Error Input Frequency Error Multiplication Ratio Error Operating Frequency Error Block Number Error Address Error Data Length Error Erasure Error Erasure Incomplete Error Programming Error Selection Processing Error Command Error Bit-Rate-Adjustment Confirmation Error
Rev. 2.00, 03/04, page 460 of 534
14.10
Usage Notes
1. The initial state of the Renesas Technology's product at its shipment is in the erased state. For the product whose revision of erasing is undefined, we recommend to execute automatic erasure for checking the initial state (erased state) and compensating. 2. For the PROM programmer suitable for programmer mode in this LSI and its program version, refer to the instruction manual of the socket adapter. 3. If the socket, socket adapter, or product index does not match the specifications, too much current flows and the product may be damaged. 4. If a voltage higher than the rated voltage is applied, the product may be fatally damaged. Use a PROM programmer that supports the Renesas Technology's 256 kbytes flash memory on-chip MCU device at 3.3 V. Do not set the programmer to HN28F101 or the programming voltage to 5.0 V. Use only the specified socket adapter. If other adapters are used, the product may be damaged. 5. Do not remove the chip from the PROM programmer nor input a reset signal during programming/erasing. As a high voltage is applied to the flash memory during programming/erasing, doing so may damage or destroy flash memory permanently. If reset is executed accidentally, reset must be released after the reset input period of 100 µs which is longer than normal. 6. The flash memory is not accessible until FKEY is cleared after programming/erasing completes. If this LSI is restarted by a reset immediately after programming/erasing has finished, secure the reset period (period of RES = 0) of more than 100 µs. Though transition to the reset state or hardware standby state during programming/erasing is prohibited, if reset is executed accidentally, reset must be released after the reset input period of 100 µs which is longer than normal. 7. At powering on or off the Vcc power supply, fix the RES pin to low and set the flash memory to hardware protection state. This power on/off timing must also be satisfied at a power-off and power-on caused by a power failure and other factors. 8. Program the area with 128-byte programming-unit blocks in on-board programming or programmer mode only once. Perform programming in the state where the programming-unit block is fully erased. 9. When the chip is to be reprogrammed with the programmer after execution of programming or erasure in on-board programming mode, it is recommended that automatic programming is performed after execution of automatic erasure. 10. To write data or programs to the flash memory, data or programs must be allocated to addresses higher than that of the external interrupt vector table (H'000040) and H’FF must be written to the areas that are reserved for the system in the exception handling vector table.
Rev. 2.00, 03/04, page 461 of 534
11. If data other than H'FF (four bytes) is written to the key code area (H'00003C to H'00003F) of flash memory, reading cannot be performed in programmer mode. (In this case, data is read as H'00. Rewrite is possible after erasing the data.) For reading in programmer mode, make sure to write H'FF to the entire key code area. If data other than H'FF is to be written to the key code area in programmer mode, a verification error will occur unless a software countermeasure is taken for the PROM programmer. 12. The programming program that includes the initialization routine and the erasing program that includes the initialization routine are each 2 kbytes or less. Accordingly, when the CPU clock frequency is 10 MHz, the download for each program takes approximately 600 µs at the maximum. 13. While an instruction in on-chip RAM is being executed, the DMAC can write to the SCO bit in FCCS that is used for a download request or FMATS that is used for MAT switching. Make sure that these registers are not accidentally written to, otherwise an on-chip program may be downloaded and damage RAM or a MAT switchover may occur and the CPU get out of control. Do not use DMAC to program flash related registers. 14. A programming/erasing program for flash memory used in the conventional F-ZTAT H8S microcomputer which does not support download of the on-chip program by a SCO transfer request cannot run in this LSI. Be sure to download the on-chip program to execute programming/erasing of flash memory in this LSI. 15. Unlike the conventional F-ZTAT H8S microcomputer, no countermeasures are available for a runaway by WDT during programming/erasing. Prepare countermeasures (e.g. use of the periodic timer interrupts) for WDT with taking the programming/erasing time into consideration as required. 16. While writing 1 to the SCO bit and downloading the internal programs, the WDT coutup operation stops.
Rev. 2.00, 03/04, page 462 of 534
Section 15 Clock Pulse Generator
This LSI has an on-chip clock pulse generator that generates the system clock (φ) and internal clocks. The clock pulse generator consists of an oscillator circuit and PLL circuit. Figure 15.1 shows a block diagram of the clock pulse generator.
EXTAL Oscillator XTAL PLL circuit (× 2)
System clock to φ pin
Internal clock to peripheral modules
Figure 15.1 Block Diagram of Clock Pulse Generator The frequency can be multiplied by two by means of the PLL circuit.
15.1
Oscillator
Clock pulses can be supplied by connecting a crystal resonator, or by input of an external clock. 15.1.1 Connecting Crystal Resonator
A crystal resonator can be connected as shown in the example in figure 15.2. Select the damping resistance Rd according to table 15.1. An AT-cut parallel-resonance type should be used. When a crystal resonator is used, the range of usable frequencies is from 5 to 16.5 MHz and a crystal resonator with half frequency of the system clock (φ) should be used. Figure 15.3 shows the equivalent circuit of the crystal resonator. Use a crystal resonator that has the characteristics shown in table 15.2.
Rev. 2.00, 03/04, page 463 of 534
CL1 EXTAL XTAL Rd CL2 CL1 = CL2 = 10 to 22 pF
Figure 15.2 Connection of Crystal Resonator (Example) Table 15.1 Damping Resistance Value
Frequency (MHz) Rd (Ω) 5 425 8 200 12 0 16.5 0
CL L XTAL Rs EXTAL AT-cut parallel-resonance type
C0
Figure 15.3 Crystal Resonator Equivalent Circuit Table 15.2 Crystal Resonator Characteristics
Frequency (MHz) RS max (Ω) C0 max (pF) 5 110 7 8 80 7 12 60 7 16.5 50 7
15.1.2
External Clock Input
An external clock signal can be input as shown in the examples in figure 15.4. If the XTAL pin is left open, make sure that parasitic capacitance is no more than 10 pF. When the counter clock is input to the XTAL pin, make sure that the external clock is held high in standby mode. Table 15.3 shows the input conditions for the external clock. When an external clock is used, the range of usable frequencies is from 5 to 16.5 MHz and an external clock with half frequency of the system clock (φ) should be used.
Rev. 2.00, 03/04, page 464 of 534
EXTAL XTAL Open
External clock input
(a) XTAL pin left open
EXTAL XTAL
External clock input
(b) Counter clock input at XTAL pin
Figure 15.4 External Clock Input (Examples) Table 15.3 External Clock Input Conditions
VCC = 3.0 V to 3.6 V Item External clock input low pulse width External clock input high pulse width External clock rise time External clock fall time Clock low pulse width Clock high pulse width Symbol tEXL tEXH tEXr tEXf tCL tCH Min. 10 10 — — 0.4 0.4 Max. — 5 5 0.6 0.6 Unit ns ns ns ns tcyc tcyc Figure 18.2 Test Conditions Figure 15.5
tEXH
tEXL
EXTAL
VCC × 0.5
tEXr
tEXf
Figure 15.5 External Clock Input Timing
Rev. 2.00, 03/04, page 465 of 534
When the specified clock signal is input to the EXTAL pin, an internal clock signal output is ensured after the external clock output stabilization delay time (tDEXT) is passed. Since the clock signal output is not ensured during the tDEXT period, the reset signal should be set to low and the reset state should be retained. Table 15.4 shows the external clock output stabilization delay time and figure 15.6 shows the timing of the external clock output stabilization delay time. Table 15.4 External Clock Output Stabilization Delay Time Conditions: Vcc = 3.0 V to 3.6 V, Vss = 0 V
Item External clock output stabilization delay time Note: * Symbol tDEXT* Min. 500 Max. Unit µs Remark Figure 15.6
tDEXT includes the RES pulse width (tRESW).
VCC
2.7V
VIH
EXTAL φ (internal or external)
tDEXT* Note: * tDEXT includes the pulse width (tRESW).
Figure 15.6 Timing of External Clock Output Stabilization Delay Time
15.2
PLL Circuit
The PLL circuit has the function of multiplying the frequency of the clock from the oscillator by a factor of 2. Therefore, a 16.5-MHz clock should be input to realize the internal 33-MHz operation. The phase of the rising edge of the internal clock is controlled so as to match that of the rising edge of the EXTAL pin.
Rev. 2.00, 03/04, page 466 of 534
15.3
15.3.1
Usage Notes
Notes on Resonator
Since various characteristics related to the resonator are closely linked to the user's board design, thorough evaluation is necessary on the user's part, using the resonator connection examples shown in this section as a guide. As the parameters for the oscillation circuit will depend on the floating capacitance of the resonator and the user board, the parameters should be determined in consultation with the resonator manufacturer. The design must ensure that a voltage exceeding the maximum rating is not applied to the resonator pin. 15.3.2 Notes on Board Design
When using the crystal resonator, 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 oscillation circuit to prevent induction from interfering with correct oscillation. See figure 15.7.
Avoid
Signal A Signal B This LSI CL2 XTAL EXTAL CL1
Figure 15.7 Note on Board Design for Oscillation Circuit 15.3.3 Note on confirming the operation
This LSI may oscillate itself on some kHz frequency even if a crystal resonator is not connected to the EXTAL pin or XTAL pin, or the external clock is not input. Therefore, make sure this LSI is working on the correct frequency before use.
Rev. 2.00, 03/04, page 467 of 534
Rev. 2.00, 03/04, page 468 of 534
Section 16 Power-Down Modes
In addition to the normal program execution state, this LSI has power-down modes in which operation of the CPU and oscillator is halted and power consumption is reduced. Low-power operation can be achieved by individually controlling the CPU, on-chip peripheral modules, and so on. This LSI's operating modes are high-speed mode and four power down modes: • • • • Sleep mode Module stop mode Software standby mode Hardware standby mode
Sleep mode is a CPU state and module stop mode is an on-chip peripheral function state. A combination of these modes can be set. After a reset, this LSI is in high-speed mode. Table 16.1 shows the internal states of this LSI in each mode. Figure 16.1 shows the mode transition diagram.
Rev. 2.00, 03/04, page 469 of 534
Table 16.1 Operating Modes and Internal States of LSI
Operating State Clock pulse generator CPU Instruction execution Register External interrupts Peripheral functions NMI IRQ0 to IRQ7 WDT Functions Functions Functions Halted (Retained) Halted (Retained) Halted (Retained) Halted (Reset) Halted (Retained) Retained Retained Halted (Reset) Functions High-Speed Mode Functions Functions Sleep Mode Functions Halted Module Stop Mode Functions Functions Software Hardware Standby Mode Standby Mode Halted Halted Halted Halted
Retained Functions Functions
Retained Functions
Undefined Halted
TMR
Functions
Functions
Halted (Retained) Functions
Halted (Reset)
DMAC
Functions
Functions
Halted (Reset)
SCI USB2
Functions Functions
Functions Functions
Halted (Reset) Halted (Retained) Functions Functions
Halted (Reset) Halted (Reset)
RAM I/O
Functions Functions
Functions Functions
Retained High impedance
Note: Halted (Retained) in the table means that internal register values are retained and internal operations are suspended. Halted (Reset) in the table means that internal register values and internal states are initialized. In module stop mode, only modules for which a stop setting has been made are halted (reset or retained).
Rev. 2.00, 03/04, page 470 of 534
pin = low Reset state pin = high pin = low
pin = high
Hardware standby mode
SSBY = 0
SLEEP instruction
Sleep mode
High-speed mode (Internal clock is PLL circuit output clock)
Any interrupt SLEEP instruction
SSBY = 1
Software standby mode
Program execution state
: Transition after exception handling
External interrupt* and SUSRI Interrupt
Program-halted state
: Power- down mode
Note: * NMI, to • From any state, a transition to hardware standby mode occurs when is driven low. • From any state except hardware standby mode, a transition to the reset state occurs when is driven low.
Figure 16.1 Mode Transitions
Rev. 2.00, 03/04, page 471 of 534
16.1
Register Descriptions
The registers relating to the power-down mode are shown below. • Standby control register (SBYCR) • Module stop control registers H and L (MSTPCRH, MSTPCRL) 16.1.1 Standby Control Register (SBYCR)
SBYCR performs software standby mode control.
Bit 7 Bit Name SSBY Initial Value 0 R/W R/W Description Software Standby This bit specifies the transition mode after executing the SLEEP instruction 0: Shifts to sleep mode after the SLEEP instruction is executed 1: Shifts to software standby mode after the SLEEP instruction is executed This bit does not change when clearing the software standby mode by using external interrupts and shifting to normal operation. This bit should be written to 0 when clearing. 6 5 4 STS2 STS1 STS0 0 0 0 R/W R/W R/W Standby Timer Select 2 to 0 These bits select the time the MCU waits for the clock to stabilize when software standby mode is cleared. Make a selection according to the operating frequency so that the standby time is at least oscillation stabilization time. Table 16.2 shows the relationship between setting values and number of wait states. With an external clock, any selection is possible. Normally the minimum value is recommended. 3 to 0 All 0 R/W Reserved The initial value should not be changed.
Rev. 2.00, 03/04, page 472 of 534
16.1.2
Module Stop Control Registers H and L (MSTPCRH, MSTPCRL)
MSTPCR performs module stop mode control. Setting a bit to 1, the corresponding module enters module stop mode, while clearing the bit to 0 clears the module stop mode. • MSTPCRH
Bit 7 6 5 4 3 2 1 0 Bit Name TMRCKSTP Initial Value 0* 0* 1* 1 1* 1*
2 2 1 1
R/W R/W R/W R/W R/W R/W R/W R/W R/W
Module 8-bit timer (TMR)
2
1*2 1*
2
• MSTPCRL
Bit 7 6 5 4 3 2 1 0 Note: Bit Name SCICKSTP USBCKSTP Initial Value 1 1*2 1* 1 1* 1* 1* 1*
2 2 2
R/W R/W R/W R/W R/W R/W R/W R/W R/W
Module Serial communication interface (SCI) Universal serial bus interface 2 (USB2)
2
2
*1 This bit must not set to 1. *2 These bits must not be cleared to 0.
Rev. 2.00, 03/04, page 473 of 534
16.2
16.2.1
Operation
Sleep Mode
Transition to Sleep Mode: When the SLEEP instruction is executed while the SSBY bit in SBYCR is set to 0, the CPU enters the sleep mode. In sleep mode, CPU operation stops but the contents of the CPU's internal registers are retained. Other peripheral functions do not stop. Exiting Sleep Mode: Sleep mode is exited by any interrupt, or signals at the RES, or STBY pins. • Exiting sleep mode by interrupts When an interrupt occurs, sleep mode is exited and interrupt exception processing starts. Sleep mode is not exited if the interrupt is disabled, or interrupts other than NMI are masked by the CPU. • Exiting sleep mode by RES pin Setting the RES pin level low selects the reset state. After the stipulated reset input duration, driving the RES pin high starts the CPU performing reset exception processing. • Exiting sleep mode by STBY pin When the STBY pin level is driven low, a transition is made to hardware standby mode. 16.2.2 Software Standby Mode
Transition to Software Standby Mode: If a SLEEP instruction is executed when the SSBY bit in SBYCR is set to 1, software standby mode is entered. In this mode, the CPU, on-chip peripheral functions, and oscillator all stop. However, the contents of the CPU's internal registers, RAM data, and the states of on-chip peripheral functions other than the SCI, and I/O ports, are retained. In this mode the oscillator stops, and therefore power consumption is significantly reduced. Clearing Software Standby Mode: Software standby mode is cleared by an external interrupt (NMI pin, or pins IRQ0 to IRQ7), SUSRI interrupt or by means of the RES pin or STBY pin. • Clearing with an interrupt When an NMI, IRQ0 to IRQ7 or SUSRI interrupt request signal is input, clock oscillation starts, and after the elapse of the time set in bits STS2 to STS0 in SBYCR, stable clocks are supplied to the entire LSI, software standby mode is cleared, and interrupt exception handling is started. When clearing software standby mode with an IRQ0 to IRQ7 or SUSRI interrupt, set the corresponding enable bit to 1 and ensure that no interrupt with a higher priority than interrupts IRQ0 to IRQ7 or SUSRI is generated. Software standby mode cannot be cleared if the interrupt has been masked on the CPU side.
Rev. 2.00, 03/04, page 474 of 534
• Clearing with the RES pin When the RES pin is driven low, clock oscillation is started. At the same time as clock oscillation starts, clocks are supplied to the entire LSI. Note that the RES pin must be held low until clock oscillation stabilizes. When the RES pin goes high, the CPU begins reset exception handling. • Clearing with the STBY pin When the STBY pin is driven low, a transition is made to hardware standby mode. Setting Oscillation Stabilization Time after Clearing Software Standby Mode: Bits STS2 to STS0 in SBYCR should be set as described below. • Using a crystal resonator Set bits STS2 to STS0 so that the standby time is more than the oscillation stabilization time. Table 16.2 shows the standby times for operating frequencies and settings of bits STS2 to STS0. • Using an external clock A PLL circuit stabilization time is necessary. Refer to table 16.2 to set the standby time. Table 16.2 Operating Frequency and Standby Time
STS2 0 STS1 0 STS0 0 1 1 0 1 1 0 0 1 1 0 1 Standby Time 8192 states 16384 states 32768 states 65536 states 131072 states 262144 states Reserved 16 states* 10 MHz 0.8 1.6 3.2 6.5 13.1 26.2 1.6 20 MHz 0.4 0.8 1.6 3.2 6.5 13.1 0.8 33 MHz 0.2 0.4 0.9 1.9 3.9 7.9 0.4 µs Unit ms
: Recommended setting time Note: * This setting must not be used in the flash memory version.
Software Standby Mode Application Example: Figure 16.2 shows an example in which a transition is made to software standby mode at the falling edge on the NMI pin, and software standby mode is cleared at the rising edge on the NMI pin. In this example, an NMI interrupt is accepted with the NMIEG bit in SYSCR cleared to 0 (falling edge specification), then the NMIEG bit is set to 1 (rising edge specification), the SSBY bit is set to 1, and a SLEEP instruction is executed, causing a transition to software standby mode. Software standby mode is then cleared at the rising edge on the NMI pin.
Rev. 2.00, 03/04, page 475 of 534
Oscillator
φ
NMI
NMIEG
SSBY
NMI exception handling NMIEG=1 SSBY=1
Software standby mode (power-down mode)
Oscillation stabilization time tOSC2
NMI exception handling
SLEEP instruction
Figure 16.2 Software Standby Mode Application Example 16.2.3 Hardware Standby Mode
Transition to Hardware Standby Mode: When the STBY pin is driven low, a transition is made to hardware standby mode from any mode. In hardware standby mode, all functions enter the reset state and stop operation, resulting in a significant reduction in power consumption. As long as the prescribed voltage is supplied, on-chip RAM data is retained. I/O ports are set to the high-impedance state. In order to retain on-chip RAM data, the RAME bit in SYSCR should be cleared to 0 before driving the STBY pin low. Do not change the state of the mode pins (MD2, MD1) while this LSI is in hardware standby mode.
Rev. 2.00, 03/04, page 476 of 534
Clearing Hardware Standby Mode: Hardware standby mode is cleared by means of the STBY pin and the RES pin. When the STBY pin is driven high while the RES pin is low, the reset state is set and clock oscillation is started. Ensure that the RES pin is held low until the clock oscillator stabilizes (for details on the oscillation stabilization time, refer to table 16.2). When the RES pin is subsequently driven high, a transition is made to the program execution state via the reset exception handling state. Hardware Standby Mode Timing: Figure 16.3 shows an example of hardware standby mode timing. When the STBY pin is driven low after the RES pin has been driven low, a transition is made to hardware standby mode. Hardware standby mode is cleared by driving the STBY pin high, waiting for the oscillation stabilization time, then changing the RES pin from low to high.
Oscillator
Oscillation stabilization time
Reset exception handling
Figure 16.3 Hardware Standby Mode Timing 16.2.4 Module Stop Mode
Module stop mode can be set for individual on-chip peripheral modules. When the corresponding bit in MSTPCR is set to 1, module operation stops at the end of the bus cycle and a transition is made to module stop mode. The CPU continues operating independently. When the corresponding bit is cleared to 0, module stop mode is cleared and the module starts operating at the end of the bus cycle. In module stop mode, the internal states of modules other than the SCI are retained. After reset clearance, all modules other than the DMAC are in module stop mode. The module registers which are set in module stop mode cannot be read or written to.
Rev. 2.00, 03/04, page 477 of 534
16.3
16.3.1
Usage Notes
I/O Port Status
In software standby mode, I/O port states are retained. Therefore, there is no reduction in current consumption for the output current when a high-level signal is output. 16.3.2 Current Consumption during Oscillation Stabilization Standby Period
Current consumption increases during the oscillation stabilization standby period. 16.3.3 On-Chip Peripheral Module Interrupts
Relevant interrupt operations cannot be performed in module stop mode. Consequently, if module stop mode is entered when an interrupt has been requested, it will not be possible to clear the CPU interrupt source activation source. Interrupts should therefore be disabled before entering module stop mode. 16.3.4 Writing to MSTPCR
MSTPCR should only be written to by the CPU.
Rev. 2.00, 03/04, page 478 of 534
Section 17 List of Registers
This section gives information on the on-chip I/O register addresses, how the register bits are configured, and the register states in each operating mode. The information is given as shown below. 1. • • • 2. • • • Register addresses (address order) Registers are listed from the lower allocation addresses. Registers are classified by functional modules. The access size is indicated.
Register bits Bit configurations of the registers are described in the same order as the register addresses. Reserved bits are indicated by in the bit name column. The bit number in the bit-name column indicates that the whole register is allocated as a counter or for holding data. • For the registers of 16 or 24 bits, the MSB is described first. 3. Register states in each operating mode • Register states are described in the same order as the register addresses. • The register states described here are for the basic operating modes. If there is a specific reset for an on-chip peripheral module, refer to the section on that on-chip peripheral module.
Rev. 2.00, 03/04, page 479 of 534
17.1
Register Addresses (Address Order)
The data bus width indicates the numbers of bits by which the register is accessed. The number of access states indicates the number of states based on the specified reference clock.
Register Name Interrupt flag register 0 Interrupt select register 0 Interrupt enable register 0 EP0o receive data size register EP1 receive data size register EP0i data register EP0o data register EP0s data register EP1 data register EP2 data register EP3 data register 3 Data status register 0 Packet enable register 0i Packet enable register 2 Packet enable register 3 FIFO clear register 0 Endpoint stall register 0 DMA setting register Control register Standby control register Module stop control register H Module stop control register L System control register Mode control register USB suspend status register Access control register CS assertion period control register Number Abbreviation of Bits Address IFR0 ISR0 IER0 EPSZ0o EPSZ1 EPDR0i EPDR0o EPDR0s EPDR1 EPDR2 EPDR3 DASTS0 PKTE0i PKTE2 PKTE3 FCLR0 EPSTL0 DMA0 CTRL SBYCR MSTPCRH MSTPCRL SYSCR MDCR USBSUSP ACSCR CSACR 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 8 8 8 8 8 8 8 8 H'FD00 H'FD04 H'FD08 H'FD0C H'FD10 H'FD14 H'FD18 H'FD1C H'FD20 H'FD30 H'FD40 H'FD44 H'FD48 H'FD4C H'FD50 H'FD54 H'FD58 H'FD5C H'FD60 H'FE14 H'FE16 H'FE17 H'FE1C H'FE1D H'FE1E H'FE20 H'FE21 Module USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 USB2 SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM USB2 BSC BSC Data Width 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 8 8 8 8 8 8 16 16 Access States 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
Rev. 2.00, 03/04, page 480 of 534
Register Name Wait control register Bus control register Read strobe timing control register RAM emulation register DRAM control register DRAM access control register Refresh control register Refresh timer counter Refresh time constant register Timer control/status register Timer counter Flash code control/status register Flash program code select register
Number Abbreviation of Bits Address WTCR BCR RDNCR RAMER DRAMCR DRACCR REFCR RTCNT RTCOR TCSR TCNT FCCS FPCS 16 16 8 8 16 8 16 8 8 8 8 8 8 8 8 8 8 32 32 32 16 16 32 32 32 16 16 H'FE22 H'FE24 H'FE26 H'FE27 H'FE28 H'FE2A H'FE2C H'FE2E H'FE2F H'FE70 H'FE71 H'FE88 H'FE89 H'FE8A H'FE8C H'FE8D H'FE8E H'FEB0 H'FEB4 H'FEB8 H'FEBC H'FEBE H'FEC0 H'FEC4 H'FEC8 H'FECC H'FECE
Module BSC BSC BSC FLASH BSC BSC BSC BSC BSC WDT WDT FLASH FLASH FLASH FLASH FLASH FLASH DMAC_0 DMAC_0 DMAC_0 DMAC_0 DMAC_0 DMAC_1 DMAC_1 DMAC_1 DMAC_1 DMAC_1
Data Width 16 16 16 16 16 16 16 16 16 16 16 8 8 8 8 8 8 16 16 16 16 16 16 16 16 16 16
Access States 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
Flash erase code select register FECS Flash key code register Flash MAT select register Flash transfer destination address register FKEY FMATS FTDAR
DMA source address register_0 DMSAR_0 DMA destination address register_0 DMA transfer count register_0 DMA mode control register_0 DMDAR_0 DMTCR_0 DMMDR_0
DMA address control register_0 DMACR_0 DMA source address register_1 DMSAR_1 DMA destination address register_1 DMA transfer count register_1 DMA mode control register_1 DMDAR_1 DMTCR_1 DMMDR_1
DMA address control register_1 DMACR_1
Rev. 2.00, 03/04, page 481 of 534
Register Name
Number Abbreviation of Bits Address 32 32 32 16 16 32 32 32 16 16 16 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 H'FED0 H'FED4 H'FED8 H'FEDC H'FEDE H'FEE0 H'FEE4 H'FEE8 H'FEEC H'FEEE H'FEF0 H'FF46 H'FF48 H'FF49 H'FF4A H'FF4B H'FF4C H'FF4D H'FF54 H'FF55 H'FF56 H'FF57 H'FF5D H'FF60 H'FF62 H'FF70 H'FF71 H'FF72 H'FF73 H'FF74 H'FF75 H'FF76
Module DMAC_2 DMAC_2 DMAC_2 DMAC_2 DMAC_2 DMAC_3 DMAC_3 DMAC_3 DMAC_3 DMAC_3 DMAC INT INT INT INT INT INT INT INT INT INT INT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT
Data Width 16 16 16 16 16 16 16 16 16 16 16 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
Access States 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
DMA source address register_2 DMSAR_2 DMA destination address register_2 DMA transfer count register_2 DMA mode control register_2 DMDAR_2 DMTCR_2 DMMDR_2
DMA address control register_2 DMACR_2 DMA source address register_3 DMSAR_3 DMA destination address register_3 DMA transfer count register_3 DMA mode control register_3 DMDAR_3 DMTCR_3 DMMDR_3
DMA address control register_3 DMACR_3 USB transfer control register IRQ enable register Interrupt control register A Interrupt control register B Interrupt control register C IRQ status register IRQ sense control register H IRQ sense control register L Address break control register Break address register A Break address register B Break address register C IRQ sense port select register Port function control register 1 Port function control register 3 Port 1 data direction register Port 2 data direction register Port 3 data direction register Port 4 data direction register Port 5 data direction register Port 6 data direction register Port 7 data direction register USTCR IER ICRA ICRB ICRC ISR ISCRH ISCRL ABRKCR PBARA PBARB PBARC ISSR PFCR1 PFCR3 P1DDR P2DDR P3DDR P4DDR P5DDR P6DDR P7DDR
Rev. 2.00, 03/04, page 482 of 534
Register Name Port 8 data direction register Port 9 data direction register Port A data direction register Serial mode register Bit rate register Serial control register Transmit data register Serial status register Receive data register Port 1 register Port 2 register Port 3 register Port 4 register Port 5 register Port 6 register Port 7 register Port 8 register Port 9 register Port A register Port 1 data register Port 2 data register Port 3 data register Port 4 data register Port 5 data register Port 6 data register Port 7 data register Port 8 data register Port 9 data register Port A data register Timer control register 0 Timer control register 1 Timer control/status register 0 Timer control/status register 1
Number Abbreviation of Bits Address P8DDR P9DDR PADDR SMR BRR SCR TDR SSR RDR PORT1 PORT2 PORT3 PORT4 PORT5 PORT6 PORT7 PORT8 PORT9 PORTA P1DR P2DR P3DR P4DR P5DR P6DR P7DR P8DR P9DR PADR TCR_0 TCR_1 TCSR_0 TCSR1 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 H'FF77 H'FF78 H'FF79 H'FF88 H'FF89 H'FF8A H'FF8B H'FF8C H'FF8D H'FFC0 H'FFC1 H'FFC2 H'FFC3 H'FFC4 H'FFC5 H'FFC6 H'FFC7 H'FFC8 H'FFC9 H'FFD0 H'FFD1 H'FFD2 H'FFD3 H'FFD4 H'FFD5 H'FFD6 H'FFD7 H'FFD8 H'FFD9 H'FFE0 H'FFE1 H'FFE2 H'FFE3
Module PORT PORT PORT SCI SCI SCI SCI SCI SCI PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT TMR_0 TMR_1 TMR_0 TMR_1
Data Width 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 16 16 16 16
Access States 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
Rev. 2.00, 03/04, page 483 of 534
Register Name Time constant register A0 Time constant register A1 Time constant register B0 Time constant register B1 Timer counter 0 Timer counter 1
Number Abbreviation of Bits Address TCORA_0 TCORA_1 TCORB_0 TCORB_1 TCNT_0 TCNT1 8 8 8 8 8 8 H'FFE4 H'FFE5 H'FFE6 H'FFE7 H'FFE8 H'FFE9
Module TMR_0 TMR_1 TMR_0 TMR_1 TMR_0 TMR_1
Data Width 16 16 16 16 16 16
Access States 2 2 2 2 2 2
Rev. 2.00, 03/04, page 484 of 534
17.2
Register Bits
Register bit names of the on-chip peripheral modules are described below. Each line covers eight bits, and 16-bit and 32-bit registers are shown as 2 or 4 lines, respectively.
Register Abbreviation Bit 7
Bit 6 EP2TR EP2TR EP2TR D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Module
IFR0
BRST BRST BRST
MODEMN1MODEMN0
MODEF USB2
VBUSMN VBUSF
EP3TR EP3TR EP3TR
EP3TS
EP2EMPTY EP1FULL SETUPTS EP0oTS
EP0ITR EP0ITS MODEF VBUSF EP3TS
ISR0
EP2EMPTY EP1FULL SETUPTS EP0oTS
EP0iTR EP0iTS MODEF VBUSF EP3TS
IER0
EP2EMPTY EP1FULL SETUPTS EP0oTS
EP0iTR EP0iTS D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1 D24 D16 D8 D0 D24 D16 D8 D0 D24 D16 D8 D0 D24 D16 D8 D0
EPSZ0o
D31 D23 D15 D7
D29 D21 D13 D5 D29 D21 D13 D5 D29 D21 D13 D5 D29 D21 D13 D5
D28 D20 D12 D4 D28 D20 D12 D4 D28 D20 D12 D4 D28 D20 D12 D4
D27 D19 D11 D3 D27 D19 D11 D3 D27 D19 D11 D3 D27 D19 D11 D3
D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2
EPSZ1
D31 D23 D15 D7
EPDR0i
D31 D23 D15 D7
EPDR0o
D31 D23 D15 D7
Rev. 2.00, 03/04, page 485 of 534
Register Abbreviation Bit 7
Bit 6 D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6 D30 D22 D14 D6
Bit 5 D29 D21 D13 D5 D29 D21 D13 D5 D29 D21 D13 D5 D29 D21 D13 D5
Bit 4 D28 D20 D12 D4 D28 D20 D12 D4 D28 D20 D12 D4 D28 D20 D12 D4
Bit 3 D27 D19 D11 D3 D27 D19 D11 D3 D27 D19 D11 D3 D27 D19 D11 D3
Bit 2 D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2 D26 D18 D10 D2
Bit 1 D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1 D25 D17 D9 D1
Bit 0 D24 D16 D8 D0 D24 D16 D8 D0 D24 D16 D8 D0 D24 D16 D8 D0 EP0IDE D24 D16 D8 D0 D24 D16 D8 D0 D24 D16 D8 D0
Module USB2
EPDR0s
D31 D23 D15 D7
EPDR1
D31 D23 D15 D7
EPDR2
D31 D23 D15 D7
EPDR3
D31 D23 D15 D7
DASTS0
EP3DE EP2DE D29 D21 D13 D5 D29 D21 D13 D5 D29 D21 D13 D5 D28 D20 D12 D4 D28 D20 D12 D4 D28 D20 D12 D4 D27 D19 D11 D3 D27 D19 D11 D3 D27 D19 D11 D3
PKTE0i
D31 D23 D15 D7
PKTE2
D31 D23 D15 D7
PKTE3
D31 D23 D15 D7
Rev. 2.00, 03/04, page 486 of 534
Register Abbreviation Bit 7
Bit 6 STS2
Bit 5 STS1 INTM1
Bit 4 STS0
Bit 3 XRST
Bit 2
Bit 1 ASCE
Bit 0
PULLUPE
Module USB2
FCLR0
EP3CLR EP2CLR EP1CLR
EP0oCLR EP0iCLR
EPSTL0
EP3STL EP2STL EP1STL EP0STL
DMA0
EP2DMAE EP1DMAE
CTRL
SBYCR MSTPCRH MSTPCRL SYSCR MDCR USBSUSP ACSCR CSACR WTCR
SSBY
SCICKSTP
RAME MDS0 AST0
SYSTEM
TMRCKSTP USBCKSTP
EXPE
INTM0
NMIEG MDS2 AST2 MDS1 AST1
USUSMONI USUSFG USUSFGE USUSOUT
USB2 BSC
ABW3
ABW2
ABW1
ABW0
AST3 IDLE1 RAMS
CSXH3 CSXH2 CSXH1 CSXH0 CSXT3 CSXT2 CSXT1 CSXT0 W32 W12 RDN2 RAST RCDM W31 W11 RDN1 DDS TPC1 W30 W10 RDN0 CAST TPC0 W22 W02 IDLE0 RAM2 MXC2 W21 W01 IDLC1 RAM1 MXC1 RCD1 W20 W00 WDBE IDLC0 RAM0 DSET MXC0 RCD0 FLASH BSC
BCR
RDNCR RAMER DRAMCR
RDN3 BE
DRACCR
Rev. 2.00, 03/04, page 487 of 534
Register Abbreviation Bit 7
Bit 6 CMIE
Bit 5 RCW1 RLW1 Bit5 Bit5 TME Bit5 K5 MS5 TDA5 Bit21 Bit13 Bit5 Bit21 Bit13 Bit5 Bit21 Bit13 Bit5
Bit 4 RCW0 RLW0 Bit4 Bit4 Bit4 FLER PPVD K4 MS4 TDA4 Bit20 Bit12 Bit4 Bit20 Bit12 Bit4 Bit20 Bit12 Bit4
Bit 3
Bit 2
Bit 1
Bit 0
Module
REFCR
CMF
RTCK2 RTCK1 RTCK0 BSC
RFSHE RTCNT RTCOR TCSR TCNT FCCS FPCS FECS FKEY FMATS FTDAR DMSAR_0 Bit7 Bit7 OVF Bit7 FWE K7 MS7 TDER Bit23 Bit15 Bit7 DMDAR_0 Bit23 Bit15 Bit7 DMTCR_0 Bit23 Bit15 Bit7 DMMDR_0 DA DIE DMACR_0 SAT1 DAT1 DMSAR_1 Bit23 Bit15 Bit7 Bit6 Bit6 WT/IT Bit6 K6 MS6 TDA6 Bit22 Bit14 Bit6 Bit22 Bit14 Bit6 Bit22 Bit14 Bit6 BEF IRF SAT0 DAT0 Bit22 Bit14 Bit6
SLFRF TPCS2 TPCS1 TPCS0 Bit3 Bit3 Bit2 Bit2 Bit1 Bit1 CKS1 Bit1 K1 MS1 TDA1 Bit17 Bit9 Bit1 Bit25 Bit17 Bit9 Bit1 Bit17 Bit9 Bit1 MDS1 Bit0 Bit0 CKS0 Bit0 SCO PPVS EPVB K0 MS0 TDA0 Bit16 Bit8 Bit0 Bit24 Bit16 Bit8 Bit0 Bit16 Bit8 Bit0 MDS0 DMAC_0 FLASH WDT
RST/NMICKS2 Bit3 K3 MS3 TDA3 Bit19 Bit11 Bit3 Bit19 Bit11 Bit3 Bit19 Bit11 Bit3 Bit2 K2 MS2 TDA2 Bit18 Bit10 Bit2 Bit18 Bit10 Bit2 Bit18 Bit10 Bit2 WEINTE
DRAKE TENDE DREQS AMS TCEIE SARIE DARIE Bit21 Bit13 Bit5 SDIR DTSIZE
LWSIZE
SARA4 SARA3 SARA2 SARA1 SARA0 DARA4 DARA3 DARA2 DARA1 DARA0 Bit20 Bit12 Bit4 Bit19 Bit11 Bit3 Bit18 Bit10 Bit2 Bit17 Bit9 Bit1 Bit16 Bit8 Bit0 DMAC_1
Rev. 2.00, 03/04, page 488 of 534
Register Abbreviation Bit 7
Bit 6 Bit22 Bit14 Bit6 Bit22 Bit14 Bit6 BEF IRF SAT0 DAT0 Bit22 Bit14 Bit6 Bit22 Bit14 Bit6 Bit22 Bit14 Bit6 BEF IRF SAT0 DAT0 Bit22 Bit14 Bit6
Bit 5 Bit21 Bit13 Bit5 Bit21 Bit13 Bit5
Bit 4 Bit20 Bit12 Bit4 Bit20 Bit12 Bit4
Bit 3 Bit19 Bit11 Bit3 Bit19 Bit11 Bit3
Bit 2 Bit18 Bit10 Bit2 Bit18 Bit10 Bit2
Bit 1 Bit17 Bit9 Bit1 Bit17 Bit9 Bit1 MDS1
Bit 0 Bit16 Bit8 Bit0 Bit16 Bit8 Bit0 MDS0
Module DMAC_1
DMDAR_1
Bit23 Bit15 Bit7 Bit23 Bit15 Bit7
DMTCR_1
DMMDR_1
DA DIE
DRAKE TENDE DREQS AMS TCEIE SARIE DARIE Bit21 Bit13 Bit5 Bit21 Bit13 Bit5 Bit21 Bit13 Bit5 SDIR DTSIZE
LWSIZE
DMACR_1
SAT1 DAT1 Bit23 Bit15 Bit7 Bit23 Bit15 Bit7 Bit23 Bit15 Bit7
SARA4 SARA3 SARA2 SARA1 SARA0 DARA4 DARA3 DARA2 DARA1 DARA0 Bit20 Bit12 Bit4 Bit20 Bit12 Bit4 Bit20 Bit12 Bit4 Bit19 Bit11 Bit3 Bit19 Bit11 Bit3 Bit19 Bit11 Bit3 Bit18 Bit10 Bit2 Bit18 Bit10 Bit2 Bit18 Bit10 Bit2 Bit17 Bit9 Bit1 Bit25 Bit17 Bit9 Bit1 Bit17 Bit9 Bit1 MDS1 Bit16 Bit8 Bit0 Bit24 Bit16 Bit8 Bit0 Bit16 Bit8 Bit0 MDS0 DMAC_2
DMSAR_2
DMDAR_2
DMTCR_2
DMMDR_2
DA DIE
DRAKE TENDE DREQS AMS TCEIE SARIE DARIE Bit21 Bit13 Bit5 SDIR DTSIZE
LWSIZE
DMACR_2
SAT1 DAT1 Bit23 Bit15 Bit7
SARA4 SARA3 SARA2 SARA1 SARA0 DARA4 DARA3 DARA2 DARA1 DARA0 Bit20 Bit12 Bit4 Bit19 Bit11 Bit3 Bit18 Bit10 Bit2 Bit17 Bit9 Bit1 Bit16 Bit8 Bit0 DMAC_3
DMSAR_3
Rev. 2.00, 03/04, page 489 of 534
Register Abbreviation Bit 7
Bit 6 Bit22 Bit14 Bit6 Bit22 Bit14 Bit6 BEF IRF SAT0 DAT0 IRQ6E ICRA6 ICRB6 ICRC6 IRQ6F
Bit 5 Bit21 Bit13 Bit5 Bit21 Bit13 Bit5 DRAKE TCEIE SARIE DARIE IRQ5E ICRA5 ICRB5 ICRC5 IRQ5F
Bit 4 Bit20 Bit12 Bit4 Bit20 Bit12 Bit4
Bit 3 Bit19 Bit11 Bit3 Bit19 Bit11 Bit3
Bit 2 Bit18 Bit10 Bit2 Bit18 Bit10 Bit2
Bit 1 Bit25 Bit17 Bit9 Bit1 Bit17 Bit9 Bit1 MDS1
Bit 0 Bit24 Bit16 Bit8 Bit0 Bit16 Bit8 Bit0 MDS0
Module DMAC_3
DMDAR_3
Bit23 Bit15 Bit7
DMTCR_3
Bit23 Bit15 Bit7
DMMDR_3
DA DIE
TENDE DREQS AMS SDIR DTSIZE
LWSIZE
DMACR_3
SAT1 DAT1
SARA4 SARA3 SARA2 SARA1 SARA0 DARA4 DARA3 DARA2 DARA1 DARA0
EP2DMAE UWCHS1 UWCHS0
USTCR IER ICRA ICRB ICRC ISR ISCRH ISCRL ABRKCR PBARA PBARB PBARC ISSR PFCR1 PFCR3 P1DDR P2DDR P3DDR P4DDR P5DDR P6DDR
EP1DMAE URCHS1URCHS0
DMAC INT
IRQ7E ICRA7 ICRB7 ICRC7 IRQ7F
IRQ4E ICRA4 ICRB4 ICRC4 IRQ4F
IRQ3E ICRA3 ICRB3 ICRC3 IRQ3F
IRQ2E ICRA2 ICRB2 ICRC2 IRQ2F
IRQ1E ICRA1 ICRB1 ICRC1 IRQ1F
IRQ0E ICRA0 ICRB0 ICRC0 IRQ0F
IRQ7SCB IRQ7SCA IRQ6SCB IRQ6SCA IRQ5SCB IRQ5SCA IRQ4SCB IRQ4SCA IRQ3SCB IRQ3SCA IRQ2SCB IRQ2SCA IRQ1SCB IRQ1SCA IRQ0SCB IRQ0SCA
CMF A23 A15 A7 ISS7
A22 A14 A6 ISS6 CS1E
A21 A13 A5 ISS5 CS2E
A20 A12 A4 ISS4 CS3E
A19 A11 A3 ISS3 CKOE
A18 A10 A2 ISS2 ALOE
A17 A9 A1 ISS1 AMOE
BIE A16 A8 ISS0 AHOE
USBSWRST
PORT
SUSRIF SUSRIE
P17DDR P16DDR P15DDR P14DDR P13DDR P12DDR P11DDR P10DDR P27DDR P26DDR P25DDR P24DDR P23DDR P22DDR P21DDR P20DDR P37DDR P36DDR P35DDR P34DDR P33DDR P32DDR P31DDR P30DDR P47DDR P46DDR P45DDR P44DDR P43DDR P42DDR P41DDR P40DDR P57DDR P56DDR P55DDR P54DDR P53DDR P52DDR P51DDR P50DDR P67DDR P66DDR P65DDR P64DDR P63DDR P62DDR P61DDR P60DDR
Rev. 2.00, 03/04, page 490 of 534
Register Abbreviation Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Module
P7DDR P8DDR P9DDR PADDR SMR BRR SCR TDR SSR RDR PORT1 PORT2 PORT3 PORT4 PORT5 PORT6 PORT7 PORT8 PORT9 PORTA P1DR P2DR P3DR P4DR P5DR P6DR P7DR P8DR P9DR PADR TCR_0 TCR_1 TCSR_0
P77DDR P76DDR P75DDR P74DDR P73DDR P72DDR P71DDR P70DDR PORT P87DDR P86DDR P85DDR P84DDR P83DDR P82DDR P81DDR P80DDR P97DDR P96DDR P95DDR P94DDR P93DDR P92DDR P91DDR P90DDR C/A Bit7 TIE Bit7 TDRE Bit7 P17 P27 P37 P47 P57 P67 P77 P87 P97 CHR Bit6 RIE Bit6 RDRF Bit6 P16 P26 P36 P46 P56 P66 P76 P86 P96 PE Bit5 TE Bit5 ORER Bit5 P15 P25 P35 P45 P55 P65 P75 P85 P95 O/E Bit4 RE Bit4 FER Bit4 P14 P24 P34 P44 P54 P64 P74 P84 P94 PA3DDR PA2DDR PA1DDR PA0DDR STOP Bit3 Bit3 PER Bit3 P13 P23 P33 P43 P53 P63 P73 P83 P93 PA3 Bit2 TEIE Bit2 TEND Bit2 P12 P22 P32 P42 P52 P62 P72 P82 P92 PA2 CKS1 Bit1 CKE1 Bit1 Bit1 P11 P21 P31 P41 P51 P61 P71 P81 P91 PA1 CKS0 Bit0 CKE0 Bit0 Bit0 P10 P20 P30 P40 P50 P60 P70 P80 P90 PA0 PORT SCI
RxDMON
P17DR P16DR P15DR P14DR P13DR P12DR P11DR P10DR P27DR P26DR P25DR P24DR P23DR P22DR P21DR P20DR P37DR P36DR P35DR P34DR P33DR P32DR P31DR P30DR P47DR P46DR P45DR P44DR P43DR P42DR P41DR P40DR P57DR P56DR P55DR P54DR P53DR P52DR P51DR P50DR P67DR P66DR P65DR P64DR P63DR P62DR P61DR P60DR P77DR P76DR P75DR P74DR P73DR P72DR P71DR P70DR P87DR P86DR P85DR P84DR P83DR P82DR P81DR P80DR P97DR P96DR P95DR P94DR P93DR P92DR P91DR P90DR PA3DR PA2DR PA1DR PA0DR CKS1 CKS1 OS1 CKS0 CKS0 OS0 TMR_0 TMR_1 TMR_0
CMIEB CMIEA OVIE CMIEB CMIEA OVIE CMFB CMFA OVF
CCLR1 CCLR0 CKS2 CCLR1 CCLR0 CKS2 OS3 OS2
Rev. 2.00, 03/04, page 491 of 534
Register Abbreviation Bit 7
Bit 6 CMFA Bit6 Bit6 Bit6 Bit6 Bit6 Bit6
Bit 5 OVF Bit5 Bit5 Bit5 Bit5 Bit5 Bit5
Bit 4 Bit4 Bit4 Bit4 Bit4 Bit4 Bit4
Bit 3 OS3 Bit3 Bit3 Bit3 Bit3 Bit3 Bit3
Bit 2 OS2 Bit2 Bit2 Bit2 Bit2 Bit2 Bit2
Bit 1 OS1 Bit1 Bit1 Bit1 Bit1 Bit1 Bit1
Bit 0 OS0 Bit0 Bit0 Bit0 Bit0 Bit0 Bit0
Module TMR_1 TMR_0 TMR_1 TMR_0 TMR_1 TMR_0 TMR_1
TCSR1 TCORA_0 TCORA_1 TCORB_0 TCORB_1 TCNT_0 TCNT1
CMFB Bit7 Bit7 Bit7 Bit7 Bit7 Bit7
Rev. 2.00, 03/04, page 492 of 534
17.3
Register States in Each Operating Mode
Module Stop Software Hardware Standby Standby Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized USB2 BSC SYSTEM Module USB2
Register Power-on Normal Abbreviation Reset Operation Sleep IFR0 ISR0 IER0 EPSZ0o EPSZ1 EPDR0i EPDR0o EPDR0s EPDR1 EPDR2 EPDR3 DASTS0 PKTE0i PKTE2 PKTE3 FCLR0 EPSTL0 DMA0 CTRL SBYCR MSTPCRH MSTPCRL SYSCR MDCR USBSUSP ACSCR CSACR WTCR BCR RDNCR RAMER Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Rev. 2.00, 03/04, page 493 of 534
Register Power-on Normal Abbreviation Reset Operation Sleep DRAMCR DRACCR REFCR RTCNT RTCOR TCSR TCNT FCCS FPCS FECS FKEY FMATS FTDAR DMSAR_0 DMDAR_0 DMTCR_0 DMMDR_0 DMACR_0 DMSAR_1 DMDAR_1 DMTCR_1 DMMDR_1 DMACR_1 DMSAR_2 DMDAR_2 DMTCR_2 DMMDR_2 DMACR_2 DMSAR_3 DMDAR_3 DMTCR_3 DMMDR_3 DMACR_3 Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Module Stop
Software Hardware Standby Standby Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Module BSC
WDT
FLASH
DMAC_0
DMAC_1
DMAC_2
DMAC_3
Rev. 2.00, 03/04, page 494 of 534
Register Power-on Normal Abbreviation Reset Operation Sleep USTCR IER ICRC ICRB ICRA ISR ISCRH ISCRL ABRKCR PBARA PBARB PBARC ISSR PFCR1 PFCR3 P1DDR P2DDR P3DDR P4DDR P5DDR P6DDR P7DDR P8DDR P9DDR PADDR SMR BRR SCR TDR SSR RDR PORT1 PORT2 Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Module Stop
Software Hardware Standby Standby Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Module DMAC INT
PORT
SCI
Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized PORT
Rev. 2.00, 03/04, page 495 of 534
Register Power-on Normal Abbreviation Reset Operation Sleep PORT3 PORT4 PORT5 PORT6 PORT7 PORT8 PORT9 PORTA P1DR P2DR P3DR P4DR P5DR P6DR P7DR P8DR P9DR PADR TCR_0 TCR_1 TCSR_0 TCSR_1 TCORA_0 TCORA_1 TCORB_0 TCORB_1 TCNT_0 TCNT_1 Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Module Stop
Software Hardware Standby Standby Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized Initialized
Module PORT
TMR_0 TMR_1 TMR_0 TMR_1 TMR_0 TMR_1 TMR_0 TMR_1 TMR_0 TMR_1
Note: is not initialized.
Rev. 2.00, 03/04, page 496 of 534
Section 18 Electrical Characteristics
18.1 Absolute Maximum Ratings
Table 18.1 lists the absolute maximum ratings. Table 18.1 Absolute Maximum Ratings
Item Power supply voltage Input voltage Program voltage (FWE) Operating temperature Symbol VCC* Vin Vin Topr Topr Value −0.3 to +4.3 −0.3 to VCC +0.3 −0.3 to VCC +0.3 Regular specifications: −20 to +75 Wide-range specifications: −40 to +85 Operating temperature (Flashmemory programing/erasure) Storage temperature Caution: Notes: * 0 to +75 Unit V V V °C °C °C
Tstg
−55 to +125
°C
Permanent damage to the LSI may result if absolute maximum ratings are exceeded. Do not apply the power supply voltage to the VCL pin. If applied, permanent damage to the LSI may result. Connect the external capacitor between this pin and GND.
Rev. 2.00, 03/04, page 497 of 534
18.2
DC Characteristics
Table 18.2 DC Characteristics (1) Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V
Item Schmitt trigger input voltage Input high voltage Symbol P34*1, P35*1, VT− 1 1 P52* , P53* , VT+ 1 1 P56* , P57* , port + − 7*1, PA0*1, PA1*1 VT − VT STBY, MD2, MD1 RES, NMI, FWE EXTAL Port 1 to Port 9, Port A*2 Input low voltage RES, STBY, MD2, MD1, FWE NMI, EXTAL Port 1 to Ports 9, Port A*2 Output high voltage Output low voltage Input leakage current All output pins VOH VOL
| lin |
Min. VCC × 0.2 VCC × 0.05 VCC × 0.9 VCC × 0.9 VCC × 0.7 2.2
Typ.
Max. VCC × 0.7 VCC + 0.3 VCC + 0.3 VCC + 0.3 VCC + 0.3 VCC × 0.1 VCC × 0.2 VCC × 0.2 0.4 10.0 1.0
Unit V V V V V V V V V V V V V
µA µA
Test Conditions
VIH
VIL
−0.3 −0.3 −0.3 VCC − 0.5 VCC − 1.0
IOH = −200 µA IOH = −1 mA IOL = 1.6 mA Vin = 0.5 to VCC- 0.5 V
All output pins RES STBY, NMI, MD2, MD1, FWE
Notes: 1. When used as IRQ0 to IRQ7. 2. When used as other than IRQ0 to IRQ7.
Rev. 2.00, 03/04, page 498 of 534
Table 18.3 DC Characteristics (2) Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V
Item Three-state Port 1 to Port 9, leakage current Port A (off state) Input capacitance RES NMI All input pins except RES and NMI Current consumption*1 Normal operation Sleep mode Standby mode*
2
Symbol | ITSI |
Min.
Typ.
Max. 1.0
Unit µA
Test Conditions Vin = 0.5 to VCC − 0.5 V Vin = 0 V f = 1 MHz Ta = 25°C f = 33 MHz f = 33 MHz Ta ≤ 50°C 50°C < Ta *4 *4
Cin
50 38 30 0
10 10 10 65 48 90 120 0.8 20
pF pF pF mA mA µA µA V V ms/V
ICC*3
RAM standby voltage Vcc start power supply Vcc rising gradient
VRAM VCCSTART SVCC
3.0
Notes: 1. Current consumption values are for VIHmin = VCC − 0.2 V and VILmax = 0.2 V with all output pins unloaded. 2. The values are for VCC = 3.0 V, VIHmin = VCC × 0.9, and VILmax = 0.3 V. 3. ICC depends on VCC and f as follows: ICCmax = 6.5 (mA) + 0.49 (mA/(MHz × V)) × VCC × f (normal operation) ICCmax = 6.5 (mA) + 0.35 (mA/(MHz × V)) × VCC × f (sleep mode) 4. These values are measured when the RES pin is low.
Rev. 2.00, 03/04, page 499 of 534
Table 18.4 Permissible Output Currents Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V
Item Permissible output low current (per pin) Ports 1 and 4 All output pins execept ports 1 and 4 Total of all output pins ΣIOL −IOH Symbol IOL Min. Typ. Max. 1.6 2 60 2 30 mA mA mA Unit mA
Permissible output low current (total)
Permissible output high All output pins current (per pin)
Permissible output high Total of all output pins Σ−IOH current (total) Caution:
1. To protect the LSI’s reliability, do not exceed the output current values in table 18.4. 2. To drive the Darlington transistor directly, inset a current-limit resister between the LSI and the transistor, as shown in figure 18.1.
This LSI 2 kΩ Port
Darlington transistor
Figure 18.1 Sample of Dalington Transistor Drive Circuit
Rev. 2.00, 03/04, page 500 of 534
18.3
AC Characteristics
3V
RL C = 50 pF: ports 5 to 9, port A C = 30 pF: ports 1 to 4 RL = 2.4 kΩ RH = 12 kΩ Input/output timing measurement level: 1.5 V (VCC = 3.0 V to 3.6 V) C RH
LSI output pin
Figure 18.2 Output Load Circuit 18.3.1 Clock Timing
Table 18.5 Clock Timing Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V, φ = 10 MHz to 33 MHz
Item Clock cycle time Clock pulse high width Clock pulse low width Clock rise time Clock fall time Reset oscillation stabilization time (crystal) Software standby oscillation stabilization time (crystal) External clock output delay stabilization time Symbol tcyc tCH tCL tCr tCf tOSC1 tOSC2 tDEXT Min. 30.3 10 10 10 8 3.9 500 Max. 100 5 5 Unit ns ns ns ns ns ms ms ms µs Figure 18.4 φ < 30 MHz Figure 18.5 φ ≥ 30 MHz Figure 18.4 Test Conditions Figure 18.3
Rev. 2.00, 03/04, page 501 of 534
tcyc tCH φ tCL tCr tCf Input/output timing measurement level : Low level : 0.8 V High level : 1.5 V
Figure 18.3 System Clock Timing
EXTAL tDEXT VCC tDEXT
tOSC1
tOSC1
φ
Figure 18.4 Oscillation Stabilization Timing (1)
Oscillator
φ
NMI
NMIEG
SSBY NMI exception handling NMI exception handling NMIEG = 1 SSBY = 1 Software standby mode (power-down mode) Oscillation stabilization time tOSC2
SLEEP instruction
Figure 18.5 Oscillation Stabilization Timing (2)
Rev. 2.00, 03/04, page 502 of 534
18.3.2
Control Signal Timing
Table 18.6 Control Signal Timing Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V, φ = 10 MHz to 33 MHz
Item RES setup time RES pulse width NMI setup time NMI hold time NMI pulse width (in recovery from software standby mode) IRQ setup time IRQ hold time IRQ pulse width (in recovery from software standby mode) Symbol tRESS tRESW tNMIS tNMIH tNMIW tIRQS tIRQH tIRQW Min. 200 20 150 10 200 150 10 200 Max. ns Unit ns tcyc ns Figure 18.7 Test Conditions Figure 18.6
φ tRESS tRESS
tRESW
Figure 18.6 Reset Input Timing
φ tNMIS tNMIH NMI tNMIW tIRQW (i = 0 to 7) tIRQS tIRQH (edge input) tIRQS (level input)
Figure 18.7 Interrupt Input Timing
Rev. 2.00, 03/04, page 503 of 534
18.3.3
Bus Timing
Table 18.7 Bus Timing (1) Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V, φ = 10 MHz to 33 MHz
Item Address delay time Address setup time 1 Address setup time 2 Address setup time 3 Address setup time 4 Address hold time 1 Address hold time 2 Address hold time 3 CS delay time 1 CS delay time 2 CS delay time 3 AS delay time RD delay time 1 RD delay time 2 Read data setup time 1 Read data setup time 2 Read data hold time 1 Read data hold time 2 Read data access time 1 Read data access time 2 Read data access time 3 Read data access time 4 Read data access time 5 Read data access time 6 Read data access time 7 Read data access time 8 Symbol tAD tAS1 tAS2 tAS3 tAS4 tAH1 tAH2 tAH3 tCSD1 tCSD2 tCSD3 tASD tRSD1 tRSD2 tRDS1 tRDS2 tRDH1 tRDH2 tAC1 tAC2 tAC3 tAC4 tAC5 tAC6 tAC7 tAC8 Min. Max. 20 Unit ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns Test Conditions Figures 18.8 to 18.17
0.5 × tcyc − 13 1.0 × tcyc − 13 1.5 × tcyc − 13 2.0 × tcyc − 13 0.5 × tcyc − 8 1.0 × tcyc − 8 1.5 × tcyc − 8 15 15 0 0 15 15 20 15 15 15 1.0 × tcyc − 25 1.5 × tcyc − 25 2.0 × tcyc − 25 2.5 × tcyc − 25 1.0 × tcyc − 25 2.0 × tcyc − 25 4.0 × tcyc − 25 3.0 × tcyc − 25 1.5 × tcyc − 25 2.0 × tcyc − 25 2.5 × tcyc − 25 3.0 × tcyc − 25
Address read data access time 2 tAA2 Address read data access time 3 tAA3 Address read data access time 4 tAA4 Address read data access time 5 tAA5
Rev. 2.00, 03/04, page 504 of 534
Table 18.8 Bus Timing (2) Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V, φ = 10 MHz to 33 MHz
Item WR delay time 1 WR delay time 2 WR pulse width 1 WR pulse width 2 Write data delay time Write data setup time 1 Write data setup time 2 Write data setup time 3 Write data hold time 1 Write data hold time 2 Write data hold time 3 Write command setup time 1 Write command setup time 2 Write command hold time 1 Write command hold time 2 Read command setup time 1 Read command setup time 2 Read command hold time CAS delay time 1 CAS delay time 2 CAS setup time 1 CAS setup time 2 CAS pulse width 1 CAS pulse width 2 CAS precharge time 1 CAS precharge time 2 OE delay time 1 OE delay time 2 Precharge time 1 Precharge time 2 Self-refresh precharge time 1 Self-refresh precharge time 2 Symbol tWRD1 tWRD2 tWSW1 tWSW2 tWDD tWDS1 tWDS2 tWDS3 tWDH1 tWDH2 tWDH3 tWCS1 tWCS2 tWCH1 tWCH2 tRCS1 tRCS2 tRCH tCASD1 tCASD2 tCSR1 tCSR2 tCASW1 tCASW2 tCPW1 tCPW2 tOED1 tOED2 tPCH1 tPCH2 tRPS1 tRPS2 Min. Max. 15 15 Unit ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns Test Conditions Figures 18.8 to 18.19
1.0 × tcyc − 13 1.5 × tcyc − 13 20 0.5 × tcyc − 13 1.0 × tcyc − 13 1.5 × tcyc − 13 0.5 × tcyc − 8 1.0 × tcyc − 8 1.5 × tcyc − 8
0.5 × tcyc − 10 1.0 × tcyc − 10 0.5 × tcyc − 10 1.0 × tcyc − 10 1.5 × tcyc − 10 2.0 × tcyc − 10 0.5 × tcyc − 10 15 15
0.5 × tcyc − 10 1.5 × tcyc − 10 1.0 × tcyc − 20 1.5 × tcyc − 20 1.0 × tcyc − 20 1.5 × tcyc − 20 15 15
1.0 × tcyc − 20 1.5 × tcyc − 20 1.5 × tcyc − 20 2.0 × tcyc − 20
Rev. 2.00, 03/04, page 505 of 534
T1 φ
tAD
T2
A23 to A0
tCSD1
to
tAS1
tASD tASD tAH1
tAS1
tRSD1
tRSD1
Read (RDNn = 1) D15 to D0
tAS1
tAC5 tAA2 tRSD1
tRDS1 tRDH1
tRSD2
Read (RDNn = 0) D15 to D0
tAS1
tAC2 tAA3 tWRD2 tWRD2
tRDS2 tRDH2
tAH1
, Write D15 to D0
tDACD1 to tDACD2
tWDD
tWSW1
tWDH1
Figure 18.8 Basic Bus Timing: Two-State Access
Rev. 2.00, 03/04, page 506 of 534
T1 φ
tAD
T2
T3
A23 to A0
tCSD1
to
tAS1 tASD tASD tAH1
tAS1
tRSD1
tRSD1
Read (RDNn = 1) D15 to D0
tAS1 tRSD1
tAC6 tAA4
tRDS1 tRDH1
tRSD2
Read (RDNn = 0) D15 to D0
tAS2
tAC4 tAA5 tWRD2 tWRD1
tRDS2
tRDH2
tAH1
, Write D15 to D0
tWDD
tWDS1 tWSW2
tWDH1
tDACD1 to
tDACD2
Figure 18.9 Basic Bus Timing: Three-State Access
Rev. 2.00, 03/04, page 507 of 534
Th φ tAD A23 to A0 tCSD1 to tAS1 tASD tAS3
T1
T2
Tt
tASD
tAH1
tRSD1 tRSD1
tAH3
Read (RDNn = 1) D15 to D0 tAS3
tAC5
tRDS1 tRDH1
tRSD1
tRSD2
tAH2
Read (RDNn = 0) D15 to D0 tAS3 , Write D15 to D0 tWDD tWDS2
tAC2
tRDS2 tRDH2
tWRD2 tWRD2
tAH3
tWSW1
tWDH3
tDACD1 to
tDACD2
Figure 18.10 Basic Bus Timing: Two-State Access (CS Assertion Period Extended)
Rev. 2.00, 03/04, page 508 of 534
Th φ tAD A23 to A0 tCSD1 to tAS1 tASD tAS3
T1
T2
T3
Tt
tASD
tAH1
tRSD1
tRSD1
tAH3
Read (RDNn = 1) D15 to D0 tAS3 tRSD1
tAC6
tRDS1 tRDH1
tRSD2
tAH2
Read (RDNn = 0) D15 to D0 tAS4 , Write D15 to D0
tDACD1 to tWDD
tAC4
tRDS2 tRDH2
tWRD2 tWRD1 tWDS3 tWSW2
tAH3
tWDH3
tDACD2
Figure 18.11 Basic Bus Timing: Three-State Access (CS Assertion Period Extended)
Rev. 2.00, 03/04, page 509 of 534
Tp φ tAD A23 to A0 tAS3
Tr
Tc1
Tc2
tAD
tAH1 tCSD2 tAS2 tCASD1 tAH2
tCSD3
tPCH2
tCASD1
tCASW1
tOED1 ,
tAC1
tOED1
Read
tAA3 tRDS2 tRDH2 tAC4 D15 to D0
, tWRD2
Write
tWCS1 tWCH1
tWRD2
tWDD D15 to D0
tWDS1
tWDH2
tDACD1 to Note: timing: when DDS = 0 timing: when RAST = 0
tDACD2
Figure 18.12 DRAM Access Timing: Two-State Access
Rev. 2.00, 03/04, page 510 of 534
Tp φ
Tr
Tc1
Tc2
Tc1
Tc2
A23 to A0
tCPW1
, Read tAC3 D15 to D0
, Write
tRCH
tRCS1 D15 to D0
tDACD1 to
tDACD2
Note:
timing: when DDS = 0 timing: when RAST = 0
Figure 18.13 DRAM Access Timing: Two-State Burst Access
Rev. 2.00, 03/04, page 511 of 534
Tp φ tAD A23 to A0 tAS2 tPCH1
Tr
Tc1
Tc2
Tc3
tAD
tAH2 tCSD2 tAS3 tAH3 tCASD2 tCASW2
tCSD3
tCASD1
tOED2 ,
tAC2
tOED1
Read tAC7 D15 to D0
tAA5
tRDS2 tRDH2
, tWRD2 Write tWDD D15 to D0
tWCS2
tWCH2
tWRD2
tWDS2
tWDH3
tDACD1 to
tDACD2
Note:
timing: when DDS = 0 timing: when RAST = 0
Figure 18.14 DRAM Access Timing: Three-State Access (RAST = 1)
Rev. 2.00, 03/04, page 512 of 534
Tp φ
Tr
Tc1
Tc2
Tc3
Tc1
Tc2
Tc3
A23 to A0
tCPW2
, Read tAC8 D15 to D0
, Write
tRCH
tRCS2 D15 to D0
to
Note:
timing: when DDS = 1 timing: when RAST = 1
Figure 18.15 DRAM Access Timing: Three-State Burst Access
Rev. 2.00, 03/04, page 513 of 534
TRp φ
TRr
TRc1
TRc2
tCSD1 tCSD2 tCSR1 tCASD1 tCASD1 ,
Figure 18.16 CAS-Before-RAS Refresh Timing
TRp φ tCSD1 tCSD2 tCSR2 , tCASD1 tCASD1 TRrw TRr TRc1 TRcw TRc2
Figure 18.17 CAS-Before-RAS Refresh Timing (with Wait Cycle Insertion)
Self-refresh
TRp φ tCSD2 tCSD2 tRPS2 tCASD1 , tCASD1 TRr TRc TRc Tpsr
DRAM access
Tp Tr
Figure 18.18 Self-Refresh Timing (Return from Software Standby Mode: RAST = 0)
Rev. 2.00, 03/04, page 514 of 534
Self-refresh
TRp φ tCSD2 tCSD2 TRr TRc TRc Tpsr
DRAM access
Tp Tr
tRPS1 tCASD1 , tCASD1
Figure 18.19 Self-Refresh Timing (Return from Software Standby Mode: RAST = 1) 18.3.4 DMAC Timing
Table 18.9 DMAC Timing Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V, φ = 10 MHz to 33 MHz
Item DREQ setup time DREQ hold time TEND delay time DACK delay time 1 DACK delay time 2 Symbol tDRQS tDRQH tTED tDACD1 tDACD2 Min. 25 10 Max. 18 18 18 ns Figure 18.22 Figures 18.20 and 18.21 Unit ns Test Conditions Figure 18.23
Rev. 2.00, 03/04, page 515 of 534
T1 φ
T2
A23 to A0
to
(read) D15 to D0 (read) , (write) D15 to D0 (write) tDACD1 to tDACD2
Figure 18.20 DMAC Single Address Transfer Timing: Two-State Access
Rev. 2.00, 03/04, page 516 of 534
T1 φ
T2
T3
A23 to A0
to
(read) D15 to D0 (read) , (write) D15 to D0 (write) tDACD1 to tDACD2
Figure 18.21 DMAC Single Address Transfer Timing: Three-State Access
T1 φ tTED tTED T2 or T3
Figure 18.22 DMAC, TEND Output Timing
Rev. 2.00, 03/04, page 517 of 534
φ tDRQS tDRQH
Figure 18.23 DMAC, DREQ Input Timing 18.3.5 Timing of On-Chip Peripheral Modules
Table 18.10 Timing of On-Chip Peripheral Modules Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V, φ = 10 MHz to 33 MHz
Item I/O ports Output data delay time Input data setup time Input data hold time 8-bit timer Timer output delay time Symbol Min. tPWD tPRS tPRH tTMOD 25 25 25 25 1.5 2.5 12 2 12 2 12 2 Max. 40 40 18 18 18 Unit ns ns ns ns ns ns tcyc tcyc ns Figure 18.28 Figure 18.25 Figure 18.27 Figure 18.26 Test Conditions Figure 18.24
Timer reset input setup time tTMRS Timer clock input setup time tTMCS Timer clock Single-edge pulse width specification Both-edge specification USB2 Data output delay time tTMCWH tTMCWL tUDO tUCO tUDS tUDH tUDH tUUCS tUDCH
USWDVLD output delay time tUWO Control output delay time Data input setup time Data input hold time
USWDVLD input setup time tUWS USWDVLD input hold time Control input setup time Control input hold time
Rev. 2.00, 03/04, page 518 of 534
T1 φ tPRS tPRH Ports 1 to 9, ports A (read) Ports 1 to 9, ports A (write)
T2
tPWD
Figure 18.24 I/O Port Input/Output Timing
φ tTMOD TMO0, TMO1
Figure 18.25 8-Bit Timer Output Timing
φ tTMCS TMCI0, TMCI1 tTMCWL tTMCWH tTMCS
Figure 18.26 8-Bit Timer Clock Input Timing
φ tTMRS TMRI0, TMRI1
Figure 18.27 8-Bit Timer Reset Input Timing
Rev. 2.00, 03/04, page 519 of 534
USCLK tUDO Data output (USD15 to USD0)
tUWO
USWDVLD output
tUCO
Control output (USXCVRS, USSER, USTXV, , USOPM1, USOPM0)
USCLK tUDS tUDH Data input (USD15 to USD0)
tUWS tUWH
USWDVLD input
tUCS tUCH
Control input (USRXACT, USRXV, USRXERR, USTXRDY, USLSTA1, USLSTA0)
Figure 18.28 USB2 Input/output Timing
Rev. 2.00, 03/04, page 520 of 534
18.4
18.4.1
Flash Memory Characteristics
Flash Memory Characteristics
Table 18.11 Flash Memory Characteristics Conditions: VCC = 3.0 V to 3.6 V, VSS = 0 V
Item Programming time*1,*2,*4 Erase time* * *
1, 2, 4
Symbol tP tE
Min.
Typ. 3 80 500
Max. 30 800 5000
Unit ms/128 bytes ms/4 kbytes ms/32 kbytes ms/64 kbytes s/256 kbytes s/256 kbytes s/256 kbytes Times Year
Test Conditions
1000 10000 5 5 10 15 15 30
Rewrite times (total)* * * Erase time (total)* * *
1, 2, 4
1,
2,
4
ΣtP ΣtE
Ta = 25°C Ta = 25°C Ta = 25°C
Programming and erase time ΣtPE (total)*1,*2,*4 Count of rewriting Data hold time*4 NWEC tDRP
100*3 10
Notes: 1. The programming and erase time depends on the data. 2. The programming and erase time does not include the data transfer time. 3. The minimum times that all characteristics after rewriting are guaranteed. (A range between 1 and minimum value is guaranteed.) 4. Data hold characteristics when rewriting is performed within the range of specifications including minimum value.
Rev. 2.00, 03/04, page 521 of 534
18.5
Use Note (Internal Voltage Step Down)
The H8S/2170 F-ZTAT have a voltage step down circuit that automatically lowers the power supply voltage, inside the microcomputer, to an adequate level. A capacitor (one 0.1-µF capacitor) should be connected between the VCL pin (a pin for internal voltage step down circuit) and VSS pin to stabilize the internal voltage. Figure 18.29 shows how to connect the capacitor. Do not connect the VCC power-supply to the VCL pin. Doing so could permanently damage the LSI. (Connect the VCC power-supply to the VCC pin, in the usual way.)
An external capacitor to stabilize the internal voltage
VCL One 0.1-µF capacitor
VSS
VDo not connect the Vcc power-supply to the VCL pin. If connected, the LSI may be permanently damaged. Connect the VCC power-Supply to the other Vcc pin in the usual way. Use a multilayer ceramic capacitor (one 0.1-µF capacitor) for this circuit, and place it/them near the VCL pin.
Figure 18.29 VCL Capacitor Connection Method
Rev. 2.00, 03/04, page 522 of 534
Appendix
A. Port States in Each Processing State
Program Execution State Sleep Mode I/O port I/O port I/O port I/O port I/O port [Address output] A15 to A8 Port 7 2 L T Keep [Address output] A7 to A0 Port 8 P97/φ 2 2 T Clock output T T Keep [Clock output] H [Other than above] Keep P96/AS 2 H T Keep I/O port [Clock output] Clock output [Other than above] Input port [AS output] AS [Other than above] I/O port P95/RD P94/HWR P93/LWR 2 2 2 H H H T T T H H [LWR output] H [Other than above] Keep RD, HWR RD, HWR [LWR output] LWR [Other than above] I/O port
Port Name Pin Name Port 1 Port 2 Port 3 Port 4 Port 5 Port 6
MCU Operating Mode 2 2 2 2 2 2
Reset T T T T T L
Hardware Standby Mode T T T T T T
Software Standby Mode Keep Keep Keep Keep Keep Keep
Rev. 2.00, 03/04, page 523 of 534
Port Name Pin Name P92/CS2
MCU Operating Mode 2
Reset H
Hardware Standby Mode T
Software Standby Mode [CS output] H [Other than above] Keep
Program Execution State Sleep Mode [CS output] CS [Other than above] I/O port [CS output] CS [Other than above] I/O port [CS output] CS [Other than above] I/O port [Address output] A19 [CS output] CS [Other than above] I/O port
P91/CS1
2
H
T
[CS output] H [Other than above] Keep
P90/CS0
2
H
T
[CS output] H [Other than above] Keep
PA3/A19/CS3 2
T
T
Keep
PA2/A18/ UCAS
2
T
T
Keep
[UCAS and address output] UCAS, A18 [Other than above] I/O port
PA1/A17/ LCAS
2
T
T
Keep
[LCAS and address output] LCAS, A17 [Other than above] I/O port
Rev. 2.00, 03/04, page 524 of 534
Port Name Pin Name PA0/A16
MCU Operating Mode 2
Reset T
Hardware Standby Mode T
Software Standby Mode Keep
Program Execution State Sleep Mode [Address output] A16 [Other than above] I/O port
[Legend] L: Low level H: High level Keep: Input port becomes high-impedance, output port retains state T: High impedance DDR: Data direction register OPE: Output port enable
B.
Product Lineup
Product Classification Type Name HD64F2170 Model Marking Package (Code) HD64F2170 100-pin TQFP (TFP-100B) F-ZTAT version
H8S/2170
Rev. 2.00, 03/04, page 525 of 534
C.
Package Dimensions
16.0 ± 0.2
14
75 76 51 50
16.0 ± 0.2
100 1
*0.22 ± 0.05
26
*0.17 ± 0.05
1.00
0.20 ± 0.04
0.08 M
1.0
0.15 ± 0.04
1.20 Max
25
0.5
1.0
0˚ – 8˚
0.10
0.10 ± 0.10
0.5 ± 0.1
*Dimension including the plating thickness Base material dimension
Package Code JEDEC JEITA Mass (reference value)
TFP-100B — Conforms 0.5 g
Figure C.1 Package Dimensions (TFP-100B)
Rev. 2.00, 03/04, page 526 of 534
Main Revisions and Additions in this Edition
Item Section 4 Exception Handling 4.3.1 Reset Exception Handling Figure 4.1 Reset Sequence Section 10 Watchdog Timer (WDT) 10.2.2 Timer Control/ Status Register (TCSR) Section 12 Universal Serial Bus 2 (USB2) 12.1 Features 12.3.16 FIFO Clear Register 0 (FCLR0) 334 319 Description added • • Supports the USB version 2.0 Supports four endpoints; EP0, EP1, EP2, and EP3 285 Bits2 to 0 amended 101: φ/8192 (frequency: 63.5 ms) Page 58 Revisions (See Manual for Details) Description added (1), (3) Reset exception handling vector address ((1) = H'000000, (3) = H'000002)
Description added EP2 having a dual-FIFO configuration is cleared by entire FIFOs. Similarly, as for EP1 FIFO with a dual-FIFO configuration, the only side currently selected is cleared. Description added That is, when there is no valid data in the FIFO even with one side, the transfer is requested to the DMAC. Description added
12.3.18 DMA Set Register 336 0 (DMA0) 12.5.1 USB Cable Connection Figure 12.2 USB Cable Connection 341
D+ pull-up on
Receive bus reset BRST in IFR0 = 1
Rev. 2.00, 03/04, page 527 of 534
Item 12.5.3 Control Transfer Figure 12.6 Data Stage Operation (Control-In)
Page 345
Revisions (See Manual for Details) Description added
Write data to EP0i data register (EPDR0i)
Write number of transmit data bytes to packet enable register 0i (PKTE0i) every packet.
12.5.3 Control Transfer Figure 12.9 Status Stage Operation (Control-Out)
348
Description added
Clear interrupt flag (EP0i TR in IFR0 = 0)
EP0i transfer request interrupt prohibited (EP0i TR in IER0 = 0)
Write 0 to packet enable register 0i (PKTE0i)
12.5.5 EP2 Bulk-In Transfer (Dual FIFO) Figure 12.11 EP2 Bulk-In Transfer Operation 12.8.11 EPDR0s Read
352
Description amended
366
Description deleted EPDR0s must be read in 8-byte units. If read is suspended, data received in the next setup cannot be read normally.
Rev. 2.00, 03/04, page 528 of 534
Item 12.8.14 Example of External Circuit Figure 12.18 Connection Example of External Circuit
Page 367
Revisions (See Manual for Details) Figure 12.18 amended
This LSI USXCVRS USTSEL USCLK USRXACT USRXV USRXERR USTXV USTXRDY USD15 to USD0 USWDVLD USVBUS USSUSP USLSTA1, USLSTA0 USOPM1 USOPM0 RES External physical layer LSI in the UTMI specification XcvrSelect TermSelect CLK RXActive RXValid (RXValidH) RXError TXValid (TXValidH) TXReady Data15 to Data0 ValidH SuspendM LineState [1:0] OpMode [1] OpMode [0] RST (assert H)
DP DM
Reset signal
Level shifter VBUS (5 V)
(3.3 V) Power-supply voltage can be applied to this IC even when the system (LSI) power is off.
USB connector
Figure 12.20 Bus Reset Detection Flow 12.8.18 USB Interrupt During Software Standby
369
Description added Description added Description added 16. While writing 1 to the SCO bit and downloading the internal programs, the WDT coutup operation stops. Description added
Section 14 Flash 462 Memory (0.18-µm F-ZTAT Version) 14.10 Usage Notes Section 15 Clock Pulse Generator 15.3.3 Note on confirming the operation Section 18 Electrical Characteristics 18.1 Absolute Maximum Ratings Table 18.1 Absolute Maximum Ratings 497 467
Description amended
Item Operating temperature Symbol Value Topr Regular specifications: −20 to +75 Unit °C
Wide-range specifications: °C −40 to +85 Operating Topr temperature (Flashmemory programing/erasure) 0 to +75 °C
18.5 Use Note (Internal Voltage Step Down)
522
Description amended A capacitor (one 0.1-µF capacitor) should be connected between the VCL pin (a pin for internal voltage step down circuit) and VSS pin to stabilize the internal voltage.
Rev. 2.00, 03/04, page 529 of 534
Item Figure 18.29 VCL Capacitor Connection Method
Page 522
Revisions (See Manual for Details) Figure 18.29 amended
An external capacitor to stabilize the internal voltage
VCL One 0.1-µF capacitor
VSS
VDo not connect the Vcc power-supply to the VCL pin. If connected, the LSI may be permanently damaged. Connect the VCC power-Supply to the other Vcc pin in the usual way. Use a multilayer ceramic capacitor (one 0.1-µF capacitor) for this circuit, and place it/them near the VCL pin.
Rev. 2.00, 03/04, page 530 of 534
Index
8-Bit Timer (TMR) ................................. 263 16-Bit Counter Mode.......................... 274 Cascaded Connection.......................... 274 Compare Match Count Mode ............. 275 Pulse Output ....................................... 270 TCNT Incrementation Timing ............ 271 Toggle output...................................... 279
Clock Pulse Generator ............................ 463 Communications Protocol....................... 437 Condition Field ......................................... 39 Condition-Code Register (CCR) ............... 24 Control Transfer...................................... 343 CPU Operating Modes.............................. 16 Advanced Mode .................................... 18 Normal Mode ........................................ 16 Crystal Resonator.................................... 463
Address Map............................................. 53 Address Space..................................... 16, 20 Addressing Mode...................................... 40 Absolute Address.................................. 41 Immediate ............................................. 42 Memory Indirect ................................... 42 Program-Counter Relative .................... 42 Register Direct...................................... 41 Register Indirect ................................... 41 Register Indirect with Displacement..... 41 Register Indirect with Post-Increment...................................... 41 Register indirect with pre-decrement.... 41
Data direction register............................. 219 Data register............................................ 219 DMA Controller (DMAC) ...................... 153 Channel Priority .................................. 186 Dual Address Mode ............................ 189 Interrupt Sources................................. 213 Repeat Area Function ......................... 179 Single Address Mode .......................... 196 Transfer Modes ................................... 171 DMA Transfer Specifications ................. 358 DRAM Interface ..................................... 122
Bcc...................................................... 29, 37 Boot Mode .............................................. 401 Bulk-In Transfer ..................................... 351 Bulk-Out Transfer................................... 349 Bus Arbitration ....................................... 151 Bus Controller (BSC) ............................... 83 Basic Timing....................................... 110 Chip Select Signals ............................. 108 Data Size and Data Alignment............ 109 Extension of Chip Select (CS) Assertion Period.................................. 121 Read Strobe (RD) Timing................... 120 Valid Strobes ...................................... 110 Wait Control ....................................... 119
Effective Address................................ 40, 44 effective address extension ....................... 39 Effective Address Extension..................... 39 Error Protection....................................... 429 Exception Handling .................................. 55 Exception Handling Vector Table............. 56 Extended Control Register (EXR) ............ 23
Flash MAT Configuration....................... 377
General Registers ...................................... 22
Hardware Protection ............................... 428
Rev. 2.00, 03/04, page 531 of 534
Hardware Standby Mode ........................ 476 Mode Comparison................................... 376 Module Stop Mode ................................. 477
Idle Cycle ............................................... 142 Instruction Set........................................... 29 Arithmetic Operations Instructions....... 32 Bit Manipulation Instructions ............... 35 Block Data Transfer Instruction ........... 39 Branch Instructions............................... 37 Data Transfer Instructions .................... 31 Logic Operations Instructions............... 34 Shift Instructions .................................. 34 System Control Instruction ................... 38 Interrupt Control Modes ........................... 72 Interrupt Controller................................... 63 Interrupt Exception Handling ................... 59 Interrupt Exception Handling Sequence................................................... 78 Interrupt Exception Handling Vector Table ............................................. 70 Interrupt Mask Bit .................................... 24 Interrupt Request Mask Level .................. 23 Interrupt-In Transfer ............................... 353 Interrupts CMIA.................................................. 275 CMIB.................................................. 275 ERI0.................................................... 314 IRQ7 to IRQ0 Interrupts....................... 69 NMI Interrupt ....................................... 69 OVI..................................................... 275 RXI0 ................................................... 314 TEI0.................................................... 314 TXI0 ................................................... 314 WOVI ................................................. 288 Interval Timer Mode............................... 287
On-Board Programming.......................... 401 on-board programming mode ................. 373 Operating Modes....................................... 49 Operation Field ......................................... 39 overflow.................................................. 286
PLL Circuit ............................................. 466 Port register............................................. 219 Power-Down Modes ............................... 469 Procedure Program ................................. 418 Processing of USB Standard Requests and Class/Vendor Requests..................... 354 Program Counter (PC) .............................. 23 Programmer Mode .................................. 434 Programming/Erasing Interface Parameter Download pass/fail result parameter... 393 Flash erase block select parameter...... 398 Flash multipurpose address area parameter ............................................ 396 Flash multipurpose data destination parameter ........................................... 396 Flash pass/fail parameter..................... 399 Flash programming/erasing frequency parameter ............................................ 394 Programming/Erasing Interface Register ................................................... 382 Protection................................................ 428
List of Registers...................................... 479 Register Addresses ............................. 480 Register Bits ....................................... 485 Register States in Each Operating Mode................................................... 493
RAM ....................................................... 371 Register Field............................................ 39 Registers ABRKCR...................... 65, 482, 490, 495 ACSCR ......................... 87, 480, 487, 493 BCR .............................. 92, 481, 487, 493 BRR ............................ 300, 483, 491, 495 CSACR ......................... 88, 480, 487, 493
Rev. 2.00, 03/04, page 532 of 534
CTRL.......................... 337, 480, 487, 493 DASTS0 ..................... 332, 480, 486, 493 DMA0......................... 336, 480, 487, 493 DMACR ..................... 165, 481, 488, 494 DMDAR ..................... 158, 481, 488, 494 DMMDR..................... 160, 481, 488, 494 DMSAR...................... 158, 481, 488, 494 DMTCR...................... 158, 481, 488, 494 DRACCR...................... 97, 481, 487, 494 DRAMCR..................... 94, 481, 487, 494 EPDR0........................ 330, 480, 485, 493 EPDR1........................ 331, 480, 486, 493 EPDR2........................ 331, 480, 486, 493 EPDR3........................ 332, 480, 486, 493 EPSTL0 ...................... 336, 480, 487, 493 EPSZ........................... 329, 480, 485, 493 FCCS .......................... 382, 481, 488, 494 FCLR0 ........................ 334, 480, 487, 493 FECS........................... 386, 481, 488, 494 FKEY.......................... 387, 481, 488, 494 FMATS....................... 388, 481, 488, 494 FPCS........................... 386, 481, 488, 494 FTDAR ....................... 389, 481, 488, 494 ICR ............................... 64, 482, 490, 495 IER................................ 68, 482, 490, 495 IER0............................ 329, 480, 485, 493 IFR0............................ 323, 480, 485, 493 ISCR ............................. 67, 482, 490, 495 ISR................................ 68, 482, 490, 495 ISR0............................ 328, 480, 485, 493 ISSR............................ 262, 482, 490, 495 MDCR .......................... 50, 480, 487, 493 MSTPCR .................... 473, 480, 487, 493 P1DDR ....................... 222, 482, 490, 495 P1DR .......................... 223, 483, 491, 496 P2DDR ....................... 226, 482, 490, 495 P2DR .......................... 226, 483, 491, 496 P3DDR ....................... 230, 482, 490, 495 P3DR .......................... 230, 483, 491, 496 P4DDR ....................... 233, 482, 490, 495 P4DR .......................... 234, 483, 491, 496 P5DDR ....................... 237, 482, 490, 495 P5DR .......................... 237, 483, 491, 496
P6DDR........................ 242, 482, 490, 495 P6DR........................... 242, 483, 491, 496 P7DDR........................ 246, 482, 491, 495 P7DR........................... 247, 483, 491, 496 P8DDR........................ 251, 483, 491, 495 P8DR........................... 251, 483, 491, 496 P9DDR........................ 254, 483, 491, 495 P9DR........................... 255, 483, 491, 496 PADDR....................... 258, 483, 491, 495 PADR.......................... 258, 483, 491, 496 PBAR ............................ 66, 482, 490, 495 PFCR1......................... 261, 482, 490, 495 PFCR3......................... 338, 482, 490, 495 PKTE .......................... 333, 480, 486, 493 PORT1 ........................ 223, 483, 491, 495 PORT2 ........................ 227, 483, 491, 495 PORT3 ........................ 231, 483, 491, 496 PORT4 ........................ 234, 483, 491, 496 PORT5 ........................ 238, 483, 491, 496 PORT6 ........................ 243, 483, 491, 496 PORT7 ........................ 247, 483, 491, 496 PORT8 ........................ 252, 483, 491, 496 PORT9 ........................ 255, 483, 491, 496 PORTA ....................... 259, 483, 491, 496 RAMER ...................... 390, 481, 487, 493 RDNCR......................... 93, 481, 487, 493 RDR ............................ 293, 483, 491, 495 REFCR.......................... 98, 481, 488, 494 RSR..................................................... 293 RTCNT ....................... 101, 481, 488, 494 RTCOR ....................... 101, 481, 488, 494 SBYCR ....................... 472, 480, 487, 493 SCR............................. 295, 483, 491, 495 SMR ............................ 294, 483, 491, 495 SSR ............................. 297, 483, 491, 495 SYSCR.......................... 51, 480, 487, 493 TCNT ......................... 265, 284, 481, 484, .................................... 488, 492, 494, 496 TCORA....................... 266, 484, 492, 496 TCORB ....................... 266, 484, 492, 496 TCR............................. 266, 483, 491, 496 TCSR ......................... 268, 284, 481, 483, .................................... 488, 491, 494, 496
Rev. 2.00, 03/04, page 533 of 534
TDR .............................293, 483, 491, 495 TSR..................................................... 294 USBSUSP....................338, 480, 487, 493 USTCR ........................169, 482, 490, 495 WTCR ...........................90, 481, 487, 493 Reset ......................................................... 57 Reset Exception Handling ........................ 57
Stall Operations....................................... 355
Trace Bit ................................................... 23 Trap Instruction Exception Handling........ 59 TRAPA instruction ............................. 42, 59
Serial Communication Interface (SCI) ....................................................... 291 Asynchronous Mode........................... 304 Bit rate ................................................ 300 Framing error...................................... 310 Overrun error ...................................... 310 Parity error.......................................... 310 Serial Communication Interface Specification ........................................... 435 Sleep Mode............................................. 474 Software Protection ................................ 429 Software Standby Mode ......................... 474 Stack Pointer (SP)..................................... 22 Stack Status .............................................. 60
Universal Serial Bus (USB2) .................. 319 USB Cable Connection ........................... 341 USB Cable Disconnection ...................... 342 user boot MAT........................................ 431 user boot memory MAT.......................... 373 User Boot Mode...................................... 415 user MAT................................................ 431 user memory MAT.................................. 373 User Program Mode................................ 405
Watchdog Timer (WDT)......................... 283 Watchdog Timer Mode ........................... 286 Write Data Buffer Function .................... 150
Rev. 2.00, 03/04, page 534 of 534
Renesas 16-Bit Single-Chip Microcomputer Hardware Manual H8S/2172 Group
Publication Date: 1st Edition Mar, 2003 Rev.2.00 Mar 17, 2004 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Technical Documentation & Information Department Renesas Kodaira Semiconductor Co., Ltd.
2004. 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
Renesas Technology America, Inc. 450 Holger Way, San Jose, CA 95134-1368, U.S.A Tel: (408) 382-7500 Fax: (408) 382-7501 Renesas Technology Europe Limited. Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, United Kingdom Tel: (1628) 585 100, Fax: (1628) 585 900 Renesas Technology Europe GmbH Dornacher Str. 3, D-85622 Feldkirchen, Germany Tel: (89) 380 70 0, Fax: (89) 929 30 11 Renesas Technology Hong Kong Ltd. 7/F., North Tower, World Finance Centre, Harbour City, Canton Road, Hong Kong Tel: 2265-6688, Fax: 2375-6836 Renesas Technology Taiwan Co., Ltd. FL 10, #99, Fu-Hsing N. Rd., Taipei, Taiwan Tel: (2) 2715-2888, Fax: (2) 2713-2999 Renesas Technology (Shanghai) Co., Ltd. 26/F., Ruijin Building, No.205 Maoming Road (S), Shanghai 200020, China Tel: (21) 6472-1001, Fax: (21) 6415-2952 Renesas Technology Singapore Pte. Ltd. 1, Harbour Front Avenue, #06-10, Keppel Bay Tower, Singapore 098632 Tel: 6213-0200, Fax: 6278-8001
http://www.renesas.com
Colophon 1.0
H8S/2172 Group Hardware Manual
1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 Japan
REJ09B0149-0200Z
工商网监
湘ICP备2023018690号
