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.

CCS: Different version CCS compile the same source, the lower version CCS produce abnormal .bin file

Other Parts Discussed in Thread: TMS320F28069

Tool/software: Code Composer Studio

Issue background: I compiled the source code, and down to control board with TMS320F28069, the control board work normal,then  I upload source code to SVN. my colleague down source code from SVN, and compile the source code by CCS on his compute, then down the .bin file to control board,the control board doesn't work. my computer is WIN10 with CCS9.1.0,and the compile version is v18.12.1. my colleague's computer is WIN7 32bit, with CCS6.1.2, compile version is v6.4.6.

then I install the CGT V6.4.6 on my PC, and compile the project with v6.4.6,the same result with my colleague.

The issue :

what cause the result when compile same source code with different version CCS? and how to find the root cause? Is this problem related to the computer system?

  • Unfortunately, this is too vague to comment on.  You need to further define exactly what has gone wrong.  What precise system behavior occurs that lets you know things are wrong?  Exactly how do you see it?  What do you expect to see instead?

    If you need help with debug techniques, then either start a new thread in the C2000 device forum, or ask me to move this thread to that forum.

    Thanks and regards,

    -George

  • thanks George for reply.

    There is LED in control board,  when firmware work normal, the LED flicker with 2Hz, and also can communicate with DSP by serial port.

    now, we program the DSP with the x.bin produced by v6.4.6. the LED off, and fail to communicate with DSP, but we program the DSP with x.bin produced by v18.12.1, the LED flicker normal, and can communicate with DSP successfully.

    the phenomenon is happened firstly. we think maybe some code affect the compiler.unfortunately, there isn't JTAG in our board, and cannot to debug by step to step.

  • we have find the cause. there is a x. cla  file in our project,and make some code change,(just a little change)that cause the phenomenon.then restore the code, every thing normal.