Teensy 3 connected on RPi - no serial device available

Status
Not open for further replies.

michu

Member
Hey

I tried to connect my Teensy 3 on the RPi... however no device pops up on the RPi. Any hints how to resolve this? here are some details:

Code:
uname:
Linux pixelmonster 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux

Dmesg:
[    2.708902] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[    2.827502] usb 1-1.3: New USB device found, idVendor=16c0, idProduct=0483
[    2.838701] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.843362] usb 1-1.3: Product: USB Serial
[    2.847832] usb 1-1.3: Manufacturer: Teensyduino
[    2.867479] usb 1-1.3: SerialNumber: 5788

lsusb -v:
Bus 001 Device 005: ID 16c0:0483 VOTI Teensyduino Serial
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x16c0 VOTI
  idProduct          0x0483 Teensyduino Serial
  bcdDevice            1.00
  iManufacturer           1 Teensyduino
  iProduct                2 USB Serial
  iSerial                 3 5788
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x01
          call management
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x06
          sends break
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              64
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
 
Maybe the kernel doesn't have the cdc_acm driver? It's certainly able to see the device from "lsusb -v".

Try looking at syslog (on Ubuntu it's /var/log/syslog... so start there, but RPi might log is somewhere else). The syslog messages should show kernel info about detecting devices and loading drivers. There's also some way to find out what drivers the kernel has, but I'm not sure how to do that. Maybe someone else knows, or you can find by searching? The driver you need is cdc_acm.
 
thanks paul, yes a "sudo modprobe cdc_acm" resolved this issue... maybe I should take a nap!

cheers
 
Status
Not open for further replies.
Back
Top