Motorola MVME197LE manual Physical Layer Manager Ethernet Driver, UDP/IP Protocol Modules

Page 56

		Debugger General Information
		Physical Layer Manager Ethernet Driver
		This driver manages/surrounds the Ethernet controller chip or board.
		Management is in the scope of the reception of packets, the transmission of
3
3		packets, receive buffer flushing, and interface initialization.

This module ensures that the packaging and unpackaging of Ethernet packets is done correctly in the Boot PROM.

UDP/IP Protocol Modules

The Internet Protocol (IP) is designed for use in interconnected systems of packet-switched computer communication networks. The Internet protocol provides for transmitting of blocks of data called datagrams (hence User Datagram Protocol, or UDP) from sources to destinations, where sources and destinations are hosts identified by fixed length addresses.

The UDP/IP protocols are necessary for the TFTP and BOOTP protocols, TFTP and BOOTP require a UDP/IP connection.

RARP/ARP Protocol Modules

The Reverse Address Resolution Protocol (RARP) basically consists of an identity-less node broadcasting a “whoami” packet onto the Ethernet, and waiting for an answer. The RARP server fills an Ethernet reply packet up with the target's Internet Address and sends it.

The Address Resolution Protocol (ARP) basically provides a method of converting protocol addresses (e.g., IP addresses) to local area network addresses (e.g., Ethernet addresses). The RARP protocol module supports systems which do not support the BOOTP protocol (next paragraph).

BOOTP Protocol Module

The Bootstrap Protocol (BOOTP) basically allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed.

TFTP Protocol Module

The Trivial File Transfer Protocol (TFTP) is a simple protocol to transfer files. It is implemented on top of the Internet User Datagram Protocol (UDP or Datagram) so it may be used to move files between machines on different networks implementing UDP. The only thing it can do is read and write files from/to a remote server.

3-14	Installation Guide

Image 56

Contents MVME197LE Restricted Rights Legend Preface Document TerminologyBIT Related Documentation Document Title Motorola Publication NumberPage Page Safety Summary Safety Depends on YOU Contents Hardware Preparation and Installation Using the 197Bug Debugger Appendix a Configure and Environment Commands List of Figures Xiv List of Tables Xvi Introduction OverviewRequirements Features MVME197LE Specifications SpecificationsBlock Diagram Block Diagram Bus Data Bus 256 BusSwitch MC88110 Address Data MUX AddressMezzanine Address Bus Memory ArrayFront Panel Switches and Indicators Functional DescriptionData Bus Structure MC88110 MPUFlash Memory Onboard DramBattery Backup RAM and Clock VMEbus InterfaceInterfaces Serial Port InterfacePrinter Interface Ethernet InterfaceScsi Interface Scsi TerminationPeripheral Resources Connectors Memory MapsInterrupt Sources Processor Bus Memory MapProcessor Bus Memory Map DramsizeAddress Range Devices Accessed Port Size Local Devices Memory MapVMEbus Short I/O Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Memory Map Unpacking Instructions Hardware PreparationHardware Preparation and Installation VMEbus Connector P1 Configuration Switch S1 General Information Configuration SwitchesSwitch S1 S1-1 to S1-8 OFF -- All Ones Factory Configuration Installation Instructions Switch S6MVME197LE Module Installation System Considerations MVME197LEIG/D1 Hardware Preparation and Installation Overview of M88000 Firmware Description of 197Bug197Bug Implementation Installation and Start-upComparison With M68000-Based Firmware Terminal to make sure XON/XOFF handshaking is enabled OteAutoboot ROMboot Network BootReset Restarting the SystemAbort BreakMPU Clock Speed Calculation Memory RequirementsSYSFAIL* Assertion/Negation Terminal Input/Output Control DELDevice Probe Function Disk I/O SupportBlocks Versus Sectors Disk I/O via 197Bug Commands Disk I/O via 197Bug System Calls DskcfigNetwork I/O Support Default 197Bug Controller and Device ParametersDisk I/O Error Codes Bootp Protocol Module Physical Layer Manager Ethernet DriverUDP/IP Protocol Modules RARP/ARP Protocol ModulesNetwork Boot Control Module Network I/O Error CodesMultiprocessor Support Multiprocessor Control Register Mpcr MethodMpar Diagnostic Facilities Gcsr MethodDebugger General Information Entering Debugger Command Lines DebuggerSyntactic Variables Expression as a ParameterData Type Base Identifier Examples Offset Registers Address as a ParameterAddress Formats Entering and Debugging Programs Port NumbersCalling System Utilities From User Programs Preserving The Debugger Operating Environment197Bug Vector Table and Workspace Hardware FunctionsFloating Point Support CPU/MPU RegistersScientific Notation Single Precision RealDouble Precision Real 197Bug Debugger Command Set Debugger CommandsNocm Noma Name Nioc RL Addrbhw Using the 197Bug Debugger Configure Board Information Block Cnfg MISet Environment to Bug/Operating System ENV DTable A-1. ENV Command Parameters ENV Parameter and Options Default Meaning of DefaultConfigure and Environment Commands Ffbffffc Table A-1. ENV Command Parameters Memory Requirement s 01FFFFFF Table A-1. ENV Command Parameters Efffffff FF7FFFFF Table A-1. ENV Command Parameters Table A-1. ENV Command Parameters Table A-1. ENV Command Parameters DISK/TAPE Controller Data Disk/Tape Controller Modules SupportedDisk/Tape Controller Default Configurations Single Board Computers 7 DevicesMVME320 4 Devices MVME323 4 DevicesMVME327A 9 Devices MVME328 14 DevicesMVME350 1 Device IOT Command Parameters for Supported Floppy Types IOT ParameterDisk/Tape Controller Data Network Controller Data Network Controller Modules SupportedNetwork Controller Data Symbols NumericsIN-2 IN-3 Nvram A-2 XON/XOFF Index

Related manuals

Manual 78 pages 27.46 Kb