This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: TDA4VM Using two M.2 SSD problems.

Part Number: TDA4VM


I try to use two "Samsung 970 PRO NVMe m.2" SSD on TDA4EVM.

Using M.2 socket and PCIe x2 Lane socket will fail.

Using M.2 socket and PCIe x1 Lane socket will succeed.

I need to use both M.2 socket and PCIe x2 Lane socket.

Software : PSDK 6.2.0

---------------------------------------------------------------------------------

M2_SSD_and_PCIex2Lane_SSD_20200423.txt

---------------------------------------------------------------------------------

M2_SSD_and_PCIex1Lane_SSD_20200423.txt

  • Pierre, 

    It seems in the 2-lane case, the 2-lane slot was successfully brought up as nvme0, but the m.2 slot device failed when enabling device. See below. I will check with our PCIe driver team to see if they help to decode the error code "-28". 

    in the mean time, if you can confirm if you modified the default device tree? 

    regards

    Jian

    1L case, m.2 slot device success:

    [ 7.788159] nvme nvme1: pci function 0002:01:00.0
    ...
    [ 7.857814] pci 0002:00:00.0: enabling device (0000 -> 0002)
    [ 7.871206] pci_bus 0002:00: 2-byte config write to 0002:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
    [ 7.880905] pci_bus 0002:00: 2-byte config write to 0002:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
    [ 7.890764] nvme 0002:01:00.0: enabling device (0000 -> 0002)
    ...
    [ 8.015391] nvme nvme1: missing or invalid SUBNQN field.
    [ 8.015447] nvme nvme1: Shutdown timeout set to 8 seconds
    
    
    2L case, m2 device failed:
    [    8.839755] nvme nvme1: pci function 0002:01:00.0
    ...
    [    8.889196] pci 0002:00:00.0: enabling device (0000 -> 0002)[FAILED] 
    [    8.895705] pci_bus 0002:00: 2-byte config write to 0002:00:00.0 offset 0x4 may corrupt adjacent RW1C bits Failed to start Synchronize System and HW clocks.
    See 'systemc
    [    8.899653] remoteproc remoteproc4: 5c00000.r5f is available l status sync-clocks.service' for details.
    [    8.918523] pci_bus 0002:00: 2-byte config write to 0002:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
    [    8.918533] nvme 0002:01:00.0: enabling device (0000 -> 0002)
    [    8.918714] nvme nvme1: Removing after probe failure status: -28
    

  • Hi,

    Can you change the msi-map property in pcie2_rc in arch/arm64/boot/dts/ti/k3-j721e-main.dtsi

    msi-map = <0x0 &gic_its 0x20000 0x10000>;

    (originally it was msi-map = <0x0 &gic_its 0x10000 0x10000>;)

    Thanks

    Kishon