Compiler/TMS320F28027: Program will not fill into available memory

Hi Sharique,

Please share with us the linker command file that you are using and also the .map file generated after build failure. It will allow us to help you further. Thanks.

Sudhakar.

You need to edit your cmd file to provide more space for .cinit. Here's a page with more information on editing the linker command file:

http://processors.wiki.ti.com/index.php/C28x_Compiler_-_Understanding_Linking

Whitney

sir, 

    Please check the attached folder which include linker cmd and .map file. I change the extension of folder by 123 as it not accept .rar extension.

Thanks & Regards,

Sharique 

e2e.123sir,

   Please check the attached folder which include linker cmd and .map file. I change the extension of folder by 123 as it not accept .rar extension.

Thanks & Regards,

Sharique

Sir,

     In my last project i.e., MPPT i used TMS320F280200PTT and i face same issue then i edit the cmd file as some memory from FLASHB transferred to FLASHA and then everything going OK.

Now i used TMS320F28027 in my project and i did same process i.e., editing of cmd file by transferring some memory from FLASHB to FLASHA. Error has gone but software's functionality got malfunctioned. So, now what to do.

Please check the attached folder which include linker cmd and .map file. I change the extension of folder by 123 as it not accept .rar extension.

4300.e2e.123

Hi,

Sharique Hussain said:

program will not fit into available memory. placement with alignment/blocking fails for section ".cinit" size 0x592 page 0. Available memory ranges:     

Simply increase the .cinit size. That's all.

I did check your attached .cmd file. Use the Flash based .cmd file instead of RAM.

Regards,
Gautam

Sir,

     Thanks for your reply.

now it's about .text instead of .cinit

#10010 errors encountered during linking; "InvDisplay_031018.out" not built

program will not fit into available memory.  placement with alignment/blocking fails for section ".text" size 0x2178 page 0.  Available memory ranges: F28027.cmd

Sir, now i attached the whole code, please make correction in cmd file according to code and then send it back to me without any error.

.rar file extension change .123 .

InvDisplay_031018.123

What I'm trying to convey is, instead of using 28027_RAM_lnk.cmd file, adapt your project wrt F28027.cmd
The same can be found here: C:\ti\c2000\C2000Ware_1_00_05_00\device_support\f2802x\common\cmd

Sir,
Now I'm using F28027.cmd instead of 28027_RAM_lnk.cmd file, I add F28027.cmd file from C:\ti\controlSUITE\device_support\f2802x\v127\DSP2802x_common\cmd and delete 28027_RAM_lnk.cmd file from my project.
But that error still exist.

sir,
no solution till yet.

I hope you're using the memcpy function too. Without that F28027.cmd is of no use.

Refer: C:\ti\controlSUITE\device_support\f2802x\v230\f2802x_examples_structs\flash_f2802x

Yes i already used memcopy function too........

Thanks & Regards,
Sharique

Can you combine a couple blocks like shown here?: processors.wiki.ti.com/.../C28x_Compiler_-_Understanding_Linking

For example, combine FLASHC and FLASHD into a FLASHC_D block and replace FLASHC | FLASHD in the SECTIONS specification with FLASHC_D.

Whitney

Sir,

Before combining of FLASHC & FLASHD

PAGE 0:

FLASHD  :  origin = 0x3F0000, length = 0x002000

FLASHC  :  origin = 0x3F2000, length = 0x002000 

FLASHA  :  origin = 0x3F6000, length = 0x001F80 

PAGE 1 : 
FLASHB  :  origin = 0x3F4000, length = 0x002000 

After combining of FLASHC & FLASHD

PAGE 0:

FLASHD_C  :  origin = 0x3F0000, length = 0x002000 

FLASHA       :  origin = 0x3F4000, length = 0x003F80 

PAGE 1 : 
FLASHB       :  origin = 0x3F2000, length = 0x002000 

Error has gone but software's functionality got malfunctioned or hanged. I attached .map file change the extension from .123 to .rar InvDisplay_300918.123check it & further help me to solve this issue

Thanks & Regards,

Sharique

I was expecting FLASHD_C to be length=0x4000 but it looks like you applied the extra 0x2000 to FLASHA instead. I don't think that's necessarily wrong--although it does mean the addresses and ranges no longer match what is listed for the sectors in the datasheet which could lead to some confusion.

Can you give me more details on the malfunction you're seeing? Is it an error? An ITRAP ISR? Where is it hanging?

Whitney

Sir,
After increasing the length of FLASHA, error has gone. But code is malfunctioning just like the below mentioned while loop can't clear and also the other flag checking while loops got hanged or give response after long time or the delays of approximately usec or msec that are used in program give response as a delay of 1-5 secs.

for(i=0;i<=6;i++) // Receive seven bytes from slave RTC chip
{
while(I2caRegs.I2CSTR.bit.RRDY != 1);
*Temp_Pointer++ = I2caRegs.I2CDRR;
if(i==5)
{
I2caRegs.I2CSTR.bit.NACKSNT = 1; // disable receive ack send to slave before to receive last
}
}


Thanks & Regards,
Sharique

Sir, waiting for your valuable reply ......

Thanks & regards,
Sharique

Was the code working before you started getting the linker error or is this the first time you've been able to try running it?

If you look in the register window, is RRDY stuck at zero? If you monitor the I2c signals between the F28027 and the slave, does the data appear to be sent correctly?

Can you elaborate on the issue with the delays? Are you using the delay function from C2000Ware (DSP2802x_usDelay/DELAY_US) or some other technique?

Whitney

Yes code working before that error i.e., program will not fit into available memory, even if i comment any other part of the code the code continues working fine, at this point i analyse from .map file that now i'm close to length 2000 of FLASHA. But after uncommenting length of FLASHA cross the limit of 2000 & delay/malfunctioning/hanging in while loop occurs as i mentioned above in I2C receiving loop.

I saw the signals in oscilloscope when code is working, that's fine.

This delay function i used only in ADC initialization(DSP2802x_usDelay/DELAY_US), for code i used other delays just like the while loop or for loop.


Thanks & Regards,
Sharique

Hi Sharique,

Any progress with your debug? I think I'm still having trouble picturing what the issue is--when .text is large enough to spread beyond a single sector, your delay loops run too long? Are you using the InitFlash() function from C2000Ware to set you wait states? I assume these settings didn't change at any point?

Is there also an issue with the while loop in the code you showed where you're waiting for I2CSTR.RRDY hanging? If you check the RRDY bit in the registers window, does it stay zero, even when you see activity on the oscilloscope?

Whitney

Sir, now i attached the whole code, please make correction in cmd file according to code or if there is any kind of problem using in variables check and then send it back to me without any error.

InvDisplay_031018.rar

Even with the project, there's not much I can do to debug your code since I don't have your hardware. I've already seen your .map file and it seems fine.

I did look over your device initialization code, and I'm wondering why you aren't calling InitFlash()? Also, if you have not done so already, update the #defines in DSP2802x_Examples.h to indicate that you're running at 40MHz so your wait states and delays will be configured correctly.

Whitney

sir,
Sorry for the delay in communication.Nowadays i'm engaging in a railway tender i.e., microprocessor control unit of RMPU for LHB AC coaches. And another staff working on that problem of memory, i already shared your last suggestion to them to solve the problem. But due to busy schedule i'm not in touch with her. So, please give me one month time to come back, till then please don't lock the thread.

Thanks & Regards,
Sharique

Thanks for the update. That's fine. I'll leave the thread open, but if it does happen to automatically lock before you're able to return to this project, just create another thread linking back to this one and we should be able to unlock it.

Whitney