CCSV5 CFG XDC

Junqing Zhao

Other Parts Discussed in Thread: TMS320DM6437, CCSTUDIO

Hi,everyone

Recently, I am migrating CCS3.3 project to CCSV5.1，A problem is happening. dm6437_demo.cfg can be built and configured correctly,but in ccsv5,it cant work .

How I can use cfg file in CCSv5?

Where I can find some useful example about CCSv5 and DM 6437?

Regards

JQ zhao

over 13 years ago

0 Sasha Slijepcevic over 13 years ago

TI__Mastermind 37985 points

You can start a new CCS project, and choose the device family C6000 and the device variant TMS320DM6437 in the project creation window. Then, you can select any of the SYS/BIOS examples under "Project templates and examples".

What's the problem you see when trying to use dm6437_demo.cfg?

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thanks.

In CCSV5, I create the new project，which need *.tcf and *.cfg. The project I have is built successfully in CCS3.3. But now something wrong happened inCCSv5.1.I don‘t know how to solve it。

The build log in Console is ：

gmake.exe *** No rule to make target 'package/cfg/Video_preview_p64P.xdl',needed by 'linker.cmd',stop.
js:"C:/ti/xdctools_3_22_04_46/packages/xdc/tools/Cmdr.xs",line 51:Error:xdc.tools.configuro:configuration failed due to earlier errors (status=2);'linker.cmd' deleted.
gmake.exe *** [configPkg/compiler.opt] Error 1
gmake:Target 'all' not remade because of errors

That is to say，the linker.cmd file did not generated automatically.

At the same time，the *cfg.h file did not generated ,too.

When I move the linker.cmd that generated in ccs3.3 to the project folder of CCSv5.1.It can be built correctly.

How to solve this problem?

Regards.

0 Sasha Slijepcevic over 13 years ago in reply to Junqing Zhao

TI__Mastermind 37985 points

Are you using --tcf option on the configuro command line? If yes, check these two threads that describe a bug that could be the cause of the error you are getting:
http://e2e.ti.com/support/embedded/bios/f/355/t/177474.aspx
http://e2e.ti.com/support/embedded/bios/f/355/t/151321.aspx

The first thread has a link to the bug report. You can check the report and add your email to the CC list, and you will be informed when the bug is fixed.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thank you for your help.

As the bug is fixed,the linker.cmd can generate.
You said"Are you using --tcf option on the configuro command line?",what do you mean?
As I asked last time,I have used #include<*cfg.h >,the *cfg.h file should be generated by *.tcf,but it didn't.So some errors happen. How can I duel with this?

Another question is that I use a xdcpath.dat file to represent the xdc package path in CCS3.3. In CCS5.1，I have to add one and one in package search path. How to use a xdcpath.dat in CCS5.1?

In CCS3.3, xdcpath.dat is like this

DVSDK_INSTALL_DIR = "C:/dvsdk_1_01_00_15";
BIOS_INSTALL_DIR = "C:/CCStudio_v3.3/bios_5_31_07";
CE_INSTALL_DIR = "C:/dvsdk_1_01_00_15/codec_engine_1_20_02";

Then in CCS3.3 project directory，I find a file like this

load("../xdcpaths.dat");

xdcpaths = CE_INSTALL_DIR + "/packages;" +
CE_INSTALL_DIR + "/examples;" +
XDAIS_INSTALL_DIR + "/packages;" +
"../common;../packages;" +
"";

How can I use like this in CCSv5.1，as it's simple?

0 Sasha Slijepcevic over 13 years ago in reply to Junqing Zhao

TI__Mastermind 37985 points

Junqing Zhao said:

Thank you for your help.

As the bug is fixed,the linker.cmd can generate.
You said"Are you using --tcf option on the configuro command line?",what do you mean?
As I asked last time,I have used #include<*cfg.h >,the *cfg.h file should be generated by *.tcf,but it didn't.So some errors happen. How can I duel with this?

What's the error that you are seeing? Have you applied the fix descibed in the first thread from my previous post? You have to have a clean build without errors to get all of the files generated.

