Hello Brad,
Checking the Component Manager, I do have several buid toos installed,
and specifically the 'Texas instruments c6000 code generation tools' for
TMS320C64xx. Anyway, the project .pjt I'm trying to open has not been
created by me but it has been generated during the compilation of the
codec server.
Is there any way to open this project? or, otherwise, what files do I
need to include if I create my own .pjt project in CCS, in order to be
able to debug the codec?
Thank you very much,
Jon
Griffis, Brad escribió:
What build tools have you specified for 64x in the component manager?
(Help -> About -> Component Manager) The error message says you
don't have any specified.
------------------------------------------------------------------------
*From:* [email protected]
[mailto:[email protected]] *On
Behalf Of *Jon Arróspide
*Sent:* Friday, February 13, 2009 10:55 AM
*To:* [email protected]
*Subject:* How to debug codec in CCS
Hello all,
I'm using DM6446 to program video analysis algorithms. For the moment,
I've compiled the example SCALE from the codec examples, and I've
created a codec server for it. Now I want to debug the remote codec
that is being executed in the DSP in the Code Composer Studio. I've
read in some posts (see below) that it is possible just to open the
.pjt file created in the package folder of the server. However, if I
try to open it, I get the following error in the CCS:
/"No build tools for the target specified in this project were found.
Cannot open project ...\servers.gti.scale.pjt". Please use Component
Manager to ensure the appropriate project server and build tools are
selected"
/I have compiled the server in a debug mode for C64P and MVArm9. Is
there something I'm missing? Is there any other way to debug the codec
in CCS?
Thank you in advance,
Jon
*Re: Re: RE: How to debug codec server using CCS*
cs
Tue, 20 May 2008 22:11:37 -0700
Hi , I use Fedora Core 8 as my development environment. I use TI's
cross-compiler tools for ARM , DSP , XDC ,
framework_components_1_10_04 , dvevm_1_20 , to build codec server and
debug DSP side code. The other tools such as gmake, automake , ......
, is just from FC8 . They work ok. I work under windows ,using vmware
5.5 and SSH Secure Shell to transfer file between windows and linux
and using CCS 3.3 and SEED-XDS560USB to link evm board. I use the
following steps to debug dsp server .
1. setup all the tools under linux.
2. fix user.bld file. set C64P.rootDir , MVArm9.rootDir to correct
path , and set Build.targets only C64P , because I want codec engine
run only on dsp side.
3. fix xdcpath.mak , modify the parameter to right path.
4. fix package.bld in your codec package( xxx.yyy.zzz.vidddec_copy )
and your codec server ( my_copy ). set Pkg.attrs.profile = "debug";
and rebuild codec package and codec server
5. modify your app code following the wiki's instruction.
6. copy your codec server and arm side app to the evm board using NFS.
7. exec the app on the board , when the app pause at getchar() after
Engine_open()
8. open CCS , and connect arm and dsp. confirm they should not be halted.
9. copy full codec server files and codec package files to windows
after compiled .
10. open ccs for dsp , and open the project in ".\my_copy\package\"
11. add viddec_copy.c to your project.
12. load symbols (my_copy.x64P file)
13. set breakpoint where u want to stop.
14. continue arm side app by serial console.
15. debug your code
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
