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.

GLSDK - correct combination of tools

I am trying to use the hardware encoding and decoding functionalities of OMAP5.

I am trying to use GLSDK 6.04.00.02. I have some problems at linking time. I get some unresolved symbols errors. Maybe  something it's wrong with the compatibility.

I am using the following versions of  the tools:

xdctools_3_25_05_94
bios_6_37_02_27
codec_engine_3_24_00_08
framework_components_3_24_00_09
xdais_7_24_00_04
edma3_lld_02_11_05_02
osal_1_24_00_09

Can you please give me a correct combination for this versions?

Thanks,

    Alexandra

  • Alexandra,

    What are you trying to build and what is the error that you get?

    Some information that can help you:

    The GLSDK installer contains scripts that will set up the required tool versions.

    Please refer to the software developers guide in the docs folder of the installer or alternately run the ./setup.sh after setting the GLSDK environment variable and answer yes to the question about the Ducati tools and downloading the required sources.

    These two steps will take time but it will ensure you have the right environment.

    After it is completed, you can run "make dspdce" or "make ipumm" and that should build everything fine.

    Regards

    Karthik

  • Hi Karthik,

    I am trying to build ti-glsdk_omap5-uevm_6_04_00_02 and i get an error regarding unresolved symbols. I attached a file with the exact error message.

    I can't run ./setup.sh because the required sources can't be downloaded. Maybe it's because https://git.ti.com doesn't work anymore.

    What should I do in this case?

    Thanks,

         Alexandra

  • Hi Alexandra,

    Yes I looked at the logs and its the same problem as I suspected earlier.

    The git.ti.com is undergoing some maintainence, please try after one day.

    If you follow the procedure that I mentioned earlier, you should be able to solve the problem.

    Regards

    Karthik

  • Karthik,

    Thank you for your response. I'll try again tomorrow, when git.ti.com will be up again.


    Regards,

       Alexandra

  • Hi Karthik,

    I finally compiled GLSDK. When I run either of the test applications for encoding and decoding (dce_test and dce_enc_test), I get the following error:

    MmRpc_create: Error: open failed, name=/dev/rpmsg-dce


    Also, regarding IPC resource manager, i tried to run a test: MessageQApp but get the following error:

    Ipc_start: NameServer_setup() failed: -8

    ProcId must be less than 0

    Ipc_stop: MessageQ_destroy() failed: -8

    Is something that I am doing wrong?

    Thank you,

        Alexandra

  • Hi Alexandra,

    I have a few questions:

    1. Have you made any source code changes on top of the default GLSDK?

    2. Have you made any changes to the filesystem?

    There are few example applications that are suggestion in the SDG. Could you please try running them? Like viddec3test or gst. And also can you share the contents of the /lib/firmware directory on the target filesystem? The above problem happens when the firmware binaries are not in the respective place.

    Regards

    Karthik

  • Hi Karthik,

     I managed to compile GLSDK and now i can run dce_test but not dce_enc_test.

    When i try to run this

    ./dce_enc_test 1920 816 300 /mnt/share/bin/out2.yuv /mnt/share/bin/out2.h264 h264 baseline 10 tiler

    i get the output from the file attached. This error comes from VIDENC2_Control which returns -1.

    How can i active debug messages for Codec Engine? I know about the following page:

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

    and I tried to modify the String Global_getenv(String name) function to return  retVal = 3 for CE_DEBUG but it didn't work.

    Thank you very much,

    Alexandra