Xiaofan Chen wrote: > On Fri, Jun 19, 2009 at 11:09 PM, Gene Smith<g...@chartertn.net> wrote: >>> That is right. This is an undocumented feature of libusb-win32 >>> that the author of libusb-win32 taught me to use back in 2007. >>> He is a very nice guy. Unfortunately he seems to be busy lately >>> so not much progress in the libusb-win32 front. >>> >>> More important question. ;-) >>> Does openocd work with this libusb-win32 driver? >>> >> Well, your're a nice guy too for helping with with this! Any yes, it >> works find with oocd. Not sure if the serial port works but I will try >> that on windows (it worked OK on linux). Still need to try jlink again >> on windows oocd (but it is also detected under LibUSB-Win32 Devices when >> I plug it in). Thanks again! > > I am glad to be of some help. I tried J-Link under Windows using > libusb-win32 driver and it seems to work fine. > >> P/S: This really needs to documented somewhere (other than random >> postings) :) >> > > Yes I agree. Once you confirm this works with OpenOCD, we > can make a documentation on this topic. > >
I can switch back and forth between jlink and olimex/ftdi OK in openocd and debug wiht insight. They both work OK. However, I don't see a new serial port in Dev mgr for the olimex. Where should I see this? I only see the built-in COM1 when I plug in the olimex ftdi adapter I see no new COM ports. (On linux it appeared as /dev/USB0tty and and I could send output to minicom.) In windows I only see builtin COM1 in hyperterm and on dev mgr. I tried the "hacked" libusb0.sys driver and it made no difference. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
