What do DEADBEEF, NRF_ERROR_BUSY, NRF_ERROR_INVALID_STATE,... actually mean?

[Marius Heil]

Hello,

I am currently looking through my error handling and noticed that there are some errors that I do not really understand fully, so I've summarized them here:

0xDEADBEEF

One of my devices just ran into a DEADBEEF error and I am wondering where it comes from. My debug backtrace does not seem to be usable at this point.

Could you give us a list of possibilities that would cause a DEADBEEF error? What are the conditions of it being thrown?

And when there is one, how can I debug it properly and find the part in my code?

NRF_ERROR_BUSY

E.g. when creating a connection with sd_ble_gap_connect, does this error simply mean that there is no more free space in the event buffer so that I have to handle another event first before I can call this function, which will generate a new event?

Or as another example: sd_ble_gattc_write. Will the NRF_ERROR_BUSY only be thrown when another write is ongoing? If my routine does only send data after a Write complete has been received, I should be safe, right?

NRF_ERROR_INVALID_STATE

How many states does this include? I know of the typical ones for BLE like Connecting, Advertising, Scanning, etc.... but according to an answer of a forum question flash operation ongoing seems to be an additional state. Could you provide us with a list of states that will cause this error?

Somewhere in the documentation it says "Invalid state to perform operation (most probably not in advertising state).", which is not really helping because I do not want to do error handling based on guessing. I could not find a more detailed description for these error, sorry if I missed it somewhere.

Marius

[Ole Bauck]

DEADBEEF means an assert from the SoftDevice and comes from softdevice_assertion_handler(uint32_t pc, uint16_t line_num, const uint8_t * file_name) which calls assert_nrf_callback(line_num, file_name) which in turn calls app_error_handler(DEAD_BEEF, line_num, p_file_name), where DEAD_BEEF is defined as 0xDEADBEEF. Could you give me the line number and file name that was used in the app_error_handler, so I can check where it comes from?

Edit 11.01.2016:

##NRF_ERROR_BUSY

You can get this if you try to connect and there are still events in the event buffer. You will also get it if you call sd_ble_gattc_write while another write is ongoing. Waiting for write complete is sufficient.

##NRF_ERROR_INVALID_STATE

We cannot give you a list over all states, so there is no automatic way to handle this error. If you try to connect without advertising you will get this error, or if you already try to initiate a new connection.

[Marius Heil]

Hello, I ported my mesh to Softdevice v2 on Friday and left it running over the weekend. Two of my nodes ran into a Softdevice assert again. This is signalled via a blue LED. I then attached the debugger to the first and the second target and got the same error:

id: 1 (NRF_FAULT_ID_SD_ASSERT)
pc: 6052
info: 0

The stacktrace shows the addresses 0x17a8 => 0x1a3ce => signal_handler => fault handler. Would be glad if you could help me on that. And one more question: After a Softdevice assert happens, there are no more interrupts, is this right? So that would mean I could safely debug the device after it runs into an endless loop in the softdevice assert handler.