Hi all,
Running our device (luminary LM3S6965, ARM Cortex-M3) in normal operation mode (with domestic like ethernet network traffic) everthing works fine and it acts very stable (tested for more than 4 weeks). However, using the device in an environment with heavy ehthernet traffic (company situation network) generates very regular a ERR_MEM_CORRUPT error at the Net_Config.c->sys_error() function. At this point the watchdog will reset the device (what else ...).
To test this in-stability behaviour I started stress testing it using flood pings, using 2 terminals (Linux). At this point our device is constantly generating above error and resets. I disabled all own traffic, so only traffic on the network triggers TCP handling on our device (like the ping does).
Someone got a clue?
Thanx!
note: Using RL-ARM v3.14a, MDK 3.10a. (Yep, not the latest.. but before changing libraries etc I'd like to know if the problem sounds familiar to someone)
Some addtional info I forgot to mention:
Debugging showed that the caller of the sys_error() function is tcp_poll_sockets() function. Only DHCP / DNS udp sockets (ports 68 and 53) are active and the standard Keil webserver TCP socket on port 80.
regards,
Eric
I updated to latest library RL-ARM v3.21. Using the http_demo instead of my own programm generated the same problems!
Eric, Did you find the cause of this problem?
Hi Tamir,
Yes we did! We could reproduce the problem with standard examples from Keil. The Keil development department then took a look at it. The new (forthcoming) delivery of the RL-ARM environment should fix the problem. Right now we are testing a beta version of RL-ARM to see if things have improved.