Difference between revisions of "User:Pau pajuelo"

From IGEP - ISEE Wiki

Jump to: navigation, search
m
m (DM3730: Decode an AAC audio file (OK))
 
(932 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= TODO:  =
 
= TODO:  =
  
Update peripheral tutorials  
+
Categorize new tutorials
  
Categorize new tutorials
+
How to manage the kernel modules on Linux
  
Upgrade ethernet gadget tutorial for new IGEP firmware and VM
+
How do I edit my kernel command line
  
Finish tutorials below
+
== AUDIO DSP-ARM==
  
NOTES: Qt, Codeblocks and Eclipse are linked to main page:  
+
===Included (IGEP GST DSP):===
 +
'''AACHEDEC -> DEC AACHE (OK)'''
  
Eclipse -> How to develop under Eclipse (copy manual) (refers at beginning VM and option to install Eclipse(under construction))
+
http://download.wavetlan.com/SVV/Media/HTTP/FAAC-HE-AAC.aac
  
Qt -> How to develop under Qt (refers at begginin VM and option to install Qt (under construction))
+
gst-launch --gst-debug-level=2 filesrc location=sampleaache.m4a ! TIAuddec1 codecName=aachedec engineName=codecServer ! volume volume=0.25 ! alsasink  sync=false
  
Codeblocks (do it)
+
outofthebox->ok
  
Upgrade ethernet gadget how to
+
----
  
<br>  
+
'''MP3DEC -> DEC MP3 (AUDIO ERRORS)'''
  
Adapt IGEPv2 to IGEPv2 Expansion
+
- Followed README file from ISEE - IGEP DSP - GST + DMAI Support Package 3.40.00
  
= How to use SPI (prove with new firmware, under construction)  =
+
http://www.stephaniequinn.com/Music/Canon.mp3
  
== Overview ==
+
gst-launch --gst-debug-level=2 filesrc location=Canon.mp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0.25 ! alsasink sync=false
  
This How-To is meant to be a starting point for people to learn use SPI for IGEP devices as quickly and easily as possible. In this how-to, we run an example program that reads and writes registers from 3-axis accelerometer ([http://www.st.com/internet/analog/product/250725.jsp LIS3DH]) included on the board IGEP New York. <br>
+
'''Random fatal bit error'''
  
== Requirements  ==
+
'''mp3-plugin doesn't resolve the error'''
  
There are some requisites to follow this guide:
+
----
  
*[http://isee.biz/component/zoo/item/igep-virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEP&nbsp;SDK&nbsp;SOFTWARE&nbsp;USER&nbsp;MANUAL (chapter 2.3 "Setting up and running the VM")<br>  
+
'''G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)'''
*[http://isee.biz/component/zoo/item/igep-firmware-yocto-1-2 IGEP Firmware]: follow the IGEP&nbsp;SDK SOFTWARE&nbsp;USER&nbsp;MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card")  
 
*[http://isee.biz/products/processor-boards/igep-com-module IGEP&nbsp;COM&nbsp;MODULE] and [http://isee.biz/products/expansion-boards/product-igep-new-york IGEP NEW&nbsp;YORK]<br>
 
*SPI example program '''(link program)'''  
 
*MicroSD Card (at least 2Gbytes)
 
  
== How Works  ==
+
'''G711ENC -> ENC PCM uLAW (speech) (NOT TESTED)'''
  
'''LIS3DH accelerometer:''' It is the accelerometer mounted in IGEP New York.
+
===Not included  (IGEP GST DSP):===
 +
'''ACCLCDEC -> DEC AACLE (NOT TESTED)'''
  
'''Omap3 SPI Peripheral:''' It is the hardware used to communicated with accelerometer and other SPI devices.
+
'''AACLDDEC -> DEC AACLD (NOT TESTED)'''
  
'''Omap2_mcspi:''' It is a bus driver than controls Omap3 SPI Peripheral.
+
'''WMA9 -> DEC WMA9 (COMPILING ISSUES)'''
  
'''Spi:''' It is a protocol driver that defines functions and strucs used in SPI bus.
+
'''ACCLCENC -> ENC AACLE (NOT TESTED)'''
  
'''Spidev:''' It is a device driver that export spi driver functionalities to userspace.
+
'''ACCHEENC -> ENC AACHE (NOT TESTED)'''
  
'''Lis3lv02d_spi:''' SPI glue layer for lis3lv02d
+
'''AACLDENC -> ENC AACLD (NOT TESTED)'''
  
'''Lis31v02d:''' Device driver for LIS3DH accelerometer.
+
'''WMA8 -> ENC WMA8 (NOT TESTED)'''
  
'''Exp_ilms0015:''' It is a startup program for IGEP New York. It attach lis31v02d with Spi driver.
+
'''Problems adding codecs into igep-gst-dsp'''
  
{| cellspacing="1" cellpadding="1" border="1" width="200"
+
== DM3730==
|-
 
| [[Image:Spi linux schematic.png|501x600px]]
 
|}
 
  
<br> More information about Linux Kernel SPI at:  
+
=== DM3730: Decode a MP3 file (OK) (ADDED TO REPOSISTORIES)===
  
*[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spi-summary;h=4884cb33845d7629987f60610eeedb863561006e;hb=refs/heads/linux-2.6.37.y SPI Overview]
+
'''under contruction'''
  
*[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev;h=ed2da5e5b28a4490a3b03787b02df66d083692be;hb=refs/heads/linux-2.6.37.y SPIDEV]
+
'''does not have an accelerated audio decoder element'''
  
== Prepare Micro SD Card  ==
+
- Compiled gst-plugins-ugly using yocto tools
  
=== Generate Micro SD Card (correct)  ===
+
- rpm -igst-plugins-ugly-0.*.rpm
  
Open a terminal and use the following steps to download and generate a Micro SD card.
+
- rpm -i libmad0-0.*.rpm
<pre>wget http://downloads.isee.biz/denzil/binary/igep_firmware-yocto-1.2.1-1.tar.bz2
 
tar jxf igep_firmware-yocto-*.tar.bz2
 
cd igep_firmware-yocto-* </pre>
 
Insert a SD-Card media and use the igep-media-create script to copy the firmware.  
 
  
./igep-media-create -–mmc &lt;mmc&gt; --image demo-image-sato-igep00x0.tar.bz2&nbsp;--machine igep0030
+
- rpm -i gst-plugins-ugly-mad-0.*.rpm
  
where &lt;mmc&gt; - is the SD-Card device of your computer. For example, assuming the SD-card device takes '/dev/sdb' type:
+
- gst-launch filesrc location=sample.mp3 ! mad ! volume volume=0.25 ! alsasink
<pre>./igep-media-create --mmc /dev/sdb --machine igep0030 --image demo-image-sato-igep00x0.tar.bz2 </pre>
 
This should give you a bootable SD-card with IGEP&nbsp;COM&nbsp;MODULE support.
 
  
=== Custom Micro SD Card  ===
+
=== DM3730: Decode a RA or RM audio file (ERRORS)===
  
==== Get Linux kernel sources  ====
+
gst-launch --gst-debug-level=3 filesrc location=sample.ra ! rmdemux ! volume volume=0.25 ! alsasink
  
We will get from git repository the kernel sources:  
+
http://www.superluminal.com/andalib/ra/listen.ra
  
*Clone the Kernel git repository
+
gst-plugins-ugly-rmdemux-0.10.19-r1.armv7a.rpm
<pre>git clone git://git.igep.es/pub/scm/linux-omap-2.6.git
 
$/home/jdoe&gt; cd linux-omap-2.6</pre>
 
*Checkout your desired branch (we used for this howto 2.6.37.y)
 
<pre>git checkout origin/linux-2.6.37.y -b linux-2-6-37.y</pre>
 
  
==== Modify Linux Kernel Sources to attach Spidev to SPI&nbsp;driver  ====
+
libgstsdp-0.10-0-0.10.36-r3.armv7a.rpm:
 +
libgstsdp-0.10-0
 +
libgstsdp-0.10.so.0
  
To read accelerometer registers from spidev, we need to attach spidev driver to spi driver at start up. So it is necessary to modify spi_board.  
+
libgstrtsp-0.10-0-0.10.36-r3.armv7a.rpm:
 +
libgstrtsp-0.10-0
 +
libgstrtsp-0.10.so.0
  
Go to $(Kernel path)/arch/arm/mach-omap2/exp-ilms0015.c and edit the next fields in bold words.
+
'''Error:'''
  
{| cellspacing="1" cellpadding="1" border="1" width="500"
+
0:00:00.084839071  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
|-
 
|
 
static struct spi_board_info lis3lv02d_spi_board_info __initdata = {
 
  
&nbsp;&nbsp;&nbsp;&nbsp;'''.modalias = "spidev",'''
+
0:00:00.085052695  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
  
&nbsp;&nbsp;&nbsp; '''//.modalias&nbsp;&nbsp;&nbsp; = "lis3lv02d_spi",'''
+
0:00:00.085540976  1550  0xa137b0 WARN                rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id .ra4
  
&nbsp;&nbsp;&nbsp; .bus_num&nbsp;&nbsp;&nbsp; = -EINVAL,  
+
0:00:00.085693564  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
  
&nbsp;&nbsp;&nbsp; .chip_select&nbsp;&nbsp;&nbsp; = -EINVAL,  
+
0:00:00.085815634  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
  
&nbsp;&nbsp;&nbsp; .max_speed_hz&nbsp;&nbsp;&nbsp; = 1*1000*1000,
+
0:00:00.085907187  1550  0xa137b0 WARN                rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id RaTC
  
&nbsp;&nbsp;&nbsp; .irq&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; = -EINVAL,
+
=== DM3730: Decode an AAC audio file (OK)===
  
&nbsp;&nbsp;&nbsp; .mode&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; = SPI_MODE_0,  
+
EXTRA_OECONF += "--disable-examples --disable-experimental --disable-sdl --disable-cdaudio --disable-directfb \
 +
                --with-plugins=musicbrainz,wavpack,ivorbis,mpegvideoparse,'''faad2''' --disable-vdpau --disable-apexsink \
 +
                --disable-orc"
 +
Install:
  
&nbsp;&nbsp;&nbsp;'''//.platform_data&nbsp;&nbsp;&nbsp; = &amp;lis3lv02d_pdata,'''
 
  
};
+
faad2-2.7-r2.armv7a.rpm
 +
libfaad2-2.7-r2.armv7a.rpm
 +
gst-plugins-bad-faad-0.10.23-r2.armv7a.rpm
  
inline void __init ilms0015_lis3lv02d_init(int bus_num, int cs, int irq)
+
'''maybe there are necessary more packages, compare actual gst-bad-recipe and add changes. Necessary add faad2 recipe'''
 +
<pre>bitbake faad2 gst-plugins-bad</pre>
 +
<pre> rpm -i faad2-2.7-r2.armv7a.rpm
 +
rpm -i libfaad2-2.7-r2.armv7a.rpm
 +
rpm -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
  
&nbsp;&nbsp;&nbsp; struct spi_board_info *spi = &amp;lis3lv02d_spi_board_info;
+
==== DM3730: Decode an WMA audio file (OK)====
  
&nbsp;&nbsp;&nbsp; if ((gpio_request(irq, "LIS3LV02D IRQ") == 0)
+
<pre>bitbake gst-ffmpeg</pre>
  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &amp;&amp; (gpio_direction_input(irq) == 0))
+
<pre>gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink  </pre>
  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; gpio_export(irq, 0);
+
=== DM3730: Decode an OGG audio file (OK)===
  
&nbsp;&nbsp;&nbsp; else {
+
'''Into repositories (base plugins):'''
  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pr_err("IGEP: Could not obtain gpio LIS3LV02D IRQ\n");
+
http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return;
+
gst-launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume=0.25 ! alsasink
  
&nbsp;&nbsp;&nbsp; }
+
== BASE0033 CONNECTOR SUMMARY TABLE==
  
&nbsp;&nbsp;&nbsp; spi-&gt;bus_num = bus_num;
+
== Configure a static IP using the same private network range ==
  
&nbsp;&nbsp;&nbsp; spi-&gt;chip_select = cs;
+
'''under construction'''
  
&nbsp;&nbsp;&nbsp; spi-&gt;irq = OMAP_GPIO_IRQ(irq),
+
IGEP Firmware Yocto uses the following Ethernet network configuration (IP addresses)
  
&nbsp;&nbsp;&nbsp; spi_register_board_info(&amp;lis3lv02d_spi_board_info, 1);
+
*eth0 − 192.168.5.1
 +
*eth0:0 − assigned via dhcp.
  
}
+
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.
  
...
+
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
  
void __init ilms0015_init(void)  
+
(Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration)
  
{
+
= igep.ini parameters  =
  
&nbsp;&nbsp;&nbsp; mux_partition = omap_mux_get("core");
+
The kernel command line syntax is name=value1. These next parameters are supported in igep.ini since IGEP-X_Loader 2.4.0-2:
  
&nbsp;&nbsp;&nbsp; /* Mux initialitzation for ilms0015 */
+
=== [kernel]  ===
  
&nbsp;&nbsp;&nbsp; omap_mux_write_array(mux_partition, ilms0015_mux);  
+
{| align="JUSTIFY" cellpadding="1" border="1" style="width: 900px; height: 240px;"
 
+
|-
&nbsp;&nbsp;&nbsp; /* 3-axis accelerometer */
+
| '''Parameter Name'''
 
+
| '''Description'''
&nbsp;&nbsp;&nbsp; ilms0015_lis3lv02d_init(1, 2, 174);
+
| '''Default value'''
 
+
| '''Comments'''
&nbsp;&nbsp;&nbsp; /* Export some GPIO */
+
|-
 
+
| kaddress
&nbsp;&nbsp;&nbsp; ilms0015_gpio_init();
+
| Kernel copy address
 
+
| =0x80008000
}
+
| Hex memory address
 
+
|-
|}
+
| rdaddress
 
+
| Ram Disk location address
Now spi_register_board_info has all information necessary to attach spidev driver instead lis3lv02d_spi.
+
| =0x81600000
 
+
| Hex memory address;<br>disabled by default
==== Compile Kernel  ====
+
|-
 
+
| serial.low
Export IGEP SDK sources:
+
| Serial number (low part)
<pre>source /opt/poky/1.2/environment-setup-armv7a-vfp-neon-poky-linux-gnueabi</pre>
+
| =00000001
*Configure the kernel
+
| Numeric
<pre>cd linux-omap-2.6
+
|-
make ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- igep00x0_defconfig</pre>
+
| serial.high
*Build the kernel and Modules
+
| Serial number (high part)
<pre>make ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- zImage modules</pre>
+
| =00000000
'''Note: '''The kernel binary resides inside the directory:$(Kernel path)/arch/arm/boot/'''zImage''' <br>
+
| Numeric
 
+
|-
==== Enable ilms0015 support  ====
+
| revision
 
+
| Revision ID
“ilms0015” is the technical name of IGEP New York.
+
| =0003
 
+
| Numeric
By default, poky-media-create (See: [http://labs.isee.biz/index.php/How_to_create_a_SD-card_with_the_latest_software_image Poky firmware with Kernel 2.6.37.y]) configured as igep0030, gives support only for IGEP Expansions Paris and Berlin. We need to configure igep.ini and gives support to IGEP New York:
+
|-
 
+
| kImageName
{| cellspacing="1" cellpadding="1" border="1" width="500"
+
| Kernel, binary image name
 +
| =zImage
 +
| Kernel or binary image name
 +
|-
 +
| kRdImageName
 +
| Kernel RAM Disk Image Name
 +
| -
 +
| Ram Disk image name
 
|-
 
|-
| &nbsp;; Machine configuration
+
| MachineID
'''&nbsp;&nbsp;&nbsp;&nbsp;;buddy=base0010 buddy.revision=B '''
+
| Machine ID (kernel ID)
 
+
| ;IGEPv2<br>=2344
'''&nbsp;&nbsp;&nbsp; buddy=ilms0015'''
+
| ;Module<br>=2717<br>;Proton<br>=3203
 
 
|}
 
 
 
==== Test changes  ====
 
 
 
Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changes:
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="500"
 
 
|-
 
|-
|  
+
| Mode
root@igep00x0:/dev# lsmod
+
| Boot Mode
 
+
| ;Linux kernel<br>=kernel
Module&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size&nbsp;&nbsp;&nbsp; Used by
+
| ;Other image (like uboot)<br>[binary image]
 
 
rfcomm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 48522&nbsp;&nbsp; 0
 
 
 
hidp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 13311 &nbsp; 0
 
 
 
l2cap&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; 49001&nbsp;&nbsp; 4 rfcomm,hidp
 
 
 
bluetooth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 67643&nbsp;&nbsp; 3 rfcomm,hidp,l2cap
 
 
 
libertas_sdio&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; 13887 &nbsp; 0
 
 
 
libertas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 99318 &nbsp; 1 libertas_sdio
 
 
 
option&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 13044 &nbsp; 0
 
 
 
usb_wwan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7196 &nbsp; 1 option
 
 
 
usbserial&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 23870 &nbsp; 2 option,usb_wwan
 
 
 
'''spidev&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4898 &nbsp; 0&nbsp;'''
 
 
 
root@igep00x0:/dev# ls /dev/spidev1.2
 
 
 
/dev/spidev1.2
 
 
 
 
|}
 
|}
  
“spidev1.2”: refers at McSPI1 bus 2. Now we can communicate to accelerometer using spi driver functions.
+
=== [kparams]  ===
  
== SPI Test program  ==
+
{| align="JUSTIFY" cellpadding="1" border="1" style="width: 900px; height: 1095px;"
 
 
=== Overview  ===
 
 
 
This program is based in [http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev_test.c;h=16feda9014692a87a4996bf51d759ab9e7500ee5;hb=refs/heads/linux-2.6.37.y spidev_test] and it was edited to run with LIS3DH accelerometer, program can be explained in four parts:
 
 
 
'''Connection properties:''' program lets change via parameters SPI configurations like: device, max speed, delay, bits per word, clock phase, clock polarity, etc. If you don't use any of this parameters program will use default options for LIS3DH communication.
 
 
 
'''Read mode: '''Reads a word from a register.
 
 
 
'''Write mode: '''Writes a word in a register.
 
 
 
'''Test mode:''' Reads X, Y and Z axes from accelerometer.
 
 
 
We recommend to read peripheral datasheet before use or modify program.
 
 
 
=== Compile program  ===
 
 
 
The program source was compiled with Poky SDK but you can use other compilers like Linaro Toolchain:
 
<pre>arm-poky-linux-gnueabi-gcc spiexamplebeta2.c -o spiexampleb2  </pre>
 
Copy your final binary to rootfs.
 
 
 
== Test program<br>  ==
 
 
 
=== Read WHO_AM_I register(0Fh)  ===
 
 
 
LIS3DH has this dummy register (See 8.6 chapter) as a device identification. Its value is 0x33:
 
<pre>root@igep00x0:~# ./spiexampleb2 -R 0F
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Value from 0F is: 33
 
root@igep00x0:~#  </pre>
 
=== Read and Write CTRL_REG1 (20h)  ===
 
 
 
This register is used to enable/disable: accelerometer and XYZ axes (See 8.8 chapter). The default value at startup is:
 
<pre>root@igep00x0:~# ./spiexampleb2 -R 20
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Value from 20 is: 07
 
root@igep00x0:~#  </pre>
 
It means that accelerometer was disabled and X, Y and Z axes was enabled. For example we can disable X axe typing:
 
<pre>root@igep00x0:~# ./spiexampleb2 -W 20 -V 06
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Register to write 20 with value 06
 
root@igep00x0:~# ./spiexampleb2 -R 20     
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Value from 20 is: 06
 
root@igep00x0:~#
 
</pre>
 
=== Read accelerometer axes  ===
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="500"
 
 
|-
 
|-
| Finally we are going to read gravity force: LIS3DH has ±2g/±4g/±8g/±16g dynamically selectable full scale (See chapter 8.11). The axes values are expressed in two’s complement in 16 bits (See chapters 8.16, 8.17 and 8.18).
+
| '''Parameter Name'''
| [[Image:Lis3dhxyzaxes.png|150x159px]]
+
| '''Description'''
|}
+
| '''Default value'''
<pre>root@igep00x0:~# ./spiexampleb2 -T
+
| '''Comments'''
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Accelerometer TEST
 
Values from X -64, Values from Y -15872 and Values from Z -256
 
root@igep00x0:~#
 
</pre>
 
The next table shows results at different positions:
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="600"
 
 
|-
 
|-
| Position
+
| buddy
| ±2g scale
+
| Enable/disable expansion board support
| ±4g scale
+
| &nbsp;;IGEPv2 Expansion Board support<br>=igep0022
| ±8g scale
+
| &nbsp;;Berlin and Paris Expansion Board support<br>=base0010<br>New York Expansion<br>=ilms0015
| ±16g scale
 
 
|-
 
|-
| [[Image:NYtopimagetest.png|center|100x100px]]
+
| console
| X = 832
+
| Setup the kernel console parameters
Y = 1024
+
| =ttyO2,115200n8
 
+
| -
Z = 15680
 
 
 
|  
 
X = 256
 
 
 
Y = 128
 
 
 
Z = 7872
 
 
 
|  
 
X = 128
 
 
 
Y = 128
 
 
 
Z = 4032
 
 
 
|
 
X = 64
 
 
 
Y = 128
 
 
 
Z = 1280
 
 
 
 
|-
 
|-
| [[Image:NYbotimagetest.png|center|100x100px]]
+
| earlyprintk
|  
+
| Enable early printk
X = 256
+
| -  
 
+
| -
Y = 704
 
 
 
Z = -17216
 
 
 
|
 
X = 256
 
 
 
Y = 256
 
 
 
Z = -8320
 
 
 
|  
 
X = 64
 
 
 
Y = 128
 
 
 
Z = -4096
 
 
 
|  
 
X = 128
 
 
 
Y = 128
 
 
 
Z = -1344
 
 
 
 
|-
 
|-
| [[Image:NYtophoritzontalimagetest.png|center|100x100px]]
+
| mem
|  
+
| Setup the Board Memory Configuration
X = -15872
+
| =430M
 
+
| -
Y = 64
 
 
 
Z = -320
 
 
 
|
 
X = -7936
 
 
 
Y = 64
 
 
 
Z = -512
 
 
 
|  
 
X = -3968
 
 
 
Y = 128
 
 
 
Z = -192
 
 
 
|  
 
X = -1280
 
 
 
Y = 64
 
 
 
Z = -128
 
 
 
 
|-
 
|-
| [[Image:NYbothoritzontalimagetest.png|center|100x100px]]
+
| boot_delay
|  
+
| Setup the boot delay
X = 16448
+
| =0
 
+
| -
Y = 640
 
 
 
Z = 640
 
 
 
|  
 
X = 8128
 
 
 
Y = 192
 
 
 
Z = 384
 
 
 
|  
 
X = 4032
 
 
 
Y = 64
 
 
 
Z = 64
 
 
 
|
 
X = 1344
 
 
 
Y = 64
 
 
 
Z = 192
 
 
 
 
|-
 
|-
| [[Image:NYtopverticalimagetest.png|center|100x100px]]
+
| mpurate
|  
+
| Setup ARM Processor Speed
X = 896
+
| -  
 
+
| -
Y = 16512
 
 
 
Z = -576
 
 
 
|
 
X = 320
 
 
 
Y = 8128
 
 
 
Z = -128
 
 
 
|  
 
X = 192
 
 
 
Y = 4096
 
 
 
Z = -64
 
 
 
|  
 
X = 128
 
 
 
Y = 1344
 
 
 
Z = -128
 
 
 
 
|-
 
|-
| [[Image:NYbotverticalimagetest.png|center|100x100px]]
+
| loglevel
|  
+
| Setup the loglevel
X = -64
+
| -  
 
+
| -
Y = -15872
 
 
 
Z = -256
 
 
 
|
 
X = -512
 
 
 
Y = -7808
 
 
 
Z = -384
 
 
 
|
 
X = -64
 
 
 
&gt;Y = -3840
 
 
 
Z = -384
 
 
 
|  
 
X = -128
 
 
 
Y = -1216
 
 
 
Z = -128
 
 
 
|}
 
 
 
= BACKUP How to use SPI (prove with new firmware, under construction)  =
 
 
 
== Overview  ==
 
 
 
This How-To is meant to be a starting point for people to learn use SPI for IGEP devices as quickly and easily as possible. In this how-to, we run an example program that reads and writes registers from 3-axis accelerometer ([http://www.st.com/internet/analog/product/250725.jsp LIS3DH]) included on the board IGEP New York. <br>
 
 
 
== Requirements  ==
 
 
 
There are some requisites to follow this guide:
 
 
 
*[http://isee.biz/component/zoo/item/igep-virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEP&nbsp;SDK&nbsp;SOFTWARE&nbsp;USER&nbsp;MANUAL (chapter 2.3 "Setting up and running the VM")<br>
 
*[http://isee.biz/component/zoo/item/igep-firmware-yocto-1-2 IGEP Firmware]: follow the IGEP&nbsp;SDK SOFTWARE&nbsp;USER&nbsp;MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card")
 
*[http://isee.biz/products/processor-boards/igep-com-module IGEP&nbsp;COM&nbsp;MODULE] and [http://isee.biz/products/expansion-boards/product-igep-new-york IGEP NEW&nbsp;YORK]<br>
 
*SPI example program '''(link program)'''
 
*MicroSD Card (at least 2Gbytes)
 
 
 
== How Works  ==
 
 
 
'''LIS3DH accelerometer:''' It is the accelerometer mounted in IGEP New York.
 
 
 
'''Omap3 SPI Peripheral:''' It is the hardware used to communicated with accelerometer and other SPI devices.
 
 
 
'''Omap2_mcspi:''' It is a bus driver than controls Omap3 SPI Peripheral.
 
 
 
'''Spi:''' It is a protocol driver that defines functions and strucs used in SPI bus.
 
 
 
'''Spidev:''' It is a device driver that export spi driver functionalities to userspace.
 
 
 
'''Lis3lv02d_spi:''' SPI glue layer for lis3lv02d
 
 
 
'''Lis31v02d:''' Device driver for LIS3DH accelerometer.
 
 
 
'''Exp_ilms0015:''' It is a startup program for IGEP New York. It attach lis31v02d with Spi driver.
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="200"
 
 
|-
 
|-
| [[Image:Spi linux schematic.png|501x600px]]
+
| debug
|}
+
| Enable kernel debug output
 
+
| -  
<br> More information about Linux Kernel SPI at:
+
| -
 
 
*[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spi-summary;h=4884cb33845d7629987f60610eeedb863561006e;hb=refs/heads/linux-2.6.37.y SPI Overview]
 
 
 
*[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev;h=ed2da5e5b28a4490a3b03787b02df66d083692be;hb=refs/heads/linux-2.6.37.y SPIDEV]
 
 
 
== Attach Spidev to SPI driver  ==
 
 
 
=== Modify Linux Kernel Sources  ===
 
 
 
To read accelerometer registers from spidev, we need to attach spidev driver to spi driver at start up. So it is necessary to modify spi_board.
 
 
 
Go to $(Kernel path)/arch/arm/mach-omap2/exp-ilms0015.c and edit the next fields in bold words.
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="500"
 
 
|-
 
|-
|  
+
| fixrtc
static struct spi_board_info lis3lv02d_spi_board_info __initdata = {
+
| Fix RTC variable
 
+
| -  
&nbsp;&nbsp;&nbsp;&nbsp;'''.modalias = "spidev",'''
+
| -
 
 
&nbsp;&nbsp;&nbsp; '''//.modalias&nbsp;&nbsp;&nbsp; = "lis3lv02d_spi",'''
 
 
 
&nbsp;&nbsp;&nbsp; .bus_num&nbsp;&nbsp;&nbsp; = -EINVAL,
 
 
 
&nbsp;&nbsp;&nbsp; .chip_select&nbsp;&nbsp;&nbsp; = -EINVAL,
 
 
 
&nbsp;&nbsp;&nbsp; .max_speed_hz&nbsp;&nbsp;&nbsp; = 1*1000*1000,
 
 
 
&nbsp;&nbsp;&nbsp; .irq&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; = -EINVAL,
 
 
 
&nbsp;&nbsp;&nbsp; .mode&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; = SPI_MODE_0,
 
 
 
&nbsp;&nbsp;&nbsp;'''//.platform_data&nbsp;&nbsp;&nbsp; = &amp;lis3lv02d_pdata,'''
 
 
 
};
 
 
 
inline void __init ilms0015_lis3lv02d_init(int bus_num, int cs, int irq)
 
 
 
{
 
 
 
&nbsp;&nbsp;&nbsp; struct spi_board_info *spi = &amp;lis3lv02d_spi_board_info;
 
 
 
&nbsp;&nbsp;&nbsp; if ((gpio_request(irq, "LIS3LV02D IRQ") == 0)
 
 
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &amp;&amp; (gpio_direction_input(irq) == 0))
 
 
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; gpio_export(irq, 0);
 
 
 
&nbsp;&nbsp;&nbsp; else {
 
 
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pr_err("IGEP: Could not obtain gpio LIS3LV02D IRQ\n");
 
 
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return;
 
 
 
&nbsp;&nbsp;&nbsp; }
 
 
 
&nbsp;&nbsp;&nbsp; spi-&gt;bus_num = bus_num;
 
 
 
&nbsp;&nbsp;&nbsp; spi-&gt;chip_select = cs;
 
 
 
&nbsp;&nbsp;&nbsp; spi-&gt;irq = OMAP_GPIO_IRQ(irq),
 
 
 
&nbsp;&nbsp;&nbsp; spi_register_board_info(&amp;lis3lv02d_spi_board_info, 1);
 
 
 
}
 
 
 
...
 
 
 
void __init ilms0015_init(void)
 
 
 
{
 
 
 
&nbsp;&nbsp;&nbsp; mux_partition = omap_mux_get("core");
 
 
 
&nbsp;&nbsp;&nbsp; /* Mux initialitzation for ilms0015 */
 
 
 
&nbsp;&nbsp;&nbsp; omap_mux_write_array(mux_partition, ilms0015_mux);
 
 
 
&nbsp;&nbsp;&nbsp; /* 3-axis accelerometer */
 
 
 
&nbsp;&nbsp;&nbsp; ilms0015_lis3lv02d_init(1, 2, 174);
 
 
 
&nbsp;&nbsp;&nbsp; /* Export some GPIO */
 
 
 
&nbsp;&nbsp;&nbsp; ilms0015_gpio_init();
 
 
 
}
 
 
 
|}
 
 
 
Now spi_register_board_info has all information necessary to attach spidev driver instead lis3lv02d_spi.
 
 
 
Once we edit code, compile your modified Kernel, you can follow [http://labs.isee.biz/index.php/Linux_Kernel_2.6.37.y#Build_kernel_from_sources this tutorial] for this purpose.
 
 
 
=== Enable ilms0015 support  ===
 
 
 
“ilms0015” is the technical name of IGEP New York.
 
 
 
By default, poky-media-create (See: [http://labs.isee.biz/index.php/How_to_create_a_SD-card_with_the_latest_software_image Poky firmware with Kernel 2.6.37.y]) configured as igep0030, gives support only for IGEP Expansions Paris and Berlin. We need to configure igep.ini and gives support to IGEP New York:
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="500"
 
 
|-
 
|-
| &nbsp;; Machine configuration
+
| nocompcache
'''&nbsp;&nbsp;&nbsp;&nbsp;;buddy=base0010 buddy.revision=B '''
+
| Configure nocompcache variable
 
+
| =1
'''&nbsp;&nbsp;&nbsp; buddy=ilms0015'''
+
| -
 
 
|}
 
 
 
=== Test changes  ===
 
 
 
Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changes:
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="500"
 
 
|-
 
|-
|  
+
| omapfb.mode
root@igep00x0:/dev# lsmod
+
| Configure frame bugger configuration
 
+
| =dvi:hd720-16@50
Module&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size&nbsp;&nbsp;&nbsp; Used by
+
| &nbsp;;Other configuration<br>=dvi:1280x720MR-16@60
 
 
rfcomm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 48522&nbsp;&nbsp; 0
 
 
 
hidp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 13311 &nbsp; 0
 
 
 
l2cap&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; 49001&nbsp;&nbsp; 4 rfcomm,hidp
 
 
 
bluetooth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 67643&nbsp;&nbsp; 3 rfcomm,hidp,l2cap
 
 
 
libertas_sdio&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; 13887 &nbsp; 0
 
 
 
libertas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 99318 &nbsp; 1 libertas_sdio
 
 
 
option&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 13044 &nbsp; 0
 
 
 
usb_wwan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7196 &nbsp; 1 option
 
 
 
usbserial&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 23870 &nbsp; 2 option,usb_wwan
 
 
 
'''spidev&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4898 &nbsp; 0&nbsp;'''
 
 
 
root@igep00x0:/dev# ls /dev/spidev1.2
 
 
 
/dev/spidev1.2
 
 
 
|}
 
 
 
“spidev1.2”: refers at McSPI1 bus 2. Now we can communicate to accelerometer using spi driver functions.
 
 
 
== SPI Test program  ==
 
 
 
=== Overview  ===
 
 
 
This program is based in [http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev_test.c;h=16feda9014692a87a4996bf51d759ab9e7500ee5;hb=refs/heads/linux-2.6.37.y spidev_test] and it was edited to run with LIS3DH accelerometer, program can be explained in four parts:
 
 
 
'''Connection properties:''' program lets change via parameters SPI configurations like: device, max speed, delay, bits per word, clock phase, clock polarity, etc. If you don't use any of this parameters program will use default options for LIS3DH communication.
 
 
 
'''Read mode: '''Reads a word from a register.
 
 
 
'''Write mode: '''Writes a word in a register.
 
 
 
'''Test mode:''' Reads X, Y and Z axes from accelerometer.
 
 
 
We recommend to read peripheral datasheet before use or modify program.
 
 
 
=== Compile program  ===
 
 
 
The program source was compiled with Poky SDK but you can use other compilers like Linaro Toolchain:
 
<pre>arm-poky-linux-gnueabi-gcc spiexamplebeta2.c -o spiexampleb2  </pre>
 
Copy your final binary to rootfs.
 
 
 
== Test program<br> ==
 
 
 
=== Read WHO_AM_I register(0Fh)  ===
 
 
 
LIS3DH has this dummy register (See 8.6 chapter) as a device identification. Its value is 0x33:
 
<pre>root@igep00x0:~# ./spiexampleb2 -R 0F
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Value from 0F is: 33
 
root@igep00x0:~#  </pre>
 
=== Read and Write CTRL_REG1 (20h)  ===
 
 
 
This register is used to enable/disable: accelerometer and XYZ axes (See 8.8 chapter). The default value at startup is:
 
<pre>root@igep00x0:~# ./spiexampleb2 -R 20
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Value from 20 is: 07
 
root@igep00x0:~#  </pre>
 
It means that accelerometer was disabled and X, Y and Z axes was enabled. For example we can disable X axe typing:
 
<pre>root@igep00x0:~# ./spiexampleb2 -W 20 -V 06
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Register to write 20 with value 06
 
root@igep00x0:~# ./spiexampleb2 -R 20     
 
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Value from 20 is: 06
 
root@igep00x0:~#
 
</pre>
 
=== Read accelerometer axes  ===
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="500"
 
 
|-
 
|-
| Finally we are going to read gravity force: LIS3DH has ±2g/±4g/±8g/±16g dynamically selectable full scale (See chapter 8.11). The axes values are expressed in two’s complement in 16 bits (See chapters 8.16, 8.17 and 8.18).
+
| vram
| [[Image:Lis3dhxyzaxes.png|150x159px]]
+
| Configure Video RAM assigned to every frame buffer
|}
+
| -  
<pre>root@igep00x0:~# ./spiexampleb2 -T
+
| -
spi mode: 0
 
bits per word: 8
 
max speed: 1000000 Hz (1000 KHz)
 
Accelerometer TEST
 
Values from X -64, Values from Y -15872 and Values from Z -256
 
root@igep00x0:~#
 
</pre>
 
The next table shows results at different positions:
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="600"
 
 
|-
 
|-
| Position
+
| omapfb.vram
| ±2g scale
+
| Configure Video RAM assigned to every frame buffer
| ±4g scale
+
| -
| ±8g scale
+
| -
| ±16g scale
 
 
|-
 
|-
| [[Image:NYtopimagetest.png|center|100x100px]]
+
| omapfb.debug
| X = 832
+
| Configure frame buffer debug output
Y = 1024
+
| -
 
+
| -
Z = 15680
 
 
 
|
 
X = 256
 
 
 
Y = 128
 
 
 
Z = 7872
 
 
 
|  
 
X = 128
 
 
 
Y = 128
 
 
 
Z = 4032
 
 
 
|  
 
X = 64
 
 
 
Y = 128
 
 
 
Z = 1280
 
 
 
 
|-
 
|-
| [[Image:NYbotimagetest.png|center|100x100px]]
+
| omapdss.debug
|  
+
| Configure DSS Video debug output
X = 256
+
| -  
 
+
| -
Y = 704
 
 
 
Z = -17216
 
 
 
|
 
X = 256
 
 
 
Y = 256
 
 
 
Z = -8320
 
 
 
|  
 
X = 64
 
 
 
Y = 128
 
 
 
Z = -4096
 
 
 
|  
 
X = 128
 
 
 
Y = 128
 
 
 
Z = -1344
 
 
 
 
|-
 
|-
| [[Image:NYtophoritzontalimagetest.png|center|100x100px]]
+
| smsc911x.mac0
|  
+
| Configure Board Ethernet Mac Address
X = -15872
+
| =0xb2,0xb0,0x14,0xb5,0xcd,0xde
 
+
| For IGEP BERLIN
Y = 64
 
 
 
Z = -320
 
 
 
|  
 
X = -7936
 
 
 
Y = 64
 
 
 
Z = -512
 
 
 
|  
 
X = -3968
 
 
 
Y = 128
 
 
 
Z = -192
 
 
 
|
 
X = -1280
 
 
 
Y = 64
 
 
 
Z = -128
 
 
 
 
|-
 
|-
| [[Image:NYbothoritzontalimagetest.png|center|100x100px]]
+
| smsc911x.mac1
|  
+
| Configure Board Ethernet Mac Address
X = 16448
+
| =0xb2,0xb0,0x14,0xb5,0xcd,0xdf
 
+
| For IGEP BERLIN (only with IGEP PROTON)
Y = 640
 
 
 
Z = 640
 
 
 
|  
 
X = 8128
 
 
 
Y = 192
 
 
 
Z = 384
 
 
 
|  
 
X = 4032
 
 
 
Y = 64
 
 
 
Z = 64
 
 
 
|
 
X = 1344
 
 
 
Y = 64
 
 
 
Z = 192
 
 
 
 
|-
 
|-
| [[Image:NYtopverticalimagetest.png|center|100x100px]]
+
| smsc911x.mac
|  
+
| Configure Board Ethernet Mac Address
X = 896
+
| =0xb2,0xb0,0x14,0xb5,0xcd,0xde
 
+
| For IGEPv2, IGEP PROTON, IGEP PARIS and IGEP BERLIN
Y = 16512
 
 
 
Z = -576
 
 
 
|  
 
X = 320
 
 
 
Y = 8128
 
 
 
Z = -128
 
 
 
|  
 
X = 192
 
 
 
Y = 4096
 
 
 
Z = -64
 
 
 
|
 
X = 128
 
 
 
Y = 1344
 
 
 
Z = -128
 
 
 
 
|-
 
|-
| [[Image:NYbotverticalimagetest.png|center|100x100px]]
+
| ubi.mtd
|
+
| Fot UBI FS boot
X = -64
+
| -  
 
+
| -
Y = -15872
 
 
 
Z = -256
 
 
 
|  
 
X = -512
 
 
 
Y = -7808
 
 
 
Z = -384
 
 
 
|
 
X = -64
 
 
 
&gt;Y = -3840
 
 
 
Z = -384
 
 
 
|  
 
X = -128
 
 
 
Y = -1216
 
 
 
Z = -128
 
 
 
|}
 
 
 
= How to install Qt Creator (under construction)  =
 
 
 
= How to install Eclipse (under construction)  =
 
 
 
= 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&nbsp;:
 
 
 
*[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>
 
 
 
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
 
 
|-
 
|-
| [[Image:Igepv2expconnectoigepv2.PNG|268px]]<br>
+
| root
| [[Image:Igepv2expconnectoigepv2 2.PNG|268px]]<br>
+
| Configure root directory for MMC, NFS or UBI
|}
+
| &nbsp;;For mmc memory<br>=/dev/mmcblk0p2 rw rootwait
 
+
| &nbsp;;For flash memory<br>=/dev/mtdblock2
== 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'''&nbsp;
 
 
 
{| align="right" cellspacing="1" cellpadding="1" border="1" width="363"
 
 
|-
 
|-
| [[Image:Igepv2expconnecttovga.jpg|150px]]
+
| nfsroot
| [[Image:Igepv2expvgaconnector.PNG|200px]]
+
| For NFS boot
|}
+
| -
 
+
| -
IGEPv2 Expansion integrates a VGA connector, the output VGA signal is equal to HDMI connector. Plug a monitor with VGA&nbsp;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" border="1" width="350"
 
 
|-
 
|-
| Signal Name
+
| rootfstype
| Pin #<br>
+
| For UBI FS boot
| Description
+
| -
 +
| -
 
|-
 
|-
| VDD_CAN
+
| ip
| J703:1
+
| For NFS boot
| Supply Voltage (+5V DC)
+
| -
 +
| -
 
|-
 
|-
| CANL
+
| init
| J703:2
+
| Assign init program
| CAN Low-Level Voltage I/O
+
| -
 +
| -
 
|-
 
|-
| GND
+
| musb_hdrc.debug
| J703:3
+
| USB debug
| Ground
+
| -
 +
| -
 
|-
 
|-
| CANH
+
| musb_hdrc.use_dma
| J703:4
+
| USB over network
| CAN High-Level Voltage I/O
+
| -  
|}
+
| -
 
 
== GSM/GPRS modem  ==
 
 
 
'''Basic'''
 
 
 
{| align="right" cellspacing="1" cellpadding="1" border="1" width="200"
 
 
|-
 
|-
| [[Image:IGEP0022 Modem with antenna.png|200px]]
+
| libertas.libertas_debug
| [[Image:Igepv2expcardreader.PNG|right|200px]]
+
| Configure libertas debug
 +
| -
 +
| -
 
|-
 
|-
| GSM-GPRS antenna (highly recommended)
+
| board.ei485
| SIM card reader
+
| Enable/disable RS485
|}
+
| &nbsp;;Enable RS485<br>=yes
 
+
| &nbsp;;Disable RS485<br>=no
IGEPv2 Expansion integrates a GSM/GPRS&nbsp;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)
 
 
 
&nbsp;&nbsp;&nbsp; - Power off: ‹ 62 uA<br>&nbsp;&nbsp;&nbsp; - 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&nbsp;(/dev/ttyS0 or /dev/ttyS1 or /dev/ttyS3, etc.). Note that if you are using a USB-&gt;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" border="1" width="200"
 
 
|-
 
|-
| [[Image:IGEPV2EXPCHMDB9.png|250px]]
+
| board.modem
| [[Image:Remoteshellpromptdb9putty.jpg|250px]]
+
| Enable/disable GPRS modem  
|}
+
| &nbsp;;Enable modem (IGEPv2 Expansion)<br>=no
 
+
| &nbsp;;Enable modem (IGEPv2 Expansion)<br>=yes
'''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 -&gt;&nbsp;:wq -&gt; Enter) and reboot your IGEP Device
 
*Power up the modem. You can power off using again these commands:
 
<pre>echo 0 &gt; /sys/class/gpio/gpio140/value
 
echo 1 &gt; /sys/class/gpio/gpio141/value
 
sleep 1
 
echo 0 &gt; /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=&lt;PIN&gt;</pre>
 
*If you correctly inserted the PIN number, the answer should be OK.&nbsp;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
 
&gt; 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 &lt;`´'"&gt;.<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-&gt;"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1-&gt;"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&nbsp;! video/x-raw-yuv,format=\(fourcc\)UYVY,width=720,height=480&nbsp;! ffmpegcolorspace&nbsp;! autovideosink</pre>
 
*Now you can see in your IGEP screen a result similar like this
 
 
 
{| cellspacing="1" cellpadding="1" border="1" width="200"
 
 
|-
 
|-
| [[Image:Igepv2expgstreamercapture.jpg|400px]]
+
| buddy.revision
 +
| Enable hardware buddy revision [A or B]  
 +
| Only for base0010<br>=A
 +
| Only for base0010<br>=B
 
|}
 
|}
 
<br>
 
 
'''Know more'''<br>
 
 
You can use other programs like [[Labs.isee.biz/index.php/How to setup tvp5151 video decoder#Play|yavta]]
 
 
== 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 &lt;bus&gt; &lt;chip&gt; &lt;register&gt;
 
i2cset &lt;bus&gt; &lt;chip&gt; &lt;register&gt; &lt;value&gt;</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:IGEP_Technology_Devices_Guides]]
 

Latest revision as of 15:28, 5 September 2014

TODO:

Categorize new tutorials

How to manage the kernel modules on Linux

How do I edit my kernel command line

AUDIO DSP-ARM

Included (IGEP GST DSP):

AACHEDEC -> DEC AACHE (OK)

http://download.wavetlan.com/SVV/Media/HTTP/FAAC-HE-AAC.aac

gst-launch --gst-debug-level=2 filesrc location=sampleaache.m4a ! TIAuddec1 codecName=aachedec engineName=codecServer ! volume volume=0.25 ! alsasink sync=false

outofthebox->ok


MP3DEC -> DEC MP3 (AUDIO ERRORS)

- Followed README file from ISEE - IGEP DSP - GST + DMAI Support Package 3.40.00

http://www.stephaniequinn.com/Music/Canon.mp3

gst-launch --gst-debug-level=2 filesrc location=Canon.mp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0.25 ! alsasink sync=false

Random fatal bit error

mp3-plugin doesn't resolve the error


G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)

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)

EXTRA_OECONF += "--disable-examples --disable-experimental --disable-sdl --disable-cdaudio --disable-directfb \

                --with-plugins=musicbrainz,wavpack,ivorbis,mpegvideoparse,faad2 --disable-vdpau --disable-apexsink \
                --disable-orc"

Install:


faad2-2.7-r2.armv7a.rpm libfaad2-2.7-r2.armv7a.rpm gst-plugins-bad-faad-0.10.23-r2.armv7a.rpm

maybe there are necessary more packages, compare actual gst-bad-recipe and add changes. Necessary add faad2 recipe

bitbake faad2 gst-plugins-bad
 rpm -i faad2-2.7-r2.armv7a.rpm
rpm -i libfaad2-2.7-r2.armv7a.rpm
rpm -i gst-plugins-bad-faad-0.10.23-r2.1.armv7a.rpm
 

gst-launch --gst-debug-level=3 filesrc location=sample.aac ! faad ! volume volume=0.10 ! alsasink

DM3730: Decode an WMA audio file (OK)

bitbake gst-ffmpeg
gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink  

DM3730: Decode an OGG audio file (OK)

Into repositories (base plugins):

http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg

gst-launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume=0.25 ! alsasink

BASE0033 CONNECTOR SUMMARY TABLE

Configure a static IP using the same private network range

under construction

IGEP Firmware Yocto uses the following Ethernet network configuration (IP addresses)

  • eth0 − 192.168.5.1
  • eth0:0 − assigned via dhcp.

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.

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

(Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration)

igep.ini parameters

The kernel command line syntax is name=value1. These next parameters are supported in igep.ini since IGEP-X_Loader 2.4.0-2:

[kernel]

Parameter Name Description Default value Comments
kaddress Kernel copy address =0x80008000 Hex memory address
rdaddress Ram Disk location address =0x81600000 Hex memory address;
disabled by default
serial.low Serial number (low part) =00000001 Numeric
serial.high Serial number (high part) =00000000 Numeric
revision Revision ID =0003 Numeric
kImageName Kernel, binary image name =zImage Kernel or binary image name
kRdImageName Kernel RAM Disk Image Name - Ram Disk image name
MachineID Machine ID (kernel ID)  ;IGEPv2
=2344
 ;Module
=2717
;Proton
=3203
Mode Boot Mode  ;Linux kernel
=kernel
 ;Other image (like uboot)
[binary image]

[kparams]

Parameter Name Description Default value Comments
buddy Enable/disable expansion board support  ;IGEPv2 Expansion Board support
=igep0022
 ;Berlin and Paris Expansion Board support
=base0010
New York Expansion
=ilms0015
console Setup the kernel console parameters =ttyO2,115200n8 -
earlyprintk Enable early printk - -
mem Setup the Board Memory Configuration =430M -
boot_delay Setup the boot delay =0 -
mpurate Setup ARM Processor Speed - -
loglevel Setup the loglevel - -
debug Enable kernel debug output - -
fixrtc Fix RTC variable - -
nocompcache Configure nocompcache variable =1 -
omapfb.mode Configure frame bugger configuration =dvi:hd720-16@50  ;Other configuration
=dvi:1280x720MR-16@60
vram Configure Video RAM assigned to every frame buffer - -
omapfb.vram Configure Video RAM assigned to every frame buffer - -
omapfb.debug Configure frame buffer debug output - -
omapdss.debug Configure DSS Video debug output - -
smsc911x.mac0 Configure Board Ethernet Mac Address =0xb2,0xb0,0x14,0xb5,0xcd,0xde For IGEP BERLIN
smsc911x.mac1 Configure Board Ethernet Mac Address =0xb2,0xb0,0x14,0xb5,0xcd,0xdf For IGEP BERLIN (only with IGEP PROTON)
smsc911x.mac Configure Board Ethernet Mac Address =0xb2,0xb0,0x14,0xb5,0xcd,0xde For IGEPv2, IGEP PROTON, IGEP PARIS and IGEP BERLIN
ubi.mtd Fot UBI FS boot - -
root Configure root directory for MMC, NFS or UBI  ;For mmc memory
=/dev/mmcblk0p2 rw rootwait
 ;For flash memory
=/dev/mtdblock2
nfsroot For NFS boot - -
rootfstype For UBI FS boot - -
ip For NFS boot - -
init Assign init program - -
musb_hdrc.debug USB debug - -
musb_hdrc.use_dma USB over network - -
libertas.libertas_debug Configure libertas debug - -
board.ei485 Enable/disable RS485  ;Enable RS485
=yes
 ;Disable RS485
=no
board.modem Enable/disable GPRS modem  ;Enable modem (IGEPv2 Expansion)
=no
 ;Enable modem (IGEPv2 Expansion)
=yes
buddy.revision Enable hardware buddy revision [A or B] Only for base0010
=A
Only for base0010
=B