In CCS 5.1, you add repositories to your package path through Project->Properties->CCS General->RTSC->Products and Repositories. Then, click on Add... and chose directories that you want to have on your XDC package path.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

I have followed the thread(the First and second is same thing). As video_preview.c I used #include<video_previewcfg.h>,but video_preview.tcf didnot generate video_previewcfg.h file.

So when I build it( I have already a clean build )，some errors happen. The errors are as bellow：

**** Build of configuration Debug for project Jpeg_loopback ****

C:\ti\ccsv5\utils\bin\gmake -k all
'Building file: ../video_preview.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_22_04_46/xs" --xdcpath="C:/dvsdk_1_01_00_15/codec_engine_1_20_02/packages;C:/dvsdk_1_01_00_15/biosutils_1_00_02/packages;C:/dvsdk_1_01_00_15/framework_components_1_20_03/packages;C:/ti/xdais_7_21_01_07/packages;C:/ti/bios_5_41_11_38/packages;D:/zhao_workspace_v5_1/packages;" xdc.tools.configuro -o configPkg -t ti.targets.C64P -p ti.platforms.evmDM6437 -r debug -c "C:/ti/ccsv5/tools/compiler/c6000" --tcf "../video_preview.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring video_preview.x64P from package/cfg/video_preview_x64P.cfg ...
ti.sdo.ce.osal.close() ...
ti.sdo.ce.osal.validate() ...
warning: xdc.cfg.Program: "C:/ti/xdctools_3_22_04_46/packages/xdc/runtime/package.xs", line 86: xdc.cfg.Program : assignment to Program.system is deprecated
    will link with ti.sdo.ce.image:lib/debug/image.a64P
    will link with ti.sdo.ce:lib/ce_debug.a64P
    will link with ti.sdo.ce.osal:lib/osal_bios.a64P
    will link with ti.bios.utils:lib/utils.a64P
    will link with ti.sdo.fc.dskt2:dskt2.a64P
    will link with ti.sdo.fc.acpy3:acpy3.a64P
    will link with ti.sdo.ce.utils.xdm:lib/XdmUtils.a64P
    will link with ti.sdo.fc.dman3:dman3Cfg.a64P
    will link with ti.sdo.ce.node:lib/node_debug.a64P
    will link with ti.sdo.ce.trace:lib/gt.a64P
cl64P package/cfg/video_preview_x64P.c ...
asm64P package/cfg/video_preview_x64Pcfg.s62 ...
cl64P package/cfg/video_preview_x64Pcfg_c.c ...
'Finished building: ../video_preview.cfg'
' '
'Building file: ../src/i2c_params.c'
'Invoking: C6000 Compiler'
"C:/ti/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/ti/ccsv5/tools/compiler/c6000/include" --include_path="D:/zhao_workspace_v5_1/Jpeg_loopback" --include_path="C:/ti/bios_5_41_11_38/packages/ti/bios/include" --include_path="C:/dvsdk_1_01_00_15/xdais_5_21/packages" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/inc" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/soc/dm6437/dsp/inc" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="src/i2c_params.pp" --obj_directory="src" --cmd_file="./configPkg/compiler.opt" "../src/i2c_params.c"
'Finished building: ../src/i2c_params.c'
' '
'Building file: ../src/video_preview.c'
'Invoking: C6000 Compiler'
"C:/ti/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/ti/ccsv5/tools/compiler/c6000/include" --include_path="D:/zhao_workspace_v5_1/Jpeg_loopback" --include_path="C:/ti/bios_5_41_11_38/packages/ti/bios/include" --include_path="C:/dvsdk_1_01_00_15/xdais_5_21/packages" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/inc" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/soc/dm6437/dsp/inc" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="src/video_preview.pp" --obj_directory="src" --cmd_file="./configPkg/compiler.opt" "../src/video_preview.c"
"../src/video_preview.c", line 32: fatal error #5: could not open source file "video_previewcfg.h"
1 fatal error detected in the compilation of "../src/video_preview.c".
Compilation terminated.

