I now get a successful build under cygwin. When I plug the jlink usb to windows and run openocd I see the the "Cannot find jlink Interface!" error as printed below. Do I need another special windows driver when running jlink in cygwin? To build I only copied usb.h and libusb.a as directed from libusb-win32 project. There is quite a bit of stuff in the libusb-win32-device-bin.tar.gz that I haven't used. Should this be installed?
$ src/openocd.exe -d 3 -s ./tcl -f interface/jlink.cfg board/stm3210e_eval.cfg Open On-Chip Debugger 0.2.0-in-development (2009-06-09-11:02) svn:2177M BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS $URL: svn://localhost:36903/openocd/trunk/src/openocd.c $ Debug: 5 0 configuration.c:83 find_file(): found ./tcl/interface/jlink.cfg Debug: 7 0 command.c:88 script_command(): script_command - interface Debug: 8 0 command.c:105 script_command(): script_command - interface, argv[0]=ocd_interface Debug: 9 0 command.c:105 script_command(): script_command - interface, argv[1]=jlink Debug: 11 15 command.c:88 script_command(): script_command - init Debug: 12 15 command.c:105 script_command(): script_command - init, argv[0]=ocd_init Debug: 13 15 openocd.c:129 handle_init_command(): target init complete Error: 14 15 jlink.c:315 jlink_init(): Cannot find jlink Interface! Please check connection and permissions. Debug: 15 15 command.c:424 run_command(): Command failed with error code -100 User : 16 15 command.c:626 openocd_jim_vfprintf(): Runtime error, file "command.c", line 453: User : 17 15 command.c:626 openocd_jim_vfprintf(): _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
