Skip to content
This repository was archived by the owner on Mar 7, 2026. It is now read-only.

Fix: JTAG-TAP cleanup#1293

Merged
esden merged 10 commits into
mainfrom
fix/jtag-tap-cleanup
Nov 18, 2022
Merged

Fix: JTAG-TAP cleanup#1293
esden merged 10 commits into
mainfrom
fix/jtag-tap-cleanup

Conversation

@dragonmux
Copy link
Copy Markdown
Member

Detailed description

In this PR we address some conformity issues with the firmware-side JTAG-TAP code and remove a point of confusion (the jtag_proc_t *jp parameters in the JTAG abstraction layer). This finishes what was started in #1118 and #1131

Your checklist for this pull request

  • I've read the Code of Conduct
  • I've read the guidelines for contributing to this repository
  • It builds for hardware native (make PROBE_HOST=native)
  • It builds as BMDA (make PROBE_HOST=hosted)
  • I've tested it to the best of my ability
  • My commit messages provide a useful short description of what the commits do

Closing issues

@dragonmux dragonmux added this to the v1.9 release milestone Nov 18, 2022
@dragonmux dragonmux added the Enhancement General project improvement label Nov 18, 2022
@dragonmux dragonmux requested a review from esden November 18, 2022 02:40
…shift_dr} as using the global instance is fine
@dragonmux dragonmux force-pushed the fix/jtag-tap-cleanup branch from 92dad5f to b2077ff Compare November 18, 2022 02:44
Copy link
Copy Markdown
Member

@esden esden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It logically LGTM. It needs practical testing. But I will lean towards optimistic merging here. We can shake out any potential regressions in the stabilization period.

@esden esden merged commit 1ea7c30 into main Nov 18, 2022
@dragonmux dragonmux deleted the fix/jtag-tap-cleanup branch November 18, 2022 11:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Enhancement General project improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants