unwanted key press with GLK19264-7T-1U

[bpereira]

I've been having a weird problem with a GLK19264-7T-1U. I am communicating with a PIC MCU. I have been able to communicate in both directions and it was working properly. I then found when I cycled the power it would stop communicating. If I held down the override key during power up the communications would be normal and my program would run properly.
I found the info about 'remember' needing to be set. I put this command in my program and then removed it and this worked to save my baudrate after a power cycle.
The program displays a message and then waits for a key press.
But now after my program displays the message it immediately receives a key press. I tried to put a clear buffer command at the start of my program but it is still receiving a key press. This program worked perfectly until I set remember to on. I also set the com speed lock by adding the command to my program then removing it.
Any ideas?

[bpereira]

Here are some more things I have tried. Setting the debounce to max, putting the clear buffer command right before I enter my polling loop. Setting the auto repeat to off. Setting the keypad to up/down mode. None of this works.
I have a two second delay at the start of my program before I send data to the display. This allows me to hold down the overide key during power up before the data stream starts. If I do hold the key briefly during power up then the program works properly and does wait in the loop for a key press. But if I then cycle the power it begins getting an immediate key press again.
There is obviously some saved setting that is causing the problem that gets cleared during an override but it does not get cleared permanently after a power cycle.
I really need help on this as I am under a tight deadline.

[Raquel]

Hello bpereira,

Thanks for your post.

I am sorry to hear about the problems you are having. Do you know what key press or value of key press it is that you are getting at power up?

When manual override jump is put on, the display takes in these temporary settings:
baud - 19200
I2C slave address - 0x50
brightness - 255
contrast - 128
data lock - 0

I am not sure which of these settings are suppressing the key press. Hopefully we can find out soon.

Also, if you connect the display to uProject, instead of your MCU, please check if the module has the same behaviour.

Thanks,