Ready to download this white paper?

First Name
Last Name
Job Title
Phone Number
You may receive a request for your feedback from OpenSystems Media. Read our new Privacy Policy to understand what data we collect, why we collect it, and what we do with it.
Europe OptIn
Your download is ready!
Error - something went wrong!

Xeon-D Vs Xeon-E for embedded radar applications

September 13, 2017

For airborne radars, longer, higher and further means more processing power in smaller, rugged efficient packages. The best implementations of ANSI/VITA 65 (OpenVPX), the de facto embedded military open system compute architecture meets the ruggedness and compact requirements, and adds scalability. Especially when implemented as VPX-REDI (VITA 48) even greater ruggedness and increased functional density is possible, as is the ease of two-level maintenance (2LM). Processing power is achieved by leveraging the best commercial Intel Xeon data-center compute capability. Xeon processors are available as either “mobile” devices (Xeon D) which are designed for laptop applications which require lower power, less cores, lower memory bandwidth and less connectivity. Xeon E processors power data-centers and cloud facilities worldwide. Such processors typically have larger core counts, faster memory and increased connectivity such as QPI enabling efficient use of multiple on-board processor and SMP.

Embedding Xeon E devices in to military applications requires rugged packaging, reliable/efficient cooling, fast and unrestricted pipes and banks of memory. Mercury’s proven (fourth generation) OpenVPX Xeon E powered blades have these enabling technologies and are known as the Ensemble® HDS (High Density Server) series of blades., How do these embedded blades with data-center performance usher in the next generation of radar systems? In the past Space Time Adaptive Processing (STAP) was a challenge for embedded systems. This white paper studies STAP processing approaches, using Xeon D and E processors for comparison.

Previous White Paper
A Low-risk, COTS Approach to Building Safety Certifiable Processing Subsystems
A Low-risk, COTS Approach to Building Safety Certifiable Processing Subsystems

How to affordably decrease safety critical processing subsystem development time and program risk using DO-...

Next White Paper
DO-178C: Get on a High with your Software Development
DO-178C: Get on a High with your Software Development

This technical briefing is an introduction to both the DO-178C standard, and the way in which automated too...