I need to user pcie-c3 for ethernet switch chip，i
I have configured ODMDATA as follows in p3834-0008-p4071-0000-nvme.conf
ODMDATA=“uphy0-config-6,pcie@3_status=okay”;
Accorrding to UphyLaneConfig tutor, i need config lane-map:
But, what is UPHY-lane-map owner-id of PCIE-C3？
And when set okay in kernel dts, the board can’t flash image.
/* PCIe C3 */
pcie@a808440000 {
status = "okay";
};
Do I need to add the line ODMDATA="uphy0-config-6,pcie@3_status=okay";?
Yes, that is still needed. ODMATA will change the UPHY setting. You have to use config 6 for UPHY0 and also enable PCIe C3 in bpmp dtb (this would be done by using ODMDATA field in board config).
I have added ODMDATA and set dts status to okay, I can’t find pci_bus 0003 in kernel log, it print tegra264-pcie a808440000.pcie: PCIe Controller-3 Link is DOWN.
Could this issue be due to a software configuration problem??
kernel_pcie-c3.log (87.8 KB)
In addition, my hardware only use lane 6 of uphy0 and does not use lane 7. Is there any additional configuration required in the software?
Did you remember to configure the pinmux setting of clkreq and rst?
My pinmux setting is that:
pex_l3_clkreq_n_pb4 {
nvidia,pins = "pex_l3_clkreq_n_pb4";
nvidia,function = "pe3_clkreq_l";
nvidia,pull = <TEGRA_PIN_PULL_NONE>;
nvidia,tristate = <TEGRA_PIN_DISABLE>;
nvidia,enable-input = <TEGRA_PIN_ENABLE>;
nvidia,drv-type = <TEGRA_PIN_1X_DRIVER>;
nvidia,e-io-od = <TEGRA_PIN_ENABLE>;
nvidia,e-lpbk = <TEGRA_PIN_DISABLE>;
};
pex_l3_rst_n_pb5 {
nvidia,pins = "pex_l3_rst_n_pb5";
nvidia,function = "pe3_rst_l";
nvidia,pull = <TEGRA_PIN_PULL_NONE>;
nvidia,tristate = <TEGRA_PIN_DISABLE>;
nvidia,enable-input = <TEGRA_PIN_DISABLE>;
nvidia,drv-type = <TEGRA_PIN_1X_DRIVER>;
nvidia,e-io-od = <TEGRA_PIN_ENABLE>;
nvidia,e-lpbk = <TEGRA_PIN_DISABLE>;
};
In addition, my hardware only use lane 6 of uphy0 and does not use lane 7. Is there any additional configuration required in the software?
HI,
that should be okay. This might not be a software configuration problem now.
You could refer to debug tips for link failure problem in the document.
Thks, this issue is not a thor software problem. We found cause that switch chip there is not firmware. I see the switch device now.