barebox on gta04

barebox on gta04

[Johannes Schauer]

Hi,

I was booting barebox from git on my "openmoko" gta04 today but what was
not working was the mmc initialization.



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

Re: barebox on gta04

[Robert Schwebel]

On Mon, Oct 24, 2011 at 11:01:52PM +0200, Johannes Schauer wrote:
> I was booting barebox from git on my "openmoko" gta04 today but what was
> not working was the mmc initialization.

Can you send us more information about *what* goes wrong? Do you see
something in the kernel output? Any error messages? Please provide your
boot lot.

rsc
-- 
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

Re: barebox on gta04

[Robert Schwebel]

On Mon, Oct 31, 2011 at 03:05:39PM +0100, Johannes Schauer wrote:
> On Mon, Oct 31, 2011 at 12:57:48PM +0100, Robert Schwebel wrote:
> > Does barebox now work on your gtk04?
>
> nope, I'm relying on input from you guys ;)
>
> > If not, I'd be willing to help with the port, but somebody would
> > have to organze a hardware for us in that case.
>
> if there are no leftover units in munich and you are located in
> germany i could lend you mine for one or two weeks?

We are located in Germany (see signature). However, the variant with the
leftover units would be preferred :-)

rsc
-- 
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

Re: barebox on gta04

[Johannes Schauer]

Hi,

On Mon, Oct 31, 2011 at 12:57:48PM +0100, Robert Schwebel wrote:
> Does barebox now work on your gtk04?

nope, I'm relying on input from you guys ;)

> If not, I'd be willing to help with the port, but somebody would have
> to organze a hardware for us in that case.

if there are no leftover units in munich and you are located in germany
i could lend you mine for one or two weeks?

cheers, josch

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

Re: barebox on gta04

[Robert Schwebel]

Hi Johannes,

On Tue, Oct 25, 2011 at 12:05:35PM +0200, Johannes Schauer wrote:
> > Strange. Should not be the case, no idea what's happening here.
>
> any ideas on what I can try?

Does barebox now work on your gtk04? If not, I'd be willing to help with
the port, but somebody would have to organze a hardware for us in that
case.

rsc
-- 
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

Re: barebox on gta04

[Johannes Schauer]

Hi,

On Tue, Oct 25, 2011 at 10:36:47AM +0200, Sascha Hauer wrote:
> > But after doing that, barebox would just not start anymore when
> > loaded by uboot.
> 
> Strange. Should not be the case, no idea what's happening here.

any ideas on what I can try?

> Look again, we accidently have the same string twice in the driver:
> 
> ./drivers/mci/omap_hsmmc.c:201:                 dev_dbg(hsmmc->dev, "timedout waiting for cc2!\n");
> ./drivers/mci/omap_hsmmc.c:224:                 dev_dbg(hsmmc->dev, "timedout waiting for cc2!\n");
> 
> The one in line 224 should really be "timeout waiting for reset done".
> 
> So what I wanted to know is whether it's the error message in line 201
> or 224 that we see. So please change one of them

I changed both, appending the string of the function calling them
(mmc_init_stream and mmc_init_setup)

when booting I get:


barebox 2011.10.0-00107-gdac6e90-dirty (Oct 25 2011 - 12:00:54)

Board: Texas Instrument's Beagle
omap-hsmmc@omap-hsmmc0: timedout waiting for cc2! (in mmc_init_setup)
Cannot reset the SD/MMC interface

So this is where it comes from.

cheers, josch

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

Re: barebox on gta04

[Sascha Hauer]

On Tue, Oct 25, 2011 at 08:38:50AM +0200, Johannes Schauer wrote:
> 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 ?

Yes, that's what I meant

> But after doing that, barebox
> would just not start anymore when loaded by uboot.

Strange. Should not be the case, no idea what's happening here.

> 
> 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");

Look again, we accidently have the same string twice in the driver:

./drivers/mci/omap_hsmmc.c:201:                 dev_dbg(hsmmc->dev, "timedout waiting for cc2!\n");
./drivers/mci/omap_hsmmc.c:224:                 dev_dbg(hsmmc->dev, "timedout waiting for cc2!\n");

The one in line 224 should really be "timeout waiting for reset done".

So what I wanted to know is whether it's the error message in line 201
or 224 that we see. So please change one of them

> 
> 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
> 

-- 
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

Re: barebox on gta04

[Johannes Schauer]

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

Re: barebox on gta04

[Sascha Hauer]

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

barebox on gta04

[Johannes Schauer]

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!

cheers, josch

PS: sorry for my previous mail which was the result of hitting "y"
instead of "e" in my mutt...

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