RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355

2008-12-15 Thread Venkatachala Upadhya 
Hello,

I have also observed similar problem in Fedora 9 core. Essentially, the 
packages from TI website download does not get installed. To work around this, 
I have installed the packages to RHEL 4 and then used the tar balls to get that 
installed on FC9. This way it worked well for me and I am not having any 
trouble in building the binary for ARM/DSP for DM6446 EVM board.

My suggestion would be, double check the installation. If the installation is 
successful, you have to update your path, so that the system can find 
arm_v5t_le-gcc in its path.


With best regards,

Venkatachala Upadhya| Extn: 65395|
--


From: davinci-linux-open-source-boun...@linux.davincidsp.com 
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of 
Laurent Meyer
Sent: 15 December, 2008 4:30 PM
To: zhij...@hotmail.com
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: RE: problem to build the new Linux kernel using the updated DVSDK v1.3 
for DM355

Hello,

I faced the same problem, check how your ubuntu box is installed

# unaeme -a
Linux darkstar 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 
GNU/Linux

If your linux is compiled in 64 bits, trying to run 32 bits binaries can result 
in "No such file or directory" message.
If your arch is 64 bits, to allow 32 bits binaries execution: type:

sudo apt-get install gcc-multilib libc6-i386

Regards
Laurent.

Your message bellow:

HI,


I reinstalled my Ubuntu linux OS, and the Apr 15 updates of DVEVM software from 
TI website. But I still cannot compile the kernel using kernelkit as I did 
successfully with the old version before. Here is the command (line wrap on) 
causing the problem,

knoppix at 
Knoppix<http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source>:/media/hda5/home/zyang1/workdir/lsp/ti-davinci$
 make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
  CHK include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC  scripts/mod/empty.o
/bin/sh: arm_v5t_le-gcc: command not found


--
Laurent MEYER.
Resp projets Borea SAS
Tél: +331 75 43 78 43
Email: laurent.me...@borea.com<mailto:laurent.me...@borea.com>




This message (including attachment if any) is confidential and may be 
privileged. If you have received this message by mistake please notify the 
sender by return e-mail and delete this message from your system. Any 
unauthorized use or dissemination of this message in whole or in part is 
strictly prohibited. E-mail may contain viruses. Before opening attachments 
please check them for viruses and defects. While MindTree Limited (MindTree) 
has put in place checks to minimize the risks, MindTree will not be responsible 
for any viruses or defects or any forwarded attachments emanating either from 
within MindTree or outside.

Please note that e-mails are susceptible to change and MindTree shall not be 
liable for any improper, untimely or incomplete transmission.

MindTree reserves the right to monitor and review the content of all messages 
sent to or from MindTree e-mail address. Messages sent to or from this e-mail 
address may be stored on the MindTree e-mail system or else where.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355

2008-12-15 Thread Laurent Meyer 
Hello,

I faced the same problem, check how your ubuntu box is installed

# unaeme -a
Linux darkstar 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008
x86_64 GNU/Linux

If your linux is compiled in 64 bits, trying to run 32 bits binaries can
result in "No such file or directory" message.
If your arch is 64 bits, to allow 32 bits binaries execution: type:

 sudo apt-get install gcc-multilib libc6-i386

Regards
Laurent.

Your message bellow:

HI, 


I reinstalled my Ubuntu linux OS, and the Apr 15 updates of DVEVM software from 
TI website. But I still cannot compile the kernel using kernelkit as I did 
successfully with the old version before. Here is the command (line wrap on) 
causing the problem,
 
knoppix at Knoppix:/media/hda5/home/zyang1/workdir/lsp/ti-davinci$ make 
ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
  CHK include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC  scripts/mod/empty.o
/bin/sh: arm_v5t_le-gcc: command not found 

-- 
Laurent MEYER.
Resp projets Borea SAS
Tél: +331 75 43 78 43
Email: laurent.me...@borea.com
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355

2008-06-23 Thread Phil Quiney 
Hi
 
See comments below...
 
Regards
 
Phil Q
 
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com <http://www.trinityconvergence.com/> 

 



