public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Takács Áron" <takacs.aron@infracont.hu>
To: linux-bluetooth@vger.kernel.org
Subject: cannot open rfcomm connection from Windows
Date: Mon, 13 Jul 2009 15:48:04 +0200	[thread overview]
Message-ID: <4A5B3B14.2080304@infracont.hu> (raw)

Hi,

I am using bluez on an embedded (ARM) board with linux and try to create
a serial connection to a Windows XP Pc.  (I use two USB Bluetooth
dongles.) My goal is to establish a connection in this direction: linux
is listening, windows is "calling". Now, the situation is the following:
I can pair the two systems, but at the end hcid and dbus-daemon do exit.
I can establish a connection when the WIndows is listening and the linux
(embedded board) is calling. In the opposite - needed - direction I
cannot create the connection. On the Windows machine I get the message:
"Cannot open port COM9. Check the port settings". On the linux board
rfcomm gets 'Terminated", hcid and dbus-daemon exit.

After experiencing this, I made some tests with a linux PC and made the
following observations:

1; If hcid terminates dbus-daemon does also.
2, hcid terminats always with the following messages:
    hcid[3663]: Got disconnected from the system message bus
    hcid[3663]: Shutting down local server
    hcid[3663]: Exit
3; If I try to pair the embedded board with the Linux PC, the situation
is the same as with the Windows PC: pairing ok, but at the end on the
embedded board hcid and dbus-daemon do exit.
4; If I try hcitool cc from the Linux PC, they don't get connected, but
hcid and dbus-daemon do exit (on the embedded board).
5;  I can establish rfcomm connection  between the embedded board
(linux) and the Linux PC in both directions.
6; I can establish a pan connection between the two.  Now the connection
is shown by hcitool con. If I disconnect them by hcitool dc, on the
embedded board hcid and dbus-daemon do exit.

Thank you for your help!


Áron Takács


                 reply	other threads:[~2009-07-13 13:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5B3B14.2080304@infracont.hu \
    --to=takacs.aron@infracont.hu \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox