From: Johannes Schauer <j.schauer@email.de>
To: barebox@lists.infradead.org
Cc: gta04-owner@goldelico.com
Subject: Re: barebox on gta04
Date: Tue, 25 Oct 2011 08:38:50 +0200 [thread overview]
Message-ID: <20111025063850.GA19390@hoothoot> (raw)
In-Reply-To: <20111024213413.GR23421@pengutronix.de>
Hi Sascha,
On Mon, Oct 24, 2011 at 11:34:13PM +0200, Sascha Hauer wrote:
> 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.
This is a great idea! So first I loaded the unmodified barebox binary
using:
mmc rescan 0
fatload mmc 0 0x82000000 barebox.bin
go 0x82000000
It started executing and the error was the same as before.
Then I tried doing what you suggested above and commented
arch_init_lowlevel in ./arch/arm/mach-omap/omap3_core.S and I was not
sure what you meant by `pin_mux` as the string appeared nowhere in the
code but I thought you might mean the mux_config in
./arch/arm/boards/omap/board-beagle.c ? But after doing that, barebox
would just not start anymore when loaded by uboot.
So can you give me some more specific advices on what to comment?
> 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"
If I read the code correctly, then my error comes from line
224 of ./drivers/mci/omap_hsmmc.c :
dev_dbg(hsmmc->dev, "timedout waiting for cc2!\n");
I activated this debug message by using "#define DEBUG" on top of the
file. Initially I only got the message "Cannot reset the SD/MMC
interface" from line 1185 in ./drivers/mci/mci-core.c after it tried to
call the init code from omap_hsmmc.c.
But where would you find "timeout waiting for reset done"? I tried to
recursively grep my barebox sources without finding this string?
thanks!
cheers, josch
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-25 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 21:11 barebox on gta04 Johannes Schauer
2011-10-24 21:34 ` Sascha Hauer
2011-10-25 6:38 ` Johannes Schauer [this message]
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=20111025063850.GA19390@hoothoot \
--to=j.schauer@email.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.