Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Bad habit in Verilog HDL

Status
Not open for further replies.

cafukarfoo

Full Member level 3
Joined
Jul 25, 2007
Messages
170
Helped
8
Reputation
16
Reaction score
5
Trophy points
1,298
Activity points
2,510
Hello All,

Can you guys share some of the bad habit when we code in Verilog HDL in order to avoid bad timing during synthesis?

Thanks.
 

One general tip is to use a linting tool to catch bad styles, poor constructs and other mistakes.
 

What is linting tool mean? Any example?
 


    cafukarfoo

    Points: 2
    Helpful Answer Positive Rating
Link is good -

csg.csail.mit.edu/6.375/papers/cummings-nonblocking-snug99.pdf
eesun.free.fr/DOC/VERILOG/synvlg.html
 

    cafukarfoo

    Points: 2
    Helpful Answer Positive Rating
this morning i face some hard-to-read verilog... i think it's bad habbits.... just MHO

doing muxing in modelling... the modelling guy do this...

assign out = sel1 ? (sel2 ? b1 : (sel3 ? (sel4 ? d1 : (sel5 ? e1 : e2)) : c2) ) : a2

arghhh... when i try to visualize and debug the design... it really make me crazy....

:D really....
 

Messing up with reg and wire in the declaration is a huge head ache...
 

SpyGlass is one of the best tool to catch bad verilog/vhdl coding styles.

It runs pretty fast compared to traditional implementation tools.

Regards,
Narayana
 

the linting tools:synopsys leda and novas Nlint
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top