Configuring TASK_APP_* for a fully hosted central

1 post / 0 new
brian
Offline
Last seen:5 years 8 months ago
Expert Master
加入:2014-10-16 18:10
Configuring TASK_APP_* for a fully hosted central

When following the documentation and creating a new project from the template it gets a little confusing especially when making a fully hosted central that exposes no services since there are no examples and there is no documentation. First there is a BLE_APP_MYPROJECT that one defines but it is not clear how to use it or who uses it for what. It appears only in the place where one defines it.

The second is when one wants to add application profiles to the 'app' group. For example, I want to add support for a device information service client. One follows the instructions in section 6 of the UM-B-003 Software Development Guide adding the c and h files and configuring the paths and one is left with a project that will not build because each client application profile app_*.c file contains an undefined task TASK_APP_* and there is no explanation as to what to do with that parameter. Do I need to add it to the rwip_config.h file? Well I cannot because the number of tasks defined there is already equal to 64 which is the maximum.

What is the procedure for configuring / adding an existing application profile (located in dk_apps\src\modules\app\src\app_profiles\) in a fully hosted central?

我注意到我n the file app_api.h there is an enum with a list of SERVER tasks to initialize but there is no corresponding list of client tasks to initialize. Is that an oversight and do I need to define a the set of client tasks here in an analogous manner?

Thanks.