• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 100 subscribers
  • Views 823 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSv4 HeapMem_alloc is causing an abort.

Eddie3909
Guru 10385 points

Other Parts Discussed in Thread: SYSBIOS

CCSv4.2.4, BIOS 6.31.4.27, IPC 1.22.3.23, Processor C6472

I noticed that HeapMem_alloc causes an abort when asked to allocate more memory than available. I've checked the ti.sysbios.heaps.HeapMem documentation and it does not discuss what happens when there is no heap available. I am stepping through the code and when it steps over HeapMem_alloc(), the abort information is output on the console window.

When I decrease the size of requested LL2 heap, it works fine.

If an abort is the expected response, is there a way to tie our own error callback to the abort?

Cheers

 

  • 0
    TI__Mastermind 32475 points

    Eddie,

    Is the HeapMem_alloc() being called from your code?  if so, you could pass in an error block into the call and it shouldn't abort.  If you pass "NULL" as the error block then it does abort.  There's no callback function you can tie to abort.  You would have to write your own xdc.runtime.ISystemSupport module to do this.

    Judah

  • 0 in reply to judahvang
    Guru 10385 points

    Ah!

    Could you point me to the documentation on this behavior? I checked in ti.sysbios.heaps.HeapMem

    C:\Program Files\Texas Instruments\bios_6_31_04_27\docs\cdoc\index.html

    Cheers

  • 0 in reply to judahvang
    TI__Mastermind 20805 points

    Eddie --

    Do avoid the abort, you should do the following:

     

    {
        Error_Block eb;

        Error_init(&eb);
        ptr = HeapMem_alloc(heap, size, align, &eb);

     

    -Karl-

  • 0 in reply to Karl Wechsler
    Guru 10385 points

    Same for HeapMemMP_alloc?

    Cheers

  • 0 in reply to Eddie3909
    TI__Mastermind 45025 points

    Eddie,

    Yes, I see that:

    Ptr ti_sdo_ipc_heaps_HeapMemMP_alloc(ti_sdo_ipc_heaps_HeapMemMP_Object *obj, SizeT reqSize, SizeT reqAlign, Error_Block *eb)

    directly calls the XDC runtime function Error_raise(eb, ...), directly passing eb to it.  This is the same behavior as HeapMem_alloc().

    The Error_rasie() function will abort if the error block argument is NULL.

    Steve


  • 0 in reply to Steven Connell
    Guru 10385 points

    It must be a different IPC version you are using. I get this from the IPC_1_22_03_23 documentation. Unfortunately it does not state what happens when the alloc fails.

    Cheers

    file:///C:/Program%20Files/Texas%20Instruments/ipc_1_22_03_23/docs/doxygen/html/_heap_mem_m_p_8h.html#a04ab3af78110251e5f22f9bc9a961a95

    Void* HeapMemMP_alloc ( HeapMemMP_Handle  handle,
    SizeT  size,
    SizeT  align  
    )

    Allocate a block of memory of specified size and alignment.

    The actual block returned may be larger than requested to satisfy alignment requirements.

    HeapMemMP_alloc will lock the heap using the HeapMemMP gate while it traverses the list of free blocks to find a large enough block for the request.

    Guidelines for using large heaps and multiple alloc() calls.

    • If possible, allocate larger blocks first. Previous allocations of small memory blocks can reduce the size of the blocks available for larger memory allocations.
    • Realize that alloc() can fail even if the heap contains a sufficient absolute amount of unalloccated space. This is because the largest free memory block may be smaller than total amount of unallocated memory.
    Parameters:
    [in]  handle  Handle to previously created/opened instance.
    [in]  size  Size to be allocated (in MADUs)
    [in]  align  Alignment for allocation (power of 2)
    See also:
    HeapMemMP_free
  • 0 in reply to Eddie3909
    TI__Mastermind 20805 points

    There are 2 APIs for HeapMemMP:

    -  ti/ipc/HeapMemMP is the public interface.  This API is documented with doxygen.  This API is portable to host side (Linux) and DSP side.

    - ti/sdo/ipc/heaps/HeapMemMP is the internal implementation of the public implemenation.  This module has a slightly different API from the public one.

    The ti/ipc/HeapMemMP_alloc() API returns NULL on failure.   I filed a bug report asking that we improve the documentation for this -- SDOCM00094029.

    -Karl-