4,199
edits
Changes
m
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 SDK SOFTWARE USER 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 SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") *[http://isee.biz/products/processor-boards/igep-com-module IGEP COM MODULE] and [http://isee.biz/products/expansion-boards/product-igep-new-york IGEP NEW YORK]<br> *SPI example program '''(link program)''' *MicroSD Card (at least 2Gbytes)
== How Works =='''G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)'''
{| 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 <mmc> --image demo-imagerpm -satoi libmad0-igep00x00.tar*.bz2 --machine igep0030 rpm
where <mmc> - 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 COM MODULE support*. rpm
'''NOTE:''' Use the following tutorial '''(upgrade it)''' to connect via Ethernet Gadget with IGEP COM MODULE - gst-launch filesrc location=sample.mp3 ! mad ! volume volume=0.25 ! alsasink
'''"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 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
'''.modalias = "spidev",Error:'''
'''//0:00:00.modalias = "lis3lv02d_spi"084839071 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header,''' unprintable FOURCC
0:00:00.bus_num = -EINVAL085052695 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
0:00:00.chip_select = -EINVAL, 085540976 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id .ra4
0:00:00.max_speed_hz = 1*1000*1000085693564 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
0:00:00.irq = -EINVAL085815634 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
0:00:00.mode = SPI_MODE_0, 085907187 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id RaTC
'''//.platform_data = &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
struct spi_board_info *spi = &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>
if ((gpio_request(irq, "LIS3LV02D IRQ") gst-launch --gst-debug-level=3 filesrc location=sample.aac ! faad ! volume volume= 0) .10 ! alsasink
&& ==== DM3730: Decode an WMA audio file (gpio_direction_input(irqOK) == 0)) ==
gpio_export(irq, 0); <pre>bitbake gst-ffmpeg</pre>
else { <pre>gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink </pre>
pr_err=== DM3730: Decode an OGG audio file ("IGEP: Could not obtain gpio LIS3LV02D IRQ\n"OK); ===
return; '''Into repositories (base plugins):'''
} http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
spigst->bus_num launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume= bus_num; 0.25 ! alsasink
spi->chip_select = cs; = BASE0033 CONNECTOR SUMMARY TABLE==
spi->irq = OMAP_GPIO_IRQ(irq), = Configure a static IP using the same private network range ==
spi_register_board_info(&lis3lv02d_spi_board_info, 1); '''under construction'''
} IGEP Firmware Yocto uses the following Ethernet network configuration (IP addresses)
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
mux_partition = omap_mux_get("core"Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration);
/* Mux initialitzation for ilms0015 */ = igep.ini parameters =
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:
/* 3-axis accelerometer */ === [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; ilms0015_lis3lv02d_init<br>disabled by default|-| serial.low | Serial number (1, 2, 174low part); | =00000001 | Numeric /* Export some GPIO */ |-| serial.high ilms0015_gpio_init| Serial number (high part); | =00000000 | Numeric|-} | revision | Revision ID |}=0003 | NumericNow spi_register_board_info has all information necessary to attach spidev driver instead lis3lv02d_spi. |-| kImageName 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. binary image name | =zImage ==== Enable ilms0015 support ====| Kernel or binary image name|-“ilms0015” is the technical name of IGEP New York. | kRdImageName | Kernel RAM Disk Image Name By default, poky| -media| Ram Disk image name|-create | MachineID | Machine ID (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]kernel ID) 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: | ;IGEPv2<br>=2344 {| border;Module<br>="1" width="500" cellspacing2717<br>;Proton<br>="1" cellpadding="1"3203
Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changes: {| borderalign="1JUSTIFY" widthcellpadding="5001" cellspacingborder="1" cellpaddingstyle="1width: 900px; height: 1095px;"
'''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 ==
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:
buddy.modem=yes
*Save changes and reboot your IGEP Device
*Power up the modem. You can power off using again these commands:
<pre>echo 0 > /sys/class/gpio/gpio140/value
echo 1 > /sys/class/gpio/gpio141/value
sleep 1
echo 0 > /sys/class/gpio/gpio141/value
</pre>
*Led D401 (near SIM card reader) is blinking now
*Once the modem is on, you can interact with it via UART 2. You can use Microcom to comunicate with it from the serial debug console:
<pre>microcom -s 115200 /dev/ttyO1</pre>
*To check the modem status use the command:<br>
<pre>at</pre>
*Answer should be OK.<br>
*Now unlock it by inserting your SIM card PIN number. Use the command:
<pre>at+cpin=<PIN></pre>
*If you correctly inserted the PIN number, the answer should be OK. If you fail more than 3 times, your SIM card will lock and you will have to insert PUK number. Now you are ready to use the GSM/GPS modem.<br>
=== Examples ===
If you successfully '''followed the the previous instructions''', you are ready to test the GSM/GPRS modem. Here are some examples:
You can check the complete list of AT commands at the Official manufacturer [http://telit.com/module/infopool/download.php?id=522 Software User Guide].
==== Test received signal strength<br> ====
Use the instruction:
<pre>at+csq</pre>
The answer should be: +CSQ: X,0, where X is the signal strenght. For example 12 is poor and 18 is good. If the answer is +CSQ:99,99 you should check your coverage or use an antenna<br>
==== Making a phone call<br> ====
Use the instruction, replace number_to_call with your number:
<pre>atd number_to_call
</pre>
Press any key to end call
'''NOTE:''' If "NO CARRIER" message appear check your coverage or use an antenna.
==== Sending a SMS<br> ====
First of all, you need to configure the SMS format type. Telit GE865 GSM/GPRS supports PDU format and Text format. We use Text format. Type the following command:
<pre>AT+CMGF=1</pre>
There are so many ways in this modem to send a message. Here you have a simple example. Use the instruction, replace destination_number with your number:
<pre>at+cmgs= destination_number
> insert here your text message
</pre>
When you are ready to send your message use Ctrl+Z to send it.
If you want to cancel or restart the message press ESC.<br>
'''NOTE:''' If "NO CARRIER" message appear check your coverage or use an antenna.<br>
'''NOTE:''' Don't use special characters in SMS text message like <`´'">.<br>
'''Know more'''<br>
Here you have the official manuals from the manufacturer's webpage:<br>
*[http://telit.com/module/infopool/download.php?id=1666 Telit GE865-QUAD Hardware User Guide]<br>
*[http://telit.com/module/infopool/download.php?id=522 Telit Modules Software User Guide]<br>
<br>
== How to use TVP5151 Video Decoder (update to kernel 37)<br> ==
=== Requirements<br> ===
*Have successfully connected the TFT Screen as explained at the [[Getting Started with IGEP0022 board#TFT_and_Touchscreen|Getting Started Guide]] or at the [http://igep.es/index.php?option=com_content&view=article&id=99&Itemid=129&dir=%2Fvar%2Fwww%2Fvhosts%2Figep.es%2Fhttpdocs%2Fdownloads%2F01-ISEE_Products%2FIGEPv2_EXPANSION%2FHW_User_Manuals&download_file=%2Fvar%2Fwww%2Fvhosts%2Figep.es%2Fhttpdocs%2Fdownloads%2F01-ISEE_Products%2FIGEPv2_EXPANSION%2FHW_User_Manuals%2FMAN-PR-IGEP.0022-001.01.HW_USER_MANUAL.pdf Official Hardware Reference Manual]<br>
*A camera or any device with PAL output video to RCA connector.<br>
<br>
----
<br>
There are two modules that you will use that are not inserted into the kernel: iommu2 (tvp5151) and isp.
You have to load these kernel modules before start:<br>
<pre>modprobe iommu2
modprobe omap3-isp
</pre>
(Note: The first load order must be the iommu2 and then the omap3-isp)<br>
----
<br>
Now, use the program media-ctl. This program is useful to configure the ISP. You can download it from [http://downloads.igep.es/files/media-ctl here]. Then you have to transfer it to your IGEP0022 (for example via SCP command).<br>
Now you have to configure the ISP and TVP5151:<br>
<pre>./media-ctl -r -l '"tvp5150 2-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'</pre>
Configure the video capture setup:<br>
<pre>./media-ctl --set-format '"tvp5150 2-005c":0 [UYVY 720x628]'
</pre>
Connect a video camera or any device with PAL output to the Composite Video RCA input connector of the IGEP0022.
Use gstreamer as live stream to capture video from your video source.<br>
Now setup the gstreamer pipeline:<br>
<pre>gst-launch-0.10 -v v4l2src device=/dev/video2 queue-size=1 ! video/x-raw-yuv,format=\(fourcc\)UYVY,width=720,height=628 ! omapfbsink</pre>
If everything was fine you will see the live video at the screen.
[[Image:TVP5151 video decoder.jpg|frame|center|514x346px]]See also: [[How to setup tvp5151 video decoder]]<br>
== How to use EEPROM ==
The IGEP0022 expansion board provides an [http://www.atmel.com/dyn/resources/prod_documents/doc5156.pdf AT24C01B] serial EEPROM memory which is connected to the OMAP via I2C.<br>
You can use easily simple reads/writes to access to the eeprom:
echo "hello world!" > /sys/devices/platform/i2c_omap.2/i2c-2/2-0050/eeprom
cat /sys/devices/platform/i2c_omap.2/i2c-2/2-0050/eeprom
Or read/write from userspace using i2c-tools:
i2cget <bus> <chip> <register>
i2cset <bus> <chip> <register> <value>
For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2:
i2cset -f -y 2 0x50 0x10 0x22
i2cget -f -y 2 0x50 0x10
See also: i2dump(8), i2cget(8) and i2cset(8) man page
== How to use CAN bus ==
a
== Handle the gpio-LED's ==
'''Basic '''
In this tutorial, we are going to use the '''4 LED's available in the board''', which probably is the most simple feature in the board, but sometimes you may want LED's to be a way of checking the status of some of your applications.
You can easily '''turn LED's on and off''' using the 'echo' instruction.
Log into IGEPv2 (for example via SSH, as shown in the previous chapter), and run the following commands to turn LED's on:
<pre>echo 1 > /sys/devices/platform/leds-gpio/leds/d240\:green/brightness
echo 1 > /sys/devices/platform/leds-gpio/leds/d240\:red/brightness
echo 1 > /sys/devices/platform/leds-gpio/leds/d440\:green/brightness
echo 1 > /sys/devices/platform/leds-gpio/leds/d440\:red/brightness
</pre>
You can turn them down using the same command and write '0' instead of '1'.
<br> '''Know more '''
IGEPv2 LED's are controlled with it's platform device at /sys/devices/platform/leds-gpio/leds/
If you want to trigger the leds you can enable this mode and select the trigger source (none by default) to: mmc0, mmc1, timer, heartbeat and default-on.<br>
To enable any of this modes you just have to change a parameter in the directory of the led you want to control. You can see all the possibilities using the instruction 'cat':<br>
<pre>$ cat /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
[none] mmc0 mmc1 timer heartbeat default-on
</pre>
In the example above, we have checked the status of the trigger in led D240:green. Mode 'none' is selected.
To change it, for example, to the ''timer'' mode you can use 'echo':
<pre>echo timer > /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
</pre>
In this case, we have set the trigger to the 'timer' mode. Now you can set the time for what the led is ON and the time it is OFF using:
<pre>echo 250 > /sys/devices/platform/leds-gpio/leds/d240\:green/delay_on
echo 750 > /sys/devices/platform/leds-gpio/leds/d240\:green/delay_off
</pre>
Now the selected led is configured with a timer consisting of 250 miliseconds ON and 750 miliseconds OFF.
<br>
== Get sound in (audio in) ==
'''Basic '''
External Audio input devices, such as a powered microphone or the audio output of a PC or MP3 player, can be connected to the via a 3.5mm jack (Audio IN).
You can record audio in with the application Arecord, for example:
arecord -t wav -c 2 -r 44100 -f S16_LE -v audio-in.wav
Following output is expected on console:
Recording WAVE 'audio-in.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Plug PCM: Hardware PCM card 0 'TWL4030' device 0 subdevice 0
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 44100
exact rate : 44100 (44100/1)
msbits : 16
buffer_size : 32768
period_size : 2048
period_time : 46439
tick_time : 7812
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 2048
xfer_align : 2048
start_threshold : 1
stop_threshold : 32768
silence_threshold: 0
silence_size : 0
boundary : 1073741824
When ever you think you want to stop recording just press CTRL+C
<br>
== Get sound out (audio out) ==
'''Basic '''
Connect an '''external output audio device''' to the 3.5mm jack Audio Out connector in IGEPv2, such as external stereo powered speakers.
The amplifiers for the headset output are disabled by default, so the first thing you'll do is enable these amplifiers with:
amixer set -D hw:0 'Headset' 0dB
amixer set -D hw:0 'HeadsetL Mixer AudioL2' on
amixer set -D hw:0 'HeadsetR Mixer AudioR2' on
Then you can easily play a *.wav sound with the application Aplay, for example:
aplay audio-in.wav
<br>
== Connect to the Serial Debug interface ==
'''Basic '''
[[Image:DSC 0177.JPG|thumb|right|550px]]
In the preinstalled software, the serial port is configured as a '''Debug interface'''.
Therefore, if you connect an external device to the serial port you will be able to see the '''Linux Kernel traces''', as the system boots.
<br> Follow these steps:
*Connect an '''AT/Everex Cable''' to the '''10-pin serial header''' on IGEPv2 and a '''[http://en.wikipedia.org/wiki/Null_modem null modem] DB9 male-male''' serial cable between the board and your host machine.
*Refer to the article: '''[[How to setup the IDC10 cable|How to setup the IDC10 cable]]''' to setup the IDC10 cable.
*You can also use a Serial port in your host machine you might need a '''USB to Serial converter''' to communicate via this port.
*Run a serial console, or any program that can interact with the serial port in your host machine, such Minicom, PuTTy (Linux, Windows), Terminal (Windows), etc.
*Refer to this extended article about '''[[Using serial debug port to communicate]]''' to setup the right configuration of your serial console.
<br> Now, as you are connected to the '''serial debug port''', you will see the system traces as the board is starting up.
Finally you will see the boot prompt asking for login.
<br> [[Image:Poky-prompt-screenshot.png|thumb|center|550px]]
<br> a
{{#lst:How to use CAN bus|IGEPv2 EXPANSION}}
<br> <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]]
→DM3730: Decode an AAC audio file (OK)
= TODO: =
'''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.
=== Custom Micro SD Card DM3730: Decode a RA or RM audio file (ERRORS)===
*eth0 − 192.168.5.1*eth0:0 − assigned via dhcp.
|-
| ; Machine configuration Mode | Boot Mode ''' | ; ;buddyLinux kernel<br>=base0010 buddy.revision=B ''' kernel '''  | ; buddy=ilms0015''' Other image (like uboot)<br>[binary image]
|}
==== Test changes [kparams] ====
|-
| root@igep00x0:/dev# lsmod Module Size Used by rfcomm 48522 0 hidp 13311 0 l2cap 49001 4 rfcomm,hidp bluetooth 67643 3 rfcomm,hidp,l2cap libertas_sdio 13887 0 libertas 99318 1 libertas_sdio option 13044 0 usb_wwan 7196 1 option usbserial 23870 2 option,usb_wwan '''spidev 4898 0 Parameter Name''' 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:Description''' 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: Default value'''Reads a word from a register. '''Write mode: '| ''Writes a word in a register. 'Comments''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). buddy | [[Image:Lis3dhxyzaxes.png|150x159px]]Enable/disable expansion board support |} ;IGEPv2 Expansion Board support<prebr>root@igep00x0:~# ./spiexampleb2 -T =igep0022 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Accelerometer TEST Values from X -64, Values from Y -15872 | ;Berlin and Values from Z -256 root@igep00x0:~# Paris Expansion Board support</prebr> The next table shows results at different positions: {| border="1" width="600" cellspacing="1" cellpaddingbase0010<br>New York Expansion<br>="1"ilms0015
|-
| Position console | ±2g scale Setup the kernel console parameters | ±4g scale =ttyO2,115200n8 | ±8g scale | ±16g scale-
|-
| [[Image:NYtopimagetest.png|center|100x100px]] earlyprintk | X = 832 Y = 1024 Z = 15680 | X = 256 Y = 128 Z = 7872 Enable early printk | X = 128 Y = 128 Z = 4032 - | X = 64 Y = 128 Z = 1280 -
|-
| [[Image:NYbotimagetest.png|center|100x100px]] mem | X = 256 Y = 704 Z = -17216 | X = 256 Y = 256 Z = -8320 Setup the Board Memory Configuration | X = 64 Y = 128 Z = -4096 430M | X = 128 Y = 128 Z = -1344
|-
| [[Image:NYtophoritzontalimagetest.png|center|100x100px]] boot_delay | X = -15872 Y = 64 Z = -320 | X = -7936 Y = 64 Z = -512 Setup the boot delay | X = -3968 Y = 128 Z = -192 0 | X = -1280 Y = 64 Z = -128
|-
| [[Image:NYbothoritzontalimagetest.png|center|100x100px]] | X = 16448 Y = 640 Z = 640 mpurate | X = 8128 Y = 192 Z = 384 Setup ARM Processor Speed | X = 4032 Y = 64 Z = 64 - | X = 1344 Y = 64 Z = 192 -
|-
| [[Image:NYtopverticalimagetest.png|center|100x100px]] loglevel | X = 896 Y = 16512 Z = -576 | X = 320 Y = 8128 Z = -128 Setup the loglevel | X = 192 Y = 4096 Z = -64 | X = 128 Y = 1344 Z = -128
|-
| [[Image:NYbotverticalimagetest.png|center|100x100px]] | X = -64 Y = -15872 Z = -256 | X = -512 Y = -7808 Z = -384 debug | X = -64 >Y = -3840 Z = -384 Enable kernel 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 SDK SOFTWARE USER 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 SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") *[http://isee.biz/products/processor-boards/igep-com-module IGEP COM MODULE] and [http://isee.biz/products/expansion-boards/product-igep-new-york IGEP NEW 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 schematic.pngfixrtc |501x600px]]Fix RTC variable |} <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. {| border="1" width="500" cellspacing="1" cellpadding="1"
|-
| nocompcache static struct spi_board_info lis3lv02d_spi_board_info __initdata = { | Configure nocompcache variable '''.modalias = "spidev",''' '''//.modalias = "lis3lv02d_spi",''' .bus_num = -EINVAL, .chip_select = -EINVAL, .max_speed_hz = 1*1000*1000, .irq = -EINVAL, .mode = SPI_MODE_0, '''//.platform_data = &lis3lv02d_pdata,''' }; inline void __init ilms0015_lis3lv02d_init(int bus_num, int cs, int irq) { struct spi_board_info *spi = &lis3lv02d_spi_board_info; if ((gpio_request(irq, "LIS3LV02D IRQ") == 0) && (gpio_direction_input(irq) == 0)) gpio_export(irq, 0); else { pr_err("IGEP: Could not obtain gpio LIS3LV02D IRQ\n"); return; } spi->bus_num = bus_num; spi->chip_select = cs; spi->irq = OMAP_GPIO_IRQ(irq), spi_register_board_info(&lis3lv02d_spi_board_info, 1); } ... void __init ilms0015_init(void) { mux_partition | = omap_mux_get("core"); /* Mux initialitzation for ilms0015 */ omap_mux_write_array(mux_partition, ilms0015_mux); /* 3-axis accelerometer */ ilms0015_lis3lv02d_init(1, 2, 174); /* Export some GPIO */ 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: {| border="1" width="500" cellspacing="1" cellpadding="1"
|-
| ; Machine omapfb.mode | Configure frame bugger configuration ''' ;buddy| =base0010 buddy.revision=B ''' dvi:hd720-16@50 ''' | buddy=ilms0015''' |} Other configuration<br>=== Test changes === Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changesdvi: {| border="1" width="500" cellspacing="1" cellpadding="1"1280x720MR-16@60
|-
| root@igep00x0:/dev# lsmod Module Size Used by rfcomm 48522 0 hidp 13311 0 l2cap 49001 4 rfcomm,hidp bluetooth 67643 3 rfcomm,hidp,l2cap libertas_sdio 13887 0 libertas 99318 1 libertas_sdio option 13044 0 usb_wwan 7196 1 option usbserial 23870 2 option,usb_wwan '''spidev 4898 0 ''' root@igep00x0:/dev# ls /dev/spidev1.2 /dev/spidev1.2 vram |} “spidev1.2”: refers at McSPI1 bus 2. Now we can communicate Configure Video RAM assigned to accelerometer using spi driver functions. every frame buffer == 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)omapfb. 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: {| border="1" width="600" cellspacing="1" cellpadding="1"
|-
| Position omapfb.debug | ±2g scale Configure frame buffer debug output | ±4g scale - | ±8g scale | ±16g scale-
|-
| [[Image:NYtopimagetestomapdss.png|center|100x100px]] debug | X = 832 Y = 1024 Z = 15680 | X = 256 Y = 128 Z = 7872 Configure DSS Video debug output | X = 128 Y = 128 Z = 4032 - | X = 64 Y = 128 Z = 1280 -
|-
| [[Image:NYbotimagetestsmsc911x.png|center|100x100px]] mac0 | X = 256 Y = 704 Z = -17216 Configure Board Ethernet Mac Address | X = 256 Y = 256 Z = -8320 0xb2,0xb0,0x14,0xb5,0xcd,0xde | X = 64 Y = 128 Z = -4096 | X = 128 Y = 128 Z = -1344 For IGEP BERLIN
|-
| [[Image:NYtophoritzontalimagetestsmsc911x.png|center|100x100px]] mac1 | X = -15872 Y = 64 Z = -320 Configure Board Ethernet Mac Address | X = -7936 Y = 64 Z = -512 0xb2,0xb0,0x14,0xb5,0xcd,0xdf | X = -3968 Y = 128 Z = -192 | X = -1280 Y = 64 Z = -128 For IGEP BERLIN (only with IGEP PROTON)
|-
| [[Image:NYbothoritzontalimagetestsmsc911x.png|center|100x100px]] mac | X = 16448 Y = 640 Z = 640 Configure Board Ethernet Mac Address | X = 8128 Y = 192 Z = 384 0xb2,0xb0,0x14,0xb5,0xcd,0xde | X = 4032 Y = 64 Z = 64 | X = 1344 Y = 64 Z = 192 For IGEPv2, IGEP PROTON, IGEP PARIS and IGEP BERLIN
|-
| [[Image:NYtopverticalimagetestubi.png|center|100x100px]] mtd | X = 896 Y = 16512 Z = -576 | X = 320 Y = 8128 Z = -128 Fot UBI FS boot | X = 192 Y = 4096 Z = -64 | X = 128 Y = 1344 Z = -128
|-
| [[Image:NYbotverticalimagetest.png|center|100x100px]] root | X = -64 Y = -15872 Z = -256 | X = -512 Y = -7808 Z = -384 Configure root directory for MMC, NFS or UBI | X = -64 >nbsp;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;For mmc memory<br> = {{Table/IGEP Technology Devicesdev/mmcblk0p2 rw rootwait |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 : *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.;For flash memory<br> *Powertrip 4.3" or [http:/=/shop.isee.bizdev/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 and composite video output peripheral (PAL or NTSC) 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> {| border="1" align="center" width="200" cellspacing="1" cellpadding="1"mtdblock2
|-
| [[Image:Igepv2expconnectoigepv2.PNG|268px]]<br> nfsroot | [[Image:Igepv2expconnectoigepv2 2.PNG|268px]]<br>For NFS boot |}- == 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 (UART1) can be used to debug system using kernel traces, getting a remote prompt, etc. <br> <br> <br> == VGA monitor == '''Basic''' {| border="1" align="right" width="363" cellspacing="1" cellpadding="1"
|-
| [[Image:Igepv2expconnecttovga.jpg|150px]] rootfstype | [[Image:Igepv2expvgaconnector.PNG|200px]]For UBI FS boot |} IGEPv2 Expansion integrates a VGA connector, the output VGA signal is equal to HDMI connector. Plug a monitor with VGA input. '''Know more''' This output is controled by ADV7125KSTZ140 Integrated Circuit. <br> <br> <br> == CAN bus == '''Basic''' [[Image:Igepv2expcanconnector.PNG|right|200px]]IGEPv2 Expansion integrates a CAN peripheral. Connect any CAN bus device or network to the CAN bus connector (J703).<br> '''Know more''' This output is controled by MICROCHIP MCP2515. J703 is a 3.5 mm pitch terminal blocks 4 Positions: - {| border="1" width="350" height="113" cellspacing="1" cellpadding="1"-
|-
| Signal Name ip | Pin #<br> For NFS boot | Description- | -
|-
| VDD_CAN init | J703:1 Assign init program | Supply Voltage (+5V DC)- | -
|-
| CANL musb_hdrc.debug | J703:2 USB debug | - | CAN Low-Level Voltage I/O
|-
| GND musb_hdrc.use_dma | J703:3 USB over network | Ground- | -
|-
| CANH libertas.libertas_debug | J703:4 Configure libertas debug | CAN High-Level Voltage I/O|} == GSM/GPRS modem == '''Basic''' {| border="1" align="right" width="200" cellspacing="1" cellpadding="1"-
|-
| [[Image:IGEP0022 Modem with antennaboard.pngei485 |200px]] Enable/disable RS485 | [[Image:Igepv2expcardreader.PNG|right ;Enable RS485<br>=yes |200px]] ;Disable RS485<br>=no
|-
| GSM-GPRS antenna (highly recommended) | SIM card readerboard.modem |} IGEPv2 Expansion integrates a GSMEnable/disable GPRS modem to make phone calls or to send SMS or to write and read data from it, etc.<br> '''Know more''' Modem chip Telit GE865 is a small GSM/GPRS Ball-Grid-Array BGA module with next main features: *Quad-band EGSM 850 / 900 / 1800 / 1900 MHz *Power consumption (typical values) | - Power off: ‹ 62 uA<br> - Idle Enable modem (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 Devicesno |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 ;Enable modem (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 UART1 (/dev/ttyO2) can be obtained through J502 DB9 connector. You can use PuTTy to get a shell prompt to IGEP: *Power up IGEPv2 *Open PuTTy. *Choose Serial line. If you are running PuTTy on Windows, the Serial line will be like (COM1 or COM2 or COM3, etc.). If you are running PuTTy on Ubuntu, the Serial line will be like (/dev/ttyS0 or /dev/ttyS1 or /dev/ttyS3, etc.). Note that if you are using a USB->Serial converter, the Serial line will be like /dev/ttyUSB0 *Configure Speed to 115200 *Select Serial Connection type *Press on Open button *You will successfully started the console. {| border="1" width="200" cellspacing="1" cellpadding="1"yes
|-
| [[Image:IGEPV2EXPCHMDB9buddy.pngrevision |250px]Enable hardware buddy revision [A or B] | [[Image:Remoteshellpromptdb9putty.jpgOnly for base0010<br>=A |250px]]Only for base0010<br>=B
|}