- 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.
I finally managed to get a Syslink "Hello World App" to run using Syslink and Ipc on the c6a8168, The ARM sends a notifiy message to the DSP and the DSP sends an acknowledgement back, indicating that it is there. I built the code in EZSDK using xdc for the DSP and with a makefile for the ARM. Everything is fine on the ARM side, but what about the DSP? Without Code Composer, or perhaps with it, how does one see directly what is going on in the DSP? As Syslink comes without the rtos library package I have been unable to build Syslink compatible DSP in Code Composer. I did try copying the Sylink rtos library from linux to Windows for Code Composer, but the resulting code does not work. Has anyone figured this out?
Lee Holeva
MugdhaK said:There shouldn't be any problem. You can halt using CCS, start again and communication with the ARM will continue.
Well, there appears to be a problem. Upon attempting to connect to the ARM Cortex-A8, I get this:
I'm using the latest GEL file from Spectrum Digital. I put a getchar() after the ProcMgr startup code, load the DSP code image and start it up, I click on Yes, the ARM is halted, but the only way I can restart it is to disconnect. I can connect to the DSP ok after the ARM is halted, load symbols, and get it running, but when I go to restart the ARM, the only way I can do this is to disconnect, and the ARM hangs.
This part has been fixed. I removed the GEL file and the connection to the ARM now works as it should. The last issue is that of breakpoints. Though I build using xdc with -g, I do not appear to be getting all of my symbols.
Lee Holeva
MugdhaK said:The way I usually debug is to keep CCS open with the required target configuration loaded (which will be setup to only have the DSP since I don't need to debug on anything else using CCS). At this point, I've not connected to any core in CCS. Then I power-up the board, boot Linux, insmod syslink etc. run ProcMgr application using SysLink and when it says that the DSP has been loaded and started, I connect to the DSP in CCS. Then load symbols with the application executable that I have built (whole_program_debug or debug build will give you symbolic debug). I also set the source lookup path to the folders where I have my application, SysLink/IPC source code (if I want to debug within that too) and sometimes BIOS code too. After that, I can go ahead and set breakpoints, do single-step, watch etc.
Hi Mughda,
thanks for clarifying that. I have succeeded in following your instructions and going as far as loading the symbols but despite adding in all the most important directories and their subdirectories in the EZSDK no source code is found by CCS no matter which thread I click on. Pic of my source path (yes, it does slow down CCS a lot having so large a search path):
And here is a picture of my Debug window after connecting and loading symbols:
Lee, would you like me to create a new thread? I don't want to hijack yours but if this is related and of use I can keep my posts here.
Cheers,
Ralph
MugdhaK said:Can you compare your .map file generated with CCS build and with the xdc build and see if they match?
xdc does not produce a .map file. I am using slighly modified config.bld and packge.bld files taken from the samples to build my code using xdc.
MugdhaK said:I do believe that your problems with symbolic debug are not because of xdc build and won't get solved with CCS build, if that's the reason why you're trying CCS build
The only bit of success that I've had is when I build the code in CCS and "Load Program", as I have actually been able to set a breakpoint and see a bit of the DSP code run. When I do "Load Symbols" from the code made using xdc in the SDK, what I see is different from what Ralph is seeing:
Perhaps this would help, here are the xdc project files:
config.bld
// ON Linux Host. Modify this to suit your tool chain paths
var rootDirPre = "/home/lholeva/ti-ezsdk_dm816x-evm_5_01_00_77";
var rootDirPost = "";
//********************* Setup for C674 target for COFF *************************
var C674_COFF = xdc.useModule('ti.targets.C674');
C674_COFF.rootDir = rootDirPre + "/cgt6x_7_2_2" + 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_2" + rootDirPost;
C674_ELF.ccOpts.suffix += " --profile:breakpt -O0 -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,
];
package.bld
var testBld = xdc.loadCapsule("ti/syslink/buildutils/rtos/buildScripts/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_dsp',
sources: ["DSPtasks", "Preprocessing"], config: "./ti81xx/DSPtasks_ti81xx_dsp",
copts: ["-g -DSYSLINK_PLATFORM_TI81XX"],
buildTargets: ["C674"],
buildPlatforms: ["platforms.ti816x.dsp"],
},
{name: 'DSPtasks_ti81xx_videom3',
sources: ['DSPtasks'], config: "./ti81xx/DSPtasks_ti81xx_videom3",
copts: " -DSYSLINK_PLATFORM_TI81XX ",
buildTargets: ["M3"],
buildPlatforms: ["platforms.ti816x.videom3"],
},
{name: 'DSPtasks_ti81xx_vpssm3',
sources: ['DSPtasks'], config: "./ti81xx/DSPtasks_ti81xx_vpssm3",
copts: " -DSYSLINK_PLATFORM_TI81XX ",
buildTargets: ["M3"],
buildPlatforms: ["platforms.ti816x.vpssm3"],
},
];
arguments[arguments.length++] = "platform=all";
arguments[arguments.length++] = "platform=debug";
/* clean generated files and folders */
Pkg.generatedFiles.$add("platforms.ti816x.dsp/");
/* Generate the makefile goals. 'arguments' is XDCARGS */
testBld.buildTests(testArray, arguments);
Lee Holeva
