All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FDT: missing stdout-path
Date: Thu, 03 Apr 2008 19:17:09 -0400	[thread overview]
Message-ID: <47F56575.9080606@gmail.com> (raw)
In-Reply-To: <20080403160044.GA7667@ld0162-tx32.am.freescale.net>

Scott Wood wrote:
> On Thu, Apr 03, 2008 at 11:56:08AM -0400, Bill Cook wrote:
>> 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?
> 
> You probably need serial0, serial1, etc. aliases.  See the device trees
> in head-of-tree Linux.
> 
> -Scott

...and that error message could stand improvement to give the poor user 
a better clue that he is missing the /aliases node or /aliases/serial0 
property.

The current error message reminds me of the "Fog in Seattle" joke
   <http://home.earthlink.net/~devinc/fogin.htm>

gvb

      reply	other threads:[~2008-04-03 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 15:56 [U-Boot-Users] FDT: missing stdout-path Bill Cook
2008-04-03 16:00 ` Scott Wood
2008-04-03 23:17   ` Jerry Van Baren [this message]

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=47F56575.9080606@gmail.com \
    --to=gvb.uboot@gmail.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.