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.

AWRL1432BOOST-BSD: There is an inconsistency within the description of the document and the code in AWRL1432 BOOST BSD.

Part Number: AWRL1432BOOST-BSD
Other Parts Discussed in Thread: AWRL1432

Tool/software:

Hi! Team TI!

 

I am using this board, www.ti.com/.../AWRL1432BOOST-BSD.

I am currently digging into the code of the AWRL1432 BOOST BSD. In this board, I tried to dump the RangeProfile and something like RangeStep, #Rx some basic parameters.

Now I want to dump the Range-Doppler Heatmap.

https://dev.ti.com/tirex/explore/node?node=A__ADnbI7zK9bSRgZqeAxprvQ__radar_toolbox__1AslXXD__1.30.00.05

 

From the above document, the length of each unit in Range-Doppler Heatmap is 2bytes. Type Identifier = 5, type value is MMWDEMO_OUTPUT_MSG_RANGE_DOPPLER_HEAT_MAP .

 

But in the code mmwave_demo.c,

 

if ((pGuiMonSel->rangeDopplerHeatMap) && (result->rngDopplerHeatMap != NULL))

            {

                mmw_UartWrite (uartHandle,

                                (uint8_t*)&tl[tlvIdx],

                                sizeof(MmwDemo_output_message_tl));

 

                {

                    int ii;

                    for (ii=0; ii<gMmwMssMCB.numRangeBins; ii++)

                    {

                        mmw_UartWrite (uartHandle,

                                (uint8_t *) &result->rngDopplerHeatMap[ii*gMmwMssMCB.numDopplerBins],

                                gMmwMssMCB.numDopplerBins * sizeof(uint32_t));

                    }

                }

 

                tlvIdx++;

            }

 

sizeof(uint32_t), means it is 4 bytes, not 2 bytes.

 

And I tried to dump this 4 bytes.

 

Something like this:

 

da03 0000 e402 0000 5d03 0000 df03 0000

1204 0000 f304 0000 5606 0000 d005 0000

7e01 0000 fc00 0000 9e06 0000 5107 0000

f300 0000 3605 0000 8003 0000 2902 0000

7d00 0000 8203 0000 c402 0000 eb03 0000

3707 0000 ee05 0000 9202 0000 fd08 0000

920a 0000 cd0b 0000 770c 0000 aa1a 0000

b13c 0000 20d0 1600 fb88 2200 31b2 1100

c82f 0000 c215 0000 1d09 0000 e30a 0000

d50a 0000 7807 0000 dd01 0000 e205 0000

bc06 0000 5a03 0000 0c02 0000 1b03 0000

9001 0000 5001 0000 7d03 0000 9504 0000

5a00 0000 2706 0000 7f05 0000 ba00 0000

1503 0000 3a07 0000 1807 0000 6b05 0000

0404 0000 5c04 0000 1c04 0000 3002 0000

e102 0000 5d00 0000 9b00 0000 cb00 0000

1005 0000 c303 0000 0f03 0000 9c03 0000

4704 0000 3304 0000 e104 0000 1504 0000

a301 0000 5f01 0000 2907 0000 2508 0000

 

There are actually 2-bytes data and another 2-bytes zero padding, but still some of the data are 4-bytes.

 

The code is from Radar Toolbox – 2.20.00.05 -> Example Projects -> mmWave Demo-> mmWave Demo xWRL1432, import from the triple dots.

 

So which one is correct? 2 bytes or 4 bytes? 

Can anyone help me? Thank you!

 

Best regard,
Webb