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.

DOA DPU config return error:-2801

Part Number: IWRL6432BOOST


Tool/software:

I am currently attempting to analyze the raw ADC data from the IWRL643BOOST eval board, using SPI transfer. I have gotten this to work with the Motion and Presence detection demo from the SDK (05.05.03.00), using the following config:

sensorStop 0
channelCfg 7 3 0
chirpComnCfg 20 0 0 128 4 32.4 0
chirpTimingCfg 6.00 24 0 84.40 58.63
frameCfg 2 0 358.93 4 250.00 1
sigProcChainCfg 16 2 1 0 2 4 0 20
adcLogging 2
lowPowerCfg 0
factoryCalibCfg 1 0 30 20 0x1ff000
sensorStart 0 0 0 0

However, my issues arise when trying to increase the number of captured samples. Going to 1024, for example, I have attempted config below. I have only changed the chirpComnCfg. chirpTimingCfg and frameCfg entries, using the SDK documentation for the config entries as well as the config generator/validator at https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator/ver/2.5.0/
Currently, I am getting the following error:

DOA DPU config return error:-2801

sensorStop 0
channelCfg 7 3 0
chirpComnCfg 20 0 0 1024 4 211.6 0
chirpTimingCfg 6 24 0 12.9235 58.63
frameCfg 2 0 1000 1 250 1
sigProcChainCfg 16 2 1 0 2 4 0 20
adcLogging 2
lowPowerCfg 0
factoryCalibCfg 1 0 30 20 0x1ff000
sensorStart 0 0 0 0

Any suggestions on what I might be doing incorrectly would be appreciated. Do I need to update the firmware in any way?

  • Hi,

    1. Make # of chirps a power of 2

    2. Reduce range FFT size. It is too large.

    Best

    Nate

  • Hi Nate, thank you for your response.

    I don't quite follow you, as my chirp_count (frame_cfg[0]) is already a power of two (2), and there is no range FFT specified in the config. There is an Azimuth FFT size, currently set to 16, but reducing it does not seem to help.
    As far as I understood, with two TX antennas I would need 2 chirps per burst for both to transmit?

    However, I noticed that increasing the chirp_count from 2 to 4 allowed the number of samples to go up to 512. I still don't understand why what I was doing was incorrect.
    Also, increasing the number of chirps in a burst doesn't achieve what I wanted, which was a higher resolution when sampling the FMCW wave for each chirp.

     

  • Hi,

    Burst count is 1000, this also needs to be a power of 2 (2 chirps / burst * 1000 bursts = 2000 chirps, which is not a power of 2).

    Range FFT will be dictated by the number of ADC samples (1024), which is too high.

    Can you make your changes sequentially and figure out which one is breaking your configuration? I suspect it's the number of bursts (too large and not a power of 2), but you can verify this by changing the values one by one.

    Best,

    Nate