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.

TMS320F280025C: Disabling CAN is causing application to not work

Part Number: TMS320F280025C
Other Parts Discussed in Thread: SYSCONFIG,

Tool/software:

We have build variants in the code ;

      1.  Development variant: with three CAN interrupts enabled via sysconfig ;
        1. Extended TX
        2. Extended RX
        3. Extended RX
      1.  Production variant: with only one RX interrupt enabled via sysconfig (rest of the part in sysconfig is exactly same);
        1. Extended RX

 

Our development variant always works on the development board as well as on the target board. But the production variant does not work with the target board.

 

If you see, the difference between two variants is only in the sysconfig in the CAN section.

 

What could be the reason for this?

 

    1.  And if we try to delete the sysconfig and create it again by copying the working sysconfig and deleting two additional CAN interrupts, code never works.

 

    1. While debugging above major issue, we observed that even if we have same version of tool chain, generated hex file is always different (we convert .out file to intel .hex using hex utility.);
      1. CCS                 : 11.0.0.00012
      2. C2000 ware      : 4.0.0.00
      3. Sysconfig         : 01.10.00
      4. Compiler          : 21.6.0.LTS

 

Ideally, the generated hex file should be same when built with the same tool chain, as intel hex file contains data only.

 

Despite many trials and combinations, our production variant is not working with the target board which is having a minor change in sysconfig only.

 

Please help us to know on what could be probable root cause and which things we can try at our end.

 

Also, which toolchain version is stable for TMS320F280025C?

 

It will be helpful for us if we get reply by today and if we meet in Monday morning, as this is the burning issue for us.