EP mode failure

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

I’m trying to set the Xavier EP mode but couldn’t make it.
What am I supposed to do further? Please give me any advises.

Model: Xavier AGX

Fusing process:

  1. Download L4T Driver Package(L4T R32.5.1)

  2. Applying roots.
    $ tar xf ${L4T_RELEASE_PACKAGE}
    $ cd Linux_for_Tegra/rootfs/
    $ sudo tar xpf …/…/${SAMPLE_FS_PACKAGE}
    $ cd …
    $ sudo ./apply_binaries.sh

  3. Edit p2972-0000.conf.common
    ODMDATA=0x9190000; —> ODMDATA=0x9191000;

  4. get into recovery mode

  5. sudo ./flash.sh jetson-agx-xavier-devkit mmcblk0p1

result:

  1. dmesg
    grep pcie1-desktop:/sys/kernel/config/pci_ep/functions/pci_epf_nv_test$ dmesg | grep pcie
    [ 0.832954] iommu: Adding device 141a0000.pcie_ep to group 0
    [ 0.833619] iommu: Adding device 14180000.pcie to group 1
    [ 0.834330] iommu: Adding device 14100000.pcie to group 2
    [ 0.835038] iommu: Adding device 14140000.pcie to group 3
    [ 0.895102] GPIO line 490 (pcie-reg-enable) hogged as output/high
    [ 0.895141] GPIO line 289 (pcie-reg-enable) hogged as output/high
    [ 4.211368] tegra-pcie-dw 141a0000.pcie_ep: Setting init speed to max speed
    [ 4.212603] tegra-pcie-dw 14180000.pcie: Setting init speed to max speed
    [ 4.213687] OF: PCI: host bridge /pcie@14180000 ranges:
    [ 4.725768] tegra-pcie-dw 14180000.pcie: link is down
    [ 4.725967] tegra-pcie-dw 14180000.pcie: PCI host bridge to bus 0000:00
    [ 4.726939] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
    [ 4.726945] pcie_pme 0000:00:00.0:pcie001: service driver pcie_pme loaded
    [ 4.727059] aer 0000:00:00.0:pcie002: service driver aer loaded
    [ 4.727205] pcie_pme 0000:00:00.0:pcie001: unloading service driver pcie_pme
    [ 4.727245] aer 0000:00:00.0:pcie002: unloading service driver aer
    [ 4.728793] tegra-pcie-dw 14180000.pcie: PCIe link is not up…!
    [ 4.729734] tegra-pcie-dw 14100000.pcie: Setting init speed to max speed
    [ 4.730443] OF: PCI: host bridge /pcie@14100000 ranges:
    [ 4.840892] tegra-pcie-dw 14100000.pcie: link is up
    [ 4.841160] tegra-pcie-dw 14100000.pcie: PCI host bridge to bus 0001:00
    [ 4.855258] pcieport 0001:00:00.0: Signaling PME through PCIe PME interrupt
    [ 4.855268] pcie_pme 0001:00:00.0:pcie001: service driver pcie_pme loaded
    [ 4.855397] aer 0001:00:00.0:pcie002: service driver aer loaded
    [ 4.857306] tegra-pcie-dw 14140000.pcie: Setting init speed to max speed
    [ 4.858060] OF: PCI: host bridge /pcie@14140000 ranges:
    [ 5.373883] tegra-pcie-dw 14140000.pcie: link is down
    [ 5.374058] tegra-pcie-dw 14140000.pcie: PCI host bridge to bus 0003:00
    [ 5.374961] pcieport 0003:00:00.0: Signaling PME through PCIe PME interrupt
    [ 5.374968] pcie_pme 0003:00:00.0:pcie001: service driver pcie_pme loaded
    [ 5.375088] aer 0003:00:00.0:pcie002: service driver aer loaded
    [ 5.375231] pcie_pme 0003:00:00.0:pcie001: unloading service driver pcie_pme
    [ 5.375306] aer 0003:00:00.0:pcie002: unloading service driver aer
    [ 5.377078] tegra-pcie-dw 14140000.pcie: PCIe link is not up…!

  2. sudo lspci -v
    0001:00:00.0 PCI bridge: NVIDIA Corporation Device 1ad2 (rev a1) (prog-if 00 [N)
    Flags: bus master, fast devsel, latency 0, IRQ 36
    Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0
    I/O behind bridge: 00000000-00000fff
    Memory behind bridge: 40000000-400fffff
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Root Port (Slot-), MSI 00
    Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [148] #19
    Capabilities: [158] #26
    Capabilities: [17c] #27
    Capabilities: [190] L1 PM Substates
    Capabilities: [1a0] Vendor Specific Information: ID=0002 Rev=4 Len=100 >
    Capabilities: [2a0] Vendor Specific Information: ID=0001 Rev=1 Len=038 >
    Capabilities: [2d8] #25
    Capabilities: [2e4] Precision Time Measurement
    Capabilities: [2f0] Vendor Specific Information: ID=0004 Rev=1 Len=054 >
    Kernel driver in use: pcieport

  3. ls -la /sys/firmware/devicetree/base/chosen/plugin-manager/odm-data
    -r–r–r-- 1 root root 4 Jan 28 11:10 bootloader_unlocked
    -r–r–r-- 1 root root 4 Jan 28 11:10 disable-pcie-c0-endpoint
    -r–r–r-- 1 root root 4 Jan 28 11:10 disable-pcie-c4-endpoint
    -r–r–r-- 1 root root 4 Jan 28 11:10 disable-pmic-wdt
    -r–r–r-- 1 root root 4 Jan 28 11:10 disable-sata
    -r–r–r-- 1 root root 4 Jan 28 11:10 enable-debug-console
    -r–r–r-- 1 root root 4 Jan 28 11:10 enable-denver-wdt
    -r–r–r-- 1 root root 4 Jan 28 11:10 enable-nvhs-uphy-pcie-c5
    -r–r–r-- 1 root root 4 Jan 28 11:10 enable-pcie-c5-endpoint
    -r–r–r-- 1 root root 4 Jan 28 11:10 enable-ufs-uphy-l10
    -r–r–r-- 1 root root 9 Jan 28 11:10 name
    -r–r–r-- 1 root root 4 Jan 28 11:10 no-battery
    -r–r–r-- 1 root root 4 Jan 28 11:10 normal-build
    -r–r–r-- 1 root root 4 Jan 28 11:10 pcie-xbar-4-1-0-1-2

3

I don’t see any issue with it.
What is the host here to which you are connecting the Xavier-EP?
and please following the procedure given in the documentation to prepare the endpoint for the link up with the host and then start the host. You should be able to get the link up.
BTW, you have to check the lspci output in the host system to be able to see the Xavier-EP getting listed not in the EP system itself.

4

We bought 2 Xaviers, one for RC and the other for EP.
Unfortunately, one of them was broken this morning.
So we will use only one Xaxiver for now,
I should have check the EP mode state in the host system but I didn’t.
Let me try again after the repair is completed.
It is really helpful and thank you.