AT91RM9200: USB broken?

[Bernd Walter]

On Tue, Jul 20, 2010 at 09:28:26AM -0400, Greg Ansley wrote:
> No, I don't think this is normal. The messages are exactly the same with 
> a known good USB flash drive attached, and the drive is not found.

Those _are_ normal for RM9200 in QFP-208.
The RM9200 has two USB ports - both of them are bonded in the BGA
version and works fine there.
In QFP case however only one is bonded and the second port can't be
terminated properly.
There is an errata in the datasheet about this.
Since it is impossible to find out via software which RM9200 you have
we can't just ignore the secondary port - maybe as a compile time
option, but not for a generic kernel.

The latest current I tested on RM9200 was svn-rev 204418 and USB
was working fine - including those error messages for the faulty
secondary port.

So it looks like your device isn't noticed as being connected at all,
which is a bit strange because your error messages clearly show that
it got the faulty device connected from the secondary port.

Did it ever work for you?
If yes - did you try it with the same USB device?
Do you have an RM9200 in BGA or QFP soldered on your board?

> Same result as far back as 8.0-RELEASE-p4. Since USB works fine on the 
> SAM9G20 card I think I will ignore this for now, so as not to delay what 
> I am doing.
> 
> Greg
> 
> On 7/20/10 8:05 AM, Hans Petter Selasky wrote:
> >On Tuesday 20 July 2010 14:04:53 Greg Ansley wrote:
> >   
> >>While regression testing my patches, I found that USB is not working on
> >>the AT91RM9200 from head (pre-patch). Error shown are the same with or
> >>without a USB device attached.
> >>
> >>Just wondering of anyone has any insights before I spend time going down
> >>this rabbit hole...
> >>
> >>...
> >>usbus0: 12Mbps Full Speed USB v1.0
> >>Root mount waiting for: usbus0
> >>ugen0.1:<Atmel>  at usbus0
> >>uhub0:<Atmel OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1>  on usbus0
> >>uhub0: 2 ports with 2 removable, self powered
> >>Root mount waiting for: usbus0
> >>usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored)
> >>usb_alloc_device: getting device descriptor at addr 2 failed,
> >>USB_ERR_IOERROR
> >>usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR,
> >>ignored)
> >>usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
> >>USB_ERR_IOERROR
> >>Root mount waiting for: usbus0
> >>usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR,
> >>ignored)
> >>Root mount waiting for: usbus0
> >>usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
> >>USB_ERR_IOERROR
> >>ugen0.2:<(null)>  at usbus0 (disconnected)
> >>uhub_reattach_port: could not allocate new device
> >>Trying to mount root from ufs:/dev/mmcsd0s1a
> >>
> >>     
> >Hi,
> >
> >I think those messages are normal, because one of the USB ports is not
> >connected.
> >
> >What messages do you get when plugging in a real USB device?
> >
> >--HPS
> >   
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"

-- 
B.Walter <bernd at bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.