I’m trying to configure RPi4 balena device to work with a cellular modem.
For this purpose, I started by generating a new image for the device using the
balena os download
balena preload
balena register (to get a new UUID for the device)
cli commands, and then the following command to configure the modem:
Configuring operating system image
Copied system-connection file: cellular
And I indeed see the cellular file had been copied to the /resin-boot/system-connections/ volume of the SD card.
However, after inserting the SD card into the device, connecting the modem to it, and booting it,
There is no internet connectivity.
Examining the device by connecting it to ethernet, additionally reveals that:
There is only eth0 interface, as well as balena0, br-8c51e5045d3d, lo, resin-dns, resin-vpn, supervisor0, wlan0 interfaces, no modem related interface.
no /dev/ttyACM* or /dev/ttyUSB* exists
lsusb doesn’t show the modem neither
dmesg doesn’t show anything related to the modem
the cellular file is not at /resin-boot/system-connections/
A few more points to note:
I’m using the latest balena-cli - 12.10.1
The same modem with the same SIM card works automatically without any issues on another Pi device with regular Raspbian OS.
Would appreciate your help configuring the device to work with the modem.
We’ve tested it with a number of very common modem models:
Telit LE910-EU v2
Telit LE910C1-EU
Simcom SIM7100E
Quectel EC25-E
Provision PR-LTE01W
I see in the list of supported modems you shared, the Quectel EC20 and Simcom SIM7600E models, which use the same ACM-CDC driver, as most of the other modems we tested.
Moreover, the Quectel EC25-E is very close to Quectel EC20, and similarly SIM7100E to SIM7600E. which balenaOS officially supports.
Therefore I assume that this is not a driver issue, but rather some kind of a miss-configuration.
If possible, enabling support access for a week would likely cover the duration of the investigation (it also relies on when the team will get a chance to take a look). Is this ok?
Let’s repeat on your side exactly what I did. I created a new empty application. Then downloaded an OS image directly from the dashboard - for test purposes I am using a dev version from there since it is more easily accessible from the local network with our CLI. Then check whether the usb controller reports all four ports with usb-devices - no need to plug-in the modem. If the four USB entries are not showing up as they should that would most probably mean that the USB controller is damaged.