[Bluez-users] hcitool scan returns wrong bdaddr

[Paul Wachendorf <pwachend@uni-koeln.de>]

Hi,
I have a strange Problem with hcitool on a ARM CPU based embedded 
system.  I have installed a debian system (tried woody, etch and lenny) 
and tried the bluez-utils from the distribution and self compiled ones. 
The bluetooth device works fine, but when I run a 'hcitool scan' to 
discover the bdaddr of remote devices  it always returns wrong MACs:
# hcitool scan
Scanning ...
        02:01:00:12:EE:58       n/a
        02:02:00:10:C6:81       n/a

on my normal i386 PC running ubuntu linux, using the same bluetooth 
device the output is:
$ hcitool scan
Scanning ...
        00:10:C6:81:48:19       NAME-FB399BACD9
        00:12:EE:58:72:1C       V630i

back again on the ARM box I can successfully l2ping  00:12:EE:58:72:1C 
and an # hcitool name 00:12:EE:58:72:1C
returns "V630i" as suspected , so on I can use ussp-push to send Files 
to my V630i. So the whole bluetooth subsystem seems to work fine, except 
of the discovering of remote MACs.

Does anybody has am idea why this wrong MACs are returned?
Thanks for your help,

Paul


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users