• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 84 subscribers
  • Views 241 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.

TMS320F280049C: issue of #pragma DATA_SECTION

xu chunlei
Prodigy 100 points
Part Number: TMS320F280049C

Tool/software:

Hi

when I set a variable to a fixed RAM address，but when I use CCS for debug，and watch the value from memory browser I saw this variable still equal 0,but when I have initialized this value to 1, So why this ？

code configuration as below：

CMD configuration ：

CCS memory browser result ：

  • 0
    Prodigy 100 points

    I though the value should be 1 at address 0x008FFD

  • 0 in reply to xu chunlei
    TI__Mastermind 23280 points

    Hello,

    The appropriate expert for this question is currently out of office, returning on Monday 9/16. Please expect a response back by then.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 100 points

    Hi Luke,

    Thanks for remind.

    just add another information for this issue, I noticed that in .map file  there is not address allocation for this varibale .

  • 0 in reply to xu chunlei
    TI__Mastermind 20876 points

    Hi Xu,

    Please ensure the continuous refresh is enabled in your CCS Window.

    Best,

    Ryan Ma

  • 0 in reply to Ryan Ma
    Prodigy 100 points

    Hi Ryan,

    Thanks for your reply.

    I have enabled the continuous refresh  in CCS Window but the value in address "0x008FFD" still 0 ，as below, is there any other reasons?

    another findings : this variable “cnt_clatest” only defined but not used , if I used it as below， I will saw the value is 0x2, So it seems variable need be used or it can't be assigned the correct value?

    best&regards

    lucas

  • 0 in reply to xu chunlei
    Guru 55553 points

    Hi,

    Seems like RAM1 length overlaps RAM10 origin by a DWORD, surprised compiler does not flag a warning. Perhaps reduce extent RAM1 minus one word. Alternatively make RAM10 origin 0x00008FFE or 0x00008FFFF avoids a memory overlap.

  • 0 in reply to Genatco
    Prodigy 100 points

    Hi Genatco,

    I have shorten RAM1 length to 0x000FF0(minus more than one word

    ) ,but the variable "cnt_clatest" in 0x008FFD still 0, Maybe this is not the root cause?


    CMD file as belwo:

  • 0 in reply to xu chunlei
    TI__Mastermind 20876 points

    Hi Xu,

    I am still unable to replicate this issue. Once I had enabled continuous refresh with the original linker command settings for Ada, I was able to see the value in memory updated accordingly.

    CAn you try moving line 185, after 186?

    Best,

    Ryan Ma

  • 0 in reply to xu chunlei
    Guru 55553 points
    xu chunlei said:
    shorten RAM1 length to 0x000FF0(minus more than one word

    Hi xu,

    There is an x49c errata, end of LSRAM sections must be defined 1 word below end length. Wondering if that could be the issue? Perhaps use CCS editor memory browser check if the #prama was copied to LSRAM section.