Hi,
I promised I will get back with some explanation.
When you start CCS 3.3 open existing project (lala.pjt in examples/lala).
You should set up the files like on the attached image. All necessary files are
in the zipped file that I sent you before.
Basically, you should follow the steps like described on wiki:
http://wiki.davincidsp.com/index.php?title=Debugging_the_DSP_side_of_a_CE_application_on_DaVinci_using_CCS
I will add some brief explanation (in red):
First compile the new server with the above changes and copy all.x64P (server
is compiled, all you need is to copy
examples\servers\video_copy\video_copy.x64P to your NFS folder ) to your target
file system along with the audio_copy app.out (instead of this, you should use
examples\apps\video_copy\dualcpu\app.out) ARM application which launches this
server (as well as the in.dat file (copy this file also to the NFS) that the
ARM app needs). Then:
Start CCS (with a proper DM6446 configuration) and open the DSP side of
CCS.
Execute app.out on your Linux target.
Select Debug->connect.
Select File->load symbols->load symbols only, and choose the file all.x64P
on your host file system. (you should choose the file
examples\servers\video_copy\video_copy.x64P)
Load the CE.gel file into CCS. (it is located in servers\video_copy)
Set your breakpoints. Open other source files in CCS as needed to
accomplish this.
Select the "Release DSP" menu item from the CCS GEL menu.
Run the DSP (Press F5) to continue execution.
Note! Currently the ARM app.out may time out during the above process due to
CE using a timeout in DSP Link PROC_start(). We are halting the DSP so early
during initialization that the DSP Link "handshake" after loading a DSP image
doesn't take place. This means you only have a limited time to do the steps
above, and is one reason why using a GEL file is a good idea (you can add the
addition of your breakpoints in to this same GEL file to speed up the process
further). ---> do the 8 steps described above fast!!!
These steps above just have to be done one time. Due to the "new"
connect/disconnect features in CCS only steps 3, 7 and 8 needs to be done next
debugging session as long as CCS isn't closed (and step 4 if the DSP image is
changed, but there is a reload symbols option in CCS).
I hope this helps,
Regards,
Valentina
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search._______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
