Hi samweber,

Please post your setting so I can re-construct the error you get, I just got a new uboot that might fix this console issue but want to validate that it fixes it before I post it.

Hi mgillespie,

If you had no issues with the current uboot (3.4.19) you are using I suggest you stick with it since the 3.4.24 has not passed QA yet.
The last uboot I uploaded had fixed the nandEcc issue that caused Linux not to run (at least this is what I experienced).

A new uboot version fixes some more problems with uboot environment bugs:
http://plugcomputer.org/plugforum/index.php?topic=921.msg5755#msg5755

Hi Tobi,

I have yet used openOcd v0.3.0 and hae never seen such an error, to my understanding it is an error comming from the host PC and you might need to add the -work-area-virt openOcd configure options.

Try editing the sheevaplug-installer-v1.0/uboot/openocd/config/board/sheevaplug.cfg file:
from to 

A bug was found in the 3.4.23 that in some cases caused the nandEcc environment to become NULL and a new environment variable "bit" was introduced.

Hi,

The nandEcc bug found in last uboot version I uploaded: http://plugcomputer.org/plugforum/index.php?topic=921.msg5698#msg5698

this fixed with this image, please use it with your installer with the attached

It looks like the uImage was not burned to nand flash, can you post the installer/console print ?
Describe host PC hw/OS and setup more so we can help you

Hi samweber,

The reason I asked about nandEcc is that I noticed that this env gets a null value and a new env appears: bit.
So to finish my installation I had to set he nandEcc=1bit.
In your case I see the same phenomenon but the uboot did load the uImage from nand and manage to run it.
So basically it looks OK, the next step would be setting the right uboot env to make kernel boot from rootfs on SD.

Please look in the installer (aplug-installer-v1.0\uboot\uboot-env\uboot-mmc-custom.txt ) for reference regarding uboot settings.

I will try to understand the nandEcc issue.

can you try re-flash the uImage to 0x100000 (from uboot) while the DOK (with uimage on it) is connected to the plug:
>usb start
>fatload usb 0 0x00800000 uImage
>nand erase clean 0x00100000 0x00400000
>nand write.e 0x00800000 0x00100000 0x00400000

Hi badcam,

I just looked at your post and noticed that uImage was not found on the DOK:

So your first problem is first to get the uboot to read the uImage from the USB DOK and flash it to the NAND first, can you try other DOK if the one you used fails.

Format it to FAT32 or FAT16 and make sure the uImage from the installer is in the root directory

what is the value of nandEcc?

Hi samweber,

OK, so now it looks like this bug is fixed, please try it out.

-rooster

  strange bug, I managed to get it also.
I will forward it and get it fixed for next version, in the meantime you can workaround this with SDHC card, I tried it with Patriot 8GB C6 SDHC card:

Since there was a bug in 3.4.19 regarding environment console, you should ask uboot to override the Env parameters when upgrading to new uboot (3.4.23) during the bubt procedure.

You can also do it by entering resetenv after uboot upgrade and perform reset afterwards.
Before resetting your uboot Env, save them as text somewhere...

Do you have a 32bit PC? I would try it out.
I never seen this kinda error from the installer, you can aloso try to build openocd version 2.0 (which was used with the installer).