• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 414 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.

Change Build profile

Jibin Scaria
Intellectual 380 points

Hi,

How can I build the syslink_2_10_02_17 rtos samples in release mode?

Thanks

Jibin

  • 0
    TI__Mastermind 18320 points

    Jibin,

    TheSYS/Link Install Guide Wiki discusses how to run examples in debug or release mode.

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

    Dave

  • 0 in reply to David Friedland
    Intellectual 380 points

    Hi Dave,

    Thanks for the reply. Unfortunately the wiki is not mentioning anything about release build in rtos.

    The ARM binary is created in bot release & debug mode eg. messageqapp_debug  & messageqapp_release but the DSP side binary "messageq_ti81xx_dsp.xe674" under debug folder.

    So I think the DSP side binary is build only in debug mode. 

    The wiki mentioning an argument "-p release" to the run scripts. That I suppose it selects the ARM side application. I could not find the run_ scripts anywhere in filesystem or as build output.

    The release build in DSP supposed to link all non-instrumented modules and optimized for size and speed. So release and debug images cannot be the same

    Thanks

    Jibin

     

  • 0 in reply to Jibin Scaria
    TI__Expert 6860 points

    The DSP side sample application are built in debug mode.  Since these are samples, we've made a choice to provide them in such a way as to allow the user to easily debug them.

    If you are so inclined, there is a build file buried in the SysLink release that would allow you to change that.  Let me know if you are interested and can provided details.

    The "-p release" script applies does make a distinction between release/debug but for the ARM-side application (as you implied) and is only relevant to QNX builds.  Frr Linux, you'll have two scripts, 1 for debug and 1 for release.  These profiles also only apply to the ARM-side applications.

    The script are copied onto your target filesystem, when issuing the "make install" command in SysLink.  It copies scripts located in the ti/syslink/tools/scripts directory based on the Device, GppOs, and SDK type set by the products.mak file in SysLink.

  • 0 in reply to Arnie Reynoso
    Intellectual 380 points

    Hi Arnie,

    I really need to build the applications in release mode. That is why I posted this in the form. Please give the changes required to build in release mode.

    Thanks

    Jibin

  • 0 in reply to Jibin Scaria
    TI__Expert 6860 points

    Sorry for the delayed response, it was somehow missed.

    To build the RTOS (slave side) sample applications in release mode you'll need to change the following file in SysLink:

    ti/syslink/buildutils/rtos/buildScripts/test.bld

    In that file, you'll find a buildTest function which set the build profile to "debug", you'll simple need to change this to "release".

    Since your original post, the latest SysLink (2.10.03.20) has provided a couple of stand-alone examples of the TI814X device that can be located in the SYSLINK_INSTALL_DIR/examples directory.  They are simple and self contained.  They also allow for more flexibility and are built with two different profiles on both the GPP and slave-cores.