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.

some xdc compiler error

Hi, I have some problem about using the xdctool to compiler, and the following is the detail about we try to recompiler the solution "soln14a_build_codec"  of the TI workshop . Can anyone give me a hand?

 We use the dm6446 EVM and use the original environment form CD and use the download cg6x_6_0_3 , framework_component_2_21 and xdctool_2_94. OS is Fedra 5.

configuring app_debug.x470MV from package/cfg/app_debug_x470MV.cfg ...
ti.sdo.ce.utils.trace.close() ...
ti.sdo.ce.bioslog.init() ...
ti.sdo.ce.bioslog.close() ...
ti.sdo.ce.osal.close() ...
error: xdc.cfg.Program: "/home/imslab/dvevm_1_10/xdctools_2_94/packages/xdc/runtime/package.xs", line 44: xdc.cfg.Program : target modules are present, but Program.system == null
js: "/home/imslab/dvevm_1_10/xdctools_2_94/packages/xdc/cfg/Main.xs", line 162: exception from uncaught JavaScript throw: Error: Configuration failed!
    "/home/imslab/dvevm_1_10/xdctools_2_94/packages/xdc/xs.js", line 137
gmake[1]: *** [package/cfg/app_debug_x470MV.xdl] Error 1
gmake: *** [/home/imslab/TI_work/solutions/soln14b_build_codec_socrates/app,.executables] Error 2

what is the Program.system == null?  how can i resolve this problem?

 

 

 

 

  • This error occurs when xdc runs close function but it finds that "Program.system" is null.  Here is the code from xdc/runtime/package.xs:

        /* system cannot be NULL if target modules are present */
        if (Program.system === null) {
            for (var i = 0; i < xdc.om.$modules.length; i++) {
                var mod = xdc.om.$modules[i];
                if (mod.$used && !mod.$hostonly) {
                    Program.$logError("target modules are present, but Program.system == null", Program);
                    return;
                }
            }
        }

     

    As the comment says, I think you should check whether your target(ti.targets.C64+) is set properly  while running xdc tools.

    [edit] For more information on XDC, please refer to XDC Consumer User's Guide

  • Thanks for Lorry~

    Our problem is solved, because each SDK(XDAIS FRAMEWORK,DSP/BIOS, CGT,  ) has some different  dependency, so we made this mistake, Actually, we just re-dowload all  SDK software (DVSDK) that can be solved this problem. 

     

  • Here I have some questions for XDC:

    1) xdc/runtime/package.xs:   what does "xdc.om" refer to?

    2) I know "Program" is an module of XDC, it just like a class in C++. Could anyone tell me where "Program.system" get its value?

    3) From a beginner perspective, I find that there are lots of  "xdc"  "xs"  "mak" "bld" "opt" ...  files in dvevm_x_xx  folder.  Could anyone provide me a shortcut to remember the function of these files.  Because I spend much time in writing codec and debug it, however, every time when I see these files again, I think I've forgotten the meaning of them. So I have to back to documents to learn them.  And some of them is related with my codec code or the process of compilation

    I want to know if it is necessary to set so many files,  if it is possible to simplify them to just three or four  types of files, I think,  that will be better for understanding.  For example: " .c",".h",".xdc",".ini".