Re: [iPAQ] Installing Via CF

T-

At 03:47 PM 10/11/2001 -0600, you wrote:
>The /dev/mtd* devices do relate to previous Linux partitioning. With
>jffs2 there would be 4 of these. 0 = bootloader, 1 = parameters, 2 =
>kernel and 3 = rootfs.

         Ah. So I could pad these to their respective flash boundaries,
concat them, and then Parrot-load?

>It is possible to pad each of these images up to the correct byte size
>and then concatenate them together. The difficulty is getting a params
>image as that is not normally passed around as a file. You could fill
>the params block with 0s, do the CF install and then boot to a serial
>console in bootldr and set the correct values. This still requires a
>serial cable or cradle though.

         Ok. So a serial install, then...

>Installing on one iPAQ and then backing up /dev/mtdblock* and creating a
>CF install from that will allow complete CF installations.

         That's my main question. The CE bootloader loads at addr
zero. Does this mean that the parrot loader lives at zero, and is
overwritten by the linux bootloader? E.g. space-bar on the serial console
during booting in Linux is the same thing (for linux) as we're doing when
we hold the "Ok" button during reset (for the parrot loader). E.g. a linux
install whacks the Parrot loader?

>As you noticed, this is only useful from CE to Linux and cannot be used
>for Linux upgrades as the Linux bootldr does not understand parrot CF
>card images.

         Sounds like a yes.

>So the mtd0-6 references would be the old cramfs/ext2 hybrid. but the
>same procedure will work with mtd0-3 style jffs2 images.

         I thought this might be a way to use the parrot loader to toggle
between OS's using only a CF card and a short wait. It seems like that
would take more R & D...

-G!

>Glenn Neufeld wrote:
> >
> > Greetings....
> >
> > I was going to try the method outlined on the Wiki by Tim Riker, wherein
> > the Parrot loader is used to store WinCE to a CF card, and then the CF card
> > is loaded with the Linux bootloader and kernel/filesystem flash image for
> > the Parrot loader to flash-on-startup....but I am confused about dd'ing the
> > kernel image onto the CF card; Tim refers to 6 files (mtdblock0..6) that
> > are concatenated into one for copying onto the CF card along with the MACAW
> > header that triggers the Parrot loader....

Glenn Neufeld _________________
_____________| neuf@power.net |
Received on Fri Oct 12 15:58:07 2001