firmware resets with high pc-ble-driver MTU valueshttps://devzone.nordicsemi.com/f/nordic-q-a/26246/firmware-resets-with-high-pc-ble-driver-mtu-valuesI want to increase the MTU values to increase the throughput from my own service (currently based on NUS service) and to receive the data with pc-ble-driver-python with the 1M serialization firmware on an nrf52832 devboard and pc-ble-driver-py 0.11.3en-USTelligent Community 13Thu, 26 Oct 2017 13:27:31 GMTRE: firmware resets with high pc-ble-driver MTU valueshttps://devzone.nordicsemi.com/thread/103341?ContentTypeID=1Thu, 26 Oct 2017 13:27:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b3e08aa1-5022-47da-a5dd-17b99b3a2517Florian Zierer<p>Jørgen Holmefjord, this was the right question to check the firmware once again. when I recently started nRF Connect v2.1.0 it flashed a connectivity firmware which seems not to support higher MTU values.</p> <p>When using the connectivity_1.2.0_1m_with_s132_3.0.hex from pc-ble-driver git tag v2.1.0 I can use higher MTU values.</p><div style="clear:both;"></div>RE: firmware resets with high pc-ble-driver MTU valueshttps://devzone.nordicsemi.com/thread/103340?ContentTypeID=1Thu, 26 Oct 2017 12:43:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:35a1f16f-9611-4c1f-80cd-3c5e8eaf49b6J&#248;rgen Holmefjord<p>Are you using the connectivity firmware from pc-ble-driver repository, or some custom firmware that you compiled?</p><div style="clear:both;"></div>