• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 590 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.

CCS v3.3 to v4.0 Migration + INTERNAL ERROR: ... failed to allocate memory

Sinoj B S
Intellectual 540 points
Other Parts Discussed in Thread: TMS320F2812

Hi,

Target: TMS320F2812

IDE: CCS v4.0 (32K MCU Core)

I have migrated CCS v3.3 project to CCSv4.0 following the guidelines from the below link:

http://www.tiexpressdsp.com/index.php/C2000_Getting_Started_with_Code_Composer_Studio_v4

I'm not using DSP/BIOS and I have modified the v3.3 *.pjt file as specified. I ended up with the following warning and error.

warning: creating output section "XIntfRegsFile" without a SECTIONS specification

INTERNAL ERROR: D:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\lnk2000.exe failed to allocate memory

This is a serious problem. Please contact Customer Support with this message and a copy of the input file and help us to continue to make the tools more robust.

>> Compilation failure

D:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [MyProject.out] Error 1

D:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: Target `main-build' not remade because of errors.

Build complete for project MyProject

Please guide on this to rectify the problem.

-SBS

  • 0
    TI__Guru**** 464711 points

    Is your code under 32K? Just wondering if you are hitting the 32K linker limitation...

  • 0 in reply to Ki
    Intellectual 540 points

    Hi,

    The problem got solved.

    The error message disappeared whenever I restarted CCS v4.0 and build the project again. The build was successfull. But some other times the error message came back. The warning was remained. I checked the checkbox to override warnings in linker options. The warning message also gone.

    I guess the problem is:

    I had a CCS v3.2 eralierly installed on the same PC but in another directory. It was not unistalled.  Also CCS v4.0 was not installed as an administrator.

    -SBS