Posts Tagged ‘systems’

Hardware-Software Integration

Wednesday, May 5th, 2010

This online cross-discipline graduate course will teach hardware engineers the basics of software design and software developers the basics of hardware design. In this way, each discipline will be able to understand the design of the complete system, following the practices established by high- level systems engineering. Factors that affect the selection of hardware and software solutions in design will be examined, as well as the use of trade studies to optimize the efficiency of integration issues. Techniques for partitioning of system-level functions and requirements to hardware/software components will be provided, as will practical guidance, through case studies, process templates and design check-lists. Prerequisite: Basic understanding of hardware or software development. For more details, see Syllabus and a presentation given by the instructor at Embedded Systems Conference.

June 21 to August 29, 2010  
For more information, visit the PSU website

Follow The Money (And Lose The ‘E’ In EDA)

Thursday, January 8th, 2009

Independent investor Jim Hogan talks about where the real value is and what companies need to do to survive in a changing market.

YouTube Preview Image

COTS Issues

Thursday, December 11th, 2008
YouTube Preview Image

What can go wrong when you use commercial off-the-shelf parts in military applications? We asked Daren McClearnon, an ESL specialst at Agilent.

Better Ways to Connect IP

Thursday, November 20th, 2008

By Ed Sperling

Re-usable intellectual property may sound great on paper, but actually getting pieces to be as interchangeable as Lego parts and automatically configuring them to work in a system on a chip requires more than technology. It requires a leap of faith on the part of chip engineers, and that doesn’t happen overnight.

The first step toward providing the tools was creation of the IP-XACT standard. The most recent iteration, version 1.4, was issued earlier this year. A follow-on to that standard, IP-XACT 1.5, should be finalized by late 2009 or early 2010, sources say.

IP-XACT was developed concurrently with the TLM 2.0 standard, which raises the abstraction level for system-level design. Both standards work almost like middleware, or the proverbial black-box, where you learn to use the tools rather than trying to understand all the steps in the underlying technology. The goal is to automate some of the connections that are repeated by engineers, but it also requires moving up a level of abstraction and putting faith in the companies providing the IP and the tools to make it work.

SPIRIT, the organization that is developing IP-XACT, worked in conjunction with the Open SystemC Initiative (OSCI), which developed TLM 2.0. Both were released early this year.

“TLM modeling was a key addition at multiple levels,” said Gary Delp, an LSI distinguished engineer and one of the key players in developing IP-XACT. “You can mix IP in transaction-level modeling with the RTL level. You can take named and referenced bus definitions and span abstraction levels.”

Delp said that in system-level design, automating parts of the design and specifying interfaces is critical. “Once you have standardized interfaces for re-use, it will get simpler. We are working with a team that is doing tool validation in India using IP-XACT. They found it produces such good designs that they’re requiring everyone to use it, including their customers.”

Most of the member groups that created the standard agree. John Swanson, Synopsys’ product marketing manager for Ethernet, Mobile Storage & IP Reuse Tools, calls 1.4 “a good, solid release.”

“IP-XACT 1.4 added basics for registers,” Swanson said. “When the design gets to the software debuggers you need another level of information. We’re working on the extensions now.”

Those extensions will become part of version 1.5, which will include support for automated documentation and extend the register description capability as well as implement register designs.

What it doesn’t do, however, is bridge the design worlds between hardware and software in electronic system-level design, said Johannes Stahl, VP of marketing and business development for design tools at CoWare. “Retooling of the IP model itself is way more important,” he said. “For us, SPIRIT’s usefulness is still several years out because productivity comes more from integrated environments than anything else.”

Stahl said the biggest problem in IP today isn’t interoperability and automating connections. He said the real issue is understanding how the IP blocks interact.

SOI Goes Mainstream

Thursday, November 20th, 2008

By Ed Sperling

The crossover for system on insulator (SOI) versus bulk CMOS was supposed to happen at the 22nm, but that was before software developers ran into problems programming multicore chips.

