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.

  • Resolved

CCS/IWR1642BOOST: Standalone using traffic monitoring

Expert 1890 points

Replies: 15

Views: 330

This is my 3857.cli.c

file for traffic monitoring. I replace this file with C:\ti\mmwave_sdk_02_00_00_04\packages\ti\utils\cli\src\cli.c. Then i rebuild dss and mss part of traffic monitoring in ccs. Though i am not able to make IWR1642BOOST standalone.

  • Hello Arpit,

    Are you able to follow the example to build the standalone 16xx out of box demo successfully? 

    Amanda

  • In reply to AmandaN:

    Hi Amanda,

                 I am able to make mmwavw sdk demo code to work standalone successfully. I have used that working cli.c file which has been provided by you to Attiya Mahmood that i have modified as per my requirement and un the end it works well. Even For traffic monitoring, I have used both the config file mmw_tm_demo_ph2.cfg and mmw_tm_demo_longRange.cfg to make it so but i am not able to make it work as standalone. Above i have attached only cli.c file for long-range.   

  • In reply to Arpit Patel:

    Hello Arpit,

    Can you describe what the issues you are seeing when you say it isn't working? What happens? 

    Are you able to successfully rebuild the normal TM demo code? Have you double checked that you are using the correct DSP compiler version?

    Amanda

  • Hi Amanda,
          My demo code is working absolutely fine.I am able to rebuild it code successfull.There is no error in any steps. I have already checked all the things which i need to make it standalone. Is my cli.c file is ok? If not then guide me. And i am using ti-cgt-c6000_8.1.3 compile version. If i need to change anything then let me know.

    # TI DSP compiler
    export C674_CODEGEN_INSTALL_PATH = $(MMWAVE_SDK_TOOLS_INSTALL_PATH)/ti-cgt-c6000_8.1.3
    # DSPlib
    export C64Px_DSPLIB_INSTALL_PATH = $(MMWAVE_SDK_TOOLS_INSTALL_PATH)/dsplib_c64Px_3_4_0_0
    # DSPlib C674
    export C674x_DSPLIB_INSTALL_PATH = $(MMWAVE_SDK_TOOLS_INSTALL_PATH)/dsplib_c674x_3_4_0_0
    # MATHlib
    export C674x_MATHLIB_INSTALL_PATH = $(MMWAVE_SDK_TOOLS_INSTALL_PATH)/mathlib_c674x_3_1_2_1

  • In reply to Arpit Patel:

    Hello Arpit,

    There should not be an issue if you were following the directions in the original e2e thread. https://e2e.ti.com/support/sensors/f/1023/p/708175/2616079#2616079

    I tried to replicate the issue and was not able to. I've captured my steps below:

    1. Downloaded mmWave SDK 2.0.0.4 

    2. Create a new cli.c file for hard coded TM config. Attached here. Replaced the original cli.c file in the CLI folder in the SDK

    3. Go to setenv.bat in mmWave SDK change to iwr1642. Run .bat file.

    4. Change director to CLI folder and run gmake clean, gmake build commands

    5. Open up CCS, import 16xx Traffic Monitoring labs build DSS and MSS projects as usual.

    6. Flash the EVM with the .bin from the MSS Debug folder.

    7. Open up Tera Term for CFG port (set baud rate to 115200) hit "Enter" key. Should see mmwDemo:/> come up. This means the demo is booting up/hasn't crashed.

    8. Open up Tera Term for Data serial port (set baud rate to 921600). See data streaming.

    Please follow the steps as specified. I would recommend that you redownload the SDK and the Industrial Toolbox to ensure that the issue isn't related to any source modifications on your local machine.

    Amanda

     7701.cli.c

  • In reply to AmandaN:

    Hi Amanda,

               Thanks for the reply. There was an only problem with cli.c file. I tried to update the cli.c file with long-range config file parameter in many ways but it is not working. Would you help me with this?  because i am trying this for long-range.

  • In reply to Arpit Patel:

    Hello Arpit,

    The original thread as well as my reply has verified that if the steps are followed the hard coded config should not be a problem. Please provide me details of the steps you followed and your debugging to better understand the issue.

    Amanda

  • In reply to AmandaN:

    Hi Amanda,

                   I apologize for not mention my issue properly. I have already clarified that previously i followed these same steps but there was the only problem with cli.c file that i have mentioned in the above reply also. So there is nothing wrong with the steps. With following same steps and using provided cli.c file i am able to make board standalone successfully. It means there was only a problem with my cli.c file. Now i want to use it for a long-range so for that i have to update my cli.c file with my long-range parameter but when i did that with using same steps which you have mentioned above it is not working. So guide me how do i arrange my long-range parameter in cli.c file so that i can make board standalone successfully.

  • In reply to Arpit Patel:

    Hello Arpit,

    You should be taking the verified known working long range cfg provided in the Industrial Toolbox and replacing the existing commands in the provided cli.c with the ones from the cfg file. Make sure to enclose it in quotes as needed. All other commands in the cli.c file can stay.

    To understand the changes you can diff the cli.c file I provided with the ph2.cfg from the Toolbox. You should make the same changes for the long range cfg.

    Amanda

  • In reply to AmandaN:

    Hi Amanda,

              I have done the same procedure with cli.c file using long-range config file of traffic monitor. I am using industrial toolbox version 3.6.1. Here is its mmw_tm_demo_longRange.cfg file. First, i have taken all the parameter as it is with enclosed in quotes in cli.c file. Then i compare cli.c file provided by you and cli.c file that i have made. First when i use my cli.c file but as it was not working i make some changes as per cli.c file given by you in many ways (adding some parameters which were not in the long-range config file). Though it was not working. If you could see my long-range config file and compare it with with the long-range config file which you have and if both are different or if you could identify some missing parameter in my given file and making it proper file which i can use in my cli.c file and load it successfully without any issue like the proper cli.c file which you have provided which work succefully.  

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.