# Coverpoint array

**URL:** <https://verificationacademy.com/forums/t/coverpoint-array/33761>\
**Category:** SystemVerilog\
**Tags:** SystemVerilog, SystemVerilog-FunctionalCoverage\
**Created:** [November 29, 2017, 2:36am UTC](https://verificationacademy.com/forums/t/coverpoint-array/33761 "2017-11-29T02:36:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![birdluo](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/b/8c91f0/32.png) [@birdluo](https://verificationacademy.com/forums/u/birdluo)\
**Post date:** [November 29, 2017, 8:54am UTC](https://verificationacademy.com/forums/t/coverpoint-array/33761/5 "2017-11-29T08:54:09Z")

</div>

_In reply to [dave\_59](https://verificationacademy.com/forums/t/coverpoint-array/33761/4):_

|\<-------------sequence0-----------\> |\<-------------sequence1-----------\>

* * *

| frame0 | frame1 | … |framen | | frame0 | frame1 | … |framen |

* * *

framecount is number of frame in a sequence.

example:  
for sequence0  
framecount[0] :2  
FARME[0]:  
length 32  
cetype 3;  
FARME[1]:  
length 32  
cetype 2;

for sequence1  
framecount[1] :3

FARME[0]:  
length 32  
cetype 2;  
FARME[1]:  
length 32  
cetype 3;  
FARME[2]:  
length 32  
cetype 3;

In verification, the sequence0 find the bug, because the difference order of cetype cause the different resulut.

cetype order:  
sequence0:  
cetype :3  
cetype :2

sequence1:  
cetype :2  
cetype :3  
…

The bug exists in the sequence0.

there are some ideas:  
1.whether there are the other cetype order that hit bug.  
2.when regress finish, coveragegoup tell me what the hole is. based on it , I will add cases or modify the test method.

for these problem, are there any proposal?

---

_[View the full topic](https://verificationacademy.com/forums/t/coverpoint-array/33761)._
