W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > February 2016

Re: [web-bluetooth] Consider an event when a device is physically disconnected

From: François Beaufort via GitHub <sysbot+gh@w3.org>
Date: Thu, 25 Feb 2016 07:44:49 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-188657168-1456386287-sysbot+gh@w3.org>
For DFU case, the GATT operation (characteristic write) causes the 
remote device to disconnect as you can read at 

> First, you must write the value 0100 to the CCCD for the DFU Control
 Point characteristic to enable DFU notifications. Next, you must 
write the value 01-XX (where XX is the code for the type of image, see
 DFU Control Point) to the DFU Control Point to start a DFU procedure.
 **The application will then disconnect and reset into bootloader/DFU 
mode.** Note that no acknowledgement will be sent when writing to the 
Control Point, but the application sends a GAP disconnect on the link 
to tell the peer that the link is closed. You can then transfer the 
firmware image.


GitHub Notification of comment by beaufortfrancois
Please view or discuss this issue at 
 using your GitHub account
Received on Thursday, 25 February 2016 07:44:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:58:20 UTC