Project

General

Profile

Sierra Wireless Modems » History » Version 1

laforge, 01/09/2017 12:02 PM

1 1 laforge
h1. Sierra Wireless Modems
2
3
Sierra Wireless also seems to offer a number of modems that run on MDM9615 or its successors, with Linux inside the module.
4
5
h2. List of related modems
6
7
* EM7455
8
* many others suspected, FIXME.
9
10
h2. Getting access to the Linux system
11
12
Sierra Wireless uses a bitmapped NVRAM variable to tell the system which functions to enable. One of these functions is 'adb'. They also implement an AT command to set this variable, but you cannot enable 'adb' there anymore (or maybe you can, using some other password?).
13
14
This AT command help text is taken from an old memory dump:
15
16
<pre>
17
#AT!USBCOMP=<Config Index>,<Config Type>,<Interface bitmask>
18
#  <Config Index>      - configuration index to which the composition applies, should be 1
19
#  <Config Type>       - 1:Generic, 2:USBIF-MBIM, 3:RNDIS
20
#                        config type 2/3 should only be used for specific Sierra PIDs: 68B1, 9068
21
#                        customized VID/PID should use config type 1
22
#  <Interface bitmask> - DIAG     - 0x00000001,
23
#                        ADB      - 0x00000002,
24
#                        NMEA     - 0x00000004,
25
#                        MODEM    - 0x00000008,
26
#                        RMNET0   - 0x00000100,
27
#                        RMNET1   - 0x00000400,
28
#                        RMNET2   - 0x00000800,
29
#                        MBIM     - 0x00001000,
30
#                        RNDIS    - 0x00004000,
31
#                        AUDIO    - 0x00010000,
32
#                        ECM      - 0x00080000,
33
#                        UBIST    - 0x00200000
34
</pre>
35
36
There are other ways to set this and other variables, so the AT comand interpreter restriction is not a show stopper.  Note that there are invalid gadget combinations, so you can softbrick the modem by changing this variable.
Add picture from clipboard (Maximum size: 48.8 MB)