• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 247 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.

[OMAP3530] Build problems with packages/ti/sdo/fc/utils

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

Issues were raised during discussion of the issue What is build profile "debug_trace"? (used by fc/rman/examples).

Two items:

  1. 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).
  2. Two include files are missing from the distribution (both in xDAIS Framework Components distribution as well as the Codec Engine distribution):  fc/utils/_rmmp.h and fc/utils/_smgrmp.h.

Thoughts so far:

  1. I'm half-inclined to use MVArm9, but that's explicitly suppressed in Codec Engine 2.23.01's example/config.bld.  Because I need *.av5T files for Codec Engine, copying/aliasing a similar ARM tool doesn't immediately work.  (UCArm9 builds .a470uC files, and MVArm9 builds .a470MV files.)  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.)
  2. Perhaps these should be added to the fc/utils/package.bld : Pkg.otherFiles list so they get into future distributions.