From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Trouble "booting using board info"
Date: Mon, 29 Jun 2009 15:03:32 -0400 [thread overview]
Message-ID: <4A491004.8060205@ge.com> (raw)
In-Reply-To: <97dd5fd20906291137h4ebe6856kcd01598cca1134f7@mail.gmail.com>
Mikhail Zaturenskiy wrote:
> Is it possible to look at a post-fixup device tree in u-boot? It looks
> like u-boot is not updating my dts with the values for my RAM, cpu
> frequency, etc. before loading the kernel.
>
> Is there any obvious reason for this? Am I missing a #define of some sort?
Hi Mikhail,
The board fixup is a board-specific thing. Are you doing that in your
board configuration?
If you have CONFIG_OF_BOARD_SETUP defined (if you don't that probably is
the answer to your missing #define question), you can run
fdt boardsetup
and then
fdt print /
to see what the fixed up tree looks like.
You can also run the bootm command step-by-step (some steps may not
apply to your board)...
bootm start
bootm loados
bootm ramdisk
bootm fdt
bootm bdt
bootm cmdline
bootm prep
Print out the tree:
fdt print /
(last step is...)
bootm go
Best regards,
gvb
next prev parent reply other threads:[~2009-06-29 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:23 [U-Boot] Trouble "booting using board info" Mikhail Zaturenskiy
2009-06-25 11:40 ` Detlev Zundel
2009-06-25 15:46 ` Mikhail Zaturenskiy
2009-06-25 16:11 ` Detlev Zundel
2009-06-25 17:00 ` Mikhail Zaturenskiy
2009-06-26 11:58 ` Detlev Zundel
2009-06-26 13:59 ` Mikhail Zaturenskiy
2009-06-29 18:37 ` Mikhail Zaturenskiy
2009-06-29 19:03 ` Jerry Van Baren [this message]
2009-06-29 20:19 ` Mikhail Zaturenskiy
2009-06-30 18:30 ` Mikhail Zaturenskiy
2009-06-30 18:38 ` Mikhail Zaturenskiy
2009-06-30 18:51 ` Jerry Van Baren
[not found] ` <4A42FBC2.8050406@tataelxsi.co.in>
2009-06-25 14:23 ` [U-Boot] "Bad Data CRC" after ramdisk size increase Mikhail Zaturenskiy
2009-06-25 14:36 ` Detlev Zundel
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=4A491004.8060205@ge.com \
--to=gerald.vanbaren@ge.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.