On 2015-05-27, Rick Thomas wrote:
> On 05/26/15 13:35, Vagrant Cascadian wrote:
>> On 2015-05-26, Rick Thomas wrote:
>>> On May 26, 2015, at 12:44 PM, Rick Thomas <rbtho...@pobox.com> wrote:
>>>> On May 26, 2015, at 10:32 AM, Vagrant Cascadian <vagr...@aikidev.net> 
>>>> wrote:
>>>>> On 2015-05-26, Rick Thomas wrote:
...
>>> I installed the file in that URL as /etc/fw_env.config and when I run 
>>> fw_printenv, it says
>>>      Warning: Bad CRC, using default environment
>>> and prints only a few lines.  I was expecting to see the many-line printout 
>>> I get when
>>> I do “printenv” in u-boot.
>>>
>>> Is this expected behavior?
>> It is if you're running the default environment and haven't saved your
>> environment to the mmc (e.g. saveenv from the u-boot prompt).
>>
>>
>>> I’m running uboot version 2015.04+dfsg1-2
>> That's the right version...
>>
>>
>> In general I prefer to work with the default environment, as I'm often
>> testing new u-boot versions and want to make sure it continues to work
>> with the defaults, and it can be tricky to remember to reset the default
>> environment.
...
> Thanks for the explanation.  I wasn't aware that there were two 
> environments.  Is this explained somewhere?  I'd love to RTFM if I only 
> knew where the FM was!

I don't think of it as two environments... it's two different sources
for the environment settings. You have the built-in settings which is in
the binary (e.g. u-boot, fw_printenv), and you have the saved
settings stored on some media (e.g. SD, NAND). If the saved settings
aren't found, it uses the built-in defaults.


> I assume, if I do "saveenv" in uboot, that I'll  make the two 
> environments equal and see the same thing from fw_printenv in Linux as I 
> do from printenv in u-boot?  Is this correct?
>
> ...  I tried it and that's what happened.  Thanks!

So u-boot had a different set of defaults than fw_printenv, as this
particular u-boot is built specifically for the cubox-i and has an
environment appropriate to the cubox-i, while the defaults for
fw_printenv are built for the sandbox config, which is admittedly not a
very useful default, but there's no reasonable universal default...


I suppose I should document this in README.Debian...


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature

Reply via email to