Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regular loss of a few connection intervals #33765

Closed
BOZHENG001 opened this issue Mar 29, 2021 · 1 comment
Closed

Regular loss of a few connection intervals #33765

BOZHENG001 opened this issue Mar 29, 2021 · 1 comment
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@BOZHENG001
Copy link

Describe the bug
When I use an nRF sniffer (nRF52840 DK) to sniff a BLE connection built between another two nRF52840 DKs (central_hr and peripheral_hr), I can always see a regular loss of some connection intervals. For example, after the event counter reached 1009, it directly goes up to 1012, and the delta time shows as 35839us (my connection interval is 12.5ms). In the beginning, I thought it should be some loss due to the sniffer serial port to my laptop, but after that, I tried to print the event counter variable from the channel selection algorithm #2 in file lll_chan.c, and I did see the counter also shows the regular connection interval loss (in my case after every four connection intervals, there are around four connection intervals lost). I am wondering if there is something wrong with my settings because the loss is so regular?

To Reproduce
Steps to reproduce the behavior:

  1. printk counter in the channel selection algorithm #2
  2. flash central_hr and peripheral_hr to two nRF52840 DKs
  3. See the issue from a serial port

Expected behavior
I expect the results from the "printk counter" should be continuous, instead of some regular connection interval loss.

Impact
It does confuse me also stops my work here because I don't know if I made it wrong or something else.

Logs and console output
A screenshot of the results of the "printk counter" from my Linux is provided below. Please have a check.
image

Environment (please complete the following information):

  • OS: Linux Mint
  • Toolchain (Zephyr RTOS version 2.4.99)
@BOZHENG001 BOZHENG001 added the bug The issue is a bug, or the PR is fixing a bug label Mar 29, 2021
@galak galak assigned galak and cvinayak and unassigned galak Mar 30, 2021
@galak galak added the priority: low Low impact/importance bug label Mar 30, 2021
@cvinayak
Copy link
Contributor

Modifying the lower link layer and adding printk and if on UART will break the hard real time requirements of connection events. Depending on UART baud rate, connection events during the UART transmission will be delayed and skipped.

If your issue is with modified lower link layer, please close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants