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.

compilation failure vision_sdk

Hi,

I am trying to compile de example "bsp_examples_uart" in the vision_sdk of texas instruments and I get always a linking error.

Firstly I compile the vision_sdk through make and the on the folder "bsp_01_04_00_08" I run "make PLATFORM=tda3xx-evm bsp_examples_uart" and I get the following error.

That happens to me only with the uart example cause I ran the i2cUtility and it gave me no problems...could anyone please help me? Does anybody know how to solve this so I can run the uart example?

Would this example be the indicated one it I want to read and write through serial port? I would need to implement the same use as "bsp_examples_i2cUtility" but not through JTAG but through USB-cable...is there an available example for it?

Thank you very much in advance!

Javier

../../ti_components/drivers/bsp_01_04_00_08/binary/ti/sdo/edma3/rm/sample/lib/tda3xx-evm/m4/release/edma3_lld_rm_sample.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/uart/lib/tda3xx-evm/m4/release/bsp_uart.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/common/lib/tda3xx-evm/m4/release/bsp_common.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/osal/lib/tda3xx-evm/m4/release/bsp_osal.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/platforms/lib/tda3xx-evm/m4/release/bsp_platforms.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/boards/lib/tda3xx-evm/m4/release/bsp_boards.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/devices/lib/tda3xx-evm/m4/release/bsp_devices.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/fvid2/lib/tda3xx-evm/m4/release/bsp_fvid2.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/src/i2c/lib/tda3xx-evm/m4/release/bsp_i2c.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/binary/examples/utility/lib/tda3xx-evm/m4/release/bsp_examples_utility.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/cg_tools/linux/ti-cgt-arm_5.2.5/lib/libc.a -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/src/devices/ov10640/lib/ov10640_lib_ipu1_0_release.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/../../../vision_bios_examples/tda2xx/src/common/prof_log/lib/prof_log_ipu1_0_release.aem4 -l/home/javier/Escritorio/tda_integration_1108/tda3/ti_components/drivers/bsp_01_04_00_08/../../../ti_components/drivers/bsp_01_04_00_08/../../../vision_sdk/binaries/lib/tda3xx-evm/ipu1_0/release/vision_sdk_lib.aem4


error: symbol "edma3init" has already been defined
error: symbol "determineProcId" has already been defined
error: symbol "edma3deinit" has already been defined
error: symbol "edma3OsSemTake" has already been defined
error: symbol "edma3OsSemGive" has already been defined
error: symbol "edma3OsProtectEntry" has already been defined
error: symbol "edma3OsProtectExit" has already been defined

>> Compilation failure

>> Compilation failure
fatal error: Failed linktime optimization

  • We have moved your post to the appropriate forum.
  • HI Javier,

    Your question has been forwarded to Vision SDK experts.

    Best regards
    Lucy
  • Javier,

    Can you edit the "Rules.make" file in BSP folder for all the tool path and do make from the BSP folder itself?

    I think the issue is "ROOTDIR" environmental variable is pointing to VSDK instead of BSP. This happens because bsp_PATH is already defined by VSDK hence the ifeq check at the top of Rules.make file in BSP is skipped. This forces the make to pick-up the EDMA library from VSDK library folder.

    Can you try this and let me know?

    We are discussing internally to see on how to fix this cleanly.

    Regards,

    Sivaraj R

  • Hi,

    thanks for your answer.

    I have modified the Rules.make in bsp by asigning the variable "bsp_PATH" directly to my path to bsp, is that the change you were suggesting? if not, could you specify please how should I edit "Rules.make"?

    After I did that, I made "make" in the folder "bsp" and it ran fine. But when I tried to compile the "bsp_examples_uart"  I got the same error

    error: symbol "edma3init" has already been defined

    error: symbol "determineProcId" has already been defined

    error: symbol "edma3deinit" has already been defined

    error: symbol "edma3OsSemTake" has already been defined

    error: symbol "edma3OsSemGive" has already been defined

    error: symbol "edma3OsProtectEntry" has already been defined

    error: symbol "edma3OsProtectExit" has already been defined

    error: symbol "edma3init" has already been definederror: symbol "determineProcId" has already been definederror: symbol "edma3deinit" has already been definederror: symbol "edma3OsSemTake" has already been definederror: symbol "edma3OsSemGive" has already been definederror: symbol "edma3OsProtectEntry" has already been definederror: symbol "edma3OsProtectExit" has already been defined

  • Can you share the entire build log without -s option?

    Need to see what all libraries are getting picked-up.

    Regards,

    Sivaraj R

  • Hi Javier, 

    Is this issue resolved? if not, can you please share the log as Sivaraj suggested?

    Rgds,

    Brijesh

  • Hi,

    We have finally discovered the problem. The variable "bsp_path" in the makefile was pointing the vision_sdk instead of the bsp and also we had one library that was being compiled but not linked.

    It works fine now

    Thank you very much for the help

    Javier