• 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 » Digital Signal Processors (DSP) » C6000 Multicore DSP » C64x Multicore DSP Forum » C6678 JPEG Problem
Share
C6000 Multicore DSP
  • Forums
  • Announcements
Options
  • Subscribe via RSS
Training Available
TI provides self-paced online training that introduces the primary components of the KeyStone II family of SoC devices.

  • KeyStone II SoC Overview >
  • KeyStone II Software Overview >
  • KeyStone II ARM Cortex-A15 Corepac Overview >
  • More Information >
  • Check out
    Multicore Mix blog
    • $core_v2_blog.Current.Name

      A look back: Two years of Multicore Mix

      Posted 21 hours ago
      by Lauren Reed1
      A big thank you to everyone who participated in our contest last...
    • $core_v2_blog.Current.Name

      It’s our second anniversary, but you get the present!

      Posted 7 days ago
      by Lindsey Bare
      It’s hard to believe it’s already been two years...
    • $core_v2_blog.Current.Name

      Limited time offer: Save $100 on Keystone-based EVM!

      Posted 20 days ago
      by tscheck
      Have you been thinking about ordering a TI Keystone-based EVM...

    Forums

    C6678 JPEG Problem

    This question is answered
    helloti
    Posted by helloti
    on Aug 16 2012 03:28 AM
    Prodigy180 points

    Hello all

    I download the "C66x_jpegenc_02_02_00_01_ELF" and "JPEG Baseline Profile Encoder (v02.02.00) on C66x User's Guide.pdf" on web.

    But, Description of "User's Guide" and  "C66x_jpegenc_02_02_00_01_ELF" don't match.

    I create a new project on ccs5.0.3 then add sourcecodes and build successful. Then debuging "TestAppEncoder.out" , it can not go main.

    the key for the problem is as follow.  In TestAppEncoder.c line 395

        if ((handle = (IALG_Handle)ALG_create (
                (IALG_Fxns *) &DMJPGE_TIGEM_IDMJPGE,  // change to "(IALG_Fxns *)NULL" can go main
                (IALG_Handle) NULL,
                (IALG_Params *) &params)) == NULL)
        {
            printf("\nFailed to Create Instance... Exiting for this configuration..");
            continue;
        }

    What's the problem?

    Do you have a new sample , it can run on ccs5.0.3 correctly ?

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • Hongmei Gou
      Posted by Hongmei Gou
      on Aug 17 2012 13:26 PM
      Intellectual2910 points

      Hi,

      The test application of C66x JPEGENC uses a custom C66x platform which is included in the codec package itself.  Not sure which platform was selected when you created your project. If it was not the right one, it can cause the issue you are observing.

      We do not recommend creating the project from scratch. Instead, please import the project from the release package. If there is any issue during the project importing, compilation, and execution, please let us know and we can help fix it.

      Thanks,

      Hongmei

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • helloti
      Posted by helloti
      on Aug 20 2012 03:06 AM
      Prodigy180 points

      Hi Hongmei:

      First, I tried to import the project. And it was transformed into ccs5 automatically(the original is ccs4).
        Messagebox "Update Managed Build Project" pop up, I click "Yes".
      Then, I changed Build Varibales
        Change BIOS_CG_ROOT from "C:\CCStudio_4.2.3\bios_6_31_00_18" to "C:\Program Files\Texas Instruments\bios_6_32_04_49"
        Change FRAMEWORK_ROOT from "C:\CCStudio_4.2.3\ccsv4\framework_components_3_20_02_29" to "C:\Program Files\Texas Instruments\framework_components_3_22_02_08"
        Change XDC_ROOT from "C:\CCStudio_4.2.3\xdctools_3_20_08_88" to "C:\Program Files\Texas Instruments\xdctools_3_22_01_21"
      Then,
        Add JPEGENC_ROOT "C:\Program Files\Texas Instruments\Codecs\C66x_jpegenc_02_02_00_01_ELF\packages\ti\sdo\codecs\jpegenc\App" to Resource->Linked Resources

      Then, build project, found 34 errors
        Description Resource Path Location Type
        cannot find file "./configPkg/linker.cmd" TestAppEncoder C/C++ Problem
        errors encountered during linking; "TestAppEncoder.out" not built TestAppEncoder C/C++ Problem
        Linking failed. Check the Console window for details. TestAppEncoder Unknown C/C++ Problem
        no valid memory range(NULL) available for placement of ".bss" TestAppEncoder C/C++ Problem
        no valid memory range(NULL) available for placement of ".const" TestAppEncoder C/C++ Problem
        no valid memory range(NULL) available for placement of ".fardata" TestAppEncoder C/C++ Problem
        no valid memory range(NULL) available for placement of ".neardata" TestAppEncoder C/C++ Problem
        no valid memory range(NULL) available for placement of ".stack" TestAppEncoder C/C++ Problem
        no valid memory range(NULL) available for placement of ".switch" TestAppEncoder C/C++ Problem
        no valid memory range(NULL) available for placement of ".text" TestAppEncoder C/C++ Problem
        placement fails for object ".const", size 0xbe9 (page 0) TestAppEncoder C/C++ Problem
        placement fails for object ".stack", size 0x2000 (page 0) TestAppEncoder C/C++ Problem
        placement fails for object ".switch", size 0x48 (page 0) TestAppEncoder C/C++ Problem
        placement fails for object ".text", size 0xd360 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".bss", size 0x30 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".data", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".fardata", size 0x250 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".init_array", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".intDataMem", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".neardata", size 0x10 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object ".rodata", TestAppEncoder C/C++ Problem
        run placement fails for object ".rodata", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object "JPEGIENC_TI_cSect", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object "JPEGIENC_TI_dSect", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        run placement fails for object "JPEGIENC_TI_uSect", size 0x0 (page 0) TestAppEncoder C/C++ Problem
        Unresolved symbol _sysbios_BIOS_start__E in file ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_family_c66_Cache_getMar__E in file ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_family_c66_Cache_setMar__E in file ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_family_c66_Cache_setSize__E in file ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_family_c66_Cache_wbInv__E in file ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_family_c66_Cache_wbInvAll__E in file ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_knl_Task_Object__create__ in file S ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        Unresolved symbol _sysbios_knl_Task_Params__init__ in file S ./Obj/TestAppEncoder.obj .xdchelp /TestAppEncoder 0 C/C++ Problem
        unresolved symbol Ipc_start, first referenced in ./Obj/TestAppEncoder.obj TestAppEncoder C/C++ Problem

      Would you please give me a sample which can run on ccs5?

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Hongmei Gou
      Posted by Hongmei Gou
      on Aug 20 2012 15:01 PM
      Verified Answer
      Verified by helloti
      Intellectual2910 points

      Hi,

      Since JPEG Encoder is verified with the specific set of tools as listed below, please use the same versions instead of changing to the newer versions.

      bios_6_31_00_18

      framework_components_3_20_02_29

      xdctools_3_20_08_88

      Please correct the above, clean the build, and then retry the compilation. If there are still errors, please provide the complete log from the very beginning.

      Thanks,

      Hongmei

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • helloti
      Posted by helloti
      on Aug 20 2012 22:28 PM
      Prodigy180 points

      Hi Hongmei,

      I change the bios,framework and xdctools to the same version. 

          BIOS_CG_ROOT    "C:\Program Files\Texas Instruments\bios_6_31_00_18"

          FRAMEWORK_ROOT    "C:\Program Files\Texas Instruments\framework_components_3_20_02_29"

          XDC_ROOT    "C:\Program Files\Texas Instruments\xdctools_3_20_08_88"

      Then, Clean and rebuild, there are 6 errors as follow

          #error xdc_target_types__ must be defined to name a target-specific header containing definitions of xdc_Int8, xdc_Int16, ... .xdchelp /TestAppEncoder 76 C/C++ Problem
          #error xdc_target_types__ must be defined to name a target-specific header containing definitions of xdc_Int8, xdc_Int16, ... .xdchelp /TestAppEncoder 76 C/C++ Problem
          #error xdc_target_types__ must be defined to name a target-specific header containing definitions of xdc_Int8, xdc_Int16, ... .xdchelp /TestAppEncoder 76 C/C++ Problem
          #error xdc_target_types__ must be defined to name a target-specific header containing definitions of xdc_Int8, xdc_Int16, ... .xdchelp /TestAppEncoder 76 C/C++ Problem
          #error xdc_target_types__ must be defined to name a target-specific header containing definitions of xdc_Int8, xdc_Int16, ... .xdchelp /TestAppEncoder 76 C/C++ Problem
          Linking failed. Check the Console window for details. TestAppEncoder Unknown C/C++ Problem

      Double click the error, it pop up "Quick Fix" dialog, and prompted "var target = xdc.useModule('target');"

      Details see attachment.1781.build_log.txt

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Hongmei Gou
      Posted by Hongmei Gou
      on Aug 21 2012 18:09 PM
      Intellectual2910 points

      Hi,

      According to the log, the "xdc.tools.configuro" command is not correctly executed due to the extra "ti.platform.custom66x" as highlighted below.

      "... xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platform.custom66x -r whole_program -c "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000" ti.platform.custom66x "../JpegEncApp6678.cfg".

      Can you please check your project settings to see if this extra "ti.platform.custom66x" can be removed?

      Two other observations from your log:

      1) the cgtool used for compilation is the default one coming with CCS: "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000". Can you please change that to "Code Generation Tool version 7.2.2" as specified in JPEGENC docs?

      2) for RTSC "Products and Repositories", please have only items under "Other Repositories" checked as shown below. 

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • helloti
      Posted by helloti
      on Aug 21 2012 22:40 PM
      Prodigy180 points

      Hi hongmei,

          Problem resolved. Thanks a lot. 

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Lucifar He
      Posted by Lucifar He
      on Sep 19 2012 00:00 AM
      Expert1235 points

      Hi I have exactly the same problem, but my problem does not solve.

      I use CCS5.2.0.

      Do you have any suggestion

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Hongmei Gou
      Posted by Hongmei Gou
      on Sep 19 2012 13:29 PM
      Intellectual2910 points

      Hi Lucifar,

      Please clean and rebuild the test application, and provide the complete log from the very beginning of the compilation.

      Thanks,

      Hongmei

      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