Release Notes for CCII END FDDI Driver --------------------------------------- Version : 1.12 Release date : 2004-06-23 1. Getting Started --------------- 1.1. Boot vxWorks and load the ccFddiEndxxx.a lib with 'ld < ccFddiEndxxx'. Where xxx=Rad for Radstone PPC HCC xxx=X86 for X86 HCC xxx=178 for SVME178 HCC xxx=179 for SVME179 HCC xxx=Mv5100 for MVME5100 HCC xxx=Mv2700 for MVME2700 HCC 1.2. Type 'muxDevStart ( muxDevLoad ( 0 , fddiLoad,"",0,0 ))' to start the driver. 1.3. Type 'ipAttach ( 0, "ccfddi" ) to attach the driver to TCP/IP. Verify that the ccfddi0 device exists by typing 'ifShow'. 1.4. Set the IP address using ifAddrSet. 1.5. Confirm the FDDI connection using ping. An example is shown below (NOTE: This example assumes there is already a NIC on the FDDI LAN which has been set up with an IP address of 10.0.0.1): -> muxDevStart ( muxDevLoad ( 0 , fddiLoad,"",0,0 )) value = 0 = 0x0 -> ifShow lo (unit number 0): Flags: (0x69) UP LOOPBACK ARP RUNNING Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 4096 0 packets received; 0 packets sent 0 input errors; 0 output errors 0 collisions ccfddi (unit number 0): Flags: (0x63) UP BROADCAST ARP RUNNING Netmask 0xffffffff Subnetmask 0xffffffff Ethernet address is 00:00:5a:45:f0:46 Metric is 0 Maximum Transfer Unit size is 4491 18 packets received; 0 packets sent 0 input errors; 0 output errors 0 collisions value = 18 = 0x12 -> ifAddrSet "ccfddi0","10.0.0.4" value = 0 = 0x0 -> ping "10.0.0.1" PING 10.0.0.1: 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=1. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=2. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=3. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=4. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=5. time=0. ms 1.6 See vxWorks documentation for building driver into kernel. 2. Known Issues with the Current Release ------------------------------------- (* = outstanding issue) 2.1 Support for one card only at this stage. (Implemented in Version 1.5) 2.2 No support for END polled mode transmit and receive. (Not supported) 2.3 * MPIC Spurious Interrupt needs to be traced on MVME5100/MVME2700(BSP related). 2.4 * Only support for one FDDI card on the MVME2700 at present. 2.5 SVME179 not stable at high throughput, but pings OK .(Fixes implemented in Version 1.8 ) 3. Revision History ---------------- b1.0 - 2000-02-10 - GJK First release. 1.1 - 2000-06-23 - GJK Traced slow receive and transmit problems to wrong BSP config : Fixed 1.3b- 2001-06-19 - GJK First Beta release of SVME179 driver, not stable at high throughput, but pings OK!! 1.5b- 2001-09-11 - GJK 2 FDDI cards per host now supported on all hosts. First release of MVME5100. FDDI END driver now supports X86, SVME178, SVME179, Radstone PPC, and MVME5100 1.6b- 2002-05-28 - GJK First release of MVME2700. Only support for one FDDI card on the MVME2700 at present. 1.7- 2002-05-28 - GJK Driver now supports command line passing of TRT, MTU size and enabling of OSM mode for bridge applications For MVME2700 also support commandline passing of Base Address and INT number to use e.g. muxDevStart (muxDevLoad (0,fddiLoad,"BaseAddress:IntoNo:TRT:MTU:OSM",0,0)) BaseAddress: Base Address in Hex - Only has effect on MVEM2700 IntNo : Interrupt no to use in Hex - Only has effect on MVME2700 TRT : Token Rotation Time to use in Decimal ms - Default 165ms MTU : Max Transfer Unit size in decimal Bytes - Default 4352bytes OSM : Online Special Mode ON(1) or OFF (0) - Default 0 (OFF) If a parameter is not used a placeholder of 0 MUST be used. e.g. You want to only change the TRT to 100ms muxDevStart (muxDevLoad (0,fddiLoad,"0:0:100:0:0",0,0)) All Parameters preceding the ones you want to change must be specified e.g. You want to only change the TRT to 100ms muxDevStart (muxDevLoad (0,fddiLoad,"0:0:100",0,0)) Use ccfddiStats to confirm your changes. 1.8- OSM void frames fixed. SVME179 now stable. 1.9- Fixed possible problem with interrupt nesting and incorrect handling of RIFF information. 1.10- 2002-10-24 - GJK Added patch to fix incorrect Windriver implementation of ipProto.c. Telnet etc works now. 1.11- 2003-10-09 - GJK Fixed problem with compiling X86 version under vxWorks 5.5. Now uses pciConfigLib.h 1.12- 2004-06-23 - GJK Fixed problem with spurious interrupts by adding some additional intLocks in the send chain. Removed SVME178/179/181 spurious interrupt handler from driver.