4,199
edits
Changes
From IGEP - ISEE Wiki
m
__NOTOC__{{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}}}}
If you have '''successfully completed the [[Getting_Started_with_BASE0010_board|getting started guide]]''' for BASE0010, you can follow this first introduction about what can you do with this board:
= How to get DVI output =This is the 2/3 chapter of IGEP BERLIN Expansion Tutorial Guide.
By default the DVI is outputs 1024 x 768 @ 60Hz, so if your monitor support this resolution you'll see the desktop when board is upWe will learn some basic tasks.
Unfortunately the capability to automatically set the display resolution to match your monitor isn't yet available. The simplest method to customize the display resolution is to set it using [[How do I edit my kernel command line | kernel command line]
The required arguments use the following pattern: omapfb.mode=<display>:<resolutionMR-bpp@refresh> omapdss.def_disp=<display> where: __TOC__
For example:
See also== 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 this reason, you should change it to adapt for HDMI standard resolution, you can [[How do I How_do_I_edit_my_kernel_command_line | edit my following kernel command linecmdline parameter]].
There are two Ethernets on the BASE0010 board which can be used, for example if your access == How to the internet is via a route you can configure one of them with following commandTelit 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|}
For second interface just change the eth0 device for eth1 buddy.modem=yes
= How to get sound out (audio out) =*Power up the modem using the next commands:
The amplifiers for the headset output are disabled by default, so the first thing you'll do is enable these amplifiers with <pre>echo 0 > /sys/class/gpio/gpio145/valueecho 1 > /sys/class/gpio/gpio163/valuesleep 1echo 0 > /sys/class/gpio/gpio163/value</pre>
amixer set -D hw:0 'Headset' 0dB amixer set -D hw:0 'HeadsetL Mixer AudioL2' on amixer set -D hw:0 'HeadsetR Mixer AudioR2' *Once the modem is on(led near power button is blinking now), you can interact with it via UART 2.
Then you You can easily play a wav sound, for example use Microcom to comunicate with it from the serial debug console:
aplay sample.wav$ microcom -s 115200 /dev/ttyO1
You can record audio in with ''From [[How to use Telit Modem]]''
arecord -== How to use to use TVP5151 Video Decoder =={{Message/Information Message|title=|message=IGEP COM MODULE AND IGEP BERLIN doesn't wav -c 2 -r 44100 -f S16_LE -v audio-support video decoder}}[[Image:Berlin rca.jpg|right|200px]]IGEP BERLIN Expansion integrates two composite video connectors to decode analog input signal.=== Configure TVP5151 ===*Plug some peripheral with video composite output inJ402 rca connector, see the image for more details.<br> *Connect a screen, for example HDMI monitor. *Refresh repositories and accept it.wav
= How to get user button =You have another example written in c.
There is one button on the BASE0010 board which can be used by the software for user interaction[[File:BERLIN_ADC. tar.gz]]
The kernel driver creates Warning: There is a device small deviation in /dev/input directoryreading values near to 1V8 due to this protection. To access The TPS65950 datasheet describes chip can support up to 2.5V at the button you will use the Linux Input Device subsystemADC input . Datasheet: http://www. In Particular evdev, which is a generic input event interfaceti. It passes the events generated in the kernel straight to the program, with timestampscom/lit/ds/symlink/tps65950. The event codes are the same on all architectures and are hardware independentpdf Under his responsibility can desolder for more accurate readings.
For example, the test program evtest ([http://beagleboard.googlecode.com/files/evtest.c evtest.c]) listens on the /dev/input/event0 file descriptor, trying == How to read any events operate USER LED's ==
evtest /dev/input/event0On BASE0010 the two leds are available via gpio 19 and 22. See the example below:
Input driver version is 1.0.0 Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100 Input device name: "gpio-keys" Supported events: Event type 0 === For D103 LED USER1(Sync) Event type 1 (Key) Event code 276 (ExtraBtn) Testing ... (interrupt to exitGPIO22): ===
If you'll press We publish the button you'll see 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
EventLED ON: time 8354.388305, type echo 1 (Key), code 276 (ExtraBtn), > /sys/class/gpio/gpio22/value 0 EventLED OFF: time 8354.388335, -------------- Report Sync ------------ Event: time 8354.573364, type 1 (Key), code 276 (ExtraBtn), echo 0 > /sys/class/gpio/gpio22/value 1 Event: time 8354.573364, -------------- Report Sync ------------
#linux-2.6 echo 19 > /Documentationsys/inputclass/input.txt gpio/export #linux-2.6 echo out>/sys/class/Documentationgpio/inputgpio19/input-programming.txtdirection
→How to Telit Modem
= Overview =
= 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=dvi omapfb.mode=1024x768MRlcd-16@6070</pre><br><br> omapdssFinally, edit file: (rootfs)/etc/X11/xorg.def_disp=dvi omapfbconf to enable default touchscreen calibration, xorg.mode=hd720-16@60conf 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>
;omapdss.def_disp= How to configure ethernet lcd-70 omapfb.mode=dvi:1280x720MR-16@60
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 IGEP BERLIN. ifconfig eth0 up udhcpc -i eth0Configure this [[How_do_I_edit_my_kernel_command_line | adding following kernel cmdline parameter]]
*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= How <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 get sound in (audio in) =insert PUK number. *Now you are ready to use the GSM/GPS modem.<br>
$ zypper ref *Install video4linux2 plugin $ zypper in gst-plugins-good-video4linux2 === 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 {| cellspacing="1" cellpadding="1" border="1" width="200"|-| [[Image:Igepv2expgstreamercapture.jpg|400px]]|}''From [[How to setup tvp5151 video decoder]]'' == How to use EEPROM ==IGEP BERLIN Expansion includes a serial EEPROM, provides 1KB of user data storage. EEPROM is connected through I2C2 of OMAP3 processor at address 0x50. The following example writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 3: $ i2cset -f -y 3 0x51 0x10 0x22 $ i2cget -f -y 3 0x51 0x10 ''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> $ ip link set can0 up type can bitrate 125000 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: can0 123 [4] aa bb cc dd Switch roles and try it again == How to use serial console ==[[Image:Berlin db9.png|right|200px]]Connect a DB9 cable between IGEP PARIS and Host PC. Open the serial on your PC using your preferred serial communications program (minicom) and configure the port as follows: * 115200* 8N1* no flow control (either software or hardware) 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 =={{#lst:How to use RS485|overview}}A detailed guide on how use UARTS can be found by following this link: [[How to use RS485]] == 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 Following output is expected on console :
Recording WAVE 'audio-in.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
boundary : 1073741824
When ever you think you want to stop recording just press CONTRLCTRL+C == Get sound out (audio out) ==Connect an external output audio device to the 3.5mm jack Audio Out connector in the board, 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 == 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://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)
=== For more information please readD103 LED USER2 (GPIO19): ===
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|device=BASE0010}}
[[Category:BASE0010]][[Category:TutorialsIGEP Technology Devices Guides]]
