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.

AM2732-Q1: TIDA-020047: 2x AWR2243 cascading hangs after second frame acquisition

Part Number: AM2732-Q1
Other Parts Discussed in Thread: AWR2243

Hi,

We implemented an applicaion for 2*AWR2243 cascading and the application hangs after receiving the second frame from DSS.

In DSS side we get an error  "Error: Unable to send DPC_OBJDET_IOCTL__TRIGGER_FRAME" .

We used radar configuration from AWR2243 Cascade Application Report SWRA574B.

You will find enclosed logs for both sides MSS and DSS and all the configuration used in the application.

Could you please help to find out the root cause of this issue ?

Thanks.

MSS-logs.txt

DSS-log.txt
NFO: MmwDemo_dssInitTask:791: Start DSS 
INFO: MmwDemo_dssInitTask:898: Debug: DPM Module Sync is done
INFO: DPC_ObjectDetection_ioctl:2873: ObjDet DPC: Pre-start Common Config IOCTL processed
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:295: DSSApp: DPM Report IOCTL, command = 101
INFO: DPC_ObjDet_preStartConfig:2679: Radar Cube Data size 786432.
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:295: DSSApp: DPM Report IOCTL, command = 100
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:304: DSSApp: DPM Report start
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:295: DSSApp: DPM Report IOCTL, command = 115
ObjDet DPC: ---- Processing Frame [1] ---- 
ObjDet DPC: detected objects after CFAR = 0
ObjDet DPC: End Processing 
Detected Objects sent to MSS
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:295: DSSApp: DPM Report IOCTL, command = 114
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:295: DSSApp: DPM Report IOCTL, command = 115
ObjDet DPC: ---- Processing Frame [2] ---- 
ObjDet DPC: detected objects after CFAR = 6
ObjDet DPC: End Processing 
Detected Objects sent to MSS
INFO: MmwDemo_DPC_ObjectDetection_reportFxn:295: DSSApp: DPM Report IOCTL, command = 114
INFO: MmwDemo_DPC_ObjectDetection_FrameTrigTask:739: Error: Unable to send DPC_OBJDET_IOCTL__TRIGGER_FRAME [Error:-1]
ASSERT: 2.47049s: ../src/dss_main.c:MmwDemo_DPC_ObjectDetection_FrameTrigTask:740: 0 failed !!!

  • Hi,

    I have another question about the number of ADC samples for frame configuration for each radar,

    In case the radar is using two profiles, the first has 128 ADC sample and the second 256 Samples , Which the expected value of ADC sample Number that should used for configuring the frame for this radar ?

    Thanks.

  • Hello,

    Another point to check is regarding the profile configuration from AWR2243 Cascade Application Report SWRA574B,

    the second profile doesn't work, I get an error when configuring the radar with this profile:

    But when I change only the Start Frequency from 78 to 77, it accepts the profile.

    Could you check it please and give us the correct configuration ?

    Thanks.

  • Hi Mohamed,

    DPC_OBJDET_IOCTL__TRIGGER_FRAME ioctl is being called based on gMmwDssMCB.DPMTrigFrameSemHandle semaphore post which is done via mmwDemo_DPC_ObjectDetection_csirxSOF0callback.

    Now you need to check if AWR2243 is either sending the CSI data or AM273x device itself is not able to receive the CSI data.

    I have another question about the number of ADC samples for frame configuration for each radar,

    No. of ADC sample must be same for both AWR2243 device (of cascade), so you need to use same profile configuration for given frame on both device. You can enable/disable TX for individual AWR2243 for given chirp or frame using chirpConfig API.

    the second profile doesn't work, I get an error when configuring the radar with this profile:

    What is error value profileConfig returning? you can map that error code to reason of failure as explained in the ICD or mmwavelink.h file.

    .

    Regards,

    Jitendra

  • Hi Gupta,

    We made some modification for the profile configuration and it works now.

    Thanks.