• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 205 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.

AWR1843BOOST: Software crashing while debugging SWI and HWI in TI-RTOS

Tanoop Rajan
Intellectual 271 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: SYSBIOS

I am running the mrr lab_07 on awr1843boost and trying to debug how the events are getting scheduled using RTOS analyzer but when I enable the logging of Swi and Hwi logging 

LoggingSetup.sysbiosSwiLogging = true;
LoggingSetup.sysbiosHwiLogging = true;

my software crashes with the following message 




but this behavior is not observed when I try just Tasklogging

  • +1
    TI__Guru*** 141284 points

    Hi,

    The MRR demo does not support these features. The MRR does not support SWI and does not enable hardware interrupts through sysbios.

    If you are interested in the Interrupts used by the demo, I recommend searching the demo files for the following: "SOC_SysIntListenerCfg"

    The Processing Chain running on the DSP uses the following interrupts:

    • Frame Start Interrupt triggered by the FRAME_START EVENT

    /* Register Frame Start Listener */
            memset((void*) &listenerCfg, 0, sizeof(SOC_SysIntListenerCfg));
            listenerCfg.systemInterrupt = SOC_XWR18XX_DSS_INTC_EVENT_FRAME_START;
            listenerCfg.listenerFxn = MRR_DSS_frameStartIntCallback;

    • Chirp Available Interrupt triggered by the CHIRP_AVAIL EVENT

            /* Register Chirp Available Listener */
            memset((void*) &listenerCfg, 0, sizeof(SOC_SysIntListenerCfg));
            listenerCfg.systemInterrupt = SOC_XWR18XX_DSS_INTC_EVENT_CHIRP_AVAIL;
            listenerCfg.listenerFxn = MRR_DSS_chirpIntCallback;

    Thank you

    Cesar