Other Parts Discussed in Thread: ENERGYTRACE
Greeting. Thanks ahead for helping out.
I have migrated and modified the simple peripheral demo project from the LAUNCHXL-CC26X2R1 SDK, the application is working fine regarding the BLE function.
One of my goal in designing the system is to maintain the BLE functionalities while keeping the device sensitive to SPI request.
Currently the problem of the system is the collision between the BLE and SPI processing.
My application failed to maintain a stable communication in both interface simultaneously.
As expected, timing of task and interrupt in the RTOS would be essential in the following system design and investigation.
I have got several question regarding the design objective.
1. Is there any debugging functionalities other than the ROV that helps better in diagnosing the timing performance of the application?
2. Is it feasible to make the controller responsive to local communication events despite the BLE functionalities?
Or technically the BLE management task would be demanding in computation power so having those task separated would make the design easier?
Would be great if you don't mind sharing your thought on the project goal or my question. I am grateful for your attention anyway.