We build two version JetPack 4.4 and 4.6 firmware on our product.(same carrier board)
E12C can be detected on JetPack 4.4 and 4.6 , (/dev/nvme0)
E13T can’t be detected on JetPack 4.6 , but worked on older JetPack 4.4
E13T logs on JetPack4.4 , dmesg | grep pci
at last line , nvme0 detected
The difference in ‘ranges’ property doesn’t really affect the PCIe link up. So, you can ignore that difference for now.
Could you please do this experiment of replacing pcie-tegra.c file from Jetpack 4.4 to 4.6 and see if it works there? also vice-a-versa replacing the same file in 4.4 with the one from 4.6 and see if it fails the link up?
The reason, I’m asking for this experiment is that, although there are some differences in pcie-tegra.c files in both version, they are not expected to affect the PCIe link up. The above experiment is to confirm that.
Seems like I also have some issues with Jetpack 4.6 upgrade regarding NVME drives with Physon and Sabrent controllers with 2242 formats and 1tb capacity.
Drives were recognised under l4t 32.5.2, but not 32.6.1. The bootloader has changed, allowing to flash directly on NVME.
I managed to get the drives recognised under 32.6.1 by downgrading cboot to the previous release version. I don’t really know if it creates instability though.