Not able to Program Any file.

Status
Not open for further replies.
TS88 said:
Do you think the board is dead?
Click to expand...

Yes, everything you have described indicates a bad cable or dead board.

If so, would there be a plausible reason? Please help.
Click to expand...

The 2 likely reasons are a defective or charge-only USB cable, and possible damage to the board during soldering.

Your board is blinking, and it does stop when you press the button, so at least that's a good sign it's still alive.
 
KurtE said:
First off it looks like AUTO is turned on, so I believe that Program and Reboot will be disabled. If you click on Auto It should enable them.

I would check to make sure that your solder job on adding the headers did not create any shorts.

Again for new boards, the steps I typically take is to:
Load up Arduino IDE with the simple blink program, click Verify button in Arduino, should compile and bring up Teensy program you show. Then press the program button and it hopefully will program your teensy. Assuming your USB type is Serial or the like, it should then assign a COM port to the new teensy and hopefully after that you can program it by simply clicking the program button on the Arduino IDE...

Edit: also if this does not work, you might try a different Serial cable in case the one you are using does not work.

Also if most recent Windows 10, you might try downloading Paul's updated tools, which appeared to fix the problem for several people.
Click to expand...

Thanks Kurt for your kind comments. The Auto is not turned ON. The indicator is dull green when Auto is desleected and becomes bright green when selected. There are no shorts in the header. This problem occurred even when no headers were soldered. I have used both the Arduino ( compile/verify) and the Teensy loader directly. I am able to open the hex file, but pressing the button does not activate the program or reboot button. My OS is Win 10, 64 bit. I noticed that you mentioned Paul's updated tool. I will try using them to see if it fixes the problem. Is it on the PJRC website?
 
TS88 said:
My OS is Win 10, 64 bit. I noticed that you mentioned Paul's updated tool. I will try using them to see if it fixes the problem.
Click to expand...

That won't make any difference. It only solves a problem where the USB-based request to reboot wasn't sent, due to an incompatibility with Windows 10 update 1703.

This problem occurred even when no headers were soldered.
Click to expand...

Why did you solder to the board when you knew it wasn't working?!
 
Agree, maybe should not have soldered. I am new to this board, was trying to measure the pins and decided to add the header. But I checked the solder under a microscope. It looks clean and I do not think it damaged the board. When I first connected the board ( with no header), I used the Arduino. The board was recognized. Compiling and verifying resulted in the Teensy Loader to pop up. Auto was off. Pressing the button did not activate the program or reboot menu items or buttons.
 
What exactly do you mean by "The board was recognized"?

Almost everything you have described sounds like a charge-only cell phone cable, where Teensy gets power, the LED blinks because Teensy still has the LED blink program we program onto the board (using Teensy Loader through a good USB cable) during testing.

But some of the language you use makes no sense to me. Remember, we can't see your screen. Usually when people say "board was recognized", they mean some visual indication on their PC showed result of communication, such as the center of the Teensy Loader window showing a bright color image of the board, or the Windows Device Manager showing HID Compliant Device.
 
Sorry, the wording might be off. But as I have mentioned that I am new to this board as in NEW and expect a little consideration. It probably is the cable, although the cables were purchased from Adafruit. I have ordered another board / cable directly from your company. Hopefully using that cable will help me identify if it was actually a cabling problem. I have only one HID compliant vendor device in my Device Manager and have nothing else connected to my laptop. The ID corresponds to what I see when I compile/verify/upload through Arduino. I also noticed that the Auto button became active when I uploaded through Arduino. The Auto button does not become active when I directly use the Teensy Loader.
teensy2.JPG
teensy3.JPG
 
MikeEpicSolutions said:
I had this issue last week. I ended up going back to Arduino 1.6.8 and the compatible Teensyduino version.
Click to expand...

Thanks. I am currently using Arduino 1.8.2 and Teensyduino 1.36. If I roll back to Arduino 1.6.8, what version of Teensyduino would you recommend? Thanks for your help in advance.
 
Look, you're just wasting time & effort (and the time of people who read and try to help on this forum) trying different software when the problem is no USB communication between Teensy and your PC.

Open the Windows Device Manager. Then try pressing the button on Teensy, or plug and unplug the cable. When any USB device is plugged or unplugged, the device manager updates. Most Windows systems also make a sound when USB devices change (though this can be disabled on some systems). The question is whether your PC is seeing any USB device appear at all. Anything?!

If you're not getting any USB communication, not even Windows detecting a device is plugged and unplugged, no amount of trying different software will help.
 
PaulStoffregen said:
Look, you're just wasting time & effort (and the time of people who read and try to help on this forum) trying different software when the problem is no USB communication between Teensy and your PC.

