This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Stress testing of TCPNet TCP socket application

I have an ARM/Cortex application that uses Keil RL-ARM in order to implement RTOS tasks and communication via TCP/IP ports. Because tasks other than the task that runs TCPNet need to talk via TCP ports (and because I am using the original event-based (callback) sockets rather than BSD), I have implemented synchronisation of the transmit / receive data using task management functions (semaphores, mailbox, and so forth).

What I would like to do is test that my synchronisation code is watertight, so I could do with a means to 'exercise' the application perhaps from some PC utility, with the application perhaps put in some test mode where it keeps pinging everything back or spits out checksum debug messages.

What I have in mind is something that keeps chucking various packets to a specified IP and port and then checks to ensure that exactly the same payload is pinged back (e.g. checksum / CRCs compared).

Writing or modifying our own PC application to perform such tests would be trivial, but before I do so, can anyone suggest a freebie utility (Windows / Linux) I could use for this?

0