pc-ble-driver compatibility with SDK15.3.0 connectivity S140_usb_hci example

[Sebastian]

Hello Nordic Support Team,

The question I have is simple. 

Can I use the pc-ble-driver with the ble_connectivity_s140_usb_hci example found in SDK15.3.0?

If not why? 

Also if not, what files are the github scripts using from the SDK to compile the USB Hex file used for connectivity with the pc-ble-driver?

Thank you for your answers.

[Jared]

Hi,

Yes, the pc-ble-driver works with SoftDevice s140 API version 6 from SDK 15.3. From GitHub: 

The generated libraries are compatible with the following SoftDevice API versions and nRF5x ICs:

• SoftDevice s130 API version 2: connectivity_<version>_1m_with_s130_2.x.x (nRF51 and nRF52 series ICs)
• SoftDevice s132 API version 3: connectivity_<version>_<1m|*usb>_with_s132_3.x.x (only for nRF52 series ICs)
• SoftDevice s132 API version 5: connectivity_<version>_<1m|*usb>_with_s132_5.x.x (only for nRF52 series ICs)
• SoftDevice s132 API version 6: connectivity_<version>_<1m|*usb>_with_s132_6.x.x (only for nRF52 series ICs)
• SoftDevice s140 API version 6: connectivity_<version>_<1m|*usb>_with_s140_6.x.x (only for nRF52 series ICs)

Note: BLE DFU with nrfutil is not supported with API version 6 as nrfutil only supports up to SD API v3. 

Best regards

Jared

[Sebastian]

Hello Jared,

Thanks for your quick reply, however, this is not what I was asking. 

I don't want to use the precompiled .hex file that can be found in github and I don't want to use the scripts that are in github to compile the files myself. 

What I am trying to find out is if the example in \nRF5_SDK_15.3.0_59ac345\examples\connectivity\ble_connectivity can work with the pc-ble-driver?

I want to make changes to that example and compile it with Segger Embedded Studio. I think that this is what the github scripts do but I want to confirm it with you. 

Maybe to explain it in a different way:

Is the SoftDevice s140 API version 6: connectivity_<version>_<1m|*usb>_with_s140_6.x.x produced by the use of the usb_hci connectivity example in the SDK?

Thank you for your answers.

[Jared]

Hi,

oh sorry for the misunderstanding. The pre-compiled hex files are the compiled from the SDK example, BUT with some modifications which are included in this patch.

Sebastian said:

I want to make changes to that example and compile it with Segger Embedded Studio. I think that this is what the github scripts do but I want to confirm it with you. 

Yes you can modify the example and then build the hex files from the SDK example. This will produce the necessary hex files likewise as the ones on GitHub.

Hope I answered your question.

Jared 

[Sebastian]

Hi Jared,

Thank you very much for your answer. 

I need some more clarification though. I am aware of the 15.2.0 patch. 

Does the serialization usb_hci example in the SDK 15.3.0 need the patch?

Thank again for your answers in advance. 

[Jared]

I don't think it needs the patch. If it doesn't work then I suggest that you go with SDK 15.2.0 and the patch.

[Sebastian]

Hello Jared,

Thank you for your answers.

I will close the subject.

[Sebastian]

Hello Jared,

Sorry but I have to reject this answer. 

I started binding the C/C++ pc-ble-driver in C#.

I tried using the example ble_connectivity_s140_usb_hci_pca10056 on my target board and the driver on the PC.

The sd_rpc_adapter_create(transport_layer) API call works fine and the adapter is created. 

However, when I try to do sd_rpc_open I get an NRF_TIMEOUT error from my target board. 

This DOES NOT happen when I use the github pre-compiled file 

connectivity_4.0.0_usb_with_s140_6.1.0.hex

This means that the example on SDK 15.3.0 is not the same as the precompiled github file. 

Can you please let me know which files I need to compile from the SDK 15.3.0 in order to get the same behaviour as with the pre-compiled hex file?

[Florian Pichler]

Hey Sebastian,

I'd like to push here... same question from my side.

@Jared: Any concrete advice which changes have to be made to get it running?