Open the Windows Device Manager. Then try pressing the button on Teensy, or plug and unplug the cable. When any USB device is plugged or unplugged, the device manager updates. Most Windows systems also make a sound when USB devices change (though this can be disabled on some systems). The question is whether your PC is seeing any USB device appear at all. Anything?!

If you're not getting any USB communication, not even Windows detecting a device is plugged and unplugged, no amount of trying different software will help.
Click to expand...

Please note as I clearly mentioned in my response to you that I suspect it is a cable issue. To that end, I have purchased a board and cable directly from your company which I will be trying first. Any other advice that I have received from the forum is on the back burner if the new board / cable give the same problem. No, I do not plan on wasting the time of people who are reading and trying to help. I am acknowledging their help and thankful to get varying advice. I do not understand your derision to your customer on a public forum. I am sure you have had customers who have been new users of your product.
 
Elwopo66 said:
I have disconnected the teency years from any presoldered connections and there was no change. No light, nothing responding, nothing. I plugged in my pro trinket and had no issues programming the blink or any other program so I know it is not the cable.

Do you think it is the board now? I do not know what my next step is now, what do you recommend?

I have spent more time trying to program the teency then the entire project so you can understand my frustration.
Click to expand...

I'd try with a spare fresh Teensy to confirm all is well. If your cable is indeed good and you followed other programming tips here and elsewhere and not seen any sign of life then it may be trashed. There are notes around about checking for 3.3V on that pin when USB powered that shows base level functionality - there are other tests like RESET and PGM pins. This post doesn't say what Teensy ## is involved and what it was soldered to and removed from and when it last worked.

Post an update with details of what was treid and the results and perhaps a picture to show the state of it after being desoldered.
 
I received the cable and Teensy 3.2 from PJRC. Since I suspected that a bad cable was most likely the problem, I tried the new cable with the Teensy with soldered headers. It worked and I was able to program the board. Thanks to everyone for advice and help.
 
Rather than starting another thread, I am piggy-backing on this one...
I have a Teensy 3.2 (one of many) that will not program. It is detected when I plug it in (dmesg below) and the LED extinguishes when TeensyLoader (v1.40) tried to put the board into program mode.
I am using Arduino IDE 1.8.4.
I have tried a number of cables and done a full reboot, but other boards (Arduino Mega, Uno, NodeMCU) all program with no problem with the same computer & cables. I have tried a number of sketches, clock speeds & USB device types (Serial, Audio etc...) The actual code I am trying to upload uses USB Audio.

Any help appreciated.

/ Gerry

Output of Verbose Logs:

