imx8mm - no pcie end point controller

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8mm - no pcie end point controller

1,195 Views
antho
Contributor II

Hi all,

I'm testing PCIe in End Point mode on an imx8mm. Linux kernel is 4.19. I cannot find a way to make it work. Please comment if anything seems wrong. Any advice could be useful.

Following kernel documentation, I should be able to play with pcie endpoint controller in /sys/class/pci_epc and test the interface with lspci and pcitest on the root complex side (x86).

https://www.kernel.org/doc/html/latest/PCI/endpoint/pci-test-howto.html 

The thing is, PCIe endpoint controller device does not exist (nothing in /sys/class/pci_epc). It should be created by a driver activated in the kernel (drivers/pci/controller/dwc/pcie-designware-ep.c ?). Is it created after pcie link is brought up ?

PCIe link is never established (timeout !). Are we talking about a link between RC and EP (see logs below) ? Or is it a phy link between two modules inside the iMX ? I tried to power up the x86 RC connected to the iMX when it is waiting, but nothing happened.

imx kernel logs :

[ 2.266698] imx6q-pcie 33800000.pcie: host bridge /hsio/pcie@33800000 ranges:
[ 2.273869] imx6q-pcie 33800000.pcie: No bus range found for /hsio/pcie@33800000, using [bus 00-ff]
[ 2.283110] imx6q-pcie 33800000.pcie: IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[ 2.290521] imx6q-pcie 33800000.pcie: MEM 0x18000000..0x1fefffff -> 0x18000000
[ 2.297926] imx6q-pcie 33800000.pcie: try to initialize pcie ep.
[ 2.304036] imx6q-pcie 33800000.pcie: Initialize PHY with PLL REfCLK!.
[ 2.310951] imx6q-pcie 33800000.pcie: PHY Initialization End!.
[ 2.317119] imx6q-pcie 33800000.pcie: iATU unroll: enabled
[ 2.322617] imx6q-pcie 33800000.pcie: ddr_test_region is 0xb8200000.
[ 2.328982] imx6q-pcie 33800000.pcie: PCIe EP: waiting for link up...

[timeout]

[ 302.268463] imx6q-pcie 33800000.pcie: PCIe EP: link down.

device tree pcie node (including kernel 4.19 fsl-imx8mm.dtsi) :

&pcie0{
    pinctrl-names = "default";
    pinctrl-0 = <&pinctrl_pcie0>;
    //disable-gpio = <&gpio1 5 GPIO_ACTIVE_LOW>;
    //reset-gpio = <&gpio4 21 GPIO_ACTIVE_LOW>;
    ext_osc = <0>; // use external clk or internal pll if 0
    status = "okay";
};

Here's a diff of my kernel .config :

+CONFIG_PCIEPORTBUS=y
+CONFIG_HOTPLUG_PCI_PCIE=y
+CONFIG_PCIEAER=y
+CONFIG_PCIEASPM=y
+CONFIG_PCIEASPM_DEFAULT=y
+CONFIG_PCIE_PME=y
CONFIG_PCI_MSI=y
CONFIG_PCI_MSI_IRQ_DOMAIN=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCIE_DW=y
CONFIG_PCIE_DW_HOST=y
+CONFIG_PCIE_DW_EP=y
+CONFIG_PCIE_DW_PLAT=y
# CONFIG_PCIE_DW_PLAT_HOST is not set
+CONFIG_PCIE_DW_PLAT_EP=y
CONFIG_PCI_IMX6=y
# CONFIG_PCI_IMX6_COMPLIANCE_TEST is not set
+CONFIG_EP_MODE_IN_EP_RC_SYS=y
# CONFIG_PCI_LAYERSCAPE is not set
CONFIG_PCI_HISI=y
# CONFIG_PCIE_QCOM is not set
+CONFIG_PCI_ENDPOINT=y
+CONFIG_PCI_ENDPOINT_CONFIGFS=y
+CONFIG_PCI_EPF_TEST=y
+CONFIG_PCI_ENDPOINT_TEST=y

Tags (2)
8 Replies

950 Views
Guohua_Liu
Contributor I

Hello ancho,

Have you managed to make your board working in EP mode? I was working on a board that is bought from other company because our own hardware is not ready for now, but their kernel is 4.14.78, and their u-boot is close-sourced, that makes it very difficult to port kernel 5.x. Now we have a new board with kernel 5.4.70. 

We have modifiied the device tree and kernel config, but it still does not work. It seems that the kernel stops when reading data from the EP controller.

Please give some help if you have done it, thanks!

0 Kudos

532 Views
pete_sensoray
Contributor II

Hi @Guohua_Liu @antho 

Were you able to make the PCIE work in endpoint mode with Kernel 5.4?  I'm trying get endpoint mode working under 5.10.72.

I've modified the device tree to use the endpoint mode as follows:

/* Switch PCIE to endpoint mode */
&pcie {
status = "disabled";
};

&pcie_ep {
ext_osc = <0>;
status = "okay";
};

&pcie_phy {
ext_osc = <0>;
/* clocks = <&clk IMX8MP_CLK_PCIE_PHY>; */
status = "okay";
};

Should the EP board use the REF_CLK or EXT_CLK?

Should the RC board be booted before the EP board?

Thanks for any help you can provide.

 

0 Kudos

1,053 Views
Guohua_Liu
Contributor I

Hello antho,

We are also working on a board which is supposed to work in EP mode and have some problems. Have you made some progress?

0 Kudos

1,034 Views
antho
Contributor II

Hi,

