[chirp_users] More baofeng woes (UV-B5)
Scott Martin
Wed May 27 13:13:26 PDT 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/27/2015 02:49 PM, Daniel Lichterman wrote:
> What driver did you use for the cables? Try the ones here:
> http://www.miklor.com/COM/UV_Drivers.php
>
> -Daniel
>
I'm using the prolific drivers in the Linux kernel. The serial device
info is below:
Bus 002 Device 027: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port
[1576/2752]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 3.00
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
Like I said, the radio's xmit light comes on for a second, but then
chirp throws the error I posted in my previous message. I don't think
it's a hub power issue as I've tried it in all the ports available, and
it isn't throwing errors in dmesg. I'm due for a kernel upgrade but
haven't dedicated time to that, yet...
Be well,
Scott
http://mailformat.dan.info/quoting/top-posting.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJVZiVgAAoJEMHo5RVayTw1F0UIAI0sp+MEgF9BpWSAnYHUvaB8
x+j+J324DbqEhbXOouoBgtLlae4229Mmjlt6kVa5gyoqzAGGnGTqYF8XOa73ZccF
HwkzVZl8AJarSPXJpcWNp+AaklNmSoInC7ugOnRcJXnxwGE+T5+HTpR8VlYCBMKd
FhnefVPsgcFLL67W9C0OTU3ND/g124Cz+sjAq0Z2kAtq5EiwhGtQNEciIZC7JKru
GDEPyA8U4DfRUkXWhRSSm1oHZjVsERRe88OFBq+eDQLAEQ3DhUvp75neOevZP2hX
df/qJ3xBHlhRkKe+Ap9gHPK038orXKtlWsgypbHrwMP8S27nAUSzFC6bskSeA5g=
=h6pk
-----END PGP SIGNATURE-----
More information about the chirp_users
mailing list