public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-users] i-Tec Bluetooth USB dongle
@ 2004-02-10  7:00 Rudolf Matousek
  2004-02-10  8:21 ` Marcel Holtmann
  0 siblings, 1 reply; 6+ messages in thread
From: Rudolf Matousek @ 2004-02-10  7:00 UTC (permalink / raw)
  To: bluez-users

Hi,

I've recently purchased i-Tec USB dongle. Before the purchase, I checked 
that the dongle is supported by linux Bluez.

Unfortunatelly, the dongle I purchased has different chipset from the 
dongle announced as functional. The chipset is Broadcom with Vendor Id: 
0a5c and Product Id: 200a.

The USB view detects three peripherals after dongle insertion:

  1) Wireless Transceiver for Bluetooth (marked red)
  2) usbkbd
  3) mouse

The detail of the usbview data of the transceiver is attached at the end 
of this email. I tried to use bluefw with the broadcom 2033 firmware. 
Unfortunatelly, I was not able to force the hotplug support to execute 
the bluefw script. I probably somehow missed the meaning of the 
bluefw.usermap file. I inserted one more line with flags 0x0000, and 
vendor and product Ids according to the usbview. With no success.

I also noticed that a file modules.usbmap (in /lib/modules/<kernel no> 
directory) also contains vendor and product IDs to load suitable driver.
It seems that all required modules are loaded correctly.

NOW, my questions: Is there a chance to force this i-Tec donge to work 
with Bluez? Do I need a new firmware binaries from Broadcom? Why the 
hotplug support does not execute bluefw?

Any help is welcome! Cheers,


Ruda Matousek

--

Wireless Transceiver for Bluetooth
Manufacturer: Broadcom
Serial Number: 2035B0CD4060
Speed: 12Mb/s (full)
USB Version:  1.10
Device Class: e0(unk. )
Device Subclass: 01
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0a5c
Product Id: 200a
Revision Number:  1.00

Config Number: 1
	Number of Interfaces: 3
	Attributes: e0
	MaxPower Needed:   0mA

	Interface Number: 0
		Name: hci_usb
		Alternate Number: 0
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 3

			Endpoint Address: 81
			Direction: in
			Attribute: 3
			Type: Int.
			Max Packet Size: 16
			Interval: 1ms

			Endpoint Address: 82
			Direction: in
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

			Endpoint Address: 02
			Direction: out
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

	Interface Number: 1
		Name: hci_usb
		Alternate Number: 0
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 0
			Interval: 1ms

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 0
			Interval: 1ms

	Interface Number: 1
		Name: hci_usb
		Alternate Number: 1
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 9
			Interval: 1ms

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 9
			Interval: 1ms

	Interface Number: 1
		Name: hci_usb
		Alternate Number: 2
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 17
			Interval: 1ms

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 17
			Interval: 1ms

	Interface Number: 1
		Name: hci_usb
		Alternate Number: 3
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 32
			Interval: 1ms

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 32
			Interval: 1ms

	Interface Number: 1
		Name: hci_usb
		Alternate Number: 4
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 64
			Interval: 1ms

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 64
			Interval: 1ms

	Interface Number: 1
		Name: hci_usb
		Alternate Number: 5
		Class: e0(unk. )
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 64
			Interval: 1ms

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 64
			Interval: 1ms

	Interface Number: 2
		Name: (none)
		Alternate Number: 0
		Class: ff(vend.)
		Sub Class: 0
		Protocol: 0
		Number of Endpoints: 2

			Endpoint Address: 84
			Direction: in
			Attribute: 2
			Type: Bulk
			Max Packet Size: 32
			Interval: 0ms

			Endpoint Address: 04
			Direction: out
			Attribute: 2
			Type: Bulk
			Max Packet Size: 32
			Interval: 0ms


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-users] i-Tec Bluetooth USB dongle
  2004-02-10  7:00 [Bluez-users] i-Tec Bluetooth USB dongle Rudolf Matousek
@ 2004-02-10  8:21 ` Marcel Holtmann
       [not found]   ` <402895E4.4040500@utia.cas.cz>
  0 siblings, 1 reply; 6+ messages in thread
From: Marcel Holtmann @ 2004-02-10  8:21 UTC (permalink / raw)
  To: Rudolf Matousek; +Cc: BlueZ Mailing List

Hi Rudolf,

> I've recently purchased i-Tec USB dongle. Before the purchase, I checked 
> that the dongle is supported by linux Bluez.
> 
> Unfortunatelly, the dongle I purchased has different chipset from the 
> dongle announced as functional. The chipset is Broadcom with Vendor Id: 
> 0a5c and Product Id: 200a.

this is not a Broadcom dongle in firmware mode, because it must have id
0a5c:2033. After the firmware was loaded the id is 0a5c:2001.

What is the content of /proc/bus/usb/devices ?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-users] i-Tec Bluetooth USB dongle
       [not found]   ` <402895E4.4040500@utia.cas.cz>
