Sierra Wireless MBPL drivers

Start by finding the latest Mobile Broadband Package for Linux (MBPL) on our website.

That zip file does contain:

Drivers
- USB
- PCIe
SDK
- Firmware Download Tool
- DM-logger tool
- Sample apps
- And a bunch more

To be able to send this zip file from your Windows to your Linux System, please see the following FAQ

How to send files, maps and zip files from your Windows system to your Linux system

Comment - This guide was done using a Raspberry Pi 5 with an MC201 adapter and an EM9293 module. This works on other Linux-based systems as well.

When we have the MBPL zip file transferred to our Linux system, we can start by setting up the drivers for our Sierra Wireless module.

To maintain an organized system, we create a folder within the Downloads folder called something like MBPL, where we place the zip file

mkdir MBPL

If you didn't place the MBPL zip file in the correct folder, you can quickly move it by sending, just remember that you need to be in the active folder and verify that the names are correct for both the file and the folder

mv [mobilebroadbandoackagelinuxr43.zip] [MBPL]

Then, after that, we need to unzip the file to access what is inside:

unzip mobilebroadbandpackagelinuxr43.zip

Now we can start the setup of the drivers

Go into the now unzipped folder
```
cd mobilebroadbandpackagelinuxR43
```

Make a name shift because Linux does have an issue with folders with names including a blank space
```
mv "Driver Binaries" Driver_Binaries
```
Then we need to jump into the next folder and unzip the drivers we want to use for our systems. In this example, we are using the USB drivers.
```
cd Driver_Binaries\
tar xvf MBPL_DRIVERS_R43_ENG1-usb-pcie-src.tar.gz
cd usb
```
Now its time to install the drivers, and that is done by sending the two commands underneath

make
make install

The supposed output should look something like this

make

rpi5@rpi5:~/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb $ make
make -C /lib/modules/6.6.62+rpt-rpi-2712/build M=/home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb
make[1]: Entering directory '/usr/src/linux-headers-6.6.62+rpt-rpi-2712'
  CC [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/qcserial.o
  CC [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/usb_wwan.o
  CC [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/qmi_wwan.o
  MODPOST /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/Module.symvers
  CC [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/qcserial.mod.o
  LD [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/qcserial.ko
  CC [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/usb_wwan.mod.o
  LD [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/usb_wwan.ko
  CC [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/qmi_wwan.mod.o
  LD [M]  /home/rpi5/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb/qmi_wwan.ko
make[1]: Leaving directory '/usr/src/linux-headers-6.6.62+rpt-rpi-2712'

make install

rpi5@rpi5:~/Downloads/Drivers_MBPL_R43/mobilebroadbandpackagelinuxR43/Driver_Binaries/usb $ make install
if [ -f /lib/modules/`uname -r`/kernel/drivers/usb/serial/qcserial.ko.zst ]; then \
zstd -f qcserial.ko; sudo cp qcserial.ko.zst /lib/modules/`uname -r`/kernel/drivers/usb/serial/qcserial.ko.zst; \
zstd -f usb_wwan.ko; sudo cp usb_wwan.ko.zst /lib/modules/`uname -r`/kernel/drivers/usb/serial/usb_wwan.ko.zst; \
zstd -f qmi_wwan.ko; sudo cp qmi_wwan.ko.zst /lib/modules/`uname -r`/kernel/drivers/net/usb/qmi_wwan.ko.zst; \
else \
sudo cp qcserial.ko /lib/modules/`uname -r`/kernel/drivers/usb/serial/qcserial.ko; \
sudo cp usb_wwan.ko /lib/modules/`uname -r`/kernel/drivers/usb/serial/usb_wwan.ko; \
sudo cp qmi_wwan.ko /lib/modules/`uname -r`/kernel/drivers/net/usb/qmi_wwan.ko; \
fi 
sudo depmod

Now the drives are installed into our system, and just to verify that the installation went correctly, we reboot the system

sudo reboot

Then, when our system is up and running again, we just need to verify that the drivers are correctly installed and attached. We do so by sending the following commands:

lsusb
lsusb -t

And they should produce similar responses to the following

lsusb

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1199:90e3 Sierra Wireless, Inc. Sierra Wireless EM9291
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:086b Logitech, Inc. BRIO 4K Stream Edition
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Communications, Driver=cdc_mbim, 5000M
    |__ Port 1: Dev 2, If 1, Class=CDC Data, Driver=cdc_mbim, 5000M
    |__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=qcserial, 5000M
    |__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=qcserial, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
    |__ Port 2: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 2: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 2: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 2: Dev 2, If 3, Class=Audio, Driver=snd-usb-audio, 480M

Now you have been able to install the MBPL drivers for your Sierra Wireless module.

If you are experiencing any issues, feel free to create a ticket here: https://techship.com/account/support/new/

And we will assist you with your issues. Remember to clearly explain the issue and provide logs from above, which will simplify the troubleshooting on our end.