4,199
edits
Changes
From IGEP - ISEE Wiki
m
__TOC__
<pre> $ microcom -s 115200 /dev/ttyO1</pre>
{{#lst:How to setup tvp5151 *Plug some peripheral with video decoder|configure}}composite output in J402 rca connector, see the image for more details.<br> *Connect a screen, for example HDMI monitor. *Refresh repositories and accept it. $ zypper ref *Install video4linux2 plugin $ zypper in gst-plugins-good-video4linux2
'''Basic''' IGEP BERLIN Expansion includes a serial EEPROM, provides 1KB of user data storage. EEPROM is connected through I2C2 of OMAP3 processor at address 0x50. {{#lstThe following example writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 3:How to use EEPROM|berlin}}'''Know more''' {{#lst:How to use EEPROM|know_more}} $ i2cset -f -y 3 0x51 0x10 0x22 $ i2cget -f -y 3 0x51 0x10
/bin/$ ip link set can0 up type can bitrate 125000
Once you connect DV9 [[Image:Berlin db9.png|right|200px]]Connect a DB9 cable between IGEP BERLIN PARIS and Host PC. Open the serial on your PC using your preferred serial communications program (minicom) and configure the port as follows:
'''under construction'''{{#lst:How to use RS485|overview}}A detailed guide on how use UARTS can be found by following this link: [[How to use RS485]]
{{Template== How to use the USB OTG ==[[Image:Berlin usbs.png|right|200px]]In order to act in host mode and add some peripherals like keyboard, mouse or pendrives you require a special cable that grounds the ID pin. Since the OTG port only provides 100mA of power a USB hub is recommended. Though a common USB Standard-A to Mini-B type cable the port acts as a device. In this mode you can connect to the board using the USB Ethernet Gadget. Use this cable between your computer and the target board and connect with: $ ssh root@192.168.7.1 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:Navigation/IGEP Technology Guides/What can I dogit.isee.biz/?p=pub/scm/Ending}} {{Tableigep_qa.git;a=tree;f=igep_qa/IGEP Technology Deviceshelpers;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. |Tech_Family madc = QMadc(2) or madc ={{#lstQMadc(3) You have another example written in c. [[File:TemplateBERLIN_ADC.tar.gz]] Warning:Links|IGEP_BERLIN_Tech_Family}}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 . |Tech_ID={{#lst Datasheet:Templatehttp:Links|IGEP_BERLIN_Tech_ID}}//www.ti.com/lit/ds/symlink/tps65950.pdf Under his responsibility can desolder for more accurate readings. |Name={{#lst= How to operate USER LED's == On BASE0010 the two leds are available via gpio 19 and 22. See the example below:Template === For D103 LED USER1(GPIO22):Links|IGEP_BERLIN_Name}}=== We publish the virtual file system to configure elements of the chip via the Linux kernel mount -t debugfs none /sys/kernel/debug/omap_muxSet the pin as function gpio22 echo 0x104 > /sys/kernel/debug/omap_mux/etk_d8Do gpio22 accessible echo 22 > /sys/class/gpio/exportConfigure the pin as output echo out > /sys/class/gpio/gpio22/direction |Image={{#lst LED ON:Templateecho 1 > /sys/class/gpio/gpio22/value LED OFF:Links|IGEP_BERLIN_Image}}echo 0 > /sys/class/gpio/gpio22/value |ISEE_MainPage={{#lst== For D103 LED USER2 (GPIO19): === echo 19 > /sys/class/gpio/export echo out>/sys/class/gpio/gpio19/direction LED ON:Templateecho 1 > /sys/class/gpio/gpio19/value LED OFF:Links|IGEP_BERLIN_ISEE_MainPage}}echo 0 > /sys/class/gpio/gpio19/value |ISEE_Hardware={{#lst:Template:Links|IGEP_BERLIN_ISEE_Hardware}}Navigation/IGEP Technology Guides/What can I do/Ending}}
→How to Telit Modem
}}
= Overview =
We will learn some basic tasks.
__TOC__
= What can I do =
== How to use TFT and Touchscreen ==
[[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.
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 ==
[[Image:Berlin hdmi.png|right|200px]] IGEP BERLIN has a '''HDMI connector''' with a '''DVI-D interface'''. IGEP Firmware configures video output with touch screen resolution. For that this reason, you should change this configuration parameter it to adapt resolution for HDMI outputstandard resolution, you can [[How_do_I_edit_my_kernel_command_line | edit following kernel cmdline parameter]].
;omapdss.def_disp=lcd-70
== How to Telit Modem ==
{| 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. Telit modem is not supported by default in IGEPv2 Expansion and IGEP BerlinBERLIN. Configure this [[How_do_I_edit_my_kernel_command_line | adding following kernel cmdline parameter]]
buddy.modem=yes
*Power up the modem using the next commands:
<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>
*Once the modem is on (led near power button is blinking now), you can interact with it via UART 2.
You can use Microcom to comunicate with it from the serial debug console:
*To check the modem status use the command:<br>
<pre>at</pre>
== How to use to use TVP5151 Video Decoder ==
{{Message/Information Message|title=|message=IGEP COM MODULE AND IGEP BERLIN doesn't support video decoder}}
[[Image:Berlin rca.jpg|right|200px]]IGEP BERLIN Expansion integrates two composite video connectors to decode analog input signal.
=== Configure TVP5151 ===
=== Play with TVP5151 ===
*Load OMAP ISP kernel module<br> $ modprobe omap3-isp *Configure ISP, for PAL resulution use 720x576 for NTSC resolution use 720x480: $ 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]' *Export display $ export DISPLAY=:0.0 *Launch gstreamer $ 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 *Now you can see in your IGEP screen a result similar like this {{#lst| cellspacing="1" cellpadding="1" border="1" width="200"|-| [[Image:How to setup tvp5151 video decoderIgepv2expgstreamercapture.jpg|400px]]|playberlin}}
''From [[How to setup tvp5151 video decoder]]''
== How to use EEPROM ==
''From [[How to use EEPROM]]''
== How to use CAN Bus ==
[[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).
You have to connect the two boards like this:<br>
IGEP BERLIN 1 IGEP BERLIN 2
.--- .---
| 1 |------------------| 1 | CANH : CAN High-Level Voltage I/O | 2 |------------------| 2 | CANL: CAN Low-Level Voltage I/O | 3 |------------------| 3 | GND : Ground
| 4 |-X X-| 4 |
| 5 |-X X-| 5 |
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:
== How to use serial console ==
* 115200
Open the serial port and the debug shell prompt should appear.
A detailed guide on how to connect via serial debug port can be found by following this link: [[Using serial debug port to communicate]]
== How to use RS-485 ==
== Get sound in (audio in) ==
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
$ aplay audio-in.wav
[[Category:IGEP Technology Devices Guides]]
