Tool News
 
 
 

Tool News

Products Info
Downloads
Tools FAQs
MESC TOOL NEWS: MESCT-PD30-980701D

PD30, PD30SIM, PD77, PD77SIM
Precaution

Please take note of the following problems in using debuggers PD30 (formerly called PDB30) and PD30SIM (formerly called PDB30SIM) for the M16C/60 series and PD77 and PD77SIM for the 7700/7751 series of microcomputers.



Products and Their Versions Concerned
All the versions of the following products are concerned in the problems:
Product NameDescription
PD30 (PDB30)Emulator debugger for M16C/60 series
PD30SIM * (PDB30SIM)Simulator debugger for M16C/60 series
PD77Emulator debugger for 7700/7751 series
PD77SIMSimulator debugger for 7700/7751 series
* PD30SIM V.3.00 Release 1 excluded.


Problems
The following problems are encountered when generating Motorola S format files using the upload function of the products concerned:
  1. When a Motorola S format file is generated using the [File] -> [Upload] menu or the UploadMot command, the check sum of the end record (the final line) cannot correctly be output. If this file is forced to be written into ROM, the ROM programmer may send an alert.

  2. When a Motorola S format file within an address range is generated using the [File] -> [Upload] menu or the UploadMot command, data in part of the range may not be output. This problem occurs if all the following conditions are satisfied:

    1. The size of the upload range specified (the ending address - the starting address + 1) is not 1024 bytes (or its multiple).
    2. The starting address specified is not 400h (or its multiple).
    3. The ending address specified is within the following range:
      • FFC00h--FFFFFh (for M16C/60 series debuggers)
      • FFC00h--FFFFFh (for 7700/7751 series debuggers)

Workaround
  1. For Problem 1.
    Motorola S format files generated with the upload function of the debuggers can be used without trouble provided that the files are re-downloaded with the debuggers. However, if these files are forced to be written into ROM, some types of ROM programmer may send an alert. Therefore, don't write these files into ROM.

  2. For Problem 2.
    When Motorola S format files are generated with the ending address specified within a range of FFC00h--FFFFFh (for M16C/60 series debuggers) or FFFC00h--FFFFFFh (for 7700/7751 series debuggers), specify the starting address as follows not to satisfy conditions a, b, and c described in Problem 2 above:

    • The size of the upload range (the ending address - the starting address + 1) is 1024 bytes (or its multiple).
    • The starting address is 400h (or its multiple).

Note
Machine language files generated with the upload function of debuggers are to be used for debugging only. Please create those to be written into the ROMs of final products with the load module converter or HEX file converter included in compilers.


Schedule for Fixing Problems
We plan to fix these problems in our next release.





© 2008. Renesas Technology Corp., All rights reserved. Privacy | Legal