• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 962 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.

RTOS/EVMK2G: Getting errors compiling the generic examples provided in the Resource Explorer

Roger Davis37
Intellectual 510 points
Part Number: EVMK2G
Other Parts Discussed in Thread: 66AK2G02, SYSBIOS

Tool/software: TI-RTOS

After floundering around with other problems (see my other posts), I came upon how to find actual examples for the EVMK2G platform.  (For those with similar problems, I had to navigate to "View->Resource Explorer Classic" which gave me the drop down list on the left side that is NOT provided from the Resource Explorer that comes up automatically when you first install.)

Then, I selected "SYS/BIOS/Unclassified Devices" in the drop down list.  I then installed and compiled three different  example projects and they all had the same basic compilation errors that I cannot figure out.

I installed and compiled:

"66AK2G02 - Cortex A [ARM] - GNU Target Examples - Typical"

"K2GEVM - Cortex A [ARM] - GNU Target Examples - Generic Examples - Hello Example"

"K2GEVM - Cortex A [ARM] - GNU Target Examples - Generic Examples - Semi-Hosting Example"

All of these failed to compile for similar reasons:

Description Resource Path Location Type
gmake: *** No rule to make target 'build-1343973039', needed by 'configPkg/compiler.opt'. typical_66AK2G02_CortexA C/C++ Problem
gmake: Target 'all' not remade because of errors. typical_66AK2G02_CortexA C/C++ Problem
gmake[1]: *** [build-1343973039-inproc] Error 1 typical_66AK2G02_CortexA C/C++ Problem
recipe for target 'build-1343973039-inproc' failed subdir_rules.mk /typical_66AK2G02_CortexA/Debug line 12 C/C++ Problem
xdc.cfg.Program : The package 'ti.sysbios.knl' is not compatible with XDCtools used in this build. Please either use XDCtools compatible with that package, or update the product containing that package, or rebuild the package with XDCtools 3.50 or later. .xdchelp /typical_66AK2G02_CortexA line 71 C/C++ Problem

SInce I am using XDCtools 3.50.03.33, I don't believe that is the issue.  I got these errors after installing ccs_setup_7.3.0.00019.exe and ti-processor-sdk-rtos-k2g-evm-04.01.00.06-Windows-x86-Install.exe and carefully following the instructions in 

  • 0
    TI__Guru 65405 points
    Hi Roger,

    Our team will need some time to gather data in the lab. Please allow us a few days and we will get back to you.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Intellectual 510 points

    Okay.  One thing that I discovered that might be helpful is looking at the Main.xs and Program.xs it looks through XDC versions to flag the error that I appear to be getting.  Even though I'm using XDCTools 3.50, there are also directories C:/ti/xdctools_3_32_01_22_core and C:/ti/xdctools_3_32_01_25_core.  I'm wondering if the loop in Program.xs is confused by these other packages being on the system.  Not sure why they are there except maybe based on what was selected when Code Composer was installed.

    Here's the loop:

    for (var i = 0; i < xdc.om.$modules.length; i++) {
      var mod = xdc.om.$modules[i];
      /* checking package versions to flag instance modules built with
      * 3.32 or older. Their header files are incompatible.
      */
      if (!mod.$hostonly && mod.$used && !mod.$$nortsflag) {
        if (mod.$$instflag && mod.PROXY$ != 1) {
          var vers = pkgVers[mod.$package.$name];
          if (vers == undefined) {
            vers = Packages.xdc.services.global.Vers.getXdcString(
                mod.$package.packageBase + "/package/package.defs.h");
          }
          pkgVers[mod.$package.$name] = vers;
          if (vers < "xdc-D00" || vers >= "xdc-a00") {
             Program.$logFatal("The package '" + mod.$package.$name
             + "' is not compatible with XDCtools used in this "
             + "build. Please either use XDCtools compatible with "
             + "that package, or update the product containing that "
             + "package, or rebuild the package "
             + "with XDCtools 3.50 or later.", Program);
          }
        }
        _targMods.push(mod);
      }
    }

    Also, when I grep for "xdc-" which seems to be the pattern being searched for in the three XDC directories, I get these pattern matches in various files in the directory:

    in C:/ti/xdctools_3_32_01_22_core:

    xdc-B21

    xdc-A65

    in C:/ti/xdctools_3_32_01_25_core:

    xdc-B24

    xdc-A65

    in C:/ti/xdctools_3_50_03_33_core  (the one selected in my build):

    xdc-D20

    xdc-A65

  • 0 in reply to Roger Davis37
    TI__Guru* 95265 points
    Hi,

    For the TI Processor SDK RTOS on K2G, the latest release is 4.1. All the driver examples are built with:
    - CCS 7.2
    - XDC_VERSION=3_32_01_22_core
    - BIOS_VERSION=6_46_05_55

    Certainly, you can try those examples directly from CCS resource explorer, like mentioned from processors.wiki.ti.com/.../Processor_SDK_RTOS_Examples. I felt there is a gap that we didn't explicitly mention the toolset used. With the 3.50.2.20 XDC I have the same built error as you reported. With the above toolset used for Rel 4.1, I have no build error. We will update the wiki page.

    Regards, Eric
  • 0 in reply to lding
    Intellectual 510 points

    Switching from XDC 3.50 to XDC 3.32 fixed the compilation error.  Thanks

    Now back to why I can't debug the application which is another thread.