Re: [U-Boot] Unable to boot the new FIT image
Hi,
On May 19, 2014 1:32 PM, "KJ H. Kiran" kj.h.kiran@us.abb.com wrote:
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:
- 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.
- Compiled the u-boot with my public key signed device tree of U-boot
harsha@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.
- 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 ###
- 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 ###
- 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.!
- 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: sjg@google.com [mailto:sjg@google.com] On Behalf Of Simon Glass Sent: Monday, May 19, 2014 10:43 AM To: Jagan Teki Cc: KJ H. Kiran; u-boot@lists.denx.de; trini@ti.com Subject: Re: [U-Boot] Unable to boot the new FIT image
+Tom
On 19 May 2014 07:39, Jagan Teki jagannadh.teki@gmail.com wrote:
On Mon, May 19, 2014 at 10:06 AM, KJ H. Kiran kj.h.kiran@us.abb.com
wrote:
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 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.
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:
copied the MLO in /boot
copied the u-boot-dtb.bin in /boot
coped the kernel_fdt.itb file
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!
Jagan.
Regards, Simon
participants (1)
-
Simon Glass