• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 238 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Understanding xdc runtime Error_block

John Smith
Prodigy 50 points
Other Parts Discussed in Thread: SYSBIOS

Hi,

I'm running a modified version of the mmWave demo with a custom raiseHook, but I'm not sure how to decode the xdc runtime Error_block it accepts. Where do the ID and site module ID fields come from? I'm getting a line number, but no file name, so this is all I have to work with.


Thanks.

  • 0
    TI__Guru*** 138329 points

    Can you please share with us the error message? Sometimes these messages are hard to understand and not very useful

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 50 points

    Hi,
    There's no error message per se, but my raise hook is being passed an Error_block struct with an ID of 1114112, site module ID 40, and line 221. I believe there is an assert somewhere in the code, but I'm unable to find it with this information. I believe these values are auto-generated by CCS, but I can't find any references to how.
    Thanks.

    Edit: Here's my configuration for the raise hook if that's any use.

    var errorHandler = xdc.useModule('xdc.runtime.Error');
errorHandler.raiseHook = '&WriteAssertLog';

    Edit 2: I managed to find out the ID is an ti_sysbios_heaps_HeapMem_E_memory error, but I'm still not sure where to look for the site module ID.

  • 0 in reply to John Smith
    TI__Guru*** 138329 points

    Hi,

    Based on my experience, unfortunately the xdc debug information is not very useful.

    It seems this issue is related to the heap memory.

    I recommend to increase the heap memory if possible

    thank you

    Cesar