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.
Hi,
According to the definitions of ESM errors Grop1 to Group3, Group3 errors just activateS ERROR pin output, not trigger low priority and high priority interrupt.
But why do Group3 errors appear in the ESM interrupts callback function?
Hi shenruming,
Started working on your issue and will provide an update soon.
—
Thanks & regards,
Jagadish.
Hi Shenruming,
Just verify the available Interrupt enable SET and CLEAR registers in ESM registers description section.
ESMIESR1 and ESMIECR1 registers will enable and disables the Group1 Channel[31:0] respectively.
ESMIESR4 and ESMIECR4 registers will enable and disables the Group1 Channel[63:32] respectively.
And similarly, ESMIESR7 and ESMIECR7 registers will enable and disables the Group1 Channel[95:64] respectively.
So, in conclusion ESM Group1 errors have configurable interrupt generation. ESM Group2 and Group3 doesn't have these registers for error configurations.
If you see ESMSR2 register,
This register bits indicates interrupt status, that means all ESM group2 errors have predefined interrupt generation.
But if we verify the ESMSR3,
This register bits not indicating any interrupt status, that means all ESM group3 errors doesn't have interrupt generation.
But why do Group3 errors appear in the ESM interrupts callback function?
Did you practically create and test any of the group3 errors given in the interrupt calls? I don't think it will work.
--
Thanks & regards,
Jagadish.
Hi Jagadish,
Since group3 error will not be reported thru ESM interrupt callback function at all, why do they appear in callback function?
Hi Shenruming,
why do they appear in callback function?
Yes, that was strange, did you test any of the errors practically and see whether they are hitting interrupt handler or not?
--
Thanks & regards,
Jagadish.