From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joao Pinto Date: Wed, 27 Apr 2016 12:44:39 +0100 Subject: [Buildroot] [PATCH 1/2] uboot and arm trusted firmware build added to juno board In-Reply-To: <20160427133149.330a7ea0@free-electrons.com> References: <20160426221915.2651d4b2@free-electrons.com> <20160427102302.GM28464@e106497-lin.cambridge.arm.com> <20160427133149.330a7ea0@free-electrons.com> Message-ID: <5720A627.6000109@synopsys.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello! On 4/27/2016 12:31 PM, Thomas Petazzoni wrote: > Hello, > > On Wed, 27 Apr 2016 11:23:02 +0100, Liviu.Dudau at arm.com wrote: > >>> On Tue, 26 Apr 2016 17:35:55 +0100, Joao Pinto wrote: >>> >>>> + +-- u-boot.bin >>>> + +-- bl1.bin >>>> + +-- bl2.bin >>>> + +-- bl2u.bin >>>> + +-- bl31.bin >>>> + +-- fip.bin >>> >>> Looking at your atfirmware package, I see bl1.bin and fip.bin being >>> copied to output/images, but not bl2.bin, bl2u.bin and bl31.bin. Why >>> are you mentioning them here? >> >> Those get embedded into the fip.bin. For Juno you need only bl1.bin and >> fip.bin to be transfered to the board. > > Right, and they are indeed not copied to $(BINARIES_DIR) by the > atfirmware package. So they shouldn't be mentioned in the readme.txt. Yes, no problem I will give a check to all your comments. > > Thomas > The SCP firmware is a critical piece for the Juno, but the problem is that it can't be built from any repository I think. @Liviu: Could you please confirm this info? If the SCP firmware exists as a binary only, then we have to include it in /board/arm/juno folder for building the ATF out-of-the-box. Opinions? Thanks, Joao