• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 23 subscribers
  • Views 2443 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Current debugging probe/AGDI documentation for Keil uVision?

Andrew Lentvorski

Where is the current documentation for creating a DLL for a debugging probe?

Application Note 173: AGDI for ARM target systems seems to have disappeared, so I presume that it has been superseded.  Application Note 145 does not apply to ARM and is ancient as well as fairly difficult to get to compile on modern Visual Studio's.

Thanks.

Parents
  • 0 in reply to Adam Lins

    CMSIS-DAP is not a solution since the abstraction is at the wrong level.  CMSIS-DAP is meant for banging bits on cheap probes and is a huge bottleneck.  USB doesn't help either.

    In my instance, I want to talk to my debugging probe via Ethernet directly from Keil.  Eventually, I want to be able to do trace over Ethernet.

    This clearly is possible as the Segger stuff does this.  What I need, however, is the specification.

Reply
  • 0 in reply to Adam Lins

    CMSIS-DAP is not a solution since the abstraction is at the wrong level.  CMSIS-DAP is meant for banging bits on cheap probes and is a huge bottleneck.  USB doesn't help either.

    In my instance, I want to talk to my debugging probe via Ethernet directly from Keil.  Eventually, I want to be able to do trace over Ethernet.

    This clearly is possible as the Segger stuff does this.  What I need, however, is the specification.

Children