SW crush, with error " NRF_ERROR_MUTEX_LOCK_FAILED "

[Shy Hefetz]

Hello,

We have crush issues, and the error code we get is : 

NRF_ERROR_MUTEX_LOCK_FAILED

Please advise, what does this means and how do we fix it ?

Thanks

[ovrebekk]

Hi 

Have you been able to identify which function it is that returns this error? 

Would you be able to show me the call stack trace when this happens?

If you put a breakpoint with the debugger it should be possible to see the sequence of function calls preseeding this error. 

Best regards
Torbjørn

[Shy Hefetz]

Hi Torbjørn,

Thank you for your reply

We were not able to identify which function returns this error, and we are not sure how to re-create the issue

As far as we understand, it happens in the SoftDevice, 

Please advise on how can re-create the condition for this type of error

Thanks,

Shy

[ovrebekk]

Hi Shy

Can you provide me more information about your setup? 

- Which SDK version are you using?

- Which SoftDevice version?

- Are you basing your code on one of our SDK examples, if so which one?

- Does the issue happen consistently, or only in rare occasions?

- Does the issue happen at a particular point in time, like just after connection, or when you do something particular in the application?

- Are you familiar with the nRF Sniffer (or some other Bluetooth sniffer) that you can use to capture a sniffer trace when the issue occurs?

Best regards
Torbjørn

[Shy Hefetz]

Hi Torbjørn

Please see our reply in RED

- Which SDK version are you using?

nRF5SDK160098a08e2

- Which SoftDevice version?

S132

- Are you basing your code on one of our SDK examples, if so which one?

UART over BLE

- Does the issue happen consistently, or only in rare occasions?

Only in rare occasions.

- Does the issue happen at a particular point in time, like just after connection, or when you do something particular in the application?

- Are you familiar with the nRF Sniffer (or some other Bluetooth sniffer) that you can use to capture a sniffer trace when the issue occurs?

We are familiar with this tool. We are trying to reproduce the error and will use it then.

Thank you,

Shy

[ovrebekk]

Hi Shy

If you are able to capture a sniffer trace and print the error details that could be really helpful. For instance there should be a PC (program counter) value included in the error handler, which would tell us which part of the SoftDevice produced this error. 

Shy Hefetz said:

- Which SoftDevice version?

S132

Would this be S132 v7.0.1?

This is the one included in SDK v16.0.0. 

Could you tell me if you use the timeslot API in your application?

This error can occur if the timeslot API is used, and you stay in the timeslot interrupt for too long. 

If not, could you give me an overview of what other peripherals you are using, and if you are using  any modules that access flash?

How many Bluetooth connections do you have running when the issue occurs?

Best regards
Torbjørn