Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Mihini/Run Mihini on an Open Hardware platform

< Mihini
Revision as of 04:46, 12 September 2012 by Unnamed Poltroon (Talk)

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 should be updatable over-the-air.

Step 1 - Build Mihini

  • Download the sources
  • Cross-compile (or compile directly on the target) the Mihini runtime
  • TODO at that stage, can we try to create a dpkg? That'd be very useful...

Step 1 (alternative) - Get a ready-to-use "Mihini for XXX" SD card binary image

  • Download a ready-to-use .img file and put it on the SD card used on the development board

Step 2 - Configure network connection

3G connection

Ethernet connection

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

Step 3 - Configure Mihini

  • Enable the application container
  • Enable (and configure) the update manager (?)

Step 4 - Setup Koneki environment

  • Download Lua Development Tools
  • Install "Mihini target management"
  • Configure the "Mihini execution environment" (provides nice autocompletion...)

Step 5 - Create your first application

  • TODO (blink a LED, use a touch sensor, measure the temperature and available RAM of the board...)

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

Step 7 - Install your application over the air

  • 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

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

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"

TODO

Back to the top