Multilink peripheral error 0x00003401 when connecting with MCP

[Sensors]

I've been playing around with the multi-central central/peripheral examples and I thought I would modify the peripheral to instead use a service I had written for another application, but simply notifies with one byte as the example does.

I copied over the service and characteristic initialisation from main.c and used it in place of my original in core_service.c where my service and service functions reside.

In testing I get some very variable results however...

If I have the central running, and program the peripheral it connects just fine.

If I have the peripheral running first, and try to connect with the MCP app, it throws a 0x00003401 error. I then have to reprogram the device if I want it to work correctly with the central; power cycling isn't enough.

From my reading of other posts I understand this error is related to the status of the CCCD.

So is the Central set up to expect the notification from the peripheral to already be enabled? How can I make this more robust so that the peripheral isn't totally locked out after a 0x00003401 error?

Project attached. I should mention it's being used on custom hardware with TWI communication. ble_app_multilink_peripheral.zip

[Hung Bui]

Hi Sensors,

Could you let me know which function returned 0x00003401 ? This error code means BLE_ERROR_GATTS_SYS_ATTR_MISSING - the system attribute has not been set. You can try to test to call sd_ble_gatts_sys_attr_set() with p_sys_attr_data = NULL.

[Sensors]

I'm actually not sure, since the error handler doesn't give me a line number or file. Usually that's the case when it's something to do with the soft device though. From commenting things it seems to occur during the characteristic update sd_ble_gatts_hvx(m_core_service.conn_handle, &hvx_params);

[Hung Bui]

@Sensors: How did you get the error_code ? You can add a breakpoint in the app_error_handler() to check. Please make sure you have change the optimization level in C/C++ tab in project setting to 0. Have you tried to call sd_ble_gatts_sys_attr_set() with p_sys_attr_data = NULL ?