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

added JTAG busDef #16

Merged
merged 2 commits into from
Apr 9, 2020
Merged

added JTAG busDef #16

merged 2 commits into from
Apr 9, 2020

Conversation

drom
Copy link
Member

@drom drom commented Apr 6, 2020

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

Copy link

@Ramlakshmi3733 Ramlakshmi3733 left a 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 drom requested a review from fferhani April 6, 2020 19:28
@drom drom added the newBus new bus definition label Apr 6, 2020
@fferhani
Copy link

fferhani commented Apr 7, 2020

@drom can you explain the purpose of defining a JTAG bus in DUH? That would help me provide useful feedback.

@fferhani
Copy link

fferhani commented Apr 7, 2020

@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.

@fferhani
Copy link

fferhani commented Apr 8, 2020

@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:

  1. WRCK: Wrapper Clock. Provides timing for the core wrapper signaling.
  2. WSI: Wrapper Serial Input. Serial input to the 1500 Wrapper Serial Port (WSP)
  3. WSO: Wrapper Serial Output. Serial output from the 1500 Wrapper Serial Port
  4. WRSTN: Wrapper Reset. Resets the wrapper.
  5. ShiftWR: Wrapper Shift. The Shift Enable signal for the active 1500 Wrapper Scan Path registers.
  6. CaptureWR: Wrapper Capture. The Capture Enable signals for the active 1500 Wrapper Scan Path
    registers.
  7. UpdateWR: Wrapper Update. The Update Enable signal for the active 1500 Wrapper Scan Path registers.
  8. SelectWIR: Select Wrapper Instruction Register. Activates an instruction register as the active Wrapper Scan Path register.

The IEEE 1687 IJTAG signals:

  1. ijtag_tck: clock
  2. ijtag_reset: reset
  3. ijtag_ce: capture
  4. ijtag_se: shift
  5. ijtag_sel: select
  6. ijtag_si: scan data in
  7. ijtag_ue: update

@drom
Copy link
Member Author

drom commented Apr 9, 2020

The IEEE 1500 Embedded Core Test signals:

  1. WRCK: Wrapper Clock. Provides timing for the core wrapper signaling.
  2. WSI: Wrapper Serial Input. Serial input to the 1500 Wrapper Serial Port (WSP)
  3. WSO: Wrapper Serial Output. Serial output from the 1500 Wrapper Serial Port
  4. WRSTN: Wrapper Reset. Resets the wrapper.
  5. ShiftWR: Wrapper Shift. The Shift Enable signal for the active 1500 Wrapper Scan Path registers.
  6. CaptureWR: Wrapper Capture. The Capture Enable signals for the active 1500 Wrapper Scan Path
    registers.
  7. UpdateWR: Wrapper Update. The Update Enable signal for the active 1500 Wrapper Scan Path registers.
  8. SelectWIR: Select Wrapper Instruction Register. Activates an instruction register as the active Wrapper Scan Path register.

Added separate issue: #18

@drom
Copy link
Member Author

drom commented Apr 9, 2020

The IEEE 1687 IJTAG signals:

  1. ijtag_tck: clock
  2. ijtag_reset: reset
  3. ijtag_ce: capture
  4. ijtag_se: shift
  5. ijtag_sel: select
  6. ijtag_si: scan data in
  7. ijtag_ue: update

Added separate issue: #19

@drom
Copy link
Member Author

drom commented Apr 9, 2020

@drom can you explain the purpose of defining a JTAG bus in DUH? That would help me provide useful feedback.

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.

@drom drom merged commit a1daf11 into master Apr 9, 2020
@drom drom deleted the JTAG_bus_def branch April 13, 2020 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
newBus new bus definition
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants