From: Manuel Sahm <Manuel.Sahm@feig.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] make env
Date: Wed, 02 Apr 2008 13:18:18 +0200 [thread overview]
Message-ID: <47F36B7A.9080104@feig.de> (raw)
In-Reply-To: <20080402103950.98436243AB@gemini.denx.de>
Hello,
how does uboot handle this flag byte ? (i I use redundant nand)
What initial value must this flag have?
Same value for enviroment1 and enviroment2 ?
If I make a "saveenv" which env. is used, and what values are then
written to the NAND flash to set it as aktiv/deactive ?
For example:
In Linux I want to write my own Enviroment to the redundant Env: What
must be the value of the flag byte to set this redundant enviroment
actik, so that UBoot will use this one ?
And: Which value do I have to write tho the other "old" enviroment in
NAND flash, so that this one becomes deactive ?
Thank you very much
Manuel Sahm
Wolfgang Denk schrieb:
> Dear Manuel,
>
> in message <47F3528A.3000202@feig.de> you wrote:
>
>> My problem the structure of the enviroment:
>> If I understand:
>> 4 byte crc; 1 byte flags, 0x20000-5 byte data.
>>
>
> Correct - the flag byte is only present if you use redundant
> environment.
>
>
>> The CRC is over the data bytes,( not the flags byte included) , right ??
>>
>
> Correct. That's because the flasg byte indicates the state of the
> environment copy (current -> bit = 1, or obsolete -> bit = 0). It
> relies on the feature of NOR flash that you can always program '1'
> bits to '0', even single bits in a single byte.
>
>
>> What about the flag byte, which values should I have to write here ?
>>
>
> See above. But you might have problems doing such a thing on NAND
> storage.
>
> Best regards,
>
> Wolfgang Denk
>
>
--
Freundliche Gr??e / Best regards
Manuel Sahm
Research & Development
FEIG ELECTRONIC GmbH
Lange Stra?e 4
35781 Weilburg
Germany
Tel.: +49 (0)6471-3109.492
Fax.: +49 (0)6471-3109.99
email: manuel.sahm at feig.de
internet: http://www.feig.de
------------------------------------------------------------------------
Amtsgericht Limburg HRB 3178
Gesch?ftsf?hrer: Dipl.-Ing. Wolfgang Feig
------------------------------------------------------------------------
------------------------------------------------------------------------
Diese Email (eingeschlossen die Anhaenge) unterliegt Urheberrecht, die
Informationen sind vertraulich und rechtswirksam privilegiert. Der
Gebrauch dieser Email oder der Anhaenge von einem anderen als den
Adressaten ist nicht gestattet und unrechtmaessig.
This email (including any attachments) is subject to copyright, the
information in it is confidential, and it is legally privileged. Use of
this email or of any information in it other than by the addressee is
unauthorised and unlawful.
------------------------------------------------------------------------
next prev parent reply other threads:[~2008-04-02 11:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 15:57 [U-Boot-Users] make env Manuel Sahm
2008-03-20 16:04 ` Wolfgang Denk
2008-03-20 17:56 ` Ladislav Michl
2008-03-20 20:02 ` Wolfgang Denk
2008-03-20 20:11 ` Ladislav Michl
2008-03-20 21:27 ` Wolfgang Denk
2008-03-20 21:33 ` Ladislav Michl
2008-03-25 12:56 ` Manuel Sahm
2008-03-25 13:36 ` Markus Klotzbücher
2008-03-25 16:19 ` Manuel Sahm
2008-03-25 17:04 ` Markus Klotzbücher
2008-03-25 20:11 ` Wolfgang Denk
2008-04-02 9:31 ` Manuel Sahm
2008-04-02 10:39 ` Wolfgang Denk
2008-04-02 11:18 ` Manuel Sahm [this message]
2008-04-02 14:33 ` Wolfgang Denk
2008-04-06 17:37 ` Markus Klotzbücher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47F36B7A.9080104@feig.de \
--to=manuel.sahm@feig.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox