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

Migrating from 33 to 52 - Linker issues

Geir
Intellectual 335 points

Other Parts Discussed in Thread: SYSBIOS

Hi,

I had to pick up an old project, which I decided to port  to 5.2. I used the wizard, and i have tweaked the paths in eclipse.
It seems like it is not picking up the symbols generated by DSP/BIOS at the final link stage.

So every symbol defined in the tcf file is undefined.

warning #10247-D: creating output section ".tskNdkStackTest$stk" without a
   SECTIONS specification
warning #10247-D: creating output section ".vers" without a SECTIONS
   specification
warning #10210-D: creating ".stack" section with default size of 0x400; use the
   -stack option to change the default size
warning #10210-D: creating ".sysmem" section with default size of 0x400; use
   the -heap option to change the default size

moving on....

undefined                first referenced                                                       
  symbol                      in file                                                            
 ---------                ----------------                                                       
 BUF_2KB$databeg          ./dsk6455cfg.obj                                                       
 CLK_A_TABBEG             ./dsk6455cfg.obj                                                       
 CLK_F_isr                ./dsk6455cfg.obj                                                       
 DDR2$B                   ./dsk6455cfg.obj                                                       
 DDR2$L                   ./dsk6455cfg.obj        

and so on.....

Ideas anyone?.

I will probably have to read a couple of thousand pages in order to get this up and running, but any hints are welcome.

geir

  • 0
    TI__Guru*** 130875 points

    Hi Geir,

    if you are not migrating BIOS at the same time then things should be easier for you :  )

    In general the errors you are getting seem to be from two areas

    - the undefined symbols come from the linker not being able to find the path to a library for example.  It is normal when importing a project into v5 to have to fix/check/add to the include paths and variables.  This wiki covers that topic

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    It also looks like you might be getting errors related to your linker command file setting as well (the SECTIONS and memory definition errors).    This could be from BIOS migration.   Were you using a tcf file previously?  In CCSv5 BIOS uses cfg files. 

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

    Please keep us informed how things go.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 335 points

    Thanks,

    I played around with different include files and managed to get the undefined symbols to go away.

    That left the problem with the SECTIONS specifications which was solved by editing my own cmd file.The fact that CCS5 generates it's own .cmd file based on the .tcf file was not obvious. So the trick with removing the include file form your own cmd file did not work at all.

    So it compiled, will test it tomorrow.

    I have not updated the to SYS/BIOS, need to read up on it. Why should we go for it?

    I have to say that the documentation for CCS is extremely fragmented. I normally work with FPGA designs, which has it's share of pdf's..But CCS is the worst ever...

    Anyway thanks for your help.

    geir

  • 0 in reply to Geir
    TI__Guru*** 130875 points

    Hi Geir,

    very glad to hear you are past the issues and sorry for the inconvenience.  We are always working to try and improve our documentation.

    Thanks for the update and all the best with development.

    Best Regards,
    Lisa