• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 323 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.

Original question:

CCS/TMS320F28377S: Warning message : " [W9999] Register write access is in the delay slot of a write of the same register...

CCS/TMS320F28379D: Register write access issue

Jonathan Ehlmann
Prodigy 80 points
Part Number: TMS320F28379D

Tool/software: Code Composer Studio

I'm compiling a c file, pll_symetric.c and the assembly throws the following error:  

"pll_symetric.asm", WARNING! at line 463: [W9999] Register write access is in the delay slot of a write of the same register
ADDF32 R0H,R1H,R2H ; [CPU_FPU] |168|

I have not programmed anything in assembly, why am I getting this.  Do I need to worry about it?  Why doesn't the compiler fix this?  I've tried 18.12.4 and 18.12.5 compilers.  

  • 0
    TI__Guru**** 249860 points

    The compiler has automatically generated assembly code for which the assembler issues this warning.  That should not happen.  For the source file pll_symetric.c, please follow the directions in the article How to Submit a Compiler Test Case.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 80 points

    Seems like a pretty serious thing if the data in the register is being overwritten.  Do I need to fix anything?  

  • 0 in reply to Jonathan Ehlmann
    TI__Guru**** 249860 points

    Please understand that this is a disagreement between the compiler and the assembler.  The compiler does not generate assembly code which has problems in the execution pipeline like that.  But the assembler thinks there is a problem, and so it issues that diagnostic.  That is why I need a test case which allows me to reproduce the problem.  Once I have that, I will file an issue with the development team, and they will investigate.  

    In the meantime, test the code.  If the compiler is correct, and the assembler is wrong, everything will work just fine.

    Thanks and regards,

    -George