HDMI edid read failed on Jetson Xavier

Hi NV team,

This Xavier devkit could not boot up with I2C error message reported. After re-flash, it can be booted up now. But it has a problem to detect the HDMI monitor (e.g. my Dell 1920x1200 monitor is detected as “40” Display" with 1280x720 or unknown display).

By checking the debugging messages (pls see the attachment), Xavier could not read the monitor’s edid.

And it still reports I2C errors. I believe the reading edid issue is caused by the I2C error.

Is this caused by the Xavier’s I2C bus on HDMI port? Please help.

Thanks,
andrewli
restart minicom message_last flash JP4_4_1_c.odt (30.1 KB)

Is your Dell monitor a monitor with native HDMI port?

Hi WayneWWW,
Yes, it’s the native HDMI port. And when I use another Xavier kit, it has no problem.

Then sounds like hardware defect. Please also try other HDMI monitors on this problematic device. They should all fail on this device.

Hi WayneWWW,

I just tried another Philips HDMI 1.4 monitor, when Xavier boots up, it shows NVidia logo first, and then no display at all.

The debugging message stops here:

Blockquote

Ubuntu 18.04.5 LTS nvidia-desktop ttyTCU0

nvidia-desktop login: [ 20.994696] edid invalid
[ 22.104416] tegra-i2c 31c0000.i2c: rx dma timeout txlen:28 rxlen:128
[ 22.104422] tegra-i2c 31c0000.i2c: — register dump for debugging ----
[ 22.104432] tegra-i2c 31c0000.i2c: I2C_CNFG - 0x22c00
[ 22.104438] tegra-i2c 31c0000.i2c: I2C_PACKET_TRANSFER_STATUS - 0x10001
[ 22.104443] tegra-i2c 31c0000.i2c: I2C_FIFO_CONTROL - 0x0
[ 22.104449] tegra-i2c 31c0000.i2c: I2C_FIFO_STATUS - 0x800080
[ 22.104454] tegra-i2c 31c0000.i2c: I2C_MST_FIFO_CONTROL - 0x70
[ 22.104459] tegra-i2c 31c0000.i2c: I2C_MST_FIFO_STATUS - 0x7c0000
[ 22.104465] tegra-i2c 31c0000.i2c: I2C_MST_PACKET_TRANSFER_CNT - 0x0
[ 22.104470] tegra-i2c 31c0000.i2c: I2C_INT_MASK - 0x6c
[ 22.104475] tegra-i2c 31c0000.i2c: I2C_INT_STATUS - 0x2
[ 22.104491] tegra-i2c 31c0000.i2c: i2c transfer timed out addr: 0x50
[ 28.176221] edid invalid
[ 28.176422] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.176705] edid invalid
[ 28.176800] edid invalid
[ 28.180725] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.185509] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.192276] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.196630] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.202568] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.208862] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.214952] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.221272] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.227240] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 28.229652] tegradc 15200000.nvdisplay: hdmi: edid read failed
[ 36.697585] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.701825] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.706268] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.710358] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.714414] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.718531] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.722579] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.726638] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.730863] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.734890] tegra-i2c 31c0000.i2c: no acknowledge from address 0x50
[ 36.735548] tegradc 15200000.nvdisplay: hdmi: edid read failed

Blockquote

For Dell monitor, even it cannot read edid, it can display on the monitor. it looks that Xavier keeps trying to detect I2C until [155.xxxxxx]

If it’s Xavier hardware issue, can we ask for RMA in this case?

Thanks,
andrewli

We can only tell you that you should RMA this device. But those RMA detail is not what we can take care of. Separate team will help on that.

Is this device a new one?

Per the end customer, this is a new kit.

Also, you can dump the log from uart and see why cboot is able to output. I also want to check your cboot log too.

I recorded dmesg and Xorg.0.log for Dell monitor in the attachment. Please let me know if you need other details. problem xavier devkit_dmesg from host.odt (46.8 KB) Xorg.0.log_after reflash_minicom.odt (25.2 KB)

They are not what I need. Dmesg is just kernel log so not related to the boot logo. Boot logo is from cboot.

Connect a micro usb cable to the micro usb port on the devkit. Use minicom on your host to open /dev/ttyUSB3 with baud rate 115200.

Adn then reboot the device.

Please see the cboot messages record For Philips monitor as attached. I just found only when the monitor is not in sleep mode, the logo can be seen. restart xavier logo display_Philips monitor.odt (27.8 KB)

Did you see logo when you dump the log you just shared?
I also see edid read failure in cboot and also display init failure in cboot.

yes, for this message I saw the logo by waking up the monitor in advance.

I think you can directly RMA it. Not sure how that logo came from. Even cboot not able to read EDID.

Thanks Wayne!