• State Not Answered
  • Locked Locked
  • Replies 17 replies
  • Subscribers 21 subscribers
  • Views 3236 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

Properly adding startup.a51

Steven Roth

Hi everyone.
So far I've only done some rather small 8051 projects, mostly with variants that had less than or equal to 64k memory.
Now I have a project which includes fairly large amounts of code-data running on SiLabs' C8051F12x, which has 128k.
Since inherently only 64k are accessible, I need to use code banking.
However, once - as noted in the application notes - I include STARTUP.A51 and the L51_BANK.A51, my application throws an Module Name Not Unique Warning for C_STARTUP.
In the KEIL Knowledge Base, I found the suggestion to rename C_STARTUP to C_STARTUP_MAIN to resolve the issue.
I did so, but then I got a code overlap warning at 0000H to 0002H.
I never had to deal with an overlap I didn't actually cause myself (manually) before, so I'm not sure how to resolve it.
In the M51, I found ...
C:0000H PUBLIC ?C_STARTUP_MAIN
(and, further down)
C:0000H LINE# 85.

I assume those are the overlapping segments, no?
I'm not sure how to progress in resolving the warning, could anybody shed some light on this for me?
Thanks alot!
Steven

Parents
  • 0 in reply to Andy Neil

    I see ... I think. ;p

    I'll first try to look into switching to the extended linker. As I have this particular project set up in the SiLabs IDE so far (I took a past project for another F8041x variant as starting point and expanded from there), it's not so simple as ticking a button, but I'll try to migrate the project to uVision and go on there. Not sure whether I'll manage to get there today, since I have some other issues I need to spend time on - otherwise it'll have to wait til monday.
    Would there be anything else to be considered in order to enable the built in support you mentioned?

    Anyway, thank you for your input.
    If anyone else can shed some light on how to relocate the startup function so it doesn't cause overlaps, this would still be appreciated, since I have a feeling I might run into this again at some time. :/

Reply
  • 0 in reply to Andy Neil

    I see ... I think. ;p

    I'll first try to look into switching to the extended linker. As I have this particular project set up in the SiLabs IDE so far (I took a past project for another F8041x variant as starting point and expanded from there), it's not so simple as ticking a button, but I'll try to migrate the project to uVision and go on there. Not sure whether I'll manage to get there today, since I have some other issues I need to spend time on - otherwise it'll have to wait til monday.
    Would there be anything else to be considered in order to enable the built in support you mentioned?

    Anyway, thank you for your input.
    If anyone else can shed some light on how to relocate the startup function so it doesn't cause overlaps, this would still be appreciated, since I have a feeling I might run into this again at some time. :/

Children
No data