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.

The problem of CCS interface function

Other Parts Discussed in Thread: SYSBIOS

Hi,

      TI has provided the CCS interface function for us, such as connect,load,run,step,set breakpoints,clear breakpoints and so on.  And we developed debugging software in the CCS based on a PCIE bus or internet, which can connect with c6678 board,can download program to the board, and debug program on the board. Now the software has been delivered to users. After they used our K1 debugging software,there are some feedback problems.

1.run to line, step over, assembly step over is not good or not supported. Users want to be able to use these features, but because TI only opens to us step, so our software can't modify "run to line, step over, assembly step over", they are background operation of CCS. We have no way to use our own code to implement these functions, could TI open these interface functions to us?

2.About Sysbios, because there is a conflict of our kernel and the Sysbios, so our software only realize the function of breakpoints. So could TI open source code of Sysbios and how to package the Sysbios module to us? So we can modify the sysbios modules and kernel according to the requirement of our kernel, and package into modules for users.

 

Thanks,

Regards