Daniel Wood danielewood

## sierra_mc7355_flashing.md

      
              1 file
            
          
              4 forks
            
          
              4 comments
            
          
              9 stars
            
          
                mleinart
                / sierra_mc7355_flashing.md
            
            
              Last active
              May 15, 2024 19:26
            
              
                Flashing Carrier configuration and updated firmware to a Sierra MC7355
              
          
    Overview

The Sierra MC7355 can run configurations for several North American carriers. These cards are easy to find on eBay
and notable for their support for the Sprint LTE network. Unless you're luck out, you may find you need to flash a new
carrier configuration onto the card you purchased before using it.
Notes

These procedures are specific to the setup I had to perform this on. Most notably, the only system I had with a mini-PCI-e
slot was the target pfSense system, a PCengines APU1d with no VGA port (serial console only). If you're able to obtain a

  
## MC7710 GPS and Mikrotik
Sierra Wireless MC7710 Ports
It depends on enumeration scheme. For DIP mode with (default) USB composition #3 selected, /dev/ttyUSBn ports are expected to be mapped as follows:
n=0 - HIP (CnS);
n=1 - QCDM (diag);
n=2 - NMEA;
n=3 - AT command;
n=4 - modem.

Please note that there isn't necessarily a 1-1 relationship between the MCxxxx serial interface numbers and the Linux /dev/ttyUSBn devices. The latter number space is shared between all USB serial devices in the system, and there is no guarantee that the AT port always will be /dev/ttyUSB2 (or whatever).

## Get-RemoteSSLCertificate.ps1
[CmdletBinding()]
param (
    [Parameter(Mandatory=$true)]
    [string]
    $ComputerName,

    [int]
    $Port = 443
)
	Sierra Wireless MC7710 Ports
	It depends on enumeration scheme. For DIP mode with (default) USB composition #3 selected, /dev/ttyUSBn ports are expected to be mapped as follows:
	n=0 - HIP (CnS);
	n=1 - QCDM (diag);
	n=2 - NMEA;
	n=3 - AT command;
	n=4 - modem.

	Please note that there isn't necessarily a 1-1 relationship between the MCxxxx serial interface numbers and the Linux /dev/ttyUSBn devices. The latter number space is shared between all USB serial devices in the system, and there is no guarantee that the AT port always will be /dev/ttyUSB2 (or whatever).
	[CmdletBinding()]
	param (
	[Parameter(Mandatory=$true)]
	[string]
	$ComputerName,

	[int]
	$Port = 443
	)