I had thought of this; but the point
1. Why is the error generated
in the assembly code? What do the error messages mean? It is perfectly valid code.
2. Even after using the
--data-loc=0x22 option, can I still define an absolute variable at, say, 30h,
without overlap? Can I make the compiler skip this loc'n when
assigning relative addresses?
----- Original Message -----
Sent: Tuesday, July 24, 2001 6:12 AM
Subject: RE: [Sdcc-user] How to define absolute
the 'data at 0x20 unsigned flags;'
use the compiler option --data-loc=0x22 this will ensure data segment starts @
not overlap with your absolute symbol.
I need to define a variable 'flags'
at internal ram loc.20h.
If I say
'data at 0x20
It converts to an equate in the
assembly file, so it does nor reserve any space, & may be overwritten by
other non-absolute variables.
specified 'extern unsigned flags;'
& made another file resv.asm
.area DSEG (DATA)
But I get the following when I try
to assemble it, I get :
.org in REL area or
missing or improper delimiters
operators terminators or delimiters
in line 6
.org in REL area or directive
Whats wrong? I'm using the default