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.

IWR1642: Need device source code and GUI code for demo

Part Number: IWR1642
Other Parts Discussed in Thread: IWR6843,

I'm lacking of IWR6843 board, so I must use another IWR1642 board as a replacement. But I can't find any dss, mss source code of this device and its GUI visualizer in toolbox 4.2.1 and the newest toolbox doesn't have either. Please send me all those files.

Besides, does IWR1642 use the same SPI/I2C library as IWR6843? Which part are they different?

  • Dear Hector:

    To access the Out of Box project files for the IWR1642 device use the following path:

    <Industrial_Toolbox Install Path>\labs\out_of_box_demo\16xx_mmwave_sdk

    Located at this location most importantly is the user guide to run the demo. I would suggest going fully through the user's guide. Specifically with the guide if you follow the instructions in the "Developer's Guide" that utilizes the CCS IDE you will be able to see the DSS/MSS source code.

    Note: Can you elaborate as to why you are lacking a IWR6843 board, or why you have not access to one. We may be able to assist.

    Let me know how it goes!

    Best regards,

    Connor Desmond

  • Hi Connor,

    I'm testing SPI read/write and need to demo it to customers. The idea is to SPI_write from IWR6843 Slave, then read on IWR6843 Master, store data in a buffer and use UART_write to demo on TI GUI. But my colleague is using another 6843, so I only have 1 board, can't implement my idea.

  • Dear Hector:

    1. You have to make sure that the #inlcude path is setup to see for example: #include <ti/drivers/uart/UART.h>

    2. You have to make sure that the following ARM Linker Path is set up properly e.g.:

    3. Both of these can checked in the CCS Project Properties:

    If the project is setup properly the API for a particular driver such as I2C or SPI will be the same across devices. The only thing that is different is in the ARM Linker Setup where in the uart/lib folder for example you will see device specific files for mss and dss.

    Best regards,

    Connor Desmond

  • In the user's guide page 10, step 2, neither the MSS nor DSS projects can be imported, instead I get a message "To look at the project source files, please import he project in CCS following the instructions provided in the user guide." I must be following the wrong user guide? I have tried the latest version of the industrial toolbox, V4.3.0, and V2.0.0. V2.0.0 allows me to load the project, but I get errors with paths not being valid.

  • Dear Clint:

    The following will allow you to import the MSS and DSS projects:

    Once you are in CCS right click in the Project Explorer: Import -> CCS Projects:

    Then use the following path:

    <Industrial Toolbox Install Path>\labs\out_of_box_demo\16xx_mmwave_sdk

    This should import both mss and dss projects into the CCS Project Explorer.

    Best regards,

    Connor Desmond

  • Thanks, that did indeed load the both projects.

    Now to get them running! Should I be getting errors when performing a build on those projects? Am I missing something?

    dss project errors

    Description Resource Path Location Type
    #141 too many arguments in function call dss_main.c /mmw_dss_16xx line 2251 C/C++ Problem
    #148 declaration is incompatible with "void MmwDemo_dataPathConfigBuffers(MmwDemo_DSS_DataPathObj *, uint32_t)" (declared at line 573 of "C:/ti/mmwave_sdk_02_00_00_04/packages/ti/demo/xwr16xx/mmw/dss/dss_data_path.h") dss_data_path.c /mmw_dss_16xx line 3857 C/C++ Problem
    gmake: *** [all] Error 2 mmw_dss_16xx C/C++ Problem
    gmake[1]: *** [dss_data_path.oe674] Error 1 mmw_dss_16xx C/C++ Problem
    gmake[1]: *** [dss_main.oe674] Error 1 mmw_dss_16xx C/C++ Problem
    gmake[1]: Target 'main-build' not remade because of errors. mmw_dss_16xx C/C++ Problem

    Warning
    <a href="file:/C:/ti/ccs1000/ccs/tools/compiler/dmed/HTML/225.html">#225-D</a> function "MmwDemo_dataPathConfigDcRangeMeanBuffers" declared implicitly dss_main.c /mmw_dss_16xx line 2241 C/C++ Problem

    mss project errors

    Description Resource Path Location Type
    #137 struct "CLI_Cfg_t" has no field "socHandle" cli.c /mmw_mss_16xx line 1231 C/C++ Problem
    #137 struct "MMWave_OpenCfg_t" has no field "customCalibrationEnableMask" mss_main.c /mmw_mss_16xx line 1648 C/C++ Problem
    #137 struct "MMWave_OpenCfg_t" has no field "useCustomCalibration" mss_main.c /mmw_mss_16xx line 1647 C/C++ Problem
    #141 too many arguments in function call mss_main.c /mmw_mss_16xx line 1660 C/C++ Problem
    gmake: *** [all] Error 2 mmw_mss_16xx C/C++ Problem
    gmake[1]: *** [cli.oer4f] Error 1 mmw_mss_16xx C/C++ Problem
    gmake[1]: *** [mss_main.oer4f] Error 1 mmw_mss_16xx C/C++ Problem
    gmake[1]: Target 'main-build' not remade because of errors. mmw_mss_16xx C/C++ Problem

    Thanks,

    Clint

  • Clint:

    Do you have a ES1.0 or ES2.0 silicon device?

    BR,

    Connor Desmond

  • Connor,

    I think I figured out my problem. It appears I built the mms project first. So I ended up having to delete both and re-import, then by compiling the dss first then the mss, I was able to get them both to compile. 

    With respect to the ES1.0 vs ES2.0, I just purchased the evaluation board, so I'm assuming ES2.0, however I can't find a label verifying that. From my research, if it doesn't explicitly state 2.0, then it is 1.0...

    I didn't see an option to specify 2.0 when ordering the evaluation board.

    Thanks,

    Clint Adams

  • Clint:

    If you ordered an EVM recently than it is most likely ES2.0. I am glad you were able to build both projects imported and built.

    Best regards,

    Connor Desmond