Hi,
I work with win10 laptop, Toolchain nrf Connect SDK 1.6.1 on a nrf5340dk.
I modifyed peripheral_uart to use 240 bytes like it's explain into "ncs 1.6.1 peripheral_uart example - increasing NUS size" ticket:
First question:
It's work perfectly with nRFToolBox but I realized that it's work diffrently with nRFConnect for Mobile.
With nRFToolBox I can send 239 bytes with Rx Characteristc and Tx charateristic.
But if i try with nRFConnect I can't send more then 19 bytes with Tx Characteristic and more then 36 bytes with Rx Characteristic.
On Rx I have the "error 9 (0x9) Gatt prepare Q full" when I send 37 bytes and on Tx I have the warning" No Att channel for MTU 24 / no buffer available to send notification / fialed to send data over BLE connection" when I send 20 bytes.
Why is that not working on nRFConnect ?
Second question:
During a BLE formation in France I learned that there is a negociation between the central and the peripheral before etablishing a connection about the size of MTU.
I need to transfert a lot of data by the uart connection and I want to be sure that I can send paquet of 239 bytes for each connection with any smartphone (Android).
Do you know how to retrieve the result of the negociation between the central (smartphone) and the peripheral (nrf5340dk) ?
Best Regards,
Rob.