• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Embedded Software » Linux » Linux forum » Undefined reference to [codec_name]_IVIDENC and [codec_name]_IDMA3 When building module test in Appro Framework
Share
Linux
  • Forum
Options
  • Subscribe via RSS

Forums

Undefined reference to [codec_name]_IVIDENC and [codec_name]_IDMA3 When building module test in Appro Framework

This question is answered
Matt Clarkson
Posted by Matt Clarkson
on Jan 28 2011 05:42 AM
Intellectual920 points

Hello,

I have got an XDAIS codec engine built using the XDC tools for the DM368.  It has two structures defined in the main .c file:

IVIDENC_Fxns [codec_name]_IVIDENC = { // Module_vendor_interface

{IALGFXNS},

[codec_name]_process,

[codec_name]K_control,

};

and

IDMA3_Fxns [codec_name]_IDMA3 = { // Module_vendor_interface

&[codec_name]_IALG, // IALG functions

[codec_name]_dmaChangeChannels, // ChangeChannels

[codec_name]_dmaGetChannelCnt, // GetChannelCnt

[codec_name]_dmaGetChannels, // GetChannels

[codec_name]_dmaInit // Initialize logical channels

};

and it builds fine into a package.

 

I then include this into the av_server.cfg in the Appro framework and perform a full build and i get the following error

make[2]: Entering directory `/home/user/work/svn/appro/ipnc/av_capture/application/test/moduletest'

moduletest: Linking to .out

/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -lpthread -lpng -fPIC -lasound -o/home/user/work/svn/appro/ipnc/av_capture/build/../bin//moduletest.out /home/user/work/svn/appro/ipnc/av_capture/build/lib//moduletest.a /home/user/work/svn/appro/ipnc/av_capture/build/lib//alg.a /home/user/work/svn/appro/ipnc/av_capture/build/lib//drv.a /home/user/work/svn/appro/ipnc/av_capture/build/lib//alg.a /home/user/work/svn/appro/ipnc/av_capture/build/lib//image_tune.a /home/user/work/svn/appro/ipnc/av_capture/build/lib//osa.a /home/user/work/svn/appro/ipnc/av_capture/build/lib//csl.a /home/user/work/svn/appro/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/cmem/lib/cmem.a470MV /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/alg_facetrack_ti.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/src/alg_config/linker.cmd  /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/alg_vstab_ti.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/alg_gbce_ti.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/alg_osd_ti.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/fr_ti/alg_fr_ti.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/fr_ti/libeOkaoFr.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/fr_ti/libeOkaoPt.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/lib/fr_ti/libeOkaoCo.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/src/aewb_ti/lib/libti_awb.a  /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/src/aewb_ap/lib/Appro_2a_lib.a /home/user/work/svn/appro/ipnc/av_capture/build/../framework/alg/src/aewb_ap/lib/Appro_aew_control.a /home/user/work/svn/appro/dvsdk_2_10_01_18/dm365mm/lib/libdm365mm.a

/home/user/work/svn/appro/ipnc/av_capture/framework/alg/src/alg_config/package/cfg/alg_server_x470MV.o470MV:(.data.rel+0x1a4): undefined reference to `[codec_name]_IVIDENC'

/home/user/work/svn/appro/ipnc/av_capture/framework/alg/src/alg_config/package/cfg/alg_server_x470MV.o470MV:(.data.rel+0x1a8): undefined reference to `[codec_name]_IDMA3'

collect2: ld returned 1 exit status

make[2]: *** [exe] Error 1

make[2]: Leaving directory `/home/user/work/svn/appro/ipnc/av_capture/application/test/moduletest'

I don't understand when the reference is undefined.  Is it a problem with:

  • The Codec Engine build?
  • The AV Server Build?
  • The module test build?

 

 

codec engine DM368 appro XDAIS
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Anshuman Saxena
    Posted by Anshuman Saxena
    on Jan 31 2011 00:59 AM
    Verified Answer
    Verified by Anshuman Saxena
    Mastermind19870 points

    Hi,

    Can you share your alg_server.cfg file and the exact place where you have placed the new algorithm?

    Also, possibly share the complete "alg_config" folder inside framework/alg. This is a generated folder.

    I assume you have done make clean all before doing make again.

     

    Regards,

    Anshuman

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Matt Clarkson
    Posted by Matt Clarkson
    on Jan 31 2011 03:23 AM
    Verified Answer
    Verified by Anshuman Saxena
    Intellectual920 points

    Hi Anshuman,

    Thanks for responding.  I managed to fix this.  Our package.xs wasn't returning the library, it didn't have a return case for the MVArm9.

    Thanks

    Matt

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use