I have a custom carrier board, i update the dtb file by converting it into dts and then back to dtb. I enabled pcie C4 for my nvme ssd. but when i flash it no nvme is found and flash breaks. Logs shows that pcie 140a000 link is up but pcie 1416000 never came up. I also changed uphy mapping selected option 2 as per design. But nothing seems to work. Any idea or hint please.
Logs:
[ 4.113603] Loaded X.509 cert âBuild time autogenerated kernel key: 8bf422cbdacfe43c83374f4270ed8f21e8dceb0fâ
[ 4.114758] tegra194-pcie 14160000.pcie_ep: Adding to iommu group 8
[ 4.120003] tegra194-pcie 14100000.pcie: Adding to iommu group 9
[ 4.129802] tegra194-pcie 14100000.pcie: Using GICv2m MSI allocator
[ 4.131065] tegra194-pcie 140a0000.pcie: Adding to iommu group 10
[ 4.142129] tegra194-pcie 140a0000.pcie: Using GICv2m MSI allocator
[ 4.169157] tegra-soc-hwpm f100000.tegra_soc_hwpm: Adding to iommu group 11
[ 4.172220] host1x 13e40000.host1x: Adding to iommu group 12
[ 4.191231] host1x 13e40000.host1x: initialized
logsforjetsonorinnx.txt (64.1 KB)
Your log is more like even the flash command is wrong. How did you flash the board?
Did same NVMe work fine on NV devkit?
yes nvme works fine on other board. I am using this command now to flash sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml -p â-c bootloader/t186ref/cfg/flash_t234_qspi.xmlâ
âshowlogs --network usb0 jetson-orin-nano-devkit internal
please share the uart log when you tried above command.
logsforjetsonorinnx.txt (64.1 KB)
Logs2onTerminal.txt (344.1 KB)
I am also getting this error now as well :
422.574] W> Firewall readback mismatch
[0422.579] I> Task: Load MB2/Applet/FSKP
[0422.583] I> Loading MB2 Applet
[0422.586] I> Slot: 1
[0422.588] E> BLOCK_DEV: Failed to open blockdev.
[0422.593] E> LOADER: Failed to open blockdev 0(0).
[0422.598] E> LOADER: Failed to get storage info for binary 21 from loader.
[0422.605] C> LOADER: Could not read binary 21.
[0422.609] E> Failed to load MB2
[0422.612] C> Task 0x46 failed (err: 0x27228311)
[0422.616] E> Top caller module: MB2_PARAMS, error module: LOADER, reason: 0x11, aux_info: 0x83
[0422.625] C> Boot Info Table status dump :
0111100000111000110111111111000000011110000000000000011000001
For this what i do is disconnect the jetson and then reboot. sometimes system reboot. But its not convenient
i changed following files:
tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi
tegra234-mb1-bct-uphy-lanes-p3767-0000.dtsi
tegra234-p3767-0000-p3768-0000-a0 .dtb
-
Just to clarify again. I need âfull logâ since the start of the flash. Not during the middleâŠ
Also, host side log is needed to. -
Why do you need to change these? PCIe C4 is enabled since beginning, no need to change them.
i changed following files:
tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi
tegra234-mb1-bct-uphy-lanes-p3767-0000.dtsi
tegra234-p3767-0000-p3768-0000-a0 .dtb
My Friend I changed these files as per the jetson orin Nx guide for our custom carrier board.
The fresh logs from start to end are here:
newBootLogs.txt (261.9 KB)
NewUartFlashLogs.txt (93.3 KB)
If you didnât change anything related to pcie 14160000 in your change, then this issue has nothing to do with software. PCIe 14160000 is already enabled in default BSP.
Yes my friend I didnt change it once i found that it was enabled by default. But then I get this error. Phy link never came up. However Ethernet connected to pcie@140a0000 link comes up. So i just trying to figure out whether its hardware issue or software related settings. Chatgpt tell me its software related. So i thought I must ask professional
What kind of device is connected on your PCIe C4 here? Is that your NVMe?
yes NVME SSD
Did same NVMe work if it is plugged on Orin Nano devkit?
Yes the same nvme works on other Hardon CTI board Orin Nx. We also switched to another NVME too.
Just to make my question here more clear. Is another carrier board there working with your nvme on pcie C4 without problem?
Yes my friend yes its C4
If you are sure the software side are same then the only difference here is the hardware.
âLink never came upâ is very common issue on PCIe. Iâve seen lots of kinds and lots of them are fixed by hardware fix. Only little of them could be got resolved from software configuration. But those âlittle caseâ do not have nvme SSD. They are mostly FPGA/wifi cards.
The precise way to check it is using the PCIe analyzer to capture LA trace.
thanks for suggestion let me try that and get back to you
What are you going to try here?