The error codes are BLE Spec related. There is one thread here that discusses them: What does 08 returned by emconinfo_getDiscReason() mean?
But there are several others as well.
link manager protocol = LMP
There are entire sections of the BLE spec devoted to the LMP and its operation.
Thanks, I saw that thread with solution to reset the chip. But isn't it a HW/FW bug which should be fixed some day by Broadcom? Resetting the whole chip does not seem to be a good option, especially when there could be other connections which are working fine. Reset will drop all obviously.
Clarification: I was referring to this post http://community.broadcom.com/message/9952 in relation to chip reset. I can understand that LMP may fail sometimes and require reconnection, but in our case it starts to fail permanently just after 5 minutes of work and only reset of the master board helps.
We spoke to the developers and unfortunately, reset is the only option.
Thanks MichaelF_56, I keep this question as "answered" unless this error causes some serious problems in our products.
Based on our experiments we have found out that this error seems to be triggered when there are more than one outstanding connection request initiated by blecen_Conn API. In other words, when blecen_Conn is called _before_ previous connection request has been completed. This seems either like a bug in the firmware our some undocumented limitation of the API. Can you please double check are multiple outstanding connections supported or not?
Thanks for the post. This is indeed limitation of the BT spec which is not verified on the API level. You should not try to Create another connection until first attempt is completed. In your app you should cancel the attempt using blecen_Conn(NO_CONN...)