[EXT_EP-10847] System goes to halAssertHandlerExt when more than LL_MAX_NUM_CTRL_PROC_PKTS are queued Created: 20/Jun/22  Updated: 30/Sep/24  Resolved: 23/Jul/24

Status: Fixed
Project: Embedded Software & Tools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: TI User Assignee: TI User
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Product: SimpleLink CC13x2-26x2 SDK BLE5 Stack
Internal ID: BLE_AGAMA-3427
Found In Release: BLE Stack BLE5-2.1.1
Fix In Release: BLE Stack BLE5-2.2.11
BLE stack BLE5-2.2.11 RC1
Affected Platform/Device: CC26X2R1

 Description   

Git \ Installer version: simplelink_cc13x2_26x2_sdk_3_40_00_02

Problem reproducibility:  100%

Problem description: 

In central role (simple_central). Calling "HCI_LE_SetHostChanClassificationCmd" in GAP_LINK_ESTABLISHED_EVENT causes a halAssertHandlerExt. To reproduce it, put the HCI_LE_SetHostChanClassificationCmd after the GAP_LINK_ESTABLISHED_EVENT(connect with the paired/bonded peripheral )

 

case GAP_LINK_ESTABLISHED_EVENT:    
{      
  uint16_t connHandle = ((gapEstLinkReqEvent_t*) pMsg)->connectionHandle;      
  uint8_t* pAddr = ((gapEstLinkReqEvent_t*) pMsg)->devAddr;      
  BLE_LOG_INT_TIME(0, BLE_LOG_MODULE_APP, "APP : ---- got GAP_LINK_ESTABLISHED_EVENT", 0);      
  HCI_LE_SetHostChanClassificationCmd(map);

After further debugging it was found that from the link layer.
 
The maximum number of control commands in queue per connection is capped at a certain amount. In case, the number of control commands in the queue exceed the designated maximum number, then there will a violation of the struct. Additional logic should be added to prevent the number of control commands to exceed the maximum number allowed.

 


Generated at Sat Apr 05 08:32:36 CDT 2025 using Jira 9.12.17#9120017-sha1:aba4002bcd633f188b6a4bb5dd8a0e1f20b79ee4.