public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexey Smishlayev <alexey@xtech2.lv>
To: u-boot@lists.denx.de
Subject: [U-Boot] Creating U-Boot env image
Date: Tue, 10 Dec 2013 14:32:22 +0200	[thread overview]
Message-ID: <52A709D6.6020708@xtech2.lv> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C4FD9B8A4@post.tritech.se>

Hello, Mats,

On 2013.12.10. 13:39, Mats K?rrman wrote:
> Hi Alexey,
>
> I can definitely see the use case in producing a complete flash image, e.g. for
> production use and maybe be able to select the env image from one of many
> depending on some factor.

Yes, the use case is exactly as you described.

> What you describe should definitely be possible. Are you sure that it's not
> something simple like a missmatch in env size?
I'm not sure, if that's not something simple, that's why I wrote to this 
list. I just don't know every little detail about using U-Boot.

> You could use U-Boots Linux fw_printenv tools and/or dd to read the flashed env
> image and perhaps compare it to an image saved by U-Boot to figure out what is
> going wrong.

That's what I've thought also - if I just dd the environment contents to 
a file, can I then use it as a valid image for production? That could be 
the most simple way to achieve what I want.

Best regards,
Alexey Smishlayev

  reply	other threads:[~2013-12-10 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 14:34 [U-Boot] Creating U-Boot env image Alexey Smishlayev
2013-12-09 20:12 ` Wolfgang Denk
2013-12-09 21:39   ` Alexey Smishlayev
2013-12-09 21:56     ` Stephen Warren
2013-12-10 11:39 ` Mats Kärrman
2013-12-10 12:32   ` Alexey Smishlayev [this message]
2013-12-10 13:33     ` Mats Kärrman
2013-12-10 13:36       ` Alexey Smishlayev
2013-12-11  9:59 ` Bo Shen

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=52A709D6.6020708@xtech2.lv \
    --to=alexey@xtech2.lv \
    --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