|
|
| (80 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | (work in progress)
| + | #REDIRECT:[[What can I do with IGEPv2 EXPANSION]] |
| − | | |
| − | = How to enable IGEP0022 support =
| |
| − | | |
| − | Add following parameter in your kernel cmdline
| |
| − | | |
| − | buddy=igep0022
| |
| − | | |
| − | = Using VGA output =
| |
| − | | |
| − | omapdss.def_disp=dvi omapfb.mode=¿?¿?
| |
| − | | |
| − | = 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 IGEP v2 expansion board has an EEPROM memory (AT24C01B) which is connected to the OMAP via I2C.<br>
| |
| − | | |
| − | You can easily interact with it by using the following example.<br>
| |
| − | | |
| − | *First of all, open a Serial client such as Putty and configure it as explained here (missing reference).<br>
| |
| − | | |
| − | *Use 'echo' to write to the memory:<br>
| |
| − | | |
| − | In order to read or write the EEPROM you must set the right I2C bus. The EEPROM memory in the IGEP0022 uses the second I2C bus (I2C 2) of the four I2C buses that the IGEPv2 OMAP can have.<br>
| |
| − | | |
| − | echo "hello world!" > /sys/devices/platform/i2c_omap.2/i2c-2/2-0050/eeprom
| |
| − | | |
| − | *Check what you have actually wrote to the memory using 'cat':<br>
| |
| − | | |
| − | cat /sys/devices/platform/i2c_omap.2/i2c-2/2-0050/eeprom
| |
| − | | |
| − | If everything was right you will see your message from the EEPROM.<br>
| |
| − | | |
| − | = 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
| |
