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

software JTAG mode #20

Merged
merged 1 commit into from
Sep 15, 2015
Merged

software JTAG mode #20

merged 1 commit into from
Sep 15, 2015

Conversation

Baldanos
Copy link
Collaborator

Software JTAG for Hydrabus.

This is a first implementation of the JTAG protocol for the HydraBus

Features :

  • Classic JTAG (TDI/TDO/TMS/TCK)
  • Can be used with command line
  • BusPirate-compatible OpenOCD binary mode ( openocd command)
  • Can scan a JTAG bus with IDCODE and BYPASS methods ( idcode and bypass commands)
  • Can try to find JTAG bus on all GPIOB pins (like JTAGulator) ( brute command)

TODO:

  • Enhance port speed
  • Enhance binary mode
  • Add support for TRST
  • Add support for MSB/LSB when reading

bvernoux added a commit that referenced this pull request Sep 15, 2015
software JTAG mode
Thanks for that amazing contribution !!
@bvernoux bvernoux merged commit 86b40fe into hydrabus:master Sep 15, 2015
@Baldanos Baldanos deleted the jtag branch September 15, 2015 19:01
@bvernoux
Copy link
Member

There is infinite loop problems when system does not answer example:
jtag_scan_bypass & tag_scan_idcode => It shall check regularly => if(USER_BUTTON) to returns (to avoid infinite loop) to be checked if there is other case to avoid infinite loop.
Also my test with LPC4330 show that scan_bypass & scan_idcode does not returns anything (but it could be specific to case of LPC43xx) I will check with other MCU/Devices with JTAG.

Could you tell on which MCU/CPU the code has been tested and is working ? (and which function ?)

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 this pull request may close these issues.

None yet

2 participants