Code: 
16:14:28.841: Teensy Loader 1.40, begin program
16:14:28.854: Listening for remote control on port 3149
16:14:28.854: initialized, showing main window
16:14:28.877: remote connection opened
16:14:28.878: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:14:28.878: remote cmd: "status"
16:14:28.884: status data sent
16:14:28.921: remote cmd: "dir:/tmp/arduino_build_705147/"
16:14:28.921: remote cmd: "file:GI1MIC-DSP-Filter.ino.hex"
16:14:28.954: File "GI1MIC-DSP-Filter.ino.hex". 182940 bytes, 284% used
16:14:28.955: File contains data beyond chip size, yikes!
16:14:28.958: remote cmd: "status"
16:14:28.961: status data sent
16:14:29.000: remote cmd: "auto:on"
16:14:29.010: remote connection closed
16:14:29.035: remote connection opened
16:14:29.035: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:14:29.036: remote cmd: "status"
16:14:29.041: status data sent
16:14:29.090: remote connection closed
16:14:29.097: remote connection opened
16:14:29.098: remote cmd: "show:arduino_attempt_reboot"
16:14:29.098: got request to show arduino rebooting message
16:14:29.100: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_reboot)"
16:14:29.100: remote cmd: "status"
16:14:29.105: status data sent
16:14:29.145: remote cmd: "status"
16:14:29.148: status data sent
16:14:29.288: remote cmd: "status"
16:14:29.291: status data sent
16:14:29.391: remote cmd: "status"
16:14:29.394: status data sent
16:14:29.494: remote cmd: "status"
16:14:29.497: status data sent
16:14:29.597: remote cmd: "status"
16:14:29.600: status data sent
16:14:29.700: remote cmd: "status"
16:14:29.703: status data sent
16:14:29.803: remote cmd: "status"
16:14:29.806: status data sent
16:14:34.845: remote cmd: "status"
16:14:34.850: status data sent
16:14:34.950: remote cmd: "status"
16:14:34.953: status data sent
16:14:35.053: remote cmd: "status"
16:14:35.056: status data sent
16:14:35.156: remote cmd: "status"
16:14:35.159: status data sent
16:14:35.259: remote cmd: "status"
16:14:35.262: status data sent
16:14:35.362: remote cmd: "status"
16:14:35.366: status data sent
16:14:35.466: remote cmd: "status"
16:14:35.470: status data sent
16:14:35.570: remote cmd: "status"
16:14:35.573: status data sent
16:14:35.673: remote cmd: "status"
16:14:35.676: status data sent
16:14:35.776: remote cmd: "status"
16:14:35.779: status data sent
16:14:35.880: remote cmd: "status"
16:14:35.882: status data sent
16:14:35.983: remote cmd: "status"
16:14:35.985: status data sent
16:14:36.086: remote cmd: "status"
16:14:36.088: status data sent
16:14:36.189: remote cmd: "status"
16:14:36.191: status data sent
16:14:36.292: remote cmd: "status"
16:14:36.295: status data sent
16:14:36.396: remote cmd: "status"
16:14:36.399: status data sent
16:14:36.500: remote cmd: "status"
16:14:36.502: status data sent
16:14:36.603: remote cmd: "status"
16:14:36.605: status data sent
16:14:36.706: remote cmd: "status"
16:14:36.709: status data sent
16:14:36.809: remote cmd: "status"
16:14:36.812: status data sent
16:14:36.912: remote cmd: "status"
16:14:36.914: status data sent
16:14:37.015: remote cmd: "status"
16:14:37.019: status data sent
16:14:37.119: remote cmd: "status"
16:14:37.123: status data sent
16:14:37.223: remote cmd: "status"
16:14:37.226: status data sent
16:14:37.326: remote cmd: "status"
16:14:37.329: status data sent
16:14:37.429: remote cmd: "status"
16:14:37.432: status data sent
16:14:37.532: remote cmd: "status"
16:14:37.536: status data sent
16:14:37.636: remote cmd: "status"
16:14:37.639: status data sent
16:14:37.739: remote cmd: "status"
16:14:37.742: status data sent
16:14:37.842: remote cmd: "status"
16:14:37.845: status data sent
16:14:37.946: remote cmd: "status"
16:14:37.950: status data sent
16:14:38.050: remote cmd: "status"
16:14:38.054: status data sent
16:14:38.154: remote cmd: "status"
16:14:38.158: status data sent
16:14:38.258: remote cmd: "status"
16:14:38.261: status data sent
16:14:38.361: remote cmd: "status"
16:14:38.364: status data sent
16:14:38.464: remote cmd: "status"
16:14:38.467: status data sent
16:14:38.568: remote cmd: "status"
16:14:38.570: status data sent
16:14:38.671: remote cmd: "status"
16:14:38.674: status data sent
16:14:38.774: remote cmd: "status"
16:14:38.777: status data sent
16:14:38.877: remote cmd: "status"
16:14:38.880: status data sent
16:14:38.980: remote cmd: "status"
16:14:38.983: status data sent
16:14:39.084: remote cmd: "status"
16:14:39.088: status data sent
16:14:39.189: remote cmd: "status"
16:14:39.193: status data sent
16:14:39.303: remote connection closed
16:14:50.791: Auto Button event
16:14:50.791: Auto mode: disabled
16:14:56.657: file changed
16:14:56.693: File "GI1MIC-DSP-Filter.ino.hex". 182940 bytes, 284% used
16:14:56.693: File contains data beyond chip size, yikes!
16:14:56.839: remote connection opened
16:14:56.840: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:14:56.840: remote cmd: "status"
16:14:56.843: status data sent
16:14:56.880: remote cmd: "auto:on"
16:14:56.890: remote connection closed
16:14:56.901: remote connection opened
16:14:56.901: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:14:56.902: remote cmd: "status"
16:14:56.905: status data sent
16:14:56.954: remote connection closed
16:14:56.959: remote connection opened
16:14:56.959: remote cmd: "show:arduino_attempt_reboot"
16:14:56.959: got request to show arduino rebooting message
16:14:56.961: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_reboot)"
16:14:56.961: remote cmd: "status"
16:14:56.964: status data sent
16:14:57.000: remote cmd: "status"
16:14:57.003: status data sent
16:14:57.140: remote cmd: "status"
16:14:57.143: status data sent
16:14:57.243: remote cmd: "status"
16:14:57.246: status data sent
16:14:57.346: remote cmd: "status"
16:14:57.349: status data sent
16:14:57.449: remote cmd: "status"
16:14:57.452: status data sent
16:14:57.553: remote cmd: "status"
16:14:57.556: status data sent
16:14:57.656: remote cmd: "status"
16:14:57.659: status data sent
16:14:57.759: remote cmd: "status"
16:14:57.762: status data sent
16:14:57.862: remote cmd: "status"
16:14:57.865: status data sent
16:14:57.965: remote cmd: "status"
16:14:57.968: status data sent
16:14:58.068: remote cmd: "status"
16:14:58.071: status data sent
16:14:58.171: remote cmd: "status"
16:14:58.174: status data sent
16:14:58.274: remote cmd: "status"
16:14:58.277: status data sent
16:14:58.378: remote cmd: "status"
16:14:58.381: status data sent
16:14:58.481: remote cmd: "status"
16:14:58.484: status data sent
16:14:58.584: remote cmd: "status"
16:14:58.587: status data sent
16:14:58.687: remote cmd: "status"
16:14:58.690: status data sent
16:14:58.790: remote cmd: "status"
16:14:58.793: status data sent
16:14:58.893: remote cmd: "status"
16:14:58.895: status data sent
16:14:58.996: remote cmd: "status"
16:14:58.998: status data sent
16:14:59.099: remote cmd: "status"
16:14:59.101: status data sent
16:14:59.202: remote cmd: "status"
16:14:59.205: status data sent
16:14:59.305: remote cmd: "status"
16:14:59.308: status data sent
16:14:59.408: remote cmd: "status"
16:14:59.411: status data sent
16:14:59.511: remote cmd: "status"
16:14:59.513: status data sent
16:14:59.614: remote cmd: "status"
16:14:59.617: status data sent
16:14:59.718: remote cmd: "status"
16:14:59.721: status data sent
16:14:59.821: remote cmd: "status"
16:14:59.824: status data sent
16:14:59.924: remote cmd: "status"
16:14:59.927: status data sent
16:15:00.028: remote cmd: "status"
16:15:00.030: status data sent
16:15:00.131: remote cmd: "status"
16:15:00.134: status data sent
16:15:00.234: remote cmd: "status"
16:15:00.238: status data sent
16:15:00.338: remote cmd: "status"
16:15:00.341: status data sent
16:15:00.441: remote cmd: "status"
16:15:00.444: status data sent
16:15:00.544: remote cmd: "status"
16:15:00.548: status data sent
16:15:00.649: remote cmd: "status"
16:15:00.651: status data sent
16:15:00.752: remote cmd: "status"
16:15:00.755: status data sent
16:15:00.855: remote cmd: "status"
16:15:00.858: status data sent
16:15:00.958: remote cmd: "status"
16:15:00.961: status data sent
16:15:01.062: remote cmd: "status"
16:15:01.065: status data sent
16:15:01.165: remote cmd: "status"
16:15:01.168: status data sent
16:15:01.268: remote cmd: "status"
16:15:01.271: status data sent
16:15:01.371: remote cmd: "status"
16:15:01.374: status data sent
16:15:01.474: remote cmd: "status"
16:15:01.477: status data sent
16:15:01.577: remote cmd: "status"
16:15:01.581: status data sent
16:15:01.681: remote cmd: "status"
16:15:01.684: status data sent
16:15:01.784: remote cmd: "status"
16:15:01.787: status data sent
16:15:01.887: remote cmd: "status"
16:15:01.892: status data sent
16:15:01.992: remote cmd: "status"
16:15:01.995: status data sent
16:15:02.095: remote cmd: "status"
16:15:02.097: status data sent
16:15:02.208: remote connection closed
16:16:15.195: file changed
16:16:15.216: File "GI1MIC-DSP-Filter.ino.hex". 182940 bytes, 284% used
16:16:15.216: File contains data beyond chip size, yikes!
16:16:15.398: remote connection opened
16:16:15.399: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:16:15.399: remote cmd: "status"
16:16:15.402: status data sent
16:16:15.450: remote connection closed
16:16:15.456: remote connection opened
16:16:15.457: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:16:15.457: remote cmd: "status"
16:16:15.460: status data sent
16:16:15.510: remote connection closed
16:16:15.513: remote connection opened
16:16:15.514: remote cmd: "show:arduino_attempt_reboot"
16:16:15.514: got request to show arduino rebooting message
16:16:15.515: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_reboot)"
16:16:15.515: remote cmd: "status"
16:16:15.518: status data sent
16:16:15.556: remote cmd: "status"
16:16:15.559: status data sent
16:16:15.698: remote cmd: "status"
16:16:15.701: status data sent
16:16:15.801: remote cmd: "status"
16:16:15.804: status data sent
16:16:15.904: remote cmd: "status"
16:16:15.907: status data sent
16:16:16.007: remote cmd: "status"
16:16:16.010: status data sent
16:16:16.110: remote cmd: "status"
16:16:16.113: status data sent
16:16:16.214: remote cmd: "status"
16:16:16.217: status data sent
16:16:16.317: remote cmd: "status"
16:16:16.320: status data sent
16:16:16.420: remote cmd: "status"
16:16:16.423: status data sent
16:16:16.523: remote cmd: "status"
16:16:16.528: status data sent
16:16:16.628: remote cmd: "status"
16:16:16.631: status data sent
16:16:16.731: remote cmd: "status"
16:16:16.734: status data sent
16:16:16.834: remote cmd: "status"
16:16:16.842: status data sent
16:16:16.942: remote cmd: "status"
16:16:16.945: status data sent
16:16:17.045: remote cmd: "status"
16:16:17.048: status data sent
16:16:17.148: remote cmd: "status"
16:16:17.151: status data sent
16:16:17.251: remote cmd: "status"
16:16:17.254: status data sent
16:16:17.354: remote cmd: "status"
16:16:17.357: status data sent
16:16:17.457: remote cmd: "status"
16:16:17.461: status data sent
16:16:17.561: remote cmd: "status"
16:16:17.564: status data sent
16:16:17.664: remote cmd: "status"
16:16:17.667: status data sent
16:16:17.768: remote cmd: "status"
16:16:17.770: status data sent
16:16:17.870: remote cmd: "status"
16:16:17.873: status data sent
16:16:17.974: remote cmd: "status"
16:16:17.976: status data sent
16:16:18.077: remote cmd: "status"
16:16:18.080: status data sent
16:16:18.180: remote cmd: "status"
16:16:18.183: status data sent
16:16:18.283: remote cmd: "status"
16:16:18.286: status data sent
16:16:18.386: remote cmd: "status"
16:16:18.389: status data sent
16:16:18.489: remote cmd: "status"
16:16:18.493: status data sent
16:16:18.593: remote cmd: "status"
16:16:18.596: status data sent
16:16:18.696: remote cmd: "status"
16:16:18.699: status data sent
16:16:18.800: remote cmd: "status"
16:16:18.802: status data sent
16:16:18.903: remote cmd: "status"
16:16:18.905: status data sent
16:16:19.006: remote cmd: "status"
16:16:19.009: status data sent
16:16:19.109: remote cmd: "status"
16:16:19.112: status data sent
16:16:19.212: remote cmd: "status"
16:16:19.215: status data sent
16:16:19.315: remote cmd: "status"
16:16:19.318: status data sent
16:16:19.418: remote cmd: "status"
16:16:19.421: status data sent
16:16:19.521: remote cmd: "status"
16:16:19.524: status data sent
16:16:19.625: remote cmd: "status"
16:16:19.627: status data sent
16:16:19.728: remote cmd: "status"
16:16:19.730: status data sent
16:16:19.831: remote cmd: "status"
16:16:19.833: status data sent
16:16:19.933: remote cmd: "status"
16:16:19.937: status data sent
16:16:20.037: remote cmd: "status"
16:16:20.041: status data sent
16:16:20.141: remote cmd: "status"
16:16:20.144: status data sent
16:16:20.244: remote cmd: "status"
16:16:20.247: status data sent
16:16:20.347: remote cmd: "status"
16:16:20.350: status data sent
16:16:20.450: remote cmd: "status"
16:16:20.453: status data sent
16:16:20.553: remote cmd: "status"
16:16:20.556: status data sent
16:16:20.657: remote cmd: "status"
16:16:20.659: status data sent
16:16:20.770: remote connection closed
16:20:14.585: file changed
16:20:14.606: File "GI1MIC-DSP-Filter.ino.hex". 182940 bytes, 284% used
16:20:14.606: File contains data beyond chip size, yikes!
16:20:14.764: remote connection opened
16:20:14.764: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:20:14.764: remote cmd: "status"
16:20:14.767: status data sent
16:20:14.814: remote connection closed
16:20:14.822: remote connection opened
16:20:14.822: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:20:14.822: remote cmd: "status"
16:20:14.825: status data sent
16:20:14.874: remote connection closed
16:20:14.877: remote connection opened
16:20:14.878: remote cmd: "show:arduino_attempt_reboot"
16:20:14.878: got request to show arduino rebooting message
16:20:14.879: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_reboot)"
16:20:14.879: remote cmd: "status"
16:20:14.882: status data sent
16:20:14.920: remote cmd: "status"
16:20:14.922: status data sent
16:20:15.060: remote cmd: "status"
16:20:15.063: status data sent
16:20:15.163: remote cmd: "status"
16:20:15.166: status data sent
16:20:15.266: remote cmd: "status"
16:20:15.271: status data sent
16:20:15.371: remote cmd: "status"
16:20:15.374: status data sent
16:20:15.474: remote cmd: "status"
16:20:15.477: status data sent
16:20:15.578: remote cmd: "status"
16:20:15.580: status data sent
16:20:15.681: remote cmd: "status"
16:20:15.684: status data sent
16:20:15.784: remote cmd: "status"
16:20:15.787: status data sent
16:20:15.887: remote cmd: "status"
16:20:15.890: status data sent
16:20:15.990: remote cmd: "status"
16:20:15.993: status data sent
16:20:16.095: remote cmd: "status"
16:20:16.098: status data sent
16:20:16.198: remote cmd: "status"
16:20:16.201: status data sent
16:20:16.301: remote cmd: "status"
16:20:16.304: status data sent
16:20:16.404: remote cmd: "status"
16:20:16.407: status data sent
16:20:16.507: remote cmd: "status"
16:20:16.510: status data sent
16:20:16.610: remote cmd: "status"
16:20:16.613: status data sent
16:20:16.714: remote cmd: "status"
16:20:16.716: status data sent
16:20:16.816: remote cmd: "status"
16:20:16.821: status data sent
16:20:16.921: remote cmd: "status"
16:20:16.924: status data sent
16:20:17.024: remote cmd: "status"
16:20:17.027: status data sent
16:20:17.128: remote cmd: "status"
16:20:17.130: status data sent
16:20:17.231: remote cmd: "status"
16:20:17.236: status data sent
16:20:17.336: remote cmd: "status"
16:20:17.339: status data sent
16:20:17.439: remote cmd: "status"
16:20:17.442: status data sent
16:20:17.543: remote cmd: "status"
16:20:17.546: status data sent
16:20:17.646: remote cmd: "status"
16:20:17.649: status data sent
16:20:17.750: remote cmd: "status"
16:20:17.753: status data sent
16:20:17.853: remote cmd: "status"
16:20:17.857: status data sent
16:20:17.957: remote cmd: "status"
16:20:17.960: status data sent
16:20:18.061: remote cmd: "status"
16:20:18.063: status data sent
16:20:18.163: remote cmd: "status"
16:20:18.166: status data sent
16:20:18.267: remote cmd: "status"
16:20:18.272: status data sent
16:20:18.372: remote cmd: "status"
16:20:18.375: status data sent
16:20:18.475: remote cmd: "status"
16:20:18.478: status data sent
16:20:18.578: remote cmd: "status"
16:20:18.581: status data sent
16:20:18.681: remote cmd: "status"
16:20:18.684: status data sent
16:20:18.785: remote cmd: "status"
16:20:18.787: status data sent
16:20:18.888: remote cmd: "status"
16:20:18.890: status data sent
16:20:18.991: remote cmd: "status"
16:20:18.993: status data sent
16:20:19.094: remote cmd: "status"
16:20:19.097: status data sent
16:20:19.197: remote cmd: "status"
16:20:19.199: status data sent
16:20:19.300: remote cmd: "status"
16:20:19.305: status data sent
16:20:19.405: remote cmd: "status"
16:20:19.413: status data sent
16:20:19.513: remote cmd: "status"
16:20:19.518: status data sent
16:20:19.618: remote cmd: "status"
16:20:19.621: status data sent
16:20:19.721: remote cmd: "status"
16:20:19.724: status data sent
16:20:19.824: remote cmd: "status"
16:20:19.827: status data sent
16:20:19.927: remote cmd: "status"
16:20:19.930: status data sent
16:20:20.031: remote cmd: "status"
16:20:20.035: status data sent
16:20:20.146: remote connection closed
16:20:58.499: file changed
16:20:58.525: File "GI1MIC-DSP-Filter.ino.hex". 182940 bytes, 284% used
16:20:58.525: File contains data beyond chip size, yikes!
16:20:58.668: remote connection opened
16:20:58.668: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:20:58.669: remote cmd: "status"
16:20:58.671: status data sent
16:20:58.718: remote connection closed
16:20:58.726: remote connection opened
16:20:58.726: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_post_compile)"
16:20:58.727: remote cmd: "status"
16:20:58.730: status data sent
16:20:58.778: remote connection closed
16:20:58.783: remote connection opened
16:20:58.783: remote cmd: "show:arduino_attempt_reboot"
16:20:58.783: got request to show arduino rebooting message
16:20:58.785: remote cmd: "comment: Teensyduino 1.40 - LINUX64 (teensy_reboot)"
16:20:58.786: remote cmd: "status"
16:20:58.789: status data sent
16:20:58.829: remote cmd: "status"
16:20:58.832: status data sent
16:20:58.972: remote cmd: "status"
16:20:58.975: status data sent
16:20:59.075: remote cmd: "status"
16:20:59.078: status data sent
16:20:59.178: remote cmd: "status"
16:20:59.181: status data sent
16:20:59.281: remote cmd: "status"
16:20:59.283: status data sent
16:20:59.384: remote cmd: "status"
16:20:59.386: status data sent
16:20:59.486: remote cmd: "status"
16:20:59.492: status data sent
16:20:59.592: remote cmd: "status"
16:21:04.520: status data sent
16:21:04.622: remote cmd: "status"
16:21:04.625: status data sent
16:21:04.726: remote cmd: "status"
16:21:04.729: status data sent
16:21:04.829: remote cmd: "status"
16:21:04.832: status data sent
16:21:04.932: remote cmd: "status"
16:21:04.935: status data sent
16:21:05.035: remote cmd: "status"
16:21:05.038: status data sent
16:21:05.138: remote cmd: "status"
16:21:05.141: status data sent
16:21:05.241: remote cmd: "status"
16:21:05.244: status data sent
16:21:05.344: remote cmd: "status"
16:21:05.347: status data sent
16:21:05.447: remote cmd: "status"
16:21:05.450: status data sent
16:21:05.551: remote cmd: "status"
16:21:05.553: status data sent
16:21:05.654: remote cmd: "status"
16:21:05.657: status data sent
16:21:05.757: remote cmd: "status"
16:21:05.760: status data sent
16:21:05.860: remote cmd: "status"
16:21:05.863: status data sent
16:21:05.963: remote cmd: "status"
16:21:05.966: status data sent
16:21:06.066: remote cmd: "status"
16:21:06.069: status data sent
16:21:06.169: remote cmd: "status"
16:21:06.172: status data sent
16:21:06.275: remote cmd: "status"
16:21:06.277: status data sent
16:21:06.378: remote cmd: "status"
16:21:06.380: status data sent
16:21:06.481: remote cmd: "status"
16:21:06.483: status data sent
16:21:06.584: remote cmd: "status"
16:21:06.586: status data sent
16:21:06.687: remote cmd: "status"
16:21:06.689: status data sent
16:21:06.790: remote cmd: "status"
16:21:06.792: status data sent
16:21:06.893: remote cmd: "status"
16:21:06.895: status data sent
16:21:06.996: remote cmd: "status"
16:21:06.998: status data sent
16:21:07.099: remote cmd: "status"
16:21:07.101: status data sent
16:21:07.202: remote cmd: "status"
16:21:07.204: status data sent
16:21:07.305: remote cmd: "status"
16:21:07.307: status data sent
16:21:07.407: remote cmd: "status"
16:21:07.410: status data sent
16:21:07.510: remote cmd: "status"
16:21:07.513: status data sent
16:21:07.613: remote cmd: "status"
16:21:07.616: status data sent
16:21:07.717: remote cmd: "status"
16:21:07.719: status data sent
16:21:07.820: remote cmd: "status"
16:21:07.822: status data sent
16:21:07.923: remote cmd: "status"
16:21:07.925: status data sent
16:21:08.026: remote cmd: "status"
16:21:08.028: status data sent
16:21:08.129: remote cmd: "status"
16:21:08.132: status data sent
16:21:08.232: remote cmd: "status"
16:21:08.235: status data sent
16:21:08.335: remote cmd: "status"
16:21:08.338: status data sent
16:21:08.438: remote cmd: "status"
16:21:08.441: status data sent
16:21:08.541: remote cmd: "status"
16:21:08.544: status data sent
16:21:08.644: remote cmd: "status"
16:21:08.647: status data sent
16:21:08.747: remote cmd: "status"
16:21:08.750: status data sent
16:21:08.850: remote cmd: "status"
16:21:08.854: status data sent
16:21:08.964: remote connection closed
16:27:28.002: Verbose Info event

