Re: regarding boot.bib and config.bib
From: Peter (arockiarajeshpeter_donot_spam_at_harita.com)
Date: 10/29/04
- Next message: Ringwood: "PBTOKEN ???"
- Previous message: Tang: "Re: ndisuio build problem"
- In reply to: Sujith: "Re: regarding boot.bib and config.bib"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 28 Oct 2004 23:52:02 -0700
In bootloader code of Lubbock BSp, MMU is turned on and turned off just
before calling Kernel Start.
I am not at all using the "ROMOFFSET" in my boot.bib file. Since, i need
boot.nb0.
How to remove this nk.bin and boot.bin overlapping that too with virtual
addressing?
here, since it's a virtual memory i'm not able to track which physical
memory will be used, any idea how to do that?
Really thanks for your reply...
Regards,
Peter
"Sujith" wrote:
> Hi,
> again that depends..
> because if you are switching on the MMU or not is very important. once MMU
> is on.. you are supposed to use only virtual address. and as you see the
> addresses are all SDRAM_BASE_C_VIRTUAL, which is cashing and buffering
> enabled area.
> since it is using virtual address.. it should be turning on the MMU.. and
> will turn off the MMU before a call to KernelStart.
> Regards
> Sujith
>
> "Peter" <peter@nospam.com> wrote in message
> news:465BD37D-7C25-43F2-85F2-7932FE4B41E2@microsoft.com...
> > Thanks for your reply.
> > I like to clarify some more.
> > If you see the boot.bib of Lubbock it is using 0x8000 0000 --> as you said
> > if it is a physical memory, in PXA255 this memory is reserved does not
> > belongs to any Chip Select. Then, here how come one can use Physical
> > memory????? really, it may be a trivial question too?
> >
> > thanks & regards,
> > Peter
> >
> > "Sujith" wrote:
> >
> > > Hi,
> > > Today I just have gone through the code, for some reference and this is
> what
> > > I understood.
> > >
> > > the address you have to use is physical address only. because, it
> > > bootloaders normally works in physical address only, not virtual
> address.
> > >
> > > as you said, you are able to download atleast 300 packets, that is
> proved.
> > > now, why it is failing after that, you have to find out!
> > > one possible option is that, the kernel is overwriting the bootloader
> area.
> > > check your boot.bib and config.bib. check your ROMOFFSET where it tries
> to
> > > load the NK.BIN.
> > >
> > > possibly this could be the problem.
> > >
> > > > Which address I need to specify in boot.bib? Physical / Virtual?
> > > physical.
> > > > boot.bib I need to give Flash address OR SDRAM Address?
> > > it depends on the type of build. if you are building for Flash it should
> be
> > > flash or else RAM
> > > > Is nk.bin configuration in config.bib should follow eboot
> configuration in
> > > > boot.bib? for SDRAM Image?
> > > certainly not. because, the configuration files in config.bib all should
> be
> > > virtual and boot.bib is physical ! :-)
> > >
> > > Best of Luck
> > >
> > > Regards
> > > Sujith
> > >
> > > "Peter" <peter@nospam.com> wrote in message
> > > news:DBB623F2-3624-405C-AD4E-74BDE02930E8@microsoft.com...
> > > > Hi,
> > > > i am porting Lubbock BSP, for a hardware made with reference to
> Accelent.
> > > > Now, i am in the process of downloading the OS nk.bin through
> Ethernet.
> > > >
> > > > I saw boot.bib and config.bib in Lubbock BSP, in that boot.bib and
> > > > config.bib is using virtual memory for the definitions. Am i right?
> > > >
> > > > But, when i use 0xA000 0000 i-e my SDRAM Physical address. My
> bootloader
> > > > atleast initiating the download process and disconnecting after 300
> TFTP
> > > > Pakcets.
> > > > config.bib i am using lubbock's configuration.
> > > >
> > > > When i change the boot.bib to 0x8000000 i-e virtual address of SDRAM i
> am
> > > > not able start download itself. PB is able to detect the target but
> it's
> > > not
> > > > starting the download. Target is keep sending BOOTME packet.
> > > >
> > > > Here are my question:
> > > >
> > > > Which address i need to sepcify in boot.bib? Physical / Virtual?
> > > > boot.bib i need to give Flash address OR SDRAM Address?
> > > > Is nk.bin configuration in config.bib should follow eboot
> configuration in
> > > > boot.bib? for SDRAM Image?
> > > >
> > > > Please suggest.
> > > >
> > > > Thanks & regards,
> > > > Peter
> > > >
> > > >
> > >
> > >
> > >
>
>
>
- Next message: Ringwood: "PBTOKEN ???"
- Previous message: Tang: "Re: ndisuio build problem"
- In reply to: Sujith: "Re: regarding boot.bib and config.bib"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
