AWR1243: Cascade Radar configration error

Hi JG

Apologies on my delay in responding to this. There is a limit in the code for the total allocatable buffer sizes to ~300 MB. When you increase the sampling points the buffer size becomes larger and then causes the total size to be beyond ~300 MB.

You can refer to https://e2e.ti.com/support/processors/f/791/t/567237 for a guide on how to change the memory map to increase the size of the DDR.

Thanks and Regards

Piyali

Hi Piyali,

I changed the DDR used by the BIOS from 512M to 1024M, but I still couldn't reach 512 sample points and 128 chirps,so I made the following changes to the code: 

Now the code is working, but it will print this when it starts:

Will this cause any problems?

And if I change both the number of sample points and the chirps to 256, the code will still report an error even if the frame time is increased to 1000ms:

The return value is 77, what does this mean?

Thanks and Regards

JG

JG

The second error of 256 giving an error of 77 is because the Frame config only accepts 1 to 255 as the number of chirps.

Please use the number of chirps parameter to 255 or lower.

Thanks and Regards

Piyali

JG

You should not be reducing the buffers for the VIP capture, you may start seeing dropped frames, Can you please highlight what were the memory map changes you have made?

Thanks and Regards

Piyali

Hi Piyali,

1. I tried 255 chirps and 200 chirps, but this error occurred:

And this error occurs when I change to 120 chirps:

Does chirp have to be an integer power of 2?

2.I modified it according to chapter 6.5 of the VisionSDK_UserGuide_MemoryMap document you provided.

I am now using SDK3.7. The configuration in this SDK is as follows:

And I noticed that the configuration used in SDK3.8 changed to:

So this goes from 16 to 6. Why does this parameter vary so much in SDK3.8?

Thanks and Regards

JG

JG

The first failure is that the total height of the frame for VIP should be less than 2048. This comes from the fact that the VIP registers cannot figure out the size of the frame unless < 2048. This does not really disallow the VIP to capture the frame. Hence, if you want to capture frames greater than 2048 total height (num chrips * numchrip loops) then you can comment out the following lines in the code:

Function:VpsCore_vipCheckMaxSizeParams

File: C:\PROCESSOR_SDK_VISION_03_08_00_00\ti_components\drivers\pdk_01_10_04_05\packages\ti\drv\vps\src\vpslib\captcore\src\vpscore_vip.c

Lines to be commented:

/*
* maxOutHeight:
* should be in the range of [1, 2048].
*/
if ((vipMaxFrmPrms->maxOutHeight[regCnt] <
VPS_VIP_MAXSIZE_MIN_HEIGHT) ||
(vipMaxFrmPrms->maxOutHeight[regCnt] > VPS_VIP_MAXSIZE_MAX_HEIGHT))
{
retVal = BSP_EINVALID_PARAMS;
}

Please make sure the width is correct. If the width is more than 4096 16 bit points then the VIP will not be able to capture this.

Thanks and Regards

Piyali

JG

For Doppler FFT we support only power of 2 sizes.

So this goes from 16 to 6. Why does this parameter vary so much in SDK3.8? --> This is done to reduce the memory requirement. Please note one should not go below 6 as the VIP timing versus the processing timing causes the buffers to start dropping.

Thanks and Regards

Piyali

Hi Piyali，

I tried to reduce the total height to below 2048, and the first error disappeared, but the following error remained:

This error seems to occur if the chirp number is not an integer power of 2.

I understand that the Doppler FFT shoule be power of 2 sizes, but there should be no such limit for the number of chirps.

Do I need to adjust other places to eliminate this error?

Thanks and Regards

JG