Hi Stan
The demo project is has a bit of everything in it. It tries to provide a simple project but at the same time quite a complete set of tools - this is of course not a simple balancing act!
If you go into the configuration file
config.h you can turn off almost everything and then just activate the things that you need for your particular tests. For example if you deactivate the Ethernet interface (comment out #define ETH_INTERFACE) it will remove the interface and all TCP/IP parts, leaving not much more than a blinking LED and serial interface, if desired. (Individual protocols and features can usually be controlled in a similar way - eg. activate the Ethernet but deactivate TCP and UDP to leave just ICMP and ARP for a ping test...)
However there is not a great deal of sense in doing this unles you want to strip the code size to the smallest possible for some reason. The reason is that the project uses the uTasker OS which effectively means that all modules are running as tasks and so can be considered in isolation to each other (modular). The file
application.c does still define a details about which of the services are actually started and this file can be manipulated for more control for your own tests.
I would also use the search function in the forum since most of the individual topics are handled in some detail with general code examples.
Examples are:
TCP:
http://www.utasker.com/forum/index.php?topic=25.0UART http://www.utasker.com/forum/index.php?topic=54.0If you concentrate on the particaular code parts of interest, you should be able to focus on the parts which are relevant for yourself without getting lost in the rest.
Good luck
Regards
Mark