mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Tegra2 USB issue
Date: Thu, 24 Jul 2014 18:39:59 +0200	[thread overview]
Message-ID: <1406219999.4590.31.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <20140724204645.108a023a6a3047737e0a2b8a@gmail.com>

Am Donnerstag, den 24.07.2014, 20:46 +0400 schrieb Antony Pavlov:
> On Thu, 24 Jul 2014 18:08:33 +0200
> Lucas Stach <l.stach@pengutronix.de> wrote:
> 
> > Am Donnerstag, den 24.07.2014, 20:05 +0400 schrieb Antony Pavlov:
> > > Hi!
> > > 
> > > I have just tested this commit
> > > 
> > > commit d8bdd537220dd83912949f19ba67029bd1f11c58
> > > Author: Lucas Stach <dev@lynxeye.de>
> > > Date:   Fri Apr 12 12:28:14 2013 +0200
> > > 
> > >     tegra: switch to proper CPU type
> > >     
> > >     Tegras main CPUs are all ARMv7.
> > >     
> > >     Signed-off-by: Lucas Stach <dev@lynxeye.de>
> > >     Tested-by: Antony Pavlov <antonynpavlov@gmail.com>
> > >     Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > 
> > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> > > index bb9b47b..dfb7e24 100644
> > > --- a/arch/arm/Kconfig
> > > +++ b/arch/arm/Kconfig
> > > @@ -137,7 +137,7 @@ config ARCH_VEXPRESS
> > >  
> > >  config ARCH_TEGRA
> > >         bool "Nvidia Tegra-based boards"
> > > -       select CPU_ARM926T
> > > +       select CPU_V7
> > >         select HAS_DEBUG_LL
> > >  
> > >  config ARCH_ZYNQ
> > > 
> > > This commit breaks 'usb' command --- it does not scan devices anymore, just hangs.
> > > 
> > > I have used codesourcery arm-2013.11 toolchain.
> > > 
> > I haven't tested USB myself, as I'm not using second stage barebox after
> > u-boot and there's still things missing for USB to work on first stage.
> > Currently only SDMMMC is fully supported.
> 
> How I can run barebox from barebox (u-boot) on AC100?
> 
Um, how did you test things before? I personally haven't used second
stage for a long time. For u-boot you need to copy the barebox image
into the right spot (0x108000 for T20) and issue 'go' command. For
barebox a 'bootm /path/to/image' should do, but I won't guarantee that I
didn't break anything for second stage.

> > Are you testing exactly this commit? If so you might need to apply
> > 431d8a247dfa63f817cda137a81dbb2244d413dc "arm: properly init alignment
> > trap bit", as USB might trigger an unaligned access.
> 
> Thanks!
> I'll try to apply 431d8a.. tomorrow.
> 
> > > I'll try to check latest barebox from next, but just now I have no means to burn
> > > barebox-tegra20-toshiba-ac100.img into AC100's ROM.
> > > 
> > You'll notice that a newer barebox won't build images for AC100 that are
> > suitable to burn into a boot media, because there are no BCTs publicly
> > available for this device. The resulting AC100 image is only useful for
> > starting with TegraRCM.
> 
> I work with my AC100 remotely so I can't press Ctrl-ESC on every boot for TegraRCM recovery mode.
> How I can run barebox from barebox (u-boot) on AC100?
> 
New barebox has a 'tegrarcm' command that will drop you right into
recovery mode, but obviously won't help if the machine is hanging.

Regards,
Lucas
-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-07-24 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 16:05 Antony Pavlov
2014-07-24 16:08 ` Lucas Stach
2014-07-24 16:46   ` Antony Pavlov
2014-07-24 16:39     ` Lucas Stach [this message]
2014-07-24 19:15       ` Antony Pavlov
2014-07-25 16:41   ` Antony Pavlov

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=1406219999.4590.31.camel@weser.hi.pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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