From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mikko Perttunen Subject: Re: How to test new bootloaders on Jetson TX1? Date: Thu, 15 Feb 2018 16:22:26 +0200 Message-ID: References: <5ff3ffde-653c-ea50-490c-efcc6dccecc2@suse.de> <2089c895-7992-9741-a471-fae5b410d4b7@kapsi.fi> <8320e1df-774c-65c1-28ae-96e1b90ad178@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <8320e1df-774c-65c1-28ae-96e1b90ad178-l3A5Bk7waGM@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: =?UTF-8?Q?Andreas_F=c3=a4rber?= Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, U-Boot , Alexander Graf , Mian Yousaf Kaukab , Tom Warren , Varun Wadekar List-Id: linux-tegra@vger.kernel.org On 15.02.2018 15:25, Andreas Färber wrote: > Hi Mikko, > > Am 15.02.2018 um 08:56 schrieb Mikko Perttunen: >> In the cboot + U-Boot combination, cboot loads U-Boot from the usual >> kernel partition (LNX or kernel depending on system), so flashing U-Boot >> there should do the trick. I believe this did indeed change in some L4T >> version, so the wiki page needs to be updated. Tom should know more >> about this. > > Thanks for explaining. > > The LNX partition is getting a boot.img - what is the relation to the > four U-Boot files? flash.sh source is not really helping here. cboot is only capable of booting Android .img's so the U-Boot binary (u-boot-dtb.bin according ton Jon) is packaged as one using mkbootimg or similar - I expect flash.sh to do this automatically. > > Might any changes to RP1 and/or DTB partitions be necessary to match my > newer U-Boot, or does U-Boot use an internal .dtb these days? My understanding is that it uses an internal .dtb. > > Is there any more efficient way to flash just U-Boot? -k LNX possibly? That might work. Jon should know the details. > > I had played with the -L option before (which mentions u-boot-dtb.bin), > but recall it ran into some form of checksum error on boot when passing > it my file... > >> I expect Varun to know the details about ATF, but I'll check if I can >> find some answer myself. > > Thanks again for your efforts. I found out that ATF and optionally a secure OS (Trusty usually) are contained in the file tos.img. The image contains a padded header, followed by bl31.bin and the secure OS binary concatenated. The header format should be pretty straightforward to reverse-engineer (need to change some fields specifying lengths), but I'll ask around if we can get a script to generate it released. Cheers, Mikko > > Regards, > Andreas >