Problem with custom service UUID and Notify

RE: Problem with custom service UUID and Notify

Doug_H — Fri, 04 Sep 2015 05:23:27 GMT

Thank you Anders! I haven't tried modifying APP_ERROR_CHECK to trap these errors before a reset. I'll do some research on how to do that now.

RE: Problem with custom service UUID and Notify

Anders Strand — Thu, 03 Sep 2015 13:02:59 GMT

Hey!

This is probably caused by the advertisement packet being longer than the maximum of 31 bytes. See this. Moving a 128 UUID to the scan response packet is normally a good solution. The continous reset loop is caused by the default APP_ERROR_CHECK. If you do not alter it, or #define DEBUG, it will reset the chip. You should always check the return codes of softdevice calls, or most function calls in general :)

It seems you have solved this yourself.

RE: Problem with custom service UUID and Notify

Doug_H — Wed, 02 Sep 2015 08:55:45 GMT

I have resolved part of the problem. The call to ble_on_button_change() handler was hanging because I was calling it from a GPIOTE ISR which is not allowed. I modified the implementation to use the app_scheduler() to move the calling context to main and it works fine now. The system still however hangs on advertising_init() if I try and populate the service UUIDs like this:

 ble_uuid_t adv_uuids[] = {{LBS_UUID_SERVICE, m_lbs.uuid_type}};    

 advdata.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);

 advdata.uuids_complete.p_uuids  = adv_uuids;

If I put the service UUID in the Scan response packet it works fine. But it hangs if I put it in the in the initial advertising data packet. I don't know why.