User Manual FDDI Adapter VxWorks Enhanced
Contents
1. endif INCLUDE CCFDDI END 6 Rebuild all VxWorks images xxx 178 for SVME178 PPC 179 for SVME179 X86 for Intel X86 or Rad for Radstone PPC1a CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 3 of 10 3 2 To Load the Driver Software Separately From the VxWorks shell type ld lt ccFddiEndxxx a 3 3 Starting the Driver The driver is started and attached to the MUX with the VxWorks muxDevLoadand muxDevLoad commands The syntax is as follows muxDevStart muxDevLoad unitno fddiLoad 0 O where unitno should usually be O Zero If two FDDI cards are installed on the same host unitno 0 for the first card and unitno 1 for the second card This is only necessary if the driver was not included in the configNet h file as described in paragraph 3 1 Type muxShow to see if the driver was installed 3 3 1 Command Line Passing of FDDI Settings The FDDI Driver supports the changing of some default parameters at startup e g muxDevStart muxDevLoad 0 fddiLoad BaseAddress IntoNo TRT MTU OSM 0 0 BaseAddress 3 Base Address in Hex Only has effect on MVME2700 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 chang2. 2 2 1 ANSI INCITS 229 Information Systems Fibre Distributed Data interface FDDI Station Management SMT dated 1994 01 01 CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 2 of 10 3 Installation Procedure This paragraph describes the installation instructions for the FDDI END VxWorks Software Driver 3 1 To Build the FDDI END VxWorks Software Driver Into the VxWorks Kernel 1 Copy ccFddiEndxxx a to your Board Support Package BSP library directory eg tornado target config svme 1 78 lib 2 Edit the Makefile in the BSP directory eg tornado target config svme1 78 Find the line MACH EXTRA and replace with MACH EXTRA lib ccFddiEndxxx a 3 Add the following code fragment to config h before define DEFAULT BOOT LINE Added by CCII for FDDI driver define INCLUDE CCFDDI END CCII FDDI END DRIVER CCII Modification ifdef INCLUDE CCFDDI END ifndef INCLUDE PCI define INCLUDE PCI endif ifdef INCLUDE BSD undef INCLUDE_BSD endif ifndef INCLUDE END define INCLUDE END endif endif End CCII Modification 4 In config h change the DEFAULT BOOT LINE to use the ccfddi driver 5 Add the folowing to configNet h Before the start of the endDevTbI decleration IMPORT END OBJ fddiLoad char initString Add the following segment to the endDevTbI before the default last entry ifdef INCLUDE CCFDDI END 0 fddiLoad NULL NULL FALSE
3. Update to include description of command line argument passing 2002 07 26 Improve document naming consistency 2009 08 20 CCII FDDI 6 ECP 034 CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 Contents T SCOPE JE 1 1 1 e oet PER ML D c 1 1 2 INTFOCUCUO ND e M c eet a Ge Meee a AE ele i pie Peis a upd ae eae hie Pesan adhe ee by ated Pied 1 2 Applicable and Reference Documents 0 0 cece eee 2 2 1 Applicable Documents sse LuumecseiikgWeeilelliRiReDuegR sw eld HE wee Rn RU LA dG 2 2 2 Reference Documents 0 00 c ce ete eee eee eee 2 3 Installation Procedure osse kIkeEREEERXEXFENYEXEPeESEREXESERERERECEREXEREXGRS 3 3 1 To Build the FDDI END VxWorks Software Driver Into the VxWorks Kernel lusus 3 3 2 To Load the Driver Software Separately 00 c cece tetas 4 3 3 Starting the Diver ova vist ecu cert eoe sven NUS US Senda Baty Galea ea Pes Datis PAS EIN ee Nae Paes 4 3 3 1 Command Line Passing of FDDI Settings 0 00 c eee ae 4 3 4 Attaching Driver to TCP IP Stack 0 nnana ccc ee hs 5 4 Application Program Interface API 0 0 0 6 4 1 Driver FUNCIONS cU Tc EPI 6 4 1 1 void ccfddiGetStats int unit struct cc fddi mib type data 0 000 cece eee 6 4 1 2 void ccfddiClrStats int unit liiis 6 4 2 Driver Data Structures 2 00 ees 6 4 2 1 cc fddi mib type 0 2 lr hr 6 4 3 Application Example
4. CT Systems CCII Systems Pty Ltd Registration No 1990 005058 07 Communications Computer Intelligence Integration g User Manual for the FDDI Adapter VxWorks Enhanced Network Software Driver C Systems Document No CCII FDDI 6 MAN 001 Issue Date 2009 08 20 Print Date 2009 08 20 File Name P FDDIKTECH MAN CFDMANO1 WPD C4 Systems The copyright of this document is the property of C2l Systems The document is issued for the sole purpose for which it is supplied on the express terms that it may not be copied in whole or part used by or disclosed to others except as authorised in writing by Cl Systems Document prepared by C I Systems Cape Town Signature Sheet mm e EN era N S QOOAQ OB QO Project Ngineer Board Level Products Completed by Accepted by Project Manager Board Level Products C Systems Lo Cyr Accepted by K Kenger 2009 08 20 Issue 1 3 Page ii of v CCII FDDI 6 MAN 001 CFDMANO1 WPD Signature Sheet Completed by Project Engineer Board Level Products C l Systems Accepted by Project Manager Board Level Products C212 Systems Quality Assurance C l Systems CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 Amendment History a owe Initial version created for END Driver review 2000 06 21 EL Updated to include support for multiple cards per single host 2002 04 03 l
5. cc ddiTimerTwosComp2Sec which demonstrate how ANSI time values are interpreted CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 7 of 10 5 Geiting Started 1 Boot VxWorks and load the ccFddiEndxxx a lib with ld lt ccFddiEndxxx a 2 Type muxDevStart muxDevLoad unitno fddiLoad 0 0 to attach and start the driver Verify by using muxShow The unitno should usually be O Zero If two FDDI cards are installed on the same host unitno 0 for the first card and unitno 1 for the second card 3 Attachthe Drivertothe TCP IP protocol stack Type ipAttach unitno ccfddi Use muxShow and ifShow to confirm that the ccfddiunitno exists and was attached to TCP IP 4 Set the IP address using ifAddrSet Refer to the VxWorks Programmers Guide paragraph 5 2 5 TCP IP Internet Protocols and Addresses and paragraph 5 3 Configuring the Network for setting up IP host names and IP routing 5 Confirm the FDDI connection using ping An example is shown below Note This example assumes there is already a Local Area Network NIC on the FDDI Local Area Network LAN which has been set up with an IP address of 10 0 0 1 gt muxDevStart muxDevLoad O fddiLoad 0 O value 0 0x0 gt ipAttach 0 ccfddi value 0 0x0 gt ifShow ppp unit number 0 Flags 0x71 UP POINT TO POINT ARP RUNNING Internet address 172 16 0 2 Destination Internet address 172 16 0 1 Netmask Oxffff000
6. 0 0 1 icmp seq 5 time 0 ms CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 9 of 10 6 Contact Details 6 1 Contact Person Direct all correspondence and or support queries to the Project Manager at C I Systems 6 2 Physical Address C212 Systems Unit 3 Rosmead Place Rosmead Centre 67 Rosmead Avenue Kenilworth Cape Town 7708 South Africa 6 3 Postal Address Cl Systems P O Box 171 Rondebosch 7701 South Africa 6 4 Voice and Electronic Contacts Tel 27 0 21 683 5490 Fax 27 0 21 683 5435 Email info ccii co za Email support ccii co za URL http Awww ccii co za 6 5 Product Support Support on C I Systems products is available telephonically between Monday and Friday from 09 00 to 17 00 CAT Central African Time CAT GMT 2 CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 10 of 10
7. 0 Subnetmask Oxffff0000 Metric is O Maximum Transfer Unit size is 1 500 5 packets received 5 packets sent 0 input errors 0 output errors 0 collisions lo unit number 0 Flags 0x69 UP LOOPBACK ARP RUNNING Internet address 127 0 0 1 Netmask Oxff000000 Subnetmask Oxff000000 Metric is O Maximum Transfer Unit size is 4 096 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 Oxffffffff Subnetmask Oxffffffff Ethernet address is 00 00 5a 45 f0 46 Metric is O Maximum Transfer Unit size is 4 491 18 packets received 0 packets sent 0 input errors 0 output errors 0 collisions value 18 0x12 xxx 178 for SVME178 PPC 179 for SVME179 X86 for Intel X86 or Rad for Radstone PPC1a Known Bug In SENS1 under Tornado 1 You can not have more than one driver with the same unitno So if you have an ethernet driver installed as etherO you can not have a ccfddiO but must make the unitno 1 This will change it to ccfddi1 This bug has been fixed in Tornado 2 CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 8 of 10 gt ifAddrSet ccfddi0 10 0 0 4 value 0 0x0 gt 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
8. 1 1 esee Re IR xe hm Pat wed ox ee hus m ee 7 5 Getting Started 20 0 0 en 8 5 Contact Details 4 444 rex o 56 ESAS ESAS Vea te bob Phe bos hae Coe X EU do ig 10 6 1 Contact PEPSI ics 3 5 sees shines ts whack c c U 10 6 2 Physical Address is ute t tere etoile ger e er ead anglers ter Gunde oir ceeg di to 10 6 3 Postal Address uum 1s asd e RC aq e e ede DE o P Ee uU ab E e PRA EAR IHE YEN I eee De ae 10 6 4 Voice and Electronic Contacts s saate enea a E eas 10 6 5 Product SUpport ETE Em 10 CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 Abbreviations and Acronyms BIT Built in Test BSD Berkley Software Distribution BSP Board Support Package END Enhanced Network Device FDDI Fibre Distributed Data Interface ICMP Internet Control Message Protocol IP Internet Protocol LAN Local Area Network MIB Management Information Base NIC Local Area Network PC Personal Computer PCI Peripheral Component Interconnect PMC Peripheral Component Interconnect Mezzanine Card SENS Scalable Enhanced Network Stack SMT Station Management TCP Transmission Control Protocol VME Versa Module Eurocard CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 1 Scope 1 1 Identification This document is the User Manual for the Cl Systems Fibre Distributed Data Interface FDDI Enhanced Network Device END VxWorks Software Driver 1 2 Introduction The FDDI END VxWorks Software Driver was developed specifically to operate o
9. e 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 To keep all setting at default values use muxDevStart muxDevLoad unit fddiLoad 0 0 Use ccfddiStats int unit to confirm your changes xxx 178 for SVME178 PPC 179 for SVME179 X86 for Intel X86 or Rad for Radstone PPC1a Known Bug In SENS 1 under Tornado 1 You can not have more than one driver with the same unitno So if you have a ethernet driver installed as etherO you can not have a ccfddiO but must make the unitno 1 This will change it to ccfddi1 This bug has been fixed in Tornado 2 CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 4 of 10 3 4 Attaching Driver to TCP IP Stack Attach the Driver to the TCP IP protocol stack with ipAttach unitno ccfddi Use muxShow and ifShow to confirm CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 5 of 10 4 Application Program Interface API 4 1 Driver Functions 4 1 1 void ccfddiGetStats int unit struct cc fddi mib type data This function is allows an application to access information about the driver as stored in the MIB If two FDDI cards are installed on the same host unitno 0 for the first card and unitno 1 for the second card 4 1 2 void ccfddiClrStats int unit Th
10. gned int smt ecm state unsigned int smt cf state unsigned int smt remote disconnect flag unsigned int smt station status unsigned int smt peer wrap flag unsigned long int smt time stamp unsigned long int smt transition time stamp unsigned int mac frame status functions unsigned int mac t max capability unsigned int mac tvx capability unsigned int mac available paths unsigned int mac current path unsigned char mac upstream nbr CC ALEN unsigned char mac downstream nbr CC ALEN unsigned char mac old upstream nbr CC ALEN CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 6 of 10 unsigned char mac old downstream nbr CC ALEN unsigned int mac dup address test unsigned int mac requested paths unsigned int mac downstream port type unsigned char mac smt address CC ALEN unsigned int mac t req unsigned int mac t neg unsigned int mac t max unsigned int mac tvx value unsigned int mac frame cts unsigned int mac copied cts unsigned int mac transmit cts unsigned int mac error cts unsigned int mac lost cts unsigned int mac frame error threshold unsigned int mac frame error ratio unsigned int mac rmt state unsigned int mac da flag unsigned int mac una da flag unsigned int mac frame error flag unsigned int mac ma unitdata available unsigned int mac hardware present unsigned int mac ma unitdata enable unsigned int path tvx lower bound unsigned int path t max lower bound unsigned i
11. is function resets the following counters in the FDDI MIB fddiMACFrame Ct fddiMACCopied Ct fddiMACTransmit Ct fddiMACError Ct fddiMACLost Ct fddiPORTLCTFail Ct fddiPORTLem Reject Ct fddiPORTLem Ct If two FDDI cards are installed on the same host unitno 0 for the first card and unitno 1 for the second card 4 2 Driver Data Structures 4 2 1 cc fddi mib type struct cc fddi mib type unsigned int rx packets total packets received unsigned int tx packets total packets transmitted unsigned int rx errors bad packets received unsigned int tx errors packet transmit problems unsigned int rx dropped no space in linux buffers unsigned int tx dropped no space available in VxWorks unsigned int multicast multicast packets received unsigned int transmit collision always 0 for FDDI Detailed FDDI statistics unsigned char smt station id 8 unsigned int smt op version id unsigned int smt hi version id unsigned int smt lo version id unsigned char smt user data 32 unsigned int smt mib version id unsigned int smt mac cts unsigned int smt non master cts unsigned int smt master cts unsigned int smt available paths unsigned int smt config capabilities unsigned int smt config policy unsigned int smt connection policy unsigned int smt t notify unsigned int smt stat rpt policy unsigned int smt trace max expiration unsigned int smt bypass present unsi
12. n DY4 s SVME178 and Radstone s PPC1a host carrier cards and Intel X86 PC platforms As such the drivers binaries are provided with explicit installation instructions The FDDI END VxWorks Software Driver conforms to the VxWorks 5 4 END driver model and the driver will interface to VxWorks using the standard The FDDI adapters attach computers to 100 Mbit s FDDI networks using fibre optic cable The driver software distribution consists of the following files ccFddiEndxxx a FDDI driver object file Readme txt Installation notes Release txt Release notes and revision history Please check this file for information on the latest updates ccMib h Defines the structure cc fddi mib type for accessing the FDDI Management Information Base MIB ShowStat c Sample C program for accessing the FDDI MIB xxx 178 for SVME178 PPC X86 for Intel X86 or Rad for Radstone PPC1a CCII FDDI 6 MAN 001 2009 08 20 Issue 1 3 CFDMANO1 WPD Page 1 of 10 2 Applicable and Reference Documents 2 1 Applicable Documents 2 1 1 DI IPSC 81443 Data Item Description for a Software User Manual 2 1 2 ISO IEC 9314 6 X3 229 Information technology Fibre Distributed Data Interface FDDI Part 6 Station Management SMT 7 October 1993 2 1 3 CCII A500 IMS 6 MAN 1 PMC FDDI Network Card Installation Guide 2 1 4 VxWorks 5 4 Programmer s Guide edition 1 2 1 5 RFC 1512 FDDI Management Information Base dated September 1993 2 2 Reference Documents
13. nt path max t req unsigned int path configuration 8 unsigned int port my type 2 unsigned int port neighbor type 2 unsigned int port connection policies 2 unsigned int port mac indicated 2 unsigned int port current path 2 unsigned char port requested paths 3 2 unsigned int port mac placement 21 unsigned int port available paths 2 unsigned int port pmd class 2 unsigned int port connection capabilities 2 unsigned int port bs flag 2 unsigned int port lct fail cts 2 unsigned int port ler estimate 2 unsigned int port lem reject cts 2 unsigned int port lem cts 2 unsigned int port ler cutoff 2 unsigned int port ler alarm 2 unsigned int port connect state 2 unsigned int port pcm state 2 unsigned int port pc withhold 2 unsigned int port ler flag 2 unsigned int port hardware present 2 This structure defined in ccMib h is used to return the results of ccfddiGetStats A detailed explanation of the meanings of these fields may be found in the ANSI document FDDI Station Management SMT Note that these definitions differ slightly from those defined in RFC 1512 FDDI Management Information Base 4 3 Application Example Included in the driver distribution is sample source code ShowStat c which shows how to use the ccfddiGetStats function to retrieve the FDDI MIB information The program simply prints out the contents of the MIB Included in the source code are two functions cc ddiTime2Sec and
Download Pdf Manuals
Related Search