the problem may be that
the pipe is naking but i am not able to comfirm this
as i do not have a USB analyzer
Without an Analyser there is no way to confirm this. NAKing would be
the most likely explanation.
If you've been assigned this project, it would be useful if whoever
is assigning it would also provide proper tools for you to do the
assignment. An analyser is the proper tool for this job.
am i able to derive the
access codes(ie: commands to capture image) through
the help of a usb sniffer program?
There are sniffers available on Windows, there use is beyond the
scope of this list. "USB Snoopy" is one which is mentioned a lot.
So it seems not only have you been assigned a task without the proper
tools, you've also not been provided with the proper documentation.
While this may be quite realistic in terms of what happens in the
real word, its not really a very good learning exercise.
Who's assigning you this exercise in futility?
Question 3:
if i am able to dervie the access codes say, .. do i send this
command through the control pipe or
the bulk pipe?
The obvious thing to do would be to do the same as what you're seeing
the Windows driver do. If it sends something over the control pipe,
send it over the control pipe, if its over the bulk pipe, use the
bulk pipe. All you can do is slavishly follow what the driver you
have is already doing.
This is not a very satisfactory way of developing a driver, but it
can be effective, I've done it myself.
I'd guess given you don't know how to initialise the camera that it
is NAKing in your first question. Until a device like this is
properly configured all you'll typically get out of it is a NAK.
--
Barry Twycross
email@hidden
---
USB, it's not a Dyslexic BUS. (Thanks to TC.)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/usb/email@hidden
