• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 793 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.

IWR1443BOOST: profile.cfg with 1024 ADC samples

Gennadii Lichkov
Intellectual 930 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443

Hi,

 

Is there working profile.cfg with 1024 ADC samples?

 

I try my own below

 

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 8 1 0

adcCfg 2 1

adcbufCfg 0 1 0 1

profileCfg 0 77 5 5 134 0 0 50 1 1024 8000 0 0 30

chirpCfg 0 0 0 0 0 0 0 1

frameCfg 0 0 1 0 100 1 0

guiMonitor 1 1 0 0 0 1

cfarCfg 0 2 8 4 3 0 1280

peakGrouping 1 1 1 1 229

multiObjBeamForming 1 0.5

clutterRemoval 0

calibDcRangeSig 0 -5 8 256

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

sensorStart

 

Demo Visualizer says:

Error: incorrect config reported by target

And

Exception: sensor_mgmt.c, line 321.

Regards,

Gennadii

  • 0
    TI__Guru 50240 points
    Hi Gennadii,

    I'd recommend looking at the chirp configuration relating to Level Sensing in the TI-Resource Explorer (TI-REX): dev.ti.com/.../

    This is a tested and working chirp configuration with 1023 ADC Samples but it likely will not work with the mmWave Visualizer because it is more sophisticated than what the Visualizer is used to. Regardless I believe that you will find that quite a few of these chirp configurations will be useful for your application.


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Intellectual 930 points
    Hi,
    I try Level Sensing profile. Unfortunately it doesn’t work with MMWAVE SDK 01.01.00.02
    I have to add strings to the end.
    Here is my new profile.cfg

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 1 1 0
    adcCfg 2 1
    adcbufCfg 0 1 0 1
    profileCfg 0 77 7 12.2 79.72 0 0 20.76 1 1023 15378 0 0 36
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 8 0 100 1 0
    guiMonitor 1 1 0 0 0 1
    cfarCfg 0 2 8 4 3 0 1280
    peakGrouping 1 1 0 1 1022
    multiObjBeamForming 0 0.5
    calibDcRangeSig 0 -5 8 256
    clutterRemoval 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
    sensorStart

    I use the profile for mmw demo.
    It rise error in file: data_path.c
    In function:
    void MmwDemo_dataPathConfigCommon(MmwDemo_DataPathObj *obj)
    In section /* CONFIG WINDOW RAM */
    In second loop on Doppler Bins: winLen = obj->numDopplerBins;
    Call below returns error code
    errCode = HWA_configRam(obj->hwaHandle,
    HWA_RAM_TYPE_WINDOW_RAM,
    (uint8_t *)&fftWindow,
    sizeof(uint32_t), //size in bytes
    hwaRamOffset); //offset in bytes

    Error: HWA_configRam returned -2801

    HWA_configRam parameters here (hwa_internal.c) :
    startIdx = 4096
    dataSize = 4

    I get same result when I change guiMonitor parameters as below.
    guiMonitor 0 1 0 0 0 1

    I don’t need Doppler Bins but range only.
    I know that IWR1443 has 4096 bytes RAM for Windowing. It’s well enough for 1024 ADC samples.

    Is it possible to get working profile.cfg for 1000 or even 1024 ADC samples or repair your SDK code?

    Regards,
    Gennadii