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.

IWR6843AOPEVM: Trying to run a lab gives the following specific error:

Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: UNIFLASH

The error is:

b'Error: You have provided partial configuration between stop and this command and partial configuration cannot be undone.Issue the full configuration and do "sensorStart" \n'

And then the following lines come out repeatedly:

Traceback (most recent call last):
   File "gui_threads.py", line 40, in run
      outputDict = self.parser.readAndParseUart()
   File "gui_parser.py", line 74, in readAndParseUart
      if (magicByte[0] == magicWord[index]):
IndexError: index out of range

I have succesfully connected the COM Ports, I am trying to run the 3D People Counting lab, I selected the Configuration from ti\mmwave_industrial_toolbox_4_12_0\labs\People_Counting\3D_People_Counting\chirp_configs\AOP_6m_default.cfg. I can get it to work I'd say 1/4 times, then it works for a minute until it tells me that it has lost access to the COM ports as UniFlash also has them open at the same time, the rest of the time I get the message displayed above.

EDIT: it is happening with all the Labs, I get the same IndexError, except for Long Range People Detection, that one works fine even without loading its meta image into UniFlash (Web Version).

  • Hello.

    Please make sure that nothing is occupying the data port of the device(for example, an open terminal with a serial connection to the data port).  In addition, could you provide your configuration that results in the partial configuration error message?

    Sincerely,

    Santosh

  • Hi,

    Nothing is occupying the port. The only other application open is UniFlash (which must be open in order for the labs to work right?). The configuration I am choosing is the AOP_6m_default.cfg from the 3D People Counting Lab.

    Even when I can get it to run, it eventually crashes after 1-2 minutes and starts displaying the same error message

    Thanks for the help,

    Nicolas

  • Hi Nicolas.

    Uniflash should not be required for the labs to run as it is just a flashing tool.  The error you are getting is a result of the sensor crashing, so let me look into this further and I will get back to you as soon as possible.

    Sincerely,

    Santosh

  • Hello Nicholas.

    Please try closing UniFlash and then running the lab again.  It is possible that UniFlash can occupy a COM port, which can cause the problems you are seeing.  Also please make sure you did not accidentally make any changes to the config file(extra space/enter) as that can cause issues with loading the config onto the device.

    Sincerely,

    Santosh

  • Ive done as you say and run the visualizer without uniflash or anything else open. It still gives me the same error after 10 minutes. The config file is as it was when I downloaded it

  • I am now getting an additional error, also occurring after -10 minutes runtime:

    Warning: invalid TLV type: 262144
    Error in gui_main.py: number of points in last frame does not match number of track indexes
    Warning: invalid TLV type: 168430090
    TLV Header Parsing Failure
    Warning: invalid TLV type: 168430090
    Parsing Error on frame: 6689
    Error Number: 2

  • Hello.

    The first error may be caused because you may not be resetting the device after closing the visualizer and then trying to start the device again.  But primarily these two errors, mostly the second, happens when the GUI can't keep up with the data coming out of the device.  This doesn't necessarily mean that the device is failing; you can check this by opening a TeraTerm window and check if anything is coming out of the output COM port.  If you want to parse the data you can save the data stream to a file and parse the TLV's from the UART stream to get the information you need.

    Sincerely,

    Santosh

  • Thanks for the reply Santosh, I am pretty sure that the problem is as you said: that the GUI cannot keep up with the data coming out of the device. Is there any recommended fix for this?

  • Hi,

    There are a couple things you can potentially try to help the GUI to run faster, but as a reminder, this is just a tool to help expedite evaluation so its performance robustness is not guaranteed across all computers.

    Some things to check:

    • If you are running the GUI from the .exe, you may see improved performance running the python source files instead
    • If you are on a laptop, be sure to have a charging cable attached, and the power mode set to Best Performance to ensure that it does not throttle you.
    • Set the task to a higher priority in task manager

    Best Regards,
    Alec

  • Thanks Alec, I will try those things out