Unable to boot the new FIT image

U-Boot KJ H. Kiran 3 participants 5 messages May 19, 2014 – May 20, 2014 2 messages not in the archive

lore

Share & tools

lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

KJ H. Kiran

author

2014-05-19 04:36 UTC #1 lore raw

Hi ,

I am trying to make a eval board from TI to boot it with the new FIT image format.

I have followed the below procedure but iam getting the "No valid FDT found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED." error message. Cannot find out what is the exact problem.

U-Boot Source:

The latest source code from denx.

patman: Suppress duplicate signoffs only for real patches on 05/17/2014

Procedure:

Followed the exact same process mentioned in

http://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/U-Boot_verified_RSA_boot_flow_on_arm_target.pdf

I created a device tree and was able to generate a u-boot-dtb.bin file.

SD CARD:

1) copied the MLO in /boot

2) copied the u-boot-dtb.bin in /boot

3) coped the kernel_fdt.itb file

4) uEnv has

console=ttyO0,115200n8
fitfdt=/boot/kernel_fdt.itb
setenv loadaddr 0x82000000; run mmcargs; ext2load mmc ${mmcdev}:2 ${loadaddr} ${fitfdt};

I loaded the u-boot-dtb.bin file but it still complains ! Not much help form the forums/internet

Please let me know if i missed anything here.

Thanks,

Harsha

Jagan Teki

2014-05-19 14:39 UTC #2 lore raw

Quoted 9 lines · KJ H. Kiran

Hi ,
I am trying to make a eval board from TI to boot it with the new FIT image format.
I have followed the below procedure but iam getting the "No valid FDT found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED." error message. Cannot find out what is the exact problem.

This shouldn't be an issue with FIT - issue with booting u-boot fdt bin

Just for FIT work usage - try to boot with u-boot.bin (fdt less u-boot bin) So-that you can end up with normal u-boot booting.

On u-boot prompt and load u-boot-fdt.bin with TEXTBASE then load u-boot> fatload mmc 0 ${TEXTBASE} u-boot-fdt.bin u-boot> go ${TEXTBASE}

------ fdt u-boot boot prompt>
u-boot> fatload mmc 0 ${LOADADDR} kernel_fdt.itb
u-boot> bootm ${LOADADDR}
.....

Please send output log for this.

Quoted 33 lines

U-Boot Source:
The latest source code from denx.
patman: Suppress duplicate signoffs only for real patches on 05/17/2014
Procedure:
Followed the exact same process mentioned in
http://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/U-Boot_verified_RSA_boot_flow_on_arm_target.pdf
I created a device tree and was able to generate a u-boot-dtb.bin file.
SD CARD:
1) copied the MLO in /boot
2) copied the u-boot-dtb.bin in /boot
3) coped the kernel_fdt.itb file
4) uEnv has
console=ttyO0,115200n8
fitfdt=/boot/kernel_fdt.itb
setenv loadaddr 0x82000000; run mmcargs; ext2load mmc ${mmcdev}:2 ${loadaddr} ${fitfdt};

Quoted 4 lines

I loaded the u-boot-dtb.bin file but it still complains ! Not much help form the forums/internet
Please let me know if i missed anything here.

thanks!

Signature · 1 line

Jagan.

Simon Glass

2014-05-19 15:43 UTC #3 lore raw

+Tom

Quoted 21 lines · Jagan Teki

Quoted 9 lines · KJ H. Kiran
Hi ,
I am trying to make a eval board from TI to boot it with the new FIT image format.
I have followed the below procedure but iam getting the "No valid FDT found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED." error message. Cannot find out what is the exact problem.
This shouldn't be an issue with FIT - issue with booting u-boot fdt bin
Just for FIT work usage - try to boot with u-boot.bin (fdt less u-boot bin) So-that you can end up with normal u-boot booting.
On u-boot prompt and load u-boot-fdt.bin with TEXTBASE then load u-boot> fatload mmc 0 ${TEXTBASE} u-boot-fdt.bin u-boot> go ${TEXTBASE}

Quoted 6 lines

