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.

AWR1642BOOST: the number of range bins for range profile and noise profile

Part Number: AWR1642BOOST

Many thanks for TI employees to solve my previous question about parsing dat file.

But I have another question. When I parse to range profile and noise profile, the length seems to be contradictory with mmw Demo Data Structure v0.1. From mmw Demo Data Structure v0.1, the length of the profile is #RangeBins * 4 bytes (#RangeBins=256?). But in fact, when I use 128 * 4 bytes, the parse result can be correct. Does #RangeBins equal to Range FFT size? Or maybe the data structure in mmw Demo Data Structure v0.1 is different from that in mmwave SDK 2.0?

Thank you very much.