Instalation errors flashing uBoot

I have just started the instalation. It's still going on.

I saw error messages about uBoot flashing and I would like someone to look at it and tell me if it went ok or not before I reboot.
As long as the dockstar is on I have access via serial and I can fix anything. When I reboot and it fails - It's over...

So please take a look.

# Installing uBoot
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb.md5   100% |*******************************|    49  --:--:-- ETA
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb       100% |*******************************|   512k 00:00:00 ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb.md5   100% |*******************************|    49  --:--:-- ETA
# Verified successfully!

# Installing uBoot environment
Warning: Bad CRC, using default environment
## Error: "ethaddr" not defined
Warning: Bad CRC, using default environment
## Error: "rescue_installed" not defined
Warning: Bad CRC, using default environment
## Error: "bootcmd_rescue" not defined
Warning: Bad CRC, using default environment
## Error: "rescue_custom_params" not defined
Warning: Bad CRC, using default environment
## Error: "usb_custom_params" not defined
Warning: Bad CRC, using default environment
## Error: "ubifs_custom_params" not defined
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.environment.md 100% |*******************************|    52  --:--:-- ETA
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.environment    100% |*******************************|   128k 00:00:00 ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
ECC failed: 6
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.environment.md 100% |*******************************|    52  --:--:-- ETA

# uBoot installation has completed successfully.

Edited 1 time(s). Last edit at 10/16/2010 08:35AM by naugtur.

naugtur Wrote:
-------------------------------------------------------
> I saw error messages about uBoot flashing and I would like someone to look at it and tell me if it
> went ok or not before I reboot.

The errors were about the u-boot environment settings. But the u-boot installation itself ("Writing data to block 0 .. 3") was successful, so it's safe to reboot. You may have to set some variables manually, but since you have serial access that shouldn't be a problem.

Thanks for the reply. It did run ok. I think I wouldn't reboot it today if you didn't respond. The "# Verifying uBoot environment\nECC failed: 6" part made me most nervous. ;)

I wish you (or anybody) could tell me where to look for info on what I'm missing in uBoot. I don't know what happened due to those errors.
I will find details for myself, I'm not a "write me commands to copy and paste in console" kind of guy ;) but I have no idea what is "uBoot environment" in the context of my log over there.

Does that mean that it had problems running binaries that set stuff in uBoot? What was being set there; do I need it; how do I set it myself in this case?

Thanx!

naugtur Wrote:
-------------------------------------------------------
> I wish you (or anybody) could tell me where to look for info on what I'm missing in uBoot.

I can't tell you exactly what the environment variables should be, since I don't use that setup. But if you interrupt the u-boot sequence and do "printenv", you can compare the settings with those posted elsewhere on this forum and you should be able to recover.

Alll of your "errors" are perfectly safe.

The errors that look like this:

Warning: Bad CRC, using default environment
## Error: "ethaddr" not defined

Are caused when the script tries to read some existing variables from the environment. Since a new Dockstar has no environment, it will generate these errors.

The

ECC failed: 6

error is just part of the output of nanddump and can be ignored.

-- Jeff

Thank you for the clarification and for the installer as well. It's one of the nicest custom installers I've used.
Next thing I'll try is the NAND install.