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

TMS320F28379D: Build error: program will not fit into available memory

Sarika Natu
Prodigy 10 points
Part Number: TMS320F28379D

Hello TI support,

I am using the TMS320F2837xD  device with its RAM_link.cmd file and I am getting the "program will not fit into available memory" error.

When I try to increase the length of RAMLS5 to 0x850 which builds my code, but then code stucks in PLL initialization

Please help me find a solution to my problem. Let me know in case you need any other details.

Thank you!

  • +1
    TI__Mastermind 32585 points

    Hi Sarika,

    You cannot change the size of the LS5RAM in the linker command file. As you can see in the device memory map, LS5RAM size is 0x800 and it is followed by D0RAM

    You might have used D0RAM for other sections, leading to a conflict.

    What you could do is combine LS5RAM with other available RAMs.

    Eg: .const : >> LS5RAM  | GS0RAM

    If this does not work, you can combine consecutive memory regions to form a larger memory region.

    Eg : 

       RAMGS0           : origin = 0x0000C000, length = 0x00001000
       RAMGS1           : origin = 0x0000D000, length = 0x00001000
    can be replaced with
       RAMGS01          : origin = 0x0000C000, length = 0x00002000

    Regards,

    Veena

  • 0 in reply to Veena Kamath
    Prodigy 10 points

    Thank you, Veena. Combining LS5RAM and GS0RAM resolved my issue. 

    For my understanding, what is the probability of occurring this issue again? Also, would this change affect GS0RAM memory?

  • +1 in reply to Sarika Natu
    TI__Mastermind 32585 points

    Since you are using GSRAM, I like to highlight that GSRAM is shared between CPU1 and CPU2; make sure CPU2 does not overwrite it. 

    Regards,

    Veena