 |
|
|
RENESAS TOOL NEWS on March 1, 2005: RSO-M3T-NC308WA_2-050301D
Notes on Using
C-Compiler Package M3T-NC308WA
|
Please take note of the following problems in using the M3T-NC308WA
C-compiler package, which is used for the M32C/90, M32C/80, and M16C/80 series of MCUs:
- On using assembler directive commands ".ID" and ".PROTECT"
- On using assembler options "-mode60" and "-mode60p"
- Problem on Using Assembler Directive Commands ".ID" and ".PROTECT"
- 1.1 Version Concerned
- M3T-NC308WA V.5.20 Release 1
- 1.2 Description
- If assembler directive commands ".ID" or ".PROTECT" is put in the
program, the following option and others cannot be used:
(1) Command option "-U" in the LN308 linkage editor
(2) The STK viewer
(3) The Map viewer
(4) The UTL308 utility, which declares SBDATA and the SPECIAL page functions
(5) The inspector functions in the TM (an integrated development environment)
- 1.3 Workaround
- This problem can be circumvented in any of the following ways:
| (1) | Delete assembler directive command ".ID" and use command
option "-ID" of the LMC308 load module converter.
|
| (2) | Delete assembler directive command ".PROTECT" and use command
option "-protect1", "-portect2", or "-protectx" of the LMC308.
|
| (3) | Use a fixed value as a value set by an assembler directive command:
Example: Case where assembler directive command ".PROTECT" used
---------------------------------------------------------------
.org 0FFFFFCh
RESET:
.lword start | 0ff000000h ; at the ROM code protect control
; address,FFH is set as a fixed value.
--------------------------------------------------------------- |
- 1.4 Schedule of Fixing the Problem
- This problem has already been fixed in the M3T-NC308WA V.5.20 Release 02.
Notes on Using C-Compiler Package M3T-NC308WA
RSO-M3T-NC308WA_2-050301D
- Problem on Assembler Options "-mode60" and "-mode60p"
- 2.1 Versions Concerned
- M3T-NC308WA V.1.00 Release 1 through V.5.20 Release 02
- 2.2 Description
- If assembler option "-mode60" or "-mode60p" is put in the assembler
source program, the following instructions are not replaced with those
for the M32C/90, M32C/80, and M16C/80 series of MCUs with no
warning messages being provided:
- 2.3 Workaround
- If the above instructions are put in the assembler source program,
check their functions performed in the M32C/90, M32C/80, and M16C/80 series of MCUs to use them.
The reason is that the registers used at the execution of the above
instructions in the M32C/90, M32C/80, and M16C/80 series of
MCUs are different from those used in the M16C/60, M16C/30, M16C/20,
M16C/10, M16C/Tiny, and R8C/Tiny series, so, the results of operations
or transfers that the user is expecting may not be obtained.
Therefore, rewrite the above instructions to meet the related functions
of the M32C/90, M32C/80, and M16C/80 series of MCUs.
- 2.4 Schedule of Fixing the Problem
- We plan to fix this problem in the next release of the product.
|
|
