AWR2E44PEVM: rlSetSubFrameStart return the error code : RL_RET_CODE_FRAME_ALREADY_ENDED

wu bin

Prodigy 150 points

Part Number: AWR2E44PEVM

Tool/software:

Hello Expert,

Sometimes, rlSetSubFrameStart return the error code(RL_RET_CODE_FRAME_ALREADY_ENDED) . The error rate is approx. 3%.

What triggers the RL_RET_CODE_FRAME_ALREADY_ENDED error? Why is RL_RET_CODE_FRAME_ALREADY_ENDED?

If we add 250us delay after rlSensorStart, the error no longer occurs during a 1-hour continuous test. I don't find the requirement for delay between rlSensorStart and rlSetSubFrameStart from mmWave-Radar-Interface-Control.pdf. I am certain that the previous frame is end, so i don't kown why 250us delay is useful for this error.

Can you explain this test result?

The SDK version is mmwave_mcuplus_sdk_04_07_01_01 and dfp version is mmwave_dfp_02_04_17_01.

Regard,

Bin

4 months ago

0 Shailesh Joshi 4 months ago

TI__Expert 5431 points

Hello Bin,

After sending the rlSensorStart, did you wait to receive async event - AWR_AE_RF_FRAME_TRIGGER_RDY_SB from the device before sending rlSetSubFrameStart?

Regards,

Shailesh

0 wu bin 4 months ago in reply to Shailesh Joshi

Prodigy 150 points

Hello Shailesh,

After adding a semphore_pend to wait for the AWR_AE_RF_FRAME_TRIGGER_RDY_SB async event, the RL_RET_CODE_FRAME_ALREADY_ENDED error no longer occurs.

Thank you very much.

Regards,

Bin

0 Shailesh Joshi 4 months ago in reply to wu bin

TI__Expert 5431 points

Thanks for the update, Bin. I will close the thread.

Regards,

Shailesh

Sensors

Sensors forum

AWR2E44PEVM: rlSetSubFrameStart return the error code : RL_RET_CODE_FRAME_ALREADY_ENDED