Motorola MVME197LE manual Bit

Page 4

Data and address sizes are defined as follows:

A byte is eight bits, numbered 0 through 7, with bit 0 being the least significant.

A two-byte is 16 bits, numbered 0 through 15, with bit 0 being the least significant. For the MVME197series and other RISC modules, this is called a half-word.

A four-byte is 32 bits, numbered 0 through 31, with bit 0 being the least significant. For the MVME197 series and other RISC modules, this is called a word.

An eight-byte is 64 bits, numbered 0 through 63, with bit 0 being the least significant. For the MVME197 series and other RISC modules, this is called a double-word.

Throughout this document, it is assumed that the MPU on the MVME197 module series is always programmed with big-endian byte ordering, as shown below. Any attempt to use small-endian byte ordering will immediately render the MVME197Bug debugger unusable.

BIT

 

 

 

 

 

 

BIT

63

56

55

48

47

40

39

32

 

 

 

 

 

 

 

 

ADRO

 

ADR1

 

ADR2

 

 

ADR3

 

 

 

 

 

 

 

 

31

24

23

16

15

08

07

00

 

 

 

 

 

 

 

 

ADR4

 

ADR5

 

ADR6

 

 

ADR7

 

 

 

 

 

 

 

 

The terms control bit and status bit are used extensively in this document. The term control bit is used to describe a bit in a register that can be set and cleared under software control. The term true is used to indicate that a bit is in the state that enables the function it controls. The term false is used to indicate that the bit is in the state that disables the function it controls. In all tables, the terms 0 and 1 are used to describe the actual value that should be written to the bit, or the value that it yields when read. The term status bit is used to describe a bit in a register that reflects a specific condition. The status bit can be read by software to determine operational or exception conditions.

Image 4
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 Block Diagram SpecificationsMVME197LE Specifications 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 Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Short I/O Memory Map Unpacking Instructions Hardware PreparationHardware Preparation and Installation VMEbus Connector P1 Switch S1 Configuration SwitchesConfiguration Switch S1 General Information 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 197BugComparison With M68000-Based Firmware Installation and Start-up197Bug Implementation Terminal to make sure XON/XOFF handshaking is enabled OteAutoboot ROMboot Network BootReset Restarting the SystemAbort BreakSYSFAIL* Assertion/Negation Memory RequirementsMPU Clock Speed Calculation Terminal Input/Output Control DELBlocks Versus Sectors Disk I/O SupportDevice Probe Function Disk I/O via 197Bug Commands Disk I/O via 197Bug System Calls DskcfigDisk I/O Error Codes Default 197Bug Controller and Device ParametersNetwork I/O Support 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 Address Formats Address as a ParameterOffset Registers 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 RegistersDouble Precision Real Single Precision RealScientific Notation 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