mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388610640
Closing this ticket, as it is long and has a few issues in it, the core of
which is solved.
Thanks @andrzej-kaczmarek
I will try to
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388610310
@andrzej-kaczmarek
Fixed for 500 bytes! It turns out that OS_MEMPOOL_POISON causes lots of
timing issues, as one might expect. My test
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388605149
@andrzej-kaczmarek
Update, using bt_shell, it is possible to receive the 500 bytes transmitted
(my test code on tx side only), ONLY if
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388416419
@andrzej-kaczmarek
ok, a few thoughts. I should try to verify that my tasks are lower priority
than bt_ll, however I think they should be
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388416419
@andrzej-kaczmarek
ok, a few thoughts. I should try to verify that my tasks are lower priority
than bt_ll, however I think they should be
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388279774
@andrzej-kaczmarek
With BTshell <--> BTshell, and a 900byte attempt, we see almost 100% of the
attempts resulting in truncated
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-388242282
Tested with a lot less printing to the console, moved to RTT. No luck with
the 500byte tx->rx. Here is what I see on Rx side:
06209
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383794994
[hci_debug_tests.txt](https://github.com/apache/mynewt-nimble/files/1940790/hci_debug_tests.txt)
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383793992
@sjanc
It seems that a patch from @andrzej-kaczmarek helped me read data-status.
I have also updated my test code to no longer say "BAD"
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383793992
@sjanc
It seems that a patch from @andrzej-kaczmarek helped me read data-status.
I have also updated my test code to no longer say "BAD"
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383644834
@sjanc
I think you are correct that my test code does not properly reassemble,
however I never get anything that is marked INCOMPLETE, all
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383343177
More research:
- It seems to happen (callback not called) more often while tx and rx
adv_ext packets at the same time. I have the following
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383248305
@andrzej-kaczmarek
Ok, pushed updates to test project. Cleaned up a little, and made max_event
cause the adv stop, to help work around
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383190799
@andrzej-kaczmarek
I have pushed interval fixes on my test project side as well. I had some
bad values which led to the scanner issue on the
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-383043922
Some more details:
- I may have fixed the scanner issue, I am not sure I provided the right
values to ble_gap_ext_disc in my first test cases.
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-381667220
@andrzej-kaczmarek Were you able to repro it no longer receiving ext_adv
messages after 5min or so?
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-381538269
Thanks, should I use max_events instead for now as a workaround, would that
be a more stable way to define the end of the broadcast?
I
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-381446367
Fixed heavy corruption, other issues remain. My fix to the corruption was
due to the fact that I didn't realize that set_ext_adv_data calls
mwilliford commented on issue #44: Extended Advertisement Issues
URL: https://github.com/apache/mynewt-nimble/issues/44#issuecomment-381446367
Fixed heavy corruption, other issues remain. My fix to the corruption was
due to the fact that I didn't realize that set_ext_adv_data calls
19 matches
Mail list logo
