Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Nov 2015 11:43:47 -0800
From:      Alfred Perlstein <alfred@freebsd.org>
To:        Hans Petter Selasky <hps@selasky.org>, usb@freebsd.org
Subject:   Re: usb modem "Can't setup transfer"
Message-ID:  <5644EBF3.9070605@freebsd.org>
In-Reply-To: <56444E5E.1030706@selasky.org>
References:  <5642B7E4.505@freebsd.org> <5642FE24.4050408@selasky.org> <56439C4B.6060407@freebsd.org> <56444E5E.1030706@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hans,

Thank you, that allows it to attach and the device nodes appear in /dev/

However I then can not seem to send any AT commands and get a response 
via either cu -l /dev/ttyU1 or cu -l /dev/ttyU1.

Any further steps?  Is there a way to virtually share this hardware with 
you?

-Alfred

On 11/12/15 12:31 AM, Hans Petter Selasky wrote:
> On 11/11/15 20:51, Alfred Perlstein wrote:
>>
>
> Hi,
>
> The device is very special in that it uses an interrupt type of 
> endpoint for receiving the data.
>
>>
>>       Endpoint 1
>>          bLength = 0x0007
>>          bDescriptorType = 0x0005
>>          bEndpointAddress = 0x0084  <IN>
>>          bmAttributes = 0x0003  <INTERRUPT>
>>          wMaxPacketSize = 0x003f
>>          bInterval = 0x0002
>>          bRefresh = 0x0000
>>          bSynchAddress = 0x0000
>>
>
> In umodem.c you might want to change the USB matching filter to accept 
> interrupt endpoints:
>
>>         [UMODEM_BULK_RD] = {
>>                 .type = UE_BULK, // change this to UE_BULK_INTR
>>                 .endpoint = UE_ADDR_ANY,
>>                 .direction = UE_DIR_RX,
>
> This change will break other modem drivers, but at least it will give 
> some clues if it works or not.
>
> --HPS
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5644EBF3.9070605>