CCSV6 Chip Support Library settings/importing problem

Timo,

Despite the recommended/tested version of this CSL is CCSv5, I was able to make the CSL_USB_CdcExample project work on my CCSv6.1 (or at least to the extent I was able to test, as I do not have a USB CDC driver installed for the C5000 device).

I simply imported the project above and was sure to select both the options "Copy Projects to workspace" and "Automatically import referenced projects...".

I also had previously installed the corresponding DSP/BIOS version required by the CSL (5.41.2.14) - a link is available from the CCS App Center (menu View --> CCS App Center).

One difference is that I am using Windows 7, but as far as I know Windows 8.1 works just as well. In any case, CCS should not freeze during project import. Perhaps you could try to use a different workspace or follow other troubleshooting options shown at the page below?
processors.wiki.ti.com/.../Troubleshooting_CCSv6

The target configuration instructions seem somewhat odd, given that you can easily create your own configuration by following instructions shown at section 2.2 of the page below:
processors.wiki.ti.com/.../Debug_Handbook_for_CCS

Hope this helps,
Rafael

Thanks for your advice!

I don't know which one is better, you said "select both the options "Copy Projects to workspace" and "Automatically import referenced projects..."." but installation guide at page 11 says "Leave the “Copy projects into workspace” box unchecked. " 

I deleted all workspaces and .metadata files and created new, because there was a lot of errors again. But no, this not work for me. When I tried to import files (installation guide says):

"To keep the dependency among projects, we highly recommend importing all the projects in one
time (by default)."

I did it. But when importing, I see myriads errors in summary windows:

"Unrecognized product of type 'com.ti.rtsc.XDAIS' is required by project 'programmer' - please install at least one product of this type before building this project."


Now CCS  stucking, C/C++ indexer shows 2%. I don't know why this is made so difficult. If I follow installation guides or what else (ex. installation manual, I can't work this. Maybe installation guide exist errors.

Nex I try to import only one example, but how can I know what libraries must import too?

There is capture my desktop:

There is capture my settings, maybe this is too wrong settings:

I tried to import only one project, but this not work too. Advises from installation guide not work. And if I try only one project, this not work too. I can' figured what is wrong. Here there are so many different options so you can not know how they should be.

Timo

Hi,

Keep in mind you are working with a version of CCS that was not used originally when the CSL package was created, therefore variations to the published process are happening.

Timo Matalalampi said:

I don't know which one is better, you said "select both the options "Copy Projects to workspace" and "Automatically import referenced projects..."." but installation guide at page 11 says "Leave the “Copy projects into workspace” box unchecked. " 

I see the confusion this creates, but some older software packages used to present several problems when its projects were copied to the workspace, which prevented them from being properly built. When I tested the options I sent it with the project you mentioned these issues did not happen.

Timo Matalalampi said:

"To keep the dependency among projects, we highly recommend importing all the projects in one
time (by default)."

Timo Matalalampi said:

Now CCS  stucking, C/C++ indexer shows 2%.

Despite the proposed way of importing projects work, the procedure I sent prevents that time and resource consuming experience. That is why I suggested enabling the option "Automatically import referenced projects..." when importing a single project. 

Timo Matalalampi said:

I did it. But when importing, I see myriads errors in summary windows:

"Unrecognized product of type 'com.ti.rtsc.XDAIS' is required by project 'programmer' - please install at least one product of this type before building this project."

These warnings show only on CCSv6, which does not install the discontinued XDAIS product anymore (the original CCSv5 version does not show these warnings). By the way, these warnings do not prevent the projects from properly building or working, as I could not identify any XDAIS components on them.

Timo Matalalampi said:

Maybe installation guide exist errors.

The user's guide shows the most conservative way to import the projects that works on CCSv5. This procedure also works for CCSv6 with the warnings and details you mentioned.

Timo Matalalampi said:

Nex I try to import only one example, but how can I know what libraries must import too?

Timo Matalalampi said:

I tried to import only one project, but this not work too.

One thing that was not clear from your posts: did you actually try to import the projects the way I mentioned with the options?

Regards,

Rafael

Thank you very much, Rafael!
I will try this and check your advices.

Regards,

Timo

Hi!

I got a compile exampleprogram , but next came to the following message: "C55xx: Error initializing emulator".

My desktop capture:

and Properties capture:

