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.

IWR6843ISK-ODS: CCS DEBUG/IWR6843: ERROR TERMINATES EXECUTION

Part Number: IWR6843ISK-ODS
Other Parts Discussed in Thread: UNIFLASH, MMWAVEICBOOST,

Hi,

I am modifying area_scanner lab from industrial toolbox 4.5.1 to make the custom application. I am using mmwave_sdk_03_05_00_04 and IWR6843ISK-ODS (ES2.0) with mmWaveICBOOST in debug mode. I flashed the xwr68xx_ccsdebug.bin image using Uniflash and then using jumpers changed it to debug mode.

After successfully built, I loaded .xe674 and .xer4f files in CCS, and then, when I send my modified .cfg file I receive the following output in the console:

[Cortex_R4_0] Debug: CLI is operational
Debug: Sending rlRfSetLdoBypassConfig with 0 0 0
============ Heap Memory Stats ============
Size Used Free DPCUsed
System Heap(TCMB) 110592 30968 79624 2048
L3 786176 131072 655104
localRam(TCMB) 4096 512 3584
============ Heap Memory Stats ============
Size Used Free DPCUsed
System Heap(L2) 32768 16032 16736 0
L3 786176 8192 777984
localRam(L2) 60928 15016 45912
localRam(L1) 16384 5632 10752
Starting Sensor (issuing MMWave_start)
Exception occurred in ThreadType_Task.
Task handle: 0x8003f38.
Task stack base: 0x8003f98.
Task stack size: 0x2000.
R0 = 0x00000000 R8 = 0x0801ea14
R1 = 0x21080058 R9 = 0x00000005
R2 = 0x00000090 R10 = 0x0801ffe0
R3 = 0x00000708 R11 = 0x51020000
R4 = 0x0000002c R12 = 0x00000000
R5 = 0x52080000 SP(R13) = 0x08005968
R6 = 0x0801ea25 LR(R14) = 0x00018883
R7 = 0x00000006 PC(R15) = 0x00005eee
PSR = 0x200c019f
DFSR = 0x0000000d IFSR = 0x00000000
DFAR = 0x2108005c IFAR = 0x00000000
{module#43}: line 205: error {id:0x1a0000, args:[0x5eee, 0x18883]}
xdc.runtime.Error.raise: terminating execution

Please let me understand how can I fix it.

Thank you

  • Hello Nastya,

    It is very hard to comment on the problem just looking at this log. Please provide some more information e.g. (not limited to)

    1. The last printout from the application "Starting Sensor (issuing MMWave_start)" is coming from mss_main.c as shown below. Please put a breakpoint and try single stepping the code from this point to localize where the code crashes.

    2. What changes did you make to the code? Try to provide a high level idea first i.e. what's your objective and then what changes did you make?

    Regards

    -Nitin

  • Hi Nitin,

    1. The code crashes at MmwDemo_transmitProcessedOutput function in mss_main.c

    line 1494   header.frameNumber = result->stats->frameStartIntCounter;

    Here, it enters to exception and prints everything I showed you in the console. 

    2. I changed DPU: instead of tracking algorithm running on DSP I use clustering algorithm. On the DSP, I collect X number of frames and then put them as an input to the clustering algorithm. My goal is to get the output from the clustering algorithm.

     _

  • Hi Nastya,

    Thanks for the information. Again, given the limited context, and your custom code, it is difficult to comment on the cause of the crash. The best way to debug this would be to put breakpoints in this function and/or the last known successfully executed statement in the code, and single step from there.

    Before trying to debug code, please make sure to review the instructions given in the following training and the section highlighted here:

    Easy evaluation and development of mmWave systems with software development kit - Section "Software Development and Debugging"

    One thing I can think of is the DSP to MSS address translation requirement. As you can see in the existing code, you need to translate buffer addresses coming from DSP side to equivalent MSS side addresses before you can access them in the MSS. Have you made sure to translate the address for your custom output buffer from the DSP side if you have added any?

      

    -Nitin

  • Hi Nitin,

    Of course, I understand that you can't advise me much on my custom code, but it's not what I asking from you.

    The code crashes at the part of the code I didn't touch at all, so I decided to ask you because it doesn't look like something that I did. Before the mentioned line the code reads configurations fine, but after that everything is crashed, all configurations and results have strange values. In the debug, at this line, it enters the exception right away and I am not sure way. 

    Can you advise me on anything else I can do to understand what is the problem and how can I fix it?

  • Hello Nastya,

    You mentioned the code crashed at the following line in mss_main.c.

    line 1494   header.frameNumber = result->stats->frameStartIntCounter;

    Please look at the source and destination data buffers in CCS expression window to check if they are valid addresses. Please provide a snapshot of the expression window with these pointers fully expanded at this point.

    -Nitin

  • Hello,

    As we have not heard back from you on this thread, we'll close it. Please create a new thread if further support is required.

    Thanks

    -Nitin