• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 54 subscribers
  • Views 4577 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS3.3 cannot open "custom.lfk"

Jerry Nettleton
Intellectual 350 points
Other Parts Discussed in Thread: CCSTUDIO

I am working on an F2406A project which was originally compiled with Code Composer 4.12.  Now I'm trying to use CCS 3.3 to build it.  After CCS 3.3 creates the project file, I get the following error when I try to build it (on a Windows XP machine).

[serial.c] dspcl -g -k -al -as -fr"C:/dev/Firmware/serial4/ACTIVE" -i"C:/tic2xx/c2000/cgtools/include" -x1 -v2xx -@"Custom.lkf" "serial.c"
>> Cannot open "Custom.lkf"
[serial.c]
TMS320C2x/C2xx/C5x ANSI C Compiler          Version 7.00
Copyright (c) 1987-1999  Texas Instruments Incorporated
   "serial.c"   ==> serial_outbyte
   "serial.c"   ==> serial_init
   "serial.c"   ==> serial_setbaud
   "serial.c"   ==> serial_peek
   "serial.c"   ==> serial_pop

 

How can I resolve this issue?

Jerry

  • 0
    TI__Guru**** 169894 points

    Jerry,

    In CCSv3.x world, the name of the lkf file usually follows the name of the Active Build Configuration. In this case, if you are simply trying to open the CC project in CCS, it is possible that your original project had a Build Configuration named "Custom" but the new CCSv3.3 project does not recognize it.

    In this case I would try to re-create the project from scratch in CCSv3.3 - the correct .lkf file will be automatically created and picked.

    You may want to check other threads that talk about a similar scenario (although none of them have an absolute solution to the problem):

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/178190.aspx

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/76265/278873.aspx#278873

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 350 points

    Good idea but I already tried creating a new project from scratch.

    [main.c] dspcl -g -q -fr"C:/CCStudio_v3.3PLA/MyProjects/TestDsp/Debug" -d"_DEBUG" -v2xx -@"Debug.lkf" "main.c"
    >> Cannot open "Debug.lkf"
    [main.c]

    I've also looked at one of the threads but it didn't offer much help.  I thought it might be a permissions issues (already a local admin) but I'm running on Windows XP which isn't as tight as Windows 7.  Not sure what else to try.

  • 0 in reply to Jerry Nettleton
    Intellectual 350 points

    The "1641.bin.zip" approach worked for me.  It added a bunch of "missing" .EXE files to the bin directory.  I'm concerned about redundant files (espcecially the include .h files).  But at least it's working for now...

    C:\CCStudio_v3.3PLA\C2400\cgtools\bin_old\Bti2400.dll

    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\Bti2400.dll
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\clist.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\crts2xx.lib
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspa.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspabs.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspac.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspar.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspcg.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspcl.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dsphex.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dsplnk.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspmk.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspopt.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\dspxref.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\gmake.exe
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\rts2xx.lib
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\assert.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\ctype.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\dspcio.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\errno.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\file.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\float.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\format.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\ioports.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\limits.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\math.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\memory.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\setjmp.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\stdarg.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\stddef.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\stdio.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\stdlib.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\string.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\time.h
    C:\CCStudio_v3.3PLA\C2400\cgtools\bin\include\values.h

     

  • 0 in reply to Jerry Nettleton
    TI__Guru**** 451251 points

    Jerry,

    Jerry Nettleton said:
    C:\CCStudio_v3.3PLA

    What version of CCS are you using? I get that install directory when I installed 3.3.83.20 and that version does not have build support for F24x by default.

  • 0 in reply to Ki
    Intellectual 350 points

    I'm a newbie at this stuff...  I inherited the legacy code and am trying to support it with the latest tools.  The previous developer used "Code Composer 4.12" which I may need to go back to.

    Yes, my legacy and "TestDsp" projects both use the TMS320C24XX target family.  For building an executable .out file with an migrated legacy project, are there significant differences between C24xx and F24xx?

    What do recommend for F2406A?

     

  • 0 in reply to Jerry Nettleton
    TI__Guru**** 451251 points

    Jerry Nettleton said:
    The previous developer used "Code Composer 4.12" which I may need to go back to.

    CCSv3 should be fine. But some of the latest CCSv3.3 releases took out 24x build support which is why i ask for your version number

  • 0 in reply to Ki
    Intellectual 350 points

    You didn't answer the other questions.  Can I build with the C24XX family for a F24XX target? 

  • 0 in reply to Ki
    Intellectual 350 points

    The "C2000/cgtools" directory has a bunch of files that the "1641.bin.zip" file didn't have in it.  So it looks like there are a bunch of missing files.

    Can I download the C2400 family to get all of the files (e.g. cgtools\include and cgtools\bin) to get better overall/c++ support?

    C:\CCStudio_v3.3PLA\C2000\cgtools\include\access.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\algorithm
     C:\CCStudio_v3.3PLA\C2000\cgtools\include\bitset
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cassert
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cctype
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cerrno
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cfloat
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\ciso646
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\climits
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\clocale
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cmath
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cpp_inline_math.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cpy_tbl.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\csetjmp
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\csignal
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cstdarg
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cstddef
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cstdio
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cstdlib
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cstring
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\ctime
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cwchar
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\cwctype
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\deque
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\exception
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\fstream
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\fstream.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\functional
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\hash_map
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\hash_set
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\inttypes.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iomanip
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iomanip.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\ios
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iosfwd
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iostream
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iostream.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iso646.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\istream
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\iterator
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\limits
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\linkage.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\list
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\locale
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\locale.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\map
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\memory
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\new
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\new.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\numeric
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\ostream
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\queue
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\rope
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\set
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\signal.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\slist
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\sstream
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\stack
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\stdexcept
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\stdint.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\stdiostream.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\stdlibf.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\stl.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\streambuf
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\string
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\strstream
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\strstream.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\typeinfo
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\unaccess.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\utility
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\valarray
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\vector
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\wchar.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\wchar.hx
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\wctype.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xdebug
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xhash
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xiosbase
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xlocale
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xlocinfo
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xlocinfo.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xlocmes
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xlocmon
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xlocnum
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xloctime
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xmemory
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xstddef
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xstring
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xtree
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xutility
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\xwcc.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\ymath.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\yvals.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\_fmt_specifier.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\_isfuncdcl.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\_isfuncdef.h
    C:\CCStudio_v3.3PLA\C2000\cgtools\include\_lock.h

    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\libc.a
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2700.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2700_eh.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2700_ml.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2700_ml_eh.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2800.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2800_eh.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2800_fpu32.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2800_fpu32_eh.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2800_ml.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rts2800_ml_eh.lib
    C:\CCStudio_v3.3PLA\C2000\cgtools\lib\rtssrc.zip

     

  • 0 in reply to Jerry Nettleton
    TI__Guru**** 451251 points

    Jerry - you still have not mentioned what exact version of CCSv3.3 you are using. Again I suspect the reason why those files were missing for you is because you installed a CCSv3.3 version that does NOT have 24x support.

    See the below FAQ to find your full version number:

    http://processors.wiki.ti.com/index.php/CCStudio_FAQ#Q:_How_can_I_find_out_which_CCStudio_3.3_Service_Release_number_is_installed.3F

  • 0 in reply to Ki
    Intellectual 350 points

    You're right.  Thanks.  I have version 3.3.83.20.  So which version should I use to support the F2406A legacy code?

    I have CCS 3.1 on a CD disk or perhaps go back to "4.12".

  • 0 in reply to Jerry Nettleton
    TI__Guru**** 451251 points

    Start a private conversation with me and I will give you more details on how to get the version you need.

    See the bottom of this thread to see how to start a private conversation:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 350 points

    According the wiki page, "CCSv3.3 is the last release to support the F24x/24xx family of microcontrollers."  So I thought I had the right stuff...

    http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v3

    And the "What's New in Code Composer Studio Developer Tools v3.3" manual mentions:

    C2000 Platforms
    – F240 XDS510, XDS560 Emulators
    – F2401 XDS510, XDS560 Emulators
    – F2402 XDS510, XDS560 Emulators
    – F2403 XDS510, XDS560 Emulators
    – F2406 XDS510, XDS560 Emulators
    – F2407 XDS510, XDS560 Emulators
    – F241 XDS510, XDS560 Emulators
    – F243 XDS510, XDS560 Emulators

    http://www.ti.com/lit/an/spraa07c/spraa07c.pdf

    Now I'm confused...

  • 0 in reply to Jerry Nettleton
    TI__Guru**** 451251 points

    The comment is mostly right. The only version that does not have support for 24x is version 3.3.83.20. 24x support was removed for various licensing reasons.