Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Frank — Fri, 12 Oct 2018 06:09:11 GMT

Hi Seven,

Good to hear that it helped youl

For more information on how I managed, you can read here:

https://devzone.nordicsemi.com/f/nordic-q-a/39173/no-valid-bidirectional-uart-communication-between-the-imx6-ul-s-evk-board-running-the-nordic-pc-ble-driver-and-the-nrf52-dk-running-the-nordic-connectivity-132-uart-software

Best regards,

Frank

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

SevenZeng — Thu, 11 Oct 2018 14:39:04 GMT

Hi Frank, Many thanks for your help, got so much infomation from your comments

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Frank — Tue, 09 Oct 2018 10:59:52 GMT

Hallo Martin,

So it is not recommended to use API v5, so building the PC BLE driver SW must be done with the define NRF_SD_BLE_API_VERSION=3. Which SoftDevice has to be used in that case?

Thanks,

Best regards,

Frank

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Frank — Tue, 09 Oct 2018 10:13:01 GMT

Hi Seven,

I'm more or less on the same development and integration track of Nordic products and facing the same hurdles when trying to setup UART communication between a custom board running the PC BLE driver applic and the Nordic DK nRF5 (PCA10040) running the Connectivity applic.

I would suggest you start from the PC BLE driver source tree from the Nordic GIT hub project.

You don't have to download yourself the SDK.

So just run the windows batch file when building on Windows OS, it will download automatically the correct SDK v15 (remark this will not be the latest release of V15) and will apply the patch automatically, the build will fail as you are not using KEIL, but that doesnot matter as you will have the patched sources you can build in your preferred IDE.

Just one important remark, the patch will adapt the UART pins to the standard ones, you will need to revert these patch changes back to the serialize UART pins: 23,24,25 and 02 at least if you are no using the standard UART of the Nordic board.

BTW the ser132hci must be used as I depends on the H5 protocol (the protocol the PC BLE driver applic implements too) to ensure more reliability for UART communication.

Good luck!

Best regards,

Frank

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Martin Lesund — Tue, 09 Oct 2018 09:23:06 GMT

Hello Seven,

Softdevice API v5 is not quite stable. Last stable version of pc-ble-driver is v2.3.2.

(It uses SoftDevice API v3)

Support for SoftDevice API v6 will come in the near future.

For patching you can use the scripts that are included.

There is a "bat-file" in :[ pc-ble-driver/hex/sd_api_v3/build_v3_win.bat ] in pc-ble-driver v2.3.2 which you can run to do the patching.

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

SevenZeng — Sat, 06 Oct 2018 15:08:39 GMT

Hi Martin,

Sorry for bothering you again.

Here is the schematic of my ev board, I think the RTS and CTS might be considered as connected (surely JP1s are all connected). And I do modified the connectivity code to match the board.

Now I'm trying to follow you guide step by step but get some stupid questions (forgive me as a rookie if they do are stupid enough 😞)

0. I downloaded the tag v3.0.1 as suggested, then found out the patch file, then I realized that I don't know which version of the SDK should be used as nowhere has stated this.

1. since the patch file name is 'sdk140_connectivity.patch', so I downloaded SDK 'nRF5_SDK_14.0.0_3bcc1f7' as a zip file.

2. when I was about to apply the patch, I suddenly realized that I don't know how to... so here is the problem, I tried to follow the step searched from web, but only found this :

a. copied the patch file <pc-ble-driver-3.0.1\hex\sd_api_v5\sdk140_connectivity.patch> to nRF5_SDK_14.0.0_3bcc1f7\

b. tried to apply the patch by doing this:

Seven@DESKTOP-61IHFS2 MINGW64 /d/Projects/BT/nRF5_SDK_14.0.0_3bcc1f7
$ git apply --stat sdk140_connectivity.patch
.../serialization/common/ble_serialization.h | 2 +
components/serialization/common/ser_config.h | 7 ++--
.../transport/ser_phy/config/ser_phy_config_conn.h | 8 ++---
.../common/transport/ser_phy/ser_phy_hci.c | 8 ++++-
.../connectivity/ser_conn_error_handling.c | 2 +
.../pca10040/ser_s132_hci/config/sdk_config.h | 4 ++
examples/connectivity/ble_connectivity/main.c | 33 ++++++++++++++++++++
.../ble_connectivity_s132_hci_pca10040.uvprojx | 4 +-
.../armgcc/ble_connectivity_gcc_nrf52.ld | 2 +
9 files changed, 56 insertions(+), 14 deletions(-)

