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: Inconsistent success while running visualization scripts

Part Number: IWR1642BOOST


I have an IWR1642BOOST board. I'm running the traffic visualization binary with the people counting visualization GUI which works successful, though only under certain circumstances:

  • I have to use the pre-built, stock binary. If I try to build the stock, based, binary with CCS, it does not work.
  • Whenever I'm done running the visualization, I have to press the rest button on the board to run it again. When re-running any visualization code, the board is sending empty packets on the DATA port

1. Is there a reason why building the stock code wouldn't produce the same results as the prebuilt binary?

2. Is there some command that should be send of the UART port to reset the board, or does it have to have the hardware button reset every time?

Thank you.

  • Hello

    For #1) Can you please list the SDK version, Tirex demo  revision that you are using while building.

    #2) Are you saying you have to  hit reset before applying a new configuration to the demo that is already running  and it inconvenient setupwise?

      For this one we do not have HW option to do a remote reset. You may want to use  a power toggle  and let the demo comeback up.

     From SW perspective  not allowing to reconfigure is not a hard constraint but one can work around that by redoing a graceful initialization of SW structures in the implementation.    Wanted to mention that so you know that it is not a device level requirement but an implementation artifact.

    Thank you,

    Vaibhav

  • Former Member
    0 Former Member in reply to Vaibhav Mahimkar

    1) You should double check the User's Guide and if you've downloaded the Software Requirements as noted when building the lab. Common issues is not having the compiler version specified in the lab. There is a warning note about this.