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.

HDVPSS build error

Other Parts Discussed in Thread: SYSBIOS

Hi,

 

I'm trying to rebuild all hdvpss. I did a gmake OS=linux -s all command.

 

But I have this error log:

 

 

# /secondHDD/ITX/hdvpss_01_00_01_26_i2c_disable/build/hdvpss_examples_m2mNsf_Subframe/bin/ti816x-evm/hdvpss_examples_m2mNsf_Subframe_m3vpss_whole_program_debug.xem3 created.

#

# Invoking configuro...

making package.mak (because of package.bld) ...

generating interfaces for package ti816x_hdvpss_configuro (because package/package.xdc.inc is older than package.xdc) ...

configuring proxyServerHost_ti816x.pem3 from package/cfg/proxyServerHost_ti816x_pem3.cfg ...

js: "/secondHDD/mn_ezsdk_5_0_0_11.vs2working/syslink_02_00_00_67/ti/syslink/ipc/rtos/package.xs", line 96: Error: Library not found: ti.syslink.ipc.rtos.aem3

gmake: *** [package/cfg/proxyServerHost_ti816x_pem3.xdl] Error 1

gmake: *** Deleting file `package/cfg/proxyServerHost_ti816x_pem3.xdl'

gmake: *** [package/cfg/proxyServerHost_ti816x_pem3.xdl] Deleting file `package/cfg/proxyServerHost_ti816x_pem3.h'

gmake: *** [package/cfg/proxyServerHost_ti816x_pem3.xdl] Deleting file `package/cfg/proxyServerHost_ti816x_pem3.c'

js: "/secondHDD/mn_ezsdk_5_0_0_11.vs2working/xdctools_3_20_07_86/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.

gmake[1]: *** [xdc_configuro] Error 1

gmake: *** [proxy] Error 2

What does it mean this error log?
I'm not able to understand where the issue could be.
Is there anyone that could suggest me a way to solve this error?
Thanks

 

  • Hi,

    Can you please check your Rules.make under HDVPSS package. We are not planning to packaged HDVPSS source code from next release with ezsdk software.

     

    Regards,

    Hardik Shah

  • This is my rules.make.

     

    Try to take a look to it,please.

     

      CODEGEN_PATH_M3 := /secondHDD/mn_ezsdk_5_0_0_11.vs2working/cgt470_4_6_4

      hdvpss_PATH := /secondHDD/ITX/$(hdvpss_RELPATH)

      bios_PATH := /secondHDD/mn_ezsdk_5_0_0_11.vs2working/sysbios_6_31_04_27

      xdc_PATH := /secondHDD/mn_ezsdk_5_0_0_11.vs2working/xdctools_3_20_07_86

      syslink_PATH := /secondHDD/mn_ezsdk_5_0_0_11.vs2working/syslink_02_00_00_67

      ipc_PATH := /secondHDD/mn_ezsdk_5_0_0_11.vs2working/ipc_1_22_03_23

     

    Is there any wrong path. Have I build something before starting building HDVPSS?

     

    So from next release HDVPSS package wil disappear?

     

    Thanks for your help!

     

  • Hi,

    I am not sure about the build mechanism from EZSDK. Can you please go to HDVPSS Rel folder and there will be rules.make and modify that and try compiling.

    Yes, HDVPSS source code will be removed as it is covered under NDA. Binaries may still remain.

     

    Regards,

    Hardik Shah

  • Yes, I modified several times my Rules.make file. That's why I posted it here in the last post, because I can't find anything wrong apparently in it. 

    Do you see something wrong in my paths posted here?

     

    So, for the future: if I have to support something different from TVP (for example a TechWell), what can I handle this if HDVPSS will disappear?

     

    Regards,

    Dario

  • Hi,

    Sorry for you not being able to compile HDVPSS with ezsdk. I will ask local EZSDK person to guide you through this.

    Regarding your second question,

    We are planning to move all the encoder/decoder support to Linux A8 stack. So it will be easy to support new encoders/decoders other than what is supported on EVM. This is scheduled in Q4'11

    Regards,

    Hardik Shah

  • Hi,

    Sorry fot the confusion, HDVPSS source will be packaged with SDK releases and wont be pacakged with EZSDK releases. So if you are using SDK you will keep on getting HDVPSS source.

     

    Regards,

    Hardik Shah

  • So, if we are limited to the EZSDK, how can we reconfigure the VIP for the correct mode?

     

    Is the SDK only for special customers?

     

    -Herb

  • Hi,

     

    VIP works in detection mode, so does need to configure mode in it. The only thing required to configure is interface.

     

    Thx,

    Brijesh Jadav

  • That sounds like magic to me. How will it know what downscaling factor I want in the input port? How will it detect what interleave format I'm using if I'm multiplexing in multiple inputs?

  • Hi,

     

    This is true only when the input is directly stored in the memory without any processing modules are used in the pipeline. Of coarse, you will require to configure down scaling factor if you are using scalar in the pipeline. By interface, i mean embedded sync, discrete sync, YC mux, 16 bit, 24 bit modes, which is required to be configured in the VIP.

     

    Thx,

    Brijesh Jadav