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.

IWR1642BOOST: ppl lab,How to let program enter CLI_task() of cli.c in SDK

Part Number: IWR1642BOOST

I want to receive .cfg file through CANFD to start radar.The reception of CANFD is tested and can be used normally

I found cli.c in SDK and mss_main.c seems to run separately.I added System_printf() to both files.Only when mmwave demo visualizer sends cfg file,System_printf() in CLI_task() of cli.c in SDK is displayed.For the rest of time, only System_printf() in mss_main.c is displayed.

I tried to change cliCfg.cliUartHandle = gMmwMssMCB.commandUartHandle to cliCfg.cliUartHandle  = canHandle and change the data type.Then I configure CANFD_createMsgObject() in CLI_task() of cli.c in SDK.I tried to start the radar with CANFD, but it didn't work

How does the program enter the CLI_task() of cli.c in SDK? Serial port interrupt or something else?

Where can I make changes to replace UART_read() with CANFD?

Thank you

  • Hello,

    I am looking into your issue. I will get back with a some information tomorrow.

    Best regards,

    Connor Desmond

  • Hello,

    I would suggest going to the following resources:

    1. TI RTOS User's Guide: www.ti.com/.../spruhd4m.pdf

    2. Main OOB Documentation - Shows how the CLI_task() is created. Remember this is not a function, but a Task. Refer to resource 1 for more info.

    <MMWAVE_SDK_INSTALL_PATH>/docs/mmwave_sdk_module_documentation.html - under demos. e.g.16xx

    3. UART Driver Documentation - <MMWAVE_SDK_INSTALL_PATH>/docs/mmwave_sdk_module_documentation.html - under drivers.

    4. CAN Driver Documentation - <MMWAVE_SDK_INSTALL_PATH>/docs/mmwave_sdk_module_documentation.html - under drivers.

    I would highly suggesting understanding the driver API for UART ( default config protocol) , the driver API for CANFD, and the CLI_task() which indirectly calls those APIs.

    Here is a snippet from resource 1. Here it shows the MmwDemo_mmsInitTask be called by main.c on the R4F. That task then creates the CLI task. The CLI task then forever, or until power is cycled, will check the UART for data e.g. commands, among other things. These commands will then configure the device. Upon successful configuration the UART will write "Done" back to the host.

    Best regards,

    Connor Desmond