Hi,
On 21 May 2014 15:12, Simon Glass sjg@chromium.org wrote:
Hi Harsha,
On 21 May 2014 06:46, Harsha Kiran harshakiran443@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