lock down DAP0 {TEST, CPU} by default on cc13xx #1
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
This was referenced Nov 26, 2017
alexrayne
pushed a commit
to alexrayne/cc13xxware
that referenced
this pull request
Aug 26, 2020
Revert "lock down DAP0 {TEST, CPU} by default on cc13xx"
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 does the same as contiki-os/cc26xxware#1 but for 13xx-ware. For completeness, the PR message is duped here:
It's clear from ccfg.c the intention is/was that all debug interfaces should be locked down unless otherwise stated. This was previously inverted, enabled by default. The latest change did not lock down DAP0 TEST and DAP0 CPU. Reason unknown. They can safely and should be locked down by default.
This PR locks this down.
Cheers,
Marcus