I have make this question on bluez-users mailing list some time ago, without
answer.
I have tested the D-Link DBT-122 dongle (BCM2035 chipset) with BlueZ-utils
and I find the following features list:
# hciconfig hci0 features
hci0: Type: USB
BD Address: 00:13:46:01:22:90 ACL MTU: 377:10 SCO MTU: 16:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
<transparent SCO> <enhanced iscan> <interlaced iscan>
<interlaced pscan> <AFH cap. slave> <AFH cap. master>
Looking the manufactured specification page of BCM2035 chipset it says that
it implements the Bluetooth v1.2 specification. Nevertheless I found that
it's not true, because this dongle doesn't support the <Inquiry with RSSI>
feature, that belongs to that version and following of the BT specification.
I have also tested other usb dongles, for example CSR BlueCore4,
successfully with this feature:
# hciconfig hci0 features
hci0: Type: USB
BD Address: 00:80:5A:46:2D:51 ACL MTU: 384:8 SCO MTU: 64:8
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO> <broadcast encrypt>
<EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <inquiry with RSSI>
<-----
<extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>
<AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
<AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>
<EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>
Please, could you confirm me that it's impossible to make an "Inquiry with
RSSI" operation with the BCM2035 chipset from Broadcom ?
Do you know on existence of an firmware upgrade for this chipsets that
solves this lack ?
I have asked the same question on D-Link support page without response.
I use Ubuntu Dapper with Kernel v2.6.15 and BlueZ-utils v2.25.
Thanks for your attention.
Best regards.
Hi Javier,
>
> simply try "hciconfig hci0 inqmode 1" and monitor with
> "hcidump -X -V"
> what happens if you call "hcitool scan". I've seen some
> Broadcom chips
> that don't set the feature bit for inquiry with RSSI, but they
> do
> support it.
>
> Regards
>
> Marcel
>
> I try the following (as root) with my D-Link DBT-122 dongle (BCM2035
> chipset):
>
> # hciconfig hci0 inqmode
> Can't read inquiry mode on hci0: Input/output error (5)
> # hciconfig hci0 inqmode 1
> Can't set inquiry mode on hci0: Input/output error (5)
so this chip doesn't support "Inquiry with RSSI".
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Javier,
> I have make this question on bluez-users mailing list some time ago,
> without answer.
>
>
> I have tested the D-Link DBT-122 dongle (BCM2035 chipset) with
> BlueZ-utils and I find the following features list:
>
> # hciconfig hci0 features
> hci0: Type: USB
> BD Address: 00:13:46:01:22:90 ACL MTU: 377:10 SCO MTU: 16:0
> Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
> <timing accuracy> <role switch> <hold mode> <sniff
> mode>
> <RSSI> <channel quality> <SCO link> <HV2 packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <power
> control>
> <transparent SCO> <enhanced iscan> <interlaced iscan>
> <interlaced pscan> <AFH cap. slave> <AFH cap. master>
>
> Looking the manufactured specification page of BCM2035 chipset it says
> that it implements the Bluetooth v1.2 specification. Nevertheless I
> found that it's not true, because this dongle doesn't support the
> <Inquiry with RSSI> feature, that belongs to that version and
> following of the BT specification.
>
>
> I have also tested other usb dongles, for example CSR BlueCore4,
> successfully with this feature:
>
> # hciconfig hci0 features
> hci0: Type: USB
> BD Address: 00:80:5A:46:2D:51 ACL MTU: 384:8 SCO MTU: 64:8
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
> <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
> <timing accuracy> <role switch> <hold mode> <sniff
> mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2
> packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
> scheme>
> <power control> <transparent SCO> <broadcast encrypt>
> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
> <interlaced iscan> <interlaced pscan> <inquiry with
> RSSI> <-----
> <extended SCO> <EV4 packets> <EV5 packets> <AFH cap.
> slave>
> <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
> <AFH cap. master> <AFH class. master> <EDR eSCO 2
> Mbps>
> <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended
> features>
>
>
>
> Please, could you confirm me that it's impossible to make an "Inquiry
> with RSSI" operation with the BCM2035 chipset from Broadcom ?
> Do you know on existence of an firmware upgrade for this chipsets that
> solves this lack ?
simply try "hciconfig hci0 inqmode 1" and monitor with "hcidump -X -V"
what happens if you call "hcitool scan". I've seen some Broadcom chips
that don't set the feature bit for inquiry with RSSI, but they do
support it.
Regards
Marcel
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
2006/5/16, Marcel Holtmann <[email protected]>:
>
> Hi Javier,
>
> > I have make this question on bluez-users mailing list some time ago,
> > without answer.
> >
> >
> > I have tested the D-Link DBT-122 dongle (BCM2035 chipset) with
> > BlueZ-utils and I find the following features list:
> >
> > # hciconfig hci0 features
> > hci0: Type: USB
> > BD Address: 00:13:46:01:22:90 ACL MTU: 377:10 SCO MTU: 16:0
> > Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
> > <3-slot packets> <5-slot packets> <encryption> <slot
> > offset>
> > <timing accuracy> <role switch> <hold mode> <sniff
> > mode>
> > <RSSI> <channel quality> <SCO link> <HV2 packets>
> > <HV3 packets> <u-law log> <A-law log> <CVSD> <power
> > control>
> > <transparent SCO> <enhanced iscan> <interlaced iscan>
> > <interlaced pscan> <AFH cap. slave> <AFH cap. master>
> >
> > Looking the manufactured specification page of BCM2035 chipset it says
> > that it implements the Bluetooth v1.2 specification. Nevertheless I
> > found that it's not true, because this dongle doesn't support the
> > <Inquiry with RSSI> feature, that belongs to that version and
> > following of the BT specification.
> >
> >
> > I have also tested other usb dongles, for example CSR BlueCore4,
> > successfully with this feature:
> >
> > # hciconfig hci0 features
> > hci0: Type: USB
> > BD Address: 00:80:5A:46:2D:51 ACL MTU: 384:8 SCO MTU: 64:8
> > Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
> > <3-slot packets> <5-slot packets> <encryption> <slot
> > offset>
> > <timing accuracy> <role switch> <hold mode> <sniff
> > mode>
> > <park state> <RSSI> <channel quality> <SCO link> <HV2
> > packets>
> > <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
> > scheme>
> > <power control> <transparent SCO> <broadcast encrypt>
> > <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
> > <interlaced iscan> <interlaced pscan> <inquiry with
> > RSSI> <-----
> > <extended SCO> <EV4 packets> <EV5 packets> <AFH cap.
> > slave>
> > <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
> > <AFH cap. master> <AFH class. master> <EDR eSCO 2
> > Mbps>
> > <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended
> > features>
> >
> >
> >
> > Please, could you confirm me that it's impossible to make an "Inquiry
> > with RSSI" operation with the BCM2035 chipset from Broadcom ?
> > Do you know on existence of an firmware upgrade for this chipsets that
> > solves this lack ?
>
> simply try "hciconfig hci0 inqmode 1" and monitor with "hcidump -X -V"
> what happens if you call "hcitool scan". I've seen some Broadcom chips
> that don't set the feature bit for inquiry with RSSI, but they do
> support it.
>
> Regards
>
> Marcel
>
I try the following (as root) with my D-Link DBT-122 dongle (BCM2035
chipset):
# hciconfig hci0 inqmode
Can't read inquiry mode on hci0: Input/output error (5)
# hciconfig hci0 inqmode 1
Can't set inquiry mode on hci0: Input/output error (5)
# hciconfig hci0 inqmode
Can't read inquiry mode on hci0: Input/output error (5)
# hciconfig hci0 inqmode 0
Can't set inquiry mode on hci0: Input/output error (5)
# hciconfig hci0 inqmode
Can't read inquiry mode on hci0: Input/output error (5)
# hcitool inq --flush
Inquiring ...
00:13:FD:D7:CD:B8 clock offset: 0x4cca class: 0x50020c
# hciconfig hci0 inqmode 1
Can't set inquiry mode on hci0: Input/output error (5)
# hcitool inq --flush
Inquiring ...
00:13:FD:D7:CD:B8 clock offset: 0x4cca class: 0x50020c
And these are the lines shown with "hcidump -x":
< HCI Command: Read Inquiry Mode (0x03|0x0044) plen 0
> HCI Event: Command Complete (0x0e) plen 4
01 44 0C 11
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
01
> HCI Event: Command Complete (0x0e) plen 4
01 45 0C 11
< HCI Command: Read Inquiry Mode (0x03|0x0044) plen 0
> HCI Event: Command Complete (0x0e) plen 4
01 44 0C 11
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
00
> HCI Event: Command Complete (0x0e) plen 4
01 45 0C 11
< HCI Command: Read Inquiry Mode (0x03|0x0044) plen 0
> HCI Event: Command Complete (0x0e) plen 4
01 44 0C 11
< HCI Command: Inquiry (0x01|0x0001) plen 5
33 8B 9E 08 00
> HCI Event: Command Status (0x0f) plen 4
00 01 01 04
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CB 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CB 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CB 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CB 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CB 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Complete (0x01) plen 1
00
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
01
> HCI Event: Command Complete (0x0e) plen 4
01 45 0C 11
< HCI Command: Inquiry (0x01|0x0001) plen 5
33 8B 9E 08 00
> HCI Event: Command Status (0x0f) plen 4
00 01 01 04
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C9 4C
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 CA 4C
> HCI Event: Inquiry Complete (0x01) plen 1
00
As you can see it does not change the inquiry mode from "Standard Inquiry"
to "Inquiry with RSSI".
It responds with standard inquiry result events "HCI Event: Inquiry Result
(0x02)", it doesn't respond with "HCI Event: Inquiry Result with RSSI
(0x22)" neither.
On the other hand if I read the possible commands supported in this dongle I
found:
# hciconfig hci0 commands
hci0: Type: USB
BD Address: 00:13:46:01:2D:95 ACL MTU: 377:10 SCO MTU: 16:0
Commands: Octet 0 = 0x7f (Bit 0 1 2 3 4 5 6)
Octet 1 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 2 = 0xaf (Bit 0 1 2 3 5 7)
Octet 3 = 0x01 (Bit 0)
Octet 4 = 0xce (Bit 1 2 3 6 7)
Octet 5 = 0xc7 (Bit 0 1 2 6 7)
Octet 6 = 0xef (Bit 0 1 2 3 5 6 7)
Octet 7 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 8 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 9 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 10 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 11 = 0x9f (Bit 0 1 2 3 4 7)
Octet 12 = 0x03 (Bit 0 1)
Octet 14 = 0xb8 (Bit 3 4 5 7)
Octet 15 = 0x7f (Bit 0 1 2 3 4 5 6)
Octet 16 = 0x04 (Bit 2)
'Inquiry' 'Inquiry Cancel' 'Periodic Inquiry Mode'
'Exit Periodic Inquiry Mode' 'Create Connection' 'Disconnect'
'Add SCO Connection' 'Accept Connection Request'
'Reject Connection Request' 'Link Key Request Reply'
'Link Key Request Negative Reply' 'PIN Code Request Reply'
'PIN Code Request Negative Reply' 'Change Connection Packet Type'
'Authentication Requested' 'Set Connection Encryption'
'Change Connection Link Key' 'Master Link Key' 'Remote Name Request'
'Read Remote Supported Features' 'Read Remote Version Information'
'Read Clock Offset' 'Hold Mode' 'Sniff Mode' 'Exit Sniff Mode'
'QoS Setup' 'Role Discovery' 'Switch Role' 'Read Link Policy
Settings'
'Write Link Policy Settings' 'Set Event Mask' 'Reset'
'Set Event Filter' 'Flush' 'Read PIN Type' 'Write PIN Type'
'Read Stored Link Key' 'Write Stored Link Key'
'Delete Stored Link Key' 'Write Local Name' 'Read Local Name'
'Read Connection Accept Timeout' 'Write Connection Accept Timeout'
'Read Page Timeout' 'Write Page Timeout' 'Read Scan Enable'
'Write Scan Enable' 'Read Page Scan Activity'
'Write Page Scan Activity' 'Read Inquiry Scan Activity'
'Write Inquiry Scan Activity' 'Read Authentication Enable'
'Write Authentication Enable' 'Read Encryption Mode'
'Write Encryption Mode' 'Read Class Of Device' 'Write Class Of
Device'
'Read Voice Setting' 'Write Voice Setting'
'Read Automatic Flush Timeout' 'Write Automatic Flush Timeout'
'Read Num Broadcast Retransmissions'
'Write Num Broadcast Retransmissions' 'Read Hold Mode Activity'
'Write Hold Mode Activity' 'Read Transmit Power Level'
'Read Synchronous Flow Control Enable'
'Write Synchronous Flow Control Enable'
'Set Host Controller To Host Flow Control' 'Host Buffer Size'
'Host Number Of Completed Packets' 'Read Link Supervision Timeout'
'Write Link Supervision Timeout' 'Read Number of Supported IAC'
'Read Current IAC LAP' 'Write Current IAC LAP' 'Read Page Scan Mode'
'Write Page Scan Mode' 'Set AFH Channel Classification'
'Read Local Version Information' 'Read Local Supported Commands'
'Read Local Supported Features' 'Read Buffer Size' 'Read Country
Code'
'Read BD ADDR' 'Read Failed Contact Counter'
'Reset Failed Contact Counter' 'Get Link Quality' 'Read RSSI'
'Read AFH Channel Map' 'Enable Device Under Test Mode'
And "hcidump -x" shows:
< HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 68
01 02 10 00 7F FF AF 01 CE C7 EF FF FF FF FF 9F 03 00 B8 7F
04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
In the list shown there are not the 'Read Inquiry Mode' and 'Write Inquiry
Mode' commands, and for that reason the change (or write) of the inquiry
mode with "hciconfig hci0 inqmode 1" didn't work, and the read of the
inquiry mode with "hciconfig hci0 inqmode" neither.
When I try exactly the same commands with BlueCore4 chipset from CSR, all of
them worked perfectly, for example:
# hciconfig hci0 inqmode <---- Read the inquiry mode
hci0: Type: USB
BD Address: 00:80:5A:46:2D:51 ACL MTU: 384:8 SCO MTU: 64:8
Inquiry mode: Standard Inquiry <---- "Standard Inquiry" mode by
default
# hcitool -i hci0 inquiry --flush <---- First inquiry in "Standard
Inquiry" mode
Inquiring ...
00:13:FD:D7:CD:B8 clock offset: 0x47c0 class: 0x50020c
# hciconfig hci0 inqmode 1 <---- Change the inquiry mode to
"Inquiry with RSSI" mode
# hciconfig hci0 inqmode <---- Read the inquiry mode
hci0: Type: USB
BD Address: 00:80:5A:46:2D:51 ACL MTU: 384:8 SCO MTU: 64:8
Inquiry mode: Inquiry with RSSI <---- It changed correctly !!!!
# hcitool -i hci0 inquiry --flush <---- Second inquiry in "Inquiry
with RSSI" mode
Inquiring ...
00:13:FD:D7:CD:B8 clock offset: 0x46be class: 0x50020c
The "hcidump -x" shows:
< HCI Command: Read Inquiry Mode (0x03|0x0044) plen 0 <---- Read of
the inquiry mode
> HCI Event: Command Complete (0x0e) plen 5
01 44 0C 00 00 <---- The last byte is 00 => "Standard
Inquiry" mode.
< HCI Command: Inquiry (0x01|0x0001) plen 5 <---- First
inquiry in "Standard Inquiry" mode
33 8B 9E 08 00
> HCI Event: Command Status (0x0f) plen 4
00 01 01 04
> HCI Event: Inquiry Result (0x02) plen 15
01 B8 CD D7 FD 13 00 01 00 00 0C 02 50 C0 47
> HCI Event: Inquiry Complete (0x01) plen 1
00
It shows a normal HCI event "Inquiry Result (0x02)". That's right because we
are still in normal inquiry mode. Let's continue.
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1 <---- We change
the inquiry mode to "Inquiry with RSSI" mode
01
> HCI Event: Command Complete (0x0e) plen 4
01 45 0C 00
< HCI Command: Read Inquiry Mode (0x03|0x0044) plen 0 <---- We read
the inquiry mode
> HCI Event: Command Complete (0x0e) plen 5
01 44 0C 00 01 <---- The last byte is 01 => "Inquiry
with RSSI" mode
< HCI Command: Inquiry (0x01|0x0001) plen 5 <---- Second
inquiry in "Inquiry with RSSI" mode
33 8B 9E 08 00
> HCI Event: Command Status (0x0f) plen 4
00 01 01 04
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
01 B8 CD D7 FD 13 00 01 00 0C 02 50 BD 46 AB
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
01 B8 CD D7 FD 13 00 01 00 0C 02 50 BD 46 AD
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
01 B8 CD D7 FD 13 00 01 00 0C 02 50 BD 46 AC
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
01 B8 CD D7 FD 13 00 01 00 0C 02 50 BD 46 AD
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
01 B8 CD D7 FD 13 00 01 00 0C 02 50 BE 46 AD
> HCI Event: Inquiry Complete (0x01) plen 1
00
It shows some HCI events "Inquiry Result with RSSI (0x22)". That's right
because we have changed it.
The last byte shows the RSSI signal level. In this example, the inquiry
results are around 0xAD value.
I repeat the question I made the first time, do you think that it's
impossible to change the inquiry mode to "Inquiry with RSSI" with the
BCM2035 chipset from Broadcom ?
Do you think it would be possible to solve this lack with an firmware
upgrade for this chipset, and in this case do you know on existence of any
public firmware for download ?
Should I do any other kind of tests with my dongles ?
Thanks for all.
Best regards.
Javier.
how you can understand that the dongle does not support <Inquiry with RSSI>.
if this is a code which test it, can you send me the code used to <Inquiry with RSSI> ? In my BT-DG03 chipset compliant with v1.1 and it says
~$ hciconfig hci0 features
hci0:
Type: USB
BD Address: 00:04:61:81:B8:45 ACL MTU: 192:8 SCO MTU: 64:8
Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<transparent SCO>
i am using Ubuntu Breezy badger with Bluez stack.
--- Original Message -----
From: Javier Rodas Gonz?lez
To: [email protected]
Sent: Saturday, May 13, 2006 10:04 PM
Subject: [Bluez-devel] Inquiry with RSSI on Broadcom BCM2035 - not supported ?
I have make this question on bluez-users mailing list some time ago, without answer.
I have tested the D-Link DBT-122 dongle (BCM2035 chipset) with BlueZ-utils and I find the following features list:
# hciconfig hci0 features
hci0: Type: USB
BD Address: 00:13:46:01:22:90 ACL MTU: 377:10 SCO MTU: 16:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
<transparent SCO> <enhanced iscan> <interlaced iscan>
<interlaced pscan> <AFH cap. slave> <AFH cap. master>
Looking the manufactured specification page of BCM2035 chipset it says that it implements the Bluetooth v1.2 specification. Nevertheless I found that it's not true, because this dongle doesn't support the <Inquiry with RSSI> feature, that belongs to that version and following of the BT specification.
I have also tested other usb dongles, for example CSR BlueCore4, successfully with this feature:
# hciconfig hci0 features
hci0: Type: USB
BD Address: 00:80:5A:46:2D:51 ACL MTU: 384:8 SCO MTU: 64:8
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO> <broadcast encrypt>
<EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <inquiry with RSSI> <-----
<extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>
<AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
<AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>
<EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>
Please, could you confirm me that it's impossible to make an "Inquiry with RSSI" operation with the BCM2035 chipset from Broadcom ?
Do you know on existence of an firmware upgrade for this chipsets that solves this lack ?
I have asked the same question on D-Link support page without response.
I use Ubuntu Dapper with Kernel v2.6.15 and BlueZ-utils v2.25.
Thanks for your attention.
Best regards.