• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 2584 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.

AWR1443: ADC raw data has a strange spur

Yang Shen
Prodigy 80 points
Part Number: AWR1443
Other Parts Discussed in Thread: AWR1243

Hello,

We used AWR1443 only. And load image of CaptureDemo project. Use CCS to export one frame of one rx raw data. The sensor setting as:

# adc 16bit 5MSPS complex 360points
# fmcw 77g 360m/72us

flushCfg
dfeDataOutputMode 1
channelCfg 2 1 0
lowPower 0 0
adcCfg 2 1
adcbufCfg 0 0 0 1
profileCfg 0 77 2 4 78 0 0 5 1 360 5000 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 128 1 20 1 0
sensorStart

But there is a strange spur per chirp. Is any setting wrong?

And other two questions:

1. The spec of AWR1443 A2D resolution is 12bit. If configure as 16bit by CLI, is that OK to run normally?

2. The spec of AWR1443 A2D sampling rate (complex) is 6.25MSPS. What if configure as 15MSPS or faster?

  • 0
    TI__Guru 58035 points
    Hello Yang Shen,
    12 bit is a default mode but you can use the 16 bit mode as well. 15Mbps sampling is not supported in the AWR1443 device, for higher sampling rates AWR1243 is recommended.

    Regarding the glitch we will get back to you on this.

    Regards,
    Vivek
  • 0 in reply to Vivek Dham
    TI__Guru 58035 points
    Hello Yang Shen,
    In the capture demo the radar data memory allocated is 128KB. From the configuration you have sent looks like radar data memory required is more than 128KB: 360 samples per chirp * 4 bytes per sample (16 bit complex) * 128 chirps.
    Can you reduce the number of chirps per frame so that the memory requirement is <128KB and try again?

    Regards,
    Vivek
  • 0 in reply to Vivek Dham
    Prodigy 80 points

    Hi Vivek,

    Thanks for your reply.

    I reduce the chirp number to 64. But the glitch still here.

    Then I test the default setting .

    flushCfg
    dfeDataOutputMode 1
    channelCfg 2 1 0
    adcCfg 2 1
    adcbufCfg 0 0 1 1
    profileCfg 0 77 20 5 80 0 0 40 1 256 8000 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 128 1 20 1 0
    lowPower 0 0
    sensorStart

    If set frequency slop as 4MHz/us

    profileCfg 0 77 20 5 80 0 0 4 1 256 8000 0 0 30

    The glitch appeared at first several bins.

    Frequency slop can't be too small?

    Regards,

    Yang Shen

  • 0 in reply to Yang Shen
    TI__Guru 58035 points

    Hello Yang Shen,

    There is no inherent restrictions with lower slopes.  

    Could you try one experiment of reducing the TX start time from 1 to 0 ?

    profileCfg 0 77 20 5 80 0 0 4 0 256 8000 0 0 30

    Regards,

    Vivek

  • 0 in reply to Vivek Dham
    Prodigy 80 points

    Hello Vivek,

    That's OK to reducing the TX start time as this configuration:

    flushCfg
    dfeDataOutputMode 1
    channelCfg 2 1 0
    adcCfg 2 1
    adcbufCfg 0 0 1 1
    profileCfg 0 77 20 5 80 0 0 4 0 256 8000 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 128 1 20 1 0
    lowPower 0 0
    sensorStart

    But if I modify ADC sampling rate, sampling points, frequency slop, etc, some glitches still exist. 

    Where or what tools for customs can I use to check my configuration?  I use Radar Studio now. 

     Regards,

    Yang Shen

  • 0 in reply to Yang Shen
    TI__Mastermind 23725 points
    Hello Yang,

    Can you please confirm you are observing this files from mmwave_sdk_01_00_00_05

    Thank you,
    Vaibhav
  • 0 in reply to Vaibhav Mahimkar
    TI__Guru 58035 points
    Hello Yang,
    Just to confirm I understood it right , by reducing the TX start time to 0 the initial "settling" like behavior is gone?

    To help select the right configuration you can use the sensing estimator tool (dev.ti.com/.../). You need to make sure the radar data cube used is within the allocated memory size. For example in the AWR1443 capture demo this memory is set to 128Kb. So when you change the configuration just make sure its still within this size.

    regards,
    Vivek
  • 0 in reply to Vivek Dham
    TI__Guru 58035 points
    Hello Yang,
    Did this help you resolve the issue you were observing?

    Regards,
    Vivek