This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How can I get the additional heap memory in cc2650 TIMAC?

Other Parts Discussed in Thread: TIMAC, CC2650

Hi

I'm on a project using a cc2650 launchpad and TIMAC

I tried to add some feature to TIMAC for research purpose.

Then, my device failed to receive any packet.

I found it was because the heap memory space is shorted, so the device cannot allocate memory to rx buffer.

We need additional heap memory space, maybe below a 1k byte, I think.

How can I use additional heap space?

I increased BIOS.heapSize several hundred but it was no use.

Thank you

  • There are a two heaps in the TI-MAC sample application.

    If you are using the function Memory_alloc (from SYS/BIOS), then you have to change BIOS.heapSize.

    If you are using ICall_malloc, then you need to increase the size HEAPMGR_SIZE in heapmgr.h

    If that doesn't work, then it most probably is not a heap issue.

    Michel
  • Thank you for  answering me

    I tried to, but it doesn't work.

    Do you have any idea of solving this problem?

    I found it goes to "Heap memory full" state of rxStartIsr in mac_rx

  • Hi,

    Before I go any further, you should Reject my previous answer since it did not solve your problem. In addition, others might not look into your question since they might think that it was not answered.

    I have tried to locate the MEM_ALLOC function definition, but it seems to be in ROM the code is not available. It seems like there might be another heap. Maybe somebody from TI can give you a better answer about which heap is used in the rxStartIsr function.

    I do have some more questions for you that might help find where the problem is:

    Can you break before it displays the error message to see what the message payload length is?

    If not, do you know what length of data your are expecting?

    Can you give us an idea of what changes you have made to get this error?

    Were the changes made in the TIMAC stack image or in the application image?

    Michel