Part Number: AM2634
Previously we have implemented custom ethernet driver based on reference of TI Ethernet driver, Then we have faced stopping of Ethernet TX interrupt after some time, not only the interrupt but the Ethernet pheriperal. But rest of the core, like processing in main and uarts are all working fine.
So we have referred the TRM and addendum and remodified the TX handling in ethernet ( moved to software queueing if headpointer is not zero). Then, the interrupt is getting triggered only for first three frames, then the interrupt is not getting triggered , but when i checked descriptors they are getting cleared. So we modifed the implementation to depend on raw interrupt status for reclaiming the tx descriptors. But in this implementation, we are phasing an issue that after long run (1-2 days), the main processing is getting suspended, as well as the rest of the pheripherals. We are not sure about the triggering condition for this.
The RX is being handled using raw interrupt status right from the start.
So can you help us in debbuging why the interrupt of tx is getting stopped, and why the core might get to a hault state.
Thanks & Regards,
Srinivas
