IWRL6432AOPEVM: decode radarCube

Part Number: IWRL6432AOPEVM
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi, 

I am looking for help to decode the radar cube coming from the example xWRL6432_Raw_Data_Over_SPI.

I modified the mmw_cli.h file in order to output the radar cube by setting the #define SPI_DATA_STREAMING to 2. Then, I used the spi_data_capture.py script to store the output of the radar, and I tried to decode it. Unfortunately, I think I am missing something because I always get only half of the expected radar cube size. For example, I used this configuration:

********** Config Sent Successfully **********
Number of ADC samples: 128
Number of chirps per burst: 2
Number of bursts per frame: 32
Number of frames being captured: 1
Number of RX antennas: 3
Number of TX antennas: 2
***********************************************

Then, the spi_data_capture.py script says that it expects 49152 bytes, but the recording stops with only half of this value in the file.

Is it possible to get some help to understand how I can decode the output of this example by using directly the radar cube from the example?

Thank you in advance for your help

Etienne D

  • Hi Etienne, 

    The radar cube size for this example is calculated as: numRangeBins * numChirpsPerBurst * numBurstsPerFrame * numRxAntenna * numTxAntenna * 2 bytes. So this is why spi_data_capture.py says that 49152 bytes is expected. 49152 = 64 * 2 * 32 * 3 * 2 * 2. 

    Can you share the cfg file you are using to configure the sensor? Also, please let me know the version of the software you are using (SDK, Radar Toolbox, etc...)

    Best regards,

    Josh

  • Hi Josh, 

    Thank you for your response. 

    Thank you for the clarification of the calculation of the size of radar cube. 

    sensorStop 0
    channelCfg 7 3 0
    chirpComnCfg 8 0 0 128 1 28 2
    chirpTimingCfg 6 63 0 75 60
    frameCfg 2 0 200 32 1000 1
    guiMonitor 2 1 0 0 0 1 0 0 0 0 0
    sigProcChainCfg 32 2 1 0 4 4 0 15
    cfarCfg 2 8 4 3 0 12.0 0 0.8 0 1 1 1
    aoaFovCfg -60 60 -40 40
    rangeSelCfg 0.1 12.0
    clutterRemoval 1
    antGeometryCfg 1 1 1 0 0 1 1 3 1 2 0 3 2.5 2.5
    compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 1.00000 0.00000 1.00000 0.00000 1.00000 0.00000 1.00000 0.00000 1.00000 0.00000
    adcDataSource 0
    adcLogging 2
    lowPowerCfg 0
    factoryCalibCfg 1 0 40 3 0x1ff000
    sensorPosition 0 0 1.44 0 0
    minorStateCfg 5 4 40 8 4 30 8 8
    majorStateCfg 4 2 30 10 8 80 4
    clusterCfg 1 0.5 2
    sensorStart 0 0 0 0

    Here is the configuration I use. 

    I'm working with the last SDK: 05_05_03 and the last radar toolbox 3_20_00_04. 
    the board is the IWRL6432AOPEVM. 

    Best Regards, 

    Etienne D

  • Etienne, 

    Thank you for the additional details. Everything looks normal in your configuration, one more question from my side: After modifying mmw_cli.h to output the radar cube, are you re-flashing a newly compiled appimage and booting in functional mode or you're loading the code to RAM in debug mode in CCS? Or both? 

    I will attempt to replicate the issue on my end. 

    Best regards,

    Josh

  • Hi Josh, 
    I compile the appimage and flash it with Uniflash and boot in functional mode. 

    Best Regards, 

    Etienne D

  • Etienne, 

    Thank you for confirming. I've not been able to replicate this issue yet. However, I noticed the developer guide for xWRL6432 SPI data capture mentions that SDK 5.4.0.1 is required so it may not support SDK 5.5.3. Can you try installing SDK 5.4.0.1 and recompiling?

    Regards,

    Josh

  • Hi Josh, 
    I will try tank you.

    Regards, 

    Etienne D