On Jan 5, 2016, at 10:14 AM, Vagrant Cascadian <vagr...@aikidev.net> wrote:
> On 2016-01-05, Rick Thomas wrote:
>> When running Debian (Sid, in this case) and I do “fw_printenv” it
>> gives an error message about a bad CRC and using default environment
…
> When you boot, does u-boot print a warning about using the default
> environment?
>
> If there is no default environment saved, fw_printenv will just show the
> compiled in defaults for fw_printenv, which will almost certainly be
> different than the compiled-in defaults for u-boot, which is built for a
> particular platform.
>
>
>>> Marvell>> saveenv
>>> Saving Environment to NAND...
>>> Erasing NAND...
>>> ^MErasing at 0x60000 -- 100% complete.
>>> Writing to NAND... OK
>>> Marvell>>
>>
>> So I presume the “Device offset” in /etc/fw_env.config is correct. Or is
>> there something I don’t know about going on?
>
> After you've run saveenv from u-boot, does fw_printenv still show a
> different environment? Does u-boot print a warning at boot about using
> the default environment at boot after using saveenv?
Thanks for the quick response!
u-boot does not mention default environment anywhere as far as I can see.
And, yes, fw_printenv behavior is the same before and after doing saveenv in
u-boot.
The only thing I see that looks like a warning is a mention of it not using
“generic board”.
Here’s a log from a recent (successful) boot of the machine…
> Marvell>> reset
> resetting ...
>
>
> U-Boot 2014.10+dfsg1-5 (Apr 07 2015 - 21:57:04)
> Marvell-Sheevaplug
>
> SoC: Kirkwood 88F6281_A0
> DRAM: 512 MiB
> WARNING: Caches not enabled
> NAND: 512 MiB
> MMC: MVEBU_MMC: 0
> In: serial
> Out: serial
> Err: serial
> Net: egiga0
> 88E1116 Initialized on egiga0
> Warning: Your board does not use generic board. Please read
> doc/README.generic-board and take action. Boards not
> upgraded by the late 2014 may break or be removed.
> Hit any key to stop autoboot: 0
> 2009340 bytes read in 835 ms (2.3 MiB/s)
> 12872333 bytes read in 1771 ms (6.9 MiB/s)
> ## Booting kernel from Legacy Image at 00800000 ...
> Image Name: kernel 4.3.0-1-kirkwood
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2009276 Bytes = 1.9 MiB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at 01100000 ...
> Image Name: ramdisk 4.3.0-1-kirkwood
> Image Type: ARM Linux RAMDisk Image (uncompressed)
> Data Size: 12872269 Bytes = 12.3 MiB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> [ 0.000000] Booting Linux on physical CPU 0x0
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Initializing cgroup subsys cpuacct
> [ 0.000000] Linux version 4.3.0-1-kirkwood
> (debian-ker...@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-10) ) #1
> Debian 4.3.3-5 (2016-01-04)
> [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE),
> cr=0005397f
> [ 0.000000] CPU: VIVT data cache, VIVT instruction cache
> [ 0.000000] Machine model: Globalscale Technologies SheevaPlug
> [ 0.000000] Memory policy: Data cache writeback
> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total
> pages: 130048
> [ 0.000000] Kernel command line: console=ttyS0,115200
> [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
> [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> [ 0.000000] Memory: 501092K/524288K available (3720K kernel code, 328K
> rwdata, 1384K rodata, 268K init, 292K bas, 23196K reserved, 0K cma-reserved,
> 0K highmem)
Any thoughts?
Rick
