Changes

User:Pau pajuelo

23,973 bytes removed, 15:28, 5 September 2014
m
DM3730: Decode an AAC audio file (OK)
= TODO: =
Update peripheral 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 http://download.wavetlan.com/SVV/Media/HTTP/FAAC-> How to develop under Eclipse (copy manual) (refers at beginning VM and option to install Eclipse(under construction)) HE-AAC.aac
Qt gst-> How to develop under Qt (refers at begginin VM and option to install Qt (under construction)) 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
<br> ----
Adapt IGEPv2 to IGEPv2 Expansion '''MP3DEC -> DEC MP3 (AUDIO ERRORS)'''
= How to use SPI (prove with new firmware, under construction) =- Followed README file from ISEE - IGEP DSP - GST + DMAI Support Package 3.40.00
== Overview ==http://www.stephaniequinn.com/Music/Canon.mp3
This Howgst-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 howlaunch --gst-to, we run an example program that reads and writes registers from 3debug-axis accelerometer ([http://www.st.com/internet/analog/product/250725level=2 filesrc location=Canon.jsp LIS3DH]) included on the board IGEP New Yorkmp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0. <br> 25 ! alsasink sync=false
== Requirements =='''Random fatal bit error'''
There are some requisites to follow this guide: '''mp3-plugin doesn't resolve the error'''
*[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 =='''G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)'''
'''LIS3DH accelerometer:G711ENC -> ENC PCM uLAW (speech) (NOT TESTED)''' It is the accelerometer mounted in IGEP New York.
===Not included (IGEP GST DSP):==='''Omap3 SPI Peripheral:ACCLCDEC -> DEC AACLE (NOT TESTED)''' It is the hardware used to communicated with accelerometer and other SPI devices.
'''Omap2_mcspi:AACLDDEC -> DEC AACLD (NOT TESTED)''' It is a bus driver than controls Omap3 SPI Peripheral.
'''Spi:WMA9 -> DEC WMA9 (COMPILING ISSUES)''' It is a protocol driver that defines functions and strucs used in SPI bus.
'''Spidev:ACCLCENC -> ENC AACLE (NOT TESTED)''' It is a device driver that export spi driver functionalities to userspace.
'''Lis3lv02d_spi:ACCHEENC -> ENC AACHE (NOT TESTED)''' SPI glue layer for lis3lv02d
'''Lis31v02d:AACLDENC -> ENC AACLD (NOT TESTED)''' Device driver for LIS3DH accelerometer.
'''Exp_ilms0015:WMA8 -> ENC WMA8 (NOT TESTED)''' It is a startup program for IGEP New York. It attach lis31v02d with Spi driver.
{| border="1" width="200" cellspacing="1" cellpadding="1"|'''Problems adding codecs into igep-| [[Image:Spi linux schematic.png|501x600px]]|}gst-dsp'''
<br> More information about Linux Kernel SPI at: == DM3730==
*[http=== DM3730://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;Decode aMP3 file (OK) (ADDED TO REPOSISTORIES)=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]'''under contruction'''
== Prepare Micro SD Card =='''does not have an accelerated audio decoder element'''
=== Generate Micro SD Card ===- Compiled gst-plugins-ugly using yocto tools
Open a terminal and use the following steps to download and generate a Micro SD card. <pre>wget http://downloads.isee.biz/denzil/binary/igep_firmware-yoctorpm -1.2.1igst-1.tar.bz2 tar jxf igep_firmwareplugins-yoctougly-*.tar0.bz2cd igep_firmware-yocto-* </pre> Insert a SD-Card media and use the igep-media-create script to copy the firmware. rpm
./igep-media-create -–mmc &lt;mmc&gt; --image demo-imagerpm -satoi libmad0-igep00x00.tar*.bz2&nbsp;--machine igep0030 rpm
where &lt;mmc&gt; - is the SD-Card device of your computer. For example, assuming the SD-card device takes '/dev/sdb' type: <pre>./igep-media-create --mmc /dev/sdb --machine igep0030 rpm -i gst-image demoplugins-imageugly-satomad-igep00x00.tar.bz2 </pre> This should give you a bootable SD-card with IGEP&nbsp;COM&nbsp;MODULE support*. rpm
'''NOTE:''' Use the following tutorial '''(upgrade it)''' to connect via Ethernet Gadget with IGEP&nbsp;COM&nbsp;MODULE - gst-launch filesrc location=sample.mp3 ! mad ! volume volume=0.25 ! alsasink
=== Custom Micro SD Card DM3730: Decode a RA or RM audio file (ERRORS)===
'''"Include clone git commands"''' gst-launch --gst-debug-level=3 filesrc location=sample.ra ! rmdemux ! volume volume=0.25 ! alsasink
==== Modify Linux Kernel Sources to attach Spidev to SPI&nbsp;driver ====http://www.superluminal.com/andalib/ra/listen.ra
To read accelerometer registers from spidev, we need to attach spidev driver to spi driver at start upgst-plugins-ugly-rmdemux-0. So it is necessary to modify spi_board10. 19-r1.armv7a.rpm
Go to $(Kernel path)/arch/arm/machlibgstsdp-omap2/exp0.10-0-0.10.36-r3.armv7a.rpm:libgstsdp-0.10-ilms00150 libgstsdp-0.10.c and edit the next fields in bold wordsso. 0
{| border="1" width="500" cellspacing="1" cellpadding="1"libgstrtsp-0.10-0-0.10.36-r3.armv7a.rpm:|libgstrtsp-0.10-0 | static struct spi_board_info lis3lv02d_spi_board_info __initdata = { libgstrtsp-0.10.so.0
&nbsp;&nbsp;&nbsp;&nbsp;'''.modalias = "spidev",Error:'''
&nbsp;&nbsp;&nbsp; '''//0:00:00.modalias&nbsp;&nbsp;&nbsp; = "lis3lv02d_spi"084839071 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header,''' unprintable FOURCC
&nbsp;&nbsp;&nbsp; 0:00:00.bus_num&nbsp;&nbsp;&nbsp; = -EINVAL085052695 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
&nbsp;&nbsp;&nbsp; 0:00:00.chip_select&nbsp;&nbsp;&nbsp; = -EINVAL, 085540976 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id .ra4
&nbsp;&nbsp;&nbsp; 0:00:00.max_speed_hz&nbsp;&nbsp;&nbsp; = 1*1000*1000085693564 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
&nbsp;&nbsp;&nbsp; 0:00:00.irq&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; = -EINVAL085815634 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
&nbsp;&nbsp;&nbsp; 0:00:00.mode&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; = SPI_MODE_0, 085907187 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id RaTC
&nbsp;&nbsp;&nbsp;'''//.platform_data&nbsp;&nbsp;&nbsp; = &amp;lis3lv02d_pdata,''' == 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:
inline void __init ilms0015_lis3lv02d_init(int bus_num, int cs, int irq)
{ faad2-2.7-r2.armv7a.rpmlibfaad2-2.7-r2.armv7a.rpmgst-plugins-bad-faad-0.10.23-r2.armv7a.rpm
&nbsp;&nbsp;&nbsp; struct spi_board_info *spi = &amp;lis3lv02d_spi_board_info; '''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.rpmrpm -i libfaad2-2.7-r2.armv7a.rpmrpm -i gst-plugins-bad-faad-0.10.23-r2.1.armv7a.rpm </pre>
&nbsp;&nbsp;&nbsp; if ((gpio_request(irq, "LIS3LV02D IRQ") gst-launch --gst-debug-level=3 filesrc location=sample.aac ! faad ! volume volume= 0) .10 ! alsasink
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &amp;&amp; ==== DM3730: Decode an WMA audio file (gpio_direction_input(irqOK) == 0)) ==
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; gpio_export(irq, 0); <pre>bitbake gst-ffmpeg</pre>
&nbsp;&nbsp;&nbsp; else { <pre>gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink </pre>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pr_err=== DM3730: Decode an OGG audio file ("IGEP: Could not obtain gpio LIS3LV02D IRQ\n"OK); ===
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return; '''Into repositories (base plugins):'''
&nbsp;&nbsp;&nbsp; } http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
&nbsp;&nbsp;&nbsp; spigst-&gt;bus_num launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume= bus_num; 0.25 ! alsasink
&nbsp;&nbsp;&nbsp; spi-&gt;chip_select = cs; = BASE0033 CONNECTOR SUMMARY TABLE==
&nbsp;&nbsp;&nbsp; spi-&gt;irq = OMAP_GPIO_IRQ(irq), = Configure a static IP using the same private network range ==
&nbsp;&nbsp;&nbsp; spi_register_board_info(&amp;lis3lv02d_spi_board_info, 1); '''under construction'''
} IGEP Firmware Yocto uses the following Ethernet network configuration (IP addresses)
*eth0 − 192.168.5.1*eth0:0 − assigned via dhcp.
void __init ilms0015_init(void) 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
&nbsp;&nbsp;&nbsp; mux_partition = omap_mux_get("core"Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration);
&nbsp;&nbsp;&nbsp; /* Mux initialitzation for ilms0015 */ = igep.ini parameters =
&nbsp;&nbsp;&nbsp; omap_mux_write_array(mux_partition, ilms0015_mux); 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; /* 3-axis accelerometer */  &nbsp;&nbsp;&nbsp; ilms0015_lis3lv02d_init(1, 2, 174);  &nbsp;&nbsp;&nbsp; /* Export some GPIO */  &nbsp;&nbsp;&nbsp; ilms0015_gpio_init();  } === [kernel] ===
{| align="JUSTIFY" cellpadding="1" border="1" style="width: 900px; height: 240px;"
|-
| '''Parameter Name'''
| '''Description'''
| '''Default value'''
| '''Comments'''
|-
| kaddress
| Kernel copy address
| =0x80008000
| Hex memory address
|-
| rdaddress
| Ram Disk location address
| =0x81600000
| Hex memory address;<br>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<br>=2344
| ;Module<br>=2717<br>;Proton<br>=3203
|-
| Mode
| Boot Mode
| ;Linux kernel<br>=kernel
| ;Other image (like uboot)<br>[binary image]
|}
Now spi_register_board_info has all information necessary to attach spidev driver instead lis3lv02d_spi. === [kparams] ===
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.  {| align="JUSTIFY" cellpadding="1" border="1" style= "width: 900px; height: 1095px;"|-| '''Parameter Name''' | '''Description''' | '''Default value''' | '''Comments'''|-| buddy | Enable ilms0015 /disable expansion board support | &nbsp;;IGEPv2 Expansion Board support <br>=igep0022 | &nbsp;;Berlin and Paris Expansion Board support<br>=base0010<br>New York Expansion<br>=ilms0015|-| console | Setup the kernel console parameters | =ttyO2,115200n8 | -“ilms0015” is the technical name of IGEP New York. |-| earlyprintk | Enable early printk 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: | mem | Setup the Board Memory Configuration {| border="1" width430M | -|-| boot_delay | Setup the boot delay | ="500" cellspacing="1" cellpadding="1"0 | -
|-
| &nbsp;; Machine configuration '''&nbsp;&nbsp;&nbsp;&nbsp;;buddy=base0010 buddy.revision=B '''  '''&nbsp;&nbsp;&nbsp; buddy=ilms0015''' mpurate | Setup ARM Processor Speed |} ==== Test changes ==== Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changes: - {| border="1" width="500" cellspacing="1" cellpadding="1"-
|-
| loglevel root@igep00x0:/dev# lsmod  Module&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size&nbsp;&nbsp;&nbsp; Used by  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 | Setup the loglevel |} “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 === {| border="1" width="500" cellspacing="1" cellpadding="1"
|-
| 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). debug | [[Image:Lis3dhxyzaxes.png|150x159px]]Enable kernel debug output |}<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:  {| border="1" width="600" cellspacing="1" cellpadding="1"
|-
| Position fixrtc | ±2g scale Fix RTC variable | ±4g scale - | ±8g scale | ±16g scale-
|-
| [[Image:NYtopimagetest.png|center|100x100px]] nocompcache | X = 832 Y = 1024  Z = 15680 Configure nocompcache variable | X = 256  Y = 128  Z = 7872 1 | X = 128  Y = 128  Z = 4032  | X = 64  Y = 128  Z = 1280 -
|-
| [[Image:NYbotimagetestomapfb.png|center|100x100px]] mode | X = 256  Y = 704  Z = -17216 Configure frame bugger configuration | X = 256  Y = 256  Z = dvi:hd720-8320 16@50 | X = 64  Y = 128  Z &nbsp;;Other configuration<br>= dvi:1280x720MR-4096  | X = 128  Y = 128  Z = -1344 16@60
|-
| [[Image:NYtophoritzontalimagetest.png|center|100x100px]] vram | X = -15872  Y = 64  Z = -320  | X = -7936  Y = 64  Z = -512 Configure Video RAM assigned to every frame buffer | X = -3968  Y = 128  Z = -192  | X = -1280  Y = 64  Z = -128  
|-
| [[Image:NYbothoritzontalimagetestomapfb.png|center|100x100px]] | X = 16448  Y = 640  Z = 640 vram | X = 8128  Y = 192  Z = 384 Configure Video RAM assigned to every frame buffer | X = 4032  Y = 64  Z = 64 - | X = 1344  Y = 64  Z = 192 -
|-
| [[Image:NYtopverticalimagetestomapfb.png|center|100x100px]] debug | X = 896  Y = 16512  Z = -576  | X = 320  Y = 8128  Z = -128 Configure frame buffer debug output | X = 192  Y = 4096  Z = -64  | X = 128  Y = 1344  Z = -128  
|-
| [[Image:NYbotverticalimagetestomapdss.png|center|100x100px]] debug | X = -64  Y = -15872  Z = -256  | X = -512  Y = -7808  Z = -384  | X = -64  &gt;Y = -3840  Z = -384 Configure DSS Video debug output | 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.  {| border="1" width="200" cellspacing="1" cellpadding="1"
|-
| [[Image:Spi linux schematicsmsc911x.pngmac0 |501x600px]]Configure Board Ethernet Mac Address |} <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 spidev0xb2,0xb0,0x14,0xb5,0xcd, we need to attach spidev driver to spi driver at start up. So it is necessary to modify spi_board. 0xde Go to $(Kernel path)/arch/arm/mach-omap2/exp-ilms0015.c and edit the next fields in bold words.  {| border="1" width="500" cellspacing="1" cellpadding="1"For IGEP BERLIN
|-
| static struct spi_board_info lis3lv02d_spi_board_info __initdata = {  &nbsp;&nbsp;&nbsp;&nbsp;'''smsc911x.modalias = "spidev",''' mac1 | Configure Board Ethernet Mac Address &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_num0xb2, int cs0xb0, int irq)  {  &nbsp;&nbsp;&nbsp; struct spi_board_info *spi = &amp;lis3lv02d_spi_board_info;  &nbsp;&nbsp;&nbsp; if ((gpio_request(irq0x14, "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(irq0xb5, 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)0xcd,  &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();  } 0xdf |} 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 For IGEP New York.  By default, poky-media-create BERLIN (See: [http://labs.isee.biz/index.php/How_to_create_a_SD-card_with_the_latest_software_image Poky firmware only with Kernel 2.6.37.y]IGEP PROTON) 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:  {| border="1" width="500" cellspacing="1" cellpadding="1"
|-
| &nbsp;; Machine configuration '''&nbsp;&nbsp;&nbsp;&nbsp;;buddy=base0010 buddysmsc911x.revision=B ''' mac | Configure Board Ethernet Mac Address '''&nbsp;&nbsp;&nbsp; buddy| =ilms0015''' 0xb2,0xb0,0x14,0xb5,0xcd,0xde |} === Test changes === Once you copy your new Kernel binaries and edit igep.ini. Power up your boardFor IGEPv2, IGEP PROTON, log in IGEP PARIS and check your changes:  {| border="1" width="500" cellspacing="1" cellpadding="1"IGEP BERLIN
|-
| root@igep00x0:/dev# lsmod  Module&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size&nbsp;&nbsp;&nbsp; Used by  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/spidev1ubi.2  /dev/spidev1.2 mtd | Fot UBI FS boot |} “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 === {| border="1" width="500" cellspacing="1" cellpadding="1"
|-
| 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). root | [[Image:Lis3dhxyzaxes.png|150x159px]]Configure root directory for MMC, NFS or UBI |}&nbsp;;For mmc memory<prebr>root@igep00x0:~# .=/dev/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:~# mmcblk0p2 rw rootwait | &nbsp;;For flash memory</prebr> The next table shows results at different positions:  {| border="1" width="600" cellspacing="1" cellpadding="1"/dev/mtdblock2
|-
| Position nfsroot | ±2g scale For NFS boot | ±4g scale - | ±8g scale | ±16g scale-
|-
| [[Image:NYtopimagetest.png|center|100x100px]] rootfstype | X = 832 Y = 1024  Z = 15680  | X = 256  Y = 128  Z = 7872 For UBI FS boot | X = 128  Y = 128  Z = 4032 - | X = 64  Y = 128  Z = 1280 -
|-
| [[Image:NYbotimagetest.png|center|100x100px]] ip | X = 256  Y = 704  Z = -17216  | X = 256  Y = 256  Z = -8320 For NFS boot | X = 64  Y = 128  Z = -4096  | X = 128  Y = 128  Z = -1344  
|-
| [[Image:NYtophoritzontalimagetest.png|center|100x100px]] init | X = -15872  Y = 64  Z = -320  | X = -7936  Y = 64  Z = -512 Assign init program | X = -3968  Y = 128  Z = -192  | X = -1280  Y = 64  Z = -128  
|-
| [[Image:NYbothoritzontalimagetestmusb_hdrc.png|center|100x100px]] | X = 16448  Y = 640  Z = 640 debug | X = 8128  Y = 192  Z = 384 USB debug | X = 4032  Y = 64  Z = 64 - | X = 1344  Y = 64  Z = 192 -
|-
| [[Image:NYtopverticalimagetestmusb_hdrc.png|center|100x100px]] use_dma | X = 896  Y = 16512  Z = -576  | X = 320  Y = 8128  Z = -128 USB over network | X = 192  Y = 4096  Z = -64  | X = 128  Y = 1344  Z = -128  
|-
| [[Image:NYbotverticalimagetestlibertas.png|center|100x100px]] libertas_debug | X = -64  Y = -15872  Z = -256 Configure libertas debug | 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 (link items with isee shop) = In this tutorial we are going to use the following peripherals:  *IGEPv2 with its power supply *a monitor compatible with VGA *a Powertrip 4.3" or [http://shop.isee.biz/buy-online/accesories/tft-24-bits-seiko-7.html Seiko 7"] screen *a DB9 connector with External Serial peripheral (example: USB Serial convertor) *4 pin connector for CAN Bus with another CAN Bus peripheral *SIM card (optional GPRS antenna) *Composite video cable with a composite video output peripheral *a PC with Linux or Windows = 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:<br>  {| border="1" align="center" width="200" cellspacing="1" cellpadding="1"
|-
| [[Image:Igepv2expconnectoigepv2.PNG|268px]]<br> | [[Image:Igepv2expconnectoigepv2 2.PNG|268px]]<br>|} '''Know more'''  The The IGEPv2 Expansion is the most complete board to expand the main features of the IGEPv2 Board:  *Fully tested, highly reliable, scalable, efficient and high performing board that allows customers to focus on their end application. ei485 *Designed for industrial and commercial purposes. *LCD and Touch Interface (to be used with 7.0’’ Seiko RGB 24-bits TFT Display or 4.3’’ Powertip RGB 24-bits TFT Display) *GSM/GPRS Modem with SIM connector and RF Coaxial external antenna connector. *RS-232 Serial Interface on DB9 connector. *CAN bus interface. *Video decoder with 2 x RCA analog video inputs. *Camera interface. == 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 IEnable/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> disable RS485  '''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. &nbsp;;Enable RS485<br>  '''Know more'''  This peripheral (UART1) can be used to debug system using kernel traces, getting a remote prompt, etc.<br><br><br> == VGA monitor == '''Basic''' yes [[Image:Igepv2expvgaconnector.PNG|right|200px]]IGEPv2 Expansion integrates a VGA connector, the output VGA signal is equal to HDMI connector.<br>  '''Know more'''  This output is controled by ADV7125KSTZ140 Integrated Circuit:  *Triple 8-bit DACs *RS-343A-/RS-170-compatible output *Complementary outputs *DAC output current range: 2.0 mA to 26.5 mA *TTL-compatible inputs *Internal Reference (1.235 V) *HSYNC and VSYNC +5 V operation *48-lead LQFP and LFCSP package == CAN bus == '''Basic'''  [[Image:Igepv2expcanconnector.PNG|right|200px]]IGEPv2 Expansion integrates a 4 pin connector used for CAN communication. Connect any CAN bus device or network to the CAN bus connector.<br>  '''Know more'''  This output is controled by MICROCHIP MCP2515:  *Implements CAN V2.0B at 1 Mb/s *Receive buffers, masks and filters *Data byte filtering on the first two data bytes (applies to standard data frames) *High-speed SPI Interface (10 MHz): SPI modes 0,0 and 1,1 == GSM/GPRS modem == '''Basic'''  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. This peripheral needs:;Disable RS485<br>  {| border="1" align="center" width="200" cellspacing="1" cellpadding="1"no
|-
| [[Image:Igepv2expcardreaderboard.PNGmodem |rightEnable/disable GPRS modem |200px]] &nbsp;;Enable modem (IGEPv2 Expansion)<br>=no | [[Image:IGEP0022 Modem with antenna.png|200px]]&nbsp;;Enable modem (IGEPv2 Expansion)<br>=yes
|-
| SIM card buddy.revision | GSM-GPRS antenna (optional)Enable hardware buddy revision [A or B] | Only for base0010<br>=A | Only for base0010<br>=B
|}
 
'''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
*GSM/GPRS protocol stack 3GPP Release 4 compliant
*Output power
 
&nbsp;&nbsp;&nbsp; - Class 4 (2W) @ 850 / 900 MHz<br>&nbsp;&nbsp;&nbsp; - Class 1 (1W) @ 1800 / 1900 MHz
 
*Control via AT commands according to 3GPP 27.005, 27.007
*Control via Remote AT commands
*Power consumption (typical values)
 
&nbsp;&nbsp;&nbsp; - Power off: ‹ 62 uA<br>&nbsp;&nbsp;&nbsp; - Idle (registered, power saving): 1.6 mA @ DRX=9
 
*Serial port multiplexer 3GPP 27.010
*TCP/IP stack access via AT commands
*Sensitivity:
 
&nbsp;&nbsp;&nbsp; - ≤- 107 dBm (typ.) @ 850 / 900 MHz<br>&nbsp;&nbsp;&nbsp; - ≤- 106 dBm (typ.) @ 1800 / 1900 MHz
 
*Extended temperature range
 
&nbsp;&nbsp;&nbsp; - -40°C to +85°C (operational)<br>&nbsp;&nbsp;&nbsp; - -40°C to +85°C (storage temperature)
 
*RoHS compliant
 
== Composite Video Decoder ==
 
'''Basic'''
 
[[Image:Igepv2expvideocompositeconnector.PNG|right|200px]]IGEPv2 Expansion integrates two composite video connectors to decode analog input signal.<br>
 
'''Know more'''
 
Analog input is decoded by TVP5151, its main blocks are:
 
*Robust sync detector
*ADC with analog processor
*Y/C separation using four-line adaptive comb filter
*Chrominance processor
*Luminance processor
*Video clock/timing processor and power-down control
*Output formatter
*I2C interface
*VBI data processor
*Macrovision detection for composite and S-video
 
== Camera interface ==
 
'''Basic '''<br>[[Image:Igepv2expcameraconnector.PNG|right|200px]]IGEPv2 Expansion integrates a 27 pin (J5) HIROSE Series FH26 (0.3mm pitch for flex circuit cable) for camera or image sensor input.<br>
 
'''Know more'''
 
OMAP3 processor family has Camera Image Signal Processing (ISP) interface. ISP interface could to be connecting to CCD and CMOS image sensors.
 
Detailed features of ISP are:
 
*CCD and CMOS Imager Interface
*Memory Data Input
*BT.601/BT.656 Digital YCbCr 4:2:2 (8-/10-Bit) Interface
*Glueless Interface to Common Video Decoders
*Resize Engine
*Resize Images From 1/4x to 4x
*Separate Horizontal/Vertical Control<br>
 
<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}}
}}
 
ff
 
<br> {{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]]
4,199
edits