Return-Path: Message-ID: From: michael grosman To: bluez-users@lists.sourceforge.net Subject: Re: [Bluez-users] hciconfig doesn't come up In-Reply-To: <1139993269.26072.25.camel@localhost> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8546_14673737.1140002357649" References: <1139993269.26072.25.camel@localhost> Sender: bluez-users-admin@lists.sourceforge.net Errors-To: bluez-users-admin@lists.sourceforge.net Reply-To: bluez-users@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ users List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 15 Feb 2006 13:19:17 +0200 ------=_Part_8546_14673737.1140002357649 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 2/15/06, Marcel Holtmann wrote: > > Hi Michael, Hi Marcel, > We would like to setup BT communication on embedded MIPS-processor > > Broadcom card with Linux 2.4.20 (patched by patch no.18 of M.Holtman). > > Kernel contained USB support, HID support and BlueTooth support (on > > all layers). > > On this card we're using USB-PCI host-controller of Philips > > (ISP1562ES1). > > We are using Bluez-2.24 library and utils. We also use the library for > > userspace-kernelspace USB translation (libusb-0.1.so.4.4.3). > > the 2.4 kernel series are no longer supported and actually the USB part > of these kernels might be buggy, too. This kernel "slightly" patched by Broadcom (for example, USB 2.0 support downgraded from 2.4.26, etc.), so it is not "really" 2.4.20, but you're right, it's still might be buggy... > We are using CSR based BT dongle with the following description: > > >T: Bus=3D02 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 5 Spd=3D12= MxCh=3D 0> > > >D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D = 1 > > >P: Vendor=3D0a12 ProdID=3D0001 Rev=3D 11.20 > > (as we saw in the supported products list, it is supported.) > > It is fully supported. What build id is this? I know that the Rev equals > the build id, but I always forget how to convert it. I gues that you are you refering to the build ID of the BT dongle firmware. Is there a way to "pull" it from the device? > ># ps -aux > > > PID Uid Stat Command > > > 1 0 S init noinitrd > > > 2 0 S [keventd] > > > 3 0 S [ksoftirqd_CPU0] > > > 4 0 S [kswapd] > > > 5 0 S [bdflush] > > > 6 0 S [kupdated] > > > 7 0 S [mtdblockd] > > > 15 0 S /usr/sbin/dnsmasq > > > 24 0 S /usr/sbin/diag > > > 25 0 S /bin/sh > > > 35 0 S [khubd] > > > 63 0 S [krfcommd] > > > 77 0 S hcid: processing events > > > 80 0 S sdpd > > > 104 0 S hcid: processing events > > > 108 0 S hcid: hci0 init > > > 111 0 S /usr/sbin/hidd --server > > > 124 0 R ps -aux > > Make sure only one hcid is running at a time. We checked with single hcid and there is no difference in the behaviour. > The problem is that hciconfig doesn't come up: > > ># hciconfig > > >hci0: Type: USB > > > BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 > > > DOWN > > > RX bytes:20 acl:0 sco:0 events:2 errors:0 > > > TX bytes:9 acl:0 sco:0 commands:3 errors:0 > > > > When we're trying to wake it up, it failed on timeout: > > ># hciconfig hci0 up > > >Can't init device hci0: Connection timed out (145) > > We received the same timeout reply for version, revision and commands > > requests. > > We received the following reply for features request (# hciconfig hci0 > > features) > > hci0: Type: USB > > BD Address: 00:00:00:00:00:00 ACL MTU: 192:8 SCO MTU: 64:8 > > Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00 > > <3-slot packets> <5-slot packets> > offset> > > > mode> > > > packets> > > > scheme> > > > > > > When we're trying to do the same actions on PC with Linux 2.6.12 > > (using the same USB-PCI card and BT dongle), the only difference that > > after "hciconfig up" it returns the BD address and UP state. Following > > that all hcitool, sdptool, l2ping etc. services worked ok and we could > > establish BT communication. > > Why don't try to use a decent 2.6 kernel for embedded board? This will > make all things a lot easier. Unfortunately, the embedded board supports only 2.4.20 kernel with all its problematic issues. > One additional issue. We see in the product list that our dongle is in > > HCI mode, so we don't have to use hid2hci utility, but for some > > strange reason it doesn't work in any direction (on both Brodacom and > > PC). > > We found that in the list, declared in the file hid2hci.c , this pair > > "vendor-productID" is defined as HID... It's strange. > > You need to have a dongle that actually supports HID proxy. Otherwise > this tool doesn't do anything. We deduct from 2.6 that our dongle supports HCI. Tx, > We see in sources that the socket to AF_BLUETOOTH with BT_PROTOHCI is > > opened successfully and even some of ioctl's succeeded, but HCIDEVUP > > did not... > > > > May someone hint us, what we did wrong. > > Should we change something in the "default" hcid.conf (class device or > > something else)? > > Or should we make something additional configurations? > > We don't find nothing extra in the manuals and HOWTOs... > > How could we fix this HCI connection and move forward in establishing > > BT communication on the described setup? > > Move to a 2.6 kernel, because I think this is a bug inside the USB > subsystem. However if you don't need SCO support, you might wanna > disable the ISOC transfers (SCO support) of the hci_usb driver. Hm... We indeed won't need any SCO support. HCO is not used although curently part of the kernel. How it might influence on our setup? Regards > > Marcel Thanks for your help, Michael. ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > Bluez-users mailing list > Bluez-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-users > ------=_Part_8546_14673737.1140002357649 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

On 2/15/06, Marcel Holtmann <marc= el@holtmann.org> wrote:
Hi Michael,

Hi Marcel,

> We= would like to setup BT communication on embedded MIPS-processor
> Br= oadcom card with Linux=20 2.4.20 (patched by patch no.18 of M.Holtman).
> Kernel contained USB = support, HID support and BlueTooth support (on
> all layers).
>= On this card we're using USB-PCI host-controller of Philips
> (ISP15= 62ES1).
> We are using Bluez-2.24 library and utils. We also use the library= for
> userspace-kernelspace USB translation (libusb-0.1.so.4.4.3).
the 2.4 kernel series are no longer supported and actually the USB pa= rt
of these kernels might be buggy, too.

This kernel "slightly" patched by Broadcom (for example, USB 2.0 support downgraded from 2.4.26, etc.), so it is not "really" 2.4.= 20, but you're right, it's still might be buggy...

> We are= using CSR based BT dongle with the following description:
> >T:&n= bsp; Bus=3D02 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D  = ;5 Spd=3D12  MxCh=3D 0>
> >D:  Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 M= xPS=3D64 #Cfgs=3D  1
> >P:  Vendor=3D0a12 Prod= ID=3D0001 Rev=3D 11.20
> (as we saw in the supported products list, i= t is supported.)

It is fully supported. What build id is this? I kno= w that the Rev equals
the build id, but I always forget how to convert it.
<= br> I gues that you are you refering to the build ID of the BT dongle firmware.= Is there a way to "pull" it from the device?


> &g= t;# ps -aux
> >  PID  Uid   &nb= sp; Stat Command
> >    1 0   &= nbsp;     S    init noinitrd
> >    2 0      = ;   S    [keventd]
> >  &n= bsp; 3 0         S  =   [ksoftirqd_CPU0]
> >    4 0 &= nbsp;       S    [kswapd]=
> >    5 0      = ;   S    [bdflush]
> >  &n= bsp; 6 0         S  =   [kupdated]
> >    7 0      = ;   S    [mtdblockd]
> >  = 15 0         S   &n= bsp;/usr/sbin/dnsmasq
> >   24 0    =      S    /usr/sbin/diag
> &g= t;   25 0         S =    /bin/sh
> >   35 0   &n= bsp;     S    [khubd]
> >   63 0       &nb= sp; S    [krfcommd]
> >   77 0 =         S    hcid: p= rocessing events
> >   80 0     = ;    S    sdpd
> >  1= 04 0         S   &nb= sp;hcid: processing events
> >  108 0   &= nbsp;     S    hcid: hci0 init
> >  111 0       &nb= sp; S    /usr/sbin/hidd --server
> > &nbs= p;124 0         R   =  ps -aux

