We have a board with MPC8349E running with VxWorks 5.5.
We got a sporadic (1 time, not reproducible) issue whereby we got a plethora of I2C1 interrupts which caused a kernel workQ panic.
In a usual run, we never get these interrupts, and we never expect it to come.
How do we continue to debug this issue? Could it be that i2c controller somehow got into a bad shape? What info can help to further debug?
Thanks
Dijo
For I2C module interrupt reasons and interrupt processing flowchart please look MPC8548E Reference Manual, Table 11-7 and Figure 11-11.
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Thanks Alexander. On checking our isr code, I could see that the branch on
the right (i.e. I2CCR[MSTA] == 0 and following tree) is not implemented.
Could you help in understanding the impact?
Thanks.
On 4 June 2014 09:08, alexander.yakovlev <admin@community.freescale.com>