Writefile problem with usb device

Question

1.00/5 (1 vote)

See more:

Hallo my friends

I have a project to communicate with a usb device using usb bus. The device has its own driver and a communication protokol Guid . In its guid there is this senetence :"After USB driver is installed any program can communicate with the device by using ‘CreateFile’, ‘ReadFile’ and ‘WriteFile’, common Windows system functions." So I followed the instructions and the Creatfile() function works very well. My problem is with Writefile()and ReadFile functions. It shows always this Error 3758100489 : Can anyone help me ? thank you very much P.s USB path is right 100%
In the guid book there is this note:All messages use Intel style byte ordering where fields larger than one byte are stored in memory so
that the least significant part is in lowest address.
So i tried to use functions to convert to littel Endien too

What I have tried:

I tried to use overlapped parameter in Creatfile() and Writefile() but still have the same problem.
i tried to use many forms of message packet with help from the guid too

Posted 12-Aug-18 23:10pm

Member 13947289

Updated 13-Aug-18 5:15am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rick York · Answer 1 · 2018-08-13T05:15:00

One odd thing with Windows API error codes is they are most often documented in hexadecimal form. This error code is E0001009 in hex and according to google there are a few different meanings for it. One is USBIO_ERR_NOT_BOUND. Reason: The handle is not bound to a pipe. This error is reported by the USBIO driver. I recommend looking for this error code in any documentation you have for the device.

A couple of tips here: display your error codes in hex. If you use printf or sprintf to deal with them then the format is "%08X" to display the error code in hex.

Also, since most windows machines run on an Intel processor the data will likely be in little endian format already so you shouldn't have to worry about converting it.