I got lucky and found a USB 2.0 Protocol Analyzer.
Since I am no expert and I am learning this myself, the bare minimum to get to a device driver.
I thought I would share the data I collect in case someone else understands it better.. or might eventually take over the whole project.
I can't see the forest for the trees right now.. so I don't know when it might be complete.
First Step:
I downloaded the "free" Datacenter and used that to capture USB bus from the moment the USB cable of the ATI USB2.0N video capture box was plugged into the laptop acting as the video capture host.
It appears to me it negotiated USB bus speeds up to (480 Mbps) High Speed, then assigned it a USB bus address number, and then interrogated it to discover why kind of device it was.
Then the Host appears to have loaded a device driver on the video capture host and started sending a binary blob to program the USB bridge chip.
Then it settled down and just pinged it every so often.
That is the basic Windows XP device driver start up procedure.
Windows recognized a new device, fetched its hardware identifier, loaded a device driver and sent a binary blog to the device to set it up.
Any Windows x64 device driver would have to do the same thing.
I can see it has one Configuration and one Endpoint, with Four Interfaces.
One interface uses the USB Bulk protocol to transfer data
Three interfaces use the USB Isochronous protocol to transfer data
All the Interfaces are Inputs
The compressed tdc capture file is attached to this message, it is very small, less than 1 Megabyte.
The USB protocol analyzer I'm using is the
www.TotalPhase.com USB 480 Beagle.
The viewer software I am using for capture and to decode the capture is the Total Phase Data Center protocol analysis software. Version 6.73.007 on Windows 7 x64.
The Data Center software can be downloaded here
Data Center
For Windows, Linux or Mac
You do not have to have the USB 480 in order to install the Data Center software and open up the capture file.
Capturing the start up the ATI USB2.0 video capture box when
VirtualDub 1.9.11 was opened on Windows XP SP2 went well and appeared to have no problems.
After a few seconds the capture produced a 98 MB file, but I think its orders of magnitude more complex.
VirtualDub had to build a Directshow graph to model the flow and use that to retrieve video and sound from the ATI USB2.0N video capture device.
That was more a "stunt" than a serious collection of data. I wanted to see if it could be done. And the results were good.
Really I think the proper way to proceed is to startup GraphEdit 32bit and load the ATI USB2.0N cross bar and capture exercising its functions retrieving and setting things. Those should send commands to the video capture device across the bus. Those same command should be appropriate for a 64 bit device driver. Then load the capture filter and do the same.
I'm not too interested in the BDA Tuner filter since NTSC signals are no longer broadcast.
This device also has no hardware MPEG encoding feature so there are no hardware encoding filters to map out.