i.MX8MP PCI issue

cancel
Showing results for 
Search instead for 
Did you mean: 

i.MX8MP PCI issue

Jump to solution
328 Views
ABDNI
Contributor I
 

Hi

I have bought the Variscite evaluation kit, so I am using a VAR-SOM-MX8M-PLUS and Symphony board together.

I am using Debian Bullseye OS. Image: imx8mp-var-dart-debian-bullseye-5.10.52-v1.0.img.gz

When de-risking the board and testing all required interfaces. I encountered a problem with the PCI interface (mPCIe connector). I will be using an EG25-G mPCIe cellular module in the project.

Not sure how to continue troubleshooting this. Do you have any solutions/recommendations? Also let me know if there are any other outputs or diagnostics that would be helpful.

I receive no output from lspci when using the Quectel EG25-G, Telit LE910C1-AP, FN-Link 6222D-UUB and when using no mPCIe device.

Thanks heaps in advance.


Diagnostic Messages:

root@CEI:~# dmesg | grep pci
[ 0.173369] imx8-pcie-phy 32f00000.pcie-phy: failed to get imx pcie phy clock
[ 1.747826] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator
[ 1.763352] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!.
[ 1.769545] imx6q-pcie 33800000.pcie: PCIe PHY PLL clock is locked.
[ 1.831769] imx6q-pcie 33800000.pcie: PCIe PLL locked after 0 us.
[ 1.842990] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[ 1.855747] imx6q-pcie 33800000.pcie: No bus range found for /soc@0/pcie@33800000, using [bus 00-ff]
[ 1.870637] imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000
[ 1.886290] imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000
[ 1.902093] imx6q-pcie 33800000.pcie: invalid resource
[ 2.911739] imx6q-pcie 33800000.pcie: Phy link never came up
[ 2.917459] imx6q-pcie 33800000.pcie: failed to initialize host
[ 2.923420] imx6q-pcie 33800000.pcie: unable to add pcie port.

0 Kudos
1 Solution
300 Views
ABDNI
Contributor I

The reason for the issue was the the Variscite Symphony board's mPCIe interface doesn't support USB communication, pins 36 and 38 are left un-routed on the carrier board. The mPCIe cellular modules that I was testing with require USB support to function.

View solution in original post

0 Kudos
1 Reply
301 Views
ABDNI
Contributor I

The reason for the issue was the the Variscite Symphony board's mPCIe interface doesn't support USB communication, pins 36 and 38 are left un-routed on the carrier board. The mPCIe cellular modules that I was testing with require USB support to function.

0 Kudos