Re: [U-Boot] call env print from uboot environment

2013-01-31 Thread Rommel Custodio
Dear Wolfgang, Wolfgang Denk 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 ___ U-Boot mailing list U-Boot@lists.denx.de http://lis

Re: [U-Boot] call env print from uboot environment

2013-01-31 Thread Wolfgang Denk
Dear Rommel Custodio, In message you wrote: > Dear Wolfgang, > > Wolfgang Denk denx.de> writes: > > > > > > What am I doing wrong. > > > > Try instead: > > > > env import -b 2005 > Skipping the CRC ... maybe "2004" is the correct address. No. As I mentioned before, this enviro

Re: [U-Boot] call env print from uboot environment

2013-01-31 Thread Rommel Custodio
Dear Wolfgang, Wolfgang Denk denx.de> writes: > > > What am I doing wrong. > > Try instead: > > env import -b 2005 Skipping the CRC ... maybe "2004" is the correct address. "env import -c 0x2000 0x200" if you want the CRC verified. All the best, _

Re: [U-Boot] call env print from uboot environment

2013-01-31 Thread 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: > 2000: 00 00 00 00 00 65 74 68 61 64 64 72 3d 33 61 3a.ethaddr=3a: > 2010: 31 66 3a 33 34 3a 30 38 3a 35 34 3a 35 34 00 741f:34:

[U-Boot] call env print from uboot environment

2013-01-31 Thread 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 0x2000. The environment uboot is compiled to load by default has one set of variables, but the environment loaded into ram by at91