Support for JTAG-PDI based Atmel parts #992
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dragonmux
added
Enhancement
dragonmux
force-pushed
the
avr
branch
2 times, most recently
from
9bf27b4 to
d102cd4
Compare
dragonmux
force-pushed
the
avr
branch
2 times, most recently
from
4d1d61a to
74b5fc2
Compare
…rrectly add Flash and SRAM regions for the devices
…e masked ID code causes for the AVR logic
…ting logic make a bit more sense
…ach phases to see if we can make scanning reliable
…tates of the PDI controller
…he early 'PD' naming we had going on
…s_read, and fixed the order of operations in regs_read
…nfiguration out to the target
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR establishes support for several things related to the Atmel 8-bit AVR lineup:
It should be noted that the AVRs are pretty sensitive to how scan is completed which is why #978 had to land first, and the PDI controller is very sensitive to how data is clocked into the target. What the PDI controller does not care about is how fast we do so as JTAG on these parts is decoupled from CPU clock speed completely. You can run the PDI side of things at 10MHz on a processor running at 2 and nothing will hurt for that, except you getting a lot of PDI Delay Byte responses (which we make transparent to the target code for simplicity's sake).