Initial Problem: " Unknown command 'katinstall' - try 'help' " while building filesystem

Overview: Get new version of uboot, load new version image, erase old version, flash new version

Get new version of uboot

• Go to http://www.gumstix.net/feeds/u-boot and download appropriate binary

  version t home directory. (Ours was u-boot-connex-400-r1604.bin, apparently

  revision is unimportant.)
      

• ?Reboot the gumstix. (Exit from GUM prompt, remove power cord, reinsert, then

  use:

	C-Kermit> take ~/gumstix/gumstix-oe/extras/kermit-setup
	C-Kermit> connect
     to get back into the GUM> prompt.)

Load new version image

• Prepare uboot to receive the file using the command:

	GUM> loadb a2000000

• Break the serial connection with the escape sequence. Begin the filetransfer

  with the command:

	C-Kermit> send u-boot.bin
	Note that nothing has changed; the image is merely sent to the stix, not
     flashed.

• So move back into the gumstix command module by reinstating the connection:

	C-Kermit> connect

Erase old version 

• And now we need to do the hard part: flashing the memory. We must first

  unshield the original uboot's sector with:

	GUM> protect off all
     the stix will respond with:
	Un-Protect Flash Bank # 1
	....................... done
	erase the image with

        GUM> erase 1:0-1
     and you should get:
	Erase Flash Sectors 0-1 in Bank # 1 
	.. done
	GUM>

Flash new version 

• Finally, we use:

	GUM> cp.b a2000000 0 ${filesize}
	Copy to Flash... done
	GUM>reset

This should result in a reboot, but stop the autoboot and we're done! 

Errors 

Note: After the reboot, wer got this message

    U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604

     *** Welcome to Gumstix ***

    DRAM:  64 MB
    Flash: 16 MB
    Using default environment

    SMC91C1111-0
    Net:   SMC91C1111-0
    Hit any key to stop autoboot:  0 
    Instruction Cache is ON
    Copying kernel to 0xa2000000 from 0x00f00000 (length 0x00100000)...done
    ## Booting image at a2000000 ...
    Bad Magic Number
    GUM> 

After checking the internet, we found that the "Bad Magic Number Error" is related

to an missing filesytem. Thus, we can ignore the error as long as we are proceeding

with loading the filesystem.