Orin 32G pice of 35.4.1 boot failed with log "Phy link never came up",and do you know how to avoid it?

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hi,
I update our custom board Orin 32G from 35.2.1 to 35.4.1.When it was 35.2.1,the 141a0000 pcie can boot up correctly.But when it was 35.4.1, the 141a0000 pcie boot up failed with the following log.Do you know how to avoid it?

~$ sudo dmesg|grep pcie
[sudo] password for xingshen001: 
[    6.367054] tegra194-pcie 14100000.pcie: Adding to iommu group 9
[    6.380021] tegra194-pcie 14100000.pcie: Using GICv2m MSI allocator
[    6.387751] tegra194-pcie 14160000.pcie: Adding to iommu group 10
[    6.400416] tegra194-pcie 14160000.pcie: Using GICv2m MSI allocator
[    6.407461] tegra194-pcie 141a0000.pcie: Adding to iommu group 11
[    6.419652] tegra194-pcie 141a0000.pcie: Using GICv2m MSI allocator
[    6.427843] tegra194-pcie 141a0000.pcie: Failed to get slot regulators: -517
[    8.239854] tegra194-pcie 14100000.pcie: Using GICv2m MSI allocator
[    8.247709] tegra194-pcie 14100000.pcie: host bridge /pcie@14100000 ranges:
[    8.262096] tegra194-pcie 14100000.pcie:       IO 0x0030100000..0x00301fffff -> 0x0030100000
[    8.278388] tegra194-pcie 14100000.pcie:      MEM 0x20a8000000..0x20afffffff -> 0x0040000000
[    8.301464] tegra194-pcie 14100000.pcie:      MEM 0x2080000000..0x20a7ffffff -> 0x2080000000
[    8.416591] tegra194-pcie 14100000.pcie: Link up
[    8.422303] tegra194-pcie 14100000.pcie: PCI host bridge to bus 0001:00
[    8.572329] pcieport 0001:00:00.0: Adding to iommu group 9
[    8.578251] pcieport 0001:00:00.0: PME: Signaling with IRQ 64
[    8.584405] pcieport 0001:00:00.0: AER: enabled with IRQ 64
[    8.590934] tegra194-pcie 14160000.pcie: Using GICv2m MSI allocator
[    8.598490] tegra194-pcie 14160000.pcie: host bridge /pcie@14160000 ranges:
[    8.605662] tegra194-pcie 14160000.pcie:       IO 0x0036100000..0x00361fffff -> 0x0036100000
[    8.614348] tegra194-pcie 14160000.pcie:      MEM 0x2428000000..0x242fffffff -> 0x0040000000
[    8.623027] tegra194-pcie 14160000.pcie:      MEM 0x2140000000..0x2427ffffff -> 0x2140000000
[    9.738300] tegra194-pcie 14160000.pcie: Phy link never came up
[    9.744467] tegra194-pcie 14160000.pcie: PCI host bridge to bus 0004:00
[    9.821260] pcieport 0004:00:00.0: Adding to iommu group 10
[    9.827266] pcieport 0004:00:00.0: PME: Signaling with IRQ 66
[    9.833423] pcieport 0004:00:00.0: AER: enabled with IRQ 66
[    9.858451] tegra194-pcie 141a0000.pcie: Using GICv2m MSI allocator
[    9.865028] tegra194-pcie 141a0000.pcie: Failed to get slot regulators: -517
[    9.865119] vdd-3v3-pcie: supplied by vdd-3v3-sys
[    9.927841] tegra194-pcie 141a0000.pcie: Using GICv2m MSI allocator
[   10.042405] tegra194-pcie 141a0000.pcie: host bridge /pcie@141a0000 ranges:
[   10.049589] tegra194-pcie 141a0000.pcie:       IO 0x003a100000..0x003a1fffff -> 0x003a100000
[   10.058274] tegra194-pcie 141a0000.pcie:      MEM 0x2b28000000..0x2b2fffffff -> 0x0040000000
[   10.066961] tegra194-pcie 141a0000.pcie:      MEM 0x2740000000..0x2b27ffffff -> 0x2740000000
[   11.186297] tegra194-pcie 141a0000.pcie: Phy link never came up
[   11.192464] tegra194-pcie 141a0000.pcie: PCI host bridge to bus 0005:00
[   11.269343] pcieport 0005:00:00.0: Adding to iommu group 11
[   11.275355] pcieport 0005:00:00.0: PME: Signaling with IRQ 68
[   11.281520] pcieport 0005:00:00.0: AER: enabled with IRQ 68

Thanks

3

You could compare the device tree onrel-35.2.1 and rel-35.4.1 are same or not first.

4

Hi,
The device tree has many different points. Can you point out the focused points?
Thansk

5

What kind of difference did you see…?

7

…Only focus on the PCIe@141a0000 part.

8

Hi,
There is some difference as following.By the way, I have not modified anything about pcie.

图片
图片1831×811 137 KB

图片
图片1831×831 224 KB

Thanks

9

please put same device to NVIDIA devkit and see if you saw same issue on rel-35.4.1 and rel-35.2.1 (or rel-35.3.1 too).

10

Hi,
I put the same module of rel-35.4.1 to NVIDIA devkit and the module can discover the nvme0n1 correctly.
Thanks

11

Hi,
There are something wrong in the circuit diagram and the problem is solved .
Thanks

1 Like
13

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