4,199
edits
Changes
m
Update peripheral Categorize new tutorials, finish gpio example program<br>
Categorize new tutorials<br>How to manage the kernel modules on Linux
Finish tutorials below<br> How do I edit my kernel command line
Upgrade IGEP Technology Devices Guides == AUDIO DSP-ARM==
Link all development tools documentation when possible===Included (IGEP GST DSP):==='''AACHEDEC -> DEC AACHE (OK)'''
= Using IGEP WLAN to communicate =http://download.wavetlan.com/SVV/Media/HTTP/FAAC-HE-AAC.aac
If your IGEP Processor Board has '''WIFI interface''' you can connect to it without any cable. You can open a SSH session in your computer and interact with your Board from your console. Here is how to. outofthebox->ok
== Requirements ==----
There are some requisites to follow this guide: '''MP3DEC -> DEC MP3 (AUDIO ERRORS)'''
*- Followed README file from ISEE - IGEP Processor Board with WIFI *Host computer with WIFI *MicroSD Card (optional: If your board has old Firmware) *[http://wwwDSP - GST + DMAI Support Package 3.chiark40.greenend.org.uk/~sgtatham/putty/download.html PuTTy program]00
== Update pre-installed software ==http://www.stephaniequinn.com/Music/Canon.mp3
'''NOTE: '''Follow these steps if you use an older firmware release gst-launch --gst-debug-level=2 filesrc location=Canon.mp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0.25 ! alsasink sync=false
== Connect to IGEP network =='''mp3-plugin doesn't resolve the error'''
Follow these steps to connect to your IGEP device: ----
*Click on the Network Manager Tray icon. *Select IGEP_<xx> network, where <xx> is different for every IGEP device, to connect.'''G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)'''
{| cellspacing'''G711ENC -> ENC PCM uLAW (speech) (NOT TESTED)''' ===Not included (IGEP GST DSP):==='''ACCLCDEC -> DEC AACLE (NOT TESTED)''' '''AACLDDEC -> DEC AACLD (NOT TESTED)''' '''WMA9 -> DEC WMA9 (COMPILING ISSUES)''' '''ACCLCENC -> ENC AACLE (NOT TESTED)''' '''ACCHEENC -> ENC AACHE (NOT TESTED)''' '''AACLDENC -> ENC AACLD (NOT TESTED)''' '''WMA8 -> ENC WMA8 (NOT TESTED)''' '''Problems adding codecs into igep-gst-dsp''' == DM3730== === DM3730: Decode a MP3 file (OK) (ADDED TO REPOSISTORIES)=== '''under contruction''' '''does not have an accelerated audio decoder element''' - Compiled gst-plugins-ugly using yocto tools - rpm -igst-plugins-ugly-0.*.rpm - rpm -i libmad0-0.*.rpm - rpm -i gst-plugins-ugly-mad-0.*.rpm - gst-launch filesrc location=sample.mp3 ! mad ! volume volume=0.25 ! alsasink === DM3730: Decode a RA or RM audio file (ERRORS)=== gst-launch --gst-debug-level=3 filesrc location=sample.ra ! rmdemux ! volume volume=0.25 ! alsasink http://www.superluminal.com/andalib/ra/listen.ra gst-plugins-ugly-rmdemux-0.10.19-r1.armv7a.rpm libgstsdp-0.10-0-0.10.36-r3.armv7a.rpm:libgstsdp-0.10-0 libgstsdp-0.10.so.0 libgstrtsp-0.10-0-0.10.36-r3.armv7a.rpm:libgstrtsp-0.10-0 libgstrtsp-0.10.so.0 '''Error:''' 0:00:00.084839071 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC 0:00:00.085052695 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC 0:00:00.085540976 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id .ra4 0:00:00.085693564 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC 0:00:00.085815634 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC 0:00:00.085907187 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id RaTC === DM3730: Decode an AAC audio file (OK)=="1" cellpadding="1" border EXTRA_OECONF +="1" width--disable-examples --disable-experimental --disable-sdl --disable-cdaudio --disable-directfb \ --with-plugins=musicbrainz,wavpack,ivorbis,mpegvideoparse,'''faad2''' --disable-vdpau --disable-apexsink \ --disable-orc"200"|Install: faad2-2.7-r2.armv7a.rpm| [[Image:Igep wificon1libfaad2-2.7-r2.armv7a.png|331px]] rpm| [[Image:Igep wificon2gst-plugins-bad-faad-0.10.23-r2.armv7a.png|331px]]rpm|}'''maybe there are necessary more packages, compare actual gst-bad-recipe and add changes. Necessary add faad2 recipe'''<suppre>Click to enlarge imagebitbake faad2 gst-plugins-bad</suppre><pre>rpm -i faad2-2.7-r2.armv7a.rpmrpm -i libfaad2-2.7-r2.armv7a.rpmrpm -i gst-plugins-bad-faad-0.10.23-r2.1.armv7a.rpm </pre> gst-launch --gst-debug-level=3 filesrc location=sample.aac ! faad ! volume volume=0.10 ! alsasink ==== DM3730: Decode an WMA audio file (OK)==== <pre>bitbake gst-ffmpeg</pre> <pre>gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink </pre> === DM3730: Decode an OGG audio file (OK)=== '''Into repositories (base plugins):''' http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
Follow these steps to get a remote shell prompt: == BASE0033 CONNECTOR SUMMARY TABLE==
*Open PuTTy program *Host Name:192.168.1.1 *Port: 22 *Connection type: SSH *Click Open, accept Security Alert and login as root user== Configure a static IP using the same private network range ==
{| cellspacing="1" cellpadding="1" border="1" width="200"|-| [[Image:Igep wifiputty1.png|331px]] | [[Image:Igep wifiputty2.png|331px]]|-| [[Image:Igep wifiputty3.png|331px]] | [[Image:Igep wifiputty4.png|331px]]|}'''under construction'''
'''<sup>Click to enlarge image</sup>''' IGEP Firmware Yocto uses the following Ethernet network configuration (IP addresses)
Note that a DHCP IP address in range *eth0 − 192.168.6.10-192.168.6.254 should be given to your host PC. The IGEP device should have IP address 192.168.65.1*eth0:0 − assigned via dhcp.
== Troubleshooting ==This Ethernet network configuration is really useful when you work using a Linux operating system like IGEP SDK Virtual Machine. Because you use eth0 device to communicate easily with your board and eth0:0 device to get Internet acces using dhcp protocol.
=== NFS in rootfilesystem ===But some scenarios this network configuration is not useful, for example: if you use a non-Linux operating system, connect to two IP private range interfaces is not simple. This How-to can be useful to
Don't use NFS in rootfilesystem combined with WIFI(Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration)
= Connect using USB Ethernet Gadget/RNDIS driver =
== Overview ==
The Linux kernel has a class of drivers called USB Gadgets that allow you to use USB as a transport for a number of different protocols like serial, virtual file systems and Ethernet devices.
The USB OTG connector supports using the Ethernet Gadget to create a networking device over USB. From the client's (and host's) perspective this driver simply appears as another Ethernet device, enabling us to have Ethernet access on the board by hooking them up to a desktop, so this USB slave device can communicate with a properly configured USB host.
== Requirements ==
There are some requisites to follow this guide:
*IGEP Processor Board
*MicroSD Card (optional: If your board has Poky Firmware)
*[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTy program]
== Update pre-installed software ==
'''NOTE: '''Follow these steps if you use an older firmware release
''(from [[How to create a SD-card with the latest software image]])'' {{:How to create a SD-card with the latest software image}}
== Connect to IGEP device<br> ==
=== Linux ===
'''NOTE:''' You should have the usbnet module available for your Linux kernel. On most distributions, this is the case by default. If this is not the case for your distribution, you will need to enable USB networking support in the kernel. If you build your own kernel then you want 'CDC Ethernet support' in USB Network adaptors.
*In the file /etc/network/interfaces, you should add:
<pre>iface usb0 inet dhcp</pre>
*Plug an USB Type-A to USB Type-A mini cable between your host PC and the USB OTG from IGEP device. Use a powered USB Hub if you use IGEP COM MODULE or PROTON.
*If you use IGEP SDK VM you need to attach the [http://labs.isee.biz/index.php/IGEP_SDK_Virtual_Machine#Attach_removable_devices_to_Virtual_Machine removable device] RNDIS driver.
*Type in a terminal:
<pre>sudo ifup usb0</pre>
*Revise that:
<pre>jdoe@ubuntu ~ $ ifconfig
...
usb0 Link encap:Ethernet HWaddr 66:cc:f2:be:51:b6
inet addr:192.168.7.10 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::64cc:f2ff:febe:51b6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2496 (2.4 KB) TX bytes:8794 (8.7 KB)
...</pre>
*Connect to IGEP device
jdoe@ubuntu ~ $ ssh root@192.168.7.1
The authenticity of host '192.168.7.1 (192.168.7.1)' can't be established.
ECDSA key fingerprint is 80:be:2d:b6:fe:b1:09:c3:3b:ac:0f:1d:f2:43:f2:20.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.7.1' (ECDSA) to the list of known hosts.
root@igep00x0:~# uname -a
Linux igep00x0 2.6.37 #1 Thu Jul 19 09:07:47 CEST 2012 armv7l GNU/Linux
root@igep00x0:~#
==== Troubleshooting ====
===== WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! =====
In the case of the SSH client in Linux, a changed host key results in the client refusing to connect and showing an remote host identification has changed error
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
8d:0b:29:f0:0a:a1:f5:56:0c:12:18:b0:26:02:6d:9d.
Please contact your system administrator.
Add correct host key in /home/eballetbo/.ssh/known_hosts to get rid of this message.
Offending key in /home/eballetbo/.ssh/known_hosts:57
RSA host key for 192.168.7.1 has changed and you have requested strict checking.
To fix the problem edit your ~/.ssh/known_hosts and remove the line corresponding to this host.
===== NFS in root filesystem =====
Don't use NFS in rootfilesystem combined with USB Ethernet Gadget
=== Windows and MAC OSX<br> ===
Use [[IGEP SDK Virtual Machine|IGEP SDK Virtual Machine]] to develop under IGEP Technology
[[Category:USB]] [[Category:How_to_forge]]
= How to use GPIOs (update it) =
== Overview ==
This How-To is meant to be a starting point for people to learn use GPIOs for IGEP v2 devices as quickly and easily as possible. For this how-to i used [http://releases.linaro.org/platform/linaro-m/headless/final/linaro-m-headless-tar-20101108-2.tar.gz Linaro Headless] with [[Linux Kernel 2.6.35.y|Kernel 2.6.35.y]], Ubuntu 10.04 with Linaro Toolchain, IGEP v2 RC5 and [http://downloads.igep.es/labs/gpio-driver.tar.bz2 GPIO driver].
There are more ways to use GPIOs in IGEP v2, but this one is very simple.<br>
== Feedback and Contributing ==
At any point, if you see a mistake you can contribute to this How-To.<br>
== Compile GPIO driver source code via Host<br> ==
Download [http://downloads.igep.es/labs/gpio-driver.tar.bz2 GPIO driver] and [[Linux Kernel 2.6.35.y|Kernel 2.6.35.y]] source code. Extract files.<br>
Edit GPIO driver Makefile's:
-In files: $/app/Makefile and $/lib/Makefile, make sure that your CROSS_COMPILE path is correct.
-In file: $/modules/Makefile, make sure that your CROSS_COMPILE path is correct and type your Kernel 2.6.35.y path.<br>
We will use the ncurses program for set up Kernel configuration, if you don't have this program installed then you must install it with this command:
<pre>sudo apt-get install ncurses-dev
</pre>
-Go to kernel path and type:
<pre>make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- igep00x0_defconfig
</pre>
Exit Linux Kernel Configuration an return to Bash. Type:
<pre>make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_prepare
</pre>
File $/include/generated/autoconf.h was created
Finally compile GPIO driver, go to main Makefile path and compile all source code using make command.
Send binaries created from Host to Igep v2. <br>
== Install binaries via IGEP<br> ==
Log with root user to install binaries.
=== Install module ===
Go to:$/modules and insert user-gpio-drv.ko into linux kernel with the following command:
<pre>insmod user-gpio-drv.ko
</pre>
Check that user-gpio-drv.ko is currently loaded with the following command:
<pre>lsmod</pre>
The result will be similar at that: <br>
<pre>root@localhost:~/gpio-driver/module# lsmod
Module Size Used by
user_gpio_drv 1639 0
omap_wdt 3411 0
spidev 4198 0
iommu 8558 0
rtc_twl 4411 0
rtc_core 11187 1 rtc_twl
twl4030_keypad 2970 0
</pre>
The module is loaded until system halt.
=== Install shared library ===
Go to:$/lib. libgpio.so is here.
If a program is linked with shared libraries, Kernel seek in specific paths when program is executed. Now is necessary link the libgpio.so path to the environment variable LD_LIBRARY_PATH, use the following command:<br>
<pre>export LD_LIBRARY_PATH=/root/gpio-driver/lib/
</pre>
Check that libgpio.so is linked correctly. Go to:$/gpio-driver/app, gpio program is here. Type next command:
<pre>ldd gpio
</pre>
ldd command, print shared library dependencies. The result will be similar at that:
<pre>root@localhost:~/gpio-driver/app# ldd gpio
libgpio.so => /root/gpio-driver/lib/libgpio.so (0x40197000)
libc.so.6 => /lib/libc.so.6 (0x401a0000)
/lib/ld-linux.so.3 (0x4008a000)
</pre>
The shared library is linked until system halt. Now you can execute gpio example program.
== Testing driver ==
To make sure than driver works well, make the next test. I used GPIO_136(sdmmc2_dat4) and GPIO_137(sdmmc2_dat5) because IGEP v2 RC5(without WIFI) don't use them by default: <br>
'''NOTE:''' For more information visit this [[Mux configuration|page]] (under construction). <br>
=== Configure Mux ===
Go to:/sys/kernel/debug/omap_mux, and change this mux configuration:
<pre>echo 0x104>sdmmc2_dat4
echo 0x104>sdmmc2_dat5
</pre>
Use cat command to check it:<br>
<pre>cat sdmmc2_dat4
cat sdmmc2_dat5
</pre>
The result will be similar at that:
<pre>root@localhost:/sys/kernel/debug/omap_mux# cat sdmmc2_dat4
name: sdmmc2_dat4.gpio_136 (0x48002164/0x134 = 0x0104), b ae4, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE4
signals: sdmmc2_dat4 | sdmmc2_dir_dat0 | NA | sdmmc3_dat0 | gpio_136 | NA | NA | safe_mode
</pre>
and
<pre>root@localhost:/sys/kernel/debug/omap_mux# cat sdmmc2_dat5
name: sdmmc2_dat5.gpio_137 (0x48002166/0x136 = 0x0104), b ah3, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE4
signals: sdmmc2_dat5 | sdmmc2_dir_dat1 | cam_global_reset | sdmmc3_dat1 | gpio_137 | hsusb3_tll_stp | mm3_rxdp | safe_mode
</pre>
Note: OMAP_PIN_INPUT=Input/Output pin and OMAP_PIN_OUTPUT=Output pin, for Read/Write test you need the first one. GPIO is configured in mode 4.<br>
=== Read/Write test ===
Link GPIO_136 and GPIO_137 with a wire, these pins are located in J990 connector with numbers 7 and 9. I use the next connector to join them:<br>
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Connector used readwrite test.JPG|center|350x230px]]
|
[[Image:All connected readwrite test.JPG|center|350x230px]]
|}
<br>
Now type next code:
<pre>root@localhost:~/gpio-driver/app# ./gpio input 136
root@localhost:~/gpio-driver/app# ./gpio output 137 0
root@localhost:~/gpio-driver/app# ./gpio get 136
0
root@localhost:~/gpio-driver/app# ./gpio output 137 1
root@localhost:~/gpio-driver/app# ./gpio get 136
1
root@localhost:~/gpio-driver/app#
</pre>
The results (CMOS Voltages: 0V-1V8):
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:GPIO value0 readwrite test.JPG|center|350x230px]]
|
[[Image:GPIO value1 readwrite test.JPG|center|350x230px]]
|}
<br> The code above shows that driver works properly, GPIO_136 is configured like input and GPIO_137 is configured like output with value 0, when read GPIO_136 the result is 0. To make sure that works well, configure GPIO_137 with value 1, now GPIO_136 reads 1. <br> This driver have more options like IRQ, but is not explained here.
<br> Other examples:[[What can I do with IGEP0020#How_to_handle_the_gpio-LED.27s]]
[[Category:GPIO]]
= How to use UARTs (update it)<br> =
== Overview ==
This How-To is meant to be a starting point for people to learn use UART for IGEPv2 devices as quickly and easily as possible. In this how-to, we use [http://releases.linaro.org/platform/linaro-m/headless/final/linaro-m-headless-tar-20101108-2.tar.gz Linaro Headless] with [[Linux Kernel 2.6.35.y|Kernel 2.6.35.y]] and [http://labs.isee.biz/images/e/ee/Uart-test-beta2.tar.bz2 UART test program]
More information about [http://en.wikipedia.org/wiki/UART UART].
'''Note''': This program has a debug option using GPIOs to debug via oscilloscope, this option is useful to learnt about the Kernel latencies. Debug has set to "write" and "select" functions.
[[Frequently Asked Questions and Their Answers#How_many_UARTs_are_available.3F|More information]]
== Feedback and Contributing ==
At any point, if you see a mistake you can contribute to this How-To.
== Preparing IGEP ==
=== Configure UART1 and UART3 in IGEP with RS232 levels on J960 connector ===
To test UARTs we use UART1 (dev/ttyS0) and UART3 (dev/ttyS2) via J960 connector using RS232 standard.
NOTE: Make sure that you installed open SSH server. If you don't have it go [[How to forge a local file system server with IGEP0020 board#Installing_Open_SSH_Server|here]].
By default, UART1 is used by RS485 driver, we need to disable it, edit igep.ini file: <br>
<pre>board.ei485= yes
</pre>
UART1 is configured in RS232 driver, when igep line is replaced by (or type in -Maybe you don't found this line-):<br>
<pre>board.ei485= no
</pre>
By default, UART3 is used by Kernel serial console, we need to disable it, go to igep.ini file, comment next line: <br>
<pre>console=ttyS2,115200n8</pre>
=== Check UARTs devices ===
Make sure that Kernel detects UARTs, type:
<pre>dmesg | grep tty</pre>
The result will be similar at that:
<pre>root@localhost:~/PROGRAM# dmesg | grep tty
[ 0.000000] console [tty0] enabled
[ 0.598999] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
[ 0.784057] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
[ 0.969085] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
[ 1.153503] serial8250.3: ttyS3 at MMIO 0x49042000 (irq = 80) is a ST16654
root@localhost:~/PROGRAM# </pre>
Get information about UARTs, type:
<pre>setserial -g /dev/ttyS[0123]</pre>
The result will be similar at that:
<pre>root@localhost:~/PROGRAM# setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16654, Port: 0x0000, IRQ: 72
/dev/ttyS1, UART: 16654, Port: 0x0000, IRQ: 73
/dev/ttyS2, UART: 16654, Port: 0x0000, IRQ: 74
/dev/ttyS3, UART: 16654, Port: 0x0000, IRQ: 80
root@localhost:~/PROGRAM# </pre>
If you don't have setserial installed type:
<pre>apt-get install setserial</pre>
NOTE: Starting from Kernel 2.6.37.y, ttySx are named ttyOx. You need to edit source program.
=== Connect peripherals ===
Connect IGEPv2 board using J960 connector like this:
J960
------
(Not used) x---| 1 2 |---o (Connect to 8)
(Connect to 9) o---| 3 4 |---x (Not used)
(GND)·|---| 5 6 |---|· (GND)
(Not used)x---| 7 8 |---o (Connect to 2)
(Connect to 3) o---| 9 10 |---x (Not used)
------
=== Send some data ===
Use minicom to prove it, open two terminals via SSH and log with root user:
Terminal 1:
<pre>minicom -D /dev/ttyS0</pre>
Terminal 2:
<pre>minicom -D /dev/ttyS2 </pre>
Type something in one terminal.
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| style="text-align: left;" | [[Image:Minicom screenshot.png|640x400px]]
|}
== Schematics ==
=== RS232 Schematic Igep V2 ===
{| align="center" cellspacing="1" cellpadding="1" border="1"
|-
| [[Image:RS232 Schematic Igep V2.png|800x531px]]
|}
<br>
=== Uart Schematic Igep Module ===
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart Schematic Igep Module.png|581x600px]]
|}
== Compile and run program ==
Download [http://labs.isee.biz/images/e/ee/Uart-test-beta2.tar.bz2 program source].
As explained above, the program uses GPIO for debug option via oscilloscope, it is necessary install user-gpio-drv.ko driver inside Linux Kernel, more information [[How to use GPIOs|here]] .
There are some interesting things to configure, before compiling the program. Open it, seek next lines:
<pre>//Define Array char size
#define SIZE 30
//Define Debug mode:0==Disable
#define DEBUG 0
//Define wait select
#define WAIT 5
//Set GPIO Debugger port
//Be sure that mux is correctly configured and GPIOs are not used
#define GPIO1 136
#define GPIO2 137 </pre>
Constant SIZE: it determines the max number of char than can be sent<br>
Constant DEBUG: it can break program infinite loop part, it can be useful to debug some errors, 0 (infinite loop) or positive number determine loop max entrances
Constant WAIT: it configurea select max time.
Constants GPIO1 and GPIO2: they configure GPIOs used for debug via oscilloscope. Take care to configure mux and don't use them for other purposes<br>
Once you have installed module. Compile program using your Cross Compiler, I used arm-linux-gnueabi-:
<pre>arm-linux-gnueabi-gcc uart-test-beta1.c -o uart-test-beta1 </pre>
== Testing UART ==
Some tests do it:
=== Decode Characters ===
Decoded with [http://www.asciitable.com/ ASCII table].
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart decode1withlf.JPG|350x230px]]
| [[Image:Uart decode0withlf.JPG|350x230px]]
| [[Image:Uart decode100000withlf.JPG|350x230px]]
|-
| Decoding "1\n"
| Decoding "0\n"
| Decoding "100000\n"
|}
Click to enlarge image
=== select timeout ===
Program sends information via UART1 but don't receive response via UART3, because only a process is executed. This problem is repeated every 5 seconds (constant WAIT=5) until other process sends information via UART3 at the same speed. If "select" hasn't been implemented, process would have stayed blocked.<br>
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart select timeout9.JPG|350x230px]]
|-
| UART1=Blue and UART3=Green
|}
Click to enlarge image
=== RS232 Voltage params ===
More information [http://en.wikipedia.org/wiki/RS-232#Standard_details here].
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart voltageparams8.JPG|350x230px]]
|-
| Vpp=11.8V aprox , Vmin=-5.6V aprox
|}
Click to enlarge image
=== Speed Overview ===
Note that wave is degraded when speed is higher
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart 300 o.JPG|260x172px]]
| [[Image:Uart 4800 o.JPG|260x172px]]
| [[Image:Uart 115200 o.JPG|260x172px]]
| [[Image:Uart 3000000 o.JPG|260x172px]]
|-
| Overview signal to 300 bauds
| Overview signal to 4800 bauds
| Overview signal to 115200 bauds
| Overview signal to 3000000 bauds
|-
| [[Image:Uart 300 s.JPG|260x172px]]
| [[Image:Uart 4800 s.JPG|260x172px]]
| [[Image:Uart 115200 s.JPG|260x172px]]
| [[Image:Uart 3000000 s.JPG|260x172px]]
|-
| Specific wave to 300 bauds
| Specific wave to 4800 bauds
| Specific wave to 115200 bauds<br>
| Specific wave to 3000000 bauds<br>
|}
Click to enlarge image
=== Lag ===
You can see that RS232 have some lag between transmisions. This caused mainly by kernel process management. UART peripheral is controlled by Linux and It isn't a [http://en.wikipedia.org/wiki/Real-time_operating_system real-time operating system].
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart lag left6.JPG|350x230px]]
| [[Image:Uart lag right7.JPG|350x230px]]select: blocked until all data is available.
|-
| Lag between UART1 and UART3 (300 bauds)
| Lag between UART3 and UART1 (300 bauds)
|}
Click to enlarge image
This program have three I/O functions that connect to UART driver via ioctl: (read(), write() and select()). But select() and write() change process stat to sleep mode until system don't receive or transmit all information via UART. "select" function is used to prevent that read function can be blocked when data aren't available. <br>The next images (program with debug_gpio enabled and 300 bauds speed) show when process is executed or is waiting. Blue=UART1, Violet="write" and Green="select". When GPIO has HIGH value, process is blocked.<br>
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart select5.JPG|260x172px]]
| [[Image:Uart select to write1.JPG|260x172px]]
| [[Image:Uart write2.JPG|260x172px]]
| [[Image:Uart write to select0.JPG|260x172px]]
|-
| select function time
| Time between select and write
| write function time
| Time between write and select
|}
Click to enlarge image<br>
In this case:
select: blocked until all data is available (LF char received).
write: blocked until all data is send to UART buffer.
=== Error test ===
Every full process the number is increased twice. Program checks that this condicion is true, if it isn't accomplished, process will be finish.
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
|-
| [[Image:Uart error test2.png|640x400px]]
|-
| Runs 16h without any transfer error (3000000 bauds)<br>
|}
<br>
= Getting started with IGEPv2 Expansion<br> =
{{Table/IGEP Technology Devices
|Tech_Family={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_Family}}
|Tech_ID={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_ID}}
|Name={{#lst:Template:Links|IGEPv2_EXPANSION_Name}}
|Image={{#lst:Template:Links|IGEPv2_EXPANSION_Image}}
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_MainPage}}
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_Hardware}}
}}
<br> __TOC__
= Overview =
This is the 1/3 chapter of IGEPv2 Expansion Tutorial Guide.
In this first chapter, we will learn how to connect some expansion peripherals.
= Requirements =
In these tutorials we are going to need the following components :
*[http://www.isee.biz/products/processor-boards/igepv2-board IGEPv2], [http://shop.isee.biz/buy-online/accesories/power-supply-2600ma-ac-6w.html +5V DC power supply], Ethernet cable and a PC with Linux or Windows.<br>
*Powertrip 4.3" or [http://shop.isee.biz/buy-online/accesories/tft-24-bits-seiko-7.html Seiko 7"] screen if you need a touch screen.
*DB9 connector and USB serial converter to follow serial communication tutorial<br>
*4 pin connector for CAN Bus with another IGEPv2 and Expansion to follow CAN Bus communication tutorial<br>
*SIM card with an antenna to follow Telit modem tutorial<br>
*Composite video cable, composite video output peripheral (PAL or NTSC) and a screen to follow TVP5151 tutorial<br>
= Getting started =
== Connect IGEPv2 Expansion with IGEPv2 Board ==
'''Basic'''
The IGEPv2 Expansion connects to the IGEPv2 Board through J990, JA41, JA42, JC30 and J960 connectors. Some IGEPv2 Expansion may include three jumpers, you should remove it because they are designed for test and lab purposes. Just take a look on the figure below to mount it:<br>
{| cellspacing="1" cellpadding="1" width="200" border="1" align="center"
|-
| [[Image:Igepv2expconnectoigepv2.PNG|268px]]<br>
| [[Image:Igepv2expconnectoigepv2 2.PNG|268px]]<br>
|}
== TFT and Touchscreen ==
'''Basic'''
[[Image:IGEP0022 PROTO RA DSC 0142.JPG|right|200px]] IGEPv2 Expansion integrates a LCD backlight driver (Texas instruments TPS61081) and touch screen controller (Texas instruments TSC2046), 4-wire touch screen controller which supports a low-voltage I/O interface which can be directly connected to a SEIKO 7” LCD or to a POWERTIP 4.3” LCD. Use J301 connector for POWERTRIP 4.3" or use J302, J303 and J304 connector for SEIKO 7".<br>
'''Know more'''<br>
IGEPv2 Expansion integrates LCD backlight driver (TPS61081) and touch screen controller (TSC2046), a 4-wire touch screen controller which supports a low voltage I/O interface from 1.5V to 5.25V.
== Serial port ==
'''Basic''' [[Image:Igepv2expdb9connector.PNG|right|200px]]
IGEPv2 Expansion integrates a DB9 RS232 connector. Plug a DB9 cable. <br>
'''Know more'''
This peripheral (UART 3) can be used to debug system using kernel traces, getting a remote prompt, etc. <br> <br> <br>
== VGA monitor ==
'''Basic'''
{| cellspacing="1" cellpadding="1" width="363" border="1" align="right"
|-
| [[Image:Igepv2expconnecttovga.jpg|150px]]
| [[Image:Igepv2expvgaconnector.PNG|200px]]
|}
IGEPv2 Expansion integrates a VGA connector, the output VGA signal is equal to HDMI connector. Plug a monitor with VGA input.
'''Know more'''
This output is controled by ADV7125KSTZ140 Integrated Circuit.
<br> <br> <br>
== CAN bus ==
'''Basic'''
[[Image:Igepv2expcanconnector.PNG|right|200px]]IGEPv2 Expansion integrates a CAN peripheral. Connect any CAN bus device or network to the CAN bus connector (J703).<br>
'''Know more'''
This output is controled by MICROCHIP MCP2515. J703 is a 3.5 mm pitch terminal blocks 4 Positions:
{| cellspacing="1" cellpadding="1" width="350" border="1"
|-
| Signal Name
| Pin #<br>
| Description
|-
| VDD_CAN
| J703:1
| Supply Voltage (+5V DC)
|-
| CANL
| J703:2
| CAN Low-Level Voltage I/O
|-
| GND
| J703:3
| Ground
|-
| CANH
| J703:4
| CAN High-Level Voltage I/O
|}
== GSM/GPRS modem ==
'''Basic'''
{| cellspacing="1" cellpadding="1" width="200" border="1" align="right"
|-
| [[Image:IGEP0022 Modem with antenna.png|200px]]
| [[Image:Igepv2expcardreader.PNG|right|200px]]
|-
| GSM-GPRS antenna (highly recommended)
| SIM card reader
|}
IGEPv2 Expansion integrates a GSM/GPRS modem to make phone calls or to send SMS or to write and read data from it, etc.<br>
'''Know more''' Modem chip Telit GE865 is a small GSM/GPRS Ball-Grid-Array BGA module with next main features:
*Quad-band EGSM 850 / 900 / 1800 / 1900 MHz
*Power consumption (typical values)
- Power off: ‹ 62 uA<br> - Idle (registered, power saving): 1.6 mA @ DRX=9 <br> <br> <br>
== Composite Video Decoder ==
'''Basic'''
[[Image:Igepv2expvideocompositeconnector.PNG|right|200px]]IGEPv2 Expansion integrates two composite video connectors to decode analog input signal. Plug some peripheral with video composite output.<br>
'''Know more'''
Analog input is decoded by TVP5151.
<br> {{Navigation/IGEP Technology Guides/Getting Started/Ending
|Next_Step={{#lst:Template:Links|IGEPv2_EXPANSION_Community_Guides_2}}
}}
{{Table/IGEP Technology Devices
|Tech_Family={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_Family}}
|Tech_ID={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_ID}}
|Name={{#lst:Template:Links|IGEPv2_EXPANSION_Name}}
|Image={{#lst:Template:Links|IGEPv2_EXPANSION_Image}}
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_MainPage}}
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_Hardware}}
}}
<br>
= What can i do with igepv2 expansion =
{{Table/IGEP Technology Devices
|Tech_Family={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_Family}}
|Tech_ID={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_ID}}
|Name={{#lst:Template:Links|IGEPv2_EXPANSION_Name}}
|Image={{#lst:Template:Links|IGEPv2_EXPANSION_Image}}
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_MainPage}}
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_Hardware}}
}}
<br> __TOC__
<br>
= Overview =
This is the 2/3 chapter of IGEPv2 Expansion Tutorial Guide.
We will learn some basic tasks such add support to IGEPv2 Expansion, control some peripherals, etc.<br>
= What can I do<br> =
== How to use Serial communication (DB9 connector) ==
'''Basic'''
RS232 link for UART 3 (/dev/ttyO2) can be obtained through J502 DB9 connector. You can use PuTTy to get a shell prompt to IGEP:
*Power up IGEPv2
*Open PuTTy.
*Choose Serial line. If you are running PuTTy on Windows, the Serial line will be like (COM1 or COM2 or COM3, etc.). If you are running PuTTy on Ubuntu, the Serial line will be like (/dev/ttyS0 or /dev/ttyS1 or /dev/ttyS3, etc.). Note that if you are using a USB->Serial converter, the Serial line will be like /dev/ttyUSB0
*Configure Speed to 115200
*Select Serial Connection type
*Press on Open button
*You will successfully started the console.
<br>
{| cellspacing="1" cellpadding="1" width="200" border="1"
|-
| [[Image:IGEPV2EXPCHMDB9.png|250px]]
| [[Image:Remoteshellpromptdb9putty.jpg|250px]]
|}
'''Know more'''
[[How to use UARTs|Read this tutorial]] to learn about UARTs.
== How to use TFT and Touchscreen ==
Seiko a Powertip touch screens are not supported by default in IGEPv2. Use the following steps for it:
*Log into IGEPv2 (via SSH, [http://labs.isee.biz/index.php/Getting_started_with_IGEPv2#Log_into_IGEPv2_via_Ethernet_interface as shown in the previous chapter]), and run the following commands:
<pre>ssh root@192.168.5.1
mkdir /tmp/temp
mount -t jffs2 /dev/mtdblock1 /tmp/temp
vi /tmp/temp/igep.ini </pre>
*In Seiko screen add the following line:
<pre>omapdss.def_disp=lcd-70</pre>
*In Powertip screen add the following line:
<pre>omapdss.def_disp=lcd-43</pre>
*Save changes and reboot your IGEP Device to finish it.<br>
== How to use Telit Modem ==
'''Basic'''
Telit modem is not supported by default in IGEPv2. Use the following steps for it:
*Log into IGEPv2 (via SSH, [http://labs.isee.biz/index.php/Getting_started_with_IGEPv2#Log_into_IGEPv2_via_Ethernet_interface as shown in the previous chapter]), and run the following commands:
<pre>ssh root@192.168.5.1
mkdir /tmp/temp
mount -t jffs2 /dev/mtdblock1 /tmp/temp
vi /tmp/temp/igep.ini </pre>
*Add the following line (press i to insert content):
buddy.modem=yes
*Save changes (ESC -> :wq -> Enter) and reboot your IGEP Device
*Power up the modem. You can power off using again these commands:
<pre>echo 0 > /sys/class/gpio/gpio140/value
echo 1 > /sys/class/gpio/gpio141/value
sleep 1
echo 0 > /sys/class/gpio/gpio141/value
</pre>
*Once the modem is on (led D401, near SIM card reader, is blinking now), you can interact with it via UART 2. You can use Microcom to comunicate with it from the serial debug console:
<pre>microcom -s 115200 /dev/ttyO1</pre>
*To check the modem status use the command:<br>
<pre>at</pre>
*Answer should be OK.<br>
*Now unlock it by inserting your SIM card PIN number. Use the command:
<pre>at+cpin=<PIN></pre>
*If you correctly inserted the PIN number, the answer should be OK. If you fail more than 3 times, your SIM card will lock and you will have to insert PUK number.
*Now you are ready to use the GSM/GPS modem.<br>
=== Examples ===
If you successfully '''followed the the previous instructions''', you are ready to test the GSM/GPRS modem. Here are some examples:
You can check the complete list of AT commands at the Official manufacturer [http://telit.com/module/infopool/download.php?id=522 Software User Guide].
==== Test received signal strength<br> ====
Use the instruction:
<pre>at+csq</pre>
The answer should be: +CSQ: X,0, where X is the signal strenght. For example 12 is poor and 18 is good. If the answer is +CSQ:99,99 you should check your coverage or use an antenna<br>
==== Making a phone call<br> ====
Use the instruction, replace number_to_call with your number:
<pre>atd number_to_call
</pre>
Press any key to end call
'''NOTE:''' If "NO CARRIER" message appears, check your coverage or use an antenna.
==== Sending a SMS<br> ====
First of all, you need to configure the SMS format type. Telit GE865 GSM/GPRS supports PDU format and Text format. We use Text format. Type the following command:
<pre>AT+CMGF=1</pre>
There are so many ways in this modem to send a message. Here you have a simple example. Use the instruction, replace destination_number with your number:
<pre>at+cmgs= destination_number
> insert here your text message
</pre>
When you are ready to send your message use Ctrl+Z to send it.
If you want to cancel or restart the message press ESC.<br>
'''NOTE:''' If "NO CARRIER" message appears, check your coverage or use an antenna.
'''NOTE:''' Don't use special characters in SMS text message like <`´'">.<br>
'''Know more'''<br>
Here you have the official manuals from the manufacturer's webpage:<br>
*[http://telit.com/module/infopool/download.php?id=1666 Telit GE865-QUAD Hardware User Guide]<br>
*[http://telit.com/module/infopool/download.php?id=522 Telit Modules Software User Guide]<br>
== How to use TVP5151 Video Decoder <br> ==
'''Basic'''
Use the following steps to capture analog video:
*Connect a video composite input to J501 connector from IGEPv2 Expansion (near CAN Bus)
*Connect a screen, for example HDMI monitor.
*Log into IGEPv2 (via SSH, [http://labs.isee.biz/index.php/Getting_started_with_IGEPv2#Log_into_IGEPv2_via_Ethernet_interface as shown in the previous chapter]), and run the following commands:
<pre>ssh root@192.168.5.1
</pre>
*Now you have a remote igep terminal<br>
*Refresh repositories and accept it.
<pre>zypper ref </pre>
*Install video4linux2 plugin
<pre>zypper in gst-plugins-good-video4linux2
</pre>
*Load OMAP ISP kernel module<br>
<pre>modprobe omap3-isp
</pre>
*Configure ISP, for PAL resulution use 720x576 for NTSC resolution use 720x480:<br>
<pre>media-ctl -r -l '"tvp5150 2-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
media-ctl -v --set-format '"tvp5150 2-005c":0 [UYVY 720x480]'
media-ctl -v --set-format '"OMAP3 ISP CCDC":0 [UYVY 720x480]'
media-ctl -v --set-format '"OMAP3 ISP CCDC":1 [UYVY 720x480]' </pre>
*Export display
<pre>export DISPLAY=:0.0 </pre>
*Launch gstreamer
<pre>gst-launch-0.10 -v v4l2src device=/dev/video2 queue-size=8 ! video/x-raw-yuv,format=\(fourcc\)UYVY,width=720,height=480 ! ffmpegcolorspace ! autovideosink</pre>
*Now you can see in your IGEP screen a result similar like this
{| cellspacing="1" cellpadding="1" width="200" border="1"
|-
| [[Image:Igepv2expgstreamercapture.jpg|400px]]
|}
<br>
'''Know more'''<br>
You can use other programs like [[How to setup tvp5151 video decoder|yavta]]<br>
== How to use EEPROM ==
'''Basic'''
The IGEP0022 expansion board provides an AT24C01B serial EEPROM memory which is connected to the OMAP via I2C (register 50).<br>
Use i2c-tools to manage it:
<pre>i2cget <bus> <chip> <register>
i2cset <bus> <chip> <register> <value></pre>
For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2:
<pre>i2cset -f -y 2 0x50 0x10 0x22
i2cget -f -y 2 0x50 0x10</pre>
'''Know more'''
See also: i2dump(8), i2cget(8) and i2cset(8) man page
== How to use CAN bus (under construction) ==
{{#lst:How to use CAN bus|IGEPv2 EXPANSION}} {{Template:Navigation/IGEP Technology Guides/What can I do/Ending}} {{Table/IGEP Technology Devices
|Tech_Family={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_Family}}
|Tech_ID={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_ID}}
|Name={{#lst:Template:Links|IGEPv2_EXPANSION_Name}}
|Image={{#lst:Template:Links|IGEPv2_EXPANSION_Image}}
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_MainPage}}
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_Hardware}}
}}
[[Category:UART]] [[Category:IGEP_Technology_Devices_Guides]]
→DM3730: Decode an AAC audio file (OK)
= TODO: =
gst-launch --gst-debug-level=2 filesrc location= Overview sampleaache.m4a ! TIAuddec1 codecName=aachedec engineName=codecServer ! volume volume=0.25 ! alsasink sync==false
''(from [[How to create a SD-card with the latest software image]])'Random fatal bit error''' {{:How to create a SD-card with the latest software image}}
gst-launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume= Connect to IGEP ==0.25 ! alsasink
= igep.ini parameters =
=== [kernel] ===
{| align="JUSTIFY" cellpadding="1" border="1" align="JUSTIFY" style="width: 900px; height: 240px;"
|-
| '''Parameter Name'''
| Ram Disk location address
| =0x81600000
| Hex memory address;<br>disabled by default
|-
| serial.low
| MachineID
| Machine ID (kernel ID)
|;IGEPv2<br>=2344 |;Module<br>=2717<br>;Proton<br>=3203
|-
| Mode
| Boot Mode
|;Linux kernel<br>=kernel |;Other image (like uboot)<br>[binary image]
|}
| buddy
| Enable/disable expansion board support
| ;IGEPv2 Expansion Board support<br>=igep0022 | ;Berlin and Paris Expansion Board support<br>=base0010<br>New York Expansion<br>=ilms0015
|-
| console
| Configure frame bugger configuration
| =dvi:hd720-16@50
| ;Other configuration<br>=dvi:1280x720MR-16@60
|-
| vram
| root
| Configure root directory for MMC, NFS or UBI
| ;For mmc memory<br>=/dev/mmcblk0p2 rw rootwait | ;For flash memory<br>=/dev/mtdblock2
|-
| nfsroot
| board.ei485
| Enable/disable RS485
| ;Enable RS485<br>=yes | ;Disable RS485<br>=no
|-
| board.modem
| Enable/disable GPRS modem
| ;Enable modem (IGEPv2 Expansion)<br>=no | ;Enable modem (IGEPv2 Expansion)<br>=yes
|-
| buddy.revision
| Only for base0010<br>=B
|}