On Wed, Jul 6, 2011 at 10:02 PM, Eric Wetzel <[email protected]> wrote: > > This built cleanly, and I got an openocd.exe that doesn't segfault > immediately and ldd says doesn't depend on cygwin1.dll. Those seem > like positive things. The trouble comes when I try to use it. I'm > using the target/omapl138.cfg because they're comparable chips (the > OMAP-L138 is an AM1808 with a sequencer and a DSP), and I need > something to get ICEpick to enable the debug ports. The same thing > happens with no target specified and J-Link disconnected from the > board. > > openocd.exe -c "source [find interface/jlink.cfg]" -c "source [find > target/omapl138.cfg]" > Open On-Chip Debugger 0.5.0-dev-00941-gff640f1 (2011-06-28-10:38) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > Warn : Adapter driver 'jlink' did not declare which transports it > allows; assuming legacy JTAG-only > Info : only one transport option; autoselect 'jtag' > RCLK - adaptive > fast memory access is enabled > dcc downloads are enabled > force hard breakpoints > use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled > Info : J-Link initialization started / target CPU reset initiated > Info : J-Link ARM V8 compiled Apr 27 2011 20:42:35 > Info : J-Link caps 0xb9ff7bbf > Info : J-Link hw version 80000 > Info : J-Link hw type J-Link > Info : J-Link max mem block 8384 > Info : J-Link configuration > Info : USB-Address: 0x0 > Info : Kickstart power on JTAG-pin 19: 0x0 > Info : Vref = 3.319 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0 > Info : J-Link JTAG Interface ready > Info : RCLK (adaptive clock speed) > Error: usb_bulk_read failed (requested=1, result=0) > Error: jlink_tap_execute, wrong result -107 (expected 1) > Error: usb_bulk_read failed (requested=1, result=0) > Error: jlink_tap_execute, wrong result -107 (expected 1) > in procedure 'transport' > in procedure 'init' > > It's clearly able to communicate with the J-Link to get the hardware > information, version string, pin states (including Vref on the > target). But then some USB reads fail. Afterwards, the J-Link becomes > unresponsive for about 2 minutes; its LED is off, but it is still > present in Device Manager, and repeated openocd attempts fail to get > J-Link info: > > openocd.exe -c "source [find interface/jlink.cfg]" -c "source [find > target/omapl138.cfg]" > Open On-Chip Debugger 0.5.0-dev-00941-gff640f1 (2011-06-28-10:38) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > Warn : Adapter driver 'jlink' did not declare which transports it > allows; assuming legacy JTAG-only > Info : only one transport option; autoselect 'jtag' > RCLK - adaptive > fast memory access is enabled > dcc downloads are enabled > force hard breakpoints > use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled > Info : J-Link initialization started / target CPU reset initiated > Error: J-Link command 0x01 failed (-116) > Error: J-Link command EMU_CMD_VERSION failed (0) > Info : J-Link JTAG Interface ready > Info : RCLK (adaptive clock speed) > Error: J-Link command 0xdf failed (-116) > Error: usb_bulk_write failed (requested=6, result=-116) > Error: jlink_tap_execute, wrong result -107 (expected 1) > Error: usb_bulk_write failed (requested=6, result=-116) > Error: jlink_tap_execute, wrong result -107 (expected 1) > in procedure 'transport' > in procedure 'init' > > Is anyone else having problems with J-Link under Windows 7? Or just > Windows 7? Or just J-Link?
Try to update the libusb-win32 version to see if that helps. On the other hand, this may have something to do with either your J-Link version or your target. I just tried J-Link V7 and LPC-2148 target under Windows 7 32bit and it is okay. I am using libusb-win32 1.2.4.7 snapshot edition and Freddie's latest development version binary. So it is not the latest git version but you can try it. I also tried the same binary under Windows 7 64bit a few days ago without an issue. -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
