• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 596 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.

Compiler/TMS320F28379D: Need help in linker command file for F28379D

golivi suresh
Prodigy 220 points
Part Number: TMS320F28379D

Tool/software: TI C/C++ Compiler

 i have read like page 0 should always be used for .text and page 1 for other sections.

But i need more memory for .text section in Ram. so Can i use Page 1 for .text and page 0 for other sections? 

  • 0
    TI__Genius 17315 points

    Golivi,

    Any memory type (i.e. RAM or flash) can be assigned to either memory space (i.e. program or data). As an example, during development all code (program and data) could be linked to RAM - this provides for easy debug/re-build with no need to re-flash the device for each change to the code (saving time) and it also allows for 'unlimited' number of breakpoints (based on available PC memory). The C2000 workshops use this methodology, where the lab exercises start with developing in RAM and then the final exercise changes the project to a self- contained 'embedded system' making use of flash. As for using flash in data space, this could be done for tables/constants which cannot be changed.

    While it is not a requirement from a microcontroller hardware or development tools perspective (since the C28x MCU has a unified memory architecture), historical convention is to link code to program memory space and data to data memory space. However, as explained above, this is not a 'strict' requirement. To provide you with a little more history, our very early DSP processors (based on a Harvard memory architecture) had three separate memory maps - program, data, and I/O space. This required the linker command file to have three separate memory section defined for each space. As a result, this carried forward and we still use the two memory spaces (for program and data) to simplify the understanding of the memory type usage. Technically, today with a unified memory architecture, you could have just one space (defined as PAGE 0), and the project should build and load without issue. But again, by convention we still use both program and data in the linker command file memory section.

    To learn more about the linker command file and the F28379D please see the F2837xD Workshops (two versions) at:

    https://training.ti.com/c2000-f2837xd-microcontroller-workshop?context=1137791-1137781

     I hope this answers your question and if so, please click the green "Verified Answer" button. Thank you.

    - Ken

  • 0 in reply to Ken Schachter
    TI__Genius 17315 points

    Golivi,

    It's been a while since I have heard from you last. Therefore, I am assuming that my last reply resolved your issue and I will close this thread. If this isn’t the case, please reject this resolution or reply to this thread. If this thread locks, please make a new thread describing the current status of your issue. Thank you.

    - Ken