• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 103 subscribers
  • Views 2987 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.

xdc build warning

Sandeep Krishnaswamy
Expert 7290 points
Other Parts Discussed in Thread: SYSBIOS

Hi Champs,

While building the BIOS PSP application using the xdc, i am getting the warning message,

"warning: creating output section ".plt" without a SECTIONS specification"

The binary is built for DM814x - A8 core.

The tool chains being used are,

                   BIOS - 6_33_00_19

                  XDC - 3_23_00_32

                  CG tools for TMS470 - 4.9.0

It looks like some section is missing and it is being initialized by the xdc. Do i need to add something in the .cfg file?

Please find the attached cfg file also.

Let me know, if any more info is required.

Thanks and Regards,

Sandeep K

i2cSample.cfg
  • 0
    TI__Mastermind 20805 points

    Hi Sandeep --

    Do you know which object file has the .plt section?  I think you can find this information from the .map file.   I'm not familiar with the .plt section and we do not explicitly place it in our generated .cmd file.   From google, I see that 'plt' is short for 'procedure linkage table' and seems to be related to dynamic linking which is not a use case we support currently with BIOS.  Are you doing dynamic linking?  I wonder if you are compiling your code with one of the dynamic link options?

    It would be good to understand why the compiler is generating this .plt section or find out where and why it is being used. 

    To workaround the linking problem, you can place the .plt section with something like the following, but I'm worried that you might have problems when you run the code.

    Program.sectMap[".plt"] = "DDR3";

    -Karl-

  • 0 in reply to Karl Wechsler
    TI__Expert 7290 points

    Thanks Karl.

    Adding the entry for .plt section in the cfg file has worked for us.

    Regards,

    Sandeep K

  • 0 in reply to Sandeep Krishnaswamy
    TI__Mastermind 20805 points

    Did you find out which file is providing the .plt section?   It would be good to know how this is getting introduced.   I don't think you should have a .plt.  It would be good to know the root cause for this.  

    -Karl-

  • 0 in reply to Karl Wechsler
    TI__Expert 8890 points

    Karl,

    I have recently seen the same linker warning in my own separate SysBios application:

    warning: creating output section ".plt" without a SECTIONS specification

    Interestingly, this section is not listed at all in the application map file.  I only noticed this warning message after I added some xdc.runtime.memory APIs to my application (i.e. Memory_alloc).  I had previously used the generic malloc instead, and I didn't see this linker warning then.  That may just be a coincidence, but it's the only clue I have.

  • 0 in reply to Joe Coombs
    Intellectual 850 points

     What cause the following build error then using the latest Syslink release 2.00.00.78?

    .dlls files complete: Mon Oct 15 13:48:49 CST 2012.
    ======== .executables [.] ========
    lnke674 bin/ti_platforms_evmTI816X/video_copy_DSP.xe674 ...
    warning: creating output section ".plt" without a SECTIONS specification

     undefined                    first referenced                                                
      symbol                          in file                                                     
     ---------                    ----------------                                                
     Engine_alwaysCollectDspTrace package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674
     Engine_ceDebugDspTraceMask   package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674
     Engine_init                  package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674
     RMS_exit                     package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674
     RMS_init                     package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674
     Server_init                  package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674
     _VISA_init                   package/cfg/bin/ti_platforms_evmTI816X/video_copy_DSP_pe674.oe674

    error: unresolved symbols remain
    warning: entry-point symbol other than "_c_int00" specified:
       "ti_sysbios_family_c64p_Hwi0"
    error: errors encountered during linking;
       "bin/ti_platforms_evmTI816X/video_copy_DSP.xe674" not built
    gmake[1]: *** [bin/ti_platforms_evmTI816X/video_copy_DSP.xe674] Error 1
    gmake: *** [.,.executables] Error 2
    gmake: *** [all] Error 2

     

  • 0 in reply to shawnstone
    TI__Expert 6860 points

    From the error message, it seems that the Codec Engine library (ce.ae674) isn't being found.  Can you pass along your Servers *.cfg file, to see if anything is missing.  Can you also pass along you servers *.xdl file?  This is a generated file (from the *.cfg) that includes all the libraries to be linked in.  This file would be locating in your servers directory under package/cfg/bin/ti_platforms_evmTI816X/*.xdl

  • 0 in reply to Arnie Reynoso
    Intellectual 850 points

    sorry for the delay!

    my files is

    1007.video_copy.cfg

     

     

  • 0 in reply to shawnstone
    TI__Expert 6860 points

    Thanks for the file.  Taking a look at them, it seem you are trying to build a server that only includes Video codec.  The configuration you've passed along seems to be based on the original (all_mc.cfg) all_codes example server.  That configuration is for  homogenous mutli-core devices.  You need to base your server off of the all_syslink.cfg file in the all_codecs server.  This support the heterogeneous multi-core devices (TI814X, TI816X, etc) which is what you are attempting to build for.

    BTW:  Its better to create a post with your issue than to post a question on a existing post.  New posts will yield more visibility then existing post particularly if the original post has already been answered.  You can always place a link in your new post to an old post if you believe its related.

  • 0 in reply to Arnie Reynoso
    Intellectual 850 points

    Thanks for your help and your suggestions,but  i haven't the right and  building errors still exist!

    There is a my_codec.tar.gz,which contains  my xdcpath.mak,_config.bld,and codec directory  ,server directory.following is my _codec.tar.gz.  Thanks!

    http://dl.vmall.com/c0ni6bjnz7

  • 0 in reply to shawnstone
    TI__Expert 6860 points

    I'm unable to download your attachment (can't understand and navigate the site).  Can you post your attachment to the forum, instead of a link?