pc-ble-driver-py pip update for new SD API

[Sebastien]

the python package is not updated through pip with last release of SD_API and corresponding hex files.

I know that you give instruction to build driver but it could be easier to just use pip update and be able to use connectivity Firmware from last SDK version.

On pip the last package support only API V2 or V3, this is very old.

Do you have a plan for this ?

Regards,

Sebastien

[Jørgen Holmefjord]

Hi,

pc-ble-driver-py was updated to support SD API v5 in version 0.12.0. The latest version available is 0.14.2.

Have you tried updating the version you have installed with pip?

pip install --upgrade pc-ble-driver-py

Best regards,
Jørgen

[Sebastien]

Yes and we still have an issue when we send data at 100Hz.

After 10 sec, we didn't receive notification anymore.

We tried to debug the connectivity firmware. What I don't understand is that we compiled connectivity firmware (nRF5_SDK_14.2.0_17b948a\examples\connectivity\ble_connectivity) from SDK 14.2 because this is the API V5 but the communicatin between the Python script and the Board don't work. After some debug, it seems that the Firmware don't use same IO for UART and the UART configuration is not the same. This is like if this is not the good firmware.

This is project that we used: ble_connectivity_s132_uart_pca10040.ewp

We seen that the pc_ble_driver firmware patch change UART configuration, pin defintion and Parity and not HW flow Control.

In pc_ble_driver_py uart is opened without HW_FLOW_CTROL and in the Firmware with or without patch this is configured with HW_FLOW_CONTROL. Is it normal?

[Jørgen Holmefjord]

The connectivity projects in the nRF5 SDK is configured for use with our serialization libraries, they do not use the serial pins to go through the Segger J-Link chip to a PC. The connectivity FW in the latest pc-ble-driver is built using nRF5 SDK v15.3.0 for all SD API versions (v3, v5, v6), but you need to apply this patch to the clean SDK or build the connectivity FW according to these instructions.

Regarding the HWFC question, see this post.

[Sebastien]

When we used the NRF52840 Eval Board (Dongle or DK) we don't have any issue.

It seems that the issue occurs only with NRF52832 Board.