RTA-FOUSB-MON Renesas Electronics America, RTA-FOUSB-MON Datasheet - Page 19

• Manufacturer Part Number: RTA-FOUSB-MON
• Description: ON CHIP DEBUG EMULATOR
• Manufacturer: Renesas Electronics America
• Type: FLASHr

Specifications of RTA-FOUSB-MON

• Contents: USB Compact Flash Programmer, USB Cable, CD-ROM and User Manual
• For Use With/related Products: M16C Family and 740 Family
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

interrupt is not set or disabled for long periods (>1s). This is the primary cause of communication
errors while using the KD30 Debugger.
The following list includes MCUs with DBC support:
The kernel program uses the serial port associated with the boot mode of the MCU for communication
with the ICD. Connect the SCLK, TxD, RxD signals from the 10-pin header to this serial port. For
example, in the case of M30624 MCU, the monitor uses UART1 as the boot UART.
For MCU’s that do NOT support DBC, ensure that the interrupt vector for the boot UART is set to FF900h.
Avoid byte-writes to the (boot UART/SIO) port, including direction register, associated with the SIO when
the other half of the port is used as General Purpose I/O (GPIO) pins. Byte-writes to the port and direction
register may prevent the monitor program from functioning properly. Use read-modify-write instructions
instead.
If possible, avoid using this serial port for other applications in the firmware when the ICD will be used for
development.
Please be aware that while the kernel 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 kernel program is in its “RUN”ning state, there is no overhead on the application code, UNLESS
a RAM monitor window is open in KD30. This window requires periodic communication with the target
MCU, which suspends normal application operation while servicing the request (approximately 2000
BCLK cycles for each 16 bytes of data displayed in the window are used per window update). The user
must determine whether or not, this behavior is acceptable.
RTA-FOUSB-MON User’s Manual Rev 2.2
•
•
•
•
•
•
•
- M16C/26, M16C/28, M16C/29
- M16C/62P, M16C/6N4, M16C/6N5
- M32C/83, M32C/85
d. Peripherals
e. Real-Time Capability
f.
Ensure that global interrupt is set in the startup file and not disabled for long periods (>1s).
Do NOT use the RAM or ROM memory as specified in sections 8.a and 8.b.
Avoid byte-writes to the port and direction register to avoid interfering with monitor operation
associated with the boot SIO/UART. Use bit manipulations.
Do NOT change boot UART configuration.
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.
Software Summary and Precautions
18 / 27
Applications Engineering
Jan 2005