APPLICATION NOTE REU05B0059-0100Z March 2004 Page 1 of 7 M16C Target Setup for the FoUSB Programmer 1.0 Abstract The ICD (In-Circuit Debugger), or USB-Monitor, is a low cost, compact interface that has two functions for Renesas’ M16C Flash microcontrollers: 1) an in-system programmer with FoUSB (Flash-over-USBTM) Flash Programmer, and 2) an in-circuit debugger tool with KD30 Debugger. The following article introduces, and shows examples of, how to configure the target hardware with Renesas’ M16C Flash MCU to interface with the ICD for in-system programming. 2.0 Introduction When used with the FoUSB Flash Programmer, the ICD provides an in-system programming interface to the target Renesas M16C Flash MCU. In addition, when used with KD30, it also provides an easy-to-use in-circuit debugging environment during application development. The ICD, by taking advantage of Universal Serial Bus (USB), provides plug-and-play connectivity and fast data transfers between the computer and the M16C target board. The ICD is powered by Renesas’ M37641 full speed USB Flash MCU, which also makes it upgradeable to support future Renesas M16C MCUs. Powering the ICD is user selectable: USB Bus powered or Target powered. When used in bus-powered mode, the USB bus supplies power to the ICD and target board. When in target-powered mode, USB bus power is disconnected and the ICD sources power from the M16C target board. Renesas recommends to use Target Power Mode and NOT USB Bus Power Mode when connected to non-Renesas SKP target boards. If you plan to use the ICD to supply power to non-SKP boards, please contact Renesas representative for details and assistance. Aside from a standalone kit (RTA-FoUSB-MON), the ICD comes included with the following Renesas Starter Kits: • MSV30102-SKP • MSV30262-SKP • MSV30245-SKP • M16C System Evaluation Kit • SKP16C26 • SKP16C28 • SKP16C62P • SKP8CMiniM16CTarget Setup for the FoUSB Programmer REU05B0059-0101Z March 2004 Page 2 of 7 PC with Windows™ 98,2000, Me, or XP andavailable USB port Figure 1 ICD System Connectivity A picture of the ICD with key components indicated is shown below. Mini-USBConnector2Target or (USB) BusPowered Switch1LED’s:Red – Target StoppedGreen – Target RunningYellow – USB-Monitor StatusRed – Power10-pin PolarizedConnector to M16CTarget Board2 Figure 2 ICD (or USB-Monitor) Note: 1. The USB Bus Power Mode was designed to supply power to Renesas SKP boards. If non-Renesas SKP boards (i.e. customer developed M16C board) are used as target boards, use the ICD in Target Power mode. Contact your Renesas representative if you plan to use the ICD in Bus Power mode to supply power to your non-SKP target board. 2. The ICD ships with a 6’ mini USB cable to connect to your PC and a 6” 10-pin flat ribbon target cable to connect to the M16C target board.M16CTarget Setup for the FoUSB Programmer REU05B0059-0101Z March 2004 Page 3 of 7 3. The ICD requires 5V for re-programming if a new MCU file (MMI) needs to be downloaded to the ICD (i.e. when the target MCU selected does not match the MCU file on the ICD). To accomplish this, disconnect the ICD from the target, set to Bus Power Mode, and then download new MCU file. After MCU file has been downloaded, switch back to Target Power Mode. 3.0 Hardware Connectivity for In-System Programming This section describes the hardware connections to the ICD for in-system programming purposes. Examples for different M16C MCU’s are shown at the end of the section. The ICD connects to an M16C target board through a polarized, .100” (2.54mm), 10-pin connection using a flat ribbon cable. It communicates with the M16C MCU using the boot UART/SIO in a clocked SIO configuration. The signals used and how these signals are assigned is described below. Figure 3 Target Board 10-Pin Header/Connector Signal Assignment Note: All target interface lines are in high impedance state until instructed to do otherwise by the FoUSB Programmer application. 3.1 Vcc – Power Supply Pin This provides the common connection point for power between ICD and the target board. This must be connected to the target board’s Vcc line/plane. In Target Power mode, the ICD requires at least 3.3V (5.0V max) and 45mA to operate properly. 3.2 Busy – Target MCU SIO Busy Signal This line indicates whether the target is busy (and cannot receive data) or not. This must be connected to the target MCU’s boot UART/SIO BUSY (CTS/RTS) 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. 3.3 SCLK – Target MCU Serial Clock Signal This clock is used for synchronous serial communication between ICD and target board. This must be connected to the target MCU’s boot UART/SIO SCLK pin. 13579246810VccSCLKCEGNDCNVssBUSYRXDEPMRESETTXDM16CTarget Setup for the FoUSB Programmer REU05B0059-0101Z March 2004 Page 4 of 7 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. 3.4 RXD –Target MCU Receive Data Input Signal (ICD Transmit Data Output Signal) 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. 3.5 CE Pin This pin is used to enter boot mode for programming of the target M16C MCU. Not all M16C MCU’s have a CE pin. If a CE pin exists on the target MCU, it should be connected to this pin (refer to serial mode flash programming in the target MCU’s datasheet). If not, leave pin unconnected. If the target MCU’s CE pin is used as input, isolate the driving circuit from the header connection with a 1Kohm resistor. If to be left unconnected (if users decides to), care must be taken to ensure that the target MCU’s CE pin has a high signal level using a pull-up resistor during any programming operations. 3.6 EPM Pin (in Target Power Mode) In Target Power Mode, the pin is used to control target MCU’s EPM pin (if it exists on the target MCU). EPM pin is used during programming of the target MCU. If this pin exists on the target MCU, it should be connected to the header (refer to serial mode flash programming of the target MCU’s datasheet). If not, leave unconnected. If the target MCU’s EPM pin is used as input,
View Full Document
Unlocking...