Changes between Version 9 and Version 10 of TBR/BSP/Mvme147s


Ignore:
Timestamp:
12/08/10 13:28:48 (13 years ago)
Author:
Jgeralnik
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TBR/BSP/Mvme147s

    v9 v10  
    1414|RAM          = 4-32 MB
    1515}}
     16
     17
     18= Overview =
     19
    1620
    1721
     
    3337
    3438Another small difference between them is the time-of-day clock. The MVME147s has a Mostek MK48T02 while the MVME147 has an M48T18.
     39
     40The MVME147S is a double-high VMEmodule and is best utilized in a 32-bit VMEbus system with both P1 and P2 backplanes. The module has high functionality with large onboard shared RAM, serial ports, and Centronics printer port. The module provides a SCSI bus controller with DMA, floating-point coprocessor, tick timer, watchdog timer, and time-of-day clock/calendar with battery backup, 2KB of static RAM with battery backup, four ROM sockets, and A32/D32 VMEbus interface with system controller functions are also provided. The MVME147S can be operated as part of a VMEbus system with other VMEmodules such as RAM modules, CPU modules, graphics modules, and analog I/O modules.
     41
     42
     43The manual can be found at www.ing.iac.es/~docs/external/vme/147s_d3.pdf
     44= Board Setup =
     45
     46
     47To select the desired configuration and ensure proper operation of the MVME147S module, certain changes may be made before installation. These changes are made through jumper arrangements on the headers. The module has been factory tested and is shipped with factory-installed jumper configurations. The module is operational with the factory-installed jumpers. The module is configured to provide the system functions required for a VMEbus system. It is necessary to make changes in the jumper arrangements for the following conditions:
     48
     49System controller select (J3)
     50Factory use only (J5, J6)
     51ROM configuration select (J1, J2)
     52Serial port 4 clock configuration select (J8, J9)
     53
     54
     55See manual for further information
     56= Downloading and Executing =
     57
     58
     59There are various ways to enter a user program into system
     60memory for execution. One way is to create the program using the
     61Memory Modify (MM) command with the assembler/disassembler
     62option. You enter the program one source line at a time. After each
     63source line is entered, it is assembled and the object code loads into
     64memory. Refer to the MVME147 BUG 147Bug Debugging Package
     65User's Manual for complete details of the 147Bug Assembler/
     66Disassembler.
     67Another way to enter a program is to download an object file from
     68a host system. The program must be in S-record format (described
     69in the MVME147BUG 147Bug Debugging Package User's Manual) and
     70may have been assembled or compiled on the host system.
     71Alternately, the program may have been previously created using
     72the 147Bug MM command as outlined above and stored to the host
     73using the Dump (DU) command. A communication link must exist
     74between the host system and the MVME147. The file is downloaded
     75from the host to MVME147 memory by the Load (LO) command.
     76= Debugging =
     77
     78
     79MVME147Bug package. Facilities are available for loading and executing
     80user programs under complete operator control for system
     81evaluation. See manual for further information
     82
     83= References =
     84
     85
     86 *  www.ing.iac.es/~docs/external/vme/147s_d3.pdf
     87 
     88{{Navbox_BSPs}}