Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

Unresovled BlackBox issues #67

Open
chick opened this issue Nov 29, 2018 · 0 comments
Open

Unresovled BlackBox issues #67

chick opened this issue Nov 29, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@chick
Copy link
Collaborator

chick commented Nov 29, 2018

  • There is no way for a developer to know what parameterized changes took place between chisel and firrtl
  • The IO's may have be different, treadle can pass in seq of io information on size, dir and type
  • internal changes could only be forwarded via some kind of annotation, analysis needed here
  • The getOutput method should be changed to eliminate the input fields
    • That information should now be handled exclusively vi the input change handing method
  • Black boxes should be allowed to allocated storage in the datastore
    • This would allow snapshotting to capture black box state
  • Black boxes should be allowed to interact with vcd log (when present)
  • There should be some mechanism for deep internal access to treadle engine
    • vcd access might be built on top of this.
@chick chick self-assigned this Nov 29, 2018
@chick chick added the enhancement New feature or request label Nov 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant