From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fastboot and MUSB driver on OMAP3
Date: Sat, 13 Dec 2014 13:30:27 +0100 [thread overview]
Message-ID: <1418473827.2438.7.camel@collins> (raw)
I've been looking at getting fastboot working on my LG Optimus Black
(P970), codename sniper, port. I found out that the BeagleBoard code is
using that too, so I copied the required config options:
#define CONFIG_MUSB_GADGET
#define CONFIG_USB_MUSB_OMAP2PLUS
#define CONFIG_MUSB_PIO_ONLY
#define CONFIG_USB_GADGET_DUALSPEED
#define CONFIG_TWL4030_USB 1
#define CONFIG_USB_ETHER
#define CONFIG_USB_ETHER_RNDIS
#define CONFIG_USB_GADGET
#define CONFIG_USB_GADGET_VBUS_DRAW 0
#define CONFIG_USBDOWNLOAD_GADGET
#define CONFIG_G_DNL_VENDOR_NUM 0x0451
#define CONFIG_G_DNL_PRODUCT_NUM 0xd022
#define CONFIG_G_DNL_MANUFACTURER "TI"
#define CONFIG_CMD_FASTBOOT
#define CONFIG_ANDROID_BOOT_IMAGE
#define CONFIG_USB_FASTBOOT_BUF_ADDR CONFIG_SYS_LOAD_ADDR
#define CONFIG_USB_FASTBOOT_BUF_SIZE 0x07000000
And removed the ones that relate to the legacy code:
-#define CONFIG_MUSB_UDC 1
-#define CONFIG_USB_OMAP3 1
-#define CONFIG_TWL4030_USB 1
-#define CONFIG_USB_DEVICE 1
-#define CONFIG_USB_TTY 1
I also added the relevant "platform" data:
http://git.code.paulk.fr/gitweb/?p=u-boot-sniper.git;a=blob;f=board/lge/sniper/sniper.c;h=d26c695df78d0334c10f35927699ce323c88b514;hb=refs/heads/sniper#l83
The current state of the port is available for reference at:
http://git.code.paulk.fr/gitweb/?p=u-boot-sniper.git;a=shortlog;h=refs/heads/sniper
It is not yet ready to be pushed upstream.
With all this, I run the fastboot command and UART shows:
musb-hdrc: peripheral reset irq lost!
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
and so on until it fails:
[11286.007890] hub 3-0:1.0: unable to enumerate USB device on port 1
So it fails early. Is there something more I need to do in order to get
the new musb driver to work properly on my device?
--
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/20141213/cc83b56e/attachment.pgp>
next reply other threads:[~2014-12-13 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 12:30 Paul Kocialkowski [this message]
2014-12-15 17:06 ` [U-Boot] Fastboot and MUSB driver on OMAP3 Paul Kocialkowski
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=1418473827.2438.7.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