4,199
edits
Changes
m
Update peripheral Categorize new tutorials
Categorize new tutorials How to manage the kernel modules on Linux
Upgrade ethernet gadget tutorial for new IGEP firmware and VM How do I edit my kernel command line
Finish tutorials below == AUDIO DSP-ARM==
NOTES: Qt, Codeblocks and Eclipse are linked to main page===Included (IGEP GST DSP): ==='''AACHEDEC -> DEC AACHE (OK)'''
Eclipse http://download.wavetlan.com/SVV/Media/HTTP/FAAC-> How to develop under Eclipse (copy manual) (refers at beginning VM and option to install Eclipse(under construction)) HE-AAC.aac
Qt gst-> How to develop under Qt (refers at begginin VM and option to install Qt (under construction)) launch --gst-debug-level=2 filesrc location=sampleaache.m4a ! TIAuddec1 codecName=aachedec engineName=codecServer ! volume volume=0.25 ! alsasink sync=false
Codeblocks (do it) outofthebox->ok
Adapt IGEPv2 to IGEPv2 Expansion- Followed README file from ISEE - IGEP DSP - GST + DMAI Support Package 3.40.00
= How to use SPI (prove with new firmware, under construction) =http://www.stephaniequinn.com/Music/Canon.mp3
This How-To is meant to be a starting point for people to learn use SPI for IGEP devices as quickly and easily as possible. In this how-to, we run an example program that reads and writes registers from 3-axis accelerometer ([http://www.st.com/internet/analog/product/250725.jsp LIS3DH]) included on the board IGEP New York. <br> '''Random fatal bit error'''
== Requirements =='''mp3-plugin doesn't resolve the error'''
There are some requisites to follow this guide: ----
*[http://isee.biz/component/zoo/item/igep'''G711DEC -virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")<br> *[http://isee.biz/component/zoo/item/igep-firmware-yocto-1-2 IGEP Firmware]: follow the IGEP SDK SOFTWARE USER MANUAL DEC PCM uLAW (chapter 6.1 "Create IGEP firmware bootable micro-sd card"speech) *[http://isee.biz/products/processor-boards/igep-com-module IGEP COM MODULE] and [http://isee.biz/products/expansion-boards/product-igep-new-york IGEP NEW YORK]<br> *SPI example program '''(link programNOT TESTED)''' *MicroSD Card (at least 2Gbytes)
== How Works =='''G711ENC -> ENC PCM uLAW (speech) (NOT TESTED)'''
{| cellspacing="1" cellpadding="1" borderDM3730="1" width="200"|-| [[Image:Spi linux schematic.png|501x600px]]|}
<br> More information about Linux Kernel SPI at=== DM3730: Decode a MP3 file (OK) (ADDED TO REPOSISTORIES)===
*[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spi-summary;h=4884cb33845d7629987f60610eeedb863561006e;hb=refs/heads/linux-2.6.37.y SPI Overview]'''under contruction'''
*[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev;h=ed2da5e5b28a4490a3b03787b02df66d083692be;hb=refs/heads/linux-2.6.37.y SPIDEV]'''does not have an accelerated audio decoder element'''
== Prepare Micro SD Card ==- Compiled gst-plugins-ugly using yocto tools
=== Generate Micro SD Card ===- rpm -igst-plugins-ugly-0.*.rpm
Open a terminal and use the following steps to download and generate a Micro SD card. <pre>wget http://downloads.isee.biz/denzil/binary/igep_firmware-yocto-1.2.1-1.tar.bz2 tar jxf igep_firmwarerpm -yoctoi libmad0-*.tar0.bz2cd igep_firmware-yocto-* </pre> Insert a SD-Card media and use the igep-media-create script to copy the firmware. rpm
./igep-mediarpm -create i gst-–mmc <mmc> plugins-ugly-image demomad-image-sato-igep00x00.tar*.bz2 --machine igep0030 rpm
where <mmc> - is the SDgst-Card device of your computerlaunch filesrc location=sample. For example, assuming the SD-card device takes '/dev/sdb' type: <pre>./igep-media-create --mmc /dev/sdb --machine igep0030 --image demo-image-sato-igep00x0.tar.bz2 </pre> This should give you a bootable SD-card with IGEP COM MODULE supportmp3 ! mad ! volume volume=0. 25 ! alsasink
'''NOTE=== DM3730:''' Use the following tutorial '''Decode a RA or RM audio file (upgrade itERRORS)''' to connect via Ethernet Gadget with IGEP COM MODULE ===
'''"Include clone git commands"'''http://www.superluminal.com/andalib/ra/listen.ra
==== Modify Linux Kernel Sources to attach Spidev to SPI driver ====gst-plugins-ugly-rmdemux-0.10.19-r1.armv7a.rpm
To read accelerometer registers from spidev, we need to attach spidev driver to spi driver at start uplibgstsdp-0. So it is necessary to modify spi_board10-0-0. 10.36-r3.armv7a.rpm:libgstsdp-0.10-0 libgstsdp-0.10.so.0
Go to $(Kernel path)/arch/arm/machlibgstrtsp-omap2/exp0.10-0-0.10.36-r3.armv7a.rpm:libgstrtsp-0.10-ilms00150 libgstrtsp-0.10.c and edit the next fields in bold wordsso. 0
{| cellspacing="1" cellpadding="1" border="1" width="500"|-| static struct spi_board_info lis3lv02d_spi_board_info __initdata = { '''Error:'''
'''0:00:00.modalias = "spidev"084839071 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header,''' unprintable FOURCC
'''//0:00:00.modalias = "lis3lv02d_spi"085052695 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header,''' unprintable FOURCC
0:00:00.bus_num = -EINVAL, 085540976 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id .ra4
0:00:00.chip_select = -EINVAL085693564 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
0:00:00.max_speed_hz = 1*1000*1000085815634 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
0:00:00.irq = -EINVAL, 085907187 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<rmdemux0> Unknown object_id RaTC
.mode = SPI_MODE_0, == DM3730: Decode an AAC audio file (OK)===
EXTRA_OECONF += "--disable-examples --disable-experimental --disable-sdl --disable-cdaudio --disable-directfb \ --with-plugins=musicbrainz,wavpack,ivorbis,mpegvideoparse,'''//.platform_data = &lis3lv02d_pdata,faad2''' --disable-vdpau --disable-apexsink \ --disable-orc"Install:
};
inline void __init ilms0015_lis3lv02d_init(int bus_num, int cs, int irq) faad2-2.7-r2.armv7a.rpmlibfaad2-2.7-r2.armv7a.rpmgst-plugins-bad-faad-0.10.23-r2.armv7a.rpm
{ '''maybe there are necessary more packages, compare actual gst-bad-recipe and add changes. Necessary add faad2 recipe'''<pre>bitbake faad2 gst-plugins-bad</pre><pre> rpm -i faad2-2.7-r2.armv7a.rpmrpm -i libfaad2-2.7-r2.armv7a.rpmrpm -i gst-plugins-bad-faad-0.10.23-r2.1.armv7a.rpm </pre>
struct spi_board_info *spi gst-launch --gst-debug-level= &lis3lv02d_spi_board_info; 3 filesrc location=sample.aac ! faad ! volume volume=0.10 ! alsasink
if ==== DM3730: Decode an WMA audio file ((gpio_request(irq, "LIS3LV02D IRQ"OK) == 0) ==
&& (gpio_direction_input(irq) == 0)) <pre>bitbake gst-ffmpeg</pre>
gpio_export(irq, <pre>gst-launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0); .25 ! alsasink </pre>
else { === DM3730: Decode an OGG audio file (OK)===
pr_err'''Into repositories ("IGEPbase plugins): Could not obtain gpio LIS3LV02D IRQ\n"); '''
return; http://upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
} gst-launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume=0.25 ! alsasink
spi->bus_num = bus_num; = BASE0033 CONNECTOR SUMMARY TABLE==
spi->chip_select = cs; = Configure a static IP using the same private network range ==
spi->irq = OMAP_GPIO_IRQ(irq), '''under construction'''
spi_register_board_infoIGEP Firmware Yocto uses the following Ethernet network configuration (&lis3lv02d_spi_board_info, 1IP addresses);
} *eth0 − 192.168.5.1*eth0:0 − assigned via dhcp.
void __init ilms0015_init(void) But some scenarios this network configuration is not useful, for example: if you use a non-Linux operating system, connect to two IP private range interfaces is not simple. This How-to can be useful to
{ (Make diagram one: IGEP and Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration)
mux_partition = omap_mux_get("core"); igep.ini parameters =
/* Mux initialitzation for ilms0015 */ The kernel command line syntax is name=value1. These next parameters are supported in igep.ini since IGEP-X_Loader 2.4.0-2:
omap_mux_write_array(mux_partition, ilms0015_mux); /* 3-axis accelerometer */ ilms0015_lis3lv02d_init(1, 2, 174); /* Export some GPIO */ ilms0015_gpio_init(); } === [kernel] ===
Now spi_register_board_info has all information necessary to attach spidev driver instead lis3lv02d_spi. === [kparams] ===
Once we edit code, compile your modified Kernel, you can follow [http://labs.isee.biz/index.php/Linux_Kernel_2.6.37.y#Build_kernel_from_sources this tutorial] for this purpose. {| align="JUSTIFY" cellpadding="1" border="1" style= "width: 900px; height: 1095px;"|-| '''Parameter Name''' | '''Description''' | '''Default value''' | '''Comments'''|-| buddy | Enable ilms0015 /disable expansion board support | ;IGEPv2 Expansion Board support <br>=igep0022 | ;Berlin and Paris Expansion Board support<br>=base0010<br>New York Expansion<br>=ilms0015|-| console | Setup the kernel console parameters | =ttyO2,115200n8 | -“ilms0015” is the technical name of IGEP New York. |-| earlyprintk | Enable early printk By default, poky| -media| -create (See: [http://labs.isee.biz/index.php/How_to_create_a_SD|-card_with_the_latest_software_image Poky firmware with Kernel 2.6.37.y]) configured as igep0030, gives support only for IGEP Expansions Paris and Berlin. We need to configure igep.ini and gives support to IGEP New York: | mem | Setup the Board Memory Configuration {| cellspacing="1" cellpadding430M | -|-| boot_delay | Setup the boot delay | ="1" border="1" width="500"0 | -|-| mpurate | Setup ARM Processor Speed | - | -
<br>
== Connect an Ethernet Network cable ==
''' Basic '''
Plug an '''Ethernet cable''' between IGEPv2 and your client machine (or any other network device with ethernet connectivity).
''' Know more '''
IGEPv2 comes with one 10/100BASE-TX Ethernet ports.
In the following chapters we will use ethernet to access IGEPv2 with IP configuration, send files, etc.
== Connect USB devices (keyboard and mouse) ==
''' Basic '''
Connect a USB hub to the USB type-A connector (USB Host) in IGEPv2.
Then plug a USB keyboard and USB mouse to the USB hub.
''' Know more '''
Only USB 2.0 devices will work in IGEPv2, so if you connect any USB mouse 1.0 into the USB host connector without using a USB hub 2.0, it will not work.
== Power up IGEPv2 (5V DC) ==
''' Basic '''
Once you have connected the peripherals '''you can apply power''' to your IGEPv2 (5V DCC).
''' Know more '''
'' Led's sequence ''
When you power up your board, you will also see how two red LED's light up while the system boots (the sequence will be different based on software version). After a few seconds, there is a fixed green led on.
'' Boot priority ''
IGEPv2 can boot from many other devices (listed by priority):
# from USB
# from UART3
# from a MMC/MicroSD card
# from OneNAND memory
As we haven't set any other boot device rather than the oneNAND (the IGEPv2 flash memory) the system boots from it.
But, for example, if as '''the MicroSD card has an upper priority than the flash''', if you plug a MicroSD card into IGEPv2 (with the right configuration on it), it will boot from the MicroSD card.
== Test the Demo software distribution ==
''' Basic '''
When IGEPv2 powers up, the desktop of the preinstalled software will appear on the screen.
You can use the mouse and the keyboard to test the demo applications.
[[Image:Poky-screenshot.png|thumb|500px|center|Screenshot of the Desktop of the pre-installed software]]
''' Know more '''
All IGEP Processor Boards, including IGEPv2, have a pre-installed software in its flash memory which consists of a '''minimal Linux-based distribution''' with a lite X Window System and GNOME Mobile based applications created with '''Poky Platform Builder'''.
In the next chapter of this tutorial guide, we will learn how to update the pre-installed software of your board.
== Log into IGEPv2 via Ethernet interface ==
'''Basic'''
You can log into IGEPv2 via many interfaces, such Serial, Wifi, USB-Ethernet Gadget, etc.
In this tutorial we are going to connect to the board via its Ethernet interface.
By default, all IGEP Processor boards have a '''static IP in their Ethernet interface which is 192.168.5.1'''
First of all, adjust the IP of your PC in order to be in the right subnet of IGEPv2, for example: 192.168.5.10
<br> ''Linux: ''
If you are running Linux in your PC, open a Terminal session and set the IP of the Ethernet interface in which IGEPv2 is connected (for example eth0):
Run the following commands:
sudo ifconfig eth0 192.168.5.10 up
<br> ''Windows: ''
If you are running Windows in your PC, depending of your OS version and your configuration the steps might be slightly different:
#Click the '''Start button''' and select the '''Control Panel'''
#Go to '''Network configuration'''
#Right click the interface where IGEPv2 is connected (for example: Local Network) and select '''Propierties'''
#Select the '''TCP/IP Internet Protocol''' configuration and click the '''Propierties button'''
#Set a static IP (192.168.5.10) and 255.255.255.0 as network submask
#Close all the dialogs
<br> Now you are ready to log into IGEPv2 via its Ethernet interface. You just need a program with a SSH client.
In this tutorial we are going to use Putty, as it is a multi-platform program.
You can download it from its official page at:
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Install and run Putty. It will look like this:
[[Image:Putty ssh.png|center]]
Follow these steps to connect to IGEPv2:
#Select the '''SSH''' at connection type.
#Insert the '''IP address of the target''' (IGEPv2 default IP: 192.168.5.1)
#Ensure that the port is set to '''22''', the default for SSH communications.
#Finally, press the '''Open button''' to start the SSH session.
If everything goes right, you will be able to access to an IGEPv2 console from your PC via Ethernet.
To login IGEPv2 use:
user:root
password: (no password for this user: press return)
<br> '''Know more '''
In the pre-installed software, the default configuration for all the network interfaces is:
*eth0 - 192.168.5.1
*eth0:0 - via dhcp
*wlan0 - 192.168.6.1
*usb0 - 192.168.7.1
<br> By default, the IP of the Ethernet interface is 192.168.5.1
Once you are logged in, you can see which interfaces are up in IGEPv2.
In the SSH console, run:
ifconfig
It will list all the active network interfaces.
If you want to change, for example, ''eth0'' you can use the following commands (if you do it now, it will close the SSH session, as it will change the Ethernet IP):
ifconfig eth0 < new IP >
In order to make permanent changes (save the configuration upon next start), you will have to edit the /etc/network/interfaces file in your IGEPv2.
<br> {{Navigation/IGEP Technology Guides/Getting Started/Ending
|Next_Step={{#lst:Template:Links|IGEPv2_EXPANSION_Community_Guides_2}}
}}
{{Table/IGEP Technology Devices
|Tech_Family={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_Family}}
|Tech_ID={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_ID}}
|Name={{#lst:Template:Links|IGEPv2_EXPANSION_Name}}
|Image={{#lst:Template:Links|IGEPv2_EXPANSION_Image}}
|ISEE_MainPage={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_MainPage}}
|ISEE_Hardware={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_Hardware}}
}}
[[Category:IGEP_Technology_Devices_Guides]]
→DM3730: Decode an AAC audio file (OK)
= TODO: =
----
'''MP3DEC -> DEC MP3 (AUDIO ERRORS)'''
gst-launch --gst-debug-level=2 filesrc location= Overview Canon.mp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0.25 ! alsasink sync==false
===Not included (IGEP GST DSP):==='''LIS3DH accelerometer:ACCLCDEC -> DEC AACLE (NOT TESTED)''' It is the accelerometer mounted in IGEP New York.
'''Omap3 SPI Peripheral:AACLDDEC -> DEC AACLD (NOT TESTED)''' It is the hardware used to communicated with accelerometer and other SPI devices.
'''Omap2_mcspi:WMA9 -> DEC WMA9 (COMPILING ISSUES)''' It is a bus driver than controls Omap3 SPI Peripheral.
'''Spi:ACCLCENC -> ENC AACLE (NOT TESTED)''' It is a protocol driver that defines functions and strucs used in SPI bus.
'''Spidev:ACCHEENC -> ENC AACHE (NOT TESTED)''' It is a device driver that export spi driver functionalities to userspace.
'''Lis3lv02d_spi:AACLDENC -> ENC AACLD (NOT TESTED)''' SPI glue layer for lis3lv02d
'''Lis31v02d:WMA8 -> ENC WMA8 (NOT TESTED)''' Device driver for LIS3DH accelerometer.
'''Exp_ilms0015:Problems adding codecs into igep-gst-dsp''' It is a startup program for IGEP New York. It attach lis31v02d with Spi driver.
gst-launch --gst-debug-level=3 filesrc location=sample.ra ! rmdemux ! volume volume= Custom Micro SD Card ===0.25 ! alsasink
This Ethernet network configuration is really useful when you work using a Linux operating system like IGEP SDK Virtual Machine..Because you use eth0 device to communicate easily with your board and eth0:0 device to get Internet acces using dhcp protocol.
{| align="JUSTIFY" cellpadding="1" border="1" style="width: 900px; height: 240px;"
|-
| '''Parameter Name'''
| '''Description'''
| '''Default value'''
| '''Comments'''
|-
| kaddress
| Kernel copy address
| =0x80008000
| Hex memory address
|-
| rdaddress
| Ram Disk location address
| =0x81600000
| Hex memory address;<br>disabled by default
|-
| serial.low
| Serial number (low part)
| =00000001
| Numeric
|-
| serial.high
| Serial number (high part)
| =00000000
| Numeric
|-
| revision
| Revision ID
| =0003
| Numeric
|-
| kImageName
| Kernel, binary image name
| =zImage
| Kernel or binary image name
|-
| kRdImageName
| Kernel RAM Disk Image Name
| -
| Ram Disk image name
|-
| MachineID
| Machine ID (kernel ID)
| ;IGEPv2<br>=2344
| ;Module<br>=2717<br>;Proton<br>=3203
|-
| Mode
| Boot Mode
| ;Linux kernel<br>=kernel
| ;Other image (like uboot)<br>[binary image]
|}
|-
| ; Machine configuration ''' ;buddy=base0010 buddy.revision=B ''' ''' buddy=ilms0015''' loglevel | Setup the loglevel |} ==== Test changes ==== Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changes: - {| cellspacing="1" cellpadding="1" border="1" width="500"-
|-
| debug root@igep00x0:/dev# lsmod Module Size Used by rfcomm 48522 0 hidp 13311 0 l2cap 49001 4 rfcomm,hidp bluetooth 67643 3 rfcomm,hidp,l2cap libertas_sdio 13887 0 libertas 99318 1 libertas_sdio option 13044 0 usb_wwan 7196 1 option usbserial 23870 2 option,usb_wwan '''spidev 4898 0 ''' root@igep00x0:/dev# ls /dev/spidev1.2 /dev/spidev1.2 | Enable kernel debug output |} “spidev1.2”: refers at McSPI1 bus 2. Now we can communicate to accelerometer using spi driver functions. == SPI Test program == === Overview === This program is based in [http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev_test.c;h=16feda9014692a87a4996bf51d759ab9e7500ee5;hb=refs/heads/linux-2.6.37.y spidev_test] and it was edited to run with LIS3DH accelerometer, program can be explained in four parts: '''Connection properties:''' program lets change via parameters SPI configurations like: device, max speed, delay, bits per word, clock phase, clock polarity, etc. If you don't use any of this parameters program will use default options for LIS3DH communication. '''Read mode: '''Reads a word from a register. '''Write mode: '''Writes a word in a register. '''Test mode:''' Reads X, Y and Z axes from accelerometer. We recommend to read peripheral datasheet before use or modify program. === Compile program === The program source was compiled with Poky SDK but you can use other compilers like Linaro Toolchain: <pre>arm-poky-linux-gnueabi-gcc spiexamplebeta2.c -o spiexampleb2 </pre> Copy your final binary to rootfs. == Test program<br> == === Read WHO_AM_I register(0Fh) === LIS3DH has this dummy register (See 8.6 chapter) as a device identification. Its value is 0x33: <pre>root@igep00x0:~# ./spiexampleb2 -R 0F spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Value from 0F is: 33 root@igep00x0:~# </pre> === Read and Write CTRL_REG1 (20h) === This register is used to enable/disable: accelerometer and XYZ axes (See 8.8 chapter). The default value at startup is: <pre>root@igep00x0:~# ./spiexampleb2 | -R 20 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Value from 20 is: 07 root@igep00x0:~# </pre> It means that accelerometer was disabled and X, Y and Z axes was enabled. For example we can disable X axe typing: <pre>root@igep00x0:~# ./spiexampleb2 -W 20 -V 06 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Register to write 20 with value 06 root@igep00x0:~# ./spiexampleb2 -R 20 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Value from 20 is: 06 root@igep00x0:~# </pre> === Read accelerometer axes === {| cellspacing="1" cellpadding="1" border="1" width="500"
|-
| Finally we are going to read gravity force: LIS3DH has ±2g/±4g/±8g/±16g dynamically selectable full scale (See chapter 8.11). The axes values are expressed in two’s complement in 16 bits (See chapters 8.16, 8.17 and 8.18). fixrtc | [[Image:Lis3dhxyzaxes.png|150x159px]]Fix RTC variable |}<pre>root@igep00x0:~# ./spiexampleb2 -T spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Accelerometer TEST Values from X | -64, Values from Y -15872 and Values from Z -256 root@igep00x0:~# </pre> The next table shows results at different positions: {| cellspacing="1" cellpadding="1" border="1" width="600"
|-
| Position nocompcache | ±2g scale Configure nocompcache variable | ±4g scale =1 | ±8g scale | ±16g scale-
|-
| [[Image:NYtopimagetestomapfb.png|center|100x100px]] mode | X = 832 Y = 1024 Z = 15680 Configure frame bugger configuration | X = 256 Y = 128 Z = 7872 dvi:hd720-16@50 | X ;Other configuration<br>= 128 Y = 128 Z = 4032 | X = 64 Y = 128 Z = 1280 dvi:1280x720MR-16@60
|-
| [[Image:NYbotimagetest.png|center|100x100px]] vram | X = 256 Y = 704 Z = -17216 | X = 256 Y = 256 Z = -8320 Configure Video RAM assigned to every frame buffer | X = 64 Y = 128 Z = -4096 | X = 128 Y = 128 Z = -1344
|-
| [[Image:NYtophoritzontalimagetestomapfb.png|center|100x100px]] vram | X = -15872 Y = 64 Z = -320 | X = -7936 Y = 64 Z = -512 Configure Video RAM assigned to every frame buffer | X = -3968 Y = 128 Z = -192 | X = -1280 Y = 64 Z = -128
|-
| [[Image:NYbothoritzontalimagetestomapfb.png|center|100x100px]] | X = 16448 Y = 640 Z = 640 debug | X = 8128 Y = 192 Z = 384 Configure frame buffer debug output | X = 4032 Y = 64 Z = 64 - | X = 1344 Y = 64 Z = 192 -
|-
| [[Image:NYtopverticalimagetestomapdss.png|center|100x100px]] debug | X = 896 Y = 16512 Z = -576 | X = 320 Y = 8128 Z = -128 Configure DSS Video debug output | X = 192 Y = 4096 Z = -64 | X = 128 Y = 1344 Z = -128
|-
| [[Image:NYbotverticalimagetestsmsc911x.png|center|100x100px]] mac0 | X = -64 Y = -15872 Z = -256 Configure Board Ethernet Mac Address | X = -512 Y = -7808 Z = -384 | X = -64 >Y = -3840 Z = -384 | X = -128 Y = -1216 Z = -128 |} = BACKUP How to use SPI (prove with new firmware0xb2,0xb0,0x14,0xb5, under construction) = == Overview == This How-To is meant to be a starting point for people to learn use SPI for IGEP devices as quickly and easily as possible. In this how-to0xcd, we run an example program that reads and writes registers from 3-axis accelerometer ([http://www.st.com/internet/analog/product/250725.jsp LIS3DH]) included on the board IGEP New York. <br> 0xde == Requirements == There are some requisites to follow this guide: *[http://isee.biz/component/zoo/item/igep-virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")<br> *[http://isee.biz/component/zoo/item/igep-firmware-yocto-1-2 | For IGEP Firmware]: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") *[http://isee.biz/products/processor-boards/igep-com-module IGEP COM MODULE] and [http://isee.biz/products/expansion-boards/product-igep-new-york IGEP NEW YORK]<br> *SPI example program '''(link program)''' *MicroSD Card (at least 2Gbytes) == How Works == '''LIS3DH accelerometer:''' It is the accelerometer mounted in IGEP New York. '''Omap3 SPI Peripheral:''' It is the hardware used to communicated with accelerometer and other SPI devices. '''Omap2_mcspi:''' It is a bus driver than controls Omap3 SPI Peripheral. '''Spi:''' It is a protocol driver that defines functions and strucs used in SPI bus. '''Spidev:''' It is a device driver that export spi driver functionalities to userspace. '''Lis3lv02d_spi:''' SPI glue layer for lis3lv02d '''Lis31v02d:''' Device driver for LIS3DH accelerometer. '''Exp_ilms0015:''' It is a startup program for IGEP New York. It attach lis31v02d with Spi driver. {| cellspacing="1" cellpadding="1" border="1" width="200"BERLIN
|-
| [[Image:Spi linux schematicsmsc911x.pngmac1 |501x600px]]Configure Board Ethernet Mac Address |} <br> More information about Linux Kernel SPI at: *[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spi-summary;h=4884cb33845d7629987f60610eeedb863561006e;hb=refs/heads/linux-2.6.37.y SPI Overview] *[http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git;a=blob;f=Documentation/spi/spidev;h=ed2da5e5b28a4490a3b03787b02df66d083692be;hb=refs/heads/linux-2.6.37.y SPIDEV] == Attach Spidev to SPI driver == === Modify Linux Kernel Sources === To read accelerometer registers from spidev0xb2,0xb0,0x14,0xb5,0xcd, we need to attach spidev driver to spi driver at start up. So it is necessary to modify spi_board. 0xdf Go to $| For IGEP BERLIN (Kernel pathonly with IGEP PROTON)/arch/arm/mach-omap2/exp-ilms0015.c and edit the next fields in bold words. {| cellspacing="1" cellpadding="1" border="1" width="500"
|-
| static struct spi_board_info lis3lv02d_spi_board_info __initdata = { '''smsc911x.modalias = "spidev",''' mac | Configure Board Ethernet Mac Address '''//.modalias = "lis3lv02d_spi",''' .bus_num = -EINVAL, .chip_select = -EINVAL, .max_speed_hz = 1*1000*1000, .irq = -EINVAL, .mode = SPI_MODE_0, '''//.platform_data | = &lis3lv02d_pdata0xb2,''' }; inline void __init ilms0015_lis3lv02d_init(int bus_num0xb0, int cs0x14, int irq) { struct spi_board_info *spi = &lis3lv02d_spi_board_info; if ((gpio_request(irq0xb5, "LIS3LV02D IRQ") == 0) && (gpio_direction_input(irq) == 0)) gpio_export(irq0xcd, 0); else { pr_err("IGEP: Could not obtain gpio LIS3LV02D IRQ\n"); return; } spi->bus_num = bus_num; spi->chip_select = cs; spi->irq = OMAP_GPIO_IRQ(irq), spi_register_board_info(&lis3lv02d_spi_board_info, 1); } ... void __init ilms0015_init(void) { mux_partition = omap_mux_get("core"); /* Mux initialitzation for ilms0015 */ omap_mux_write_array(mux_partition, ilms0015_mux); /* 3-axis accelerometer */ ilms0015_lis3lv02d_init(1, 2, 174); /* Export some GPIO */ ilms0015_gpio_init(); } 0xde |} Now spi_register_board_info has all information necessary to attach spidev driver instead lis3lv02d_spi. Once we edit codeFor IGEPv2, compile your modified Kernel, you can follow [http://labs.isee.biz/index.php/Linux_Kernel_2.6.37.y#Build_kernel_from_sources this tutorial] for this purpose. === Enable ilms0015 support === “ilms0015” is the technical name of IGEP New York. By default, poky-media-create (See: [http://labs.isee.biz/index.php/How_to_create_a_SD-card_with_the_latest_software_image Poky firmware with Kernel 2.6.37.y]) configured as igep0030PROTON, gives support only for IGEP Expansions Paris PARIS and Berlin. We need to configure igep.ini and gives support to IGEP New York: {| cellspacing="1" cellpadding="1" border="1" width="500"BERLIN
|-
| ; Machine configuration ''' ;buddy=base0010 buddyubi.revision=B ''' ''' buddy=ilms0015''' mtd | Fot UBI FS boot |} === Test changes === Once you copy your new Kernel binaries and edit igep.ini. Power up your board, log in and check your changes: - {| cellspacing="1" cellpadding="1" border="1" width="500"-
|-
| root | Configure root@igep00x0:/dev# lsmod Module Size Used by rfcomm 48522 0 hidp 13311 0 l2cap 49001 4 rfcommdirectory for MMC,hidp NFS or UBI bluetooth| 67643 3 rfcomm,hidp,l2cap libertas_sdio 13887 0 libertas 99318 1 libertas_sdio option 13044 0 usb_wwan 7196 1 option usbserial 23870 2 option,usb_wwan '''spidev 4898 0 ''' root@igep00x0:For mmc memory<br>=/dev# ls /dev/spidev1.2 /dev/spidev1.2 mmcblk0p2 rw rootwait |} “spidev1.2”: refers at McSPI1 bus 2. Now we can communicate to accelerometer using spi driver functions. == SPI Test program == === Overview === This program is based in [http://git.isee.biz/?p=pub/scm/linux-omap-2.6.git a=blob;f=Documentation/spi/spidev_test.c;h=16feda9014692a87a4996bf51d759ab9e7500ee5;hb=refs/heads/linux-2.6.37.y spidev_test] and it was edited to run with LIS3DH accelerometer, program can be explained in four parts: '''Connection properties:''' program lets change via parameters SPI configurations like: device, max speed, delay, bits per word, clock phase, clock polarity, etc. If you don't use any of this parameters program will use default options for LIS3DH communication. '''Read mode: '''Reads a word from a register. '''Write mode: '''Writes a word in a register. '''Test mode:''' Reads X, Y and Z axes from accelerometer. We recommend to read peripheral datasheet before use or modify program. === Compile program === The program source was compiled with Poky SDK but you can use other compilers like Linaro Toolchain: <pre>arm-poky-linux-gnueabi-gcc spiexamplebeta2.c -o spiexampleb2 </pre> Copy your final binary to rootfs. == Test programFor flash memory<br> == === Read WHO_AM_I register(0Fh) === LIS3DH has this dummy register (See 8.6 chapter) as a device identification. Its value is 0x33: <pre>root@igep00x0:~# ./spiexampleb2 -R 0F spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Value from 0F is: 33 root@igep00x0:~# <dev/pre> === Read and Write CTRL_REG1 (20h) === This register is used to enable/disable: accelerometer and XYZ axes (See 8.8 chapter). The default value at startup is: <pre>root@igep00x0:~# ./spiexampleb2 -R 20 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Value from 20 is: 07 root@igep00x0:~# </pre> It means that accelerometer was disabled and X, Y and Z axes was enabled. For example we can disable X axe typing: <pre>root@igep00x0:~# ./spiexampleb2 -W 20 -V 06 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Register to write 20 with value 06 root@igep00x0:~# ./spiexampleb2 -R 20 spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Value from 20 is: 06 root@igep00x0:~# </pre> === Read accelerometer axes === {| cellspacing="1" cellpadding="1" border="1" width="500"mtdblock2
|-
| Finally we are going to read gravity force: LIS3DH has ±2g/±4g/±8g/±16g dynamically selectable full scale (See chapter 8.11). The axes values are expressed in two’s complement in 16 bits (See chapters 8.16, 8.17 and 8.18). nfsroot | [[Image:Lis3dhxyzaxes.png|150x159px]]For NFS boot |}<pre>root@igep00x0:~# ./spiexampleb2 -T spi mode: 0 bits per word: 8 max speed: 1000000 Hz (1000 KHz) Accelerometer TEST Values from X | -64, Values from Y -15872 and Values from Z -256 root@igep00x0:~# </pre> The next table shows results at different positions: {| cellspacing="1" cellpadding="1" border="1" width="600"
|-
| Position rootfstype | ±2g scale For UBI FS boot | ±4g scale - | ±8g scale | ±16g scale-
|-
| [[Image:NYtopimagetest.png|center|100x100px]] ip | X = 832 Y = 1024 Z = 15680 | X = 256 Y = 128 Z = 7872 For NFS boot | X = 128 Y = 128 Z = 4032 - | X = 64 Y = 128 Z = 1280 -
|-
| [[Image:NYbotimagetest.png|center|100x100px]] init | X = 256 Y = 704 Z = -17216 | X = 256 Y = 256 Z = -8320 Assign init program | X = 64 Y = 128 Z = -4096 | X = 128 Y = 128 Z = -1344
|-
| [[Image:NYtophoritzontalimagetestmusb_hdrc.png|center|100x100px]] debug | X = -15872 Y = 64 Z = -320 | X = -7936 Y = 64 Z = -512 USB debug | X = -3968 Y = 128 Z = -192 | X = -1280 Y = 64 Z = -128
|-
| [[Image:NYbothoritzontalimagetestmusb_hdrc.png|center|100x100px]] | X = 16448 Y = 640 Z = 640 use_dma | X = 8128 Y = 192 Z = 384 USB over network | X = 4032 Y = 64 Z = 64 - | X = 1344 Y = 64 Z = 192 -
|-
| [[Image:NYtopverticalimagetestlibertas.png|center|100x100px]] libertas_debug | X = 896 Y = 16512 Z = -576 | X = 320 Y = 8128 Z = -128 Configure libertas debug | X = 192 Y = 4096 Z = -64 | X = 128 Y = 1344 Z = -128
|-
| [[Image:NYbotverticalimagetestboard.png|center|100x100px]] ei485 | X = -64 Y = -15872 Z = -256 Enable/disable RS485 | X = -512 Y = -7808 Z = -384 | X = -64 >nbsp;;Y = -3840 Z = -384 | X = -128 Y = -1216 Z = -128 |} = How to install Qt Creator (under construction) = = How to install Eclipse (under construction) = New igepv2 expansion getting startedEnable RS485<br> {{Table/IGEP Technology Devices|Tech_Family={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_Family}}yes |Tech_ID={{#lst:Template:Links|IGEPv2_EXPANSION_Tech_ID}}|Name={{#lst:Template:Links|IGEPv2_EXPANSION_Name}}|Image={{#lst:Template:Links|IGEPv2_EXPANSION_Image}}|ISEE_MainPage={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_MainPage}}|ISEE_Hardware={{#lst:Template:Links|IGEPv2_EXPANSION_ISEE_Hardware}}}} <br> __TOC__ = Overview = This is the 1/3 chapter of IGEPv2 Expansion Tutorial Guide. In this first chapter, we will learn '''how to connect some expansion peripherals'''. = Requirements (link items with isee shop) = In this tutorial we are going to use the following peripherals: *IGEPv2 with its power supply *a monitor compatible with VGA *a Powertrip 4.3" or [http://shop.isee.biz/buy-online/accesories/tft-24-bits-seiko-7.html Seiko 7"] screen *a DB9 connector with External Serial peripheral (example: USB Serial convertor) *4 pin connector for CAN Bus with another CAN Bus peripheral *SIM card (optional GPRS antenna) *Composite video cable with a composite video output peripheral *a PC with Linux or Windows = Getting started = == Connect IGEPv2 Expansion with IGEPv2 Board == The IGEPv2 Expansion connects to the IGEPv2 Board through J990, JA41, JA42, JC30 and J960 connectors. Some IGEPv2 Expansion may include three jumpers, you should remove it because they are designed for test and lab purposes. Just take a look on the figure below: ;Disable RS485<br> {| border="1" align="center" width="200" cellspacing="1" cellpadding="1"no
|-
| [[Image:Igepv2expconnectoigepv2board.PNGmodem |268px]]<br> Enable/disable GPRS modem | [[Image:Igepv2expconnectoigepv2 2.PNG|268px]] ;Enable modem (IGEPv2 Expansion)<br>=no |} == TFT and Touchscreen == ;Enable modem (IGEPv2 EXPANSION integrates a LCD backlight driver (Texas instruments TPS61081Expansion) and touch screen controller (Texas instruments TSC2046), 4-wire touch screen controller which supports a low-voltage I/O interface which can be directly connected to a SEIKO 7” LCD or to a POWERTIP 4.3” LCD. Use J301 connector for POWERTRIP 4.3" or use J302, J303 and J304 connector for SEIKO 7".<br> {| border="1" align="center" width="544" cellspacing="1" cellpadding="1"yes
|-
| buddy.revision | Enable hardware buddy revision [[Image:IGEP0022 PROTO RA DSC 0142.JPGA or B] |centerOnly for base0010<br>=A |536px]]Only for base0010<br>=B
|}