• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 7335 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler/TMS320F28377S: warning: Data is being written to auto-generated file

Leif Grundmann
Prodigy 65 points
Part Number: TMS320F28377S

Tool/software: TI C/C++ Compiler

Hi there!

Recently I've got a warning I've never seen before.

"warning: Data is being written to auto-generated file" dsp_app.i10

It occurs right before the build process is completed. I.e. After compiling, linking hex generation ...

Can you provide information what this warning refers to ?

Thanks!

  • 0
    TI__Guru**** 249420 points

    If you use hex utility version 17.6.0.STS, then you are probably experiencing the bug described in this forum thread.

    Otherwise, my best guess is that you have an initialized section on PAGE 1, and you shouldn't.  Visit this article for background on memory pages.  The hex utility only converts initialized sections, like .text and .data.  Uninitialized sections, like the stack and .ebss, are ignored.  Usually (bordering on always), a C2000 linker command file has initialized sections on PAGE 0, and uninitialized sections on PAGE 1.  The hex utility always outputs data for PAGE 0 and PAGE 1 in different files.  Usually, no output is needed for PAGE 1, and so only one file is output.  If, for some reason, there are initialized sections on PAGE 0 and PAGE 1, then two files are output.  If you have not specified a name for the second output file, then the hex utility automatically chooses an output file name and issues the warning diagnostic you show in your post.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 65 points
    Hey! Even though I can't pinnpoint the problem exacly you lead me to the right trace.
    In the end the problem was caused by a struct initialization with all 0 within a function in the following manner:

    ThreePhaseAB0 stPWMOutputVoltageAB0 = {0};

    Removing the '=0' let the warning vanish.

    Thank you!
  • 0 in reply to Leif Grundmann
    Prodigy 65 points
    Oh and I forgot: In CLA!