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

Strange CCSv4 error with C6713

Sean Bedford
Expert 1560 points

Strange in the fact that it is not actually telling me what the error is, there is just a file path to csl6713.lib and the build is sucesful?  This is the error that appears:

Severity and Description                                                                                    Resource   Path   Location   Creation Time        Id
\Program Files\Texas Instruments\ccsv4\C6xCSL\lib_3x\csl6713.lib"     14du                       line 0         1296749884333   10877

I tried to load the program and it says

TMS320C671X: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.

Acording to the map file everything fits in IRAM and there is still redundant space.

Has naybody come accross anything like this before?

Many thanks

Sean

 

 

  • 0
    TI__Guru**** 173310 points

    Sean,

    I don't recall ever seeing a message like this in the Problems view. Is there any message in the CCS build console? Is this library just being linked in directly to your project?

    Are you loading to a DSK6713 or a simulator?

  • 0 in reply to AartiG
    Expert 1560 points

    Hi Aarti,

    I am loading to our own board by a XDS510PP Plus.  I assume the library is loaded as a result of including csl.h.  I dont think it is a problem with the library though as it just appears to be the end of the linker arguments.  The console doesn't report any errors just warning as a result of some of the codes functionality being excluded.  The error only has one question mark and does seem to be the end o the argument invoking the linker.  The text from the console window is below.

    Sean

     

    **** Build of configuration Debug for project 14du ****

    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all

    'Building file: ../main.c'

    'Invoking: Compiler'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6700 -g --define=CHIP_6713 --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/C6xCSL/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/DSK6713/c6000/dsk6713/include" --include_path="C:/CCS_projects/14du/Debug" --include_path="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/bios/include" --include_path="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/rtdx/include/c6000" --diag_warning=225 --preproc_with_compile --preproc_dependency="main.pp" "../main.c"

    "../main.c", line 391: warning: argument of type "unsigned char *" is incompatible with parameter of type "char *"

    "../main.c", line 83: warning: variable "oldTime" was set but never used

    "../main.c", line 84: warning: variable "FastLoopTime" was set but never used

    "../main.c", line 85: warning: variable "PpsTime" was set but never used

    "../main.c", line 86: warning: variable "FloopTime" was set but never used

    "../main.c", line 87: warning: variable "AlignTime" was declared but never referenced

    "../main.c", line 88: warning: variable "KnackeredTimings" was declared but never referenced

    "../main.c", line 89: warning: variable "ComPortFull" was declared but never referenced

    "../main.c", line 90: warning: variable "RTSCount" was declared but never referenced

    "../main.c", line 98: warning: variable "td" was declared but never referenced

    "../main.c", line 129: warning: variable "str" was declared but never referenced

    "../main.c", line 407: warning: function "update_calib" was declared but never referenced

    "../main.c", line 684: warning: function "linearise_all_gyroscopes" was declared but never referenced

    "../main.c", line 691: warning: function "linearise_all_accelerometers" was declared but never referenced

    'Finished building: ../main.c'

    ' '

    'Building target: 14du.out'

    'Invoking: Linker'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6700 -g --define=CHIP_6713 --diag_warning=225 -z -m"14du.map" --warn_sections -i"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/lib" -i"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" -i"C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/rtdx/lib/c6000" -i"C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/bios/lib" --reread_libs --rom_model -o "14du.out" -l"./14ducfg.cmd" "../link.cmd" "./time.obj" "./rs232.obj" "./pps.obj" "./main.obj" "./linearfit.obj" "./imu.obj" "./icomtx.obj" "./flash.obj" "./filter.obj" "./commandrx.obj" "./calib.obj" "./boot.obj" "./SPI.obj" "./QUATERN.obj" "./MATRIX.obj" "./FASTLOOP.obj" "./ERRORS.obj" "./ALIGN.obj" "./14ducfg_c.obj" "./14ducfg.obj" -l"C:\Program Files\Texas Instruments\ccsv4\C6xCSL\lib_3x\csl6713.lib"

    <Linking>

    'Finished building target: 14du.out'

    ' '

    Build complete for project 14du

  • 0 in reply to Sean Bedford
    Expert 1560 points

    Hi,

    I have managed to get rid of the error.  It is down to having a file named ERRORS.c.  If i rename this file it doesn't have the errors so I assume there must be a clash somewhere with something in the library.  This seems to me like a ccs bug at least with the error message that should be displayed.

    Sean

  • 0 in reply to Sean Bedford
    TI__Guru**** 173310 points

    Sean,

    I can duplicate this issue. It seems to be due to a combination of ERRORS.c and specifying the csl library using the full path in the --library option (under Project Properties->C/C++ Build->Linker->File Search Path). If the --library option is modified such that only the library name is specified there (without the full path), and the path were instead added to the --search_path option, then it does not generate the error. Also as you mentioned renaming the source file to something other than ERRORS.c also gets rid of the error. I will submit a bug on this and update this post with the bug number.

     

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    FYI, tracking # for this bug is SDSCM00039251.

  • 0 in reply to AartiG
    Expert 1560 points

    Ok thanks aarti