Skip to main content
Jump to: navigation, search

Mihini/Run Mihini on an Open Hardware platform

< Mihini
Revision as of 12:22, 17 January 2013 by (Talk | contribs) (Manually)

This page describes a scenario for illustrating the use of Mihini on an Open Hardware Linux-based platform such as BeagleBoard or RaspberryPi.

The goal would be for someone to be able to be only one hour away from taking a bare development board and have it configured to collect data out of the GPIO sensors and send this data on a remote server. The application aims to be updatable over-the-air.

Step 1 - Build Mihini

So far, all the work is being done directly on your remote system. For the following sample, pi user is being used on a RaspberryPi. Connect to you device using ssh and follow the steps.

Compilation prerequisites

First of all, you will need some compilation tools:

$ sudo apt-get install git build-essential cmake

Sources to compile

Get the sources

$ cd /tmp/
$ git clone ssh://host/mihini.git

Run the compilation

Lets move into the repository you just cloned. Make sure you have all prerequisites mentioned above installed. Now, simply run the following in the repository you just cloned, here called mihini/.

# Compile Mihini
$ cd mihini/bin
$ ./
# Compile Lua
$ cd build.default/
$ make lua

Configure Mihini

Then there will be some configuration on bin/build.default/runtime/lua/agent/defaultconfig.lua.

  • Enable the application container
    • appcon.activate = true
  • Enable the update manager
    • update.activate = true

OPTIONAL (but useful :))

  • Enable Lua shell on all network interfaces by adding
    • shell.address = "*"
  • Disable colors while logging ( you will thank me later )
    • log.enablecolors = false

It should be easier

What is explained above is just a beginning. We are about to provide material which will speed up previous steps, such as:

  • How to cross compile Mihini from your Desktop machine
  • A defaultconfig.lua with the right default settings
  • A Linux package, to avoid any kind of compilation or configuration ( It is hypothetical )

Step 2 - Configure network connection

Ethernet connection

  • Configure/verifiy that there is Ethernet connection as a fall-back

3G connection

Step 3 - Start Mihini on your device

One of the features of Mihini is to manage the life cycle of your application. In order to do so, applications are run from another program: the Appmon. We need to start it.


On your device, here a RaspberryPi with user pi.

$ cd mihini/bin/
$ sudo ./appmon_daemon -a /home/pi/mihini/ -w .. -u pi -g pi -n 5 2>&1 | logger -t Mihini&

Notice: we launched appmon_daemon with user pi in order to benefit from valid user rights.

As a service

Soon :)

Step 4 - Setup Koneki environment

  • Download Lua Development Tools
  • Install "Mihini target management"
  • Define your device and configure its "SSH Lua" paths like this
    • If you want the text version
LUA_PATH: /home/pi/mihini/lib/?.lua;/home/pi/mihini/lib/?/init.lua;/home/pi/mihini/lua/?.lua;/home/pi/mihini/lua/?/init.lua;./?.lua
LUA_CPATH: /home/pi/mihini/lib/?.so;/home/pi/mihini/lua/?.so
LD_LIBRARY_PATH: $LD_LIBRARY_PATH:/home/pi/mihini/lib
  • Configure the "Mihini execution environment" (coming soon, will provide nice autocompletion...)

Step 5 - Create your first application

You could blink a LED, use a touch sensor, measure the temperature and available RAM of the board... I decided to keep it simple in this tutorial, my application will simply log :). The file is main.lua.

local io    = require 'io'
local log   = require 'log'
local sched = require 'sched'
local function main()
    log('GENERAL', 'INFO', 'My first Mihini app is alive :)')

Step 6 - Test the application

  • Configure the remote target in the Koneki environment
    • You will need to know the IP address of the target, but you likely know it already :-)
  • Create a launch/debug configuration and test your script

Do not worry, it is all explain on Koneki's Wiki.

Step 7 - Install your application


All you a have to do in order to enable Mihini to handle you application is:

  1. Create a launcher
  2. Provide sources

Create a launcher

Mihini Application container runs executables. To run a Lua application, we need to set some variables beforehand and then lauch your application. In order to do so lets create the proper launcher. In the Mihini world, it is an executable file called run. Here is its content:

# Setting up paths
export LUA_PATH="/home/pi/mihini/lib/?.lua;/home/pi/mihini/lib/?/init.lua;/home/pi/mihini/lua/?.lua;/home/pi/mihini/lua/?/init.lua;./?.lua"
export LUA_CPATH="/home/pi/mihini/lib/?.so;/home/pi/mihini/lua/?.so"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/pi/mihini/lib"
# Running app
/home/pi/mihini/bin/lua main.lua

Now the my application folder looks like

$ find raspapp/

Install application

First of all, I presume you already have an Appmon Daemon running. We are about to install an app which will be named 'sample', available at '/tmp/raspapp', this application will benefit from autostart ( the last true parameter ).

$ telnet localhost 2000
Connected to localhost.
Escape character is '^]'.
Lua interactive shell
> appcon = require 'agent.appcon'
> = appcon.install('sample', '/tmp/raspapp', true )
= ok

We can check that the application is properly installed

> for app, t in pairs(appcon.list()) do
+     print( app )
+     for field, data in pairs(t) do
+         print('\t', field, data)
+     end
+ end
                autostart       true
                runnable        true

Over the air

It will soon be possible to install application to your remote system Mihini just from its IP, and even more:

  • Use the Koneki tools to create an application package
  • Deploy the package on a publically available web server
  • Connect to the Mihini console and for a connection to the testing server


  • You may want to have udev rules so as your USB devices (typically the 3G stick) does not end up having an always changing /dev/ttyUSB<something> file descriptor...
    • For a Sierra 3G stick, create a 99-aircard.rules in /etc/udev/rules.d, with the following rules (your ID_VENDOR_ID and ID_MODEL_ID may be different):



Back to the top