Error: "Unable to start device"

[Bernhard Walle-4]

Hi @all,

At first some background: I'm the maintainer of the USBprog PC software.
USBprog is a custom USB device
(http://www.embedded-projects.net/index.php?page_id=135) that allows to
program various microcontrollers with different firmwares.

I'm in the process of porting the software from libusb-0.1 to
libusb-1.0. On Windows, we used libusb-win32 previously which didn't
work always as flawlessly as we wished. On Linux, the libusb-1.0 port is
now working, so I wanted to try out the Windows version.

After installing the driver binary
http://libusb-winusb-wip.googlecode.com/files/setdrv_20100330.exe, I
have following error:

http://dl.dropbox.com/u/5838417/usbprog_error.png

The English translation is "Unable to start device (Error 10)". I'm
using Windows 7 Prof. (32 bit). Does somebody know what that error
message means, and where to look further? I coulnd't exclude firmware
errors (e.g. in the device enumertation), but further debugging messages
would be very helpful.

Thanks for your advise!


Regards,
Bernhard

------------------------------------------------------------------------------
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel

[Xiaofan Chen]

On Sat, May 1, 2010 at 6:43 PM, Bernhard Walle <[hidden email]> wrote:
> I'm in the process of porting the software from libusb-0.1 to
> libusb-1.0. On Windows, we used libusb-win32 previously which didn't
> work always as flawlessly as we wished.

What is the main problem you are facing with libusb-win32?
I am interested to know that since now I am port of the
admin team for libusb-win32. ;-) We will probably come out
a new release pretty soon trying to address some bugs.

> On Linux, the libusb-1.0 port is
> now working, so I wanted to try out the Windows version.
>
> After installing the driver binary
> http://libusb-winusb-wip.googlecode.com/files/setdrv_20100330.exe, I
> have following error:
>
> http://dl.dropbox.com/u/5838417/usbprog_error.png

So you are using WinUSB right now.

> The English translation is "Unable to start device (Error 10)". I'm
> using Windows 7 Prof. (32 bit). Does somebody know what that error
> message means, and where to look further? I coulnd't exclude firmware
> errors (e.g. in the device enumertation), but further debugging messages
> would be very helpful.
>

With code 10, you may want to look at the following two files.

C:\windows\system32\inf\setupapi.app.log
C:\windows\system32\inf\setupapi.dev.log

Please post the relevant part when you plug the device in.

Previous report by others show that the major problem tend to
be firmware bug with regard to the "set interface" command.
http://old.nabble.com/libusb-V1.0-with-Win2K---libusb0.sys-back-end-support-td27965705.html

Quote from Graeme Gill:
[ Unfortunately it seems that I will need the libusb0.sys back end,
   as an important device for me is incompatible with WinUSB, since
   WinUSB seems to do a GET_STATUS before SELECT_CONFIGURATION
   on device insertion, and something about that causes this device
   to lock up. ]

libwdi page has some links as well.
http://www.libusb.org/wiki/libwdi
http://www.microsoft.com/whdc/driver/install/diagnose.mspx

The Windows USB Core Team blog can be very helpful as well.
http://blogs.msdn.com/usbcoreblog/


--
Xiaofan http://mcuee.blogspot.com

------------------------------------------------------------------------------
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel

[Graeme Gill]

Xiaofan Chen wrote:
> Quote from Graeme Gill:
> [ Unfortunately it seems that I will need the libusb0.sys back end,
>    as an important device for me is incompatible with WinUSB, since
>    WinUSB seems to do a GET_STATUS before SELECT_CONFIGURATION
>    on device insertion, and something about that causes this device
>    to lock up. ]

Yep, I think the symptoms I was getting was error 10, "unable to start".

Graeme Gill.

------------------------------------------------------------------------------
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel

[Bernhard Walle-4]

Hi,

Am 01.05.2010 13:12, schrieb Xiaofan Chen:
> On Sat, May 1, 2010 at 6:43 PM, Bernhard Walle<[hidden email]>  wrote:
>> I'm in the process of porting the software from libusb-0.1 to
>> libusb-1.0. On Windows, we used libusb-win32 previously which didn't
>> work always as flawlessly as we wished.
>
> What is the main problem you are facing with libusb-win32?
> I am interested to know that since now I am port of the
> admin team for libusb-win32. ;-) We will probably come out
> a new release pretty soon trying to address some bugs.

The main problem was that it make Windows Vista and Windows 7 unusable
in some constellations (at least if you have a USB keyboard, if the USB
stack doesn't work any more, I would consider it as unusable). Ok, after
we stopped using the filter driver, it became better. It worked at least
in my tests, but I still got some rare customer reports that said that
it still broke Windows. I could not confirm that.

The other problem was that it looked like the project was dead. That's
not true any more now. :-)

In any case, the new USBprog version can be compiled against both the
old libusb-0.1 API and the new libusb-1.0 API. So it would be still
possible for me to release the version against libusb-win32 if it turns
out to be the better base. (http://gitorious.org/usbprog, BTW.)

> With code 10, you may want to look at the following two files.
>
> C:\windows\system32\inf\setupapi.app.log
> C:\windows\system32\inf\setupapi.dev.log
>
> Please post the relevant part when you plug the device in.

The correct path is C:\windows\inf\setupapi.app.log and
C:\windows\inf\setupapi.dev.log, BTW (only for the archive). The
relevant snipped should be attached. At least I don't see anything that
says more about the error than I already know (error 10).

> Previous report by others show that the major problem tend to
> be firmware bug with regard to the "set interface" command.
> http://old.nabble.com/libusb-V1.0-with-Win2K---libusb0.sys-back-end-support-td27965705.html

Thanks for that hint. Since I can exchange the firmware, that could be
fixed in the device. However, I need to do further debugging which takes
some time. I'll come back to the list if I need further advise.

Thanks a lot for all the hints.


Regards,
Bernhard


------------------------------------------------------------------------------
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel

[Bernhard Walle-4]

Am 03.05.2010 06:43, schrieb Bernhard Walle:
> The relevant snipped should be attached.

Forgot the attachment. Well, here's a link:
http://dl.dropbox.com/u/5838417/setupapi.dev.log


Regards,
Bernhard

------------------------------------------------------------------------------
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel

[Pete Batard]

On 2010.05.03 06:44, Bernhard Walle wrote:
> Forgot the attachment. Well, here's a link:
> http://dl.dropbox.com/u/5838417/setupapi.dev.log

Thanks for the log. I'm not seeing anything obvious there, and by the
looks of it, I don't believe it comes from using the automated driver
installer either. Up to the device restart, everything looks as
expected, and any issue with the inf or driver files would have been
picked up prior to that, so the driver installation itself should be OK.

I remember getting similar errors when I was building a custom firmware
for an USB PIC device, and the firmware had a problem, so I too would
think it might be a firmware issue.

If you can try with a different firmware, and see if it helps, that
might be the best course of action for now.

Regards,

/Pete

------------------------------------------------------------------------------
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel