 |
|
|
MESC TOOL NEWS:
MESCT-AS30-990216D
Please take note of the following problems in using assembler AS30 for the M16C/60 and M16C/20 series of microcomputers.
On Using abs30
- Versions Concerned
All the versions of AS30
- Problem
When assembler directive ".ORG" is described more than once in an absolute data section, the absolute address of the symbols defined in the second and later ".ORG" directives is not correctly generated (see Example 1).
[Example 1]
-----------------------------------------------------------------------
|
| .section ram,data
| .org 100h
| sym1: .blkb 1
| sym2: .blkb 1
| .org 200h
| sym3: .blkb 1 ; Address not correctly generated
| sym4: .blkb 1
|
-----------------------------------------------------------------------
- 3. Workaround
Please define a data section for each ".ORG" directive (see Example 2).
[Example 2]
-----------------------------------------------------------------------
|
| .section ram,data
| .org 100h
| sym1: .blkb 1
| sym2: .blkb 1
| .section ram1,data
| .org 200h
| sym3: .blkb 1
| sym4: .blkb 1
|
-----------------------------------------------------------------------
AS30 Precaution
MESCT-AS30-990216D
On Description of Sections
- Versions Concerned
Versions of AS30 V.3.00 Release 1 and later
- Problem
When, in lmc30, the address of a section where data exists and the one of a section where data does not are the same, and the latter section is linked later than the former address, the items of data existing in the same and later addresses may not be output to the machine-language file created by lmc30.
- Workaround
At linking, if a message appears which warns address overlapping in a section where no data exists, delete the section and reassemble.
Schedule of Fixing Problems
We plan to fix these problems in our next release.
|
|
