Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Embedded Systems

Comment: Software Development Environments -- Quo Vadis?


First, to assess different options, these design teams require fast simulation, crossing hardware/software boundaries and exceeding today's capabilities. Today, software on an instruction set simulator (ISS) for single processors can be simulated at multiple MIPS. Those capabilities are not scaling appropriately when using 10, 20 or even 50 processors and trying to meet the requirement of running a significant portion of the application (think 30 seconds of video and audio in a multimedia application).

Second, today's embedded debug solutions are built for single processors, not taking into account requirements of debugging parallelism in an application distributed to 10, 20 or 50 processors.

Lastly, today's compilers are targeted to single processors only. Problems of expressing parallelism in application programming, then mapping and distributing software on a MPSoC platform, remain largely unaddressed.

Who is up for the challenge? Will it be driven by the software side or the hardware side? Who can afford the investment? Who is willing to pay the price?

While hardware designers are used to paying a price for fast simulation and debug, software designers are used to free or almost free tools in the age of GCC and GDB. This trend is exacerbated by the expectation of software developers to get a software development environment presented with the silicon they are programming. Vertically integrated semiconductor houses such as Texas Instruments and Philips understand this and have hired more software developers recently than hardware developers to support and differentiate their silicon.

The bottom line for requirements and trends suggest that the new system design automation paradigm can only be addressed in close cooperation with hardware and software designers. It will have to be funded by the hardware world in which users — software developers — expect to receive as part of the silicon offering a state-of-the-art software development environment supporting the platform. Otherwise, they will switch platforms or remap the application to a new, highly programmable MPSoC specifically taking into account their application requirements.

Providing this new methodology for system design automation is the next great challenge, particularly with the need to cross traditional industry boundaries and attitudes between EDA and embedded software. When a design team can apply functionality across a range of processors, successfully debug and simultaneously validate software and hardware, this new design paradigm will yield significant benefits for all. It will also enable accelerated growth in consumer electronics based on cheaper, faster, more power efficient and reliable chips.

If — and only if — system design automation becomes reality, then the next generation of convergence in consumer devices will be possible. We will be able to think back at and smile while confirming that our PDA has computed directions correctly using the integrated GPS, while phoning our children, all using one device. Quo vadis, indeed.

Simon Davidmann is president and CEO of Imperas Inc. He has been an executive with six U.S. EDA startups and one of the original developers of the HILO logic simulation system.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.