nRF51822n.cpp@56:a1071b629aa3, 2014-09-02 (annotated)

Committer:

Rohit Grover

Date:

Tue Sep 02 15:50:05 2014 +0100

Revision:

56:a1071b629aa3

Parent:

52:120bd37b9d0d

Child:

79:540d11f2764f

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.

Who changed what in which revision?