OK, today I have been mostly learning about updater.sh and how to brick and unbrick an SL-C3000.
I am at the point of working on the flashing process although it doesn't seem to be going as swimmingly well as possible.
After decoding the updater.sh that comes with the Sharp ROM 1.11 I found that it chops 16 bytes off the beginning of your initrd.bin and 16 bytes off the end of your Kernel image before flashing so my scripts that generate these files currently borrow the same region of bytes from each file on the original Sharp distribution...
This does not seem to be enough though. If I flash with tetsu's kernel I still end up with bricked Zaurus.. in fact the only way to get the tetsu Kernel to work is to flash using the updater.sh.c3000 file that he mentions on his site... strange... can't see anything else in updater.sh that may be causing it.
If, however, I use everything else (mversion.bin, initrd.bin and hdimage..) from the new build then everything works out absolutely fine... strange.
Anyone that's been playing around with updater.sh on an SL-C3000 please shout out...
I would like to just use this updater if possible for first tests.. I'll work on a Cacko like updater later on.
Regards,
Andy