Jump to: navigation, search

Difference between revisions of "Mihini/Run Mihini on an Open Hardware platform"

(Step 3 - Setup Koneki environment: Now uses the nightly)
m (Install application)
 
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
This page describes a scenario for illustrating the use of Mihini on an Open Hardware Linux-based platform such as <em>BeagleBoard</em> or <em>RaspberryPi</em>.
 
This page describes a scenario for illustrating the use of Mihini on an Open Hardware Linux-based platform such as <em>BeagleBoard</em> or <em>RaspberryPi</em>.
  
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.
+
The goal is to allow someone to take a bare development board and configured it to collect data from the GPIO sensors. All this within an hour!
  
 
Please bear in mind that <strong>Mihini is still under development</strong>.<br/>
 
Please bear in mind that <strong>Mihini is still under development</strong>.<br/>
  
== Step 1 - Get Mihini  ==
+
== Step 1 - Get and/or build Mihini  ==
  
To get Mihini, you have 3 options :
+
Mihini sources are available from their [http://git.eclipse.org/c/mihini/org.eclipse.mihini.git Git repository], as well as [[Mihini/Install_Mihini | packaged for the most common Linux distributions]].
  
*[[Mihini/Build Mihini|Build Mihini]]  
+
To build Mihini, you have 4 options :
*[[Mihini/Cross Compilation|Cross Compilation]]  
+
*[[Mihini/Mihini_Agent_Linux_build_instructions | Build Mihini for your local system ]]
*[[Mihini/Install_Mihini|Install Mihini]]
+
*[[Mihini/Build Mihini|Build Mihini on a remote system ]]  
 +
*[[Mihini/Cross Compilation|Cross Compilation: build Mihini on your local system for a remote system ]]  
 +
*[[Mihini/Install_Mihini|Install Mihini using existing Linux distribution packages]]
  
== Step 2 - Start Mihini on your device ==
+
== Step 2 - Configure Mihini ==
 +
If you have installed Mihini from a .deb or a .rpm, you can skip this section.
 +
 
 +
You may want to use directly this [https://github.com/nim65s/mihini-repo/blob/CPack/porting/raspberrypi-linaro/agent/defaultconfig.lua defaultconfig.lua] in <code>mihini/lua/agent/</code> ; but you can also read the comments in this file to get your own configuration.
 +
 
 +
The agent.deviceId can be generated from your device with the platform.lua corresponding to your platform:
 +
 
 +
* [https://github.com/nim65s/mihini-repo/blob/CPack/porting/raspberrypi-linaro/agent/platform.lua Raspberry Pi]
 +
* [https://github.com/nim65s/mihini-repo/blob/CPack/porting/beaglebone/agent/platform.lua BeagleBone]
 +
 
 +
== 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 <code>Appmon</code>. We need to start it.
 
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 <code>Appmon</code>. We need to start it.
Line 25: Line 37:
 
=== Manually ===
 
=== Manually ===
  
On your device, if you have built mihini, here a <em>RaspberryPi</em> with user <code>pi</code>.
+
On your device, if you have built mihini on a <em>RaspberryPi</em> with user <code>pi</code>:
 +
 
 +
Firstly, you should link the librairies:
  
 
<source lang="bash">
 
<source lang="bash">
$ cd ~/mihini
+
cd /etc/ld.so.conf.d/
$ sudo ./bin/appmon_daemon -a /home/pi/mihini/start.sh -w /home/pi/mihini -u pi -g pi -n 5 2>&1 | logger -t Mihini &
+
sudo /bin/sh -c 'echo "/home/pi/mihini/lib/" > 01-mihini.conf'
 +
sudo ldconfig
 
</source>
 
</source>
  
'''Notice''':  we launched <code>appmon_daemon</code> and <code>mihini</code> with <code>root</code> user rights, and applications managed by <code>appmon_daemon</code> will be launched using user <code>pi</code> that should give sufficient user rights for most of needs.
+
Then, you can start it:
  
'''Possible starting issues'''
 
The execution of ps aux must show something like the following line to successfully verify that the daemon is running:
 
 
<source lang="bash">
 
<source lang="bash">
root      2360 0.0  0.0  2028  300 pts/0    S+  09:55  0:00 ./bin/appmon_daemon -a /home/pi/mihini/start.sh -w /home/pi/mihini -u pi -g pi -n 5
+
$ cd ~/mihini
 +
$ sudo ./bin/appmon_daemon -a /home/pi/mihini/start.sh -w /home/pi/mihini -u pi -g pi -n 5 2>&1 | logger -t Mihini &
 
</source>
 
</source>
If this is not the case this may be due to a missing library. Check with ldd bin/appmon_daemon and ldd bin/agent that all required libraries are resolved. If not, try this code
 
  
<source lang="bash">
+
'''Notice''':  we launched <code>appmon_daemon</code> and <code>mihini</code> with <code>root</code> user rights, and applications managed by <code>appmon_daemon</code> will be launched using user <code>pi</code> that should give sufficient user rights for most of needs.
cd /etc/ld.so.conf.d/
+
 
sudo /bin/sh -c 'echo "/home/pi/mihini/lib/" > 01-mihini.conf'
+
sudo ldconfig
+
</source>
+
Now the respective ldd commands re-executed should resolve.
+
  
 
==== Stop Mihini manually ====
 
==== Stop Mihini manually ====
Line 54: Line 63:
 
</source>
 
</source>
  
== Step 3 - Setup Koneki environment ==
+
== Step 4 - Setup Koneki environment ==
  
 
* Download and launch [http://www.eclipse.org/koneki/ldt/#installation Lua Development Tools]
 
* Download and launch [http://www.eclipse.org/koneki/ldt/#installation Lua Development Tools]
 
* Install the Mihini Development Tools
 
* Install the Mihini Development Tools
    * Help -> Install new software
+
** Help -> Install new software
    * Work with: `http://download.eclipse.org/koneki/updates-nightly` **NB:** This stills a nightly build.
+
** Work with: <code>http://download.eclipse.org/koneki/updates-nightly</code> '''NB:''' This stills a nightly build.
    * Select the "Mihini Development Tools for Lua"
+
** Select the "Mihini Development Tools for Lua"
 
* Configure the connection to your Raspberry Pi
 
* Configure the connection to your Raspberry Pi
    * Open the perspective "Remote System explorer"
+
** Open the perspective "Remote System explorer"
    * "Define a connection to remote system" -> "Mihini Device"
+
** "Define a connection to remote system" -> "Mihini Device"
    * Fill the "Host name" with your Raspberry Pi's IP address, and "Finish"
+
** Fill the "Host name" with your Raspberry Pi's IP address, and "Finish"
    * Right clic on "Applications", then "Connect…", and fill your credential
+
** Right clic on "Applications", then "Connect…", and fill your credential
  
== Step 4 - Create your first application  ==
+
== 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&nbsp;:). The file is <code>main.lua</code>.  
+
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&nbsp;:). The file is the <code>main.lua</code> from a new LUA Project.  
  
 
<source lang="lua">
 
<source lang="lua">
Line 82: Line 91:
 
</source>  
 
</source>  
  
To run the above example, select the ''main.lua'' file, right-click ''Run As/Lua Remote Application'', it will then be executed on your Raspberry.
+
=== Automatically ===
  
= Step 5 - Install your application =
+
To run the above example, right click on your LUA Project > Export > Mihini > Lua Application Package.
  
== Manually ==
+
Then, you will be able to start, stop, delete and enable or disable the autostart of your application directly from LDT.
  
All you a have to do in order to enable Mihini to handle you application is:
+
=== Manually ===
# Create a launcher
+
# Provide sources
+
  
=== Create a launcher ===
+
==== Create a launcher ====
  
 
Mihini ''Application container'' runs executables. To run a Lua application, we need to create a launcher. In the Mihini world, it is an <em>executable file called <code>run</code></em>. Here is its content:
 
Mihini ''Application container'' runs executables. To run a Lua application, we need to create a launcher. In the Mihini world, it is an <em>executable file called <code>run</code></em>. Here is its content:
Line 101: Line 108:
 
</source>
 
</source>
  
Now the my application folder looks like
+
Now my application folder looks like
 
<source lang="bash">
 
<source lang="bash">
 
$ find raspapp/
 
$ find raspapp/
Line 109: Line 116:
 
</source>
 
</source>
  
=== Install application ===
+
==== Install application ====
  
First of all, I presume you already have an [[#Step_3_-_Start_Mihini_on_your_device|Appmon Daemon running]]. You may wonder which way you can interact with Mihini. While starting, Mihini opens a <code>Telnet</code> server on port <code>2000</code>, it enables you communicate with its runtime. We are about to use it to install an app available at <em>'/tmp/raspapp'</em>, which will be named <em>'sample'</em>, this application will benefit from <em>autostart</em> ( the last <code>true</code> parameter ).
+
First of all, you should be sure that the [http://download.eclipse.org/mihini/doc/agent/Appmon_Daemon.html AppMon Daemon] is running on your device. Secondly, be sure that the appcon is activated. While starting, Mihini opens a <code>Telnet</code> server on port <code>2000</code>, it enables you communicate with its runtime. We are about to use it for activating the appcon and then install an application.
<source lang="bash">$ telnet localhost 2000
+
 
 +
<source lang="bash">
 +
$ telnet localhost 2000
 +
> agent.config.appcon.activate = true
 +
</source>
 +
 
 +
Then restart your agent. <source lang="bash">
 +
> os.exit(1)
 +
## if appmon_deamon is monitoring the agent, it will restart it automatically within seconds
 +
## if not, then launch the agent manually
 +
$ ./runtime/start.sh
 +
</source>
 +
 
 +
Now, We are about to install an app available at '''/tmp/raspapp''', which will be named '''sample''', this application will benefit from ''autostart'' ( the last <code>true</code> parameter ). <source lang="bash">$ telnet localhost 2000
 
Trying 127.0.0.1...
 
Trying 127.0.0.1...
 
Connected to localhost.
 
Connected to localhost.
Line 118: Line 138:
 
Lua interactive shell
 
Lua interactive shell
 
> appcon = require 'agent.appcon'
 
> appcon = require 'agent.appcon'
> = appcon.install('sample', '/tmp/raspapp', true)
+
> appcon.install('sample', '/tmp/raspapp', true)
 
2013-01-22 13:33:45 APPCON-INFO: Installing application "sample"
 
2013-01-22 13:33:45 APPCON-INFO: Installing application "sample"
 
= ok
 
= ok
</source>
+
</source> We can check that the application is properly installed <source lang="lua">
We can check that the application is properly installed
+
> :appcon.list()
<source lang="lua">
+
= { sample = { autostart = true, runnable = true } }
> for app, t in pairs(appcon.list()) do
+
</source>
    print( app )
+
    for field, data in pairs(t) do
+
        print("\t", field, data)
+
    end
+
end
+
  
sample
+
'''Notice''': <code>CTRL-D</code> to quit.  
                autostart      true
+
                runnable        true
+
</source>
+
'''Notice''': <code>CTRL-D</code> to quit.
+
  
We can even check logs:
+
We can even check logs: <source lang="bash">
<source lang="bash">
+
 
$ tail -f /var/log/syslog | grep Mihini
 
$ tail -f /var/log/syslog | grep Mihini
</source>
+
</source> <!-- We may show log output. -->
<!-- We may show log output. -->
+
 
+
== Over the air ==
+
 
+
One day, it will 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
+
  
 
= MISC. TIP & TRICKS =
 
= MISC. TIP & TRICKS =
  
 
* 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...
 
* 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):
+
** For a Sierra Wireless 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):
 
<code>
 
<code>
 
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="1199", ENV{ID_MODEL_ID}=="68a3", ENV{ID_USB_INTERFACE_NUM}=="03", SYMLINK+="ttyATConsole0"
 
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="1199", ENV{ID_MODEL_ID}=="68a3", ENV{ID_USB_INTERFACE_NUM}=="03", SYMLINK+="ttyATConsole0"
Line 161: Line 162:
  
 
** For a serial-USB adapter: http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
 
** For a serial-USB adapter: http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
* Remove Lua comments to save some flash on very tiny devices (could probably be part of the build process btw)
+
* Remove Lua comments to save some flash on very tiny devices (could probably be part of the build process by the way)
 
** <source lang="bash">
 
** <source lang="bash">
 
find . -type f -name '*.lua' -print0 | xargs -0 sed -i '/^[ \t]*--/d'
 
find . -type f -name '*.lua' -print0 | xargs -0 sed -i '/^[ \t]*--/d'

Latest revision as of 07:46, 18 September 2013

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 is to allow someone to take a bare development board and configured it to collect data from the GPIO sensors. All this within an hour!

Please bear in mind that Mihini is still under development.

Step 1 - Get and/or build Mihini

Mihini sources are available from their Git repository, as well as packaged for the most common Linux distributions.

To build Mihini, you have 4 options :

Step 2 - Configure Mihini

If you have installed Mihini from a .deb or a .rpm, you can skip this section.

You may want to use directly this defaultconfig.lua in mihini/lua/agent/ ; but you can also read the comments in this file to get your own configuration.

The agent.deviceId can be generated from your device with the platform.lua corresponding to your platform:

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.

As a service

If you have installed Mihini from a .deb, you have an init script to just do what you want to: /etc/init.d/mihini {start|stop|restart|status|purge}

Or if you have installed Mihini from a .rpm or the AUR (ArchLinux User Repository), you can use systemctl {start|stop|restart|enable|disable} mihini

Manually

On your device, if you have built mihini on a RaspberryPi with user pi:

Firstly, you should link the librairies:

cd /etc/ld.so.conf.d/
sudo /bin/sh -c 'echo "/home/pi/mihini/lib/" > 01-mihini.conf'
sudo ldconfig

Then, you can start it:

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

Notice: we launched appmon_daemon and mihini with root user rights, and applications managed by appmon_daemon will be launched using user pi that should give sufficient user rights for most of needs.


Stop Mihini manually

$ sudo killall agent appmon_daemon

Step 4 - Setup Koneki environment

  • Download and launch Lua Development Tools
  • Install the Mihini Development Tools
  • Configure the connection to your Raspberry Pi
    • Open the perspective "Remote System explorer"
    • "Define a connection to remote system" -> "Mihini Device"
    • Fill the "Host name" with your Raspberry Pi's IP address, and "Finish"
    • Right clic on "Applications", then "Connect…", and fill your credential

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 the main.lua from a new LUA Project.

local log   = require "log"
local sched = require "sched"
local function main()
    log("GENERAL", "INFO", "My first Mihini app is alive :)")
end
 
sched.run(main)
sched.loop()

Automatically

To run the above example, right click on your LUA Project > Export > Mihini > Lua Application Package.

Then, you will be able to start, stop, delete and enable or disable the autostart of your application directly from LDT.

Manually

Create a launcher

Mihini Application container runs executables. To run a Lua application, we need to create a launcher. In the Mihini world, it is an executable file called run. Here is its content:

#!/bin/sh
lua main.lua

Now my application folder looks like

$ find raspapp/
raspapp/
raspapp/run
raspapp/main.lua

Install application

First of all, you should be sure that the AppMon Daemon is running on your device. Secondly, be sure that the appcon is activated. While starting, Mihini opens a Telnet server on port 2000, it enables you communicate with its runtime. We are about to use it for activating the appcon and then install an application.

$ telnet localhost 2000
> agent.config.appcon.activate = true
Then restart your agent.
> os.exit(1)
## if appmon_deamon is monitoring the agent, it will restart it automatically within seconds
## if not, then launch the agent manually
$ ./runtime/start.sh
Now, We are about to install an app available at /tmp/raspapp, which will be named sample, this application will benefit from autostart ( the last true parameter ).
$ telnet localhost 2000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Lua interactive shell
> appcon = require 'agent.appcon'
> appcon.install('sample', '/tmp/raspapp', true)
2013-01-22 13:33:45 APPCON-INFO: Installing application "sample"
= ok
We can check that the application is properly installed
> :appcon.list()
= { sample = { autostart = true, runnable = true } }

Notice: CTRL-D to quit.

We can even check logs:
$ tail -f /var/log/syslog | grep Mihini

MISC. TIP & TRICKS

  • 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 Wireless 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):

SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="1199", ENV{ID_MODEL_ID}=="68a3", ENV{ID_USB_INTERFACE_NUM}=="03", SYMLINK+="ttyATConsole0" SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="1199", ENV{ID_MODEL_ID}=="68a3", ENV{ID_USB_INTERFACE_NUM}=="04", SYMLINK+="ttyATConsole1"

  • Remove Lua comments to save some flash on very tiny devices (could probably be part of the build process by the way)
    • find . -type f -name '*.lua' -print0 | xargs -0 sed -i '/^[ \t]*--/d'
  • Strip binary code, to save flash too
    •  find . -type f -name '*.so' -print0 | xargs -0 $STRIP_EXECUTABLE_PATH