For our 7455 modems which firmware should we download? Generic? Sierra Wireless? Verizon? And why? We have Verizon SIMs, by the way.
What is the recommended AT!IMPREF=??? setting? GENERIC? VERIZON? VZW? AUTO-SIM? And, again, why?
Thanks for everyones’ patience – just diving in headfirst and trying to get this all sorted out.
Hi Perry,
If you are using Verizon SIM, you can download firmware for Verizon carrier.
The latest firmware is here: https://source.sierrawireless.com/resources/airprime/minicard/74xx/airprime-em_mc74xx-approved-fw-packages/#sthash.Ygdnwsbc.dpbs
For EM/MC7455 you can load many packages to the devices, you can use AT!IMAGE? to list all firmware releases.
And AT!IMPREF="" command is used to select which carrier will be used.
Example: I loaded 2 carriers: GENERIC and SIERRA, and I used AT!IMPREF to switch these carriers as below:
at!impref?
!IMPREF:
preferred fw version: 02.35.02.00
preferred carrier name: GENERIC
preferred config name: GENERIC_001.064_001
preferred subpri index: 000
current fw version: 02.35.02.00
current carrier name: GENERIC
current config name: GENERIC_001.064_001
current subpri index: 000
OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 FOTA 129 0 0 ?_? 02.32.02.00_?
FW 2 FOTA 128 0 0 001.028_002 02.16.06.00_GENERIC
FW 3 GOOD 130 0 0 001.064_001 02.35.02.00_GENERIC
Max FW images: 3
Active FW image is at slot 3
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 001.064_001 02.35.02.00_GENERIC
PRI FF GOOD 0 0 0 001.036_001 02.35.02.00_SIERRA
Max PRI images: 50
OK
at!impref="SIERRA"
OK
at!reset
OK
at!impref?
!IMPREF:
preferred fw version: 02.35.02.00
preferred carrier name: SIERRA
preferred config name: SIERRA_001.036_001
preferred subpri index: 000
current fw version: 02.35.02.00
current carrier name: SIERRA
current config name: SIERRA_001.036_001
current subpri index: 000
OK
+CREG: 2
+CGREG: 2
+CEREG: 2
at!impref?
!IMPREF:
preferred fw version: 02.35.02.00
preferred carrier name: SIERRA
preferred config name: SIERRA_001.036_001
preferred subpri index: 000
current fw version: 02.35.02.00
current carrier name: SIERRA
current config name: SIERRA_001.036_001
current subpri index: 000
OK
Hope it can help.
Thanks,
Thank you for the reply. I am familiar with the AT commands required to list available images and set the preferred image. I am trying to understand what the relative plusses and minuses are of using the different available firmware images, and the relative benefits of setting GENERIC, SIERRA, VERIZON, or simply AUTO-SIM.
Why would I prefer the Verizon firmware over GENERIC or Sierra, for example?
Why not just set AT!IMPREF=“AUTO-SIM”, and use Sierra Wireless firmware?
What are the differences between the firmware available for download? Is it just the PRI configurations? Or is there more to it?
Thanks again
Hi,
The configuration of Verizon is different than other carrier.
Because you said you use Verizon SIM, so I suggest using the Verizon image is the best.
Beside that, if you plan to use different carriers, you can configure “AUTO-SIM”, after inserting SIM to device, device is reboot. And it will check the SIM and load with the stored PRI
If there is no image that matches with that SIM, the Generic will be launched.
Because the device has to check the PRI of the SIM to launch the image, so the booting time is longer than when you select the specific image.
And if you select “AUTO-SIM”, when you remove/insert SIM, the device will be reboot.
If the specific image is selected, device will not reboot when removing/inserting new SIM.
Thanks,
I thought I would throw out some breadcrumbs for anyone seeking guidance on Sierra Wireless firmware. The firmware itself is not carrier-specific, except certain versions may be untested or problematic with certain carriers – therefore earlier firmware versions (.cwe files) are offered in combination certain PRI provisioning files (.nvu files).
The PRI files for ‘Generic’ contain provisioning information for numerous carriers, in addition to a default generic PRI.
I’ve chosen to download ‘Generic’, since it has the latest firmware available and happens to contains PRI information for Verizon, my carrier.
I could speed up the initial modem discovery/connection step by executing AT!IMPREF=“VERIZON”
If anyone from Sierra is reading this, please jump in and correct me where I’m wrong.
The carrier specific .nvu files may contain a number of settings and files as required by that carrier. Looking at one of the Verizon files I see that there are two CA certificates included. I have no idea if these are necessary or optional or what, but I assume there is a reason they were included in the firmware file.
openssl text dumps of /cert_swi/omadm/cert1.der:
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
18:da:d1:9e:26:7d:e8:bb:4a:21:58:cd:cc:6b:3b:4a
Signature Algorithm: sha1WithRSAEncryption
Issuer: C = US, O = "VeriSign, Inc.", OU = VeriSign Trust Network, OU = "(c) 2006 VeriSign, Inc. - For authorized use only", CN = VeriSign Class 3 Public Primary Certification Authority - G5
Validity
Not Before: Nov 8 00:00:00 2006 GMT
Not After : Jul 16 23:59:59 2036 GMT
Subject: C = US, O = "VeriSign, Inc.", OU = VeriSign Trust Network, OU = "(c) 2006 VeriSign, Inc. - For authorized use only", CN = VeriSign Class 3 Public Primary Certification Authority - G5
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:af:24:08:08:29:7a:35:9e:60:0c:aa:e7:4b:3b:
4e:dc:7c:bc:3c:45:1c:bb:2b:e0:fe:29:02:f9:57:
08:a3:64:85:15:27:f5:f1:ad:c8:31:89:5d:22:e8:
2a:aa:a6:42:b3:8f:f8:b9:55:b7:b1:b7:4b:b3:fe:
8f:7e:07:57:ec:ef:43:db:66:62:15:61:cf:60:0d:
a4:d8:de:f8:e0:c3:62:08:3d:54:13:eb:49:ca:59:
54:85:26:e5:2b:8f:1b:9f:eb:f5:a1:91:c2:33:49:
d8:43:63:6a:52:4b:d2:8f:e8:70:51:4d:d1:89:69:
7b:c7:70:f6:b3:dc:12:74:db:7b:5d:4b:56:d3:96:
bf:15:77:a1:b0:f4:a2:25:f2:af:1c:92:67:18:e5:
f4:06:04:ef:90:b9:e4:00:e4:dd:3a:b5:19:ff:02:
ba:f4:3c:ee:e0:8b:eb:37:8b:ec:f4:d7:ac:f2:f6:
f0:3d:af:dd:75:91:33:19:1d:1c:40:cb:74:24:19:
21:93:d9:14:fe:ac:2a:52:c7:8f:d5:04:49:e4:8d:
63:47:88:3c:69:83:cb:fe:47:bd:2b:7e:4f:c5:95:
ae:0e:9d:d4:d1:43:c0:67:73:e3:14:08:7e:e5:3f:
9f:73:b8:33:0a:cf:5d:3f:34:87:96:8a:ee:53:e8:
25:15
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Basic Constraints: critical
CA:TRUE
X509v3 Key Usage: critical
Certificate Sign, CRL Sign
1.3.6.1.5.5.7.1.12:
0_.].[0Y0W0U..image/gif0!0.0...+..............k...j.H.,{..0%.#http://logo.verisign.com/vslogo.gif
X509v3 Subject Key Identifier:
7F:D3:65:A7:C2:DD:EC:BB:F0:30:09:F3:43:39:FA:02:AF:33:31:33
Signature Algorithm: sha1WithRSAEncryption
93:24:4a:30:5f:62:cf:d8:1a:98:2f:3d:ea:dc:99:2d:bd:77:
f6:a5:79:22:38:ec:c4:a7:a0:78:12:ad:62:0e:45:70:64:c5:
e7:97:66:2d:98:09:7e:5f:af:d6:cc:28:65:f2:01:aa:08:1a:
47:de:f9:f9:7c:92:5a:08:69:20:0d:d9:3e:6d:6e:3c:0d:6e:
d8:e6:06:91:40:18:b9:f8:c1:ed:df:db:41:aa:e0:96:20:c9:
cd:64:15:38:81:c9:94:ee:a2:84:29:0b:13:6f:8e:db:0c:dd:
25:02:db:a4:8b:19:44:d2:41:7a:05:69:4a:58:4f:60:ca:7e:
82:6a:0b:02:aa:25:17:39:b5:db:7f:e7:84:65:2a:95:8a:bd:
86:de:5e:81:16:83:2d:10:cc:de:fd:a8:82:2a:6d:28:1f:0d:
0b:c4:e5:e7:1a:26:19:e1:f4:11:6f:10:b5:95:fc:e7:42:05:
32:db:ce:9d:51:5e:28:b6:9e:85:d3:5b:ef:a5:7d:45:40:72:
8e:b7:0e:6b:0e:06:fb:33:35:48:71:b8:9d:27:8b:c4:65:5f:
0d:86:76:9c:44:7a:f6:95:5c:f6:5d:32:08:33:a4:54:b6:18:
3f:68:5c:f2:42:4a:85:38:54:83:5f:d1:e8:2c:f2:ac:11:d6:
a8:ed:63:6a
and /SUPL/SuplRootCert:
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
d6:95:e3:ee:04:31:3b:c3
Signature Algorithm: sha1WithRSAEncryption
Issuer: C = US, ST = Texas, L = Irving, O = NSN, OU = NLS, CN = 4.31.128.202, emailAddress = yankee.zheng@nsn.com
Validity
Not Before: Jun 24 21:08:26 2014 GMT
Not After : Jun 21 21:08:26 2024 GMT
Subject: C = US, ST = Texas, L = Irving, O = NSN, OU = NLS, CN = 4.31.128.202, emailAddress = yankee.zheng@nsn.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:9f:f2:79:20:ad:74:88:18:65:27:ce:ff:bb:a1:
f1:28:b0:bb:6f:41:50:0a:77:15:29:81:b0:6f:a5:
6d:8e:2f:de:49:c3:94:ce:f1:14:fa:19:73:4c:ae:
52:90:c3:6b:d7:25:ad:35:8e:00:34:17:49:cb:98:
62:85:73:1d:03:93:ec:4c:e7:6d:9b:ba:cf:18:5b:
17:14:8f:81:8e:67:8d:d0:05:20:17:96:05:99:9f:
61:22:e5:7b:84:09:14:ea:fa:61:ac:cc:9b:a1:8f:
aa:36:da:6a:3f:00:e6:35:ae:76:49:af:5e:62:36:
f2:26:b7:ab:ef:ce:c8:69:58:a1:e0:83:da:60:ba:
10:88:15:2e:f3:1e:26:ba:db:e0:5a:36:79:f1:c5:
12:81:26:16:9a:bb:7c:90:3f:a4:bb:73:7b:f5:d8:
c7:dd:bf:18:c1:43:4f:96:df:1d:3f:ed:cf:16:55:
10:6e:48:37:da:99:4e:6f:e2:08:d6:62:03:f0:bf:
bf:2b:19:cd:3e:a8:5b:9e:a0:c8:ff:81:81:3a:d4:
fc:a3:ce:af:b0:59:a1:b3:b8:96:75:3d:f8:31:a1:
d1:d7:7e:e2:87:16:28:50:fe:35:d5:6d:3c:ff:70:
d2:0d:19:78:e6:89:fc:a2:7d:69:65:fd:f5:a6:86:
ff:f1
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Key Identifier:
0F:46:64:38:0B:F3:1E:4E:24:05:F2:98:22:FB:EE:C7:35:E3:33:2C
X509v3 Authority Key Identifier:
keyid:0F:46:64:38:0B:F3:1E:4E:24:05:F2:98:22:FB:EE:C7:35:E3:33:2C
DirName:/C=US/ST=Texas/L=Irving/O=NSN/OU=NLS/CN=4.31.128.202/emailAddress=yankee.zheng@nsn.com
serial:D6:95:E3:EE:04:31:3B:C3
X509v3 Basic Constraints:
CA:TRUE
Signature Algorithm: sha1WithRSAEncryption
08:b0:06:06:0c:72:f2:20:93:25:31:86:0a:64:9b:49:99:e0:
18:e4:79:ed:1d:a8:18:05:94:e7:54:5c:e8:0d:7b:52:61:7b:
02:0b:6f:7b:7d:29:a6:e2:59:b0:bc:2e:4c:98:71:7e:db:8b:
18:dd:09:06:8e:6d:37:9a:8d:8f:01:a4:64:44:e1:e8:07:74:
79:43:71:f0:4b:4d:af:1a:fc:88:e0:17:51:b7:f4:da:46:83:
3c:ef:ef:ba:1d:c8:e5:54:43:8c:7b:a4:01:8f:17:56:8f:50:
42:d8:31:5f:88:be:07:6c:2f:37:ff:4d:a5:74:44:0a:d0:e6:
a0:b6:f0:03:e9:02:c9:08:a3:60:62:17:13:bb:f0:a2:10:7a:
19:9d:b3:c4:7d:5c:eb:13:c5:74:1b:2e:01:dd:0e:46:8d:b7:
1e:da:b8:6b:8e:7f:b2:e7:f5:5d:2d:fd:cc:e9:2b:82:5e:c6:
53:0f:a9:5d:8f:7c:27:f3:23:64:5d:21:b6:84:cb:7d:5c:35:
a8:f6:f8:2d:16:4e:db:c4:df:f8:f7:6f:62:7a:70:95:39:35:
38:74:01:cb:6d:7d:3f:90:00:a2:ae:a3:5a:08:fa:d7:f1:fc:
52:05:ab:ac:70:69:6e:67:98:29:8f:38:fb:33:f0:3d:15:e3:
5e:ab:9e:6dInteresting. Where did you find these files? Is the .nvu file some sort of compressed file? I didn’t think to try that…
These files are containers for NVRAM settings, scripts, data files and probably other stuff. I assume the bootloader and/or application software knows how to apply these, and under which conditions. Like when you select a specific operator.
You can easily unpack recognizable stuff like certificates using binwalk:
bjorn@miraculix:/tmp$ binwalk -Me SWI9X30C_02.27.01.00_VERIZON_002.038_000.nvu
Scan Time: 2020-09-23 17:08:29
Target File: /tmp/SWI9X30C_02.27.01.00_VERIZON_002.038_000.nvu
MD5 Checksum: a81ef420c2e93809ab19dc58b12b405f
Signatures: 391
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
11911 0x2E87 Certificate in DER format (x509 v3), header length: 4, sequence length: 1235
13544 0x34E8 Certificate in DER format (x509 v3), header length: 4, sequence length: 1152Very interesting! I’ve never used binwalk – you’ve given me a new superpower.
hexdump -C (or just ‘hd’) shows some other interesting stuff in there, in addition to the certificates.
Thanks for responding.