DMESG

Code: 
[  237.567616] cdc_acm 3-3:1.0: ttyACM0: USB ACM device
[  237.568104] usbcore: registered new interface driver cdc_acm
[  237.568107] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[  369.428897] usb 3-3: USB disconnect, device number 11
[  369.796804] usb 3-3: new full-speed USB device number 12 using xhci_hcd
[  369.925242] usb 3-3: New USB device found, idVendor=16c0, idProduct=0478
[  369.925246] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[  369.925248] usb 3-3: SerialNumber: 0000AECD
[  374.925441] hid-generic 0003:16C0:0478.0008: hidraw5: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:14.0-3/input0
[  383.138051] usb 3-4.2: 2:1: cannot get freq at ep 0x1
[  398.580243] usb 3-3: USB disconnect, device number 12
[  398.981862] usb 3-3: new full-speed USB device number 13 using xhci_hcd
[  399.110661] usb 3-3: New USB device found, idVendor=16c0, idProduct=0478
[  399.110664] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[  399.110666] usb 3-3: SerialNumber: 0000AECD
[  399.111903] hid-generic 0003:16C0:0478.0009: hidraw5: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:14.0-3/input0
[  647.375258] usb 3-3: USB disconnect, device number 13
[  652.235751] usb 3-3: new full-speed USB device number 14 using xhci_hcd
[  652.399823] usb 3-3: Device not responding to setup address.
[  652.603782] usb 3-3: Device not responding to setup address.
[  652.807792] usb 3-3: device not accepting address 14, error -71
[  653.179795] usb 3-3: new full-speed USB device number 15 using xhci_hcd
[  653.308452] usb 3-3: New USB device found, idVendor=16c0, idProduct=0478
[  653.308455] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[  653.308456] usb 3-3: SerialNumber: 0000AECD
[  653.309769] hid-generic 0003:16C0:0478.000A: hidraw5: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:14.0-3/input0
[  709.699625] usb 3-4.2: 2:1: cannot get freq at ep 0x1
[  723.857887] usb 3-3: USB disconnect, device number 15
[  726.146629] usb 3-3: new full-speed USB device number 16 using xhci_hcd
[  726.275408] usb 3-3: New USB device found, idVendor=16c0, idProduct=0483
[  726.275412] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  726.275414] usb 3-3: Product: USB Serial
[  726.275416] usb 3-3: Manufacturer: Teensyduino
[  726.275417] usb 3-3: SerialNumber: 447490
[  726.276109] cdc_acm 3-3:1.0: ttyACM0: USB ACM device
[  759.120082] usb 3-3: USB disconnect, device number 16
[  759.487918] usb 3-3: new full-speed USB device number 17 using xhci_hcd
[  759.620454] usb 3-3: New USB device found, idVendor=16c0, idProduct=0478
[  759.620457] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[  759.620458] usb 3-3: SerialNumber: 0000AECD
[  764.620429] hid-generic 0003:16C0:0478.000B: hidraw5: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:14.0-3/input0

