• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 692 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.

Qt Embedded 4.7.4+DM816x: Reading keyboard input from both a USB keyboard and a ssh session doesn't work.

Rodney Lott
Prodigy 180 points

I am working with a DM-816x EVM. I have been able to use the QWS_KEYBOARD export as follows to get keyboard input from my application:

export QWS_KEYBOARD="TTY LinuxInput:/dev/input/event0"

This allows the application to receive the key presses, but once I start the application from an SSH shell, it no longer will respond to keyboard input from that shell (e.g. Ctrl+C to kill it will not work). 

Is there anything special I need to do to get it to respond to both a USB keyboard and the keyboard input from the SSH shell?  It's something that I can work around, but it would be nice to be able to have both working.

Thanks.

-Rodney

  • 0
    TI__Genius 11470 points

    Hello, Rodney

    I'll try to reproduce this issue. Just to double check that: You have USB keyboard connected to your Netra board, and after you enable it, the keyboard, that is connected to your Host-PC (connected to the board via serial console), is disabled?

    BR

    Vladimir

  • 0 in reply to Vladimir-XID
    Prodigy 180 points

    My host computer is running Ubuntu Lucid natively.  I have installed the dropbear package on the EVM that I built with Arago.

    The serial console into the board is fine.  I'm talking about the ssh connection.  When I have ssh'd into the Netra board and ran my program, I would then have to go to the serial console login and use that to kill the dropbear session (since the application appears to eat the ssh terminal's keyboard input).  I also noticed that the output from the program had lots of blank space added to it and that the text was displaced (see attached screenshot).  I have a workaround for this (i.e. using the daemonize program) which detaches the program from the terminal and runs it in its own session.  But, if the QWS_KEYBOARD is supposed to allow for multiple input sources, then this is something to be concerned about. 

    Thanks, Vladimir.

    -Rodney