wiki:TBR/BSP/Mvme5500

Mvme5500

The MVME5500 is an Emerson (formerly Motorola) VMEBus board. <!-- When filling in the box,

+ Try to include links to other Wiki pages and websites. + If a field is not applicable, not setting the variable will result in it not being displayed + If Simulator is not set, then No. is displayed.

-->

{{Infobox BSP |BSP_name = MVME5500 |Manufacturer = Motorola |image = MVME_5500.png |caption = MVME5500 |Board_URL = EMERSON |Architecture = PowerPC® |CPU_model = MPC7457 PowerPC® |Monitor = MotLoad? |Simulator = Yes. Skyeye |Aliases = |RAM = 512MB ECC SDRAM |NVMEM = 32 MB Flash, 16 KB EEPROM |Serial = Two TL16C550C UARTs |NICs = |Other = MVME5500 data sheet }}

Overview

  • MPC7455 processor at speeds of 1 GHz and beyond
  • 256KB of on-chip L2 cache and 2MB of L3 cache
  • AltiVec? coprocessor for high-performance computational applications
  • 512MB of on-board SDRAM ECC memory and 512MB additional memory via a memory mezzanine card for a total of 1GB of memory
  • 40MB Flash memory (32MB soldered and 8MB in sockets)
  • Dual PCI buses and dual PMC sites with a bus speed of up to 66 MHz
  • Gigabit Ethernet interface and a 10/100BaseTX Ethernet interface
  • 64-bit PCI expansion mezzanine connector allowing up to four more PMCs
  • I/O compatibility with MVME51xx family
  • Single VME slot even when fully configured with two PMC modules or one PMC module and an add-on memory mezzanine

Board Setup

The MVME5500 is user-configurable by setting on-board jumpers. Two I/O modes are possible: PMC mode or SBC mode (also called 761 or IPMC mode). The SBC mode uses the IPMC712 I/O PMC and the MVME712M transition module, or the IPMC761 I/O PMC and the MVME761 transition module. The SBC mode is backwards compatible with the MVME761 transition module and the P2 adapter card (excluding PMC I/O routing) used on the MVME5100 product. This mode is accomplished by configuring the on-board jumpers and by attaching an IPMC761 PMC in PMC slot 1. Secondary Ethernet is configured to the rear.

PMC mode is backwards compatible with the MVME5100 and is accomplished by configuring the on-board jumpers.

TBD - RTEMS specific setup instructions

Downloading and Executing

WARNING: It is extremely important that a MOTLoad "waitProbe", "netShut" sequence be executed before booting RTEMS. Otherwise, network interface interrupt handlers installed by MOTLoad may cause memory corruption

TBD - RTEMS specific download and program execution instructions

Software Support

Firmware Monitor

Firmware must fulfill the traditional functions of power-on self-test (POST), initialization, and operating system booting. Motorola’s innovative firmware (known as MotLoad?) that is resident on the MVME5500 exceeds these requirements with expanded features such as interrupt driven I/O, more comprehensive power-up tests, and extensive diagnostics with new scripting capability. And of course, MotLoad? provides a debugger interface similar to the time proven "BUG" interface on previous VMEbus boards from Motorola.

Libraries

VSI/Pro VSIPL libraries from MPI Software Technology will be available on the MVME5500.

Built-In Test Software

Motorola Built-In Test (MBIT) software is available for use on the MVME5500 series. MBIT is an off-the-shelf software infrastructure designed to verify correct operation of Motorola hardware and enable the incorporation of system-level diagnostics. Two versions of MBIT, board-level and system-level, are available and are compatible with WindRiver? Systems Tornado 2.1. The board-level MBIT is a comprehensive diagnostic software package designed to verify the performance of board- mounted logic devices. All tests can execute at boot-up, while selected tests can run continuously in the background of user applications. An application programming interface (API) is included to provide access to test results and to modify and control the operation of device tests. A comprehensive user’s manual is available. The system-level MBIT includes all functionality and API function calls of the board-level version and enables system-wide testing. The system-level MBIT provides a framework and additional API function calls to support the inclusion of software designed to test custom hardware and/or system components. A comprehensive user’s manual with software development guidelines is available.

References

{{Navbox_BSPs}}

Last modified on Jan 16, 2014 at 8:12:44 AM Last modified on Jan 16, 2014, 8:12:44 AM