Myke Predko

Updated I2C Interrupt Driver Trashing Memory

Discussion created by Myke Predko on Jun 1, 2013
Latest reply on Jun 3, 2013 by Myke Predko

I guess this is for Martin and Robert,


I've been using the driver code you provided as the reply to my question of April 19, 2013 ( and it has worked quite well except that periodically it trashes memory in the system. 


When I say "trashes memory" the application locks up to external inputs.  I can still pause execution and when I look at the task summary, the task names after "_mqx_idle_task" are written over with random strings - and the data values, for the most part are randomized (ie the TaskIDs). 


When it does this, it seems to be in circumstances of heavy activity on the bus (primarily to the OLED display in my system).  It does happen randomly (there is no sequence which repeatedly causes the problem).  I have commented out the calls to the new I2C driver calls and I cannot reproduce this problem, which is why I believe the problem is with the I2C Driver. 


Please let me know if you require any additional information from me. 


Thanx guys - any suggestions would be appreciated.