BalenaFin and LTE with EC25 mPCIe

Hello,

Can you please paste the contents of the CELLULAR file here?

@zvin Please see below.
[connection]
id=cellular
type=gsm
autoconnect=true

[gsm]
apn=wireless.twilio.com

[serial]
baud=115200

[ipv4]
method=auto

[ipv6]
addr-gen-mode=stable-privacy
method=ignore

Is this the CELLULAR file in the system-connections folder of the boot partition?
Do you see the same content in /etc/NetworkManager/system-connections/CELLULAR on the host OS after rebooting?
I am asking, because the error you pasted here:

keyfile: error loading connection from file /etc/NetworkManager/system-connections/CELLULAR: invalid connection: connection.type: connection type 'gsm ’ is not valid.

has an extra space after gsm and the second quote is different from the first one.

@zvin I’ve confirmed that the CELLULAR file is in both /etc/NetworkManager/system-connections and /mnt/boot/system-connections with the exact same content. I’ve rebooted and restarted numerous times. I looked at the logs for both ModemManager and NetworkManager and I didn’t see the CELLULAR file being called at all, but cellular data still isn’t working.

What is the output of nmcli in the host OS ?

@jmeyers2 if you have corrected the gsm keyfile error and its still not working, can you paste the logs from journalctl -u ModemManager --no-pager, that should indicate at which point this is failing. Also if you can run mmcli -m 0 and see what signal quality the modem is getting, that would be interesting to know.

Hi @zvin Please see below
“0424 ec00”
ethernet (smsc95xx), B8:27:EB:20:63:45, hw, mtu 1500
ip4 default, ip6 default
inet4 192.168.1.117/24
route4 0.0.0.0/0
route4 192.168.1.0/24
inet6 2601:404:cf00:de8:6f02:c096:ef82:4fc6/64
inet6 fe80::affa:1261:3ed3:da8d/64
route6 2601:404:cf00:de8::/64
route6 ::/0
route6 ff00::/8
route6 fe80::/64

Not sure if that helps you as it’s connected to ethernet.

@shaunmulligan

Results from running mmcli -m 0

General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: 13166f14f6a99a2231cfaa24004c78a963bcf084

Hardware | manufacturer: QUALCOMM INCORPORATED
| model: QUECTEL Mobile Broadband Module
| revision: EC25AFFAR07A03M4G
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 866834040069416

System | device: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2
| drivers: option1, qmi_wwan
| plugin: Quectel
| primary port: cdc-wdm0
| ports: ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0 (qmi), wwan0 (net),
| ttyUSB3 (at)

Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-pin2 (10), sim-puk (10), sim-puk2 (10)
| state: enabled
| power state: on
| signal quality: 0% (cached)

Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 3g
| allowed: 3g, 4g; preferred: 4g
| current: allowed: 3g, 4g; preferred: 4g

Bands | supported: utran-4, utran-5, utran-2, eutran-2, eutran-4, eutran-5,
| eutran-12, eutran-13, eutran-14, eutran-66, eutran-71
| current: utran-4, utran-5, utran-2, eutran-2, eutran-4, eutran-5,
| eutran-12, eutran-13, eutran-14, eutran-66, eutran-71

IP | supported: ipv4, ipv6, ipv4v6

3GPP | imei: 866834040069416
| registration: idle

3GPP EPS | ue mode of operation: csps-1

SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0

