Project with common errors of the designers

[dmitriym]

Hello All!

I'm sorry, if my request is a little bit weird: I'm looking for some
verilog design with COMMON DESIGNER ERRORS (that are detectable by
modern LINTing tools). Actually, I'm doing research in this field, and
my target is to collect interesting errors in some kind of guide or
demo-project.

Maybe, someone from experiensed designers has been confronted with such
problem - I will be very much apperciated for any help!

 

[Ajeetha]

Hi,
I don't believe such a list exists ready some where, mainly b'cos as
soon as we find an "error" we tend to fix it. One thought will be to
walk through archives of this group and groups such as ASICDESIGN
(Yahoogroups.com) etc. where mainly students and freshers participate,
I've seen several newbie code posts that might fit your need.

On a different note, if you are looking for a commercial EDA product to
be built and require a test suite to meet this need, my compant can
help you, please write to ajeetha <> gmail.com if interested.


Good Luck
Ajeetha, CVC
www.noveldv.com

dmitriym wrote:

Hello All!

I'm sorry, if my request is a little bit weird: I'm looking for some
verilog design with COMMON DESIGNER ERRORS (that are detectable by
modern LINTing tools). Actually, I'm doing research in this field, and
my target is to collect interesting errors in some kind of guide or
demo-project.

Maybe, someone from experiensed designers has been confronted with such
problem - I will be very much apperciated for any help!

 

[dmitriym]

Hi, Ajeetha!

I'm thakful for your response! I'll try to find some interesting things
through archives and I'll search through yahoogroops.com (I had no idea
about it before).

As I understood from the second part of your post (and from your site),
your company deals with solutions for ASICs verification. Thanks, but
I'm looking only for some project. Actually, it can be some kind of
demo from well-known linters (its a pity, but I haven't access to any
of them). IOW, I need any project with common errors of the designers
to analyze it and make some kind of tutorial "how code should not be
written".

Maybe, the best idea will be to take some commercial project (or
project from the opencores) and manually introduce errors in it? But
its quite complex to do - as you have said, errors are commonly
fixed if they are found

With Best Wishes,
Dmitry Melnik

Ajeetha wrote:

Hi,
I don't believe such a list exists ready some where, mainly b'cos as
soon as we find an "error" we tend to fix it. One thought will be to
walk through archives of this group and groups such as ASICDESIGN
(Yahoogroups.com) etc. where mainly students and freshers participate,
I've seen several newbie code posts that might fit your need.

On a different note, if you are looking for a commercial EDA product to
be built and require a test suite to meet this need, my compant can
help you, please write to ajeetha <> gmail.com if interested.


Good Luck
Ajeetha, CVC
www.noveldv.com

dmitriym wrote:
Hello All!

I'm sorry, if my request is a little bit weird: I'm looking for some
verilog design with COMMON DESIGNER ERRORS (that are detectable by
modern LINTing tools). Actually, I'm doing research in this field, and
my target is to collect interesting errors in some kind of guide or
demo-project.

Maybe, someone from experiensed designers has been confronted with such
problem - I will be very much apperciated for any help!

 

dmitriym wrote:

Hi, Ajeetha!

I'm thakful for your response! I'll try to find some interesting things
through archives and I'll search through yahoogroops.com (I had no idea
about it before).

As I understood from the second part of your post (and from your site),
your company deals with solutions for ASICs verification. Thanks, but
I'm looking only for some project. Actually, it can be some kind of
demo from well-known linters (its a pity, but I haven't access to any
of them). IOW, I need any project with common errors of the designers
to analyze it and make some kind of tutorial "how code should not be
written".

Maybe, the best idea will be to take some commercial project (or
project from the opencores) and manually introduce errors in it? But
its quite complex to do - as you have said, errors are commonly
fixed if they are found

....

If you are looking for a taxonomy of bug types and bug/error
descriptions then there are several sources:

Books such as

Principles of Verifiable RTL Design ..., L. Bening etal
REUSE METHODOLOGY MANUAL ..., M. Keating etal

provide guidelines on how to or how not to write code (among other
topics).

Perhaps you could build your tutorial around errors highlighted in
these books.

The book COMPREHENSIVE FUNCTIONAL VERIFICATION: THE COMPLETE INDUSTRY
CYCLE, Wile etal has some case studies of test escapes.

You might also search for papers on Verification Methodology used in
microprocessor or big system projects like Alpha, Power PC, etc. These
papers often contain a bug taxonomy that categorizes bugs found in the
verification.

 

[dmitriym]

Hi, ditsdad,

Thanks a lot! I'll try to find these books and maybe order them, if
they are good and not avaliable online.

Very good idea about looking through the papers with bugs taxonomy!!!
I'll chek any I could find - its should be rich field for research!

Regards,
Dmitry Melnik

ditsdad@gmail.com wrote:

dmitriym wrote:
Hi, Ajeetha!

I'm thakful for your response! I'll try to find some interesting things
through archives and I'll search through yahoogroops.com (I had no idea
about it before).

As I understood from the second part of your post (and from your site),
your company deals with solutions for ASICs verification. Thanks, but
I'm looking only for some project. Actually, it can be some kind of
demo from well-known linters (its a pity, but I haven't access to any
of them). IOW, I need any project with common errors of the designers
to analyze it and make some kind of tutorial "how code should not be
written".

Maybe, the best idea will be to take some commercial project (or
project from the opencores) and manually introduce errors in it? But
its quite complex to do - as you have said, errors are commonly
fixed if they are found

...

If you are looking for a taxonomy of bug types and bug/error
descriptions then there are several sources:

Books such as

Principles of Verifiable RTL Design ..., L. Bening etal
REUSE METHODOLOGY MANUAL ..., M. Keating etal

provide guidelines on how to or how not to write code (among other
topics).

Perhaps you could build your tutorial around errors highlighted in
these books.

The book COMPREHENSIVE FUNCTIONAL VERIFICATION: THE COMPLETE INDUSTRY
CYCLE, Wile etal has some case studies of test escapes.

You might also search for papers on Verification Methodology used in
microprocessor or big system projects like Alpha, Power PC, etc. These
papers often contain a bug taxonomy that categorizes bugs found in the
verification.