search

captaingz2github / btstack

Automatically exported from code.google.com/p/btstack
0 stars 0 forks source link

problems with RFCOMM connection #417

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello there. I modified the example code of https://github.com/byly/uubt/ and 
try to run it on my STM32F2 board connected with an USB Bluetooth dongle. 
Currently I can find the device using
hcitool scan
and obtain information using
hcitool info
But the was no response using
l2ping XX:XX:XX:XX:XX:XX

My problem is that I want to connect to the device using RFCOMM and print the 
string sent from the device. But the is no data received. I tried both using
minicom -D /dev/rfcomm0
or simply
cat /dev/rfcomm0

The info log of btstack shows the connection is completed, but it seems that 
there is no RFCOMM_EVENT_INCOMING_CONNECTION or 
RFCOMM_EVENT_OPEN_CHANNEL_COMPLETE event, thus I can't obtain a valid 
rfcomm_channel_id. Therefore rfcomm_send_internal() is never called. Are there 
any possible reasons to cause this situation? Thanks!

Original issue reported on code.google.com by ming...@gmail.com on 2 Sep 2014 at 8:18

GoogleCodeExporter commented 9 years ago 
Please make this as resolved. Thanks.
It is because there are some problems sending ACL data over USB. Fix it will 
resolve this issue.

Original comment by ming...@gmail.com on 25 Nov 2014 at 6:03

GoogleCodeExporter commented 9 years ago 
Hi. Thanks for reporting back. If you run into something similiar, please use 
the newly added "packet log to console" (see mailing list) and post on the 
mailing list.

Original comment by matthias.ringwald@gmail.com on 25 Nov 2014 at 2:34