We are running application written in C# under .NET framework under Windows CE 6.0 on our hardware based on LPC3240 with PHY DP83848I. This application communicates with PC over Ethernet. Everything goes well when there is other activity on Ethernet. When we have quite Ethernet (no communication from other nodes) our application stops after couple of hours, e.g. every 2 hours. If during stop state we do ping against our IP address it continues to work. On Ethernet where other packet activity happens our application was running 10 days without any stop. Does anybody know what can be wrong?
None of which has anything to do with Keil!
"Does anybody know what can be wrong?"
You need to talk to the supplier of your .NET implementation...
Sounds like an error in the interrupt handler.
Maybe transmit interrupts are not working as expected, resulting in messages not being resent after a lost packet. The only thing that reactivates the transmit is if you get a receive interrupt and the interrupt handler at that time polls for pending packets to send.
But as already mentioned, this does not have anything with Keil to do.
Sounds like an error in the interrupt handler.<p>
Something stopping working after a certain time with no activity sounds suspiciously like an error in some timeout handler or a similar bug in handling a timer (maybe a timer wraparound isn't handled correctly).