| 35 | |
| 36 | |
| 37 | The MVME147 is a double-high VMEmodule based on the |
| 38 | MC68030 microprocessor. It is best utilized in a 32-bit VMEbus |
| 39 | system with both P1 and P2 backplanes. The module has high |
| 40 | functionality with large onboard shared RAM, serial ports, and |
| 41 | Centronics printer port. The module provides a SCSI bus controller |
| 42 | with DMA, floating-point coprocessor, tick timer, watchdog timer, |
| 43 | and time-of-day clock/calendar with battery backup, 4KB of static |
| 44 | RAM with battery backup, four ROM sockets, and A32/D32 |
| 45 | VMEbus interface with system controller functions. |
| 46 | |
| 47 | The manual can be found at ppd.fnal.gov/experiments/e907/TPC/DAQ/147aih.pdf |
| 48 | = Board Setup = |
| 49 | |
| 50 | |
| 51 | Set jumpers on your MVME147 module. |
| 52 | Ensure that ROM devices are properly installed in the sockets. |
| 53 | Install your MVME147 module in the chassis. |
| 54 | Set jumpers on the transition board; connect and install the transition board, P2 adapter module, and optional SCSI device cables. |
| 55 | Connect a console terminal to the MVME712. |
| 56 | Connect any other optional devices or equipment you will be using. |
| 57 | Power up the system. |
| 58 | Note that the debugger prompt appears. |
| 59 | Initialize the clock. |
| 60 | Examine and/or change environmental parameters. |
| 61 | Program the PCCchip and VMEchip. |
| 62 | |
| 63 | See manual for further information |
| 64 | = Downloading and Executing = |
| 65 | |
| 66 | |
| 67 | There are various ways to enter a user program into system |
| 68 | memory for execution. One way is to create the program using the |
| 69 | Memory Modify (MM) command with the assembler/disassembler |
| 70 | option. You enter the program one source line at a time. After each |
| 71 | source line is entered, it is assembled and the object code loads into |
| 72 | memory. Refer to the MVME147 BUG 147Bug Debugging Package |
| 73 | User's Manual for complete details of the 147Bug Assembler/ |
| 74 | Disassembler. |
| 75 | Another way to enter a program is to download an object file from |
| 76 | a host system. The program must be in S-record format (described |
| 77 | in the MVME147BUG 147Bug Debugging Package User's Manual) and |
| 78 | may have been assembled or compiled on the host system. |
| 79 | Alternately, the program may have been previously created using |
| 80 | the 147Bug MM command as outlined above and stored to the host |
| 81 | using the Dump (DU) command. A communication link must exist |
| 82 | between the host system and the MVME147. The file is downloaded |
| 83 | from the host to MVME147 memory by the Load (LO) command. |
| 84 | = Debugging = |
| 85 | |
| 86 | |
| 87 | MVME147Bug package. Facilities are available for loading and executing |
| 88 | user programs under complete operator control for system |
| 89 | evaluation. See manual for further information |
| 90 | |
| 91 | = References = |
| 92 | |
| 93 | |
| 94 | * ppd.fnal.gov/experiments/e907/TPC/DAQ/147aih.pdf |
| 95 | |
| 96 | {{Navbox_BSPs}} |