5.3.0b (2021-01-08)

Note that the source image for this release is labeled 5.3.0d. This is because 5.3.0b had recipe issues that required special access to Multitech servers during the build. The resulting build output of 5.3.0b and 5.3.0d are identical in function.

node.js support was dropped. This is because Node.js has dropped support for the ARMV5 architecture.

Ruby language support was dropped. This is because Yocto/Open-Embedded dropped support of Ruby.

mLinux 5.3 uses Yocto 2.6/Thud. There were extensive library changes. Because of this, updating packages is not a viable way to upgrade the device. You must do a firmware image update.

Major fixes:

• On rare occassions the modem was disabled with COPS=2. The COPS state is now verified before ppp starts
• The administrator now has /usr/sbin and /sbin in the path. This was ommitted in 5.2.7, but was in the path in older versions of mLinux.

5.2.7 (2020-06-24)

Errata (2021-01-25)

The repository git.multitech.net module mlinux.git at the 5.2.7 tagged version does not retrieve the version of meta-openembedded that was used to build the images and source tarball. It is recommended that the tagged version 5.2.7a be used instead, so the correct version of Yocto Morty is used. Readme for 5.2.7a

Changes since 5.1.8

Commissioning

Commissioning mode has been added to mLinux. Devices must now undergo a first time
setup to create a username and password. This can be executed via a webUI by browsing
to 192.168.2.1 while networked locally to the device via Ethernet. Additionally,
commissioning may be completed via a curl interface described here.

MTCAP

• lighttpd 1.4.48

MTCDT

• lighttpd 1.4.48

Known Issues

• PATH for Commissioned users does not initially include /sbin or /usr/sbin

5.1.8 (2019-11-08)

Changes since 5.0.0

Cellular

Registration with carrier is now dropped before an APN change, which is required
by some newer modems (LNA4, L4E1).

Support for LNA4, L4E1, LEU7.

LAP3 APN changes now work correctly (carrier registration is dropped).

mtadm added to the dialout group to implement carrier disconnect on modem APN change.

MTCAP

• sudo 1.8.27

MTCDT

• sudo 1.8.27
• lldpd
• flush debug port buffer on boot before read to prevent boot hangs
• Various support programs for Redpine WiFi/Bluetooth in /opt/rs9113 directory which were mistakenly removed from mLinux 5.0.0

Known Issues

• Log rotate will cause the packet forwarder to quit when using the LoRa Network Server, install lora-logging-1.0-r2

5.0.0 (2019-07-02)

Changes since 4.1.9

MTCAP

• Linux 4.9.87
• LoRa Packet Forwarder 4.0.1
• AT91Bootstrap 3.8.12-m2 with support for ONFI flash, improved GNSS reset handling
• U-Boot 2016.09.01 with USB removed for improved GNSS reset handling
• Upgraded packages

MTCDT

• Linux 4.9.87, which allows BLE GATT Server, better GNSS reset handling
• LoRa Packet Forwarder 4.0.1-r17
• LoRa Geolocation 5.1.0-r6
• MTAC 4.0.1 which reads the EEPROM when the driver loads
• rs9113-autostart package so RS9113 (WiFi/BT) is disabled without this package.
• mtd-utils 2.0.2 with Linux 4.9 support
• AT91Bootstrap 3.8.12-m2 with support for ONFI flash, improved GNSS reset handling
• U-Boot 2016.09.01 with USB removed for improved GNSS reset handling
• U-Blox GNSS is now held in reset until the device comes up, which prevents lock-ups in the GNSS
• Upgraded packages

Known Issues

• Hardware watchdog cannot be turned off, and the device will reset if an attempt is made to halt. This is considered a feature.
• The example files from Redpine used to configure WiFi were left off of the device (such as /opt/rs9113/hostapd_open.conf). They are contained in the package rs9113-misc_1.6.1-r10.4.9.87r9.0_all.ipk. To obtain this file it will be necessary to open a support ticket .

Support tickets to obtain Redpine Drivers
mLinux source code

4.1.9 (2019-05-13)

Changes since 4.1.7

MTCDT Only

It was found that gpsctl does not reliably set the baud rate and message mode of the GPS. In some circumstances, messages with latitude and longitude were shut off which caused there to be no location in some software. For this reason, all gpsd packages except libgps24 (to provide compatibility) were downgraded to 3.16. This issue has existed since 4.0.0.

Changed software components

4.1.7 (2019-04-23)

Changes since 4.1.6

MTCDT Only

Bootstrap, U-Boot, and the kernel were revised to hold the U-Blox GNSS reset line high during most of the boot. This is to correct an unresponsive GPS, which happens rarely on some units. The same treatment was also given to the USB Hub reset.

