All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wesley Revens <wesley@sonifex.co.uk>
To: Neal Frager <neal.frager@amd.com>, buildroot@buildroot.org
Cc: luca@lucaceresoli.net, giulio.benetti@benettiengineering.com,
	michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig
Date: Fri, 6 May 2022 12:17:42 +0100	[thread overview]
Message-ID: <77b0f29f-7df7-36f4-9b49-5212fd46c5af@sonifex.co.uk> (raw)
In-Reply-To: <20220505155424.3002847-1-neal.frager@amd.com>

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.

Regards,

Wesley


On 05/05/2022 16:54, Neal Frager via buildroot wrote:
> This patch adds support for Xilinx Kria KV260 starter kit.
>
> KV260 features can be found here:
> https://www.xilinx.com/products/boards-and-kits/kv260.html
>
> While the Kria SOM is based on a ZynqMP SoC, there are some key
> boot config differences from the other ZynqMP evaluation boards.
>
> 1. There are no boot switches on Kria SOMs. The boot mode is thus
> hard configured for QSPI flash. A pre-programmed boot.bin comes
> with every Starter Kit. U-Boot can then find the Linux kernel and
> file system on the SD card.
>
> Optional instructions for updating the boot.bin in the QSPI flash
> can be found in the readme.txt file and the link below.
>
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM
>
> 2. Kria SOMs use UART1 for the console instead of UART0. For this
> reason, Kria Starter Kits will use a separate extlinux.conf file
> from other ZynqMP evaluation boards.
<snip>
To unsubscribe click: http://link.sonifex.co.uk/us/?e=1nXvxxPuEp2Zja.ddedfjkAKO6ol
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-05-06 11:32 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 ` Wesley Revens [this message]
2022-05-06 11:30   ` [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig 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
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=77b0f29f-7df7-36f4-9b49-5212fd46c5af@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=neal.frager@amd.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.