…Just to clarify. I want to check the log when this situation happened.
[ 5.330345] tegra194-pcie 14160000.pcie: Failed to get PHY: -19
But the log you shared didn’t have it at all…
I dont find this in current log is it old log sir…
dmesgLogsonlyPcie.txt (4.0 KB)
Then please follow up previous debug tips and do your check.
Nothing to check on my side now.
I meant the issue is same but the timestamp was different. I have done all the debugging steps. I have also corrected debugging in the link where it says steps to debug if link never came up.
If you could please tell me I made some mistake in the process, then I will leave and search for the cause
- for custom carrier board I modiifed dtb file to enable C4 and C7.
- I modified uphy lane configuration in uphy-lane.dtsi. to configure it for option2.
- Used default pin mux settings as I see most of the pins are same as the devkit.
- for reset and clk pins i changed them from rsvd to pex where x is the number.
5.tried every flashing command.
Are these steps right for custom carrier board.
I think i may need to add kernel image by building one and not using the default that is downloaded.
kindly give me opinion on this one. I wont bug you anymore
- for custom carrier board I modiifed dtb file to enable C4 and C7.
You don’t need to do this for C4 at all because C4 is enabled in the default setting already. I am afraid that you broke that thing by yourself after your modification.
If you didn’t change anything for C4 and same NVMe can work fine on NV devkit but failed on your board, then please review your hardware design.
Hi, I am back with the same problem. I tried every configuration I possibly could change. But I was not able to bring up the pcie. still “Pcie phy link never came up”… Can you please guide me is it hardware problem or software configuration issue…
New Text Document.txt (3.3 KB)
the issue in the log “vddio-pex-ctl” can be ignored for pcie 140c… I changed the ctrl value to match 1416…
I am using config option 2 as suggested by hardware engineer. Shall i chose c10 or c4 for nvme I am confused there is contradicting table
some relvant log on C1 busybox devmem 0x02437020
Only this picture is valid to Orin NX. The other one is not feasible. Option 1 or 2 does not matter to C4.
And I don’t know what is your purpose to modify C1 as the issue here is totally C4.
I would suggest you just take a look at Orin Nano devkit schematic for your C4 design.
I compared the schematic of jetson dev kit and custom carrier board. I find the pins to be same. May be my pin configuration is incorrect .My pin configuration for most important pins for the C4 pCie is : is this configuration correct …
In the shell I get this response
Shell> pci
Seg Bus Dev Func
01 00 00 00 ==> Bridge Device - PCI/PCI bridge
Vendor 10DE Device 229E Prog Interface 0
01 01 00 00 ==> Network Controller - Other network controller
Vendor 10EC Device C822 Prog Interface 0
04 00 00 00 ==> Bridge Device - PCI/PCI bridge
Vendor 10DE Device 229C Prog Interface 0
08 00 00 00 ==> Bridge Device - PCI/PCI bridge
Vendor 10DE Device 229C Prog Interface 0
08 01 00 00 ==> Network Controller - Ethernet controller
Vendor 10EC Device 8168 Prog Interface 0
Respected @WayneWWW
You could just compare your pinmux setting with default BSP setting.
My DTB configuration work on devkit and Another custom board from another manufacturer. I still get the same issue. Even though i compared the schematic with the official dev kit schematic.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.