Topic: Chumby classic strangely bricked

Hi,
I've bricked my chumby sad
Not quite sure how - I was trying to get the latest linux kernel (2.6.34-rc1) running (but not by flashing it, rather kexecing it into ram from a modifed 2.6.16)

Bootloader appears to be intact because it gives me:
Block 0x00000081 is bad.
Block 0x00000082 is bad.
Block 0x000000A2 is bad.
Block 0x00000659 is bad.
80 bad blocks or less are normal for this NAND FLASH.

Welcome to the Chumby Ironforge Linux Loader v1.1 (bunnie@chumby.com)
Brought to you by Chumby Industries, Inc.

        --> Happy hacking! <--
<snip>
Version code for 3.8 found

MSP is cleared; flagging normal mode.

--> Booting into normal mode... <--

Copy Kernel to Memory
................................
Jump To Kernel


Then nothing.
It does this for both normal and recovery mode.

So I tried hostboot and with that (slightly modifed to setup spll correctly so that USB works) I can boot and mount the normal root filesystem (mtd5). Network works so I can ssh in.

I've dumped all the flash partitions and nothing looks amis.
I've also reflashed the normal kernel (mtd4) and it still doesn't work.

Before this problem I only had one bad block:
Block 0x00000659 is bad.

I now seem to have gained 3 more
Block 0x00000081 is bad.
Block 0x00000082 is bad.
Block 0x000000A2 is bad.

But according to my calculation they're in the PSP partition anyway.

Is the official bootloader image available somewhere so I can do a binary comparison?

Any Ideas?
Cheers,
Martin

Re: Chumby classic strangely bricked

Well replying to my own post here.

Finally got it working by erasing the three "bad" blocks - after patching the kernel to allow this.

I think they were caused by a bug in the driver (my fault) but the chumby shouldn't fail to boot due to this.

I'll start a new post for that problem...