logo elektroda
logo elektroda
X
logo elektroda

Firmware request for JVC LT-50UHL730 17MB180E VES500QNDB-L4-N41 | Random key presses

DavidStruggle 345 1
ADVERTISEMENT
  • #1 21902274
    DavidStruggle
    Level 2  
    Posts: 2
    I am in need of a firmware for:

    TV: JVC LT-50UHL730
    Board: Vestel 17MB180E
    Panel: VES500QNDB-L4-N41

    Symptom: TV spams (quickly) random button presses. Pretty much unable to control anything anymore.

    When it started to happen: After connecting a Win10 PC over HDMI, CEC enabled.

    Troubleshooting:
    - All board voltages are fine.
    - All I2C communications seem to be fine.
    - Powered board standalone without any other external connections (nothing besides lab power supply and UART) -> Still present.
    - Debug UART gets spammed with:
    
    #*KEYPAD_VAL = 0xac
    #*KEYMAP = 0xf7
    #*KEY = 0xf7
        > app/demoapp: preHandleKeyPressMessage() key: 713>
        > app/demoapp: preHandleKeyPressMessage() key: 552>
    #*KEYPAD_VAL = 0xac
    #*KEYMAP = 0xf7
    #*KEY = 0xf7
        > app/demoapp: preHandleKeyPressMessage() key: 713>
        > app/demoapp: preHandleKeyPressMessage() key: 552>
    

    Firmware request for JVC LT-50UHL730 17MB180E VES500QNDB-L4-N41 | Random key presses Firmware request for JVC LT-50UHL730 17MB180E VES500QNDB-L4-N41 | Random key presses

    - Factory reset via service menu did not fix the issue.

    Diagnosis:
    It seems that somehow my Windows10 machine managed to screw things up in the Linux subsystem. My guess would be that it somehow assigned a new caller to the key handle task.
    I do not believe this is a hardware issue, since the keypad would be connected via I2C and not simple GPIO pins. I also do not see any floating signals on the I2C bus.
    If it is a hardware issue, the main SoC has to be damaged in a way that shorts the internal I2C communication to some other bus/noise.

    If anyone would be able to share a compatible image for this board it would be great.
    I can provide a full boot log if necessary.
    Did you already physically disconnect the local keypad / IR-button board (or its cable) from the mainboard, and if yes, does the random key spam still happen on UART?
    The TV in question does not have a local keypad, but a single button on the IR board. I disconnected this button, but it did not solve the problem. I also measured the signal on this button and it looks perfect.
    Can you post the exact software/loader/version info from the service menu or boot log, plus any sticker/barcode numbers from the 17MB180E board? For Vestel, board number panel alone is often not enough to match the correct firmware image.
    I did add pictures of the barcode & numbers to the post.
    From the Bootlog:
    01-2L-SM-04-20191125
    NOTICE: BL3-1: v1.1(debug):a3777e8<r>
    NOTICE: BL3-1: Built : 11:52:40, Oct 22 2021
    INFO: BL3-1: Initializing runtime services
    INFO: <27>[0;32;31m [Booting] mstar_send_magic_ATF 483
    INFO: BIN1_32bit mode Oct 22 2021 11:52:37
    U-Boot 2011.06-00000-g527e439e-dirty (Mar 22 2023 - 08:26:48)
    Image Name: Linux-4.19.84.
  • ADVERTISEMENT
  • #2 21903696
    DavidStruggle
    Level 2  
    Posts: 2
    I made progress on the problem and found the cause:
    - The debug console is connected to HDMI 1.
    - Normally, these pins get short to ground if a HDMI cable is inserted.
    - I was using a DisplayPort to HDMI cable and the pins did not short to ground but instead seem to have transmitted data (did not inspect the payload yet).
    - The debug port was spammed and it enabled the keypad, which is not part of this TV model.

    Now, using the debug console, I can temporarily disable the keypad with "KEYPADACTION 0", which ignores the keypad inputs.
    The keypad peripheral seems to be still enabled, though, slowing the TV inputs down.

    After sending the command, the TV is usable as normal - minus the slower inputs. This fix is only valid until the AC plug gets removed - after that I have to resend the command.
    There must be a command that saves the "new" config, but I haven't found it yet.

    For now, I made a small modchip, which sends the command after boot.
ADVERTISEMENT