• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 579 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.

Original question:

CCS/LAUNCHXL-F28069M: Example_F2806xLaunchPadDemo Compilation failure

CCS/LAUNCHXL-F28069M: Multiple problems compiling and debugging Example_F2806xLaunchPad

Ciaran Brennan
Intellectual 775 points

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: CONTROLSUITE, POWERSUITE

Tool/software: Code Composer Studio

I have a new computer and a new installation of the TI tools, and I'm checking that everything works by running some example projects for the several different LaunchPads I have.  I encountered multiple problems running Example_F2806xLaunchPad, the example code for the LAUNCHXL-F28069M LaunchPad.

I am using ControlSuite 3.4.9, CCS 9.2.0.13, powerSuite 2.5.1

Here is a list of the errors I encountered and the solutions I found for them.

Error:
This project was created using a version of compiler that is not currently installed - 6.1.0 [C2000]. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update.

Solution:
Left click on project and choose Properties. Go to General: Project tab. Change Compiler version from TI v6.1.0 to the latest installed compiler version.

Error:
Product XDAIS v0.0 is not currently installed and no compatible version is available. Please install this product or a compatible version.

Solution:
Properties: General: Products: Unselect XDAIS. Apply and close, then rebuild.

Error:
error: --cdebug_asm_data is no longer supported

Solution:
Properties: Build: C2000 Compiler: Advanced Options: Assember Options: uncheck "Generate asm debug directive (--cdebug_asm_data, -mg)". Apply and close, rebuild.

Error:
"C:/ti/controlSUITE/device_support/f2806x/v140/F2806x_common/cmd/F28069.cmd", line 141: error:
program will not fit into available memory. run placement with
alignment/blocking fails for section ".ebss" size 0x1c2 page 1. Available
memory ranges:
RAML2 size: 0x400 unused: 0x0 max hole: 0x0
.ebss : > RAML2, PAGE = 1

Solution:
Edit the file F28069.cmd. Change line 142 from this:
.esysmem : > RAML2, PAGE = 1
to this:
.esysmem : > RAML3, PAGE = 1

With these changes it compiles, loads, and debugs.  

I'm putting this here mostly to share with anyone else who may encounter these problems.  But I have two questions:

1) Is my fix for the last problem an appropriate change to the .cmd file?  I don't know much about the linker command files yet.  It seemed that nothing else was using the RAML3 block.

2) What changed?  I don't recall all these errors before.  The first two looked familiar, but I don't remember the --cdebug_asm_data problem, and I haven't had to edit the .cmd file to get a demo project to run.

  • 0
    TI__Guru**** 173310 points

    Thank you for summarizing the errors and their solutions. This will surely be helpful for others that may encounter the same issues.

    Ciaran Brennan said:
    1) Is my fix for the last problem an appropriate change to the .cmd file? 

    Yes this is an appropriate workaround.

    Ciaran Brennan said:
    2) What changed?  I don't recall all these errors before.  The first two looked familiar, but I don't remember the --cdebug_asm_data problem, and I haven't had to edit the .cmd file to get a demo project to run.

    The --cdebug_asm_data option was supported in older versions of compiler tools (that were used to create the original example project) but dropped in later compiler versions. A reference thread is here.

    Regarding the need to edit linker command file, that really depends on the size of the output sections generated by the compiler and whether the memory regions to which they are allocated is sufficiently large enough to accommodate the section. The size of the output section can vary slightly from one version of compiler tools to another and sometimes it may be just enough to push it over the available memory. 

    This page further explains some of these concepts: http://software-dl.ti.com/ccs/esd/documents/c2000_c28x-compiler-understanding-linking.html