@ 2004-02-10  8:33     ` Marcel Holtmann
       [not found]       ` <40289CAA.8050204@utia.cas.cz>
  0 siblings, 1 reply; 6+ messages in thread
From: Marcel Holtmann @ 2004-02-10  8:33 UTC (permalink / raw)
  To: Rudolf Matousek; +Cc: BlueZ Mailing List

Hi Rudolf,

> T:  Bus=01 Lev=03 Prnt=11 Port=00 Cnt=01 Dev#= 12 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
> P:  Vendor=0a5c ProdID=200a Rev= 1.00
> S:  Manufacturer=Broadcom
> S:  Product=Wireless Transceiver for Bluetooth
> S:  SerialNumber=2035B0CD4060
> C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
> I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
> I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms

this is your Bluetooth device and it is grabbed by the hci_usb driver.
Do it really not work?

> T:  Bus=01 Lev=03 Prnt=11 Port=01 Cnt=02 Dev#= 13 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0a5c ProdID=0099 Rev= 1.00
> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=hid
> E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

> T:  Bus=01 Lev=03 Prnt=11 Port=02 Cnt=03 Dev#= 14 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0a5c ProdID=0097 Rev= 1.00
> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=hid
> E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

These two above are funny, because both are also Broadcom devices. Maybe
your Broadcom dongle has somekind of HID Proxy support, but I don't know
anything about it. Do you see these two if the dongle is unplugged?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-users] i-Tec Bluetooth USB dongle
       [not found]       ` <40289CAA.8050204@utia.cas.cz>
@ 2004-02-10  9:34         ` Marcel Holtmann
       [not found]           ` <4028C63C.8070604@utia.cas.cz>
  2004-02-15 18:09           ` i-Tec Bluetooth USB dongle with CSR chip Zdzislaw A.Kaleta
  0 siblings, 2 replies; 6+ messages in thread
From: Marcel Holtmann @ 2004-02-10  9:34 UTC (permalink / raw)
  To: Rudolf Matousek; +Cc: BlueZ Mailing List

Hi Rudolf,

> I don't see any of these devices when dongle is unplugged. All these 
> devices are definitely integrated in the dongle.
> 
> I guess that the chip may be Broadcom 2035 (see serial no.).
> 
> This is the output of the hciconfig:
> 
> hci0:   Type: USB
>          BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
>          DOWN
>          RX bytes:0 acl:0 sco:0 events:0 errors:0
>          TX bytes:3 acl:0 sco:0 commands:1 errors:0
> 
> # hciconfig hci0 up
> Can't init device hci0. Connection timed out(110)
> 
> # dmesg after dongle insertion
> hub.c: new USB device 00:07.2-2.4, assigned address 15
> hub.c: USB hub found
> hub.c: 3 ports detected
> hub.c: new USB device 00:07.2-2.4.1, assigned address 16
> hub.c: new USB device 00:07.2-2.4.2, assigned address 17
> input: USB HID v1.11 Keyboard [0a5c:0099] on usb1:17.0
> hub.c: new USB device 00:07.2-2.4.3, assigned address 18
> input: USB HID v1.11 Mouse [0a5c:0097] on usb1:18.0
> 
> # /var/log/daemon.log removal and insertion
> 
> Feb 10 09:54:22 Cipisek hcid[739]: HCI dev 0 unregistered
> Feb 10 09:54:36 Cipisek hcid[739]: HCI dev 0 registered
> Feb 10 09:54:46 Cipisek hcid[10193]: Can't init device hci0. Connection 
> timed out(110)
> 
> If you wish, I can create an account on my machine and you can try to 
> dig in by yourself. Maybe you will be much more sucessful.

thanks for the offer, but I can't do anything without proper information
about these dongle. You must log the USB traffic on a Windows machine
with USB SnoopyPro (http://sourceforge.net/projects/usbsnoop/). There
must be some kind of firmware loading or switching stuff to make these
dongle working.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-users] i-Tec Bluetooth USB dongle
       [not found]                     ` <1076519321.2696.61.camel@pegasus>
@ 2004-02-13  7:31                       ` Rudolf Matousek
  0 siblings, 0 replies; 6+ messages in thread
From: Rudolf Matousek @ 2004-02-13  7:31 UTC (permalink / raw)
  To: Marcel Holtmann, bluez-users

Hi Marcel,

I've got no reply from Broadcom yet.

