Teensy 3.1 quit communicating

Status
Not open for further replies.

JayK

New member
I had been updating code in a 3.1 for about 2 hours with minor changes and reloads when it suddenly stopped communicating on the USB. The device was mounted on a circuit board in a plastic box with ventilation and nothing near it to cause an ESD event. The JPG named Fail_2 shows the W7 device info with a working 3.1. Fail_1 has the failing 3.1 which shows up as Serial Controller D. The W7 window updates each time the button on the 3.1 is pressed or released.

The 5V and 3.3V look good on the 3.1 and it doesn't get hot. I have tried the normal system shutdown and replug/restart everything fixes as well has holding down the 3.1 button while connecting the USB.

Any idea of other things I should try before declaring the 3.1 dead?

Should I not run the 3.1 at 96MHz? It didn't seem to be getting hot before I put it in the box but the air circulation in the box is not as good as an open board.
 

Attachments

  • Fail_1_18May15.jpg
    Fail_1_18May15.jpg
    81.7 KB · Views: 94
  • Fail_2_18May15.jpg
    Fail_2_18May15.jpg
    88.2 KB · Views: 133
both pictures feature this 'USB-Serial Controller D' in the failed condition - do I assume correctly that you have two Teensys and left the failed one plugged in whilst checking out another one?

Search the forums for testing both Mini54TAN and MK20DX256VLH7 basic functionality (Paul has answered similes of your problem many times).
 
Teensy recovered from USB problem

both pictures feature this 'USB-Serial Controller D' in the failed condition - do I assume correctly that you have two Teensys and left the failed one plugged in whilst checking out another one?

Search the forums for testing both Mini54TAN and MK20DX256VLH7 basic functionality (Paul has answered similes of your problem many times).

Rob,

Thanks for the hint on where to look for the answer. I was able to recover the Teensy. I think the explanation is that we sometimes have to use the Reset signal to get the Teensy to stop what it is doing and notice that we are trying to reprogram it.

On the pictures, the failed Controller D has to be uninstalled to remove it from the list and I forgot to do that before taking the good Teensy picture.
 
Status
Not open for further replies.
Back
Top