[U-Boot] call env print from uboot environment

[U-Boot] call env print from uboot environment

[John Stile]

I am finally on uboot-2013.01.
I having issue using: env import

I have at91bootstrap reading an uboot environment from an address
location in NAND to RAM address 0x20000000.

The environment uboot is compiled to load by default has one set of
variables, but the environment loaded into ram by  at91bootstrap is
different.

I hope to see the change by using: env print.

[U-Boot] call env print from uboot environment

[Wolfgang Denk]

Dear John Stile,

In message <1359663873.7974.308.camel@genx> you wrote:
>
> I see the new environment in memory (which includes the CRC).
> Example:
> 20000000: 00 00 00 00 00 65 74 68 61 64 64 72 3d 33 61 3a    .....ethaddr=3a:
> 20000010: 31 66 3a 33 34 3a 30 38 3a 35 34 3a 35 34 00 74    1f:34:08:54:54.t
> 20000020: 69 6d 65 73 74 61 6d 70 3d 31 32 33 35 00 62 6f    imestamp=1235.bo
> 20000030: 6f 74 64 65 6c 61 79 3d 33 00 62 61 75 64 72 61    otdelay=3.baudra
> ...
> 200001f0: 30 20 30 78 30 30 32 30 30 30 30 30 20 30 78 30    0 0x00200000 0x0

Your CRC is 0x00000000 - this looks bogus to me.

And you have set up for redundant environment, and the flag is 0x00.

Where exactly is this data coming from?  It does not appear to hav
ebeen stored by U-Boot...

> I try to load the environment from RAM:
> U-Boot> env import -t 0x20000000 0x200

"-t" means text format.  This is not what you have.

> What am I doing wrong.

Try instead:

	env import -b 20000005

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Substitute "damn" every time you're inclined to write "very"; your
editor will delete it and the writing will be just as it should be.
                - Mark Twain

[U-Boot] call env print from uboot environment

[Rommel Custodio]

Dear Wolfgang,

Wolfgang Denk <wd <at> denx.de> writes:

> 
> > What am I doing wrong.
> 
> Try instead:
> 
> 	env import -b 20000005
Skipping the CRC ... maybe "20000004" is the correct address.

"env import -c 0x20000000 0x200" if you want the CRC verified.


All the best,

[U-Boot] call env print from uboot environment

[Wolfgang Denk]

Dear Rommel Custodio,

In message <loom.20130201T035118-798@post.gmane.org> you wrote:
> Dear Wolfgang,
> 
> Wolfgang Denk <wd <at> denx.de> writes:
> 
> > 
> > > What am I doing wrong.
> > 
> > Try instead:
> > 
> > 	env import -b 20000005
> Skipping the CRC ... maybe "20000004" is the correct address.

No.  As I mentioned before, this environment was set up for redundant
env, and has a flag byte after the CRC. So you must start at offset 5.

> "env import -c 0x20000000 0x200" if you want the CRC verified.

Which will not work, as there is no valid CRC in his environment.

You should actually read what I wrote before trying to correct me.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A good marriage would be between a blind wife and deaf husband.
                                               -- Michel de Montaigne

[U-Boot] call env print from uboot environment

[Rommel Custodio]

Dear Wolfgang,

Wolfgang Denk <wd <at> denx.de> writes:

> 
> Dear Rommel Custodio,
> 
:
:
> 
> You should actually read what I wrote before trying to correct me.
Apologies kind sir. 

All the best,
Rommel