3.2 on Mac programming issues.

Status
Not open for further replies.
jim lee

jim lee

Well-known member
Just bought a Teensy 3.2 from Adafruit. runnung Arduino IDE 1.8.0 and did an install from the teensy installer found here.

I see that the IDE has the 3.2 selected but what programmer do we select?

And I've not had any luck choosing them at random..

Code: 
17:56:11.937: Teensy Loader 1.34, begin program
17:56:11.975: File "Blink.ino.hex". 14208 bytes, 22% used
17:56:11.978: Listening for remote control on port 3149
17:56:11.978: initialized, showing main window
17:56:12.014: remote connection opened
17:56:12.015: remote cmd: "comment: Teensyduino 1.34 - MACOSX (teensy_post_compile)"
17:56:12.016: remote cmd: "status"
17:56:12.016: status data sent
17:56:12.017: remote cmd: "auto:on"
17:56:12.029: remote connection closed
17:56:12.061: remote connection opened
17:56:12.061: remote cmd: "comment: Teensyduino 1.34 - MACOSX (teensy_post_compile)"
17:56:12.062: remote cmd: "status"
17:56:12.063: status data sent
17:56:12.074: remote connection closed
17:56:12.078: remote connection opened
17:56:12.079: remote cmd: "comment: Teensyduino 1.34 - MACOSX (teensy_reboot)"
17:56:12.080: remote cmd: "status"
17:56:12.081: status data sent
17:56:12.081: remote cmd: "status"
17:56:12.082: status data sent
17:56:12.183: remote cmd: "status"
17:56:12.184: status data sent
17:56:12.228: HID/macos: no devices found
17:56:12.284: remote cmd: "status"
17:56:12.285: status data sent
17:56:12.386: remote cmd: "status"
17:56:12.387: status data sent
17:56:12.488: remote cmd: "status"
17:56:12.489: status data sent
17:56:12.590: remote cmd: "status"
17:56:12.590: status data sent
17:56:12.691: remote cmd: "status"
17:56:12.692: status data sent
17:56:12.793: remote cmd: "status"
17:56:12.794: status data sent
17:56:12.895: remote cmd: "status"
17:56:12.896: status data sent
17:56:12.997: remote cmd: "status"
17:56:12.998: status data sent
17:56:13.099: remote cmd: "status"
17:56:13.100: status data sent
17:56:13.201: remote cmd: "status"
17:56:13.202: status data sent
17:56:13.303: remote cmd: "status"
17:56:13.304: status data sent
17:56:13.405: remote cmd: "status"
17:56:13.405: status data sent
17:56:13.507: remote cmd: "status"
17:56:13.508: status data sent
17:56:13.609: remote cmd: "status"
17:56:13.610: status data sent
17:56:13.711: remote cmd: "status"
17:56:13.712: status data sent
17:56:13.813: remote cmd: "status"
17:56:13.814: status data sent
17:56:13.915: remote cmd: "status"
17:56:13.916: status data sent
17:56:14.017: remote cmd: "status"
17:56:14.018: status data sent
17:56:14.119: remote cmd: "status"
17:56:14.120: status data sent
17:56:14.154: Auto Button event
17:56:14.155: Auto mode: disabled
17:56:14.221: remote cmd: "status"
17:56:14.222: status data sent
17:56:14.323: remote cmd: "status"
17:56:14.324: status data sent
17:56:14.425: remote cmd: "status"
17:56:14.426: status data sent
17:56:14.528: remote cmd: "status"
17:56:14.528: status data sent
17:56:14.630: remote cmd: "status"
17:56:14.630: status data sent
17:56:14.732: remote cmd: "status"
17:56:14.732: status data sent
17:56:14.834: remote cmd: "status"
17:56:14.834: status data sent
17:56:14.936: remote cmd: "status"
17:56:14.936: status data sent
17:56:15.037: remote cmd: "status"
17:56:15.038: status data sent
17:56:15.139: remote cmd: "status"
17:56:15.140: status data sent
17:56:15.240: remote cmd: "status"
17:56:15.241: status data sent
17:56:15.343: remote cmd: "status"
17:56:15.343: status data sent
17:56:15.445: remote cmd: "status"
17:56:15.445: status data sent
17:56:15.547: remote cmd: "status"
17:56:15.547: status data sent
17:56:15.649: remote cmd: "status"
17:56:15.649: status data sent
17:56:15.751: remote cmd: "status"
17:56:15.751: status data sent
17:56:15.853: remote cmd: "status"
17:56:15.854: status data sent
17:56:15.955: remote cmd: "status"
17:56:15.956: status data sent
17:56:16.057: remote cmd: "status"
17:56:16.058: status data sent
17:56:16.159: remote cmd: "status"
17:56:16.160: status data sent
17:56:16.261: remote cmd: "status"
17:56:16.261: status data sent
17:56:16.363: remote cmd: "status"
17:56:16.363: status data sent
17:56:16.465: remote cmd: "status"
17:56:16.465: status data sent
17:56:16.567: remote cmd: "status"
17:56:16.568: status data sent
17:56:16.669: remote cmd: "status"
17:56:16.670: status data sent
17:56:16.771: remote cmd: "status"
17:56:16.772: status data sent
17:56:16.873: remote cmd: "status"
17:56:16.874: status data sent
17:56:16.975: remote cmd: "status"
17:56:16.976: status data sent
17:56:17.078: remote cmd: "status"
17:56:17.078: status data sent
17:56:17.191: remote connection closed
17:56:24.760: Verbose Info event


