I2C interrupt priority

Hi,

All of the interrupt sources are represented by a bit in the aforementioned registers. Therefore, the priority of processing these is up to the code base you are pulling from.

Thanks,

Dear Ganapathi.
I don't understand you, I'm sorry. I try to explain why I asked you.
I2C module acts as a slave and I2C master device writes 3 bytes to DSP. I've assumed the first I2C interrupt vector should be AAS (0x7), then ICRRDY (0x4), ICRRDY (0x4), ICRRDY (0x4) and SCD (0x6). But sometimes I've got ICRRDY (0x4) and then AAS (0x7), or ICRRDY (0x4), ICRRDY (0x4) and only then AAS (0x7). That's why I've asked you about I2C interrupt flags priority.
Best regards,
Miloserdin Oleg

Dear Ganapathi!

And another question:

Sometimes (I've tested I2C module for a long time) I2C interrupt is fired, but I2C interrupt vector value read from ICIVR register is 0 (None). What does it mean?

Best regards,

Miloserdin Oleg

Hi,

Have you properly configured the both CIC and CorePac INTC for I2C interrupt on your test code?

Take a look at below thread to check your interrupt configuration
e2e.ti.com/.../876950

Thanks,

Dear Ganapathi!
I wrote that I've tested I2C module for a long time, so, yes, I've properly configured the both CIC and CorePac INTC for I2C interrupt.
If not so, how could I got I2C interrupt vector values I wrote about before?
Best regards,
Miloserdin Oleg

Dear Ganapathi!

Do you have any suggestions about I2C interrupt vector values I wrote about before?

Or TI hasn't tested I2C module at all?

I have another unanswered question about I2C module:

e2e.ti.com/.../1261269.

Best regards,
Miloserdin Oleg