nRF51822-060mod - Nordic stack and drivers for the mbed BLE API Mod…

Users » todotani » Code » nRF51822-060mod

Ken Todotani / nRF51822-060mod

Nordic stack and drivers for the mbed BLE API Modified for HRM 1017 and correct DISCONNECT event processing

Fork of nRF51822 by Nordic Semiconductor

History

nRF51822 modified for HRM1017 and correct DISCONNECT event processing. default tip

2014-09-06, by todotani [Sat, 06 Sep 2014 08:03:38 +0000] rev 61

nRF51822 modified for HRM1017 and correct DISCONNECT event processing.

Release 0.1.2: Minor bugfix release.

2014-09-02, by Rohit Grover [Tue, 02 Sep 2014 17:01:18 +0100] rev 60

Release 0.1.2: Minor bugfix release.

Bugfixes
~~~~~~~~

- drop un-necessary app_button.c.

Compatibility
~~~~~~~~~~~~~

Compatible with revision 0.1.0 of the BLE_API.

Release 0.1.1

2014-09-02, by Rohit Grover [Tue, 02 Sep 2014 16:42:56 +0100] rev 59

Release 0.1.1
=============

Minor bugfix release.

Bugfixes
~~~~~~~~

- drop duplicate app_timer.cpp; it's already present in the mbed SDK.
- add missing code for custom_add_in_descriptor() to custom_helper.cpp

Compatibility
~~~~~~~~~~~~~

Compatible with revision 0.1.0 of the BLE_API.

Release 0.1.0

2014-09-02, by Rohit Grover [Tue, 02 Sep 2014 16:15:26 +0100] rev 58

Release 0.1.0
=============

We've achieved significant gains in power consumption: the BLE_Beacon demo now
runs at around 35uA of average current broadcasting once a second at 0dB; when
not using the radio, this demo consumes around 7uA.

Features
~~~~~~~~

- Replace initialization of high-frequency external crystal clock-source with
the use of low-frequency clock. This brings in significant gains in power
consumption.

- Re-implement the micro-second timer on nRF51 using the app_timer module
(which internally uses RTC). This limits the precision of the us_Timer to
30uS; but brings in significant gains in power consumption.

- Reduce the number of available app_timers and the event depths for app-timer
events; this will reduce memory consumption for zero-initialized data by
around 1K.i

- Remove the call to conn_params_init() at startup. This is not mandatory; and
was causing an unnecessary re-negotiation of connection parameters a few
seconds into every connection.

- Reduce default transmission power level to 0dbB (was 4dbB before).

- Reduce min connection interval to 50ms and max to 500ms (previous values
were much larger).

- Replace a few instances of use of wait() with nrf_delay_us().

- onConnection() callback now receives connection-parameters applicable to the
new connection.

- onDataSent() callback now receives a count parameter containing the number of
times notifications were sent out since the last callback.

- A 'reason' parameter has been added to Gap::disconnect() to indicate the
reason for disconnection; and also to the onDisconnection callback to
receive a reason from the remote host.

- disable the app_gpiote module by default.

Bugfixes
~~~~~~~~

- onDataWritten() callback now passes an additional parameter
(GattServer::WriteEventCallback_t) encapsulating the update. This avoids
having to re-fetch the updated characteristic's value attribute. It also
fixes a bug where multiple updates to the characteristic's value-attribute
could get clobbered if they occurred in quick succession before the
callbacks could be processed.

Compatibility
~~~~~~~~~~~~~

Compatible with revision 0.1.0 of the BLE_API.

resolve merge

2014-09-02, by Rohit Grover [Tue, 02 Sep 2014 15:58:06 +0100] rev 57

resolve merge

Release 0.1.0

2014-09-02, by Rohit Grover [Tue, 02 Sep 2014 15:50:05 +0100] rev 56

Release 0.1.0
=============

We've achieved significant gains in power consumption: the BLE_Beacon demo now
runs at around 35uA of average current broadcasting once a second at 0dB; when
not using the radio, this demo consumes around 7uA.

Features
~~~~~~~~

- Replace initialization of high-frequency external crystal clock-source with
the use of low-frequency clock. This brings in significant gains in power
consumption.

- Re-implement the micro-second timer on nRF51 using the app_timer module
(which internally uses RTC). This limits the precision of the us_Timer to
30uS; but brings in significant gains in power consumption.

- Reduce the number of available app_timers and the event depths for app-timer
events; this will reduce memory consumption for zero-initialized data by
around 1K.

- Remove the call to conn_params_init() at startup. This is not mandatory; and
was causing an unnecessary re-negotiation of connection parameters a few
seconds into every connection.

- Reduce default transmission power level to 0dbB (was 4dbB before).

- Reduce min connection interval to 50ms and max to 500ms (previous values
were much larger).

- Replace a few instances of use of wait() with nrf_delay_us().

- onConnection() callback now receives connection-parameters applicable to the
new connection.

- onDataSent() callback now receives a count parameter containing the number of
times notifications were sent out since the last callback.

- A 'reason' parameter has been added to Gap::disconnect() to indicate the
reason for disconnection; and also to the onDisconnection callback to
receive a reason from the remote host.

- disable the app_gpiote module by default.

Bugfixes
~~~~~~~~

- onDataWritten() callback now passes an additional parameter
(GattServer::WriteEventCallback_t) encapsulating the update. This avoids
having to re-fetch the updated characteristic's value attribute. It also
fixes a bug where multiple updates to the characteristic's value-attribute
could get clobbered if they occurred in quick succession before the
callbacks could be processed.

Compatibility
~~~~~~~~~~~~~

Compatible with revision 0.1.0 of the BLE_API.