Devicetree
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Allow dtc to decompile device tre blobs in hexdump format
Date: Sun, 4 Apr 2010 00:30:15 -0600	[thread overview]
Message-ID: <y2vfa686aa41004032330xa771e6d5tdc8550fb9d451433@mail.gmail.com> (raw)
In-Reply-To: <20100404042232.GN8865@yookeroo>

On Sat, Apr 3, 2010 at 10:22 PM, David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> When debugging handoffs between different boot stages which use
> flattened device trees to communicate, it's often useful to dump the
> device tree blob being passed and use dtc to decompile it to something
> readable.  However, with some debugging tools it's possible to perform
> a hex memory dump of the device tree, but it's awkward or impossible
> to directly dump the memory as a binary blob.
>
> Obviously, it's quite straightforward to write a script or program to
> convert the hex dump back to binary, but I'm not aware of a standard
> tool to do so.
>
> This patch, therefore, adds a "hex" input format to dtc which allows
> it to directly (or almost so) parse and decompile a device tree blob
> supplied as a hex dump.  The input dtc expects in this mode must have
> no addresses or other extraneous text which could contain valid hex
> digits, however it will silently ignore any whitespace, punctuation,
> or other non-hex-digit formatting in the dump.  The dump must also
> either be either byte-by-byte, or display each hex number as
> big-endian (so "od -t x1" will produce suitable output on any system,
> but "od -t x2" will produce suitable output only when run on a
> big-endian system).
>
> Thus, if addresses and any header/footer are removed (usually easy to
> do in an editor), dtc will accept quite a wide range of likely hex
> dump formats.

Does it really make sense to build marshaling tools into dtc itself?
I think it would make more sense to keep transformation tools
independent.  ie. what if I have srecord format?  or intel hex?  A
trivial python or perl script would do the job for raw hex.  The
ascii2binary tool should also work.  Also, objcopy handles
srecord/ihex conversion beautifully.

I don't think it makes sense to be teaching dtc different
representations of the same dtb format.

g.

  reply	other threads:[~2010-04-04  6:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04  4:22 Allow dtc to decompile device tre blobs in hexdump format David Gibson
2010-04-04  6:30 ` Grant Likely [this message]
     [not found]   ` <y2vfa686aa41004032330xa771e6d5tdc8550fb9d451433-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-04 21:11     ` David Gibson
2010-04-04 22:01       ` Grant Likely

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=y2vfa686aa41004032330xa771e6d5tdc8550fb9d451433@mail.gmail.com \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    /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