From: YangZhijun [mailto:[EMAIL PROTECTED] 
Sent: 23 June 2008 09:59
To: Phil Quiney; davinci-linux-open-source@linux.davincidsp.com
Subject: RE: problem to build the new Linux kernel using the updated DVSDK v1.3 
for DM355


HI, 

I reinstalled my Ubuntu linux OS, and the Apr 15 updates of DVEVM software from 
TI website. But I still cannot compile the kernel using kernelkit as I did 
successfully with the old version before. Here is the command (line wrap on) 
causing the problem,
 
[EMAIL PROTECTED]:/media/hda5/home/zyang1/workdir/lsp/ti-davinci$ make ARCH=arm 
CROSS_COMPILE=arm_v5t_le- uImage
  CHK include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC  scripts/mod/empty.o
/bin/sh: arm_v5t_le-gcc: command not found 
 
[Phil Q] here is the error, the shell cannot find the cross compiler. You have 
2 fixes
1/ Add the path to the compiler to the PATH variable 
2/ set CROSS_COMPILE to the full path to the compiler + arm_v5t_le-
 
The command 'which arm_v5t_le-gcc' must work if you use option #1 
[EMAIL PROTECTED] linux]$ which arm_v5t_le-gcc
/opt/dm355/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc
 
make[2]: *** [scripts/mod/empty.o] Error 127
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2

By the way, in the same directory I can run the following two commands without 
problem,

make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_evm_defconfig

make ARCH=arm CROSS_COMPILE=arm_v5t_le- checksetconfig

[Phil Q] no great suprise - neither of these use the cross compiler 
 
In the new guide I notice that it seems there is a subdir linux-2.6.10_mvl401 
in /home//workdir/lsp/ti-davinci in which one should do compilation 
of the kernel, but I cannot find this subdir. 

[Phil Q] You need to take a copy of the kernel source you unpacked from 
mvl_4_0_1_demo_lsp_setuplinux_01_20_00_014.bin into your working area. After 
running the .bin file you should have a DaVinciLSP-01_20_00_014.tar.gz (in 
/opt/dm355/mv_pro_4.0.1) file that would install the kernel source to 
montavista/pro/devkit/lsp/ti-davinci. You can use this file to unpack into your 
working directory and move the ti-davinci directory wherever you want 
afterwards.
 

 
 
 I did these according to the new guide, so it should be all right. The 
following is my Rules.make file,
 
[Phil Q] You wasted a lot of time changing lines you didn't need to change in 
this file. Any line with  DVSDK_INSTALL_DIR or
DVEVM_INSTALL_DIR  will pick up the chage you make to its definition for itself.
The kernel pointed to must be built before the DVSDK build will work.
 
#
# This make variable must be set before the demos or examples
# can be built.  It must be set to either dm355 or dm6446
#
PLATFORM=dm355
ifndef PLATFORM
   $(error PLATFORM must be set in Rules.make to dm355 or dm6446 before 
building the demos)
endif


# The installation directory of the DVSDK  dvsdk_1_30_00_40.
DVSDK_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40

# For backwards compatibility
#DVEVM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)
DVEVM_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40

# Where the Codec Engine package is installed.
#CE_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/codec_engine_2_00_01
CE_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/codec_engine_2_00_01

# Where the XDAIS package is installed.
#XDAIS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/xdais_6_00_01
XDAIS_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/xdais_6_00_01

# Where the DSP Link package is installed.
#LINK_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dsplink_140-05p1
LINK_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/dsplink_140-05p1

# Where the CMEM (contiguous memory allocator) package is installed.
#CMEM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/cmem_2_00_01
CMEM_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/cmem_2_00_01

# Where the codec servers are installed (dm6446) or codecs (dm355)
ifneq ($(PLATFORM),dm355)
   CODEC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dm6446_dvsdk_combos_1_34
else
   #CODEC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dm355_codecs_1_12_000
   CODEC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/dm355_codecs_1_12_000
endif

# Where the RTSC tools package is installed.
XDC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/xdc_3_00_02

# Where Framework Components product is installed
#FC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/framework_components_2_00_01
FC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/framework_components_2_00_01

# Where DSP/BIOS is installed
#BIOS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/__BIOS_VERS__
BIOS_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/__BIOS_VERS__

# The directory that poin

RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355

2008-06-23 Thread ganesh 
Hi,

 

 

   My 2 cents. One dirty way to do it is to set the PATH manually

 

Type PATH=/opt/montavista/……../armv5l-linux/bin:$PATH in the command
shell.

 

The above path is the path to the directory where arm_v5t_le-gcc is
installed.

 

U may Type “locate arm_v5t_le-gcc  in the command prompt to get the
location of the cross compiler. You may need to do updatedb first on the
command prompt. 

 

