Tool/software:
Hi,
I want to build a single Tx, 4 Rx TDM configuration.
I built the following one and it works fine (checked using loading the configuration file into Visualizer):
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 1 0
adcCfg 2 0
adcbufCfg -1 1 1 1 1
lowPower 0 0
profileCfg 0 77 10 10 140 0 0 2.8 1 512 4200 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 128 0 512 100 1 0
lowPower 0 0
guiMonitor -1 1 1 0 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.5
calibDcRangeSig -1 0 -5 8 256
clutterRemoval -1 0
antGeometryCfg 1 0 1 1 1 2 1 3 0 2 0 3 0 4 0 5 1 4 1 5 1 6 1 7 1 8 1 9 1 10 1 11 0.5 0.8
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 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 22.88
cfarFovCfg -1 1 -1 1.00
extendedMaxVelocity -1 0
calibData 0 0 0
spreadSpectrumConfig 1 1 0.25 1 0 0 0 0 0 0 0 0
sensorStart
As you can see, the Radar Cube size in this case is:
Nfft_range = 512
Nfft_Doppler = 128
Sample_size = 2 bytes (Real sample)
Number of virtual channels = 1Tx * 4Rx = 4
So, the Cube size = 2*512*128*4=524288 Bytes = 0.5MByte
Suggesting that L3 size in the chip is 2.5M, we are by far from the memory limit.
Moreover, based on the datasheets, the maximal number of loops in a frame is limited by 255.
So, basically, I should be able to increase the number of loops in the configuration to 255 without any problem.
However, once I set it to 255, that is, writing
frameCfg 0 0 255 0 512 100 1 0
the loading is successful (see that in the visualizer prompt), but the visualizer doesn't run, in other words something is wrong with the configuration.
Please explain which additional constrains exist in the chip that limit this increase in the number of loops.
Arie