not able to upload sketches anymore to teensy 3.0

[hcgilje]

I have been using the teensy 3s on macs for 8 months, running arduino 103 and teensy 1.16, without any problems. Today I was not able to update teensies I used just a few weeks back, it just seems to shut down when trying to reset it and next time I boot up the old sketch is still running.

I thought this might be related to a bug which was fixed in 1.18:
"#2: Teensy 3.0 would become unresponsive on Macintosh computers after 3 to 20 uploads, due to failure to send a USB NAK response in certain circumstances. Linux and Windows were not affected by this issue."
http://forum.pjrc.com/threads/25126-...ghlight=sketch

So I updated to arduino 105 and teensy 1.18 but still no luck.

I am using Mavericks.

This is the output from the verbose window in teensy:

first, verify + reset button:

18:13:12: Teensy Loader 1.18, begin program
18:13:12: File "mobillinjetest03_frognerseteren_newlib.cpp.he x". 16084 bytes, 12% used
18:13:12: Listening for remote control on port 3149
18:13:12: initialized, showing main window
18:13:12: remote connection opened
18:13:12: remote cmd: "comment: Teensyduino 1.18 - MACOSX"
18:13:12: remote cmd: "dir:/var/folders/9b/lyp7_7x572s003brb2vx1r3h0000gq/T/build7718291686599349613.tmp/"
18:13:12: remote cmd: "file:mobillinjetest03_frognerseteren_newlib.cpp.h ex"
18:13:12: File "mobillinjetest03_frognerseteren_newlib.cpp.he x". 16084 bytes, 12% used
18:13:12: remote cmd: "status"
18:13:12: status data sent
18:13:12: remote cmd: "auto: on"
18:13:12: remote connection closed
18:13:12: HID/macos: no devices found

then clicking directly on the upload button in arduino:
18:13:29: Verbose Info event
18:13:49: remote connection opened
18:13:49: remote cmd: "comment: Teensyduino 1.18 - MACOSX"
18:13:49: remote cmd: "dir:/var/folders/9b/lyp7_7x572s003brb2vx1r3h0000gq/T/build7718291686599349613.tmp/"
18:13:49: remote cmd: "file:mobillinjetest03_frognerseteren_newlib.cpp.h ex"
18:13:49: File "mobillinjetest03_frognerseteren_newlib.cpp.he x". 16084 bytes, 12% used
18:13:49: remote cmd: "status"
18:13:49: status data sent
18:13:49: remote connection closed
18:13:49: remote connection opened
18:13:49: remote cmd: "status"
18:13:49: status data sent
18:13:49: remote cmd: "status"
18:13:49: status data sent
18:13:49: remote cmd: "status"
18:13:49: status data sent
18:13:49: remote cmd: "status"
18:13:49: status data sent
18:13:49: remote cmd: "status"
18:13:49: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:50: remote cmd: "status"
18:13:50: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:51: remote cmd: "status"
18:13:51: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:52: remote cmd: "status"
18:13:52: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:53: remote cmd: "status"
18:13:53: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote cmd: "status"
18:13:54: status data sent
18:13:54: remote connection closed

[PaulStoffregen]

First, physically unplug Teensy and reboot your Mac.

Then with Teensy Loader running, turn off auto mode (if it's on), plug it back in, and press the button on Teensy. Does Teensy Loader recognize it? Or can you see if on the System Profiler (aka "About this mac" and then "more info")?

[hcgilje]

First, physically unplug Teensy and reboot your Mac.

Then with Teensy Loader running, turn off auto mode (if it's on), plug it back in, and press the button on Teensy. Does Teensy Loader recognize it? Or can you see if on the System Profiler (aka "About this mac" and then "more info")?

thank you for the quick reply and troubleshooting tips!
It turned out the micro usb cable I was using now was not a proper cable, only for charging it seems. Anyway I found a working cable, so now it´s back to work!

best,
hc