Does either rev 1833 or 1833 with my patch displaying something like this in the beginning?
Info : J-Link compiled Feb 20 2006 18:20:20 -- Update -- Info : JLink caps 0x3 Info : JLink max mem block 32 Info : Vref = 3.283 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 1 TRST = 255 The problem is that my old JLink uses a different USB endpoint, so if one version succedes this simple output message, the other WILL fail because it is sending to a channel where the jlink doesn't answer at all I only have access to a stm32 and an at91sam7s64 board ./src/openocd -f ./src/target/interface/jlink.cfg -f ./src/target/target/stm32.cfg That's how i call oocd atm... With my patch I only get one Error: J-Link command EMU_CMD_VERSION failed (-110) error in the beginning and every other 2 or 3 times it doesn't detect the jlink at all, but if the JLink info message appeares, there'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 > > > > > > > > It can show the hardware version. > > With patch still gets three EMU_CMD_GET_CAPS errors and "don't worry". > Then LED goes off on jlink. Should it go off? Not sure how I know that > it is definitely working or not working. "Reset halt" command fails > "usb_bulk_read failed ...". "flash info 0" seems to work. > Will try the link above in morning. > What command line do you use to start openocd with jlink and str712 > board? Thanks for any pointers you can provide! > -gene > > > On Monday 18 May 2009 11:24:51 pm Gene Smith wrote: > >> Benjamin Schmidt wrote: > >>> Hello, > >>> > >>> I posted a similar patch several month ago. > >>> I have a JLink version v3.0 > >>> > >>> To get it to work you have to change several little things. > >>> > >>> This is just a very ugly hack that somewhat disables support for >=V5 > >>> JLinks > >>> > >>> I'd just be interested if any of you can also get it to work this > >>> 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... > >> > >> I will let you know if it works before you explain it. > >> > >>> Benjamin Schmidt > >> > >> Thanks! I have no idea what "version" jlink I have (yellow, marked > >> j-link ks/IAR systems on front, j-link-arm-ks on back. Where do you find > >> the version? Inside? > >> > >> I see your patch is against 1833 (head) which I now have so will give it > >> a try. Thanks again! > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
