[John Klug]

If using dnsmasq, the location of /etc/resolv.conf is configurable. A suggested location would be /etc/network/resolv.conf.

In your DNS configuration for dnsmasq:

resolv-file=/etc/network/resolv.conf

[John Klug]

Here is the Lora-network-server:

http://www.multitech.net/mlinux/feeds/3.3.13/arm926ejste/lora-network-server_1.0.41-r1.0_arm926ejste.ipk

Or if the device has internet access, you can edit /etc/opkg/mlinux-feed.conf to point at the mLinux level you wish (for instance there is a 3.3.14 package feed) and do opkg install lora-network-server.

[John Klug]

I can only point you at the bluez examples. mLinux 3 is based on Bluez 4.101:

https://www.kernel.org/pub/linux/bluetooth/bluez-4.101.tar.xz

Look in the directory /bluez-4.101/test/ in the archive.

For instance, test-thermometer is a python program for monitoring a thermometer. I have not tried these. D-BUS is the recommended infrastructure to write BLE programs.

[John Klug]

You need to access U-Boot. I assume you can see things happening on the debug port? Repeatedly hit a key on your PC connected through the debug port after you power up the device. You need to be quick.

You should see:
Hit any key to stop autoboot: 0
U-Boot>

You will need the images and a tftp server.

Flashing mLinux Firmware

See:
Using U-boot & TFTP on the flashing firmware page.

[John Klug]

If you are using mLinux, there is no factory default code, unless you wrote it yourself. Factory default reset is a feature of AEP.

If ethernet is configured, and ssh is running, it may be possible to log in with ethernet, even if boot does not complete.

Can you ping the ethernet port? Do you know its address? I believe the Conduit will print the ethernet port address on the debug port during boot, if it is a static IP. If you are using DHCP, you may have to get the address from your DHCP server. If you have created settings in /etc/network/interfaces that cause boot to hang, and you are using mLinux you will need to reflash your unit. Remember that if you have a WiFi/BT version of Conduit, you will need to get the images from the support portal as documented on this page:

Downloads:

Downloads

How to flash your unit (look at the U-Boot information):

Flashing mLinux Firmware

[John Klug]

Are you trying to use git to maintain configuration?

Are you familiar with the opkg command on the Conduit?

You need to look for the git*.ipk package.

Start here:

Downloads

Look on the above page for:

Conduit: mLinux model

Other Downloads:

Pre-built Packages

Here is an example from Pre-Built packages:
http://www.multitech.net/mlinux/feeds/3.3.9/arm926ejste/git_1.9.0-r0.0_arm926ejste.ipk

• This reply was modified 6 years, 8 months ago by John Klug.
• This reply was modified 6 years, 8 months ago by John Klug.

[John Klug]

We mostly use UBUNTU 14.04LTS.

[John Klug]

You must install the toolchain on a compatible Linux system. Conduit is too small in footprint for a development system.

Look for Toolchain on this page:

Downloads

Instructions here:
http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html

You must run the source script to set CC and CXX, which is described in section 2.3 of the adt-manual.

Alternatively, you might try Python or Bash which does not require a development system.

[John Klug]

The latest mLinux firmware for MTCAP is 3.3.9. http://www.multitech.net/developer/downloads/

You will find Node Red under pre-built packages.

http://www.multitech.net/mlinux/feeds/3.3.9/arm926ejste/node-red_0.15.3-r0.0_arm926ejste.ipk

If you need an admin GUI, you will need to install AEP instead. If you have flashed mLinux over AEP, you will need to contact customer support.

[John Klug]

If you received an MTCAP with 3.3.6, the password was mistakenly set wrong. Here is the readme with the password at the end:

http://www.multitech.net/mlinux/images/mtcap/3.3.6/Readme.txt

[John Klug]

Node.js beyond version 0.10 will not work on the Conduit. This is because of architecture dependencies built into newer versions of Node.js, such that it will no longer run on ARM 9.

[John Klug]

If you flash mLinux, you will not have AEP. You need to contact customer support if you need AEP images.

[John Klug]

You will need to re-flash your unit with U-Boot. You will need to connect your system to a PC with both ethernet and USB through the debug port.

Flashing mLinux Firmware

You will need the jffs2 root image, and the uImage.

If you are using mLinux, images can be found here:

http://www.multitech.net/mlinux/images/

• This reply was modified 6 years, 11 months ago by John Klug.

[John Klug]

To download the minicom script from most web browsers, after bringing up the page do <File>, <Save Page as> or possibly <Ctrl>S.

In Minicom, while logged into U-Boot, execute the minicom control character (usually CTRL-A), followed by <G>. Up should pop a menu with items A, B, and C. Then type <C> (name of script selection), and enter the path of the minicom script, then type <enter>. The minicom script should now execute, which will put the flash commands into the U-Boot environment.

• This reply was modified 7 years ago by John Klug.
• This reply was modified 7 years ago by John Klug.

[John Klug]

This output is usually indicative of a bad ethernet connection:

TFTP from server 192.168.2.99; our IP address is 192.168.2.1
Filename ‘oe_uImage.bin’.
Load address: 0x22000000
Loading: T T T T T T T T T T

You might want to try to use the U-Boot ping command, and recheck your tftp server.

[John Klug]

If you wish to re-flash your mLinux firmware using u-boot, take a look here:

Flashing mLinux Firmware

This can put the system back to defaults.

You will need to know what level of mLinux you were using so that you download the appropriate images, or if you wish, you may use the latest firmware (3.3.6). The instructions are for using minicom as a TTY program, and you will need a tftp server.

[John Klug]

There should be a Conduit soon with integrated WiFi. There is no supported WiFi dongle.

[John Klug]

You could try building the image. Instructions are here:

Building Images

Eventually we will be releasing new images.

Levels 3.3 and above allow the builder of the image to set the initial root password.

[John Klug]

All we provide pre-compiled is the toolchain for 64 bit AMD64. We do not have a native compiler. And usually one needs more than just the compiler.

Here is access to the toolchain(SDK):
http://www.multitech.net/mlinux/sdk/

[John Klug]

https://www.yoctoproject.org/downloads

Look at http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2

It has bitbake recipes for 4.9. You could try putting these in the toolchain layer:

meta-openembedded/toolchain-layer/recipes-devtools/gcc

Sorry I can’t be of more help.

Maybe later.

[John Klug]

AEP includes mLinux and provides a web browser based system management interface supported by Multitech.

mLinux provides a Linux distribution based on Open Embedded/Yocto, and does not provide a GUI interface.

[John Klug]

This error means that your build system kernel is not supported by the icedtea build. Apparently you are on Linux kernel 4.2.0-27?

>&2 echo “*** This OS is not supported:” ‘uname -a’; exit 1;
| *** This OS is not supported: Linux ulc-VirtualBox 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

For instance, my Ubuntu 14.04 system is kernel 3.13.0.

[John Klug]

The newest Ubuntu that I know works is 14.04LTS. We also do builds on 12.04LTS.

Thanks for letting us know.
John Klug

[Author]

Posts