Marcel Holtmann wrote:
> Hi Rudolf,
> 
> 
>>don't you have an advice how to get a sensible usbsnoop log? I installed 
>>snooper on all devices and then I removed and again inserted the dongle. 
>>  Is this procedure right?
> 
> 
> this should show us the initial URB's to get this device working. You
> have it working with Windows? What software do you use?

Well is there a document like "Idiot guide to BT stack"? I mean, a few 
details about the BT layers and implementation?

The dongle is probably running. I tried to detect my Ericsson T39m, but 
unfortunatelly the bluetooth is broken on it (I tested it with T610 and 
a BT handsfree in a shop). Up to now, I don't have a device that I could 
use to verify the functionality of the i-Tec dongle. If my phone is 
broken, then there is a good chance that the dongle is ok. Anyway I'll 
check it with another BT device once it will get one.

I'm using the original software driver provided by i-Tec. The tool is 
probably called BTW v1.4, but who knows. It's a driver CD called 
Bluetooth USB dongle with no vendor...

Regards,


Ruda M.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i-Tec Bluetooth USB dongle with CSR chip
  2004-02-10  9:34         ` Marcel Holtmann
       [not found]           ` <4028C63C.8070604@utia.cas.cz>
@ 2004-02-15 18:09           ` Zdzislaw A.Kaleta
  1 sibling, 0 replies; 6+ messages in thread
From: Zdzislaw A.Kaleta @ 2004-02-15 18:09 UTC (permalink / raw)
  To: Marcel Holtmann, BlueZ Mailing List

I read on the list that there are problems with i-Tec Bluetooth USB dongle.
In November 2002 I try to use this dongle and then, with Bluez instaled as=
=20
exctra pckages, not in kernel I obtain
> hci0: =A0 Type: USB
> =A0 =A0 =A0 =A0 BD Address: 00:08:1B:00:1E:49 ACL MTU: 192:8 =A0SCO MTU: =
64:8
> =A0 =A0 =A0 =A0 UP RUNNING PSCAN ISCAN
> =A0 =A0 =A0 =A0 RX bytes:2864 acl:6 sco:0 events:99 errors:0
> =A0 =A0 =A0 =A0 TX bytes:558 acl:6 sco:0 commands:53 errors:0
> =A0 =A0 =A0 =A0 Features: 0xff 0xff 0x0f 0x00
> =A0 =A0 =A0 =A0 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> =A0 =A0 =A0 =A0 Link policy:
> =A0 =A0 =A0 =A0 Link mode: SLAVE ACCEPT
> =A0 =A0 =A0 =A0 Name: '(none)'
> =A0 =A0 =A0 =A0 Class: 0x000000
> =A0 =A0 =A0 =A0 Service Classes: Unspecified
> =A0 =A0 =A0 =A0 Device Class: Miscellaneous,
> =A0 =A0 =A0 =A0 HCI Ver: 1.1 (0x1) HCI Rev: 0x110 LMP Ver: 1.1 (0x1) LMP =
Subver:
0x110
> =A0 =A0 =A0 =A0 Manufacturer: Cambridge Silicon Radio (10)
Then I stop use this dongle and now I try to check it again and the dongle=
=20
wasn't found by hotplug, usb and my laptop. The /proc/bus/usb/devices not=20
show the dongle.
I try to check on internet and I have found that the dongle that is shown a=
s=20
i-tec look completly diferent that the on I have. My i blue one and may be=
=20
twisted. The new one, at least on photo is black and in differnt shap. May =
by=20
they change the chpsets not changings name as D-Link do with wireless?

I hope this can help. I have one problem? Why the hotplug stop find my dong=
le=20
and how I can solve this.
=2D-=20
z.a.kaleta, registered Linux User #279350

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2004-02-15 18:09 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-10  7:00 [Bluez-users] i-Tec Bluetooth USB dongle Rudolf Matousek
2004-02-10  8:21 ` Marcel Holtmann
     [not found]   ` <402895E4.4040500@utia.cas.cz>
2004-02-10  8:33     ` Marcel Holtmann
     [not found]       ` <40289CAA.8050204@utia.cas.cz>
2004-02-10  9:34         ` Marcel Holtmann
     [not found]           ` <4028C63C.8070604@utia.cas.cz>
     [not found]             ` <1076450519.2777.1.camel@pegasus>
     [not found]               ` <4029E0D7.6010205@utia.cas.cz>
     [not found]                 ` <1076506482.2777.91.camel@pegasus>
     [not found]                   ` <402A3528.6090005@utia.cas.cz>
     [not found]                     ` <1076519321.2696.61.camel@pegasus>
2004-02-13  7:31                       ` Rudolf Matousek
2004-02-15 18:09           ` i-Tec Bluetooth USB dongle with CSR chip Zdzislaw A.Kaleta

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox