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.

TMDXIDDK379D: SYS/BIOS and Minimal Latency Interrupts

Part Number: TMDXIDDK379D

Hello everyone,


maybe, it is a discrepancy in TI documentation.

If the bit INTM is set, all maskable interrupts are disabled. It is correct and it does not matter if the interrupts are managed by SYS/BIOS or not (see the image below)

But on the following website it says something different
https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/953170/faq-are-there-any-c28-device-specific-items-with-ti-rtos-sys-bios?tisearch=e2e-sitesearch&keymatch=faq%3atrue


Is it a spelling mistake? If not, what is the best way to enable and disable all interrupts (managed by SYS/BIOS and "minimal latency interrupt")?


Thanks in advance - Bui van Linh

  • Different Hwi functions are generated depending on whether or not zeroLatencyIERMask == 0. When there are no zero-latency interrupts, it will just set INTM, but when there are it will use the zero-latency interrupt mask to clear IER, leaving the zero-latency interrupts enabled.

    To disable all interrupts, you could use Hwi_disableIER() and pass it a mask that covers all the interrupts.

    Whitney

  • Good morning Whitney,

    thank you very much for your quick reply. It is now clear to me how to enable and disable interrupts with functions of SYS/BIOS.

    I use both SYS/BIOS and DriverLib for my development. DriverLib also provides some functions for handling interrupts.

    I think I shouldn't use these functions. Otherwise it will lead to a conflict with SYS / BIOS. Is it correct?

    Apart from the functions for handling interrupts, DriverLib has many other functions for various topics. Can I use these functions without risking conflict with SYS/BIOS?

    Thank you in advance and best regards

    Bui van Linh

  • Otherwise it will lead to a conflict with SYS / BIOS. Is it correct?

    Yes, for managing interrupts, it's best to use the equivalent Hwi module functions instead of the driverlib.

    Can I use these functions without risking conflict with SYS/BIOS?

    There are some possible conflicts that you need to look out for with Timers, SYSCLK, and Flash configurations. There's some discussion in this thread. For the most part the driverlib functions for those modules are okay to use as long as you've disabled the related options in SYS/BIOS.