1710 and USB host
Anyone else having success using the 1710 in USB host mode? Using the latest git kernel, I'm getting the boot messages below. I have a USB key plugged in and it's lighting up, so presumably it's getting powered properly.
Maybe the jumpers aren't set quite right, I don't quite grok the comments around the 'hmc_mode' value in. board-h3.c. In any case, my SW1501 settings are 1=on, and the rest are off.
Thanks for any pointers,
Kevin
isp1301_omap 0-002d: chiprev 2.00, driver 24 August 2004
MUX: initialized N21_1710_GPIO14
usbmon: debugfs is not availableisp1301_omap 0-002d: A-Host sessions ok
ohci ohci: OMAP OHCI
ohci ohci: new USB bus registered, assigned bus number 1 ohci ohci: irq 38, io mem 0xfffba000
ohci ohci: init err (00000000 0000)
ohci ohci: can't start
ohci ohci: startup error -75
ohci ohci: USB bus 1 deregistered
ohci: probe of ohci failed with error -75
Quoted 1 line · Kevin Hilman
Anyone else having success using the 1710 in USB host mode?
Last time I tried it was on a platform where the transceiver wasn't wired up usably, so it was kind of pointless. I expect that's not what you're finding ...
Quoted 7 lines
Using the latest
git kernel, I'm getting the boot messages below. I have a USB key plugged in and it's lighting up, so presumably it's getting powered properly.Maybe the jumpers aren't set quite right, I don't quite grok the comments around the '
hmc_mode' value in.board-h3.c. In any case, my SW1501 settings are 1=on, and the rest are off.
I have no H3, so I can't say whether any of this is sane or not. As I recall, there are two transceivers on that board: OTG, and non-OTG. Ideally both should work. I seem to recall positive reports about using the OTG transciever.
Quoted 4 lines
Thanks for any pointers,
Kevin
Quoted 8 lines
isp1301_omap0-002d: chiprev 2.00, driver 24 August 2004
MUX: initializedN21_1710_GPIO14
usbmon: debugfs is not availableisp1301_omap0-002d: A-Host sessions ok
ohci ohci: OMAP OHCI
ohci ohci: new USB bus registered, assigned bus number 1 ohci ohci: irq 38, io mem0xfffba000
ohci ohci: init err (00000000 0000)
That "init err" means the controlle wasn't responding to basic stuff. Like maybe it wasn't clocked correctly ... you could turn on USB_DEBUG in Kconfig and see if the register dump looks even vaguely sane (like, it should report three ports etc).
- Dave
Quoted 5 lines
ohci ohci: can't start
ohci ohci: startup error -75
ohci ohci: USB bus 1 deregistered
ohci: probe of ohci failed with error -75
Hi Kevin,
Quoted 9 lines · David Brownell
Quoted 8 lines
isp1301_omap0-002d: chiprev 2.00, driver 24 August 2004
MUX: initializedN21_1710_GPIO14
usbmon: debugfs is not availableisp1301_omap0-002d: A-Host sessions ok
ohci ohci: OMAP OHCI
ohci ohci: new USB bus registered, assigned bus number 1 ohci ohci: irq 38, io mem0xfffba000
ohci ohci: init err (00000000 0000)
Quoted 4 lines
That "init err" means the controlle wasn't responding to basic stuff. Like maybe it wasn't clocked correctly ... you could turn on
USB_DEBUGinKconfigand see if the register dump looks even vaguely sane (like, it should report three ports etc).
We have a custom 1710 based board and I see exactly the same error message. Did you solve your problems with the "init err" on the 1710 platform? If yes, what was the solution. Thanks for any input here.
Best regards,
Stefan