Error output:

Code: 
Arduino: 1.8.4 (Linux), TD: 1.40, Board: "Teensy 3.2 / 3.1, Audio, 96 MHz (overclock), Faster, US English"

Sketch uses 11112 bytes (4%) of program storage space. Maximum is 262144 bytes.
Global variables use 4588 bytes (7%) of dynamic memory, leaving 60948 bytes for local variables. Maximum is 65536 bytes.
Teensy did not respond to a USB-based request to enter program mode.
Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.
An error occurred while uploading the sketch

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
 
Last edited:
gerryk said:
Rather than starting another thread, I am piggy-backing on this one...
I have a Teensy 3.2 (one of many) that will not program. It is detected when I plug it in (dmesg below) and the LED extinguishes when TeensyLoader (v1.40) tried to put the board into program mode.
I am using Arduino IDE 1.8.4.
I have tried a number of cables and done a full reboot, but other boards (Arduino Mega, Uno, NodeMCU) all program with no problem with the same computer & cables. I have tried a number of sketches, clock speeds & USB device types (Serial, Audio etc...) The actual code I am trying to upload uses USB Audio.

Any help appreciated.

/ Gerry
Click to expand...

Only to double check
you compiled with USB type Serial-Midi-Audio, right?
 
Is this a new Teensy?

