From: "François Beaufort" <beaufort.francois@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Write should return error if device is disconnected while expecting a response
Date: Wed, 2 Mar 2016 16:19:45 +0100 [thread overview]
Message-ID: <CAEZxfGPZOj+uHQde5Lzb3G9HyF-vvDR8R29BatccKkOMkcwGSg@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZK35diyf=VMGikSJ79+qR=8F5adLt=ddkaOPv3f2x-Ksg@mail.gmail.com>
It does:
[DFU_Test:/service000c/char000d]# write 01 04
Attempting to write /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000d
[CHG] Device F1:6F:DE:EC:F1:D6 Connected: no
[CHG] Device F1:6F:DE:EC:F1:D6 Connected: yes
[CHG] Device F1:6F:DE:EC:F1:D6 Name: DfuTarg
[CHG] Device F1:6F:DE:EC:F1:D6 Alias: DfuTarg
On Wed, Mar 2, 2016 at 2:31 PM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> Hi François,
>
> On Wed, Mar 2, 2016 at 9:31 AM, François Beaufort
> <beaufort.francois@gmail.com> wrote:
>> When writing to a characteristic and that a disconnection happens
>> before getting a write (error) response, BlueZ should inform that
>> write operation failed.
>> See my real example logs below:
>>
>> [DFU_Test:/service000c/char000d]# write 01 04
>> Attempting to write /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000d
>>
>>
>>
>> < ACL Data TX: Handle 32 flags 0x00 dlen 9
>> [hci0] 5.066808
>> ATT: Write Request (0x12) len 4
>> Handle: 0x000e
>> Data: 0104
>>> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 5.106370
>> Num handles: 1
>> Handle: 32
>> Count: 1
>>> HCI Event: Vendor (0xff) plen 7 [hci0] 5.579396
>> 82 12 95 40 10 36 59 ...@.6Y
>>> HCI Event: Disconnect Complete (0x05) plen 4 [hci0] 5.580376
>> Status: Success (0x00)
>> Handle: 32
>> Reason: Connection Timeout (0x08)
>> @ Device Disconnected: F1:6F:DE:EC:F1:D6 (2) reason 1
>
> Interesting, does bluetoothctl print anything after this?
>
> --
> Luiz Augusto von Dentz
next prev parent reply other threads:[~2016-03-02 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 7:31 Write should return error if device is disconnected while expecting a response François Beaufort
2016-03-02 13:31 ` Luiz Augusto von Dentz
2016-03-02 15:19 ` François Beaufort [this message]
2016-03-03 9:46 ` François Beaufort
2016-03-07 15:36 ` François Beaufort
2016-03-07 15:54 ` Luiz Augusto von Dentz
2016-03-09 10:53 ` Luiz Augusto von Dentz
2016-03-09 12:17 ` François Beaufort
2016-03-10 9:27 ` François Beaufort
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=CAEZxfGPZOj+uHQde5Lzb3G9HyF-vvDR8R29BatccKkOMkcwGSg@mail.gmail.com \
--to=beaufort.francois@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).