Standard Co-Emulation Modeling Interface (SEC-MI).

                                                 (One prototype for IoT)

   Basics for the Beginners:
     

•         Motivation. 
•         SCE-MI standards and Types.
•         SCE-MI Simulation Flow.

Motivation :

                To avoid communication bottlenecks b/w the SW models to HW emulation platforms

              during SoC verification.

               

Purpose :

              The purpose of the SCE-MI standard is to enable SoC modeling environments to be re-used for HW emulation and rapid prototyping platforms.

              

             Modeling IF provided by the SCE-MI allows mulitple channels of communications between high level SW models to connect to RTL models of a DUT residing in a hardware. 

      Example: Connecting an untimed Test bench (SW) to a timed module residing in an emulator. 

SCE-MI STANDARDS and TYPES:

            Standards here means, just tot synthesis interface by all EDA vendors tools.

There are 3 types SCE-MI interfaces:

1.             Macro based (SCE-MI version 1.0)
2.             Function based (SCE-MI version 2.1,DPI-Adv of SV DPI for user to do own API).
3.             Pipe-based (SEC-MI version 2.1)

Overview of Macro-based SCE-MI environment :

       Overall SCE-MI component:

   

SCE-MI Simulation Flow (ALDEC example)

The Beginning of Next :

 Once we started working on this real time ,we can come up with examples to make you understand further.