it would seem that the following two commands would effect the upgrade after I sshed k1.bin.zip to the chumby's /tmp
flash_eraseall /dev/mtd4
unzip -p /tmp/k1.bin.zip |chumbyflash -m /dev/mtd4 -s 0x0 #no bad blocks at all in my chumby so no offset?
anyway here goes
time to brick a chumby classic
my flash exhibits no bad blocks so zero offset would be appropriate?
chumby:/usr/chumby# flash_eraseall /dev/mtd4
Erasing 16 Kibyte @ 2f8000 -- 98 % complete.
chumby:/usr/chumby# unzip -p /tmp/k1.bin.zip |chumbyflash -m /dev/mtd4 -s 0x0
Scanning for bad blocks..
Bad block scan complete.
Flash complete: wrote 1508864 bytes.
hmm so far so good..
now to follow the rest of the debian instructions... more later
hmm wiped out /usr/chumby/scripts somehow.. had to restore to factory defaults but the uname -a shows my kernel still there
uname -a
Linux (none) 2.6.16-csb #3 Tue Sep 14 01:33:50 PDT 2010 armv5tejl unknown
chumby:/usr/chumby/scripts#
and /usr/chumby/scripts back to normal
cat /proc/filesystems shows
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev usbfs
nodev pipefs
nodev futexfs
nodev tmpfs
nodev inotifyfs
nodev eventpollfs
nodev devpts
ext3
ext2
cramfs
nodev ramfs
msdos
vfat
hfsplus
nodev nfs
nodev nfs4
nodev jffs2
romfs
so ext2 and ext3 there and supported..
Cool I used the U2 removal tool and now my drive is seen by the chumby.. after I managed to find another valid path for updating the kernel image
So now the chroot stage for debootstrap is running and I am waiting..
So far this debian install procedure has been completely accurate .. all errors have been caused by the U3 windows garbage.
Then I have 3 more chumbys to do it to
gwen