Here are the binary images that we have been loading into shipped Balloon2s, in case you need to go back to a known-good image.
On 2.05g boards shipped from Sept 2003 onwards:
[Bootloader|http://balloonboard.org/files/balloon2/205g/sept2003/bootldr.fast] v2-20-2 (September 18th 2003) (218k)
[CPLD data|http://balloonboard.org/files/balloon2/205g/sept2003/balloonv11.jed] (66k)
[(Initial small bootloader|http://balloonboard.org/files/balloon2/205g/sept2003/bootldr.small]) (54k)- for faster JTAG uploads if starting from scratch
This is the currently-recommended set of files, which has a newer bootloader that allows easy changing of the board 'build' flavour, and a newer kernel (2.4.25), but is otherwise as above. An updated root image with the 2.4.25 kernel modules in would be useful, but I haven't prepared one yet (Wookey).
[Kernel|http://balloonboard.org/files/balloon2/205g/zImage] 2.4.25-vcs2-tcl1 (717k)
[Bootloader|http://balloonboard.org/files/balloon2/205g/bootldr.fast] v2-20-2 (November 6th 2003) (196k)
[CPLD data|http://balloonboard.org/files/balloon2/205g/balloonv11.jed] (66k)
[(Initial small bootloader|http://balloonboard.org/files/balloon2/205g/bootldr.small]) (54k)- for faster JTAG uploads if starting from scratch
Important: If you are attempting to load a yaffs filesystem image, such as the root filesystem, into a partition which already contains a filesystem, it's likely that the resulting mixture of new and old filesystems will cause problems. These can range from mysterious files which won't delete to a kernel panic when attempting to mount the filesystem.
To avoid this, erase the NAND flash and reset yaffs before loading a new filesystem: %%%nand erasechip %%%yaffs reset %%%load root