• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2111 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

incompatible xdctools and sysbios

eok seob kim
Intellectual 340 points
Other Parts Discussed in Thread: SYSBIOS, OMAPL138

My configuration is CCS v5.4.0.00091(xdctools v3.25.00.48, sysbios v6.35.01.29).

I just opened a sysbios clock example after setting device c6000, variant OMAP-L1x & OMAPL138.

Target ti.targets.C674, Platform ti.platforms.evmOMAPL138, Build-profile release.

By the way, I got the following error.

//====================================================================================================================

incompatible use of package 'ti.platforms.evmOMAPL138'[in C:/ti/xdctools_3_25_00_48/packages/ti/platforms/evmOMAPL138]:version of the loaded package 'ti.platforms.evmOMAPL138' is [], while 'ti.sysbios' [in C:/ti/bios_6_35_01_29/packages/ti/sysbios] was built with 'ti.platforms.evmOMAPL138'

//====================================================================================================================

So I checked my CCS configuration, but I could not find out the wrong configuration.

I need your helps a lot !!

  • 0
    TI__Guru** 116020 points

    I have exactly the same set of software packages that you are using but don`t see the issue that you are reporting when I create an example clock project.Under Windows->Preferences, can you go into the Code composer studio menu and see if all the RTSC product have been recognize and the right version preferences have been set? I am moving this post to the CCS forum to see if someone else has seen this issue.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 340 points


    **** Build of configuration Debug for project clock ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all
    'Building file: ../clock.cfg'
    'Invoking: XDCtools'
    "C:/ti/xdctools_3_25_00_48/xs" --xdcpath="C:/ti/bios_6_35_01_29/packages;C:/ti/ccsv5/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.C674 -p ti.platforms.evmOMAPL138 -r debug -c "C:/ti/ccsv5/tools/compiler/c6000_7.4.2" --compileOptions "-g --optimize_with_debug" "../clock.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring clock.x674 from package/cfg/clock_p674.cfg ...
    js: "C:/ti/xdctools_3_25_00_48/packages/xdc/cfg/Main.xs", line 153: Error: incompatible use of package 'ti.platforms.evmOMAPL138' [in C:/ti/xdctools_3_25_00_48/packages/ti/platforms/evmOMAPL138/]: version of the loaded package 'ti.platforms.evmOMAPL138' is [], while 'ti.sysbios' [in C:/ti/bios_6_35_01_29/packages/ti/sysbios/] was built with 'ti.platforms.evmOMAPL138' [1, 0, 0, 1363059619440]
    Adding the following line to your program configuration script:
    environment['xdc.cfg.check.fatal'] = 'false';
    converts this incompatibility error into a warning. Please, check the documentation for the package xdc.cfg for more information.
    gmake.exe: *** [package/cfg/clock_p674.xdl] Error 1
    js: "C:/ti/xdctools_3_25_00_48/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

    I checked my configuration. but I got above error

  • 0 in reply to eok seob kim
    Intellectual 340 points

    I read above error comment and found out the following sentence.

    Adding the following line to your program configuration script:
    environment['xdc.cfg.check.fatal'] = 'false';

    So I added "environment['xdc.cfg.check.fatal'] = 'false';" to the last part of configuration script file "clock.cfg".

    The above error is removed....