Re: where is eboot's ethernet download buffer?

oh but i am using my own controller driver, and the big data buffer I am
talking about is my ethernet device's data.
I guess it has something to do with eboot's tftp layer, where do eboot place
it's downloaded data?

"Yannick Chamming's [eMVP]" <ychammings_nospam@xxxxxxxxxx> wrote in message
news:eVM2OwNZFHA.3220@xxxxxxxxxxxxxxxxxxxxxxx
> 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: Assembly conversion to Pocket Pc format
    ... But in my case it is throwing exception before executing that statement what ... That is before reading buffer size it is throwing ... Stream respStream = resp.GetResponseStream; ... upload and download files in compact framework. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Reading a table
    ... Consider that the file must STILL have a rigorously-applied delimiter ... with a buffer of strings delimited by NULs that corresponds to your ... text files I download from the net, and I ... But when it comes time to parse a file that I've written myself ...
    (comp.lang.c)
  • Re: Memory Allocation in a Multi-Threaded Environment
    ... In general, I believe if you are sharing the same data between two threads, the design is ... A worker thread is created to read the entire file into a buffer whilst the ... catching up with the download. ... If you have to wait to resize until the processing is done, ...
    (microsoft.public.vc.mfc)
  • Re: 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)
  • Re: [PATCH] input/spi: add ads7843 support to ads7846 touchscreen driver
    ... to the spi layer while receiving data. ... I said that because it is true that most of spi controller drivers manage rx only transactions filling the tx buffer with zerros but the spi_s3c24xx.c driver seems to fill with ones ) ... I will check in our controller driver to sort this out. ... I ran into those troubles and add a zerroed buffer as tx. ...
    (Linux-Kernel)