• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 915 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

usb keyboard support on dm6446

may vilaiphanh
Prodigy 10 points

All,

Our dm6446 platform has external HUB with 3 usb ports running on kernel 2.6.30.  When plugged in usb keyboard alone, I always see the "usb 1-1.2:reset low speed USB device using musb_hdrc ...."  message running through console.  Enabled "interrup EP scheduling" under "inventra contoller" per Ravi B suggested then the "reset low speed" message went away and I can see the any keyboard pressed detected on cat  /dev/input/event0 (keyboard) but it is not in readable format (looks like invalid baud rate character on serial console).  This is my first time working on keyboard project, please advice if there is any additional setup or configuration I could turn on to enable mapping keyboard pressed to console readable format.   Also wonder if you could provide the completed reources or reference how to support usb keyboard on dm6446.

thanks!!

 

 

 

  • 0
    TI__Genius 9460 points

    May,

    Please follow the original thread where Ravi had suggested for "interrup EP scheduling".

    Ajay

  • 0 in reply to Ajay
    TI__Expert 7885 points

    may,

    If you observe unreadable character on console while using cat /dev/input/event0, it means the keyboard is events are captured and working. For testing USB HID devices, there is a event capture application available. I was not able to attach the evtest application through this. Please refer to download http://people.freedesktop.org/~whot/evtest/.

    Regards

    Ravi B

  • 0 in reply to Ravi B
    TI__Expert 4510 points

    Hi Ravi,

     

    May was trying to post this reply but had trouble doing this - I am posting on her behalf.

     

     

    I have two keyboards.  One works fine with your reply, the other doesn’t seem to capture any keyboard event at all.  This keyboard also works fine on Linux PC.

    There is no keyboard event go into input module.

     

    usb 1-1.2: new full speed USB device using musb_hdrc and address 10

    usb 1-1.2: configuration #1 chosen from 1 choice

    input: Microsoft Microsoft� Nano Transceiver v2.0 as /devices/platform/musb_hdrc/usb1/1-1/1-1.2/1-1.2:1.0/input/input2

    input_open_device: dev_name Microsoft Microsoft� Nano Transceiver v2.0

    evdev_connect

    evbug_connect

    input_open_device: dev_name Microsoft Microsoft� Nano Transceiver v2.0

    generic-usb 0003:045E:0745.0004: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft� Nano Transceiver v2.0] on usb-musb_hdrc-1.2/input0

    input: Microsoft Microsoft� Nano Transceiver v2.0 as /devices/platform/musb_hdrc/usb1/1-1/1-1.2/1-1.2:1.1/input/input3

    input_open_device: dev_name Microsoft Microsoft� Nano Transceiver v2.0

    evdev_connect

    evbug_connect

    input_open_device: dev_name Microsoft Microsoft� Nano Transceiver v2.0

    generic-usb 0003:045E:0745.0005: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft� Nano Transceiver v2.0] on usb-musb_hdrc-1.2/input1

    input: Microsoft Microsoft� Nano Transceiver v2.0 as /devices/platform/musb_hdrc/usb1/1-1/1-1.2/1-1.2:1.2/input/input4

    input_open_device: dev_name Microsoft Microsoft� Nano Transceiver v2.0

    evdev_connect

    evbug_connect

    input_open_device: dev_name Microsoft Microsoft� Nano Transceiver v2.0

    generic-usb 0003:045E:0745.0006: input,hiddev96,hidraw2: USB HID v1.11 Device [Microsoft Microsoft� Nano Transceiver v2.0] on usb-musb_hdrc-1.2/input2

     

    # cat /sys/class/input/input2/event0/device/name

    Microsoft Microsoft� Nano Transceiver v2.0

     

    # cat /proc/bus/input/devices

    I: Bus=0003 Vendor=045e Product=0745 Version=0111

    N: Name="Microsoft Microsoft� Nano Transceiver v2.0"

    P: Phys=usb-musb_hdrc-1.2/input0

    S: Sysfs=/devices/platform/musb_hdrc/usb1/1-1/1-1.2/1-1.2:1.0/input/input2

    U: Uniq=

    H: Handlers=kbd event0 evbug

    B: EV=120013

    B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe

    B: MSC=10

    B: LED=7

     

    #cat /dev/input/event0 => no respond for any keyboard pressed

     

     

  • 0 in reply to Ravi B
    Prodigy 20 points

    Hello all,

    Sorry to bump topics, but I think it's relevant since I'm the person who inherited all of May's keyboard code and I have been given the task of getting it working again.  Apparently the code that was in version control was the version this thread was about because I get the "reset full speed USB device using musb_hdrc and address" error repeatedly.

    I have gone into menuconfig and enabled the "Enable Scheduling of Interrupt Endpoint (EXPERIMENTAL)" option under "Inventra Highspeed Dual Role Controller" as directed by Ravi. 

    Unfortunately, every time I make the kernel it clears the flag!  What am I missing?  Some dependancy, you can think of??

    -Kurt