(work in progress) = How to enable IGEP0022 support = The required #REDIRECT:[[How do What can I edit my kernel command line | kernel command line]] option here is buddy=igep0022 = Getting VGA output = The required [[How do I edit my kernel command line | kernel command line]] option here is omapfb.mode followed by the desired resolution, make sure to select a video mode compatible with your monitor For example: omapdss.def_disp=dvi omapfb.mode=dvi:1024x768-16@60 Note that you could connect both a VGA monitor and a DVI-D monitor and see the same image, as long as the video mode is compatible with both monitors. = Using TFT and Touchscreen = Seiko 7.0 inch WVGA (800 x RGB x 480) TFT: omapdss.def_disp=lcd-70 Powertip 4.3 inch (480 x RGB x 272) TFT: omapdss.def_disp=lcd-43 To configure the touchscreen, add "Configured Touchscreen" in "ServerLayout" section and remove "Configured Mouse" Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" # InputDevice "Configured Mouse" InputDevice "Configured Touchscreen" Option "AllowEmptyInput" "no" EndSection calibrate it yourself until you are happy with the result, for example: /etc/init.d/xserver-nodm stop TSLIB_CALIBFILE=/etc/pointercal TSLIB_TSDEVICE=/dev/input/touchscreen0 TSLIB_CONSOLEDEVICE=none ts_calibrate /etc/init.d/xserver-nodm start = Using Telit Modem = = Using TVP5151 Video Decoder = = Using EEPROM = The IGEP0022 expansion board provides an [http://www.atmel.com/dyn/resources/prod_documents/doc5156.pdf AT24C01BIGEPv2 EXPANSION] 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 = Using CAN bus = Several tools are provided by socketCAN: * candump: dump traffic on a CAN network* cansend: simple command line tool to send CAN-frames via CAN_RAW sockets* cangen: CAN frames generator for testing purpose* canplayer: send CAN frames from a file to a CAN interface /sbin/ip link set can0 up type can bitrate 125000 On the receiver side: candump can0 On the sender side: cansend can0 123#AABBCCDD cansend can0 123#R cansend can0 1F334455#1122334455667788 cansend can0 1F334455#R On the receiver side, you must see the following messages: can0 123 [4] AA BB CC DD can0 123 [0] remote request can0 1F334455 [8] 11 22 33 44 55 66 77 88 can0 1F334455 [0] remote request Switch roles and do again
