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

Code Generation Tools in CCS

wqyhandsome
Intellectual 520 points

Hi,

    Our current applicational DSP board--DSP: C6416 and the board designed(XD510-USB2.0), can not support CCS3.3 well and its design team suggest us the CCS2.2 or use the XD560plus(may support CCS3.3 well I think). When using the *.lib(such as fastrts64x.lib), the error message happened: error: illegal relocation type 050002 found in section .debug_info, file fastrts64xe.lib. I hopely know whether I can use the  fastrts64x.lib(except the rts6400.lib)) in my case.

   I have tried to run the mk6x.exe(c:\ti\c6000\cgtools\bin\mk6x.exe), but error still exists. My steps:(1) copy the fastrts62x64x.src in the bin file folder; (2)run the mk6x.exe: mk6x fastrts62x64x.src -mv6400 -l fastrts64xe.lib(3)The message shows divdp.asm is wrong in my command window. I do not know the reason.

TMS320C6000 Optimizing Compiler User’s Guide  comments that the Code Composer Studio provides a graphical interface for using the code generation tools.Could I use the *.lib(they run OK in CCS3.3 environment) in CCS2.2  and How can I get the Code Generation Tools Help?

Appreciated if get your suggestions

[:)]Thanks and Best Regards

  • 0
    TI__Guru**** 451251 points

    Looks like you are trying to use the library from CCSv3.3 with the compiler in CCSv2.2. This issue is covered in this FAQ. Looks like you tried option #1 already (rebuild the library with the 2.2 compiler). You can try option #2 (strip the debug info) and see if that works for you.

    For Code Generation Tools help, the user's guide you reference is a good one. Is there some other type of information you are looking for?

    Thanks

    ki

  • 0
    TI__Guru**** 169894 points

    Hi,

    Just adding to Ki's reply, the fastRTS seems to have an issue when you try to rebuild it from its source. The main problem is that when it tries to extract the <divdp.asm> file that depends on <divc30.asm>, <mpy62.asm> and <flt64.asm>, it cannot find them anywhere.

    In order to workaround this issue, extract the given functions above using the archiver before rebuilding it:

    ar6x -x fastrts62x64x.src mpy62.asm

    ar6x -x fastrts62x64x.src flt64.asm

    mk6x --k --c fastrts62x64x.src -l fastrts64x.lib (or any other library you want)

    If building for big endian, just add -me:

    mk6x --k --c fastrts62x64x.src -me -l fastrts64xe.lib

    This procedure works for both Code Generation Tools 4.3.2 (from CCS2.2) and 6.0.8 (from CCS3.3).

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 520 points

    Hi,

        I have followed your steps and get the new library(fastrts64xe.lib used in CCS2.2)

        The new library is 16kb while the fastrts64xe.lib from CCS3.3 is 34kb. I will try to use the new *.lib in my CCS2.2.

    Thanks for your suggestions

  • 0 in reply to wqyhandsome
    TI__Guru**** 169894 points

    Hi,

    I am glad it worked.

    Just for clarification, the size differences you see in the .lib files are due to the different standards used by the tools to store debug information: CCS2.2 CGT uses STABS and CCS3.3 CGT uses DWARF debug information. Despite this, when the functions are loaded to the DSP the memory used by the functions should be identical or at least very similar, therefore having little effect on your final application.

    Regards,

    Rafael