All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neal Frager <nealf@xilinx.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>,
	"giulio.benetti@benettiengineering.com"
	<giulio.benetti@benettiengineering.com>,
	Michal Simek <michals@xilinx.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022
Date: Wed, 23 Feb 2022 11:02:24 +0000	[thread overview]
Message-ID: <PH0PR02MB775035975B305CECD5D842F3D73C9@PH0PR02MB7750.namprd02.prod.outlook.com> (raw)
In-Reply-To: <87sfs96gqj.fsf@dell.be.48ers.dk>

Hi Peter,

> Hmm, did you test this on a zcu106 board?

> I just got access to a zcu106 rev 1.0 board and gave it a try here, and see nothing on either of the serial ports.

> Looking at the u-boot configuration I see that xilinx_zynqmp_virt_defconfig sets:

> CONFIG_DEFAULT_DEVICE_TREE="zynqmp-zcu100-revC"

> Which seems to have a different uart and pinmuxing setup. Changing that to zynqmp-zcu106-revA it does boot (but complains here and there).

> This is the first time I use a zcu106, so maybe I am missing something, but I don't understand how it can work for you with the zcu100 DTB?

Thank you for catching this.  I will take care of getting this corrected with a follow up patch.

The way zynqmp_virt_defconfig works is described on our wiki page below:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841973/Build+U-Boot

The reason why this was working for me is because I had the DEVICE_TREE environment variable set when building.

make distclean
make xilinx_zynqmp_virt_defconfig
export DEVICE_TREE="zynqmp-zcu106-revA"
make

What is the proper way for setting an environment variable with buildroot?  Should I add this as a pre-build script in each defconfig?

Best regards,
Neal Frager
Xilinx

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-02-23 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 14:44 [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022 Neal Frager
2022-02-11 14:44 ` [Buildroot] [PATCH v6 2/2] add configs/zynqmp_zcu102_defconfig Neal Frager
2022-02-12 13:43   ` Peter Korsgaard
2022-02-12 13:13 ` [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022 Luca Ceresoli
2022-02-12 13:18   ` Neal Frager
2022-02-12 13:45   ` Peter Korsgaard
2022-02-12 14:47     ` Neal Frager
2022-02-23 10:05     ` Peter Korsgaard
2022-02-23 12:55       ` Neal Frager
2022-02-12 13:42 ` Peter Korsgaard
2022-02-23 10:04   ` Peter Korsgaard
2022-02-23 11:02     ` Neal Frager [this message]
2022-02-23 11:11       ` Peter Korsgaard
2022-02-23 11:29         ` Neal Frager
2022-02-23 11:18       ` Peter Korsgaard
2022-02-23 11:27         ` Neal Frager
2022-02-23 11:07     ` 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=PH0PR02MB775035975B305CECD5D842F3D73C9@PH0PR02MB7750.namprd02.prod.outlook.com \
    --to=nealf@xilinx.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=luca@lucaceresoli.net \
    --cc=michals@xilinx.com \
    --cc=peter@korsgaard.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.