| Anonymous | Login | 2010-09-07 11:24 PDT |
| Main | My View | View Issues | Docs | Wiki |
| Viewing Issue Simple Details [ Jump to Notes ] [ Wiki ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Date Submitted | Last Update | |||
| 0001710 | [SystemVerilog P1800] V-1364 | minor | 2007-01-06 23:12 | 2008-06-22 23:08 | |||
| Reporter | shalom | View Status | public | ||||
| Assigned To | shalom | ||||||
| Priority | immediate | Resolution | fixed | ||||
| Status | closed | Product Version | |||||
| Summary | 0001710: 15.3.5: $period error | ||||||
| Description |
Following up on 0001708, I saw that Table 15-11 in 1364-2005 defines the $period arguments as Table 15-11 $period arguments Argument Description reference_event Timestamp edge triggered event (data_event - implicit) Timestamp edge triggered event limit Non-negative constant expression notifier (optional) Reg whereas the violation criterion is defined as "The $period timing check reports a violation in the following case: (timecheck time) - (timestamp time) < limit" while "timecheck time" is not defined. I think that in the argument list, the implicit argument data_event should have been defined as the timecheck event. Also, this section does not clearly define what $period does. That description should be the first thing in this section. As a starting point, the NC manual has the following text: "The $period timing check specifies the duration of signal levels from one edge transition to the same edge transition. A violation occurs when the pulse width is smaller than the specified limit. The following figure illustrates how a violation occurs with the $period timing check." and this is followed by a figure. |
||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Type | Errata | ||||||
| Attached Files |
|
||||||
|
|
|||||||
Relationships |
||||||
|
||||||
| Mantis 1.1.7[^] Copyright © 2000 - 2008 Mantis Group |