Lpc2000

--- In lpc2000@yahoogroups.com, Dominic Rath <Dominic.Rath@g...> wrote:
>
> I asked ARM if I could get access to the RDI specifications, and got
a "no". I 
> didn't ask to have it for free, but I said that I wanted to use it
for my 
> open source debugger (OpenOCD).
> I asked if there would be licensing issues when using RDI in an open
product 
> (there's enough information publicly available to get RDI working),
and got a 
> "sorry can't help".
> 
> I want to support it, but I can't. By your definition, that makes
RDI a closed 
> standard.
> 
> Regards,
> 
> Dominic
> 
You are right, Dominic!  By my definition your experience with ARM
pretty much describes a "closed" standard.  If that is the current
situation regarding RDI from, then I am completely wrong in calling it
an "open" standard.

That does raise some interesting questions though!  How did twentyone
get it working so well for H-JTAG?  It works very well with all the
debuggers that I have tried that claimed RDI support.  There are also
a number of other high priced commercial debuggers in existance that
support RDI, when you do a Google on RDI. SDT2.51, Keil, and IAR are
the only systems that I have personally used RDI with.  I've also used
 ARM ADS1.2, but I used Trace32 instead of an RDI debugger with that.

Anyway, I apologize for classifying RDI as an "open" interface if it
is as "closed" as it was to you, Dominic.

-- Dave