Did you try to program it with something like blink? That is:
Load simple example blink sketch. Make sure IDE set to your 3.2 and USB type = Serial
Now click the verify button in the IDE. It should compile and bring up the Teensy loader program. Now press the program button on your 3.2. Does it now program the chip?

If that works, then load your program make sure you have the USB type set correctly and try to do upload.
 
I tried on another computer with pretty much identical configuration and it worked... odd.
Thanks for the suggestions!
 
I'd really like to know why it didn't work on the 1st computer. The dmesg info in message #66 looks like Teensy is working properly, and you had Tools > USB Type in Arduino set to Serial (the default).

Is there any chance the udev rules weren't installed correctly? The check, you'd type "ls -l /dev/ttyACM*". You should see this:

Code: 
crw-rw-rw- 1 root dialout 166, 0 Jan 15 12:57 /dev/ttyACM0

If the permissions are not "rw-rw-rw-", that's a sure sign the udev rules are not installed. This is by far the most common issue with Linux systems, and really the only explanation I can imagine, given the correct responses from the kernel in the dmesg info.
 
The port exists with the following perms...

Code: 
crw-rw---- 1 root dialout 166, 0 Jan 16 10:00 /dev/ttyACM0

My user is a member of dialout however, so I would have thought world r/w was not necessary.
 
"rw-rw----" is a sure sign the udev rules file is not installed.

See step #2 on the download page.

https://www.pjrc.com/teensy/td_download.html

When you get the udev rules file in place, just unplug and reconnect the USB cable. Then you'll see the permissions become "rw-rw-rw-".

Most Linux distros have file change monitoring on the udev directory. So all that's needed it to put the file in that directory, and then unplug and reconnect the cable. No reboot or restarting any system service is supposed to be needed.
 
gerryk said:
My user is a member of dialout however, so I would have thought world r/w was not necessary.
Click to expand...

The udev rule does more than merely the permissions on this serial device. It also allows permissions on usbfs device nodes (used for non-serial access), and it tells the pesky Gnome Modem Manager to not interfere.

You *do* need the udev rule, even if you're a member of "dailout".
 
Status
Not open for further replies.
Back
Top