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

using old code rom with new code ram

Hi,

I have a working old code in rom 32k, I added ram code at the upper 32k and I set the hw to start form the new ram at 32k.

I want to address old function from the new ram code without modify the old project.

once I compile the project code the hex output is not the old rom hex with the new ram code.

rather it recompiled the old code to optize it and I have a new hex that is not like the old rom hex with the new additions.

The thinng is that I need to address the old code function (fixed hex in rom).

what can I do?

regards,
dan

Parents
  • "once you know how to call the function in asm its solved."

    Repeating the same claim many times doesn't make it true. You are still driving head-first into a meteor storm without any shields. You would already have managed a lot of architecture work on a new design if you hadn't decided to waste time with a lost cause.

    Look until you die, but it's the job of the compiler/linker to do what it is intended to do. It is most definitely not designed to scoop out usable code fragments from a completely different application - an application that is mixed assembler/C and that may not be changed but does require lots of global bits and bytes to be in known states to work as expected.

    "There must be an easier way" is a dreamers hope to untie the Gordian knot. Yes - the easier way is to ignore our OTP contents, and cut the Gordian knot instead of trying to untie it.

Reply
  • "once you know how to call the function in asm its solved."

    Repeating the same claim many times doesn't make it true. You are still driving head-first into a meteor storm without any shields. You would already have managed a lot of architecture work on a new design if you hadn't decided to waste time with a lost cause.

    Look until you die, but it's the job of the compiler/linker to do what it is intended to do. It is most definitely not designed to scoop out usable code fragments from a completely different application - an application that is mixed assembler/C and that may not be changed but does require lots of global bits and bytes to be in known states to work as expected.

    "There must be an easier way" is a dreamers hope to untie the Gordian knot. Yes - the easier way is to ignore our OTP contents, and cut the Gordian knot instead of trying to untie it.

Children
No data