CCS/IWR1642: UART

Hi JianFeng,

Are you using a lab from the industrial toolbox for reference? The IWR1642 features two COM ports: a User UART port used for sending commands to the device and a Data Port used for receiving bit stream data from the device. For reference, here is the UART code from the Out of Box Demo.

    /* Setup the default UART Parameters */
    UART_Params_init(&uartParams);
    uartParams.clockFrequency = gMmwMssMCB.cfg.platformCfg.sysClockFrequency;
    uartParams.baudRate       = gMmwMssMCB.cfg.platformCfg.commandBaudRate;
    uartParams.isPinMuxDone   = 1;

    /* Open the UART Instance */
    gMmwMssMCB.commandUartHandle = UART_open(0, &uartParams);
    if (gMmwMssMCB.commandUartHandle == NULL)
    {
        MmwDemo_debugAssert (0);
        return;
    }

    /* Setup the default UART Parameters */
    UART_Params_init(&uartParams);
    uartParams.writeDataMode = UART_DATA_BINARY;
    uartParams.readDataMode = UART_DATA_BINARY;
    uartParams.clockFrequency = gMmwMssMCB.cfg.platformCfg.sysClockFrequency;
    uartParams.baudRate       = gMmwMssMCB.cfg.platformCfg.loggingBaudRate;
    uartParams.isPinMuxDone   = 1U;

    /* Open the Logging UART Instance: */
    gMmwMssMCB.loggingUartHandle = UART_open(1, &uartParams);
    if (gMmwMssMCB.loggingUartHandle == NULL)
    {
        System_printf("Error: Unable to open the Logging UART Instance\n");
        MmwDemo_debugAssert (0);
        return;
    }

Notice that there is a commandUartHandle and a loggingUartHandle. In reference to the receive function, here is reference code derived from the Gesture Recognition lab.

uint8_t                 cmdString[256];
memset ((void *)&cmdString[0], 0, sizeof(cmdString));
UART_read (gCLI.cfg.cliUartHandle, &cmdString[0], (sizeof(cmdString) - 1));

Please reference the Out of Box demo from the industrial toolbox if you wish to implement the UART_writePolling() function.

Regards,

Peter

Hi JianFeng,

Can I ask why you would only want to use a single COM port? Using the sensor requires two COM ports, one to send the configuration information to the sensor and one to receive the stream data. An alternative approach would be to hardcode the chirp configuration onto the device so that it is able to start streaming data on bootup. This method only requires a single COM port to receive the stream data after the image binary has been flashed on the device.

Information and steps on how to do this can be found in the mmWave doxygen. Additionally, we are releasing a new OOB demo for the IWR6843 in the next TIREX update that utilizes this hardcoded configuration method. Once that is available within the next 2 weeks, you could use the example code and take the same approach to bypass the CLI and hardcode the configuration onto your IWR 1642 device. If you have any further questions, do not hesitate to ask.

Regards,

Peter