Part Number: TMS320F280049
Other Parts Discussed in Thread: SYSBIOS, C2000WARE
Hi,
my customer is using BIOS to configure HWI, and they are also using the lib function(Interrupt_register, interrupt_enable) to configure the interrupt.
Are there any difference of interrupt response priority between these 2 methods?
If you're creating a Hwi, you don't want to use the Interrupt_register() function. SYSBIOS plugs its Hwi dispatcher into the PIE vector table to handle the Hwis, and calling Interrupt_register would overwrite that. Furthermore, since that interrupt is now plugged outside the dispatcher, it can not longer call SYSBIOS scheduler functions like Semaphore_post() or Swi_post().
If the customer does want to intentionally bypass the dispatcher as the cost of not being able to call scheduler functions from the ISR, it should be done through what SYSBIOS calls zero latency interrupts which bypass the Hwi dispatcher to avoid the additional latency it adds. There's more info about it in this thread:
Like I said, the above difference can affect latency, but it doesn't really have an impact on priority. Priority is still determined by the interrupt's location in the PIE and masking in the ISR to allow nesting like we demonstrate in the software prioritized interrupts example in C2000Ware.
Whitney
