AWR1843: Limitation of detection processing

Hello Kazuki,

I don't fully understand your query here.

AWR Device supports max of 4 profile configurations.

What is that limitation you are asking here?

Processing time depends on lot of factors: no. of sample in each chirp, no. of chirps in a frame, chirp idle time etc.

Please elaborate on your query with more details.

Regards,

Jitendra

Hello Jitendra,

I apologize for any confusion.

I think there is limitation of data size per frame. (in OOB demo)

This data size would be calculated by 16bit * no. of Tx antenna * no. of Rx antenna * no. of sample * no. of chirp.

How is the limitation of data defined in OOB demo?

And is it possible to change this limitation? Let me know how to change it if possible.

Regards,

Kazuki

Hello Jazuki,

For radar signal processing you need to do 1D, 2D and 3D FFT. and you need to store 1D result of all the chirp in the memory to further calculate the 2D, 3D FFT and other algo on it.

So the limitation is due to the memory required to store these result on L3/L2 memory of DSP.

One RadarCube data size = 16bit * 2(if complex data)* no. of Rx antenna * no. of sample * no. of chirps

no. of tx doesn't include in this formula.

Configuration should not be exceeded the memory available on the device.

For AWR1843 device, available memory can support all possible medium range use-case.

Are you facing memory limitation with your particular use case or configuration to implement on AWR1843 device??

Regards,

JG

Hello Jitendra,

I would like to use below parameters if possible.

This parameter was optimized for medium range (<100m) use-case.

I understand there are many trade-off relationships. (max range, range separability, max speed, speed separability)

So, I would like to define a parameter achieving high performance as much as possible.

Could you tell me a limitation of memory and solution of way to operate by below parameters if possible.

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 76.57 2.6 4.5 30.6 0 0 11.71875 1 256 10000 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
frameCfg 0 2 128 0 100 1 0
lowPower 0 1
guiMonitor -1 1 0 0 0 0 0
cfarCfg -1 0 2 8 4 3 0 15 1
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 1 0.5
clutterRemoval -1 0
calibDcRangeSig -1 0 -5 8 256
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
CQRxSatMonitor 0 3 5 121 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 8.92
cfarFovCfg -1 1 -1 1.00
sensorStart

Best Regards,
Kazuki

Hello Kazuki,

Are you facing errors with this CLI command list?

And which SDK version you are trying this?

Regards,

Jitendra

Hello Jitendra,

Yes.

I'm facing errors with this CLI command list and these command are loaded by 'LOAD CONFIG FROM PC AND SEND' in 'mmWave Demo Visualizer'.

I show my environment below.

[SDK]

 mmwave_sdk_03_03_00_03

[Loading image ]

‘…\ti\mmwave_sdk_03_03_00_03\packages\ti\utils\ccsdebug\xwr18xx_ccsdebug.bin’

[Demo]

out-of-box 

[CCS]

8.3.1.00004

[mmWave Demo Visualizer]

3.4 (not cloud version)

I just want to know a data size limitation of radar cube and how to change this limitation.

Regards,

Kazuki

Hello,

I resolved this issue.

AWR1843 has L3 memory of 1024KB .

http://www.ti.com/lit/ds/symlink/awr1843.pdf?ts=1590988301278

And data size is decided below equation. 

2Byte(16bit ADC output) * 2 (complex) * no. of sample * no. of chirp * no. of Tx * no. of Rx

By the way, IWR6843 has L3 memory of 768KB according to below documents.

https://www.tij.co.jp/lit/ds/symlink/iwr6843.pdf?ts=1590988267768

I understood AWR1843 has bigger memory than IWR6843.

Is this correct?

Regards,

Kazuki