RTOS/CC2650: Is HeapBuff allowed within a SimpleLink application structure?

Anthony Andreoli

Part Number: CC2650

Tool/software: TI-RTOS

Hello,

I am currently running a regular RTOS system w/o the app/stack interface... Just a simple Launchpad implementation. Within this code, I am using my own custom made HeapBuf for a custom made linked list (Using Memory_Alloc and Memory_Free on its corresponding IHeap upcast). I am now looking to implement the SimpleLink App/BLE Stack version of my simple code, and I have read that

"Due to shared resources and to maintain interprocess communication, the application must use the following ICall primitive service functions: • Messaging and Thread Synchronization • Heap Allocation and Management"

Does this mean I can no longer use my custom made HeapBuf, and must now only allocate to a pre-defined ICall heap using ICall_Alloc and ICall_Free ? I am trying to bridge the gap between working on a regular RTOS code, and one that implements the App/BLE stack infrastructure (slowly understanding but it is an uphill climb)

Thank you

over 9 years ago

0 JXS over 9 years ago

TI__Guru** 105180 points

Hello Anthony,

You should be ok to call HeapBuf APIs in your application since they are not blocking. Of course, passing memory into the stack requires the use of the GATT_bm_alloc API.

Best wishes

0 Anthony Andreoli over 9 years ago in reply to JXS

Intellectual 460 points

If i am simply using HeapBuf, why must i use Gat to allocate memory? Can't i just use Memory_alloc?

0 JXS over 9 years ago in reply to Anthony Andreoli

TI__Guru** 105180 points

I didn't say you must use GATT APIs to alloc memory, I said if you are supplying memory to the stack (e.g., for sending an GATT Notification PDU) you must use the GATT bm APIs. If you are just alloc'ing memory for your application, they you can use any supported function.

Best wishes

Bluetooth®︎

Bluetooth forum

RTOS/CC2650: Is HeapBuff allowed within a SimpleLink application structure?