Skip to content

Custom DAP_Info bytes #5

Description

@bugadani

Hi! I'm looking into adding cusom extensions to some CMSIS-DAP implementation, and I'd like ARM to reserve a few DAP_Info requests for vendor-specific use so that I can build tooling to detect my additions. Both the adaptor firmware and the tooling involved are open-source. The immediate goal I have is to implement raw JTAG transfer commands more efficiently, but I'd like to do this is a more generic and composable way.

What I'm looking for is an Info request that would return the list of extensions. The response would include, for each extension:

  • a magic number identifying the extension (this could be a 4-byte random number, hoping for no collisions)
  • a start byte and count that identifies a DAP_Info range specific to the extension
  • a start ID and count that identifies extension-specific commands

Could I ask ARM to reserve/define this scheme, or a similar extension description method?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions