All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot build and deploy added to juno board
Date: Wed, 20 Apr 2016 22:02:28 +0200	[thread overview]
Message-ID: <20160420220228.59d5e54f@free-electrons.com> (raw)
In-Reply-To: <fce2649dcd6d9c232e557bfb06de3ff222fe9fa6.1461174061.git.jpinto@synopsys.com>

Hello,

On Wed, 20 Apr 2016 18:47:04 +0100, Joao Pinto wrote:
> This patch has the goal to add to the juno board defconfig the u-boot build 
> configurations. The juno board readme file was also updated with the
> necessary steps to build the ARM Trusted Firmware (with u-boot in it) and
> how to deploy it.

Thanks!

> +Building bootloader files bl1.bin and fip.bin
> +=============================================
> +First clone ARM Trusted Firmware repository
> +
> +   $ git clone https://github.com/ARM-software/arm-trusted-firmware.git
> +
> +After clonning, please configure the following environment variables:
> +
> +  CROSS_COMPILE=<buidlroot_path>/output/host/usr/bin/aarch64-buildroot-linux-gnu-
> +  BL33=<buidlroot_path>/output/images/u-boot.bin
> +  SCP_BL2=<path_to_scp_firmware>
> +
> +Finaly execute:
> +  make PLAT=juno all fip

The whole point of Buildroot is to automate the build process, so this
should be done by a Buildroot package, rather than manually by the
user. So a package for ATF should probably be created.

I also work on an ARM64 platform that uses ATF+U-Boot, so I'll be able
to compare and tell you whether what you're proposing is only
applicable to Juno, or can be used for other platforms as well.

> +BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY=y

Using the legacy build system with a modern U-Boot such as 2016.03
doesn't make much sense. Please use the kconfig based build system,
unless there is a real reason not to.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-04-20 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 17:47 [Buildroot] [PATCH] uboot build and deploy added to juno board Joao Pinto
2016-04-20 20:02 ` Thomas Petazzoni [this message]
2016-04-21 10:34   ` Joao Pinto
2016-04-21 11:26     ` Thomas Petazzoni
2016-04-21 16:35       ` Joao Pinto
2016-04-21 19:28         ` Thomas Petazzoni
2016-04-21 20:55 ` Arnout Vandecappelle

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=20160420220228.59d5e54f@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.