• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 963 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.

Meaning of parameters in Hardware Interrupt Support Module

Simon lapointe
Expert 1315 points

Other Parts Discussed in Thread: SYSBIOS

Hello,

 I want to control the interrupt's priority of my TMS570 application.

  Could-you explain the meaning of the « priority » parameter in the GUI.

 

 

First, which direction goes the priority (The lower the higher?)

And second,  does this parameter overcomes the genuine priority of the processor? For instance, NHET priority is 10 and CAN priority is 16. Is this parameter could change the order?

Also could-you explain theses parameters:

 eventID?

wakeEnable?

My setup is:

TMS570, CCS4.2, SYS/BIOS  6.31.4.27

 

Simon

 

 

 

  • 0
    TI__Mastermind 30830 points

    1) The eventID parameter is not supported on the TMS570 hardware.

    2) The priority value (which can range from 0-63) is used as the CHANMAPx value written to the interrupt's corresponding CHANCTRL register. The lower the number, the higher the priority. Unless explicitly set at Hwi_create() time, or using the Hwi_setPriority() API, the priority/channel of each interrupt is the same as it's interrupt number (ie intNum 0 = priority 0, intNum 63 = priority 63.

    3) The wakeEnable parameter is currently not supported but was envisioned as the parameter that would configure an interrupt's bit in the WAKEMASK registers.

  • 0 in reply to Alan DeMars
    Expert 1315 points

    Thanks.

    It seems that my timers threads (ti_sysbios_hal_Timer) have in fact lower priority than my ISR (ti_sysbios_family_arm_tms570_Hwi) even if their interrupt number are lower (higher priority). Is it possible? Even if in the ROV diagnostic I could see that the priority of hte 20Khz timer is higher (2), I still have jitter in this function as I have CANBUS interrupts (16).

    Are you sure that the priority isn't reversed, the higher the digit, the higher priority?

     

     

    And I don't see where I can configure the priority of my timer thread, tough I can configure the priority of the CAN interrupt (Hwi).

    Simon