Log files: (I didn’t see a way to attach a file, sorry for the wall of text)
Jun 04 23:32:35 localhost systemd[1]: Starting Modem Manager…
Jun 04 23:32:35 189d441 ModemManager[698]: ModemManager (version 1.10.0) starting in system bus…
Jun 04 23:32:36 189d441 systemd[1]: Started Modem Manager.
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] Opening device with flags ‘version-info, proxy’…
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] loaded driver of cdc-wdm port: qmi_wwan
Jun 04 23:32:38 189d441 ModemManager[698]: cannot connect to proxy: Could not connect: Connection refused
Jun 04 23:32:38 189d441 ModemManager[698]: spawning new qmi-proxy (try 1)…
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] Checking version info (10 retries)…
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] QMI Device supports 30 services:
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] ctl (1.5)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] wds (1.67)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] dms (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] nas (1.25)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] qos (1.12)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] wms (1.10)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] auth (1.3)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] at (1.2)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] voice (2.1)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] cat2 (2.24)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] uim (1.46)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] pbm (1.4)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] test (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] loc (2.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] sar (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] ims (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] csd (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] ts (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] tmd (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] wda (1.16)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] csvt (1.1)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] imsp (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] imsa (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] coex (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] pdc (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] rfrpe (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] dsd (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] unknown [0x2d] (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] unknown [0x30] (1.0)
Jun 04 23:32:38 189d441 ModemManager[698]: [/dev/cdc-wdm0] unknown [0x36] (1.0)
Jun 04 23:32:39 189d441 ModemManager[698]: Couldn’t check support for device ‘/sys/devices/platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1’: not supported by any plugin
Jun 04 23:32:39 189d441 ModemManager[698]: Couldn’t check support for device ‘/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1’: not supported by any plugin
Jun 04 23:32:47 189d441 ModemManager[698]: (tty/ttyUSB0) failed to parse QCDM version info command result: -7
Jun 04 23:32:53 189d441 ModemManager[698]: [device /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2] creating modem with plugin ‘Quectel’ and ‘6’ ports
Jun 04 23:32:53 189d441 ModemManager[698]: Could not grab port (tty/ttyUSB1): ‘Cannot add port ‘tty/ttyUSB1’, unhandled serial type’
Jun 04 23:32:53 189d441 ModemManager[698]: Modem for device ‘/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2’ successfully created
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Opening device with flags ‘version-info, proxy’…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] loaded driver of cdc-wdm port: qmi_wwan
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Checking version info (10 retries)…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] QMI Device supports 30 services:
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] ctl (1.5)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] wds (1.67)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] dms (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] nas (1.25)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] qos (1.12)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] wms (1.10)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] auth (1.3)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] at (1.2)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] voice (2.1)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] cat2 (2.24)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] uim (1.46)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] pbm (1.4)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] test (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] loc (2.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] sar (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] ims (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] csd (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] ts (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] tmd (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] wda (1.16)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] csvt (1.1)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] imsp (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] imsa (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] coex (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] pdc (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] rfrpe (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] dsd (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] unknown [0x2d] (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] unknown [0x30] (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] unknown [0x36] (1.0)
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Reading expected data format from: /sys/class/net/wwan0/qmi/raw_ip
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Allocating new client ID…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Registered ‘wda’ (version 1.16) client with ID ‘1’
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Writing expected data format to: /sys/class/net/wwan0/qmi/raw_ip
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Reading expected data format from: /sys/class/net/wwan0/qmi/raw_ip
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Allocating new client ID…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Releasing ‘wda’ client with flags ‘release-cid’…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Unregistered ‘wda’ client with ID ‘1’
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Registered ‘dms’ (version 1.0) client with ID ‘1’
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Allocating new client ID…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Registered ‘nas’ (version 1.25) client with ID ‘4’
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Allocating new client ID…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Registered ‘wms’ (version 1.10) client with ID ‘1’
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Allocating new client ID…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Registered ‘uim’ (version 1.46) client with ID ‘2’
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Allocating new client ID…
Jun 04 23:32:53 189d441 ModemManager[698]: [/dev/cdc-wdm0] Registered ‘loc’ (version 2.0) client with ID ‘1’
Jun 04 23:32:53 189d441 ModemManager[698]: Unhandled QMI radio interface (9)
Jun 04 23:32:53 189d441 ModemManager[698]: Unhandled QMI radio interface (9)
Jun 04 23:32:54 189d441 ModemManager[698]: Unhandled QMI radio interface (9)
Jun 04 23:32:54 189d441 ModemManager[698]: couldn’t load list of Own Numbers: ‘Couldn’t get MSISDN: QMI protocol error (16): ‘NotProvisioned’’
Jun 04 23:32:54 189d441 ModemManager[698]: Modem: state changed (unknown -> disabled)
Jun 04 23:32:54 189d441 ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
Jun 04 23:32:54 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:32:54 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:32:55 189d441 ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> idle)
Jun 04 23:32:55 189d441 ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> enabled)
Jun 04 23:32:55 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:33:11 189d441 ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> unknown)
Jun 04 23:33:12 189d441 ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> idle)
Jun 04 23:33:58 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:33:58 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:33:58 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:35:01 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:35:01 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:35:01 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:36:02 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:36:02 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:36:02 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:37:05 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:37:05 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:37:05 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:38:08 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:38:08 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:38:08 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:39:11 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:39:11 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:39:11 189d441 ModemManager[698]: Simple connect state (5/8): Register
Jun 04 23:40:14 189d441 ModemManager[698]: Simple connect started…
Jun 04 23:40:14 189d441 ModemManager[698]: Simple connect state (4/8): Wait to get fully enabled
Jun 04 23:40:14 189d441 ModemManager[698]: Simple connect state (5/8): Register

