From: Sascha Hauer <s.hauer@pengutronix.de>
To: 20111024202514.GA17005@hoothoot
Cc: gta04-owner@goldelico.com, barebox@lists.infradead.org
Subject: Re: barebox on gta04
Date: Mon, 24 Oct 2011 23:34:13 +0200 [thread overview]
Message-ID: <20111024213413.GR23421@pengutronix.de> (raw)
In-Reply-To: <20111024211137.GB19298@hoothoot>
Hi Johannes,
On Mon, Oct 24, 2011 at 11:11:37PM +0200, Johannes Schauer wrote:
> Hi,
>
>
> I was booting barebox from git on my "openmoko" gta04 today but what was
> not working was the mmc initialization.
>
> It was failing in mmc_init_setup() in ./drivers/mci/omap_hsmmc.c after
> printing "timedout waiting for cc2!" when I had DEBUG enabled.
>
> -%<-----------------------------------------------------------------
> barebox 2011.10.0-00107-gdac6e90-dirty (Oct 24 2011 - 22:12:10)
>
> Board: Texas Instrument's Beagle
> omap-hsmmc@omap-hsmmc0: timedout waiting for cc2!
> Cannot reset the SD/MMC interface
> ->%-----------------------------------------------------------------
>
> The gta04 should be very similar to the beagleboard and hence I was
> building using the omap3530_beagle_defconfig.
>
> any hints on how to continue debugging this problem are highly
> appreciated!
You could start barebox from U-Boot (just load the barebox binary image
to RAM and jump to it using the U-Boot 'go' command). Then you could
comment out the lowlevel code from barebox (arch_init_lowlevel, pin_mux)
and see if the problem persists. Maybe there is something different in
the lowlevel code.
Another thing: Where does this string come from? We have this twice in
the driver and one of them should really be "timeout waiting for reset
done"
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-24 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 21:11 Johannes Schauer
2011-10-24 21:34 ` Sascha Hauer [this message]
2011-10-25 6:38 ` Johannes Schauer
2011-10-25 8:36 ` Sascha Hauer
2011-10-25 10:05 ` Johannes Schauer
2011-10-31 11:57 ` Robert Schwebel
2011-10-31 14:05 ` Johannes Schauer
2011-10-31 14:18 ` Robert Schwebel
-- strict thread matches above, loose matches on Subject: below --
2011-10-24 21:01 Johannes Schauer
2011-10-24 21:07 ` Robert Schwebel
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=20111024213413.GR23421@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=20111024202514.GA17005@hoothoot \
--cc=barebox@lists.infradead.org \
--cc=gta04-owner@goldelico.com \
/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