Embedded systems rely on a close, integrated relationship between software and hardware. However, in a traditional embedded systems design cycle, hardware and software are often developed separately, then integrated after the hardware has been built. Not surprisingly, often the hardware and software do not work correctly together the first time. In many cases the real software and integration debugging begins only after the hardware has been built. Hardware/software co-verification is one of the techniques that can be used to begin the debugging process sooner, before physical prototypes are available. This paper will explain what hardware/software co-verification is and how it works. It will also cover what software and hardware are appropriate for this type of verification and what should be avoided. We will also give some “real world” examples of what designers have done with co-verification.
Please disable any pop-up blockers for proper viewing of this Whitepaper.