Seven@DESKTOP-61IHFS2 MINGW64 /d/Projects/BT/nRF5_SDK_14.0.0_3bcc1f7
$ git apply --check sdk140_connectivity.patch
error: patch failed: components/serialization/common/ble_serialization.h:166
error: components/serialization/common/ble_serialization.h: patch does not apply
error: patch failed: components/serialization/common/ser_config.h:66
error: components/serialization/common/ser_config.h: patch does not apply
error: patch failed: components/serialization/common/transport/ser_phy/config/se r_phy_config_conn.h:65
error: components/serialization/common/transport/ser_phy/config/ser_phy_config_c onn.h: patch does not apply
error: patch failed: components/serialization/common/transport/ser_phy/ser_phy_h ci.c:39
error: components/serialization/common/transport/ser_phy/ser_phy_hci.c: patch do es not apply
error: patch failed: components/serialization/connectivity/ser_conn_error_handli ng.c:101
error: components/serialization/connectivity/ser_conn_error_handling.c: patch do es not apply
error: patch failed: examples/connectivity/ble_connectivity/pca10040/ser_s132_hc i/config/sdk_config.h:48
error: examples/connectivity/ble_connectivity/pca10040/ser_s132_hci/config/sdk_c onfig.h: patch does not apply
error: patch failed: examples/connectivity/ble_connectivity/main.c:57
error: examples/connectivity/ble_connectivity/main.c: patch does not apply
error: patch failed: examples/connectivity/ble_connectivity/pca10040/ser_s132_hc i/arm5_no_packs/ble_connectivity_s132_hci_pca10040.uvprojx:329
error: examples/connectivity/ble_connectivity/pca10040/ser_s132_hci/arm5_no_pack s/ble_connectivity_s132_hci_pca10040.uvprojx: patch does not apply
error: patch failed: examples/connectivity/ble_connectivity/pca10040/ser_s132_hc i/armgcc/ble_connectivity_gcc_nrf52.ld:6
error: examples/connectivity/ble_connectivity/pca10040/ser_s132_hci/armgcc/ble_c onnectivity_gcc_nrf52.ld: patch does not apply

So by now I'm choked here, please save me 😞

And one more question, there are 2 possible connectivity projects <ser_s132_uart> and <ser_s132_hci>, which one should be used?

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Martin Lesund — Tue, 28 Aug 2018 15:18:45 GMT

Hi Seven,

Can you confirm that you have connected RTS and CTS?

Have you modified the connectivity firmware to fit your custom board?

Like using the correct version , which comes with the pc-ble-driver "hex-folder". (It's a patch-file there which you have to run on the SDK example)

For example, choose the correct one according to your SoftDevice.

(you can find that through the "tags"-tab:)

(If you are using nrf52832 you can use the project : examples/connectivity/ble_connectivity/pca10040/ser_s132_hci )

1. Download the correct version of the SDK

2. Use the .patch file in "pc-ble-driver/hex" (to get the patched version of connectivity)

3. Do the necessary changes based on your custom card. (Change to BOARD_CUSTOM instead of PCA10040, and change what suits your card (crystals, pins etc.))

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

SevenZeng — Tue, 28 Aug 2018 13:02:47 GMT

Yeah that's exactly what I've done 'to modify the example to use flow control', by simply changed the enum form none to hardware like this @file main.c:

static adapter_t * adapter_init(char * serial_port, uint32_t baud_rate)
{
physical_layer_t * phy;
data_link_layer_t * data_link_layer;
transport_layer_t * transport_layer;

phy = sd_rpc_physical_layer_create_uart(serial_port, baud_rate, SD_RPC_FLOW_CONTROL_HARDWARE,
SD_RPC_PARITY_NONE);
data_link_layer = sd_rpc_data_link_layer_create_bt_three_wire(phy, 100);
transport_layer = sd_rpc_transport_layer_create(data_link_layer, 100);
return sd_rpc_adapter_create(transport_layer);
}

But after I did this, the host just no longer send any message again. Did I missed anything?

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Martin Lesund — Tue, 28 Aug 2018 09:33:34 GMT

Hi Seven,

(from the thread posted)

The pc-ble-driver library is written for use with SEGGER J-Link devices. The J-Link OB firmware have a flow control sensing mechanism that will enable HWFC if it is detected on the other side. In the example, the flow control is set to none, but in the connectivity firmware, HWFC is enabled. If the serial to USB chip on your board does not support this automatic sensing, you might get error or unstable connections. Please try to modify the example to use flow control in line with the connectivity firmware.

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

SevenZeng — Mon, 27 Aug 2018 14:57:19 GMT

Hi Martin, I tried to change the flow control setting and found this:

if the HWFC is enabled on the PC, the PC just never send any message

if the HWFC is disabled on the PC, the PC do send message but get no response from the target.

So if I'm understanding this correctly, the connectivity firmware is not supported by my custorm board. is that right?

RE: Get no response from connectivity program running on custom board with pc-ble-driver hrc v5 example host

Martin Lesund — Fri, 24 Aug 2018 14:28:51 GMT

Hi Seven,

I think this thread can help you out