I note that Variant is not correct: TMS320C5505 (EZDSP5535 can be found in the menu).

I changed correct Variant:

and get warning: This project was created using a version of DSP/BIOS tools that is not currently installed: 5.41.2.14. Please install the DSP/BIOS tools of this version, or migrate the project to one of the supported versions.

compiling and things just get worse:

build log:

**** Clean-only build of configuration Debug for project CSL_USB_CdcExample_Out ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k clean
DEL /F  "CSL_USB_CdcExample_Out.out"
DEL /F "csl_usb_cdc_example.pp"
DEL /F "csl_usb_cdc_example.obj"
'Finished clean'
' '

**** Build Finished ****

**** Build of configuration Debug for project CSL_USB_CdcExample_Out ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../csl_usb_cdc_example.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_01_09/packages/ti/bios/include" --include_path="C:/ti/bios_5_42_01_09/packages/ti/rtdx/include/c5500" --include_path="C:/CSL/c55xx_csl/inc" --include_path="C:/CSL/c55xx_csl/ccs_v5.0_examples/usb/CSL_USB_CdcExample/Debug" --define="_DEBUG" --define=c5535 --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --asm_listing --preproc_with_compile --preproc_dependency="csl_usb_cdc_example.pp"  "../csl_usb_cdc_example.c"
'Finished building: ../csl_usb_cdc_example.c'
' '
'Building target: CSL_USB_CdcExample_Out.out'
'Invoking: C5500 Linker'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 -g --define="_DEBUG" --define=c5535 --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --asm_listing -z -m"CSL_USB_CdcExample_Out.map" --stack_size=0x200 --heap_size=0x400 -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/lib" -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" -i"C:/ti/bios_5_42_01_09/packages/ti/rtdx/lib/c5500" -i"C:/ti/bios_5_42_01_09/packages/ti/bios/lib" -i"C:/CSL/c55xx_csl/ccs_v5.0_examples/C55XXCSL_LP" -i"C:/CSL/c55xx_csl/ccs_v5.0_examples/usb/CSL_USB_CdcExample" -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/lib" --reread_libs --warn_sections --xml_link_info="CSL_USB_CdcExample_Out_linkInfo.xml" --rom_model --sys_stacksize=0x200 -o "CSL_USB_CdcExample_Out.out" "./csl_usb_cdc_example.obj" "../C5535.cmd" "../VC5505_USB.cmd"  -l"Debug/C55XXCSL_LP.lib" -l"rts55x.lib" -l"libc.a"
<Linking>
"../VC5505_USB.cmd", line 8: error: VEC memory range overlaps existing memory
   range DARAM0
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM0
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM1
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM2
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM3
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM4
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM5
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM6
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range DARAM7
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range SARAM0
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range SARAM1
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range SARAM2
"../VC5505_USB.cmd", line 9: error: DATA memory range overlaps existing memory
   range SARAM3
"../VC5505_USB.cmd", line 10: error: PROG memory range overlaps existing memory
   range SARAM4
"../VC5505_USB.cmd", line 10: error: PROG memory range overlaps existing memory
   range SARAM5
"../VC5505_USB.cmd", line 10: error: PROG memory range overlaps existing memory
   range SARAM6
"../VC5505_USB.cmd", line 10: error: PROG memory range overlaps existing memory
   range SARAM7
"../VC5505_USB.cmd", line 10: error: PROG memory range overlaps existing memory
   range SARAM8
fatal error: file
   "C:/CSL/c55xx_csl/ccs_v5.0_examples/C55XXCSL_LP/Debug/C55XXCSL_LP.lib<csl_cd
   c.obj>" has a Tag_Memory_Model attribute value of "2" that is different than
   one previously seen ("1"); combining incompatible files

>> Compilation failure
gmake: *** [CSL_USB_CdcExample_Out.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

I am even more confused now. Getting this work looks really hard.

Regards,

Timo

I cant' get changed dsp/bios to older version (5.42.1.09 -> 5.41.2.14) and compiler ver. to 4.3.9. Maybe this would have helped.
I must be try to something else.

Regards,

Timo

Hello! Thanks a lot of advices, Rafael! I get It now compiled without warnings or errors! I still have a lot to learn.

I created a new project and copy files to a current project folder. In addition I modified the .cmd -memory settings file. I used to help the error log.

Thanks,

Timo