M32100T2-SDI-E User`s Manual
Contents
1. 1 e When the user program is stopped by the MVTC instruction at the address of the instruction which operates BPC a BPC value may be changed even if the MVTC instruction has not been executed Occurrence of this phenomenon depends on the MCU status and the instruction sequence After this phenomenon occurs the program is normally re executed starting with the PC value of the MVTC instruction The following shows sample data when the phenomenon occurs Example Address Instruction H 100 LD24 RO H 100 H 104 MVTC RO BPC H 106 NOP When a break occurs at PC H 104 in the above program fragment BPC H 100 may be enabled even before the MVTC instruction is executed Using the MVTC Instruction 2 In cases when instructions used to operate on the BPC with the MVTC instruction are followed by an RTE instruction do not set a preexecution PC breakpoint for the RTE instruction This is because the BPC value becomes illegal and the program cannot be run normally after a break The following shows sample data when the phenomenon occurs Example Address Instruction H 100 LD24 RO H 100 H 104 MVTC RO BPC H 106 NOP H 110 RTE If in the above program fragment a preexecution PC breakpoint is set at PC H 110 to cause a break the BPC value becomes illegal Note on WDT If a user program is stopped during operation of WDT built in the MCU the WDT count halts meanwhile This prevents SBI interruption by WDT while the user prog2. MSD M32100T2 SDI E NE010901 2 1 M32102S6FP 1 Differences between the emulator and MCUs IMPORTANT e The emulator initializes the MCU internal register to the following values Initial ization starts when the power switch is turned ON or MCU is reset RO 00000000 R1 00000000 R2 00000000 R3 00000000 R4 00000000 R5 00000000 R6 00000000 R7 00000000 R8 00000000 R9 00000000 R10 00000000 R11 00000000 R12 00000000 R13 00000000 R14 00000000 R15 00000100 SPI 00000100 SPU 00000100 BPC 00000000 PC 00000000 ACCH 00000000 ACCL 00000000 PSW 00000000 2 MCU signals connected to the SDI MCU control interface connector referred from Section 3 4 of the User s Manual Direction Emulator to target Connected to TCK of MCU Remarks Clock frequency 4 MHz GND 0 V Emulator to target TDI of MCU Target to emulator TDO of MCU Emulator to target TMS of MCU Emulator to target TRST of MCU Totem pole output on the emulator Emulator to target DBI of MCU Not used O WDINIO A HR W PM Target to emulator VCCX of MCU oO Emulator to target System reset 3 MCU signals connected to the SDI trace interface connector referred from Section 3 4 of the User s Manual TRCLK Direction Target to emulator Connected to TRCLK of MCU Open corrector output on the emulator Remarks Vss GND 0 V T
3. TRDATAO of MCU TRDATA 1 Target to emulator TRDATA1 of MCU Vss GND 0 V TRDATA 2 Target to emulator TRDATA2 of MCU DOIN Oa R oO Pp TRDATA 3 Target to emulator TRDATAS of MCU Vss GND 0 V TRDATA 4 Target to emulator TRDATA4 of MCU TRDATA 5 Target to emulator TRDATAS5 of MCU Vss GND 0 V TRDATA 6 Target to emulator TRDATA6 of MCU TRDATA 7 Target to emulator TRDATA7 of MCU Vcc Target to emulator VCCJ of MCU EVENTO Target to emulator EVENTO of MCU EVENT1 Target to emulator EVENT1 of MCU NC Not used NC Not used NC 4 Debug specifications dependent on MCU model referred from Section 5 1 of the User s Manual Not used Emulation memory Flash ROM built in MCU used as the emulation memory RAM area Implemented by instruction replacement ROM area Implemented by preexecution PC breakpoints of MCU four points Software break Forcible break Implemented by internal resource of MCU Hardware break Implemented by internal resource of MCU two data pala access oreak access break points Trace clock frequency TRCLK frequency CPU operation frequency 2 5 9 7rPENESAS Renesas Technology Corp MSD M32100T2 SDI E NE010901 5 Other cautions and restrictions dependent on MCU model IMPORTANT Note on Using the MVTC Instruction
4. WDT If a user program is stopped during operation of WDT built in the MCU the WDT count halts meanwhile This prevents SBI interruption by WDT while the user program is stopped However WDT is normally initialized then 319 7rtENESAS Renesas Technology Corp MSD M32100T2 SDI E NE010901 2 2 M32121CFWG 1 Differences between the emulator and MCUs IMPORTANT e The emulator initializes the MCU internal register to the following values Initial ization starts when the power switch is turned ON or MCU is reset RO 00000000 R1 00000000 R2 00000000 R3 00000000 R4 00000000 R5 00000000 R6 00000000 R7 00000000 R8 00000000 R9 00000000 R10 00000000 R11 00000000 R12 00000000 R13 00000000 R14 00000000 R15 00000100 SPI 00000100 SPU 00000100 BPC 00000000 PC 00000000 ACCH 00000000 ACCL 00000000 PSW 00000000 e To execute a target program which transfers to the sleep mode or to the stop mode you must observe the following restrictions because of the MCU specifications 1 Add the instructions given below after the store instruction which transfers the target program to the sleep stop mode 2 Do not set a break point between the STB instruction and the last NOP instruction added Target program Store instruction lt Instruction to transfer to the sleep stop mode BRA LOOP NOP NOP 5 Insert 16 NOP instructions after the address branch command NOP e When a break is forced while t
5. frequency TRCLK frequency CPU operation frequency 2 5 Other cautions and restrictions dependent on MCU model IMPORTANT Note on Using the MVTC Instruction 1 e When the user program is stopped by the MVTC instruction at the address of the instruction which operates BPC a BPC value may be changed even if the MVTC instruction has not been executed Occurrence of this phenomenon depends on the MCU status and the instruction sequence After this phenomenon occurs the program is normally re executed starting with the PC value of the MVTC instruction The following shows sample data when the phenomenon occurs Example Address Instruction H 100 LD24 RO H 100 H 104 MVTC RO BPC H 106 NOP When a break occurs at PC H 104 in the above program fragment BPC H 100 may be enabled even before the MVTC instruction is executed Using the MVTC Instruction 2 In cases when instructions used to operate on the BPC with the MVTC instruction are followed by an RTE instruction do not set a preexecution PC breakpoint for the RTE instruction This is because the BPC value becomes illegal and the program cannot be run normally after a break The following shows sample data when the phenomenon occurs Example Address Instruction H 100 LD24 RO H 100 H 104 MVTC RO BPC H 106 NOP H110 RTE If in the above program fragment a preexecution PC breakpoint is set at PC H 110 to cause a break the BPC value becomes illegal Note on
6. RSYNC Target to emulator TRSYNG of MCU TRDATA 0 Target to emulator TRDATAO of MCU TRDATA 1 Target to emulator TRDATA1 of MCU Vss GND 0 V TRDATA 2 Target to emulator TRDATA2 of MCU COINIO aA R wW ry TRDATA 3 Target to emulator TRDATA3 of MCU Vss GND 0 V TRDATA 4 Target to emulator TRDATA4 of MCU TRDATA 5 Target to emulator TRDATA5 of MCU Vss GND 0 V TRDATA 6 Target to emulator TRDATA6 of MCU TRDATA 7 Target to emulator TRDATA7 of MCU Vcc Target to emulator VCCX of MCU EVENTO Target to emulator EVENTO of MCU EVENT1 Target to emulator EVENT1 of MCU NC Not used NC Not used NC 7rtENESAS Renesas Technology Corp 2 9 Not used MSD M32100T2 SDI E NE010901 4 Debug specifications dependent on MCU model referred from Section 5 1 of the User s Manual e No built in emulation memory provided in the emulator Emulation memory e Function to download the data to an external flash ROM supported RAM area Implemented by instruction replacement Software break ROM area Implemented by preexecution PC breakpoints of MCU four points Forcible break Implemented by internal resource of MCU Hardware break Dat Deak Implemented by internal resource of MCU two data ata access Dreak access break points Trace clock
7. 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 Standard Computers office
8. To our customers Old Company Name in Catalogs and Other Documents On April 1 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 1 2010 Renesas Electronics Corporation Issued by Renesas Electronics Corporation http www renesas com Send any inquiries to http www renesas com inquiry CENESAS 8 10 11 12 Notice 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 grant
9. ea Implemented by instruction replacement ROM area Implemented by preexecution PC breakpoints of MCU four points Implemented by internal resource of MCU Software break Forcible break Hardware break Implemented by internal resource of MCU two data aeons reak access breakpoints Trace clock frequency TRCLK frequency CPU operation frequency 2 8 9 2tENESAS Renesas Technology Corp MSD M32100T2 SDI E NE010901 5 Other cautions and restrictions dependent on MCU model IMPORTANT Note on CLOCK LED e When using M3217xFxVWG or connecting M3217xFxVFP to the converter for in circuit connection option CLOCK LED may light regardless of oscillation on the MCU target board Thus you cannot use CLOCK LED to judge presence absence of oscillation of vibrators on the target board Note on Access Prohibited Areas e The emulator uses the system space from H C000 0000 to H FFFF FFFF stipulated in the MCU user s manual as an emulator only area If the system space is accessed by the target program operation of the emulator cannot be guaranteed Therefore do not access the area H C000 0000 through H FFFF FFFF from the target program 9 9 7PENESAS Renesas Technology Corp
10. ed 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
11. 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 anti crime 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 ce
12. he target MCU is set in the sleep stop mode the target MCU may return to the normal mode Also when memory is referenced or set while the target MCU is set in the sleep stop mode the target MCU may return to the normal mode from the sleep stop mode e Do not change the target MCU to the sleep stop mode using the memory rewrite function of the emulator debugger 2 MCU signals connected to the SDI MCU control interface connector referred from Section 3 4 of the User s Manual Direction Connected to Remarks Emulator to target TCK of MCU Clock frequency 8 MHz GND 0 V Emulator to target TDI of MCU Target to emulator TDO of MCU Emulator to target TMS of MCU Emulator to target TRST of MCU _ Totem pole output on the emulator Emulator to target DBI of MCU Emulator to target FVCC of MCU Voltage is set to 2 5 V Turned ON OFF according to the setting of the ON OFF switch supplied by FVCC DOIN IO a R o p Target to emulator VCCJ of MCU Emulator to target System reset Open corrector output on the emulator 4 9 7tENESAS Renesas Technology Corp MSD M32100T2 SDI E NE010901 3 MCU signals connected to the SDI trace interface connector referred from Section 3 4 of the User s Manual TRCLK Direction Target to emulator Connected to TRCLK of MCU Remarks Vss GND 0 V TRSYNC Target to emulator TRSYNC of MCU TRDATA 0 Target to emulator
13. ics products or if you have any other inquiries Note 1 Renesas Electronics as used in this document means Renesas Electronics Corporation and also includes its majority owned subsidiaries Note 2 Renesas Electronics product s means any product developed or manufactured by or for Renesas Electronics To all our customers Regarding the change of names mentioned in the document such as Mitsubishi Electric and Mitsubishi XX to Renesas Technology Corp The semiconductor operations of Hitachi and Mitsubishi Electric were transferred to Renesas Technology Corporation on April 1st 2003 These operations include microcomputer logic analog and discrete devices and memory chips other than DRAMs flash memory SRAMs etc Accordingly although Mitsubishi Electric Mitsubishi Electric Corporation Mitsubishi Semiconductors and other Mitsubishi brand names are mentioned in the document these names have in fact all been changed to Renesas Technology Corp Thank you for your understanding Except for our corporate trademark logo and corporate statement no changes whatsoever have been made to the contents of the document and these changes do not constitute any alteration to the contents of the document itself Note Mitsubishi Electric will continue the business operations of high frequency amp optical devices and power devices Renesas Technology Corp Customer Support Dept April 1 2003 tENESAS Renesas Technol
14. ogy Corp REJ10J0811 0100Z MSD M32100T2 SDI E NE010901 Be sure to read this note SDI Emulator System for M32R Family MCUs M32100T2 SDI E Release Note MITSUBISHI ELECTRIC SEMICONDUCTOR APPLICATION ENGINEERING CORPORATION September 1 2001 Outline This Release Note explains the specifications cautions and restrictions dependent on MCU models which are not covered by the M32100T2 SDI E User s Manual When referring to a required section in the User s Manual read the Release Note together with the manual Contents e MCU Model Leistts 20 Sich iia he oie ad eines LAE Mite erate 1 2 Specifications Cautions and Restrictions Dependent on the MCU Model 1 ZA LMB2LO2SGRP sci A E esbercobiod Qaaeee devas tea tate Movers tere LE 2 22 M3B21IZICEW G va vient Nae ai ely AIR eae 4 2 3 32170 32171 32172 32173 and 32174 Groups ceeeeeecseeseeeceeeeeeseeaeeeseeeene 7 1 MCU Model List This Release Note covers the MCU models listed in Table 1 Table 1 MCU model list M32102 Group M32102S6FP M32121 Group M32121FCWG M32170 Group M32170FxVFP M32170F6VWG M32171 Group M32171FxVFP M32172 Group M32172FxVFP M32172FxVWG M32173 Group M32173FxVFP M32173FxVWG M32174 Group M32174FxVFP 2 Specifications Cautions and Restrictions Dependent on the MCU Model The following explains the emulator specifications cautions and restrictions dependent on the MCU model 1 9 2tENESAS Renesas Technology Corp
15. ram is stopped However WDT is normally initialized then 6 9 2tENESAS Renesas Technology Corp MSD M32100T2 SDI E NE010901 2 3 32170 32171 32172 32173 and 32174 Groups 1 Differences between the emulator and MCUs IMPORTANT e The emulator initializes the MCU internal register to the following values Initial ization starts when the power switch is turned ON or MCU is reset RO 00000000 R1 00000000 R2 00000000 R3 00000000 R4 00000000 R5 00000000 R6 00000000 R7 00000000 R8 00000000 R9 00000000 R10 00000000 R11 00000000 R12 00000000 R13 00000000 R14 00000000 R15 00000100 SPI 00000100 SPU 00000100 BPC 00000000 PC 00000000 ACCH 00000000 ACCL 00000000 PSW 00000000 2 MCU signals connected to the SDI MCU control interface connector referred from Section 3 4 of the User s Manual Direction Connected to Remarks Emulator to target JTCK of MCU Clock frequency 4 MHz GND 0 V Emulator to target JTDI of MCU Target to emulator JTDO of MCU Emulator to target JTMS of MCU Emulator to target JTRST of MCU _ Totem pole output on the emulator Emulator to target JDBI of MCU Not used Target to emulator VCCE of MCU Emulator to target System reset Open corrector output on the emulator 1 2 3 4 5 6 7 8 9 o 719 7tENESAS Renesas Technology Corp MSD M32100T2 SDI E NE010901 3 MCU signals connected to the SDI trace in
16. rtain 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 Electron
17. terface connector referred from Section 3 4 of the User s Manual This connector is not necessary because M32170FxVFP and M32171FxVFP do not have a signal to be connect to the SDI trace interface connector If you need debug functions such as real time trace prepare a target board for debugging using M32170F6VWG or use the converter for in circuit connection option TRCLK Direction Target to emulator Connected to TRCLK of MCU Remarks Vss GND 0 V TRSYNC Target to emulator TRSYNC of MCU TRDATA 0 Target to emulator TRDATAO of MCU TRDATA 1 Target to emulator TRDATA1 of MCU Vss GND 0 V TRDATA 2 Target to emulator TRDATA2 of MCU DOINID a R oO mM TRDATA 3 Target to emulator TRDATA3 of MCU Vss GND 0 V TRDATA 4 Target to emulator TRDATA4 of MCU TRDATA 5 Target to emulator TRDATA5 of MCU Vss GND 0 V TRDATA 6 Target to emulator TRDATA6 of MCU TRDATA 7 Target to emulator TRDATA7 of MCU Vcc Target to emulator VCCE of MCU EVENTO Target to emulator JEVENTO of MCU EVENT1 Target to emulator JEVENT1 of MCU NC Not used NC Not used NC 4 Debug specifications dependent on MCU model referred from Section 5 1 of the User s Manual Not used Emulation memory Flash ROM built in MCU used as the emulation memory RAM ar
Download Pdf Manuals
Related Search