Using the TAM3517 "Twister" Board

Download the Root File System Image
Install Root File System on SD-Card
Prepare Twister Board
Prepare the ELDK boot evironment
Using the ELDK Environment

Download the Root File System Image

The demo image is currently available in the "beta-eldk/twister" directory of the DENX FTP server. Please contact DENX for access data.

$ ncftpget -u eldk-beta ftp://ftp.denx.de/twister/twister-rootfs.bz2
Password: ***********
twister-rootfs.bz2:                                    201.77 MB    1.51 MB/s

Install Root File System on SD-Card

You need a Micro-SD-Card of at least 2 GB (or bigger). Attach it to your host using any suitable Micro-SD-Card reader. To find out as which device it was registered, run for example:

...
... kernel: [576512.948487] sd 18:0:0:2: [sdh] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
... kernel: [576512.953356] sd 18:0:0:2: [sdh] Write Protect is off
... kernel: [576512.953363] sd 18:0:0:2: [sdh] Assuming drive cache: write through
... kernel: [576512.955979] sd 18:0:0:2: [sdh] Assuming drive cache: write through
... kernel: [576512.955986]  sdh:
... kernel: [576512.961490] sd 18:0:0:2: [sdh] Assuming drive cache: write through
... kernel: [576512.961495] sd 18:0:0:2: [sdh] Attached SCSI removable disk

In this case the SD-Card has been registered as "sdh".

WARNING: Be careful and double-check the data! Using the wrong device may corrupt your host computer's hard disk or destroy other important data!

Note: Also make sure to use the whole device (i. e. "/dev/sdX") and not for example a partition on that device (like "/dev/sdX1" or so).

Write image to SD-Card (double-check the output device name!):

Wait until the command completes.  Depending on the speed of your
system and your SD-Card this may take several minutes.  Do not remove
the SD-Card from the Reader before the command has completed and any
LEDs or simila on your reader show that the SD-Card is nolonger
active.
$ bunzip2 <twister-rootfs.bz2 | sudo dd bs=512k of=/dev/sdh 
[sudo] password for wd: 
...

Prepare Twister Board

Make sure the "Twister" board boots into the Angström environment. If necessary, follow the instructions in the "TAM-3517 System On Module User's Guide" to (re-) install Angström on your board.
Power off the "Twister" board
Insert the SD-Card with the ELDK root file system.
Power on the "Twister" board and boot into the Angström environment.
log in on the serial console port as "root" (no password required)
Install the ELDK's Linux kernel image into NAND:
```
root@tam3517:~# dd if=/media/mmcblk0/boot/twister-uImage of=/dev/mtdblock3 bs=128k
22+0 records in
22+0 records out
root@tam3517:~# sync
root@tam3517:~# 
```
Note: the ELDK's Linux kernel is compatible with and capable of also booting into the Angström and Android environments.
Reset the "Twister" board

Prepare the ELDK boot evironment

During the initial boot sequence, press any key on the serial console to stop the boot loader from booting into Angström.

At the U-Boot prompt, please enter the following commands:
Save previously used boot command:

TAM3517 # setenv oldbootcmd ${bootcmd}

This allows you to still boot into the previously installed (Angström) environment by entering the "run oldbootcmd" command at the U-Boot boot prompt.

TAM3517 # setenv rootfstype ext3
TAM3517 # setenv rootdev /dev/mmcblk0
TAM3517 # setenv eldkargs 'setenv bootargs root=${rootdev} ro rootwait rootfstype=${rootfstype}'
TAM3517 # setenv tam3517 'setenv bootargs ${bootargs} mem=${memsize} mpurate=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr} eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${sys_mode} ${board_info} omapdss.def_disp=${def_disp} ${disp_mode} mtdparts=${nandparts}'
TAM3517 # setenv eldk 'run eldkargs tam3517 load_nand_k;bootm
${kernel_load}'
TAM3517 # setenv bootcmd run eldk
TAM3517 # save
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x180000 -- 100% complete.
Writing to Nand... done

Note: please double check your input. Especially the "tam3517" is a very long line. Make sure you enter it correctly. If you are not sure, just repeat the whole "setenv" command. Run "saveenv" only after you verified everything is OK.

Now test booting into the new ELDK environment:

TAM3517 # boot

Note: you can as well just reset or power-cycle the "Twister" board.

Using the ELDK Environment

The ELDK environment is primarily oriented for a touch screen operated device. Normally such devices do not show a cursor. For easier testing you can attach a USB keyboard and/or mouse, and to be able to use the mouse the cursor has be enabled. [This can be easily changed.]
If you find your touch screen is operating not reliably, you may want to recalibrate it. Log in on the serial console port as "root" (no password needed) and enter the following commands:
```
root@twister:~# /etc/init.d/xserver-nodm stop
root@twister:~# ts_calibrate
```
Press the crosshairs (in the 4 corners, then in the middle) on the LCD to calibrate the touch. It is recommended to do this carefully, using a suitable pin to allow for exact input. If you pressed a bad location, just complete the sequence and then re-run the "ts_calibrate" command. Once completed, restart the GUI:
```
root@twister:~# /etc/init.d/xserver-nodm start
```

If you "Twister" board is connected to a network, it will try to auto-configure using DHCP. If you have a working DHCP server, you can log in over the network using ssh. To find out the assigned IP address you can run the following command on the serial console port:

root@twister:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1F:7B:15:01:59  
          inet addr:192.168.5.218  Bcast:192.168.255.255 Mask:255.255.0.0
          inet6 addr: fe80::21f:7bff:fe15:159/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:186 errors:0 dropped:0 overruns:0 frame:0
          TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:18149 (17.7 KiB)  TX bytes:20407 (19.9 KiB)
          Interrupt:57 

eth1      Link encap:Ethernet  HWaddr 00:1F:7B:15:01:58  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:67 
...

Here the network cable was attached to the left Ethernet connector (interface eth0). It was assigned IP address 192.168.5.218. We can login over the network like this:

$ ssh root@192.168.5.218  
...
root@192.168.5.218's password: 
root@twister:~#

Just press enter when prompted for the password.