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

Dynamic loading ARM9 executables.

Note: This was originally posted on 28th January 2009 at http://forums.arm.com

Hi all,

Our system have one DSP and one ARM and system will boot with DSP  then DSP  should load ARM executable in ARM program memory.  how to do this ?.
We tried the following, but unable to succeed .
1] build the ARM code(which has boot code also), it will generate '.out ' executable
2] convert '.out ' executable into binary using hex470.exe .
3] From DSP read generated binary file and copy into arm program memory.

I think we are missing something like we need get address of each sections like .text , .data etc.. according to that we need to copy(is it right??). But how to get this address location information?
Or is there any procedure to do that?

Thank you,
Vicky
Parents
  • Note: This was originally posted on 28th January 2009 at http://forums.arm.com

    I think we are missing something like we need get address of each sections like .text , .data etc.. according to that we need to copy(is it right??). But how to get this address location information?
    Or is there any procedure to do that?


    You can get this information from your ".out" file.  You don't say which tools you used initially to build this file, but they ought to have a tool that can extract this information.  In the RVCT tools, for example, the "fromelf" utility can be used on an image (which usually has a .axf file extension) to get this information.

    Once you have this information you just need to make sure the sections are loaded to the correct places and branch to the entry point to start executing.
Reply
  • Note: This was originally posted on 28th January 2009 at http://forums.arm.com

    I think we are missing something like we need get address of each sections like .text , .data etc.. according to that we need to copy(is it right??). But how to get this address location information?
    Or is there any procedure to do that?


    You can get this information from your ".out" file.  You don't say which tools you used initially to build this file, but they ought to have a tool that can extract this information.  In the RVCT tools, for example, the "fromelf" utility can be used on an image (which usually has a .axf file extension) to get this information.

    Once you have this information you just need to make sure the sections are loaded to the correct places and branch to the entry point to start executing.
Children
No data