Key Technical Specifications

Parameter	Specification
Processor	MPC7457 PowerPC @ 1.267 GHz with 128-bit AltiVec co-processor
VMEbus Interface	Tundra Tsi148, 2eSST protocol, up to 320 MB/s throughput
System Memory	Up to 1GB DDR SDRAM with ECC protection, 133 MHz bus
Flash Memory	128MB (two 64MB banks, switch-selectable boot bank)
L3 Cache	2MB DDR SRAM @ 211 MHz
Ethernet	Dual 10/100/1000 Mbps RJ-45 (Broadcom BCM5461S PHY)
Serial Ports	2x asynchronous (ST16C554D UART), 1x front-panel RJ-45
PMC Slots	2x PMC-X (33/66/100 MHz, IEEE 1386.1 compliant)
NVRAM/RTC	32KB MK48T37 with battery-backed real-time clock
OS Support	VxWorks, Linux, QNX
Form Factor	6U Eurocard, VMEbus standard
System Controller	Marvell MV64360 Discovery II

 

Product Introduction

I’ve pulled these boards out of VME crates in steel mills and power plants where the ambient temperature would make a laptop shut down in minutes. The MVME6100 was Motorola’s answer to the question: “What happens when you need real-time determinism but your old MVME1600 series can’t keep up anymore?” It slots into a standard 6U VME chassis and just works. No fuss, no proprietary backplane requirements.What makes this board worth hunting down today is the MPC7457 running at 1.267 GHz paired with that 128-bit AltiVec co-processor. For data-intensive tasks like vibration analysis or high-speed motion control, it punches well above its weight class. The 2eSST VMEbus interface delivers a real-world 320 MB/s across the backplane — that’s four times what the older 2eVME boards managed. I’ve seen these run VxWorks with sub-millisecond scan times in turbine control applications. One thing to watch: the -0163 revision uses IEEE-style handles while the -0161 uses Scanbe handles. They’re functionally identical, but if your crate has a specific handle type requirement, make sure you order the right suffix.

Quality SOP & Tech Pitfalls

The Lab Report (SOP):
Every MVME6100 goes through a five-step check before it ships. Visual inspection under magnification for counterfeit markings, cold solder joints, or capacitor swelling. Live power-up on our VME test rack — we verify the MOTLoad firmware boots, all LEDs sequence correctly, and the board passes its own POST. We run a full RAM march test and an ECC error monitor check using the built-in MOTLoad diagnostics (testRamMarch, testRamEccMonitor). Ethernet loopback on both ports confirms the Broadcom PHY is healthy. Finally, we log the firmware revision, seal the board in anti-static packaging, and tag it with the test date.The Engineer’s Warning (Pitfalls):
Two things will brick your swap before you even get the cover back on the crate. First: write down your VME address and interrupt settings from the old board before you pull it. The MVME6100 uses jumper-configured VME address modifiers and interrupt levels. I once watched a technician spend six hours chasing a “board not responding” fault because he assumed the new board shipped with the same jumper configuration as the old one. It didn’t. Second: the NVRAM battery (MK48T37) dies. If your board has been sitting on a shelf for more than five years, that battery is flat. A dead NVRAM battery means lost VME configuration, lost Ethernet MAC address, and a boot failure. Test it with a Fluke 115 before you install it. If the voltage is below 2.8V, replace the RTC/NVRAM chip — it’s socketed, so it’s a five-minute job.

 

Installation & Configuration Guide

1. Pre-Installation ⚠️
   • Power down the VME crate and wait 30 seconds for residual charge to dissipate.
   • Strap on your ESD wristband and clip it to a verified ground point.
   • Photograph the old board’s jumper settings — specifically the VME address modifier jumpers and any PMC configuration headers. This prevents 90% of “board won’t boot” issues.
2. Removal
   • Label every cable connected to the front panel (Ethernet, serial, any PMC mezzanine cables).
   • Unscrew the two handle retention screws at the top and bottom of the board.
   • Simultaneously squeeze the ejector levers on both handles — the board will release from the backplane connectors. Slide it straight out.
3. Installation
   • Set the jumpers on the new MVME6100 to match the old board’s configuration. Double-check. Then double-check again.
   • Align the board’s top and bottom edges with the crate’s guide rails. Slide it in firmly until you feel the backplane connectors seat — you’ll hear a distinct click.
   • Close the ejector levers and tighten the retention screws. Don’t overtighten — the threads strip easily.
4. Power-On & Testing
   • Apply power to the VME crate. Watch the front-panel LEDs: PWR should be solid green, FAIL should be off.
   • Connect a serial terminal to the front-panel COM1 port (9600 baud, 8N1). You should see the MOTLoad bootloader prompt within 10 seconds.
   • At the MOTLoad prompt, run show vme to verify the VME address and interrupt settings match your system map.
   • Download your application image (VxWorks or Linux) and verify it boots. Run testRamQuick to confirm memory integrity before putting the board into production.

Compatible Replacement Models

• ✅ Drop-in Replacement: MVME6100-0161, MVME6100-0163, MVME6100-0171, MVME6100-0173 — All share the same MPC7457 processor and VME interface. The -0161/-0163 have 512MB RAM; the -0171/-0173 have 1GB RAM. The -0161/-0171 use Scanbe handles; the -0163/-0173 use IEEE handles. No firmware or wiring changes needed.
• ⚠️ Software Compatible: MVME5100 series — Same VME form factor but uses a different processor architecture (MPC7448). Requires VxWorks BSP recompilation and potential application code changes. Budget 4-8 hours for software migration.
• ❌ Hardware Mod Required: MVME7100 series — Different form factor and VME generation. Requires a new VME crate and full system redesign. Only consider this if you’re doing a complete platform refresh.

 

Frequently Asked Questions (FAQ)

Can I hot-swap the MVME6100 in a running VME crate?
No. The MVME6100 does not support hot-swap. You must power down the crate before removing or inserting the board. Attempting a hot-swap will likely damage the backplane connectors and could fry the board’s VME interface ASIC.Will my existing VxWorks application run on this board without changes?
If you’re coming from an older MVME series (MVME1600, MVME2600, MVME3100), you’ll need to recompile your application with the MVME6100 BSP. The PowerPC architecture is the same, but the memory map, interrupt controller, and VME bridge chip are different. Budget a day for the BSP migration and regression testing.How do I know if the NVRAM battery is still good?
At the MOTLoad prompt, type show nvram. If the date/time is wrong or the command returns garbage data, the battery is dead. You can also measure the voltage across the MK48T37 pins with a multimeter — anything below 2.8V means it’s time for a replacement.What’s the difference between the -0161 and -0163 suffixes?
Nothing functional. The -0161 comes with Scanbe-style ejector handles; the -0163 comes with IEEE-style handles. Pick whichever matches your crate’s handle style for a cleaner fit. RAM and flash are identical (512MB DDR, 128MB flash).Can I use this board with a standard VME backplane, or do I need a special 2eSST backplane?
It works on any standard VME64x backplane. The Tundra Tsi148 chip handles backward compatibility automatically. You won’t get the full 320 MB/s 2eSST bandwidth on an older backplane, but the board will operate correctly at the lower 2eVME or 2eSST speeds that the backplane supports.Is the MOTLoad firmware upgradable?
Yes. Emerson provides MOTLoad firmware updates through their support portal. You’ll need a serial connection and a TFTP server to flash the new image. Always back up your current VME configuration and NVRAM contents before flashing. A failed firmware update will leave the board unbootable until you recover it via the BDM debug header.