> 2) Another approach that I've used in the past, that does not
require
> a network connected computer is to save several Redboot
configuration
> images to files on the flash file system. Set up a particular
Redboot
> configuration using fconfig. Then using nanddump, create a file
image
> to be restored selectively later. To restore a particular redboot
> configuration, use nandwrite (I think it's called) from userspace.
> You also have to use mtd_debug to erase the whole 16K block, so
make
> sure the image file is the whole 16k block as well.
> Following are the relevant lines from a writerbconfig script file I
> used for some time.
>
> mtd_debug erase /dev/mtd/2 3096576 16384
> nandwrite -s 3096576 /dev/mtd/2 $1
>
> (Please use with caution and verify addresses carefully. This was
> used with a ts7260.)
Be careful with this. Each NAND chip has bad blocks in different
places that our production process "works around" when placing
RedBoot on flash. What this means is that one image taken from one
board may not be compatible with another board with different bad
blocks.
//Jesse Off
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|