Welcome to our site! EDAboard.com is an international Electronic 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.
Well, this is a too big topic. Debugging is inevitable. But several guideline to keep RTL code consistent with netlist is that:
1. Never leave out any signal in sensitivity list in combinational block.
2. Separate combinational block from sequential block;
3. never compare any signal with 'x' or 'z';
4. Be careful about blocking and non-blocking assignment.
During debug, set some monitor signals. It will always help.
For test benches - any style will do - as long as other team members can understand it. Try to use as many notes & symbols (for variables names) as you can.
For synthesys - try to follow Synopsys HDL (Verilog) User Guide.
nLint from Novas (or Debussy) will check your code for Style (and many other pitfalls) - way before actual Synthesis - thus you will save youself a lot of design/re-design efforts/time.
If you are writing FPGA design, don't even dream about vendor-independent HDL.
You'll be digging your own grave. Actually, there is no good reason to write such HDL.
Nobody is changing FPGA vendor in the middle of project. As for ASIC prototyping, some
parts of ASIC won't be synthesised from HDL
anyway, but taken from a library (memory etc).
Vendor-independent HDL is a mistake usually made by people who come from ASIC.