Adding NUS to existing profile - how to get a 'link context' ?

[eyalasko]

Hi, 

I'm trying to add the NUS service to an existing application (freertos based, SDK15.2, already use a custom service)

• I copied the relevant code snippets from the example
• Modified the project setup - Add ble_nus.c & ble_link_ctx_manager.c, increased start address + 0x10 bytes (for the additional service uuid)
• Updated sdk_config.h - increased NRF_SDH_BLE_VS_UUID_COUNT to 2 (was 1 for the prev proprietary service), BLE_NUS_ENABLED = 1

The app builds and runs to the point where I do BLE connect.

The program crash when ble_nus.c on_connect() function calls blcm_link_ctx_get(), as the 1st parameters p_nus->p_link_ctx_storage == NULL.

I had to add ble_link_ctx_manager.c to the project following the example project. However, I couldn't find what it does and how it is used/initialized

Any advice will be appreciated.

Thanks

[goldwake]

are you calling

BLE_NUS_DEF(ble_nus, TOTAL_NUM_CONNECTIONS)

anywhere?

[eyalasko]

Hi, 

I've added the following line at the beginning of main.c (it wouldn't build otherwise)

BLE_NUS_DEF(m_nus, NRF_SDH_BLE_TOTAL_LINK_COUNT);

and the following snippet in services_init() - 

   // Initialize NUS.
    memset(&nus_init, 0, sizeof(nus_init));

    nus_init.data_handler = nus_data_handler;

    err_code = ble_nus_init(&m_nus, &nus_init);
    APP_ERROR_CHECK(err_code);

[Amanda Hsieh]

Hi,

 

What value does blcm_link_ctx_get() return? If p_link_ctx_storage is NULL or contains a NULL pointer, or if pp_ctx_data is NULL, it will return NRF_ERROR_NULL instread of crash. 

For BLE Link Context Manager, you can refer to <nRF5_SDK>\examples\ble_peripheral\ble_app_uart for the usuage. 

Best regards,

Amanda H.

[eyalasko]

Hi Amanda,

p_link_ctx_Storage is not null but it has a null member that causes the crash: p_link_ctx_storage->p_ctx_data_pool.

It crashes at the highlighted line in the screen cap below which is the first line in ble_nus.c on_connect()

[Amanda Hsieh]

Hi, 

BLE Link Ctx storage instance is created together with the NUS service instance. p_link_ctx_storage->p_ctx_data_pool can never be null because its populated during Ctx storage variable declaration in the macro. p_ctx_data_pool gets the value on the connected callback in the ble_nus.c file: on_connect().

p_link_ctx_storage->p_ctx_data_pool is not changed anywhere in the code and it's a constant pointer so we would get a warning if somebody tried to overwrite it.

It's hard to say what causes it. It would be useful to track if some other part of the software accidentally resets this part of memory to NULL. You can check if p_ctx_data_pool is non-null after NUS initialization.

-Amanda H.