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

CCS/TMS320F28377S: How to tell if running in RAM or FLASH

Eric ***
Prodigy 130 points
Part Number: TMS320F28377S

Tool/software: Code Composer Studio

Perhaps I'm missing something, but when I assign functions to run in RAM via the "__attribute__((ramfunc))" I still see the debugger's disassembly in flash memory (0x80000 and up).  I would expect to see RAM addresses, but I don't, which makes me suspicious that I haven't properly set up the functions to run in RAM.

In the map file, I do see space allocated in "TI.ramfunc" section for source files that should have "RAM functions".

  • 0
    TI__Guru 53765 points
    Hi Eric,

    Looking at the addresses in the disassembly view should be a reliable way to tell if you're running from RAM or Flash. What compiler version are you using? Do you mind sharing your linker command file?

    Just out of curiosity, does using #pragma CODE_SECTION(function name, ".TI.ramfunc"); instead of the attribute work any better?

    Thanks,
    Whitney
  • 0 in reply to Whitney Dewey
    Prodigy 130 points
    Hi Whitney,

    You know, I'm not sure I had a problem to begin with. Upon reexamining the project this morning, I do see my ramfuncs operating out of 0x8000 (RAMLS). I may have been misreading the disassembly locations the other day and adding an extra 0 to the address.

    Just FYI, I have compiler version v15.12.3.LTS. Both "CODE_SECTION" and "__attribute__" work as expected.

    Thanks!
  • 0 in reply to Eric ***
    TI__Guru 53765 points

    Eric,

    Glad it's working. I'll close this thread. Go ahead and start a new one if the issue pops up again.

    Whitney