From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Does ft_dump_blob() work for anyone?
Date: Tue, 23 Jan 2007 11:40:03 -0500 [thread overview]
Message-ID: <45B63A63.6030108@smiths-aerospace.com> (raw)
In-Reply-To: <45B6335B.9040201@freescale.com>
Timur Tabi wrote:
> I'm trying to debug some problems with ft_setup(), and when I call
> ft_dump_blob(), I get output like this:
>
> recieved oftree
> / {
> model = [00 00 00 00 4d 50 43 38 33 34 39 45 4d];
> ** Unknown tag 0x00000000 at 0xfd9d05c
> final OF-tree
> /memreserve/ 1 0;
> / {
> model = [00 00 00 00 4d 50 43 38 33 34 39 45 4d];
> ** Unknown tag 0x00000000 at 0xfd9d06c
> /memreserve/ 1 0;
> / {
> model = [00 00 00 00 4d 50 43 38 33 34 39 45 4d];
> ** Unknown tag 0x00000000 at 0xfd9d06c
>
> Obviously, it's hard to debug OF code without this function working. I believe
> the bug is somewhere in this code:
>
> sz = be32_to_cpu(*p++);
> s = (const char *)p_strings + be32_to_cpu(*p++);
> t = (const char *)p;
> p = (const u32 *)_ALIGN((unsigned long)p + sz, 4);
>
>
> Notice, for instance, the 'model' node, how it displays 4 zeros first.
> Obviously, the value of 't' above is incorrect.
>
> Unfortunately, I don't know the binary layout of the DTB, so this will take me a
> while to debug. I was just wondering if anyone else is seeing these problems.
It worked for me 2006-10-31
<http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/24664>
I have not been using it lately, so I cannot vouch for it still working.
You may also want to double-check your dtb version, I was using
version 16 when it worked.
gvb
next prev parent reply other threads:[~2007-01-23 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 16:10 [U-Boot-Users] Does ft_dump_blob() work for anyone? Timur Tabi
2007-01-23 16:40 ` Jerry Van Baren [this message]
2007-01-23 17:02 ` Timur Tabi
2007-01-23 17:06 ` Jon Loeliger
2007-01-23 16:42 ` Ben Warren
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=45B63A63.6030108@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.