Make sure only one hcid is running at a time.

We checked with single hcid and there is no difference in the behaviour.
> The pr= oblem is that hciconfig doesn't come up:
> ># hciconfig
> &g= t;hci0:   Type: USB
> >        BD Address: 00= :00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
> >   &nb= sp;    DOWN
> >     &= nbsp;  RX bytes:20 acl:0 sco:0 events:2 errors:0
> >&nbs= p;       TX bytes:9 acl:0 sco:0 commands= :3 errors:0
>
> When we're trying to wake it up, it failed on timeout:
= > ># hciconfig hci0 up
> >Can't init device hci0: Connection= timed out (145)
> We received the same timeout reply for version, re= vision and commands
> requests.
> We received the following reply for features req= uest (# hciconfig hci0
> features)
> hci0:   Type: US= B
>         BD Address: 00:00= :00:00:00:00 ACL MTU: 192:8 SCO MTU: 64:8
>    &n= bsp;    Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>           &= nbsp;     <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
>      &nbs= p;          <timing accuracy> <role switch> <hold mode> <sniff
= > mode>
>         =         <park state> <RSSI> <channel quality> <SCO link> <HV2
> packets>
>     &= nbsp;           <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
> scheme>
>      &n= bsp;          <power control> <transparent SCO>
>
> When we're tr= ying to do the same actions on PC with Linux 2.6.12
> (using the same= USB-PCI card and BT dongle), the only difference that
> after "= hciconfig up" it returns the BD address and UP state. Following
> that all hcitool, sdptool, l2ping etc. services worked ok and we c= ould
> establish BT communication.

Why don't try to use a dece= nt 2.6 kernel for embedded board? This will
make all things a lot easier= .

Unfortunately, the embedded board supports only 2.4.20 kernel with all its = problematic issues.  

> One ad= ditional issue. We see in the product list that our dongle is in
> HC= I mode, so we don't have to use hid2hci utility, but for some
> strange reason it doesn't work in any direction (on both Brodacom = and
> PC).
> We found that in the list, declared in the file hi= d2hci.c , this pair
> "vendor-productID" is defined as HID.= .. It's strange.

You need to have a dongle that actually supports HID proxy. Otherwi= se
this tool doesn't do anything.

We deduct from 2.6 that our dongle supports HCI. Tx,

> We= see in sources that the socket to AF_BLUETOOTH with BT_PROTOHCI is
>= opened successfully and even some of ioctl's succeeded, but HCIDEVUP
> did not...
>
> May someone hint us, what we did wrong.=
> Should we change something in the "default" hcid.conf (c= lass device or
> something else)?
> Or should we make something= additional configurations?
> We don't find nothing extra in the manuals and HOWTOs...
> H= ow could we fix this HCI connection and move forward in establishing
>= ; BT communication on the described setup?

Move to a 2.6 kernel, bec= ause I think this is a bug inside the USB
subsystem. However if you don't need SCO support, you might wanna
di= sable the ISOC transfers (SCO support) of the hci_usb driver.
<= div>
Hm...  We indeed won't need any SCO support. HCO is not used although curently part of the kernel.  How it might influence on our setup?


Regards=

Marcel

Thanks for your help, Michael.
 

-------= ------------------------------------------------
This SF.net email is sp= onsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search = engine that makes
searching your log files as easy as surfing the &= nbsp;web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486= &dat=3D121642
_______________________________________________Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/list= info/bluez-users

------=_Part_8546_14673737.1140002357649-- ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users