File: (null), Line: 0, Error code: 4

[Jim Dattolo]

I'm using Python bindings 0.5.0 and the connectivity app. On one of our machines that is running tests with the satck/dongle we see it fail a lot with a scrolling of this message from the DLL (our registered handler in python gets it with a severity code of 4)

What is this error? It's not recoverable

[syntroniks]

I am not familiar with running connectivity but I do know defining "DEBUG" in your preprocessor for firmware and including app_error.c allows me to inspect the p_file_name and line number variables. Often they get optimized away. The most common scenarios I see (if this is an NRF_ERROR_NO_MEM) are insufficient timer or pstorage allocations.