All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Neal Frager <nealf@xilinx.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>
Subject: Re: [Buildroot] [PATCH 2/2] Add configs/zynqmp_zcu102_defconfig
Date: Fri, 4 Feb 2022 11:13:54 +0100	[thread overview]
Message-ID: <2b671b31-5f2e-e3f1-b365-e5f2be2ca4fc@benettiengineering.com> (raw)
In-Reply-To: <SJ0PR02MB775844C568A8974CFF89518BD7299@SJ0PR02MB7758.namprd02.prod.outlook.com>

Hi Neal,

On 04/02/22 08:09, Neal Frager wrote:
> Hi Giulio,
> 
>> Hi Neal,
> 
>> can you please improve commit log doing a presentation of what is zynqmp_zcu102?
> 
>> Is this for thi boards
>> https://www.xilinx.com/products/boards-and-kits/ek-u1-zcu102-g.html ?
> 
>> If yes please describe its features and point the url at the end of commit log.
> 
> Yes, no problem.  I will add the url that describes the board to the commit log.
> 
> On 03/02/22 14:44, Neal Frager wrote:
>> Signed-off-by: Neal Frager <neal.frager@xilinx.com>
>> ---
>>    configs/zynqmp_zcu102_defconfig | 34 +++++++++++++++++++++++++++++++++
>>    1 file changed, 34 insertions(+)
>>    create mode 100644 configs/zynqmp_zcu102_defconfig
>>
>> diff --git a/configs/zynqmp_zcu102_defconfig
>> b/configs/zynqmp_zcu102_defconfig new file mode 100644 index
>> 0000000000..5f98e72aaf
>> --- /dev/null
>> +++ b/configs/zynqmp_zcu102_defconfig
>> @@ -0,0 +1,34 @@
>> +BR2_aarch64=y
>> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10=y
>> +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/zynqmp/post-image.sh"
>> +BR2_LINUX_KERNEL=y
>> +BR2_LINUX_KERNEL_CUSTOM_GIT=y
>> +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://github.com/Xilinx/linux-xlnx.git"
>> +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xlnx_rebase_v5.10_2021.2"
>> +BR2_LINUX_KERNEL_DEFCONFIG="xilinx_zynqmp"
>> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
>> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="xilinx/zynqmp-zcu102-rev1.0"
> 
>> Here you need also:
>> BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
> 
> Thanks for making me aware of this.  I will add it to both defconfigs.
> 
>> +BR2_TARGET_ROOTFS_EXT2=y
>> +BR2_TARGET_ROOTFS_EXT2_4=y
>> +# BR2_TARGET_ROOTFS_TAR is not set
>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://github.com/ARM-software/arm-trusted-firmware.git"
>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="v2.4"
>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="zynqmp"
>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31_UBOOT=y
>> +BR2_TARGET_UBOOT=y
>> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>> +BR2_TARGET_UBOOT_CUSTOM_GIT=y
>> +BR2_TARGET_UBOOT_CUSTOM_REPO_URL="git://github.com/xilinx/u-boot-xlnx.git"
>> +BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xlnx_rebase_v2021.01_2021.2"
>> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="xilinx_zynqmp_virt"
>> +BR2_TARGET_UBOOT_NEEDS_DTC=y
>> +BR2_TARGET_UBOOT_SPL=y
>> +BR2_TARGET_UBOOT_SPL_NAME="spl/boot.bin"
>> +BR2_TARGET_UBOOT_ZYNQMP=y
>> +BR2_TARGET_UBOOT_ZYNQMP_PMUFW="https://github.com/lucaceresoli/zynqmp-pmufw-binaries/raw/2021.2/bin/pmufw-v2021.2.bin"
> 
>> This ^^^ URL is unreachable and I've found this as substitution:
>> https://github.com/lucaceresoli/zynqmp-pmufw-binaries/blob/v2021.2/bin/pmufw-v2021.2.bin
> 
>> Luca, is that the correct one? I've switched to v2021.2 tag and copied the link.
> 
> Sorry about this one.  I was balancing a couple too many versions of my defconfig files and this typo slipped through the cracks.  I have corrected it in both defconfigs for the next version of the patch.
> 
>> +BR2_TARGET_UBOOT_FORMAT_ITB=y
>> +BR2_PACKAGE_HOST_DOSFSTOOLS=y
>> +BR2_PACKAGE_HOST_GENIMAGE=y
>> +BR2_PACKAGE_HOST_MTOOLS=y
> 
>> I've built with gitlab-CI, check this patch for the manual to reproduce:
>> https://patchwork.ozlabs.org/project/buildroot/patch/20220203235438.610277-1-giulio.benetti@benettiengineering.com/
> 
>> BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y came out using the docker.
> 
>> Can anyone test it on real hardware? Luca maybe?
> 
> Regarding the board test, there is one thing still missing.  U-Boot 2021.01 uses distro boot, so for U-Boot to properly boot the Linux kernel and rootfs, a boot.scr file needs to be in the boot partition of the SD card.  I have been getting it to work by manually adding this file to the SD card image after the build.  But a better way would be that this file is already included with the genimage.cfg.  How does buildroot typically handle U-Boot boot.scr files?  I would be happy to add this to the automated build process, but I do not wish to re-invent the wheel.

Lately a lot of extlinux.conf has been used instead of boot.scr, so you 
could go for something like this:
https://git.buildroot.net/buildroot/tree/board/stmicroelectronics/stm32mp157c-dk2/overlay/boot/extlinux/extlinux.conf

and point to it in board defconfig.

Best regards
-- 
Giulio Benetti
Benetti Engineering sas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-02-04 10:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 13:44 [Buildroot] [PATCH 1/2] configs/zynqmp_zcu106: Bump ATF/U-Boot/Linux to Xilinx 2021.2 Neal Frager
2022-02-03 13:44 ` [Buildroot] [PATCH 2/2] Add configs/zynqmp_zcu102_defconfig Neal Frager
2022-02-04  1:40   ` Giulio Benetti
2022-02-04  7:09     ` Neal Frager
2022-02-04 10:13       ` Giulio Benetti [this message]
2022-02-04  1:41 ` [Buildroot] [PATCH 1/2] configs/zynqmp_zcu106: Bump ATF/U-Boot/Linux to Xilinx 2021.2 Giulio Benetti
  -- strict thread matches above, loose matches on Subject: below --
2022-02-08  7:15 [Buildroot] [PATCH 1/2] configs/zynqmp_zcu106: Bump ATF/U-Boot/Linux to Xilinx 2022 Neal Frager
2022-02-08  7:15 ` [Buildroot] [PATCH 2/2] Add configs/zynqmp_zcu102_defconfig Neal Frager

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2b671b31-5f2e-e3f1-b365-e5f2be2ca4fc@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=buildroot@buildroot.org \
    --cc=luca@lucaceresoli.net \
    --cc=nealf@xilinx.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.