AWR1843: xdc runtime error raise: terminating execution

Hi Lei,

The assert essentially means that the data path task did not have sufficient time to complete processing the previous frame when the current frame arrived.

One issue I can think of is that if the UART is configured in polled mode, and the UART task is at a higher priority than the datapath task, the task may indefinitely block the datapath task, causing this issue.

Could you confirm this, and if this is the case, try changing task priorities to avoid this issue?

To avoid this on the MSS side, we keep the CLI task priority low enough that all other necessary tasks can preempt it.

Regards,

Aayush

Thanks Aayush, 

I set the taskParams.priority  = 2; for this task.

As I know the larger the higher, priority 2 is lower than priority 3.  Is it?

Kind regards

I set the task priority to 1, the lowest priority according to the guide. In mrr demo, datapth task is much higher than it. But it doesn't fix the problem.

Can we solve this issue by increasing the time of frame processing in configuration setting? 

Thanks

Hi Lei,

This would be worth considering. Also, have you modified the data processing in any way? As Cesar mentioned, this assert occurs when the last frame didn't have enough time to process.

Regards,

Aayush

Hi Aayush, I didn't modified the data processing. Can you please tell which parameter is related with time of fram processing?

In mrr demo, Is it: 

#define SUBFRAME_MRR_PERIODICITY_VAL           (6000000U) // 30ms 

?

Thanks

Hi Aayush, is there any update for this ticket?

Regards

Hi Lei,

Sorry for the delay.

Yes, the #define that you had pointed to dictates the time for the MRR subframe. Keep in mind that this define is in multiple config files, you might have to see which one is getting included (and hence applied) in the demo.

Like this, there will also be a variable for the USRR frame in both config header files.

Regards,

Aayush

Thanks Aayush,

If I significantly increase this value, ex.

#define SUBFRAME_MRR_PERIODICITY_VAL           (60000000U) // 300ms 

What problems will this cause?

Regards