From: <Pet...@t-...> - 2019-04-08 10:09:19
|
Hello Xiaofan, in the meantime I´ve already recognized my fault. I´ve told that question to the OpenOCD mailing list, and I´ve got a very good support by Paul Fertser. But thank you for your comment: now it is clear for me. Best regards, Peter -----Original-Nachricht----- Betreff: Re: [Libusb-win32-devel] Error: unable to open ftdi device Datum: 2019-04-07T05:26:05+0200 Von: "Xiaofan Chen" <xia...@gm...> An: "Pet...@t-..." <Pet...@t-...>, "lib...@li..." <lib...@li...> In order to use OpenOCD under Windows you have to use a supported driver. For FTDI device, the recommended driver is to use WinUSB and use libusb-1.0 Windows (libusb-1.0.dll) and not libusb-win32 together with OpenOCD. Yet another possibility is usbdk driver, again with libusb-1.0 Windows and not libusb-win32. You should ask for more help in OpenOCD mailing list. This is the wrong mailing list for OpenOCD. This is also not the correct mailing list for libusb-1.0 Windows. Regards, Xiaofan On Wed, Mar 27, 2019 at 6:41 PM Pet...@t-... <Pet...@t-...> wrote: > > Hello all, > > > > I waant to use a mikrocontroller board communicatin by OpenOCD via USB. I´ve installed > > https://sourceforge.net/projects/libusb-win32/ > > > > And when I connect that device at USB I see two entries > > USB Serial Converter A (Interface 0) > > USB Serial Converter B (Interface 1) > > > > Both with Driver libusb0 (v1.2.6.0) > > USB ID 0403 6010 00 > > > > I use a config file thm_arduino.cfg with the follwoing entries: > > > > interface ftdi > ftdi_device_desc "OOCDLink" > ftdi_vid_pid 0x0403 0x6010 > > > > and run on console of my Windows Vista Business Service Pack 2 (latest version) > > > > openocd -f C:\Users\oehler\workspace\Labor3\interface\thm_arduino.cfg -f C:\Users\oehler\workspace\Labor3\mrt\board\thm_arduino.cfg > > > > But I am getting always the message: > > > > Error: no device found > > Error: unable to open ftdi device with vid 0403, pid 6010, description 'OOCDLink', serial '*' at bus location '*' > > > > Why OpenOCD can not find that device? What can I do to further check that the driver is correct installed? > > > > Best regards, > > Dr. Peter Oehler > |