TMS320F28379D: Nesting interrupts with the USER software interrupt

Hi,

I am looking into this and get back to you shortly.

Thanks
Vasudha

Hi,

Thank you!

Hi,

I need some more information to understand the issue. How is the User interrupt getting triggered in the application? How are the tasks getting triggered using USER interrupt?

Thanks
Vasudha

Hello Vasudha,

Yes, why not!

The User interrupt is triggered using the asm("     TRAP #24") instruction.

I have the address of the function task affected to the interrupt vector.

When I execute the TRAP instruction the function is called, but without nesting the Timer interrupt is masked.

In some conditions, the task executed using the USER ISR takes more time and The timer interrupt is not reaching the CPU.

a question please, Nesting in Texas instruments DSP means that inside an interrupt we authorize another interrupt to be executed?

Thank you.

One more thing,

I trayed to add nesting interrupts to the project.

In the USER interrupt, I added the EINT instruction to allow the timer interrupt to be executed.

I added also this code to my Timer 1 Interrupt service routine.

IER &= MINT13; // Set "global" priority
EINT;

In the F2837xD_SWPrioritizedIsrLevels.h, I am setting the Timer1 to higher interrupt.

#define	INT1PL      0        // Group1 Interrupts (PIEIER1)
#define	INT2PL      0        // Group2 Interrupts (PIEIER2)
#define	INT3PL      0        // Group3 Interrupts (PIEIER3)
#define	INT4PL      0        // Group4 Interrupts (PIEIER4)
#define	INT5PL      0        // Group5 Interrupts (PIEIER5)
#define	INT6PL      0        // Group6 Interrupts (PIEIER6)
#define	INT7PL      0        // Group7 Interrupts (PIEIER6)
#define	INT8PL      0        // Group8 Interrupts (PIEIER6)
#define	INT9PL      0        // Group9 Interrupts (PIEIER9)
#define	INT10PL     0        // Group10 Interrupts (PIEIER6)
#define	INT11PL     0        // Group11 Interrupts (PIEIER6)
#define	INT12PL     0        // Group12 Interrupts (PIEIER6)
#define	INT13PL     1        // XINT13
#define	INT14PL     0        // INT14 (TINT2)
#define	INT15PL     0        // DATALOG
#define	INT16PL     0        // RTOSINT

And still has the problem, I could not interrupt the USER interrupt event if I clear INTM.

The user interrupt could not be stopped with the timer1 interrupt, is there any manual context to be done before entering the high priority interrupt?

This is the interrupt assembly code:

Does the nesting have limitations in the debugging mode?

Regards,

Hi,

Are you adding EINT in the user interrupt ISRs i.e. task functions in your case? The above attached assembly is for which ISR? Is the interrupt keyword used with the task functions?

Thanks
Vasudha

Vasudha Bhadoria said:

EINT in the user interrupt ISRs i.e. task functions in your case

Yes, that's right.

Vasudha Bhadoria said:

The above attached assembly is for which ISR?

This is the assembly code of the USER interrupt.

Vasudha Bhadoria said:

Is the interrupt keyword used with the task functions?

Yes, __interrupt keyword is used and the function is called.

Hi,

From where is this Trap to user interrupt is triggered in the application? The interrupt triggerred through Trap would be a non-maskable interrupt and hence cannot be blocked by INTM. C28x core immediately approves this type of interrupt and branches to the corresponding ISR. Since there are 3 non-maskable interrupts in the application, timer ISR might be interrupted due to any of these and resulting in the above shown behaviour.

Thanks
Vasudha

yes, I agree with you,

non-maskable doesn't mean non-interruptible, with the TI example for prioritization I could branch for another interrupt from the pie while the User interrupt is executing.

I have to enable the interrupt inside the USER and it happens.

Hi,

Yes, once the interrupts are enabled inside USER interrupt, timer interrupt should be able to interrupt it. Were you able to resolve the issue?

Thanks
Vasudha

Hi, 

I have some trouble with my project I am using the nesting driver like TI, but I could not see why I could not get out from the user interrupt when the Timer interrupt is triggered.

For this reason, I trying to experiment this ...

Hi,

I will also try this at my end and get back.

Thanks
Vasudha

Hello,

Do you have any updates about this tread pleas?

No, I am yet to try this. I will get back to you on this shortly.