Changes between Version 6 and Version 7 of TBR/BSP/Mvme147


Ignore:
Timestamp:
12/08/10 13:16:43 (13 years ago)
Author:
Jgeralnik
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TBR/BSP/Mvme147

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