 |
|
|
RENESAS TOOL NEWS on December 16, 2006: 061216/tn6
| A Note on Using Debuggers
for the SuperH RISC engine,
M16C, H8SX, H8S, H8, and 740 MCU Families |
Please take note of the following problem in using simulator and
emulator debuggers for the SuperH RISC engine, M16C, H8SX, H8S, H8, and
740 MCU families:
- With updating debuggers using the AutoUpdate Utility
1. Products Concerned
(1) SuperH RISC engine simulator debugger V.9.06.00
(2) M32C PC7501 emulator debugger V.1.02 Release 00
(3) M32C PC4701 emulator debugger V.1.02 Release 00
(4) M32C compact emulator debugger V.1.02 Release 00
(5) M32C FoUSB/UART debugger V.1.02 Release 00
(6) M32C simulator debugger V.1.02 Release 00
(7) M16C R8C PC7501 emulator debugger V.1.02 Release 00
(8) M16C PC4701 emulator debugger V.1.02 Release 00
(9) M16C R8C compact emulator debugger V.1.02 Release 00
(10) M16C R8C FoUSB/UART debugger V.1.02 Release 00
(11) M16C R8C simulator debugger V.1.02 Release 00
(12) 740 PC4701 emulator debugger V.1.02 Release 00
(13) 740 compact emulator debugger V.1.02 Release 00
(14) 740 simulator debugger V.1.02 Release 00
(15) Simulator debugger for the H8SX, H8S, and H8 families V.5.05.00
(16) H8/300H Tiny compact emulator debugger V.1.01 Release 00
2. Description
After the update to any of the above products concerned has been made
using the AutoUpdate Utility, the name of the updated product may be
displayed in the Select Updates dialog box (which tells you new
updaters are available) if the AutoUpdate Utility is re-invoked.
At the same time, symbol ! (which also tells you new updaters
available) will stay on the icon of the AutoUpdate Utility appearing
on Windows' system tray.
In this case, the version number of the product before updated and
the one after updated are both provided in the Select Applications
dialog box of the wizard of AutoUpdate Utility.
3. Workaround
For the product two version numbers of which are provided in the
Select Applications dialog box, uncheck the check box for the
previous version number.
4. Schedule of Fixing the Problem
We plan to fix this problem in the next release of each debugger.
|
|
