Yes, it is for bringup purpose. We have working uboot software and we split
the code in order to have FSBL and SSBL and I had such problem but it was a
matter of deleting "-f auto" and -E option from mkimage for building
u-boot.img. Now FSBL, SSBL and kernel starts successfully.
pt., 6 gru 2019 o
On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said:
> And this uboot and spl is somekind of experimental software which is in
> the middle of creation. Could anyone try to guide what might be possible
> the reason of the issue as I am a bit new in u-boot development?
Is there a reason why
OK I found on my own.
The proper mkimage command is:
./tools/mkimage -A arm -T firmware -C none -O u-boot -a 0x10 -e 0 -n
"someName" -d u-boot-dtb.bin u-boot.img
without '-f auto and -E'
pt., 6 gru 2019 o 10:03 Tomek Domek napisał(a):
> Hi
> I have FSBL and SSBL. SPL uboot starts
Hi
I have FSBL and SSBL. SPL uboot starts successfully and u-boot.img is
loaded successfully but it hangs on 'boot_from_devices' function and
'fit_find_config_node':
fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
Firmware image with one or more FDT blobs
