Brand new uno R3 suddenly stopped registering but meg16u2 is oscillating

Development Tools IDE 1.x
1

Hi
There appears to nothing blown on my board as I can't see any obvious signs it's gone wrong.
I have confirmed both the 328 and the mega16u2 are oscillating using my scope. However in windows it doesn't
recognise it as the uno. JUst says "Windows has stopped this device because it has reported problems. (Code 43)" why? Ihave tried two usb cable and two pc's I even tried it under linux to ensure windows wasn't being stupid.

It was working the last time I used it because that's how I uploaded my firmware onto a blank chip.

2

What is oscillating? That is where have you put the two scope leads to see the oscillation?

3

Sorry guys I've found the problem. I have some how managed to damage the tiny tiny 22 ohm resistor on one of the data lines of the usb connection. I fixed it by soldering a temporary bodge resistor to the pad.

4

It is customary to say what the problem was so that others can benefit form your experience.