apache / apache/mynewt-nimble

controller: assertion in ble_ll_adv_send_conn_comp_ev

Open
#1,805 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
893
Forks
512
Avg merge
13d 31m
Merged PRs (30d)
7

Description

Failed assertion occurs in **ble_ll_adv_send_conn_comp_ev()** while testing blestress app - testcase num 11.

![image](https://github.com/apache/mynewt-nimble/assets/119607575/6928e5ab-3685-41c7-88ab-c9f01c8aea86)

![image](https://github.com/apache/mynewt-nimble/assets/119607575/266d99aa-e04f-4a60-b80c-065f0c012339)

![image](https://github.com/apache/mynewt-nimble/assets/119607575/252c3d75-4486-4325-8959-85d9a66ae93d)

Unfortunately, for some reason this isn't reproducing when running only specific test case. To reproduce this issue, you'll have to run all tests. You'll need two nRF52 boards. Use blestress README file to setup blestress app correctly or create targets as shown in the picutre below.
![image](https://github.com/apache/mynewt-nimble/assets/119607575/2a62a0ac-d1dd-45e5-972b-606abbf63c14)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at ble_ll_adv_send_conn_comp_ev() and review the blestress README for setup details. Reproduce testcase 11 by running all tests with two nRF52 boards, rather than the individual testcase alone, and capture the failing assertion. Done means the assertion no longer occurs during the full test run.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.