Re: [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave

Marcel Holtmann
2004-09-06T09:17:55Z

Hi Michael,

> > this sounds like a chip limitation. What does "hciconfig -a" say?
>
> Here goes:
>
> BL-554:
>
> hci0: Type: USB
> BD Address: 02:00:F4:18:51:74 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:1787 acl:1 sco:0 events:92 errors:0
> TX bytes:543 acl:1 sco:0 commands:44 errors:0
> Features: 0xff 0xff 0x0f 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0)'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1)
> LMP Subver: 0x175
> Manufacturer: Cambridge Silicon Radio (10)
>
>
> BL-500:
>
> hci0: Type: UART
> BD Address: 02:00:80:EC:7C:4A ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:897 acl:0 sco:0 events:19 errors:0
> TX bytes:634 acl:0 sco:0 commands:20 errors:0
> Features: 0xff 0xff 0x0f 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0)'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x135 LMP Ver: 1.1 (0x1)
> LMP Subver: 0x135
> Manufacturer: Cambridge Silicon Radio (10)
>
>
> Don't get confused by the apparently weird device addresses; this is
> part of my project.

you need at least a HCI 16.4 firmware to get it working. Check my pages
and the "hciconfig hci0 revision" command for more information.

Regards

Marcel