Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	U-Boot <u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org>,
	Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>,
	Mian Yousaf Kaukab <yousaf.kaukab-IBi9RG/b67k@public.gmane.org>,
	Tom Warren <twarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: How to test new bootloaders on Jetson TX1?
Date: Thu, 15 Feb 2018 14:01:33 +0000	[thread overview]
Message-ID: <33de1065-1372-282c-9646-30a63729e08e@nvidia.com> (raw)
In-Reply-To: <8d80b0d3-eaed-b1ab-02c9-86f81ac4b7fa-l3A5Bk7waGM@public.gmane.org>


On 15/02/18 12:32, Andreas Färber wrote:
> Am 15.02.2018 um 10:22 schrieb Jon Hunter:
>> On 15/02/18 01:51, Andreas Färber wrote:
>>> I would like to test the latest version of U-Boot on the Jetson TX1.
> [...]
>>> Here's what I have tried:
>>>
>>> $ sudo ./flash.sh p2371-2180-devkit mmcblk0p1
>> This should work. Which u-boot binary are you copying and where are you
>> copying it?
>>
>> I copy the u-boot-dtb.bin over u-boot.bin in the L4T directory
>> Linux_for_Tegra/bootloader/t186ref/p2771-0000/500/u-boot.bin.
> 
> I downloaded the .rpm from
> https://build.opensuse.org/package/show/hardware:boot/u-boot-p2371-2180
> extracting all of u-boot, u-boot.bin, u-boot.dtb and u-boot-dtb.bin to
> bootloader/t210ref/p2371-2180/ - and as described it makes a difference
> in that it then ceases to boot to a U-Boot prompt.

Sorry, looks like I mixed TX1 and TX2. I see you are using TX1. However,
I believe you are still booting the wrong u-boot file.

If you look at the p2371-2180-devkit.conf you will see that it has ...

 DFLT_KERNEL_IMAGE="bootloader/${target_board}/p2371-2180/u-boot.bin

For using the upstream u-boot, we need to use the u-boot-dtb.bin and not
the u-boot.bin. So you can either ...

1. Update the p2371-2180-devkit.conf to use the u-boot-dtb.bin that you
copied.
2. Move the u-boot-dtb.bin from your rpm to
bootloader/t210ref/p2371-2180/u-boot.bin.

Cheers
Jon

-- 
nvpublic

  parent reply	other threads:[~2018-02-15 14:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15  1:51 How to test new bootloaders on Jetson TX1? Andreas Färber
     [not found] ` <5ff3ffde-653c-ea50-490c-efcc6dccecc2-l3A5Bk7waGM@public.gmane.org>
2018-02-15  7:56   ` Mikko Perttunen
     [not found]     ` <2089c895-7992-9741-a471-fae5b410d4b7-/1wQRMveznE@public.gmane.org>
2018-02-15 13:25       ` Andreas Färber
     [not found]         ` <8320e1df-774c-65c1-28ae-96e1b90ad178-l3A5Bk7waGM@public.gmane.org>
2018-02-15 14:22           ` Mikko Perttunen
2018-02-15  9:22   ` Jon Hunter
     [not found]     ` <0247bb39-1f53-5c45-4d37-247813b53b96-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-15 12:32       ` Andreas Färber
     [not found]         ` <8d80b0d3-eaed-b1ab-02c9-86f81ac4b7fa-l3A5Bk7waGM@public.gmane.org>
2018-02-15 14:01           ` Jon Hunter [this message]
     [not found]             ` <33de1065-1372-282c-9646-30a63729e08e-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-15 15:12               ` Andreas Färber
2018-02-15 15:38                 ` Jon Hunter
2018-02-15 15:44                   ` Tom Warren
     [not found]                     ` <d6a44448867a47028685fb0af0005d59-wO81nVYWzR7wKU+G0hyRhFaTQe2KTcn/@public.gmane.org>
2018-02-15 16:57                       ` Varun Wadekar
2018-02-16  3:04                         ` How to test new bootloaders on Jetson TX1? - ATF Andreas Färber
2018-02-16  6:18                           ` Varun Wadekar
     [not found]                             ` <e9728e54-8c58-4586-8863-0f26eb156deb-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-17  5:34                               ` Andreas Färber
2018-02-17  7:04                                 ` Varun Wadekar
2018-02-15 23:38   ` How to test new bootloaders on Jetson TX1? Stephen Warren

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=33de1065-1372-282c-9646-30a63729e08e@nvidia.com \
    --to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=afaerber-l3A5Bk7waGM@public.gmane.org \
    --cc=agraf-l3A5Bk7waGM@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=twarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org \
    --cc=vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=yousaf.kaukab-IBi9RG/b67k@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox