Ti OMAP 3530 PSP compile note (3)

It turns out wrong!

 

In the early stage, I had a hard time following the so-called experience. I compiled uboot, kernel, and so on. Later I compiled devkit8000 with some kernel and boot code.

Later, I saw a dvsdk. I looked at the instructions and added the dvsdk_3_01_00_10 version. It was easy to install and run. It was a graphical interface. It seemed that I could install it under SSH or other command lines.

During this period, a bunch of things were downloaded from Ti, such as the c6x DSP compilation tool.

 

After the installation is complete, you need to set some internal environment variables. In rules. Make, the most important ones are:

 

Dvsdk_install_dir =/home/WPL/dvsdk/dvsdk_3_01_00_10

......

Codegen_install_dir =/opt/Ti/c6000cgt6.1.12/

......

Omap3503_sdk_install_dir =/home/WPL/OMAP/AM35x-OMAP35x-PSP-SDK-03.00.01.06

......

Cstool_dir =/home/WPL/OMAP/arm-2009q1

 

Install and specify the corresponding directories for PSP, arm tool-chain, C6000 tool-chain, and dvsdk.

 

Note: codec_install_dir = $(dvsdk_install_dir)/cs1omap1_01_00

 

This is the original method, but when I installed the cs1omap1_01_00 package, it was not actually installed in the dvsdk directory, so in order to save trouble, I set up a soft connection to the cs1omap directory under the dvsdk directory.

 

Why is it wrong? In fact, if you use the dvsdk, This is what Ti provides to developers to the unified environment, and the others are from the tool environment to the dependency package. Make help can see:

 

Available Build targets are:

Check: Make sure rules. Make is set up properly
Info: List versions of dvsdk Components

ALL: Build the components below
Clean: Remove files generated by the 'all' target

Cmem: Build the cmem kernel module for omap3530
Cmem_clean: Remove generated cmem files.

Dmai: Build dmai for omap3530_al
Dmai_clean: Remove generated dmai files.

LPM: Build LPM for omap3530
Lpm_clean: Remove generated LPM files.

Sdma: Build sdma for omap3530
Sdma_clean: Remove generated sdma files.

Demos: Build the dvsdk demos for omap3530
Demos_clean: Remove generated dvsdk demo files.

Dvtb: Build dvtb for omap3530
Dvtb_clean: Remove generated dvtb files

The following targets have to be explicitly built and cleaned:

Everything: rebuild everything including below targets
Note: C6000 code Gen tools are required
Clobber: Remove all generated files
Note: C6000 code Gen tools are required

Dsplink: Configure and build DSP link for omap3530 arm and DSP
Note: C6000 code Gen tools are required
Dsplink_arm: Configure and build DSP link for omap3530 arm
Dsplink_dsp: Configure and build DSP link for omap3530 DSP
Note: C6000 code Gen tools are required
Dsplink_samples: Build DSP link arm and DSP sample applications for omap3530
Note: C6000 code Gen tools are required
Dsplink_clean: Remove generated DSP link files
Note: C6000 code Gen tools are required

Codecs: Build codec servers for omap3530
Codecs_clean: Remove generated codec server files

Uboot: Build uboot for omap3530
Uboot_clean: Remove generated uboot files

Linux: Build Linux kernel uimage for omap3530
Linux_clean: Remove generated Linux kernel files

Install: Install binaries to/home/WPL/workdir/filesys/opt/dvsdk/omap3530
Dmai_install: Install dmai binaries to/home/WPL/workdir/filesys/opt/dvsdk/omap3530

Ce_examples: Build codec engine examples for omap3530
Note: C6000 code Gen tools are required
Ce_examples_clean: Remove codec engine examples
Note: C6000 code Gen tools are required

 

 

Therefore, run make Linux to compile the kernel (uboot is compiled first, and mkimage and other tools are estimated to be required), and run make uboot to compile uboot.

 

However, pay attention to the permission (compiler) during compilation, and use sudo if necessary.