DAP: add DAP_GetInterfaceCapabilities vendor command #931
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
… implementation. Includes documentation of the new command in docs/dap_vendor_commands.md.
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.
The default implementation of the
get_interface_capabilities()function is weak so it can be overridden by HICs.Only two capabilities are defined so far, primarily for discussion purposes:
kCapability_FileFormatBinary: Programming of binary firmware files is supported.kCapability_FileFormatIntelHex: Programming of Intel hex files is supported.Includes documentation of the new command in a new
docs/dap_vendor_commands.mddocumentation file. (Existing vendor commands need to be documented here.)