• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 458 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.

TCA8418E-EVM GUI SOFTWARE FREEZING/LOCKING WHEN PUSHBUTTON #3 (COLUMN 3/ROW1) IS PRESSED

Chuck Faust
Prodigy 20 points
Other Parts Discussed in Thread: TCA8418E-EVM

We are using a NEW (out of the ESD bag) TCA8418E-EVM with an MSP-340G22553 LaunchPAD module.

The EVM is being handled at an approved ESD workstation.

Both the LaunchPAD & the EVM are configured per TI's setup procedure.

After properly configuring the devices for use with the USB port, and "flashing" the module, the GUI software is activated. The GUI screen for the "keypad" evaluation loads properly, and the keypad buttons are being displayed properly on the screen until the #3 button (Col3/Row1) is pressed. At that point the GUI locks up and the keypad scan no longer functions when any other buttons are pressed. 

Has anyone else experienced this before?

Any suggestions?

  • 0
    TI__Genius 16450 points
    Hello Chuck,

    Thank you for the question.

    This is actually a demo of the "keypad lock" feature. To unlock the keyboard, press the middle button (button 22) of the 3x3 array twice. It should unlock the keypad again.

    I've updated the software recently to remove this functionality on the 3rd button press, because I felt it was not clear that a keypad lock was being demo'd, but am currently in the process of trying to get this pushed to the website.

    Rest assured, this is not a frozen EVM, but instead the keypad locking feature of the EVM. A press to key 3 will lock the keypad until a double tap of center button (key 22) is performed.
  • 0 in reply to Jonathan Valdez
    Prodigy 20 points
    Thank you for the quick response! We were concerned that the decoder became damaged. Thanks again for the clarification and we will keep a look out for the updates.