• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 21 subscribers
  • Views 1297 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

WARNING L5: CODE SPACE MEMORY OVERLAP

Terry .

I have an asm file that generates a “WARNING L5: CODE SPACE MEMORY OVERLAP” message.

If I add the following line at the top of the code it compiles OK:

CSEG at 0x4000

But I want the linker to allocate the address so I tried the following:

CSEG

But the warning came back as the asm code is located at 0x0000.

The rest of my project is in “C”.

How do I get the linker to relocate my asm to an unused area of memory?

Terry

Parents
  • 0 in reply to ²erik malund

    Full version protected with a dongle.

    uVision3 V3.05c
    A51.exe V7.10
    BL51.exe V5.12

    I only have one asm file with one CSEG + lots of C files.

    I've worked out what the problem was.

    For some reason my asm file was at the end of the
    obj list in the lnp file so it was linking first.

    Putting it at the end fixed things.

    Terry

Reply
  • 0 in reply to ²erik malund

    Full version protected with a dongle.

    uVision3 V3.05c
    A51.exe V7.10
    BL51.exe V5.12

    I only have one asm file with one CSEG + lots of C files.

    I've worked out what the problem was.

    For some reason my asm file was at the end of the
    obj list in the lnp file so it was linking first.

    Putting it at the end fixed things.

    Terry

Children
No data