Frontline USB analyzer does not report all USB events???

[st2000]

Hi,

I'm trying to see what events lead up to Win7 changing the state of a Ethernet-over-USB network from "Disabled" to "Available"  I have a Frontline USB analyzer between my test-firmware-hardware board which is trying to be a Ethernet-over-USB Device.  But I don't see any new entries/event in any of the Frontline windows (Event Display or Frame Display) when I plug in my board.  So I decided to make a base line test.  I substituted a know good Trendent Ethernet-over-USB dongle for my test-firmware-hardware board .  Again, I did not see any new entries/events in any of the Frontline windows.  I checked the Frontline filters and I am fairly sure there are none.  There has to be something going on over the USB cable.  The Win7 box creates a new Network when I plug my test-firmware-hardware board in.  The Win7 box also create a new Network when I plug in the Trendent dongle.  The difference is that my firmware is not complete (the goal here is to make it complete) and results in a "Disabled" network.

-thanks

[st2000]

Maybe a better line of questioning would be to ask what are the "USB negotiations messages" called?  If there is such a term, I could do a bit of research/searching.  My guess is that this analyzer and/or host-computer-software is not displaying these messages by default in an attempt to keep the noise down.  But since I am at the initial stages of USB development, I am very interested in everything that is being said over the USB bus.

-thanks

[Jan Axelson]

A hardware analyzer should show every packet on the bus unless you've configured it to hide some traffic.

If the device completes enumeration with a configuration > 0, Windows has assigned a driver (look in Device Manager to find the driver).

Then the device must successfully communicate using the driver.

[st2000]

A hardware analyzer should show every packet on the bus unless you've configured it to hide some traffic.

I suspect there is pilot error on my part here.  But I checked and do not believe any filters are defined/active.  I'm trying several other things now, but will probably come back and spend more time reading up on Frontline software.

If the device completes enumeration with a configuration > 0, Windows has assigned a driver (look in Device Manager to find the driver).

There is a driver: "Freescale USB RNDIS #3".  But under "Control Panel\Network and Internet\Network Connections" the network is still assigned a description of "Disabled".

Then the device must successfully communicate using the driver.

I have a feeling the windows description ("Disabled") is somewhat subjective.  My bet is that the driver is communicating successfully.  But the connected Ethernet network is not-connected-well (I'm still working on that part). 

I was hoping to take this in small steps and verify the USB portion of my code was functioning by using the Frontline USB analyzer.  But since the analyzer is not working for me and the network is "Disabled" I have no tools that I know of to "look at" the USB activity.

So it looks like I will have to take one big step and cross my fingers that when I write all the code to connect the Ethernet to the USB in my device that the Win7 box will start behaving.  That's a big step and a lot of untested code all at once.

-thanks for your help.