• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 567 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR6843ISK-ODS: 3D People Counting Baud Rate modification

Bing Chen1
Intellectual 290 points
Part Number: IWR6843ISK-ODS

Hello,

I would like to change to ES 2.0 ISK-ODS 3D demo lab data logging rate to 2000000. The default rate of 1843200 is not standard for the Linux support library.

Directly changing the rate to 2000000 would cause minor bit-flip issues and packet drop. Could you tell me if there are other places or stack sizes I need to change to support a 2000000 rate?

Thanks,

Bing

  • 0
    TI__Mastermind 28055 points

    Hi Bing,

    You will need to change the logging baud rate in the MSS project - find it in mss_main.c. Otherwise, you would also need to change the baudrate of the software capturing the UART from the device. Please see the uart driver documentation in the SDK for more.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Intellectual 290 points

    Hi Justin,

    Thanks for the reply. I did change the logging baud in MSS to 2000000 and rebuilt the project binary. The issues mentioned above would occur. It looks like every frame is being sent out (frame header present) except the packets would be completed. It looks like the firmware simply lets go the buffered frame data at some point and moves on to send out the next frame.

    The other issue mentioned was that sync word would get a bit flip and becomes 0201 0403 0605 1807.

    Are there any memory elements I should increase in MSS?

    Thanks,
    Bing

  • 0 in reply to Bing Chen1
    TI__Mastermind 28055 points

    Hi Bing,

    Since you are seeing a bit flip in the magic word, you may be getting bit flips in the rest of the data, making it seem like the transmissions are incomplete. See the UART driver API and try adding parity bits to ensure correctness.

    Regards,

    Justin