public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Environment "image" tool
Date: Mon, 18 Jul 2011 10:47:51 -0700	[thread overview]
Message-ID: <4E2471C7.4050401@manoweb.com> (raw)
In-Reply-To: <CAJaTeTo9O-sCW5VDkz2Vx5WqMpdDsd2syKoqiLz3wWPg2GU0Kw@mail.gmail.com>

On 07/18/2011 10:38 AM, Mike Frysinger wrote:
> On Sat, Jul 16, 2011 at 19:18, Alessio Sangalli wrote:
>> Hi, is there a tool to create an "environemnt image" that I can flash to
>> my NAND?
> 
> tools/envcrc will output the binary env blob if you give it the
> --binary option.  but it does not take arbitrary env inputs.
> ./tools/envcrc --binary > env.bin

In the meanwhile I've written my own utility, but I do not understand
the "it does not take arbitrary env inputs".

> sounds like it might be a useful addition to tools/envcrc

I could not find it so I rewrote such functionality. If you want, I
could extract the relevant part of the code and send it to you. It's
quite trivial once I figured out how the U-Boot environment works.

>> Alternatively, is there a description of how the environment is read, my
>> U-Boot, so that I can write my own program to create such image?
> 
> <4 byte crc><var=value>\0[<var=value>\0]...\0

Yes, and the environment has a size specified by ENV_SIZE

bye
as

  reply	other threads:[~2011-07-18 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 23:18 [U-Boot] Environment "image" tool Alessio Sangalli
2011-07-16 23:31 ` Wolfgang Denk
2011-07-17  5:19   ` Alessio Sangalli
2011-07-18 16:22     ` Alessio Sangalli
2011-07-18 17:38 ` Mike Frysinger
2011-07-18 17:47   ` Alessio Sangalli [this message]
2011-07-18 17:59     ` Mike Frysinger
2011-07-18 19:52       ` Alessio Sangalli
2011-07-18 19:56         ` Mike Frysinger

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=4E2471C7.4050401@manoweb.com \
    --to=alesan@manoweb.com \
    --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