• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 916 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.

Problem generating valid TI-TXT file from CCS4 project.

Chad Killion
Prodigy 190 points
Other Parts Discussed in Thread: MSP430F5438A

I've recently switched from the IAR compiler to Code Composer Studios 4 (microcontroller edition).  I'm able to emulate and load the executable.out file onto my board using CCS 4 with no problems, but the TI-TXT file generated is invalid  (the FET-Pro430 says the code exceeds the flash size and is unable to load it.  My BSL application fails too.  Both apps worked with the IAR generated TI-TXT file).

I generate the TI-TXT file by adding the Post-build step to the CCS4 project build options:

"${CG_TOOL_ROOT}/bin/hex${CG_TOOL_SUFFIX}.exe" --ti_txt "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.txt" -order MS -romwidth 16 

(this command was added automatically by selecting the appropriate "Apply Predefined Step" in the dropdown box.)

 

I'm using an MSP430F5438A.  Any ideas?

 

-Chad

  • 0
    Prodigy 190 points

    Okay, the problem is that the RAM memory section is getting added to this file (even though it should be FLASH addresses only).  If I manually cut out the RAM memory section from the TI-TXT file, everything works. 

    Does anyone know how to keep Code Composer 4.0 from adding this RAM section to the TI-TXT output?

    -Chad

  • 0 in reply to Chad Killion
    Prodigy 190 points

    I fixed it by adding  --exclude=.bss  to the command line of the hex430 utility.  I'm not sure why I had to explicity do this, but there it is.

  • 0 in reply to Chad Killion
    Guru 227245 points

    Thanks for sharing your experience.

    Chad Killion said:
    I'm not sure why I had to explicity do this

    I guess, teh conversion tool is jsut converting the file, but not interpreting it. So every section gets converted, no matter of its meaning.
    -bss contains variables that are uninitialized. They do, however, occupy space, and this space is in ram, so the segment itself gets created in the linker output file. And therefore appears in the .txt file too, if not expicitely excluded.

**Attention** This is a public forum