Browse Source
The default thread priority for the CoAP client thread is set to NUM_PREEMPT_PRIORITIES which is not a valid thread priority, as the lowest application thread priority is actually NUM_PREEMPT_PRIORITIES - 1. Because of this, CoAP client library gave an assert on boot if assertions were enabled. Kconfig does not allow for arithmetics when setting integer defaults, therefore handle this at the preprocessor stage by limiting the actual priority assigned to the CoAP client thread to a valid range. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>pull/88895/head
1 changed files with 5 additions and 1 deletions
Loading…
Reference in new issue