Remove efuse validation for JTAG #1382
Open
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
|
Download the artifacts for this pull request: |
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.
Description
Removing extra validation that was added with the enhancement of flash encryption in 1.9.0 release. The validation was checking efuse to see if JTAG is disabled on the board, by doing this the board was being reset to enter second bootloader. This was causing a timing issue with JTAG flashing.
These types of low level validation needs to be handled by OPENOCD.
Fixes #1368
Type of change
Please delete options that are not relevant.
Steps to test this pull request
Flash a project using JTAG flash method.
How has this been tested?
As described above
Test Configuration:
Checklist