• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 250 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

After installing CCSv4, cannot build CCSv3 version. XDCException: xdc.PACKAGE_NOT_FOUND

Eddie3909
Guru 10385 points

Hi

I installed CCSv4 but had to build in CCSv3.3 for a release (haven't got enough testing on CCSv4 to do production releases). I did the ritual of deleting all CCS generated files and folders. When I compile in CCS3.3, I get the error below. I think the problem is that the XDC package is for CCSv4 and not CCSv3.3 (see below in bold). I compared the output to another PC that compiles CCSv3.3 and it was using XDC package path C:\dvsdk_1_11_00_00_DM648\xdc_2_95_02.

How do I change the XDC package path?

Thanks


**************CCS v3.3 output********************************************************************************

  • 0
    Expert 1200 points

    i have to assume the implicit install of the XDC add on package altered all existing CCS installs it could find and is able to manage.

     

    the XDC version used by CCS 3.xx is determined by the CCS version-info dialog and its child dialog for the compiler and tools settings.

    you should be able to adjust the build environment to your needs. please be aware that this settings are processor/family dependent in the IDE.

  • 0 in reply to Alexander Stohr
    Guru 10385 points

    Thanks Alexander

    I didn't even think of checking the CCS v3 component manager. It appears CCSv4 changed the XDC version but left everything else unchanged (i.e. BIOS, CGT).

    Had to also restart v3 after changing the component manager settings.

    Now to get the load to manufacturing. Wow, that was a ruch[:O]

    Hope you have a great day![:Y]

    FYI for those reading this, I get a warning below that TI has never told me why, but the code seems to work.

    making package.mak (because of package.bld) ...
    generating interfaces for package xdcconfig (because package/package.xdc.xml is older than package.xdc) ...
    configuring tase_lt_vps.x64P from package/cfg/tase_lt_vps_x64P.cfg ...
    Warning: incompatible use of package 'xdc.bld': imported xdc.bld [1,0,0,0,1183011756898], ti.pmi was built with xdc.bld [1, 0, 1], ti.bios was built with xdc.bld [1, 0, 1]; incompatible use of package 'xdc': imported xdc [1,1,0,0,1183011749422], ti.rtdx was built with xdc [1, 1, 1, 0], ti.pmi was built with xdc [1, 1, 1, 0], ti.bios was built with xdc [1, 1, 1, 0]
    Adding the following line to your configuration script: