public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: James Chargin <jimccrown@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Variable content dump to memory
Date: Thu, 24 Mar 2016 10:51:21 -0700	[thread overview]
Message-ID: <56F42919.1060302@gmail.com> (raw)
In-Reply-To: <CAH=tA9E_TH9QbesdOwfY1JAOYAN6_3mZbF_Z_rX30EfMe2260w@mail.gmail.com>


On 03/24/2016 03:30 AM, Nicolae Rosia wrote:
> Hello,
>
> I'm trying to write the contents of a variable to a file using ext4write
> but it requires a memory address as input.
> Is there an easy way to get the contents of a variable to a particular mem
> address?

You weren't completely specific about your needs, but assuming you are 
wanting to write a U-Boot environment variable to memory, try something like

=> # set up a test value
=> setenv var 12345678
=> printenv var
var=12345678
=>
=> # do the actual write
=> mw.l 80020000 $var 1
=>
=> # observe memory was set
=> md.l 8001fff0 c
8001fff0: 67ffedc4 dbc98df5 8e71cdd4 628fcacd    ...g......q....b
80020000: 12345678 a2fe8db5 df34c767 636dbd37    xV4.....g.4.7.mc
80020010: 375dfdcb fde86ca2 3f273cdf 1fe951f9    ..]7.l...<'?.Q..

Also, "help mw".

This was done on something similar to beaglebone x15. You will need to 
use memory addresses that are valid for your target system.

Jim

>
> Best regards,
> Nicolae
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>

-- 
Jim Chargin
AJA Video Systems                       jimc at aja.com
(530) 271-3334                          http://www.aja.com

  reply	other threads:[~2016-03-24 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 10:30 [U-Boot] Variable content dump to memory Nicolae Rosia
2016-03-24 17:51 ` James Chargin [this message]
2016-03-25  9:12   ` Nicolae Rosia
2016-03-25 15:14     ` James Chargin

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=56F42919.1060302@gmail.com \
    --to=jimccrown@gmail.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