• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 759 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.

Dynamic Memory Allocation failure between CCS v4 and CCS v5

David Meyers
Prodigy 70 points

Other Parts Discussed in Thread: OMAP-L138

I upgraded from CCS v4  to CCS v 5.2.0.00069 and attempted to run the same code on the Zoom Omap-L138 EVM with the TMS3206748 installed.  The code fails in v5 becuase the dyanmic memory allocation does not appear to be working. I originally experienced a similar problem using CCS v4 when running on Windows Vista machine but it was subsequently solved by installing the CCS v4 on a Windows 7 machine (this problem may have been due to security/account settings etc. differences or a link I found suggesting setting the flag to create a heap in the DDR memory (see Memory Allocation for "new" C6748, which may have been one of the ways I initially solved this dyanmic memory allocation issue.).  I am now running both CCS v4 and CCS v5 on the same Windows 7 machine -and v4 works and v5 does not.  When I compared Tconf Script file parameters they all appear to be the same between the two projects.   In my view there is either a CCS v5 install problem or there is settting that did not port over to CCS v5 project file.  Is there a way to automatically compare the settings? Is there any issues I need to be concerned with during the v5 install? Any other places to look?

  • 0
    TI__Guru**** 173310 points

    Sorry about the late reply to this. Are you saying that the same project built with CCSv4 works but fails with CCSv5? What exactly is the symptom of failure, and how did you isolate it to be due to dynamic memory allocation? Have you tried increasing the heap size to see if that helps?

    Did you simply import the CCSv4 project into CCSv5 and rebuild? CCSv5, by default, uses different versions of the compiler tools, BIOS etc than CCSv4, so that could be one difference. Something you could try as a test would be to set the project in CCSv5 to use the same version of compiler tools and BIOS that were used with CCSv4. This page describes the process to do it. That should produce an output similar to what you had with v4 and you can confirm if that works well. After that incrementally moving to the newer versions of compiler and BIOS might help isolate the issue further.

  • 0 in reply to AartiG
    Prodigy 70 points

    I discovered the problem. It turns out that the link to the GEL file was lost.  It is not obvious this has happened since it only affected the dynamic memory allocation and not the other code.  TI should make the GEL file link more obvious so that  you don't have to go to an obscure place on the advanced page under initialization scripts to see the problem. 

    Thanks