• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1176 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.

Original question:

CCS/AWR1642: How to import the xwr16xx_mmw_demo project?

CCS/AWR1642: problem with import xwr1642 demo to ccs

roy tech
Prodigy 30 points

Part Number: AWR1642

Tool/software: Code Composer Studio

Hi,

im using latest industrial toolbox with mmwave sdk 3.05 . i would like to import the awr1642 demo project to ccs but facing some problems.

See details below...
mmw_dss_16xx
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_mmw.cfg' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_mmw.h' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_config_edma_util.c' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_config_edma_util.h' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_data_path.c' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_data_path.h' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/utils/rx_ch_bias_measure.c' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_resources.h' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_lvds_stream.c' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/xwr16xx/mmw/dss/dss_lvds_stream.h' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/utils/mmwDemo_monitor.c' cannot be resolved!
Path 'COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/demo/utils/mmwDemo_monitor.h' cannot be resolved!

seems that the files in the sdk are not compatible!!

any ideas?

roy

  • 0
    TI__Guru**** 484311 points

    Hello,

    It appears that the COM_TI_MMWAVE_SDK_INSTALL_DIR linked resource path variable is invalid. Please check that it is set to a valid path.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 30 points

    Hello,

    the  path variable of COM_TI_MMWAVE_SDK_INSTALL_DIR is set correct to mmwave_sdk_03_05_00_04.

    the problem is thet some files in the sdk as wrong name (for ex: data_path.c instead of dss_data_path) and some are completely missing from the folder. it seems that the project is compatible to earlier sdk like 1.02 and not to latest sdk. could you check if you are able to import it using this SDK ??

    thanks,

    Roy

  • 0 in reply to roy tech
    TI__Guru**** 484311 points

    Yes I notice differences between SDK 3.05 and 1.02 where many of the mentioned files do not exist it the 3.05 version. It is very likely that the project is not compatible with the current version of the SDK. I will bring this thread to the attention of the device experts.

  • 0 in reply to Ki
    Prodigy 30 points

    hey Ki,

    I am still waiting to load the demo project to my new AWR1642BOOST evm. what about the competability problem? 

    Roy

  • 0 in reply to roy tech
    TI__Guru**** 484311 points

    This thread has been brought to the attention of the device experts. I will re-ping them.

  • 0 in reply to roy tech
    TI__Genius 15046 points

    Hi Roy,

    The mmWave SDK itself does not provide CCS projectspec files for the OOB demo. If you are using the files provided in the mmWave industrial toolbox, those are indeed outdated for SDK 3.5.

    We recently created projectspec files for the interference lab available in the mmWave platform toolbox. The interference lab is identical (with some additional functionality) to the OOB demo in SDK 3.5. 

    The folder structure for the interference lab is a little different from the OOB demo. If you want, you could refer to those projectspecs and try to modify them.

    If the CCS environment isn't a necessity, you could use the makefiles provided with the SDK to build the demo.

    Regards,

    Aayush