• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 1330 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM335x keypad GPIO and wakeup

Patrick Loef1
Expert 1230 points
Other Parts Discussed in Thread: AM3352, TCA8418E

Hello,

We are developing an own board with the AM3352 processor, on this board we gonna use the Linux kernel/SDK from TI, and we will program in QT the main software.

Now we need to connect 13 buttons that will be used as a keypad, QT needs to get from the Linux the information which button is pressed so we can handle it.

I saw in TRM and that and keyboard / keypad interface can be connected to the GPIO port. Could this be connected to the GPIO1 port, so yes which pins can be used and how must the interface being made. Also is this already standard in the Linux kernel, so that when a key is pressed this information will come forward in QT?

Could also tell somebody which GPIO0 pin could be used to wakeup?

Thanks in advance

Patrick

  • 0
    Expert 1230 points

    Hello,

    In my first post  I talked about the keypad, now I saw that there are some chips like: ADP5587(88) or the TCA8418E chips to make an I2C keyboard.

    This looks very interesting, because that could be needed to generate an event in the QT. Now on this moment I use the 6.00 SDK and I saw that the ADP5587(88) is supported as keyboard driver.

    The support for TCA84148E I didn't found in this SDK, maybe in the 7.00 SDK, but what I like to know is what for I2C port the best can be used and which interupt gpoi for the ADP5587(88)

    Thanks in advance

    Patrick

  • 0 in reply to Patrick Loef1
    TI__Guru**** 393215 points

    Hi Patrick,

    I2C port and interrupt GPIO are entirely up to the board designer. Generally AM335X I2C0 tends to be a bit loaded (PMIC, etc.). You should check that the I2C slave address doesn't conflict with another device too. For interrupt any GPIO can be used, but if you want to wake the processor from low-power modes you should use the GPIO0 bank.

  • 0 in reply to Biser Gatchev-XID
    Expert 1230 points

    Hi Biser,

    Thanks for your help and advice.

    If I would like to design a GPIO buttons keyboard, so Linux will see an key when one this buttons is pressed. Then I must enable this in the SDK I saw, but which port can I then use, and where would the settings of the gpio pins being set?