1. When using M3T-PDxx (M3T-PD308, M3T-PD30, M3T-PD79, M3T-PD77, M3T-PD38) with PC4701U/PC4701M, the
emulator serial number must be input during the M3T-PDxx installation. But what happens when I install using a
PC4701U/PC4701M with a different serial number?
2. Can I use the M3T-PDxx bundled in the "Debug Tools" (formerly called "PDxx service pack") for the PC4701U/PC4701M
with any other PC4701 emulator besides PC4701U/PC4701M? (July 22, 2003)
●
I get an error and I can not use the custom commands when I:
Use the OPEN button in the script window to open a *.scr file which is not in the same directory as PDxx.EXE,1.
then execute a custom command, in the script window, which exists in the same directory as PDxx.EXE does.2.
I realize I can execute custom commands by placing the *.scr file in the same directory as the PDxx.EXE, but in this case
having to put both in the same directory is not convenient. (Nov. 19, 1999)
●
I want to refer to the data at address 0x46x and 0x500 from the RAM monitor window, but because the real-time RAM
monitor function specifies that the memory must continually be 1K bytes, I can not refer to both at the same time. Is there any
way to separate the RAM monitor area into sections? (Nov. 19, 1999)
●
In PD79 V.1.10, the setMemoryWord command (MW command) modifies the memory contents of a specified address in
2-byte units. When I use this command to change the memory contents at an even address, the upper 8 bits are not changed.
Yet, if I specify an odd address, I have no problem. (Nov. 19, 1999)
●
Why doesn't PD79 V.1.10 display task names in the TaskTrace window (task names were displayed in PD79 V.1.00)? (Nov.
19, 1999)
●
Top of Page | 79xx Series FAQ Index | FAQ Index
Terms of Use Privacy Policy
(C)2004 Renesas Technology Corp., All Rights Reserved.
Kommentare zu diesen Handbüchern