[Gumstix-users] bootcmd on build 1464

[Nicholas C. <nc...@cs...>]

I recently upgraded the uboot on my basix 400xm-bt from 1.1.4 to 1.2.0 
and then followed the verdex instructions to load the root filesystem 
and uImage. The initial bootm succeeded but on subsequent the system 
could no longer find the uImage:

### JFFS2 loading 'boot/uImage' to 0xa2000000
Scanning JFFS2 FS:
find_inode failed for name=boot
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for boot/uImage

I changed the command: 'fsload && bootm' in bootcmd to 'katload 100000 
&& bootm' and now the system boots correctly.

This seems like the logical and correct solution right? What I'm 
wondering now is whether there is some type of persistence from the 
previous uboot occurring in the environment variables when uboot gets 
upgraded? If so, others who are upgrading might like to be aware of this.

Nick