I'm having a problem where I get i2c errors from the tvp5146 under unusual circumstances. I want to send SNMP traps from my DM368 encoder application. Basically I build a string and execute a system call to invoke the NET-SNMP snmptrap application to send the trap. When I make the system call I will frequently get a hung tvp5146 with i2c errors. The snmp trap apps takes a while to execute, but is executing from it's own thread. I'm thinking of writing a separate app to send the traps and communicate with a pipe.
Could it be that the system call is messing up the i2c? The video continues to encode and stream to the network when the trap app is invoked. And I do have another thread checking the tvp5146 for valid video every 5 seconds.
JohnA