• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 498 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.

What is build profile "debug_trace"? (used by fc/rman/examples)

Dirk Helgemo
Intellectual 475 points
Other Parts Discussed in Thread: OMAP3530

Context = Codec Engine 2.23.01 for Linux, XDCtools 3.10.03, CodeGen 6.1.8, building for OMAP3530

Several of the package.bld files down in examples/ti/sdo/fc/rman/examples want to build the profile "debug_trace", but this is not defined in XDCtools (neither in xdc/bld/ITarget.xdc nor ti/targets/ITarget.xdc).  This results in build errors "TypeError: Cannot read property "compileOpts" from undefined" from each offending package.bld file.  Adding null checks to skip the build (i.e., "if (targ.profiles[profName] == null)") or seting the profile to just "debug" allows the build to advance, but this is definitely not what was intended.

What compiler and linker options are intended for "debug_trace"?  Perhaps this could be added to XDCtools.  (Looking forward, I didn't see it in XDCtools 3.15.00.50.)

Thanks in advance for any advice,  -Dirk

  • 0
    TI__Expert 7415 points

     Dirk,

    If you try and build the rman examples using the steps listed in the FC release notes, you will see that you need to use the config.bld that is the <FC_INSTALL_DIR>/examples directory.

    This config.bld lists the compiler/linker options to build the debug_trace and trace profiles for the examples.

    Let us know if you have trouble with this.

    Gunjan

  • 0 in reply to Gunjan
    Intellectual 475 points

    Thanks.

    I didn't see any FC release notes bundled inside Codec Engine (nor the FC-specific config.bld).

    Let's see, for Codec Engine 2.23.01, I'll need to get xDAIS Framework Components 2.23.01.  OK, I see examples/config.bld.default inside, and I see how the "debug_trace" and "trace" profiles are generated (as variations of "debug" and "release").

    I'll see if I can either integrate this into Codec Engine's examples/config.bld (maybe I could use an environment variable to turn on FC's tweaks to C64P and MVArm9), or stash FC's config.bld somewhere where it won't get in the way of other Codec Engine example builds.

    I'll keep you posted...  -Dirk

  • 0 in reply to Dirk Helgemo
    Intellectual 475 points

    There seems to be a mismatch on the ARM side of things.  In Codec Engine, I want to build GCArmv5T (and generally this works well), but in Framework Components 2.23.01 there is no such thing (only UCArm9, MVArm9, and Arm9t).  I'm half-inclined to use MVArm9, but that's explicitly suppressed in Codec Engine 2.23.01's example/config.bld.  Ideas?

  • 0 in reply to Dirk Helgemo
    Intellectual 475 points

    Because I need *.av5T files for Codec Engine, copying/aliasing a similar ARM tool doesn't immediately work.  (UCArm9 builds .a470uC, and MVArm9 builds .a470MV.)  And fortunately there appear to be only three files that call this out:  {acpy3,dman3,utils}/package.bld.  (All the other package.bld files follow whatever is set in Build.targets[], so they happily build GCArmv5T for Codec Engine.)