Hi,
Does it possible to know where ( physical address ) the loader has
stored the different sections of an ELF executable file ?
That’s a good question, is the source avaliable for the primary, and
secondary boot loaders?
You could find out from there, and modify them if you had to. I would
REALLY like to play with that.
EZK
“pe” <pelskens@tecatom.fr> wrote in message
news:3B8D076E.BEE78A47@tecatom.fr…
Hi,
Does it possible to know where ( physical address ) the loader has
stored the different sections of an ELF executable file ?
The loaders at this time are not available for free. I know that the
loaders are available for most BSP (board support packages) however
for x86, I am not certain if it is available or not.
E.
EZK <peter.w.eddy@lmco.com> wrote:
That’s a good question, is the source avaliable for the primary, and
secondary boot loaders?
You could find out from there, and modify them if you had to. I would
REALLY like to play with that.EZK
“pe” <> pelskens@tecatom.fr> > wrote in message
news:> 3B8D076E.BEE78A47@tecatom.fr> …
Hi,Does it possible to know where ( physical address ) the loader has
stored the different sections of an ELF executable file ?
Hardware Support Account <hw@qnx.com> wrote:
The loaders at this time are not available for free. I know that the
loaders are available for most BSP (board support packages) however
for x86, I am not certain if it is available or not.
I think the original post was refering to a process loader, not a boot loader.
You can use the function mem_offset() or mem_offset64() to get the
physical location of memory block. So if you could fine your elf headers
with a virtual address, you can convert that to a physical one. There is
an example of that conversion in the docs for mem_offset().
-Adam
amallory@qnx.com