Skip to contentSkip to conversation

FIT-image with fdt doesn't work]

U-Boot Jon Loeliger 1 participant 1 message Sep 30, 2008

lore
Share & tools
lore
#0 lore raw

Gah. List foo. Sorry. -- jdl

-------- Forwarded Message --------
From: Jon Loeliger <[email protected]>
To: Simon Pasch <[email protected]>
Cc: u-boot-users <[email protected]>
Subject: Re: [U-Boot-Users] FIT-image with fdt doesn't work
Date: Tue, 30 Sep 2008 10:37:50 -0500

Quoted 2 lines · Simon Pasch

3.) create a flat device tree blob (using dtc 1.2.0):
dtc -b 0 -V 17 -R 4 -S 0x3000 -I dts -O dtb -f devicetree.dts > target.dtb

The -V 17 is the current default, so the option isn't needed. The -S 0x3000 may not be enough, and is really obsoleted but the -p <pad-value> option too. Try, oh, -p 0x1000 instead.

If you have a large DTS or resulting DTB file, it might lead to problems like this:

Quoted 36 lines

7.) try to boot it:
=> bootm
## Booting kernel from FIT Image at 00700000 ...
Using 'conf at 1' configuration
Trying 'kernel at 1' kernel subimage

     Description:  Vanilla Linux kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x007000ec
     Data Size:    4052683 Bytes =  3.9 MB
     Architecture: PowerPC
     OS:           Linux
     Load Address: 0x00000000
     Entry Point:  0x00000000
     Hash algo:    crc32
     Hash value:   d4c2683b
     Hash algo:    sha1
     Hash value:   0f3c591c4f201d8cc1020725da0639d0b04d065a

Verifying Hash Integrity ... crc32+ sha1+ OK Uncompressing Kernel Image ... OK
## Flattened Device Tree from FIT Image at 00700000
Using 'conf at 1' configuration
Trying 'fdt at 1' FDT blob subimage

     Description:  Flattened Device Tree blob
     Type:         Unknown Image
     Compression:  Unknown Compression
     Data Start:   0x00add8e4
     Data Size:    12288 Bytes = 12 kB
     Hash algo:    crc32
     Hash value:   e07e11d2
     Hash algo:    sha1
     Hash value:   8ee8e8ce07508c534666f6d79fe89e46b8a7ae7a

Verifying Hash Integrity ... crc32+ sha1+ OK
ERROR: Not a FDT image - must RESET the board to recover.

Quoted 5 lines

As you can see the image-type of the fdt changed from "Flat Device Tree" to "Unknown Image" after decompressing the kernel, but the hash integrity seems to be fine (?!)

What am I doing wrong? What's missing?

Do some length analysis and make sure you are not stomping on any images in memory too, especially after uncompressing.

jdl