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

TMS320F280039: variable allocation report warning when doing LFU project

Terry Deng
Expert 3015 points

Part Number: TMS320F280039

Tool/software:

Customer developing the LFU project, new version project enable "preserve" option and set old version .out file as reference.  

They found some new variable in new version project will report warnings as below capture, may we know what is the meaning for this warning? and do it affect the LFU function implement? 

  • 0
    TI__Guru**** 253560 points

    What version of the C2000 compiler (not CCS) is used?  

    The most recent version of the C2000 compiler is 22.6.2.LTS.  Please view this table of defects fixed in that release, from the online readme.  Several are related to LFU.  I cannot guarantee that upgrading to version 22.6.2.LTS will fix your problem.  But I think it is worth the time and effort.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Expert 5915 points

    Terry,

    Please see below jira: 
        sir.ext.ti.com/.../EXT_EP-11487

    This issue can be ignored. It's a nuisance warning due to how lfu places "preserved" variables into subsections of .TI.bound:var. The variable will be placed at the same location as the lfu reference out file and should not impact lfu.


  • 0 in reply to GregM
    TI__Expert 5915 points

    Terry,

    Also, please confirm that the variable involved with above issue is indeed a new variable in the new project. 
    If yes then does it have a location attribute?

    The only variables that get placed into .TI.bound are either variables with location attribute or variables with lfu preserve attribute which were also in the reference executable (ie not new variables in the new lfu build). 

    Above Jira ticket only applies to lfu preserved variables.

    Regards
    Greg