When I used to work at Silicon Engineering in the nineties, I wrote a Verilog preprocessor using Perl. Verilog ’95 is pretty limited in what it can do, so we used this preprocessor on our projects to enhance our Verilog code. Back in the Verilog ’95 days, we used to write every RTL file as a preprocessor file and used GNU Make to convert it into pure Verilog. What with Verilog 2005 and System Verilog, these days I only use this preprocessor when necessary. But that’s still pretty often.<\/p>\n
The cool thing about this preprocessor is that it does very little of the work on its own. It can be used in place of the standard Verilog preprocessor\u2013 which is well and good if you need that type of thing, but it’s still pretty limited. After all, you already have something that does that. This preprocessor’s neat trick is that you can embed Perl code inside your Verilog code. What the preprocessor does, essentially, is it converts the input code into a perl program which, when run, prints the input code. Now, by itself that is kind of boring. However the preprocessor allows you to use special comments to drop out of this mode and embed Perl code.<\/p>\n
One simple example of what you can do is to build a table to use in your Verilog module. In my CORDIC module, I needed a table of arctan values. This table is static and doesn’t ever need to change. All I needed was one entry in the table for each pipeline stage in the CORDIC. The table takes the pipeline stage number as input and returns a 64-bit value as the result. I implemented this as a function which is basically just a big case statement. You can see the special comment is wrapped in a \/*@ and @*\/ pair. I chose these because they are real Verilog comments so they won’t mess up editors that know how to edit Verilog (like Emacs). Once you drop into Perl mode, anything that your Perl code writes to standard output will appear in the preprocessor output. Here is the input to the\u00a0preprocessor:<\/p>\n
function [63:0] k_table;\n input [5:0] index;\n begin\n\t case(index)\n\/*@\n $k = 1;\n for my $i (0..63)\n {\n $k *= cos(atan2(1,2**$i));\n printf \"%8d: k_table = 64'd%s; \/\/ %.20e\\n\",$i,int($k*2**64+.5),$k;\n }\n @*\/\n\t default: k_table = 0;\n\t endcase\n end\n endfunction\n<\/code><\/pre>\nInterpolation<\/h2>\n
Code enclosed within the \/*@ and @*\/ pairs, or prefixed with the \/\/@ comment, is just copied into the output Perl program. Other lines are just printed by the Perl program, which means\u00a0you can use Perl string interpolation on those lines. Here’s a rather contrived example:<\/p>\n
\/\/@ my $reset_style = \" or negedge clk\";\nalways @(posedge clk $reset_style)\n q <= d;\n<\/code><\/pre>\nIn this example, the Perl reset_style<\/code> variable is used in the verilog code without needing to drop into the more cumbersome comment syntax. This can help make your code a lot more readable. I have a library that I commonly use which defines a bunch of variables. These variables match the Verilog system tasks and functions that begin with a dollar sign ($). This way, you can say $display<\/code>\u00a0and the preprocessor will expand the Perl variable display<\/code>\u00a0(which, by the way, conveniently has the value $display<\/em>.)<\/p>\nOther Possibilities<\/h2>\n
I also write a lot of structured documentation for my designs using XML. By using the XML::LibXML library I can read the XML documentation from my Verilog code and parse that for information that drives the RTL code generation. So I can document registers, instruction sets, interrupts, or other types of information, and then that do generate my verily code.<\/p>\n
Useful Links<\/h2>\n\n- vpp.pl\u00a0man page<\/a> and perl code<\/a>.<\/li>\n
- Vpp.pm man page<\/a> and perl library<\/a>.<\/li>\n<\/ul>\n
Look for more posts using this technique soon.<\/p>\n","protected":false},"excerpt":{"rendered":"
A long time ago… When I used to work at Silicon Engineering in the nineties, I wrote a Verilog preprocessor using Perl. Verilog ’95 is pretty limited in what it can do, so we used this preprocessor on our projects … Continue reading