Hi,
I want to use bluetooth to get a communication between two PC's.
I have a "normal" PC with debian woody, and backports of Kernel 2.4.24 und
the bluez package.
The Second PC is an embedded PC104 with Kernel 2.4.19 called "Viper" and
the with it shipped bluez package
I have also two Acer 510 USB - Bluetooth Dongles
What does works is this:
With hcitool scan the devices find each other.
l2ping works fine in both directions.
I can set up an rfcomm conection by typing
on Debian:
debian:~# rfcomm -i hci0 listen /dev/rfcomm0 5
Waiting for connection on channel 5
Connection from 00:04:3E:C0:8B:30 to /dev/rfcomm0
Press CTRL-C for hangup
on Viper:
rfcomm -i hci0 connect /dev/rfcomm0 00:04:3e:c0:9d:79 5
Connected /dev/rfcomm0 to 00:04:3E:C0:9D:79 on channel 5
Press CTRL-C for hangup
The Problem:
now if i press CTRL-C on the Viper it says the connection is closed, but
debian still says "press CTRL-C to hangup".
And the hci0 device somehow gets crashed, because after the establishment
of the connection I get timeot on hci0 as it shows the following output:
root@viper root# hciconfig -a
hci0: Type: USB
BD Address: 00:04:3E:C0:8B:30 ACL MTU: 1356:5 SCO MTU: 48:1
UP RUNNING PSCAN ISCAN
RX bytes:1800 acl:37 sco:0 events:70 errors:0
TX bytes:1475 acl:39 sco:0 commands:27 errors:0
Features: 0xff 0x07 0x04 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0. Connection timed out(110)
root@viper root# hciconfig hci0 down
root@viper root# hciconfig hci0 up
Can't init device hci0. Connection timed out(110)
root@viper root#
The hci0 device on debian keeps working.
Additionaly I tried to set up a PAN connection instead of rfcomm. I think
this would be my favourite way for communication. This way I can use
/write a normal socket Programm for a communication, can't I?
I type:
debian:~# pand -s -r NAP -M
and
root@viper root# pand -c 00:04:3e:c0:9d:79 --service NAP
I also get the bnep0 devices and can configure them with ifconfig
ping <localip> works, but trying to ping the remote ip i get an error in
"dmesg":
hci_acl_tx_to: hci0 ACL tx timeout
hci_acl_tx_to: hci0 killing stalled ACL connection 00:04:3e:c0:9d:79
I get this error on both sides. and after this on both sides the hci0
device is somehow down in the above mentioned way:
I get timeouts trying to "hciconfig -a" and "hciconfig hci0 up"
any ideas?
would appreciate any help. I'm pretty desperate...
Oh, and even if the rfcomm connection _would_ work. I didn't know how to
use it.
How can I communicate over this? does minicom work? how? or how else can i
use this?
--
MfG,
Christoph Torens
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Christoph,
> #
> # USB Host Controller Drivers
> #
> # CONFIG_USB_EHCI_HCD is not set
> # CONFIG_USB_UHCI is not set
> # CONFIG_USB_UHCI_ALT is not set
> # CONFIG_USB_OHCI is not set
> # CONFIG_USB_OHCI_SA1111 is not set
> CONFIG_USB_ISP116x=m
maybe your host controller is a little bit buggy. I don't know anything
about it.
> #
> # Bluetooth device drivers
> #
> CONFIG_BLUEZ_HCIUSB=m
> CONFIG_BLUEZ_USB_SCO=y
> CONFIG_BLUEZ_USB_ZERO_PACKET=y
Disable USB_SCO and USB_ZERO_PACKET if you don't really need it. The
zero packet should not be needed in any case and disabling the SCO
support safes USB bandwith.
> hm, why does the comment say:
> "USB Bluetooth can only be used with disabled Bluetooth subsystem"
It's about the old bluetooth.o kernel module. See archives for more
details.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
> ask them if they use big or little endian with their Xscale.
i'll ask them, but can't I figure this out somehow manually?
(could probably be faster... ? )
> Show us the
> Bluetooth specific parts of the kernel config.
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_UHCI is not set
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set
# CONFIG_USB_OHCI_SA1111 is not set
CONFIG_USB_ISP116x=m
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_EMI26 is not set
#
# USB Bluetooth can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_MIDI is not set
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
[...]
#
# Bluetooth support
#
CONFIG_BLUEZ=m
CONFIG_BLUEZ_L2CAP=m
CONFIG_BLUEZ_SCO=m
CONFIG_BLUEZ_RFCOMM=m
CONFIG_BLUEZ_RFCOMM_TTY=y
CONFIG_BLUEZ_BNEP=m
CONFIG_BLUEZ_BNEP_MC_FILTER=y
CONFIG_BLUEZ_BNEP_PROTO_FILTER=y
#
# Bluetooth device drivers
#
CONFIG_BLUEZ_HCIUSB=m
CONFIG_BLUEZ_USB_SCO=y
CONFIG_BLUEZ_USB_ZERO_PACKET=y
CONFIG_BLUEZ_HCIUART=m
# CONFIG_BLUEZ_HCIUART_H4 is not set
CONFIG_BLUEZ_HCIUART_BCSP=y
CONFIG_BLUEZ_HCIUART_BCSP_TXCRC=y
# CONFIG_BLUEZ_HCIBFUSB is not set
# CONFIG_BLUEZ_HCIDTL1 is not set
# CONFIG_BLUEZ_HCIBT3C is not set
# CONFIG_BLUEZ_HCIBLUECARD is not set
# CONFIG_BLUEZ_HCIBTUART is not set
# CONFIG_BLUEZ_HCIVHCI is not set
hm, why does the comment say:
"USB Bluetooth can only be used with disabled Bluetooth subsystem"
?
> Run "hcidump -x" to see what is on the ACL link.
root@viper root# pand --search -Q 20 --service NAP -n
pand[320]: PAN daemon ver 1.1
pand[320]: Inquiring
pand[320]: Searching for NAP on 00:04:3E:C0:9D:79
pand[320]: Connecting to 00:04:3E:C0:9D:79
pand[320]: bnep0 connected
root@viper root# ifconfig bnep0 10.0.0.2
root@viper root# hciconfig -a
hci0: Type: USB
BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:526 acl:11 sco:0 events:39 errors:0
TX bytes:675 acl:14 sco:0 commands:19 errors:0
Features: 0xff 0xff 0x0b 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0. Connection timed out(110)
*the hcidump of the above action follows*
root@viper root# hcidump -x
HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Inquiry(0x01|0x0001) plen 5
33 8B 9E 0A 0A
> HCI Event: Command Status(0x0f) plen 4
00 01 01 04
> HCI Event: Inquiry Result(0x02) plen 15
01 79 9D C0 3E 04 00 01 00 00 00 01 00 FD 6C
> HCI Event: Inquiry Complete(0x01) plen 1
00
< HCI Command: Create Connection(0x01|0x0005) plen 13
79 9D C0 3E 04 00 18 CC 01 00 FD EC 01
> HCI Event: Command Status(0x0f) plen 4
00 01 05 04
> HCI Event: Role Change(0x12) plen 8
00 79 9D C0 3E 04 00 01
> HCI Event: Connect Complete(0x03) plen 11
00 28 00 79 9D C0 3E 04 00 01 00
< ACL data: handle 0x0028 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
28 00 0E 00
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> HCI Event: Command Complete(0x0e) plen 6
01 0D 08 00 28 00
> HCI Event: Max Slots Change(0x1b) plen 3
28 00 05
> ACL data: handle 0x0028 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0028 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> ACL data: handle 0x0028 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> ACL data: handle 0x0028 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
< ACL data: handle 0x0028 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0028 flags 0x02 dlen 17
L2CAP(d): cid 0x40 len 13 [psm 1]
SDP SS Req: tid 0x0 len 0x8
pat uuid-16 0x1116 (NAP)
max 0x1
cont 00
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> ACL data: handle 0x0028 flags 0x02 dlen 18
L2CAP(d): cid 0x40 len 14 [psm 1]
SDP SS Rsp: tid 0x0 len 0x9
cur 0x1 tot 0x1 hndl 0x804f230
cont 00
< ACL data: handle 0x0028 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 0x0028 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 15 scid 0x0041
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> ACL data: handle 0x0028 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> ACL data: handle 0x0028 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0041 result 0 status 0
< ACL data: handle 0x0028 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 39682
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> ACL data: handle 0x0028 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0
> ACL data: handle 0x0028 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4
MTU 39682
< ACL data: handle 0x0028 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0028 flags 0x02 dlen 11
L2CAP(d): cid 0x40 len 7 [psm 15]
BNEP: Control(0x01|0)
Setup Req(0x01) size 0x02 dst 0x1116(NAP) src 0x1115(PANU)
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> HCI Event: Number of Completed Packets(0x13) plen 5
01 28 00 01 00
> ACL data: handle 0x0028 flags 0x02 dlen 8
L2CAP(d): cid 0x41 len 4 [psm 15]
BNEP: Control(0x01|0)
Setup Rsp(0x02) res 0x0000
< ACL data: handle 0x0028 flags 0x02 dlen 20
L2CAP(d): cid 0x40 len 16 [psm 15]
BNEP: Control(0x01|0)
Filter MultAddr Set(0x05) len 0x000c
ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
< ACL data: handle 0x0028 flags 0x02 dlen 32
L2CAP(d): cid 0x40 len 28 [psm 15]
BNEP: Control(0x01|0)
Filter MultAddr Set(0x05) len 0x0018
ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
01:00:5e:00:00:01 - 01:00:5e:00:00:01
< ACL data: handle 0x0028 flags 0x02 dlen 32
L2CAP(d): cid 0x40 len 28 [psm 15]
BNEP: Control(0x01|0)
Filter MultAddr Set(0x05) len 0x0018
ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
01:00:5e:00:00:01 - 01:00:5e:00:00:01
< HCI Command: Read Local Name(0x03|0x0014) plen 0
Receive failed: Broken pipe
So, I don't understand this, but to me this looks very unusefull :-(
because there aren't any outputs after the last command "Read Local Name"
the last line takes VERY long ("Receive failed"). I nearly hadn't have
seen it.
But, accidently I found something that is perhaps more wicked.
After a reboot everything works fine:
"hciconfig -a"
"hcitool scan"
but after I put hci0 down manually, I can't get it up again :-(
root@viper root# hciconfig hci0 down
root@viper root# hciconfig hci0 up
Can't init device hci0. Connection timed out(110)
root@viper root# hcidump -x
HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Reset(0x03|0x0003) plen 0
> HCI Event: Command Complete(0x0e) plen 4
01 03 0C 00
< HCI Command: Read Local Supported Features(0x04|0x0003) plen 0
Well, thats bad because this definitly works with the zeevo chip.
I just rechecked that.
--
Regards,
Christoph Torens
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Christoph,
> it's been a few days since my last mail, hope you remeber some facts from
> it.
> I managed to get one Acer 500 BT-Dongle with CSR chipset.
> I also upgraded to Kernel 2.4.21
> this is the latest kernel i can get from the vendor
> (this is "arcom" if anyone knows them
> the embedded pc is a: "Viper Embedded Linux Development Kit")
ask them if they use big or little endian with their Xscale. Show us the
Bluetooth specific parts of the kernel config.
> and now I have the following situation:
>
> root@viper root# hciconfig -a
> hci0: Type: USB
> BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:1810 acl:0 sco:0 events:17 errors:0
> TX bytes:299 acl:0 sco:0 commands:13 errors:0
> Features: 0xff 0xff 0x0b 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0) on viper'
> 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)
>
> root@viper root# pand --search -Q 20 --service NAP -n
> pand[315]: PAN daemon ver 1.1
> pand[315]: Inquiring
> pand[315]: Searching for NAP on 00:04:3E:C0:9D:79
> pand[315]: Connecting to 00:04:3E:C0:9D:79
> pand[315]: bnep0 connected
> root@viper root# hciconfig -a
> hci0: Type: USB
> BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:2380 acl:9 sco:0 events:37 errors:0
> TX bytes:495 acl:9 sco:0 commands:19 errors:0
> Features: 0xff 0xff 0x0b 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0) on viper'
> 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)
>
> root@viper root# ifconfig -a
> bnep0 Link encap:Ethernet HWaddr 00:60:57:0C:88:1A
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> eth0 Link encap:Ethernet HWaddr 00:80:66:10:04:40
> inet addr:192.168.0.50 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:312 errors:1 dropped:0 overruns:1 frame:0
> TX packets:642 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:37644 (36.7 KiB) TX bytes:316263 (308.8 KiB)
> Interrupt:1 Base address:0x9300
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
>
> root@viper root# ifconfig bnep0 10.0.0.2
> root@viper root# hciconfig -a
> hci0: Type: USB
> BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:2657 acl:9 sco:0 events:40 errors:0
> TX bytes:564 acl:12 sco:0 commands:22 errors:0
> Features: 0xff 0xff 0x0b 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Can't read local name on hci0. Connection timed out(110)
> root@viper root#
Run "hcidump -x" to see what is on the ACL link.
> ###
>
> as you can see... I get the bnep connection and the interface bnep0.
> i try to set an ip adress and ...the hci device crashes.
>
> any ideas?
>
> ifconfig works on the other side at my debian-PC.
>
> i have binary packages of bluez-libs provided by arcom
> bluez-pan is not provided by arcom, so i had to cross-compile bluez-libs,
> bluez-sdp and finally bluez-pan
The userspace programs should not be involved, because after the bnep0
device shows up everything is handled by the kernel. Looks like a Xscale
specific bug.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi again,
it's been a few days since my last mail, hope you remeber some facts from
it.
I managed to get one Acer 500 BT-Dongle with CSR chipset.
I also upgraded to Kernel 2.4.21
this is the latest kernel i can get from the vendor
(this is "arcom" if anyone knows them
the embedded pc is a: "Viper Embedded Linux Development Kit")
and now I have the following situation:
root@viper root# hciconfig -a
hci0: Type: USB
BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1810 acl:0 sco:0 events:17 errors:0
TX bytes:299 acl:0 sco:0 commands:13 errors:0
Features: 0xff 0xff 0x0b 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0) on viper'
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)
root@viper root# pand --search -Q 20 --service NAP -n
pand[315]: PAN daemon ver 1.1
pand[315]: Inquiring
pand[315]: Searching for NAP on 00:04:3E:C0:9D:79
pand[315]: Connecting to 00:04:3E:C0:9D:79
pand[315]: bnep0 connected
root@viper root# hciconfig -a
hci0: Type: USB
BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:2380 acl:9 sco:0 events:37 errors:0
TX bytes:495 acl:9 sco:0 commands:19 errors:0
Features: 0xff 0xff 0x0b 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0) on viper'
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)
root@viper root# ifconfig -a
bnep0 Link encap:Ethernet HWaddr 00:60:57:0C:88:1A
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:80:66:10:04:40
inet addr:192.168.0.50 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:312 errors:1 dropped:0 overruns:1 frame:0
TX packets:642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:37644 (36.7 KiB) TX bytes:316263 (308.8 KiB)
Interrupt:1 Base address:0x9300
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
root@viper root# ifconfig bnep0 10.0.0.2
root@viper root# hciconfig -a
hci0: Type: USB
BD Address: 00:60:57:0C:88:1A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:2657 acl:9 sco:0 events:40 errors:0
TX bytes:564 acl:12 sco:0 commands:22 errors:0
Features: 0xff 0xff 0x0b 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0. Connection timed out(110)
root@viper root#
###
as you can see... I get the bnep connection and the interface bnep0.
i try to set an ip adress and ...the hci device crashes.
any ideas?
ifconfig works on the other side at my debian-PC.
i have binary packages of bluez-libs provided by arcom
bluez-pan is not provided by arcom, so i had to cross-compile bluez-libs,
bluez-sdp and finally bluez-pan
by the way, this is my student project (german: Studienarbeit)
--
Regards,
Christoph Torens
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Christoph,
> I will upgrade debian to 2.4.25 tomorrow, this can be done with apt-get :-)
> the viper kernel needs special patches I think... i'm not sure if / how
> this can be done
> I don't think they exist for the newest kernel vversion :-(
build your own Debian kernel package.
http://www.holtmann.org/linux/kernel/debian.html
> root@viper root# hciconfig -a
> hci0: Type: USB
> BD Address: 00:04:3E:C0:8B:30 ACL MTU: 1356:5 SCO MTU: 48:1
> UP RUNNING PSCAN ISCAN
> RX bytes:93 acl:0 sco:0 events:12 errors:0
> TX bytes:296 acl:0 sco:0 commands:12 errors:0
> Features: 0xff 0x07 0x04 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0) on viper'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x86 LMP Ver: 1.1 (0x1) LMP Subver:
> 0x86
> Manufacturer: Telencomm Inc. (18)
>
> This output says nothing about Zeevo, but my win driver definitely says
> Zeevo.
Yes, it does, because Telencomm is Zeevo. This is the TC2001 as I
expected and maybe this chip is not really a good choice for your
"viper" system. If your problems is still there after you have upgraded
your kernel, try to get a CSR based dongle and see how it goes.
> ehm, i thought writing a programm using bnep would be the same as with a
> normal network... and the others? where can i get some reading stuff/
> tutorials on programming each of the three choices?
BlueZ L2CAP and RFCOMM socket programming is mostly the same as if you
are using a UDP or TCP socket.
http://www.holtmann.org/papers/bluetooth/
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
Thanks for the tips, so far
-- comments from Lalith Chakravarthi
> and you should see bluez, usb-uhci, hci_usb, rfcomm, l2cap and bnep
> modules there (doesnt hurt to have extra modules!!)
all running.
I already experienced this stages ;-)
and can say that the error messages were different without loaded
modules...
> make sure you have connected both the dongles and that they are
> up and running.
Jup, l2ping does work for example.
> then, get the daemons running
> motospin> hcid
> motospin> sdpd
also running on both devices
> then on the server side run the pand
> motospin> pand --listen --role GN
> and on the client side
> motospin2> pand --connect --search 20 (20 is the time out value)
i tried this and get the following:
debian:/# pand -n --listen --role GN
pand[3204]: PAN daemon ver 1.1
pand[3205]: New connection from 00:04:3E:C0:8B:30 bnep0
root@viper root# pand -n --search 20 --service GN
pand[161]: PAN daemon ver 1.1
pand[161]: Inquiring
pand[161]: Searching for GN on 00:04:3E:C0:9D:79
pand[161]: Connecting to 00:04:3E:C0:9D:79
> motospin> ifconfig bnep0 10.0.0.1
> motospin2> ifconfig bnep 10.0.0.2
this time i didn't get till here, because:
debian:~# pand -l
bnep0 00:04:3E:C0:8B:30 GN
but pand -l on viper says nothing!
hm, here it seems the viper can't fully establish the connection
At the moment I can't reproduce this other failure message "ACL Timeout".
This does really astonish me, cause i got nothing but this failure for
more than three days, and it was the reason I decided to write to this
list.
-- comments from Marcel Holtmann
> try to use the latest 2.4 or 2.6 kernel on both machines.
I will upgrade debian to 2.4.25 tomorrow, this can be done with apt-get :-)
the viper kernel needs special patches I think... i'm not sure if / how
this can be done
I don't think they exist for the newest kernel vversion :-(
> show us "hciconfig -a" before your system "crashes". I think this Acer
> dongles uses the Zeevo chip
debian:/# hciconfig -a
hci0: Type: USB
BD Address: 00:04:3E:C0:9D:79 ACL MTU: 1356:5 SCO MTU: 48:1
UP RUNNING PSCAN ISCAN
RX bytes:8362 acl:132 sco:0 events:422 errors:0
TX bytes:6736 acl:148 sco:0 commands:197 errors:0
Features: 0xff 0x07 0x04 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0) on debian'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x86 LMP Ver: 1.1 (0x1) LMP Subver:
0x86
Manufacturer: Telencomm Inc. (18)
root@viper root# hciconfig -a
hci0: Type: USB
BD Address: 00:04:3E:C0:8B:30 ACL MTU: 1356:5 SCO MTU: 48:1
UP RUNNING PSCAN ISCAN
RX bytes:93 acl:0 sco:0 events:12 errors:0
TX bytes:296 acl:0 sco:0 commands:12 errors:0
Features: 0xff 0x07 0x04 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0) on viper'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x86 LMP Ver: 1.1 (0x1) LMP Subver:
0x86
Manufacturer: Telencomm Inc. (18)
This output says nothing about Zeevo, but my win driver definitely says
Zeevo.
> You can write a socket program to communicate over L2CAP, RFCOMM or with
> TCP/IP over BNEP. You have to choose ;)
ehm, i thought writing a programm using bnep would be the same as with a
normal network... and the others? where can i get some reading stuff/
tutorials on programming each of the three choices?
--
Regards,
Christoph Torens
ps: netiquette question: should i write this mail only to the list, or to
the list and the nice people who answered me?
don't know :-)
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Christoph,
> I want to use bluetooth to get a communication between two PC's.
> I have a "normal" PC with debian woody, and backports of Kernel 2.4.24 und
> the bluez package.
> The Second PC is an embedded PC104 with Kernel 2.4.19 called "Viper" and
> the with it shipped bluez package
> I have also two Acer 510 USB - Bluetooth Dongles
try to use the latest 2.4 or 2.6 kernel on both machines.
> What does works is this:
> With hcitool scan the devices find each other.
> l2ping works fine in both directions.
> I can set up an rfcomm conection by typing
> on Debian:
> debian:~# rfcomm -i hci0 listen /dev/rfcomm0 5
> Waiting for connection on channel 5
> Connection from 00:04:3E:C0:8B:30 to /dev/rfcomm0
> Press CTRL-C for hangup
>
> on Viper:
> rfcomm -i hci0 connect /dev/rfcomm0 00:04:3e:c0:9d:79 5
> Connected /dev/rfcomm0 to 00:04:3E:C0:9D:79 on channel 5
> Press CTRL-C for hangup
>
> The Problem:
> now if i press CTRL-C on the Viper it says the connection is closed, but
> debian still says "press CTRL-C to hangup".
> And the hci0 device somehow gets crashed, because after the establishment
> of the connection I get timeot on hci0 as it shows the following output:
>
> root@viper root# hciconfig -a
> hci0: Type: USB
> BD Address: 00:04:3E:C0:8B:30 ACL MTU: 1356:5 SCO MTU: 48:1
> UP RUNNING PSCAN ISCAN
> RX bytes:1800 acl:37 sco:0 events:70 errors:0
> TX bytes:1475 acl:39 sco:0 commands:27 errors:0
> Features: 0xff 0x07 0x04 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Can't read local name on hci0. Connection timed out(110)
> root@viper root# hciconfig hci0 down
> root@viper root# hciconfig hci0 up
> Can't init device hci0. Connection timed out(110)
> root@viper root#
Show us "hciconfig -a" before your system "crashes". I think this Acer
dongles uses the Zeevo chip.
> Additionaly I tried to set up a PAN connection instead of rfcomm. I think
> this would be my favourite way for communication. This way I can use
> /write a normal socket Programm for a communication, can't I?
You can write a socket program to communicate over L2CAP, RFCOMM or with
TCP/IP over BNEP. You have to choose ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Christopher
I have worked on the 2.4.20-8 kernel ... if it helps, go on with
reading this...
first check if all the modules are there (I know this is the basic
stuff but most errors creep up from here)
motospin> lsmod
and you should see bluez, usb-uhci, hci_usb, rfcomm, l2cap and bnep
modules there (doesnt hurt to have extra modules!!)
make sure you have connected both the dongles and that they are
up and running.
then, get the daemons running
motospin> hcid
motospin> sdpd
motospin2> hcid
motospin2> sdpd
then on the server side run the pand
motospin> pand --listen --role GN
and on the client side
motospin2> pand --connect --search 20 (20 is the time out value)
and then do the ifconfig bnep0 on both the sides..
motospin> ifconfig bnep0 10.0.0.1
motospin2> ifconfig bnep 10.0.0.2
I was able to establish a connection between a laptop with a USB dongle
and a PC with a USB dongle... both on the 2.4.20-8 kernel. I set up the
PS as the gateway and connectd to the net from the laptop also!!!
Hopefully you can also do the same...
regards
lalith
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users