• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 1078 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.

CCS/TMS320DM648: How is linkcmd.xdt run & passed args?

kenneth Macfarlane
Intellectual 775 points

Part Number: TMS320DM648

Tool/software: Code Composer Studio

I'm trying to get the dm6437_demo to link - I've got it to compile by adding some include paths.

C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\linker.cmd is the problem, yet its generated – so what’s the source linkcmd.xdt? I can't find where its referenced in the build options/ linker tab i.e. how do I amend the paths?

Thanks for your time!

Ken

  • 0
    TI__Guru* 96960 points
    I've moved this to the device forum. There are more familiar with their examples.
  • 0 in reply to ToddMullanix
    Intellectual 775 points
    the linker command (cut from edit window) & made a bit more readable is:

    -c -m".\Debug\dm6437_demomap" -o".\Debug\dm6437_demo.out" -w -x
    -i"%BIOS_INSTALL_DIR%/packages/ti/rtdx/lib/c6000"

    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\hal\evmdm6437\hal_eth_dm64lc.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\hal\hal_ser_stub.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\hal\hal_timer_bios.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\hal\hal_userled_stub.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\miniPrintf.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\netctrl.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\nettool.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\os.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval\packages\ti\ndk\lib\c64plus\stack.lib"

    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\edma3\lib\Debug\edma3_drv_bios.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\edma3\lib\Debug\edma3_drv_sample.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\edma3\lib\Debug\edma3_rm_bios.lib"

    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\audio_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\i2c_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\mcasp_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\mcbsp_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\palos_bios.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\prev_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\rsz_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\video_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\vpbe_bios_drv.lib"
    -l"%BIOSDVSDK_INSTALL_DIR%\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug\vpfe_bios_drv.lib"

    -l"%BSL_EVMDM6437_INSTALLDIR%\lib\evmdm6437bsl.lib"
  • 0 in reply to ToddMullanix
    Intellectual 775 points
    I'm not sure if this is being posted onto the end of the original message, or whether I am now in the device forum..


    However, I don't think that this is a device issue - I think its due to not being able to find a explanation of the linker include paths c/w the the libraries.

    This linker error looks to me like the linker is being passed absolute file paths via linker.cmd, but I can't find out how to edit the source that autogen's linker.cmd:

    >> C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\xdcconfig\\linker.cmd, line 32: error:
    can't find input file
    'C:\dvsdk_1_01_00_10\biosutils_1_00_02\packages\ti\bios\log\support\lib\logsupport.a64P'

    The string in the Incl's field is 2400 characters long due to including the paths the libs over & over again - surely the linker libraries search path field should be used to handle that? But is this not a reference example, written by TI? Surely it shouldn't have absolute paths in it?