• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 387 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.

DCA1000EVM: Clarification on raw data on file and over ethernet

Cagri Tanriover
Intellectual 905 points
Part Number: DCA1000EVM

Hi,

I have been reading quite a few threads on the ADC data related topics and I need some clarification on the raw ADC data format as sent over ethernet and saved as *.bin file BEFORE the post processing. Below is the diagram I prepared for clarification and following are my questions:

1 - In Case 1, does field B give the number of bytes in field C?

2 - In Case 2, does field E give the sum of number of bytes in fields F and field G?

3 - I read in one of the posts that field F actually gives the number of raw mode data bytes received UNTIL that packet (but excluding raw mode data in that packet). If that is correct, field E should give the number of bytes in field G. Can you please confirm? (Also, if this is the case, does field E give the total number of bytes in fields F and G?)

4 - If there are other details I should keep in mind regarding these packet formats, can you please comment?

Thank you for your help.

Regards,

Cagri

  • 0
    TI__Guru 69970 points

    Hello Cagri,

    mmWave Studio provides the DCA1000 CLI source code which captures the raw data over ethernet and stores to a *.bin file.

    You can refer this code for further detail to find how data format is used within it.

    C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\ReferenceCode\DCA1000

     

     Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Intellectual 905 points

    Hi Jitendra,

    I had a look at the code.

    I was able to confirm my question related to Case 1 based on the information in the code. However, for Case 2, the code is pretty difficult to follow to get a straight answer. There are no comments in the code to assist the reader either and therefore following offsets and pointers between multiple functions and conditional statements turned out to be a loss of time.

    I will reverse engineer the output file, which will take less time.

    Cagri

    P.S. In Case 1, there seems to be discrepancies between the #defines for total read buffer size (i.e. 1470 bytes) versus the documentation (i.e. 1472 bytes)