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

Cocotb Integration #1567

Closed
veripoolbot opened this issue Oct 17, 2019 · 2 comments
Closed

Cocotb Integration #1567

veripoolbot opened this issue Oct 17, 2019 · 2 comments
Labels
area: invoking/options Issue involves options passed to Verilator area: usability Issue involves general usability effort: weeks Expect this issue to require weeks or more of invested effort to resolve type: feature-non-IEEE Request to add new feature, outside IEEE 1800

Comments

@veripoolbot
Copy link
Contributor


Author Name: Wilson Snyder (@wsnyder)
Original Redmine Issue: 1567 from https://www.veripool.org


Tracking issue for integrating Verilator with Cocotb - which is currently under development.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Stefan Wallentowitz (@wallento)
Original Date: 2019-12-13T15:50:57Z


Nearly there, #1636 is the last one we need for the basic examples. The merge progress can be tracked here: cocotb/cocotb#943

@veripoolbot veripoolbot added area: invoking/options Issue involves options passed to Verilator area: usability Issue involves general usability effort: weeks Expect this issue to require weeks or more of invested effort to resolve type: feature-non-IEEE Request to add new feature, outside IEEE 1800 labels Dec 22, 2019
@wallento
Copy link
Member

Basic support is done as per cocotb/cocotb#943 (for cocotb 1.3)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: invoking/options Issue involves options passed to Verilator area: usability Issue involves general usability effort: weeks Expect this issue to require weeks or more of invested effort to resolve type: feature-non-IEEE Request to add new feature, outside IEEE 1800
Projects
None yet
Development

No branches or pull requests

2 participants