[U-Boot-Users] mpc83xx boot error

[U-Boot-Users] mpc83xx boot error

[Russell McGuire]

All,

I have downloaded the latest U-boot 1.3.0 dirty <a week old> and compiled it
up for a 8360E-MDS board.
I have downloaded the latest version of the DTC 1.0.0-ge1109207 today, and
compiled up a preconfigured dts file 
and burnt that into flash. Also I have downloaded denx's latest linux-git
tree 2.6.23.1 and configured it for said board.

However, when I try to boot Linux, I get an immediate error as follows:

> bootm $kerneladdr - $blobaddr
.. Bla bla standard printf.. 

Uncompressing the Kernel Image . OK
Booting using the fdt at 0xe0080000
Loading device tree to 0x007fe000, end 0x007ff432 . ERROR: fdt move failed -
must reset board to recover. Resetting the board.

I am coming at this from my experience with U-boot 1.1.2 and 1.1.6 and a 1
yr old version of the dtc compiler.
Are there new options, or less options that should be used with the dtc
compiler to avoid this error? 
I know before we had to fix the version of the blob, so perhaps I am
compiling the blob wrong? The dts file compiles fine with no warnings.

dtc -I dts -O dtb -f -V 0x10


Using this without -V 0x10 gives me a different error
dtc -I dts -O dtb -f

WARNING: could not create /chosen FDT_ERR_NOSPACE
ERROR: /chosen node create failed - must RESET the board to recover

Anybody have any ideas?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20071212/eb38ff1f/attachment.htm 

[U-Boot-Users] mpc83xx boot error

[Kim Phillips]

On Wed, 12 Dec 2007 15:17:20 -0800
"Russell McGuire" <rmcguire@videopresence.com> wrote:

> Are there new options, or less options that should be used with the dtc
> compiler to avoid this error? 

I use

dtc -I dts -O dtb  -R 8 -S 0x3000

Kim

[U-Boot-Users] mpc83xx boot error

[gvb.uboot]

Russell McGuire wrote:
> All,
> 
> I have downloaded the latest U-boot 1.3.0 dirty <a week old> and 
> compiled it up for a 8360E-MDS board.
> 
> I have downloaded the latest version of the DTC 1.0.0-ge1109207 today, 
> and compiled up a preconfigured dts file
> 
> and burnt that into flash. Also I have downloaded denx?s latest 
> linux-git tree 2.6.23.1 and configured it for said board.
> 
> However, when I try to boot Linux, I get an immediate error as follows:
> 
>>  bootm $kerneladdr - $blobaddr
> 
> ?. Bla bla standard printf??
> 
> Uncompressing the Kernel Image ? OK
> 
> Booting using the fdt at 0xe0080000
> 
> Loading device tree to 0x007fe000, end 0x007ff432 ? ERROR: fdt move 
> failed ? must reset board to recover. Resetting the board.
> 
> I am coming at this from my experience with U-boot 1.1.2 and 1.1.6 and a 
> 1 yr old version of the dtc compiler.
> 
> Are there new options, or less options that should be used with the dtc 
> compiler to avoid this error?
> 
> I know before we had to fix the version of the blob, so perhaps I am 
> compiling the blob wrong? The dts file compiles fine with no warnings.
> 
> dtc ?I dts ?O dtb ?f ?V 0x10
> 
> Using this without ?V 0x10 gives me a different error
> 
> dtc ?I dts ?O dtb -f
> 
> WARNING: could not create /chosen FDT_ERR_NOSPACE
> 
> ERROR: /chosen node create failed - must RESET the board to recover
> 
> Anybody have any ideas?

Hi Russell,

