RTOS/CC2640: can not find osal_heap_high_water

dsp999

Expert 1495 points

Part Number: CC2640

Tool/software: TI-RTOS

I am checking stack usage.

I used function osal_heap_high_water in ble4.2. but can not find it in blestack5

simplelink_cc2640r2_sdk_1_40_00_45

compiler says:

Error[Li005]: no definition for "osal_heap_high_water" [referenced from C:\ti\simplelink_cc2640r2_sdk_1_40_00_45\examples\rtos\CC2640R2_LAUNCHXL\ble5stack\MySample1\tirtos\iar\app\FlashROM_StackLibrary_RCOSC\Obj\hal.o]

over 6 years ago

0 Evan W over 6 years ago

TI__Mastermind 39870 points

DSP,

Assigning you to someone who can follow up.

That said, you are using a much older SDK. I recommend that you move to a more recent SDK like 3.10 or 3.20.

If you are trying to check heap size, please reference the following:

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_3_10_00_15/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#debugging-common-heap-issues

If you are trying to check stack size of tasks, please reference the following under the last bullet point about using TI RTOS Object Viewer:

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_3_10_00_15/docs/ble5stack/ble_user_guide/html/ble-stack-5.x/creating-a-custom-bluetooth-low-energy-application.html?highlight=stack%20size#ram-optimization

0 dsp999 over 6 years ago in reply to Evan W

Expert 1495 points

thanks, it is helpful. I can know heap size and how much used now.

quesiton:

1, what's the advantage of 3_10 than 1_40

2, in the page it says: Also note that these functions have not been updated for BLE5-Stack, and may not work as expected. This will be updated in the future.

can I count on this function?

how can I know overflow ever happened?

is heapmgrMemMax the value for maximum memory (heap) ever used?

3, how can I set (increase/decrease) heap?

4, I found SBP_TASK_STACK_SIZE in simple_peripheral.c very tricky. how to determine which value should I set for this?

0 Sean2 over 6 years ago in reply to dsp999

TI__Mastermind 33460 points

Hello,

1. What's the advantage of 3_10 than 1_40:

3.10 contains the latest fixes in the stack. You can see what these are in the release notes.

Note that 3.20 will be released in a couple of days, keep an on here: http://www.ti.com/tool/SIMPLELINK-CC2640R2-SDK

2. heapmgrMemMax is updated and should replace osal_heap_high_water. heapmgrMemMax is the max size of the heap. heapmgrMemUB is the max address of the heap.

3. THe heap is automatically given all the space between the end of static allocation and the beginning of the system stack. In theory, it cannot be increased above this number.\

See here for info on configuring the heap

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_3_10_00_15/docs/blestack/ble_user_guide/html/ble-stack-common/memory_management.html#configuring-the-heap

See here for info on the memory map and auto sized heap

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_3_10_00_15/docs/blestack/ble_user_guide/html/ble-stack-common/memory_map.html

4. You can use ROV Task -> detailed to see the high water mark of each task stack including the SBP task. Be sure to apply the workaround listed in the second link

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_3_10_00_15/docs/blestack/ble_user_guide/html/ble-stack-3.x-guide/debugging-index.html#ti-rtos-object-viewer

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_3_10_00_15/docs/blestack/ble_user_guide/html/ble-stack-3.x-guide/debugging-index.html#workaround-for-rov