pc-ble-driver V4.0.0

[Christian Waldmann]

I can communicate with success from the pc to my custom nrf52832 device (SDK 15.2, S132v6.1) using the pc-ble-driver (sd_api_v3) with Tag 4.0.0 from Github. Great work!

But I can not request a RTU other than 23 from the PC. Values > 23 return Error 7 (NRF_ERROR_INVALID_PARAM) when calling sd_ble_gattc_exchange_mtu_request, using interface sd_api_v3. 

Using 23 as value, the server sends the response with 517 as expected (recorded with WireShark)

My questions:

A) What is the value of NRF_SDH_BLE_GATT_MAX_MTU_SIZE used for compiling the precompiled HEX files for the connectivity chip?

B) Do I have to compile the connectivity software by myself with the desired MAX_MTU_SIZE > 23?

C) What are the correct steps to apply the patch "nRF5_SDK_15.2.0_connectivity.patch"

Thanks in advance and happy coding

Christian

[Einar Thorsrud]

Hi Christian,

A) All connectivity firmwares for SD versions larger than 3 are patched to support MTU size up to 250 (you can see that by searching for NRF_SDH_BLE_GATT_MAX_MTU_SIZE in the patch file).

B) No, the precompiled hex files are patched to use max MTU 250.

C) The build script will download and patch the SDK automatically when building the connectionvity firmware. You can see the details here.

Einar

[Christian Waldmann]

Hello Einar

I can exchange larger MTU with success with the S132_V3 from the pc-ble-driver V4.0.0, after adding the following line to the init for the call to sd_ble_enable(...):

ble_enable_params.gatt_enable_params.att_mtu = 150;

Thanks for support

Happy coding

Chris