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: dat file from mmwave demo visualizer reading
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.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Kyle Cousino:
In reply to Li Lu:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.