Difference between revisions of "User:Pau pajuelo"

From IGEP - ISEE Wiki

Jump to: navigation, search
m (→‎CAN bus)
m (→‎DM3730: Decode an AAC audio file (OK))
 
(474 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= TODO:  =
 
= TODO:  =
  
−
Update peripheral tutorials, finish gpio example program<br>
+
Categorize new tutorials
−
 
 
−
Categorize new tutorials<br>
 
−
 
 
−
Finish tutorials below<br>
 
−
 
 
−
Upgrade IGEP Technology Devices Guides
 
−
 
 
−
Link all development tools documentation when possible (do a diagram)
 
  
 
How to manage the kernel modules on Linux
 
How to manage the kernel modules on Linux
Line 15: Line 7:
 
How do I edit my kernel command line
 
How do I edit my kernel command line
  
−
Basic Software instructions
+
== AUDIO DSP-ARM==
  
−
= What can I do with IGEP PARIS =
+
===Included (IGEP GST DSP):===
 +
'''AACHEDEC -> DEC AACHE (OK)'''
  
−
= Getting started with IGEP BERLIN =
+
http://download.wavetlan.com/SVV/Media/HTTP/FAAC-HE-AAC.aac
  
−
{{Table/IGEP Technology Devices
+
gst-launch --gst-debug-level=2 filesrc location=sampleaache.m4a ! TIAuddec1 codecName=aachedec engineName=codecServer ! volume volume=0.25 ! alsasink  sync=false
−
|Tech_Family={{#lst:Template:Links|IGEP_BERLIN_Tech_Family}}
 
−
|Tech_ID={{#lst:Template:Links|IGEP_BERLIN_Tech_ID}}
 
−
|Name={{#lst:Template:Links|IGEP_BERLIN_Name}}
 
−
|Image={{#lst:Template:Links|IGEP_BERLIN_Image}}
 
−
|ISEE_MainPage={{#lst:Template:Links|IGEP_BERLIN_ISEE_MainPage}}
 
−
|ISEE_Hardware={{#lst:Template:Links|IGEP_BERLIN_ISEE_Hardware}}
 
−
}}
 
  
−
<br> __TOC__
+
outofthebox->ok
  
−
= Overview  =
+
----
−
This is the 1/3 chapter of IGEP BERLIN Expansion Tutorial Guide.
 
  
−
In this first chapter, we will learn how to connect some expansion peripherals.
+
'''MP3DEC -> DEC MP3 (AUDIO ERRORS)'''
  
−
= Requirements =
+
- Followed README file from ISEE - IGEP DSP - GST + DMAI Support Package 3.40.00
  
−
In these tutorials we are going to need the following components:  
+
http://www.stephaniequinn.com/Music/Canon.mp3
  
−
*[http://isee.biz/products/processor-boards/igep-com-proton IGEP COM PROTON] or [http://isee.biz/products/processor-boards/igep-com-module IGEP COM MODULE].
+
gst-launch --gst-debug-level=2 filesrc location=Canon.mp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0.25 ! alsasink  sync=false
−
*5V DC power supply with a minimum of 3A current capacity.
 
−
*[http://shop.isee.biz/buy-online/accesories/tft-24-bits-seiko-7.html Seiko 7"] screen if you need a touch screen.
 
−
*Ethernet cable for network communications.
 
−
*A monitor compatible with DVI-D.
 
−
*An USB keyboard and a mouse (optional).
 
−
*4 pin connector for CAN Bus with another IGEP Board with CAN peripheral to follow CAN Bus communication tutorial.
 
−
*SIM card with an antenna to follow Telit modem tutorial.
 
−
*Composite video cable, composite video output peripheral (PAL or NTSC) and a screen to follow TVP5151 tutorial.
 
−
*Li-on battery with 3V3 (optional).
 
−
*A PC.
 
  
−
= Getting started =
+
'''Random fatal bit error'''
−
== TFT and Touchscreen ==
 
−
'''Basic'''
 
−
[[Image:berlin_paris_screen_connectors.JPG|right|200px]] IGEP BERLIN Expansion supports SEIKO 7” LCD screen. Use J200, J203 and J204 connectors to attach screen. See image for more details.<br>
 
  
−
'''Know more'''<br>
+
'''mp3-plugin doesn't resolve the error'''
  
−
IGEP BERLIN 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.<br><br><br><br>
+
----
  
−
== Serial port ==
+
'''G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)'''
−
'''Basic''' [[Image:Berlin db9.png|right|200px]]
 
  
−
IGEP BERLIN Expansion integrates a DB9 RS232 connector.<br>  
+
'''G711ENC -> ENC PCM uLAW (speech) (NOT TESTED)'''
  
−
'''Know more'''  
+
===Not included  (IGEP GST DSP):===
 +
'''ACCLCDEC -> DEC AACLE (NOT TESTED)'''
  
−
This peripheral (UART 3) can be used to debug system using kernel traces, getting a remote prompt, etc. <br> <br> <br>
+
'''AACLDDEC -> DEC AACLD (NOT TESTED)'''
  
−
== Ethernet Network cable ==
+
'''WMA9 -> DEC WMA9 (COMPILING ISSUES)'''
−
''' Basic ''' [[Image:Berlin ethernet.jpg|right|200px]]
 
  
−
Plug an Ethernet cable between IGEP BERLIN and your client machine (or any other network device with Ethernet connectivity). Use J3 connector with IGEP PROTON and J1001 connector with IGEP MODULE.
+
'''ACCLCENC -> ENC AACLE (NOT TESTED)'''
  
 +
'''ACCHEENC -> ENC AACHE (NOT TESTED)'''
  
−
''' Know more '''
+
'''AACLDENC -> ENC AACLD (NOT TESTED)'''
  
−
IGEP BERLIN comes with three 10/100BASE-TX Ethernet ports.
+
'''WMA8 -> ENC WMA8 (NOT TESTED)'''
  
−
In the following chapters we will use Ethernet to access IGEP PARIS.
+
'''Problems adding codecs into igep-gst-dsp'''
  
−
== USB devices ==
+
== DM3730==
−
''' Basic ''' [[Image:Berlin usbs.png|right|200px]]
 
  
−
Plug an USB keyboard and USB mouse to the USB HOST ports.
+
=== DM3730: Decode a MP3 file (OK) (ADDED TO REPOSISTORIES)===
  
 +
'''under contruction'''
  
−
''' Know more '''
+
'''does not have an accelerated audio decoder element'''
  
−
Only USB 2.0 devices will work in IGEP BERLIN, so if you connect any USB mouse 1.0 into the USB host connector without using a USB hub 2.0, it will not work.
+
- Compiled gst-plugins-ugly using yocto tools
  
−
== Composite Video Decoder ==
+
- rpm -igst-plugins-ugly-0.*.rpm
−
{{Message/Information Message|title=|message=IGEP COM MODULE AND IGEP BERLIN doesn't support video decoder}}
 
−
'''Basic'''
 
−
[[Image:Berlin rca.jpg|right|200px]]IGEP BERLIN Expansion integrates two composite video connectors to decode analog input signal. Plug some peripheral with video composite output.<br>
 
  
−
'''Know more'''
+
- rpm -i libmad0-0.*.rpm
  
−
Analog input is decoded by TVP5151.<br><br><br><br><br>
+
- rpm -i gst-plugins-ugly-mad-0.*.rpm
−
 
 
−
== GSM/GPRS modem ==
 
−
'''Basic'''
 
−
 
 
−
{| align="right" cellspacing="1" cellpadding="1" border="1" width="200"
 
−
|-
 
−
| [[Image:Berlin antenna.png|200px]]
 
−
| [[Image:Berlin simcard.png|right|200px]]
 
−
|-
 
−
| GSM-GPRS antenna (highly recommended)
 
−
| SIM card reader
 
−
|}
 
  
−
IGEP BERLIN Expansion integrates a GSM/GPRS modem to make phone calls or to send SMS or to write and read data from it, etc.<br>
+
- gst-launch filesrc location=sample.mp3 ! mad ! volume volume=0.25 ! alsasink
  
−
'''Know more'''
+
=== DM3730: Decode a RA or RM audio file (ERRORS)===
  
−
Modem chip Telit GE865 is a small GSM/GPRS Ball-Grid-Array BGA module with next main features:
+
gst-launch --gst-debug-level=3 filesrc location=sample.ra ! rmdemux ! volume volume=0.25 ! alsasink
  
−
*Quad-band EGSM 850 / 900 / 1800 / 1900 MHz
+
http://www.superluminal.com/andalib/ra/listen.ra
−
*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>
+
gst-plugins-ugly-rmdemux-0.10.19-r1.armv7a.rpm
  
−
== CAN bus ==
+
libgstsdp-0.10-0-0.10.36-r3.armv7a.rpm:
 +
libgstsdp-0.10-0
 +
libgstsdp-0.10.so.0
  
−
'''Basic'''
+
libgstrtsp-0.10-0-0.10.36-r3.armv7a.rpm:
 +
libgstrtsp-0.10-0
 +
libgstrtsp-0.10.so.0
  
−
[[Image:Berlin can.png|right|200px]]IGEP BERLIN Expansion integrates a CAN peripheral. Connect any CAN bus device or network to the CAN bus connector (J901).<br>
+
'''Error:'''
  
−
'''Know more'''
+
0:00:00.084839071  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
  
−
This output is controled by MICROCHIP MCP2515. J901 is a 3.5 mm pitch terminal blocks 5 Positions:  
+
0:00:00.085052695  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
  
−
{| cellspacing="1" cellpadding="1" width="350" border="1"
+
0:00:00.085540976  1550  0xa137b0 WARN                rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id .ra4
−
|-
 
−
| Signal Name
 
−
| Pin #<br>
 
−
| Description
 
−
|-
 
−
| CANH
 
−
| J901:1
 
−
| CAN High-Level Voltage I/O
 
−
|-
 
−
| CANL
 
−
| J901:2
 
−
| CAN Low-Level Voltage I/O
 
−
|-
 
−
| GND
 
−
| J901:3
 
−
| Ground
 
−
|}
 
  
−
== DVI monitor ==
+
0:00:00.085693564  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
  
−
''' Basic '''
+
0:00:00.085815634  1550  0xa137b0 WARN                rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
−
[[Image:Berlin hdmi.png|right|200px]]
 
−
IGEP BERLIN has a '''HDMI connector''' with a '''DVI-D interface'''
 
  
−
Connect IGEP BERLIN to a DVI-D compatible monitor.
+
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)===
  
−
''' Know more '''
+
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:
  
−
The Digital Visual Interface (DVI) is a video standard interface designed to provide very high visual quality on digital display devices such as flat panel LCD computer displays and digital projectors. It is partially compatible with the High-Definition Multimedia Interface (HDMI) standard in digital mode (DVI-D), and VGA in analog mode (DVI-A).
 
  
−
Note that your monitor should be able to support 1024 x 768 @ 60 Hz, which is the default resolution in the preinstalled software.
+
faad2-2.7-r2.armv7a.rpm
 +
libfaad2-2.7-r2.armv7a.rpm
 +
gst-plugins-bad-faad-0.10.23-r2.armv7a.rpm
  
−
== VGA monitor ==
+
'''maybe there are necessary more packages, compare actual gst-bad-recipe and add changes. Necessary add faad2 recipe'''
−
[[Image:Berlin vga.png|right|200px]]
+
<pre>bitbake faad2 gst-plugins-bad</pre>
−
'''Basic'''
+
<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>
  
−
IGEP BERLIN Expansion integrates a VGA connector, the output VGA signal is equal to HDMI connector.
+
gst-launch --gst-debug-level=3 filesrc location=sample.aac ! faad ! volume volume=0.10 ! alsasink
  
−
'''Know more'''
+
==== DM3730: Decode an WMA audio file (OK)====
  
−
This output is controled by ADV7125KSTZ140 Integrated Circuit.
+
<pre>bitbake gst-ffmpeg</pre>
  
−
<br> <br> <br><br> <br>
+
<pre>gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink  </pre>
  
−
== Battery ==
+
=== DM3730: Decode an OGG audio file (OK)===
−
[[Image:Berlin battery.png|right|200px]]
 
−
J102 is a 2.5mm pitch, can be used to connect a 3,7V battery to power the base board.<br><br><br><br><br><br>
 
  
−
== Connect IGEP BERLIN Expansion with IGEP COM MODULE/NEUTRON Board ==
+
'''Into repositories (base plugins):'''
−
[[Image:BERLIN+module.JPG|right|200px]]
 
−
The IGEP BERLIN Expansion connects to the IGEP COM MODULE/NEUTRON Board through J1 and J4 connectors. Just take a look on the figure below to mount it:<br> <br><br><br><br><br><br>
 
  
−
== Connect IGEP BERLIN Expansion with IGEP COM PROTON Board ==
+
http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
−
[[Image:BERLIN+proton.JPG|right|200px]]
 
−
The IGEP BERLIN Expansion connects to the IGEP COM PROTON Board through J1, J4, J9 and J8 connectors. Just take a look on the figure below to mount it:<br> <br><br><br><br><br><br>
 
  
−
== Power up IGEP BERLIN Expansion ==
+
gst-launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume=0.25 ! alsasink
−
[[Image:Paris berlin connector.png|right|200px]]
 
−
Once you have connected the peripherals '''you can apply power''' to your IGEP BERLIN with 5V DC power supply (J101) with a minimum of 3A current capacity. Press SW101 button (between LEDs) to power up system.<br><br><br><br><br><br><br><br>
 
  
−
== Test the Demo software distribution with touch screen ==
+
== BASE0033 CONNECTOR SUMMARY TABLE==
  
−
''' Basic '''
+
== Configure a static IP using the same private network range ==
  
−
When IGEP BERLIN powers up, the desktop of the preinstalled software will appear on the touch screen.
+
'''under construction'''
  
−
You can use your fingers or a mouse and a keyboard to test the demo applications.
+
IGEP Firmware Yocto uses the following Ethernet network configuration (IP addresses)
  
−
[[Image:Poky-screenshot.png|thumb|500px|center|Screenshot of the Desktop of the pre-installed software]]
+
*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.
  
−
''' Know more '''
+
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
  
−
All IGEP Processor Boards have a pre-installed software in its flash memory which consists of a '''minimal Linux-based distribution''' with a lite X Window System and GNOME Mobile based applications created with '''Poky Platform Builder'''.
+
(Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration)
−
 
 
−
== Log into IGEP BERLIN Expansion via Ethernet interface ==
 
−
 
 
−
{{Message/Information Message|title=|message=In non-Linux operating system, use [http://labs.isee.biz/index.php/IGEP_SDK_Virtual_Machine IGEP SDK Virtual Machine] to connect to IGEP COM MODULE via USB or read article [http://labs.isee.biz/index.php/Using_USB_ethernet_gadget_to_communicate "Using USB ethernet gadget to communicate"]}}
 
−
 
 
−
In your Host Machine:
 
−
 
 
−
Open a Terminal session and set the IP of the Ethernet interface in which IGEP is connected (for example eth0):
 
−
 
 
−
*In the file /etc/network/interfaces, you should add:
 
−
<pre>iface eth0 inet dhcp
 
−
iface eth0:0 inet static
 
−
address 192.168.5.10
 
−
netmask 255.255.255.0</pre>
 
−
*Type in a terminal:
 
−
<pre>sudo ifup eth0:0</pre>
 
−
*Revise that:
 
−
<pre>jdoe@ubuntu ~ $ ifconfig
 
−
...
 
−
eth0:0    Link encap:Ethernet  HWaddr 08:00:27:ad:0c:ad 
 
−
          inet addr:192.168.5.10  Bcast:0.0.0.0  Mask:255.255.255.0
 
−
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 
−
...</pre>
 
−
*Connect to IGEP device
 
−
 
 
−
jdoe@ubuntu ~ $ ssh root@192.168.5.1
 
−
 
 
−
 
 
−
{{Navigation/IGEP Technology Guides/Getting Started/Ending
 
−
|Next_Step={{#lst:Template:Links|IGEP_BERLIN_Community_Guides_2}}
 
−
}}
 
−
 
 
−
{{Table/IGEP Technology Devices
 
−
|Tech_Family={{#lst:Template:Links|IGEP_BERLIN_Tech_Family}}
 
−
|Tech_ID={{#lst:Template:Links|IGEP_BERLIN_Tech_ID}}
 
−
|Name={{#lst:Template:Links|IGEP_BERLIN_Name}}
 
−
|Image={{#lst:Template:Links|IGEP_BERLIN_Image}}
 
−
|ISEE_MainPage={{#lst:Template:Links|IGEP_BERLIN_ISEE_MainPage}}
 
−
|ISEE_Hardware={{#lst:Template:Links|IGEP_BERLIN_ISEE_Hardware}}
 
−
}}
 
−
 
 
−
[[Category:IGEP Technology Devices Guides]]
 
−
 
 
−
= [IGEP Technology devices features table proposal] =
 
−
 
 
−
{| cellspacing="0" cellpadding="1" border="1" style="text-align: center;"
 
−
|-
 
−
|
 
−
| bgcolor="#cccccc" | IGEP0032
 
−
| bgcolor="#cccccc" | IGEP0030
 
−
| bgcolor="#cccccc" | IGEP0030
 
−
| bgcolor="#cccccc" | IGEP0020
 
−
| bgcolor="#cccccc" | IGEP0010
 
−
|-
 
−
| '''Product name'''
 
−
| bgcolor="#cccccc" | '''IGEP COM PROTON'''
 
−
| bgcolor="#cccccc" | '''IGEP COM MODULE'''
 
−
| bgcolor="#cccccc" | '''IGEP COM ELECTRON'''
 
−
| bgcolor="#cccccc" | '''IGEPv2'''
 
−
| bgcolor="#cccccc" | '''IGEP0010'''
 
−
|-
 
−
|
 
−
| width="200" | [[Image:Igep0032 side.png|145x93px|center|link=Category:IGEP0032]]
 
−
| width="200" | [[Image:Igep0030.jpg|184x120px|center|link=Category:IGEP0030]]
 
−
| width="200" | [[Image:Igep0030neutron.png|184x120px|center|link=Category:IGEP0030]]
 
−
| width="200" | [[Image:Igep0020.jpg|174x116px|center|link=Category:IGEP0020]]
 
−
| width="200" | [[Image:Igep0010.jpg|181x114px|center|link=Category:IGEP0010]]
 
−
|-
 
−
| '''Devices and interfaces'''
 
−
|| || || || || (discontinued product)
 
−
|-
 
−
| style="text-align: right;" | ARM CPU
 
−
|| DM3730 1GHz || DM3730 1GHz|| AM3703 1GHz || DM3730 1GHz || -
 
−
|-
 
−
| style="text-align: right;" | DSP
 
−
|| TMS320DM-C64+ 800 Mhz || TMS320DM-C64+ 800 Mhz || - ||TMS320DM-C64+ 800 Mhz || -
 
−
|-
 
−
| style="text-align: right;" | RAM Memory
 
−
|| 512 MBytes / 200 Mhz || 512 MBytes / 200 Mhz || 256 MBytes / 200 Mhz || 512 MBytes / 200 Mhz || -
 
−
|-
 
−
| style="text-align: right;" | Flash Memory
 
−
|| 512 MBytes || 512 MBytes || 512 MBytes || 512 MBytes || -
 
−
|-
 
−
| style="text-align: right;" | MicroSD Card Reader
 
−
|| x 1 || x 1 || x 1 || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | USB 2.0 Host
 
−
|| - || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | USB 2.0 OTG
 
−
|| x 1 || x 1 || x 1 || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | RS232
 
−
|| - || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | RS485
 
−
|| - || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | JTAG
 
−
|| x 1 || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | Stereo audio In/Out
 
−
|| - || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | DVI on HDMI
 
−
|| - || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | Ethernet
 
−
|| - || - || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | Wifi
 
−
|| - || x 1 || - || x 1 || -
 
−
|-
 
−
| style="text-align: right;" | Bluetooth
 
−
|| - || x 1 || - ||  x 1 || -
 
−
|-
 
−
| style="text-align: right;" | EEPROM
 
−
|| x 1 || - || - || - || -
 
−
|-
 
−
| style="text-align: right;" | S-Video
 
−
|| - || - || - || T.P. || -
 
−
|-
 
−
| style="text-align: right;" | Camera Interface
 
−
|| - || x 1 || - || N.P. || -
 
−
|-
 
−
| style="text-align: right;" | Analog to digital converter
 
−
|| - || - || - ||N.P.|| -
 
−
|-
 
−
| style="text-align: right;" | Keyboard matrix
 
−
|| - || - || - || N.P. || -
 
−
|-
 
−
| style="text-align: right;" | LEDs
 
−
|| x 3 green LEDs || x 2 bicolor LEDs|| x 1 bicolor LED||  x 2 bicolor LEDs|| -
 
−
|-
 
−
| style="text-align: right;" | TFT Interface
 
−
|| - || - || - || x 2 || -
 
−
|-
 
−
| style="text-align: right;" | RTC Battery Back Up
 
−
|| - || - || - || x 2 || -
 
−
|-
 
−
| Size
 
−
||35x51,2mm || 18x68,5mm || 18x68,5mm || 65x95mm || -
 
−
|-
 
−
| style="text-align: right;" | '''Expansion connectors'''
 
−
|| Power and many functionalities from OMAP3 processor || Power and many functionalities from OMAP3 processor || Power and many functionalities from OMAP3 processor || Power 5V and 1.8V, UART, McBSP, McSPI, I2C, GPIO, RS485 with transceiver, Keyboard || -
 
−
|-
 
−
| style="text-align: right;" rowspan="2" | '''Main pages'''
 
−
| style="text-align: center;" | [[Image:Isee logo.png|57x57px|link=http://www.isee.biz/products/processor-boards/igep-com-proton]]
 
−
| style="text-align: center;" | [[Image:Isee logo.png|57x57px|link=http://www.isee.biz/products/processor-boards/igep-com-module]]
 
−
| style="text-align: center;" | [[Image:Isee logo.png|57x57px|link=http://www.isee.biz/products/processor-boards/igep-com-electron]]
 
−
| style="text-align: center;" | [[Image:Isee logo.png|57x57px|link=http://www.isee.biz/products/processor-boards/igepv2-board]]
 
−
| style="text-align: center;" rowspan="3" | -
 
−
|-
 
−
| style="text-align: center;" | [[Image:Igep community logo.png|62x62px|link=Category:IGEP0032]]
 
−
| style="text-align: center;" | [[Image:Igep community logo.png|62x62px|link=Category:IGEP0030]]
 
−
| style="text-align: center;" | [[Image:Igep community logo.png|62x62px|link=Category:IGEP0030]]
 
−
| style="text-align: center;" | [[Image:Igep community logo.png|62x62px|link=Category:IGEP0020]]
 
−
|-
 
−
| style="text-align: right;" | '''Getting started guide'''<br>
 
−
| style="text-align: center;" | [[Image:Documentation.png|33x33px|link=Getting Started with IGEP0032 board]]
 
−
| style="text-align: center;" | [[Image:Documentation.png|33x33px|link=Getting Started with IGEP0030 board]]
 
−
| style="text-align: center;" | [[Image:Documentation.png|33x33px|link=Getting Started with IGEP0030 board]]
 
−
| style="text-align: center;" | [[Image:Documentation.png|33x33px|link=Getting Started with IGEP0020 board]]
 
−
|-
 
−
| style="text-align: right;" | '''Hardware manual'''
 
−
| style="text-align: center;" | [[Image:Hw manual.png|30x42px|link=http://www.isee.biz/component/zoo/item/igep-com-proton-hardware-reference-manual]]
 
−
| style="text-align: center;" | [[Image:Hw manual.png|30x42px|link=http://www.isee.biz/component/zoo/item/igep-com-module-hardware-reference-manual]]
 
−
| style="text-align: center;" | [[Image:Hw manual.png|30x42px|link=http://www.isee.biz/component/zoo/item/igep-electron-hardware-reference-manual-copy]]
 
−
| style="text-align: center;" | [[Image:Hw manual.png|30x42px|link=http://www.isee.biz/component/zoo/item/igepv2-hardware-reference-manual]]
 
−
| -
 
−
|}
 
−
 
 
−
 
 
−
* O: Available on board
 
−
 
 
−
* N.P.: Not populated THESE DEVICES and/or CONNECTORS ARE AVAILABLE, BUT NOT POPULATED BY DEFAULT
 
−
 
 
−
* T.P.: Test points
 
  
 
= igep.ini parameters  =
 
= igep.ini parameters  =
Line 608: Line 373:
 
| Only for base0010<br>=B
 
| Only for base0010<br>=B
 
|}
 
|}
−
 
−
= How to use GPIOs (update it)  =
 
−
 
−
== Overview  ==
 
−
 
−
This How-To is meant to be a starting point for people to learn use GPIOs for IGEP v2 devices as quickly and easily as possible. For this how-to i used [http://releases.linaro.org/platform/linaro-m/headless/final/linaro-m-headless-tar-20101108-2.tar.gz Linaro Headless] with [[Linux Kernel 2.6.35.y|Kernel 2.6.35.y]], Ubuntu 10.04 with Linaro Toolchain, IGEP v2 RC5 and [http://downloads.igep.es/labs/gpio-driver.tar.bz2 GPIO driver].
 
−
 
−
There are more ways to use GPIOs in IGEP v2, but this one is very simple.<br>
 
−
 
−
== Feedback and Contributing  ==
 
−
 
−
At any point, if you see a mistake you can contribute to this How-To.<br>
 
−
 
−
== Compile GPIO driver source code via Host<br>  ==
 
−
 
−
Download [http://downloads.igep.es/labs/gpio-driver.tar.bz2 GPIO driver] and [[Linux Kernel 2.6.35.y|Kernel 2.6.35.y]] source code. Extract files.<br>
 
−
 
−
Edit GPIO driver Makefile's:
 
−
 
−
-In files: $/app/Makefile and $/lib/Makefile, make sure that your CROSS_COMPILE path is correct.
 
−
 
−
-In file: $/modules/Makefile, make sure that your CROSS_COMPILE path is correct and&nbsp;type your Kernel 2.6.35.y path.<br>
 
−
 
−
We will use the ncurses program for set up Kernel configuration, if you don't have this program installed then you must install it with this command:
 
−
<pre>sudo apt-get install ncurses-dev
 
−
</pre>
 
−
-Go to kernel path and type:
 
−
<pre>make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- igep00x0_defconfig
 
−
</pre>
 
−
Exit Linux Kernel Configuration an return to Bash. Type:
 
−
<pre>make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_prepare
 
−
</pre>
 
−
File $/include/generated/autoconf.h was created
 
−
 
−
Finally compile GPIO driver, go to main Makefile path and compile all source code using make command.
 
−
 
−
Send binaries created from Host to Igep v2. <br>
 
−
 
−
== Install binaries via IGEP<br>  ==
 
−
 
−
Log with root user to install binaries.
 
−
 
−
=== Install module  ===
 
−
 
−
Go to:$/modules and insert user-gpio-drv.ko into linux kernel with the following command:
 
−
<pre>insmod user-gpio-drv.ko
 
−
</pre>
 
−
Check that user-gpio-drv.ko is currently loaded with the following command:
 
−
<pre>lsmod</pre>
 
−
The result will be similar at that: <br>
 
−
<pre>root@localhost:~/gpio-driver/module# lsmod
 
−
Module                  Size  Used by
 
−
user_gpio_drv          1639  0
 
−
omap_wdt                3411  0
 
−
spidev                  4198  0
 
−
iommu                  8558  0
 
−
rtc_twl                4411  0
 
−
rtc_core              11187  1 rtc_twl
 
−
twl4030_keypad          2970  0
 
−
</pre>
 
−
The module is loaded until system halt.
 
−
 
−
=== Install shared library  ===
 
−
 
−
Go to:$/lib. libgpio.so is here.
 
−
 
−
If a program is linked with shared libraries, Kernel seek in specific paths when program is executed. Now is necessary link the libgpio.so path to the environment variable LD_LIBRARY_PATH, use the following command:<br>
 
−
<pre>export LD_LIBRARY_PATH=/root/gpio-driver/lib/
 
−
</pre>
 
−
Check that libgpio.so is linked correctly. Go to:$/gpio-driver/app, gpio program is here. Type next command:
 
−
<pre>ldd gpio
 
−
</pre>
 
−
ldd command, print shared library dependencies. The result will be similar at that:
 
−
<pre>root@localhost:~/gpio-driver/app# ldd gpio
 
−
libgpio.so =&gt; /root/gpio-driver/lib/libgpio.so (0x40197000)
 
−
libc.so.6 =&gt; /lib/libc.so.6 (0x401a0000)
 
−
/lib/ld-linux.so.3 (0x4008a000)
 
−
</pre>
 
−
The shared library is linked until system halt. Now you can execute gpio example program.
 
−
 
−
== Testing driver  ==
 
−
 
−
To make sure than driver works well, make the next test. I used GPIO_136(sdmmc2_dat4) and GPIO_137(sdmmc2_dat5) because IGEP v2 RC5(without WIFI) don't use them by default: <br>
 
−
 
−
'''NOTE:''' For more information visit this [[Mux configuration|page]] (under construction). <br>
 
−
 
−
=== Configure Mux  ===
 
−
 
−
Go to:/sys/kernel/debug/omap_mux, and change this mux configuration:
 
−
<pre>echo 0x104&gt;sdmmc2_dat4
 
−
echo 0x104&gt;sdmmc2_dat5
 
−
</pre>
 
−
Use cat command to check it:<br>
 
−
<pre>cat sdmmc2_dat4
 
−
cat sdmmc2_dat5
 
−
</pre>
 
−
The result will be similar at that:
 
−
<pre>root@localhost:/sys/kernel/debug/omap_mux# cat sdmmc2_dat4
 
−
name: sdmmc2_dat4.gpio_136 (0x48002164/0x134 = 0x0104), b ae4, t NA
 
−
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE4
 
−
signals: sdmmc2_dat4 | sdmmc2_dir_dat0 | NA | sdmmc3_dat0 | gpio_136 | NA | NA | safe_mode
 
−
</pre>
 
−
and
 
−
<pre>root@localhost:/sys/kernel/debug/omap_mux# cat sdmmc2_dat5
 
−
name: sdmmc2_dat5.gpio_137 (0x48002166/0x136 = 0x0104), b ah3, t NA
 
−
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE4
 
−
signals: sdmmc2_dat5 | sdmmc2_dir_dat1 | cam_global_reset | sdmmc3_dat1 | gpio_137 | hsusb3_tll_stp | mm3_rxdp | safe_mode
 
−
</pre>
 
−
Note: OMAP_PIN_INPUT=Input/Output pin and OMAP_PIN_OUTPUT=Output pin, for Read/Write test you need the first one. GPIO is configured in mode 4.<br>
 
−
 
−
=== Read/Write test  ===
 
−
 
−
Link GPIO_136 and GPIO_137 with a wire, these pins are located in J990 connector with numbers 7 and 9. I use the next connector to join them:<br>
 
−
 
−
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
 
−
|-
 
−
| [[Image:Connector used readwrite test.JPG|center|350x230px]]
 
−
|
 
−
[[Image:All connected readwrite test.JPG|center|350x230px]]
 
−
 
−
|}
 
−
 
−
<br>
 
−
 
−
Now type next code:
 
−
<pre>root@localhost:~/gpio-driver/app# ./gpio input 136
 
−
root@localhost:~/gpio-driver/app# ./gpio output 137 0
 
−
root@localhost:~/gpio-driver/app# ./gpio get 136   
 
−
0
 
−
root@localhost:~/gpio-driver/app# ./gpio output 137 1
 
−
root@localhost:~/gpio-driver/app# ./gpio get 136   
 
−
1
 
−
root@localhost:~/gpio-driver/app#
 
−
</pre>
 
−
The results (CMOS Voltages: 0V-1V8):
 
−
 
−
{| align="center" cellspacing="1" cellpadding="1" border="1" width="200"
 
−
|-
 
−
| [[Image:GPIO value0 readwrite test.JPG|center|350x230px]]
 
−
|
 
−
[[Image:GPIO value1 readwrite test.JPG|center|350x230px]]
 
−
 
−
|}
 
−
 
−
<br> The code above shows that driver works properly, GPIO_136 is configured like input and GPIO_137 is configured like output with value 0, when read GPIO_136 the result is 0. To make sure that works well, configure GPIO_137 with value 1, now GPIO_136 reads 1. <br> This driver have more options like IRQ, but is not explained here.
 
−
 
−
[[Category:USB]] [[Category:How_to_forge]] [[Category:GPIO]] [[Category:UART]] [[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
Retrieved from "http://labs.isee.biz/index.php?title=User:Pau_pajuelo&oldid=10302"