Hi Simon. I am able to successfully load the FIT image now :) Thanks for the help.
I applied Heiko's patch. If CONFIG_OF_CONTROL is defined, the behaviour of the board is same as i mentioned in my previous emails. I tried removing the CONFIG_OF_CONTROL from the config file and it was able to read the u-boot.img. I modifed my uEnv.txt file and i was able to load my FIT image. I was wondering if we use CONFIG_OF_SEPERATE and CONFIG_DEFAULT_DEVICE_TREE is it fine not to use the CONFIG_OF_CONTROL? and how should i use the u-boot-dtb.bin file? I tried stopping the u-boot and entered the following in the u-boot prompt to load the u-boot-dtb.bin u-boot# fatload mmc 0 0x81000000 u-boot-dtb.bin U-Boot# U-Boot# U-Boot# fatload mmc 0 0x81000000 u-boot-dtb.bin reading u-boot-dtb.bin 460759 bytes read in 43 ms (10.2 MiB/s) U-Boot# go 0x81000000 ## Starting application at 0x81000000 ... U-Boot 2014.07-rc1 (May 25 2014 - 00:46:36) I2C: ready DRAM: 1 GiB and it hangs here.. Which address should i use to load the u-boot-dtb.bin? I will start working on the secure u-boot with FIT signatures soon on am335xsk EVM. Thanks, Harsha On Fri, May 23, 2014 at 7:08 PM, Simon Glass <s...@chromium.org> wrote: > Hi, > > On 21 May 2014 15:12, Simon Glass <s...@chromium.org> wrote: > > Hi Harsha, > > > > On 21 May 2014 06:46, Harsha Kiran <harshakiran...@gmail.com> wrote: > >> Hi Simon, > >> > >> I have added the next patch in the series i.e., (....../339610/) But the > >> result is still the same. This particular patch just created a device > tree > >> In the arch/arm/dts folder For the beaglebone. I have already tried > creating > >> for am335x-evmsk and was able to build the u-boot-dtb.bin. > >> > >> I have noticed that MLO is configured to read only the u-boot.img not > any > >> other binaries (eg U-boot.bin or u-boot-dtb.bin). > >> It gives me the following error.. > >> spl_load_image_fat: error reading image u-boot.img, err - -1 Which part > of > >> the configuration I should change so that MLO tries to read the > >> u-boot-dtb.bin as the third stage bootloader?? > >> I tried loading MLO->u-boot.img first, but this time it reads the > u-boot.img > >> but gives the following error.. > >> > >> 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 ### > > Also I wonder if this is related to Heiko's patch? Worth trying. > > http://patchwork.ozlabs.org/patch/350541/ > > Regards, > Simon > --
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
