uboot-envtools

[jherm]

Does anyone know what offset the U-Boot env config lives at for a GuruPlug?

I don't see anything obvious at 0xa0000 in my nanddump of /dev/mtd0.

[savenger]

Hi everyone,

I am trying to use your little tool, but it does not seem to work at my sheevaplug.
When I run

Code:

root@debian:/# sheeva-ubootenv-print > bla

I get the following error:

Code:

sheeva-nandrs-decode: too many errors in block #0 of chunk #0
sheeva-ubootenv-decode: environment must be 128Kb.

Am I doing something wrong?

[truehl]

Sorry for the dumb question: Where can I download this tool. I can't find a download link on the google code site!

Thx a lot,
Thomas

[b382f29]

Does anyone know what offset the U-Boot env config lives at for a GuruPlug?

I don't see anything obvious at 0xa0000 in my nanddump of /dev/mtd0.

# for Marvell GuruPlug ServerPlus
# (in /proc/cpuinfo:
#  Hardware     : Marvell Plug2L Reference Board)

# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
/dev/mtd0                      0x40000          0x20000       0x20000

[truehl]

Sorry, is there noone to answer that simple question?

Sorry for the dumb question: Where can I download this tool. I can't find a download link on the google code site!
Thx a lot,
Thomas

[firehawk]

Hi,

you can simply install the package uboot-envtools on any debian/ubuntu.
Check http://packages.debian.org/lenny/uboot-envtools for further details. Including a link to the tool homepage.
It seems to be part of Das U-Boot: http://www.denx.de/wiki/U-Boot/WebHome.

FireHawk

[truehl]

Thx FireHawk I've installed the package with apt-get install uboot-envtools. That worked!

But I can't any hints how to handle this package now. I would like to read the settings from NAND, modify them and then write back. How to to that?

Greetings
Thomas

[e-squizo]

Sorry for the dumb question: Where can I download this tool. I can't find a download link on the google code site!

Sorry for the delay, I haven't been around here in a while. I haven't made a package yet... you must download the source and compile it yourself.

[e-squizo]

When I run

Code:

root@debian:/# sheeva-ubootenv-print > bla

I get the following error:

Code:

sheeva-nandrs-decode: too many errors in block #0 of chunk #0
sheeva-ubootenv-decode: environment must be 128Kb.

Is that a Sheeva or a Guru? I'm having the same trouble as you with my Gurus, but it works fine on my sheevas! It seems something has changed in the way the environment is being saved: altough u-boot itself is stored using 4-bit ECC, it stores the environment using 1-bit ECC, in the same partition, which seems really ugly. This means that you can read the memory that holds the environment from Linux just using dd (which you can't do when the data is stored with 4-bit ECC), but so far I have been unable to write the data back, it becomes garbled both with dd and with nandwrite -q -n -s 0xa0000 /dev/mtd0.

[b382f29]

Is that a Sheeva or a Guru? I'm having the same trouble as you with my Gurus, but it works fine on my sheevas!

Aehm, just look up a few posts... I posted the configl file needed for the envtools for the guruplug.
The offset as you can see is 0x40000 (not 0xa0000 as with the sheevaplug)

[cjm]

Looks like we got two threads in one

b382f29, you're referring to configuration files for the uboot-envtools package on Debian/Ubuntu.

e-squizo is talking about the tools he wrote some time ago for Sheevaplugs, sheeva-uboot-tools, and problems with the way the Guruplug stores the configuration data.

I guess the reason why the uboot-envtools are working with Guruplugs (they don't work on Sheevaplugs) is the same reason why e-squizo's tools stopped working with the Guruplugs:

• Sheevaplugs use 4-bit ECC for uboot and the configuration.
• Guruplugs use 4-bit ECC for uboot but 1-bit ECC for the configuration.

Thanks,
--Christian

[wergio]

e-squizo about the "too many errors in block #0 of chunk #0" problem

i think the problem is related to mtdpart mapping

in my system (original sheevaplug with mainline kernel in nand) i've got the same problem

if I do:

Code:

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00400000 00020000 "uImage"
mtd1: 1fb00000 00020000 "rootfs"

mtd0 should be "uboot" to work, right?

I think my problem is related to "bootargs" parameter in u-boot

Code:

rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.1.9:192.168.1.4:192.168.1.4:255.255.255.0:DB88FXX81:eth0:none

but i must have 3 mtdparts: "uboot", "uImage", "rootfs", right?

any ideas how to correct this? thanks

[wergio]

SOLVED "too many errors in block #0 of chunk #0" problem:

as I suspected was mtdpart mapping related:

this was my bootargs setting in uboot

Code:

rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) root=/dev/mtdblock1 rw

mtd partition was speficied in uboot and the "u-boot" mtdpart was absent

the solution is to completly remove the mtdparts option from bootargs

IMPORTANT: if you do that you must speficy root=/dev/mtdblock2  because now rootfs is the third part:

Code:

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "root"

[Julf]

Unfortunately I have the same problem on a sheevaplug:

Code:

# sheeva-ubootenv-print
sheeva-nandrs-decode: too many errors in block #0 of chunk #0
sheeva-ubootenv-decode: environment must be 128Kb.

Due to an apparentlly broken USB port, I do not have access to the normal uboot console, so was hoping the sheeva-ubootenv commands would allow me to update the sheevaplug without console access.

[netter]

SOLVED "too many errors in block #0 of chunk #0" problem:

as I suspected was mtdpart mapping related:

this was my bootargs setting in uboot

Code:

rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) root=/dev/mtdblock1 rw

mtd partition was speficied in uboot and the "u-boot" mtdpart was absent

the solution is to completly remove the mtdparts option from bootargs

IMPORTANT: if you do that you must speficy root=/dev/mtdblock2  because now rootfs is the third part:

Code:

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "root"

I have a tonido plug and I am looking to configure fw_env.config from the info from "cat /proc/mtd". I get the same info that you get:

mtd0 00100000 00020000 "u-boot"
mtd1 00400000 00020000 "uImage"
mtd2 1fb00000 0020000 "root"

so how do I convert these into a fw_env.config file? Can you post yours?