• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 549 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MMWAVE-SDK: AWR6843AOPEVM / CCS 10.1.1 - xdc.runtime.Error.raise: terminating execution - breakpoint in objectdetection.c file.

Darshan Shet
Prodigy 20 points
Part Number: MMWAVE-SDK
Other Parts Discussed in Thread: AWR6843AOP

Hi Team

I am running mmwave sdk 3.5.0.4 - xwr68xx demo on AWR6843AOP EVM - Rev F  in debug mode in CCS version : 10.1.1.

When I  put breakpoint in C:\ti\mmwave_sdk_03_05_00_04\packages\ti\datapath\dpc\objectdetection\objdetdsp\src\objectdetection.c under function DPC_ObjectDetection_execute.  the code is terminating with below error

[Cortex_R4_0] **********************************************
Debug: Launching the MMW Demo on MSS
**********************************************
Debug: Launched the Initialization Task
Debug: mmWave Control Initialization was successful
Debug: mmWave Control Synchronization was successful
[C674X_0] Debug: DPM Module Sync is done
[Cortex_R4_0] Debug: CLI is operational
Debug: Sending rlRfSetLdoBypassConfig with 0 0 0
============ Heap Memory Stats ============
Size Used Free DPCUsed
System Heap(TCMB) 32768 27024 5744 3072
L3 786432 196608 589824
localRam(TCMB) 4096 512 3584
============ Heap Memory Stats ============
Size Used Free DPCUsed
System Heap(L2) 32768 16112 16656 0
L3 786432 8192 778240
localRam(L2) 50176 15016 35160
localRam(L1) 16384 5632 10752
Starting Sensor (issuing MMWave_start)
{module#9}: "C:\ti\mmwave_sdk_03_05_00_04/packages/ti/datapath/dpc/objectdetection/objdetrangehwa/src/objdetrangehwa.c", line 640: error {id:0x10000, args:[0x1ce3c, 0x1ce3c]}
xdc.runtime.Error.raise: terminating execution
**********************************************

The line no: 640 in objdetrangehwa.c" corresponds to 

/* Check if previous frame (sub-frame) processing has completed */
DPC_Objdet_Assert(objDetObj->dpmHandle, (objDetObj->interSubFrameProcToken == 0));

When I tried putting breakpoint in objdetrangehwa.c file, the debug mode is working fine, there is no termination.

We just want to know  whether it is the known issue caused from using both the core in xwr68xx pipeline? or issue contained in only SDK 3.5 ?  How to resolve it?

Please let me know if in need any other details.

Regards

Darshan

-

  • 0
    TI__Genius 17265 points

    Hi Darshan,

    It may be helpful to mention what demo you are running or your code is based on. However, I believe I know the issue and it will not be needed. When using both the MSS and DSS, it is recommended not to use breakpoints after sensorStart for most debugging. When you use a breakpoint to stop one core (DSS in this case), the MSS and RadarSS continue their normal data processing, completely unaware that the DSS has been halted. When this happens, you will typically see errors for a number of reasons. The other cores may be trying to read data that has not been written by the other subsystem due to where you halted, or altenatively the other cores may be continuing to write data for the DSS, which is overflowing DSS buffers since you are not handling them any longer.

    If you are debugging after sensorstart, you will likely want to use prints (depending on frequnecy) or use a breakpoint that will have all the necessary information you need BEFORE the device crashes, meaning that you do not need to continue stepping through code. 

    Let me know if there is anything else I can help you with. 

    Best Regards,
    Alec