Re: lots of easy questions about eboot/nk startup
From: Tweeeek (Tariq.Mahmood_at_nospam.com)
Date: 03/09/04
- Next message: Oliver Chang: "Re: About Screen Saver and IME status window"
- Previous message: Yannick Chamming's [eMVP]: "Re: GetIdleTime vs. PXA-255 (Lubbock)"
- In reply to: Yannick Chamming's [eMVP]: "Re: lots of easy questions about eboot/nk startup"
- Next in thread: Andrew: "Re: lots of easy questions about eboot/nk startup"
- Reply: Andrew: "Re: lots of easy questions about eboot/nk startup"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Mar 2004 08:45:55 -0000
WOW.....that was brilliant cleared a few of questions that were lingering at
the back of my mind
Thanks
"Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in message
news:ufKW7BbBEHA.3184@TK2MSFTNGP09.phx.gbl...
> 1/ you can set in image settings under PB if you want to maintain eboot
> space when copying NK in RAM or if it can be overwritten.
>
> 2/ NK.BIN is not a compressed format : it is binary record files (a record
> consist in a start address, a length and datas). It allows to avoid
> including '0' in the image, but it is not compressed more than that.
> You can activate compression in your image for some modules, but it will
be
> uncompressed at execution, not when loading from flash to RAM.
> If you want to use compression, you have to update your bootloader to
> implement the decompression algorithm in it.
>
> 3/ ??? I think you're talking about multi bin architecture : this
> architecture allows you splitting the content of your image in different
bin
> files, which can be mounted separately, or even at execution time (a kind
of
> paging). By default, PB includes all features in one bin file : NK.BIN, so
> it is ok if your driver is in NK.BIN
>
> 4/ Yes, but it has to be taken in account in CONFIG.BIB file when you
define
> where the various memory area are located : you can test on the activation
> of this flag to define if your NK.BIN will overwrite EBOOT.BIN or not (be
> careful : when downloading NK.BIN from flash to RAM, eboot.bin is still
> executing, so you might have some issues if you don't maintain eboot space
> in memory)
>
> 5/ No it is using a TFTP server (implemented in eboot) + BOOTP commands.
> KITL is activated once kernel is started for debugging.
>
> 6/ MAybe you should maintain a download support in eboot that can be
> activated through a specifc mode (on a GPIO, or smthg like that). You can
> support download on eboot without activating kernel debugging on CE
device,
> which allows you to free the download link once download is done for
> applicative usage.
> Another way is to directly burn your flash from a "golden unit"
>
> Best regards,
> Yannick
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> ADESET
> Windows Embedded Manager
> ychammings AT adeset DOT com>
> http://www.adeset.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
>
> "Andrew" <anonymous@discussions.microsoft.com> wrote in message
> news:99bb01c405a6$b6727180$a101280a@phx.gbl...
> > Hi All,
> >
> > I have a few questions which would help me greatly if
> > answered or if you could point me to a URL that would
> > provide the info. Sometimes the PB help can be cryptic,
> > outdated and/or platform specific (CEPC). This seems
> > like very basic pieces of information but your answers or
> > location of the answers would be appreciated. I'm using
> > the XSC1BD BSP with eboot and PB 4.2.
> >
> > 1) Does eboot use any RAM after the Kernel is started
> > (does it stay resident)?
> >
> > 2) Is there an existing method of compressing NK.bin in
> > flash and extracted into RAM when the device boots or do
> > I have to perform this in my bootloader myself? Or is NK
> > already compressed?
> >
> > 3) I read in the PB help that there is a NK image and a
> > Driver image. My drivers appear to be included in my NK
> > image. Is this correct?
> >
> > 4) I read in the PB help that there is a "Enable Eboot
> > Space in Memory" under the build options tab. Does this
> > actually exist?
> >
> > 5) Is the downloading of the NK image in PB (after eboot
> > has started) via the KITL transport? I know that CESH
> > and the debug interface (stepping/breakpoints) do.
> >
> > 6) If in the future I want to concrete my bootloader and
> > disable all download/kitl/serial etc and just have it
> > start the current image burned into flash, how do I
> > download a new NK image in the future? Is there a
> > current method through PB/KITL? Can I just overwrite the
> > image in flash and restart the device with an application?
> >
> > Cheers, Andrew
> >
> >
>
>
- Next message: Oliver Chang: "Re: About Screen Saver and IME status window"
- Previous message: Yannick Chamming's [eMVP]: "Re: GetIdleTime vs. PXA-255 (Lubbock)"
- In reply to: Yannick Chamming's [eMVP]: "Re: lots of easy questions about eboot/nk startup"
- Next in thread: Andrew: "Re: lots of easy questions about eboot/nk startup"
- Reply: Andrew: "Re: lots of easy questions about eboot/nk startup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|