I fixed a hardware problem on my board. I had swapped RX lanes on the pcb. Then, I could go further in the link detection.

[ 2.285062] imx6q-pcie 33800000.pcie: host bridge /hsio/pcie@33800000 ranges:
[ 2.292244] imx6q-pcie 33800000.pcie: No bus range found for /hsio/pcie@33800000, using [bus 00-ff]
[ 2.301502] imx6q-pcie 33800000.pcie: IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[ 2.308945] imx6q-pcie 33800000.pcie: MEM 0x18000000..0x1fefffff -> 0x18000000
[ 2.316374] imx6q-pcie 33800000.pcie: try to initialize pcie ep.
[ 2.322492] imx6q-pcie 33800000.pcie: Initialize PHY with PLL REfCLK!.
[ 2.329350] imx6q-pcie 33800000.pcie: PHY Initialization End!.
[ 2.335549] imx6q-pcie 33800000.pcie: iATU unroll: enabled
[ 2.341068] imx6q-pcie 33800000.pcie: ddr_test_region is 0xb8200000.
[ 2.347446] imx6q-pcie 33800000.pcie: PCIe EP: waiting for link up...
[ 2.482082] imx6q-pcie 33800000.pcie: pcie ep: Starting data transfer...
[ 2.791039] imx6q-pcie 33800000.pcie: dma write no end ...
[ 2.848045] imx pcie dma read error 0x10000.
[ 2.848052] imx pcie dma read error 0x10000.
[ 2.852322] imx pcie dma read error 0x10000.
[ 2.856592] imx pcie dma read error 0x10000.
[ 2.860862] imx pcie dma read error 0x10000.
[ 2.865131] imx pcie dma read error 0x10000.
[ 2.869401] imx pcie dma read error 0x10000.
[ 2.873670] imx pcie dma read error 0x10000.
[ 2.877939] imx pcie dma read error 0x10000.
[ 2.882211] imx pcie dma read error 0x10000.
[ 2.886481] imx pcie dma read error 0x10000.
[ 2.890750] imx pcie dma read error 0x10000.
[ 3.099038] imx6q-pcie 33800000.pcie: dma read no end
[ 3.108369] imx6q-pcie 33800000.pcie: pcie ep: Data transfer is failed.

I was told to port my layer in kernel 5.4 to investigate. So I did.

Then, I had only a few kernel logs concerning pcie :

[ 2.153297] imx6q-pcie 33800000.pcie_ep: 33800000.pcie_ep supply epdev_on not found, using dummy regulator
[ 2.163173] imx6q-pcie 33800000.pcie_ep: PLL REF_CLK is used!.
[ 2.173755] imx6q-pcie 33800000.pcie_ep: PCIe PLL locked after 20 us.

and /sys/class/pci_epc/ controller is working, so I can set a pcie test function.

The problem is, the x86 root complex of my system does not detect the imx8 configured in end point.

Now I'm stuck here. Do you guys know what to check ? Any advice to help me debugging ?

Edit :
I had to use the EXT REF_CLK and boot the EP after the RC, so I suppose its clk is available on the PCIe connector. Then I can set a PCIe test function thanks to /sys/class/pci_epc/ controller and detect a device on the RC side.

0 Kudos

1,003 Views
Guohua_Liu
Contributor I

Sorry for replying so late. Because of some high priority tasks we have not been working on it for some days. Before my last reply, our hardware engineer modified the hardware, he swapped the rx/tx, cut off power supply of pcie port and disconnected the clock source from the pcie. We also enabled EP feature in kernel configuration. It seems that host PC can detect the board, but the R/W test fails as you mentioned above.

We just compiled a new boot image with yocto, the kernel version of which is 5.10.72, but unfortunately we failed to burn it with uuu even to official imx8mm-evk board. A strange thing is that the size of our "imx-boot-imx8mmddr4evk-sd.bin-flash_ddr4_evk" is 3552KB which is much bigger than the size (1962KB) of the one I download from official web site, the later can easily be burned  to the official evk board.

Any one who can give some advice? Thanks in advance.

0 Kudos

997 Views
antho
Contributor II

Hi,

Do you flash into an emmc storage ? I had a very similar problem :

MMC memory chips have a boot hardware partition (write protected). You can check it size by running in u-boot=> mmc info
Look for "Boot Capacity". Mine was 2MB, which was okay for yocto Warrior imx-boot image but not big enough for yocto Zeus image of 3.5MB.

Solutions :
-you can resize the mmc boot partition (it didn't work)
-you can move the bootloader to the main partition (but it won't be protected)
-you can reduce the imx-boot size by removing some feature. I removed the optee binary (2.1MB) in the distro config file. And it worked !

0 Kudos

1,143 Views
antho
Contributor II

Hi Igor,
I know this article from 2013. It is more an old validation and results note than a real tutorial to me.

It is base on an old kernel (imx_3.0.35 ?). I don't even find the drivers files that have to be patched (arch/arm/mach-mx6/pcie.c or mxc_ipudev_test.c). We don't even know what the attached test program is supposed to do (no source code).

Sorry, but this is not helping me.

Please, do you have more recent application notes about PCIe in EP mode ?

I'm planning to jump to kernel 5.4, but it is going to take a while.

0 Kudos

1,165 Views
igorpadykov
NXP TechSupport
NXP TechSupport

Hi Anthony

 

for testing pcie one can look at tutorial

https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX6Q-PCIe-EP-RC-Validation-System/ta-p...

and sect.4.8 PCI Express Root Complex  i.MX Linux Reference Manual​

 

Best regards
igor

0 Kudos