Hdmi cause problem on PCIE

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
, ,
1

I have custom board
If i boot without hdmi connected , everything is ok .
If i boot with connected HDMI display kernel logging pcie errors

PS: if i boot withouit hdmi and then connect it picture doesnt show but system works normally (kernel only print i2c error and on edid)

[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[ 0.000000] NR_IRQS:64 nr_irqs:64 0
[ 0.000000] /interrupt-controller@60004000: 192 interrupts forwarded to /interrupt-controller
[ 0.000000] t210 clock and reset probe
[ 0.000000] tegra-pmc: get_secure_pmc_setting: done secure_pmc=1
[ 0.000000] clk_cbus_recalc_rate: no gbus parent
[ 0.000000] clk_cbus_recalc_rate: no gbus parent
[ 0.000000] clk_cbus_recalc_rate: no gbus parent
[ 0.000000] clk_cbus_recalc_rate: no gbus parent
[ 0.000000] clk_cbus_recalc_rate: no gbus parent
[ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000006] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.009961] Console: colour dummy device 80x25
[ 0.014609] console [tty0] enabled
[ 0.018141] bootconsole [uart8250] disabled
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.337-miro_wo_wifi_wo_bt-tegra (miro@legion) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #11 SMP PREEMPT Thu May 23 11:27:46 CEST 2024
[ 0.000000] Boot CPU: AArch64 Processor [411fd071]
[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 32,
** 169 printk messages dropped ** [ 0.474874] platform 57000000.gpu: domain= (ptrval) allocates as[2]= (ptrval)
** 980 printk messages dropped ** [ 1.175413] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 935 printk messages dropped ** [ 1.185641] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 866 printk messages dropped ** [ 1.197281] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Receiver ID)
** 1005 printk messages dropped ** [ 1.210145] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 847 printk messages dropped ** [ 1.221739] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 729 printk messages dropped ** [ 1.230003] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Receiver ID)
** 966 printk messages dropped ** [ 1.242602] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 852 printk messages dropped ** [ 1.254080] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 703 printk messages dropped ** [ 1.262271] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010
** 822 printk messages dropped ** [ 1.273595] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 770 printk messages dropped ** [ 1.282639] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 794 printk messages dropped ** [ 1.293464] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 806 printk messages dropped ** [ 1.304592] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 831 printk messages dropped ** [ 1.314505] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 687 printk messages dropped ** [ 1.324450] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 802 printk messages dropped ** [ 1.334091] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 873 printk messages dropped ** [ 1.345937] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 808 printk messages dropped ** [ 1.356652] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010
** 859 printk messages dropped ** [ 1.367113] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 687 printk messages dropped ** [ 1.376698] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 990 printk messages dropped ** [ 1.390249] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010
** 798 printk messages dropped ** [ 1.399201] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 692 printk messages dropped ** [ 1.408251] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 885 printk messages dropped ** [ 1.418976] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 712 printk messages dropped ** [ 1.428364] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 802 printk messages dropped ** [ 1.438986] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 833 printk messages dropped ** [ 1.448967] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 818 printk messages dropped ** [ 1.460125] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Receiver ID)
** 1055 printk messages dropped ** [ 1.474205] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Receiver ID)
** 1123 printk messages dropped ** [ 1.488635] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 715 printk messages dropped ** [ 1.496841] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 851 printk messages dropped ** [ 1.507696] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 1006 printk messages dropped ** [ 1.520959] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Receiver ID)
** 996 printk messages dropped ** [ 1.532104] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 850 printk messages dropped ** [ 1.543354] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 775 printk messages dropped ** [ 1.552767] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 714 printk messages dropped ** [ 1.563048] pcieport 0000:00:01.0: [ 0] Receiver Error (First)
** 807 printk messages dropped ** [ 1.573961] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Receiver ID)
** 948 printk messages dropped ** [ 1.585176] pcieport 0000:00:01.0: AER: Corrected error received: id=0010
** 719 printk messages dropped ** [ 1.595504] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010
** 841 printk messages dropped ** [ 1.607094] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010
** 841 printk messages dropped ** [ 1.616945] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010
** 751 printk messages dropped ** [ 1.626892] pcieport 0000:00:01.0: device [10de:0fae] error status/mask=00000001/00002000
** 929 printk messages dropped ** [ 1.639539] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0010

3

If that is a custom board, I could only ask you to review the hardware design.

I don’t think this issue could be reproduced with NV devkit.

4

But which kind of error can i search .
I has custom board with Jetson Nano , and PCIE nvme , if i not connect HDMI everything is ok , nvme is mounted.
if i try boot with HDMI it freeze and still print pcie errors. In general i want use small hdmi display 800x480 during boot it shows some kind of color noise and kernel freeze in pcie errors. If i connect bigger lcd or regular PC screen logo was appeared during boot but it freeze again with pcie errors. And if i connect lcd after success boot nothing happened, system run properly , no picture shown on any kind of display and kernel write me

[   74.500880] tegra-i2c 7000c400.i2c: no acknowledge from address 0x50
[ 1096.611631] edid invalid
[ 1106.775155] tegra-i2c 7000c700.i2c: rx dma timeout txlen:28 rxlen:128
[ 1106.781943] tegra-i2c 7000c700.i2c: --- register dump for debugging ----
[ 1106.788947] tegra-i2c 7000c700.i2c: I2C_CNFG - 0x2c00
[ 1106.794051] tegra-i2c 7000c700.i2c: I2C_PACKET_TRANSFER_STATUS - 0x10001
[ 1106.800935] tegra-i2c 7000c700.i2c: I2C_FIFO_CONTROL - 0x1c
[ 1106.806584] tegra-i2c 7000c700.i2c: I2C_FIFO_STATUS - 0x800040
[ 1106.812445] tegra-i2c 7000c700.i2c: I2C_INT_MASK - 0x6c
[ 1106.817683] tegra-i2c 7000c700.i2c: I2C_INT_STATUS - 0x2
[ 1106.823151] tegra-i2c 7000c700.i2c: i2c transfer timed out addr: 0x50
[ 1117.015087] tegra-i2c 7000c700.i2c: rx dma timeout txlen:28 rxlen:128
[ 1117.021887] tegra-i2c 7000c700.i2c: --- register dump for debugging ----
[ 1117.029125] tegra-i2c 7000c700.i2c: I2C_CNFG - 0x2c00
[ 1117.034345] tegra-i2c 7000c700.i2c: I2C_PACKET_TRANSFER_STATUS - 0x10001
[ 1117.041110] tegra-i2c 7000c700.i2c: I2C_FIFO_CONTROL - 0x1c
[ 1117.046900] tegra-i2c 7000c700.i2c: I2C_FIFO_STATUS - 0x800040
[ 1117.052833] tegra-i2c 7000c700.i2c: I2C_INT_MASK - 0x6c
[ 1117.058101] tegra-i2c 7000c700.i2c: I2C_INT_STATUS - 0x2
[ 1117.063597] tegra-i2c 7000c700.i2c: i2c transfer timed out addr: 0x50

what can cause this???

5

for HDMI i use DP1 pins

6

Looks just typical hardware error when i2c tries to access EDID from the HDMI monitor.

I has custom board with Jetson Nano , and PCIE nvme , if i not connect HDMI everything is ok , nvme is mounted.

I am not sure why you are repeating the topic again. We already knew that. You don’t need to repeat it.
The rest of comment seems not providing much info either.

This issue is definitely a hardware related problem.

7

sorry for that , i apologize

but which HW problem you mean . Have u any tip ?

8

please review the Jetson Nano design guide document first. We don’t know your board so not possible to tell in such way.

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.