Henrik
Mon Jun 19 10:18:59 CDT 2006
If we're talking about the same kit (and if i remember correctly), you
should be able to get 600-800kb/s download performance over ethernet.
I definately think you should make sure you're not running a debug
built bootloader. The numbers you say you get correspond pretty closely
to what you can expect from a debug guilt bootloader.
Also, you'll see a huge performace degredation if you're downloading
images that are stored and run directly from flash. However, since I
don't think that's supported out of the box for that kit, that's
_probably_ not the case.
Henrik Viklund
http://www.addlogic.se
Fredrik Jansson wrote:
> Yes, five minutes is slow... The platform is a Intel PXA27x Processor
> Developers Kit, and I only get ~85KB/s when downloading. On a samsung boa=
rd
> I got ~250KB/s... I haven't been able to figure out the problem is here.
>
> Thanks for all your id=E9as!
>
> Best regards,
> Fredrik
>
>
> "Henrik Viklund" <henrik.viklund@gmail.com> wrote in message
> news:1150725580.609419.90910@c74g2000cwc.googlegroups.com...
> > First of all, 5 minutes sounds extraordinalrily slow, atleast if you're
> > using ethernet as transport. You're not by any chanse using a debug
> > built bootloader?
> >
> > Anyway: yes you can develop a driver without having to download the
> > entire image for every change. I assume you have a working kitl
> > connection up and running:
> >
> > First of all a good thing is to be able to load the driver dll over
> > relfsd (the "release" directory), so ensure you have this up and
> > running (this gives your device direct access to all files under your
> > platform project's falat release directory).
> >
> > Second, you want the CE loader to load the driver from your flatrelease
> > directory rather than from your OS image's windows directory. This you
> > can do by setting up the module (driver dll) as a release directory
> > module (under menu Target->Release Directory Modules). This enures the
> > specified dll will be loaded from the flat release directory
> > ("release"), which is handy since that's where your driver output dll
> > will end up everytime you do a "build project".
> >
> > The thirt part of the equation may involve a (little) bit of extra work
> > depending on the driver. To be able to work effectively with the driver
> > in the release directory you need a mechanism to load and unload the
> > driver on command or else you won't be able to reload the new version
> > of the driver (in fact you won't be able to build the project if the
> > driver is loaded through the release driectory sincce the file is in
> > use). If it's a PnP driver, you might get away with simply unplug
> > whatever hardware you're driver interfaces for it to unload. Otherwise,
> > you need to write a small utility that can load and unload the driver
> > programatically.
> >
> > Henrik Viklund
> >
http://www.addlogic.se
> >
> > Fredrik Jansson wrote:
> >> Hi!
> >>
> >> I have developed an image that suites my needs and I am gonna start
> >> developing a driver. The image is pretty large (~20MB) and takes about
> >> five
> >> minutes to download.
> >>
> >> Is there any way to develop the driver in PB, download it (I can do th=
at
> >> manually with e.g. ActiveSync, it's not a problem) but I want to be ab=
le
> >> to
> >> debug it using the kernel debugger.
> >>
> >> My question in short is: it takes a long while to download the whole
> >> image
> >> so can I just download and debug a driver using PB?
> >