Problems after switching Project to SDK 5.2.0

RE: Problems after switching Project to SDK 5.2.0

Richard Wurdack — Sat, 14 Jun 2014 00:44:27 GMT

And this problem went away after correctly responding to BLE_GATTS_EVT_SYS_ATTR_MISSING. I hope that helps anyone else who stumbles across this thread.

RE: Problems after switching Project to SDK 5.2.0

Richard Wurdack — Fri, 13 Jun 2014 20:46:34 GMT

I am seeing precisely this problem with our service as well. MCP is unable to perform service discovery without hitting this failure. The application in the firmware is not hitting any errors. I do get a disconnect notification with reason 0x13 (BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION). After MCP fails to connected, it is still possible to connect from our mobile application.

This is a bit troubling because our CM plans to use the MCP as a test tool, since they can run it on Windows.

RE: Problems after switching Project to SDK 5.2.0

Christoph Inhestern — Thu, 10 Apr 2014 09:06:25 GMT

I don't get into the error handler and so I don't know where this error is caused. I switched back to SDK 5.0.0 and everything is working. I' ll maybe try to update later, but for now I have to go forward. Although thank you for your help and time.

RE: Problems after switching Project to SDK 5.2.0

Petter Myhre — Thu, 10 Apr 2014 08:26:47 GMT

Hi Chris

You are correct, it is. It seems like the application is stuck somewhere, and is not able to respond. I would recommend you to make sure that the error handler in the top of main doesn't reset, and instead use the debugger to inspect the file name, line number and error code that you most likely get there.

RE: Problems after switching Project to SDK 5.2.0

Christoph Inhestern — Thu, 10 Apr 2014 06:24:38 GMT

Hi Petter

Yes, it was working so far. The characteristics with the handle 0x000A and 0x00B belong to the "PrimaryService Generic Attribute (0x1801)". Isn't that a default BLE service? On the handle 0x000A there was always a READ_NOT_PERMITTED, so I didn't care about it.

RE: Problems after switching Project to SDK 5.2.0

Petter Myhre — Wed, 09 Apr 2014 18:13:33 GMT

Hi Chris

This worked perfectly with SDK 5.0.0?

Seems like you don't have permission to read the attribute value with handle 0x000A, and then you disconnects because you don't get any response when trying to read attribute value with handle 0x000B. Could you examine how that characteristic is configured?