Re: Fwd: umodem (4) recognize a CDC-ACM device

From: Hans Petter Selasky <hselasky_at_c2i.net>
Date: Wed, 2 Jun 2010 17:50:17 +0200
On Wednesday 02 June 2010 03:23:47 Garrett Cooper wrote:
> Looks like this device might be a bit quirky... Just forwarding to you
> to see if you had any details for the OP.
> Thanks!
> -Garrett

Hi,

Can you dump the USB descriptors of your device?

usbconfig -u 0 -a 3 dump_device_desc dump_curr_config_desc

0,3 is for ugen0.3

--HPS

> 
> ---------- Forwarded message ----------
> From: Marcelo/Porks <marcelorossi_at_gmail.com>
> Date: Tue, Jun 1, 2010 at 5:41 PM
> Subject: umodem (4) recognize a CDC-ACM device
> To: current <current_at_freebsd.org>
> 
> 
> Hi guys. I have a device[1] that is recognized on Linux by the generic
> CDC-ACM driver and I'm trying to do the same on FreeBSD current with
> umodem (4). But, as you can see, I had no success:
> 
> Jun  1 20:00:54 BARAD-DUR kernel: uhub_reattach_port: port 1 reset
> failed, error=USB_ERR_TIMEOUT
> Jun  1 20:00:54 BARAD-DUR kernel: uhub_reattach_port: device problem
> (USB_ERR_TIMEOUT), disabling port 1
> Jun  1 20:00:55 BARAD-DUR kernel: ugen0.3: <www.recursion.jp> at usbus0
> Jun  1 20:00:55 BARAD-DUR kernel: umodem0: <www.recursion.jp USB-232,
> class 2/0, rev 1.10/1.00, addr 3> on usbus0
> Jun  1 20:00:55 BARAD-DUR kernel: umodem0: data interface 1, has CM
> over data, has no break
> Jun  1 20:00:55 BARAD-DUR kernel: device_attach: umodem0 attach returned 6
> Jun  1 20:00:55 BARAD-DUR kernel: umodem0: <www.recursion.jp USB-232,
> class 2/0, rev 1.10/1.00, addr 3> on usbus0
> Jun  1 20:00:55 BARAD-DUR kernel: umodem0: data interface 1, has CM
> over data, has no break
> Jun  1 20:00:55 BARAD-DUR kernel: device_attach: umodem0 attach returned 6
> 
> Have you some tip for me to make this work on FreeBSD?
> 
> I had put some 'printf' at the source code and noticed that
> umodem_attach() failed at line 378 [2]. The main reason is basically
> that the usbd_transfer_setup() got an endpoint [3] with 'ep->methods
> == NULL' [4] and this leads to "USB_ERR_NO_PIPE" on [5].
> 
> Thanks.
> 
> [1] http://www.recursion.jp/avrcdc/driver.html#linux
> [2] http://fxr.watson.org/fxr/source/dev/usb/serial/umodem.c#L378
> [3] http://fxr.watson.org/fxr/source/dev/usb/usb_transfer.c#L877
> [4] http://fxr.watson.org/fxr/source/dev/usb/usb_transfer.c#L880
> [5] http://fxr.watson.org/fxr/source/dev/usb/usb_transfer.c#L886
> 
Received on Wed Jun 02 2010 - 13:53:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:04 UTC