• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 677 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: People Counting Demo Parser

Hank Tsou
Prodigy 110 points
Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843, IWR1642, , MMWAVEICBOOST

Hi,

I have been working on iwr1642 and iwr6843 and using my own python parser for people counting demo. It was working perfectly fine without any error on iwr1642 board. Recently, I ran the lab15 people counting demo on iwr6843ISK. It frequently appears invalid TLV type parsing result. In general, it still works but frames which have invalid TLV type are missing since parser is unable to parse the reset of data.

My question is if there are any changes from iwr1642 to iwr6843 in terms of data structure format. I referred this document for data structure format. It's the same as iwr1642.

http://dev.ti.com/tirex/explore/node?node=ANoGbRd1GQzjC9YA7IUpPQ__VLyFKFf__LATEST&r=VLyFKFf__3.6.2

Thanks,

Hank

  • 0
    TI__Mastermind 28055 points

    Hi Yi-Hao,

    The output data is the same between 1642 and 6843. You can check task_mbox.c in the mss folder of the lab to get a better understanding of output data.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 110 points

    Hi Justin,

    Thank you for clarifying. I tested a bit today and found out it might be UART problem since I was using 40 pin LP/BP on MMWAVEICBOOST connecting to my Pi board. I have checked the voltage on  MSS_Logger pin to Rpi Rx was 3.3V and baudrate was set to 921600. However, when I used parser to parsing the data, it frequently showed that checksum error. On the other hand, using USB connection didn't show any checksum error. Eventually, I need to use UART interface instead of USB.

    Do you have any idea how this happened?

    Thanks,

    Hank

  • 0 in reply to Hank Tsou
    TI__Mastermind 28055 points

    Hi Hank,

    Did you write your own parser to work with the RPi? Please double check the code and make sure there isn't anything causing the occasional error.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 110 points

    Hi Justin,

    I have tested my parser on iwr1642 and iwr6843 with UBS. It didn't show up any checksum error so I assumed my parser was working. This morning, I found out that Rpi's mini UART clock highly depends on CPU load. That might occasionally cause byte transmission error which results to checksum error. I have switched from mini UART to PL011 UART which was more stable and I rarely seen the checksum error.

    Thank you for your answer,

    Hank