From: Bill Cook <cook@isgchips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FDT: missing stdout-path
Date: Thu, 3 Apr 2008 11:56:08 -0400 [thread overview]
Message-ID: <HAELLJHFKFMKJBAJIOFGAENDDDAA.cook@isgchips.com> (raw)
Hello experts,
With U-Boot-1.3.2 and a Freescale MPC8313ERDB,
I'm getting this message from bootm
...
Booting using the fdt at 0xfc700000
Loading Ramdisk to 07ca1000, end 07f419bf ... OK
Loading Device Tree to 007fc000, end 007fefff ... OK
WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND.
ERROR: /chosen node create failed - must RESET the board to recover.
Resetting the board.
U-Boot 1.3.2 (Apr 2 2008 - 10:02:55) MPC83XX
Reset Status: Software Hard, External/Internal Soft, External/Internal
Hard
CPU: e300c3, MPC8313E, Rev: 10 at 333.333 MHz, CSB: 166 MHz
...
What do I need to add to DTS file or u-boot environment to make this go?
Thanks
Bill Cook
_____________________________
cook at ISGchips.com
Imaging Solutions Group of NY
1387 Fairport Rd., Suite 890
Fairport, NY 14450
http://ISGcameras.com
next reply other threads:[~2008-04-03 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 15:56 Bill Cook [this message]
2008-04-03 16:00 ` [U-Boot-Users] FDT: missing stdout-path Scott Wood
2008-04-03 23:17 ` Jerry Van Baren
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=HAELLJHFKFMKJBAJIOFGAENDDDAA.cook@isgchips.com \
--to=cook@isgchips.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