------ fdt u-boot boot prompt>
u-boot> fatload mmc 0 ${LOADADDR} kernel_fdt.itb
u-boot> bootm ${LOADADDR}
.....
Please send output log for this.

I hit this problem myself and posted this patch and the following series:

http://patchwork.ozlabs.org/patch/339609/

I heard from one person that it didn't work for them, but I haven't got back to it yet. Still, it might help you. There was a problem with the hash pushing out the end of the image.

Quoted 38 lines

Quoted 38 lines
U-Boot Source:
The latest source code from denx.
patman: Suppress duplicate signoffs only for real patches on 05/17/2014
Procedure:
Followed the exact same process mentioned in
http://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/U-Boot_verified_RSA_boot_flow_on_arm_target.pdf
I created a device tree and was able to generate a u-boot-dtb.bin file.
SD CARD:
1) copied the MLO in /boot
2) copied the u-boot-dtb.bin in /boot
3) coped the kernel_fdt.itb file
4) uEnv has
console=ttyO0,115200n8
fitfdt=/boot/kernel_fdt.itb
setenv loadaddr 0x82000000; run mmcargs; ext2load mmc ${mmcdev}:2 ${loadaddr} ${fitfdt};
I loaded the u-boot-dtb.bin file but it still complains ! Not much help form the forums/internet

Quoted 6 lines

Quoted 1 line
Please let me know if i missed anything here.
thanks!
--
Jagan.

Regards,
Simon

A message that is not in the archive (sent off-list or not yet received): b9dcc0f55ffd46ac94aaa2ef4b2616ac@DB3PR06MB185.eurprd06.prod.outlook.com

KJ H. Kiran

author

2014-05-20 03:39 UTC #5 lore raw

Hi Simon and Jagan,

Thanks for the help. I tried your suggestions but still I could not able to boot up my device.
Here is what I tried:
1) Applied the patch from Simon's email (.....http://patchwork.ozlabs.org/patch/339609/)
2) Compiled the u-boot with my public key signed device tree of U-boot
harsha at harshakiran_kasha:/abb/Experiments/u-boot$ sudo make ARCH=arm CROSS_COMPILE=/abb/compilers/gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux/bin/arm-linux-gnueabihf- -j8 DEV_TREE_DTB=./am335x-evmsk-pubkey.dtb

Please find attached log in the txt file attached. I got the MLO, u-boot.img, u-boot.bin, u-boot-dtb.bin binaries.

3) Copied the MLO, u-boot.bin and u-boot-dtb.bin and the FIT image into the SD card. This was the response:

U-Boot SPL 2014.07-rc1 (May 19 2014 - 13:17:49) reading u-boot.img
spl_load_image_fat: error reading image u-boot.img, err - -1 ### ERROR ### Please RESET the board ###

4) Second time , I copied MLO, u-boot.img, u-boot-dtb.bin and FIT image. This was the response:
U-Boot SPL 2014.07-rc1 (May 19 2014 - 13:17:49)
reading u-boot.img
reading u-boot.img
No valid FDT found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file .dtb>
### ERROR ### Please RESET the board ###

5) Since I added the CONFIG's to support the FIT, I was thinking even the u-boot.img expects a fdt binary. That?s the reason even the u-boot.img didn?t work.!

6) I commented out the CONFIGs from the am335x_evm.h file and compiled again. This time I loaded the MLO , u-boot.img, u-boot.dtb.bin and FIT just to check and follow jagan's suggestions..

I was able to successfully load MLO and U-boot and came to the u-boot# prompt.
....
U-Boot# fatload mmc 0 ${TEXTBASE} u-boot-dtb.bin
reading zImage
** Unable to read file zImage **
U-Boot# fatload mmc0
** No device specified **
U-Boot# fatload mmc0 u-boot-dtb.bin
** Bad device specification mmc0 u-boot-dtb.bin **
U-Boot# fatload mmc 0 ${TEXTBASE} u-boot-fdt.bin
reading zImage
** Unable to read file zImage **
U-Boot#
U-Boot#
U-Boot#

Please let me know if I am still missing anything.

Thanks,
Harsha kiran

