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.

LInker warnings

Other Parts Discussed in Thread: SYSBIOS

I've suddenly started getting a large number of warnings when linking my project:

remark #10268-D: symbol "_ti_sysbios_family_c64p_EventCombiner_unused__E" is
   mapped to symbol "_ti_sysbios_family_c64p_EventCombiner_unused__F"; mapped
   symbol cannot have definition and reference in the same file
   ("C:\firmware\mybios\Default\configPkg\package\cfg\mybios_p674.o674")

The bios is targetted at a C6746.

Tools are:

  Compiler   V7.0.5

  XDCTools  V3.22.2.27

  SYSBIOS  6.32.3.43

  BIOS build profile is release

 

Any ideas on how to fix this?

 

Thanks,

  Peter Steinberg

  • Peter,

    Are you builiding within CCS?  Was this project previously working before without the remarks?  If this is a project that came from a previous SYSBIOS, XDCTOOLS version, did you try cleaning the project before rebuilding it with the new tools?

    Judah

  • Building with CCS (4.2.4.00033).

     

    I tried a full clean within CCS, and also closing CCS and manually deleting all the release directories and BIOS generated directories.

     

    I'm pretty sure it built without the warnings a few days ago; the most recent changes I recall making in the BIOS area were to set the build profile to "Release" instead of "whole_program" to avoid those warnings.

  • To me the remark is suggesting that generated object file from the *.cfg file (mybios_p674.o674) is not being built with the right profile.

    It appears to me like perhaps this file is old?  One suggestion would be to create a new project and just copy all your sources to the new project?

    I've just created a BIOS project with almost exact versions of all your tools [except my compiler is newer v7.2] and I don't get this remark.

    Judah

  • The CFG file isn't old; I've also manually deleted the generated directories (Default and Src) that the tools build.

    The full .CFG file is:

    var MyBoard_Platform = xdc.useModule('MyBoard.Platform');
    var ti_sysbios_BIOS = xdc.useModule('ti.sysbios.BIOS');
    var ti_sysbios_family_c64p_Cache = xdc.useModule('ti.sysbios.family.c64p.Cache');
    var ti_sysbios_family_c64p_EventCombiner = xdc.useModule('ti.sysbios.family.c64p.EventCombiner');
    var ti_sysbios_family_c64p_Exception = xdc.useModule('ti.sysbios.family.c64p.Exception');
    var ti_sysbios_family_c64p_Hwi = xdc.useModule('ti.sysbios.family.c64p.Hwi');
    var ti_sysbios_knl_Clock = xdc.useModule('ti.sysbios.knl.Clock');
    var ti_sysbios_knl_Event = xdc.useModule('ti.sysbios.knl.Event');
    var ti_sysbios_knl_Mailbox = xdc.useModule('ti.sysbios.knl.Mailbox');
    var ti_sysbios_knl_Semaphore = xdc.useModule('ti.sysbios.knl.Semaphore');
    var ti_sysbios_knl_Swi = xdc.useModule('ti.sysbios.knl.Swi');
    var ti_sysbios_knl_Task = xdc.useModule('ti.sysbios.knl.Task');
    var ti_sysbios_timers_timer64_Timer = xdc.useModule('ti.sysbios.timers.timer64.Timer');
    var xdc_runtime_Defaults = xdc.useModule('xdc.runtime.Defaults');
    var xdc_runtime_Diags = xdc.useModule('xdc.runtime.Diags');
    var xdc_runtime_Log = xdc.useModule('xdc.runtime.Log');
    var xdc_runtime_Main = xdc.useModule('xdc.runtime.Main');
    var xdc_runtime_Memory = xdc.useModule('xdc.runtime.Memory');
    var xdc_runtime_SysStd = xdc.useModule('xdc.runtime.SysStd');
    var xdc_runtime_System = xdc.useModule('xdc.runtime.System');
    var Load = xdc.useModule('ti.sysbios.utils.Load');
    Program.argSize = 0;
    Program.heap = 1048576;
    ti_sysbios_family_c64p_Exception.enablePrint = true;
    ti_sysbios_knl_Clock.timerId = 0;
    ti_sysbios_knl_Mailbox.common$.namedInstance = true;
    ti_sysbios_knl_Semaphore.common$.namedInstance = true;
    ti_sysbios_knl_Task.common$.namedInstance = true;
    ti_sysbios_knl_Task.deleteTerminatedTasks = true;
    ti_sysbios_knl_Task.idleTaskStackSize = 2048;
    ti_sysbios_timers_timer64_Timer.common$.namedInstance = true;
    xdc_runtime_Memory.defaultHeapSize = 1048576;
    xdc_runtime_System.SupportProxy = xdc_runtime_SysStd;
    Program.sectMap[".text:_c_int00"]       = new Program.SectionSpec();
    Program.sectMap[".text:_c_int00"].loadAddress   = 0xc0000000;
    Program.sectMap[".acqVars"] = "IRAM_DATA";
    Program.sectMap[".acqCode"] = "IRAM_CODE";
    Program.sectMap[".servoVars"]   = "IRAM_DATA";
    Program.sectMap[".servoCode"]   = "IRAM_CODE";
    Load.swiEnabled = true;
    Load.hwiEnabled = true;
    ti_sysbios_BIOS.libType = ti_sysbios_BIOS.LibType_Custom;
    

    MyBoard is my hardware's RTSC configuration
  • Peter,

    I took your .cfg file above, commented out a few lines that didn't apply to me and rebuilt a new BIOS example in release profile and it worked fine for me.

    At this point, may I suggest copying your sources files to another directory and create a new project with it there?  The error looks like a result of changing your profile.

    You might also want to comment out the following line to see what happens: "ti_sysbios_BIOS.libType = ti_sysbios_BIOS.LibType_Custom;"

    Judah

  • if I comment out the libType line I get the errors:

    js: "C:/firmware/g2/bios/mybios.cfg", line 49: syntax error
    js: */
    js: .^
    js: "C:/firmware/mybios/bios/mybios.cfg", line 1: Compilation produced 1 syntax errors.
    js: "./package/cfg/mybios_p674.cfg", line 193: Compilation produced 1 syntax errors. (C:/firmware/mybios/bios/mybios.cfg#1)
        "./package/cfg/mybios_p674.cfg", line 272
        "./package/cfg/mybios_p674.cfg", line 180
    gmake.exe: *** [package/cfg/mybios_p674.xdl] Error 1
    js: "C:/Program Files/Texas Instruments/xdctools_3_22_02_27/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake: *** [configPkg/linker.cmd] Error 1
    gmake: Target `all' not remade because of errors.

    I will try creating new projects and coping the files into them and then set all the build properties, etc.  That will take some time.

    Peter

  • Creating and building under a new project looked okay until i enabled the Issue remarks (-pdr) compiler option; then all the messages reappeared.

  • Peter,

    I'm at a lost on why/how you are getting those warnings.  Is it possible that you can make a cut down project that reproduces the error and attach it here?

    Judah

  • The attached should be complete.7608.ti.zip

     

    Peter

  • Peter,

    I was able to reproduce the "remarks".  I was told that this is a known issue.

    In fact, in BIOS, we are explicity supressing these remarks by doing the following and not issue "remarks".

      --diag_remark=10268

    My recommendation would be if you don't want to see the remarks that you do the same thing.

    Judah

  • Thanks.

     

    I knew that I could suppress them, I just don't want to suppress messages without knowing why they occur.

     

    Peter