Re: [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig

[Neal Frager <nealf@xilinx.com>]

Hi Michal,

> 
> Hi Neal,
> 
> I have been working on a Buildroot image for the Kria recently so my 
> company can evaluate the K26 SOM.
> I reached a similar position to what has been included in your patch 
> however I have not been able to get the Kria to boot using the U-Boot 
> SPL.
> 
> I have tried out your patch and found that the Linux kernel is booting 
> fine from the SD card using the pre-programmed boot.bin that is 
> already present on the Kria.
> However, after building using your patch, I tried uploading the 
> boot.bin that appears in buildroot/output/images to my Kria using the 
> "Boot Image Recovery Tool" web UI that runs on the Kria if you hold 
> down the FWUEN button during reset of the board. On boot, I then get 
> the following output from U-Boot SPL:
> 
> U-Boot SPL 2022.01 (May 06 2022 - 11:21:55 +0100)
> PMUFW:  v1.1
> Loading new PMUFW cfg obj (2016 bytes) Silicon version:        3 EL 
> Level:       EL3 Chip ID:        xck26
> Multiboot:      64
> Trying to boot from SPI
> 
> Then nothing else happens.
> 
> There is a big difference in the file sizes for the boot.bin from 
> buildroot/output/images and the BOOT.BIN I downloaded from 
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+
> K26+SOM#Boot-Firmware-Updates
> 
> so I am obviously missing something somewhere. I think all the 
> components are being built but I'm not sure they are being packaged in 
> a similar way to how the pre-loaded boot.bin is laid out (or I am 
> using the wrong output file!)
> 
> In my own testing I was able to test the u-boot.img produced by my 
> Buildroot build but I had to use the Xilinx bootgen tools and use the 
> Xilinx fsbl rather than the U-Boot SPL.
> 
> In future, we would like to be able to bypass this step and just use 
> whatever Buildroot produces.
> I was wondering if you could point me in the right direction.

> Not quite sure what Neil is using but of course you can use SPL with Kria SOM and I am using it on daily basis.
> It really depends what exactly you want do and do some alignments to u-boot config.
> Let's assume you have starter kit with preinstalled A/B updates you need to say if you want to have this functionality or not.
> I personally didn't try to use A/B with SPL and using partition for image A for boot.bin (SPL only) and partition B for image.itb.
> That being said you need to tell SPL where u-boot.itb is placed in QSPI.

> It means you need to setup CONFIG_SYS_SPI_U_BOOT_OFFS=0xF80000 as offset to place image to this location.

> If you use update utility then write u-boot.itb (you need to rename it because gui expects *.bin filename) first to imageB and then boot.bin to Image A.

> Compare to the latest upstream version you need enable some configs.
> CONFIG_DEFAULT_DEVICE_TREE="zynqmp-smk-k26-revA"
> CONFIG_ENV_SIZE=0x40000
> CONFIG_SYS_SPI_U_BOOT_OFFS=0xF80000

These configs are clear and specific to the Kria SOM.

> CONFIG_DTB_RESELECT=y
> CONFIG_MULTI_DTB_FIT=y
> CONFIG_ENV_IS_NOWHERE=y (only)
> CONFIG_USE_DEFAULT_ENV_FILE=y
> CONFIG_DEFAULT_ENV_FILE="vars"
> CONFIG_DMA=y
> CONFIG_XILINX_DPDMA=y
> CONFIG_PHY=y
> CONFIG_PHY_XILINX_ZYNQMP=y
> CONFIG_PINCTRL=y
> CONFIG_PINCONF=y
> CONFIG_POWER_DOMAIN=y
> CONFIG_ZYNQMP_POWER_DOMAIN=y
> CONFIG_DM_RESET=y
> CONFIG_RESET_ZYNQMP=y
> CONFIG_VIDEO_ZYNQMP_DPSUB=y

These configs do not appear specific to Kria.  Should we be using them for other zynqmp boards as well?
Such as the zcu102 and zcu106?

We are currently just using the xilinx_zynqmp_virt_defconfig with the CONFIG_DEFAULT_DEVICE_TREE
for each individual board.  Is this sufficient for the zcu102 and zcu106 boards?

Best regards,
Neal Frager
AMD
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot