Re: where is eboot's ethernet download buffer?

You should look at the ethdbg library for the controller you are using : it
is probably using buffers through a define that is compliant with the
declaration in boot.bib

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADENEO (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
----------------------------------------------------------------

"mobilevil" <mobilevil@xxxxxxxxxx> a écrit dans le message de news:
urPAuypYFHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
> hello,
> this is ce 5.0, mainstoneii's eboot.bib
> i was placing my big data buffer in 80060000, which is GAP, reserved for
> future.
> and I found out that someone is using this space during image download.
> and it happen in the exact same time(well % of the download it is) if I
> move my data futher, then the download can go futher.
>
> seems it is the eboot downloading buffer.
> now I move my data to 83F00000 and everything works fine. but it is not a
> GOOD way to avoid problem, right? so can anyone tell me how to config the
> eboot download buffer?
>
> ; 8000.0000 -+
> ; | Bootloader Stack (64KB)
> ; 8001.0000 -+
> ; | Bootloader RAM (64KB)
> ; 8002.0000 -+
> ; | Bootloader Code (256KB)
> ; 8006.0000 -+
> ; | GAP (reserved for future)
> ; 800F.F000 -+
> ; | ARGS (4KB)
> ; 8010.0000 -+
> ; |
> ; | OS (NK) Code (48MB)
> ; |
> ; 8310.0000 -+ **auto-size**
> ; |
> ; | OS (NK) RAM (15MB)
> ; |
> ; 8400.0000 -+
> ;
> ;******************************************************************************
>
> MEMORY
>
> ; Name Start Size Type
> ; ------- -------- -------- ----
> STACK 80000000 00010000 RESERVED
> RAM 80010000 00010000 RAM
> EBOOT 80020000 00040000 RAMIMAGE
> RSVD 80060000 0009F000 RESERVED
> ARGS 80FF0000 00001000 RESERVED
>
>
> CONFIG
>
> AUTOSIZE=OFF
> COMPRESSION=OFF
> PROFILE=OFF
> KERNELFIXUPS=ON
>
> ROMSTART=80020000
> ROMWIDTH=32
> ROMSIZE=00040000
>
> ; The bootloader is fixed up to run from RAM, but is stored in flash.
> ROMOFFSET
> ; adjusts the .bin file record headers to that they lie in flash (this
> tells the
> ; bootloader already on the device to store the image in flash).
> ROMOFFSET=3C9E0000
>
> MODULES
>
> ; Name Path Memory
> Type
>
> - ---------------------------------------------- -----------
> nk.exe $(_TARGETPLATROOT)\target\$(_TGTCPU)\$(WINCEDEBUG)\eboot.exe
> EBOOT
>
>
>


.

Relevant Pages

  • Re: Sony MAVICA FD-92 Question...
    ... Why is is that you can only record video for ... I can't understand why they couldn't buffer it with the ram and write to the flash as you go. ...
    (sci.electronics.repair)
  • Re: where is eboots ethernet download buffer?
    ... oh but i am using my own controller driver, and the big data buffer I am ... >> and I found out that someone is using this space during image download. ... >> seems it is the eboot downloading buffer. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Audio skips when RAM is ~full
    ... It's different because you need to reserve a fixed amount of ram for the ... There may be a problem with the way the audio buffer gets allocated or freed. ... Basically, you tell it how many kB you want to free, then it allocates ...
    (Linux-Kernel)
  • Re: Fast memcpy in kernel space
    ... I would like to see a VC managed method of mapping direct access to the video ... hardware frame buffer. ... the RAM copy of the VC being switched to would be copied in. ... the video hardware buffer from the text buffer ... ...
    (comp.os.linux.development.system)
  • where is eboots ethernet download buffer?
    ... seems it is the eboot downloading buffer. ... RAM 80010000 00010000 RAM ... The bootloader is fixed up to run from RAM, but is stored in flash. ...
    (microsoft.public.windowsce.platbuilder)