Hi Kever, On Mon, 10 Aug 2020 at 01:47, Kever Yang <kever.y...@rock-chips.com> wrote: > > Hi Simon, > > On 2020/8/8 下午9:28, Simon Glass wrote: > > +#ifdef CONFIG_ROCKCHIP_SPI_IMAGE > +&binman { > + rom { > + filename = "u-boot.rom"; > + size = <0x400000>; > + pad-byte = <0xff>; > + > + mkimage { > + args = "-n rk3399 -T rkspi"; > + u-boot-spl { > + }; > + }; > + u-boot-img { > + offset = <0x40000>; > + }; > + u-boot { > + offset = <0x300000>; > + }; > + fdtmap { > + }; > > There is a output name 'u-boot.rom' including: > > - u-boot-spl output with mkimage cmd at offset 0? > > Yes > > - u-boot-img at offset 0x40000, how this is generated and what is > inside? does binary in bl31.elf included? > > It is just the u-boot.img file created by the Makefile. There is no BL31. > > - u-boot at offset 0x300000, what is this binary and where is it from? > > This is u-boot.bin as created by the Makefile. > > Why do you need both u-boot.img and u-boot.bin, I don't understand this.
Neither do I. It needs a look. > > And if there is no BL31, the system is not possible to boot up. This was done quite a while ago with the objective of getting a basic U-Boot going on this board, so it needs more work to finish it off. Regards, SImon