On Tue, Sep 18, 2012 at 12:37 AM, Abhishek Kumar <abhishek.kak...@hotmail.com> wrote: > Hello All, > > I am using an STM32F4Discovery Board along with ChibiOS/RT on a Windows system > (Freddie Choppin's binaries), with a development platform of ChibiStudio > (http://forum.chibios.org/phpbb/viewtopic.php?f=13&t=557). It does not seem > to work with my system. Whenever I try to start it up, I encounter the > following errors: > > Brief Log: > ---------------------------------------------------------------------- > Open On-Chip Debugger 0.6.0 (2012-09-07-10:48) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.sourceforge.net/doc/doxygen/bugs.html > adapter speed: 1000 kHz > Info : clock speed 1000 kHz > libusbx: > warning [windows_get_device_list] > '\\.\USB#VID_0461&PID_4DFA#5&540BBBE&0&1' was only > detected in late pass (newly connected device?) - ignoring > libusbx: > warning [windows_get_device_list] > '\\.\USB#VID_0483&PID_3748#5&540BBBE&0&3' was only > detected in late pass (newly connected device?) - ignoring > Error: open failed > in procedure 'transport' > in procedure 'init' > >... > > I am able to use my device with the ST-LINK utility provided, and debug > using Atollic's GDB server for ST-LINK. > > I tried first with the default driver, then with vanilla libusb-win32 > drivers, but none seems to work. Also, I face the same problems with > 32-bit as well as 64-bit binaries, on both rc2 and release versions. > > OpenOCD is launched with the following parameters: > -f interface/stlink-v2.cfg -f target/stm32f4x_stlink.cfg
stlink requires libusbx (or libusb-1.0 API). Freddie's binary uses libusbx-1.0.12 which needs WinUSB driver. So you can not use the libusb-win32 driver. But the default driver from ST for ST-Link V2 is WinUSB, so it should work out of the box. > My System configuration is a Dell Laptop (i7 Ivy Bridge, HM77 > express chipset) which has 4 USB ports, all USB 3.0. > > I have no idea what's going on. I'm unable to understand this > late pass thing and want to know what's wrong. USB 3.0 may be the issue here. You may want to use 1.0.13 rc2 version of libusbx and try again. It fixes some issues of libusbx with regard to USB 3.0. The following commits is the relevant one. https://github.com/libusbx/libusbx/commit/636ed66d2639f7610dba792ffe998dc636625f01 Take note right now only the source codes of libusbx 1.0.13 rc2 is provided. You need to build from source. But 1.0.13 release of libusbx is coming soon and then a Windows binary will also be provided. -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
