OMAPL138 Software Developers Guide- How to Create an SD Card

Hi:

Thanks for following up. This can get so overwhelming so yeah, I appreciate your help. I amanaged to get through it and create an SD card as per the instructions in the Software Developers Guide. Now I am trying to run the setup.sh script under Setting up the DVSDK and this is the error I get:

clark@HalifaxVm32bitUbuntu:~/ti-dvsdk_omapl138-evm_4_02_00_06$ ./setup.sh

--------------------------------------------------------------------------------
TISDK setup script

This script will set up your development host for dvsdk development.
Parts of this script require administrator priviliges (sudo access).
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 10.04 LTS found successfully, continuing..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will make sure you have the proper host support packages installed
using the following command: sudo apt-get install xinetd tftpd nfs-kernel-server minicom build-essential libncurses5-dev uboot-mkimage autoconf automake

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

[sudo] password for clark:
Reading package lists... Done
Building dependency tree      
Reading state information... Done
xinetd is already the newest version.
tftpd is already the newest version.
nfs-kernel-server is already the newest version.
minicom is already the newest version.
build-essential is already the newest version.
libncurses5-dev is already the newest version.
uboot-mkimage is already the newest version.
autoconf is already the newest version.
automake is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 84 not upgraded.

Package verification and installation successfully completed
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/clark/targetfs ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/clark/targetfs

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/clark/targetfs already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] o
Old /home/clark/targetfs removed
ls: cannot access ./bin/../filesystem/??sdk*rootfs.tar.gz: No such file or directory
tar: -C: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: /home/clark/targetfs: Not found in archive
tar: Exiting with failure status due to previous errors
Failed setup, aborting..
Failed setup, aborting..
clark@HalifaxVm32bitUbuntu:~/ti-dvsdk_omapl138-evm_4_02_00_06$

Where can I find this filesystem file?

Thanks

Derek

Derek,

       The filesystem must be found under ~/ti-dvsdk_omapl138-evm_4_02_00_06/filesystem, there would be two files as below under this directory. During setup the file dvsdk-da850-omapl138-evm-rootfs.tar.gz is the one getting installed in to directory you choose for target filesystem.

       1. arago-base-tisdk-image-da850-omapl138-evm.tar.gz

       2. dvsdk-da850-omapl138-evm-rootfs.tar.gz

I had never noticed below error

       "ls: cannot access ./bin/../filesystem/??sdk*rootfs.tar.gz: No such file or directory"

I think this problem mught be because ./setup.sh is not run with sudo or root previlege, as you can see in the trace it says "Note! This command requires you to have administrator priviliges (sudo access)"

Best Regards,

Velan

Hi:

Yes, I figured the file should be there but it isnt so I am wondering where it is and why it isnt there? The setup asks for root automatically if u dont run it with sudo, but I ran it both ways and the same results.

Any thoughts?

Thanks

Derek

Derek,

         I suggest you re-download the SDK installer from http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

         I suspect the state of the SDK in SD card.

         Please send us the trace from beginning to debug further

Best Regards

Velan

Hi:

Following the OMAPL138 Software Developers Guide, I reinstalled the DVSDK on my desktop host and it seemed to work this time and I got as far as trying to run the hello world app  on the target but when I store the file in the NFS directory it doesnt show up on the target. Any thoughts? Also I have a development environment steup the same on my laptop but the DVSDK install keeps Seg faulting on the ../install-tools/bin/install_rootfs.sh line13: 13385 Segmentation Fault    $*

One step forward and two back... any help is appreciated.

Derek 

Ok...

So since I didnt have an SD card with my kit I had to create one using the instructions in the OMAPL138 Software Developers Guide. In doing so it sets up the the EVM to boot from SD not tftp and NFS... so I ran the script $DVSDK/bin/setup-uboot-env.sh and changed it to have the EVM boot through tftp and NFS and that seemed to work ok... Now when I power up the EVM (using minicom) I see:

booto broadcast 1

WARN: emac_send_packet: no link

I see in the boot params there is:

bootcmd

and it says dhcp... should I be giving the EVM an ip. My desktop (host) doesnt have a dhcp server on it (would it go out to the network to get one via teh serial connection- doesnt seem to make sense for it to do that...)?? Any help is appreciated.

I still cannot get my laptop to finish the DVSDK install. It seg faults everytime. I have tried downloading the setup file several times... same issue...

Thanks

Derek

Hi Derek,

Are you sure the Ethernet cable is connected to the board?

Regards,

Yan

Seems like the problem with the Seg fault was that all the necessary packages needed for install were not installed. The same thing happened on my desktop, but I didnt notice that it had seg faulted so I went on to run the /DVSDK/ti.../setup.sh. This script then figured out what packages I needed. I then downloaded those packages and re-ran the DVSDK installer and it worked... so before you install the DVSDK kr if you get a seg fault on install, run the setup script in the root ti dir. Then download and install the packages and then re-run the DVSDKk

Thanks all...

Derek

Hi:

So know I can get to the point where it sits here...

Booting with TI UBL
Device OPP (300MHz, 1.2V)

U-Boot 2009.11 (Mar 24 2011 - 23:24:35)

I2C:   ready
DRAM:  64 MB
MMC:   davinci: 0
In:    serial
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
DDR Clock : 132000000 Hz
Net:   Ethernet PHY: GENERIC @ 0x00

Hit any key to stop autoboot:  0
BOOTP broadcast 1
DHCP client bound to address 131.136.21.64
Using  device
TFTP from server xxx.xxx.xxx.xxx; our IP address is yyy.yyy.yyy.yyy
Filename 'uImage-da850-omapl138-evm.bin'.
Load address: 0xc0700000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################
done
Bytes transferred = 2187060 (215f34 hex)
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Arago/2.6.32+2.6.33-rc4-psp03.20
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2186996 Bytes =  2.1 MB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel

And it just sits there and doesnt do anything else... I tried loadingit several times and it just gets to the same point and hangs.

Any help is appreciated.

Thanks

Derek

Nevermind, I reinstalled everything from the ./setup.sh script in the root TI dir and it booted this time.

Thanks

Derek

   Good to hear this.

Best regards

Velan