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

Caliptra JTAG TdoEn missing output #159

Closed
nstewart-amd opened this issue Feb 9, 2024 · 2 comments · Fixed by #182
Closed

Caliptra JTAG TdoEn missing output #159

nstewart-amd opened this issue Feb 9, 2024 · 2 comments · Fixed by #182

Comments

@nstewart-amd
Copy link

“IEEE1149.1 standard says in chapter 4.5.1 “The TDO driver shall be set to its inactive drive state except when the scanning of data is in progress”. So TdoEn is needed to implement this requirement, detailed in Table 6.2.”

Caliptra RTL currently does not expose TdoEn as a top-level port.
However, TdoEn appears to be implemented in the VEER TAP controller.

File: riscv_core/veer_el2/rtl/dmi/rvjtag_tap.v
assign tdoEnable = shift_dr | shift_ir;

However, this output is left dangling at the VEER wrapper and not pulled to the top of Caliptra.

File: riscv_core/veer_el2/rtl/el2_veer_wrapper.sv
.tdoEnable (),

@algrobman
Copy link

tdoEnable output is meant to tristate real SOC TDO pin. Since debug subsystem is not alone is a SOC, but connected to the SOC JTAG someway, there is no sense to use VEER tdoEnable in the SOC level.

@nstewart-amd
Copy link
Author

We should not assume that VeeR is not alone in the system.
VeeR tdoEnable should be output of VeeR, and system integrators should use it or ignore as appropriate for their systems.

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 a pull request may close this issue.

2 participants