>> Compilation failure
gmake: *** [src/video_preview.obj] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

The .tcf property is ：

which is different the project just based on DSP/BIOS(not contain xdc or *.cfg).That can generate *cfg.h correctly.

How to solve these problems？ Thank you for your help in advance.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

I have followed your what yousaid in the thread(Both the two thread are same thing). As I used #include<Video_previewcfg,h> in Video_preview.c，which(*cfg.h) should be

generated by Video_preview.tcf. However,it is not.

I have rebuilt the project(I have a clean build before).Still,some errors are as bellow:

**** Build of configuration Debug for project Jpeg_loopback ****

>> Compilation failure
gmake: *** [src/video_preview.obj] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

I have saw the video_preview.tcf property:

Which is different with the project just based on DSP/BIOS(not used xdc or .cfg file).That can generate *cfg.h correctly。

How to solve these errors?Looking forward your answers.

Thank you for your help in advance.

0 Sasha Slijepcevic over 13 years ago in reply to Junqing Zhao

TI__Mastermind 37985 points

The option --tcf causes the generated files to have a slightly different names from the ones when you use Tconf and DSP/BIOS 5. The file that you are looking for is named video_preview_x64Pcfg.h. But, you don't need to know about that file or include it. You should instead have
#include <xdc/cfg/global.h>
and that will include all global symbols.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thank you.

When I used #include <Debug\configPkg\package\cfg\video_preview_x64Pcfg.h>,then program can built correctly,

But when I used #include <xdc/cfg/global.h>,errors stills exist.The build log is:

**** Build of configuration Debug for project Jpeg_loopback ****

C:\ti\ccsv5\utils\bin\gmake -k all
'Building file: ../src/video_preview.c'
'Invoking: C6000 Compiler'
"C:/ti/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/ti/ccsv5/tools/compiler/c6000/include" --include_path="D:/zhao_workspace_v5_1/Jpeg_loopback" --include_path="C:/ti/bios_5_41_11_38/packages/ti/bios/include" --include_path="C:/dvsdk_1_01_00_15/xdais_5_21/packages" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/inc" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/soc/dm6437/dsp/inc" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="src/video_preview.pp" --obj_directory="src" --cmd_file="./configPkg/compiler.opt" "../src/video_preview.c"
"../src/video_preview.c", line 437: error #20: identifier "stsDatarate" is undefined
1 error detected in the compilation of "../src/video_preview.c".
gmake: *** [src/video_preview.obj] Error 1
gmake: Target `all' not remade because of errors.

>> Compilation failure

**** Build Finished ****

The stsDatarate had be defined in video_preview_x64Pcfg.h file. So your suggestion did not work. The global.h is:

/*
* ======== global.h ========
* This header is used by C/C++ sources that want to "portably" include a
* configuration-specific generated header (which contains extern
* declarations of configuration specified global variables).
*
* To use this header you must define the symbol xdc_cfg__header__ to be
* the package-qualified name of the configuration header.
*
* For example, to compile sources that reference config values
* for a TI C6x target with a generated
* configuration header named "package/cfg/mycfg_x62.h" in a package
* named "local.examples" the following command line is sufficient:
*
* cl6x -Dxdc_cfg__header__=local/examples/package/cfg/mycfg_x62.h ...
*/

#ifndef xdc_cfg_global__include
#define xdc_cfg_global__include

/* support old compiler option for naming config include file */
#ifdef xdc_cfg__header__
#define xdc_cfg__xheader__ <xdc_cfg__header__>
#endif

/* if specified, include configuration generated header */
#ifdef xdc_cfg__xheader__
#include xdc_cfg__xheader__
#endif

#endif
/*
* @(#) xdc.cfg; 1, 0, 2, 0,344; 9-14-2011 15:36:07; /db/ztree/library/trees/xdc/xdc-x20x/src/packages/
*/

What this happens?How to do with it?

②Another question is about the Bug.

Firstly，Why I replace the -p with -x，then the program can run ? Why did this？

Secondly，

If I modified package.bld.xdt and package.xs.xdt follow the thread(http://e2e.ti.com/support/embedded/bios/f/355/t/151321.aspx), what potential risks do we face?Here I meet some erros. When I creat a sample application(Generic Example-Hello Example for SYS/BIOS).

The same errors happen:

**** Build of configuration Debug for project hello ****

C:\ti\ccsv5\utils\bin\gmake -k all
'Building file: ../hello.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_22_04_46/xs" --xdcpath="C:/ti/bios_6_32_05_54/packages;C:/ti/ipc_1_23_05_40/packages;" xdc.tools.configuro -o configPkg -t ti.targets.C64P -p ti.platforms.evmDM6437 -r debug -c "C:/ti/ccsv5/tools/compiler/c6000" --compileOptions "-g --optimize_with_debug" "../hello.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
gmake.exe: *** No rule to make target `package/cfg/hello_x64P.xdl', needed by `linker.cmd'. Stop.
js: "C:/ti/xdctools_3_22_04_46/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 ****

Then I modified back as before. That is to say

package.bld.xdt ：replace '.x' with '.p'

package.xs.xdt ：base + '_p' + suffix + '.o' + suffix,

The errors then eliminate. So the solution for the Bug is not pefect. How to solve this??

③ Why can't I use the RTA tool？the CPU Load、print log can't be used.

④ when I built efc.c,a error happen inCCSV5.1. Part of efc.c is

void efs_createfilecb( char *name, INT32 length, UINT8 *pData,
EFSFUN pllDestroyFun, UINT32 MemMgrArg )
{
FILEHEADER *pfh, *psh;

    // Allocate the file header structure
    pfh = mmAlloc( sizeof(FILEHEADER) );
    if( !pfh )
        return;

pfh->Type = HTYPE_EFSFILEHEADER;

    // Record the filename, size, and data pointer
    strncpy( pfh->Filename, name, EFS_FILENAME_MAX-1 );
    pfh->Filename[EFS_FILENAME_MAX-1] = 0;
    pfh->Length     = length;
    pfh->RefCount   = 0;
    pfh->pData      = pData;
    pfh->Flags      = 0;
    pfh->pMemMgrCallback = pllDestroyFun;
    pfh->MemMgrArg = MemMgrArg;

    psh = mmAlloc( sizeof(FILEHEADER) );
    if( !psh )
        return;

pfh->Shadow = psh;

psh->Type = HTYPE_EFSSHADOWHEADER;

    // Record the filename, size, and data pointer
    strncpy( psh->Filename, "_EFS_INTERNAL_shadow", EFS_FILENAME_MAX-1 );
    psh->Filename[EFS_FILENAME_MAX-1] = 0;
    psh->Length     = 0;
    psh->RefCount   = 0;
    psh->pData      = 0;
    psh->Flags      = 0;
    psh->pMemMgrCallback = 0;
    psh->MemMgrArg = 0;
    psh->Shadow = NULL;
    psh->pNext = NULL;

llEnter();

    // Put it in our list
    pfh->pNext = pRoot;
    pRoot      = pfh;

llExit();

}

Part of built log is

'Building file: ../os/efs.c'
'Invoking: C6000 Compiler'
"C:/ti/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/ti/ccsv5/tools/compiler/c6000/include" --include_path="D:/zhao_workspace_v5_1/Web_Video" --include_path="C:/ti/bios_5_41_11_38/packages/ti/bios/include" --include_path="C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/example/tools" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/inc" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/soc/dm6437/dsp/inc" --include_path="C:/CCStudio_v3.3/boards/evmdm6437_v2/include" --include_path="C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/inc" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="os/efs.pp" --obj_directory="os" --cmd_file="./configPkg/compiler.opt" "../os/efs.c"
"../os/efs.c", line 186: error #20: identifier "HTYPE_EFSSHADOWHEADER" is undefined
1 error detected in the compilation of "../os/efs.c".

>> Compilation failure
gmake: *** [os/efs.obj] Error 1
'Building file: ../os/efs_orig.c'
'Invoking: C6000 Compiler'
"C:/ti/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/ti/ccsv5/tools/compiler/c6000/include" --include_path="D:/zhao_workspace_v5_1/Web_Video" --include_path="C:/ti/bios_5_41_11_38/packages/ti/bios/include" --include_path="C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/example/tools" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/inc" --include_path="C:/dvsdk_1_01_00_15/psp_1_00_02_00/pspdrivers/soc/dm6437/dsp/inc" --include_path="C:/CCStudio_v3.3/boards/evmdm6437_v2/include" --include_path="C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/inc" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="os/efs_orig.pp" --obj_directory="os" --cmd_file="./configPkg/compiler.opt" "../os/efs_orig.c"
'Finished building: ../os/efs_orig.c'

How to solve this Compilation failure?

Thank you for reading all this,I am looking forward your reply.

Regards.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thank you.

When I used #include <Debug\configPkg\package\cfg\video_preview_x64Pcfg.h>,then program can built correctly,

But when I used #include <xdc/cfg/global.h>,errors stills exist.The build log is:

**** Build of configuration Debug for project Jpeg_loopback ****

>> Compilation failure

**** Build Finished ****

The stsDatarate had be defined in video_preview_x64Pcfg.h file. So your suggestion did not work. The global.h is:

#ifndef xdc_cfg_global__include
#define xdc_cfg_global__include

/* support old compiler option for naming config include file */
#ifdef xdc_cfg__header__
#define xdc_cfg__xheader__ <xdc_cfg__header__>
#endif

/* if specified, include configuration generated header */
#ifdef xdc_cfg__xheader__
#include xdc_cfg__xheader__
#endif

#endif
/*
* @(#) xdc.cfg; 1, 0, 2, 0,344; 9-14-2011 15:36:07; /db/ztree/library/trees/xdc/xdc-x20x/src/packages/
*/

What this happens?How to do with it?

②Another question is about the Bug.

Firstly，Why I replace the -p with -x，then the program can run ? Why did this？

Secondly，

The same errors happen:

**** Build of configuration Debug for project hello ****

**** Build Finished ****

Then I modified back as before. That is to say

package.bld.xdt ：replace '.x' with '.p'

package.xs.xdt ：base + '_p' + suffix + '.o' + suffix,

The errors then eliminate. So the solution for the Bug is not pefect. How to solve this??

③ Why can't I use the RTA tool？the CPU Load、print log can't be used.

④ when I built efc.c,a error happen inCCSV5.1. Part of efc.c is

void efs_createfilecb( char *name, INT32 length, UINT8 *pData,
EFSFUN pllDestroyFun, UINT32 MemMgrArg )
{
FILEHEADER *pfh, *psh;

    // Allocate the file header structure
    pfh = mmAlloc( sizeof(FILEHEADER) );
    if( !pfh )
        return;

pfh->Type = HTYPE_EFSFILEHEADER;

    psh = mmAlloc( sizeof(FILEHEADER) );
    if( !psh )
        return;

pfh->Shadow = psh;

psh->Type = HTYPE_EFSSHADOWHEADER;

llEnter();

    // Put it in our list
    pfh->pNext = pRoot;
    pRoot      = pfh;

llExit();

}

Part of built log is

How to solve this Compilation failure?

Thank you for reading all this,I am looking forward your reply.

Regards.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thank you.

When I used #include <Debug\configPkg\package\cfg\video_preview_x64Pcfg.h>,then program can built correctly,

But when I used #include <xdc/cfg/global.h>,errors stills exist.The build log is:

**** Build of configuration Debug for project Jpeg_loopback ****

>> Compilation failure

**** Build Finished ****

The stsDatarate had be defined in video_preview_x64Pcfg.h file. So your suggestion did not work. The global.h is:

#ifndef xdc_cfg_global__include
#define xdc_cfg_global__include

/* support old compiler option for naming config include file */
#ifdef xdc_cfg__header__
#define xdc_cfg__xheader__ <xdc_cfg__header__>
#endif

/* if specified, include configuration generated header */
#ifdef xdc_cfg__xheader__
#include xdc_cfg__xheader__
#endif

