How do I open, close, and then reopen a device driver?

I have WinUSB installed as the driver for a USB device and everything seems to work fine the first time I access the device, I can read and write to the device. Once I close the device handles (bResult=WinUsb_Free(myDevInfo.winUsbHandle); and bResult=CloseHandle(myDevInfo.deviceHandle);), run my open routine, which worked the first time, I can not read from the device any more. bResult in both of the above statements returns TRUE, so the resources for WinUSB should have been released. Am I missing something, why can I not open the device, close the device and then open it again? I am writing the code in VC++ 6.0.
Eric_BraunAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jkrCommented:
Are you calling 'WinUsb_Initialize()' (http://msdn.microsoft.com/en-us/library/aa476455.aspx) again after reopening the device?
0
trinitrotolueneDirector - Software EngineeringCommented:
you need to pass the device interface to the initialize routine...so each time an enumeration has to be done so that you get the list of device interfaces.

Are you doing this in your intialize routine?
0
Eric_BraunAuthor Commented:
Sorry for not responding to any of these comments. Everytime I went to view the comments all I would get was a blank screen, think I had a bad cookie or something. Anyways that aside, I have solved this issue, worked around, all though I still am not sure why I had the issue to start with. Yes, I do 'WinUsb_Initialize()' after reopening the device and I do set and read the device interfaces. What I had to do to get this to work was after running WinUsb setup routines, loading the device firmware,  I had to issue a WinUsb_ResetPipe on the IN and OUT pipes. This takes the pipes out of any stall that may have happened, which is what seems to be happening for some reason when the device is reopened, but not the first time it is opened.
Eric
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Editors IDEs

From novice to tech pro — start learning today.