From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fastboot and MUSB driver on OMAP3
Date: Mon, 15 Dec 2014 18:06:18 +0100 [thread overview]
Message-ID: <1418663178.2544.8.camel@collins> (raw)
In-Reply-To: <1418473827.2438.7.camel@collins>
> On the host side, I get the following messages from dmesg:
>
> [11281.565099] usb 3-1: new high-speed USB device number 39 using xhci_hcd
> [11283.178280] usb 3-1: Device not responding to set address.
> [11283.378663] usb 3-1: Device not responding to set address.
> [11283.579739] usb 3-1: device not accepting address 39, error -71
> [11283.939123] usb 3-1: new high-speed USB device number 41 using xhci_hcd
> [11283.939313] usb 3-1: Device not responding to set address.
> [11284.140316] usb 3-1: Device not responding to set address.
> [11284.341381] usb 3-1: device not accepting address 41, error -71
I investigated a bit further and added a few debug prints to U-Boot. If
I understand correctly, IRQs are not actually being used and the
fastboot command is polling on usb_gadget_handle_interrupts.
The status so far is that it still doesn't work on the host. As far as I
can see, it doesn't get as far as enumerating the endpoints (see the log
below).
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.
Do you have any clue?
Here is the relevant U-Boot log:
U-Boot SPL 2015.01-rc2-gfc9200f-dirty (Dec 15 2014 - 17:59:56)
reading u-boot.img
reading u-boot.img
U-Boot 2015.01-rc2-gfc9200f-dirty (Dec 15 2014 - 17:59:56)
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
Sniper + LPDDR/MMC
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
In: serial
Out: serial
Err: serial
musb_register
musb_init_controller
omap2430_musb_init
HS USB OTG: revision 0x40, sysconfig 0x1008, sysstatus 0x1, intrfsel 0x1, simenable 0x0
omap2430_musb_disable
musb_gadget_setup
USB Peripheral mode controller at 480ab000 using PIO, IRQ 0
Hit any key to stop autoboot: 0
usb_gadget_register_driver
musb_gadget_start
musb_start
omap2430_musb_enable
fastboot_add
adding 'f_fastboot'/9fe55240 to config 'usb_dnload'/9fe55180
fastboot_bind IN
fastboot_bind OUT
generic_interrupt: 45 1 0
** IRQ peripheral usb002d tx0001 rx0000
<== Power=f0, DevCtl=98, int_usb=0x2d
csr 0001, count 8, myaddr 0, ep0stage idle
musb-hdrc: peripheral reset irq lost!
musb_g_ep0_irq: power: 0xf0 speed: 0x3
new ep0 state is 6
service_zero_data_request()
service_zero_data_request: SET_ADDRESS
new ep0 state is 4
generic_interrupt: 1 0 0
** IRQ peripheral usb0001 tx0000 rx0000
<== Power=e0, DevCtl=99, int_usb=0x1
generic_interrupt: 4 0 0
** IRQ peripheral usb0004 tx0000 rx0000
<== Power=f0, DevCtl=99, int_usb=0x4
generic_interrupt: 8 0 0
--
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/20141215/c2bfd8ef/attachment.pgp>
next prev parent reply other threads:[~2014-12-15 17:06 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 [this message]
2014-12-24 12:58 ` Paul Kocialkowski
2015-01-15 11:41 ` Paul Kocialkowski
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=1418663178.2544.8.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 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.