Hi,
Is there a way to use DSP/SYS/BIOS project without using XDC? Is there another way to define what XDC is doing?
Thanks,
HR
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.
There is no way to use SYS/BIOS without XDCtools. To replace XDCtools, you would need another tool to read a CFG script and then generate a source file that's compiled and linked with SYS/BIOS libraries and the app. I don't know of any such tool.
DSP/BIOS uses Gconf for GUI configuration and Tconf for textual configuration. They also need an XDCtools installation to work. The concept is the same as for SYS/BIOS - you define a configuration using those tools, and then C source files and a linker command file come out as a result. There are no alternative tools that could replace Gcong and Tconf, as far as I know.
Since all the xdc functions have C equivalents, and all xdc tools do is generate C code in the background, it should be quite feasible to dump the xdc tools & co. and setup sysbios in straight C.
Example:
XDC:
C equivalents:
So, if you are creating a task, in XDC .cfg file it would look something like this:
var params = new Task.Params;
params.config = ...
var inst = Task.create("&task_function", params);
The equivalent thing in straight C:
#include <ti/sysbios/knl/Task.h>
Task_Params params;
params....
Task_create(task_function, ¶ms, NULL);
Or, if you want to create static tasks, use the Task_construct() function.
Relevant documentation:
There are no plans or any current development for using SYS/BIOS without XDCtools.
We do support a closure tool - http://rtsc.eclipse.org/docs-tip/Command_-_xdc.tools.closure, which can be used to generate XDCtools artifacts only once and then use them to recompile and relink an app without using XDCtools.