開啟原PDF
Contents
1. numCalls 2048 msec call 22 66 calls sec 45 18 C peattcp gt _ rT v Windows host packet capture Using Etherpeek here is a screen shot of the Receive test EtherPeek File Edit View Capture Send Monitor Tools Window Help D HGH 23499 4 72460 gt Packets received 4 506 Memory usage 22 h NETTEN Packets filtered 4 506 Filter state Accept all packets P P ms Ez ox a Qu pe Packet Source o jojq O8Stination Size Absolute Time et Broadcast 64 14 0 10 101 P 10 10 10 64 4 43 714217 IP 10 10 10 64 0 10 10 4 43 715710 IP 10 10 10 101 P 10 i10 4 715844 IP 10 10 10 101 E 10 10 4 716238 IP 10 10 10 101 P 10 10 4 43 717151 IP 10 10 10 64 10 10 4 43 723559 IP 10 10 10 101 E Be 723651 IP 10 10 10 64 E 10 10 10 728175 IP 10 10 10 64 P 10 10 10 4 43 730006 IP 10 10 10 101 0 10 4 43 730078 IP 10 10 10 101 0 10 10 4 s 730123 IP 10 10 10 101 P 10 10 10 6 730167 3rc 1150 Dst 4 sAP Oo p 8983664 L 1460 A 5001 175 IP 10 10 10 64 P 10 10 10 10 4 4 43 737535 Src 4096 Dst 1150 A x 5001 L A 3778983664 W 1460 IP 10 10 10 64 0 10 10 4 43 740699 31 4096 Dst 1150 A 8 5001 1 A 3778985124 W IP 10 10 10 64 P 10 10 10 10 43 741828 Src 4096 Dst 1150 A 3 5001 L A 3778985124 W 43E Ni lt gt Packets Nodes Protocols h Summary Graphs Log Conversations Filters B9 3Com Megah2. It also creates a few tasks and other kernel objects that will inform you about the state of the system 5 02 TTCP startup code main Listing 5 1 main int main void if OS _ TASK NAME SIZE gt 16 CPU_INTO8U err endif BSP_Init Initialize BSP APP_TRACE_DEBUG Initialize OS n OSInit Initialize OS Create start task OSTaskCreateExt AppTaskStart void 0 OS_SIK GAppstartTaskstk APP_START OS CFG TASK SIK SIZE 1 APP_START_OS_CFG_TASK_PRIO APP_START_OS_CFG_TASK_PRIO 05 _STR amp AppStartTaskSstk 0 APP START OS CPG TASK SIK SLlIZPb void 0 OS_TASK_OPT_STK_CHK OS_TASK_OPT_STK_CLR Give a name to tasks if OS_TASK_NAME_SIZE gt 16 OSTaskNameSet OS_TASK_IDLE_PRIO Idle task amp err OSTaskNameSet OS_TASK_STAT_PRIO Stat task amp err OSTaskNameSet APP START OS CFG TASK PRIO Start task amp err endif APP_TRACE DEBUG Start OS n OSStart Start 05 L5 1 1 Initialize the on board l Os Interrupts Timers LEDs and the serial port used for the command line interface 19 5 03 TTCP startup code AppStartTask Note that some lines of the listings have been removed to help you focus on the uC TTCP usage Listing 5 2 AppStartTask static void AppTaskStart void p arg youd p arg Prevent compiler warning APP TRACE DEBUG Initialize interrupt controller n BSP_InitIntCtrl1 Initialize in
3. Packets Nodes Protocols Summary Graphs Log Conversations Fitters j 59 3Com Megahertz LAN PC Card 589E Ethernet Packets 2 060 Duration 00 12 44 For Help press F1 B9 3Com Megahertz LAN PC Card 589E Ethernet o c 0 10 0 10 0 10 10 0 109 0 10 0 10 30 0 10 i10 0 10 10 0 10 10 10 10 10 220 10 10 10 10 10 10710 4 10 210 0 20 t0210 10 160 4 10 10 10 10 10 10 W t uU uU bFo04 OOOO O to w Ud Ww oOID Ur w Nie 9 90190 0 s et i ee i ion to w LS ojoilojlojojoiloloiloiloio e W oOjojoOi i 5noeaoioijo d o i 0000 d W WW U td wid to oD oo w llw Aidididididididididiaidididiatle gBigigigBigigigigBigiBgigiBiBgigi g v Ojocioiloioloioiloioiloilolooioclo IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 PPP PPP Pee PP eRe ee PREP RPP RPP RPP RPP RP RB Re OiOiOoOloiIoloioiloioloiliooooioiloilo PRI RP BBR a ojlo o ooo 9 Oroa 2 c 17 5 00 uC TTCP The TTCP code is found in the following directory and will be briefly described Micrium Software uC TTCP Source The files are LELCD C 1h ee Oe n 5 01 TTCP Code ttcp c This file contains the TTCP code ttcp c Is written to exercise the capabilities of the TTCP testing application The code begins by initializing uC OS I uC TCP IP and the serial port used for user interface
4. also have to remove the maximum IP header size which is 60 bytes NET IP MTU Minimum 1500 1596 IP header size 1500 60 1440 NET UDP MTU IP MTU UDP header size 1440 8 1432 Depending on your configuration you may want to modify the uC TTCP code to accommodate your NET UDP_MTU 6 02 Target performance Again this is an issue that affects UDP particularly the UDP receive test uC TCP IP re assembles fragmented IP packets This issue here is how fast can the target retrieve fragmented packets to reassemble them As a matter of fact with a buffer size to 8192 bytes no data is received by uC TTCP the PC being able to transmit al lot faster than the target can receive We could find a compromise between 8192 and 1432 bytes The sample we provided in this user manual section 4 05 used a buffer size of 1432 bytes Each UDP datagram transmitted by the PC fills one buffer on our target No re assembly is required References LC OS II The Real Time Kernel 2 Edition Jean J Labrosse R amp D Technical Books 2002 ISBN 1 57820 103 9 Embedded Systems Building Blocks Jean J Labrosse R amp D Technical Books 2000 ISBN 0 87930 604 1 Contacts IAR Systems CMP Books Inc Century Plaza 1601 W 23rd St Suite 200 1065 E Hillsdale Blvd Lawrence KS 66046 9950 Foster City CA 94404 USA USA 1 785 841 1631 1 650 287 4250 1 785 841 2624 FAX 1 650 287 4253 FAX e mail rushorders cmpbooks com e mail I
5. buffers 2048 e Length of buffers 1432 Note because uC TCP IP does not presently support transmission fragmentation uC TTCP limits the buffer size to 1432 bytes See the limitations section for the explanation of this buffer size choice e UDP port 5001 Note public domain TTCP uses default port 5001 If a firewall blocks this port please choose another 14 Windows host TTCP session The Windows host running pcattcp must initiate the UDP Receiver part of this test Figure 4 5 shows the command used Command Prompt C pcattcp gt pcattcp r u p 4096 f k PCAUSA Test TCP Utility U2 01 01 08 UDP Receive Test Protocol UDP Port 4096 Buffer Size 8192 Alignment 16384 0 recufrom UDP lt 10 10 10 64 65500 Statistics UDP lt 10 10 10 64 65500 16601688 bytes in 30 05 real seconds 4316 59 Kbit sec numCalls 12160 msec call 2 53 calls sec 404 70 C pcattcp gt a F4 5 Windows host packet capture Using Etherpeek here is a screen shot of the UDP Transmit test 79 EtherPeek LOX File Edit View Capture Send Monitor Tools Window Help amp ss dd srl anm BE mI Packets received 4713 Memory usage 2 5 EMEN Stop Capture Packets filtered 4 713 Filter state Accept all packets Stop Capture tion Size Absolute Time Pr 64 64 19 51 37 381136 2 64 37 382679 U 1478 37 385370 0U 1478 37 387981 U 1478 37 390505 U 1478 251 37 393039 t 1478 51
6. cfg his the uC TCP IP configuration file e os cfg his the uC OS II configuration file This directory also contains the IAR EWARM 4 31a project workspace files Exl ewd Exl ewp Exl eww Micrium Software EvalBoards Cogent CSB337 IAR BSP This directory contains the Board Support Package BSP files and linker file for the project and target development board used for the example used to demonstrate TTCP This directory contains bsp c bsp h CSB33z_lnk_ram xcl net_bsp c e bsp c contains the board support functions for Interrupts Timers LEDs and Serial port e bsp h contains the header definition for bsp c e CSB33x_lnk_ram xcl1 is the linker file for the IAR tool e net_bsp c contains the low level interface functions for the Ethernet controller used in the sample project 2 00 Network setup Even if TTCP stands for Test TCP the TTCP module can perform the following tests Transmitting TCP segments also called TCP Client mode Receiving TCP segments also called TCP Server mode Transmitting UDP datagrams also called UDP Client mode Receiving UDP datagrams also called UDP Server mode TTCP always work in a peer to peer configuration In developing uC TTCP we were always running on a Cogent CSB337 and we were using PCATTCP on a PC Ethernet Hub or Switch F2 1 Network set up Windows system PCATTCP and Packet Capture Sniffer 10 10 10 101 lily u r ee m f 4 ot ae x A i E LI
7. parameter values and press Enter gt These messages are generated as the test starts up ttcp r BufLen 8192 NumBuf 2048 port 5001 tcp ttcp r Listening socket opened 9 ttcp r Waiting for client to request connection These messages indicate that a TCP connection has been accepted from a remote host ttcp r Server socket 8 active When the test exits it displays the test results ttcp r Client socket 8 closed ttcp r Listen socket 9 closed ttcp r 16777216 bytes in 45 34 real seconds 2891 06 Kbit sec ttcp r 9093 I O calls msec call 4 99 calls sec 200 56 As you can see all the default parameters are used e CP is the default Layer 4 protocol used Sinkmode is enabled by default Number of buffers 2048 Length of buffers 8192 TCP port 5001 Note public domain TTCP uses default port 5001 If a firewall blocks this port please choose another 12 Windows host TTCP session The Windows host running pcattcp must initiate the Transmitter part of this test Figure 4 1 shows the command used Command Prompt C pcattcp gt pcattcp t p 4096 f k 10 10 10 64 PCAUSA Test TCP Utility U2 01 01 08 TCP Transmit Test Transmit TCP gt 10 10 10 64 4096 Buffer Size 8192 Alignment 16384 0 TCP_NODELAY DISABLED 0 Connect Connected to 10 10 10 64 4096 Send Mode Send Pattern Number of Buffers 2048 Statistics TCP gt 10 10 10 64 4096 16777216 bytes in 45 33 real seconds 2891 63 Kbit sec
8. 2002 uC OS II Directory Structure Specifically the files are placed in the following directories Micrium Software uC TTCP Doc This directory contains the uC TTCP documentation files including this one Micrium Software uC TTCP Source This directory contains the uC TTCP source files ttcp c and ttcp h Micrium Software uC LIB This directory contains the uC LIB source files the Micrium version of the C library most used utilities The goal of this library is to ease a certification process by providing the source code and documentation for all the functions This directory contains lib def lib mem Lib mem lib_str lib_str DaDa D Micrium Software uC CPU This directory contains the uC CPU source files cpu_def h This file provides definition for byte alignment endianess and critical section handling Micrium Software uC CPU ARM IAR This directory contains the files to configure standard data types cou word configuration critical section configuration and cpu data types for the IAR compiler used for this sample project cpu h and cpu_a s Micrium Software EvalBoards Cogent CSB337 IAR uC APPs Ex1l This directory contains the source code for Example 1 running on a Cogent CSB337 with IAR tools This directory contains app rds includes h net cfg h os_cfg h e app cfg c contains the application OS task priorities and stack space e includes h contains a master include file used by the application e net
9. 37 395601 U 1078 51 37 397227 U 1478 51 37 400094 U 1478 51 37 402637 1 1478 37 405146 1 1478 407738 0 1478 37 410272 U 1078 37 411925 U 10 10 64 1478 E 37 415037 0U 10 10 64 1478 251 37 417336 0 acr 3 lt gt Packets Nodes Protocols Summary Graphs Log Conversations Fitters Capturing 59 3Com Megahertz LAN PC Card 589E Ethernet Packets 4 713 Duration 00 00 31 For Help press Fi By 3Com Megahertz LAN PC Card 589E Ethernet pm p i J 04 97 32 E3 Ol 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 10 10 64 vu Uv vid b EP DA I un oj ololoiloiloloiloioloiloloiojololo ojojoloiloio T nj d I Pham H H HPoO p O O O W 2 OO OOOO 0O m s d yom w Mo tg Bd ERI RCM RA RI I He He 9 0 0100 e gt v 010 0 019010 0 01090101 0 0 010 0 0 PIP IP RPI RP RPP PPP PRR Re YYYY wid tu to Ye do to 0 W lolol ojojo H e EA pip RP PP PPP I I B P I PO TP E IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 Ci t qididqdidic Cia ica ici OIGO IO 515150 50 000 Dro 5 a F4 6 15 4 05 UDP Receive Test Target To start the TTCP UDP Receive Test start uC TTCP with the r option followed by the u option and the l option see note below gt r u 1 1432 The UDP receiv
10. 9 closed ttcp t 16777216 bytes in 38 38 real seconds 3415 38 Kbit sec ttcp t 2111 I O calls msec call 18 18 calls sec 55 01 As you can see all the default parameters are used TCP is the default Layer 4 protocol used Sinkmode is enabled by default Number of buffers 2048 Length of buffers 8192 TCP port 5001 Note public domain TTCP uses default port 5001 If a firewall blocks this port please choose another 10 Windows host TTCP session The Windows host running pcattcp must initiate the Receiver part of this test Figure 4 1 shows the command used Command Prompt C Xpcattcp pcattcp r p 4096 Ff k PCAUSA Test TCP Utility U2 01 01 08 TCP Receive Test Local Host Christian SRE EE EE EE Listening On port 4096 Accept TCP lt 10 10 10 64 65500 Buffer Size 8192 Alignment 16384 0 Receive Mode Sinking discarding Data Statistics TCP lt 10 10 10 64 65500 16777216 bytes in 41 84 real seconds 3132 40 Kbit sec numCalls 2227 msec fcall 19 24 calls sec 53 22 F4 1 Windows host packet capture Using Etherpeek here is a screen shot of the Transmit test 79 EtherPeek File Edit View Capture Send Monitor Tools Window Help D dg nAdA 4 7240 gt t Capture 1 Packets received 4801 Memory usage C20 Stop Capture Packets filtered 4 801 Filter state Accept all packets Stop Capture E E ej Destinatio vod oo oic CG e RI A R
11. L5 2 4 The task 1 toggles LED 3 on the CSB337 board This activity can tell you that the application is running i e the OS is doing its job L5 2 5 Output the TTCP application banner with the first command line prompt The application is ready to take user commands L5 2 6 Clear all LED so that their state is known at the beginning of the idle task loop 20 6 00 uC TTCP module limitations Designed for embedded systems in mind uC TCP IP works with the usually resource constrained platforms available At this stage uC TCP IP does not support some functionality For example uC TCP IP now only supports a single Network Interface uC TTCP must work with these limitations mainly for UDP with the absence of IP transmit fragmentation and the performance of the target versus a PC 6 01 IP transmit fragmentation The absence of IP transmit fragmentation has an impact on the UDP transmit test Because uC TCP IP can not fragment a packet on transmission the maximum size of UDP datagram is then limited by the maximum size of the Network Interface frame size The Maximum UDP datagram is based on the IP packet size to which the UDP header size is removed 8 bytes The IP packet size is the minimum between the configured Maximum Transmission Unit and the Large buffer size In our tests we have set the MTU to 1500 which is standard for any Ethernet based Network Interface Our Large Buffer Size was set to 1596 bytes From this minimum we
12. Micrium Copyright 2005 2007 Micrium All Rights reserved UC T TCP Test TCP User s Manual www Micrium com Empowering Embedded Systems Table of Contents 1 00 Introduction 1 01 Directories and Files 2 00 Network setup 3 00 PCATTCP 3 01 Network Analyzer Sniffer 4 00 uC TTCP 4 01 uC TTCP command line 4 02 TCP Transmit Test 4 03 TCP Receive Test 4 04 UDP Transmit Test 4 05 UDP Receive Test 5 00 uC TTCP 5 01 TTCP Code ttcp c 5 02 TTCP startup code main 5 03 TTCP startup code AppStartTask 6 00 uC TTCP module limitations 6 01 IP transmit fragmentation 6 02 Target performance References Contacts 1 00 Introduction Test TCP or TTCP is a test tool to perform TCP IP or UDP IP performance tests TTCP is a command line sockets based benchmarking tool for measuring performance between two systems It was originally developed in 1984 by Mike Muuss and Terry Slattery for the BSD operating system The original TTCP and sources are in the public domain and copies are available from many anonymous FTP sites This document describes how to configure and use the uC TTCP module in a uC TCP IP and uC OS II environment We used the Cogent CSB337 single board computer and IAR s Embedded Workbench to demonstrate the examples but other embedded platforms and tool chains can be used 1 01 Directories and Files The code and documentation of the uC TTCP module are placed in a directory structure according to AN
13. S d wonwln Cn 4 Ww ho OjloOIiOIoOIoioiloic H d d 30 874373 0 877391 879678 3rc 65501 Dst 4 A p 37 13 0 879767 CE 3rc t096 Dst 65501 A 3 479268 30 882784 3 rc 65501 Ds 408 UN suu tb 0 885061 E 3rc 65 1 Dst 4 5 A 357 lt Packets l Nodes Protocols Summary Graphs Log Conversations Filters Capturing B9 3Com Megahertz LAN PC Card 589E Ethernet Packets 4 801 Duration 00 01 13 For Help press F1 B3 3Com Megahertz LAN PC Card 589E Ethernet pir N tu ytd Ie ac p d IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 IP 1 10 IP 10 EPAI IP 1 IP 1 IP 1 Ep IP I IP 1 eiee ee oO oo oo o oloic ojloloilolojoilo c ja 10 10 64 F4 2 11 4 03 TCP Receive Test Target To start the TTCP TCP Receive Test start uC TTCP with the r option ADUXE The TCP receiver will start and then wait until a remote TTCP client makes a connection attempt Here is an example of the output you would see ttcp r BufLen 8192 NumBuf 2048 port 5001 tcp ttcp r Listening socket opened 9 ttcp r Waiting for client to request connection ttcp r Server socket 8 active ttcp r Client socket 8 closed ttcp r Listen socket 9 closed ttcp r 16777216 bytes in 45 34 real seconds 2891 06 Kbit sec ttcp r 9093 I O calls msec call 4 99 calls sec 200 56 uC TCP IP Performance measurements Type the TTCP parameters
14. With uC TTCP the Serial port is used as the standard I O Standard stream has only been implemented in Receiver mode The code for Transmitter mode still needs to be developed Defaults The uC TTCP defaults for the command parameters are Parameter Value Command line o FNumberofbufersused 248 m Layer4potnumer 500 Pp po x Enabled Block read Disabled B LONE AN second Socket options MNotsuppoted d X Buffer TCP writes Not supported D T4 1 4 02 TCP Transmit Test Target To start the TTCP TCP Transmit Test start uC TTCP with the t option followed by the dotted IP address of the remote TTCP client pL A IDOL ttcp t BufLen 8192 NumBuf 2048 port 5001 tcp gt 10 10 10 101 ttcp t Client socket 9 opened ttcp t Client socket 9 connected ttcp t Client socket 9 closed ttcp t 16777216 bytes in 41 87 real seconds 3130 30 Kbit sec ttcp t 2099 I O calls msec call 19 95 calls sec 50 13 uC TCP IP Performance measurements Type the TTCP parameters and parameter values and press Enter gt These messages are generated as the test starts up LtLOp t BufLen 9192 NumBuf 20495 port 5001 tep gt 10 104 10 101 ttcp t Client socket 9 opened These messages indicate that a connection has been established with the remote host ttcp t Client socket 9 connected When the test exits it displays the test results ttcp t Client socket
15. er will start and then wait until a remote TTCP client makes a connection attempt Here is an example of the output you would see ttcp r BufLen 1432 NumBuf 2048 port 5001 udp ttop r UDP socket 9 opened ttcp r Waiting for client to send UDP datagrams ttcp r Client socket 9 closed ttcp r 1241544 bytes in 2 47 real seconds 3928 54 Kbit sec ttocp ri 967 I O calls msec call 2 85 calls sec 351 15 uC TCP IP Performance measurements Type the TTCP parameters parameter values and press Enter gt These messages are generated as the test starts up ttcp r BufLen 1432 NumBuf 2048 port 5001 udp ttcp r UDP socket 9 opened ttcp r Waiting for client to send UDP datagrams These messages indicate that a UDP connection has received the last signaling packet less than 4 bytes from the remote host ttcp r Client socket 9 closed When the test exits it displays the test results ttcp r 1241544 bytes in 2 47 real seconds 3928 54 Kbit sec ttcp r 867 I O calls msec call 2 85 calls sec 351 15 As you can see all the default parameters are used e Sinkmode is enabled by default e Number of buffers 2048 e Length of buffers 1432 Note The transmission buffer size is fixed as the maximum UDP datagram to allow time for target to retrieve a maximum of data because of the absence of flow control in UDP See the limitations section for the explanation of this buffer size choice e UDP port 5001 Note publ
16. ertz LAN PC Card 589E Ethernet Packets 4 506 Duration 00 00 14 For Help press Fi B3 3Com Megahertz LAN PC Card 589E Ethernet Qm o o Q0 Mie F4 4 13 4 04 UDP Transmit Test Target To start the TTCP UDP Transmit Test start uC TTCP with the t option followed by the u option followed finally by the dotted IP address of the remote TTCP client s ee Le TO el LOL The UDP transmitter will start Here is an example of the output you would see ttcp t BufLen 8192 NumBuf 2048 port 5001 udp gt 10 10 10 101 ttcp t Client socket 9 opened ttcp t Client socket 9 connected ttcp t Client socket 9 closed ttcp t 16777216 bytes in 30 06 real seconds 4361 07 Kbit sec ttcp t 12288 I O calls msec call 2 45 calls sec 408 85 uC TCP IP Performance measurements Type the TTCP parameters parameter values and press Enter gt These messages are generated as the test starts up ttcp t BufLen 8192 NumBuf 2048 port 5001 udp gt 10 10 10 101 ttcp t Client socket 9 opened These messages indicate that a UDP transmission is in progress toward the remote host ttcp t Client socket 9 connected When the test exits it displays the test results ttcp t Client socket 9 closed ttcp t 16777216 bytes in 30 06 real seconds 4361 07 Kbit sec ttcp t 12288 I O calls msec call 2 45 calls sec 408 85 As you can see all the default parameters are used e Sinkmode is enabled by default e Number of
17. ic domain TTCP uses default port 5001 If a firewall blocks this port please choose another 16 Windows host TTCP session The Windows host running pcattcp must initiate the UDP Transmitter part of this test Figure 4 7 shows the command used Command Prompt C pcattcp gt pcattcp t u 1 1432 p 4096 f k 10 10 10 64 PCAUSA Test TCP Utility U2 01 01 08 UDP Transmit Test Transmit UDP gt 10 10 10 64 4096 Buffer Size 1432 Alignment 16384 0 Send Hode Send Pattern Number of Buffers 2048 Statistics UDP gt 10 10 10 64 4096 2932736 bytes in 2 45 real seconds 9340 40 Kbit sec numCalls 2050 msec call 1 23 calls sec 835 71 C pcattcp gt _ Windows host packet capture Using Etherpeek here is a screen shot of the UDP Receive test 78 EtherPeek POX File Edit View Capture Send Monitor Tools Window Help amp ss dd srl anm gt OX Packets received 2 060 Memory usage i lo L Stop Capture Packets filtered 2 060 Filter state Accept all packets Stop Capture gt Ej s Q Packet Source Destination Je hbBsolute Time Protocol 09 09 09 09 09 09 09 092 09 09 09 09 09 38 38 467285 U 38 468606 U 38 469765 U 38 470914 U 38 472107 U 38 473372 U 38 474473 U 38 475661 38 476861 1 38 478063 U 38 479257 0 38 480452 0 ap Lipo Re 0 10 09 2 38 481671 0 10 10 10 09 38 482880 U 31 S 32 lt gt
18. ired transmit data rate in bytes second Options specific to r B for Ss only output full blocks as specified by 1 lt for TAR T touch access each byte as it s rea C peattcp gt 3 01 Network Analyzer Sniffer In our test setup we also used a Software based Network Analyzer sometimes called a Sniffer Micrium used Etherpeek Though you can see global network statistics without capturing packets for some analysis sessions you ll want to capture packets Etherpeek is a commercial product of WildPackets Inc To find more information about Etherpeek please use the following link http www wildpackets com products etherpeek nx Public domain Network Analyzers are also available One of the most popular that we can also recommend is Ethereal You can download Ethereal from http www ethereal com 4 00 uC TTCP uC TTCP is compliant with the other TTCP tools available in the public domain It was written for target systems running UC OS II and uC TCP IP This section describes the uC TTCP usage 4 01 uC TTCP command line As soon as the application is launched on the target via a JTAG interface or other means the Terminal Window running on the Development system will display the application status and a command line The user controls uC TTCP by entering parameters on the command line The command usage is displayed if the user makes an error entering the command line or by pressing ENTER at the gt command pr
19. nfo IAR com WEB http www cmpbooks com WEB www IAH com Micrium Inc Validated Software 949 Crestview Circle Lafayette Business Park Weston FL 33327 2590 Trailridge Drive East Suite 102 USA Lafayette CO 80026 1 954 217 2036 USA 1 954 217 2037 FAX 1 303 531 5290 e mail 1 720 890 4700 FAX Christian Legare Micrium com e mail Sales ValidatedSoftware com WEB www Micrium com WEB www ValidatedSoftware com
20. ompt Here is the command usage Usage t options host options Common options Verein length of buffers read from or written to network default 8192 i use UDP instead of TCP p port number to send to or listen at default 5001 S t source a pattern to network r sink discard all data from network m set SO DEBUG socket option not supported b set socket buffer size not supported i X format for rate k K kilo bit byte m M mega g G giga Options speciric to rti n number of source buffers written to network default 2045 D don t buffer TCP writes sets TCP_NODELAY socket option Options specific to f E for only output full blocks as specified by 1 T touch access each byte as it is read As an example to start the TTCP TCP Receive Test start uC TTCP with the r option DUE The TCP server will start and then wait until a remote TTCP client makes a connection attempt Instead of explaining all of the uC TTCP options we will be going through a few examples that illustrate basic usage oinkmode s The simplest and most popular TTCP mode of operation is called sinkmode In this mode of operation the TTCP transmitter sends a fabricated data pattern and the TTCP receiver simply sinks discards any data that it receives This is the default TTCP mode of operation otandard Streams Alternatively TTCP can use what is called standard streams or standard I O
21. rt pcattcp C pcattcp gt pcattcp Without any arguments pcattcp will output the command usage For more detailed information about the pcattcp commands please refer to the html help file by double clicking on PCATTCP chm This will automatically open a help file F3 1 e Command Prompt C gt cd peattcp C pceattcp gt pcattc PCAUSA Test TCP Utility U2 01 01 08 sage pcattcp t options host lt in 1 peattcp r options gt out Common options 1 length of bufs read from or written to network Cdefault 8192 gt use UDP instead of TCP H port number to send to or listen at Cdefault 5 61 gt toggle sinkmode Cenabled by default sinkmode enabled t source transmit fabricated pattern r sink lt discard gt all received data sinkmode disable t reads data to be transmitted from stdin F writes received data to stdou align the start of buffers to this modulus default 16384 start buffers at this offset from the modulus default verbose print more statistics set SO_DEBUG socket option set socket buffer size Cif supported format for rate k K kilotbit byte gt m M mega g G giga t send continuous ty r accept multiple connections sequentially concurrent TCP UDP multithreaded receiver Options specific to t number of source bufs written to network default 2048 E don t buffer TCP writes Csets TCP_NODELAY socket option wu HH milliseconds of delay before each write default gt L des
22. terrupt controller APP TRACE DEBUG Initialize OS timer n Tmr Init Initialize OS timer APP TRACE DEBUG Initialize OS statistic task n OSSEaEInit 0 Initialize OS statistic task AppInit TCPIP Initialize TCP IP stack AppInit DHCPc Initialize DHCP client if present APP TRACE DEBUG Create application task n AppTaskCreate Create application task APP TRACE DEBUG Wn F X XXX KCKCKkCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCk Ck Ck OK M APP TRACE DEBUG n 5 APP_TRACE_DEBUG n Micrium uC TCP IP TTCP Performance measurement APP TRACE DEBUG n AT91RM9200 on Cogent CSB337 SDK APP TRACE DEBUG n APP TRACE DEBUG n XXX kkCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCk Ck OK M APP TRACE DEBUG Mn TTCP_Init Initialize TTCP application LED Oft LED Off 2 LED Off 3 while DEF YES Task body always written as an infinite loop OSTimeDlyHMSM 0 0 0O 100 L5 2 1 Start the uC OS II task responsible to collect OS statistics in case we want to analyse the performance of the application with a Kernel Awareness module or uC OS View L5 2 2 Initialization of the uC TCP IP stack L5 2 3 Configuration of the TCP IP stack using DHCP service The application could also be modified to use static values
23. v M a a ud 0 a 3 T EM 3 CT Cogent CSB337 10 10 10 64 Development system Debugger and Termnial Window The target system is running Micrium uC TTCP The Windows station also needs to run a TTCP application The next section describes the Windows TTCP implementation Micrium has selected 3 00 PCATTCP For our development Micrium has selected the PCAUSA port of TTCP to Windows Sockets for the TTCP module running on the Windows host It is called pcattcp It is not part of the official release but you can download it from Micrium s web site and put it in the directory Micrium Software uC TTCP pcattcp This directory should then contain the following files PCATTCP chm PCATICP exe RELEASE TXT sourcesv2 Z1ip ttcpzip exe e PCATTCP chm is the pcattcp html help file e PCATTCP exe is the tool itself e RELEASE TXT contains release information for the pcattcp versions e sourcesv2 zip isa winzip file containing the pcattcp sources e ttcpzip exe a Self extract zip file containing the 4 files above the download result You can also download pcattcp from ftp ftp pcausa com utilities ttcpzip exe You will find more information about pcattcp at http www pcausa com Utilities pcattcp htm Running pcattcp e Copy the content of ttcpzip exe to a directory C pcattcp for example e Open a DOS prompt window e Change directory to the directory now containing pcattcp exe e From the DOS prompt sta
Download Pdf Manuals
Related Search