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/TMS320F28377D: TI-TXT File Generation issues with C2000-GANG

Part Number: TMS320F28377D
Other Parts Discussed in Thread: C2000-GANG

Tool/software: Code Composer Studio

I am trying to generate a TI-TXT file to use with a C2000-GANG programmer for standalone programming. I have a project that I have been able to build/program successfully. When I enable the C2000 Hex Utility and set the Output Format Options to "Output TI-TXT hex format (--ti_txt)," I get a .txt file that is not successfully read into the C2000-GANG programmer utility.

I receive the error: "ERROR 354: Code in the file contains invalid data."

When I open the .txt file, I see the following:

@14a58
05 00 03 E2 BD 03 03 E2 BD 04 03 E2 BD 05 03 E2 
...
@100000
48 00 A3 3F 
@104000
1B 76 F0 FF 05 00 BD AB BD A8 BD A0 BD C2 BD C3 
...

My understanding is that I am supposed to see the correct memory sections as defined by the linker file in the project? Am I missing something in the configuration of the Hex Utility that is preventing the output of the correct file? I am using CCS8 but have also tried on CCS9.

Thanks.

  • Hi Eric,

    Data in C28 MCUs are 16 bits wide, not 8 bits wide. You should convert the output file from your project to 16 bits wide hex file. Use TI hex2000.exe file co convert the output file to hex file with parameters

        "-romwidth=16 -memwidth=16 -i -o=%s   %s", HexFileName, OutFileName

    Data in the hex file in TI format should be as e.g follows:

    @100000   //address

    4801 4356 3457 4356       //16 bits wide data

    Let me know if that helps.

    Regards,
    Gregory Czajkowski
    Elprotronic Inc.

  • Hi Gregory,

    Thanks for the quick reply. I have tried to use the options you specified both in the Hex Utility in ccs as well as Windows Command line, but it is still showing up in 8-bit format, exactly as I had pasted above. I believe this is only one issue. The other is that I haven't seen any recognizable memory section (per my linker file).

    I assume that the .txt should contain the same memory sections as I've specified in my linker file, correct?

    Thanks,

    Eric

  • Hi Eric,

    Email me the out file then we can check if we can convert it to 16-b hex. It can be dummy code doing the same.

    Regards,

    Gregory
    gregory@elprotronic.com

  • Eric,

    I am closing this post assuming you are working with Greg.

    If you need further help, or if you have feedback, please reply to this post.

    Greg,

    Please consider posting the resolution here for the benefit of other E2E users that may see similar issue.

    Thanks and regards,
    Vamsi