-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
verilog2tex: there should be //IO pragma for interface signals #201
Comments
suggested change example: //START_IO_TABLE axis_in
`IOB_INPUT(audio_in_s_axis_tvalid, 1), //Audio input stream valid signal.
`IOB_INPUT(audio_in_s_axis_tdata, 32), //Audio input stream data signal.
`IOB_OUTPUT(audio_in_s_axis_tready, 1), //Audio input stream ready signal. to: //START_IO_TABLE axis_in
`IOB_INPUT(audio_in_s_axis_tvalid, 1), // V2TEX_IO Audio input stream valid signal.
`IOB_INPUT(audio_in_s_axis_tdata, 32), // V2TEX_IO Audio input stream data signal.
`IOB_OUTPUT(audio_in_s_axis_tready, 1), // V2TEX_IO Audio input stream ready signal. update
|
This will be solved by upgrading axi_gen.py to if_gen.py to be able to handle axi, iob and clk/rst interfaces if_gen.py can later be used by another script that inserts the verilog code into verilog templates instead of generating .vh files that need to be included. |
The intent is to have v2tex work even if |
otherwise, IOs in internal modules will inadvertently appear in the doc
another advantage of having this new pragma is that verilog2tex will work regardless if the user chooses to use the lib IO macros or not
if you decide to implement test in i2s please
The text was updated successfully, but these errors were encountered: