Re: [Openocd-development] OpenOCD broken

2009-12-13 Thread Benjamin Schmidt
Not sure if interesting to anyone, but I just ran svn head againt cppcheck... this is the result: [./contrib/libdcc/dcc_stdio.c:156]: (style) Warning - using char variable in bit operation [./src/flash/aduc702x.c:140]: (style) The scope of the variable x can be limited [./src/flash/aduc702x.c:1

Re: [Openocd-development] OpenOCD and different versions of J-Link

2009-05-19 Thread Benjamin Schmidt
On Tuesday 19 May 2009 03:19:06 pm Gene Smith wrote: > Info : J-Link compiled Dec 2 2004 09:13:33 That seems like a very very old firmware version. And I just remembered something... When I got my JLink, it was on a somewhat old firmware version as well... Linux segger tool did nothing at all..

Re: [Openocd-development] OpenOCD and different versions of J-Link

2009-05-19 Thread Benjamin Schmidt
Hello Magnus, thanks for your patch... that is half the way needed to make my V3 JLink work. The other thing is that at least mine doesn't support the EMU_CMD_HW_JTAG3 command. This is not documented in the USB protocol description as far as I know. My JLink doesn't answer at all to this comman

Re: [Openocd-development] OpenOCD and different versions of J-Link

2009-05-18 Thread Benjamin Schmidt
Hello Igor I think this wouldn't hurt anyone and could be very useful for debugging like this. But it should definately check via EMU_CMD_GET_CAPS first if command is available. At the moment the caps value is read from the device but for example the call to EMU_CMD_GET_MAX_MEM_BLOCK is done o

Re: [Openocd-development] OpenOCD and different versions of J-Link

2009-05-18 Thread Benjamin Schmidt
27;s no more errors... Benjamin On Tuesday 19 May 2009 12:36:24 am Gene Smith wrote: > Benjamin Schmidt wrote: > > There's this segger closed source linux gdm server tool... > > > > http://www.segger.com/pub/jlink/JLink_Linux_090202.tar.gz > > > > > >

Re: [Openocd-development] OpenOCD and different versions of J-Link

2009-05-18 Thread Benjamin Schmidt
There's this segger closed source linux gdm server tool... http://www.segger.com/pub/jlink/JLink_Linux_090202.tar.gz It can show the hardware version. On Monday 18 May 2009 11:24:51 pm Gene Smith wrote: > Benjamin Schmidt wrote: > > Hello, > > > > I posted a s

Re: [Openocd-development] OpenOCD and different versions of J-Link

2009-05-18 Thread Benjamin Schmidt
way... I would like to build a clean version of this patch that doesen't break the rest of the system, but I'd need some more help as I'm not experienced in any openocd/jtag code If you're interested I can explaine all the things that I needed to change... Benjamin Schmidt On

[Openocd-development] Build problem with Rev1795 on Linux, GCC 4.4.0

2009-05-15 Thread Benjamin Schmidt
emonk/openocd-head/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/demonk/openocd-head' make: *** [all] Error 2 Is this a known issue? Benjamin Schmidt ___ Openocd-development mailing list Openocd-development@lists.ber

Re: [Openocd-development] PATCH for black JLink Rev <5.0

2009-03-17 Thread Benjamin Schmidt
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 - > Von: "Spencer Oliver" > An: "\'Benjamin Schmidt\'&quo

[Openocd-development] PATCH for black JLink Rev <5.0

2009-03-15 Thread Benjamin Schmidt
Link < 5.0 doesn't seem to understand the EMU_CMD_HW_JTAG3 command, so changed to EMU_CMD_HW_JTAG2. Difference is that EMU_CMD_HW_JTAG2 doesn't reply 0x00 on success, so removed that part. As far as I tested the hole thing seems to work ok. Benjamin Schmidt de