• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 317 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F478: Why are Code Composer Essentials and Code Composer Studio's header files different?

Qi Liu
Intellectual 2640 points
Part Number: MSP430F478

Hi, support team

Why are Code Composer Essentials and Code Composer Studio's header files different?
For example, in msp430x47x.h and msp430f478.h of CCE, the XX parts of XCAPxPF are different.
Using the source code built by CCE on CCS will report an error.
So are there any setting information let CCE and CCS build result consistent.

Thanks so much.

Best regards,
Yuki

  • 0
    TI__Guru 64896 points

    Hi Yuki,

    Let me check with our SW development team on this.

  • 0
    TI__Genius 16840 points

    Hi Yuki,

    Thank you for bringing this to our attention.

    I assume you were using Rev 1.0 of this header file, while the newer CCS uses Rev 1.1:

    Looking at the release notes (C:\ti\ccs1031\ccs\ccs_base\msp430\ReleaseNotes_MSP430_HeaderFiles.txt), I believe that change was implemented in 2010:

    It's a bit confusing since the User's Guide shows XCAPxPF, and I don't know the exact reason behind this change, but I can only assume it was to make it more descriptive and consistent with other MSP430s.

    MSP430 header files are included as part of CCS, and your CCE project was using an older version. Unfortunately, there's no setting in CCS to achieve this compatibility, but perhaps you could try diff-ing the files giving you trouble and replacing them. 

  • 0 in reply to Luis RC
    TI__Intellectual 2640 points

    Thanks so much for your support.

    I see that the version of the header file has been updated.

    Since the last question was not correctly conveyed, please allow me to ask again:

    Make Intel hex file in CCE, write the Intel hex file to MSP430 and execute it
    Modify XCAP part in CCS, make Intel hex file, write the Intel hex file to MSP430 and execute it

    The above two cases, although some actions will change,
    are building results created by the same code different in CCE and CCS?

    In addition, whether it can be set in CCS to make the generated Intel hex file same as CCE?

    Best regards,
    Yuki

  • 0 in reply to Qi Liu
    TI__Genius 16840 points

    Hi Yuki,

    The output generated by CCS will be different from your CCE. 

    The changes can come from sources like:

    - Header file changes (as you saw): this would mostly be due to bugs or other issues. So, it's less likely.

    - Changes in linker file. Linker files also change, but also mostly due to bug fixes. 

    - CGT: Code Generation Tools change often, to fix bugs, add features, improvements, etc. This will cause differences in your output files.

    - MCU libraries: these can be for things like math.h, or just basic MCU initialization of stack, RAM, etc. Same as above, this will cause differences in your output files. 

    In theory, none of these changes would cause an application to break once it's migrated properly.

    CCS includes documentation explaining changes between versions, but things change a lot in >10yrs.

    I'm not sure I understand your last question, but CCS can generate an Intel HEX output using this option:

**Attention** This is a public forum