IWR6843AOP: DPU_RangeProcHWA_process processing time measurement

Part Number: IWR6843AOP


Hello TI Team,

    1. I did measure the processing time for DPU_RangeProcHWA_process. 

       I did use the configuration 

      sensorStop
      flushCfg
      dfeDataOutputMode 1
      channelCfg 1 1 0
      adcCfg 2 1
      adcbufCfg -1 0 1 1 1
      %profileCfg 0 60 359 7 57.14 0 0 70 1 256 5209 0 0 158
      profileCfg 0 60 5 1 55.14 0 0 70 1 128 2500 0 0 158
      chirpCfg 0 0 0 0 0 0 0 1
      frameCfg 0 0 2 0 5 1 0
      lowPower 0 0
      guiMonitor -1 1 1 0 0 0 1
      %guiMonitor 0 0 1 0 0 1
      cfarCfg -1 0 2 8 4 3 0 15 1
      cfarCfg -1 1 0 4 2 3 1 15 1
      multiObjBeamForming -1 0 0.0
      clutterRemoval -1 0
      calibDcRangeSig -1 0 -5 8 128
      extendedMaxVelocity -1 0
      lvdsStreamCfg -1 0 0 0
      compRangeBiasAndRxChanPhase 0.0 1 0 -1 0 1 0 -1 0 1 0 -1 0 1 0 -1 0 1 0 -1 0 1 0 -1 0
      measureRangeBiasAndRxChanPhase 0 1.5 0.2
      analogMonitor 0 0
      aoaFovCfg -1 -90 90 -90 90
      cfarFovCfg -1 0 0 8.92
      cfarFovCfg -1 1 -1 1.00
      sensorStart
      I'm using a single RX and a single TX antenna, and I only calculate the Range; I don't need another processing of out_of_box_6843_aop yet.

      HWA Range Processing time = about 128.49 microseconds

      Is it correct?
    2. How can I use the downChirp in this out_of_box_6843_aop?
    3.  How can I use the numLoops by 1?
      I need to use the HWA.

Best Regards,

Eric.

  • Hello.

    We are looking into this; please provide us a day or two to provide a response.

    Sincerely,

    Santosh

  • Hi,

    The processing time would vary by the configuration used. Could you elaborate a bit more on what you need to do with HWA?

    Regards

  • Hello Sharan,
    I did use the single RX, single TX antenna, and only calculated the Range using the HWA by down chirp. 

    I'm using this configuration currently

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 1 1 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    profileCfg 0 63.95 5 1 55.14 0 0 -70 1 128 2500 0 0 30
    %profileCfg 0 60 5 1 55.14 0 0 70 1 128 2500 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 2 0 5 1 0
    lowPower 0 0
    guiMonitor 0 0 1 0 0 0 1
    cfarCfg -1 0 2 1 1 1 0 15 1
    multiObjBeamForming -1 0 0.0
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -1 1 1
    extendedMaxVelocity -1 0
    lvdsStreamCfg -1 0 0 0
    compRangeBiasAndRxChanPhase 0.0 1 0
    measureRangeBiasAndRxChanPhase 0 5.30 0.0
    analogMonitor 0 0
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 5.35
    sensorStart


    Best Regards,
    Eric.

  • Hi eric,

    Thanks for the explanation. What do you need help with respect to HWA?

    Regards

  • Hello Sharan,
    Many thanks for your feedback.
    1.If I use numloops = 2, how does it work? 

    I did use single RX, single TX, and estimated only the range on the HWA by downchirp.

    Does it work like this?

    HWA processing time = ~ 137.61 μs. Is Chirp's processing on the HWA?

    If it’s not the same, could you show some diagrams of how it works?

    2. Can I use a single chirp with HWA that processes only range?
    Best Regards,
    Eric.

  • Hi Eric,

    numloops is basically the number of the times the entire paramset chain gets executed repeatedly.
    Yes, you can use a single chirp with only 1 TX and 1 RX for calculating just 1D FFT and range.

  • Hello Sharan,
    Thanks for your feedback.
    Do you have any examples?
    Regards,

    Eric.

  • Hi Eric,

    You can refer to level sensing demo that uses 1TX and 1RX with range and zoom FFT.