Hi Mahesh,
(also including gem5 list)
I forced the linker to put the sections at specific locations eg
SECTIONS {
.text 0xc0000000: { *(.text); }
}
That way the linker puts the .text section at this specific virtual
address. Back then I did it to get the same memory layout as the linux
kernel, since this was working. As of now I've written my own loader which
takes care of loading and relocating my kernel.
Hope that helps.
cheers,
Samuel
On Fri, Jun 22, 2012 at 8:37 AM, Mahesh Jethanandani <
mjethanand...@gmail.com> wrote:
> Samuel,
>
> I am having the same issue. But I do not understand what you mean by changing
> the linker script. Could you elaborate on it?
>
> Thanks
>
> -------------------------------------------------------------------
>
>
>
>>
>> Yes you're right, I specified --bare-metal to test some stuff. I changed my
>
> linker script to get the same entry point as the sample arm linux kernel.
> Without --bare-metal it now complains that 'udelay' is missing, but it
> seems to get past the error.
>
> I don't know about udelay yet. Is that something linux kernel specific (I'm
> not booting a linux kernel)? Do I have to provide this or can I just
> 'ignore' it?
>
> Best,
>
> Samuel
>
>
> On Sun, Mar 11, 2012 at 5:21 PM, Ali Saidi <sa...@umich.edu> wrote:
>
> > What is happening is that the elf loader is trying to load the kernel in
> > memory at address 0xc0008000 which doesn't exist in the system. It should
> > be loading it at address 0x8000. Perhaps you've specified bare-metal on the
> > command line or somehow created a ArmSystem object as opposed to
> > LinuxArmSystem? The latter takes care of mundging the address for Linux.
> >
> > Thanks,
> > Ali
> >
>
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
