i use Ubuntu 18/20/24 in desktop version via USB communication
You can download the linux driver “MBPL_DRIVERS_R48_ENG4-usb-pcie-src.tar” here:
one question how your modem is connected for flashing? directlly in PCIE slot through an adapter b-key → nvme or through an adapter b-key to USB port? Actually Im connected to PCIE M.2 and I have only those devices:
root@E3C:~# ls -ltr /dev/ttyU*
ls: cannot access ‘/dev/ttyU*’: No such file or directory
root@E3C:~# ls -ltr /dev/mhi*
ls: cannot access ‘/dev/mhi*’: No such file or directory
root@E3C:~# ls -ltr /dev/wwa*
crw------- 1 root root 511, 2 Jul 10 16:16 /dev/wwan0qmi0
crw------- 1 root root 511, 0 Jul 10 16:16 /dev/wwan0qcdm0
crw------- 1 root root 511, 1 Jul 10 16:16 /dev/wwan0mbim0
crw------- 1 root root 511, 3 Jul 10 16:16 /dev/wwan0at0
i connect through USB port
yes but it changes nothing:
AT!USBCOMP?
Config Index: 1
Config Type: 4 (MBIM V2)
Interface bitmask: 00001009 (diag,modem,mbim)
aren’t you connecting by PCIe?
why are you configuring AT!USBCOMP?
BTW, from the readme file of the fw-download tool, it supports PCIe interface:
-p --devpath <QMI/MBIM device path>
For SDX12 and SDX35 modems, this command is not used.
For other modems, this command is available but no longer needed for single modem scenarios.
Specifies the QMI or the MBIM device path.
Example:
- "-p /dev/cdc-wdm0" for a USB modem (either MBIM or RmNet interface)
- "-p /dev/mhi_0306_00.01.00_pipe_12" for PCIe MBIM interface
- "-p /dev/mhi_0306_00.01.00_pipe_14" for PCIe QMI interface
-d --qdl <QDL port>
For SDX12 or SDX35 modems (-m 6), this command is used to specify the device AT port as the download path.
Example: "-d /dev/ttyUSB2"
For other modems, this command is available but no longer needed for single modem scenarios.
Specifies the QDL port while the modem is in download mode during a FW download.
Example: "-d /dev/mhiqdl0" for PCIe device or "-d /dev/ttyUSB0" for USB device
Problem is there: /dev/mhi* >>> nothing
Compiled MBL modules make nothing new here:
qcserial.ko
usb_wwan.ko >> problably not needed for PCIE mode
qmi_wwan.ko
This tool has no chance to work with PCIE/MHI with new wwan framework/kernel:
root@E3C:/home/orangepi/work/soft/SampleApps/Static/fw-download-tool/bin# strings fw-download-toolhostx86_64 | grep -i “/dev/mhi”
/dev/mhi
Example: -d /dev/mhiqdl0 or -d /dev/ttyUSB2
Example: -p /dev/mhi_0306_00.01.00_pipe_12
/dev/mhi
/dev/mhiqdl0
/dev/mhi_%04d_%02d.%02d.%02d_pipe_12
/dev/mhi_%04d_%02d.%02d.%02d_pipe_14
/dev/mhi0_SAHARA
Those MHI devices are old fashion… I need to take very old Ubuntu and try 
did you install the correct PCIe driver “MBPL_DRIVERS_R48_ENG4-usb-pcie-src.tar” in linux?
yes I did but Im afraid it could be not possible to work out… Look, I m going back to the kernel 5 Ubuntu 20 but MBL drivers are really fresh… It can happen I would rewrite them for the old kernel to fit 
What kernel are you using?
Openwrt 6.18.35 and Ubuntu 7.0.
Never mind, to clarify the situation I will open new topic and explain all and why
The mbpl driver should be supporting kernel 4.4 or newer
This is not true! If we have a lot of changes in kernel drivers should be changed too Sometimes it is completely new approach / framework etc 
For instance here initially I had had an issue with 5GNSA and EM9291 modem. Huge download makes the communication stale although the communication modem ↔ BTS is ok and reporting connected , no errors sometimes “Event element points to an unexpected TRE” indicating problems on RX rings as desynchronisation.
Solution?
- Maybe some approvement with antennas to get more signal gain (in progress but it is for sure no radio issue)
- Upgrade firmware (still issues as above in thread)
- Patches for MHI or/and MHI_NET (in progress - after some first tests indeed here is the problem)
Ubuntu 7 is using a kernel version 2.6, so it is not supported …
What is the problem of using the mbpl pcie driver in kernel 6.18? Cannot compile?
Which firmware is using in your EM92 module?
qmicli -d /dev/wwan0qmi0 --dms-swi-get-current-firmware
[/dev/wwan0qmi0] Successfully retrieved current firmware:
Model: EM9291
Boot version: SWIX65C_02.17.08.00
AMSS version: SWIX65C_02.17.08.00
SKU ID: 1105271
Package ID: unknown
Carrier ID: 1
Config version: 030.081_001
Ubuntu 7 is using a kernel version 2.6, so it is not supported …
he he kernel 7.0, Ubuntu 26.04 TLS
Sierra MBL drivers use old fashion mhi framework - since long time there is no more /dev/mhi* devices as all is replaced and migrated to:
crw------- 1 root root 511, 2 Jul 10 16:16 /dev/wwan0qmi0
crw------- 1 root root 511, 0 Jul 10 16:16 /dev/wwan0qcdm0
crw------- 1 root root 511, 1 Jul 10 16:16 /dev/wwan0mbim0
crw------- 1 root root 511, 3 Jul 10 16:16 /dev/wwan0at0
However precompiled Sierra flashing tools still refer to /dev/mhi* devices as I put somewhere above in the thread so by now no way to flash on PCI. I was thinking to make a link old mhi devices to new ones and try but I guess linkining it is not all
Do you mean it is Ok if you are using kernel 5 Ubuntu 20?
FYI, if using the MBPL driver and compile in the linux PC, it should be OK to download firmware:
root@xxx-ET1861:/home/xxx/Desktop/SWI/fw-download-tool# sudo ./bin/fw-download-toolhostx86_64 -c QMI -p /dev/mhi_0308_00.06.00_pipe_14 -f /home/xxx/Desktop/SWI/fw-download-tool -s test_firmware.cwe
Application version: 1.0.2412.2
INFO: QDL Port: /dev/mhiqdl0
INFO: Device Path: /dev/mhi_0308_00.06.00_pipe_14
INFO: Device Port: 0-0
INFO: FW Path: /home/xxx/Desktop/SWI/fw-download-tool
Switching device into download mode ...
Waiting for modem to disconnect from the host ...
Modem disconnected from host.
Waiting for modem to come up in BOOT and HOLD mode ...
BOOT and HOLD Mode. Downloading firmware ...
Downloading: /home/xxx/Desktop/SWI/fw-download-tool/test_firmware.cwe
All image data was downloaded successfully.
Device is about to reset ...
Waiting for modem to come up in ONLINE mode ...
Modem is now in ONLINE mode ...
FW update status: Successful
FW info from modem:
Model ID : EM9291
FW Version : SWIX65C_02.17.08.00
Carrier Name : GENERIC
Carrier PRI Revision: 030.081_001
Firmware download process completed successfully.
I probably fixed all my issues but some strange results:
- mhi dirver fixes needed
- pci_generic.c adjusted
- some OS parameters too
- firmware upgrade not done still
What is strange I was not succesful to fix MHI issue in bananapi bpi-r4. All works on miniPC E3C. ARM vs x64 architecture? Also very disappointing that bananpi bpi-r4 limits PCI to only 1 lane as em9291 has capability of 2. The same but expected with NVME-> BKey adapter used in E3C but I met nowhere such a one with 2 lanes…
Huge download makes modem generating a lot of heat so we need to think about temp control.