How_to_build_an_arm/dsp_hello_world_program_on_the_davinci_evm resume

Solve the problem of missing dsplinkdata. Lib

I wrote how to build an arm/DSP Hello World Program on the DaVinci EVM,

In fact, the previous operation was not successful, because even though the compilation was successful, there was still a failed during the operation, and the specific error was not confirmed at the time and cannot be completed now.

At that time, it was a virtual machine directly provided by the Development Board. All the SDK tools in it were installed, but there were some files in it. I don't know if they deleted them or what happened. Two days ago, I set up my own development environment in Red Hat Enterprise 5. Of course, they all follow the get start document. Refer to the previous article on Samba NFS software installation under Red Hat Enterprise 5.

Today, I suddenly thought that there was a scale routine in it, because I mentioned this in TI's codec engine alogorith creator USR guide, and I will try again.

According to the http://processors.wiki.ti.com/index.php? Title = how_to_build_an_arm/dsp_hello_world_program_on_the_davinci_evm

During compilation in this article, the following error may be prompted, that is, the dsplinkdata. Lib file cannot be found,

After trying a lot of methods, I finally found the ultimate solution and wrote it for reference.

Method of writing failure first:

Failed 1:

For example, if this file is not ready for use, you can directly create a. txt file and rename it as dsplinkdata. Lib. The result shows that the file length is too short because the new file is empty,

Since the file length is too short, it will be extended. Just copy something into it. This is the general line. Then you will be prompted that the *** cannot be found. The *** here may be a word you copied into the object. It is estimated that he uses the file pointer to get it in it. This method won't work.

Failure 2:

Copy the existing dsplink. Lib file and rename it to the result of dsplinkdata. Lib. More error codes are displayed... Speechless

Find information http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/29343.aspx

TMS320DM6446 dvevm v1.30 Getting Started Guide A.5 rebuilding DSP/BIOS Link re-generates dsplinkk. Ko and other files without the dsplinkdata. Lib file,

However, one note is that the command sh-F buildmodule. Sh is used to re-compile the DSP/BIOS in the file.

There are several other files in the same folder, which may be useful for research.

Use text edit or other text editing tools to open and view each file. These documents are well written, and the path of each file is described in it.

Buildmodule. Sh script to build the kernel module

Dsplinkcfg CILS Perl script to create build configuration

Dsplinkenv sets the necessary environment for DSP/BIOS (TM) link development

Dsplinkenv. Bash sets the necessary environment for DSP/BIOS (TM) link development

Dspmake builds the DSP side libraries, samples and testsuite for OMAP.

Dspprobemake sets the necessary environment for DSP/BIOS (TM) link development.

The dspmake file is useful here, and you can see its function to build the DSP side libraries samples and testsuite. You can generate a DSP-side library, routine, and so on. This is what we want.

The following error message is displayed when you execute dspmake.

Compiling failure. C...
/Bin/sh: C: ti-toolsC6000cgtoolsbincl6x: Command not found
Make [3]: *** [failure. C. rel] Error 127
Make [2]: *** [objrel] Error 2
Make [1]: *** [gen. objrel] Error 2
Make: *** [base. objrel] Error 2

This may be because I chose a Windows platform during configuration. It doesn't matter. I have set it in the article on how to build an Hello world, it's a big deal to find the corresponding file compilation under XP.

Note that all the files mentioned above are in the $ (dsplink)/etc/host/scripts/Linux/path. To get to XP, you need to switch to the corresponding folder, for example, $ (dsplink) /etc/host/scripts/msdo/The dspmake below. bat

The following is my DSP/BIOS link configuration file, which may not be completely consistent. This file can be used to generate library files and examples, which are exactly what I need.

See: e: \ dsplink_140-05p1 \ packages \ dsplink \ config \ currentcfg. mk

:::::::::::::::::::::::::::::::::::::::: ::::::::::::::::::::
The selected configuration is:

Gpp OS = Linux
Dsp OS = dspbios
Gppdistribution = davinci_mvlpro4.0
Gpposversions = 2.6
Dspdistribution = c64xxp_5.xx_windows

Gppplatform = davinci
Dspplatform = davinci

Use_proc = 1
Use_pool = 1
Use_policy = 1
Use_mpcs = 1
Use_ringio = 1
Use_mplist = 1
Use_chnl = 1
Use_msgq = 1

Trace = 1
Profile = 0
Probe = 0

:::::::::::::::::::::::::::::::::::::::: ::::::::::::::::::::
Edit GPP and DSP distribution files for user specific path
Settings for OS base Directory, tool chain path etc

Edit GPP distribution file:
E: \ dsplink_140-05p1 \ packages \ dsplink \ make \ Linux \ davinci_mvlpro4.0.mk
Edit DSP distribution file:
E: \ dsplink_140-05p1 \ packages \ dsplink \ make \ dspbios \ c64xxp_5.xx_windows.mk

Then gmake-S release in the corresponding samples folder.

E: \ dsplink_140-05p1 \ packages \ dsplink \ etc \ host \ scripts \ msdos> Cd % dsplink % \ DSP \ SRC
\ Samples

E: \ dsplink_140-05p1 \ packages \ dsplink \ DSP \ SRC \ samples> gmake-S release

The output of the specific routine is still to be verified. write these down first...