Memory Requirements, SYSFAIL* Assertion/Negation | Motorola MVME162

Debugger General Information

Many times it may be desirable to terminate a debugger command prior to its completion; for example, during the display of a large block of memory. Break allows you to terminate the command.

3SYSFAIL* Assertion/Negation

Upon a reset/powerup condition the debugger asserts the VMEbus SYSFAIL* line (refer to the VMEbus specification). SYSFAIL* stays asserted if any of the following has occurred:

❏confidence test failure

❏NVRAM checksum error

❏NVRAM low battery condition

❏local memory configuration status

❏self test (if system mode) has completed with error

❏MPU clock speed calculation failure

After debugger initialization is done and none of the above situations have occurred, the SYSFAIL* line is negated. This indicates to the user or VMEbus masters the state of the debugger. In a multi-computer configuration, other VMEbus masters could view the pertinent control and status registers to determine which CPU is asserting SYSFAIL*. SYSFAIL* assertion/negation is also affected by the ENV command. Refer to Appendix A.

MPU Clock Speed Calculation

The clock speed of the microprocessor is calculated and checked against a user definable parameter housed in NVRAM (refer to the CNFG command in Appendix A). If the check fails, a warning message is displayed. The calculated clock speed is also checked against known clock speeds and tolerances.

Memory Requirements

The program portion of 162Bug is approximately 512KB of code, consisting of download, debugger, and diagnostic packages and contained entirely in Flash or PROM.

The 162Bug executes from $FF800000 whether in Flash or PROM. With jumper at J22 pins 9-10 installed (factory ship configuration), the Flash memories appear at address $FF800000 and are the parts executed during reset. With this configuration, the PROM socket is mapped to address $FFA00000. If you remove the jumper at J22 pins 9 and 10, the address spaces of the Flash and PROM are swapped.

3-10	MVME162 Embedded Controller Installation Guide

Image 72

Motorola MVME162 manual Memory Requirements, SYSFAIL* Assertion/Negation, MPU Clock Speed Calculation

Contents

