The goal is the ability to generate derivatives of a basic design with quick feature upgrades without modifying the basic topology. These let designers start embedded software development and integrate hardware and software before they gain access to the physical prototype. Typically, embedded software development and debugging starts after hardware development. With a virtual platform, hardware-software integration can occur earlier. Therefore, not only are those bugs found and resolved, but the designer can also discover and resolve issues related to communications between the hardware and software, the timing of this communication, and the servicing of interrupts.
Most applications using platforms are in the telecom, wireless, and consumer multimedia domains.
These domains also benefit from the critical mass of existing standards, such as Bluetooth and W-CDMA, that can be implemented as platform libraries and then reused throughout a large variety of designs. Other mainstream applications are systems with a raft of potential features or applications for disparate markets. Other potential uses include communications and Internet appliances. After you have analyzed your needs and determined that a platform-based approach to SoC design is right for you and your team, you must confront certain issues and answer some questions before comfortably taking the plunge. Right up front is the added cost of switching to a new methodology.