Re: [iPAQ] corrupted flash downloads

Hm. I take it back, I'm not so convinced it's xmodem's fault (esp. with
the xmodem block checksums). I now remember what happened last time I
had this problem -- I could not get the image to flash right through the
boot loader, and I had to resort to doing 'rsh otherbox if=usr-cramfs
bs=4096 | dd of=/dev/flash5 bs=4096' to get it to flash right. Now, I
can't do that in this case because of two reasons -- it's my root cramfs
that's corrupted (md5sum is incorrect and I get decompression errors),
and I don't think that the system would do too nicely if I dd'd over the
/ filesystem (then again, I don't think it would do all that badly --
I'm dd'ing the same data.. hmmm. I'll have to try it, worst case I
reflash from bootldr).

The other issue is that I think that my kernel image is corrupted. I was
poking around the bootldr code last night to figure out where the kernel
is stored, and added a 'cksum' command that runs the already-included
bsd_cksum code on an arbitrary chunk of flash; this should be enough,
md5sum is probably overkill for this purpose. However, I'm a little
hesitant to put my own bootloader on my iPAQ :-) Is there a way that I
can get at the kernel? I'm going to try dd'ing from /dev/flash0 at the
offset that's specified for the kernel in the bootldr. Also, does the
ipaq have space for the altkernel that seems to be an option? (I'm
assuming this would eat up /usr/local.)

        - Vlad
        
Received on Sat Sep 23 08:10:23 2000