Renesas HEW Target Manuel D’Utilisation
HTS Demo Kit V1.0
10/ 20
December 2007
7.0 System Operation & Limitations
The HTS Demo Kit board provides sophisticated debugging features at a low cost via its on-board in-
circuit debugging and programming circuitry (ICD).
For M16C boards without on-board debugging/programming circuitry, Renesas offers the functionally
equivalent, standalone E8 in-circuit debugger/programmer. You can find detailed information on the E8
and its functionality in the E8 Emulator User’s Manual, which you can view via the HEW Manual Navigator.
The HTS Demo Kit board does have some limitations when used with the HEW software debugger and
the board’s ICD circuit. Section 6.1 introduces the kernel (ROM monitor) program and its purpose. The
limitations when this kernel is running with the user program are listed in Table 7-1.
circuit debugging and programming circuitry (ICD).
For M16C boards without on-board debugging/programming circuitry, Renesas offers the functionally
equivalent, standalone E8 in-circuit debugger/programmer. You can find detailed information on the E8
and its functionality in the E8 Emulator User’s Manual, which you can view via the HEW Manual Navigator.
The HTS Demo Kit board does have some limitations when used with the HEW software debugger and
the board’s ICD circuit. Section 6.1 introduces the kernel (ROM monitor) program and its purpose. The
limitations when this kernel is running with the user program are listed in Table 7-1.
Table 7-1: System Limitations when Debugging
Item
Please Refer To
User Limitations
7.6 Stop or Wait Mode Limitations
The kernel cannot be run in STOP or WAIT modes. Do not use these
modes when debugging your program
The kernel cannot be run in STOP or WAIT modes. Do not use these
modes when debugging your program
Debugger Limitations
7.7 User Program’s Real-Time Capability
7.1. Kernel (ROM Monitor) Introduction
During debug, a small program called a kernel is uploaded to the M16C/26A (M30260F8AGP) MCU. The
kernel communicates with HEW through the ICD portion of the HTS Demo Kit board regarding MCU
status during user code debugging operations.
There are no special steps required in the user program to make use of the ICD portion. The operation of
the kernel is transparent to the user, but there are some limitations. These are discussed from section 7.2
onward.
After starting a HEW debug session, the ICD uploads the kernel to the M16C/26A if it does not already
exist (e.g. on a blank device or a device that was programmed with the Flash Development Toolkit
Programmer). After downloading the kernel, the M16C/26A is ready to download user code.
Connecting the HTS Demo Kit board without starting HEW will not affect the signal lines connected
between the ICD MCU (HD64F2215RUBR) and the M16C/26A; the ICD MCU keeps the signal lines in
high-impedance state. The ICD MCU only drives the pins after HEW or the Flash Development Toolkit
software attempts to connect.
After completing program debug and verification with HEW, you can create an image of your code in Intel
(.hex) or Motorola (.mot) file formats. This image can be programmed into the M16C/26A using the Flash
Development Toolkit programming software. This procedure erases the kernel and leaves only the user
program.
kernel communicates with HEW through the ICD portion of the HTS Demo Kit board regarding MCU
status during user code debugging operations.
There are no special steps required in the user program to make use of the ICD portion. The operation of
the kernel is transparent to the user, but there are some limitations. These are discussed from section 7.2
onward.
After starting a HEW debug session, the ICD uploads the kernel to the M16C/26A if it does not already
exist (e.g. on a blank device or a device that was programmed with the Flash Development Toolkit
Programmer). After downloading the kernel, the M16C/26A is ready to download user code.
Connecting the HTS Demo Kit board without starting HEW will not affect the signal lines connected
between the ICD MCU (HD64F2215RUBR) and the M16C/26A; the ICD MCU keeps the signal lines in
high-impedance state. The ICD MCU only drives the pins after HEW or the Flash Development Toolkit
software attempts to connect.
After completing program debug and verification with HEW, you can create an image of your code in Intel
(.hex) or Motorola (.mot) file formats. This image can be programmed into the M16C/26A using the Flash
Development Toolkit programming software. This procedure erases the kernel and leaves only the user
program.
7.2. Pin and Peripheral Limitations
SIO/UART1 pins are used for communication between the M16C/26A kernel on the HTS Demo Kit board
and the board’s ICD MCU (HD64F2215RUBR). Do not connect these pins to any other circuit, as
SIO/UART1 cannot be used in the user program while using the Debugger.
and the board’s ICD MCU (HD64F2215RUBR). Do not connect these pins to any other circuit, as
SIO/UART1 cannot be used in the user program while using the Debugger.