Quantcast
Channel: Wireless Connectivity
Viewing all articles
Browse latest Browse all 116964

Forum Post: RE: OSAL Design/Architecture

$
0
0

Hello TI Employees and other Devs,

I am part of a team using the CC2541 EM R1.1 and CC2541 Mini Development Kit. We are trying to figure out the OSAL before we can tackle the BLE stack. So far our Library of TI Documentation for the OSAL includes:

  • SWRU271D Texas Instruments CC2540/41 Bluetooth Low Energy Software Developers Guide v1.3
  • SWRA194 OS Abstraction Layer Application Programming Interface
  • SWRA193 HAL Drivers Application Programming Interface
We are also looking for better information to understand code flow, events, OSAL state diagrams and hardware resource used (timers needed by the OSAL, RAM used etc). Are there any other documents that Devs or TI employees could recommend to better understand and come to terms with the OSAL and as a separate matter the BLE Stack?
This is also my first time using Bluetooth, I have had a little experience with RtOSs and many years experience in Embedded C. The CC2541 is a fun little chip to program, quite easy to use and manipulate. The using OSAL is a much more difficult task.
I have seen in the forums that the only method to create new OSAL projects using the BLE stack for the CC254x is to modify an existing project. This is a viable work around, but is not a long term solution. It would be great if TI could provide a blank project template or instructions to create OSAL projects to assist Devs who are working with the OSAL and BLE stack. TI could also assist Devs by providing projects to introduce features and functions of the OSAL (task creation, execution, order manipulation etc). Are there  projects available to demonstrate the OSAL purely as an operating system?
I'm also aware the OSAL is not an RtOS (SWRU271D says so), but has anyone had any success in making it perform hard-real time tasks? As an example could I use an ISR to periodically interrupt any other task (even BLE stack) and make an ADC acquisition. This would be stored into a FIFO and be manipulated and dealt with by tasks which are less important than BLE stack tasks when there is OS time available. Has anyone tried this?
Regards,
Morgan

Viewing all articles
Browse latest Browse all 116964

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>