• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 5136 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 MyProject.m10" since compiler v17.6

A GIR
Genius 3615 points
Part Number: TMS320F28377S

Tool/software: TI C/C++ Compiler

Hello

I'm working on CCS v7 with a project using the F28377s

This morning, I have updated the compiler from v17.3 to v17.6.

I have the following warning message at the end of link if the both condition are meet:

- Compiler v17.6

- Properties-> Build -> C2000 Hex utility ->"Enable C2000 Hex utility" ticked.

What does mean this warning? How remove it?

Thank

  • 0
    TI__Guru**** 249420 points

    I don't see the diagnostic.  Please perform a complete build, then submit the contents of the Console view (not Problems view).  Use the icon Copy Build Log to save all of the Console view to a file.  Be sure to use the file extension .txt.  Then attach that to your next post.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Genius 3615 points

    Hi

    Please find attached file.

    Warning Log.txt

  • 0 in reply to A GIR
    TI__Guru**** 249420 points

    Unfortunately, you have found a bug in the hex utility.  It issues the diagnostic ...

    warning: Data is being written to auto-generated file SMD_Boot_Project.m10

    ... even though that file is never created.  As far as I can tell, this is the only error the hex utility makes.  The main hex utility output file is present and correct.  This means the workaround is simple: Just ignore this diagnostic.

    I filed CODEGEN-2372 in the SDOWP system to have this addressed.  You are welcome to follow it with the SDOWP link below in my signature.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Genius 3615 points
    Hi,

    Thank for your back.
    I try to follow the CODEGEN-2372 like you said, but this issue is not found..
    Please, could you verify if you d'ont made a mistake on the number "2372"?
  • 0 in reply to A GIR
    TI__Guru**** 249420 points

    It takes a few hours for a new entry to propagate out to the external view.  It should be there soon.  Sorry about that.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Genius 3615 points
    Ok
    Thank for this.
    Have you an idea about the time would take this correction?

    Because one of the safty rules in our project is:
    - Don't have any warning or suspicious message on tool chain (compiler, linker....), else we must made some justifications of this!
  • 0 in reply to A GIR
    TI__Guru**** 249420 points

    A GIR said:
    Have you an idea about the time would take this correction?

    For this specific issue, I don't know.  For similar sorts of issues, a fix is available in something around 3 months.

    Thanks and regards,

    -George