07:53 <ldts> agraf: do you remember where the 0x9c0 address came from on the zynqmpbif layout? and why we could place the firmware before the spl binary? I dont think the layout that it generates follows the documentation so I am a bit puzzled.....

07:57 <ldts> ...notice that since bootgen cant read the layout generated by mkimage, I think it is fair to say that is not following the documentation...so not quite sure how to extend it ATM

08:24 <faruk> Hi. Is there any way to read kernel from jffs2 in spi flash ?

08:24 <faruk> For example, https://linux-sunxi.org/U-Boot page has "load mmc 0:1 0x42000000 uImage || load mmc 0:1 0x42000000 boot/uImage".

08:24 <faruk> So it's reading from the mmc interface. With which interface can I read the kernel in spi from the file system in uboot?

08:24 <faruk> Thanks

09:33 <agraf> ldts: which 0x9c0 address? Do you have a code pointer?

09:53 <ldts> https://github.com/ARM-software/u-boot/blob/master/tools/zynqmpimage.c#L55

09:55 <ldts> just because I am not sure how that address was determined https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_2/ug1283-bootgen-user-guide.pdf page 25

10:12 <ldts> it is just weird that it boots because the device image header table (page 26) is placed at the bottom of the image (after the PMUFW and the SPL+dtb binary)