GATT_CONN_LMP_TIMEOUT after 40 seconds

[Tim Roberts]

I have an nRF52832, coding with SEGGER and the SDK 14.2.0.  I'm trying the ble_peripheral/ble_app_uart example (although I get similar results with the other BLE examples).  I can build and run it, and I see a few debug messages.  The nRF Connect app sees the advertising, but when I go to connect, there is a 40 second delay, and then GATT_CONN_LMP_TIMEOUT.  But if I load a hex file built from the same source on a colleague's machine, it works.  We both started from the same VM image.  I have to assume I have a configuration problem, but I don't know where to look.

[tesc]

Hi,

This sounds strange, especially since you both started from the same VM.

Are you sure that you are using the unmodified SDK 14.2.0? You could try extracting the zip again, in order to be 100 % sure there is nothing wrong with the SDK itself.

Can you confirm that there are no compiler or linker warnings or errors?

Do you have the log from the nRF application, or a sniffer log, that you can share?

Regards,
Terje

[Tim Roberts]

The problem was, indeed, a local modification to the SDK.  My colleague incorporated some fixed suggested by Nordic to allow switching between the regular SDK and the mesh SDK.  When I remove those modifications, it all works.

[tesc]

I am happy to hear that you figured it out!

The modifications, do they work, (but they were wrongly implemented on your machine,) or do they not work? If they do not work, please let us know what suggestions we are talking about, so that we can look into them and do corrections.

Regards,
Terje