Jetson TK1 HDMI display having problem

I was using NVIDIA Jetson Tegra K1 development kit and the HDMI display went off after some time. Unable to solve the problem, I re-flashed the board two times. After first time, the screen didn’t show anything. Second time flashing eventually resulted in showing the screen for a short time (3-4 s after desktop appears). Plugging and unplugging HDMI cable also results in showing the screen for short time. I also followed https://devtalk.nvidia.com/default/topic/800294/?comment=4411244 and was able to display data for somewhat longer time (may be a minute). But the screen never stays for a longer time.

Following is the output of

sudo get-edid | parse-edid

which doesn’t result in success:

This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
[  372.158945] tegra-i2c tegra12-i2c.5: --- register dump for debugging ----
[  372.167519] tegra-i2c tegra12-i2c.5: I2C_CNFG - 0x2c00
[  372.175465] tegra-i2c tegra12-i2c.5: I2C_PACKET_TRANSFER_STATUS - 0xff0001
[  372.189109] tegra-i2c tegra12-i2c.5: I2C_FIFO_CONTROL - 0xe0
[  372.198125] tegra-i2c tegra12-i2c.5: I2C_FIFO_STATUS - 0x800040
[  372.208749] tegra-i2c tegra12-i2c.5: I2C_INT_MASK - 0xed
[  372.214926] tegra-i2c tegra12-i2c.5: I2C_INT_STATUS - 0x0
[  372.221302] tegra-i2c tegra12-i2c.5: msg->len - 1
[  372.228866] tegra-i2c tegra12-i2c.5: is_msg_write - 1
[  372.240146] tegra-i2c tegra12-i2c.5: next_msg->len - 1
[  372.246338] tegra-i2c tegra12-i2c.5: is_next_msg_write - 0
[  372.253524] tegra-i2c tegra12-i2c.5: buf_remaining - 1
[  372.262705] tegra-i2c tegra12-i2c.5: i2c transfer timed out, addr 0x0050, data 0x00
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
        Identifier "LONTIUM"
        ModelName "LONTIUM"
        VendorName "LTM"
        # Monitor Manufactured week 45 of 2009
        # EDID version 1.3
        # Digital Display
        DisplaySize 880 500
        Gamma 2.20
        Option "DPMS" "true"
        Horizsync 30-68
        VertRefresh 50-60
        # Maximum pixel clock is 150MHz
        #Not giving standard mode: 1024x768, 60Hz
        #Not giving standard mode: 1600x1200, 60Hz

        #Extension block found. Parsing...
Hmm, you have data blocks, but not video ones... weird
Something strange happened. Please contact the author,
Matthew Kern at <pyrophobicman@gmail.com>

and the output of

sudo get-edid | edid-decode
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
[  423.644597] tegra-i2c tegra12-i2c.5: --- register dump for debugging ----
[  423.665059] tegra-i2c tegra12-i2c.5: I2C_CNFG - 0x2c00
[  423.674954] tegra-i2c tegra12-i2c.5: I2C_PACKET_TRANSFER_STATUS - 0xff0001
[  423.682143] tegra-i2c tegra12-i2c.5: I2C_FIFO_CONTROL - 0xe0
[  423.688054] tegra-i2c tegra12-i2c.5: I2C_FIFO_STATUS - 0x800040
[  423.694158] tegra-i2c tegra12-i2c.5: I2C_INT_MASK - 0xed
[  423.699912] tegra-i2c tegra12-i2c.5: I2C_INT_STATUS - 0x0
[  423.705549] tegra-i2c tegra12-i2c.5: msg->len - 1
[  423.710484] tegra-i2c tegra12-i2c.5: is_msg_write - 1
[  423.715724] tegra-i2c tegra12-i2c.5: next_msg->len - 1
[  423.721332] tegra-i2c tegra12-i2c.5: is_next_msg_write - 0
[  423.726973] tegra-i2c tegra12-i2c.5: buf_remaining - 1
[  423.732339] tegra-i2c tegra12-i2c.5: i2c transfer timed out, addr 0x0050, data 0x00
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   32 8d 00 00 00 00 00 00 2d 13
version:         01 03
basic params:    a0 58 32 78 2a
chroma info:     ee 91 a3 54 4c 99 26 0f 50 54
established:     21 08 00
standard:        61 40 a9 40 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    02 3a 80 18 71 38 2d 40 58 2c 45 00 a0 5a 00 00 00 1e
descriptor 2:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 3:    00 00 00 fd 00 32 3c 1e 44 0f 00 0a 20 20 20 20 20 20
descriptor 4:    00 00 00 fc 00 4c 4f 4e 54 49 55 4d 0a 20 20 20 20 20
extensions:      01
checksum:        04

Manufacturer: LTM Model 0 Serial Number 0
Made week 45 of 2009
EDID version: 1.3
Digital display
Maximum image size: 88 cm x 50 cm
Gamma: 2.20
DPMS levels: Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
  640x480@60Hz
  800x600@60Hz
  1024x768@60Hz
Standard timings supported:
  1024x768@60Hz
  1600x1200@60Hz
Detailed mode: Clock 148.500 MHz, 160 mm x 90 mm
               1920 2008 2052 2200 hborder 0
               1080 1084 1089 1125 vborder 0
               +hsync +vsync
Manufacturer-specified data, tag 0
Monitor ranges: 50-60HZ vertical, 30-68kHz horizontal, max dotclock 150MHz
Monitor name: LONTIUM
     Has 1 extension blocks
Checksum: 0x4

CEA extension block
Extension version: 3
31 bytes of CEA data
  Video data block
    VIC 16
    VIC 31
    VIC 04 (native)
    VIC 00
    VIC 00
    VIC 00
    VIC 02
    VIC 00
    VIC 00
    VIC 00
  Audio data block
  Speaker allocation data block
  Extended tag: video capability data block
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 2.0.0.0
    Supports_AI
    Maximum TMDS clock: 225MHz
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 27.000 MHz, 160 mm x 90 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync
Checksum: 0xd2

EDID block does NOT conform to EDID 1.3!
        Digital display field contains garbage: 20

Thanking in anticipation!!

I see what might be the issue. On rare occasion people run into a monitor with edid data not conforming to what is expected, which means Jetson won’t be able to make sense of what the monitor says it is (other monitors with edid support probably still work on the Jetson). Look at this in particular:

EDID block does NOT conform to EDID 1.3!
        Digital display field contains garbage: 20

In at least one previous case the same information occurred, but also included a maintainer’s email for edid issues (not related to Jetson). The issue was fixed within a couple of days after he contacted the maintainer with the edid information. I found this web page via the man page of read-edid, and mentions email to the maintainer, but I did not see the exact email address…you’ll probably need to dig around on this web site:
http://www.polypux.org/projects/read-edid/

Many thanks for the swift response! I think you are talking about this:

https://devtalk.nvidia.com/default/topic/773175/jetson-tk1-fails-to-detect-hdmi-monitor/

I have also emailed the problem to the read-edid author. Let’s wait for the reply.