-
Notifications
You must be signed in to change notification settings - Fork 1
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
Tap verilog #13
Tap verilog #13
Conversation
…tagdriver and test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, looks good, thanks! Minor comment on adding fault to requirements.txt, is that necessary? It's already in the setup.py
, so installation should be managed there.
requirements.txt
Outdated
@@ -5,3 +5,4 @@ git+git://github.com/phanrahan/mantle.git#egg=mantle | |||
git+git://github.com/phanrahan/loam.git#egg=loam | |||
coreir | |||
git+git://github.com/leonardt/veriloggen.git#egg=veriloggen | |||
git+git://github.com/leonardt/fault.git#egg=fault |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this required? fault
installation should be handled in setup.py
@leonardt, I reverted the requirements.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks! At some point I may run this file through a processor to make it 4 space tabs. Not a blocking issue, but to keep the codebase consistent, it's nice to have every file follow the same style. (I know I'm an offender of inserting 4 space tabs in the 2 space tabs code base of coreir). But I'll defer the formatting to a tool which should make it easy to change (mainly just want to avoid merge conflicts from whitespace changes).
It's been done, probably a good idea to get those changes ASAP if you plan to modify the file. |
This PR contains TAP verilog along with a test which uses fault to test the verilog using a custom JTAG "driver"
Next step is to write a silica implementation of the tap fsm.