Home

Renesas M16C FAMILY User's Manual

1. d 8 XOT IOW AE Av gt NI PPA ita IOW AS Av lt NI PPA H 333339 y2IMS afin AE AS ae ZOdTOWXZ zo fd T 2 gt IOW Vun NI i 300V 1009 GaINNHS A JEE DW NN Ldr szy XOT ano oo asui adee P se 7 WOCH ory Tal oA Se Dei ETD TZOZ 0 ZZ d bo Ko Lal zezsu t TEEN AS T LLN T EN Tzu at a ano ER z 2A ZH ee TA T t T TIOS OTOS DA H A Zdl Td DA e SS d o S a a X E Balu dd ker z T eet Bas ai Tr Sr Z Baus Bai oat 8d OXLS ESCH L aen Dor z T ZS anin a ou s or Horoa sN ke 22 s Bataxun 8 K He sR Ee en 33 E OSIO ji z T ez id E XOT Fie R z2 jd EM ctal Ge BE vty YOTEOSO8OIH z z T 6zu a a2 L ot d lg z9 X sa Lzy A Y Dr EI oza O d fant zzy Cru RF Za es E rE HES D H el Zd Eed HX DA SE ved tee NED DEE Sed hee es DA nza SEI od ees e SCC tex v a asn asn 7 E sei Ss s S A S zZ a ea Se Sr TIND_SSAND S 9 T dH8JTH9LEW zta Le Egg OTdSHS OZONW SE rn eta DE x rf en EE bid LEZ X Ant eta LE ESO ei 89 ta Le Et SR e its oe aS L k SCH Sur 6E v 2 p ve SqNt mH or UMd dvoLxa p nl el x sto Ss NI nore Teana JOT ec We SS o DOE AT Xor Kee SE zez ECH K e S KS ou sn ZOdT9WXZ 4 oe Zed Zod e X 2 S Ae ee Od res g E DA D H LEESCH Ga
2. 7 Appendix 7 Appendix 7 1 USB Monitor Board 7 1 1 Board Specifications Figure 7 1 list Board specifications of USB Monitor Board Gi Power Source Supply SES J3 10 Pin connector Flat Cable J1 USB connector JP1 MCU Mode Pin USB Cable d Boot User M37641F8 LED s USB MCU D2 Red Stop D3 Green Run D4 Yellow Status D1 Red Power J2 UART Interface Figure 7 1 USB Monitor Board Board specifications 79 7 Appendix 7 1 2 Pin Assignments As an example of M16C 62A group Pin assignments of the 10 pin connector for Flat Cable are shown in Figure 7 2 Pin No Signal 1 Vcc 2 P6 4 BUSY 3 P6 5 SCLK 4 P6 6 RxD 5 P5 0 CE 6 P5 5 EPM 10 Pin connector 7 GND 8 RESET 9 CNVss 10 P6_7 TxD Figure 7 2 An example of 10 Pin connector pin assignment 7 1 3 Example Connection An example of how to connect the 10 pin connector for the Flat Cable to the Target Board is shown in following page 80 7 Appendix Example Connection for M16C 62A M 6N M306NAFG M306NBFC only M3062GF8N 80 24 l Ve OI BUSY f USB Monitor Board 8 O19 D I Lee SCLK o 2 CE z 4 EPM 0 SE GND o RESET FLAT Cable Connection os a lo TxD 477 Connector Ty
3. Chapter orders and composition contents are all reviserd Feb 15 2004 Cover is renewed Windows NT is deleted from OS which can be used Pin assignment is revised Jul 30 2004 Whole page is revised according to the FoUSB version upgrade Dec 24 2004 Compatible Product List is upgrade Software Break Number List is upgrade Software License Agreement screen is added to install procedure Selectable MCU List is upgrade Precautions on KD3083 Emulation Memory is added Section Title is changed 5 2 1 Limitations on Special Page Jump gt 5 2 1 Lmitations on Special Page Vector Description of Section 5 2 1 is chaged A So fy Description ev ate Summary Section 5 2 4 Precautions on Internal Reserved Area Expansion Bit is added 61 62 Description of Section 5 2 6 is changed 63 64 ROM RAM Area Table is upgrade 66 Description of NMI pin is deleted from Section 5 4 4 01 Dec 24 2004 68 Description of Realtime and Reset Vector Table in Section 5 5 3 is changed 76 77 Section 6 13 Debug operation has not worked well is added 80 86 User reset signal is added to Example connection of target board 82 Example connection of target board M16C 26 26A 28 29 is changed 86 Example connection of target board 38C2 is added USB Flash Writer User s Manual Publication
4. 2 The ID code is automatically read in Click the lt OK gt button If file don t have ID code a message is not displayed ID code 00 00 00 00 00 00 G A file has been loaded that will create an ID Code of 00 on the current attached device Please make note of this Figure 4 6 ID code screen Note A file which is out of flash area cannot be open The addresses specified in the firmware file you are trying to load are out of bounds of the flash area for the current selected device Section Start Address OxFOO00 4 Using the FoUSB 2 READ button This button performs to verify data written in the Target MCU and the file read by OPEN Also performs to read out data written in the Target MCU 1 Clik the READ button Figure 4 7 screen will appear Flash Memory Read Figure 4 7 Flash Memory Read screen 1 2 For Verify click the lt verify gt button and the file downloaded by OPEN and data written in the Target MCU will be verified If the verified result matches Figure 4 8 will appear Click the lt OK gt button Figure 4 8 Verify OK screen If the data does not match following figure will be displayed VERIFY FAILED x 4 Using the FoUSB 3 For Read Area specify the range of data to read in hexadecimal By default the data opens in a custom window Click the lt Read Area gt button and the downloaded data will be displayed but not saved If you wish se
5. blinks PC with Windows 98SE ME 2000 or XP USB Monitor Board p e Peer USB Cable Figure 3 2 USB Monitor Board connectivity 3 Installing 3 When an operating system is Windows 98SE ME 2000 Windows system detect USB Driver automatically and recognizes USB Monitor Board Recognition of USB Monitor Board for USBMON Driver is completion 4 When an operating system is Windows XP Windows system displays the Found New Hardware Wizard screen Then choose Install the software automatically and click the lt Next gt button Found New Hardware Wizard Welcome to the Found New Hardware Wizard This wizard helps you install software for Renesas FoUSB ICD Di If your hardware came with an installation CD or floppy disk insert it now What do you want the wizard to do Click Next to continue Next gt Cancel 5 Next the Hardware Installation screen is displayed click the lt Continue Anyway gt button Note Hardware Installation The software you are installing for this hardware Renesas FoUSB ICD has not passed Windows Logo testing to verify its compatibility with Windows XP Tell me why this testing is important Continuing your installation of this software may impair or destabilize the correct operation of your system either immediately or in the future Microsoft strongly recommends that you stop this installation now and contact the hardware vendor for software
6. communication When the data is received the DBC interrupt generates and the monitor program is executed The DBC interrupt is not influenced of flag The receive interrupt is used for some models because there is no DBC interrupt In this case the DBC interrupt is influenced of flag The monitor program analyzes the received data and executes each command 5 5 2 Command Execution 1 User Program exection A User Program is executed in the following procedure 1 An address match interrupt is disabled 2 One instruction of a User Program is executed using a single step interrupt and executing only one instruction and go back to the monitor program 3 When a software break is set enable an address match interrupt 4 The User Program continuance is executed When a User Program is stopped by a software break if a User Program is executed an address match interrupt is generated and stops in the same address again therefore to move from the address is not possible Above 1 to 3 processes are performed to avoid this re interrupt 2 Software break An address match interrupt is used for software break When an address match interrupt is generated a monitor program is operated The number of the software breaks which can be used simultaneously is the same as the number of the address match functions which are built in a microcomputer 3 Step Execution A single step interrupt is used for step execution When a single step interru
7. Date Rev 1 00 Oct 23 2002 Rev 4 01 Dec 24 2004 Published by Renesas Solutions Corp 4 1 6 Miyahara Yodogawa ku Osaka City 532 0003 Japan 2004 Renesas Technology Corp and Renesas Solutions Corp All Rights Reserved Printed in Japan USB Flash Writer User s Manual 2tENESAS Renesas Solutions Corp 4 1 6 Miyahara Yodogawa ku Osaka City 532 0003 Japan
8. Flash over USB you ve installed choose Settings Control Panel from the Start menu and then click Add Remove Programs Select Flash over USB V from the program list and click the lt Add Remove gt button An uninstall window will appear with the Flash over USB V compiler uninsalled 3 Installing 3 4 Recognition of USB Monitor Board From installer version V 2 04 the FoUSB installer has an automatic USB Driver install function Refer to 3 3 FoUSB Flash over USB installing This section explains recognition of USB Monitor Board when confirming this function and installing FoUSB When this function is not confirmed please perform installation of a USB Driver and recognition of USB Monitor Board with reference to 7 2 Installation of a USB Driver and recognition of USB Monitor Board Manual setup 3 4 1 Recognition of USB Monitor Board 1 for USBMON Driver 1 Remove the cover of USB Monitor Board and make a USB Monitor Board Board the following setup before connecting USB Monitor Board to your host computer PC If a setup is completed attach a cover in a USB Monitor Board Board Power Source Supply Selector S1 Power Mode USB side MCU Mode Pin JP1 MCU Mode Open Figure 3 1 Setup of USB Monitor Board Board 2 Connect the USB Monitor Board included with the package to the USB port of PC The Power indicator D1 Power of USB Monitor Board lights and a Status indicator D4 Status
9. M16C 62P_ M30622F8P 64K 4K 1380h 13FFh OF0000h M30623F8P 64K 4K 1380h 13FFh OF0000h M30620FCP 128K 10K 2B80h 2BFFh 0E0000h M30621FCP 128K 10K 2B80h 2BFFh 0E0000h M30624FGP 256K 20K 5380h 53FFh 0C0000h M30625FGP 256K 20K 5380h 53FFh 0C0000h M30626FHP 384K 31K 7F80h 7FFFh O0A0000h M30627FHP 384K 31K 7F80h 7FFFh O0A0000h M30626FJP 512K 31K 7F80h 7FFFh 080000h M30627FJP 512K 31K 7F80h 7FFFh 080000h M16C 62N_ M3062GF8 64K 8K 2380h 23FFh OF0000h 5 Using the KD Table 5 3 ROM RAM areas 2 ROM RAM XXXXXh YYYYYh ZZZZZh M16C 6N M306N4FC 128K 5K 0E0000h M306N5FC 128K 5K 0E0000h M306N4FG 256K 10K 0C0000h M306NBFC 128K 5K 1780h 17FFh OE0000h M306NAFG 256K 10K 2B80h 2BFFh 0C0000h M16C 80 M30800FC 128K 10K 2B00h 2BFFh FE0000h M30803FG 256K 20K 5300h 53FFh FC0000h M32C 83 M30833FJ 512K 31K 7FOOh 7FFFh F80000h M30835FJ 512K 31K 7FOOh 7FFFh F80000h M32C 84 M30845FJ 512K 24K F80000h M32C 85 M30855FW 320K 24K FB0000h M30855FH 384K 24K FA0000h M30852FJ 512K 16K F80000h M32C 86 M30865FJ 512K 24K F80000h M32C 87 M3087BFL 1M 48K F00000h R8C 10 R5F21102 Note 8K 512 0C800h R5F21103 Note1 12K 768 0C800h R5F21104 16K 1K 0C800h R8C 11 R5F21112 Note2 8K 512 0C800h R5F21113 Note2 R5F21114 12K 768 16K 1K 0C800h 0C800h R8C 12 R5F21122 Note3 8K 512 0C800h R5F21123 Note
10. MCU File is chosen Choose USB as the communication interface and click the lt OK gt button MCU Debugging Information Run Mode Resume MCU M30262f8 mcu Parallel Serial LAN LPT Ge USB m Monitor Debug E Stert op for moniter debug Cancel Help T Next Hide Figure 5 4 Init screen 2 NOTICE Precautions on KD3083 Emulation Memor The address allocated to the Emulation Memory cannot be debugged in the KD3083 Therefore allocate the Emulation Memory to the address which is not used in debug Status Emulation Memory l Debug Monitor Bank Address Fo intemal ROM Area 78DC14 78DC14 jp allocated m Emulation Me The address in the Emulation Memory can be modified by the bank address default vale FO Area 1 The high order 24 to 17 bits of the address will be a bank address Area 2 Area 3 jo 256KB D No Use x Area 4 fo 256KB D No Use x Cancel Help T Next Hide Figure 5 5 Emem screen KD3083 only The following section describes the address modification of the Emulation Memory as an example of the M3087BFLGP M32C 87 Group microcomputer 5 Using the KD a At first an example to which the Emulation Memory overlaps the User Program is shown In this example the User Program is allocated from F00000h and the Emulation Memory is allocated from F00000h using default value FO of bank address Therefore the Emulation Memory overlaps
11. Select components to install be phe SS IDVET VOUT TTGUSE OVE Shortcut on Desktop a component to see its Install USB Drivers desorption Update KD30 Files Update KD 3083 Files Space required 6 8MB Nullsotinstal System v20 GE lt Back Cancel NOTICE Explanation of install component a Shortcut on Desktop The shortcut of a FoUSB Flash over USB execution file is created on a desktop b Install USB Drivers FoUSB installer installs a USB Driver in the correct location of Windows system automatically We recommend choosing this component in all operating systems In addition when this component is not chosen please perform installation of a USB Driver and recognition of USB Monitor Board with reference to 7 2 Installation of a USB Driver and recognition of USB Monitor Board Manual setup c Update KD30 Files FoUSB installer updates KD30 to KD30 with a firmware older than the firmware of FoUSB d Update KD3083 Files FoUSB installer updates KD3083 to KD3083 with a firmware oloder than the firmware of FoUSB 3 Installing 6 Choose the install location of FoOUSB and click the lt Install gt button The default install location of FoUSB is C AMTOOL FOUSB a Flash Over USB Programmer 2 04 Setup Choose Install Location Choose the folder in which to install Flash Over USB Programmer V 2 04 C AMTOOLSFOUSEB KES sc E A 7 The following figure is displayed when the install component Install US
12. USB MCU is used only for the use shown below 1 Installation of FOUSB Driver 2 When the firmware of USB MCU is erased or damaged When the firmware of USB MCU is erased or damaged the phenomenon of 6 4 FoUSB cannot operate Why or 6 6 A communication error occurs when the KD starts What is the cause of this problem occurs In this case it is necessary to install FoUSB driver first time only and download firmware compulsorily on a USB MCU Please refer to 6 4 FOUSB cannot operate Why 3 Installing 3 5 KD30 KD3083 intalling 3 5 1 Installing 1 Installing the Remote Debugger Double click installer file on the CD ROM KD KD30 for KD30 In KD3083 the installer file is included in KD KD3083 2 A flow of installation procedures is shown in the pages that follow a Click the lt Yes gt button InstallShield Self extracting EXE ES b Click the lt Next gt button c Only when you agree click the lt Yes gt button Software License Agreement 3 Installing d Click the lt Next gt button A default install location is C MTOOL If an install location is changed please click the lt Browse gt button and determine an install location Select Components e Click the lt Yes gt button Question f Click the lt OK gt button Information 3 Now you ve finished installing the KD30 Note The installation of KD3083 is the same 3 Installing 3 5 2 U
13. block area in which the downloaded data are written 4 1 8 Details of Main Button 2 1 SETTINGS button When you click the SETTINGS button the screen shown in Figure 4 26 appears allowing you to customize FoUSB User Setting Figure 4 26 User Setteing screen 4 Using the FoUSB 1 Contents of Options Debug Mode Whether debug mode is available Unusable Show splash screen Whether FoUSB sound is available Ignore FoOUSB Devices Whether FoUSB devices are included Unusable Ignore Monitor Devices Whether USB monitor is included Unusable Auto Unlock Whether or not to automatically set ID code Multi Programming Mode Whether Multi Programming Mode is available Unusable Language Language select 2 Automated Programming This function currently cannot be used 2 HELP button Opens a help file 3 EXIT button Terminates FoUSB 4 2 Other Functions FoUSB does not have a check sum function Therefore when checking written contents check READ gt Verify gt Verification For cletails refer to 4 1 3 Details of Main Button 1 for other functions refer to Onlie Help 5 Using the KD 5 Using the KD 5 1 Using the KD 5 1 1 Before Starting the KD 1 Corresponding MCU become only R8C Tiny M16C 10 M16C 20 M16C Tiny M16C 60 series M16C 80 and M32C 80 series 2 Check to see that the KD is installed in your host computer PC 3 Check to see that PC USB Cable USB Monitor Boar
14. install wizard So click the lt Next gt button Add New Hardware Wizard 5 Select the method to search for your new hardware Normally choose Search for the best driver for your device Recommended and click the lt Next gt button Add New Hardware Wizard 6 Select the check box labeled Specify a location Then specify the folder into which you ve installed FoUSB files USB Drivers folder and click the lt Next gt button Add New Hardware Wizard CA MTOOL FOUSB USB Drivers i 89 7 Appendix 7 When the Windows system has been prepared to install the driver the wizard shown in Figure 7 3 appears So click the lt Next gt button Add New Hardware Wizard Pm ba e E lt A gt Se Figure 7 3 USBMON Driver 1 8 When the Windows system has finished installing the driver the wizard shown in Figure 7 4 appears So click the lt Finish gt button Add New Hardware Wizard Ki Ze a Figure 7 4 USBMON Driver 2 9 Installation of a USBMON Driver and recognition fo USB Monitor Board have been finished Separate USB Monitor Board from your host computer PC 90 7 Appendix 7 2 2 For FoUSB Driver 1 Remove the cover of USB Monitor Board and make a USB Monitor Board Board the following setup before installing FoUSB Driver If a setup is completed attach a cover in a USB Monitor Board Board Power Source Supply Selector S1 Power Mode
15. output by FoUSB Normal message Your device has been automatically unlocked with the ID code The correct firmware already loaded on the USB Monitor Board Do you want to reprogram anyway Programming in new firmware image Download successtful Verify passed A file has been loaded that will create an ID code of 00 00 00 00 00 00 00 on the current attached device Please make note of this Error message The ID code did not match the one on the device You are about to program Flash blocks that have not been erased yet Do you want to continue Device is locked You must first unlock the device The USB Monitor Board is currently begin used as part of the KD30 Debugger System Please close KD30 first before using the USB monitor board the firmware currently loaded on your USB monitor board doesn t support the device your have selected Verify FAILED The Flash memory on the device does not match the current loaded firmware file No Flash Blocks Selected Please only enter numbers between C0000 and FFFFF only USB Monitor could not erase that Flash Block Error erasing device Erase Unsuccessful No File loaded Vendor Read Request Error unable to complete GET_DEV_INFO command Unknown USB device attached the target board that is attatched USB monitor board currently does not have its own 5volt supply Unable to place target MCU into syncronoos BootMode
16. software that has passed Windows Logo testing Continue Anyway STOP Installation Note Microsoft has advocated authentication of the USB drivers to the USB vendors in the Microsoft Windows XP and Windows based operating systems released after Microsoft Windows XP This is aimed at elimination of illegal drivers and improvement of host computer PC Renesas USB Drivers are not authenticated by Microsoft but we provide them baased on the sufficient examination 6 Click the lt Finish gt button Windows system recognizes USB Monitor Board for FOUSB Driver Found New Hardware Wizard Completing the Found New Hardware Wizard The wizard has finished installing the software for _g2_ Renesas Flash Over USB for M37641F Click Finish to close the wizard Recognition of USB Monitor Board for FOUSB Driver is completion 7 Separate USB Monitor Board from host computer PC 8 Finally remove the cover of USB Monitor Board and set the MCU Mode Pin JP1 MCU Mode as Open 3 4 3 Other Notes Caution The USB Drivers folder below is stored Driver Name Description USBMON Driver USBMON driver is a driver for using FoUSB Flash over USB and KD KD30 KD3083 3 Installing Related Files usbmon sys usbmon inf FoUSB Driver FoUSB driver is a driver for using USB MCU M367641F8 of USB Monitor Board in Boot mode Note Note fousb sys fousb inf The Boot mode of
17. 0 or XP j a i E d T f ms d USB Monitor Board USB Cable Figure 3 4 USB Monitor Board connectivity 3 When an operating system is Windows 98SE ME 2000 Windows system detect USB Driver automatically and recognizes USB Monitor Board Recognition of USB Monitor Board for USBMON Driver is completion Please skip to 7 4 When an operating system is Windows XP Windows system displays the Found New Hardware Wizard screen Then choose Install the software automatically and click the lt Next gt button Found New Hardware Wizard Welcome to the Found New Hardware Wizard This wizard helps you install software for Renesas Flash Over USB for M37641F D If your hardware came with an installation CD QP or floppy disk insert it now What do you want the wizard to do EI Click Next to continue 3 Installing 5 Next the Hardware Installation screen is displayed click the lt Continue Anyway gt button Note Hardware Installation A The software you are installing for this hardware Renesas Flash Over USB for M37641F has not passed Windows Logo testing to verify its compatibility with Windows xP Tell me why this testing is important Continuing your installation of this software may impair or destabilize the correct operation of your system either immediately or in the future Microsoft strongly recommends that you stop this installation now and contact the hardware vendor for
18. 1F6HP FoUSB KD30 M30281F6 M30281F8HP FoUSB KD30 M30281F8 M30281FAHP FoUSB KD30 M30281FA M16C 29 M30290F8HP FoUSB KD30 M30290F8 M30290FAHP M30290FCHP FoUSB KD30 FoUSB KD30 M30290FA M30290FC M30291F8HP FoUSB KD30 M30291F8 M30291FAHP FoUSB KD30 M30291FA M30291FCHP FoUSB KD30 M30291FC Table 1 4 Compatible Products 2 MCU Product Name Corresponding 1 Contents of Product MCU Product Name Software to select in Software M16C 24 M30245FCGP FoUSB KD30 M30245FC M16C 62A M M30620FCAFP GP M30621FCAGP FoUSB KD30 M30620FCA M30620FCMFP GP M30621FCMGP M30624FGAFP GP M30625FGAGP FoUSB KD30 M30624FGA M30624FGMFP GP M30625FGMGP M16C 62P M30622F8PFP GP FoUSB KD30 M30622F8P M30623F8PGP FoUSB KD30 M30623F8P M30620FCPFP GP FoUSB KD30 M30620FCP M30621FCPGP FoUSB KD30 M30621FCP M30624FGPFP GP FoUSB KD30 M30624FGP M30625FGPGP FoUSB KD30 M30625FGP M30626FHPFP GP FoUSB KD30 M30626FHP M30627FHPGP FoUSB KD30 M30627FHP M30626FJPFP GP FoUSB KD30 M30626FJP M30627FJPGP FoUSB KD30 M30627FJP M16C 62N M3062GF8NFP GP FoUSB KD30 M3062GF8 M16C 6N M306N4FCTFP FoUSB KD30 M306N4FC M306N4FGTFP FoUSB KD30 M306N4FG M306N5FCTFP FoUSB KD30 M306N5FC M306NAFGTFP FoUSB KD30 M306NAFG M306NBFCTFP FoUSB KD30 M306NB
19. 3 12K 768 0C800h R5F21124 16K 1K 0C800h R8C 13 Note1 When using KD30 select the Note2 When using KD30 select the Note3 When using KD30 select the Note4 When using KD30 select the R5F21132 Note4 8K 512 0C800h R5F21133 Note4 12K 768 0C800h R5F21134 16K 1K R5F21104 MCU File R5F21114 MCU File R5F21124 MCU File R5F21134 MCU File 0C800h 00000h User RAM Area Op ell YYYYYh Flash Memory ZZZZZh FF900h FFEFFh User Fixed Vector Area M16C Series FFFFFh 000000h User RAM Area Gi eed YYYYYh Flash Memory ZZZZZh FFF900h FFFEFFh User Fixed Vector Area M16C 80 M32C 80 Series FFFFFFh Figure 5 12 Mmemory map 5 Using the KD 00000h User RAM Area YYYYYh 0C000h ZZZZZh Flash Memory OFEFFh User Fixed Vector Area OFFFFh R8C Tiny Series 5 Using the KD 5 4 Peripheral Function Related Limitations 1 UART pins TxDi RxDi The UARTIi transmit and receive interrupts are used for communication between the USB Monitor Board and host computer PC Make sure that UARTIi is not used in the User Program Do not connect the UART pins with other pins UART1 use prohibition MCUs R8C 10 Group R8C 11 Group R8C 12 Group R8C 13 Group M32C 80 Series M16C 80 Group M16C Tiny Series M16C 24 M30245 Group M16C 62A M Group M16C 62P Group M16C 62N M3062GF8 Group M16C
20. 6N Group UARTO use prohibition MCUs M16C 10 Group M16C 1N Group 2 Set up OFF900h or OFFF900h in the UARTI receive with User Program because UARTI is being used for the communication with KD30 and KD3083 The interruption of relocatable vector table variable vecter table except for UARTi can be used with User Program UART1 receive interrupt setting required MCUs OFF900h address M16C 62A M Group M16C 6N M306NAFG M306NBFC only Group M16C 24 M30245 Group UARTO receive interrupt setting required MCUs OQFF900h address M16C 10 Group M16C 1N Group UART1 receive interrupt setting required MCUs QFFF900h address M16C 80 Group Note Setting the UARTi receive interrupt is not necessary for MCUs other than the above MCU 5 5 FOUSB Debugger Principle FoUSB debug formula is a monitor program formula The monitor program debugs by communicating with FoUSB A use program is interrupted at the time of command execution and a monitor program is executed A monitor program is written in flash memory user ROM area when a debugger KD30 and KD3083 is started The monitor program has the following functions 1 A function which communicates with FoUSB 2 A function which executes command Next the differences between the realization method of these functions and CPU operation are described 5 Using the KD 5 5 1 Communication Function with FoUSB The clock synchronous serial I O is used for FoUSB and the monitor program
21. 7 66 7E BF 63 66 E 64 F4 OF 66 7E 9F 3B 66 G4 g c n FO6D6 7E BF 63 66 E 64 F4 91 66 B7 O4 66 7E 8F 50 66 c n P FOGEG EB 36 80 66 EB 56 51 65 EB op op on EB 20 OF op 6 PQ FOGFG EB 16 66 F7 EB 64 B4 AA OG O4 75 C3 OG OG 7C EA d U F6166 B4 AA op 64 75 C3 OG OG 7C EA B4 AA G2 G4 75 C3 u u xi CRAN JK AA FP CH Dh oo oo Ah FO FO AN AA FF Co AND NP 9 i fou 1 Figure 4 10 Flash Memory Contents 4 Using the FoUSB 4 To change the custom window used for displaying data to an editor select the lt Display using gt By default data is displayed in Notepad To change Notepad to any editor click the lt Change Editor gt button See Figure 4 11 Flash Memory Read Figure 4 11 Flash Memory Read screen 3 5 To save the read data select the lt Save to Motorola S Record File gt and click the lt Read Area gt button See Figure 4 12 Then enter a name for the file See Figure 4 13 Flash Memory Read Figure 4 12 Flash Memory Read screen 4 4 Using the FoUSB Save in ja program x Si zl cl File name Jann mat Save as type Tat x Cancel ZA Figure 4 13 Save screen 3 ERASE button This button erases the Flash ROM in the Target MCU 1 When you click the ERASE button the screen changes to one of the following two depending on whether vou ve downloaded data using OPEN 2 Before downloading You can choose to erase all bloc
22. B Drivers is choosen Click the lt Yes gt button Driver Install Next warning is displayed Please check that USB Monitor Board is not connected to your host computer PC and click the lt OK gt button Driver Install 3 Installing 8 When an operating system is Windows XP notes screen is displayed Click the lt OK gt button Please Note Because you are running XP you will have to click the Continue Anyway button in the Windows XP Logo certification screen Then the software install screen is displayed two times for USBMON Driver and FoUSB Driver click the lt Continue Anyway gt button twice Note Software Installation A The software you are installing has not passed Windows Logo testing to verify its compatibility with Windows xP Tell me why this testing is important Continuing your installation of this software may impair or destabilize the correct operation of your system either immediately or in the future Microsoft strongly recommends that you stop this installation now and contact the software vendor for software that has passed Windows Logo testing REISER Note Microsoft has advocated authentication of the USB drivers to the USB vendors in the Microsoft Windows XP and Windows based operating systems released after Microsoft Windows XP This is aimed at elimination of illegal drivers and improvement of host computer PC Renesas USB Drivers are not authentica
23. BFL 4 Using the FoUSB 2 When pressing the Select MCU button the screen shown in Figure 4 21 is displayed Select the Target MCU in this screen First select the category of the Target MCU to be used form the MCU Category Column M16C 26 Group is selected from M16C Tiny Series in Figure 4 21 Next select the Target MCU to be used from the MCU Select Column If the MCU which is indicated by highlight is duble click or lt OK gt button is clicked the confirmation screen will be displayed Chip Selection x Flash RAM MMI Ver a 24K 4K 1K 7 06 32K 4K 1K MCU Select Column OK Help Cancel Figure 4 21 Chip Selection screen 3 Click the lt OK gt button if the confirmation screen is displayed and download the firmware to USB Monitor Board FOUSB We must download new firmware to the USB Monitor Board to support that device Figure 4 22 Confirmation screen 4 The screen shown in Figure 4 23 is displayed while the system is downloading the firmware to USB Monitor Board Programming in new firmware image Figure 4 23 Firmware Download screen 4 Using the FoUSB 5 When the system has finished download the firmware the screen shown in Figure 4 24 is displayed Click the lt OK gt button Download MMI Download succesfull Figure 4 24 Completion screen NOTICE The cautions about firmware download in 3 3V operation In 3 3V operation firmware download to U
24. F L 5k User Reset Signal 77 Example Connection for M16C 1N 0 1uF Vec BUSY USB Monitor Board ne O13 DiE if lt a eae co a 4 CE 4 EPM 7 Q o S RESET SA P R s TD FLAT Cable Connection o 2 Ka Connector Type P17 CNTRO HIF3FC 10PA 2 54DSA P15 RxD 10 Pin Connector assign P30 TXout o P14 TxD 30pF P16 CLK d 10MHz 30pF 6 P31 TZout 5k User Reset Signal 83 7 Appendix Example Connection for M32C 83 oE V Ze BUSY f USB Monitor Board O19 D I SCLK ln s t CE z 4 EPM 0 ann S RESET Gig 2 TD FLAT Cable Connect able Connection olo Connector Type HIF3FC 10PA 2 54DSA P64 CTS1 RTS1CT50 CLKS1 ae 30p ERR x 10 Pin Connector assign PeG RxD1 a 10MHz P55 MOTD 4 P67 TxD1 30pF 77 5k S77 P65 CLKL P5OWRUWR 5k P85 NMI User Reset Signal 5k Example Connection for M32C 84 85 86 87 oE Ver ale BUSY me i USB Monitor Board 1u HH oP E e P 4 EPM 0 Zu RESET eas SE TxD FLAT Cable Connect able Connection elo Connector Type HIF3FC 10PA 2 54DSA 10 Pin Connector assign Pin No Signal User Res
25. FC M16C 80 M30800FCFP GP M30802FCGP FoUSB KD3083 M30800FC M30803FGFP GP M30805FGGP FoUSB KD3083 M30803FG M32C 83 M30833FJFP GP FoUSB KD3083 M30833FJ M30835FJGP FoUSB KD3083 M30835FJ M32C 84 M30843FJFP GP M30845FJGP FoUSB KD3083 M30845FJ M32C 85 M30853FHFP GP M30855FHGP FoUSB KD3083 M30855FH M30853FWFP GP M30855FWGP FoUSB KD3083 M30855FW M30850FJFP GP M30852FJGP FoUSB KD3083 M30852FJ M32C 86 M30865FJGP FoUSB KD3083 M30865FJ M32C 87 M30879FLFP GP M3087BFLGP FoUSB KD3083 M3087BFL R8C 10 R5F21102FP FoUSB KD30 R5F21102 R5F21104 1 R5F21103FP FoUSB KD30 R5F21103 R5F21104 1 R5F21104FP FoUSB KD30 R5F21104 R8C 11 R5F21112FP FoUSB KD30 R5F21112 R5F21114 1 R5F21113FP FoUSB KD30 R5F21113 R5F21114 1 R5F21114FP FoUSB KD30 R5F21114 R8C 12 R5F21122FP FoUSB KD30 R5F21122 R5F21124 1 R5F21123FP FoUSB KD30 R5F21123 R5F21124 1 R5F21124FP FoUSB KD30 R5F21124 R8C 13 R5F21132FP FoUSB KD30 R5F21132 R5F21134 1 R5F21133FP FoUSB KD30 R5F21133 R5F21134 1 R5F21134FP FoUSB KD30 R5F21134 7542 M37542F8SP FP GP FoUSB M37542F8 38C2 M38C29FFAFP HP FoUSB M38C29FF 1 When using the KD30 1 Contents of Product 1 4 Board Specification Table 1 5 shows the USB Monitor Board Specification When saving these products put them into the conductive bag Store them into the container box which is used for shipping as possible Table 1 5 USB Monitor Board Specification Item Description Debug formula Monitor pr
26. Fh set the address after DOOOOh to the reset vector and set the PM13 bit to 1 on the User Program which operates from the address after DOOOOh Applicable MCUs M306NAFGTFP 5 Using the KD 5 2 5 Limitations on Stop and Wait Modes To use stop or wait modes in the User Program start the KD in free run mode If you want to debug close the RAM C Watch and ASM Watch Windows before actually debugging Furthermore set a breakpoint or take other necessary measures when getting out of stop or wait mode in order to ensure that no window operations will be performed until the program stops at the breakpoint 5 2 6 Realtime Capability of the User Program Please be aware that while the Monitor Program is in its STOP ed state the hardware peripherals will continue to run Therefore interrupts may not be serviced properly Also the watchdog timer will not be serviced and will likely timeout if active Note While the Monitor Program is in its RUN ning state there is no overhead on the User Program unless the RAM C Watch and ASM Watch Windows are open in KD30 KD3083 These windows require periodic communication with the target MCU which suspends normal User Program operation while servicing the request approximately 2000 BCLK cycles for each 16 bytes of data displayed in the window are used per window update When enabling Realtime Capability in the User Program close these windows 5 Using the KD 5 3 Memory Map L
27. Program Only Erasing Options _ Erase ALL Blocks C Erase Only Needed Blocks Help P Program ES Close Figure 4 20 Program Flash screen 2 In the Choose an Options section select either Erase gt Program gt Verify or Program Only a Erase gt Program gt Verify without lock bit function When you select this option processing is performed in order of Erase Program and Verify A progress bar is displayed indicating the progress of processing in Erase Program and Verify b Program Only without lock bit function When you select this option processing is performed for only programming A progress bar is displayed indicating the progress of processing in programming Note The following warning will be displayed if clicking the Program Only before erasing the Target MCU Clik the lt Yes gt button only when Target MCU is blank chip If the Target MCU is not blank erase Flash ROM of the Target MCU and perform the program process Blank Check Error LO You are about to program Flash Blocks that have not been erased yet Do you want to continue 4 Using the FoUSB 3 Erasing Options is useful when you select Erase gt Program gt Verify for Choose An Options allowing you to select the method for erasing flash memory blocks a Erase All Blocks All flash blocks are erased b Erase Only Needed Block Only the correspo
28. REJ10J0143 0401Z Rev 4 01 Revision date Dec 24 2004 Everywhere you imagine E d ES DN ESAS USB Flash Writer User s Manual RENESAS SINGLE CHIP MICROCOMPUTER M16C FAMILY 740 FAMILY Renesas Solutions Corp www renesas com Keep safety first in your circuit designs Renesas Technology Corporation 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 These materials are intended as a reference to assist our customers in the selection of the Renesas Technology Corporation 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 Corporation or a third party Renesas Technology Corporation assumes no responsibility for any damage or infringement of any third party s rights originating in the use of any product data diagrams charts programs algorithms or circuit application examples contained in these materials All information conta
29. SB Monitor Board cannot be performed The following error screen will be displayed if the firmware is downloaded to USB Monitor Board in 3 3V operation Error have its own 5 volt supply You must supply 5 volts to the Target Board before CA The Target Board that is attached to USB Monitor Board currently does not attempting to downloading new firmware In such a case please use FoUSB KD30 KD3083 are included afeter downloading the firmware to USB Monitor Board in the procedure shown below Frimware download is not required unless the MCU to be used is changed after downloading the firmware lt Procedure of firmware download in 3 3V gt a Set the power source supply selector S1 Power Mode on the USB Monitor Board to the USB side Refer to Figure 4 2 b Connect the USB Monitor Board to host computer PC In this case do not connect the Target Board to the USB Monitor Board PC with Windows 98SE ME 2000 or XP P USB Monitor Board p b l USB Cable 4 Using the FoUSB c Start FoUSB At this time although the following error screen is displayed ignore the error and click the lt OK gt button pa a FLASH OVER USB pa O irar odeia Unable to place target MCU into Synchronous Boot Mode Please verify that your target board is plugged in correctly and the hardware pins needed for MCU Serial Boot Mode are unrestricted as noted in the device spec Use the Try Again button to attempt conn
30. SS Source void main lt void gt DIS 6608 1 GETT 009E ve set RT ve Enable dtl O ve Intial le Eeer display lt 1 messageli1 i while i lt 5 0000 gt lt i _asmC nop MCU STOP 4 Figure 5 10 Software Break 5 1 8 Reset Execution User Program is in the same status as immediately after download Click the Reset button Figure 5 6 D on the KD Main screen 5 1 9 KD Completion 1 Before completing a KD stop the User Program 2 Next select File Exit menu in the KD Main screen When the Exit menu is selected opens click OK button If Cancel is clicked the KD is not completed Q Do you really want to exit 5 Using the KD 5 1 10 If a Communication Error Occurs If a communication error occurs the error screen shown in Figure 5 11 appears In that case click the OK button and check the following two points When you finished checking restart the KD Check1 Is the power source supply selector on the USB Monitor Board set to USB side Check2 Are the USB Cable and Flat Cable are firmly inserted into position Error Communication ERROR Can t accept data ERROR 16014 Figure 5 11 Communication Error screen 5 1 11 Error Except a Communication Error Occurs If an error except a communication error occurs refer to the KD online help 5 1 12 Operation Method When operating except specifying above refer to the KD online help 5 U
31. Target MCU matches with the input ID code and Figure 4 18 will be displayed When the ID code does not match Figure 4 19 will be displayed Target MCU is locked and enter the correct ID code Enter the 7 byte HEX ID code Teen eb ol ning mer Je Figure 4 17 ID code dialog FOUSB Succesfully Unlocked Figure 4 18 ID code match ERROR x The ID code did not match the one on the device Figure 4 19 ID code not match The setting method of the ID code is the following a Macro input The lt Fill 00 gt button or the lt Fill FF gt button is clicked and input All 00h or All FFh b Manual input Input the ID code by the keyboard input c File input Input the HEX file or Motorola file which has an ID code The example of File input is shown in the next page 4 Using the FoUSB Example of File input In this example the ID code of 01 02 03 04 05 06 07 is programmed in the Target MCU First click the OPEN button and open the HEX file or Motorola file which has an ID code Click the lt OK gt button on the ID code screen which FoUSB displays The Motorola file with the ID code of 01 02 03 04 05 06 07 is open in this example Look in ja 62a_demo x Ka c 62a_demo mot ERASE UNLOCK 5 FILE PROGRAM Everywhere you imagine e file has been loaded that will create an ID Code of 01 02 03 04 05 06 07 on the current attached device Please make
32. USB side MCU Mode Pin JP1 MCU Mode Shorted LS ee i e gt USBside WA CC i a gg 2 Connect the USB Monitor Board included with the package to the USB port of your host computer PC The Power indicator D1 Power of USB Monitor Board lights i PC with Windows 98SE ME 2000 or XP ge USB Monitor Board a USB Cable 3 Windows system recognizes new hardware The following installation methods are the examples which used Windows 98SE Although the installation methods differ a little for every operating system it is installable by the almost same operation 91 7 Appendix 4 Recognition of new hardware displayes an install wizard So click the lt Next gt button Add New Hardware Wizard 5 Select the method to search for your new hardware Normally choose Search for the best driver for your device Recommended and click the lt Next gt button Add New Hardware Wizard 6 Select the check box labeled Specify a location Then specify the folder into which you ve installed FoUSB files USB Drivers folder and click the lt Next gt button CAMTOOL FOUSB USB Drivers E 92 7 Appendix 7 When the Windows system has been prepared to install the driver the wizard shown in Figure 7 5 appears So click the lt Next gt button Add New Hardware Wizard ES Figure 7 5 FoUSB Driver 8 When the Windows system has finished installing the driver the wizard sho
33. When a microcomputer is reset a monitor program is operated therefore when a program is stopped at the head of a User Program the CPU register and the SFR value may differ from the initial value value after reset of a microcomputer 6 Troubleshooting 6 Troubleshooting 6 1 FoUSB cannot communicate with the Target MCU Why It is possible that the firmware written in the USB Monitor Board has gone wild In such a case temporarily remove the USB Cable and insert it back into position 6 2 The MCU cannot enter standerd serial I O why 1 Check to see that the Busy signal is connected to the writer s connector accurately 2 Check to see that the Reset signal is pulled up 5K on a board 6 3 The MCU cannot be programmed using FoUSB Why Check to see that the MCU type name displayed in FoUSB and that of the Target MCU match 6 4 FoUSB cannot operate Why When FoUSB Flash over USB is started in the state where your host computer PC USB Cable USB Monitor Board Flat Cable and Target Board are connected the firmware of USB MCU is erased or damaged if the following window see Figure 6 1 is displayed Moreover when firmware is erased or damaged the status display of USB Monitor Board lights only a Power indicator FOUSB and KD KD30 KD3083 cannot be used 6 Troubleshooting FLASH OVER USB Ewes Se OPEN READ ERASE e UNLOCK FILE PROGRAM E SETTINGS HELP EXIT Everywhere you imagine emm Te
34. Xcout P16ANT4 5k 30pF 10MHz 30pF Example Connection for M16C 26 26A 28 29 2 Note It is necessary to connect the CE pin or the EPM RP pin and the P1_6 pin The EPM RP pin connected in this Target and the P1_6 pin are USB Monitor Board FLAT Cable Connection Connector Type HIF3FC 10PA 2 54DSA 10 Pin Connector assign Signal Cap TS z BUSY Et 2 JE RxD P16 S P EPM RP o F RESET PLS CNVss TD FE l A 477 5k 0 1uF 0 1uF 5k User Reset Signal Met 5k P64 CTS1 RTS1I CTSO CLKS1 P66 RxD1 P85 NMI P67 TxD1 P65 CLK1 P86 Xcout Dog 82 7 Appendix Example Connection for M16C 10 0 1uF Vec Vee Ze BUSY USB Monitor Board am o WE 4 J Lae SCLK RxD E a P S77 g 0 RESET FLAT Cable Connection 1 o EH S Connector Type P17 CNTRO HIF3FC 10PA 2 54DSA P15 RxD 10 Pin Connector assign P14 TxD 30pF P16 CLK 10MHz 30p
35. al setting 1 Automatic setting Automatic setting checks in the following condition in ID code of All FFh and All 00h gt gt When FoUSB is started gt gt When a firmware is changed during FoUSB use This condition shows FoUSB restart If the ID code consists All 00h Figure 4 16 will be displayed and the Target MCU is unlocked When the ID code of Target MCU is not All FFh or All 00h please unlock Target MCU using manual setting Unlocked a Your device has been automatically unlocked with the ID code 00 00 00 00 00 00 00 Figure 4 16 Unlocked screen Automatic setting can select whether it performs by user Click the SETTING button and user setting screen is displayed Select enabled or disabled in Auto Unlocok check box and click the lt Save gt button Options I Debug Mode I Show splash screen I Ign jor 0 READ i EA ERASE F Language Engish x UNLOCK z Ez PROGRAM mAutomated Programming zeg x net 3 is save P Se eegend H E es SETTINGS HELP EXIT verywhere you imagine a ee Note When the lt Cancel gt button is clicked on a user setting screen a former setting condition is saved 4 Using the FoUSB 2 Manual setting If you click the UNLOCK button Figure 4 17 will be displayed Enter the ID code and click the lt OK gt button When the ID code written in the
36. circuit numbers are built in MCU NOTICE The software break number of MCUs M16C 10 Group number 2 points software break M16C 1N M16C 24 2 points 2 points M16C 26 26A 6 points M16C 28 6 points Group software break number M16C 6N 2 points M3062NAFG M3062NBFC M16C 6N 8 points M306N4FC M306N4FG M306N5FC M16C 29 6 points R8C Tiny Series 2 points M16C 62A M 2 points M16C 80 4 points M16C 62P 8 points M32C 83 4 points M16C 62N 2 points M32C 84 85 86 87 8 points 3 Installing 3 1 Before installing Do not connect the USB Cable which belongs to this product to the Host computer PC before installing 3 2 Preparation before installing Be sure to confirm the following point before performing installation of a tool GUI and a driver 1 The CD ROM includes files required for the FoUSB Flash over USB installation Copy all files to any folder in your PC before installation 2 All tools and USB drivers must be installed with the administrator if installed on Windows 2000 XP Both PowerUser for a standard access and User for a limited access can use software after installation 3 Installing 3 3 FOUSB Flash over USB installing 3 3 1 Method of Installation 1 To install FoUSB double click FoUSB_V exe on the folder into which you ve copied FoUSB files from the CD ROM 2 Select the lang
37. d Flat Cable and Target Board are firmly connected See Figure 5 1 U z USB Monitor Board Flat Cable Target Board Figure 5 1 connect 2 5 Using the KD 5 1 2 Starting the KD 1 From the Start menu choose Programs RENESAS TOOLS KD30 V Release KD30 to start the KD When the KD starts the screen shown in Figure 5 2 appears If the screen appears click the lt Refer gt button and choose MCU File Note In the case of M16C 80 and M32C 80 start KD3083 MCU Debugging Information Run Mode Resume CG Parallel C Seial FLAN LPT USB m Monitor Debug Startup for monitor denua Cancel Help Ir Next Hide Figure 5 2 Init screen 1 2 Next the Select MCU File screen on Figure 5 3 will be displayed For KD30 select the category folder of MCU to be used from the MCU category folder of the McuFiles folder and open it For KD3083 open the MCU File from the McuFiles folder Select MCU File 2x Lookin S Mewies AA A ol M16C 10 Series t iere M16C 24 Group G Select MCU File 21x DS ck in aM 160 26 Group Je Al cl M16C 264 Group MI6C 28 Group C 8 M30262f3 meu M16C 29 Group M30262f4 mcu File name mcu Files of type mcu File File name M30262f8 meu C Files of type mcu Files mcu D Cancel Figure 5 3 Select MCU File screen 5 Using the KD 3 The Init screen of the Figure 5 4 opens when it is done after a
38. device or system that is used under circumstances in which human life is potentially at stake Please contact Renesas Technology Corporation or an authorized Renesas Technology Corporation 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 The prior written approval of Renesas Technology Corporation is necessary to reprint or reproduce in whole or in part these materials 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 Please contact Renesas Technology Corporation for further details on these materials or the products contained therein Microsoft MS and MS DOS are registered trademarks of Microsoft Corporation of the U S Windows is trademark of Microsoft Corporation of the U S IBM and PC AT are registered trademarks of International Business Machines Corporation of the U S Pentium is a trademark of Intel Corporation of the U S Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated Preface Thank you for purchasing Renesas USB Flash Wri
39. directory or folder 2 Whether the source file has been opened by any editor other than the KD 6 9 Is peripheral I O operating during a break Although no interrupts are accepted during a break peripheral I O continues operating If the User Program is halted by a break after starting a timer for example timer interrupts are not accepted although the timer continues counting 6 10 Can coveragefunction be used in KD Coverage function cannot be used in KD 6 11 Can check sum function be used FoUSB dose not have check sum function Therefore when checking written contents check READ gt Verify gt Verification For details refer to 4 1 3 Details of Main Button 1 6 12 ID code written to microcomputer after KD exits The ID code of the User Program is not written to the microcomputer but all FFh is written to it when using KD Therefore the ID code which is written to the microcomputer after KD exits is assumed all FFh 6 Troubleshooting 6 13 Debug operation has not worked well Isn t the resource of a Monitor Program used When using the resource of the Monitor Program in debug a communication error or an unexpected operation may occur Therefore note that the resource of the Monitor Program should not be used a Peripheral Serial UO The BUSY SCLK TxD and RxD pins are used for communications between the Target MCU and KD30 KD3083 Do not connect a user I O to the
40. ection again dee SETTINGS Everywhere you imagine emm em Figure 4 25 Error screen d Click the Select MCU button and download the firmware to the USB Monitor Board Refer to 2 to 5 of this section for details e When the download of the firmware is completed Figure 4 25 will be displayed again Ignore the error and click the lt OK gt button Finish FoUSB f Remove the USB Monitor Board from host computer PC and set the power source supply selector S1 Power Mode on the USB Monitor Board to the TARGET side Refer to Figure 4 3 g Connect the PC USB Monitor Board and Target Board h Input 3 3V to the Target Board and USB Monitor Board from the external power External Power Supply F J USB Monitor Board d E J Target Board FoUSB KD30 KD3083 are included can be used in 3 3V operation with the above procedure 4 Using the FoUSB 4 1 6 Monitor Information 1 Monitor Firmware The version of the firmware currently written in the USB Monitor Board is indicated here 2 MMI Loaded The name of the firmware currently written in the USB Monitor Board is indicated here 3 Serial Boot Code The boot version written in the MCU is indicated here 4 1 7 Detailed File Information 1 DETAILS button Shows details of the downloaded data program size ID code blocks and sections used 2 SECTIONS button Shows the address area in which the downloaded data are written 3 MAP button Shows the
41. eeisreseesisrtsttstresttntentsttntsntntentnnententnnentenennennentanenne 60 5 2 3 Limitations on Memory Eviension AEN 61 5 2 4 Precautions on Internal Reserved Area Expansion Dn 61 5 2 5 Limitations on Stop and Wait Mocdes AAA 62 5 2 6 Realtime Capability of the User Program 62 5 3 Memory Map Limitations eege ben ia a A N 63 5 4 Peripheral Function Related Limitations ENEE 66 5 5 FOUSB Debugger pell geseis dee ences coe en ender tase ene arden ene 66 5 5 1 Communication Function with Fo AE 67 5 5 2 Command EXecution EE 67 5 5 3 The difference from an actual CPU operaton nene 68 Troubleshooting a sssce0siecas aes etdiicen aaaea a a a E a aA AENEA A pE TEE AENEA TE EE EEAS 69 6 1 FoUSB cannot communicate with the Target MCU Wmd AAA 69 6 2 The MCU cannot enter standerd Serial O wm NEE 69 6 3 The MCU cannot be programmed using FOUSB Why NEE 69 6 4 FOUSB cannot operate WHY een 69 6 4 1 Compulsive download procedure Of Tmmware ue 71 6 5 Can FoUSB information be transmitted to KN 74 6 6 A communication error occurs when the KD starts What is the cause of this Droblem eee 74 Table of Content 6 7 A communication error occurred when debugging the program What is the cause of this problem 74 6 8 A message Source file cannot be found was output What should dot 75 6 9 Is peripheral I O operating during a break AEN 75 6 10 Can coveragefunction be used in KI 75 6 11 Can check SUM function e KEE 75 6 12 ID code wr
42. emote Debugger AAA 26 Using the FOUSB EE 27 4 1 Using the FOUSB Floaeb over UP 27 4 1 1 Before Starting the Fo 27 451 2 FOUSB Slants EE 30 4 1 3 Details of Main Button A BEE 31 4 1 4 Details of the Update Button AEN 42 4 1 5 Details of the Select MCU Button 43 4 1 6 Monitor Information ai2 sci seinen hn ee hi ee ees eee 47 4 1 7 Detailed Eielmtormmeten seiss AER tars ceed sueueuedsesuesites seetnecurecesesurgesivsestveesteceetaeesseevecnsteevtee 47 4 1 8 Details of Main Button EE 47 Table of Content A 2 Otner e 48 ie eu KB EE 49 5T Using the KD EE 49 5 41 Before Starting the Kean Rate idee dahl al ee el 49 51 2 Starting OR RE 50 5 tS Program DOWN odd ee ccceccneetsscataes iescecezca aise xasc decstanssd as aA Parr SAET E ses snepeesinsapeFeiedeeensdasasaesiesereerss 55 51 4 Program Executions ak EE EE SERA 56 5 15 Program StOp scarcverayste wae diet ahead tides aint asin niet auidiieen E acta 56 5 1 6 Program Step Execution srs cscs GENEE EE E TATT 56 5 1c 7sottware Break Method aa a aE a a aR aa a aerae Ea aa ae aai aa A Re TE AE ari 57 51 8 ResetiExecutlon kaiina a A A E eens 57 WE RE Eeler 57 5 1 10 If a Communication Error OCCUIS esii ii riea iaon ariaa ai a i p iaa 58 5 1 11 Error Except a Communication Error Oecurs nenne 58 5 112 Operation Method geneet A ea ee i ee nee 58 RA KNUET 59 5 2 1 Limitations on Special Page Vechor AEN 59 5 2 2 A limitation item about the language s seseeseess
43. et Signal P64 CTS1 RTS1 CT50 CLKS1 P66 RxD1 Xin P55 HOLD 10MHz 30pF P67 TxD1 P65 CLK1 P50 WRUWR P85 NMI 30pF 84 7 Appendix Example Connection for R8C 10 11 12 13 USB Monitor Board co Pin No 1 FLAT Cable Connection Connector Type HIF3FC 10PA 2 54DSA 10 Pin Connector assign Por e sl en ES MODE 0 1uF RxD OI RESET TxD o Mo Po fo fo 33k MODE P37 RxD1 POO TxD11 User Reset Signal 30pF C_J 10MHz 30pF Example Connection for 7542 USB Monitor Board co FLAT Cable Connection Connector Type HIF3FC 10PA 2 54DSA 10 Pin Connector assign Signal Vee BUSY SCLK RxD CE EPM GND Vec SCLK CE GND a CNVss PSPSPS to be ke le be 477 P04 LEDO4 RxD2 PO5 LED05 TxD2 User Reset Signal P32 LED12 ICMP3 P37 LED17 cm POS LEDO6 ISCLK2 POXLEDO7 mm Note When the flash mode control pins are used for user s application circuit Refer to the 7542 group datasheet for operation details 85 Exam
44. et en Figure 6 1 FoUSB main window Figure 6 2 USB Monitor Board Board In such a case it is necessary to download firmware compulsorily to USB MCU Please perform compulsive download of firmware to USB MCU according to the procedure shown in the following page 6 Troubleshooting 6 4 1 Compulsive download procedure of firmware 1 Remove the cover of USB Monitor Board and make a USB Monitor Board Board the following setup il USBside PB 2 Connect the USB Monitor Board Board with your host computer PC PC with Windows 98SE ME 2000 or XP d USB Monitor Board mmn ess USB Cable 3 Start FoUSB Flash over USB and click the Load MMI button on a GUI window FLASH OVER USB te gg e UNLOCK PROGRAM b gt Click here asn e Information of USB MCU eat SETTINGS HELP EXIT Everywhere you imagine emm me RE 6 Troubleshooting 4 On the Chip Selection screen select your MCU and download a firmware to the USB MCU Chip Selection x E maoe20FcP 1 Select your MCU Kumar BAK 4K 4K Dah Sh 4h 5 If download of firmware is completed to USB MCU since the completion screen of download will be displayed click the lt OK gt button FOUSB USB Monitor Programmed succesfully Remove the MCU MODE jumper and reset the board 6 End FoUSB and separate a USB Monitor Board Board from your host computer PC 7 Make Open JP1 MCU M
45. et to the USB side 5 2 4 Precautions on Internal Reserved Area Expansion Bit a M16C 62A M M16C 62P The Target MCU operates when the PM13 bit Internal Reserved Area Expansion Bit is set to 1 Expands the internal RAM area and internal ROM area to over 15KB and to over 192KB respectively for 256KB or above version of the M16C 62A M and 62P groups Since the access area of the internal memory is limited The Monitor Program RAM area is limited by setting the PM13 bit to 0 the KD will not be able to be used Therefore do not set the PM13 bit to 0 on the User Program Applicable MCUs M30624FGAFP GP M30625FGAGP M30624FGMFP GP M30625FGMGP M30624FGPFP GP M30625FGPGP M30626FHPFP GP M30627FHPGP M30626FJPFP GP M30627FJPGP b M16C 6N 6N4 The Target MCU operates when the PM13 bit Internal Reserved Area Expansion Bit is set to 1 Expands the internal ROM area to over 192KB for 256KB version of the M16C 6N 6N4 group Although the PM13 bit is set to 0 the Monitor Program area is not limited and the KD will be able to be used However the area of COO000h to CFFFFh cannot be used Applicable MCUs M306N4FGTFP c M16C 6N 6NA The Target MCU operates when the PM13 Internal Reserved Area Expansion BIt is set to 0 The internal ROM area is 192KB or less for 256KB version of the M16C 6N 6NA group Therefore the area of C0000h to CFFFFh cannot be used When using the area of CO000h to CFFF
46. ftware includes USB Flash Writer run on the Host Computer PC under the OS Operating System version that are listed respectively in Table 1 2 Table 1 2 Operating Environment Host Computer PC IBM PC AT series or its compatible OS Operating System Microsoft Windows 98SE ME 2000 XP PU i Pentium Il 2833MHz or newer recommended 8 Mbyte or more 16 Mbyte recommended 1 3 Compatible Products Compatible products with USB Flash Writer are as follows Table 1 3 Compatible Products 1 M16C 10 MCU Product Name M30100F3FP M30102F3FP Corresponding Software FoUSB KD30 MCU Product Name to select in Software M30102F3 M16C 1N M301N2F8TFP FoUSB KD30 M301N2F8 M16C 24 M30245FCGP FoUSB KD30 M30245FC M16C 26 M30262F3GP FoUSB KD30 M30262F3 M30262F4GP FoUSB KD30 M30262F4 M30262F6GP FoUSB KD30 M30262F6 M30262F8GP FoUSB KD30 M30262F8 M16C 26A M30260F3AGP FoUSB KD30 M30260F3A M30260F4AGP FoUSB KD30 M30260F4A M30260F6AGP FoUSB KD30 M30260F6A M30260F8AGP FoUSB KD30 M30260F8A M30263F3AFP FoUSB KD30 M30263F3A M30263F4AFP FoUSB KD30 M30263F4A M30263F6AFP FoUSB KD30 M30263F6A M30263F8AFP FoUSB KD30 M30263F8A M16C 28 M30280F6HP FoUSB KD30 M30280F6 M30280F8HP FoUSB KD30 M30280F8 M30280FAHP FoUSB KD30 M30280FA M3028
47. ftware that runs on a Windows version host computer This KD is usable for only the R8C Tiny M16C 10 M16C 20 M16C Tiny M16C 60 M16C 80 or M32C 80 series of Renesas 16 bit and 32 bit single chip microcomputers with built in flash memory The KD provides a powerful debugging environment In addition it is operationally compatible with and can therefore be used the same way as PD30 or PD308F the emulator control debugger for Renesas 16C 62 microcomputers The features of the Remote Debugger are outlined below For details see Section 5 Using the KD Table 2 1 PD30 and KD30 comparison Software break function 64 points 2 points to 8 points Note Hardware break function 6 points not included RAM monitor function included included Real time trace included not included Time measurement function included not included Script function included included Note Software break numbers are dependent on the address match circuit numbers are built in MCU 2 Product Specifications Table 2 2 PD308F and KD3083 comparison PD308F KD3083 1 Software break function 64 points 4 points to 8 points Note 2 Hardware break function 6 points not included 3 RAM monitor function included included 4 Real time trace included not included 5 Time measurement function included not included 6 Script function included included Note Software break numbers are dependent on the address match
48. he Target MCU is idle RUN Green When steadily on the Target MCU is running STATUS Yellow When flashing normal the USB Monitor is normal When flashing fast the USB Monitor is operating erratically Note When steadily on the Target MCU is being supplied with power Note If this LED flashes fast the USB Monitor Board may have gone wild In such a case see Section 6 Troubleshooting 87 7 Appendix 7 2 Installation of a USB Driver and recognition of USB Monitor Board Manual setup 7 2 1 For USBMON Driver 1 Remove the cover of USB Monitor Board and make a USB Monitor Board Board the following setup before installing USBMON Driver If a setup is completed attach a cover in a USB Monitor Board Board Power Source Supply Selector S1 Power Mode USB side MCU Mode Pin JP1 MCU Mode Open 2 Connect the USB Monitor Board included with package to the USB port of your host computer PC The Power indicator D1 Power of USB Monitor Board lights and a Status indicator D4 Status blinks PC with Windows 98SE ME 2000 or XP o E l USB Monitor Board USB Cable 3 Windows system recognizes new hardware The following installation methods are the examples which used Windows 98SE Although the installation methods difer a little for every operating system it is installable by the almost same operation 88 7 Appendix 4 Recognition of new hardware displays an
49. imitations Table 5 2 and Table 5 3 list the ROM RAM areas which the monitor program uses Figure 5 12 shows the memory map Table 5 2 ROM RAM areas 1 ROM RAM XXXXXh YYYYYh ZZZZZh M16C 10 M30102F3 24K 1K 780h 7FFh OFA000h M16C 1N M301N2F8 64K 3K F80h FFFh OF0000h M16C 24 M30245FC 128K 10K 2B80h 2BFFh 0E0000h M16C 26 M30262F3 24K 1K 780h 7FFh OFA000h M30262F4 32K 1K 780h 7FFh OF8000h M30262F6 48K 2K B80h BFFh 0F4000h M30262F8 64K 2K B80h BFFh OF0000h M16C 26A M30260F3A 24K 1K 780h 7FFh OFA000h M30260F4A 32K 1K 780h 7FFh OF8000h M30260F6A 48K 2K B80h BFFh 0F4000h M30260F8A 64K 2K B80h BFFh OF0000h M30263F3A 24K 1K 780h 7FFh OFA000h M30263F4A 32K 1K 780h 7FFh OF8000h M30263F6A 48K 2K B80h BFFh 0F4000h M30263F8A 64K 2K B80h BFFh OF0000h M16C 28 M30280F6 48K 4K 1380h 13FFh 0F4000h M30280F8 64K 4K 1380h 13FFh OF0000h M30280FA 96K 8K 2380h 23FFh 0E8000h M30281F6 48K 4K 1380h 13FFh 0F4000h M30281F8 64K 4K 1380h 13FFh OF0000h M30281FA 96K 8K 2380h 23FFh 0E8000h M16C 29 M30290F8 64K 4K 1380h 13FFh OF0000h M30290FA 96K 8K 2380h 23FFh 0E8000h M30290FC 128K 12K 3380h 33FFh 0E0000h M30291F8 64K 4K 1380h 13FFh OF0000h M30291FA 96K 8K 2380h 23FFh 0E8000h M30291FC 128K 12K 3380h 33FFh O0E0000h M16C 62A M30620FCA 128K 10K 2B80h 2BFFh OE0000h 62M M30624FGA 256K 20K 5380h 53FFh 0C0000h
50. ined 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 Corporation without notice due to product improvements or other reasons It is therefore recommended that customers contact Renesas Technology Corporation or an authorized Renesas Technology Corporation 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 Corporation 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 Corporation by various means including the Renesas Technology Corporation Semiconductor home page http Awww renesas com 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 Corporation assumes no responsibility for any damage liability or other loss resulting from the information contained herein Renesas Technology Corporation semiconductors are not designed or manufactured for use in a
51. itten to microcomputer after KD XitS EE 75 6 13 Debug operation has not Worked well AEN 76 6 14 Message let opges de slits Aer E eae th eet a ee ee dee 78 tac en 79 7 1 WSB Monitor BOard tee eebe livid iain ihe Dit tte a 79 74 1 Board Specifications cicecisetiina ada ed ee 79 en e lU 80 KEE HE Eu Ee E e EEN 80 7 1 4 Power Source Supply Gelechor AA 87 7 15 LED Status Indicators whichis cee ie ee 87 7 2 Installation of a USB Driver and recognition of USB Monitor Board Manual sep 88 7 2 1 FOPUSBMON HE VE 88 E e e TER 91 7 3 Referencing Electronic Manuals se ceccceseecscesseseseeseeeeseseeeseesceetsceeesceesseeseesseeesceessseessesesenseeeeeeteeeeeoeees 95 T A Product Tute E 95 1 Contents of Product 1 Contents of Product This section shows the contents of theUSB Flash Writers product package When unpacking your USB Flash Writer check to see that all products listed below are included 1 1 Contents of product Table 1 1 lists the products included in the USB Flash Writer Table 1 1 USB Flash Writer Product List Product List Quantity USB Monitor Board USB Cable Used for the connection with the Host Computer Flat Cable Pin Header HIFS3FC 10P 2 54DSA straight type CD ROM pc Je Note 1 Starter kit doesn t include pin header straight type Note 2 When a FoUSB is included with starter kit only one CD ROM is in the FoUSB 1 Contents of Product 1 2 Operating Environment The so
52. ks Select All or erase evry one block When you select a block to erase the check box by block is indicated with a check mark and the block is displayed in color Click the lt Erase gt button and the block will be erased See Figure 4 14 Select All Blocks Start Address E GUEUE M430262F8 Flash Blocks trae Help ES Figure 4 14 Erase Flash 1 4 Using the FoUSB 3 After downloading The system reads information from the downloaded data to determine which block to erase and marks the corresponding check box with a check mark and displays the block in color Click the lt Erase gt button and the block will be erased You can erase all blocks collectively or one block at a time See Figure 4 15 Erase Flash x F200 Select All Blocks Start Address M 30262F8 Flash Blocks Help oneal Figure 4 15 Erase Flash 2 4 UNLOCK button This button sends the ID code to the locked Target MCU and unlock the Target MCU In the Locked display as shown in the following figure a flash command program erase read verify to the Target MCU cannot be e xecuted St 3 Seria 1 Unlocked UNLOCK P TONG SE Flash command can be executed PROGRAM ger SECTIONS Flash command cannot be executed Everywhere you imagine SS 4 Using the FoUSB When you click the UNLOCK button the system checks ID code The ID code check has automatic setting and manu
53. lect the lt Show ASCIl gt check box in the Options section and ASCII code will be added to the downloaded data See Figure 4 9 and Figure 4 10 Flash Memory Read X Verify SKPTest mot verify Current loaded firmware image Read Area n S al OEE een gt ah SS From Jop to FFFFF hex teas Area Ge Display data in custom window Options EECH Display using notepad exe Change Editor C Save to Motorola S Record File Figure 4 9 Flash Memory Read screen 2 Flash memory contents of x ASCII F6666 16 27 E8 63 64 66 GA 66 61 66 53 4B 50 20 54 ob d SKP Te a F6616 73 74 66 26 26 26 26 26 20 26 26 66 31 3A 280 53 st Sue SS F6626 57 26 26 26 66 4C 45 44 20 54 53 54 20 66 32 3A W amp LED TST 2 F6636 26 50 4F 54 26 26 66 33 3A 26 54 45 4D 56 26 66 POT 3 TEMP F0046 34 3A 26 52 53 32 33 32 66 35 3A 26 4D 2D 4F 53 4 RS232 5 M OS F6656 43 66 52 4D 26 52 45 53 26 20 66 26 26 26 26 260 C RM RES F66660 26 26 20 66 53 54 4F 56 560 45 44 26 66 52 55 4E STOPPED RUN FO676 4E 49 4E 47 26 66 36 3A 58 43 26 4F 53 43 66 37 NING 6 XC OSC 7 FO686 3A 52 43 20 4F 53 43 66 49 4E 53 2D 4A 33 26 34 RC OSC INS J3 amp 4 F6696 66 36 31 32 33 34 35 36 37 38 39 26 66 66 EB 46 6123456789 FOGAG 91 65 C7 02 GA 66 7E ar 56 66 7E 8F 36 00 7E 8F P 6 FOGBG 37 60 7E 8F 3E 66 7E 8F 3F 66 7E 9F 60 60 7E OF 7 gt FO6CG 6
54. m the Start menu choose Programs RENESAS TOOLS Flash over USB V FoUSB Programmer to start the FoUSB When the FoUSB starts the FoUSB main window shown in Figure 4 4 appears Q R B P 7 Ti lt Si vue LE ye i LJ Map Figure 4 4 FoUSB main window 2 Guide to understanding the display of the main screen Content Main button 1 Use these main buttons to download a program as well as read erase or write to the flash memory Update button Click this button to upgrade the FoUSB version MCU select button Use this button to select the Target MCU Monitor information Shows information on the selected MCU Detail button Shows detailed information on the downloaded program Main button 2 Use these main buttons to set functions show help or exit 4 Using the FoUSB 4 1 3 Details of Main Button 1 1 OPEN button This button reads the downloading programming file to the Target MCU 1 Click the OPEN button and the screen shown in Figure 4 5 will appear allowing you to choose the file to download into the Target MCU The type of file that can be downloaded is HEX or Motorola After selecting the file to download click the lt Open gt button Open 2 x Lokin aser eA A alba File name SKPT est mot J Files of type Intel Hex or Motorola S Record zl Cancel Z Figure 4 5 Open screen
55. mm bel Pele Gi le va fee fe ot p x4 Ed vod Lo A EE sod or as x E 970d LX p d p ES ECO DH E OT our or or L ou geome ova Les EM zy Wi s N KKH Trd H H H IST Santo SE eod za LS Di E Ee eva LO E D Z 5 et fi Bn SI ves Gir 2 Ger DA GH 24 Meee z lt lt OJYMOd Lui N D EP ae 7 aaum od sng gsn 39D S E E E TINDAVOX Od f k Nid Ile iod LS HOCH EE H OINI Tra e anto bat SG BR TINI Zyd y nao A3 OVvzZ0Z0ZAV ta DIN vd e IC EI Od Ts t THIND Prd 7 5 Na ad T gjNi Up De anzz anto is he Amt o P ig g S NI B Sep 99 or Kei z2 XOT OT 180Z E0 2Z OGEEPZSAL 15 F ru Les ozy lt ey zal en kd dh DA MIEO90XTIWS REVISION HISTORY z T Description ev ate Summary Jul 12 2003 Whole page is revised according to the firm name chage Sep 12 2003 Changed method of USB Driver s installation Added limitations on Memory Expansion M16C 62P Oct 15 2003 Added method of USB Driver s FoUSB Driver installation Added countermeasure when a firmware of USB MCU is erased or damaged Changed example connection of target board M16C 26 28 Nov 05 2003 Changed example connection of target board M16C 26 28 Jan 15 2004 Jan 31 2004 Changed example connection of target board addition of oscillator circuit Added example connection of target board M16C 1N and M32C 85 Changed peripheral function related limitations
56. nding flash block is erased 4 1 4 Details of the Update Button Use the Update button when you want to upgrade the version of FoUSB 4 Using the FoUSB 4 1 5 Details of the Select MCU Button 1 The following MCUs can be selected in FoUSB MCU Product Name MCU Product Name Group MCU ProductName Group toselectin FOUSB M16C 62A M16C 10 M30102F3 M16C 1N M301N2F8 M16C 24 M30245FC 62M to selectin FoUSB M30620FCA M30624FGA M3062GFE8N Note R8C 10 to selectin FoUSB R5F21102 R5F21103 R5F21104 M16C 26 M30262F3 M30262F4 M30262F6 M30262F8 M16C 26A M30260F3A M30260F4A M30260F6A M30260F8A M30263F3A M30263F4A M30263F6A M30263F8A M16C 62P M30622F8P M30623F8P M30620FCP M30621FCP M30624FGP M30625FGP M30626FHP M30627FHP M30626FJP M30627FJP R8C 11 R5F21112 R5F21113 R5F21114 R8C 12 R5F21122 R5F21123 R5F21124 R8C 13 R5F21132 R5F21133 R5F21134 M37542F8 M16C 28 M16C 29 Note M3062GF8N M16C 62N Group is contained in M16C 62A Group list M30280F6 M30280F8 M30280FA M30281F6 M30281F8 M30281FA M30290F8 M30290FA M30290FC M30291F8 M30291FA M30291FC M16C 6N M306N4FC M306N4FG M306N5FC M306NAFG M306NBFC M38C29FF M16C 80 M32C 83 M30800FC M30803FG M30833FJ M30835FJ M32C 84 M30845FJ M32C 85 M30855FH M30855FW M30852FJ M32C 86 M30865FJ M32C 87 M3087
57. ninstalling the Remote Debugger To uninstall choose Settings Control Panel from the Start menu and then click the Add Remove Programs Select KD from the program list and click the lt Add Remove gt button An uninstall window will appear with the integrated development environment uninsalled The uninstallation of KD3083 is the same too 4 Using the FoUSB 4 Using the FoUSB 4 1 Using the FoUSB Flash over USB 4 1 1 Before Starting the FoUSB 1 Check to see that the FoUSB is installed in your host computer PC 2 Check to see that PC USB Cable USB Monitor Board Flat Cable and Target Board are firmly connected See Figure 4 1 3 USB Monitor Board 1 USB Cable 4 Flat Cable 2 Target Board d J Ee H BS Target MCU U Figure 4 1 connect 4 Using the FoUSB 3 Connection Method It specifies as a premise that MCU is carried on the Target Board 1 Connection order when using the USB bus powered Connect in order of 2 4 3 1 host computer PC 2 Separation order after using the USB bus powered Connect in order of PC 1 3 4 2 3 Connection order when using external power supply Set a power source supply selector to the TARGET side Connect in order of PC 1 3 4 2 and finally supply power from outside 4 Separation order after using external power supply Drop the power which is supplied from outside Separate in order of PC 1 3 4 2 4 The power source supply selector on the USB M
58. note of this Next click the UNLOCK button The screen into which the ID code of the read file was input is displayed When clicking the OK button the ID code written in the Target MCU and the input ID code match and the Target MCU will be unlocked Enter the 7 byte HEX ID code or oe or for fos foo for non FOUSB Succesfully Unlocked NOTICE ID code address of MCU Series ID code address M16C 10 M16C 20 M16C Tiny M16C 60 ID1 ID2 ID3 ID4 ID5 ID6 ID7 OFFFDFh OFFFESh OFFFEBh OFFFEFh OFFFF3h OFFFF7h OFFFFBh M16C 80 M32C 80 ID1 ID2 ID3 ID4 ID5 ID6 ID7 OFFFFDFh OFFFFESh OFFFFEBh OFFFFEFh OFFFFF3h OFFFFF7h OFFFFFBh R8C Tiny ID1 ID2 ID3 ID4 ID5 ID6 ID7 OFFDFh OFFE3h OFFEBh OFFEFh OFFF3h OFFF7h OFFFBh 740 38000 ID1 ID2 ID3 ID4 ID5 ID6 ID7 The ID code address of following relations Dialog Enter the 7 byte HEX ID code Io fio2 Jos fioa fios Joe Jos Fill 00 Fill FF OK Cancel OFFD4h OFFD5Sh OFFD6h OFFD7h OFFD8h OFFD9h OFFDAh 4 Using the FoUSB MCU and the ID code input forms of FoUSB are the 4 Using the FoUSB 5 PROGRAM button This button performs programming to the Target MCU 1 Click the PROGRAM button and the screen shown in Figure 4 20 will appear Program Flash EN Choose an Operation Erase gt Program gt Verify
59. ode Pin of the USB Monitor Board Board 6 Troubleshooting 8 Connect USB Monitor Board Board with your host computer PC PC with Windows 98SE ME 2000 or XP u A USB Monitor Board USB Cable 9 Since firmware has downloaded normally if a Power indicator D4 Status is lighting and the Status indicator is blinking as shown in the following figure FOUSB and KD KD30 KD3083 can be used blinking Di Ear m lighting 10 Separete USB Monitor Board Board from PC and attach a cover in the USB Monitor Board Board 11 Now you ve finished compulsive downloading the firmware 6 Troubleshooting 6 5 Can FoUSB information be transmitted to KD A written program using FoUSB cannot be debugged with KD It is necessary to download a program on KD again when executing debug using KD Therefore written program information in flash area is not transmitted to KD30 KD3083 6 6 A communication error occurs when the KD starts What is 6 7 the cause of this problem If a communication error occurs when the KD starts check the following 1 Whether the cables are properly connected and whether the power is turned on 2 Whether the serial port you set in the KD s Init dialog box is correct 3 Whether the Status indicator D4 Status of USB Monitor board is blink 4 Has CNVSss pin on the target board been pulled down 5 Is the target MCU ID code all 00h or all FFh In 3 when the S
60. ogram formula Monitor program ROM size Approx 1600 byte In the case of R8C Tiny Series 2K byte RAM size 128 byte In the case of M16C 80 Group 256 byte In the case of M32C 80 Series 256 byte In the case of R8C Tiny Series not used Operation frequency 700KHz or above Note1 Operation mode Single chip mode Software break 2 points to 8 points Note2 USB microcomputer M37641F8HP 8 bit USB flash microcomputer USB interface J1 USB2 0 full speed Target interface J3 Synchronous serial Interface Starter kit and 10 pin connector for target board connection Operation voltage 4 75V to 5 25V USB bus powered supply or target supply enabled 3 0V to 3 6V supply from target is necessary Note3 Power consumption Max 50mA Board size 70mm x 29mm Use environment condition Temperature 25 5 C no corrosive gas at the time of operation Humidity no condensation Use environment condition Temperature 25 5 C no corrosive gas at the time of storage Humidity no condensation Note 1 Maximum operating frequency is dependent on the MCU Note 2 Software break numbers are dependent on the address match circuit numbers are built in MCU Note 3 When operating in 3 3V supply power from the target board In this case it is not possible to change the FoUSB firmware When the model name of the microcomputer to be used is changed remove the target board supply the USB bus p
61. on the Relocatable Vector Table Variable Vector Table in the User Program it is necessary to set the UARTIi receive interrupt routine FF900h or FFF900h on the Monitor Program to the vector address of the UARTI receive interrupt lt Hardware Interrupt gt Interrupt Vector Address R8C Tiny M16C 10 20 60 Tiny M16C 80 M32C 80 BRK Instruction FFE4h to FFE7h FFFE4h to FFFE7h FFFFE4h to FFFFE7h Address Match FFE8h to FFEBh FFFE8h to FFFEBh FFFFE8h to FFFFEBh Single Step FFECh to FFEFh FFFECh to FFFEFh FFFFECh to FFFFEFh DBC FFF4h to FFF7h FFFF4h to FFFF7h FFFFF4h to FFFFF7h lt Software Interrup gt UARTO transmit receive interrupt M16C 10 series UART1 transmit receive interrupt MCUs other than M16C 10 series Note Whether the DBC interrupt is applicable or not and the UART channel are shown below Users cannot use the UARTi transmit receive interrupt even if the DBC interrupt is applicable M16C 10 N A M16C 80 N A M16C 1N N A M32C 83 Applicable M16C 24 N A M32C 84 85 86 87 Applicable M16C 26 26A 28 29 Applicable R8C 10 11 12 13 Applicable M16C 62A M 62N N A M16C 6N N A M306NAFG M306NBFC M16C 6N Applicable M306N4FC M306N4FG M306N5FC M16C 62P Applicable Related section 5 2 2 A limitation item about the C language 2 5 4 Peripheral Function Related Limitations 2 6 Troubleshooting 6 14 Message List The following lists the messages
62. onitor Board must be set differently depending on the Target MCU used 1 When using 5 V The power for the Target MCU is supplied from the USB Monitor Board Therefore there is no need to supply power for the Target MCU from the Target Board In this case set the power supply selector on the USB Monitor Board to the USB side as shown in Figure 4 2 TARGET uss 5 ENES When using 5 V set the Power Moa switch to the USB side USB PC STOP RUN STATUS RTA FoUSB MON Fiash Programmer amp in Circuit Debugger Figure 4 2 Power source supply selector 1 4 Using the FoUSB 2 When using 3 3 V The power for the Target MCU is not supplied from the USB Monitor Board and must therefore be supplied from the Target Board In this case set the power source supply selector on the USB Monitor Board to the TARGET side as shown in Figure 4 3 gt usa RG When using 3 3 V set the Mod switch to the TARGET SS ue B PC STOP RUN RTA FoUSB MON Fiash Programmer amp In Circuit Debugger Figure 4 3 Power source supply selector 2 3 Other Depending on the host computer PC environment you are using no 5 V power supply may be fed to the Target MCU even when the select switch on the USB Monitor Board is set to the USB side In such a case set the power source supply selector to the TARGET side so that the power for the Target MCU will be supplied from the Target Board 4 Using the FoUSB 4 1 2 FoUSB starts 1 Fro
63. owered and rewrite the firmware 1 Contents of Product 1 5 CD ROM The CD ROM contains software products necessary for developing programs and electronic manuals as well Here follow the contents of the CD ROM CD ROM Rev 2 10 or later root Readme_e txt Readme File English version Readme_j txt Readme Flle Japanese version Document User s manual is included English and Japanease version FOUSB FoUSB Installer is included English and Japanese common version USB Drivers USB Driver is included English and Japanese common version KD KD30 KD30 Installer is included English and Japanese version KD3083 KD3083 Installer is included English and Japanses version NC NC30WA NC30WA C Compiler is included English and Japanese version Note NC308WA NC308WA C Compiler is included English and Japanese version Note Note Entry version 1 6 System Requirements In addition to the products listed above you must have the following equipment before you can use the USB Flash Writer 1 Host Computer PC 2 Target Board 2 Product Specifications 2 Product Specifications 2 1 FOUSB Flash over USB FoUSB is the software that allows you to operate on M16C M32C R8C or 740 microcomputers with built in flash memory from a Windows version host computer Windows 98SE or later 2 2 KD30 KD3083 The KD included with the package is the debug so
64. ownload click the Go button on the KD Main screen to execute a program After this the program is executed 2 KD30 C SAMPLES SKPTest SKPTest x30 File Edit View Environment Debug Option BasicWindows Optionalwindows Help a Program Window ncrtO_ skptest a30 681 66164 66165 belr 66166 66167 belr 66168 belr enable CM16 17 Xin sel No div woe 3 enable clock monitorin bset 6 8Ch bset 7 8Ch btst 3 DCH jz ENABLE_XIN bset 3 87h nop btst 3 CH dz ENABLE_XIN CONTINUE INIT Z mov bh 66h 64h set pro ww enable enable check f imp if enable H 66666661 check f jmp if weer wn wn wn O I MCU STOP Ui Figure 5 9 Program Execution 5 1 5 Program Stop Click the Stop button on the KD Main screen Figure 5 6 C to stop the program which is already executed after this the program is stopped the KD Main screen is as Figure 5 8 5 1 6 Program Step Execution When performing step execution click the Step button Figure 5 6 B on the KD Main screen 5 Using the KD 5 1 7 Software Break Method When executing the software break the software break can be set as the place which has in BRK in Program Window screen The KD Main screen is as Figure 5 10 Zo KD30 C SAMPLES SKPTest SKPT est x30 iof x File Edit View Environment Debug Option BasicWindows OptionalWindows Help L A siaal ARARA a Program Window main AAA KI PA
65. pcoming KD3083 Therefore it is not necessary to set evry time the KD3083 starts 5 Using the KD 4 This KD Main screen appears when the KD was able to communicate normally at startup 29 KD30 File Edit View Environment Debug Option Basicwindows Optionalwindows Help MCU STOP Figure 5 6 KD Main screen 5 Using the KD 5 1 3 Program Download 1 Download a program by File Download in KD Main screen Please note that SKPTest x30 is not included in this product Look in ja SKPTest gt Si al cl Ps mme SKPTest x30 Files of type Absolute Module Files x30 695 abs Cancel Figure 5 7 Program Download 2 When completing the download a program which is downloaded into Program window is indicated See Figure 5 8 Z KD30 C SAMPLES SKPTest SKPT est x30 iof x File Edit View Environment Debug Option Basicwindows Optionalwindows Help SE ee IR E Program Window ncrt0_skptest a30 3 enable 6 6h 3 CM16 17 H Bh 3 Xin sel belr 6 07h 3 No div belr 87h 3 3 enable clock monitoring bset H 8Ch 3 enable bset 2 BCh 3 enable btst 3 CH 3 check f jz ENABLE_XIN 3 jmp if bset 3 07h 3 enable nop btst 3 CH 3 check f jz ENABLE_XIN 3 jmp if CONTINUE INIT mov bh 66h 64h 3 set pro of MCU STOP A Figure 5 8 Program window 5 Using the KD 5 1 4 Program Execution When completing d
66. pe HIF3FC 10PA 2 54DSA P64 CTS1 RTS1 CT50 CLKS1 30pF 10 Pin Connector assign PRS RXDI Gate 10MHz P67 TxD1 30pF P65 CLKL 5k P85 NMI User Reset Signal 5k Example Connection for M16C 62P 6N M306N4FC M306N4FG M306N5FC only oE Vee USB Monitor Board co Pin No FLAT Cable Connection Connector Type HIF3FC 10PA 2 54DSA 10 Pin Connector assign Signal Vec 0 1uF e lie BUSY scLK Hr rep Z r CE EPM 21S RESET PL s TxD E 95 5k P64 CTS1 RTS1 CTS0 CLKS1 P66 RxD1 Xin P55 HOLD 30pF gt 10MHz P67 TxDL P65 CLK1 P50 WRUWR User Reset Signal P85 NMI 30pF 81 7 Appendix Example Connection for M16C 26 26A 28 29 1 Note It is necessary to connect the CE pin or the EPM RP pin and the P1_6 pin The CE pin is connected in this Target USB Monitor Board FLAT Cable Connection Connector Type HIF3FC 10PA 2 54DSA 10 Pin Connector assign Signal GND RESET BUSY RxD RESET TxD Oo Po roro Fo 5k 0 1uF 0 1uF 5k P64 CTS1 RTS1 CTSO CLKS1 P66 RxD1 P85 NMI P67TxD1 P65 CLK1 AM User Reset Signal P86
67. ple Connection for 38C2 7 Appendix Connector Type HIF3FC 10PA 4DSA 10 Pin Connector assign ve 7 a Sax ese Save BUSY USB Monitor Board a 2 len Jee SCLK o a fe CO 7 K a EPM 0 vm Er RESET KA CNVss ae TD FLAT Cable Connection Va Te wT 15pF e Co am 15pF Veo 5 1k User Reset Signal Vas 5 1k AVss P3s RxDa LED P3V ScLKi LED P2 Tx LED P30 5RDY2 LE D Note When the flash mode control pins are used for usexpplication circuit Refer to the 38C2 group A version datasheet for operation details 86 7 Appendix 7 1 4 Power Source Supply Selector Specifications of the Power Source Supply Selector S1 Power Mode are shown in Table 7 1 Table 7 1 Jumper Settings Switch No Default State Function Selects the power supply for the Target MCU USB BUSPWRD USB The power is supplied from the USB Monitor Board BUSPWRD TARGET TRGTPWRD The power is supplied from the Target Board Note The USB Monitor Board supplies a 5 V power If a 3 3 V power supply is needed choose to supply the power from the Target Board 7 1 5 LED Status Indicators The LED status indicators on the USB Monitor Board are listed in the table below Function STOP Red When steadily on t
68. pt is generated a monitor program is operated Step execution has step over and return 4 Dump When using dump a User Program execution is stopped temporarily and the data of the area currently opened in the dump window is transferred A monitor program is used for a register regarding a clock therefore these registers may be the values which the user doesn t set up 5 Using the KD 5 RAM monitor When using RAM monitor a User Program execution is stopped temporarily 6 Register reference When using register reference a User Program execution is stopped temporarily and the data of CPU register and SFR is transferred 7 User Program stop A User Program stops a monitor program operates and it waits for next command 5 5 3 The difference from an actual CPU operation 1 Real time When opening a RAM monitor window a User Program execution is stopped temporarily RAM is read out and the communication is performed Since a User Program is stopped User Program execution time is prolonged 2 Reset vector table A reset vector is rewritten at the routine address which is used for a monitor program therefore when referring this area by dump the value is differenet from the value which a user sets 3 Interrupt Interrupts of Address Match interrupt and Single Step interrupt and BRK instruction interrupt and DBC interrupt are used by a monitor program therefore do not use these interrupts in a User Program 4 Values after reset
69. se pins Related section 5 4 Peripheral Function Related Limitations 1 b SFR UART association Do not modify registers associated with UARTi including the port register and port direction register allocated to the Serial I O on a User Program When modifying ports other than the serial port modify it with the read modify write instruction BSET BCLR etc Related section 5 2 2 A limitation item about the C language 1 a c RAM Do not use a Monitor Program RAM on a User Program The Monitor Program RAM is allocated from the lowest order address in RAM which the Target MCU has However there is no Monitor Program RAM since R8C Tiny has special debug RAM Related section 5 3 Memory Map Limitations d Flash ROM Excluding Fixed Vector Table Do not overlap a User Program with a Monitor Program ROM When the User Program overlaps with the Monitor Program the KD30 KD3083 indicate an error Error 16256 The specified area includes the debugging monitor memory area Related section 5 2 2 A limitation item about the C language 1 c 5 3 Memory Map Limitations 6 Troubleshooting e Interrupt Interrupts shown below are the resources of the Monitor Program Do not use these interrupts Also some microcomputers do not support the DBC interrupt Note In microcomputers which do not support the DBC interrupt ex M16C 62A group the UARTI receive interrupt is used Therefore when using relocati
70. set treatment after reset this program will start The interrupt enable flag is cleared and communication is disabled after the LDINTB instruction Therefore execute the interrupt enable setting immediately after the LDINTB instruction gt Applicable MCUs M16C 10 M16C 1N M16C 62A M M16C 6N M306NAFG M306NABFC only M16C 24 M3062GF8N M16C 80 c Variable Vector process INTERRUPT VECTOR ADDRESS definition The initial setting of the relocatable vector table variable vector table will cause the program to overlap with the monitor memory area Set the address so that it does not overlap with the memory area gt Applicable MCUs All MCUs except R8C Tiny 2 The change point of sect30 inc a UARTI receive interrupt vector address setting The user must set the UARTI receive interrupt address for communication between the monitor program and the debugger Set the interrupts as indicated below applicable MCUs gt Applicable MCUs UART1 receive interrupt FF900h M16C 24 M16C 62A M M3062GF8N M16C 6N M306NAFG M306NBFC only UARTO receive interrupt FF900h M16C 10 M16C 1N UART1 receive interrupt FFF900h M16C 80 5 Using the KD 5 2 3 Limitations on Memory Extension When using memory extension make sure the power source supply selector on the USB Monitor Board is set to the TARGET side so that the power for the Target MCU will be supplied from the Target Board Memory extension cannot be used when the selector is s
71. sing the KD 5 2 KD Limitations 5 2 1 Limitations on Special Page Vector A Monitor Program uses several Special Page Vectors Therefore the Special page Vector which can be used in the User Program is limited as Special Page Vector Number shown in the following table When updating the version of the Monitor Program or Firmware the Special Page Vector which can be used in the User Program may be modified Table 5 1 Specail Page Vector Limitations Group Available Special Page Vector Number M16C 10 127 to 24 M16C 1N 238 to 24 M16C 24 234 to 24 M16C 26 205 to 24 M16C 26A 28 29 199 to 24 M16C 62A M 234 to 24 M16C 6N 6NA 6NB M16C 62P 200 to 24 M16C 6N 6N4 6N5 M16C 62N M3062GF8N 237 to 24 M16C 80 196 to 24 M32C 83 182 to 24 M32C 84 85 86 87 164 to 24 Note The contents in this Table are applied to the following KD30 KD3083 KD30 Ver 4 10 Release 1 Firmware version V 8 00 KD3083 Ver 3 30 Release 1 Frimware version V 8 00 5 Using the KD 5 2 2 A limitation item about the C language When using Renesas C compiler It is necessary to change a start up file ncrt0 a30 and sect30 inc 1 The change point of ncrt0 a30 a Initialize standard I O The UARTIi setting is modified in the I O initialization treatment Therefore to ensure that the I O initialization treatment is not called up comment it out gt Applicable MCUs All MCUs b Re
72. tatus indicator is not blinking the firmware of USB MCU is erased or damaged When firmware is erased or damaged FoUSB Flash over USB and KD KD30 KD3083 cannot be used In such a case it is necessary to download firmware compulsorily to USB MCU Please refer to 6 4 FoUSB cannot operate Why in order to download firmware compulsorily to USB MCU A communication error occurred when debugging the program What is the cause of this problem 1 If a communication error occurs when debugging your program initialize the system following the procedure described below This should help you restart debugging 1 Click the lt OK gt button in the error dialog box to close the KD 2 Start up the KD again 3 Download your program 2 Check whether the data OFF900h or OFFF900h is set when transmitting receiving via UARTi in your program 6 Troubleshooting 3 If a communication error occurs frequently when debugging your program check the following When using an interrupt program in which multiple interrupts interrupt from within another interrupt are not enabled gt H the interrupt program takes more than 260 us of processing time set the flag to 1 at the beginning of the interrupt program 6 8 A message Source file cannot be found was output What should do If an error Source file cannot be found occurs check the following 1 Whether the source file and the executable file exist in the same
73. ted by Microsoft but we provide them based on the sufficient examination 9 The following figure is displayed when the USB Driver is already installed in the PC Click the lt OK gt button Driver Install USBMON Driver i USB Monitor driver already installed FoUSB Driver Driver Install G MCU with USB bootmode driver already installed 3 Installing 10 The following figure is displayed when installation of USB Driver is completed Click the lt OK gt button Driver Install Complete Q 11 When the install component Update KD30 Files is chosen FoUSB installer seaches KD30 with a firmware older than the firmware of FOUSB The following figure will be displayed if KD30 is detected If you want to update a firmware click the lt Yes gt button When lt No gt button is clicked the firmware of KD30 is not updated a Flash Over USB Programmer 2 04 Setup Note When the install component Update KD3083 Files is chosen the update check screen is displayed like the above 3 Installing 12 Finally click the lt Finish gt button g Flash O ver USB Programmer 2 04 Setup Bisi E Completing the Flash Over USB Programmer V 2 04 Setup Wizard Flash Over USB Programmer 2 04 has been installed on your computer Click Finish to close this wizard 13 Now you ve finished installing the FoUSB Flash over USB 3 3 2 Method of Uninstallation To uninstall the FoUSB
74. ter M3A 0665 This manual describes how to use the hardware and software products included with USB Flash Writer M3A 0665 To other tools look other tools s manulas 1 Table of Content Table of Content Gontents Of Proguct scesivs c ctet paccuecticieed deaigestebies ete dance vesetansel chutes eleivie ENEE ENEE EENEG Eeer 4 1 1 Contents Of product ce ceeceesetetseseeeseseseseseseseceeseaeeesesseeeecaeaeaeeeseseecaeaeaeseesecesaeaeseseeeeseaeataeeeeneseseeasaneeaeates 4 1 2 Operating Environment 5 1 3 Compatible re Te E 5 1 4 Board Specification EE 7 W e Re EE 8 1 6 System EC 8 Product Gpechflcatone tnta tentten tantn tnn ttnn tnn tte nnant tentanta te nennen ee 9 2 1 FOUSB Flash over USB riisiin anona aiia Ear A A E aE S A N AEE 9 2 2 REN EI EE 9 EC DE 11 B Before MSTA EE 11 3 2 Preparation before installirng scsccccssecsseseeeeeeeesseeesneeesceeeseesseessersseensuesensessseesseesseessaeesneeeseeneseeseeneeetens 11 3 3 FOUSB Flash over USB installing cceesseeseseeseseeeeeeeseseseeeeeeecaeseseseseeeseeasaeseseseeeeacaeaeseeeeesenenaeasaeeeseeas 12 3 3 1 Method of gn GC le EE 12 3 3 2 Method erg ll CHE WEE 17 3 4 Recognition of USB Monitor Board AEN 18 3 4 1 Recognition of USB Monitor Board 1 for USBMON Driver 18 3 4 2 Recognition of USB Monitor Board 2 for FOUSB Driver 20 3 4 3 Other NOtGS EN 23 3 5 KD30 KD3083 intallling AEN 24 3 921 We ET EE 24 3 5 2 Uninstalling the R
75. that has passed Windows Logo testing Continue Anyway 1 Note Microsoft has advocated authentication of the USB drivers to the USB vendors in the Microsoft Windows XP and Windows based operating systems released after Microsoft Windows XP This is aimed at elimination of illegal drivers and improvement of host computer PC Renesas USB Drivers are not authenticated by Microsoft but we provide them based on the sufficient examination 3 Installing 6 Click the lt Finish gt button Windows system recognizes USB Monitor Board for USBMON Driver Found New Hardware Wizard Completing the Found New Hardware Wizard The wizard has finished installing the software for e Renesas FoUSB ICD Click Finish to close the wizard Recognition of USB Monitor Board for USBMON Driver is completion 3 4 2 Recognition of USB Monitor Board 2 for FoUSB Driver 1 Remove the cover of USB Monitor Board and make a USB Monitor Board Board the following setup before connecting USB Monitor Board to your host computer PC If a setup is completed attach a cover in a USB Monitor Board Board Power Source Supply Selector S1 Power Mode USB side MCU Mode Pin JP1 MCU Mode Shorted Figure 3 3 Setup of USB Monitor Board Board 3 Installing 2 Connect the USB Monitor Board included with the package to the USB port of PC The Power indicator D1 Power of USB Monitor Board lights PC with Windows 98SE ME 200
76. the User Program and contes of the User program and asseble codes are not matched Bank Address F00000h j i A Emulation Memory The Emulation Memory overlaps F10000h FFF900h FFFEFFh Fixed Vector Table FFFFFFh E Program Window test1 a30 Mi Ei View E Source Bem W Dis Line 66607 66668 DD 66616 66611 66612 60613 60614 66615 46616 66617 46618 46619 66626 ERD PRH ERR ISISIGIE ERR 5 Using the KD b Then an example to which the Emulation Memory does not overlap the User Program is shown In this example the User Program is allocated from F00000h and the Emulation Memory is allocated from E00000h set EO to the bank address Since the Emulation Memory does not overlap the User Program contents of the User Program and assemble codes are matched Bank Address E00000h x Emulation Memory The Emulation Memory does not E10000h ES overlap the user program F00000h User Area Fixed Vector Table FFF900h FFFEFFh FFFFFFh Si Program Window test1 a30 ioj E View E Source By Mix W Dis Line 66067 66068 66089 66616 66611 66612 66613 66614 66615 66616 66617 66618 66619 66626 PR PR ERR PRppp3 PR Note The setting contents on the Emem screen will be continued to the u
77. uage of installer Installer Language x Please select the language of the installer 3 Click the lt Next gt button EN Flash Over USB Programmer 2 04 Setup Welcome to the Flash Over USB Programmer V 2 04 Setup Wizard This wizard will guide you through the installation of Flash Over USB Programmer V 2 04 It is recommended that you close all other applications before starting Setup This will make it possible to update relevant system files without having to reboot your computer Click Next to continue 4 Only when you agree click the lt l Agree gt button ER Flash Over USB Programmer 2 04 Setup License Agreement RE NES eee terms before installing Flash Over USB Everywhere you imagine Press Page Down to see the rest of the agreement If you accept the terms of the agreement click Agree to continue You must accept the agreement to install Flash Over USB Programmer 2 04 Nullsoft rstalllSpstern yZi0 lt Back Cancel 3 Installing 5 Choose the component which you want to install and click the lt Next gt button aR Flash Over USB Programmer V 304 Setup Pije Ea tENESAS Everywhere you imagine Choose Components Choose which features of Flash Over USB Programmer 2 04 you want to install Check the components you want to install and uncheck the components you don t want to install Click Next to continue
78. wn in Figure 7 6 appears So click the lt Finish gt button Add New Hardware Wizard a A E Figure 7 6 FoUSB Driver 2 9 Installation of a FoUSB Driver and recognition fo USB Monitor Board have been finished Separate USB Monitor Board from your host computer PC 93 7 Appendix 10 Remove the cover of USB Monitor Board and make a USB Monitor Board Board the following setup If a setup is completed attach a cover in a USB Monitor Board Board MCU Mode Pin JP1 MCU Mode Open 94 7 Appendix 7 3 Referencing Electronic Manuals Electronic Manuals of the Product are in the form of files in PDF portable document format To reference them the user needs Adobe Acrobat Reader The user can download Adobe Acrobat Reader from the home page of Adobe Systems Incorporated For latest information as to Adobe Acrobat Reader go to the following URLs http www adobe co jp http www adobe com 7 4 Product Information The latest information about this product is carried here M16C Family http Awww renesas com en m16c 740 Family http Awww renesas com en 740 95 90 y Mac WTH903030W Jagun y Euro ev azis En

Renesas M16C FAMILY User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents