• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 100 subscribers
  • Views 621 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.

CCSv5.3 - SYSBIOS configuration fails after upgrading from 5.2.1

JohnDedes
Prodigy 100 points
Other Parts Discussed in Thread: SYSBIOS

UBUNTU 12.04 (32 bit)

After upgrading CCS to 5.3.0 SYSBIOS cannot be configured.

generating custom ti.sysbios library makefile ...
generating custom ti.sdo.utils library makefile ...
Starting build of library sources ...
making $PROJECT_DIR//Release/configPkg/CustomBldSysBios/utils.a64P ...
gmake: *** $PROJECT_DIR/Release/configPkg/CustomBldSysBios/utils: No such file or directory.  Stop.
gmake[1]: *** [$PROJECT_DIR/Release/configPkg/CustomBldSysBios/utils.a64P] Error 2
Build of libraries failed.

With 5.2.1 instead of making utils.a64P it was doing:

making $PROJECT_DIR/Release/configPkg/CustomBldSysBios/sysbios/sysbios.lib ..

This step seems to be missing after upgrading tools.

Tried using separate workspaces to no avail.

Weird thing is that a utils directory is created in the wrong place! A $PROJECT_DIR/src/utils directory is created, while it seems the tool was expecting it under $PROJECT_DIR/Release/....


Also the XGCONF editor results in a cryptic message: "Sorry, I'm having problems creating this editor. An unexpected exception was thrown"

Any suggestions as to how to proceed would be appreciated.


John Dedes

  • 0
    TI__Mastermind 37985 points

    John,
    can you check the version of SYS/BIOS you are using? By default, 5.3.0 ships with SYS/BIOS 6.34.2.18 and XDCtools 3.24.5.48. If you go to Project Poperties->CCS General->RTSC, you'll be able to see the version of SYS/BIOS and XDCtools.

    Is there any reference to the module 'xdc.cfg.SourceDir' in your CFG script? That module controls the custom libraries built at the config time, so if you are configuring that module, please post the relevant part of the CFG script.

    Also, if you can post any makefile or makefile.libs file that you can find under $PROJECT_DIR/src, that would help.

  • 0 in reply to Sasha Slijepcevic
    Prodigy 100 points

    Indeed the SYSBIOS version is 6.34.2.18 and the XDC version is 3.24.5.48.

    There is no reference to the xdc.cfg.SourceDir in the cfg script.

    Previously we were using the following three lines in the cfg:

    BIOS.libType = BIOS.LibType_Custom;
    BIOS.customCCOpts += " -Dxdc_FILE=__FILE__ ";
    BIOS.libDir = "CustomBldSysBios";

    which when I comment out the build is successful.

    The makefile( appended a .txt to upload) is from $PROJECT_DIR/src/utils, while .

    3060.makefile.libs.txt

  • 0 in reply to JohnDedes
    Prodigy 100 points

    {something seems to have gone wrong uploading}

    The makefile is missing from the previous post and a sentence is replaced by .! 

    8865.makefile.txt

    Hope this helps.

  • 0 in reply to JohnDedes
    TI__Mastermind 18320 points

    John,

    I had marked this thread as Answered, but there actually seems to be some uncertainty on whether this was proper.  Can you give us an update/summary of where you are with respect to this issue?

    Thanks,

    Dave

  • 0 in reply to David Friedland
    Prodigy 100 points

    Dave,

    No the issue still remains. The workaround, for now, is not to use a custom build of the BIOS, i.e. the three lines in the .cfg have been commented out.  I have posted the files requested but nobody seems to have looked at them yet.  Were they helpful?

    Thanks

  • 0 in reply to JohnDedes
    TI__Mastermind 30830 points

    John,

    Configuring the UNDOCUMENTED BIOS configuration parameter "BIOS.libDir" is not currently a supported option and leads to the problem you are facing.

    The workaround for the problem introduced by setting "BIOS.libDir" requires setting yet another UNDOCUMENTED and UNSUPPORTED configuration parameter.

    var Build = xdc.useModule("ti.sdo.utils.Build");
    Build.libDir = "CustomBldSysBios";

    While this will probably get you going again, there is no guarantee that this favorable behavior will be preserved with newer releases of SYS/BIOS and/or IPC products.

    Alan

  • 0 in reply to Alan DeMars
    Prodigy 100 points

    Alan,

    Thanks for the reply. After following your suggestion:

    generating custom ti.sysbios library makefile ...
    generating custom ti.sdo.utils library makefile ...
    Starting build of library sources ...
    making /home/jdedes/testSandbox/trunk/software/dsp/ti64x/audio/XYZ/Release/configPkg/CustomBldSysBios/utils.ae64P ...
    gmake: *** /home/jdedes/testSandbox/trunk/software/dsp/ti64x/audio/XYZ/Release/configPkg/CustomBldSysBios/utils: No such file or directory.  Stop.

    It seems to me we are going in circles. The point of the custom build had been to help us in debugging crashes. As this method of doing custom builds is unsupported going forward, I would appreciate it if you can point me to some documentation on how to do custom BIOS builds. Our products have been based on CCS 5.1 so far and we are exploring upgrading to the latest ones.

    Regards

  • 0 in reply to JohnDedes
    TI__Mastermind 30830 points

    I was able to reproduce the results you were getting and by adding the config file changes I suggested, the problem cleared up.

    If you're willing to post your CCS project, I'd be happy to look into this more closely.

    Perhaps just sharing the config script would be sufficient.

    Alan