RTA-FOUSB-MON Renesas Electronics America, RTA-FOUSB-MON Datasheet
RTA-FOUSB-MON
Specifications of RTA-FOUSB-MON
Related parts for RTA-FOUSB-MON
RTA-FOUSB-MON Summary of contents
Page 1
... RTA-FOUSB-MON User’s Manual Rev 2.2 Applications Engineering ! "! " Jan 2005 ...
Page 2
... Appendix D. Reference Manuals..………………………………………………………...26 Appendix E. Board Schematic & BOM……..…………………………………………….27 RTA-FOUSB-MON User’s Manual Rev 2.2 Table of Contents ...
Page 3
... Mini USB Connector 1. Kit Overview The RTA-FoUSB-MON (ICD low cost compact device that can function as an In-Circuit Debugger (ICD) tool FoUSB (Flash-over-USB (MCU). KD30 and KD3083 are the software applications for debugging M16C and M32C firmware and FoUSB Programmer is the software application for programming the Renesas M16C Flash MCU’s. ...
Page 4
... Before using the ICD the device drivers need to be installed. There are two USB drivers for Flash-Over-USB devices. They are: USBMON.SYS This is the USB driver that is used for the RTA-FoUSB-MON hardware. Note: In Japan it is called the USB Flash Writer (M3A-0665). FOUSB.SYS This is the USB driver that is used for direct-connected MCU+USB devices operating in boot-mode ...
Page 5
... Windows will then begin installing the USB driver. Another screen may appear stating that this driver has not been XP certified by Microsoft because we did not participate in Microsoft XP driver certification. Click the “Continue Anyway” button. Your driver is now installed. Click Finish to close the wizard. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 6
... To close KD30, click on ‘File’ menu and select ‘Exit’; or, click on the close button on the upper right corner of the Window. Do not unplug or detach the ICD from your PC without closing KD30 first. Detaching the ICD while KD30 is still up may cause problems when you try to use KD30 again. RTA-FOUSB-MON User’s Manual Rev 2.2 DBC Support Breakpoints ...
Page 7
... NOTE: 1. For additional descriptions and operations, please click on Help button of the FoUSB Programmer. 2. Renesas continues to update the application and the version number may be different from what is on this document. RTA-FOUSB-MON User’s Manual Rev 2 Programmer MCU Device Select Button Fig. 5.1 FoUSB Programmer Screen ...
Page 8
... For these two ID’s, the application automatically unlocks the device. The Command button is used to send boot commands to the target MCU (when in boot mode). This button is used to debug monitor firmware and by device programmer manufacturers. RTA-FOUSB-MON User’s Manual Rev 2.2 with Target Connected Applications Engineering ...
Page 9
... Serial Boot Code: Flash boot code on the target MCU. The Settings button allows the user to configure the FoUSB Programmer for various settings and operational modes including Multi-programming and Automated programming. RTA-FOUSB-MON User’s Manual Rev 2.2 Fig. 5.3 MCU Selection Screen ...
Page 10
... This is the ICD SIO transmit data output. This must be connected to the target MCU’s boot UART/SIO receive data input (RXD) pin. This pin may be used for other applications as long as the user ensures that the ICD can drive the pin to valid levels with 5mA current. RTA-FOUSB-MON User’s Manual Rev 2.2 TXD 10 9 ...
Page 11
... This is the ICD SIO receive data input. This must be connected to the target M16C MCU’s boot UART/SIO transmit data output (TXD) pin. This pin may be used for other applications as long as the user ensures that the ICD can drive the pin to valid levels with 5mA current. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 12
... CLK 3 P6_5/CLK1 (SCLK) RxD 4 P6_6/RxD1 (RxD P8_6/XCout (CE) EPM 6 GND 7 Vss !RESET 8 !RESET CNVss 9 CNVss TxD 10 P6_7/TxD1 (TxD) 47K (nominal) RTA-FOUSB-MON User’s Manual Rev 2.2 10-Pin 47K Header Vcc (nominal) M16C/29 Vcc 1 BUSY 2 CLK 3 RxD 4 CE** 5 EPM 6 GND 7 !RESET 8 CNVss 9 TxD ...
Page 13
... GND 7 !RESET 8 CNVss 9 TxD 10 47K (nominal) NOTE: If you cannot find your M16C Flash MCU in the examples shown, please contact Renesas representative for assistance. RTA-FOUSB-MON User’s Manual Rev 2.2 User UART/ 10-Pin Header Chip Mode Vcc Vcc 1 BUSY 2 CLK 3 RxD 4 CE ...
Page 14
... This is the ICD SIO transmit data output. This must be connected to the target MCU’s boot UART/SIO receive data input (RXD) pin. This pin cannot be used while the Kernel program is running (during in-circuit debug operations). RTA-FOUSB-MON User’s Manual Rev 2.2 TXD 10 ...
Page 15
... ICD before running the user program. Without the pull-down resistor, the target MCU will only run the Kernel program program. This pin cannot be used while the Kernel program is running (during in-circuit debug operations). RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering ...
Page 16
... Vcc 1 BUSY 2 CLK 3 RxD EPM 6 GND 7 !RESET 8 CNVss 9 TxD 10 47K 47K (nominal) (nominal) RTA-FOUSB-MON User’s Manual Rev 2.2 10-Pin M16C/26, M16C/28, Header Vcc M16C/29 Vcc Vcc 1 P6_4/RTS1 (Busy) BUSY 2 P6_5/CLK1 (SCLK) CLK 3 P6_6/RxD1 (RxD) RxD 4 P8_6/XCout (CE) CE** 5 EPM 6 Vss GND ...
Page 17
... CNVss 9 TxD 10 47K 47K (nominal) (nominal) NOTE: If you cannot find your M16C Flash MCU in the examples shown, please contact Renesas representative for assistance. RTA-FOUSB-MON User’s Manual Rev 2.2 10-Pin Header Memory Mode Vcc* Vcc 1 P6_4/RTS1 (Busy) BUSY 2 P6_5/CLK1 (SCLK) CLK ...
Page 18
... NOTE: For MCU’s that do NOT have DBC interrupts, always ensure that the global interrupt is enabled in the startup files. Communications between ICD and the kernel program will fail when the global RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 19
... Ensure that the boot SIO/UART vector is properly set-up to point to FF900H for those M16C MCU’s that do NOT support/have DBC interrupt. • Do NOT attempt to debug watchdog, WAIT mode, or STOP mode. • Do NOT execute a ‘STEP’ operation after a write to PRC2 SFR. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 20
... Bus Power (S1) b. MCU Mode (JP1) c. Debug (JP3) Power Configuration Current Requirements Board Size RTA-FOUSB-MON User’s Manual Rev 2.2 Description Renesas M37641F8HP (8-bit USB Flash MCU) PC host and target connectivity. Full speed USB connection and USB 2.0 compliant. Primary connection to debug PC. ...
Page 21
... JP9’s (UART1) RXD line to be able to run user code. The monitor program polls the RXD line for the presence of the ICD before running the user program. Without the pull-down resistor, the M16C/62 MCU will only run the monitor program. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering ...
Page 22
... USB Drivers folder, i.e. fousb.inf, fousb.sys (driver files to run FoUSB.exe), usbmon.inf, and usbmon.sys (driver files to run KD30). The C:\MTOOL\RTA-FOUSB-MON folder contains all latest documentation about the ICD from Quick Start Guide to schematics. The development tools can be found under tools folder from the CD root ...
Page 23
... Delete the driver ‘usbmon.sys’ from ‘\WINNT\SYSTEM32\DRIVERS\ folder in Windows 2000 or \WINDOWS\SYSTEM32\DRIVERS folder in Windows 98. 3. Plug in ICD + target and try installing the driver as written above and use the driver from the C:\MTOOL\FOUSB\USB Drivers. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 24
... Task Bar and select ‘Task Manager’; for Windows 98 XP, press CTRL-ALT-DEL and select ‘Task Manager’). Select KD30.exe on the ‘Processes’ list and click on ‘End Process’ to terminate KD30. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 25
... ICD and target board. Please review the connection and check your circuit. Refer to section 6 in this manual, ‘Target Hardware Connectivity for In-System Programming’. (4) The target MCU maybe damaged. Try a different target board and MCU. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering FoUSB ...
Page 26
... If you plug the ICD into the PC, the FoUSB Programmer should show the target MCU device name you selected earlier. If for some reason, it still does not come up, your ICD may have been damaged. Please contact your Renesas representative to get a replacement. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...
Page 27
... Firmware Requirements for In-Circuit Debugger Support NOTE: The RTA-FOUSB-MON installer will copy all these manuals during installation. They can be accessed using the Document Descriptions file by clicking on the Start > Programs > Renesas-Tools > RTA- FOUSB-MON > Document Descriptions. RTA-FOUSB-MON User’s Manual Rev 2.2 Description Document that will help you get started on using the ICD ...
Page 28
... Appendix E. Board Schematic & BOM The circuit board schematic and BOM are available as separate documents, RTA-FoUSB-MON_Schematic_RevX.pdf and RTA-FoUSB-MON_Board_BOM_RevX.pdf respectively. RTA-FOUSB-MON User’s Manual Rev 2 Applications Engineering Jan 2005 ...