• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 664 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: Sometimes Getting Continuous Exception in parsing the TLVheader

Shraddha Swami
Intellectual 370 points
Part Number: IWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST,

Hi TI Team, 

We are using Area scanner zone application on IWR6843ISK + MMWAVEICBOOST. We are getting pointcloud and SNR etc information in the TLV's received from device. Sometimes we are observing exception in parsing the TLV header for few frames, so that frame is getting missed. But it has been observed , that exception is being received frequently and lot of frames(Data) are missing. 

Currently in configuration frame period is 100ms (10 frames per second)

eg. Getting this print from parsing application we wrote with reference to oob_parser.py from visualiser codebase from SDK.

Exeption  at tlvHeader unpack requires a bytes object of length 8  

print('read fail: not enough data') 

Exception in parseStaticDetectedObj unpack requires a bytes object of length 16
failed to get pointcloud

I tried to reproduce the issue but could not find exact scenario. 

1. May i learn what is the root cause of getting exception for receiving data?

2. Is it because of wrong TLV's received from RADAR ?

3. Which factor is causing this issue frequently ?

4. How we can resolve it?

5. Do we need to change anything in config file?

Please clarify my queries. 

Thanks

Shraddha

  • 0
    TI__Mastermind 23725 points

    Hello

    Are you trying to  run the Area scanner code   on the device while running the SDK's visualizer?

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Intellectual 370 points

    Hi Vaibhav,

    No, We are not running SDK's Visualiser. We just took reference of that for writing data parsing application.

    We are running python application on host PC(linux)  which will send the area_scanner_ISK.cfg  configuration to device, receive the TLV data from Radar and parse the respective TLV's. 

    sometimes this error is observed while parsing the received TLV data.

    Thanks

    Shraddha

  • 0 in reply to Shraddha Swami
    TI__Mastermind 23725 points

    Hello

    A few things to check:

    1. Please see if the XDS110 firmward change applies to the issue you are seeing. Mention here https://dev.ti.com/tirex/explore/node?node=AF4jhFuBH13mLPnsCXgawg__VLyFKFf__LATEST

    2. Is the demo + cfg send working well on TI's gui, or do you see such errors there as well.

    3. When the error occurs do you see the TLV being inconsistent with TLV description in the USer's guide.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Intellectual 370 points

    Hi Vaibhav, 

    1. I checked in area scanner zone application overview on  https://dev.ti.com/tirex/explore/node?node=AD6F02XtKZMeXTYUwLQKMw__VLyFKFf__LATEST , there i could not see the similar prerequisite. 

    2. We were able to run the demo using TI's gui previously.

    3. I think that might be the case, because the application is failing in parsing the TLV header which gives type and length of the TLV.

    We are getting exception in parsing that TLV.

    Please find the below logs from our application which shows invalid TLV type at the time of exception.

    But sometimes exception observed for valid TLV type as well, as in below logs TLV tye = 1 is valid TLV for area scanner application.

    TLV type: 2898140284
    Exeption at tlvHeaderDecode unpack requires a bytes object of length 8
    read fail: not enough data

    Exception in Data parsing: unpack requires a bytes object of length 40

    Not enough data
    Data length: 62
    Reported Packet Length: 1824
    Exception in parseDynamicPoints unpack requires a bytes object of length 16
    failed to get point cloud
    TLV type: 1
    Exeption at tlvHeaderDecode unpack requires a bytes object of length 8
    read fail: not enough data
    Exception in Data parsing: unpack requires a bytes object of length 40
    Not enough data
    Data length: 82
    Reported Packet Length: 2624
    TLV type: 16384
    Exeption at tlvHeaderDecode unpack requires a bytes object of length 8
    read fail: not enough data
    Exception in Data parsing: unpack requires a bytes object of length 1
    Not enough data

     

    Thanks 

    Shraddha

  • 0 in reply to Shraddha Swami
    TI__Mastermind 23725 points

    Hello

    For #1)  XDS uart driver apples to all demos as it could be the uart to USB related.

    #2) If  gui procied by TI is working well then  that means the Demo and Data stream out from device doesn't have issues.

    #3) Would you be able to inspect the TLV at which it failed and confirm if :

    Data out from the device matches the TLV expectations.

    Pipe TLV to your parser in offline and single step to where the failure occurs.

    In general it will be difficult for us to help debug a custom parser.  We can help if you debug errors in  TLV data. Please see if the parser logic you have implemented is consistent with TI's gui/TLV expecations.

    Please try changing the frame rate to see if sped and size of data makes a difference.

    Thank you,

    Vaibhav