I just flashed an image with latest balenaOS on a Fin device and attached an EC25 modem. I did not pushed any application to it. I also did not specify any NetworkManager connection profiles.

The modem automatically registers to the network without any action from me:

  --------------------------------
  Status   |                 lock: sim-pin2
           |       unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)
           |                state: registered
           |          power state: on
           |          access tech: lte
           |       signal quality: 42% (recent)
  --------------------------------

Do you have another sim card available to try that out? The one you are using indicates an issue with network registration.

@majorz I swapped over to a hologram sim chip that’s activated. Changed the CELLULAR file on the apn side to reflect the hologram apn, and deleted the CELLULAR file in the the NetworkManager directory. I still don’t have cellular connectivity. I was digging through the logs for Network Manager, and I noticed this line over and over:

Jun 06 00:18:41 189d441 NetworkManager[740]: [1559780321.2769] device (cdc-wdm0): Activation: failed for connection ‘cellular’
Jun 06 00:18:41 189d441 NetworkManager[740]: [1559780321.2789] device (cdc-wdm0): state change: failed -> disconnected (reason ‘none’, sys-iface-state: ‘managed’)
Jun 06 00:18:41 189d441 NetworkManager[740]: [1559780321.2832] policy: auto-activating connection ‘cellular’ (1e88cf76-e32a-3267-8081-9c9525c758d8)
Jun 06 00:18:41 189d441 NetworkManager[740]: [1559780321.2887] device (cdc-wdm0): Activation: starting connection ‘cellular’ (1e88cf76-e32a-3267-8081-9c9525c758d8)
Jun 06 00:18:41 189d441 NetworkManager[740]: [1559780321.2895] device (cdc-wdm0): state change: disconnected -> prepare (reason ‘none’, sys-iface-state: ‘managed’)
Jun 06 00:18:41 189d441 NetworkManager[740]: [1559780321.2924] manager: NetworkManager state is now CONNECTING
Jun 06 00:19:44 189d441 NetworkManager[740]: [1559780384.2790] modem-broadband[cdc-wdm0]: failed to connect modem: Network timeout
Jun 06 00:19:44 189d441 NetworkManager[740]: [1559780384.2792] device (cdc-wdm0): state change: prepare -> failed (reason ‘gsm-registration-timeout’, sys-iface-state: ‘managed’)
Jun 06 00:19:44 189d441 NetworkManager[740]: [1559780384.2821] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 06 00:19:44 189d441 NetworkManager[740]: [1559780384.2859] device (cdc-wdm0): Activation: failed for connection ‘cellular’

I want to make sure my understanding is correct. Is that saying, that it’s trying to connect to the cellular network for the hologram sim but it’s unable too? I’ve verified the sim is active as I can see it on the Hologram website.

Hi,

Some clarification about ModemManager and NetworkManager. When you start a freshly flashed OS (without any connection profiles defined), ModemManager will still start to register to an available network. That is - when you run mmcli -m 0 you should still observe that the modem is registered to a network. When you specify a connection profile for the modem for NetworkManager, it will be used by NetworkManager to instruct ModemManager for phases after network registration. So to narrow this down, we do not have to specify one.

