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.

SYSBIOS - xdc runtime error

Other Parts Discussed in Thread: SYSBIOS

Hello,

I'm working with an application that started reporting a BIOS error, and terminating.  The error is:

    ti.sysbios.hal.Hwi: line xdc.runtime.Error.raise: terminating execution.

I have no idea where this is coming from, or how to debug, and would appreciate any suggestions on how to track it down.

Regards,

Robert

 

P.S.  software versions being used:

    XDC: 3.20.7.86

    IPC: 1.22.3.23

    SYS/BIOS: 6.31.4.27

    XDAIS: 6.23

    CCS:  4.2.3.00004

  • Robert,

    Does the error include a line number? I noticed that the word 'line' is followed by the name of the module that raised the error (instead of the actual line number) and I'm wondering whether this is a simple copy-paste omission.

    Are you actually using HAL Hwi APIs in your application or is this error being raised elsewhere?  Also, have you disabled Asserts in your application?

    Regards,

    Shreyas

  • Thanks for the reply.  There is no line number provided in the error message.

    Could you tell me how to figure out if HAL Hwi APIs are being used?  As far as I know, I've not explictly used them, but I've incorporated some example code that might be.  Please also tell me how to determine if Asserts are being used.

    Robert

  • OK.  I suspect the error is being raised while the Hwi is being created--this seems to be the only place where an Error is raised in the HAL Hwi code.

    Do you see any other raised errors besides the 'HAL Hwi' one?

    When do you encounter this error?  Before getting to main()?  Do you get this after stepping over a Timer_create(..) (Hwi's are most commonly created during the creation of a timer).  Or if you're using IPC, do you get this after stepping over Ipc_start/attach?

  • No other errors besides the HAL Hwi one.  It occurs during the BIOS_start() function call.  Before that, I do a bunch of initialization (PSC, PLL, etc) and then at the end of the initialization, call BIOS_start(), which should result in tasks being started, plus a software interrupt.  But if I step over BIOS_start(), it terminates with the HAL Hwi failure.

    Robert

  • Do you know whether BIOS_start() is failing before any of your tasks start running?  I.e. before you step over BIOS_start, do you set a breakpoint at each of your Task functions' entry point and do you never hit these breakpoints before you get the error?

    Which device/processor are you using?  Does your CCS project have any external dependencies other than the products that you've listed on your first post?  Would you be able to export your project to a .zip file and post it on the forum?

    Regards,

    Shreyas

  • I have 3 tasks, and 2 of them start.  I'm looking into why the 3rd one doesn't.  But I don't think it's the cause of this problem.  What I found is that on the chip I'm using, the C6748, there are 3 interrupt multiplexer registers (INTMUX1, INTMUX2, INTMUX3), which route the interrupt event to the correct interrupt vector.  For some reason, right after loading the code, one of them had an interrupt vector that was not intended.  So now when starting up, before the BIOS_start(), I initialize those registers to valid default values.  And the problem has gone away ;)

    Thanks,

    Robert