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

TMS320F28377D: When the executable consists of both a boot and an app project, how should the TMS320F28377D clear the memory and resources used by the boot code before entering the app?

neil lan
Prodigy 50 points
Part Number: TMS320F28377D


Tool/software:

Hello, experts.

when the boot project  jump to APP，how should the TMS320F28377D clear the memory which boot used?

Did I need to clear the “.ebss”, “.stack”, or “.TI.ramfunc” sections which boot used?

Look forward to your reply.

  • 0
    TI__Genius 11515 points

    Hello,

    In general, yes, but it depends. There could be conflicts when you switch from the bootloader to the app if you didn't take adequate care in the linker command files to separate them and avoid conflicts/overlaps. However, when you switch from the bootloader to the app, if you go through the C initialization routine (provided by the compiler), it will initialize whatever the application needs in RAM and initialize the SP before arriving at main(). In the process, it may end up overwriting some RAM areas that were being used earlier by the bootloader. This should not be an issue since you are not going to switch back live to the bootloader from the application.

    Please refer to this thread:  TMS320F280049C: Will there be a memory conflict when the bootloader and the app share a RAM area? 

    Best,

    Matt