First of all, I think you have failed to upgrade u-boot. from your early post, you state that you load u-boot.bin in memory but I did not see any description you write it back to nand. I could give you instruction on how to write the u-boot.bin in mmeory to NAND but I am not in front of plug, I don't trust my memory to give the right instruction so please search this fourms, I think you can find the right command sequence on how to write the uboot back to NAND.

the reset of message most likly because uboot 1.1.4 (3.4.16) have problem with USB device, so once you succeed upgrade u-boot you should have no problem.

successfully from the Marvell shell. Device 0:1 might be your problem there. Also, a few on the forums here say to use FAT16 partitions. I believe this prevents you from accidentally creating partitions larger than 2GB, and possibly improves compatibility for the tools.

First of all, I think you have failed to upgrade u-boot. from your early post, you state that you load u-boot.bin in memory but I did not see any description you write it back to nand.

Related to this, can I test a new uboot by loading it and the running commands, but not the ones() to save it back to nand. By test I mean try it, and if it fails then a power off/on will take me back to where I was with the previous, working uboot.And, if I do update uboot, do I lose environment variables and have to reset them?

# I'm thinking that the problem may be that OSX's disk utility formats to FAT32, hence the bad partition. So I used to Disk Utility to simply erase the existing partitions and reformat the drive to FAT32 "Unfortunately, when I try to repartition the USB thumb drive with:

Started partitioning on disk2Unmounting diskCreating partition map[ \ 0%..10%..20%......................................... ] Waiting for disks to reappearFormatting disk2s1 as MS-DOS (FAT16) with name SDA1Error: -9962: The chosen size is not valid for the chosen filesystem

#I was thinking that the size might be too big, so I tried the same command with 250M, but got the same -9962 error. Any ideas?

First of all, I think you have failed to upgrade u-boot. from your early post, you state that you load u-boot.bin in memory but I did not see any description you write it back to nand.

Related to this, can I test a new uboot by loading it and the running commands, but not the ones() to save it back to nand. By test I mean try it, and if it fails then a power off/on will take me back to where I was with the previous, working uboot.And, if I do update uboot, do I lose environment variables and have to reset them?

You can test u-boot without writing it in to storage. you will need to have access to u-boot elf file, not the .kwb file. I use openond to load it into ram.

Thanks. But those instruction seemed to be a way of testing it on a running kernel!?!I was really just wondering whether it could be tested at the "console prompt" (i.e. before any kernel had booted) without writing it to nand.