• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 22 subscribers
  • Views 1497 views
  • Users 0 members are here
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

locating functions automatically

Michael Albano

I need to locate a large number of functions in the a specific memory range. I have tried using the ?pr?*?myobject wildcard like this:

?PR?*?myobject (0XC11200)


(myobject has 3 functions: fxn1,fxn2,fxn3)

all it does is locate the first function and then gives these error messages:

*** ERROR L120: CONTENT BELONGS TO ERRONEOUS SEGMENT
    SEGMENT: ?PR?fxn2?myobject
*** ERROR L120: CONTENT BELONGS TO ERRONEOUS SEGMENT
    SEGMENT: ?PR?fxn3?myobject

===
is there a better way to do this? can i simply specify a new memory class and assign my new functions to the new class? if so, how do i do this?

Parents
  • 0 in reply to ²erik malund

    "if you can get a code patch in, you can get new code in as well. WHY PATCH?"

    Well, the original code is in ROM and it's around 80kb. and i only have around 16kb EEPROM for the patch.
    I still need the patch to be able to call into the original ROM code. Unfortunately, the linker isn't cooperating...

    Any help would be much appreciated.

Reply
  • 0 in reply to ²erik malund

    "if you can get a code patch in, you can get new code in as well. WHY PATCH?"

    Well, the original code is in ROM and it's around 80kb. and i only have around 16kb EEPROM for the patch.
    I still need the patch to be able to call into the original ROM code. Unfortunately, the linker isn't cooperating...

    Any help would be much appreciated.

Children
  • 0 in reply to Michael Albano

    Well, the original code is in ROM and it's around 80kb. and i only have around 16kb EEPROM for the patch.

    And how were you planning on getting that patch code to be called by the ROM image in the first place?

    Unfortunately, the linker isn't cooperating...

    Well, you didn't exactly ask it to cooperate, did you? So far, you're fighting it. You should be linking the original ROM application into your patch project so all functions already present will be taken from that. The "symbols only" option should help with that.

  • 0 in reply to HansBernhard Broeker

    "And how were you planning on getting that patch code to be called by the ROM image in the first place?"

    the rom application was written with a patch in mind. it checks certain addresses in the eeprom to see if there is a patch. if so, it jumps to a predetermined address in eeprom.
    This already works and i successfully call into my patch. my problem is the link back. it seems that the compiler/linker determined that i need additional functions in my ?C?LIB_CODE. that's why it grew in size.
    Now because of this, my patch code is linked to a differently mapped version of the rom code, not identical to the original.

    i'm at home now. will look into the "symbols only" option when i get in tomorrow. Thanks for all the help.

  • 0 in reply to Michael Albano

    Michael, I am very interested in finding out if you could make it work and how you were able to compile/link new version of patch keeping ROM binary exactly the same. I am guessing you would need to pin-down some patchRAM code/data (directly referenced by the ROM) to original addresses used during ROM tapeout.

    I have a very similar requirement for my project.

  • 0 in reply to Shashank Shekhar

    actually, i wasn't able to make the full patch work. i did a simple workaround by isolating what parts of the patch caused the CLIB to enlarge and excluded them from the build. then i worked with what i had left...

    I was pressed for time so that was the best solution.
    if you find a better way to do it, please tell me. thanks. :)