public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] libfdt problem when loading device tree
Date: Thu, 13 Dec 2007 10:34:15 -0600	[thread overview]
Message-ID: <7295C709-91F2-4184-8C7F-9ED682B8232D@kernel.crashing.org> (raw)
In-Reply-To: <1197563083.8607.19.camel@gentoo-jocke.transmode.se>


On Dec 13, 2007, at 10:24 AM, Joakim Tjernlund wrote:

> I get this when I try to boot my board:
> ## Booting image at 00200000 ...
>   Image Name:   oskernel02a:p1a:99
>   Created:      2007-12-13   9:59:43 UTC
>   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>   Data Size:    1238992 Bytes =  1.2 MB
>   Load Address: 00000000
>   Entry Point:  00000000
>   Verifying Checksum ... OK
>   Uncompressing Kernel Image ... OK
>   Loading Device Tree to 007fe000, end 007ff6f9 ... OK
> WARNING: could not create /bd_t FDT_ERR_NOSPACE.
> fdt_bd_t: FDT_ERR_NOSPACE
> ERROR: /bd_t node create failed - must RESET the board to recover.
> Resetting the board.
>
> I have tried different combinations of -S and -R options to dtc,
> but nothing helps:
> dtc -S 2000 -R 2000 -f of-tmcu.dts -O asm > of-tmcu.S
>
> If I remove the chosen node from my dts file, I get the error when
> libfdt tries to create a chosen node.
>
> I am using dtc 1.0.0 and u-boot 1.3.1

How big is the .dtb if you don't specify -S?  The -R should only be  
something like 8.

- k

  reply	other threads:[~2007-12-13 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 16:24 [U-Boot-Users] libfdt problem when loading device tree Joakim Tjernlund
2007-12-13 16:34 ` Kumar Gala [this message]
2007-12-13 16:39   ` Joakim Tjernlund
2007-12-13 18:59   ` Jerry Van Baren
2007-12-13 22:11     ` Joakim Tjernlund
2007-12-13 16:46 ` Jerry Van Baren
2007-12-13 17:00   ` Joakim Tjernlund
2007-12-13 17:07   ` Joakim Tjernlund
2007-12-13 17:16     ` Joakim Tjernlund
2007-12-13 18:03     ` Jerry Van Baren
2007-12-13 18:17       ` Joakim Tjernlund

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=7295C709-91F2-4184-8C7F-9ED682B8232D@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --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