Help?

THanks!

-jim lee
 
If this is a brand new 3.2 that you have not programmed yet.

Once you have Teensyduino installed, which looks like you have done.

Plug the Teensy in.

Then choose Teensy 3.2 as the board type USB type of Serial. Now load up a simple program like blink, and use the verify command. When the compile completes, Teensy Loader app should be launched. Once it is launched, press the program button on the Teensy and you should see the Teensy loader app, download the program to your teensy, and once that completes, a Serial port should be available in the Port menu. After your first program of the Teensy, you should then be able to have the board automatically programmed when you use the Upload command in the Arduino IDE.
 
You don't need to select a programmer in Arduino, or even a port. Teensy Loader does everything automatically using HID protocol (not serial, as regular Arduino).

Perhaps you've got a charge-only USB cable. Many of the cables sold with cell phones have only 2 wires for power and no wires for data.
 
OK, used KurtE's directions it worked on my home laptop. That is just a bizzarre method. I'd never been able to figure that out on my own.

Thanks millions!
 
Ok, my home laptop works fine. Its a newer machine running latest or close to it OSx. The work/shop computer is giving me fits. Its running OSx 10.8.5 I installed a new Arduino and re-run the teensy installer again, as far as I can tell exactly like the home laptop and.. Nothing. Well not nothing. The code compiles and outputs a hex file as it should. The teensy app sees the hex file but no one seems to be able to "see" the poor little teensy 3.2 hanging on the USB cable. (Same cable I use for programming stuff every day.) I noticed the home computer when running the Arduino stuff I could see the teensy listed on the port choices. On this machine I don't. If I plug in a Uno, it will show up as a choice.

Any thing I can try? Besides attempting to update my entire OS over my cellphone?

-jim lee
 
did you initially try pushing the teensy button for the first time on the mac for programming? if not, try that. After that, it'll be automatic, as Kurt explained to you and as showed in the last page of teensyduino installer.
 
JUST to make sure..

I rebooted the Mac
Reinstalled the teensy stuff.
Grabbed a fresh UNOPENED teensy
plugged in the new teensy. (It started blinking as it should)
Set the IDE to teensy 3.2
USB type of Serial
Grabbed "blink".
compiled it with the checkmark
Saw that that teensy loader came alive telling me to press the button.
pressed it, the blnking stopped and..

nothing.

Solder irons, parts & wire are here, programming machine is at home..

Grr...

Oh well..

-jim lee
 
no, pressing the button puts it in programming mode thats why the led stopped, try to upload now....
 
Code: 
Sketch uses 14212 bytes (5%) of program storage space. Maximum is 262144 bytes.
Global variables use 3544 bytes (5%) of dynamic memory, leaving 61992 bytes for local variables. Maximum is 65536 bytes.
Teensy did not respond to a USB-based request to automatically reboot.
Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.
 
I fear I'm going to have to lug this giant thing home and update the OSX to whatever the zippiest thing is today. As far as I can tell, that's the biggest difference between the two Macs. And I'm running out of ideas.

-jim lee
 
have you tried rebooting the mac since thekernal drivers for arduino&teensy were installed? maybe they need to be initialized. When i played with hackintoshes, usually a reboot will initialize the drivers..
 
It does, but I program lots of ProTrinkets with that cable.

I'll bring the working cable from home today just to be pedantic.

-jim lee
 
Cable, I'm once again completly flummoxed. The cable I use for programming ALL my TinketPros, won't program my Teensy! First I tried the work cable with everything else USB unplugged from the computer. Just in case something was cross talking or who knows what. Nothing. So I swapped out to the cable I've been using at home. Presto! Works wonderful.

And there you have it. Just because it can program other stuff doesn't mean it'll program a Teensy.

Go figure!

So, thank you everyone for all your help! I really appreciate it.

-jim lee
 
think of it like those cheap chinese iphone cables, they supply power, but wont charge, sometimes work, sometimes not.
 
Any chance you could send that USB cable to me? I'd really like to figure out why it works with Trinket but not Teensy.

Have you tried that cable with other non-Trinket USB devices?
 
Let me re-try it tomorrow and make sure it still does the trinkets. AND Won't do the Teensys. If it still checks out, I'll send it to you. I'm thinking maybe it broke between times?

I don't think I've used it with anything else..

-jim lee
 
Status
Not open for further replies.
Back
Top