From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Mike <mailinglists@in-box.at>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Bluez with Raspberry Pi for BLE
Date: Mon, 14 Sep 2015 15:39:46 +0300 [thread overview]
Message-ID: <CABBYNZLGjKYF2+aXUupJpNtOQJpY9T9sQpH=D-xU2GP9xj14oQ@mail.gmail.com> (raw)
In-Reply-To: <55F55C99.7070803@in-box.at>
Hi Mike,
On Sun, Sep 13, 2015 at 2:23 PM, Mike <mailinglists@in-box.at> wrote:
> Hi,
>
> I am trying to get my RPi to work with BLE. I downloaded and compiled
> bluez-5.34.tar.xz.
>
> uname -a says: Linux raspberry 4.1.6-v7+ #810 SMP PREEMPT Tue Aug 18
> 15:32:12 BST 2015 armv7l GNU/Linux
>
> My BLE-stick is recognized and hci0 is up and running. I can scan for
> advertising peripherals with "sudo hcitool lescan". This works. But if I
> try to connect to a peripheral I always get Connection refused (111). So
> I looked at the output of hcidump and found that after the connection is
> completed, I get disconnected by remote.
If you are running bluetoothd using hcitool is _not_ recommended,
please use bluetoothctl instead.
Note: Requiring root access should already warn you about that.
> < HCI Command: LE Create Connection (0x08|0x000d) plen 25
> bdaddr 34:B1:F7:D4:FE:F3 type 0
> interval 4 window 4 initiator_filter 0
> own_bdaddr_type 0 min_interval 15 max_interval 15
> latency 0 supervision_to 3200 min_ce 1 max_ce 1
>> HCI Event: Command Status (0x0f) plen 4
> LE Create Connection (0x08|0x000d) status 0x00 ncmd 1
>> HCI Event: LE Meta Event (0x3e) plen 19
> LE Connection Complete
> status 0x00 handle 72, role master
> bdaddr 34:B1:F7:D4:FE:F3 (Public)
> < HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2
> 0000: 48 00 H.
>> HCI Event: Command Status (0x0f) plen 4
> LE Read Remote Used Features (0x08|0x0016) status 0x00 ncmd 1
>> HCI Event: LE Meta Event (0x3e) plen 12
> LE Read Remote Used Features Complete
> status 0x00 handle 72
> Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> < HCI Command: Disconnect (0x01|0x0006) plen 3
> handle 72 reason 0x13
> Reason: Remote User Terminated Connection
>> HCI Event: Command Status (0x0f) plen 4
> Disconnect (0x01|0x0006) status 0x00 ncmd 1
>> HCI Event: Disconn Complete (0x05) plen 4
> status 0x00 handle 72 reason 0x16
> Reason: Connection Terminated by Local Host
>
> I tried three different peripherals and I always get "Connection refused
> (111)". Any ideas would be appreciated.
Perhaps are not running bluetoothd or any other tool to keep the
connection alive, try starting bluetoothd and use bluetoothctl, in
addition you can use org.bluez.GattManager1.RegisterProfile to mark
the device to auto connect (passive scanning):
https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/gatt-api.txt
or using the python test script:
https://git.kernel.org/cgit/bluetooth/bluez.git/tree/test/test-gatt-profile
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2015-09-14 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 11:23 Bluez with Raspberry Pi for BLE Mike
2015-09-14 12:39 ` Luiz Augusto von Dentz [this message]
2015-09-19 7:59 ` Mike
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='CABBYNZLGjKYF2+aXUupJpNtOQJpY9T9sQpH=D-xU2GP9xj14oQ@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mailinglists@in-box.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.