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

IWR1642BOOST: Number of chirps per frame with the SDK firmware ?

OLIVIER GUICHARD
Prodigy 50 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642

Hi,

I'm using the IWR1642BOOST board with a DCA1000 to capture raw packets.

I'm also using the default SDK firmware in the IWR1642.

I'm wondering how I can compute the number of chirps per frame, because the amount of captured data with the DCA1000 does not match my expectations ?

So something is wrong in my computation !

Parameters, according to profile (see below):

- 4 RX channels, complex I/Q -> 8 samples

- 256 samples per chirp (sampling frequency is 5500 KHz)

- 2 chirps profile '0' and '1' + 32 loops ==> should be 64 chirps per frame ???

So, for one frame of 100 ms, I should receive 8x256x64 samples. Samples are 16-bit. So total amount of raw data should be 262144 bytes (256 KB),

but I receive twice this amount of data (512 KB per frame).

So what is wrong ?

Thanks

OG

dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 77 7 7 58 0 0  68 1 256 5500 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 32 0 100 1 0
bpmCfg -1 0 0 1

  • 0
    TI__Expert 4025 points
    Hi Olivier,

    It looks like you're capturing complex data, so this will double the size. If you switch to only capturing real data (adcCfg2 0), you will receive the size you calculated.

    Hope this helps.

    -Chloe
  • 0 in reply to Chloe Shay71
    Prodigy 50 points
    Hi,
    Thanks, but I already took into account the complex data:
    - 4 complex channels = 8 samples = 16 bytes
    - 256 samples per chirp
    - 2 chirp profiles x 32 loops = 64 chirps per frame
    TOTAL should be 16x256x64 = 256 KB of raw data per frame, but I receive 512 KB ???
    I probably miss something in the chirp configuration...
    OG

    My full profile:

    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 0 1 0
    profileCfg 0 77 7 7 58 0 0 68 1 256 5500 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    bpmCfg -1 0 0 1
    frameCfg 0 1 32 0 100 1 0
    lowPower 0 1
    guiMonitor -1 1 1 1 0 0 1
    cfarCfg -1 0 2 8 4 4 0 5120
    cfarCfg -1 1 0 8 4 4 0 5120
    peakGrouping -1 1 0 0 1 224
    multiObjBeamForming -1 1 0.5
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    clutterRemoval -1 1
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    nearFieldCfg -1 0 0 0
    CQRxSatMonitor 0 3 4 127 0
    CQSigImgMonitor 0 63 8
    analogMonitor 1 1
    lvdsStreamCfg -1 0 0 0
  • 0 in reply to OLIVIER GUICHARD
    TI__Expert 4025 points
    Hi Olivier,

    Can you please sent me your output log from mmWave Studio, so I can take a closer look.

    -Chloe
  • 0 in reply to Chloe Shay71
    Prodigy 50 points
    Hello,
    Sorry, I found the issue last week.
    In fact, I'm not using mmWave Studio, but my own software and there was a mistake in the CONFIG_FPGA_GEN command for the DCA1000. I was using parameters for the 1443 chip instead of 1642. Now, everything is working fine. I receive the correct number of bytes from the DCA1000 interface.
    Thanks for your support
    OG