From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fastboot and MUSB driver on OMAP3
Date: Thu, 15 Jan 2015 12:41:19 +0100 [thread overview]
Message-ID: <1421322079.2417.5.camel@collins> (raw)
In-Reply-To: <1419425936.2269.7.camel@aldrin>
> > The SET_ADDRESS request is received just fine, it then sets
> > musb->ep0_state = MUSB_EP0_STAGE_STATUSIN; but no IRQ arrives to trigger
> > another call to musb_g_ep0_irq. Eventually, the host just sends back
> > another SET_REQUEST. Looking at dmesg on the host (Device not responding
> > to set address), I guess that the device should send something back and
> > it apparently doesn't.
Over the past few days, I have figured part of the problem (I am still
far from being done). I was loading the U-Boot SPL via USB, which
implies that the bootrom sets up the USB link first: that was the key to
that first issue. The controller was simply not being reset properly:
MUSB_POWER_SOFTCONN was still present in the MUSB_POWER register, so I
cleared it early and cleared the interrupt registers as well. Then, the
musb-new driver could work properly.
This is all because the bootrom doesn't cleanly deinit musb (the host
isn't notified of the disconnection when the bootrom starts executing
the loaded software). I'll submit a patch in due time so that the
musb-new driver works with bootrom USB peripherial load.
While working on this, I flashed the U-Boot SPL to the internal memory.
When the device boots from it, with no USB cable attached, neither the
legacy musb driver nor musb-new work properly. I only get the first IRQ
and nothing more. However, as soon as I boot with the bootrom
initializing USB, it works in U-Boot. So there must be an extra step in
the initialization process that the bootrom is taking and U-Boot is
missing.
I have looked at muxing and clocks, everything seems to be fine, so I'm
starting to run out of ideas.
Any suggestion or help appreciated!
--
Paul Kocialkowski, Replicant developer
Replicant is a fully free Android distribution running on several
devices, a free software mobile operating system putting the emphasis on
freedom and privacy/security.
Website: http://www.replicant.us/
Blog: http://blog.replicant.us/
Wiki/tracker/forums: http://redmine.replicant.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150115/028f2318/attachment.pgp>
next prev parent reply other threads:[~2015-01-15 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 12:30 [U-Boot] Fastboot and MUSB driver on OMAP3 Paul Kocialkowski
2014-12-15 17:06 ` Paul Kocialkowski
2014-12-24 12:58 ` Paul Kocialkowski
2015-01-15 11:41 ` Paul Kocialkowski [this message]
2015-01-18 16:33 ` Paul Kocialkowski
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=1421322079.2417.5.camel@collins \
--to=contact@paulk.fr \
--cc=u-boot@lists.denx.de \
/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