Particularly in the case of the Bootloader.
This is made optional based on a preprocessor macro: USE_APP_TIMER.
Some Nordic code assumes the use of AppTimer, and if we replace it with mbed's timer, then a lot more code gets pulled in than necessary. Ideally this should not have been a problem, but it is, and the bootloader is a bit unforgiving in its size constraints.
=============
Enhancements
~~~~~~~~~~~~
* Changes needed to support v8 of the Nordic SDK.
* provide more detail about BLE spec and fwid in getVersion().
Workarounds
~~~~~~~~~~~
* ble_radio_notification_init requires DISTANCE_800US for now. :(
=============
Enhancements
~~~~~~~~~~~~
* updating to v7.1 of the Nordic SDK. Re-organized file layout to match that from the SDK.
* Allow ble_conn_params to still use APP_TIMER if needed. Particularly in the case of the Bootloader.
This is made optional based on a preprocessor macro: USE_APP_TIMER. Some
Nordic code assumes the use of AppTimer, and if we replace it with mbed's
timer, then a lot more code gets pulled in than necessary. Ideally this
should not have been a problem, but it is, and the bootloader is a bit
unforgiving in its size constraints.
* Add new API: onRadioNotification(). Radio Notification is a feature that
enables ACTIVE and INACTIVE (nACTIVE) signals from the stack that notify the
application when the radio is in use. The ACTIVE signal is sent before the
Radio Event starts. The nACTIVE signal is sent at the end of the Radio
Event. These signals can be used by the application programmer to
synchronize application logic with radio activity. For example, the ACTIVE
signal can be used to shut off external devices to manage peak current drawn
during periods when the radio is on, or to trigger sensor data collection
for transmission in the Radio Event.
Bugfixes
~~~~~~~~
none.
enables ACTIVE and INACTIVE (nACTIVE) signals from the stack that notify the
application when the radio is in use. The ACTIVE signal is sent before the
Radio Event starts. The nACTIVE signal is sent at the end of the Radio
Event. These signals can be used by the application programmer to
synchronize application logic with radio activity. For example, the ACTIVE
signal can be used to shut off external devices to manage peak current drawn
during periods when the radio is on, or to trigger sensor data collection
for transmission in the Radio Event.
Bugfixes
~~~~~~~~
none.
Particularly in the case of the Bootloader.
This is made optional based on a preprocessor macro: USE_APP_TIMER.
Some Nordic code assumes the use of AppTimer, and if we replace it with mbed's timer, then a lot more code gets pulled in than necessary. Ideally this should not have been a problem, but it is, and the bootloader is a bit unforgiving in its size constraints.
==============
Enhancements
~~~~~~~~~~~~
* Updated to use of new APIs for authorizeRead() and authorizeWrite() which
return status.
* Implement APIs for getMinAdvertisingInterval() and variants.
* add #ifdef __cplusplus to pstorage.h
Bugfixes
~~~~~~~~
none.
=============
Enhancements
~~~~~~~~~~~~
* Disregard bytes 2 and 3 when comparing long UUIDs. This is in response to a
user request to avoid zeroing out bytes 2 and 3 when storing long UUIDs
within the class UUID.
* Added optional data and length fields to the return struct for authorized
reads so a new value can be provided for each individual authorization. Pull
request from Marcus Chang.
* Updated return value for nRF51GattServer::updateValue. Will now report when
call fails. Pull request from Marcus Chang.
* Use GattAttribute::Handle_t for GattServer::readValue() and updateValue().
* add code to support getPermittedTxValues().
Bugfixes
~~~~~~~~
* Write permission was not set for 'write without response' characteristics.
Pull request from Marcus Chang.
* When the write-authorization attribute is enabled for a characteristic,
handleDataWritten() should still be called after authorization.
Compatibility
~~~~~~~~~~~~~
This release is backward compatible with 0.2.3.
Rohit Grover