The problem is the NET Chip doesn't interrupt any more and doesn't respond to a get device descriptor after the chirp. After the chirp, the USB device appears hung and only a hardware reset (not USB bus reset) will clear it and make it operation again. Of course on a HS enabled bus, the reset will cause the Chirp again, so it is vicious cycle. So if I could maybe filter the chirp, then the NET2890 might have chance to work.
I guess the real question is, has anybody on this forum ever gotten the NET2890 to work correctly on a USB 2.0 HS bus? If so I would like know how, so I can fix my problem without having to change the design to a USB device chip that will work when connected to a HS USB bus. Maybe a read of the USB device receive buffer would "clear and enable" USB interrupts if it was known when the chirp had completed?
Thanks, again, jmw