RP2350: Improve config examples for secure/non-secure debug #131
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 replaces the previous examples
rp2350-dbgkey-nonsecure.cfg
andrp2350-dbgkey-secure.cfg
that had a hardcoded sequence of bits being sent. The new filerp2350-dbgkey.cfg
can take the key from a variable. It also adds a print of the lock status after the key has been sent.Example usage:
Another file
rp2350-nonsecure.cfg
can be used to connect to targets which only allow non-secure debugging.(This pull request is related to issue #129)