haukepetersen opened a new issue #824: URL: https://github.com/apache/mynewt-nimble/issues/824
## Context I am still trying to understand the behavior described in #818. To make sure this is not a RIOT or a porting issue, I ported the benchmark application to mynewt (-> https://github.com/haukepetersen/riotsandbox/tree/master/tests/mynewt_nimble_l2cap_coc_flooding) This is the first time I actually did something with mynewt and I am still learning - so please excuse the project structure and code maturity :-) ## Problem When flooding an L2CAP COC link between two nodes for a long enough amount of time (~some seconds), the transmitting node will crash (reboot). By e.g. trying to send 10k chunks of 100byte (`flood 100 10000`), the `source` node will reboot after a random time, mostly something around ~15-20 seconds. ## Setup Two `nrf52dk` nodes on my desk, one flashed with the `source` application (target `source`), one with the `sink` (target `sink`) application. The nodes open a BLE connection automatically, and once connected also open a custom L2CAP connection oriented channel. Then, once connected, simply call the `flood` shell command on the `source` node. Is anyone able to reproduce this behavior? And does anyone have an idea where to look further? I am a little stuck here... ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