-----Original Message-----
From: [email protected] [mailto:sjg at google.com] On Behalf Of Simon Glass
Sent: Monday, May 19, 2014 10:43 AM
To: Jagan Teki
Cc: KJ H. Kiran; u-boot at lists.denx.de; trini at ti.com
Subject: Re: [U-Boot] Unable to boot the new FIT image

+Tom

Quoted 18 lines · Jagan Teki

Quoted 9 lines · KJ H. Kiran
Hi ,
I am trying to make a eval board from TI to boot it with the new FIT image format.
I have followed the below procedure but iam getting the "No valid FDT found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED." error message. Cannot find out what is the exact problem.
This shouldn't be an issue with FIT - issue with booting u-boot fdt bin
Just for FIT work usage - try to boot with u-boot.bin (fdt less u-boot bin) So-that you can end up with normal u-boot booting.

Quoted 8 lines

On u-boot prompt and load u-boot-fdt.bin with TEXTBASE then load u-boot> fatload mmc 0 ${TEXTBASE} u-boot-fdt.bin go ${TEXTBASE}
------ fdt u-boot boot prompt>
u-boot> fatload mmc 0 ${LOADADDR} kernel_fdt.itb bootm ${LOADADDR}
.....
Please send output log for this.

I hit this problem myself and posted this patch and the following series:

http://patchwork.ozlabs.org/patch/339609/

I heard from one person that it didn't work for them, but I haven't got back to it yet. Still, it might help you. There was a problem with the hash pushing out the end of the image.

Quoted 42 lines

Quoted 42 lines
U-Boot Source:
The latest source code from denx.
patman: Suppress duplicate signoffs only for real patches on
05/17/2014
Procedure:
Followed the exact same process mentioned in
http://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/U-Boot_verifie
d_RSA_boot_flow_on_arm_target.pdf
I created a device tree and was able to generate a u-boot-dtb.bin file.
SD CARD:
1) copied the MLO in /boot
2) copied the u-boot-dtb.bin in /boot
3) coped the kernel_fdt.itb file
4) uEnv has
console=ttyO0,115200n8
fitfdt=/boot/kernel_fdt.itb
setenv loadaddr 0x82000000; run mmcargs; ext2load mmc ${mmcdev}:2 ${loadaddr} ${fitfdt};
I loaded the u-boot-dtb.bin file but it still complains ! Not much help form the forums/internet

Quoted 6 lines

Quoted 1 line
Please let me know if i missed anything here.
thanks!
--
Jagan.

Regards,
Simon

Simon Glass

2014-05-20 04:23 UTC #6 lore raw

In reply to a message not in the archive

Hi,

Quoted 4 lines · KJ H. Kiran

Hi Simon and Jagan,
Thanks for the help. I tried your suggestions but still I could not able

to boot up my device.

Quoted 2 lines

Here is what I tried:
1) Applied the patch from Simon's email (

http://patchwork.ozlabs.org/patch/339609/)

I think you need at least the next patch in that series.

Quoted 2 lines

2) Compiled the u-boot with my public key signed device tree of U-boot harsha at harshakiran_kasha:/abb/Experiments/u-boot$ sudo make ARCH=arm

CROSS_COMPILE=/abb/compilers/gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux/bin/arm-linux-gnueabihf- -j8 DEV_TREE_DTB=./am335x-evmsk-pubkey.dtb

Quoted 2 lines

Please find attached log in the txt file attached. I got the MLO,

u-boot.img, u-boot.bin, u-boot-dtb.bin binaries.

Quoted 2 lines

3) Copied the MLO, u-boot.bin and u-boot-dtb.bin and the FIT image into

the SD card. This was the response:

Quoted 7 lines

U-Boot SPL 2014.07-rc1 (May 19 2014 - 13:17:49) reading u-boot.img
spl_load_image_fat: error reading image u-boot.img, err - -1 ### ERROR ### Please RESET the board ###
4) Second time , I copied MLO, u-boot.img, u-boot-dtb.bin and FIT image.

This was the response:

Quoted 4 lines

U-Boot SPL 2014.07-rc1 (May 19 2014 - 13:17:49) reading u-boot.img
reading u-boot.img
No valid FDT found - please append one to U-Boot binary, use

