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

TMDSCNCD263: DebugP_log interrupts ISRs with priority 0

Justin Smith
Prodigy 180 points
Part Number: TMDSCNCD263

Tool/software:

Hi!

I am seeing the DebugP_log trump even ISRs configured with priority 0. 

In my program, I only have 1 interrupt driven by this ISR. In the main loop, I have a periodic DebugP_log statement running to show the state of the system.

i.e. 

```

/* Register & enable interrupt */
HwiP_Params_init(&hwiPrms);
hwiPrms.intNum = CSLR_R5FSS0_CORE0_CONTROLSS_INTRXBAR0_OUT_0;
hwiPrms.priority = 0; /* setting high priority. optional */
hwiPrms.callback = &App_adcISR;
status = HwiP_construct(&gAdcHwiObject, &hwiPrms);
DebugP_assert(status == SystemP_SUCCESS);

```

Even App_adcISR will wait until the cycles needed to run a DebugP_log line. 

Any idea where this is configured / how I can ensure the ISR interrupt runs always?

Thanks!

  • +1
    TI__Expert 5366 points

    Hello,

    The DebugP_log has three ways to output: CCS console, UART or memory dump. You can change it in the DebugP Log option in example.syscfg. For real time environment, you want to use the memory dump, or UART (if the DebugP_log calling frequency is not too high). Never use the CCS console, because it is very intrusive (disable interrupts and slow).

    Regards,

    Sahana