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

Memory Problem on Delfino F28377D

Ralf Juchem
Prodigy 40 points

Hi,

I am using a controlCard with a F28377D Controller to run some Matlab/Simulink models in Processor in the loop (PIL) configuration. Until now, everything seemed to work fine. I was able to run some smaller example files.

But now, I wanted to run a larger model. It seems that this is quite too large. I got the following error Messages:

C:/MATLAB/SupportPackages/R2015b/texasinstrumentsc2000/toolbox/target/supportpackages/tic2000/src/c28377D.cmd
<Linking>
"C:/MATLAB/SupportPackages/R2015b/texasinstrumentsc2000/toolbox/target/supportpackages/tic2000/src/c28377D.cmd", line 87: error: 
   program will not fit into available memory.  placement with
   alignment/blocking fails for section ".text" size 0x36ca page 0.  Available
   memory ranges:
   RAMM0        size: 0x2de        unused: 0x7          max hole: 0x7
   RAMD0        size: 0x800        unused: 0x6          max hole: 0x6
   RAMLS0_4     size: 0x2800       unused: 0x7          max hole: 0x7       
"C:/MATLAB/SupportPackages/R2015b/texasinstrumentsc2000/toolbox/target/supportpackages/tic2000/src/c28377D.cmd", line 92: error: 
   program will not fit into available memory.  placement with
   alignment/blocking fails for section ".econst" size 0x1f2 page 1.  Available
   memory ranges:
   RAMLS5       size: 0x800        unused: 0x65         max hole: 0x65      
"C:/MATLAB/SupportPackages/R2015b/texasinstrumentsc2000/toolbox/target/supportpackages/tic2000/src/c28377D.cmd", line 89: error: 
   program will not fit into available memory.  placement with
   alignment/blocking fails for section ".cinit" size 0xab page 0.  Available
   memory ranges:
   RAMM0        size: 0x2de        unused: 0x7          max hole: 0x7
   RAMD0        size: 0x800        unused: 0x6          max hole: 0x6
   RAMLS0_4     size: 0x2800       unused: 0x7          max hole: 0x7       
error: errors encountered during linking; "Wrap_AC_Ctrl.out" not built  

Does this really means that my code is too large for the Controller? Is there anything I can do to run it?

Thank you very much,

 

Ralf

  • 0
    TI__Guru** 116041 points

    Hi Ralf,

    Does this really means that my code is too large for the Controller? Is there anything I can do to run it?

    It's not that code is too large for controller but it's not able to fit into section which have been defined in cmd file as of now. What are you using the GSx RAM for?  GSx RAMs are larger RAMs and you should be able to allocate GSx RAM for the .text.

    Regards,

    Vivek Singh

     

  • 0 in reply to Vivek Singh
    Prodigy 40 points
    Hi Vivek,
    thank you for your reply.

    Since I am quite new to using this toolchain, I have no idea how to do this.

    How can I force the linker to use GSxRAM? How much GSxRAM is available?

    Thank you very much,
    Ralf
  • 0 in reply to Ralf Juchem
    TI__Guru** 116041 points
    Hi Ralf,

    We have 128KB of GSx RAMs (16 blocks of 8KB). Please have a look into the linker cmd file. You should be able to change the this file as per your requirement.

    Regards,
    Vivek Singh