All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wesley Revens <wesley@sonifex.co.uk>
To: Neal Frager <nealf@xilinx.com>, Michal Simek <michals@xilinx.com>,
	Neal Frager <neal.frager@amd.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>,
	"giulio.benetti@benettiengineering.com"
	<giulio.benetti@benettiengineering.com>,
	"michal.simek@amd.com" <michal.simek@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig
Date: Mon, 9 May 2022 15:58:04 +0100	[thread overview]
Message-ID: <73ea7940-e778-cdf9-9364-66773632efbd@sonifex.co.uk> (raw)
In-Reply-To: <SJ0PR02MB7758B99F6AD8F668FE7F318AD7C69@SJ0PR02MB7758.namprd02.prod.outlook.com>

Hi Neal,

On 09/05/2022 15:41, Neal Frager wrote:
> Hi Wesley,
>
>> No change with the updated psu_init_gpl.c.
>> When using the pmufw from the 2022.1 BSP is there a different pm_cfg_obj.c also required?
>> I am still using the original in buildroot/board/zynqmp/kria/kv260
> I am currently stuck in the same place as you with the exact same boot log.
Glad I'm not the only one!
>
> I generated the buildroot/board/zynqmp/kria/kv260/pm_cfg_obj.c with Vitis 2022.1, so this file should not be the issue.
>
> Also, for completeness, only the zynqmp_console needed to be correctly defined for the atf as the zynqmp uses uart1.
> BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES="ZYNQMP_CONSOLE=cadence1"
>
> The PRELOADED_BL33_BASE parameter was already correct by default when using the zynqmp platform.
If I leave out the PRELOADED_BL33_BASE setting, my ATF does not run and 
I get stuck at the end of U-Boot SPL with "Trying to boot from SPI"
>
> Once we get this working properly, I will patch buildroot, so other users will have a working solution.
>
> Thank you for your patience and let me know if you make any progress on your side.
No problem, It will be good to get it all working
> Best regards,
> Neal Frager
> AMD
>
Regards,
Wesley
To unsubscribe click: http://link.sonifex.co.uk/us/?e=1no4prDIIaINlS.-fv7cCEYCzrKP
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-05-09 14:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 15:54 [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig Neal Frager via buildroot
2022-05-05 15:54 ` [Buildroot] [PATCH v1 2/2] DEVELOPERS update Neal Frager via buildroot
2022-05-05 19:49   ` Arnout Vandecappelle
2022-05-06 19:22   ` Peter Korsgaard
2022-05-06 11:17 ` [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig Wesley Revens
2022-05-06 11:30   ` Neal Frager
     [not found]   ` <51fb4a8c-cd8c-9db0-76e4-5461e72871f8@xilinx.com>
2022-05-09  6:23     ` Neal Frager
     [not found]       ` <dd608132-245a-32b7-7d27-f267c1524fee@xilinx.com>
2022-05-09  9:14         ` Wesley Revens
2022-05-09  9:22           ` Neal Frager
2022-05-09 10:54             ` Wesley Revens
2022-05-09 11:00               ` Neal Frager
2022-05-09 11:19                 ` Wesley Revens
2022-05-09 13:46                   ` Neal Frager
2022-05-09 14:33                     ` Wesley Revens
2022-05-09 14:41                       ` Neal Frager
2022-05-09 14:58                         ` Wesley Revens [this message]
2022-05-09 19:01                           ` Neal Frager
2022-05-10  4:29                             ` Neal Frager
2022-05-10  4:36                               ` Neal Frager
2022-05-10  8:22                               ` Wesley Revens
2022-05-10  8:26                                 ` Neal Frager
2022-05-06 19:22 ` Peter Korsgaard
2022-05-07  6:26   ` Neal Frager
2022-05-07 21:01     ` Peter Korsgaard
2022-05-08  6:46       ` Neal Frager
2022-05-08  9:05         ` Peter Korsgaard
2022-05-10  9:15           ` Neal Frager
     [not found]   ` <32c2dc3c-10c1-cda7-219f-f3753940f294@xilinx.com>
2022-05-09  8:14     ` 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=73ea7940-e778-cdf9-9364-66773632efbd@sonifex.co.uk \
    --to=wesley@sonifex.co.uk \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=luca@lucaceresoli.net \
    --cc=michal.simek@amd.com \
    --cc=michals@xilinx.com \
    --cc=neal.frager@amd.com \
    --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.