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

IWRL6432BOOST: SPI RAW ADC DATA

Tom Lackinger
Prodigy 80 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432

Tool/software:

Hello TI Team,

I have another question about the IWRL6432 SPI RAW DATA.

So did I understand right, that the ADC Data, which I get over SPI ist captured directly after the IF? So there is no calculation done for example RangeBias und RX Channel Phase Correction?

I'm just wondering because the configuration file seems to define a complete signal processing chain.

sensorStop 0
channelCfg 7 3 0
chirpComnCfg 8 0 0 128 1 15 1
chirpTimingCfg 6 40 2 240 57
frameCfg 600 0 19860 1 40 800
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.5 0 1 1 1
aoaFovCfg -60 60 -40 40
rangeSelCfg 0.1 12.0
clutterRemoval 1
compRangeBiasAndRxChanPhase 0.06559 -0.12472 -0.67939 0.51038 0.58357 -0.53357 -0.62848 0.06786 0.94560 -0.60156 -0.79883 0.57553 0.77879
adcLogging 2
lowPowerCfg 0
factoryCalibCfg 0 1 40 0 0x1ff000
mpdBoundaryBox 1 0 1.48 0 1.95 0 3
mpdBoundaryBox 2 0 1.48 1.95 3.9 0 3
mpdBoundaryBox 3 -1.48 0 0 1.95 0 3
mpdBoundaryBox 4 -1.48 0 1.95 3.9 0 3
sensorPosition 0 0 1.44 0 0
minorStateCfg 5 4 40 8 4 30 8 8
majorStateCfg 4 2 30 10 8 80 4 4
clusterCfg 1 0.5 2
profileSwitchCfg 0 25 25
sensorStart 0 0 0 0


Furthermore I want to get the ADC Smaples not in Burst Mode, so I can measure high velocitys. But it seams that when I turn NumberofBursts in Frame to 1, it doesn't work anymore?

***WARNING*** Sensor did not respond with done
Response: b'DOA DPU config return error:-2801 \n'

  • 0
    TI__Expert 4150 points

    Hi,

    The adc data is captured simultaneously when the actual demo is running. Hence, the entire configuration is required to run the demo, the adc data is just a byproduct output while executing. 

    For the burst error, can you step through  DPU_DoaProc_config and check which conditions fails ?

    Regards

  • 0 in reply to Sharan S S
    Prodigy 80 points

    Thank you.

    I'm a bit confused. I captured the data in BPM mode via SPI, so I need to perform the demodulation myself. However, I don't quite understand how to parse the data, because unlike TDM, there is no direct relation to the individual transmit antennas. I also couldn’t find any documentation on how the ADC data is ordered when captured via SPI in BPM mode.

    Is there any information I might have missed?

  • 0 in reply to Tom Lackinger
    TI__Expert 4150 points

    Hi,

    Please look at the matlab parsing script present in the MMWAVE_L_SDK.

    {SDK_INSTALL_DIR}\tools\ADC_parser\Test_read_adc_data_xWRLx432.m

    Regards

  • 0 in reply to Sharan S S
    Prodigy 80 points

    I saw the script but my problem is, that in BPM mode there is no TX reference, so I the reshape doesn't work for me right? Because I have to demodulate it later or am I wrong?

    elseif adcLogging == 2
    %% Read ADC log file
    fid = fopen('adc_data_spi.txt');
    testadc = fscanf(fid, '%d');
    fclose(fid);
    %testAdcreshape = reshape(testadc,[numAdcSamples,numRx,numChirps*numBursts,numFrames]);
    adc_spi = reshape(testadc,[n_samp_per_chirp,n_rx_chan,n_tx_chan,(n_chirps_per_frame*n_bursts),n_frames]);
    adcOut = permute(adc_spi, [5, 3, 2, 4, 1]);
    end
  • +1 in reply to Tom Lackinger
    TI__Expert 4150 points

    Hi,

    Yes you are right. The script doesnt support BPM mode captured data. You have to take care of the demodulation.

    Regards