Clearfog Pro - MPCIE LTE Card (Quectel EC25) Not Detected

Hello,

The card in question is described here: Link.

I’ve tried both slots and neither are detecting the card in u-boot or the kernel. The card is confirmed to work in another box. The slots on the CN9130 both function having tested with an 802.11 card. I did roll my own kernel using solidrun’s build environment to include necessary modules. The EC25 card isn’t power hungry; my supply should be adequate.

Console output isn’t particularly interesting to my untrained eye (PCIE2 is populated with my 802.11 card. The EC25 is in the other slot, closest to the SOC:

Starting AP IOROM 1.02
Booting from eMMC 0
Found valid image at boot postion 0x004
lNOTICE:  Starting binary extension
NOTICE:  SVC: DEV ID: CN913x, FREQ Mode: 0x0
NOTICE:  SVC: AVS work point changed from 0x2e3 to 0x2db
w/o ecc; strap value=0
4GB capacity; strap value=0
mv_ddr: 14.0.0-g3afcac0 (Jul 07 2022 - 19:20:34)
SSCG_EN
Synopsys DDR43 PHY Firmware version: A-2017.11
SNPS DDR: 1D training passed
SNPS DDR: 2D training passed
SNPS DDR: training completed
dma memcmp pass
mv_ddr: completed successfully
NOTICE:  Cold boot
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.3(release):v2.3-864-gfa3b71394 (Marvell-devel-18.12.0)
NOTICE:  BL1: Built : 19:20:34, Jul  7 2022
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.3(release):v2.3-864-gfa3b71394 (Marvell-devel-18.12.0)
NOTICE:  BL2: Built : 19:20:35, Jul  7 2022
NOTICE:  SCP_BL2 contains 7 concatenated images
NOTICE:  Skipping MG CP1 related image
NOTICE:  Load image to CP0 MG
NOTICE:  Loading MG image from address 0x403114c Size 0xe0f0 to MG at 0xf2100000
NOTICE:  Skipping MSS CP3 related image
NOTICE:  Skipping MSS CP2 related image
NOTICE:  Skipping MSS CP1 related image
NOTICE:  Load image to CP0 MSS AP0
NOTICE:  Loading MSS image from addr. 0x4044930 Size 0x1cfc to MSS at 0xf2280000
NOTICE:  Done
NOTICE:  Load image to AP0 MSS
NOTICE:  Loading MSS image from addr. 0x404662c Size 0x5400 to MSS at 0xf0580000
NOTICE:  Done
NOTICE:  BL1: Booting BL31
lNOTICE:  BL31: v2.3(release):v2.3-864-gfa3b71394 (Marvell-devel-18.12.0)
NOTICE:  BL31: Built : 19:20:35, Jul  7 2022

U-Boot 2019.10-10.0.0-00016-g1e7b1b0bab (Jul 07 2022 - 19:20:32 +0000)

Model: SolidRun CN9130 based SOM ClearFog Pro
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
SoC: cn9130-A1; AP807-B0; CP115-A0
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
Clock:  CPU     2000 [MHz]
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
        DDR     1200 [MHz]
ERROR:   mrvl_sip_smc_handler: unhandled SMC (0x82000014)
        FABRIC  1200 [MHz]
        MSS     200  [MHz]
LLC Enabled (Exclusive Mode)
DRAM:  4 GiB
Running in RAM - U-Boot at: 0x7fef0000
                 Env at:    0x7ff9bfe6
Comphy chip #0:
Comphy-0: SATA1
Comphy-1: USB3_HOST0
Comphy-2: SFI0          10.3125 Gbps
Comphy-3: SGMII1        1.25 Gbps
Comphy-4: PEX1
Comphy-5: PEX2
UTMI PHY 0 initialized to USB Host0
UTMI PHY 1 initialized to USB Host1
PCIE-0: Link down
PCIE-2: Link up (Gen1-x1, Bus2)
NAND:  0 MiB
MMC:   sdhci@6e0000: 0, sdhci@780000: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

get_fdtfile_from_tlv_eeprom: could not identify carrier, defaulting to Clearfog Pro!
Net:
Error: mvpp2-0 address not set.

Error: mvpp2-0 address not set.

Error: mvpp2-1 address not set.

Error: mvpp2-2 address not set.
eth-1: mvpp2-0
Error: mvpp2-1 address not set.
, eth-1: mvpp2-1
Error: mvpp2-2 address not set.
, eth-1: mvpp2-2
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
223 bytes read in 10 ms (21.5 KiB/s)
1:      primary kernel
Retrieving file: /boot/Image
33759744 bytes read in 2075 ms (15.5 MiB/s)
append: console=ttyS0,115200 root=PARTUUID=30303030-01 rw rootwait
Retrieving file: /boot/marvell/cn9130-cf-pro.dtb
24929 bytes read in 25 ms (973.6 KiB/s)
## Flattened Device Tree blob at 06f00000
   Booting using the fdt blob at 0x6f00000
   Loading Device Tree to 000000007f5ce000, end 000000007f5d7160 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
[    0.000000] Linux version 5.15.0devkernel-00009-g0d215743bc4b (devon@ddsk) (aarch64-linux-gnu-gcc (Linaro GCC 7.5-2019.12) 7.5.0, GNU ld (Linaro_Binutils-2019.12) 2.28.2.20170706) #2 SMP PREEMPT Sat Jul 23 12:19:32 EDT 2022
[    0.000000] Machine model: SolidRun CN9130 based SOM Clearfog Pro
...

Any tips on how I may continue troubleshooting?

Loving the board so far - so many possibilities.

Thanks,

Devon

an EC25 modem connects to the mPCIe slot but uses usb 2.0 as the connected protocol. Can you please provide the output of lsusb -t? Additionally the EC25 requires the protocols wlan_en and perst to be handled. It is possible that these are not being set properly so the modem is not intializing.

Well, now I feel silly. Returning the card to mpcie slot 1, furthest from soc, the card is now detected. Makes sense considering per the block diagram, that slot supports usb. Compared to last time I tested this slot, the only change is that I placed a small silicone washer over the half-size standoff. It’s a full-size card and the standoff was contacting components on the underside of the card. Here’s the related output:

> dmesg
[    7.084316] usb 1-1: new high-speed USB device number 4 using xhci-hcd
[    7.118596] option 1-1:1.0: GSM modem (1-port) converter detected
[    7.118746] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[    7.118886] option 1-1:1.1: GSM modem (1-port) converter detected
[    7.118974] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[    7.119112] option 1-1:1.2: GSM modem (1-port) converter detected
[    7.119215] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[    7.119379] option 1-1:1.3: GSM modem (1-port) converter detected
[    7.119497] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[    7.143406] libphy: mv88e6xxx SMI: probed
[    7.147066] usbcore: registered new interface driver cdc_wdm
[    7.151725] cdc_ether 1-1:1.4 usb0: register 'cdc_ether' at usb-f2500000.usb-1, CDC Ethernet Device, 2a:a4:f6:fe:25:af
[    7.151898] usbcore: registered new interface driver cdc_ether
[    7.152475] usbcore: registered new interface driver qmi_wwan
[    7.167374] cdc_ether 1-1:1.4 enx2aa4f6fe25af: renamed from usb0

> lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=option, 480M
    |__ Port 1: Dev 4, If 1, Class=Vendor Specific Class, Driver=option, 480M
    |__ Port 1: Dev 4, If 2, Class=Vendor Specific Class, Driver=option, 480M
    |__ Port 1: Dev 4, If 3, Class=Vendor Specific Class, Driver=option, 480M
    |__ Port 1: Dev 4, If 4, Class=Communications, Driver=cdc_ether, 480M
    |__ Port 1: Dev 4, If 5, Class=CDC Data, Driver=cdc_ether, 480M

So, this is probably solved. I’ll report back once I get it working and should I encounter anything interesting/helpful to others. Apologies for the oversight.

Devon

Is the single uSim slot on this board only accessible by MPCIE slot 0 or to both? It’s unclear to me between the block diagram and board layout, and the EC25 card is not detecting the sim from MPCIE1.

The SIM holders are only accessible to the mPCIe slots closest to them. You can verify this on the carrier schematic where the signals are labeled as UIM*

I see. That’s too bad. I guess that means this board cannot support LTE cards like mine and really limits options, as most cards on the market seem to use USB as a data interface. I’ll try to source an appropriate card and report back if I find one.

I don’t understand what the issue is. Each mPCIe slot has its own sim-card holder, however only one is populated by default. Both mPCIe slots also support USB as well as PCIe.

Allow me to summarize. I’m including a couple photos to assure we’re on the same page. My board is the Clearfog-A1, Revision 2.2.

Block diagram from Clearfog Pro wiki:

The block diagram only lists one mPCIe slot as supporting USB. This matches my observations which include:

  • EC25 card does not initialize and is invisible to kernel if in slot #0
  • Intel 7260 (wifi+bt) card doesn’t initialize bluetooth if in slot #0, as it too depends on USB
  • USB-dependent features of both cards work when in slot #1

My populated board:

Understood that the SIM card holder on the board is tied to slot #0. Whereabouts on the board would one solder a secondary SIM holder?

Thanks, and apologies once again if I’m misunderstanding the layout/features/settings of this board.

You are correct and it was my misunderstanding. I have already brought the issue up with the hardware team. I thought that with the new SOM both USB 2.0 connections were active, but that is not the case. For the CON3 mPCIe slot the push-pull SIM assembly is on the bottom of the board right under the slot.

Great. I see it and can make that work. But, it’s a tight spot. Can your hardware guys perhaps recommend a part appropriate for that space? A nano push/pull assembly works for my purposes, but my initial searches on Mouser look not to be easily adaptable. I’ll keep searching, but a known, properly sized part# would very helpful.

The schematic has it spec’d for SF56S006V4B

Thanks. That part appears to be discontinued and unavailable. Recommended alternative is the following. I’m comparing pinouts to see if this will work.

SF56K006VBAR2000

I will check with them.