Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 14 of 14

Thread: Teensy 3.1 is not recognized under Mac OS X - Yosemite (10.10)

  1. #1
    Junior Member
    Join Date
    Sep 2014
    Location
    Paris
    Posts
    19

    Teensy 3.1 is not recognized under Mac OS X - Yosemite (10.10)

    Hi All,

    Since I've updated my laptop under OS X - Yosemite, my Teensy is not longer recognized.
    If you don't want to loose some time ;-)

    Bruno.

  2. #2
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,776
    Does any USB device appear in the system profiler when you plug in Teensy?

  3. #3
    Junior Member
    Join Date
    Sep 2014
    Location
    Paris
    Posts
    19
    Hi,

    No Teensy appears as you can see. I've tried with my second Teensy but it's the same: nothing
    I've also change the cable to see if something change but no.

    Click image for larger version. 

Name:	Capture d’écran 2014-10-24 à 13.17.01.png 
Views:	252 
Size:	67.8 KB 
ID:	2832

    Bruno

  4. #4
    Junior Member
    Join Date
    Sep 2014
    Location
    Paris
    Posts
    19
    Hi,

    No Teensy appears as you can see. I've tried with my second Teensy but it's the same: nothing
    Sorry this screen shot is in french.

    Click image for larger version. 

Name:	Capture d’écran 2014-10-24 à 13.17.01.png 
Views:	252 
Size:	67.8 KB 
ID:	2832

    Bruno

  5. #5
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,776
    Can your mac see it if you plug Teensy into a USB hub, and then plug the hub into your Mac?

  6. #6
    Senior Member
    Join Date
    Feb 2013
    Posts
    179
    I'll pipe up and ask if you've hit command-R to refresh the system report after plugging the teensy in? If you had system report open before plugging it in, I don't think it'll recognize it until you refresh the list.

  7. #7
    Junior Member
    Join Date
    Jan 2013
    Posts
    13
    I too am having this problem in Yosemite. Just installed the FTDI drivers just to be sure. I don't see my Teensy 3.1 in the serial devices list on Arduino or ls /dev/tty.* but when I compile/upload in Arduino, the Teensy Loader app somehow magically makes it appear as a serial device until I unplug/replug it.

    Paul, any ideas?

    IOUSBFamily doesn't like it when I plug in. I get this in the console:

    10/26/14 4:01:36.000 PM kernel[0]: USBF: 409.598 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:36.000 PM kernel[0]: USBF: 409.898 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:37.000 PM kernel[0]: USBF: 410.453 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:37.000 PM kernel[0]: USBF: 410.754 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:38.000 PM kernel[0]: USBF: 411.310 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:38.000 PM kernel[0]: USBF: 411.611 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:39.000 PM kernel[0]: USBF: 412.165 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:39.000 PM kernel[0]: USBF: 412.687 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:40.000 PM kernel[0]: USBF: 413.542 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:40.000 PM kernel[0]: USBF: 413.843 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:41.000 PM kernel[0]: USBF: 414.398 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:41.000 PM kernel[0]: USBF: 414.698 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:42.000 PM kernel[0]: USBF: 415.253 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:42.000 PM kernel[0]: USBF: 415.554 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:43.000 PM kernel[0]: USBF: 416.107 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:43.000 PM kernel[0]: USBF: 417. 29 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:44.000 PM kernel[0]: USBF: 417.884 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:45.000 PM kernel[0]: USBF: 418.184 The IOUSBFamily was not able to enumerate a device.
    10/26/14 4:01:45.000 PM kernel[0]: USBF: 418.738 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:45.000 PM kernel[0]: USBF: 418.738 The IOUSBFamily gave up enumerating a USB device after 10 retries. (Port 1 of Hub at 0x14000000)
    10/26/14 4:01:45.000 PM kernel[0]: USBF: 418.738 The IOUSBFamily was not able to enumerate a device.

  8. #8
    Junior Member
    Join Date
    Jan 2013
    Posts
    13
    After Teensy Loader does it's thing, this gets printed in Console:

    10/26/14 4:13:12.000 PM kernel[0]: USB (XHCI Root Hub USB 2.0 Simulation):Port 2 on bus 0xa connected or disconnected: portSC(0xe0206e1)
    10/26/14 4:13:14.000 PM kernel[0]: AppleUSBCDCACMData: Version number - 4.2.2b5, Input buffers 8, Output buffers 16
    10/26/14 4:13:14.000 PM kernel[0]: AppleUSBCDC: Version number - 4.2.2b5

  9. #9
    Junior Member
    Join Date
    Dec 2014
    Posts
    1
    Any update to this, i'm hitting the same issue here :/

  10. #10
    Junior Member
    Join Date
    Nov 2014
    Posts
    4
    Hi Paul and the team,

    I have a few Teensy 3.1 that I'm playing with and I've spotted a pattern.
    The "older" board that I've been using to develop my code with reports in "System Report" as a s"USB Serial" ... notice that the Product ID is 0x0483
    Name:  Oldboard.jpg
Views: 1258
Size:  20.2 KB

    The "newer" ones that I have are reporting as "Teensy RawHID" and the Product ID of these are all 0x0486:
    Name:  Newboard.jpg
Views: 1258
Size:  22.1 KB

    After going through the rest of the boards to confirm this, I've also found a DoA board - Paul any chance you could help out?

    But more pressing, is there a set of steps to be able to get the 0486 mod'd boards to come up as a serial port ?

    Thanks,

    Anthony

  11. #11
    Junior Member
    Join Date
    Nov 2014
    Posts
    4
    Ok, some more poking and I've made some progress:

    1) from the IDE, choose "Tools" -> "USB Type" -> Raw HID

    2) Compile and upload the code, the Teensyloader sparks up and loads the code.

    3) Again, click "Tools" -> "USB Type" -> "Serial"

    4) Then "Tools" -> "Serial Port" and the Teensy should be there ready for use.

    So far so good (apart from the DoA unit)

    -Anthony

  12. #12
    Junior Member
    Join Date
    Nov 2014
    Posts
    4
    Oh yes: the product ID is back to 0x0483...

  13. #13
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,776
    Yes, that's what it's supposed to do. The Product ID changes, depending on which option to choose in Tools > USB Type. Of course, it only shows up as a serial device after you've programmed it with one of the options with "Serial". The others don't implement Serial, so MacOS won't detect them as serial ports or modems.

    Please email me directly about the DOA board, paul at pjrc dot com. Please include a link to this thread in your email, and info about the purchase (eg, order number or other info we can use the look up the order).

  14. #14
    I had the same issue. In my case it was a "cheap" flat-band cable.

    I then used a seemingly more shielded version and it worked instantly.

    So try at least 3 different cables when in doubt.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •