Date: Sun, 16 Mar 2003 12:51:49 +0900 From: miniyan <miniyan@kt.rim.or.jp> To: "Maksim Yevmenkin" <Maksim.Yevmenkin@cw.com> Cc: current@FreeBSD.ORG Subject: Re: bluetooth BW-BH02U reset failure Message-ID: <20030316124643.254A.MINIYAN@kt.rim.or.jp> In-Reply-To: <790A8B1F40ACA848939EBD247AE490302794E9@scl8ex04.int.exodus.net> References: <790A8B1F40ACA848939EBD247AE490302794E9@scl8ex04.int.exodus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Maksim, > > At first, I installed 5-CURRENT on P3 machine and sync with cvsup to > > latest. and overwrite 2003-03-05 maksim's bluetooth modules. > > please verify that tarball you have downloaded has both kernel > and userland stuff, i.e. you have sys, share, usr.bin and usr.sbin > in the snapshot's src/ directory. if not please download updated > snapshot from the same location. OK, I checked my copy of 2003-03-05. It only has sys. I'd download latest 2003-03-05 on your directory. I've rebuild environment. > > I tried to use planex(http://www.planex.co.jp/) BW-BH02U BlueTooth USB > > dongle. > > > > I plugged BW-BH02U in to FreeBSD without any ko module. FreeBSD found > > that device with ugen0. following message got with usbdevs -v and udesc_dump. > > ugen(4) is generic USB device driver. you need to load ng_ubt(4) driver > before plugging your device. > > > ugen0: Broadcom product 0x2033, rev 1.01/0.a0, addr 2 > I just mistake device name, it not BW-BH02U. true name is "GW-BH02U". > D-Link DBW-120M, but there is D-Link DWB-120M. it could be that > i mistyped the name. is that the one you have > > http://www.dlink.com/products/usb/dwb120m/ > > the bad news is that page says its Mac only. also it seems in order > to make D-Link DWB-120M work on PC you need to download some sort of > firmware into it. > > according to D-Link there is another adapter D-Link DBT-120 > > http://www.dlink.com/products/usb/dbt120/ > > and the page says it works with Mac & PC. also to make things very > confusing according to BlueZ page there are two revisions of DBT-120. > One has Broadcomm chip (Rev A1) and other CSR chip (Rev B1). The > version with Broadcomm chip (Rev A1) also needs firmware download. > Version with CSR chip (Rev B1) works just as it is. I check that site, but I cannot find any topic and drivers out. also WWW.planex.co.jp does not have any new information. > i will have to go back to the original tester for clarification on that. > sorry i do not have this device my self. No problem. > if you have original D-Link DWB-120M or D-Link DBT-120 (Rev A1) than > for now you out of luck :( i need to get one of these devices myself > to figure out how to download firmware and add proper support in ng_ubt(4) > driver. i have downloaded w2k driver for D-Link DBT-120 and will try > to poke around later. I tried to get DBT-120M, but I cannot get yet. fortunately, I got another device. It is HASEGAWA SYS-COM's HNT-UB01. I checked this device with usbdevs. ng_ubt asked this device is MITSUMI(0x3ee) BT_DONGLE(0x641f) This device is work on my environment(some time failure in "reset", "initialize" I cannot solved yet why that failure). following message is this devices' one. Action is connect -> start -> stop -> disconnect ---------# hcidump HCIDump - HCI packet analyzer ver 1.4 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Reset(0x03|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 4 > HCI Event: Command Status(0x0f) plen 4 < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > HCI Event: Command Complete(0x0e) plen 10 < HCI Command: Read Local Supported Features(0x04|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 12 < HCI Command: Read Buffer Size(0x04|0x0005) plen 0 > HCI Event: Command Complete(0x0e) plen 11 < HCI Command: Write Scan Enable(0x03|0x001a) plen 1 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Write Class of Device(0x03|0x0024) plen 3 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Change Local Name(0x03|0x0013) plen 248 > HCI Event: Command Complete(0x0e) plen 4 ---------- dmesg ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xf, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=10 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=12 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=11 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_l2cap_lower_rcvmsg: ubt0l2cap - HCI node is up, bdaddr: xx:xx:xx:xx:xx:xx, pkt_size=128 bytes, num_pkts=8 ng_btsocket_l2cap_default_msg_input: Updating hook "ubt0l2c", src bdaddr=xx:xx:xx:xx:xx:xx ng_btsocket_l2cap_raw_input: Updating hook "ubt0ctl", src bdaddr=xx:xx:xx:xx:xx:xx ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_intr_complete: ubt0 - Interrupt xfer failed. IOERROR (13) ---- 12 time repeats last 3 lines---- ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt0: at uhub0 port 2 (addr 2) disconnected ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ----- 19 times repeat last line ---- ubt0: detached So back to GW-BT02U, I tried to GW-BT02U again. This device ofcourse failure with "reset" command. I captured hcidump for this. Action is same connect -> start -> stop -> disconnect hcidump log is just follows: ------ hcidump rainfall# hcidump HCIDump - HCI packet analyzer ver 1.4 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Reset(0x03|0x0003) plen 0 ------ dmesg ubt0: Broadcom product 0x2033, rev 1.01/0.a0, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_intr_complete: ubt0 - Interrupt xfer failed. IOERROR (13) ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_intr_complete: ubt0 - Interrupt xfer failed. IOERROR (13) ---- 3 times repert last 4 lines ----- ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ubt_intr_complete: ubt0 - Interrupt xfer failed. IOERROR (13) ----- a report last 3 line ----- ubt0: at uhub0 port 2 (addr 2) disconnected ubt_bulk_in_complete: ubt0 - Bulk-in xfer failed. IOERROR (13) ---- 19 times repert last line ---- ubt0: detached This looks like device not response. I think freebsd should work because MITSUMI's device work. Then this problem relate BroadCom's device. What's next steps? Thanks, Takahiko -- miniyan <miniyan@kt.rim.or.jp> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030316124643.254A.MINIYAN>