In the logs we looked at earlier on (and I maybe the last ones indicate that as well), it is indicated that the modem does not reach successful registration phase. That is - NetworkManager interaction is not yet needed.

Let’s do the following please:

  1. Flash a fresh OS image from an empty application without any code pushed and application container running (this is important so that we ensure that things like udev running in a container do not interfere with the modem).

  2. Paste the output of mmcli -m 0 from different sim cards. You can use the Hologram one, one from a mobile phone, etc. You just need to plug it as we do not need to specify a NetworkManager connection profile.

Once we know the registration output we have narrowed down the problem.

Please let me know if you have any questions.

Thanks,
Zahari

Ah, and one last thing. If you do not have antennas attached to the modem, then that could be a possible explanation for the failure of registration.

I created a new application and clicked on add device to grab the .img file. Flashed it to my BalenaFin board and plugged it into an ethernet cable. The device doesn’t appear on the dashboard, nothing does. Are there technical problems?

It sounds to me like what you tried (empty app with an ethernet cable) should have worked. Is there anything in the following troubleshooting pages that helps? E.g. blinking LED patterns:

Edit: I’ve just tested an empty app with a Raspberry Pi 2 with only an Ethernet cable connection, and it showed up in the dashboard. So yes, the process works…

I’m getting a 404 error on those links.

I have double checked the links and they seem to be working OK. Perhaps copy-and-paste from plain text:

https://www.balena.io/fin/1.1/docs/troubleshooting/
https://www.balena.io/docs/faq/troubleshooting/troubleshooting/#raspberry-pi

Other debugging suggestions (when the a device is not shown on the dashboard and you have physical access to it) include:

$ sudo balena scan
Reporting scan results
-
  host:          b1878c6.local
  address:       192.168.1.118
  dockerInfo:
...

I created a new application, and flashed a new OS on it. Plugged in the ethernet cable and let everything load. Then I ran the command mmcli -m 0 and the results are below:

General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: 15efea8d5eceb957cef6f3179cda21902ab620f8

Hardware | manufacturer: QUALCOMM INCORPORATED
| model: QUECTEL Mobile Broadband Module
| revision: EC25AFFAR07A03M4G
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 866834040075835

System | device: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2
| drivers: option1, qmi_wwan
| plugin: Quectel
| primary port: cdc-wdm0
| ports: ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0 (qmi), wwan0 (net),
| ttyUSB3 (at)

Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)
| state: enabled
| power state: on
| signal quality: 0% (cached)

Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 3g
| allowed: 3g, 4g; preferred: 4g
| current: allowed: 3g, 4g; preferred: 4g

Bands | supported: utran-4, utran-5, utran-2, eutran-2, eutran-4, eutran-5,
| eutran-12, eutran-13, eutran-14, eutran-66, eutran-71
| current: utran-4, utran-5, utran-2, eutran-2, eutran-4, eutran-5,
| eutran-12, eutran-13, eutran-14, eutran-66, eutran-71

IP | supported: ipv4, ipv6, ipv4v6

3GPP | imei: 866834040075835

3GPP EPS | ue mode of operation: csps-2

SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0

Should I add a file telling the system to what mobile network to connect as described in this tutorial:
https://www.balena.io/blog/balena-fin-gps-tracker-project/ or not? What’s the next step?

Edit: I attached an antenna to the EC25 and I got the following output with the antenna, trying different sim cards, Hologram and Twilio.

Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)
| state: registered
| power state: on
| access tech: lte
| signal quality: 76% (recent)

The Twilio sim card has a 80% signal quality. However, it is still not connecting to the network without Ethernet. What are the next steps? Is it adding that connection file ?

@pdcastro You are correct, the process works. Had a faulty ethernet cable that had to be swapped out. Thanks for the documentation.

Hey @jmeyers2, I am glad to know that it worked!
Anything let us know!
Cheers