Upgraded software components

4.1.6 (2019-03-26)

Changes since 4.0.1

MTCAP

• Sprint Cellular Modem LSP3 support
• Australia Cellular Modem LAP3 support
• Radio reset package, which is configurable via /etc/default/radio-reset
• ifplugd package, which starts DHCP when a network becomes available
• IPV6 is enabled by default in ppp, required by some carrier accounts
• LoRa Network Server 2.2.18 is included on the image, but is inoperable, except on mPower^™ hardware.
• LoRa Packet Forwarder 4.0.1
• Upgraded packages

MTCDT

• MTAC-XDOT support
• MTAC-PULSE support
• The mts-io driver (mts_io.ko) was split into separate modules to make mtac card development easier.
• New gpsd 3.18.1 with ubxtool
• New LoRa packet forwarder compatible with gpsd and ntp usage of the GPS,except on MTCDTIP with LoRa geolocation
• Removed gpsd-udev USB GPS package which caused issues on some Conduits^® with certain cellular modems
• LoRa Network Server 2.2.18
• LoRa Packet Forwarder 4.0.1
• Upgraded packages

Known Issues

• gpsd cannot be used with MTCDTIP with LoRa geolocation

mtac driver change

The mtac accessory cards for MTCDT now each have separate loadable modules. There is a new driver module, mtac.ko, which is the mtac card supervisor. It maintains a list of which cards are inserted into the Conduit. The init script, /etc/init.d/mts-io, now attempts to load each mtac card driver module. If the correct mtac card is not found, the module will not load. The mtac card is identified through its EEPROM on the i2c bus on the card itself. The source code for the various mtac drivers can be found in the mts-io section at the bottom of this page:

mLinux source code

4.0.1 (2018-08-01)

Changes since 3.3.24

• mLinux^™ 4 is based on Yocto 2.2. mLinux 3 was based on Yocto 1.6
• OpenJDK was removed from the image. Still available from feeds or build your own image
• The new kernel fixes write hangs when doing high volume writes to jffs2 file system or SD card
• Enhanced security. Root user logins are removed. New admin is mtadm, and is not root. Root privilege is accessed via sudo
• Default login on MT provided images is mtadm/root
• Support for LoRa 2.1
• Support for address ranges in firewall settings
• Bluez5 replaces Bluez4
• ifplugd to bring up connections and restart DHCP
• kernel support for Cat M Cellular radios
• U-Boot password protection
• php-fpm replaces fastcgi on the images
• eudev replaces udev
• Upgraded packages

Known Issues

• sms does not work with LNA3 Cellular Modem on Verizon with MTCAP
• Radio reset does not work with LNA3 and MTCAP with firmware 20.00.522 (AT&T) or 20.00.12 (Verizon). The solution is to upgradethe firmware to 20.00.524/20.00.14.
• Upgrading Telit firmware
• In mLinux 3, libcurl4 was mistakenly called libcurl5. This was a bug in Yocto 1.6. This bug has since been corrected, and libcurl4 is now called libcurl4 as it should be. However, old programs linked by the toolchain for mLInux 3 will not be able to find libcurl4. This can probably be fixed with a symlink, but this solution needs testing.
• libcurl5 issue

3.3.24 (2018-04-09)

Changes since 3.3.22

• Lora Network Server 2.0.19
• Add kernel revision to revision of vizzini and mts-io pacakges
• Correct revision of kernel-module-bluetooth
• Fix gpsd scripts used by ntpd to prevent possible boot hangs

3.3.22 (2018-03-05)

Changes since 3.3.15

• Bluetooth Blueborne security fixes

• WiFi (hostapd and wpa_supplicant)

• RS9113 driver 1.5.6 update for new revision RS9113 part. New devices are not compatible with older versions of this driver.Old devices are compatible with the new driver.

Package upgrade:

• Failure to complete boot in certain newer devices:

• Do not do Radio Reset of Cellular modem when the modem is not on the device.

• Build the /run/config directory during boot for Lora software to make it easier to discoverdevices. This does not include cellular radio information.

• Preserve hostapd and dnsmasq (if installed) files across installations.

• Allow radio reset of cellular modem despite backoff timer restrictions.

• Support for LDC3 radio (Japan)

• Support for network bonding

• Netfilter additional support:

• mts-fpga-loader for Lora firmware updates.

• Support for IP67:

• LNS 2.0.16

• Don’t allow mPower version to be overwritten by mLinux version.

• New channel plans

• NodeJS 0.10.48-r1.7

