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.

Sharing TI development tools with projects for non TI devices

Hi,

We are using TI ARM MCUs in our products. We use CCSv5.4, XDS100v2 JTAG debugger and SYS/BIOS in our development process.

However, we'll also have to use non-TI ARM based MCU chips for some other of our products. Specifically we consider using Xillinx Zynq-7000, as it has FPGA integrated with Cortex A9 core on same chip.

However, we would be highly interested in sharing our codebase and unifying our development practices for all our products. That's much better than working with two different development environments.

So, can we theoretically utilize our existing development platform (CCS+XDS debugger+SYS/BIOS) and use it for the non TI chip too?
Are there any licensing/technical problems that would stop us from doing the above?

We understand that to make it all work with a different (non TI) chip we shall do some amount of work. Like prepare GEL files, alter some code of SYS/BIOS... But can it work at all? Are there any underlying basic problems?
All ARM chips provide "standard" JTAG interface. So shall CSS/XDS100v2 work with just any chip or it has some hard-coded limitations and will work only with TI products?

Best,
Vasili

  • Vasili Galka said:
    So, can we theoretically utilize our existing development platform (CCS+XDS debugger+SYS/BIOS) and use it for the non TI chip too?
    Are there any licensing/technical problems that would stop us from doing the above?

    From the restrictions section of the Code Composer Studio 5.4 Software License Agreement:
    ii. Use of any software application generated, analyzed or debugged using the Licensed Materials on processing devices manufactured by or for an entity other than TI is a material breach of this Agreement.
    While I am not a lawyer this implies the CCS license stops you from using CCS with non TI chips.

  • I see. Pity. That means we have to switch all our products to some other tool-set/OS.

    Thank you!