Alright, so..
Repeated this process using compatible hardware "Raspberry Pi 2 - Model B", the latest version of OpenWRT (15.05.1), and followed the walkthrough posted here (
https://forum.sierrawireless.com/viewtopic.php?f=117&t=10117#p39975) exactly as posted, with no success.
1.) Flashed an SD card with Chaos Calmer 15.05.1, and inserted in to Pi2.
2.) Hooked up MC7455 via Windows PC, used that Russian Huawei AT application, and sent successful AT commands to switch the MC7455 to MBIM mode. (I only changed the APN to reflect T-Mobile 4G service in the area.)
Code:
AT!entercnd="A710"
AT!USBCOMP=1,1,1009
AT+cgdcont=1,"IP","fast.t-mobile.com"
2.) Initially logged in to luci web interface of Pi2, and set the "lan" interface as a DHCP client for the time being (for opkg updates through existing network connection using windows "Internet Connection Sharing" with th MC7455 through Win10 laptop to WAN on my primary router.)
3.) opkg update
4.) All of these package installs went smooth as butter, and no dependency errors:
Code:
opkg install umbim kmod-usb-net-cdc-mbim kmod-usb-net-sierrawireless kmod-usb-serial-wwan kmod-usb-serial-sierrawireless kmod-usb-serial-qualcomm kmod-usb-net-qmi-wwan uqmi comgt
5.) I ran in to "not found" errors with "opkg install screen" and "opkg install watchcat", but I don't need to lock bands (T-Mobile only has LTE Band 12 in my area), and I could care less about watchcat until I can actually get this connected once.
6.) Logged in with SSH, added in the modified mbim.sh, and set it chmod 755.
7.) Ran the following CLI commands (only changing the APN for T-Mobile here again):
Code:
uci del network.wan #this resulted in an error, since the "wan" network didn't originally exist (since Pi2 only has the one ethernet port, which is already assigned to "lan" interface by default.)
uci set network.wan=interface
uci set network.wan.proto=mbim
uci set network.wan.device=/dev/cdc-wdm0
uci set network.wan.apn=fast.t-mobile.com
uci set network.wan.username=
uci set network.wan.password=
uci commit network
reboot
8.) Logged back in to luci interface, and turned "lan" interface back to a Static IP, and re-enabled DHCP server. The Pi can function as the gateway AND primary router/DHCP server, until I can get this figured out (later it will become just the modem/gateway with all other functionality disabled.)
I know this isn't a signal or module issue. The MC7455 and PCI-to-USB bridge hasn't moved from the position in which it sat when originally connected to a Windows 10 laptop.The adapter with paddle/whip antennas attached sits in a project box literally 1 foot away from a cellular amplifier in the basement boasting a strong signal (the SNR is a little off, but I can tune the antenna/amplifier later to correct it after I have this responding reliably.)
It registers all associated drivers, and creates the cdc-wdm0 device. Just no WWAN communication, and I am unaware of how to check the module's connection, signal strength, and network registration using CLI with these specific packages. And luci just reports the "unknown protocol", as others have indicated is expected.
