From: Thierry Reding <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Adding board support
Date: Thu, 27 Oct 2011 12:29:34 +0200 [thread overview]
Message-ID: <20111027102934.GA24333@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173D51C577-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]
* Stephen Warren wrote:
> Thierry Reding wrote at Thursday, October 20, 2011 1:08 PM:
> > * Stephen Warren wrote:
> > > Thierry Reding wrote at Thursday, October 20, 2011 2:08 AM:
> > > ...
> > > > I've been working some on getting our boards to boot from a device tree.
> > > > Unfortunately, the U-Boot issue seems to be more of a problem than I
> > > > anticipated. Since the mainline U-Boot doesn't run properly,
> > >
> > > What issues are you having? I assume you're referring to something more
> > > than just getting stuff flashed with nvflash.
> >
> > Flashing U-Boot is not the problem, but when booting the device, there's no
> > output whatsoever on the debug port. That's what I meant in one of the
> > previous mails. nvflash says it's loading fastboot.bin at address 0x00108000,
> > and quickboot seems to use the same load address. However, U-Boot is built
> > with CONFIG_SYS_TEXT_BASE set to 0x00E08000. If it is loaded to the same
> > address as fastboot/quickboot it obviously cannot run. So I went ahead and
> > built U-Boot (both mainline and the one from the Chromium repo) with a load
> > address of 0x00108000 - to no avail.
>
> OK, I built U-Boot with load address 0x00108000 and also see nothing at boot.
> So, I've reproduced at least one of your problems.
>
> (This is with an Android-style nvflash that configures the BCT to tell the CPU
> to load/boot the bootloader at address 0x00108000, so this should work.)
>
> So, I've added this observation into the bug I filed. I'll let you know once
> we've had a chance to investigate and/or solve this.
>
> Sorry this isn't working yet; it's pretty early days for U-Boot on Tegra
> outside of ChromeOS, which uses the modified nvflash and hence doesn't hit
> these issues.
I've been able to make limited progress on this. I've been able to
successfully run a mainline U-Boot (c30a15e) with the patches you mentioned
previously applied on top. However, this currently only works as quickboot
payload. Standalone is not working yet. However this allows booting a
mainline kernel with device tree support. So while the nvflash issues are
sorted out, I have something I can get work done with.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-27 10:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 5:49 Adding board support Thierry Reding
[not found] ` <20111014054945.GA32399-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-10-14 16:31 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173BE1A290-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-10-14 18:58 ` Thierry Reding
[not found] ` <20111014185847.GA916-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-10-14 19:20 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173BE1A33E-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-10-14 23:24 ` Thierry Reding
[not found] ` <20111014232404.GB916-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-10-17 10:26 ` Thierry Reding
[not found] ` <20111017102658.GA12373-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-10-17 16:15 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173BE1A4C4-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-10-20 8:08 ` Thierry Reding
[not found] ` <20111020080808.GA5450-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2011-10-20 16:01 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173D51C14B-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-10-20 19:08 ` Thierry Reding
[not found] ` <20111020190827.GA31480-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2011-10-21 20:13 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173D51C577-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-10-25 5:57 ` Thierry Reding
[not found] ` <20111025055737.GB30358-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-10-27 15:47 ` Stephen Warren
2011-10-27 10:29 ` Thierry Reding [this message]
2011-11-09 19:41 ` 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=20111027102934.GA24333@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding-rm9k5ik7kjkj5m59nbduvrnah6klmebb@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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