首页 installguide_linux_omap3530

installguide_linux_omap3530

举报
开通vip

installguide_linux_omap3530 Document Template Version 1 Version1.60 Page1of21 INSTALLATIONGUIDE DSP/BIOS™ LINK OMAP3530 EVM LNK 173 USR Version 1.60 OCT 21, 2008 Page2of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE Thispagehasb...

installguide_linux_omap3530
Document Template Version 1 Version1.60 Page1of21 INSTALLATIONGUIDE DSP/BIOS™ LINK OMAP3530 EVM LNK 173 USR Version 1.60 OCT 21, 2008 Page2of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE Thispagehasbeenintentionallyleftblank. Page3of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. All products are sold subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment. TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TI’s standard warranty. Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except where mandated by government requirements, testing of all parameters of each product is not necessarily performed. TI assumes no liability for applications assistance or customer product design. Customers are responsible for their products and applications using TI components. To minimize the risks associated with customer products and applications, customers should provide adequate design and operating safeguards. TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right, copyright, mask work right, or other TI intellectual property right relating to any combination, machine, or process in which TI products or services are used. Information published by TI regarding third–party products or services does not constitute a license from TI to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI. Reproduction of information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an unfair and deceptive business practice. TI is not responsible or liable for such altered documentation. Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Mailing Address: Texas Instruments Post Office Box 655303 Dallas, Texas 75265 Copyright ©. 2003, Texas Instruments Incorporated Page4of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE Thispagehasbeenintentionallyleftblank. Page5of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE TABLEOFCONTENTS A. INTRODUCTION........................................................................ 7 1 Purpose ........................................................................................................ 7 2 Text Conventions.......................................................................................... 7 3 Terms & Abbreviations ................................................................................. 7 4 References ................................................................................................... 7 B. INSTALLATION ......................................................................... 8 5 Basic Installation.......................................................................................... 8 5.1 Installing Standalone DSP/BIOS™ and CGTools ......................................... 8 6 Creating development workspace................................................................. 8 7 Setting up Linux Workstation ..................................................................... 10 7.1 Building the kernel ...............................................................................10 7.2 U-Boot boot-loader ...............................................................................11 7.3 LPM ....................................................................................................11 7.4 Enable TFTP for downloading the kernel image to target............................12 7.5 Create target file system .......................................................................12 8 Configuring CCS.......................................................................................... 13 8.1 OMAP3530...........................................................................................13 C. WORKING ON TARGET PLATFORM .......................................... 14 9 OMAP3530.................................................................................................. 14 9.1 Configuring Kernel Parameters ...............................................................14 9.2 Configure the DSP/BIOS LINK ................................................................14 9.3 Using LPM............................................................................................14 10 Running the sample applications................................................................ 15 10.1 Copying files to target file system...........................................................15 10.2 Loading the kernel module: dsplinkk.ko ..................................................16 10.3 Loading the LPM module........................................................................16 10.4 Invoking the application ........................................................................17 10.5 Unloading the kernel module: dsplinkk.ko ...............................................20 D. ADDITIONAL INFORMATION .................................................. 21 Page6of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE TABLEOFFIGURES Figure1. Expected directory structure on development host..................................... 9 Figure2. Expected directory structure on the Linux workstation ..............................10 Page7of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE A. INTRODUCTION 1 Purpose DSP/BIOS™ LINK is foundation software for the inter-processor communication across the GPP-DSP boundary. It provides a generic API that abstracts the characteristics of the physical link connecting GPP and DSP from the applications. It eliminates the need for customers to develop such link from scratch and allows them to focus more on application development. This document provides the users necessary information to install DSP/BIOS™ LINK on the development host. This document corresponds to the engineering release Version 1.60 dated OCT 21, 2008. 2 TextConventions � This bullet indicates important information. Please read such text carefully. � This bullet indicates additional information. [ arg1 | arg2 ] In context of the commands, contents enclosed in square brackets are the optional arguments to the command. Different values of these arguments are separated by “|”. 3 Terms&Abbreviations CCS Code Composer Studio IPC Inter Processor Communication GPP General Purpose e.g. ARM DSP Digital Signal Processor e.g. TMS320C5510 CGTools Code Gen Tools, e.g. Compiler, Linker, Archiver 4 References 1. UserGuide_1_0_2.pdf PSP Linux release 1.0.2 User Guide 2. Various Documentation included with the OMAP3530 hardware. Page8of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE B. INSTALLATION 5 BasicInstallation The DSP/BIOS™ LINK is made available as a tar.gz file. To install the product follow thestepsbelow: 1. Unzip and untar the file dsplink_.tar.gz. � This document assumes the install path to be intheuserhomedirectory if working on a Linux PC. This path will be used in remainder of this document. � This document assumes the install path to be L:\dsplink ifworkingona WindowsPC. This path will be used in remainder of this document. � If the installation was done at different location, make appropriate changes to the commands listed in the document. It is advisable to archive the released sources in a configuration management system. This will help in merging: � The updates delivered in the newer releases of DSP/BIOS™ LINK. � The changes to the product, if any, done by the users. 5.1 InstallingStandaloneDSP/BIOS™andCGTools For compilation of DSP-side sources and applications for OMAP3530, the CGTools version 6.0.18 can be used. This release has been validated with DSP/BIOS™ version 5.32.04. The standalone DSP/BIOS™ and standalone CGTools are available for Linux platform as well. Refer to the URL mentioned below for getting the distribution of DSP/BIOS™ and the associated installation instructions. https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html The directory structure specified in Figure 1 is expected by the build system of DSP/BIOS™ LINK. If you install the tools to a different directory, you will also need to modify the make system and the scripts contained in the release package. You may need to copy the directories to create the structure expected for compiling sources. Refer to section on “Understanding the MAKE System” in the User Guide for details. 6 Creatingdevelopmentworkspace This document and the scripts included in the release assume the following directory structure on your development host: Page9of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE Figure1. Expected directory structure on development host � For Linux, the build system shipped with DSP/BIOS™ LINK assumes that the standalone DSP/BIOS™ is installed in the /opt/‘ti-tools/’ directory on the and CGTools is installed in the ‘ti-tools/c6000’ directory on the . � For the Windows development host, the build system shipped with DSP/BIOS™ LINK assumes that the standalone DSP/BIOS™ is installed in the ‘ti-tools\’ directory on the and CGTools is installed in the ‘ti- tools\c6000\’ directory on the . � To support multiple installations of DSP/BIOS with a single DSP/BIOS™ LINK DSP-side distribution file, a standard /opt/ti-tools/bios on Linux and c:\ti- tools\bios directory is used for the BIOS installation. This can be a soft link or copy to the actual DSP/BIOS installation directory. /opt/ti-tools c:\ti-tools bios c6000 cgtools bios_5_32_04soft link or copy bin include lib Page10of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE 7 SettingupLinuxWorkstation The description in this section is based on the following assumptions: 1. The workstation is running on Redhat Linux version 9.0 2. Services telnetd, nfsd, ftpd are configured on this workstation. 3. The workstation is assigned a fixed IP address. � The release package has been tested on RedHat Linux version 9.0. You may be able to build on a different version depending on the compatibility of the build tools in your version with version 9.0. � A fixed IP address is preferred, as the IP address needs to be specified while booting the target board. This allows the boot loader configuration to be saved in flash. This document and the scripts included in the release assume the following directory structure in your home directory on the Linux workstation: Figure2. Expected directory structure on the Linux workstation In this diagram: � represents the actual user name � represents the actual distribution of Linux being used. This section assumes that PSP 1.0.2 release is installed on the development workstation at ${HOME}/omap3530 7.1 Buildingthekernel 7.1.1 Toolchain 1. The tool chain arm-2007q3-51 can be downloaded from :- http://www.codesourcery.com/gnu_toolchains/arm/portal/package1786?@t emplate=release Un tar the tool chain and add the tool chain directory in your path. $ tar–xjvfarm-2007q3-51-arm-none-linux-gnueabi-i68 6-pc-linux- gnu.tar.bz2 $ exportPATH=$PATH:${HOME}/omap3530/arm-2007q3/bin /home/ dsplink kernel Toolchain Page11of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE 7.1.2 Kernel 1. Un tar the kernel that comes with the PSP_1.0.2 release. Build the kernel according to the PSP Linux User Guide document. Refer to the PSP u-boot related documentation on how to build the mkimage utility which is needed for creation of uImage. Along with the tool chain, location of mkimage utility should also be there in the path. $ tar–zxvfREL_OMAP35x_LINUX_PSP_1.0.2.tgz 7.2 U-Bootboot-loader Please refer the user guide to load the u.boot and x-loader to the target. REL_OMAP35x_LINUX_PSP_1.0.2/PSP_1_0_2/docs/OMAP35x/UserGuide_1_0_2.pdf. 7.3 LPM 1. Download the ti_bios_power,omap3530_bld.tar or ti_bios_power,omap3530_mod.tar present at http://www.sanb.design.ti.com/web/power/local_power_manager_1_20_EA /local_power_manager_1_20_00_12/ Untar the LPM source code (ti_bios_power,omap3530_bld.tar) and module (ti_bios_power,omap3530_mod.tar). $ tar-xvfti_bios_power,omap3530_bld.tar 2. Copy the LPM module (lpm_omap3530.ko) from $HOME/LPM/omap3530/lpm to target NFS. If the insmod step is giving error while inserting the module then the existing binaries needs to be re- compile with proper OS and tool chain. To build the LPM module modify the Makefile present at $HOME/omap3530/lpm/Makefile #KERNEL_DIR=theLinuxkernelsourcedirectory #TOOL_PREFIX=thetoolchaindirectoryanddecorat edname prefix ($(HOME)/arm-2007q3/bin/arm-none-linux-gnueabi-) #DSPLINK_REPO=therepositorywhichcontainsDSPL INK #DSPLINK_BLD=theDSP/BIOSLINKbuildvariant (Linux/OMAP/3530/RELEASE)or(Linux/OMAP/3530/DEBUG ) #LINK_INCS:=$(shellcat$(LINK_PATH)/PMGR_include s.txt) cd$HOME/LPM/omap3530/lpm make-srelease or make-sdebug Page12of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE 3. Download the ti_bios_power_test.tar from same location. Copy LPM On (lpmON.x470MV) and OFF (lpmOFF.x470MV) binaries in your target file system. ForDEBUGbuild: $HOME/LPM/ti/bios/power/test/bin/ti_platforms_evm3530/linux/debu g ForRELEASEbuild: $HOME/LPM/ti/bios/power/test/bin/ti_platforms_evm3530/linux/rele ase 7.4 EnableTFTPfordownloadingthekernelimageto target U-boot can be configured to download the kernel onto the target by various mechanisms: a. TFTP b. Serial Port This section configures the Linux development host as a TFTP server. Modify the ‘xinet.d/tftp’ file to enable TFTP: 1. Make the following changes: disable=no server_args=-s/tftpboot 2. Restart the network service $ /etc/init.d/xinetdrestart � The above configuration assumes that a directory ‘tftpboot’ has been created at the root ‘/’ directory. The files in this directory are exposed through the TFTP protocol. 7.5 Createtargetfilesystem The target device needs a file system to boot from. The file system can be exported to the target through NFS. 7.5.1 ExportingtargetfilesystemthroughNFS A directory on the development host can be setup and exported for this purpose. 1. $(HOME)/REL_OMAP35x_LINUX_PSP_1.0.2/PSP_1_0_2/bin contains the NFS file system nfs.tar.gz. tarxzvfnfs.tar.gz � Enter the command shown above in a single line. � You need to be ‘root’ to successfully execute this command. � The file system can be copied to a different location. In such a case ~/omap3530/target can be a soft link to the actual location. 2. libpthread libraries required for DSP/BIOS™ LINK are not available by Page13of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE default within the target file system. Copy this from the tool-chain. $ cp${HOME}/omap3530/arm-2007q3/arm-none-linux- gnueabi/libc/lib/libpthread*~/omap3530/target/lib � This step is not required if libpthread libraries are available by default in the target file system. 3. The directory ~/omap3530/target will be mounted as root directory on the target through NFS. To do so, add the following line to the file /etc/exports. /home//omap3530/target*(rw,no_root_squash) � Replace "/home/" in the path above with the actual path of your home directory on the development workstation. 8 ConfiguringCCS 8.1 OMAP3530 To use CCS for debugging the DSP side application, you will need to configure CCS to use both ARM and DSP with the OMAP3530. � CCS can attach to only ARM in the beginning. It can attach to the DSP only after the ARM-side application releases it from reset through a call to PROC_Start() . Page14of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE C. WORKING ON TARGET PLATFORM 9 OMAP3530 9.1 ConfiguringKernelParameters DSP/BIOS™ LINK requires a few specific arguments to be passed to the Linux kernel during boot up. 2MB of memory is used by DSP/BIOS™ LINK for communication between GPP and DSP, and for DSP external memory. This must be reserved by specifying 2MB less as available for the Linux kernel for its usage. 9.2 ConfiguretheDSP/BIOSLINK The build configuration command must be executed to configure DSPLink for the various parameters such as platform, GPP OS, build configuration etc. perldsplinkcfg.pl--platform=OMAP3530--nodsp=1- - dspcfg_0=OMAP3530SHMEM--dspos_0=DSPBIOS5XX--gppos =OMAPLSP-- comps=ponslrmc � For details please refer user guide. 9.3 UsingLPM When cache is enabled, a MMU fault is seen when one application is run followed by a run of another application. This issue is not seen when one application is run followed by a run of the same application. To overcome this issue the LPM module is used to power cycle the EVM between runs. Page15of21 Version1.60 DSP/BIOS™ LINK LNK 173 USR INSTALLATION GUIDE 10 Runningthesampleapplications Seven sample applications are provided with DSP/BIOS™ LINK for the OMAP3530 platform. All the sample applications are described in detail in the user guide. This section describes the way to execute the sample applications. The specific instructions shown below refer to the message sample. However, similar instructions can be used for the other applications also. The steps for execution of the samples are given below for execution with Linux running on the GPP. 10.1 Copyingfilestotargetfilesystem The generated binaries on the GPP side and DSP side and the data files must be copied to the target directory. The commands below demonstrate this for the ‘message’ sample application as reference. Appropriate sample directory name must be used for other sample applications. GPP Side For executing the DEBUG build, follow the steps below to copy the relevant binaries: $ cd~/dsplink $ cpgpp/export/BIN/Linux/OMAP/3530/DEBUG/messagegpp ../omap3530/target/opt/dsplink/samples/message $cpgpp/export/BIN/Linux/OMAP/3530/DEBUG/dsplinkk. ko ../omap3530/target/opt/dsplink/ For executing the RELEASE build, follow the steps below to copy the relevant binaries: $ cd~/dsplink $ cpgpp/export/BIN/Linux/OMAP/3530/RELEASE/messageg pp ../omap3530/target/opt/dsplink/samples/message $ cpgpp/export/BIN/Linux/OMAP/3530/RELEASE/dsplinkk .ko ../omap3530/target/opt/dsplink/ � Enter the commands shown above in single line. � By default Ring_
本文档为【installguide_linux_omap3530】,请使用软件OFFICE或WPS软件打开。作品中的文字与图均可以修改和编辑, 图片更改请在作品中右键图片并更换,文字修改请直接点击文字进行修改,也可以新增和删除文档中的内容。
该文档来自用户分享,如有侵权行为请发邮件ishare@vip.sina.com联系网站客服,我们会及时删除。
[版权声明] 本站所有资料为用户分享产生,若发现您的权利被侵害,请联系客服邮件isharekefu@iask.cn,我们尽快处理。
本作品所展示的图片、画像、字体、音乐的版权可能需版权方额外授权,请谨慎使用。
网站提供的党政主题相关内容(国旗、国徽、党徽..)目的在于配合国家政策宣传,仅限个人学习分享使用,禁止用于任何广告和商用目的。
下载需要: 免费 已有0 人下载
最新资料
资料动态
专题动态
is_086801
暂无简介~
格式:pdf
大小:198KB
软件:PDF阅读器
页数:21
分类:互联网
上传时间:2012-05-06
浏览量:26