Difference between revisions of "Getting started with IGEP MODULE"

Revision as of 15:42, 22 November 2010

Introduction

This page describes how to use the USB device port of our ISEE IGEP MODULE with OMAP3 processor to communicate with the USB port of your computer (or USB hub connected to your computer).

We can power up the IGEP MODULE via the on-board USB OTG port, and we only need to use a USB cable (USB A type plug to mini B type plug).

The on-board HS USB OTG port is used as the default power input for IGEP MODULE standalone operating mode.

Once the board is powered up and running, we will get Ethernet connectivity over the same USB cable (USB Ethernet Gadget/RNDIS driver).

By default, the IGEP MODULE interface will have the IP address 192.168.7.2.

Other available ways to communicate with IGEP MODULE are WIFI or Bluetooth on-board interfaces. But by default, they are not configured.

Linux Host USB Network Configuration

You should have the usbnet module available for your Linux kernel. On most distributions, this is the case by default. If this is not the case for your distribution, you will need to enable USB networking support in the kernel. If you build your own kernel then you want 'CDC Ethernet support' in USB Network adaptors.

Ubuntu 10.04 LTS Lucid Lynx

In the file /etc/network/interfaces, you should add a section which looks like this:

auto usb0
iface usb0 inet static
    address 192.168.7.1
    network 192.168.7.0
    netmask 255.255.255.0
    broadcast 192.168.7.255
    gateway 192.168.7.1

Connect to the board using ssh

ssh -l root 192.168.7.2
 
The authenticity of host '192.168.7.2 (192.168.7.2)' can't be established.
RSA key fingerprint is 9d:0e:ba:02:2a:76:e4:5f:d1:c1:9b:2d:85:6c:83:d4.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.7.2' (RSA) to the list of known hosts.
root@192.168.7.2's password: [enter] (no password)
root@igep0030:~#

Windows Host USB Network Configuration

Windows 7

• http://robosavvy.com/forum/viewtopic.php?p=28788

Mac OS X Host USB Network Configuration

Please contribute ...

Updating and flashing the firmware

Latest is: Poky 3.3.1-3 (/etc/version - 201011081439)

Updating the firmware is done using a SD card, first we will create a minimal SD card and copy latest firmware image into the SD card

mkdir workdir && cd workdir
wget http://downloads.igep.es/poky/green-3.3/v3.3.1-3/poky-media-create
wget http://downloads.igep.es/poky/green-3.3/v3.3.1-3/poky-media-minimal-igep0030-sdcard-3.3.1-3.tar.gz
chmod +x poky-media-create

Next, insert your SD card into the host machine and ensure you know the device node for your sd card reader. In the following example we assume /dev/mmcblk0. If you are unsure of the device node of your SD card, remove and reinsert the card and type dmesg on the command line. The last few lines should give you the device node of the card you just inserted.

./poky-media-create --mmc /dev/mmcblk0 --binary poky-media-minimal-igep0030-sdcard-3.3.1-3.tar.gz

Now it's time to download needed packages and copy into SD card

wget http://downloads.igep.es/poky/green-3.3/v3.3.1-3/poky-media-minimal-igep0030-flash-3.3.1-3.tar.gz
wget http://downloads.igep.es/poky/green-3.3/v3.3.1-3/u-boot-env_2010.06-0-r0_igep0030.ipk
mkdir disk && sudo mount /dev/sdb2 disk
sudo tar xzf poky-media-minimal-igep0030-flash-3.3.1-3.tar.gz -C disk/home/root/
sudo cp u-boot-env_2010.06-0-r0_igep0030.ipk disk/home/root
sudo umount disk && rmdir disk

Connect to device

ssh -l root 192.168.7.2

Some packages are missing in SD image, we should install

opkg install u-boot-env_2010.06-0-r0_igep0030.ipk

Next, enter into firmware directory

cd poky-media-minimal-igep0030-flash-3.3.1-3

By default the flash.sh script test fulls OneNAND, it takes a long time and it's not really necessary, we should speed up the flash process editing the flash.sh script and commenting next lines

# Test and mark OneNAND bad blocks
# for i in 0 1 2 3 4; do nandtest -m /dev/mtd${i}; done

Now you can run the flash script

./flash.sh

Troubleshooting

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

In the case of the SSH client in Linux, a changed host key results in the client refusing to connect and showing an remote host identification has changed error

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
8d:0b:29:f0:0a:a1:f5:56:0c:12:18:b0:26:02:6d:9d.
Please contact your system administrator.
Add correct host key in /home/eballetbo/.ssh/known_hosts to get rid of this message.
Offending key in /home/eballetbo/.ssh/known_hosts:57
RSA host key for 192.168.7.2 has changed and you have requested strict checking.

To fix the problem edit your ~/.ssh/known_hosts and remove the line corresponding to this host.