ble_issue_tracker.md now the file to track BLE issues in

This commit is contained in:
bluetooth-mdw 2015-09-10 10:06:27 +01:00
parent 2839c131c0
commit d4575c55f1
2 changed files with 7 additions and 30 deletions

View file

@ -1,26 +1,3 @@
# micro:bit BLE profile : Tracking changes from planned specification
This document briefly outlines changes to the planned BLE specification made during implementation.
These are typically made with purpose, so the rationale is also provided where possible.
## LEDService:
* Lose the System LED State characteristic since it cannot be controlled from the BLE MCU.
* Lose the Scrolling State characteristic due to complexity and memory constraints.
## IO Pin Service:
* Simplify the IO Pin Service, possible to expose the edge connector pins only.
* Possibly drop it to save memory and use the event service to transport pin values in either direction. Needs further thought.
## Generic Access Service:
* Device Name and Appearance are mandatory and so need values
* Peripheral Privacy Flag is optional and I dont think we need it.
* Ditto Reconnection Address.
* Ditto Peripheral Preferred Connection Parameters.
## Generic Attribute Service:
* profile design doc/report doesnt show it and its mandatory (issue with Bluetooth Developer Studio).
## Device Information Service:
* All characteristics are optional. Which ones do we really want/need? Save a little memory.....
# micro:bit BLE profile : Changes
See ble _ issue _ tracker.md for Bluetooth Low Energy profile related issues

View file

@ -1,4 +1,4 @@
BLE Issues
# micro:bit BLE - Issue Tracker
----------
Profile Design
@ -7,17 +7,17 @@ Profile Design
OPEN:
D1. Lose the System LED State characteristic since it cannot be controlled from the BLE MCU.
D2. Lose the Scrolling State characteristic complexity and memory constraints
D2. Lose the Scrolling State characteristic complexity and memory constraints
D3. Simplify the IO Pin Service, possible to expose the edge connector pins only. Possibly drop it to save memory and use the event service to transport pin values in either direction. Needs further thought.
D4. Generic Access Service: Peripheral Privacy Flag is optional and I dont think we need it. Ditto Reconnection Address, ditto Peripheral Preferred Connection Parameters.
D4. Generic Access Service: Peripheral Privacy Flag is optional and I dont think we need it. Ditto Reconnection Address, ditto Peripheral Preferred Connection Parameters.
D5. Generic Attribute Service: profile design doc/report doesnt show it and its mandatory (issue with Bluetooth Developer Studio).
D5. Generic Attribute Service: profile design doc/report doesnt show it and its mandatory (issue with Bluetooth Developer Studio).
D6. Device Information Service: All characteristics are optional. Which ones do we really want/need? Save a little memory.....
D7. Why does LED Matrix State support “Write Without Response”? I think this should be plain “Write” so that no further writes are made until theres been an ACK back from the previous one.
D7. Why does LED Matrix State support “Write Without Response”? I think this should be plain “Write” so that no further writes are made until theres been an ACK back from the previous one.
D8. MicroBit Requirements supports Write. This is (ironically and puntastically) wrong. Client should not be able to modify the requirements the MicroBit has.