[Buildroot] [PATCH] uboot build and deploy added to juno board

[Joao Pinto <Joao.Pinto@synopsys.com>]

Hello,

On 4/20/2016 9:02 PM, Thomas Petazzoni wrote:
> 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.

It would great to do it 100% automatic. I'll be waiting for your feedback
regarding your ARM64 platform. If it is the same we could do it together.

> 
>> +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.

Yes, you are right, made a mistake!

> 
> Thanks!
> 
> Thomas
> 

Thanks,
Joao