* You need to use version 17 (simply don't specify -V 0x10).
* As Kim mentioned, you need -S padding to allow extra space for the
     /chosen node.
* Since you burned the blob into flash, bootm has to relocate the blob
    to RAM.  This is what is giving you the "fdt move failed" error in
    your first example, it is moving the blob to 0x007fe000 - is this
    a valid address (seems like it should be)?  Perhaps it is simply
    because you didn't pad it?  Perhaps we let a bug slip in?

Good luck,
gvb

[U-Boot-Users] mpc83xx boot error

[gvb.uboot]

gvb.uboot wrote:
> Russell McGuire wrote:
>> All,
>>
>> I have downloaded the latest U-boot 1.3.0 dirty <a week old> and 
>> compiled it up for a 8360E-MDS board.
>>
>> I have downloaded the latest version of the DTC 1.0.0-ge1109207 today, 
>> and compiled up a preconfigured dts file
>>
>> and burnt that into flash. Also I have downloaded denx?s latest 
>> linux-git tree 2.6.23.1 and configured it for said board.
>>
>> However, when I try to boot Linux, I get an immediate error as follows:
>>
>>>  bootm $kerneladdr - $blobaddr
>> ?. Bla bla standard printf??
>>
>> Uncompressing the Kernel Image ? OK
>>
>> Booting using the fdt at 0xe0080000
>>
>> Loading device tree to 0x007fe000, end 0x007ff432 ? ERROR: fdt move 
>> failed ? must reset board to recover. Resetting the board.
>>
>> I am coming at this from my experience with U-boot 1.1.2 and 1.1.6 and a 
>> 1 yr old version of the dtc compiler.
>>
>> Are there new options, or less options that should be used with the dtc 
>> compiler to avoid this error?
>>
>> I know before we had to fix the version of the blob, so perhaps I am 
>> compiling the blob wrong? The dts file compiles fine with no warnings.
>>
>> dtc ?I dts ?O dtb ?f ?V 0x10
>>
>> Using this without ?V 0x10 gives me a different error
>>
>> dtc ?I dts ?O dtb -f
>>
>> WARNING: could not create /chosen FDT_ERR_NOSPACE
>>
>> ERROR: /chosen node create failed - must RESET the board to recover
>>
>> Anybody have any ideas?
> 
> Hi Russell,
> 
> * You need to use version 17 (simply don't specify -V 0x10).
> * As Kim mentioned, you need -S padding to allow extra space for the
>      /chosen node.
> * Since you burned the blob into flash, bootm has to relocate the blob
>     to RAM.  This is what is giving you the "fdt move failed" error in
>     your first example, it is moving the blob to 0x007fe000 - is this
>     a valid address (seems like it should be)?  Perhaps it is simply
>     because you didn't pad it?  Perhaps we let a bug slip in?
> 
> Good luck,
> gvb

Oops, I missed the -R 8 that Kim recommended (very correctly).  This 
makes more reserved map entries which is important as well as the -S 
extra space.

gvb

[U-Boot-Users] mpc83xx boot error

[Marc Leeman]

>> * You need to use version 17 (simply don't specify -V 0x10).
>> * As Kim mentioned, you need -S padding to allow extra space for the
>>      /chosen node.
>> * Since you burned the blob into flash, bootm has to relocate the blob
>>     to RAM.  This is what is giving you the "fdt move failed" error in
>>     your first example, it is moving the blob to 0x007fe000 - is this
>>     a valid address (seems like it should be)?  Perhaps it is simply
>>     because you didn't pad it?  Perhaps we let a bug slip in?
>>
> Oops, I missed the -R 8 that Kim recommended (very correctly).  This 
> makes more reserved map entries which is important as well as the -S 
> extra space.

I don't think this fully describes it, I just came across the same error
when porting from 1.3.1 to 1.3.2-rc2:

dtc -I dts -O dtb -S 0x3000 -R 8 

with dtc 1.1.0 

still gives the following when booting u-boot-1.3.2-rc2:

## Booting image at fe700000 ...
   Image Name:   Linux-2.6.24
   Created:      2008-02-25  15:38:37 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    930624 Bytes = 908.8 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using the fdt at 0xfefe0000
   Loading Device Tree to 007fe000, end 007ff4e1 ... OK
WARNING: could not create /chosen FDT_ERR_NOSPACE.
ERROR: /chosen node create failed - must RESET the board to recover.
Resetting the board.


-- 
  greetz, marc
You made me drink piss?
	Jool - Different Destinations
chiana 2.6.18-4-ixp4xx #1 Tue Mar 27 18:01:56 BST 2007 GNU/Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080228/d55f5132/attachment.pgp 

[U-Boot-Users] mpc83xx boot error

[Jerry Van Baren]

Marc Leeman wrote:
>>> * You need to use version 17 (simply don't specify -V 0x10).
>>> * As Kim mentioned, you need -S padding to allow extra space for the
>>>      /chosen node.
>>> * Since you burned the blob into flash, bootm has to relocate the blob
>>>     to RAM.  This is what is giving you the "fdt move failed" error in
>>>     your first example, it is moving the blob to 0x007fe000 - is this
>>>     a valid address (seems like it should be)?  Perhaps it is simply
>>>     because you didn't pad it?  Perhaps we let a bug slip in?
>>>
>> Oops, I missed the -R 8 that Kim recommended (very correctly).  This 
>> makes more reserved map entries which is important as well as the -S 
>> extra space.
> 
> I don't think this fully describes it, I just came across the same error
> when porting from 1.3.1 to 1.3.2-rc2:
> 
> dtc -I dts -O dtb -S 0x3000 -R 8 
> 
> with dtc 1.1.0 
> 
> still gives the following when booting u-boot-1.3.2-rc2:
> 
> ## Booting image at fe700000 ...
>    Image Name:   Linux-2.6.24
>    Created:      2008-02-25  15:38:37 UTC
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    930624 Bytes = 908.8 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
>    Booting using the fdt at 0xfefe0000
>    Loading Device Tree to 007fe000, end 007ff4e1 ... OK
> WARNING: could not create /chosen FDT_ERR_NOSPACE.
> ERROR: /chosen node create failed - must RESET the board to recover.
> Resetting the board.

Hi Marc,

Hmmm, this is an interesting line:
 >    Loading Device Tree to 007fe000, end 007ff4e1 ... OK
I have not looked who generates this printout, but it seems to indicate 
the fdt is 0x14e1 in length.

Is the "interesting line" indicating that the blob got moved *and 
truncated*?  If it is being truncated, that would be why it runs out of 
space creating the /chosen node.

What sort of image/combination are you booting?  I'm booting a separate 
linux image, fdt blob, and RAM disk and my boot sequence looks 
different, including not having the "Loading Device Tree..." line.

=> tftp $ramdiskaddr $ramdiskfile ; tftp $fdtaddr $fdtfile ; tftp 
$loadaddr $bootfile
UEC: PHY is Marvell 88E11x1 (1410cc2)
FSL UEC0: Full Duplex
switching to rgmii 100
FSL UEC0: Speed 100BT
FSL UEC0: Link is up
Using FSL UEC0 device
TFTP from server 192.168.47.8; our IP address is 192.168.47.214
Filename 'mpc8360emds/uRamdisk'.
Load address: 0x1000000
Loading: T #################################################################
          ########################################
done
Bytes transferred = 1531127 (175cf7 hex)
Using FSL UEC0 device
TFTP from server 192.168.47.8; our IP address is 192.168.47.214
Filename 'mpc8360emds/mpc836x_mds.dtb'.
Load address: 0x400000
Loading: #
done
Bytes transferred = 12288 (3000 hex)
Using FSL UEC0 device
TFTP from server 192.168.47.8; our IP address is 192.168.47.214
Filename 'mpc8360emds/uImage'.
Load address: 0x200000
Loading: #################################################################
          ##########################
done
Bytes transferred = 1329289 (144889 hex)
=> bootm $loadaddr $ramdiskaddr $fdtaddr
## Booting image at 00200000 ...
    Image Name:   Linux-2.6.25-rc3-00001-g5fb74e4-
    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
    Data Size:    1329225 Bytes =  1.3 MB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 01000000 ...
    Image Name:   Simple Embedded Linux Framework
    Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
    Data Size:    1531063 Bytes =  1.5 MB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
    Booting using the fdt at 0x400000
    Loading Ramdisk to 0fe2b000, end 0ffa0cb7 ... OK
Using MPC836x MDS machine description
Linux version 2.6.25-rc3-00001-g5fb74e4-dirty (vanbaren at dellserver) (gcc 
version
  4.0.0 (DENX ELDK 4.1 4.0.0)) #1 Mon Feb 25 20:38:46 EST 2008
Found initrd at 0xcfe2b000:0xcffa0cb7
console [udbg0] enabled
setup_arch: bootmem
mpc836x_mds_setup_arch()
:
[snip]
:
root:~>


Best regards,
gvb

[U-Boot-Users] mpc83xx boot error

[Marc Leeman]

> I have not looked who generates this printout, but it seems to indicate 
> the fdt is 0x14e1 in length.

My fault: I was loading the wrong dtb file while developing. U-Boot was
loading the dtb from the upgrade location, not from the factory location
as I assumed it was doing.

tnx.

-- 
  greetz, marc
All right, one quick trip to the pharmacy coming up. Out the door,
turn left at the creature.
	Crichton - Bone To Be Wild
chiana 2.6.18-4-ixp4xx #1 Tue Mar 27 18:01:56 BST 2007 GNU/Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080228/72ea0dc6/attachment.pgp