Dear people,
I use a pca10056 (alternatively the pca10059 dongle) and have compiled the connectivity firmware as described on the github page (release 4.1.1).
The only changes I did in the connectivity source files were:
- increasing the LINK_COUNT in sdk_config and adjusting the APP_RAM_BASE accordingly
- adding the line err_code = nrf_sdh_ble_default_cfg_set(1, &app_ram_base); SER_ASSERT(err_code == NRF_SUCCESS, err_code); after line 325 in conn_mw_ble.c of the segger SES project ble_connectivity_132v5_usb_hci_pca10056.
- it seems this line is necessary so that the sdk_config.h defines for the LINK_COUNT have an effect.
Now, I use the HRS_Collector sample provided by the python bindings of the pc-ble-driver-py and get measurement values from my device(s) by receiving notifications. This works so far, however I have the problem, that after some time (minutes, sometimes seconds), it seems that the connection to the peripheral is lost (i notice that by a led blinking on my peripheral) while the python driver/script does not report any loss of connection or error.
The peripheral itself is based on a custom nRF52832 board and the "link loss problem" doe snot occur when the peripheral is used with another BLE dondle/software so this seems to be related to the nordic python driver and/or connectivity firmware. Behaviour is the same for pca10056 and pca10059.
Can you please provide a hint of what could be wrong here and how to start useful debugging from here? (it seems a bit daunting to debug the connectivity firmware...)
[EDIT]: If I use the precompiled connectivity hex file delivered with the 4.1.1. version of the pc driver (connectivity_4.1.1_usb_with_s132_5.1.0.hex) I have(only one device possible with precompiled firmware) the following error after some time: Disconnected: 0 BLEHci.conn_interval_unacceptable
Thanks a lot and best regards!
