Global Sources
EE Times-Asia
Stay in touch with EE Times Asia
EE Times-Asia > Embedded

Examining OS as the hub of hardware emulator

Posted: 24 Apr 2015 ?? ?Print Version ?Bookmark and Share

Keywords:operating system? OS? hardware description language? simulator? emulators?

For more than a decade, I have been following the practice of upgrading my laptop every three years. I do so for more than one reason. After three years of intense use, subjected to the wear and tear of international travel, a laptop gets tired. New generations of hardware run faster, consume less energy, and weigh less. Also, new displays have higher resolutionsan attribute that tops my list of features.

The mandatory criteria for supporting the upgrade is that the suite of application software I have gathered over time must run, no matter what the underlining hardware is. This is made possible by the operating system (OS). It is the OS, with its embedded drivers, that shields the application software from the hardware and assures the compatibility of any new and old software application with any new or old hardware platform.

Hardware emulators are a unique type of special-purpose compute engines that are designed and built to perform one task, albeit with a multitude of anglesdesign verification of digital electronic systems. With a special OS, they verify the functionality of a design without taking into account its timing behavior. They do so at speeds 100,000 to 1,000,000 times faster than any hardware description language (HDL) simulator.

They are versatile in deployment since they can accommodate any test environment one can think of before silicon availability. Test environments range from the real target system to an equivalent virtual target system to any testbench (no matter how complex) to embedded softwareand any combination of the above. Some commercial emulators enable software developers to debug software offline. This is similar to the methodology used by hardware engineers who use waveforms generated by the emulator for offline hardware debug.

They support assertions, monitors, and checkers; they can track functional coverage; and they can perform power analysis and power estimation. They are an ideal vehicle for software bring-up, security checking, hard/soft error recovery, integration/validation of IPs and memories, and can even accomplish performance characterization and system stress.

Compared with earlier generations, today's emulators have advanced in several directions. A case in point is the ability to be shared among several concurrent users, including hardware designers, verification engineers, firmware engineers, and software developers. Combined with remote accessibility, their raw performance and deployment versatility can be made available in any place of the world where there is an SoC design team. Obviously, this plays a significant role in a return-on-investment (ROI) analysis.

Still, emulators are subject to peculiarities inherent to hardware systems. Installing and testing an emulation platform may take days, which is a far cry from the minutes typically needed for a software application. Major upgrades and re-configurations follow the same pattern. Sometimes, a large company may elect to move the emulator to a different site, or maybe even to another continent. This would lead to a downtime of several weeks, if not a month or more.

Unlike software-based verification tools, emulators require maintenance that can be scheduled if preventive, such as system software upgrades, minor hardware replacements, and re-configurations. It would cause unplanned downtime when corrective, such as hardware failures, A/C malfunctions, and an electrical power breakdown.

1???2?Next Page?Last Page

Article Comments - Examining OS as the hub of hardware ...
*? You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.

Back to Top