Benjamin Schmidt wrote: > 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
This is what I see with 1833 with your patch. It is some different that my original post of the reaction, but not sure if it is OK or not. Does this look correct?: [g...@localhost src]$ sudo ./openocd -f target/interface/jlink.cfg -f target/board/iar_str712_sk1.cfg Password: Open On-Chip Debugger 0.2.0-in-development (2009-05-18-18:21) svn:1833M BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS $URL: svn://localhost:36903/openocd/trunk/src/openocd.c $ 10 kHz Info : J-Link compiled Dec 2 2004 09:13:33 Error: J-Link command EMU_CMD_GET_CAPS failed (-110) Info : J-Link compiled Dec 2 2004 09:13:33 Error: J-Link command EMU_CMD_GET_CAPS failed (-110) Info : J-Link compiled Dec 2 2004 09:13:33 Error: J-Link command EMU_CMD_GET_CAPS failed (-110) Info : J-Link initial read failed, don't worry Info : J-Link JTAG Interface ready Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (9219). Workaround: increase "set remotetimeout" in GDB Error: usb_bulk_read failed (requested=1, result=-110) Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (3029). Workaround: increase "set remotetimeout" in GDB Error: usb_bulk_read failed (requested=1, result=-110) Error: usb_bulk_read failed (requested=1, result=-110) Warn : no telnet port specified, using default port 4444 Warn : no gdb port specified, using default port 3333 Warn : no tcl port specified, using default port 6666 > > 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... Mine is about the same but I am using the file for str710 (but my board is str712 that I copied to target/board/iar_str712_sk1.cfg > > 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 > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
