Other Parts Discussed in Thread: MMWAVEICBOOST,
Hi all,
I’m currently experiencing issues while debugging the IWR6843ISK + MMWAVEICBOOST setup.
I’m working with the “68xx Vital Signs” module from Industrial Toolbox 4.12.1, extending its functionality for further development.
However, when I run the code in debug mode, I encounter an assertion failure caused by a deadline miss.
The log shows as:
C674X_0: Debug: MMWDemoDSS mmWave Control Initialization succeeded
Cortex_R4_0: **********************************************
Cortex_R4_0: Debug: Launching the Vital-Signs Monitoring Demo
Cortex_R4_0: **********************************************
Cortex_R4_0: Debug: VitalSignsDemoMSS Launched the Initialization Task
C674X_0: Debug: MMWDemoDSS Data Path init succeeded
C674X_0: Debug: MMWDemoDSS initTask exit
C674X_0: Debug: Sending Vital Signs Configuration Message
C674X_0: Debug: MMWDemoDSS Config event received, starting configuration...
C674X_0: Heap L1 : size 16384 (0x4000), free 14320 (0x37f0)
C674X_0: Heap L2 : size 49152 (0xc000), free 35096 (0x8918)
C674X_0: Heap L3 : size 786432 (0xc0000), free 618144 (0x96ea0)
C674X_0: Debug: MMWDemoDSS Data Path config succeeded
C674X_0: Debug: MMWDemoDSS Data Path start succeeded
C674X_0: {module#8}: "../dss/dss_main.c", line 346: error {id:0x10000, args:[0x817ec4, 0x817ec4]}
C674X_0: xdc.runtime.Error.raise: terminating execution
The code snippet causing the issue is:
/* Check if previous frame processing has completed */
if (gMmwDssMCB.dataPathContext.interFrameProcToken != 0)
{
MmwDemo_triggerDss2MssISR(MMWDEMO_DSS2MSS_FRAME_PROC_DEADLINE_MISS_EXCEPTION);
DebugP_assert(0);
}
To reproduce the issue, I follow these steps:
-
Run the DSS module.
-
Run the MSS module.
-
Send the CFG file through the CLI.
At this point, logging shows assertion failure due to a deadline miss, after receiving "sensorStart."
Interestingly, this problem only appears when running in debug mode. When the code is executed in normal (non-debug) mode, everything works without errors.
Has anyone encountered this behavior before or found a way to resolve it?
CCS version: 20.3
SDK version: mmwave_sdk_03_05_00_04