MVME162 MVME162IG/D2 Restricted Rights Legend Preface Page Safety Summary Safety Depends On You Page Introduction Overview Related Documentation Document Title Motorola Publication Number Introduction MVME162 Embedded Controller Installation Guide Features Requirements Specifications MVME162 SpecificationsCharacteristics Specifications Special Considerations for Elevated Temperature Operation Manual Terminology Block Diagram MVME162 Block Diagram Front Panel Switches and Indicators Functional Description Data Bus Structure MC68040 or MC68LC040 MPUNo-VMEbus-Interface Option MC68xx040 Cache Memory Options Dram OptionsSram Options About the Battery Battery Backed Up RAM and Clock Eprom and Flash VMEbus Interface and VMEchip2 InterfacesSerial Communications Interface MVME162 Serial Port MVME162 Serial Port IndustryPack IP Interfaces Optional LAN Ethernet Interface Optional Scsi Interface Scsi Termination Programmable Tick Timers Watchdog TimerLocal Bus Timeout Local Resources Connectors Memory MapsLocal Bus Arbiter Local Bus Arbitration Priority Local Bus Memory Map Normal Address RangeLocal Bus Memory Map MVME162 Embedded Controller Installation Guide Local Bus I/O Devices Memory Map Address Range Device Port Width Size MVME162 Embedded Controller Installation Guide VMEbus Accesses to the Local Bus VMEbus Memory MapVMEbus Short I/O Memory Map Board Level Hardware Description Unpacking Instructions Hardware Preparation SIM Selection Hardware Preparation Configuration Part Number Model Standard Serial Interface Module Part Numbers Installation of New SIM System Controller Select Header J1 Clock Select Header J12 for Serial Port J12 Sram Battery Backup Source Select Header J20 Eprom Size Select Header J21 General Purpose Readable Jumpers Header J22 J22 Installation Instructions IP Installation on the MVME162 MVME162 Module Installation System Considerations MVME162 Embedded Controller Installation Guide MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 1 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 2 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 3 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 4 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 5 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 6 SIM07 Hardware Preparation and Installation MVME162 EIA-530 Connection Diagram Sheet 1 MVME162 EIA-530 Connection Diagram Sheet 2 MVME162 EIA-232-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 1 MVME162 EIA-23-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 2 MVME162 EIA-232-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 3 MVME162 EIA-232-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 4 Hardware Preparation and Installation Overview of M68000 Firmware Description of 162Bug MVME162 Embedded Controller Installation Guide Installation and Startup 162Bug Implementation Bit J22 Pins Description Debugger General Information Ote Autoboot ROMboot Network Boot Restarting the System Reset AbortBreak Memory Requirements SYSFAIL* Assertion/NegationMPU Clock Speed Calculation Terminal Input/Output Control DEL Disk I/O Support Blocks Versus Sectors Disk I/O via 162Bug Commands Device Probe FunctionIOI Input/Output Inquiry IOP Physical I/O to Disk BO Bootstrap Operating System BH Bootstrap and HaltDisk I/O via 162Bug System Calls IOC I/O Control Default 162Bug Controller and Device Parameters Disk I/O Error Codes Network I/O SupportIntel 82596 LAN Coprocessor Ethernet Driver UDP/IP Protocol Modules Bootp Protocol Module Network Boot Control ModuleNetwork I/O Error Codes RARP/ARP Protocol Modules Multiprocessor Support Multiprocessor Control Register Mpcr Method Mpar Diagnostic Facilities Gcsr Method Manufacturing Test Process Entering Debugger Command Lines Debugger Syntactic Variables Italic strings Expression as a Parameter Data Type Base Identifier ExamplesString Numeric Value Literal Hexadecimal Address as a Parameter Address FormatsExpression Result In Hex Debugger Address Parameter Formats Format Example Description Offset Registers Relative addresses are limited to 1MB 5 digits, regardlessRange of the closest offset register 162BugMD 1327CDI Port Numbers Entering and Debugging Programs Calling System Utilities from User ProgramsPreserving the Debugger Operating Environment 162Bug Vector Table and Workspace Hardware Functions Exception Vectors Used by 162Bug Exception Vectors Used by 162BugVector Exception 162Bug Facility Offset Using 162Bug Target Vector Table Creating a New Vector Table Buildx MOVEC.L VBR,A0 162Bug Generalized Exception Handler 162BugMD A7&30 Floating Point Support Integer Data TypesFloating Point Data Types Single Precision Real Double Precision RealExtended Precision Real Packed Decimal Real Scientific Notation 162Bug Debugger Command Set Debugger Commands 162Bug Debugger Command Set Norb Configure Board Information Block Cnfg IM Configure and Environment Commands Set Environment to Bug/Operating System ENV D Table A-1. ENV Command Parameters ENV Parameter and Options Default Meaning of Default Ffdffffc Nvram Memory Requirements section Base Address of Dynamic Memory Slave Ending Address #1 Master Starting Address #1 Master Starting Address #3 Table A-1. ENV Command Parameters Configuring the IndustryPacks Bits Register Address FFFBC016 Disk/Tape Controller Modules Supported First Second Controller TypeAddress Disk/Tape Controller Default Configurations Cisc Embedded Controllers -- 7 DevicesMVME320 -- 4 Devices Controller LUN Address Device LUN Device Type MVME323 -- 4 Devices MVME327A -- 9 Devices MVME328 -- 14 Devices MVME350 -- 1 Device IOT Command Parameters for Supported Floppy Types Disk/Tape Controller Data Network Controller Modules Supported Controller Interface TypeAddress Type Network Controller Data Symbols Numerics IN-2 IN-3 IN-4 IN-5 IN-6 Scsi LED Sysfail