4,199
edits
Changes
From IGEP - ISEE Wiki
m
__TOC__
$ <pre>echo 0 > /sys/class/gpio/gpio145/value $ echo 1 > /sys/class/gpio/gpio163/value $ sleep 1 $ echo 0 > /sys/class/gpio/gpio163/value</pre>
<pre> $ zypper ref </pre>
<pre> $ zypper in gst-plugins-good-video4linux2</pre>
<pre> $ modprobe omap3-isp</pre>
<pre> $ media-ctl -r -l '"tvp5150 3-005d":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' $ media-ctl -v --set-format '"tvp5150 3-005d":0 [UYVY 720x480]' $ media-ctl -v --set-format '"OMAP3 ISP CCDC":0 [UYVY 720x480]' $ media-ctl -v --set-format '"OMAP3 ISP CCDC":1 [UYVY 720x480]' </pre>
<pre> $ export DISPLAY=:0.0 </pre>
<pre> $ gst-launch-0.10 -v v4l2src device=/dev/video2 queue-size=8 ! video/x-raw-yuv,format=\(fourcc\)UYVY,width=720,height=480 ! ffmpegcolorspace ! autovideosink</pre>
<pre> $ i2cset -f -y 3 0x51 0x10 0x22 $ i2cget -f -y 3 0x51 0x10</pre>
/bin/$ ip link set can0 up type can bitrate 125000
→How to Telit Modem
}}
= Overview =
We will learn some basic tasks.
__TOC__
= What can I do =
By default, Seiko screen is supported in IGEP BERLIN. However open igep.ini, you can do this [[How_do_I_edit_my_kernel_command_line | checking following kernel cmdline parameter]]:
<pre>omapdss.def_disp=lcd-70</pre><br><br>
Finally, edit file: (rootfs)/etc/X11/xorg.conf to enable default touchscreen calibration, xorg.conf touchscreen and ServerLayout sections should look like this:
<pre>Section "InputDevice"
Identifier "Seiko Touchscreen"
Driver "evdev"
Option "Device" "/dev/input/touchscreen0"
# Option "Calibration" "138 3923 311 3962"
EndSection </pre>
<pre>Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default fbdev Screen 0"
InputDevice "Seiko Touchscreen"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection</pre>
== How to use DVI ==
*Power up the modem using the next commands:
*Once the modem is on (led near power button is blinking now), you can interact with it via UART 2.
*Connect a screen, for example HDMI monitor.
*Refresh repositories and accept it.
*Install video4linux2 plugin
=== Play with TVP5151 ===
*Load OMAP ISP kernel module<br>
*Configure ISP, for PAL resulution use 720x576 for NTSC resolution use 720x480:
*Export display
*Launch gstreamer
*Now you can see in your IGEP screen a result similar like this
The following example writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 3:
''From [[How to use EEPROM]]''
Now you can set up the interface (on all boards when using multiple IGEP BERLIN <span lang="en" id="result_box" class="short_text"><span title="Click for alternate translations" class="hps">connected to a CAN network simultaneously)</span></span>:<br>
If you want to receive CAN data, use:
$ candump can0
If you want to send CAN data, use:
$ cansend can0 -i 0x123 0xaa 0xbb 0xcc 0xdd
On the receiver side, you must see the following messages:
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).
Note that the board has been designed to use Line In for the audio input which means users need to add some type of pre-amp for a microphone to work or use a powered microphone. For a pre-amp for a microphone you can use MAX9812. Enable capture: $ amixer -c 0 sset 'Analog Right AUXR' cap $ amixer -c 0 sset 'Analog Left AUXL' cap You can record audio in with the application arecord, for [http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/Samples/AFsp/M1F1-int32WE-AFsp.wav example]:
$ arecord -t wav -c 2 -r 44100 -f S16_LE -v audio-in.wav
A detailed guide on how use wifi can be found by following this link: [[Using USB ethernet gadget to communicate]]
== How to read analog values (ADC) ==
IGEP BERLIN provides 2 analog inputs on J1206: Maximum allowed analog voltage is 1V8.
[[Image:BASE_BERLIN_CONNECTORS.png|right|300px]]
To protect the ADC input for higher voltages than 1V8, exist a diode protection (Z300). See diagram on the right side.
[[Image:BERLIN_ADC_SCHEMA.png|right|300px]]
To prove the lectures, you have examples codes written in phyton in the ISEE GIT.
[http://git.isee.biz/?p=pub/scm/igep_qa.git;a=blob_plain;f=igep_qa/helpers/madc.py;hb=HEAD Downlaod Python example]
[http://git.isee.biz/?p=pub/scm/igep_qa.git;a=tree;f=igep_qa/helpers;h=e0671966af9f539bdd7628e101c181d8e74dc506;hb=HEAD ->Link to GIT directory]
To read the ADC2 or ADC3 you have to modify one line of code at end of document for the channel 2 or 3.
madc = QMadc(2) or madc = QMadc(3)
You have another example written in c.
[[File:BERLIN_ADC.tar.gz]]
Warning: There is a small deviation in reading values near to 1V8 due to this protection.
The TPS65950 datasheet describes chip can support up to 2.5V at the ADC input .
Datasheet: http://www.ti.com/lit/ds/symlink/tps65950.pdf
Under his responsibility can desolder for more accurate readings.
== How to operate USER LED's ==
On BASE0010 the two leds are available via gpio 19 and 22. See the example below:
=== For D103 LED USER1(GPIO22): ===
We publish the virtual file system to configure elements of the chip via the Linux kernel
mount -t debugfs none /sys/kernel/debug/omap_mux
Set the pin as function gpio22
echo 0x104 > /sys/kernel/debug/omap_mux/etk_d8
Do gpio22 accessible
echo 22 > /sys/class/gpio/export
Configure the pin as output
echo out > /sys/class/gpio/gpio22/direction
LED ON: echo 1 > /sys/class/gpio/gpio22/value
LED OFF:echo 0 > /sys/class/gpio/gpio22/value
=== For D103 LED USER2 (GPIO19): ===
echo 19 > /sys/class/gpio/export
echo out>/sys/class/gpio/gpio19/direction
LED ON: echo 1 > /sys/class/gpio/gpio19/value
LED OFF:echo 0 > /sys/class/gpio/gpio19/value
{{Template:Navigation/IGEP Technology Guides/What can I do/Ending}}
[[Category:IGEP Technology Devices Guides]]
