BLE Beacon Scanning Callback Issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

BLE Beacon Scanning Callback Issue

313 Views
kiranc_danlaw
Contributor I

Case Information

  • Priority : Critical
  • Project Name: Telematics Control Unit

Case Additional Information

  • Topic : Others
  • Sub Topic : Others
  • Part Number / Device Family :
  • Selected Product Info : KW45B41Z83AFTBT
  • Product Breadcrumb : Products > Wireless Connectivity > Bluetooth Low Energy > KW45: 32-Bit Bluetooth® 5.3 Long-Range MCUs with CAN FD and LIN Bus Options, Arm® Cortex®-M33 Core > KW45B41Z83AFTBT

Case Description

  • Subject : BLE Beacon Scanning Callback Issue

Description : 

We have used eatt_central_bm has the base project and then added static freeRTOS into this and then introduced our application tasks.

We are using SDK_2_12_5_KW45B41Z83xxxA.

 The FreeRTOS version of eatt_central demo app has dynamic freeRTOS and we need static freeRTOS only.

Current Status of Bluetooth application:

  • Bluetooth scanning works well when standalone BLE task is run.
  • Bluetooth scanning works for few minutes when all our other application tasks are running. After that scanning is inconsistent.

It resets the software as well (could be because of the blocking calls in BLE stack).

  • On further debugging, we observe that the Bluetooth scanning callback is not getting triggered.

Any help to resolve this issue is well appreciated.

--

Regards,
Kiran

Labels (1)
0 Kudos
Reply
1 Reply

268 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello @kiranc_danlaw

This is a recap of what was discussed in your internal ticket:

Due to the deadlines for data transmission that the Bluetooth SIG states in their Core Specification, and in order to comply with these task deadlines, some kind of RTOS is necessary. The bm or bare-metal implementation of a BLE Application should already use an OS Abstraction Layer, which is based on a non-preemptive task scheduler. Perhaps the already implemented OS may be causing some conflicts or incompatibility with your FreeRTOS implementation.

Regards,
Eduardo.

0 Kudos
Reply