Difference between revisions of "What can I do with IGEPv2"

From IGEP - ISEE Wiki

Jump to: navigation, search
m (the example had a minor mistake, 'echo "echo Hello world!" > /home/root/example.sh' had an extra >)
(Re-ordered and adapted some sections)
Line 1: Line 1:
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
{{Table/IGEP Technology Devices
|-
+
|Tech_Family={{#lst:Template:Links|IGEPv2_Tech_Family}}
| bgcolor="#cccccc" |'''IGEPv2 - Part 2/3'''
+
|Tech_ID={{#lst:Template:Links|IGEPv2_Tech_ID}}
|-
 
| It is recommended that you '''follow the [[{{#lst:Template:Links|IGEPv2_Community_Guides_1}}|previous chapters]]''' of this guide before continuing with this tutorial.
 
|}
 
 
 
 
 
{{Navigation/IGEP Technology Guides
 
 
|Name={{#lst:Template:Links|IGEPv2_Name}}
 
|Name={{#lst:Template:Links|IGEPv2_Name}}
 
|Image={{#lst:Template:Links|IGEPv2_Image}}
 
|Image={{#lst:Template:Links|IGEPv2_Image}}
 
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_ISEE_MainPage}}
 
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_ISEE_MainPage}}
 
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_ISEE_Hardware}}
 
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_ISEE_Hardware}}
|Community_MainPage={{#lst:Template:Links|IGEPv2_Community_MainPage}}
 
|Community_Guides_1={{#lst:Template:Links|IGEPv2_Community_Guides_1}}
 
|Community_Guides_2={{#lst:Template:Links|IGEPv2_Community_Guides_2}}
 
 
}}
 
}}
  
  
{| cellspacing="0" cellpadding="5" border="1" align="center" style="text-align: left;"
+
__TOC__
|-
+
 
| bgcolor="#cccccc" colspan="3" | '''IGEP Technology Devices Guides - Part 2/3 - Summary'''
+
 
|-
+
= Overview =
| [[Image:{{#lst:Template:Links|IGEPv2_Image}}|250px|center|link={{#lst:Template:Links|IGEPv2_Community_MainPage}}]]
+
 
|-
+
This is the 2/3 chapter of IGEPv2 Tutorial Guide.
|'''1) [[#Booting and setting up|Booting up IGEPv2]]'''
+
 
|-
+
We will learn some basic tasks such to send a file between IGEPv2 and your PC , handle the IGEPv2 Leds, update the pre-installed software to the latest release, etc.
|'''2) [[#Updating the pre-installed software|Updating the pre-installed software]]'''
 
|-
 
|'''3) [[#Flashing the software image|Flashing the latest firmware to the IGEPv2 flash memory]]'''
 
|-
 
|'''4) [[#Connect to IGEPv2 via network interfaces|Connect to IGEPv2 via network interfaces]]'''
 
|-
 
|'''5) [[#Basic instructions|Basic instructions]]'''
 
|-
 
|'''6) [[#Send a file between a PC and IGEPv2|Send a file between a PC and IGEPv2]]'''
 
|-
 
|'''7) [[#How to handle the gpio-LED's|Handle IGEPv2's leds]]'''
 
|-
 
|'''8) [[#Mount a MicroSD card|Mount a MicroSD card]]'''
 
|-
 
|}
 
  
__NOTOC__
 
  
=== Booting and setting up ===
+
= What can I do =
----
 
  
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
== Handle the gpio-LED's ==
|-
 
| bgcolor="#cccccc" |'''Pre-installed software'''
 
|-
 
|By default, '''all brand new IGEP Processor Boards have a firmware installed''' on its flash memory.
 
  
That means that if you power up your board it will run a Linux distribution provided and installed by ISEE.
+
''' Basic '''
|}
 
  
 +
In this tutorial, we are going to use the '''4 LED's available in the board''', which probably is the most simple feature in the board, but sometimes you may want LED's to be a way of checking the status of some of your applications.
  
All IGEP Processor Boards have a pre-installed software which consists of a '''minimal Linux-based distribution''' with a lite X Window System and GNOME Mobile based applications created with '''Poky Platform Builder'''.
+
You can easily '''turn LED's on and off''' using the 'echo' instruction.
  
In the previous chapter of this tutorial, we have booted IGEPv2 with its pre-installed software.
+
Log into IGEPv2 (for example via SSH, as shown in the previous chapter), and run the following commands to turn LED's on:
  
Once the board has booted up, it asks for a login in the serial debug port. You can log in into IGEPv2 via the serial interface.
+
<pre>echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/brightness
 +
echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d240\:red/brightness
 +
echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d440\:green/brightness
 +
echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d440\:red/brightness
 +
</pre>
  
 +
You can turn them down using the same command and write '0' instead of '1'.
  
*The default login user is: '''root'''
 
*There is '''no password''' for this user.
 
  
 +
''' Know more '''
  
'''Boot priority'''
+
IGEPv2 LED's are controlled with it's platform device at /sys/devices/platform/leds-gpio/leds/
  
In fact, IGEPv2 can boot from many other devices (listed by priority):  
+
If you want to trigger the leds you can enable this mode and select the trigger source (none by default) to: mmc0, mmc1, timer, heartbeat and default-on.<br>
  
# from USB
+
To enable any of this modes you just have to change a parameter in the directory of the led you want to control. You can see all the possibilities using the instruction 'cat':<br>
# from UART3
 
# from a MMC/MicroSD card
 
# from OneNAND memory
 
  
 +
<pre>$  cat /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
  
As we haven't set any other boot device rather than the oneNAND (the IGEPv2 flash memory) the system boots from it.
+
[none] mmc0 mmc1 timer heartbeat default-on
 +
</pre>
  
 +
In the example above, we have checked the status of the trigger in led D240:green. Mode 'none' is selected.
  
But, as '''the MicroSD card has an upper priority than the flash''', if you plug a MicroSD card (with the right configuration on it) to the MicroSD card reader, IGEPv2 will boot from it and won't boot from the flash memory.
+
To change it, for example, to the ''timer'' mode you can use 'echo':
  
 +
<pre>echo timer &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
 +
</pre>
  
Now, We are going to use this functionality to update your pre-installed software.
+
In this case, we have set the trigger to the 'timer' mode. Now you can set the time for what the led is ON and the time it is OFF using:
  
=== Updating the pre-installed software ===
+
<pre>echo 250 &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/delay_on
----
+
echo 750 &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/delay_off
 +
</pre>
  
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
Now the selected led is configured with a timer consisting of 250 miliseconds ON and 750 miliseconds OFF.
|-
 
| bgcolor="#cccccc" |'''Requirements - Overview'''
 
|-
 
| For this purpose, you will need:
 
  
* a '''microSD card'''
 
* a '''computer''' with microSD card reader (or with adapter)
 
* a '''GNU/Linux distribution installed''' on the computer (a Linux partition or a virtual machine on Windows)
 
** the main reason is that Windows does not detect multiple partitions on a microSD card
 
|-
 
|1) '''Download the latest firmware''' into an external computer.
 
  
2) '''Uncompress the downloaded file'''.
+
== Send a file between your PC and IGEPv2 via SCP ==
  
3) '''Create a MicroSD card''' in your external computer.
+
''' Basic '''
  
4) '''Plug the MicroSD card''' to IGEPv2 and boot from it.
+
In a Linux host PC, you can use SCP (secure copy) via SSH to transfer files between IGEPv2 and your PC.
|}
 
  
 +
Now let's transfer a file called original.file in your host PC to IGEPv2 in /home/root/
  
We are now going to update the pre-installed software to the latest version.
+
In your Host PC open Terminal and type:
  
{{#lst:How to create a SD-card with the latest software image|IGEPv2}}
+
scp -r original.file root@< IGEPv2 IP >:/home/root/destination.file
  
4) '''Plug the MicroSD card'''
+
You can repeat the process from the IGEPv2 console, and transfer a file from IGEPv2 to your Host PC.
  
Therefore, you are ready to try the MicroSD Card. '''Plug the MicroSD card into IGEPv2''' and '''power up your board'''.
 
  
=== Flashing the software image ===
+
== Update your pre-installed software ==
----
 
  
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
=== Overview ===
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| 1) '''Log into IGEPv2'''
 
  
2) '''Run /opt/firmware/flasher.sh script'''
+
# Download the latest firmware''' into an external computer
|}
+
# Uncompress the downloaded file
 +
# Create a MicroSD card in your external computer
 +
# Plug the MicroSD card to IGEPv2 and boot from it.
  
 +
=== Requirements ===
  
Now your IGEPv2 has the latest firmware '''running from MicroSD card'''.
+
* a '''microSD card'''
 +
* a '''computer''' with microSD card reader (or with adapter)
 +
* a '''GNU/Linux distribution installed''' on the computer (a Linux partition or a virtual machine on Windows)
 +
** the main reason is that Windows does not detect multiple partitions on a microSD card
  
But you might want to write the firmware to the flash memory, so '''you won't need the MicroSD card when booting''' the board. So let's do it.
+
=== Basic ===
  
 +
We are now going to update the pre-installed software to the latest version.
  
''Note: The following process is assuming that your host PC is connected to IGEPv2 via the Serial Debug port. If not, read the Serial Port instructions in the [[Getting Started with IGEPv2|previous chapter of this tutorial]].''
+
{{#lst:How to create a SD-card with the latest software image|IGEPv2}}
  
  
Enter to IGEPv2 using:
+
== Flash the latest software image ==
  
* root as login name
+
If you followed the previous section you have IGEPv2 with the latest firmware '''running from MicroSD card'''. But you might want to write the firmware to the flash memory, so '''you won't need the MicroSD card when booting''' the board.
* an empty password
 
  
The software provided by ISEE has a script that flashes the content of your MicroSD Card to the flash memory in your IGEPv2.
+
The software provided by ISEE has a script that flashes the content of your MicroSD Card to the flash memory in your IGEPv2. You have to run this script, that is located at /opt/firmware directory.
  
You have to run this script, that is located at /opt/firmware directory. Open a Terminal and run:
+
Log into IGEPv2 and run the following commands:
  
 
  cd /opt/firmware
 
  cd /opt/firmware
Line 155: Line 122:
 
  reboot
 
  reboot
  
Enjoy the new firmware running from flash memory.
+
You will have the new firmware running from IGEPv2 flash memory.
  
'''Other references''': [[Update_the_PRE-INSTALLED_software_image_to_a_current_release|'''update your pre-installed software image''']]
 
  
=== Connect to IGEPv2 via network interfaces ===
+
''' Know more '''
----
 
  
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
IGEPv2 can run many other software distributions. Check the [[:Category:Software distributions]] to learn how to install other distributions.
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| 1) '''Plug an ethernet cable to IGEPv2
 
 
 
2) '''Connect via ethernet network''', SSH: root@192.168.x.x
 
 
 
3) '''Connect via wireless network''', SSH: IGEP_WLAN at root@192.168.x.x
 
|}
 
  
You can log into IGEPv2 via many '''interfaces with network connectivity''', such ethernet, wifi, usb-ethernet gadget, etc.
 
  
In this tutorial we are going to connect via an ethernet cable. To to that, you need to set an IP in IGEPv2 (host) and start a SSH session in your PC (client). Let's do it.
+
== Basic instructions ==
 
 
First of all, you will need:
 
 
 
* an '''Ethernet cable'''
 
* a '''Linux or a Windows host PC'''
 
 
 
 
 
Log into IGEPv2 via the '''serial cable to the serial debug port in IGEPv2''', as you have done in the previous chapter of this tutorial guide.
 
 
 
Once you are logged in, run the following command:
 
 
 
ifconfig
 
 
 
This will '''list all the enabled network interfaces''' in your IGEPv2.
 
 
 
We are going to '''focus on 'eth0''''. This is the ethernet interface in your IGEPv2, which is the interface we will '''connect to from our host PC'''.
 
 
 
Connect the ethernet cable between your host PC and IGEPv2 (or through any wired network such switch).
 
 
 
Now, let's '''set an static IP''' to this interface in IGEPv2, so we will be able to reach the target from the PC.
 
 
 
Type the following command in your serial console:
 
 
 
ifconfig eth0 192.168.6.2
 
 
 
 
 
Next, set an '''IP within the subnet''' in your host PC, for example: 192.168.6.3
 
 
 
Then, run a '''SSH client''' such '''Putty''' and start a SSH session to the target from your host PC.
 
 
 
You can download it from its official page at: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
 
 
 
Install and run Putty. It will look like this:
 
 
 
[[Image:Putty ssh.png|center]]
 
 
 
# Select the '''SSH''' at connection type.
 
# Next insert the '''IP address of the target'''. In this case, the IGEPv2 IP you have already set (192.168.6.3).
 
# Ensure that the port is set to '''22''', the default for SSH communications.
 
# Finally, push the '''Open button''' to start the SSH session.
 
 
 
 
 
If everything goes right, you will be able to access to an IGEPv2 console from your PC via ethernet.
 
 
 
=== Basic instructions ===
 
----
 
 
 
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
 
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| Learn some Bash basic instructions in Linux (for newbies).
 
 
1) Create, edit, move and delete files
 
 
 
2) Run a simple script
 
|}
 
  
 
IGEPv2 is '''compatible with many Linux distributions'''. In this tutorial we are using Poky Linux, which is the pre-installed software from ISEE.
 
IGEPv2 is '''compatible with many Linux distributions'''. In this tutorial we are using Poky Linux, which is the pre-installed software from ISEE.
Line 325: Line 223:
  
  
=== Send a file between a PC and IGEPv2 ===
+
== Mount a MicroSD card ==
----
 
 
 
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
 
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| Transfer a file from IGEPv2 to your PC via SCP
 
|}
 
 
 
In a Linux host PC, you can use SCP (secure copy) via SSH to transfer files between IGEPv2 and your host PC.
 
 
 
First of all, set an static IP to your Linux Host (for example, 192.168.6.3) and another IP within the subnet for IGEPv2 (for example, 192.168.6.2).
 
 
 
First of all, you check the connectivity (From IGEPv2 console):
 
 
 
ping 192.168.6.3
 
 
 
Press CTRL-C to stop the command.
 
 
 
Now let's transfer a file called original.file in your host PC to IGEPv2 in /home/root/
 
 
 
In your Host PC open Terminal and type:
 
 
 
scp -r original.file root@192.168.6.2:/home/root/destination.file
 
 
 
You can repeat the process from the IGEPv2 console, and transfer a file from IGEPv2 to your Host PC.
 
 
 
=== How to handle the gpio-LED's ===
 
----
 
 
 
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
 
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| Using IGEPv2 LED's with the associated platform device at /sys/devices/platform/leds-gpio/leds/
 
|}
 
 
 
IGEPv2 has many devices that can be controlled using '''simple instructions'''.
 
 
 
In this tutorial, we are going to use the '''4 LED's available in the board''', which probably is the most simple feature in the board, but sometimes you may want LED's to be a way of checking the status of some of your applications.
 
 
 
You can easily '''turn LED's on and off''' using the 'echo' instruction.
 
 
 
Log into IGEPv2 (via serial port or via SSH, as shown before), and run the following commands to turn LED's on:
 
 
 
<pre>echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/brightness
 
echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d240\:red/brightness
 
echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d440\:green/brightness
 
echo 1 &gt; /sys/devices/platform/leds-gpio/leds/d440\:red/brightness
 
</pre>
 
 
 
You can turn them down using the same command and write '0' instead of '1'.
 
 
 
'''Other functionalities'''
 
 
 
If you want to trigger the leds you can enable this mode and select the trigger source (none by default) to: mmc0, mmc1, timer, heartbeat and default-on.<br>
 
 
 
To enable any of this modes you just have to change a parameter in the directory of the led you want to control. You can see all the possibilities using the instruction 'cat':<br>
 
 
 
<pre>$  cat /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
 
 
 
[none] mmc0 mmc1 timer heartbeat default-on
 
</pre>
 
 
 
In the example above, we have checked the status of the trigger in led D240:green. Mode 'none' is selected.
 
 
 
To change it, for example, to the timer mode you can use 'echo':
 
 
 
<pre>echo timer &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
 
</pre>
 
 
 
In this case, we have set the trigger to the 'timer' mode. Now you can set the time for what the led is ON and the time it is OFF using:
 
 
 
<pre>echo 250 &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/delay_on
 
echo 750 &gt; /sys/devices/platform/leds-gpio/leds/d240\:green/delay_off
 
</pre>
 
 
 
Now the selected led is configured with a timer consisting of 250 miliseconds ON and 750 miliseconds OFF.
 
 
 
 
 
=== Mount a MicroSD card ===
 
 
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
 
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
 
|-
 
|-
Line 415: Line 232:
  
  
(Work in progress section!)
+
=== Access to Generic FAT32 microSD  ===
 
 
==== Access to Generic FAT32 microSD  ====
 
  
 
  mount -t vfat /dev/mmcblk0 /mnt/tmp/
 
  mount -t vfat /dev/mmcblk0 /mnt/tmp/
  
==== Access to Generic USB Flash disk ====
+
=== Access to Generic USB Flash disk ===
  
 
  mount -t vfat /dev/sda1 /mnt/tmp/
 
  mount -t vfat /dev/sda1 /mnt/tmp/
  
==== Safety Remove microSD  ====
+
=== Safety Remove microSD  ===
  
 
  umount /mnt/tmp
 
  umount /mnt/tmp
  
==== Access to IGEP demo microSD  ====
+
=== Access to IGEP demo microSD  ===
  
 
  mount -t jffs2 /dev/mmcblk0 /mnt/tmp/
 
  mount -t jffs2 /dev/mmcblk0 /mnt/tmp/
  
=== How to use RS-485  ===
 
----
 
  
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
== How to use RS-485 ==
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| Follow the link to the extensive article: [[How_to_use_RS485_on_IGEP0020_board|How to use RS-485 on IGEPv2 board]]
 
|}
 
  
 +
Follow the link to the extensive article: [[How_to_use_RS485_on_IGEP0020_board|How to use RS-485 on IGEPv2 board]]
  
=== How to get sound out (audio out) ===
 
----
 
  
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
+
== How to get sound in (audio in) ==
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| Use: aplay
 
|}
 
  
The amplifiers for the headset output are disabled by default, so the first thing you'll do is enable these amplifiers with:
+
''' Basic '''
  
amixer set -D hw:0 'Headset' 0dB
+
External Audio input devices, such as a powered microphone or the audio output of a PC or MP3 player, can be connected to the via a 3.5mm jack (Audio IN).
amixer set -D hw:0 'HeadsetL Mixer AudioL2' on
 
amixer set -D hw:0 'HeadsetR Mixer AudioR2' on
 
 
 
Then you can easily play a *.wav sound with the application Aplay, for example:
 
 
 
aplay sample.wav
 
 
 
=== How to get sound in (audio in) ===
 
 
 
{| cellspacing="0" cellpadding="5" border="1" align="center" width="100%" style="text-align: left;"
 
|-
 
| bgcolor="#cccccc" |'''Overview'''
 
|-
 
| Use: arecord
 
|}
 
  
 
You can record audio in with the application Arecord, for example:
 
You can record audio in with the application Arecord, for example:
Line 506: Line 293:
  
 
When ever you think you want to stop recording just press CTRL+C  
 
When ever you think you want to stop recording just press CTRL+C  
 +
 +
 +
== How to get sound out (audio out) ==
 +
 +
''' Basic '''
 +
 +
Connect an '''external output audio device''' to the 3.5mm jack Audio Out connector in IGEPv2, such as external stereo powered speakers.
 +
 +
The amplifiers for the headset output are disabled by default, so the first thing you'll do is enable these amplifiers with:
 +
 +
amixer set -D hw:0 'Headset' 0dB
 +
amixer set -D hw:0 'HeadsetL Mixer AudioL2' on
 +
amixer set -D hw:0 'HeadsetR Mixer AudioR2' on
 +
 +
Then you can easily play a *.wav sound with the application Aplay, for example:
 +
 +
aplay audio-in.wav
 +
  
 
{{Navigation/IGEP Technology Devices Guides/Next Step
 
{{Navigation/IGEP Technology Devices Guides/Next Step
Line 514: Line 319:
  
 
[[Category:IGEP Technology Devices Guides]]
 
[[Category:IGEP Technology Devices Guides]]
[[Category:IGEP0020]]
 
[[Category:Work in progress]]
 

Revision as of 11:41, 2 August 2012



Overview

This is the 2/3 chapter of IGEPv2 Tutorial Guide.

We will learn some basic tasks such to send a file between IGEPv2 and your PC , handle the IGEPv2 Leds, update the pre-installed software to the latest release, etc.


What can I do

Handle the gpio-LED's

Basic

In this tutorial, we are going to use the 4 LED's available in the board, which probably is the most simple feature in the board, but sometimes you may want LED's to be a way of checking the status of some of your applications.

You can easily turn LED's on and off using the 'echo' instruction.

Log into IGEPv2 (for example via SSH, as shown in the previous chapter), and run the following commands to turn LED's on:

echo 1 > /sys/devices/platform/leds-gpio/leds/d240\:green/brightness
echo 1 > /sys/devices/platform/leds-gpio/leds/d240\:red/brightness
echo 1 > /sys/devices/platform/leds-gpio/leds/d440\:green/brightness
echo 1 > /sys/devices/platform/leds-gpio/leds/d440\:red/brightness

You can turn them down using the same command and write '0' instead of '1'.


Know more

IGEPv2 LED's are controlled with it's platform device at /sys/devices/platform/leds-gpio/leds/

If you want to trigger the leds you can enable this mode and select the trigger source (none by default) to: mmc0, mmc1, timer, heartbeat and default-on.

To enable any of this modes you just have to change a parameter in the directory of the led you want to control. You can see all the possibilities using the instruction 'cat':

$   cat /sys/devices/platform/leds-gpio/leds/d240\:green/trigger

[none] mmc0 mmc1 timer heartbeat default-on

In the example above, we have checked the status of the trigger in led D240:green. Mode 'none' is selected.

To change it, for example, to the timer mode you can use 'echo':

echo timer > /sys/devices/platform/leds-gpio/leds/d240\:green/trigger

In this case, we have set the trigger to the 'timer' mode. Now you can set the time for what the led is ON and the time it is OFF using:

echo 250 > /sys/devices/platform/leds-gpio/leds/d240\:green/delay_on
echo 750 > /sys/devices/platform/leds-gpio/leds/d240\:green/delay_off

Now the selected led is configured with a timer consisting of 250 miliseconds ON and 750 miliseconds OFF.


Send a file between your PC and IGEPv2 via SCP

Basic

In a Linux host PC, you can use SCP (secure copy) via SSH to transfer files between IGEPv2 and your PC.

Now let's transfer a file called original.file in your host PC to IGEPv2 in /home/root/

In your Host PC open Terminal and type:

scp -r original.file root@< IGEPv2 IP >:/home/root/destination.file

You can repeat the process from the IGEPv2 console, and transfer a file from IGEPv2 to your Host PC.


Update your pre-installed software

Overview

  1. Download the latest firmware into an external computer
  2. Uncompress the downloaded file
  3. Create a MicroSD card in your external computer
  4. Plug the MicroSD card to IGEPv2 and boot from it.

Requirements

  • a microSD card
  • a computer with microSD card reader (or with adapter)
  • a GNU/Linux distribution installed on the computer (a Linux partition or a virtual machine on Windows)
    • the main reason is that Windows does not detect multiple partitions on a microSD card

Basic

We are now going to update the pre-installed software to the latest version.



Flash the latest software image

If you followed the previous section you have IGEPv2 with the latest firmware running from MicroSD card. But you might want to write the firmware to the flash memory, so you won't need the MicroSD card when booting the board.

The software provided by ISEE has a script that flashes the content of your MicroSD Card to the flash memory in your IGEPv2. You have to run this script, that is located at /opt/firmware directory.

Log into IGEPv2 and run the following commands:

cd /opt/firmware
./flash.sh

This will last a few minutes. When it is ready, unplug the SD card from IGEPv2 and reboot the board:

reboot

You will have the new firmware running from IGEPv2 flash memory.


Know more

IGEPv2 can run many other software distributions. Check the Category:Software distributions to learn how to install other distributions.


Basic instructions

IGEPv2 is compatible with many Linux distributions. In this tutorial we are using Poky Linux, which is the pre-installed software from ISEE.

In case you are not familiar with Bash instructions, here comes some basic instructions to help you startup with the board.

First of all, log in to IGEPv2 with a console from your host PC (via serial port or via SSH), as shown previous sections in this article. Remember the default settings:

login: root
password: (none: press return)

Once you are logged in IGEPv2, run the following commands:

cd /
ls

You have moved to the root directory, that is "/". The instruction "ls" lists all the existing files and directories in the current "path".

Now let's go to the directory /home/root/ with:

cd /home/root/

You can always check at which directory you are with the instruction:

pwd

Most instructions include a 'help' option that can be accessed by inserting the parameter --help. Check out the help page of 'echo' instruction, for example:

echo --help

You can try the instruction by yourself and type:

echo Hello

You have sent the text "Hello" to the standard output, that is the console you are interacting with.

But you can change and 'redirect' the output by using the character '>' :

echo Hello world! > /home/root/name.file

Now notice you have redirected the output to a file called name.file :

ls

You can append any file using '>>' instead of '>'. You can print the content of the file to the standard output:

cat /home/root/name.file

Building a basic script

You can create a script that can run any instruction you want to use in Bash. The main advantage is that you do not have to compile the code, as is auto-interpereted by the system.

We are going to create a basic 'Hello World' script that is going to run the same command you have actually used before:

echo "echo Hello world!" > /home/root/example.sh
cat example.sh

Now you have created a file called example.sh, but by default it has no execute permissions (x):

ls -la

We are going to add permission to the file by:

chmod a+x example.sh
ls -la

Now you can run the script:

./example.sh

You can edit this file (example.sh) with 'vi', the pre-installed text editor in IGEPv2.

vi example.sh

Press ESC and:

  •  :q! , to exit without saving
  •  :w , to save
  •  :wq , to quit and save
  • i , to insert text

Other simple & useful instructions

  • mkdir
  • rmdir
  • find
  • grep

You can stop any instruction by pressing CTRL+C


Mount a MicroSD card

Overview
Mount the MicroSD card partitions into IGEPv2


Access to Generic FAT32 microSD

mount -t vfat /dev/mmcblk0 /mnt/tmp/

Access to Generic USB Flash disk

mount -t vfat /dev/sda1 /mnt/tmp/

Safety Remove microSD

umount /mnt/tmp

Access to IGEP demo microSD

mount -t jffs2 /dev/mmcblk0 /mnt/tmp/


How to use RS-485

Follow the link to the extensive article: How to use RS-485 on IGEPv2 board


How to get sound in (audio in)

Basic

External Audio input devices, such as a powered microphone or the audio output of a PC or MP3 player, can be connected to the via a 3.5mm jack (Audio IN).

You can record audio in with the application Arecord, for example:

arecord -t wav -c 2 -r 44100 -f S16_LE -v audio-in.wav

Following output is expected on console:

Recording WAVE 'audio-in.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Plug PCM: Hardware PCM card 0 'TWL4030' device 0 subdevice 0
Its setup is:
stream       : CAPTURE
access       : RW_INTERLEAVED
format       : S16_LE
subformat    : STD
channels     : 2
rate         : 44100
exact rate   : 44100 (44100/1)
msbits       : 16
buffer_size  : 32768
period_size  : 2048
period_time  : 46439
tick_time    : 7812
tstamp_mode  : NONE
period_step  : 1
sleep_min    : 0
avail_min    : 2048
xfer_align   : 2048
start_threshold  : 1
stop_threshold   : 32768
silence_threshold: 0
silence_size : 0
boundary     : 1073741824

When ever you think you want to stop recording just press CTRL+C


How to get sound out (audio out)

Basic

Connect an external output audio device to the 3.5mm jack Audio Out connector in IGEPv2, such as external stereo powered speakers.

The amplifiers for the headset output are disabled by default, so the first thing you'll do is enable these amplifiers with:

amixer set -D hw:0 'Headset' 0dB
amixer set -D hw:0 'HeadsetL Mixer AudioL2' on
amixer set -D hw:0 'HeadsetR Mixer AudioR2' on

Then you can easily play a *.wav sound with the application Aplay, for example:

aplay audio-in.wav


Continue with this tutorial at: Start developing under IGEP Technology