Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

Build SysLink 2.2x examples in CCSv5

$
0
0

Hi,

thanks to your help I can run SysLink 2.2x examples on OMAP3530, builded in command line. Now I'd like to use CCSv5 for SysLink project, I supose it could be easier to understand it.

So I have to ask again for your help.Informations presented here  http://processors.wiki.ti.com/index.php/Creating_CCS_Project_for_SysLink_samples are not enough for me, because SysLink 2.2x examples are different from samples in 2.1x and I have not enough advanced to deal with it.

I started with slave DSP side, as it is in mentioned tutorial:

  • I created new CCS Project named Hello_world_DSP,
  • Output type: Executable,
  • Device: Family: C6000; Variant: Generic devices, Generic C64x+
  • Advanced settings: I choosed compiler from filesystem, which I used in command line building (TI v7.2.2) and Output format: eabi(ELF),
  • Project templates: SYS/BIOS > Typical

In the next window I should add RTSC products, but CCS doesn't recognize them. I read in some thread that directory names have to be default. So I added earlier in preferences to discovery path my main directory with installed tools in directories: bios_6_34_03_19, ipc_1_25_01_09, xdctools_3_24_03_33. It doesn't work. I tried also add to discovery path each directory of tools, but it also didn't helped. Selecting tool from filesystem during project creation shows e.g. for XDCtools: No tools selected! Please select a directory that contains the XDCtools installation. Adding SysBios and IPC show in Other Repositories category branch.There was no such a problem with adding CGT in Advanced settings, CCS detected new TI v7.2.2.

Could you help with this step?


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>