For years, SOI was considered the high-performance cousin of CMOS—more expensive, more difficult to manufacture and unnecessary for most applications. It is the heart of the Cell processor, for example, which drives Sony’s Playstation 3, the latest versions of digital televisions and some network appliances that need the benefits of always-on active power.

But with the persistent problems of writing general-purpose applications that can scale with multicore processors, SOI is quietly gaining more mainstream appeal. By running either faster or cooler—or both—it can provide the performance gains that multicore chips would provide if the software could take advantage of all the cores.

“SOI does offer a way out,” says Horacio Mendez, executive director of the SOI Consortium. “The big issue is the scalability of bulk CMOS, and there are significant challenges there. When you shrink the transistors, they’re not stable. And with stability comes a power consumption problem.”

The instability is caused in large part by voltage threshold variations. As companies continue down the Moore’s Law road map, short-channel effects (see Fig. 1 below), an increase in parasitic leakage as a result of scaling gate-length dimension and gate oxide leakage all contribute to power dissipation. SOI chips use up to 40% less power due to lower parasitic capacitance, and because they can use higher current they operate at lower voltages.

In practical terms, that means SOI chips can at least keep the number of cores constant and still add performance at each process node. And because they run cooler, they also can use less expensive packages—something that affects when they become economically feasible to use in lower-performance applications.

Fig. 1: SOI VS. Bulk-Stability Comparison

Much of the transistor instability is caused by Vth variation, causing higher leakage, increased power. SOI shows more stability.

Short Channel Effects — Source: IBM

Given the advantages, it should come as no surprise that IBM has opened its SOI fab to commercial business at 45nm. Mark Ireland, IBM’s vice president of semiconductor platforms, said SOI is expected to be adopted by the Common Platform group—IBM, Samsung and Chartered Semiconductor—at 32nm.

“What we’re doing now is creating an industry ecosystem,” Ireland said. “From a design standpoint, this is more about education of engineers. At IBM we moved our entire ASIC business to SOI at 45nm. A lot of the hesitation is just about the unknown. But it’s the same design tools and ARM physical IP.”

Opening SOI technology to a broader market also should drop the cost even further, bringing it much closer to parity even at 45nm. But the biggest advantage is still on the software side. While many applications can be threaded to deal with between two and eight cores, far fewer will gain from the addition of more cores. On top of that, very few applications are scalable so they can be written once and recompiled for as many cores as become available.

“Customers already are coming to us looking for higher single-threaded performance,” Ireland said. “Clearly, that legacy market is not going away. Applications will not change overnight. And you do get a performance gain every time you move to the next node, so at 32nm vs. 45nm, there is a performance gain.”

Intel developed a similar technology called TerraHertz in 2000, but so far has done nothing with it commercially. It is one of several possibilities that Intel can tap into at future process nodes, along with its Tri-gate technology. Likewise, IBM has been developing its own tool bag of options, which includes everything from FinFETS to AirGap insulation between structures on a chip.

All of these technologies can be manufactured using existing equipment, and likely will have a significant role in future system development

Cognitive Radio

Wednesday, November 19th, 2008
YouTube Preview Image

The Trouble With Serial Design

Thursday, November 13th, 2008
YouTube Preview Image

John Isaac, director of system market development at Mentor Graphics, talks about problems at the board level.

Systems Engineering Management

Tuesday, November 11th, 2008

This online graduate course covers the essentials of systems engineering management and its critical interconnection to program/project management. Systems engineering is the integration of several engineering fields into an efficient and effective process for the overall technical management of programs and development of systems and products. Students will gain detailed knowledge in management techniques applicable to activities within Systems Engineering, including evaluating new technology, integrating legacy systems, trade-off studies, technical performance measurement, cost-effective process tailoring, technical reviews and audits, and others. Several case studies projects will be studied throughout the course to illustrate key concepts and management techniques

Professor: John Blyler

Class Begins: September 28, 2009

Class Ends:  December 6, 2009

YouTube Preview Image