• Allow for an install script in an upgrade package.

Additional LoRa Notes

LoRa Network Server v2.0.16

3.3.15 (2017-10-30)

Changes since 3.3.13

• Lora Network Server 1.0.43-r1.0.
• Lora Packet Forwarder 3.1.0-r10.0.

• Bluez4 Blueborne fix 4.101-r10.m1.0
• Bluetooth kernel module Blueborne fix, kernel-module-bluetooth 3.12.27-r14.2, srcversion: A663C5831F3BBA8C48735E5
• gpsd script could cause hang in ntpd start-up, gpsd-conf 3.16-m4.0
• /etc/init.d/umountfs allows for package updates rather than just image replacement, mlinux-scripts 1.1-r3.0
• Lora eprom burning tool, mts-fpga-loader, for mtcdt, mts-id-eeprom 0.3.3-r1.0.0

3.3.13 (2017-09-27, revised 2017-10-23)

Features since 3.3.9

• Remove radio reset from MTCAP units with no cellular radio.
• Support for MTCDTID harware version
• Support for LNA3 radio option
• Support for Netfilter TEE available in kernel module xt_TEE.ko.
• ppp waits for SIM registration before starting. Seehttp://www.multitech.net/developer/software/mlinux/using-mlinux/start-cell-connection-on-boot/
• International dialing support in sms-utils
• When umountfs attempts an upgrade, first clean up /var/volatile of unneeded files
• New Lora calibration data in /opt/lora/global_conf.json.MTCAP_LORA_1_5.US915.

Known Issues

When building an upgrade file for MTCDTIP, you must update the model file after the build.

3.3.9 (2017-08-10)

Features since 3.3.7

• gethostbyname memory leak fix — libc6_2.19-r0.m1.0
• MTCAP had an unusual password in 3.3.7. Set to root in 3.3.9
• New Lora software related to support for Japan
  • Lora-gateway from 4.0.1-r9.0 to 4.1.3-r10.0
  • Lora-network-server from 1.0.26-r1.0 to 1.0.36-r1.0
  • Lora-packet-forwarder from 3.0.0-r9.0 to 3.1.0-r9.0

3.3.7 (2017-06-26)

Features

• Support for LJP1 (LE866) Radio (Japan)
• Support for LJP1 (LE910-JN1) (Japan)
• Support for LNA3 (LE910-NA1)

Fixes

• OPEN SSL Version 3 Support added for Python. New SSL package is openssl – 1.0.2k-bpo8.1m2.0
• GPSD no longer will start if the GPS capability flag is not set by the MTS-IO driver.
• When starting GPSD, a maximum of 20 seconds is allowed for changing the baud rate of the GPS. This will allow the boot to proceed if a baud rate change is not possible.
• Eliminated setserial command invocation from udev which was producing error messages and not needed.
• Bootstrap patch borrowed from MTR to lessen the likelihood of the Real Time Clock preventing boot when operating with a battery.
• Build change: source control for 3.x.y above 3.3.6 was moved to git 3 branch from master. This was to prepare for mLinux release 4.0

See also

Using mLinux

3.3.6 (2017-04-21)

Changes

• lora-network-server is at level 1.0.26.
• Upgraded to openssl 1.0.2k-1~bpo8+1 from Debian backports to be compatible with mLinux 3.1 and 3.2 and provides security enhancements.
• GPSD support for leap second on Conduits with GPS receiver feature.
• NTPD starts by default if the GPS has a position fix. NTPD adjusts the system clock and sets the hardware clock.
• To disable GPSD, set parameter /etc/default/gpsd: ENABLED="no". Reboot.
• To disable NTPD, set parameter /etc/default/ntpd: ENABLED="no". Reboot.
• To disable GPS requirement for NTP, set /etc/default/ntpd: GPSD_REQUIRED=0.
• To check GPSD when it is running, type gpsmon.
• Ethernet Bonding feature added.

Known Issues

• Lora only supports 915MHz, 868MHz, and AU915MHz channel plans.

See also

Using mLinux

3.2.0 (2016-05-18)

Changes

• Updated openembedded-core with latest security fixes from Yocto 1.6
• Fixed monit building issue with 3.1.0
• lora-network-server 1.0.8
• Added support for LTE radio models: LVW2, LEU1, LAT1
• mts-io 1.1.4 — fix possible kernel crash in driver
• node.js 0.10.44
• Added strongswan to images
• Fix sms bugs where some characters wouldn’t be sent or received correctly

Known Issues

• Will not build on Ubuntu 14.04/16.04 with kernel 4+

3.1.0 (2015-05-27)

• First official release!