I am using e-mail because your 'gateway' does not allow attachments
For product info etc refer to call 334462 (a solved issue of mine)
I have used
c:\tools\keil\c51\bin\bl51 SLVstart.obj, SLVisr.obj, SLViic.obj, ... SLVmain.obj, SLVxdata.obj, SLVzdata.obj, ... SLVUmain.obj, as.lib, c51s.lib TO as.omf ... RS(256) IX >protl.log
without any problems for a while. Now I want to add a bootloader and try to the best of my understanding of the CO description in the manual this which gives errors
c:\tools\keil\c51\bin\bl51 SLVstart.obj, SLVisr.obj, SLViic.obj, ... SLVmain.obj, SLVxdata.obj, SLVzdata.obj, ... SLVUmain.obj, as.lib, c51s.lib ... CO ( ?PR?SLVUmain?SLVUMAIN (0xe000), ?PR?CUP*) ... TO as.omf RS(256) IX >protl.log
.src of the first (SLVUmain) and one consecutive module is attached
The intention is to locate SLVUmain at 0xe000 and the CUP* functions following it
In advance, thanks
Erik
Note This message was edited to reduce width.
I have used the Keil LX51 linker (i.e. not BL51) to do something similiar in the past.
The following would work in that linker.
SEGMENTS (?PR?SLVUmain?SLVUMAIN (C:0XE000), ?PR?CUP*)
Maybe using the extended linker is an option for you?
C:0XE000
I wonder, do you need the address qualifiers for addresses on the command line with BL51 as well?
No, you don't.
The BL51 Linker has segment-specific directives (CODE, XDATA, DATA, IDATA, and so on) that you use to specify the addresses for segments in these areas.
The LX51 Linker uses a generic SEGMENTS directive for all segment types. And, you need to specify qualified addresses (with the segment prefix).
Jon