To: "'Tony Taylor'" Subject: RE: STIL.3 - Review of Draft 06 of STIL-TRC standard Hi Tony, I read the .3 proposal and my comments are below. Generally things look pretty good. My main comments are probably more of a question (or misunderstanding). The rest are just the typos I noticed. Hope this helps, Bruce ============================================================ COMMENTS: Page 16, first para (ED. Opinion) Remove "Please" from "Please compare and contrast this to the usage of the labels which accomplish ...." Page 21 Section 13.1: (COMMENT) On MaxVectorMemory: How would the constraints document handle a tester that configures memory differently depending on how the test is run? For example, if I ran a test and told the tester to save (return) all the mismatch data, the tester may need to reserve a lot of memory for the mis match data. Then, if I ran the same test but told the tester to just tell me whether it passed or failed (ie the tester does not need to save mis match info), tester could use more memory for vectors (assuming the same memory is used for vector data and mismatch data). How can this be specified using the constraints? Page 23 Section 10.1 (Nit) Change "Pragma TARGET_NAME {* ... ANY OLD SYNTAX ... *} to "Pragma TARGET_NAME {* ... Tester Interpreted Code ... *} Page 24 First Para: (Typo) In STIL.1, Clause 18, there is..." should be "In STIL.1, Clause 19.1, there is...." Page 26 (Typo) Remove extra "the" from (6) PeriodCharacteristics PER_CHAR_NAME: The PeriodCharacteristics block is optional and contains information relative the the period capabilities Page 26 Para beginning wih 11 (Typo) Waveform is mispelled in the para. Page 28 Para beginning with 3) (Typo) switching in "...this statement specifies when the in/out swithing may occur..." Page 39 2nd para (Typo) default in "...By deafult, only wfc data is..." Page 20 Section 20 (Comment/question) Maybe I didn't spend enough time with this but I don't see how a particular Stil program would reference the Category "SIZE_512" (for example). And it seems to me that this spec offers several ways to do the same thing. For example, couldn't I just set up two SignalCharacteristic blocks that define max pins instead of using Spec block? Page 44 2nd para in 20 (Typo)defined in "...These should be devined as Spec-...." Page 44 2nd para in 20 (Typo) names and -> "The definition of category namesand variable..." Page 44 Section 20.1 (Typo) increments in "...assigned to the segments in incriements of 64...."