Hello guys and thank you all your support. I really like how Sierra Wireless designed this modem and how clear the documentation is. I am a newbie and a DIY’er for IoT.
Provided voltage but not exactly 1.8, because the manual says it can accept min and max High 1.6 – 5.25 - therefore I assume any voltage between – so I measured 3.8V. could add a pull-up resitor of 1.8kO with around 0.0011A for 1.8V … is it necessary???
Sorry for being silly but what would be the reason not to work between the spec sheet voltage?
Any reason not to work with USB3.0 – will work only with USB3.1???
Have tried to install a EM9293 on a RHEL 10 with all drivers loaded and still no modem found.
here is an output
Feb 12 22:11:45 x5test kernel: usbcore: registered new interface driver option
Feb 12 22:11:45 x5test kernel: usbserial: USB Serial support registered for GSM modem (1-port)
Feb 12 22:11:49 x5test sudo[1911]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c ‘echo '1199 90e3' > /sys/bus/usb-serial/drivers/option1/new_id’
Feb 12 22:12:32 x5test kernel: usbcore: registered new interface driver qcserial
Feb 12 22:12:32 x5test kernel: usbserial: USB Serial support registered for Qualcomm USB modem
Feb 12 22:12:36 x5test kernel: usbcore: registered new interface driver cdc_wdm
Feb 12 22:12:36 x5test kernel: usbcore: registered new interface driver qmi_wwan
Feb 12 22:12:41 x5test kernel: usbcore: registered new interface driver cdc_ether
Feb 12 22:12:41 x5test kernel: usbcore: registered new interface driver cdc_ncm
Feb 12 22:12:41 x5test kernel: usbcore: registered new interface driver cdc_mbim
Feb 12 22:14:13 x5test sudo[1939]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c ‘echo '1199 90e3' > /sys/bus/usb-serial/drivers/option1/new_id’
root@x5test ~]# lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 20000M/x2
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 006: Dev 002, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 006: Dev 002, If 1, Class=Wireless, Driver=btusb, 12M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
In fact the procedure is clear
begin default
Always High VBUS -
VBUS_SENSE PD USB Detection Input High 1.6 – 5.25
end default
boot into pcie
else usb
PCIE_DIS PD Host interface selection Input
High 1.5 - 1.80 - 2.10
end
Hello — sure, I.ve seen it. thanks for sharing still yet why PCIE_DIS only accepts 2.10V max? that’s like 1/2 VCC in some cases …
Anyway – love the design but I think that I need to design a custom board for my application. As for now … adding a rezistor is the easiest to go. Thanks for sharing … I love the over complication that this developer did …
I’m really struggling to understand the min/max value of your voltage regulator, in order to have PD—Digital input (internal pull down) -300mV to 2.1V it’s quite some Khz away … what is the real max Vin, if Analog output, cannot be greater than 4.4V which is the max Input of the VCC.
In other words, this PD—Digital input (internal pull down) ---- resistor … 4.4 to 3.1 or 3.8 to 3.63V – therefore – the remaining minimum voltage. As in max aperage?? 2.1V / xWatts // however
the LDO which I could find would be 1.65 to 2.1 — but cannot find one that can stay at 2.1 it goes to 3.6 min and 5V
would 3.6v burn the ldo or the virtual switch for the PCIE_DIS?.
Bus 004 Device 002: ID 1199:90e3 Sierra Wireless, Inc. Sierra Wireless EM9293
[root@localhost ~]# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated] Sierra Wireless EM9293
