From: Brian Avery (Brian.Avery@compaq.com)
Date: Tue Sep 17 2002 - 18:54:50 EDT
to verify the .gz files do gzip -tv file.gz (verbose verify)
-bavery
Jamey Hicks wrote:
>
> On Mon, 2002-09-16 at 19:23, morphius@symonds.net wrote:
> > Hi
> > Considering the size of the SDK after extraction, i was tempted to drop
> > the project. It gobbled up my entire free disk space.
>
> It is frightening, isn't it? But toolchains do tend to be large.
>
> > Thankfully, I did get the executable built. I copied the bootblaster over
> > and made a backup of wince_image.gz, asset_image.gz and saved_bootldr.gz. I also
> > took a dump of the register set.
> >
>
> Excellent!
>
> > The contents of
> > asset_image.gz - "asset_image."
> > saved_bootldr.gz - "saved_bootldr."
> > wince_image.gz - "wince_image."
> >
> > Now proceeding to install Linux....
> >
> > I have a couple of questions
> >
> > 1) How do i figure out that the gz files created by the bootblaster 3900
> > are corrupted or not?
>
> Use gzip to unpack them? gzip may have a verification option.
>
> > 2) I downloaded the latest copy of the bootldr source from the CVS
> > repository. Where and what tools do i require to build?
>
> The 2.95.2 toolchain at ftp://ftp.handhelds.org/pub/linux/arm/toolchain
> (if I didn't get the url wrong). This installs in /skiff/local/bin. Or
> the 3.0 cross toolchain from http://www.arm.linux.org.uk/
>
> Jamey
>
> _______________________________________________
> Bootldr mailing list
> Bootldr@handhelds.org
> http://handhelds.org/mailman/listinfo/bootldr
This archive was generated by hypermail 2.1.5 : Fri Jan 17 2003 - 17:47:04 EST