Ganesh

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
YangZhijun
Sent: 23 June 2008 01:59
To: Phil Quiney; davinci-linux-open-source@linux.davincidsp.com
Subject: RE: problem to build the new Linux kernel using the updated DVSDK
v1.3 for DM355

 

HI, 

I reinstalled my Ubuntu linux OS, and the Apr 15 updates of DVEVM software
from TI website. But I still cannot compile the kernel using kernelkit as I
did successfully with the old version before. Here is the command (line wrap
on) causing the problem,

[EMAIL PROTECTED]:/media/hda5/home/zyang1/workdir/lsp/ti-davinci$ make
ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
  CHK include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC  scripts/mod/empty.o
/bin/sh: arm_v5t_le-gcc: command not found
make[2]: *** [scripts/mod/empty.o] Error 127
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2

By the way, in the same directory I can run the following two commands
without problem,

make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_evm_defconfig

make ARCH=arm C ROSS_COMPILE=arm_v5t_le- checksetconfig

In the new guide I notice that it seems there is a subdir
linux-2.6.10_mvl401 in /home//workdir/lsp/ti-davinci in which one
should do compilation of the kernel, but I cannot find this subdir. 

You should have the following files (these are the Apr 15 updates)

 

dvsdk_setuplinux_1_30_00_40.bin

mvl_4_0_1_demo_lsp_setuplinux_01_20_00_014.bin

xdc_setuplinux_3_00_02_14.bin



Yes, I have these updates.

The dvsdk_setuplinux_1_30_00_40.bin and xdc_setuplinux_3_00_02_14.bin files
you install to your working directory - the 'xdc' goes 'inside' the dvsdk
directory so you must install dvsdk first. The Rules.mak file in the dvsdk
directory needs editing to point to toolchain & kernel source.

I did these according to the new guide, so it should be all right. The
following is my Rules.make file,

#
# This make variable must be set before the demos or examples
# can be built.  It must be set to either dm355 or dm6446
#
PLATFORM=dm355
ifndef PLATFORM
   $(error PLATFORM must be set in Rules.make to dm355 or dm6446 before
building the demos)
endif


# The installation directory of the DVSDK  dvsdk_1_30_00_40.
DVSDK_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40

# For backwards compatibility
#DVEVM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)
DVEVM_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40

# Where the Codec Engine package is installed.
#CE_INSTALL_DIR=$(DVSDK_INST! ALL_DIR)/codec_engine_2_00_01
CE_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/codec_engine_2_00_01

# Where the XDAIS package is installed.
#XDAIS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/xdais_6_00_01
XDAIS_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/xdais_6_00_01

# Where the DSP Link package is installed.
#LINK_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dsplink_140-05p1
LINK_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/dsplink_140-05p1

# Where the CMEM (contiguous memory allocator) package is installed.
#CMEM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/cmem_2_00_01
CMEM_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/cmem_2_00_01

# Where the codec servers are installed (dm6446) or codecs (dm355)
ifneq ($(PLATFORM),dm355)
   CODEC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dm6446_dvsdk_combos_1_3! 4
else
   #CODEC_INSTALL_DIR =$(DVSDK_INSTALL_DIR)/dm355_codecs_1_12_000
   CODEC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/dm355_codecs_1_12_000
endif

# Where the RTSC tools package is installed.
XDC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/xdc_3_00_02

# Where Framework Components product is installed
#FC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/framework_components_2_00_01
FC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/framework_components_2_00_01

# Where DSP/BIOS is installed
#BIOS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/__BIOS_VERS__
BIOS_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/__BIOS_VERS__

# The directory that points to your kernel source directory.
LINUXKERNEL_INSTALL_DIR=/home/zyang1/workdir/lsp/ti-davinci

# The prefix to be added before the GNU compiler tools (optionally inc!
luding
# path), i.e. "arm_v5t_le-" or "/opt/bin/arm_v5t_le-".
MVTOOL_DIR=/db/toolsrc/library/vendors2005/mvl/arm/mvl4.0.1-root-new//montav
ista/pro/devkit/arm/v5t_le
MVTOOL_PREFIX=$(MVTOOL_DIR)/bin/arm_v5t_le-

# Where to copy the resulting executables and data to (when executing 'make
# install') in a proper file structure. This EXEC_DIR should either be
visible
# from the target,

RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355

2008-06-23 Thread YangZhijun 

HI, 

I reinstalled my Ubuntu linux OS, and the Apr 15 updates of DVEVM software from 
TI website. But I still cannot compile the kernel using kernelkit as I did 
successfully with the old version before. Here is the command (line wrap on) 
causing the problem,

[EMAIL PROTECTED]:/media/hda5/home/zyang1/workdir/lsp/ti-davinci$ make ARCH=arm 
CROSS_COMPILE=arm_v5t_le- uImage  CHK include/linux/version.h  HOSTCC  
scripts/basic/fixdep  HOSTCC  scripts/basic/split-include  HOSTCC  
scripts/basic/docproc  SPLIT   include/linux/autoconf.h -> include/config/*  CC 
 scripts/mod/empty.o/bin/sh: arm_v5t_le-gcc: command not foundmake[2]: *** 
[scripts/mod/empty.o] Error 127make[1]: *** [scripts/mod] Error 2make: *** 
[scripts] Error 2
By the way, in the same directory I can run the following two commands without 
problem,

make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_evm_defconfigmake 
ARCH=arm CROSS_COMPILE=arm_v5t_le- checksetconfig
In the new guide I notice that it seems there is a subdir linux-2.6.10_mvl401 
in /home//workdir/lsp/ti-davinci in which one should do compilation 
of the kernel, but I cannot find this subdir. 

You should have the following files (these are the Apr 
15 updates)
 
dvsdk_setuplinux_1_30_00_40.bin
mvl_4_0_1_demo_lsp_setuplinux_01_20_00_014.bin
xdc_setuplinux_3_00_02_14.bin


Yes, I have these updates.

The dvsdk_setuplinux_1_30_00_40.bin and xdc_setuplinux_3_00_02_14.bin 
files you install to your working directory - the 'xdc' goes 'inside' the dvsdk 
directory so you must install dvsdk first. The Rules.mak file in the dvsdk 
directory needs editing to point to toolchain & kernel 
source.

I did these according to the new guide, so it should be all right. The 
following is my Rules.make file,

#
# This make variable must be set before the demos or examples
# can be built.  It must be set to either dm355 or dm6446
#
PLATFORM=dm355
ifndef PLATFORM
   $(error PLATFORM must be set in Rules.make to dm355 or dm6446 before 
building the demos)
endif


# The installation directory of the DVSDK  dvsdk_1_30_00_40.
DVSDK_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40

# For backwards compatibility
#DVEVM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)
DVEVM_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40

# Where the Codec Engine package is installed.
#CE_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/codec_engine_2_00_01
CE_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/codec_engine_2_00_01

# Where the XDAIS package is installed.
#XDAIS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/xdais_6_00_01
XDAIS_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/xdais_6_00_01

# Where the DSP Link package is installed.
#LINK_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dsplink_140-05p1
LINK_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/dsplink_140-05p1

# Where the CMEM (contiguous memory allocator) package is installed.
#CMEM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/cmem_2_00_01
CMEM_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/cmem_2_00_01

# Where the codec servers are installed (dm6446) or codecs (dm355)
ifneq ($(PLATFORM),dm355)
   CODEC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dm6446_dvsdk_combos_1_34
else
   #CODEC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dm355_codecs_1_12_000
   CODEC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/dm355_codecs_1_12_000
endif

# Where the RTSC tools package is installed.
XDC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/xdc_3_00_02

# Where Framework Components product is installed
#FC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/framework_components_2_00_01
FC_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/framework_components_2_00_01

# Where DSP/BIOS is installed
#BIOS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/__BIOS_VERS__
BIOS_INSTALL_DIR=/home/zyang1/dvsdk_1_30_00_40/__BIOS_VERS__

# The directory that points to your kernel source directory.
LINUXKERNEL_INSTALL_DIR=/home/zyang1/workdir/lsp/ti-davinci

# The prefix to be added before the GNU compiler tools (optionally including
# path), i.e. "arm_v5t_le-" or "/opt/bin/arm_v5t_le-".
MVTOOL_DIR=/db/toolsrc/library/vendors2005/mvl/arm/mvl4.0.1-root-new//montavista/pro/devkit/arm/v5t_le
MVTOOL_PREFIX=$(MVTOOL_DIR)/bin/arm_v5t_le-

# Where to copy the resulting executables and data to (when executing 'make
# install') in a proper file structure. This EXEC_DIR should either be visible
# from the target, or you will have to copy this (whole) directory onto the
# target filesystem.
EXEC_DIR=/home/zyang1/workdir/filesys/opt/dvsdk/dm355


You can then extract mvl_4_0_1_demo_lsp_setuplinux_01_20_00_014.bin, which 
contains 
the file DaVinciLSP-01_20_00_014.tar.gz which is the kernel source. You need to 
extract, copy & build this code 
 
I did these according to the Guide, so it is same as you said and should be all 
right.


You should then be able to build the dvsdk 
stuff.

Unfortunately I still cannot build the kernel. Any comment is appreciated. 

Many thanks. 

Michael


Subject: RE: problem to build the new Linux kernel using the updated DVSDK v1.3 
 for DM355
Date: Mon,

RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355

2008-06-16 Thread Phil Quiney 
Hi,
 
I really need to see the exact error here
 
Did you also update the kernel source?
 
I don't understand how updating the DVSDK affects the kernel build - the two 
are independant.
 
You should have the following files (these are the Apr 15 updates)
 
dvsdk_setuplinux_1_30_00_40.bin
mvl_4_0_1_demo_lsp_setuplinux_01_20_00_014.bin
xdc_setuplinux_3_00_02_14.bin
 
Do get the assiciated release notes and the sprue73a.pdf document and take note 
of the changes, especially kernel arguments for the new kernel.
 
The dvsdk_setuplinux_1_30_00_40.bin and xdc_setuplinux_3_00_02_14.bin files you 
install to your working directory - the 'xdc' goes 'inside' the dvsdk directory 
so you must install dvsdk first. The Rules.mak file in the dvsdk directory 
needs editing to point to toolchain & kernel source.
 
You can then extract mvl_4_0_1_demo_lsp_setuplinux_01_20_00_014.bin, which 
contains the file DaVinciLSP-01_20_00_014.tar.gz which is the kernel source. 
You need to extract, copy & build this code & then edit the Rules.mak file in 
the DVSDK to point to it.
 
You should then be able to build the dvsdk stuff.
 
/bin/sh is the shell - it is possible that your toolchain is corrupt but 
without the exact output of the command it is difficult to say
 
Regards
 
Phil Q
 
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com  

 



From: YangZhijun [mailto:[EMAIL PROTECTED] 
Sent: 15 June 2008 22:59
To: Phil Quiney; davinci-linux-open-source@linux.davincidsp.com
Subject: problem to build the new Linux kernel using the updated DVSDK v1.3 for 
DM355


Hi Phil, 

With your help I've gone through the getting started guide of the DM355 DVEVM 
software coming with the board. But now I have an issue again, after I 
uninstall the old version of DVSDK and install the new version from TI's new 
software update website.

The problem is that I cannot compile the kernel using the following command in 
kernelkit, as I successfully did for the old version, 

make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage

After a long compilation process I finally got something like, 

/bin/sh: arm_v5t_le-gcc: no such file ..

In my .bashrc I have already had:

EXPORT PATH="/media/hda1/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/bin:
  /media/hda1/opt/mv_pro_4.0.1/montavista/pro/bin:
   
/media/hda1/opt/mv_pro_4.0.1/montavista/common/bin:$PATH"

which is okay to compile the old kernel in kernelkit. 

I found that in /opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/bin I have 
arm_v5t_le-gcc, but I don't know why kernelkit try to find it in /bin/sh? what 
is that? Thanks for your help.

Best regards,

Michael



 





Date: Tue, 10 Jun 2008 08:16:22 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; davinci-linux-open-source@linux.davincidsp.com
CC: 
Subject: RE: how to compile own source code for DM355


Hi,
 
There are several ways of producing the root filesystem that I can 
think of (& some that I actually tried)
 
1/ Use LTIB (since you mentioned it) - it works fine - you need to 
force it to use 'external' kernel source and point it to the compiler from the 
DM355 MV installation. There are other 'free' tools out there that do this sort 
of thing, 'buildroot' being one that comes to mind. I went with LTIB basically 
because we use it for the Freescale platforms we have so it was familiar.
 
2/ Pay MV some money & license DevRocket. That will produce the file 
system as MV intended for the distribution.
 
3/ Invoke rpm manually to install the packages that produce the file 
system. This is basically what DevRocket does but you get the added fun of 
resolving the dependancies for yourself.
 
4/ Start with the root filesystem that is part of MV pro. Cut it down 
with 'rm' till you end up with something that you find suitable. I wouldn't 
recommend doing this but it is possible.
 
 
Of the above, I started with 4/, then tried 1/. Then went on to 2/ and 
once I had figured out what DevRocket did wished I had tried 3/ although the 
dependancy thing would have probably got to me in the end ;-)
 
Regards
 
Phil Q
 
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com  

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Amit 
Nehra
Sent: 10 June