• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 492 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

link error when I build DSP server in windows

yun shen
Prodigy 220 points
Other Parts Discussed in Thread: CCSTUDIO

I use bios_5_31_02, codec_engine_2_24_01, dsplink_1_63, xdctools_3_15_00_50, xdais_6_24
to compile DSP server in windows, but when I use "xdc release -PR ." to create X64P file,
I get link error messages,

C:\CCStudio_v3.3\codec_engine_2_24_01\packages\ti\sdo\ce\VIDENCCOPY_server>xdc r
elease -PR .
making release: Tue Sep 1 13:28:32 2009 ...
======== .interfaces [.] ========
making package.mak (because of package.bld) ...
building for target C64P ...
generating interfaces for package ti.sdo.ce.VIDENCCOPY_server (because package/p
ackage.xdc.inc is older than package.xdc) ...
.interfaces files complete: Tue Sep 1 13:28:48 2009.
======== .libraries [.] ========
.libraries files complete: Tue Sep 1 13:28:49 2009.
======== .dlls [.] ========
.dlls files complete: Tue Sep 1 13:28:50 2009.
======== .executables [.] ========
configuring VIDENCCOPY_server.x64P from package/cfg/VIDENCCOPY_server_x64P.cfg .
..
platform   = ti.platforms.evmDM6446
Warning: ti.sdo.ce.VIDENCCOPY.ce.VIDENCCOPY did not supply a max DARAM scratch s
ize; assuming 0 bytes is sufficient.
Warning: ti.sdo.ce.VIDENCCOPY.ce.VIDENCCOPY did not supply a max SARAM scratch s
ize; assuming 0 bytes is sufficient.
ti.sdo.ce.ipc.bios.close(): loading dsplink.dsp

NOTE: You can find the complete server data sheet in ./package/info/VIDENCCOPY_s
erver.x64P.DataSheet.html
--------------------------------------------------------------------------------
-------------------------

Warning: incompatible use of package 'ti.bios' [in C:/CCStudio_v3.3/bios_5_31_02
/packages/ti/bios/]: version of the loaded package 'ti.bios' is [5, 2, 3, 14], w
hile 'ti.sdo.ce.bioslog' [in C:/CCStudio_v3.3/codec_engine_2_24_01/packages/ti/s
do/ce/bioslog/] was built with 'ti.bios' [5, 2, 5, 12], while 'ti.sdo.fc.dskt2'
[in C:/CCStudio_v3.3/codec_engine_2_24_01/cetools/packages/ti/sdo/fc/dskt2/] was
 built with 'ti.bios' [5, 2, 5, 12], while 'ti.sdo.fc.dman3' [in C:/CCStudio_v3.
3/codec_engine_2_24_01/cetools/packages/ti/sdo/fc/dman3/] was built with 'ti.bio
s' [5, 2, 5, 12], while 'ti.sdo.ce.ipc.bios' [in C:/CCStudio_v3.3/codec_engine_2
_24_01/packages/ti/sdo/ce/ipc/bios/] was built with 'ti.bios' [5, 2, 5, 12], whi
le 'ti.sdo.fc.acpy3' [in C:/CCStudio_v3.3/codec_engine_2_24_01/cetools/packages/
ti/sdo/fc/acpy3/] was built with 'ti.bios' [5, 2, 5, 12], while 'ti.sdo.fc.memut
ils' [in C:/CCStudio_v3.3/codec_engine_2_24_01/cetools/packages/ti/sdo/fc/memuti
ls/] was built with 'ti.bios' [5, 2, 5, 12], while 'ti.sdo.ce.osal.bios' [in C:/
CCStudio_v3.3/codec_engine_2_24_01/packages/ti/sdo/ce/osal/bios/] was built with
 'ti.bios' [5, 2, 5, 12], while 'ti.bios.utils' [in C:/CCStudio_v3.3/codec_engin
e_2_24_01/cetools/packages/ti/bios/utils/] was built with 'ti.bios' [5, 2, 5, 12
]
    will link with ti.sdo.ce.video:lib/release/video.a64P
    will link with ti.sdo.ce.bioslog:lib/release/bioslog.a64P
    will link with ti.sdo.ce:lib/release/ce.a64P
    will link with ti.sdo.ce.alg:lib/release/Algorithm_BIOS.a64P
    will link with ti.sdo.ce.ipc.bios:lib/release/ipc_bios.a64P
    will link with ti.sdo.ce.osal.bios:lib/osal_bios.a64P
    will link with ti.sdo.ce.osal.bios:lib/osal_bios_load.a64P
    will link with ti.bios.utils:lib/utils.a64P
    will link with ti.sdo.fc.acpy3:lib/release/acpy3.a64P
    will link with ti.sdo.fc.memutils:lib/release/memutils.a64P
    will link with ti.sdo.ce.utils.xdm:lib/release/XdmUtils.a64P
    will link with ti.sdo.ce.node:lib/release/node.a64P
    will link with ti.sdo.fc.dman3:lib/release/dman3Cfg.a64P
    will link with ti.sdo.fc.dskt2:lib/release/dskt2.a64P
    will link with ti.sdo.utils.trace:lib/release/gt.a64P
    will link with ti.sdo.ce.VIDENCCOPY:lib/videnc_copy_dma.a64P
cl64P main.c ...
cl64P package/cfg/VIDENCCOPY_server_x64P.c ...
cl64P package/cfg/VIDENCCOPY_server_x64Pcfg_c.c ...
asm64P package/cfg/VIDENCCOPY_server_x64Pcfg.s62 ...
lnk64P VIDENCCOPY_server.x64P ...

undefined                        first referenced
 symbol                              in file
---------                        ----------------
_HWI_D_inhwi                     C:\CCStudio_v3.3\codec_engine_2_24_01\packages\
ti\sdo\ce\osal\bios\lib\osal_bios.a64P
_SWI_D_inswi                     C:\CCStudio_v3.3\codec_engine_2_24_01\packages\
ti\sdo\ce\osal\bios\lib\osal_bios.a64P
_MEM_getBaseAddress              C:\CCStudio_v3.3\codec_engine_2_24_01\packages\
ti\sdo\ce\osal\bios\lib\osal_bios.a64P
>>   error: symbol referencing errors - 'VIDENCCOPY_server.x64P' not built
gmake[1]: *** [VIDENCCOPY_server.x64P] Error 1
xdctools_3_15_00_50\gmake.exe: *** [.,.executables] Error 2

which lib include HWI_D_inhwi, SWI_D_inswi and MEM_getBaseAddress? how to link the X64P
file correcttly? Thanks.

  • 0
    TI__Mastermind 24340 points

    Hi yun,

    Please update your bios version to later than 5.32 and see if the problem is solved.

  • 0 in reply to Mariana
    Prodigy 220 points

    When I update bios version to 5.33, the problem is solved. Thanks

  • 0 in reply to Mariana
    Prodigy 160 points

    Hello:

     

    I have a very similar, if not the same problem, when linking I have:

     

    [Linking...] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -@"iDebug.lkf"

>> warning: creating output section $build.attributes without SECTIONS
            specification

undefined                        first referenced
 symbol                              in file
---------                        ----------------
_HWI_D_inhwi                     C:\dvsdk_1_10_00_26_DM648\pspdrivers_1_10_03\packages\ti\sdo\pspdrivers\pal_os\bios\lib\dm648\Debug\palos_bios_i.lib
_SWI_D_inswi                     C:\dvsdk_1_10_00_26_DM648\pspdrivers_1_10_03\packages\ti\sdo\pspdrivers\pal_os\bios\lib\dm648\Debug\palos_bios_i.lib
_PSP_i2cTransfer                 C:\\project\\component\\lib\\Debug\\audio_bios_drv_i.lib
>>   error: symbol referencing errors -
            'C:/project/audio/build/../bin/Debug/audio_st_sample_1_to_1_i.out' not built


>> Compilation failure



    In my case, I'm using pspdrivers 1.10.3 for DM648, and DSP/BIOS 5.31.8 which is supposed to be supported for that pspdrivers, at least it's stated so in the pspdrivers datasheet.
    I don't have this error with pspdrivers 1.10.1

    What do you think I can do in this situation?