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: CLI is producing garbage values at Serial Port

Part Number: IWR1642BOOST

Hi,

I have done manual modification in CLI.c file as guided in 

e2e.ti.com/.../653296

and it is working.

But I am getting garbage values at the serial port. I have selected 115200 and tested with other numbers too but no luck. It seems it is sending encoded values and serial port is not able to decode. Anybody help me to understand this?

  • Update:
    Logging baud rate is 921600 so changed to it. I think it is decoded message and I need to decode in char formate if I want to see in human readable format.
    Any suggestions, how to do it?
  • Hi Laxmi,

    This definitely shouldn't be happening. Would you mind posting what kind of changes you have made to the CLI.c file? We'll need more information in order to assist you.

    Cheers,
    Akash
  • Hi,
    Got it working. Silly mistakes. My bad. Thanks Akash for getting back to me.
  • Hi Akash,

    There is a correction in my previous answer. Yes, it is working but only for a char array. That means if I send an array of char, it prints exactly same that means there is nothing to do with cli.c file. I had sent an array of char

    char data[6] = {'H', 'E', 'L', 'L', 'O', '!'};

    and it prints perfectly. But when I tried to send

    uint8_t header_magic_number[8] = {0x02, 0x01, 0x04, 0x03, 0x06, 0x05, 0x08, 0x07};

    It printed garbage. I used UART_writePolling(). I am not sure what is wrong here. Am I doing something wrong while sending this byte array data or it is being sent right but displaying wrong because of wrong ASCII decode?

    I have used debug window to print values on CCS debug console window using System_printf('%x', [i]) and it printed right numbers so the array is right here.

  • Hi Laxmi,

    Would you mind posting your modded CLI .c-file? Have you tried using the standard CLI file?


    Cheers,
    Akash