-
Notifications
You must be signed in to change notification settings - Fork 2
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
added JTAG busDef #16
Conversation
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.
much needed
Francois also needs to be aware so that it could be netbundle in ICC
@drom can you explain the purpose of defining a JTAG bus in DUH? That would help me provide useful feedback. |
@drom if your purpose is to define all the possible DFT connections in a design you would also need IEEE 1687 and IEEE 1500 buses. I can define them for you if you want. |
@drom in case your purpose is to the DFT connections in a design you need to add the two buses below: The IEEE 1500 Embedded Core Test signals:
The IEEE 1687 IJTAG signals:
|
Added separate issue: #18 |
Added separate issue: #19 |
While onboarding or developing IP blocks, we should be able to map ports as "bus interfaces" of a specific type. For this purpose, we have to create "bus definition" (like a type signature) that would provide a set of rules/constraints associated with this interface type. Later when composing SoC out of specific IP clocks we can automate the discovery of specific interfaces, creation, and validation of appropriate infrastructure. |
Here is a proposed JTAG bus Definition document.
I am looking for feedback on what additional signals related to JTAG should be included?
Related to #15