#endif
/*
* @(#) xdc.cfg; 1, 0, 2, 0,344; 9-14-2011 15:36:07; /db/ztree/library/trees/xdc/xdc-x20x/src/packages/
*/

What this happens?How to do with it?

②Another question is about the Bug.

Firstly，Why I replace the -p with -x，then the program can run ? Why did this？

Secondly，

The same errors happen:

**** Build of configuration Debug for project hello ****

**** Build Finished ****

Then I modified back as before. That is to say

package.bld.xdt ：replace '.x' with '.p'

package.xs.xdt ：base + '_p' + suffix + '.o' + suffix,

The errors then eliminate. So the solution for the Bug is not pefect. How to solve this??

③ Why can't I use the RTA tool？the CPU Load、print log can't be used.

④ when I built efc.c,a error happen inCCSV5.1. Part of efc.c is

void efs_createfilecb( char *name, INT32 length, UINT8 *pData,
EFSFUN pllDestroyFun, UINT32 MemMgrArg )
{
FILEHEADER *pfh, *psh;

    // Allocate the file header structure
    pfh = mmAlloc( sizeof(FILEHEADER) );
    if( !pfh )
        return;

pfh->Type = HTYPE_EFSFILEHEADER;

    psh = mmAlloc( sizeof(FILEHEADER) );
    if( !psh )
        return;

pfh->Shadow = psh;

psh->Type = HTYPE_EFSSHADOWHEADER;

llEnter();

    // Put it in our list
    pfh->pNext = pRoot;
    pRoot      = pfh;

llExit();

}

Part of built log is

How to solve this Compilation failure?

Thank you for reading all this,I am looking forward your reply.

Regards.

0 Sasha Slijepcevic over 13 years ago in reply to Junqing Zhao

TI__Mastermind 37985 points

Junqing Zhao said:

Thank you.

When I used #include <Debug\configPkg\package\cfg\video_preview_x64Pcfg.h>,then program can built correctly,

But when I used #include <xdc/cfg/global.h>,errors stills exist.The build log is:

I think you actually need both. The first one includes global symbols from your TCF script, and the second one includes globals from your CFG script. It's possible that you are not using any globals created in your CFG script, so not including <xdc/cfg/global.h> does not make any difference. But, you should be including both in case you decide to use globals from the CFG script later.

Junqing Zhao said:

Firstly，Why I replace the -p with -x，then the program can run ? Why did this？Secondly，
If I modified package.bld.xdt and package.xs.xdt follow the thread(http://e2e.ti.com/support/embedded/bios/f/355/t/151321.aspx), what potential risks do we face?Here I meet some erros.

The replacements suggested in that thread are a workaround for a specific error, and they are not really tested so it's possible that they cause errors in some other use cases. When you switch to another project you may need to revert the changes. When we develop a solution that's tested against all use cases, then we will release it as an official bug fix.

Your 3rd and 4th question should go to new threads. I don't know where HTYPE_EFSSHADOWHEADER is coming from and why it's not found.

0 Junqing Zhao over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Sasha Slijepcevic said:

Are you using --tcf option on the configuro command line? If yes, check these two threads that describe a bug that could be the cause of the error you are getting:
http://e2e.ti.com/support/embedded/bios/f/355/t/177474.aspx
http://e2e.ti.com/support/embedded/bios/f/355/t/151321.aspx

The first thread has a link to the bug report. You can check the report and add your email to the CC list, and you will be informed when the bug is fixed.

When I use SYS/BIOS,the bugs have to modified as before. The CCS has update to CCSv5.2. I want to know whether the bug roblems solved thoroughly？

Thank you

JQ Zhao

0 Sasha Slijepcevic over 13 years ago in reply to Junqing Zhao

TI__Mastermind 37985 points

The complete fix for that bug will be available in XDCtools 3.23.04, which will be released in two weeks or so. When it's released, you'll be able to add that release to your CCSv5.2 installation.
Here is the Web page where we publish XDCtools releases: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/.

Processors

Processors forum

CCSV5 CFG XDC