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.
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 you're using an experimental uboot/spl rather than
a known-stable working version for whatever hardware this is?
(Of course, if this is bring-up of a new architecture that has never been
supported by uboot, so there's never been a working uboot for the device, it's
time to quote the movie Animal House: "My advice to you is to start drinking
heavily")