[EXT_EP-10439] Mesh stack delay work API is limited to a maximum delay of uint32 maximum value (42,949,672 milliseconds) Created: 05/Jul/21 Updated: 11/Dec/22 |
|
| Status: | Accepted |
| 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: | Unresolved | 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-3383 |
| Found In Release: | BLE Stack BLE5-2.2.2 RC8 |
| Fix In Release: | BLE Stack BLE5-2.2.9 |
| Description |
|
Description Mesh stack delay work API is limited to a maximum delay of 42949672 milliseconds. (uint32).
Details When using mesh stack API _k_delayed_work_submit_ to schedule a delayed work, the timeout time is limited by the following value: 42949672 milliseconds (maximum value of uint32), This has some implications on the mesh stack behavior. An example would be of the following scenario: When a node (other device) subscribes to receive a periodic heartbeat message from our device, it may configure the period value to be at a range of 0 - 65536 seconds. Due to the given limitation, any period value in the range of 42949 - 65536 seconds, will be converted to 42949 seconds. This limitation is driven by the internal timers API.
|