geekhack
geekhack Projects => Making Stuff Together! => Topic started by: mikew0w on Wed, 28 May 2014, 14:45:40
-
Hello,
I recently got an ergodox from another member here.
After I received it I hooked up the right side and it was working fine. I didn't have a trrs cable or key caps so I didn't get a chance to type on it.
A few days later I plug it in and windows doesn't recognize it. I tried holding down reset while plugging it in (suggested on pjrc site) with no luck.
I tested continuity with a multimeter and I don't believe that there is any issues on the USB side of things.
I have an additional teensy++ 2.0 that my laptop sees instantly so I don't think that I have any driver issues.
Do teensys fail? Is there any other last ditch trouble shooting I can try?
Would it be best to just swap the teensy?
Thank you
-
They can fail but in this forum, of all the ergodox problems I've seen solved I'm not sure a failed teensy has ever been one of them.
So ... you held the reset button down. Doesn't that put it into programming mode? Like, maybe wipe it? Try reloading the firmware and see if that tells it to become a keyboard again.
Also, if PJRC's program could see it, then it was in programming mode, and / or had lost its keyboard firmware. Further, if the program can see the device, the teensy is probably fully functional.
...good luck...
-
I think that I wrecked a Teensy once. I probably reversed 5V and ground. I sent it back to Paul and he gave me a new one, but, really, it was probably my mistake.
-
I had one Teensy that was bad when I received it from PJRC. It tried to boot, but no led blink at all. I actually got it programmed with a firmware once, but then it would never recognize after that. I sent it back to PJRC, and they sent me a replacement.
-
So ... you held the reset button down. Doesn't that put it into programming mode? Like, maybe wipe it? Try reloading the firmware and see if that tells it to become a keyboard again.
Still not detected by the computer after holding down the button. This is why I tried troubleshooting the connectivity.
I've ordered an additional teensy 2.0. I guess I'll report back if that was the culprit.