NRF_ERROR_RESOURCES after upgrade to SDK 17

[Roei]

Hi,

I've upgraded my SDK from 15.2 to 17.

After upgrading - I can't connect my device via NFC - it keeps disconnect with NRF_ERROR_RESOURCES.

I've tried to increase BLE queue size, it didn't help.

Can you please help me?

Thanks!

[ovrebekk]

Hi 

Can you give me a bit more detail on what you are doing when this error is returned?

When sending data over BLE it is quite normal to get the NRF_ERROR_RESOURCES error when the buffers are full, but this should not cause the link to disconnect, unless you explicitly disconnect when the error is returned. 

Is your code based on one of the examples in the SDK, or is it created from scratch?

Best regards
Torbjørn

[Roei]

Hi,

When the error occurs, BLE_GAP_EVT_DISCONNECTED event is called and NRF_ERROR_RESOURCES is the disconnection reason code.

I used the examples from the SDK, it was OK with SDK 15, but after upgrading to SDK 17, the issue started to occur.

I tried to find if there is a place in my code with calls explicitly to a disconnection function, but I didn't find.

Thanks!

[ovrebekk]

Hi

NRF_ERROR_RESOURCES is not really a disconnect reason. I assume you mean the reason is 19 (or 0x13 hexadecimal) ?

This corresponds to BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION, which means that the device you are talking to decided to disconnect the link. 

Can you let me know what kind of device you are communicating with?

Best regards
Torbjørn

[Roei]

Hi,

I'm communicating with a PC, via NFC.

However, it worked before SDK upgrade, so I think that the reason related to the SDK.

Thanks!

[ovrebekk]

Hi 

Do you have any means to get a sniffer trace of the BLE communication when you try to establish a connection?

Then you can compare the traces from your working SDK v15.2 project and the non working SDK v17 project, which should make it easier to spot the issue. 

Best regards
Torbjørn