If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Teensy 2 ++

Got a Teensey 2 ++ and loaded some keyboard code into it, needed to update the code and when I got it hooked back up to reload the new code, the switch will not bring it into program mode, and the menu is greted out...any ideas

Thank you for your quick response...that did not work, pressing the button does nothing (use to bring up the teensey programmer) I am using Ubuntu to run the code in...any other ideas on has my Teensey somehow gotten hosed?

Try running "tail -f /var/log/syslog" in a terminal. This will let you see the Linux kernel's log messages. Every USB connect & disconnect should show something. If you get nothing, plug and unplug other USB cables to confirm you're seeing the kernel's info.

The recovery process involves holding the button down while the plug in the cable. Then you release the button after the cable is fully mated. If you loaded "bad" code which interferes with the USB, this lets Teensy start up with only the known-good bootloader.

This...tail -f /var/log/syslog did nothing, however...have done a bunch of testing since last post. If I try the recovery process, where you hold the button while plugging in the cable, the computer will audibly indicate that the device was connected...i.e. the "ding-dong" microsoft uses to alert you that a device has been plugged in, however, the light does not light up and when plugged into the computer that has the teensy loader on it, it still will not allow you to program the device....I am thinking it's bricked. anyone have anything else to try before I order up another one (or two)?

it bricked also...so question now is is there another way to reset the teensy, the normal way is not working

Pressing the button, or holding the button while plugging in the cable is the right way. There isn't any other supported way.

We can help you, but you're going to have to show us what you're really doing. Nobody can see your screen, nobody can see what steps you're actually trying, so we can't know where things are going wrong. We can't even tell which version of Ubuntu you're running.

With Linux, the kernel syslog messages are the way to troubleshoot. Earlier you said "This...tail -f /var/log/syslog did nothing". What exactly is "did nothing"? Not even an error message? The tail command should always print the last several lines of the already present data, or an error if that file doesn't exist, so you should at least have *something* in the terminal window.

When I said nothing....it was nothing. I am using it on a Umbuntu install on a laptop. I am trying to set it up to pick up a keyboard, but the gentelman helping I think grabbed the wrong code when he compiled it. So if I plug it into my windows machine, I can hear the "ding-dong" but nothing else. When I plug it into the Linux box, nothing with a capital N....no connection sound no light blink ....nothing, when I hold down the button and plug it in, absolutly nothing, no error message...nothing

I can tell you the most common problem is charge-only USB cables, which have only the power wires but not data wires at all.

But even with such a cable, the Teensy should still get power. Every brand new Teensy should blink when powered, because our final test loads the LED blink example. The LED should stop blinking when you press the button on the Teensy.

With a good USB cable, after pressing the button on Teensy, on Linux when viewing the kernel log messages, you should see lines similar to those I showed. On Windows, you should see a HID device appear in the Windows Device Manager, with ID 16C0 / 0478. It should look like this:

Linux can be quite difficult if you are not an expert with Unix & Linux.

Since you're getting the "ding dong" sound on Windows, please try using the Windows Device Manager. Open the section for Human Interface Device. When you hear the sound, after pressing the button, you should see the Human Interface Device section change. Look at the properties for all the devices listed. You should find one with the 16C0 / 0478 numbers.