Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve shutdown to clear BLE API and not just SD #87

Merged
merged 6 commits into from
Dec 15, 2015

Conversation

andresag01
Copy link

Improve the shutdown functionality, such that a call to ble.shutdown() from
the user application clears the API and nRF5x state and NOT only the
SoftDevice. To achieve this the following changes are introduced:

  • Add a protected member cleanup() to nRF5xGap, nRF5xGattClient,
    nRF5xGattServer, nRF5xSecurityManager and nRF5xServiceDiscovery.
  • Modify the shutdown() implementation in nRF5xn such that it also calls the
    static member shutdown() exposed by the BLE API in Gap.h, SecurityManager.h,
    GattClient.h and GattServer.h.
  • Modify nRF5xGattClient, nRF5xGattServer and nRF5xSecurityManager
    classes so that they dynamically create their respective objects only if
    needed. Previously the GattClient, GattServer and SecurityManager objects were
    declared as static, which means that they were always present even though they
    were not always needed. This increases memory consumption unnecessarily.
    Furthermore, pointers to the object instances are stored in static members of
    the classes as specified by the BLE API base classes. This ensures that
    calls to shutdown do not require calls to getInstance() functions that would
    otherwise result in undesired memory allocations.
  • nRF5xGap object is always needed, so this remains allocated statically. But
    the reference in Gap is pointed to this object.

The shutdown procedure is as follows:

  1. The user calls ble.shutdown() which executes the code in nRF5xn::shutdown()
  2. The SoftDevice is shutdown
  3. The static members of Gap.h, SecurityManager.h, GattClient.h and
    GattServer.h are called to clean up their own state.

If at any point an error occur during the last step, BLE_ERROR_INVALID_STATE is
returned.

NOTE: This enhancement also requires changes to the ble module
@rgrover @pan- @LiyouZhou

Improve the shutdown functionality, such that a call to ble.shutdown() from
the user application clears the API and nRF5x state and NOT only the
SoftDevice. To achieve this the following changes are introduced:

* Add a protected member cleanup() to nRF5xGap, nRF5xGattClient,
nRF5xGattServer, nRF5xSecurityManager and nRF5xServiceDiscovery.
* Modify the shutdown() implementation in nRF5xn such that it also calls the
static member shutdown() exposed by the BLE API in Gap.h, SecurityManager.h,
GattClient.h and GattServer.h.
* Modify nRF5xGattClient, nRF5xGattServer and nRF5xSecurityManager
classes so that they dynamically create their respective objects only if
needed. Previously the GattClient, GattServer and SecurityManager objects were
declared as static, which means that they were always present even though they
were not always needed. This increases memory consumption unnecessarily.
Furthermore, pointers to the object instances are stored in static members of
the classes as specified by the BLE API base classes. This ensures that
calls to shutdown do not require calls to getInstance() functions that would
otherwise result in undesired memory allocations.
* nRF5xGap object is always needed, so this remains allocated statically. But
the reference in Gap is pointed to this object.

The shutdown procedure is as follows:

1. The user calls ble.shutdown() which executes the code in nRF5xn::shutdown()
1. The SoftDevice is shutdown
1. The static members of Gap.h, SecurityManager.h, GattClient.h and
GattServer.h are called to clean up their own state.

If at any point an error occur during the last step, BLE_ERROR_INVALID_STATE is
returned.
Andres Amaya Garcia added 2 commits December 11, 2015 18:19
The module is updated to comply with the changes to BLE API regarding correct
shutdown functionality. The following changes are introduced to ble-nrf51822:

* Calls to the old static function shutdown in Gap, GattClient, GattServer and
SecurityManager are removed.
* The cleanup function in Gap, GattClient, GattServer and SecurityManager is
renamed to `reset()` and made public.
* The static references inside nRF5xGap, nRF5xGattClient, nRF5xGattServer and
nRF5xSecurityManager to objects of their own class are moved to nRF5xn.
* The static getInstance accessors in nRF5xGap, nRF5xGattClient,
nRF5xGattServer and nRF5xSecurityManager are removed and their functionality is
moved to the implemented virtual accessors in nRF5xn i.e. getGap(),
getGattClient, etc.
* A static function Instance is added to nRF5xn class to make the transport
object accessible across the module.
@andresag01
Copy link
Author

@rgrover @pan- I have made changes according to comments in this pull request.

/* Shutdown the BLE API and nRF51 glue code */
if (gattServerInstance != NULL &&
gattServerInstance->reset() != BLE_ERROR_NONE) {
return BLE_ERROR_INVALID_STATE;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you return the error code instead of BLE_ERROR_INVALID_STATE ?

@andresag01
Copy link
Author

@rgrover @pan-: Made changes according to comments.

@andresag01
Copy link
Author

@rgrover made changes to make _gapInstance non-static

@rgrover
Copy link
Contributor

rgrover commented Dec 15, 2015

@andresag01 I'm happy with this. Will wait for @pan-

@pan-
Copy link
Member

pan- commented Dec 15, 2015

It's alright, I'm looking for the next PR including onShutdown

pan- added a commit that referenced this pull request Dec 15, 2015
Improve shutdown to clear BLE API and not just SD
@pan- pan- merged commit fd8b73f into ARMmbed:develop Dec 15, 2015
@rgrover
Copy link
Contributor

rgrover commented Dec 15, 2015

ble-nrf51822-2.2.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants