Two things (hard to be specific without knowing what tools you are using):
1. If you are lucky, this is just a problem with your setup of what
MCUez calls the PRM file. That's where you give absolute address
ranges to the named code/data segments of your program. Sounds like
your boot address (FFFE/FFFF) isn't properly reserved, and overlaps
some other segment.
2. [And you don't want to encounter this one.] If you are using
MCUez, there are some serious bugs in the linker. It does NOT
calculate relative offsets correctly when using math in code segment
declarations within an assembly program. [I don't recall the
details, but the result is that the assembly listings look fine, but
the S19/physical are messed up.] This can produce the same error msg
(because things aren't where they are supposed to be).
jmk
At 07:45 AM 2/9/2010 +0000, you wrote:
>Hi all,
>
>i am new to this software and hope to find some guidance over here.
>
>Firstly, I have encountered with this error:
>
>Link Error : L1119: Vector allocated at absolute address 0xFFFE
>overlaps with sections placed in segment .absSeg2. At the same time,
>over at my prm file, i realised this:
>
>*********************************************************************************************
>VECTOR-ALLOCATION SECTION
> Address InitValue InitFunction
>---------------------
> 0xFFFE 0x0'Error _Startup
>
>Both should be linked.
>
>Can someone advise me what to do? what am i supposed to do to
>rectify this error.
>
>Secondly, I would like to ask how to create a interrupt vector table
>in assembly language.
>
>fyi, my program is written solely in assembly language.
>Hope to hear from someone soon! =)
>
>