Skip to content
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

Merged
merged 8 commits into from
Oct 19, 2018
Merged

Tap verilog #13

merged 8 commits into from
Oct 19, 2018

Conversation

rdaly525
Copy link
Collaborator

@rdaly525 rdaly525 commented Oct 18, 2018

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.

@coveralls
Copy link

coveralls commented Oct 18, 2018

Pull Request Test Coverage Report for Build 257

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 72.482%

Totals Coverage Status
Change from base Build 237: 0.0%
Covered Lines: 1425
Relevant Lines: 1966

💛 - Coveralls

Copy link
Owner

@leonardt leonardt left a 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
Copy link
Owner

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

@rdaly525
Copy link
Collaborator Author

@leonardt, I reverted the requirements.txt

Copy link
Owner

@leonardt leonardt left a 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).

@leonardt leonardt merged commit 7dd3514 into master Oct 19, 2018
@leonardt
Copy link
Owner

741a5a2

It's been done, probably a good idea to get those changes ASAP if you plan to modify the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants