__TOC__= Overview =
This is the 2/3 chapter of the Getting Started with IGEPv2 Tutorial Guide.
= Overview =In this second chapter, we will learn some basics tasks. Upon completion, you will be ready to continue with chapter 3/3 that explains more advanced tasks.
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.__TOC__
= What can I do =
== Handle You must logged in the gpio-LED's =={{#lst:How to handle the gpio-LED|IGEPv2}}board.
== Send a file between your PC and IGEPv2 via SCP How to use serial console ==
''' Basic '''Connect a serial (COM port) cable (known as the AT/Everex Cable) to the 10-pin header J960 on the board. Now you need a Null-Modem DB9 male-make serial cable. Connect the cable between the board and your PC. Open the serial on your PC using your preferred serial communications program (minicom) and configure the port as follows:
In a Linux host PC, you can use SCP * 115200* 8N1* no flow control (secure copyeither software or hardware) via SSH to transfer files between IGEPv2 and your PC.
Now let's transfer a file called originalOpen the serial port and the debug shell prompt should appear.file in your host PC to IGEPv2 in /home/root/
In your Host PC open Terminal and typeA detailed guide on how to connect via serial debug port can be found by following this link:[[Using serial debug port to communicate]]
scp == Handle the GPIO-r original.file root@< IGEPv2 IP >:/home/root/destination.fileLEDS ==
You The board has two user bicolor (green/red) leds available that can repeat the process from the IGEPv2 consolebe controlled. In its simplest form, and transfer a file you can control of LEDs from IGEPv2 to your Host PCuserspace.LEDs appear in /sys/class/leds/ and you can turn on and off with following commands:
$ echo 0 > /sys/class/leds/d240\:green/brightness
== Update your pre-installed software == $ echo 1 > /sys/class/leds/d240\:red/brightness $ echo 0 > /sys/class/leds/d240\:red/brightness
=== Overview === $ echo 1 > /sys/class/leds/d440\:green/brightness $ echo 1 > /sys/class/leds/d440\:red/brightness
# Download the latest firmware''' into an external computer# Uncompress the downloaded file# Create a MicroSD card in your external computer# Plug A detailed guide on how use GPIO-LEDS can be found by following this link: [[How to handle the MicroSD card to IGEPv2 and boot from it.gpio-LED]]
=== Requirements =Handle generic GPIO ==See [[How_to_use_GPIOs|GPIOs HOWTO]] to know details about that.Quick example could be:<pre>echo 156 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio156/directionecho 0 > /sys/class/gpio/gpio156/value</pre>
* a '''microSD card'''<pre>echo 157 > /sys/class/gpio/export * a '''computer''' with microSD card reader (or with adapter)echo in > /sys/class/gpio/gpio157/direction* a '''GNUcat /sys/class/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 cardgpio/gpio157/value</pre>
=== Basic =How to use UART1 (RS232) ==
We are now going to update The board has another UART available on J960 connector (UART1). This UART is shared with RS485 so it's incompatible use both interfaces at the pre-installed software same time. For that reason to the latest versionuse UART1 for RS232 comunications you should disable RS485 interface.You can do this [[How_do_I_edit_my_kernel_command_line | adding following kernel cmdline parameter]]
{{#lst:How to create a SD-card with the latest software image|IGEPv2}} board.ei485=no
Now, you can connect the serial AT/Everex Cable to the 10-pin header J960 on the board. In that case the first pin of the AT/Everex Cable (red) should be connected to the pin number 10 of the header J960. You also need a Null-Modem DB9 male-make serial cable. Connect the cable between the target board and your PC.
== Flash Open the latest software image ==serial port on your PC using your preferred serial communications program (minicom) and configure the port as follows:
{{:How to flash the latest * 115200* 8N1* no flow control (either software image}}or hardware)
On the target board open a serial port as follows:
''' Know more ''' $ microcom -s 115200 /dev/ttyS0
IGEPv2 can run many other software distributions. Check Now when you write a character in you PC serial port, the [[:Category:Software distributions]] to learn how to install other distributionscharacter should appear in the target board.
== Basic instructions ==A detailed guide on how use UARTS can be found by following this link: [[How to use UARTs]]
IGEPv2 is '''compatible with many Linux distributions'''. In this tutorial we are using Poky Linux, which is the pre== How to use RS-installed software from ISEE.485 ==
In case you are not familiar with Bash instructions, here comes some basic instructions {{#lst:How to help you startup with the board.use RS485|overview}}A detailed guide on how use UARTS can be found by following this link: [[How to use RS485]]
First of all, '''log == Get sound in to IGEPv2''' with a console from your host PC (via serial port or via SSHaudio in), as shown previous sections in this article. Remember the default settings:==
login: root password: (none: press return) Once you are logged in IGEPv2External Audio input devices, run such as a powered microphone or the following commands: cd / ls You have moved to the root directoryaudio output of a PC or MP3 player, that is "/".The instruction "ls" lists all the existing files and directories in the current "path". Now let's go can be connected 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 via a 'help' option that can be accessed by inserting the parameter --help3.5mm jack (Audio IN). 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 Note that the text "Hello" board has been designed to use Line In for the standard output, that is the console audio input which means users need to add some type of pre-amp for a microphone to work or use a powered microphone. For a pre-amp for a microphone you are interacting withcan use MAX9812.
But you can change and 'redirect' the output by using the character '>' Enable capture:
echo Hello world! <pre> amixer -c 0 sset 'Analog Right AUXR' capamixer -c 0 sset 'Analog Left AUXL' cap </home/root/name.filepre>
Now notice you have redirected You can record audio in with the output to a file called name.file application arecord, for example:
ls You can append any file using '<pre>>' 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 == ''' Basic '''' Log into IGEPv2 and run any of the following commands: * 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_RS485_on_IGEP0020_board|How to use RS-485 on IGEPv2 board]] == 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</pre>
Following output is expected on console:
boundary : 1073741824
When ever you think you want to stop recording just press CTRL+C
== Get sound out (audio out) ==
''' Basic ''' Connect an '''external output audio device''' to the 3.5mm jack Audio Out connector in IGEPv2the board, 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 == Connect to the Serial Debug interface == ''' Basic '''
[[Image:DSC 0177.JPG|thumb|550px|right|AT/Everex Cable connected == How to the 10-pin serial header on IGEPv2]]use wifi ==
In If you have a wireless network adapter in your computer you can also connect to the preinstalled software, board using the serial port is configured as a '''Debug interface'''ad hoc network connection that the firmware configures byu default.
Therefore, if you Use your wireless manager to connect an external device to the serial port you will be able to see the '''Linux Kernel traces''', as wireless network called in the system boots.form
IGEP_xx
Follow these steps:After connecting, a DHCP IP address should be adquired. Now you can access, for example with ssh, to the target board connecting to the 192.168.7.1 address.
* Connect an '''AT/Everex Cable''' to the '''10-pin serial header''' on IGEPv2 and a '''[http://en $ ssh root@192.wikipedia168.org/wiki/Null_modem null modem] DB9 male-male''' serial cable between the board and your host machine6.1
* Refer to the articleA detailed guide on how use wifi can be found by following this link: '''[[How_to_setup_the_IDC10_cable|How Using IGEP WLAN to setup the IDC10 cablecommunicate]]''' to setup the IDC10 cable.
* You can also == How to use a Serial port in your host machine you might need a '''USB to Serial converter''' to communicate via this port.bluetooth ==
* Run a serial console, or any program that A detailed guide on how use bluetooth can interact with the serial port in your host machine, such Minicom, PuTTy (Linux, Windows), Terminal (Windows), etc.be found by following this link: [[How to setup Marvell bluetooth]]
* Refer == How to this extended article about '''[[Using serial debug port to communicate]]''' to setup use the right configuration of your serial console.SD card ==
You can connect a micro SD card for storage. After plugin the SD card the kernel should detect the card and automount in /media directory.
Now, as you are connected == How to use the '''serial debug port''', you will see the system traces as the board is starting up.USB OTG ==
Finally In order to act in host mode and add some peripherals like keyboard, mouse or pendrives you will see require a special cable that grounds the boot prompt asking for loginID pin. Since the OTG port only provides 100mA of power a USB hub is recommended.
Though a common USB Standard-A to Mini-B type cable the port acts as a device. In this mode you can connect to the board using the USB Ethernet Gadget. Use this cable between your computer and the target board and connect with:
[[Image:Poky-prompt-screenshot $ ssh root@192.png|thumb|550px|center|IGEPv2 Serial Debug interface prompt]]168.7.1
A detailed guide on how use wifi can be found by following this link: [[Using USB ethernet gadget to communicate]]
{{Template:Navigation/IGEP Technology Guides/What can I do/Ending}}
{{Table/IGEP Technology Devices
|Tech_Family={{#lst:Template:Links|IGEPv2_Tech_Family}}
|Tech_ID={{#lst:Template:Links|IGEPv2_Tech_ID}}
|Name={{#lst:Template:Links|IGEPv2_Name}}
|Image={{#lst:Template:Links|IGEPv2_Image}}
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_ISEE_MainPage}}
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_ISEE_Hardware}}
}}
[[Category:IGEP Technology Devices Guides]]
