- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Using the C6a816x EVM and connecting the JTAG without a GEL file, both the ARM and C674 may be made to run and my test program runs to completion as it should, but I am missing symbols. I attempt to set a breakpoint and if I try to enable the breakpoint I get:
After loading symbols, for the C674 I see under Thread:
0 ti_sysbios_knl_Idle_loop__F(unsigned int, unsigned int) at Idle.c:70 0x8b0148fc
1 <symbol is not available> 0x00000000
It appears that my program symbols aren't getting saved. I built the program using xdc in linux. The config.bld file:
var rootDirPre = "/home/lholeva/ti-ezsdk_c6a816x-evm_5_00_00_56";
var rootDirPost = "";
//********************* Setup for C674 target for COFF *************************
var C674_COFF = xdc.useModule('ti.targets.C674');
C674_COFF.rootDir = rootDirPre + "/cgt6x_7_2_0" + rootDirPost;
C674_COFF.ccOpts.suffix += " -g -mi10 -mo ";
//set default platform and list of all interested platforms for c674
C674_COFF.platforms = [
//"ti.platforms.evmDA830:dsp",
"platforms.ti816x.dsp"
];
//********************* Setup for C674 target for ELF *************************
var C674_ELF = xdc.useModule('ti.targets.elf.C674');
C674_ELF.rootDir = rootDirPre + "/cgt6x_7_2_0" + rootDirPost;
C674_ELF.ccOpts.suffix += " -g -mi10 -mo ";
//set default platform and list of all interested platforms for c674
C674_ELF.platforms = [
// "ti.platforms.evmDA830:dsp",
//"ti.syslink.samples.rtos.platforms.ti816x.dsp",
"platforms.ti816x.dsp"
];
//list interested targets in Build.targets array
Build.targets = [
//C28_large,
//C64,
//C64P_COFF,
//C64P_ELF,
//C67P,
//C674_COFF,
C674_ELF,
//M3_ELF,
];
Do I need something more than the -g option?
The package.bld file:
var Build = xdc.useModule('xdc.bld.BuildEnvironment');
var Pkg = xdc.useModule('xdc.bld.PackageContents');
for each (var targ in Build.targets) {
Pkg.attrs.profile = "debug" ;
}
var testBld = xdc.loadCapsule("ti/sdo/ipc/build/test.bld");
/*
* Export everything necessary to build this package with (almost) no
* generated files. This also exports subdirectories like 'golden'
* and 'docs'.
*/
var srcRelease = Pkg.addRelease(Pkg.name + ",src", {exportSrc: true, exportExe : true, exportCfg: true, exportAll: true});
/*
* Export everything necessary to build this package with (almost) no
* generated files. This also exports subdirectories like 'golden'
* and 'docs'.
*/
//Pkg.attrs.exportAll = true;
/*
* ======== testArray ========
* See ti/bios/build/test.bld. Only the test name is required.
*
* Example:
* var testArray = [
* {name: Test1},
* {name: Test2, sources: ["Test"], config: "Test", refOutput: "Test", timeout: "15", buildTargets: ["C64", "C28_large"]}
* ];
*/
var testArray = [
{name: 'DSPtasks_ti81xx',
sources: ["DSPtasks", "Preprocessing"], config: "./DSPtasks_ti81xx",
copts: ["-DSYSLINK_PLATFORM_TI81XX"],
buildTargets: ["C674"],
buildPlatforms: ["platforms.ti816x.dsp"],
} ];
arguments[arguments.length++] = "platform=all";
/* clean generated files and folders */
Pkg.generatedFiles.$add("platforms.ti816x.dsp/");
/* Generate the makefile goals. 'arguments' is XDCARGS */
testBld.buildTests(testArray, arguments);
Lee Holeva
desouza said:Is the file <DSPTasks.c> written by you? If not, are you able to do source code debugging in the parts you have written yourself?
Yes, DSPtasks.c is my code, and no I cannot do source code debugging on this code. Do I have config.bld setup correctly to get all the symbols?
Here is what I see:
I cannot set a watch variable, CCs says that the identifier is not found. The error window is from right clicking where I tried to put the breakpoint, in my code, followed by attempting to enable the breakpoint. I am apparently not getting symbols from xdc.
Could this have anything to do with missing debug symbols:
Debugger/IDE file generation support
| XDCspec declarations | sourced in xdc/bld/ITarget.xdc |
Program.gen.debuggerFiles = true;
Lee Holeva
I moved Pkg.attrs.profile = "debug"; to after the loadCapsule of test.bld, but xdc still build whole_program_debug, not debug. the package.bld file that I am using is copied from that used in the Syslink samples (perhaps someone from that group knows how to set this up for debug?). I tried changing the compile options to:
-O0 -g
but I still do not have symbols for my program:
Lee Holeva
Shreyas Prasad said:Try inserting the following line
arguments[arguments.length++] = "profile=debug";
after the following line in your package.bld:
arguments[arguments.length++] = "platform=all";
I did this, and I do see the global sysmbols of my code, but this is interesting. After loading the symbols with both the ARM and DSP halted, I have watch variables:
I still cannot set breakpoints. I set the DSP and then the ARM running and my Watch variables are no longer defined:
The code runs fine. This suggests that this is more a code Composer problem than an xdc problem.
Lee Holeva