u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file

Quoted 4 lines

.dtb>
### ERROR ### Please RESET the board ###
5) Since I added the CONFIG's to support the FIT, I was thinking even the

u-boot.img expects a fdt binary. That?s the reason even the u-boot.img didn?t work.!

Quoted 2 lines

6) I commented out the CONFIGs from the am335x_evm.h file and compiled

again. This time I loaded the MLO , u-boot.img, u-boot.dtb.bin and FIT just to check and follow jagan's suggestions..

Quoted 2 lines

I was able to successfully load MLO and U-boot and came to the u-boot#

prompt.

Quoted 36 lines

....
U-Boot# fatload mmc 0 ${TEXTBASE} u-boot-dtb.bin reading zImage
** Unable to read file zImage **
U-Boot# fatload mmc0
** No device specified **
U-Boot# fatload mmc0 u-boot-dtb.bin
** Bad device specification mmc0 u-boot-dtb.bin ** U-Boot# fatload mmc 0 ${TEXTBASE} u-boot-fdt.bin reading zImage
** Unable to read file zImage **
U-Boot#
U-Boot#
U-Boot#
Please let me know if I am still missing anything.
Thanks,
Harsha kiran
-----Original Message-----
From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
Sent: Monday, May 19, 2014 10:43 AM
To: Jagan Teki
Cc: KJ H. Kiran; u-boot at lists.denx.de; trini at ti.com
Subject: Re: [U-Boot] Unable to boot the new FIT image
+Tom
Quoted 2 lines · Jagan Teki
On Mon, May 19, 2014 at 10:06 AM, KJ H. Kiran <[email protected]>

Quoted 5 lines · wrote:

Quoted 5 lines
Quoted 5 lines
Hi ,
I am trying to make a eval board from TI to boot it with the new FIT

image format.

Quoted 3 lines

Quoted 3 lines
Quoted 3 lines
I have followed the below procedure but iam getting the "No valid FDT

found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED." error message. Cannot find out what is the exact problem.

Quoted 15 lines

Quoted 15 lines
Quoted 1 line
This shouldn't be an issue with FIT - issue with booting u-boot fdt bin
Just for FIT work usage - try to boot with u-boot.bin (fdt less u-boot bin) So-that you can end up with normal u-boot booting.
On u-boot prompt and load u-boot-fdt.bin with TEXTBASE then load u-boot> fatload mmc 0 ${TEXTBASE} u-boot-fdt.bin go ${TEXTBASE}
------ fdt u-boot boot prompt>
u-boot> fatload mmc 0 ${LOADADDR} kernel_fdt.itb bootm ${LOADADDR}
.....

Quoted 7 lines

Quoted 1 line
Please send output log for this.
I hit this problem myself and posted this patch and the following series:
http://patchwork.ozlabs.org/patch/339609/
I heard from one person that it didn't work for them, but I haven't got

back to it yet. Still, it might help you. There was a problem with the hash pushing out the end of the image.

Quoted 14 lines

Quoted 14 lines
Quoted 14 lines
U-Boot Source:
The latest source code from denx.
patman: Suppress duplicate signoffs only for real patches on
05/17/2014
Procedure:

Quoted 7 lines

Quoted 7 lines
Quoted 7 lines
Followed the exact same process mentioned in
http://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/U-Boot_verifie
d_RSA_boot_flow_on_arm_target.pdf
I created a device tree and was able to generate a u-boot-dtb.bin

file.

Quoted 33 lines

Quoted 22 lines
Quoted 22 lines
SD CARD:
1) copied the MLO in /boot
2) copied the u-boot-dtb.bin in /boot
3) coped the kernel_fdt.itb file
4) uEnv has
console=ttyO0,115200n8
fitfdt=/boot/kernel_fdt.itb
setenv loadaddr 0x82000000; run mmcargs; ext2load mmc ${mmcdev}:2 ${loadaddr} ${fitfdt};
I loaded the u-boot-dtb.bin file but it still complains ! Not much help form the forums/internet
Quoted 6 lines
Quoted 1 line
Please let me know if i missed anything here.
thanks!
--
Jagan.
Regards,
Simon