Good idea! Don't have the device with me right now, will check that in the evening. Problem is I only have access to a V4 JLink, but I'm pretty sure I'll find some openocd logs of V5 on the net.
I think even I can implement that. But to do the automatic version check you need to send using 2 different endpoints. First try using Version 5 endpoint, in case of error fall back to older protocol. Benjamin -------- Original-Nachricht -------- > Datum: Mon, 16 Mar 2009 21:20:19 -0000 > Von: "Spencer Oliver" <s...@spen-soft.co.uk> > An: "\'Benjamin Schmidt\'" <dem...@gmx.net>, > openocd-development@lists.berlios.de > Betreff: RE: [Openocd-development] PATCH for black JLink Rev <5.0 > > Hi! > > > > I'm not really familiar with OpenOCD development but I wanted > > to make my older black JLink interface work with OpenOCD. It > > took some time to understand the differences between v5 and pre v5... > > > > I got it to work but I'm not really sure how to implement a > > second variant of the JLink interface for the older protocol. > > It's only very few differences, so I guess it shouldn't be > > that much of a problem. > > > > we could possibly make this automatic - what is returned for the version > of > a v5 jlink? > run jlink_info cmd and hopefully you may see some output. > > Cheers > Spen -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
