Shabtay’s take 04/28 - Issues resolved. Addressed by spec and only requires spec review.

Committee comment: Agreed. Need to review. Annotate IM with name/title of section altered.

Time

a) How is advancement of time tracked on the hardware side for DPI-only applications?

b) SceMiClockPort in DPI-only applications.

c) Clarify how cycle stamp handling is done in SCE-MI 2

d) Clarify how separation of external clock specifications from internals of transactor models leads to portability to DPI compliant simulators

Should provide a behavioral model that mimics the Clock and reset macro for simulation.

No way across the interface to provide time. In 2.0, there is no natural way. Can get end time but not begin time of a transaction.

Cycle stamp is basically a count of the fastest clock. Need a current time accessor for 2.0. - Time of last received message

Define a cycle Stamp Port. Russ wants this to be implicit. Could either be provided for 2.1 or done as a library macro. Shabtay to look at a definition on top of 1.1

Could add a port to the clock macro to do this.

New models can always accept clocks from a 1.1 clock port.