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

From Eclipsepedia

Jump to: navigation, search
m (Step 1 - Get Mihini)
m (Install application)
 
(30 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.
  
=== Manually ===
+
=== As a service ===
  
On your device, here a <em>RaspberryPi</em> with user <code>pi</code>.
+
If you have installed Mihini from a <code>.deb</code>, you have an init script to just do what you want to: <code>/etc/init.d/mihini {start|stop|restart|status|purge}</code>
  
<source lang="bash">
+
Or if you have installed Mihini from a <code>.rpm</code> or the AUR (ArchLinux User Repository), you can use <code>systemctl {start|stop|restart|enable|disable} mihini</code>
$ 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>
+
  
'''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.
+
=== Manually ===
  
'''Possible starting issues'''
+
On your device, if you have built mihini on a <em>RaspberryPi</em> with user <code>pi</code>:
The execution of ps aux must show something like the following line to successfully verify that the daemon is running:
+
 
<source lang="bash">
+
Firstly, you should link the librairies:
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
+
</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">
 
<source lang="bash">
Line 40: Line 46:
 
sudo ldconfig
 
sudo ldconfig
 
</source>
 
</source>
Now the respective ldd commands re-executed should resolve.
 
  
==== Stop Mihini manually ====
+
Then, you can start it:
  
 
<source lang="bash">
 
<source lang="bash">
$ sudo killall agent appmon_daemon
+
$ 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>
  
=== As a service ===
+
'''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.
  
Soon :)
 
WIP lbarthelemy
 
  
== Step 3 - Setup Koneki environment ==
+
==== Stop Mihini manually ====
  
* Download Lua Development Tools
+
<source lang="bash">
* Install [http://wiki.eclipse.org/Koneki/LDT/Developer_Area/User_Guides/User_Guide_1.0#Remote_session Remote Development Support for LDT]  
+
$ sudo killall agent appmon_daemon
* Configure the remote target in the Koneki environment
+
</source>
** Define your device and configure its <em>"SSH Lua"</em> paths like this (to reach the presented view, open the Views "Remote Systems" and "Properties". In "Properties" toggle ''Show Advanced Properties'' to true, then select "Ssh Lua" from the "Remote Systems" View) [[Image:SshLuaConfiguration.png|center]]
+
 
*** If you want the text version
+
== Step 4 - Setup Koneki environment ==
<code><pre>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
+
* Download and launch [http://www.eclipse.org/koneki/ldt/#installation Lua Development Tools]
LD_LIBRARY_PATH: $LD_LIBRARY_PATH:/home/pi/mihini/lib</pre></code>
+
* Install the Mihini Development Tools
* Configure the <em>"Mihini execution environment"</em>
+
** Help -> Install new software
** Download the latest Mihini execution environment [http://download.eclipse.org/mihini/mihini-0.8.zip here]
+
** Work with: <code>http://download.eclipse.org/koneki/updates-nightly</code> '''NB:''' This stills a nightly build.
** Setup this Execution Environment in your LDT environment (Preferences > Lua > Execution Environments))
+
** Select the "Mihini Development Tools for Lua"
* Create a launch/debug configuration and test your script.
+
* 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 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 83: 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 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 <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:
  
 
<source lang="bash">
 
<source lang="bash">
 
#!/bin/sh
 
#!/bin/sh
 
+
lua main.lua
# 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
+
 
</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 117: 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 126: 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
+
                autostart       true
+
                runnable       true
+
</source>
+
'''Notice''': <code>CTRL-D</code> to quit.
+
 
+
We can even check logs:
+
<source lang="bash">
+
$ cat /var/log/syslog | grep Mihini
+
</source>
+
<!-- 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:
+
'''Notice''': <code>CTRL-D</code> to quit.
  
* Use the Koneki tools to create an application package
+
We can even check logs: <source lang="bash">
* Deploy the package on a publically available web server
+
$ tail -f /var/log/syslog | grep Mihini
* Connect to the Mihini console and for a connection to the testing server
+
</source> <!-- We may show log output. -->
  
 
= 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 169: 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 08: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.

Contents

[edit] 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 :

[edit] 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:

[edit] 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.

[edit] 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

[edit] 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.


[edit] Stop Mihini manually

$ sudo killall agent appmon_daemon

[edit] 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

[edit] 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()

[edit] 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.

[edit] Manually

[edit] 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

[edit] 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

[edit] 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