On Mon, Aug 06, 2018 at 02:03:22AM +0100, Lukasz Wolnik wrote:
> Hi Chris,
>
> I have resolved the issue. It wasn't my mbuf structure but MSYS_1's pool
> memory leak (caused by my app).
[...]
>
> I finally have a stable Mynewt app <-> Android repeated communication even
> on MSYS_1_BLOCK_COUNT
Hi Chris,
I have resolved the issue. It wasn't my mbuf structure but MSYS_1's pool
memory leak (caused by my app).
After verifying that the same actions recreated in btshell result in no
MSYS_1 memory leak (BTW, SHELL_TASK and its mpool stat is a great tool!) I
turned my attention back to my
Hi Chris,
It's been more than a year but I have finally got some findings.
In my another Mynewt powered device I got the BLE_HS_ENOMEM error
from ble_gattc_write_flat this time. I tried changing BLE_GATT_MAX_PROCS
(down to 2 or up to 8) but with no effect.
My device was keeping a connection
