5.1 Migrating Non WME Bluetooth® Low Energy Applications to WME Bluetooth® Low Energy
Applications
Create a new WME BLE application (Refer to
the Getting Started with WME Bluetooth Low Energy Applications from Related Links)
that is consistent with the existing BLE application the user plans to migrate.
Modifications to the
app_ble_handler.c and app_<profile>_handler.c
files, where <profile> may refer to ANCS, ANPS, and so on., can be
incorporated into the WME application by replacing the generated handler file with the
user-modified handler file.
Any code added or modified by users for
BLE-related functionality must be moved to app_ble_callbacks.c and
app_ble_callbacks.h. Similarly, code related to BLE profile functionality
must be moved to app_<profile>_callbacks.c and
app_<profile>_callbacks.h.
In non-WME applications, any code added or
modified by users in the app_module.c and app_module.h
files pertaining to BLE functionality must be moved to app_ble_callbacks.c
and app_ble_callbacks.h. For BLE profile-related functionality, the code
must be moved to app_<profile>_callbacks.c and
app_<profile>_callbacks.h files.
In non-WME applications, code added or
modified by users in app_<profile>.c and
app_<profile>.h files must be moved to
app_<profile>_callbacks.c and
app_<profile>_callbacks.h files.
