// use this bashrc file in ue home/UserName folder to denote the cross compiler folder
#path Export export PATH=$PATH : /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le_gcc/bin export PATH=$PATH : /opt/mv_pro_4.0/montavista/pro/bin export PATH=$PATH : /opt/mv_pro_4.0/montavista/pro/common/bin ----------------------- Pls use some echo command to make sure the bashrc file is working. Thanks Ramesh. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, June 23, 2008 5:08 PM To: [email protected] Subject: Davinci-linux-open-source Digest, Vol 30, Issue 94 Send Davinci-linux-open-source mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Davinci-linux-open-source digest..." Today's Topics: 1. RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355 (ganesh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 23 Jun 2008 17:10:31 -0700 From: "ganesh" <[EMAIL PROTECTED]> Subject: RE: problem to build the new Linux kernel using the updated DVSDK v1.3 for DM355 To: "'YangZhijun'" <[EMAIL PROTECTED]>, <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-2022-jp" 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; [email protected] 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/<useracct>/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, 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, 16 Jun 2008 09:01:51 +0100 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [email protected] 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 <http://www.trinityconvergence.com/> _____ From: YangZhijun [mailto:[EMAIL PROTECTED] Sent: 15 June 2008 22:59 To: Phil Quiney; [email protected] 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 <http://get.live.cn/product/writer.html> _____ 用 Windows Live Spaces 展示个性自我，与好友分享生活！ <http://spaces.live.com/?page=HP> 了解更多信息！ [This e-mail is confidential and may be privileged. If you are not the intended recipient, please kindly notify us immediately and delete the message from your system; please do not copy or use it for any purpose, nor disclose its contents to any other person. Thank you.] ---ST Electronics Group--- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20080623/b1b3ad6a/attachment.htm ------------------------------ _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source End of Davinci-linux-open-source Digest, Vol 30, Issue 94 ********************************************************* _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
