This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LOCATING SUBROUTINES IN MEMORY

I am trying to put a subroutine at a fixed address (I want it to remain fixed after the code is rebuilt and other modules are changed).

First I linked my code and obtained its absolute linked address (assigned by the linker). Then I used the _at_ (0x07A) command in the C source file.
I got a FIXUP error when I linked.
When I did the same thing using the linker SE command, I didn't get any errors. I really wanted to cast the addresses in the source
C code file using the _at_ command but I am having problems.... Any thoughts...



Thanks, Jim

Parents
  • Tom

    Thanks for the help and your design comments.

    I believe that I can locate variables and subroutines where I want them in
    internal or external memory. I am concerned about the library routines
    as you pointed out. Is it possible to get the library source and then locate subroutines
    and data to external memory when the application code may require
    these utilities? I could let the linker relocate them if this is possible. Note: This
    system design should not see many changes in the functional side, however
    the fixed side (251 onboard) will not be allowed to change once burnt into the 251.

    The functional code changes will be done so as not to intentionally
    change the onboard code image.

    Any thoughts on this???

Reply
  • Tom

    Thanks for the help and your design comments.

    I believe that I can locate variables and subroutines where I want them in
    internal or external memory. I am concerned about the library routines
    as you pointed out. Is it possible to get the library source and then locate subroutines
    and data to external memory when the application code may require
    these utilities? I could let the linker relocate them if this is possible. Note: This
    system design should not see many changes in the functional side, however
    the fixed side (251 onboard) will not be allowed to change once burnt into the 251.

    The functional code changes will be done so as not to intentionally
    change the onboard code image.

    Any thoughts on this???

Children
No data