From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Mon, 29 Jun 2009 15:03:32 -0400 Subject: [U-Boot] Trouble "booting using board info" In-Reply-To: <97dd5fd20906291137h4ebe6856kcd01598cca1134f7@mail.gmail.com> References: <4A42612E.4050807@shoppertrak.com> <4A439BC6.8070404@shoppertrak.com> <4A43AD42.8000601@shoppertrak.com> <97dd5fd20906260659r79d40562mb92a896c86878c6e@mail.gmail.com> <97dd5fd20906291137h4ebe6856kcd01598cca1134f7@mail.gmail.com> Message-ID: <4A491004.8060205@ge.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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