 |
|
|
RENESAS TOOL NEWS on October 16, 2005: RSO-DebuggerPackage_2-051016D
A Note on Using the Debuggers
for the M16C/60, /30, /Tiny, /20, /10,
and R8C/Tiny Series of MCUs
--On Reading Object Module Files Created by TASKING tool chains Manufactured by Altium Limited-- |
Please take note of the following problem in using the debugger for the M16C/60, /30, /Tiny, /20, /10 and R8C/Tiny series of MCUs:
- On Reading Object Module Files Created by TASKING tool chains Manufactured by Altium Limited
- Products and Versions Concerned
| (1) |
|
M16C R8C PC7501 emulator debugger V.1.00 Release 00 and V.1.01 Release 00, which runs on the High-performance Embedded Workshop |
| (2) |
|
M16C PC4701 emulator debugger V.1.00 Release 00 and V.1.01 Release 00, which runs on the High-performance Embedded Workshop |
| (3) |
|
M16C R8C compact emulator debugger V.1.00 Release 00 and V.1.01 Release 00, which runs on the High-performance Embedded Workshop |
| (4) |
|
M16C R8C simulator debugger V1.00 Release 00, which runs on the High-performance Embedded Workshop |
| (5) |
|
M16C R8C FoUSB/UART debugger V.1.00 Release 00 and V.1.01 Release 00, which runs on the High-performance Embedded Workshop |
| (6) |
|
KD30 FoUSB/UART debugger V.1.00 Release 1 through V.4.10 Release 1, which is used for the M16C/60, /Tiny, /20, /10 and R8C/Tiny series |
- Description
The products concerned cannot correctly read object module files written in the ELF/DWARF format created using TASKING tool chains. So such symptoms may take place that errors arise at loading files into the emulator or some parts of debugging information of the files loaded are missing.
- Workaround
Use any of the TASKING tool chains that can create object module files in the IEEE-695 format and load these files into the emulator.
- Schedule of Fixing the Problem
We are going to improve the products concerned so that they can correctly read object module files in the ELF/DWARF format created using TASKING tool chains.
|
|
