0
edits
Changes
m
__NOTOC__{{Table/IGEP Technology Devices|Tech_Family={{#lst:Template:Links|IGEP_PARIS_Tech_Family}}|Tech_ID={{#lst:Template:Links|IGEP_PARIS_Tech_ID}}|Name={{#lst:Template:Links|IGEP_PARIS_Name}}|Image={{#lst:Template:Links|IGEP_PARIS_Image}}|ISEE_MainPage={{#lst:Template:Links|IGEP_PARIS_ISEE_MainPage}}|ISEE_Hardware={{#lst:Template:Links|IGEP_PARIS_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 PARIS 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 do I edit my kernel command line]]to use EEPROM ==IGEP PARIS Expansion includes a serial EEPROM, provides 1KB of user data storage. EEPROM is connected through I2C2 of OMAP3 processor at address 0x50.
= How The following example writes the value 0x22 to configure ethernet =register 0x10 of device 0x50 on i2c bus 3:
There are two Ethernets on the BASE0010 board which can be used, for example if your access to the internet is via a route you can configure one of them with following command: $ i2cset -f -y 3 0x51 0x10 0x22 $ i2cget -f -y 3 0x51 0x10
ifconfig eth0 up udhcpc -i eth0''From [[How to use EEPROM]]''
For second interface just change the eth0 device for eth1 == How to use serial console ==
= How to get sound out [[Image:Paris db9.jpg|right|200px]]Connect a DB9 cable between IGEP PARIS and Host PC. Open the serial on your PC using your preferred serial communications program (audio outminicom) =and configure the port as follows:
The amplifiers for the headset output are disabled by default, so the first thing you'll do is enable these amplifiers with * 115200* 8N1* no flow control (either software or hardware)
amixer set -D hw:0 'Headset' 0dB amixer set -D hw:0 'HeadsetL Mixer AudioL2' on amixer set -D hw:0 'HeadsetR Mixer AudioR2' onOpen the serial port and the debug shell prompt should appear.
Then you A detailed guide on how to connect via serial debug port can easily play a wav sound, for example be found by following this link: [[Using serial debug port to communicate]]
aplay sample== How to use SW101 button ==IGEP PARIS has a button configured like GPIO.wavYou can test it using the following program:
= How to get sound in (audio in) =$ evtest /dev/input/event0
You can record audio in with 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 just Now press CONTRL+C = How to get user button = There is one button on the BASE0010 board which can be used by the software for user interaction. The kernel driver creates a device in /dev/input directory. To access to the button you will use the Linux Input Device subsystem. In Particular evdev, which is a generic input event interface. It passes the events generated in the kernel straight to the program, with timestamps. The event codes are the same on all architectures and are hardware independent. For example, the test see program evtest ([http://beagleboard.googlecode.com/files/evtest.c evtest.c]) listens on the /dev/input/event0 file descriptor, trying to read any events evtest /dev/input/event0 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 (Sync) Event type 1 (Key) Event code 276 (ExtraBtn) Testing ... (interrupt to exit) If you'll press the button you'll see Event: time 8354.388305, type 1 (Key), code 276 (ExtraBtn), value 0 Event: time 8354.388335, -------------- Report Sync ------------ Event: time 8354.573364, type 1 (Key), code 276 (ExtraBtn), value 1 Event: time 8354traces.573364, -------------- Report Sync ------------ For more information please read: #linux-2.6/Documentation/input/input.txt #linux-2.6/Documentation/input/input-programming.txt {{Template:Navigation/IGEP Technology Guides/What can I do/Ending|device=BASE0010}} [[Category:BASE0010]][[Category:TutorialsIGEP Technology Devices Guides]]
no edit summary
= Overview =
= What can I do omapdss=You must logged in the board.def_disp== How to use TFT and Touchscreen ==dvi omapfb[[Image:berlin_paris_screen_connectors.JPG|right|200px]] IGEP PARIS 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 PARIS.mode=1024x768MR-16@60However 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=hd720lcd-16@6070</pre><br><br>